ROCm support?

Hey guys,
Just wanted to let you know about this  project, that might allow you to cross-compile alpa to AMD gpus.

Thanks for sharing the information. XLA also supports AMD gpus via ROCm, so this should be possible.
However, we don't have the bandwidth to do this and we don't have AMD GPUs in our hands either.
Community contribution is welcome.


More crystal gazing areas

Untested, and code probably can be far cleaner

Hmm, @Kasekopf what do you think?
On one hand, this PR isn't needed.
On the other, it's future proofing.
On the third freakshow hand, the code could be cleaner?


Power saving mode?

I wanted to ask if a power saving mode for Atom is on the roadmap for future releases.
Power saving mode would turn off many battery intensive feature like background update checks, package update checks, animations and more for the time while it is on.
This would be very helpful if you are running out of battery and really want to squeeze that last extra juice out of your battery and finish writing your code etc.
Thank you all so very much
Cheers!

Most of our power-saving work has been around making Atom battery-friendly when not in the foreground. We generally assume that if Atom is in the foreground, then you want Atom to work like it always does. Also, what will typically save battery more than most things Atom could do are things like:

Spin down hard drives (if still using platter technology)
Turn off WiFi (which would solve the update checks)
Turn down the backlight on your screen

With that said, if there is anything that you see that is anomalous or you have specific suggestions around ways that Atom can save battery, please file an Issue! We'd love to hear about it. (And I'd especially interested. I spent a few years working on power and thermal measurement for mobile devices, so it is a passion of mine.)
I hope that helps answer your question! Let me know if you have any others.


6to5 support

This provides 6to5 builds of ES6-Module-Loader.
Currently passing all tests except circular references and live bindings as expected. Generators also seem not to work naturally without needing to manually include regenerator.
This needs further polishing / testing. Feedback appreciated.
//cc @douglasduteil @sebmck

6to5 now has complete support for ES6 Module Loader. Live bindings, circular dependencies etc.

6to5 now has complete support for ES6 Module Loader. Live bindings, circular dependencies etc.

Awesome we did it :D

Awesome we did it :D

This is really great! I'm aiming to get this full 6to5 support in the next minor release.
I'm also working on ways of properly enabling users to pick a compiler more easily (see https://github.com/ModuleLoader/es6-module-loader/issues/278).

@guybedford This all looks good, what is broken with sourcemaps?

@thejameskyle thanks for checking it out - I just haven't tested them fully, but if they're working then that is great to hear!
This may be a little while yet as I'd like to get this in with some other changes, it is not being forgotten though certainly.

This is blocked by https://github.com/ModuleLoader/es6-module-loader/issues/278.

Full disclosure: This is my first attempt to use es6 modules, so I'm probably missing something obvious.

I'm trying this out on a toy project and am trying load a single module with no dependencies called goodtimes/year. It looks like this:
export default class Year {
  constructor(timezone, value = new Date(Date.UTC()).getFullYear()) {
    this.zone = timezone;
    this.value = value;
  }

  get date() {
    var date = new Date(36000);
    date.setFullYear(this.value);
    return date;
  }
};

When I do a System.import('goodtimes/year')
It successfully, loads and transpiles the module, but when executing its body, I get the following exception:
Potentially unhandled rejection [2] ReferenceError: to5Runtime is not defined
    at eval (eval at __eval (http://localhost:9876/base/vendor/es6-module-loader-6to5.src.js:2732:105), <anonymous>:18:9)
    at System.register.execute (eval at __eval (http://localhost:9876/base/vendor/es6-module-loader-6to5.src.js:2732:105), <anonymous>:31:9)
    at doExecute (http://localhost:9876/base/vendor/es6-module-loader-6to5.src.js:2053:22)
    at ensureEvaluated (http://localhost:9876/base/vendor/es6-module-loader-6to5.src.js:2100:11)
    at doEnsureEvaluated (http://localhost:9876/base/vendor/es6-module-loader-6to5.src.js:2063:15)
    at evaluateLoadedModule (http://localhost:9876/base/vendor/es6-module-loader-6to5.src.js:2038:5)
    at http://localhost:9876/base/vendor/es6-module-loader-6to5.src.js:2226:20
    at tryCatchReject (http://localhost:9876/base/vendor/es6-module-loader-6to5.src.js:1177:30)
    at runContinuation1 (http://localhost:9876/base/vendor/es6-module-loader-6to5.src.js:1136:4)
    at Fulfilled.7.Fulfilled.when (http://localhost:9876/base/vendor/es6-module-loader-6to5.src.js:927:4)es6-module-loader-6to5.src.js:139 (anonymous function)es6-module-loader-6to5.src.js:166 reportes6-module-loader-6to5.src.js:188 flush

The content of the transpiled source:
(function() { var __moduleName = "goodtimes/year"; var __moduleAddress = "/base/lib/goodtimes/year.js";System.register([], function (_export) {
  "use strict";

  var Year;
  return {
    setters: [],
    execute: function () {
      Year = (function () {
        function Year(timezone) {
          var _this = this;
          var value = arguments[1] === undefined ? new Date(Date.UTC()).getFullYear() : arguments[1];
          return (function () {
            _this.zone = timezone;
            _this.value = value;
          })();
        }

        to5Runtime.prototypeProperties(Year, null, {
          date: {
            get: function () {
              var date = new Date(36000);
              date.setFullYear(this.value);
              return date;
            },
            enumerable: true,
            configurable: true
          }
        });

        return Year;
      })();
      _export("default", Year);
    }
  };
});
//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJzb3VyY2VzIjpbIi9iYXNlL2xpYi9nb29kdGltZXMveWVhci5qcyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOzs7TUFBcUIsSUFBSTs7OztBQUFKLFVBQUk7QUFDWixpQkFEUSxJQUFJLENBQ1gsUUFBUTs7Y0FBRSxLQUFLLGdDQUFHLElBQUksSUFBSSxDQUFDLElBQUksQ0FBQyxHQUFHLEVBQUUsQ0FBQyxDQUFDLFdBQVcsRUFBRTs4QkFBRTtBQUNoRSxrQkFBSyxJQUFJLEdBQUcsUUFBUSxDQUFDO0FBQ3JCLGtCQUFLLEtBQUssR0FBRyxLQUFLLENBQUM7V0FDcEI7U0FBQTs7dUNBSmtCLElBQUk7QUFNbkIsY0FBSTtpQkFBQSxZQUFHO0FBQ1Qsa0JBQUksSUFBSSxHQUFHLElBQUksSUFBSSxDQUFDLEtBQUssQ0FBQyxDQUFDO0FBQzNCLGtCQUFJLENBQUMsV0FBVyxDQUFDLElBQUksQ0FBQyxLQUFLLENBQUMsQ0FBQztBQUM3QixxQkFBTyxJQUFJLENBQUM7YUFDYjs7Ozs7O2VBVmtCLElBQUk7O3lCQUFKLElBQUkiLCJmaWxlIjoiL2Jhc2UvbGliL2dvb2R0aW1lcy95ZWFyLmpzIiwic291cmNlc0NvbnRlbnQiOlsiZXhwb3J0IGRlZmF1bHQgY2xhc3MgWWVhciB7XG4gIGNvbnN0cnVjdG9yKHRpbWV6b25lLCB2YWx1ZSA9IG5ldyBEYXRlKERhdGUuVVRDKCkpLmdldEZ1bGxZZWFyKCkpIHtcbiAgICB0aGlzLnpvbmUgPSB0aW1lem9uZTtcbiAgICB0aGlzLnZhbHVlID0gdmFsdWU7XG4gIH1cblxuICBnZXQgZGF0ZSgpIHtcbiAgICB2YXIgZGF0ZSA9IG5ldyBEYXRlKDM2MDAwKTtcbiAgICBkYXRlLnNldEZ1bGxZZWFyKHRoaXMudmFsdWUpO1xuICAgIHJldHVybiBkYXRlO1xuICB9XG59O1xuIl19!eval
 }).call(__global);

I'm seeing on this  branch, and  using 6to5/browser.js packaged with 6to5 2.12.3.

It looks like runtime is being set to true but the actual runtime isn't being included.

Thanks @sebmck. I was basing my setup on the tests in this PR (which I didn't run).  For anybody else encountering this issue, details about the 6to5 runtime are here. http://6to5.org/docs/usage/runtime/

I've updated this branch, all tests will be passing pending the fixing of https://github.com/6to5/6to5/pull/555 and https://github.com/6to5/6to5/issues/553.
Note that the export * override test is failing due to the fact that carefully supporting export * clobbering is not currently planned for implementation in 6to5 so we should skip this test.
Source maps are all working properly with line-debugging in chrome.

Great! If it's fine with you I'd like to time this with the release of 6to5 3.0.0 which should be out by next week.

Sure, that would work great. Keep me in the loop, it would be nice to be able to time the SystemJS and jspm support as well.

I've rebased to use the new test system added from @douglasduteil's work.
The remaining tests should pass pending 6to5 version 3 which is coming out soon.


Suggestion: Add an option for Corner Tile Indicators

I'd like to toggle a setting in "True Tile Overlay Settings" to replace the tile indicator for the true tile metronome with the Corner Tile indicator like the one provided by the hub plugin with the same name

I checked it out and it's a cool plugin idea, but not sure if the creator of that plugin would like it if I just copy pasted his plugin into this one.
If you want you can ask the creator of the plugin if they want to make a pull request here and add it themselves, or give me permission to add it then that could work


bugfix(driver/gpio): Fix SIG_GPIO_OUT_IDX comment for signal connect

This PR aims to fix the comment regarding SIG_GPIO_OUT_IDX in esp_rom_gpio_connect_out_signal by commenting on the signal_idx parameter and not on gpio_num. This avoids the misunderstanding that the GPIO number needs to be set to SIG_GPIO_OUT_IDX rather than the signal number.

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

sha=64f8222ec6badc13bce0759bac1afd80efd91acb


Add CHANGELOG

Fixes #382

Why not provide this file to release action?

bodyFile:	An optional body file for the release. This should be the path to the file.

I'm okay with manual effort for now. Will discuss automation later depending on how frequently we change features. We might also work on automatic release notes generation based on commit messages. For now, manual changelog is enough to satisfy the expectation of the community.

For now, manual changelog is enough

You plan to copy changelog for every release? It's inconvenient to keep the changelog only in code. F.e. to check the changelog for older versions you need to find the corresponding commit in the repository , rather than just read it from the release post.

I don't see any ambiguity in the decision to publish the release notes. Generating them based on commits is a separate step that can be done later. But publishing notes from the file are the minimum for comfortable use of the library.
So far, no differences between versions 1.x.x and 2.x.x have been published anywhere. It is not clear to users what to expect from the new version and how to migrate to it. That's why we within the team are still using version 1.2.3.

I don't see any ambiguity in the decision to publish the release notes. Generating them based on commits is a separate step that can be done later. But publishing notes from the file are the minimum for comfortable use of the library. So far, no differences between versions 1.x.x and 2.x.x have been published anywhere. It is not clear to users what to expect from the new version and how to migrate to it. That's why we within the team are still using version 1.2.3.

Adding older changelog manually is not in scope for this PR. Also, not possible through release action, as older releases doesn't have accurate notes for all versions.
For now, you can go through our docs (https://kermit.touchlab.co/docs/) and Kermit samples to try out the newer version.

So, how much more time needed to add changelog?


Intelisense doesn`t work currently for Blazor component .razor files in VS2019 latest version

To Reproduce
Steps to reproduce the behavior:

Create .razor file
Add some logic and view
Close and open .razor file while intelisense dont stop working
See error

Expected behavior
Intelisense helps with namespace including

Create .razor file
Add some logic and view
All working as with cshtml file

Screenshots
Current

Expected result:

@olkuziv Please make sure you are using the latest Visual Studio Preview release (https://visualstudio.com/preview). Blazor tooling requires Visual Studio updates that are not available in the stable release of Visual Studio 2019.
I'm going to go ahead and close this issue, but if you still have issues with the latest Visual Studio preview, please let us know!

I was install latest preview version. Result stay the same:

@olkuziv Is the namespace of the MainLayoutModel type in scope? What happens if you qualify MainLayoutModel with it's namespace?

When i full path all is working

@olkuziv Could you please share the .csproj file contents for the project that is not showing correct intellisense?

Closing due to lack of response.


Add new plugin-e2e package

This PR adds the new plugin-e2e package that will eventually replace the grafana/e2epackage (details in this PR). Upgrading the tests to the newest package will also address several security issues associated with the grafana/e2e package that is currently not being maintained.

Closes #244


Flutter App Demo server not working <IP_ADDRESS>

Hello guys. Im trying to connect to the webrtc server with this wss://<IP_ADDRESS>:4443 but I can't connect. I tried this wss://demo.cloudwebrtc.com:4443 and it works but the webrtc running on the node can;t connect to the demo app on mobile. can you help me with this one? i'm new with web rtc stuffs

try your local IP Adress


Remove trailing comma so that it is valid JSON

Loading the Heroku app gives me Manifest parsing error: Line: 14, column: 2, Trailing comma not allowed.

GAH, 😥.Thanks!


[EventGrid] updating healthcare enums

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-eventgrid


[DDW-590] Bump cardano-wallet

This PR bumps cardano-wallet to the tip of the latest master branch: https://github.com/input-output-hk/cardano-wallet/commit/1b42a42b58c4f5c8c49de65bd5c5786b01f1b2a5.
Todos

[x] Rename asset acronym to ticker
[x] Update to the new CWB release once it becomes available.

Testing Checklist

Slack QA thread
[ ] Run regression testing

Review Checklist
Basics

[ ] PR has been assigned and has appropriate labels (feature/bug/chore, release-x.x.x)
[ ] PR is updated to the most recent version of the target branch (and there are no conflicts)
[ ] PR has a good description that summarizes all changes
[ ] PR has default-sized Daedalus window screenshots or animated GIFs of important UI changes:

[ ] In English
[ ] In Japanese

[ ] CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance and unit tests are passing (yarn test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (yarn dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (yarn package / CI builds)
[ ] There are no flow errors or warnings (yarn flow:test)
[ ] There are no lint errors or warnings (yarn lint)
[ ] There are no prettier errors or warnings (yarn prettier:check)
[ ] There are no missing translations (running yarn manage:translations produces no changes)
[ ] Text changes are proofread and approved (Jane Wild / Amy Reeve)
[ ] Japanese text changes are proofread and approved (Junko Oda)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (yarn storybook)
[ ] In case of dependency changes yarn.lock file is updated

Code Quality

[ ] Important parts of the code are properly commented and documented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-renderings
[ ] Any code that only works in main process is neatly separated from components

Testing

[ ] New feature/change is covered by acceptance tests
[ ] New feature/change is manually tested and approved by QA team
[ ] All existing acceptance tests are still up-to-date
[ ] New feature/change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review

[ ] Merge the PR
[ ] Delete the source branch
[ ] Move the ticket to done column on the YouTrack board
[ ] Update Slack QA thread by marking it with a green checkmark

@gabriela-ponce @ManusMcCole @miorsufianiohk this one is ready for regression testing 🙏


add currency_id attribute to the sales invoice

Add missed attribute to the sales invoice object

@v-may thanks for pull request :+1:


Update pull requests with pending status as soon as possible

These changes will move the responsibility of updating a pull request witha "pending" status to the jenkins pipeline. This ensures that the pull request is updated with a pending status as soon as possible.
This change will also ensure that if an unexpected error occurs during the testing process, the pull request will still be updated with a failure status rather than left in a pending state.
An additional change removes the title and body of pull requests from webhook data. This ensures that possible issues parsing unexpected characters in the body and title of a pull request cannot occur. In testing, I saw issues not just with JSON parsing the title and pull request, but also with passing the data to the Docker build, passing the data to the openshift build, and passing the data to the jenkins plugin.
Note that the changes in this pull request will not take affect until merged. I expect tests to fail for this pull request since I've changed the data being passed to the docker build. Tests should however work when submitting against prod after merged into stg.

@twiest @kwoodson this is ready for review when you have time.
A lot of refactoring was required to get this working right, but I think it was definitely worth the time and effort.

Tests are failing, as expected, due to the name of the environment variable supplied to the build being changed:
Unable to load JSON data from $GITHUB_WEBHOOK_PAYLOAD

@tiwillia the bot didn't run against this PR, not sure why.
Will this PR fix that?
I went ahead and approved hoping so.

@twiest Tests did actually run for this PR (and the other you emailed me about), but the PR status was never updated with a link to the jenkins build. These changes will ensure that the PR is updated with a link to the build and if an unexpected error occurs during testing (like in these PRs), the PR will be updated with a "tests failed to run" status.
As for why the other PR failed, I'm investigating and will let you know.


The Tiling Layer

I think I'm ready to get started on the tiling layer now that we have a pretty decent floating layer.
Can someone get me started on how this might be done?

So previous versions of Way Cooler had i3 like tiling. However, for Awesome tiling the tiling is done "entirely" through Lua.
I say "entirely" because obviously the compositor (or X in Awesome's case) still needs to know where to put the clients. Thankfully we can share the same representation and use the Lua state directly, like we are already doing for the drawins to render the status bar.
We'll probably need to implement the API of almost everything in this issue for the Lua libraries to call. Then we "just" grab the coordinates and other information from the client structure and render it (here is how Awesome defined it, ours will be similar potentially).
Now I'm not sure of how this interacts with standard drawins. Are they treated as clients as well? Are clients always other clients or could they just be other floating "windows" that Awesome creates (like popups and the like)? If so then that will complicate this (and if not, wee we can just stick an View in there and do that). @psychon will probably know more.
This is definitely the biggest and ugliest API to implement, but once it is implemented tiling should "just werk".

Oh ok, what's the first thing to do?

I don't know what exactly part of the API is needed (except definitely geometry). You can see what's necessary with the errors that are spat out on the console.

I don't know what exactly part of the API is needed (except definitely geometry).

I would guess geometry. However, before that, clients need to be actually created for any windows that the compositor manages and the manage signal has to be emitted (and I guess unmanage for when they go away). I would start with implementing this and then stubbing methods until the resulting errors go away. :-)
Next step would IMO be to implement client.get which lets Lua query the list of all clients, but this could again cause lots of errors for unimplemented APIs.
Before the above is done, the Lua code will not assign geometry to clients anyway.

Now I'm not sure of how this interacts with standard drawins.

Short version: For now this can be ignored. The only interaction that I see is "stacking order" and that can be handled much later, I guess.
Long version:
In awesome, drawins and clients "inherit" from something internal called "window". A window (basically) has a geometry (Area in way-cooler).
Right now, the only important interaction that I can come up with is the stacking order. This is defined/handled in stack.c, but I guess could be ignored for now. Anyway: A window is assigned some layer and the order is like this:

clients with .type == "desktop" at the bottom.
clients with .below == true
drawins with .ontop == false
clients not assigned to any other layer
clients with .above == true
clients with .fullscreen == true
clients with .ontop == true
drawins with .ontop == true

Oh and one more thing: transient windows (e.g. a "Open file" dialog) are ignored by the algorithm and are instead stacked ontop of their parent window.
Inside the layers, the order is basically "in order of creation". For drawins, no one yet had a reason to be able to influence this, but for clients, the C code can influence this. For this, there is a single, global list of all clients (globalconf.stack) and Lua can influence the order in this list via client:swap(other_client). (And for rendering, you basically filter this list for clients that are assigned to the currently active layer)

Tiled layouts are configured per tag, so I think I need to do basic tags first.

I thought "basic tags" were done already? They can be selected and activated. The only missing piece would be :clients(), which is a "TODO / FIXME" in src/awesome/tag.rs, I guess (I have not checked).


md files

Is it possible to have in each project a readme.md with a short project descriptions and dependencies?
:)Torsten

Now you’re just being picky!  :)
Will do…
From: Torsten Schuster<EMAIL_ADDRESS>Sent: Wednesday, August 12, 2015 6:25 AM
To: ms-iot/samples<EMAIL_ADDRESS>Subject: [samples] md files (#44)
Is it possible to have in each project a readme.md with a short project descriptions and dependencies?
:)Torsten
—
Reply to this email directly or view it on GitHub https://github.com/ms-iot/samples/issues/44 .  https://github.com/notifications/beacon/AKXoTxzt5zZ1Kb5KsUPcxAC0ZKoJTAf7ks5omySegaJpZM4FqIKk.gif

Our strategy has been to create in depth descriptions on our documentation site (look under the Samples tab):
http://ms-iot.github.io/content/en-US/win10/StartCoding.htm
Please take a look!

Thanks i got it. If this link is not in the Main MD file it would be helpfull to place them there also, i think.

That makes a lot of sense!  We'll look into getting the link into our MD files.

Why not keep that file with the project code in the MS-IOT/Samples repository? That way updates to the documentation can be part of the specific project updates. Could have an automatic copy mechanism to https://github.com/ms-iot/content/tree/develop/en-US/Docs.
PS I am looking at contributing a new project to Samples. How do I currently get my .md file up into Docs?

Please see https://github.com/ms-iot/content/blob/develop/README.md on how to add new .md files for Docs.You would need to also update _data_docs-index.json to add a link to new doc.

Closing Stale - Site has been overhauled and is scheduled for another soon.


Add some clarifications to the Azure Files documentation

@neilpeterson - Would you review the proposed changes? Thank you.


added fluent .properties

added .properties for the fluent builder.
            var props = new Dictionary<string, object>
            {
                {"prop1", "1"},
                {"prop2", "2"},

            };

            _logger.Trace()
                .Message("This is a test fluent message.")
                .Properties(props).Write();

Fixes https://github.com/NLog/NLog/issues/724

Has unit test, but not a good one. See https://github.com/NLog/NLog/issues/911


Entity with @Column('simple-array') fails to seed

Some column-types in typeorm are resolving to objects. For example entitites with column-type "simple-array" failing to seed because the following expression is "true":
https://github.com/w3tecch/typeorm-seeding/blob/9e9c59118a5a4bbc171d3c4eb79e0f15523976ac/src/entity-factory.ts#L90
and the subentity can't be resolved. These issue is even harder to grasp, because the thrown error says simply "Error: Could not save entity".

the same issue with @column({ type: ''json })

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Added Burmese Text

Max,
I have added the translations. There are a couple more required (they have been kept in English for now). This branch is based on this PR - #155 . Please merge the parent PR before merging this one.
The only file which has been changed is - RcdaTextBurmese.ts
Let me know in case of any issues. Thanks!

@blueelvis Looks good, ready to land this, but can you rebase this onto just dev so it isn't associated with content from the other branches that haven't landed yet?

@maxnorth  -- Rebased from Dev and added the missing translations. Could you please verify this once? I see above some of your commits as well? o.O


Update requirements.in

Just testing for now

Hi @mihaimaruseac Can you please review this PR ? Thank you!


Dead Code in Example

Describe the Issue
We have code that does nothing in this example.
Affected Page
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/basic-javascript/using-objects-for-lookups
Your code
const alpha = {
  1:"Z",
  2:"Y",
  3:"X",
  4:"W",
  ...
  24:"C",
  25:"B",
  26:"A"
};

alpha[2]; // This does nothing
alpha[24]; // This does nothing

const value = 2;
alpha[value]; // This does nothing

Expected behavior
We should update the example to include meaningful example code.
Perhaps:
const alpha = {
  1:"Z",
  2:"Y",
  3:"X",
  4:"W",
  ...
  24:"C",
  25:"B",
  26:"A"
};

const thirdLetter = alpha[2];
const lastLetter = alpha[25];

const value = 2;
const valueLookup = alpha[value];

Screenshots
No response
System
All
Additional context
No response

Thanks for opening this issue.
This looks something that can be fixed by "first time" code contributors to this repository. Here are the files that you should be looking at to work on a fix:
List of files:

https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/02-javascript-algorithms-and-data-structures/basic-javascript/using-objects-for-lookups.md

Please make sure you read our guidelines for contributing, we prioritize contributors following the instructions in our guides. Join us in our chat room or the forum if you need help contributing, our moderators will guide you through this.
Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first.
Happy contributing.

I would like to work on this issue.

Welcome @Dhruv-Gajjar, as described in the documentation, issues are up for grubs, they are not assigned, so feel free to work on it.


Not showing Liveries

I can't see the liveries i used the code main.js

Can you please send me a screenshot with the geofs and the console (ctr+shift+i)? I have no idea what the problem is. :(

here


Incompatability with Camping Tools

UpdateCaloriesInPrefab is throwing an NPE when this mod is installed.

it throws NRE whenever something else makes Modcomponent error, it's been like this since forever and unless something changed in MC - there is no incompatibility, likely just incorrect installation of some other MC mod

oh whoops it's a month old issue 😅

it throws NRE whenever something else makes Modcomponent error, it's been like this since forever and unless something changed in MC - there is no incompatibility, likely just incorrect installation of some other MC mod

half a year later i see this, it's really good to know what actually causes it. learning experiences


WorkloadEntry will only get implicit network from environment for remote clusters

https://github.com/istio/istio/blob/d9fe12a9901e88e830afc9ab487663f681779876/pilot/pkg/serviceregistry/kube/controller/multicluster.go#L179 -- this works for remote clusters.
But for the same cluster, we never set this.
its hard to fix since to build kubeRegistry we need serviceEntryController, so we have a circular dependency

Maybe we need to pull out a per-cluster "network id provider". This needs to watch:

meshNetworks from config map in the control plane's  own cluster
system namespace in the watched cluster

and we pass in:

labels to detect network from
clusterId to use when we look at meshNetworks fromRegistry stuff

Not stale


Increasing memory usage while

I hope you don't mind posting my questions as issues...
I am interested in using this library ovds-utils to make an xarray engine for VDS so that we can use VDS directly with xarray.  How to add a new backend
I have made a new backend for it, and it works, but I noticed that when I load subsets of the volume, I get incrementing memory usage. I believe this is because of caching, or something like that. I am opening pieces of the vds volume using xarray in chunks, for example to get a slice or a small subset.
But it is not clear to me how to best handle doing an operation and returning the slice result without keeping all of the other chunks
How do you handle this scenario? I will make a repo for the VDS engine and post it here so you can take a look if you are interested.

Also take a look how __getitems__ method work https://github.com/micmurawski/ovds-utils/blob/be1882436e784d95171936187d4ca1d230388acb/src/ovds_utils/vds.py#L225


Update to 6003001 & Flex Support

Checklist

[x] App update process has been followed
[x] Target branch is develop
[x] Application version has been bumped

https://ledgerhq.atlassian.net/browse/B2CA-1745