fixed casing responsible for linux build agent failures

Overview/Summary
Replace this with a brief description of what this Pull Request fixes, changes, etc.
This PR fixes/adds/changes/removes
Fixes casing within the policies.bicep file.  Failures were occurring when using a linux agent to build.
Breaking Changes
None
As part of this Pull Request I have

[ ] Read the Contribution Guide and ensured this PR is compliant with the guide
[ ] Checked for duplicate Pull Requests
[ ] Associated it with relevant GitHub Issues or ADO Work Items (Internal Only)
[ ] Ensured my code/branch is up-to-date with the latest changes in the main branch
[ ] Ensured PR tests are passing
[ ] Updated relevant and associated documentation (e.g. Contribution Guide, Docs etc.)

Prior to change
Build was failing due to wrong case used when calling the file
/azp/_work/1/s/patterns/alz/templates/policies.bicep(144,21) : Error BCP091: An error occurred reading file. Could not find a part of the path '/azp/_work/1/s/services/Network/frontdoors/Deploy-FD-BackendHealth-Alert.json'. /azp/_work/1/s/patterns/alz/templates/policies.bicep(145,21) : Error BCP091: An error occurred reading file. Could not find a part of the path '/azp/_work/1/s/services/Network/frontdoors/Deploy-FD-BackendRequestLatency-Alert.json'. /azp/_work/1/s/patterns/alz/templates/policies.bicep(187,21) : Error BCP091: An error occurred reading file. Could not find a part of the path '/azp/_work/1/s/services/storage/storageAccounts/Deploy-SA-Availability-Alert.json'. /azp/_work/1/s/patterns/alz/templates/policies.bicep(188,21) : Error BCP091: An error occurred reading file. Could not find a part of the path '/azp/_work/1/s/services/storage/storageAccounts/Deploy-ActivityLog-SA-Delete-Alert.json'.

After the Change
Build was successful

@cdomansky again thank you for your input and for submitting the pull request, I couldn't merge this PR due to the build errors. However, I've updated the casing in the dev branch, which is planned to merge by the end of the month.


Function import path not correct in tamagui example

From Discord: if helpful you can actually use the entire thing in the tamagui repo if you're willing to wait for yarn install and ignore all the tamagui stuff, just:
git clone git@github.com:tamagui/tamagui.git
yarn
yarn build
yarn vertql

and you can see it run / genreate schema etc.

I think I see the issue here. There is a tsconfig.json in the repo root and also one in apps/vertql-example. Unless you specify a specific tsconfig via a config option or cli option, Grats will fallback to finding one relative to the current working directory. I suspect the schema was generated with grats running in the root dir, and then when it runs from within the project directory it ends up using a different tsconfig.
The issue is that we rely on the tsconfig to tell us where the .js version of the file is going to be placed. So we are looking for js file where the root config would have put it rather than where the example app's tsconfig is actually putting it.
Need to think more about how we can avoid this issue or at least provide a more helpful error message.

Looking more closely, this wasn't the actual issue. I now believe the actual issue is that the setup in tamagui is to use esbuild-register to dynamically convert typescript to javascript at runtime. This breaks our dynamic imports because they expect the .js file to exist on disk.
Possible mitigation/solution is to include both the js module and ts module in the directive and use a try/catch to try each one, perhaps with some caching?

Exploring a fix here: https://github.com/captbaritone/grats/pull/56

Reopening as the issue still reproduces even after #56


Add LightningModule.lr_scheduler_step

What does this PR do?

Fixes #10190
Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

sure :)

Where is the issue/RFC describing this feature and what it aims to solve? The PR has 0 summary for what this PR does. This makes it very difficult for anyone in the community to review.
This is touching the core LightningModule! There needs to be much more information about this before changes are just merged

Where is the issue/RFC describing this feature and what it aims to solve? The PR has 0 summary for what this PR does. This makes it very difficult for anyone in the community to review.
This is touching the core LightningModule! There needs to be much more information about this before changes are just merged

It's still draft. Attached the issue link in the description.


feat: migrating the wcme track to webrtc core

Moved the track related logic from https://sqbu-github.cisco.com/CPaaS/web-client-media-engine/tree/main/src
to webrtc core
Removed the effects for now untill we export public types for the effects
Did some minor test fixes , no other changes are done for now
moved some of the eslint rules from wcme to core

Did you have to make any changes to the files being copied over? Or is it all copy-paste from wcme?

@bbaldino  yep only the files in the wcme branch thats it

sure @bbaldino  did not touch any of the track related stuff , eslint , test fix and logger (moved from WCME)
once i raise a PR for WCME next you should see what has been removed and what the function names
will have a PR ready by tomorrow for WCME
I have no plans to change any track without having a proposal for it or JIRA (Might take help from WCME team )


Cannot be installed on linux due to binary dependencies

$ npm i knip -g
npm ERR! code 1
npm ERR! path /home/raynos/projects/nvm/versions/node/v18.16.1/lib/node_modules/knip/node_modules/tree-sitter-bash
npm ERR! command failed
npm ERR! command sh -c prebuild-install || node-gyp rebuild
npm ERR! make: Entering directory '/home/raynos/projects/nvm/versions/node/v18.16.1/lib/node_modules/knip/node_modules/tree-sitter-bash/build'
npm ERR!   CC(target) Release/obj.target/tree_sitter_bash_binding/src/parser.o
npm ERR!    In file included from ../src/parser.c:1:
npm ERR! ../src/parser.c: In function ‘ts_lex_keywords’:
npm ERR! ../src/tree_sitter/parser.h:135:8: warning: variable ‘eof’ set but not used [-Wunused-but-set-variable]
npm ERR!   135 |   bool eof = false;             \
npm ERR!       |        ^~~
npm ERR! ../src/parser.c:12592:3: note: in expansion of macro ‘START_LEXER’
npm ERR! 12592 |   START_LEXER();
npm ERR!       |   ^~~~~~~~~~~
npm ERR! make: g++-10: No such file or directory
npm ERR! make: *** [tree_sitter_bash_binding.target.mk:122: Release/obj.target/tree_sitter_bash_binding/bindings/node/binding.o] Error 127
npm ERR! gyp ERR! build error
npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
npm ERR! gyp ERR! stack     at ChildProcess.onExit (/home/raynos/projects/nvm/versions/node/v18.16.1/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
npm ERR! gyp ERR! System Linux 6.2.6-76060206-generic
npm ERR! gyp ERR! command "/home/raynos/projects/nvm/versions/node/v18.16.1/bin/node" "/home/raynos/projects/nvm/versions/node/v18.16.1/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd /home/raynos/projects/nvm/versions/node/v18.16.1/lib/node_modules/knip/node_modules/tree-sitter-bash
npm ERR! gyp ERR! node -v v18.16.1
npm ERR! gyp ERR! node-gyp -v v9.3.1
npm ERR! gyp ERR! not ok

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/raynos/.npm/_logs/2023-08-21T15_46_25_651Z-debug-0.log

The tree sitter bash library does not compile.

Yeah sorry about that. Duplicate of #209, let's track it over there.

It's clearly not a duplicate because it has nothing to do with missing python and everything to do with the third party dependency not compiling due to a bug in their C++

It looks like they hard coded g++-10 somewhere
npm ERR! make: g++-10: No such file or directory

And because I don't have g++-10 on my laptop I cannot compile this third party depedency.

I should probably install 2.19.5 instead because it does not have the broken third party dependency.

I should probably install 2.19.5 instead because it does not have the broken third party dependency.

Yes.
I'm thinking about downgrading tree-sitter-bash to v0.19.0 but that will likely not help you here either.

You might want to try v2.19.8 with the downgraded 3rd party dep.

We have this same issue and v2.19.8 does not fix it I'm afraid. The newest version that works is v2.18.0 .

It's clearly not a duplicate because it has nothing to do with missing python and everything to do with the third party dependency not compiling due to a bug in their C++

Sorry about that, read and assumed too fast that "No prebuilt binaries found" would essentially be the same issue (since the binaries are missing):

npm ERR! prebuild-install warn install No prebuilt binaries found (target=18.16.1 runtime=node arch=x64 libc= platform=linux)

tree-sitter-bash v0.19.0 has this list of binaries: https://github.com/tree-sitter/tree-sitter-bash/releases/tag/v0.19.0. Not sure what's missing that would match your environment(s)?
Wanted to get rid of an ancient dependency. Also see #72. The tree-sitter replacement works slightly better than bash-parser, so I don't fancy reverting, which would be a breaking change again.

None of those prebuilt binaries have anything to do with prebuild-install ( https://github.com/tree-sitter/tree-sitter-bash/blob/master/bindings/node/index.js ).
If you look at https://www.npmjs.com/package/leveldown?activeTab=code it has the binaries in the npm package.
If you look at https://www.npmjs.com/package/tree-sitter-bash?activeTab=code you will see zero binaries in the npm tarball.
The package author of tree-sitter-bash has to change their npm publish strategy ( see https://github.com/Level/leveldown/blob/master/.github/workflows/release.yml as reference )

Guess this wasn't the right time for tree-sitter yet. Reverted to bash-parser in v2.19.11.
Thanks for all the info, I will look into it and pass it through.

None of those prebuilt binaries have anything to do with prebuild-install ( https://github.com/tree-sitter/tree-sitter-bash/blob/master/bindings/node/index.js ).

prebuild-install uses the prebuilt binaries in the GitHub Release by default (the script you link then uses the GitHub Release asset fetched through prebuild-install).
With linking to https://github.com/tree-sitter/tree-sitter-bash/issues/188 I'm going to close this issue.
Tips & tricks still most welcome, either for preventing similar issues in the future or for alternatives.


Add a programmable API to non-ui command line options

Fixed added the APIs https://github.com/google/android-classyshark/releases/tag/6.0


Update dependencies to latest version

Hello guys, can you please update dependencies to the latest version? There are some breaking changes when using compileSdkVersion 33 with some of deprecations on the package versions you are using

Thanks for the suggestions @AndonZeno


MODULE NOT FOUND

While trying to run the program it shows module not found. Due to this issue, it is not possible to run the program. The screenshots of the error are attached below.

As for now we don't have requirements.txt file though I opened a PR to fix this.


truststore and certifi-win32 cause error stating file is already open

To reproduce:
Install the following on a Windows machine:

requests - latest
certifi
python-certifi-win32
truststore
python 3.10

Then run:
import requests
The error pops up stating that the file is already open by another program.

@achapkowski Could you please show us the full error that you saw? That may clarify whether it has anything to do with truststore. I suspect it doesn't, because your reproduction steps don't include importing truststore's SSLContext.
Trying to use python-certifi-win32 and truststore at the same time doesn't make sense to me. They are both attempting to accomplish something similar (trust CAs from Windows trust stores) by opposite mechanisms. python-certifi-win32 extracts CA certs from the Windows stores and constructs a combined file that includes both those certs and the ones from certifi, then patches certifi to use the combined file instead of its original bundle. On the other hand, truststore attempts cert verification twice, first using the Windows trust store and then using the certs from the certifi bundle (or other that have been loaded). Using them both should in theory not be a problem, but the work that python-certifi-win32 does to extract the Windows CA certs is unnecessary, and the patches it applies could contribute to subtle problems like this.
That said, let me be clear that unlike python-certifi-win32, truststore does not automatically install itself to be used by requests. One way to do this is by using a custom transport adapter for requests:
import requests
import requests.adapters
import truststore

class TruststoreHTTPAdapter(requests.adapters.HTTPAdapter):
    def init_poolmanager(self, *args, **kwargs):
        kwargs['ssl_context'] = truststore.SSLContext()
        return super().init_poolmanager(*args, **kwargs)

session = requests.Session()
session.mount('https://', TruststoreHTTPAdapter())
response = session.get(url)

@achapkowski By the way, thanks for giving truststore a try! :) Is there a project or initiative in particular you're trying to integrate the library with? We're interested in gathering an initial set of users to prove out our implementation.

I'm trying to use truststore with requests on the Windows OS. I would like to leverage the windows store over the certifi store.

If you don't install python-certifi-win32 with truststore this error does not occur.  It's really strange TBH.
Environment Setup
Python Version: Python 3.10
Packages:
requests>=2.24.0
python-certifi-win32;platform_system=='Windows'
truststore;python_version >= '3.10'

Code to Reproduce
import requests
import truststore

Full Stack
File "C:\envs\mypy310\Lib\importlib\_common.py", line 89, in _tempfile
  os.write(fd, reader())
File "C:\envs\mypy310\Lib\importlib\abc.py", line 371, in read_bytes
  with self.open('rb') as strm:
File "C:\envs\mypy310\Lib\importlib\_adapters.py", line 54, in open
  raise ValueError()

builtins.ValueError

During handling of the above exception, another exception occurred:

￼File "C:\SVN\requests_issue_truststore_demo\src\___test_requests_only.py", line 4, in <module>
  certifi_win32.wincerts.verify_combined_pem()
File "C:\envs\mypy310\Lib\site-packages\certifi_win32\wincerts.py", line 65, in verify_combined_pem
  with open(certifi_pem()) as certifi_pem_handle:
File "C:\envs\mypy310\Lib\site-packages\certifi_win32\wincerts.py", line 52, in certifi_pem
  import certifi
File "C:\envs\mypy310\Lib\site-packages\wrapt\importer.py", line 177, in _exec_module
  notify_module_loaded(module)
File "C:\envs\mypy310\Lib\site-packages\wrapt\decorators.py", line 470, in _synchronized
  return wrapped(*args, **kwargs)
File "C:\envs\mypy310\Lib\site-packages\wrapt\importer.py", line 136, in notify_module_loaded
  hook(module)
File "C:\envs\mypy310\Lib\site-packages\certifi_win32\wrapt_certifi.py", line 20, in apply_patches
  certifi_win32.wincerts.CERTIFI_PEM = certifi.where()
File "C:\envs\mypy310\Lib\site-packages\certifi\core.py", line 37, in where
  _CACERT_PATH = str(_CACERT_CTX.__enter__())
File "C:\envs\mypy310\Lib\contextlib.py", line 135, in __enter__
  return next(self.gen)
File "C:\envs\mypy310\Lib\importlib\_common.py", line 95, in _tempfile
  os.remove(raw_path)

builtins.PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: 'C:\\Users\\USERACCOUNT\\AppData\\Local\\Temp\\1\\tmpuiyh5sdq'File "C:\\envs\mypy310\Lib\importlib\_common.py", line 89, in _tempfile
  os.write(fd, reader())
File "C:\envs\mypy310\Lib\importlib\abc.py", line 371, in read_bytes
  with self.open('rb') as strm:
File "C:\envs\mypy310\Lib\importlib\_adapters.py", line 54, in open
  raise ValueError()

builtins.ValueError

During handling of the above exception, another exception occurred:

File "C:\SVN\requests_issue_truststore_demo\src\___test_requests_only.py", line 4, in <module>
  certifi_win32.wincerts.verify_combined_pem()
File "C:\envs\mypy310\Lib\site-packages\certifi_win32\wincerts.py", line 65, in verify_combined_pem
  with open(certifi_pem()) as certifi_pem_handle:
File "C:\envs\mypy310\Lib\site-packages\certifi_win32\wincerts.py", line 52, in certifi_pem
  import certifi
File "C:\envs\mypy310\Lib\site-packages\wrapt\importer.py", line 177, in _exec_module
  notify_module_loaded(module)
File "C:\envs\mypy310\Lib\site-packages\wrapt\decorators.py", line 470, in _synchronized
  return wrapped(*args, **kwargs)
File "C:\envs\mypy310\Lib\site-packages\wrapt\importer.py", line 136, in notify_module_loaded
  hook(module)
File "C:\envs\mypy310\Lib\site-packages\certifi_win32\wrapt_certifi.py", line 20, in apply_patches
  certifi_win32.wincerts.CERTIFI_PEM = certifi.where()
File "C:\envs\mypy310\Lib\site-packages\certifi\core.py", line 37, in where
  _CACERT_PATH = str(_CACERT_CTX.__enter__())
File "C:\envs\mypy310\Lib\contextlib.py", line 135, in __enter__
  return next(self.gen)
File "C:\envs\mypy310\Lib\importlib\_common.py", line 95, in _tempfile
  os.remove(raw_path)

builtins.PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: 'C:\\Users\\USERNAME\\AppData\\Local\\Temp\\1\\tmpuiyh5sdq'


Add encryption support for RBD volumes with KMIP

Describe the feature you'd like to have
Encryption support for RBD volumes with KMIP
The Key Management Interoperability Protocol (KMIP) is an extensible communication protocol that defines message formats for the manipulation of cryptographic keys on a key management server. This facilitates data encryption by simplifying encryption key management.
References:

What is Key Management Interoperability Protocol (KMIP)? | Thales
OASIS Key Management Interoperability Protocol (KMIP) TC
GitHub - ThalesGroup/kmip-go: KMIP client library in Golang

Thanks @Rakshith-R .. tracking this for 3.7 :+1:


Simulator backends

Working towards plug-and-play interchangability of simulator backends, ensuring input/outputs are the same.
Resolves #281 (Simulator Interfaces)
Resolves #314 (Simulator testing)
Resolves #324 (Sympy Simulator testing).
Description

Adds 2 new backends: statevector_simulator_cpp and statevector_simulator_py, used for simulating the wavefunction for a single shot, without noise and measurement. The result is returned in the quantum_state field of the result dictionary

Adds a new snapshot command for saving snapshots of simulator internal representations, over all qubits. For the python simulator, this is only the quantum_state. For the cpp simulator, this can be quantum_state, density_matrix, probabilities, etc. (refer to doc). The following simulator commands are treated like barriers to prevent reordering: snapshot, noise, save, load

Converts the qasm_simulator_sympy to statevector_simulator_sympy, since the point of a sympy simulator is to preserve precise amplitudes, not to do measurements and counts.

Adds a mechanism for providers to report information about aliased names and deprecated names.
Aliased names are useful since there could be several implementations of functionally similar backends within a provider. So, for example, the user can just write get_backend('local_qasm_simulator'), and this would return an instance of QasmSimulatorCpp(). If that is not built, then an instance of QasmSimualtorPy().
Deprecated names are useful since backend names could change. For example, now all previous code that use local_qiskit_simulator will automatically redirect to local_qasm_simualtor_cpp, with a deprecation warning.

Adds an optional compact flag when inquiring backend names from the wrapper. For example, wrapper.local_backends() returns:

['local_qasm_simulator',
 'local_clifford_simulator',
 'local_unitary_simulator',
 'local_statevector_simulator']

but wrapper.local_backends(compact=False) returns:
['local_qasm_simulator_cpp',
 'local_qasm_simulator_py',
 'local_qasm_simulator_projectq',
 'local_statevector_simulator_cpp',
 'local_statevector_simulator_py',
 'local_statevector_simulator_sympy',
 'local_unitary_simulator_sympy',
 'local_unitary_simulator_py',
 'local_clifford_simulator_cpp']

One positive effect of the above is that all previous code that simply used local_qasm_simulator now run with a faster version, if available. This speeds up running the test suite.

Adds a _validate() method to several simulators, which is called immediately before a qobj is run(). This can validate semantic things that a schema cannot, such as measurements being at the end of circuit.

The behavior of getting the quantum_state by setting shots=1 in the simulators is now deprecated. You can either use the local_statevector_simulator to do this automatically, or use the local_qasm_simulator and place an explicit snapshot command. However, backwards compatibility is still preserved.

This PR touches a lot of files, but most are only minor name changes.
New names are in accordance with this (also see picture below):

PROVIDERNAME_SIMPLEALIAS_simulator_LANGUAGEORPROJECT

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@diego-plan9 @chriseclectic I think I'm done with this PR.

Just a public note following the private discussion to remember that, when merging, this PR should get squashed as the git story is not clean (in particular, it is showing some "duplicated" commits from master with different hashes and content) and might cause issues on upcoming PRs. Can you manually verify that the changes from these commits are included in this PR:
298d42d Circuit drawing improvement
ea195d7 Backporting changes from stable-0.4.14 to master, manually.
f813445 DAGCircuit layer functions yield generators
c1752f4 Compiling with skip_translation
77ffd96 Resyncing master stable
182c2ee fixing up the backend in the example
3f6c023 WIP: Serializable Qobj + Pass cpp/projectq simulator tests

@diego-plan9 added more tests and confirmed that all previous PRs are intact.

Finally merging, thanks @ajavadia !


Remove some signed/unsigned integer comparison warnings

Can one of the admins verify this patch?

Adding @keveman for review.
However, I think TensorFlow in general prefers signed int over unsigned int. But I'll leave it up to @keveman.

Changes mainly look like the ones from this pull request, accepted at the time: https://github.com/tensorflow/tensorflow/pull/1099

@tensorflow-jenkins test this please.

@sdenel it looks like some of these were already fixed. Can you please rebase your PR? In general, this PR looks fine to me apart from the change to ExecutorState.

@rmlarsen I just rebased my PR.

@tensorflow-jenkins test this please

@sdenel It looks like you have to rebase again to pick up the changes I pushed earlier to day, sorry about the duplicate work.

@rmlarsen done!

@sdenel I'm still seeing a bunch of changes to the shape inference code in array_ops.cc. did you fail to resolve a merge conflict?

@rmlarsen It looks like I failed my first rebase :) Sorry for the mess, it should ok now.

@tensorflow-jenkins test this please
@sdenel Thanks!

@tensorflow-jenkins test this please.

@sdenel thanks for the cleanup!


Fix Output format so options are case-insensitive

Currently:
if ($OutputFormat) {
    switch ($OutputFormat) {
        CSV  {
            $OutputString = $MyKeys |
                Select-Object -Property Name,Faction,Class,Dungeon,Level,WeeklyBest |
                ConvertTo-Csv -NoTypeInformation
        }
        JSON { $OutputString = $MyKeys | ConvertTo-Json }
    }

    $OutputString | Set-Content -Encoding utf8 $Path

Actually, since issue #2 is outputting to pipeline, it should be able to work with converting to CSV or JSON using built-in cmdlets, so no need for this feature.


Allow the user to select the OSP version on which the stack will run

The bastion host must communicate with the OSP service and gather host information from the other instances.  It uses the os-collect-config RPM to configure the communications and collect information.
The location of this package depends on the version of OSP in use.  The OSP RPM repo names change with the OSP version.
This patch allows the caller to set the OSP version so that the templates can install and configure the correct version of the os-collect-config package and prepare for operation.

LGTM, Mark reported that testing this on OSP 8 and 10 was OK, merging this as there is nobody else ATM.

@markllama it would be also nice to add a note into README about posibility to set OCP version (in a followup patch).


Compiling scanner missing builder image

Hello, I'm trying to build/compile the scanner, which seems to require the image stackrox/scanner:builder-${BUILD-DIR_HASH} or in the case of CI quay.io/rhacs-eng/scanner:builder-$(BUILD_DIR_HASH).
https://github.com/stackrox/scanner/blob/master/Makefile#L26-L32
Both of these appear to be inaccessible, is this builder image accessible somewhere else or does it need to be generated through other means?

Both of these appear to be inaccessible, is this builder image accessible somewhere else or does it need to be generated through other means?

Hi Michael, I think make scanner-image-builder will provide that for you.

I think I see the problem, I've been getting this error:
Unexpected docker pull error: Error response from daemon: pull access denied for stackrox/scanner, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Which is triggering the script to die immediately instead of building the image. The specific logic I;m getting stuck on is located here:
https://github.com/stackrox/scanner/blob/master/scripts/ensure_image.sh#L29-L31
Not entirely sure what the best solution is here though.

I tried to deconstruct it but I'm hitting an error with the build:
$ docker build -t stackrox/scanner:builder-"$(git ls-files -sm build | git hash-object --stdin)" -f build/Dockerfile build/
[+] Building 2.8s (5/9)
 => [internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 37B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.1s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/centos:8                                                                                0.5s
 => CACHED [1/6] FROM docker.io/library/centos:8@sha256:a27fd8080b517143cbbbab9dfb7c8571c40d67d534bbdee55bd6c473f432b177                                  0.0s
 => ERROR [2/6] RUN yum update -y && yum install -y epel-release dnf-plugins-core                                                                         2.1s
------
 > [2/6] RUN yum update -y && yum install -y epel-release dnf-plugins-core:
#5 1.937 CentOS Linux 8 - AppStream                       30  B/s |  38  B     00:01
#5 1.945 Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist
------
executor failed running [/bin/sh -c yum update -y && yum install -y epel-release dnf-plugins-core]: exit code: 1

maybe @RTann can help us

Not sure what's going on with the centos:8 mirrors, though if I'm not mistaken that release is EOL. Switching to rockylinux:8 could be a quick workaround.

The stackrox repo (this one) builds the main image's binaries in a centos:stream8 image in publicly accessible quay.io repos. Thank you for posting this issue, as it encouraged me to copy that concept over to the scanner repo. I will respond back to this issue once that is complete.

Scanner is now build by using a quay.iostackrox-io/apollo-ci:scanner-build-<version> image in the Scanner repo. This image should be public, so I don't expect more build issues. Feel free to close the issue @msierks if you are able to build the Scanner image locally

Thanks @RTann, much appreciated. This is working as expected.


[EN] Feedback for: /web/updates/2015/03/push-notifications-on-the-open-web?hl=en

This post needs to reflect the change to the subscribe() method:
serviceWorkerRegistration.pushManager.subscribe({userVisibleOnly: true})

Also needs to be altered to remove the 'var subscriptionId = pushSubscription.subscriptionId;' piece of code - no longer valid.

More feedback (This should be confirmed :
endpoint: Check what the endpoints used are for GCM.
authentication: it is required to pass in authentication header when using GCM


Add standard 'localforage' interface for Extensions

📦 Pull Request
Adds localforage support to encourage/enforce a consistent, cross-environment compatible internal API for arbitrary storage.
🗜 Versioning
(Check one!)

[ ] Patch: Bug Fix?
[x] Minor: New Feature?
[ ] Major: Breaking Change

:rocket: PR was released in<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:


Add support to Eclipse Vert.x JsonObject

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Add new JsonProvider implementation to Vert.x's JsonObject.
Describe alternatives you've considered
N/A
Additional context
vert.x is a toolkit for reactive programming created by the developers of Eclipse. It's used by 1K+ open source projects in Maven Central. And it encapsulates a special JsonObject implementation used by that framework.
<!-- https://mvnrepository.com/artifact/io.vertx/vertx-core -->
<dependency>
    <groupId>io.vertx</groupId>
    <artifactId>vertx-core</artifactId>
    <version>4.3.3</version>
</dependency>

This enhancement aims to provide JSON Merge to work seamlessly with the JsonObject handled by the vert.x framework.
The new dependency shall be optional to avoid an unnecessary dependency on applications that do not use vert.x.
Tasks

[x] Add vert.x dependency (optional) to the jsonmerge-core project.
[ ] Create a new JsonProvider implementation named VertxJsonProvider
[ ] Create JUnit test suite VertxJsonProviderTest
[ ] Create JUnit test suite JsonMergerVertxJsonProvider extending JsonMergerTest to secure that all tests available for the other providers may pass for the new provider as well
[ ] Update README.md with new provider information

A medium-severity vulnerability is associated with the latest Vert.x version available (4.3.3).
There is currently no published exploit for this vulnerability. So this enhancement must be put "on hold" for a while.
More details of the vulnerability can be found at:
https://security.snyk.io/vuln/SNYK-JAVA-IONETTY-1042268


change drawable model "Unknown 1" property to "Bone Count"

The 'Unknown 1' property for ydr/ydd/yft drawable models refers to how many total bones the respective skel has (or 0 if the object has no skel, like a regular/static prop YDR). We should name it something like "Bone Count" or "Total Bones" or something of that nature.
For example, mp_m_freemode_01.yft has 128 bones. If you import base-game mp_m_freemode_01 uppr_015 (which requires external skel) and click on each of the High, Medium, and Low LOD drawable models for the YDD you will see that 'Unknown 1' is 128 in the Sollumz dropdown for Object Properties:

For a non-freemode example, a_c_poodle.yft has 59 bones. If you import a_c_poodle.ydd and check the drawable models for head, lowr, and uppr you will see that 'Unknown 1' is 59:

For car YFTs, I imported kalahari_hi.yft . The skel has 57 bones, and the Unknown 1 on the drawable model is 57:

I'm gonna close this for now since we aren't completely sure about this and it's not too important at the moment.


Add createTFile/TFolder functions

Merge after #69

The functions could use a little bit of documentation to explain how this differs to create and createFolder from the API, is it for creating a mock folder/file?

@Fevol it is for creating an instance of TFile/TFolder when the underlying file/folder doesn't exist

@Fevol Ready to merge


cipher list is different when DefaultTLSOptions is used and when an unmarshaled TLSOption with nil CipherSuites

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
traefik 2.11.2
Configured using kubernetes.
Reference TLSOption:
apiVersion: traefik.io/v1alpha1
kind: cipher
metadata:
  name: default
  namespace: default
spec:
  sniStrict: true

The cipher list presented to nmap -p 443 --script ssl-enum-ciphers <domain> is different when TLSOption is absent  vs when present, even though the above TLSOption configuration has no ciphers present. Specifically, the cipher "TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA" is present when TLSOption has been applied, even if no ciphers are listed.
Ciphers without TLSOption applied:
PORT    STATE SERVICE
443/tcp open  https
| ssl-enum-ciphers:
|   TLSv1.2:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (secp256r1) - A
|     compressors:
|       NULL
|     cipher preference: client
|   TLSv1.3:
|     ciphers:
|       TLS_AKE_WITH_AES_128_GCM_SHA256 (ecdh_x25519) - A
|       TLS_AKE_WITH_AES_256_GCM_SHA384 (ecdh_x25519) - A
|       TLS_AKE_WITH_CHACHA20_POLY1305_SHA256 (ecdh_x25519) - A
|     cipher preference: server
|_  least strength: A

Ciphers with TLSOption applied:
PORT    STATE SERVICE
443/tcp open  https
| ssl-enum-ciphers:
|   TLSv1.2:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA (secp256r1) - C
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (secp256r1) - A
|     compressors:
|       NULL
|     cipher preference: client
|     warnings:
|       64-bit block cipher 3DES vulnerable to SWEET32 attack
|   TLSv1.3:
|     ciphers:
|       TLS_AKE_WITH_AES_128_GCM_SHA256 (ecdh_x25519) - A
|       TLS_AKE_WITH_AES_256_GCM_SHA384 (ecdh_x25519) - A
|       TLS_AKE_WITH_CHACHA20_POLY1305_SHA256 (ecdh_x25519) - A
|     cipher preference: server
|_  least strength: C

The difference is the addition of TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA when TLSOption is applied.
Code Analysis
As of 2024-04-12 commit 1ffbffb26a3676b368c4fc52c4fb737de56cd65d on master.
pkg/tls/tlsmanager.go:37 function getCipherSuites() builds the list from crypto/tls.CipherSuites().  This results in the 3DES not being applied because the CipherSuites() call excludes that cipher.
pkg/tls/tlsmanager.go:384 in function buildTLSConfig, checks if the TLSOptions.CipherSuites is not nil. Because the default TLSOption builds the cipher suite (above) is called, when no user defined TLSOption is present, this will be called an a list of ciphers will be constructed here. However, If a TLSOption is provided, but leaves the CipherSuites off, then the *tls.Config.CipherSuites will be unset, which will result in a different list of ciphers getting applied.
This results in a different list of applied ciphers if no user supplied TLSOption is supplied vs a TLSOption is supplied but no ciphers are listed.
One solution would be to make the default ciphers explicit in all situations by adjusting pkg/tls/tlsmanager.go:384
diff --git a/pkg/tls/tlsmanager.go b/pkg/tls/tlsmanager.go
index ecf9692cf..776fc5854 100644
--- a/pkg/tls/tlsmanager.go
+++ b/pkg/tls/tlsmanager.go
@@ -381,16 +381,19 @@ func buildTLSConfig(tlsOption Options) (*tls.Config, error) {
 	}

 	// Set the list of CipherSuites if set in the config
-	if tlsOption.CipherSuites != nil {
-		// if our list of CipherSuites is defined in the entryPoint config, we can re-initialize the suites list as empty
-		conf.CipherSuites = make([]uint16, 0)
-		for _, cipher := range tlsOption.CipherSuites {
-			if cipherConst, exists := CipherSuites[cipher]; exists {
-				conf.CipherSuites = append(conf.CipherSuites, cipherConst)
-			} else {
-				// CipherSuite listed in the toml does not exist in our listed
-				return nil, fmt.Errorf("invalid CipherSuite: %s", cipher)
-			}
+	// Set default TLS Ciphers consistently.
+	ciphers := tlsOption.CipherSuites
+	if len(ciphers) == 0 {
+		ciphers = getCipherSuites()
+	}
+	// if our list of CipherSuites is defined in the entryPoint config, we can re-initialize the suites list as empty
+	conf.CipherSuites = make([]uint16, 0)
+	for _, cipher := range ciphers {
+		if cipherConst, exists := CipherSuites[cipher]; exists {
+			conf.CipherSuites = append(conf.CipherSuites, cipherConst)
+		} else {
+			// CipherSuite listed in the toml does not exist in our listed
+			return nil, fmt.Errorf("invalid CipherSuite: %s", cipher)
 		}
 	}

What did you see instead?
Inconsistent list of default ciphers, depending on if I built the TLSOption or if the default TLSOption was provided by traefik.
What version of Traefik are you using?
v2.11.2
What is your environment & configuration?
Linux
Kubernetes
If applicable, please paste the log output in DEBUG level
No response

Hello @dtscd,
Thanks a lot for reporting this, and I'm sorry for the late answer.
We confirmed the problem and attributed the p1 priority to this bug.


rake export hangs

I ran this about 18 hours ago when I was leaving the office:
$ sudo bundle exec rake production:export
Stopping huginn ...
Exporting new services ...

I don't actually know anything about Ruby, so I have no idea what to do next.

I've following the install directions at https://github.com/huginn/huginn/blob/master/doc/manual/installation.md and have completed everything up until this final step in the Install Init Script section.
System is Ubuntu 18, database is PostgreSQL running on localhost. I'm also running Mattermost on this VM, proxy'd through nginx.

Can you post the contents of the logs mentioned in the troubleshooting section?

Following the troubleshooting instructions...
sudo bundle exec rake production:check produces:
[  OK  ] Everything is fine
No nginx log yet as I haven't gotten to the step of configuring that.
The only thing in the log directory is production.log, which doesn't have any errors in it:
I, [2018-11-05T12:43:37.302749 #23377]  INFO -- : Migrating to DeviseCreateUsers<PHONE_NUMBER>0244)
I, [2018-11-05T12:43:37.345974 #23377]  INFO -- : Migrating to AddAdminToUsers<PHONE_NUMBER>5449)
I, [2018-11-05T12:43:37.385458 #23377]  INFO -- : Migrating to EnableLockableStrategyForDevise<PHONE_NUMBER>1122)
I, [2018-11-05T12:43:37.434047 #23377]  INFO -- : Migrating to AddUsernameToUsers<PHONE_NUMBER>3304)
I, [2018-11-05T12:43:37.456720 #23377]  INFO -- : Migrating to CreateEvents<PHONE_NUMBER>5930)
I, [2018-11-05T12:43:37.495722 #23377]  INFO -- : Migrating to CreateAgents<PHONE_NUMBER>3905)
I, [2018-11-05T12:43:37.548016 #23377]  INFO -- : Migrating to CreateLinks<PHONE_NUMBER>4732)
I, [2018-11-05T12:43:37.576240 #23377]  INFO -- : Migrating to CreateDelayedJobs<PHONE_NUMBER>3701)
I, [2018-11-05T12:43:37.617837 #23377]  INFO -- : Migrating to AddMemoryToAgents<PHONE_NUMBER>0705)
I, [2018-11-05T12:43:37.620532 #23377]  INFO -- : Migrating to AddInvitationCodeToUsers<PHONE_NUMBER>0049)
I, [2018-11-05T12:43:37.623391 #23377]  INFO -- : Migrating to AddIndexes<PHONE_NUMBER>0117)
I, [2018-11-05T12:43:37.635623 #23377]  INFO -- : Migrating to ChangeMemoryToLongText<PHONE_NUMBER>0736)
I, [2018-11-05T12:43:37.637683 #23377]  INFO -- : Migrating to AddLastWebhookAtToAgents<PHONE_NUMBER>3743)
I, [2018-11-05T12:43:37.639936 #23377]  INFO -- : Migrating to CreateAgentLogs<PHONE_NUMBER>0603)
I, [2018-11-05T12:43:37.661578 #23377]  INFO -- : Migrating to AddExpiresAtToEvents<PHONE_NUMBER>3248)
I, [2018-11-05T12:43:37.674507 #23377]  INFO -- : Migrating to AddKeepEventsForToAgents<PHONE_NUMBER>1558)
I, [2018-11-05T12:43:37.724196 #23377]  INFO -- : Migrating to SwitchToJsonSerialization<PHONE_NUMBER>2112)
I, [2018-11-05T12:43:37.729832 #23377]  INFO -- : Migrating to AddCachedDatesToAgent<PHONE_NUMBER>0021)
I, [2018-11-05T12:43:37.733928 #23377]  INFO -- : Migrating to CreateUserCredentials<PHONE_NUMBER>5418)
I, [2018-11-05T12:43:37.765190 #23377]  INFO -- : Migrating to ChangeHandlerToMediumText<PHONE_NUMBER>4931)
I, [2018-11-05T12:43:37.767564 #23377]  INFO -- : Migrating to AddModeToUserCredentials<PHONE_NUMBER>2747)
I, [2018-11-05T12:43:37.797673 #23377]  INFO -- : Migrating to AddEventIdAtCreationToLinks<PHONE_NUMBER>3001)
I, [2018-11-05T12:43:37.828606 #23377]  INFO -- : Migrating to AddPropagateImmediatelyToAgent<PHONE_NUMBER>1250)
I, [2018-11-05T12:43:37.876840 #23377]  INFO -- : Migrating to AddDisabledToAgent<PHONE_NUMBER>3556)
I, [2018-11-05T12:43:37.925603 #23377]  INFO -- : Migrating to RenameWebhookToWebRequest<PHONE_NUMBER>0825)
I, [2018-11-05T12:43:37.931379 #23377]  INFO -- : Migrating to MigrateAgentsToLiquidTemplating<PHONE_NUMBER>1716)
I, [2018-11-05T12:43:37.955650 #23377]  INFO -- : Migrating to CreateScenarios<PHONE_NUMBER>0420)
I, [2018-11-05T12:43:38.033770 #23377]  INFO -- : Migrating to CreateScenarioMemberships<PHONE_NUMBER>0443)
I, [2018-11-05T12:43:38.046709 #23377]  INFO -- : Migrating to CreateServices<PHONE_NUMBER>1100)
I, [2018-11-05T12:43:38.089576 #23377]  INFO -- : Migrating to AddServiceIdToAgents<PHONE_NUMBER>0040)
I, [2018-11-05T12:43:38.092385 #23377]  INFO -- : Migrating to MigrateAgentsToServiceAuthentication<PHONE_NUMBER>0140)
I, [2018-11-05T12:43:38.144438 #23377]  INFO -- : Migrating to AddFieldsToScenarios<PHONE_NUMBER>2016)
I, [2018-11-05T12:43:38.167965 #23377]  INFO -- : Migrating to AddIndicesToScenarios<PHONE_NUMBER>4917)
I, [2018-11-05T12:43:38.197857 #23377]  INFO -- : Migrating to RenameDigestEmailToEmailDigest<PHONE_NUMBER>4211)
I, [2018-11-05T12:43:38.202502 #23377]  INFO -- : Migrating to AddGuidToAgents<PHONE_NUMBER>2822)
I, [2018-11-05T12:43:38.221774 #23377]  INFO -- : Migrating to ConvertEfaSkipAgent<PHONE_NUMBER>1220)
I, [2018-11-05T12:43:38.225699 #23377]  INFO -- : Migrating to AdoptXpathInWebsiteAgent<PHONE_NUMBER>0551)
I, [2018-11-05T12:43:38.231613 #23377]  INFO -- : Migrating to ConvertEfaSkipCreatedAt<PHONE_NUMBER>5210)
I, [2018-11-05T12:43:38.234337 #23377]  INFO -- : Migrating to RemoveServiceIndexOnUserId<PHONE_NUMBER>1540)
I, [2018-11-05T12:43:38.239485 #23377]  INFO -- : Migrating to AddUidColumnToServices<PHONE_NUMBER>0922)
I, [2018-11-05T12:43:38.269929 #23377]  INFO -- : Migrating to SetCharsetForMysql<PHONE_NUMBER>0107)
I, [2018-11-05T12:43:38.273273 #23377]  INFO -- : Migrating to AddTagColorToScenarios<PHONE_NUMBER>3139)
I, [2018-11-05T12:43:38.276657 #23377]  INFO -- : Migrating to AddControlLinks<PHONE_NUMBER>3732)
I, [2018-11-05T12:43:38.316711 #23377]  INFO -- : Migrating to SetEventsCountDefault<PHONE_NUMBER>0139)
I, [2018-11-05T12:43:38.323360 #23377]  INFO -- : Migrating to AddTypeOptionAttributeToPushbulletAgents<PHONE_NUMBER>3604)
I, [2018-11-05T12:43:38.327019 #23377]  INFO -- : Migrating to UpdateKeepEventsForToBeInSeconds<PHONE_NUMBER>3436)
I, [2018-11-05T12:43:38.329707 #23377]  INFO -- : Migrating to RemoveRequirementFromUsersInvitationCode<PHONE_NUMBER>5436)
I, [2018-11-05T12:43:38.331591 #23377]  INFO -- : Migrating to WebsiteAgentDoesNotUseEventUrl<PHONE_NUMBER>1620)
I, [2018-11-05T12:43:38.340202 #23377]  INFO -- : Migrating to AddModeOptionToFtpsiteAgents<PHONE_NUMBER>0316)
I, [2018-11-05T12:43:38.346192 #23377]  INFO -- : Migrating to AddConfirmableAttributesToUsers<PHONE_NUMBER>3717)
I, [2018-11-05T12:43:38.360229 #23377]  INFO -- : Migrating to AddDeactivatedAtToUsers<PHONE_NUMBER>5413)
I, [2018-11-05T12:43:38.373447 #23377]  INFO -- : Migrating to AddDeactivatedToAgents<PHONE_NUMBER>4729)
I, [2018-11-05T12:43:38.440371 #23377]  INFO -- : Migrating to WarnAboutDuplicateUsernames<PHONE_NUMBER>5545)
I, [2018-11-05T12:43:38.445059 #23377]  INFO -- : Migrating to PostAgentSetEventHeaderStyle<PHONE_NUMBER>2512)
I, [2018-11-05T12:43:38.448431 #23377]  INFO -- : Migrating to AddIconToScenarios<PHONE_NUMBER>0930)
I, [2018-11-05T12:43:38.451122 #23377]  INFO -- : Migrating to AddXmlNamespaceOptionToDataOutputAgents<PHONE_NUMBER>3416)
I, [2018-11-05T12:43:38.455601 #23377]  INFO -- : Migrating to ChangeEventsOrderToEventsListOrder<PHONE_NUMBER>5850)
I, [2018-11-05T12:43:38.458420 #23377]  INFO -- : Migrating to RemoveQueueFromEmailDigestAgentMemory<PHONE_NUMBER>0122)
I, [2018-11-05T12:43:38.463737 #23377]  INFO -- : Migrating to SetEmitErrorEventForTwitterActionAgents<PHONE_NUMBER>1303)
I, [2018-11-05T12:43:38.469686 #23377]  INFO -- : Migrating to UpdatePushoverAgentOptions<PHONE_NUMBER>0214)
I, [2018-11-05T12:43:38.474190 #23377]  INFO -- : Migrating to ResetDataOutputAgents<PHONE_NUMBER>0910)
I, [2018-11-05T12:43:38.476621 #23377]  INFO -- : Migrating to ConvertWebsiteAgentTemplateForMerge<PHONE_NUMBER>1256)
I, [2018-11-05T12:43:38.479261 #23377]  INFO -- : Migrating to AddTemplatesToResolveUrl<PHONE_NUMBER>5838)
I, [2018-11-05T12:43:38.481700 #23377]  INFO -- : Migrating to AddMinEventsOptionToPeakDetectorAgents<PHONE_NUMBER>0555)
I, [2018-11-05T12:43:38.484820 #23377]  INFO -- : Migrating to SetRssContentType<PHONE_NUMBER>3748)
I, [2018-11-05T12:43:38.487250 #23377]  INFO -- : Migrating to MigrateGrowlAgentToLiquid<PHONE_NUMBER>1002)
I, [2018-11-05T12:45:48.058634 #23409]  INFO -- :   Rendering devise/mailer/confirmation_instructions.html.erb
I, [2018-11-05T12:45:48.060494 #23409]  INFO -- :   Rendered devise/mailer/confirmation_instructions.html.erb (1.7ms)
I, [2018-11-05T12:45:49.132128 #23409]  INFO -- : Sent mail to<EMAIL_ADDRESS>(20.9ms)

Do you get any output when running this?
foreman export runit -a huginn -l /home/huginn/huginn/log /etc/service

If that ran successfully check if there is a directory in /etc/service/ for every service you configured in the Procfile and run chown -R huginn:huginn /etc/service/huginn*.
When that worked you should be able to proceed with the installation instructions.

I'm thinking the installation only made it part-way through before hanging. At the Ensure Your Huginn Instance Is Running step:
$ sudo bundle exec rake production:status
rake aborted!
'sv status huginn-jobs-1' exited with a non-zero return value: warning: huginn-jobs-1: unable to open supervise/ok: file does not exist
/home/huginn/huginn/lib/tasks/production.rake:85:in `run'
/home/huginn/huginn/lib/tasks/production.rake:77:in `block (2 levels) in run_sv'
/home/huginn/huginn/lib/tasks/production.rake:93:in `with_retries'
/home/huginn/huginn/lib/tasks/production.rake:76:in `block in run_sv'
/home/huginn/huginn/lib/tasks/production.rake:75:in `each'
/home/huginn/huginn/lib/tasks/production.rake:75:in `run_sv'
/home/huginn/huginn/lib/tasks/production.rake:47:in `block (2 levels) in <top (required)>'
/home/huginn/huginn/vendor/bundle/ruby/2.5.0/gems/rake-12.3.1/exe/rake:27:in `<top (required)>'
Tasks: TOP => production:status
(See full trace by running task with --trace)

Running with --trace just gives a longer stack trace into rake's code.

I over read that you are using Ubuntu 18, installing runit-systemd might fix the issue.

@dsander Looks like you've provided an excellent hint!
$ sudo bundle exec rake production:status
run: huginn-jobs-1: (pid 10676) 58s; run: log: (pid 10675) 58s
run: huginn-web-1: (pid 10678) 58s; run: log: (pid 10677) 58s

Ok, I've got it installed, it's running, and I've got my nginx config going, I've been able to see Huginn's 404 page at least.
Thanks for your help!

Hi,
trying to install this on Gentoo I ran into a very similar looking problem. I don't know how to narrow the problem down further.
The information I have so far:
sudo bundle exec rake production:check warns about
WARNING: Nokogiri was built against LibXML version 2.9.10, but has dynamically loaded 2.9.9, but still produces:
[ OK ] Everything is fine
Running foreman export runit -a huginn -l /home/huginn/huginn/log /etc/service leads to the output underneath.
 We don't support Gentoo in the manual installation guide, it's probably easier to install Huginn using Docker.

/etc/service does exist, /service does not. How can I check the runit installation? And how is it supposed to be configured?
I must admit, I'm not very familiar with Docker. Using Docker would mean to use the web server and database included in the container, rather than my systems install, right?
I'd prefer to be able to update especially nginx and mariaDB independent from some container maintainer...

You can try to create /service and run the export again.

I got it working!
Step 1: take the runit.service file from the .deb file and put it in /etc/systemd/system/ after installing runit --> runit-systemd on Gentoo
Step 2: Create the /service folder as a SYMLINK to to /etc/service
ln -s /etc/service/ /service
(I guess this could be done more elegantly by changing the appropriate part of some config)
(Step 3: create a symlink from the webroot to /home/huginn/huginn/public, but I assume this depends on the webserver config, which I simply copied over from my old machine, so I just put that there again)
Thx for the hint with /etc/service and /service, @dsander!


[Code health] Remove usages of reposition view

Remove usages of LocationOfInterestRepositionView and all related tests. Later, the view would be refactored into a fragment for collecting "Drop a point" type data.

Some usages of the VM are still remaining


fix(jcenter): remove jcenter

Builds will no longer be able to resolve artifacts from JCenter after February 1st, 2022 because jcenter servers shut down
so, i remove jcenter and update react-native (since 0.65.1 they don't use jcenter)

@Titozzz, PR is ready
#2142


Unable to locate credentials. You can configure credentials by running "aws configure".

https://github.com/sampingantech/sampingan-android-docker/runs/7841463894?check_suite_focus=true#step:13:18
references: https://github.com/aws-actions/amazon-ecr-login

mas @serventera kemarin teh ga bisa pake amazon-ecr-login karena apa kah?


JhiResolvePagingParams

add JhiResolvePagingParams and test for that to move all resolver for paging to ng-jhipster

@azizkhani I still haven't found time to take a look at the issue you are facing, I can't promise when I'll find time as i'll be busy with Devoxx FR, vacation etc. But since this is not urgent I guess it can wait

Ok .I starting change generator and waiting for view that  👍

@deepu105 can you help me to resolve this test?

@deepu105 i changed test and pass all test. 👍


isomericSmiles=False

First, thank you for your awesome work!
I'm wondering why you set isomericSmiles=False in file map4.py at Line 15.
From my perspective, the stereochemistry information is quite important in Molecular representation. In repo rdkit, there is an optional argument called useChirality when obtain Morgan Fingerprint.
So, if the code still works if I manually set isomericSmiles to True?
Test Code Below
import tmap as tm
from map4 import MAP4Calculator

MAP4 = MAP4Calculator(is_folded=True)

smiles_a = 'n1nn2N=C(C=C(c2n1)N)C(=O)Nc3c(cc(c(c3)C#C)F)C(=O)O[C@H]4[C@H](O)CSSC4'
mol_a = Chem.MolFromSmiles(smiles_a)
map4_a = MAP4.calculate(mol_a)

smiles_b = 'n1nn2N=C(C=C(c2n1)N)C(=O)Nc3c(cc(c(c3)C#C)F)C(=O)O[C@@H]4[C@H](O)CSSC4'  # '@' -> '@@'
mol_b = Chem.MolFromSmiles(smiles_b)
map4_b = MAP4.calculate(mol_b)

print(sum(map4_a == map4_b), MAP4.dimensions)

# [isomericSmiles=False output]: (1024, 1024)
# [isomericSmiles=True output]: (921, 1024)

Hi,
yes, it is possible to set "usechirality" to True. The code should still work but I haven't tested it.
However, the reason why I did not consider this option is that in this way two shingles representing the same substructure with different chirality would be considered as 100% different, which I am not sure it is necessarily a good idea. Probably implementing a second set of shingles that would account only for chirality (e.g "R|distance in bonds|S") to which one could give a desired weight would be a better option.
If you experiment with MAP4 and chirality keep me updated, I am definitely curios.
cheers,
Alice

Thank you for your reply! Your code still works when I set isomericSmiles to True in my test cases.

However, the reason why I did not consider this option is that in this way two shingles representing the same substructure with different chirality would be considered as 100% different, which I am not sure it is necessarily a good idea.

Indeed, I found this problem during my experiments. I do want to distinguish molecules with different chirality but they got too far in representation (like I mentioned above, 103 dim different with only one chirality different), which is unexpected.

...Probably implementing a second set of shingles that would account only for chirality (e.g "R|distance in bonds|S") to which one could give a desired weight would be a better option.

This is a good idea! I will try it in the future.

If you experiment with MAP4 and chirality keep me updated, I am definitely curios.

Of course! You shall close this issue for now. I may reopen it one day if I get some progress. 🍻


Slim 3: missing referer in Request

I can't access referer in Request object in Slim 3. It seems there is none. Shouldn't be referer set automatically when routing/redirecting?
Update: There is referer but not always. When I use:
return $response->withRedirect('/admin/user/login');

in middlewere, I cannot see any referer in action handling this URI.

How are you reading the referrer?

I tested this and it was present at the time, the only time the referrer was missing was if I went directly to the route itself, but on using the build in redirect it was always present.

Also browser does not always the send referer header.

I tried simple action like this:
public function test(Request $request, Response $response, $args) {
     return $response->withRedirect('/admin/user/login');
}

public function login(Request $request, Response $response, $args) {
    var_dump($request->getHeaders());die();
}

And there is no REFERER header. Can you please confirm you have it there?

How are you testing?

The REFERER header is set by the browser. So, you need to use the browser to redirect from test to login.

i.e.:

$app->get('/one', function ($request, $response, $args) {
     return $response->write('Click here');
});

$app->get('/two', function ($request, $response, $args) {
    var_dump($request->getHeaders());
});

Doing return $response->withRedirect('/two'); instructs the browser to do a redirect. It is not an internal Slim subrequest. Following gives me HTTP_REFERER header at /two.
$app->get("/one", function ($request, $response, $args) {
     return $response->write('Click here');
});

$app->get("/redirect", function ($request, $response, $args) {
    return $response->withRedirect("/two");
});

$app->get("/two", function ($request, $response, $args) {
    print_r($request->getHeader("HTTP_REFERER"));
});

Yields.
Array
(
    [0] => http://<IP_ADDRESS>:8081/one
)

@tuupola, Your example shows what's going on. The act of clicking on "click here" sets the HTTP_REFERER to /one. Then, The redirect in /redirect simply passes that HTTP_REFERER value onto /two.
i.e. using withRedirect doesn't set or change the HTTP_REFERER header.

But withRedirect returns HTTP 302 response with Location in header. Browser then makes new request with that Location. And if it doesn't create Referer, what is the best way to get original location?

I use ?r=xyz in URL that I redirect

That will work. I must Google for some best practice for this. Anyway I think this issue is well answered and should be closed. Thanks for replies.

@akrabat my point exactly. If referer header exists using withRedirect() will not remove it.  So you can use withRedirect() and still have the referer header.
But in any case relying on referer header is bad practice since there any many cases when it might be missing.


Change config regexes to full-string matches.

This anchors all regular expressions entered via the config to match a
full string vs. a substring.
Fixes part of https://github.com/prometheus/prometheus/issues/996

@fabxc let me know if you think the NewRegexp/MustNewRegexp is overkill. I did it that way to share more of the relevant code between UnmarshalYAML and the tests.
/cc @brian-brazil

Can you note in the description that this is a breaking change?

:+1:


listItem Help

Hi
I am really struggling to get this working in Node-Red for a list item.
Do you have an example flow that I could use to understand how to format the listItem selector?
Many thanks

Hi
Do you want to get a specific item or the whole list?
To retrieve a whole list you can use
{     property: {        listItem:'listselector',        data:{...}     }   }
If you only need one element, you can add another node to get the specific element of the vector

Hm, have there been any scrape-it changes recently? My mapping is not working and in debug log I see this.
SyntaxError: Unexpected token a in JSON at position 2

And this is my mapping.
{
   articles: {
       listItem: ".oglas_container"
     , data: {
           id: {
               selector: ".div h2 a::attr(title)"
           }
       }
   }
}

@mfin
It must be a valid json
{
   "articles": {
       "listItem": ".oglas_container"
     , "data": {
           "id": {
               "selector": ".div h2 a::attr(title)"
           }
       }
   }
}


Moving Snapshot Serengeti to Panoptes

We should move SS to PFE before adding any more data to the project. I've recreated SS here:
https://www.zooniverse.org/projects/aliburchard/snapshot-serengeti
@camallen these are the remaining to-dos we've discussed. I'm happy to be in touch when the time actually comes to move things over if there are any issues.
TO DO:

[ ] Change ownership of the project from aliburchard to zooniverse
[ ] Redirect www.snapshotserengeti.org to  https://www.zooniverse.org/projects/zooniverse/snapshot-serengeti
[ ] Redirect www.snapshotserengeti.org/#/authors to https://www.zooniverse.org/projects/zooniverse/snapshot-serengeti/about/results
[ ] Keep Talk so that volunteers can still access their old collections and comments, but discourage (eventually disable?) activity on that forum
[ ] Message the change to moderators and volunteers (I'm alerting the science team to the change, but @mrniaboc will be good if you can coordinate with them to when the time comes). I'm especially keen to alert mods ahead of time to the change and to translations (which will likely be in place before S11 goes up).

Since Serengeti is now on project builder, should we close?


Apply standard and cleanup of Measure-DbaDiskSpaceRequirement

General cleanup of standards.
Addressed variable and properties names to make less generic and a bit clearer in reading output.
Removed use of EnableException parameter on Write-Message and Stop-Function calls.
Added code block for building connections to source and destination, to allow it to also properly test the access to each before trying to run the code.
@FriedrichWeinmann and/or @potatoqualitee  please review...if there is anything that needs to be addressed let me know (or by all means address, the branch is in the dbatools repo).

@potatoqualitee if you get a chance give this one a spin, fixed the output issue as I had to update properties on the call to default view...forgot to update those.
I added DbaSize and think I did this right, the size unit from SMO is in KB so I simply had it product of that value times 1k and that should be the value in Bytes.

sweet will do, thank you shawn. sorry for the delay, the past 3 days have been crazy!

LOVE! such a cool command. thanks for the updates @wsmelton and thanks for the original command @pollusb !!


bug in topo.py Topo.AddLink()

The function AddLink() in topo.py in class Topo is in my version like this:
def addLink( self, node1, node2, port1=None, port2=None,
             key=None, **opts ):
    """node1, node2: nodes to link together
       port1, port2: ports (optional)
       opts: link options (optional)
       returns: link info key"""
    if not opts and self.lopts:
        opts = self.lopts
    port1, port2 = self.addPort( node1, node2, port1, port2 )
    opts = dict( opts )
    opts.update( node1=node1, node2=node2, port1=port1, port2=port2 )
    self.g.add_edge(node1, node2, key, opts )
    return key

The last line should be removed and the line before it should get the return, like this:
..... other code...
opts.update( node1=node1, node2=node2, port1=port1, port2=port2 )
return self.g.add_edge(node1, node2, key, opts )
The key argument in is by default None and Multigraph.add_edge will change the key if it is None to the actual key value and return the actual key. AddLink also have key as None by default and the present code simply returns the input key even if it is None.
Instead it should return the key it gets from add_edge so that it returns the actual key used.

The PR #895 will fix this issue when merged :)

PR is merged, this can be closed @lantz


Repeat Start Stop of WebSocketServer

Specification
For js-ws, the only thing that should be able to be repeatedly started and stopped should be WebSocketServer. No other classes can do this.
In order to do this properly you need to do these in a few places.
For the server stop near the end while awaiting for this._closedP.:
    // Wait for the socket to be closed
    await this._closedP;
    // Resets the `closedP`
    const { p: closedP, resolveP: resolveClosedP } = utils.promise();
    this._closedP = closedP;
    this.resolveClosedP = resolveClosedP;

For the server start right at the end before the this.logger.info:
    this._closed = false;

This should ensure that when stopping, you will reset the closedP promise. And when you start again, you have ensured that this._closed = false.
Right now your comments https://github.com/MatrixAI/js-ws/blob/fe32230e55e2831b12739975fda81faad9b81c3c/src/WebSocketServer.ts#L300C27-L300C27 doesn't quite make sense.
Then make sure you are testing this.
Also this._closedP should be used, because closedP should be exposed as a readonly getter. So that this._closedP is a protected property.
Tasks

Reset the closedP during WebSocketServer.stop().
Make sure that you set this._closed = false when you start it again.
Make sure you have a repeated start/stop.
Make sure the closedP is a readonly getter method.

This should be resolved in the latest commit on staging

if the closedP is reset on stop, won't there be a floating promise? @CMCDragonkai

No, it's a tracked promise because it's a property.

No promises don't keep the process open. They get gced when there's no more reference.

Can you get this quick fixed and closed?

Just push straight to staging, no PR required.

Remember to lintfix!! And regenerate docs.

@amydevs you should have to closed this within the commit.
8514cb110468b1c16d82ab3662acebfb9a77a3f1
Also remember to lintfix, you should use chore: lintfix or just lintfix along with the commit in the future.


Live: Added step property.

Replacing get_step() and set_step().
Closes #172

Codecov Report

:exclamation: No coverage uploaded for pull request base (1.0@f985113). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@          Coverage Diff           @@
##             1.0     #357   +/-   ##
======================================
  Coverage       ?   95.03%
======================================
  Files          ?       36
  Lines          ?     1713
  Branches       ?      147
======================================
  Hits           ?     1628
  Misses         ?       60
  Partials       ?       25

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Changing GUI Slots

Hello!  I am trying to set up my /ce gui to be 1 row of 9 with success dust in the first slot, fixing dust on the 9th, white scroll on the 2nd, and black scroll on the 8th with Tier 1 on the 4th, tier 2 on the 5th, and tier 3 on the 6th.  When I try to do /ce reload it says "An internal error occured while attempting to perform this command."  This is my config.  What is wrong?  http://pastebin.com/AzbpVvYj

Hello the problem is on line number 194. You put Tier1 in a slot that doesn't exist.
Slot: 12 #The Slot number the item will be in


Stream list doesn't update itself after deleting stream

If we try to delete a sole remaining stream, the stream removes itself as expected from the list in
stream settings but the list in left sidebar still shows the stream as listed and gives an error if we click on it:

Full error stack trace given in browser:

@zulipbot claim

Is this issue Closed ?

@zulipbot claim

@zulipbot claim

@zulipbot  abandon

@zulipbot abandon


Can this run on CPU-only computer?

Hi @Prem95
Can this run on CPU-only computer?
If so, how can I modify your code
thanks!

Hi there, the models are trained on a GPU, but I believe TF has functions to force to load the model on a CPU memory instead of a GPU. You can take a look at this StackOverflow


Fix SQLAlchemy update errors

The /points page returns error 500 in the current version due to a semi-recent SQLAlchemy update (https://github.com/pajbot/pajbot/commit/d32c0a81f2b0b3243eae6acc4a88b193e4f93afb or https://github.com/pajbot/pajbot/commit/2d77cba213dd9b1771f01b7c6ccc11fb102eda94)
Pull request checklist:

[x] CHANGELOG.md was updated, if applicable
[x] Documentation in docs/ or install-docs/ was updated, if applicable

I have not added a changelog entry as this issue occurred and was fixed within the same unreleased version.
When this version has been fixed a new release is in order

And I thought because SQLAlchemy updates were only bugfix or minor releases there wouldn't be any breakages to worry about. Thanks for fixing it though!


Eliminate Race Condition in Negative HTTP2 Clients

All four negative http2 clients (python, c++, java, go), have a potential race condition in the GOAWAY test. There is a situation in which the client sends out the second UnaryRequest before the server can send the GOAWAY. This could cause flakiness.
We should have the client wait for verification that a GOAWAY was seen before sending the second request.

cc @ericgribkoff @makdharma

This has not caused any problems in about a year. Closing


feat: selects the sole provider when no key is supplied and there is exactly 1 provider.

Let's close this, we can reopen if necessary.


ORDER BY ignored when query parenthesized

presto> SELECT * FROM (VALUES 11,2,3) t(x) ORDER BY x;
 x
----
  2
  3
 11
(3 rows)

but
presto> (SELECT * FROM (VALUES 11,2,3) t(x) ORDER BY x);
 x
----
 11
  2
  3
(3 rows)

WARNING: ORDER BY in subquery may have no effect

This is expected behavior. A parenthesized query is a <query expression> that contains only a <query primary> of the shape <left paren> <query expression body> ... <right paren>
<query expression> ::=
  [ <with clause> ]
  <query expression body>
  [ <order by clause> ]
  [ <result offset clause> ]
  [ <fetch first clause> ]

<query expression body> ::=
    <query term>
  | <query expression body> UNION [ ALL | DISTINCT ] [ <corresponding spec> ] <query term>
  | <query expression body> EXCEPT [ ALL | DISTINCT ] [ <corresponding spec> ] <query term>

<query term> ::=
    <query primary>
  | <query term> INTERSECT [ ALL | DISTINCT ] [ <corresponding spec> ] <query primary>

<query primary> ::=
    <simple table>
  | <left paren>
       <query expression body>
       [ <order by clause> ]
       [ <result offset clause> ]
       [ <fetch first clause> ]
    <right paren>

Per the spec:
a) If QE does not immediately contain an <order by clause>, then the ordering of rows in T is implementation-dependent.

So, since the <query expression> doesn't immediately contain an ORDER BY clause, the ordering is not guaranteed.


Remove ExactSizeIterator from QueryCominationIter

Objective

QueryCombinationIter can have sizes greater than usize::MAX.
Fixes #5846

Solution

Remove ExactSizeIterator from QueryCombinationIter

Migration Guide

Switch to using other methods of getting the length.

I'd suggest you edit the PR comment to improve the migration guide. Ideally it contains actionable instructions. Here is an example:

Only the implementation of ExactSizeIterator is removed, instead of using query_combination.len(), you can use query_combination.size_hint().0 to get the same value as before

Oh no, more merge conflicts. I'll merge it ASAP once those are resolved.

bors r+


Allow composer to be managed by other tools

We handle composer in other roles and it is installed / updated via
a user with higher privileges than the user the sites managed by. We
don't want the user the project is deployed as to be able to deal with
it. This is a backwards compatible change and seems to work.

Thanks for contributing! :-)


feat: Add property definition utilities to Deno.core

These are common utilities that are duplicated several times in deno and Deploy.

@crowlKats requested it

@crowlKats reminder to update lib.deno_core.d.ts


Not Compatible with Xcode 10.

Hi! I do not have problems with Xcode 10.

@abhishekthanvi8
Hey here https://github.com/SachK13/SKActivityIndicatorView/pull/6 are fixes to support the newest swift 4.2 version.
Maybe it will help.

@abhishekthanvi8 Now supporting to Xcode 10 & Swift 4.2.


[BUGS & SUGGESTIONS]

Bugs :
RCS completely fked up[HIGH PRIORITY]
Knife changer issue flickering [medium]
Spec list/watermark font keeps changing size (flickering) [medium]
Suggestions :
BOX, Name, Health Esp [HIGH PRIORITY]
Nearest hitbox [HIGH PRIORITY]
Nade tracers [mid]
Add more skins(low)

Recoil control works inside an aimbot - it does not control your recoil when target is not found.

Thanks it has been a great learning experience with this as a base. I am finally able to work comfortably with other bases as well.


style(card review modal): reorder stats containers

Small follow-up on #899
I think that we should show the "most useful" counts first. When reviewing, it's best if users see the due & new cards first as this makes it a bit easier to select the deck to review especially for left-to-right languages which are the vast majority of what we support. Or if they have many decks.
@KyleKlus

Yes, that is a very valid argument. I just wanted that the colors are in the order of the hard, good and easy buttons, so it is a bit more uniform.
If I just switched the colors, then the association of the user, which color represents what would maybe confuse some users.
But I am fine with them switching back, if you choose function over form here.


Allow opening the browser even when verbose mode is disabled

// @thgh

@thgh Fixed!

// @thgh

Thanks! Released in<EMAIL_ADDRESS>


Emmet is not working at all. Sublime text 3126, I am using Ubuntu 16.04 64-bit

Hey guys, emmet is not working at all. I installed emmet and Pyv8 manually  and nothing happened.
I downloaded all the file from this link https://github.com/sergeche/emmet-sublime#readme
Please help!

I think I have the same issue (on ElementaryOS 14.04), though I did not install the Pyv8 manually. I re-installed everything through PackageControl. The log that I get is this:
Traceback (most recent call last):
  File "/opt/sublime_text/sublime_plugin.py", line 109, in reload_plugin
    m = importlib.import_module(modulename)
  File "./python3.3/importlib/__init__.py", line 90, in import_module
  File "<frozen importlib._bootstrap>", line 1584, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1565, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1532, in _find_and_load_unlocked
  File "/opt/sublime_text/sublime_plugin.py", line 915, in load_module
    exec(compile(source, source_path, 'exec'), mod.__dict__)
  File "emmet-plugin in /home/user/.config/sublime-text-3/Installed Packages/Emmet.sublime-package", line 24, in <module>
  File "<frozen importlib._bootstrap>", line 1565, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1532, in _find_and_load_unlocked
  File "/home/user/.config/sublime-text-3/Installed Packages/Emmet.sublime-package/emmet/pyv8loader.py", line 20, in <module>
AttributeError: 'module' object has no attribute 'error'

Maybe that can shed some light on what could be the issue. :+1:

The workaround suggested on Sublime Forum works, but needs to be repeated after every restart and Sublime opens with following warning (at least in my case ‒ might depend on installed plugins):
2 missing dependencies were just installed. Sublime Text should be restarted, otherwise one or more of the installed packages may not function properly.
Exception in thread Thread-25:
Traceback (most recent call last):
  File "./python3.3/threading.py", line 901, in _bootstrap_inner
  File "./python3.3/threading.py", line 1142, in run
  File "/home/kout/.config/sublime-text-3/Packages/JSHint Gutter/JSHint.py", line 188, in <lambda>
    self.timer = Timer(timeout, lambda: view.window().run_command("jshint", { "show_panel": False }))
AttributeError: 'NoneType' object has no attribute 'run_command'

Complete log from my Sublime.  It only contains the request method.
For now I've implemented a hacky solution in my system, which will work on the cases that there's no errors while downloading the pyv8 library. I cloned the repository to the  sublime packages folder and made changes in the emmet-sublime/emmet/pyv8loader.py file at line 20 and 21 to:
url_err = ''
url_parse = ''

It works at multiple restarts as well. But we'll have to find a better solution for this problem.

from SubodhDahal #638

Closing as duplicate of #636
Let’s continue discussion there


Add heart drawing on "celebration" button click

Draw heart with particles, something like this but another shape: bevy_hanabi/gradient.gif at main · djeedai/bevy_hanabi

This can be re-opened if someone wants to work on it.


npm error

i have this error while i type "npm start"
npm ERR! code 1
npm ERR! path C:\Users\pc\Desktop\discord COMPUTE MACHIN\discord-bot-for-gcp
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c "node index.js"
npm ERR!      C:\Users\pc\AppData\Local\npm-cache_logs\2021-01-12T12_04_32_958Z-debug.log

Hi, I am currently unavailable. I will get back to you as soon as possible. Sorry for the delay!

Hi, I am currently unavailable. I will get back to you as soon as possible. Sorry for the delay!

i readed README.md and nothing helped : (

i readed README.md and nothing helped : (

Hi there, I just looked into your error.
GCP_config.json file is missing from your directory. You can read the README.md to know how to generate the GCP_config.json file
or
You can visit the link given below and follow the steps there. Do let me know if you face an issue.
Link to generate GCP_config.json: https://cloud.google.com/docs/authentication/production?_ga=2.205580179.1089106346.1589480557-1074299793.1585422711#obtaining_and_providing_service_account_credentials_manually

Hi there, I just looked into your error.
GCP_config.json file is missing from your directory. You can read the README.md to know how to generate the GCP_config.json file
or
You can visit the link given below and follow the steps there. Do let me know if you face an issue.
Link to generate GCP_config.json: https://cloud.google.com/docs/authentication/production?_ga=2.205580179.1089106346.1589480557-1074299793.1585422711#obtaining_and_providing_service_account_credentials_manually

thanks! that fixed everything!

thanks! that fixed everything!

Glad I could help. Good Luck!

Glad I could help. Good Luck!


[FLINK-10050] Support allowedLateness in CoGroupedStreams

What is the purpose of the change
https://issues.apache.org/jira/browse/FLINK-10050
Add 'allowedLateness' method to coGroup and join streams API.
Brief change log

add 'allowedLateness' for CoGroupedStreams/JoinedStreams java and scala API
delegate calls to underlying WindowedStream (as for Trigger/Evictor scenario)

Verifying this change
This change is a trivial rework.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): yes
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no

@aljoscha @tillrohrmann
guys, please can you take a glance on it?

Hi @EugeneYushin . This PR has no tests. Please add them.

Thanks for updating the PR @EugeneYushin . I will have a look today.

@kl0u I didn't want to ping you until Travis is finished.
Thanks for quick turnaround

I see one build from Travis has been finished with error:
10:15:13.087 [ERROR] Failed to execute goal on project flink-storm-examples_2.11: Could not resolve dependencies for project org.apache.flink:flink-storm-examples_2.11:jar:1.7-SNAPSHOT: Could not transfer artifact org.apache.storm:storm-starter:jar:1.0.0 from/to central (http://repo.maven.apache.org/maven2): GET request of: org/apache/storm/storm-starter/1.0.0/storm-starter-1.0.0.jar from central failed: Connection reset -> [Help 1]

Looks like it's not related to proposed changes.
What is the best way to deal with such kind of failures during CI?
Is there any way to rerun PR?

I would recommend to relaunch that specific build and see if it happens again.

Nice, CI checks have been passed. I think I have no access to Travis to relaunch builds (at least, I don't see any button there to perform such kind of operation).
Thanks for cooperation

@kl0u Great news!


Movement function works after respawn

https://github.com/PrismarineJS/mineflayer-pathfinder/issues/212

https://github.com/PrismarineJS/mineflayer/issues/2269 is resolved.


BAQE-1695: Test from VS Code interaction to cloud deployment

for more details see:

https://issues.redhat.com/browse/BAQE-1695

This is still WIP, missing parts are

[ ] to run actual asset manipulation in VS Code
[ ] check more properly DMN service (processes return json, while DMN xml)
[ ] tests more combinations by the data-table

The command for I used for running is stored in jira comment.
Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[ ] You have read the contributors' guide
[ ] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[ ] Pull Request contains a link to the JIRA issue
[ ] Pull Request contains a description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

Command I use locally for running:
rm test/logs/ -rf;  make run-tests operator_image=quay.io/kiegroup/kogito-operator operator_tag=1.5.0 local=true cr_deployment_only=true feature=features/deploy_kogito_build_vs_code.feature runtime_application_image_registry=quay.io maven_mirror=https://bxms-qe.rhev-ci-vms.eng.rdu2.redhat.com:8443/nexus/content/groups/public tags=smoke namespace_name=jomarko-testing runtime_application_image_namespace=jomarko

@radtriste @jstastny-cz changes are in

Looks good to me.
Just a generic note, originally all BDD steps were designed to be in passive tense. Thinking about it, it may shift the intended sentence meaning and be less descriptive. IMHO it would be better to use active tense for steps which perform some action, keeping passive tense for steps which check the status or result, what do you think?

@radtriste  is it still needed?

@jomarko ?

Closing this effort. Similar tests should be probably developed rather in BA Studio testsuite where a deployment a decision on cloud is one of key features.


feat: upgrade to spectral 6 and convert to monorepo

This commit refactors the project into a monorepo and separates the project
into two NPM packages. One is the existing ibm-openapi-validator package and
one is the new package for our custom Spectral ruleset. As part of this change,
we upgraded to Spectral 6 which contained a number of breaking changes.
There are some incompatible changes for this tool (not many) as a result. These
are described in the migration guide. Since a number of these files were being
moved around already, I took the opportunity to rename a bunch of files to match
our kebab-case convention of file naming.

:tada: This PR is included in version 0.1.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.52.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


debugger.md: link to Portable PDB wiki page

This updates the portable PDB documentation in debugger.md to link to the wiki page.

@DanielMeixner please review

Sorry, I can't comment on your file directly.

You're pointing to "additional launch.json options below" but there are no other options in this document.

don't display the full link on the bulletpoint. Instead like this here.
Review finished.

Done


Multiple deprecation removals

It might be easier to review per commit.

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


INBOX: Ability to drag item from INBOX into DRAFT #371

I've done the following changes to this

added drag function and hand icon in Inbox, also passed the data from props to home page
In this I've also added one function regarding removing items from the inbox after being dragged to draft
made the changes to a home component in which the main logic is written.

This PR is for both tasks

INBOX: Once an item has been dragged from INBOX to DRAFT, remove from DRAFT automatically #370
INBOX: Ability to drag item from INBOX into DRAFT #371

This doesn't work for me.
It deletes the lines, but doesn't put them in DRAFT. Please see screen recording
https://user-images.githubusercontent.com/104105362/176830099-29ccb9b0-5015-4c77-9cbd-14efc5fe3340.mov
.


Make sure renderers output is generated

For #12941
This only happens when using dev bits. Root cause was because nothing was building the render output.

Codecov Report

Merging #13879 into main will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #13879      +/-   ##
==========================================
- Coverage   60.06%   60.03%   -0.03%
==========================================
  Files         687      687
  Lines       38100    38100
  Branches     5488     5488
==========================================
- Hits        22883    22874       -9
- Misses      14037    14043       +6
- Partials     1180     1183       +3

Impacted Files
Coverage Δ

src/client/datascience/crossProcessLock.ts
79.41% <0.00%> (-11.77%)
:arrow_down:

src/client/common/utils/platform.ts
60.00% <0.00%> (-8.00%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
: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 5a0ef97...80e1bbe. Read the comment docs.


Directory's name containing spaces

Is it possible to backup a directory that contain a space in its name?
I tried escaping it like directory\ name but acts didn't like it.
acts-1.0
tarsnap 1.0.35
cygwin

Sorry, unfortunately there's no easy solution, due to the simple
(primitive) way acts reads its configuration file.
I don't think directories with spaces is a common use case either, so
complicating the code to support it is off the table until more of the user
base ask for it.
As a workaround, I'd suggest creating a symlink without spaces to the
directory you want to back up. This will complicate your restores somewhat,
of course.
On 4 May 2015 2:44 am, "Bruno Bigras"<EMAIL_ADDRESS>wrote:

Is it possible to backup a directory that contain a space in its name?
I tried escaping it like directory\ name but acts didn't like it.
acts-1.0
tarsnap 1.0.35
cygwin
—
Reply to this email directly or view it on GitHub
https://github.com/alexjurkiewicz/acts/issues/6.

As a workaround, I'd suggest creating a symlink without spaces to the
directory you want to back up.

It seems tarsnap doesn't follow symlink by default and I can't use tarsnap="tarsnap -L
$ ./acts
tarsnap: Option -L is not permitted in mode --list-archives
Couldn't get list of existing archives, exiting.
Hint: is Tarsnap configured correctly?
Exiting unexpectedly.

I didn't see an option in https://www.tarsnap.com/man-tarsnap.conf.5.html.

Try adding -L to tarsnapbackupoptions in acts.conf.
On 4 May 2015 at 11:18, Bruno Bigras<EMAIL_ADDRESS>wrote:

As a workaround, I'd suggest creating a symlink without spaces to the
directory you want to back up.
It seems tarsnap doesn't follow symlink by default and I can't use tarsnap="tarsnap
-L
$ ./acts
tarsnap: Option -L is not permitted in mode --list-archives
Couldn't get list of existing archives, exiting.
Hint: is Tarsnap configured correctly?
Exiting unexpectedly.
I didn't see an option in https://www.tarsnap.com/man-tarsnap.conf.5.html.
—
Reply to this email directly or view it on GitHub
https://github.com/alexjurkiewicz/acts/issues/6#issuecomment-98563667.

It worked. Thanks!

The primary directory I'm tarsnapping has a space in it (which bugs me, but I can't change it).  So, I would prefer to have this work without a workaround, in some future version of acts.

I'd like to see this handled as well, because not backing up some valid data seems against the whole point of a backup tool, and creates fear and uncertainty (Do I have files/directories with spaces in their name ? What other names will acts not back up ? Will they be silently ignored, loudly reported, cause backups to fail ? Am I sure I'll remember how to handle this safely over the long term ?)

Tarsnap handles spaces perfectly. Things with spaces get backed up just fine. The only thing that acts doesn’t support is specifying an archive root that has spaces in it.
backuptargets=“var/data/db name with spaces” would fail. But backuptargets=“var/data” would back up /var/data/db name with spaces with no issue.
You could:

Use symlinks
Make the backup target the directory containing the one with spaces.

Ah, I misunderstood.  That’s less of an issue, thanks.

(That could be made clearer in the issue name.)


feat(config): allow opting out of envPrefix security

Previous discussions:

https://github.com/vitejs/vite/pull/12347
https://github.com/vitejs/vite/pull/9880

So, I know this has already been discussed, but I'd like to re-open the conversation about it. This pull request adds the ability to opt-out of envPrefix security by setting that option to false.
In many situations, we have to duplicate environment variables (eg. VITE_APP_ENV="$APP_ENV") or write custom define logic to allow non-prefixed variables to be used in client code.
I have been adding the actual variable names to envPrefix myself as a convenience, but this is kind of hijacking the feature to make it act as an allowlist:
export default defineConfig({
	// ...
	envPrefix: [
		'APP_ENV',
		'MAPBOX_TOKEN',
		'PUSHER_APP_KEY',
		'PUSHER_APP_CLUSTER',
		'CJ_ONESIGNAL_APP_ID',
		'JF_ONESIGNAL_APP_ID',
		'STRIPE_PUBLISHABLE_KEY',
		'CLOUDFLARE_TURNSTILE_SITE_KEY',
		'CLOUDFLARE_TURNSTILE_SECRET_KEY',
		'FLARE_KEY',
	]
})

This is quite common in Laravel-land (we have a lot of configuration defined in .env files), and a papercut I'd like to remove.
The main reason I think it is perfectly fine to allow this option is that there is actually no risk of exposing unwanted values in client bundles unless the developer specificially writes import.meta.env.VARIABLE_NAME, which can't be done by mistake.

Marking this as draft, because after testing, apparently all environment variables are written in the client bundle, even without import.meta.env.* call.
I'll look if we can do something about it, otherwise I'll close the pull request.

Yeah, I'm not sure there's a way around that. As far as I understand it, any third party can reference import.meta.env and it could be bundled.


Require at least 1 endpoint to listen on. (#3637)

Support multiple listen addresses and fix to listen to both ::1 and 1… (#3631) (#3634)

Require at least 1 endpoint to listen on.

Description
Cherry pick into master.
Issue reference

Please reference the issue this PR will close: #2914
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-perf


Add bump config to track debian:buster-slim version

Just have to remember to add a BUMP_TOKEN secret before merge

I usually prefer to use a specific version tags as possible to keep things as reproducible as possible that is the reason i built bump. One bad thing about doing this is that if someone forks or copies the Dockerfile they will be on the same version until manual change.


🌱 Parameterize api folder path in Makefile

What this PR does / why we need it:
Parameterizes api folder path in the Makefile targets.
We can use just run: make modules instead of running go mod tidy in every folder where go.mod file is updated.

/test-v1b1-ubuntu-integration

/retest all


Provide amd id for umd build

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[x] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
We are running a dev-setup where all our code is converted to amd module and then concatenated to one file. This is the approach that Bazel takes for js dev. For more details see: https://github.com/alexeagle/angular-bazel-example/wiki/Running-a-devserver-under-Bazel When depending on the vue build the problem is it does not have an id so when the umd file is being loaded requirejs complains about an anonymous module. Just by providing the id this is fixed and we can depend on vue from our application.

Angular for example provides amd ids and it seems to work fine there. I see that in theory it makes it less portable, but how else would one want to call vue? I would be surprised if anyone would not have import Vue from 'vue' or the equivalent depending on their module format. But if there is sentiment against it that is also fair enough and this can be closed.


initial changes for alert messages

I removed the validation stuff from this. This should just be the alert message. Accept or change as you see fit. Fixes #32.

Looks good. Thanks!


Potential license

Hello! Would it be possible to have a license here, please? I'm assuming, as it's been posted here publicly and a couple of us are keen to use for a non-business purpose, that there's no issue, but wanted to double-check. It's helpful as a nice clean template, so thank you!

Thanks!


Mark resources that exist in current cluster

When loading / previewing resources it would be nice to easily identify which already exist in my configured cluster - some kind of visual marker!?
Perhaps red = doesn't exist, orange = exists but different, green = exists

@olensmar should we close this now that we have the Cluster Compare feature?

Closing this as it looks like finished

thanks - the Cluster Compare does the trick so we can close it