ESM does not work

if I try to use earl from inside an ESM module, mocha fails with the fllowing error:
import { expect } from "earl";
         ^^^^^^
SyntaxError: Named export 'expect' not found. The requested module 'earl' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'earl';
const { expect } = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:190:5)

thinking it is a commonjs because of the missing "type": "module" in package.json.
if I modify the import as suggested, I get a different error:
(node:40437) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.

/Users/*****/node_modules/earl/dist/esm/index.js:1
export * from './Control';
^^^^^^

SyntaxError: Unexpected token 'export'
    at internalCompileFunction (node:internal/vm:73:18)
    at wrapSafe (node:internal/modules/cjs/loader:1176:20)
    at Module._compile (node:internal/modules/cjs/loader:1218:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Object.require.extensions.<computed> [as .js] (/Users/*****/node_modules/ts-node/src/index.ts:1608:43)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Function.Module._load (node:internal/modules/cjs/loader:958:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:169:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:194:25)

That's probably related to the fact that transpilation to esm doesn't add .js into extensions. This will definitely need to be fixed.

Fixed in v1.0.1.
Please reopen if the issue persists, but I hope that I've tested it enough so that it works :P


Shopware has switched to .env.local

Shopware has switched to .env.local for modifications since <IP_ADDRESS>, whereas the .env provides sane defaults now.

[x] Bug fix #…?

[ ] New feature?

[x] BC breaks?

[ ] Tests added?

[ ] Docs added?
Please, regenerate docs by running next command:
$ php bin/docgen

I guess this can break old setups, depending on how deploy:update_code was implemented. Since the basic recipe is not working anyway at the moment, I guess it can be changed though…

Agreed!

Some further discussion here: https://github.com/deployphp/deployer/commit/059fa07941e73bcf2d43ae286bf2d43cc0b9e736#commitcomment-141337160


Consider to adopt new createStatusBarItem API for id and name properties

👋  Hi there, Ben here, from the VS Code team.
We just released VSCode 1.57 that landed a new stable API for status bar items to provide id and name properties: https://code.visualstudio.com/updates/v1_57#_status-bar-item-id-and-name-properties
I noticed that your extension is a consumer of the createStatusBarItem API.
Here is an example how using the new API will improve the user experience around managing status bar items:
Without id / name right clicking on the status bar item from your extension will show a generic label that is just the name of the extension:

As you can see from the example above, the GH Pull Request extension did not yet adopt this new API and as such, the menu only shows a generic entry (as opposed to the other entries that are more specific).
Another motivation to adopt this new API is that it will enable a user to selectively hide/show status bar entries from your extension in case you register more than one status bar item.
An adoption of the new API involves:

configuring "engines": { "vscode": "^1.57.0" } in package.json
where createStatusBarItem is called, add a unique id: string property as first parameter
in the returned StatusBarItem set name to something that describes the intent of the status bar entry (if you provide multiple status bar entries, make sure the name is different for each entry)

Thanks for the support and the great work! ❤

Thanks 🙏

To verify:

Install the GHRPI nightly build and disable the stable build if you have.
Check out a PR branch
Verify that you can see the pull request status bar item and verify that it has a nicer name than listed in the original issue.


Docs: Troubleshooting updates.

Minor fixes to the troubleshooting docs.
Signed-off-by: Jarno Rajahalme<EMAIL_ADDRESS>

This change is

test-docs-please

@jrajahalme 2 misspelled words were found
00:25:22 * Documentation/contributing.rst:805: (ubuntu)
00:25:22 * Documentation/contributing.rst:805: (Vagrantcloud)

test-docs-please

07:04:53 error pulling image configuration: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/3f/3fd9065eaf02feaf94d68376da52541925650b81698c53c6824d92ff63f98353/data?verify=1529567690-iNiUTFdlGrlnSums%2BbZkcUok0Rg%3D: dial tcp: lookup production.cloudflare.docker.com on <IP_ADDRESS>:53: server misbehaving
07:04:53 Makefile:258: recipe for target 'docs-container' failed
07:04:53 make: *** [docs-container] Error 1

test-docs-please

test-docs-please

test-docs-please

@jrajahalme sorry, I forgot to mention afterwards, the issue got fix into master. You would only need to rebase your PR


Setting environment variables in now.json not working as expected

I don't know if there is something I am missing but unless I specifically set the environment variables when I deploy manually, they won't be defined in Node when the app is started.

I think I'm having the same problem, but in the desktop app where I don't think you can even set environment variables. Deployed code just does not work as it has no env variables with secrets.

For now, my workaround is to just run a batch file.
now -e MONGODB_USERNAME=@mongodb_username -e MONGODB_PASSWORD=@mongodb_password

Thank you so much for the effort you have put into this issue! 😊
However, since we completely re-worked the entire codebase of Now CLI and this issue does not apply to the new code anymore, I'm closing it now.
You can read more about our biggest release yet here: https://zeit.co/blog/now-2


add telegram integration

Love telegram integration!

It's great to have Telegram supported! I see this PR before I start coding.
But are you still using go dep and committed the vendor into the repository? I don't think it's good to have vendor included.
Besides, go module is already integrated in kubewatch, maybe you should remove these files before merging, or we should start another pr to avoid these files appear in commit history.

Sorry I didn't notice this is a pr from 2018 🌚, looks like this project is not well maintained...


Handle one way tags from professional data

OSM data represent oneway using from node -> to node + oneway=yes
Professional data doesn't reverse this and using "to node-> from node" + oneway=-1 to represent  oneway.

From the Key:oneway, OSM data also can use oneway=-1 to represent reverse direction is open.

Also some logic to handle the oneway=-1 in Lua code:
https://github.com/Telenav/osrm-backend/blob/7677b8513bf8cdbadb575c745acf4f9124887764/profiles/lib/way_handlers.lua#L569-L572

That's great.
I guess we need specific test cases to verify such situation.
Another case need to be confirmed is conditional oneway, cases like in the morning go into town and afternoon go out of town.


Include artifact transforms in profile report

Show artifact transforms in the --profile report.

This looks not so pretty when used on the Gradle build:

The transform names seem to be way too long.

Branch build

Branch build: https://builds.gradle.org/viewQueued.html?itemId=14777794

Ad-hoc performance test build for the Android test that failed: https://builds.gradle.org/viewQueued.html?itemId=14815936

Branch build with disabled profiler adapter: https://builds.gradle.org/viewQueued.html?itemId=14823294
Ad-hoc performance build: https://builds.gradle.org/viewLog.html?buildId=14823010

Looks like the performance tests are now back to normal if we only register the profile adapter when profiling is actually enabled.
Quick feedback build for some further reduction in memory pressure when the profiler is actually enabled: https://builds.gradle.org/viewQueued.html?itemId=14825912

The branch build succeeded on most of the commits, also the quick check build succeeded on the last commit. I'm going ahead and merging this.


An error was encountered while executing action link

Here is my current install.conf.yaml file:
#!/usr/bin/env bash

- clean: ['~']

set -e

- link:
  ~/.tmux.conf: tmux.conf
  ~/.vim: vim/
  ~/.vimrc: vimrc
  ~/.zsh: zsh/
  ~/.zshrc: zshrc

- shell:
  - [git submodule update --init --recursive, Installing/updating submodules]

Here is my install script:
#!/usr/bin/env bash

CONFIG="install.conf.yaml"
DOTBOT_DIR="dotbot"

DOTBOT_BIN="bin/dotbot"
BASEDIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"

cd "${BASEDIR}"
git submodule update --init --recursive "${DOTBOT_DIR}"

"${BASEDIR}/${DOTBOT_DIR}/${DOTBOT_BIN}" -d "${BASEDIR}" -c "${CONFIG}" "${@}"

Here is my output:
All targets have been cleaned
An error was encountered while executing action link
Action link not handled
Action ~/.zsh not handled
Action ~/.vimrc not handled
Action ~/.vim not handled
Action ~/.zshrc not handled
Action ~/.tmux.conf not handled
Installing/updating submodules [git submodule update --init --recursive]
All commands have been executed

==> Some tasks were not executed successfully

This happens no matter what. I have created and destroyed multiple vimrc, zshrc, etc. files, I have completely removed Dotbot and re-downloaded it, I have tried using JSON formatting. Nothing I seem to try will let me create the links. I'm not sure what the problem is at this point; any suggestions will be appreciated.

I've just run into this problem too, and I would like to suggest a mention to this 4-space indentation requirement somewhere in the README to make it easier for other people to use dotbot. :)

Do you think it would be enough to add something like this as a fourth paragraph in the Configuration section:

When writing nested constructs, keep in mind that YAML is whitespace-sensitive. Following the spacing used in the examples is a good idea.

I'm not sure if that's clear enough. YAML seems to require at least 4 spaces of indentation, maybe this specific information should be mentioned.
Another option is to make dotbot show more meaningful error messages. When I tried with two spaces, dotbot's output was:
Action ~/.gitconfig not handled
An error was encountered while executing action link
==> Some tasks were not executed successfully

This didn't give me any clue about the indentation problem, maybe dotbot could give us more information about what's gone wrong.

YAML doesn't need 4 spaces of indentation, it just needs to be indented more than the link (so that it's under link, rather than having an object with multiple properties, with link being null. 3 spaces suffices.
This isn't exactly Dotbot-specific -- it's about the YAML format itself.
Showing a more meaningful error message for this would be a little tricky. Maybe a custom parser would be better for this, but if someone writes a config file that's valid YAML but doesn't make sense for Dotbot, it's a little tricky to pinpoint exactly why something went wrong.

I see, you're right. Hopefully other people will be more acquainted than I was with the YAML syntax. I agree on that paragraph you suggested before, it'll at least call people's attention to whitespaces and indentation. Thanks for the thorough clarifications.

Okay, great. I've added the paragraph in bdc1b2.

I'm sorry to resurrect this, but what else could cause that error message? I am setting up another machine using files I created a looong time ago for this one and it fails with the same error message. The spaces seem fine, though:
- clean: ['~']

- link:
    ~/.bash_profile: bash_profile
    ~/.bashrc: bashrc
    ~/.ssh/config:
        path: ssh/config
        create: true
    ~/.config/deadbeef:
        path: config/deadbeef/
        create: true

It processes bash_profile and bash_rc then dies with "Action link not handled" Did something change between the dotbot versions that made this syntax invalid?

Hmm, the syntax looks valid. Also, your dotfiles are probably locked to a specific version of Dotbot, right? (like if you're using submodules) What version of Dotbot are you using?

I am not sure, I just pulled the whole git repo from the second PC and ran ./install
The usual dotbot --version doesn't seem to print the version, how do I check?

git submodule status | grep dotbot

dcc3a1947a85aaa038d143f9f6a0c2a1c1a76a15 dotbot (v1.6.0-5-gdc3a19), it seems. Should I update?

Maybe try it with the latest version and see if that works?

Sorry, I have only a vague idea about how submodules work. I managed to update to the latest version now (I think). It parses the script just fine now.
The confusing part is that I did not modify that file since I've set it up, so I expected it to just work with the old version as well. In any case, it's working now, thanks for the hint about the locked version.

Hmm, there's no reason it shouldn't have worked with the old version… glad you got it working, though!
Let me know if you decide to investigate / figure it out. Closing this issue for now.

Encountered the same error message running on a windows 10 machine with python 2.7.13 and git shell (MINGW64).
$ ./install
All targets have been cleaned
An error was encountered while executing action link
Action link not handled

Upon further investigation the root cause of my issue was that git shell didn't have sufficient permissions to create a symlink. Running git shell as admin resolved the issue.

Might be related to #137.

@shawntoffel it worked for me too. Thanks for posting this workaround.

It's baaaaack
I'm indenting with 4 spaces.
- defaults:
    link:
        relink: true
        create: true
        force: true
    shell:
        stdin: true
        stdout: true
        stderr: true
    clean:
        force: true

- clean:
    ~/:
        force: true
    ~/.config:
        recursive: true
    ~/.tmux:
        recursive: true
    ~/.gnupg:
        recursive: true
    ~/Documents/Code:
        force: false

- link:
    # Convenience
    ~/Documents/Code: ~/Code
    # Bash
    ~/.bashrc: bash/xdg-shim
    ~/.config/bash/bashrc: bash/bashrc
    # Fasd
    ~/.fasdrc: fasd/.fasdrc
    ~/.config/fasd/.fasdrc: fasd/.fasdrc
    # Fish
    ~/.config/fish/config.fish: fish/config.fish
    ~/.config/fish/fishfile: fish/fishfile
    ~/.config/fish/functions/:
        glob: true
        path: fish/functions/*
    # Git
    ~/.config/git/config: git/config
    ~/.config/git/config.insteadofhttp: git/config.insteadofhttp
    ~/.config/git/message: git/message
    ~/.config/git/ignore: git/ignore
    ~/.config/git/init-template/hooks/prepare-commit-msg:
        path: /usr/local/bin/mit-prepare-commit-msg
        ignore-missing: true
    ~/.config/git/init-template/hooks/commit-msg:
        path: /usr/local/bin/mit-commit-msg
        ignore-missing: true
    ~/.config/git/init-template/hooks/pre-commit:
        path: /usr/local/bin/mit-pre-commit
        ignore-missing: true
    # git-mit
    ~/.config/git-mit/authors.yml: git-mit/authors.yml
    # Git Duet
    ~/.config/git-duet/authors.yml: git-duet/authors.yml
    ~/.bin/git-duet:
        path: /usr/local/bin/git-duet-wrap-for-sops
        ignore-missing: true
    ~/.bin/git-duet-commit:
        path: /usr/local/bin/git-duet-wrap-for-sops
        ignore-missing: true
    ~/.bin/git-duet-install-hook:
        path: /usr/local/bin/git-duet-wrap-for-sops
        ignore-missing: true
    ~/.bin/git-duet-merge:
        path: /usr/local/bin/git-duet-wrap-for-sops
        ignore-missing: true
    ~/.bin/git-duet-post-commit:
        path: /usr/local/bin/git-duet-wrap-for-sops
        ignore-missing: true
    ~/.bin/git-duet-prepare-commit-msg:
       path: /usr/local/bin/git-duet-wrap-for-sops
       ignore-missing: true
    ~/.bin/git-duet-pre-commit:
        path: /usr/local/bin/git-duet-wrap-for-sops
        ignore-missing: true
    ~/.bin/git-duet-revert:
        path: /usr/local/bin/git-duet-wrap-for-sops
        ignore-missing: true
    ~/.bin/git-solo:
        path: /usr/local/bin/git-duet-wrap-for-sops
        ignore-missing: true

    # GnuPG
    ~/.gnupg/gpg-agent.conf: gnupg/gpg-agent.conf
    # Starship
    ~/.config/starship.toml: starship/starship.toml
    # Tmux
    ~/.config/tmux/tmux.conf: tmux/tmux.conf
    # Vim
    ~/.config/vim/.vimrc: vim/.vimrc
    # ZSH
    ~/.zshenv: zsh/.zshenv
    ~/.config/zsh/.zshrc: zsh/.zshrc
    # Kitty
    ~/.config/kitty/kitty.conf: kitty/kitty.conf
    ~/.config/kitty/dracula.conf: kitty/dracula.conf
    # Sops
    ~/.sops.yaml: sops/sops.yaml
    ~/.bin/1password: 1password/bin/1password
    # Cargo
    ~/.cargo/config: cargo/config

- create:
    - ~/Code/
    - ~/Downloads/
    - ~/Documents/
    - ~/Desktop/
    - ~/Library/Caches/
    - ~/Library/Caches/run/
    - ~/.local/share/
    # Tmux
    - ~/.config/tmux/plugins

- brewfile:
    - brew/Brewfile

- shell:
    - brew update
    - brew upgrade
    - brew cask upgrade
    - brew bundle cleanup --force --file="brew/Brewfile"
    - mas upgrade
    - rustup-init -y
    - rustup update
    - cargo install cargo-script
    - crontab - <"crontab/crontab"
    - ./fish/bin/make-default-shell
    - fish -c fisher
    - ./bash/bin/test
    - gcloud components update --quiet
    - ./git/bin/test
    - ./git-duet/bin/test
    - fix-gnupg-permissions
    - ./gnupg/bin/test
    - ./tldr/bin/test
    - ./vim/bin/test
    - fix-compaudit
    - ./zsh/bin/test
    - setup-a-keyring-for-sops secret-store purplebooth-secret-storage sops sops-key
    - bash -c "if [[ ! -f ~/.config/gcloud/application_sops_credentials.json ]] ; then cp \"~/.config/gcloud/application_default_credentials.json\" \"~/.config/gcloud/application_sops_credentials.json\" ; fi"
    - ./1password/bin/generate-envsecret


Industry - Save sessions

Save current state of a session after adding layers and geometry so they can return to it and submit to FMO or others.

@bferguso Not sure if this is included in MVP or not, there is a "No?" in the MVP column of the spreadsheet


register.go:89: Database is unavailable.

Hi Joseph,
I am trying to make a new gowebapp using mariadb 10 and go1.9.2  , but I get this error at registration:
$ go build && ./myapp
2018-01-22 08:05:42 AM Running HTTP :8090
2018-01-22 08:05:47 AM <IP_ADDRESS>:50590 POST /register
2018-01-22 08:05:48 AM <IP_ADDRESS>:50590 GET /register
2018-01-22 08:05:49 AM <IP_ADDRESS>:50590 GET /static/favicons/favicon-32x32.png
2018-01-22 08:05:57 AM <IP_ADDRESS>:50590 POST /register
register.go:89: Database is unavailable.

Here is the relevant config.js:
	"Database": {
		"Type": "MySQL",
		"Bolt": {
 			"Path": "gowebapp.db"
  		},
		"MongoDB": {
			"URL": "<IP_ADDRESS>",
			"Database": "myappdb"
		},
		"MySQL": {
			"Username": "myuser",
			"Password": "mypasswd",
			"Name": "myappdb",
			"Hostname": "<IP_ADDRESS>",
			"Port": 3306,
			"Parameter": "?parseTime=true"
		}

I did not forget to replace the database name into myappdb before  importing mysql.sql schema to mariadb.
In terminal, I can also connect to the database using myuser and mypassword and see 3 tables are being created on myappdb.
I have also another app based on  gowebapp (created about a year a go) which is still compiles and runs fine.
So I'm out of ideas and appreciate your hints.

Closing - old issue.


Can't start the connector using the documentation

Hi, i'm trying to set up an egeria instance and connect to it using the hadoop connector.
I'm using the documentation in: https://odpi.github.io/egeria-connector-hadoop-ecosystem/getting-started/index.html#/7/1
Currently i have deployed an apache atlas instance using docker:
docker run -p 9026:9026 -p 9027:9027 -p 21000:21000 docker.io/planetf1/apache-atlas:latest

An apache kafka instance using:
bin/zookeeper-server-start.sh config/zookeeper.properties
bin/kafka-server-start.sh config/server.properties

And i followed the documentation except the part that is using the truststore.p12

The OMAG server chasis gets opened in a http 8080 port
The atlas server is in the 21000 port using http
Everything is in the same machine

The fact that i use http instead of https is the only difference.
But when i launch the server using:
curl -k -X POST "http://localhost:8080/open-metadata/admin-services/users/admin/servers/atlas/instance"

I always get this error:
Desktop → curl -k -X POST "http://localhost:8080/open-metadata/admin-services/users/admin/servers/atlas/instance"
{"class":"SuccessMessageResponse","relatedHTTPCode":500,"exceptionClassName":"org.odpi.openmetadata.adminservices.ffdc.exception.OMAGConfigurationErrorException","exceptionCausedBy":"org.odpi.openmetadata.repositoryservices.ffdc.exception.OMRSConfigErrorException","actionDescription":"activateWithSuppliedConfig","exceptionErrorMessage":"OMAG-ADMIN-500-001 Method activateWithSuppliedConfig for OMAG server atlas returned an unexpected exception of org.odpi.openmetadata.repositoryservices.ffdc.exception.OMRSConfigErrorException with message OMRS-CONNECTOR-400-005 The connector to the local repository failed with a org.odpi.openmetadata.repositoryservices.ffdc.exception.OMRSLogicErrorException exception and the following error message: OMRS-REPOSITORY-400-025 Local metadata repository has not initialized correctly because it was unable to create its metadata collection","exceptionErrorMessageId":"OMAG-ADMIN-500-001","exceptionErrorMessageParameters":["atlas","activateWithSuppliedConfig","org.odpi.openmetadata.repositoryservices.ffdc.exception.OMRSConfigErrorException","OMRS-CONNECTOR-400-005 The connector to the local repository failed with a org.odpi.openmetadata.repositoryservices.ffdc.exception.OMRSLogicErrorException exception and the following error message: OMRS-REPOSITORY-400-025 Local metadata repository has not initialized correctly because it was unable to create its metadata collection"],"exceptionSystemAction":"The system is unable to work with the OMAG server.  No change was made to the server's configuration document.","exceptionUserAction":"This is likely to be either a configuration, operational or logic error. Look for other errors.  Validate the request.  If you are stuck, raise an issue."}
I dont underestad what means Local metadata repository has not initialized correctly because it was unable to create its metadata collection
The other configuration posts calls does not throw any error, just a {"class":"VoidResponse","relatedHTTPCode":200} as the documentation says.
Could someone give me some hint about what is happening? I'm really stuck at this point.
Thank you very much in advance!

The REST API call that is failing is starting up the repository proxy server called "atlas" on the OMAG Server Platform.  This call interprets the configuration document created by the previous administration calls and attempts to start up the services requested.  The repository services failed to start the atlas repository connector.  This acts as a client to Apache Atlas, translating Egeria requests into calls to Apache Atlas's APIs.  The error message that you see is saying that this connector is unable to initialize correctly.
To find out more, you need to look at the audit log messages that appear in the console of the platform (stdout).  This should show the exception and stack trace coming out of the repository connector.

Hi, Thanks for the help.
I was able to make it work, but I don't fully underestand why it does not work using this configuration.
As the documentation says in the page you sent me:
"The URL to which we post indicates that we will use the Egeria server chassis's built-in repository proxy capability to access the Apache Atlas repository connector."
https://localhost:9443/open-metadata/admin-services/users/admin/servers/atlas/local-repository/mode/repository-proxy/connection

To make it work i used this:
curl -k -X POST "http://localhost:8080/open-metadata/admin-services/users/admin/servers/atlas/local-repository/mode/in-memory-repository"

I underestand that this uses the "local-repository" wich the documentation says that is just for testing.
Doing this change i'm not really using the Apache Atlas connector?
Or the Local-repository is like an internal database where to save the data?
Sorry if the question is to naive, i'm trying to figure it out using the documentation that i have.

@rubtobar as you guessed, the last command you issued changed the server from a repository proxy server that runs the atlas connector to a metadata access store that runs the in-memory repository - which I do not think is what you want.
Egeria is an integration technology.  It has a platform on which you can configure and run many different servers.  Egeria supports different types of servers.  Each type of server focuses on integrating particular types of technology.  Apache Atlas is a metadata repository and so it has a repository connector that runs in a type of server called a repository proxy.  The instructions you were following explain how to set up a repository proxy server on your platform.
https://egeria-project.org/concepts/repository-proxy/
Its local repository is Apache Atlas and it connects to other servers via a cohort.
https://egeria-project.org/features/cohort-operation/overview
The repositories in the other servers are referred to as "remote repositories".
So if we go back to your original problem then we need to understand what is wrong with the set up of the atlas repository connector.  This will probably be described in the audit log console message output by Egeria's platform.  If you share these messages - and the curl command used to configure the atlas connector then I might be able to spot what is wrong

Hi, thanks for the explanation.
Here is my log when i try to start the egeria server platform.
egeria-platform.log
The Apache Atlas connector is in the same directory as the server platform .jar
And the commands i used to configure the server are:
To start the server:
jdk-22/bin/./java -Dstrict.ssl=false -Dloader.path=. -Dserver.port=9456 -jar server-chassis-spring-4.2-20230529.083359-1.jar

To configure the server:
curl -k -X POST -H "Content-Type: application/json" --data '{"producer":{"bootstrap.servers":"my-kafka-url:9093", "sasl.jaas.config": "com.sun.security.auth.module.Krb5LoginModule required useTicketCache=true;", "sasl.mechanism": "GSSAPI", "security.protocol": "SASL_SSL", "sasl.kerberos.service.name":"kafka"},"consumer":{"bootstrap.servers":"my-kafka-url:9093", "sasl.jaas.config": "com.sun.security.auth.module.Krb5LoginModule required useTicketCache=true;", "sasl.mechanism": "GSSAPI", "security.protocol": "SASL_SSL", "sasl.kerberos.service.name":"kafka"} }' "http://localhost:9456/open-metadata/admin-services/users/admin/servers/atlas/event-bus?connectorProvider=org.odpi.openmetadata.adapters.eventbus.topic.kafka.KafkaOpenMetadataTopicProvider&topicURLRoot=egeria"

curl -k -X POST "http://localhost:9456/open-metadata/admin-services/users/admin/servers/atlas/cohorts/mycohort"

curl -k -X POST -H "Content-Type: application/json" --data '{"class":"Connection","connectorType":{"class":"ConnectorType","connectorProviderClassName":"org.odpi.egeria.connectors.apache.atlas.repositoryconnector.ApacheAtlasOMRSRepositoryConnectorProvider"},"endpoint":{"class":"Endpoint","address":"localhost:31443","protocol":"https"},"userId":"admin","clearPassword":"mypassword"}' "http://localhost:9456/open-metadata/admin-services/users/admin/servers/atlas/local-repository/mode/repository-proxy/connection"

Start the connector
curl -k -X POST "http://localhost:9456/open-metadata/admin-services/users/admin/servers/atlas/instance"

As you can see the Apache Atlas server is in the same server on port 31443. There's nothing in between (no firewalls or anithing).
And the Kafka cluster i'm using uses kerberos to log-in. This is another thing that is giving me problems, but this error is shown even using a minimal Kafka instance deployed in the same machine for testing, with no security enabled. So i think the problem is between egeria and the apache atlas server.
Thanks your help :D

And that is the response i get from the server when executing the initialization command:

curl -k -X POST "http://localhost:9456/open-metadata/admin-services/users/admin/servers/atlas/instance"
{"class":"SuccessMessageResponse","relatedHTTPCode":500,"exceptionClassName":"org.odpi.openmetadata.adminservices.ffdc.exception.OMAGConfigurationErrorException","exceptionCausedBy":"org.odpi.openmetadata.repositoryservices.ffdc.exception.OMRSConfigErrorException","actionDescription":"activateWithSuppliedConfig","exceptionErrorMessage":"OMAG-ADMIN-500-001 Method activateWithSuppliedConfig for OMAG server atlas returned an unexpected exception of org.odpi.openmetadata.repositoryservices.ffdc.exception.OMRSConfigErrorException with message OMRS-CONNECTOR-400-005 The connector to the local repository failed with a org.odpi.openmetadata.repositoryservices.ffdc.exception.OMRSLogicErrorException exception and the following error message: OMRS-REPOSITORY-400-025 Local metadata repository has not initialized correctly because it was unable to create its metadata collection","exceptionErrorMessageId":"OMAG-ADMIN-500-001","exceptionErrorMessageParameters":["atlas","activateWithSuppliedConfig","org.odpi.openmetadata.repositoryservices.ffdc.exception.OMRSConfigErrorException","OMRS-CONNECTOR-400-005 The connector to the local repository failed with a org.odpi.openmetadata.repositoryservices.ffdc.exception.OMRSLogicErrorException exception and the following error message: OMRS-REPOSITORY-400-025 Local metadata repository has not initialized correctly because it was unable to create its metadata collection"],"exceptionSystemAction":"The system is unable to work with the OMAG server.  No change was made to the server's configuration document.","exceptionUserAction":"This is likely to be either a configuration, operational or logic error. Look for other errors.  Validate the request.  If you are stuck, raise an issue."}

The logs says that the atlas client can not find a class ...
Caused by: java.lang.NoClassDefFoundError: org/apache/commons/configuration/PropertiesConfiguration
	at java.base/java.lang.ClassLoader.defineClass1(Native Method)
	at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1018)
	at java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
	at java.base/java.net.URLClassLoader.defineClass(URLClassLoader.java:524)
	at java.base/java.net.URLClassLoader$1.run(URLClassLoader.java:427)
	at java.base/java.net.URLClassLoader$1.run(URLClassLoader.java:421)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:714)
	at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:420)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:593)
	at org.springframework.boot.loader.LaunchedURLClassLoader.loadClass(LaunchedURLClassLoader.java:151)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526)
	at org.apache.atlas.AtlasBaseClient.getClientProperties(AtlasBaseClient.java:335)
	at org.apache.atlas.AtlasBaseClient.initializeState(AtlasBaseClient.java:448)
	at org.apache.atlas.AtlasBaseClient.<init>(AtlasBaseClient.java:131)
	at org.apache.atlas.AtlasClientV2.<init>(AtlasClientV2.java:138)

It looks like you need to add the apache commons configuration library (https://commons.apache.org/proper/commons-configuration/userguide/overview.html) to Egeria's libs in the docker build.
Also  ... I had a look at the documentation that you are using and I agree it is misleading in terms of terminology.  We are in the process of consolidating our documentation on a new site (https://egeria-project.org/) and this got missed out ...

Hi @dwolfson I'm currently deploying the connector in a linux server directly. I'm currently launching the service using the commands that the documentation shows.
If the Docker deployment is the recomended i will try to do it that way.
In the enviroment we currently have bare metal machines, i'm launching the connector in the same machine where atlas is deployed. We also have a Kafka cluster in a multiple of this bare melat machines, and i whould like to use this production kafka instance to comunicate the cohort.
Maybe i'm missing some JAR files as @mandy-chessell is pointing out that the service can't find some libraries.
I will try to use the dockerfile as a referece to see what librearies i'm missiong out.
If i can't find it i will use the Docker image to deploy egeria in the machine.
Rubén

Hello @rubtobar,
@dwolfson and I tried to get this connector up and running last week and hit issues too.   The Atlas client was missing a class that we have not been able to track down.
This connector has not been used for a couple of years and I am not surprised it is not working.  In that time we have upgraded Java twice (now on 17).  Atlas has also had a couple of releases.
Because of a limitation in Atlas, this repository connector is only able to retrieve metadata from Atlas.  It can not store new open metadata in Atlas.  This limitiation has understandably reduced its usefulness which is why we stopped investing in it.
About a month ago, we started to create a new connector for Atlas to replace this one.  The new connector is an integration connector.  (See https://egeria-project.org/guides/developer/integration-connectors/overview/). When finished, the integration connector will be able to perform a 2-way exchange of metadata in and out of Atlas.   We are also hoping to call the Atlas REST API directly to eliminate the Atlas client.  (The Atlas client is based on java 8 and pulls in a lot of Hadoop libraries.)  This will simplfy its set up.
So, which is better for you?  My preference would be to accelerate the work on the new Atlas connector and try to get it finished for R4.2 (branching 17th July, shipped end of July).  Would this fit in your schedule?  What are your overall goals?
The alternative is that we could focus on getting this connector working for 4.2 and work on its replacement in 4.3.

Hi @mandy-chessell @dwolfson,
I do agree that a new Atlas Connector would be the best option.
Our goal by now is to sync the metadata from Atlas into a IBM Watson Knowledge Catalog. In the last releases, IBM WKC has added Egeria compatibility with their product.
https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=administering-configuring-synchronization-external-repositories

Excellent :) So what types of metadata are most important to you? And what levels of control do you need?
I am currently working on is to synchronize glossaries between Atlas and the repositories (like WKC) connected to the open metadata ecosystem.   It is possible to set up the connector to synchronize all glossaries or specific named glossaries.
Next I was going to look at bringing Hive tables from Atlas into the open metadata ecosystem.  This would include their tags (classifications); connection information and links to glossary terms.  Is this useful?
What else? and do you care about Atlas lineage?

Hi @mandy-chessell,
Yes, bringing all the hive tables to the ecosistem is very usefull for us.
I'm going to prepare a list of thigs to be more specific about the data that we would like to add to the open metadata ecosistem.
Lineaje is important for us, yes. We are using the MANTA integrated softare in the WKC to manage lineage in the platform.
As soon as i got the list i'll post it in here if that would help :D

That would be brilliant - thank you :)

Hi @mandy-chessell,
Currently we are using:
Hive
Impala
Nifi
HDFS
Hbase
Spark
Ozone
Avro
Kafka
Whould it be usefull to give you our Atlas type system graph?
It contains more concrete objects of every one of this types.
Thanks!

hi @mandy-chessell ,
there's somenthing  we could test or do right now?
theres some slack channel to keep in contact about this?
thanks!
Rubén

Hello @rubtobar, I added an update to the Apache Atlas integration connector yesterday.  This is for the 4.2 release we are working on this week.  Would you like a call to see it demonstrated and to show you how to set it up? How about Thursday afternoon?
Are you on our slack - I have just sent you an invite.  There are a number of egeria channels.  For example, #egeria-announce for new features and #egeria-discussion for questions.

Hi @mandy-chessell,
I have joined the slack grup. Thanks for the invite.
I'm in CEST time.
Thursday between 14:00-16:00 CEST  would be a good fit if it suits you.
We are in contact in Slack too.
Thanks!


Fix for signature test

Fixes signature tests:

@jgallimore I'm going to merge this so we can move our work to https://github.com/tomitribe/geronimo-specs

@jgallimore I'm going to merge this so we can move our work to https://github.com/tomitribe/geronimo-specs

The PR and merge to Tomitribe fork was this one: https://github.com/tomitribe/geronimo-specs/pull/1


Don't pin libc.

Is there any reason this is needed? This prevents updating other stuff in Gecko.

@shravanrn can we merge this -- or at least as @emilio to rebase and then merge?  Updating to getrandom 0.1.14 will require a similar change, and this change produces less churn on its own.

oh sorry, I don't know what it is about github pr's that somehow never notify me. I'll merge this.

Actually looks like the getrandom change also includes this. I'll just merge and test that. Closing this PR.


Issue with az login error for null_resource

I have created the following null_resource

The command tha is running is
az functionapp config appsettings set --name ${self.triggers.function_app_name} --slot ${self.triggers.slot} --resource-group   ${self.triggers.resource_group_name} --settings 'APPINSIGHTS_INSTRUMENTATIONKEY=${self.triggers.instrumentation_key}'
The problem is that when i run it from my pipeline i shows an error that needs az login.
The plugin does not support null_resource that run az cli?

Hi @epapalefkas, have you found a solution for your problem? I have the same issue that I need run the az login command.

I have not used the extention. Instead used azure CLI to run terraform.
.
Terraform does not adapt so quickly, so for azure related resources consider bicep.

The client ID and secrets are saved as environment variables, so you will need to use them and do az login again yourself.
resource "null_resource" "az_command" {
  provisioner "local-exec" {
    command = <<EOC
      set -ex
      if [ -n "$ARM_CLIENT_ID" ]; then
        # We are running on an Azure DevOps agent, need to log in
        az login --service-principal \
                 --username "$ARM_CLIENT_ID" \
                 --password "$ARM_CLIENT_SECRET" \
                 --tenant "$ARM_TENANT_ID" \
                 --output none
      fi

      az functionapp <WHATEVER YOUR AZ COMMAND IS DOING HERE>
      EOC
  }


Fix code scanning alert - Weak hashes

Tracking issue for:

[ ] https://github.com/microsoft/Web-Dev-For-Beginners/security/code-scanning/1

Link is not working!!


Prevent dcos-history leaking auth tokens

High-level description
dcos-history used a common method for creating the headers used to make
requests to mesos (which could have an Authorization header set with a token)
and making responses to the client.
This led to the auth token being leaked in the header.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS-40373 History service returns its auth token in the header

Checklist for all PRs

[x] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label ready for review

@mesosphere-mergebot bump-ee

:yell_at_cloud:

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

teamcity/dcos/test/aws/onprem/static has a single test_vip failure. It needs an override with https://jira.mesosphere.com/browse/DCOS_OSS-2115.

You wrote this, but nobody did the override. Still, the tests are all green.
Did someone re-run the test?
One of my standard quotes recently:

The override command provides structured data representing the pain, and we evaluate these data later. Without issuing the override command it is "as if the flake didn't happen"

@jgehrcke I reran the failing tests this morning as I knew they were failing due to infra issues, they all passed.

@jgehrcke I reran the failing tests this morning as I knew they were failing due to infra issues, they all passed.

@ArmandGrillet which tests failed and why? Let's run the corresponding override commands in retrospect. Each override command is a valuable data point used in subsequent analyses.

@jgehrcke Docker w/ Static Backend and Security Strict https://jira.mesosphere.com/browse/DCOS-41304

@mesosphere-mergebot override-status teamcity/dcos/test/azure/arm https://jira.mesosphere.com/browse/DCOS-41324

@mesosphere-mergebot override-status teamcity/dcos/test/aws/onprem/static https://jira.mesosphere.com/browse/DCOS_OSS-2115

AWS Onprem w/ Static Backend was failing because of https://jira.mesosphere.com/browse/DCOS-39700

I think it was https://jira.mesosphere.com/browse/DCOS_OSS-2115 by looking at the logs again.
Thanks, Armand. Have now issued the overrides.
Please, amplify this voice among your peers: don't re-run without also issuing an override command :-) Override commands actually help us prioritize work based on facts, not so much based on opinions!


where is the code? it said code was here but it is empty.

Hi there, thanks for your interest. Now the codes are open.


Update gems

Coverage remained the same at 87.228% when pulling 007a1a7d51f0db9027abb7c6562ee3d053aaabd5 on update-gems into c567d80da9b73538d6be4bc871a0180b02ceb839 on master.


Merge ts files with ffmpeg

Using copy or cat to combine the files might leave you with a file that plays far past the limit and can't seek along with playback issues.

On windows system, explorer can't generate thumbnail for videos merged by copy command.

if user don't install the ffmpeg, it will throw error. Can you provide a parameter to enable merge files with ffmpeg? This parameter is disable by default.
User still can use the merge file method by default.
BTW, the templist.txt also need to be deleted after merge successfully.

if user don't install the ffmpeg, it will throw error. Can you provide a parameter to enable merge files with ffmpeg? This parameter is disable by default.
User still can use the merge file method by default.
BTW, the templist.txt also need to be deleted after merge successfully.

Can you provide a parameter to enable merge files with ffmpeg? This parameter is disable by default

Currently I check ffmpeg by invoking ffmpeg -L and fallback to default if failed, would it be more convenient? Glad to add a new option if there is still a need.

Can you provide a parameter to enable merge files with ffmpeg? This parameter is disable by default

Currently I check ffmpeg by invoking ffmpeg -L and fallback to default if failed, would it be more convenient? Glad to add a new option if there is still a need.

For me, I'd like to add new option to call ffmpeg to merge file

Sorry for the long delay! I've added a new option for ffmpeg.


Allow streaming when using exec

Related to #263

Cassettes need to be re-recorded, do you want me to do it ?

Thanks! Yes, please re-record.

I'm using boot2docker, latest docker image is 1.5, is that an issue ? Seems that the version you're currently using is 1.6

Running rake vcr:spec on master throws some errors for me :
rspec ./spec/docker/container_spec.rb:113 # Docker::Container#rename renames the container
rspec ./spec/docker/image_spec.rb:314 # Docker::Image.create when the Image does not yet exist and the body is a Hash sets the id and sends Docker.creds
rspec ./spec/docker/image_spec.rb:375 # Docker::Image.save when a filename is specified exports tarball of image to specified file
rspec ./spec/docker/image_spec.rb:383 # Docker::Image.save when no filename is specified returns raw binary data as string
rspec ./spec/docker_spec.rb:181 # Docker#info returns the info as a Hash

I'm on OSX Yosemite with the latest boot2docker.
I've done everything stated in TESTING.md
Not sure if the culprit is boot2docker or anything else going wrong on my system.

I only re-recorded the cassettes I needed and now it's green :)

Hmm. CI is still failing. I can take a look this evening.

It's because of a complexity violation :/
On Mon, Apr 6, 2015, 15:48 Bright Fulton<EMAIL_ADDRESS>wrote:

Hmm. CI is still failing. I can take a look this evening.
—
Reply to this email directly or view it on GitHub
https://github.com/swipely/docker-api/pull/272#issuecomment-90070567.

Can you share how you're going about the streaming?
I used the following with a simple container running just bash and it's streaming for me just fine.
c = Docker::Container.all.first
c.exec(["/bin/bash","-c","while [ 1 ]; do echo hello; sleep 5; done"]) do |stream, chunk|
  puts "#{stream}: #{chunk}"
end

I'm doing exactly the same way, and I only get a response when the command
is finished.
I'm on OSX and using boot2docker, not sure if this changes anything
On Tue, Apr 7, 2015, 21:49 Todd Lunter<EMAIL_ADDRESS>wrote:

Can you share how you're going about the streaming?
I used the following with a simple container running just bash and it's
streaming for me just fine.
c = Docker::Container.all.first
c.exec(["/bin/bash","-c","while [ 1 ]; do echo hello; sleep 5; done"]) do |stream, chunk|
puts "#{stream}: #{chunk}"
end
—
Reply to this email directly or view it on GitHub
https://github.com/swipely/docker-api/pull/272#issuecomment-90711861.

I ran your code to be extra sure and I'm having no output at all since it's an infinite loop.
This is very strange that you're getting it to work on your development environment

I wonder if this has to do with SSL.  You're using one of the latest boot2docker, right?

The latest, and I have to disable ssl verification
On Tue, Apr 7, 2015, 23:04 Todd Lunter<EMAIL_ADDRESS>wrote:

I wonder if this has to do with SSL. You're using one of the latest
boot2docker, right?
—
Reply to this email directly or view it on GitHub
https://github.com/swipely/docker-api/pull/272#issuecomment-90732009.

I have done the same and using the code above, this PR isn't working for me.  I am thinking this has to do with Excon's SSLSocket versus regular Socket.  Using tcpdump I can see the 5 second echo payload, but cannot see Excon producing anything from it.  Will need to look into deeper.

@tlunter any updates on this one?
I tried to apply those changes, and it does not seem to work for me.

@danielmanesku I haven't been able to look into this one since my last post.  Would love it if you could take a deep dive if you're available to do so.

Thanks for a quick reply! I am busy at the moment with something else, but I added this on my TODO list and I will try to investigate in the coming weeks.


bazel_latest: 2.1.0 -> 3.0.0

Motivation for this change
Upgrade to latest version of Bazel.
Things done
Renamed bazel_2 to bazel_latest, upgraded.

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

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

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

Not sure what this is about, is it a preexisting issue on master?
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/qfsz9zn71803bhwqzr8fmhkcbfp58762-bazel-watcher-0.10.3
shrinking /nix/store/qfsz9zn71803bhwqzr8fmhkcbfp58762-bazel-watcher-0.10.3/bin/ibazel
cannot find section .dynamic
strip is /nix/store/sq2b0dqlq243mqn4ql5h36xmpplyy20k-binutils-2.31.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/qfsz9zn71803bhwqzr8fmhkcbfp58762-bazel-watcher-0.10.3/bin
patching script interpreter paths in /nix/store/qfsz9zn71803bhwqzr8fmhkcbfp58762-bazel-watcher-0.10.3
checking for references to /build/ in /nix/store/qfsz9zn71803bhwqzr8fmhkcbfp58762-bazel-watcher-0.10.3...
cannot find section .dynamic
error: build of '/nix/store/i33llps78bk1145jmkjx5vlmdg0fmamr-bazel-test-shebangs.drv' failed

This removes Bazel 2, which I don't think is what we want. I think a separate commit introducing Bazel 3 (bazel_3: init at 3.00) is in order, without changing the default.

correct, please leave the individual bazel version, then bazel_latest should just be aliased to whatever happens to be latest

don't want to end up with tensorflow broken for another 4 months

Tensorflow uses bazel_0_26 and bazel_0_29, and I saw a PR for a version of tensorflow that uses bazel_1, is there one that uses bazel_2? Rather than adding a new bazel derivation for each bazel version regardless of whether other derivations are using them or not, wouldn't it make sense to only add versions that are used? So rather than leave bazel_2 and add bazel_3 now, then bazel_4 etc, we can keep bazel_latest rolling, and add bazel_2 when we update tensorflow to a version that needs bazel_2, bazel_3 when we need that etc. And when we remove the last package that is using bazel_0_26 we can remove that.
That way we don't add more and more bazel derivations with no clear way of reducing the number of them.

Bazel releases a new major at most every 3 months, according to:
https://docs.google.com/document/d/1NCKLVwYMMp7Wjpb4-49FuVCWmQci6i4WZQVvm3u-WcI/edit#heading=h.t52pudpvuk1s
Bazel 1.0.0: 2019-10-10 https://github.com/bazelbuild/bazel/releases/tag/1.0.0
Bazel 2.0.0: 2019-12-19 https://github.com/bazelbuild/bazel/releases/tag/2.0.0
Bazel 3.0.0: 2020-04-06 https://github.com/bazelbuild/bazel/releases/tag/3.0.0
This is why I think there's too many version to keep them all regardless of whether another derivation is using them or not.

I can definitely see the use case where a future version of tensorflow requires bazel_2.

One possible policy would be to always keep

The current release
The last major release
All releases that are currently in use

Keeping the last major release will make it possible to use a semi-recent version of bazel in packages like tensorflow which always lag behind a bit.

Tensorflow 2.1.0 (latest stable release) requires bazel 0.29; they're currently doing the release candidates for 2.2.0, which looks like it's going to be on bazel 3.0:
https://github.com/tensorflow/tensorflow/commit/2f65c2468d7ff69df9caed94fa4cd6e01d1bd87a

Rebased on current master to see if the issue is still there.
ping @mboes @kalbasit @Profpatsch

I'm still getting the same error, but I haven't figured out how to reproduce it locally.

We can revive bazel versions posthumously if some package upgrades to an older version.

Agreed, I'd say delete old bazel versions, unless it's actually being used by something that can't upgrade to a newer one.

Huh @uri-canva, what’s the reason this PR was closed?

I never managed to figure out the reason behind this error on ofborg:
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/qfsz9zn71803bhwqzr8fmhkcbfp58762-bazel-watcher-0.10.3
shrinking /nix/store/qfsz9zn71803bhwqzr8fmhkcbfp58762-bazel-watcher-0.10.3/bin/ibazel
cannot find section .dynamic
strip is /nix/store/sq2b0dqlq243mqn4ql5h36xmpplyy20k-binutils-2.31.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/qfsz9zn71803bhwqzr8fmhkcbfp58762-bazel-watcher-0.10.3/bin
patching script interpreter paths in /nix/store/qfsz9zn71803bhwqzr8fmhkcbfp58762-bazel-watcher-0.10.3
checking for references to /build/ in /nix/store/qfsz9zn71803bhwqzr8fmhkcbfp58762-bazel-watcher-0.10.3...
cannot find section .dynamic
error: build of '/nix/store/i33llps78bk1145jmkjx5vlmdg0fmamr-bazel-test-shebangs.drv' failed

I switched to using bazelisk from nix and instead of bazel, and letting bazelisk get bazel, so I closed this PR so other people wouldn't get blocked on it and could start their own attempts to upgrade.

FYI Tensorflow 2.2 build with bazel 2.0.0


MAINT simplify tqdm calls

Codecov Report

Merging #34 into develop will decrease coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop      #34      +/-   ##
===========================================
- Coverage    98.83%   98.83%   -0.01%
===========================================
  Files           54       54
  Lines         4386     4363      -23
  Branches       485      474      -11
===========================================
- Hits          4335     4312      -23
  Misses          27       27
  Partials        24       24

Impacted Files
Coverage Δ

skhubness/reduction/mutual_proximity.py
100% <100%> (ø)
:arrow_up:

skhubness/neighbors/onng.py
100% <100%> (ø)
:arrow_up:

skhubness/neighbors/lsh.py
96.82% <100%> (-0.13%)
:arrow_down:

skhubness/reduction/local_scaling.py
100% <100%> (ø)
:arrow_up:

skhubness/neighbors/random_projection_trees.py
98.88% <100%> (-0.1%)
:arrow_down:

Continue to review full report at Codecov.

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


Gptq refactor

Type of Change
feature
API changed or not: yes
Description

[x] Reduce additional initialization of quantizer between prepare and convert
Before:

Now:
Reduce additional initialization of quantizer between prepare and convert

[x] Migrate GPTQ to Torch new 3x API

GPTQ
from neural_compressor.torch.quantization import get_default_gptq_config, prepare, convert
quant_config = get_default_gptq_config()
model= prepare(model, quant_config)
run_fn(model)
q_model = convert(model)

How has this PR been tested?
Pre-ci

Final decision:

One more thing, suggest merging it into master directly.


Remove panic from wasi stop

Although we cannot actually stop a running wasi runtime, we can drop the handle from the map and not panic so we don't stop the whole thing from running

Hey @thomastaylor312, can you please share a little more detail on how this can occur and how others can reproduce this? I'm assuming this has to do with a kubectl delete pod?

Right now when we call stop on a wasi runtime, it panics because of the unimplemented macro. This will happen any time a pod is deleted


Closing and reopening a PR probably causes a failure

We're in the middle of a blog post release, so I can't provide full details/debugging, but it looks like closing an reopening a PR causes a failure in the build actions. The issue seems to persist if I create s new PR from the same branch:
make_bucket: pulumi-hugo-origin-pr-2668-a0af4c46
Synchronizing to s3://pulumi-hugo-origin-pr-2668-a0af4c46...
Sync complete.
http://pulumi-hugo-origin-pr-2668-a0af4c46.s3-website.us-west-2.amazonaws.com/
Completed 6 Bytes/6 Bytes (37 Bytes/s) with 1 file(s) remaining
upload: public/latest-version to s3://pulumi-hugo-origin-pr-2668-a0af4c46/latest-version
Writing result metadata.
Completed 237 Bytes/237 Bytes (1.3 KiB/s) with 1 file(s) remaining
upload: ./origin-bucket-metadata.json to s3://pulumi-hugo-origin-pr-2668-a0af4c46/metadata.json

An error occurred (ParameterAlreadyExists) when calling the PutParameter operation: The parameter already exists. To overwrite this value, set the overwrite option in the request to true.
make: *** [Makefile:46: ci-pull-request] Error 254
Error: Process completed with exit code 2.

https://github.com/pulumi/pulumi-hugo/actions/runs/4641506644/jobs/8214550437?pr=2668

@jkodroff yeah I believe this is due to reopening the PR that was previously closed. I believe it is due to a collision in the parameter store, since the keys are derived from the commit sha if I am remembering correctly. So when you reopened, it was probably at the same commit that it was at before and tried to put the same parameter that was already existing when it attempted to regen the preview. We should be able to find a way around this.

@sean1588 should i add this to the papercuts tracking issue?


fix(metrics): solve bug on type assertion on apecer and bpcer functions

Codecov Report

Merging #13 (23a7629) into main (d0daaaa) will not change coverage.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main      #13   +/-   ##
=======================================
  Coverage   90.14%   90.14%
=======================================
  Files          60       60
  Lines        1887     1887
=======================================
  Hits         1701     1701
  Misses        186      186

Impacted Files
Coverage Δ

gradgpad/foundations/metrics/apcer.py
100.00% <100.00%> (ø)

gradgpad/foundations/metrics/bpcer.py
100.00% <100.00%> (ø)

gradgpad/foundations/metrics/eer.py
100.00% <100.00%> (ø)

...adgpad/foundations/metrics/metrics_demographics.py
100.00% <100.00%> (ø)

gradgpad/foundations/scores/scores.py
91.84% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add support for configurable default route (default GW)

This PR removes the hardcoded default route from VPP to the host stack. Instead,
it allows specifying a custom default gateway as a node-config option Gateway
in the contiv-vpp.yaml deployment file.
In order to remove the default route to host on VPP, specific routes need to be added:
VPP needs to be able to reach host's local IP addresses (addresses on interfaces not bound to VPP),
since one of them may be the main IP address of the node, as k8s sees it. Since this IP is used
for NAT translations of services with host networking, PODs behind VPP need to be able to reach it.
Note: "github.com/vishvananda/netlink" should be added as an explicit dependency once https://github.com/contiv/vpp/pull/574 is merged. Not required for successful build, since it already exists in the vendor folder due to transient dependencies.

Coverage decreased (-0.2%) to 75.961% when pulling c52273ddf1465a758d4495d53781d55676803068 on rastislavszabo:master into 05330953f4e1be4aaa4b24f95f3286ac42692ed4 on contiv:master.

I'll try to finish the required KSR changes today or not later than tomorrow.


Enable passing nginx ./configure parameters to build_ngx_pagespeed.sh when using --assume-yes

This would allow automated installs to configure nginx properly before building, without user intervention. Surely --with-http_ssl_module is pretty common these days, it's a shame having to forgo --assume-yes because of this.

You're right, we should definitely have this.  Working on this today.


Benchmarking

We need to benchmark ALR against other search methods, as well as have a test benchmark to see if system parts work working.
Lets look up recommended methods for benchmarking.
We will need to choose benchmarks too:

Amit examples
Others?

Add your notes here:

Standardized Installation Test:
Time                          =            1/seconds
Dependency failures           =            - 1,-2,etc
Cross platform                =            + 1 each for windows, linux and mac , 2 for web-based
Cross platform (docs)         =            + 0.5 each for windows, linux and mac
Prerequisite specific         =            python or any other version specific ??
post install                        Depth of search                =            ordinal 0 ------> 10
Total retrieves per search      =            comparison  a/b , or the s/n
1% , 5% , 10% relevancy test   =            ordinal scale -2 , -1, 0, +1, +2
Output formats                 =            PDF +1, HTML/xml +2, Text, 1.5
Downstreaming applications     =            Feature extraction , summarization , (+1 for each)
Interface                           Documentation                  =            Ordinal scale 0 ------> 5
UI                             =            Command line = 1, interactive shell = 2 , local GUI (tk like) = 3 , web browser(html) = 4
Updates
New updates (all major releases and bug fixes) in last 1 year      =  +n
New updates (all major releases and bug fixes) in last 5 years     =  +n
Relevancy testing, (to be manually tested or using TF - IDF) algorithm made
1%, 5%, and 10% relevancy tests, assessed on an ordinal scale ranging from -2 to +2,
1% for the very large datasets
5% for the medium sized datasets
10% for small like 100 papers


#42: Response information was added to the callbak to provide access …

…to the headers

@UnbounDev please promote it to the master

This looks like a very valuable addition to me.
However, I would argue that it would make sense to instead pass the whole response object to the callback, we should extract the rate limit info and map it to an easily processable format.
This way we A) have a layer of abstraction over the HTTP internals that are not particularly relevant to the caller, and B) the rate info in a format that can immediately be used instead of having to parse it on the side of the caller.
According to the API docs, strava provides the rate info as two HTTP headers with two parts each:
X-Ratelimit-Limit: 600,30000
X-Ratelimit-Usage: 642,27300

That is comma separated the short term and long term usage and limit.
My suggestion would be to parse those two headers inside the util._requestHelper to the following format and pass it to the callback as a third parameter rateLimit:
{
    "shortTermUsage": 642,
    "shortTermLimit": 600,
    "longTermUsage": 27300,
    "longTermLimit": 30000
}

This seems like a cleaner API design to me then just passing the response object back and would still fulfill your requirement of providing rate information.
Your thoughts?

Hi @TimoSta,
Absolutely agree with your format. For me just important to get this information in any representation, because right now I have to calculate it by myself and it's an additional complexity in my code.
Should I prepare a PR according to your description or you can do?

@vlavrynovych If you don't mind, please go ahead. I will merge it into master then ASAP.
Could you please make sure that there is some unit test coverage of this feature and maybe a short paragraph outlining the feature in the Usage section of the readme? We should strive to improve the quality of the project to keep it maintainable, and I believe proper documentation is an important first step.
Thank you!

Hello @TimoSta,
Could you please help me with tests. I've ran my new test locally and it works perfect.
Also I've tried to run all the tests using npm test from the master branch without any changes and they failed. Please assist.

@TimoSta,
401 Unauthorized is returning from Strava

Thanks for making this change.
We had an issue where the test set for the authenticator cleared the STRAVA_ACCESS_TOKEN environment variable, which is used by Travis to authenticate the test cases. This causes all following tests to fail due to auth errors. This was resolved with 0ee9444a2646d0445224246707ebac61a2f9b545 on the master.
Additionally, we have a short term limit of 600 calls to the Strava API within 15 minutes. This has also caused tests to fail randomly in the past.
Bottom line is, the server side build againt the actual API is very unreliable and brittle right now. I will write a stub for the Strava API to test against instead when I find some time for it to enable us to reliably run unit tests. Until then, we will have to live with what we have.
I will go ahead and merge this change into the master. In combination with the fix I mentioned above, the test suite should run on the server as well. If not, I'll find out why. :-)
-- Timo

Looks good to me. Thanks!

@TimoSta,
Thank you too. Finally we can continue work on this cool library.

+1
The build was successful on the master: https://travis-ci.org/UnbounDev/node-strava-v3/builds/221752993


Limit testcase name to 120 chars.

Reason:
Encrypted filesystems have a smaller limit on maximum file name
length (somewhere around 123 chars).
Fixes #1610

bors try

bors try

bors r+

Just an important note that the libcxx 5000+ tests should also be tested with this change. I suspect there are several files that violate this limitation.

bors r-

@anitagov All righty, I'll kick off a full test build with this branch.

Oh, @anakrish tested the original change on an encrypted disk with full libcxx tests, and is kicking off another test with my additional change. Thanks!

Confirmed that all the all the libcxx tests pass when run in an encrypted filesystem.

bors r+


Special-case React StyleSheets

Flow seems not to know that the output type of StyleSheet({k1: {...}, k2: {...}}) is an object with keys "k1" and "k2". Here is a simple repro case:
/**
 * @providesModule ExampleStyles
 * @flow
 */
var {StyleSheet} = require('react-native');
var ExampleStyles = StyleSheet.create({
  button: {},
});
module.exports = ExampleStyles;

Used by another module:
/**
 * @providesModule ExampleComponent
 * @flow
 */
var ExampleStyles = require('ExampleStyles');
var React = require('react-native');
var {View} = React;
var ExampleComponent = React.createClass({
  render() {
    return <View style={ExampleStyles.button} />;
  },
});
module.exports = ExampleComponent;

Flow (v0.7.0) says "property button \ Property not found in ExampleStyles.js".

Supporting this case in a general way would be even better, since there are projects like https://github.com/pjjanak/react-native-nested-stylesheets that could benefit too.

Immutable.Record has the same kind of API, where a constructor function takes an object and returns an object with the same properties (and others).

One thing is that Flow seems to handle stylesheets within the same JS file fine, but if the stylesheet object is imported from another module it has issues. Immutable records might have the same problem (haven't tried it but the function signature is pretty similar to StyleSheet's).
StyleSheet.js:
static create(obj: {[key: string]: any}): {[key: string]: number}
Immutable.js:
new (values: {[key: string]: any}): Map<string, any>

I have been dealing with this problem recently. The best way as of now is this. Define your styles like this:
/**
 * @providesModule ExampleStyles
 * @flow
 */
var {StyleSheet} = require('react-native');
var ExampleStyles = {
  button: {},
};
var toExport: typeof ExampleStyles = StyleSheet.create(ExampleStyles);
module.exports = toExport

This will give you exactly the bahaviour you want. Using an incorrect key will throw an error, and autocomplete should potentially work.
Ideally, declaring the type of the Stylesheet.create method should do the same, but so far that hasn't worked for me:
declare module 'react-native' {
  declare class StyleSheet {
    declare function create<T: Object>(styles: T): T;
  }
}

Maybe there is a slightly different syntax for this??

Something like this works for aphrodite:
declare module "aphrodite" {
  /**
   * Aphrodite style declaration
   */
  declare type StyleDeclaration = {
    [key: string]: CSSProperties;
  }

  declare type StyleDefinition = { _name: string, _definition: Object };
  declare type StyleSheetDefinition<T> = { [key: $Enum<T>]: StyleDefinition };

  declare interface StyleSheetStatic {
    /**
     * Create style sheet
     */
    create<T: StyleDeclaration>(styles: T): StyleSheetDefinition<T>;
    /**
     * Rehydrate class names from server renderer
     */
    rehydrate(renderedClassNames: string[]): void;
  }
}

The key is in:
  declare type StyleSheetDefinition<T> = { [key: $Enum<T>]: StyleDefinition };

This typechecks rightly, but autocomplete doesn't work unfortunately.

@aaronjensen I've been trying to solve the problem on both sides.

StyleSheet.create takes and object and returns an object. This is easy enough to write a type for:

declare module 'aphrodite' {
  declare var exports: {
    StyleSheet: {
      create: <O: Object>(styles: O) => {[key: $Keys<O>]: string}
    }
  }
}

Here, O is a subtype of just object. Ideally, we could write a really huge type that type checks all of CSS, but this is slow, and will not work perfectly anyway as different CSS-in-JS libraries support different parts of the spec.
The $Keys part (same as $Enum, though I think $Keys is the new canonical name now) should work correctly in theory, but I have seen autocomplete not working with it too. That I think is something that should be marked as a bug for Flow to solve.

@nmn Here is my complete types for aphrodite, based on the typescript ones from definitely typed: https://gist.github.com/aaronjensen/7151830b15e3bb35485763c5c89c7033
Good to know about $Keys replacing $Enum, thanks.
I opened a bug for the autocomplete issue: #2433

@aaronjensen Those types look pretty epic. Perhaps many of the anys can be replaced by number and string.
Also, would you submit your types for aphrodite to FlowTyped please!

We fixed this in React Native with $Keys, Flow shouldn't need to special case StyleSheet anymore.

I'm going to close this, it seems that $ObjMap solves this issue


Allow metrics endpoint token to be shared

Non-admin users most likely will not have permissions to connect to the prometheus server.
This PR allows admins to share their tokens with all users - the backend metrics can then use the admin token to get the metrics for an application that the requesting user has permission to access.
This allows non-admin users to see application metrics for their applications. They can't see any other metrics.

LGTM. Works only for metrics shared endpoints, for CF endpoints I ran into permission issues.


Better handling of uncompressed zip files.

I did a first try to fix this issue. I'm not sure if my fix is correct. This fixes #477
My test is not working now because there is a EndOfStreamException thrown which I don't know how to avoid or if this is correct.

The Zip file in your test exposes two problems with the library

The archive.ExtractAllEntries does not propagate the compressed/uncompressed sizes of entries
Your test file is generated in streamed mode, the size information is missing (set to 0), trying to skip will fail in current implementation. (need the size from the above)

One way to solve this would be to handle the searching for the Data descriptor, this can be tricky, you could embedd a zip in a zip and you might detect the wrong one.
This would be an example implementation
https://github.com/Erior/sharpcompress/tree/feature/Failed-to-extract-onedrive-zipped-file

@Erior thanks for your hint. This l guided me in the right direction.
The problem was a unset skip marker so the inner file was skipped several files which lead to the exception.

thanks for the fix...it looks sound


Highlight SME input on the data for Challenge details page

We want to enable Organizers to highlight whether their Challenge dataset was annotated/curated with clinical subject matter expertise.
Consider ways of more visibly highlighting the clinical institutions (e.g: Penn Medicine, UW Medicine, Radiological Society, etc) contributions towards the dataset, on the Challenge details page.

Challenge sponsors are now shown on the challenge details page.


Removed deprecated method on CMSToolbarLoginForm.

This method is a no-op in Django 1.6 and removed in 1.7.

Coverage decreased (-0.0%) to 90.66% when pulling 864392c0a642029210f20f474e4f56e76747846c on timgraham:test-cookie into 0dbb961f8427a74845dc9f226987b8f4a525bed8 on divio:develop.

combined with https://github.com/divio/django-cms/pull/3792


fix(types): make MagicStringOptions optional

Looks based on usage that both of these properties are optional.
Currently, I can't provide an option with just filename without providing indentExclusionRanges.

Someone please merge this

Duplicated 183


Banner/Counter - Sunspotter Citizen Science Challenge

Design a banner to feature on Sunspotter home for the Sunspotter Citizen Science Challenge (8/29-9/5)

Hopefully this fits the bill. I envisioned the banner itself being a progress with a marker at the current level. Would be cool if on page load the fill could be animated.

Pretty!
On Tue, Aug 25, 2015 at 2:27 PM, Heath V<EMAIL_ADDRESS>wrote:

Hopefully this fits the bill. I envisioned the banner itself being a
progress with a marker at the current level. Would be cool if on page load
the fill could be animated.
[image: sunspot-citsci-banner]
https://cloud.githubusercontent.com/assets/4551411/9476949/2cfede70-4b35-11e5-93b4-003cd71c0f57.jpg
—
Reply to this email directly or view it on GitHub
https://github.com/zooniverse/Sunspots/issues/13#issuecomment-134708536.

--
Citizen Science Education Lead
Adler Planetarium

How's this? http://www.sunspotter.org/staging/

Looks great to me.
Thanks,
Kelly
On Tue, Aug 25, 2015 at 9:52 PM, Chris Snyder<EMAIL_ADDRESS>wrote:

How's this? http://www.sunspotter.org/staging/
—
Reply to this email directly or view it on GitHub
https://github.com/zooniverse/Sunspots/issues/13#issuecomment-134801373.

--
Citizen Science Education Lead
Adler Planetarium

I ended up changing the numeric color to white to match the site and be more legible.


Should gh.nvim config.prefer_https_remote use gh config?

The gh config already stores the user preference for https/ssh.
Do you think you should respect that as well? as all the other actions use gh under the hood I'm assuming.

Aha!
🖭  gh config list
git_protocol=ssh
editor=
prompt=enabled
pager=
http_unix_socket=
browser=

That would be pretty cool, and probably the right thing to do, so you're thinking, on gh.nvim startup, do something like:
🖭  gh config get git_protocol
https

and then automatically set the git remote accordingly?

Yes I think thats the approach

Would you want to take on that PR? Seems relatively straight forward.

Yeah I can do that

Cool, we may want an "auto" flag in the "prefer_https_remotes" config value, where we dynamically look it up. This then still allows the user to force "ssh" or "https" if they want to. Maybe its useful?

My intuition is that a user wouldn't need to define a different protocol for gh.nvim that is different than gh.
I would add it in the future if there's an interest but I could be wrong here

@David-Kunz in issue #15 you had to flip the "prefer_https_remote" flag in your private repo.
In this issue we are trying to determine if we looked at the "gh config list" command and set the remote type with the setting in there, would it have set the correct remote for you?
Could you run that command in your private repo where you're using the "prefer_https_remote" flag and tell us the value of the "git_protocol" config.

Hi @ldelossa,
When I execute gh config list, the value is gh_protocol=https.
Best regards,
David

Cool, thanks @David-Kunz.
a little unscientific @dlvhdr but seems like on all our systems the gh cli matches the git protocol that works. Just wanted to make sure.

Closed! Thanks again @dlvhdr

Thank occurred just now:
~/git/vim/litee-gh-testing remotes/litee-gh_ldelossa/litee-gh-testing/branch-1
🖭  gh config list
git_protocol=ssh
editor=
prompt=enabled
pager=
http_unix_socket=
browser=

~/git/vim/litee-gh-testing remotes/litee-gh_ldelossa/litee-gh-testing/branch-1
🖭  gh config get git_protocol
https

Weird lol. I manually set it to get it to work again.
~/git/vim/litee-gh-testing main
🖭  gh config set git_protocol ssh

~/git/vim/litee-gh-testing main
🖭  gh config get git_protocol
ssh


argo-rollouts pod can't match virtualservice sourceLabels

Bug Description
my virtualservice spec is
spec:
  hosts:
    - example-demo02-stable
  http:
    - match:
        - sourceLabels:
            role: canary
      route:
        - destination:
            host: example-demo02-canary
            port:
              number: 8080
    - route:
        - destination:
            host: example-demo02-stable
            port:
              number: 8080

and my rollout have set labels to stable pod and canary pod like this
    canary:
      canaryMetadata:
        labels:
          role: canary
      stableMetadata:
        labels:
          role: stable

on first canary the pod have the wright labels so the rule is match
but when canary done, the canary pod will become stable pod and the label is change to stable, but it still match the canary rule, i think istio have already record this pod have canary label but not update to stable label.
can i have update the record for the right labels?
Version
client version: 1.13.5
control plane version: 1.15
data plane version: 1.13.5 (8 proxies)

Client Version: v1.24.1
Server Version: v1.22.8+k3s1

Additional Information
No response

I think i know what's the cause, you update the pod label at some time after it is stable, right? Unfortunately, istio does not update  proxy labels after startup.

sound so bad, i just found if i restart the pod it will match my virtualservice rule
so there is no way can i update the proxy labels? or any workaround can  do?

Take a look at my fix

i'm not familiar with istio code, how can i test it😅

Just build a new pilot discovery image and replace

We're still seeing this issue.  If I understand correctly, the fixes did not make it into the Istio 1.15 release.  Are there any updates we need to do to do to get this working in our environment, or can we expect to see it in an upcoming release?

right


Where is the DXDialogService in DevExpress.Mvvm.Free?

I only use DevExpress.Mvvm.Free for MVVM, not the full DevExpress framework. I want to inject the IDialogService into IoC container, but I can't find the implementation for registering.

Hello,
You can use the techniques described in the following help topic to register a DevExpress MVVM service in an IoC container: Use Services with Dependency Injection.
P.S. Would you please clarify why you chose the DevExpress MVVM framework over other free frameworks?
Thanks,
Alexander

I had read this, but the example is DXMessageBoxService, I need DialogService but not found.


Adds tests for get_one

This PR
Attempting to help along with https://github.com/jonhoo/rust-evmap/issues/31.
Notes
It appeared that get_one wasn't tested. I'm not sure if these tests are in the right place or if they should live in read/mod. Or maybe this isn't tested because it's not valuable functionality? 🤷
I tried to handle both inner cases - ValuesInner::Short and ValuesInner::Long. I'm not 100% sure it's necessary to test ValuesInner::Long because, although it's supported, it's clearly documented that, in the case of multiple values, the exact return value is not guaranteed. So it's nice to make sure it doesn't explode with multiple values but it also doesn't feel particularly useful asserting any particular returned value. I also feel pretty badly about the magic number with no hard-reference to BAG_THRESHOLD. ~If we do want to improve the readability there, it looked like there was a with_capacity on Options but I didn't see one for evmap so I wasn't sure how to do that idiomatically. I probably read the docs wrong.~ It looks like you can do something like:
Options::default().with_capacity(BAG_THRESHOLD).construct()

although maybe there's a slightly more compact method.
~Finally, I don't know how to check code coverage before merging this so acknowledging that there's no guarantee the coverage will increase, I'm fine with just chucking this PR (but would still like to help if any more specific guidance is available!).~ Looks like it shows up right there in the PR! Neat!

This change is

This is great, thank you! I left some comments :)

Also, slightly unrelated - I see the CI failing scarily (to someone who didn't know why). It seems like the version of evmap in benchmark/Cargo.toml can be updated to the current 11.0.0-alpha.1. Is that something to fix or is that purposefully not being upgraded until a non-alpha/beta/whatever release lands?

Oh, yeah, good catch! If you want to include a quick fix for that in this PR too, that'd be great.

Oh, yeah, good catch! If you want to include a quick fix for that in this PR too, that'd be great.

Sorry, just saw this. Do you mind if I make it a new PR? I already had a new PR ready to go with the changes and figured it'd keep each PR's focus clean? But I'm also 100% down to combine them to reduce overhead!
I could squash all the existing commits and then add the new commit that bumps the dependency version and not squash those two if you'd prefer 👍

Beautiful! I merged that PR, and squashed and merged this one. Thanks for all your work on this :D

It's been my pleasure! Are there any other tests I should focus on next? Or any other things you've been wanting to get to but haven't had time? I really want to start contributing and learning/writing rust. Seeing as I've already learned a handful of things from this, I'd say continuing on would be fruitful. So I'm ready and rearing for anything you need or know about someone else needing! 👍

I think an awesome thing would be to adopt parts of the test suites from hashbrown and indexmap. They have extensive test suites, which evmap could possibly benefit a lot from. You'll have to work around evmap having a slightly different API, but it shouldn't be too bad, at least for the simpler tests. Some quicktests would also be fantastic.


feat: add AP-11 Diagnosing a problem in production at the pod level

@emmanuelbernard I'm not convinced this is an architectural pattern. I think it's a howto - in which case it could be a blog or similar.

@StevenTobin can you see how we can convert this one into a SOP even though not actionable from a defined root cause yet? Would you agree.
We can also see how we would also blog it for exchange, @maxandersen fancy doing a blog around it?

@StevenTobin to see if the generic SPO can be improved with that content.

Closing as not able to find the content a productive home.


Not working on Windows 7

OS: Windows 7 Enterprise SP 1 (CS conference room computer)
Firefox ESR 38.5.2
After clicking "Calculate # of Thumbnails", there's a small popup near the back button that says "Please fill out this field" and nothing further happens.
Chrome 48.0.2564.103m
After clicking "Calculate # of Thumbnails", nothing happens.

Ping @a-mabe @dhruv282

This is a usability issue. The placeholder (the gray text "http://4genderjustice.org/") makes it seem like there is a value that is pre-populating the field. Clicking the "Calculate # of Thumbnails" button gives the impression that the default, which is actually a placeholder and not a default, will be used as a parameter for processing.
A few ways to remedy this:

Change the placeholder value to "e.g., http://4genderjustice.org/" or "For example, http://4genderjustice.org/", which will give an indication that the field requires more input before he button can be pressed.
Pre-populate the field with http://4genderjustice.org/, not just as a placeholder. Use some JS that reads, on the initial use focus of the focus, that the user has interacted with the field and clears it so as to not require the user to do so...since they likely don't want to use this URI for their own test.

The latter is very inaccessible but allows for those just testing the tool to actually have results shown instead of an alert that tells them they have done something wrong. The former requires more input from the user. Consider, also, providing an example outside of the field, i.e., not as a placeholder, to help guide the user as to what is required as an example to use the tool.

Changing the placeholder value to "For example, http://4genderjustice.org/" did not fix the issue. Pre-populating the field fixed it. However, a new error appeared UnCaught TypeError: Cannot read property 'push' of undefined from timeline.js line 48.
Including this script file, https://code.jquery.com/jquery-migrate-3.1.0.js, in index.html fixed this new error, and I was able to fully calculate thumbnails on Firefox ESR 38.5.2, Chrome 48.0.2564.103m, as well as current versions of Firefox and Chrome.

Placeholder text is supposed to be an illustration or instruction rather than a default value unless a default value makes sense. By design browsers keep placeholder text in a muted color, so that is enough visual clue for people to not assume that as a value. The experience can be improved by removing the alert dialogue (these are considered a bad practice) and showing the error inline with input field highlighted in red (the way it is commonly done in form validations).

As above, a placeholder is the way to go. The issue is that it is unclear that the dimmed URI in the placeholder is not a pre-populated value. Adding the text to precede the placeholder makes it more clear that the greyed text is a placeholder value.
The first approach I mentioned above is preferred over the second, the latter which seems to have been implemented in #56.


Question concerning Equation (Reference or so)

Sorry to bother you again:
I am trying to understand the ppm part of your code.
Could you help me to explain this line:
https://github.com/atisharma/bellini/blob/d911b0bbf9d995c639758e95ccdbfbf49a1ee9b4/bellini.c#L488
I do not get the part with the exp(): Where does that come from?
and
Why os there a dt involved? I thought ppm is an average of the samples having a amplitude unit without time (e.g. V and not V/s)....
A reference where I can read that on my own would help I think, but I do not know where to look...
My target overall goal is changing the decay time to a lower value and I do not see how...

The exp(...) is the exponential decay from the single pole.
The calculations are my own from the specification referenced in the code.
The PPM average is a decaying average over time, so is described by a
stable single pole system forced by the current V. The dt arises as it
is integrated in time.
If you just want to change the decay time you can change the numerical
constant -1.3545.
On Mon, Nov 29, 2021 at 03:09:04AM -0800, chincheta0815 wrote:

Sorry to bother you again:
I am trying to understand the ppm part of your code.
Could you help me to explain this line:
https://github.com/atisharma/bellini/blob/d911b0bbf9d995c639758e95ccdbfbf49a1ee9b4/bellini.c#L488
I do not get the part with the exp(): Where does that come from?
and
Why os there a dt involved? I thought ppm is an average of the samples having a amplitude unit without time (e.g. V and not V/s)....
A reference where I can read that on my own would help I think, but I do not know where to look...
My target overall goal is changing the decay time to a lower value and I do not see how...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/atisharma/bellini/issues/4


Use the same keycodes cross-platform

Use the same keycodes cross-platform.  Keyboard keys work fine on Windows.

 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.


Error entries in the wacs 2 console

Hi guys
Thanks for this great software.
I have been using it for some time now, without any issues, and i dont think there are any related to my issue posted here. I would just like to konw how i can remove those error enteries showing in my console.
It is probably my own fault why they are showing, but short question, how do i get rid of em'?
**Client version<IP_ADDRESS>:
**Windows version2012R2:
Relevant part of log file:

You can simply delete the files that are mentioned in those error messages if you are sure that you don't need those renewals anymore. They may be leftovers from an early alpha build, if you've tried that.

Thanks, :)


translation enquiry

Hi, my name is Sangbok Lee.
I work for Hanbit Media, one of the largest IT publisher in Korea
and I'm interested in translating your book into Korean and publishing in Korea.
I've tried to contact you via our copyright agency but they said there's no reply.
Can we talk a bit further? Please tell me how to contact you. Thank you.

At this point I am not looking for translation partners.


Fix ts-check error: Type 'string' is not assignable to type '{ componentStack: string[]; }'. at src/layout/ErrorBoundary.js

Explication
This looks how a problem with types. Please to investigate what is the correct way to declare this types and implement
Screenshots

https://github.com/Azordev/dasher-user/blob/dccbce3b5b6ea8af657388eec98dfaac7b201ff9/src/layouts/ErrorBoundary.js#L26-L36
Checklist

[ ] The reason why the error occurs is known
[ ] Possible solutions were created
[ ] It was decided between fixing the error or leaving it like that

check that your tasks have the corresponding labels

This issue has solved in #104 because, currently the Error component isn't used

This is the current code of ErrorBoundary component, just render the JSX, and not import some component

I see that the component Error still is used at the Routes.
Do u think that this component should be deleted?
Since we don't use it

So, can we close this issue?


Rectangular terrain map

How should I modify the code if I am actually interested in rectangular terrain? Like 1024x512 pixels.

Going to look into this soon as it's something that annoys me as well... only 4 years later! ;)