'Import from' does not work

Hi,
I am using plugin version <IP_ADDRESS>, Intellij ulimate edition 2017.1.4 and AEM 6.3. I work on Windows. I am trying to import some components, I get this message:
Successfully ended Action 'Import from Server'
components don't get imported though.
I just started using this plugin, is there something I should do before using?
Agnieszka

Can you provide some more details?
What is the node you select to import, are you connected to AEM and can you provide part of the IntelliJ logs that covers the import. Some screenshots would be helpful.

HI @schaefa I couldn't get 'import from...' to work as you know a while ago.  (I had problems using AEM plugins for Eclipse IDE but was able to resolve those by renaming _cq_dialog.xml to prefer a _cq_dialog folder containing .content.xml files).
I'd rather use Intellij, given the choice so tried AEM tools for Intellij again today.  On creating a new server and trying the 'AEM > import from...' option the import successfully works, but not subsequently.
I'll attach my log files from today 🤞

@josephh I reviewed your logs and I found this:
Import failed: 'Resource at path /apps/simplyhealth/components/page/editorialpage/editorialpage.html is not a direct child of /apps/simplyhealth/components/page/editorialpage/basic'
java.lang.IllegalArgumentException: Resource at path /apps/simplyhealth/components/page/editorialpage/editorialpage.html is not a direct child of /apps/simplyhealth/components/page/editorialpage/basic
I am not sure what is going on but I am assume that you have a new entry (editorialpage) in the parent node which is missing in IntelliJ.
Can you try to import from /apps/simplyhealth/components/page/editorialpage and let me know what happened there (go to the idea.log and search for 'Import failed:'.
Thanks - Andy Schaefer

All, 'Import From' doesn't work for me, I am trying with the latest Beta drop on Mac OS Sera , IntelliJ 2018.1, PFB the trace.
`4:09 PM	Debug Message: Folder Path: 'com.headwire.aem.tooling.intellij.eclipse.stub.IPath@243a85cf'
4:09 PM	Debug Message: OS Based String: '/Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root/apps/fmdita'
4:09 PM	Debug Message: Folder Path: 'com.headwire.aem.tooling.intellij.eclipse.stub.IPath@74b5f96d'
4:09 PM	Debug Message: OS Based String: '/Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root/apps/fmdita/vijesh-fixed-import'
4:09 PM	Start Action: 'Import from Server'
4:09 PM	Debug Message: Content Base Path: '/Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root'
4:09 PM	Debug Message: Content Base Path: '/Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root'
4:09 PM	Updated File: Start to Updated File '/Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root/apps/fmdita/vijesh-fixed-import' with Change Type: CREATED
4:09 PM	Debug Message: Got Repository: 'org.apache.sling.ide.impl.vlt.VltRepository@2dede1fc'
4:09 PM	Debug Message: Got Command: 'org.apache.sling.ide.transport.TracingCommand@1486119'
4:09 PM	Debug Message: Check Parent File: File Wrapper for: /Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root/apps/fmdita
4:09 PM	Debug Message: Check Parent File: File Wrapper for: /Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root/apps
4:09 PM	Debug Message: Check Parent File: File Wrapper for: /Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root
4:09 PM	Successfully ended Action: 'Import from Server'
4:09 PM	Updated File: Successfully Updated File '/Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root/apps/fmdita/vijesh-fixed-import'
4:09 PM	Debug Message: Content Base Path: '/Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root'
4:09 PM	Updated File: Start to Updated File '/Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root/apps/fmdita/vijesh-fixed-import/.content.xml' with Change Type: CREATED
4:09 PM	Debug Message: Got Repository: 'org.apache.sling.ide.impl.vlt.VltRepository@2dede1fc'
4:09 PM	Debug Message: Got Command: 'null'
4:09 PM	Updated File: Failed to Update File '/Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root/apps/fmdita/vijesh-fixed-import/.content.xml' in Module 'Module: module name = 'pwc-madison.ui.apps', last modification timestamp = 0, part of build = true'
4:09 PM	Updated File: Start to Updated File '/Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root/apps/fmdita/vijesh-fixed-import/.content.xml' with Change Type: CHANGED
4:09 PM	Debug Message: Got Repository: 'org.apache.sling.ide.impl.vlt.VltRepository@2dede1fc'
4:09 PM	Debug Message: Got Command: 'null'
4:09 PM	Updated File: Failed to Update File '/Users/vijeshknair/Documents/sourcecode/pwc.madison.base/ui.apps/src/main/content/jcr_root/apps/fmdita/vijesh-fixed-import/.content.xml' in Module 'Module: module name = 'pwc-madison.ui.apps', last modification timestamp = 0, part of build = true'`

I tested the 'Import from Server' and it works for me with the caveat that when a node properties were updated then I had to call the 'Import from Server' on the node and not on .content.xml.

Due to high maintenance we decided to End the Development of this plugin.

Due to high maintenance we decided to End the Development of this plugin.


Fallback to reading the entire file when filehandle.createReadStream() isn't available

filehandle.createReadStream has only been available since NodeJS v16.11.0. Users not yet on a version this recent will be prevented from using this package due to us not gracefully falling back to another implementation.
See: https://github.com/oblador/esbuild-server/blob/c26201077fbcb6800ae8dc82229dd8470a5d782a/src/index.ts#L188-L189

We're on 14.x, and it's not a trivial upgrade due to our scale. I think supporting non-EOL releases makes sense (14.x, 16.x, 18.x, 19.x) when backwards compatibility is relatively straight forward (as is in this case -- if createReadStream doesn't exist on the FileHandle, use fs.createReadStream).

Sure, that would be great!

@cuongvo Still up for that PR?

Closing due to lack of response


add links about ports and firewalls

Links added to:

doc for gcloud compute instances list
GCE on firewall rules. This topic is GCP-specific, but also offers a nice overview of firewall rules. A better solution down the road might be to update this existing K8s topic and link to it: https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/
but that's a bigger fix. AWS is pretty opaque about firewall customization from what I can see, for example (mostly third-party tools?)

Fixes issue #4440

This change is

/unassign

/assign @bowei


chore: update the cilium nightly config

Reason for Change:

Update the cilium nightly config based on the changes on the master branch. Removal support for kube-proxy-replacement: strict : https://github.com/cilium/cilium/blob/main/Documentation/operations/upgrade.rst?plain=1#L448
Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] relevant PR labels added

Notes:

/azp run Azure Container Networking PR


Install and configure Jenkis

Anusha working

Installed Git.
yet to install jenkins

I installed jenkins.

Not yet configured.
Am not understanding how to configure it.

installed Jenkins

Write a pipeline job and view in blue ocean

go through batch scripting

execute python from stage as explained


:bug: can't find file types

When i try to import the vite-popoyoko library, i have a types error.
The problem is that typescript can't find the typings, yet we have a .d.ts file in the build.

In the meantime, a simple ts ignore allows you to use the package :

I tried to modify the package.json file in the exports section :
"exports": {
    ".": {
      "import": "./build/popoyoko-ui-vite.es.js",
      "require": "./build/popoyoko-ui-vite.cjs.js",
+    "types": "./build/index.d.ts"
    }
  },

This solution fix the declaration file import, but it doesn't fix the autocompletion for the "auto" import

Resolved by this [pr] (https://github.com/Popoyoko/popoyoko-ui-vite/pull/105)

Find why CI stops

Fixed !
Now pushing on develop will automatically build on the package branch. If the build fails, no build is push but we can still develop.


Automated continuous integration

Issue
Currently we have unit tests for individual parts of the simulator, but no integration tests to ensure different components of the simulator interact correctly
Ideas

Use the tutorial as an integration test
Write run method so that internal state can be readily accessed
Automatic tests on github (eg TravisCI)
Tests with known behavior (e.g. deterministic algorithm, specific event queues, etc.)

@sunash This is set up, right? Should we close the issue?


Regression: Cannot override default_font

Software Versions

Python: 3.7.8
OS: Fedora Silverblue 32
Kivy: 1.11.1
Kivy installation method: pip wheel

Describe the bug
Importing config.Config implicitly imports core.text, and so sets core.text.DEFAULT_FONT before the user has a chance to update the kivy/default_font config option.
Expected behavior
Importing config.Config does not set core.text.DEFAULT_FONT, enabling the user to override the kivy/default_font config option and thus override the default font before the start of the app.
This behaviour was actually tested and worked with the inclusion of core.text.DEFAULT_FONT.
To Reproduce
Assuming the Source Sans Pro font exists in data/fonts, this code will still create an app using Roboto as the default typeface:
from kivy.config import Config
Config.set('kivy', 'log_level', 'debug')
Config.set('kivy', 'default_font', [
    'Source Sans Pro',
    'data/fonts/SourceSansPro-Regular.otf',
    'data/fonts/SourceSansPro-It.otf',
    'data/fonts/SourceSansPro-Bold.otf',
    'data/fonts/SourceSansPro-BoldIt.otf',
])

from kivy.app import App
from kivy.lang import Builder

KV = """
Label:
    text: 'The quick brown fox jumps over the lazy dog'
    font_size: '42pt'
"""

class TestApp(App):
    def build(self):
        return Builder.load_string(KV)

if __name__ == '__main__':
    TestApp().run()

However by changing default_font to ['Source Sans Pro', 'data/fonts/SourceSansPro-Regular.otf', 'data/fonts/SourceSansPro-It.otf', 'data/fonts/SourceSansPro-Bold.otf', 'data/fonts/SourceSansPro-BoldIt.otf'] inside ~/.kivy/config.ini, the font does change in the app.
Additional context
I want to include a custom font with my app and use it in any text shown in it.

Oh gosh, I cannot reproduce it anymore, by the looks of it during my testing a neighbouring __init__.py file was imported, seemingly causing this bug. Sorry for the noise.

Actually, it wasn’t the __init__.py file, it was the inspector module that was being imported (since it was set in the config)! Hope this helps someone, it’s a frustrating edge-case.


Fix compilation of hwloc

The linux specific define is wrong and the string replacement was done in the wrong order which caused defines such as:
#define HWLOC_HAVE_ATTRIBUTE 1_SENTINEL
#define HWLOC_HAVE_ATTRIBUTE 1_UNUSED
#define HWLOC_HAVE_ATTRIBUTE 1_WARN_UNUSED_RESULT
#define HWLOC_HAVE_ATTRIBUTE 1_WEAK_ALIAS

etc

Not a good reviewer for this.


chore: setup prod and dev docker with compose

This PR introduces several enhancements to the Docker setup:

Staged Builds in Dockerfiles: Ensures all Dockerfiles use multi-stage builds, allowing services to be built for both development and production using the same file.
Alpine-Based Images: Standardizes all images to use Alpine as the base image to reduce the overall size.
Compose Files for Different Environments:

Build: Adds a Docker Compose file for building the images to verify they won't break in CI.
Production: Adds a Docker Compose file for running services in production mode to ensure they won't break once deployed.
Development: Adds a Docker Compose file for development mode, including hot-reload and other development tools.

Root Package.json Updates: Adds relevant commands to the root package.json to improve the developer experience (DX).

With these changes, we can ensure that any developer can test and run the project in any environment, whether it's for development, continuous integration, or production, providing a consistent and reliable setup across all stages.

We need to test actually deploying in prod with this config

After some thinking I removed the dep on .env.local for some services in docker compose file. Added a .env.sandbox.docker-compose-dev to git having all that's needed for staging

@baktun14 @baktun14 improved this further today:

ensured all apps are build the same way and this allowed to use same docker files for apps with the same stack: nodejs and nextjs
added health checks to so that apps wait to start till migration is done
ensured apps are served in non-privileged mode for security implications

@baktun14 @Redm4x another thing is I noticed that console is served on port 3001 https://github.com/akash-network/cloudmos/blob/main/apps/deploy-web/deploy.yml#L15 which basically means that Nginx is unused. So I removed the config and relevant steps in the Dockerfile. Let me know if I'm missing anything.


Adding a key binding for scrolling pages

Is it possible to add a keybinding for scroll the webpage of jupyterlab up and down? Like Ctrl + e/y or Ctrl + u/d work in vim. I just could find a way to scroll the page continuously without using mouse. The j/k key and Ctrl + j/k key can only scroll discretely based on the cell which makes it impossible to see a long output of a cell without using a mouse.

This would be great!
It maybe best to have it in command mode, so that ctrl+u or ctrl+d goes to the previous and the next cell directly without having to move the pointer all the way to the top or all the way to the bottom.


Improve the Mobile Experience

As a person who uses the web via a phone I want to be able to read EmpEmp.org !
AC:

The font on mobile is large enough that people can read it as easily as the current desktop site.
The desktop site keeps the current look.

@carletonclara here is one of the issues I thought you might be interested in.

Google Search Console says:
Viewport not set
Text too small to read
Clickable elements too close together

This is now on Master


How to extract tweets using coordinates of the location

Can someone help me to extract tweets using the coordinates? I see that the Exporter.py contains a "geo" entity in the outputFile.write (line 60). But there are no coordinates in the extracted tweets.
I want to extract the tweets specifying the coordinates similar to what we do by specifying a query/since/until etc. currently.
If someone can fix this, it'll be a great help. Thanks :)

This is an important issue to attempt to solve and I would also be interested in a solution.

Have you found the solution? I also need the coordinates of the tweets but they are all empty. I am aware that not all of the tweets are geotagged but I find it wierd that none of them come with coordinates. Is there some other problem or there are actually no coordinates at all my collected tweets?

There are two different requirements in this thread.

Search tweets based on given Geo Coordinates. This is not possible since Twitter itself doesn't have that feature. You can search using Location though ex. City, State, Country.

Required geo coordinates for each tweet. First, geo is deprecated by Twitter and they put all location information in Coordinates item of json response. Second with this Twitter scrapper twitter do not provide location information in search result. There is a way though but it takes time and reduce performance. You can hit the "permalink" and parse that html document and get the location info. You have to do this for each tweet.


dolphinEmuMaster: 2018-07-22 -> 2018-08-17

Motivation for this change
Version bump.
Things done

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

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

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

@GrahamcOfBorg build dolphinEmuMaster

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: dolphinEmuMaster
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: dolphinEmuMaster
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/9xy770r3ilp9pcj5fcja27h5c11apdi4-dolphin-emu-2018-08-17
shrinking /nix/store/9xy770r3ilp9pcj5fcja27h5c11apdi4-dolphin-emu-2018-08-17/bin/.dolphin-emu-nogui-wrapped
shrinking /nix/store/9xy770r3ilp9pcj5fcja27h5c11apdi4-dolphin-emu-2018-08-17/bin/.dolphin-emu-wrapped
gzipping man pages under /nix/store/9xy770r3ilp9pcj5fcja27h5c11apdi4-dolphin-emu-2018-08-17/share/man/
strip is /nix/store/553rihc190vsyy8b22iqcq25a6489h8y-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/9xy770r3ilp9pcj5fcja27h5c11apdi4-dolphin-emu-2018-08-17/lib  /nix/store/9xy770r3ilp9pcj5fcja27h5c11apdi4-dolphin-emu-2018-08-17/bin
patching script interpreter paths in /nix/store/9xy770r3ilp9pcj5fcja27h5c11apdi4-dolphin-emu-2018-08-17
checking for references to /build in /nix/store/9xy770r3ilp9pcj5fcja27h5c11apdi4-dolphin-emu-2018-08-17...
postPatchMkspecs

Failure on x86_64-darwin (full log)
Attempted: dolphinEmuMaster
Partial log (click to expand)
                                  ^
/tmp/nix-build-dolphin-emu-2018-08-17.drv-0/source/Externals/lzo/lzoconf.h:146:33: note: 'lzo_uint32' declared here
     typedef unsigned int       lzo_uint32;
                                ^
2 errors generated.
make[2]: *** [Source/Core/Core/CMakeFiles/core.dir/build.make:245: Source/Core/Core/CMakeFiles/core.dir/NetPlayServer.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:906: Source/Core/Core/CMakeFiles/core.dir/all] Error 2
make: *** [Makefile:152: all] Error 2
builder for '/nix/store/2jh3llpj1vyg6g5a7qbj9gnk6jyfxi3h-dolphin-emu-2018-08-17.drv' failed with exit code 2
error: build of '/nix/store/2jh3llpj1vyg6g5a7qbj9gnk6jyfxi3h-dolphin-emu-2018-08-17.drv' failed

Thank you.


Fix for missing physical plan in UI

Fixes #3784 and Fixes #3785

Nice catch. The tests seem to work for me, but there's definitely more to clean up as you mentioned. I guess I started making the code match this line: https://github.com/apache/incubator-heron/blob/4d1ab84eea99a374c6838cb9401d6a7fc908af24/heron/tools/ui/resources/static/js/stat-trendlines.js#L264 with the assumption we had broken something in the Tracker cleanup. But looking back at old versions of the code, this UI query may never have matched up with the tracker api. Very odd. I personally prefer the /metrics/query syntax, but might be easier to just roll back to /metricsquery style route. And instead I'll update the javascript to use the proper api call.

But looking back at old versions of the code, this UI query may never have matched up with the tracker api. Very odd.

My guess is technical debt.

I personally prefer the /metrics/query syntax, but might be easier to just roll back to /metricsquery style route.

I agree. Good REST API design necessitates versioning of the API as well as nesting under path routes. All metrics queries should be nested under the /metrics/ path.
I have never used Node.js and I am not sure if the URL needs to have the ? embedded in it - I think the framework should deal with the query string delimiter itself. We typically do not have to do this in libraries for C++/Java/Golang.
https://github.com/apache/incubator-heron/blob/dd23309cba06853e495f378f5d2cf2c50706a41e/heron/tools/ui/resources/static/js/plan-stats.js#L378
Please ping when ready for review.

I'm running into some other issues with parameter mismatch betwen ui and tracker. So I'm doing a bit of testing. One example is topology vs topology_name. There is an alias here, but it didn't seem to work. I was testing with a failed Tracker API call and got different response when using either topology or topology_name. Perhaps the alias isn't working? @Code0x58 might have some insight in helping answer that question.
Another issue I'm seeing is an exception on an API call because role isn't present. But it's listed as Optional. The parameter is treated differently between the two set of routes. Example 1 and Example 2.

I have always had issues bringing up the UI so I can only look at the code.

One example is topology vs topology_name. There is an alias here, but it didn't seem to work.

The naming convention for topologies has changed on K8s and I am not sure if this would affect the UI. Labels have the topology's name and the StatefulSet name has either -manager or -executors appended to it. I am not sure how the tracker manages the scraping and collecting of stats.

Another issue I'm seeing is an exception on an API call because role isn't present. But it's listed as Optional. The parameter is treated differently between the two set of routes. Example 1 and Example 2.

According to the Optional docs, a value of None will be returned as required. How is a role value of None handled? Exception? What changed?

So for testing heron-tracker and heron-ui, I realized doing the local install is much easier. You can try this:

bazel run --config=darwin_nostyle -- scripts/packages:heron-install.sh --user
Add ~/.heron/bin/ to your $PATH
Submit analytic:

heron submit local ~/.heron/examples/heron-streamlet-examples.jar \  org.apache.heron.examples.streamlet.WindowedWordCountTopology \
WindowedWordCountTopology \
--deploy-deactivated

Run the tracker: heron-tracker --type file --rootpath ~/.herondata/repository/state/local/
Run the UI: heron-ui

I'm running into some other issues with parameter mismatch betwen ui and tracker. So I'm doing a bit of testing. One example is topology vs topology_name. There is an alias here, but it didn't seem to work. I was testing with a failed Tracker API call and got different response when using either topology or topology_name. Perhaps the alias isn't working? @Code0x58 might have some insight in helping answer that question.

It looks like alias may be a bit of a misnomer, it may be better to call it source, if this reference covers everything

I've been banging my head against this code. Things are definitely broken. I have more drastic changes, but I haven't pushed them yet because I'm still testing. The exceptions page is still broken. Somewhere we lost the combo of component and instances query parameters.

I am time-constrained for the next few weeks and I still cannot bring up the UI. I typically find it faster to jump in with a debugger and find the issue causing the problem and address it there. Failing that it is time to find what caused the issue.
We need to isolate the commit in which this happened. I would start by checking out the last tagged release to see if the UI is working there. If it is, run a Git bisect between that commit and master branch's HEAD to find the problematic commit. You should have a better idea of what caused the issue. There were major changes to the backend of the UI in the PR that bumped Python to 3.8/3.9, so that is a potential candidate.

I figured out one of my main blockers that I was banging my head against. The Topology object that I was referencing was a Protobuf object. Once I reference the proper TopologyInfo type, the code worked better. Finally making progress again. Will have more commits to this PR in the near future.

I now have most of it working, except the exceptions.json call on heron-ui. I think I'm going to have to put some of the ResponseEnvelope stuff back. Running into an issue with the ApiResponse requiring a dict, but it's getting a list instead. Hopefully will have this all figured out soon.

To give some context to one of the issues I ran into with this work. In the Heron Tracker, we are now using FastAPI. There is a limitation in the framework which does not allow for custom routers in a nested router. Some information can be found here: https://github.com/tiangolo/fastapi/issues/4110
So I think my options are as follows.

Remove the envelope which was part of each returned API call. Not sure if it's a great idea to have. We didn't really use the feature. We never set the timing info. We already have HTTP return codes for status.
Keep the envelope on API returns, but implement in each handler method. The custom API Router decoration doesn't seem to work.
I can technically hack it by making separate nested App instantiations, but this seems wrong.

In the PR, I've gone back and forth between option 1 and 2 as I worked through various issues. I'm currently leaning towards option 1. This is reflected in the PR as it currently stands. But I can be convinced that it is better to go back to the original API responses with the envelope on each Heron Tracker API result.

Remove the envelope which was part of each returned API call. Not sure if it's a great idea to have. We didn't really use the feature. We never set the timing info. We already have HTTP return codes for status

If option 1 simplifies the code then I would agree with going down this route but my fear is that it might break something elsewhere. For option 2, how many/which handlers would we need to update to handle the encasing envelopes?
I am looking things over and I will try to assist as much as I can on this PR.

I think we can safely remove the ResponseEnvelope. There may have been grander plans when it was for its use but they do not seem to have ever been implemented.
https://github.com/apache/incubator-heron/blob/8841d1c4d6b3156a40ffed856fb32c1ceb682855/heron/tools/tracker/src/python/utils.py#L56-L63
It is just a data struct with references to it restricted to:
https://github.com/apache/incubator-heron/blob/8841d1c4d6b3156a40ffed856fb32c1ceb682855/heron/tools/tracker/src/python/app.py
https://github.com/apache/incubator-heron/blob/8841d1c4d6b3156a40ffed856fb32c1ceb682855/heron/tools/tracker/src/python/utils.py
The values of importance are limited to the HTTP response codes, which are themselves restricted to success and failure. Nothing else in the data structure is ever used in a worthwhile way.

Fixes #3801

I think I have most of the UI working again. But having issues with this menu on the Exception page. I'm not sure, but this might have been broken for a long time before. I'm inclined to wrap up this PR to get it into the master branch. We can fix the exceptions menu at a later point. Don't want to leave the main branch broken for too long.

We can fix the exceptions menu at a later point. Don't want to leave the main branch broken for too long.

I agree, let us get this into a stable state and merge. We can create another set of issues for what we know is broken and outstanding.

Another realization I had thanks to some chatting with @surahman ... The Tracker client is not only used by the Heron UI. There seem to also be references in Heron Explorer (I'm not 100% sure what that code does). But we will need to ensure those API changes did not break those referencing components.

This is a tricky set of issues to resolve and is compounded by a lack of access to design documents. There are a lot of moving parts and interdependencies.

Verified that the changes didn't break Heron Explorer (I actually had never used it before, but it's pretty handy tool). The Tracker client code helped abstract away the changes.

Updated pylint to resolve an issue with it failing on Python 3.9+. https://github.com/PyCQA/pylint/issues/3882

I'm now updating to resolve the style fix suggestions.

I will get started on the bottom end of the list of style errors to help out. Files I am looking at:
************* Module basics.base_instance
************* Module basics.bolt_instance
************* Module basics.spout_instance
************* Module instance
************* Module network.gateway_looper
************* Module network.heron_client
************* Module network.metricsmgr_client
************* Module network.protocol
************* Module network.socket_options
************* Module utils.metrics.metrics_helper
************* Module utils.metrics.py_metrics
************* Module utils.misc.pplan_helper
************* Module utils.misc.serializer_helper
************* Module utils.topology.topology_context_impl

Resolving the merge conflict with changes from this branch.

I think these style fixes will require editing most of the Python codebase. The errors Just keep propagating.

I think these style fixes will require editing most of the Python codebase. The errors Just keep propagating.

Yes. Lots of Python changes. But most of them seem to be related to the f-string syntax. Hopefully once we get through that, it won't be too bad. Just takes a lot of time to fix each one and repeat the process.

@surahman Could you help me convert the deprecated asyncore to asyncio? I might just add the waiver for now, but we should update it because it will be removed in Python 3.12. What do you think? I don't know how easy it will be to switch over.

@surahman Could you help me convert the deprecated asyncore to asyncio?

I have not worked with either of those libraries but I can look into it when I have some time. It is best to address this before it becomes an issue.

I just removed a reference to update the global Log that I added.

I can't figure out why the timeline is not working. I've tracked my issue to this line of code. Within the compute_max function, I can print the final dict that is returned. It has values. But when I print data, it only has an empty dict.

I am not sure but I do not think there is a need to convert the zipped together values into a list and then a dict. But then I also do not believe this would affect the return value.
https://github.com/apache/incubator-heron/blob/06e9f75988fd254053b640689879c3393703b0dd/heron/tools/common/src/python/clients/tracker.py#L626
Maybe try this:
return dict(zip(keys, values))

I am not sure but I do not think there is a need to convert the zipped together values into a list and then a dict. But then I also do not believe this would affect the return value.
https://github.com/apache/incubator-heron/blob/06e9f75988fd254053b640689879c3393703b0dd/heron/tools/common/src/python/clients/tracker.py#L626
Maybe try this:
return dict(zip(keys, values))

I think zip() returns an Iterator and the list() call converts to an actual List. I was not familiar with the zip method, but it seems to be a standard pattern. When I print the value returned from that call I can see the value. It's only when that same result is returned from the compute_max that I get an empty {} in the data variable.

I think zip() returns an Iterator and the list() call converts to an actual List.

I believe dict might have a constructor to handle zip return values as seen here.

I can't figure out why the timeline is not working. I've tracked my issue to this line of code. Within the compute_max function, I can print the final dict that is returned. It has values. But when I print data, it only has an empty dict.

Did you do that print within the len(filtered_ts) > 0 and len(filtered_ts[0]["timeline"]) > 0: branch of compute_max(...)? I'm wondering if the {} you are seeing is from the fall-though branch.
Beware that timelines and values in compute_max(...) are generators, so will be exhausted if you do something with them before they are used in the return dict(list(zip(keys, values))), so if you did print(dict(list(zip(keys, values)))) it would consume values and lead to zip of the keys list and an empty generator which results in an empty zip (python 3.10 adds strict=True to help detect these) and would so make the return dict(...) line return an empty dict.
p.s.

I am not sure but I do not think there is a need to convert the zipped together values into a list and then a dict. But then I also do not believe this would affect the return value.
https://github.com/apache/incubator-heron/blob/06e9f75988fd254053b640689879c3393703b0dd/heron/tools/common/src/python/clients/tracker.py#L626
Maybe try this:
return dict(zip(keys, values))

both are equivalent and will be handled the same way due to python's duck typing, as both a generator (returned by zip, in type annotations it is compatible with typing.Iterator but is more strictly a typing.Generator) and list will be treated as iterables. The use of list(generator) can be faster for some cases, but constructs an object which will be discarded so can be a waste of memory.

Thank you for the detailed explanation!

I think this PR is finally done. I'm now able to see the timeline in the UI and most of the functionality is working (as good as it probably was working in the past). There are some super deep menus I think I'd like to clean up in the future, but this is good to go. Thank you for the help @surahman @Code0x58 and @thinker0 !

+1
Test Success

#3814 typo


[Cassandra] cassandra-binding major refactor

All the Thrift-based clients (all clients except CassandraCQLClient) in the cassandra-binding are essentially the same. They have no major functional differences (except for better property support in CassandraClient10). They are all built against the same dependencies and so to me it seems that they are all redundant.
Dredging back through commit history, it looks like the multiple Cassandra clients used to be built against different versions of the Cassandra driver and so were necessary. #64 brought a major paradigm shift in how the project was built and it seems that that is when they really started to just be copies of each other.
Posting this issue to see if anyone sees any reason why they are different that I may have missed. Otherwise they should be consolidated into a single client. This may help ease confusion between which Cassandra clients do what and are for what versions.
I'd be happy to take this on, just want to make sure I did not miss any reason why they are actually different and necessary as they are now.

Related question: do we have anyone willing to test against the earlier versions of Cassandra that need to use (or even can use) the older Thrift-base clients?
If not, should we just deprecate them and remove them in e.g. 6 months?

I had planned on testing against 7, 8, and 10 as the binding suggests. But I agree, deprecating might also make sense, most if not all people are going to be using the cassandra2-binding now.

It might be worth asking on the cassandra user list, since they're more likely to have visibility into current prevalence.

I received a few responses from folks on the Cassandra users mailing list<EMAIL_ADDRESS>Looks like they don't expect many people to be using Cassandra versions in 0.X or 1.X.
So, my thoughts are to follow @busbey suggestion and plaster a deprecation warning on the cassandra-binding README, give it a stated amount of time, then remove it. Really no point in spending much effort on fixing that binding.
I would think keeping the cassandra2-binding named as it is, self documenting, and clearly state the versions it is compatible with at the top of the README. The current README suggests it is good for 2.1+, I want to test and see if it is actually good for 2.0 also.


List non-standard .janno columns to identify non-breaking mistakes in the .janno file

https://github.com/poseidon-framework/published_data/pull/4 made me aware that it can be tricky to identify spelling mistakes in .janno file column names.
Ideas to make this more easy:

Print the non-standard column names while loading. Problem: This could become cumbersome and awfully verbose.
Add the non-standard column names to the output of survey. Problem: This option might get overlooked easily.

The functionality could also go into validate :thinking:

How about we implement a simple --strict option for validate which fails if any of the standard janno columns are missing. We can debate whether it should also fail a janno-file has additional columns, which I think is fine, as long as they're truly extra columns and not wrongly typed standard columns. So I think simply checking and failing if any of the columns we recognise is missing would already help, wouldn't it?

I fear that would not be too useful. I assume usually you would have .janno files with missing columns, given the growing number of variables we're defining for that.
I think a --verbose switch for validate might be an option. Something that is forwarded to readPoseidonPackageCollection and triggers a more informative reading process.


Minimum Difficulty of a Job Schedule

Please fill the details before contributing.

⚠Important!!

[x] Done reading CONTRIBUTING.md?

Adding Code PRs?🔥
⚠Do not add multiple files for the same solution!!!

[ ] Added problem statement(Readme.md) with solution?

[x] Contributing new file?
[ ] Appending your code in already existing file?

From Platform:

[x] Leetcode
[ ] GFG
[ ] Interviewbit
[ ] Others(only acceptable after DISCUSSIONS)

Migration PRs?🤝

[ ] Done deleteing file from home directory?
[x] Added file with correct name and correct directory?

File name changed

Still you have not resolved the issue, next time I have no other option but to ban you from contributing here.


Gauge write messages not appearing in the console

Expected Behavior
Gauge write messages should be available in the output.
Actual Behavior
Gauge write messages is not available in the console output.
Steps to replicate

Create a spec

With Long Steps
===============

     |sleepTime|
     |---------|
     |100      |
     |1000     |
     |4000     |
     |10000    |

* Wait for <sleepTime> to execute

With long Steps1
---------------
* Wait for <sleepTime> to execute

With long Steps2
---------------
* Wait for <sleepTime> to execute

With long Steps3
---------------
* Wait for <sleepTime> to execute

With long Steps4
---------------
* Wait for <sleepTime> to execute

With long Steps5
---------------
* Wait for <sleepTime> to execute

With long Steps6
---------------
* Wait for "100000" to execute

Create a implementation

    @Step("Wait for <sleepTime> to execute")
    public void implementation1(int sleepTime) throws InterruptedException {
        //Thread.sleep(sleepTime);
        Gauge.writeMessage("here");
    }

Run the specs from command line/IDE.
The messages do not appear on the console.

Version
Gauge version: 0.6.2.nightly-2016-08-05

Plugins
-------
csharp (0.9.1.nightly-2016-08-12)
html-report (2.2.0.nightly-2016-08-28)
java (0.5.1.nightly-2016-08-18)
ruby (0.3.2.nightly-2016-08-22)
spectacle (0.0.1)
xml-report (0.1.4.nightly-2016-07-25)

Even if this is not the default behavior and appears when gauge is run in the debug mode, this will help.

As of now this will remain only on the html reports.


AutoRotatingFileDestination crashes

I've been seeing a few of these crashes:
*** -[NSConcreteFileHandle synchronizeFile]: No such file or directory

0
CoreFoundation
__exceptionPreprocess + 124

1
libobjc.A.dylib
objc_exception_throw + 56

2
CoreFoundation
-[NSException initWithCoder:] + 0

3
Foundation
_NSFileHandleRaiseOperationException + 160

4
XCGLogger
block_copy_helper.11 + 26280

5
XCGLogger
block_copy_helper.14 + 12280

6
XCGLogger
globalinit_33_37E021B542BFDF2516C3B96896CA446C_func4 + 21728

7
XCGLogger
__swift_destroy_boxed_opaque_existential_1 + 1732

8
XCGLogger
__swift_destroy_boxed_opaque_existential_1 + 2668

9
XCGLogger
swift_rt_swift_isUniquelyReferenced_nonNull_native + 20816

10
XCGLogger
swift_rt_swift_isUniquelyReferenced_nonNull_native + 8440

11
XCGLogger
globalinit_33_15E519061A979936292C27E39C87C896_func37 + 11532

12
XCGLogger
globalinit_33_15E519061A979936292C27E39C87C896_func34 + 16136

13
XCGLogger
globalinit_33_15E519061A979936292C27E39C87C896_func34 + 11536

@gilroykilroy Can you please give me some more info. How you're reproducing this. What version of Xcode etc you're using.

It just happened a few times. Nothing I could reproduce nor figure out why. I always use the latest Xcode available. Alas due to this issue sitting there for a while I switched to SwiftyBeaver and added my own rotate log code to it.
Sent from my iPad

On Jun 11, 2018, at 3:23 AM, Dave Wood<EMAIL_ADDRESS>wrote:
@gilroykilroy Can you please give me some more info. How you're reproducing this. What version of Xcode etc you're using.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok thanks.

Hi i use the XCGLogger Version 6.1.0 github "DaveWoodCom/XCGLogger" "6.1.0" and get sometimes the File Rotataion Crash at  syncronizeFile()
may be you will add a Lock on the File Handler to fix it?
private func closeFile() {         logFileHandle?.synchronizeFile()         logFileHandle?.closeFile()         logFileHandle = nil     }
Here is the Crash Report
`Application Specific Information:
*** Terminating app due to uncaught exception 'NSFileHandleOperationException', reason: '*** -[NSConcreteFileHandle synchronizeFile]: No such file or directory'
Last Exception Backtrace:
0   CoreFoundation                       0x00000001948c4ec4 __exceptionPreprocess + 228
1   libobjc.A.dylib                      0x0000000193a95a40 objc_exception_throw + 52
2   CoreFoundation                       0x00000001947cb594 +[NSException raise:format:] + 112
3   Foundation                           0x0000000195318610 NSFileHandleRaiseOperationException + 156
4   XCGLogger                            0x000000010d25a38c XCGLogger.FileDestination.rotateFile(to: Any, closure: (Swift.Bool) -> ()?) -> Swift.Bool (FileDestination.swift:137)
5   XCGLogger                            0x000000010d249478 XCGLogger.AutoRotatingFileDestination.rotateFile() -> () (AutoRotatingFileDestination.swift:237)
6   XCGLogger                            0x000000010d249768 XCGLogger.AutoRotatingFileDestination.write(message: Swift.String) -> () (AutoRotatingFileDestination.swift:283)
7   XCGLogger                            0x000000010d23902c closure #1 () -> () in XCGLogger.BaseQueuedDestination.output(logDetails: XCGLogger.LogDetails, message: Swift.String) -> () (BaseQueuedDestination.swift:41)
8   XCGLogger                            0x000000010d238bcc XCGLogger.BaseQueuedDestination.output(logDetails: XCGLogger.LogDetails, message: Swift.String) -> () (BaseQueuedDestination.swift:48)
9   XCGLogger                            0x000000010d23ea8c XCGLogger.BaseDestination.process(logDetails: XCGLogger.LogDetails) -> () (BaseDestination.swift:124)
10  XCGLogger                            0x000000010d2400c4 protocol witness for XCGLogger.DestinationProtocol.process(logDetails: XCGLogger.LogDetails) -> () in conformance XCGLogger.BaseDestination : XCGLogger.DestinationProtocol in XCGLogger (:0)
11  XCGLogger                            0x000000010d25dff8 XCGLogger.XCGLogger.logln(: XCGLogger.XCGLogger.Level, functionName: Swift.String, fileName: Swift.String, lineNumber: Swift.Int, userInfo: [Swift.String : Any], closure: () -> Any?) -> () (XCGLogger.swift:335)
12  XCGLogger                            0x000000010d25dc7c XCGLogger.XCGLogger.logln(: XCGLogger.XCGLogger.Level, functionName: Swift.StaticString, fileName: Swift.StaticString, lineNumber: Swift.Int, userInfo: [Swift.String : Any], closure: () -> Any?) -> () (XCGLogger.swift:313)
13  XCGLogger                            0x000000010d25f9d0 merged XCGLogger.XCGLogger.verbose(: @autoclosure () -> Any?, functionName: Swift.StaticString, fileName: Swift.StaticString, lineNumber: Swift.Int, userInfo: [Swift.String : Any]) -> () + 144
14  XCGLogger                            0x000000010d25f2ac XCGLogger.XCGLogger.warning(: @autoclosure () -> Any?, functionName: Swift.StaticString, fileName: Swift.StaticString, lineNumber: Swift.Int, userInfo: [Swift.String : Any]) -> () + 28
15  Ticketing-Offline                    0x00000001031135b4 generic specialization <Ticketing_Offline.TSDataImageDownloadResponse> of closure #3 (Alamofire.DefaultDownloadResponse) -> () in closure #1 (RxSwift.AnyObserver) -> RxSwift.Disposable in Ticketing_Offline.TSAPIService.download(: Swift.String, destinationPath: Swift.String, method: Alamofire.HTTPMethod, parameters: [Swift.String : Any]?, headers: [Swift.String : Swift.String]?) -> RxSwift.Observable (TSAPIService.swift:390)
`


Incorrect colouring for Gherkin code after table

(Original issue 858 created by quantoid on 2013-02-26T04:41:03.031837+00:00)
Given this snippet:
Feature: Gherkin Syntax Highlighting
    Syntax highlighting for Gherkin code fragments.

    Background: Setting the scene
        Given we have some Gherkin code
          and it includes a table like this:
              |Parameter | Value|
              |ALPHA     |     1|
              |BETA      |     2|

    Scenario: This appears in the wrong colour.
         When Sphinx renders as HTML
         Then all of this scenario is in the same colour as the table above

When rendered as HTML
Then we get the Scenario in the same colour as the table (see attached image).
What's really weird is that if I paste the same code into the demo form at http://pygments.org/ then it works fine.

(Original comment by quantoid on 2013-02-26T04:42:17.195534+00:00)
https://bitbucket.org/birkenfeld/sphinx/issue/1104

(Original comment by quantoid on 2013-02-26T04:44:10.421473+00:00)
See comment here on where this may have been introduced.

(Original comment by leevigraham on 2014-05-23T05:35:52.340368+00:00)
Should the milestone be changed given this isn't fixed in 1.6?


Prevent the event from bubbling

@martingg88 Could you outline the issue that PR #19 was solving.

Fixed in ec97f4953b6cfba1e6f58940f80ad64258f26028


AssertionError: The message does not specify a sender and a default sender has not been configured

The message is pretty clear. Have you configured a sender?

I have solved the problem,so I just delete my problem,thank you sir, you can close the issue.


PMID:30044717 normal membrane closure during cytokinesis

normal cleavage furrow ingression

normal cleavage furrow ingression FYPO:0006879
It's not clear whether the ticket title is a request for a separate term or a synonym, but I've just added the one new term because it has a corresponding GO BP.
edit file: 2a736df11cb4a1235a331761aa20a2d40cdd3f79
release: c6bb70640c22d92a2fafb32d18a7329d277aaf44


METRON-1953 Stellar REPL Fails on Start

The Stellar REPL will fail to launch.  See full stack trace in METRON-1953

Since #1249, two parsers jars are deployed with Metron.
[root@node1 0.7.0]# find $METRON_HOME/lib/ -name metron-parsers-*
/usr/metron/0.7.0/lib/metron-parsers-0.7.0-uber.jar
/usr/metron/0.7.0/lib/metron-parsers-common-0.7.0-uber.jar

The Stellar REPL will refer to metron-parsers-0.7.0-uber.jar since this actually contains the metron-parsers-common code.

In a subsequent PR, we should probably not deploy metron-parsers-common-0.7.0-uber.jar

Testing

Launch Full Dev.
cd metron-deployment/development/centos6
vagrant up
vagrant ssh

Launch the REPL.  Ensure that it successfully is started.
sudo su -
source /etc/default/metron
cd $METRON_HOME
bin/stellar -z $ZOOKEEPER

Run some commands to validate the REPL.

Pull Request Checklist

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.

[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[x] Have you included steps or a guide to how the change may be verified and tested manually?

[x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:

[x] Have you written or updated unit tests and or integration tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

testing

Actually, looking at this again, the intention is to depend on the Parsers Storm Uber jar.  I think I should restore that behavior, not depend on metron-parsers.

Ok, I fixed it.  This follows the intention of what is supposed to happen.  The only problem was "parsers" needed to be "parsing".

+1 by inspection

I think I verified the first fix and not the second.
The second doesn't work for me now.
https://github.com/apache/metron/tree/master/metron-stellar/stellar-common/src/main/scripts/deployed
Is the file that I think needs to be changed, not metron-common


Ungraded Ex1: Suggestions on isSameRide(Ride otherRide) without modifying the interface provided

As the title, since we are not allowed to modify the Ride interface provoded, may I get a hint on how to actually tell whether the two rides are the same ride apart from type checking? Since getting a certain property will not be defined for the interface, and thus not able to compare them directly

I see! Thank you!


[Excel] (Custom Functions) Update Custom Functions 1.3 error handling documentation

Internal work item.

Docs Build status updates of commit e11a1ee:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-errors.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a3bddb0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-errors.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-json.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit ffbe34a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-errors.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-json.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit ee7fbef:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-errors.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-json.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 21116ab:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-errors.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-json.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 297a19d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-errors.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-json.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit fe6b114:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-errors.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-json.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1856b84:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

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

Docs Build status updates of commit 1856b84:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-errors.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-json.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@mscharlock I'm uncertain how to format the output in this sentence:

For example, a custom function could output the array [1],[#NUM!],[3].
Please take a look and let me know what you think. Line 62 in custom-function-errors.md.
Thanks!

Docs Build status updates of commit af6b415:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-errors.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-json.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel