Initial implementation of new jsg module registry

RM-17318
First step of the new module registry implementation (the jsg only bits). Expect several more follow up PRs.
This PR provides the initial core of the new module registry implementation. It DOES NOT enable it in workerd at all, this is just the core implementation in workerd/jsg plus tests. Note that this will be gated with a compatibility flag because there are observable changes in behavior. The old module registry implementation will continue to exist but it will be incrementally refactored a bit later to reduce some complexities and eliminate some redundancies.
The new tests should illustrate fairly clearly how the new registry implementation works. I recommend spending a fair amount of time reading through the test code.
Here's a tl;dr with some highlights.
Every Worker will have a ModuleRegistry that is built when the worker is created. The ModuleRegistry is composed of zero or more ModuleBundles. It is the reponsibility of the ModuleBundle to actually manage and maintain the Modules.
A ModuleRegistry::Builder is used to create the ModuleRegistry. Multiples types of ModuleBundles can be added:

The BUNDLE type ModuleBundle contains modules from the worker configuration bundle itself.
The BUILTIN type ModuleBundle contains modules from the runtime that can be imported by user code
The BUILTIN_ONLY type ModuleBundle contains modules from the runtime that can only be imported by other built-ins
The FALLBACK type ModuleBundle is used to provide dynamic resolution using a fallback service (for local dev)

Importantly, the ModuleBundle is a virtual type that can be implemented in multiple ways. This will give us long term flexibility to add new kinds of modules from different kinds of sources without having to modify workerd/jsg directly to support them.
Once a ModuleRegistry is created it is entirely immutable other than any internal caching a ModuleBundle might do to optimize performance or ensure consistent resolution.
Importantly, a ModuleRegistry only needs to be built once. While workerd will only ever use a ModuleRegistry instance with a single Worker, the production environment may share a single instance across multiple replicas. The ModuleRegistry may be bound to any number of v8::Isolates.
All import specifiers are URLs. For BUNDLE Modules, the URL base is always file:///. For BUILTIN and BUILTIN_ONLY Modules, the base is always some built-in prefix like node: or cloudflare: or workerd:. FALLBACK type modules have a bit more flexibility on the base URL.
ESM modules support import.meta.url and import.meta.resolve(...).
New module types can be added without making any modifications to workerd/jsg.
All modules are resolved and evaluated lazily (when they are first imported). Dynamic imports and sync requires run within the current IoContext (if any) so they can schedule i/o (e.g. fetch, scheduler.wait(...), setTimeout(...)) if there is a current IoContext.
Expanded metrics are supported (via a new ResolveObserver) so we can measure resolution times and track which built-ins are actually being used.
All ESM modules (and eventually all CommonJS modules) will use v8 compile cache.
So... why do this at all? There are a number of intended goals:

Treat all import specifiers as URLs (per web platform standards)
Implement web platform standard import.meta.url, import.meta.resolve(...), and import.meta.main
Soon, support TC-39 import attributes
Resolve and evaluate all modules lazily
Allow all replicas of a worker to use the same ModuleRegistry (avoid rebuilding it for every replica)
Support compile cache for all ESM/CJS modules
Improve impl of fallback resolution service for local dev
Allow dynamic imports/requires to be IoContext aware
Enable nodeJsCompatModule to use node.js built-ins without needing the nodejs-compat flag (eventually, not covered in this PR)
Allow workerd internals to use node.js built-ins even when legacy service worker syntax is used
Allow easier introduction of new module types (can be added without modifying workerd/jsg)
Improve observability and metrics
Improved maintainability

Some details on handling import specifiers as URL:

All modules contained in a worker bundle use file:/// as the default base URL. We don't actually expose a filesystem in workerd so these aren't actual file paths but using file:/// is consistent with other runtimes, such as Node.js
Worker bundles CAN specify full absolute URLs other than file:///. For instance, they can shadow built-ins like node:buffer, or even use http:// URLs. These are used only as identifiers and never actually are used for http requests.
Single and double dot segments are normalized in the specifier. For instance, the import specifiers foo/../bar and bar are equivalent.
Relative import specifiers are resolved relative to the module that is importing them. For instance, if the importing module has a base URL of file:///foo, then the import specifier bar will resolve to file:///bar. However, if the importing module has a base URL of file:///foo/ (with a trailing slash), then the import specifier bar will resolve to file:///foo/bar.
Percent-encoding in the specifier path is normalized. For instance %66oo is normalized to foo.
Query strings and fragments in the specifier are significant in that they will resolve to the same underlying module but will result in a new evaluated instance. For example, foo?x and foo?y will cause the module registry to resolve the module file:///foo only once but the specifiers will evaluate into two separate instances of the module. This is consistent with the behavior we see in other runtimes.

Few other bits and pieecs:

Import attributes are explicitly unsupported right now. This is per the recommendation of the TC-39 proposal that asks embedders to explicitly reject import attributes that are not understood in order to preserve backwards compatibility.
Alias specifiers are supported. This means the module registry can map one import specifier as an alias of another import-maps style. If file:///foo is registered as an alias of file:///bar, then both will resolve the same underlying Module but will be instantiated as two different instances.
WASM modules are compiled once and cached. When multiple instances are evaulated, the cache will be used, speeding initialization and reducing memory.

TODOs...

[ ] Review Asan failures reported in github CI

Does this address https://github.com/cloudflare/workerd/issues/854#issuecomment-1675324298 ?

Separated out a couple of the smaller changes to separate PRs in #1823 and #1824

Separated a bit more of this out into a separate PR https://github.com/cloudflare/workerd/pull/1977 ... just trying to shrink the size a bit more.

[build] Note that as of #2012 we no longer use a glob for the JSG source files in src/workerd/jsg/BUILD.bazel – you'll need to explicitly add modules-new.c++ to the set, linking the new test will fail otherwise after rebasing.

I went through the header and some of the tests, the API design looks good! Will continue reviewing this tomorrow.

LGTM otherwise! 😌
I didn't really see correctness issues in the implementation, perhaps the prior comments were already useful for that although we might find some later on. Looks well-designed and coherent overall.
My only ask would be to clean up the foo.slice(0, foo.size()) pattern in the tests I mentioned by using kj::Array/ArrayPtr directly if possible. It appears around 20 times and should be somewhat amenable to Find-Replace. If it feels like something that would slow down the shipping process let's add a TODO for now.

@fhanau .. I believe I've addressed all the feedback thus far.


Drag and drop in tree will open a new tab(firefox)

Reproduction link
https://github.com/SortableJS/Sortable/issues/985
Steps to reproduce
en: In Firefox browser, drag and drop in Tree component will open a new tab.
cn: 在火狐浏览器中, Tree组件的拖拽会引起快捷搜索(并非所有火狐都能复现, 我们的客户复现了, 大概就是拖拽组件的时候浏览器会突然新弹一个搜索页面, 搜索的内容是tree的key)
What is expected?
en: Do not open a tab
cn: 不弹新的tab
What is actually happening?
en: Seach with key of tree's node
cn: 会以tree的key为关键字进行搜索

Environment
Info

ng-zorro-antd
9.3.0

Browser
Firefox

Hi @Mr-Eve
can you submit a PR to fix this?
I have seen some comments here
https://github.com/SortableJS/Sortable/issues/985#issuecomment-282646581

Sure. I'm ready to do that. I need to open a issue before submit a PR. Thanks for your quick reaction.

I'm so sorry to report this problem. I can't run the project, the errors as below. Before run the project, I tried following steps:

git fetch and based on latest master branch
delete node_modules and use yarn install again

Sometimes I can run the project. After several zorro's updates, run fails. And after several updates, I can run it successfully again. That's really weird.

cc @hsuanxyz

try An unhandled exception occurred: Cannot read property ‘Minus’ of undefined ?

try An unhandled exception occurred: Cannot read property ‘Minus’ of undefined ?

I have searched it already, but it doesn't work for me.

@hsuanxyz It looks like have been solved by close firefox's addon. You can find more details in ant-degisn's issue as up. You can try to fix this issue in zorro or close this issue. :D


[AzureMonitorExporter] Add support new HTTP semantics - Dependency Telemetry

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Allow extra nodes to be reported in test harness

High Level Description
Changes the test harness to not fail if more agents than expected appear in the history service agent
list. This is expected to happen if a agent is replaced as in the case of the aws resiliency test
Related Issues
https://jira.mesosphere.com/browse/QUALITY-1424
Checklist for all PR's

[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

@mesosphere-mergebot ship it

@mesosphere-mergebot label ship it


added multiheadattention alias

Continuing from #3552.
Added MultiHeadAttention alias.
Also added sow_weights arg to SelfAttention,  see #3529.

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

Comparison is base (fae3a30) 56.72% compared to head (09f6ea4) 56.72%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3572   +/-   ##
=======================================
  Coverage   56.72%   56.72%
=======================================
  Files         100      100
  Lines       12008    12009    +1
=======================================
+ Hits         6811     6812    +1
  Misses       5197     5197

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Support setuptools.sic in egg_info and bdist_wheel commands

In response to issue #308, PR #2026 added a sic class to allow versions to bypass normalization. Unfortunately this only fixed things for a few cases. Many other aspects of setuptools use safe_version in pkg_resources.
For example, consider a version of "1.2.3.beta". When running python setup.py egg_info, or python setup.py bdist_wheel (using the wheel extension), this will be truncated to 1.2.3b0.
As mentioned by some in issue #308 the full fix appears to be both what the sic function does as well as the monkeypatching of the pkg_resources.safe_version function. Someone even wrote a package to do this.

In https://github.com/pypa/setuptools/pull/2182#pullrequestreview-442538435, I've declined the PR, but outlined suggestions to address the underlying concerns in egg_info and bdist_wheel. I'll re-word this bug to more accurately describe the failed expectation and avoid prescribing a particular remedy.

@jaraco Any update on when this issue will be fixed? If i run "python setup.py egg_info" with a version of 0.1.2.rc.0, it is normalized ot 0.1.2rc0 still

In the aforementioned commit, I drafted the idea I described previously. I'm unsure if it has the intended effect.
There's still a lot of work that's going to have to happen here, namely:

create a test or tests capturing the missed expectation.
determine if changes will also need to be applied to the bdist_wheel command.
determine which calls to safe_version are pertinent to egg_info and bdist_wheel.

Similar behavior for sdist as well. If I run "python setup.py sdist" with version 1.8.0-dev it will be normalizet to 1.8.0.dev.
Please include the sdist into this fix as well.

setuptools/command/egg_info.py, class InfoCommon, method _maybe_tag - keep version type: str or sic
    def _maybe_tag(self, version):
        """
        egg_info may be called more than once for a distribution,
        in which case the version string already contains all tags.
        """
        if self.vtags and version.endswith(self.vtags):
            return version;
        tagged_version = version + self.vtags
        return (sic(tagged_version) if isinstance(version, sic) else tagged_version)

pkg_resources/__init__.py, function safe_version, if someone uses sic - he knows what he do, so there don't need to normalize version if it is sic
    try:
        # normalize the version
        return version if isinstance(version, sic) else str(packaging.version.Version(version))
    except packaging.version.InvalidVersion:
        version = version.replace(' ', '.')
        return re.sub('[^A-Za-z0-9.]+', '-', version)

or instead of modifying _maybe_tag we can override __add__ operator in sic that looks better


CLLocationManager doesn't document accuracy authorization

iOS 14 added accuracyAuthorization and locationManagerDidChangeAuthorization(_:). The Xamarin.iOS CLLocationManager has some new members that seem to correlate, but they are undocumented, both in their XML comments and in the online docs. The online docs only describes the prior authorization API, which is now deprecated but still required for compatibility.

Thanks for your report!


Ldo jsonld refactor

Refactor for more support of ShEx features and a new JSON-LD element

Closed in favor of https://github.com/o-development/ldo/pull/62


Fixed ChefSpec/Fauxhai warning

The warning said in the future that this would be fatal:
WARNING: you must specify a platform and platform_version to your ChefSpec Runner and/or Fauxhai constructor, in the future omitting these will become a hard error

thanks very much!!!


Adds test for RT#126394

Checking that it fails and effectively includes the important message.

👍 Thanks!


New helpTarget CLI config setting

💡Idea
The aim is to add a new CLI config setting that would define if the --help should show up in the console (like now) or open the command sit in CLI for Microsoft 365 docs web page

Setting name
Definition
Default value

helpTarget
Defines the way the command help will be shown. Set console - to show the help in console or web - to open the command docs in default browser
console

Things to consider
This setting should not change the way CLI works when a command failure. So on command fail we should still show help in console output not open the docs web page in default browser every time 😉
Original discussion in Issue
#3958

@pnp/cli-for-microsoft-365-maintainers opening this up for discussion 😉

--online is too generic of a name and in my opinion it's unclear that it relates to help. In the original example from PowerShell brought up by @garrytrinder it's used in conjunction with the Get-Help cmdlet, where it makes sense. spo field set --online is confusing. It would be clearer to use --helpOnline, which would clearly depict the option's purpose and wouldn't possibly collide with future commands.
Also, the short -o is already reserved for the global --output option, so we can't use it here.

My main reason for suggesting that the --online option would work only when with the existing --help option would be used would be to avoid having two options for returning help.
I do take on board however that if we were to introduce --online in another command where it is more relevant, we wouldn't be able to.
I wonder if we actually need to introduce a new option here, maybe this is a setting instead that users can set globally with there preference?

I wonder if we actually need to introduce a new option here, maybe this is a setting instead that users can set globally with their preference?

You mean a setting that when set, would open by default all docs in the browser as opposed to in the terminal?

We could also add online to the list of possible values of #3782.
It's different from the other values in the effect it has, but on the other hand it might fit there nicely...

hmmm @garrytrinder interesting idea 🤔
@pnp/cli-for-microsoft-365-maintainers  what do you think we create CLI config for it how should the --help option work? either open in command in CLI docs webpage in the browser or show the help in the console as now?
@martinlingstuyl I don't quite feel it 🤔. The issue you mentioned is more about which part of docs should be shown and not what to show 🤔. If someone would pick --online then we would show the webpage with full help anyway 😉

We could also add online to the list of possible values of https://github.com/pnp/cli-microsoft365/issues/3782.

Agreed with @Adam-it that it would be confusing to combine online with other --help values.

https://github.com/orgs/pnp/teams/cli-for-microsoft-365-maintainers what do you think we create CLI config for it how should the --help option work? either open in command in CLI docs webpage in the browser or show the help in the console as now?

If think having the ability to automatically open help in the browser would be beneficial, then I think a config setting is the best way forward.

Ok cool, I will update the spec ASAP

Agreed with @Adam-it that it would be confusing to combine online with other --help values.

I was not entirely convinced about it myself as well. If you both don't like it, let's go for the config key instead.

ok I updated the spec
@waldekmastykarz, @martinlingstuyl what do you think about it now?

I'm actually using helpMode for #3782 😄  How about helpTarget?

I'm actually using helpMode for #3782 😄 How about helpTarget?

done ✅

@pnp/cli-for-microsoft-365-maintainers any other remarks or should we open this up ?

Nothing to add. Let's open it up

I could give this a go!

All yours!

Making available due to lack of reply from @MathijsVerbeeck

Can you reassign this one to me please? I'd love to continue the work on this one.


Pairing menu elements belong in the download ... menu

Logically, pairing is related to download and should be moved to the download ... menu.

We decided in the UI meeting not to add for now as it doesn't work most of the time.

fixed. But I am unsure pairing even works on arcade


Update ug with undo and history command

Add description for undo and history command.
Rearrange commands (and command summary) to match order listed in TAPA's manual command.
Add tick and cross emojis to progress command description.
Shorten the header line for sort command since "descending" is mentioned in the description a couple of times.
Add 2 simple questions to FAQ.
Add description to command summary section like Jerrold suggested.

Codecov Report

Merging #141 (5560fad) into master (527b74d) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #141   +/-   ##
=========================================
  Coverage     52.80%   52.80%
  Complexity      546      546
=========================================
  Files           105      105
  Lines          2420     2420
  Branches        318      318
=========================================
  Hits           1278     1278
  Misses         1031     1031
  Partials        111      111

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 527b74d...5560fad. Read the comment docs.


[unblocking_watcher] Server watcher will no longer halt application from disconnecting.

https://github.com/darkChozo/FAbot/issues/13

Looks good...


Upgrade aws java sdk to v2

Change Logs
Describe context and summary for this change. Highlight if any code was copied.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@yihua

LGTM since most of the changes update API usage only. Is there any compatibility issue with different Spark, Flink and Hadoop versions?

So far I have only tested with Spark3 and Hadoop3. And I manually tested the aws hudi features like OCC, GlueSyncTool, CloudWatchMetricsReporter on EMR.
I can try looking into doing some tests with flink but just curious what combinations of version testing I should do before we land this?( Hadoop, Spark, Flink)

@yihua

LGTM since most of the changes update API usage only. Is there any compatibility issue with different Spark, Flink and Hadoop versions?

So far I have only tested with Spark3 and Hadoop3. And I manually tested the aws hudi features like OCC, GlueSyncTool, CloudWatchMetricsReporter on EMR.
I can try looking into doing some tests with flink but just curious what combinations of version testing I should do before we land this?( Hadoop, Spark, Flink)

Synced offline already sometime before.  We should test Spark 2.4, Spark 3.x with Hadoop 2 on S3 to make sure there is no compatibility issue, especially around S3A file system.

Closing this in favor of #9347 .


Add all support for Target Leakage

No linked issues found. Please add the corresponding issues in the pull request description.  Use GitHub automation to close the issue when a PR is merged


Docker multi-arch build

Today, Docker Hub pulls from GitHub and performs a linux/amd64 build on the Dockerfile. We need to perform a linux/arm build as well, and create a :latest manifest from it.

Started the process by creating a buildx workflow.

Now building edge tags and pushing to Docker. Working on tagged releases.

Well, here's another example of learning live on GitHub. Turns out that my vX.Y.z nomenclature was breaking the regex for determining whether we applied the edge or latest tags on automated builds. Changing the nomenclature to just X.Y.z will fix this. Good Times.


Updating a single node

Hey,
Could you help me out update only a single cell? Currently I'm calling the Create grid to update the changes but that's not really efficient.
Thanks

so the line of code that changes the obstacle value for a certain node in a grid is:
Grid[x, y].SetObstacle(true);

So you can call SetObstacle on the Grid object in order to change just that one Node. This doesn't change the tilemap that visually represents the walkable terrain so you would have to change the tilemap tile separately with SetTile or something like that. If you are already changing the tilemap and want to update just the Grid for that tile, you would have to find the x,y positions on the grid that match that world position and the call SetObstacle on the Node at that position

Thanks for replying!
I already updated the visuals, so I only need to update the grid now.
This is what I came up with, but I'm getting an out of bounds error.
  public void  UpdateGrid(Vector3Int updatedCell)
      {
          worldBottomLeft = transform.position - Vector3.right * gridWorldSize.x / 2 - Vector3.up * gridWorldSize.y / 2;
          Vector3Int worldPoint = Vector3Int.FloorToInt(worldBottomLeft + Vector3.right * (updatedCell.x * nodeDiameter + nodeRadius) + Vector3.up * (updatedCell.y * nodeDiameter - nodeRadius));
          Grid[worldPoint.x, worldPoint.y].SetObstacle(true);
      }

Ok, this did the trick. Had to take absolute value, also swap the operator from + to minus.
public void  UpdateGrid(Vector3Int updatedCell)
    {
        worldBottomLeft = transform.position - Vector3.right * gridWorldSize.x / 2 - Vector3.up * gridWorldSize.y / 2;
        print(worldBottomLeft);
        Vector3Int worldPoint = Vector3Int.FloorToInt(worldBottomLeft - (Vector3.right * (updatedCell.x)) - (Vector3.up * updatedCell.y ));
        Grid[System.Math.Abs(worldPoint.x), System.Math.Abs(worldPoint.y)].SetObstacle(true);
    }

I also had to change the offset for the nodeRadius in CreateGrid() from :
Vector3 worldPoint = worldBottomLeft + Vector3.right * (x * nodeDiameter + nodeRadius) + Vector3.up * (y * nodeDiameter + nodeRadius);

To:
Vector3 worldPoint = worldBottomLeft + Vector3.right * (x * nodeDiameter - nodeRadius) + Vector3.up * (y * nodeDiameter - nodeRadius);

As it was detecting the cell one to the left and down.

That's awesome to hear that you got it working! I also was having tile offset problems that I fixed somehow but it's been so long, I can't remember.


Dump Table

This PR implements the function of dumping tables to disk. We build this function on top of the data table layer because we want to make full use of the relaxed Arrow format and the data table is where we have access to blocks.
This PR also fixed two bugs in block_compactor (CopyToArrowVarlen() and BuildDictionary())
RoadMap:

[x] Implement exporting fixed-length columns
[x] Implement exporting variable-length columns
[x] Implement exporting dictionary-compressed columns
[x] (Manually) Debugged and verified that PyArrow can correctly load fixed-length columns
[x] (Manually) Debugged and verified that PyArrow can correctly load variable-length columns
[x] (Manually) Debugged and verified that PyArrow can correctly load dictionary-compressed columns
[x] Automate tests
[x] Improve code style, modularity, etc.

@YuzeLiao If the data is already in the Arrow format, why not write out raw Arrow blocks to disk? What does Flatbuffers provide for us?

@YuzeLiao If the data is already in the Arrow format, why not write out raw Arrow blocks to disk? What does Flatbuffers provide for us?

I think Flatbuffers mainly does metadata serializations. In Arrow's doc, it says "The Arrow columnar memory layout only applies to data and not metadata. Implementations are free to represent metadata in-memory in whichever form is convenient for them. We handle metadata serialization in an implementation-independent way using Flatbuffers, detailed below.", so if we want to use them in different scenarios (Pandas/Numpy for now), we may need to be consistent with Apache Arrow Spec. Actually, in your recently submitted paper,  what the latter half of the third graph of section 2.2 describes is exactly something implemented with Flatbuffers (DDL .........)

Hi @crd477, we're facing some strange issue with this PR on the Jenkins build. Basically we can build it locally and on Travis, but the build always failed during installing gflags on Jenkins under many retries, like here. And this PR does not touch gflags at all. We're wondering would you be able to help us diagnose this issue, or guide us to get the gflags installation error log (gflags_ep-install-*.log) printed out under build failure?

Hi @crd477, we're facing some strange issue with this PR on the Jenkins build. Basically we can build it locally and on Travis, but the build always failed during installing gflags on Jenkins under many retries, like here. And this PR does not touch gflags at all. We're wondering would you be able to help us diagnose this issue, or guide us to get the gflags installation error log (gflags_ep-install-*.log) printed out under build failure?

I'm looking at this now and it's odd.  I can't reproduce it manually even in the same exact environment that Jenkins uses.
Unfortunately, the gflags logs mentioned in that result got automatically cleaned up but I'll see if I can workaround that temporarily for this branch.  I'll let you know what I find.

OK, I believe this is fixed now.  @YuzeLiao, I recommend backing out your control experiment change(s) and trying again.
The error that was generated inside the container was the result of a nonexistent directory inside the Docker builder image that cmake was trying to write to.  I corrected it by adding that directory and re-rolling the image.  While I was doing that, I took the opportunity to refresh the pre-installed package dependencies since I noticed the significant amount of time that was being spent on that step.  The previous version of the image was about 8 months old already.
I still cannot understand how this was never triggered before...

OK, I believe this is fixed now. @YuzeLiao, I recommend backing out your control experiment change(s) and trying again (sorry, was looking at a reversed diff - leave the pandas stuff in...) .
The error that was generated inside the container was the result of a nonexistent directory inside the Docker builder image that cmake was trying to write to. I corrected it by adding that directory and re-rolling the image. While I was doing that, I took the opportunity to refresh the pre-installed package dependencies since I noticed the significant amount of time that was being spent on that step. The previous version of the image was about 8 months old already.
I still cannot understand how this was never triggered before...

Thank you Chad @crd477!

Thanks a lot, @crd477!

@YuzeLiao You can ignore the Travis error. The build timed out. Your code had nothing to do with that.
The Jenkins errors are real though.

@mbutrovich @apavlo This PR is only failing DataTableBenchmark::SelectSequential on Jenkins. But I don't think it modified any layout or existing operations in the DataTable. It only adds the ability to dump the table in the Arrow format. Should we just merge this?

@malin1993ml It seems DataTableBenchmark::SelectSequential also failed on other PRs such as 768 and 790. It may be good to go but feel free to let me know your decision and I can make any further modifications to this PR. Thanks!

@YuzeLiao Sounds good, thanks! We'll discuss this during tomorrow's meeting.

I have some changes to request that I'll type up later. Don't merge yet please.

@mbutrovich I think the review comment is addressed and all the Jenkins tests are passing after merging with the latest master. Shall we merge this one?


Plugin still in use? We've updated the VoIP Call Code for our purposes / Video calls...

...and would like to know if you think it'd be worth adding these changes back to this repo and/or maybe having to make them more "generic" to be able to fulfil both your original purpose (I guess audio only calls?) as well as video calls.
We'll do a WIP PR so you can have a quick look at our changes, you don't have to merge as-is, it's just so you can have a look in case you might be interested in having these changes integrated.
We're also updating cordova-plugin-push in order to enable video calls on the android side too.
All the best!

Hi, I just briefly glanced through the PR. It seems fine if I were to merge it into the current code base if it can help other people.
However, this code is kinda obsolete since I've published it. There are a lot of changes that I've implemented based on this code base. The reason why I couldn't share my current code is it is kinda "close-source" since it is being used in a production app and I'm not allowed to share it.
The main goal of this repo is to provide an idea or a solution (a base) on how to overcome the limitation that Apple has imposed on us when using hybrid development. Maybe I should just archive this repo since I'm not maintaining it at all since I've made this.
Thanks for the PR. Appreciate as always.

However, this code is kinda obsolete since I've published it. There are a lot of changes that I've implemented based on this code base. The reason why I couldn't share my current code is it is kinda "close-source" since it is being used in a production app and I'm not allowed to share it.

Could you please describe the changes you made to understand what problems you solved. Without code, but to understand what problems will need to be solved after installing the plugin. Thank you.

@seoplague The changes I've implemented are mostly bug fixes for Android to suit my current environment. The plugin is fairly stable for iOS though. One of them is toggling the speakers but this only applies to Android since certain versions of Android is broken. For iOS, it is being handled by another plugin.


A4T piece is missing on this page when we do server side target implementation

Issue in ./help/server-api/personalization-target.md
Please update with A4T content in server side implementation or provide reference link for A4T with edge API.
A4T piece is missing on this page when we do server side target implementation.

Thank you for submitting this issue. We will review the documentation and make the necessary updates as quickly as possible. Tracking internally in PLAT-181491.


Autolink on URLs without protocol should add // prefix to href

This is how it works now:

Related info:
https://stackoverflow.com/questions/43803778/href-without-https-prefix

Encountered in 0.2.0.pre-4

Should be fixed in master and kotlin-js-clean branches, 0.2.0-pre-6 version is published.


Cant not connect J-Link debug probe via USB

Hi I am try to developing embedded application for ARM Cortex microcontrollers in Ubuntu on Windows.
I use J-Link command tool to access J-Link debug probe to flash the image to the connected hardware.
When I try to run JLinkExe in Ubuntu on Windows, It's pirnt "Connecting to J-Link via USB...FAILED: Cannot connect to J-Link via USB."

But in Windows the connect is OK
My OS version is : Windows 10 Pro 1709

Not only does this fail on his hardware, it fails on ANY hardware. I've tried to use multiple devices through the WSL system, and none of them show up.
I've tried a USB printer, a Logitech camera, a Movidius NCS, a phone in adb mode, and an Xbox controller.
I also get errors when running several programs saying: ERROR: Could not get I/O privileges (Function not implemented).

+1
I come from a seamless OSX based embedded development environment. JLink, Eclipse, gnu arm, makefiles.
I am struggling to achieve this with WSL/Windows

Does anyone found the solution ?

Duping #2185 for lack of repro.

I am having the same problem.  If you need any proof of a repro to re-open / not re-close this, please let me know. IoT dev is impossible on WSL without it.


add Patterns anmol20goyal

What does the program do ?
made the program generalized for any number of rows....
In what programming language it is written?
C language

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


index signature used in generic class

Can the index signature be used with generic, like the following:
class Map<K, T> {
    private map: {[index: K]: T};
}

here the compiler will inform "An index signature parameter type must be 'string' or 'number'"

Indexes can only be for string or number. This models the JS indexing semantics, which is basically converting the key to a string before lookup. Consider using ES6 maps for indexing with arbitrary objects.

can K be constrained to number | string.
besides, if the above grammar be supported, the application layer can take care of the constraint of K, and only instance Map with K be string | number.
For now, we can only use ES5.

It is worth noting that JavaScrip array indexing actually converts number to string before performing the lookup.

That is why in TS the numeric indexer target needs to be a subtype of the string indexer if both exist.

To make this usage more sensible, I take an enhanced example.
class SortedMap<K, T> { // where K only support number | string
    private map: {[index: K]: T};
    private array: T[];
}

It would make sense if this were valid:
class SortedMap<K extends number | string, T> {
  map: { [key: K]: T };
}

but it doesn't actually provide anything since you can index into anything  with either a string or number

@aluanhaddad Yes, if it's valid, then my problem is solved.

@fwang2002 unfortunately it's not valid, but it's not as useful as one might think it would be because you could still index with either type. Numeric indeces are string indeces.

see related reply in https://github.com/Microsoft/TypeScript/issues/6641#issuecomment-175727391


Add ServiceMonitor support for openshift-controller-manager

This commit adds ServiceMonitor support to the openshift-controller-manager
component, using the same label rules as OCP. It also refactors the existing
ServiceMonitor code so that they all share a single client certificate bound to
the system:monitoring role in the guest cluster. This was done to prevent
unnecessary secret and certificate sprawl.
Checklist

[x] Subject and description added to both, commit and PR.

nice!
This looks better
/lgtm


Coding standards and workflow testing

The pytest test that has been implemented in the testing branch includes two flake8 tests that are now included in the workflow. This is done before of the python -m pytest call, which uses the two basic tests for atmosphere and coupled runs. The workflow is executed to every new commit and on every new pull request on the main
The first one of the flake8 call produces errors and makes the workflow to fail. It actually checks for undefined variables and syntax errors (and it made me spot one undefined vars!)
flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics

The second produce a full report under the form of a warning. Line length is set according to Github standard.
flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics

It would be important to run those tests BEFORE doing a pull request or a commit on the main
A very basic way to fix the most of the minor issue that arise from coding is running autopep8
autopep8 --in-place --max-line-length=127 --recursive .

The call of this three commands should be run always before merging a pull request.

Moved to wiki, closing this


change search input type from "text" to "search"

modern browsers add an X icon to quickly clear the value of a search type input when it contains a value.
if they aren't using a modern browser it falls back to a standard text type anyways.
this makes users happy.

Released in v1.13.12!


Add dry run mode

Similar to make -n, it would be nice to have a 'dry run' mode where Bunny does not actually execute anything but just prints statements it would execute.
My use case is a quick way to syntax-check my CWL and sanity-check the command sequence before actually executing on it.
I suppose with memoization this feature will become more important, because there a faulty run can mess up my intermediary results. The earlier I can catch such errors the better.
Besides make I have worked with different workflow engines in the past where dry runs were possible, so I immediately started missing this feature with Bunny.

It's implemented on a tool level in the cottontail editor, where you can preview generated command with provided inputs, but I guess could also be added to bunny relatively easily. On a workflow level it's a bit tricky to implement, because embedded expressions might fail when provided with dummy inputs, and all intermediary tools would get some sort of mocked inputs. If you are indeed asking for a dry run of an entire workflow, One way it could be done if user also prepares a cache directory with assumed results of steps, but it sounds like a lot of upfront work for user to prepare, so I'm not sure of it's utility.


List and download subfolders and files in a publicly shared directory

Hi,
I have a publicly shared link accessing which requires no authentication. I want to list all the contents in this directory and its sub-directories and download the files one by one. How to do this using onedrive-sdk-python? I am a newbie in this. Please help.
Link: https://indianinstituteofscience-my.sharepoint.com/:f:/g/personal/alankardutta_iisc_ac_in/EhdL9SYY45FOq7zjrWGD0NQBcy3pn6oTP2B9pGhxPwLnkQ?e=E956ug

@dutta-alankar
do you know how to do that?

No! I couldn't figure this out. I generated individual links for every item and appended ?download=1 at the end of the links.

Thank you for reaching out and for your patience. This SDK is being officially deprecated. See #209 for more information


JSON annotations for custom object detection using YOLOv2

Currently, AFAIK, the YOLOv2 model from IMAGEAI supports only .xml annotations for training models.
Do you @OlafenwaMoses think, it would be a good idea to add support for JSON annotations?
Thanks :)

It would make much sense bc you would have to standardize the JSON file so it could be read so you should have to rewrite the JSON file anyway bc there are so many different options it's like choosing a color for example orange it is impossible to what know orange you want it is the same with the JSON files all are different. And like I said you will have to rewrite your JSON any way
So if you need help converting your JSON to XML files just send me your JSON file and I will write a script for you that converts it :)


[flutter_test]scrollUntilVisible has different results if ListTile's onTap is null or not

Steps to reproduce

Paste sample code to tests/xxx_test.dart in Flutter project
Execute test by flutter test --plain-name 'scrollUntilVisible'

Expected results
The test passes, whether or not the ListTile's onTap attribute is null.
Actual results
The test will fail if ListTile's onTap attribute is not null.
Code sample
Code sample
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';

// flutter test --plain-name 'scrollUntilVisible'
void main() {
  group("scrollUntilVisible", () {
    Future<void> pumpListViewAndScrollToEndContent(
        WidgetTester tester, bool hasOnTap) async {
      int itemCount = 30;
      final controller = ScrollController();
      await tester.pumpWidget(MaterialApp(
          home: Scaffold(
        body: ListView.builder(
          controller: controller,
          itemBuilder: (context, index) {
            if (index <= itemCount) {
              return ListTile(
                onTap: hasOnTap
                    ? () {
                        //debugPrint("tapped");
                      }
                    : null,
                title: Text("$index"),
              );
            }
            return null;
          },
        ),
      )));

      // controller.addListener(() {
      //   debugPrint(
      //       "${controller.position.pixels}, ${controller.position.maxScrollExtent}");
      // });

      await tester.scrollUntilVisible(
        find.text("${itemCount - 1}"),
        20,
        maxScrolls: 2000,
        duration: const Duration(milliseconds: 50),
        scrollable: find.byType(Scrollable),
      );
    }

    testWidgets("This results success", (tester) async {
      // ListTile has "onTap" as null
      await pumpListViewAndScrollToEndContent(tester, false);
    });

    testWidgets("This results failed", (tester) async {
      // ListTile has "onTap" as not null
      await pumpListViewAndScrollToEndContent(tester, true);
    });
  });
}

Screenshots or Video
No response
Logs
Logs
% flutter test --plain-name 'scrollUntilVisible'
00:06 +1: /xxx/xxx.dart: scrollUntilVisible This results failed
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following StateError was thrown running a test:
Bad state: No element

When the exception was thrown, this was the stack:
#0      Iterable.single (dart:core/iterable.dart:674:25)
#1      WidgetController.element (package:flutter_test/src/controller.dart:448:30)
#2      WidgetController.dragUntilVisible.<anonymous closure> (package:flutter_test/src/controller.dart:1709:38)
<asynchronous suspension>
#3      TestAsyncUtils.guard.<anonymous closure> (package:flutter_test/src/test_async_utils.dart:117:7)
<asynchronous suspension>
#4      WidgetController.scrollUntilVisible.<anonymous closure> (package:flutter_test/src/controller.dart:1675:7)
<asynchronous suspension>
#5      TestAsyncUtils.guard.<anonymous closure> (package:flutter_test/src/test_async_utils.dart:117:7)
<asynchronous suspension>
#6      main.<anonymous closure>.pumpListViewAndScrollToEndContent (/xxx/xxx_test.dart:36:7)
<asynchronous suspension>
#7      main.<anonymous closure>.<anonymous closure> (/xxx/xxx_test.dart:52:7)
<asynchronous suspension>
#8      testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:168:15)
<asynchronous suspension>
#9      TestWidgetsFlutterBinding._runTestBody (package:flutter_test/src/binding.dart:1013:5)
<asynchronous suspension>
<asynchronous suspension>
(elided one frame from package:stack_trace)

Flutter Doctor output
I have not installed the Android environment, but it is not related to the test.
% flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.16.9, on macOS 14.1.1 23B81 darwin-arm64, locale ja-JP)
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
[✓] Chrome - develop for the web
[!] Android Studio (not installed)
[✓] VS Code (version 1.86.0)
[✓] Connected device (4 available)
[✓] Network resources

! Doctor found issues in 2 categories.

Thanks for the report @megur0.
I can reproduce this on the latest stable and master channels.
Logs

══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following StateError was thrown running a test:
Bad state: No element

When the exception was thrown, this was the stack:
#0      Iterable.single (dart:core/iterable.dart:674:25)
#1      WidgetController.element (package:flutter_test/src/controller.dart:863:30)
#2      WidgetController.dragUntilVisible.<anonymous closure> (package:flutter_test/src/controller.dart:2222:38)
<asynchronous suspension>
#3      TestAsyncUtils.guard.<anonymous closure> (package:flutter_test/src/test_async_utils.dart:117:7)
<asynchronous suspension>
#4      WidgetController.scrollUntilVisible.<anonymous closure> (package:flutter_test/src/controller.dart:2188:7)
<asynchronous suspension>
#5      TestAsyncUtils.guard.<anonymous closure> (package:flutter_test/src/test_async_utils.dart:117:7)
<asynchronous suspension>
#6      main.<anonymous closure>.pumpListViewAndScrollToEndContent (file:///Users/damilolaalimi/development/master/test/widget_test.dart:36:7)
<asynchronous suspension>
#7      main.<anonymous closure>.<anonymous closure> (file:///Users/damilolaalimi/development/master/test/widget_test.dart:52:7)
<asynchronous suspension>
#8      testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:183:15)
<asynchronous suspension>
#9      TestWidgetsFlutterBinding._runTestBody (package:flutter_test/src/binding.dart:1019:5)
<asynchronous suspension>
<asynchronous suspension>
(elided one frame from package:stack_trace)

The test description was:
  This results failed
════════════════════════════════════════════════════════════════════════════════════════════════════
00:03 +1 -1: scrollUntilVisible This results failed [E]
  Test failed. See exception logs above.
  The test description was: This results failed

To run this test again: /Users/damilolaalimi/fvm/versions/master/bin/cache/dart-sdk/bin/dart test /Users/damilolaalimi/development/master/test/widget_test.dart -p vm --plain-name 'scrollUntilVisible This results failed'
00:03 +1 -1: Some tests failed.

This might be similar or related to https://github.com/flutter/flutter/issues/54665.
stable, master flutter doctor -v

[!] Flutter (Channel stable, 3.19.1, on macOS 14.2.1 23C71 darwin-arm64, locale
    en-NG)
    • Flutter version 3.19.1 on channel stable at
      /Users/damilolaalimi/sdks/flutter
    ! Warning: `dart` on your path resolves to
      /opt/homebrew/Cellar/dart/3.1.5/libexec/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/damilolaalimi/sdks/flutter.
      Consider adding /Users/damilolaalimi/sdks/flutter/bin to the front of your
      path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision abb292a07e (2 days ago), 2024-02-20 14:35:05 -0800
    • Engine revision 04817c99c9
    • Dart version 3.3.0
    • DevTools version 2.31.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

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

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

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

[✓] Android Studio (version 2022.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.6+0-17.0.6b802.4-9586694)

[!] Android Studio (version unknown)
    • Android Studio at /Users/damilolaalimi/Downloads/Android Studio
      Preview.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
    ✗ Unable to determine Android Studio version.
    • Java version OpenJDK Runtime Environment (build
      17.0.7+0-17.0.7b1000.6-10550314)

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

[✓] VS Code (version 1.83.1)
    • VS Code at /Users/damilolaalimi/Downloads/Visual Studio Code.app/Contents
    • Flutter extension version 3.78.0

[✓] Connected device (3 available)
    • Damilola’s iPhone (mobile) • 00008110-001964480AE1801E • ios            •
      iOS 17.1.1 21B91
    • macOS (desktop)            • macos                     • darwin-arm64   •
      macOS 14.2.1 23C71 darwin-arm64
    • Chrome (web)               • chrome                    • web-javascript •
      Google Chrome 121.0.6167.184

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

! Doctor found issues in 2 categories.

[!] Flutter (Channel master, 3.20.0-11.0.pre.80, on macOS 14.2.1 23C71 darwin-arm64, locale en-NG)
    • Flutter version 3.20.0-11.0.pre.80 on channel master at /Users/damilolaalimi/fvm/versions/master
    ! Warning: `flutter` on your path resolves to /Users/damilolaalimi/sdks/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/damilolaalimi/fvm/versions/master. Consider adding /Users/damilolaalimi/fvm/versions/master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /opt/homebrew/Cellar/dart/3.1.5/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/damilolaalimi/fvm/versions/master. Consider adding /Users/damilolaalimi/fvm/versions/master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision efee280cfa (8 hours ago), 2024-02-21 21:44:25 -0500
    • Engine revision 7eeb697687
    • Dart version 3.4.0 (build 3.4.0-163.0.dev)
    • DevTools version 2.33.0-dev.6
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

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

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

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

[✓] Android Studio (version 2022.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.6+0-17.0.6b802.4-9586694)

[!] Android Studio (version unknown)
    • Android Studio at /Users/damilolaalimi/Downloads/Android Studio Preview.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
    ✗ Unable to determine Android Studio version.
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

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

[✓] VS Code (version 1.83.1)
    • VS Code at /Users/damilolaalimi/Downloads/Visual Studio Code.app/Contents
    • Flutter extension version 3.78.0

[✓] Connected device (4 available)
    • Damilola’s iPhone (mobile)      • 00008110-001964480AE1801E • ios            • iOS 17.1.1 21B91
    • macOS (desktop)                 • macos                     • darwin-arm64   • macOS 14.2.1 23C71 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad     • darwin         • macOS 14.2.1 23C71 darwin-arm64
    • Chrome (web)                    • chrome                    • web-javascript • Google Chrome 121.0.6167.184

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

! Doctor found issues in 2 categories.


Improve IPython console Options menu

The Options menu of the IPython console has grown a lot lately:

My idea is to shrink it a bit, like this:
New console
Specialized consoles > Pylab / Sympy / Cython
----
Restart kernel
Connect to an existing kernel
Remove all variables
----
Rename tab
Show env vars
Show sys.path contents
Show elapsed time

Notes:

Specialized consoles would be a submenu but only of the IPython console options menu. The main Consoles menu wouldn't have it.
The last two actions in the screenshot above will be added to all plugins after PR #8192.

@spyder-ide/core-developers, what do you think?

Good thinking; what you have so far is a major improvement. Would these changes also affect the context menu similarly?
A few comments:

Connect to an existing kernel should definitely be in the first group, under Specialized consoles, since it relates to opening a new Console tab (as does the first group) rather than modifying an existing one (as do the other actions in the second group).
Similarly, since Rename Tab modifies the current Console tab, rather than is a general action (like the others in its group), it should go in the second group,
What's the reason for including the Specialized consoles submenu in the context/options menu but not the main Consoles menu?

Also, a a detail note, I'd suggest naming it something like New IPython console/New specialized console for clarity and parallelism.

Generally I like this.

What's the reason for including the Specialized consoles submenu in the context/options menu but not the main Consoles menu?

Do we even need a main Console menu? If we do it need it might as well have more things in it.
I've always wondered why the stop command isn't in the menu and the remove variables is.
This might be out of scope but a restart kernel button next to the remove variables could be useful. I've been trapped in a live updating plot and the stop button wouldn't stop it but restart did trick. But it was hard to get focus long enough to click the drop down with a new figure popping up every second :-)

Do we even need a main Console menu?

Yeah, I've always wondered that, since it relates to a particular pane. A few core functions from each pane (run profiler, run static analysis, open project, etc) are present in the menus, but the Consoles pane is the only one that gets its own menu, which is just a curiously abbreviated version of the main Consoles menu. IMO since its dedicated to one and only one pane and is based directly off that pane's menu rather than taking up space in another, we should either just make it identical (ideally sharing the same codebase) to reduce maintenance burden and user confusion, or remove it entirely.

This might be out of scope but a restart kernel button next to the remove variables could be useful.

Maybe out of scope, but agreed—I almost never use Remove Variables but use Restart Kernel all the time.

Ok, so let's go with
New console
Specialized consoles > Pylab / Sympy / Cython
Connect to an existing kernel
----
Restart kernel
Remove all variables
Rename tab
----
Show env vars
Show sys.path contents
Show elapsed time

What's the reason for including the Specialized consoles submenu in the context/options menu but not the main Consoles menu?

Because the Consoles menu can be much taller than the Options one.

Also, a a detail note, I'd suggest naming it something like New IPython console/New specialized console for clarity and parallelism.

I think that's too detailed and it'd also make the menu too wide.

About your other comments:

I've always wondered why the stop command isn't in the menu and the remove variables is.

I thought it was enough with the stop button. Do you think we should add it? (I'm a bit -1 on it).

This might be out of scope but a restart kernel button next to the remove variables could be useful.

The thing the restart kernel action is blocking (i.e. it freezes the entire interface) so I wouldn't like people to start using it all the time. But if you feel this is important, please open a new issue about it.

I'm confused; that seems backward—you mentioned the Consoles menu wouldn't have it, while the option one would, yet its the Console menu that can be much taller as you say.

Yes, we don't need to create a submenu in the Consoles menu because it can be much taller.

How about New special console

Ok, no problem.

but IMO there should either be a clear rationale for why Remove all variables is in the options menu while the stop button isn't

There's no rationale. I just thought it was not necessary. So let's add it with this work.

@juanis2112, let's go with this for the Options menu:
New console (default settings)
New special console >
    New Pylab console (data plotting)
    New SymPy console (symbolic math)
    New Cython console (Python with C extensions)
Connect to an existing kernel
----
Restart kernel
Interrupt kernel (<- This action will trigger the same action as the stop button)
Remove all variables
Rename tab
----
Show env vars
Show sys.path contents
Show elapsed time

And for the Consoles menu on top, please organize it like this
New console (default settings)
New Pylab console (data plotting)
New SymPy console (symbolic math)
New Cython console (Python with C extensions)
Connect to an existing kernel
----
Restart kernel
Interrupt kernel
Remove all variables

I suggest placing Interrupt kernel above Restart kernel; IMO just seems more intuitive and natural to have interrupt above a complete restart but maybe that's just me.
Is there currently a clear distinction for what goes on the Consoles top-level menu vs. the Consoles pane options menu? If not, I'd consider putting commands that aren't specific to a particular Console sub-tab (e.g. the middle section) only on the Console pane options menu, while including global (first section) or quasi-global (third section) options on both; this also ensures the common sections are identical. Alternatively, if there isn't a clear distinction other than subjection personal perception, since the Consoles menu can be longer anyway I'd just make then identical to be consistent.

Yes, we don't need to create a submenu in the Consoles menu because it can be much taller.

Oh, I see—I interpreted your original comment to mean those options wouldn't be included at all.

There's no rationale. I just thought it was not necessary. So let's add it with this work.

Okay, sure, if you think so.


Avoid dtoh copy for dequantization of f16/f32

Currently, we execute a dtoh copy when dequantizing f16/f32 on CUDA when this is not necessary. We can just add a simple cast kernel to ensure that we keep the data on the device.
This PR only updates CUDA dequantization, Metal dequantization executes on the CPU. Generall, dequantization performance shouldn't matter too much, as we should avoid it in a hot loop.

Closing to avoid excessive stagnant PRs.


xarchiver: <IP_ADDRESS> -> <IP_ADDRESS>

Motivation for this change
Update package, can't reproduce #92630 - tried before and after update starting from dmenu/cli, choosing file and extracting. Using i3wm.
Things done
Update version, hash, tested  after install

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

Result of nixpkgs-review pr 122848 at 681f2c26 run on x86_64-linux 1

1 package built successfully:

xarchiver

2 suggestions:

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/tools/archivers/xarchiver/default.nix:27:5:
   |
27 |     license = lib.licenses.gpl2;
   |     ^

warning: build-tools-in-build-inputs
intltool is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/tools/archivers/xarchiver/default.nix:16:3:
   |
16 |   buildInputs = [ gtk3 intltool libxslt ];
   |   ^

Updated according to feedback, as far as I found out by comparing with other packages it should be gpl2Plus :)


Ammonite Repl does not support \u

val `a\u0060 = 1 is a valid Scala expression and can be compiled in Official Scala REPL:
Welcome to Scala 2.12.1 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_102).
Type in expressions for evaluation. Or try :help.

scala> val `a\u0060 = 1
a: Int = 1

However, Ammonite Repl does not support it:
Welcome to the Ammonite Repl 0.8.1
(Scala 2.12.1 Java 1.8.0_102)
@ val `a\u0060 = 1
SyntaxError: found "`a\\u0060 = 1", expected Binding ~ InfixPattern | InfixPattern | VarId at index 4
val `a\u0060 = 1
    ^

This is a limitation that is unlikely to ever go away, due to the way the parser works, unfortunately. Although I've tried to support every weird edge case of the Scala language, some things are just to weird and too edge for me to think it's worth supporting


Update config.toml

updating old docs to reference 1.14, updating minor version numbers, and dropping 1.9.

@lucperkins We'd love your input here.
For context: when we release a new version of the docs, we have to update the version selector in the previous four release branches. This requires four separate PRs to update config.toml in the respective release branches.
This PR (on Hugo v0.53) is failing. Release 1.12 docs (on Hugo v0.49) continue to display the deprecation warning correctly.
As near as @jimangel and I can tell, this PR may be failing due to changes introduced in #12079, specifically to syntax changes in the deprecation warning.
3:46:10 PM: ERROR 2019/03/25 22:46:10 "/opt/build/repo/content/ko/_index.html:7:1": failed to render shortcode "deprecationwarning": failed to process shortcode: "/opt/build/repo/layouts/shortcodes/deprecationwarning.html:6:16": execute of template failed: template: shortcodes/deprecationwarning.html:6:16: executing "shortcodes/deprecationwarning.html" at <.Param>: can't evaluate field Param in type *hugolib.ShortcodeWithPage
3:46:10 PM: ERROR 2019/03/25 22:46:10 "/opt/build/repo/content/ja/_index.html:7:1": failed to render shortcode "deprecationwarning": failed to process shortcode: "/opt/build/repo/layouts/shortcodes/deprecationwarning.html:6:16": execute of template failed: template: shortcodes/deprecationwarning.html:6:16: executing "shortcodes/deprecationwarning.html" at <.Param>: can't evaluate field Param in type *hugolib.ShortcodeWithPage
3:46:10 PM: ERROR 2019/03/25 22:46:10 "/opt/build/repo/content/fr/_index.html:7:1": failed to render shortcode "deprecationwarning": failed to process shortcode: "/opt/build/repo/layouts/shortcodes/deprecationwarning.html:6:16": execute of template failed: template: shortcodes/deprecationwarning.html:6:16: executing "shortcodes/deprecationwarning.html" at <.Param>: can't evaluate field Param in type *hugolib.ShortcodeWithPage
3:46:10 PM: ERROR 2019/03/25 22:46:10 "/opt/build/repo/content/it/_index.html:7:1": failed to render shortcode "deprecationwarning": failed to process shortcode: "/opt/build/repo/layouts/shortcodes/deprecationwarning.html:6:16": execute of template failed: template: shortcodes/deprecationwarning.html:6:16: executing "shortcodes/deprecationwarning.html" at <.Param>: can't evaluate field Param in type *hugolib.ShortcodeWithPage
3:46:10 PM: Total in 13696 ms
3:46:10 PM: Error: Error building site: "/opt/build/repo/content/en/_index.html:7:1": failed to render shortcode "deprecationwarning": failed to process shortcode: "/opt/build/repo/layouts/shortcodes/deprecationwarning.html:6:16": execute of template failed: template: shortcodes/deprecationwarning.html:6:16: executing "shortcodes/deprecationwarning.html" at <.Param>: can't evaluate field Param in type *hugolib.ShortcodeWithPage

/cc @seokho-son too as this could also be related to this PR: https://github.com/kubernetes/website/pull/12418
As the original CI tests would pass (since master isn't "deprecated") and fail on build as we sunset 1.13 docs (toggling to deprecated, which triggers the notice.html build).
I think we need to look very closely at what all is involved when https://github.com/seokho-son/website/blob/9a4e86dd5da30859bf9bc36d0975bd676c7b2251/layouts/shortcodes/deprecationwarning.html is generated.

we have to update the version selector in the previous four release branches. This requires four separate PRs to update config.toml in the respective release branches.

wow, never thought that is the process today, ouch

@zacharysarah @lucperkins @seokho-son  I think I see what is needed:
s/.Param/.Page.Param/ on line 6
Adding to this PR now...

@jimangel Thanks for your work here!
Unrelated to this PR, I have a nit with the wording of the deprecation warning itself. I'm noting it here for reference in a follow-up PR.

/lgtm
/approve


fix(utility): initialize the "_attrs_fields" in "init_subclass"

Pull Request Test Coverage Report for Build 852745056

2 of 3 (66.67%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 80.958%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tensorbay/utility/attr.py
2
3
66.67%

Totals

Change from base Build 850140227:
-0.02%

Covered Lines:
4243

Relevant Lines:
5241

💛  - Coveralls


Applications功能报错 EXECUTE_PYTHON_ERROR

手机:iPhone7
系统版本:iOS13.4.1
用Checkra1n 越狱
APPLICATIONS报错：
EXECUTE_PYTHON_ERROR -> stderr:-> Failed to enumerate applications: this feature requires an iOS Developer Disk Image to be mounted; run Xcode briefly or use ideviceimagemounter to mount one manually  -> stdout: -> whenExec:'/Users/lee/Library/Application Support/Code/User/globalStorage/lakr233.wikiqaqiosre/lkbins/bins/py3/lsapps.py' 0ce588e7558891fe0605b446e73d0ab2c8feb0d1  ==> Install dependency may solve the problem.

Failed to enumerate applications: this feature requires an iOS Developer Disk Image to be mounted; run Xcode briefly or use ideviceimagemounter to mount one manually
可能是 手机没有信任 或者手机端的环境存在问题
一般来说 用Xcode跑个App就能解决问题 或者打开终端输入 ideviceimagemounter
如果问题依然存在 请考虑更新一下libimobiledevice
brew uninstall --ignore-dependencies libimobiledevice usbmuxd
brew install -v --HEAD --build-from-source usbmuxd libimobiledevice

感谢大佬，最新的libimobiledevice是1.2.1么，用1.2.0可不可以，因为我1.2.1的编译报错，没编译出来
Error: libimobiledevice HEAD-80eec8b did not build Logs:      /Users/lee/Library/Logs/Homebrew/libimobiledevice/02.configure      /Users/lee/Library/Logs/Homebrew/libimobiledevice/00.options.out      /Users/lee/Library/Logs/Homebrew/libimobiledevice/02.configure.cc      /Users/lee/Library/Logs/Homebrew/libimobiledevice/03.make.cc      /Users/lee/Library/Logs/Homebrew/libimobiledevice/config.log      /Users/lee/Library/Logs/Homebrew/libimobiledevice/03.make      /Users/lee/Library/Logs/Homebrew/libimobiledevice/01.autogen.sh      /Users/lee/Library/Logs/Homebrew/libimobiledevice/01.autogen.sh.cc READ THIS: https://docs.brew.sh/Troubleshooting Please create pull requests instead of asking for help on Homebrew's GitHub, Discourse, Twitter or IRC

03.make.txt

homebrew不要开加速用官方地址去build试试？
既然问题出现了就不能懒人咯

感谢！


refactor: make Functor, Apply, FunctorComposition and ApplicativeComposition data-last

So following https://github.com/gcanti/fp-ts/issues/925#issuecomment-523546371 this PR is a POC of a data-last Functor, Apply, FunctorComposition and ApplicativeComposition for seamless usage with pipe.
Monadic data structures as well as their monad transformers now implement data-last typeclasses.
Previously (in the time of<EMAIL_ADDRESS>we didn't have pipe and TS couldn't infer the type of curried data-last argument. Now pipe allows to start the chain from that argument so that the types are correctly inferred.
As a side effect this PR is to show that pipeable can be made redundant when (if) all typeclasses migrate to data-last

@gcanti Do you have any thoughts on this? This PR is a breaking change but it ultimately fixes some of the existing annoying issues with fp-ts:

API inconsistency:  pipe is an idiomatic way to use fp-ts however its abstract core - the typeclasses - have signatures not suitable for this idiomatic way out of the box and require some messy (redundant IMO) steps like calling pipeable, destructuring, reexporting and so on. When they actually could be used as is.
transformers: if I need a "pipeable" version (an idiomatic version actually) of some transformer I need to register its type as a separate monad on the HKT dictionary. This doesn't  make much sense because the type is already "bundled" in the transformer instance (for example the result of getOptionM already contains info about Option and passed M.
pipeable module itself is a mess with no sensible profit - it just fixes data-first typeclasses when they could be data-last by design completely eliminating the need for this module.

PS. This reminds me https://github.com/gcanti/fp-ts/pull/202 actually :)

This PR is a breaking change

@raveclassic Indeed, sorry but I'm afraid I can't accept this PR.

Thanks for such an informative answer on the main topic of this POC.

@raveclassic just adding my 2 cents here: the proposed API change has some advantages for sure (uniformity of the API and import/exports mainly) but, if I understand it correctly, at the cost of:

dropping completely the support for e.g. either.map(e, fn) (which is something I find myself using many times when only a few operations are needed) (and as you already know this can't be achieved in a data-last fashion because of how TS inference works)
being a breaking change: after all the effort and discussion spent on drafting and then releasing v2, and people still in the middle of upgrades on their projects, this library just can't have another major breaking change right now

@giogonzo This is just a POC for a discussion. I'm sorry for not being more clear with that in the description.
Thanks a lot for the discussion, regarding your points:

yep, but that's the minimisation of API surface. All the time I find myself explaining new people coming to our projects which way exactly to use in which situation.  I'd would be better to stick to one idiomatic way once and for all - pipe(e, map(f)), TS even forces you to stick to it being unable to infer the type with direct application.
yeah, that's sad, really sad. I'm the one of those in the middle of upgrades. But that doesn't mean I suggest breaking the whole library once again right now. I'm just searching for a proper solution to the problems my teams face every day. That could be a separate package, or a subpackage, IDK

It would be better to stick to one idiomatic way once and for all

this could be achieved in steps and:

push on pipe in terms of documentation and examples for the time being
reevaluate in some time how people are using pipe vs data-first methods and, if it is the case, re-propose to drop support for data-first, passing through minor versions & deprecations. But again, this just can't happen right away.

That could be a separate package, or a subpackage, IDK

Do you think I'd be possible to re-export fp-ts from e.g. an internal library of yours and "hide" data-first methods? That could lead to some good data points to contribute to this discussion

this could be achieved in steps

Agree. Long time ago there were Fantasy<name> typeclasses in fp-ts which followed fantasy-land however they were not usable with static approach and therefore were dropped. One of possible solutions would be to add static-land interfaces and update data structures with proper instances for them. This will however massively bloat API.

re-export fp-ts

This will end in rewriting the major part of fp-ts including typeclasses and instances as well (some of implementations could be picked from pipeable output, but only non-constrained ones). That's why I opened this PR for discussion - maybe there's a better way that I don't see. Creating a maintained wrapper around fp-ts or even a replacement which follows static-land as close as possible could be a way however we'd go that way in the worst case.


Request for AmberChat and AmberSafe Implementation Details

Truly grateful for your exceptional work in the open source community. Could you possibly share the implementation details of AmberChat and AmberSafe?"

sorry for not following the github issues closely. yes we shared a bit on how we did it here:
AmberChat: https://huggingface.co/LLM360/AmberChat
AmberSafe: https://huggingface.co/LLM360/AmberSafe


Training on customer dataset

Thanks for the excellent work.
In the paper, you said the RGB and T detectors must be trained with the same annoations.
So the two detectors are trained using paired dataset.
How to fusion the detectors trained with different datasets?
Because we only have own-collected thermal images without RGB ones.
For paired RGB and T cameras, is there any restrictions for FOV overlapping or resolution?
Thanks.

Maybe you can split your own dataset to "train" and "validation" datasets and fine-tune detectors on your own dataset?
For the question about paired RGB and T cameras, I am sorry that they didn't give many details on the data they collect. For more information about KAIST and FLIR, please check KAIST paper and FLIR dataset website, thanks


Storage Accounts created before Sept 24th, 2018

"Azure AD DS authentication for SMB access is available only for storage accounts created after September 24, 2018."
Any options, like a migration or magic behind the scenes, that can be done without having to create another instance and have to manually move things to the new storage account?

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

ID: d254d903-bd6c-48ce-967d-0a96f2ca9431
Version Independent ID: 2980ab92-7e11-12f7-fa51-86d58a311905
Content: Overview - Azure AD Domain Services authorization - Azure Files
Content Source: articles/storage/files/storage-files-active-directory-overview.md
Service: storage
GitHub Login: @roygara
Microsoft Alias: rogarana

@dmarlow Hi Dariel, I'd recommend filing a support ticket with specific request: https://azure.microsoft.com/en-us/support/create-ticket/
You'd receive an accurate response whether it is possible or not.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Upgrading to .NET core 2.1 or higher makes the vbdbg to fail on attaching

Prerequisites:

App running on docker contained Service fabric cluster on Ubuntu 16.04
Previously it worked to debug .net 2.0 apps via piperProgram: docker
Upgrading to a .net core version higher than 2.2 makes the debugger to fail to attach.

 {
            "name": ".NET Core Docker Attach",
            "type": "coreclr",
            "request": "attach",
            "processId": "${command:pickRemoteProcess}",
            "pipeTransport": {
                "pipeProgram": "docker",
                "pipeArgs": [ "exec",  "-u", "sfappsuser", "-i", "dhcloud_sfcluster_1" ],
                "debuggerPath": "/vsdbg/vsdbg",
                "pipeCwd": "${workspaceRoot}",
                "quoteArgs": false
            },
            "logging": {
                "engineLogging": true
            },
            "requireExactSource": false
        },

Logs
{"seq":9,"type":"response","request_seq":6,"success":false,"command":"configurationDone","message":"Failed to attach to process: Unknown Error: 0x80131c08"}

This is a problem with the .NET Runtime's IPC mechanism. It is failing with CORDBG_E_TIMEOUT.
Are you by chance using a private temp directory for the app you are trying to debug? See https://github.com/OmniSharp/omnisharp-vscode/issues/3277

Hi Gregg,
We are not using a private directory, as far as I know, our project is using Service Fabric and I am not completely aware of how it handles the processes. We tried what you suggest on #3277 but we could not find anything.
This only happens with versions higher than 2.1. Otherwise, the debugger works fine.
Do you have any other clues?
In order to debug, create a SF cluster on Linux, and try to attach to a 3.1 .NET core.

I have been having the same problem. I am trying to attach to Service Fabric Application.
OS: Ubuntu 18.04.4 LTS
OmniSharp: 1.22.1
DotNet: 3.1.301
SF: 7.1
While trying to attach to service from VS code, it is giving an error: 0x80131c08
I am running VS Code as a elevated privileges under sudo and it is using its own private user data directory.
Output from vsdbg-ui
Waiting for communication on port 4711...
>> accepted connection from client
-> (C) {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"coreclr","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en-us","supportsProgressReporting":true},"type":"request","seq":1}
<- (R) {"seq":0,"type":"response","request_seq":1,"success":true,"command":"initialize","message":"","body":{"supportsConfigurationDoneRequest":true,"supportsFunctionBreakpoints":false,"supportsConditionalBreakpoints":true,"supportsHitConditionalBreakpoints":true,"supportsEvaluateForHovers":true,"exceptionBreakpointFilters":[{"filter":"all","label":"All Exceptions","default":false},{"filter":"user-unhandled","label":"User-Unhandled Exceptions","default":true}],"supportsSetVariable":true,"supportsGotoTargetsRequest":true,"supportsModulesRequest":true,"additionalModuleColumns":[],"supportedChecksumAlgorithms":["MD5","SHA1","SHA256"],"supportsExceptionOptions":true,"supportsValueFormattingOptions":true,"supportsExceptionInfoRequest":true,"supportTerminateDebuggee":true,"supportsSetExpression":true,"supportsReadMemoryRequest":true,"supportsExceptionConditions":true,"supportsLoadSymbolsRequest":true,"supportsModuleSymbolSearchLog":true,"supportsDebuggerProperties":true,"supportsSetSymbolOptions":true}}
-> (C) {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"coreclr","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en-us","supportsProgressReporting":true},"type":"request","seq":1}
-> (C) {"command":"attach","arguments":{"name":".NET Core Attach","type":"coreclr","request":"attach","processId":"6352","logging":{"engineLogging":false},"debugServer":4711,"__sessionId":"107ce00b-afc0-40f9-bbc4-eb86c7786acb"},"type":"request","seq":2}
<- (E) {"seq":3,"type":"event","event":"output","body":{"category":"console","output":"-------------------------------------------------------------------\nYou may only use the Microsoft .NET Core Debugger (vsdbg) with\nVisual Studio Code, Visual Studio or Visual Studio for Mac software\nto help you develop and test your applications.\n-------------------------------------------------------------------\n"}}
<- (R) {"seq":4,"type":"response","request_seq":2,"success":true,"command":"attach"}
<- (E) {"seq":5,"type":"event","event":"initialized","body":{}}
-> (C) {"command":"setExceptionBreakpoints","arguments":{"filters":["user-unhandled"]},"type":"request","seq":3}
<- (R) {"seq":6,"type":"response","request_seq":3,"success":true,"command":"setExceptionBreakpoints"}
-> (C) {"command":"configurationDone","type":"request","seq":4}
<- (E) {"seq":7,"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/vsdbg/AttachFailed","data":{"VS.Diagnostics.Debugger.vsdbg.ErrorCode":-2146231288,"VS.Diagnostics.Debugger.vsdbg.Distribution.Name":"ubuntu","VS.Diagnostics.Debugger.vsdbg.Distribution.Version":"18.04","VS.Diagnostics.Debugger.vsdbg.OSFamily":"Linux","VS.Diagnostics.Debugger.vsdbg.Version":"16.6.20415.1 commit:0184bb70e1ed40656c0dfa53125805036207007b"}}}
<- (R) {"seq":8,"type":"response","request_seq":4,"success":false,"command":"configurationDone","message":"Failed to attach to process: Unknown Error: 0x80131c08"}
-> (C) {"command":"disconnect","arguments":{"restart":false},"type":"request","seq":5}
-> (C) {"command":"threads","type":"request","seq":6}
<- (E) {"seq":9,"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/vsdbg/DebugCompleted","data":{"VS.Diagnostics.Debugger.vsdbg.AdapterId":"coreclr","VS.Diagnostics.Debugger.vsdbg.DebugCompleted.BreakCounter":0,"VS.Diagnostics.Debugger.vsdbg.Distribution.Name":"ubuntu","VS.Diagnostics.Debugger.vsdbg.Distribution.Version":"18.04","VS.Diagnostics.Debugger.vsdbg.OSFamily":"Linux","VS.Diagnostics.Debugger.vsdbg.Version":"16.6.20415.1 commit:0184bb70e1ed40656c0dfa53125805036207007b"}}}
<- (R) {"seq":10,"type":"response","request_seq":5,"success":true,"command":"disconnect"}
>> client connection closed

For me all of a sudden a couple of weeks ago it started working. Have you tried updating vsdbg to the latest version?


Lags

More lags in conversion name->uuid for offline users
Please add UUID caching for offline of users who left from the server
After all for online of players, UUID are cached and UUID shouldn't load anew
PEX 1.22.10

All UUID resolution is handled in the server. Bug Spigot/Mojang folks to improve performance.


parse_openshift_release_url disable cache - 327

[Auto generated]
Number: [#327]

openshift-python-utilities(ngPfu)[PR 327]: Closing issue for PR: parse_openshift_release_url disable cache.
PR was closed.


Am masthead add on

Makes modal available in masthead so that clickable links can be used in masthead.

👍


Broken?

Just getting errors and the fn never runs that it makes.  Below are logs for the plugin-warmup function.
Looks like this is the error:
{
  "errorMessage": "callback called with Error argument, but there was a problem while retrieving one or more of its message, name, and stack"
}

20:47:43
START RequestId: 1113ea0b-ce60-11e8-9706-b39018c2c283 Version: $LATEST

20:47:44
module initialization error: TypeError

20:47:45
END RequestId: 1113ea0b-ce60-11e8-9706-b39018c2c283

20:47:45
REPORT RequestId: 1113ea0b-ce60-11e8-9706-b39018c2c283	Duration: 1269.59 ms	Billed Duration: 1300 ms Memory Size: 128 MB	Max Memory Used: 33 MB

20:47:45
module initialization error TypeError

20:48:38
START RequestId: 1113ea0b-ce60-11e8-9706-b39018c2c283 Version: $LATEST

20:48:39
module initialization error: TypeError

20:48:39
END RequestId: 1113ea0b-ce60-11e8-9706-b39018c2c283

20:48:39
REPORT RequestId: 1113ea0b-ce60-11e8-9706-b39018c2c283	Duration: 1162.79 ms	Billed Duration: 1200 ms Memory Size: 128 MB	Max Memory Used: 31 MB

20:48:39
module initialization error TypeError

20:50:42
START RequestId: 1113ea0b-ce60-11e8-9706-b39018c2c283 Version: $LATEST

20:50:43
module initialization error: TypeError

20:50:43
END RequestId: 1113ea0b-ce60-11e8-9706-b39018c2c283

20:50:43
REPORT RequestId: 1113ea0b-ce60-11e8-9706-b39018c2c283	Duration: 1355.07 ms	Billed Duration: 1400 ms Memory Size: 128 MB	Max Memory Used: 31 MB

20:50:43
module initialization error TypeError

20:52:43
START RequestId: c3deca1d-ce60-11e8-ac11-0334b25c9585 Version: $LATEST

20:52:44
module initialization error: TypeError

20:52:44
END RequestId: c3deca1d-ce60-11e8-ac11-0334b25c9585

20:52:44
REPORT RequestId: c3deca1d-ce60-11e8-ac11-0334b25c9585	Duration: 1541.81 ms	Billed Duration: 1600 ms Memory Size: 128 MB	Max Memory Used: 31 MB

20:52:44
module initialization error TypeError

20:53:47
START RequestId: c3deca1d-ce60-11e8-ac11-0334b25c9585 Version: $LATEST

20:53:48
module initialization error: TypeError

20:53:48
END RequestId: c3deca1d-ce60-11e8-ac11-0334b25c9585

20:53:48
REPORT RequestId: c3deca1d-ce60-11e8-ac11-0334b25c9585	Duration: 1591.97 ms	Billed Duration: 1600 ms Memory Size: 128 MB	Max Memory Used: 32 MB

20:53:48
module initialization error TypeError

20:55:48
START RequestId: c3deca1d-ce60-11e8-ac11-0334b25c9585 Version: $LATEST

20:55:49
module initialization error: TypeError

20:55:50
END RequestId: c3deca1d-ce60-11e8-ac11-0334b25c9585

20:55:50
REPORT RequestId: c3deca1d-ce60-11e8-ac11-0334b25c9585	Duration: 1485.05 ms	Billed Duration: 1500 ms Memory Size: 128 MB	Max Memory Used: 31 MB

20:55:50
module initialization error TypeError

20:57:43
START RequestId: 76eef019-ce61-11e8-840b-81109a057e28 Version: $LATEST

20:57:44
module initialization error: TypeError

20:57:45
END RequestId: 76eef019-ce61-11e8-840b-81109a057e28```

Based on #68 it would appear source map support breaks this module for some reason.  When I remove that it works.

Upon tons of investigation I have discovered what is happening here.  This module is, essentially incompatible with serverless-webpack.  This is due to the fact that webpack sees your es5 code and ignores it completely when bundling, therefore it exports nothing.
I manually fixed the code that webpack builds but it is not really a solution since every deploy would break it again.
By looking at the packaged code, I noticed this:
/*!**************************!*\
  !*** ./_warmup/index.js ***!
  \**************************/
/*! no exports provided */```

Then inside of the initialization code I saw the untouched module.exports.warmUp call.  I had to change that to this:

```javascript
__webpack_exports__["warmUp"] = (async (event, context, callback) => {
  console.log("Warm Up Start");
  const invokes = await Promise.all(functionNames.map(async functionName => {
    const params = {

PR with fix: https://github.com/FidelLimited/serverless-plugin-warmup/pull/74


Node not defined

As in: https://developer.mozilla.org/en-US/docs/Web/API/Node
I found this while running AngularJS inside benv. At (this line)[https://github.com/angular/angular.js/blob/1537651c8c5f26f1c75576b881e04a3cf818447f/src/jqLite.js#L259], an error is thrown due to Node not being defined.
This is with version 2.1.0 of benv. Running tests on older versions of node so I can't upgrade just yet.

It looks like this is fixed with later versions of jsdom that require Node 4+ so I'll work around this for now.


Colliding with objects and walls

I haven't used your plugin yet, but I wanted to know if there is a collision between the camera and obstacles? walls and other objects?

Yes, there is.
We use SpringArm for that then it is possible to set the collision mask for the objects it should collide with.


Move to vscode-languageclient 8.0.2

Signed-off-by: Jessica He<EMAIL_ADDRESS>

There is a compilation error in one of the test files (you can see it if you run npm test).

(sorry, didn't realize you already had a PR for this)

(sorry, didn't realize you already had a PR for this)

No that's my bad, I should have created an issue for it first or included it in my stand up

Closes #145


Implemented pre-save validation in DBPydanticMixin

Implemented validation method called before operations of save to database:

create (with save)
update
save
bulk create
bulk update

Codecov Report

Merging #36 (48ceb1e) into master (6fe87c6) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #36   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            6         6
=========================================
  Hits             6         6

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 6fe87c6...48ceb1e. Read the comment docs.

Codecov Report

Merging #36 (48ceb1e) into master (6fe87c6) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #36   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            6         6
=========================================
  Hits             6         6

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 6fe87c6...48ceb1e. Read the comment docs.


DOC: add warning about adjusting .PREC

closes #1115

Codecov Report

Merging #1132 into master will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1132      +/-   ##
==========================================
+ Coverage   89.27%   89.33%   +0.05%
==========================================
  Files          51       51
  Lines        8553     8553
==========================================
+ Hits         7636     7641       +5
+ Misses        917      912       -5

Impacted Files
Coverage Δ

bluesky/log.py
75% <0%> (+6.57%)
:arrow_up:

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 e9e66dd...4982bb1. Read the comment docs.

self merged due to blessing from both @danielballan and @prjemian
@prjemian feel free to push the big green button!


this code just like an art

who codes like this BRUH

Absolutely no one, this is generated code 🤣! As you can see on this GitHub repository the source code doesn't like like this at all.

who codes like this BRUH

Who put underage japanese girls on his desktop ? That's cringe 👀

why code open like this ????

Ram or Rem ? Who is Rem ?

This has got the be one of the funniest exchanges I've seen on Github.

someone help me god pleaseee

 why code open like this ????

You seem to have opened the dist folder. You are not supposed to edit what's in it, its content is automatically generated at build time and isn't supposed to be edited or read.
You should open the src folder instead, it's where the original source files are located.

Is this code golfing ?

what ? ı don't understand what you mean code golfing?


Disable default stat collection. Update README.

I noticed the CLI switch -server-statistics having a default value true. Though you are collecting anonymous stats, its a dark pattern to leave this switch enabled by default.
Any privacy concerned user will definitely be caught by surprise.

There is no prominent mention in the README that stats are collected by mmock by default. Though there is a mention of statistics in the Contributors it doesn't convey that the tool collects anonymous stats.
The CLI switches listed in the README don't feature this flag (perhaps not updated). I happened to find this switch only after running the tool with -h; after which I began to inspect rest of the code.

I know this is a very subjective issue. You are entitled to your PoV. But, my request to you is:

Please disable this switch by default.
Please display information in a very prominent location in the README about mmock's statistic collection, the actual data collected and what can the user do to enable/disable it.

Please let me know your views. Please also let me know if you'd like a PR for this change. TIA.

Hi there,
I've never been really concerned about this topic since you can disable the anonymous statics with a flag and you have all the code available to check how mmock is using them (mainly to check if the features are being used or not).
But I see your point.
I will apply the following changes:

Update the readme adding all the flags from the CLI.
Add specific section about what data is collected by mmock and why
Add a line (if it's enabled) below the application banner explaining that mmock is sending statistic information and how to disable it.

Cheers

I understand that you want usage statistics, but shouldn't the default be to not enable this feature instead? Such kind of metrics collection will be problematic in a lot of work places and is an unexpected default to have IMHO, personally I would expect something like this to be an opt-in feature instead of an opt-out.

For me with that is pretty clear what is mmock doing with the statistics, and how to disable it.
https://github.com/jmartin82/mmock/commit/f9c3570216aa5c9f3d400838030854066d7aa464
And I don't expect anybody concerned about this innocuous metrics.
Thanks!


Make it easier to create teachers and add their class right away

When creating a staff member it should be easy to add their classroom immediately upon creation.

I downloaded the code but it is not working, can you please help me to setup Montessori info system


add comments to code loading (#7199)

Pull request opened by the merge tool on behalf of #7199

Merged into branches iso7 in 89877fd8058027ba4c2c8d79b0ac474cd667f144


Is anyone interested in a Game Design Guides section?

These would include tutorials regarding general game design, level design, and music composition for video games.
I have a decent list of such resources for my own use and would love to share it if possible.

In my opinion, you may add a part named Stuff Resource and put the decent list into it with appropriate description.

@HummusSamurai sounds good, Can you put a new section called Game design with the game design/ level design tools? As for music composition, we already got a Audio section, where you can put links on.
If you have any courses/blogs/etc about learning those , please add them into the Lean section.
Looking forward to check the pull request!

@HummusSamurai any updates?

+1 here :)

@ellisonleao Got a bit caught up for a while, but I'm still here and the resource ain't going anywhere.
Keep in mind it's not tools as much as guides and such, so it'll likely go under the Learn section under a Game Design sub-section.
Could be something of massive scope, really, so I'm also worried it might be too much.

I see. If you think you can add just only the links that you think are most important, feel free to open a pull request.  I am happy to check them


@orta -> disable zoom in internal web views

fixes https://github.com/artsy/eigen/issues/118

CHANGELOG pwease

needs rebase

@orta rebased