CPU memory increase while training

During the training step, the code block:
for blk in self.v.blocks:
x = blk(x)
causes an increase in CPU memory, eventually leading to full CPU memory.  What is you cpu/gpu memory?
x = blk(x) means the input tensor passes a Transformer layer, it should take GPU memory. I don't know how torch manages cpu memory in this case.
-Yuan

i am using my own training code but following the ast_models.py code to define ASTModel.
i can see from the memory_profiler, at line 174 of screenshot, my htop cpu memory linearly increase while trianing step.

--> This is part of my code.
class ASTModel(nn.Module):
"""
The AST model.
:param label_dim: the label dimension, i.e., the number of total classes, it is 527 for AudioSet, 50 for ESC-50, and 35 for speechcommands v2-35
:param fstride: the stride of patch spliting on the frequency dimension, for 1616 patchs, fstride=16 means no overlap, fstride=10 means overlap of 6
:param tstride: the stride of patch spliting on the time dimension, for 1616 patchs, tstride=16 means no overlap, tstride=10 means overlap of 6
:param input_fdim: the number of frequency bins of the input spectrogram
:param input_tdim: the number of time frames of the input spectrogram
:param imagenet_pretrain: if use ImageNet pretrained model
:param audioset_pretrain: if use full AudioSet and ImageNet pretrained model
:param model_size: the model size of AST, should be in [tiny224, small224, base224, base384], base224 and base 384 are same model, but are trained differently during ImageNet pretraining.
"""
def init(self, label_dim=527, input_fdim=128, input_tdim=1024, imagenet_pretrain=True, audioset_pretrain=False, model_size='base384', verbose=True):
    super(ASTModel, self).__init__()
    assert timm.__version__ == '0.4.5', 'Please use timm == 0.4.5, the code might not be compatible with newer versions.'

    if verbose == True:
        print('---------------AST Model Summary---------------')
        print('ImageNet pretraining: {:s}, AudioSet pretraining: {:s}'.format(str(imagenet_pretrain),str(audioset_pretrain)))
    # override timm input shape restriction
    # timm.models.vision_transformer.PatchEmbed = PatchEmbed

    # if AudioSet pretraining is not used (but ImageNet pretraining may still apply)
    if audioset_pretrain == False:
        if model_size == 'tiny224':
            self.v = timm.create_model('vit_deit_tiny_distilled_patch16_224', pretrained=imagenet_pretrain)
        elif model_size == 'small224':
            self.v = timm.create_model('vit_deit_small_distilled_patch16_224', pretrained=imagenet_pretrain)
        elif model_size == 'base224':
            self.v = timm.create_model('vit_deit_base_distilled_patch16_224', pretrained=imagenet_pretrain)
        elif model_size == 'base384':
            self.v = timm.create_model('vit_deit_base_distilled_patch16_384', pretrained=imagenet_pretrain)
        else:
            raise Exception('Model size must be one of tiny224, small224, base224, base384.')

def get_shape(self, fstride, tstride, input_fdim=128, input_tdim=1024):
    test_input = torch.randn(1, 1, input_fdim, input_tdim)
    test_proj = nn.Conv2d(1, self.original_embedding_dim, kernel_size=(16, 16), stride=(fstride, tstride))
    test_out = test_proj(test_input)
    f_dim = test_out.shape[2]
    t_dim = test_out.shape[3]
    return f_dim, t_dim

@autocast()
def forward(self, x):
    """
    :param x: the input spectrogram, expected shape: (batch_size, time_frame_num, frequency_bins), e.g., (12, 1024, 128)
    :return: prediction
    """
    # expect input x = (batch_size, time_frame_num, frequency_bins), e.g., (12, 1024, 128)
    # x = x.unsqueeze(1)
    # x = x.transpose(1, 2)

    B,T,F = x.shape
    # x = self.v.patch_embed(x)
    cls_tokens = self.v.cls_token.expand(B, -1, -1)
    dist_token = self.v.dist_token.expand(B, -1, -1)
    x = torch.cat((cls_tokens, dist_token, x), dim=1)
    x = x + self.v.pos_embed
    x = self.v.pos_drop(x)
    for blk in self.v.blocks:
        x = blk(x)
    x = self.v.norm(x)

--> i am only utilizing pretrained raw vit_deit_tiny_distilled_patch16_224 without changing patch embedding or positional encoding.
class LSQSL(nn.Module):
# def init(self, in_chans=1, frequency=129, d1_model=32, d2_model=172, n_layers=1, hidden_size=88, bidirectional=True):
def init(self, in_chans=1, time=29, frequency=129, n_seq=10, seq_length=20, d1_model=32, d2_model=128, n_layers=1, hidden_size=64, bidirectional=True, head_num=2):
super(LSQSL, self).init()
    self.ast_mdl = ASTModel(label_dim=5, \
     input_fdim=192, input_tdim=196, \
     imagenet_pretrain=True, audioset_pretrain=False, \
     model_size='tiny224')
def forward(self, raw):
    B, L, D = raw.shape

    raw = self.ast_mdl(raw)

    return raw

-->   i use GPU for training with (model = LSQSL.to(device)).
but the blk(x) increase my htop cpu memory linearly increase.
when i track the code until /python3.7/site-packages/timm/models/vision_transformer.py,
in the Block class, self.attn and self.mlp operation increase the cpu memory.
def forward(self, x):
x = x + self.drop_path(self.attn(self.norm1(x)))
x = x + self.drop_path(self.mlp(self.norm2(x)))
return x
class Mlp(nn.Module):
def init(self, in_features, hidden_features=None, out_features=None, act_layer=nn.GELU, drop=0.):
super().init()
out_features = out_features or in_features
hidden_features = hidden_features or in_features
self.fc1 = nn.Linear(in_features, hidden_features)
self.act = act_layer()
self.fc2 = nn.Linear(hidden_features, out_features)
self.drop = nn.Dropout(drop)
def forward(self, x):
    x = self.fc1(x)
    x = self.act(x)
    x = self.drop(x)
    x = self.fc2(x)
    x = self.drop(x)
    return x

class Attention(nn.Module):
def init(self, dim, num_heads=8, qkv_bias=False, qk_scale=None, attn_drop=0., proj_drop=0.):
super().init()
self.num_heads = num_heads
head_dim = dim // num_heads
# NOTE scale factor was wrong in my original version, can set manually to be compat with prev weights
self.scale = qk_scale or head_dim ** -0.5
    self.qkv = nn.Linear(dim, dim * 3, bias=qkv_bias)
    self.attn_drop = nn.Dropout(attn_drop)
    self.proj = nn.Linear(dim, dim)
    self.proj_drop = nn.Dropout(proj_drop)

def forward(self, x):
    B, N, C = x.shape
    qkv = self.qkv(x).reshape(B, N, 3, self.num_heads, C // self.num_heads).permute(2, 0, 3, 1, 4)
    q, k, v = qkv[0], qkv[1], qkv[2]   # make torchscript happy (cannot use tensor as tuple)

    attn = (q @ k.transpose(-2, -1)) * self.scale
    attn = attn.softmax(dim=-1)
    attn = self.attn_drop(attn)

    x = (attn @ v).transpose(1, 2).reshape(B, N, C)
    x = self.proj(x)
    x = self.proj_drop(x)
    return x

--> However, Mlp and Attention class foward have nothing related about cpu operation or stack of  trash variables as detach() or append(). Do u know the reason of this unexpected CPU memory leack? i am only suspecting the timm library own Issues.

What's your GPU memory and CPU memory?
Have you tried to use our recipe (e.g., ESC-50, which is very fast to run, see our Readme) and see if the issue is still there?
This is the first time I heard this issue.

I also see this memory leak from your ESC-50 training code also. but, not as much as mine. I think the difference from mine is sequence length. I use original 198 sequence length with much more attention computation.

I am using
GPU: NVIDIA A100-PCIE-40GB, and
CPU:
Architecture:            x86_64
CPU op-mode(s):        32-bit, 64-bit
Address sizes:         46 bits physical, 48 bits virtual
Byte Order:            Little Endian
CPU(s):                  48
On-line CPU(s) list:   0-47
Vendor ID:               GenuineIntel
Model name:            Intel Xeon Processor (Skylake, IBRS)
CPU family:          6
Model:               85
Thread(s) per core:  1
Core(s) per socket:  1
Socket(s):           48
Stepping:            4
BogoMIPS:            6185.46
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid tsc_k
nown_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti
ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec
xgetbv1 arat pku ospke avx512_vnni md_clear
Virtualization features:
Hypervisor vendor:     KVM
Virtualization type:   full
Caches (sum of all):
L1d:                   1.5 MiB (48 instances)
L1i:                   1.5 MiB (48 instances)
L2:                    192 MiB (48 instances)
L3:                    768 MiB (48 instances)
NUMA:
NUMA node(s):          1
NUMA node0 CPU(s):     0-47
Vulnerabilities:
Gather data sampling:  Unknown: Dependent on hypervisor status
Itlb multihit:         KVM: Mitigation: VMX unsupported
L1tf:                  Mitigation; PTE Inversion
Mds:                   Mitigation; Clear CPU buffers; SMT Host state unknown
Meltdown:              Mitigation; PTI
Mmio stale data:       Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
Retbleed:              Mitigation; IBRS
Spec rstack overflow:  Not affected
Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2:            Mitigation; IBRS, IBPB conditional, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
Srbds:                 Not affected
Tsx async abort:       Mitigation; Clear CPU buffers; SMT Host state unknown

Thank you for answering my questions. It was not any problem of the timm library or the AST codes.
While training, there was a tensor operation without using .item() such
<running_loss += loss>
So i changed it to
<running_loss += loss.item()>
and RAM memory leak was fixed!

thanks for letting me know. Good luck with your research!


feature: Tooltip Target HtmlElement

Adding the option to provide an HtmlElement as Tooltip target.
This is my take on issue #395 and maybe #387 as well.

Thanks @kaipaysen !, looks good but let me review more closely soon.  Started a new role and some delay in sveltestrap issues.

I think the merge of this PR is what introduced the bug #414


add functionality to allow low power operation for STM32L1xx

get sleep mode from BSP (WFI or STOP)
allow BSP to deinit/init board peripherals when enter/exit sleep via callback
allow BSP to deinit/init MCU peripherals if mynewt core code does not have this functionality
use RTC during sleep instead of systick (tickless operation)
restart PLL clock when returning from STOP mode

In this form it even automatic style checker give up.
It's hard to decide which part was actually added or changed by this PR.
Watchdog interval does not belong here.
There are conflicts reported by hithub anyway.
I would prefer to have this code rebased, maybe there is no 155 files to review after all.

It's hard to decide which part was actually added or changed by this PR.
Watchdog interval does not belong here.
There are conflicts reported by hithub anyway.
I would prefer to have this code rebased, maybe there is no 155 files to
review after all.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/mynewt-core/pull/2224#issuecomment-615286276,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMIHRIDCU5AN2BZVEYLPNHDRNBTWZANCNFSM4LAKTJ4A
.


Automatic diagnosis and (potential) action on stuck rules that are holding up workflows

Impact of the new feature
Create a way for WM monitoring to more actively detect issues with rules that are preventing workflow completion
Is your feature request related to a problem? Please describe.
There are a number of common issues that cause rules to be stuck that are also relatively simply diagnosed or fixed (a file has no replicas, or the source replica is corrupt).
Describe the solution you'd like
Implement logic into workflow monitoring that is able to detect those rules that have these simple issues and alert DM operators. In the future, could potentially upgrade for automatic action.
Additional context
See https://github.com/dmwm/WMCore/issues/11220 for context on efforts to streamline instances where a new rule needs to be created to fix the workflow.

@cmoore24-24 Hi Connor, thanks for creating this issue.
Do you think you could describe one or two scenarios that you would like to cover within this GH issue? If so, feel free to update the initial description of this issue.
If you think you have a 3rd or 4th scenario that you would like to work on during this week, that's fine as well. Otherwise, we could make more GH issues such that we can break those scenarios into different developments (easier to track and accomplish work).

Hi @amaltaro, I've updated the request with the most important scenarios we discussed the other day. Let me know if there's any others you think would be helpful to add.

Discussed with Alan: Probably worth waiting on implementing any autonomous code until other projects are completed.


test change

just a test

Fixed languagetool not finding typos. ^^
It's unclear how well it will behave on real world use-cases, this setup is very experimental so I will play with it more.
Some of the potential issues I noticed:

We have limitations on the api and checking power: https://dev.languagetool.org/public-http-api
Action is 'In progress' for 20mins already, unsure if it's broken.
Not sure how well it will work on the code and markdown, although all checks that would trigger on code syntax are disabled, like underscores and similar.

Action is erroring out with 'Only 65535 characters are allowed; 97549 were supplied. []', because the request is too large for github's liking.
I believe changing reporter to github-pr-review might solve this problem.
I think review comments are much better anyway, because we can discuss if it's a real mistake or something that should be ignored. If it could suggest fixes that you can merge from the UI, it would be a really nice experience.
Also, with review comments, you can 'resolve' them to hide them from the review UI, so it's not cluttering everything.
Currently, it looks like this:

It didn't crash, seems to be working well now. :relaxed:

the reason i didnt go with that setting it is bc people can bypass it by just resolving the convo. so its impossible to make it "required".
but i think it would be fine anyways

Closing this


Double counting between bootstrap and beam driven currents

In GitLab by @hlux on Aug 22, 2018, 08:57
From Richard:

I got this reply to a comment/question I made reviewing a paper on the subject of fast-ion pressure contributions to the bootstrap current:
“In principle the fast ion beta does contribute to the bootstrap current. Analytic expressions have been derived for beam ions [e.g., Taguchi1996] and alpha particles [e.g., Hsu1992]. The beam-ion bootstrap current depends on the toroidal injection angle and the ratio of the critical velocity to the birth velocity. For perpendicular injection, Taguchi calculated that the beam-ion bootstrap current is 9% of the bulk (i.e., thermal) bootstrap current at the same pressure gradient. In this paper, these analytic expressions are not utilized, however, as the current
drive determined by the orbit-following Monte Carlo code NUBEAM includes all sources of fast-ion current. That is, NUBEAM does not distinguish between what we might call NBCD and what we might call fast-ion bootstrap current."
In other words, we may be making an erroneous division between beam-driven current and beta-driven bootstrap current, if in PROCESS we scale the beam-driven current to match the output of e.g. NUBEAM. So the bootstrap model in PROCESS – if this is the case – should include contributions from fusion-born alphas, but not from auxiliary-power driven fast ions IF the NUBEAM approach is generalised across the current drive codes we benchmark against. We should be careful not to double-count current contributions.
This may help explain some of the past discrepancies between the PROCESS bootstrap model and other models.

@mkovari , @jmorris-uk , @stuartmuldrew and @kellis (for your information and to keep in mind, when we are implementing any new beam models into e.g. PLASMOD, because I don't know when we would have benchmarked against NUBEAM in the past.)

There are actually two separate topics here.

Does the Process bootstrap model include contributions from fusion-born alphas, and should it?  I suspect the answer is no, since the alphas don't explicitly contribute to the temperature and density distributions (although you could say they are included if you wanted to).
Does the Process bootstrap model include contributions from auxiliary-power driven fast ions and should it?

We don't often use NBCD (neutral beam current drive) in Process these days, since it is not included in the STEP or EU-DEMO scenarios.
We don't understand the bootstrap current model in PROCESS anyway, and we may replace it with the one proposed by Sakai et al in #954:

We created a fitting database for the $f_{BS}$ using the ACCOME code.  In this study, equilibria with the fully non-inductively driven conditions with neutral beam (NB) injection only are calculated, where the total plasma current is sustained by NB driven current together with the bootstrap current and the diamagnetic current. Note that the toroidal component of the diamagnetic current $I_{DI}$ was included in $f_{BS}$ in our fitting database; $f_{BS} = (I_{BS} + I_{DI})/I_P$.

The same question will arise - how does ACCOME divide up the current between bootstrap and beam-driven fractions?
Note that Sakai does not include alphas or helium ions at all - the only impurity is carbon.

No replies so I will close the issue.


Usage question: attaching an array and have option elements lazily created?

This may be trivial.
I have a large array and want the select to create the option elements only as necessary - me creating them all up front is too slow.  I saw a few hints that this might be possible with bootstrap-select as it is but I haven't seen that it is fully possible....
thanks!

While the groundwork is laid for dynamic options, there is still some work needed in order to get this to work smoothly. Something like this might point you in the right direction:
$('#number').on('loaded.bs.select', function () {
  var Selectpicker = $('#number').data('selectpicker');

  Selectpicker.$menuInner.on('scroll', function () {
    var scrollTop = Selectpicker.selectpicker.view.scrollTop;

    // if within 100px of the bottom of the menu, load more options
    if ($(this)[0].scrollHeight - Selectpicker.sizeInfo.menuInnerHeight - scrollTop < 100) {
      $('#number').append(newOptions);
      $('#number').selectpicker('refresh');
    }
  });
});

See an example here: https://next.plnkr.co/edit/OAfCYwHVHOArFAz7.

wow thanks! - would the livesearch work on data not yet in an option element?  I looked at the code and this did not seem to be case on a quick look

btw - I had forgotten about jquery ui's autocomplete, where you can pass it the array and it just adds things as necessary based on what you typed

It's not yet possible to use live search to search for options not yet in the array. You'll want to follow #1305. How many options would there potentially be? With bootstrap-select v1.13.2 and the virtualScroll option, thousands of options render much faster than in previous versions.

it seems like first just creating > 10,000 option elements alone is the bottleneck, before the selectpicker is even instantiated.
jquery's autocomplete is much faster (since it does the lazy load thing from the array you give it) and works, but you don't get a nice look at what's there before you decide to enter a particular search term... which might be incompatible with performance in the first place...

Check out https://github.com/truckingsim/Ajax-Bootstrap-Select in the meantime.

I haven't looked at that plugin too closely, but I think you should be able to simulate an Ajax request and use local data instead.

could also try lazy-loading https://github.com/snapappointments/bootstrap-select/issues/2187

Please 👍 and follow #899.


Toolbar items are too white

When you have a message open, you need to be able to use the toolbar buttons up top (archive, snooze, etc.). Currently they are a bit difficult to view against a very light gray background.
If they could either be darkened or create an option to increase the contrast - that would be beneficial to the usability.

I think you must have dark theme enabled, please try switching back to the default theme in Gmail Settings -> Themes. Dark Theme will eventually be supported, but it will take some time.

Thanks for the tip. While I didn't have the dark theme enabled - I had a background image set. After switching back to the default theme the toolbar buttons look great!


Template exts: Prioritize .twig -> .tpl -> .ctp

I don't know when I find time to setup a local dev env for Twig but this PR requires changes around the tests and possibly test comparison file names.

If you have *nix based system and you have both git and php installed on it you can clone your fork, checkout your branch and run make and that will install all composer dependencies and run the unit tests.

Didn't see the makefile. If you can't do the fixes yourself I will try to squeeze them in yourself.
TLDR:
Makefiles. That's awesome and makes me wonder why https://github.com/cakephp/app doesn't come with such things and - skimmed through https://github.com/cakephp/cakephp/blob/master/Makefile and it seems to do more/complex stuff.

Can do the changes, just not today. Currently at work, and booked in the evening.
Seems that it's mainly a matter of renaming files and update the tests where needed.
Yup makefiles are awesome, and I ship them in nearly all my projects these days :smile: . Mainly as easy use for me, but also to let contributors like you get started quickly.

Is there anyway I can assist with this? Want to see if I can get this out the door today :smile:

I'll be honest I cannot do soon (I am not even using Twig, just planning to and it looks awesome!).
I think just test cases have to be fixed.

Alright no problem, I'll look into it :+1:

FYI #39


Event.keyCode is deprecated

While working on https://github.com/phetsims/scenery/issues/1145, I found that keyCode is no longer supported, and we should start phasing it our for "code" instead.
See https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/keyCode#Browser_compatibility.

duplicate of https://github.com/phetsims/scenery/issues/1053

duplicate of https://github.com/phetsims/scenery/issues/1053


Update setup-infra-gameengine.md

Minor change in wording to clarify

Related to issue https://github.com/azure-adventure-day/aad-team/issues/5


fix broken test runner

https://github.com/Agoric/agoric-sdk/pull/8360 caused errors with Endo lockdown in Ava tests.
This drops the dependencies back to beta which worked.
The contract is still tested against Mainnet 11wf with https://github.com/Agoric/agoric-sdk/pull/8361

obsolete


Delare non secured subcontext within /api/users/v1 not supported

In ResourceAccessControl in identity.xml /api/users/v1 has been declared as a secured context. However, it should be possible to declare a subcontext such as /api/users/v1/webauthn which is not secured. In that case, non secured /api/users/v1/webauthn should receive the precedence, but current implementation doesn't support this no matter what order you use.

This is already fixed with https://github.com/wso2-extensions/identity-carbon-auth-rest/pull/81


feature request: AQL CONTAINS function for arrays

Right now, I need to do something like
INTERSECTION(UNIQUE(myArray), [mySearchValue]) == [mySearchValue]

I'd prefer something like this (for consistency with the CONTAINS function for String)
CONTAINS(myArray, mySearchValue)

There you go:
yourArray ANY == yourSearchValue
Jan implemented the array operators ALL, ANY and NONE 10 days ago (available in devel branch). Have a look here: #1629

Oh cool. Thanks!


[OSD-11460] Address gosec lint warnings

What this PR does / why we need it?
The PR addresses the gosec lint warnings
Which Jira/Github issue(s) this PR fixes?
Fixes # OSD-11460

/approve

/lgtm


[WIP] Improved syntax of docstring in mitigation

Summary
Syntactic fixes in the docstring to improve readability of the documentation.
Details and comments

@ShellyGarion , can you please review?


bug: alert buttons propagate to the below page

Bug Report
Ionic version:
[x] 5.x
Current behavior:
All my Alerts now seem to propagate any alert button click through to the page below it. Therefore any buttons on the page underneath are activated by using the alert buttons.
Expected behavior:
the alert should have no impact on the page below from taps/clicks
Steps to reproduce:
I tested with the exact code from the docs - pasted that into the app and exactly the same thing - so that can be used to reproduce
Other information:

Ionic info:

Ionic:
Ionic CLI                     : 6.10.0 (/usr/local/lib/node_modules/@ionic/cli)
Ionic Framework               : @ionic/angular 5.2.1
@angular-devkit/build-angular : 0.901.8
@angular-devkit/schematics    : 9.1.8
@angular/cli                  : 9.1.8
@ionic/angular-toolkit        : 2.2.0
Capacitor:
Capacitor CLI   : 2.2.0
@capacitor/core : 2.2.0
Utility:
cordova-res : not installed
native-run  : not installed
System:
NodeJS : v14.0.0 (/usr/local/bin/node)
npm    : 6.14.5
OS     : macOS Catalina

same problem with version 5.2.1

Thanks for the issue. I am going to close this as a duplicate of https://github.com/ionic-team/ionic/issues/21503. The bug has been resolved, and a fix will be available in the next release of Ionic Framework.


Create share link while creating a file with snapshot summary

ODSP /snapshot api now provides a new feature where we can create a file sharing link along with the creation of a new fluid file in the hope to improve performance by reducing the number of roundtrips to the server. Parameter can be provided to the api like so: &createLinkType=csl. When this parameter is provided, ODSP will return a sharing link or an error message in the response of the /snapshot api call. If the creation of sharing link fails, the API does not fail and just returns an error message. Note: at the moment, it only supports csl (oraganization) share links, but the code in this PR is written in a generic way to support other types as well in the future.
In order to let applications to request creation of a share link with file creation, this PR proposes following updates:

createOdspCreateContainerRequest is updated to accept an additional optional parameter called createLinkType. Added supporting documentation in the comments. When createLinkType is not provided, attach flow proceeds as is. When this value is provided, we add a new request parameter to the /snapshot api call to let ODSP know that a sharing link needs to be created as well along with the creation of the file.
Added a new property bag shareLinkInfo in IOdspResolvedUrl definition, which would save all the sharing link related information.
Moved the sharingLinkToRedeem within shareLinkInfo property bag in IOdspResolvedUrl and also updated corresponding usage. For now we are preserving sharingLinkToRedeem in IOdspResolvedUrl  as before as well, but it will be deprecated in future versions.
createNewFluidFile method is updated to save the new share link or error message in odspResolvedUrl.shareLinkInfo.
After container.attach() is complete, applications can request share link information by requesting container.resolvedUrl() and read the shareLinkInfo within this object.
Added a new feature flag called enableShareLinkWithCreate so that this feature can be enables/disabled if needed. This flag is temporary until we are sure everything works smoothly.

@pragya91 Can you please add a unit test here:
https://github.com/microsoft/FluidFramework/blob/main/packages/drivers/odsp-driver/src/test/createNewUtilsTests.spec.ts
See the usage mock fetch here. You can use that to return whatever response you want and then see share link is set properly.


sign up page with stub pending sign up api

This fixes issue #10
Bootstrapped with create-react-app
Sass for styling
Notiflix for notifications and alerts

Hi, add gitignore in the frontend folder to ignore node modules, you pushed it along

remove the tracked files too, so we dont' merge it
git -rm --cached "node_modules"

also request me as a reviewer

also request me as a reviewer

Alright

remove the tracked files too, so we dont' merge it
git -rm --cached "node_modules"

I didn't know I could still make those changes to a pull request

just work on the same branch and push again, the pr will update with the new commits

Where are there package.json and log files updated in the root folder, pleaes remove them

I realized why the node_modules and package.json appeared in root. I'm correcting it now

Where are there package.json and log files updated in the root folder, pleaes remove them

It has been corrected


Prepare release secrets-injector-1.0.1

Version 1.0.1 contains a pretty critical fix: https://github.com/1Password/kubernetes-secrets-injector/pull/24. It might be a good idea to make it the default and release a new version of the chart.
Closes #143

Thanks for opening this @antoineco. Sorry for the late reply. In the meantime, we have released v1.0.2. of the secrets injector. I've opened a separate PR to bump the chart to that version.
I've mentioned you as a co-author in that PR, which will get you listed as a contributor on this repository.


Enrich accountIDs and customerIDs

When building a UI against the transfers endpoint, it provides source and destination accountIDs and customerIDs, which are necessary for showing a meaningful UI.
For each transfer in a list (default limit/count is ~25 transfers per request) there are likely two customers and two accounts, which is 4 requests. That would equal 100 requests a browser/client would have to make to hydrate a UI, which is WELL above the number of concurrent requests that can be made. Related, there is no endpoint to fetch a single accountID at this time.
Ideally, we'd have some orchestration in a service that would return the customer and account models in the source and destination objects, perhaps like:
{
  "transferID": "UUID",
  "source": {
    "customer": {
      "customerID": "UUID",
      "firstName": "Josh",
      "lastName": "Sadler",
      "email"<EMAIL_ADDRESS>      ...
    },
    "account": {
      "accountID": "UUID",
      "type": "Checking",
      "maskedAccountNumber": "***1234",
      "status": "validated"
      ...
   }
  "amount": {
    "currency": "USD",
    "value": "1000"
  }
  ...
}

I have no strong opinions about how we achieve this, just that it not be orchestrated on a frontend.

This change would use https://github.com/moov-io/customers/issues/170 to grab those two Accounts.

I talked with @InfernoJJ about this and we came up with a different solution than stuffing all of this orchestration into paygate.
In the short term, what if we created an endpoint in customers that could perform a batch fetch of customers and accounts in one call? Something like:
POST /customers-reports/customers-by-account  [ <account id1>, <account id2>, ...]   => [ { account: {...}, customer: {...} }, { account: {...}, customer: {...} }, { account: {...}, customer: {...} } ... ]
So for a transfer, the UI could make one API call to the customers service to get all of the customer and account objects for that transfer?
In the longer term, we should probably look at creating a new service named something like ux-reports which can make these orchestration kind of calls in one call from the UI.
@joshsadler Thoughts?

The biggest bonus of this is the decrease I/O pre-LB and post-LB and
effectively eliminating it because it would just be one DB quiet rather
than 100.
pre-LB = 10 seconds to load.
post-LB = 2 seconds to load.
Batching = 50-100ms.
On Fri, Sep 25, 2020 at 10:23 AM Jordan Brown<EMAIL_ADDRESS>wrote:

I talked with @InfernoJJ https://github.com/InfernoJJ about this and we
came up with a different solution than stuffing all of this orchestration
into paygate.
In the short term, what if we created an endpoint in customers that could
perform a batch fetch of customers and accounts in one call? Something
like:
POST /customers-reports/customers-by-account [ , , ...] => [ { account: {...}, customer: {...} }, { account: {...},
customer: {...} }, { account: {...}, customer: {...} } ... ]
So for a transfer, the UI could make one API call to the customers
service to get all of the customer and account objects for that transfer?
In the longer term, we should probably look at creating a new service
named something like ux-reports which can make these orchestration kind
of calls in one call from the UI.
@joshsadler https://github.com/joshsadler Thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/moov-io/paygate/issues/573#issuecomment-698992474,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFMTIX6FP2QZWZ2PBDSU5DSHSYYLANCNFSM4RTM3ELA
.

@jmbrown412 the individual transfer UI or API isn't the concern, it's the transfers list UI for an organization.
The data we get for the list of transfers matches the functionality we want to expose through the UI, with the exception of displayable information for customers and accounts on each individual transfer in the list.
I don't think this counter-proposal solves the problem.

The proposed new endpoint in customers should take care of the exception you mentioned for the displayable information for customers and accounts. @joshsadler Wanna jump on a short call to discuss?

Moving this to blocked/waiting until we come up with an agreeable approach to solving the backend orchestration of data from multiple services.

https://drive.google.com/file/d/114_VJQxm-tiPKnRnsqMtyNNxcDgpoxBa/view?usp=sharing


Fix memoization

It's necessary to put subscribeToMore in the dependencies of useEffect (the first one that is received on mount doesn't work). This means that it needs to be memoized in sync with the JS value. Because there is a function fromJS where it's not possible to add hooks I created useFromJs. I also had trouble satisfying the typechecker when passing a function to useMemo (I got "This field value has type ... which is less general than ..."). So I brute forced with Obj.magic (external types are correct anyway and without useMemo it also works).
Let me know what you think. There are some refactoring possibilities.
Oh yeah. subscribeToMore returns an unsubscribe function which is pretty important, because it needs to be called to clean up the useEffect hook.

Let me know what you think. There are some refactoring possibilities.

Awesome, thanks! I don’t think I fully understand the nuances of this issue well enough to comment yet, so bear with me as I try to understand a bit better 😄

It's necessary to put subscribeToMore in the dependencies of useEffect (the first one that is received on mount doesn't work). This means that it needs to be memoized in sync with the JS value.

These memoizations assume  that they can rely on the fact that the underlying JS result object will be new every time something changed. And that is not the case here? So you’re saying this is failing because we’ve memoized on the first object received, but then… they are mutating the subscribeToMore property on the previous result object or something rather than creating a new object and we don’t create a new record?
Also, the subscribeToMore that initially renders doesn’t work? That’s interesting. Is this an Apollo bug do you think? I’ll try to get a reproduction up to understand it better. Like, if the subscribeToMore function is changing and you’re only supposed to call it once, this seems like it would also be highly problematic in vanilla JS? What would you do? Only call it on the second change in useEffect? I feel like I must not be understanding.

Oh yeah. subscribeToMore returns an unsubscribe function which is pretty important, because it needs to be called to clean up the useEffect hook.

Yes, great. Probably a recent addition, but maybe I missed it. In any case, I think I recall useQuery is supposed to automatically tear down any subscriptions, so while this should definitely be added, I don’t think you need to manually call it? Doesn’t hurt, though. https://github.com/apollographql/apollo-client/blob/15536f5240259c7d05f26ec335a2242f2bab70e2/src/core/ObservableQuery.ts#L643

@jfrolich I wasn't able to reproduce this behavior. Using subscribeToMore in a React.useEffect0 worked as expected. What version of @apollo/client and subscriptions-transport-ws are you using?

Ah ok, let me try to upgrade

By the way, is memoizing the whole js object the right thing to do anyway? It looks like its different every time and only the keys are "stable".

Ok you were right, I found the root cause haha! I have some funky stuff going on with subscriptions, but it's not due to apollo or due to rescript-apollo-client. I still think we might need to do memorization differently to get some more performance.

By the way, is memoizing the whole js object the right thing to do anyway? It looks like it's different every time and only the keys are "stable".

Let's reconsider. I may have just assumed this is what should happen since it's what reason-apollo-hooks was  doing as well as reason-urql and not properly analyzed what was going on. Anecdotally, there was also a discussion on reason-urql when I was PR'ing there that some people definitely had the expectation they should be able to rely on the result to be memoized when it hadn't changed.
I'll try and investigate more.

I still think we might need to do memorization differently to get some more performance.

I'd love to hear more.


albatrossd did not clear up tap devices on shutdown

a service albatross_daemon stop killed all the unikernels, but left the tap devices in place. this was with 2d26a56c0d21bf9bf195a9dd448cf90f83ea2202. need to investigate (stress test) whether this is still an issue with more current albatross.

system log:
Jul 29 12:03:59 <kern.info> beast kernel: tap6: link state changed to DOWN
Jul 29 12:03:59 <daemon.notice> beast daemon[84677]: albatrossd: [WARNING] unikernel [vm: YYY] solo5 exit failure (1)
Jul 29 12:03:59 <daemon.notice> beast daemon[84638]: albatross_stats: [INFO] removing vmid [vm: ZZZ]
Jul 29 12:03:59 <daemon.notice> beast daemon[84638]: albatross_stats: [INFO] removing pid AAAA

the "solo5 exit failure (1)" is from Vmm_core.should_restart, but for some reason the waitpid handler was not executed (and the new albatross_log failed to read entries with version 0x2 /o\ -- unclear whether the Unikernel_stop log entry was dumped)

from the albatross log, there's only a few "stopped unikernel YYY" -- the sleep 1 in https://github.com/hannesm/albatross/blob/1b1164166b409ec4daf6ea87d067031a7bc9973a/daemon/albatrossd.ml#L176-L186 should be revised (with appropriate waiters / inversion of control / eventually Lwt.join)


Avoid Arch Linux & Fedora workaround

Replace all occurence of /etc/openvpn by OVPN_ROOT variable.
Set this variable accordingly after OS detection to
- /etc/openvpn/server on Arch and Fedora
- /etc/openpvn to all other distros

Breaks the service on Fedora 28.


[Deploy] Zoho Mail

Service

Zoho Mail
Link to your repository

https://github.com/eightieskhild/Franz-recipes-Zoho
Additional Information

@eightieskhild could you implement the change asked by @adlk as mentioned in #49 ?


Regression: Memory consumption when using scipy.stats.rv_continuous

Following the example given in the documentation I am using rv_continuous to generate a custom pdf. The following code snippet works as expected in scipy v0.18.1 but exhibits a very large (~GB) memory consumption when run with scipy v0.19.0
from scipy.stats import rv_continuous
import numpy as np
import resource
import scipy
import sys

print "numpy version: {}".format(np.version.full_version)
print "Scipy version: {}".format(scipy.version.full_version)
print "Python {}".format(sys.version)

class gaussian_gen(rv_continuous):
    "Gaussian distribution"
    def _pdf(self, x):
        return np.exp(-x**2 / 2.) / np.sqrt(2.0 * np.pi)

def print_mem():
    mem = resource.getrusage(resource.RUSAGE_SELF).ru_maxrss
    print 'Memory usage: %s (kb)' % mem

print_mem()
gaussian = gaussian_gen(name='gaussian')
print_mem()
values = gaussian.rvs(size=1000)
print_mem()
values = gaussian.rvs(size=5000)
print_mem()

The output of the snippet for version 0.18.1 is:
numpy version: 1.12.1
Scipy version: 0.18.1
Python 2.7.12 (default, Nov 19 2016, 06:48:10)
[GCC 5.4.0 20160609]
Memory usage: 70048 (kb)
Memory usage: 70048 (kb)
Memory usage: 70048 (kb)
Memory usage: 70592 (kb)

while 0.19.0 looks as follows:
numpy version: 1.12.0
Scipy version: 0.19.0
Python 2.7.12 (default, Nov 19 2016, 06:48:10)
[GCC 5.4.0 20160609]
Memory usage: 69672 (kb)
Memory usage: 69672 (kb)
Memory usage: 426952 (kb)
Memory usage: 2215576 (kb)

I just noticed that it appears to be working in master, but I figured it might be good to post this issue in any case, just so that people can find it or if it was only fixed by accident. Output when run on master:
numpy version: 1.12.1
Scipy version: 1.0.0.dev0+ab9eff3
Python 2.7.12 (default, Nov 19 2016, 06:48:10)
[GCC 5.4.0 20160609]
Memory usage: 75972 (kb)
Memory usage: 75972 (kb)
Memory usage: 75972 (kb)
Memory usage: 75972 (kb)

Before opening this issue I asked a question about it at stackoverflow

Possibly duplicate of gh-7214

If it is really a quad bug, it should disappear if you define _cdf too:
https://github.com/scipy/scipy/blob/3d5024b40e2e089251af1b4b89c5ec1c7145412c/scipy/stats/_distn_infrastructure.py#L1613
Can you add a _cdf implementation and check memory consumption @cbourjau ?

@ev-br : Yes, I can confirm that the issue goes away if _cdf is defined using scipy 0.19. Thanks for your fast feedback on this issue!

Good, then this issue should be fixed in master.


[gen_l10n] Checking for unused messages

Currently, there is no way to tell if there is a message that isn't being used in the Flutter application. It would be nice to be able to use the tool to check what messages aren't being used in the application so that they can be removed, edited, properly used, etc.
/cc @HansMuller

I just did as much for an app we've been working on. This is the rough and ready approach.

Create a list of the message names from the template arb file. I did it with grep, but the tool could easily do it.
Change the generated app_localizations.dart and code generated for the template file (say app_localizations_en.dart): comment all of the message methods. As before, it would be easy for the tool to do this.
Apply the analyzer to the project and extract the warnings about missing AppLocalization methods.  This can be converted into a list of method names (the AppLocalization methods the app is actually using).
Generating a list of unused message names is trivial:

  for (String messageName in messageNames) {
    if (!methodNames.contains(messageName))
      print(messageName);
  }

We could leave the job of actually removing the unused messages to the developer or do that too.

For the record this is a shell code that counts the occurrences of each label (from /lib):
grep '^    "' l10n/app_en.arb | awk -F: '{print $1}' | grep -v "@" | awk -F\" '{print "TAG=" $2 ";COUNT=`grep -r \"\\.$TAG\" * | wc -l`;print \$COUNT \$TAG"}' | zsh | sort -r

If the count is 0 you're sure the label is not used.
You cannot be sure if a label is used with a count greater than 0, as the code would count occurrences of add_item also for add.
The code is good in a first approach.
cf. https://github.com/openfoodfacts/smooth-app/issues/3856


Repeated prompt segfaults on 61th iteration

Simple script like:
import llm
model = llm.get_model("orca-mini-3b-gguf2-q4_0")
for i in range(70):
    print(i, model.prompt("How are you today?"))

seems to always crash on the 61th prompt() call.
It doesn't seem to be related to running out of memory but something else.
I'm not quite sure if this is actually llm-gpt4all issue or issue in gpt4all or even in llama.cpp.
But at least, I didn't see issues when using gpt4-all directly (at least the following version works):
from gpt4all import GPT4All
model = GPT4All(MODEL)
for i in range(70)
    print(model.generate("How are you", max_tokens=5))

Anyway, the gpt4-all Python API behaves quite a bit differently here.
E.g., the llm-gpt4all re-creates LLModel objects in Python for each prompt.
The coredump shows that the ctx variable seen by the C++ code is null but how that exactly happens:
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f5a024a8ac4 in ggml_new_object (ctx=ctx@entry=0x0, type=type@entry=GGML_OBJECT_GRAPH, size=262440)
at /home/johannes/ai/llm/gpt4all/gpt4all-backend/llama.cpp-mainline/ggml.c:2430
2430	    struct ggml_object * obj_cur = ctx->objects_end;
(gdb) bt
#0  0x00007f5a024a8ac4 in ggml_new_object (ctx=ctx@entry=0x0, type=type@entry=GGML_OBJECT_GRAPH, size=262440)
at /home/johannes/ai/llm/gpt4all/gpt4all-backend/llama.cpp-mainline/ggml.c:2430
#1  0x00007f5a024cc3c2 in ggml_new_graph_custom (ctx=0x0, size=8192, grads=false)
at /home/johannes/ai/llm/gpt4all/gpt4all-backend/llama.cpp-mainline/ggml.c:15834
#2  0x00007f5a02488bae in llm_build_context::build_llama (this=this@entry=0x7ffc5fb27d60)
at /home/johannes/ai/llm/gpt4all/gpt4all-backend/llama.cpp-mainline/llama.cpp:4326
#3  0x00007f5a024606c4 in llama_build_graph (lctx=..., batch=...) at /home/johannes/ai/llm/gpt4all/gpt4all-backend/llama.cpp-mainline/llama.cpp:6191
#4  0x00007f5a0246e405 in llama_new_context_with_model (model=, params=...)
at /home/johannes/ai/llm/gpt4all/gpt4all-backend/llama.cpp-mainline/llama.cpp:9514
#5  0x00007f5a02456a98 in LLamaModel::loadModel (this=0x419eed0, modelPath="/home/johannes/.cache/gpt4all/orca-mini-3b-gguf2-q4_0.gguf", n_ctx=)
at /home/johannes/ai/llm/gpt4all/gpt4all-backend/llamamodel.cpp:215
#6  0x00007f5a03f770df in llmodel_loadModel (model=, model_path=0x7f5a02acbdd0 "/home/johannes/.cache/gpt4all/orca-mini-3b-gguf2-q4_0.gguf",
n_ctx=2048) at /usr/include/c++/13/bits/basic_string.tcc:238
#7  0x00007f5a03f898b6 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#8  0x00007f5a03f8634d in ffi_call_int (cif=cif@entry=0x7ffc5fb297f0, fn=, rvalue=, avalue=,
closure=closure@entry=0x0) at ../src/x86/ffi64.c:673
#9  0x00007f5a03f88f33 in ffi_call (cif=cif@entry=0x7ffc5fb297f0, fn=fn@entry=0x7f5a03f77060 <llmodel_loadModel(llmodel_model, char const*, int)>,
rvalue=rvalue@entry=0x7ffc5fb29700, avalue=) at ../src/x86/ffi64.c:710
#10 0x00007f5a042142e9 in _call_function_pointer (argtypecount=, argcount=3, resmem=0x7ffc5fb29700, restype=,
atypes=, avalues=, pProc=0x7f5a03f77060 <llmodel_loadModel(llmodel_model, char const*, int)>, flags=)
at /usr/src/python3.11-3.11.6-3/Modules/_ctypes/callproc.c:923
#11 _ctypes_callproc (pProc=, argtuple=, flags=, argtypes=, restype=,
checker=) at /usr/src/python3.11-3.11.6-3/Modules/_ctypes/callproc.c:1262
I'm using Ubuntu, Python 3.11.6, no GPU used here.

Hi,
I use Fedora 38, python 3.11.8, no GPU and have the same problem.


README update

To work with Achintya @RaoOfPhysics to update and expand the README. ✨

This will also update the description on PyPi


multiple instances of playerview and MediaController in different activities for same service, like the mediasessions demo

multiple instances of playerview in different activities
We are planning to have a Player Activity and  a common player fragment
While the player activity, will be a separate activity with its own , playerview ,as provided in the mediasessions demo
we also want to have a common palyerfragment which can act as a mini player which is the common pattern accross music apps, which we can include in various activities.
the question is can we have different instances of player view and MediaController in this player activity and player fragment.
Also I am confused regarding the pattern we need to follow, while the mediasessions demo directly calls the playerview and MediaController  in player activity and calls the MediaBrowser in the PlayableFolderActivity , where as the UAMP has a MusicServiceConnection -->   that manages a connection to a [MediaLibraryService] instance, in the musicservice class,
So do we need to have a MusicServiceConnection class or as is mentioned in this video
https://www.youtube.com/watch?v=sTIBDcyCmCg&t=480s
which mentions  mediacontroller is a player implementation, we can direclty pass it to the playerview

In general I would only create a single controller at a time which can be passed to multiple UI elements at the same time if this is required. The state of the controller always reflects the state of the session, so the state of multple controllers area always the same. There is no point in having more then one instances from that point of view.
There are no design constraints in how you design you app that is using a media MediaLibraryService. The demo app and UAMP that you mention have chosen a different design. There is no need for you to follow on or the other as you can pick whatever suits your app and use cases best.


react-beautiful-dnd not working within react flow node

Describe the Bug
I built a node item where it's possible to reorder the list with the node
But each time I drag an item it moves out of the node
Please is there a way to fix this ??
Many Thanks
https://codesandbox.io/s/hopeful-bose-i0rxsj?file=/src/App.js
Expected behavior
Item should stay with the node
Screenshots or Videos

I found the fix for this
it's as a result transform property on the react-flow-renderer nodes
see this

I found the fix for this it's as a result transform property on the react-flow-renderer nodes see this

Could you clarify a bit more about your solution if you have a moment? Definitely just hit this roadblock and trying to figure out the best way to unblock myself.


ExternalDocumentation now correctly inherits from SwaggerModel

ExternalDocumentation now serialises correctly. Added an example into the demo.

Looks good to me, would you mind adding a unit test?

Seeing as this looks more like a simple oversight, I've just written a basic test to ensure that it correctly inherits from the SwagerModel. Feels a bit out of place but not really sure how else to test that, open to ideas. If you're happy with that test i'll go back and add similar tests to the other builders.

@LucasMoffitt hey sorry, yeah this is fine, not sure checking the inheritance is necessary but it doesn't hurt. If you want to update the other tests you can, up to you!


/* istanbul ignore next */ ignored with ES6 syntax ?

Expected Behavior
I expected that excluded comments work to keep my coverage with my ES6 syntax.
Observed Behavior
Simply ignored ^^
Bonus Points! Code (or Repository) that Reproduces Issue

My repository
Main File on coveralls.io

@jy95 I think I'm facing this too. Did you find a workaround?

No : I guess the coverage stuff doesn't like this excluded comment in the 'catch' part of my code ^^

@jy95 I just tested your current repo by adding the following code inside src/TorrentLibrary.js:
    /* istanbul ignore next */
    if (false) {
      console.log('here');
    }

This unreachable console.log was not reported, I then removed the istanbul ignore next and it was reported.  Your repo shows 100% coverage so I'm closing this issue as it appears to be resolved (turns out I was wrong about comments: false causing an issue).


feat: Support new pipe function for valibot

close https://github.com/chimame/conform-to-valibot/issues/26
TODO

[x] parseWithValibot
[x] getValibotConstraint

If you describe your problem to me, I can try to help you fix it.

@fabian-hiller
Thank you. I'd like some advice on the schema type.
For example, to define a function that takes an Array and a String schema as arguments, it would look like this:
import {
  ArraySchema,
  ArrayIssue,
  StringSchema,
  StringIssue,
  BaseSchema,
  ErrorMessage,
} from "valibot";

type ParamSchema =
  | ArraySchema<
      BaseSchema<unknown, unknown, BaseIssue<unknown>>,
      ErrorMessage<ArrayIssue> | undefined
    >
  | StringSchema<ErrorMessage<StringIssue> | undefined>;

const testFunction = <T extends ParamSchema>(
  schema: T,
): BaseSchema<unknown, unknown, BaseIssue<unknown>> => {
  if (schema.type === "array") {
    return schema.item;
  }

  return schema;
};

However, I would like to consider cases where Array and String schemas come with pipes. In that case, I tried writing the code as follows:
const testFunction = <T extends ParamSchema>(
  schema:
    | T
    | SchemaWithPipe<[T, ...PipeItem<T, unknown, BaseIssue<unknown>>[]]>,
): BaseSchema<unknown, unknown, BaseIssue<unknown>> => {
  if (schema.type === "array") {
    return schema.item;
  }

  return schema;
};

This code is unable to identify the Array schema, and the following type error occurs:

I'd like some advice on type specification that will accept both schemas with and without pipes attached.

Maybe the T is the problem:
// Try to change this
SchemaWithPipe<[T, ...PipeItem<T, unknown, BaseIssue<unknown>>[]]>

// To this
SchemaWithPipe<[T, ...PipeItem<unknown, unknown, BaseIssue<unknown>>[]]>

Thank you for your advice.
I've tried to fix it, but it seems that the type error is still occurring.

Can you double check your code? It should generally work. See this playground. One problem might be the nested if-statements, but that's just a guess. You can also try using v.isOfType('array', schema) instead of 'item' in schema.

Thank you for your continued advice.
Following your sample code, when the condition 'item' in schema is removed from the if statement, the pipe type is correctly recognized and retrieved. However, even if schema.type === "array" or the new isOfType function is used to recognize ArraySchema, the type of item is still not recognized. The issue seems to be that SchemaWithPipe<[T, ...PipeItem<unknown, unknown, BaseIssue<unknown>>[]]> does not recognize the pipe-added type of ArraySchema.
I created my sample code here.
I also think that the SchemaWithPipe type described in valibot is correct. I'm thinking about how to do this with TypeScript.

Feel free to recreate the problem in our playground and tell me what your goal is. That way I can easily investigate it.

I will release it this or next week.


Denmark phoneNumberType issue

Hello,
It seems that the pattern used to differentiate mobile and fixed line is incorrect because they are similar.
I did some research and I found this

Mobile phones :
20-xx-xx-xx – 31-xx-xx-xx
40-xx-xx-xx – 42-xx-xx-xx
50-xx-xx-xx – 53-xx-xx-xx
60-xx-xx-xx – 61-xx-xx-xx
71-xx-xx-xx
81-xx-xx-xx
91-xx-xx-xx – 93-xx-xx-xx
Landlines :
32-xx-xx-xx – 36-xx-xx-xx
38-xx-xx-xx – 39-xx-xx-xx
43-xx-xx-xx – 49-xx-xx-xx
54-xx-xx-xx – 59-xx-xx-xx
62-xx-xx-xx – 66-xx-xx-xx
69-xx-xx-xx
72-xx-xx-xx – 79-xx-xx-xx
82-xx-xx-xx
86-xx-xx-xx – 89-xx-xx-xx
96-xx-xx-xx – 99-xx-xx-xx

thanks

Hi @Cgen37
Can you say more about the research you used? Please see our guidelines.

Hi, Thanks you for your reactivity.
I found information in this website : https://en.wikipedia.org/wiki/Telephone_numbers_in_Denmark

Thanks for sharing the link!
We have categorized the same ranges for both fixed-line and mobile because the official documentation from Denmark classifies these as "mainly" mobile or fixed-line, but not all one or the other. See official documentation: https://erhvervsstyrelsen.dk/sites/default/files/8-cifrede_abonnentnumre.xls, these are all "mainly" mobile or fixed-line.
The library is working as intended, we do not want to stop supporting these numbers as valid both for mobile and fixed-line. Thanks for reporting, please let us know if you find other issues!


ShaderGraph version not work.

Hello. Can you check what the problem might be? If I switch URPJigglePhysicsSoftbody.shadergraph, the vertex disappears.

I tried the way it is in the ASE shader but it doesn't work I don't understand.

Yeah, okay. I was looking at your shader and saw that it's local movement. you still need to add the original vertex positions at the end.

Yeah sorry, I made the original code node with respect to Amplify Shader's defaults which uses local space offsets.
You found the intended solution just fine!


Functions, Types and Methods are undocumented

All the objects in the SDK packages are completely undocumented, making it hard to understand how to use the API. This is most obvious when reading the godoc for the package.

@ahmetalpbalkan Thanks! This is much better!
As an aside, we use golint during our build to check exported documentation for each PR. Its obnoxious, at first, but ensures that everything gets some docs.


Add badges for Stars and Forks in the Readme

Description
The Readme does not have the badges stating the current number of stars and forks on this repository

I would like to work on the issue please assign this to me. Thanks

@anitab-org/mentorship-flutter-maintainers do we need these badges?

I would like to work on this.
please assign it to me

Closing as this is not needed as of now as we can already see these stats on top of the repo page.


Allowing duplicate rule names when collecting from different namespace should be prevented or optional

What did you do?
Created PrometheusRules in several namespaces and gather them in a centralized cluster Prometheus.
Defined a rule in a namespace with the same name as another rule in a different namespace. Both rules are collected without errors even when they have the same name.
What did you expect to see?
The operator handles the duplicated Rule on creation time detecting that there's another rule in a different namespace with the same name.
What did you see instead? Under which circumstances?
The operator let the rule with the same name pass through and the last one definition overwrites the first one.
Proposal
Support an option to letting the operator decide if allowing duplicate rule names from different namespaces or not.
I basically want to have more isolation of PrometheusRules per namespace. Since the operator supports the collection of PrometheusRules from different namespaces, I think it makes sense to support options to isolate both rule groups (that must be unique anyway) and Prometheus rules too.
I know that Prometheus allows the definition of more than one rule with the same name because you can add more "dimensions" by using labels, for example, but in case of a multi-tenant cluster this is cumbersome because some people may define their own rules with the same name as others and therefore will overwrite them, in best case only changing labels, in worst case changing the expression and annotations.
So I have the following proposal:

Create a handler to check the rule names and if they're the same apply one of the following strategies:

Add the namespace name as prefix or suffix to the rule name on creation.
Fail immediately and let the user modify the name.
Allow duplicates.

@mxinden @brancz If this is of interest I think I can prepare a PR with this changes

I’m about to go on vacation. I’ll let @mxinden handle this, he also implemented the current PrometheusRule work.

I’m about to go on vacation. I’ll let @mxinden handle this, he also implemented the current PrometheusRule work.

Also on vacation till mid of January. Will come back to this afterwards. Sorry about the delay @richerve and thanks for the offer.

@mxinden is this still of interest?

@richerve I am not involved in the Prometheus Operator development anymore. Maybe one of the maintainers can jump in?

@richerve yes, there is definitely still interest in this and we will actually have a more intense look at this issue :+1:

I was able to reproduce this, and I agree this is something we need to fix.  I created https://github.com/prometheus/prometheus/issues/6334 to potentially solve this in prometheus.
Currently, each prometheusrule object is mounted as a separate file in the configmap and is named according to the namespace and object where it comes from, so adding a label with this filename should be similar to what @brancz suggested previously.

Would just enforcing a label be sufficient or do we have to tinker with the rule (group) name?

@brancz I don't think I understand what you mean by "enforcing a label"? I think I would be happy if the rule names are prefixed with the namespace, and ideally the rule groups too, but I'm not completely sure about Prometheus' logic regarding duplicated groups with same name, is that possible? My only concern with this approach is that is sort of "magic" in the sense that alert names will have a new prefix and that could make difficult for silences and/or routing, but in any case if it's an optional parameter and correctly documented, don't think it's a big issue

The group names already won't conflict since they are also qualified by the rule filename which is based on the namespace and prometheusrule object name.  So you would only get a group conflict if you had two groups with the same name in the same prometheusrule.

@brancz I don't think I understand what you mean by "enforcing a label"?

@richerve I think he means could we just use a namespace label instead of modifying the rule names?
One potential problem with modifying the rule names is that recording rules that depend on the results of previous rules would not work correctly.


Add computeDryLayout

Hello!
In Flutter 1.25, there is a new method in RenderObject called computeDryLayout. It is used to calculate the size of the RenderObject by given constraints without the need to layout it.

https://flutter.dev/docs/release/breaking-changes/renderbox-dry-layout
As an example here is the implementation for RenderConstrainedBox used for SizedBox.
https://github.com/flutter/flutter/blob/4901744e62f67ad10440725d2c97e84e66ce77f5/packages/flutter/lib/src/rendering/proxy_box.dart#L288-L295
If you need, I would be happy to help with a PR

Hi @jamesblasco ! Thanks for raising this issue :-).
I have no bandwidth for the moment so I would be very happy if you could make this PR. The only thing I would need to do then, would be to create a new branch for this, because this change cannot be in the master branch where I want it to be available for the stable branch of Flutter.
I also wonder if we can have more than one pre-release in pub.dev, do you if it's possible?

Hi @jamesblasco ! Thanks for raising this issue :-).
I have no bandwidth for the moment so I would be very happy if you could make this PR. The only thing I would need to do then, would be to create a new branch for this, because this change cannot be in the master branch where I want it to be available for the stable branch of Flutter.
I also wonder if we can have more than one pre-release in pub.dev, do you if it's possible?

I created the beta branch for this. It would be great if you can make this PR to this branch. Thanks again

I created the beta branch for this. It would be great if you can make this PR to this branch. Thanks again

I will do that then! Thanks.  I think it is possible to publish multiple pre release versions with different names. But we can wait until it reaches beta and add it inside null safety

I will do that then! Thanks.  I think it is possible to publish multiple pre release versions with different names. But we can wait until it reaches beta and add it inside null safety

Added in 2.0


I can’t use jishaku shell command

Summary
I can’t use jishaku shell command
Reproduction steps
Use docker image("python:3-alpine”)
Expected results
Run command
Actual results

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/jishaku/features/shell.py", line 87, in jsk_shell
    with ShellReader(argument.content, escape_ansi=not Flags.use_ansi(ctx)) as reader:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/jishaku/shell.py", line 86, in __init__
    self.process = subprocess.Popen(sequence, stdout=subprocess.PIPE, stderr=subprocess.PIPE)  # pylint: disable=consider-using-with
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/subprocess.py", line 1026, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/local/lib/python3.11/subprocess.py", line 1950, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/bin/bash'

Checklist

[ ] I have updated discord.py and jishaku to the latest available versions and have confirmed that this issue is still present
[ ] I have searched the open issues for duplicates
[ ] I have shown the entire traceback, if possible
[ ] I have removed my token from display, if visible

System information

discord.py v2.3.2
jishaku v2.5.1

While this falls into a weird documentation hole (I really need to get this consistent eventually), the README mentions that the shell command looks at your SHELL environment variable or otherwise uses /bin/bash. So to fix this, you either need to set SHELL to a suitable shell (such as /bin/sh), or install bash.

I see thanks


GHC 8.10 support

A few changes to support GHC 8.10.
Relies on:

haskell-lsp-types PR https://github.com/alanz/haskell-lsp/pull/213
hie-bios PR https://github.com/mpickering/hie-bios/pull/134

Hopefully fakeDynFlags won't be necessary in the future if a patch like this one (Disentangle DynFlags and SDoc) lands.


drivers: ssd16xx: Make voltage overrides optional

Many modern panels don't require any overrides to work. All the relevant voltages are normally loaded from OTP when performing a refresh with the built-in LUT. Such panels are currently not possible to drive using the existing driver since it insists on specifying voltages and other parameters that aren't always provided by the vendor.
This pull requests includes a series of commits that:

Refactor and clean up activation handling.
Make voltage overrides optional.
Make updates of ssd167x-specific registers optional.

Please not that the change that makes ssd167x-specific registers, specifically SSD16XX_CMD_DUMMY_LINE and SSD16XX_CMD_GATE_LINE_WIDTH, optional and left with their default values unless the device tree provides an override. This is unlikely to cause issues in practice since the loaded values didn't match those used by some of the panels (e.g., GDEH0213B72) supported by Zephyr.

Update 2022-07-26: Rebased onto latest main.

@mbolivar-nordic you have reviewed a few other changes related to this driver. Could you have a look at this PR as well?

@mbolivar-nordic Can you please take a look?


Can't resolve waves.css and waves.js

ERROR in ./~/vue-waves/index.js
Module not found: Error: Can't resolve './waves.css' in '...\node_modules\vue-waves'
 @ ./~/vue-waves/index.js 1:0-20

ERROR in ./~/vue-waves/index.js
Module not found: Error: Can't resolve './waves.js' in '...\node_modules\vue-waves'
 @ ./~/vue-waves/index.js 2:0-30

me too.

@bigperson I solved, My English is not very good. Such use

npm i vue-waves-button --save
import Vue from 'vue';
import VueWaves from  'vue-waves-button';
import 'vue-waves-button/waves.css';
Vue.use(VueWaves);

try to update version to 0.1.1 , thx

@Teddy-Zhu That is OK?

@liujinyang1994  i try to fix the problem , the missing files have been included in package.json


Stakeholder buy-in

Stakeholder buy-in for user research

Having Trouble with Stakeholders? Try Treating Them as Users
WORDS BY NIKKI ANDERSON-STANIER, VISUALS BY THUMY PHAN
https://dscout.com/people-nerds/stakeholders-as-users

How to get stakeholder buy-in for user research: expert tips
Christopher Ratcliff
https://www.userzoom.com/ux-blog/how-to-get-stakeholder-buy-in-for-user-research/

4 Mistakes I made as a UX researcher & how to avoid them
A UXinsight by Anna Efimenko (she/her)
https://uxinsight.org/4-mistakes-i-made-as-a-ux-researcher-how-to-avoid-them/

Want stakeholder buy-in? Present the MVR (Minimum Viable Research)
Nikki Anderson
https://uxdesign.cc/want-stakeholder-buy-in-present-the-mvr-minimum-viable-research-75556bfa0e2d

Adopt-A-Participant: Five Tips for Engaging Stakeholders in Large Foundational Projects
https://medium.com/spotify-insights/adopt-a-participant-five-tips-for-engaging-stakeholders-in-large-foundational-projects-c0f75a84526c
Spotify Insights
Follow
Oct 15, 2021
How can you meaningfully break down the walls between your research participants and stakeholders? Here, Spotify Senior User Researchers, Akshay Verma and Kathy Lin, dig into the tips and lessons they learned from creatively engaging 40+ stakeholders through a longitudinal diary study with 60+ participants — and how they humanized research along the way.

12 Ways Innovative Companies do More Impactful Research with dscout
https://pages.dscout.com/hubfs/dscout-12_Ways (2).pdf?utm_campaign=Marketing Qualified Nurture Stream&utm_medium=email&_hsmi=159139600&_hsenc=p2ANqtz-_VEjEjOsc8HcZML7QokWEsG4LM_dhrkXodasA1FZjrY0wuds2zYWtHF8Be-PBrXZCoftnt8c5ljZiCZzbZ5FSKyYNHaz5JUGmyIplEcaqOhO6I8aU&utm_content=159139600&utm_source=hs_automation


09-create-power-bi-dashboard.md Exercise  Exercise 1 lab step changes

Priority
Breaking
Lab/Demo Number/Name
09-create-power-bi-dashboard.md Exercise  Exercise 1 lab step changes
Exercise 1, Task 2, Step 2 and 3
Also: Exercise 1, Task 4, Step 4:
Describe the bug
Step 2 states: "Select New > Dataset. This opens the Get Data page, and under Create new content > Files, select Get."
The interface has changed. It should say: " Click upload, then Browse.
Step 3 should now state: "Navigate to D:\PL300\Labs\09-create-power-bi-dashboard\Starter folder."
Note: the current step 3 referenced a Solution folder which does not exist. It should be the Starter folder.
Exercise 1, Task 4, Step 4: When I hovered over the Sales and Profit Margin By Month visual, the options that are to show up in the bottom right weren't showing completely because the visuals below were too close. I edited the report and lowered the 2 bottom visuals to give more room and now I can see the options including the Pin Visual option fully.
Screenshots
Tasks 2 Step 2:

Task 2 Step 3:

Task 4 Step 4: (After my report edit and fixed)

Note: To share feedback for the slides, please use the MCT Courseware Forum.

Thank you for the catch. Fix will be updated by EOD 2023/2/3.


Added data resiliency card

-fixtures ans tests for it
-components

Pull Request Test Coverage Report for Build 1082

15 of 17 (88.24%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 87.258%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/StorageOverview/DataResiliency/DataResiliency.js
12
14
85.71%

Totals

Change from base Build 1297:
-0.04%

Covered Lines:
3206

Relevant Lines:
3522

💛  - Coveralls

@mareklibra @suomiy @rawagner please review the PR..I have made requested changes


⚠ Bofrost.at has degraded performance

In 5c36271, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 3022 ms

Resolved: Bofrost.at performance has improved in 6f62469 after 6 minutes.


IGNITE-13591 added metric LastCheckpointStart

Added methods for reading of new metrics:

DataStorageMetrics.getLastCheckpointStartDate()
DataStorageMetricsImpl.getLastCheckpointStartDate()
DataStorageMetricsMXBean.getLastCheckpointStartDate()
DataStorageMetricsSnapshot.getLastCheckpointStartDate()

Added metric registration:

DataStorageMetricsImpl (see class constructor)

Added metric value update:

DataStorageMetricsImpl.onCheckpoint()
GridCacheDatabaseSharedManager.updateMetrics()

This PR is associated with a resolved ticket. Closing the PR, please reopen it if you still need it.


Inactive ?

Any plan to update this great library ?  I had to add many declarations to get it working with TypeScript 1.8.9.

Hey @smamessier
first of all thank you for thinking the library was/is great :-)
I'm thinking a lot lately on reviving the library. And doing a complete rewrite. If I do, I will probably use ES6 + Babel and not TypeScript. But I'm not totally sure yet.

TypeScript seems to get more and more popular. I think it's the right choice for a library like that. Actually I picked this library for my project because it was in TypeScript. In any case, I'll be happy to help out.

Can't we get basically the same with babel and flow? Or am I missing an advantage of Typescript?

In any case, I'll be happy to help out.

Awesome, I'll keep you updated :-)

You could I guess, but why rewrite it entirely as TypeScript is getting mainstream?


add config helper.

Signed-off-by: ChengZi<EMAIL_ADDRESS>

Codecov Report

Merging #899 (7e05f1d) into main (532707b) will increase coverage by 0.09%.
The diff coverage is 88.00%.

@@            Coverage Diff             @@
##             main     #899      +/-   ##
==========================================
+ Coverage   69.85%   69.95%   +0.09%
==========================================
  Files         200      200
  Lines        8718     8729      +11
  Branches     1429     1431       +2
==========================================
+ Hits         6090     6106      +16
+ Misses       2210     2205       -5
  Partials      418      418

Impacted Files
Coverage Δ

towhee/trainer/utils/visualization.py
59.66% <40.00%> (ø)

towhee/trainer/training_config.py
83.72% <100.00%> (+1.51%)
:arrow_up:

towhee/hub/repo_manager.py
81.08% <0.00%> (+0.90%)
:arrow_up:

towhee/dataframe/dataframe.py
74.15% <0.00%> (+1.04%)
:arrow_up:

Continue to review full report at Codecov.

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


PR to address minor UI features

NOT mobile specific UI changes

Small thing: the end of article marker (as well as the HUD) are displayed while loading. Probably want to turn that off by default

conflicts resolved, verified on local

The end of article maker and timebox still show up? Also the screen goes black before the prompt starts?
Lmk if you need me to reproduce these.

I can't seem to reproduce these myself, so yes pls

Fixed it myself lol, merging


new version of asde and db project

these are not tied to the new release, i will publish the changes after merge.

Lets wait for testing before uploading stable please...
... Also do we need to update one more file for RC testing?

Lets wait for testing before uploading stable please...
... Also do we need to update one more file for RC testing?

@udeeshagautam , RC gallery is copied from stable, no separate file for it

asde -> insider, stable.
sqldbproj->insider


[FEATURE] Improve the Readme.md file

Description
the Readme.md contains some info but many are missing.
this issue is for someone who knows the 4C community well
Screenshots
No response

Just for asking, is there any particular type of information that should be added to the README that is related to 4C?

we should talk about the project itself and a bit about the community. any improvement is welcome

@Njong392 Any idea how to improve the README file? @FrancescoXX Can I give a brief description of the project, and how it would be helpful for all the developers out there?

yes, can I assign this to you? @Arijit1000

yes, can I assign this to you? @Arijit1000

Yes, please assign @FrancescoXX

Any updates on this???

Any updates on this???

Yes, working on this issue

@Njong392 If you have any suggestions for me, you can go ahead and we can work together.

@Njong392 If you have any suggestions for me, you can go ahead and we can work together.

Sure thing! I'll check out your fork

@Njong392 and @Arijit1000 do you still wanna work on this?

??

I thought @Arijit1000 was on this. Don't know how far they've gone with it, I'm happy to jump in.

Sure thing Emy!! Go ahead!!

Great job once again @Njong392!!


arch/clang: add support for Clang LTO

Summary
arch/clang: add support for Clang LTO
add support of Clang's Link Time Optimization (LTO) on NuttX build system
Reference:
https://llvm.org/docs/LinkTimeOptimization.html
Signed-off-by: chao.an<EMAIL_ADDRESS>Impact
Clang + LTO
Testing

Code Size

Coremark

LVGL BenchMark

Weighted FPS

All Cases

Depends on: https://github.com/apache/incubator-nuttx/pull/6097

@anchao have you tried GCC Os + lto?

@anchao have you tried GCC Os + lto?

Not yet, will add gcc lto + link plugin support later

@anchao
I think the results are very interesting.
Please add descriptions such as CPU arch and board config to the summary.

@anchao
I think the results are very interesting. Please add descriptions such as CPU arch and board config to the summary.

@masayuki2009 architecture information and board config has been updated

@anchao have you tried GCC Os + lto?

Not yet, will add gcc lto + link plugin support later

Update performance profiling data of GCC lto on below PR:
https://github.com/apache/incubator-nuttx/pull/6123


Some UI/info suggestions

Hi, thanks as always for the site :)
For the Wii U page, can you show whether something is dlc, updates, gameapp, etc?
It's just the as as 3ds, apart from in the title id: '008c' for 3ds dlc is simply '000c' for wii u.
How about displaying the size of the game? (Just add all the data sizes from the tmd)
Although dlc and updates (and rarely the base game itself) can get updated so the size won't always be correct...
You are actually checking if each ticket is legit, verifying the signatures? That's cool if so.
It's an neat way to also verify that the title key is correct.
Is it simple to upload tickets/keys to the site, from the wii u/3ds? Nothing preventing access or submissions when not using the web page directly?
And check this title id, you have it twice, once lower case and once uppercase:
0005000010145C00
Thanks!

This is open source and I will accept pull requests. I forked this from the 3ds page when I originally moved to titlekeys.com so in time I will port back the features from the 3ds page.

You are actually checking if each ticket is legit, verifying the signatures?

Yes, this was suggested as a way to allow encrypted title keys to be uploaded into the 3DS page at some point. I will push the latest code soon.

Is it simple to upload tickets/keys to the site, from the wii u/3ds?

Yes. Myself used curl to batch upload the tickets and titlekeys originally.

That is all good to hear, thank you :hot_pepper:

Feel free to separate your requests on changes to the website out as separate issues.

Well in a way, if some things are already implemented on the 3ds side, it might be easier/fast to back port it like you say, rather than recreate them.
But sure, for new features I understand, thanks.


[Suggestion] Improvement to the delayed validation example

Currently, the delayed validation example forcibly resets $dirty, which can make other detection tricky as it's then unclear whether the fields $dirty state was set programmatically or by user input.
An alternative is to do something like this:
delayTouch($v) {
  if (touchMap.has($v)) {
    clearTimeout(touchMap.get($v))
  }

  if ($v.$error) {
    $v.$touch()
  } else {
    touchMap.set($v, setTimeout($v.$touch, 400))
  }
}

This causes the form to instantly validate if it is already in an error state, as the user tries to correct it, which make the input feel responsive, but if the form is not in an error state (i.e., its initial unvalidated state) it will delay by 400ms after input (resetting with each input).
Whilst I understand it's not up to Vuelidate to provide examples for every single scenario, given that this gives a more pleasant experience to the user and correctly maintains the $dirty state, I think it would be a worthwhile modification to the current documentation. Happy to put up a PR if you agree.

As an example, I mark form fields that are required and not dirty with a small blue "Required" badge; but once the user has made any alterations, if they then clear the field, it gets the usual red validation message saying "this field is required" or similar.


⚠ Fortnite has degraded performance

In c83e2af, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1591 ms

Resolved: Fortnite performance has improved in af149a6.


TextAnalyticsApiVersion Undefined variable

In the client declaration, the "TextAnalyticsApiVersion" enum gives a NameError, after the import of the "TextAnalyticsClient".

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

ID: 8f57e416-a37f-e719-4a3e-58a4e6390818
Version Independent ID: dbb3821b-5793-b41b-9601-559b00e4096a
Content: Quickstart: Text mining using the Text Analytics client library - Azure Cognitive Services
Content Source: articles/cognitive-services/text-analytics/quickstarts/text-analytics-sdk.md
Service: cognitive-services
Sub-service: text-analytics
GitHub Login: @aahill
Microsoft Alias: aahi

@Makrenos we'll review your feedback and get back to you shortly, thanks.

@Makrenos what version are you using?

Im using version 5.0.0. of azure-ai-textanalytics library.

@aahill specifying 'api_version=TextAnalyticsApiVersion.V3_0' results in the following error "NameError: name 'TextAnalyticsApiVersion' is not defined". Can you please review and update doc accordingly? Thanks.

Thanks for reaching out about this. the api_version param is available in v5.1.0 beta of the client library.
If your client version is v5.0.0 it will throw an error. For 5.0.0, you can use the following format
# Only use the following code sample if you're using v5.1.0 of the client library,
# and are looking to specify v3.0 of the Text Analytics API for your client
from azure.ai.textanalytics import TextAnalyticsClient, TextAnalyticsApiVersion
from azure.core.credentials import AzureKeyCredential
def authenticate_client():
   ta_credential = AzureKeyCredential(key)
   text_analytics_client = TextAnalyticsClient(
     endpoint=endpoint,
     credential=ta_credential,
     api_version=TextAnalyticsApiVersion.V3_0
   )

client = authenticate_client()

If you use v5.1.0, you can use
from azure.ai.textanalytics import TextAnalyticsClient
from azure.core.credentials import AzureKeyCredential

def authenticate_client():
    ta_credential = AzureKeyCredential(key)
    text_analytics_client = TextAnalyticsClient(
            endpoint=endpoint,
            credential=ta_credential) # use this code if your SDK version is 5.0.0
    return text_analytics_client

client = authenticate_client()

I'll work on updating the documentation.
#please-close


spec: clarify type elision rules for composite literals

Per the spec ( https://golang.org/ref/spec#Composite_literals ):
"Within a composite literal of array, slice, or map type T, elements or map keys that are themselves composite literals may elide the respective literal type if it is identical to the element or key type of T. Similarly, elements or keys that are addresses of composite literals may elide the &T when the element or key type is *T."
Given this paragraph, it's not obviously clear if the following code should be permitted:
type T *struct {
  s string
}

var _ = []T{
  { "foo" },
}

Here, the element type is a named type T that happens to be a *S. From the phrasing in the spec, it's not obvious whether the rule also applies in this case, or not (it doesn't explicitly say whether the underlying type is meant or not).
The gc and gccgo compilers accept the code above, go/types does not.
In contrast, the code below is also accepted by go/types (and clearly satisfies the spec rule).
var _ = []*struct {
  s string
}{
  { "foo" },
}

The two compilers agreeing suggests that this should (continue to) be accepted. Is there a test for this behavior that led to the compilers agreeing? If so, that would even more strongly push in that direction.
If past behavior does not determine the answer, then looking at the spec itself, there are many places in the spec that talk about 'a type T' meaning "your type here" and not meaning only named types. Otherwise there is no way to talk about "any type". The text quoted seems to be talking about arbitrary types, not only named types (it never mentions names), in which case the answer is that yes the example is OK. That is, if you think of the example as being a shortening of:
type X *struct {
  s string
}

var _ = []X{
  &struct{s string}{ "foo" },
}

(I changed the type name to avoid 'T'), then "elements ... that are addresses of composite literals may elide the &T when the element ... type is *T" seems to be satisfied. The element type X is *T for T = struct{s string}.

I would like to agree with this (and I already have an easy fix for this for go/types: https://go-review.googlesource.com/33358). But it's not that simple. Given
type Point  struct{x, y int}
type PPoint *Point

this is valid
[]*Point{{1.5, -3.5}, {0, 0}}    // same as []*Point{&Point{1.5, -3.5}, &Point{0, 0}}

Note that &Point{...} creates a value of type *Point which is identical to the element type *Point of the composite literal type []*Point.
If we allow the same rule for PPoint, we arrive at
[]PPoint{{1.5, -3.5}, {0, 0}}    // "same" as []PPoint{&?{1.5, -3.5}, &?{0, 0}}

What should the type marked with ? be? The obvious choice seems Point as above, which would create an element of type *Point. However, *Point is not identical to the element type PPoint of the composite literal type []PPoint, only assignment-compatible.
More to the point (no pun intended), we can't actually write down the element type of PPoint: There's no way to write a type T such that &T is identical to PPoint. (Fundamentally, this goes all the way back to the rule that a type declaration introduces a new, and different, type.)
The spec says very clearly:
"Within a composite literal of array, slice, or map type T, elements or map keys that are themselves composite literals may elide the respective literal type if it is identical to the element or key type of T."
In this example, the element types are not identical. Thus, I argue that gc and gccgo are incorrect.
(We may not be able to change this at this point, but then the spec has to be adjusted.)

But the sentence you are quoting is not the relevant one.  Here T is a meta-syntactic variable, and clearly the second clause does not apply--the type of the elements is not, and can not be, type PPoint.  For a pointer type, it's the second sentence that governs: "Similarly, elements or keys that are addresses of composite literals may elide the &T when the element or key type is *T."  Here the element type is *PPoint, so we are permitted to elide the &T.  It is true that there is no T we could properly write there, but, good news!  We can elide it.  So at least so far I am with Russ in thinking that this is OK.

@ianlancetaylor Fair point, I quoted the wrong sentence. The element type is PPoint (rather than *PPoint as you said, though). I guess we could write PPoint(&Point{x, y}) and thus elide the PPoint(&Point ... ) part.

But putting it another way, if we don't allow
[]PPoint{{1, 2}}

there would be no way to actually write a composite literal of type []PPoint.


Add custom hydration directive

Implements custom hydration directives using a definition transformer.

Will most likely be superceded by #635
Will close this once that's merged.


MINOR: fixes on streams upgrade test

In test_upgrade_downgrade_brokers, allow duplicates to happen.
In test_version_probing_upgrade, grep the generation numbers from brokers at the end, and check if they can ever be synchronized.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Runs system tests a couple of times and succeeds.

@vvcephei @bbejeck please take another look.
I am running system tests at the same time.

System test passed: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/2001/


Bug Fix of Mobile View (Blog page)

Related Issue

Information about the related issue

Closes: #697
Describe the changes you've made

Type of change
What sort of change have you made:

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Code style update (formatting, local variables)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update.
[ ] This change requires a documentation update

How Has This Been Tested?

Checklist

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented on my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

Screenshots (if applicable)
Code of Conduct

[x] I agree to follow this project's Code of Conduct

@amanjaiman1

@amanjaiman1 yeh merge kardo tumare repo me bug tha ...

@PatilHarshh Desktop version m kharab hogaya bhai


[QUERY] How to update Network Security Group with new SDK

Library name and version
Azure.ResourceManager.Network 1.0.1
Query/Question
How are we supposed to update a network security group with a list of DestinationAddressPrefixes, DestinationPortRanges, SourceAddressPrefixes or SourcePortRanges?
This was possible in the old SDK, but now those properties seem to be get only.
Environment
net6
VS2022

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'ARM:0.5505122,Compute:0.03756801,Search:0.025651367'

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Hi @davidobrien1985, according to the .NET design guideline, we don't provide setter for the collection type, please call the Add() method to add values, you can see more details here about how to initialize the collection read-only property.


Need more description regarding decryption init request challenge than just UML flow

https://github.com/crypto-com/chain-docs/blame/master/plan.md#L214-L215
"Client/Wallet" -> TQE: decryption init request
TQE -> "Client/Wallet": decryption init request challenge

has no further details.

@CeruleanAtMonaco https://github.com/crypto-com/chain/blob/master/enclave-protocol/src/lib.rs#L215

audit report ?


Switch partitionsFor() etc to non-blocking versions

From the Kafka documentation:

Overloads have also been added for other KafkaConsumer methods like partitionsFor, listTopics, offsetsForTimes, beginningOffsets, endOffsets and close that take in a Duration.

"Non-blocking"? How do they mean?
public void close(Duration timeout) {
        if (timeout.toMillis() < 0)
            throw new IllegalArgumentException("The timeout cannot be negative.");
        acquire();
        try {
            if (!closed) {
                closed = true;
                close(timeout.toMillis(), false);
            }
        } finally {
            release();
        }
    }

...
  try {
            if (coordinator != null)
                coordinator.close(Math.min(timeoutMs, requestTimeoutMs));
        } catch (Throwable t) {
            firstException.compareAndSet(null, t);
            log.error("Failed to close coordinator", t);
        }
        ClientUtils.closeQuietly(fetcher, "fetcher", firstException);
        ClientUtils.closeQuietly(interceptors, "consumer interceptors", firstException);
        ClientUtils.closeQuietly(metrics, "consumer metrics", firstException);
        ClientUtils.closeQuietly(client, "consumer network client", firstException);
        ClientUtils.closeQuietly(keyDeserializer, "consumer key deserializer", firstException);
        ClientUtils.closeQuietly(valueDeserializer, "consumer value deserializer", firstException);
        AppInfoParser.unregisterAppInfo(JMX_PREFIX, clientId, metrics);
        log.debug("Kafka consumer has been closed");

I don't see any async interaction...
More over looks like all those non-Duration APIs just delegate to the Duration-based:
public List<PartitionInfo> partitionsFor(String topic) {
       return partitionsFor(topic, Duration.ofMillis(defaultApiTimeoutMs));
}

What am I missing? Why doesn't that look for me as non-blocking?
Thanks

We should also decide whether a TimeoutException is fatal for start() when checking for the existence of the partitions.

OK. All sounds good. Although I don't think that org.apache.kafka.common.errors.TimeoutException should be considered in boundaries of this issue.
But I'm not so good in guessing what you have in mind about Kafka 😄
Thanks for sharing your thoughts!


Add base test classes to help with adding new temp scales

Is your feature request related to a problem? Please describe.
The tests for the From() and To()` classes are very long and will only get bigger. When I add a new temp scale, adding more tests is very hard and time consuming.
Describe the solution you'd like
I would like some base classes that have a set of properties and tests already available. So, all I have to do is add a class that inherits from the base tests and add any additional tests I think are relevant to the temp scale I am adding.
Describe alternatives you've considered
I've already been adding tests as I went when I added the previous temp scales. They take a lot of time.
Additional context
The base class for the From() extensions would start like this:
public abstract class BaseFromExtensionTests<TInputType, TOutputType>
    where TInputType : struct
    where TOutputType : TypeBase<TInputType>

It would contain a few properties that could be expanded on for the To() tests.
    protected virtual TInputType HighValue { get; }
    protected virtual TInputType MidHighValue { get; }
    protected virtual TInputType MidValue { get; }
    protected virtual TInputType MidLowValue { get; }
    protected virtual TInputType LowValue { get; }

The classes that would inherit from the base class would have to override the ConvertFrom() method.
Base Class:
protected abstract TOutputType ConvertFrom(TInputType value);
Overridden version:
    protected override CelsiusDouble ConvertFrom(
        double value)
    {
        return value.FromCelsius();
    }

I have done this work - well started it and done a few test classes. It looks like it is working well.

The To() extension tests are not going well.

I have made some headway with the To() base test methods. These are for same value tests and simple checks.
The next stage is to add a way to have a collection of inputs and the respective "expected" converted values.
My thoughts at the moment are having abstract methods in the base class for an input (using a generic type) and a DTO that contains all of the expected values when converted. The method could have a collection of these input/output items that might be used in a Theory test.


maxW{Size} not working

The maxW{Size} does not seem to work (typescript has typings for these, and the docs suggest t.maxW{Size} should work):
https://tvke.github.io/react-native-tailwindcss/sizing/max-width.html
console.log(tw.maxW3);

undefined

The named units work though:
console.log(tw.maxWXs);

Object {
  "maxWidth": 320,
}

Hi @markstreich
I think you ment to use tw.maxW3xl as there is no option tw.maxW3 in the docs
greetings
Thomas

@TVke Thanks, there are typescript entries for example for tw.maxW3 though.
https://github.com/TVke/react-native-tailwindcss/blob/721c3699b1b421bf0e937012f5436a89d62f0004/index.d.ts#L3282
If nothing else, might be an inconsistency in the typescript types?

Hi @markstreich
There are indeed inconsistencies in the typescript definition and theere are 2 PR's working to improve it.
For now I am going to leave it but if I have the time I will maken an intermediate PR to fix the typescript problems.
greetings
Thomas

Thanks! For my needs it’s not urgent at all, I’m keeping an eye on the pending PRs.