kickback B-18648 multiplier was showing up as undefined on non FSC items and mileage didn't show comma

Agility Story: B-18648
Test steps I took to recreate

Make a HHG move using the HHGNeedsCounseling test harness data.
Take note of the move locator and the username of the customer that created the move from the JSON object shown.
Navigate back to the Sign In page for customers.
Sign in as the user who created the move.
Go to the move and add a to an HHG move shown.
During the shipment creation process, make sure you enter the following details for Origin and Destination:

Origin ZIP: 01824
Origin Duty Location: Chelmsford MA
Dest ZIP: 62225
Dest Duty Location: Scott AFB

After the shipment has been created, switch to a SC user role under the AGFM and send and approve the move.
Switch to TOO and approve the move.
Switch to Prime and add the following service items:

Origin SIT

Switch to TOO and approve the new service items
Switch back to Prime and choose the "Create payment request" option.
Create payment requests for the following:

FSC
Origin SIT FSC
1st Day Origin SIT

Switch back to the TOO or TIO user role and attempt to review the payment requests.
On each, show calculations and you should get the following findings:

Each of the FSC items should show a weight based FSC multiplier with a value
Mileage value should have a comma in the thousands place

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 14faed602b9bb8b202fa41fc44a5b9a4c1f010de

Comma showing on FSC but not SIT FSC?

Comma showing on FSC but not SIT FSC?

Good catch.. lemme take a look


Code in SPR illustration may be wrong

Search the code for TODO, in make.SPR.illustration()
It looks like it is using the old fecundity assumptions and needs updating.

so this only had an influence on the explanation of SPR in our glossary?

Yes, there was some old code in there from before we changed the fecundity/weight-at age. It made a small difference in the plot and values on the plot in the glossary only.


Using .Chart.name in range function

I'm trying to use the following syntax in one of the templates (deployment.yaml):
        {{- range $key, $value := .Values.secrets }}
        - name: $key
          valueFrom:
            secretKeyRef:
              name: {{ .Chart.Name }}
              key: $value
        {{- end }}

But when I run helm upgrade --install I get this error:
Error: UPGRADE FAILED: render error in "MY_APP/templates/deployment.yaml": template: MY_APP/templates/deployment.yaml:29:25: executing "MY_APP/templates/deployment.yaml" at <.Chart.name>: can't evaluate field Chart in type interface {}

Looks like I'm able to use any kind of variable inside a range function. Neither {{ .Values.env }}
Is it expected behavior?

@idirouhab So because you are in a range block, . no longer refers to the top level scope. I believe you should be able to use $ (e.g. $.Chart.name) to access the top level variables

Thanks @thomastaylor312 ,
unfortunately doesn't work, I tried even defining a variable in the very first line and try to using it but works just for simple string but not variables.
That works:
       {{ $myChartName := "FooBar" }}
        {{- range $key, $value := .Values.secrets }}
        - name: $key
          valueFrom:
            secretKeyRef:
              name: {{ $myChartName }}
              key: $value
        {{- end }}

That doesn't work:
       {{ $myChartName := .Chart.name }}
        {{- range $key, $value := .Values.secrets }}
        - name: $key
          valueFrom:
            secretKeyRef:
              name: {{ $myChartName }}
              key: $value
        {{- end }}

I also face this issue when trying to use .Chart.Name and .Release.Version inside a range

I'm working around this by storing . in a variable.
{{- $dot := . }}
{{- range $name, $data := .Values.configMaps }}
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: {{ $name }}
  labels:
    app: {{ include "cronjob.name" $dot }}
    chart: {{ include "cronjob.chart" $dot }}
    release: {{ $dot.Release.Name }}
    heritage: {{ $dot.Release.Service }}
data: {}

Just to confirm, as per my minimal repro here - https://github.com/kierenj/helm-template-issue-repro - that this is a bug.  The documentation even cites $.Chart.Name as the example use case where $ as a root global scope is useful.  It just doesn't work

@kierenj dot variables are not accessible through define functions, hence why it won't work. If you want to pass in variables to a function, use the template directive instead as others have demonstrated in this thread.
Looks like this can be closed because the original submitter's question seems to have been answered by several community members chiming in. Thanks everyone!

Just for reference here in case you are landing to this issue, the documented way is working . as long as you are using template as mentioned by @bacongobbler :
  labels:
    app: {{ template "mychart.name" $ }}
    chart: {{ template "mychart.chart" $ }}

@fredleger this is the right answer. Always pass the root scope and work from an absolute path. Avoid relative pathing, as there is some level of cognitive load when debugging passed scopes in large code bases.


[Popover] Fix wrong getContentAnchorEl definition

Update typescript definition.
Closes #12539

While this is indeed correct I would rather change the warning message. This change could theoretically be applied to most optional props which would add way to much noise in my opinion.
You could also pass 0 or false and suppress the warning. The only difference is that the component would not behave as expected and prop-types would issue a warning. Because prop-types considers optional props to match T | null | undefined. However both flow and typescript consider optional types to be T | undefined.

@eps1lon Interesting concern, what do you think of
https://github.com/mui-org/material-ui/blob/96d2c38cfa6f5d8800b8a2632bff4cab56fd9472/packages/material-ui/src/Popover/Popover.d.ts#L22
and
https://github.com/mui-org/material-ui/blob/96d2c38cfa6f5d8800b8a2632bff4cab56fd9472/packages/material-ui/src/Popper/Popper.d.ts#L22
What would you suggest as the best path forward?

@eps1lon I have to admit, I don't follow here you are going with this. What do you think this pull request so we stay consistent with the other occurrences of null in the TypeScript definition? And then, we work on a global better answer? cc @pelotom

@duvet86 It's a great first pull request on Material-UI 👌🏻. Thank you for giving it a shot!

I agree with @eps1lon, I would rather change all the TS definitions to exclude null. It’s common practice in TS to only use undefined for “nully” things, because of its compatibility with optional (?) properties. There’s even a tslint rule to forbid the use of null.

At least, the warning message was updated :).


fix(unplugin): correct unplugin-react plugin due to rspack deprecated buildin option

fix(unplugin): correct unplugin-react plugin due to rspack deprecated buildin option

Types of changes

[ ] New feature
[x] Bug fix
[ ] Documentation change
[ ] Coding style change
[ ] Refactoring
[ ] Performance improvement
[ ] Test cases
[ ] Continuous integration
[ ] Typescript definition change
[ ] Breaking change

Background and context
Fix issue https://github.com/arco-design/arco-plugins/issues/61

Solution
Use builtin:swc-loader loader instead to legacy

How is the change tested?
N/A

Changelog

Changelog(CN)
Changelog(EN)
Related issues

修复 unpack-react 在 rspack 版本更新引起的启动错误
Fix unpack-react startup errors on  rspack
https://github.com/arco-design/arco-plugins/issues/61

Checklist:

[x] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
[ ] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others should be submitted to master branch)

Other information

我看这个已经合入main分支了，@arco-plugins/unplugin-react什么时候可以发新的npm包呢？

我看这个已经合入main分支了，@arco-plugins/unplugin-react什么时候可以发新的npm包呢？

用 2.0.0-beta.0 吧，没问题的话过段时间就发正式版了


[REQ] License and others

Hi there, thanks again for this cool work !
Since we've "doxed" it in our HyMPS project (under the AUDIO category \ Tools section \ Restoring subsection), can you please specify the license for it ?
As you know, expliciting licensing terms is extremely important to let anyone better/faster understand how to reuse/adapt/modify sources (and not only) in other open projects and vice-versa.
The license file omission causes an inconsistent generation of the relative badge too:

(badge-generator URL: https://flat.badgen.net/github/license/catfact/depops/?label=LICENSE)
You can easily set one using the GH's license wizard tool.
We also suggest you to keep in consideration to establish some kind of collaboration both with Python Audio Restoration Suite by @HENDRIX-ZT2 and DEVINYL by @matiaszanolli, that are the most interesting projects on the scene.
Last but not least, let us know how - in your opinion - we could improve our categorizations and links to resources in order to favor collaboration between developers (and therefore evolution) of listed projects.
Thanks in advance.

https://github.com/catfact/depops/blob/main/LICENSE.md

its tempting to just take the thing down (this just represents an hour of quick work to share ideas with a collaborator a few years ago)
but i added a license


Don't clean generated files

Description
make clean no longer removes generated files. In addition, we weren't generating the deepcopy-gen associated with upgrade/migrator/clients/v1/k8s/custom, so I've added a target for that.
There's a new check-gen-files target which checks there are no un-committed changes to the generated files. This is connected to the pre-existing static-checks target.
Addresses: https://github.com/projectcalico/libcalico-go/issues/795.
Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

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

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

closing + re-opening to work around semaphore blocked in "pending" state.

Looks awesome


Fix transforms on Empty object children not maintained by ABC cache load.

Changelog Description
Resolve #2
These changes consolidate the way imported hierarchy is re-parented in Blender upon cache load.
Only top nodes of "Empty" objects without any transforms will be skipped.
Published hierarchy:

Loaded hierarchy (note how only Empty.002 is removed cause unecessary):

Additional info
This is my first MR for the project, please do let me know if any troubles.
Testing notes:

Create scene with meshes
Parent some of the meshes to new empty objects
Apply random transform on both empty and mesh objects
Publish the empty as a pointcacheMain
Load the pointcache
Ensure all of the transforms are preserved

Only top nodes of "Empty" objects without any transforms will be skipped.

Any reason we are doing that? Shouldn't we just load whatever data comes in, whatever the Alembic file hold

Only top nodes of "Empty" objects without any transforms will be skipped.

Any reason we are doing that? Shouldn't we just load whatever data comes in, whatever the Alembic file hold

Good question, it was there initially I assumed that was by design to avoid complex hierarchy in the outliner.
@BigRoy not sure who to ask, do you know who could have final call on this ?

Only top nodes of "Empty" objects without any transforms will be skipped.

Any reason we are doing that? Shouldn't we just load whatever data comes in, whatever the Alembic file hold

Good question, it was there initially I assumed that was by design to avoid complex hierarchy in the outliner. @BigRoy, @moonyuet not sure who to ask, do you know who could have final call on this ?

I dont have really the final call.
Guess what @BigRoy means, we can simply load the alembic data , and add and link to the collection, no need to remove the empty(aka the locator). And it is actually doable by removing some conditions inside the code.

Only top nodes of "Empty" objects without any transforms will be skipped.

Any reason we are doing that? Shouldn't we just load whatever data comes in, whatever the Alembic file hold

Good question, it was there initially I assumed that was by design to avoid complex hierarchy in the outliner. @BigRoy, @moonyuet not sure who to ask, do you know who could have final call on this ?

I dont have really the final call.
Guess what @BigRoy means, we can simply load the alembic data , and add and link to the collection, no need to remove the empty(aka the locator). And it is actually doable by removing some conditions inside the code.

Perfect then, well I've gone ahead and implemented @BigRoy suggestion (keep as it come), even simpler logic.
Let me know if that works for you guys.

hmm weird that the wrong load happens also when using the latest ayon-blender 0.2.2 addon....
when inspecting the loaded pointcache that empty acting as a parent for that cube got reset transforms to XYZ > 0 0 0
Anyone any idea whats up??


Feature: absolute and relative file path validator functions for Unix & Windows #278

Description
since the IsFilePath() function just checked the absolute paths #278, I've added IsUnixFilePath() & IsWinFilePath() functions for checking both absolutes and relative file paths in Unix and Windows.
Example:
isUnixFilePath("relative_file_path") => true
isUnixFilePath("./relative_file_path") => true
isUnixFilePath("../relative_file_path") => true
isWinFilePath("relative_file_path") => true
isWinFilePath("..\relative_file_path") => true
isWinFilePath("..\\relative_file_path") => false
IsUnixFilePath() & IsWinFilePath() functions are using UnixARPath & WinARPath regex in patterns.go
there are TestIsWinFilePath() & TestIsWinFilePath() test functions in validator_test.go for to demonstrate more

Thank you!


${env:MYVAR} not working in serverless.yml

When I run in offline mode (serverless-offline) I'm unable to access the loaded env variables in my serverless.yml.  For example in the config below, the  ${env:STAGE} always rolls over to the default.
# serverless.yml
service: serverless-framework-starter

plugins:
  - serverless-dotenv-plugin
  - serverless-webpack
  - serverless-offline #serverless-offline needs to be last in the list

custom:
  webpack:
    webpackConfig: 'webpack.config.js'
    includeModules: true
    packager: 'npm'
  serverless-offline:
    port: 4000
  dotenv:
    path: "./.env.${opt:NODE_ENV, 'development'}"

provider:
  name: aws
  runtime: nodejs8.10
  stage: ${env:STAGE, 'dev'}
  region: ${env:REGION, 'us-east-1'}
  versionFunctions: false
  iamRoleStatements:
  -  Effect: "Allow"
     Action:
       - "s3:*"
     Resource: "*"

functions:
  test-func:
    handler: src/test-func/handler.default
    name: ${self:provider.stage}-${self:service}-upload
    memorySize: 128
    events:
      - http:
          path: hello
          method: get
          cors: true

The test handler has no trouble accessing SOMEVAL and it uses the proper value if I change the NODE_ENV at runtime.
// handler.js
const hello = (event, context, callback) => {
  const response = {
    statusCode: 200,
    body: JSON.stringify({
      message: `Go Serverless v1.0! Your function executed successfully! ENV: ${process.env.SOMEVAL}`,
      input: event,
    }),
  };

  callback(null, response);

  // Use this code if you don't use the http event with the LAMBDA-PROXY integration
  // callback(null, { message: 'Go Serverless v1.0! Your function executed successfully!', event });
};

export default hello;

It seems like a timing issue.  It seems like the serverless.yml is processed before the serverless-dotenv-plugin is able to load the environment variables into scope.  Any idea how I can prove this or whether this is the right concept?

Oh, yeah, if it helps:
.env.development
STAGE=dev
REGION=us-east-1
SOMEVAL=dev val
HELLO_PATH=hello

.env.production
STAGE=prod
REGION=us-east-1
SOMEVAL=prod val
HELLO_PATH=hello_world

I have the same issue though it does not seem to be related to serverless-offline. I fail to run ´serverless deploy´
bash output
> serverless deploy

 Serverless Warning --------------------------------------

  A valid environment variable to satisfy the declaration 'env:COGNITO_USER_POOL_ARN' could not be found.

 Serverless Warning --------------------------------------

  A valid environment variable to satisfy the declaration 'env:COGNITO_USER_POOL_ARN' could not be found.

Serverless: DOTENV: Loading environment variables:
Serverless: 	 - COGNITO_USER_POOL_ARN
Serverless: 	 - COGNITO_USER_POOL_ID
Serverless: 	 - MONGODB_URI
Serverless: 	 - MONGODB_DATABASE
Serverless: 	 - SENTRY_DSN

config
plugins:
  - serverless-dotenv-plugin
  - serverless-webpack
  - serverless-offline

custom:
  webpack:
    webpackConfig: ./webpack.config.js
    includeModules: true
  dotenv:
    path: .env-${self:provider.stage}

provider:
  name: aws
  runtime: nodejs8.10
  stage: ${opt:stage, 'dev'}
  region: us-east-1
  iamRoleStatements:
    - Action:
        - cognito-idp:AdminGetUser
      Resource: ${env:COGNITO_USER_POOL_ARN}
      Effect: Allow

Have the same issue, and it's pretty annoying =(

It took me a while to figure out why I couldn't load env vars before the provider config, but then it dawned on me that there's no purpose to using hooks in the first place. Just load the env vars in the plugin constructor. Avoid hooks altogether!
A fix is coming soon.

I published a new version. Go ahead and give it another try. Thanks for your help!

@colynb
Still no luck with version 1.2.0, seems that the env file is not found when pointing out the path to the env file dynamically like this:
custom:
  dotenv:
    path: .env-${self:provider.stage}

also tried
custom:
  dotenv:
    path: .env-${opt:stage, 'dev'}

it works when setting it statically:
custom:
  dotenv:
    path: .env-dev

OK. I guess I misunderstood your specific problem. I did resolve a bigger
issue that's similar but I'll take a look at this further.
On Mon, Aug 6, 2018 at 1:56 PM Anders Steiner<EMAIL_ADDRESS>wrote:

@colynb https://github.com/colynb
Still no luck with version 1.2.0, seems that the env file is not found
when pointing out the path to the env file dynamically like this:
custom:
dotenv:
path: .env-${self:provider.stage}
also tried
custom:
dotenv:
path: .env-${opt:stage, 'dev'}
it works when setting it statically:
custom:
dotenv:
path: .env-dev
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/infrontlabs/serverless-dotenv-plugin/issues/10#issuecomment-410850354,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABACJBHa_HYeD5H4e2C7JFZa42AalfPtks5uOK2IgaJpZM4TuVwS
.

The problem that I mentioned is introduced in the 1.2.0 release. It worked in 1.1.3. Maybe I should have created a new issue.

@colynb That update fixed my issue! Thanks a lot.


[Bug] H2LogQueryDAO and LogQuery don't support fuzzy query of AbstractLogRecord.CONTENT

Search before asking

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

Apache SkyWalking Component
OAP server (apache/skywalking)
What happened
Both of H2LogQueryDAO (H2 storage plugin) and LogQuery (InfluxDB storage plugin) don't use the parameter--keywordsOfContent and excludingKeywordsOfContent. They don't support fuzzy query of AbstractLogRecord.CONTENT. Related PR #6120
What you expected to happen
We should make H2LogQueryDAO and LogQuery support fuzzy query of AbstractLogRecord.CONTENT like LogQueryEsDAO in ES storage plugin.
How to reproduce
As mentioned above.
Anything else
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

We don't support fuzzy search on the 2 storages because they are not good at indexing and searching, or is poor performant, or is not recommended in production environment, I don't know how you will implement this?

This is not a bug, it is designed likr this. Check the APIs, they response to UI whether this storage supports content fuzzy query.

Got it. Thanks for your explanation.


added ID example to the documentation

see if you like it! just wanted to highlight a couple of more usecases

Thank you!


Task/classification labels mapping

Allowing the user to pass a "id2label" map to classification_labels. For instance:
classification_labels = {0: "Default", 1: "Not default"}

which will display "Default" and "Not default" in the UI for the credit scoring dataset defined like this:
    _classification_labels = {"Default": 0, "Not default": 1}
    gsk_dataset.df[gsk_dataset.target] = gsk_dataset.df[gsk_dataset.target].apply(lambda x: _classification_labels[x])

This still needs to be properly propagated to the backend

@rabah-khalek what's the use-case for this feature? When a user messes up an order of classification_labels?

It’ll help this a bit, but no it’s suppose to be a solution for the label being not “human readable” issue. This dict will do the mapping internally without the need for the user to change his df. Its Done in python, but still needed one of you in order to propagate it through the other parts of the code. Do you think it’s a lot of work?On 24 May 2023, at 17:54, Andrey Avtomonov @.***> wrote:
@rabah-khalek what's the use-case for this feature? When a user messes up an order of classification_labels?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@rabah-khalek
Actually, I don’t think I understand the use case for this PR. While previously we were creating predicted_labels by using a list and taking elements from it by their positions, now we use a dictionary and take elements by key which is still a position of the column in the prediction matrix.
There was indeed a problem when people used classification_labels different to what they actually stored in the target column or used an incorrect order (which this PR doesn't solve). You'd still have to change classification_labels, but instead of changing the order of elements in the list you have to change dictionary keys.
There was a feature request (from Max) that was about supporting a mapping between a "technical" prediction and a human-readable explanation. For example in case you have a target columns containing classes "A", "B" and "C" you need your model.predict(...).predicted_labels to still return a list of values from {A, B, C} in order to calculate metrics, but to show this in the UI you'd use human-readable representation of each code using a user-provided mapping:
{"A": "Iris Setosa",  "B": "Iris virginica", "C": "Iris versicolor"}

This branch doesn't have the goal to solve the "order" of classification_labels issue.
It supposed to solve what Max is talking about. But I also added on the python side, the action that, if you provide a dict, I suppose that you want to do a mapping between your model output (via the classification_labels dict) and your target variable.
If you think we should not allow the user to do a mapping between his model and target variable (the issue we faced in this notebook) -- which is what HF does with id2label, then it becomes purely a UI feature, and they keys of the dict must match the target variable of the df.

@rabah-khalek I had just a quick look but I see an issue with the internal usage of raw_prediction.argmax(axis=1) to determine the label index which does not seem to be addressed in the code. We expect labels to be in order 0, 1, 2, etc. but with dict support this would break.

but with dict support this would break
IIRC dicts guarantee order or element in recent Python, so it shouldn't be an issue in principle.

However this PR only adds a support of Dict[int, str] as a new classification_labels type. So the case when your model returns a not-so-human-readable prediction, but not necessarily a number from 0 to N you can't map it to a human-readable label that you'd show in the UI. This was the case of Max, he was using encoded targets, so you could roughly understand what the target means but it was far from being readable.
And yes, I think this is more of a UI feature

yes, the argmax shouldn't be a problem, but that means that the dict need to also be ordered correctly.
The PR as it stands, not only supports dict type for classification_labels + allows a mapping between the model output and the dataset.target.
Take the credit scoring example, and say the dataset.target had [0, 1] instead of ['Default', 'Not default'], passing this dict classification_labels={0: 'Default', 1: 'Not default'} will make PredictionResults cast to the dict values, resulting in the same output we get usually from the default credit scoring example, this can be summarised by this unit-test: https://github.com/Giskard-AI/giskard/blob/021ad16d749a23595939493a6385ee32000dbc3a/python-client/tests/test_classification_labels.py#L41-L57
So in principle, this will propagate the classification_labels mapping to the UI for predictions, but not the dataset.target which is what i meant here: https://github.com/Giskard-AI/giskard/pull/1009#issuecomment-1545862439.
My end goal, was to make the dict classification_labels cast both model predictions and dataset.target from the key to the values provided in the dict.
With or without this casting, there's some work to do on the UI, if you think it's not that crucial before the launch, I'll put this PR on hold. We can discuss it further after the launch.


Inconsistent integer type for document version

Some fields use int64, some int. For example BulkResponseItem uses int, whereas GetResult uses int64. This is minor, but annoying.

@atombender Yes. I tried to fix it in the release 2 to 3, but unfortunately I missed some fields. We get another chance at the 3 to 5 migration. I don't want to introduce breaking changes in minor releases.

Great, thanks!

Missed it in the 5.0 release. Sorry.

I checked a few and it looks like they match the Java type in Elasticsearch (some are long, some are int in the Java source). Sometimes it's even worse, e.g. TTL in the response always seems to be long whereas in some APIs you can specify it as a long or a string (as in "1d").
Anyway, I feel more confident in using the corresponding Go types in Elastic although I agree it's annoying.

Forgot to say that I'll change Version in BulkResponseItem to int64.


bug: avatar & avatar Group

[ ] Highlight the part

As like reference doc

from #67

[ ] 1. fix this

Highlight

Ref

no work done from my side on this issue


Support multiple listeners on an element

Right now you couldn't do something like
specialButton
  = onClick "clicked"
  $ onHover "hovered"
  $ button [ text "I'm a button ]

This should be supported and I think will result in better handling of events anyways

Done with #103


Bugfix/yury/aogcm notilehist regrid_exch: tile_hist.data was removed from history template

... for tripolar collections in previous PR and this PR removes linking tile_hist.data in gcm_run.j script, since it is not necessary anymore. Interpolation of tripolar output to latlon grid is done with grid_label option. Perhaps, regrid_exch option should be removed from MAPL too, but I am not sure about this.

I'm going to invoke @bena-nasa to see if maybe regrid_exch is just dead code in MAPL now. Always good to remove unneeded code!


Error in AnimationPlayer 3D mappings

Godot version
3.5 rc7
System information
Windows 11 Pro, GLES3 and Vulkan(for Godot 4.0)
Issue description
AnimationPlayer has some bugs in the 3D space, namely, some functions are not displayed. In the video I demonstrated this error:
https://user-images.githubusercontent.com/91805483/181018652-0c18e482-fcc8-49b7-a42e-3563993299a4.mp4
Steps to reproduce
Adding keys to the AnimationPlayer track
Minimal reproduction project
No response

@InkRobert Please upload a minimal reproduction project to make this easier to troubleshoot.
Also, can you reproduce this on 3.4.4?


[BUGFIX] Write plugin changes to database only if it is a string

I found this by trying to install the latest update of the "FutiFAQManager" plugin which raised an error:
bin/console sw:plugin:update FutiFAQManager
PHP Catchable fatal error:  Object of class Enlight_Config could not be converted to string engine/Library/Zend/Db/Statement/Pdo.php on line 228
After digging in the code I found out that the Plugin Namespace Component tries to write an Enlight_Config object to the database.
This PR checks that the given info is a string. Even though I think writing the changes to the database isn't needed anymore. Looking into our production database there are only 2 entries both with the value "Object"...

HI @FiveDigital, thanks for your PR.
Please rebase your PR. We'll then verify it again.

Rebasing done @janbuecker

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


Update use command to use config if no version is provided

Update fvm use to use the Flutter version defined in the config file if the version is not provided as an argument.

I didn't see any existing tests for the install command on this similar feature, and I'm not sure how to add one for this. But happy to give it a go if you can share how to write tests for this.

Close #397

@zeshuaro thanks for the PR. Would love to get some help improving a bit the tests on FVM... If it's something you can help out feel free to open a PR or open an issue about specific sections you would like to focus on.

@all-contributors please add @zeshuaro for code


Pre-selected Data

I've been using and enjoying react-grid-table. Thank you!
Question: When rows are generated, I would like some rows to be pre-checked depending on the contents of the row data. Is this possible?
For example: Suppose I want to produce a table containing a list of cars that I own. Columns would be something like "Owned (checkbox)", "Brand", "Model", "Color", "Year", etc.
My row data has a key-value called "owned." If it's 'owned' is true, the row's "Owned" column checkbox is checked. If it's false, then it is not checked.
Does this make sense? Is this possible?
Thank you!
-B

Hi...
This can be done by initially passing the selected rows ids using the selectedRowsIds prop, whatever logic you apply to get the ids doesn't matter.
Demo:
https://codesandbox.io/s/rgt-initial-row-selection-7kc6f?file=/src/App.js
In my example, I'm initially selecting all the users that have gender: 'Male in the row data (initialSelectedRows ).


BUG ModelPipeline.from_existing handle future training templates

If users called ModelPipeline.from_existing on a model training job which used a version of CivisML newer than what the client is aware of, we got errors because the prediction template ID was set to None. Let's warn and default to the newest known prediction template. At the very least, this should generate much clearer errors when the prediction job does a version check.

@jmemich , I needed to address a merge conflict in the changelog. Re-approve?


Uncaught exception occurred while initializing app on iOS.

RN 0.38.1/react-native-fcm 2.5.2
Xcode 8.2/iOS simulator 10.2 and iOS device 10.2
I met  an uncaught exception while initializing app on iOS.
Xcode screenshot:

Console log:
2016-12-15 22:33:35.484: <FIRMessaging/INFO> FIRMessaging library version 1.2.0
2016-12-15 22:33:35.484 MyAppXXXXXX[7135:90164] *** Assertion failure in -[GIPReachability startWithCompletionHandler:](), googlemac/iPhone/Shared/Net/GIPReachability.m:120
2016-12-15 22:33:35.515 MyAppXXXXXX[7135:90164] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'GIPReachability should be used from the main thread'
*** First throw call stack:
(
	0   CoreFoundation                      0x0000000107d24d4b __exceptionPreprocess + 171
	1   libobjc.A.dylib                     0x000000010866121e objc_exception_throw + 48
	2   CoreFoundation                      0x0000000107d28e42 +[NSException raise:format:arguments:] + 98
	3   Foundation                          0x000000010822c599 -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 166
	4   MyAppXXXXXX                         0x000000010726bc2e -[GIPReachability startWithCompletionHandler:] + 172
	5   MyAppXXXXXX                         0x000000010724f06c -[FIRMessaging startWithConfig:] + 270
	6   MyAppXXXXXX                         0x000000010724ed04 __25+[FIRMessaging messaging]_block_invoke + 124
	7   libdispatch.dylib                   0x000000010c2480cd _dispatch_client_callout + 8
	8   libdispatch.dylib                   0x000000010c22d1f8 dispatch_once_f + 501
	9   MyAppXXXXXX                         0x000000010724ec85 +[FIRMessaging messaging] + 45
	10  MyAppXXXXXX                         0x0000000107465634 -[RNFIRMessaging setBridge:] + 676

Because the log said 'GIPReachability should be used from the main thread', I added code like this:
  dispatch_async(dispatch_get_main_queue(), ^{
    [[FIRMessaging messaging] setRemoteMessageDelegate:self];
  });

This works for me.
Can you fix it? or can I create a PR?

@miyabi I created a PR for you ;) Thanks for suggesting this workaround.

@cooperka Thanks!

fixed in master


Implement KeyGenerator

PR adds core/format/KeyGenerator. Usage:
const u64 = KeyGenerator.fromString('key_name') // returns UInt64

Pull Request Test Coverage Report for Build 727

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 720:
0.0%

Covered Lines:
10

Relevant Lines:
10

💛  - Coveralls

Pull Request Test Coverage Report for Build 727

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 720:
0.0%

Covered Lines:
10

Relevant Lines:
10

💛  - Coveralls


add modularity to kubernetes functions

Modifications
All of the Kubernetes-related functions were in the same file, which was getting long. I wanted to create some separation to put into separate files:

generic code related to using the dynamic client to get/update/create resources
generic utilities for interacting with unstructured objects
generic utilities for interacting with common Kubernetes types (structured)

Also, I don't think we should put code related to specific Rollout types in this directory - rather those can be collocated with the Rollout itself.

Codecov Report
Attention: Patch coverage is 61.81818% with 42 lines in your changes missing coverage. Please review.

Project coverage is 51.85%. Comparing base (d830c00) to head (a49dcf7).

Files
Patch %
Lines

internal/util/kubernetes/structured_util.go
21.42%
19 Missing and 3 partials :warning:

...controller/numaflowcontrollerrollout_controller.go
78.94%
4 Missing and 4 partials :warning:

internal/util/kubernetes/dynamic_client.go
0.00%
7 Missing :warning:

internal/util/kubernetes/unstructured_util.go
80.00%
3 Missing and 2 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #101      +/-   ##
==========================================
+ Coverage   49.81%   51.85%   +2.04%
==========================================
  Files          12       15       +3
  Lines        1371     1371
==========================================
+ Hits          683      711      +28
+ Misses        582      550      -32
- Partials      106      110       +4

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


resolving files ending in rc

Config files that end with rc are not resolved. Should they be? If so - needs to be implemented

for now they won't be resolved


[FLINK-17757] Implement format factory for Avro serialization and deseriazation schema of RowData type

…eriazation schema of RowData type
Add new factory for Avro RowData format.
Verifying this change
Added UTs.
Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? not documented

@flinkbot run azure

Passed in my branch: https://dev.azure.com/imjark/Flink/_build/results?buildId=90&view=results


Filter Chain Match Trie logic leads to unexpected matches leading to various bugs

Bug description
We find that Istio seems to cause outbound HTTPS traffic issues in some of our Kubernetes clusters.  For eg:- We have an application that makes HTTPS calls to the NewRelic and AWS API. The behaviour is inconsistent in that the outbound HTTPS call works in some of our Kubernetes clusters. We are trying to understand what the root cause is.
In an effort to find the root cause, we are trying to compare the istio proxy configs from Kubernetes clusters that have and don't have this issue. Since the istio-proxy config dumps are huge JSONs. we request help to narrow down on the relevant JSON fields/structs for configuring outbound HTTPS requests.
 time="2020-07-30T23:11:49Z" level=error msg="RequestError: send request failed\ncaused by: Get \"https://route53.amazonaws.com/2013-04-01/hostedzone\": http: server gave HTTP response to HTTPS client"

[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[X] User Experience
[ ] Developer Infrastructure
Expected behavior
Steps to reproduce the bug
Just inject istio-proxy to these pods that make outbound HTTPS calls
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
v1.6.3
How was Istio installed?
Helm
Environment where bug was observed (cloud vendor, OS, etc)
AWS

It would be helpful to understand what in envoy is causing the HTTPS outbound request to be intercepted and forwarded as an HTTP call to the server.
I've done a fair bit of reading on this. From my understanding, we have ALLOW_ANY as the mode and it creates 'PassthroughClusters' which is supposed to forward the outgoing HTTPS requests directly. I have verified that the envoy proxy config has PassthroughClusters configured but it still fails.

I have enabled trace logs and access Logs. Strangely, an access log is never created for the outbound https call to collector.newrelic.com
2020-08-06T04:19:34.972583Z	debug	envoy filter	[external/envoy/source/extensions/filters/listener/original_dst/original_dst.cc:18] original_dst: New connection accepted
2020-08-06T04:19:34.972671Z	debug	envoy filter	[external/envoy/source/extensions/filters/listener/tls_inspector/tls_inspector.cc:78] tls inspector: new connection accepted
2020-08-06T04:19:34.972682Z	trace	envoy filter	[external/envoy/source/extensions/filters/listener/tls_inspector/tls_inspector.cc:171] tls inspector: recv: -1
2020-08-06T04:19:34.972740Z	trace	envoy filter	[external/envoy/source/extensions/filters/listener/tls_inspector/tls_inspector.cc:171] tls inspector: recv: 292
2020-08-06T04:19:34.972771Z	debug	envoy filter	[external/envoy/source/extensions/filters/listener/tls_inspector/tls_inspector.cc:148] tls:onServerName(), requestedServerName: collector.newrelic.com
2020-08-06T04:19:34.972782Z	trace	envoy filter	[external/envoy/source/extensions/filters/listener/tls_inspector/tls_inspector.cc:192] tls inspector: done: true
2020-08-06T04:19:34.972788Z	debug	envoy filter	[external/envoy/source/extensions/filters/listener/http_inspector/http_inspector.cc:37] http inspector: new connection accepted
2020-08-06T04:19:34.972795Z	trace	envoy filter	[external/envoy/source/extensions/filters/listener/http_inspector/http_inspector.cc:45] http inspector: cannot inspect http protocol with transport socket tls
2020-08-06T04:19:34.972842Z	debug	envoy conn_handler	[external/envoy/source/server/connection_handler_impl.cc:411] [C14] new connection
2020-08-06T04:19:34.972852Z	trace	envoy main	[external/envoy/source/common/event/dispatcher_impl.cc:163] item added to deferred deletion list (size=1)
2020-08-06T04:19:34.972855Z	trace	envoy main	[external/envoy/source/common/event/dispatcher_impl.cc:79] clearing deferred deletion list (size=1)
2020-08-06T04:19:34.972862Z	trace	envoy connection	[external/envoy/source/common/network/connection_impl.cc:493] [C14] socket event: 3
2020-08-06T04:19:34.972865Z	trace	envoy connection	[external/envoy/source/common/network/connection_impl.cc:581] [C14] write ready
2020-08-06T04:19:34.972870Z	trace	envoy connection	[external/envoy/source/common/network/connection_impl.cc:531] [C14] read ready
2020-08-06T04:19:34.972878Z	trace	envoy connection	[external/envoy/source/common/network/raw_buffer_socket.cc:25] [C14] read returns: 292
2020-08-06T04:19:34.972890Z	trace	envoy connection	[external/envoy/source/common/network/raw_buffer_socket.cc:39] [C14] read error: Resource temporarily unavailable
2020-08-06T04:19:34.972913Z	trace	envoy http	[external/envoy/source/common/http/http1/codec_impl.cc:486] [C14] parsing 292 bytes
2020-08-06T04:19:34.972925Z	trace	envoy connection	[external/envoy/source/common/network/connection_impl.cc:429] [C14] writing 66 bytes, end_stream false
2020-08-06T04:19:34.972954Z	debug	envoy http	[external/envoy/source/common/http/conn_manager_impl.cc:284] [C14] dispatch error: http/1.1 protocol error: HPE_INVALID_METHOD
2020-08-06T04:19:34.972961Z	debug	envoy connection	[external/envoy/source/common/network/connection_impl.cc:109] [C14] closing data_to_write=66 type=2
2020-08-06T04:19:34.972965Z	debug	envoy connection	[external/envoy/source/common/network/connection_impl_base.cc:30] [C14] setting delayed close timer with timeout 1000 ms

cc @GregHanson

please provide config dump of the <IP_ADDRESS>:443 listener on the failing cluster

@rshriram Here it is
 {
     "name": "<IP_ADDRESS>_443",
     "active_state": {
      "version_info": "2020-08-05T19:53:52Z/2",
      "listener": {
       "@type": "type.googleapis.com/envoy.api.v2.Listener",
       "name": "<IP_ADDRESS>_443",
       "address": {
        "socket_address": {
         "address": "<IP_ADDRESS>",
         "port_value": 443
        }
       },
       "filter_chains": [
        {
         "filter_chain_match": {
          "application_protocols": [
           "http/1.0",
           "http/1.1",
           "h2c"
          ]
         },
         "filters": [
          {
           "name": "envoy.http_connection_manager",
           "typed_config": {
            "@type": "type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager",
            "stat_prefix": "outbound_<IP_ADDRESS>_443",
            "rds": {
             "config_source": {
              "ads": {}
             },
             "route_config_name": "443"
            },
            "http_filters": [
             {
              "name": "istio.metadata_exchange",
              "typed_config": {
               "@type": "type.googleapis.com/udpa.type.v1.TypedStruct",
               "type_url": "type.googleapis.com/envoy.extensions.filters.http.wasm.v3.Wasm",
               "value": {
                "config": {
                 "vm_config": {
                  "runtime": "envoy.wasm.runtime.null",
                  "code": {
                   "local": {
                    "inline_string": "envoy.wasm.metadata_exchange"
                   }
                  }
                 },
                 "configuration": "{}\n"
                }
               }
              }
             },
             {
              "name": "istio.alpn",
              "typed_config": {
               "@type": "type.googleapis.com/istio.envoy.config.filter.http.alpn.v2alpha1.FilterConfig",
               "alpn_override": [
                {
                 "alpn_override": [
                  "istio-http/1.0",
                  "istio"
                 ]
                },
                {
                 "upstream_protocol": "HTTP11",
                 "alpn_override": [
                  "istio-http/1.1",
                  "istio"
                 ]
                },
                {
                 "upstream_protocol": "HTTP2",
                 "alpn_override": [
                  "istio-h2",
                  "istio"
                 ]
                }
               ]
              }
             },
             {
              "name": "envoy.cors",
              "typed_config": {
               "@type": "type.googleapis.com/envoy.config.filter.http.cors.v2.Cors"
              }
             },
             {
              "name": "envoy.fault",
              "typed_config": {
               "@type": "type.googleapis.com/envoy.config.filter.http.fault.v2.HTTPFault"
              }
             },
             {
              "name": "istio.stats",
              "typed_config": {
               "@type": "type.googleapis.com/udpa.type.v1.TypedStruct",
               "type_url": "type.googleapis.com/envoy.extensions.filters.http.wasm.v3.Wasm",
               "value": {
                "config": {
                 "root_id": "stats_outbound",
                 "vm_config": {
                  "vm_id": "stats_outbound",
                  "runtime": "envoy.wasm.runtime.null",
                  "code": {
                   "local": {
                    "inline_string": "envoy.wasm.stats"
                   }
                  }
                 },
                 "configuration": "{\n  \"debug\": \"false\",\n  \"stat_prefix\": \"istio\"\n}\n"
                }
               }
              }
             },
             {
              "name": "envoy.router",
              "typed_config": {
               "@type": "type.googleapis.com/envoy.config.filter.http.router.v2.Router"
              }
             }
            ],
            "tracing": {
             "client_sampling": {
              "value": 100
             },
             "random_sampling": {
              "value": 1
             },
             "overall_sampling": {
              "value": 100
             }
            },
            "access_log": [
             {
              "name": "envoy.file_access_log",
              "typed_config": {
               "@type": "type.googleapis.com/envoy.config.accesslog.v2.FileAccessLog",
               "path": "/dev/stdout",
               "format": "[%START_TIME%] \"%REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%\" %RESPONSE_CODE% %RESPONSE_FLAGS% \"%DYNAMIC_METADATA(istio.mixer:status)%\" \"%UPSTREAM_TRANSPORT_FAILURE_REASON%\" %BYTES_RECEIVED% %BYTES_SENT% %DURATION% %RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)% \"%REQ(X-FORWARDED-FOR)%\" \"%REQ(USER-AGENT)%\" \"%REQ(X-REQUEST-ID)%\" \"%REQ(:AUTHORITY)%\" \"%UPSTREAM_HOST%\" %UPSTREAM_CLUSTER% %UPSTREAM_LOCAL_ADDRESS% %DOWNSTREAM_LOCAL_ADDRESS% %DOWNSTREAM_REMOTE_ADDRESS% %REQUESTED_SERVER_NAME% %ROUTE_NAME%\n"
              }
             }
            ],
            "use_remote_address": false,
            "generate_request_id": true,
            "upgrade_configs": [
             {
              "upgrade_type": "websocket"
             }
            ],
            "stream_idle_timeout": "0s",
            "normalize_path": true
           }
          }
         ]
        }

need complete dump of that listener with all filter chains and listener filters

I've corrected this. Thanks

@rshriram What's happening here is
a. Client initiates a HTTPS request, which Envoy cannot terminate its TLS
b. The first filter chain  "application_protocols": ["http/1.0",  "http/1.1", "h2c"] matches because TLS inspector fills application_protocols with ALPN (which include http/1.1)
c. The filter chain respond HTTP with response (because it has HCM)
while in case of a. the connection should go to PassthroughFilterChain. The filter chain match for plaintext http should specific about plaintext.

The first filter chain "application_protocols": ["http/1.0", "http/1.1", "h2c"] matches because TLS inspector fills application_protocols with ALPN (which include http/1.1)

This is news!!! Thanks lizan. How do we make it be specific about plaintext?

https://github.com/envoyproxy/envoy/blob/6a71f16c664f2e3a874d2a991262d49e6ed485c8/api/envoy/api/v2/listener/listener_components.proto#L134 use raw_buffer in transport_protocol

Per @lizan ,
to match only on plaintext http,
application_protocols: http/1.0, http/1.1, h2c
transport_protocols: raw_buffer

to match on non-TLS traffic,
transport_protocols: raw_buffer

So we have to fix our passthrough listener generation logic to use the raw buffer transport protocols. I wonder if we need to update other aspects of the sniffing logic to not assume that empty transport protocol + only application protocols mean no tls.

I changed the port name of another service from http to https and that took out the <IP_ADDRESS>:443 listener completely from the istio-proxy config

@rshriram Could you point out where the logic for port.Name is being used here? Trying to understand how the port Naming affects listener creation

port.Name very early on becomes server.Protocol which is handled
differently in listener.go
On Thu, Aug 6, 2020, 6:09 PM Tariq Ibrahim<EMAIL_ADDRESS>wrote:

@rshriram https://github.com/rshriram Could you point out where the
logic for port.Name is being used here? Trying to understand how the port
Naming affects listener creation
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/26079#issuecomment-670266104, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXO5DMBQVO5KLTKXXBDR7NH6JANCNFSM4PTT5WAQ
.

I just want to add that this is rather concerning. The customer workload which had this bad port naming was not even meant to be a part of the service mesh (no istio-injection enabled in its namespace) and yet it broke the entire mesh. This speaks to the fragility of the Istio service mesh network. We can't afford to have such a mishap in production especially given its likely due to envoy's hot reloads.
I see two problems here
i) Why should just ONE service workload that's not istio-meshed bring down the service network?
ii) port.Name is intended to be largely informational and not of much consequence Kubernetes-wise. Why is Istio's proxy configuration so reliant on this field port.Name.

@tariq1890 we need a way to identify the protocol for a service. Until Kubernetes 1.18 (see appProtocol in https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/#manual-protocol-selection) we had no way of doing this other than either relying on port name, or relying on a special annotation on the Service. For better or worse, we chose to use port name rather than annotation.

i) Why should just ONE service workload that's not istio-meshed compromise the entire service network?

It shouldn't, its a bug.

its likely due to envoy's hot reloads.

Not sure what you mean by this - we never do hot reload anymore

Thanks for your response. I can see why you chose the port name approach. But sadly, in our not-ideal world, there will always be some sort of typos or hacks and misconfigurations by K8s users.
At the very least, we should have an istioctl analyze warning/error. But I am not sure if non-meshed components fall under the scope of istioctl analyze.

It shouldn't, its a bug.

Sure happy to help and contribute a fix in any way I can

Not sure what you mean by this - we never do hot reload anymore

Oh, I thought hot reloads were an instrinsic feature of envoy. If istio-proxy overrides that, please disregard :)

Opened envoy bug: https://github.com/envoyproxy/envoy/issues/12572

Found another bug on inbound match
See a declared port:
{"destinationPort":9090,"applicationProtocols":["istio","istio-http/1.0","istio-http/1.1","istio-h2"]}
{"destinationPort":9090}

vs undeclared:
{"prefixRanges":[{"addressPrefix":"<IP_ADDRESS>","prefixLen":0}],"transportProtocol":"tls","applicationProtocols":["istio-peer-exchange","istio"]}
{"prefixRanges":[{"addressPrefix":"<IP_ADDRESS>","prefixLen":0}],"transportProtocol":"tls","applicationProtocols":["http/1.0","http/1.1","h2c","istio-http/1.0","istio-http/1.1","istio-h2"]}

Two issues here:

A TLS request with no alpn set (or not matching any listed above) will not match any filter chain
A TLS request with ALPN set to http (not istio mTLS!) will match the istio mtls filter chain, and fail

(1) is just broken because we didn't realize how FCM works I guess. (2) is there for backwards compatibility with 1.3- Istio versions that do not set istio-* ALPN
cc @gargnupur if you are interested in this rabbit hole...

I think there are 2 in the undeclared one above for tcp and http traffic separately...

@gargnupur see https://github.com/envoyproxy/envoy/issues/12572 for details. tl;dr we all misunderstood how FCM works, if you send TLS traffic it will never match those other 2

As I understand, this bug is not fixed yet, right? Could we then remove the lifecycle/stale label?

Also, is there a known workaround (other than not using ALPN)?

@howardjohn : If you disable TCP telemetry, that should help too?

@yann-soubeyrand the original issue of http port blocking https IS fixed - in 1.8+. As a workaround you should not have an http port on 443 (probably shouldn't do this anyways), or you can not set ALPN I suppose.
The longer term issue that the FCM logic is super confusing and may lead to potential bugs, which is why this is still open

any workaround for this. not working after renaming port as well

after having http port on 443, still all the external traffic was blocked.

We saw an issue upgrading from 1.7.3 to 1.8.2 where 1.7.3 proxies configured by a 1.8.2 control plane could not access a TCP service with an unrecognizable port name (eg, foo). The proxy access logs report filter_chain_not_found:
[2021-02-12T18:24:58.184Z] "- - -" 0 "filter_chain_not_found" NR "-" "-" 0 0 0 - "-" "-" "-" "-" "-" - - <IP_ADDRESS>:9000 <IP_ADDRESS>:48670 - -

The 1.7.3 proxy filterchain matches look like the example in the envoy bug above
{
  "transportProtocol": "raw_buffer",
  "applicationProtocols": [
    "http/1.0",
    "http/1.1",
    "h2c"
  ]
}
null

Whereas 1.8.2 adds a default_filter_chain for the tcp proxy configuration instead of a null match for a catch all.
The connection works fine when the control plane and proxy are both 1.7.3 or 1.8.2.
Could this failed connection be a symptom of the bugs described in this issue? If so, is there a better workaround than requiring tenants to correctly name their TCP ports before the upgrade?


Develop

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

Project coverage is 100.00%. Comparing base (986b439) to head (3eff217).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #23   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          116       116
  Branches        10        10
=========================================
  Hits           116       116

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


Notifications Sounds

Running 5.006 on a rooted Nexus 6P with Android 6, build MDB08K.
When email comes in there are no notifications sounds. Is this a setting that I cannot find or is it a bug.
Thanks...Great App, P Prog

You can set the notification sound in settings -> account settings -> notification -> notification sound.
I don't remember what the default was, but I think the default notification sound for messages is used as default.

Thanks, that worked! That setting must have not come over in the imported settings from the other phone.


add major/minor/makedev on apple OSes

This impl corresponds to the macros in sys/types.h:
#define major(x)        ((int32_t)(((u_int32_t)(x) >> 24) & 0xff))
#define minor(x)        ((int32_t)((x) & 0xffffff))
#define makedev(x, y)    ((dev_t)(((x) << 24) | (y)))

r? @Amanieu
(rust-highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 11a1ffe2246cdcb029a1d7f6f1e96a869ef9e336 has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 11a1ffe2246cdcb029a1d7f6f1e96a869ef9e336 with merge 198beb0d45ef9ae2be1f4a6d35446a2822c13d76...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14
Approved by: JohnTitor
Pushing 198beb0d45ef9ae2be1f4a6d35446a2822c13d76 to master...


Prereqs code dupl

@rpelisse I tested the offline installation of the Kafka Connect cluster successfully in the PR #48.
As this PR includes some changes from the PR #48 (with an extension in the PR #50), IMHO it is better to review, and close these ones, before continuing reviewing this.
What do you think?


Seg fault running octo-tiger with latest HPX commit

When running Octotiger with the current master, 4007f0619c33ecd2c1ffa5282d1444ab1bd3bb3e, I get the following error: https://gist.github.com/dmarce1/ea432fb28773e590950e90b136ce1e78
And the following stack trace: https://gist.github.com/dmarce1/6feca10a46d4cdd6602133a98ad4364a

@dmarce1 I'm not able to reproduce this. Could you please be more specific on how you built HPX and OctoTiger, and how you ran the application?

For both HPX and Octotiger I am using GNU C++ 5.4.0
I built HPX using:
cmake    -DCMAKE_BUILD_TYPE=release
-DHPX_WITH_PARCELPORT_MPI=ON  -DCMAKE_C_COMPILER=gcc -DCMAKE_CXX_COMPILER=g++
-DCMAKE_INSTALL_PREFIX="/usr/local/packages/hpx/"
-DHPX_WITH_MALLOC=custom
-DHPX_WITH_HWLOC=ON
-DHPX_WITH_EXAMPLES=OFF
-DHPX_WITH_TESTS=OFF -DHPX_WITH_DATAPAR_VC=Off -DVc_ROOT=/opt/Vc/
~/code/hpx
I build octotiger using:
cmake -DCMAKE_PREFIX_PATH=/usr/local/packages/hpx/ $1
-DCMAKE_CXX_COMPILER="g++"
-DCMAKE_C_COMPILER="gcc"
-DCMAKE_C_FLAGS="-O2 -g"
-DCMAKE_CXX_FLAGS="-O2 -g"
-DOCTOTIGER_WITH_GRAV_PAR=OFF

I am not getting the seg fault now. Only difference I can think of is I removed the HPX install entirely before building. Must have been a stale binary?


Remove guards from pattern patches

Addresses issue #32

Coverage increased (+0.2%) to 91.5% when pulling d80a459e0303004a547f3e319b4a20d06324c4a6 on Christewart:remove_guards_from_pattern_patches into ecadd61cd9f3085671147ff5d9e2b8069a897bd0 on bitcoin-s:master.

ACK.


Add cargo-deny

This PR adds cargo-deny in the actions workflows and adds the appropriate cargo-deny configuration as well.

bors single on
bors merge

bors retry


Feature: Tagged template literal support

Many JS GraphQL implementation require you to wrap GraphQL queries around a tagged template literal. Mostly so they can do some compiler magic. Such as Apollo can extract al queries in an application into a manifest. That manifest can then be used for several things including that the client doesn't send a whole query, but just an identifier of the query.
Another example is Gatsby. You need to wrap queries so the compiler can recognize them and statically compile the javascript pages with the GraphQL results pre-rendered.
So to facilitate using these libraries in ReasonML we need to emit code that these tools understand.
Unfortunately there is no official template literal escape hatch in Bucklescript. I already created an issue for this as I think this will help a lot for interop. However we can emit template literals with the current versions of Bucklescript, with the bs.raw extension.
There are some downsides to this. Because the contents of bs.raw are a black box, you need to make sure that the identifier you use is imported if they need to be imported (and make sure the identifier is not renamed when there are name collisions). Some tools however it's fine to use a global (unimported) identifier as it's compiled away (Gatsby).
This PR will add template literal support.
For this query:
module SEO = [%graphql
  {|
    query SEO {
      site {
        siteMetadata {
          defaultTitle: title
          titleTemplate
          siteUrl: url
        }
      }
    }
  |};
  {templateLiteral: graphql}
];

Instead of
var ppx_printed_query = "query SEO  {    site  {      siteMetadata  {        defaultTitle: title        titleTemplate        siteUrl: url      }    }  }`);

It will emit:
var ppx_printed_query = (graphql`
  query SEO  {
    site  {
      siteMetadata  {
        defaultTitle: title
        titleTemplate
        siteUrl: url
      }
    }
  }
`);

We can make this functionality even better at the moment that Bucklescript adds some kind of support for tagged template literals. Then we can upgrade this functionality without any breaking changes. But this functionality itself will allow me to add ReasonML bindings1 to Gatsby, so this is already worth it I believe.
(1): I also needed to add a PR to the Gatsby internals to deal with Bucklescript's import * as Gatsby from 'gatsby' syntax which was not supported (https://github.com/gatsbyjs/gatsby/pull/20330).

What about the option, should it be templateLiteral, taggedTemplateLiteral or templateTag. I think template tag is more correct.

Any objections @baransu?

This would be super cool!

This is ready but waiting for my merge and release. Sorry for the delay. I’ll try to do that today/tomorrow.

No problem thank you both :smile:

Would this be merged into the 1.0 beta? I did merge these two and there were some tricky issues merging the two that I resolved locally. Shall I merge this into the 1.0 PR? Cool thing is that then the 1.0 beta would work with Gatsby.

We can merge to 1.0 beta but can also merge  to master and release as 0.x.

This has been merged in 1.0


Bravely Default

Game Name (and version if necessary)
Bravely Default
Hardware Specs (If necessary)
No response
Operating System
Windows
Game State
Goes into menu, it has missing textures, broken fmvs, no audio and crashes with:
[FATAL] FS service requested. Command: 08060142
Screenshots

Additional information
No response

Master no longer crashes with 0x08060142 after ext-save-data is merged, but needs audio.


refs #PMP2-278 Applied the following changes:

Removed all messages waiting to be sent to the HNZ device when connection is lost.
Ensured that no message received addressed to the HNZ device while connection is not established will be buffered.
Improved log messages displayed when an information message is rejected.
Added unit test for this new behavior.

Sonar still report a lot of duplicate line in hnzpath but appart from that, I let Yannick merge if he deemed it ready

Sadly the global coverage is quite low due to this issue that cannot really be solved unless we change the tools we are working with: https://stackoverflow.com/questions/42003783/lcov-gcov-branch-coverage-with-c-producing-branches-all-over-the-place
About duplication it appears to be related to already existing blocks of duplicated code that were slightly modified during this ticket, not sure how we should treat those cases.


Can't import config

Here is my code src/utils/check-url.js:
import config from '../../config';
const {__PROD__} = config.globals;
const {compiler_public_path} = config;

export default function(url) {
  if (__PROD__) {
    return url;
  } else {
    var woUrl = url.replace(/(https?):\/\/[\.[a-zA-Z0-9\/\-]+/);
    return `${compiler_public_path}${woUrl}}`;
  }
}

I just want to strip out website url from a string in development mode.
But when running this code I get the following errors:
WARNING in ./~/yargs/lib/parser.js
Critical dependencies:
359:21-48 the request of a dependency is an expression
 @ ./~/yargs/lib/parser.js 359:21-48

ERROR in ./config/index.js
Module not found: Error: Cannot resolve module 'fs' in E:\pi-website\config
 @ ./config/index.js 11:10-23

ERROR in ./~/yargs/lib/completion.js
Module not found: Error: Cannot resolve module 'fs' in E:\pi-website\node_modules\yargs\lib
 @ ./~/yargs/lib/completion.js 1:9-22

ERROR in ./~/y18n/index.js
Module not found: Error: Cannot resolve module 'fs' in E:\pi-website\node_modules\y18n
 @ ./~/y18n/index.js 1:9-22

ERROR in ./~/os-locale/index.js
Module not found: Error: Cannot resolve module 'child_process' in E:\pi-website\node_modules\os-locale
 @ ./~/os-locale/index.js 2:19-43

This happens because of this exact line: import config from '../../config';. Can't understand why this works well in build/webpack.config.js line 5 import config from '../config'; and doesn't work for me.

The config is not meant to be imported in the app since it relies on dependencies/files that aren't meant to be bundled. I recommend either exposing additional globals as needed (you do not need to import the config to access __PROD__, for example, it's implicitly available on the "global" scope [technically inserted by webpack]) or creating your own custom config inside of src that's intended for the client bundle.
Closing since this is not in fact an issue with the project, but feel free to continue the discussion.

Ok, I see. Just if (__DEV__) works fine. But how can I access the compiler_public_path variable?

Thank you.

Thanks @davezuko and @web2style I just posted the same issue.
But as I see my approach was flawed.
Would be great if this was a FAQ Q&A or something as it appears as if it might be something that a newbie would stumble into. I'll close my other issue.


parseTree() returns undefined on empty string input

I ran into an issue with jsonc.parseTree when my input file was an empty file thus causing the text parameter to be an empty string. My code did something very similar to the following:
const rawFileContents = (await readFile(myFilePath)).toString();
const root = jsonc.parseTree(rawFileContents, parseErrors);

if (root.type === MY_EXPECTED_TYPE) {/* do something. */}
else { /* handle invalid file */ }

This causes an exception at root.type when the file at myFilePath is empty because root is undefined.
Is this WAI or should the function signature below include undefined or the function itself return an empty Node when text is the empty string?
/**
 * Parses the given text and returns a tree representation the JSON content. On invalid input, the parser tries to be as fault tolerant as possible, but still return a result.
 */
export declare function parseTree(text: string, errors?: ParseError[], options?: ParseOptions): Node;

It's a bug in the spec. parseTree can return undefined for empty inputs.


updates to HarpDevice/DaqDevice

[ ] add firmware field that uses Software class as optional in DAQ
[ ] add hardware_version in DAQ
[ ] remove harp_device_version in Harp
[ ] Add harp_device_type_whoAmI in Harp (id of device type)
[ ] add manufacturers: AIND, Second Order Effects, Champalimaud Foundation (ror=03g001n57)
[ ] change data_interface to use USB by default, but not to be constant.
[ ] add boolean field clock_generator

anything I'm missing @bruno-f-cruz @poofjunior

I would change clock_generator to is_clock_generator.
Also maybe add the field to the harp class whoAmI. This is a 4-digit number that fully specifies the device type.
For future reference here's how we are currently defining a device using in harp:
device schema example: https://github.com/harp-tech/device.behavior/blob/main/device.yml

The device, whoAmI, firmwareVersion, hardwareTargets are probably what we want to track in some of the aforementioned fields

For general harp documentation, here's the new website too:
https://harp-tech.org
and protocol
https://harp-tech.org/protocol/BinaryProtocol-8bit.html

@bruno-f-cruz is whoAmI redundant with harp_device_type? Do we really need both if they are redundant?

I would rather have the whoami than the name. Makes it way easier to automate code since whoami are guaranteed to be unique and are reserved for each device. I suspect that users will still want the name. So to kill two birds with one stone, I suggest making it an enumerator of int.

We do need the whoami and needs to be automatically populated. I can validate devices by whoami (immutable) but not my name (users can change the name of the device). All my workflows validate if the board I am connected to is of the type I expect.
Also I just thought of a way to automatically instantiate devices that I want to try and this feature would make things so much easier and water tight!


guide: document config options (-c)

-c is being used as a catch-all and a way to avoid specifying the actual expected options for each command

The reason to use -c instead of --<option name> is because different implementations have different set of options. and adding options dynamically will probably require a lot of our cli framework butchering. we might do it later...
From documentation point of view, we need a dedicated page for each implementation (not only target envs, but other base classes too). It's huge amount of work but it needs to be done at some point
Originally posted by @mike0sv in https://github.com/iterative/mlem/issues/233#issuecomment-1190869678

outdated, since we removed those in 0.3.0


Add repo topics

Hi,
You have a great guide going on here, congrats. May I suggest that for increased findability you add some topic labels to the repo, like 'mastodon', 'fediverse', 'activitypub', 'activitystreams', 'decentralization', etc.?

I didn't know I could do that, and have done so! Thank you!

Great, thx! Fediverse rocks :)
PS. I added a link to your guide in the SocialHub wiki post that is also collecting AP user-targeted info.


Item geometry / proj:geometry extended to support MultiPolygon

In edge cases, the geometry of an object can be a GeoJSON MultiPolygon rather than a Polygon (e.g. aerial/drone imagery mosaic).  It is proposed that the schema for the geometry field in the Item spec, and proj:geometry in the Projection Extension be extended to support the GeoJSON MultiPolygon type to cover these instances.

Item geometry does this -- it's any GeoJSON geometry and links to that spec.
I originally wrote up the Proj Extension, and I don't know now if I wasn't thinking it through or it got changed, but I do think that field should have the same type as Item.geometry.

Discussed on call 2-18-21, everyone agreed it should have the same type as item.geometry

PR #995 addresses the issue.


gperftools and libunwind cause project crash

@alk Hi, I got the crash when use gperftools and libunwind to analyse the memory of java program via "LD_PRELOAD=/.../libtcmalloc.so" .  When I disable libunwind by "./configure --prefix=... --enable-shared=no --enable-frame-pointers --disable-libunwind", and make && make install, but the libtcmalloc.so would not be generated, so LD_PRELOAD cannot be set to /.../libtcmalloc.so, and gperftools cannot work.
Environment: Red Hat 4.8.5-36, x86_64, gperftools 2.7, libunwind 0.99-alpha

You did --enable-shared=no which asked ./configure to only build static library. Thus no .so produced.
Also note that profiling java programs should be done with some other means. gperftools is not for java.


Back to search results

Story: As a user, I would like to navigate back from the detailed-ad-view to the adds search results overview in order to look into other ads founded.
AC1: The button [Back] / [Zurück] is visible on the detailed-ad-view
AC2: When I click [Back], the page with the search results is displayed
AC3: Page contains the same search results as already found
_to be verify  if the Button really needed or navigating back in the browser is sufficient -> team decided to do the [Back] Button

Back button is visible and translated to the correct language


Dynamic Component support?

<svelte:component> like tag to render component dynamically (without Switch)
https://svelte.dev/docs#svelte_component

Hmm.. haven't thought about this one at all really but let's see if we can make this. The way Solid works is that with the general primitives you should be able to make whatever you want.
First Level, all Components are just functions. So if this is a matter of a downstream condition or something that doesn't update dynamical you can just:
let SelectedComponent = state.selected.component
return <SelectedComponent someProp={(state.selected)} />

Or look it up from a lookup table etc. But I'm going to assume that is not the case.
So we want a Switcher Component. Maybe something like this:
<Switcher component={( state.selected.component )} someProp={(state.selected)} />

So I think we could write that like:
function Switcher(props) {
  return createMemo(() => {
    const SelectedComponent = props.component;
    return SelectedComponent && SelectedComponent(props);
  })
}

This is just a first draft but take a look at an example here. What I did actually was check the prop propagation by passing the swap button as props.  https://codesandbox.io/s/solid-switcher-qhmsn
Does this make sense?

I'm trying to make it simpler by utilize state but it seems not working, a function state's value is not "reacted"?
function Component(props) {
    return createMemo(() => {
        const SelectedComponent = props.Class;
        return SelectedComponent && sample(() => SelectedComponent(props));
    });
}

const App = () => {
    const [state, setState] = createState({
        Class: ComponentA,
    });

    return (
        <>
            <Component Class={(state.Class)}></Component>

            <button onClick={() =>
                setState({
                    Class: ComponentB
                })
            }>Swap</button>
        </>
    )
}

The use case was render a list of components by string class name;
API maybe like this:
const ComponentRegistry = [
  ComponentA,
  ComponentB,
]

const data = [
  { name: '  ComponentA', props: {} },
  { name: '  ComponentB', props: {} }
]

...
state.list = data

...
<For each={(state.list)} fallback={(
Loading...
)}> { item =>
  <Component Class={ ComponentRegistry[item.name] } />
}</For>

Fortunately I'm able to get the expected behavior by using h helper
<For each={(state.list)} fallback={(
Loading...
)}> { item =>
  { h(ComponentRegistry[item.name], item.props) }
}</For>

Glad to know if there is a more elegant way 😁

Ok, yeah. I need to change that. At some point way back to reduce the overhead of native methods I stopped tracking functions. I think that it's inconsistent I will change that. It's a one-liner.
As for your example, I think there are a few things going on. Although it could just be shorthand. I think you just forgot the inner parens (although that shouldn't be necessary for initial render), the registry should be an object. It should be:
const ComponentRegistry = {
  ComponentA,
  ComponentB,
}

const data = [
  { name: 'ComponentA', props: {} },
  { name: 'ComponentB', props: {} }
]

...
const [state] = createState({ list: data })

...
<For each={(state.list)} fallback={(
Loading...
)}> { item =>
  <Component Class={( ComponentRegistry[item.name] )} {...(item.props)} />
}</For>

See: https://codesandbox.io/s/solid-switcher-2-g5c7t
Although for your case are you changing it dynamically? If not the following should be the equivalent of the h function:
<For each={(state.list)} fallback={(
Loading...
)}> { item => {
  const Component = ComponentRegistry[item.name];
  return <Component {...(item.props)} />
}}</For>

The Switcher is only necessary if you intend item.name to change.

Nice sample!
The list can be changed dynamically depend on async fetch for example
If the instance has been created the item.name should not changes I think, but if that happen it should destroy and create a new one
What is the proper way if name never changed?

If the name will never change the Switcher Component is completely unnecessary. If you want to obscure it in a Component to encapsulate you could remove the memo and sample:
function Switcher(props) {
    const SelectedComponent = props.component;
    return SelectedComponent && SelectedComponent(props);
}

Basically Components are just functions. So if it looks too messy. Wrap it up.

Great! Finally the following mimics Svelte's <svelte:component>
function Component(props) {
    const SelectedComponent = props.Class;
    return SelectedComponent && SelectedComponent(props);
}

return <For each={( state.list )}>{item =>
    <Component Class={( ComponentRegistry[item.name] )} {...item.props} />
  }</For>

Dynamic Component very useful for example routing, load many pages dynamically (without Switch) from another module / class. People who see this feature will get an idea of how to implement a single page application with easy.
Love to have this as a Solid's built-in feature 😁

Do you have something against <Switch />? The children <Match/> can also be generated iteratively from data.  I guess it's my React background where routing generally looks like Switch.
I mean this approach is fine but with a JavaScript DSL, it is fairly trivial to write in 2 lines. Essentially we ended wrapping my first suggestion. The 'dirty' solution is fairly common for simple things like passing in template components to children (not so much for routing). A dynamic version is more interesting since I think it could be made to preserves children. Picture swapping out a Container Component that swaps between a panel and modal without destroying and recreating the children. Maybe not common and could handled without changing the Component hierarchy, but unique to this sort of Component.
Anyway, while it's a candidate for control flow inclusion, I feel the verdicts still out for now.

No I haven't, but for this case in my opinion Switch Match is not best, too verbose.
Or I'm missed some docs? This one I found.
<Suspense fallback={( <Loader /> )} maxDuration={ 500 }>
  <Switch transform={ awaitSuspense }>
    <Match when={( state.tab === 0 )}>
      <AsyncChild page='Uno' />
    </Match>
    <Match when={( state.tab === 1 )}>
      <AsyncChild page='Dos' />
    </Match>
    <Match when={( state.tab === 2 )}>
      <AsyncChild page='Tres' />
    </Match>
  </Switch>
</Suspense>

Or can you give me a sample in this case using Switch Match?

Well your case was just iterating over different templates and in itself isn't routing. There is no condition just template mapping. For custom templating what was done makes a lot of sense. You can build routing on top of that if you wish by pushing the conditionals into the children (essentially build your own Switch). You could also do routing with that Component switching approach much like the first sandbox and just switch between selected components. But you'd be making the list of possible routes and condition resolution elsewhere (developing whatever DSL makes sense) which is perfectly fine.
It's pretty common in dynamic nested routing libraries to work more like Switch. Especially in React land. For example:
React Router
Reach Router
Svelte Routing
Polymer App Route
I think there are several ways to approach this and I know there is some aversion to putting something like Route resolution in JSX. I did have that at one point. My own WebComponent Router works more like Vue or Ember Router. And this is a good approach to take something like what we have built in this thread and have it read off a Context API store that its Provider wraps your app with. A pretty slick Router could be the output.
As a library author something like Switch is appealing because it's so dirt simple. As a primitive it handle a lot of different cases (including routing) very easily but doesn't prevent people from developing more advanced routing mechanisms. I can build a simple router with path resolution: https://codesandbox.io/s/jjp8m8nlz5. A handful of lines of code I've built a single layer router based on hashchange. Or in the other example a simple tab switcher. I'm sure there are better Routing options out there for Solid but I will leave that for the community as I'm sure they will have a good idea exactly what they are looking for that week, and it feels like opinions like this change weekly. I know mine do.
I was just interested what about Switch put you off right off the start since I do like the basic primitives to at least feel inviting if only a little basic. If it's just the verbosity, that's fine. I'm always interested in feedback.

I'm going to leave this as is for now. I do see some value here. However, its very standard JSX stuff. Stuff I realize that isn't obvious if you haven't used JSX or React before. Maybe I need to work on better examples. But I don't see the need to include this as part of core currently.


Kusama app in Ledger Nano S shows only one account  Added via  Ledger in Polkadot.js apps

Hi I added via Ledger one account in Polkadot.js apps and used it. The problem appeared when I added the second account.  Since then when I try on the first account Show address on hardware device the Kusama app shows me the address of the second account . When I try to transfer funds from the first account to injected one Ledger shows me the address of the second account and I can not make transfer (error 1010). I "forget" the second account and nothing has changed. Ledger shows the address of the second account.
This might be helpful to the developers:
The first account on Polkadot.js apps was created by add via  Ledger  on Polkadot network by using option Allow on all networks so I got account on Kusama network either.  I used both Polkadot and Kusama accounts on Ledger Nano S but not at the same time because of the lack of memory and had no problem. Now I can install Polkdot app and use Polkadot account but when I install Kusama app can not use the Kusama account.
The second account was created and added via Ledger on Kusama network directly.
Is it possible that account added on Kusama netowork directly, somehow has priority?
Do not let this question of mine mislead  you.
Anyway, I am in situation that I can not approach to my funded account and it is chaos that I did not expect.
Kusama v. 4.28.3 right now on my Ledger. The first account was created and used in march the second a week ago and I
I am not the developer. I hope I explain the situation well.  If you have any question I will try to answer. My account is funded and I expect the solution.

Any news regarding the issue I had reported? I can not connect Polkadot.js apps account and Ledger properly. Kusama app shows me wrong address.

Thanks for your message.
The problem you are describing is related to polkadot.js (webwallet) not the software running in the device itself.
We would recommend opening this issue in their repository https://github.com/polkadot-js/apps


Update Schemes and voting machine options to whats available in the last version of Arc

Work ongoing in branch generic_view-scheme_with_voting


Ensure Open Front End dependabot updates target develop

The choice to restrict this change to the Open Front End code is deliberate as I think it's the only instance of Python code with a properly curated requirements.txt file. There are 2 other instances:

/tools/cloud-build/requirements.txt
/docs/hybrid-slurm-cluster/requirements.txt

The cloud-build requirements.txt contains no version constraints at all while the Slurm docs appear to be more of a tutorial without any integration testing. So, for now, I think we are better off configuring what we test.

[ ] Is unit test coverage still above 80%?
[x] Have you updated all applicable documentation?
[x] Have you followed the guidelines in our Contributing document?

@heyealex the force push updates the path from /community/front-end to /community/front-end/ofe/ to (A) properly restrict to Open Front End code and (B) include the trailing slash which I think might be more correct.


Mask not working on inital value on Ionic.

Howdy.
The initial value is not masked, only by changing the value does the mask begin to work.
Steps to reproduce:
ionic start test blank
cd test
npm i -S angular2-text-mask

Then add import { TextMaskModule } from 'angular2-text-mask'; to app.module.ts, and the following home.ts:
import { Component } from '@angular/core';
import { NavController } from 'ionic-angular';

@Component({
  selector: 'page-home',
  templateUrl: 'home.html'
})
export class HomePage {
  server: string;
  mask: any = [/\d/, /\d/, '-', /\d/]

  constructor(public navCtrl: NavController) {}

  ngOnInit() {
    this.server = '134';
  }

}

and home.html:
<ion-header>
  <ion-navbar>
    <ion-title>
      Ionic Blank
    </ion-title>
  </ion-navbar>
</ion-header>

<ion-content padding>
  <ion-label stacked>Digite o número do servidor</ion-label>
  <ion-input [(ngModel)]="server" [textMask]="{mask: mask}"></ion-input>
</ion-content>

Ionic info:
global packages:

    @ionic/cli-utils : 1.1.2
    Ionic CLI        : 3.1.2

local packages:

    @ionic/app-scripts              : 1.3.7
    @ionic/cli-plugin-ionic-angular : 1.3.1
    Ionic Framework                 : ionic-angular 3.4.2

System:

    Node       : v7.9.0
    OS         : Linux 4.10
    Xcode      : not installed
    ios-deploy : not installed
    ios-sim    : not installed

This is not a bug, but expected behavior.

On 21. Jun 2017, at 19:19, Jeann Porfírio<EMAIL_ADDRESS>wrote:
Howdy.
The initial value is not masked, only by changing the value does the mask begin to work.
Steps to reproduce:
ionic start test blank
npm i -S angular2-text-mask
Then add import { TextMaskModule } from 'angular2-text-mask'; to app.module.ts, and the following home.ts:
import { Component } from '@angular/core';
import { NavController } from 'ionic-angular';
@Component({
selector: 'page-home',
templateUrl: 'home.html'
})
export class HomePage {
server: string;
mask: any = [/\d/, /\d/, '-', /\d/]
constructor(public navCtrl: NavController) {}
ngOnInit() {
this.server = '134';
}
}
and home.html:

      Ionic Blank

Digite o número do servidor

Ionic info:
global packages:
@ionic/cli-utils : 1.1.2
Ionic CLI        : 3.1.2

local packages:
@ionic/app-scripts              : 1.3.7
@ionic/cli-plugin-ionic-angular : 1.3.1
Ionic Framework                 : ionic-angular 3.4.2

System:
Node       : v7.9.0
OS         : Linux 4.10
Xcode      : not installed
ios-deploy : not installed
ios-sim    : not installed

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Sounds fair, but why is it different outside of ionic? Making a similar example on Angular works, applying the mask correctly.
More important, how may I get around that?

Would really love some help on this issue, if anybody could chime in.

Ionic overwrites every custom ControlValueAccessor such as textmask, see my comment here: https://github.com/text-mask/text-mask/issues/294#issuecomment-309097923
The only viable solution would be to stop using ionic-input.

Shame it doesn't work, hopefully the Ionic team patches it on their end so it works more like Angular and less like it does now. That is my biggest problem with Ionic: the ways it doesn't work like Angular.
Thanks for the help, gonna try to find another way out of this.


Add order to REST endpoints jogadores/partidas/goleadores

Improve user experience showing, for example, jogadores ordering by their name.

Defined, on back-end, defaults for sorting endpoints jogadores and partidas:

/api/jogadores?sort=nome,asc
/api/partidas?sort=dataRealizacao,desc

The API client can pass other order like /api/jogadores?sort=id,desc.
The API client can pass too a page it want to retrieve like: /api/jogadores?page=1&size=5
In goleadores endpoint, the order was hardcoded to totalGols,desc


Does not work for me?

I have tried the mod on its own, and with other mods but when I try to run the buyday option, it says order cancled every single time, and I do not recieve any extra days. And its not because I dont have enough credits/money.

Hey @xlilpulpx , thanks for letting me know.
What is the version of the mod (the latest is 2.1.2)? What other mods are you playing with? Some mods might overwrite this mod terminal extension.
If you disable all mods and keep only this, is it working?

I am on the latest version currently.

Hey @xlilpulpx thanks. I will look into it, but I will also would suggest that maybe we can talk over Discord and I will try to troubleshoot with you what's going on. Plus if you can share logs it will help me to investigate and identify the issue


Problem with conda and channel

Hi,
I try to install asp with conda, but when I run the install command, it gives me the following message.
"(base) @Mini-de-Thomas / % conda install stereo-pipeline==3.2.0
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
PackagesNotFoundError: The following packages are not available from current channels:

stereo-pipeline==3.2.0

Current channels:

https://conda.anaconda.org/nasa-ames-stereo-pipeline/osx-arm64
https://conda.anaconda.org/nasa-ames-stereo-pipeline/noarch
https://conda.anaconda.org/usgs-astrogeology/osx-arm64
https://conda.anaconda.org/usgs-astrogeology/noarch
https://conda.anaconda.org/conda-forge/osx-arm64
https://conda.anaconda.org/conda-forge/noarch
https://repo.anaconda.com/pkgs/main/osx-arm64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/r/osx-arm64
https://repo.anaconda.com/pkgs/r/noarch

To search for alternate channels that may provide the conda package you're
looking for, navigate to
https://anaconda.org

and use the search bar at the top of the page".
Channels are well configured :
"(base) @Mini-de-Thomas / % conda config --env --add channels conda-forge
(base) @Mini-de-Thomas / % conda config --env --add channels usgs-astrogeology
(base) @Mini-de-Thomas / % conda config --env --add channels nasa-ames-stereo-pipeline
(base) @Mini-de-Thomas / % conda config --show channels
channels:

nasa-ames-stereo-pipeline
usgs-astrogeology
conda-forge
defaults"

It seems not to find stereo pipeline on conda.
Could you help me to install it? Thanks
My computer is a Mac Mini M1 with Mac Os X Monterey version 12.6.5
Thomas

ASP does not support M1, only the Intel processor. I heard people ran
successfully the Intel binaries via the translation layer. Those can be
obtained from https://github.com/NeoGeographyToolkit/StereoPipeline/releases
.
On Mon, May 15, 2023 at 6:34 AM tthomopoulos @.***>
wrote:

Hi,
I try to install asp with conda, but when I run the install command, it
gives me the following message.
"(base) @Mini-de-Thomas / % conda install stereo-pipeline==3.2.0
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with
flexible solve.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with
flexible solve.
PackagesNotFoundError: The following packages are not available from
current channels:

stereo-pipeline==3.2.0

Current channels:

https://conda.anaconda.org/nasa-ames-stereo-pipeline/osx-arm64
https://conda.anaconda.org/nasa-ames-stereo-pipeline/noarch
https://conda.anaconda.org/usgs-astrogeology/osx-arm64
https://conda.anaconda.org/usgs-astrogeology/noarch
https://conda.anaconda.org/conda-forge/osx-arm64
https://conda.anaconda.org/conda-forge/noarch
https://repo.anaconda.com/pkgs/main/osx-arm64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/r/osx-arm64
https://repo.anaconda.com/pkgs/r/noarch

To search for alternate channels that may provide the conda package you're
looking for, navigate to
https://anaconda.org
and use the search bar at the top of the page".
Channels are well configured :
"(base) @Mini-de-Thomas / % conda config --env --add channels conda-forge
(base) @Mini-de-Thomas / % conda config --env --add channels
usgs-astrogeology
(base) @Mini-de-Thomas / % conda config --env --add channels
nasa-ames-stereo-pipeline
(base) @Mini-de-Thomas / % conda config --show channels
channels:

nasa-ames-stereo-pipeline
usgs-astrogeology
conda-forge
defaults"

It seems not to find stereo pipeline on conda.
Could you help me to install it? Thanks
My computer is a Mac Mini M1 with Mac Os X Monterey version 12.6.5
Thomas
—
Reply to this email directly, view it on GitHub
https://github.com/NeoGeographyToolkit/StereoPipeline/issues/400, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKDU3AO6QOMOZ5KQJ4NEEDXGIWFRANCNFSM6AAAAAAYCGULLU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Since ASP depends on the USGS's ISIS software libraries, and until those are fully functional natively on Apple Silicon, we can't do much about it.
For now, it does appear that running conda, ISIS, and ASP via the translation layer might work for some folks.  You can also certainly experiment with virtualization solutions to try and run a Linux image to install ISIS and ASP in.
Of course, as Oleg says, you should be able to run the pre-compiled ASP Intel binaries via the translation layer.  Of course, running ASP with a Mac Mini is a brave act, and we salute you.

Based on https://github.com/DOI-USGS/ISIS3#installation, they don't do have custom binaries for M1, and they trick your system into installing x86-64 and Rosetta. Can the same instructions be used with ASP?

I understand. I was wondering if one can ignore the ASP instructions and use the ISIS instructions that worked for you, except for adding the ASP channel on top of the rest. I surely understand if you find these things too tricky, and it should be on our side to sort things out.
For now, one should not use conda then with M1, and download the ASP tarball as in https://stereopipeline.readthedocs.io/en/latest/installation.html. I know from people that that approach works.


AzDO issue #5882

https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_workitems/edit/5882

@missymessa what's with Tampermonkey showing undefined instead of the internal content❔ please let me know if I'm unique of course :grin:

done

@missymessa what's with Tampermonkey showing undefined instead of the internal content❔ please let me know if I'm unique of course 😁

I think the script needs to be fixed. Feel free to make a PR https://github.com/missymessa/tampermonkey-scripts


Double-click on machine name in 'edit connection' launches test connection

Create connection
Open it for editing
Double-click on machine name (say, you want to paste over selection)
Observed: Test connection starts
Expected: select machine name in the edit box

Looks like it just closes the edit area

It seems to trigger the double click event since, the event is set on the list view item.


Using reactiveplusplus with vcpkg and MSBuild

Hey there! Firstly, thanks for this wonderful library!
Has anyone tried using reactiveplusplus with vcpkg and MSBuild? I'm currently using it as a submodule and it works great, but I'd like to start using vcpkg (already using it for other dependencies).
It seems the installation folder is a level before, so I can access it by including rpp/rpp/rpp.hpp but that doesn't solve the issue, since the other files depend on the correct location. Any clues?

Hey @idotta!
Looks pretty interesting.. unfortunately i can't access windows-based machine for some time so i can't check/reproduce it.
As far as i know this pr is successful usage of rpp via vcpkg but not sure about MSBuild... Anyway, i think it could help if you would make some short simple example to reproduce issue =)

Hey @victimsnino! Yeah, it works with CMake. However it doesn't work correctly with MSBuild. I created an issue in the vcpkg repository and they suggested to work around it by adding a new include directory to the solution.
This is the working sample that I created for future reference. Thanks!


Elasticsearch 1.4.0 hangs on running twitter river

When running Twitter in elasticsearch 1.4, it could happen that some cluster API don't work anymore.
The river is not created properly so the cluster does not seem to be updated and is kept in a blocked state.
This patch makes the start() method returning as soon as possible and spawn a Thread which will actually do the initialization when the cluster is in yellow or green state.
Closes #83.

LGTM, but I really don't like the Thread.sleep() after tests. We should try to find something else...

@tlrx Agreed. I think the answer should be in the test framework itself. We should may be wait for some seconds while all threads has not been closed instead of failing the test immediately?


Tests

Hello.
I was thinking about creating some tests (with coverage) for this repository and I'd like to know what you think about it. So I know if I should carry on or not.
I'd also like to setup the integration with travis and coveralls, if you like the idea.
Anyway, here's what I got so far:
https://github.com/ericmdantas/angular-recaptcha

Hey @ericmdantas
We'd love to have that! If you feel like taking over, please do!
Thanks!

Alright!
I'll submit a PR when I have most stuff done.
Closing this.


Canot fetch news

Since last month? CNBETA might change API. Please have a look at it, thanks.

是的，确实是换了 API，比如文章的链接，Load More 的链接都换了。因为最近我在考虑模仿你的那个写一个，所以也在研究。

Sincerely yours,
Shilei Tian
On 12 Mar 2017, 21:07 +0800, mailbyms<EMAIL_ADDRESS>wrote:

Since last month? CNBETA might change API. Please have a look at it, thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

官方改版，接口失效了，我暂时没有精力继续维护，但是依然接受PR


Test difference.

For the multi-view reasoning task, the prediction results of model llava-1.6 are all (A).

Test in official demo (LLaVa-1.6-34B)

Hi ApolloRay, apologies for the late reply! Feel free to shoot me an email at<EMAIL_ADDRESS>and I'm happy to schedule a meeting and discuss about this issue with you.