Rlmclaughlin/stock ticker

Description
Ticker board functionality has been achieved. Stock prices are delegated to the board and return correct values. I changed the board because I was having issues making updated code with with Redux. The new board is coded cleanly and a loop is used to populate all of the categories.
Fixes # (issue)
Ticker board has been fixed and functionality has been accomplished. Merge conflicts were resolved as well.
Type of change
This adds a new feature to the landing page
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
The methods used to test this feature were the following:
-Started the React Server and was able to observe recent addition.
-Used the console log to verify that no bugs or errors were present behind the scenes.
-Used the console log to verify that Data was being dispatched as expected.
Checklist:

[x] My code follows the style guidelines of this project
[x ] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] New and existing unit tests pass locally with my changes

we should not be having to deal with styles at this point of our project. In fact we were told not to do styles yet.


TypeError: undefined is not a function this._childrentypeof Symbol === 'function'? Symbol.iterator: '@@iterator'')

Version
Tell us which versions you are using:

react-native-router-flux v4.0.0-beta.22 (v3 is not supported)
react-native v0.49.3

Expected behaviour
Router don't crash
Actual behaviour
Router crash on android when navigating between screens, with error:
TypeError: undefined is not a function this._children[typeof Symbol === 'function'? Symbol.iterator: '@@iterator']()')

It is maybe linked to this:
https://github.com/react-community/react-navigation/issues/1777
Steps to reproduce
For non-obvious bugs, please fork this component, modify Example project to reproduce your issue and include link here.

Just run any app with StackNavigator and babelrc es2015 and stage-0 presets

Tested a little bit more options, it really seems to be a bug inherent to the stack navigator. The tab navigator is working well...

Same here

@CarbonC I solved my problem by importing babel-polyfill, can you try this?

Yeah, i just updated the babel-react-native-preset version right now and it fixed it. Thanks!

@CarbonC Hi, I just started trying out React and having trouble with Navigation.
I got TabNavigator working, but not StackNavigator.
Can you please state which version of babel-react-native-preset you updated to fix the issue?
For reference these are my versions:
{   "name": "SimpleApp",   "version": "0.0.1",   "private": true,   "scripts": {     "start": "node node_modules/react-native/local-cli/cli.js start",     "test": "jest"   },   "dependencies": {     "react": "16.0.0-beta.5",     "react-native": "0.49.5",     "react-navigation": "^1.0.0-beta.16"   },   "devDependencies": {     "babel-jest": "21.2.0",     "babel-preset-react-native": "4.0.0",     "jest": "21.2.1",     "react-test-renderer": "16.0.0-beta.5"   },   "jest": {     "preset": "react-native"   } }
Thanks

This is probably related to a reported bug in beta 16.   See this issue.

@sfreeman28 - your error is probably related to this issue.

@skicson Yea thanks I just saw that Issue report and looks like what I am getting. Thanks for the help

npm install --save babel-polyfill

and add
import "babel-polyfill"

to your entry file.
This work for me on Android.


TestDaemonDiscoveryBackendConfigReload behavior

TestDaemonDiscoveryBackendConfigReload was doing some weird things
with files, creating a file (directly in ./integration-cli), removing
it, then creating a new file in the same place with new data.
This is just weird, so fixed it to use a single file, file will go into
a temp dir so it doesn't pollute integration-cli.
Only reason I found this is because I saw the test.json sitting in integration-cli after a test run.
It was also blindly sending a SIGHUP to the daemon process then sleeping
for 3 seconds.  This is racey, and slow.
Change this to look for the daemon-reload event in the event stream.
Reload logic is moved to a separate function and blocks (w/ a timeout)
waiting for the reload event to fire.
Runtime of the test is now ~0.5s on my machine, where as it was a
minimum of 3s due to the time.Sleep before.

@cpuguy83 valid failure on win2lin.

This should be fixed

LGTM

LGTM

@cpuguy83 needs a rebase 👼

Rebased

Rebased again


example doesn't run

After running yarn install then yarn start
ERROR in ./app.js
Module build failed: ReferenceError: Unknown plugin "transform-flow-strip-types" specified in "/Users/booker/Code/revalidation/.babelrc" at 0, attempted to resolve relative to "/Users/booker/Code/revalidation"
    at /Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/file/options/option-manager.js:180:17
    at Array.map (native)
    at Function.normalisePlugins (/Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
    at OptionManager.mergeOptions (/Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
    at OptionManager.init (/Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
    at File.initOptions (/Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/file/index.js:212:65)
    at new File (/Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/file/index.js:135:24)
    at Pipeline.transform (/Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
    at transpile (/Users/booker/Code/revalidation/example/node_modules/babel-loader/lib/index.js:48:20)
    at Object.module.exports (/Users/booker/Code/revalidation/example/node_modules/babel-loader/lib/index.js:163:20)
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./app.js

Can't replicate the error.
cd example
yarn install
npm start // or yarn start

Should actually run. Can you remove node_modules and try again?

Yeah, of course!
Unfortunately, I get the same error:
~/Code/revalidation master
► cd example

~/Code/revalidation/example master
► rm -rf node_modules

~/Code/revalidation/example master
► yarn install
yarn install v0.24.5
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
✨  Done in 8.09s.

~/Code/revalidation/example master 8s
► yarn start
yarn start v0.24.5
$ webpack-dev-server
Project is running at http://localhost:8080/
webpack output is served from /
Hash: 9151a33f9de3115ff78b
Version: webpack 2.6.1
Time: 1143ms
        Asset    Size  Chunks                    Chunk Names
    bundle.js  317 kB       0  [emitted]  [big]  app
bundle.js.map  375 kB       0  [emitted]         app
chunk    {0} bundle.js, bundle.js.map (app) 303 kB [entry] [rendered]
   [35] ./app.js 1.46 kB {0} [built] [failed] [1 error]
   [36] (webpack)-dev-server/client?http://localhost:8080 5.68 kB {0} [built]
   [37] ./~/ansi-html/index.js 4.26 kB {0} [built]
   [38] ./~/ansi-regex/index.js 135 bytes {0} [built]
   [40] ./~/events/events.js 8.33 kB {0} [built]
   [41] ./~/html-entities/index.js 231 bytes {0} [built]
   [48] ./~/querystring-es3/index.js 127 bytes {0} [built]
   [51] ./~/sockjs-client/lib/entry.js 244 bytes {0} [built]
   [77] ./~/strip-ansi/index.js 161 bytes {0} [built]
   [78] ./~/url/url.js 23.3 kB {0} [built]
   [79] ./~/url/util.js 314 bytes {0} [built]
   [80] (webpack)-dev-server/client/overlay.js 3.73 kB {0} [built]
   [81] (webpack)-dev-server/client/socket.js 897 bytes {0} [built]
   [83] (webpack)/hot/emitter.js 77 bytes {0} [built]
   [84] multi (webpack)-dev-server/client?http://localhost:8080 ./app.js 40 bytes {0} [built]
     + 70 hidden modules

ERROR in ./app.js
Module build failed: ReferenceError: Unknown plugin "transform-flow-strip-types" specified in "/Users/booker/Code/revalidation/.babelrc" at 0, attempted to resolve relative to "/Users/booker/Code/revalidation"
    at /Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/file/options/option-manager.js:180:17
    at Array.map (native)
    at Function.normalisePlugins (/Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
    at OptionManager.mergeOptions (/Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
    at OptionManager.init (/Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
    at File.initOptions (/Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/file/index.js:212:65)
    at new File (/Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/file/index.js:135:24)
    at Pipeline.transform (/Users/booker/Code/revalidation/example/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
    at transpile (/Users/booker/Code/revalidation/example/node_modules/babel-loader/lib/index.js:48:20)
    at Object.module.exports (/Users/booker/Code/revalidation/example/node_modules/babel-loader/lib/index.js:163:20)
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./app.js
webpack: Failed to compile.

Seems like package.json is missing a dependency (do you have it installed globally?)
Sorry, I haven't really tried to debug this, I ran yarn add babel-plugin-transform-flow-strip-types --dev but the problem continues. Will look into it tomorrow

The babel-plugin-transform-flow-strip-types should be a dev dependency in package.json. I'll retry tomorrow and let you know!

The problem is that, only doing yarn install inside the example folder without doing a yarn install inside project root will cause this error.  Added a babel config to the example folder. This should solve the problem.

Awesome, nice one @busypeoples !!

We can close this issue, in case the example works now.

Great, it works now, thanks!


Refactor annotation display layer code to use classes

This patch refactors the annotation display layer code to use classes. This work makes it easier to add new annotation types and improves readability and testability of the code. Feedback is appreciated.
Most of this patch is moving existing code. The following structural additions have been made:

Introduction of AnnotationElementFactory, which is based on the code in src/core/annotation.js, to handle returning the correct annotation element type object.
Introduction of AnnotationElement, a base class for other annotation element types that is responsible for creating a generic empty container.
Introduction of LinkAnnotationElement, responsible for rendering a link annotation element. Contains existing code, but _bindLink and _bindNamedAction have been moved to separate methods where they were previously inlined.
Introduction of TextAnnotationElement, responsible for rendering a text annotation element. Contains existing code, but _toggle, _show and _hide have been moved to separate methods where they were previously inlined.
Introduction of WidgetAnnotationElement, responsible for rendering a widget annotation element. Contains existing code with _setTextStyle as a method here instead of an overall function before.

Aside from the above, JSDoc comments have been added to the classes and methods.
I have tested this with a set of 23 PDF files containing different annotation types, where Link, Text and Widget are covered. I found no difference in behavior, rendering or printing before and after the patch.
@Snuffleupagus Do you have time to review this? If not, feel free to unassign yourself. This patch follows the same pattern as src/core/annotation.js and it's primarily moving around existing code, so hopefully it's not too hard to review. Using ?w=1 might help a bit. Let me know if you would like me to split this into more commits. I can, for example, extract the JSDoc comment additions into a separate commit. Extracting more will be hard because then each commit would not be a working version on its own.

/botio-linux preview

/botio test

I have tested this with a set of 23 PDF files containing different annotation types, where Link, Text and Widget are covered. I found no difference in behavior, rendering or printing before and after the patch.

@timvandermeij Would you be able to look into #6673 next, since having more complete test-coverage for annotations would mean that testing e.g. refactoring PRs like this one would be so much easier?

/botio-linux preview

/botio test

Thank you both. I will address the comments soon. @Snuffleupagus, there is now #6780 for the regression testing.

/botio-linux preview

/botio test

/botio-linux preview

/botio test

Looks good, thank you for the patch!
Also, thanks for your continued efforts in improving both the annotation code and the related tests!


Fixed typo in router.d.ts

Update router.d.ts
Also fixed typo in Photo Browser KS pages (Core/React/Svelte/Vue), request.js and request.d.ts

https://github.com/framework7io/framework7/blob/69a577c97af9f16d4943a9f4b891cb017eacd3cf/src/core/shared/request.js#L324
@nolimits4web  This message: xhr.status is right or should it be message: xhr.statusText?

@DAnn2012 it was xhr.status in before (in v5) but i think .statusText has more sense here

@nolimits4web So will you make the change after merging this PR?
I also point out that there are some references to Template7 in this file:
https://github.com/framework7io/framework7/blob/43480d032de6a4804c562ebe1d6fc767f529aca3/kitchen-sink/core/pages/page-loader-component.html#L17-L20
https://github.com/framework7io/framework7/blob/43480d032de6a4804c562ebe1d6fc767f529aca3/kitchen-sink/core/pages/page-loader-component.html#L38

Thanks. I've fixed mentioned issue


Reduce tests flakiness, especially in CI / constrained environments

Work to reduce flakiness of the tests suite.

I've tested multiple times on macOS, Github actions and Linux on WSL. Seems ok, I encourage reviewers to check locally as well.

Merging this one, it's been quite reliable in many recent CI runs.


NVIDIA SDXL "Detected system did not match any known systems."

Hi I am running into this issue. Are there any ways that I can run the SDXL benchmark on an Intel cpu?
(mlperf) ziw081@mlperf-inference-ziw081-x86-64-10725:/work$ make run_harness RUN_ARGS="--benchmarks=stable-diffusion-xl --scenarios=Offline --test_mode=PerformanceOnly"
[2024-10-19 19:36:27,381 systems.py:197 INFO] Found unknown device in GPU connection topology: NIC0. Skipping.
[2024-10-19 19:36:27,381 systems.py:197 INFO] Found unknown device in GPU connection topology: NIC1. Skipping.
[2024-10-19 19:36:27,381 systems.py:197 INFO] Found unknown device in GPU connection topology: NIC2. Skipping.
[2024-10-19 19:36:27,381 systems.py:197 INFO] Found unknown device in GPU connection topology: NIC3. Skipping.
[2024-10-19 19:36:27,382 systems.py:197 INFO] Found unknown device in GPU connection topology: NIC4. Skipping.
[2024-10-19 19:36:27,382 systems.py:197 INFO] Found unknown device in GPU connection topology: NIC5. Skipping.
[2024-10-19 19:36:27,382 systems.py:197 INFO] Found unknown device in GPU connection topology: NIC6. Skipping.
[2024-10-19 19:36:27,382 systems.py:197 INFO] Found unknown device in GPU connection topology: NIC7. Skipping.
[2024-10-19 19:36:27,382 systems.py:197 INFO] Found unknown device in GPU connection topology: NIC8. Skipping.
[2024-10-19 19:36:27,382 systems.py:197 INFO] Found unknown device in GPU connection topology: NIC9. Skipping.
[2024-10-19 19:36:27,625 main.py:227 INFO] Detected system did not match any known systems. Exiting. SystemConfiguration(host_cpu_conf=CPUConfiguration(layout={CPU(name='Intel(R) Xeon(R) Platinum 8480+', architecture=<CPUArchitecture.x86_64: AliasedName(name='x86_64', aliases=(), patterns=())>, core_count=56, threads_per_core=2): 2}), host_mem_conf=MemoryConfiguration(host_memory_capacity=Memory(quantity=2.1134187, byte_suffix=<ByteSuffix.TB: (1000, 4)>, _num_bytes=2113418700000), comparison_tolerance=0.05), accelerator_conf=AcceleratorConfiguration(layout=defaultdict(<class 'int'>, {GPU(name='NVIDIA H100 80GB HBM3', accelerator_type=<AcceleratorType.Discrete: AliasedName(name='Discrete', aliases=(), patterns=())>, vram=Memory(quantity=79.6474609375, byte_suffix=<ByteSuffix.GiB: (1024, 3)>, _num_bytes=85520809984), max_power_limit=700.0, pci_id='0x233010DE', compute_sm=90): 8})), numa_conf=NUMAConfiguration(numa_nodes={}, num_numa_nodes=2), system_id=None)

======================== Result summaries: ========================

Hi @zixianwang2022. Nvidia implementation won't run on Intel CPUs. You can use the reference implementation for it.


vim.desktop: Set NoDisplay=true

vim.desktop came from Debian where it was requested so that text files could easily be opened with vim.
However, this also made Vim show up in the applications menu which seems very odd for a terminal "app". It might not have been noticed by GNOME users on Debian since the Debian GNOME team has blacklisted vim.desktop from showing in GNOME's Activities Overview.
The Desktop Entry Spec says

NoDisplay means "this application exists, but don't display it in the menus". This can be useful to e.g. associate this application with MIME types, so that it gets launched from a file manager (or other apps), without having a menu entry for it (there are tons of good reasons for this, including e.g. the netscape -remote, or kfmclient openURL kind of stuff).

Therefore, I think it would be very appropriate for vim.desktop to set NoDisplay=true. I confirmed that this hides Vim from the Activities Overview but it still shows up in the Open With dialog on Ubuntu 17.10.
This is different from gvim.desktop which is closer to a traditional desktop app. At least in Debian, gvim is a separate package for those who want that instead of the traditional terminal version.

On Ubuntu both show up, and I think that is fine.  It's up to the user if he wants to use the GUI or a terminal.


How to migrate an on-prem application to serverless?

The article covers the following:
the problems faced with on-prem applications and why opt for seeverless way, the journey to serverless solution and the migration approach from on-prem to serverless using practical example, and the challenges likely to faced during development and delivery phase.
Article checklist
ATTENTION: In your PR - add the ISSUE (topic form) # that this PR corresponds to. You can do this by also adding a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.
[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines
This fixes #2968

This solves issue #2968

Hello @ogoti-lilian, this article is well written and flows well. However, be sure to check out the changes that I made.

@ogoti-lilian, resize your hero image to 600 X 400px

Hello @ogoti-lilian, this article is well written and flows well. However, be sure to check out the changes that I made.

Thank you. I have noted the changes you made and I will improve on the next article.

@Ericgacoki The changes requested have been made.
Thank you

Seems like you have decided to change your author image. Well, you may proceed.🤗

@ogoti-lilian, resize your hero image to 600 X 400px

Sorry for the confusion the requested change has been made.
Thank you

Seems like you have decided to change your author image. Well, you may proceed.🤗

@Ericgacoki It was a slight mistake but I have rectified it.
Thank you

No problem. It happens from time to time 😀
Remember to upload a better hero image :rocket:

plagiarism check done

Great article @ogoti-lilian - very informative and easy to follow through.
Thank you for the awesome review @Ericgacoki.


[Draft] Create configuration for GitHub Issues

Expects addition/removal requests from microsoft/terminal maintainers

Summary of the Pull Request
Configuration for GitHub Issues

PR Checklist

[x] Closes #7953
[x] CLA signed. If not, go over here and sign the CLA
~Tests added/passed~
~Documentation updated. If checked, please file a pull request on our docs repo and link it here: #xxx~
~Schema updated.~
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments
The current commit does the following:

Prevents opening blank issues (Nothing prevents from deleting the contents of an chosen issue template)
Links to MSRC (for security vulnerabilities)
Links to create an issue page in MicrosoftDocs/terminal

This seems fine to me. I personally use the blank one to go my own way sometimes as a core contributor... but I'm not opposed to changing my workflow to just open one and blank it myself to stop the accidental misfires.
Also, I'm wondering if we should have a link out to both docs repos. We have one for Terminal and one for Console stuff (microsoftdocs/console-docs for the latter). Or would that be too confusing? We can always port console issues off of the terminal one if necessary.

Ok. I will let it allow blank issues

Ok. I will let it allow blank issues

Well, hold up. Don't change it until some of the other core contributors chime in with their opinions. I intended a discussion, not ruling with an iron fist.

I am pinging @zadjii-msft because he was not happy to add links to MSRC directly for submitting security vulnerabilities.

I don't think blindly directing people directly to MSRC would be helpful to us as a dev team, I think I'd rather have us notified of the request as well, so we could at least follow up on it.

https://github.com/microsoft/terminal/issues/7953#issuecomment-712119640

@miniksa Since you are not sure about adding links to Console Docs. I will add it. It's easier to remove than to add. So if other members of the team also suggests to not have the link to the console docs, I will remove them.

Oops! My commit title is wrong!

/azp run

Can't rerun CI for my PR? Why?
I always like to see build passing in my PRs. Even if it has nothing to do with the code.

Can't rerun CI for my PR? Why?

Well, the CI runs on MSFT's compute time, so I'm pretty sure the company doesn't want to be able to grant random users the ability to just manually start builds. That makes sense, right?
This is a docs-only PR though, so I think the team will be just fine merging it manually. We don't usually even have the CI trigger for docs-only PRs

Thank you!


chore: update to automatically fire start/end events

This PR updates the InstrumentedCmd wrapper to automatically fire exit events in addition to start events.
The 10 existing commands that have bespoke exit events (i.e. they fire custom CliEvent.aborted or CliEvent.failed) are updated to use a new PartialInstrumentedCmd wrapper that continuous to only fires start events automatically.  Logged https://github.com/meltano/meltano/issues/6342 for a future cleanup pass. That covers these commands specifically:

src/meltano/cli/add.py
src/meltano/cli/config.py
src/meltano/cli/elt.py
src/meltano/cli/environment.py
src/meltano/cli/install.py
src/meltano/cli/invoke.py
src/meltano/cli/job.py
src/meltano/cli/lock.py
src/meltano/cli/run.py
src/meltano/cli/schedule.py

All other commands are updated use InstrumentedCmd which now fires both start AND exit events.
closes #6324
closes #6041

Note
Here's a sample of a CliEvent.failed that was fired automatically when I executed a meltano state move not-an-id okthx: https://gist.github.com/pandemicsyn/dc780f4a0d1cd9983042105ba656ba6b

@pandemicsyn do bespoke exit events in commands not conflict with the new base command class? Don't we receive duplicate events? Or is #6342 meant as a quick follow-up?
Nit: should the semantic type be refactor instead of chore?

@pandemicsyn do bespoke exit events in commands not conflict with the new base command class? Don't we receive duplicate events? Or is https://github.com/meltano/meltano/issues/6342 meant as a quick follow-up?

Nope we're all good, theres no duplication of exit events for these. The 10 commands with bespoke exit events where already reliant on automatic start events, so I switched them to use a PartialIntstrumentedCmd class that only fires start events, it doesn't fire exit events.
When we remove the bespoke exit events we can switch the commands over to use InstrumentedCmd and remove PartialInstrumentedCmd.
https://github.com/meltano/meltano/issues/6342 is not meant/required to be a quick follow up. I'd actually rather we take our time with #6342 because while we're removing it - we shoud also take the time and see which of those try/except that where added to capture telemetry events should raise clearer errors or generate more end-user friendly errors.


Circuit Graph in local

Create the Circuit Graph representation in local mode.
Current Behavior & Expected Behavior
Now the Circuit Graph from the QASM/Qobj is generated via IBM Q Experience API, the idea is move part of this graph generation into the local functions.
Possible Solution
use the Python graphic library to done it, one very standard option is Pillow library.

Closed by #295 - and followed-up by #311!


Add new core libraries to napari info

Description

Add magicgui, superqt, in-n-out, app-model and npe2 versions to napari info for better debug informations
Type of change

[x] improve debug information

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change
[ ] example: I check if my changes works with both PySide and PyQt backends
as there are small differences between the two Qt bindings.

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

As this would be ideal to have in v0.4.17.rc0, I'll likely merge this within the next 12 hours.


Question: How to make app visible for batarangle debugger?

batarangle debugger does not see an app data.

Or augury. ?

It works great with augury for me


Bug Report Unable login with crendentials.yaml

Describe the bug
Unable login with crendentials.yaml, cant register, cant logout
Steps to reproduce bug
using docker deploy hummingbot/dashboard:latest
credentials.yml
# This only works if you change the env variable in the docker-compose.yml
credentials:
  usernames:
    admin:
      email<EMAIL_ADDRESS>      name: test
      logged_in: False
      password: $2b$12$I32ZqZ6Od3nUptrwfXtiiutlCfJ5/UQzPyQq7DivqwKUBixy8qoka
cookie:
  expiry_days: 30
  key: some_signature_key # Must be string
  name: some_cookie_name
pre-authorized:
  emails:
  -<EMAIL_ADDRESS>  -<EMAIL_ADDRESS>


Error when adding  a process matrix to the noise model

Hi! I'm trying to build a noise model using ExplicitOpModel. I want to add 'XX' gate to the basis gates.
model1 = pygsti.objects.ExplicitOpModel([0,1],'pp')

#Populate the Model object with states, effects, gates,
# all in the *normalized* Pauli basis: { I/sqrt(2), X/sqrt(2), Y/sqrt(2), Z/sqrt(2) }
# where I, X, Y, and Z are the standard Pauli matrices.
model1['rho0'] = np.kron([ 1/sqrt(2), 0, 0, 1/sqrt(2) ],[ 1/sqrt(2), 0, 0, 1/sqrt(2) ]) # density matrix [[1, 0], [0, 0]] in Pauli basis
model1['Mdefault'] = pygsti.objects.UnconstrainedPOVM(
    {'00': np.kron([ 1/sqrt(2), 0, 0, 1/sqrt(2) ],[ 1/sqrt(2), 0, 0, 1/sqrt(2) ]),   # projector onto [[1, 0], [0, 0]] in Pauli basis
     '01': np.kron([ 1/sqrt(2), 0, 0, -1/sqrt(2) ],[ 1/sqrt(2), 0, 0, 1/sqrt(2) ]),
    '10': np.kron([ 1/sqrt(2), 0, 0, 1/sqrt(2) ],[ 1/sqrt(2), 0, 0, -1/sqrt(2) ]) ,
     '11': np.kron([ 1/sqrt(2), 0, 0, -1/sqrt(2) ],[ 1/sqrt(2), 0, 0, -1/sqrt(2) ])
    }) # projector onto [[0, 0], [0, 1]] in Pauli basis

angle=np.pi/4
U1_xx= [[np.cos(angle),0,0,-np.sin(angle)*1j],
             [0,np.cos(angle),-np.sin(angle)*1j,0],
              [0,-np.sin(angle)*1j,np.cos(angle),0],
              [-np.sin(angle)*1j,0,0,np.cos(angle)]]
XX= np.kron(U1_xx,np.conjugate(U1_xx))

mdl['Gxx',0,1]=XX

I get an error back pointing to the XX gate. I'm not sure why pysgti thinks 'XX' is of evolution type 'statevec'.

Cannot add an object with evolution type 'statevec' to a model with one of 'densitymx'

Also, is it possible to add Molmer Sorensen to the basis set of gates so that it can be used for circuit simulations?

Quick answer: you need to insert the line
XX = pygsti.tools.change_basis(XX, 'std', 'pp')
before the final line of your example.
Explanation:
You're getting this error because you're assigning a complex numpy array (see the elements of XX in your code above) to a model operation.  Since pyGSTi uses Hermitian bases for density matrices, it assumes that if you're specifying a super-operator (a map from density matrices to density matrices) as a dense array then this array will be real because a density matrix expressed in a Hermitian basis is a real vector.  Since your array is complex, it interprets it as a unitary operator on (complex) state-vectors as opposed to density matrices - i.e. it has evolution type "statevec".  But model1 in your example has already been setup to represent quantum states as density matrices (evolution type "densitymx"), so it gives you the error you see.
To fix this, you need to convert XX into the Pauli basis - that is, write the action of XX as you have it as the action on a state represented as a length-16 real vector specifying the 2-qubit density matrix as a linear combination of the 16 2-qubit product-of-two-Pauli matrices.  To do this, you can use the change_basis function to move from the "standard" ("std") matrix-unit, basis you've expressed XX in to the "Pauli-product" ("pp") basis the your model expects - that's what the line:
XX = pygsti.tools.change_basis(XX, 'std', 'pp') does.

Thank you for the explanation! Makes sense to me and works now.
As for the second question: when I'm defining the processor specification that I'm trying to benchmark or run any simulation on, XX gate is not one of the standard set of gates. Just like I did for the model building, is it possible to input XX as a basis get for the processor?
As an example, my goal is to do something like this:
#Specify the device to be benchmarked - in this case 2 qubits
nQubits = 2
qubit_labels = [0,1]

Gxx = ...........

gate_names = ['Gx', 'Gy','Gxx']

availability = {'Gxx':[(0,1)]}
pspec = pygsti.obj.ProcessorSpec(nQubits, gate_names, availability=availability,
                                 qubit_labels=qubit_labels)

You should be able to just supply the nonstd_gate_unitaries argument to the ProcessorSpec constructor, which as its name implies, should contain the unitary for your MS gate, not the super operator.  So, using the U1_xx variable from your original post, you can just write:
gate_names = ['Gx', 'Gy','Gxx']
availability = {'Gxx':[(0,1)]}
pspec = pygsti.obj.ProcessorSpec(nQubits, gate_names, availability=availability,
                                 qubit_labels=qubit_labels,
                                 nonstd_gate_unitaries={'Gxx': U1_xx})

That's perfect! Thanks for all the help, Erik!


Allow other identifiers instead of t

import test from 'ava';

test(assert => {
  const actual = true;
  const expected = false;

  assert.ok(actual === expected);
});

yields
 1 failed

  1. [anonymous]
  false == true
  AssertionError: false == true
    Test.fn (index.js:7:10)

instead of the expected
  1 failed

  1. [anonymous]

  assert.ok(actual === expected)
            |          |
            true       false

  AssertionError: false == true
    Test.fn (index.js:7:10)

It seems to be because of the patterns used to configure power-assert in lib/enhance-assert.js. Would it be possible to drop the t. to allow any identifier ?

Just by skimming the power-assert docs I don't really see support for "multiple" patterns at once (like a * operator), but this is a question for @twada.

@Kl0tl Sorry, this is a current limitation of CallExpression matching and intended to propose sensible default variable name for consistency. However it's nice to have some callee pattern matching notation like wildcard. Thanks @sotojuan.

@Kl0tl - Can you explain why you need this? What prevents you from using t?

I think it was just an idea he had—but so far it doesn't seem like it's feasible.

It's feasible, it just isn't really practical (at least not with a wildcard *). You almost certainly don't want any method called same wrapped with power-assert stuff.
We would have to do static analysis for test() calls, and then see what variable name was used as the first parameter, and then build new patterns from that. It's certainly doable, but it involves additional AST analysis - which pretty much guarantees a minimum amount of difficulty.

Nothing prevents me from using t but enforcing this variable name seemed a bit artificial.

Just use t.
Allowing * creates a namespace conflict with outside objects that might have methods with the same name.
We could do static analysis to detect test methods and match the first parameter, but that is going to be unreliable.

Echoing what I said here: https://github.com/avajs/ava/issues/551#issuecomment-226838995
I say we just close this. This would require a lot of effort in power-assert, ava-codemods, and our linter.


dataset download

may I have a cloud pan link to download datasets, hugging face is very difficult to download. Thank you very much.

Hi @YvoGao
Thank for showing interest in our work.
Could you let me know the issues you are facing while downloading the datasets from Huggingface?
At this moment, we do not have cloud link to share.

Thank you for your reply.  I fix the download problem. I find NS-Instruments and VocalSound miss the context in hugging face. So will you put it in cloud pan soon?

We will upload NS-Instruments and VocalSound within one week. I'll post an update here once the dataset upload is complete.

Thank you very much!!!

Hi @YvoGao
NS-Instruments and VocalSound datasets have been uploaded. Please refer to updated instructions o these datasets in DATASETS.md. Please let me know if you face any issue.

Hi @YvoGao NS-Instruments and VocalSound datasets have been uploaded. Please refer to updated instructions o these datasets in DATASETS.md. Please let me know if you face any issue.

In NS-Instruments dataset, there are only five classes:'bass', 'brass', 'flute', 'guitar', 'keyboard', missing another five classes: 'mallet', 'organ', 'reed', 'string', 'vocal']

Hi @YvoGao
Could please confirm if the downloaded NS-Instruments dataset with following commands:
import os
import zipfile
import shutil
import huggingface_hub
audio_datasets_path = "DATASET_PATH/Audio-Datasets"
if not os.path.exists(audio_datasets_path): print(f"Given {audio_datasets_path=} does not exist. Specify a valid path ending with 'Audio-Datasets' folder.")
huggingface_hub.snapshot_download(repo_id="MahiA/NS-Instruments", repo_type="dataset", local_dir=os.path.join(audio_datasets_path, "NS-Instruments"))
zipfile_path = os.path.join(audio_datasets_path, 'NS-Instruments', 'NS-Instruments.zip')
with zipfile.ZipFile(zipfile_path,"r") as zip_ref:
    zip_ref.extractall(os.path.join(audio_datasets_path, 'NS-Instruments'))
shutil.move(os.path.join(audio_datasets_path, 'NS-Instruments','NS-Instruments', 'audios'), os.path.join(audio_datasets_path, 'NS-Instruments'))
shutil.move(os.path.join(audio_datasets_path, 'NS-Instruments','NS-Instruments', 'train.csv'), os.path.join(audio_datasets_path, 'NS-Instruments'))
shutil.move(os.path.join(audio_datasets_path, 'NS-Instruments','NS-Instruments', 'test.csv'), os.path.join(audio_datasets_path, 'NS-Instruments'))
shutil.rmtree(os.path.join(audio_datasets_path, 'NS-Instruments', 'NS-Instruments'))
os.remove(zipfile_path)

yes, we use this.
In hugging face web, we have downloaded the org NS-Instruments.zip, and there are no other five classes.

We are trying to fix the issue and will update soon.

Hi @YvoGao
The issue has been resolved. Please try downloading the dataset again.
The problem occurred due to an incomplete transfer from the compute cluster to the local machine, which resulted in an incomplete dataset being mistakenly uploaded. This has now been corrected.

I hope you are able to download the full dataset. Feel free to reopen the issue if you encounter any issues.


Add setItem Method

Add a method to set Items instead of adding them, since with the current AddItem method, the item cannot be removed. In the case of pagination, I would like the "Previous Page" button not to be displayed on the first page, or the "Next Page" button not be displayed on the last page, but with the AddItem method, it cannot be removed even if you use an if-statement to compare if it is the first page.
Example code:

import mc.obliviate.inventory.Gui;
import mc.obliviate.inventory.Icon;
import mc.obliviate.inventory.pagination.PaginationManager;
import org.bukkit.ChatColor;
import org.bukkit.Material;
import org.bukkit.entity.Player;
import org.bukkit.event.inventory.InventoryOpenEvent;
import org.bukkit.inventory.ItemStack;

public class TestGui extends Gui {

    private final PaginationManager pagination = new PaginationManager(this);

    public TestGui(Player player) {
        super(player, "example-gui", "Title", 6);
    }

    @Override
    public void onOpen(InventoryOpenEvent event){
        this.pagination.registerPageSlotsBetween(0, (4 * 9) - 1);

        for (Material material : Material.values()) {
            this.pagination.addItem(new Icon(material));
        }

        fillRow(getIcon(new ItemStack(Material.STAINED_GLASS_PANE, 1, (short) 15), "&0"), 4);
        Icon nextPage = getIcon(new ItemStack(Material.PAPER), "&eNext Page");
        nextPage.onClick((e) -> {
            this.pagination.update();
            this.pagination.goNextPage();
        });
        Icon previousPage = getIcon(new ItemStack(Material.PAPER), "&ePrevious Page");
        previousPage.onClick((e) -> {
            this.pagination.update();
            this.pagination.goPreviousPage();
        });
        Icon lastPage = getIcon(new ItemStack(Material.BARRIER), "&cLast Page");
        lastPage.onClick((e) -> {
            this.pagination.update();
            this.pagination.goLastPage();
        });
        Icon firstPage = getIcon(new ItemStack(Material.EMERALD), "&aFirst Page");
        firstPage.onClick((e) -> {
            this.pagination.update();
            this.pagination.goFirstPage();
        });

        if(!this.pagination.isLastPage()){
            addItem(this.getLastSlot() - 1, lastPage);
            addItem(this.getLastSlot(), nextPage);
        }
        if(!this.pagination.isFirstPage()){
            addItem(this.getLastSlot() - 7, firstPage);
            addItem(this.getLastSlot() - 8, previousPage);
        }
        this.pagination.update();
    }

    private Icon getIcon(ItemStack itemStack, String name){
        return new Icon(itemStack).setName(ChatColor.translateAlternateColorCodes('&', name));
    }
}

Pagination module only affects the pagination slots. The visibility of navigation icons is in your responsbility because they're coded by you. You can override items using addItem method, so addItem(1, null) should work. However a lot of people confuses about it. I think I should write a wiki page for pagination navigations.
To fix this issue, create and use your own update method that tracks your visibility of navigation buttons and calls pagination manager's update method.

Pagination module only affects the pagination slots. The visibility of navigation icons is in your responsbility because they're coded by you. You can override items using addItem method, so addItem(1, null) should work. However a lot of people confuses about it. I think I should write a wiki page for pagination navigations.
To fix this issue, create and use your own update method that tracks your visibility of navigation buttons and calls pagination manager's update method.

Oh, I see, thank you


[6.0 🍒][Test Only] Make CachingBuildTests.testDependencyScanning be adaptable to scanner diagnostic revisions

Instead of throwing a failure, a scan may return a hollow result carrying diagnostic error payload

@swift-ci test


Fix OWASP failures.

force uplift log4j to 2.17.1
force uplift thymeleaf to 3.0.14.RELEASE

Ran locally:
`» ./gradlew dependencyCheckAnalyze

Task :dependencyCheckAnalyze
Verifying dependencies for project manage-recalls-api
Checking for updates and analyzing dependencies for vulnerabilities
Generating report for project manage-recalls-api
Found 0 vulnerabilities in project manage-recalls-api

BUILD SUCCESSFUL in 11s
1 actionable task: 1 executed
`


Handle posting networkPolicy objects

Does this gem support creating network policy objects in this style for example?
I can do it with kubeclient...
apiVersion: extensions/v1beta1
kind: NetworkPolicy
metadata:
 name: standard-ingress-policy
 namespace: fd5ce1e9481667af26bf6a78697d8ccf4fe2d172
spec:
  podSelector:
  ingress:
    - from:
        - namespaceSelector:
            matchLabels:
                tier: frontend

Need to be able to craft these programmatically and apply at namespace creation time.

@moolitayer Maybe I can do this now with the way you've got things set up... would this be a difficult addition to the gem?

@moolitayer Maybe I can do this now with the way you've got things set up... would this be a difficult addition to the gem?

@andrewkrug I think the support should be there already (given that we discover the entities automatically now).

@simon3z any chance you could point me in the right direction of some documentation on that?

@simon3z any chance you could point me in the right direction of some documentation on that?

I expect @moolitayer will answer your questions with the details (meanwhile you could try to learn the examples and guess how it should work for network policies).

Getting network policies on my local server:
client = Kubeclient::Client.new('http://localhost:8080/apis/extensions' , 'v1beta1', ssl_options: { verify_ssl: 0 })
client.get_network_policies

Posting should work similarly.

@andrewkrug did this work for you?  Can this be closed?

[closing old inactive question issues.  feel free to reopen/open a new one.]


The latest version doesn't work on Windows

Hello,
With Python 2.7.16 on Windows the following code
from accumulation_tree import AccumulationTree
t = AccumulationTree(lambda x: x)
t.insert(1, 1)

fails with this error:
Traceback (most recent call last):
  File "D:\app\scripts\--TMP--\test.py", line 3, in <module>
    t.insert(1, 1)
  File "accumulation_tree\\accumulation_tree.pyx", line 233, in accumulation_tree.accumulation_tree._AccumulationTree.insert
TypeError: unbound method cython_function_or_method object must be called with RBTree instance as first argument (got AccumulationTree instance instead)

On macOS, it works fine with the same Python version.

Thanks for reporting the issue @alexey-stankevich . Is this something you can reproduce with a supported version of python?

It does work with python 3.8.3 and doesn't work with python 2.7.18.

It seems I've found the issue. For some reason files in tar.gz don't have modification time, and Windows set it to 01/01/1970. This triggers weird python behavior when trying to build a wheel.
When I changed timestamps, the issue disappeared.

Wow, that's very odd. Thanks for finding the issue and documenting it here!


Create a VisualStudio parser to handle the editing loop.

Renamed RazorEditorParser => VisualStudioRazorParser
Tried to make as little changes as possible to the BackgroundParser due to its complexity; mostly just removed the TreeStructureChanged logic since this is re-done on the Razor editor side of things.
Split the RazorEditorParserTests into two separate tests. Partial parser tests and the VS parsing tests.
Updated StringTextSnapshot to support changes in order to test the VS parser.

#1536

🆙 📅
Ran this through the WTE tests and the pieces that are missing right now are brace completion and formatting. I need to meet with Todd/Alex to find out why formatting fell off.

Let's make the new stuff internal until it's ready

:shipit:


Golden file test failure closing tree

On the Engine roll here https://github.com/flutter/flutter/pull/100244, I accepted the diffs, the presubmit check went green, but it looks like something went wrong and the diffs are still getting flagged in post submit, closing the tree:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux web_tests_7_last/3935/overview
I need an adult. @Piinks @mdebbar

I should also note that I followed the instructions in the failure logs, clicked through the link to SkiaPerf there, accepted the diff again, and tried a re-run, and that re-run also failed on the diff.

We have had a similar issue yesterday on the flutter/engine repo. Images are triaged in the PR, then post-submit runs, but images don't make it to Gold. So Gold keeps thinking they are untriaged.
I spoke with @kjlubick who recommended the following fix: https://github.com/flutter/engine/pull/32071
But it looks like that didn't work either. Here are the post-submit logs for the above PR. The goldctl exception is gone, but the images still didn't make it to Gold.

Thanks @kjlubick!
From our discussion offline, @kjlubick identified the issue on Gold's side, and expects it'll take a few days to fix.
In the meantime, I think we have 2 options:
1. Disable Gold checks:
Stop checking golden changes. This means we will be accepting all changes without triage, and we'll be flying blind.
2. Block golden changes:
Prevent any golden changes from going in. This means we'll probably delay a lot of work and we may need to disable the rollers.
@Piinks what do you think?

Filed https://github.com/flutter/flutter/issues/100304 if previous comment sounds good with everyone else, I am preparing a PR to disable the post submit failure now.

That's a good plan Kate. Thanks for owning the monitoring.

We also need to manually re-triage all golden changes once they land in master, right?

I don't think so.
@kjlubick can correct me if I am wrong, but it looks like the images are triaged, the test is just coming back as a failure. The dashboard currently shows there are no images in need of approval https://flutter-gold.skia.org/
If the fix on Gold's end means we need to update a few images then I think we can manage that.
We currently manage all of our image approval in pre-submit, so I am pretty confident disabling post-submit failures will be fine. We only recently enabled it in https://github.com/flutter/flutter/pull/93516 to better identify when something has gone wrong. So it kinda worked as expected! :)

Tree is green.

This is happening again:

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8819409321084715617/+/u/run_test.dart_for_web_tests_shard_and_subshard_7_last/test_stdout
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8819412057180872097/+/u/run_test.dart_for_web_tests_shard_and_subshard_7_last/test_stdout

https://github.com/flutter/flutter/pull/100332 should disable this for good until we can find out where Gold is broken. It looks like the tree went green, and then more image changes were made that again were not ingested properly.


Added new container parameter installed_plugins

Description

Questions
Answers

Why?
Easier handle to dependency plugins

BC breaks?
no

Tests exists & pass?
yes

Related tickets?

How to test?
See below

Requirements met?
Yes

public function build(ContainerBuilder $container)
    {
        if (in_array('SwagPaymentPaypal', $container->getParameter('installed_plugins'))) {
            $container->addCompilerPass(new PaypalExtensions());
        }
        parent::build($container);
    }

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-18654.
Please use this issue to track the state of your pull request.

thanks @shyim :+1:


Add DefaultHostsFileEntriesResolver#addresses to provide all hosts file's entries for a hostname

Motivation:
DefaultHostsFileEntriesResolver should provide all hosts file's entries for a hostname when
DnsNameResolver#resolveAll as opposed to the current implementation where only the first
entry is taken into consideration.
Modification:

Add DefaultHostsFileEntriesResolver#addresses to provide all hosts file's entries for a hostname
Add HostsFileEntriesProvider to provide all hosts file's entries for a hostname and to keep
backwards compatibility for HostsFileEntries and HostsFileParser
DnsNameResolver#resolveAll uses the new DefaultHostsFileEntriesResolver#addresses
BlockHound configuration: replace HostsFileParser#parse with HostsFileEntriesProvider$ParserImpl#parse
as the latter does the parsing
Add junit tests

Result:
Fixes #10834

@normanmaurer How can I find the test that is not passing the build on CI?

@violetagg it failed due some network problems:
2021-05-11T18:51:11.3115666Z [INFO] ------------------------------------------------------------------------
2021-05-11T18:51:11.3116421Z [INFO] BUILD FAILURE
2021-05-11T18:51:11.3117366Z [INFO] ------------------------------------------------------------------------
2021-05-11T18:51:11.3118128Z [INFO] Total time:  20:49 min
2021-05-11T18:51:11.3118926Z [INFO] Finished at: 2021-05-11T18:51:11Z
2021-05-11T18:51:11.3119884Z [INFO] ------------------------------------------------------------------------
2021-05-11T18:51:11.3125549Z [ERROR] Failed to execute goal on project netty-codec-dns: Could not resolve dependencies for project io.netty:netty-codec-dns:jar:4.1.64.Final-SNAPSHOT: The following artifacts could not be resolved: org.apache.directory.server:apacheds-core:jar:1.5.7, org.apache.directory.server:apacheds-core-api:jar:1.5.7: Could not transfer artifact org.apache.directory.server:apacheds-core:jar:1.5.7 from/to central (https://repo.maven.apache.org/maven2): transfer failed for https://repo.maven.apache.org/maven2/org/apache/directory/server/apacheds-core/1.5.7/apacheds-core-1.5.7.jar: Connection timed out (Read failed) -> [Help 1]
2021-05-11T18:51:11.3129407Z [ERROR]
2021-05-11T18:51:11.3130408Z [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
2021-05-11T18:51:11.3131587Z [ERROR] Re-run Maven using the -X switch to enable full debug logging.
2021-05-11T18:51:11.3132323Z [ERROR]
2021-05-11T18:51:11.3133240Z [ERROR] For more information about the errors and possible solutions, please read the following articles:
2021-05-11T18:51:11.3134751Z [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
2021-05-11T18:51:11.3135857Z [ERROR]
2021-05-11T18:51:11.3136650Z [ERROR] After correcting the problems, you can resume the build with the command
2021-05-11T18:51:11.3137718Z [ERROR]   mvn <args> -rf :netty-codec-dns
2021-05-11T18:51:11.4706176Z 1

/cc @NiteshKant can you check as well ?

@normanmaurer @NiteshKant Thanks a lot!

@violetagg I need to investigate... with this change I see a test-failure in servicetalk... It seems to return the IPV6 address for localhost when we expect the IPV4. I need to investigate if the problem is with the test or the change here that it may return the IPV6 as first when we want the IPV4.

@violetagg I need to investigate... with this change I see a test-failure in servicetalk... It seems to return the IPV6 address for localhost when we expect the IPV4. I need to investigate if the problem is with the test or the change here that it may return the IPV6 as first when we want the IPV4.

if I can help just tell me ...

@violetagg all good... I debugged a bit with the team and we are ok from a netty side..

@violetagg all good... I debugged a bit with the team and we are ok from a netty side..

That's good. Thanks


Grouped Row shows 'undefined'

I just upgraded to lastest ngGrid, but all my grouped rows in powergrid show 'undefined' at each column

Any news on this issue?


examples: remove multipart example

Closes #5193

Awesome, thank you! Would you mind also removing the reference to it from the examples/README.md file?

The reference to multipart in README.md has been removed 👍


multiple-cs, multiple-go, and multiple-d are broken (FileNotFound)

I wonder if this might just be user error on my end. Is there a step for installing compilers like csc that I skipped over before running bigcode_eval?
Run log / full outputs here: https://gist.github.com/alat-rights/705edc6d3aae51db7c871afa153cc3a5
FileNotFoundError: [Errno 2] No such file or directory: 'csc'

Code point
System Information
Ubuntu Linux
Lambda Labs Instance: 1x A10 (24 GB PCIe) (30 CPU cores, 205.4 GB RAM, 1.5 TB SSD)

Here are logged failures for multiple-go and multiple-d: https://gist.github.com/alat-rights/1e0092cd9ccba9adc4057c4fa309948e

Closed, was just missing dependencies, sorry.


Open related tab at end of tab list

While I understand this extension was born from a specific need useful for some, lot-of-confusing and counter-productive for others, I hereby make a feature request that would make it a more general purpose extension:
Chrome, by default, opens a new empty tab at the end of the tab bar. (using Ctrl-T or + button). This extension changes that behaviour to the opposite - open the new tab next to the current one.
The feature request is either for this becoming a general purpose extension regarding how new tabs are opened (configurable), or a dedicated separate extension.
Chrome, when right-click -> open_new_tab is requested, opens a new tab, by default, next to the current tab. For some people this is counter-productive and would desire the new tab to be opened at the end of the tab list.
Thank you.

Hello, I understand your request but this is not the goal of this extension: it handle the "new tab" event an try to create the new new after the active one.
There is a lot of others extensions that handles tabs and maybe answers your request.


OLS-624: Tag for attachments tests

Description
Tag for attachments tests
Currently integration tests are a bit slow, so it is good to have the ability to select (or deselect) group of them based on marks. New mark is used for tests that sends (any) attachment to tested OLS service via mocked REST API.
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)
[x] Integration tests

Related Tickets & Documents

Related Issue #OLS-624
Closes #

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.36%. Comparing base (0322da5) to head (631f30b).
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1072   +/-   ##
=======================================
  Coverage   95.36%   95.36%
=======================================
  Files          55       55
  Lines        2353     2353
=======================================
  Hits         2244     2244
  Misses        109      109

see 2 files with indirect coverage changes

/lgtm

/approve

/retest

/retest

/override ci/prow/e2e-ols-cluster

/override ci/prow/e2e-ols-cluster

@tisnik you overrode because of the BAM failures which don't seem OLS related?

/override ci/prow/e2e-ols-cluster

@tisnik you overrode because of the BAM failures which don't seem OLS related?

the CI is unstable for the last 2 hours (at least), and yes, it is unrelated


enable falcon-180b inference

1 The current code can load only .bin or .pt whereas Falcon-180B ckpt files are in .safetensors format. This change enabled loading ckpt files in .safetensor format
2 The ValueError "The following model_kwargs are not used by the model: ['token_type_ids'] )" is addressed by introducing a workaround that removes ‘token_type_ids’ from the model_kwargs.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

@schoi-habana Merging this PR. Please follow guidelines below when propagating this change to huggingface/optimum-habana

Maintain  1:1 mapping between PRs on OH-fork & OH (=> every PR on OH-fork should have only 1 corresponding PR on OH).  Use exactly same commit message for PR done on OH-fork and corresponding PR on OH! However content of PR going to OH can change (e.g. changes based on review comments).
Do not propagate any changes done to final PR going into OH back to OH-fork (makes OH-fork rebases messy and error prone)! We will anyway pick your finalized content (that went to OH) in next rebase.
If you do need to violate above rule (exception cases). Please sync with me.

https://github.com/huggingface/optimum-habana/pull/773


DO NOT REVIEW - copy of https://github.com/grpc/grpc/pull/17110

attn: @billfeng327
DO NOT REVIEW
this is a copy of https://github.com/grpc/grpc/pull/17110 to help @billfeng327 debug the current issues with multipool config.
Sample passing run:
https://source.cloud.google.com/results/invocations/1162dee4-c602-424c-9327-d562371f4865
toolchain / Platform flags I used:
--crosstool_top=@com_github_bazelbuild_bazeltoolchains//configs/debian8_clang/0.4.0/bazel_0.16.1/default:toolchain
--extra_execution_platforms=//third_party/toolchains:rbe_ubuntu1604,//third_party/toolchains:rbe_ubuntu1604_large
--host_platform=//third_party/toolchains:rbe_ubuntu1604
--platforms=//third_party/toolchains:rbe_ubuntu1604,//third_party/toolchains:rbe_ubuntu1604_large
--extra_toolchains=@com_github_bazelbuild_bazeltoolchains//configs/ubuntu16_04_clang/1.1/bazel_0.16.1/cpp:cc-toolchain-clang-x86_64-default

I honestly don't know what is wrong in your PR, or how you are running this as the only difference I can see now is in the extra properties (which I cannot have as I don't have pools with those properties set) and the fact that I'm using bazel 0.19.0 (you might be using an older version?)

@nlopezgi   someone from gRPC team needs to add "kokoro:run" label to get a test run. I did so just now, @billfeng327  can do that for next runs you'll need.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

Corrupt JSON data (indicates timeout or crash):
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.new: 10
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.old: 10

[microbenchmarks] No significant performance differences


feat: Adds -g / --glob flag for restricting matches to glob patterns.

Addresses a shared feature request here
Introduces a new flag, -g/--glob for restricting searches to supplied glob patterns.
Adds unit tests to evaluate output when in glob search mode.

✅ Remove the first argument any in all of your tests/args_test.go cases
✅ Remove the if arg == "any" condition added to src/args.go
✅ Updated README with new flags / usage examples
Have a peek & lemme know if anything else needs attending-to.

Thank you so much! Works for me!


Sink generates log urls for pods

Which Issue(s) this Pull Request Resolves

Resolves #538
Release Note

sink generates log urls for pods

Notes for Reviewers

These are some of the changes made to enable logging in the sink

add database interface method to return SQL query to delete rows in the log_url table based on uuid
add database interface method to return SQL query to add add rows to the log_url table
add database method that deletes all rows that have the same uuid as the kubernetes object passed to it and then write all urls passed to it to the database.
update fake database test type to support the write and delete operations added
refactored some code in cmd/sink/main.go make it easier to write log urls to the database in the right places

I am testing with:
bash test/log-generators/cronjobs/install.sh --num-jobs=10
cat <<EOF | kubectl apply -f -
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: kubearchive-splunk
  namespace: kubearchive
data:
  POD_ID: cel:metadata.uid
  CONTAINER_NAME: cel:spec.containers.map(m, m.name)
  POD: 'spath "kubernetes.pod_id" | search "kubernetes.pod_id"="{POD_ID}"'
  CONTAINER: 'spath "kubernetes.container_name" | search "kubernetes.container_name"="{CONTAINER_NAME}"'
  LOG_URL: http://<IP_ADDRESS>:8111/app/search/search?q=search * | {POD} | {CONTAINER}
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: kubearchive-config
  namespace: kubearchive
data:
  logging: |
    configMapRef: splunk-logging
EOF
kubectl exec -i -n postgresql pods/kubearchive-1 -- psql kubearchive -c "SELECT * FROM log_url;" | tail

The count increases but I'm not getting any URL. Following my own suggestions, I see this one the warns:
2024/10/29 10:14:13 WARN logging information does not exist key=logging-configmap-name keys=[logging]

So logging-configmap-name is what the logging configuration option should be called?
PD: the configMaps are from https://kubearchive.github.io/kubearchive/main/integrations/logging.html

I had been following what was described here https://kubearchive.github.io/kubearchive/main/design/logging-integration.html#_configuration
I think we need @ggallen to help sort this out

Please add the documentation that tells admins they have to manually rollout for the changes to take effect.

updated the documentation

I think we need @ggallen to help sort this out

That's an illegal ConfigMap as @skoved pointed out.  The documentation incorrect. I'm not sure what I was thinking.

rebased the branch so I can merge this


Arm64 Apple Darwin CI test failures

This issue is a place to track failures that occur with AMD64 Apple Darwin tests that are unrelated to changes that were being tested. There's something amiss either in CI setup or an intermittent bug (or bugs) on Arm64 Apple Darwin.

The following "ponyc-runner" tests failed with a timeout:
[  FAILED  ]
12 test(s), listed below:
[  FAILED  ]
annotation-methods
[  FAILED  ]
regression-3840
[  FAILED  ]
array-infer-from-values-call-with-iterator-antecedent
[  FAILED  ]
bare-function-bare-lambda-callback
[  FAILED  ]
array-infer-from-array-type
[  FAILED  ]
identity-digestof-boxed-tuple
[  FAILED  ]
with-in-loop-with-continue
[  FAILED  ]
c-callback
[  FAILED  ]
iftype-false
[  FAILED  ]
class-final
[  FAILED  ]
regression-3615
[  FAILED  ]
identity-boxed-numeric-is-boxed-numeric

Note they were all run around the same time and then everything else passed again. Perhaps a pause in CPU availability in the CI environment that caused them all the fail.

I've attached the complete log as well.
release_test.log.txt

I saw the same timeouts on #4124

Similar timeout failures clumped together in #4146:
[ RUN      ] identity-tuple-is-boxed-tuple
[  FAILED  ] identity-tuple-is-boxed-tuple (60011 ms): timed out after 60 seconds
[ RUN      ] array-infer-from-apply-interface-box-element-in-tuple
[  FAILED  ] array-infer-from-apply-interface-box-element-in-tuple (60001 ms): timed out after 60 seconds
[ RUN      ] actor-final
[  FAILED  ] actor-final (60002 ms): timed out after 60 seconds
[ RUN      ] iftype-else-if-true
[  FAILED  ] iftype-else-if-true (60012 ms): timed out after 60 seconds
[ RUN      ] iftype-true
[  FAILED  ] iftype-true (60034 ms): timed out after 60 seconds
[ RUN      ] while-else-trigger-else-clause
[  FAILED  ] while-else-trigger-else-clause (60005 ms): timed out after 60 seconds
[ RUN      ] small-finalisers
[  FAILED  ] small-finalisers (60010 ms): timed out after 60 seconds
[ RUN      ] codegen-trace-struct-field
[  FAILED  ] codegen-trace-struct-field (60006 ms): timed out after 60 seconds
[ RUN      ] identity-abstract-type-no-subtyping
[  FAILED  ] identity-abstract-type-no-subtyping (60010 ms): timed out after 60 seconds
[ RUN      ] lambda-with-return-in-behaviour
[  FAILED  ] lambda-with-return-in-behaviour (60002 ms): timed out after 60 seconds
[ RUN      ] identity-digestof-object
[  FAILED  ] identity-digestof-object (60014 ms): timed out after 60 seconds

Failures from PR #4150
[  FAILED  ]
12 test(s), listed below:
[  FAILED  ] regression-2408
[  FAILED  ] match-exhaustive-all-cases-including-dont-care-and-tuple
[  FAILED  ] custom-serialisation
[  FAILED  ] array-infer-from-values-of-array-interface
[  FAILED  ] regression-849
[  FAILED  ] try-then-clause-break
[  FAILED  ] codegen-trace-number-boxed
[  FAILED  ] array-infer-most-specific-from-union-of-array-types
[  FAILED  ] primitive-init
[  FAILED  ] array-infer-from-seq
[  FAILED  ] codegen-trace-tuple-boxed-sent-through-interface
[  FAILED  ] try-else-can-initialize-fields
make: *** [test-full-programs-debug] Error 1
Exit status: 2

Failures from #4149
[ RUN      ] codegen-trace-number-boxed-sent-through-interface
[  FAILED  ] codegen-trace-number-boxed-sent-through-interface (60002 ms): timed out after 60 seconds
[ RUN      ] ffi-return-arg-reachable
[  FAILED  ] ffi-return-arg-reachable (60011 ms): timed out after 60 seconds
[ RUN      ] bare-function-call
[  FAILED  ] bare-function-call (60037 ms): timed out after 60 seconds
[ RUN      ] regression-3447
[  FAILED  ] regression-3447 (60010 ms): timed out after 60 seconds
[ RUN      ] codegen-trace-tuple-boxed
[  FAILED  ] codegen-trace-tuple-boxed (59984 ms): timed out after 60 seconds
[ RUN      ] try-then-clause-continue
[  FAILED  ] try-then-clause-continue (60018 ms): timed out after 60 seconds
[ RUN      ] array-infer-from-array-val
[  FAILED  ] array-infer-from-array-val (60008 ms): timed out after 60 seconds
[ RUN      ] codegen-trace-object-dynamic
[  FAILED  ] codegen-trace-object-dynamic (60001 ms): timed out after 60 seconds
[ RUN      ] if-block-ending-with-dont-care-assign
[  FAILED  ] if-block-ending-with-dont-care-assign (60029 ms): timed out after 60 seconds
[ RUN      ] array-no-as-iso-consumed-elements
[  FAILED  ] array-no-as-iso-consumed-elements (60013 ms): timed out after 60 seconds
[ RUN      ] identity-tuple-cardinality
[  FAILED  ] identity-tuple-cardinality (60023 ms): timed out after 60 seconds
[ RUN      ] object-literal-with-return-in-behaviour
[  FAILED  ] object-literal-with-return-in-behaviour (60005 ms): timed out after 60 seconds

Aside from https://github.com/ponylang/ponyc/issues/4138#issuecomment-1167699736, I am convinced that this is environmental; a vm losing CPU access. However https://github.com/ponylang/ponyc/issues/4138#issuecomment-1167699736 gives me pause and wondering if that is entirely true. I'm still believing that this is environmentally though.

At sync we discussed a bit more and decided that https://github.com/ponylang/ponyc/issues/4138#issuecomment-1167699736 is probably also environmental where a pause of almost 60 seconds would explain the failures.
There's no much we can do for this but track for now and let Cirrus know what we are seeing.

What do you mean CPU access? Like a VM freezes? Then all of the process should've been paused I think.
Also do you mind providing links to Cirrus tasks. I have hard time figuring them out from the PR links. Seems some other failures were on Arm Linux instances as well.

@fkorotkov it would appear that some tests are started and then all of them that are running time out. The only thing looking at when and how this happens is that everything executing stops and when starting again, all of or most of the timeout has passed. Given the weird little batches it appears in, it feels like the vm stops running. I don't know the particulars of the architecture but this feels like when vms are overprovisioned and every now and then don't have access to the CPU. I doubt that is the architecture here but it definitely looks like it.
I don't have specific logs but could go digging some up based on looking at the PRs linked above, finding the branch name for the PR and combing through the different runs looking for the specific failures.

@fkorotkov these are all Apple silicon failures. I haven't seen anything like this in any other test environments and yes, this looks like the entire vm froze and when it came back, the timeout had passed and the test runner that started again timed out all of the tests that were running when the freeze occurred.
I suspect if we turned off timeouts for Apple arm that these failures would go away as the tests would pass. However that would be problematic for the scenario where a problem was introduced.
All in all, this is a minor annoyance to us and can be easily distinguished from "real failures" so I'm not concerned for us, but in thought you'd be interested in the report given it's a new platform and tech for you.

@fkorotkov it would appear that via the UI, once we do "rerun failure" that there's no way in the UI to get the given run that failed.

This is no longer occurring. So I'm closing for now.


Multiple Y axis

Is there a way to implement 2 Y axis on both sides?

Hi @froz3nice , currently no, and i dont think so I intend to implement this feature, bacause it seems rarely needed.
But you can put chart in the row/column and build your own labels or indicators in both sides of chart.


add callables for airflow connection handling

adds python callables for programmatically CRUD-ing airflow connections

closing, merged to rc/0.3.0 branch


feat: list files by git when possible

Although we try to use ignore pattern present by a .gitignore file, it's possible that users have a global git ignore settings or manually ignore a file.
We can use git command to list files when runs under a git worksapce, and if there's no git workspace, we don't have to see .gitignore. Normally, it's via directly download and all ignored files already excluded. If users want to respect to the ignore pattern, they can simply git init.
cc @kezhenxu94 @wu-sheng @fgksgf @spacewander
Reference:

https://github.com/apache/skywalking/issues/7543
https://github.com/apache/skywalking/issues/7538

Although we try to use ignore pattern present by a .gitignore file, it's possible that users have a global git ignore settings or manually ignore a file.
We can use git command to list files when runs under a git worksapce,

This is a good idea, but it looks like the implementation in this PR only lists files that have been committed into the codebase, however, in most cases, I'm using the tool in the following workflow:

In a git repo, checkout a new branch.
Do modifications, for example, touch a-new-file.yaml.
... many other new files.
license-eye h f to fix all files that are missing license headers.
git add . && git commit -m'...'.

In this PR, nothing will be fixed, even if I run license-eye h f after git add ..
This also breaks users who used this tool as a git pre-commit hook.

@kezhenxu94 good point. Let me try to find a way to list staged/unstaged files.

@kezhenxu94 fixed at https://github.com/apache/skywalking-eyes/pull/133/commits/18af4c46d588d211d2983861689b7e7117376777.

This patch fixes my case under incubator-kvrocks:
➜  incubator-kvrocks git: ~/Brittani/skywalking-eyes/bin/darwin/license-eye -c tools/ci/licenserc.yml header check
INFO Loading configuration from file: tools/ci/licenserc.yml
INFO Totally checked 250 files, valid: 212, invalid: 0, ignored: 38, fixed: 0
➜  incubator-kvrocks git: ~/go/bin/license-eye -c tools/ci/licenserc.yml header check
INFO Loading configuration from file: tools/ci/licenserc.yml
INFO Totally checked 4279 files, valid: 212, invalid: 2045, ignored: 2022, fixed: 0
INFO GITHUB_TOKEN is not set, license-eye won't comment on the pull request
ERROR the following files don't have a valid license header:
cmake-build-debug/_deps/gtest-src/googletest/scripts/test/Makefile
cmake-build-debug/_deps/luajit-src/src/Makefile
...
cmake-build-debug/_deps/lz4-src/contrib/snap/snapcraft.yaml
ERROR one or more files does not have a valid license header

... where:
cat $(git config --global core.excludesFile)
# JetBrains
.idea
*.iml
cmake-build-*

# VS Code
.vscode

# macOS
.DS_Store

# Ruby
.ruby-version

I'll try to dig it out a bit :)

@kezhenxu94 I think we can handle the returned FileStatus. Previously, I assume that all ignored files don't occur in the status list, but it seems not true :)

@kezhenxu94 it's a go-git wart. Workaround at 2687d4ee5f20e4589a79367536196485176be3be.
There're still some issues about .gitignore files in nested path https://github.com/go-git/go-git/pull/522. But previously we also only handle the gitignore file at root path of the repo. If someone else asks for it, they can nudge the upstream fix or switch to a patching mod replacement. I'll leave it as is for now.

This patch fixes my case

I spot that it's about another issue on the master branch. I'll create an issue for it.

it doesn't expand the tilde (~) for the core.excludesfile

I dug the code a bit. Finally, I notice that it's the Golang stdlib that causes the issue:
func main() {
	_, err := os.OpenFile("~/.gitignore", 0, 0666)
	fmt.Printf("%v", err)
}

// open ~/.gitignore: no such file or directory

Setup a cross-reference to https://github.com/go-git/go-git/issues/578. If upstream resolves this issue, we can upgrade to fix the ~ in path issue.


Bug: events are propagating outside of the carousel

Hi,
Firstly, thanks for this very nice component :)
I'd like to have input range inside draggable carousel. But it's impossible to use these inputs because on drag carousel moves to previous / next slide. Can I somehow control when to swipe carousel or not? Disabling drag functionality for carousel is not an option for me, unfortunately.
jsfiddle
Thanks for any help :)

As mentioned in #418, it seems this is also happening for most other events in the carousel

Hi, I'm trying to figure out something related to event propagation too.
If dragging and releasing on an anchor tag in slide item the anchors default behaviour remains.
Expected behaviour would in my eyes be that any child event with mousedown before dragstart and mouseup after the dragstart would be preventDefault:ed, at least if mouseup is between dragstart and dragend.
Current behaviour isn't good anyway.
I've tried setting a data-value on component with slider and pass that as property into an anchor component where I consider the passed property and tries preventDefault:ing on the click event.
The problem is probably that the events I can listen on isn't actually one that is telling me if a drag is started, active or finished.
Have you any idea on how I can fix this or do you have any idea on how to provide the event callbacks? ;)

I'm with you @jonascarlbaum. Unfortunately this library is unusable for me.  The cards contain a link to the product. On mobile, when dragging the carousel the links are getting clicked and navigating away.
Additionally I am noticing that while dragging, the native window scroll still takes place as well, which makes it very award to use. Expected behavior for me would be that most (all) events are prevented from occurring while the user is dragging.
Slick Carousel seems to have figured this out. I was trying to look through their code to see if there was quick way to use the same strategy, but I couldn't figure it out.
Anyone have any advice on this?

I'm with you @jonascarlbaum. Unfortunately this library is unusable for me.  The cards contain a link to the product. On mobile, when dragging the carousel the links are getting clicked and navigating away.
Additionally I am noticing that while dragging, the native window scroll still takes place as well, which makes it very award to use. Expected behavior for me would be that most (all) events are prevented from occurring while the user is dragging.
Slick Carousel seems to have figured this out. I was trying to look through their code to see if there was quick way to use the same strategy, but I couldn't figure it out.
Anyone have any advice on this?

I don’t have the code in front of me, but I either turned mouse drag of with some property or used some device width check in JS and toggle some data to change some property... Not completely tested on mobile yet though...


Make click on version to not copy to clipboard but go to github

Reviewing #722 an idea came to mind
https://github.com/dandi/dandiarchive/tree/0.1.0-421-g609c077 works just fine ;)  so URL could be easily constructed from the exact commit or current git describe which is sweet.
copy pasting could be done via regular select/copy, but getting to github requires "knowledge"

I had the same thought, in a way. I clicked on the version string expecting to be taken to GitHub and felt a sense of disappointment that it only copied the URL to the clipboard.
I'll do this as a followup to #722.

Great (when) users think alike! ;-)


Wildcard Issue

results in this

It does not seem to be loading the text file, or it will load in the last text file in the chain and cannot replace correctly?

Prompt: "_color_ color, _costume_ expression, detailed skin"
Console Result: " expression, detailed skinme" (without the quotes, notice the leading space)
The full prompt results in this output:

I have produced a node structure highlighting the degradation of the prompt line by line:

Attached to this is the .json so that you can drag it onto ComfyUI without having to set all of this up yourself.
workflow (22).zip

Probably an issue with the regrx replacement. Thanks for the workflow and console logs.

I did discover that breaking the noodles onto their own lines did the expected results, but it really takes up a lot of room.

I did discover that breaking the noodles onto their own lines did the expected results, but it really takes up a lot of room.

That's... kinda odd. I think it's cause I thought I was clever and going to use regex which should be faster at finding things in a string, but failed to realize how this specifically works in Python (it does seem a bit different than regular expression parsers I've used in say PHP/Java)
Maybe I should just rewrite it like the NSP parser.

As a side note, the layout gets borked when you load it into ComfyUI.
That might be a ComfyUI issue, though. Try it and see if you get the same problem.

NSP is what most the wildcard default files are based on. They converted my project to individual files instead of a JSON database (for easier editing, instead of designing a webui interface to load database and add/remove/view).
So it contains most everything you're already using, though may be named differently: https://github.com/WASasquatch/noodle-soup-prompts/wiki/Terminology-Reference

A patch is in for the input replacement.

New method for loading wildcards: https://github.com/WASasquatch/was-node-suite-comfyui/tree/main/workflows#wildcards-from-load-text-file-dictionary
(Same Workflow from link)

This should be a lot more flexible.

Just an FYI:

My fix:

It should now be just using os.path.join(WAS_SUITE_ROOT, 'nsp_pantry.json') Hasn't been updated for colab support or downloading directly


Implement Weather API to change board condition based on time of day

Implemented weather api and displays grid skin based on user input


The combat cursor needs to be replaced

Apparently had to get jumped by half of #deckhjand-general before I budged

too bright
not "round enough"

I don't know what either of these mean but the combat cursors need to be replaced apparently

Fixed in #280