Have installed tensorflow but still unbale to access it in Jupyter Error: ModuleNotFoundError: No module named 'tensorflow'

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

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
TensorFlow version:
Python version:
Installed using virtualenv? pip? conda?:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

Describe the problem
Provide the exact sequence of commands / steps that you executed before running into the problem
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

@qaiserizvi
Please install tensorflow in jupyter notebook using !pip install tensorflow and then you import tensorflow. If you have created virtual environment then please make sure you have installed  tensorflow in that environment.Please, find the gist here. Thanks!

Still getting these errors, after running pip install tensorflow==2.3.0
ImportError                               Traceback (most recent call last)
~\anaconda3\lib\site-packages\tensorflow\python\pywrap_tensorflow.py in
63   try:
---> 64     from tensorflow.python._pywrap_tensorflow_internal import *
65   # This try catch logic is because there is no bazel equivalent for py_extension.
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: The specified module could not be found.
During handling of the above exception, another exception occurred:
ImportError                               Traceback (most recent call last)
 in
----> 1 import tensorflow as tf
~\anaconda3\lib\site-packages\tensorflow_init_.py in
39 import sys as _sys
40
---> 41 from tensorflow.python.tools import module_util as _module_util
42 from tensorflow.python.util.lazy_loader import LazyLoader as _LazyLoader
43
~\anaconda3\lib\site-packages\tensorflow\python_init_.py in
38 # pylint: disable=wildcard-import,g-bad-import-order,g-import-not-at-top
39
---> 40 from tensorflow.python.eager import context
41
42 # pylint: enable=wildcard-import
~\anaconda3\lib\site-packages\tensorflow\python\eager\context.py in
33 from tensorflow.core.protobuf import config_pb2
34 from tensorflow.core.protobuf import rewriter_config_pb2
---> 35 from tensorflow.python import pywrap_tfe
36 from tensorflow.python import tf2
37 from tensorflow.python.client import pywrap_tf_session
~\anaconda3\lib\site-packages\tensorflow\python\pywrap_tfe.py in
26
27 # pylint: disable=invalid-import-order,g-bad-import-order, wildcard-import, unused-import
---> 28 from tensorflow.python import pywrap_tensorflow
29 from tensorflow.python._pywrap_tfe import *
~\anaconda3\lib\site-packages\tensorflow\python\pywrap_tensorflow.py in
81 for some common reasons and solutions.  Include the entire stack trace
82 above this error message when asking for help.""" % traceback.format_exc()
---> 83   raise ImportError(msg)
84
85 # pylint: enable=wildcard-import,g-import-not-at-top,unused-import,line-too-long
ImportError: Traceback (most recent call last):
File "C:\Users\DELL\anaconda3\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 64, in
from tensorflow.python._pywrap_tensorflow_internal import *
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: The specified module could not be found.
Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/errors
for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.

@qaiserizvi
What is make/model of your cpu?
I suspect your cpu model does not support AVX instructions sets.See hardware requirements
Make sure to download the latest microsoft visual c++ redistributable from here.
.Also, please follow the instructions from to install from Tensorflow website.
Please, check Your CPU/Python is on 32 bits?
Please, refer duplicate issue #39007
Thanks!


Added mpheist4 vehicles & Alphabetical order

Updated. I only only added the cars of mpheist4 update.

Updated. I only only added the cars of mpheist4 update.

Thanks 👍

Thanks 👍


Delete FAQ.md

As part of revamping docs.
Currently useless. All the information on it is already covered in other places.

Another minor point to add about the revamp: https://github.com/caskroom/homebrew-cask/blob/master/developer/bin/update_issue_template_urls should be updated accordingly

Fixing that now.


encoder api: function headers for extra channels

Header only change, implementation to follow.
Pair with Lode.

This is a proposal for the new encoder API function. Comments/suggestions welcome.

Somewhere we need to explain better how passing the alpha channel in JxlEncoderAddImageFrame works. Is that alpha channel counted in num_extra_channels? (so far it wasn't).

Good point! If it wasn't counted so far, perhaps it is best to keep it that way.


Experimental telemetry

Reference:  https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/telemetry-stability.md
Currently the instrumentation libraries are versioned as "stable".
However, the most (all?) semantic conventions which are used are "experimental":

https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/database-metrics.md
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/semantic_conventions/process.md
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md

For instrumentation library modules, I propose to add a "status label" (in docs) to mark that the instrumentation libraries are experiential. The other way would be to retract all released versions and start releasing 0.x.y, however I do not know how dependabot will handle it.
I am not sure what do with Go runtime metrics, which we wanted to enable if OTLP_METRICS_EXPORTER=otlp is set (since v1.4.0).
A similar problem is with process resource detector which is marked as stable, but uses experimental semantic conventions. These resource attributes are ALWAYS added (since v1.4.0). I have not noticed that the semantic conventions are not stable as the Go module was stable. I created an issue in upstream.

We decided just to add notice in the docs in packages where the produced telemetry is not stable.


Updated workspaces-styles.css

Description of changes:
Removed a redundant '}' on line 123
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Cool, thanks!


Fix InstantiationException

java.lang.Class<com.example.android.roomwordssample.WordViewModel> has no zero argument constructor

Thanks for creating this.
Another PR was merged that should have fixed the initialisation issue


linkTextVariations should kick in only if no direct match is found

Proposed patch for ReferenceManager.
I didn't test if that works, but I remember you have a test suite, so that should do the trick :D

Nah, correct fix was in the core search algorithm - it shouldn't even try to find variations if an exact match hit. Fixed now.

LGTM. Thanks.

I think this commit caused a ton of breakage all over.

E.g., try building DOM.

@FremyCompany So my patch for this was wrong - it meant that if something was squatting on your exact term but wasn't good enough to link by default, and a variation would have grabbed the right term, you'd get a link failure.
I'll have to rewrite this to be closer to your originally suggested "just do it twice" code, so I can go through the entire matching rigmarole with the exact term first, and then fail over to using variations if that failed.  For now, I've reverted it because it was breaking several other specs.


Add a bulk-export subcommand that just exports

Right now there's no way to just do a bulk-export and not do the ETL part.
That seems needlessly awkward. It would make sense to add a new subcommand like bulk-export or export that does an export.
All the code is already written for it internally, just needs some CLI & doc love.

Fixed by #332!


Utilize new AWS Price List API for live pricing data

AWS recently released a price list API obsoleting the need to scrape AWS pricing pages for data:
https://aws.amazon.com/blogs/aws/new-aws-price-list-api/

Example us-east-1 endpoint and EC2 pricing data URL:
https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonEC2/current/index.json

This is great to see! Hopefully they'll continue to expose other data via API as well.
I don't have time to incorporate this info right now but if someone wants to start work on it just drop a note here so others are aware.

You could probably just use a Lambda to poll the pricing API once a day and cache the result. It looks the the `rds.oy

The data they provide is unfortunately denormalized, there is a lot of redundancy in there. The price data needs 102MB in their format, while in ours it's about 1.7MB.
I wish they would have used a similar format with what we have on instances.json, which would be much more efficient.

@powdahound hi Garret. myself and @sergiPopescou are looking at picking up this ticket and would like to consider submitting it to ec2instances.info. It sounds like a relatively big change for the repo - can we get some input from you before we start.
background
Currently, AWS metadata collector collects data using ec2instance.info or something similar. This internally calls a URL with JS, then parses this JS, stripping out comments etc.
This file is not guaranteed for accuracy and validity:
{code}
/*

This file is intended for use only on aws.amazon.com. We do not guarantee its availability or accuracy.>

Copyright 2017 Amazon.com, Inc. or its affiliates. All rights reserved.
*/
{code}

We need to extract data from the right source. This was raised previously with github project that parses the data, but they will not fix it, so it seems. Instead the data needs to be pulled out from their pricing API:
https://aws.amazon.com/blogs/aws/new-aws-price-list-api/
Metadata collector should use details described in the above post to populate On-Demand prices.

It sounds like you are referencing another project ("AWS metadata collector") but haven't linked to it. Or have I misread your comment?

@powdahound Apologies - you are right.  I have updated the above to make it clearer.

I'm afraid I still don't understand the "background" section referencing the disclaimer.
I'm in agreement that it'd be nice to pull from that source, though the file size is still concerning.


fix!: correctly detect if file is outside base path on Windows

Prerequisites checklist

[X] I have read the contributing guidelines.

What is the purpose of this pull request?
Fix logic that detects when a file is outside the base path so it works well with Windows-style paths. Also fixed an edge case with paths that start with ".." but are not external like "..file.js".
What changes did you make? (Give an overview)
Windows paths have some unique features not shared by Unix paths. For one, absolute local paths start with a drive letter followed by a colon like "C:". The fact that the drive letter must be the first character in a local path means that a relative path cannot specify a drive. In Node.js, path.relative() will just return the absolute path of the second argument when it cannot calculate a relative path across different drives, so for example with path.relative("C:\\dir", "D:\\file.js").
Besides local paths, Windows uses UNC paths in the form \\Server\Volume\dir1\dir2\file to specify files on a network. Those paths are always absolute.
Both config-array and ESLint use relative paths to check if a file is inside a base directory: if the file's relative path from the directory starts with "..", then the file is not in the directory. This check is currently failing when the base directory and the file were located on different drives or servers, because as previously mentioned path.relative() doesn't handle those cases.
The fix I've come up with consists in calculating what Node.js calls namespace-prefixed paths of the base directory and the file and calling path.relative() on those two. Namespaced paths are prefixed with \\?\ for local paths or with \\?\UNC for network paths. When the provided arguments are namespaced paths on different drives, path.relative() will return a path in the form ..\..\C:\dir1\dir2\file.js. While such a path is not valid as it contains a drive letter in middle position, it can be readily recognized as for being outside the base path because of the leading .. and discarded as external.
Related Issues

refs https://github.com/eslint/eslint/issues/18575
Is there anything you'd like reviewers to focus on?
Instead of using toNamespacedPath, we could manually parse the absolute path, normalize the drive letter or server specification and compare the path components to the corresponding values of the base path. This would make the check more explicit and possibly easier to maintain. The downside is that we would end up reinventing (part of) the wheel.

We may want to consider using the Deno standard path library, which is not runtime or OS specific:
https://jsr.io/@std/path

We may want to consider using the Deno standard path library, which is not runtime or OS specific: https://jsr.io/@std/path

It looks like that library contains different implementations for windows and posix, and by default, it selects the implementation for the current platform. That is similar to how Node.js node:path works.
It would be useful to find a library that can be installed via npm so we don't need to copy the source files manually.

npx jsr add @std/path works. :smile:

Finally made it work as expected using only the Deno standard library for path handling and without considering the current directory. This fixes the way external files are matched on Windows by including drive letters or UNC server names when resolving relative paths.
An important note: external files are files located outside the base path, but the base path is an optional parameter. If no base path is specified, files will never be considered external. This changes the current behavior where the base path defaults to be the current directory if not specified (in ESLint, the base path is always specified).

I'd say let's just use the URL for now. We can always update the approach if/when they respond to your question.

The build is now failing because the generated CommonJS module is trying to require() @jsr/std__path, which is an ESM-only package. In packages/config-array/dist/cjs/index.cjs I can see:
var posixPath = require('@jsr/std__path/posix');
var windowsPath = require('@jsr/std__path/windows');

I'm not sure why there was no build error in my previous commit. The error doesn't seem connected to the way @jsr/std__path is declared in package.json. Maybe we need to bundle @jsr/std__path in the CommonJS module so it gets transpiled.

Maybe we need to bundle @jsr/std__path in the CommonJS module so it gets transpiled.

If we're going to bundle @jsr/std__path in CJS, then we could bundle it in ESM as well, to avoid having a URL depedency (which I think is not a common practice for packages published to npm).

Maybe we need to bundle @jsr/std__path in the CommonJS module so it gets transpiled.

If we're going to bundle @jsr/std__path in CJS, then we could bundle it in ESM as well, to avoid having a URL depedency (which I think is not a common practice for packages published to npm).

Thanks! I tried to bundle @jsr/std__path in dist/cjs/index.cjs and dist/esm/index.js, but then tsc started to complain because of the checkJs option in tsconfig.json:
dist/esm/index.js:316:46 - error TS1313: The body of an 'if' statement cannot be the empty statement.

316       if (lastSlash === i - 1 || dots === 1) ; else if (lastSlash !== i - 1 && dots === 2) {
                                                 ~

dist/esm/index.js:516:15 - error TS2339: Property 'Deno' does not exist on type 'typeof globalThis'.

516       const { Deno } = globalThis;
                  ~~~~

dist/esm/index.js:1148:5 - error TS2353: Object literal may only specify known properties, and 'extended' does not exist in type '{ globstar?: boolean; }'.

1148     extended,
         ~~~~~~~~

dist/esm/index.js:1590:46 - error TS1313: The body of an 'if' statement cannot be the empty statement.

1590       if (lastSlash === i - 1 || dots === 1) ; else if (lastSlash !== i - 1 && dots === 2) {
                                                  ~

dist/esm/index.js:1970:13 - error TS2339: Property 'Deno' does not exist on type 'typeof globalThis'.

1970     const { Deno } = globalThis;
                 ~~~~

dist/esm/index.js:2742:5 - error TS2353: Object literal may only specify known properties, and 'extended' does not exist in type '{ globstar?: boolean; }'.

2742     extended,
         ~~~~~~~~

Found 6 errors in the same file, starting at: dist/esm/index.js:316

So I decided to bundle @jsr/std__path/posix and @jsr/std__path/windows in separate modules that tsc would not check. This seems to be working well and results in the following files being generated:
dist/esm/types.d.ts
dist/esm/index.js
dist/esm/types.ts
dist/esm/std__path/posix.js
dist/esm/std__path/windows.js
dist/esm/index.d.ts
dist/cjs/index.d.cts
dist/cjs/types.ts
dist/cjs/index.cjs
dist/cjs/std__path/posix.cjs
dist/cjs/std__path/windows.cjs

I will update this PR shortly with the new solution, and hopefully the CI build will pass this time.

Checks are all green now, but I found another issue. In ESLint, when a Linter method like verify() or verifyAndFix() is called without a filename parameter, configArray.getConfig() gets called with argument "__placeholder__" instead of a full path. And if filename is a relative path, the relative path will be passed unchanged. Here is the relevant code (https://github.com/eslint/eslint/blob/343f99216096f1db955766870e35d92d5a121448/lib/linter/linter.js#L2010-L2014):
        const filename = options.filename || "__placeholder__.js";

        // Store the config array in order to get plugin envs and rules later.
        internalSlotsMap.get(this).lastConfigArray = configArray;
        const config = configArray.getConfig(filename);

Relative paths will no longer work when this PR is merged, and I don't think everybody is using the Linter with full paths, because that isn't currently necessary. So we should discuss how to update the Linter code as well when we upgrade config-array in ESLint.

To make sure I'm understanding correctly: relative paths will no longer work when passed to Linter because they would previously be resolved relative to process.cwd()?

To make sure I'm understanding correctly: relative paths will no longer work when passed to Linter because they would previously be resolved relative to process.cwd()?

Correct. path.relative() uses the current directory to resolve relative paths. We are using that logic in multiple places in packages/config-array/src/config-array.js.

And again, just for clarity, the path.relative() we're using in this PR does not use process.cwd()?

For a better error message, and also to stay safe in case the Deno global is defined for some reason, we could validate path arguments preemptively in config-array to make sure that they are absolute paths.

That seems like a good idea...although how would we end up passing an absolute path when ESLint#lintText() is called and we use a placeholder? Maybe the placeholder should be /__placeholder__.js instead?

I've added logic to throw an error when a path is not absolute in a783ba1d19664f18c545bf86c2395f637c73ba98.

how would we end up passing an absolute path when ESLint#lintText() is called and we use a placeholder? Maybe the placeholder should be /__placeholder__.js instead?

In order to keep the current behavior unchanged we could resolve the filename passed to getConfig() using path.resolve():
- const config = configArray.getConfig(filename);
+ const config = configArray.getConfig(path.resolve(filename));

Also, we should manually resolve the cwd option used to create a Linter, because cwd is used as a basePath for a ConfigArray, and we don't want to throw an error when a relative path is passed:
function normalizeCwd(cwd) {
    if (cwd) {
-       return cwd;
+       return path.resolve(cwd);
    }
    if (typeof process === "object") {
        return process.cwd();
    }

I tried it and with those two changes, all Linter tests were passing. I also had to update RuleTester to make sure that linter.verify() was being called with a full path, and fixed a couple of expected paths in the unit tests. And at that point, all tests passed, so I'm confident that this solution will work.
We could also change the way the Linter works so it doesn't depend on process.cwd() to resolve relative paths, or we could just ban relative paths in the cwd option so that process.cwd() is not used. Both would be breaking changes I think, but maybe that is where we want to go in ESLint v10?

Which file is that first code snippet from?
I don't think we want to create a dependency on path inside of Linter, as that's a Node-specific API.
Do we ever pass a relative cwd anywhere right now?

Which file is that first code snippet from?

Both snippets are from linter.js in ESLint:

https://github.com/eslint/eslint/blob/v9.10.0/lib/linter/linter.js#L2014
https://github.com/eslint/eslint/blob/v9.10.0/lib/linter/linter.js#L1200-L1206

I don't think we want to create a dependency on path inside of Linter, as that's a Node-specific API.

Actually Linter already has a dependency on node:path. For path.resolve() we could also use an external library like Deno's @std/path, or rewrite the logic manually.

Do we ever pass a relative cwd anywhere right now?

On closer look there are only three unit tests where the cwd Linter option is a relative path (the string "cwd"), so I think we could just fix those tests to use an absolute path like "/cwd" instead:

https://github.com/eslint/eslint/blob/v9.10.0/tests/lib/linter/linter.js#L3869-L3886
https://github.com/eslint/eslint/blob/v9.10.0/tests/lib/linter/linter.js#L9766-L9786
https://github.com/eslint/eslint/blob/v9.10.0/tests/lib/linter/linter.js#L9849-L9869

We still need a mechanism to resolve relative file paths in Linter for when config-array will only accept absolute paths.

Actually Linter already has a dependency on node:path. For path.resolve() we could also use an external library like Deno's @std/path, or rewrite the logic manually.

Ah good point. However, the current usage is limited to chopping up filenames rather than resolving. I don't think we can do @std/path, because we'd end up needing to bundle like we do here? And that would mean two bundles of @std/path in the final eslint package.

We still need a mechanism to resolve relative file paths in Linter for when config-array will only accept absolute paths.

I'm wondering, could we allow relative paths and just path.resolve() it relative to cwd? Maybe that would make the problem a bit easier?

However, the current usage is limited to chopping up filenames rather than resolving. I don't think we can do @std/path, because we'd end up needing to bundle like we do here? And that would mean two bundles of @std/path in the final eslint package.

Yes, in order to use @std/path in ESLint we would have to add an additional compilation step, so it's better to choose an approach that doesn't need changing the build process.

I'm wondering, could we allow relative paths and just path.resolve() it relative to cwd? Maybe that would make the problem a bit easier?

You mean resolveing relative paths in config-array rather that in Linter? That should work, as long as a cwd/basePath is specified (Currently, basePath can be omitted in the ConfigArray options and it will implicitly default to process.cwd()). I can update the PR and test the changes in ESLint.

You mean resolveing relative paths in config-array rather than in Linter? That should work, as long as a cwd/basePath is specified.

Yes, exactly. And sorry, I meant if config array receives a relative path, it should resolve it against the config array's basePath (not cwd).

(Currently, basePath can be omitted in the ConfigArray options and it will implicitly default to process.cwd()).

Is that true even after we switched to @std/path?

I meant if config array receives a relative path, it should resolve it against the config array's basePath (not cwd).

Okay, I tried this solution and it seems to work well. In ESLint, only a small change in the RuleTester class is required, apart from some tweaks to the unit tests.
Here is what I did:

In commit 2b97a8162d329700f91e276285f2f98b6b5ff3fa, I added logic to resolve relative paths from the specified basePath. If a basePath is specified, it must be an absolute path. If basePath is not specified, then all other paths passed to ConfigArray methods must be absolute paths.
In commit d9b14789f87f1780bb7d57484d834d5f99f5d6da, I updated the test logic to use relative paths when possible. In the unit tests it is no longer necessary to call path.resolve(basePath, ...) or path.join(basePath, ...) to create absolute paths when basePath is set.
I prepared a branch in ESLint with the changes necessary to upgrade config-array with this PR: https://github.com/eslint/eslint/compare/update-for-rewrite-pr-59. Verified that all tests will pass both with the current version of config-array and with the new changes, too.

(Currently, basePath can be omitted in the ConfigArray options and it will implicitly default to process.cwd()).

Is that true even after we switched to @std/path?

No. With the changes in this PR, when basePath is omitted other paths must be absolute paths, or otherwise an error will be thrown.

If basePath is not specified, then all other paths passed to ConfigArray methods must be absolute paths.

Is that necessary? It seems like this should work without a basePath. Maybe we could default basePath to / to allow relative paths to still be passed to the various functions?

Is that necessary? It seems like this should work without a basePath. Maybe we could default basePath to / to allow relative paths to still be passed to the various functions?

It should be fine to use to / as a default basePath in a ConfigArray. Note that this assumes we will be working with Unix-style paths when basePath is not specified. I was trying to avoid making that assumption, but after checking the ESLint code, I think this change should be fine, because Linter always sets the basePath explicitly inside Node.js.
Shall I update the PR to make/ the default basePath ?

Shall I update the PR to make/ the default basePath ?

I think so. @mdjermanovic what do you think?

Shall I update the PR to make/ the default basePath ?

Makes sense to me 👍

Thanks for the feedback. I've made basePath default to "/" in commit 193ece2730eda650859b72274c305a23a613ccef and cleaned up the code used to support a missing base path. Only test changes are required in ESLint in order to use the updated config-array: https://github.com/eslint/eslint/compare/update-for-rewrite-pr-59.

LGTM. Would like @mdjermanovic to verify before merging.

https://github.com/eslint/rewrite/pull/59#discussion_r1806708934 still needs to be addressed by disallowing empty string?

#59 (comment) still needs to be addressed by disallowing empty string?

I pushed a commit to disallow empty strings: 4ed3c1c3f6b3665a552aa0f6d762f8daa8bbfd36. Also updated the readme file to reflect the changes: 8c30779592c6402313531e17cfb78a8474e4aea6.


base64 with normal padding: input=>encode=>decode=>output (!=input)

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
[jkayser@oel7latest ~]$ go version
go version go1.10.2 linux/amd64
[jkayser@oel7latest ~]$
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
[jkayser@oel7latest ~]$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/jkayser/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/jkayser"
GORACE=""
GOROOT="/usr/local/go1.10.2"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go1.10.2/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build522215723=/tmp/go-build -gno-record-gcc-switches"
[jkayser@oel7latest ~]$
What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
https://play.golang.org/p/-CtQL8ilWPK
What did you expect to see?
The input and output being identical.
What did you see instead?
input:   6162
output:  5957493d
decoded: 616200
input != decoded

If you actually checked the number of bytes written during decode and resize it, you will end up with the same value as input.

https://play.golang.org/p/OKp3jWYwTb7

Closing as @fraenkel and @opennota seem to have provided an answer to your issue. Please let me know if I should re-open.


"evaluation_scripts_squad_v2" was not found

Hello,
Thank you very much for this implementation.
The path for package "imprt  evaluation_scripts_squad_v2  as ev" in the ./evaluate.py file was not found.
Best,
Xiny

Hello, Thank you very much for this implementation. The path for package "imprt evaluation_scripts_squad_v2 as ev" in the ./evaluate.py file was not found. Best, Xiny

could you tell me how you solve the problem?


[service-bus] Error handling needs work to be consistent and reliable

As part of a recent refactor it's become more obvious that the error handling in Service Bus needs to be made more consistent. There are some good classification functions in the older code (which needs to be brought forward) and basically we just need to have enough information to say:

This link is dead and needs to restart
There is a retryable issue here (transient) and we should just try it again

This affects the Receiver and Sender a bit more since the Processor doesn't really make any distinctions about what's retryable vs not.
Tagging @jhendrixMSFT on this as we've had discussion about how we might provide some interfaces or similar to make the classification easier for client code.

I'm taking a first stab at this for beta 1 (October release).
The big things:

The processor type brings in built-in infinite retrying, which should be more durable than the previous APIs.
Our error classification has been improved - much thanks to the go-shuttle project (and @serbrech). I've added in some further checking and also allow for link and connection level recovery (we fallback to connection more than I'd like, but it's a first go).

As a first beta release bar I've got a stress test running, with network outages every minute for 5 seconds. This gives us some decent recovery testing, while also getting a good ballpark on our longevity.

Some of this work has been incorporated by not requiring the user to intervene. We still report the error but the next call to Receiver.ReceiveMessages() will repair it.
We still want to add in some classification, as that will help customers if they want to decide to make that next call or not,.

Note, another interesting discussion was here:
https://github.com/Azure/azure-service-bus-go/issues/96
When applicable, we should return a structured error. The equivalent of a 404 here would be useful.

My team is working on a servicebus integration, and running into a problem differentiating recoverable and unrecoverable errors.
Specifically we're writing a function to ensure a topic is defined, calling GetTopic to see if it exists, and a CreateTopic if needed. We're not seeing an official way to differentiate between recoverable "topic not found" errors and unrecoverable network errors.
resp, err := client.GetTopic(ctx, "topic", &admin.GetTopicOptions{})
if err != nil {
  // err could be an unrecoverable auth/network/etc problem
  // or a recoverable 404 because the topic is not defined
}

There's an internal atom.NotFound(err) helper to differentiate these error cases, but that's not exported. Currently we're using string comparisons on err.Error(), but that feels brittle; the specific error messages are not part of the exported API and we'd like to only rely on documented behavior. We have a similar situation with GetSubscription/CreateSubscription.
It'd be great if y'all could export something like feedEmptyError, NotFound(err), or any other mechanism to enable this logic.

@ryepup, I'll need to look at it a bit more. The admin client could use some more work to get it consistent with how the rest of the Azure SDK's http based clients work, which should involve exporting a standard error type to look at the HTTP resp and status code, directly.

@richardpark-msft  including a status code would be great

Thanks for the fixes, definitely will solve my problem!
Any idea when the changes from #16831 will get a release?


CP-19508: refactor workflows to solve permissions issues with forks

Background
There are two parts to the changes in the PR.
1. Permissions Issue

2. Testing before publish
Previously, the workflow would publish to GHCR before testing the chart. That opens a window to trash the develop or release x.x.x image. The workflow has been adjusted to use a local registry along side the KinD cluster and host to allow us to build the image and push to that local registry.
If the build and chart test pass, the image is published to GHCR only if it is a release or a develop branch. This ensures we are not publishing bad images which do not pass the deployment validation.

Description

Remove old workflows
refactor workflow to separate chart linting into unique workflow
refactor workflow to use local registry for chart installation testing before publishing
refactor publishing to only work on develop branch or tag branch

Testing
There are 3  unique scenarios which we must accomidate:

ability to run workflow in a forked repository (this CI/CD pipelines outline the success of that approach)
ability to run workflow in the public repository in a PR (this is will be part of the acceptance criteria before accepting the PR)
ability to run workflow on develop and observe the image is published to GHCR

This was performed by modifying the if logic, but cannot be fully tested until the PR is accepted into the public repository.

The description of the PR is excellent. Might be good to add that to the README somewhere or some sort of doc in the repo to help explain the flow for future developers


Typescript TS file fold generated files in the tree view

Hi all
I wonder if it's possible to implement a folding option for TypeScript like WebStorm's one so transpiled files are somehow more navigable.
Thanks in advance!

Must have feature!

I wonder if it's possible to implement a folding option for TypeScript

Duplicate of : https://github.com/TypeStrong/atom-typescript/issues/253 see discussion there. Some people like the way it is. Will only be done if the treeview provides native support for it :rose:


🚀 Feature: Infer --base from existing package.json scripts during migration

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Overview
Right now, if you run npx create-typescript-app in an existing repository made from the template, you always get the standard mode selection:
◆  How much tooling would you like the template to set up for you?
│  ○ everything  The most comprehensive tooling imaginable: sorting, spellchecking, and more!
│  ● common      Bare starters plus testing and automation for all-contributors and releases. (recommended)
│  ○ minimum     Just bare starter tooling: building, formatting, linting, and type checking.
│  ○ prompt      (allow me to customize)
└

But as a convenience, we could set a default value for this based on package.json's scripts.  Let's say:

If >=3 of the scripts listed under the everything base exist, set the initial value to everything
If >=2 of the scripts listed under the common base exist, set the initial value to common

Additional Info
No response

I'd like to take this, but I'm not quite understanding the potential solution. Could you give me an example please?

Absolutely - thanks for asking!
Suppose npx create-typescript-app --mode migrate (or, if running from a local build, node path/to/create-typescript-app/bin/index.js --mode migrate) is run in a directory that includes a package.json with the following "scripts":
{
	"scripts": {
		"build": "tsup",
		"format": "prettier \"**/*\" --ignore-unknown",
		"initialize": "tsx ./src/bin/index.js --mode initialize",
		"lint": "eslint . .*js --max-warnings 0",
		"lint:knip": "knip",
		"lint:md": "markdownlint \"**/*.md\" \".github/**/*.md\" --rules sentences-per-line",
		"lint:package-json": "npmPkgJsonLint .",
		"lint:packages": "pnpm dedupe --check",
		"lint:spelling": "cspell \"**\" \".github/**/*\"",
		"prepare": "husky install",
		"should-semantic-release": "should-semantic-release --verbose",
		"test": "vitest",
		"tsc": "tsc"
	}
}

The migration script could infer that the repo is probably using the "everything" base (https://github.com/JoshuaKGoldberg/create-typescript-app/blob/main/docs/Options.md#base-and-mode). In that case it shouldn't need to ask for which base to use: https://github.com/JoshuaKGoldberg/create-typescript-app/blob/a51c624da09df2fefe7e2b12615a07f0a2457538/src/shared/options/augmentOptionsWithExcludes.ts#L135-L140
Does that answer what you're looking for?

Ah yeah, that makes sense! Thanks for the explainer :)


ItemViewModel: Remove circular dependency with IShellPage

Improves code quality. Unfortunately, no positive impact on memory usage.

ItemViewModel has FolderSettingsViewModel - which has IShellPage instance so there is still circular dependency

Looks fine to me

Is it just me or after this Recycle Bin is broken? :)


WIP: new tests to verify streaming capabilities of itkResampleImageFilter

PR only for the tests that are expected to succeed with #82 (and to fail currently) in order to check their outcome without the changes to itkResampleImageFilter #82  (which currently appear to effect other tests like itkMultiResolutionPyramidImageFilterWithResampleFilterTest as well)
According to https://github.com/InsightSoftwareConsortium/ITK/pull/84#issuecomment-450907156, history squashed into single ENH-commit rebase on to master.
creation history:

plain copy of itkResampleImageTest.cxx and its cmake
employ itkResampleImageTest2s, still the same as itkResampleImageTest2
write MHAs (which support streaming) instead of PNGs
demand streaming and employ where possible
verify streaming for linear case
itkResampleImageTest7.cxx for comparing output of stream driven imaging (SDI) and without SDI
mark resample as modified to enforce re-execution of filter chain

Taking a look, the PipelineMonitorImageFilter needs to be in a different position in the pipeline, i.e.,
reader -> monitor -> resample -> writerOrStreamingFilter
This way, if resample is streaming, it will only request smaller regions from monitor, and monitor can keep track of the regions it is requested.
In contrast, with this topology
reader -> resample -> monitor -> writerOrStreamingFilter
monitor does not know whether or not resample is streaming.
Have patch, will push :-)

rebasing on master...

Cool. Many thanks @thewtex for taking a look and sorting things out. It wasn't easy for me to fully see your changes, i.e. those between my old https://github.com/InsightSoftwareConsortium/ITK/commit/29f4e00f6883b07119df55bc9b7565f03d51df9c and the new one https://github.com/InsightSoftwareConsortium/ITK/pull/392/commits/f9732088f9e81c7dc35f883e36c2df4a29f8a6c4 due to rebasing on newest master and squashing.
So I rebased https://github.com/InsightSoftwareConsortium/ITK/commit/29f4e00f6883b07119df55bc9b7565f03d51df9c onto https://github.com/InsightSoftwareConsortium/ITK/commit/a1bd6835b28b85ba7e6e837ac0e177ae73016fa1 (parent of https://github.com/InsightSoftwareConsortium/ITK/pull/392/commits/f9732088f9e81c7dc35f883e36c2df4a29f8a6c4) and renamed to itkResampleImageTest2Streaming.cxx accordingly which results in https://github.com/romangrothausmann/ITK/commit/4566b7419b4c2bfa860a18957fd30db49eb26d55.
Sadly, GH comparison does not work well in that case (https://github.com/InsightSoftwareConsortium/ITK/compare/f9732088f9e81c7dc35f883e36c2df4a29f8a6c4...romangrothausmann:4566b7419b4c2bfa860a18957fd30db49eb26d55) showing itkResampleImageTest2Streaming.cxx  and itkResampleImageTest7.cxx as new files instead of just the differences. So I create a new commit on top of https://github.com/romangrothausmann/ITK/commit/4566b7419b4c2bfa860a18957fd30db49eb26d55 with the files as in https://github.com/InsightSoftwareConsortium/ITK/pull/392/commits/f9732088f9e81c7dc35f883e36c2df4a29f8a6c4 resulting in https://github.com/romangrothausmann/ITK/commit/e41fff83f86407feae9552354e4567eb7ca96efe, so looking at that in GH should show the actual changes from @thewtex between https://github.com/InsightSoftwareConsortium/ITK/commit/29f4e00f6883b07119df55bc9b7565f03d51df9c https://github.com/InsightSoftwareConsortium/ITK/pull/392/commits/f9732088f9e81c7dc35f883e36c2df4a29f8a6c4 (please correct me if I got that wrong).
So there I can see that (apart from white space changes https://github.com/romangrothausmann/ITK/commit/e41fff83f86407feae9552354e4567eb7ca96efe#diff-50f53fc01f72ba938548d64a1218589bL79):

the unnecessary readers and their args got removed (https://github.com/romangrothausmann/ITK/commit/e41fff83f86407feae9552354e4567eb7ca96efe#diff-50f53fc01f72ba938548d64a1218589bL93).
typdefs replaced by using (sorry, I didn't catch those in the transition)
the order was changed to reader->monitor->resample (https://github.com/romangrothausmann/ITK/commit/e41fff83f86407feae9552354e4567eb7ca96efe#diff-50f53fc01f72ba938548d64a1218589bR121 and https://github.com/romangrothausmann/ITK/commit/e41fff83f86407feae9552354e4567eb7ca96efe#diff-50f53fc01f72ba938548d64a1218589bR175) which is great and (I understand now), same for itkResampleImageTest7.cxx (https://github.com/romangrothausmann/ITK/commit/e41fff83f86407feae9552354e4567eb7ca96efe#diff-dfa5983cf67253ce0e03aca56a207db2R91).
that ClearPipelineSavedInformation was introduced (e.g. https://github.com/romangrothausmann/ITK/commit/e41fff83f86407feae9552354e4567eb7ca96efe#diff-dfa5983cf67253ce0e03aca56a207db2R137)
VerifyAllInputCanStream was changed from 1 to 8: https://github.com/romangrothausmann/ITK/commit/e41fff83f86407feae9552354e4567eb7ca96efe#diff-50f53fc01f72ba938548d64a1218589bR181
Modified() is called on image instead of resample https://github.com/romangrothausmann/ITK/commit/e41fff83f86407feae9552354e4567eb7ca96efe#diff-dfa5983cf67253ce0e03aca56a207db2R137

I think all are fine except 5, where I intended that the monitor filter checks that streaming took not place, which I thought VerifyAllInputCanStream(1) would do. That and some minor corrections are proposed in #468.
Just for my better understanding: What is point 4. for, and why the change of 6.?

@thewtex Just noticed that for itkResampleImageTest2Streaming the comparison to the output of itkResampleImageTest2 was removed:
https://github.com/InsightSoftwareConsortium/ITK/compare/29f4e00f6883b07119df55bc9b7565f03d51df9c..69bb0bf11e345aaeeb4f72066d53b8d822061411#diff-e496b4f78280279f13a386cdbc983d41L255
Is that intended? My idea was that the itkResampleImageTest2Streaming return value and the comparison with the output from itkResampleImageTest2 should determine failure or success of the test.

@romangrothausmann the comparison could be added back. If the test depends on the output of itkResampleImageTest2, we will need to add DEPENDS property to ensure itkResampleImageTest2 is executed first hen running in parallel.


Emergancy party kit

About the PR

Why / Balance

Technical details

Media

Requirements

[ ] I have read and am following the Pull Request and Changelog Guidelines.
[ ] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

Your issue is that the validator is detecting that an extra icon.png isn't included in your JSON.
You need to either include it or remove it. I recommend changing,
    {
      "name": "EmergencyPartyKit"
    },

to
    {
      "name": "icon"
    },

and keeping it the same for the rest.


 I downloaded the latest version. I was looking for a APM RUM demo microservice application.
Can you help me with latest images for petclinic . Any microservice application will help

@aishvaryaps In what environment are you trying to run this? Have you tried running using - https://splunk.github.io/observability-workshop/v5.64/en/resources/local-hosting/index.html?

   The issue may be related that the containers are build for the splunk show intel machines
So if you are using an arm based platform it wil fail

Investigate building arm containers

I am using GKE to get set up pet clinic. Not using ARM based platform.

Can you post the CrashLoopBackoff logs please so we can determine what is happening in your environment. We have not tested on GKE and only support K3s running locally or on an EC2 instance.

Unabled to replicate so closing out


Some quetions

If your account is gg69420.us-east-1.aws.snowflakecomputing.com what would do put on account and username? I've been trying every possible combination and it doesn't seem to be working. Any thoughts?

In that case your account is gg69420. The username is not part of the URL. Your username is the one you use to log in to the snowflake console, for example.
I created a simple API test please take a look maybe it helps: https://github.com/szabacsik/snowflake-json-web-token/blob/1.0.1/tests/EndToEndTest.php, and I also updated the readme, how to create private and public keys for snowflake users.

@szabacsik thanks a lot. it works perfectly now!


SliverAppBar that snaps with RefreshIndicator

How can I have a SliverAppBar that snaps like in the contacts demo but also be able to use RefreshIndicator ?

StackOverflow is a goid pkace to ask how-to questions

If you can't see, try this attribute.
RefreshIndicator  displacement


Do not split tests on AllVersionsCrossVersion

See https://github.com/gradle/gradle-private/issues/2693
This commit disable test splits for AllVersionsCrossVersion.

Thanks @wolfs !


Update Cake.Git to the latest version

Update Cake.Slack to latest, and Cake 0.18.0 compatible, version

@pascalberger thank you for making this change!


Client side redirect to keep old URLs in place

Check out this technique: https://www.w3.org/TR/WCAG20-TECHS/H76.html

[ ] /students-projects/ > /projects/
[ ] /students_projects/* > /projects/*
[ ] /about-us/ > /about/
[ ] /mat-news/ > /news/
[ ] /ars-2019/* > /events/ars-2019/*
[ ] /chi2019/ > /events/chi2019/
[ ] /nime2020/ > /events/nime2020/
[ ] /xr-chi-2021/ > `/events/xr-chi-2021/


Request for Guidance on Robustness Testing in IDEAW Framework

Hello, I am currently studying your work on the IDEAW framework, and I find it very insightful for audio watermarking research. I have been testing the provided implementation for embedding and extracting watermarks, and I aim to evaluate the robustness of the system under various audio attacks. Could you kindly provide guidance or share any sample code to perform robustness testing for the IDEAW framework? Thank you

Hi, thanks for your interest in IDEAW.
As the previous tests were performed on an internal company server, I currently do not have the robustness evaluation code readily available to me.
The robustness evaluation code is generally written following this process:
audio+msg+l.code -(embedder)-> watermarked audio -(attack (e.g. attack in attack layer))-> attacked audio -(extractor)-> msg+l.code, then calculate the ACC of the extracted msg+l.code is extracted.
Note that the applied attack can be any one of the attacks in the attack layer or a combination of multiple attacks, and the parameters of the attack can be different from those in the attack layer.


Collab svc - end session bugs (and related)

integrate w db for sessioning (@smolegz)
end session - deletes/removes record (so that subsequent matches between the same user will create a new session and get the correct question) (@lynnetteeee can do after db implemented)

Re-verify point 2 after merging #66


Force LF line endings

Closes #62 (I hope). This forces Git to use LF line endings.
When cloning the repo via Git, #62 does not occur, as Git is smart enough to use the correct line endings. I suppose the npm packages are packed by a Windows user, and npm doesn't seem to convert CRLF to LF line endings. This should force LF line endings, but the packager should probably also use something like dos2unix or change their editor's settings so that it truly stays LF (don't know how Windows handles this).

Hi @krmax44 , thank you, I will ask on #62 if it closes the issue


Switch to cloud formation ASGs

for automatic rollout of new launch configurations
See: https://github.com/hashicorp/terraform/issues/1552#issuecomment-191847434

Would like more details on what cloudformation gives us, how it differs from the existing setup, and if there are any stability concerns. And perhaps why this is relevant for us.
Thanks!

@igorwwwwwwwwwwwwwwwwwwww tl;dr - updating a launch configuration automatically propagates.See the linked terraform thread for oodles of details.


Changed Either.sequence return type

Fixes #2064

Codecov Report

Merging #2072 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #2072      +/-   ##
============================================
- Coverage     97.55%   97.55%   -0.01%
  Complexity     5204     5204
============================================
  Files            92       92
  Lines         11932    11930       -2
  Branches       1574     1572       -2
============================================
- Hits          11640    11638       -2
  Misses          144      144
  Partials        148      148

Impacted Files
Coverage Δ
Complexity Δ

vavr/src/main/java/io/vavr/control/Either.java
100% <100%> (ø)
45 <3> (ø)
: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 3db51f8...8f34732. Read the comment docs.


Recurring events fail silently with daily note calendars

Describe the bug
I have set full calendar to use daily notes.  In full calendar I create a recurring tasks or event and neither is added.
To Reproduce
have a daily note calendar.
on whichever day is today click a time slot.
enter a title and then check the recur box.  select the current day of the week and the next 3 days.
can be either an event or task
click save.
nothing is created
Expected behavior
events appear on the calendar for today and the next 3 days.
an items is added to the specified section for events in today's daily note
Console Errors
Uncaught (in promise) Error: MiniSearch: cannot remove document with ID DONE.md: it is not in the index
at CF.remove (plugin:omnisearch:6:12068)
at e0.removeFromMinisearch (plugin:omnisearch:39:6419)
at jE (plugin:omnisearch:53:7235)
at async eval (plugin:omnisearch:53:5493)
plugin:obsidian-full-calendar:9105 The specified value "hsl(214, 100%, calc(85% - 3.8%))" does not conform to the required format.  The format is "#rrggbb" where rr, gg, bb are two-digit hexadecimal numbers.
set @ plugin:obsidian-full-calendar:9105
3plugin:obsidian-full-calendar:56904 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'startsWith')
at IcsSource.eval (plugin:obsidian-full-calendar:56904:15)
at Generator.next ()
at eval (plugin:obsidian-full-calendar:78:61)
at new Promise ()
at __async (plugin:obsidian-full-calendar:62:10)
at IcsSource.toApi (plugin:obsidian-full-calendar:56902:12)
at eval (plugin:obsidian-full-calendar:57940:138)
at Array.map ()
at CalendarView.eval (plugin:obsidian-full-calendar:57940:123)
at Generator.next ().
Device info (please complete the following information):
windows 11, latest version

Hi @pcause, recurring events are not yet supported in daily notes. Trying to add one should throw up a notice for users rather than failing silently, though.

Hello @davish. Thank you for a wonderful plugin! I wonder whether this will be implemented in the plugin or not? I might change workflow if this is not implemented before the year starts properly.

this is an area where using some of the tasks plugin format might make sense.  In daily notes if you use the tasks plugin format they have a recurs spec using rrule to parse and then a start date and a due date.  You might make it appear:

with start and no due, every instance forever or until completed
with due and no start, every day from the date of the daily note page where it appears until due date or completed
with start and due, every day between start and due until due or completed
with neither start nor due, start on the date of the daily note where it appears, goes until completed.


Store triggers by job

Motivation:
We have tens of thousands of jobs which caused major performance issues when the jobs completed. Looking into it further, removing from the triggers list was causing the problem.
Change:
Convert triggers list to a map of lists keyed on JobKey since most accesses are done from the JobKey.

Hi @jsteinich,
This contribution falls under the conditions described under the heading "Contributions which do require a full Contributor’s License Agreement (CLA)" here: http://www.quartz-scheduler.org/community/contribute.html
We very much appreciate your contribution, and request that you submit a signed agreement.
Thanks!

Signed CLA received. Thanks!

Thanks for the PR @jsteinich ! There is a one extra { that resulted in compiler error, but other than that, the change looks good and all tests passed. I will go ahead and fix this minor problem and merge it in.

Sorry about the error. It must have been a typo when I copied my local change to GitHub.
I'm glad the changes are helpful.


refactor: clean up exports

More cleanups, import organization, removal of symbol exports (pub use) where not necessary.

FYI not sure what's going on with codecov, please ignore the error...

This is great.


React to aspnet/Razor#561.

TagHelper directives no longer have quotes.
Regenerated test output.

Just an FYI.

:heart_eyes: does this mean we have intellisense for these now?

lol @rynowak nopppe, It'd be incredibly difficult to add IntelliSense for these bits.


Refine class syntax

This change refines the syntax highlighting inside a class.

This commit actually fixes #20.

Thanks for this pr. Will merge it.

Thanks for this, fixes matchit nicely as well!


chore(lint): add import rule checks

What is the previous behavior before this PR?
import statements were unchecked, and cycles of imports were undetected
What is the new behavior after this PR?
import statements are checked, and cycles of imports are detected
Indeed, this PR won't pass CI until #3198 or #3157 gets merged.
eslint-plugin-import required upgrading eslint to parse ECMAScript 2017 (from the default of v5!), which triggered some new instances of comma-dangle in function calls and arguments.  Some of them look really ugly (e.g. when calling a function with an inline function as sole argument), so I've made comma-dangle optional for functions.

Codecov Report

Merging #3199 (931b41e) into master (35db4ff) will increase coverage by 0.39%.
The diff coverage is n/a.

:exclamation: Current head 931b41e differs from pull request most recent head e277613. Consider uploading reports for the commit e277613 to get more accurate results

@@            Coverage Diff             @@
##           master    #3199      +/-   ##
==========================================
+ Coverage   93.54%   93.94%   +0.39%
==========================================
  Files          88       88
  Lines        6557     6345     -212
  Branches     1513     1314     -199
==========================================
- Hits         6134     5961     -173
+ Misses        393      354      -39
  Partials       30       30

Impacted Files
Coverage Δ

src/Namespace.js
93.93% <0.00%> (-0.94%)
:arrow_down:

src/functions/kern.js
84.21% <0.00%> (-0.79%)
:arrow_down:

contrib/auto-render/auto-render.js
72.00% <0.00%> (-0.55%)
:arrow_down:

src/buildTree.js
90.00% <0.00%> (-0.33%)
:arrow_down:

src/functions/arrow.js
95.55% <0.00%> (-0.28%)
:arrow_down:

contrib/render-a11y-string/render-a11y-string.js
84.34% <0.00%> (-0.18%)
:arrow_down:

src/functions/mclass.js
98.03% <0.00%> (-0.18%)
:arrow_down:

src/functions/accent.js
98.64% <0.00%> (-0.15%)
:arrow_down:

src/functions/delimsizing.js
97.39% <0.00%> (-0.13%)
:arrow_down:

src/functions/includegraphics.js
93.67% <0.00%> (-0.08%)
:arrow_down:

... and 39 more

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 167f38d...e277613. Read the comment docs.


Task firewall config does not complete

Fix
If you're on Windows and you cloned Drupal VM in a way that resulted in some files getting Windows line endings, it could be the line endings cause issues when you try to run vagrant up or vagrant provision. A quick fix:

Find /drupalvm/provisioning/roles/geerlingguy.firewall/templates/firewall.j2
Edit it in notepad++ and convert it to Unix format (LF)
Edit > EOL Conversion > UNIX Format
Save the file
Run vagrant up or vagrant provision again.

Original Issue
the drupal folder that the documentation refers to is not generated. the synced folder that i put in config.yml is empty. the error printed to screen is:
TASK [geerlingguy.firewall : Ensure the firewall is enabled and will start on boot.] ***
fatal: [drupalvm]: FAILED! => {"changed": false, "failed": true, "msg": "Error when trying to enable firewall: rc=1 firewall.service is not a native service, redirecting to systemd-sysv-install\nExecuting /lib/systemd/systemd-sysv-install enable firewall\nupdate-rc.d: error: firewall Default-Start contains no runlevels, aborting.\n"}

my host is windows7. here is the put put of vagrant up:
----------------START-----
ccarnnia@CST328169 MINGW64 /d/drupal-vm (master)
$ vagrant up
Bringing machine 'drupalvm' up with 'virtualbox' provider...
==> drupalvm: Cloning VM...
==> drupalvm: Matching MAC address for NAT networking...
==> drupalvm: Checking if box 'geerlingguy/ubuntu1604' is up to date...
==> drupalvm: Setting the name of the VM: drupalvm.dev
==> drupalvm: Clearing any previously set network interfaces...
==> drupalvm: Preparing network interfaces based on configuration...
drupalvm: Adapter 1: nat
drupalvm: Adapter 2: hostonly
==> drupalvm: Forwarding ports...
drupalvm: 22 (guest) => 2222 (host) (adapter 1)
==> drupalvm: Running 'pre-boot' VM customizations...
==> drupalvm: Booting VM...
==> drupalvm: Waiting for machine to boot. This may take a few minutes...
drupalvm: SSH address: <IP_ADDRESS>:2222
drupalvm: SSH username: vagrant
drupalvm: SSH auth method: private key
==> drupalvm: Machine booted and ready!
==> drupalvm: Checking for guest additions in VM...
==> drupalvm: Setting hostname...
==> drupalvm: Configuring and enabling network interfaces...
==> drupalvm: Mounting shared folders...
drupalvm: /vagrant => D:/drupal-vm
drupalvm: /var/www/drupalvm => D:/drupal-vm/data
==> drupalvm: Running provisioner: ansible_local...
drupalvm: Installing Ansible...
drupalvm: Running ansible-playbook...
PLAY [all] *********************************************************************
TASK [setup] *******************************************************************
ok: [drupalvm]
TASK [Define config_dir.] ******************************************************
skipping: [drupalvm]
TASK [include_vars] ************************************************************
ok: [drupalvm] => (item=/vagrant/config.yml)
TASK [include] *****************************************************************
included: /vagrant/provisioning/tasks/init-debian.yml for drupalvm
TASK [Update apt cache if needed.] *********************************************
ok: [drupalvm]
TASK [Get software for Python-based control.] **********************************
changed: [drupalvm] => (item=[u'curl', u'python-apt', u'python-pycurl', u'build-essential', u'sudo', u'unzip'])
TASK [Disable the ufw firewall (since we use a simple iptables firewall).] *****
changed: [drupalvm]
TASK [Add repository for Apache 2.4 on Ubuntu 12.] *****************************
skipping: [drupalvm]
TASK [Add repository for PHP 5.5.] *********************************************
skipping: [drupalvm]
TASK [Add repository for PHP 5.6.] *********************************************
skipping: [drupalvm]
TASK [Add repository for PHP 7.0.] *********************************************
skipping: [drupalvm]
TASK [Define php_xhprof_html_dir.] *********************************************
skipping: [drupalvm]
TASK [include] *****************************************************************
skipping: [drupalvm]
TASK [Run configured pre-provision shell scripts.] *****************************
TASK [Run configured pre-provision ansible task files.] ************************
TASK [Set the PHP webserver daemon correctly when nginx is in use.] ************
skipping: [drupalvm]
TASK [geerlingguy.repo-remi : Install remi repo.] ******************************
skipping: [drupalvm]
TASK [geerlingguy.repo-remi : Import remi GPG key.] ****************************
skipping: [drupalvm]
TASK [geerlingguy.firewall : Ensure iptables is installed (RedHat).] ***********
skipping: [drupalvm]
TASK [geerlingguy.firewall : Ensure iptables is installed (Debian).] ***********
ok: [drupalvm]
TASK [geerlingguy.firewall : Flush iptables the first time playbook runs.] *****
changed: [drupalvm]
TASK [geerlingguy.firewall : Copy firewall script into place.] *****************
changed: [drupalvm]
TASK [geerlingguy.firewall : Copy firewall init script into place.] ************
changed: [drupalvm]
TASK [geerlingguy.firewall : Ensure the firewall is enabled and will start on boot.] ***
fatal: [drupalvm]: FAILED! => {"changed": false, "failed": true, "msg": "Error when trying to enable firewall: rc=1 firewall.service is not a native service, redirecting to systemd-sysv-install\nExecuting /lib/systemd/systemd-sysv-install enable firewall\nupdate-rc.d: error: firewall Default-Start contains no runlevels, aborting.\n"}
NO MORE HOSTS LEFT *************************************************************
RUNNING HANDLER [geerlingguy.firewall : restart firewall] **********************
to retry, use: --limit @/vagrant/provisioning/playbook.retry
PLAY RECAP *********************************************************************
drupalvm                   : ok=10   changed=5    unreachable=0    failed=1
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
----------------END-------

@carnnia

the drupal folder that the documentation refers to is not generated.

The part of Drupal VM that builds the drupal site via composer doesn't run until a little later in the build process.

firewall Default-Start contains no runlevels, aborting.

Can I ask what version of Drupal VM are you running, and also what version of Vagrant and VirtualBox is installed? Also, can you give the output of vagrant box list?
One note—I haven't tested Drupal VM on Windows 7 in at least a year, and I'm not sure if anyone else using it on windows is still on 7 (I think there are some users... but everyone who helps with bugfixes/testing on Windows is at least on 8, mostly on 10), so I can't help much if it turns out there's something related to Windows 7...

i am now trying to install it on my ubuntu machine. i'll keep you informed.
back to windows:
Drupal VM: the latest, I guess. I just cloned the repo.
VirtualBox: Version 5.0.26 r108824
Vagrant: Vagrant 1.8.5
List of boxes:
ccarnnia@CST328169 MINGW64 /d/drupal-vm (master)
$ vagrant box list
geerlingguy/ubuntu1604 (virtualbox, 1.0.4)
precise32              (virtualbox, 0)

Okay, thanks, very helpful!
Also, does anything in this issue help? https://github.com/geerlingguy/drupal-vm/issues/695
Maybe try vagrant provision to see if the second run through works?

I have the same issue on win7 64 pro.

@oliperas - Can you try with geerlingguy/ubuntu1404? There are some differences between that box and the bento box.

Tried with geerlingguy/ubuntu1404
`TASK [geerlingguy.firewall : Ensure the firewall is enabled and will start on bo                                               ot.] ***
fatal: [drupalvm]: FAILED! => {"changed": false, "failed": true, "msg": "failed                                                determining service state, possible typo of service name?"}
NO MORE HOSTS LEFT *************************************************************
RUNNING HANDLER [geerlingguy.firewall : restart firewall] **********************
to retry, use: --limit @/vagrant/provisioning/playbook.retry
PLAY RECAP *********************************************************************
drupalvm                   : ok=9    changed=6    unreachable=0    failed=1
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.`

@oliperas - Just to confirm, are you on windows, and what version of Windows if so? Also, what version of Vagrant are you running (run vagrant --version).

Facing same problem..
TASK [geerlingguy.firewall : Ensure the firewall is enabled and will start on bo ot.] ***
fatal: [drupalvm]: FAILED! => {"changed": false, "failed": true, "msg": "failed determining service state, possible typo of service name?"}
NO MORE HOSTS LEFT *************************************************************
RUNNING HANDLER [geerlingguy.firewall : restart firewall] **********************
to retry, use: --limit @/vagrant/provisioning/playbook.retry
PLAY RECAP *********************************************************************
drupalvm : ok=9 changed=6 unreachable=0 failed=1
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
OS: windows 7 Enterprise Service Pack1.
Virtaul Box version: 5.1.2
vagrant version: 1.8.5
vagrant boxlist:  geerlingguy/ubuntu1404 (Virtualbox 1.1.3)
vagrant plugin list: vagrant -share (1.1.5, system)
vagrant -winnfsd (1.3.0)

I'm closing #695 and moving that conversation into this thread. For anyone having this problem, please post the following:

Exact OS version you're using (e.g. Windows 7, 8, 10)
The step where the build fails.
Any config.yml customizations (especially which vagrant_box you're using).
Versions of Vagrant, VirtualBox and Drupal VM being used.

Brock, just FYI. I shall post it as a new ticket.
Best regards,
Surya Paruchuri
On Aug 16, 2016 3:44 PM, "Jeff Geerling"<EMAIL_ADDRESS>wrote:

I'm closing #695 https://github.com/geerlingguy/drupal-vm/issues/695
and moving that conversation into this thread. For anyone having this
problem, please post the following:

Exact OS version you're using (e.g. Windows 7, 8, 10)
The step where the build fails.
Any config.yml customizations (especially which vagrant_box you're
using).
Versions of Vagrant, VirtualBox and Drupal VM being used.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/geerlingguy/drupal-vm/issues/829#issuecomment-240215453,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT6XOob6ifV6bUL27ZSLeFPpptPKLul6ks5qghMxgaJpZM4JVYO-
.

So, using the following environment, all fresh/brand new installs, I can't replicate the issue:

Windows 10
Cygwin
N/A - success with all defaults
No config.yml customizations (using all defaults)
Vagrant 1.8.5, VirtualBox 5.1.2, Drupal VM 3.2.0

So do I have to move-on to windows 10 to install drupalvm? Cannot I run it
on windows 7 and yes I think I am using a custom config.yml file.
--
Best regards,
Surya Paruchuri
On Aug 16, 2016 4:17 PM, "Jeff Geerling"<EMAIL_ADDRESS>wrote:

So, using the following environment, all fresh/brand new installs, I can't
replicate the issue:

Windows 10
Cygwin
N/A - success with all defaults
No config.yml customizations (using all defaults)
Vagrant 1.8.5, VirtualBox 5.1.2, Drupal VM 3.2.0

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/geerlingguy/drupal-vm/issues/829#issuecomment-240224295,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT6XOkznezKgyhESTCrmUIYjmCRnkIiZks5qghrEgaJpZM4JVYO-
.

OK so seems I hadn't done a 'sudo apt-get upgrade' & 'sudo apt-get dist-upgrade' on my linux laptop for a while - just done that now and it's running through fine.
So perhaps that's the issue on yours, can't remember how cygwin works, seem to remember it runs linux within windows so perhaps the version of linux it's running needs some updates.

@suryatp - Drupal VM should work on Windows 7... but I don't have access to any computers with that old a version of Windows, and I only know one person with quick access to a Windows 8 laptop, so I can only reliably test things in a Windows 10 environment.

I'm happy to help test Windows 7. However, I can't recreate the problem. Here are my stats:

OS: Windows 7 Professional, service pack 1
Shell: Babun (wrapper around Cygwin, I believe)
NA (doesn't fail)
No significant config.yml changes from the default (interestingly, I happen to be using the exact same config.yml as suryatp, who posted above and is experiencing the problem)
Vagrant 1.8.4, Virtual Box 5.0.24, DrupalVM cloned from Github on July 31

Like I said, it's working for me. But if anyone wants me to try anything to recreate it, just let me know and I'll give it a shot.

I have solved this issue by adding:
sudo: yes
behind task

name: Ensure the firewall is enabled and will start on boot of file
povisioning/roles/geerlingguy.firewall/tasks/main.yml

@stephanebelazouz - That's really strange, because the entire playbook should be run under the sudo user, because of the line become: yes at the top of the main playbook: https://github.com/geerlingguy/drupal-vm/blob/master/provisioning/playbook.yml#L3
When you add the sudo: yes do you get any warnings? Also, if you take it out and run vagrant provision again does it still succeed?

You right, this is make no sense  because of the become: yes...
So after another test with fresh install it's seems to work perfectly.
Thx for your job and your time.

Exact OS version you're using: Windows 7 Pro SP1
Which terminal/CLI you're using: Cmder 160724 stable
The step where the build fails: "TASK [geerlingguy.firewall : Ensure the firewall is enabled and will start on boot.]"
Any config.yml customizations (especially which vagrant_box you're using): Drupal core version 7, hostname , and machine_name updates.
Versions of Vagrant, VirtualBox and Drupal VM being used:

Vagrant 1.8.5

VirtualBox Version 5.0.26 r108824

Drupal VM up to commit 84e0ed145817ee7acfe7f0bd04af917bca8dedb9 (git cloned from the GitHub page)

The error I run into specifically is

fatal: [betterpt]: FAILED! => {"changed": false, "failed": true, "msg": "Job for firewall.service failed because the control process exited with error code. See "systemctl status firewall.service" and "journalctl -xe" for details.\n"}

I just destroyed and re-provisioned it and now get a new error.

fatal: [drupalvm]: FAILED! => {"changed": false, "failed": true, "msg": "Error when trying to enable firewall: rc=1 firewall.service is not a native service, redirecting to systemd-sysv-install\nExecuting /lib/systemd/systemd-sysv-install enable firewall\nupdate-rc.d: error: firewall Default-Start contains no runlevels, aborting.\n"}

After getting this the first time, it goes back to the control process error code message from my previous post.

I tried a couple of things to recreate the problem:

Upgraded to Vagrant 1.8.5
Instead of Babun/Cygwin just ran "vagrant up" in the normal Windows cmd.exe.
Still no luck recreating it - still no errors.

Same problem:
Windows 10 Pro 64-bit (should be SP1, but I don't see it)
Virtualbox: 5.0.26 r108824
Vagrant: 1.8.5
Box: geerlingguy/ubuntu1604 1.0.4
config.yml and config.local.yml attached.
drupal-vm-config.zip
TASK [geerlingguy.firewall : Ensure the firewall is enabled and will start on boot.] ***
fatal: [massforms8vm]: FAILED! => {"changed": false, "failed": true, "msg": "Error when trying to enable firewall: rc=1 firewall.service is not a native service, redirecting to systemd-sysv-install\nExecuting /lib/systemd/systemd-sysv-install enable firewall\nupdate-rc.d: error: firewall Default-Start contains no runlevels, aborting.\n"}

Same error with custom config removed.  If it helps, I attach the results of "vagrant provision" run after I removed the custom config.
provisioning.txt

I had the same firewall errors on vagrant up and vagrant provision, running Windows 7 with the latest versions of Drupal VM/Vagrant/Virtual Box, and [https://github.com/geerlingguy/drupal-vm/issues/832#issuecomment-236153465](this comment from 832) fixed it for me:

Find /drupalvm/provisioning/roles/geerlingguy.firewall/templates/firewall.j2
Edit it in notepad++ and convert it to Unix format (LF)

Edit > EOL Conversion > UNIX Format

Thank you @rjgwiz . That worked like magic. Thanks a lot. Shall keep posting the progress.

Worked for me too.   Thanks @rjgwiz !

Would a .gitattributes file that forced LF checkouts resolve this problem?

Not sure if this host-system specific as I am OS X El Capitan (10.11.6) and I received the same error.  Works fine for me on geerlingguy/ubuntu1404, but not on geerlingguy/ubuntu1604.

Same for me - I tried to build on a Windows 8.1 laptop as I was travelling and got the Firewall message.  My Windows 10 desktop machine builds fine  - both are set up identically using builds of vagrant (1.8.5) and Virtual box (5.0.26).  Both are using identical build sets from our own repo.  Doing the EOF conversion to Unix worked on my Win 8.1 laptop for me... weird.

getting the same error here, systemctl list-unit-files shows no firewall.service file, and the firewall init script in /etc/init.d gives the following error on call
bash: /etc/init.d/firewall: /bin/sh^M: bad interpreter: No such file or directory
Running on Windows 10 x64, fresh install with Git Bash  as the shell, error below
TASK [geerlingguy.firewall : Ensure the firewall is enabled and will start on boot.] *** fatal: [drupalvm]: FAILED! => {"changed": false, "failed": true, "msg": "Error when trying to enable firewall: rc=1 firewall.service is not a native service, redirecting to systemd-sysv-install\nExecuting /lib/systemd/systemd-sysv-install enable firewall\nupdate-rc.d: error: firewall Default-Start contains no runlevels, aborting.\n"}

Thanks @rjgwiz for the solution and the steps to apply the solution. Your solution (EOL conversion) fixed my problem. My environment was:

OS: Win 10 Enterprise x64
Shell: Cmder (running cmd.exe in admin mode)
Error: No error
Vagrant 1.8.5, VirtualBox 5.1.2, Drupal VM 3.2.1

I've just started playing with drupal-vm on a windows 10 machine; I'm in the process of translating a mac os vagrant setup into a windows compatible one and I ran into the same firewall error as the others here have. The EOL conversion suggested by @rjgwiz  got me past the firewall error as well, I'm on a windows 10 pro environment using powershell, virtualbox 5.1.4, vagrant 1.8.5.

Can also confirm that switching to ubuntu1404 allowed the build to pass the firewall error.
macOS Sierra, fresh install of vagrant, virtualbox, and ansible via brew

I've updated the top comment, and will point others with the issue there (thanks @rjgwiz!). This should help anyone running into the issue on Windows. On Mac, it could be something else... so if people keep running into this issue, we can open a new issue to investigate further.

Hi,
With the default configuration and the previous drupal-vm version (downloaded oct 11, 2016) all is fine. This morning I downloaded the master branch again -because of release 3.4.0- and now I get this issue with the firewall. I tried the fix as suggested but those line endings are already Unix endings. So that fix does not work for this version.
Versions:
Windows 7 (yup, I'm one of those, can't change that anytime soon i'm afraid)
Vagrant version 1.8.6
Virtualbox version 5.1.6
Any suggestions would be great! Thanks

Fails on macOS (El Capitan 10.11.6), Vagrant 1.8.6, VirtualBox 5.0.28, latest Ansible 2.3.0 devel branch, latest geerlingguy/drupal-vm (Oct 22, 1e942fb), standard /bin/bash shell.
TASK [geerlingguy.firewall : Ensure the firewall is enabled and will start on boot.] ***
fatal: [drupalvm]: FAILED! => {"changed": false, "failed": true, "msg": "Could not find the requested service \"'firewall'\": "}

Re-running vagrant provision makes no difference.
Fixed after replacing Ansible 2.3.0 devel with stable version (<IP_ADDRESS> from homebrew) followed by vagrant provision.
(actually it now fails at Generate Drupal project with composer package with a "Content-Length mismatch" error when downloading something, will create a separate issue for that one.)
If I can help with further debugging, let me know.

@wturrell - I don't support the latest devel branch of Ansible, as there's often a lot of experimentation that goes on in there—right now around service module and some of it's internals—and so I like to wait to target new stable releases.
Often these bugs are either fixed by the next minor release, or in a quick followup bugfix release, so there's no use for me to try fixing it in all my roles where things are broken with HEAD. Hopefully Ansible keeps getting more stable over time as more tests are added :)

That said, this would be something that could be pursued in a bug report against Ansible core if it's reproducible on devel but not on stable 2.1.

Hmm... Now I'm hitting this with Ansible 2.2.0 :( Opening a new issue: #958

Using Windows 7, cmder, centos7 box.
Changing line endings made no difference.
Making sure this was in config.yml did:
drupalvm_ansible_version_min: '2.1'
Didn't work under:
drupalvm_ansible_version_min: '2.2'

There's a web of related issues here, but I thought I'd report back that my firewall errors and my postgresql errors are gone when I merged in the latest from master. Gracias.

Interesting, thanks for posting!

I have the same problem:
`TASK [geerlingguy.firewall : Ensure the firewall is enabled and will start on boot.] ***
fatal: [netnod]: FAILED! => {"changed": false, "failed": true, "msg": "Could not find the requested service "'firewall'": "}
to retry, use: --limit @/Users/nbintev/Projects/netnod/provisioning/playbook.retry
PLAY RECAP *********************************************************************
netnod                     : ok=9    changed=0    unreachable=0    failed=1
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.`
I've changed the box to: geerlingguy/ubuntu1404, and it works for me, but it doesn't solve the issue.
I'm running on:
OS: Mac OS x 10.12.2
Vagrant: 1.8.6
ansible: 2.2.0
Virtual box: 5.1.8


Add scenarios text/basic scenarios

https://github.com/Jakehp/carcalc/commit/b6377a6f62fafbb722362fb6fc92dae09828c461


Revalidation failed with reason: ParserError: invalid line (no token ";" or ":")

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports and didn't find any similar reports.

Expected Behavior
Sync remote calendar (iCloud)
Current behaviour
Not syncing remote calendar (iCloud)
JavaScript console output
plugin:obsidian-full-calendar:64678 Revalidating remote calendars...
revalidateRemoteCalendars @ plugin:obsidian-full-calendar:64678
plugin:obsidian-full-calendar:64715 Revalidation failed with reason: ParserError: invalid line (no token ";" or ":") "Boucherville Québec J4B6G4"
eval @ plugin:obsidian-full-calendar:64715
plugin:obsidian-full-calendar:64715 Revalidation failed with reason: ParserError: invalid line (no token ";" or ":") "Boucherville Québec J4B6J9"
eval @ plugin:obsidian-full-calendar:64715
plugin:obsidian-full-calendar:64715 Revalidation failed with reason: ParserError: invalid line (no token ";" or ":") "Brossard Québec J4Y 0E2"
eval @ plugin:obsidian-full-calendar:64715
Steps to reproduce

Create App specific password in Apple account
Use that password to import the calendars
Fail

Calendar information
I have four calendars in iCloud and one of them is shared with someone else.
Which Operating Systems are you using?

[X] macOS
[ ] Windows
[ ] Linux
[ ] Android
[ ] iOS

Obsidian Version
1.2.8
Full Calendar Plugin Version
0.10.7
Checks

[X] I have tried it with all other plugins disabled and the error still occurs.

Possible solution
Wild guess, but I live in Québec, so maybe the accent is causing problems. I have seen this sort of problem before. But given that the error says no token ";" or ":" I am not sure how to jump from the accent to that.
Also not sure where town and province are coming from, otherwise I would try to change it to see if it helps.
Comments
No response

I have this issue also. Same steps to reproduce. Error message is:
Revalidation failed with reason: ParserError: invalid line (no token plugin:obsidian-full-calendar:64715 ";" or ":") "Lafayette IN"

Looks like part of the street address for an event in my calendar.

The same error for me, many calendars and events not displayed because of this bug :/
I don't live in Canada or USA (I live in France) but same error : no token ";" or ":".
Unfortunately the plugin is unusable :(

Also experience an issue with this

Same issue here

Also encountering this issue. Was there any resolution or solution discovered by anyone? I even tried searching through my events for the specific address and nothing comes up.

No update in the last 2 years it seems. It's all but dead.


lang: Don't pass in program account info to CpiContext

The program being invoked no longer needs to be passed into the list of account infos when using cpi. We should remove it from the CpiContext to save compute.

blocked by #454, also see https://github.com/project-serum/anchor/pull/965#discussion_r753378295


Latest 8.4.0 snapshot builds often fail to deploy using terraform

Expected Behavior
Deployment is created successfully.
Current Behavior
Build deployment fail. Deployment is "Unhealthy".

## Terraform definition
The following parameters were used:
TF_VAR_cluster_name=test TF_VAR_apikey=<your key> TF_VAR_cluster_template_id=gcp-compute-optimized-v2 TF_VAR_cluster_mem_fleet=16G TF_VAR_cluster_mem_es=32G TF_VAR_stack_version=8.4.0-SNAPSHOT TF_VAR_docker_image=docker.elastic.co/observability-ci/elasticsearch-cloud:8.4.0-deb082e1
terraform {
  required_version = ">= 0.12.29"

  required_providers {
    ec = {
      source  = "elastic/ec"
      version = "0.4.1"
    }
  }
}

variable "cluster_name" {
  type = string
  default = "oblt_perf"
}

variable "region" {
  type = string
  default = "gcp-us-west2"
}

variable "apikey" {
    type = string
    default = "<your key>"
}
variable "stack_version" {
  type = string
  default = "8.3.0"
}

variable "docker_image" {
  type = string
  default = "docker.elastic.co/observability-ci/elasticsearch-cloud:8.3.0"
}

variable "cluster_template_id" {
  type = string
  default = "gcp-io-optimized-v2"
}

variable "cluster_mem_es" {
  type = string
  default = "16g"
}

variable "cluster_mem_esw" {
  type = string
  default = "4g"
}

variable "cluster_mem_esm" {
  type = string
  default = "16g"
}

variable "cluster_mem_esc" {
  type = string
  default = "8g"
}

variable "cluster_mem_kibana" {
  type = string
  default = "8g"
}

variable "cluster_mem_apm" {
  type = string
  default = "16g"
}

variable "cluster_mem_fleet" {
  type = string
  default = "16g"
}

provider "ec" {
    # ECE installation endpoint

  # APIKey is the recommended authentication mechanism. When
  # Targeting the Elasticsearch Service, APIKeys are the only
  # valid authentication mechanism.
  apikey = var.apikey

  verbose = false
}

resource "random_uuid" "main" {}

resource "ec_deployment" "main" {
  name = var.cluster_name != "oblt_perf" ? var.cluster_name : "oblt_perf-${random_uuid.main.result}"

  # Mandatory fields
  region                 = var.region
  version                = var.stack_version
  deployment_template_id = var.cluster_template_id

  #observability {
  #  deployment_id = "de5622671ad44072bfda58d1eaec5eb3"
  #}

  elasticsearch {
    config {
        docker_image = var.docker_image
    }
    topology {
      id = "hot_content"
      size = var.cluster_mem_es
      zone_count = 2
    }
#    topology {
#      id = "master"
#      size = var.cluster_mem_esm
#      zone_count = 2
#    }
    topology {
      id = "coordinating"
      size = var.cluster_mem_esc
      zone_count = 2
    }
#   topology {
#      id = "warm"
#      size = var.cluster_mem_esw
#      zone_count = 2
#   }
  }

  kibana {
    topology {
      size = var.cluster_mem_kibana
    }
  }

  integrations_server {
    config {
      user_settings_yaml = "agent.logging.level: debug\n"
     }
    topology {
       size = var.cluster_mem_fleet
     }
  }

#  apm {
#    config {
#      user_settings_yaml = "agent.logging.level: debug\n"
#    }
#  }

}

Steps to Reproduce

Pick the latest build number from https://artifacts-api.elastic.co/v1/versions/8.4.0-SNAPSHOT/builds/
Try to create a new cluster using terraform parameters from the above.

Context
Issue is found within the Fleet scalability project (you can refer to #fleet-scaling channel in Slack).
Currently I only use the following snapshot: 8.4.0-5954f776. I always succeed at creating cluster with it, Newer versions fail to deploy.
It's essential for the project using the latest versions of Stack to validate recent scalability defect fixes.
Your Environment
Terraform v1.2.4
on linux_amd64

@ablnk , this is a public repo to note terraform issues. A deployment failing to build from a next verisons' snapshot likely has nothing to do with terraform itself... I'm closing this one unless you can specify what terraform does wrong that causes this.


"npm run build" creates incorrect paths to scripts when using github pages with custom domain

Hi, I am working on a react project that I am deploying using github pages with an custom domain I purchased through google. In my package.json I have the url of my github repo with the project: "homepage": "https://epaudio.github.io/hammerheadaudio/".
When I run npm run build, this generates a index.html file with the following path to the react scripts: "/hammerheadaudio/static/js/main.7020354e.js"
When my website is deployed with the custom domain the page is unable to find the react scripts until I go into the index.html and change the path to "/static/js/main.7020354e.js". I can get this path to be automatically generated by changing homepage in my package.json to be: "https://epaudio.github.io/", but then the page no longer deploys to my git repo.
Is there something I can do to get npm run build to generate the correct paths automatically in this situation so that I don't have to go through and change things manually every time I push an update?
Here is my repo and the url I am deploying to:
https://github.com/epaudio/hammerheadaudio
http://hammerheadaudio.com/
Thanks!

If you are deploying to http://hammerheadaudio.com/ then that should be your homepage URL, not the github pages URL.


security

The issue which to be  used in for the website The security of websites is frequently overlooked in favour of design and user experience. But, security should be taken into account at every stage of the website development process, but especially when the website is handling sensitive data like credit card numbers and personal information. When it comes to website security, there are numerous factors to take into account, including denial of service attacks, the security of user data, database errors, unauthorised access to password-protected areas of the website, etc. Cross-Site Scripting, Phishing, Cross-Site Request Forgery, Shell Injection, Session Hijacking, SQL Injection, Buffer Overflow, etc. are a few of the security risks.

We have to consider for the fact how much traffic is on our website and how should be able to manage by having zero broken links and make sure there is no clutter on home webpage.

We have to consider for the fact how much traffic is on our website and how should be able to manage by having zero broken links and make sure there is no clutter on home webpage.

We will use to track issues as part of a larger issue, so we can use task lists and see which data should be connected with.

All the relevent options to be used for each user depending on if user is a student or pro member.

we can open meaningful issues that provide the information that you need, and also about issue templates to help the contributers in the group.


 All GET Methods seems fine, but I can't make all the "Write"-Methods working. The NGINX Proxy always logs GET and all my PUT Requests also just acts as if theye were GETs.
Not sure if this is Netbox related or just some NGINX misconfiguration.. Can't find any useful informations at the moment.
Any suggestions? Have you seen this behaviour? I tried the the docker-compose way locally, but also on our OpenShift Installation I see the same behaviour.
Regads, sebastian from Puzze ITC, Bern
edit:
and yes, the API Token is write enabled =)

never mind....
I sent the Request to http and not https.. and then with the Redirect the Method probably got lost. :man_facepalming:


KeyError: 'instances'  when running nndet_prep on nndet_example dataset

Hello everyone,
When using nndet_prep 000D3 command (on the test dataset), the following error occured:
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
  File "/anaconda/envs/nnDetection/lib/python3.9/multiprocessing/pool.py", line 125, in worker
    result = (True, func(*args, **kwds))
  File "/anaconda/envs/nnDetection/lib/python3.9/multiprocessing/pool.py", line 51, in starmapstar
    return list(itertools.starmap(args[0], args[1]))
  File "/home/ndebs/code/nndetection/nnDetection/nndet/planning/properties/instance.py", line 155, in analyze_instances_per_case
    props["num_instances"] = count_instances(props, all_classes)
  File "/home/ndebs/code/nndetection/nnDetection/nndet/planning/properties/instance.py", line 177, in count_instances
    instance_classes = list(map(int, props["instances"].values()))
KeyError: 'instances'
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/anaconda/envs/nnDetection/bin/nndet_prep", line 33, in <module>
    sys.exit(load_entry_point('nndet', 'console_scripts', 'nndet_prep')())
  File "/home/ndebs/code/nndetection/nnDetection/nndet/utils/check.py", line 58, in wrapper
    return func(*args, **kwargs)
  File "/home/ndebs/code/nndetection/nnDetection/scripts/preprocess.py", line 475, in main
    run(OmegaConf.to_container(cfg, resolve=True),
  File "/home/ndebs/code/nndetection/nnDetection/scripts/preprocess.py", line 394, in run
    run_dataset_analysis(cropped_output_dir=Path(cfg["host"]["cropped_output_dir"]),
  File "/home/ndebs/code/nndetection/nnDetection/scripts/preprocess.py", line 198, in run_dataset_analysis
    _ = analyzer.analyze_dataset(properties)
  File "/home/ndebs/code/nndetection/nnDetection/nndet/planning/analyzer.py", line 80, in analyze_dataset
    props.update(property_fn(self))
  File "/home/ndebs/code/nndetection/nnDetection/nndet/planning/properties/instance.py", line 46, in analyze_instances
    props_per_case = run_analyze_instances(analyzer, all_classes)
  File "/home/ndebs/code/nndetection/nnDetection/nndet/planning/properties/instance.py", line 77, in run_analyze_instances
    props = p.starmap(analyze_instances_per_case, zip(
  File "/anaconda/envs/nnDetection/lib/python3.9/multiprocessing/pool.py", line 372, in starmap
    return self._map_async(func, iterable, starmapstar, chunksize).get()
  File "/anaconda/envs/nnDetection/lib/python3.9/multiprocessing/pool.py", line 771, in get
    raise self._value
KeyError: 'instances'

I am facing the exact same problem when running nndet_prep on my own personal dataset.  It seems that the key "instances" is not created in the pickle files in "data/Task000D3_Example/raw_cropped/labelsTr/" (I printed the dictionnary inside caseXX.pkl in order to check).
Do you have any idea how to solve this problem?
Best
Noëlie

Hi @ndebs,
I just reran the example and did not encounter any issues.
The commands I ran:
nndet_example
nndet_prep 000

The error you describe typically arrises when the json files of the labels in raw_splitted/labelsTr don't contain the "instances" key. Running nndet_prep with the --full_check will check the underlying data and raise an error if something is missing.
The example script generates the json files here:
https://github.com/MIC-DKFZ/nnDetection/blob/880d40a135e388c230621c544ccdaff1aa99151a/scripts/generate_example.py#L91-L98
Best,
Michael

Hello Michael,
Thank you for your feedback!
I correctly launch the code that you mentioned, so the mistake was somewhere else. I finally found my problem: in file load.py, l.85 https://github.com/MIC-DKFZ/nnDetection/blob/61d46a7fac4ed754f8c3c27709ad50dbe224ac33/nndet/io/load.py#L85 :
seg_props_file = f"{str(seg_file).split('.')[0]}.json"

It turns out that the path of my json file contained dots ('/datadrive/db_1.8/Task000D3_Example/).  Therefore the split only retained the first part of my path ('/datadrive/db_1.').
I replaced this line by the following 3 lines and it works:
head,tail = os.path.split(seg_file)
seg_props_file_name = f"{str(tail).split('.')[0]}.json"
seg_props_file = os.path.join(head,seg_props_file_name)

Best,
Noëlie

Hi @ndebs ,
thanks for the update! I try to avoid any punctuation inside the names (I added a note to the readme) since it can mess up the naming as in this case, sorry for that.
Best,
Michael


Why "quantized or perfectly correlated input dimensions" may hurt learning?

Hi,
I found in the tips that "Add some slight noise to the inputs (order of 1E-2). This stabilizes training and prevents sparse gradients, if there are some quantized or perfectly correlated input dimensions."
And I noticed that when I repeat the input features (thus "perfectly correlated input"), the log_jac_det will be large, but I have no idea about the reason.
Could you kindly explain this problem?
My practical question is that dimension of input and output is not the same, for example, x.shape=4, y.shape=100. I want to fit a mapping between x and y, but the dimension of the input and output should be the same, how could I achieve this?

Is there any way to reduce dimensions in INNs?
I know the iRevNet pooling, but the size of the output vectors does not really decrease.

It's difficult to give a succinct answer for this - hopefully someone will come along and make this answer redundant.
It intuitively seems obvious it may hinder learning in a similar way to collinearity violating assumptions in statistical models. For one thing, if you have perfectly correlated inputs, it suggests the dimensionality of your input can easily be reduced (i.e. remove features or use dimensionality reduction). Solving an arbitrarily higher dimensionality problem will be more complicated in terms of optimisation (curse of dimensionality).
I found a casual explanation for how this might hinder gradient descent here, but I couldn't find any literature on this (though I'm sure it exists).
This NIPS paper (which I found from this Quora answer) explains in detail how correlated input dimensions can slow down learning using gradient descent.
I am going to interpret sparse gradients as vanishing gradients, although vanishing gradients implies the problem is the architectural choices in the model (such as depth and activation function). One intuitive explanation (don't hold me to this) is that given the initial direction of the gradients on the loss surface are random, there are now more possible incorrect directions to travel in than the lower dimensional 'true' surface you want to learn on (i.e. by finding a low dimension representation of the data and learning on that). Travelling in these incorrect directions causes small gradients, which with a deep architecture or poor choice of activation function could cause vanishing gradients. It also makes sense that if two data sets have the same number of equally informative (independent of each other) dimensions, where input data X has many perfectly correlated dimensions and input data Y doesn't, then input data X will provide a weaker 'signal' than input data Y. That weak signal could manifest as sparse gradients.
This Quora answer  does a simple experiment to show highly correlated data can lead to unstable weights. It should be fairly easy to setup a test of this using synthetic data?


Diagrams and variation captions don't need a period before the number anymore

Presently the beginning of the caption for diagrams and variations is generated as "Diagram. x ..." or "Variation. x ..." respectively.
I think the period after Diagram/Variation was required before because it was used to denote the abbreviation of Dia. x or Var. x. However, now that these labels have been expanded to the full word the period is redundant and I think it would be better to remove it.
In short, simply "Diagram x ..." and Variation x ..." seems to be better.
(Where other books use a period in between it's because they're abbreviating the word.)

easy fix. I'll push it out tomorrow

Fixed in 6fa84ae


Create arm64 images in PROW images job

We need to add arm64 images to PROW images job
We need changes in Dockerfile of the repo and in PROW repo
Changes in this repo:

Dockerfile-FROM golang:1.22 AS builder
+FROM --platform=$BUILDPLATFORM golang:1.22 AS builder
+ARG BUILDPLATFORM

probably some logic in Makefile to choose platform

Changes in PROW repo:

add .config.prowgen like https://github.com/openshift/release/blob/master/ci-operator/config/openshift/oadp-operator/.config.prowgen to https://github.com/openshift/release/tree/master/ci-operator/config/migtools/oadp-non-admin
add multi_arch: true here https://github.com/openshift/release/blob/master/ci-operator/config/migtools/oadp-non-admin/migtools-oadp-non-admin-master.yaml#L8

I have 2 PRs up for this issue:

https://github.com/migtools/oadp-non-admin/pull/75
https://github.com/openshift/release/pull/56106