DQSurviving step added

Please include answers to these questions as part of your pull request
In the GitHub webUI, use the Write tab to modify the Markdown text that is part of the pull request. For each question simply place an X inside the square brackets, [X], that represents your answer. Using the Preview tab you can see the formatted/rendered version of the message.

Q1: Confirm that you have the right to submit the code that is being contributed. Please consider the origin of your code and confirm you have the appropriate rights to make the submission subject to the Apache 2.0 license that applies to everything in this repository of custom steps. If so, follow the instructions for the Contributor Agreement (which is based on the industry-standard Developer Certificate of Origin (DCO)).

[X] Yes, I have the right to submit the contributed code on behalf of myself, my company, or any other owner of the code. I have also attached my signed copy of the DCO to this message.
[ ] No

Q2: Confirm that your contribution does not include any personally identifiable information (PII), for example, in any examples used in your README file.

[X] My contribution does NOT include PII data
[ ] My contribution includes PII data

Q3: Confirm your contribution does not include any encryption or other export-controlled technology.

[X] My contribution does NOT contain encryption or other export-controlled technology
[ ] My contribution includes encryption or other export-controlled technology
ContributorAgreement.txt

Looks like a very useful and powerful data quality transformation!  Have some questions though to better understand the options listed in the UI:

Surviving Record tab

Surviving Options

"First cluster", it sounds like this is "First record in cluster after sorting"? Did I get that right? If so, would  you mind renaming it?
"Last cluster", it sounds like this is  "Last record in cluster after sorting"? DId I get that right? If so, would you mind renaming it?
"Merge Cluster by Fields (Rules)", perhaps rename this to "Merge cluster using field rules"?
"Merge Cluster by Record (Rules)", perhaps rename this to "Merge cluster using record rules"?

Options tab

Delete Work Tables: Is this about cleaning up intermediate helper/work tables created by your step and provided so the user can see intermediate results as some sort of debug option? If so, perhaps change the label to "Delete helper tables created by this custom step"?

SAS Internal Due Diligence Review - COMPLETED on 30SEP2022


Server Crash

Describe the bug
Server crashes upon launch
To Reproduce
Steps to reproduce the behavior:

Install this mod to server
Launch server

Expected behavior
To server work?
Screenshots
I have no screenshots but there is crash log
Description: Exception in server tick loop
net.minecraftforge.fml.LoadingFailedException: Loading errors encountered: [
Occultism (occultism) has failed to load correctly
§7Attempted to load class net/minecraft/client/entity/player/ClientPlayerEntity for invalid dist DEDICATED_SERVER
]
at net.minecraftforge.fml.ModLoader.dispatchAndHandleError(ModLoader.java:201) ~[?:?] {re:classloading}
at net.minecraftforge.fml.ModLoader.gatherAndInitializeMods(ModLoader.java:183) ~[?:?] {re:classloading}
at net.minecraftforge.fml.server.ServerModLoader.begin(ServerModLoader.java:45) ~[?:?] {re:classloading}
at net.minecraft.server.dedicated.DedicatedServer.func_71197_b(DedicatedServer.java:122) ~[?:?] {re:classloading,pl:accesstransformer:B}
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:613) [?:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A}
at java.lang.Thread.run(Unknown Source) [?:1.8.0_221] {}
System (please complete the following information):
I don't think these are necessary?
Additional context
Idk

That's a bad one, I'll look into it. Got a reference to client code somewhere, forcing it to load. Might take a bit to track that one down.

Alpha 0.2.2 will fix this issue. Please test it once it's available on forge and let me know if it worked. Thank you!

Server starts with this mod in now yeah, haven't got to test the mod yet but i assume it is working as server does load up


server: directly inspect the BoringSSL FIPS mode

Commit Message:
Rather than depending on the preprocessor macro, directly inspect the
BoringSSL FIPS mode API to determine whether FIPS mode is enabled. This
binds Envoy's notion of FIPS mode directly to BoringSSL's notion of
FIPS mode, reducing the liklihood of build misconfigurations not being
detected.
Additional Description: N/A
Risk Level: Low
Testing: Unit tests in FIPS and non-FIPS mode
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

Closing in favor of verifying the FIPS mode in a test. I'll post a new PR with that change.


Nodename allocated to node are unknown

I am working apstra terraform for pod based design.
In a pod-based design, I am facing an issue with device allocation. The sequence in which pods are being created by Apstra is unknown, as a result, we are unable to determine which nodename will be assigned to which pod node, and the same applies to rack nodes.
I have multi pod design which consists of 4 pods.
Pod Untitled-5344528 has 2 rack
Pod Untitled-5353720 has 3 rack
Pod Untitled-3837048 has  3 rack
Pod Untitled-3847627 has 4 rack
Now in Terraform Apstra, we are not aware of which sequence pod creation will occur, which is causing us to be unable to fabricate the correct nodename which is required in ‘device allocation resource’ and there is no other way I am able to figure out nodename for a particular  node. The nodename is internal to Apstra and is being created on run.
I tested out a simple single pod-based arrangement with one pod and one rack, and it worked well.
pod based terraform file
terraform_file

#275 helped with this issue - we render pods in a predictable order now.
Long term: we should replace many maps in design API with lists. See, for example, #337 and #338.


README: Fix apisonator docker commands order

Docker-related commands when starting apisonator commands
must be placed before the identifier of the image. Otherwise,
are detected as parameters of the command to be executed
in the image.

bors r+

bors r-

bors r=@guicassolato,@unleashed

Ok, bors cancelled it again. sigh
bors r=@guicassolato,@unleashed

bors r=@guicassolato,@unleashed

bors r=@unleashed

bors r=@unleashed,@davidor


test(e2e): Upgrade existing RHDH release deployed via Operator to new version -

Description
Please explain the changes you made here.
Which issue(s) does this PR fix

Fixes rhidp-2914

PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

/test all

/test all

/test all


Not able to lock some built roles like - "cluster owner".

Rancher versions: v2.0.5-rc1
Steps to Reproduce:
Go to Global->Security->Roles.
Edit "cluster owner" role and choose "yes" for locked and save.
UI is stuck in "saving" and I see no api call being made.

Tested with v2.0.5-rc3
Able to lock built roles "cluster owner".


Slow Download Connection through Reverse Proxy

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you're not using someone else's docker image?

Yes

Have you searched for similar issues (both open and closed)?

Yes

Describe the bug
I use the docker-compose File from this repo to start the Container. In my Local Network everything works fine and fast, but i am using a WikiJS and a Nextcloud Container too and made them public. If i want to download a Video for example, i only get about 200kb/s Download, the upload is a bit faster. In WikiJS i embedded a PDF with 20Mb and it takes about 3-5 Minutes to load this file.
In the advanced Settings i have this Configuration:
add_header X-Frame-Options SAMEORIGIN;
add_header X-XSS-Protection "1; mode=block" always;
add_header X-Content-Type-Options  nosniff;
add_header Referrer-Policy "no-referrer-when-downgrade" always;
add_header Strict-Transport-Security "max-age=63072000" always;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Port $server_port;
location = /.well-known/carddav {  return 301 $scheme://$host/remote.php/dav; }
location = /.well-known/caldav {  return 301 $scheme://$host/remote.php/dav; }
location ^~ /.well-known { return 301 $scheme://$host/index.php$uri; }

Nginx Proxy Manager Version

2.9.9
Operating System
I am using a Raspberry Pi4 with 4GB of RAM and the new Debian Bullseye dietpi Image.
Everything is up to date (Docker, Docker-Compose, etc..)
Is anyone else having this issue or even found a solution for that?

Your Internet connection could also be the issue. If you are running this in your home network you most likely only have a consumer-grade internet connection. Which means the upload speeds are very significantly worse than your download speeds. And slow upload speeds from your home network to the www means slow download speeds when accessing it from the www. When the traffic stays inside your local network, there is no bottleneck of course.


Cannot control endpoint through Amazon Alexa app

#908  Briefly summarize your issue:
Not able to control endpoint via Amazon Alexa app.
I have build SampleApp with Power Controller smart home feature enabled.
Extra endpoint device named Discoball is getting listed in Amazon Alexa app.
But I cannot control or do Power ON/OFF using the app. There is no such toggle.
I can say, "TurnOff Discoball" however to get TurnOff directive.
There is one Enable toggle however in app, which does not do the same thing.
What is the expected behavior?
App should show TurnOff/On option which could send directive to device.
What behavior are you observing?
Not able to control endpoint via Amazon Alexa app.
Provide the steps to reproduce the issue, if applicable:
Build sample app with PowerController endpoint API.
(-DENDPOINT_CONTROLLERS_POWER_CONTROLLER=1)
Tell us about your environment:

What version of the AVS Device SDK are you using?
 < 1.19.0>

Tell us what hardware you're using:
Mac
Tell us about your OS (Type & version):

[ ] MacOS

Please help with the same and let me know if I am missing something.
Or is there something that needs whitelisting etc?
Please find the attachment showing endpoint getting listed as Discoball:

Hi @vikramdattu, could you please provide more information? I'd like you to attach DEBUG9 logs and also provide the full cmake command you used to build the SDK.
You should not need to whitelist the account. I tried just briefly now and was able to control the Discoball via Alexa app, so I will need your help and some more information to figure out why this is not working for you.

Hi again @vikramdattu, I was mistaken earlier - I am indeed able to reproduce this problem. It seems only to happen when the power controller is enabled, and no other controllers are enabled. I'm going to file an internal ticket for this for us to investigate. Thanks!

Hi again @vikramdattu, I just wanted to follow up on this since I got a bit more information. This is not an issue with the SDK but rather with the Alexa app GUI. This is a known area for improvement in the Alexa app user interface.
Because the Discoball is an atypical device type, GUI controls for it will only show up if it supports one of the following controllers: Toggle, Mode, Range.
When you build the Discoball with just the Power controller, that option will not show up in the app.
If you want to see the controls in the Alexa app, you will need to enable at least one additional controller (Mode/Range/Toggle).
We have a ticket filed internally to improve this experience. I'm going to close this issue, since it's unrelated to the SDK, but please feel free to ask more questions.


Disabling email and phone login

Environment information
System:
  OS: Windows 10 10.0.19045
  CPU: (16) x64 11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz
  Memory: 48.14 GB / 63.81 GB
Binaries:
  Node: 20.9.0 - C:\Program Files\nodejs\node.EXE
  Yarn: undefined - undefined
  npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/backend: 0.13.0-beta.6
  @aws-amplify/backend-cli: 0.12.0-beta.6
  aws-amplify: 6.0.18
  aws-cdk: Not Found
  aws-cdk-lib: 2.131.0
  typescript: 5.3.3
AWS environment variables:
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
  AWS_STS_REGIONAL_ENDPOINTS = regional
No CDK environment variables

Description
When setting the loginWith properties of defineAuth, we should be able to disable both email and phone if externalProviders are set. Currently, we get a warning saying either phone or email login must be enabled.
We can disable them manually from the console. However, subsequent updates will override that console settings so it would be ideal to have them disabled in our defineAuth code.

Hey @ideen1 :wave: thanks for raising this! Are you looking to only allow signing in via an external provider? Unfortunately these values cannot be changed after the initial deployment, however you can disable user sign-ups, or use a pre-sign-up trigger to customize the desired sign-up experience
// amplify/backend.ts
import { defineBackend } from "@aws-amplify/backend"
import { auth } from "./auth/resource"
import { data } from "./data/resource"

const backend = defineBackend({
  auth,
  data,
})

const { cfnUserPool } = backend.auth.resources.cfnResources

cfnUserPool.adminCreateUserConfig = {
  allowAdminCreateUserOnly: true,
}

Yeah, certain enterprise applications require only externalProviders to be enabled. If it’s not something that can be changed after the first deployment, is it something that can be set before the first deployment at least? I don’t imagine needing to turn that back on if that’s what the user wants to do initially. I have already disabled user sign ups as you showed and that’s is a great step.

Hey @ideen1 thanks for clarifying! That makes total sense 🙂 the Cognito User Pool's username attributes cannot be changed after deployment, where this corresponds to loginWith.email and loginWith.phone in defineAuth. Disabling user self sign-up will block attempts at signing up, but allows user creation with the AdminCreateUser API in the event you'd like to create users manually. (this permission can also be denied for your AWS users)
An alternative is to use a custom Identity Pool to allow users to federate but with the caveat that a Cognito-native user will not be created. The Cognito-native users will allow you to bind specific attributes from your upstream identity provider to the Cognito user, bucket users into groups, etc.

Right I see, perhaps what I'm asking is to disable it on the Hosted UI. Then, the login form does not appear on the Hosted UI. I know this is possible through the console on the Hosted UI settings page even after the UserPool as been deployed. Is this something we could do from our Amplify backend configuration?

Hey the Gen 2 documentation has been updated, do checkout at https://docs.amplify.aws/react/build-a-backend/auth/concepts/usernames/ and let us know this assists in building your use case.

@ykethan Correct me if I am wrong but I believe that link is more related to usernames. My original question was the ability to completely remove email/password sign on from the UserPool during the initial deployment. @josefaidt Mentioned that it can not be done after initial deployment but I'm wondering if it can be done during the initial deployment.
The thing that is missing here is fully enforcing that no user can ever be able to "self-sign-up" .As mentioned above, the allowAdminCreateUserOnly is marked readonly, so I am not sure if this is safe to use.  It may be ideal to have something as crucial as this added as a argument to defineAuth.

Hey @ideen1 :wave: yes, while that property of adminCreateUserConfig is readonly, the parent is not and we can safely override it with our own settings. Using the snippet above, when sandbox is running we can inspect the rendered CloudFormation template in the artifacts at .amplify/artifacts

Closing the issue due to inactivity. Do reach out to us if you are still experiencing this issue.


Out of date

This page refers to the settings "Scale to fit" and "Lock Aspect Ratio".  These are no longer available.

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

ID: 73233c3d-8bfe-eadc-5b8a-264742ec7045
Version Independent ID: a34dc40d-9d6e-33b2-7e61-0c46a71d3608
Content: Create responsive layouts in canvas apps - PowerApps
Content Source: powerapps-docs/maker/canvas-apps/create-responsive-layout.md
Service: powerapps
GitHub Login: @emcoope-msft
Microsoft Alias: emcoope

@mherzog01
I still see "Scale to fit" and "Lock Aspect Ratio" in the application settings in the powerapps builder.

Could this be closed?

A screen shot shows these setting in Advanced Settings, whereas the screen shot above has them in a different heading.  Are these not different?

I think I see where the confusion is.
The top of the doc says that these settings live in File -> App Settings -> Screen Size + Orientation, which happens to have a subheading 'Advanced Settings'.
But you can see from the previous screenshot that there is also a File -> App Settings -> Advanced Settings, which is a different set of settings to do with delegation and experimental powerapps features.
The use of Advanced Settings in two places itself is confusing, but this doc itself references the two areas distinctly (eg later on it mentions about going to File -> App Settings -> Advanced' to switch on the component feature

Yes, makes sense.  Thanks for all your work and clear explanations on this.  You can close the issue.


How to change the default title?

Laravel Version: 5.5
Voyager Version: dev
PHP Version: 7.1

Description:
Where is the dashboard's index page? I wants to change the default title "voyager" to my project's title. How can I do that?

The page title is managed by Voyager Settings (/admin/settings): https://github.com/the-control-group/voyager/blob/master/resources/views/master.blade.php#L4


Loads of Vue warns with 6.6.0

Vue devtools version
6.6.0
Link to minimal reproduction
None
Steps to reproduce & screenshots

What is expected?
No errors. Seems that for each component state, render & currentRoute are accessed while not being defined on that particular component, causing the vue warn handler to kick in.
What is actually happening?

System Info
System:
    OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (8) x64 QEMU Virtual CPU version 2.5+
    Memory: 8.93 GB / 15.62 GB
    Container: Yes
    Shell: 5.2.15 - /bin/bash
  Binaries:
    Node: 20.11.1 - /usr/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 10.2.4 - /usr/bin/npm
  npmPackages:
    vue: 2.6.14 => 2.6.14

  System:
    OS: Windows 11 10.0.22631
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
    Memory: 7.25 GB / 31.68 GB
  Binaries:
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.21 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (121.0.2277.112)
    Internet Explorer: 11.0.22621.1

Any additional comments?
This started this morning, so with the 6.6.0 update.
I do not have a usable repro yet.

It seems to happen when the page you're working is being reloaded: the extension does not pick up this reload at all (old components and values are still being shown, and it is no longer possible to navigate at all). When reopening the Edge devtools (which seems to restarts the vueks/devtools) the errors start for me.
I strongly suspect this is related to the reload behaviour, which is reproducible on https://sfc.vuejs.org/. Steps:

Open the playground
Open the devtools
See the value of the msg ref change when typing in the default input field
Refresh the page
vuejs/devtools is no longer connected to the page being shown, navigation doesn't do anything, values are not updated etc.
Reopening the complete devtools and with it the vuejs/devtools solve the issue


HamburgerMenu: Content sometimes moves behind navigation bar

Sometimes, the content of the HamburgerMenu moves behind the navigation bar when starting up the application. In the demo app, it would look like this (assuming that it actually happens):

(here the whitespace on the left is missing)
Unfortunately it only happens rarely and thus is hard to reproduce, but it happens often enough to be a real annoyance.
I've already spent a lot of time on this to figure out why it's happening. The issue occurs because the column width is set to 1* in ColumnDefinition1 (SplitView.xaml) instead of the expected numeric value.
This unexpected value is set by the ClosedCompactLeftStoryboard animation, at some point the value of ColumnDefinition1.Width will be set to Auto (so a default GridLength) which then gets converted to 1* by the GridLengthAnimation later in this line of code:
return new GridLength(animationClock.CurrentProgress.Value * (toVal - fromVal) + fromVal, GridUnitType.Star);
It should be noted that it doesn't make any difference whether it's Auto or 1* though, both values cause the appearance to be incorrect.
The root issue seems to be that the binding of the To property occasionally breaks:

The bindings to ElementName=ProxyElement indeed seem a bit fishy to me, especially since there also is a resource
<FrameworkElement x:Key="ProxyElement" DataContext="{TemplateBinding TemplateSettings}" />
which isn't being used. Do you have a suggestion for reorganising the bindings so that such a problem can no longer occur?
Environment:

MahApps.Metro version: develop branch, April 28th
OS: Win10 18363
.NET Framework 4.6.0 target

Hi @floele-sp
can you test this with the current release v2.0.0? There were some fixes on this control, maybe it was solved "by accident"
Happy testing
Tim

Hi @timunie,
the issue still occurs in 2.0.0. Now 100% of the time though (so far). This makes testing much easier, but I'm still not quite sure what I should do with those bindings.

@floele-sp Can you create a sample with exactly this scenario? This makes it easier to debug this, because I can not see this in the main demo. Thx

@punker76 I created a small test project with some copy & paste XAML from our application. Apparently the issue reproduces, there is a data binding error as well.
I made the panel color transluscent so that you can see the parts that are covered unintentionally.
TestHamburgerBug.zip

@floele-sp I think your problem is the DockPanel. IMO a HamburgerMenu should use the complete space of a window (inside a Grid). In your case, if you really need the DockPanel with another Grid (Content) then you should change the DockPanel settings.
    <DockPanel LastChildFill="True">
        <Grid DockPanel.Dock="Right">
            <TextBlock>Content</TextBlock>
        </Grid>

        <mah:HamburgerMenu x:Name="sidebarPanel" ...

@punker76 When I try your suggested changes it looks like this:

How did you make the control fill the gap between the left bar and content?
I need the hamburger control to be constrained in any case.

@floele-sp This happens because of  OpenPaneLength="48". I will try to fix this.

@punker76 What about the binding errors though? Should they not be fixed?

@floele-sp Do you mean this?
System.Windows.Data Error: 40 : BindingExpression path error: 'IsDocked' property not found on 'object' ''HamburgerMenu' (Name='sidebarPanel')'. BindingExpression:Path=IsDocked; DataItem='HamburgerMenu' (Name='sidebarPanel'); target element is 'Grid' (Name=''); target property is 'NoTarget' (type 'Object')

Why? IsDocked is no property on HamburgerMenu.

@punker76 No, I mean the error seen in the Snoop screenshot in my first post. It also exists in the sample app.

@floele-sp This will be fixed in another PR.

@punker76 OK, great!
I just tested your fix, seems to work fine. Thanks.

@punker76 Did you already fix the binding issues? We still have problems with the HamburgerMenu unfortunately.


Training and validation accuracy multi label classification

Hi, thank you IndoNLU team for making this indobert model. I'm currently working on thesis with this IndoBERT for BertForMultiLabelClassification Task.
I have successfully run the "finetune_casa.ipynb" provided in the examples folder.
I used a private dataset and adapted it to the one in AspectBasedSentimentAnalysisAiryDataset on utils/data_utils.py . The dataset I use is imbalance.
However, after I visualize using matplotlib, the result accuracy between train and eval is much different and the accuracy of eval tends to be static. I have also tried to do something similar using the dataset that has been provided in dataset/casa_absa-prosa however, the results are also not much different from the dataset that I use.
this is the code used for fine tuning  :
train_loss_lists = []
train_acc_lists = []
eval_loss_lists = []
eval_acc_lists = []

# Train
n_epochs = 8
for epoch in range(n_epochs):
    model.train()
    torch.set_grad_enabled(True)

    total_train_loss = 0
    list_hyp, list_label = [], []

    train_pbar = tqdm(train_loader, leave=True, total=len(train_loader))
    for i, batch_data in enumerate(train_pbar):
        # Forward model
        loss, batch_hyp, batch_label = forward_sequence_multi_classification(model, batch_data[:-1], i2w=i2w, device='cuda')

        # Update model
        optimizer.zero_grad()
        loss.backward()
        optimizer.step()

        tr_loss = loss.item()
        total_train_loss = total_train_loss + tr_loss

        # Calculate metrics
        list_hyp += batch_hyp
        list_label += batch_label

        train_pbar.set_description("(Epoch {}) TRAIN LOSS:{:.4f} LR:{:.8f}".format((epoch+1),
            total_train_loss/(i+1), get_lr(optimizer)))

    # Calculate train metric
    metrics = absa_metrics_fn(list_hyp, list_label)
    print("(Epoch {}) TRAIN LOSS:{:.4f} {} LR:{:.8f}".format((epoch+1),
        total_train_loss/(i+1), metrics_to_string(metrics), get_lr(optimizer)))
    train_acc_lists.append(metrics['ACC'])
    current_train_loss = round(total_train_loss/(i+1), 4)
    train_loss_lists.append(current_train_loss)

    # Evaluate on validation
    model.eval()
    torch.set_grad_enabled(False)

    total_loss, total_correct, total_labels = 0, 0, 0
    list_hyp, list_label = [], []

    pbar = tqdm(valid_loader, leave=True, total=len(valid_loader))
    for i, batch_data in enumerate(pbar):
        batch_seq = batch_data[-1]
        loss, batch_hyp, batch_label = forward_sequence_multi_classification(model, batch_data[:-1], i2w=i2w, device='cuda')

        # Calculate total loss
        valid_loss = loss.item()
        total_loss = total_loss + valid_loss

        # Calculate evaluation metrics
        list_hyp += batch_hyp
        list_label += batch_label
        metrics = absa_metrics_fn(list_hyp, list_label)

        pbar.set_description("VALID LOSS:{:.4f} {}".format(total_loss/(i+1), metrics_to_string(metrics)))

    metrics = absa_metrics_fn(list_hyp, list_label)
    print("(Epoch {}) VALID LOSS:{:.4f} {}".format((epoch+1),
        total_loss/(i+1), metrics_to_string(metrics)))
    eval_acc_lists.append(metrics['ACC'])
    current_eval_loss = round(total_loss/(i+1), 4)
    eval_loss_lists.append(current_eval_loss)

The result of matplotlib look like this :

Obviously there's some issue with how this is checked, but I can't put my finger on it. Is there anything I can check?

Hi @exzt, first of all, if the label is imbalanced, it will be better to use F1 or other evaluation metrics that are less skewed.
Regarding the issue, before getting into the accuracy, I feel quite unsure about the loss curve, does the loss on the first few steps drop significantly? One would expect a steep downward trend of the training loss, especially on the early steps/epochs during the fine-tuning. Do you observe the same behavior on the early steps of the fine-tuning?
Additionally, based on the train loss, it seems like something is a bit off (either the hyperparameter settings or other problems). You can first try to overfit the model, perhaps you can try to turn off all the drop-out using model.eval() before each training step and try to tune the model and see whether you can reach 0 training loss.
If you can achieve 0 training loss, then you can try to reapply the drop-out and other regularizers to achieve a better generalization of the model such that it can perform well in both the validation and the test sets. If you cannot achieve 0 training loss, I would suggest checking your data (or code), there are probably some problems that hinder the model to learn well on the training set.
Hope it helps!

Hi, indoNLU.
Thank you for making this indobert model.
I am working on my coursework related to bert model on multilabel data too. I found this model very helpful. However, when I execute the code in "finetune_casa.ipynb", I found something odd in the accuracy of the valid data, where the value remains on the same line.

@exzt @cynthiasbahri : Sorry for the late reply and thank you for your interest in using IndoNLU. I just updated the requirements.txt to ensure the multi_label_classification.py works with the newer transformers and pytorch version. I try running our dataset and it seems to work fine for our dataset.  Additionally, if you have an imbalance dataset, I think that won't be a problem as long as the train, valid, and test distribution are similar. In case your dataset is highly imbalanced (e.g.: 99% vs 1% class ratio), I would suggest using other metrics that don't rely on a single threshold such as AUROC and AUPRC to get a more representative evaluation score.

Hi @SamuelCahyawijaya
Thank you very much for the response and solution that you gave, I really look forward to this
I learned a lot from here, I am looking forward to the next amazing work


upgrade /statuses view

add header sort

we can sort statuses by clicking headers

add size option

we can see more than 25 statuses

@pramodshinde
This is a whole changes. https://github.com/utgarda/sidekiq-status/pull/77/files
I think the commit  should not be one commit because this pull-request includes two changes.
And all changes is only related to Web UI.

@mosasiru -  Its okay to make it one commit even if change includes multiple files changes, since all changes is only related to Web UI, I would suggest to squash your commits to one commit as its same feature, use git squash command to this. If your are finding difficulties doing this let me know.

I meaned not two files commits but two functional commits, but I see your point. I squashed.

@mosasiru Perfect! :+1:  I'll merge this after some testing at my side.

thank you!


stream go mod vendor output

Summary

Leverage the packit scribe.LogEmitter writer to stream go mod vendor logs in real-time.
The outcome will be logs that look like this:
[builder] Paketo Buildpack for Go Mod Vendor 1.2.3
[builder]   Checking module graph
[builder]     Running 'go mod graph'
[builder]       Completed in 219ms
[builder]
[builder]   Executing build process
[builder]     Running 'go mod vendor'
[builder]       go: downloading github.com/satori/go.uuid v1.1.0
[builder]       go: downloading github.com/BurntSushi/toml v0.3.1
[builder]       Completed in 356ms

Use Cases

Checklist

[ ] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[ ] I have reviewed the styleguide for guidance on my code quality.
[ ] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@paketo-buildpacks/go-maintainers I have opted not to add the log streaming for the go mod graph command, as the output is very similar to the output from go mod vendor, and the logs will still be output in the event of a failure. Let me know if you want me to add that.

@go-maintainers I have opted not to add the log streaming for the go mod graph command, as the output is very similar to the output from go mod vendor, and the logs will still be output in the event of a failure. Let me know if you want me to add that.

Not a go maintainer but this seems reasonable to me.


FIX: GAT y_pred error when inconsistent axis

Some sklearn classifiers can predict y_pred_ with shape (n_trials, 1) instead of (n_trials,)

see https://github.com/scikit-learn/scikit-learn/issues/5058

ready for merge if travis' happy

besides LGTM

thanks @kingjr !


 I'm using a white container on a white background in the code example.
Run the web app using the HTML renderer.
See that it doesn't render correctly on mobile and desktop Safari. [It's fine on Chrome. So if you want to try it on desktop, copy the link from your debug Chrome instance and open it using Safari]

Expected results
Actual results

Reproducible on both iOS and macOS.

Code sample
import 'package:flutter/material.dart';

class ShadowTest extends StatelessWidget {
  const ShadowTest({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Material(
      color: Colors.white,
      child: Center(
        child: Container(
          width: 100,
          height: 100,
          decoration: BoxDecoration(
            color: Colors.white,
            boxShadow: [
              BoxShadow(
                color: Colors.black26,
                // This is not rendered correctly on the mobile browsers.
                offset: Offset(15, 15),
                blurRadius: 40,
              ),
            ],
            borderRadius: BorderRadius.circular(30),
          ),
        ),
      ),
    );
  }
}

Logs
No logs were found between backlits after running flutter run --verbose.
No analysis errors were found after running flutter analyze.

[✓] Flutter (Channel stable, 2.10.0, on macOS 12.1 21C52 darwin-x64, locale en-US)
    • Flutter version 2.10.0 at /Users/behnamsattar/tools/bin/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5f105a6ca7 (8 days ago), 2022-02-01 14:15:42 -0800
    • Engine revision 776efd2034
    • Dart version 2.16.0
    • DevTools version 2.9.2

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/behnamsattar/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

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

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

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

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

Issue is reproducible on stable and master.
This seems to be an issue with Safari on iOS and macOS. I couldn't reproduce on an android device running chrome but it reproduced on all my browsers on iOS.

screenshots

safari-ios
safari-macOS
chrome-macOS

code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'GitHub Client',
      theme: ThemeData(
        primarySwatch: Colors.blue,
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: const ShadowTest(),
    );
  }
}

class ShadowTest extends StatelessWidget {
  const ShadowTest({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Material(
      color: Colors.white,
      child: Center(
        child: Container(
          width: 100,
          height: 100,
          decoration: BoxDecoration(
            color: Colors.white,
            boxShadow: [
              BoxShadow(
                color: Colors.black26,
                // This is not rendered correctly on the mobile browsers.
                offset: Offset(15, 15),
                blurRadius: 40,
              ),
            ],
            borderRadius: BorderRadius.circular(30),
          ),
        ),
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 2.10.1, on macOS 12.2 21D49 darwin-arm, locale en-GB)
    • Flutter version 2.10.1 at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision db747aa133 (13 hours ago), 2022-02-09 13:57:35 -0600
    • Engine revision ab46186b24
    • Dart version 2.16.1
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

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

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[☠] IntelliJ IDEA Community Edition (the doctor check crashed)
    ✗ Due to an error, the doctor check did not complete. If the error message below is not helpful, please let us know about this issue at https://github.com/flutter/flutter/issues.
    ✗ FormatException: Unexpected extension byte (at offset 5)
    • #0      _Utf8Decoder.convertSingle (dart:convert-patch/convert_patch.dart:1789:7)
      #1      Utf8Decoder.convert (dart:convert/utf.dart:351:42)
      #2      InputStream.readString (package:archive/src/util/input_stream.dart:207:30)
      #3      new ZipDirectory.read (package:archive/src/zip/zip_directory.dart:40:30)
      #4      ZipDecoder.decodeBuffer (package:archive/src/zip_decoder.dart:19:30)
      #5      ZipDecoder.decodeBytes (package:archive/src/zip_decoder.dart:14:12)
      #6      IntelliJPlugins._findPluginXml (package:flutter_tools/src/intellij/intellij.dart:130:44)
      #7      IntelliJPlugins._readPackageVersion (package:flutter_tools/src/intellij/intellij.dart:141:40)
      #8      IntelliJPlugins.validatePackage (package:flutter_tools/src/intellij/intellij.dart:63:35)
      #9      IntelliJValidator.validate (package:flutter_tools/src/intellij/intellij_validator.dart:103:15)
      #10     asyncGuard.<anonymous closure> (package:flutter_tools/src/base/async_guard.dart:111:32)
      #11     asyncGuard.<anonymous closure> (package:flutter_tools/src/base/async_guard.dart:109:18)
      #12     _rootRun (dart:async/zone.dart:1426:13)
      #13     _CustomZone.run (dart:async/zone.dart:1328:19)
      #14     _runZoned (dart:async/zone.dart:1861:10)
      #15     runZonedGuarded (dart:async/zone.dart:1849:12)
      #16     runZoned (dart:async/zone.dart:1780:12)
      #17     asyncGuard (package:flutter_tools/src/base/async_guard.dart:109:3)
      #18     Doctor.startValidatorTasks (package:flutter_tools/src/doctor.dart:205:9)
      #19     Doctor.diagnose (package:flutter_tools/src/doctor.dart:309:47)
      #20     DoctorCommand.runCommand (package:flutter_tools/src/commands/doctor.dart:50:48)
      #21     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1320:12)
      <asynchronous suspension>
      #22     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1161:27)
      <asynchronous suspension>
      #23     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
      <asynchronous suspension>
      #24     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
      <asynchronous suspension>
      #25     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
      <asynchronous suspension>
      #26     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
      <asynchronous suspension>
      #27     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
      <asynchronous suspension>
      #28     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
      <asynchronous suspension>
      #29     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
      <asynchronous suspension>
      #30     main (package:flutter_tools/executable.dart:94:3)
      <asynchronous suspension>

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

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 12 (API 31) (emulator)
    • iPhone 13 (mobile)          • 304CA91D-8D77-4AAE-A50F-ECFC57AFD011 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-2 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 12.2 21D49 darwin-arm
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 2.11.0-0.0.pre.501, on macOS 12.2 21D49 darwin-arm, locale en-GB)
    • Flutter version 2.11.0-0.0.pre.501 at /Users/nexus/dev/sdks/flutters
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 0ce527eb91 (10 hours ago), 2022-02-09 15:05:03 -0800
    • Engine revision a57061eda8
    • Dart version 2.17.0 (build 2.17.0-87.0.dev)
    • DevTools version 2.10.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

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

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] IntelliJ IDEA Community Edition (version 2021.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin version 213.5744.122

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

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 12 (API 31) (emulator)
    • iPhone 13 (mobile)          • 304CA91D-8D77-4AAE-A50F-ECFC57AFD011 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-2 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 12.2 21D49 darwin-arm
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

As a workaround, you can try using MaskFilter.blur or ImageFilter.blur?

@yjbanov, using the blur effect seems to be a bit overkill as it would not perform very well and would require me to move things around in the code. For now, I've just decided to remove the offset from my shadows.


Not logging trace id after AWS Auto Instrumentation Agent upgrade to 1.2.0 or 1.4.0

Describe the bug
We are tracing our SpringBoot/SpringCloudGateway application by the AWS Auto Instrumentation Agent. After I change the release from Release v1.1.0 to Release v1.4.0, the traceId shows empty, and the key AWS-XRAY-TRACE-ID in MDC context map has also disappeared.
Steps to reproduce
java -Dspring.profiles.active=local -javaagent:/aotel/aws-opentelemetry-agent-1.4.0.jar one.jar
"one.jar" is a SpringBoot application, configuring by logback pattern:
%d{yyyy-MM-dd HH:mm:ss.SSS}\t[%X{AWS-XRAY-TRACE-ID}] - %msg%n
What did you expect to see?
Before upgrade, using agent 1.1.0:
java -Dspring.profiles.active=local -javaagent:/aotel/aws-opentelemetry-agent-1.1.0.jar one.jar
the log is showing like this:
2021-07-29 18:50:09.618  [1-610287e1-4bad020c021ab9b074d04217@a01edea91aca582c] origin request body: ...
What did you see instead?
After upgrade to agent 1.2.0 or 1.4.0, logging like this:
2021-07-29 18:50:09.618  [] origin request body: ...
There are none AWS-XRAY-TRACE-ID in MDC context by debug mode:
  "mdc": {     "appVersion": "",     "interface io.opentelemetry.javaagent.shaded.io.opentelemetry.api.trace.Span": "{opentelemetry-trace-span-key=RecordEventsReadableSpan{traceId=610399e3815dc59e58765f785125a19c, spanId=52817ef4208de551, parentSpanContext=ImmutableSpanContext{traceId=610399e3815dc59e58765f785125a19c, spanId=0877b939030ee172, traceFlags=01, traceState=ArrayBasedTraceState{entries=[]}, remote=false, valid=true}, name=FilteringWebHandler.handle, kind=INTERNAL, attributes=AttributesMap{data={thread.name=reactor-http-nio-4, thread.id=43}, capacity=128, totalAddedValues=2}, status=ImmutableStatusData{statusCode=UNSET, description=}, totalRecordedEvents=0, totalRecordedLinks=0, startEpochNanos=1627625955919426700, endEpochNanos=0}, opentelemetry-traces-server-span-key=RecordEventsReadableSpan{traceId=610399e3815dc59e58765f785125a19c, spanId=0877b939030ee172, parentSpanContext=ImmutableSpanContext{traceId=00000000000000000000000000000000, spanId=0000000000000000, traceFlags=00, traceState=ArrayBasedTraceState{entries=[]}, remote=false, valid=false}, name=HTTP POST, kind=SERVER, attributes=AttributesMap{data={net.peer.port=51264, schoolCode=415, http.method=POST, clientType=, http.user_agent=PostmanRuntime/7.28.2, platformVersion=, http.url=http://localhost:8080/v1/aggregate/user/info, platform=, studentId=7592518, http.client_ip=0:0:0:0:0:0:0:1, net.peer.ip=0:0:0:0:0:0:0:1, thread.name=reactor-http-nio-4, deviceName=, appVersion=, thread.id=43, http.flavor=1.1, appName=}, capacity=128, totalAddedValues=17}, status=ImmutableStatusData{statusCode=UNSET, description=}, totalRecordedEvents=0, totalRecordedLinks=0, startEpochNanos=1627625955919001800, endEpochNanos=0}}",     "appName": "",     "requestMethod": "POST",     "reactor.onDiscard.local": "reactor.core.publisher.Operators$$Lambda$1192/593986789@222b5946",     "requestUri": "/v1/aggregate/user/info",     "deviceName": "",     "platform": "",     "studentId": "7592518",     "hostname": "ZT-081201",     "clientType": "",     "platformVersion": "",     "schoolCode": "415",     "remoteAddr": "0:0:0:0:0:0:0:1",     "trace_id": "610399e3815dc59e58765f785125a19c",     "trace_flags": "01",     "span_id": "0877b939030ee172"   },
I don’t know where the usage has changed, or there is a bug here, any suggestions or code would be appreciated.

@drazzi-lee Thanks for filing this issue - this seems to be a bug, we will fix and issue a patch soon

@drazzi-lee 1.4.1 has been released and should propagate through Maven Central shortly, containing the fix for this. Thanks again for reporting!


Extract Overpass API runtime error from

Addresses #26. Example for failing request: https://nrenner.github.io/achavi/?changeset=61744384

Thanks!


Improve framebuffer creation error message to mention size limits

Low-end hardware is often limited to framebuffers with a width/height of 2048 or 4096 pixels.
This also turns the warning message into an error message.
This closes https://github.com/godotengine/godot/issues/38879.

We can and should poll for device limits before doing this. We can actually check max framebuffer size for the user and conclusively tell them that the allocated framebuffer is too big. I started a work in progress PR for it a few months ago but haven't quite finished.
I'm concerned that many users won't realize there are size limits, or how to figure out the size limit for their target hardware.

We can and should poll for device limits before doing this. We can actually check max framebuffer size for the user and conclusively tell them that the allocated framebuffer is too big. I started a work in progress PR for it a few months ago but haven't quite finished.
I'm concerned that many users won't realize there are size limits, or how to figure out the size limit for their target hardware.

Should we still merge this or a variant of it in the meantime, or close this?

I'd prefer to close this and have a proper PR.

Superseded by https://github.com/godotengine/godot/pull/45982.


LICENSE mismatch

The repo has Apache-2.0 and the script uses GPL-3.0-or-later. I am about to submit some PRs assuming 2.0. I will also provide a PR to fix the license.

Thanks a lot, closing this.


Filters Not Displaying Properly on Mobile View in Leaderboard Page

Description:
When viewing the leaderboard page on mobile devices, the filters (Duration, Role, and other filters) are not displayed correctly. Specifically, when clicking on any of the filters, the content gets cut off, and the scroll bar to view the full list of options is not visible or working correctly.
Steps to Reproduce:

Go to the Leaderboard page.
Switch to mobile view (using browser dev tools or on an actual mobile device).
Click on the Duration filter.
Click on the Role filter.
Click on other filters.
Observe that the filter dropdown content is either partially visible or not scrollable, causing some options to be hidden.

Expected Behavior:

The filters should be fully visible, and if the content exceeds the available space, the dropdown should be scrollable without being cut off.
Scrollbars should either be visible or invisible while still allowing users to scroll through the filter options.

Actual Behavior:

The filter options are either partially hidden or not accessible in mobile view, and there is no visible scrollbar to scroll through the filter options.
https://github.com/user-attachments/assets/44e5b600-9393-4f9c-b40f-384e93d27982

I Would like work on these issue.Please Assign it to me


Feat fast mosaic

Closes https://github.com/aimakerspace/PeekingDuck/issues/519
Changes include:

Change underlying mosaic algorithm to use 2x cv2.resize()

A downsize to (mosaic_level, mosaic_level) followed by an upsize to the original size

Change both mosaic_bbox and mosaic to private
Convert mosaic to an instance method so it can access self.mosaic_level directly without have to be passed in as an argument
Check that bbox coordinates are within bounds

There are some differences in the mosaiced output between the current implementation and PR implementation:

Current
PR
Remarks

Output may appear jittery as it is more sensitive to source pixel color

Jitteriness is less noticeable with higher mosaic_level

Less noticeable with smaller bounding boxes too

While a robust comparison was not performed, the PR implementation provides an improvement in FPS performance for rows 2 and 3 in the above table:

23.94 vs 25.26 FPS
19.99 vs 21.49 FPS

NOTE: Similar to the current implementation, the PR implementation does not check that an appropriate mosaic_level is used. When mosaic_level is large or approximately same as bbox size, the output is not "properly" mosaiced, i.e., the person's privacy is not actually protected.

Code looks good to go.
Just two minor comments:

Past tense of mosaic (verb) is spelled mosaicked. Can update documentation accordingly.
In above PR examples, would be instructive to mention the mosaic_level used, to give users an idea of what are good mosaic level values.

Fixed typo and added video resolution with mosaic_level used for the examples in the opening comment.


LU fix

Pull Request Description
Closes #654
Check lower bound is less than the upper bound
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
What are the significant changes in functionality due to this change request?

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

@mandd I changed the description from "Addresses " to "Closes" #653 . Otherwise the merge will not close it.

Job Test qsubs on ceec6e7 : invalidated by @alfoa

Job Test mac on ceec6e7 : invalidated by @alfoa

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code. OK
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts). N/A
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details. OK
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.  OK
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True. OK. NO MODEL CHANGES
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync. N/A
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done. #654
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added? N/A

PR Check list passed...
Issue closure list passed...


Change anything in en.yml that needs to be changed from Authy

If something references Authy, it needs to be changes in an appropriate manner.

@wwahammy There are no references `authy' in the 'en.yml' file or the 'devise.en.yml' file.
I did find a 'devise.authy.en.yml' file. Did you mean for that file to be deleted or changed?

@wwahammy Is this the appropriate manner? This info was taken from the Twilio-authy-devise readme:
Do a project code wide search & replace of these terms devise-authy -> devise-twilio-verify authy_ -> twilio_verify_ _authy -> _twilio_verify authy- -> twilio-verify- -authy -> -twilio-verify Authy -> TwilioVerify

@wwahammy Is this the appropriate manner? This info was taken from the Twilio-authy-devise readme:
Do a project code wide search & replace of these terms
* devise-authy -> devise-twilio-verify

* authy_ -> twilio_verify_

* _authy -> _twilio_verify

* authy- -> twilio-verify-

* -authy -> -twilio-verify

* Authy -> TwilioVerify

We're only looking to change the authy in the values in en.yml, not the keys. I've edited the issue to better reflect that.
More generally, while jayywolff's fork may be a good reference, we made different design decisions than he did. So his changes and decisions may or may not be appropriate.


moment.js complains about your code

Deprecation warning: moment construction falls back to js Date. This is discouraged and will be removed in upcoming major release. Please refer to https://github.com/moment/moment/issues/1407 for more info.
Arguments: [object Object]
...
getUTCTime@http://.../js/datetimepicker/datetimepicker.js:396:42
$render@http://.../js/datetimepicker/datetimepicker.js:433:85
...
I've downloaded the latest version of moment.min.js from the official website.
I didn't do much else, just inserted a datetimepicker into the code of my AngularJS controller.

Basically a replace of all instances of moment( with moment(new Date( in the datetimepicker.js file seems to resolve this as instructed in the linked moment URL. I counted 6 occurrences in this file. Testing so far indicates this was all that is needed.

Fixed in the latest release


. QA GREEN

Tutorial issue found: https://github.com/sap-tutorials/Tutorials/blob/master/tutorials/btp-app-create-ui-freestyle-sapui5/btp-app-create-ui-freestyle-sapui5.md contains invalid tags. Even though your tutorial was created, the invalid tags listed below were disregarded. Please double-check the following tags:

sogtware-product>sapui5

Affected server: QA GREEN

https://github.com/sap-tutorials/Tutorials/pull/7341


window.Store.Wap was depracated ? (web api)

window.Store == undefined

Please refer to #45 to continue this discussion.


zooming far out crashes signal plots

recreating the bug:

start the "plot types" demo
clear
plot a signal (10M points)
zoom out horizontally very far

If you zoom out far enough it doesn't crash. If you zoom out smoothly it will. It crashes in the "RenderLowDensity" function, which is probably a clue to the problem - that function should only be used when signals are zoomed very far in. Therefore, this problem will probably be corrected code in this function:
https://github.com/swharden/ScottPlot/blob/ffe802fed54f06904f949ea61b1a9eb2e5740c6a/src/ScottPlot/plottables/PlottableSignal.cs#L132-L148

Fixed
https://github.com/swharden/ScottPlot/blob/310a27bc0e337f4d426495ed836becec3ff82c40/src/ScottPlot/plottables/PlottableSignal.cs#L142-L148
But now the graph disappears (rather than crashing) when you zoom far out...

I have same problem then testing 500M poins. Zoomed out not far, 2x-4x. This problem based on int overflow during indexes calculation. Int32.MaxValue not so far from 500 millions :).  Get negative visible points count becouse overflow in addition, goes wrong render type and crashed on trying allocate negative size array.
This problem may be more complex then it looks. Whole library based on int types, so fixing one place may be not enouth.

Posible solutions:

calculate indexes using long type
block zoming to that ranges
stay as is, this happened on rare use cases
stay as is, but documented this behavour, to let users avoid them

Heh, I came up with a different solution still! A custom function to render very zoomed-out data as a single vertical line.
https://github.com/swharden/ScottPlot/blob/500b655f604ff73b0f432bfc97425e350545bf8a/src/ScottPlot/plottables/PlottableSignal.cs#L155-L162
https://github.com/swharden/ScottPlot/blob/500b655f604ff73b0f432bfc97425e350545bf8a/src/ScottPlot/plottables/PlottableSignal.cs#L61-L68
... another speed boost for PlotSignalConst() could be storing the values of min/max so they don't have to get looked-up repeatedly.

On huge signals before crasing it looks not like single vertical line.
Render calls only then signal displaying must be change. This means different intervals in most cases, story previous gives nothing.
I think it have enouth speed at queries.
#73 brings significant reduce trees initial calculation time. About 1 second for 50M signal.

Sounds good, thank you!

I settled on this solution:
https://github.com/swharden/ScottPlot/blob/bf4d562f78c2168bf27179ce3ffbd9ae5bb21b60/src/ScottPlot/plottables/PlottableSignal.cs#L155-L166


Quitting command window should cancel search

To be consistent with other command windows like q:, vim-grepper should only execute the search if the user hits enter. If the users quits the window with :q, the search should be cancelled.
Step to repro:
:Grepper

:q
(I'm using version b8f52fc)

Command window? Do you mean at the prompt?

Ahh sorry, my repro steps markdown formatting must have been bad.
Steps to repro:
:Grepper
<C-f>
:q

Oh. Yea, I should have believed you when you said "command(-line) window", but honestly, I never use <c-f> myself, only <c-n>/<c-p, so it didn't came to mind.
You can leave the cmdwin with the current line with <c-c>. So, hitting <c-c> twice hopefully works for you.
I can't come up with a better idea anyway. It would probably involve hooking into CmdwinEnter and setting/unsetting global variables to detect if the cmdwin was opened from a Grepper prompt.. pretty messy.

By the way, in case it isn't clear: When you use :q in the cmdwin, you discard the cmdwin and the prompt, which leads to an empty query which means using the word under the cursor as query.

Okay, I thought about this for a while and every other solution, than simply using what Vim already provides, would involve wild hacks that probably break in some cases.
So, please use <c-c><c-c> in your case!

Gotcha. Thanks!


I have changed my repo name and have to update the link in index.md

do i update the link and send a pull request again with the new link.
Team "Constant Variables"

@rxhxt , https://github.com/ISTESRMNCR/CODE-CAMP-2020/issues/68#issuecomment-663021962

Hiya, checked the code but the only place I could see anything with a link to github was in index.js
Are you looking to change the link in the  ?

Hey! @Serhazor, thanks for taking interest. But don't think this issue requires any change in the website. But Thanks for your support.

When will the list be out for the teams who made it through the first round of evaluation?

@KaranBengani , This issue is closed, I merely saw your query, please make it up to issue's section.
FIrst Evaluation [ Divided into 2 parts ]

Documentaion ( Status [ DONE ] )
CODE i.e neatness and percentage complete ( Status [ Pending ] )

Requesting you to push the code for Evaluation Round... by 10 PM Today i.e  ( 25th July, 2020 )
When the Score sums and will get back to you. and will announce the finalist in the group itself don't worry.

From now please create a new issue section. I can't look after CLOSED ISSUES... CLOSED ISSUE MEANS THE ISSUE IS RESOLVED if may i say.


Use Rational for specification of aspect ratio

Avoids floating-point pitfalls

I'll integrate the same change in pluto_*.jl since I want it to serve as an example of best practices.


Synth Modes

As suggested by lognes. Modes would hide certain options for a cleaner workflow (eg. an NES mode that only allows 3 chip and 1 noise channel, or a Modbox mode that only allows features from that mode, etc.). The current configuration would work as a "superset" mode that houses every feature.
I assume this would work like themes/layouts internally

I think most of the trouble with this would be changing the way certain UI elements works so you can remove options without messing with the index or snap sliders to a smaller range of values or whatnot

Okay so, I wanna give my opinions on this issue specifically. I don't like the idea at all.
Adding Synth Modes to UltraBox would literally kill any reason to use ModBox at all, this might not seem like that bad of a thing given that ModBox is rather archaic in nature, but there's larger underlying issue than just giving people zero reasons to use ModBox. Adding Synth Modes to UltraBox would remove any desire to ever modify ModBox ever again. The one thing that draws people to ModBox is its unique synth, and some people might also want to make their own mods of ModBox to add things that weren't there before. Adding Synth modes would remove any desire for future modders to try and mod ModBox, which isn't something that we should actively desire.
The great thing about BeepBox Mods is the fact that anyone can start a mod at any time. I know that UltraBox is supposed to be the "Ultimate BeepBox Mod" that "adds all the cool features from other mods". But I think that's not a very good idea. Not only is UltraBox eventually gonna get bloated with features that other mods excel at given their focus on that feature, it's also going to get to a point where UltraBox becomes too overbearing for its own good. Which is why I think having other BeepBox mods that do their own thing is much more interesting and productive. First off, having mods that add unique features gives each BeepBox user their own choice in what they want. Maybe they want a feature that goes well with Electronic music but don't care about a feature that doesn't help them at all with electronic music. Well you could have a BeepBox Mod that focuses on making Electronic music easier for people to make.
ModBox is also one of these situational mods, It has a unique form of synth that no other BeepBox mod has, and that's something special. People that want to use ModBox should just use ModBox, or a mod of ModBox that makes it easier. There's also those recent mods that's been popping up here recently like MidBox and Slarmoo's Box which both add their own form of envelopes that are different from each other in their own way. I think a better direction for UltraBox to take would be to make the most Stable, Reliable, and Standard BeepBox mod to use. That way if people want to use the most polished BeepBox mod instead of all these experimental mods out there, then UltraBox is always there waiting for them to use it.
Overall, I think we shouldn't add this feature. I'm sorry for having you read through my entire essay about my opinions on this feature. But I really do hope that you'll focus on other things instead of this.


docs: Fix typo in setup-advanced.md

There was a grammatical typo in setup-advanced.md. I have fixed the typo by changing long to longer
Testing plan:
GIFs or screenshots:

Merged, thanks @aditya-mitra!  Note that I added a . to the end of the commit message title in line with our commit style.
Check out the Zulip commit message guidelines for more details: https://zulip.readthedocs.io/en/latest/contributing/version-control.html#commit-messages

I will keep that in mind throughout my contributions


Setting rdo_lookahead_frames to 1 doesn't reduce the lookahead window to 1

I suspect #1700 is similar to this but there was no meaningful description or update provided.
I'm using the rav1e C libraries in a low-latency environment. This is part of my configuration code:
rav1e_config_parse_int(rav1eConfiguration, "rdo_lookahead_frames", m_configuration.rdo_lookahead_frames);
rav1e_config_parse(rav1eConfiguration, "low_latency", "true");

I'm setting the lookahead window to 1 which from what I've heard earlier is the minimum value, and low_latency to true. But even then, I still need to put 9 frames into the encoder before I can receive one. Once I've received the first frame, I receive a new AV1 frame every time I put a raw frame in, but the 8-frame-long buffer still introduces undesired latency into my pipeline (over 250ms).

Thanks, I've been able to reproduce this on my own code at $dayjob using the C API (luckily it's only for VoD), and also in the rav1e CLI tool, and in FFmpeg.
I gave it a cursory look, and it looks to be a somewhat complex issue; that is, it's not just a simple math error in needs_more_fi_lookahead when calculating the number of needed frames - ready_frames seems to be the culprit, and I cannot easily find what is causing this (being unfamiliar with the voodoo it invokes). Possibly @lu-zero or @shssoichiro or @ycho has further insights, or possibly Tim.
I guess the bug you referenced has a cursed tag for a reason...

@yannlandry, hi- thanks for trying this. and sorry for not adding background or story for #1700. What I worried was rav1e seems missing realtime more that requires smallest possible frame latency. Which was once achieved when frame lookahead was not enabled by default for all speed levels.
@dwbuiten, hi-. as said above, it seems a decision from some of us preferring to exploit frame lookahead by all times. I think @tdaede can add comments here.

FWIW I landed a test for this and currently the 4th frame in creates the 1st packet out, e.g. we have a latency of 3 when we want 0. I believe there are actually 3 separate locations that cause this bug, I'm fixing them one at a time.


Different KB with same data giving different results of the same query

I have two different knowledge bases created in two seperate QnA. One for staging and one for development environment. Both the kb's are trained with the same data.
But the user query to both the kb's yield different results.
The notable difference is the location of app service & app service plan associated with each qnamaker.
What can be the issue?

Hello @anishjaindev, Can you share the Azure document link / URL that you are referring to ?
This azure-docs repository deals about feedback related to particular Azure document page (like correcting doc bugs, doc enhancements, product issues related to wrong doc instructions if any, etc.) so that's the reason for asking related Azure document link / URL to get more context of this issue if it's intended to update / correct / enhance anything in the referred Azure document.

Closing this issue for now as there is no response to the previous comment.


Additional dependencies info

Dear David,
Could you please include the info on additional required dependencies that are needed (by rdi-live/live) and implied but not included. Perhaps what has to be in the $GOPATH for it to build.
Any help and clarification is appreciated! Alternatively some added guidance in the instruction / documentation that covers that (lists the prerequisites from clean slate) in a reasonably comprehensive way would be great.
Evgeny.

Hello Eugene,
The README states basic installation instructions.  While basic, these are complete.  The single stated prerequisite is go 1.11 or newer.  If my memory serves me correctly, "modules" were supported automatically for out-of-gopath builds starting from go 1.11.  All dependencies are stated idiomatically using the go module framework, and are automatically collected by the go toolchain in the command stated in the README:
go get github.com/rditech/rdi-live/tools/...

Upon successful completion of the above command, all of the tool binaries, including rdi-live, are placed in your $GOPATH/bin.  If you need to modify the code, I recommend working with the repo outside of your gopath, and building the binaries with
go install ./tools/...

when in the root repo directory.  All of this is completely go-idiomatic, and extra documentation of dependencies would only be superfluous.  You can, however, take a look at the go.mod file to see particular dependencies in the go modules format.  A word to the wise: be careful updating go.mod, since breaking changes can occur.

Gotcha, much appreciated.
Will try to move fwd...
Best,
Eugene.
On Wed, Feb 19, 2020, 21:45 David Blyth<EMAIL_ADDRESS>wrote:

Hello Eugene,
The README states basic installation instructions. While basic, these are
complete. The single stated prerequisite is go 1.11 or newer. If my memory
serves me correctly, "modules" were supported automatically for
out-of-gopath builds starting from go 1.11. All dependencies are stated
idiomatically using the go module framework, and are automatically
collected by the go toolchain in the command stated in the README:
go get github.com/rditech/rdi-live/tools/...
Upon successful completion of the above command, all of the tool binaries,
including rdi-live, are placed in your $GOPATH/bin. If you need to modify
the code, I recommend working with the repo outside of your gopath, and
building the binaries with
go install ./tools/...
when in the root repo directory. All of this is completely go-idiomatic,
and extra documentation of dependencies would only be superfluous. You can,
however, take a look at the go.mod
https://github.com/rditech/rdi-live/blob/master/go.mod file to see
particular dependencies in the go modules format. A word to the wise: be
careful updating go.mod, since breaking changes can occur.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rditech/rdi-live/issues/6?email_source=notifications&email_token=ANXAJUPRG37H2VIT3FAUM5TRDYDHFA5CNFSM4KV5NXI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMKW4LI#issuecomment-588607021,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANXAJUMNJUWM64IOOXYTVRLRDYDHFANCNFSM4KV5NXIQ
.


Create FlaggedType as a reusable replacement for StorageType and ArmType

Create new Type implementation FlaggedType that can be a wrapper around any existing Type.

Supports multiple flags
Adding a flag to an existing flagged type does not nest
Removing the last flag from a wrapped type unwraps

1st of 3 related PRs.

Coverage increased (+3.05%) to 73.81% when pulling 2f0d3146f8c128dbd108aa93022564ce328580f4 on feature/flagged-types into b3806d11fea96f424b751070c9f0218ca480c06e on master.


1533 Toggling Safes on Organization page

Fixes #1533
Go to Safe with multiple sub Safes. Then toggle favorites and navigate away and back (or refresh) should now save all changes properly

@Da-Colon can you check the video I just sent here -
I went through your flow and its still not 100%

@tomstuart123 your video demonstrates a different issue. This PR addresses the issue where you were unable to favorite/unfavorite Safes consistently from a Safe's hierarchy page.

are I misunderstood the test flow above and what @Da-Colon meant by 'toggle'. Let me retry

@tomstuart123 no worries, @Da-Colon probably should have used the words "Hierarchy page" somewhere in this PR!

Right after doing the test flow correctly both in production and on this PR, I understand it now. It all worked well in the new PR so will approve

Approved.
Re; my seperate issue in the video above, I was sadly able to replicate this issue also in the PR 1909 (the fix for 1515 issue)
Recommend we create a new issue for this.

Recommend we create a new issue for this.

@tomstuart123 please do!

@tomstuart123 sorry was trying to retrain my brain on new copy ha.


Android Stripe React Native Init Payment Sheet Error,  React Native Stripe Version 0.37.0

could not invoke stripe sdk init payment
Didn't find class "com.stripe.android.paymentsheet.PaymentSheet$GooglePayConfiguration$ButtonType
When I used it with IOS, it worked fine. But when worked with Android it gave me the above error. I didn't want to work with Google Pay. but seems it automatically uses Google Pay for payment intent which I created for Cards.
Here is my stripe provider.
<StripeProvider       publishableKey={stripe_public_key}       merchantIdentifier={stripe_merchant_identifier}     > .... </StripeProvider>
and I initiated the payment sheet this way.
const paymentIntentResponse = await paymentIntentRequest(data);     if (paymentIntentResponse) {       const { error } = await initPaymentSheet({         merchantDisplayName: "example",         customerId: paymentIntentResponse?.data?.customer,         customerEphemeralKeySecret: paymentIntentResponse?.data?.ephemeralKey,         paymentIntentClientSecret: paymentIntentResponse?.data?.paymentIntent,       });       if (error) {         showErrorToast(error?.message);       }     }
Payment Intent also fine and all the relevant data are coming. But only in Android, it gives above error. I tried to set null to googlePay as well. but no success.
React Native Version: 0.72.8
React Native Stripe: 0.37.0

Are you using Expo? I can't reproduce this error myself

No, I'm not using expo.

Previously I had several build issues. Those were from R8 issues related to transforming when dexing.
I added below code snippets to my android -> app -> build.gradle  and it resolved.
implementation('com.stripe:stripe-android') {
version {
strictly '20.28.0' // when coming to 20.34.0 same build issues happens again
}
}
implementation('com.stripe:financial-connections') {
    version {
        strictly '20.28.0'
    }
}

but the above-mentioned issue still persists.

that would probably cause this bug. If you manually override the installed versions, that can break our dependencies

that would probably cause this bug. If you manually override the installed versions, that can break our dependencies

I had to do that because I had a lot of build issues when I built the app. After overriding, I successfully built the app.

I have a solution. It's not proper, but downgrading to @stripe/stripe-react-native to 0.28.0 worked successfully for both IOS and Android. after installing, don't forget to pod update.

This issue has been fixed using an older version


Type variable incorrect inferred as "{}

TypeScript Version:  2.6.0-dev.201xxxxx
Code
// A *self-contained* demonstration of the problem follows...
// Test this by running `tsc` on the command-line, rather than through another build tool such as Gulp, Webpack, etc.

Expected behavior:
Actual behavior:

Closing as duplicate of #19382.


Moving location header out of data div

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes #11741

Description

Per issue description, Problem: Header for geo-location data is presently being overwritten with js data insertion inside the div.
Solution: Moved header for display of geo-location data above and outside of the div for data.  Now the header should remain intact after data is loaded.

LGTM :+1:
Thanks for contributing :tada:


KafkaAttribute.MaxMessageBytes is never used in KafkaProducerFactory

It is currently impossible to produce messages over 1MB because KafkaAttribute.MaxMessageBytes is never used in KafkaProducerFactory.  MaxMessageBytes is also not exposed via KafkaOptions, so I can't set it in host.json either.
Additionally, MaxMessageBytes can't be set directly as an attribute:
                       [Kafka(@"%Merge_Broker%",
                               @"%Merge_TopicName%",
                               MaxMessageBytes = 999999999,  // <-------
                               Protocol = BrokerProtocol.Plaintext,
                               AuthenticationMode = BrokerAuthenticationMode.NotSet,
                               SslCaLocation = "%Merge_SslCaLocation%")] IAsyncCollector<KafkaEventData<string>> collector,

Because int? is not a valid attribute type in C#.

Thank you, @shaunco to notice it.
I check the code and I confirm that the value is not used. I'll find a time to implement it.

This is addressed in #179, and all the other nullable attribute parameters are fixed in #175


[Bug]: Uploading file that does not exist does not produce any error

Bug expectation
I expected an error but did not get one. I did waste half a day on it (I am not mad, it is only really hard to tell if something went wrong...)
Bug behavior

[ ] Flaky
[ ] PDF

Minimal, reproducible example
import puppeteer from 'puppeteer';

(async () => {
  const browser = await puppeteer.launch();
  const page = await browser.newPage();
  await page.setContent('<input type="file">')
  const inputHandle = await page.$('input[type=file]');
  await inputHandle.uploadFile('non-existing-src.jpg');
})();

Error string
no error
Puppeteer configuration
I am using `jest-pupeteer` with `.jest-puppeteerrc.json` file:

{
  "launch": {
    "headless": true,
    "devtools": true,
    "exitOnPageError": false
  }
}

Puppeteer version
19.10.0
Node version
16.13.2
Package manager
npm
Package manager version
9.1.2
Operating system
Windows

Sorry about this. We used to validate, but now we don't because the file comes from your remote environment which is not possible to validate. This sadly implies if your remote is your local, then we still can't validate because we can't detect that difference.
Under the hood, the input element doesn't validate what gets set there, it's assumed that you validated beforehand, so it's best to somehow validate the file before using your own framework (if it's local, then just use fs.existsSync) and then continuing on from there.

How about an update to the docs of uploadFile? Maybe a hint that the file is not validated could be helpful?


Java 11 compatibilty

Jus to inform you, some options you used for Java8 don't exist anymore in Java11.
And the version of the apache felix framework you are currently using also generates errors with java11. These erros were fixed in the 6.0.2version.
(This was tested   when installing jira with your code on a Ubuntu18.04 Server where by default you have Java10. And it seems better to upgrade Java to 11 than to downgrade to 8.)

We use Java 8 during Ubuntu 18.04 test
https://github.com/alvistack/ansible-role-jira/blob/master/molecule/ubuntu-18.04/playbook.yml
And Java 11 is not yet supported by JIRA

It is now supported by Jira, because when I had neither 8 or 11, it was proposing both. It just requests some changes but it works just fine.
But yes I saw that, and it worked really well with Java8.

Should not yet support Java 11
https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html
Should be after JIRA 8.1, after Q1
https://developer.atlassian.com/blog/2019/01/december-update-upcoming-breaking-changes-across-server-products/

P.S. I will usually upgrade all my Atlassian related role Java support, after ALL of them already support Java 11, else usually VERY buggy :-(

Yes of course, I understand. But seems to work with your version of Jira under Java11. And I only wanted to give you the info. If you want to make it Java 11 compatible, you don't have a lot of changes to do :)
But that's true that it's not listed in the supported version on their website.

Fixed by https://github.com/alvistack/ansible-role-jira/commit/86df9c7f28511fe7af05da9681726b8e23b4395e


Support Amazon Security Lake data events in S3 source with SQS queue

Is your feature request related to a problem? Please describe.
Amazon Security Lake provides events over Amazon EventBridge. The format is different from S3 directly to SQS or via SNS as shown in this sample configuration.
Describe the solution you'd like
Automatically detect events from Amazon Security Lake and read the S3 object accordingly.
Additional context
See #2604 for another feature that was able to parse SQS messages which came via SNS.

It appears that the solution for this may also work for general Amazon EventBridge events. However, I see at least one clear difference. With Amazon Security Lake, the notifications are for create object only (which is what Data Prepper wants). But, with Event Bridge, there is a detail-type which indicates if it was created. See the Event Bridge sample structure.


Update module.pp to match current version

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

Thanks! I've fixed the lint issues and squashed the PR.


heatmap dissapear after zoom in

Describe the bug
It seems to work perfectly, but when you perform a zoom in with the mouse wheel, the red "clouds" start to vanish.  Is it the desired behaviour or is it a bug?
How can I make the colored areas stay while zooming? IMHO they should increase their area, instead of decreasing the area and color until they disappear.
To Reproduce
I've seen this example of Heat Maps https://openlayers.org/en/latest/examples/heatmap-earthquakes.html
Go to a red "cloud", and zoom in
Expected behavior
The red "cloud" should increase while zooming in, occupying the same area that initially was covering

I misunderstood the heatmap class.
It's just clustering closer points, and zooming in you can get a fine grained detail. It's working perfectly.
For my purpose, there is another example that fits better: https://openlayers.org/en/latest/examples/semi-transparent-layer.html


use merlin compat for imports of gpu specific packages

This PR enables a user to run our GPU docker container without GPUs and successfully be able to run all tests. Previously we had try catches in a few places in the code for importing GPU specific packages. This PR remediates those try catches because in an environment where you have the package but no GPU you end up getting ccuda.pyx init failure. This is because, the package (i.e. cudf, dask_cudf, rmm) do exist but when they try to access information about GPUs it fails and throws an error something like:
collecting ... Traceback (most recent call last):
  File "cuda/_cuda/ccuda.pyx", line 3671, in cuda._cuda.ccuda._cuInit
  File "cuda/_cuda/ccuda.pyx", line 435, in cuda._cuda.ccuda.cuPythonInit
RuntimeError: Failed to dlopen libcuda.so
Exception ignored in: 'cuda._lib.ccudart.utils.cudaPythonGlobal.lazyInitGlobal'
Traceback (most recent call last):
  File "cuda/_cuda/ccuda.pyx", line 3671, in cuda._cuda.ccuda._cuInit
  File "cuda/_cuda/ccuda.pyx", line 435, in cuda._cuda.ccuda.cuPythonInit
RuntimeError: Failed to dlopen libcuda.so
Fatal Python error: Segmentation fault

This PR leverages the compat file, and makes it the single point of import for the main packages (cudf, cupy) and it adds a security around it that ensures you can only import those packages if GPUs are detected. So if you find yourself in a scenario where the package is installed but no GPUs are detected you can, now, still safely use the core package. Therefore, we can now run our containers with and without the --gpus=all flag in docker. This was a customer ask and it helps developers when trying to test cpu only environment on a resource that has GPUs.
This PR works in conjunction with https://github.com/NVIDIA-Merlin/core/pull/261

The remaining test failure here is addressed by NVIDIA-Merlin/core#276, so waiting on that PR to go through in order to merge this one


Remove Windows related things

Put references for restoring them if it needs:

https://github.com/himkt/dotfiles/pull/228
https://github.com/himkt/dotfiles/pull/230

Done


Admin metadata editing of types

Context & motivation
On the Grapher side, we would like to make use of ordinal type information, especially in a few places such as scatterplot legend labels. (e.g. income groups)
But we have a chicken and egg problem; we don't have this data to use yet, so it's not helpful to support using it in Grapher.
Proposal
Enable setting ordinal type information on an indicator in the admin, so that someone doing a chart can go and fix the ordering of an indicator legend this way.
Mojmir notes
I'm sceptical of the value of editing types in admin. This only makes sense for ordinal type now. I don't think this should be important because:

No one has edited any metadata yet
Ordinal type is only relevant to a couple of indicators (two as of now - income and age groups)
Implementing this in admin could be non-trivial (fetching all values from JSON file and displaying them as sortable component)

Thanks for your thoughts @Marigold!
I totally understand that it can feel not valuable to invest in something people aren't using. The motivation for this was not about where we are not, but we're we're trying to take Grapher's type model. Based on your feedback though, I agree we can take it off the table for this cycle and discuss it with Sophia at the offsite instead.
Separately, on admin editing, I bet that the complexity of the mapping between indicator + chart to data page is a big barrier to people editing in the admin. It could be cool to do an experiment where we help an author upgrade an chart/indicator into a data page, purely using the admin, then we see if there are a few simple links we could add that make that easier.

We can park this one for now, the type system is not the main focus in Grapher-land in the near future.


Fix cursor on double tap

Feature Description

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria
QA Instructions

Duplicate of #386?

Closing as no longer needed


Migrate Bartholomew documentation

close #183
ref https://github.com/fermyon/bartholomew/pull/148
This commit migrates the Bartholomew documentation from its standalone website to the Fermyon Developer Home website.
I updated:

the navigation bar to include Bartholomew
the main and sidebar templates for Bartholomew
the search functionality to include Bartholomew docs

Signed-off-by: Radu Matei<EMAIL_ADDRESS>

Testing this locally, the menus, search and docs pages are all working great - thanks @radu-matei!
I noticed some urls pointing at bartholomew.fermyon.dev, added an update to make those relative.
The developer homepage layout was too narrow as well, so I tweaked that.

We should also probably set up redirects on the bartholomew.fermyon.dev in the same manner as we have done for spin.

Fixed the broken links and added the missing images from the Bartholomew static assets.
Looking at redirects now.

@radu-matei this looks ready to go, there are two conflicts that need resolution
A fresh run of npm run spin and npm run styles should overwrite those to move forward.

Thanks so much for this @radu-matei
Thanks @flynnduism for your input also
Thanks @karthik2804 for your help tonight getting this rebased and updating some extras. Really appreciate it.
Please see new PR which replaces this one (a few extras in there)
https://github.com/fermyon/developer/pull/267


Genesys: missing images from "ship" section of character sheet CSS.

Lines 1676 and 1686, I believe.
sheet-ship-char-thre-bg
sheet-ship-char-thre-bg-speed
Sheet looks like this: https://app.roll20.net/forum/post/8467932/genesys-sheet-ship-display-issue

This issue is fixed now.


upgrade PF core package

Upgrade PF Core Package to match Control plane UI

@christiemolloy done local check for this.
CC @jschuler

Closing as stale. Update were done already by @jschuler


Upload failed on AWS S3 with "File was not opened in write mode"

Hi guys,
I'm running python 3.6.x with django 1.11.11 on gunicorn 19.7.1.
When I upload a file, I get the following error:
"File was not opened in write mode."
Sentry points me to this line:
    self.file.open(mode='ab')  # mode = append+binary
    # We can use .read() safely because chunk is already in memory
    self.file.write(chunk.read())

I already checked this issue but it was related to an old version of django.
Any ideas?
Thanks
Ron
PS: Maybe this is related to my storage of media files on AWS S3? Chunked parts are created but have size zero.

@GitRon Did you find a solution?

@sighmon I branched out and this is my solution: https://github.com/GitRon/django-chunked-upload

nice fix

@birkanozer Unfortunately we are stuck here...

Unfortunately we are stuck here...

@GitRon Does that mean you weren't able to get a full working solution? I've seen some other errors downstream as well, so curious if you ended up getting it fully working.

Unfortunately we are stuck here...

@GitRon Does that mean you weren't able to get a full working solution? I've seen some other errors downstream as well, so curious if you ended up getting it fully working.

I wanted to add the general fix for using a temporary storage. But the guy who took over the project started changing way more things. Variable names etc. IMHO this is too big for now and will cause loads of problems for people using the package. We somehow got lost along the way and since some time I haven't heard or (I have to admit) said anything on this topic.
My dream scenario would be that we start where the old maintainer left of, merge in my fix, maybe I have to update the docs a bit because the fix is just also a fix for the cloud. But it can be used in other circumstances as well.
When this is one the road, we could discuss in an issue if renaming variables etc is a proper way to go.

I wanted to add the general fix for using a temporary storage. But the guy who took over the project started changing way more things. Variable names etc. IMHO this is too big for now and will cause loads of problems for people using the package. We somehow got lost along the way and since some time I haven't heard or (I have to admit) said anything on this topic.
My dream scenario would be that we start where the old maintainer left of, merge in my fix, maybe I have to update the docs a bit because the fix is just also a fix for the cloud. But it can be used in other circumstances as well.
When this is one the road, we could discuss in an issue if renaming variables etc is a proper way to go.


use Stream Invalid argument(s): Must not be null

When the exception was thrown, this was the stack:
#0      ArgumentError.checkNotNull (dart:core/errors.dart:235:20)
#1      QueryAdapter.queryStream (package:floor/src/adapter/query_adapter.dart:64:42)
#2      _$PersonDao.findAllPersonCount (package:simple_flutter/db/AppDatabase.g.dart:152:26)
#3      _ButtonState.build (package:simple_flutter/widget/button_widget.dart:33:37)
#4      StatefulElement.build (package:flutter/src/widgets/framework.dart:5080:27)
#5      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4968:15)
#6      StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:5133:11)
#7      Element.rebuild (package:flutter/src/widgets/framework.dart:4690:5)
#8      ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:4950:5)
#9      StatefulElement._firstBuild (package:flutter/src/widgets/framework.dart:5124:11)
#10     ComponentElement.mount (package:flutter/src/widgets/framework.dart:4944:5)
...

NO use  _queryAdapter.query() is not error ,but use _queryAdapter.queryStream() will happen error

Why did not a changeListener be generated

I found that the changeListener parameter was not used when creating a QueryAdapter
class _$PersonDao extends PersonDao {   _$PersonDao(     this.database,     this.changeListener,   )   : _queryAdapter = QueryAdapter(database),

Since the QueryAdapter was designed to only fetch data from the database, it doesn't make sense to apply a changeListener for this adapter type. However, there is a pull request (#733 ) that parses the Query request and notifies the changeListener if it's a DELETE, UPDATE, or INSERT operation.


chore: add Node.js 10

Changes proposed in this pull request:

add Node.js for testing builds on PRs and commits

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

Thanks for your PR! We are now building on node 10 👍


feat: add kusion server, engine api and refactor preview logic

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., design docs, usage docs, etc.:

Sample usage(requires workspace config to be present currently, should automatically query in future versions):
http://localhost:8888/api/v1/project/simple-service-4/stack/dev/preview?path=/Users/forest/playground/simple-service-4&isKCLPackage=true&detail=true&output=json

http://localhost:8888/api/v1/project/simple-service-4/stack/dev/preview?path=/Users/forest/playground/simple-service-4&isKCLPackage=true