Interop with FreeSWITCH's "NDLB-connectile-dysfunction"

When trying to place a call to the soft client via WSS, FreeSWITCH reports "NORMAL_TEMPORARY_FAILURE"
the lines look like this
68c1c893-62c2-4035-823c-c19b90232960 2014-08-17 10:47:50.066431 [NOTICE] sofia.c:7286 Hangup sofia/internal/sip:ck4vtuei@<IP_ADDRESS>:57566 [CS_CONSUME_MEDIA] [NORMAL_TEMPORARY_FAILURE]
I can call a regular sip client just fine, and even using SipML5 (which we had been previously using) works without issues.
This is also affecting presence subscriptions (no messages are seen).
Changing over to WS, calls and presence both start working.
I would attach JS SIP Traces and wiresharks, but JS SIP traces never show a call attempt, and because its HTTPS/WSS wire shark is pretty much useless (unless someone knows how to decrypt the streams).
What testing has been done against WSS, am i missing something that could potentially be killing me?
Unfortunately using WS is not really an option because you cannot connect to WS from HTTPS due to security restrictions.
Outbound calling works flawlessly on both WS and WSS.
In the mean time, i will start investigating the code to see if i can generate any sort of output.

We will be resuming development on our soft client in December, if during that time we find a resolution on either end i will update this issue...
Has anything come out of that?

@wakamoleguy
We had to push development off a little bit, we've resumed it just recently but we don't have any time slated for looking into this.
I did some very basic tests and didn't get anywhere.  We want to address this once we have some more time available as we're going to be advertising it as highly secure, and it'll be our main push for people who don't want to buy hardware phones.

This interests me as well and I've started looking into it.
Very preliminary dive points to the default case in the switch statement checking the method var within the US.prototype.receiveRequest method.
I'll be digging in at some point this week and let you know what I find

For anyone still experiences issues with this setting in FreeSWITCH as I was, if you set

hackWssInTransport: true

in your ua configuration then you will be able to successfully make inbound and outbound calls with wss.
This workaround does make it so you cannot make inbound calls (calls to the soft client) using regular ws however. Which is the opposite of the original issue of not being able to make inbound calls with wss. As wss is more secure anyways I see this as an okay tradeoff because you can just always enforce wss.
I've done minimal testing on this, but I will report back if I find any issues with this.

My conclusion at the moment is that we are not compatible with FreeSWITCH NDLB (no device left behind). This is turned on or off based on the individual user registering and should be off by default. The purpose of the option in FreeSWITCH is to support devices that have bad behavior with certain headers and params or for networks with NAT problems etc. Since SIP.js is establishing a socket based connection to FreeSWITCH and SIP.js correctly deals with SIP headers no NDLB options should be required. To make SIP.js behave correctly NDLB would be a backwards move. I am going to close this issue, but if there are more questions definitely feel free to continue this thread.


Abbot chimes in every N messages (Nostr)

Requirements
Telegram

2 new slash commands: unleash and leash
[x] 1. /unleash

takes an optional argument that must be an integer
default is 5 if no arg passed
sets DM keys "config.unleashed" = true and "count" = arg | 5 to turn on the feature
arg = how many messages abbot waits before chiming in

[x] 2. /leash

takes an optional argument that must be an integer
default is None if no arg passed, don't change the count
sets DB keys "config.unleashed" = false to turn off the feature

Nostr
TBD

Telegram complete with this commit: https://github.com/ATLBitLab/abbot/commit/483b24d5c8caea0c26f9ed4539f5fada7c6516a7


It seems there are no 3D operations in DebiasHead.

It seems that the debiashead is used to implement CED.
But it seems no 3D operations  though some modules (self.f1_conv3d, self.f2_conv3d) are named with '3D'. Because the temporal size of conlolution kenerls is 1.
In this way , shuffling the feat actually won't make any sense.  Actually  it seems no difference between this three branch: 1.(f1_conv3d-->avg_pool-->fc1), 2.(temporal shuffling-->f2_conv3d-->avg_pool-->fc2) 3.(reshape-->f3_conv2d-->avg_pool-->fc3).
Here is the code in

https://github.com/Cogito2012/DEAR/tree/master/mmaction/models/heads/debias_head.py:

@HEADS.register_module()
class DebiasHead(BaseHead):
    """Debias head.

    Args:
        num_classes (int): Number of classes to be classified.
        in_channels (int): Number of channels in input feature.
        loss_cls (dict): Config for building loss.
            Default: dict(type='EvidenceLoss')
        spatial_type (str): Pooling type in spatial dimension. Default: 'avg'.
        dropout_ratio (float): Probability of dropout layer. Default: 0.5.
        init_std (float): Std value for Initiation. Default: 0.01.
        kwargs (dict, optional): Any keyword argument to be used to initialize
            the head.
    """

    def __init__(self,
                 num_classes,
                 in_channels,
                 loss_cls=dict(type='EvidenceLoss'),
                 loss_factor=0.1,
                 hsic_factor=0.5,  # useful when alternative=True
                 alternative=False,
                 bias_input=True,
                 bias_network=True,
                 dropout_ratio=0.5,
                 init_std=0.01,
                 **kwargs):
        super().__init__(num_classes, in_channels, loss_cls, **kwargs)
        self.bias_input = bias_input
        self.bias_network = bias_network
        assert bias_input or bias_network, "At least one of the choices (bias_input, bias_network) should be True!"
        self.loss_factor = loss_factor
        self.hsic_factor = hsic_factor
        self.alternative = alternative
        self.f1_conv3d = ConvModule(
            in_channels,
            in_channels * 2, (1, 3, 3),
            stride=(1, 2, 2),
            padding=(0, 1, 1),
            bias=False,
            conv_cfg=dict(type='Conv3d'),
            norm_cfg=dict(type='BN3d', requires_grad=True))
        if bias_input:
            self.f2_conv3d = ConvModule(
                in_channels,
                in_channels * 2, (1, 3, 3),
                stride=(1, 2, 2),
                padding=(0, 1, 1),
                bias=False,
                conv_cfg=dict(type='Conv3d'),
                norm_cfg=dict(type='BN3d', requires_grad=True))
        if bias_network:
            self.f3_conv2d = ConvModule(
                in_channels,
                in_channels * 2, (3, 3),
                stride=(2, 2),
                padding=(1, 1),
                bias=False,
                conv_cfg=dict(type='Conv2d'),
                norm_cfg=dict(type='BN', requires_grad=True))
        self.dropout_ratio = dropout_ratio
        self.init_std = init_std
        if self.dropout_ratio != 0:
            self.dropout = nn.Dropout(p=self.dropout_ratio)
        else:
            self.dropout = None
        self.f1_fc = nn.Linear(self.in_channels * 2, self.num_classes)
        self.f2_fc = nn.Linear(self.in_channels * 2, self.num_classes)
        self.f3_fc = nn.Linear(self.in_channels * 2, self.num_classes)
        self.avg_pool = nn.AdaptiveAvgPool3d((1, 1, 1))

     .............
        def forward(self, x, num_segs=None, target=None, **kwargs):
        """Defines the computation performed at every call.

        Args:
            x (torch.Tensor): The input data. (B, 1024, 8, 14, 14)

        Returns:
            torch.Tensor: The classification scores for input samples.
        """
        feat = x.clone() if isinstance(x, torch.Tensor) else x[-2].clone()
        if len(feat.size()) == 4:  # for 2D recognizer
            assert num_segs is not None
            feat = feat.view((-1, num_segs) + feat.size()[1:]).transpose(1, 2).contiguous()
        # one-hot embedding for the target
        y = torch.eye(self.num_classes).to(feat.device)
        y = y[target]
        losses = dict()

        # f1_Conv3D(x)
        x = self.f1_conv3d(feat)  # (B, 2048, 8, 7, 7)
        feat_unbias = self.avg_pool(x).squeeze(-1).squeeze(-1).squeeze(-1)
        x = self.dropout(feat_unbias)
        x = self.f1_fc(x)
        alpha_unbias = self.exp_evidence(x) + 1
        # minimize the edl losses
        loss_cls1 = self.edl_loss(torch.log, alpha_unbias, y)
        losses.update({'loss_unbias_cls': loss_cls1})

        loss_hsic_f, loss_hsic_g = torch.zeros_like(loss_cls1), torch.zeros_like(loss_cls1)
        if self.bias_input:
            # f2_Conv3D(x)
            feat_shuffle = feat[:, :, torch.randperm(feat.size()[2])]
            x = self.f2_conv3d(feat_shuffle)  # (B, 2048, 8, 7, 7)
            feat_bias1 = self.avg_pool(x).squeeze(-1).squeeze(-1).squeeze(-1)
            x = self.dropout(feat_bias1)
            x = self.f2_fc(x)
            alpha_bias1 = self.exp_evidence(x) + 1
            # minimize the edl losses
            loss_cls2 = self.edl_loss(torch.log, alpha_bias1, y)
            losses.update({'loss_bias1_cls': loss_cls2})
            if self.alternative:
                # minimize HSIC w.r.t. feat_unbias, and maximize HSIC w.r.t. feat_bias1
                loss_hsic_f += self.hsic_factor * self.hsic_loss(feat_unbias, feat_bias1.detach(), unbiased=True)
                loss_hsic_g += - self.hsic_factor * self.hsic_loss(feat_unbias.detach(), feat_bias1, unbiased=True)
            else:
                # maximize HSIC
                loss_hsic1 = -1.0 * self.hsic_loss(alpha_unbias, alpha_bias1)
                losses.update({"loss_bias1_hsic": loss_hsic1})

        if self.bias_network:
            # f3_Conv2D(x)
            B, C, T, H, W = feat.size()
            feat_reshape = feat.permute(0, 2, 1, 3, 4).contiguous().view(-1, C, H, W)  # (B*T, C, H, W)
            x = self.f3_conv2d(feat_reshape)  # (64, 2048, 7, 7)
            x = x.view(B, T, x.size(-3), x.size(-2), x.size(-1)).permute(0, 2, 1, 3, 4)  # (B, 2048, 8, 7, 7)
            feat_bias2 = self.avg_pool(x).squeeze(-1).squeeze(-1).squeeze(-1)
            x = self.dropout(feat_bias2)
            x = self.f3_fc(x)
            alpha_bias2 = self.exp_evidence(x) + 1
            # minimize the edl losses
            loss_cls3 = self.edl_loss(torch.log, alpha_bias2, y)
            losses.update({'loss_bias2_cls': loss_cls3})
            if self.alternative:
                # minimize HSIC w.r.t. feat_unbias, and maximize HSIC w.r.t. feat_bias2
                loss_hsic_f += self.hsic_factor * self.hsic_loss(feat_unbias, feat_bias2.detach(), unbiased=True)
                loss_hsic_g += - self.hsic_factor * self.hsic_loss(feat_unbias.detach(), feat_bias2, unbiased=True)
            else:
                # maximize HSIC
                loss_hsic2 = -1.0 * self.hsic_loss(alpha_unbias, alpha_bias2)
                losses.update({"loss_bias2_hsic": loss_hsic2})

        if self.alternative:
            # Here, we use odd iterations for minimizing hsic_f, and use even iterations for maximizing hsic_g
            assert 'iter' in kwargs, "iter number is missing!"
            loss_mask = kwargs['iter'] % 2
            loss_hsic = loss_mask * loss_hsic_f + (1 - loss_mask) * loss_hsic_g
            losses.update({'loss_hsic': loss_hsic})

        for k, v in losses.items():
            losses.update({k: v * self.loss_factor})
        return losses

@RongchangLi Thanks for pointing out this issue.
Yes, you're right, this is a mistake when implementing the module. The size of kernels for self.f1_conv3d, self.f2_conv3d, and self.f3_conv2d can all be set to 3. The code lines as pointed are updated.
After making this change, the results on HMDB-51 show around 0.7% and 0.2% drop in terms of Open maF1 and Open Set AUC when compared to the results reported in the main paper.

Open maF1
Open Set AUC
Closed Set Acc

76.52 (0.17)
76.81
94.03

@RongchangLi Thanks for pointing out this issue.

But  3D operations seem essential for debias operations. When the three branch are the same, it doesn't seem to have the ability to remove static bias shown in the paper. I am confused why it still works and the performance drops after debugging?

If the three branches are using Conv2D, the loss functions will remove the appearance bias. For example, you may say that in an implicit way, the middle branch learns the foreground appearance feature while the rest two branches learn the background appearance feature.
For the performance drop, it could be explained that Conv3D features are not optimally learned since I did not change any hyperparameters that are tuned based on the previous implementation.

If the three branches are using Conv2D, the loss functions will remove the appearance bias. For example, you may say that in an implicit way, the middle branch learns the foreground appearance feature while the rest two branches learn the background appearance feature.
For the performance drop, it could be explained that Conv3D features are not optimally learned since I did not change any hyperparameters that are tuned based on the previous implementation.

This article is insightful.So I want to discuss some issues in more detail. Is it too subjective to think that implicit elimination of appearance bias has occurred? When all three branches are 2D, the inputs of the three branches are high-order features extracted from the same spatial-temporal network, and the structure of the three branches is the same and simple (consisting of only one convolution, pooling, and fully-connected layer). The only difference is that the loss function makes the output of one branch different from the outputs of the other two branches. Why can we say that this process eliminates appearance bias?

If the three branches are using Conv2D, the loss functions will remove the appearance bias. For example, you may say that in an implicit way, the middle branch learns the foreground appearance feature while the rest two branches learn the background appearance feature.
For the performance drop, it could be explained that Conv3D features are not optimally learned since I did not change any hyperparameters that are tuned based on the previous implementation.

This article is insightful.So I want to discuss some issues in more detail. Is it too subjective to think that implicit elimination of appearance bias has occurred? When all three branches are 2D, the inputs of the three branches are high-order features extracted from the same spatial-temporal network, and the structure of the three branches is the same and simple (consisting of only one convolution, pooling, and fully-connected layer). The only difference is that the loss function makes the output of one branch different from the outputs of the other two branches. Why can we say that this process eliminates appearance bias?

I see your points. In this case, the middle branch and the others will learn to give two sets of features, which are independent of each other but both discriminative for classification. Without explicit inductive bias (like the Conv2D/shuffle vs Conv3D) in the design, we indeed cannot claim the debiasing effect.

Thank you very much for your patiently explaining.  It helps a lot.


download problem

hi i'm trying to dowlnload the lastest release but i can't.
If i use the link in the README file i got the following messege:   404: Not Found
i'm new here and i just wanna complete cucumber's course

Hi @alebaqueroben, you're trying to complete one of the courses at https://school.cucumber.io/, is that right?
Can you say which course and lesson you were on when you tried to download the code and got a 404?

Hi @mattwynne, yeah thats right, i'm doing BDD with Cucumber (Java) and i'm in thew "Your first escenario part".
I tryed to follow the instruccions and download the files but i can't. I arrived to this URL and i don't know how to continue:
https://github.com/cucumber-school/bdd-with-cucumber/tree/main/content/02/code/java/01-skeleton-unzipped/cucumber-java-skeleton-5.2.0


fixing name for python unit tests in ppa

For third task of https://github.com/Princeton-CDH/ppa-django/issues/489

Tests are failing but I'm pretty sure that's not the fault of this change?

Tests are failing but I'm pretty sure that's not the fault of this change?

No, it's not related. I'll try to figure out why they're failing, maybe can address when I clean up the old prosody playbooks.


Pull Refresh is messed with Pull Indicator.

Pull indicator still appears even RefreshControl is used.
Will try to see and debug this issue

ok, thanks for your report, I will fix this next week~~~

This has been fixed in version1.1.1, so I close this issue, if you still has problem tell me please.


font files are copied into the root directory on render

When rendering the wiley-njd-example.qmd it appears that all of the fonts from the _extensions/ramiromagno/wiley-njd/wiley-njd-v5/Fonts folder are copied into the root directory.
I'm presuming this might a requirement for rendering but wondering if it might be possible to clean up all of these files after render is completed? It would be nice not to have all of those font files clutrering the root directory.

Hi @jmlondon,
I apologize for the delayed response.
If this issue is still relevant to you, could you please check if the fonts are still located in the root directory?

Related to https://github.com/quarto-dev/quarto-cli/issues/1460.

I haven't revisited this in a while but will make some time to check with the latest versions.

Thank you. I think the issue persists. I'm looking for a workaround.


Fix e2e test while combining data from multiple maintenaces

This looks good to me!

This looks good to me!

if so, could you approve the PR?


feat: support "remove" of any array index

WDYT?
(no tests yet)

Coverage decreased (-1.8%) to 91.523% when pulling f7fa0f1acb6d0db760687a6bfe2386f58fc164f6 on aleclarson:feat2 into c41b4ab215f4cab31c7f4650da3d099c9408c6bd on mweststrate:master.

Eh no it doesn't :-). Will accept PR though if you add some tests for the specific cases (the coverage report is a great way to verify that all of them are covered!)

Yes
Op za 13 okt. 2018 02:48 schreef Alec Larson<EMAIL_ADDRESS>
@aleclarson commented on this pull request.
In src/patches.js
https://github.com/mweststrate/immer/pull/210#discussion_r224943924:

                       throw new Error(

                           `Remove can only remove the last key of an array, index: ${key}, length: ${

                               base.length

                           }`

                       )

               } else delete base[key]

                   const index = Number(key)

                   if (!Number.isNaN(index)) {

                       if (index < 0 || index > base.length) {

                           throw new Error(

                               "Invalid array patch: The given index is out of bounds"

                           )

                       }

                       if (index === 0) {

                           base.shift()

                           break

Oh I suppose you mean to break this out into its own function?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mweststrate/immer/pull/210#discussion_r224943924, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABvGhGaKFYXf_sooNZ1L8dbRMqR3I6vFks5ukThEgaJpZM4XGvjJ
.

Closing this for now.


Fix QuickStatus selector

Coverage: 93.93% (-0.01%) from 93.944% when pulling d629901da183107777f6e18996faa37c9e0378e3 on cody-fix-quick-status-selector into 1b5b1aea055bf44bae9f9f433e47270d1813d6d1 on main.


:construction: wip

Here are links to notebooks available in this branch:

Notebook
Colab

1_example.ipynb


Changing install name can break the binary

MachOFile#change_install_name corrupts load commands in the sense that it doesn't preserve the type of the command when changing the name. This will happen rarely, but wen it does, it usually changes semantics and thus breaks the binary. (Sorry I missed this earlier in review.)
Steps to reproduce:
$ echo "void foo() {}" > lib.c
$ clang -dynamiclib -o libtest.dylib -Wl,-reexport-lz lib.c
$ otool -l libtest.dylib > otool-old.log
$ ruby -Ilib -rmacho -e 'MachO::Tools.change_install_name("libtest.dylib", "/usr/lib/libz.1.dylib", "does_not_matter")'
$ otool -l libtest.dylib > otool-new.log

Notice how LC_REEXPORT_DYLIB has changed to LC_LOAD_DYLIB:
diff --git 1/otool-old.log 2/otool-new.log
index 55435787..62636422 100644
--- 1/otool-old.log
+++ 2/otool-new.log
@@ -109,9 +109,9 @@ Load command 8
   cmdsize 16
   version 0.0
 Load command 9
-          cmd LC_REEXPORT_DYLIB
-      cmdsize 48
-         name /usr/lib/libz.1.dylib (offset 24)
+          cmd LC_LOAD_DYLIB
+      cmdsize 40
+         name does_not_matter (offset 24)
    time stamp 2 Thu Jan  1 01:00:02 1970
       current version 1.2.5
 compatibility version 1.0.0

cc @woodruffw

Luckily, this is a single-line fix in MachOFile#change_install_name:
LoadCommand.create(:LC_LOAD_DYLIB, ...)

to
LoadCommand.create(old_lc.type, ...)

PR will be ready in a few minutes :smile:


Add TTL

Add TTL signals from Axon Binary Format (ABF) file

requires #38

need to double check excitation sources, assumed here it is the same as the previous experiment (Azcorra dataset)

example file also contains the optogenetic data from #38 and raw data from #21


Feature/issue 23 - Restructured Project to Suit Tutor Guidelines

#23  I have restructured the project and added some Docker files. I believe we can get started with this. I will set up Docker Compose for the project before the end of the week. It should make development a lot easier. I also set up the database shortly.

@MrDecipher I prefer docker not docker compose because it has many unnecessary files and folders. Please just put the Docker files and some guidelines to start the container, that suffices.


186208247-revert-id-change

The id change broke comments on curriculum tiles.
With this id change, if a tile doesn't have an id then one was randomly assigned when it is loaded. There are several curriculum files that do not have ids on all of their tiles, so each time one of these was loaded the tile would get a different id. When a comment is made on a tile it is associated with this id. So comments on these id-less tiles would not match any tile when viewed on a new instance of CLUE.
With this reversion PR, the tile ids will again be set deterministically based on their type and index in the section. This means that comments will continue to match up with the tile in the curriculum. However this approach is fragile, if a new tile is inserted into the curriculum the indexes of tiles after it will change so their ids will change and then the comments will get messed up.  Additionally when the content is loaded the ids currently need to be unique across the whole unit not just the section so this can result in id conflicts.
Even with these downsides reverting seems like the right thing to do for now, and then we can look for better solutions later.
I can think of a few solutions, but each has up and downsides.
Assign ids to all of the content
This way ids will not change at runtime.  New tiles added by authors using the authoring system already have unique ids.
Authors could still add tiles manually by editing the json and they might forget to add an id. To resolve this, we could add a check in GitHub based deployment of the content to make sure it has ids before it is deployed.
Downsides
Old comments on curriculum would be broken unless we also migrate these comments within Firestore.
The logs of making these comments would be broken unless we migrate the logs.
Doing these migrations won't be perfect since the actual tile ids might have changed when the curriculum was modified.  To be super safe we'd have to compare the date the tile was created with the content at this date.
Prevent id conflicts while loading the content
The id conflict that caused this problem to start with could be avoided by changing the runtime. I didn't realize this before. The conflict happened because we load the whole unit into one MST tree. When we actually use the sections of the unit they are in separate trees. So if we avoid loading the whole unit the id conflict wouldn't happen.
As long as authors only edit content in the authoring system, this might not break existing comments. This is because when the authoring system loads the content the deterministic id will be assigned. When they save the content these deterministic ids will be saved into the content. Even if they re-order the tiles the ids will remain how they were initially loaded so any comments will still point at the correct tile. If they add a new tile it will be given a random id.
We could migrate the authored content to explicitly assign these deterministic ids. This migration could identify cases of id conflicts which could still happen if content has been copied from one sections to another in the past. If we do this then we could add an id check in GitHub before the content is deployed. This would prevent any manual edits from breaking things.
Downsides
If we don't migrate the authored content and add the id check. We could still get id conflicts when authors manually edit the JSON.
Only assign random ids at authoring time
We could just assign random ids in the authoring system. This way the deterministic ids would still be used at runtime for any tile that doesn't have an explicit id. So as long as the authored content doesn't change the comments should continue to match up.
Downsides
When an author edits a section that doesn't have explicit ids, random ids will be assigned to all tiles when it is saved. Now any comments that have been made on the old version of this section will no longer match up.

I'm not sure why the codecov/* checks are there twice. It is probably related to the delayed running of the regression tests.

@tejal-shah Because this fixes broken tests on master and is just going back to what we had before, I'm going to merge it without waiting for a QA review.


Question about why the predict noise is used ?

InST  is a great work! Thanks for your great work  and releasing your  code . But  i feel a little  confused that   content image is added the predicted noise , and why the predict noise is used instead of the stochastic noise? Thanks for your reply.

Hi. This is to maintain the content structure of the image, i.e. to reduce the impact of bias when adding noise on the content image.


Python Taint Flow: False negative when taint originates in default value of function argument

I'm trying to catch CVE-2019-19775 with CodeQL. The flow is from the REQ function called to create the default argument value, to the redirect function call:
@has_request_variables
def backend_serve_thumbnail(request: HttpRequest, user_profile: UserProfile,
                            url: str=REQ(), size_requested: str=REQ("size")) -> HttpResponse:
    ...
    thumbnail_url = generate_thumbnail_url(url, size)
    return redirect(thumbnail_url)

This is the code I've been using (yes I know I'm reinventing the wheel, but I wanted to make the example self contained and do some sanity checking):
import python
import semmle.python.security.TaintTracking
import semmle.python.web.HttpRequest

class ZulipReqSource extends TaintTracking::Source {
    ZulipReqSource() {
        exists( FunctionValue f | f.getName() = "REQ" and f.getACall() = this)
    }
    override predicate isSourceOf(TaintKind kind) { kind instanceof DjangoRequest }
    override string toString() { result = "Zulip's custom 'Req' source" }
}

class RedirectSink extends TaintTracking::Sink {
    RedirectSink() {
        Module::named("django").attr("redirect").getACall().getArg(0) = this
    }
    override predicate sinks(TaintKind kind) {
        kind instanceof DjangoRequest
    }
    override string toString() { result = "Django's redirect sink" }
}

class UrlRedirectConfiguration extends TaintTracking::Configuration {
    UrlRedirectConfiguration() { this = "URL redirect configuration" }
    override predicate isSource(TaintTracking::Source source) {
        source instanceof ZulipReqSource
    }
    override predicate isSink(TaintTracking::Sink sink) {
        sink instanceof RedirectSink
    }
}

from UrlRedirectConfiguration config, TaintedPathSource src, TaintedPathSink sink
where config.hasFlowPath(src, sink)
select sink.getSink() , src, sink, "This argument to 'unsafe' depends on<EMAIL_ADDRESS>src.getSource(), "a user-provided value"

I can't seem to catch the flow when running on the Zulip database from lgtm.com. As best I can tell, I think taint flow through the defaulted parameter might not be being tracked properly. If I run the above code, but swap generate_thumbnail_url for REQ, it works and I am able to catch the flow from generate_thumbnail_url -> redirect

What happens if you put thumbnail_url = url? I'm wondering if what you're seeing is the fact that the taint is getting lost during the call to generate_thumbnail_url.
In general, function calls do not preserve taint, unless we can figure out (by an examination of the function) that taint is preserved all the way through. The function generate_thumbnail_url is fairly complicated, and in turn depends on urllib, so my guess is that somewhere in all of this URL manipulation, the taint is getting lost.
If you know that a function should preserve taint, you can always tell the taint analysis this explicitly by adding an additionalFlowStep(src, dest) method to your configuration.

What happens if you put thumbnail_url = url?

@tausbn, is there a way for me to rebuild the database after modifying the code? I'm using a database from lgtm.com right now. Happy to follow the docs if you can give me a link.
As an attempt to test your theory within the constraints of not regenerating the database, I modified the above code to make the first argument of `` a sink:
class RedirectSink extends TaintTracking::Sink {
    RedirectSink() {
        // This is the only line I changed:
        exists( FunctionValue f | f.getName() = "generate_thumbnail_url" and f.getACall().getArg(0) = this)
    }
    override predicate sinks(TaintKind kind) {
        kind instanceof DjangoRequest
    }
    override string toString() { result = "Django's redirect sink" }
}

I tested the source and sink definitions seperately like this, and confirmed they returned the expected REQ() and generate_thumbnail_url(...) calls:
from TaintSource source
where source instanceof ZulipReqSource
select source

and
from TaintSink source
where source instanceof RedirectSink
select source

When querying for the flow from REQ() -> arg 0 of generate_thumbnail_url, I still get no results.

For creating databases, you can use the CodeQL CLI. See here for information on how to set it up, as well as the licensing terms that apply.
I just tried out a small test case, and I think you're right that we are not handling taint flow from default arguments correctly. In the short term, this may be possible to fix by defining additional taint flow steps (as I mentioned above). I'm working on a fix for the libraries themselves, but this change will likely take a few weeks before it goes live on LGTM.com.


DOC: stats: Fix LaTeX markup of a couple distribution PDFs.

The ncf_gen one is a nasty one. I think the initial \exp brackets also require \left and \right but I would also propose to maybe group the square root terms as the following

Thanks Warren!


Redesign the home page into a more modern look and feel (e.g., use different Jekyll template or React)

We've made some changes to the home page: added a home page image, streamlined the information, made the TOC scroll-able and sticky, and added a feedback mechanism and comment field. Common navigation is in progress. As we start to incorporate OUI components, we'll create new issues.


Unable to export Reports

When i click on export the xls file is not downloading in app,when i open in browser its downloading.

I believe there are some limitations of the webview in the app.

The same with me , it's not working when I click on export on manager(android) nothing happens while on browser it works , is it solved yet ? @tananaev


Dependabot cannot update to the required version (Failed to create a security fix)

I found one dup but its closed.

Package manager/ecosystem
JavaScript (Firebase)
Manifest contents prior to update
package.json
Updated dependency

What you expected to see, versus what you actually saw
I expect the dependent bot should provide a fix and create a pull request. Dependent unable to create a security fix. see the screenshot above.
Images of the diff or a link to the PR, issue or logs
image is above repo is https://github.com/darkRaspberry/Forest

Hi @darkRaspberry, in this case this is working as expected. Dependabot cannot create an automated fix, because firebase-admin depends on a version of node-forge of ^0.7.6 and google-p12-pem relies on version ^0.9.0.
If you click View details about this error the message there should have some info about this.


[WIP] Implement chunk-prove in run-testnet and add gpu Dockerfile

Use https://github.com/scroll-tech/mass-testing/pull/1


Postgres example in feature/bodyparser, not merged to master

The readme in master does link to the file, as though it has been merged
https://github.com/rustless/rustless/blob/feature/bodyparser/examples/postgres/src/main.rs

Hello @bguiz 	! It's is separate crate now. I'll fix the link, thanks for your report.

Thanks!


Add guide on operators and observables

Fixes #3575. (Perhaps #1550 as well.)
As mentioned in the notebook, the intended audience for this guide is someone already familiar with these concepts, just not how they are defined/used in Cirq.
Let me know @balopat how close this is to what you had in mind! Comments and feedback of course welcome.

Now ready for review.
I learned that PauliSumCollector.collect which uses asyncio doesn't always mix well with notebooks - throws RuntimeError: This event loop is already running or a more mysterious papermill error (KeyError: 'language_info') - but collect_async seems to work fine.

Now ready for review.
I learned that PauliSumCollector.collect which uses asyncio doesn't always mix well with notebooks - throws RuntimeError: This event loop is already running or a more mysterious papermill error (KeyError: 'language_info') - but collect_async seems to work fine.

I wonder if we want to talk about projectors (cirq.KET_IMAG.projector()) here too?

Seems like a good idea - probably in the section on measurements? I'm thinking of a simple example showing measurements in a different basis, after describing cirq.measure_state_vector and cirq.measure_density_matrix which measure in the Z basis. Something like
prob_plus = np.trace(cirq.KET_PLUS.projector() @ rho).real

where rho is the same single-qubit density matrix from the previous example. Or maybe a two-qubit example is better. Is this what you had in mind?

I wonder if we want to talk about projectors (cirq.KET_IMAG.projector()) here too?

Seems like a good idea - probably in the section on measurements? I'm thinking of a simple example showing measurements in a different basis, after describing cirq.measure_state_vector and cirq.measure_density_matrix which measure in the Z basis. Something like
prob_plus = np.trace(cirq.KET_PLUS.projector() @ rho).real

where rho is the same single-qubit density matrix from the previous example. Or maybe a two-qubit example is better. Is this what you had in mind?

How did you fix KeyError: 'language_info' ?

How did you fix KeyError: 'language_info' ?

How did you fix KeyError: 'language_info' ?

Just to document for posterity: Looks like this was unrelated to asyncio as it popped up in #3669, see also https://github.com/quantumlib/Cirq/issues/3603#issuecomment-765830201. So here I'm not sure why the error went away.

How did you fix KeyError: 'language_info' ?

Just to document for posterity: Looks like this was unrelated to asyncio as it popped up in #3669, see also https://github.com/quantumlib/Cirq/issues/3603#issuecomment-765830201. So here I'm not sure why the error went away.

I wonder if we want to talk about projectors (cirq.KET_IMAG.projector()) here too?

Seems like a good idea - probably in the section on measurements? I'm thinking of a simple example showing measurements in a different basis, after describing cirq.measure_state_vector and cirq.measure_density_matrix which measure in the Z basis. Something like
prob_plus = np.trace(cirq.KET_PLUS.projector() @ rho).real

where rho is the same single-qubit density matrix from the previous example. Or maybe a two-qubit example is better. Is this what you had in mind?

Hmm...I was just thinking about a separate section for Projector operators, which are also coming in form of KetBraSum operators soon(ish) #3386. Simulating measurement this way would be an interesting idea too!
I think this all is looking really good now. We can add the projectors as part of a separate issue, after we implemented the KetBraSum features. Then we can expand on pros/cons there - in the end KetBraSum should be a more generic and efficient, sparse representation for projectors.

We can add the projectors as part of a separate issue, after we implemented the KetBraSum features. Then we can expand on pros/cons there - in the end KetBraSum should be a more generic and efficient, sparse representation for projectors.

Sounds good!


Streaming Azure Function Logs - not working/supported

Repro steps:

Action: azureFunctions.startStreamingLogs
Error type: Error
Error Message: This operation is not supported by this app service plan.
Version: 0.17.1
OS: win32
Product: Visual Studio Code
Product Version: 1.36.1
Language: en

Call Stack
SiteClient.get kudu [as kudu] extension.bundle.js:332:359969
Object.<anonymous> extension.bundle.js:332:832250
o extension.bundle.js:332:831321
process._tickCallback next_tick.js:68:7

Repro:-

Create Python Azure Function per https://docs.microsoft.com/en-us/azure/azure-functions/tutorial-vs-code-serverless-python#visual-studio-code-python-and-the-azure-functions-extension
Right click on the Azure Function Project from the Azure Tab in VS Code, and click on "Start Streaming Logs".
You will get the error in the output window - this is not supported.

@kprpg correct this is not supported yet. See https://github.com/microsoft/vscode-azurefunctions/issues/589


Scalable born digital workflow

Initiative
Investigate Enduro+a3m prototype with Artefactual
Objective
Build the platform services to support born digital access
Key results

IIIF services support born digital access

Better understanding of future direction for born digital workflow

Link to feature: https://wellcomecollection.productboard.com/feature-board/planning/features/15789458

Closing as represented as part of other work: https://www.notion.so/wellcometrust/Archivematica-next-steps-f91856390fcc4ec69753bd3fcecabb63?pvs=4


Add support for DD_APPEND_SLASH

Avoid situations like https://owasp.slack.com/archives/C2P5BA8MN/p1705702146187379
Better context description: https://learndjango.com/tutorials/trailing-url-slashes-django
Documentation: https://docs.djangoproject.com/en/4.2/ref/settings/#append-slash

Hi @grendel513 / @devGregA / @cneill / @blakeaowens. I would like to ask for a review.


Any pretrained model?

Hello,
thank you for your code.
I am wondering if  you can provide the pretrained model of the resnet_v2 with cbam attention model?
Thanks!!!

Dear kobiso,
thank you for your code.
I am wondering who first come up with the model "InceptionResnetv2+CBAM".I used this model in the article and would like to quote it.I've already quoted the two separate parts.
Thank you very much!!!


Markdown File Change

In the markdown file, change
Clone the repo using git clone git@github.com:gerwinf/simple-marketplace.git
To
Clone the repo using git clone git clone https://github.com/gerwinf/simple-marketplace.git
This will allow for the repo to be cloned using the command line (on a mac at least)

Done. Previous line was compatible with Ubuntu but your suggestion works as well.

Done. Previous line was compatible with Ubuntu but your suggestion works as well.


zephyr: Kconfig: SOC_GECKO_USE_RAIL_API option for RAIL for proprietary

Currently on zephyr, RAIL library is used only by Bluetooth applications, with this update, it will be able to be used for sample applications, that are using proprietary phys. Other wireless protocols and proprietary wireless communications will be added to zephyr system later.
With this update, the missing files will be also included and added to the source, that are needed for the Radio to be able to use the Radio Configurator generated c and h files for proprietary usage.
Second half of the PR can be found here: silab_hal: https://github.com/zephyrproject-rtos/hal_silabs/pull/39

@fkokosinski @jerome-pouiller I have updated the PRs according to your comments, could you please take a look at them again?

Hi @zohavas, could you bump the HAL SiLabs revision to 72a67203f0b37dc2c12bfae5ddf05c991c0ab0a4? Thanks!

@mrfuchs @MaureenHelm @galak @ioannisg @tgorochowik could you please take a look at this PR? If it is okay with you please approve it.


Maya: Validate Rig Controllers - fix Error: in script editor

The code implemented with this commit by @tokejepsen prints "error" messages in my script editor in both Maya 2020 and 2022.
For example:
# Error: 'visibility' is not a dynamic attribute of node 'pCube1'. #
# Error: 'translateX' is not a dynamic attribute of node 'pCube1'. #
# Error: 'translateY' is not a dynamic attribute of node 'pCube1'. #
# Error: 'translateZ' is not a dynamic attribute of node 'pCube1'. #
# Error: 'rotateX' is not a dynamic attribute of node 'pCube1'. #
# Error: 'rotateY' is not a dynamic attribute of node 'pCube1'. #
# Error: 'rotateZ' is not a dynamic attribute of node 'pCube1'. #
# Error: 'scaleX' is not a dynamic attribute of node 'pCube1'. #
# Error: 'scaleY' is not a dynamic attribute of node 'pCube1'. #
# Error: 'scaleZ' is not a dynamic attribute of node 'pCube1'. #

For sake of example I just quickly added a cube as "controller"
The script continues fine but it's a confusing/annoying side effect and because it prints so many in the Script Editor it also slows down the validation.
This code change avoids the error and still correctly skips the usedAsProxy attributes as intended originally.
Note that it's using maya.cmds.addAttr flag exists=True instead of checking whether the attribute itself exists with attributeQuery. According to the docs exists on maya.cmds.addAttr should:

Returns true if the attribute queried is a user-added, dynamic attribute; false if not.

Nice work!


Add Interactions between On-Disk Files and In-Memory Archives

Fixes  #173
Changes proposed in this PR

Add a method for unzipping an archive that's not necessarily on disk to a location on disk.

let inMemoryArchive = Archive(someData, .read)
let destinationOnDisk = URL(fileURLWithPath: "path/to/destination")
FileManager.default.unzip(inMemoryArchive, to destinationOnDisk)

Add a method for zipping a file on disk to an archive that's not necessarily on disk.

let inMemoryArchive = Archive(someData, .create)
let sourceOnDisk = URL(fileURLWithPath: "path/to/destination")
FileManager.default.zipItem(at sourceOnDisk, to inMemoryArchive)

Add a method for zipping a file on disk and returning an in-memory archive containing the zipped file.

let sourceOnDisk = URL(fileURLWithPath: "path/to/destination")
let archive: Archive = FileManager.default.itemZipped(from sourceOnDisk)

Tests performed

Added unit tests for the 3 new methods.
Tests passed on macOS 10.15.3 with Xcode 11.3.1 (11C504).

Further info for the reviewer

Refactored existing file-to-file zipping and unzipping methods. They now delegate the majority of work to the first 2 new methods.
Fixed a bug where unzipItem(at:to:skipCRC32:progress:preferredEncoding:) didn't check if destinationURL was writable.

Open Issues
For some reason, sourceURL has to be checked twice in zipItem(at:to:shouldKeepParent:compressionMethod:progress:).

Thank you for your contribution and sorry for the delayed reply.
The changes look good, but there are some minor issues we need to fix before merging this.
The Linux build currently fails and there are also some swiftlint warnings.
I saw, that you added a FIXME comment regarding a test case that fails if no fileExists check is performed. This is expected behavior. We try to also cover the error code paths with tests and this test case exercises the condition where the source archive does not exist and we therefore expect an error to be thrown.

The Linux build currently fails

I found out the root problem: a newly initialised archive wasn't unwrapped in itemZipped(from:shouldKeepParent:compressionMethod:progress), so I changed it.
This problem wasn't Linux specific, but it hasn't been caught on Apple platforms in testing. I'm not completely sure why this is the case, yet. It seems like all test cases that are conditionally compiled at Swift ≥ 5.0 are skipped by Xcode in testing.
I fixed as much as I could, and don't know how to deal with the remaining errors. Somehow XCTFail allows guard to fall through when the entire guard statement is conditionally compiled.

some swiftlint warnings

I think I fixed most of the warnings. The rest are complaints about either functions or files having too many lines. There aren't many empty lines in the entire codebase. I think one way to fix it is through some heavy refactoring that gathers together some common parts, and make better use of setUp() and teadDown().
I find these linter rules quite arbitrary, and even a bit silly, though. They could inadvertently force developers to make code less readable, just to conform to the forms.

I saw, that you added a FIXME comment regarding a test case that fails if no fileExists check is performed. This is expected behavior. We try to also cover the error code paths with tests and this test case exercises the condition where the source archive does not exist and we therefore expect an error to be thrown.

This occurs in zipItem(at sourceURL: URL, to destinationURL: URL, shouldKeepParent: Bool = true, compressionMethod: CompressionMethod = .none, progress: Progress? = nil), which delegates everything to try zipItem(at: sourceURL, to: archive, shouldKeepParent: shouldKeepParent, compressionMethod: compressionMethod, progress: progress). The latter already checks if the source exists for the former. So, it seems strange to me that it needs to be checked again.

While trying to figure out why some of the tests failed, I modified the CI script. Mostly expanded and updated the test platform versions.

Thanks for looking into that so quickly!
This problem wasn't Linux specific, but it hasn't been caught on Apple platforms in testing. I'm not completely sure why this is the case, yet. It seems like all test cases that are conditionally compiled at Swift ≥ 5.0 are skipped by Xcode in testing.
This is a shortcoming of the current test setup.
We mainly provide an .xcodeproj for Cathage support. SPM and CocoaPods don't use the .xcodeproj at all.
Sadly, the Xcode project file doesn't provide a mechanism to define a range of supported Swift versions. You can only set SWIFT_VERSION to a single value. As Swift 4.0 currently is the "baseline" language version we support, we have to set it to that. We currently use the Xcode-based test runners for Darwin platforms and they use the xcodeproj and therefore pick up the language version from there. Swift 5.0 codepaths are currently only exercised by the SPM based Linux test runs.

While trying to figure out why some of the tests failed, I modified the CI script. Mostly expanded and updated the test platform versions.

I plan to move to GitHub Actions for CI in the near future. While I think the changes you introduced (using the latest version & setting up a test matrix, ...) are a good idea, I'd rather do that in a dedicated PR, that also migrates to GH Actions.
Can you please revert the following changes for now:

.xctestplan
.xcscheme
.azure-pipelines.yml

I find these linter rules quite arbitrary, and even a bit silly, though. They could inadvertently force developers to make code less readable, just to conform to the forms.

I totally understand that - I often run into swiftlint-imposed constraints myself. Of course that shouldn't lead to less readable code. Ideally it should point out locations where improvements can be made.
As a concrete example, we could move the Date helper methods in FileManager+ZIP into a dedicated file. That is a low hanging fruit and would fix the file length warning for that file.
No worries, if you don't have time for those cleanups - I can also look into that when I work on the project the next time. Would it be okay for you if I push directly onto your PR branch?

Add a method for zipping a file on disk and returning an in-memory archive containing the zipped file.

Providing this method seems a bit too convenient IMO. As far as I can see it only wraps zipItem(... to ...) and implicitly creates an in-memory archive. What happens if a user innocently passes in a large directory here? I think it'd be better to remove this method and only offer zipItem(... to ...), because the latter requires explicit creation of an in-memory archive. Therefore users have to manually indicate their intent.

You can only set SWIFT_VERSION to a single value.

Would using a workspace that targets multiple Swift versions work? It will be very hacky tho.

Can you please revert the following changes for now:

.xctestplan
.xcscheme
.azure-pipelines.yml

Just did. Sorry, I should have consulted you first before making those changes.

Would it be okay for you if I push directly onto your PR branch?

Yep.

What happens if a user innocently passes in a large directory here?

This is a problem I overlooked. I suppose the OS would just keep on paging until it crashes. What if we add some checks and have it throw an error if there isn't enough memory? Would it make the convenient method valuable to have?
Maybe I can refactor the methods further to make zipping and unzipping truly location-agnostic?

Would using a .xcworkspace that refer to multiple .xcodeproj files, with each of them targeting a different Swift version, work? It will be very hacky tho.

I'd like to get rid of anything Xcode related altogether at some point and solely rely on the information provided by the SPM metadata.

Just did. Sorry, I should have consulted you first before making those changes.

Thank you. I will re-add some of your changes (esp. the CI test matrix 👍) in another PR when switching to GitHub Actions.

This is a problem I overlooked. I suppose the OS would just keep on paging until it crashes. What if we add some checks and have it throw an error if there isn't enough memory? Would it make the convenient method valuable to have?

An API user should consider the memory requirements of the code while writing the code. Hence I think that an error thrown at runtime is too late here.
I am currently juggling a lot of different tasks, so I might be slow to respond - But I will try to help out with this PR when I can.

Could this be merged for iOS/macOS/tvOS/watchOS first, and solve Linux_Swift as a separate PR?

It's been a while since I last worked on this. If I remember correctly, it's some of my ill-written test cases that are causing the CI failures. I will reinvestigate them.
I think I can also mark the new methods introduced in this pull request with @available or put them in #if conditional compilation blocks, if @weichsel thinks it's ok.

Add a method for zipping a file on disk and returning an in-memory archive containing the zipped file.

Providing this method seems a bit too convenient IMO. As far as I can see it only wraps zipItem(... to ...) and implicitly creates an in-memory archive. What happens if a user innocently passes in a large directory here? I think it'd be better to remove this method and only offer zipItem(... to ...), because the latter requires explicit creation of an in-memory archive. Therefore users have to manually indicate their intent.

^ There is also this thing I need to address first.


Support [pulsar]

as Apache’s incubation process ‘s top-level project， pulsar become more and more popular, so many company upgrade from kafka to pulsar
also，pulsar use Apache jclouds to support Amazon S3 and same others for long term storage. may the integration with lakefs is simple and fast

Hi @Janus-Xu ! This makes perfect sense. From skimming the Pulsar docs, this seems to be doable without any modification to lakeFS or Pulsar, using the S3 Offloader:

There is a third driver type, s3, which is identical to aws-s3, though it requires that you specify an endpoint url using s3ManagedLedgerOffloadServiceEndpoint. This is useful if using a S3 compatible data store, other than AWS.

So it seems that setting s3ManagedLedgerOffloadServiceEndpoint to the lakeFS S3 domain name should do the trick, but requires some testing. If it works I'll gladly add it to our documentation.
@Janus-Xu Would you be willing to help test this?

Requires testing and documentation of testing outcome.


Pass context in operators instead of individual objects

This will allow us to easily add more params to operators constructors in the future without major refactoring.

Codecov Report

Merging #10306 (d25d4e5) into master (0927e94) will decrease coverage by 54.73%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master   #10306       +/-   ##
=============================================
- Coverage     68.41%   13.69%   -54.73%
+ Complexity     5109      182     -4927
=============================================
  Files          2015     1961       -54
  Lines        109656   107209     -2447
  Branches      16686    16393      -293
=============================================
- Hits          75024    14679    -60345
- Misses        29283    91358    +62075
+ Partials       5349     1172     -4177

Flag
Coverage Δ

integration1
?

unittests1
?

unittests2
13.69% <0.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

 Learn more

After discussion with @walterddr it seems like not the right approach to go with. Reason being the PlanRequestContext object is destroyed after the visitor is called. Any operator if it caches this object, will not be able to use it at runtime. Better to not take this risk in the future.

So we should close this PR?

But #10299 isn't focused on passing context operators, right? I think we still need to think how to pass this contextual information in Pinot. I've found several places where contextual information is needed and in order to do not add tons of arguments to the constructor I had to delegate on static methods. For example when dealing with #10183 or sending metrics. I have the feeling that we should start thinking on using some dependency injector in order to try to decouple our objects from the contextual arguments

I agree with @gortiz here. Passing more than 3-4 arguments is simply not the correct way and also increases the time to make small changes to functions.


Custom Style for Template child control is not applied correctly

example Style - Expander.paml
if in DefaultTheme.paml style Expander.paml is included before ToggleButton.paml:
  <StyleInclude Source="resource://application/Perspex.Themes.Default/Perspex.Themes.Default.Expander.paml"/>
  <StyleInclude Source="resource://application/Perspex.Themes.Default/Perspex.Themes.Default.ToggleButton.paml"/>

For the toggle button in the expander header, default style for ToggleButton is used not the one specified in Expander.paml.

This is expected behavior I think - later styles have precedence of earlier styles, and the default ToggleButton style will apply to all ToggleButtons.


Load sprite sheet

Hi! I would like to know if you can provide a way to load sprite sheet (A sprite sheet packs a number of smaller images into a single large image.) ? Some tools like TexturePacker help you to create these sprite sheets and it's based on json to load these images.
Thanks for your answer!

We provide this already, you can use both the class Sprite and SpriteSheet.
https://github.com/flame-engine/flame/blob/master/doc/images.md

Yes I saw it but it looks like very simple and it's only possible to load animations of a character that is design in a single line. In my case I would like to load a big sprite sheet with a lot of different images that can be objects, menu assets, a lot of images that will be not animated. All these objects are not of the same size. Like in this image for example : https://amakaseev.github.io/sprite-sheet-packer/screens/main.png

You can already load this using the Sprite class, when creating a new Sprite it receives parameters x, y, width and height, with those parameters you can select parts of the image.
The only annoying thing about this is that given that image you provided as example, it would be a very manual process.
The Spritesheet class is meant to be only a help class on top of the Sprite class, and it covers aonly the basic, common uses that we identified.
I imagine that an image like the example you provided, would be needing some kind of metadata, like a json or xml to describe the positions and dimensions of each chunk.
We could create our own format for that, shouldn't be very hard, but if you happen to know, or use one already, and if it is something generic enough, we could try to integrate it on Flame.

Yes manual job it's not a good thing. TexturePaker provide you a generic json file that discribe how you put your images here is an example it's pretty basic :
{"frames": [
{
	"filename": "image1.png",
	"frame": {"x":579,"y":604,"w":62,"h":62},
	"rotated": false,
	"trimmed": true,
	"spriteSourceSize": {"x":1,"y":1,"w":62,"h":62},
	"sourceSize": {"w":64,"h":64},
	"pivot": {"x":0.5,"y":0.5}
},
{
	"filename": "image2.png",
	"frame": {"x":511,"y":668,"w":62,"h":62},
	"rotated": false,
	"trimmed": true,
	"spriteSourceSize": {"x":1,"y":1,"w":62,"h":62},
	"sourceSize": {"w":64,"h":64},
	"pivot": {"x":0.5,"y":0.5}
}],
"meta": {
	"app": "http://www.codeandweb.com/texturepacker",
	"version": "1.0",
	"image": "sprites.png",
	"format": "RGBA8888",
	"size": {"w":1206,"h":1003},
	"scale": "1",
	"smartupdate": "$TexturePacker:SmartUpdate:b5fb5d5db8ad960a7927226c3156595b:fd6909c3527bc05911568aa5fd053d0d:1eabdf11f75e3a4fe3147baf7b5be24b$"
}
}

Okay, we could add support to TexturePacker, since we already have spritesheet support on flame, and what you need is support for a third party tool format, I will close this and ask you to open a new issue, asking specifically for TexturePacker support.
On the new issue, please link the documentation for this tool format, and if you could provide an example image and its metadata file, would help us a lot.


test-macincloud-macos1013-x64-1 connection issue.

Test_openjdk8_j9_sanity.openjdk_x86-64_mac_xl
https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk8_j9_sanity.openjdk_x86-64_mac_xl/218/console
18:58:06  XML output with verification to /Users/jenkins/workspace/Test_openjdk8_j9_sanity.openjdk_x86-64_mac_xl/openjdk-tests/TKG/test_output_15911206752866/jdk_lang_j9_0/work 19:00:29  Cannot contact test-macincloud-macos1013-x64-1: java.lang.InterruptedException 19:07:54  wrapper script does not seem to be touching the log file in /Users/jenkins/workspace/Test_openjdk8_j9_sanity.openjdk_x86-64_mac_xl@tmp/durable-c83a6035

@gdams Would you mind taking a look at this?

Re running the sanity job on test-macincloud-macos1013-x64-1, https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/3186/, couldnt recreate the error. I suspect this is an intermittent failure so will be closing this for now while keeping an eye on the job


Restructure failure_cases

Good point about failure_cases. They are indeed failing, and 'old-way' tests check that they do. Would be great to restructure these so that they pass both ways.
Originally posted by @ev-br in https://github.com/ev-br/scpdt/issues/84#issuecomment-1653337023

OK, so the failure occurs in an unsupported way of running tests. The recommended way is
$ pytest --pyargs scpdt

which runs all tests and reports success. Which is fine then.


[BEAM-8850,BEAM-8849] FlinkBatchTranslationContext respects input par…

Preparation for https://issues.apache.org/jira/browse/BEAM-8848
This PR covers:
https://issues.apache.org/jira/browse/BEAM-8849
https://issues.apache.org/jira/browse/BEAM-8850

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Run Flink ValidatesRunner

Run Java PreCommit

Run Java PreCommit

Run Java PreCommit

Run Java PreCommit

Java preCommit keeps failing on unrelated tests, especially sdks:java:io:rabbitmq:test

Closing in favor of https://github.com/apache/beam/pull/11874


Project screen

List important files/docs

Show latest activity?

If linked to repository

List issues of repo
List branches of repo

Only be able to change state when logged in and authorized to edit.

Keep in mind that nested projects will be added in the feature and that this will be a central thing in the ui.

Will the back-end provide the repository-linked information such as issues and branches or should the front-end do the API calls to github directly?

For now the plan is that the backend will provide all needed information.
Otherwise only public repositories could be used because the front-end will not get the global access key to prevent miss-usage by the users.

Frontend will further be developed in it's own repository found here: https://github.com/ZeusWPI/g2-frontend/issues/2
Moving frontend issues there.
Closing.


Stack template for tasty-discover

It would be really great if one could simply run:
$ stack new tasty-discover

All that needs to be done, is add the template here.

Submitted a first attempt at the PR here.

Previous one got merged but I borked it with a typo, round two happening here


Error: ChatGPT invalid session token

Hi @kxxt , thanks for your great project! Could you give me some ideas to resolve this error?

Hi @haoran0412 , this github action no longer works because OpenAI has integrated Cloudflare into their ChatGPT app. To resolve this error, we need to upgrade our chatgpt dependency from v2 to v4 and change the code base correspondingly. Now I am busy with other stuffs so I don't have time to do that.

Got it, thanks!


Add A->B mapping for SPDX-2.0 to SPDX-3.0

After new spdx syntax pulled in https://github.com/openSUSE/spec-cleaner/commit/5d8397c52b99e6f8beb0f52a03796dab8a902aff most spec files will warn about the license
We should create known mappings to allow auto conversion:
Ie:
GPL-2.0 -> GPL-2.0-only

Also the license-changes.txt will need tweaking as it is now explicity some exact version or newer. Those + additions are wrong.
+GFDL-1.2-only	GFDL-1.2-only
￼ +GFDL-1.2-only+	GFDL-1.2-only+
￼+GPL-2.0-or-later	GPL-2.0-or-later
+GPL-2.0-or-later+	GPL-2.0-or-later+

@coolo could you somehow check if it seems +- correct? Also any idea where to edit directly the first gdoc in the script, it migth be cooler to fix stuff there rather than hunting it around later with seds...

Also it seems we are not handling the WITH syntax from SPDX-2.2 at all...
ANYLICENSE (WITH|with) ANYTHING_FROM_LICENSES_EXCEPTIONS.txt
"GPL-2.0-only WITH openssl-exception" is one string based on the spec which would fail currently.

Ouky, now we match up the obs part and it should be working, at least no tests explode.


Fixing some links

https://github.com/MicrosoftDocs/office-docs-powershell/issues/5876
@kaarins thanks for the links

according to Kaarin, links for information barriers will be published soon.

Docs Build status updates of commit bec7f5e:
:clock10: Full build: the average full build time is 18 min(s) 1 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit bec7f5e:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

[Error-GetDocumentsFromDHSFailed] Getting documents from document hosting service failed with locale: en-us, depot name: MSDN.exchange-ps, branch name: pr-en-us-5893. Error: A task was canceled.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 36da402:
:clock10: Full build: the average full build time is 18 min(s) 1 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 36da402:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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


Add support for Swedish

Tradukisto is the library what converts numbers to human-readable words - for example from 14 to fourteen. This issue was created to add support for counting in new language. Depending on how numeral system in your language is similar to other languages (english, arabic, german, slavic) and how many exceptions it have - it can be easy or more demanding.
Implementing unit tests will be really helpful for you, I encourage you to create them first (TDD paradigm), before developing new changes in the code.  You can run them in terminal with ./gradlew test or green button in Intellij code editor.
New language needs to have implementation for Container. Depending on how your language works, having conjugation, gender forms, custom chunking (typically divider is for 3 numbers) etc it may be needed to define more advanced container with custom implementations for counting, for example turkish. Tests will really be helpful for you to see if it needs custom implementations or not.
Also define Values - translations for base numers  and for plural forms (thousands, millions etc).
Feel free to ask if you have more questions, we will try to help you.
https://github.com/allegro/tradukisto/wiki/How-to-start-contributing

Hi @R055A - I will assign you :)

Thanks @R055A, we will take a look at this PR in next week.

Done. Thanks, I didnt knew it was needed.


Crash in -[RCTImageLoader _loadURLRequest:progressBlock:completionBlock:]

Description

Version
0.63.3
Output of npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 12.3.1
CPU: (10) arm64 Apple M1 Pro
Memory: 67.80 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 17.5.0 - /opt/homebrew/bin/node
Yarn: 1.22.17 - /opt/homebrew/bin/yarn
npm: 8.4.1 - /opt/homebrew/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Xcode: 13.3/13E113 - /usr/bin/xcodebuild
Languages:
Java: Not Found
Python: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.63.3 => 0.63.3
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
npm notice
npm notice New minor version of npm available! 8.4.1 -> 8.6.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.6.0
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
Steps to reproduce
Online problem, can't repro.
Snack, code example, screenshot, or link to a repository
No response

The initial suspicion is that there is a multi-threaded operation of variable objects in the RCTNetwoking class.


Is there a way to generate file that can be analyze by perfetto (systrace file)?

Is there a way to generate file that can be analyze by perfetto (systrace file)?

(Sorry about not getting to this earlier!)
No, there's unfortunately no systrace export. However, it wouldn't be hard to write given our python parser - we already build up "blocks" and "threads" and it would be just a matter of exporting the data model in the formats that perfetto expects.
I'd be happy to walk you through how to do that in more detail, if you're interested. :)


Feature request: Allow to return argument arrays when using a function configuration

Most examples with a function configuration are missing a robust file arguments escaping method. Merging #875 would help by providing a utility function. However, a simple solution (when not using the shell option) would be to allow function configuration to return argument arrays instead of strings, so that execa can use those without intermediate serialization.

Can you perhaps be more specific and provide a few examples?

 // .lintstagedrc.js
 module.exports = {
-  '**/*.js?(x)': (filenames) => filenames.map((filename) => `prettier --write '${filename}'`),
+  '**/*.js?(x)': (filenames) => filenames.map((filename) => ['prettier', '--write', filename]),
 }

A good suggestion, @make-github-pseudonymous-again! That would definitely be simpler than having to manually use the escape helper in the config.

Oh I like that! Are there any use cases when we would not like to do that?
do you want to provide a PR please?

Maybe this should not be unnecessarily restricted to function configurations? For instance
module.exports = {
  '*.x': ['a b c d', 'e f g h'],
  '*.y': [['a', 'b', 'c', 'd'], ['e', 'f', 'g', 'h']],
  '*.z': () => ['a b c d', 'e f g h'],
  '*.w': () => [['a', 'b', 'c', 'd'], () => ['e', 'f', 'g', 'h']],
};

Is '*.js': 'a b c d' allowed (without a surrounding array)? Anyway, double nestedness should be mandatory to interpret an array as command line arguments.

Basically if we could pass command all the way here as string[], we could skip parsing it and instead just spread it to execa. I guess it would be fine to assume command[0] is the program and rest arguments:
https://github.com/okonet/lint-staged/blob/4f9a146708862b06d19c7627f4dd1b094b2b88ce/lib/resolveTaskFn.js#L88
In the case of '*.js': 'a b c d' it would be a single command a with arguments b c d.

Would it also make sense to allow objects {title: string, command: string[]} or similar? title would allow displaying a custom string for a command, in case an autogenerated one is unreadable. For instance, replace npm run lint a.js b.js c.js ... by lint 14 staged files. Each configuration item would be transformed down to that representation.

Generally I’d be against polymorphism but if the title is something everyone thinks is needed then I’m fine with this too. In this case we’d need to refactor everything to use this format under the hood, right?


globals: Re-add RSVP link and add global flag for if RSVPs are allowed. see also #52

https://github.com/hackumass/hackathon-dashboard/commit/4567886402f28975bb53ea0575e32e07663c438f#diff-ffbfa86d935f0c4261073232dd2ee6d2

Done as a part of the custom application questions refactoring


Support PHP 8

Being able to use this with PHP 8 would be nice. This requires deployer/deployer v7, though…

ping  @jonnitto


No font icon imported to scene builder version 10.0.0

Im using scene builder version 10.0.0. imported all the jar ikonli-core, ikonli-javafx,ikonli-fontawesome all the jar version 11.0.0 to scene builder library manager but none of these jar have component when imported ,so im unable to use fonticon.

What do you mean there’s no component? The ikonli-javafx artifact provides a FontIcon class. https://github.com/aalmiray/ikonli/blob/master/subprojects/ikonli-javafx/src/main/java/org/kordamp/ikonli/javafx/FontIcon.java

Basically when imported jar to scene builder from library manager thru maven repo , the basic component for example FontIcon and StackFontIcon are not loaded into import dialog of scene builder. That why FontIcon no available inside scene builder.


Flutter Embedders should be able to use Direct3D on Windows.

Based on guidance from the Skia team in a recent sync, the Direct3D 12 backend may be ready to be experimented with. It was noted (though I did not find references) that the minimum version supported was 12 with an Angle based fallback recommended for versions less than 12. The backend may currently be enabled by setting the skia_use_direct3d GN flag.

This issue came up at the sync today and my initial comment about this being ready to experiment with was inaccurate. @brianosman says the backend probably can't draw anything just yet.

Update from the sync this week: This backend is still about 1 quarter away from being ready for experimentation with. Some Skia tests and applications are functional.

Update: The Skia team indicates that the D3D 12 backend is getting close to testing for readiness.

When release Impeller Preview for Windows Direct3D Backend?


Remove extra space from --ci description

Summary

I ran jest --help and noticed the extra space in the --ci option.
Test plan

I just removed a space, I'm sure CI would catch any errors :)

Codecov Report

Merging #9516 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #9516   +/-   ##
=======================================
  Coverage   65.01%   65.01%
=======================================
  Files         283      283
  Lines       12148    12148
  Branches     3009     3009
=======================================
  Hits         7898     7898
  Misses       3607     3607
  Partials      643      643

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 964dc16...1b24f6c. Read the comment docs.


Relax Plug.Cowboy dependency requirements

Hi there! 👋
Currently the package specifies the following dependency on the Plug.Cowboy package:
https://github.com/getsentry/sentry-elixir/blob/02a2cc31c7444af88d079f7c32a789b9b1b4e6f1/mix.exs#L44
We have some apps still using Cowboy 1.x, which causes a dependency conflict. For the sake of testing, we've set override: true on :plug_cowboy in our mix.exs files, and the integration with Sentry seems to be working correctly.
Is there a reason why the package depends on Plug.Cowboy 2.x? I've looked at the code and it looks like Plug.Cowboy is only used in tests. If there's not, would it be possible to relax the requirement to allow Plug.Cowboy 1.x too?
Thanks!

The complicating part is the Logger integration depends on behavior in Plug 2.x to avoid double logging an error through PlugCapture and Logger.
The commit is here: https://github.com/elixir-plug/plug_cowboy/commit/3760ab479b02279d39ddf2b9cf7791f07470277c#diff-87fab128ba958876d471b11a331119757921bd6a6c29c364881497a280b3f1af

Thanks Mitchell! With Cowboy 1.x override, it's more likely that we'd lose the events, or that they'd be reported twice?

They would be reported twice (with slightly different metadata) if you use both Sentry.LoggerBackend and Sentry.PlugCapture. The bit that enables it is having :cowboy in the excluded domains here: https://github.com/getsentry/sentry-elixir/blob/master/lib/sentry/logger_backend.ex#L48

Thank you for clarification! I'm gonna close the issue then 👍


Adds a JWT token usage example to show how you can add a 'Recently Purchased Products' block.

What? Why?
Now that he bc App supports JWT this adds a JWT example usage to the app.
Also:

Added DotEnv via composer and updated the readme so you don't have set server variables when working locally.
Added .htaccess so you don't need to include /index.php/ in apache requests.
Added additional commenting some methods.

How to test
Try it out by reading the instructions. The JWT steps are totally optional.
@pedelman @mattolson @bc-AlyssNoland

@bookernath If we can add this in that'd be greats well :).

👍

LGTM 👍


Uninstall instructions

Right clicking on the screen saver and clicking delete did not remove the screen saver for me. This is really needed because I had duplicate arial screen savers and didn't know which one I should delete.

Good. But should probably update it to also mention the Cache folder. No point keeping 5+GB worth of MOV files if they aren't being used.

In the location provided I have only symlink to brew files location. Perhaps it would be possible to uninstall directly from homebrew?

@skybleu If you installed with brew, does brew cask uninstall aerial not work?

It would work. I'm just pointing out that there's no mention of it in the proposed Uninstall section, and that might lead to removing only the alias.


Change back to Brightspace/app-localize-behavior

...

Why back to the repo?

The Brightspace one has this commit in particular, which addresses some IE concerns. I'm not sure if those concerns have been addressed in the PolymerElements version of it, but if so, then everything should be updated. (Right now, causing bower conflicts when I try to update BSI.)


package.json Illegal characters

Hey, I'm getting the following error:
$ yarn add gatsby-plugin-favicon
yarn add v1.3.2
error package.json: Name contains illegal characters
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
Any thoughts?

I didn't have any problem, can you still reproduce the bug? Don't hesitate to reopen the bug if it's the case :)


unknown state

Hello,
Thank you for this component, its useful!
I often have connectivity issues, where the state changes to unknown, I was wondering if its possible to fine tune the duration prior to changing state to unknown (as it spams my logs / state)
I often see in the logs

while looking at it, I was also seeing a very high rate of DNS requests (but I assume that's a failure on wallbox dns records).

Hi, the component works as follows:
HomeAssistant Component -> Python Wallbox Integration -> Wallbox API -> Your Wallbox at Home
If I look at your issue, it seems that the Wallbox API cannot communicate with you Wallbox at Home. That is something out of my control. I could of course reduce the amount of polling (no of requests to the API) but that will be bad for other users, and I'm not sure if it would fix your problem. Have you considered using a template sensor for this issue?

I wonder, the mobile application uses websockets for notifications, can we reuse the same mechanism vs continuously poll? also, if we poll and get unknown state, can we expose a configuration to set the timeout that we update ha with that state? (e.g. from looking at the image above, its nearly almost resolved under a minute.
I'll try opening a service call with wallbox to try and understand why the api return the unknown state, do you happen to know which end point is being queried so I could try to reproduce it?
thanks!

We cannot easily change the method, I use the following library to get the data: https://pypi.org/project/wallbox/, which determines the method downstream. If you log in on the wallbox webportal, do you also see the unknown status?
If you're handy you can prototype a bit (with the above library) and see what happens. The status of the charger comes from the following URL: "https://api.wall-box.com/chargers/status/(station_serial_here)" (if you look at the code of the above library you can find additional endpoints if necessary).


added support for HTTP user agent in Graph API

Added support for HTTP user agent in Graph API as requested by MSFT
User-Agent: PaloAltoNetworks-MineMeld/{version} where version is the current MM version.

:shipit:


CAIRO_STATUS_NO_MEMORY on pretty simple svg

Hi there!
I have bumped into svg that cannot be processed.
It's unlikely that there is no memory it looks like a bug.
Hope you could sort this out as usual easily )
granddad.zip

This seems to be a bug in cairo. I will try to create a minimal example and submit a bug to cairo.

It appears that there is a bug for this already:
https://bugs.freedesktop.org/show_bug.cgi?id=102966

@Papirosnik
While it does not look like the cairo bug will be fixed anytime soon, I'm attaching the corrected version of the original SVG which can be rendered by svgren. I commented couple of paths and it does not seem to change anything in the image.
granddad_corrected.svg.zip

I can see that blue outlines on grandfather's sleeves have been disappeared.
At least in Chrome this is pretty noticeable.
Anyway, thank you for the problem localization.

Ok. The commeted path elements are using radial gradients for fill style property. And if you look up those referenced gradients you'll see that those are using some weirdly large values for gradient transformation matrix and gradient radius. These gradients are causing problems in cairo. If you could adjust those in your SVG editor to use some more sane values, then you could have those blue outlines on sleeves.
These are those gradients:
<radialGradient cx="0" cy="0" gradientTransform="matrix(0.9999999999999999999999999997, 0.9999999999999999999999999997, 0.00001797114126678521327014218009, 0.00002596838591034755134281200631, -52694933.1, -76139799.3)" gradientUnits="userSpaceOnUse" id="2" r="-6481920.0">

...

<radialGradient cx="0" cy="0" gradientTransform="matrix(1.000000000000000000000000000, 1.000000000000000000000000000, -0.000007911964699074074074074074077, 0.00003057385766050028174786127761, 93951826.35, 107374165.8)" gradientUnits="userSpaceOnUse" id="73" r="-7995801.6">

@Papirosnik maybe this bug can be closed too since workaround was implemented in #56 ?

Well, I thought we have to have some reminder about that bug
but this was a weak argument in favor of it.
so, let's close.

I agree that workaround should be considered a temporary solution. But, on practice there is nothing more permanent than temporary :). It does not look like this Cairo bug will be fixed in near future, so I see no reason having the reminder about that :). So, yeah, let's close.


[WIP] Add dmd to released pages

https://github.com/dlang/dlang.org/pull/1686 without the last commit to test with DAutoTest.

Finally figured it out. Sorry for the noise.


Unsupported layout animation createConfig property (null)

In linear animation mise to set property: LayoutAnimation.Properties.opacity,  see
https://github.com/facebook/react-native/issues/1135#issuecomment-98903335
Here is code in Animation.js:

   linear: {
      duration: 300,
      create: {
        type: LayoutAnimation.Types.linear,
      },
      update: {
        type: LayoutAnimation.Types.linear,
        springDamping: 0.7,
      },
    },

It should be:

   linear: {
      duration: 300,
      create: {
        type: LayoutAnimation.Types.linear,
        property: LayoutAnimation.Properties.opacity,
      },
      update: {
        type: LayoutAnimation.Types.linear,
        springDamping: 0.7,
        property: LayoutAnimation.Properties.opacity,
      },
    },

Thanks @bright-sea, my issue of createConfig error is resolved with the following code.

PR has been merged (https://github.com/Kureev/react-native-side-menu/pull/29)

Hi All.
I am learning React-Native now.
I was going to make side menu.
So I have done it using guide by Kureev.
But the execution is out.
Could you please help me?

Hi @GiantGit15! Please, create a new issue and attach logs/screenshots to give us more insights about your bug.

I'm seeing it again when running another app in simulator then going back to the RN app that was already running.

@Kureev  can you please re-open?


Staysafe? Command Update

Hey,
Could we please update the first line of the Staysafe? reply to:
"Always double check who you are trading with! Discord handles can appear to be similar so verify a user by checking their User ID. How to here <1021586607188496465>"
Then can we add a new line below "If something seems..." and above "Official Art Blocks Links:"
"Stay up to date and report scams in #scam-reporting <1019738320303030345>"

@grantoesterling sending this your way if it is a quickfix ser.


why execute _disk.Close() after transaction commit(Complete)

hi dear:
updated to the 2.0.0 - rc2, I found it always throw exception while I do GetIndexes() after EnsureIndex().

step into the source code, I found that caused by transaction commit (line 67 in "DBEngine\Services\TransactionService.cs" file)

ps: compared with last version( 2.0.0 -rc), It's written with _disk.unlock().

it's appeared in FileDiskService while StreamDiskService doing nothing in Close()

Hi @speedb, this new version use open mode as a concurrency control. So it´s ok close file after each operation. In StreamDisk implementation are complete "single user/no concurrency", so keeps stream open all the time.
I look source and found the bug - are missing "open transaction" here https://github.com/mbdavid/LiteDB/blob/master/LiteDB/DbEngine/DbEngine/Index.cs#L94
I will fix at today and add some unit tests to validate.

yes I see, thanks for your answer


Update yiisoft/hydrator version to ^1.0

Need to make it after Yii Hydrator release

Done by #203


add position to text pos

xmlparser errors return a TextPos, which Stream::gen_text_pos  mentions is expensive to calculate. But I'd like to use a library like Ariadne or Miette to report parser errors. Both of these are offset based, i.e. a position.
I figured I'd just get the stream from the tokenizer when there's an error, using stream().pos(). I have to obtain the stream when there's an error, because stream() generates a copy, and I don't want a stale copy. But since Tokenizer is an iterator and is moved when I start iteration, I can't access it:
for token in tokenizer {
     match token {
        ...
       Err(e) => {
             let position = tokenizer.stream().pos(); // not allowed
        }
    }
}

The easiest way to fix this would be to simply retain the position in TextPos when it is calculated. Would you accept a PR that implements this?
For my use case, I'd actually prefer it if the TextPos calculation doesn't happen at all, as I don't need this to happen, but I don't see a way to do this without breaking backwards compatibilty.
Without this I think the only way forward is for me to write some really ugly code to calculate the position back from the text pos and the input as I don't see another way to obtain it.

Thanks, I should have realized that and I feel dumb now!
But after I changed that I realized that doing this in the error handler:
      let position = tokenizer.stream().pos();

is too late, as the stream already has moved on. I now have this:
let mut position;
loop {
   position = tokenizer.stream().pos();
   if let Some(token) = tokenizer.next() {
       match token {
            Ok(token) => ...,
            Err(e) => {
                 // use position here
             }
   }
}

Obtaining a copy of the stream for each token so I can retain the position information just for the purposes of error handling means the error handling requirements have a performance impact on parsing overall, which isn't ideal but I can live with it.
I'm going to be bold and propose a design where Xot wouldn't incur the TextPos calculations but roxmltree can still have them:

xmlparser::Error only maintains position, and does no expensive TextPos calculation
in roxmltree, whenever an error with a TextPos needs to be produced, ctx is available so that ctx.doc.text could be used to construct TextPos.

Oh, after investigating all this I realized that xmlparser is an internal fork of roxmltree. Have they diverged or is the intent to keep the code identical? What are your plans for 'xmlparser' as a separate crate in general?

Why do you need tokenizer.stream().pos() to begin with, if each token has its position already?
As for any changes, I'm no longer maintaining this crate, as well as roxmltree. So no changes from me. It's up to the new maintainers to decide.
As for roxmltree, it has a modified fork of xmlparser which is a bit simpler and event/push based and not iterator/pull based like xmlparser. Which makes code simpler and faster.


Reuse creation of Client

Currently a new Client is created for each time a request is made, e.g.: https://github.com/durch/rust-s3/blob/69e3efe3a7219bc9d2aab8535b74265642e22d45/s3/src/request.rs#L77
The documentation of Client tells us that the Client should be reused: https://github.com/seanmonstar/reqwest/blob/7d8c32784e543b1a2b9536a70db466c0250876c2/src/async_impl/client.rs#L54
It is better for performance to cache. What do you think about this?

I think this relates to (perhaps duplicates?) https://github.com/durch/rust-s3/issues/152.

Due to the way the request is currently architected, I don't see it happening any time soon


Upgrade to lerna 6.x

Summary
See https://blog.nrwl.io/lerna-reborn-whats-new-in-v6-10aec6e9091c

If you are an OSS maintainer and you use a Lerna workspace, let us know!
Ping the Lerna team on Twitter or ping me directly. We’d love to have a look and help with the migration, look at the repository and make sure it is configured in the best optimal way in terms of monorepo setup and features like caching.

That said, as an open-source maintainer you also get unlimited free computation caching with Nx Cloud. So we’d love to set you up with that.

/azp run


Service Destroy message appears each time

More Details :
D:\docker>fandogh service destroy —name mr-test
Service destroyed successfully.

D:\docker>fandogh service destroy —name hello-world
Service destroyed successfully.

D:\docker>fandogh service destroy —name hello-world
Service destroyed successfully.

D:\docker>fandogh service destroy —name hello-world
Service destroyed successfully.

D:\docker>fandogh service destroy —name hello-world
Service destroyed successfully.

D:\docker>fandogh service list
+-------------+-----------------------------------------------------+----------+
|    name     |                     start date                      |  state   |
+-------------+-----------------------------------------------------+----------+
| hello-world |             2018-05-08T08:31:13.909070Z             | SHUTDOWN |
| hello-world |             2018-05-08T08:46:02.705621Z             | SHUTDOWN |
|   mr-test   |             2018-05-08T08:52:50.676924Z             | SHUTDOWN |
+-------------+-----------------------------------------------------+----------+

Thanks  for the feedback.
Now cli shows a message like No service with name ${GIVEN_SERVICE_NAME} running if service is destroyed already.


Take ownership of app dependencies

coming from this

Studying the app dependencies code and verifying impact
Tests
Create relevant docs

I briefly tested the feature. It is truely lightweight, it works, code looks clean, impact depends - the risk of bad impact is low in my opinion, in terms of positive impact it should increase flexibility of apps deployments. Doc has been created, closing the issue.


Carthage won't build for macOS

When trying to build for macOS with Carthage, I get the error Dependency "Advance" has no shared framework schemes for any of the platforms: Mac.
The main GitHub page indicates Advance is compatible with macOS. Is that not yet implemented or is there some way I can make it work?
I'm using Xcode 10.1, macOS 10.13.6.

First of all, thank you for opening an issue to report this!
This is an error in the readme: the xcodeproj was removed in the latest version in favor of simply including source files (which are integrated into the sample app and are externally consumable via cocoapods). I'll consider bringing back a small Xcode project file to re-add Carthage support – the old one was just overly complicated.

This should be resolved – please let me know if you have any further issues with Carthage.


fix startup on android

Objective

Make Bevy work on android

Solution

Update android metadata and add a few more
Set the target sdk to 31 as it will soon (in august) be the minimum sdk level for play store
Remove the custom code to create an activity and use ndk-glue macro instead
Delay window creation event on android
Set the example with compatibility settings for wgpu. Those are needed for Bevy to work on my 2019 android tablet
Add a few details on how to debug in case of failures
Fix running the example on emulator. This was failing because of the name of the example

Bevy still doesn't work on android with this, audio features need to be disabled because of an ndk-glue version mismatch: rodio depends on 0.6.2, winit on 0.5.2. You can test with:
cargo apk run --release --example android_example --no-default-features --features "bevy_winit,render"

Recorded on device:
https://user-images.githubusercontent.com/8672791/176429665-41bca823-ac54-44bc-89da-2f4fa666897d.mp4
Also works on emulator but it's much slower there

bors try

Tried running this and I'm getting a link error on my new Pixel 6:
06-29 14:51:29.898 13254 13254 E AndroidRuntime: java.lang.UnsatisfiedLinkError: Unable to load native library "/data/app/~~m4g7axUMj33njZDZE6J9Sw==/org.bevyengine.example-czbVgT7PSmsP6pipS0Aong==/lib/arm64/libandroid_example.so": dlopen failed: cannot locate symbol "__cxa_pure_virtual" referenced by "/data/app/~~m4g7axUMj33njZDZE6J9Sw==/org.bevyengine.example-czbVgT7PSmsP6pipS0Aong==/lib/arm64/libandroid_example.so"...

Seems like I'm hitting this: https://github.com/katyo/oboe-rs/issues/28#issuecomment-1001103335
Mentioned in #4103

Ahh I didn't fully read the pr description. Ill try without audio features. Oops :)

Disabling audio did fix the problem. But its pretty inconsistent about whether or not it will work. Sometimes it starts up just fine.

But its pretty inconsistent about whether or not it will work. Sometimes it starts up just fine.

Well... still an improvement 😄
Do you have anything in logs when it's a black screen?

I've tried running the example on my Samsung S21+ and it occasionally works when I start the app, but I more often than not I get a black screen. The following message appears the adb logcat output and I assume is the crux of the problem:
RustStdoutStderr: thread '<unnamed>' panicked at 'Cannot get the native window, it's null and will always be null before Event::Resumed and after Event::Suspended. Make sure you only call this function between those events.', /home/komadori/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.26.1/src/platform_impl/android/mod.rs:598:13

Thanks for testing and reporting the issue!
So it seems this PR doesn't fix that issue, it just happens less often. I would like to keep this PR free of rendering fix so that it doesn't become controversial...
@cart would you agree on moving on with this PR as a first step to fix metadata, naming, and so on? I'll open more controversial PRs for the rest 😄

I'm in favor of merging this ASAP; it clearly improves matters, and Android is already broken so the user impact is 0.

bors r+

bors r+


Postbox options in progress. Having trouble accessing prefs.

https://github.com/adam-p/markdown-here/commit/9ea04209a49f77f8f497af7a5e18b98591b60c33

I appreciate the effort, but Postbox has stopped supporting third-party extensions so we're dropping support for it.


SAK-32687 fix aria-pressed state issues

CC: @adrianfish @Johnson-Mickey
This is related to the second commit in https://jira.sakaiproject.org/browse/SAK-32389

@ottenhoff Indeed my goal with making the  clickable was to try and align the behavior of the expand/collapse toggle button with the tools in the left side toolnav.
Do your changes here satisfy the issues raised in SAK-32687? If not I can try and find a CSS based solution as you suggest.

An li element is not tabbable/focusable without tabindex manipulation and JavaScript manipulation to capture space/enter presses.
It's much better to just use a button or an a link so the keyboard navigator can find and press these elements.
Making an li element work like a button is a lot of unnecessary work.