Rostland Bravo doesn't apply Swashbuckler Finesse to Dueling sword.

I mean, no Swashbuckler apply the Finesse to that weapon, but it seems that the bravo should. If you pick weapon finesse mythic the damage roll change to dex, but the str atack roll is still there.

you are wielding it one handed right?

I have tried both one and two-handed. The other weapons apply dex even when two-handed, i didn't know that should not work.

rostland bravo has the same swashbuckler finesse as other archetypes. all it gains is dueling sword proficiency. so, you'll need to take aldori dueling mastery to treat it as a swashbuckler weapon.
kinda silly, honestly, but thats what the rules say unless im misreading it.

I made the testing and you are right:

The finnesse works with dueling if you pick "aldori dueling mastery". For all the other archetypes it doesn't seems to be bad, but for the bravo it is weird and deeply underwelhming, I have seen that it was an error the writters of the tabletop had. I truly recommend to add the aldori feat in level 1 or to completly remove the piercing finesse for the Bravo and remake the archetype. A tax-feat that is mandatory if you want to use some of the deeds made the Bravo very confusing (i need to be a regular swas until level 3, and then... do i change my combat technique?)
In that particular case i truly recommend to take distance from TT and make the change, as WOTR is more min-max and class-optimized than a regular pathfinder campaing

The finesse works with dervish dance and slashing grace. That makes the class more fun, as you can be a agile fighter even with axes, jaja.

Ty for the time to answer me and for the work to adapt the class to the game

i agree. i will make the change if/when i get back to modding, which might be when the dlc drops. will keep the issue open so i dont forget.
and thank you for your kind words, glad you enjoyed swashbuckling.

rostland bravo now gets aldori dueling mastery as a bonus feat


Inlined FluidIndex methods to fix issue #9

Inlined FluidIndex methods to fix issue #9

Checked against Supercollider tests, all seems fine. Many thanks

No probs


[tool_crash] StateError: Bad state: Existing VM service clients prevent DDS from taking control.

Command
flutter --no-color run --machine --verbose --track-widget-creation --device-id=BVK6R19426005588 --start-paused --dart-define=flutter.inspector.structuredErrors=true lib\main.dart

Steps to Reproduce

...
...
...

Logs
StateError: Bad state: Existing VM service clients prevent DDS from taking control.
#0      DartDevelopmentService.startDartDevelopmentService (package:flutter_tools/src/base/dds.dart:83:11)
<asynchronous suspension>
#1      FlutterDevice.connect.<anonymous closure> (package:flutter_tools/src/resident_runner.dart:249:11)
<asynchronous suspension>

[✓] Flutter (Channel dev, 1.26.0-8.0.pre, on Microsoft Windows [Version 10.0.19042.746], locale en-US)
    • Flutter version 1.26.0-8.0.pre at C:\src\flutter
    • Framework revision b9d06fffb2 (2 weeks ago), 2021-01-07 18:36:48 -0800
    • Engine revision 42a8d4c681
    • Dart version 2.12.0 (build 2.12.0-179.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\USER\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: C:\Program Files\Android\Android Studio1\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[✓] Android Studio (version 4.1.0)
    • Android Studio at C:\Program Files\Android\Android Studio1
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[✓] Connected device (2 available)
    • DUB LX1 (mobile)        • BVK6R19426005588 • android-arm64 • Android 8.1.0 (API 27)
    • sdk gphone x86 (mobile) • emulator-5554    • android-x86   • Android 11 (API 30) (emulator)

• No issues found!

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version:<PHONE_NUMBER>7c3a836feee883712c241a5fd22983
Plugins
flutter_keyboard_visibility-4.0.2
flutter_keyboard_visibility_web-1.0.1

Similar (maybe duplicate) to https://github.com/flutter/flutter/issues/74033?!

Similar (maybe duplicate) to https://github.com/flutter/flutter/issues/74033?!

@bkonyi this looks like https://github.com/flutter/flutter/issues/66557 again?

@bkonyi this looks like https://github.com/flutter/flutter/issues/66557 again?

Yes, that's the same failure, but should be resolved by this CL which landed in the framework a week or two ago. We shouldn't be seeing this once we release the next beta.

Yes, that's the same failure, but should be resolved by this CL which landed in the framework a week or two ago. We shouldn't be seeing this once we release the next beta.


otecol-data-flow-dashboard documentation

replacement for feature/otecol-data-flow-dashboard-PR797

Woohoo! Glad that this has landed. Thanks @devrimdemiroz! ✨

Woohoo! Glad that this has landed. Thanks @devrimdemiroz! ✨

@chalin Thank you for sharing your insights and recommendations in general and especially about the positioning of images in the document. After publishing, I have come to understand the validity of your perspective.
I am grateful for your patience and cooperation as we navigated this issue together.
Collaborating with someone as skilled and experienced as you is always a great experience. I appreciate your constructive feedbacks, which has undoubtedly contributed to the quality of the document.

@devrimdemiroz this is awesome! Thanks you!


Implement transaction fee collection

In order to support transaction replacement via bigger fees (https://github.com/bpfkorea/agora/issues/245), we also need to implement fee collection first.
Each transaction's fee is defined as the Sum(Inputs) – Sum(Outputs).
In Bitcoin, collecting the fees is simple. The single miner which mined the block generates a Coinbase transaction which includes all of the transactions' combined fees and outputs them all to the miner's desired public key.
In our case, it's different. We don't have miners, we have consensus nodes. Therefore the fee needs to be distributed among the validator nodes. There are some open questions:

How are the fees distributed among the nodes? Are they distributed evenly towards all (non-slashed) validators? Or does distribution depend on other factors such as: stake amount, number of total externalized Enrollments for that node..?
After fee distribution is decided how do we update the UTXO set? In Bitcoin they use the Coinbase transaction for this. Do we need something similar? Or could we make it implicit in the protocol and not add any additional transactions to the block? If it's implicit then after externalization the UTXO set would need to be automatically updated to add new UTXOs to each validator node (the fees). But we need to be careful here because we're creating UTXOs from thin air basically. Maybe a Coinbase transaction would still be a better option.

I think Coinbase transactions are way to go, implicitly generating UTXOs is too error-prone.
The problem is that this may not scale as the network grows. Potentially thousands of Validators could be enrolled each block. If we pay the fees for each Validator every block this would create a lot of bloat. Thousands of Coinbase transactions with very small amounts of coin, every block.
What do you think of paying the fees of a Validator at the end of it's cycle? Fees that would be paid to a Validator is accumulated and paid in a single Coinbase transaction on the last Block they are enrolled. We would make it a part of the protocol/block validation so that the Coinbase transactions would not be voted off in consensus.
Any opinions?

You raise excellent points. I fully agree, once per validator cycle would be ideal.

However with the CoinBase approach there is an issue that there's more data that needs to be kept in the block and sent over the network. That's why I suggested making it implicit might be better in terms of saving costs on total block storage size. Then again the total amount of outputs in Coinbase wouldn't necessarily be that big. Let me know what you think.

However with the CoinBase approach there is an issue that there's more data that needs to be kept in the block and sent over the network. That's why I suggested making it implicit might be better in terms of saving costs on total block storage size. Then again the total amount of outputs in Coinbase wouldn't necessarily be that big. Let me know what you think.

Yep, there is that. But with 1008 blocks validator cycle, on average, we would have 1 coinbase tx for every 1000 Validators per block. Probably negligible. But I would sugggest that we take the easier and probably safer route of using Coinbase TX for now. We can later evaluate the overhead in TestNet?

Sure. Then I think coinbase is the right first approach.

How are the fees distributed among the nodes?

About this, I am thinking of initial implementation to be purely stake amount based. But there could be cases where the total fee can't be divided properly.
Simplest example is distributing 5 BOA among 4 Validators with equal stake. The process should be both fair to all Validators and  should probably be deterministic to simplify the validation process. Even if we factor in additional stuff, we still might end up in a state where multiple nodes have exact same priority.
I noticed the CommonsBudgetAddress, could we use this to deposit the change BOA we can't easily distribute among Validators?

Even if we factor in additional stuff, we still might end up in a state where multiple nodes have exact same priority.

In theory this shouldn't be a problem for example we could just look at the hash of the previous block as a random number and then we would distribute extra coins to validators in the following way: first the validator with the smallest public key hash gets the coin, however his public key hash has to be greater than the 'random' number of the previous block hash. (we need this random number because we don't want attackers pregenerate keys with the lowest possible public key hash to have a high chance of getting the extra coins)
I am not saying we should do this, your idea of distributing extra coins to CommonsBudgetAddress is better

Sending the remainder to the commons budget sounds better to me too.

Data fees are currently expected to be paid by the wallet in each transaction.
https://github.com/bpfkorea/agora/pull/1368
https://github.com/bpfkorea/agora/pull/1321
As far as I can see, these PRs dont follow what white paper defines, in terms of the 70/30 split between validators and commons budget. Also, do we really want the wallet to explicitly create the payment output to commons budget? Transfers to commons budget could very well be done with a single Coinbase TX per block, saving a bunch of space in a block. Also this makes the wallet implementation more complex too, all the edge cases we will cover in the Validator, like the ones mentioned in this issue, would be replicated in the wallet too.

Transfers to commons budget could very well be done with a single Coinbase TX per block, saving a bunch of space in a block. Also this makes the wallet implementation more complex too, all the edge cases we will cover in the Validator, like the ones mentioned in this issue, would be replicated in the wallet too.

You mean the coinbase idea would make the wallet implementation more complex, or the current implementation is making it more complex?
In general I agree that collecting all the fees into the commons budget is not ideal. Because then nobody is paying the validators for the storage fee. So there is very little incentive of actually wanting to include such a transaction in the block. But I'm not sure if the c-level wants to change this (when I say c-level I am excluding the CTO). It was their executive decision that the entirety of the data payload fee has to be sent to the commons budget.

You mean the coinbase idea would make the wallet implementation more complex, or the current implementation is making it more complex?

I was talkıng about the existing implementation making the wallet more complex, because it would need to handle the 70/30 split as well. But since the data fees would all go to the commons budget, wallet may not be any more complex.
What is your take on not including commons budget outputs in each tx with payload? Instead we would just create one Coinbase TX per block, that would pay all the data fees and the %30 from the regular tx fees.

It sounds good to me if we can make the wallet less complex.

On the side note, paying each Validator at the end of their cycle requires the ability to get a list of Validators of any Block in the past. Without any additions to the existing code, I think, only way to do this is walk the entire chain. We have to walk the entire chain because we don't have a maximum value defined for validator cycles yet.
We could either store this information in ValidatorSet or could we extract it from the block signatures that was just implemented? :)

What do you mean "entire chain"?  Unless I misunderstood your question?

So, we are at block height H and Validator #0's cycle of N blocks is about to end.
We need to calculate the fees for Validator #0 in Block H-N to Block H. For every block in this range, we would need to know the other Validators that are active on that height and their stake amount. Validator set for each block could be different.
To get a Validator set of Block height K there is no other way than checking enrollments of all the blocks up to K. Since they could've been enrolled in any point. If we had an upper bound for cycle_length we would need to scan starting from Block K - max_cycle_lengthand going upward.
Hope that makes sense.

Since currently the cycle length (or max cycle length) is set in the consensus params, you could get away with just always keeping the list of active validators per block for the last 1008 blocks. So current height - 1008.
Of course if we allowed custom cycle lengths then it's a bit different.
In any case I think we would need to come up with an efficient data structure to keep track of the active validators.

The white paper describes the transaction fee as follows the transaction fee.
Transaction Fee: The transaction fee is a fixed 0.01 BOA. Congress Nodes receive
70% of the collected transactions fee in a block, and 30% is sent to the Commons
Budget. Transaction fees can be adjusted through the Congress.

@omerfirmak 's points are excellent (and I think we already discussed this):

Distribution needs to be periodic, not with every block;
Said fee should be derived directly from the protocol, so everyone with the same history will reach the same transaction;

Data fees are currently expected to be paid by the wallet in each transaction.

Source.
Data fee are different. They are additional fees (on top of the tx fee), and don't follow the same rules. The only relationship they have is that they are minored by the tx fee (at least that was the original idea).

Note that my original idea was to distribute every X blocks (with X = 144 for example, aka 1 day) so that everyone is paid at the same time. As we want a stale network, keeping validators on as long as possible is desirable, hence we should be careful not to influence them into having shorter cycles so that the payout is more frequent.

@omerfirmak 's points are excellent (and I think we already discussed this):
1. Distribution needs to be periodic, not with every block;

2. Said fee should be derived directly from the protocol, so everyone with the same history will reach the same transaction;

Data fees are currently expected to be paid by the wallet in each transaction.

Source.
Data fee are different. They are additional fees (on top of the tx fee), and don't follow the same rules. The only relationship they have is that they are minored by the tx fee (at least that was the original idea).

So, do we keep the per-TX output to the commons budget? For the data fees.

Note that my original idea was to distribute every X blocks (with X = 144 for example, aka 1 day) so that everyone is paid at the same time. As we want a stale network, keeping validators on as long as possible is desirable, hence we should be careful not to influence them into having shorter cycles so that the payout is more frequent.

With this, every Xth block will probably be larger than the other blocks. This could become significant with a large number of Validators.


1398607 rajibugfix

Issue nos.2421 and 2169 are addressed with this PR. Please review

Docs Build status updates of commit 2b3bac8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/Cards/carousel.png
:white_check_mark:Succeeded
View

msteams-platform/messaging-extensions/how-to/action-commands/create-task-module.md
:white_check_mark:Succeeded
View

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

That JSON in the PR is not correct. That Adaptive Card has to be wrapped in a Task object.


"disconnected" after "go to definition"

Issue Type: Bug
When you select "go to definition" of a view or store procedure (SQL Server) you appear as disconnected, and you have to reconnect in order to work. It would be good to be connected to the same connection of the original view or procedure.
Azure Data Studio version: azuredatastudio 1.13.1 (d08d07fe39c7fe74f9265db02cb963c38d048299, 2019-11-14T23:08:09.800Z)
OS version: Windows_NT x64 6.3.9600

System Info

Item
Value

CPUs
Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz (8 x 2195)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: unavailable_offprotected_video_decode: unavailable_offrasterization: unavailable_offskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
16.00GB (2.16GB free)

Process Argv

Screen Reader
no

VM
100%

Extensions: none

Thanks for the feedback! I'm closing this as a duplicate of https://github.com/microsoft/azuredatastudio/issues/6298 - you can track that one for status updates.


Error: Uncaught TypeError: Cannot read properties of undefined (reading 'load') for index.html

Describe the bug
Page sits and spins, trying to load forever, only message is in browser developer tools console see:
"Uncaught TypeError: Cannot read properties of undefined (reading 'load') for index.html
at (index):206:30"
To Reproduce
Steps to reproduce the behavior:
Upgrade from Flutter SDK 3.19 to 3.22 or 3.24, without making any code changes.
Run with newer SDK and see deprecation errors.
Follow recommendations from deprecations errors to modify code in index.html script sections for flutter servicer worker and flutter loader changes.
clean, get, build, run.
See error.
Expected behavior
Flutter loader deprecation issues should be addressed, and web page should load normally, not hang.
Screenshots

Environment (please complete the following information):

OS: This is a Flutter Web application.

Experience the error on Windows, Mac, and Linux, with multiple versions of Chrome and Firefox.
flutter doctor -v
[✓] Flutter (Channel stable, 3.24.1, on macOS 14.5 23F79 darwin-arm64, locale en-US)
• Flutter version 3.24.1 on channel stable at /Users/User/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision https://github.com/flutter/flutter/commit/5874a72aa4c779a02553007c47dacbefba2374dc (2 days ago), 2024-08-20 16:46:00 -0500
• Engine revision c9b9d5780d
• Dart version 3.5.1
• DevTools version 2.37.2

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /Users/User/Library/Android/sdk
• Platform android-34, build-tools 34.0.0
• ANDROID_HOME = /Users/User/Library/Android/sdk
• ANDROID_SDK_ROOT = /Users/User/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
• All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 15F31d
• CocoaPods version 1.15.2

[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

[✓] VS Code (version 1.90.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.94.0

[✓] Connected device (2 available)
• Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin • macOS 14.5 23F79 darwin-arm64
• Chrome (web) • chrome • web-javascript • Google Chrome 127.0.6533.120

[✓] Network resources
• All expected network resources are available.

• No issues found!

Additional context
We upgraded from 3.19.5 to 3.24.0 (also tried with 3.22.3 but had same problem), and now upgraded to 3.24.1.
After upgrading, then  received messages during build and run about deprecation:
* Warning: In index.html:69: Local variable for "serviceWorkerVersion" is deprecated. Use "{{flutter_service_worker_version}}" template token instead. See https://docs.flutter.dev/platform-integration/web/initialization for more details.

* Warning: In index.html:189: "FlutterLoader.loadEntrypoint" is deprecated. Use "FlutterLoader.load" instead. See https://docs.flutter.dev/platform-integration/web/initialization for more details.

Tried dart pub cache clean, flutter clean, flutter pub get, flutter build web.
Still have the same error (and page sits and spins forever waiting to load with no other error messages):
We were abble to address the Service Worker error by updating syntax. Unfortunately, updating syntax for Flutter Loader, leads to this reported error and unusable app. The upgrade is working or the {{flutter_service_worker_version}} upgrade, but still broken for the FlutterLoader.load.
This line change from the previous code triggers the error
"_flutter.FlutterLoader.load({"
If revert that line back to deprecated syntax, then the page will load normally:
"_flutter.loader.loadEntrypoint({"
But then of course get the deprecation warning returns:
"Warning: In index.html:206: "FlutterLoader.loadEntrypoint" is deprecated. Use "FlutterLoader.load" instead. See
https://docs.flutter.dev/platform-integration/web/initialization for more details."

Any additional suggestions what I can try on our end to address this? Anything else you need from me to help track this down? Should I create this as a new ticket issue?
Here is the whole script snippet for the web/index.html template (any syntax or other issues that might be contributing this perhaps?):
<script>
    function delay(time) {
      return new Promise(resolve => setTimeout(resolve, time));
    }

    window.addEventListener('load', function (ev) {
      // Download main.dart.js
      _flutter.FlutterLoader.load({
        serviceWorker: {
          serviceWorkerVersion: '{{flutter_service_worker_version}}',
        },
        onEntrypointLoaded: function (engineInitializer) {
          var loaderContent = document.querySelector('#loader-content');

          engineInitializer.initializeEngine().then(async function (appRunner) {
            loaderContent.style.opacity = "0";
            await delay(400);
            await appRunner.runApp();
          });
        }
      });
    });
  </script>

Hi @hawkewebtpa, before applying the custom initialization script, can you try what is at the end of the doc to see if that helps? https://docs.flutter.dev/platform-integration/web/initialization#upgrade-an-older-project

Trying the suggested approach. Will report back soon.

I have tried this process (did I make any errors along the way?):
Back up the /web directory and all contents to somewhere outside of the flutter project folder, for example cp -Rf ./web ../../web.old (so that I can incrementally bring back our content and code after web template rebuild).
Remove the web template directory completely from the project.
Remove the test/widget_test.dart file.
Then from inside the flutter project directory run: flutter create . --platforms=web .
If this is the first time working on this upgrade, you probably should clear out your dart cache before going any further: dart pub cache clean (or flutter pub cache clean)f. You probably don't need to do this every time, just if you have been working on older/different SDK versions than this one (3.24.1). This will impact all of your flutter projects on your system for this (OS) login account directory structure.
Then flutter clean (run every time).
Then flutter pub get (run every time).
Then flutter build web.
I had to also copy the backed up scripts directory into the new web directory (from the root of the project directory): cp -R ../../web.old/scripts web/ and other called files used in this app.
At this point, I am now able to load the login screen, login successfully, run through the forum submissions process.
And that partially resolved in that the page loads now instead of just hanging. However I still see error in browser console: "Uncaught TypeError: Cannot read properties of undefined (reading 'load')".

Also now, later in our flow of form submission, a new error occurs that isn't there before these changes: ". Message: failed to create draft ApiException 500: {"type":"https://tools.ietf.org/html/rfc7231#section-6.6.1","title":"An error occurred while processing your request.","status":500,"detail":"Object reference not set to an instance of an object.","traceId":"|85e045bc-43fbb9e6173ab2fd.85e045bd_5de9a763_"}".   Not sure if related or not.
Perhaps a conflict, or issue with syntax as I bring back our required code changes? Perhaps wrong order?
Appreciate any further suggestions. Thanks!
index.html now looks like this (with some redactions as underlines):

____________

<!-- End Code Addition -->

<script src="flutter_bootstrap.js" async></script>

<!-- The script below installs service_worker.js to provide PWA functionality to
   application. For more information, see:
   https://developers.google.com/web/fundamentals/primers/service-workers -->

<script>
  function delay(time) {
    return new Promise(resolve => setTimeout(resolve, time));
  }

  window.addEventListener('load', function (ev) {
    // Download main.dart.js
    // For _______ changed syntax below from serviceWorkerVersion due to deprecation in Flutter SDK 3.22 or later
    // recommend using Flutter SDK 3.24.1 or later due to significant bug fixes.
    // Still working on addressing Flutterloader.loadEntrypoint deprecation issue in separate ticket _________.
    // More detailed information in ______ wiki:
    // https://_________/_______/_wiki/wikis/Documentation/Index.html-Deprecation-Warnings
    _flutter.FlutterLoader.load({
      serviceWorker: {
        serviceWorkerVersion: '{{flutter_service_worker_version}}',
      },
      onEntrypointLoaded: function (engineInitializer) {
        var loaderContent = document.querySelector('#loader-content');

        engineInitializer.initializeEngine().then(async function (appRunner) {
          loaderContent.style.opacity = "0";
          await delay(400);
          await appRunner.runApp();
        });
      }
    });
  });
</script>

<!-- End Code Addition -->

I am still delving into this, trying to remove the other third-party scripts and our code dependencies to figure out why it is still failing.

And that partially resolved in that the page loads now instead of just hanging. However I still see error in browser console: "Uncaught TypeError: Cannot read properties of undefined (reading 'load')".

At what point in your application do you get this error?
I also noticed you have both flutter.js && flutter_bootstrap.js in your index.html file. It doesn't seem like the flutter.js import is necessary. The new index.html does not include it. You can also do the custom initialization with just the flutter_bootstrap.js. See https://docs.flutter.dev/platform-integration/web/initialization#customize-initialization onwards
<!DOCTYPE html>
<html>
<head>
  <!--
    If you are serving your web app in a path other than the root, change the
    href value below to reflect the base path you are serving from.

    The path provided below has to start and end with a slash "/" in order for
    it to work correctly.

    For more details:
    * https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base

    This is a placeholder for base href that will be replaced by the value of
    the `--base-href` argument provided to `flutter build`.
  -->
  <base href="$FLUTTER_BASE_HREF">

  <meta charset="UTF-8">
  <meta content="IE=Edge" http-equiv="X-UA-Compatible">
  <meta name="description" content="A new Flutter project.">

  <!-- iOS meta tags & icons -->
  <meta name="apple-mobile-web-app-capable" content="yes">
  <meta name="apple-mobile-web-app-status-bar-style" content="black">
  <meta name="apple-mobile-web-app-title" content="webby">
  <link rel="apple-touch-icon" href="icons/Icon-192.png">

  <!-- Favicon -->
  <link rel="icon" type="image/png" href="favicon.png"/>

  <title>webby</title>
  <link rel="manifest" href="manifest.json">
</head>
<body>
  <script src="flutter_bootstrap.js" async></script>
</body>
</html>

Making progress.
With 3.24.0 it previously it was happening as the index.html page loaded (which is the login prompt page).
"Uncaught TypeError: Cannot read properties of undefined (reading 'load') for index.html at (index):206:30"
This was originally happening loading the index.html page and the screen would just spin.
Running the rebuilt project web steps suggested earlier in this thread, helped solve loading the front page, and shows the login page successfully. The login works, but as the user's home page / dashboard loads, as slight variation on the same error appears:
Uncaught TypeError: Cannot read properties of undefined (reading 'load')
Now the error occurs right after the login as the user's home page / dashboard loads. So it is definite progress, but clearly something still off. We are utilizing Azure ADB2C as part of our authentication infrastructure.
I pulled the line with flutter.js and just kept the flutter_bootstrap.js, I am not seeing a difference in error output from that change, but appreciate that correction.
I am also reaching out and experimenting with disabling/isolating the other plugins like Pendo (93 instances across 13 files) to see if they are causing an interaction issue triggering this similar error message.
Any suggestions for specific things to look out for as I wade through main.dart and the other files that might be relevant to this error?
Thanks!

@hawkewebtpa Something that I've noticed from your example is that the old and new JS bootstrap methods are mixed:

The flutter.js script and the window.addEventListener('load'... stuff
The flutter_bootstrap.js script

You should want only the second one with Flutter web 3.24+.
Please try to move your custom initialization code (the bits in the load callback) into a new file: flutter_bootstrap.js (should be next to index.html). We have some instructions and examples of the flutter_bootstrap.js file in the flutter docsite.
See:

flutter.dev > Flutter web app initialization (With lots of information about the flutter_bootstrap.js file).
https://github.com/flutter/devtools/issues/7444

Have run into issue with third-party plugin acting up with this change to which is added to challenges debugging and getting response back about this. Still work on this and will report back as soon as able. Trying to clean out the interfering third-party plugins to get cleaner testing of issue here.

U am still trying to weed out the third-party vendors interference with troubleshooting this (or if it is is a specific plugin that is causing this (for example pendo.js)).
This is still unresolved, but hopefully I will have something more useful to report in the next 2-3 days.


Memory control

https://swiftwalker.vercel.app/memory-control?
A quick overview of how memory is managed in Swift. From the article, it will become clearer to you what improvements have occurred in the transition from Objective-C to Swift and how this has affected modern development.

Test

Test

Answer


[WIP] Openstack neutron complex network env builder and tests

need to finish 2 ports association to VM builder and tests

continues expanded with models clean up in https://github.com/ManageIQ/manageiq/pull/6043


all: update after we've renamed from Id to ID

Also, update a couple docker images we use in tests to their latest release.

Codecov Report

Merging #221 into master will decrease coverage by 4.21%.
The diff coverage is 57.41%.

@@            Coverage Diff             @@
##           master     #221      +/-   ##
==========================================
- Coverage    57.9%   53.69%   -4.22%
==========================================
  Files          31       31
  Lines        4274     4274
==========================================
- Hits         2475     2295     -180
- Misses       1310     1516     +206
+ Partials      489      463      -26

Impacted Files
Coverage Δ

http.go
81.13% <0%> (ø)
:arrow_up:

internal/filetransfer/config.go
55.11% <0%> (-0.79%)
:arrow_down:

accounts.go
10.95% <0%> (-69.87%)
:arrow_down:

ofac.go
38.65% <43.75%> (-35.3%)
:arrow_down:

receivers.go
48.04% <47.36%> (ø)
:arrow_up:

transfers_ccd.go
84.21% <50%> (ø)
:arrow_up:

file_transfer_async.go
48.68% <54.54%> (ø)
:arrow_up:

depositories.go
58.11% <55%> (ø)
:arrow_up:

transfers.go
59.48% <57.44%> (ø)
:arrow_up:

events.go
43.61% <63.15%> (ø)
:arrow_up:

... and 9 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 62513d1...2cff0d4. Read the comment docs.


normalize_comments = true de-normalizes some comments

According to https://rust-lang.github.io/rustfmt/?version=v1.4.36&search=#normalize_comments should convert /* yada */ to // yada, but the inverse happens.
# rustfmt +nightly --version
rustfmt 1.4.37-nightly (d2b04f0 2021-07-07)

normalize_comments = true
normalize_doc_attributes = true

results in a delta of
@@ -150,11 +151,11 @@ pub enum Stage {
        AvailabilityRecovery = 6,
        BitfieldDistribution = 7,
        ApprovalChecking = 8,
-       // Expand as needed, numbers should be ascending according to the stage
-       // through the inclusion pipeline, or according to the descriptions
-       // in [the path of a para chain block]
-       // (https://polkadot.network/the-path-of-a-parachain-block/)
-       // see [issue](https://github.com/paritytech/polkadot/issues/2389)
+       /* Expand as needed, numbers should be ascending according to the stage
+        * through the inclusion pipeline, or according to the descriptions
+        * in [the path of a para chain block]
+        * (https://polkadot.network/the-path-of-a-parachain-block/)
+        * see [issue](https://github.com/paritytech/polkadot/issues/2389) */
 }

 /// A wrapper type for a span.

Thanks for the report. This is technically a duplicate of a similar report added in a comment in #3350, but better to have a dedicated issue for it any way

I just hit this when commenting out a field in a struct definition, but I haven't even set normalize_comments = true.
rustfmt --version: 1.4.37-nightly (5ecc8ad 2021-09-19)


GORA-512 Add HBase configuration exception for erroneous mapping file and test

This PR resolves GORA-512 by adding the necessary exception for erroneous mapping files and a test case to capture it.

+1, Looks good. @alfonsonishikawa Can you please have a look?

@djkevincr , sure!
Looks good, test passes. I will merge in a while :)

+1

Pushed. Thank you, @nishadi !

Thank you for merging :)

this looks to me +1


0 base variants

Hi there,
Firstly, thanks for this cool tool. I have two data-sets (Illumina PE reads) corresponding to two related individuals (humans). I want to compare their SVs which I created using Lumpy (and GrCh38 as the reference). When I run truvari with one of them as ground/base_calls and the other as compare_calls, I get everything 0 in summary.txt.
The log file of the run is attached.
truvari_log.txt

This is an odd error because the ground(comparision) calls are being parsed (53944 call variants in total), but the base vcf individual1.sorted.vcf.gz seems to be the problem. Can you inspect the two to see if there's any important differences?


Add missing or incorrect shadow troubleshooting info

Copied from this question: https://forum.babylonjs.com/t/how-to-fix-shadow-shape/28580

Actually we should either:

put a link to the question so that if the image URL changes then someone can more easily find the original image and optionally update it to fix it.
or put this / another image into this repo

Thank you so much for that :-)
This is one of many reasons as to why you don't see your shadows. Whereas this is a great start, I don't want people to think this is the only thing they can try if their shadows don't work. This should probably expand a little more. Maybe instead of a very abstract title we can add a sentence saying it is possible to try if you are having difficulties with the shadows as part of the text before the newly added section?

Thank you so much for that :-)

My pleasure :)

This is one of many reasons as to why you don't see your shadows. Whereas this is a great start, I don't want people to think this is the only thing they can try if their shadows don't work.
This should probably expand a little more.

Yes sorry I do not know of any of the other approaches to fixing missing shadows.

Maybe instead of a very abstract title we can add a sentence saying it is possible to try if you are having difficulties with the shadows as part of the text before the newly added section?

Sorry I do not know how to improve it, could you do this please?  Or I will be happy to update the PR with some text you write here.

Closing this for now, but I totally understand the need for that. I'll create an issue and see how we tackle this.


Can't bundle huge (37k line) files.

Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment
Environment:
OS: Windows 10
Node: 6.10.2
Yarn: Not Found
npm: 3.10.10
Watchman: Not Found
Xcode: N/A
Android Studio: Version  <IP_ADDRESS> AI-171.4408382
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.50.4 => 0.50.4
Steps to Reproduce

react-native init project
cd project
install the kotlin runtime library npm install --save kotlin
modify index.js like

import { AppRegistry } from 'react-native';
import App from './App';
import Kotlin from 'kotlin'; // this is the added line

AppRegistry.registerComponent('project', () => App);

bundle the source (react-native bundle --verbose --platform android --dev true --entry-file index.js --bundle-output output.bundle)

Expected Behavior

I would expect the bundle file is created.
Actual Behavior
The execution stops with this error message:
TimeoutError: transforming C:\project\node_modules\kotlin\kotlin.js took longer than 601 seconds.

Same here on Mac.


New feature: enable accessing user custom virtual memories from a file.

Idea:
The new ic-polyfill function mounts some virtual memory in the file system. Whenever a user tries to read or write in this file, the read and write operations work directly on the virtual memory as if it was one of the files on the filesystem. Direct memory access is much faster because there is less inherent data copying, and no extra overhead related to the use of complex data structures such as btreemap. This creates a "fast file" at the cost of using one dedicated virtual memory storages. The user can mount several virtual memories, however, the number of virtual memories is limited.
The feature can have several purposes:

Fast file for reading and writing can be helpful for applications like sqlite or some application related to intensive reading and writing to some particular file.
A user can see their own virtual memory from the perspective of the file system or the wasi file system calls.
Comparison with the fast file can be a sort of a baseline for estimating performance of work with the usual files.

The feature is being implemented in pull request #15.

the implementation of virtual memory mounts was merged into the main branch with v0.6


Add file size info in dataset

Since the modal for the frontend of downloading matrices displays the file size per file, we need to populate the GET dataset API with file size information. We also need to update the database with a field for file size and calculate it for each dataset artifact.

Since the modal for the frontend of downloading matrices displays the file size per file, we need to populate the GET dataset API with file size information. We also need to update the database with a field for file size and calculate it for each dataset artifact.

@mckinsel - can we not simply use the common pattern of HEAD to retrieve Content-Length?
For example:

How to determine the file size of a remote HTTP object
Determine file size in JavaScript without downloading a file

Yeah I think that would be better. There's also an object.content_length attribute in boto3 if we have to use that for auth or something.

OK sounds good -- perhaps this ticket can be reworded to be a frontend ticket to fetch and display the files sizes in the modal then using @brianraymor's second suggestion link. The existing frontend UI ticket is size 8 anyways so this can be one of the sub-tickets of implementation.

Closing this ticket since the file size will be returned as part of the POST API to get a pre-signed URL for a dataset. Please see #476 for more information.


Unable to modify spriteFilename if loader rule has resourceQuery while using SpriteLoaderPlugin

Do you want to request a feature, report a bug or ask a question?
report a bug
What is the current behavior?

Loader gets filename from options and plugin uses it
If the current behavior is a bug, please provide the steps to reproduce, at least part of webpack config with loader configuration and piece of your code.
{
    test: /\.svg$/,
    resourceQuery: /^$/,
    use: [
        {
            loader: "url-loader",
            options: {
                generator: (content) =>
                    svgToMiniDataURI(content.toString()),
                esModule: false,
            },
        },
        {
            loader: "svgo-loader",
        },
    ],
},
{
    test: /\.svg$/,
    resourceQuery: /\?symbol$/,
    use: [
        {
            loader: "svg-sprite-loader",
            options: {
                extract: true,
                spriteFilename: 'sprite-[hash:6].svg',
                outputFolder: outputFolder,
                symbolId: (filePath) => {
                    const dirName = path
                        .dirname(filePath)
                        .split(path.sep)
                        .slice(-1);
                    return `${dirName}--${path.basename(
                        filePath,
                        ".svg",
                    )}`;
                },
            },
        },
        {
            loader: "svgo-loader",
        },
    ]
},

Please tell us about your environment:

Node.js version: 16.15.1
webpack version: 5.44.0
svg-sprite-loader version: ^6.0.6
OS type & version: Windows

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
As I debug problem is in this line
https://github.com/JetBrains/svg-sprite-loader/blob/051b82e48db26e1bb234ab9ba5f3ea9fdbc3b9db/lib/utils/get-matched-rule-5.js#L46
It works only for the first rule and thats why several lines later plugin can`t find the rule for itself and sets it as empty object
...And little bit later in this condition plugin use default sprite name
https://github.com/JetBrains/svg-sprite-loader/blob/4a3d105491aa88400734e1cdaba80da1657e8efa/lib/utils/mapped-list.js#L91

for me too


Sekey not working after upgrading to Big Sur

Hello,
Not sure if anyone else has noticed. After upgrading to Big Sur, sekey is still running and able to list and export keys, but the SSH client is unable to use it to sign the challenge, throwing this error:
debug1: Offering public key: ecdsa-sha2-nistp256 ECDSA SHA256:REDACTED agent
debug1: Server accepts key: ecdsa-sha2-nistp256 ECDSA SHA256:REDACTED agent
sign_and_send_pubkey: signing failed: communication with agent failed
...

 Nothing that required touch id was working. I had to shutdown and hold the power button for 10 seconds to fix the issue.

Well, it turns out it was a problem with the Macbook's touch bar itself. Nothing that required touch id was working. I had to shutdown and hold the power button for 10 seconds to fix the issue.

Big sur has some weird glitches, like sound disappearing for a while or touchid not working on lock screen (but working otherwise) etc. Annoying, but hopefully going away in future updates.

Big sur has some weird glitches, like sound disappearing for a while or touchid not working on lock screen (but working otherwise) etc. Annoying, but hopefully going away in future updates.


feat: added sockets to frontend and backend to listen for each other.…

… Backend now queries the database observation table and passes the data to the logsheet component to populate the data. Team talked about using requests instead of sockets for this portion but after trying to switch too many problems arose with rendering the data on the component whereas the socket stays open and will constantly update the table. At this point using requests seems like something that would be nice to have but currently dual sockets works here.

2. We can probably use context to pass an instance of io() down from the top of the app. We didn't discuss this in the meeting but we're using this pattern ~in the file writer~ for the status updates. After that content is available to us, we can look at using it here too.

This is okay for now, I'll do a refactor when my part is done.


Variables for Repeating Panels

Hey,
i got the Issue in Version 1.0 when i use the Variables like "&var-Hostname=Host1&var-Hostname=Host2" for my Dashboard wich is configure to use repeating Panels by Hostname, the generated report shows my two variables, but only shows Images from the first Host.

I'm not sure that the reporter plays nicely with repeating panels; I haven't used that feature myself. See this comment for a more detailed explanation on why I think this is unlikely to work.
Furthermore, multiple variable support does not imply you can provide conflicting values for the same variable. Rather, if you have a dashboard that takes two different variables as input, e.g. var-hostname=host1&var-port=eth0, both of these would be passed through to Grafana when fetching the each png panel.
I suggest you look at the Grafana dashboard data model and HTTP API and play around with curl or wget and see if you can get all access the panels you anticipate. I don't think it is possible, but If I am missing something, please re-open this issue.


Kernel dies - sc.pp.neighbors

Hi there.
Everytime I run the code sc.pp.neighbors the kernel dies. Unfortunately, there is no error message or error code. It just dies while computing neighbors.
Other scanpy codes like sc.pp.filter_cells and sc.pp.filter_genes work without a problem.
I'm using:

windows 10 64-bit 24 gb ram
python 3.8.5 in jupyter notebook
numpy 1.19.4
scanpy 1.6.0

Is there someone who would be able to solve this issue?
Thank you very much!

Does this cause the same issue?
import numpy as np
import umap

umap.UMAP().fit_transform(np.random.randn(10_000, 20))

And when you say "dies", is there a segfault message, or are you seeing a jupyter kernel failure message?
In general, this sounds like a numba issue. I'd recommend taking searching the umap-learn or numba repositories for similar issues.

Does this cause the same issue?
import numpy as np
import umap

umap.UMAP().fit_transform(np.random.randn(10_000, 20))

And when you say "dies", is there a segfault message, or are you seeing a jupyter kernel failure message?
In general, this sounds like a numba issue. I'd recommend taking searching the umap-learn or numba repositories for similar issues.

It causes exactly the same issue when I run:
import numpy as np
import umap

There is no segfault message. The jupyter kernel failure message is:
Kernel restarting. The kernel appears to have died. It will restart automatically.

It causes exactly the same issue when I run:
import numpy as np
import umap

There is no segfault message. The jupyter kernel failure message is:
Kernel restarting. The kernel appears to have died. It will restart automatically.

First, make sure your versions of numba and umap are up to date.
Then running this without jupyter, just in python. I think jupyter is likely hiding whatever error the python process is crashing with. E.g.:
$ python3 -c "import numpy; import umap"

If this fails, I think you should be opening an issue upstream with numba or umap (if you can figure out which one is at fault).
I've had this sort of thing happen a few times. Some of the causes were:

Multiple versions of C libraries being linked to
Threading backends not working

I've been able to work around both of these in the past by using conda environments.

First, make sure your versions of numba and umap are up to date.
Then running this without jupyter, just in python. I think jupyter is likely hiding whatever error the python process is crashing with. E.g.:
$ python3 -c "import numpy; import umap"

If this fails, I think you should be opening an issue upstream with numba or umap (if you can figure out which one is at fault).
I've had this sort of thing happen a few times. Some of the causes were:

Multiple versions of C libraries being linked to
Threading backends not working

I've been able to work around both of these in the past by using conda environments.

sometimes the jupyter console logs give you an idea of what is happening as well. I've had this happen when you run out of memory.

sometimes the jupyter console logs give you an idea of what is happening as well. I've had this happen when you run out of memory.

@wicktir Was there a solution for this problem that worked? I am running into the same issue.

@jnmark Unfortunately, I haven't found a solution yet. I decided to run it on a different machine (macOS).

I didn't keep perfect track of the steps that I took to solve this or the exact versions of everything that I used but I'll try outlining what I did.
First I tried to upgrade numba and umap as suggested by the other individuals in the thread:
pip install --upgrade numba
pip install --upgrade umap-learn

Then I essentially reinstalled scanpy using the steps in their installation docs.
conda install seaborn scikit-learn statsmodels numba pytables
conda install -c conda-forge python-igraph leidenalg
pip install scanpy

I think I then ended up with a version of numpy that was incompatible with numba so I ran
pip install numpy==1.20

After each step, you should be able to run the code from above to check if your installations worked, which I used to pinpoint what still needed work in my environment:
python3 -c "import numpy as np; import umap; umap.UMAP().fit_transform(np.random.randn(10_000, 20))"

This seemed to fix my problems; I hope it's able to help others!

I would recommend creating fresh conda environments frequently, especially if you mix conda and pip installation. Upgrading them in finicky, and often results in a broken state.

I am running into the same issue and unfortunately running the steps as described here https://github.com/theislab/scanpy/issues/1567#issuecomment-968181500 does not solve my problem. My kernel systematically dies when I run sc.pp.neighbors (even with only 1,000 cells). What I am also confused about is that this used to work - I am guessing I updated a package somewhere that broke everything but I cannot identify what.
This is my config:

MacBook Pro (13-inch, M1, 2020) - macOS Big Sur 11.5.2
python 3.8.8
numpy 1.20.0
numba 0.51.2
umap-learn 0.5.2

I have tried running the following code in Jupyter and then in a script to see if I could get more info on the bug:
unhealthy_cells = sc.read_h5ad("path/to/file")

unhealthy_cells.layers["counts"] = unhealthy_cells.X.copy()

sc.pp.normalize_total(unhealthy_cells,target_sum=10000)

sc.pp.log1p(unhealthy_cells)

sc.pp.scale(unhealthy_cells)

sc.tl.pca(unhealthy_cells)

sc.pp.neighbors(unhealthy_cells)

When I run it as a python script, I get the following error when getting to sc.pp.neighbors (everything else works):
zsh: illegal hardware instruction
Is there anything I could do?
Thank you for your help!

I have the same issue even after updating numba, umap and scanpy :(

I didn't keep perfect track of the steps that I took to solve this or the exact versions of everything that I used but I'll try outlining what I did.
First I tried to upgrade numba and umap as suggested by the other individuals in the thread:
pip install --upgrade numba
pip install --upgrade umap-learn

Then I essentially reinstalled scanpy using the steps in their installation docs.
conda install seaborn scikit-learn statsmodels numba pytables
conda install -c conda-forge python-igraph leidenalg
pip install scanpy

I think I then ended up with a version of numpy that was incompatible with numba so I ran
pip install numpy==1.20

After each step, you should be able to run the code from above to check if your installations worked, which I used to pinpoint what still needed work in my environment:
python3 -c "import numpy as np; import umap; umap.UMAP().fit_transform(np.random.randn(10_000, 20))"

This seemed to fix my problems; I hope it's able to help others!

I followed your instruction but it still threw errors:
:219: RuntimeWarning: scipy._lib.messagestream.MessageStream size changed, may indicate binary incompatibility. Expected 56 from C header, got 64 from PyObject
Segmentation fault

I would recommend creating fresh conda environments frequently, especially if you mix conda and pip installation. Upgrading them in finicky, and often results in a broken state.

Creating a new environment and reinstalling everything worked for me. Thanks!

pip install -U pynndescent
This fix my problems; I hope it's able to help others!

conda install -c conda-forge pynndescent
This also fixed my problem. Thanks @FlyPythons for the hint.

conda install -c conda-forge pynndescent
This also fixed my problem. Thanks @FlyPythons for the hint.

Thanks!This also  work for me.


Scoring sync improvements

Store all scores in a new table for the sources that we sync with separately: User, AniDB, MAL, Trakt.
Add setting which would define what happens in case of conflict:
(Do nothing, Always use [user, anidb, mal, trakt] score.
Default option is - do nothing, user has to resolve manually, if server detects that it is about to overwrite something with default setting it will abort the operation.

From our conversation:
Add a new utility to show conflicts so user can select the "correct" score which will then update the other scores for the community sites.


create lmdb error

I use my own dataset which has three big images in different size. Then I crop these images in 182 smaller images but they have 3 types of size. Then I use extract_subimages.py and achieve 14392 images with size of 480*480. When I try to use create_lmdb.py , I found an error said:
runfile('C:/Users/ThinkPad/Desktop/SR/mmsr-master/codes/data_scripts/create_lmdb.py', wdir='C:/Users/ThinkPad/Desktop/SR/mmsr-master/codes/data_scripts')
Reloaded modules: data, data.util, utils, utils.util
Reading image path list ...
data size per image is:  691200
Traceback (most recent call last):
File "", line 1, in
runfile('C:/Users/ThinkPad/Desktop/SR/mmsr-master/codes/data_scripts/create_lmdb.py', wdir='C:/Users/ThinkPad/Desktop/SR/mmsr-master/codes/data_scripts')
File "D:\anaconda3\lib\site-packages\spyder_kernels\customize\spydercustomize.py", line 668, in runfile
execfile(filename, namespace)
File "D:\anaconda3\lib\site-packages\spyder_kernels\customize\spydercustomize.py", line 108, in execfile
exec(compile(f.read(), filename, 'exec'), namespace)
File "C:/Users/ThinkPad/Desktop/SR/mmsr-master/codes/data_scripts/create_lmdb.py", line 412, in
main()
File "C:/Users/ThinkPad/Desktop/SR/mmsr-master/codes/data_scripts/create_lmdb.py", line 40, in main
general_image_folder(opt)
File "C:/Users/ThinkPad/Desktop/SR/mmsr-master/codes/data_scripts/create_lmdb.py", line 106, in general_image_folder
env = lmdb.open(lmdb_save_path, map_size=data_size * 10)
Error: C:/Users/ThinkPad/Desktop/SR/changping-GF2/train_sub_HR.lmdb: ���̿ռ䲻�㡣
I donnot know how to debug this error, can anybody help me?

Check you have enough disk space?

Check you have enough disk space?

Yeah, this may be the point, I change my computer to a sever and it runs well.
Thank u!


Create 2024-06-14-Tales-From-TCamp.md

Another blog post ready for review/approval @compilerla/engineering :)

@AnthonyRollins I think the photo issue is resolved, so this should hopefully be good to approve. Angela approved as well

@laneymangan You can also go ahead and mark this pull request as "ready for review." That will take the pull request out of "Draft"


Add sem_try_acquire()

sem_try_acquire() attempts to acquire a permit without blocking, returns true on success, or false if no permits are available. I have a PR coming up.

Added in #856


Enhance waitDdpReady for performance

This ends up to cause the same enhancement as https://github.com/Astrocoders/rn-meteor-containerize provides with much less code.
As @Tim-M pointed in #93, workers could also provide more performance but for now I'm just going to stick a bit researching about them.
For now the current improvement guarantees that the Mixin will let any on going animations or Tracker invalidations finish first before booting up.

Thanks !

@grsabreu looks like there's an issue in Data.js:35: runAfterInteractions(()=>{ should be InteractionManager.runAfterInteractions(()=>{

Right thanks for pointing this out !
I'm fixing it now.

No worries! :)

true! thanks @NiallBrickell
I must have did a undo without noticing before pushing.

When will this update be pushed to npm? Seems like the package version needs to be updated from 1.0.1 which was last updated a month ago.

It is now.


Crystal miner constantly pauses itself while trying to output several items on a belt at once.

Mod source
Factorio Mod Portal
Operating system

=Windows 10

What kind of issue is this?

[ ] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[ ] Graphical
[ ] Crash
[ ] Progression
[ ] Balance
[ ] Pypostprocessing failure
[X] Other

What is the problem?
Instead of outputting one ore at a time this miner tries to output several ores at a time (per one mining cycle) and ends up constantly pausing itself (when miner productivity bar reaches 100% the pause is even longer). This leads to all planner tools underreporting the number of miners you need (cos they expect them to work without these self-inflicted hiccups).
https://github.com/user-attachments/assets/cbed4844-9232-4124-a92b-fbc8b28694b2
Steps to reproduce
No response
Additional context
No response
Log file
No response

I don't see any pauses except when the productivity bar fills at the exact same time as the normal production bar. Perhaps would the solution be to increase mining productivity from 10% to 11%?

I don't see any pauses except when the productivity bar fills at the exact same time as the normal production bar. Perhaps would the solution be to increase mining productivity from 10% to 11%?

Pay close attention to the bottleneck indicator, you can clearly see it switching to yellow even when there's no bonus prod output

It's even consistent with issue's logic i.e. a miner is incapable of placing several ores on a belt at the same time so it must wait for one to slide out of the way so the second could be placed next and therefore it pauses while having yet unplaced ore in its buffer or something.

A potential solution would be to make it output one ore per mining cycle, not multiple


Don't read data from heap for zero HNID

For string and binary properties if we receive HNID=0, we should not try to read data from heap.
HNID=0 means nil data or empty string.

Hey, thanks again for your contribution!
I have accidentally marked this as ready for review but I saw you marked it as a draft.
Is this pull request ready to be merged?

This is a draft. Don't merge, please. This fix is not enough.
We should check all code working with ReferenceHNID and handle the case ReferenceHNID==0.
For example: GetData func in PropertyContextItem: we should not find local descriptors if hnid==0 and return nil, nil.
But I don't have enough time to check and test it.

If you don't mind me asking, what are you using go-pst for?
I'm working on forensic software (SaaS) which presents and analyzes digital evidence to be presented in court. I'm starting with emails so go-pst was created.

We use this lib for our tests.

I have merged pull request #13 which had this pull request code in it already.
Is it alright if we close this issue?
@newgenid I'm curious, what are you testing with this library?

This fix was merged in #13.

@mooijtech In our tests we read data from pst files.

@newgenid Alright, good luck!


Cannot update tags on existing resource of type Microsoft.Network/publicIPAddresses

Describe the bug

I have an existing resource of type Microsoft.Network/publicIPAddresses. I'm trying to update its tags. The operation fails with an unrelated error.

ERROR: Resource /subscriptions/xxx/resourceGroups/yyy/providers/Microsoft.Network/publicIPAddresses/zzz has an existing availability zone constraint 1, 2, 3 and the request has availability zone constraint NoZone, which do not match. Zones cannot be added/updated/removed once the resource is created. The resource cannot be updated from regional to zonal or vice-versa.

To Reproduce

Resource looks like:
{
  "etag": "W/\"dc92c146-fcef-4457-88cd-7a8feb067044\"",
  "id": "/subscriptions/xxx/resourceGroups/yyy/providers/Microsoft.Network/publicIPAddresses/zzz",
  "identity": null,
  "kind": null,
  "location": "westus2",
  "managedBy": null,
  "name": "zzz",
  "plan": null,
  "properties": {
    "dnsSettings": {
      "domainNameLabel": "blah",
      "fqdn": "blah.westus2.cloudapp.azure.com"
    },
    "idleTimeoutInMinutes": 4,
    "ipAddress": "<IP_ADDRESS>",
    "ipConfiguration": {
      "id": "/subscriptions/xxx/resourceGroups/yyy/providers/Microsoft.Network/loadBalancers/kubernetes/frontendIPConfigurations/ac73e065675454458a4b08efd38a7880",
      "resourceGroup": "yyy"
    },
    "ipTags": [],
    "provisioningState": "Succeeded",
    "publicIPAddressVersion": "IPv4",
    "publicIPAllocationMethod": "Static",
    "resourceGuid": "qweasd"
  },
  "resourceGroup": "yyy",
  "sku": {
    "capacity": null,
    "family": null,
    "model": null,
    "name": "Standard",
    "size": null,
    "tier": "Regional"
  },
  "tags": {
    "blah": "blah",
    "qwe": "asd",
    "asd": "zxc"
  },
  "type": "Microsoft.Network/publicIPAddresses",
  "zones": [
    "1",
    "2",
    "3"
  ]
}

Command to update tags:
az resource tag --ids /subscriptions/xxx/resourceGroups/yyy/providers/Microsoft.Network/publicIPAddresses/zzz --tags blah=blah qwe=asd asd=zxc new=tag
Expected behavior

Tags must be updated without issues, since the change doesn't affect any other properties of the resource.
Environment summary

Azure Cloud Shell
{
  "azure-cli": "2.23.0",
  "azure-cli-core": "2.23.0",
  "azure-cli-telemetry": "1.0.6",
  "extensions": {
    "ai-examples": "0.2.5",
    "aks-preview": "0.5.10",
    "front-door": "1.0.14",
    "resource-graph": "1.1.0",
    "ssh": "0.1.5"
  }
}

ARM

Can be worked around with az tag command, which does the right thing.
az resource tag is broken though.


Correct updating of config file when (un)registering clusters

Addresses: https://github.com/couchbaselabs/couchbase-shell/issues/415

Ignore my review, I hadn't seen @chvck's comments (and I should have asked the same questions, as I was wondering the same)


List of refactoring tasks

Frontend

[ ] Try using vuex-class-modules (alternatively vuex-class-component). Start from one module, if everything goes well - spread to other modules.

[ ] components/analytics - create one universal component for uploading JSON

[ ] Divided interfaces and APIs into modules and use shorter names for classes and functions inside module:

interfaces/IAgentEdit -> interfaces.agent.IEdit
api/getAgents -> api/agent/get

[ ] Migrate to vue3

Backend

[ ] Try to remove top-level "app" folder in backend
The structure should be:

backend
    alembic
    app
        api
        core
        ...
    lib
    scripts
    ...

[ ]  Move all independent modules (modules that don't have dependencies on any specific project modules or resources) to module "lib"

[ ] Move all business logic from app.workers to some dedicated module (core.postprocessing?). Modules inside app.workers should only contain logic related to tasks management.

[ ] Move logic not related to ORM from app.models to app.crud

Wrong repo I think.

Oh, sorry  :)


US users are not redirected to US URL if there is no GL EN translation

Level Playing Field:

node is published
US EN translation is published
GL EN translation does not exist

As an anonymous user coming from the US, if I go to https://thor.dosomething.org/campaigns/level-playing-field, I'm not being redirected to the US experience. The desired behavior is that I would be getting redirected.
Some tangible side effects to this are that

Problem fact is missing on the pitch page
I'm seeing the GL EN footer

Since we have a lot of marketing out there pointing people directly to the base URL (i.e. www.dosomething.org/campaigns/level-playing-field) we need to resolve this before we launch.

Can't reproduce on my dev?


[<EMAIL_ADDRESS>+ ] index out of bounds: the len is 1 but the index is 1

Describe the bug
thread '<unnamed>' panicked at 'index out of bounds: the len is 1 but the index is 1', /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/swc_common-0.29.6/src/syntax_pos/hygiene.rs

env: typescript v4.8.4
in @swc/core v1.3.6 ok
Input code
//
class HuluCssModules extends Visitor {
  visitImportDeclaration(expression) {
     return expression;
  }
}

exports.default = HuluCssModules;

### Config

```json
{
            test: /\.(js|mjs|jsx|ts|tsx)$/,
            exclude: /node_modules/,
            use: {
                loader: require.resolve('swc-loader'),
                options: {
                    parseMap: true,
                    sync: true,
                    jsc: {
                        parser: {
                            syntax: 'typescript',
                            tsx: true
                        },
                        transform: {
                            react: {
                                runtime: 'automatic',
                                throwIfNamespace: true,
                                development: devMode,
                                useBuiltins: false,
                                refresh: true
                            }
                        }
                    },
                    plugin: (m) => new HuluCssModules().visitProgram(m)
                }
            }
        }

### Playground link

_No response_

### Expected behavior

compile no error

### Actual behavior

_No response_

### Version

v1.3.10

### Additional context

_No response_

I'm also seeing this in our formatjs swc plugin

@longlho Please provide a repro case

It's a little hard to isolate it because our plugin does a bunch of transformations, but specifically this test fail:
Test: https://github.com/formatjs/formatjs/blob/main/packages/swc-plugin/tests/issue-3362.test.ts
Fixture: https://github.com/formatjs/formatjs/blob/main/packages/swc-plugin/tests/fixtures/issue-3362.tsx
The dep upgrade bot put up the PR: https://github.com/formatjs/formatjs/pull/3846 which failed our build
Build log: https://app.buildbuddy.io/invocation/5bac68ac-7edb-48a2-8018-b8a6bb32faf1
In the fixture our plugin basically tries to find all intl.formatMessage and transform the params (removing/adding some attributes). In the test specifically it's mainly a no-op since it just makes sure our plugin doesn't bomb swc. The result snapshot is here: https://github.com/formatjs/formatjs/blob/main/packages/swc-plugin/tests/snapshots/issue-3362.test.ts.snap (kinda looks exactly the same as the fixture except for the downtranspilation piece).
When I run with RUST_BACKTRACE=full the stack trace doesn't look very useful:
thread '<unnamed>' panicked at 'index out of bounds: the len is 1 but the index is 1', /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/swc_common-0.29.10/src/syntax_pos/hygiene.rs:580:34
stack backtrace:
   0:        0x11fd42cd7 - _napi_register_module_v1
   1:        0x11fa1621a - <unknown>
   2:        0x11fd1639c - _napi_register_module_v1
   3:        0x11fd4370b - _napi_register_module_v1
   4:        0x11fd43f52 - _napi_register_module_v1
   5:        0x11fd43a44 - _napi_register_module_v1
   6:        0x11fd439a8 - _napi_register_module_v1
   7:        0x11fd43972 - _napi_register_module_v1
   8:        0x12104fa03 - _wasmer_vm_raise_trap
   9:        0x12104fa76 - _wasmer_vm_raise_trap
  10:        0x12071e7a6 - _napi_register_module_v1
  11:        0x1206b293b - _napi_register_module_v1
  12:        0x12071994c - _napi_register_module_v1
  13:        0x11fecb93b - _napi_register_module_v1
  14:        0x11fe788de - _napi_register_module_v1
  15:        0x11f8cc732 - <unknown>
  16:        0x10f7da46a - _worker
  17:     0x7ff80f16d4e1 - __pthread_start
 FAIL  packages/swc-plugin/tests/issue-3362.test.ts
  ✕ github issue #3362 (30 ms)

  ● github issue #3362

    failed to handle: index out of bounds: the len is 1 but the index is 1

      Stack backtrace:
         0: _napi_register_module_v1
         1: _wasmer_vm_raise_trap
         2: <unknown>
         3: _worker
         4: __pthread_start

Hope that helps.
The code snippet that @mizi-lin posted seems a lot simpler and also crapped out?

I got this error also

Does it work on v1.3.5?

@IWANABETHATGUY I think https://github.com/swc-project/swc/pull/6019 is the cause, thoughts?
There's no PR touches it other than #6019

@aelbore Can you try 1.3.4 and 1.3.5?

@kdy1  works on <=1.3.6
heres the minimal reproduction
import { transformSync, plugins } from '@swc/core'
import { Visitor } from<EMAIL_ADDRESS>
const content = `
  const store = () => {

  }

  export default store;
`

class MyPlugin extends Visitor {
  visitModule(e) {
    return e;
  }
}

const myPlugin = () => {
  return (p) => new MyPlugin().visitProgram(p)
}

const { code } = transformSync(content, {
  filename: 'abc.ts',
  jsc: {
    parser: {
      syntax: 'typescript',
      tsx: true
    }
  },
  plugin: plugins([
    myPlugin()
  ])
})

console.log(code)

if you change the content to this
const content = `
  export default () => {

  }

it works

So https://github.com/swc-project/swc/pull/6118 is the cause.
But seems like @longlho has a different issue from this.
@longlho Can you try v1.3.6?

I expected this will not cause issues, i will try to revert the code and see if we could fix this issue.

Oh, nevermind. Your plugin was based on js, so this is an identical isssue.
@IWANABETHATGUY That was not the cause, sorry

Oh, nevermind. Your plugin was based on js, so it was an identical issue. @IWANABETHATGUY That was not the cause, sorry

That's fine, hhhh

another thing, empty plugin cause error also
plugin: plugins([])

For formatjs, please use https://github.com/kwonoj/swc-plugin-formatjs instead

Just want to ask if theres any plan to fix this? though version <=1.3.6 works Many thanks

For formatjs, please use kwonoj/swc-plugin-formatjs instead

that's not maintained but us btw

@aelbore Not sure. Fix would be trivial but I don't want to use my time for this

Just to add also
this cause the error

const randomId = () => { }

export { randomId }

Solution

export const randomId = () => { }

I'm not going to fix this by myself as fixing this encourages wrong usage

I didn't close it because I would accept PR

So what is actually the issue here? I'm seeing the "index out of bounds" in my build and came here to find a fix or at least a workaround. I read "this encourages wrong usage", so I would like to know what I'm doing wrong. I also read "Fix would be trivial" so I assume a root cause is found, but I don't see it, is is the default exports? How would a PR to fix this look like?

For anyone still encountering the issue: it may not be the issue from @swc/core itself; it may be due to the plugins.
I tried the 1.3.58 version of @swc/core, and there is no export {xxx}; in my project, but I still got the "index out of bounds" message. But when I pasted my code to the SWC playground, it worked well. There's also no issue when I use 1.3.7 version in the playground.
Then I removed all plugins in my project and found it worked... After several tries, I found that both options.plugin and options.jsc.experimental.plugins can cause this issue.
I'm not familiar with Rust so I didn't find the root cause, but removing all SWC plugins is an acceptable solution for me.

I get this with a blank plugin in JS just extending Visitor (class MyPlugin extends Visitor { }). How does this "encourage wrong usage"? The only way to not cause this error (on my machine) is to not use any JS plugins.

So, I comment as well to say that I have a similar error with this parsed code
myGlob = function () {
    let a = 42;
};
myGlob();

I can't remove the plugins because I use them to transform code for a specific parser. I don't know rust as well in order to make a PR.
Is the wrong usage mentioned before the fact that we use JS plugins instead of rs plugins ?

I'm not going to fix this by myself as fixing this encourages wrong usage

I also encountered this now with completely unrelated code to be transformed (see https://github.com/swc-project/swc/issues/7570) and the use of a plugin that merely returns the module/program. In my case, it's not possible to adjust the code, as that's provided by third parties.

I'm not going to fix this by myself as fixing this encourages wrong usage

@kdy1, would you mind elaborating why the wrong usage is in this case? The use of the plugin hook?
As the removal of the plugin fixes the issue in all instances, it means that the issue lies with calling the transform function with an swc-generated AST for those code snippets.
In other words,
const module = parseSync('fn((obj) => obj?.method());');
transformSync(module);

fails, but
transformSync('fn((obj) => obj?.method());');

succeeds.
Shouldn't this be fixed?

@rene-leanix transform(Module) will also be removed when we can make a breaking change.

I have this issue when just using transform(string), when using a blank JS plugin.

JS plugins will be removed in v2, and it's deprecated.

Thanks for the quick response and clarification, @kdy1! Is there any place I can read up about the major (especially breaking) changes planned for v2?
If JS plugins are removed, could there be a way to register a (published or local) Rust plugin from within the JS code for a particular transformation?


Changing tab index programmatically to another tab index sub-screen.

I am using this library with react-navigation. sometime i need to switch between screens programmatically.I have tab indexes and every tab in i can navigate to another screen within that tab, now suppose i am on a tab at index 1 and from there i want to go to a screen which will navigate from tab index 4 so i will reset my navigation action from screen at tab index 1.For this i am resetting my navigation action so after resetting this if i change the current index in state to show the selected tab so instead of staying to the screen where i navigated it, it will come to the initialRoute screen of that tab.

This is a coflict  react-navigation to this lib,
You can try with this lib react-native-scrollable-tab-view instead of.
I hope can help u improve them @@

Hey, I just released a new alpha 2.0.0-alpha.0 of the library. It's rewritten using react-native-gesture-handler and react-native-reanimated addresses a many platform specific bugs and performance problems. The documentation is updated as well.
Please try the new version and see if it addresses your issue. If not, please open a new issue following the issue template.


vue-lazyload doesn't work properly in Nuxt

Here's my example - http://many-winter.surge.sh/
If you go to that link, then go to Page Two, you'll see that all 4 image already loaded on the page. But if you refresh that Page Two, then Lazyload will work properly, and loading images one by one.
I want Nuxt not to preload all that images and not execute lazyload untill I go to Page Two.
How to fix it? Why is that happening?
<template>

</template>

Just now tried to use vue-lazyload as plugin. Nothing changed :cry:
It's working, but with this issue. With initial page load all image on OTHER pages are loaded too.

I think you have Misunderstood about lazyload ...
if you listen scroll event , that mean when pic on screen ( or close to ) then load pic ...
so , you need block space let screen keep away picture , and use different photo test .
I checked your source , first , you only loaded 1 pic , so , other pic will be fast show on screen .
and , you don't define img height ( I seen it height:auto ) so , if you don't have height ( or some Text )
that  tag will all in first screen and load it .
I tried it working , see this video gif

@ausir0726 sorry, but it seems that you doesn't understood what I am talking about.
lazyload is working fine when I reload page.

 You will see that all images are on the page already (they suposse to load one by one when scroll).

But if you then refresh the Page Two, then everything willl work fine. Images will be load one by one.

If you want to repeat the process, then you have to start from / again. If you continue visout it you will get the WRONG impression that there is no problem (I guess it was your case). It is because if code bundling. Other words - you must start site navigation from any page beside Page Two (where lazyload are) - then you will see the bug.

By the way. In nuxt/express EVERYTHING WORKS FINE. With the same code!
So the problem is with npm run generate.
To be truth I am really tired of all this generate issue and just at one step to leave it and not to use this function.

@ausir0726 I don't see nothing in your video related to my issue.

About placeholder images and width - I know that, but it's not related.
Repeat - in nuxt/express everything working like it should.

@kodekrendel  umm....
I think my English is not good for understand clear ...
anyway , I just want say if you use same pic and without height maybe is difficult see lazyload effect .
http://incompetent-smoke.surge.sh/
so , I put my example on surge.sh .
I watch the network console , It only when that pic close to screen then load on ineternet.
I refresh on my about page , then go to index , also have lazy load ...

@ausir0726 no, it's my English bad to describe this issue :smile:
I appreciate you help very much!
I tried different images, problem remains, just like I feel.
I will record video.

@ausir0726
https://www.youtube.com/watch?v=BMOt_7vjJRY

@ausir0726 well, you was right (again). I just need to add height. Thank you :+1:

never mind 😺
keep going , let nuxt.js amazing your site .

@ausir0726 also, adding a fixed height actually don't lazyload images. I don't need actual lazyload, but if you need some kind of infinite scroll, then this fix is not working.

yes ,
but maybe you can give a min-height .
As much as possible don't let image ( close to ) on the screen ...

Too bad, but min-height is not helping. I guess, I have to not use vue-lazyload, because it doesn't allow to use responsive image (NONSENSE!)


Doesn't work in 4.13 - Compile actions are response files

In 4.13 the compile files are response files rather than ordinary arguments. Just a heads up to changes in the future.

4.13 has released. https://github.com/epicgames/unrealengine/tree/4.13

Hi, thanks for the report! I'll sync the latest Unreal and see what can be done. :)

Ok I've pushed a change to allow it to work with 4.13's default behaviour here https://github.com/liamkf/Unreal_FASTBuild/commit/8285d1c0aee4df24b7a5ad1d694c3b5be75f75f5#diff-4582a3d8c09dcb4a7c9b2fde4f9a41bc which allows it to build fine.
As mentioned in the check-in comment it may be preferable to modify VCToolChain.cs instead to not use reponse files, particularly given Epic only made the change to support XGE! :)
Thanks again for the report!


Does not find visa electron

Hi,
He does not recognize the credit card starting with "4508 03XX XXXX XXXX". Card visa electron.

@obzc Have you checked the code for why that one is missed?

Fixed in 2.5.0 Visa electron now supported.


Improve worker logs

This is a first pass at improving worker logs.
Example without error:

Example with error:

Here's a first draft, it needs many improvements but a few things are here:

prepend each log entry with the task ID (useful when tasks running in parallel)
log directory contents as a single json line (takes less space)
log tuple key when starting "prepare materials"

e2e :heavy_check_mark:


Switch to dummyimage.com for local placeholder images

This morning https://placekitten.com reports a DreamHost "site not found" error. This commit switches our local placeholder image service to https://dummyimage.com, which generates boxes of text with the image size overlaid.
This service has fewer kittens but does have the benefit of generating the same image each time the same URL is requested, unlike placekitten which generates a random kitten. This makes dummyimage nicer for visual regression testing.
Screenshots

Notes and todos
I used Green 60 and Mid Dark Green from the design system palette here; please suggest a better combination if one is preferred!
Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code follows the standards laid out in the CFPB development guidelines

the saddest GH thread there ever was


Enable https

Get letsencrypt working on the EC2 instance, update the nginx config to use it.
Imported from Georgia Tech github:
{"created_at":"2019-03-22T15:05:09Z","updated_at":"2019-03-22T21:07:03Z","closed_at":"2019-03-22T21:06:44Z","html_url":"https://github.gatech.edu/ekobrin3/2019-Spring-CSE6242-flowgridviz/issues/18","id":74801}

https site: http://pcapviz.erluko.org/
Imported from Georgia Tech github:
{"created_at":"2019-03-22T21:07:03Z","updated_at":"2019-03-22T21:07:03Z","html_url":"https://github.gatech.edu/ekobrin3/2019-Spring-CSE6242-flowgridviz/issues/18#issuecomment-40229","id":40229}


Problems with accessing external services through edgemesh at the edge

What happened:
Prerequisites
make a ubuntu-test image from ubuntu:21.04, and install with telnet, net-tools, dnsutils, mosquitto, mosquitto-clients, inetutils-ping etc.
run it to a container from yaml:
apiVersion: v1
kind: Pod
metadata:
  name: edge-ubuntu-test
spec:
  nodeSelector:
    node-role.kubernetes.io/edge: ""
  containers:
  - name: edge-ubuntu-test
    image: ubuntu-test:21.04
    # Just spin & wait forever
    command: [ "/bin/bash", "-c", "--" ]
    args: [ "while true; do sleep 30; done;" ]

Success case
在边缘端pod层面创建一个mosquitto容器，供边缘端edge-ubuntu-test访问。
Create a mosquitto container at the edge pod for access by edge-ubuntu-test.
service -> endpoints

configmap-mosquitto.yaml

apiVersion: v1
kind: ConfigMap
metadata:
  name: mosquitto-config
  labels:
    app: chirpstack-mosquitto
data:
  mosquitto.conf: |
    persistence true
    persistence_location /mosquitto/data/
    # per_listener_settings false
    log_dest stdout
    # listener 1886
    listener 31883 <IP_ADDRESS>
    protocol mqtt

    listener 32901 <IP_ADDRESS>
    protocol websockets
    # Defaults to false, unless there are no listeners defined in the configuration
    # file, in which case it is set to true, but connections are only allowed from
    # the local machine.
    allow_anonymous true
    #    password_file /.config/mosquitto/auth/password_file.txt
    #    cafile: /mosquitto/config/certs/ca.crt
    #    certfile: /mosquitto/config/certs/server.crt
    #    keyfile: /mosquitto/config/certs/server.key
    require_certificate false
    use_identity_as_username false

deployment-chirpstack-mosquitto.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: chirpstack-mosquitto
spec:
  replicas: 1
  selector:
    matchLabels:
      app: chirpstack-mosquitto
  template:
    metadata:
      labels:
        app: chirpstack-mosquitto
    spec:
      nodeSelector:
        node-role.kubernetes.io/edge: ""
      containers:
      - name: chirpstack-mosquitto
        image: eclipse-mosquitto:2.0.10
        ports:
        - containerPort: 31883
          name: mqtt
          hostPort: 31883
        volumeMounts:
        - name: mosquitto-data
          mountPath: /mosquitto/data
        - name: mosquitto-log
          mountPath: /mosquitto/log
        - name: config-file
          mountPath: /mosquitto/config/mosquitto.conf
          subPath: mosquitto.conf
      securityContext:
        runAsNonRoot: true
        fsGroup: 1
        runAsGroup: 1000
        runAsUser: 1000
        supplementalGroups:
        - 1
      volumes:
      - name: config-file
        configMap:
          name: mosquitto-config
      - name: password-file
        configMap:
          name: mosquitto-password
      - name: mosquitto-data
        emptyDir: {}
      - name: mosquitto-log
        emptyDir: {}

svc-mosquitto.yaml

apiVersion: v1
kind: Service
metadata:
  name: chirpstack-mosquitto
  labels:
    app: chirpstack-mosquitto
spec:
  type: ClusterIP
  ports:
    - name: tcp-mqtt
      port: 31883
      targetPort: 31883
      protocol: TCP
  selector:
    app: chirpstack-mosquitto

validate the dns
root@ubuntu:/# dig -t A chirpstack-mosquitto
;; Warning: Message parser reports malformed message packet.

; <<>> DiG 9.16.8-Ubuntu <<>> -t A chirpstack-mosquitto
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61934
;; flags: qr rd ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;chirpstack-mosquitto.		IN	A

;; ANSWER SECTION:
chirpstack-mosquitto.	64	IN	A	<IP_ADDRESS>

;; Query time: 0 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Thu Jun 10 13:45:27 CST 2021
;; MSG SIZE  rcvd: 54

pub and sub the broker of service -> endpoints
mosquitto_sub -h chirpstack-mosquitto -p 31883 -t test

mosquitto_pub -h chirpstack-mosquitto -p 31883 -t test -m 'hello'

edgemesh's log
I0610 05:27:48.565550       1 dns.go:298] [EdgeMesh] dns server parse chirpstack-mosquitto ip <IP_ADDRESS>
W0610 05:27:48.565628       1 dns.go:136] [EdgeMesh] failed to resolve dns: get from real dns
I0610 05:27:48.571146       1 serviceproxy.go:53] ip: <IP_ADDRESS> port: 31883
I0610 05:27:48.571192       1 serviceproxy.go:125] newProtocolFromSock().svcPorts:tcp,31883,31883|http,32901,32901|default.chirpstack-mosquitto
W0610 05:27:48.571259       1 strategy.go:21] failed to find default.chirpstack-mosquitto DestinationRule, use default strategy RoundRobin from config file
I0610 05:27:48.571267       1 tcp.go:84] MicroServiceName:chirpstack-mosquitto.default.svc.cluster.local:31883, Endpoint:, Port:, SourceServiceID:, Protocol:tcp, Strategy:RoundRobin, Args:[]
I0610 05:27:48.571284       1 log.go:181] DEBUG: add [2] handlers for chain [tcp]
I0610 05:27:48.571440       1 tcp.go:120] responseCallback:ep:<IP_ADDRESS>:31883
I0610 05:27:48.571455       1 tcp.go:144] l4 proxy get server address: <IP_ADDRESS>:31883
I0610 05:27:48.572029       1 tcp.go:187] l4 Proxy start a proxy to server <IP_ADDRESS>:31883
I0610 05:27:48.623079       1 tcp.go:212] processClientProxy read err: EOF
I0610 05:27:48.623282       1 tcp.go:257] processServerProxy read err: EOF
E0610 05:27:48.623295       1 tcp.go:260] rconn close err: close tcp <IP_ADDRESS>:49800-><IP_ADDRESS>:31883: use of closed network connection
E0610 05:27:48.623306       1 tcp.go:264] lconn close err: close tcp <IP_ADDRESS>:40001-><IP_ADDRESS>:40780: use of closed network connection

Failed case
将宿主机的mosquitto当作外部资源引入到Service层，这种方式需要先创建Endpoints，然后创建同名的Service与之对应。
Mapping the host's mosquitto as an external resource to the Service layer. In this way, you need to create Endpoints first, and then create a Service with the same name to correspond to it.
endpoints -> service

endpoint-edge1.yaml

kind: Endpoints
apiVersion: v1
metadata:
  name: mosquitto-host-edge1
  namespace: default
subsets:
  - addresses:
      - ip: <IP_ADDRESS>
    ports:
      - port: 1883
        name: tcp-mqtt-edge1

service-edge1.yaml

apiVersion: v1
kind: Service
metadata:
  name: mosquitto-host-edge1
spec:
  ports:
    - port: 1883
      name: tcp-mqtt-edge1
      protocol: TCP

validate the dns
root@ubuntu:/# dig -t A mosquitto-host-edge1
;; Warning: Message parser reports malformed message packet.

; <<>> DiG 9.16.8-Ubuntu <<>> -t A mosquitto-host-edge1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58529
;; flags: qr rd ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;mosquitto-host-edge1.		IN	A

;; ANSWER SECTION:
mosquitto-host-edge1.	64	IN	A	<IP_ADDRESS>

;; Query time: 0 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Thu Jun 10 13:30:08 CST 2021
;; MSG SIZE  rcvd: 54

sub the broker of endpoint -> service
mosquitto_sub -h mosquitto-host-edge1 -p 1883 -t test

NOTE! Start the mosquitto_sub process, the edgemesh continue to report errors.
edgemesh's log
I0610 05:31:43.840156       1 dns.go:298] [EdgeMesh] dns server parse mosquitto-host-edge1 ip <IP_ADDRESS>
W0610 05:31:43.840216       1 dns.go:136] [EdgeMesh] failed to resolve dns: get from real dns
I0610 05:31:43.845059       1 serviceproxy.go:53] ip: <IP_ADDRESS> port: 1883
I0610 05:31:43.845071       1 serviceproxy.go:125] newProtocolFromSock().svcPorts:tcp,1883,1883|default.mosquitto-host-edge1
W0610 05:31:43.845138       1 strategy.go:21] failed to find default.mosquitto-host-edge1 DestinationRule, use default strategy RoundRobin from config file
I0610 05:31:43.845144       1 tcp.go:84] MicroServiceName:mosquitto-host-edge1.default.svc.cluster.local:1883, Endpoint:, Port:, SourceServiceID:, Protocol:tcp, Strategy:RoundRobin, Args:[]
I0610 05:31:43.845152       1 log.go:181] DEBUG: add [2] handlers for chain [tcp]
I0610 05:31:43.845184       1 tcp.go:120] responseCallback:ep:<IP_ADDRESS>:0
I0610 05:31:43.845188       1 tcp.go:144] l4 proxy get server address: <IP_ADDRESS>:0
E0610 05:31:43.845766       1 tcp.go:156] l4 proxy dial server error: dial tcp <IP_ADDRESS>:0: connect: connection refused
I0610 05:31:44.847295       1 dns.go:298] [EdgeMesh] dns server parse mosquitto-host-edge1 ip <IP_ADDRESS>
W0610 05:31:44.847334       1 dns.go:136] [EdgeMesh] failed to resolve dns: get from real dns
I0610 05:31:44.852629       1 serviceproxy.go:53] ip: <IP_ADDRESS> port: 1883
I0610 05:31:44.852655       1 serviceproxy.go:125] newProtocolFromSock().svcPorts:tcp,1883,1883|default.mosquitto-host-edge1
W0610 05:31:44.852688       1 strategy.go:21] failed to find default.mosquitto-host-edge1 DestinationRule, use default strategy RoundRobin from config file
I0610 05:31:44.852693       1 tcp.go:84] MicroServiceName:mosquitto-host-edge1.default.svc.cluster.local:1883, Endpoint:, Port:, SourceServiceID:, Protocol:tcp, Strategy:RoundRobin, Args:[]
I0610 05:31:44.852718       1 log.go:181] DEBUG: add [2] handlers for chain [tcp]
I0610 05:31:44.852765       1 tcp.go:120] responseCallback:ep:<IP_ADDRESS>:0
I0610 05:31:44.852771       1 tcp.go:144] l4 proxy get server address: <IP_ADDRESS>:0
E0610 05:31:44.853449       1 tcp.go:156] l4 proxy dial server error: dial tcp <IP_ADDRESS>:0: connect: connection refused
......

pub the broker of endpoint -> service

sub the topic from edge1 host

[root@ke-edge1 ~]# mosquitto_sub -h <IP_ADDRESS> -p 1883 -t test

pub the topic from pod in the edge

root@ubuntu:/# mosquitto_pub -h mosquitto-host-edge1 -p 1883 -t test -m 'hello'
Error: The connection was lost.

NOTE! Start the mosquitto_pub process, the edgemesh report error, and the mosquitto_sub <IP_ADDRESS> is no message is received.
edgemesh's log

I0610 05:33:14.925329       1 dns.go:298] [EdgeMesh] dns server parse mosquitto-host-edge1 ip <IP_ADDRESS>
W0610 05:33:14.925426       1 dns.go:136] [EdgeMesh] failed to resolve dns: get from real dns
I0610 05:33:14.930465       1 serviceproxy.go:53] ip: <IP_ADDRESS> port: 1883
I0610 05:33:14.930477       1 serviceproxy.go:125] newProtocolFromSock().svcPorts:tcp,1883,1883|default.mosquitto-host-edge1
W0610 05:33:14.930507       1 strategy.go:21] failed to find default.mosquitto-host-edge1 DestinationRule, use default strategy RoundRobin from config file
I0610 05:33:14.930511       1 tcp.go:84] MicroServiceName:mosquitto-host-edge1.default.svc.cluster.local:1883, Endpoint:, Port:, SourceServiceID:, Protocol:tcp, Strategy:RoundRobin, Args:[]
I0610 05:33:14.930519       1 log.go:181] DEBUG: add [2] handlers for chain [tcp]
I0610 05:33:14.930588       1 tcp.go:120] responseCallback:ep:<IP_ADDRESS>:0
I0610 05:33:14.930593       1 tcp.go:144] l4 proxy get server address: <IP_ADDRESS>:0
E0610 05:33:14.931273       1 tcp.go:156] l4 proxy dial server error: dial tcp <IP_ADDRESS>:0: connect: connection refused

I modified part of the log output, trying to find the cause of the error, but I suffered from the lack of knowledge of the principle;
What you expected to happen:
It is passable to run the second test case in the k8s cloud.
Environment:

EdgeMesh version: branch release-1.7

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.10", GitCommit:"98d5dc5d36d34a7ee13368a7893dcb400ec4e566", GitTreeState:"clean", BuildDate:"2021-04-15T03:28:42Z", GoVersion:"go1.15.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.10", GitCommit:"98d5dc5d36d34a7ee13368a7893dcb400ec4e566", GitTreeState:"clean", BuildDate:"2021-04-15T03:20:25Z", GoVersion:"go1.15.10", Compiler:"gc", Platform:"linux/amd64"}

KubeEdge version(e.g. cloudcore --version and edgecore --version):
branch release-1.7

Cloud nodes Environment:

Hardware configuration (e.g. lscpu):
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    2
Socket(s):             2
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 142
Model name:            Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz
Stepping:              12
CPU MHz:               2112.048
BogoMIPS:              4224.00
Hypervisor vendor:     VMware
Virtualization type:   full
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              6144K
NUMA node0 CPU(s):     0-3
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon nopl xtopology tsc_reliable nonstop_tsc eagerfpu pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch fsgsbase tsc_adjust bmi1 avx2 smep bmi2 invpcid rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 arat
OS (e.g. cat /etc/os-release):
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"
- Kernel (e.g. `uname -a`):

Linux ke-master1 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
- Go version (e.g. go version):
go version go1.14.15 linux/amd64
- Others:

- Edge nodes Environment:
Same to cloud

@yz271544 Good issue!
In your successful case, edgemesh works normally, but some error logs are still printed, as you said:
......
E0610 05:27:48.623295       1 tcp.go:260] rconn close err: close tcp <IP_ADDRESS>:49800-><IP_ADDRESS>:31883: use of closed network connection
E0610 05:27:48.623306       1 tcp.go:264] lconn close err: close tcp <IP_ADDRESS>:40001-><IP_ADDRESS>:40780: use of closed network connection
......

This is because we did not gracefully close the tcp connection, which does not affect edgemesh use (but we will optimize it later).
In your failed case, because edgemesh did not associate the Endpoints  when selecting the backend instance, but instead looked for the corresponding podlist, perhaps this was the cause of the error. You can refer to the code: https://github.com/kubeedge/edgemesh/blob/main/pkg/networking/trafficplugin/registry/registry.go#L72

I did not find a file similar to hack/local-up-xxx.sh in the code. I tried to use go-delve with edgemesh code to debug in the k8s virtual machine environment, but the container crashed and exited. Can you describe your development environment below? Can you communicate via email if it's convenient<EMAIL_ADDRESS>

hack/local-up-xxx.sh file will be added in the future. When debugging, you can deploy edgemesh as a binary file instead of a container. Remember to create the edgemesh.yaml file in the /etc/kubeedge/config directory.