npm install gives errors

After cloning open-wc, running npm install returns errors.
Here is what I am getting:
merc@merc-All-Series:~/Development/FORKS/open-wc3$ npm install --verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/bin/node', '/usr/bin/npm', 'install', '--verbose' ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm verb npm-session 1884acf221be5c96
npm info lifecycle @open-wc/root@~preinstall: @open-wc/root@
npm timing stage:loadCurrentTree Completed in 1971ms
npm timing stage:loadIdealTree:cloneCurrentTree Completed in 26ms
npm timing stage:loadIdealTree:loadShrinkwrap Completed in 654ms
npm http fetch GET 304 https://registry.npmjs.org/fsevents 194ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/nan 39ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/bindings 62ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/file-uri-to-path 77ms (from cache)
npm timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 2376ms
npm timing stage:loadIdealTree Completed in 3734ms
npm timing stage:generateActionsToTake Completed in 108ms
npm verb correctMkdir /home/merc/.npm/_locks correctMkdir not in flight; initializing
npm verb lock using /home/merc/.npm/_locks/staging-5665b77b8bd6aa97.lock for /home/merc/Development/FORKS/open-wc3/node_modules/.staging
npm timing action:extract Completed in 261ms
npm timing action:finalize Completed in 102ms
npm timing action:refresh-package-json Completed in 109ms
npm timing action:preinstall Completed in 2ms
npm timing action:build Completed in 2ms
npm timing action:install Completed in 2ms
npm timing action:postinstall Completed in 1ms
npm verb unlock done using /home/merc/.npm/_locks/staging-5665b77b8bd6aa97.lock for /home/merc/Development/FORKS/open-wc3/node_modules/.staging
npm timing stage:executeActions Completed in 512ms
npm timing stage:rollbackFailedOptional Completed in 93ms
npm info linkStuff @open-wc/root@
npm info lifecycle @open-wc/root@~install: @open-wc/root@
npm info lifecycle @open-wc/root@~postinstall: @open-wc/root@

> @open-wc/root@ postinstall /home/merc/Development/FORKS/open-wc3
> npm run build

npm info it worked if it ends with ok
npm verb cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'build' ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm verb run-script [ 'prebuild', 'build', 'postbuild' ]
npm info lifecycle @open-wc/root@~prebuild: @open-wc/root@
npm info lifecycle @open-wc/root@~build: @open-wc/root@

> @open-wc/root@ build /home/merc/Development/FORKS/open-wc3
> lerna run build

Configuring yargs through package.json is deprecated and will be removed in a future major release, please use the JS API instead.
Configuring yargs through package.json is deprecated and will be removed in a future major release, please use the JS API instead.
lerna notice cli v3.4.3
lerna info versioning independent
lerna info Executing command in 4 packages: "yarn run build"
lerna ERR! yarn run build exited 127 in '@import-maps/resolve'
lerna ERR! yarn run build stdout:
yarn run v1.22.0
$ babel src --out-dir dist --copy-files --include-dotfiles
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

lerna ERR! yarn run build stderr:
/bin/sh: 1: babel: not found
error Command failed with exit code 127.

lerna ERR! yarn run build exited 127 in '@import-maps/resolve'
lerna WARN complete Waiting for 3 child processes to exit. CTRL-C to exit immediately.
npm verb lifecycle @open-wc/root@~build: unsafe-perm in lifecycle true
npm verb lifecycle @open-wc/root@~build: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/merc/Development/FORKS/open-wc3/node_modules/.bin:/usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/merc/Development/FORKS/open-wc3/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
npm verb lifecycle @open-wc/root@~build: CWD: /home/merc/Development/FORKS/open-wc3
npm info lifecycle @open-wc/root@~build: Failed to exec build script
npm verb stack Error: @open-wc/root@ build: `lerna run build`
npm verb stack spawn ENOENT
npm verb stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
npm verb stack     at ChildProcess.emit (events.js:198:13)
npm verb stack     at maybeClose (internal/child_process.js:982:16)
npm verb stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
npm verb pkgid @open-wc/root@
npm verb cwd /home/merc/Development/FORKS/open-wc3
npm verb Linux 4.15.0-88-generic
npm verb argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
npm verb node v10.19.0
npm verb npm  v6.13.4
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! @open-wc/root@ build: `lerna run build`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the @open-wc/root@ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm verb exit [ 1, true ]
npm timing npm Completed in 2157ms

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the @open-wc/root@ postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm verb exit [ 1, true ]
npm timing npm Completed in 11418ms

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/merc/.npm/_logs/2020-03-02T05_27_35_283Z-debug.log
merc@merc-All-Series:~/Development/FORKS/open-wc3$

I tried a few things to hammer it in, and couldn't work out what was going on. It looks like lerna is not getting installed.
In case it helps:
 node --version
v10.19.0
merc@merc-All-Series:~/Development/FORKS/open-wc3$

We use yarn workspaces, can you try with yarn install?

Done. I had  never used yarn before. I thought it was totally compatible with NPM -- well, I was obviously wrong.
Would you recommend yarn for my own projects?

For regular projects there isn't much difference in everyday use, there are pros and cons for both. Yarn workspaces for monorepos is really good though, npm doesn't have that.

Thanks. I will look into it -- although I don't have monorepos to manage
(and hopefully never will!)
On Mon, 2 Mar 2020 at 20:12, Lars den Bakker<EMAIL_ADDRESS>wrote:

For regular projects there isn't much difference in everyday use, there
are pros and cons for both. Yarn workspaces for monorepos is really good
though, npm doesn't have that.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/open-wc/open-wc/issues/1395?email_source=notifications&email_token=AAQHWXQD3IUU7JJCKPICCDLRFOPDHA5CNFSM4K7M2JA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENPCMGI#issuecomment-593372697,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQHWXUD3O7VP7RWPOMWNFDRFOPDHANCNFSM4K7M2JAQ
.


Ensure that resource paths begin with "/" as required by Tomcat 8.

This fixes https://issues.apache.org/jira/browse/MTOMCAT-302

merged. Thanks you can close this pr.


17042 Fixed draft restoration bug + fixed validation flags error

Issue #: bcgov/entity#17042
Description of changes:
- app version = 4.7.17
- added check before restoring approval type from state filing
- misc cleanup/comments
- fixed some Action declarations
- fixed some filing data typing
- set state filing before parsing draft restoration (which depends on it)
Collateral fixes:
- fixed scrollToTop async (and callers)
- fixed scrollToTop typing
- added validation flags comments
- fixed incorrect validation flag order in state model
- fixed mockImplementation variable issue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

/gcbrun

Temporary Url for review: https://business-edit-dev--pr-563-ucr8v2i7.web.app

/gcbrun

Temporary Url for review: https://business-edit-dev--pr-563-ucr8v2i7.web.app


Follow up to #87

@annehaley, please address the remaining unresolved comments from @zachmullen in #87 as a new PR if necessary

replaced by #12, #13 and #14


Docs: Transitive dependencies docs dropped with docs refactor

The section about how to use transitive dependencies was last when refactoring documentation in #566.
Pick the documentation written in #579 and add it to the appropriate section in current docs.

I already merged #621 to rectify this. Do you think that solves this issue or should we add the original explanation somewhere as well?

The only downside I see with the current fix is that it does not have a name. So it will be hard to refer to it. Both in terms of links (no header) and also anywhere else in the docs where you want to talk about it.

:+1: Solved with #627


new logo/icon

Hi, I am a graphic designer, I want to help others in graphic design.
After I reviewed your project, you have no logo on this project. Therefore I want to contribute to this project by creating a new logo / icon. what do you think?

Feel free to do it! We could use it as the sample app icon

I have design logo for this project. what do you think ? do you l like it ?

half circle design that shaped the letter C that I took it from the word Complete which initials C and A in the letter C that I took it from the Auto word initials A. and icon green colored icon describes the complete.

how about the logo. I really hope for a positive response from you.


out_file plugin should allow customizing permissions

When using fluentd to write logs to disk using out_fule plugin, for certain sensitive logs, it would be good to be able to restrict the ownership and access of the files.  At the moment, all output files are owned by the user fluentd runs as, and with default umask, so probably world-readable.
Ideally we'd be to be able to configure for each file, the owner, group, and standard Unix permissions (eg 0600).
Environment information - fluentd 0.12, in docker container on CentOS 7.5.

You can set file_permission in global system section.
Note that this changes all generated files.
<system>
  file_permission 600
</system>

https://docs.fluentd.org/v1.0/articles/system-config#file_permission

fluentd 0.12

Ah, I missed it. This feature is since v1

I tried
<system>   file_permission 600 </system>
but changed only read and execute. write not set.
fluentd in docker with ver 1.10.4-1.0


CUSTOM_SECURITY_MANAGER not working in 0.34.0rc1

App routing is broken in the latest release with respect to Custom Security Manager.  Please deprecate this release.
Expected results
When attempting to access the root url for Superset, this should redirect to the login page if the user is not logged in.  This redirect is failing to work when AUTH_TYPE = AUTH_OID
Actual results
The app routes to /superset/welcome
Screenshots
If applicable, add screenshots to help explain your problem.
How to reproduce the bug

Use a custom security manager, akin to https://stackoverflow.com/questions/54010314/using-keycloakopenid-connect-with-apache-superset#54024394
Deploy
Navigate to bare url

Environment
(please complete the following information):

superset version: 0.34.0rc1
python version: 3.6
node.js version: 10.0
npm version: npm -v

Checklist
Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
This works perfectly fine on 0.33.0rc1, so I have had to downgrade.  Because of this issue, where the routing is not correct, I believe this issue should be resolved and 0.34.0rc1 should be pulled.

Hi @ericandrewmeadows ,
We had the same issue as explained in that StackOverflow question although we are using a different openId connect provider called IdentityServer4.
We, therefore, did a custom security manager that does the integration by extending the superset security manager. I would be happy to provide my approach if need be. It involved a little bit of code and understanding of the workings of openId connect(built on top of OAuth2)

Hi @ericandrewmeadows,
Can you please provide:

server logs for 0.33.0rc1 and 0.34.0rc1?
Your custom SM

This could be a FAB related issue, feel free to open an issue there so we can narrow it down

App routing is broken in the latest release with respect to Custom Security Manager. Please deprecate this release.

IMO, the 0.34 release has a good deal of bug fixes/improvements that merit releasing 0.34 rather than 0.33. As 0.34 will (hopefully) become the first official ASF Superset release, there will for sure be many bugs that surface as people try it out. Rest assured committers (myself included) will give reported issues high priority to make sure that bugs are ironed out of the 0.34 branch (along with master) as quickly as possible.

Custom SM:
# https://stackoverflow.com/questions/54010314/ ...
#   using-keycloakopenid-connect-with-apache-superset#54024394
from flask import redirect, request
from flask_appbuilder.security.manager import AUTH_OID
from superset.security import SupersetSecurityManager
from flask_oidc import OpenIDConnect
from flask_appbuilder.security.views import AuthOIDView
from flask_login import login_user
from urllib.parse import quote
from flask_appbuilder.views import ModelView, SimpleFormView, expose
import logging
import os

# Testing Okta
from okta import UsersClient
from okta.framework.ApiClient import ApiClient

# DELETE
import json

DEFAULT_USER_ROLE = 'Gamma'
USER_ROLE_TRANSLATION_DICT = {
    'Charts Admin': 'Admin',
    'Charts Alpha Users': 'Alpha',
    'software': 'Software',
}

class AuthOIDCView(AuthOIDView):
    def get_given_and_family_name_from_name(self, info):
        name = info.get('name')
        first_space_location = name.find(' ')

        given_name = info.get('given_name', name[:first_space_location])
        family_name = info.get('family_name', name[first_space_location+1:])
        return (given_name, family_name)

    def get_user_info(self, okta_client, uid):
        response = ApiClient.get_path(okta_client, '/{0}'.format(uid))
        user_info = json.loads(response.text)
        return user_info

    def get_account_creation_info(self, user_info):
        profile = user_info['profile']
        username = profile.get('login')
        first_name = profile.get('firstName')
        last_name = profile.get('lastName')
        email = profile.get('email')
        return (username, first_name, last_name, email)

    def create_user(self, sm, user_info):
        (username, first_name, last_name, email) =\
            self.get_account_creation_info(user_info)
        role = sm.find_role(DEFAULT_USER_ROLE)
        user = sm.add_user(username, first_name, last_name, email, role)
        return user

    def get_group_info(self, okta_client, uid):
        response = ApiClient.get_path(okta_client, '/{0}/groups'.format(uid))
        group_info = json.loads(response.text)
        return group_info

    def get_group_membership(self, group_info):
        group_membership = [group["profile"]["name"] for group in group_info]
        return group_membership

    def get_or_create_roles(self, sm, group_membership):
        roles = [
            sm.add_role(USER_ROLE_TRANSLATION_DICT.get(group, group))
            for group in group_membership
        ]
        return roles

    def update_user_roles(self, sm, user, group_info):
        group_membership = self.get_group_membership(group_info)
        roles = self.get_or_create_roles(sm, group_membership)
        existing_roles = user.roles
        for role in roles:
            if role in existing_roles:
                continue
            user.roles.append(role)
            logging.info(f'Role added to {user.username}: {role.name}')
        return user

    @expose('/login/', methods=['GET', 'POST'])
    def login(self, flag=True):
        sm = self.appbuilder.sm
        oidc = sm.oid

        @self.appbuilder.sm.oid.require_login
        def handle_login():
            uid = oidc.user_getfield("sub")
            user = sm.auth_user_oid(uid)

            okta_client = UsersClient(
                os.environ['ORG_URL'],
                os.environ['OKTA_AUTH_TOKEN']
            )

            user_info = self.get_user_info(okta_client, uid)
            user_active = user_info['status'] == "ACTIVE"

            if not user_active:
                return
            if user is None:
                user = self.create_user(sm, user_info)
            logging.info(f"User:  {user}")

            group_info = self.get_group_info(okta_client, uid)
            user = self.update_user_roles(sm, user, group_info)
            sm.update_user(user)

            login_user(user, remember=False)
            return redirect(self.appbuilder.get_url_for_index)

        return handle_login()

    @expose('/logout/', methods=['GET', 'POST'])
    def logout(self):

        oidc = self.appbuilder.sm.oid

        oidc.logout()
        super(AuthOIDCView, self).logout()
        redirect_url = request.url_root.strip('/') + self.appbuilder.get_url_for_login

        return redirect(oidc.client_secrets.get('issuer') + '/protocol/openid-connect/logout?redirect_uri=' + quote(redirect_url))

class OIDCSecurityManager(SupersetSecurityManager):
    def __init__(self, appbuilder):
        super(OIDCSecurityManager, self).__init__(appbuilder)
        if self.auth_type == AUTH_OID:
            self.oid = OpenIDConnect(self.appbuilder.get_app)
        self.authoidview = AuthOIDCView

Sorry - accidentally opened & closed.
In my superset_config.py, this is how I am implementing the OAuth:
from flask_appbuilder.security.manager import AUTH_OID
    from create_client_secret_json import create_client_secret_json
    from security import OIDCSecurityManager

    SECRETS_FILENAME = 'client_secret.json'
    client_secrets_dict = create_client_secret_json(SECRETS_FILENAME)
    os.environ['ORG_URL'] = client_secrets_dict['issuer']

    AUTH_TYPE = AUTH_OID
    OIDC_CLIENT_SECRETS = SECRETS_FILENAME
    OIDC_ID_TOKEN_COOKIE_SECURE = True
    OIDC_USER_INFO_ENABLED = True
    AUTH_USER_REGISTRATION = True
    AUTH_USER_REGISTRATION_ROLE = 'Gamma'
    OIDC_SCOPES = ["openid", "email", "profile", "groups"]
    OIDC_INTROSPECTION_AUTH_METHOD = os.environ['OID_AUTH_METHOD']
    CUSTOM_SECURITY_MANAGER = OIDCSecurityManager

@villebro - my main item is that rc1 broke custom security, and is a large issue.  I am also beginning to make commits and help this as well, I am just waiting on some people to comment on the features I am contributing on.

i need to create an authentication with jwt identity to access api inside it

Any updates here?

Have you tried to disable Talisman, TALISMAN_ENABLED=False?


[SPARK-19599][SS]Clean up HDFSMetadataLog for Hadoop 2.6+

What changes were proposed in this pull request?
SPARK-19464 removed support for Hadoop 2.5 and earlier, so we can do some cleanup for HDFSMetadataLog.
This PR includes the following changes:

Remove the workaround codes for HADOOP-10622.
Remove unnecessary writer: (T, OutputStream) => Unit and just call serialize directly.

How was this patch tested?
Jenkins

Merged build triggered.

Merged build started.

Test build #72890 has started for PR 16932 at commit 81bcc48.

Test build #72890 has finished for PR 16932 at commit 81bcc48.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72890/
Test FAILed.

retest this please

Test build #72898 has started for PR 16932 at commit 81bcc48.

Test build #72899 has started for PR 16932 at commit 14a199c.

Test build #72899 has finished for PR 16932 at commit 14a199c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72899/
Test FAILed.

retest this please

Test build #72906 has started for PR 16932 at commit 14a199c.

Test build #72898 has finished for PR 16932 at commit 81bcc48.

This patch fails from timeout after a configured wait of `250m`.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72898/
Test FAILed.

Test build #72906 has finished for PR 16932 at commit 14a199c.

This patch fails from timeout after a configured wait of `250m`.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72906/
Test FAILed.

Test build #72954 has started for PR 16932 at commit 38444ea.

LGTM!

Test build #72954 has finished for PR 16932 at commit 38444ea.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72954/
Test PASSed.

Merged build finished. Test PASSed.

Thanks! Merging to master.

Since this change is minor and safe, I also cherry-picked to 2.1 to avoid merge conflicts in future.

The final code change doesn't assume Hadoop 2.6 right?

The final code change doesn't assume Hadoop 2.6 right?

Right.


SmokeTest -> Master -- Preview ToC Updates

Docs Build status updates of commit 375fb09:
:warning: Validation status: warnings

File
Status
Preview URL
Details

preview-packages/docs-ref-autogen/overview/FormRecognizer.yml
:warning:Warning
View (azure-node-preview)
Details

preview-packages/docs-ref-autogen/overview/Search.yml
:warning:Warning

Details

preview-packages/docs-ref-autogen/overview/CognitiveServices/SpeechService.yml
:warning:Warning
View (azure-node-preview)
Details

preview-packages/docs-ref-autogen/overview/KeyVault.yml
:warning:Warning
View (azure-node-preview)
Details

preview-packages/docs-ref-autogen/overview/KeyVault/Secrets.yml
:warning:Warning
View (azure-node-preview)
Details

preview-packages/docs-ref-autogen/overview/CognitiveServices.yml
:warning:Warning
View (azure-node-preview)
Details

preview-packages/docs-ref-autogen/overview/TextAnalytics.yml
:warning:Warning
View (azure-node-preview)
Details

preview-packages/docs-ref-autogen/overview/KeyVault/Keys.yml
:warning:Warning
View (azure-node-preview)
Details

preview-packages/docs-ref-autogen/overview/ServiceBus.yml
:warning:Warning
View (azure-node-preview)
Details

preview-packages/docs-ref-autogen/overview/KeyVault/Certificates.yml
:warning:Warning
View (azure-node-preview)
Details

preview-packages/docs-ref-autogen/overview/Core.yml
:warning:Warning
View (azure-node-preview)
Details

:warning:Warning

Details

preview-packages/docs-ref-mapping/reference.yml
:white_check_mark:Succeeded

preview-packages/docs-ref-autogen/overview/FormRecognizer.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.

preview-packages/docs-ref-autogen/overview/Search.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.
[Warning-DuplicateUids] Uid(azure.nodejs.sdk.landingpage.services.search.pre) has already been defined in docs-ref-services/search.md.

preview-packages/docs-ref-autogen/overview/CognitiveServices/SpeechService.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.
[Warning-DuplicateUids] Uid(microsoft-cognitiveservices-speech-sdk.pre) has already been defined in docs-ref-services/speech-service.md.

preview-packages/docs-ref-autogen/overview/KeyVault.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.
[Warning-DuplicateUids] Uid(azure.nodejs.sdk.landingpage.services.keyvault.pre) has already been defined in docs-ref-services/key-vault.md.

preview-packages/docs-ref-autogen/overview/KeyVault/Secrets.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.
[Warning-DuplicateUids] Uid(azure.nodejs.sdk.landingPage.services.keyvault.Secrets.pre) has already been defined in docs-ref-services/keyvault-secrets-readme.md.

preview-packages/docs-ref-autogen/overview/CognitiveServices.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.
[Warning-DuplicateUids] Uid(azure.nodejs.sdk.landingpage.services.cognitiveservices.pre) has already been defined in docs-ref-services/cognitive-services.md.

preview-packages/docs-ref-autogen/overview/TextAnalytics.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.
[Warning-DuplicateUids] Uid(azure.nodejs.sdk.landingpage.services.textanalytics.pre) has already been defined in docs-ref-services/ai-text-analytics-readme.md.

preview-packages/docs-ref-autogen/overview/KeyVault/Keys.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.
[Warning-DuplicateUids] Uid(azure.nodejs.sdk.landingPage.services.keyvault.Keys.pre) has already been defined in docs-ref-services/keyvault-keys-readme.md.

preview-packages/docs-ref-autogen/overview/ServiceBus.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.
[Warning-DuplicateUids] Uid(azure.nodejs.sdk.landingpage.services.servicebus.pre) has already been defined in docs-ref-services/service-bus.md.

preview-packages/docs-ref-autogen/overview/KeyVault/Certificates.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.
[Warning-DuplicateUids] Uid(azure.nodejs.sdk.landingPage.services.keyvault.Certificates.pre) has already been defined in docs-ref-services/keyvault-certificates-readme.md.

preview-packages/docs-ref-autogen/overview/Core.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.
[Warning-DuplicateUids] Uid(azure.nodejs.sdk.landingpage.services.core.pre) has already been defined in docs-ref-services/core-http-readme.md.

[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "docs-ref-services/search.md, preview-packages/docs-ref-autogen/overview/Search.yml".
[Warning-DuplicateOutputFiles] Multiple input files would generate to the same output path overwriting each other. Please rename at least 1 of following input files to ensure that there will be only one file to generate to the output path: "docs-ref-services/search.md, preview-packages/docs-ref-autogen/overview/Search.yml".

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Mismatch implementation wrt equation in the paper?

In your paper "Unified Focal loss: Generalising Dice and cross entropy-based losses to handle class imbalanced medical image segmentation" in Elviser, equation (20) is like :

But, in line 277 you have multiplied cross-entrocpy of the 'common' class instead of rare class a mentioned in paper. Which one is correct?

Hi Nelson,
That is a good spot, thank you for pointing it out! There is a mistake in the equation in the paper which should say log(pt,c) rather than log(pt,r). The code is correct :)
I hope that answers your question.
Best wishes,
Michael


{   "message": ""The requested name is valid, but no data of the requested type was found. (management.azure.com:443)"" }

{
"message": ""The requested name is valid, but no data of the requested type was found. (management.azure.com:443)""
}

sign in error in Azure Storage explorer

can anyone help here

@peteMorgan007 thanks for reaching out.  Can you please follow these steps (https://learn.microsoft.com/en-us/troubleshoot/azure/azure-storage/storage-explorer-troubleshooting?tabs=Windows#authentication-logs) to gather Authentication Logs. Please make sure to follow all the steps, including enabling Verbose Authentication Logging, and ideally clearing the contents of the ServiceHub/logs folder before starting the Storage Explorer session where you reproduce the sign in failure.
Thanks!

Closing due to lack of response. This issue will no longer be monitored. If you need further help, we recommend opening a support ticket via the Azure portal. Alternatively you can open a new issue here.


S3 Client customer logger doesn't print debug message properly

S3 Client customer logger doesn't print debug message properly #4650
There was a previous issue fixed. However, I found that the following files are still printing only 'endpoints' without useful debug messages.
packages/util-endpoints/utils/evaluateEndpointRule.ts
packages/util-endpoints/utils/evaluateConditions.ts
packages/util-endpoints/utils/evaluateCondition.ts
I would apply the same patch to these files.

Generally, the Logger interface methods use rest parameters. If you see only endpoints, it is probably due to the logger implementation only looking at the first argument rather than all of them.
That being said, I think it's ok to make the messages print a single string in the spots you mentioned.

Based on my understanding, pino and winston are two of the most popular logging libraries for Node.js.
While they do not follow strictly the logger interface, it would be beneficial for greater compatibility with these widely-used options.

#1268 was merged, closing this issue.


Resume playing current playlist?

Is there a way to update the code to just play/pause the player (play whatever is on the current playlist), rather than play random tracks?
Even better would be a way of selecting something from the library, e.g. play music by ARTIST.

I am in process of adding some functionality to muzak and improving the utterance definitions to handle a broader range of terms.
One question I have is how do I know what methods and corresponding parameters are available on the Player object?
For example, I'd like to implement 'play' (as opposed to random), 'next track', 'last track', 'pause', among others.

tmn103 - my fork has this implemented now, with the addition to a randomization command and other functionality.  I plan to add the ability to search and play by artist, album or track name in the future.


Button URL no Work on P.Ajax GridView

The page not reloaded when i use kartik\grid\GridView with pAjax Setting true. the page not reloaded so the form input cannot show the data that i want to edit..

Please report to kartik. This tracker is about framework issues.

ok thanks.


allow specifying InfluxDB URL with username/password, database, port

what:
allow specifying different influxdb username/password, port database

why:
extended security and configuraility

Checklist:

[X] Documentation
[x] Tests N/A
[X] Ready to be merged
[x] Added myself to contributors table  N/A

LGTM, thanks @darashenka

Released in 2.1


Add Vintage color scheme to defaults; fixes #1781

This change adds the "Classic" color scheme to the ones in the default profiles.json settings file, with the colors suggested by @ocalvo in issue #1781. I named it "Vintage" per @DHowett-MSFT's suggestion.
PR Checklist

[x] Closes #1781
[x] CLA signed - N/A; I work for Microsoft
[ ] Tests added/passed - N/A; see discussion below
[x] Requires documentation to be updated - N/A; no doc update required
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan.

Validation Steps Performed
All manual tests. I didn't feel it was necessary to add any automated tests because the only ones that would make sense would be ones to check that other default color schemes aren't regressed, and we don't have any tests for default settings today (presumably because they change too often!).

Deleted profiles.json, started Terminal.
Verified that the output "Vintage" color scheme existed in the newly created profiles.json file.
Verified that "Vintage" diffed equal to the "Classic" scheme in the issue, apart from the name and the addition of  "background" and "foreground" colors, which I made equal to the "black" and "white" ones respectively.
Verified that I could set a profile to use Vintage and that the colors changed accordingly.

/azp run


Allow Bazel 6 users to opt-in for rules_apple 2.x

Regressed in https://github.com/bazel-ios/rules_ios/pull/773

@justinseanmartin To confirm the sed to use rules_apple 2.x on CI + Bazel 6.1.2 I checked the events here and saw this:
  {
    "id": {
      "fetch": {
        "url": "https://github.com/bazelbuild/rules_apple/releases/download/2.5.0/rules_apple.2.5.0.tar.gz"
      }
    },
    "fetch": {
      "success": true
    }
  },

Think this should be a major version bump since we're changing the public API? I'm curious how many folks are using this definition vs. the maybe support outside of Block.

I personally wouldn't consider that public api, IMO it shouldn't have been merged to begin with since again users in Bazel can simply define the version they want to use. Ideally, we wouldn't have this at flag all.
If we wanted to test in CI with 6.x and rules_apple 2 we can configure that in CI

+1 to treating this as an improved contract but not necessarily a major version bump (no strong opinions though if folks want to do so). To hard code it to "Bazel 6.1.x" was a bit hack-y and would bite folks on that version without them knowing. With this new flag at least it's now an opt-in for "I'm using whatever Bazel version <=6.x.x and I want to use rules_apple 2.x".

I don't feel strongly. Please just call it out in the release notes. 🙏


Passing input without optional properties to fn throws error

/* @flow */

type O = {
  str: string,
  str2?: string,
  str3?: string,
};

type A = {
  str: string,
};

const a: A = { str: '' };

function fn(o: O) {
 if (typeof o.str2 === 'string') {
   console.log('ay');
 }
}

fn(a);

https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVAXAngBwKZgDyYAvGAN6phgDOGATgFy0MCWAdgOYA0VY7AVwC2zQUIBGeerwC+AbnTZ8YAApwaNVuJh4V9ODhqkKfHPpwBGZnXocep8wCZrbLrIWZcBQhgAWUvQMjMkpqMwMAZhdbNwcDABZou3dFLzAAFWNiADIwAAo1DS0dQMMwAB8iPwDzGgBKDygBdgBjDFY4djAodjy4ZnS6k2pWKHy4ADpwyyHQ6jB6PAwBei7J6ccFahlUGSA
Shouldn't this typecheck correctly ?
The logic is this code can't crash ; A fits B actually, as str2 and str3 are optional properties.
Yet flow throws theses errors:
15: function fn(o: O) {
                   ^ property `str2`. Property not found in
21: fn(a);
       ^ object type
15: function fn(o: O) {
                   ^ property `str3`. Property not found in
21: fn(a);
       ^ object type

Is this logical for Flow to throw an error and why ?
If not, how can I make this typecheck correctly ?

This typechecks correctly, you make the assumption that A is a subtype of O (which seems logical), however, nothing in your types says that A doesn't have an str2 prop. It could actually even be a number. What you're looking for here are exact objects, see your corrected example.
I'm sorry for not explaining well this case, I hope that the docs will do a better job than me!

This exemple may explain why it's logical that flow throw an error  :
/* @flow */

type A = {
  str: string,
  str2?: string,
  str3?: string,
};

type B = {
  str: string,
}

type C = {
  str: string,
  str2?: number,
  str3?: number,
}

const a : A = { str: '' }; // Works

const b : B  = { str: '' }; // Works

const c : C  = { str: '' }; // Works

const d : A = b; // Error

const e : A = c; // Error

@AugustinLF

What you're looking for here are exact objects

Your explanation makes totally sense to me, and therefore, it sounds logical that exact objects would be the safest thing to do here. However, for some reasons, I couldn't get it to work through the following example:
'use strict';

// @flow

/*::
type User = {
  name: string,
  age?: number,
  city?: string
};
*/

function greetUser(user/*: User */) {
  let greeting = `Hi ${user.name}!`;
  if (user.age) {
    greeting += ` You are ${user.age} years old.`;
  }
  if (user.city) {
    greeting += ` You live in ${user.city} city.`;
  }
  return greeting;
}

const user /*: {| name: string |} */ = { name: 'my name' };
greetUser(user);

Here, Flow complains about:
» flow
Error: index.js:27
 27: greetUser(user);
     ^^^^^^^^^^^^^^^ function call
 14: function greetUser(user/*: User */) {
                                ^^^^ property `age`. Property not found in
 27: greetUser(user);
               ^^^^ object type

Error: index.js:27
 27: greetUser(user);
     ^^^^^^^^^^^^^^^ function call
 14: function greetUser(user/*: User */) {
                                ^^^^ property `city`. Property not found in
 27: greetUser(user);
               ^^^^ object type

Found 2 errors

However, changing
const user /*: {| name: string |} */ = { name: 'my name' };
greetUser(user);

to
const user /*: { name: string } */ = { name: 'my name' };
greetUser({ name: user.name });

seems to please Flow.
Isn't the exact object annotation supposed to make the two above equivalent?

Hmmm, no, the exact object annotation makes it sure that there are no other properties, and in our initial case, that you won't find the same property with a different type (which is the reason why there was this subtype problem).
In your last comment, the {| name: string |} means that there can't be any age or city property, so {| name: string |} and { name: string, age?: number} are not compatible.
I'm not totally sure of what you want to do, in your last example, removing the typings of the const user works.

In your last comment, the {| name: string |} means that there can't be any age or city property, so {| name: string |} and { name: string, age?: number} are not compatible.

Could you explain what makes them incompatible? The former should be a subtype of the latter shouldn't it? If that's not the case, then why does greetUser({ name: 'a string' }) work? { name: 'a string' } could be typed as {| name: string |} right?

I'm not totally sure of what you want to do, in your last example, removing the typings of the const user works.

Yep, I wouldn't add a type touser in this case, I'm just making an example reproducing what I believe is happening in a more complex situation.
For example, one issue I'm currently facing is:

I have an imported function fn(args: A)
understand the type A as { p1?: string, p2?: string, p3?: string, p4?: string }.
in my code, I have to type the output of a library that doesn't have any type annotation
that library returns an object b of type B defined as { p1: string, p2: string }
when calling fn(b), Flow complains about the non-existence of p3 and p4 in b.
changing the type B to {| p1: string, p2: string |} doesn't change anything
however, calling fn() as fn({ p1: b.p1, p2: b.p2 }) makes Flow is happy.

I thought the example I originally wrote would make things a little easier to understand. Sorry if it was misleading.
Am I missing and/or misunderstanding something?

I got to play a little more with this and noticed two things. Let me use my original example and slightly modify it:
'use strict';

// @flow

/*::
type ShortUser = {
  name: string,
};
type User = {
  name: string,
  age?: number,
  city?: string
};
*/

function greetUser(user/*: User */) {
  let greeting = `Hi ${user.name}!`;
  if (user.age) {
    greeting += ` You are ${user.age} years old.`;
  }
  if (user.city) {
    greeting += ` You live in ${user.city} city.`;
  }
  return greeting;
}

const user /*: * */ = { name: 'my name' };
greetUser(user);

// Error on the line below. The type of `age` is incorrect
const wrongSubUser/*: User */ = { name: 'John', age: true };

// No problem with the 2 lines below
const subUser/*: User */ = { name: 'John' };
const subUserAlias/*: ShortUser */ = subUser;

// This works
greetUser(subUser);

// This generates an error: the properties `age` and `city` are said to be missing
greetUser(subUserAlias);

The first thing I noticed is that, by using the existential type * for user, Flow types it same as User. It seems that it uses the type of the first argument of greetUser().
The second thing I noticed is that despite Flow seems to consider ShortUser as a subtype of User, it wouldn't allow calls to greetUser() with an argument of type ShortUser.
Could it be that Flow is ok with subtype relations but doesn't do this resolution on function calls and require types to be strictly equals?

The second thing I noticed is that despite Flow seems to consider ShortUser as a subtype of User, it wouldn't allow calls to greetUser() with an argument of type ShortUser.

It's the other way around, ShortUser is a supertype of User

@vkurchatkin

It's the other way around, ShortUser is a supertype of User

You're totally right! I realized afterwards that something went wrong while I was copy-pasting back and forth between my editor and here. My apologizes.
Below is the (simplified) code I originally intended to post:
'use strict';

// @flow

/*::
type ShortUser = {|
  name: string,
|};
type User = {
  name: string,
  age?: number,
  city?: string
};
*/

function greetUser(user/*: User */) {
  let greeting = `Hi ${user.name}!`;
  if (user.age) {
    greeting += ` You are ${user.age} years old.`;
  }
  if (user.city) {
    greeting += ` You live in ${user.city} city.`;
  }
  return greeting;
}

const user = { name: 'user' };
greetUser(user);

const shortUser/*: ShortUser */ = { name: 'short user' };
greetUser(shortUser);

First of all, just to make sure I'm not missing anything:

ShortUser is limited to objects with one single key, being name and its value being a string
User is any object containing:

a name key whose value is a string
possibly an age key whose value would be a number
possibly a city key whose value would be a string
any other key whose value could be anything

ShortUser's set of possible values being a subset of User's possible values, ShortUser is a subtype of User here right?
If the above is correct, then why doesn't Flow let me call greetUser() with shortUser ?
Sorry if I'm missing something obvious.

It is possible to come to wrong conclusions If you think about subtypes just as subsets of possible values. You also have to consider a set of possible operations. For example, if operation O is allowed on type A and not allowed on type B , then B can not be a subtype of A.
For example, type A = { foo: string, bar?: string } allows deleting property bar, where type B = { foo: string } does not. Hence B is not a subtype of A. In this case it's not even a subset of values, because A contains only those values B that either don't have property bar or it is a string.

Right, thanks for the explanations! :)


Add readme and changelog to sdist

I'm maintaining this package on conda-forge, and we build pytermgui from the sdist deployed on PyPI. Because hatch-pancy-pypi-redme is building the fancy readme from README.md and CHANGELOG.md during the build, we need those two files in the PyPI sdist as well.

All seems good to me, thank you!


🐛 [EPic Games Free] Add-on won't start after latest update

Description
Current version: debian-2024-04-26
After update Addon wont start logs only show the below
exec /sbin/tini: exec format error
Reproduction steps
1. Go to Addon
2. Click on Start
3. Swap to Log
4. "exec /sbin/tini: exec format error"

Addon Logs
exec /sbin/tini: exec format error

Architecture
No response
OS
HAos

Thanks! It means the upstream container messed up their architecture :) i'll revert


[Feat]: Want to add new tool

What feature?
I have an idea to add a new tool which is RAPID API which provides various categories of APIs for developers.
Add screenshots

Code of Conduct

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

@JasonDsouza212 kindly assign me this issue.


Fix: Correctly parse the right version of SPDX JSON in Identify

Thanks for adding this test case and starting on this work @jamietanna - I think this work might actually be addressed by #2186 so I'm linking this here for convenience

https://github.com/anchore/syft/pull/2186 refactored this path and also added tests to ensure all supported versions are decoded and identified correctly.


BUG: Refreshing the palomabot website 3x disconnects teh EVM wallet

Steps to reproduce:

connect EVM wallet to Palomabot
refresh 2-3 times

Expected: EVM wallet should still be connected
Actual: EVM wallet is no longer connected and user has to connect again

Could you please check this problem on your side? This problem did not happen on my side. @verabehr

yes, I could reproduce see my loom here https://www.loom.com/share/c647ebb2d0d74e90af6b45a0576d9673

happens on other pages as well, not just this one

Sorry, could you please check again after cleaning the cache? @verabehr

Just this? or more?

Please select Browsing history. and also please clear local storage too

I cleared all three (it didn't show in the loom unfortunately), but now the connected wallet doesn't even show in the beginning. I also still see the issue
https://www.loom.com/share/44d7691d7eaa4dcf8f62cda7140e5ac1


Added demo link

Added clean link to demo, so it's present in the main README body.
Referencing #4

Thanks for the PR @xelarate86 , I'm gonna merge it.


Notebook fails to run

Hi there, I tried to run the  google colab notebook (used to work in the past) but now it fails to load the scREAD data and gives  the following error:
Warning message in load(url("https://github.com/OSU-BMBL/scread-protocol/raw/master/overlapping_genes/scread_db.rdata")):
“input string '10<96>12 months' cannot be translated to UTF-8, is it valid in 'CP936'?”
Error in value[3L]: attempt to apply non-function
Can you please advice on how to proceed?

The main server is in maintenance so the link does not for now. I have updated the database URL, now it will only load from GitHub.
Note that the finding overlapping DEG function is also available on scREAD website now: http://osubmi.com/scread/


Jonmv/vespa feed client

@bjorncs please review and merge.

Ready.

Bleh, need to parse traces properly too.


time_slice of analogsignalarray also accepts None as t_start and t_stop values

Analogsignalarray.time_slice() does not require two quantities as input (t_start and t_stop), but also accepts None for any of them. If None is provided as t_start (t_stop) no shortening of the signal is performed at the beginning (end) of the signal.

Coverage decreased (-0.09%) to 62.85% when pulling c7d46449656fe033a499f7398b513199e9074cf6 on INM-6:time_slice into 71c0d6a2c6abff682cfc6226a4ad9e09b6445f4b on NeuralEnsemble:master.

Coverage decreased (-0.09%) to 62.85% when pulling c7d46449656fe033a499f7398b513199e9074cf6 on INM-6:time_slice into 71c0d6a2c6abff682cfc6226a4ad9e09b6445f4b on NeuralEnsemble:master.

Many thanks for this. Please could you add a unit test?

Coverage increased (+0.06%) to 63.0% when pulling f305d753ba72427337f86ae2d0aa6f2d9d6de00a on INM-6:time_slice into 71c0d6a2c6abff682cfc6226a4ad9e09b6445f4b on NeuralEnsemble:master.

Coverage increased (+0.06%) to 63.0% when pulling f305d753ba72427337f86ae2d0aa6f2d9d6de00a on INM-6:time_slice into 71c0d6a2c6abff682cfc6226a4ad9e09b6445f4b on NeuralEnsemble:master.

I added a unit test to cover 'None' as input parameter.


Send cursor position along with document URI when a command is invoked from a (context) menu

In the documentation about Contribution Points, specifically the section on contributes.menus, there's a note that says the following:

Note: When a command is invoked from a (context) menu, VS Code tries to infer the currently selected resource and passes that as a parameter when invoking the command. For instance, a menu item inside the Explorer is passed the URI of the selected resource and a menu item inside an editor is passed the URI of the document.

I was wondering if it would be possible to also send the cursor position (line and column) where the context menu was invoked when inside an editor. The document URI is very useful, but I have some commands that also depend on knowing where in the document the command is invoked from.
(Please excuse my ignorance if this is already possible. I did some querying, and I didn't find any examples.)
Thanks for your time!

Actually, after further investigation, it looks like this is already possible using registerTextEditorCommand instead of registerCommand. With registerTextEditorCommand we also have access to the editor from which the command was invoked, and I can pull the document URI and cursor position where the menu was invoked directly from that editor. So, I'm closing this issue. Sorry to waste your time. 👍


新增一个产业案例

本项目通过使用PaddleDetection2.0中的YOLOv3(主干网络为mobilenetv3的轻量化模型)，通过几行代码就能实现跌倒的目标检测，后期可部署用于监控医院、疗养院甚至家里等,mAP值达到80.28%。

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

thank you


Use longer exec probe timeouts for Head pods

Why are these changes needed?
This is a follow-up to https://github.com/ray-project/kuberay/issues/2264 and https://github.com/ray-project/kuberay/pull/2265
For the Head pod, the exec probe timeout should be higher than 2 as exec probes run 2 "wget" commands:
wget -T 2 -q -O- http://localhost:52365/api/local_raylet_healthz | grep success
 && wget -T 2 -q -O- http://localhost:8265/api/gcs_healthz | grep success

This PR updates the probe timeout for Head pods to 5 seconds. See https://github.com/ray-project/kuberay/pull/2265#discussion_r1742846215 for more details.
Related issue number
https://github.com/ray-project/kuberay/issues/2264
Checks

[X] I've made sure the tests are passing.
Testing Strategy

[X] Unit tests
[ ] Manual tests
[ ] This PR is not tested :(

I did more testing and I'm not sure that increasing the probe timeout is actually helping. Let's hold off on this PR for now, I will do more testing and report back

I opened a separate PR to use HTTP probes which resolves some of the issues I'm encountering with exec probes: https://github.com/ray-project/kuberay/pull/2360
However, HTTP probes have a limitation of checking only a single endpoint


Use lx-valid validation hooks for jwks and jwks_uri

NOTE: Depends on https://github.com/anvilresearch/modinha/pull/14
Per discussion in #212

Added new releases of modinha and modinha-redis


fix typo in changelog link

Fix dead link for changelog in README. A similar typo was fixed early but this one remained.

Ouch. Thanks!


Switzerland, Liechtenstein and Austria added.

We have implemented some new countries: Switzerland, Liechtenstein and Austria.

Thank you for your pull request. The service now provides AT, LI and CH data!


Tests/add in some tests

The one with tests
Originally started as making a start with tests, ended up adding tests for all public methods.
Istanbul is reporting 85% test coverage, which is better than the zero before.

Nice LGTM 👍


Add RenovateBot RegexManager to automate defid versions update in @defichain/testcontainer

What would you like to be added:
As per the title, RenovateBot supports custom Regex Matcher. https://docs.renovatebot.com/configuration-options/#regexmanagers
Why is this needed:
Shift left and update docker image earlier. Prevent regression and incompatibility issues earlier in the development workflow.

/triage accepted
/area workflow

/assign @shohamc1 can you help with this? It's directly related to https://github.com/JellyfishSDK/jellyfish/pull/1841
By automating this, when we merge and release on DeFiCh/ain it will automatically create a PR here.

This does not seem possible on Renovate. The versioning requires some form of semver to tell if a newer version is available, which does not work with our current master-* and HEAD-* tagging scheme.

There is still some merit towards just tracking the semver updates.
However, I will remove the issue assignment for now for you to work on other things.

There is still some merit towards just tracking the semver updates.
However, I will remove the issue assignment for now for you to work on other things.

E.g. https://github.com/JellyfishSDK/jellyfish/pull/1879

/triage accepted
We should tackle this somehow, having to manually update along side renovatebot is pretty annoying.


some improvements

iaw @Sergic mail, the following improvements will be included:
clearParam
clearParams
getParam
new config parameter: default-return who will return by default an exception.if the value name does not exist

i think about other...
compromise:

need critical table column for parameter
or
in config some parameter that promote returning default value or exception

default in config is not good.
imagine we have such parameters:
site_name
items_per_page
default_culture
in config we set
default-return: sometext
and that we get in the outcome if three are not >2 params? - something not understandable
so
if ($param->getCritical()){
//to do some exception
}
else{
//return $default ('some text value' or null)
}
but i need return this null value and set default param in method ))

sorry can't explained you.
i want to set default value in getter method. if there is no value - return null.
see founded class http://trac.symfony-project.org/browser/branches/1.4/lib/config/sfConfig.class.php  on symfony 1.4

Latest commits add getParam method for the bundle with an argument for the return if no value
$kdb = $this->container->get('kparams');
$kdb->findParam('site_name', 'oops');

@Sergic pls take a look at /cc #2 to see if it fit your needs

ok looks seems not bad
why not use memory for parameter (save all parameters once in protected array property)
return $this->parameterManager->findParamByName($name);
this string will do mysql query every call of this function

Can not mind up what you want, maybe if you do a PR I can take a closer look to it.

to use pattern Registry design pattern for save in memory parameters and then use getParam function to get value from array
don't you think so?
load all parameters at once
private $params = null; // will convert to array()
private function getAllParams()
{
    if (!$this->params)
    {
        $allParameters = $this->parameterManager->findParams();
        $params = array();
        foreach ($allParameters as $k=>$v)
        {
            if ($v->getActive() == 1)
            {
                $params[$v->getName()] = $v->getValue();
            }
        }
        $this->params = $params;
    }
    return $this->params;
}


Fix running with ALL when using gitlab.com

and improve behavior in other cases when running as
a non-admin. In that case there is no point in trying
to get all groups or projects as you need at least
Reporter role to change their configuration.
Fixes: https://github.com/gitlabform/gitlabform/issues/509

I would appreciate it if someone could take a look at this, conceptually. Do you think it is okay to limit getting groups and projects like this, @amimas @jimisola?


Difficulty in rewinding the video when the it is in scroll component

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When you are trying to rewinding the video when the it is in scroll component - you will be as well scroll RN scrollable compoents like ScrollView, FlatList or SectionList
Expected Behavior
Rewind the video shouldn't trigger scroll events. Working as expected on iOS
Steps To Reproduce

Init RN application
Add bitmovin library
Replace App.tsx with code snippets
Replace SOME_URL and YOUR_LICENSE_KEY with valid data
Run application

What platform(s) are you experiencing the issue on?

[X] Android
[ ] Android TV / Fire TV
[ ] iOS
[ ] tvOS

Player React Native SDK version
0.9.2
Device
No response
Environment
No response
Stream URL (Optional)
No response
Additional information / Code snippets / Screenshots
import React, {useEffect} from 'react';
import {useWindowDimensions, View, ScrollView} from 'react-native';
import {usePlayer, PlayerView, SourceType} from 'bitmovin-player-react-native';

const VideoPlayer = (): React.ReactElement => {
  const {width} = useWindowDimensions();

  const player = usePlayer({
    licenseKey: 'YOUR_LICENSE_KEY',
  });

  useEffect(() => {
    player.load({
      url: 'SOME_URL',
      type: SourceType.HLS,
    });
  }, [player]);

  return (
    <ScrollView horizontal>
      <PlayerView style={{width, height: (width * 9) / 16}} player={player} />
      <View style={{width: 300, height: 300, backgroundColor: 'red'}} />
    </ScrollView>
  );
};

export default VideoPlayer;

@NazarKuryl0 -  Closing this issue since this was discussed and a solution was found to work around this on the integration side.


Routes are 404 on vercel deployment

Describe the bug
Hi last night I encountered I think a bug. There is no problem on local development(npm run dev) or even production(npm run build && npm start) on my machine everthing works fine. But when I deploy my application on vercel. All the routes are 404.
Example url https://v2.bestizmirege.org/
Occurs in next-i18next version
^8.8.0
next version:11.1.2
Steps to reproduce
Here is the repository https://github.com/ekinndev/best-izmir-v2
Additional context
I saw 500 error code on network tab

I checked vercel logs

Somehow it can't find locales folder maybe?
The build output folder structure

You'll need to provide more information/logs. At the moment I have no idea how to help you.

I added vercel logs and showing build folder structure maybe it can help to figure it out what's going on.

This issue with the Vercel fs has been discussed numerous times on this repo. You need to add localePath: path.resolve('./my/custom/path') to your config.


Set a received record to "read" if we've already had close_notify

If the peer already sent close_notify the comment in the code says that
we throw anything away that is sent to us. In reality though we weren't
setting the record as "read" and so it was never thrown away. This would
mean any further records will never be removed from the underlying BIO.
I don't think this makes any practical difference (we shouldn't be trying
to read stuff after having a close_notify anyway). But we should do it
for consistency and cleanliness of the code.
Impacts master and 1.1.0

We should never process packets after the close notify. We should
not attempt to read from the socket after we've seen it. Do we
have a test covering the "stoptls" case?

Do we have a test covering the "stoptls" case?

Not as far as I know.

This reads as potentionally breaking it

I'm not going to pursue this at the moment.


window.onerror is missing column, error arguments

As of HEAD:
  @JsFunction
  public interface OnerrorCallbackFn {
    Object onInvoke(String p0, String p1, double p2);
  }

From whatwg spec
[TreatNonObjectAsNull]
callback OnErrorEventHandlerNonNull = any ((Event or DOMString) event, optional DOMString source, optional unsigned long lineno, optional unsigned long colno, optional any error);

From MDN:

window.onerror
window.onerror = function(messageOrEvent, source, lineno, colno, error) { ... }

Function parameters:

message: error message (string or event object). Available as event (sic!) in HTML onerror="" handler and also as an event object when dispatching an Event to window in which case the other arguments will not be supplied (as opposed to ErrorEvent which does cause the full range of arguments to be supplied to window.onerror whereas the single error event object is supplied to window.addEventListener('error') handlers) .
source: URL of the script where the error was raised (string)
lineno: Line number where error was raised (number)
colno: Column number for the line where the error occurred (number)
error: Error Object (object)

Of note, this document also indicates that the last two arguments were missing from firefox until version 31 (though, this is almost old enough to still support the legacy dev mode plugin...).
Notes at https://github.com/google/closure-compiler/blob/master/externs/browser/w3c_dom1.js#L873 appear incorrect - msdn link redirects to a different MDN on the error event with no other detail about this, and the MDN link is the one I quoted above.
I wasn't sure if you wanted this filed upstream, or instead made into a diff as with most of the other bugs in closure externs, so I filed it here for triage.

Thanks I'm fixing that upstream internally.

fixed with https://github.com/google/closure-compiler/commit/7bee1ca1beaa4f9695a02d0130e915f0e65ac3c6


Fixed $$ to $

replace function by escaping dollar dollar with additional one that two dollars remain at export

close #4


Update renovatebot/github-action action to 34.40.0

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
minor
v34.39.3 -> v34.40.0

Release Notes

renovatebot/github-action
v34.40.0
Compare Source
See the the changelog for changes in all releases.
34.40.0 (2022-11-27)
Bug Fixes

deps: update renovate/renovate docker tag to v34.40.0 (59a935a)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

@balena-ci I self-certify!


Fix build on RHEL 7

Add detection for rhel.7-x64 runtime id to cibuild.sh
Add rhel.7-x64 runtime ids to project.json's with runtime sections

Tested on RHEL 7.3 with a ./cibuild.sh.

Yes. I tested it (only) on RHEL 7.3.

@dotnet-bot test Ubuntu16.04 Build for CoreCLR please
(it looks like something convinced the init script that it was running on 16.10? But the machine was named ubuntu1604-20170216-40d4a0 which I assume implies 16.04 . . .)

16.10 support need to be added along with 17.04 as well. Ubuntu 17.04 will be out in April.

@dotnet-bot test Ubuntu16.04 Build for CoreCLR please

Is the issue being experience by the builder a general issue or is it a bug in the fix?

@omajid I don't think it's related to your change; I plan to spend some time today chasing it down. No action needed from you at the moment . . .

@dotnet-bot test Ubuntu16.04 Build for CoreCLR please

Looks good. @Microsoft/msbuild-maintainers can I get a second opinion?

Thanks! Sorry for the confusion on had build issues not related to this change.

Thanks for accepting this!


NoGummi not working

NoGummi is not working with Luabackend hook 1.3.0

Yes it does. Just tested again to make sure.


unrecognized directive: on

Caddyfile is almost exact the same as the example here, except the change of root path, however when i tried to execute caddy.exe run, the following error occurred:
using adjacent Caddyfile
run: adapting config using caddyfile: Caddyfile:3: unrecognized directive: on
output of caddy.exe version:
v2.0.0-beta.14 h1:QX1hRMfTA5sel53o5SuON1ys50at6yuSAnPr56sLeK8=

here is the Caddyfile:
:8888 {
root D:\WWW
on startup php_cgi2.bat &
fastcgi / <IP_ADDRESS>:6545 php
}

On hasnt been implemetned in V2.
You can use V1 and it will work perfectly.
https://caddyserver.com/v1/download

On hasnt been implemetned in V2.
You can use V1 and it will work perfectly.
https://caddyserver.com/v1/download

Ok, thank you so much!


WIP: allow path conflicts in conda builds

Nightly conda builds for 24.12 and 25.02 are currently failing because of file-clobbering issues with xorg-* packages. It looks like this is because those packages on conda-forge are in the middle of a migration.
That clobbering should generally be safe, and anyway is out of our control, so this PR proposes temporarily allowing it in CI.
See #800 for details.

/ok to test


Download error

Hello
My OS - Win 7.1 - 32 bit
youtube-dl version - 2018.05.01
python ver 3.6
I am trying to download some videos from paid Udemy course core-java-programming-the
-complete-course
But when i enter the course name i was not asked to enter the password and automatically video download process gets started with the immediate following error.
C:\Users\satish>youtube-dl -u<EMAIL_ADDRESS>https://www.udemy.com/core-java-programming-the
-complete-course/learn/v4/overview
Type account password and press [Return]:

Here the process starts automatically with following error.

[udemy:course] Downloading login popup
[udemy:course] Logging in
ERROR: Unable to log in; please report this issue on https://yt-dl.org/bug . Make sure you are using
the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl wit
h the --verbose flag and include its complete output.
Please let me know the system fault and the steps to be followed to get rid of this error.
satish

Try with this method?
https://github.com/rg3/youtube-dl#authentication-with-netrc-file

I'd recommend including the site's name [Udemy] in the issue name. Makes it easier for other users to find your issue if they're also experiencing it.

@sa7mon  Thanks. I have already written the site name in the post.
@KharmaScribbles Thanks. Today i upgraded to the latest version 2018.05.09 on one PC and its working. Lets see it will work on another PC also.


guest OCI hooks are not working with Kata

Description of problem
OCI hooks are not working with Kata. Created a rootfs with hook scripts and enabled guest_hook_path = "/usr/share/oci/hooks" in the configuration.toml.
Running the container results in the following error:
Error response from daemon: OCI runtime create failed: rpc error: code = Unknown desc = open /run/kata-containers/shared/containers/7217217f69ef8af65581790aa06fe3b54499dd3b8f1a79e6116
94ec670a6182a/config.json: read-only file system: unknown.
time="2020-06-10T11:49:58Z" level=error msg="error waiting for container: context canceled"
The problem got introduced since the following commit a3dec26
Expected result
Container should start and hooks should run
Actual result
Container fails to start.
Reference Issue - https://github.com/kata-containers/runtime/issues/2763

Closing as PR is already merged.


CLOUDP-178644: Upgrade the develop branch in envoy-serverless to v1.26 (DO NOT MERGE THIS PR)

NOTE: See the comment below for a more up-to-date outline of the upgrade process.
Manual Steps Taken

git fetch upstream --tags
git checkout upstream/release/v1.26 && git checkout -b CLOUDP-178644-rebase
Cherry picked the given commits onto the v1.26 release branch

NOTE: We will not merge in this commit but instead force push the following changes to the develop branch
Proposed Future Upgrade Process For Repo Admins

Run git describe --tags --dirty --always --match 'v[0-9]*' --abbrev=7 | cut -c 2- and then checkout a branch with the name v<VERSION_NUMBER> (i.e. v1.21.3-15-g24dc879)
Add the same branch protection rules to this branch as on the main branch
Run git fetch upstream --tags
Run git checkout <NEW_RELEASE_BRANCH_OR_TAG> && git checkout -b <JIRA_TICKET_NUMBER>
Cherry-pick all necessary commits from the develop branch onto the new branch
Open a PR outlining the commits to be cherry-picked (like this PR)
Force push to the develop branch

^ this process, while not ideal, forces us to keep fairly close to the mainline envoy codebase (i.e. discourages large refactors). I think this is acceptable given the fact that this fork of envoy is simply meant to be a base for serverless-proxy.

Evergreen Patch: https://spruce.mongodb.com/version/6488c8a87742aedbb7f6e5f6/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC

Recommend this be closed in lieu of #69

Change of plan; we are going to use this PR after all.  Siyuan brought up good points on the flaws with the plan in PR #69.

Upgrade Process for the develop branch in envoy-serverless

git remote add upstream https://github.com/envoyproxy/envoy.git
git fetch upstream --tags
git checkout develop
git rebase -i upstream/release/v1.26 and remove unneeded commits. This includes commits that we made and those backported to v1.21 by the Envoy maintainers.

Before removing commits:
pick 09fb37bcb8 Kickoff release v1.21.1 (#19998)
pick 5bf9b0f1e7 [1.21] CVE-2022-21655
pick d0079e6512 [1.21] CVE-2022-21654
pick 1aa9da394f [1.21] CVE-2021-43824
pick 8b05f8f6a4 [1.21] CVE-2022-23606
pick 2728610b1b [1.21] CVE-2021-43825
pick af50070ee6 [1.21] CVE-2021-43826
pick 99ce7dbef2 Clean up version number and history following the v1.21.1 release (#20083)
pick 2f552e8e9e Fix CI for release/v1.21 (#20166)
pick 52668550a9 backport #19971 SDS: reduce cost of secret update (#20189)
pick 7c56be5892 ci: Fix tests (#20828)
pick a18d7a057a docs: Fix mappings for version history links (#20965)
pick 18fbb28438 cryptomb: remove PKCS1_5 padding support. (#20507)
pick dc7f46eb44 repo: Prepare release (`v1.21.2`) (#20825)
pick 7739bc9214 [Backport 1.21] perf: add config to enable looking up local interface name for upstream connections (#19758) (#20860)
pick 98488f9a05 repo: Dev 1.21.3 (#21226)
pick 41c269252e decompressors: stop decompressing upon excessive compression ratio (#733)
pick 8c8c75fe7a Prepare Release.
pick fe29083d4b Apply patch all-remove-tcpstats.patch to remove TCP stats for CentOS 7.
pick 34f16ba486 Update certificates for tests since the existing ones expired in 2022 Aug.
pick 17ae19f482 Add evergreen scripts to compile with docker.
pick dbdcfa34cf CLOUDP-132396 Add evergreen task to build and test Envoy serverless binary (#3)
pick db38f6a8a2 CLOUDP-132397 Add evergreen task to upload the release tarball to an s3 bucket (#4)
pick 6ea671b2dc CLOUDP-152133 Remove prefix 'archive' in the tarball hierarchy and make the tarball public (#5)
pick e7b027006f update hyphen matching in regex in version_out_test.sh (#11)
pick 407a9b1a68 CLOUDP-152702: Update Envoy Serverless --version to reflect the change after the base Envoy version (#7)
pick 7551e8b568 fix the regex in the version test case to only return the second group (#12)
pick 008b3cfc37 CLOUDP-155417: Setup PR checks on GitHub (#15)
pick c5dd9b5093 CLOUDP-152702: Update test to check for substring in expected commit (#16)
pick 832cb0a0bb CLOUDP-152703 Compile envoy serverless on Graviton (#8)
pick 921448e05d CLOUDP-153323 Merge CLOUDP-103046 into envoy-serverless/develop: Pass Proxy Protocol TLVs to upstream. (#9)
pick ddda7691eb CLOUDP-183802: Create a "dummy" version to test upgrade procedure of envoy-serverless
pick 24dc879cee CLOUDP-183038: Use AWS ECR for docker images in envoy-serverless (#51)

After removing commits:
pick 17ae19f482 Add evergreen scripts to compile with docker.
pick dbdcfa34cf CLOUDP-132396 Add evergreen task to build and test Envoy serverless binary (#3)
pick db38f6a8a2 CLOUDP-132397 Add evergreen task to upload the release tarball to an s3 bucket (#4)
pick 6ea671b2dc CLOUDP-152133 Remove prefix 'archive' in the tarball hierarchy and make the tarball public (#5)
pick 008b3cfc37 CLOUDP-155417: Setup PR checks on GitHub (#15)
pick 832cb0a0bb CLOUDP-152703 Compile envoy serverless on Graviton (#8)
pick 24dc879cee CLOUDP-183038: Use AWS ECR for docker images in envoy-serverless (#51)

Resolve any conflicts during the rebase. If you get warnings about merge.renameLimit being too low, run git config merge.renameLimit 999999 to silence them.
git cherry-pick e4d588ac67 d42be6cc0f 0c8d74ec8b 925a7c22cc. These commits include Betsy's commit to disable tcp_stats in v1.26 (same thing we do for serverless-proxy) and Tristan's commits to output the correct version when running ./envoy --version.
Checkout a new branch with the upgrade changes, create a PR, and use release/v1.26 as the base. We won't merge this PR but it allows others to review the upgrade.
Run Evergreen tests and confirm that they pass.
Force push the develop branch with git push origin develop --force.

The tests in https://spruce.mongodb.com/version/6488c8a87742aedbb7f6e5f6/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC are not failing but certain won't build because of the following error:
/usr/bin/env: python3: No such file or directory

I propose we proceed with the force push and handle the above in a follow up ticket (to be filed).

The plan looks good. One question: shall we create a v1.21 branch instead? I imagine we may need to have minor releases on stable branches.

git describe --tags --dirty --always --match 'v[0-9]*' --abbrev=7 | cut -c 2- and then checkout a new branch from develop with the name v<VERSION_NUMBER> (in this case v1.21.3-15-g24dc879).

The plan looks good. One question: shall we create a v1.21 branch instead? I imagine we may need to have minor releases on stable branches.

git describe --tags --dirty --always --match 'v[0-9]*' --abbrev=7 | cut -c 2- and then checkout a new branch from develop with the name v<VERSION_NUMBER> (in this case v1.21.3-15-g24dc879).

That's a good point. Is the suggestion to rename a branch like v1.21.3-15-g24dc879 to just v1.21?

Force push has been performed. Closing this PR and deleting the branch.
In order to perform the force push, I had to modify the branch protection rule for the develop branch temporarily.

Unchecked Do not allow bypassing the above settings.
Checked Allow force pushes and selected myself as the only person who is able to force push.

These modifications have been rolled back.

Yeah, I think branch v1.21 could work.


Fix to gz pattern when looking for files, unzip on win32

Caches correctly from gz files

@Ayzse I appreciate your contribution, however we are removing the ability to cache files in the upcoming release. If you want to see where we are in development of the next version, check the dev branch. In addition, you can join our slack where we discuss new development: https://mlbgame-slack-invite.herokuapp.com/


Create 1.md

Hi @niksiksan
Please see https://www.tensorflow.org/hub/publish for details on how to contribute models to tfhub.dev. Once you have a model Markdown file, please head over to https://github.com/tensorflow/tfhub.dev to open a PR. Thanks!


MGRS lines overlay

Hello
We’re using OpenLayers in our Angular application. Among other things we use Graticule feature to display longitude/latitude lines, and it works really well. But now we need to add an option to display MGRS (Military Grid Reference System) grid lines over the map.
As I see OpenLayers API hasn’t got anything like this. Is there a chance that I missed something? or similar feature is in plans for next releases? Thank you.

@ahocevar thank you for the feedback.
I see your point: the approach would be to extend ol/Graticule.
But also I’m thinking about an implementation using the OpenLayers API: e.g. to add a VectorLayer with polygon features representing MGRS zones, cells. Would it work or could you advice better strategy on this way?

Actually a vector layer would be an even better strategy. I'd use lines rather than polygons though.

Please note that on master the current implementation of Graticule uses a vector layer with a custom loading strategy where the features (lines and text) are regenerated on each bbox change, see:
https://github.com/openlayers/openlayers/pull/8944

Thank you for the answers.
I've started work on MGRS grid using the suggested approach (based on the implementation of ol\Graticule), made some tests. All looks clear now.

Thank you for the answers. I've started work on MGRS grid using the suggested approach (based on the implementation of ol\Graticule), made some tests. All looks clear now.

Hi. sounds interesting. Would you share your work? I was also tasked for an OL MGRS graticule

Hi @sergektp I'm also working on MGRS with OL. Would you share some hints?

Hi
I just followed the described approach: used Graticule layer as reference on how to integrate with the map. Then basically it only needs to make
this.createGraticule_(renderExtent, center, resolution, squaredTolerance);
for MGRS. The function calculates lines which present borders of 500km/100km squares  and coordinate grid lines inside 100km squares. The base idea: split renderExtent into, in general case, a number of extents – for each visible UTM zone. Then project extents into UTM space. Then calculate mesh of 500km/100km squares, coordinate grids in UTM space. Then project the resulting lines from UTM.
I used proj4 to convert Mercator to UTM and back, and made all calculations regarding 500/100km squares just according MGRS definitions.

@sergektp I apologize for the long after the fact ping.
I was wondering, like geotom, if you would be willing to share your work on this. Barring that, I would also appreciate any advice or resources you used when building this. I'm not very familiar with OL/mapping projections and such in general, so trying to figure this out has been a pain.

Hi @sergektp Would you please share your code to make your explanation even easier to understand? :)

We, at 3Liz company, would like to pay for a complete example of Graticule with MGRS grid.
@mike-000 Could you contact me please (email in my Github profile)?

I'm currently working at extending Graticule to display a MGRS grid.
WIP (draft) here: https://github.com/3liz/lizmap-web-client/pull/3236
I hope it will help someone.


How to listen playing state changed ?

Hi,
Currently, I'm playing an rtsp video stream and getting the play status by listening for events:
player.stream.error.listen((error) => debugPrint("error: " + error));
player.stream.buffering.listen((buffering) => debugPrint("buffering: " + buffering.toString()));
player.stream.playing.listen((playing) => debugPrint("playing: " + playing.toString()));
player.stream.log.listen((event) => debugPrint(" mpv: ${event.prefix}: ${event.level}: ${event.text}"));
with available stream, the status sequence is as follows:
playing: false => playing: true => buffering: true => buffering: false
with not available stream (disconnect):
playing: false => playing: true => buffering: true
the error event never fires and buffering still true although connection timeout.
mpv log:
mpv: ffmpeg/demuxer: error: rtsp: method DESCRIBE failed: 404 Stream Not Found
mpv: lavf: error: avformat_open_input() failed
cplayer: error: Failed to recognize file format.
Can I only listen for 1 event where the player's state is updated ?
Here is the set of player's state in VLC
enum PlayingState {
initializing,
initialized,
stopped,
paused,
ended,
buffering,
playing,
recording,
error,
}

The error will correctly fire for this situation in the next update.

Thanks,
in case of source switching from one stream to another, can you discard the last frame of the previous stream (go to black screen) before connecting to the new stream?

In most cases preserving last frame is ideal, I'll see.

Hi, my case is:
I use media kit to display video from some network cameras (rtsp stream). When switching from one camera to another, I want to hide the image of the previous camera to show that I am connecting to another camera.

Another question:
By default the player decodes on GPU, but on my 1 old device, with H265 video stream, the video is not displayed. However if I set enableHardwareAcceleration=false, the video stream can display normally. In cases like this, can the media kit automatically switch back to CPU decoding when the GPU fails?

I simply do not care.

Hi, my case is:
I use media kit to display video from some network cameras (rtsp stream). When switching from one camera to another, I want to hide the image of the previous camera to show that I am connecting to another camera.

Raised #418.


Build numbers not considered in dependency ranges

Describe the bug
When defining a dependency with a version range which includes a build number, e.g. ">= 1.13.3+2", the build number is ignored and version 1.13.3+1 would also be considered as compatible.
To Reproduce
Steps to reproduce the behavior:

use local package repo, where kubernetes-dashboard depends on cert-manager > 1.13.3+1
install cert-manager in version 1.13.3+1
install kubernetes-dashboard: cert-manager will not be updated, although it would be required when installing kubernetes-dashboard

Expected behavior
Up for discussion: When checking a version against a version constraint, the build number should be considered too. Alternatively, we can also disallow using build numbers in the dependency version ranges, which would make things a lot easier.
Glasskube Info (please complete the following information):

Package Operator version: dev
CLI version: dev

Additional context
Similar to #397

@christophenne can this ticket be closed after https://github.com/glasskube/glasskube/pull/426 got merged?

No this is not the same. #426 fixes #397, but afterwards we realized we have the same problem when declaring versions in dependencies. It's up for discussion how we want to deal with it (see expected behavior).

Decision: won't fix but document the constraint


dynamodb errors

Hi all,
I have added a bit of code to make the basics of the new Etcd library work, but had to comment out all the dynamodb configurations due to issues with their library.  I am not in the position to work on dynamodb at this time, and was wondering how to handle this situation.  I could easily move the dynamodb out, but fear that would result in some not noticing that the code was commented out.
Any ideas on how to handle the pull request and get some feedback on the Etcd code?
-> https://github.com/jbkc85/confd/commit/d863548a01bb80850df5440751501c424bdcc2bf
Please be gentle, first time coding in Go and committing back to the community :-)

Looks like we got the new etcd stuff merged and I've fixed the issues around dynamodb so all should be good now. Testing what we have on master would be awesome.

Sure thing, I will see if i can write out some unit testing and just share it in a repository for others to test whenever you build new versions of Confd in case things change.
out of curiosity, did my code help at all?  I wasn't sure as I didn't make a pull request, but would be happy if it helped :-)

Etcd works great.  Tested with TLS encryption on our dev cluster.

@jbkc85 FYI we do have integration tests for dynamodb as well, so hopefully in the future these bugs shouldn't come up. :)


Change hook from emit to done

I cant see any reason why this cant be at the 'done' hook.
'emit' is bad, because other plugins use this and 'after-emit' to do other stuff. zip should be the last step as a zipped file does not usually need any modification by other webpack plugins.
https://webpack.js.org/api/compiler/#event-hooks
Ex. I got trouble using replace-in-file-webpack-plugin because of this, even after I changed replace plugin to 'emit' hook

Or maybe change to 'after-emit' instead


With the new Authorization Server the resources must be protected

UAA is always behind an API gateway that cares about authorization. No need to protect resources additionally in the service. Also the UserInfo endpoint is only accessible via API gateway not directly.

changed description, closing issue


<EMAIL_ADDRESS>install exits with non-zero status, which is too different from 2.1.0

Hi there,
Doing flow-typed install gives us !! No<EMAIL_ADDRESS>libdefs found in flow-typed for the above untyped dependencies !! as before, but in 2.1.0 the exit code was 0 and in 2.1.1 it changed to 1, and scripts start failing. I don't believe it's something that should have ended up in patch version release. Way too backward incompatible :)
Thanks!

Same problem here and actually also flow-typed update does no longer return 0.
Generally not a big deal but now when invoking flow-typed using npm run also fails and all CI scripts as well.

Apologies: I moved the new-install command over to replace the install command and must've missed this inconsistency between the two.
I have a patch release coming up to fix some other issues, so I'll make sure this is fixed in that as well.

@jeffmo seems to be solved in 2.1.1


Add Functionality To Limit Queued Jobs

The limit_queued_job utility checks how many IN_PROGESS and QUEUED jobs a source has, and then automatically fails the job if adding it to the queue brings the source over MAX_JOBS_ALLOWED.

Is it possible for this project to be donated to CS 162 and/or ASUC OCTO (who runs Berkeleytime.com) for continued open source development? @rogerhub @aykamko

Fine with me! @rogerhub thoughts?


Changed event is not triggered on pressing enter for default value.

Hi, I am facing issue, with enter event on text box for default value. For reference my text box is
<input type="text" class="form-control " data-max="20" data-min="0" data-step="0.1"  value="10" data-rule="currency">
and i have bind the "changed" event. It's working fine if changed the value from 10 to 15 and 15 to 16. Now problem is when I changed the text box value from 16  to 10 and pressing enter without loosing the focus changed event is not getting fired.
I have debugged the library and found at line number 96 : this.oldValue is still 10 even i have updated the text box value from 10 to 15 to 16.
Please check and update the library if needed.
Thanks

Hi, I am facing issue, with enter event on text box for default value. For reference my text box is
<input type="text" class="form-control " data-max="20" data-min="0" data-step="0.1" value="10" data-rule="currency">
and i have bind the "changed" event. It's working fine if changed the value from 10 to 15 and 15 to 16. Now problem is when I changed the text box value from 16 to 10 and pressing enter without loosing the focus changed event is not getting fired.
I have debugged the library and found at line number 96 : this.oldValue is still 10 even i have updated the text box value from 10 to 15 to 16.
Please check and update the library if needed.
Thanks

Hi @neelu-singh , you found a solution?


Use mirror-action upstream

[ ] Blocked by https://github.com/yesolutions/mirror-action/pull/29

Wrong repo, closed


EID-1762 Move attribute hash logging logic to saml-lib

This saml-lib PR will need merging and the new building importing before Travis will be happy: https://github.com/alphagov/verify-saml-libs/pull/102
We log eIDAS attribute hashes in the proxy-node as well as the hub.
These hashes are compared for security in Splunk.
We want to ensure the same logic is used so the hashes will be the same.
The proxy-node receives attributes from the VSP. The VSP extracts those
attributes from an assertion and serializes them before sending in a
response.
This commit removes the custom Assertion and Attribute objects the
proxy-node has and replaces them with the same classes as used in the
VSP (via saml-lib). This way they should de-serialize into the same
objects. It also imports the new logger that is defined in saml-lib.

Closing in favour of https://github.com/alphagov/verify-proxy-node/pull/381


make non-matching types in arrays type "any"

This fixes #26

@mholt I was thinking of creating a small CI to at least run the tests and those would only trigger on PRs. If you don't mind, I would continue open PRs, wait for the CI and then merge them myself.

That sounds good to me. Thanks so much for helping with this!


Standardize docs headers syntax

Overview

Converts some third level lines that were bolded into headers
Removes the trailing # from any closed headers, as most of our docs use the unclosed style

/azp run mrtk_docs


Ensure only a single task is created

KAFKA-62

This ensures no matter what the user configures only a single task configuration is created.  Stopping users accidentally misconfiguring and duplicating processing or messages to/from topics.
https://evergreen.mongodb.com/version/5ddd3cde56234319b545bb2b

Ah, I see.  What's the default value for maxTasks?  If it's 1, then would it be better to instead throw an exception when maxTasks > 1 rather than ignore the user's configuration?
I don't have an opinion on it, just throwing it out there as an alternative.

Its not ignoring it as such - its just the maximum number you can produce. This is for connectors that can handle different levels of parallelism.


feat: added EmptySection

Overview

Adds an EmptySection that can be used to provide a placeholder with action button to content area that might have an empty state.
Currently, this is just for the profile page. Updates to make it fit in the Dashboard, Achievements page, and My Workspaces will come later.

To see how it would look on a profile, view a new user's profile as another user.
https://pr-24452.dev-eks.codecademy.com/

~You can see how this would look with the dashboard here:
https://pr-24205.dev-eks.codecademy.com/learn~

~From there, unenroll from any courses/paths if you're enrolled in any, and you should see this gamut component in action (it should look like the one in production, except the illustration might be NumberBlocks because the one in production hasn't been added to Gamut yet).~

PR Checklist

[ ] Related to designs:
[x] Related to JIRA ticket: EGG-984
[x] I have run this code to verify it works
[x] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.67-alpha.eb4d90.0@codecademy/gamut-labs@15.2.7-alpha.eb4d90.0@codecademy/styleguide@36.9.4-alpha.eb4d90.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6090089c13c1c200b77d26b2--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.67-alpha.98d072.0@codecademy/gamut-labs@15.2.7-alpha.98d072.0@codecademy/styleguide@36.9.4-alpha.98d072.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6090426cdca51c0f42b35a28--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.67-alpha.89503b.0@codecademy/gamut-labs@15.2.7-alpha.89503b.0@codecademy/styleguide@36.9.4-alpha.89503b.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60915de2402978208e84a3e6--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.76-alpha.d9d3ba.0@codecademy/gamut-labs@15.4.2-alpha.d9d3ba.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6092cd775e7891298d10a761--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.97-alpha.515a30.0@codecademy/gamut-labs@16.0.2-alpha.515a30.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://609c17e5654f7f106db96f92--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.97-alpha.7541d1.0@codecademy/gamut-labs@16.0.2-alpha.7541d1.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://609c3a5f5a3f7a1f528e0dfa--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.97-alpha.62af9e.0@codecademy/gamut-labs@16.0.2-alpha.62af9e.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://609d385ccd7e5903fd389261--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.97-alpha.8d8bf1.0@codecademy/gamut-labs@16.0.2-alpha.8d8bf1.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://609e87a461eaecea4e111c1c--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.97-alpha.740729.0@codecademy/gamut-labs@16.0.2-alpha.740729.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://609e9025885a4df410372b36--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.102-alpha.3f10d9.0@codecademy/gamut-labs@17.0.1-alpha.3f10d9.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://609e93e1949b2230d99ccc51--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.102-alpha.2b73fe.0@codecademy/gamut-labs@17.0.1-alpha.2b73fe.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://609e96d6b9337b1e5c666e1c--gamut-preview.netlify.appDeploy Logs


library is not able to get stories

Hello,
from yesterday, library is not able to get stories, is there any new update ?
Thank you

I have the same issue.

@raiym is there any new update of library to make get stories function works correctly ?

Hi @zubairsultan786
did you find any solution to fix that ?

Not yet .. still searching and finding solution.. what about you?
On Wed, 19 Jun 2019, 4:26 pm sagitaire123<EMAIL_ADDRESS>wrote:

Hi @zubairsultan786 https://github.com/zubairsultan786
did you find any solution to fix that ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/postaddictme/instagram-php-scraper/issues/503?email_source=notifications&email_token=AIHRSCZNTHCE2ELPTHUPMILP3IXZRA5CNFSM4HXIPSEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYB3OMQ#issuecomment-503559986,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIHRSC7SZCXSMWN2UXW53VLP3IXZRANCNFSM4HXIPSEA
.

@zubairsultan786  I tried many things but its still returning blank in return to getstories function

the problem is in login function

OK thank you @zubairsultan786 , did you manage to solve it?

I tried but failed to solve the problem
On Sat, 22 Jun 2019, 5:31 pm sagitaire123<EMAIL_ADDRESS>wrote:

OK thank you @zubairsultan786 https://github.com/zubairsultan786 , did
you manage to solve it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/postaddictme/instagram-php-scraper/issues/503?email_source=notifications&email_token=AIHRSC4RUXBCYVAFWSKUA5LP3YZTLA5CNFSM4HXIPSEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYKKRSQ#issuecomment-504670410,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIHRSCZYK4RICS4ABTBEQL3P3YZTLANCNFSM4HXIPSEA
.

Try to use another account to check stories, it's seems working now
1 IP per account

So it means everytime whenever i will get this error so i need new account?
On Sun, 23 Jun 2019, 7:15 pm sagitaire123<EMAIL_ADDRESS>wrote:

Try to use another account to check stories, it's seems working now
1 IP per account
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/postaddictme/instagram-php-scraper/issues/503?email_source=notifications&email_token=AIHRSC5O4SP24WR3R76U4UDP36OSNA5CNFSM4HXIPSEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYLB4QQ#issuecomment-504766018,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIHRSC6VEHSGXY3CVLBERMTP36OSNANCNFSM4HXIPSEA
.

Instagram is blocking if you send a lot of request, so yes you need to change account eveerytime when you get this error.
i don't know how many request we need to send to avoid accounts blocks

Are getting stories is not working for you all the time?
or maybe you reach the api requests limits?

@raiym accounts are blocked after too many api request, but we don't know what's the new limit or the way to avoid that.


Deserialization

We need to have a deserializer as well.

I took a crack at this in my personal fork, but I use key value coding so it crashes if your object contains optionals of Swift types, otherwise it seems good. Ex: var a: Int? crashes var a: NSNumber? doesn't.
You can see the commit at https://github.com/mpavlinsky/swift-serializer/commit/c11e6b47d2f2c5b94fb838cc476591296aac73df

Will check it out. Thanks!

@mpavlinsky can you add an example for a simple deserialization that might work?

@mpavlinsky can you add an example for a simple deserialization that might work? :)

I have worked half way through Deserialisation
If any one want to complete it with me let me know i will pate code here.
And i am working on simple technique not too much complicated.
Method Process

Convert Json From Object - Done by This Lib.
Parce Json String and put it in Casting Stack array - Done
Find a way to Create Dynamic Object And Assign Value to that Object Property - Done
Sort Casting Stack Order For Deepest Element to Top  to Complete Deserialisation - Pending

For 4th need help don't have time right now.
Let me know if admin wants this.

@jayb611, where is the code, I'm interested... @mpavlinsky, did you also write a test/sample? I might look into this, too...


Implement breadcrumbs for better navigation

Currently when you navigate from something like the use-cases section...

... to a sub-page you basically loose the context of where you are:

It would be great if we could somehow indicate that a specific subpage is part of the bigger section of the website.

Hi Marco,
I made this PR https://github.com/marcoroth/hotwire.io/pull/45 to add breadcrumbs. They would look this is:

Done via #45/#46