bug or feature ? better optimisation console output

#Deploying an Angular2 app, I run the following build common, after compilation and at-loader plugin run, I get a remote console output info, then no output for a long time ... and the optimisation process output in a bad format ( no break in the lines..) which make it difficult to read.
I don't know if it's a due to wrong parameters or if it's. bug...
Could it be possible :
1- to insert a spinner or any indication to the user when a long process is running ..?
2- correct the format of the console output during optimization ?
build command
"build:production": "node_modules/.bin/del-cli public/js/app && node_modules/.bin/ngc -p tsconfig.aot.json && node_modules/.bin/ngc -p tsconfig.aot.json && node_modules/.bin/webpack --config webpack.config.prod.js --optimize-minimize  --progress --profile --bail && node_modules/.bin/del-cli 'public/js/app/**/*.js' 'public/js/app/**/*.js.map' '!public/js/app/bundle.js' '!public/js/app/*.chunk.js' 'assets/app/**/*.ngfactory.ts' 'assets/app/**/*.shim.ts'"

webpack.config.prod.js   (extract)
`
watch:` false,
module: {
    loaders: [
        {
            test: /\.ts$/,
            loaders: [
                'awesome-typescript-loader',
                'angular2-template-loader',
                'angular2-router-loader?aot=true&genDir=public/js/app'
            ]
        }
    ]
},

`
console-output. very long lines... slide horizontally to see them...)
<EMAIL_ADDRESS>    	@erwin16.live [at-loader] Using<EMAIL_ADDRESS>from typescript and "tsconfig.json" from
                                  11870ms building modules                                                                                @erwin78ms sealing
@er3ms optimizing                                                                                2ms basic module optimization                                                                                183ms module optimization                                                                                4ms advanced module optimization                                                                                0ms basic chunk optimization                                                                                1ms chunk optimization                                                                                4ms advanced chunk optimization                                                                                2ms module and chunk tree optimization                                                                                233ms module reviving                                                                                11ms module order optimization                                                                                20ms module id optimization                                                                                11ms chunk reviving                                                                                3ms chunk order optimization                                                                                40ms chunk id optimization
@erwin97ms hashing                                                                                2ms module assets processing                                                                                287ms chunk assets processing                                                                                16ms additional chunk assets processing
  `

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template, or open a new issue.


Visitor and listener interfaces can only access top level keywords

Problem:
If I use a class that implements SuiteVisitor class and visit_keyword method kw.keywords always comes back as an empty list:
    def visit_keyword(self, kw):         print(kw.keywords)
visit_suite or start_suite behave similarly - they only return the top level keywords for the suites.
Same issue with listener interface with the start_suite method with ROBOT_LISTENER_API_VERSION = 3
Suggestions:

return at least the first level of depth for keywords. Right now if I create a --prerunmodifier script for keywords it has no effect for keywords with multiple layers - anything that is in a robot resource file for example.
add one more parameter so the user can choose how deep the script will go
if any of the above suggestions would not be ok, at least remove the keywords attribute from the keyword class - I can't find a scenario where it could be used right now.

You mentioned using --prerunmodifier so I assume you are visiting the data model, not the result model. On the data model keywords don't have any child keywords simply because resolving keywords only occurs during execution. Because of this having keywords and messages attributes on the data model made no sense and, as you suggested, they were removed in RF 4.0 as part of #3749.
On the result side keywords can have child keywords and there you can access them using a visitor. Notice that RF 4.0 ( #3749) changed keywords to body, though, and that body nowadays also contains messages.


How can i create .rec file for R

suppose, as example just take captcha picture from this classic task
https://github.com/apache/incubator-mxnet/tree/master/example/captcha
so, i create train.lst
https://github.com/apache/incubator-mxnet/blob/master/example/captcha/captcha_example.png
my train.lst file contain
0	6	6	4	3	train /C:/Users/Adm/Downloads/pic/captcha_example.png
How to get .rec file for it in R language?

.Rec file is a binary file and should be independent from the platform - once you have it, you should be able to use either R or Python.
You can create both .lst file and .rec file using im2rec tool. Please, look at this explanation how to do it: https://github.com/leocvml/mxnet-im2rec_tutorial

in R there is im2rec function,
but  my train.lst contains
0	6	6	4	3	train/C:/Users/adm/Downloads/pic/captcha_example.png
library(“mxnet”)
im2rec(image_lst=“C:/Users/adm/Desktop/train.lst”, root=‘C:/Users/adm/Downloads/captcha_example’,
output_rec=‘C:/Users/adm/Desktop/my.rec’, label_width = 4L, pack_label = 0L,
new_size = -1L, nsplit = 1L, partid = 0L, center_crop = 0L,
quality = 95L, color_mode = 1L, unchanged = 0L, inter_method = 1L,
encoding = “.png”)
then i get the error
Error in mx.internal.im2rec(image_lst, root, output_rec, label_width, :
could not find function “mx.internal.im2rec”
What’s wrong
hoe to correct set the arguments

Unfortunately, im2rec doesn’t work from R. There is an open issue about that, but so far it hasn’t been done: https://github.com/apache/incubator-mxnet/issues/7273
Please, use python or C++ to generate both .lst and .rec files. Take a look at this tutorial for more information: https://github.com/leocvml/mxnet-im2rec_tutorial

Ishitori may i ask you help me here?
https://github.com/apache/incubator-mxnet/issues/14204


Allow specifying run tags in pipeline configuration

Describe changes
This PR adds the ability to specify tags for pipeline runs

in the config file

# config.yaml
tags:
  - tag_in_config_file

in code on the pipeline decorator or in pipeline.configure/with_options

@pipeline(tags=["tag_on_decorator"])
def my_pipeline():
  ...

my_pipeline = my_pipeline.with_options(config_file="config.yaml")
run = my_pipeline()
run.tags  # <- will be tag_in_config_file and tag_on_decorator

Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
[ ] If my changes require changes to the dashboard, these changes are communicated/requested.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

This looks great. I have a few follow-up comments though:

First, since we are using tags more often now, it would be great if we implement a filtering mechanism for these entities based on their tags. (Not just for pipeline runs, but also for artifact versions, model versions, and so on). What do you think?
We have recently added the ability to add tags to sagemaker pipelines and steps. Structurally, they look a bit different and it might get a bit confusing to define tags separately for ZenML pipelines and orchestrator pipelines.

pipeline_settings = SagemakerOrchestratorSettings(
    pipeline_tags={
        "project": "my-ml-project",
        "environment": "production",
    }
)

step_settings = SagemakerOrchestratorSettings(
    tags={
        "step": "data-preprocessing",
        "owner": "data-team"
    }
)

Do you think there is also value in using the same tags in the future to tag step runs as well (as we do for Sagemaker pipelines)?

Filtering by tags is implemented in the API and even in the frontend for all these entities? Or am I missing some other place where you'd want to filter by them?
We currently don't display steps anywhere separately (at least in the dashboard, which IMO is the main usecase for filtering). So I don't see any value in tagging step runs, at least for now. As for the confusion with sagemaker tags: They'll figure it out if they explicitly define tags for their sagemaker orchestrator and they don't show up on their ZenML pipelines, I wouldn't worry about that.


Making dockershim FAQ evergreen

After a brief discussion in ContribEx Slack, we realized we shouldn't mark the dockershim FAQ as out of date once it hits a year old. It's still relevant, accurate, and I know I reference it at least once a month still.
@reylejano says we should mark it as evergreen and this PR accomplishes that.

and edit the source for https://k8s.io/docs/tasks/administer-cluster/migrating-from-dockershim/ – add a prominent comment to the front matter. The comment should say that if we are removing that page / section, we need to go back and edit https://kubernetes.io/blog/2022/02/17/dockershim-faq/ to remove the link to it.

@sftim I was a little confused by this at first (might be the lack of coffee).
But, basically you want a comment at the top of migrating-from-dockershim file stating update the FAQ if this page is changed/removed? Same PRs or different ones?

But, basically you want a comment at the top of migrating-from-dockershim file stating update the FAQ if this page is changed/removed? Same PRs or different ones?

Same PR is good, because that shows we've checked the boxes for making the blog article need minimum maintenance. What we don't want is to have to set reminders to check for or fix these things every few months. evergreen means we're promising to maintain the article, or that it doesn't need maintenance.

/approve
/hold
@chris-short you're welcome to unhold this if you judge that you've made the article evergreen, and you've got an LGTM from another contributor to confirm that.

/lgtm
@chris-short , feel free to unhold when ready

/label tide/merge-method-squash

Re-applying lgtm
/lgtm
@chris-short feel free to unhold when ready

/unhold
A followup PR can be made to address comment


TrashedFilter only works when i refresh the page

Package
filament/filament
Package Version
3.2
Laravel Version
10.10
Livewire Version
10.0
PHP Version
8.2.1
Problem description
The TrashedFilter when chained with ->native(false) doesn't apply until i refresh the page
https://github.com/filamentphp/filament/assets/76778937/0650ac6a-2f77-4bfc-81db-66f684831e0d
when removing the ->native(false) chain it doesn't work until i click anywhere on the screen
https://github.com/filamentphp/filament/assets/76778937/5f926d5f-6c2b-4aea-947b-6bb9ba6d6cf8
Expected behavior
the TrashedFilter should work without refreshing the screen
Steps to reproduce

the filter should work correctly without need to refresh the page when
chained with ->native(false)

the filter should work correctly when chained with ->native(true) without need to anywhere on the screen

Reproduction repository
https://github.com/AHMED-GAMAL-AG/Filament-TrashedFilter-Bug
Relevant log output
No response

Works fine for me
https://github.com/filamentphp/filament/assets/41773797/a121328b-defc-47b6-8d5b-1a6e62abe40d


chore(deps): update renovate/renovate docker tag to v35.73.0

This PR contains the following updates:

Package
Update
Change

renovate/renovate
minor
35.71.0 -> 35.73.0

Release Notes

renovatebot/renovate
v35.73.0
Compare Source
Features

manager/gradle: Support properties map in gradle kts (#21792) (2112ea2)

Code Refactoring

scm: use scm for getFileList, checkoutBranch (#22006) (9276a54)

v35.72.1
Compare Source
Build System

deps: update dependency @renovatebot/pep440 to v2.1.15 (#22003) (1cd405b)

v35.71.7
Compare Source
Build System

deps: update dependency semantic-release to v21.0.2 (#22002) (9015d10)

v35.71.6
Compare Source
Build System

deps: update dependency @renovatebot/ruby-semver to v3 (#21984) (f9f52a5)

v35.71.5
Compare Source
Build System

switch hcl parser (#21988) (4924973)

v35.71.4
Compare Source
Build System

deps: update dependency redis to v4.6.6 (#21981) (44f2298)

v35.71.1
Compare Source
Bug Fixes

onboarding: don’t check onboarding cache unless onboarding=true (#21967) (665866a)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

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


Config option for list widget to allow default list when using fields option

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

Currently, the default option on the list widget only allows you to provide a default value when using the field option which allows you to specify a comma separated list of string items. However, when using the fields option, the default option has no effect, instead you must specify defaults for each of the individual fields being used.
From the documentation:

you may specify a list of strings to populate the basic text field, but declare defaults on the child widgets if you are specifying fields

This makes it impossible to, for example, specify a default list of 2 or more items
Describe the solution you'd like

Add a new config option for list widgets called default_list that allows users to specify the default list that should be applied for new entries.
For example, given the config:
label: Buttons
label_singular: button
name: buttons
widget: list
fields:
  - label: Text
    name: text
    widget: string
  - label: Link
    name: link
    widget: string
  - label: Type
    name: type
    widget: select
    default: primary
    options:
      - label: Primary
        value: primary
      - label: Secondary
        value: secondary
  - label: Inverted
    name: inverted
    widget: boolean
    required: false
default_list:
  - text: Get Started
    link: /get-started/
    type: primary
    inverted: false
  - text: Book a Demo
    link: /demo/
    type: secondary
    inverted: true

The default list in the editor pane should contain 2 items with the shape:
[
    {
        text: "Get Started",
        link: "/get-started/",
        type: "primary",
        inverted: false,
    },
    {
        text: "Book a Demo",
        link: "/demo/",
        type: "secondary",
        inverted: true,
    },
];

After looking into this a bit, it looks like you can set a default empty array for complex lists as per #3746.
I propose that list widgets should always use whatever default array (or comma separated string for simple lists). If no default option is provided, then it can fallback to the current implementation which creates a single item using the defaults of the provided fields.


"Error displaying widget" in Jupyterlab

Hi
I can get ipysankeywidget working in jupyter (on jupyterhub), but it fails when the notebook is opened with jupyterlab. Here the error:
Error displaying widget

The console shows a bit more information:

Any idea on how to install it on jupyterlab? jupyterlab-manager is well installed, plotly and other ipywidget extension work fine. I can't get ipysankey to load jupyter-sankey-widget.
Thanks

Hi, thanks for reporting this! I believe jupyterlab uses a slightly different widget extension system so ipysankeywidget needs to be updated before it will work there.
I’d like to get this to work at some point whenever we have time to work on it. If you know any more about this or would like to do some research that’d be very helpful to get the ball rolling.
Thanks

On 23 Oct 2018, at 14:32, Gaetan Semet<EMAIL_ADDRESS>wrote:
Hi
I can get ipysankeywidget working in jupyter (on jupyterhub), but it fails when the notebook is opened with jupyterlab. Here the error:
Error displaying widget
The console shows a bit more information:
Any idea on how to install it on jupyterlab? jupyterlab-manager is well installed, plotly and other ipywidget extension work fine. I can't get ipysankey to load jupyter-sankey-widget.
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.

indeed the plugin should be ported to jlab

+1

+1


Task Docker@0 fails on Azure Pipeline vmimage windows-latest or windows-2019

After serveral attempts to build an image with the task Docker@0 or Docker@2, the process fails every time.
The scenario is the following:
ymal build template with two stages
Stage 1 - builds the app
Stage 2 - builds the docker image and pushes to registry
Simple.
We use this task on other pipelines, but it only works when there is no other task. Besides a replace tokens task like:  colinsalmcorner.colinsalmcorner-buildtasks.replace-tokens-task.ReplaceTokens@1.
On the build pipeline with two stages the Docker task returns errors that can not find docker command.
Agent name: 'Hosted Agent'
Agent machine name: 'WIN-JSNSO4LLK4M'
Current agent version: '2.166.4'
Current image version: '20200430.2'
Agent running as: 'VssAdministrator'
Prepare build directory.
Set build variables.
Download all required tasks.
Downloading task: DownloadPipelineArtifact (2.3.0)
Downloading task: ReplaceTokens (1.2.178)
Downloading task: Docker (2.166.1)
Checking job knob settings.
Finished checking job knob settings.
Start tracking orphan processes.

Task log, build pipeline with 2 stages:
##[error]Unhandled: Unable to locate executable file: 'docker'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
On the build pipeline that has only Replace tokens task runs fine.
Agent name: 'Hosted Agent'
Agent machine name: 'WIN-JSNSO4LLK4M'
Current agent version: '2.166.4'
Current image version: '20200430.2'
Agent running as: 'VssAdministrator'
Prepare build directory.
Set build variables.
Download all required tasks.
Downloading task: ReplaceTokens (1.2.178)
Downloading task: Docker (0.157.0)
Checking job knob settings.
Finished checking job knob settings.
Start tracking orphan processes.
Log task sample:
C:\Program Files\Docker\docker.exe" build -f D:\a\1\s\Dockerfile -t

In both build pipelines the agents are the same.
I also did a test with self-hosted agents and the same issue.

@thovipe Thank you for the feedback.
Please see if this recent post addresses the issue.

I am already using the latest versions, the point that is we have some other pipelines working. Today I did a adjust in a old pipeline definition and broke that one was well. Even removing the adjust did not solve. I had to revert the definition.

Guys problem solved.
It was a bad variable name.
Thanks for the support.


Set Allow response headers

To the HTTP methods the service supports. See http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.14.7

Closed via https://github.com/feathersjs/feathers-rest/pull/42


500 Error when trying to open non renamed page

In our Grav installation (available upon request), we had a page /products/p/astrobox which was moved to /products/p/astrobox-gateway.
Google Webmaster tools detected an error 500 when trying to access the old route, instead of the expected 404. Looking in the logs in our dev environment the error is:
PHP message: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 67905 bytes) in /Users/arroyo/3dagogo-repos/astroprint/CMS/www/system/src/Grav/Common/Page/Pages.php on line 410" while reading response header from upstream, client: <IP_ADDRESS>, server: ~www.astroprint.(dev|net|intranet)$, request: "GET /products/p/astrobox HTTP/1.1"
Using Grav 1.2.3

I'm not able to replicate a simple moved page causing a 500 error.  The only think i can think of off hand is some redirect or rewrite rule (either in Grav or webserver) that is getting in the way.
is it possible to get a zipped copy of this site to see if I can replicate the issue?

It's this route in your site.yaml conflicting:
routes:
  # /p/astrobox: /products/p/astrobox-gateway

Commenting it fixes the problem and you get a 404


"Show by: Size": improve symbol overlap

It's a bit much at low zooms as "Largest" obscures the rest:

I tried flipping the order but it still looked rough. Also couldn't get the MB style property(ies?) for that to work so had to flip the array.
Neither scenario is problematic at high zooms, however, so consider this issue lowest priority:

@rperlin-ela is this actually a problem or are we treating it same as World Region density? i know it's more arbitrary that World Region but not icon-based like Status, so let's close if we can.


(9.x) Fix for WFLY-4799

Currently timers that are persisted to the file store, when retrieved/loaded back aren't marked as "persistent". This causes issues with the way the timers are dealt with later, one of which is reported in https://issues.jboss.org/browse/WFLY-4799.
The commit here fixes the issue by marking such persisted timers as persistent.
PR for master branch: https://github.com/wildfly/wildfly/pull/7620

Linux with security manager Build 120 is now running using a merge of df35d6ac1a052e107dcda61d87cedb05e1b873fa

Windows Build 127 is now running using a merge of df35d6ac1a052e107dcda61d87cedb05e1b873fa

Linux Build 125 is now running using a merge of df35d6ac1a052e107dcda61d87cedb05e1b873fa

Linux with security manager Build 120 outcome was SUCCESS using a merge of df35d6ac1a052e107dcda61d87cedb05e1b873fa
Summary: Tests passed: 828, ignored: 319 Build time: 0:06:23

Windows Build 127 outcome was SUCCESS using a merge of df35d6ac1a052e107dcda61d87cedb05e1b873fa
Summary: Tests passed: 2870, ignored: 374 Build time: 0:49:21

Linux Build 125 outcome was FAILURE using a merge of df35d6ac1a052e107dcda61d87cedb05e1b873fa
Summary: Tests failed: 31 (29 new), passed: 2762, ignored: 374, muted: 1 Build time: 1:08:33
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase.testPassivationMaxSize: <no details avaliable>

org.jboss.as.test.manualmode.ws.ReloadWSDLPublisherTestCase.testHelloStringAfterReload: <no details avaliable>

org.jboss.as.test.manualmode.ws.WSAttributesChangesTestCase.testWsdlPathRewriteRuleChanges: <no details avaliable>

org.jboss.as.test.manualmode.ws.WSAttributesChangesTestCase.testWsdlPortChanges: <no details avaliable>

org.jboss.as.test.manualmode.ws.WSAttributesChangesTestCase.testWsdlUriSchemeChanges: <no details avaliable>

org.wildfly.test.integration.security.picketlink.federation.SAMLPostBindingWithSignaturesTestCase.testFederationWithGlobalLogout: <no details avaliable>

org.wildfly.test.integration.security.picketlink.federation.SAMLPostBindingWithSignaturesTestCase.testFederationWithLocalLogout: <no details avaliable>

org.wildfly.test.integration.security.picketlink.federation.SAMLMetadataTestCase.testFederationWithGlobalLogout: <no details avaliable>

org.wildfly.test.integration.security.picketlink.federation.SAMLMetadataTestCase.testFederationWithLocalLogout: <no details avaliable>

org.wildfly.test.integration.security.picketlink.federation.SAMLRedirectBindingTestCase.testFederationWithGlobalLogout: <no details avaliable>

org.wildfly.test.integration.security.picketlink.federation.SAMLRedirectBindingTestCase.testFederationWithLocalLogout: <no details avaliable>

##### there are 21 more failed tests, see build details

retest this please

Windows Build 128 is now running using a merge of df35d6ac1a052e107dcda61d87cedb05e1b873fa

Linux Build 126 is now running using a merge of df35d6ac1a052e107dcda61d87cedb05e1b873fa

Linux with security manager Build 121 is now running using a merge of df35d6ac1a052e107dcda61d87cedb05e1b873fa

Linux with security manager Build 121 outcome was SUCCESS using a merge of df35d6ac1a052e107dcda61d87cedb05e1b873fa
Summary: Tests passed: 828, ignored: 319 Build time: 0:05:29

Windows Build 128 outcome was SUCCESS using a merge of df35d6ac1a052e107dcda61d87cedb05e1b873fa
Summary: Tests passed: 2870, ignored: 374 Build time: 0:46:26

Linux Build 126 outcome was SUCCESS using a merge of df35d6ac1a052e107dcda61d87cedb05e1b873fa
Summary: Tests passed: 2869, ignored: 374, muted: 1 Build time: 0:48:54


shield role producing invalid YAML

I could be doing something wrong but here is what I have:
puppet manifest:

  elasticsearch::shield::role { 'admin':
    mappings   => ['cn=kibana-acl,ou=Groups,ou=Users,dc=X,dc=corp',],
    privileges => {
      'cluster' => 'all',
      'indices' => {
        'names'      => '*',
        'privileges' => ['all'],
      },
    },
  }

This produces the following roles.yml:
admin:
  cluster: all
  indices:
    privileges:
      - all
    names: "*"

Which doesn't parse and causes the following log in my elasticsearch.log:
[2016-05-17 21:51:33,145][ERROR][shield.authz.store       ] [lg10-instance] invalid role definition [admin] in roles file [/etc/elasticsearch/instance/shield/roles.yml]. could not resolve indices privileges [*]. skipping role...

If I manually change the roles.yml to:
admin:
  cluster: all
  indices:
    - names: "*"
      privileges:
        - all

Things work as expected but of course my changes are overwritten at the next puppet run.

Yeah, this is the unfortunate ambiguity of yaml. In your case you want an array of hashes for indices, so wrapping the value for indices in brackets forms the yaml you want:
  elasticsearch::shield::role { 'admin':
    mappings   => ['cn=kibana-acl,ou=Groups,ou=Users,dc=X,dc=corp',],
    privileges => {
      'cluster' => 'all',
      'indices' => [{
        'names'      => '*',
        'privileges' => ['all'],
      }],
    },
  }

Creates:
$ cat /usr/share/elasticsearch/shield/roles.yml
---
admin:
  cluster: all
  indices:
    - names: "*"
      privileges:
        - all

Let me know if this fixes it.

Here is the result:
admin:
  cluster: all
  indices:
    - privileges:
        - all
      names: "*"

which does not work.

Gotcha. Could you share what version of Puppet, Elasticsearch, and Shield you're working with?

Elasticsearch 2.3.2
Shield 2.3.2
Puppet 3.7.2

Just wanted to follow-up quickly that I did reproduce this, apparently Shield doesn't parse valid yaml and expects name to be the first key in the list of hashes in the roles yaml file. It's pretty annoying behavior, and because ZAML (yaml library in use in Puppet < 4) doesn't dump hashes in sorted form, the problem can be intermittent.
Given some of the other obnoxious behaviors of ZAML, I'll probably just have to write something that returns the yaml in the form Shield expects.
Thanks for tracking this one down, I'll update this once I've got something put together.

@laf-rge alright, this was kind of a hairy problem but for your case it should be fixed in my bugfix branch, feel free to test it out if you want to try it. tl;dr yaml order matters for some shield .yml files, the patch monkey patches each_pair so ZAML gets key/value pairs returned in order (recursively.)
The problem will still exhibit in Puppet >= 4 though, where the native to_yaml is in use rather than ZAML. This is probably significantly easier to solve, but I wanted to ensure this solution works before extending it to Puppet 4.
Work left for this to be merged and fixed is probably either to 1) adjusted the extended method to insert keys in sorted order (which Ruby > 1.8 will preserve) or 2) override each with sorted return values (which native to_yaml uses instead of each_pair in ZAML).

Great! Now:
 44  elasticsearch::shield::role { 'admin':
 45     mappings   => ['cn=kibana-acl,ou=Groups,ou=Users,dc=domain,dc=corp',],
 46     privileges => {
 47       'cluster' => 'all',
 48       'indices' => [{
 49           'names'      => '*',
 50           'privileges' => ['all'],
 51       }],
 52     },
 53   }

produces:
admin:
  cluster: all
  indices:
    - names: "*"
      privileges:
        - all

Also we should update the Readme to reflect the proper way to encode the role (is it [{}]?).
I notice it takes two puppet runs for a config change to actually cause the roles.yml to write out. That could be peculiar to my environment.


Focus locked in the element - Polymer 2

On Polymer 2, once the element is focused, you can not exit it by pressing the TAB key.
The input is focused, then the show clear button is focused, then the input is focused, then the show clear button etc...
The issue is gone by setting disable-show-clear attribute.

I can also reproduce it at least with Chrome in Polymer 2.x. I don't know why this is happening so I will look into it. Do you have any suggestions?
And thanks for letting us know about this issue

Just tried quickly try to reproduce it with the following code:
<paper-input value={{value}}>
   <paper-icon-button slot="suffix" suffix id="clear" icon="clear" on-click="_clear"></paper-icon-button>
</paper-input>

It seems like maybe it is no longer possible to use suffix for this. Or might be a problem with paper-input. I will post more info once I figure out more.

Looks like you hit https://github.com/PolymerElements/paper-input/issues/324.
You could eventually set tabindex="-1" on the icon button for Polymer 2 so the element is not focusable while the issue is open.

@Zecat I think is a good workaround. I will do that

Just pushed your suggestions to the branch. I close this for now


Where is the .yaml file?

All I can find is a file called "discurses". The description is not specific enough

According to the README.md file:

Put the file example_discurses.yaml in your ~/.config/ […]

You need to create it then put the token into it.


Put getting started example on cargo page

The crates.io description page only shows the text description of the package, but interested users do not see at first glance how this library can fulfill his/her needs.

It would be nice if the same example as in the README was shown on the cargo page.

I think this is the same as #22, i.e. when releasing 0.3.1 I didn't fill out the Cargo.toml metadata correctly.
I'm doing a fairly large rewrite in #28, so hopefully it'll be fixed when that is released.


Add support for kalkih/simple-weather-card

Version of HACS
0.8.1
Describe the bug
I can't add the simple-weather-card
Other customs card from @kalkih are supported and already in store
"kalkih/mini-media-player",
"kalkih/mini-graph-card",

Debug log
2019-06-20 22:22:32 [custom_components.hacs.frontend] GET POST call for repository_register with new
2019-06-20 22:22:32 [custom_components.hacs.frontend] GET POST call for https://github.com/kalkih/simple-weather-card with plugin
2019-06-20 22:22:32 [custom_components.hacs.hacs] Starting repository registration for kalkih/simple-weather-card
2019-06-20 22:22:33 [homeassistant.core] Bus:Handling , new_state=>
2019-06-20 22:22:33 [homeassistant.core] Bus:Handling , new_state=>
2019-06-20 22:22:35 [custom_components.hacs.hacs] kalkih/simple-weather-card - No acceptable js files found
2019-06-20 22:22:35 [custom_components.hacs.hacs] kalkih/simple-weather-card - Could not register.

I have no control over nor do I wish to have control over any external repository.
Your error is correct "No acceptable js files found".


transient-universe 0.3.2

Ping @agocorona
Building transient-universe-0.3.2...
Preprocessing library transient-universe-0.3.2...
[1 of 4] Compiling Transient.Move   ( src/Transient/Move.hs, dist/build/Transient/Move.o )
[2 of 4] Compiling Transient.MapReduce ( src/Transient/MapReduce.hs, dist/build/Transient/MapReduce.o )
[3 of 4] Compiling Transient.Move.Utils ( src/Transient/Move/Utils.hs, dist/build/Transient/Move/Utils.o )
[4 of 4] Compiling Transient.Move.Services ( src/Transient/Move/Services.hs, dist/build/Transient/Move/Services.o )

src/Transient/Move/Services.hs:99:52: error:
    • Variable not in scope:
        (!>) :: Cloud [Node] -> (Node, Int) -> Cloud [Node]
    • Perhaps you meant one of these:
        ‘>>’ (imported from Control.Monad),
        ‘<>’ (imported from Data.Monoid),
        ‘*>’ (imported from Control.Applicative)

Sent a fix yesterday to Hackage...

fixed


Struct tags get ignored for net.Prefix

Describe the bug
The tags on netip.Prefix types get ignored when generating the OpenAPI spec.
To Reproduce
Here is a full example:
package main

import (
	"context"
	"net/http"
	"net/netip"

	"github.com/swaggest/rest/web"
	"github.com/swaggest/swgui/v4emb"
	"github.com/swaggest/usecase"
)

type Prefix struct {
	ID     uint64       `json:"id" readonly:"yes"`
	Name   string       `json:"name" required:"true" example:"My Name" description:"Some human-readable name"`
	Owner  string       `json:"owner"<EMAIL_ADDRESS>format:"idn-email"`
	Prefix netip.Prefix `json:"prefix" required:"true" example:"<IP_ADDRESS>/24" description:"Prefix in CIDR notation" format:"cidr"`
}

func getPrefixes() usecase.Interactor {
	u := usecase.NewInteractor(func(ctx context.Context, _ struct{}, output *[]Prefix) error {
		*output = append(*output, Prefix{
			ID:     1,
			Name:   "Example name",
			Owner<EMAIL_ADDRESS>			Prefix: netip.MustParsePrefix("<IP_ADDRESS>/8"),
		})
		return nil
	})
	return u
}

func main() {
	service := web.DefaultService()

	service.Get("/prefixes", getPrefixes())
	service.Docs("/docs", v4emb.New)

	if err := http.ListenAndServe("localhost:8080", service); err != nil {
		panic(err)
	}
}

When looking at the schema returned by http://localhost:8080/docs/openapi.json I see:
{
  "…",
  "components": {
    "schemas": {
      "NetipPrefix": {
        "type": "string"
      },
      "Prefix": {
        "required": [
          "name",
          "prefix"
        ],
        "type": "object",
        "properties": {
          "id": {
            "minimum": 0,
            "type": "integer"
          },
          "name": {
            "type": "string",
            "description": "Some human-readable name",
            "example": "My Name"
          },
          "owner": {
            "type": "string",
            "format": "idn-email",
            "example"<EMAIL_ADDRESS>          },
          "prefix": {
            "$ref": "#/components/schemas/NetipPrefix"
          }
        }
      }
    }
  }
}

Expected behaviour
I expected to see my example, description and format tags represented in the schema output.
I also didn't expect that the netip.Prefix would be represented as
"NetipPrefix": {
  "type": "string"
}

but that's just an implementation detail I guess.
My preferred output would be to have the prefix field documented as
"prefix": {
  "type": "string",
  "format": "cidr",
  "description": "Prefix in CIDR notation",
  "example"<EMAIL_ADDRESS>}

This is a somewhat tricky issue.
Explanation of current behavior:

netip.Prefix is a named type, that's why it is expressed as reference.
JSON schema (as of draft 4 that is used in OpenAPI 3.0) ignores any keywords adjacent to $ref, that's why there are no format and other fields in "prefix": {"$ref": "#/components/schemas/NetipPrefix"}.
netip.Prefix is expressed as {"type":"string"} because it implements TextMarshaler.

And here is the problem.
Struct fields can't go into referenced schema, because potentially there can be multiple conflicting definitions, e.g.
type Prefix struct {
	Prefix1 netip.Prefix `json:"prefix1" required:"true" example:"<IP_ADDRESS>/24" description:"Prefix in CIDR notation" format:"cidr"`
	Prefix2 netip.Prefix `json:"prefix2" required:"true" example:"foo" description:"bar" format:"baz"`
}

The schema could be inlined (without a $ref), but that is also not the best general solution because it

may lead to duplications,
will not work for cyclic schemas.

A "clean" general solution might be leveraging allOf to combine both $ref and struct field keywords, but it also leads to extra complexity in schema.
A current approach (workaround) to handle such case is to declare centralized schema for a 3rd-party named type (instead of struct tags), like here.
	// Create custom schema mapping for 3rd party type.
	uuidDef := jsonschema.Schema{}
	uuidDef.AddType(jsonschema.String)
	uuidDef.WithFormat("uuid")
	uuidDef.WithExamples("248df4b7-aa70-47b8-a036-33ac447e668d")
	s.OpenAPICollector.Reflector().AddTypeMapping(uuid.UUID{}, uuidDef)

For this particular case, I think we can introduce a special case to not use $ref (always inline) for named types that have trivial schema (type only, e.g. {"type":"string"}).

Thanks for looking into this! I like the simplicity of not creating a named type for just {"type":"string"}. To me that also makes the spec easier to read.


where is the leaf style ?

hi @chitezh , thanks for your great work.
is there styles for the leaf.gif ?

leaf.gif is a shot from a past project. I may not be able to share the code with you but I could guide you through specific parts. Holla<EMAIL_ADDRESS>

thank you sir, i send a mail to your gmail. best regards.


Create standalone vue components of the request builder.

Is your feature request related to a problem? Please describe.
I'm trying to integrate postwoman in a website i'm building. The website allows users to create a request and use it for later. Part of the functionality is building the request, for which i'd like to integrate postwoman (and save the built request in localStorage or something like that.
Describe the solution you'd like
A vue component that can be embedded into my vue site. e.g, point to it with a route with vue-router, and binding a value to the built request with v-model.
Describe alternatives you've considered
Until now i'm building something similar, but i feel like this would be an easier approach.

Possible duplicate of #384

Please consider contributing to the project for resolving this issue 🙌🏼

Hmm now that i read that issue again it seems we want similar things. I'll hook into that thread and try to contribute


Sort command palette items alphabetically

Is your feature request related to a problem? Please describe.
Being new to Zed, the command palette is a handy way of browsing through features and keyboard shortcuts.
Describe the solution you'd like
It isn't very clear how all the commands are sorted, but it would be much easier to go through the list if all commands were sorted alphabetically, specially since they're already grouped by categories: editor, vim, workspace, etc.

I actually assumed we would eventually want to rank these based on where you are/what actions you use. I guess in the short term alpha ordering would be an improvement though.

It would also be nice to have an option to sort commands by recency.


Tier Badges #96

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves: #96
Summary:

update auro design token to provide new color for
lounge, lounge+, mvp, and mvp gold badges.
add example of tier badges on docs
also update other dependencies
except eslint and markdown magic

Type of change:
Please delete options that are not relevant.

[x] New capability
[ ] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

:tada: This PR is included in version 2.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Sector/more fixes

This contains fixes and improvements discussed in #2, such as making getEntityPool return an Optional, and adding moveToPool.
There are also some other small updates, such as renaming methods and adding more documentation.
Along with adding moveToPool, I updated setScope to automatically transfer the entities to the correct pool. It is worth noting that due to module permissions (of the Entity.Scope enum in EntityData) this can't currently be used in module code. I imagine modules will want to use it, so either changing the permissions on the enum (or moving it to somewhere else) (I haven't looked into module permissions, so I'm not sure what this involves), or implementing different methods (e.g.setGlobalScope(), setSectorScope()), is probably worthwhile.
I've also added tests for these new methods, which helped find some initial bugs (e.g. initially, the ref was destroyed, and you had to get a new ref with the id, but now the ref stays pointing to the entity). The setup code for BaseEntityRefTest was mostly copied from PojoEntityManagerTest. I'm not sure if this is the best way to do things, and it's possible that bits of it can be cut or changed to better suit this class' needs, but the testing works fine.

Merged in https://github.com/MovingBlocks/Terasology/pull/3009


Support retina mode

Hello, I made some changes to support simulating retina mode (note: If geoserver supports retina @2 tiles then it it advised to use them instead of simulating).
It won't detect if device supports retina because I don't want force user to use Material app because of MediaQuery.of(context).
However it is documented how to use it:
  /// If `true`, it will request four tiles of half the specified size and a
  /// bigger zoom level in place of one to utilize the high resolution.
  ///
  /// If `true` then MapOptions's `maxZoom` should be `maxZoom - 1` since retinaMode
  /// just simulates retina display by playing with `zoomOffset`.
  /// If geoserver supports retina `@2` tiles then it it advised to use them
  /// instead of simulating it (use {r} in the [urlTemplate])
  ///
  /// It is advised to use retinaMode if display supports it, write code like this:
  /// TileLayerOptions(
  ///     retinaMode: true && MediaQuery.of(context).devicePixelRatio > 1.0,
  /// ),
  final bool retinaMode;

Moreover if retina is enabled then MapOptions's  maxZoom should be maxZoom - 1, currently MapState doesn't detect any maxZoom based on Layers like Leaflet (If not specified and at least one GridLayer or TileLayer is in the map, the highest of their maxZoom options will be used instead.).

Note: this PR needs #584 so merge this only when it is accepted.
closes #212

@maRci002 @HugoHeneault I compared rendering quality of this Flutter lib to the native osmdroid lib a few weeks.
The map looked better and more crisp on osmdroid (same bounding box). Is this related to this density fix?

#584 updated so I merged that into this to avoid conflicts whenever they got approved.


Remove unused abstraction

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

Comparison is base (9c4889a) 100.00% compared to head (965a6ce) 100.00%.

Additional details and impacted files
@@             Coverage Diff             @@
##                main       #23   +/-   ##
===========================================
  Coverage     100.00%   100.00%
+ Complexity        97        96    -1
===========================================
  Files             11        11
  Lines            238       235    -3
===========================================
- Hits             238       235    -3

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


Traduire la section "Abstract Factory et Builder"

French : J'effectuerais la traduction de ces deux sections.
English : I would translate those two sections.

Thanks a lot for your contributions !

I started translating the two sections.
It would be judicious to create a label "in progress".

Both sections are completed.

#6 merged


[FLINK-16135][core] Unify the TemporaryClassLoaderContext and AutoContextClassLoader

What is the purpose of the change
These two classes do basically same thing, this PR unifies the use to a consolidated implementation.
The consolidated implementation

Resides in org.apache.flink.util (not in the plugins sub-package) because it is intended as a general util
Is called TemporaryClassLoaderContext (better name)
Uses TemporaryClassLoaderContext.of(classLoader) pattern from the AutoContextClassLoader. This pattern is more in line with the "don't do work in the constructor" coding guide. This also makes it more future-proof, in case we need to do extended handling in the future for specific classloaders (child-first, plugins) or more elaborate handling of thread local variables, etc.

Will change the @Public to @Internal for now and merge this, unless there are further objections.


change the job title

in the add new user form please change the( job title) to (Role)

Should be done


device: Introduce reference to parent device name.

This PR introduces a pointer to parent device name in
the device_config structure. Such reference provides generic
method to extract device hierarchy.
Also, the DEVICE_* macros used to create device instances
are updated in order to add new "parent_name" parameter.
Please note, that this PR only modifies data structures.
API for traversing the hierarchy as well as DT integration will follow.

This is going to break a lot of out-of-tree subsystems. Isn't there a way to make this optional?

It lacks of any explanation why it's being done. What is the reason for this?

This is going to break a lot of out-of-tree subsystems. Isn't there a way to make this optional?

Not really. Our current device registration model requires manual mapping of DT_* and CONFIG_* macros to arguments of the DEVICE_* macros. If our transition to device tree was complete and the DEVICE_* macros itself extracted all the parameters from DT_* definitions (basing on the label for example), the transparency would be possible.
The optionality is another problem. For real device-level power management we have to be able traverse the device tree. If we allow for optionality we will get out-of-tree devices (and multiple tress), we will end with more complex data structure and algorithms to manage devices.

@tbursztyka, @aescolar: Yes. We have to have device hierarchy in order to track device usage counts for power management.
Please also note, that thus commit only adds the new field to the device_config data structure and DEVICE_* macros. Replacing NULLs to meaningful values will follow.

CC @mped-oticon @kapedev @hersp

Please note, that this PR only modifies data structures.

not really. DEVICE_INIT and friends are APIs, so you are breaking an existing API.

I wonder if that should not wait for device instance auto-generation via DT.
The switch will be easier, and there won't be the problem of obsoleting the macros.

@nashif: Yes. DEVICE_* API is modified. My point was that there is no consumer of the introduced field yet.

I wonder if that should not wait for device instance auto-generation via DT.
The switch will be easier, and there won't be the problem of obsoleting the macros.

That is true. However it looks that the power management is something we need now...

@pizi-nordic could you add this explanation into your commit message?

Yes. Will be fixed.

Codecov Report

Merging #13129 into master will not change coverage.
The diff coverage is n/a.

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

@pizi-nordic, I see interest in this but can you can you provide the big picture on why you're intrudocing this? and what it intents to solve?

I see interest in this but can you can you provide the big picture on why you're introducing this? and what it intents to solve?

Major driver of this changes is https://github.com/zephyrproject-rtos/zephyr/issues/14309.
We can also use this information for better clock control (see https://github.com/zephyrproject-rtos/zephyr/pull/15585). For example the USB driver could request a 48MHz clock from its clock provider and the clock provider could adjust clocking tree in order to fulfil the request.


[DataStore] Implement mutations in batches or upload data in the background

Is your feature request related to a problem? Please describe.
Users open our app once or twice a day. On app startup we fetch data from physical device and save it in DataStore. For each day we may have ~2000 rows to save. We observe that DataStore send mutation queries for each row one by one and only when app is the foreground. Each mutation takes 300-800ms so to send all data to backend we have to keep app open for almost 20 minutes while our user have the app open for a few minutes only. In result we don't have a recent data on the backend and not synced data grows on mobile device.
Describe the solution you'd like
If Amplify SDK send mutation queries in batches (let's say 50 rows per request) then uploading ~2000 rows will be significantly faster and it will solve our issue.
Describe alternatives you've considered
Alternatively, if Amplify SDK let us to upload data when app is in the background it will also solve our issue. Our app keeps BLE connection with external device so it's active in the background for many minutes per day - enough to send all ~2000 rows.
Is the feature request related to any of the existing Amplify categories?
DataStore
Additional context
No response

Thank you for raising the feature request. Our team will prioritize it and will post an update on the issue once we have more information.

Hi @lawmicha any update on this? we're seeing https://github.com/aws-amplify/amplify-swift/issues/3437 a lot too so we would be very interested in this feature

@lawmicha I am experimenting with BackgroundTasks on iOS in order to trigger DataStore syncing to cloud and have a question.
I am trying a naive approach that will "simply" call DataStore.stop() followed by DataStore.start() methods and will observe outboxStatus event until it reaches empty: true state.
So far I have observed that I am able to call start/stop methods but I am unable to receive outbox events. Is there any code in DataStore which might prevent it running when app is in background state?

Hi @fzy-spyro, there isn't anything in DataStore that I'm aware of that depends on the background/foreground state of the app. I wonder what the start sequence logs look like when you call start() from the background task, perhaps it's not emitting the event because it didn't sync the mutation? Do you see any other events emitted? the events are sent through the Hub category in Amplify.

@madej10 / @kubatatami  DataStore currently does not have any special implementation that checks the app states to see whether it's in foreground or background, I think the path forward in this feature request are one or a combination of:

DataStore to own the implementations of the background tasks that will execute in the background. This may or may not be opt-in, such that the developers may have to enable background mode of some sort for DataStore to utilize this behavior.

DataStore to provide APIs which are to be called during background task execution, the developer writes the background tasks and as part of the code, call into something like DataStore.performBackgroundSync() , where the API is a slim down version of the DataStore sync sequence (probably wouldn't have to estasblish the subscriptions for example).

A note about batching, DataStore calls AppSync APIs create/update/delete, so batching may be difficult because the AppSync API to perform batch mutations simply doesn't exist. If AppSync does provide a batch API, we may be able to reconcile the entire pages pretty quickly, as we do with the full/delta sync response which is also a page of model data.


Prevent fast scroll (ALT + mouse scroll) from triggering menu bar mnemonics

Type: Bug
Steps to Reproduce:

"Move into New Window" any open file/tab
With focus on the new window, fast scroll using ALT + mouse scroll

Expected Result:
Focus doesn't leave current window when releasing ALT key, nor are the main window menustrip item mnemonics triggered.
Actual Result:
Main window's menustrip gains focus and the menustrip is waiting for an ALT+key mnemonic key combo.
VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.19045
Modes:

@bpasero This is interesting, I did not know that the aux window toggles the menu in the main window. But also, this behavior only reproduces in the aux window.

I think this needs more feedback from others, its also the first time its reported. Removing Alt from going to the main menu could be seen as a accessibility regression. Maybe we can detect that the user is scrolling, but would need investigation.


deposit form: re-enable language field in additional titles/descriptions

Blocked as of 2021-04-23
This task requires:

changing react-invenio-deposit to save additional_titles[].lang = {id: <suggest id>} (same for additional description)
changing invenio-rdm-records to have the schema accept this change and the data layer relations field to dereference the localized language correctly -- :warning: this step is the blocker because the structure: id of attribute (lang) of array element for field (additional_titles) is not supported right now
changing invenio-app-rdm to display the human readable localized language (invenio_app_rdm/records_ui/templates/semantic-ui/invenio_app_rdm/records/macros/detail.html)

Draft WIP PRs have been made in those repos but they should not be merged.

blocked
For https://<IP_ADDRESS>:5000/api/vocabularies/languages?q=engl&size=20, the languages endpoint is returning:
{
  "hits": {
    "hits": [],
    "total": 0
  },
  "sortBy": "bestmatch",
  "aggregations": {},
  "links": {"self": "https://<IP_ADDRESS>:5000/api/vocabularies/languages/?page=1&q=engl&size=20&sort=bestmatch"}}

(notice that the links.self has a typo too making the link invalid)
Environment:

http://localhost:9200/vocabularies-vocabulary-v1.0.0-1619035738/_search returns language hits though e.g.

{

    "_index": "vocabularies-vocabulary-v1.0.0-1619035738",
    "_type": "_doc",
    "_id": "1d604d93-3794-4117-85c2-9c83894e4510",
    "_score": 1.0,
    "_source": {
        "$schema": "local://vocabularies/vocabulary-v1.0.0.json",
        "type": {
            "id": "languages",
            "pid_type": "lng"
        },
        "tags": [
            "individual",
            "living"
        ],
        "title": {
            "en": "Armenian Sign Language"
        },
        "id": "aen",
        "pid": {
            "pk": 100,
            "pid_type": "lng",
            "status": "R",
            "obj_type": "rec"
        },
        "uuid": "1d604d93-3794-4117-85c2-9c83894e4510",
        "version_id": 2,
        "created": "2021-04-21T20:09:14.946286+00:00",
        "updated": "2021-04-21T20:09:14.966377+00:00"
    }

},

invenio-vocabularies master
invenio-app-rdm master
invenio-records             1.5.0a4
invenio-records-resources   0.14.8

What could be causing this?

Note, you have to use suggest instead of q now for auto-complete use cases:
https://<IP_ADDRESS>:5000/api/vocabularies/languages?suggest=engl&size=20

closed via https://github.com/inveniosoftware/invenio-app-rdm/pull/927 + https://github.com/inveniosoftware/invenio-app-rdm/pull/924


Fastboot enabled ember app's session cookie is not populated correctly in Safari

Hi,
I am using this commit as my ember-simple-auth to get a jumpstart on the fastboot compat feature and also to test it out and report any issues found:
"git://github.com/simplabs/ember-simple-auth.git#2d49133ec8543ae53af713d7551072ba49f65ce7"
I realized that the session cookie is not populated as expected in Safari so it causes a redirect back to login after the promise resolves in my custom authenticator.  the cookie in Safari looks like this:
name: ember_simple_auth-session
value: %7B%22authenticated%22%3A%7B%7D%7D
the same app running on chrome has the following as the cookie and the session is authenticated (user is able to login) as expected:
name: ember_simple_auth-session
value: %7B%22authenticated%22%3A%7B%22authenticator%22%3A%22authenticator%3Acustom-authenticator%22%2C%22result%22%3A%7B%22user%22%3A%7B%22userId%22%3A%22custom%3Ausername12122323%40gmail.com%22%7D%2C%22authenticationToken%22%3A%22eyJ0e46bWljcm9zb2Z0OndpbmRvd3MtYXp1cmU6enVtbyIsImF1ZCI6InVybjptaWNyb3NvZnQ6d2luZG93cy1henVyZTp6dW1vIiwibmXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJ1cmJmIjoxNDY5OTg4OTI1LCJleHAiOjE0NzI1ODA5MjUsInVybjptaWNyb3NvZnQ6Y3JlZGVudGlhbHMiOiJ7fSIsInVpZCI6ImN1c3RvbTp0dXJndXRhQGdtYWlsLmNvbSIsInZlciI6IjIifQ.wyrzaZE0P8rVQgUabfaaZE-884Q5LtZnlydUjCXL7i8%22%7D%7D%7D
Let me know if you need more info.
Thanks!

This was due to my own bug.  Sorry


Negative sampling / candidate sampling with Keras API

Please make sure that this is a feature request. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:feature_template
System information

TensorFlow version (you are using): 2.0
Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state.
It looks like TF Keras has no built in functions to do candidate sampling like in TF 1.0. As far as I can tell, the official keras word2vec example doesn't have negative sampling https://www.tensorflow.org/tutorials/text/word_embeddings even though it's an integral part for producing quality word embeddings.
Will this change the current api? How?
The original tensorflow losses had options for negative sampling, including different distributions to select from. So perhaps some new loss functions and candidate sampling options will need to be added.
Who will benefit with this feature?
Anyone who is training embedding models.

@Santosh-Gupta What do you mean by "The original tensorflow losses had options for negative sampling, including different distributions to select from" whereas TF2 doesn't have it?

Closing this. If the above article doesn't help you, let us know!


added new favicon

Requesting a pull for favicon and main page logo:  #22 .
I have concerns with the resolution of the logo - and the fact I am not an artist. :P

Let's fix the resolution.
Try using this (created from svg version):

I like the direction you're taking it with the orange whale. The container does not need to be detailed - a simple black square might look good.

@mkasberg That is way better!  I did not know there was a higher res version.  I'll rework it.  Thanks!


fix: Add  comment

Add <auto-generated /> comment
Description
Adds an // <auto-generated /> comment at the top of all generated output. This further informs tooling of the auto-generated nature of this source.
Fixes # 494
Checklist

[x] The existing code style is followed
[x] The commit message follows our guidelines
[x] Performed a self-review of my code
[x] Hard-to-understand areas of my code are commented
[x] The documentation is updated (as applicable)
[x] Unit tests are added/updated
[x] Integration tests are added/updated (as applicable, especially if feature/bug depends on roslyn or framework version in use)

Note I added this as fix but not sure that feels exactly right. It is changing the output and it can result in tooling behaving different (by no longer producing compiler warnings in some cases for the generated code), so I wasn't exactly sure. Could be chore potentially instead.

Ok I think I've got all the snapshots updated now. 🤞


feat: support plugin options for templete

What type of PR is this?

/kind feature
What does this PR do?

Which issue(s) does this PR fix?

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

cherry-pick to main

/lgtm
/approve


New Component: CopyBox

Describe what feature you'd like. Pseudo-code, mockups, or screenshots of similar solutions are encouraged!
The idea for this is essentially a component similar to the CodeBlock component, or modifying that component to be more versatile.
The use case would be when wanting to make it easy for a user to copy text content that isn't code, such as API credentials, share url, webhook urls etc.
Features:

Display text content.
Show/hide text button (optional - useful for credentials).
Optional auto-copy if the text is clicked and/or copy button like what CodeBlock has.

What type of pull request would this be?
None
Any links to similar examples or other references we should review?
No response

Have you looked into our Clipboard action?
https://www.skeleton.dev/actions/clipboard
This is actually what we use internally for the CodeBlocks


Migrate from python-poetry to setuptools

Title is self explanatory. Poetry is becoming a pain to deal with so before caching or std product generation can be added there need to be a migration to setuptools.

Addressed in #56


Wireguard Clients stopped connecting since last docker update

Hi
I had client connecting to my docker wireguard server just fine until recently. I looked at the server settings and noticed a "Pre Down Script" field that was never there before. Do i need to put anything in there? If so do i need to recreate my client connections?
I know all my ports are forwarded just fine but for the life of me i cant figure out why my clients wont communicate properly. Heres a rundown of what happens when a client connects, it shows 0 RX packets transmitted but there is a flow of TX packets so it looks like it is connecting or trying to connect but not communicating properly. If anyone can help that would be great. Cheers.

Same problem with our installation.
Client connection not possible, WireGuard-ui status shows no clients.
docker Log:
[#] iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o ens6 -j MASQUERADE /usr/bin/wg-quick: line 295: iptables: command not found [#] ip link delete dev wg0

I have just tested the latest image built from commit 45849a2. It works fine for me.
@jkksanders No, you don't need to configure the Pre Down Script field if you don't need it. Please try to debug from the shell to see what is current status of your WireGuard server is. Like, the output of the wg command or systemctl status<EMAIL_ADDRESS>@karbrueggen1 do you have iptables command available on your host machine? Usually, it is in /usr/sbin/iptables. Please make sure it is available in the PATH environment variable of the user who runs the Wireguard server. You can try to use the absolute path of iptables command as well.

Hi, yes iptables is available on the host system.
Also tried to run the container as root, but got the same error.
I'm using the system compose file btw.

What does the Pre Down Script do?
Btw i'm running all of this in portainer, i've checked logs in both wireguard and wireguard ui and nothing out of the ordinary has popped up.
I've updated my PATH but still no further forward
/usr/sbin/iptables:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Not sure what else to check

Ah just checked and i have this error...
[#] iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
/usr/bin/wg-quick: line 295: iptables: command not found

Ok i reverted the PATH to the original on Wireguard UI and changed the PATH on the Wireguard Server to include the mentioned iptables directory and i'm getting no errors in my logs so thats a plus but when my clients connect im still getting 0 RX and multiple bytes in the TX and the clients are issued an ip address but theres no full communication and i cannot access resources on my network

What does the Pre Down Script do?
It do nothing if you leave it empty. It's my PR #480

The problem in something else a lot of commits was added last 2 weeks..

What does the Pre Down Script do?

It do nothing if you leave it empty. It's my PR #480
The problem in something else a lot of commits was added last 2 weeks..

Ah gotcha ok so nothing to worry about there. I've noticed some people seemed to have reverted back to a previous version of wire guard and wire guard ui as a work around. Is this a true work around?
Cheers

Huzzah!!!
Work around reverted back to wireguard UI version 0.5.2. This version seems to work better than the latest. Not sure whats changed. but it seems to be a bug.
I'll keep running this version until its fixed. Thank you all for you time and happy new year
Cheers

can confirm I had exacttly the same issue. Reverting to the previous image fixed things again

Same problem. PATH is set correctly but somehow iptables is not found. I played around a bit and it seems that the container is nearly ignoring PATH.

@karbrueggen1 do you have iptables command available on your host machine? Usually, it is in /usr/sbin/iptables. Please make sure it is available in the PATH environment variable of the user who runs the Wireguard server. You can try to use the absolute path of iptables command as well.

Hello @ngoduykhanh
The problem is that you need to have the iptables within the image.
Please change the Dockerfile:
change line: RUN apk --no-cache add ca-certificates wireguard-tools jq
to: RUN apk --no-cache add ca-certificates wireguard-tools jq iptables
This should do the trick. Apparently, the latest alpine does not have the iptables within; or it was build before with those, but not anymore.

confirmed as the solution. alpine 3.19 lacks iptables, while 3.16 includes it.

Thanks guys, I added iptables package in PR https://github.com/ngoduykhanh/wireguard-ui/pull/520. Please try the latest image again if it still has an issue with missing iptables

Thanks guys, I added iptables package in PR #520. Please try the latest image again if it still has an issue with missing iptables

tested and solved


add set-weights plugin

Hello! This is a CF CLI plugin to use the weighted routing feature for the Istio routing tier, developed by the CF Networking Team.
https://github.com/tstannard/set-weights-plugin
Thanks!
CF Networking Program
[#164789272]

Thank you @jeffpak!


Identical selectors can be returned as distinct strings

The Issue
At the moment, the web-vitals attribution builds can return distinct selector strings for elements that have semantically identical selectors. For example, in the image below, you’ll see two selectors that are identical in the abstract/query sense, but distinct as strings:

A Proposal
In the construction of the selector string, sort the element class names before joining them. This sorting would ensure that the selectors reported above are consolidated and identical. The drawback is that the as-is order of classes could (in theory) help a developer delineate between elements that have the exact same classes but in a different order, but my guess is that that drawback is outweighed by the benefit of cleaner selector aggregation.

Here it is, I think?
Seems easy enough to take a stab, and honestly might be improved in a few other ways.  Do you think this is something you would be interesting in submitting a PR for?

Do you think this is something you would be interesting in submitting a PR for?

Yeah, I'm happy to. I've noticed that the repo leans heavily into webdriver tests. You cool with unit tests for getSelector, or should I alter/augment some webdriver assertions?

I'm not necessarily opposed to changing this, though I do want to point out that any change to the selector generation logic would mess up people's existing reports. E.g. the situation that @vanderhoop is describing in his screenshot would start happening to everyone using the attribution build of this library whose HTML classes are not already in alphabetical order.
So this is something we'd want to run by RUM providers using the library to make sure they'd be OK with, and it would also need to be released with a major version bump (since it's a breaking change, for the reason I just mentioned).

I do want to point out that any change to the selector generation logic would mess up people's existing reports. E.g. the situation that @vanderhoop is describing in his screenshot would start happening to everyone using the attribution build of this library whose HTML classes are not already in alphabetical order... ...so this is something we'd want to run by RUM providers using the library to make sure they'd be OK with

That's a great callout, and should be weighed against the existing selector inconsistency that library consumers are currently subject to. The optimistic view (that others might not share) is that this change in the selector data coming over the wire would end up causing a diff between the aggregated selectors in navigations ingested before/after upgrade, but that diff would be flushed within months for the common RUM use cases. Maybe @ErwinHofmanRV has thoughts, as I believe he's leveraging web-vitals under the hood?

it would also need to be released with a major version bump (since it's a breaking change, for the reason I just mentioned).

I don't see this change necessitating a new SEMVER major, as none of the APIs are changing, nor is the overall semantic structure of the returned result. T
One option (which I don't love, but which scratches all the itches) is to make this sorting functionality opt-in. getSelector already has an optional maxLen(th) arg, though it doesn't actually appear to be leveraged in the current lib.

make this sorting functionality opt-in

Although adding flags for everything can be a sign of poor design, I think this is a reasonable path forward.  Default disabled in current version, default enabled in next version.
The opt-out could be a perf benefit for any provider that prefers to do it server-side.

+1 for sorting/'uniqueifying' selectors
In general, the amount of distinct results/selectors would reduce. And the appearances/events-rate of selectors would improve, making it easier to grasp which with selector users should continue debugging in DevTools.
I do agree that sites that would be doing periodic comparisons (either manually or via alerts) might see a weird change in this number and might suddenly receive notifications if alerts were configured for the selector-dimension.
But that will be phased out over time and all for the benefit of RUM users I would say.
So based on the way we use this selector data (basically the same as shown in the screenshot as provided by @vanderhoop ), I don't see a risk in a sudden change.


Is there any documentation for how to wire up Ampersand views to work with Marionette?

I'm using webpack and I'm wondering how to wire up Marionette to use Ampersand views instead of Backbone for CommonJS.  Is there any documentation or examples for this?

hey @dschissler, if I read your question right, are you asking to have Marionette use AmpersandView as the view it extends from, instead of Backbone.View?  I don't believe that would be possible without some javascript ninja stuff via playing with the prototype chain, or alternatively forking Marionette and changing what their views extend from.
It is possible to use Ampersand and Marionette together though, I've been doing it for the past year.  The view's all have a similar api (render, remove) so you can render a marionette view as an ampersand subview or have marionette regions show ampersand views.


show song title on different discord server

i only see playing music 2 of the server
something like that
hope theres a way to show it different songs on both servers
lets say i prevail scars on server 1
and 2nd is o2jam v3
any idea?

I don't think this is possible, since accounts can only have one playing status at a time.

that wouldn't be possible, but you can set up a custom status by doing this: https://github.com/Just-Some-Bots/MusicBot/pull/227/files


Source code is recognized as Binary

Hello,
I have several files generated by VS2015. They are recognized as binary on github so that I couldn't follow their commit history. The file does contain Chinese in comment and when I run git diff upon it, I got sth like:
^@c^@o^@u^@t^@ ^@<^@<^@ ^@
The legal characters are separated with illegal one, which is pretty strange.
I have attached one of them. Can anyone help me to make its commit history readable?
Thanks!
LLSIF_VirtualPlayerDlg.h.txt

The file is misencoded, probably as a result of a failed character-set conversion.
It's being detected as binary because there are null-bytes between each character.

@Alhadis Thank you! Then I can simply remove the null-bytes by copying and pasting. One more thing, may I ask is it possible for github to show a readable commit history for such binary files?

No, it isn't.
You can explicitly tell Git the file isn't binary by using a .gitattributes file:
./relative-path-to-file.txt text

However, this doesn't work on GitHub: only when running Git client-side.

@Alhadis  Okay thank you so much!


Conflict with the Click Listener of Google Tag Manager

Hi,
The Colorbox does not work anymore on 2 Colorbox-enabled websites after Google Tag Manager (V2) was deployed on these websites.
If you click on a Colorbox enabled anchor link then the image-url is opened in the browser tab/window, so only the image is shown. The normal behaviour is that the Colorbox overlay is displayed and the clicked image is shown in the overlay.
Scenario:

Open http://www.feestdagen-belgie.be/agenda-toevoegen-outlook-com/
Goto the section with the screenshots (the one with a thumbnail and some short  links below it).
Click on the thumbnail, or an anchor just below the thumbnail.  Screenshot: https://dl.dropboxusercontent.com/u/5629939/temp/capture_20150715_213214.jpg
The image opens very briefly in the Colorbox overlay but... 0.5 seconds later the image-url is opened "full screen" in the browser. Expected result: open the image in the colorbox overlay, stay there and wait for user interaction.  Screenshot: https://dl.dropboxusercontent.com/u/5629939/temp/capture_20150715_213217.jpg
Note the warning in DevTools console: Resource interpreted as Document but transferred with MIME type image/jpeg (I'm sure the http headers of the image are correct though).
If you do not see the problem then please open the webpage once more, or clear the browser cache and try again.

System:
Google Chrome and IE (latest versions) on Windows 7. Firefox works fine consistently.
Colorbox init code:
jQuery(document).ready(function($){
    $("a.mjd-colorbox").colorbox({
        current: "{current} van {total}",
        maxHeight: "95%",
        maxWidth: "95%",
        rel: "mjd-colorbox"
    });
});

Notes:

FYI: GTM is used for example to configure the Google Analytics tracking script, to track anchor clicks for analysis, some conversion pixels, etc.
I can see in Chrome DevTools that 2 click listeners exist (one of Colorbox and one of GTM).
Unfortunately the behavior is not consistent. It works fine 5-10% of the times you open a webpage with some Colorbox logic in it. It is probably a timing related problem which is impossible for me to sort out.
I have tested it as well with a GTM version where all GTM Click Listener logic was removed (https://support.google.com/tagmanager/answer/3415369?hl=en#LinkClickListener) and that works fine (but this is of course not a final solution as the click data is neede for website analysis). This specific test was done on the dev website which is not publicly available (i might give jackmoore access if needed).

Thanks for your time.

Thanks for opening a ticket, but I don't see how this is a bug with Colorbox - it could be anything that's causing an error which would prevent Colorbox from working properly.  There isn't a way I can safeguard against other scripts introducing errors, if that's the case.
You got a lot going on here so I don't plan on getting into debugging something that is specific to a single site. My recommendation is to create a minimal demonstration of the problem with only the scripts required to reproduce the issue.

Thanks for the follow-up. I did not say it is a bug in Colorbox. Note I already did quite some investigation. But it is somehow a conflict between these 2 components and I'm trying to fix it.
I can try to make a small mini website with a standard GTM tag (with a link click listener inside, no special logic added inside the GTM container) and some Colorbox things in there. Assuming the same things happen, would that be interesting for you (and me) to have look at?

Hi,
I have followed your advice and made a small reproducible case. All irrelevant things have been stripped.
If you click on a Colorbox enabled anchor link when the page is in the cache then the image-url is opened in the browser tab/window, so only the image is shown. The normal behaviour is that the Colorbox overlay is displayed and the clicked image is shown in it.
System:
Google Chrome evergreen on Windows 7.
Scenario:

Open an incognito window in Google Chrome.

Open http://www.feestdagen-belgie.be/tmp90210/tmp-20150716/cb.php

Save it as a bookmark.

Try the colorbox anchors and they will work fine. Screenshot: https://dl.dropboxusercontent.com/u/5629939/temp/capture_20150716_180228.jpg

Open the bookmark, e.g. open the page again. PS Do not reload/refresh the page because then the things are not taken from the browser cache and it will work fine.

Click on one of the colorbox anchors.

The image opens very briefly in the Colorbox overlay but... very quickly the image-url is opened "full screen" in the browser. Screenshot: https://dl.dropboxusercontent.com/u/5629939/temp/capture_20150716_180257.jpg

Remarks:

If you disable the cache in Chrome DevTools -> Network Tab then it works correctly.
Problem occurs in Google Chrome and IE (latest versions) on Windows 7. Firefox works fine.
The DevTools console reports this but I do not know it is related (I'm sure the http headers of the image are correct though): "Resource interpreted as Document but transferred with MIME type image/jpeg"

Thanks for your time.

I am having a similar issue on a drupal site with colorbox and Google Tag Manager.
Removing Google Tag Manager resolved the issue. The issue only appeared for me using Chrome.
Clicking on the image the for first time, after a F5 cache flush, the image would not load in colorbox. It would just display the image.  Pressing the back button (closing the image)  and clicking on the image a second time,  the image would load in color box. If I had a devel tools window open and clicked on the image after a cache flush the image would load in colorbox. Close the devel tools window and the issue resurfaced. -- weird behavior.

Thanks for knowing I'm not the only person seeing this issue. I have not found a solution since I reported it.

Having the same problem with GTM and fancybox as well... It is problem with GoogleTagManager.

I am having the same issue, in my case GoogleTagManager vs. colorbox.
In my case I generate links after requesting a JSON file via AJAX where all information about the links are stored. All other links that are delivered directly with the initial request seem to work fine but as soon as I add content and initialize colorbox for the new links it seems to collide with Google Tag Manager.

@SpikeShape I'm glad it worked for you but for my system is not.

I just tried it on your page. I entered the following using the Developer Tools in Chrome:
jQuery('.mjd-colorbox').on('click', function(event) {
  event.preventDefault();
});

It seemed to work as expected. At least I could open the image and switch between them without leaving the page.
I found an article on a blog describing how the GoogleTagManager works and how it delivers the events: http://www.simoahava.com/gtm-tips/fix-problems-with-gtm-listeners/
I hope that helps.

@SpikeShape okay it works now. thanks!

@SpikeShape Thank you!
Google Tag Manager is not something I have experience with.  Colorbox does do a preventDefault on click event, but it's delegated to the document body in order to minimize the number of event bindings.  I'm guessing by default GTM is intercepting the event before it has a chance to bubble all the way up, leading it to the wrong conclusion about what to do.  Either way your solution looks fine to me.

Hi,
I am having the same issue with colorBox. I have tried with preventDefault() on .on event without success.
I have images array and each photo with .photo tag class
My code is the following and i have tried this
    $(document).ready(function () {
            $(".photo").colorbox(
                {
                    rel: 'galerie-photo',
                    width: '800px',
                    height: '600px',
                    onComplete: function(){
                        var img = document.querySelector('[class*="cboxPhoto"]');
                        wheelzoom(img);
                    }
                }
            ).on('click', function(event) {
                console.log('dans click');
                event.preventDefault();
            });
        });

and
  $(document).ready(function () {
            $(".photo").colorbox(
                {
                    rel: 'galerie-photo',
                    width: '800px',
                    height: '600px',
                    onComplete: function(){
                        var img = document.querySelector('[class*="cboxPhoto"]');
                        wheelzoom(img);
                    }
                }
            });
            $('.photo').on('click', function(event) {
                 event.preventDefault();
             });
        });

2 solutions without success. Where to put .preventDefault() on .on event in code.
Thanks for your help.
Christophe

Hey  @Chrispnv
The code seems to be correct so I assume there is something different like other events handlers. Would you mind delivering some markup or a dumped down jsfiddle?

Thanks for your prompt reponse.
it will be difficult because images are loaded from a database. I'm going to try with simple example on my web space.
What is the best solution between the two I tried. First, .on event directly on colorbox() or second on photo tag class.
I think my problem is the application loading time. In Chrome debugger network tab when application is loaded, colorbox is ok, if not colorbox is ko. Is it possible ? I have tried $(window).load instead of $(document).ready and the application works better with $(window).load
Thanks
Christophe

I was also experiencing a conflict between Google Tag Manager v2 (GTM) and colorbox when loading an html page with the iframe option. I was using the Google Tag Manager and was also trying something somewhat fancy with GTM which was tracking outbound links. The html form page would load but then kick it to expand the whole browser/url. When i added an exclude with regex for my site URL it no longer fired that particular trigger when the colorbox iframe was opened. This may not be the solution for everyone since GTM can be quite complex and it depends on different triggers and variables - but i hope it helps those who use both the wonderful colorbox (Thank you Mr. Moore) and the very powerful Google Tag Manager.

Solved my problem
$('a[data-lightbox]').on('click', function(event) {
           event.preventDefault();
});


fix running tasks when circuit breaker is open

Signed-off-by: Yaliang Wu<EMAIL_ADDRESS>Description
When disk circuit breaker is open, the upload model task will never completed/failed.
The original design of String errorMsg = checkAndAddRunningTask(mlTask, maxUploadTasksPerNode); will never throw exceptions, will throw exception by checking errorMsg. Now circuit breaker will throw limit exceed exception inside checkAndAddRunningTask, so we should move this method inside the try block.
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

CI failed , common issue reported
https://github.com/opensearch-project/OpenSearch/issues/5121


update network client api version for vmss

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

issue for adding test coverage https://github.com/Azure/azure-sdk-for-net/issues/3452

we have added tests for private access. creating an issue for ER

Issue for ER: https://github.com/Azure/azure-sdk-for-net/issues/3456
Also just to be clear, we (vinaya andI) are having environment issues and that is preventing us from checking in tests.


[Morgan][Student][Bug] Redeem records order not correctly

@Morgan-Leon

@jerrywalker0435

@Morgan-Leon what is that mean?

http://localhost:9999/api/students/1/exchanges?page=0&size=10&direction='desc'


SAK-45075 lessons - fix subpage renaming

(cherry picked from commit 935465d8d2a4560fb96ce75e39ef40c74158a9ca)
Please preserve commit authorship

Awesome, thanks Sam!


Better validation on binding settings

This is split from https://github.com/VSpaceCode/VSpaceCode/issues/78 and to track the work to have better error messages when which key binding json is incorrect.

Just jotting notes here. Thinking we can use JSON Schema with https://ajv.js.org. To handle requirements of different requirement of properties on the type name, we can use the if/then/else as described in https://json-schema.org/understanding-json-schema/reference/conditionals.html and https://ajv.js.org/keywords.html#ifthenelse

I've used json schema before. I could write the schema if you want.
Tell me:

the file(s) to be validated
where to place the schema file

Thank you for helping, it would be great if you can help as I am going to be busy in the next few weeks. The schemas are used to validate the bindings and bindingOverrides.
Thebindings contains an array of BindingItem(s).
BindingItem

key
value

key
required string

name
required string

type
required enum string (command, commands, bindings and transient)

command
required string if type == command | (optional if type == transient && only if commands is not exists)

commands
required array of strings if type == commands | (optional if type == transient && only if command is not exists)

args
optional any object | array of objects if type == commands

bindings
Array of BindingItem(s), required if type == bindings

The bindingOverrides contains an array of OverrideBindingItem(s).
OverrideBindingItem

key
value

keys
required (string | array of string)

position
optional number

name
optional string if keys is negative else required

type
optional enum string as in BindingItem if keys is negative else required

command
Same as BindingItem

commands
Same as BindingItem

args
Same as BindingItem

bindings
Same as BindingItem

Can you put the schemas in src/scemas in a new branch? Then I can use the schema to validate finish this out.

Kind of just jotting here. Apparently, we can add the (limited) schema into package.json so there is a prompt of possible value when people edit the settings.json
For example:
"whichkey.bindings": {
    "type": "array",
    "items": {
        "type": "object",
        "title": "Binding",
        "properties": {
            "key": {
                "type": "string",
                "description": "Key of this binding in this level"
            },
            "name": {
                "type": "string",
                "description": "The display name of this binding"
            },
            "type": {
                "type": "string",
                "enum": ["command", "commands", "transient", "conditional"],
                "description": "The type of this binding"
            }
        }
    },
    "markdownDescription": "The bindings of the which key menu",
    "default": []
}

Maybe the hack mentioned in https://github.com/microsoft/vscode/issues/95270#issuecomment-662091151 can bypass the limited functionality. Also maybe be able to reuse across extensions like VSpaceCode and which-key

Kind of just jotting here. Apparently, we can add the (limited) schema into package.json so there is a prompt of possible value when people edit the settings.json
For example:
"whichkey.bindings": {
    "type": "array",
    "items": {
        "type": "object",
        "title": "Binding",
        "properties": {
            "key": {
                "type": "string",
                "description": "Key of this binding in this level"
            },
            "name": {
                "type": "string",
                "description": "The display name of this binding"
            },
            "type": {
                "type": "string",
                "enum": ["command", "commands", "transient", "conditional"],
                "description": "The type of this binding"
            }
        }
    },
    "markdownDescription": "The bindings of the which key menu",
    "default": []
}

Maybe the hack mentioned in https://github.com/microsoft/vscode/issues/95270#issuecomment-662091151 can bypass the limited functionality. Also maybe be able to reuse across extensions like VSpaceCode and which-key


Pipelining parameter sweeping for long-term degradation modelling

Description
This relates to a tool ParaSweeper proposed in this paper, which is mainly about pipelining parameter sweeping for long-term degradation modelling. It aims to generate large amount of long-term degradation modelling data, which can later be used for sensitivity analysis and optimization. It might be a nice feature to add on PyBaMM.
Motivation
I notice there are questions about degradation modelling on PyBaMM Discussions from time to time involving how to fit the model to ageing datasets and deal with multiple errors. This tool ParaSweeper may help a lot on those questions.
There are three useful features of ParaSweeper:

Can be tailored for HPC system
Run and check – always return something and not always assume the simulation runs well (all other tools assume the model runs well)
Tidy up input/outputs

For these reasons, I think it can be a upgrade for the BatchStudy or Degradation experiments with reference performance tests example.
Possible Implementation
ParaSweeper has already been here. But I am happy to re-write it, break into little chunks and do whatever you may thinks that can become more compatible with PyBaMM. Any suggestions will be appreciated.
Additional context
No response

Open to this if it can be sufficiently generalized, but in general the PyBaMM development philosophy should be to be as model-agnostic as possible and work on things that make all models more robust. Opinionated functions that do very specific things for specific models are valuable but should live outside of the main PyBaMM repository.

I am going to close this for now. We can re-open it as a discussion if needed


stable var(), sd(), covar() and corr() calculations with analytic derivatives

From @bob-carpenter on April 12, 2015 2:8
We should write versions of all these functions that are numerically stable and have analytic derivatives:

var(reals) : real
sd(reals) : real
covar(reals,reals) : real
corr(reals,reals) : real

The signatures for reals would allow any of the 1D containe types (real[], vector, or row_vector).
Then we want versions to calculate whole matrices of covariances and correlations, as in:

covar(matrix): matrix
covar(vector[]): matrix
covar(row_vector[]) : matrix
corr(matrix): matrix
corr(vector[]): matrix
corr(row_vector[]): matrix

The signatures taking matrices should go row-wise, taking an N x K matrix to an K x K matrix of results.  These should be careful to only compute values for the below (or above) diagonal elements and reuse them in the final result and to only calculate the variance of each variable once.
It might make sense to have versions that return a triangular matrix of results, but it's not urgent as the copies will be relatively cheap.
The Wikipedia has a nice summary of the problems the naive approaches have with catastrophic cancellation:

Wikipedia: Algorithms for Calculating (Co)Variance

The upshot is that we should be using Welford's algorithm for the calculations.  There's an implementation built into Boost's accumulators:

Boost: Accumulators reference

We just have to be careful to do the (unbiased) sample versions of (co)variance that divide by N-1 and not by N.  And then use those for sd and corr.
Copied from original issue: stan-dev/stan#1423

This is basically duplicative of #75


Add GDScript optional prefix filter for enum exports.

Closes #20988's use-case and (removes the need for) #21014.
(Edit: Also closes #22122 now)
A simple change that will let users optionally define a string constant to filter out of their Inspector's generated enum fields' textual representation.
enum Elements {
    ELEM_NONE,
    ELEM_FIRE,
    ELEM_ICE
}
export(Elements, "ELEM_") var element = ELEM_FIRE
# or...
export(Elements, FLAGS, "ELEM_") var element_combo = ELEM_FIRE | ELEM_ICE

The above code would now display the options as (with the additional edit)...
None
Fire
Ice

rather than...
Elem None:0
Elem Fire:1
Elem Ice:2

The implementation allows the ordering of the FLAGS flag and the string constant to be flexible.

Nice.  Seeing this reminding me that had posted this:  https://github.com/godotengine/godot/issues/22122
It is a little unrelated, but wondering what thoughts you might have on options to hide the enumerated values from the inspector?

I would imagine it might not be too hard. I'll have a look-see and check how to do it. It's probably just a one-liner change.

Cool.  Thanks Will.  X)

We really need to add annotation support...

@avencherus Updated it. Just a few lines of code to change. Removes the value from the hint string, consequently updating the text in the Inspector.

@groud When we do actually add annotations, we should totally make them scriptable to some extent, that way people can use an EditorPlugin to define new annotations! drools XD

Nice nice.  X)  Looking good on my end at least.

Any news on this? The change looks good IMO, but need to fix the issue @neikeq mentioned.

This one should be ready for merging. Handled neikeq's objection.

Actually, I see a couple problems with this:
First, it runs in a loop so not only you can put FLAGS and the prefix at any order, but also you can put FLAGS twice (or the prefix twice). Putting the prefix twice makes the second override the first.
Second, the prefix is only used for the length. So it doesn't matter whether you put ELEM_ or Bodge, it'll work the same, which is kind of weird. Maybe we need only to set the prefix length.

Moving to 3.2 milestone as we're about to enter the beta stage and release freeze for Godot 3.1. Only bug fixes against issues of the 3.1 milestone (or enhancements to core features of the 3.1 roadmap) will be considered until 3.1-stable is released.
Note: If it's merged after 3.1-stable is released, this change might be considered for cherry-picking into a later 3.1.x release.

@willnationsdev This still needs changes to take https://github.com/godotengine/godot/pull/22820#issuecomment-445415888 into account.
Otherwise it should be OK to merge, though I'm not convinced about the use case in post-3.1 times where enum values are no longer in the global scope, so the example in OP would no longer be relevant (nowadays you'd have to use Elements.ELEM_FIRE explicitly, so changes are you'd no longer add a redundant prefix in the first place, which thus would no longer need to be removed...)

@akien-mga Yeah I heard you have added autocompletion for enums in their Dictionary form, in which case, using the constants is no longer necessary. No prefixes needed, so I don't think we even really need this change anymore.

Thanks, closing then.
For the reference, @vnen and @bojidar-bg were not strictly opposed to the feature (and it's not much code), so if a use case arises for it it could be considered again. But yeah, without a clear need it's better not to make the export() syntax more complex than it already is.