Fixed #18307 -- Fixed formset add_fields().

Fixes https://code.djangoproject.com/ticket/34349#ticket
Description
Formsets' add_fields() method fails in some circumstances if the argument index is None.
When a FormSet has the attributes self.can_delete == True and self.can_delete_extra == False, calling the add_fields() method on that FormSet fails if the argument index is None. This occurs for example when calling FormSet.empty_form(). The result is that the method raises the exception TypeError: '<' not supported between instances of 'NoneType' and 'int'.
MyFormSet = forms.formset_factory(
    form=MyForm,
    can_delete=True,
    can_delete_extra=False,
)
my_formset = MyFormSet(
    initial=None,
)
print(my_formset.empty_form)

Replaced by https://github.com/django/django/pull/16569


Highlight Python API in GS/tips/tutorials/demos/manuals

Improve documentation
Highlight the new Python API in the documentation. It could be interesting to add a Python API version for each code if possible.
Here is how we contribute to Taipy Doc.
User Feedback
A Discord user reported their learning journey on TGB:
He wanted to create a dialog using the tgb so he stumbled on this page:
https://docs.taipy.io/en/release-1.1/manuals/gui/viselements/dialog/
This page does not contain the tgb syntax for dialog so he looked for this page:
https://docs.taipy.io/en/release-3.0/manuals/reference/taipy.gui.builder.dialog/
This page either does not contain the information
All in all, it took them hours to figure out how to create a dialog using the tgb by experimenting.
Expected change
The discord user suggested that all visual elements have a link towards the tgb doc page. And that the tgb doc page contains a list of syntaxes for all visual elements
I would go further by simply adding the tgb syntax somewhere on all the visual elements pages.

Here is a list of functioning tgb code as reference:
from taipy import Gui
import taipy.gui.builder as tgb

# slider_value needs to be initialized first
slider_value = 5

with tgb.Page() as page:
    tgb.slider('{slider_value}', min=0, max=10)
    tgb.text('slider_value: {slider_value}')

if __name__ == '__main__':
    Gui(page).run(use_reloader=True)

from taipy import Gui
import taipy.gui.builder as tgb

with tgb.Page() as page:
    tgb.status('Any text will be displayed this way')
    tgb.status('')
    # some keywords will change the color of your status
    tgb.status('warning')
    tgb.status('success')
    tgb.status('secondary')

if __name__ == '__main__':
    Gui(page).run(use_reloader=True)

from taipy import Gui
import taipy.gui.builder as tgb

choice = 'No'

def toggle_func(state, var_name, value):
    print(f'state.choice: {state.choice}')
    print(f'var_name: {var_name}')
    print(f'value: {value}')

with tgb.Page() as page:
    tgb.text('Current choice: {choice}')
    tgb.toggle(value='{choice}', lov=['Yes', 'No'], on_change=toggle_func)

if __name__ == '__main__':
    Gui(page).run(use_reloader=True)

from taipy import Gui
import taipy.gui.builder as tgb

# the variable used to open/close the dialog
dialog_status = False

def open_dialog(state):
    state.dialog_status = not state.dialog_status

with tgb.Page() as dialog_content:
    tgb.html('p', 'Inside the dialog')

with tgb.Page() as page:
    tgb.button("Open dialog", on_action=open_dialog)
    tgb.dialog('{dialog_status}', on_action=open_dialog, partial='{dialog_partial}')

if __name__ == "__main__":
    gui = Gui(page=page)
    dialog_partial = gui.add_partial(dialog_content)
    gui.run(use_reloader=True)

from taipy import Gui
import taipy.gui.builder as tgb

# The variable used to open/close the expandable
expand_status = False

with tgb.Page() as partial_content:
    tgb.html('p', 'Inside the expandable')

def change_status(state):
    print(state.expand_status)
    state.expand_status = not state.expand_status

with tgb.Page() as page:
    #  You can click both the button or the expandable to open it
    tgb.button('Open Expandable', on_action=change_status)
    tgb.expandable(title='Expandable title', partial='{expandable_content}', expanded='{expand_status}', on_action=change_status)

if __name__ == '__main__':
    gui = Gui(page)
    expandable_content = gui.add_partial(partial_content)
    gui.run(use_reloader=True)

from taipy import Gui
import taipy.gui.builder as tgb

# input_value needs to be initialized first
input_value = '...'

with tgb.Page() as page:
    tgb.input('{input_value}')
    tgb.text('input_value: {input_value}')

if __name__ == '__main__':
    Gui(page).run(use_reloader=True)

from taipy import Gui
import taipy.gui.builder as tgb

choice = 'B'  # the variable displayed by the selector

with tgb.Page() as page:
    tgb.selector(value='{choice}', lov=['A', 'B', 'C'], dropdown=True)
    tgb.html('p', 'Not displayed alone:')
    tgb.text('{choice}')
    tgb.html('p', 'Displayed when added some text:')
    tgb.text('You selected: {choice}')

if __name__ == '__main__':
    Gui(page).run(use_reloader=True)

from taipy import Gui
import taipy.gui.builder as tgb

status = {"status": "error", "message": "This is an error message"}

with tgb.Page() as page:
    tgb.status("{status}")

if __name__ == "__main__":
    Gui(page).run(use_reloader=True)

@FlorianJacta, we improved the documentation on manuals.
Is it enough, or should we add an entry to the knowledge base page?

I asked feedback to the user who reported this issue on Discord, waiting for answer:


NotADirectoryError on Windows

The provided example for fine-tuning a BERT Model results in this error:
2024-02-26 12:47:02,763 - DefaultPrinterCallback - INFO - Saving checkpoint in checkpoints\checkpoint_001_26-02-2024_12:47
Traceback (most recent call last): history = trainer.train()
NotADirectoryError: [WinError 267] The directory name is invalid: 'checkpoints\checkpoint_001_26-02-2024_12:47'

Hi, which versions of medkit are you using? Version 0.13.1 features a fix for Windows paths.

Hello, I am using 0.13.0. I will update it right now. Thank you for your
prompt response.
On Mon, Feb 26, 2024 at 1:21 PM Ghislain Vaillant @.***>
wrote:

Hi, which versions of medkit are you using? Version 0.13.1 features a fix
for Windows paths.
—
Reply to this email directly, view it on GitHub
https://github.com/medkit-lib/medkit/issues/27#issuecomment-1963905520,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVA4APT734JAGROPHWFVD6LYVRV4FAVCNFSM6AAAAABDZ7INYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRTHEYDKNJSGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


[PE-D][Tester C] UI does not update for view after deleting tags [UI][Live-updates]

Not sure if this is intended but understood that the backend storage deleted the tag. The view does not update , not sure if this is intended or not. This is also not mentioned in the UG

Labels: severity.VeryLow type.DocumentationBug
original: sk2001git/ped#8

mentioned in known issues in ug


Message "EasyCLA is not enabled for this project.." is shown on Corporate Console even though there is a CLA group present for the project

I am receiving following error on Staging environment on Corporate Console:

This is for project vinods3foundation_child1 under foundation vinods3foundation.
I have already created cla group by name vinods3foundation_clagrp1 with  project vinods3foundation_child1 selected,.
GraphQL API with following input
{
"operationName": "claGroupsForProjectListQuery",
"variables": {
"organizationId": "0012M00002MnADGQA3",
"projectId": "a097c000007oC8kAAE",
"organizationInternalId": "d6367896-27f0-4c06-9f9a-3420846e0ec9"
},
"query": "query claGroupsForProjectListQuery($organizationId: String!, $projectId: String!, $organizationInternalId: String) {\n  claGroupsForProjectList(organizationId: $organizationId, projectId: $projectId, organizationInternalId: $organizationInternalId) {\n    signedClaList {\n      cclaUrl\n      projectLogo\n      projectName\n      projectSfid\n      projectType\n      signatoryName\n      signedOn\n      claGroupName\n      subProjects\n      __typename\n    }\n    unsignedProjectList {\n      canSign\n      claGroupId\n      claGroupName\n      projectName\n      projectSfid\n      cclaEnabled\n      iclaEnabled\n      subProjects\n      __typename\n    }\n    __typename\n  }\n}\n"
}
is returning
{"data":{"claGroupsForProjectList":null}}
I called following CLA API from postman
https://api-gw.staging.platform.linuxfoundation.org/cla-service/v4/company/d6367896-27f0-4c06-9f9a[…]e0ec9/project/097c000007oC8kAAE/active-cla-list
and it returned following output:
{
"Code": "403",
"Message": "EasyCLA - 403 Forbidden - CLA Group not found with given project SFID: 097c000007oC8kAAE - error: [GET /projects/{projectId}][404] getProjectNotFound ",
"x-request-id": "0b5765c0-6a7f-11eb-a587-9d3f3a63a2ec"
}
This issue blocks the signing of a CCLA.
The CLA group is indeed present as the API https://api-gw.staging.platform.linuxfoundation.org/cla-service/v4/foundation/a097c000007oC8kAAE/cla-groups
returns the following output:
{
"list": [
{
"ccla_enabled": true,
"ccla_pdf_url": "https://cla-signature-files-staging.s3.amazonaws.com/contract-group/8daf81df-a7ae-45b3-809e-ef63db3a1ad9/template/ccla-2021-02-09T02-20-26Z.pdf",
"ccla_requires_icla": true,
"cla_group_description": "",
"cla_group_id": "8daf81df-a7ae-45b3-809e-ef63db3a1ad9",
"cla_group_name": "vinods3foundation_clagrp1",
"foundationLevelCLA": false,
"foundation_name": "vinods3foundation",
"foundation_sfid": "a097c000007oC8fAAE",
"icla_enabled": true,
"icla_pdf_url": "https://cla-signature-files-staging.s3.amazonaws.com/contract-group/8daf81df-a7ae-45b3-809e-ef63db3a1ad9/template/icla-2021-02-09T02-20-26Z.pdf",
"project_list": [
{
"project_name": "vinods3foundation_child1",
"project_sfid": "a097c000007oC8kAAE",
"repositories_count": 1
}
],
"repositories_count": 1,
"root_project_repositories_count": 1,
"setup_completion_pct": 100,
"total_signatures": 0
}
]
}

Closed this ticket as created LFX-3091 as fix is coming from Corporate Console side for this issue.


TQL syntax highlighting in docs site

This PR adds support for syntax highlighting of TQL code blocks in the docs site.
To review, add a TQL code block in any docs or blog page, and run docusaurus.
Missing feature: copy to clipboard button, see upstream issue - https://github.com/rehype-pretty/rehype-pretty-code/issues/235.
Closes https://github.com/tenzir/issues/issues/2035.

Let's merge it and then iterate on it, @jachris. Better to get this in than to leave it open.
One follow-up we should resolve sooner rather than later is filling in missing tql tags:
rg --multiline '```\n\/\/ tql2'


🐛 [Design Fix]: The line under the text hide the text

Descrcibe the bug?
The underlined line hides the text  as you can see it in the attached screen shot

Steps to reproduce the bug?
Go on to the home page of the reactpaly.io and scroll down to the What our community says section
Expected behavior
The underline should be behind the text as shown in the attached screen shot.

Desktop (Please provide your system information)
OS:Windows
browser: Chrome
Mobile (Please provide your device information)
No response
Screenshot / Screenshare
Current behavior

Expected behavior

Relevant log output
No response
Code of Conduct

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

If you think this issue should be worked on then I would like to work on it as I have already implemented the expected behavior described above :)


Improve logging in InternalCommandPortListeningCheck (#2984)

Related to:
Mock Server doesn't start after updating to 5.11.0 #2984
When /bin/sh -c $command exists with code 126 (Command invoked cannot execute), the error output is not logged.
An example, /bin/sh is not available starting certain image version:
OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "exec: "/bin/sh": stat /bin/sh: no such file or directory": unknown
Such error output could be logged to assist troubleshooting. It shouldn't bloat logs since such outcome is rare.

Hey @vcvitaly,
Sorry for overlooking this PR. Could you please resolve the conflict? It looks like you have "enable edits by maintainers" disabled, otherwise I'd do it myself :) Thanks!

Hey @vcvitaly,
Sorry for overlooking this PR. Could you please resolve the conflict? It looks like you have "enable edits by maintainers" disabled, otherwise I'd do it myself :) Thanks!

@bsideup Thanks for the review! I merged the master, it should be good.

@vcvitaly thanks! Merged 🎉


[ENHANCEMENT] Add user to choose in toolbar auto/light/dark

Now i have set:
CMS_COLOR_SCHEME = "auto"

CMS_COLOR_SCHEME_TOGGLE = True

I'd like to give the logged in user the choice to set it on auto or fixed dark/light mode.
Now with the TOGGLE setting to True it shows in toolbar options light/dark.
I would like to add auto to it.
Steps to reproduce
Django==3.2.18
Django-cms==3.11.3
Screenshots

Do you want to help fix this issue?

[x] Yes, I want to help fix this issue and I will join #workgroup-pr-review on Slack to confirm with the community that a PR is welcome.
[ ] No, I only want to report the issue.

#7549 did add the auto option to the toggle. I am not sure whether it also covered fixing the color scheme with CMS_COLOR_SCHEME = "auto".

Fixed with #7556 and #7549


Remix 2.4.1 Vite, virtual:remix/server-build, when importing cjs module,  ReferenceError: exports is not defined

Reproduction
reproduction is made using
npx create-remix@latest --template remix-run/remix/templates/unstable-vite-express
https://stackblitz.com/~/github.com/tomer-yechiel/remix-vite-spectrum
production build works
System Info
N/A

Used Package Manager
npm
Expected Behavior
should work
Actual Behavior
throws error

I'm trying to track down an error of ReferenceError: exports is not defined myself in an app I'm testing with the Vite support, no luck so far. I'm slowly going through the app removing parts until I can find the culprit.

OK I found my issue, I had a stray .babelrc.json file in my root, once this was removed all seems to be working now

This is an issue with React Spectrum + Vite, not specifically Remix related.
I was able to fix the provided repro by updating the ssr.noExternal array in the Vite config to be a list of package names which I got from the React Spectrum docs on Next.js (https://react-spectrum.adobe.com/react-spectrum/ssr.html#nextjs) thanks to this comment: https://github.com/adobe/react-spectrum/issues/5401#issuecomment-1815445715. I'm not sure why but like others in that thread, I couldn't get it to work with regular expressions.
import { unstable_vitePlugin as remix } from "@remix-run/dev";
import { defineConfig } from "vite";
import tsconfigPaths from "vite-tsconfig-paths";

export default defineConfig({
  ssr: {
    noExternal: [
      "@adobe/react-spectrum",
      "@react-spectrum/actionbar",
      "@react-spectrum/actiongroup",
      "@react-spectrum/avatar",
      "@react-spectrum/badge",
      "@react-spectrum/breadcrumbs",
      "@react-spectrum/button",
      "@react-spectrum/buttongroup",
      "@react-spectrum/calendar",
      "@react-spectrum/checkbox",
      "@react-spectrum/combobox",
      "@react-spectrum/contextualhelp",
      "@react-spectrum/datepicker",
      "@react-spectrum/dialog",
      "@react-spectrum/divider",
      "@react-spectrum/dnd",
      "@react-spectrum/form",
      "@react-spectrum/icon",
      "@react-spectrum/illustratedmessage",
      "@react-spectrum/inlinealert",
      "@react-spectrum/image",
      "@react-spectrum/label",
      "@react-spectrum/labeledvalue",
      "@react-spectrum/layout",
      "@react-spectrum/link",
      "@react-spectrum/list",
      "@react-spectrum/listbox",
      "@react-spectrum/menu",
      "@react-spectrum/meter",
      "@react-spectrum/numberfield",
      "@react-spectrum/overlays",
      "@react-spectrum/picker",
      "@react-spectrum/progress",
      "@react-spectrum/provider",
      "@react-spectrum/radio",
      "@react-spectrum/slider",
      "@react-spectrum/searchfield",
      "@react-spectrum/statuslight",
      "@react-spectrum/switch",
      "@react-spectrum/table",
      "@react-spectrum/tabs",
      "@react-spectrum/tag",
      "@react-spectrum/text",
      "@react-spectrum/textfield",
      "@react-spectrum/theme-dark",
      "@react-spectrum/theme-default",
      "@react-spectrum/theme-light",
      "@react-spectrum/tooltip",
      "@react-spectrum/view",
      "@react-spectrum/well",
      "@spectrum-icons/illustrations",
      "@spectrum-icons/ui",
      "@spectrum-icons/workflow",
    ],
  },
  plugins: [remix(), tsconfigPaths()],
});


Overload comparison operators for LazyUUIDTaskSet?

https://github.com/vit-project/vit/issues/300 exposes a limitation in LazyUUIDTaskSet, namely, that it cannot be used in a standard Python comparison, because of a type mismatch.
It seems reasonable for tasklib to provide some overloaded comparison operators for LazyUUIDtTaskSet, which would do the required loading of the dependencies and convert them to a proper set, so that comparisons work natively.
Looks like it should be pretty straightforward: https://www.tutorialspoint.com/How-to-overload-Python-comparison-operators
Thoughts?

This bug was treated in the 2.4.0 release?

@mhalano No, this issue is still pending a fix :slightly_smiling_face: actually something I would consider a good first issue!
@thehunmonkgroup The proposal for making LazyUUIDTaskSet comparable with a regular set of UUIDs sounds good to me.

which would do the required loading of the dependencies, and convert them to a proper set
Unclear if you mean that the laziness would have to be dropped, because I suspect that does not have the be the case.

Unclear if you mean that the laziness would have to be dropped, because I suspect that does not have the be the case.

I don't think it would have to be dropped. If I understand the overloaded comparison operators correctly, the lazy UUIDs could be converting to a proper set in the overloaded method, so lazy UUIDs would only be converted to proper UUIDs when the set is part of a comparison.

lazy UUIDs would only be converted to proper UUIDs when the set is part of a comparison.

Correct, we're on the same page then. This can even just happen within the operator implementation internally, so no changes to the object itself are needed. Actually a lot of operators are overloaded, it's just that __gt__ and __lt__ are not among them.

@tbabej The PR made by @RonMcKay didn't close this issue?

Pretty sure this is done.


New issue | DECODE_PERCENTS  is not working on Azure devops agent Version 2.181.2

Having issue with YAML?
Please log an issue at Azure-Pipelines-YAML. Over there we discuss YAML templates, samples for Azure Pipelines, and designs for upcoming YAML features. Also a place for the community to share best practices, ideas, and so on. File suggestions and issues here if they're specific to YAML pipelines.
I am using the below yaml file.
trigger:

main

pool:
vmImage: 'ubuntu-latest'
variables:

name : system.debug
value : true
name : skipComponentGovernanceDetection
value: true
name: DECODE_PERCENTS
value: true

jobs:

job:
variables:

name: DECODE_PERCENTS
value: true

steps:

powershell: Write-Host '##vso[task.setvariable variable=test]a%AZP25'
displayName: 'Set Variable'

This will print the a% correctly as the value of test

powershell: 'Get-ChildItem env:'
displayName: 'printenv'

======================
When I am running on the Microsoft Hosted agents ( V2.181.2) system is not able to decode the value of the test. It's still printing as "a%AZP25" , Please finds the below screenshot for the same.
Agent details :

Variable output:

When I am using the self hosted agent V2.181.1 , system is displaying the value as ""
Self Hosted agent version :

Variable output:

Having issue with software on Hosted Agent?
Log an issue at Hosted Agent Image Repository. It contains the VM image used in the Azure Pipelines Hosted Agent Pool. If you're having Build/Release failures that seems like they are related to software installed on the Hosted Agent (e.g. the dotnet SDK is missing or the Azure SDK is not on the latest version) please log an issue there.
Agent Version and Platform
Version of your agent? 2.181.2
OS of the machine running the agent? OSX/Windows/Linux/... Windows
Azure DevOps Type and Version
dev.azure.com (formerly visualstudio.com) or on-premises TFS/Azure DevOps Server?
Dev.azure.com/kohithfs
What's not working?
Please include error messages and screenshots.

Variable  "DECODE_PERCENTS " is not working on Agent V2.181.2 whereas its working on V2.181.1

Tested on platforms :
vmImage:
                 'windows-latest'
                 'macOS-latest'
                 'ubuntu-latest'

Reference Links :
https://github.com/microsoft/azure-pipelines-agent/blob/master/docs/design/percentEncoding.md
https://github.com/Microsoft/azure-pipelines-agent/releases
https://github.com/microsoft/azure-pipelines-agent/tree/releases/2.181.2
Key URL : https://github.com/microsoft/azure-pipelines-agent/blob/master/src/Agent.Sdk/Knob/AgentKnobs.cs
https://github.com/microsoft/azure-pipelines-agent/commit/9852cea2ab09f1efbd514db7e0ed3a5b02cc2330#diff-e9f1aa1a3ae52b26e46536b534890cf3e4957c7008a05fd36c65e6de7b6afa8f

https://github.com/microsoft/azure-pipelines-agent/commit/6dd5c59e042b437f1d639aaaa84879cf82886385
https://github.com/microsoft/azure-pipelines-agent/issues

Hey @kohithms this change was applied in agent release 2.182.1, it looks like you're using version 2.181.2 in your example, so it shouldn't have the change yet

We have two different agent pools and the % encoding was fixed using the DECODE_PERCENTS:true successfully using 2.181.1.
We have updated one of our pools to 2.182.1 and now the build pipeline is encoding % incorrectly again.
It's around retrieving the SAS token for storage account, i'm observing %25253A in the response.

Hi @damccorm,
Thanks for confirming that but even on agent version 2.181.1 we are able to see the value as

Hey @kohithms I'm not able to reproduce this behavior. Here's an example pipeline - https://dev.azure.com/damccorm-repros/setVariable escaping/_build/results?buildId=1029&view=logs&j=011e1ec8-6569-5e69-4f06-baf193d1351e&t=486c0909-f67d-5748-80b3-bb1d531e7b43, driven off of this yaml file - https://dev.azure.com/damccorm-repros/_git/setVariable escaping?path=%2Fazure-pipelines.yml.
Would you mind attaching the yaml file you're using, as well as the full build logs?

Hello @damccorm ,
Thanks for sharing the sample pipeline. In the given pipeline agent is using 2.182.1 looks like the issue is addressed over there.

But in version 2.181.1 it's still reproducible.

Sample Pipeline:
https://dev.azure.com/KohithFS/test/_build/results?buildId=42017&view=logs&j=011e1ec8-6569-5e69-4f06-baf193d1351e&t=486c0909-f67d-5748-80b3-bb1d531e7b43

Hi @damccorm, have u gt a chance to view this?

Reproduced on the agent version: '2.195.2'


Documentation error?

It seems like "Accepted protocols are HTTP. Forwarding protocol is either match request or HTTPS." should be "Accepted protocols are HTTP. Forwarding protocol is either match request or HTTP."

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

ID: 42cb8651-4d1d-4031-ad64-93fc7a2c0c6c
Version Independent ID: d2f0f0f6-378b-d3e9-b5de-59ab8ac71c72
Content: Troubleshoot Azure Front Door configuration issues
Content Source: articles/frontdoor/front-door-troubleshoot-routing.md
Service: frontdoor
GitHub Login: @sharad4u
Microsoft Alias: sharadag

@OwenTN Thanks for the feedback. The doc has been updated to show the change.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


[FEA] Look into adding an AST Filter, turning on AST project by default, and partial AST projection???

Is your feature request related to a problem? Please describe.
Right now AST is really only used in joins. We added in an AST Project as a way to easily test AST versions of various expressions, but no one has really done any serious benchmark to find out how good it might be. Some recent experimental work has indicated that for some operations a filter that could do AST operations might be very highly performant compared to a non-AST version.  We should take the time to explore what cases the AST operations are better than non-AST operations, and which cases they are not. If we see some big gains we should work with CUDF to add in AST filter support, and either turn on AST Project in cases where it would be best, or possibly update tiered project so that it could select some tiers to be executed using AST and not others.

We can start by experimenting with AST project config turned on.

As a note on why this might be a big win. https://github.com/NVIDIA/spark-rapids/pull/11810 needed to do a special case where multiple logical OR operators needed to be nested together. Using AST sped up the processing of this significantly. The AST or processing dropped the end to end time almost as much as the multi-contains work did.
If this works out we could eventually rewrite the complex rlike expression into a set of contains with OR expressions, which then we could automatically combine the into a multi-contains and an ast OR for the results.  This would let us, in theory combine multiple complex rlike expressions or similar processing into a single multi-contains with some AST post processing.


Change Player Name

What problem is this solving
When looking at demos, sometimes on faceit people can have streamer mode on, or they change their steam name for a few matches for fun. Would be nice to be able to change that person's name in the overview so instead of the player being 'Pirojenka-' they can be labeled as 'Ax1le'.
Proposed solution
In the demo overview, right click on a player and hit 'Change Name' and change it to a new name and have it populate through the stats and the 2d viewer.
Describe alternatives you've considered
No response

I noticed you can right click on the player with the fake name and go to their profile and it shows their normal steam name. Maybe possible to just grab that as an option?

The next version will allow overriding players' nicknames from scoreboards or the players list through the right-click context menu.

Thank you!!


Quality control standard cannot be set in config.yaml

The option to set a standard as a quality control standard is not available in the config.yaml file ("set standards" section of the file). This is a needed option and also needed to harmonise the stand-alone use of piccr with the use from Cpt.-Picarr; see also EarthSystemDiagnostics/cpt-picarr#47.

Closing this issue since it is resolved by EarthSystemDiagnostics/piccr#30.


Repository isn't injected into resolver

I learnt of this library from a discussion in routing controller. I've been testing the typeorm sample.
When I made a query
{
   recipe(id: 2) {
       title
   }
}

I got this error "message": "Cannot read property 'findOneById' of undefined".
So obviously the repository isn't injected into the resolver. What is wrong with the sample below?
import {Args, ArgsType, Field, ID, Query, Resolver} from "type-graphql";
import {Recipe} from "../entity/Recipe";
import {Repository} from "typeorm";
import {OrmRepository} from "typeorm-typedi-extensions";

@ArgsType()
class FindRecipeArgs {
    @Field(type => ID)
    id: number;
}

@Resolver(objectType => Recipe)
export class RecipeResolver {
    public constructor(
        @OrmRepository(Recipe) private readonly recipeRepository: Repository<Recipe>,
    ){}
    @Query(returnType => Recipe, { nullable: true })
    async recipe(@Args() { id }: FindRecipeArgs): Promise<Recipe | undefined> {
        return this.recipeRepository.findOneById(id);
    }

    @Query(() => Recipe, { array: true })
    recipes(): Promise<Array<Recipe>> {
        return this.recipeRepository.find();
    }

}

Library version:
    "type-graphql": "^0.8.0",
    "typedi": "^0.7.1",
    "typeorm": "^0.1.16",
    "typeorm-routing-controllers-extensions": "^0.1.0",
    "typeorm-typedi-extensions": "^0.1.1",

Thank you.


Cellular network not working on mi 10

After flashing zip n restart cellular network issue on mi 10

Hello,
I have been contacted by many other people with newer xiaomi devices and Pixel Spoofs are not supported on some xiaomi phones. Sorry for this. I also do not have a xiaomi phone to test it on to make it work.


Implements terms page directly under Cofacts website

Loads latest term from Github; updating term do not require a rebuild and redeploy.
Loads markdown parser and DOM sanitizer from CDN (so that it does not take space).
Includes a link to Github for users to check the revision of this agreement

Desktop

Mobile

Coverage decreased (-0.01%) to 76.235% when pulling 9c58e6db88f3537c06531e62b2a219be448462c8 on terms into f20078346f8d54c02e965eea59a66fa816b2a8ad on master.


@!attribute is not documenting dynamic setters when the type specifier is [rw]

I'm working on a fog module and using the @!attribute directive to document the models' and collections' attributes. The getters and setters are dynamically created by fog.
When I generate the docs with the '--list-undoc' flag, I get numerous undocumented setters, and they all appear to be the ones with a type specifier of [rw]. The ones that have a type specifier of [w] do not seem to be showing up in the undocumented methods data. Here's a snippet of the document generation output:
(in file: lib/fog/vzcloud/models/compute/vnic_metrics.rb)
Fog::Compute::VZCloud::VnicMetrics#granularity=
Fog::Compute::VZCloud::VnicMetrics#number=
And in that file, here's the directives in question:
    # @!attribute [rw] granularity
    #   The granularity of these metrics, can be either H for hourly or D for daily
    #   @return [String] the granularity
    attribute :granularity, :type => :string

    # @!attribute [rw] number
    #   The number of the Vnic these metrics are for
    #   @return [Integer] the Vnic's number
    attribute :number, :type => :integer

@stjeanp YARD attaches documentation to the reader, so the attributes are getting documented, just not on the generated writer object. This is expected behavior, and you can safely ignore this undocumented attribute.

Interesting... Thanks for explaining that.
I haven't had time to crawl through the code, but I'm wondering if there's a way to tweak it so that the code thinks the writer is documented so that the warnings are suppressed and the stats accurately reflect the actual documentation state...

It would be incorrect to convince YARD that the object is documented. The reality is that the metric used for calculating coverage of generated HTML is not exactly that of the actual objects themselves in the registry. Specifically, the yard stats command as well as the stats that come out of running yard, should never be used as accurate representations of documentation coverage-- at best they are estimates. I've stated this a number of times and stand by this.
What you actually want is to use the registry to programmatically query for undocumented methods using your own custom heuristics. Registry.all.select {|o| o.docstring.blank? } will get you the list of undoc'd objects, which you can then prune down further using your own rules. Appending your own --query conditions would be valid too (like --query 'o.name !~ /=$/').

Makes sense and thanks for the tips. I'm going to go ahead and close this and start messing around with that.
I appreciate you taking the time to work through this with me.


Improve error handling at plugin load time

See original issue on GitLab
In GitLab by [Gitlab user @tristanvb] on Mar 25, 2018, 10:47
Historically, I added PluginError near the beginning of the project, to test for all the odd cases where we have trouble loading malformed or broken plugin.
Since then we have improved a lot in the domain of error reporting, but the existing PluginError does something incorrect, as it:

Inherits from BstError, and as such is treated as a simple informative message to the user.
Is actually used to indicate a bug in a plugin - these errors are aimed at making life easier for plugin authors.

Recommended course of action
First, we should make PluginError stop inheriting from BstError, as it is more helpful to a plugin author to see a full stack trace in the case there is an error loading their plugin.
Further, since we have identified an opportunity (as a result of discussion about issue #317) to report a generic error to the user in the specific case that a python plugin tries to import a dependency that is not a hard dependency of BuildStream, we should raise a LoadError for that specific case instead of a PluginError, with a more informative message; such as:

"The foo plugin failed to import python module bar, please install it with pip3 or using your distribution package manager"

Plugins which can behave better
deb
Currently, we have the new deb source plugin which imports arpy at the toplevel (as discovered in #317), I think with a generic error about not being able to find python dependencies, such as the suggested LoadError above - we should not really need anything custom in the deb source for this.
Without the above suggested improvement in the core, it currently says something a little bit to cryptic to report to an innocent user:

Error loading pipeline: Failed to load Source plugin 'deb': No module named 'arpy'

ostree
The ostree plugin on the other can be installed on platforms where ostree is not a hard dependency of BuildStream. In this case, it would not be acceptable to just report an error about a failure to import the gi introspection module.
In this case, it could be interesting to do something like this at the toplevel:
try:
    from buildstream import _ostree
except ImportError as e:
    raise SourceError("Informative message about installing ostree, " +
                       "with a hint that it may not be available on the given platform") from e

In GitLab by [Gitlab user @tristanvb] on Mar 25, 2018, 10:59
changed the description

In GitLab by [Gitlab user @tristanvb] on Nov 4, 2020, 15:14
It's time for me to drop this, I've come back and looked at it conflicted a few times over the year, we refactored the plugin factories significantly and I think the user and developer experiences are satisfactory the way things are.

In GitLab by [Gitlab user @tristanvb] on Nov 4, 2020, 15:14
changed the description


chore: fix typedoc setup

chore: use branch for link references
update docs
use markdown for docs

fixes #275

Codecov Report

Merging #309 (0a35128) into main (a6096b2) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main     #309   +/-   ##
=======================================
  Coverage   89.83%   89.83%
=======================================
  Files           6        6
  Lines          59       59
  Branches       17       17
=======================================
  Hits           53       53
  Misses          6        6


V04 MEX

Hi @gronert-m ,
This is the V4 of MEX ready to be merged. I integrated all the changes as per our discussions and everything is checked.
Best,
Alexandra

Thank you @alexandraqn ! Please delete the branch once you are sure it is no longer needed.


Update the game over message

Update the game over message so people know how to play again!
Click Create pull request.

Tutto ok


Missing arrow and weird blue box

Please verify the version of auro-combobox you have installed
@latest
Please describe the bug
Go to Auro docsite
Go to auro-combobox
See dropdown arrow is blue and arrow seems to be located outside of the component.

Reproducing the error
This issue is reproducible on the Auro docsite
Expected behavior
I would expect an arrow like select
What browsers are you seeing the problem on?
Chrome
Additional context
I only checked one browser.
Exit criteria
Arrow design matches blueprint.

Root cause of bug is an issue in Auro input that'll be going out shortly.  moving to code review needed to await re-test after that fix is in.


should not have to ping logoIsTouched to force v2 rendering

Requires fix at https://github.com/microsoft/pxt-microbit/issues/3920
to remove input.logoIsPressed call in jacdac.

Required fixes: https://github.com/microsoft/pxt/pull/8065 https://github.com/microsoft/pxt-microbit/pull/3955


Updated Versions etc...

feel free to edit / merge if it helps keep your example up to date

Thanks for this, I'm away right now, but I'll take a look later in the month.
I see you closed the PR though. Is it still merge-able?

I may have inadvertently forgotten I was working on a public repo and pushed a commit later without thinking too deeply and realised I pushed a teams channel webhook url to a public repo lol. So deleted the fork on github. I can make a new pr in a bit, yeah no rush anyway
[cid:feefo-logo_e238e049-1773-4b11-8c35-989753960847.png]<www.feefo.com>
Matt Coffey
Chapter Lead Engineer
e<EMAIL_ADDRESS>t:
[cid:sig-labels_c9ee415b-11bd-4c82-ba2f-7253fe4529e6.png]
This message is confidential. It may also be privileged or otherwise protected by work product immunity or other legal rules. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone.
Feefo Holdings Ltd. is a company registered in England and Wales. Registered number: 71 91 962. Registered office: Feefo Barn, Heath Farm, Heath Road East, Petersfield, Hampshire, GU31 4HT, United Kingdom.
London: 2nd Floor, Walbrook Wharf, 78-83 Upper Thames St., London EC4R 3TD
Boston: 28 Atlantic Wharf, Boston, MA 02110, United States

From: Joe Wright @.>
Sent: Tuesday, July 11, 2023 2:32:58 AM
To: joejag/synthetic-cypress @.>
Cc: Matt Coffey @.>; State change @.>
Subject: Re: [joejag/synthetic-cypress] Updated Versions etc... (PR #1)
Thanks for this, I'm away right now, but I'll take a look later in the month.
I see you closed the PR though. Is it still merge-able?
—
Reply to this email directly, view it on GitHubhttps://github.com/joejag/synthetic-cypress/pull/1#issuecomment-1629963148, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2AW4HGP3LBCIL2JH6LEIR3XPSUMVANCNFSM6AAAAAA2ART2FQ.
You are receiving this because you modified the open/close state.Message ID: @.***>

Hi @joejag,
Could you ask github to delete this pr here: https://support.github.com/contact?source=subtitle&tags=rr-general-technical
I accidentally pushed stuff not appropriate for the public repo.
Thanks,
Matt


ECS version update

When logging via winston I noticed that the ecs version is 1.6.0. Is this maintained to catch up with ECS versions 8.x?

Today, do have a solution to resolve this problem ? or alternative code ?
I got the same probleme

Note that (per https://www.elastic.co/guide/en/ecs/current/ecs-ecs.html#field-ecs-version) the ecs.version field shouldn't itself be a cause of compatibility concerns. Are there particular compatibility issues with some fields that you are hitting?
The ECS logging formatters from this repo don't touch on that many fields in ECS, so it is possible (even likely) that there won't be any breakage when moving the ecs.version value forward.
I'll keep this issue open until we've updating the ecs.version value emitted by these loggers.
(Note to self: I'll need to work forward through the ECS versions starting from https://github.com/elastic/ecs/blob/main/CHANGELOG.md#160 to see if there are any adjustments needed.)

The relevant ECS field namespaces for these ecs-logging-nodejs libs are:

log - https://www.elastic.co/guide/en/ecs/current/ecs-log.html
ecs - https://www.elastic.co/guide/en/ecs/current/ecs-ecs.html
tracing - https://www.elastic.co/guide/en/ecs/current/ecs-tracing.html
error - https://www.elastic.co/guide/en/ecs/current/ecs-error.html
client - https://www.elastic.co/guide/en/ecs/current/ecs-client.html
http - https://www.elastic.co/guide/en/ecs/current/ecs-http.html
url - https://www.elastic.co/guide/en/ecs/current/ecs-url.html
event? Just event.dataset.
host? Only for host.hostname used for Pino.
process? Possibly relevant for Winston exception log record conversion, but not being used now.
os? Possibly relevant for Winston exception log record conversion, but not being used now.

working through the ECS changelog
Pulling out relevant references in https://github.com/elastic/ecs/blob/main/CHANGELOG.md from 1.6.0 to the current latest (8.10.0):
1.7.0

http.[request|response].mime_type #944
Added the field .subdomain under client, destination, server, source and url, to match its presence at dns.question.subdomain. #981

1.8.0
Added os.type. #1111
1.9.0
Added http.request.id. #1208
8.0.0

Remove deprecation notice on http.request.method. #1443

8.7.0

description for host.name definition updated to encourage use of FDQN #2122

summary

log - No relevant changes.
ecs - No changes.

We'll bump ecs.version to "8.10.0".

tracing - No changes.
error - No changes.
client - No relevant changes.
http

http.[request|response].mime_type added in 1.7.0, but not considering
adding this. It must be determined from response content, not a header.
http.request.id added in 1.9.0. Consider adding a possible req.id
to http.request.id instead of to event.id. Note that req.id is not
part of the http.IncomingMessage
interface. Need to trawl through the various web frameworks to come up
with any typical interface for a request id.
http.request.method guidance was changed in 8.0.0 to retain the origin casing.

url - No relevant changes.
event? Just event.dataset. - No change.
host? Only for host.hostname used for Pino. - No change.


 It'll chunk away on this for an hour. If I just cancel it, delete the file and download a different encoding of the same episode it will be done in less than 5 minutes. Most files I download (including 1080p content) are done in under 10 minutes. This one took at least an hour before I killed it.
When I check top, python is using 100% CPU.
CPU:
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 61
Model name:            Intel(R) Celeron(R) 3205U @ 1.50GHz
Stepping:              4
CPU MHz:               1499.941
CPU max MHz:           1500.0000
CPU min MHz:           500.0000
BogoMIPS:              2993.04
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              2048K

Memory: 8GB, 2GB free when this is running
Is there any more info I can provide that will help?

Entirely depends on what is being done to the file
Remuxing is quick
Reencoding is slow, and depending on how many streams need to be reencoded this is compounded

Close the ffmpeg.exe process that is running, check the log file and see if ffmpeg is spamming this warning:
non-monotonous dts in output stream
I ran into the same file that you are. It was taking forever to re-encode only the audio, and when it finished it would be out of sync with the video.  It infuriated me so much that I engaged kludge/crappy hack mode to fix it:
https://github.com/Collisionc/sickbeard_mp4_automator/commit/c2aef76c5bde0be5ed91640f919bd349cb358782
(Explanation of what is occurring is in the commit note)
She sure isn't a pretty fix, but she works.

If you're using manual.py the JSON output should specify which codecs are being copied vs which are needing active transcoding
If you post that output I can let you know if it looks like lots of transcoding is taking place

I will check it out. Might be a while though.

This is happening right now. Where can I find the relevant logs for ffmpeg ? or SBA logs?

Easiest way to force logs for ffmpeg is to open task manager in windows and end the process named ffmpeg.exe while it is encoding the video that is giving you problems. Then go to your sickbeard mp4 automator folder, and there will be a file named info.log, which will have the necessary logs.
I would delete info.log before you do this, so that it will only have logs from the most recent video.

OK. Missed it that time (went to bed). I'll try and catch it next time it happens.

This happened again tonight. I renamed info.log to info.log.old and then killed the ffmpeg process (not on windows though, used kill via ssh). Unfortunately it did not write out to info.log.
/opt/sickbeard_mp4_automator $ ll | grep log
-rw-------  1 media media 1455721 Aug  4 21:03 info.log.old
-rw-r--r--  1 media media    1122 Mar 26 10:45 logging.ini


[Feature] Add Tests for Web Cmdlet Certificate Authentication

Address #4609 and replaces tests for #4546.
This test uses an ASP.NET Core 2.0 app to run a simple service to echo back the client certificate details if one was  provided. If a client cert is not provided, the details are empty and the status reports FAILED. The app runs in a Job.

@markekraus,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@markekraus See as we prepare TestExe.csproj https://github.com/PowerShell/PowerShell/blob/b3e7fd374f2898f7e84b28229aada18a3fcbe23e/build.psm1#L780

@iSazonov Thanks, I'll see how I can fit this one in into Publish-PSTestTools
on another note, the mdspell is falsely calling out ASP.NET in my README.md. Is there place to add that to be ignored? Or is there another way to handle it?

Yes, it is .spelling - add Asp.Net (case-sensitive).

@markekraus Can we replace our ListenerHttp script with the application (not in the PR)?

@iSazonov In theory we could move all of the we tests to this, but, it would mean rewriting the existing features of HttpListener into ASP.NET. Or doing something that allowed PowerShell to manage the business logic.
I was already considering switching the Validate Invoke-WebRequest -SkipCertificateCheck tests over to this new listener since the ServerCert fails as a self-signed cert.

@markekraus Please keep the PR as small as possibly - it is better to make cleanups later.
If we can move to the new application from HttpListener we should ask the test area experts to  this /cc @adityapatwardhan - if it will be approved we'll review the code with the point in mind.

@iSazonov Should I roll back the baddssl changes?  Aside from those, the rest of the changes on this PR are interdependent.
Can you restart the failed Travis CI test? it failed an unrelated test due to httpbin not being unavailable.

@markekraus Main rule is to keep PR as small as possible and don't add unneeded changes.
So I believe, yes, we should rollback - only keep the commit for follow PR. Also you can wait conclusion from @adityapatwardhan I asked to lead this change as the test area expert.
Main question now to continue the review is - do we want move from HttpListener in future or not.

Hmm... The macOS Build is "passing" but in actuality it is hitting an unhandled exception and exiting without property saying it has failed.

It looks like the AppVeyor build beta.5-4786 failed due to temporary issue with powershell.myget.org. if someone could restart the build, that would be helpful.

@markekraus It seems I haven't permissions. So you can "rename" last commit and push - it will be restart CI jobs.

@iSazonov I'm going to assign this to you as you've been involved while @adityapatwardhan is taking time off

@SteveL-MSFT We need get approve from test area experts because of significant changes in the PR - please ping anybody if @adityapatwardhan is busy.

Thanks, @markekraus  and @iSazonov for all your work on this so far.

Something is amiss with macOS and the client certificate. It was working with Get-PfxCertificate and the ClientCert.pfx then it started failing without any change to the cert or the Get-PfxCertificate. so I switched to GetSelfSignedCert and it was working a few commits ago. I made change to another portion of WebCmdlets.Tests.ps1 but didn't touch this function and now it is failing to import the certificate with this function. I'll have to find some macOS environment to troubleshoot this in.

After moving past the password protected pfx issue, I discovered that this is still not supported on macOS
The handler does not support client authentication certificates with this combination of libcurl (7.55.1)
dotnet/corefx#9728
dotnet/corefx#19718
It was missed as passing on mac because of the issue reported in #4641. The test was actually failing
https://travis-ci.org/PowerShell/PowerShell/jobs/265494069#L8693 but the CI reported passing. Then we ultimately marked the test pending so that we could address this through #4609
@TravisEz13 @iSazonov , I'm not sure where to go from here. It looks like this is definitely still unsupported in macOS. It does work in windows and Linux. I could make this test skipped on macOS, but the bigger issue of this functionality being enable but not available in macOS, I'm unsure what to do.

@TravisEz13 The test for this are currently set to pending in master. But, without these replacement tests, there is no need to add the HttpsListener. Essentially, this entire PR is probably not worth merging if the tests will remain pending unless we want this PR to add the HttpsListner in preparation for the future with the new tests pending. Would you like to go forward with adding the HttpsListener or should we close this PR and save the HttpsListener for when it is needed?

Sorry, I should clarify.  You should detect if the tests are running on macOS and set them to skip.  We have this pattern for windows only features in many tests.

Here is an example that skips for everything that is not Windows:  https://github.com/PowerShell/PowerShell/blob/e83fcca277a9dd81d5cb2ff56002b6179c34ec3b/test/powershell/engine/Api/BasicEngine.Tests.ps1#L7

@TravisEz13  Thanks for clarifying. I have adjusted the tests. I still kept the changes to client cert. It at least removes that hideous base64 block from the test file.

@markekraus Great investigations! I think we should open new tracking Issue for the MacOs issue (not 4609) and cross reference it to 3648 (and change comments in test files).

@iSazonov #4650 created and comments updated.

@markekraus Thank you for your patience and your speedy work.
LGTM.

@iSazonov Thanks for being patient with me too and for all your suggestions!

@iSazonov can you formally approve?

It will be good to get a review from test area experts.

Thanks! I'll merge on next week.

@markekraus Many thanks for great work!
The PR was merged and  way is opened for follow work:

[ ] - Cleanup HTTPS tests, replace #region with "Context".
[ ] - Cleanup HTTP test to use WebListener.

Please move the points to a tracking Issue.

@iSazonov  I have opened #4179 to track the HTTPS tests.
Should I continue the work for the second item under the already open #2504 or should I create a new issue?

@markekraus #2504 is good. Please leave a message about WebListener there for cross reference. And if you want work on this you should ask Travis there.


Create dummy test data

Please add ideas of visually satisfying and physically meaningful data that we can use for demo and testing.
I am thinking of simulated 3d scan of lime...?

3d was too hard! 2d it is...!


use raw voice input

hello, do we have options not parse the voice collected by microphone into command, but output it directly?

The microphone only returns the mapped strings listed at
https://docs.petoi.com/extensible-modules/voice-command-module#id-2.-use-the-predefined-voice-commands
On Sun, Jun 23, 2024 at 5:26 PM sheep @.***> wrote:

hello, do we have options not parse the voice collected by microphone into
command, but output it directly?
—
Reply to this email directly, view it on GitHub
https://github.com/PetoiCamp/OpenCatEsp32/issues/18, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACKLZGB6G3MHIOEA5KLATFTZI2IEJAVCNFSM6AAAAABJYGRJ7GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3DQNBWG4YDQOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
~~
Rongzhong Li, PhD
http://borntoleave.github.io

get, thanks for your reply. Guess i need another microphone to collect additional sounds

I have a related question.  Can those mapped strings be changed programmatically (perhaps by reflashing the memory in the voice module)?  Basically, I 'd like to programmatically trigger voice feedback (e.g. have the voice module say "Object detected", triggered by a programmatic detection of an object on one of the sensors.  Would be pretty cool to be able to do this...)


Added Animated Splash Screen

I have added an animated splash screen.

@avjinder Could you please review it?


Adds CRUD methods based on new flags.

I wanted to generate the CRUD functions as methods on a type. This allows me to define a CRUD interface in my application. That then allows me to inject the interface as a dependency into my handlers. This allows me to mock the interface easily when testing those handler functions.
The mechanism is the addition of two flags.

doDI adds a receiver to the CRUD functions
diName defaults to *sql.DB and is the name of the receiver.

this doesn't include the tests. I'm closing this pull request.


Fix Windows python path instructions

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Fixed on another PR


Removing extra worker param

I am removing extra worker param which was causing TS2345 errors when using a simple tsconfig.json
{
    "compilerOptions": {
        "lib": [
            "dom",
            "es2017",
            "deno.ns",
            "dom.iterable"
        ]
    }
}

running: deno run -A -c .\tsconfig.json .\crypt.ts
deno 1.2.0
v8 8.5.216
typescript 3.9.2

@JamesBroadberry Do you think you can merge this in so I can move my project forward? Thanks

Hi @Bidek56, sorry, I've been busy with work so haven't had chance to properly review this.
I've just tried it out without the deno: true flag and it's causing issues because the worker requires access to Deno specific modules. This is because crypto.GetRandomValues is required.
It doesn't seem to cause any issues with my projects using it so if you can create some steps to reproduce and raise an issue, I can take a further look.
Thanks!

Simple: import { hash, compare } from<EMAIL_ADDRESS>causes:
error: TS2345 [ERROR]: Argument of type '{ type: "module"; deno: boolean; }' is not assignable to parameter of type 'WorkerOptions'.
  Object literal may only specify known properties, and 'deno' does not exist in type 'WorkerOptions'.
    { type: "module", deno: true },
                      ~~~~~~~~~~
    at https://deno.land/x/bcrypt@v0.2.3/main.ts:18:23

TS2345 [ERROR]: Argument of type '{ type: "module"; deno: boolean; }' is not assignable to parameter of type 'WorkerOptions'.
  Object literal may only specify known properties, and 'deno' does not exist in type 'WorkerOptions'.
    { type: "module", deno: true },
                      ~~~~~~~~~~
    at https://deno.land/x/bcrypt@v0.2.3/main.ts:50:23

TS2345 [ERROR]: Argument of type '{ type: "module"; deno: boolean; }' is not assignable to parameter of type 'WorkerOptions'.
  Object literal may only specify known properties, and 'deno' does not exist in type 'WorkerOptions'.
    { type: "module", deno: true },
                      ~~~~~~~~~~
    at https://deno.land/x/bcrypt@v0.2.3/main.ts:83:23

Found 3 errors.

when running deno run -c .\tsconfig.json .\crypt.ts
with:
{
    "compilerOptions": {
        "lib": [
            "dom",
            "es2017",
            "deno.ns",
            "dom.iterable"
        ]
    }
}

If you know the tsconfig.json that would resolve the error, that would be great. Thx


chore: clean repo

Motivation
I started doing a little cleanup like in https://github.com/caas-team/py-kube-downscaler/pull/112.

Changes

Made pre-commit config usable
Removed not needed files
Formatted files
Adjusted a few parameters
Bumped version number for new release

Tests done
pre-commit and pytest pass

TODO

[x] I've assigned myself to this PR

@JTaeuber We should bump python version in the workflows too (similar to this), and maybe also the classifiers in pyproject.toml

forgot about the worflows, good call 👍

Yeah, exactly, will look clean on pypi  then


build.DeleteOffer broken?

It looks like some recent change in the way build.Amount is parsed broke build.DeleteOffer.
 DeleteOffer: could not build transaction: ManageOfferBuilder error: cannot parse amount:

If you look at the two implementations, the only difference between UpdateOffer and DeleteOffer is the amount.
// UpdateOffer updates an existing offer
func UpdateOffer(rate Rate, amount Amount, offerID OfferID) (result ManageOfferBuilder) {
	return ManageOffer(false, rate, amount, offerID)
}

// DeleteOffer deletes an existing offer
func DeleteOffer(rate Rate, offerID OfferID) (result ManageOfferBuilder) {
	return ManageOffer(false, rate, Amount("0"), offerID)
}

UpdateOffer works correctly when the amount is non-zero, but if you set it to 0 (or called DeleteOffer, you get the same error (above.)
I also tried 0.0000000 for the amount, and that had the same error.

Okay, never mind. This was an issue on our side. Apologies for the noise.


Extract logic from bin/git-pr-release

Ref: https://github.com/motemen/git-pr-release/issues/29
Overview
I also got the same issue as https://github.com/motemen/git-pr-release/issues/29. (Our CI server uses rbenv.)
main if $0 == __FILE__ || $0 == File.join(Gem.dir, "bin", "git-pr-release")

I tried to fix this code, but at the end, I also have come to the same conclusion with @hkurokawa.

So I am wondering if there might be no way to tell apart script loading from script execution (as rbenv loads the script to run).

I think this is one of the ways to fix current situation. My motivation is just to make this script work properly. Basically I tried to not change any logic.
Tested as below
gem build git-pr-release.gemspec
gem uninstall git-pr-release
gem install /path/to/git-pr-release/git-pr-release-0.8.0.gem
git-pr-release

@onk
Thanks! would you release when you have time? 🙇

+1 on this. Looking forward to the release of this fix soon 🙏

Released as v1.0.1.


Add tests exercising private IP with fuse and without it.

Feature Description
We can use custom runners deployed to App Engine.
Sample code
// sample code here

Alternatives Considered
No response
Additional Details
No response

Closing this as low-value. The custom runners don't support FUSE presently.


Update angel_seo to Angel 2

Needs almost no changes: https://github.com/angel-dart/seo

Remove dart2_constant use
Update dependency - angel_framework: ^2.0.0-alpha
Update dependency - file: ^5.0.0
Update example to mirror example/main.dart

V2: https://pub.dartlang.org/packages/angel_seo


Upgrade to React Router 6.4

Ref: https://www.youtube.com/watch?v=aX74DbFT5nI

Current latest is 6.17.0


Test & document Visibility Control Header with static built libraries

Test a change to the Symbol Visibility Control Header to accommodate building code as a static library. The export macros will be blank in the case of a static library.
The change is discussed in this comment thread:
https://github.com/ms-iot/ROSOnWindows/pull/322#discussion_r595002284

To clarify, I usually suggest to support the static usecase for standalone libraries so that they can be easily packaged inside vcpkg (https://github.com/Microsoft/vcpkg) for all the official supported triplets.

https://ms-iot.github.io/ROSOnWindows/Porting/SymbolVisibility.html

We need to move our symbol visibility doc to ROS.org. And add the CMake doc

fixed - documented and published


Jasmine test config hotswap

For every Jasmine test that is ran, a new nodeJS process, a Karma server and a PhantomJS is started. This wastes a lot of time. By keeping the nodeJS process, the server and the browser running in between tests, tests could be ran much faster.
A proof of concept for this feature has been made by Nico which shows it is possible to keep the processes running while collecting code coverage for every test. The proof of concept can be found here.

This issue will be solved with #34


Introduce weak references

Fix #69
Fix #48 (maybe)

Author is @Cologler
Continued from #153 because that branch was mistakenly deleted.

@piskvorky @Cologler Please eyeball this PR and let me know if you spot anything odd

@piskvorky @Cologler Please eyeball this PR and let me know if you spot anything odd

Looks Good To Me 👌.

What if the user does some longtime work in the loop?
for value in a_sqlite_dict.values():
    # long timework here, like an HTTP request
    ...

What if the user does some longtime work in the loop?
for value in a_sqlite_dict.values():
    # longtime work here, like an HTTP request
    ...

I think the response queue will continue to receive new items.
Basically, there is a producer/consumer problem here. The producer is the sqlite thread and the consumer is the user. We want to produce results quickly enough for the user to consume them without overwhelming the user. If we produce too quickly (or the user is too slow to consume) then the queue grows in size and occupies more memory.
I think one way to solve that particular problem is to use fixed-size queues for the responses. If a queue is full, then it means the user is consuming faster than we are producing, and we can produce slower.
@piskvorky What do you think? Is there a reason why we use queues of unlimited size?

If a queue is full, then it means the user is consuming faster than we are producing, and we can produce slower.

Do you mean "consuming slower"?
Anyway, limiting the queue is technically easy, here:
https://github.com/RaRe-Technologies/sqlitedict/blob/8545a174a4a32bd2f8eb7c17d89899370138fe3a/sqlitedict.py#L623-L624
But I'm not sure about the implications. The code is sufficiently complex that blocking puts could lead to dead locks, unless we think through all the code paths very carefully. What happens when the consumers don't get (for whatever reason – generator, exception…), so that the put blocks forever?

Do you mean "consuming slower"?

Yes, sorry.

Anyway, limiting the queue is technically easy, here:

Yes, as you point out, this is the easy part. The hard part is ensuring nothing else breaks.

What happens when the consumers don't get (for whatever reason – generator, exception…), so that the put blocks forever?

Good question...
Anyway, I think this discussion is out of scope for this PR (but definitely helpful). I think we're done for now.


force refresh of lists in listpicker

Category
[ ] Enhancement
[ ] Bug
[x ] Question
Version
Please specify what version of the library you are using: [  latest       ]
Expected / Desired Behavior / Question
Hey, I have a webpart that lets the user select an existing list using the list picker  or create a new one.  If the user creates the new list i want the newly created list to be  selected in the listpikcer.
The listpicker is caching its list of lists , so even though i set the selectedList property to the ID of the new list it does not appear as selected. The only time the list gets reloaded in componentdidupdate is
if (
prevProps.baseTemplate !== this.props.baseTemplate ||
prevProps.includeHidden !== this.props.includeHidden ||
prevProps.orderBy !== this.props.orderBy ||
prevProps.webAbsoluteUrl !== this.props.webAbsoluteUrl
) {
this.loadLists();
}
Any way to have it refresh the list of lists? I was thinking we could just add a boolean 'refresh' switch to its props and also check that in the comnponentdidupdate.  then in my code i could just toggle the refresh prop.
Any thoughts on this. How is it solved elsewhere in the library.

arghh!! just added for lines of code to my PR and it failed. Any idea whats wrong. The change is working great locally.

forgot about this one! i think it’s included in my pr

@russgove just to double-check, is this change included on the PR that you submitted and was merged recently?

yes, this issue was fixed in my last pr


MySQL container won't connect and stop after a while when creating a new application.

Sail Version: 1.14.9
Laravel Version: 9.17.0
PHP Version: 8.1.6
OS: Ubuntu 22.04 LTS

Description:
When trying to create a new application from scratch with
curl -s http s://laravel.build/example-app | bash

And then start the containers with sail up -d The MySQL container won't properly start.

If I try to enter the mysql console with sail mysql, it shows me the following:ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)

If I wait a little more, the MySQL container will stop and show the following:service "mysql" is not running container #1

Then if I check the logs (docker logs example-app-mysql-1), it shows the following:[Entrypoint] MySQL Docker Image 8.0.29-1.2.8-server
[Entrypoint] Initializing database
2022-06-08T18:46:31.600497Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.29) initializing of server in progress as process 17
2022-06-08T18:46:31.807325Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-06-08T18:46:44.159136Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-06-08T18:47:11.073736Z 6 [Warning] [MY-010453] [Server] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
[Entrypoint] Database initialized
2022-06-08T18:48:08.580864Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.29) starting as process 88
2022-06-08T18:48:08.651958Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-06-08T18:48:09.564375Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-06-08T18:48:10.523509Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2022-06-08T18:48:10.523690Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2022-06-08T18:48:10.611744Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.29'  socket: '/var/lib/mysql/mysql.sock'  port: 0  MySQL Community Server - GPL.
2022-06-08T18:48:10.611764Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: /var/run/mysqld/mysqlx.sock
Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/leapseconds' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/tzdata.zi' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/zone.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/zone1970.tab' as time zone. Skipping it.

[Entrypoint] running /docker-entrypoint-initdb.d/10-create-testing-database.sh
/docker-entrypoint-initdb.d/10-create-testing-database.sh: line 3: testing%: command not found
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 1064 (42000) at line 2: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '.* TO 'sail'@'%'' at line 1

For some reason the create-testing-database.sh script is not working. I'm guessing it detect it as a shell script not a sql script.
Workaround

MySQL won't be capable of connect again, so it will stop the container
Start the MySQL container with docker start example-app-mysql-1
The container will start correctly without the testing database, just the project database.
Enter the MySQL console with the root user: docker exec -it example-app-mysql-1 mysql -u root -p
Enter the password
Enter the following 2 commands: CREATE DATABASE IF NOT EXISTS testing; and GRANT ALL PRIVILEGES ON `testing%`.* TO 'sail'@'%';

Hi @FaruNL,
I ran into this issue myself last week and fixed it in #429 which was released in Sail 1.14.10 on Thursday.
I wasn't able to replicate the issue with a fresh install using curl -s https://laravel.build/example-app | bash which installed 1.14.10.
I'm not sure why you would have got 1.14.9 unless this occurred prior to the release of 1.14.10?

Hi @FaruNL,
I ran into this issue myself last week and fixed it in #429 which was released in Sail v1.14.10 on Thursday.
I wasn't able to replicate the issue with a fresh install using curl -s https://laravel.build/example-app | bash which installed v1.14.10.
I'm not sure why you would have got v1.14.9 unless this occurred prior to the release of v1.14.10?

I'm gonna try this rn. It was prior to v1.14.9 the first time. The other times I'm not sure.

Now it works, however it was very slow, maybe 5 minutes to correctly set up the user and databases in the container.


nixos/iso-image: Support specialisations.

Not the most elegant of code just yet, so marking as draft for now.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@vlinkz My only remaining concern with this PR before marking ready for review is that I don't think the graphical installer will automatically select the latest kernel when that specialisation is booted. Do you have any ideas for how to fix that?

@vlinkz My only remaining concern with this PR before marking ready for review is that I don't think the graphical installer will automatically select the latest kernel when that specialisation is booted. Do you have any ideas for how to fix that?

/etc/nixos-generate-config.conf has the specialisation config for the booted session right? We can just parse that file and add the option as needed

Not sure how far you're planning on upgrading nixos-generate-config, but another option could be add all the options currently supported by the graphical installer to nixos-generate-config (like --desktop=gnome/kde) and then use nixos-generate-config within calamares instead of the current custom snippets.

@vlinkz Yea, I think unifying nixos-generate-config with the calamares installer would be a great step. Heck, we could rewrite nixos-generate-config in python or rust or something (to go with all the other -ng rewrites lately) and add options to this new nixos-generate-config.conf file so that calamares can just generate that file instead of generating nix expressions.
(Also, I should probably make it TOML instead of INI)

That said, I hadn't originally been planning to upgrade nixos-generate-config much at all. So maybe to start with we just leave it the way it is (except TOML) and parse the kernel option in calamares. We can make it fancy later.

Heck, we could rewrite nixos-generate-config in python or rust or something

Definitely a fan of that idea! But yeah definitely a longer term project.

That said, I hadn't originally been planning to upgrade nixos-generate-config much at all. So maybe to start with we just leave it the way it is (except TOML) and parse the kernel option in calamares. We can make it fancy later.

Sounds good, I'll work on a way for calamares to detect the file and modify the config accordingly.


Visualscript connection lines get drawn over or below the nodes each time a node gets selected

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Godot 3.0 master https://github.com/godotengine/godot/commit/da144fed4c49133a93b3b83cfc665352c0af351a
Issue description:

Steps to reproduce:

Add nodes to a visualscript
Make lines overlap nodes to better see the issue
Start selecting different nodes (or the same sometimes)
Lines get drawn over and below the overlapping node each time you select a node

I tried a bit in 3.3-stable and didn't manage to reproduce the issue, could you confirm if it's also fixed on your end?
I've been trying with the setup and all kinds of attempts at selecting different or the same nodes:

Sadly it seems it's still happening on 3.3-stable.

The gif was recorded on Windows 10 GLES3

Now I can also reproduce it... not sure what I missed before.

I have seen this happen in my own tools, this is a problem with GraphEdit


Bandit 1.6.0 no longer respects excluded directories

Describe the bug
Prior to the bandit 1.6.0 release, I was using bandit like so:
bandit -r . -x ./mymodule1/tests/,./mymodule2/tests/

However, with bandit 1.6.0 the ./mymodule1/tests/ and ./mymodule2/tests/ directories are included in the results. I have confirmed that you can exclude individual files still, just not directories.
To Reproduce
Steps to reproduce the behavior:

Create a directory with a vulnerability in it somewhere
Run bandir -r . -x ./your-new-dir/
See vulnerability results that should be excluded

Expected behavior
Bandit should be excluding the directories entirely that are passed as args to the -x flag.
Bandit version
bandit 1.6.0
  python version = 3.6.5 (default, Jun 17 2018, 12:13:06) [GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-9<IP_ADDRESS>)]

Most likely a regression caused by https://github.com/PyCQA/bandit/pull/450

Thanks, I can try fix it in a couple hours

I have also just run into this issue with 1.6.0 - my auto builds are now failing due to scanning excluded directories :)

Likewise I have found that exclude: ./tests/ in my .bandit file no longer are respected.
I have tested several times with different paths and using exclude_dirs: instead of exclude: but to no avail.
A quick fix would be much appreciated! :-)

Yep, I just encountered this as well. Glad to see there's already an issue filed and a fix in the works. I'll temporarily downgrade to 1.5.1 until 1.6.1 is out.

pinning to 1.5.1 worked out for me :)
keep up the good work!

I confirm this bug.
Following works in 1.5 but fails with 1.6.0 (tests directory contains unit tests):
bandit --exclude tests -r .

Is there by any chance an ETA for the resolution of this regression?

@volans- My PR (#489) is pending review

I tried to play a little with exclude directory in 1.6.0.
After changing bandit -r anitya/ anitya_schema/anitya_schema/ -x anitya/db/migrations -ll to bandit -r anitya/ anitya_schema/anitya_schema/ -x anitya/db/migrations/* -ll, the excluded folders are no longer ignored.
So before 1.6.1 is out, you could use the above.

Can anyone confirm this bug has been fixed?
I still run bandit<1.6 as the latest Bandit from PyPI scans the .tox/ folder. Here is an example that uses an absolute directory path to rule out location translation issues.
$ bandit --debug -r . -x $(pwd)/.tox
...
[node_visitor]	DEBUG	{'imports': {'sys', '_locale', 'locale'}, 'import_aliases': {}, 'node': <_ast.Load object at 0x7fc53651c278>, 'linerange': [0, 1], 'filename': './.tox/bandit/lib/python3.6/_bootlocale.py'}

Interestingly, specifying an absolute target path combined with absolute exclusion paths seems to work:
$ bandit -x $(pwd)/.tox/ -r $(pwd)
[main]	INFO	profile include tests: None
[main]	INFO	profile exclude tests: None
[main]	INFO	cli include tests: None
[main]	INFO	cli exclude tests: None
[main]	INFO	running on Python 3.6.8
Run started:2019-10-10 08:51:10.630871

Test results:
...
Code scanned:
	Total lines of code: 70
	Total lines skipped (#nosec): 0

Run metrics:
	Total issues (by severity):
		Undefined: 0.0
		Low: 2.0
		Medium: 0.0
		High: 0.0
	Total issues (by confidence):
		Undefined: 0.0
		Low: 0.0
		Medium: 0.0
		High: 2.0
Files skipped (0):

Also, specifying all absolute paths in a Tox target, a section in tox.ini, "fixes" the issue:
[testenv:bandit]
deps = bandit
commands = bandit --exclude {toxinidir}/.git,{toxinidir}/.tox,{toxinidir}/tests -r {toxinidir}

$ tox -e bandit
bandit installed: bandit==1.6.2,gitdb2==2.0.6,GitPython==3.0.3,pbr==5.4.3,PyYAML==5.1.2,six==1.12.0,smmap2==2.0.5,stevedore==1.31.0
bandit run-test-pre: PYTHONHASHSEED='2508293914'
bandit runtests: commands[0] | bandit --exclude /home/peter/.../scratch/example-flask/.cache,/home/peter/.../scratch/example-flask/.git,/home/peter/.../scratch/example-flask/.tox,/home/peter/.../scratch/example-flask/build,/home/peter/.../scratch/example-flask/dist,/home/peter/.../scratch/example-flask/docs,/home/peter/.../scratch/example-flask/tests -r /home/peter/.../scratch/example-flask
[main]	INFO	profile include tests: None
[main]	INFO	profile exclude tests: None
[main]	INFO	cli include tests: None
[main]	INFO	cli exclude tests: None
[main]	INFO	running on Python 3.6.8
Run started:2019-10-10 08:53:59.209246

Test results:
	No issues identified.

Code scanned:
	Total lines of code: 26
	Total lines skipped (#nosec): 0

Run metrics:
	Total issues (by severity):
		Undefined: 0.0
		Low: 0.0
		Medium: 0.0
		High: 0.0
	Total issues (by confidence):
		Undefined: 0.0
		Low: 0.0
		Medium: 0.0
		High: 0.0
Files skipped (0):
___________________________________________________________________________________________________________________________________ summary ____________________________________________________________________________________________________________________________________
  bandit: commands succeeded
  congratulations :)

Looks like there is still some hidden issue that needs fixing.

@LefterisJP I'm using bandit 1.6.2 and it works, however it depends on how you specify all paths. I'm using all full relative paths (eg. bandit -x './tests' -r .). If I omit ./ at the beginning of the exclude directory, that directory is not considered in the exclusion. It seems also that this behavior is the same with the full path, as stated by @bittner . There is definitively an issue on path handling

This issue still exists nearly one year later on Bandit 1.6.2.
While it makes very little sense, -x or --exclude seems to require an absolute path or ./-prefaced relative path.
E.g. if you have a venv in your current directory:
python -m bandit --exclude ./venv --recursive --output bandit.json --format json .

will work as intended whereas
python -m bandit --exclude venv --recursive --output bandit.json --format json .

Will attempt to scan all of venv/.

Still having this issue in 1.7.0. For gitlab reasons I had to include the virtualenv inside the project_root and bandit ignores all attempts to ignore that folder...

Just confirming that this issue still persists in 1.7

Coming back here include my workaround.
Using absolute paths has worked, but since that wasn't an option for gitlab i found that
bandit  --exclude ./.pipenv/* -r -ll .
seems to respect the excluded folder.

@ericwb please reopen based on ample evidence above.

I've faced just the same issue on 1.7. This command is hanging for several minutes:
bandit -lll -r -x tests .

as well as this one:
bandit -lll -r -x "tests/*" .

but this one works just as expected:
bandit -lll -r -x "./tests/*" .

The help output says that it excludes .tox by default, but my tox-dir is still scanned which is quite useless.
This is certainly not resolved and needs to be reopened.

Can confirm here than it still doesn't work when I add exclude tests to pyproject.toml
[tool.bandit]
exclude = "./tests/*"

Bandit 1.7.4 (Python 3.10.4)
bandit -c pyproject.toml -r src

with config pyproject.toml
[tool.bandit]
exclude_dirs = ["*/tests/*"]

works as expected.
In stdout I can see all exluded dirs:
['*/tests/*', '.svn', 'CVS', '.bzr', '.hg', '.git/*', '__pycache__/*', '.tox', '.eggs', '*.egg']

@zelenyjan There are a few interesting facts about the information your share:

Where did you get the exclude_dirs option from? It's neither in the documentation (which says, exclude) nor in the CLI help screen, Only from the code this can be seen. Which suggests that we have a bug in the docs.
Interestingly enough, the exclude_dirs option covers not only directories: You can specify a path to a single file, which then also gets excluded, specifically. (The naming seems a bit misleading.)
The Bandit source code suggests that you have a Bandit INI file present that gets read (because reading the excluded dirs from TOML doesn't seem to be logged, which is what my local tests confirm).
The option considered in an INI file is called exclude, which is consistent with the docs but inconsistent with what is considered from a TOML (or YAML) file.

Can you share your complete Bandit (and Tox) configuration, please?
Also, can you try to run against . instead of src (which will likely walk directories like .git, .tox and .venv if they are not ignored effectively)?
bandit -c pyproject.toml -r .

Related: #528
And yes, the implementation of the config parsing is super-complicated and probably warrants a complete rewrite. :worried:

I found exclude_dirs it in the code. -x "*/tests/*" from CLI was working so was trying to find out what's different.
pyproject.toml
[tool.bandit]
exclude_dirs = ["*/tests/*"]
skips = ["B410", "B106", "B308", "B703", "B311", "B324", "B105", "B110"]  # just for testing

tox.ini not really using tox. It's just for flake8 config for now
[flake8]
ignore = E203, E501, W503, B950, FS003, S101
max-line-length = 120
per-file-ignores = __init__.py:F401,tests/*.py: S101
exclude = .tox,.git,*/migrations/*,*/static/CACHE/*,docs,node_modules,venv
pytest-mark-no-parentheses = true
pytest-fixture-no-parentheses = true

for testing just created .venv and .tox folders and they are not excluded by defaul. The list of excluded dirs I posted is print(excluded_path_globs) on this line .
To exlude .tox and .venv dirs I have to set:
pyproject.toml
[tool.bandit]
exclude_dirs = ["*/tests/*", "*/.tox/*", "*/.venv/*"]


When can Asp.Net Core support linux-Arm64?

I saw the .Net Core 2.2 preview 3 has pubished last week.but Asp.Net Core still doesn‘t support Arm64.
So I want know when the .Net Core 2.2 stable version release,if it support linux-arm64?
If not,when can Asp.Net Core work on linux-Arm64?
Thank you !

I don't think we announced any official plans/timelines for arm64 Linux support yet.
cc @leecow @vivmishra to confirm

Here's latest official information about arm64: https://github.com/dotnet/announcements/issues/82

I see that dotnetcore runtime works on linux arm64 hardware, but I still see there is no package available for installing aspnetcore runtime on linux arm64. Is aspnetcore supported for linux arm64. If not please suggest any alternative available?
I currently using NVIDIA Jetson Nano board(ARM64,Ubuntu 18.04 OS), trying to run aspnetcore service on this hardware. Please  let me know if there is any support for this ?


API Response Error: Not authorized

Since about yesterday, I can't make any new builds, it fails with:

exp does not even ask for my credentials, although the -c flag is used.
Versions tested are 45.0.2, then 45.1.0, no two factor auth is used.
Any other thing I could do to force exp to ask for my credentials?

Hi @cseelus, please try re-logging in with exp login and see if that fixes your problem.

Thanks @skevy, that did the trick. May be helpful to add that hint to the error from above.


Fix tooltip for entries with no description

When hovering over an entry with no description, tooltip reads "undefined"; should read "(no description)".

Olden UI, closing


Make Track

Make a track or path for player to drive on

If there is a track, we need a cart. Maybe this doesn't need to be done at all.


Missing crypto module when building the project using ncc and Webpack

Hi everyone, this may or may not be an issue with js-ethereum-cryptography itself but rather an issue with @vercel/ncc and webpack builds.  I'm posting it here anyways in case anyone has any ideas on what is going on.
Issue
I have a project that is using a dependency that is dependent on the keccak file from<EMAIL_ADDRESS> I then bunde my project into a single JS file using the ncc build command from this project, which  uses Webpack internally.
Now the issue is that ncc transforms this code to the code below as ncc can't find the crypto package for some reason:
/***/ 84310:
/***/ ((module) => {

function webpackEmptyContext(req) {
	var e = new Error("Cannot find module '" + req + "'");
	e.code = 'MODULE_NOT_FOUND';
	throw e;
}
webpackEmptyContext.keys = () => ([]);
webpackEmptyContext.resolve = webpackEmptyContext;
webpackEmptyContext.id = 84310;
module.exports = webpackEmptyContext;
/***/ }),

This leads to my project crashing with this error when I try run it:
Error: Cannot find module 'crypto'
    at Object.webpackEmptyContext (/Users/christophersastropranoto/Documents/external-adapters-js/packages/sources/layer2-sequencer-health/bundle/index.js:183577:10)
    at /Users/christophersastropranoto/Documents/external-adapters-js/packages/sources/layer2-sequencer-health/bundle/index.js:83270:43
    at Object.78777 (/Users/christophersastropranoto/Documents/external-adapters-js/packages/sources/layer2-sequencer-health/bundle/index.js:83273:3)
    at __nccwpck_require__ (/Users/christophersastropranoto/Documents/external-adapters-js/packages/sources/layer2-sequencer-health/bundle/index.js:183842:43)
    at Object.35681 (/Users/christophersastropranoto/Documents/external-adapters-js/packages/sources/layer2-sequencer-health/bundle/index.js:83194:17)
    at __nccwpck_require__ (/Users/christophersastropranoto/Documents/external-adapters-js/packages/sources/layer2-sequencer-health/bundle/index.js:183842:43)
    at Object.30038 (/Users/christophersastropranoto/Documents/external-adapters-js/packages/sources/layer2-sequencer-health/bundle/index.js:169615:16)
    at __nccwpck_require__ (/Users/christophersastropranoto/Documents/external-adapters-js/packages/sources/layer2-sequencer-health/bundle/index.js:183842:43)
    at Object.55944 (/Users/christophersastropranoto/Documents/external-adapters-js/packages/sources/layer2-sequencer-health/bundle/index.js:168123:14)
    at __nccwpck_require__ (/Users/christophersastropranoto/Documents/external-adapters-js/packages/sources/layer2-sequencer-health/bundle/index.js:183842:43) {
  code: 'MODULE_NOT_FOUND'
}

I've confirmed that this issue is also happening when I try to build the ethereum-cryptography package by itself.
Steps to repro
Run from the root of the ethereum-cryptography repository.

Add @vercel/ncc package yarn add @vercel/ncc
Build the keccak.ts file.  ncc build keccak.js -o bundle/index.js
This should have created a new directory named bundle in the root folder with an index.js file.  Inspect the generated index.js file and find the code below

exports.crypto = (() => {
    const webCrypto = typeof self === "object" && "crypto" in self ? self.crypto : undefined;
    const nodeRequire =  true &&
        __nccwpck_require__(387).bind(module); ------>. The node ID might be different
    return {
        node: nodeRequire && !webCrypto ? nodeRequire("crypto") : undefined,
        web: webCrypto
    };
})();

The module with ID 387 resolves to the code below

/***/ 387:
/***/ ((module) => {

function webpackEmptyContext(req) {
	var e = new Error("Cannot find module '" + req + "'");
	e.code = 'MODULE_NOT_FOUND';
	throw e;
}
webpackEmptyContext.keys = () => ([]);
webpackEmptyContext.resolve = webpackEmptyContext;
webpackEmptyContext.id = 387;
module.exports = webpackEmptyContext;

Expected Behavior
Running ncc build does not generate a webpackEmptyContext function when looking for the crypto module.
Versions
@vercel/ncc: 0.34.0
Any suggestions on what to check are appreciated!  Thanks in advance.

The code is tested with webpack and rollup, so the problem seems to be in your configuration. Report this to NCC.

@paulmillr Hey thanks for responding.  I'll open an issue in NCC but I wanted to mention that I didn't configure anything when I built this project directly.  I just pulled this repo and ran these steps from the root of the ethereum-cryptography repository to check that NCC bundled the project correctly on it's own.

Add @vercel/ncc package yarn add @vercel/ncc
Build the keccak.ts file. ncc build keccak.js -o bundle/index.js
This should have created a new directory named bundle in the root folder with an index.js file. Inspect the generated index.js file and find the code below

exports.crypto = (() => {
    const webCrypto = typeof self === "object" && "crypto" in self ? self.crypto : undefined;
    const nodeRequire =  true &&
        __nccwpck_require__(387).bind(module); ------>. The node ID might be different
    return {
        node: nodeRequire && !webCrypto ? nodeRequire("crypto") : undefined,
        web: webCrypto
    };
})();

The module with ID 387 resolves to the code below
/***/ 387:
/***/ ((module) => {

function webpackEmptyContext(req) {
	var e = new Error("Cannot find module '" + req + "'");
	e.code = 'MODULE_NOT_FOUND';
	throw e;
}
webpackEmptyContext.keys = () => ([]);
webpackEmptyContext.resolve = webpackEmptyContext;
webpackEmptyContext.id = 387;
module.exports = webpackEmptyContext;

@cds95 right -- even if you did not configure anything specifically, vercel/ncc executes some configuration on its own.

Gotcha ok.  I've gone ahead and opened an issue with NCC.


New tests

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+9.002%) to 59.512%

Totals

Change from base Build<PHONE_NUMBER>:
9.002%

Covered Lines:
84

Relevant Lines:
117

💛  - Coveralls


mutliclass

Hi Pratyush Tripathy,
the Landsat-Classification-Using-Neural-Network works very well...Great Work bro......as i was able to adapt it to Sentinel-2 imagery .
The question I have is that have you tested it with a muti-class scenario????

Hi Pratyush Tripathy, the Landsat-Classification-Using-Neural-Network works very well...Great Work bro......as i was able to adapt it to Sentinel-2 imagery . The question I have is that have you tested it with a muti-class scenario????

Hello, I am wondering if you could share your code of implementation to Sentinel-2 with us?


Change old info about pagination to the new one

Can explain what the "new one" is or provide a description?

While the documentation change you made makes sense (from what I can understand), I'd rather see this get built into Draper automatically. For example, automatically adding the delegation if the Kaminari constant is defined or something. This would provide a more friction free experience.
I could make a case for adding this to the documentation until we get that functionality added. However, the documentation you provided isn't entirely complete. The README goes on to mention the PaginatingDecorator reference that you are removing. If you wanted to update all those references, I'd be happy to merge this if we haven't added the functionality by then.


What's the point of the configureSwaggerPaths method?

The documentation only shows how to use it to remove the {format} portion of the path, is there any other point to it?
I always assumed I could use the {format} on the path, to specify more than one format (like json and xml for instance), is that possible?
Thanks

This is handled in #209


Improvement for k8s.io/docs/reference/access-authn-authz/abac/

This is a...

[ ] Feature Request
[ ] Bug Report

Problem:
Proposed Solution:
Page to Update:
https://kubernetes.io/...

Hi @poul22
What improvement to this page did you have in mind?

no save change looking for day furste web traning


Site: Extract site into a separate repository

We added a bunch of dependencies in our monorepo mainly for supporting the build of our site at https://frint.js.org
I suggest extracting the site out into a separate repo, preferably at https://github.com/frintjs/frint.js.org
When doing it, also think of:

removing CNAME from this repo
add CNAME in new repo
Send a PR to dns.js.org: https://github.com/js-org/dns.js.org/blob/789d497df2497650cff2e07a0c4febc831a329fc/cnames_active.js#L334
For API docs, use GitHub API to fetch package READMEs

Internally, we recently had success using FrintJS for building a PoC with routing + server-side rendering. Consider using similar stack for this new website too, to also serve as a living example.

In progress: https://github.com/frintjs/frint.js.org

PR to dns.js.org: https://github.com/js-org/dns.js.org/pull/1538


Community Meeting February 7, 2023

Overview
At 11am Eastern, 8am Pacific, 3pm UTC; find your time
Video call link: https://meet.google.com/mpd-cypd-sdp
Or dial: (DE) +49 30 300195060 PIN: 500<PHONE_NUMBER>#
More phone numbers: https://tel.meet/mpd-cypd-sdp?pin=5005991305702
Or join via SIP<EMAIL_ADDRESS>Meeting recordings available on YouTube at https://www.youtube.com/playlist?list=PLqN7RcoCwL96nXIIW6O51l8Lu_J-f5D27
Incoming issues: https://github.com/orgs/kcp-dev/projects/1/views/22
Milestone epics: https://github.com/kcp-dev/kcp/issues?q=is%3Aopen+is%3Aissue+label%3Amilestone-blocker+label%3Aepic
Add topics you'd like to discuss below!

Workspace Initialization progress.
https://docs.google.com/drawings/d/124_IdF71om1EyKab23RCUwLIx9gUeqSq722lVED7N30/edit


Embed dbt-databricks and databricks-sql-connector versions to SQL comments

Description
Embeds dbt-databricks and databricks-sql-connector versions to SQL comments.

Thanks! merging.


✨ update to use the openshift 3.9. Also using aerogear openshift web

console image
Motivation
The mobile-core was still using the old version of openshift, and the MCP is not relevant anymore.
Description
This PR uses the latest version of openshift (v3.9), and it also removes MCP and uses the openshift web console image instead.
Progress

[x] Finished task

Additional Notes

@maleck13 I fixed the issues you were seeing. can you try again?

@wei-lee not sure if it was introduced in this PR, but installation of oc client v3.9 does not work: https://gist.github.com/psturc/652935248055467ed0c0ed4aabe07e10

First attempt failed on usual step
Error: The `brew link` step did not complete successfully
The formula built, but is not symlinked into /usr/local
Could not symlink bin/oc
Target /usr/local/bin/oc
already exists. You may want to remove it:
  rm '/usr/local/bin/oc'

After executing this everything worked. Continuing tests!

@wei-lee Works like dream with the first start! Awesome work!
I have tested that on mac environment with docker 17.09.0
Going to continue testing metrics and push APB's to make sure that there are no problems with routing etc.
ping @david-martin

going to merge this now and we can address some of the issues in separate PRs. cc @maleck13


STORM-976

I looked through the branch and found some I hadn't noticed before:

logback.xml file under flux is still there.  We could fix this separately in another JIRA since it is external.  If we can fix it now, then that is even better.
FAQ.md already mentions moving to logback from log4j (1.x), so we should update that one part since we have moved again to log4j2.
SECURITY.md also mentions logback in one spot.  We could change it or make it generic.

It would be nice to take care of these three as part of this work, otherwise we can create another JIRA Issue to track.

Thanks for the suggestions. Addressed them in the latest commit. logback.xml is converted to an equivalent log4j2.xml according to their docs.

logback.
log4j2 config.

Passed Travis CI build.
Changing external/flux/flux-core/src/test/resources/logback.xml to log4j2.xml is in accordance with STORM-850 that changed storm-core/test/resources/logback-test.xml to log4j2-test.xml in a similar way.

+1 Looks good to me.

Looks good to me, +1
Thanks @YvonneIronberg

@YvonneIronberg , I did not see an Apache JIRA user name for you, so I have resolved STORM-976 as Unassigned.
If you would like, share your JIRA user name so that we can assign the STORM-976 to you.

Thanks, @d2r! I've assigned STORM-976 to me on Apache jira.


ENV variables?

Hi!
Is have any way to use env variables in swagger.yml?
Thx a lot.

hey,
Unfortunately no. ReDoc is client side lib and has no access to env variables


Add AbiMap and WitnessMap terminology to nargo

Related issue(s)

This is a small refactor that adds AbiMap and WitnessMap it then shows how we convert an AbiMap into a WitnessMap.
Note that if this does not match the way the mapping is done in the evaluator, this will produce errors. This is a separate issue and issues have been opened up for it.
Description
Summary of changes

Dependency additions / changes

Test additions / changes

Checklist

[ ] I have tested the changes locally.
[ ] I have formatted the changes with Prettier and/or cargo fmt with default settings.
[ ] I have linked this PR to the issue(s) that it resolves.
[ ] I have reviewed the changes on GitHub, line by line.
[ ] I have ensured all changes are covered in the description.

Additional context

@kevaundray happy if I take over this PR?

@kevaundray happy if I take over this PR?

Yep, please do


Update Azure AD B2B Limitations documentation

Added additional clarity for distribution lists not being supported instead of assuming reader knows what DL's stands for.

Hi @egbill3eagle, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@egbill3eagle : Thanks for your contribution to the Azure documentation! The author, @viv-liu, has been notified to review your proposed change.

Thanks for the added clarity and keen eye! #sign-off

#sign-off


Notebooks: Clicking Cancel on Add New Connection Dialog Removes Connection

Repro:
Choose SQL kernel, connect to server
Create new cell, execute it
Choose Add new connection from Attach To dropdown
Click cancel on dialog
Attempt to execute same cell again
Cell appears to be running for quite a while, get error when trying to click cancel

No longer repros.


Resize the logo

Currently logo is this huge,

Change the size and add a hover effect on the logo.

Hi Sandhya,
Can you assign this issue to me?

Hi Sandhya,
Can you assign this issue to me?

Sure @greyjedi7

Hi Sandhya,
Can you assign this issue to me?

Sure @greyjedi7

Great. Thanks :)

@2024-SANDHYA , I've made the changes. Kindly review it. If you need changes in the color or hover effect, let me know