[591] Implement the courses index page

Context

https://trello.com/c/T5fMViQB/591-migrate-courses-courses-index-page

Changes proposed in this pull request

Migrate the courses index page to new publish
Bring over supporting code and fix where things are broken

Guidance to review
https://teacher-training-api-pr-2460.london.cloudapps.digital/publish/organisations/2AT/2022/courses
Assert the current list of courses (and information) matches the same view in old publish.
Note: Course adding/editing (and vacancies editing) will be handled in upcoming tickets
Checklist

[x] Make sure all information from the Trello card is in here
[x] Attach to Trello card
[x] Rebased master
[x] Cleaned commit history
[x] Tested by running locally

 Migrate Courses - Courses Index Page


Unable to create Lambda Function using server less from Bamboo build tool

Are you certain it's a bug?

[X] Yes, it looks like a bug

Is the issue caused by a plugin?

[X] It is not a plugin issue

Are you using the latest version?

[X] Yes, I'm using the latest version

Is there an existing issue for this?

[X] I have searched existing issues, it hasn't been reported yet

Issue description
I can install Lambda Function using server less cli from a docker locally
Where as if I use the same docker image from bamboo build tool I get the below error, when it invokes "serverless deploy --verbose" command.

25-May-2022 16:27:26
✔ Plugin "serverless-python-requirements" installed  (31s)

25-May-2022 16:27:27
Running "serverless" from node_modules

25-May-2022 16:27:32

25-May-2022 16:27:32
Deploying XXXXX to stage dev (ap-south-1)

25-May-2022 16:27:32

25-May-2022 16:27:32
Generated requirements from /workspace/master/api_health_lambda/requirements.txt in /workspace/master/api_health_lambda/.serverless/requirements.txt

25-May-2022 16:27:32
Installing requirements from "/root/.cache/serverless-python-requirements/993a177f330b98d5c2189d004569e1d1bfd60a5874e541041bc3c2d19b870b7b_x86_64_slspyc/requirements.txt"

25-May-2022 16:27:32
Using download cache directory /root/.cache/serverless-python-requirements/downloadCacheslspyc

25-May-2022 16:27:33
Running ...

25-May-2022 16:27:34
Stdout:

**_25-May-2022 16:27:34
Stderr: ERROR: Can not combine '--user' and '--target'_**

Service configuration (serverless.yml) content
# Welcome to Serverless!
#
# This file is the main config file for your service.
# It's very minimal at this point and uses default values.
# You can always add more config options for more control.
# We've included some commented out config examples here.
# Just uncomment any of them to get that config option.
#
# For full config options, check the docs:
#    docs.serverless.com
#
# Happy Coding!

service: grafana-app-status
# app and org for use with dashboard.serverless.com
#app: your-app-name
#org: your-org-name

# You can pin your service to only deploy with a specific Serverless version
# Check out our docs for more details
frameworkVersion: '3'

provider:
  name: aws
  runtime: python3.9
  stage: dev
  region: ap-south-1
  profile: default
  timeout: 10
  memorySize: 128
  iam:
    role:
      statements:
      - Effect: "Allow"
        Action:
        - health:Describe*
        Resource: "*"
  environment:
     REGION_NAME: ${self:provider.region}
     routing_key: XXX
     chk_svcs: "xx,yy"
     chk_rgns: "us-east-1,us-east-2,us-west-1,us-west-2"

custom:
  pythonRequirements:
   dockerizePip: false

functions:
  f1:
    handler: handler.f1
    events:
      - schedule:
          rate: rate(1 minute)
  f2:
    handler: handler.f2
    events:
      - schedule:
          rate: rate(1 minute)
  f3:
    handler: handler.f3
    events:
      - schedule:
          rate: rate(1 minute)

plugins:
  - serverless-python-requirements

Command name and used flags
serverless deploy --verbose
Command output
25-May-2022 16:27:34 | Stderr: ERROR: Can not combine '--user' and '--target'

Environment information
dev

Hey @ae07177 - you should get a notification about that

Thank you @pgrzesik

Hello Team, Any update on this? Or can you let me know if there is any official serverless-python docker image, that works?

FYI.. I have managed to fix the issue. This is not a docker image issue.
I had to add the below block in server less.yml file to fix the issue.
custom:
pythonRequirements:
dockerizePip: false
pipCmdExtraArgs:
-  --no-user


libjwt-typed: unbreak with minor changes

Unbreak libjwt-typed. I was able to build using:
nix-build --no-out-link -A haskellPackages.libjwt-typed .
This was accomplished by removing dependency
bounds, skipping tests, and adding the libjwt
librarySystemDepends.
Removed broken status from libjwt-typed.
This has not been tested in any concrete way (I am
essentially new to Nix). I would have liked to try
using these changes with a project which spurred
these changes, but I am unsure how to override in
a manner that used the local nixpkgs repo (where I
worked on these changes).
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Thx!
2 small things.
a) you need to move the libjwt dependency from the hackage-packages.nix (which is autogenerated and will be overriden) to configuration-nix.nix. See the miniball override in that file as an example for how to do that.
b) Can you open an issue upstream informing them which bounds are out of date and put that in a comment?

@maralorn thank you for your encouragement on Mastodon and Matrix. Your nice help has made this relatively painless.
Here is the issue you requested I make, in order to alert the author of libjwt-typed that the version bounds are out-of-date for said project: https://github.com/marcin-rzeznicki/libjwt-typed/issues/2

Nearly there. Can you put the link into a comment above the line with the override? I personally also like to add a timestamp
# 2022-08-07: Bounds are to restrictive: https://github.com/marcin-rzeznicki/libjwt-typed/issues/2

and then please rebase everything into one commit.

Okay, it's all in one commit now, plus there's also the timestamped comment you requested, @maralorn.

Sorry to bother you again, but that comment belongs together with the jailbreak in the configuration-common.nix. After all it’s about why you do the jailbreak. The library override already had a satisfying comment.

That makes sense, sorry about that, @maralorn. I have made the amended commit changing the comments. Thank you.

Thank, you!
Next time you can also run maintainers/scripts/haskell/regenerate-hackage-packages.sh to remove the broken flag from the hackage-packages.nix file, but we will run it later on the branch this time …


Update payload_data schema to 1-0-4

It also seems that the stm field should be a string instead of an integer.

You're right @juriglx. Thanks.


Restore the previous way to convert strings in ecma_builtin_json_parse()

JerryScript-DCO-1.0-Signed-off-by: Zsolt Borbély<EMAIL_ADDRESS>

LGTM after the comment is fixed

Note: This is a quickfix for the failing testcase on travis. This old logic should be eliminated or the json parse should be revised completely. Please raise an issue for it.
LGTM


[future] Add "weed mount" feature for FUSE access

Current "weed mount" is half baked. Need some help to work on this.

hello, need what can work on this? weed-fs version 0.70 beta.

POSIX attributes are added to filer


refactor(*): Cleanup

Description:
Related issue (if exists):

Closing as clippy does not work as intended


React UI: Starting Screen flashes before going to requested page

What did you do?
I opened the Prometheus web UI on a version that has the starting screen (for example https://prometheus-react.netlify.app).
What did you expect to see?
I expected to be taken right to the graph page.
What did you see instead? Under which circumstances?
The starting screen flashed for a second before forwarding me to the graph page.

Prometheus version:
main (1270b87)

This happens because the UI starts out on the starting screen and only moves off it once a request to /ready responds with a 200 status. I wonder if we could have the request happen in the background instead and just delay all requests on other pages until it responds (and if the server isn't ready then go to the starting screen).

Can you assign this issue to me?
I have some experience in ReactJS, I think I can help.
@LeviHarrison

Feel free to work on it. Thanks!

Thanks.


Schema validation fails for declarations omitting "template" since v3.20

Environment

Application Services Version: 3.20 & 3.21
BIG-IP Version: N/A

Summary
Since AS3.20 the template property is optional and defaults to generic.
This seems to break JSON Schema validation for multiple validation implementations.
Details
The template property in the AS3 Schema references a default of generic:
https://github.com/F5Networks/f5-appsvcs-extension/blob/3e93ab8120477f7edd4e390b9326f815f65d49bf/schema/3.21.0/as3-schema.json#L5763-L5768
When a JSON Schema (draft7) validator tries to validate a declaration like the "quick start" declaration from the 3.21 docs, it seems to ignore the default and assume that the template property is either empty or unspecified.
This leads to a validation error as the tested JSON Schema validators due to the allOf keyword trying to apply if conditions based on the value of the template property  (which either seems to not exist or is empty).
https://github.com/F5Networks/f5-appsvcs-extension/blob/3e93ab8120477f7edd4e390b9326f815f65d49bf/schema/3.21.0/as3-schema.json#L5880
The validation failure for the different implementations differ.
Steps To Reproduce
Steps to reproduce the behavior:

Save "quick start" declaration from the 3.21 docs to $PWD/quick_start.json:

Run https://github.com/simonkowallik/as3ninja (from docker for example):

docker run -it --rm \
  -v $PWD/quick_start.json:/as3.json \
  simonkowallik/as3ninja:latest \
  as3ninja validate -d /as3.json -v 3.21.0

Observe Python exception/validation error:

as3ninja.exceptions.AS3ValidationError: AS3 Validation Error: 'serviceMain' is a required property

Failed validating 'required' in schema['properties']['declaration']['additionalProperties']['additionalProperties']['allOf'][0]['if']['then']:
    {'description': 'Declares an HTTPS application',
     'properties': {'serviceMain': {'$ref': '#/definitions/Service_HTTPS'}},
     'required': ['serviceMain'],
     'title': 'HTTPS application',
     'type': 'object'}

On instance['declaration']['Sample_01']['A1']:
    {'class': 'Application',
     'service': {'class': 'Service_HTTP',
                 'pool': 'web_pool',
                 'virtualAddresses': ['<IP_ADDRESS>']},
     'web_pool': {'class': 'Pool',
                  'members': [{'serverAddresses': ['<IP_ADDRESS>',
                                                   '<IP_ADDRESS>'],
                               'servicePort': 80}],
                  'monitors': ['http']}}

In this repro the python jsonschema library uses the first Schema $ref (Template_https) to validate the application A1, which fails due to the requirement of serviceMain.
https://www.jsonschemavalidator.net/ fails as well, as does ajv (tested with as3_schema_validator)
Expected Behavior
Schema validation does not fail.
Possible solution
I couldn't find what the expected behavior of a if condition against a non-existing property should be in the JSON Schema spec.
But specifically testing if "template": "generic" does NOT exist seems to work:
      "if": { "not": { "properties": { "template": { "const": "generic" } } } },
      "then": {
        "allOf": [ .. ]
      },
      "else": {
        "$ref": "#/definitions/Template_generic"
      },

replacing "allOf": [ .. ] with the existing definition (and probably remove the if/then for generic):
https://github.com/F5Networks/f5-appsvcs-extension/blob/3e93ab8120477f7edd4e390b9326f815f65d49bf/schema/3.21.0/as3-schema.json#L5880

Added to the internal product backlog as AUTOTOOL-1776.

This also applies to Schema version 3.22, another example for a schema validation failure from VS Code:

That is strange. The fix should have been available in 3.22.0.
Is it possible that VS Code has the old schema still cached? You could confirm that you are using the latest schema by trying to set the schemaVersion property to "3.22.0".

@dstokesf5 setting the schemaVersion to 3.22.0 did not resolve the problem. Validation also fails with the other Schema validation implementations previously listed.

Sorry for being unclear. I was not expecting changing the schemaVersion to fix the problem, I was suggesting it as a diagnostic step. If VS Code gave an error for a value of "3.22.0", then that would suggest that it is using an outdated schema. It sounds like that is not the case.
Marking as "untriaged" to take another look at this issue.

This issue should be resolved in the 3.22.1 release.


Save mapping of which device tenants are stored on in v1/v2

We need to know which device a tenant "lives on" for scaling purposes.

[ ] Make migration for database table to store which device each tenant is on
[ ] Initially populate table with the tenant's current device

We need to store which device each loadbalancer/vip is on. Break the indirect dependency
loadbalancer ---> tenant ---> device
              |           ^ hash of tenant id
              ^ neutron table

And replace it with
loadbalancer ---> device
              ^ new table

(The loadbalancer will still know which tenant it belongs to)

The plan is to make one polymorphic table for loadbalancers (A10_SLB) and another one for devices (A10_DEVICES). In the alembic migrations there'll be separate branches for tables that depend on lbaas v1 and lbaas v2. The SQL alchemy classes for the version specific models will only be defined if there's support for that version.

To do:

[ ] Rename device_key to configuration_key
[ ] Make migration to populate existing appliances (devices)
[ ] Make migration to populate appliance (device) for existing lbaas v1 vips
[ ] Make migration to populate appliance (device) for existing lbaas v2 loadbalancers
[ ] Create appliances as needed
[ ] Create a10_slb_v1 when handling a v1 vip creation
[ ] Delete the a10_slb_v1 when handling a v1 vip removal
[ ] Create a10_slb_v2 when handling a v2 loadbalancer creation
[ ] Delete the a10_slb_v2 when handling a v2 loadbalancer removal
[ ] patch whatever vip code is checking the hash to get the device to instead get it from the model (will still use the hash to pick devices for new vips)
[ ] patch whatever loadbalancer code is checking the hash to get the device to instead get if from the model (will still use the hash to pick devices for new loadbalancers)
[ ] Make the A10ApplianceConfigured model present the data from the configuration (might be a separate story)

To do the migration we need to load the real configuration. I tried hacking one together by making an A10OpenstackLBV1(None), but that doesn't get the provider name so we don't know which vips are ours. We're going to have to figure out how to load the real deal, enumerate the providers, and check to see if they are the a10 provider we're working with.

The following demonstrates getting the (almost) real configuration for the drivers. It doesn't provide a plugin and doesn't import all of the set up for oslo configuration that is set up when a driver loads for real.
import neutron.plugins.common.constants as constants
import neutron.services.service_base as service_base
from oslo_config import cfg

cfg.CONF(project='neutron')

lbv2 = service_base.load_drivers(constants.LOADBALANCERV2,None)
print lbv2
print lbv2[0][lbv2[1]].a10.hooks.select_device('012-345')

The migrations are going to use this mechanism to get the drivers and their provider names.

The cli unfortunately includes a workaround for [https://bitbucket.org/zzzeek/alembic/issues/336/branching-causes-destination-is-not-a](alambic issue 336).

Blocked by #122


Update hostname validator TLD

Backport of https://github.com/zendframework/zend-validator/blob/master/src/Hostname.php

The Long Term Support for version 2.4 ended on 2018-03-31. Therefore, I do not see a chance to backport the updates of the validator.
@weierophinney is working on a new support policy, which will clarify the new time frame of support.

@kachar As noted, 2.4 is past its EOL, and we will not be doing new releases of it.
We recommend upgrading to at least the v2.5 series of Zend Framework, and, ideally, installing only the packages you actually use. This will allow Composer to pull in updates as soon as they happen, and provide you clearer upgrade paths.


error login security

hello i need help from login security
it writes to me on the console
[INFO]: [LoginSecurity] Enabling LoginSecurity v2.0.10
[ERROR]: [LoginSecurity] Could not read from auth list!
someone will help

hello i need help from login security
it writes to me on the console
[INFO]: [LoginSecurity] Enabling LoginSecurity v2.0.10
[ERROR]: [LoginSecurity] Could not read from auth list!
someone will help


[Bug?] Failed to refresh profile with gh data: timeout of 30000ms exceeded

I tried to Refresh > Update Github repos @ https://sourcerer.io/sarpik.
I get this error in my console:
baeee485d24a395e21be.js:1 failed to refresh profile with gh data:  Error: timeout of 30000ms exceeded
    at t.exports (e005c28999e832bcba4a.js:2)
    at XMLHttpRequest.d.ontimeout (e005c28999e832bcba4a.js:2)

Thanks!

Hi @sarpik, could you please check there is an access for Sourcerer in github settings
Settings -> Applications -> Authorized OAuth Apps?

Hello @yaronskaya, thanks, yes there is: https://i.imgur.com/vS0Hzmx.png (under Authorized OAuth Apps)

@sarpik looks like your github token doesn't provide access for Sourcerer now.
Could you please revoke it and add github account at sourcerer.io again:
Settings->Applications->Github: sign in?

@yaronskaya yep, that did sync the profile.
Though if I click Refresh > Update Github repos, I still get the same errors and cannot refresh.
Also, before that, I tried signing in with a different browser with the same github account, and a different profile was created - https://sourcerer.io/sarpik1. I don't know if this is expected so just letting you know:D
And they (sarpik and sarpik1) are a little out of sync lol

@sarpik yes, these two profiles have different emails. Therefore assigned commits are different.
Meanwhile, I reassigned the github token from your second profile to the original one - it processes the profile https://sourcerer.io/sarpik now.  Did you change the primary email in github settings?

@yaronskaya I have changed my primary email a while back, but not after I started using sourcerer.
Now the refresh feature seems to work, at least with /sarpik:)
Would it be possible to merge the contributions from both (all) of my emails (that my profile has) into a single sourcerer profile, just like github does?
I don't think that having 2 (or more) separate profiles for every email is useful if that's still the same user (at least in my case).
Thanks!

@sarpik you can add emails in Settings -> Emails and after that Update Github repos.

Thanks @yaronskaya - I've removed the duplicate account /sarpik1 and added emails to the main account /sarpik. Everything seems to be fine now.
The Refresh feature is now working as expected, some maybe there were some issues with the duplicate account - I don't know.
I suppose we can close this?
Thanks again!

Closing the Sourcerer account and then reconnecting seems to work.


Python 3.6 runtime is no longer available

Importing this Watson Studio project sets up a notebook with a Python 3.6 runtime.  The Python 3.6 runtime no longer exists in Watson Studio as a option.  As a result, the notebook will open but it can't start a kernel to run.
We need to bump this notebook to run in a Python 3.7 runtime.  It works successfully.
Don't choose a Python 3.8 runtime because the pip install tensorflow==1.15 is not available/compatible with Python 3.8.

I exported the project using a Default Python 3.7 XXS (1 vCPU 4GB RAM) runtime so that it will execute in an IBM Cloud Lite account.  I have a replacement coffee-donut.zip
Will import / test again and then open a PR

@upkarlidder  This PR is necessary to support the IBM booth demo at Open Source Summit this week. Can you merge?

Absolutely. I will merge this afternoon. Thank you.

Thanks @upkarlidder  - Tonight / tomorrow, I might have additional PRs to update the VCPI shorturl and a few Watson Studio screenshots that have changed.


Does opencache serve as a cluster?

What will happen if I push the same key with different data to different endpoints?

It will just create a multiverse for the application.
Client-A write key1=value_x to cache-node-x;
Client-B write key1=value_y to cache-node-y;
Client-C will see value_x if it uses the same algorithm to distribute data as Client-A.
Client-C will see value_y if it uses the same algorithm to distribute data as Client-B.


Ruby group capstone: set up your Kanban board

Hello Reviewer,
This is @shafiuyushawu, @edubew and @Matthieu96Code. This is the link to the Kanban board
Highlights

We are in the group of three, @edubew assigned to books, @Matthieu96Code assigned to musical album and @shafiuyushawu games.

Hi Team,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Highlights

All cards are created and assigned equally to each member of the team

Cheers, and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Fix for a secrets validator error when we change env without changing secrets

Summary: Secrets validator was only passing if we submit a secret environment variable update with a corresponding secret definition section. This change makes secret validator to preload existing definitions, so now we can update an environmental variable without specifying any secrets definitions as long as they're present in the app definition.
Jira issue: DCOS-41267

It looks like there's an PR, https://github.com/mesosphere/marathon/pull/6655/files, that targets to merge in to this one.
Can we just combine those pull requests into this? Or, can you help me understand why we have two of them?

@jeschkies yes!


manticore: 2018.09.29 -> 2019.09.20

Motivation for this change
manticore wasn't building on master or 19.09. This upgrade fixes that.
Connected to #68361
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

It also seems to install its source: /nix/store/xh6vh4zhy32ri9c4hlhq4j6y4qlizk3g-manticore-2019.09.20/repo_checkout/src
Is this supposed to happen?

That was added in https://github.com/NixOS/nixpkgs/commit/53dde421533d96de8c8c72c9d756042de800fd6b#diff-d44f3788bd35dd171c6fc74abc8da4d5 and seems to be intentional. I admit I don't know what goes wrong without this, though.


cypress test on seedlot detail page

Implement a Cypress test on seedlot detail page /seedlots/details/{seedlot_number}
Useful commands:
npm run cy:open

[x] All relative information should be rendered
[x] Can change applicant seedlot info
[x] All tests pass

reopened for more review


Paloma.js: Add Scheduling functions and new required metata data to JavaScript SDK

As a Paloma.js user, I want the JavaScript package to include the ability to schedule jobs and with the required creator and signer metadata for Paloma v1.10.0.
Acceptance Criteria

Deliver job scheduling in JavaScript SDK
Deliver metadata in JavaScript SDK
Check with Python SDK format for design patterns.
TEST the JavaSript SDK feature at release.

Here is the equivalent change for the python sdk https://github.com/palomachain/paloma.py/pull/17/files

@webelf101 will you please support @rootedbox as he does this upgrade!

@fullstack412 how much more is left here?


genome metadata needs cleanup

I was about to regenerate data landing page cache, but I stopped because this may mess up the chart.

remove undefined in disease
merge None and none in disease
Merge Human, Homo sapiens and Homo sapiens in host name
remove or rename "not applicable" in host name
Merge "Non-susceptible" and "Nonsusceptible" in Antimicrobial Resistance

ok, I will run the clean up this morning.

On Dec 6, 2016, at 9:44 AM, hyoo<EMAIL_ADDRESS>wrote:
https://cloud.githubusercontent.com/assets/1236467/20931873/3dfc9774-bb98-11e6-90f6-c40be709722f.png
I was about to regenerate data landing page cache, but I stopped because this may mess up the chart.
remove undefined in disease
Merge Human, Homo sapiens and Homo sapiens in host name
remove or rename "not applicable"
Merge "Non-susceptible" and "Nonsusceptible" in Antimicrobial Resistance
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/PATRIC3/patric3_website/issues/1365, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLd7z1WvE9CH2J25Nid1Y_Qo1RB8J04ks5rFYLvgaJpZM4LFjd_.

This is not done yet. removing Obsolete tag.

Fixed.


Publish: Allow to disable printing logs to host

Is your feature request related to a problem? Please describe.
I'd like to disable Pyblish (and potentially even OpenPype Logger logs during publishing) printing its logs into the Host DCC (e.g. Maya) as a setting when running the Pyblish UI.
Describe the solution you'd like
Be able to set e.g. a OPENPYPE_PRINT_PYBLISH_LOGS=0 or an equivalent setting to disable the printing to stderr. The logs should still get collected and handled by the UI. I'd only like to have it not propagate its logs into the host DCC.
Describe alternatives you've considered
I've tried disabling the propagating of the Pyblish loggers like this:
import logging

log = logging.getLogger("pyblish")
log.propagate = False

But that also avoids the Pyblish Pype UI to actually capture the logs. Note that the original Pyblish QML does work with propagate disabled - there the logs still get handled by the UI regardless.
Additional context
Printing in the Maya script editor has always been relatively slow - and during publishing there's relatively quite a high amount of logging/printing being done. I'd like to try and avoid the clutter in the Script Editor and at the same time likely optimize the publishing steps too.
Especially with the new publisher UI coming up the logs are much easier to debug per instance in the UI - better than the printed logs into the host DCC would allow for debugging.
First mentioned on OpenPype discord here

Of course would also love to know if this is a bad idea to begin with. :)
[cuID:OP-3914]

This issue coming from OpenPype is still relevant to AYON since I've still noticed slowness on the printing of logs to the host - so I transferred the issue.


Frontendbuild env

Fixes GHE#900#issuecomment-41489
Changes

Adds an environment variable to our .env_SAMPLE which devs should add to our local .env file
Renames grunt tasks to match up with our various deployment environments: local/dev task is dev-deploy, release to production is production-deploy
frontendbuild.sh checks the variable to run either grunt production-deploy or grunt dev-deploy depending on the environment

This will require changes to our build job(s) and production
This means we can remove inconsistent configurations for those jobs and just use frontendbuild.sh but we have to set the environment locally and in our deployment configs.
Review

does this make sense? are we using that environment variable for something else in our jobs? we can discuss over Office Hours if needed for Security Purposes @contolini @imuchnik @Ooblioob
@virginiacc can you try out the renamed grunt tasks plus frontendbuild.sh to assure they work as expected?

todos

if merged we can maybe use this to write our URLs based on environment  (omgggg what a dream)
if merged update jobs in all environments + the wiki front end deploy doc
add similar updates to the old branch for #421

@Ooblioob can you take a look at this and let me know what you think? thanks.

@Ooblioob bumpity bump bump bump

We have a release in July so we need to make this change and test well before then.

Sorry  for the delayed response. Couple of clarifying questionsL

What is the difference between release and ship?
Why would we want to run deploy in grunt? I would be more inclined to keep this as configuration settings in Jenkins jobs, unless we deploy with Grunt? @contolini @Ooblioob  can you confirm and/or shed some light?

@imuchnik the grunt tasks are documented in GHE oah wiki.
as for the changes here, see GHE#900#issuecomment-41489 for history/discussion

@cfarm Can you include a link please.

Made an update based on @contolini's comment, and also updated the env file so it echoes the value of your DEPLOY_ENV for developers to see what it's set to

(above defaults to dev)

Planning to merge these changes and update the corresponding Janks jobs next sprint so it doesn't delay this week's planned plugin release.

@virginiacc can you review so we can try to make this change for Journey release this week?

@amymok

@amymok Apparently I didn't comment at the time, but when I reviewed this before our release last month everything looked good...

looks good!


unbind hotkey

How unbind hotkey?

Just remove the line of code that is binding it to a method.
Sent from my iPhone

On Oct 21, 2015, at 8:48 AM, Anderson Lima<EMAIL_ADDRESS>wrote:
How unbind hotkey?
—
Reply to this email directly or view it on GitHub.


[release/1.6] update to Go 1.18.8 to address CVE-2022-41716

relates to https://github.com/containerd/containerd/pull/7620
On Windows, syscall.StartProcess and os/exec.Cmd did not properly
check for invalid environment variable values. A malicious
environment variable value could exploit this behavior to set a
value for a different environment variable. For example, the
environment variable string "A=B\x00C=D" set the variables "A=B" and
"C=D".
Thanks to RyotaK (https://twitter.com/ryotkak) for reporting this
issue.
This is CVE-2022-41716 and Go issue https://go.dev/issue/56284.

This Go release also fixes https://github.com/golang/go/issues/56309, a runtime bug which can cause random memory corruption when a goroutine exits with runtime.LockOSThread() set. This fix is necessary to unblock work to replace certain uses of pkg/reexec with unshared OS threads.

lawl, the linter exceeded its timeout so this needs a re-run

looks like golangci-lint timed out; could someone give CI a kick?

looks like golangci-lint timed out; could someone give CI a kick?

Done!

Thanks ❤


Apply back behavior to modals

Why is this issue important?
This issue is to build upon the work done in #2575 which enables back behavior in more places in grant finder. This issue is to add "back" functionality to places where modal/pop-up windows show in the app to ensure consistency with how back behavior works in other places of grant finder.
Current State
If you are on the Users page and you click "add," the modal opens. If you click back on the browser when the modal is open, it will bring you to the page you were on before the Users page. This applies to all the modals described below.
Expected State
Users Tab

When you click "add" button or the "bulk import" button, the modal that come up should have a unique url
if you click back in the browser when the modal is open, it should take you to the page you were previously on (we expect most users to get to the modal from the Users page, so in most cases, clicking back will close the modal)
if you had partially completed the form and click back on the browser, the content you entered will not be saved (i.e. same as current behavior for closing a modal)

Team Tab

When you click "add" button, the "bulk import" button, or the edit pencil on any of the Teams, the modal that come up should have a unique url
if you click back in the browser when the modal is open, it should take you to the page you were previously on (we expect most users to get to the modal from the Teams page, so in most cases, clicking back will close the modal)
if you had partially completed the form and click back on the browser, the content you entered will not be saved (i.e. same as current behavior for closing a modal)

Browse Grants Tab

When you click "new search", when the drawer appears on the right side of the page, it should have a unique url
If you click back on the browser when the search drawer is open, it should take you to the previous page you were on

*need to add behavior for my saved searches and edit search
Implementation Plan
The following functions need to be added...
Relevant Code Snippets
No response

@caitlinwinner need to discuss - what happens when you go back to a modal that has been submitted? For add user/team, should it just show as a blank version?
and what do we expect for going back to new search? should it always be a fresh/blank new search?
and for edit search - confirm that it should go back to edit for the search you were on, but reflect what has been applied to the search (i.e. save as if you click on edit the search)?


Update to UE 5.4

Please update the script for UE 5.4, as it refuses to work on the newest version. Says that the plugin is not compatible with the newest version

Please update the script for UE 5.4, as it refuses to work on the newest version. Says that the plugin is not compatible with the newest version

https://www.youtube.com/watch?v=vMPWc-rdxWM Video on how you can update it yourself.


Gateway works as wildcard even if it's not defined like that way

Bug description:
I have 2 domains in different gateway 1) example.com 2) api.example.com
Website gateway:
	---
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
 name: example.com
spec:
  selector:
    istio: ingressgateway # Use Istio default gateway implementation
  servers:
  - port:
      name: example-http-80 # This must be unique
      number: 80
      protocol: HTTP
    hosts:
    - "example.com"
    tls:
      httpsRedirect: true # sends 301 redirect for http requests
  - port:
      name: example-https-443 # This must be unique
      number: 443
      protocol: HTTPS
    tls:
      credentialName: example-crt # The certificate name you created above
      mode: SIMPLE
      #privateKey: sds
      #serverCertificate: sds
    hosts:
    - "example.com"

API gateway:
	---
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
 name: api.example.com
spec:
  selector:
    istio: ingressgateway # Use Istio default gateway implementation
  servers:
  - port:
      name: api-example-http-80 # This must be unique
      number: 80
      protocol: HTTP
    hosts:
    - "api.example.com"
    tls:
      httpsRedirect: true # sends 301 redirect for http requests
  - port:
      name: api-example-https-443 # This must be unique
      number: 443
      protocol: HTTPS
    tls:
      credentialName: api-example-crt # The certificate name you created above
      mode: SIMPLE
      #privateKey: sds
      #serverCertificate: sds
    hosts:
    - "api.example.com"

Affected product area (please put an X in all that apply)
[x] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
It should point to appropriate domains. But, when I try to access api.example.com I am getting 404-not found when I delete example.com gateway then I can access api.example.com service. It looks like when example.com gateway is there it also tries to send api requests thru this gateway which is incorrect.
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version)
kubernetes version: v.1.12.4
istio version: v.1.2.6
How was Istio installed?
helm template
Environment where bug was observed (cloud vendor, OS, etc)
AKS

So, I had wildcard domains in the certificate issued from letsencrypt. It worked when I removed and put simple domain name. But, istio should only rely on gateway configurations. However, when I tested with letsencrypt-staging with wildcard certificates everything works normally.

I can't reproduce this issue, with istio.io docs as https://istio.io/docs/tasks/traffic-management/ingress/secure-ingress-sds/, for the multi host section. I tweaked the credential for the example.com to use *.example.com as common name as the certificate. curl request against helloworld still works. Following gist has the content of the keycert, gateway configuration, virtual service I'm using.
https://gist.github.com/incfly/95ce8c4a4bbc28b63dc5bde332fb2e98

Plus you get 404 error, I suspect this is a error of your reconfiguration of the routing, virtual service. The gateway CRD looks fine.


settings: Refactor code to update realm group based settings.

This PRrefactors code such that we do not add separate if condition block for each
realm group based settings using the new API format to send the request accordingly.
We now use a single if-block to update the request data for realm group permission
settings using new API format.

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @sahil839!


fix bug: invalid customized metrics

(This is a relevant issue that's worthwhile to read: https://github.com/neulab/ExplainaBoard/issues/455)
Debugging route:

specified metrics in ExplainaBoard web cannot work
verify the correctness of frontend code
move to SDK
the same thing happened in SDK CLI
bug in processor

metric_configs should be a list here: https://github.com/neulab/ExplainaBoard/blob/cd54c1b61e490295db8c1cfee8460aff4cce1880/explainaboard/processors/processor.py#L454
this will fail: https://github.com/neulab/ExplainaBoard/blob/cd54c1b61e490295db8c1cfee8460aff4cce1880/explainaboard/processors/processor.py#L203

Relevant issues: https://github.com/neulab/explainaboard_web/issues/284

@pfliu-nlp I haven't dug into this in detail yet, but it's not clear to me if the discussion in https://github.com/neulab/ExplainaBoard/issues/455 has finished? Once you've finished and decided which direction to go I'll be happy to review.

I want you to have a quick read of [this], I think we need to use Accuracy instead of AccuracyConfig to keep consistent with metric names in the processor. However, to this end, we need to modify this line of code.  Not sure if it makes sense to you.

Revised the PR a little bit.

register metrics with the form of  XConfig
if users specify metrics, then the default metrics list will be ignored.


Make proto handling more robust, improve gRPC client 'connected' state and make project structure more pythonic

This is mostly a preparation work before implementing the new kuksa.val.v1 protobuf API.
It addresses the following:

General project strucuture: split the project in three packages: client, certificates and protobuf definitions.
Misleading CLI feedback for the gRPC client stating that the client is connected when it's not.
Using absolute imports instead of relative ones for generated python stubs as protoc does not handle well the latter.

I notice that you move around files and adds an extra sub-directory here and where. Have you seen https://github.com/eclipse/kuksa.val/issues/318. I am thinking that as you anyway moves around files, would this PR also be a good candidate for changing name to get rid of VISS (as we do not support only VISS (websocket protocol) but also gRPC. But we could do it later as well.

I notice that you move around files and adds an extra sub-directory here and where. Have you seen eclipse#318. I am thinking that as you anyway moves around files, would this PR also be a good candidate for changing name to get rid of VISS (as we do not support only VISS (websocket protocol) but also gRPC. But we could do it later as well.

I've just opened a separate PR for this: https://github.com/boschglobal/kuksa.val/pull/8

Replaced with https://github.com/boschglobal/kuksa.val/pull/10.


adding activeDirectoryConnectors resource type (2022-03-01-preview)

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[X] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[X] I commit to follow the Breaking Change Policy of "no breaking changes"
[X] I have reviewed the documentation for the workflow.
[X] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[X] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version

[X] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[X] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Adding @ArcturusZhang for Go Breaking change review.

@changlong-liu @ArcturusZhang I think this Go Breaking Change alert might be a false alarm.
To test this, I made a draft PR: https://github.com/Azure/azure-rest-api-specs/pull/18029/checks?check_run_id=5364447618 where the only change was a small description change, and the Go SDK breaking change check is the only one that fails there too, which makes me think this check failure is unrelated to the actual PR changes

/azp run

@changlong-liu @ArcturusZhang I think this Go Breaking Change alert might be a false alarm.
To test this, I made a draft PR: https://github.com/Azure/azure-rest-api-specs/pull/18029/checks?check_run_id=5364447618 where the only change was a small description change, and the Go SDK breaking change check is the only one that fails there too, which makes me think this check failure is unrelated to the actual PR changes

Hi @sasank-chaganty , the breaking change log content are different between your temporary PR #18029 and this PR #17825.
And beside the GO breaking change, the validation tool Avacado finds API(s) missing in default tag, would you have a check? https://github.com/Azure/azure-rest-api-specs/pull/17825/checks?check_run_id=5369008048

@changlong-liu @ArcturusZhang I think this Go Breaking Change alert might be a false alarm.
To test this, I made a draft PR: https://github.com/Azure/azure-rest-api-specs/pull/18029/checks?check_run_id=5364447618 where the only change was a small description change, and the Go SDK breaking change check is the only one that fails there too, which makes me think this check failure is unrelated to the actual PR changes

Hi @sasank-chaganty , the breaking change log content are different between your temporary PR #18029 and this PR #17825.
And beside the GO breaking change, the validation tool Avacado finds API(s) missing in default tag, would you have a check? https://github.com/Azure/azure-rest-api-specs/pull/17825/checks?check_run_id=5369008048

@changlong-liu We are not removing any field from the swagger for SQL as well as common types for this API version. The real diff is in this link.
I did swagger refactor before on 2021-11-01 and 2021-08-01 version and not quite sure if these are causing issues.
Another thing is that we are very sure that no our customer is using GO SDK. So there wouldn't be any impact to the customer.
This swagger change is essentially blocking the next release for SqlServerInstance which includes ExtendedSupportUnit for SQL Server 2012 and other version, and it has a pretty tight deadline. We would appreciate if you can approve and merge the PR or would allow us to address the issue in a separate PR. Thanks.

Hi @sasank-chaganty , @sureleo ,
The new api version has not been deployed online in ARM, hasn't it? (since the "API Readiness Check" failed)
I added 'Approved-OkToMerge' label for the review is done, but don't merge this PR since the swagger should only be merged after the service is ready.
Since the ''

Hi @sasank-chaganty , @sureleo ,
The new api version has not been deployed online in ARM, hasn't it? (since the "API Readiness Check" failed)
I added 'Approved-OkToMerge' label for the review is done, but don't merge this PR since the swagger should only be merged after the service is ready.
Since the ''

Thanks @changlong-liu. Actually our RP is an RPaas RP. The first thing to release a new API version in RPaas RP is to check in the Swagger. After that, we just need to do a manifest rollout. In other words, without Swagger being merged, we cannot deploy it in ARM.
Let me know if this makes sense to you.

Hi @sasank-chaganty , @sureleo ,
The new api version has not been deployed online in ARM, hasn't it? (since the "API Readiness Check" failed)
I added 'Approved-OkToMerge' label for the review is done, but don't merge this PR since the swagger should only be merged after the service is ready.
Since the ''

Thanks @changlong-liu. Actually our RP is an RPaas RP. The first thing to release a new API version in RPaas RP is to check in the Swagger. After that, we just need to do a manifest rollout. In other words, without Swagger being merged, we cannot deploy it in ARM.
Let me know if this makes sense to you.

Hi @sureleo, as I know swagger pr's approval is enough for release new api-version :)

Are you sure this is also the case with RPaas RP? We have been checking in the Swagger first for all of our API version bumps. With RPaas RP, we don’t need to write any code but just specify the checked in Swagger URL and RPaas will take the rest once manifest rollout.

Hi @sasank-chaganty , @sureleo ,
The new api version has not been deployed online in ARM, hasn't it? (since the "API Readiness Check" failed)
I added 'Approved-OkToMerge' label for the review is done, but don't merge this PR since the swagger should only be merged after the service is ready.
Since the ''

Thanks @changlong-liu. Actually our RP is an RPaas RP. The first thing to release a new API version in RPaas RP is to check in the Swagger. After that, we just need to do a manifest rollout. In other words, without Swagger being merged, we cannot deploy it in ARM.
Let me know if this makes sense to you.

Hi @sureleo, as I know swagger pr's approval is enough for release new api-version :)

@changlong-liu Are you sure this is also the case with RPaas RP? We have been checking in the Swagger first for all of our API version bumps. With RPaas RP, we don’t need to write any code but just specify the checked in Swagger URL and RPaas will take the rest once manifest rollout.

Hi @sasank-chaganty , @sureleo ,
The new api version has not been deployed online in ARM, hasn't it? (since the "API Readiness Check" failed)
I added 'Approved-OkToMerge' label for the review is done, but don't merge this PR since the swagger should only be merged after the service is ready.
Since the ''

Thanks @changlong-liu. Actually our RP is an RPaas RP. The first thing to release a new API version in RPaas RP is to check in the Swagger. After that, we just need to do a manifest rollout. In other words, without Swagger being merged, we cannot deploy it in ARM.
Let me know if this makes sense to you.

Hi @sureleo, as I know swagger pr's approval is enough for release new api-version :)

@changlong-liu Are you sure this is also the case with RPaas RP? We have been checking in the Swagger first for all of our API version bumps. With RPaas RP, we don’t need to write any code but just specify the checked in Swagger URL and RPaas will take the rest once manifest rollout.

Thanks for the clarification, merging PR


Performance improvement and element resize watcher

Tested +1 for performance improvement

@miraclemarc
Please update to my latest change this morning.
My previous change places the ellipsis not so accurate...

I'll take a look at the pull request this evening and merge it then - thanks for the update!

This works much better than the current version. For our implementation the current version failed to work at all. This one works fine.

I'm getting an error with the PR:


No files when mounting Dropbox

Hello,
I recently purchased a new laptop (ASUS Chromebook) and tried mounting File System for Dropbox, however I kept getting the error "Failed to Mount" that was covered in depth in another thread. Today I updated my Chromebook (version 81.0.4044.103), tried downloading and mounting Dropbox again, and it was a success!
However, when I view my Dropbox account, none of my team's files show. As a reference, my old laptop was a Dell on which I installed the Dropbox app and was able to view all of my dropbox files and folders as if it were a normal folder on my computer; much like Google Drive is on this new Chromebook.
If I remember correctly there was some kind of "sync offline files" setting or something like that on the other laptop, but I don't see a feature like that on this. Is there a way to show my Dropbox files with this Chrome app?
Thank you!

Following up with info that I saw on another thread: we use a Dropbox Business account for our team. Is it possible that the files aren't showing because it's a business account and not a personal account?


MMB: evolve structure of all files to be more readable

This is my new proposed structure:
src/
├── components/                       - generic components reused accross all scenes in MMB
├── navigation/                       - React Navigation related files
├── scenes/                           - navigation independent (more or less) scenes
└── MainMenu.js                       - main file with defined items

Definitely a big improvement, thanks 🙂


asDebugSourceUri does not adhere to spec regarding sourceReference

VSCode Version: 1.52.1
OS Version: Win10 / WSL2

asDebugSourceUri was introduced in #79228 by @weinand.
https://github.com/microsoft/vscode/blob/04efea43fa3ab33e8a50bbf3caf0270f6b0b3030/src/vs/workbench/api/common/extHostDebugService.ts#L151-L171
But it doesn't follow the spec which allows sourceReference set to 0 to denote a normal path which is what the C# debugger does:
"stackFrames": [
      {
        "id": 1000,
        "name": "Program.Main(string[] args) Line 16",
        "source": {
          "name": "Program.cs",
          "path": "/.../Program.cs",
          "sourceReference": 0,
        },
        "line": 16,
        "column": 13,

which when passed to showTextDocument results in a blank editor with Could not load source '/.../Program.cs': Incorrect format of 'source' message..
const srcuri = vs.debug.asDebugSourceUri(frame.source);
const editor = await vs.window.showTextDocument(srcuri);

@Trass3r good find, thanks!

@Trass3r good find, thanks!

@Trass3r Same prblem here... did the latest vscode (1.53.2) fix it for you? It didn't for me.


I can't remove environment... Rancher Version 1.4.1 and Docker 1.13.1

Rancher	v1.4.1
Cattle	v0.176.9
User Interface	v1.4.6
Rancher CLI	v0.4.1
Rancher Compose	v0.12.2
Docker version 1.13.1, build 092cba3
(AWS) SMP Debian (Jessie) 3.16.39-1 (2016-12-30) x86_64 GNU/Linux
single node rancher
Environment Type: (Cattle)
I created a stack, but I can not delete it. It's like that for many hours...
Is there any place in the database where I can manually remove this? I searched using ID but I'm not finding it. There are many tables ...
Very thanks.

Before fixing it manually, can you share what you did to end up in this state? Maybe check the logging and provide it if there is something in there.
You can find the environments under the v2-beta/projects endpoint, by sending a HTTP DELETE to the correct ID you can remove it but I think the GUI is hiding it because it's stuck in Deactivating

I believe Docker 1.13 is not yet supported, so you might want to downgrade if this is reproducible. It could help to look at your host and server logs, as suggested above. Error loading schema in the screenshot (top right) might mean the env has already been actually removed. You can try restarting the Rancher server container and see if it trues up its state with the DB upon restart.
PS: Unrelated, but you might want to redact your screenshot to remove your Rancher URL, and put your Rancher install behind SSL (I doubt it has anything to do with this error, but just a good practice).

The delete action is based on whether the API is going to allow it in the current state so calling or from the API won't help.  The admin ->processes ascend should give some insight into what is going on related to that environment.

Thanks for you good pratice @ebr . :+1:
I remove and recreate rancher server (using same database) and solved. Thanks @vincent99  and @superseb


Instability

delete this template text while filling your issue/request but before that please check if:

do you hLogger: homeassistant.util.async_
Source: util/async_.py:120
First occurred: 12:15:05 (11 occurrences)
Last logged: 12:22:07

Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for sonoff doing I/O at custom_components/sonoff/init.py, line 175: r = requests.post('https://{}-api.coolkit.cc:8080/api/user/login'.format(self._api_region),
Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for sonoff doing I/O at custom_components/sonoff/init.py, line 372: r = requests.get('https://{}-api.coolkit.cc:8080/api/user/device?lang=en&apiKey={}&getTags=1&version=6&ts=%s&nonce=%s&appid=oeVkj2lYFGnJu5XUtWisfW4utiN4u9Mq&imei=%s&os=iOS&model=%s&romVersion=%s&appVersion=%s'.format(
Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for sonoff doing I/O at custom_components/sonoff/init.py, line 221: r = requests.post('https://%s-disp.coolkit.cc:8080/dispatch/app' % self._api_region, headers=self._headers)ave the latest version of the code in use? (this is a very common problem & fix that everyone ignores)

did you gave a quick look to the other issues to see if the issue is already reported? (otherwise i will close the issue without any response. it takes me good hours to develop & manage this plugin, you can take 3 minutes to do a quick reading)

same message for me

solution in #267


Minor documentation update to clarify pre-reqs

This is a suggestion for a minor documentation update to three pages. It is intended to make sure that pre-requisite resource providers are obvious when following the Learn documentation, as they are not currently mentioned. It is therefore possible that a user follows the link directly from Learn to the Portal and initiates an ALZ deployment without being aware that RPs need enabling, as they are documented separately on the Github wiki.
Current state:

https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/#azure-landing-zone-accelerator has a 'click here to deploy landing zones' button that launches the portal ALZ deployment wizard. It does not make any reference to pre-reqs other than the permissions required at / scope
https://github.com/Azure/Enterprise-Scale/wiki/Deploying-ALZ-Pre-requisites discusses the / scoped permissions but makes only a passing reference to resource providers in the context of AMBA and no link to the pre-reqs page
https://github.com/Azure/Enterprise-Scale/wiki/ALZ-Resource-Provider-Recommendations has a full list of required resource providers
Page 3 above also has a line "To successfully deploy an Enterprise-Scale with a predefined [template] (https://aka.ms/caf/ready/accelerator)...", but the 'template' link is directly to the ALZ portal wizard, not to the Bicep or Terraform templates

From these documents it is unclear when reading the first two that the resource provider pre-reqs exist, and so it is easy to miss them.
Suggestion:

Update the pre-reqs document (no. 2) to include a reference to all pre-reqs including a full list of all required resource providers (i.e. consolidate all pre-reqs into a single doc)
Update the Learn doc (no. 1) with an explicit link to the pre-reqs documentation
Update page no 3. above to link 'template' to a Bicep/Terraform/Portal options landing page, not directly to the portal

Thanks @soderholmd, would you be willing to make these updates?

@jtracey93 happy to as long as it looks good to you!

Yup LGTM

Two PRs raised:
https://github.com/MicrosoftDocs/cloud-adoption-framework-pr/pull/5751
https://github.com/Azure/Enterprise-Scale/pull/1735


dowhy version 0.11.1 - Incompatibilities, can be fixed ?

First of all, congratulations on the book! It is a great work.
In parallel with reading, I am trying to run the .pynb in the updated version of dowhy under python 3.11.8, which is closer to my Data Science environment than the python 3.9, and 0.8 dowhy version.
Unfortunately, I am not able to fix the error in Chapter 7 and Chapter 8.
In chapter 7, the cell 21:
estimate = model.estimate_effect(
      identified_estimand=estimand,
      method_name='backdoor.econml.dml.DML',
      method_params={
          'init_params': {
              'model_y': GradientBoostingRegressor(),
              'model_t': GradientBoostingRegressor(),
              'model_final': LassoCV(fit_intercept=False),
          },
          'fit_params': {}}
  )

  print(f'Estimate of causal effect (DML): {estimate.value}')

leads to an ImportError: "Error loading econml.dml.DML. Double-check the method name and ensure that all econml dependencies are installed.".
which looks similar to the cell 5 which also try to use DML:
# Get estimate (DML)
estimate_dml = model.estimate_effect(
    identified_estimand=estimand,
    method_name='backdoor.econml.dml.DML',
    method_params={
        'init_params': {
            'model_y': GradientBoostingRegressor(),
            'model_t': GradientBoostingRegressor(),
            'model_final': LassoCV(fit_intercept=False),
        },
        'fit_params': {}}
)

Complaining that: "ImportError: Error loading econml.dml.DML. Double-check the method name and ensure that all econml dependencies are installed."
Any clue/ guidance on how to fix this?

Hi @Slepetys
It seems that you're missing econml installation in your environment.
You can install it using pip install econml or via conda.
Please let me know if that solved the problem for you.

Thank you @AlxndrMlk , it worked. I had the impression that econml would be automatically installed with dowhy. Also, I tried to install it with conda together with dowhy, and it didn´t work, but it worked using pip.

Great, I am happy to hear it worked @Slepetys!
Wish you a joyful journey with the remaining part of the book & code!


Grid is not showing the column value as and when I update it in the grid object. It is showing only when I refresh the browser. (Ctrl+F5)

Grid is not showing the column value as and when I update it in the grid object. It is showing only when I refresh the browser. (Ctrl+F5)
--resetVxInstance() is not working.. couldn't find an option to reopen the bug, so created it as a new issue.

The requirements were fulfilled as part of another commit.


Thoughts on moving the linalg and math abstractions into a standalone crate?

Hello Smartcore team,
I'm pretty new to the rust language, and have been working on a personal machine learning project to try to learn the language a bit better. In the process of looking for good code examples, I came upon this library, and am impressed with the organization and level of abstraction present in some modules. Particularly, I keep thinking about how useful it would be to develop my personal project against the interface provided by the n-dimensional array/vector/real number abstractions present in the linalg and math modules of this crate.
What are your thoughts on making those modules, linalg and math, part of a standalone crate that Smartcore then depends on? I feel like as those abstractions continue to be refined (e.g. https://github.com/smartcorelib/smartcore/pull/108), they could become an invaluable part of the ML/AI ecosystem in rust.
If this isn't something you're all interested in, no worries! Just a thought and figured I'd put it out there.
Cheers, from an aspiring rust developer!
-Sean

I think that we should move in this direction

I don't know. I have picked up #108 and it looks good enough to give it a shot and see, I will push new commits in the PR as soon as I solved all the conflicts with current branch. Before thinking about this we need to have the PR finalised.
There are already stand-alone libraries that do linear algebra in Rust, what would be the extra provided but our package?

I think that we can do this after #108, my idea is not that the lineal algebra crate is needed but that we could separate smartcore in several crates so people can install only what they need. For instance, smartcore-naive-bayes, smartcore-dataset, etc. We always could re-import all in a main crate smartcore. This could improve compilation times for people that don't need everything

I understand, that is how Linfa is structured. I think this is not the time as the library is quite under-development, maybe when we reach version ~0.5? I mean this sounds adding some overhead in terms of organisation and operations and we have to focus on implementation I think. I would prefer to wait for some fixes and the big refactoring to be done before even thinking about this; for now I would just add a label like "postponed" and pick it up later.

Part of the reason I chose Smartcore over Linfa was because having everything contained in a single package made browsing the documentation and code a lot easier to get started with. There are parts of the Linfa documentation that are now out of sync across packages, and all the packages are interdependent anyway between the core, datasets, and whatever algorithm you want you need to be on matching versions, and having to specify each feature that I need in each package (inter-package co-dependencies aren't well documented) was a lot of asking the compiler what am I missing now...

Just want to second @montanalow on consistency across crates. I actually chose smartcore for exactly the same reason! Maybe feature-gating would be worth considering? I could imagine one for classification and one for regression.

Thanks for the feedback.
I will close this issue then since that seems to be one of the selling points of smartcore.
I agree that we could then use more feature-gating


Trained model

Hello,
Thank you very much for providing this exciting tool! As training on the provided data generally takes a long time, are there already-trained models or super-resolved gene expressions for the data used here? It would be greatly helpful for us to quickly understand what the super-resolved data will look like. Thanks!
Best,
Hao

Hi Hao, Sorry for my late reply. I think this is a good suggestion, but we will need to figure out somewhere to host the model. I'll keep this in mind and see if we can find a solution.

https://huggingface.co/ might be an option to host trained models.

Hi @ludvb , Just wondering whether the trained models are available now? Thank you!


Interrupt the thinking state and then go to the listening state.

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:
We want Amazon to tell you how to interrupt the thinking state and then go to the listening state.
What is the expected behavior?

What behavior are you observing?

Provide the steps to reproduce the issue, if applicable:

Tell us about your environment:

What version of the AVS Device SDK are you using?
  <x.y.z>

Tell us what hardware you're using:

[ ] Desktop / Laptop
[ ] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux

Hello liunanxuan,
Interrupting the Thinking state is not something we currently support.  When Thinking is in progress, the SDK's AudioInputProcessor explicitly prevents barge-in, as per the AVS
SpeechRecognizer specification.
Hope that helps,
-SWH

Thanks for your support. But we can see that your company's product Echo device can support this behavior.

Hello liunanxuan,
Perhaps I am not understanding what you are asking for.  Can you give me a step by step example of what you are experiencing with an Echo product that you can not replicate with the SDK?
Thank you,
-SWH

We want to achieve this behavior in order to improve the user experience.
Voice: alexa.what is the weather like?
State:IDLE ->RECOGNIZING
AVS: StopCapture directive
State:RECOGNIZING -> BUSY
In the BUSY state, the voice wakes up "alexa" again. We hope to interrupt the last voice conversation and reopen a new round of voice conversations.

Thanks for your support.
We see that the ECHO setting can support the behavior I described above.

Hello liunanxuan,
I have not been able to reproduce the behavior you describe on my Echo.  When I interrupt the Echo's flashing blue busy state with Alexa it seems be ignored.  However, often when I attempt this, Alexa responds quickly enough that speaking Alexa overlaps the start of the response and truncates it, allowing my subsequent utterance to be processed.
I get the sense that I am still missing something.  Maybe if you provide an audio recording of the interaction with an Echo that you want to achieve, I will better understand what you are asking for.
Thank you,
-SWH

Thanks for your support.
It seems that standard authentication does not support think interrupts.
Thank you very much for your answer.

Is there any difficult allowing cancel a recolonization in THINKING state?


Installation instructions need to tell user to set up their preferred python before install

Can a note be added to the installation instructions telling people to make certain their preferred python is the path before doing an install.  In particular, have the install fail immediately.   This may be dune specific but I think a lot of people are going to have issues with compatibility if they build incorrectly.

I think that whether the user uses "setup.py" to install the product or "pip", in both cases it is necessary to have their Python set up. Otherwise neither one of the mechanisms would work. I think how exactly the user sets up their preferred Python is beyond the scope of MetaCat documentation.


How would one implement a timer based loop with this plugin?

Hi,
There are very few examples on the web which use this plugin.
In my use-case I am trying to move an endless loop that uses the camera for motion-detection into an isolate.
So ideally I'd like to create a timer based loop inside the isolate
I kind-of got it to work (testing with the camera flash), but this feels like a hack:
    messenger.listen((msg) async {
   messenger.send('received command: ' + msg);
if (msg == 'stop') {
  run = false;
}

if (msg == 'start') {
  run = true;
}

while (run) {
  await Future<void>.delayed(Duration(seconds: 1));
  toggleFlash();
}

 TorchLight.disableTorch(); //make sure that the light is off in the end

 });
The reason I don't trust this approach is.... while trying different things I once forgot the "await" in the above code snippet.
The app tried to turn the flash on/off as fast as it could, and this resulted in the following warning in the debug console:
I/Choreographer(13526): Skipped 116 frames!  The application may be doing too much work on its main thread.
Why did the main thread get blocked by something going wrong in the isolate?
Could you advise how we are intended to create timer based loops  with this plugin?

I don't really think this is anything to do with this plugin in special. :-))
You have several ways to create a periodic timer in Flutter and none of them is about awaiting repeatedly for every second. The most obvious choice would be Timer.periodic() where you provide a callback that does just what you want it to do. You will probably also want to store the timer object itself and then you can call its cancel() when you want to stop it.

most obvious choice would be Timer.periodic()

Of course you are 100% correct.
I did try that first and erroneously concluded: "..didn't work"
I was extending your included example... which has one line that ends the isolate after the first run
I wasn't clever enough to connect those dots.
So now I have timer.periodic() sitting above messenger.listen()  and it all appears to work as expected.

Then we're happy. :-)
Actually, don't look for specific examples regarding this plugin on the net because there's nothing really specific. Look for examples about isolates in general. This plugin only really makes handling the isolates easier but they're not any different from any other isolates.


Add regex to filter out premature line breaks

This prevents text alignment issues, most visible on iPads, as in #41

Sorry! Too many commits! Let me try to make another one with just the regex addition


update comments and avoid early returns

I added some info to the comments because I wanted to explain every detail as to how things work. I also change the code to remove early returns, as I think it is clearer.
Just opening a PR in case I made any mistakes, but I'd like to merge soon. All tests still pass.

Going to merge this because there's another important PR I want to make after it


Add logger section to host.json schema

Related portal issue: https://github.com/Azure/azure-functions-ux/issues/1884

/cc @brettsam

This is now in dev and v1.x and the schemastore PR is out: https://github.com/SchemaStore/schemastore/pull/371


native change event not dispatched when change

Prerequisites

[x] I have searched for similar issues in both open and closed tickets and cannot find a duplicate
[ ] The issue still exists against the latest master branch of Select2
[x] This is not a usage question (Those should be directed to the community)
[x] I have attempted to find the simplest possible steos to reproduce the issue
[ ] I have included a failing test as a pull request (Optional)

Steps to reproduce the issue

create a select2 box and run the following code

<select id="sel">
<option value="1">11</option>
<option value="2">22</option>
</select>
<script>
var elem = document.getElementById('sel');
elem.addEventListener('change', function() { alert('event listener'); } );
$("sel").select2();
</script>

Whatever you do here on the browser, alert does not show up.
Expected behavior and actual behavior
I expect 'event listener' alert will show up when I change the selection.
Environment
Browsers

[x] Google Chrome
[ ] Mozilla Firefox
[ ] Internet Explorer

Operating System

[ ] Windows
[ ] Mac OS X
[x] Linux
[ ] Mobile

Libraries

jQuery version: 2.2.3
Select2 version: 4.0.2

Isolating the problem

[ ] This bug happens on the examples page
[x] The bug happens consistently across all tested browsers
[ ] This bug happens when using Select2 without other pluigns
[ ] I can reproduce this bug in a jsbin

Select2 uses jQuery's trigger function to handle events, which doesn't fire native DOM events. You can use a simple modification of the code to swap the jQuery trigger for a native DOM one:
var change = new Event('change')

And replace every change event with:
$element[0].dispatchEvent(change)

The reasons for this are discussed in #1908.


Remove a fractal store

This is a...

[x] feature request
[ ] bug report
[x] usage question

I have an Angular app that potentially allows an infinite number of widgets to be opened. Because each widget contains a form with rather complex logic, I am trying to use the fractal store pattern, giving a widget its own redux store.
By looking at the source code here: https://github.com/angular-redux/store/blob/master/src/components/fractal-reducer-map.ts, it seems that there is currently no way to remove local reducers from reducerMap. If I’m reading the source code correctly, reducerMap will keep growing, resulting in a memory leak.
My questions are therefore:

Is fractal store the correct pattern to use for my use case?
Is there a way to properly remove a sub store after it is configured, so there is no memory leak? If not, this would be a feature request.

Thank you!

You are correct - I did not think of the case where components come and go. Or rather, I made the assumption that the substores would be keyed by some kind of persistent Id that could be re-used.
This is a good feature request. Unfortunately I'm not heavily involved in this project right now having changed jobs.  However if you wanted to take a stab at it, one possible implementation would involve creating and exposing a destroySubStore method that would

fire an internal action (e.g. @angular-redux::cleanup_fractal_store)
remove all registered reducers rooted at or under that state path
have rootFractalReducer listen for that action and delete the corresponding state from the store.

@e-schultz does any of that make sense?


Capture standard out and error

For troubleshooting purposes it would be great if the output of an external application would be captured into a Sublime buffer. At the moment, you just don't see anything and wonder if the application is actually run or generated an error.

You're right. I'll add the echo of the execution result to sublime console.

The new version captures the error message and stdout correctly.


Add thrift diff api

Add thrift diff api which can diff two thrift structs or two thrift
messages. The result is reported as ThriftDiff data structure which
contains diff details of two types (a) fields which look 'similar' by virtue
of their meta data & (b) fields which are exactly same in terms of both
meta data and actual data
This change also add some basic unit tests for the diff api.

@shrijeet mind squashing the 3 commits after addressing the last issue? thx!

@rgs1 squashed.

Oh also the last issue was a non-issue, I intended to diff 'clones'. Did you mean to improve test case further?


Get install process tested and working.

The install process does not work correctly currently, as it forces an install of GDAL. To remedy this, the install instructions should include GDAL install instructions to ensure success. I will need to test out the install of spatialfriend in a virtual environment on my mac, because it does not work for GDAL-related stuff right now!

Turns out the GDAL stuff did work, I just didn't have the right DEM files. Woops!


Tracking issue: Deploy new dapp+extension

The minimum remaining features to complete until we can:

Deploy dapp to app.testnet.penumbra.zone
Deploy extension to chrome web store

[x] https://github.com/penumbra-zone/web/pull/38
[x] #50
[x] #55
[x] #51
[x] #53
[x] https://github.com/penumbra-zone/web/issues/59
[x] #52
[x] https://github.com/penumbra-zone/web/issues/62
[x] https://github.com/penumbra-zone/web/pull/48
[x] https://github.com/penumbra-zone/web/issues/67
[ ] #65
[ ] BIP44 is merged to testnet
[ ] #54

The Firebase hosting in #48 is looking good. Once that PR is merged, I'll try a few manual deploys via the web UI and confirm it works reliably. We don't yet have secrets in place in this repo for Firebase access; I'll wire that up in the meantime while we wait for 48 to land.

The Firebase hosting in https://github.com/penumbra-zone/web/pull/48 is looking good. Once that PR is merged, I'll try a few manual deploys via the web UI and confirm it works reliably.

We followed up with https://github.com/penumbra-zone/web/pull/78 and now the action is passing: https://github.com/penumbra-zone/web/actions/runs/6408559513


Display execution time?

Hey, great extension -- have been loving it so far. One small visual thing, though: the interactive window collapses the output block, hiding the execution time beneath .... It would be great if the execution time could display by default next to the green check. I searched preferences/settings but was unable to find any way to enable this.

I think that would be a request for upstream; this is just for sending blocks of code to be executed at once


Investigate into data loss on page refresh

there was a missing property in the realtime database under projects. property was userUID


Update prometheus object to use baseImage

Right now the Prometheus object that is created by the prometheus-operator component it uses a deprecated parameter called baseImage. It has been replaced by just image.
Following is a log line taken from the prometheus-operator pod:
level=warn ts=2020-08-20T16:24:00.649149163Z caller=operator.go:486
component=alertmanageroperator msg="alertmanager key=monitoring/prometheus-operator-alertmanager,
field spec.baseImage is deprecated, 'spec.image' field should be used instead"

Shouldn't that be something to report and fix upstream?

Shouldn't that be something to report and fix upstream?

Upstream is not on the same prometheus-operator version as us.


Adds ability to pass in children to render

Gives the ability to inject icons etc to the circle, per the attached image.

Thanks!  I like it :)


istio multiple  clusters question

I have a question. I have now deployed two sets of services and placed them in two istio clusters. These two istio clusters have been configured with multiple clusters. Then use gateway+vs to access the same service for both clusters. When both services are normal, the service polls for access. But after I inject the error in the service in cluster B, why can I access it through the gateway of cluster B, why can't I access it at all? It stands to reason that it should not cut to the normal service in the A cluster? ? ?
Who can help me ？？？

how did you install multiclusters? what is version of istio?

@howardjohn can you help me？

Problems with my multi-cluster installation

Same here. What was ur problem? @mark8s


Delete log.json

Didn't mean to commit this.

Current dependencies on/for this PR:

master

PR #60   (this PR)

PR #61

PR #62

PR #63

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: 🔄 Waiting for checks to pass
This pull request is currently waiting for CI and mergeability checks to pass before being merged.
This comment was auto-generated by Graphite.

Job Reference: Xyf5xoMTqneX2jTHoCF0


GSOC22 RFE: k6 + prometheus + quality evaluation

@jainammm now has a working k6 + prometheus extension container which runs k6 then pushes metrics to Prom.
The ask for this issue is to extend that Keptn sequence and add a new task evaluation which will USE those outputted metrics in a Keptn quality gate.
The logical workflow is:

I run a load test with k6 and output metrics to Prometheus (completed)
I use those metrics by asking Keptn to evaluate a quality gate

Note: This workflow gives the benefit of both k6 thresholds (if they fail, step 1 will fail) but also encorporating other metrics in Prom. Meaning we can also evaluate metrics from sources other than k6. In other words, a wholistic quality evaluation.
Demo Shipyard
apiVersion: "spec.keptn.sh/0.2.2"
kind: "Shipyard"
metadata:
  name: "argocd-demo-shipyard"
spec:
  stages:
    - name: "dev"
      sequences:
        - name: "mysequence"
          tasks:
            - name: "test"  # < k6 responds
            - name: "evaluation" # < lighthouse service + sli provider responds

This is done and was demoed on the GSoC call 01/09/2022. YouTube link to follow once it is uploaded.


"Debug adapter has terminated unexpectedly" on Linux

Extension crashes in early stage when used on Linux.
Steps to reproduce:
Open an arbitrary app on Linux in VSCode, generate launch.json and start Launch on Android Emulator configuration. The extension crashes with "Debug adapter has terminated unexpectedly".

Fixed 5644d09feba9d1ff5d6b52ef19bc93f1ae4ef48d, 9e6d8fb722e0371ef6d1a5f2f8bf81359fe842e7 and bad570aa56c1ba481d0370cf34ef3771f36aa315


ses: Factor out makeCompartmentConstructor

This change prepares for creating unique compartment constructors for two scenarios.
First, allowing the start compartment and shared compartments to use variations on their intrinsics.
For example, the start compartment might keep an unsafe Math, Date, or Error, but child compartments must still be safe.
Second, every child compartment must be able to inherit the static module records of their parent compartment through the compartment constructor module map.
This change only indents the compartment constructor in preparation for these changes.
The shim still creates an initial global compartment constructor without tamed or hardened intrinsics.  A future version of lockdown will replace this compartment constructor.
Fixes https://github.com/Agoric/SES-shim/issues/366

Added a commit for a shared compartment prototype, a disabled prototype.constructor, and rebased to resolve conflicts with master.
Since the compartment shim is orthogonal to lockdown shim, the initial objects should be mutable. Lockdown should then harden the initial Compartment constructor, compartment prototype, and shared compartment prototype constructor.
In a subsequent change, we’ll need to make sure that after lockdown, and descendent of the tamed Compartment constructor uses makeCompartmentConstructor to create frozen constructors.
Please look closely into how the prototype methods use the weak map to obtain private fields from this. I don’t think this constitutes a leak, but I’m not yet a trained JS saboteur.

trained JS saboteur.

Nice phrase!

@erights writes:

We need to check how XS wired up multiple compartments.

I suspect a handful of experiments / tests cases are in order. Do you have any specific things I could / should check?
Their examples are quite good... (I think the readme here has fallen behind; don't let it throw you off)
https://github.com/Moddable-OpenSource/moddable/tree/public/examples/js/compartments
If you're willing to look at it with me, I can try to walk you through the C implementation... but it makes me a little dizzy...
fx_Compartment weighs in at 144 lines
https://github.com/Moddable-OpenSource/moddable/blob/public/xs/sources/xsModule.c#L1470-L1614
plus another dozen lines in fxBuildModule
https://github.com/Moddable-OpenSource/moddable/blob/public/xs/sources/xsModule.c#L112-L121

Do all Compartment constructors share the same .prototype? IOW, for all compartment instances c1 and c2, is c1.globalThis.Compartment.prototype === c2.globalThis.Compartment.prototype?
If so, what does cn.globalThis.Compartment.prototype.constructor point at? Is it a cn.globalThis.Compartment for some compartment instance cn? If not, what happens when you do new cn.globalThis.Compartment.prototype.constructor()?
Preferred answers, i.e., what we're planning to spec and implement, follows the precedent of Function:
All compartment constructors share the same .prototype.
That prototype's .constructor points as a useless Compartment constructor that always throws. That useless Compartment constructor does not appear as a Compartment property on any global object.
Attn @phoddie

@erights - The current version of XS in the Moddable SDK does not implement the behavior described above for the Compartment constructor. The next update -- likely available next week -- does.

@erights - The following notes are from Patrick about the current implementation in XS:
Each compartment has its own Compartment constructor:
c1.global.Compartment === c2.global.Compartment: false

All compartments share Compartment.prototype and Compartment.prototype.constructor
c1.global.Compartment.prototype === c2.global.Compartment.prototype: true
c1.global.Compartment.prototype.constructor === c2.global.Compartment.prototype.constructor: true

Which is different from their own Compartment constructor:
c1.global.Compartment.prototype.constructor === c1.global.Compartment: false

What XS did not implement was the Compartment constructor that always throws. Change committed. Now...
new c1.global.Compartment.prototype.constructor

...throws a TypeError. (This will be in the next updated of XS in the Moddable SDK.)

@phoddie Excellent, thanks!


Check the version subcommand as well

helm (a kubernetes package manager) uses a version subcommand. I am not aware of any already installed binaries, which is why I didn't add a new test.

That's a new one!


feat: allow to specify app id when creating a nuxt app

🔗 Linked issue

📚 Description
When creating a new nuxt application via createNuxtApp, it is now possible to overwrite the app id specified in the nuxt config.
This is needed for the storybook module where we create multiple instances of the same nuxt app (in the same website) and would like to give them different ids to preserve their context. See https://github.com/nuxt-modules/storybook/pull/723#issuecomment-2250731275 for more context that triggered this PR.

@danielroe @huang-julien I've tried to use this PR in the storybook module but encountered the following error:
Error: [nuxt] A composable that requires access to the Nuxt instance was called outside of a plugin, Nuxt hook, Nuxt middleware, or Vue setup function. This is probably not a Nuxt bug. Find out more at `https://nuxt.com/docs/guide/concepts/auto-imports#vue-and-nuxt-composables`.
  at definePayloadReviver (/@fs/D:/Programming/nuxt-storybook/node_modules/.pnpm/nuxt@3.13.0_@parcel+watcher@2.4.1_@types+node@22.5.0_encoding@0.1.13_eslint@9.9.0_jiti@1.21.6_3xmfrk4x4fipugkjlwslnycjnu/node_modules/nuxt/dist/app/composables/payload.js?v=728a24b5:125:5)
  at setup (/@fs/D:/Programming/nuxt-storybook/node_modules/.pnpm/nuxt@3.13.0_@parcel+watcher@2.4.1_@types+node@22.5.0_encoding@0.1.13_eslint@9.9.0_jiti@1.21.6_3xmfrk4x4fipugkjlwslnycjnu/node_modules/nuxt/dist/app/plugins/revive-payload.client.js?v=728a24b5:40:27)
  at /@id/virtual:nuxt:D:/Programming/nuxt-storybook/examples/showcase/.nuxt/plugins/client.mjs:33:69
  at executeAsync (/@fs/D:/Programming/nuxt-storybook/node_modules/.pnpm/unctx@2.3.1/node_modules/unctx/dist/index.mjs?v=728a24b5:111:19)
  at setup (/@id/virtual:nuxt:D:/Programming/nuxt-storybook/examples/showcase/.nuxt/plugins/client.mjs:33:43)
  at /@fs/D:/Programming/nuxt-storybook/node_modules/.pnpm/nuxt@3.13.0_@parcel+watcher@2.4.1_@types+node@22.5.0_encoding@0.1.13_eslint@9.9.0_jiti@1.21.6_3xmfrk4x4fipugkjlwslnycjnu/node_modules/nuxt/dist/app/nuxt.js?v=728a24b5:140:66
  at fn (/@fs/D:/Programming/nuxt-storybook/node_modules/.pnpm/nuxt@3.13.0_@parcel+watcher@2.4.1_@types+node@22.5.0_encoding@0.1.13_eslint@9.9.0_jiti@1.21.6_3xmfrk4x4fipugkjlwslnycjnu/node_modules/nuxt/dist/app/nuxt.js?v=728a24b5:217:44)
  at runWithContext (/@fs/D:/Programming/nuxt-storybook/node_modules/.pnpm/@vue+runtime-core@3.4.38/node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js?v=728a24b5:2682:18)
  at callWithNuxt (/@fs/D:/Programming/nuxt-storybook/node_modules/.pnpm/nuxt@3.13.0_@parcel+watcher@2.4.1_@types+node@22.5.0_encoding@0.1.13_eslint@9.9.0_jiti@1.21.6_3xmfrk4x4fipugkjlwslnycjnu/node_modules/nuxt/dist/app/nuxt.js?v=728a24b5:223:24)
  at createNuxtApp/runWithContext (/@fs/D:/Programming/nuxt-storybook/node_modules/.pnpm/nuxt@3.13.0_@parcel+watcher@2.4.1_@types+node@22.5.0_encoding@0.1.13_eslint@9.9.0_jiti@1.21.6_3xmfrk4x4fipugkjlwslnycjnu/node_modules/nuxt/dist/app/nuxt.js?v=728a24b5:37:53)
  at run (/@fs/D:/Programming/nuxt-storybook/node_modules/.pnpm/@vue+reactivity@3.4.38/node_modules/@vue/reactivity/dist/reactivity.esm-bundler.js?v=728a24b5:32:16)
  at runWithContext (/@fs/D:/Programming/nuxt-storybook/node_modules/.pnpm/nuxt@3.13.0_@parcel+watcher@2.4.1_@types+node@22.5.0_encoding@0.1.13_eslint@9.9.0_jiti@1.21.6_3xmfrk4x4fipugkjlwslnycjnu/node_modules/nuxt/dist/app/nuxt.js?v=728a24b5:37:31)
  at applyPlugin (/@fs/D:/Programming/nuxt-storybook/node_modules/.pnpm/nuxt@3.13.0_@parcel+watcher@2.4.1_@types+node@22.5.0_encoding@0.1.13_eslint@9.9.0_jiti@1.21.6_3xmfrk4x4fipugkjlwslnycjnu/node_modules/nuxt/dist/app/nuxt.js?v=728a24b5:140:39)
  at executePlugin (/@fs/D:/Programming/nuxt-storybook/node_modules/.pnpm/nuxt@3.13.0_@parcel+watcher@2.4.1_@types+node@22.5.0_encoding@0.1.13_eslint@9.9.0_jiti@1.21.6_3xmfrk4x4fipugkjlwslnycjnu/node_modules/nuxt/dist/app/nuxt.js?v=728a24b5:159:34)
  at applyPlugins (/@fs/D:/Programming/nuxt-storybook/node_modules/.pnpm/nuxt@3.13.0_@parcel+watcher@2.4.1_@types+node@22.5.0_encoding@0.1.13_eslint@9.9.0_jiti@1.21.6_3xmfrk4x4fipugkjlwslnycjnu/node_modules/nuxt/dist/app/nuxt.js?v=728a24b5:190:11)
  at /@fs/D:/Programming/nuxt-storybook/packages/storybook-addon/dist/preview.mjs:40:9

when calling applyPlugins (see https://github.com/nuxt-modules/storybook/pull/762)
The reason is that I do set the context via getContext("nuxt-app-customid").set(nuxt, true) but later definePayloadReviver calls useNuxtApp() without any appId, which thus falls back to the id nuxt-app; which is not set. As a workaround I now use getContext('nuxt-app').set(nuxt, true). This works but feels a bit like a hack (and I'm not sure if it covers all edge cases).
How is useNuxtApp() (without a nuxt-app id as argument) supposed to work in a multi-app context? Moreover, should callWithNuxt also set the default nuxt-app context to the passed nuxt instance?
(I can open a new issue for these questions, but thought this PR has the required context.)

@tobiasdiez Yes, multi-app support hasn't yet landed. The next step would be a compile time injection of the nuxt app-id in calls to useNuxtApp. For now, it's definitely safer to use nuxt-app as the app id, and I think your workaround is fine.
If you are able to add some tests we can add it to https://github.com/nuxt/ecosystem-ci/ so we ensure any future changes along these lines don't break the storybook integration. 🙏

@tobiasdiez Yes, multi-app support hasn't yet landed. The next step would be a compile time injection of the nuxt app-id in calls to useNuxtApp. For now, it's definitely safer to use nuxt-app as the app id, and I think your workaround is fine.

Thanks for the feedback! I really like the multi-app feature and the possibilities it opens. Big thanks to everyone that worked on it so far!

If you are able to add some tests we can add it to https://github.com/nuxt/ecosystem-ci/ so we ensure any future changes along these lines don't break the storybook integration. 🙏

Sure! https://github.com/nuxt/ecosystem-ci/pull/14


Sass 453: Dividends content iterations

Description
Dividends content updates
Add a link to the relevant story in Jira
https://jira.tools.tax.service.gov.uk/browse/SASS-453
Checklist PR Reviewer
Before Reviewing

[ ]  Have you pulled the branch down?
[ ]  Have you assigned yourself to the PR?
[ ]  Have you moved the task to “in review” on JIRA?
[ ]  Have you checked to ensure all dependencies are up to date?

Whilst Reviewing

[ ]  Have you run the tests?
[ ]  Have you run the journey tests?
[ ]  Have you looked at the JIRA story to make sure all Acceptance Criteria has been met?

After Reviewing

[ ]  Have you checked for merge conflicts?
[ ]  Have you checked to make sure there are no builds in the pipeline before you merge?
[ ]  Have you moved the task to “in pipeline” on Jira?

Checklist PR Raiser
Before creating PR

[ ]  Have you run the tests?
[ ]  Have you run the journey tests?
[ ]  Have you addressed warnings where appropriate?

After PRs been Reviewed

[ ]  Have you checked the PR Builder passes?
[ ]  Have you checked for merge conflicts?
[ ]  Have you checked code coverage isn’t lower than previously?

Needs to be merged alongside https://github.com/hmrc/income-tax-submission-frontend/pull/98, https://github.com/hmrc/income-tax-submission-journey-tests/pull/58 and https://github.com/hmrc/income-tax-submission-performance-tests/pull/21


[Bug] +store_failures config in singular tests not working in Fabric

Is this a new bug in dbt-core?
I believe this is a new bug in dbt-core
I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
The store_failures config is set(false) in a singular test and in the dbt_project.yml at a project lvl(true). This shouldn't work like this according to the config inheritance https://docs.getdbt.com/reference/configs-and-properties
Expected Behavior
store_failures should be false for the singular test but its true.
Steps To Reproduce
Setup a dbt-fabric project
Specify the store_failures config in data_tests(dbt_project.yml) and for the singular test.
Set connection with the fabric data warehouse
dbt_project.yml
version: "1.0.0"
config-version: 2

profile: "default"
...
data_tests:
  +store_failures: true

stg_customers.sql
with customers as (

    select * from {{ ref("raw_customers") }}
)

select * from customers

raw_customers.csv
id,first_name,last_name,email
<EMAIL_ADDRESS>1,Paris, H<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
tst_invalid_id.sql
{{ config(store_failures = false) }}

with invalid as (
select
*
from stg_customers
where id is null
)

select * from invalid

Set connection in your profiles.yml file. (something like this)
jaffle_shop:
  target: dev
  outputs:
    dev:
      authentication: CLI
      database: jaffle-shop-warehouse
      driver: ODBC Driver 18 for SQL Server
      host: <sql end point to the fabric warehouse>
      schema: <schema name>
      threads: 4
      type: fabric

Run dbt test --select tst_invalid_id
It will create an output table in the fabric warehouse.
Environment
- OS: windows 11 pro
- dbt=1.8.1
- fabric=1.8.6

It looks like the config.get(store_failures) is using model or data tests level config. I have created a bug in dbt-adapters https://github.com/dbt-labs/dbt-adapters/issues/395


Test change to see if the IDS-G master protection works.

test PR, no content

I leave this PR open for a few days. Please do not merge the PR, it's only for demo/testing purposes.

Pull request for test purposes. Discarded as decided in IDSA-TSC on 2020-11-25.


Adding text summarisation

Changes

Fixes #5  (issue)
Adding Text summarisation to Gradsflow
Type of change

[x] Documentation Update
[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Great work @gagan3012 ! Could you rename AutoSummarisation to AutoSummarization? Gradsflow should follow the same naming as Flash and Huggingface.

@aniketmaurya Hey I think its ready