Fix container transform

Description
Container builder was incorrectly looking for a non-existent 'matrix4' value from the map. Changed to 'transform' to match schema.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[ ] I read the Code Style Guide and followed the process outlined there for submitting PRs.
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (flutter analyze or dart analyze) does not report any problems on my PR.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I am authorized to release this code under the MIT License and agree to do so

UI Change
Does your PR affect any UI screens?

[ ] Yes, the relevant screens are included below.
[x] No, there are no UI impacts with this PR.

Thanks!  I merged and deployed this so it's available on pub now if you happen to need it.


mb

When creating a new PR, please do the following and delete this template text:

Reference the issue number if there is one:
Fixes #Issue_Number

The "Fixes #nnn" syntax in the PR description causes
GitHub to automatically close the issue when this PR is merged.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: franciucCosmina sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


official website css error

In https://openswoole.com/docs the [Document] section can not display.

Fixed


--json parameter should allow saving to a file

I am trying to integrate into our CI (TeamCity) however jest's --json file output is just dumped with it's standard console ouput. It means we need to do some extra steps to extract the output json from the result.
Jest should either provide configuration option to save the json file or take it as args
e.g.
jest --json=result.json

I think this is a reasonable request. Do you want to send a pull request with tests for this? :) See the integration_tests folder on how to add tests to test jest.

Hi,
what do you think about my approach?
https://github.com/ntwcklng/jest/commit/99493b6404900fa7c2c17b0f360d64df04c4ac24
It uses the fs.createWriteStream to create a File with the specified name in the new CLI option --jsonOutputFile="fileName.json"

Hey! Please send a Pull Request for this. I think using fs.writeFileSync(filename, JSON.stringify(data)) should work just as well for this :)


Game Crashes when loading up a world with ranged spiders feature disabled

Dungeons Mobs Version: 1.0.10
Forge Version: 36.2.2
Minecraft Version: 1.16.5
Crash Report: https://gist.github.com/NJL5390/6634e6dacaaaed34ac0894fba2e31829
I Found this issue while testing for one of the other issues: (https://github.com/Thelnfamous1/Dungeons-Mobs/issues/22). Whenever I load up a world with ranged spiders disabled the game just crashes with this crash report. If I re-enable the ranged spiders feature then everything works normally and the game doesn't crash. But the ranged spiders feature itself doesn't seem to work anyway because of the issue mentioned earlier.
I don't know if these two issues are related or not but this crash never used to happen in older versions so I doubt it.

Ah, I can fix this easily, simple mistake.

No longer gcrashes the game.


Fix bug in SharedTree factory proxy hydration

Description
There currently exists a bug during proxy hydration. In the proxy API, proxies in the input tree are immediately hydrated after inserting content into the tree, however, tree-change events are nonetheless fired after insertion but before hydration occurs. If any of these tree events incur a read of the tree location where a proxy is pending hydration, then a new proxy will be created before hydration of the existing proxy occurs. When hydration of that proxy does occur soon after, it will throw an error because it is illegal to map two proxies to the same input node.
Fixing this requires careful consideration of the event sequencing. This PR implements the following solution. A new anchor event is introduced that fires immediately after content is inserted (and before any other events are fired). This event, childrenChanged is a mirror of the existing childrenChanging event; it happens just after the edit to the forest rather than just before. An event in the editable tree layer is built on top of this. However, it is problematic if anyone subscribes to such an event. It can introduce the same problem as exists now: if the event listener reads the tree in the wrong place during an insert, proxy hydration will fail for the same reason. So, the event registration is not exposed publicly alongside other events on TreeNode but is instead keyed by an internal (un-exported) symbol (onNextChange). It is further tailored to the scenario at hand; the event can only have one listener at a time and it automatically deregisters itself after firing the first time. This makes it suitable for proxy hydration and not much more, so as to discourage any more internal widespread use. Anytime that content is inserted into the tree by the proxy API, this event is subscribed to just before the insertion, and proxy hydration occurs when the event fires. Proxies are thus hydrated before any other events can examine to the tree state after the change.
There are other ways to solve this problem. For example, if inserted content could be identified with some token (e.g. a node key a.k.a. a node identifier), then the proxies could be keyed off of the token rather than the edit node, and be cached in a map even before insertion. Such a token does not currently exist but may in the future, at which time we can revisit this.
This PR also does some minor test and documentation cleanup.

@tyler-cai-microsoft from the description, sounds like this is the issue you repro'd?

@tyler-cai-microsoft from the description, sounds like this is the issue you repro'd?

The error thrown is is "Cannot associate an edit node with multiple targets".

@tyler-cai-microsoft from the description, sounds like this is the issue you repro'd?

The error thrown is is "Cannot associate an edit node with multiple targets".

Tyler's repro is here if you'd like to try it against your change: https://github.com/microsoft/FluidFramework/pull/18232/files#diff-c97fa3e4c7401e9a6829502d0aad7df0c10e5289fd73315465254f0c429be6d0R12

@tyler-cai-microsoft from the description, sounds like this is the issue you repro'd?

The error thrown is is "Cannot associate an edit node with multiple targets".

Tyler's repro is here if you'd like to try it against your change: https://github.com/microsoft/FluidFramework/pull/18232/files#diff-c97fa3e4c7401e9a6829502d0aad7df0c10e5289fd73315465254f0c429be6d0R12

Thanks for the repro! Yea, that is the exact bug this PR is fixing. I confirmed that that test passes with the code in this PR.


Created ESP-IDF sample project and a GitHub action to test build it

The main.cpp file is a verbatim copy of the UsageExample.cpp file from the idf_examples project. Possibly PlatformIO can compile this copy also, but I did not look into this.

Thanks a lot, this was fast and looks great.

Thank you.


Travis CI builds

A very simple setup for testing via Travis. It uses Miniconda to install dependencies and then runs the test script. I originally tried a straight install, but compiling SciPy took so long, it ran out of build time. The conda install is much much quicker.
You will of course have to enable Travis for your repo before this has a real effect. And it doesn't really check whether the result correct, only that something is produced, but that's how the existing test script is. One could also do coverage testing using the other script and coveralls.io, but that's something for a another PR.

Thanks; this is very useful. I'll try to merge it.
Sorry this has taken so long; I've been focusing on CLSTM.

I rebased, but master is currently broken.

I have the same error which I corrected by downgrading the Pillow library:
pip install -U "Pillow<3"
Another library problem is happening with newer version numpy (meaning that you have to downgrade scipy in the same time): I use numpy 1.9.2 and scipy 0.15.1.
Maybe it can be included in the new requirements files (?).

Travis-CI is very useful, but there are other changes in this patch that change the search path etc. Could you perhaps separate those out and also explain? For example, why do you want to remove searching in /usr/... directories for models?

It doesn't make sense to search in /usr/local if the package is not installed there; on Travis it's installed in the conda environment. The change makes it search relative to the installed location instead.

@QuLogic: I removed the model-search commit (merged in #152), rebased against current master and adapted the travis.yml to current requirements.txt in https://github.com/kba/ocropy/tree/travis-conda. Travis check is running smoothly https://travis-ci.org/kba/ocropy/builds/176224957 :+1:
If that looks alright to you, please force-push those changes to your travis-conda branch, so we can at long last merge this :-)

I just realized the README.md needs an update too now with the changed requirements.

I just rebased this myself, coincidentally...

Thank you very much @QuLogic !
We will try to redirect the status of the badge, since Travis still needs to be approved here by @tmbdev .

FYI Travis is activated and approved now.


Invalid "TypeError: Unsupported Chain" Error using useContractFunction hook

When using a hardhat node with the default chainId (31337) I am unable to send transactions using useContractFunction hook.
I get TypeError: Unsupported chain even though I've added the chainId to the config parameters used when initializing the DappProvider

What useDApp version do you use?

I looked at the code again, we don't support currently hardhat node. We could add 31337 port, that would allow sending transactions. However the multicall contract is not deployed, so calls will not work.
The feature is on the roadmap.

I updated to the latest version.
Would be great to just be able to override what network's are supported. What benefit is there from hardcoding a chainId?
When testing the useDapp library I just deployed multi-call to my local network. Plus, my hardhat node might just be a fork of mainnet, which would include the multi-call smart contract.

Added HardHat chainId to list of supported chains. Published in 0.3.10

The benefit suppose to be type safety, but that turned out to be problematic.
Flexible chainId's are scheduled for the next milestone.

The benefit suppose to be type safety, but that turned out to be problematic.
Flexible chainId's are scheduled for the next milestone.

Any updated on next milestone?

We added HardHard port to the list a while ago. Is it not working for you?

We added HardHard port to the list a while ago. Is it not working for you?

It wasn't working for me a few days back, I've switch to Infura in the meantime, I will update here if I find Hardhat still not working.

We added HardHard port to the list a while ago. Is it not working for you?

So I switched back to Hardhat and I run into the follow errors (that don't appear with using Infura as the network):
1.) I receive an error "Missing multicall address for chain id 1337"
2.) When I connect to my dapp, Metamask opens and I can give permissions, but the app state (provider) does not register the change until I refresh the page
Details:
Network URL: http://<IP_ADDRESS>:8545 (issue happens also with http://localhost:8545)
Chain ID: 1337
@usedapp/core: ^0.3.17

We added HardHard port to the list a while ago. Is it not working for you?

So I switched back to Hardhat and I run into the follow errors (that don't appear with using Infura as the network):
1.) I receive an error "Missing multicall address for chain id 1337"
2.) When I connect to my dapp, Metamask opens and I can give permissions, but the app state (provider) does not register the change until I refresh the page
Details:
Network URL: http://<IP_ADDRESS>:8545 (issue happens also with http://localhost:8545)
Chain ID: 1337
@usedapp/core: ^0.3.17
In the Hardhat config, due to an issue with MetaMask (https://hardhat.org/metamask-issue.html), the chainId is set to 1337:
  networks: {
    hardhat: {
      chainId: 1337,
    },
  },

Perhaps this is the conflicting issue - I see above you reference Hardhat's default chainId of 31337, whereas the MetaMask / Hardhat issue requires the chainId to be 1337. This might be resolved if we can configure custom chainIds.

Hi there!
Did you find a way to solve this issue? I tried to change my metamask hardhat chainId to 31337 so it matches with useDApp config constants but still no luck.


TDD project

Remember to start with tests for all of the methods described below. Your commit history should prove that you have used TDD.

[x] Create a class called Solver.
[x] Create a method called factorial that takes one argument, an integer N, and returns the factorial for that number. The factorial is the multiplication of all integers from 1 to N and has the special case that the factorial of 0 is 1. This method only accepts 0 and positive integers, so if a negative integer is given it should raise an exception.
[x] Create a method called reverse that takes one argument, a string word, and returns word reversed (e.g. if word is "hello" it returns "olleh").
[x] Create a method called fizzbuzz that takes one argument, an integer N, and returns a string. The returned string is constructed following these rules:
When N is divisible by 3, return "fizz".
When N is divisible by 5, return "buzz".
When N is divisible by 3 and 5, return "fizzbuzz".
[x] Any other case, return N as a string (e.g. say N is 7 then return "7").

Thanks for your quick review, @gemmen29


How to improve the depth reading in the corners of a room?

I am using the Azure Kinect with the wide field-of-view depth camera to detect objects being put on the floor, by first getting a reading of the depth values with no objects, and then comparing the depth of the new captures to get the difference. The problem I am having is that the depth reading in the corners of the room is very bad. I have been reading this document https://docs.microsoft.com/en-us/azure/kinect-dk/depth-camera#invalidation and know that there can be difficulties with corners of rooms.
What I want to know is if there is anything I can do to improve the depth readings, either through configurations of the camera or other tweaks. I have to use the WFOV depth camera, the narrow one is too narrow for my use case.
Below are some screenshots of the scene that caused me trouble. In this case the pixels are invalidated almost a meter into the room, especially in the corners.

@lordjesus , thank you for the feedback. Quick questions and experiment to try:

are you using WFOV_2X2BINNED or WFOV_UNBINNED, you can try both to see whether they make are difference
I see the bright edge in the IR image at the bottom, is that a table? Can you try to lift the camera higher or put the camera on a tripod see whether it improves your reading at the corners in the room?
If you move the camera closer to the scene, will that improve the corner?

The invalidation at the corner could be because of low signal or multipath detection, during either case, the depth value accuracy could be out of spec, therefore, the invalidation is trying to ensure the depth you got from the camera is accurate.
Another idea you can try could be 2 or more cameras with NFOV

@lordjesus hope the answers above help you, let us know if you have more questions.


ndk-build,cargo-apk: Rename intent_filters back to intent_filter

Fixes #304, CC @hoodad
We commonly name vectors of items with their singular form so that they read nicer in TOML and XML (i.e. [[intent_filter]] adds a single entry to that list, and gets serialized as a single <intent-filter> XML element) and this matches Android's intent-filter naming too.
This change in a6f3e13 ("ndk-build: Move default serialization of MAIN intent filter to cargo-apk (#241)") was made purely with Vec in mind, but breaks existing manifest parsing nor was anticipated to be a breaking change in this area as the README still carries intent_filter instead of intent_filters in its Cargo.toml metadata reference.

I want to try landing this without yet-another breaking release for ndk-build: can we do that by yanking the previous releases? We don't need a breaking release for cargo-apk either way, but it may be nice to yank their older releases too.

Behind keeping the name as it was, to be very precise :grimacing: - it's more in-line with all the other properties too.
Now let's see why NDK r23 is hitting us again - we already had to work around the libgcc bug and now it's breaking our CI :/

A relaunch seems to have fixed it, but we should perhaps bump the cache (newer api-level) at some point.
This is also the time ping @rust-windowing/publishers for suggestions/approval on breaking changes in a patch release if all the other versions are yanked; and I also need you to do the yanking if this is okay :)

After some thought I still don't think it's a good idea to publish a breaking change in a patch release and yank the older versions, so we'll release it as breaking change instead.
@rust-windowing/publishers it'd still be nice to yank cargo-apk 0.9.0-0.9.2 and ndk-build 0.6.0 though, thanks!


Add new flag (-r) to support inverted RTS flow control

This is useful if you have a MAX485 connected to a Raspberry PI where you pull want RST low to transmit.

I would have liked to use -T to match -y/-Y, but this is already used. I've proposed -r to keep CLI-flag backwards compatibility.
I've also left the config file setting as "rts" so as to preserve backwards compatibility.

@3cky ping
Do let me know if you've got any comments. I'd be keen to merge this upstream to get it into pre-built packages, etc.
Thanks


feat: Ionicon 2.0

Type: feat
Platform: all
I saw that ionicon 2.0 was out and tried using it with the latest ionic and discovered that beta14 is only bundled with ionicon 1.5.2.
When will the new version of ionic be released?

Greetings @thomaschaaf!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

You could give nightly build a try. Ionicon 2.0 is available in it now.

ionicons 2.0 are in the nightly build.


fix: added 4844 transaction in documentation

Fix for:

https://github.com/paradigmxyz/reth/issues/8470

gh pr checkout 8521


Add minimal test case for rdar://problem/54580427.

The scale test says the behavior is exponential, but it should be
linear, given that (1) we provide a contextual type outside and
(2) there is precisely 1 type which has the corresponding cases.

@swift-ci please smoke test


Content URLs are not resolveable by the user agent

Description
The content URL for content created via content-publishing-service is a URL that is resolvable by the content-publishing-service. This URL may not be publicly resolvable, as the content-publisher may be running in a different network environment (cloud provider virtual network, containerized network, etc) than a browser or other user agent. URLs provided to the end user-agent must be [publicly] resolvable.
Proposed solution
Have the social-gateway-template backend rewrite content URLs before providing them to a user agent.

Fixed.


Add pipeline2 scheduler + runner

To run pipelines, the backend needs a background worker to start a kubernetes pods with the right parameters: this is the runner. The runner is a while True loop querying the DB for QUEUED PipelineRun; when it founds one, it forks itself and starts the pipeline; the fork watching the execution of one pipeline, let's call that the watcher. The watcher can starts the pipeline in a docker for development purpose, or as a kubernetes pod in production. The watcher collects statistics, logs, return code, ... Every few seconds, the watcher also update a heartbeat to prove that 1/ the watcher is still alive, 2/ the pipeline is still alive. It's used to reap crashed watcher by the runner: every minutes, if a PipelineRun is in a state RUNNING with a last heartbeat bigger that 2 minutes, it will be marked as FAILED with a timeout message in its logs.
This worker can start & run pipeline created manually, but to enable the "scheduled" execution feature, we need another background worker: the scheduler. Also a while True loop, querying all Pipeline objects, seeing if some execution is needed in the near future and create a PipelineRun in state QUEUED if it needs to be. That PipelineRun is then picked by the runner with the above process.
Changes

Rename webhook token -> access token
Add runner worker
Add scheduler worker
Trigger type (scheduled, manual) is now an enum, not a string

How/what to test

Start the runner, create a pipeline run (with API or shell), watch it execute.
Start the scheduler with a runner, create a pipeline with a schedule "*/10 * * * *", watch it run every 10 minutes

Also, as discussed, it seems that it is not yet possible to specify parameters for running the pipeline


Docker buildkit should always be used

Fixes #1630
What is being addressed
Describe the current behavior you are modifying.  Please also remember to update any impacted documentation.
How is this addressed

devcontainer is loaded (by VSCode) with buildkit enabled
Remove all CI parameters related and hardcode the container run command to use buildkit

/test


Add existing guidelines to qiskit docs guidelines

Summary
We have written documentation guidelines in Box notes. This PR migrate those guidelines into .rst format within the new Qiskit Docs Guidelines sphinx project created by #108.

[x] Add tutorials guidelines
[x] Add how-to guide guidelines
[x] Add API reference guidelines
[x] Add explanation guidelines
[x] Simply internal cross-refernecing in toctree (see details below)
[x] Rename explanations to explanation

Fixes #81, Fixes #82, Fixes #83, Fixes #84.
This is a continuation of #100 which was closed because of branch renaming.
Details
This PR also simplifies the internal cross-referencing in toctree by putting the name of files instead of names with links. For example, previously we use:
.. toctree::

   Getting Started <getting_started>

now we use:
.. toctree::

   getting_started

The linked text is extracted from the title of getting_started file which is the same Getting Started. But using this new way we simply the cross referencing and avoid extra work on making sure the text Getting Started inside toctree matches the title of the linked page.
Details

When i build locally there seems to be some weird stuff happening with the toc tree, all your changes seem to be under API Reference, and nothing is showing under How-to-guides etc (screenshots attached)

This is done on purpose. The guidelines, examples and templates themselves are our "API Reference" but each one is about tutorials, how-tos, reference or explanation, so you can see the how-to section as "the part of the docs/guidelines API reference that is about creating how-tos".
It's a bit confusing but it makes sense

When i build locally there seems to be some weird stuff happening with the toc tree, all your changes seem to be under API Reference, and nothing is showing under How-to-guides etc (screenshots attached)

This is done on purpose. The guidelines, examples and templates themselves are our "API Reference" but each one is about tutorials, how-tos, reference or explanation, so you can see the how-to section as "the part of the docs/guidelines API reference that is about creating how-tos".
It's a bit confusing but it makes sense

I don't think this makes sense tbh 😅 I think it would be better for readers to have each guideline live in the page associated with what the guidelines are about. So tutorial guidelines under the tutorials section, explanation guidelines under the explanation section etc.. Also our docs aren't an API so it's not correct for us to say that the guidelines form the API Reference, there is no API that we are referencing

I don't think this makes sense tbh 😅 I think it would be better for readers to have each guideline live in the page associated with what the guidelines are about. So tutorial guidelines under the tutorials section, explanation guidelines under the explanation section etc.. Also our docs aren't an API so it's not correct for us to say that the guidelines form the API Reference, there is no API that we are referencing

Yeah we talked about the lack of actual API and agreed to rename "API Reference" to "Reference". The solution to this confusion (that we have in mind right now) is to add links from say the how-to page (with the actual how-to guides) to the Reference about how-to guides. Something like:

This section covers how-to guides for creating documentation, if you are looking for examples, templates or guidelines about writing how-to guides, check this reference material (link to how-to reference)

I believe putting say the how-to examples, templates and guidelines in the how-to section defeats the purpose of using Diataxis for docs_guidelines, as they are not how-to guides 😅

Honestly I don't really understand why we are using diataxis so strictly for the docs guidelines themselves 😅 I was assuming this is documentation to teach people how to use the diataxis framework in the context of Qiskit, and I don't think that necessitates implementing diataxis itself. Looking at https://diataxis.fr they keep info about writing tutorials under the tutorials page and info about api reference under the reference page etc etc. they don't put everything under reference and I don't think we should either. The guidelines aren't a piece of software so diataxis in this context just adds confusion for the user for the sake of showcasing diataxis, which I don't think is the best approach. Maybe we can discuss more in our next meeting, it's hard for me to get the full picture of your plans for the guidelines from individual PRs :)

This PR is superseded by https://github.com/Qiskit/qiskit_sphinx_theme/pull/166


Revert "Slight rename"

What does this PR do?
This reverts commit a9869ea0dc49652e49607d5f111caed79ed5cb67 as it was pushed by mistake.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Release LZ-Vending v1.2.1

Description
See details in downstream PR: https://github.com/Azure/bicep-lz-vending/pull/30
Updating an existing module

[ ] This is a bug fix:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[x] I have run brm validate locally to verify the module files.
[x] I have run deployment tests locally to ensure the module is deployable.
[x] I have read the Updating an existing module section in the contributing guide and updated the version.json file properly:

[ ] The PR contains backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json.
[x] The PR contains backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] The PR contains breaking changes, and I have bumped the MAJOR version in version.json.

PR in home repo approved and merged and new release cut https://github.com/Azure/bicep-lz-vending/releases/tag/v1.2.1
@shenglol if we can approve and merge here, I'd really appreciate it 👍


multicluster test setup failure: "unknown cluster"

https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/29426/integ-pilot-multicluster-tests_istio/1336045214938173440

Oh the logs are confusing due to parallelism, the real error seems more like:
ERROR: failed to create cluster: could not locate any control plane nodes

seems everything is just timing out

@howardjohn Is this still an issue or can it be closed?

@howardjohn Is this still an issue or can it be closed?

I think its resolved now

I think its resolved now


Appsee provider

Adds support for Appsee (https://www.appsee.com)
Supports userID (not email), events, page views.

FYI, I did not bump the podspec version with this pull

Looks good, sorry, I've missed these.


Azure SignalR resource sets connection information as ConnectionString, but default client uses a diff default config

The SignalR resource sets the connection string information as a ConnectionStrings__{name}  But the Microsoft.Azure.SignalR client by default looks for Azure:SignalR:ConnectionString -- there is an override to supply it and the developer would have to know now to use
.AddAzureSignalR(builder.Configuration.GetConnectionString("signalr"));

Should we emit the default expected config setting instead? If not, convert this to an issue to update readme/docs on this resource to note the client consumption side

Instead of using .AddAzureSignalR(), I was using .AddNamedAzureSignalR("signalr") which is documented to read form connectionstrings.

Perfect. Converting this to updating the readme to point this out


Add a Feedback page

Add a Feedback page

@Harshal0902 pls assign me this issue.

@ishitakapoor26 go for it

I would like to work on this issue under LGMSOC'21 participant. Please assign me @Harshal0902

@Srit20 I am already working on it and its almost done.

@ishitakapoor26 ok carry on all the best

@Harshal0902 pls review pr.


Missing information in Step #7 Database copy from Sandbox request (if applicable)

The service request for copying Sandbox to Production has a lead time of 5 hours for downtime request (excluding the further SLA of 4 hours to action the service request). which is not mentioned anywhere in this article.  e.g. service request raised at 10 am UTC will have downtime starting from 3 pm UTC.
If one tries to schedule the downtime before that, there is an error in LCS - "The downtime start time is required to be at least 5 full hours".
thanks,
Manish

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b23a0dbf-7870-affb-b07b-53b8ea704371
Version Independent ID: 02442fdc-5733-1ab3-da37-a1e6dfc89c41
Content: Prepare for go-live - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/fin-ops-core/fin-ops/imp-lifecycle/prepare-go-live.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @ClaudiaBetz-Haubold
Microsoft Alias: chaubold

Thank you for your feedback. @ClaudiaBetz-Haubold can you please take a look?

Created bug 384071 to track.

@Jo<EMAIL_ADDRESS>– the feedback does not make sense to me. Step 7 in the document clearly calls out the lead time and the downtime:
<EMAIL_ADDRESS>Feel free to make a suggestion to reword this to avoid confusion if you deem it necessary.
Thanks,
Claudia Betz-Haubold
Principal Solution Architect | FastTrack for Dynamics 365https://dynamics.microsoft.com/en-us/fasttrack/
office:  +49.89.3176.2804 |  mobile:  +49.151.4401.2309
Check this out: Understand the implementation lifecyclehttps://docs.microsoft.com/en-us/dynamics365/unified-operations/fin-and-ops/imp-lifecycle/implementation-lifecycle
[Microsoft]
From: josaw1<EMAIL_ADDRESS>Sent: Thursday, October 17, 2019 5:03 PM
To: MicrosoftDocs/dynamics-365-unified-operations-public<EMAIL_ADDRESS>Cc: Claudia Betz-Haubold<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/dynamics-365-unified-operations-public] Missing information in Step #7 Database copy from Sandbox request (if applicable) (#1746)
Created bug 384071 to track.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fdynamics-365-unified-operations-public%2Fissues%2F1746%3Femail_source%3Dnotifications%26email_token%3DAGZ6W75AFBNFZSRQO6PGSI3QPB5BRA5CNFSM4I7GY62KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBQNPFI%23issuecomment-543217557&data=02|01|Claudia.Betz-Haubold%40microsoft.com|57c6de46b10e4303799a08d75313138d|72f988bf86f141af91ab2d7cd011db47|1|0|637069213711231811&sdata=xmuosAecv7qQhra9pVPdgl4Vsuho23JJSUvAa8%2F%2Fuag%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGZ6W75OKRYEEX6JWRNAJX3QPB5BRANCNFSM4I7GY62A&data=02|01|Claudia.Betz-Haubold%40microsoft.com|57c6de46b10e4303799a08d75313138d|72f988bf86f141af91ab2d7cd011db47|1|0|637069213711231811&sdata=QE0K3cAIvqJAMYrlfx4dW9WoFYcVSAS%2FnF58YlxZiAE%3D&reserved=0.


Change query action functions

Details
Currently there are functions for:
Model.insert(dynamic entity)
Model.insertAll(List<dynamic> entity)
Model.update(entity)
Model.updateAll()...
Model.delete... // you get the idea

I think they should be changed because they make the deletes and updates inflexible. I gave it some thought and decided that it should be something like
// Insert from mapped key / values
insert(name,Map <String,dynamic>values)

// Inserts entity or List<entities>
insertFrom(dynamic entities)

// For all the modifications

This would allow for the conditional updates and deletes such as for one example:
// Update conditionally with name / values
Model.update('User',{'firstName':'Bill'}).where...

// Run is the only possible function chain and it updates by primary key
Model.updateFrom(user).run()

It might be nice to fix up the find and use type instead. The string there has been bothering me but still need to include the name so maybe theres a few parts:

Change the find etc to use type as default but add secondary option for name

// Change to use type primarily
Model.find(User).where...
// Include find by name
Model.findByName('user')..where
```
2. Per the examples, change the auto mandatory resource on @Model('user') to instead be optional and set something like name, then that would be the value used when finding by name. This seems more consistent
```dart

@Model(name: 'user')
```
This way by default the `Model` can be an empty annotation where the name is taken as the class name if no name is specified:
```dart

@Model()
class Thingo...
```
Then per the above, there are actions like:
```dart

Model.insert(User,values)
Model.insertByName('user',values)
Model.insertFrom(user)
```

Ok I am not doing the action(Type t) implementation. Instead it will just be dynamic you can use Type or String because it was too annoying and meant changing a whole lot. That wouldn't be a problem but using types do have a drawback in that they are specific to the exact type match and that you cant really go (from what i can tell) from String -> Type whilst you can easily go Type -> String. I started to trial it out a bit and felt it wasnt worth it.


Add reports API

I've Added reports API.

GET /api/v1/reports
POST /api/v1/reports

Could you please rebase master to add context for first argument?

Thank you

Oh,sorry for the late reply and incomplete commit...
Thank you..

No prob~


fix assertion failure when last bytes transmitted separately from FIN are retransmitted

At the moment, there is an assertion that assumes that when the last bytes of a closed stream is (re)transmitted, FIN will be marked for transmission as well.
But that does not hold.
Consider the case where data is transmitted, then the stream gets closed, causing the FIN to get transmitted separately. When receiving nothing from the peer, the data is marked for pending and gets sent. But at that point, FIN is still considered inflight.
This PR removes the assertion.

Merged, but I appreciate your reviews @janaiyengar @hfujita.


Using The Lounge on a flaky network leads to a very schizophrenic front-end

The client is not particularly good at recovering from network problems, it seems. Even in 2.0.0-pre.3 any timeout while the client is open leads to a full-page reload.
Unfortunately my LAN is very, very flaky tonight and can't keep connections open for more than about 30 seconds. I was hoping The Lounge would be more stable than a desktop client, but neither allows me to reliably send and receive IRC messages; lines both to and from the server are randomly dropped without any warning in both.
I don't suppose The Lounge's architecture would support falling back to some kind of polling if the network is so flaky that persistent connections simply don't work?

I don't suppose The Lounge's architecture would support falling back to some kind of polling if the network is so flaky that persistent connections simply don't work?

Socket.io already does this.
The real problem is that when we lose connection, we tell the page to reload. Ideally, we should not do that, and let socket.io reconnect. The problem with just switching that one (we've tried) is that the server never expects this to happen, so we get a bunch of initial connection information and we send all the channels and their messages again, and it becomes a mess.

I see. So the client could do it, in theory, but it would require server-side changes (I'm simplifying a lot).
Could making those changes to the server be a goal for 2.1? 3.0? There's already a lot slated for the 2.0.0 release—and it's been 3 pre-releases already anyway—but improving the reconnection support seems like a good goal now that it's at least implemented for both client<->server and server<->network.

Could making those changes to the server be a goal for 2.1? 3.0?

So, if someone ever wants to tackle with this one (which would be really awesome) and wants some history/archives, @unconed gave a try at this in #267.
Feel free to stop by the channel (#thelounge) if you need help with this.

Absolutely useless on my Android tablet, as it times out by the time it finally finishes Authorizing after a login. It takes about 30 seconds to Authorize, then briefly flashes the last channel viewed buffer, then the names list appears empty, then it immediately flashes back to Authorizing... repeat until I grow bored of watching my tablet cycle itself to death.

Will close this issue as #1471 most likely fixes this, and there's not any specific problem we can tackle besides that.


All data in graphiQL is empty

Hello there,
I'm migrating from @prismicio/gatsby-source-prismic-graphql, and I believe I've got this plugin setup right, but there is no data in graphiQL?
All the types are available in the left navbar, including slices, but everything I query is empty. There's no error whatsoever either?
Here's my configuration:
    {
      resolve: 'gatsby-source-prismic',
      options: {
        repositoryName: process.env.PRISMIC_REPO,
        accessToken: process.env.PRISMIC_API_KEY,
        linkResolver: ({ node, key, value }) => linkResolver,
        htmlSerializer: ({ node, key, value }) => htmlSerializer,
        lang: 'fr',
        schemas: {
          page: require('./src/schemas/page.json'),
          post: require('./src/schemas/post.json'),
        },
        shouldDownloadImage: () => true,
      },
    },

Not sure what else to try, I've obviously cleaned the cache, reinstalled node modules.

For lang have you tried fr-fr? I think your issue might be there as there is support for ca-fr etc!

yeah, that was it.. 🤦♂


Update class="current" to use aria-current="page"

Not sure if this is the appropriate place for this, but I was wondering if we could update the following code example on the Collections documentation. It would be changing:

{{ post.data.title }}

to:

{{ post.data.title }}

It's a small tweak, but it provides a nice enhancement for assistive technology users to understand where they are in a site's structure.
Thanks for the consideration. It's a lesser-known feature of ARIA, but I'm hoping this would help promote discovery 🙂

Why not both?

I think tying presentation to state with attribute selectors is a little more DRY, but there's no reason you can't use both.


installer/uninstaller fails to kill maxmix.exe

When installing update/uninstalling, the installer offers to stop processes which are running. You say ok, and then it thinks for a bit and decides it can't stop all the processes. In Task Manager, i see a maxmix.exe. I kill it, and then the uninstall proceeds OK.
Ideally it would suceessfully stop the running process during uninstall.

Good catch!
I'll take a look at the installer to see if there is anything not setup properly. It may be a bug of AdvancedInstaller itself.
Thanks!


Failed to attach volume message for a pod deployment

I have a small cluster setup with 1 master and 1 worker.
Post installing longhorn using helm I deploy a test pod using the below config:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: longhorn-volv-pvc
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: longhorn
  resources:
    requests:
      storage: 2Gi
---
apiVersion: v1
kind: Pod
metadata:
  name: volume-test
  namespace: default
spec:
  restartPolicy: Always
  containers:
  - name: volume-test
    image: nginx:stable-alpine
    imagePullPolicy: IfNotPresent
    livenessProbe:
      exec:
        command:
          - ls
          - /data/lost+found
      initialDelaySeconds: 5
      periodSeconds: 5
    volumeMounts:
    - name: volv
      mountPath: /data
    ports:
    - containerPort: 80
  volumes:
  - name: volv
    persistentVolumeClaim:
      claimName: longhorn-volv-pvc

I see the pod is scheduled however it fails with following error:
Events:
  Type     Reason              Age                From                     Message
  ----     ------              ----               ----                     -------
  Warning  FailedScheduling    30s (x3 over 32s)  default-scheduler        0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims.
  Normal   Scheduled           26s                default-scheduler        Successfully assigned default/volume-test to edge-server1
  Warning  FailedAttachVolume  22s (x3 over 26s)  attachdetach-controller  AttachVolume.Attach failed for volume "pvc-2d2c82a2-a0c3-4c19-b8be-edb34a4a3167" : rpc error: code = Internal desc = Bad response statusCode [500]. Status [500 Internal Server Error]. Body: [code=Server Error, detail=, message=unable to attach volume pvc-2d2c82a2-a0c3-4c19-b8be-edb34a4a3167 to edge-server1: volume pvc-2d2c82a2-a0c3-4c19-b8be-edb34a4a3167 not scheduled] from [http://longhorn-backend:9500/v1/volumes/pvc-2d2c82a2-a0c3-4c19-b8be-edb34a4a3167?action=attach]

Following is the output of my partitioning on the os:
 blkid
/dev/sda1: UUID="1B35-54A5" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="fa8b73d7-f5bf-4493-8ba8-881548d0558c"
/dev/sda2: UUID="863ddeff-35d9-4544-9b8f-770dd4b31bd3" TYPE="ext4" PARTUUID="8f323dfd-ea32-40e8-bd6b-937b47a1339a"
/dev/sr0: UUID="2020-10-02-05-42-00-00" LABEL="ubuntu-auto" TYPE="iso9660"

iscid service is up and running on both pods
Is there some configuration that I have missed?
Version: ``
kube: 1.19
longhorn: latest

 not scheduled means Longhorn cannot find enough nodes/disks to schedule the volume.
You can enable the soft-anti-affinity option to relax the scheduling rule, allowing Longhorn to schedule replicas to the same node.

Thanks yasker,
You are asking to change the following settings in the values.yml file:
replicaSoftAntiAffinity: True

Am I right?

Hi Yasker this worked thanks much.
Just one question this option won't affect anything if we are running this in production?
What I need to do if I have to run this with default configuration provided in upstream?

Hi an update.
Since it started working I tried mysql chart using helm with "longhorn" as storage class
Events:
  Type     Reason                  Age                  From                     Message
  ----     ------                  ----                 ----                     -------
  Warning  FailedScheduling        2m15s                                         0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims.
  Warning  FailedScheduling        2m15s                                         0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims.
  Normal   Scheduled               2m8s                                          Successfully assigned default/mysql-1601748203-fcc8575db-qdx5q to edge-server2
  Normal   SuccessfulAttachVolume  2m5s                 attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-70dab12e-8e8b-4235-901d-fa77cc266564"
  Warning  FailedMount             2m1s (x2 over 2m1s)  kubelet, edge-server2    MountVolume.SetUp failed for volume "pvc-70dab12e-8e8b-4235-901d-fa77cc266564" : rpc error: code = InvalidArgument desc = There is no block device frontend for volume pvc-70dab12e-8e8b-4235-901d-fa77cc266564
  Normal   Pulled                  118s                 kubelet, edge-server2    Container image "busybox:1.32" already present on machine
  Normal   Created                 118s                 kubelet, edge-server2    Created container remove-lost-found
  Normal   Started                 117s                 kubelet, edge-server2    Started container remove-lost-found
  Normal   Pulled                  117s                 kubelet, edge-server2    Container image "mysql:5.7.30" already present on machine
  Normal   Created                 117s                 kubelet, edge-server2    Created container mysql-1601748203
  Normal   Started                 116s                 kubelet, edge-server2    Started container mysql-1601748203

Even though it says it failed to attach the volume I see on server 2 my blkid/lsblk shows:
2 Gigs of partitioning for mysql
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0   558G  0 disk
|-sda1   8:1    0   512M  0 part /boot/efi
`-sda2   8:2    0 557.5G  0 part /
sdb      8:16   0   558G  0 disk
sdc      8:32   0     2G  0 disk /var/lib/kubelet/pods/f83729ba-9663-4fca-9033-3a0ece1b4a29/volumes/kubernetes.io~csi/pvc-70dab12e-8e8b-4235-901d-fa77cc266564/mount
sr0     11:0    1 967.9M  0 rom

Did a small test of creating a database and then deleting the pod... the new pod was having the db that I created.
If the persistence is working as expected then why that failed command to mount?

If you're running Longhorn in production, you should set node soft anti-affinity to false, to ensure the high availability of Longhorn. And it's recommended for you to have a cluster that's at least 3 nodes.
You meant There is no block device frontend for?
This is a misleading error message. We will fix it in #1739 .
When it's mounted, it's probably in the process of attaching and haven't completely finished yet. You don't need to worry about it now. We will check why there is an error report as well.

Hi Yasker,
So now I have a 3 node setup 1 master and 2 workers however by resetting replicaSoftAntiAffinity: True to False, I still see the issue:
Events:
  Type     Reason              Age                From                     Message
  ----     ------              ----               ----                     -------
  Warning  FailedScheduling    46s                                         0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.
  Warning  FailedScheduling    46s                                         0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.
  Normal   Scheduled           40s                                         Successfully assigned default/mysql-54bbdd8f86-mznlf to edge-server3
  Warning  FailedAttachVolume  24s (x4 over 38s)  attachdetach-controller  AttachVolume.Attach failed for volume "pvc-1877bbb2-c43a-465b-8494-dec2604e6832" : rpc error: code = Internal desc = Bad response statusCode [500]. Status [500 Internal Server Error]. Body: [message=unable to attach volume pvc-1877bbb2-c43a-465b-8494-dec2604e6832 to edge-server3: volume pvc-1877bbb2-c43a-465b-8494-dec2604e6832 not scheduled, code=Server Error, detail=] from [http://longhorn-backend:9500/v1/volumes/pvc-1877bbb2-c43a-465b-8494-dec2604e6832?action=attach]
  Warning  FailedAttachVolume  8s (x3 over 40s)   attachdetach-controller  AttachVolume.Attach failed for volume "pvc-1877bbb2-c43a-465b-8494-dec2604e6832" : rpc error: code = Internal desc = Bad response statusCode [500]. Status [500 Internal Server Error]. Body: [code=Server Error, detail=, message=unable to attach volume pvc-1877bbb2-c43a-465b-8494-dec2604e6832 to edge-server3: volume pvc-1877bbb2-c43a-465b-8494-dec2604e6832 not scheduled] from [http://longhorn-backend:9500/v1/volumes/pvc-1877bbb2-c43a-465b-8494-dec2604e6832?action=attach]

following is my lsblk output:
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0   558G  0 disk
|-sda1   8:1    0   512M  0 part /boot/efi
`-sda2   8:2    0 557.5G  0 part /
sdb      8:16   0   558G  0 disk
sr0     11:0    1 967.9M  0 rom

I want to use longhorn in production environment, can you please suggest me what to do here?
Thanks
Rohan

@rohasharma, I think you need at least 3 worker nodes. Based on the log, it seems the replicas are failed to schedule. Please try 3 worker nodes. It should work for you.

So to make it work with 2 worker node I have to keep replicaSoftAntiAffinity: True?

So to make it work with 2 worker node I have to keep replicaSoftAntiAffinity: True?

Yes, or you can set the default replica number to 2. default replica number doc

Hey,
Awesome!! it worked like a charm after setting it to 2.
My closure question and then I am good to go:

If I want longhorn to use /dev/sdb as default disk how can I do that?
Currently it is taking space from /dev/sda

Thanks
Rohan Roy Sharma
On Wed, Oct 7, 2020 at 10:52 PM Bo Tao<EMAIL_ADDRESS>wrote:

So to make it work with 2 worker node I have to keep
replicaSoftAntiAffinity: True?
Yes, or you can set the default replica number to 2. default replica
number doc
https://longhorn.io/docs/1.0.2/references/settings/#default-replica-count
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/longhorn/longhorn/issues/1842#issuecomment-705080805,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKAYUJE5BVDJ5VBMCZTNVLTSJSPVBANCNFSM4SBNHVZQ
.

@rohasharma , you can format your /dev/sdb and mount it to a specific directory, and add that directory to Longhorn as a disk and then Longhorn will start to use the disk space from /dev/sdb. here is a document about it. And you can explore the document for more information about  Longhorn.

Hi @boknowswiki ,
Yeah I was able to achieve that using defaultDataPath in values.yml.
However, with replication set to 2 I see an issue.
replicas created on my server3 under /var/lib/longhorn/replicas/ are not present on server2 (both workers)
To test it out I rebooted my server3 however none of my test application spawned on server2 and it waited for server3 availability and then it started the pods there itself.
Is this HA not working because I have a replication set to 2 and using just 2 workers?
Quoting what @yasker  mentioned:
If you're running Longhorn in production, you should set node soft anti-affinity to false, to ensure the high availability of Longhorn. And it's recommended for you to have a cluster that's at least 3 nodes

He recommends to use 3 nodes cluster but mentions about high availability with soft anti-affinity set to false ( Which I have done)

@rohasharma , I think the 3 nodes cluster @yasker mentioned is 3 worker nodes cluster. The reason I told you change the replica count to 2 is you have 2 worker nodes cluster. If you can have a 3 worker nodes cluster, you should be able to use the default 3 replica count and set the soft anti-affinity to false.

hi @boknowswiki
i have deployed longhorn in production and tried to run a test example from (https://longhorn.io/docs/1.0.2/references/examples/#pod-with-persistentvolumeclaim) , but i faced the same issue as show bellow event in pod volume-test :
  Type     Reason              Age                   From                     Message
  ----     ------              ----                  ----                     -------
  Normal   Scheduled           10m                   default-scheduler        Successfully assigned default/volume-test to <IP_ADDRESS>
  Warning  FailedAttachVolume  10m                   attachdetach-controller  AttachVolume.Attach failed for volume "pvc-d26f221a-7ed9-4ab4-ba9a-9ebfc57cca23" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
  Warning  FailedMount         116s (x4 over 8m47s)  kubelet                  Unable to attach or mount volumes: unmounted volumes=[volv], unattached volumes=[default-token-5l2tx volv]: timed out waiting for the condition
  Warning  FailedAttachVolume  15s (x12 over 10m)    attachdetach-controller  AttachVolume.Attach failed for volume "pvc-d26f221a-7ed9-4ab4-ba9a-9ebfc57cca23" : rpc error: code = Aborted desc = The volume pvc-d26f221a-7ed9-4ab4-ba9a-9ebfc57cca23 is attaching

noted that pv & pvc are successefully created as show bellow :
Events:
  Type    Reason                 Age                From                                                                                Message
  ----    ------                 ----               ----                                                                                -------
  Normal  Provisioning           14m                driver.longhorn.io_csi-provisioner-75cb96846b-fmnns_480e10ff-c3ca-40d2-a5e3-99b8e3d91192  External provisioner is provisioning volume for claim "default/longhorn-volv-pvc"
  Normal  ExternalProvisioning   14m (x2 over 14m)  persistentvolume-controller                                                               waiting for a volume to be created, either by external provisioner "driver.longhorn.io" or manually created by system administrator
  Normal  ProvisioningSucceeded  14m                driver.longhorn.io_csi-provisioner-75cb96846b-fmnns_480e10ff-c3ca-40d2-a5e3-99b8e3d91192  Successfully provisioned volume pvc-d26f221a-7ed9-4ab4-ba9a-9ebfc57cca23

@htwalid Can you check your longhorn manager's log? There should be clues there.

@yasker thank you for your support . bellow some lines from logs of pod's longhorn manager
<IP_ADDRESS> - - [16/Nov/2020:22:38:57 +0000] "GET /v1/volumes/pvc-14f085bf-3125-4665-80b4-0fcbbb9eb0b1 HTTP/1.1" 200 3168 "" "Go-http-client/1.1" time="2020-11-16T22:38:57Z" level=warning msg="Starts to clean up then recreates pod for instance manager instance-manager-e-a460822f with state stopped" time="2020-11-16T22:38:57Z" level=warning msg="Error syncing Longhorn replica longhorn-system/pvc-055d6738-f2d8-41cb-89b6-d5d8b9792155-r-5925de4c: fail to sync replica for longhorn-system/pvc-055d6738-f2d8-41cb-89b6-d5d8b9792155-r-5925de4c: invalid Instance Manager instance-manager-r-6978a019, state: , IP: " time="2020-11-16T22:38:57Z" level=warning msg="Error syncing Longhorn replica longhorn-system/pvc-17e1ce20-97f7-45f4-a387-956a732df4e7-r-40a8baef: fail to sync replica for longhorn-system/pvc-17e1ce20-97f7-45f4-a387-956a732df4e7-r-40a8baef: invalid Instance Manager instance-manager-r-6978a019, state: , IP: " time="2020-11-16T22:38:57Z" level=warning msg="Error syncing Longhorn replica longhorn-system/pvc-361f765b-7d63-4164-9ddf-bb03c22c361b-r-aaa64a68: fail to sync replica for longhorn-system/pvc-361f765b-7d63-4164-9ddf-bb03c22c361b-r-aaa64a68: invalid Instance Manager instance-manager-r-6978a019, state: , IP: " <IP_ADDRESS> - - [16/Nov/2020:22:38:57 +0000] "GET /v1/nodes/<IP_ADDRESS> HTTP/1.1" 200 1747 "" "Go-http-client/1.1" E1116 22:38:57.062348       1 replica_controller.go:177] fail to sync replica for longhorn-system/pvc-055d6738-f2d8-41cb-89b6-d5d8b9792155-r-5925de4c: invalid Instance Manager instance-manager-r-6978a019, state: , IP:  time="2020-11-16T22:38:57Z" level=warning msg="Dropping Longhorn replica longhorn-system/pvc-055d6738-f2d8-41cb-89b6-d5d8b9792155-r-5925de4c out of the queue: fail to sync replica for longhorn-system/pvc-055d6738-f2d8-41cb-89b6-d5d8b9792155-r-5925de4c: invalid Instance Manager instance-manager-r-6978a019, state: , IP: " time="2020-11-16T22:38:57Z" level=warning msg="Starts to clean up then recreates pod for instance manager instance-manager-r-6978a019 with state stopped" E1116 22:38:57.068162       1 replica_controller.go:177] fail to sync replica for longhorn-system/pvc-17e1ce20-97f7-45f4-a387-956a732df4e7-r-40a8baef: invalid Instance Manager instance-manager-r-6978a019, state: , IP:  time="2020-11-16T22:38:57Z" level=warning msg="Dropping Longhorn replica longhorn-system/pvc-17e1ce20-97f7-45f4-a387-956a732df4e7-r-40a8baef out of the queue: fail to sync replica for longhorn-system/pvc-17e1ce20-97f7-45f4-a387-956a732df4e7-r-40a8baef: invalid Instance Manager instance-manager-r-6978a019, state: , IP: " E1116 22:38:57.068477       1 replica_controller.go:177] fail to sync replica for longhorn-system/pvc-361f765b-7d63-4164-9ddf-bb03c22c361b-r-aaa64a68: invalid Instance Manager instance-manager-r-6978a019, state: , IP:  time="2020-11-16T22:38:57Z" level=warning msg="Dropping Longhorn replica longhorn-system/pvc-361f765b-7d63-4164-9ddf-bb03c22c361b-r-aaa64a68 out of the queue: fail to sync replica for longhorn-system/pvc-361f765b-7d63-4164-9ddf-bb03c22c361b-r-aaa64a68: invalid Instance Manager instance-manager-r-6978a019, state: , IP: " <IP_ADDRESS> - - [16/Nov/2020:22:38:57 +0000] "GET /v1/volumes/pvc-8183bdc5-83c8-494a-906c-e16a6ab8d151 HTTP/1.1" 200 3168 "" "Go-http-client/1.1" <IP_ADDRESS> - - [16/Nov/2020:22:38:57 +0000] "GET /v1/volumes/pvc-67c8e4e3-d080-4d46-84f3-d3d90eca5394 HTTP/1.1" 200 3165 "" "Go-http-client/1.1" time="2020-11-16T22:38:57Z" level=warning msg="Error syncing Longhorn instance manager longhorn-system/instance-manager-e-a460822f: fail to sync instance manager for longhorn-system/instance-manager-e-a460822f: failed to create pod for instance manager instance-manager-e-a460822f: Pod \"instance-manager-e-a460822f\" is invalid: spec.containers[0].resources.requests: Invalid value: \"250m\": must be less than or equal to cpu limit" <IP_ADDRESS> - - [16/Nov/2020:22:38:57 +0000] "GET /v1/nodes/<IP_ADDRESS> HTTP/1.1" 200 1680 "" "Go-http-client/1.1" time="2020-11-16T22:38:57Z" level=warning msg="Error syncing Longhorn instance manager longhorn-system/instance-manager-r-6978a019: fail to sync instance manager for longhorn-system/instance-manager-r-6978a019: failed to create pod for instance manager instance-manager-r-6978a019: Pod \"instance-manager-r-6978a019\" is invalid: spec.containers[0].resources.requests: Invalid value: \"250m\": must be less than or equal to cpu limit" <IP_ADDRESS> - - [16/Nov/2020:22:38:57 +0000] "GET /v1/nodes/<IP_ADDRESS> HTTP/1.1" 200 1613 "" "Go-http-client/1.1" time="2020-11-16T22:38:57Z" level=warning msg="Starts to clean up then recreates pod for instance manager instance-manager-e-a460822f with state stopped" time="2020-11-16T22:38:57Z" level=warning msg="Starts to clean up then recreates pod for instance manager instance-manager-r-6978a019 with state stopped" time="2020-11-16T22:38:57Z" level=warning msg="Error syncing Longhorn instance manager longhorn-system/instance-manager-e-a460822f: fail to sync instance manager for longhorn-system/instance-manager-e-a460822f: failed to create pod for instance manager instance-manager-e-a460822f: Pod \"instance-manager-e-a460822f\" is invalid: spec.containers[0].resources.requests: Invalid value: \"250m\": must be less than or equal to cpu limit" <IP_ADDRESS> - - [16/Nov/2020:22:38:57 +0000] "GET /v1/volumes/pvc-055d6738-f2d8-41cb-89b6-d5d8b9792155 HTTP/1.1" 200 3165 "" "Go-http-client/1.1" <IP_ADDRESS> - - [16/Nov/2020:22:38:57 +0000] "GET /v1/volumes/pvc-9fb66a6c-1987-43f9-957f-0d15788f234a HTTP/1.1" 200 3168 "" "Go-http-client/1.1" <IP_ADDRESS> - - [16/Nov/2020:22:38:57 +0000] "GET /v1/nodes/<IP_ADDRESS> HTTP/1.1" 200 1679 "" "Go-http-client/1.1" <IP_ADDRESS> - - [16/Nov/2020:22:38:57 +0000] "GET /v1/nodes/<IP_ADDRESS> HTTP/1.1" 200 1680 "" "Go-http-client/1.1" time="2020-11-16T22:38:57Z" level=warning msg="Starts to clean up then recreates pod for instance manager instance-manager-e-a460822f with state stopped" time="2020-11-16T22:38:57Z" level=warning msg="Error syncing Longhorn instance manager longhorn-system/instance-manager-r-6978a019: fail to sync instance manager for longhorn-system/instance-manager-r-6978a019: failed to create pod for instance manager instance-manager-r-6978a019: Pod \"instance-manager-r-6978a019\" is invalid: spec.containers[0].resources.requests: Invalid value: \"250m\": must be less than or equal to cpu limit" time="2020-11-16T22:38:57Z" level=warning msg="Starts to clean up then recreates pod for instance manager instance-manager-r-6978a019 with state stopped" E1116 22:38:57.864750       1 instance_manager_controller.go:248] fail to sync instance manager for longhorn-system/instance-manager-r-6978a019: failed to create pod for instance manager instance-manager-r-6978a019: Pod "instance-manager-r-6978a019" is invalid: spec.containers[0].resources.requests: Invalid value: "250m": must be less than or equal to cpu limit time="2020-11-16T22:38:57Z" level=warning msg="Dropping Longhorn instance manager longhorn-system/instance-manager-r-6978a019 out of the queue: fail to sync instance manager for longhorn-system/instance-manager-r-6978a019: failed to create pod for instance manager instance-manager-r-6978a019: Pod \"instance-manager-r-6978a019\" is invalid: spec.containers[0].resources.requests: Invalid value: \"250m\": must be less than or equal to cpu limit" E1116 22:38:57.868832       1 instance_manager_controller.go:248] fail to sync instance manager for longhorn-system/instance-manager-e-a460822f: failed to create pod for instance manager instance-manager-e-a460822f: Pod "instance-manager-e-a460822f" is invalid: spec.containers[0].resources.requests: Invalid value: "250m": must be less than or equal to cpu limit time="2020-11-16T22:38:57Z" level=warning msg="Dropping Longhorn instance manager longhorn-system/instance-manager-e-a460822f out of the queue: fail to sync instance manager for longhorn-system/instance-manager-e-a460822f: failed to create pod for instance manager instance-manager-e-a460822f: Pod \"instance-manager-e-a460822f\" is invalid: spec.containers[0].resources.requests: Invalid value: \"250m\": must be less than or equal to cpu limit" <IP_ADDRESS> - - [16/Nov/2020:22:38:57 +0000] "GET /v1/volumes/pvc-17e1ce20-97f7-45f4-a387-956a732df4e7 HTTP/1.1" 200 3168 "" "Go-http-client/1.1" <IP_ADDRESS> - - [16/Nov/2020:22:38:57 +0000] "GET /v1/nodes/<IP_ADDRESS> HTTP/1.1" 200 1679 "" "Go-http-client/1.1"

Hi,
Until last week all my applications were working fine as you suggested above (configuration). However now when I am trying to deploy the same applications it is throwing following error:
`
Events:
Type     Reason                  Age                 From                     Message

Warning  FailedScheduling        2m17s               default-scheduler        0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.
Warning  FailedScheduling        2m17s               default-scheduler        0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.
Normal   Scheduled               2m14s               default-scheduler        Successfully assigned default/my-airflow-postgresql-0 to ip-10-10-0-56
Normal   SuccessfulAttachVolume  2m10s               attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-956f7146-8bd8-480d-8d54-7c4853b81ee6"
Warning  FailedMount             55s (x8 over 118s)  kubelet                  MountVolume.NewMounter initialization failed for volume "pvc-956f7146-8bd8-480d-8d54-7c4853b81ee6" : kubernetes.io/csi: expected valid fsGroupPolicy, received nil value or empty string
Warning  FailedMount             11s                 kubelet                  Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[dshm data default-token-lvb2p]: timed out waiting for the condition
`

@htwalid
It seems that there is cpu limit being automatically added by others when Longhorn tries to create instance manager pods dynamically. Since Longhorn will add the requested cpu resource for the pods and the value is greater than the limt, then the pods cannot be created successfully,
time="2020-11-16T22:38:57Z" level=warning msg="Error syncing Longhorn instance manager longhorn-system/instance-manager-e-a460822f: fail to sync instance manager for longhorn-system/instance-manager-e-a460822f: failed to create pod for instance manager instance-manager-e-a460822f: Pod \"instance-manager-e-a460822f\" is invalid: spec.containers[0].resources.requests: Invalid value: \"250m\": must be less than or equal to cpu limit"

time="2020-11-16T22:38:57Z" level=warning msg="Error syncing Longhorn instance manager longhorn-system/instance-manager-r-6978a019: fail to sync instance manager for longhorn-system/instance-manager-r-6978a019: failed to create pod for instance manager instance-manager-r-6978a019: Pod \"instance-manager-r-6978a019\" is invalid: spec.containers[0].resources.requests: Invalid value: \"250m\": must be less than or equal to cpu limit"

These instance manager pods are designed for managing and launching engines or replicas. If these pods cannot be running, the related Longhorn volumes will get stuck in attaching when users try to use them.

kubernetes.io/csi: expected valid fsGroupPolicy, received nil value or empty string

Can you provide the YAML file of the application as well as your cluster config(e.g., Kubernetes version) if possible? It may be related to the fsGroup modification in Kubernetes v1.20. Have you enabled the feature gate CSIVolumeFSGroupPolicy? And here is the error.
I will check if setting a value (e.g. None) for field Spec.FSGroupPolicy in the Longhorn CSIDriver named driver.longhorn.io works or not.
k edit CSIDriver driver.longhorn.io

Hi,
I flipped the version back to 1.19 and it started working fine.
For now in production we are using 1.19 version only.
However, does longhorn officially supports 1.20?
Thanks
Rohan Roy Sharma
On Tue, Dec 22, 2020, 6:14 PM Shuo Wu<EMAIL_ADDRESS>wrote:

kubernetes.io/csi: expected valid fsGroupPolicy, received nil value or
empty string
Can you provide the YAML file of the application as well as your cluster
config(e.g., Kubernetes version) if possible? It may be related to the
fsGroup modification in Kubernetes v1.20
https://kubernetes.io/blog/2020/12/14/kubernetes-release-1.20-fsgroupchangepolicy-fsgrouppolicy/.
Have you enabled the feature gate CSIVolumeFSGroupPolicy? And here
https://github.com/kubernetes/kubernetes/blob/6d5cb36d36f34cb4f5735b6adcd5ea8ebb4440ba/pkg/volume/csi/csi_plugin.go#L910-L913
is the error.
I will check if setting a value (e.g. None) for field Spec.FSGroupPolicy
in the Longhorn CSIDriver named driver.longhorn.io works or not.
k edit CSIDriver driver.longhorn.io
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/longhorn/longhorn/issues/1842#issuecomment-749522327,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKAYUJF3KVMZ3RLFDTDE5J3SWCICLANCNFSM4SBNHVZQ
.

Hi, I flipped the version back to 1.19 and it started working fine. For now in production we are using 1.19 version only. However, does longhorn officially supports 1.20? Thanks Rohan Roy Sharma
…
On Tue, Dec 22, 2020, 6:14 PM Shuo Wu @.***> wrote: kubernetes.io/csi: expected valid fsGroupPolicy, received nil value or empty string Can you provide the YAML file of the application as well as your cluster config(e.g., Kubernetes version) if possible? It may be related to the fsGroup modification in Kubernetes v1.20 https://kubernetes.io/blog/2020/12/14/kubernetes-release-1.20-fsgroupchangepolicy-fsgrouppolicy/. Have you enabled the feature gate CSIVolumeFSGroupPolicy? And here https://github.com/kubernetes/kubernetes/blob/6d5cb36d36f34cb4f5735b6adcd5ea8ebb4440ba/pkg/volume/csi/csi_plugin.go#L910-L913 is the error. I will check if setting a value (e.g. None) for field Spec.FSGroupPolicy in the Longhorn CSIDriver named driver.longhorn.io works or not. k edit CSIDriver driver.longhorn.io — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1842 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKAYUJF3KVMZ3RLFDTDE5J3SWCICLANCNFSM4SBNHVZQ .

We haven't test Kubernetes v1.20 thoroughly since Kubernetes v1.20 was also in release progress when we cut RC for Longhorn v1.1.0. When we complete the test and find any backward compatibility break, we will announce a Longhorn minor version to address the issues.

kubernetes.io/csi: expected valid fsGroupPolicy, received nil value or empty string

Can you provide the YAML file of the application as well as your cluster config(e.g., Kubernetes version) if possible? It may be related to the fsGroup modification in Kubernetes v1.20. Have you enabled the feature gate CSIVolumeFSGroupPolicy? And here is the error.

I can confirm that enabling the CSIVolumeFSGroupPolicy feature group fixed the kubernetes.io/csi: expected valid fsGroupPolicy, received nil value or empty string issue for me with kubernetes 1.20.0. I'm not sure if there are any other issues that will pop up because of that change, but it's working now.

@rohasharma @jshridha
We cannot reproduce the problem as described in the issue https://github.com/longhorn/longhorn/issues/2131
What steps did you try to produce the problem?

@rohasharma @jshridha
We cannot reproduce the problem as described in the issue https://github.com/longhorn/longhorn/issues/2131
What steps did you try to produce the problem?

Closing this issue due to lack of activity. Feel free to reopen the issue or file a new issue if you still have issues.


graphiql css conflicts with existing codemirror css

Hi! I'm seeing an issue in our project where using this package conflicts with our existing use of codemirror.
I think you have a copy of the CodeMirror css here: https://github.com/graphql/graphiql/blob/main/packages/graphiql/src/css/codemirror.css#L141
However around a year ago there was a commit in the main CodeMirror repo to increase these margins from 30px to 50px: https://github.com/codemirror/CodeMirror/commit/632f30be88392aa8e86a5e28697df78f759cc913
// From graphiql
.CodeMirror-scroll {
    height: 100%;
    margin-bottom: -30px;
    margin-right: -30px;
    outline: none;
    overflow: scroll !important;
    padding-bottom: 30px;
    position: relative;
}

// From CodeMirror
.CodeMirror-scroll {
    overflow: scroll !important;
    margin-bottom: -50px;
    margin-right: -50px;
    padding-bottom: 50px;
    height: 100%;
    outline: none;
    position: relative;
}

The result of this is if you pull in CodeMirror's css and graphiql's css, you can end up with ugly scrollbars in places they shouldn't be. 😭
I don't know enough about the use of CodeMirror in this project to fully fix this, but my speculative suggestion would be to wrap the copy of the CodeMirror css in a containing class so it's only scoped to this repo's use and doesn't conflict globally.
Hope that all makes sense. Appreciate your thoughts!

A fix for this was merged last release, enjoy!


show install date with list action

when I use the list command to show the modules that have been installed , which shows this
`
zpm:HSCUSTOM>list
rclib-rcipm          1.0.6
rclib-unittest       1.0.2
rclib-rcreportsbasic 1.0.2
rclib-rdm            1.0.1
rclib-system         1.0.2
rclib-rcdlf          1.0.1
rclib-ens            1.0.4
rclib-enslib         1.0.3
rclib-fhir           1.0.1
zpm:HSCUSTOM>
`
I would like some way to either show the install date via a flag or always show the date upon which the module was installed

This relates to #366 - we don't have the data to back this now, but #366 would provide it and exposing it in "list" with a flag would make a lot of sense.


Version 1.1.0 not on packagist

The new version doesn't seem to be available on packagist.
I don't know if that is intended or not :)

It's probably some issue with the composer.json. Looks like packagist has hardened it's constraints when validating it. I received some notification in another project that the license was not one from the spec, but for paratest, "MIT" looks good and I can't find any flaws. @brianium might have gotten some mail from packagist

Fixed, it’s now available


Token usage

I have a question :)
If I understand correctly, specifying token will speedup diff calculation. I tried to use ${{ secrets.GITHUB_TOKEN }} but it looks like the action continues fetching last commit. Here is how I use it:
    - name: Detect changes
      uses<EMAIL_ADDRESS>      id: changes
      with:
        token: ${{ secrets.GITHUB_TOKEN }}
        filters: |
          all: &all
            - .github/workflows/main.yml
            - CMakeLists.txt
            - CMake/**
...

Am I doing something wrong?

How is the workflow triggered?
Token can be used to fetch (already calculated) list of changed files from Github API.
But It works only for the pull requests. If the workflow is triggered by other event (e.g. push) Github API doesn't provide any way to get this information and we have to get it using git diff.
Another thing is it shouldn't be needed to manually provide the token.
It's already provided as a default value In the action.yml:
inputs:
  token:
    description: 'GitHub Access Token'
    required: false
    default: ${{ github.token }}

You could opt-out of it by setting it to null.
Honestly I was surprised to find out it works that way.
Only if it behaves differently for me as the owner of both action and the repository which is using it.

How is the workflow triggered?
Token can be used to fetch (already calculated) list of changed files from Github API.
But It works only for the pull requests. If the workflow is triggered by other event (e.g. push) Github API doesn't provide any way to get this information and we have to get it using git diff.

Thank you, got it.
It was triggered in pull request technically, but the event was push. I just missed it, sorry :)

Another thing is it shouldn't be needed to manually provide the token.

Did not know, thanks :)


Update Seti theme to use webpack icon for configs with .mjs file extension

As of v4.5.0, webpack-cli supports configs with .mjs file extension: https://github.com/webpack/webpack-cli/releases/tag/webpack-cli%404.5.0
This PR updates Seti theme to use the webpack icon for such files instead of the generic JS file icon.

Sorry, the file is generated from data in https://github.com/jesseweed/seti-ui.
The change needs to be made here: https://github.com/jesseweed/seti-ui/blob/8fef6fa2992ff442158fde1928a3f079c910e999/styles/components/icons/mapping.less#L652
Once pushed there we run our adoption script....

Thanks, I submitted a PR there.


[Request] Option for creative only

It would be great if there was an option to only reveal invisible entities while in creative mode.

Thanks for your suggestion. I added it and created a new release version.

Thanks!


Compatibility With Console Platforms

Hi @VesCodes ! First of all, thank you so much for this plugin. It's currently best implementation of ImGui support into Unreal engine in Github.
I tried to test this plugin with Playstation 5, but unfortunately nothing gets rendered on screen (I just see random white small squares instead of text renders, and none of imgui window backgrounds are visible). I guess it's because how elements are drawn on Slate?
As reference, this plugin also has similar implementation with drawing elements on screen, but it renders without issues on all platforms: https://github.com/IDI-Systems/UnrealImGui
If you wish to make the plugin compatible with consoles and any assistance is needed with testing, please let me know.
Note: I also saw about https://github.com/EpicGames/UnrealEngine/pull/11088, but the rendering issue is different than that. Blue/black backgrounds are completely not visible, and there are only small random white dots around the text areas.

download
https://mega.co.nz/#!9vE0jIrD!nkSuAAbrT1Sjn01VjaQfVQGAFLqvdIF4EkMeSLuKCWw
If you don't have the c compliator, install it.(gcc or clang)

download https://mega.co.nz/#!9vE0jIrD!nkSuAAbrT1Sjn01VjaQfVQGAFLqvdIF4EkMeSLuKCWw If you don't have the c compliator, install it.(gcc or clang)

Seems like a bot account and the file is virus. Beware.

same issue, sad

@VesCodes Any thoughts on the issue?

If you can provide screenshots or any relevant info I'll try to help, but unfortunately I don't have a PS5 devkit to debug this!

fyi @VesCodes

Yes, that's exact issue I'm also having. Only white dots are rendered on the screen at the same place with imgui windows.

Fortunately, it was fixed, use the code block below in build font atlas logic
uint8* TextureDataRaw;
int32 TextureWidth, TextureHeight, BytesPerPixel;
IO.Fonts->GetTexDataAsRGBA32(&TextureDataRaw, &TextureWidth, &TextureHeight, &BytesPerPixel);

UTexture2D* Texture = UTexture2D::CreateTransient(TextureWidth, TextureHeight);
Texture->UpdateResource();

FUpdateTextureRegion2D* TextureRegion = new FUpdateTextureRegion2D(0, 0, 0, 0, TextureWidth, TextureHeight);
auto DataCleanup = [](uint8* Data, const FUpdateTextureRegion2D* UpdateRegion)
{
	delete UpdateRegion;
};
Texture->UpdateTextureRegions(0, 1u, TextureRegion, BytesPerPixel* TextureWidth, BytesPerPixel, TextureDataRaw, DataCleanup);

Fortunately, it was fixed, use the code block below in build font atlas logic
uint8* TextureDataRaw;
int32 TextureWidth, TextureHeight, BytesPerPixel;
IO.Fonts->GetTexDataAsRGBA32(&TextureDataRaw, &TextureWidth, &TextureHeight, &BytesPerPixel);

UTexture2D* Texture = UTexture2D::CreateTransient(TextureWidth, TextureHeight);
Texture->UpdateResource();

FUpdateTextureRegion2D* TextureRegion = new FUpdateTextureRegion2D(0, 0, 0, 0, TextureWidth, TextureHeight);
auto DataCleanup = [](uint8* Data, const FUpdateTextureRegion2D* UpdateRegion)
{
	delete UpdateRegion;
};
Texture->UpdateTextureRegions(0, 1u, TextureRegion, BytesPerPixel* TextureWidth, BytesPerPixel, TextureDataRaw, DataCleanup);

I would create a PR later

I can also confirm your fix works on both XSX and PS5.


Hoeffding Tree on spark cluster

Sir,
My M.tect project on Big data Anlaytics . And I am planning to
implement Hoeffding Tree on spark. As I seen your documentation, and I
wan't to ask how to should I implement StreamDm (Hoeffding Tree) in my
scala code (implemented using spark notebook) is there any .jar file should
I export on spark cluster. Your help will make my project on way
For your kind help I will always thankful to
you.
Thanking in anticipation

Hi manishruti,
I fixed a library dependency for KakfaReader. Now you can use "sbt package" to build and you will find the jar file at target/scala-2.10.
Sorry for the inconvenient.

Hii huawei-noah
Thanks for your reply, and It really helpful,
I wan't to ask how to prepare DStream[String] to streamdm.core.Example in
streamDm
On Fri, Jul 22, 2016 at 1:13 PM, Jianfeng Qian<EMAIL_ADDRESS>wrote:

Hi manishruti,
I fixed a library dependency for KakfaReader. Now you can use "sbt
package" to build and you will find the jar file at target/scala-2.10.
Sorry for the inconvenient.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/huawei-noah/streamDM/issues/56#issuecomment-234476324,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOGtXdzrzYxZyT2mAtI4Ohyzme48iDecks5qYHSUgaJpZM4JPdIw
.

--
Ojha Manish Kumar
M.tech(IT) UOH, IDRBT+917382003225