[plot] Programatic API resetZoom should not take care of autoscale config

There is no way to reset the zoom programmaticaly.
The resetZoom function should take more parameters to custom the kind of zoom, or another API should be provided for that.

How would you distinguish a programmatic resetZoom and a reset from the user interface?
I would say that if one wants to do it programmatically one can always retrieve the autoscale configuration apply the reset and restore it.
Alternatively, resetZoom(force=False) and changing the keyword could allow you to do what you want.


can't connect mysql db

I've write an initDb func in init.go , code is here
But I got error message :  default addr for network '<IP_ADDRESS>' unknown Failed to establish database connection with root:password@<IP_ADDRESS>/dbname?charset=utf8&parseTime=True&loc=Local
In /github.com/revel/modules/orm/gorp/app/controllers/controller.go (around line 23)

try  ...
root:password@/dbname?etc
or
root:password@tcp(<IP_ADDRESS>)/dbname?etc


After applying a filter; stickers, text, and emoji's will clip.

After applying a filter; Stickers, text, and emoji's will clip or disappear while moving them. Only happens with some backgrounds. Try it with this picture.

I have fixed this. Use view.bringToFront(); in onTouch event on MultiTouchListener class. See below
switch (action & event.getActionMasked()) {             case MotionEvent.ACTION_DOWN:                 mPrevX = event.getX();                 mPrevY = event.getY();                 mPrevRawX = event.getRawX();                 mPrevRawY = event.getRawY();                 mActivePointerId = event.getPointerId(0);                 if (deleteView != null) {                     deleteView.setVisibility(View.VISIBLE);                 }                 **view.bringToFront();**                 firePhotoEditorSDKListener(view, true);                 break;             case MotionEvent.ACTION_MOVE:                 int pointerIndexMove = event.findPointerIndex(mActivePointerId);                 if (pointerIndexMove != -1) {                     float currX = event.getX(pointerIndexMove);                     float currY = event.getY(pointerIndexMove);                     if (!mScaleGestureDetector.isInProgress()) {                         adjustTranslation(view, currX - mPrevX, currY - mPrevY);                     }                 }                 **view.bringToFront();**                 break;             case MotionEvent.ACTION_CANCEL:                 mActivePointerId = INVALID_POINTER_ID;                 break;             case MotionEvent.ACTION_UP:                 mActivePointerId = INVALID_POINTER_ID;                 if (deleteView != null && isViewInBounds(deleteView, x, y)) {                     if (onMultiTouchListener != null)                         onMultiTouchListener.onRemoveViewListener(view);                 } else if (!isViewInBounds(photoEditImageView, x, y)) {                     view.animate().translationY(0).translationY(0);                 }                 if (deleteView != null) {                     deleteView.setVisibility(View.GONE);                 }                 **view.bringToFront();**                 firePhotoEditorSDKListener(view, false);                 break;             case MotionEvent.ACTION_POINTER_UP:                 int pointerIndexPointerUp = (action & MotionEvent.ACTION_POINTER_INDEX_MASK) >> MotionEvent.ACTION_POINTER_INDEX_SHIFT;                 int pointerId = event.getPointerId(pointerIndexPointerUp);                 if (pointerId == mActivePointerId) {                     int newPointerIndex = pointerIndexPointerUp == 0 ? 1 : 0;                     mPrevX = event.getX(newPointerIndex);                     mPrevY = event.getY(newPointerIndex);                     mActivePointerId = event.getPointerId(newPointerIndex);                 }                 **view.bringToFront();**                 break;         }

I have fixed this. add view.bringToFront(); in onTouch event on MultiTouchListener class.
Add this on following MotionEvents at the end
MotionEvent.ACTION_MOVE
MotionEvent.ACTION_DOWN
MotionEvent.ACTION_UP
MotionEvent.ACTION_POINTER_UP

Simply adding view.bringtoFront() on the existing cases didn't work for me.
Adding a default case at the end of the switch statement with your answer solved mine.
 default:
     view.bringToFront();

@shafimuhammed @ExquisiteKyle You can generate a PR if you have fixed this issue.

Using your example app. Load this background. Apply any filter. Now choose an emoji, text or sticker. Move it around the screen. (You might need to shrink the sticker)

I am trying to achieve this UI but IDK how to do that. in the readme file there is no way to achieve this kind of setup i am Nob here not much experience so can you please guide me how to get this complete UI with Text and Stickers on my email<EMAIL_ADDRESS>

[https://github.com/burhanrashid52/PhotoEditor/issues/111#issuecomment-601044700](check this ans)


o1vm/pickles: absorb quotient polynomial and evaluate

Closing in favor of https://github.com/o1-labs/proof-systems/pull/2692


Disappear the last line when using without a new line (\n)

Hi, this is not a serious bug. However, It bothers me.
OS: Ubuntu 16.04
This is my .zshrc configuration
POWERLEVEL9K_MODE='awesome-fontconfig'
POWERLEVEL9K_MULTILINE_FIRST_PROMPT_PREFIX="↱"
POWERLEVEL9K_PROMPT_ON_NEWLINE=true
POWERLEVEL9K_RPROMPT_ON_NEWLINE=true
POWERLEVEL9K_MULTILINE_LAST_PROMPT_PREFIX="↳ "
POWERLEVEL9K_PROMPT_ADD_NEWLINE=true

and I typed this code for testing.
#include <stdio.h>
main() {
int a,b;
scanf("%d %d, &a, &b);
printf("%d", a+b);
}

then I compiled with clang and GCC. I was guessed that if put the 5 8, this program will show that 13.
However, I show the result like that:

The result is disappeared. However, in bash, this result appears.

I guess this is a bug. So, I report this bug.

This is the expected ZSH behavior with options no_prompt_sp and prompt_cr. You can observe it by typing zsh -df --no_prompt_sp --prompt_cr and then echo -n 'hello\nbye'. It's almost always a bad idea to use this set of options.
You can get the same behavior in ZSH as in Bash with no_prompt_sp and no_prompt_cr. It is quite terrible and is unlikely to appeal to anyone.
The best combination is prompt_sp and prompt_cr, which is also the default. So the practical advice is to either add setopt prompt_sp at the end of your ~/.zshrc or remove whatever it is that unsets this option in the first place.


[WIP] Expose switches to reporting

Purpose or Intent
Exposing switches to reporting
Links
Steps for Testing/QA

@miq-bot add_label wip

@miq-bot remove_label wip

👍


Adding ability to peek view state without creating builders

This is needed if you want a view that's "back in history" to be displayed behind the currently active screen.

I like it.  We should keep talking about the types involved-- only saving states from Views does feel a bit wrong, just wary of creating an accidental "history scope".


Supports Intel AVX-512 processor families.

I add intel-avx512 cmake configuration file.
Current available AVX-512 processors:

Intel Xeon Phi (Knights Landing processor families), but please use intel-knl configuration file.
Intel Scalable Processor (Skylake-SP processor families)

I tested the performance under the ISSP System C, University of Tokyo (trial operation).

Thank you @yhirokawa san, I will check it later.

I confirm this PR works well with building "intel-avx512" on intel KNL environment. Thank you for contribution.


Update Math Editor

Do some styling redesigns.

Also do you have any ideas how we could get whether or not the editor has been opened to update or opened to do a new insert? This is useful for figuring out which button text to display but I could also see it as being useful as part of a general callback API.


how to use online sync on linux

I want to sync my ST installed packages and settings between my laptop (linux) and pc (mac).
How can I do it ? I enable online syncing and set online sync folder="Shared" (a folder on my Google drive), then I select command "Push Settings to Online Sync Folder" but nothing is happened...
I guess that I need to install a sync client tool on my computer, but I can not find it. Google drive does not have a sync client on linux.

You would have to choose an alternative sync client that works on both OS X and Linux. FreeFileSync is one such client. Alternatively, you could also look at the post here on how to setup Google Drive on Linux. Do note that I haven't tried this myself.

I see that in many other packages, they have use gist.github.com for store data and sync. I think it will help users easily config and use.
@utkarsh9891: could you add this feature to new version of this package ? It will much awesome !!!

Seems like a nice idea. Would look into the feasibility for this & update the package accordingly. But, unfortunately, I would require some time before I start working on this. You would have to resort to some other file sync client till then.
Or even better if you could add a fork for the gist usage. 👍

@lbngoc: Sorry for the extremely late update but unfortunately I have been unable to find time to work on this package. I did do a feasibility study of the use of gists for syncing packages but the effort required did not seem worth the output.
Although I would definitely work towards adding this feature in a future version, but I would advise you to try syncing via DropBox till then.
Closing this thread as there is no action to be taken at this point of time regarding the feature update.


Store two URLs on monitor (one public, one internal)

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
UI Feature, Other
🔖 Feature description
On HTTP, push, and any other monitor with a URL field—or on monitors that have previously had a URL field set and have had their type changed, so that the url field is set in the database—that URL (which may be internal) is used in a number of places, including status pages, Discord alerts, and as the action for Ntfy notifications.
In the case of status pages, you can elect to show or hide the URL. But for notifications and Discord, you cannot hide the URL; it will always be shown to the end user. There may be other places this can happen other than what I have listed.
The problem is that unless you protect your notification/integration endpoints so that only authorized users may utilize them, this can expose internal-only URLs to external users. And I imagine it would be common to use special URLs for Uptime Kuma, that bypass WAFs, authentication, or otherwise, so that they do not get in the way of monitoring the service.
If there is not a proxy sitting in front of the URL given to Uptime Kuma that can protect against external users accessing it, and if there is no network firewall that blocks sources other than Uptime Kuma and the frontend web proxy, then anyone could grab these URLs and access the underlying service, potentially without the usual protections for the public URL.
✔ Solution
Add a public-facing URL field in addition to the existing internal URL field. This field could also point to documentation for monitors that don't have a web interface. In all cases where the internal URL field is used, the public one is shown instead. Database migrations for this change could copy over the internal URL to a new public URL column for forward-compatibility.
❓ Alternatives
Always make sure any URLs you put into Uptime Kuma are protected by a reverse proxy with basic auth/bearer tokens enabled.
📝 Additional Context
I am not sure how this is separate to #3991. It seems to me that we are talking about the same things, just in different ways.
#1793 is also relevant: It shows that a lot of potentially sensitive information is leaked out of Uptime Kuma, to anyone that is given access to notifications or potentially the status pages. This makes it difficult to use/recommend Uptime Kuma for public-facing service.

I am not sure how this is separate to https://github.com/louislam/uptime-kuma/issues/3991

Currently the push url is bound to the primary base url of the instance. Said issue asks if it is possible to change this for push monitors.
Related duplicate of https://github.com/louislam/uptime-kuma/issues/927
Closing as a duplicate of #2507

This makes it difficult to use/recommend Uptime Kuma for public-facing service.

Here is our contribution guide: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md


Plot_bayesian_cone (problem might be in ppc_t)

Problem Description
In bayesian.py, _plot_bayes_cone has variable perc which results in the error given down the post. So it is apparently of the wrong shape (wrong values - training, correct index - test. The culprit is variable preds, a dict, that is used in a function in tears.py where preds = ppc_t that in turn comes from the bayesian.run_model(model = 't', ppc = True....) where in,
    if ppc:
        ppc_samples = pm.sample_posterior_predictive(trace, samples=samples, # import pymc3 as pm
                                    model=model, size=returns_test.shape[0], # len(returns_test)
                                    progressbar=progressbar)
        return trace, ppc_samples['returns']

Clearly (or maybe not), size should be wrong but doesn't look like it.
I just replaced len(returns_test) with returns_test.shape[0] to see if it does something (it didn't). Now, I am at the end of my thinking capacity and hope someone else follows the trail that why this is happening (or maybe I am missing something trivial).
The full traceback:
ValueError                                Traceback (most recent call last)
<ipython-input-8-4a15f56a81e6> in <module>
      5                           cone_std = (1,2,3),
      6                           live_start_date=live_date,
----> 7                           benchmark_rets=benchmark,)

~\.conda\envs\adv_investment\lib\site-packages\pyfolio\tears.py in create_full_tear_sheet(returns, positions, transactions, market_data, benchmark_rets, slippage, live_start_date, sector_mappings, bayesian, round_trips, estimate_intraday, hide_positions, cone_std, bootstrap, unadjusted_returns, style_factor_panel, sectors, caps, shares_held, volumes, percentile, turnover_denom, set_context, factor_returns, factor_loadings, pos_in_dollars, header_rows, factor_partitions)
    256                                    live_start_date=live_start_date,
    257                                    benchmark_rets=benchmark_rets,
--> 258                                    set_context=set_context)
    259
    260

~\.conda\envs\adv_investment\lib\site-packages\pyfolio\plotting.py in call_w_context(*args, **kwargs)
     50         if set_context:
     51             with plotting_context(), axes_style():
---> 52                 return func(*args, **kwargs)
     53         else:
     54             return func(*args, **kwargs)

~\.conda\envs\adv_investment\lib\site-packages\pyfolio\tears.py in create_bayesian_tear_sheet(returns, benchmark_rets, live_start_date, samples, return_fig, stoch_vol, progressbar)
   1156     # Plot Bayesian cone
   1157     ax_cone = plt.subplot(gs[row, :])
-> 1158     bayesian.plot_bayes_cone(df_train, df_test, ppc_t, ax=ax_cone)
   1159     previous_time = timer("plotting Bayesian cone", previous_time)
   1160

~\.conda\envs\adv_investment\lib\site-packages\pyfolio\bayesian.py in plot_bayes_cone(returns_train, returns_test, ppc, plot_train_len, ax)
    624         ppc,
    625         plot_train_len=plot_train_len,
--> 626         ax=ax)
    627     ax.text(
    628         0.40,

~\.conda\envs\adv_investment\lib\site-packages\pyfolio\bayesian.py in _plot_bayes_cone(returns_train, returns_test, preds, plot_train_len, ax)
    496     perc = compute_bayes_cone(preds, starting_value=returns_train_cum.iloc[-1])
    497     # Add indices
--> 498     perc = {k: pd.Series(v, index=returns_test.index) for k, v in perc.items()}
    499
    500     returns_test_cum_rel = returns_test_cum

~\.conda\envs\adv_investment\lib\site-packages\pyfolio\bayesian.py in <dictcomp>(.0)
    496     perc = compute_bayes_cone(preds, starting_value=returns_train_cum.iloc[-1])
    497     # Add indices
--> 498     perc = {k: pd.Series(v, index=returns_test.index) for k, v in perc.items()}
    499
    500     returns_test_cum_rel = returns_test_cum

~\.conda\envs\adv_investment\lib\site-packages\pandas\core\series.py in __init__(self, data, index, dtype, name, copy, fastpath)
    300                         raise ValueError(
    301                             "Length of passed values is {val}, "
--> 302                             "index implies {ind}".format(val=len(data), ind=len(index))
    303                         )
    304                 except TypeError:

ValueError: Length of passed values is 1105, index implies 101

Please provide any additional information below:
Note that there are 1105 of in sample data and 101 out of sample data and if I change the shape of index of perc and the fill_between functions to returns_train.index, the sheet is generated so I think ppc_t needs to be generated for out of sample as compared to in sample data that it is doing now.
Versions

Pyfolio version: 0.9.2
Python version: 3.7
Pandas version: 0.25.3
Matplotlib version: 3.1.1

I think this error has to do with a change made to PyMC3's sample_posterior_predictive method (formerly sample_ppc, there is currently an open PR to change this). This discourse article describes how the shape of the returned array now depends on the shape of the training data. My fix for this was to define a data container (see this notebook) for the training data, and then swap out the data in the container for testing data prior to calling sample_posterior_predictive.
Here's what I did specifically (all edits in bayesian.py):

In the functions for each model (e.g., model_returns_t  ), define a data container.

with pm.Model() as model:
        data_container = pm.Data("data", data)
        mu = pm.Normal('mean returns', mu=0, sd=.01, testval=data.mean())
        sigma = pm.HalfCauchy('volatility', beta=1, testval=data.std())
        nu = pm.Exponential('nu_minus_two', 1. / 10., testval=3.)

        returns = pm.StudentT('returns', nu=nu + 2, mu=mu, sd=sigma,
                           observed=data_container)
        pm.Deterministic('annual volatility',
                         returns.distribution.variance**.5 * np.sqrt(252))

        pm.Deterministic('sharpe', returns.distribution.mean /
                         returns.distribution.variance**.5 *
                         np.sqrt(252))

        trace = pm.sample(samples)

In run_model, change

if ppc:
        ppc_samples = pm.sample_ppc(trace, samples=samples,
                                    model=model, size=len(returns_test))
        return trace, ppc_samples['returns']

to
if ppc:
        with model:
            pm.set_data({"data" : returns_test})
            ppc_samples = pm.sample_posterior_predictive(trace, samples=samples,
                                        model=model)
        return trace, ppc_samples['returns']

I'm not sure if this is the best way to fix this, but it works for me!


About Box L10N

Fixes https://github.com/flutter/flutter/issues/11887
Adds two material localizations:
  "aboutListTileTitle": "About $applicationName",
  "@aboutListTileTitle": {
    "description": "The default title for AboutListTile",
    "type": "text"
  },

  "licensesPagePoweredByTitle": "Powered by Flutter",
  "@licensesPagePoweredByTitle": {
    "description": "The Powered by Flutter subtitle for the [LicensePage] widget.",
    "type": "text"
  },

I think it may be better to make the entire license screen explicitly English. It needs to be LTR for the licenses anyway (right now the punctuation gets all messed up in RTL). In which case, "powered by flutter" can remain in English to avoid complicated gyrations with the directionality.

LGTM for Japanese and French!


feat: Rename actions to events in property pane

Description
This PR renames the 'Actions' section in the widget property pane to 'Events'. This better communicates the intent of the section i.e users can run actions when events occur, thus the section should be named events.
I've also made an update to the relevant parts of the documentation to update actions to events. See this PR for more info https://github.com/appsmithorg/appsmith-docs/pull/281
Fixes  #4495
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Test A: This has been tested locally on my computer
Test B: All unit tests were run after this change and they all passed

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Okay, I'll remove it

Done

@hetunandu  Can this be merged?

/ok-to-test sha=2023234


Check if coin-op is available by calling the 'fundedAccountAvailable' endpoint

Problem
While creating an account, the wallet shows the verification options regardless of whether coin-op is available/funded or not. This leads to a suboptimal UX since the user may try to verify using their phone/email but end up on the 'self funded' option anyway.

Expected Behavior
The wallet calls the checkFundedAccountAvailable endpoint in near-contract-helper to check if coin-op is available. If coin-op is not available, the email and phone verification options are not visible to the user.
Steps to reproduce

Initiate account creation with a seed phrase
Verify the seed phrase
Observe the phone and email verification options

@MaximusHaximus the checkFundedAccountAvailable in near-contract-helper is currently returning true but suspecting it just doesn't have the same minimum amount logic that we added for the identity funded account creation yet?

❇ 💖  -- Resolved the issue with the checkFundedAccountAvailable endpoint!  Nice work @Patrick1904, this is a big improvement. Shipping this out today.


Bump Microsoft.Extensions.ObjectPool to the latest versions for all TFMs

@ArieGato I suggest you to publish release this time.


Negative amount in RO orders

Two reports so far but I haven't been able to replicate.

What's interesting is that in the first picture the amount in the "MAX" tab and the position size sum up to 1 BTC exactly, maybe that's relevant.

Finally replicated this with the help of a community member. It appears that RO orders in market x affecting the quantity of RO orders in market y for some reason.
As an example, if you open an RO in INJ/USDT PERP and try to open an RO in ETH/USDT PERP you end up with a negative amount.

At the same time I get a very weird error when I try to close my BTC/USDT PERP position which has no RO orders open.

cc @ThomasRalee

Hey @ThomasRalee, commit https://github.com/InjectiveLabs/injective-dex/commit/b252f4605bb44af9e99f8c5dd4c145b5343750f7 fixed the issue with RO orders fetching negative amounts but RO orders are still affecting my ability to close un-related positions.
For instance,

I tried to close my INJ/USDT PERP position and got this error but there are no RO orders in that market. Additionally, shouldn't we automatically cancel RO orders and close the position as per a previous implementation? (I get the same error in BTC/USDT PERP)


Resizing ""-Chat-Input-Textfield on macOS breaks UI

Resizing the Chat-Input-Textfield by draging the handler on the bottom right causes the whole UI to break and creates a horizontal scroller in the chatview.

Just curious, could you please provide a screenshot?
I'm unable to resize chat message text area and I'm also using macOS. 🤔

It has a handlebar in the bottom left corner.

Interesting. I see the handle but I can't click it and drag it on my computer. Weird...
Thanks for the report and subsequent pull request.

Thanks for merging. You can drag it, while the mouse cursor is still the text cursor. Btw: Thanks so much for this client! The original is garbage.


removed unused smartcollection.products endpoint

The SmartCollection#products endpoint was behind a beta flag, which was never enabled. Sitting at 0% since 2018. The REST API documentation was never added. All calls to this endpoint would result in a 401. Since we're removing the endpoint from the controller, I'm first removing it from the API.
I checked with #api-patterns and they confirmed this is safe to remove.

/shipit


Map tags to inventory devices and test catalog

Increase flexibility by using tags on inventory devices and the test catalog, so that catalog tests can run on relevant devices only. For instance, in s typical EVPN scenario there.might be some tests that should run only in spines and some other tests only on leaf switches, having also some tests that run on all devices. Using tags or filters on tests and inventory devices could achieve this easily and add flexibility to the way tests execute. For inventory networks/ranges, tags would apply to the whole range/network...

We are going to start tag implementation with the following approach:

Inventory file:

anta_inventory:
  hosts:
  - host: <IP_ADDRESS>
     tags: []
  - host: <IP_ADDRESS>
     tags: []
  - host: <IP_ADDRESS>
  - host: <IP_ADDRESS>
  - host: <IP_ADDRESS>
  - host: <IP_ADDRESS>
  networks:
  - network: <IP_ADDRESS>/24
  # ranges:
  # - start: <IP_ADDRESS>
  #   end: <IP_ADDRESS>

Closing this issue since the current tags implementation fits the use case:

Define multiple test catalogs, one per inventory tag
Run ANTA multiple times mapping the device tags with their test catalogs


Reproducible failure in TestUnifiedHighlighter.testOneSentence (and others) - index order

Description
I came across this one by stress-testing the package with -Dtests.iters=200. Occasional hiccups in unified highlighter tests, for example:
gradlew :lucene:highlighter:test --tests "org.apache.lucene.search.uhighlight.TestUnifiedHighlighter.testOneSentence" -Ptests.seed=24C86DF477CBF09B:8FFE031B3019BA09

The test expects documents in indexing order:
    body.setStringValue("This is a test.");
    iw.addDocument(doc);
    body.setStringValue("Test a one sentence document.");
    iw.addDocument(doc);

    IndexReader ir = iw.getReader();
    iw.close();

    IndexSearcher searcher = newSearcher(ir);
    UnifiedHighlighter highlighter = randomUnifiedHighlighter(searcher, indexAnalyzer);
    Query query = new TermQuery(new Term("body", "test"));
    TopDocs topDocs = searcher.search(query, 10, Sort.INDEXORDER);
    assertEquals(2, topDocs.totalHits.value);
    String[] snippets = highlighter.highlight("body", query, topDocs);
    assertEquals(2, snippets.length);
    assertEquals("This is a test.", snippets[0]);
    assertEquals("Test a one sentence document.", snippets[1]);

But for some reason they're swapped.
I didn't look into it but it also happens with other tests (rarely).
Version and environment details
No response

The test occasionally gets MockRandomMergePolicy and it relies on document addition order.


Token authentication - vRO Inventory not persisted permanently.

When using token authentication on first connect vRO inventory is functional.
This is timing out after a short period of time, with pre-existing virtualservices that still exist no longer visible in the vRO inventory.
The workaround here is to reattach the vRO client by rerunning the "Attach Avi Controller" workflow, generally vRO inventory connections are a one off connection then persisted.

Confirmed resolved in latest beta release


Vim9: cannot create a hidden terminal buffer

Describe the bug
In Vim9 script, we cannot create a hidden terminal buffer.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    term_start(&shell, #{hidden: true})
EOF
)

E611 is raised:
E611: Using a Special as a Number

And the terminal buffer is displayed in a window.
Expected behavior
No error is raised, and the terminal buffer is not displayed in a window.
Environment

Vim version: 8.2 Included patches: 1-1471
OS: Ubuntu 16.04.7 LTS
Terminal: XTerm(358)

Additional context
It's caused by a regression introduced in 8.2.1465.

E611 is not documented.

In Vim9 script, we cannot create a hidden terminal buffer.

Actually, we can.  We just need to avoid true, and use 1 instead:
vim9script
term_start(&shell, #{hidden: 1})

Still, we should be able to use true; I find it makes the code more readable.

E611 is not documented.

The message is pretty clear by itself, but there is no help tag.

The following doesn't work anymore either:
vim9script
call popup_create('test...........', {'wrap': true})

Vim version 8.2.1477

The following doesn't work anymore either:
vim9script
call popup_create('test...........', {'wrap': true})

I'm trying to find a balance between being backwards compatible and
being strict about the values for options.
When the value is a number, e.g. a height, then passsing "true" or
"false" is wrong.  So far that was accepted, I think it's good to start
giving an error for this.
When the value is a flag, e.g. "hidden", then passing 1234 is possibly
wrong.  But "0" and "1" are OK, as these were advertised as being the
same as "false" and "true".
At the other end of the possibilities, in a Vim9 expression we accept
many types and consider them "falsey" or not.  E.g. an empty list is
false, a non-empty list is true.  But this is where it's clear that the
expression needs to evaluate to a boolean, such as for ":if".
I tend to think that for these options it's easy to make a mistake and
use a number (or list or dict) where a boolean is expected.  And
accidentally use true/false for where a number of string is expected.
Thus I'm currently aiming at making this more strict.
Problem is that until now "get_number()" was used for both numbers and
booleans.  Thus we need to find all of the ones that are actually
booleans and change those.
--
hundred-and-one symptoms of being an internet addict:
231. You sprinkle Carpet Fresh on the rugs and put your vacuum cleaner
in the front doorway permanently so it always looks like you are
actually attempting to do something about that mess that has amassed
since you discovered the Internet.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Transformation.DepthImageToPointCloud does not work on OrbbecSDK v1.9.1

I need to convert Depth image to PointCloud data.
Describe the bug

When I call Transformation.DepthImageToPointCloud the returning Image has all the data equals to 0.
To Reproduce

Open the camera
Get the Calibration object
Create the Transformation object passing the Calibration object.
Retrieve Depth Image.
Check that Depth.Memory has data different from 0.
Call Transformation.DepthImageToPointCloud passing the Depth Image.
Check if the output Image Memory data has some byte different from 0.

Expected behavior

The output image from Transformation.DepthImageToPointCloud must have data different from 0.
Logs

Screenshots

Desktop (please complete the following information):

OS with Version:  Windows 10
SDK Version:   1.9.1 (OrbbecSDK.dll = 1.9.4)
Firmware version:   1.0.9

Additional context

On Azure SDK, the same code works well.

Is it normal to save point clouds using this sample? （https://github.com/orbbec/OrbbecSDK-K4A-Wrapper/tree/main/examples/transformation）

Thanks @zhonghong322 for your reply.
To my understanding the only way to get the Point Cloud is via the method
k4a_transformation_depth_image_to_point_cloud().
And from what I've tried, it doesn't work on this Orbbec Wrapper.
Are there other ways to do that?

Thanks @zhonghong322 for your reply. To my understanding the only way to get the Point Cloud is via the method k4a_transformation_depth_image_to_point_cloud(). And from what I've tried, it doesn't work on this Orbbec Wrapper. Are there other ways to do that?

https://github.com/orbbec/OrbbecSDK-K4A-Wrapper/commit/f831db7d20782192e6537e148ab1ced785894a58    Thank you for your feedback，The current develop branch has fixed this issue. You can pull the latest code for compilation, or wait for our new version to be released


Incorrect routing with setup.php based base

There is an incorrect use of str_replace in Grav\Common\Uri::init():
[https://github.com/getgrav/grav/blob/eca23a918a71b0a49f5abad59e6c824f9e146351/system/src/Grav/Common/Uri.php#L321]($uri = str_replace($setup_base, '', $uri);).
The problem is that instead of removing just the prefix, each occurence of $setup_base is removed. For example, if the input $uri is equal to '/foo/bar/foo/baz' and $setup_base is equal to '/foo', then the output $uri is now equal to '/bar/baz'.  The correct result should be  '/bar/foo/baz'.

assigned to @mahagr to look at.

I just checked this and the behaviour is correct. It should do just that as the base path gets added to the urls by base_url variable in twig or by using url().
Uri is always relative to the site itself and is used in routing. If you want to point files outside of the site, you need to use absolute (or external) URLs.

The behaviour which I have observed is that if the name of the subsite coincides with the name (the slug) of some page, then that page (or any of its subpages) is routed incorrectly.
For example, suppose 'foo' is the name of the subsite ('/foo' is then passed as $prefix to $container['pages']->base($prefix)). Furthermore, suppose that some page of the subsite is also named 'foo'.  Let $url be  $hostname . '/foo/bar/foo'. Then this url is resolved to the 'bar' page instead of to the 'foo' page.

Just pressed the wrong button, no intention to close the issue.

Ok, I think I got it now.
You're saying that /foo/bar/foo will become /bar/ instead of /bar/foo...?

Yes, exactly. Similarly, in my first example which I gave when I opened the issue, I was saying that /foo/bar/foo/baz will become /bar/baz instead of /bar/foo/baz.

Should be fixed for Grav 1.4.6


Update sbt-tpolecat to 0.1.22

Updates io.github.davidgregory084:sbt-tpolecat from 0.1.19 to 0.1.22.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.github.davidgregory084", artifactId = "sbt-tpolecat" } ]

labels: sbt-plugin-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #713.


Monitor application health issues

Is pinpoint now able to check the health status of monitoring applications?

Hello, @zqzgit
What do you mean by health status of the application?

Pinpoint monitoring an application, the agent's health status can be obtained, but the agent's health status can not represent the health status of the application being monitored, how can I know whether the monitored application is healthy? Does pinpoint provide this feature?

Hello, @zqzgit
Currently, Pinpoint doesn't have any standard or rule to check the health of the application being monitored.

Okay thank you


Adding Linting Rules and Auto-Linting

This PR adds the following:

It adds coveralls as an NPM dependency for when we're ready to plug into that system.
Removes nyc from the test to speed up unit tests in Travis CI. Coverage reporting is run after tests have passed.
Adds a script to generate html coverage reports.
Adds eslint and Prettier rules for auto-linting in the Atom text editor.

:tada: This PR is included in version 1.0.0 :tada:
Your semantic-release bot :package::rocket:


Is it possible to model a transfer function using an IOBlock?

Newbie to this library.  I'm wondering if there's a way to define the transfer function of a second order harmonic oscillator using this library?

No, currently it is state-space system only. You could use ControlSystems.jl to get the ABCD system matrices from a transfer function object. Requires some additional code to digest those matrices though, I've used something like that for another project
function IOBlock(A::Matrix,B::Matrix,C::Matrix,D::Matrix,x,y,u; name=gensym(:LTI), warn=BlockSystems.WARN[], rem_eqs=Equation[])
    @assert size(A)[1] == size(A)[2] == size(B)[1] == size(C)[2]  == length(x)
    @assert size(B)[2] == size(D)[2] == length(u)
    @assert size(C)[1] == size(D)[1] == length(y)
    iv_candidate = unique(vcat(Symbolics.arguments.(value.(x)),
                               Symbolics.arguments.(value.(y)),
                               Symbolics.arguments.(value.(u))))
    @assert length(iv_candidate) == 1 && length(iv_candidate[begin]) == 1
    iv = iv_candidate[1][1]
    dt = Differential(iv)
    eqs = vcat(dt.(x) .~ A*x + B*u,
               y .~ C*x + D*u)
    filter!(eq -> !isequal(eq.lhs, eq.rhs), eqs)

    IOBlock(eqs, u, y; name, warn, rem_eqs)
end


Improve Gradle and Makefile test cases

@dariusf I wasn't able to build the gradle project on latest Java. Is there a particular version it works on?
Asankhayas-MacBook-Pro:multi-modules asankhaya$ srcclr scan --debug
com.sourceclear.agent.services.ConfigServiceImpl	DEBUG	Using config file at "/Users/asankhaya/.srcclr/agent.yml"
com.sourceclear.agent.services.ConfigServiceImpl	DEBUG	Using config file at "/Users/asankhaya/.srcclr/agent.yml"
com.sourceclear.agent.services.ConfigServiceImpl	DEBUG	Using config file at "/Users/asankhaya/.srcclr/agent.yml"
com.sourceclear.agent.services.ConfigServiceImpl	DEBUG	Using config file at "/Users/asankhaya/.srcclr/agent.yml"
com.sourceclear.agent.services.ConfigServiceImpl	DEBUG	Using config file at "/Users/asankhaya/.srcclr/agent.yml"
com.sourceclear.agent.services.ConfigServiceImpl	DEBUG	Using config file at "/Users/asankhaya/.srcclr/agent.yml"
com.sourceclear.agent.services.ConfigServiceImpl	DEBUG	Using config file at "/Users/asankhaya/.srcclr/agent.yml"
com.sourceclear.agent.util.TrustManagerFromEnv	DEBUG	Skipping additional SSL Trust Manager configuration because both $SRCCLR_SSL_CERT_DIR and $SRCCLR_SSL_CERT_FILE are blank
com.sourceclear.agent.services.ConfigServiceImpl	DEBUG	Using config file at "/Users/asankhaya/.srcclr/agent.yml"
com.sourceclear.agent.EntryPointImpl	DEBUG	Executing scan with com.sourceclear.agent.commands.ScanCommand
com.sourceclear.agent.EntryPointImpl	DEBUG	SourceClear Agent/3.3.9 (Azul Systems, Inc./11.0.2+9-LTS; arch="x86_64" name="Mac OS X" version="10.14.5" language="en" timezone="America/New_York")
com.sourceclear.agent.EntryPointImpl	DEBUG	Verb Options := verbOpts = {
}
left-overs = []
com.sourceclear.agent.services.LicenseServiceImpl	INFO 	Checking Agent authentication against the SourceClear API...
com.sourceclear.util.io.GitUtils	DEBUG	git status --porcelain stdout:
com.sourceclear.util.io.GitUtils	DEBUG	git status --porcelain stderr:
com.sourceclear.agent.commands.ScanCommand	DEBUG	Scanning local directory with upload. Repo is clean. Proceeding...
com.sourceclear.agent.commands.ScanCommand	DEBUG	Scan collectors:
com.sourceclear.agent.commands.ScanCommand	DEBUG	Skip collectors:
com.sourceclear.agent.commands.ScanCommand	DEBUG	Skip vulnerable methods: false
com.sourceclear.agent.commands.ScanCommand	DEBUG	Setup completed in 0s
com.sourceclear.engine.component.ComponentEngineBuilder	DEBUG	collectorsToRun: []
com.sourceclear.engine.component.ComponentEngineBuilder	DEBUG	collectorsToSkip: []
SourceClear scanning engine ready
com.sourceclear.agent.services.ConfigServiceImpl	DEBUG	Using config file at "/Users/asankhaya/.srcclr/agent.yml"
com.sourceclear.agent.services.ScanServiceImpl	DEBUG	Beginning dependency analysis
Running the Gradle scanner
com.sourceclear.engine.component.NativeLocalEngine	DEBUG	Collector "Gradle" started
com.sourceclear.engine.component.collectors.GradleNativeCollector	INFO
com.sourceclear.engine.component.collectors.GradleNativeCollector	INFO 	FAILURE: Build failed with an exception.
com.sourceclear.engine.component.collectors.GradleNativeCollector	INFO
com.sourceclear.engine.component.collectors.GradleNativeCollector	INFO 	* What went wrong:
com.sourceclear.engine.component.collectors.GradleNativeCollector	INFO 	Could not determine java version from '12.0.1'.
com.sourceclear.engine.component.collectors.GradleNativeCollector	INFO
com.sourceclear.engine.component.collectors.GradleNativeCollector	INFO 	* Try:
com.sourceclear.engine.component.collectors.GradleNativeCollector	INFO 	Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
com.sourceclear.engine.component.collectors.GradleNativeCollector	DEBUG	Executing '/Users/asankhaya/git/efda/java/gradle/multi-modules/gradlew --version' to get gradle version.
com.sourceclear.engine.component.collectors.GradleNativeCollector	DEBUG	non-zero rc when getting gradle version: 1. stderr:
FAILURE: Build failed with an exception.

* What went wrong:
Could not determine java version from '12.0.1'.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

com.sourceclear.engine.component.collectors.GradleNativeCollector	DEBUG	version found from executing '/Users/asankhaya/git/efda/java/gradle/multi-modules/gradlew': 'Optional.empty'
com.sourceclear.engine.component.collectors.GradleNativeCollector	DEBUG	default scope set to: compile
com.sourceclear.engine.component.collectors.GradleNativeCollector	DEBUG	GRADLE_TASKS is neither a string or a list: null
com.sourceclear.engine.component.collectors.GradleNativeCollector	DEBUG	Running default tasks: [projects, classes]
com.sourceclear.engine.component.collectors.GradleNativeCollector	INFO 	Running Gradle Graph Building with: /Users/asankhaya/git/efda/java/gradle/multi-modules/gradlew -Psrcclr.graph.location=/var/folders/8g/6318h_294_50lq3drcthxrr40000gp/T/graph-3897482977608724231.json -Psrcclr.scope=compile --init-script /var/folders/8g/6318h_294_50lq3drcthxrr40000gp/T/init-1831441623383698571.gradle projects classes
com.sourceclear.engine.component.collectors.JsonComponentGraphNativeCollector	INFO
com.sourceclear.engine.component.collectors.JsonComponentGraphNativeCollector	INFO 	FAILURE: Build failed with an exception.
com.sourceclear.engine.component.collectors.JsonComponentGraphNativeCollector	INFO
com.sourceclear.engine.component.collectors.JsonComponentGraphNativeCollector	INFO 	* What went wrong:
com.sourceclear.engine.component.collectors.JsonComponentGraphNativeCollector	INFO 	Could not determine java version from '12.0.1'.
com.sourceclear.engine.component.collectors.JsonComponentGraphNativeCollector	INFO
com.sourceclear.engine.component.collectors.JsonComponentGraphNativeCollector	INFO 	* Try:
com.sourceclear.engine.component.collectors.JsonComponentGraphNativeCollector	INFO 	Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
Encountered errors while collecting component information.
Processing results...
com.sourceclear.engine.scan.PlatformScan	DEBUG	Evidence set is empty after collection.
com.sourceclear.api.client.SourceClearClient	DEBUG	Skipping post-fact status code check because of retry-mode (but, code=200 status=null)
com.sourceclear.engine.scan.PlatformScan	DEBUG	Matched in 0 seconds.
Processing results complete
com.sourceclear.agent.EntryPointImpl	DEBUG	Exiting with 1
com.sourceclear.agent.FatalException: This project does not seem to build.
Because of this, SourceClear cannot scan it. Please ensure that the project compiles prior to scanning.
	at com.sourceclear.agent.commands.ScanCommand.handleScanErrors(ScanCommand.java:1004)
	at com.sourceclear.agent.commands.ScanCommand.executeRepoScan(ScanCommand.java:782)
	at com.sourceclear.agent.commands.ScanCommand.execute(ScanCommand.java:476)
	at com.sourceclear.agent.EntryPointImpl.runVerb(EntryPointImpl.java:372)
	at com.sourceclear.agent.EntryPointImpl.dispatchVerbOptions(EntryPointImpl.java:321)
	at com.sourceclear.agent.EntryPointImpl.apply(EntryPointImpl.java:157)
	at com.sourceclear.agent.Main.main(Main.java:96)
Caused by: com.sourceclear.engine.component.CollectionException: This project does not seem to build.
Because of this, SourceClear cannot scan it. Please ensure that the project compiles prior to scanning.
	at com.sourceclear.engine.component.collectors.JsonComponentGraphNativeCollector.handleNonZeroProcessExit(JsonComponentGraphNativeCollector.java:176)
	at com.sourceclear.engine.component.collectors.JsonComponentGraphNativeCollector.collect(JsonComponentGraphNativeCollector.java:128)
	at com.sourceclear.engine.component.collectors.GradleNativeCollector.collect(GradleNativeCollector.java:49)
	at com.sourceclear.engine.component.NativeLocalEngine.collect(NativeLocalEngine.java:96)
	at com.sourceclear.agent.services.ScanServiceImpl.performScanEx(ScanServiceImpl.java:573)
	at com.sourceclear.agent.services.ScanServiceImpl.performScan(ScanServiceImpl.java:447)
	at com.sourceclear.agent.commands.ScanCommand.lambda$executeRepoScan$5(ScanCommand.java:790)
	at com.sourceclear.agent.commands.ScanCommand.handleScanErrors(ScanCommand.java:984)
	... 6 more

Tried it on 1.8.0_181. Unfortunately we don't support Gradle 5+ yet, which would be required to build with Java 12.

Also updated the spreadsheet with a bunch of package managers.

fixes #14 .


Reference App crashed on search.

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #877
Description
There are two fatal exceptions.

As per the attached log, exception is dataformat exception which was caused at the time of json parsing. Just remove the separator which is used to separate the object entity in resource  entity under the serialised resource section. Now, this exception is caught in reference application so that it will not crash the app
Another exception is ResourceNotFoundException which get thrown by engine module. To reproduce it just update the patient id which is not present in resource entity table in serialized resource column. When user click on origin patient item on patient list, it throws ResourceNotFoundException. Now exception is caught at application side, so that it will not crash the app.

Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
Type
Choose one: Bug fix
Screenshots (if applicable)
Checklist

[x] I have read and acknowledged the Code of conduct
[x] I have read How to Contribute
[x] I have read the Developer's guide
[x] I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA
[x] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project
[x] I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally
[x] I have built and run the reference app(s) to verify my change fixes the issue and/or does not break the reference app(s)

@jingtang10
I have updated comment in issue.
jfyi, issue itself raised by modifying application local database ResourceEntity table serialized column through database inspector which was mentioned in precondition.

Updated comment in the issue #877


Cache leak

Seriously, why do electron apps try to cache everything, the app after a few weeks of usage can eat up to GBs of space

Could add delete cache as a temporary fix. But hopefully this cache can be reused to play music that has already been listened to.

Added temporary fix in https://github.com/duzda/deezer-enhanced/commit/2a93865c94484987ed7da10410bd3aacc1a7d8bc

The blob_storage seems to be leaking randomly, one day it stays at 0 bytes, the other 2GB get created randomly.

The temporary fix, can be safely removed


A theano.clone() equivalent for Tensorflow

This an implementation of a clone() function for Tensorflow based on meta_graph utilities, inspired by discussion with @sherrym in #5477 .
Feature requests on this can be found in #1070  #5479 . Previous implementations of copying graphs #557 does copy naively and doesn't have replace feature as in theano.clone().
Though this implementation is almost good. It still has problems for now with control flow copies. To be specific, I'm not sure how to deal with collections of cond_context and while_context, because both of its to_proto functions only consider the case of stripping export_scope.
Not copying cond_context collection to new operations (to their _control_flow_context) will cause problems described in #5477 , also demonstrated in the last test (testCloneBatchNorm) in this pull request, which is failed for now. I'm opening this PR early before that test pass, wondering if someone can have advice on dealing with control flow collections when cloning subgraphs. Thanks.

Can one of the admins verify this patch?

Anyone help with this PR? @sherrym , @keveman , @vrv , @ebrevdo , especially about the control flow context part.

@yuanbyu may know about control flow parts

Ping all! @sherrym, @yuanbyu can you look at this?

@yaroslavvb @martinwicke Thanks for help. I'm always willing to keep working on this feature.

How does this work related to the graph view and replace operations in contrib?  Can those tools be used to perform cloning?

@ebrevdo Thanks for the question. The short answer:
They cannot do exactly the same thing due to bugs, but to fix bugs touches the design. While using meta_graph, from my view, is the most elegant way to implement and maintain this feature.
Long answer:
I used to rely on tf.contrib.graph_editor. It seems to have everything. But I have to say it's still buggy, and maintenance seems to have stopped for some time. The graph_replace function provided in tf.contrib.graph_editor tries to do similar things with this PR, however, there are big cases it fails, for example, when one node in the given replacements is a descendant of another, the copied subgraph won't cover the uprooting graph of the descendant node even there are target nodes between this two nodes. I tries to fix but it turns out things are not easy under that framework. This is not the only problem, you could see I had a PR ( #5451 ) merged on problems about control inputs. It's still an easy one to fix, but there exist much harder ones.
Though this owes much to lack of extensive tests in tf.contrib modules, I'm still wondering whether tf.contrib.graph_editor is the right way to achieve this clone() ability. Then I found the _control_flow_context problem, which I raised in #5477 . This is because copying operations in tf.contrib.graph_editor is by directly copying members of a python objects. In that issue @sherrym pointed out to me that I could use meta_graph utilities to achieve what I want. So I made this trial. Though I still don't succeed in copying control flow contexts, I find the codes more elegant in this way, compared to implementations in tf.contrib.graph_editor.
I believe this is at least a right direction to implement this theano equilvalent. And I also want to point out that this function is of great value to people building higher level libraries based on Tensorflow, it helps on operation level reuse (which cannot be achieved either by using name scope or by experimental function utilities in TF).

@sherrym  ping. Can you comment if this is feasible to get merged?
@thjashin note that getting added to contrib means it's a candidate to be moved into core, which means that core TensorFlow team would have to take over support and maintenance. Hence, the code has to be easy enough to transfer over (ie, design docs can help sometimes)

@thjashin could you merge and push again?

@yaroslavvb Thanks. Any templates for design docs?

@drpngx Sure, I'll do it tomorrow.

@thjashin I was thinking more of an informal thing that'll help someone understand for someone reading the code for the first time (ie, motivation, brief outline of how code is structured and why)

@drpngx Done.

Jenkins, test this please.

We might have to move that to contrib first.

@drpngx I think I've modified things in the framework, not just adding other functions...Can you give some advice on how to move them into contrib? btw, I guess if you can get some team member to review, can we directly merge? I guess I don't change the original behavior of other parts of code. Also if you need design docs. I'm very happy to write one. In fact it's just a DFS in the graph with some terminal conditions.

@sheerym or @yuanbyu are the best to review this.

@sherrym sorry, typo.

@thjashin I'll try pinging sherrym and yuanbyu directly to review this. In the mean time, can you fix the merge conflict that's appeared?

@dandelionmane Sure. I will do this tomorrow.

cc @purpledog

@dandelionmane I've done the merge.

Jenkins, test this please.

@yuanbyu @sherrym Could you take a look? I'm not super familiar with this part of the code.

I am not very familiar with this part of the codebase. For the control flow context, it seems to strip name scope when exporting and to add back the "current" name scope when importing. Why doesn't it work in your case?

I think for now, given that we don't really have any volunteer maintainers of this code internally, we're going to close this PR;  I think the current implementation of GraphDef and state in TensorFlow's python implementation is not very amenable to analysis and correctness, and while what you've done is very neat, it will probably make it very difficult or impossible to move the existing complex python code (control flow, state management) to better implementations (not a proof, but just a gut feeling).
I believe some of the work on improving functions and state management will make something equivalent to clone() possible and maintainable, and that's what we really need to make sure we do if we intend to make our users happy.

+1 I think for now we need to reserve the right to make changes to this
part of the tf codebase without maintaining a .clone implementation,
especially given the lack of internal maintainers.
On May 5, 2017 5:45 PM, "Vijay Vasudevan"<EMAIL_ADDRESS>wrote:

I think for now, given that we don't really have any volunteer maintainers
of this code internally, we're going to close this PR; I think the current
implementation of GraphDef and state in TensorFlow's python implementation
is not very amenable to analysis and correctness, and while what you've
done is very neat, it will probably make it very difficult or impossible to
move the existing complex python code (control flow, state management) to
better implementations (not a proof, but just a gut feeling).
I believe some of the work on improving functions and state management
will make something equivalent to clone() possible and maintainable, and
that's what we really need to make sure we do if we intend to make our
users happy.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/5802#issuecomment-299604392,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtim4hXvJfm5wuLY7Kd6F2SbPmX1GAXks5r28LFgaJpZM4K6UfI
.


Harbor 1.10 upgrade

This PR upgrades our version of Harbor from 1.9.3 to 1.10.0
Checklist

[ x] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated.
[ x] Changelog entry has been written

Changelog Entry
Improvement - Upgrade Harbor version

Builds are passing, and pods are running successfully. I'll be testing various functionality to make sure everything works as it should before we can call this 100% ready to merge

After this is deployed, we'll be required to update the db password for the newly created harborclair config and delete the previous harbor-clair deployment, config, and secrets.


Merge dev branch, containing several fixes and optimizations

This PR:

Adds a method to check signal generation common to all methods, deprecate individual ones.
Add common wrapper for all lc_gen_*.
Upgrades Correlation().peak_find(), which now interpolates if specifically asked, optionally smooths with a gaussian kernel. It also does not plot over the correlation.
Remove the *_ab from kroedel_ab and welsh_ab function names.
Implement kroedel, welsh and lc_gen_ou with numba. Significant speed up when using these functions (kept old ones under the suffix _old, for debugging purposes.
Updates requirements, tests and notebooks.

I think it is ready for merging.

I increased test coverage, now all check pass. Merging.


V1.3

Here's what could become CLDF 1.3. Please have a look @jcgood @fmatter @Glottotopia

Looks good to me

Looks good to me, too, though I'm still new to reviewing these sorts of things. Thanks!

👍


[WFLY-14864] Remove "always true" instanceof checks

Fixes https://issues.redhat.com/browse/WFLY-14864
Includes dead code removal.

the check failed with an unused import JBossGenericBeanMetaData

@bstansberry Hello Brian, tests for this PR passed, PR is approved. Could you please check and merge?


How to print loss value for each given iterations?

Can I print the loss values for each N iteration without checkpointing the model?

Use this callback, it will be called after each batch:
https://github.com/dmlc/mxnet/blob/master/python/mxnet/callback.py#L30

Thanks ..


the final result

I find your output file-train-log  , the accuracy is almost 10% , why obtain the not ideal result

I'm sorry to disturb you. Since the link of the data set of this project in the current year is invalid and the author cannot be contacted, I can only ask you in this way. If you still have the data set of this project, could you please send it to me<EMAIL_ADDRESS>


Adds support for considering checkpoint dir size in retention policy.

Signed-off-by: Harkishen Singh<EMAIL_ADDRESS>
Fixes: #7954

cc @codesome

@codesome done as per said.

@codesome fixed tests.

https://github.com/prometheus/prometheus/issues/7954#issuecomment-699940659

Closing PR in favour of https://github.com/prometheus/prometheus/issues/7954#issuecomment-699940659.

Thanks for working on it so far!


chore: separate component definitions from component server

Stack:

#216
#215
#214
#213 ⬅

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

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

Project coverage is 67.39%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #213   +/-   ##
=======================================
  Coverage   67.39%   67.39%
=======================================
  Files          25       25
  Lines         917      917
  Branches      917      917
=======================================
  Hits          618      618
  Misses        273      273
  Partials       26       26

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

✓ Commit merged in pull request #216


IPv6 listener support

please update the code for IPv6 support as in "ethtool-exporter" https://github.com/Showmax/prometheus-ethtool-exporter/issues/3

mistake


add panel, pad, form, menu binding

;-)

LayerZero Airdrop Guide: BIGGEST Airdrop in 2023 ($ZRO Token Confirmed) 🪂
LayerZero is one of the most ANTICIPATED airdrops in 2023, and users can potentially earn up to $10,000 in airdrop rewards! This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Claim Now on Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Share on Social Media:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Reddit

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

3. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

Winners: @yemtao, @Jolg42, @656025633, @luohaoyuan, @hyperknob, @jimlgx, @darkdown, @vanpersiexp, @Smoogold7, @shirohige


Resource object instances returned by HydroShare object are memcached

It may be desirable for a Resource returned by HydroShare.resource(...) be memcached in the HydroShare instance. This means any metadata retrieved and cached at the Resource object level are maintained in memory through a reference in the HydroShare instance. Here, this is implemented through a dictionary, HydroShare._resource_object_cache.
There are two downsides (that I can think of) to this implementation that should be considered:

HydroShare.resource(...) now is not thread safe. One could argue it was not thread safe previously as it passes a reference to a mutable HydroShareSessionobject, but for the most part, that object should be read only.
Introduces complexity in managing references. Meaning, if a user wanted the garbage collector to destroy a Resource instantiated via HydroShare.resource(...), they would have to remove the key value pair from the HydroShare._resource_object_cache dictionary. I don't think this is really an issue, but I wanted to mention it as it is an assumption the software is now imposing.

Tests failed because hydroshare credentials were not passed as env variables.

I'll take a look at what went wrong with the tests when I get a chance.  Thanks for submitting this so quickly.

@sblack-usu are the secrets used in the gh-action repo level secrets? I wonder if i'm added in a different role to the project if it will fix this.

@sblack-usu this appears to be the issue. Under a repos settings/secrets:
Secrets are not passed to workflows that are triggered by a pull request from a fork. Learn more.

You're right, that's unfortunate.  I've added you as a collaborator with write access.

It's still failing.  I wonder if the PR needs to be resubmitted instead of just redploying the job to pick up the newly available secrets?

I think it is an issue with using a PR from a fork workflow. I just created a new branch on my fork and added a gh-action that just runs the unit tests. The branch is based off of 3243379  (the last commit  in the PR at this time).

Tests are still failing, but it doesn't look like anything i've added here:
=========================== short test summary info ============================
FAILED tests/test_functional.py::test_creator_order - AttributeError: 'str' o...
FAILED tests/test_functional.py::test_resource_metadata_updating - AttributeE...
FAILED tests/test_functional.py::test_resource_delete - AssertionError: asser...
FAILED tests/test_functional.py::test_aggregation_fileset[files0] - Exception...
FAILED tests/test_functional.py::test_aggregations[files4] - Exception: Faile...
FAILED tests/test_functional.py::test_filename_spaces - Exception: Failed GET...
ERROR tests/test_functional.py::test_pandas_series_local - Exception: Failed ...
ERROR tests/test_functional.py::test_folder_download - Exception: Failed GET ...
============== 6 failed, 37 passed, 2 errors in 959.08s (0:15:59) ==============

let's table this for now and I'll take a look soon.

@horsburgh - What do you think about caching Resource objects in the HydroShare instance?  @aaraney's implementation looks good and I'm working on figuring out what is going on with the test secrets when a fork submits a PR (the reason why the tests are failing).  The concern over thread safety when accessing/updating a dictionary isn't a concern for me, the dictionary won't get corrupted, the only possible issue is a race condition when saving multiple instances of the same resource to the cache in multiple threads.  It's definitely an edge case and we could solve it with a lock, but the case is rare and the consequence is small.
We could solve @aaraney second point by including a clear_resource_cache() method and documenting the feature.

The same cache functions could be added to aggregations within a resource.  I don't think aggregations should hold up this PR though.  @aaraney, do you have an eta for this?  I'm aiming for a release this week if you have the time.

The same cache functions could be added to aggregations within a resource. I don't think aggregations should hold up this PR though. @aaraney, do you have an eta for this? I'm aiming for a release this week if you have the time.

@sblack-usu, I can add in the requested use_cache param plus the units tests pushed up this afternoon. Is there anything else you would like me to include?

That should cover it.

@sblack-usu In writing tests for the aforementioned additions, I ran into an issue that requires an implementation decision. I wanted to shed light on it before I go further.
In short, HydroShare.create calls HydroShare.resource (with the default use_cache parameter), so if a user creates a resource from an instantiated HydroShare object, they will implicitly add the resource to the resource cache. This already existed for the validate kwarg as well. What are your thoughts?

@aaraney - sorry for the slow response.  I suggest adding the use_cache parameter with a default of True to create and pass that parameter to resource.

@aaraney - sorry for the slow response. I suggest adding the use_cache parameter with a default of True to create and pass that parameter to resource.

No worries, sorry I am just now getting around to this myself. As you will see above, I added use_cache to HydroShare.create as requested. With that, are we ready to merge? If you'd like me to bump the minor package version, im happy to do that as well.

Thanks @aaraney.  I'll do the minor bump when I do the release.  I really need to update the release action to use the version given with the github release eventually.


WIP: Start blog post on execution client architecture

This will be superseded by https://github.com/ethereum/portal-website/pull/38 and will be re-written once that is merged


Überscript, squashed

This is a continuation of #114, with bugfixes, squashed down, docs moved inline, etc.

Action items from today's call:

Remove dependency on boto/etc in adam_gatk_pipeline
Clean up spurious diffs in final PR in tertiary pipelines
Remove job encapsulation
Remove argument validation for jobstore

@hannes-ucsc will add something about spot tentative

Everyone, read second bullet of https://github.com/BD2KGenomics/toil/wiki/Python-Dos-and-Don'ts.

Everyone, read second bullet of https://github.com/BD2KGenomics/toil/wiki/Python-Dos-and-Don'ts.

Ah, good to know. I haven't used python logging libraries much before, so I didn't realize they were variadic.

And don't do from foo import * unless foo has an __all__

Which part of the code is this in reference to? The adam_gatk_pipeline? That code path doesn't seem to work with explicit imports due to what I think is some sort of serialization issue I've mentioned earlier.

And don't do from foo import * unless foo has an __all__

Which part of the code is this in reference to? The adam_gatk_pipeline? That code path doesn't seem to work with explicit imports due to what I think is some sort of serialization issue I've mentioned earlier.

Nevermind; figured it out from https://github.com/fnothaft/toil-scripts/pull/7.

Pushed an update with the fixes discussed earlier today. I will test and remove the needs work tag.

Just pushed a new commit with additional fixes from testing tonight. Mostly around error checking on the cgcloud grow-cluster call. Also, there's something that I think is an off-by-one error RE: the desired cluster size. I've got these fixes running now and will report back later as to whether they are sufficient.

 This seems to make the process of waiting for spot instances get really long. How well did this approach work on the RNA-seq recompute?

Hrmmm...
So, something we didn't consider: what do we do when running a spot instance based cluster, and we lose the Spark master? We just had that happen on my test cluster, and alas, as is designed now, I am afraid the cluster is unrecoverable because there is no way to change the master IP that the workers are looking at.
Argh!!!
I'm going to take my test cluster down for now. We'll need to think about this further...

Also, the --spot-tentative flag can't be working right. I just logged into the AWS console and... we have 95 machines running, most of which are spot instances that we gave up on.

@hannes-ucsc I've just pushed the commit we discussed.

 This seems to make the process of waiting for spot instances get really long. How well did this approach work on the RNA-seq recompute?

--quick and --spot-tentative should make cgcloud grow-cluster return much quicker. We can discuss the 5 minute wait. The reasoning is that unless all instances were provisioned, there is no need to retry to provision the rest of them immediately.

For TCGA, we were adding a 100 instances at a time. If the grow_cluster() function is called for each sample then that might slow overall provisioning down. But I don't think it is.

For TCGA, we were adding a 100 instances at a time. If the grow_cluster() function is called for each sample then that might slow overall provisioning down. But I don't think it is.

It is being called per sample. I think it should be straightforward to batch.

Ping @hannes-ucsc can we get this merged or did you want any more changes?


Added missing word 'of'

This tiny PR adds a missing word from the opening sentence of this doc.

@thefisk : Thanks for your contribution! The author(s) have been notified to review your proposed change.


onnxruntime_genai.models.builder script produces model with incorrect tokenizer schema

Describe the bug
When using the onnxruntime_genai.models.builder script to generate an ONNX model from a model on Hugging Face, I cannot run the model, as the tokenizer is invalid JSON.
To Reproduce
Example using microsoft/Phi-3-mini-4k-instruct

Install dependencies

pip install numpy
pip install --pre onnxruntime-genai
pip install torch transformers onnx "huggingface_hub[cli]"

Log in to Hugging Face

huggingface-cli login

Convert microsoft/Phi-3-mini-4k-instruct to ONNX

python -m onnxruntime_genai.models.builder -m microsoft/Phi-3-mini-4k-instruct -o phi3 -p int4 -e cpu

Run ONNX model using onnxruntime_genai

curl https://raw.githubusercontent.com/microsoft/onnxruntime-genai/main/examples/python/phi3-qa.py -o phi3-qa.py
python phi3-qa.py -m phi3

Error

Traceback (most recent call last):
  File "/home/azureuser/phi3-qa.py", line 93, in <module>
    main(args)
  File "/home/azureuser/phi3-qa.py", line 13, in main
    tokenizer = og.Tokenizer(model)
RuntimeError: [json.exception.type_error.302] type must be string, but is array

Expected behavior
The phi3-qa.py script should start without any errors.
Desktop (please complete the following information):

OS: Ubuntu 20.04.6 LTS - Standard_NV12s_v3

Additional context
Comparing tokenizer.json in the generated ONNX model against tokenizer.json present in the microsoft/Phi-3-mini-4k-instruct-onnx model on Hugging Face, it appears that the difference lies in .model.merges, where it is a list of list of strings, rather than a list of strings.

This is a known issue from Hugging Face's transformers package. Suggested workarounds are listed here and in the troubleshooting section.

Thanks a lot. happy to close


pls check the issue regarding android application

adroid application cryptobullcoin are always no connection status even if i have a strong and stable internet connection i cant view and transfer my bullcoin to pc wallet or exchanger pls update asap thanks

#12
The same question at, please check


Updated docs on running tests in README

Closes #280.
So an interesting problem I experienced whilst running the test suite was the following error.
03 01 2016 20:30:57.130:DEBUG [plugin]: Loading karma-* from /usr/local/lib/node_modules
03 01 2016 20:30:57.135:DEBUG [plugin]: Loading inlined plugin (defining launcher:Chrome_travis_ci).
03 01 2016 20:30:57.137:WARN [preprocess]: Can not load "browserify", it is not registered!
  Perhaps you are missing some plugin?
03 01 2016 20:30:57.141:WARN [reporter]: Can not load "mocha", it is not registered!
  Perhaps you are missing some plugin?
/usr/local/lib/node_modules/karma/node_modules/di/lib/injector.js:9
      throw error('No provider for "' + name + '"!');
      ^

Error: No provider for "framework:browserify"! (Resolving: framework:browserify)

After digging around some issues in the karma-browserify repo, the solution ended up being running the command as $(npm bin)/karma. Leaving this as a note to all who may experience similar issues.
cc: @jdfreder

Thanks @captainsafia !


[W04] add testcases where key1.equals(key2) but key1 != key2

Checklist
General

[x] I confirm that my tests, if any, are correct

[x] Optional: I pass all artemis tests.
[x] Optional: I pass all tests, that are added in this PR.
[ ] Optional: I calculated manually the correct solutions on paper.

[x] I chose a title conforming to the naming conventions for pull requests.
[x] The newly added tests do not reveal the solutions dynamically calculating the solutions as expected in the exercise.
[ ] Other students approved this Pull Request.

Description

Keys that are equal but not the same object should be treated correctly. e.g. Interned Strings...

Thanks for reviewing

Your PR title must be capitalized to fit the checks ([W04]). Other than that well done, LGTM.

Yeahyeah amigo, I know that... happens all the time :(

Yeahyeah amigo, I know that... happens all the time :(

feel you, i always have to double check :(


Fix CI for Swift 5.3

Motivation
The Swift 5.3 CI currently fails with the error:
ERROR:  Error installing jazzy:
	The last version of jazzy (>= 0) to support your Ruby & RubyGems was 0.13.7. Try installing it with `gem install jazzy -v 0.13.7`
	jazzy requires Ruby version >= 2.6.3. The current ruby version is 2.5.0.

Example log: https://ci.swiftserver.group/job/async-http-client-swift53-prb/338/console
Changes

Explicitly set jazzy version number

Result
Happy Swift 5.3 CI

last version is 1.2.3...

last version is 1.2.3...
https://swift-server.github.io/async-http-client/docs/current/AsyncHTTPClient/index.html

Ah, cool, I didn't realise we published them at some point. I guess @tomerd will have some insight on why the last version is 1.2.3.


Customer informed that documentation is incorrect - Embarassing situation

Documentation link - https://docs.microsoft.com/en-us/power-bi/collaborate-share/service-embed-report-spo#known-issues-and-limitations

As per one of the known limitations mentioned in the doc, the feature is not available for national cloud which seems to be out of date information

As per documentation, we advised to customer like that but the customer responded that the feature is indeed available for national clouds and he was able to implement it

Please review and change the documentation for accuracy

Updated documentation myself (pending review)


Create room within signaling server

For example, User A opens a rooms. User B, User C and User D joins, everything is fine. However, when User A leaves, he cannot rejoin in the room and other users cannot enter.
I'm thinking that one way to solve this is by creating the room within the signaling server. We need something that the room is open forever and all users in the room can just join and leave as they want.
How to solve this?
Thanks

+1

webRTC is peer to peer. It makes sense that if the host leaves, the room goes with him. Hosting the room on the signaling server defeats the purpose of p2p. A better solution would be to have the host and guests switch to someone who is already in the room. You should be able to implement that yourself.
Host Leave -> other users detect host leaves -> select new host -> host spins up room -> others join

Thank you. Do you have an idea how I can achieve this? I will try to do this but I will appreciate if you can provide me a source code on how to make this happen.
Thanks

Any solutions to this yet? Its not working. Moderator can't join the room again. Instead it creates the room again with same name.

    beforeOpenOrJoin(roomid, function() {       connection.checkPresence(roomid, function(isRoomExist, roomid) {         // join callback         if (isRoomExist === true) {           connection.join(roomid);         } else {           connection.open(roomid);         }         afterOpenOrJoin();       });     });
You can use connection.checkPresence function to check if room is available or not . If it is available you can join the room else create a new one ..
On upon leaving room use this code.
`  // disconnect with all users
connection.getAllParticipants().forEach(function(pid) {
connection.disconnectWith(pid);
});
// stop all local cameras
connection.attachStreams.forEach(function(localStream) {
  localStream.stop();
});

// close socket.io connection
connection.closeSocket();`

This will close the socket connection of moderator and he can join the room again.

This issue is solved since 3.4.7.  Ref: https://github.com/muaz-khan/RTCMultiConnection/commit/7e35a011c305696fe0d932c2c0edd1dae0be04ad (and all upcoming commits)
NPM package or git clone is recommended to fetch/get latest release. Current version is 3.5.2.
Signaling-server is also isolated to be installed separately, if needed.


fix: use buildPackages.xsltProc in case of cross compilation

Motivation for this change
Fix cross compilation of fontconfig.
See: https://github.com/NixOS/nixpkgs/issues/50801
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

This is very interesting.
Indeed, every instance of ${somePackage.bin}/an-elf defined in postInstall should be replaced accordingly. What else?

@eburimu why was this closed?


Scala 2.13 support

I'm not sure which dependencies are missing, but 2.13 things are showing up now...

@hseeberger please turn on @scala-steward updates for jsoniter-scala, it supports Scala 2.13-RC1 already:
http://repo1.maven.org/maven2/com/github/plokhotnyuk/jsoniter-scala/jsoniter-scala-macros_2.13.0-RC1/

PR please, I‘m on vacation 😉

PR: https://github.com/hseeberger/akka-http-json/pull/281

upickle dropped support for 2.11 when it introduced support for 2.13 in 0.7.5: https://mvnrepository.com/artifact/com.lihaoyi/upickle
@hseeberger are you OK with dropping support for 2.11 when 2.13 is added?

@2m It is not OK to drop 2.11, it is a MUST! ;-)
Couple of days ago I already looked into bumping the Scala version to 2.13, but some libraries like Circe had not yet been there.

Is any option to release selected modules for those libraries that were already released for Scala 2.13?

@plokhotnyuk that is indeed an option, let's do it.

PR incoming.

Closed by #297.


Parse failure where + reduce(.) is used

Not sure if this has to do with reduce, but jq works with this, whereas gojq can't parse it.  FWIW, using a locally defined function def pass: .; instead of the reduce will parse.
# cat x.jq
. as $rec | foreach . as $c ({};
  $c | . +
  reduce(.) as $k ({}; .) |
  . += {"qq": "baz"} )

# echo '{"foo": "bar"}' | jq -f x.jq
{
  "foo": "bar",
  "qq": "baz"
}

# echo '{"foo": "bar"}' | ./gojq -f x.jq
gojq: invalid query: x.jq:2
    2 |   $c | . +
                 ^  unexpected "+" (expected ")")

This issue has been fixed for now.


Add 0.1.0 release documentation

Create release notes for the 0.1.0 release.
Update project documentation as needed. Look particularly at https://github.com/eclipse-pass/main/blob/main/docs/dev/release.md

https://github.com/eclipse-pass/main/blob/main/docs/dev/release.md has been updated with full details for performing both snapshot and version releases


Support for bitcoin testnet listunspent and rawsubmit via chain.so

I've added support for bitcoin testnet using chain.so as it's already used for multiple coins.

I'm getting this error when I want to load unspent outputs from an bitcoin testnet address:
"Unexpected error, unable to retrieve unspent outputs!"

Unfortunately chain.so closed their API in August 2019.  Coinbin has been updated to support two additional backends: blockcypher and blockchair.  There is https://github.com/OutCast3k/coinbin/pull/196 to support bitcoin testnet via blockcypher.


feat: Shiny new ES module builds

Summary
This PR will expose ES module code into the published libraries under dist/esm.
Test plan
Needs to make sure there are builds being produced from the ES modules and not the umd code.

[ ] Test main bundle to make sure everything is included, because there was a 20% size drop
[ ] Make sure all the bundles are creating valid module builds. A good test would be to use rollup to do a full build from the published libraries.
[ ] Check to make sure all exports and peers working properly on bundles.

A picture of a cute animal (not mandatory but encouraged)
🐉

This is incredible @talves!!!

Webpack analyzer outputs:

2.6.1
master without this PR
this PR

@erquhart testing the building off of esm published libraries:
The following code does not get replaced, because it is a webpack replacement.
The esm build could use the transform babel-plugin-transform-define and pull the version from the config. I will do this to move my test forward and we can discuss.
.
From:
  /**
   * Log the version number.
   */

  if (NETLIFY_CMS_VERSION) {
    console.log(`netlify-cms ${NETLIFY_CMS_VERSION}`);
  } else if (NETLIFY_CMS_CORE_VERSION) {
    console.log(`netlify-cms-core ${NETLIFY_CMS_CORE_VERSION}`);
  }

To:
  if ("esm-v2.6.2-beta.0") {
    console.log(`netlify-cms ${"esm-v2.6.2-beta.0"}`);
  } else if ("esm-v2.8.1-beta.0") {
    console.log(`netlify-cms-core ${"esm-v2.8.1-beta.0"}`);
  }

Also, here is the code reference from the NumberConrol.js widget that breaks an esm import to outside linking. This needs to be fixed and decision made on how we want to handle.
My proposal is below:
From:
import ValidationErrorTypes from '

To:
const ValidationErrorTypes = {
  PRESENCE: 'PRESENCE',
  PATTERN: 'PATTERN',
  RANGE: 'RANGE',
  CUSTOM: 'CUSTOM'
}

@erquhart I got it!!! The test for building off the ES modules PR is working using parcel!
https://github.com/talves/netlify-cms-parcel-example
https://cms-parcel-example.netlify.com
✨✨🚀🔥
Build log: https://app.netlify.com/sites/cms-parcel-example/deploys/5c9168baf448f80008be2ea1
That pretty much tests the builds 100%, because it used the dist/esm builds to get the modules for the build. The bundles are better now for parcel and takes the right amount of time 93s vs 383s on umd builds. Also the bundle dropped in size appropriately. Great stuff!

Tony this is crazy awesome, can't wait to get it merged. Anything you need from me? I know you mentioned some odds and ends in chat, but wanted to get specifics here so I don't lose track. UMD builds already made releases and the app itself faster, ready to go all the way!

I have been getting some weird side affects when trying to bring these modules into a CRA app.
I am not sure if this is just a devServer isssue in CRA, so I may eject and try it on a branch. If I do a production build things work fine. It is worrying me that we might have some issues with these builds, because I have not tested every little thing in the parcel build.

So, If we bring this into master, I am afraid we will get stuck in beta until these things are ironed out. What are your thoughts?

@erquhart OMG. It just occurred to me that this might just be an issue with my fs backend and the new api changes! I will check that tonight!

@erquhart (and others) Sorry for all the spamming. It WAS the fs backend that needed to be updated for the api changes for media! There are so many moving parts that I was getting caught up in misreading the errors as issues with the esm builds using ref=. Although we will need to address these eventually, just not required for this release.
Although there are errors showing up during development, most are the ref warnings and prop-types that we can deal with as we go. They have always been there, just more apparent now with the new version of React and developing from a transpiled version.
One more successful test: A full create-react-app example using the ES modules
Included in the test...

uses all the test data from the test-repo backend, but setup for the file-system backend.
tests the ability to run a backend registered and built outside of the cms using react hooks.
All the custom previews converted to use React Hooks for testing the single instance of React!
imports the libraries individual for now, until we decide what to do with providing a BARE library or not. But this was a good test.

I would like to release this as beta soon also, so we can make sure the github, git-gateway backends are all working properly.
What a relief it was to get this version of tests up and running. 🚀


Let the user know that there is an ongoing operation during async operations

What problem are you facing?
If we encounter a problem during an async operation, we report it in the AsyncOperation condition. However, this informs user about only the last operation error like the following:
  conditions:
  - lastTransitionTime: "2021-10-12T16:01:21Z"
    reason: ReconcileSuccess
    status: "True"
    type: Synced
  - lastTransitionTime: "2021-10-12T16:04:34Z"
    message: '{"@level":"error","@message":"Error: Error creating DB Instance: DBParameterGroupNotFound:
      DBParameterGroup not found: example-dbparametergroup\n\tstatus code: 404, request
      id: 7cbae0b0-6d1d-4b21-859e-e103fd9bd01f","@module":"terraform.ui","@timestamp":"2021-10-12T19:03:38.109151+03:00","diagnostic":{"severity":"error","summary":"Error
      creating DB Instance: DBParameterGroupNotFound: DBParameterGroup not found:
      example-dbparametergroup\n\tstatus code: 404, request id: 7cbae0b0-6d1d-4b21-859e-e103fd9bd01f","detail":"","address":"aws_db_instance.example-dbinstance","range":{"filename":"main.tf.json","start":{"line":1,"column":734,"byte":733},"end":{"line":1,"column":735,"byte":734}},"snippet":{"context":"resource.aws_db_instance.example-dbinstance","code":"{\"provider\":{\"tf-provider\":{\"access_key\":\"REDACTED\",\"region\":\"us-east-1\",\"secret_key\":\"REDACTED\",\"token\":\"\"}},\"resource\":{\"aws_db_instance\":{\"example-dbinstance\":{\"allocated_storage\":20,\"auto_minor_version_upgrade\":true,\"backup_retention_period\":14,\"backup_window\":\"09:46-10:16\",\"engine\":\"postgres\",\"engine_version\":\"12.4\",\"identifier\":\"example-dbinstance\",\"instance_class\":\"db.t2.micro\",\"lifecycle\":{\"prevent_destroy\":true},\"maintenance_window\":\"Mon:00:00-Mon:03:00\",\"name\":\"example\",\"parameter_group_name\":\"example-dbparametergroup\",\"password\":\"testPassword!123\",\"publicly_accessible\":false,\"skip_final_snapshot\":true,\"storage_encrypted\":false,\"storage_type\":\"gp2\",\"username\":\"adminuser\"}}},\"terraform\":{\"required_providers\":{\"tf-provider\":{\"source\":\"hashicorp/aws\",\"version\":\"3.56.0\"}}}}","start_line":1,"highlight_start_offset":733,"highlight_end_offset":734,"values":[]}},"type":"diagnostic"}'
    reason: ApplyFailure
    status: "False"
    type: AsyncOperation
  - lastTransitionTime: "2021-10-12T16:01:21Z"
    reason: Creating
    status: "False"
    type: Ready

If user fixes the error and then the apply operation for example continues successfully, the error is still there until that operation finishes and users don't have a clear way of knowing that they fixed the problem.
How could Terrajet help solve your problem?
We cannot re-use the same condition to notify about the new operation because that would mean deleting the error in every reconcile and writing a new one. So, we need a way to let the user know that there is a new operation begun since the last error we show.

A separate condition & an event that marks the beginning of the current operation would probably help here.


Timeout scanning low cardinality unindexed column in large table

When scanning a column to determine if it's low cardinality, DataHerald runs SQL:
SELECT DISTINCT col_name FROM table_name LIMIT 200;

That query does a full table scan if the column is low cardinality and not indexed, which times out on a large table. DataHerald catches the timeout as an error and assumes the column is not low cardinality.

For PostgreSQL at least we could avoid this and make scanning much faster by reading the query planner statistics from the pg_stats view:
SELECT n_distinct FROM pg_stats WHERE tablename = 'table_name' AND attname = 'col_name';

That query returns instantly regardless of the size of the table. Probably similar statistics are available in some other databases.

Is there any interest in making this change for PostgreSQL?
I could see a fair argument that if these columns aren't indexed then they shouldn't be treated as low-cardinality columns for query generation purposes anyway, but when running against a legacy database sometimes adding indexes isn't an option.

Hello,
You're absolutely correct. We do indeed have a ticket to enhance the cardinality logic, and we plan to implement an optimized solution for each database system. As you suggested, we should utilize 'pg_stats' specifically for Postgres.
If you're interested in contributing, please feel free to make these changes for Postgres and create a pull request (PR). Otherwise, rest assured that we will be making this change in the near future.
Best regards,

Thanks for the quick response! I may be able to contribute. Do you have any general guidance for what this code should look like, or how you'd like to architect database-specific code?

Because the process of scanning a table does not occur often and scanning tables is nicely done in parallel asynchronously , it is not a show stopper. We have tables with almost a billion rows with low-cardinality columns that are not indexed (didn't make much sense to index) that do take a few minutes (enough to grab a coffee) but still the process doesn't crash.
This is the code that you're talking about I think using sqlalchemy.
try:
    cardinality_query = sqlalchemy.select([func.distinct(dynamic_meta_table.c[column["name"]])]).limit(200)
    cardinality = db_engine.engine.execute(cardinality_query).fetchall()
except Exception:
    return ColumnDetail(
        name=column["name"],
        data_type=str(column["type"]),
        low_cardinality=False,
    )

etc.,...

I wanted to ask what you mean by using pg_stats for PostgreSQL and how this would be implemented.
pg_stats is not compatible with other SQL flavours but there are basically equivalents.

pg_stats is a system view provided by PostgreSQL to access the query planner statistics. We would query it using the SQL I posted above. It will be PostgreSQL-specific of course. Hopefully I will be able to provide a PR soon.

@roy-moven Hello, I apologize for the delayed response. Our goal is to establish adapter classes for each supported database system to maintain clean and modular code. Since this marks our inaugural integration with Postgres, it's acceptable to implement a conditional statement. If the driver indicates that the database is Postgres, we should execute the pg_stats query; otherwise, we can maintain the current behavior.
You can add the logic in the method called get_processed_column in the sqlalchemy.py file.
Use the next condition:
if db_engine.engine.driver == 'psycopg2':     <your logic>
To debug the code I use this line:
import ipdb; ipdb.set_trace()
and while the docker containers are running I execute this
docker attach <app-container-id>
Please let me know if you have any question.

Yep that was my plan. I'll try to quickly get something working and leave it to you to make the architecture elegant later.