Modified the UI of women safety laws, women rights and helpline number pages

Related Issuse or bug

Info about Issue or bug

Fixes: #81
Describe the changes you've made
A clear and concise description of what you have done to successfully close your assigned issue. Any new files? or anything you feel to let us know!
Modified the existing UI and added some pictures to make it look better and made the pages responsive.
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

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

Fix this hover colour issue
Make the Women Helpline page responsive as you have made the other two pages.

@swapnilsparsh I have done all the changes requested by you. Please review the changes.


refactor(Editor): Move editorId from GGEditor into Editor as id

So that we don't need to pass the editorId down the context.

👍


Improve Keylogger

I would like to add email functionality to the keylogger.
For example: after x minutes, send an email with the key logs.

You may go ahead 🚀

Great! I'm working on this under Social Winter of Code (SWC) 2023

Congratulations @deadex-ng
Let's do it 🔥


Switch to published version of web-tree-sitter-0.20.5

A new version of web-tree-sitter has finally been published to NPM!
https://www.npmjs.com/package/web-tree-sitter/v/0.20.5
We should probably keep the machinery for hand rolling our own version around, but we can now switched to simply using the latest published version! (If our tests pass.)

Sounds good! Are we sure we want to keep the hand-rolling machinery around? It will be in the git history if we find we need it again. We could tag the last commit that has it and leave a note in the readme.
I guess if we think it's very likely we'll need it again soon, it's probably worth keeping around, but otherwise I prefer to remove code when we can

I’d no longer suggest this, as web-tree-sitter releases are sparse and not timed with actual tree-sitter releases.


Crash in Flutter app

I was writing a simple demo app. The app allows the user to press buttons and adds text to a Text widget in response. I can't provide a way to replicate the state because I had done at least one hot-reload, but don't know what changed. Below is the content of the Console view in IntelliJ. The app was being run on a Pixel XL.
Performing hot reload...
Reloaded 1 of 467 libraries in 1,055ms.
I/zygote  (16941): Do partial code cache collection, code=30KB, data=29KB
I/zygote  (16941): After code cache collection, code=30KB, data=29KB
I/zygote  (16941): Increasing code cache capacity to 128KB
F/libc    (16941): Fatal signal 11 (SIGSEGV), code 128, fault addr 0x0 in tid 17061 (ui_thread)
I/Choreographer(16941): Skipped 34 frames!  The application may be doing too much work on its main thread.
Application finished.

Is it possible for you to see if this replicates again for you and then maybe give us your demo app and steps you did to replicate the problem.

Given how long we've gone without a repro I don't think this issue retains it's value. Feel free to reopen if we have enough information to investigate.


textcolor crashed in 0.2.0

Example:
#import "@preview/mitex:0.2.0": *
#mitex(`\textcolor{orange}{test}`)

caused this problem:
Unknown variable: tex

Thanks, this is a typo, I've fixed it. It will be fixed in version 0.2.1.
https://github.com/typst/packages/pull/343

Should it close since 0.2.1 is published?

Yes, i will close it.


Create 0000-01-02-cnuehren.md

add slide

Step 8: Merge your pull request
Nicely done @cnuehren! sparkles
You successfully created a pull request, and it has passed all of the tests. You can now merge your pull request.
keyboard Activity: Merge the pull request
1. Click **Merge pull request**

2. Click **Confirm merge**

3. Once your branch has been merged, you don't need it anymore. Click **Delete branch**.

I'll respond when this pull request is merged.

made it


Fix/26431:  Web focus border is not disappearing on click

Details

Web - Focus Border is not disappearing on Click
Fixed Issues

$ https://github.com/Expensify/App/issues/26431
PROPOSAL: https://github.com/Expensify/App/issues/26431#issuecomment-1706236926
Tests

For web/desktop

Open chat, and hover over a chat to get a popup with menu items.
Use Tab/f11 to navigate to that element.
Once it's on Focus click on it, Click multiple times, Click on neighbouring elements,
Observe that the Border should be disappeared after clicking

For other devices

Open chat, click on the composer to bring it into focus
Long press on any report to get the menu items
Choose any emoji
Observe that it works as normal

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

For web/desktop

Open chat, and hover over a chat to get a popup with menu items.
Use Tab/f11 to navigate to that element.
Once it's on Focus click on it, Click multiple times, Click on neighbouring elements,
Observe that the Border should be disappeared after clicking

For other devices

Open chat, click on the composer to bring it into focus
Long press on any report to get the menu items
Choose any emoji
Observe that it works as normal

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Screencast from 19-09-2023 22:09:00.webm

Mobile Web - Chrome

https://github.com/Expensify/App/assets/141406735/10f13d79-d3c7-43a4-a658-4c770ce5b256

Mobile Web - Safari

https://github.com/Expensify/App/assets/141406735/a4c30a7c-0a1a-4eee-b778-892b425ca8a5

Desktop

https://github.com/Expensify/App/assets/141406735/e74d5050-0a51-441a-8452-def39e25d41d

iOS
https://github.com/Expensify/App/assets/141406735/23166bb3-6707-49ab-a8d1-bfe8a244d6fe

Android

https://github.com/Expensify/App/assets/141406735/0a39840e-992e-48f2-abb2-0d2d7cc9dc26

@ArekChr  please help review this one

@DylanDylann Overall, it works, but there is another edge case: when pressing the same emoji which is bordered, the border does not disappear
https://github.com/Expensify/App/assets/24796318/00be96c6-8955-401f-ac38-83bc20ce8c05

@DylanDylann Overall, it works, but there is another edge case: when pressing the same emoji which is bordered, the border does not disappear
web.mov

We can update the onMouseDown listener to:
   onMouseDown={(e) => {
                    if (!ReportActionComposeFocusManager.isFocused() && !ReportActionComposeFocusManager.isEditFocused()) {
                        DomUtils.getActiveElement().blur();
                        return;
                    }

                    e.preventDefault();
                }}

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/24796318/a46bf4f5-89b8-4afd-9441-c4e51b01120a

Mobile Web - Chrome
https://github.com/Expensify/App/assets/24796318/c99c58d2-a5b7-4ff7-a1ca-bed5842141bc

Mobile Web - Safari
https://github.com/Expensify/App/assets/24796318/77e3cd3c-a882-48af-9152-ee0e68aa4db1

Desktop
https://github.com/Expensify/App/assets/24796318/c604159e-7b5d-4eeb-b20d-36461170f4a3

iOS

Android

@jasperhuangg any problem here? Let's merge it

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/jasperhuangg in version: 1.3.74-0 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/chiragsalian in version: 1.3.74-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


New Package: win32_gui

FYI:
win32_gui
Win32 API GUI in Object-Oriented style with some helpers. Uses package win32 and dart:ffi.
https://pub.dev/packages/win32_gui
https://github.com/gmpassos/win32_gui

Is this worth linking from the README?


Post Release -> 0.8.0-SNAPSHOT

For a snapshot version, I think the convention is to use the next patch version, so that would be 0.7.2-SNAPSHOT.

This has not been the convention for this repo, but I agree it's a more sensible rule. Done.


DS-3892 add the findBySchema name method

https://jira.duraspace.org/browse/DS-3892

This is now ready to be reviewed.
Integration Tests are included (also fixing previous test that were flagged as Ignored or inaccurate).
Documentation has been added to the REST contract https://github.com/DSpace/Rest7Contract/blob/master/metadatafields.md
This PR has been rebased on top of #2073 that should be merged asap.
The most relevant change here is commit 6b74ef5 that allows us to specify the precedence between builder to be able to cleanup "complex" context (the metadatafields must be deleted before cleanup the metadataschema to avoid violation of DB constraints)

Hi @tomdesair
I have done the refactor that you have suggested to avoid code duplication.
It seems a good idea to add a "fields" link in the metadataschema HAL document but it is not trivial to do it well so I have created a separate issue for that:
Finally, I have also noted that the MetadataSchemaRestRepositoryIT was named incorrectly (was Metadataschema...) I have renamed it and enable the findOne test that currently success


[Question] How would i clear an layoutContainer

I want to clear and then set a large amount of items into the layoutContainer while only updating the screen once. I was using textArea before but found it ugly. Also, does layoutContainer scroll if it fills to much? Is there already a different "Fancy list" container?

So far there is no function to clear all items of a container or to disable screen updates. I think on Windows it could be implemented by using SendMessage(Handle, WM_SETREDRAW, WPARAM(False), 0);. For Gtk I found no equivalent.
The widget containers automatically provide scrollbars when the minimum size of the child widgets do not fit inside.
Lists are so far missing in NiGui.


Unable to configure TLS for hubble-ui frontend (nginx)

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Currently hubble-ui frontend (nginx) configuration is hardcoded in templates thus it is impossible to reconfigure it to listen on secure port.
expected behaviour:
Hubble-ui frontend (nginx) configuration can be overridden from values file, at least ssl configuration.
Cilium Version
1.13.x, 1.14.x
Kernel Version
N/A
Kubernetes Version
N/A
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

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

Thanks for the report, I think it would make sense to make this configurable.

This is still actual issue, please reopen....


mwc-textfield: problem with focus

Hi...
I'm calling the focus method of the element:
document.getElementById("myTextField").focus()
And I have three problems:

The first time it is executed, the component gets focus correctly, but if I click on other elements, it doesn't blur.
Only works the first time. The next executions don't do anything.
When the component gets focus, the input inside doesn't get the focus (i'm registering a focus event in the input, and it is not fired).

is this the normal behaviour of the focus method?
Thank you.

I'm not able to reproduce this issue with this link that tries to follow your problem: https://jsbin.com/ditakacihe/edit?html,output
I'm able to focus the textfield multiple times, it blurs correctly when I focus the other input (both with keyboard and mouse), and piercing the shadow root reveals that the inner input is receiving focus events.
Can you add a playground link that reproduces the problem?

Hi... thanks for your answer.
I think the problem comes when you try to focus it after enable it.
Look this examples: https://jsbin.com/bagadebolu/edit?html,output
If you click, the textfield is enabled, it is focused (styled), but the
input doesn't get focus, and if you click on the input outside, the
textfield doesn't blur.
Regards.
On Tue, May 5, 2020 at 7:16 PM Liz Mitchell<EMAIL_ADDRESS>wrote:

I'm not able to reproduce this issue with this link that tries to follow
your problem: https://jsbin.com/ditakacihe/edit?html,output
I'm able to focus the textfield multiple times, it blurs correctly when I
focus the other input (both with keyboard and mouse), and piercing the
shadow root reveals that the inner input is receiving focus events.
Can you add a playground link that reproduces the problem?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/material-components/material-components-web-components/issues/1257#issuecomment-624189657,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXC525QTGTE45EZLR3BVHDRQBCWXANCNFSM4MZW2N2A
.

When you set disabled = false, you need to let the element update itself before calling focus. This is because the element updates asynchronously when properties change. You can do that by awaiting the updateComplete promise.
https://jsbin.com/ribelaledi/1/edit?html,output

Now makes sense and its working fine.
I couldn't find any reference about that promise in any documentation.
Thank you very much for the help.
Regards.
On Tue, May 5, 2020 at 9:03 PM Liz Mitchell<EMAIL_ADDRESS>wrote:

When you set disabled = false, you need to let the element update itself
before calling focus. This is because the element updates asynchronously
when properties change. You can do that by awaiting the updateComplete
promise.
https://jsbin.com/ribelaledi/1/edit?html,output
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/material-components/material-components-web-components/issues/1257#issuecomment-624246353,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXC5222ZKDG64FV3PAIUY3RQBPHRANCNFSM4MZW2N2A
.


Random and Intermittent Pods Stuck in ContainerCreating Due to Volumes Not Mounting

Bug Description
We launched a system stress test for lightweight provisioning on a Kubernetes cluster that has 7 worker nodes.
Each deployment launches 1 pod that has 31 pvcs. The pods run a very simple busybox read/write of a 1 meg file.
After 357 total deployments (1 pod each), we see a random set of pods that are in ContainerCreating. They are distributed among all worker nodes. The number of pods with ContainerCreating appears to be decrementing over an extended period of time.

Worker nodes have the following CPU and memory utilization:

The problem does not appear to be stress related.
Deleting the pod results in redeployment, but it is also stuck in ContainerCreating.
Description of pods show the following errors:

What could be causing this?
This stress test is required for CSI 2.0.0.
To Reproduce
Steps to reproduce the behavior:
A stress test of multiple pods each with 31 lightweight pvc should demonstrate this. It is uncertain if other fileset pvc would result in the same thing.
Expected behavior
There should not be any pods stuck in ContainerCreating. If so, a deletion of the pod should cause the deployment to launch one that can run.
Environment
CSI 2.0.0 (Downloaded 5/21/20)

Additional context
A snap of the logs is resident on the system (Archie):
/ibm/fs0/CSI/CSI-2.0.0-tools/ibm-spectrum-scale-csi/tools/ibm-spectrum-scale-csi-logs_05-29-2020-08:17:17

Hi @tristan-le ,
I see following in the logs
ibm-spectrum-scale-csi-vgccn.log:E0529 15:18:00.198231       1 utils.go:55] GRPC error: rpc error: code = Internal desc = ControllerPublishVolume : SKIP_MOUNT_UNMOUNT == yes and either fs0 or fs0 is not mounted on node archieprt05.
So I checked the node mapping, I don't see node mapping for archieprt05 and all the pods you are mentioning are being scheduled on this node itself and CSI Driver is not able to figure out the mount status of fs0 hence the attach is failing.
`  nodeMapping:

k8sNode: archieprt01
spectrumscaleNode: archieprt01-40
k8sNode: archieprt02
spectrumscaleNode: archieprt02-40
k8sNode: archieprt03
spectrumscaleNode: archieprt03-40
k8sNode: archieprt04
spectrumscaleNode: archieprt04-40
k8sNode: archieprt06
spectrumscaleNode: archieprt06-40
k8sNode: archieprt07
spectrumscaleNode: archieprt07-40
k8sNode: archieprt09
spectrumscaleNode: archieprt09-40
scaleHostpath: /ibm/fs0`

I will remedy node mapping for Archie prt05.  I  will double check, but I think that there are other nodes that were mapped that had the same problem.

Changed the cr file and applyied it:
kubectl apply -f csiscaleoperators.csi.ibm.com.cr.yaml
csiscaleoperator.csi.ibm.com/ibm-spectrum-scale-csi configured
[root@archieprt01 CSI-2.0.0-210520] 2020-06-01 06:38:45
date
Mon Jun  1 06:38:48 MST 2020
It looks like only the pods on archiepr05 are the ones still stuck in Container Creating.  We will close this defect later today if we can't recreate.  But I agree that it looks like a miss in the cr yaml

It looks like even though, I fixed the custume resource file, the pods starting on archieprt05 are still stuck in ContainerCreating with the same error.  Do I have to delete the csi driver or anything else to get the volumes to mount?

The POD are still in ContainerCreating because CSI Driver pod is not yet ready.
[root@archieprt01 ~]# kubectl get pod -n ibm-spectrum-scale-csi-driver
NAME                                               READY   STATUS              RESTARTS   AGE
ibm-spectrum-scale-csi-6r2q7                       2/2     Running             0          38m
ibm-spectrum-scale-csi-9dbsf                       2/2     Running             0          38m
ibm-spectrum-scale-csi-attacher-0                  1/1     Running             0          27m
ibm-spectrum-scale-csi-d8zkt                       2/2     Running             0          38m
ibm-spectrum-scale-csi-nbh2r                       2/2     Running             0          38m
ibm-spectrum-scale-csi-operator-74564b7cd9-nxrln   1/1     Running             0          10d
ibm-spectrum-scale-csi-p69cp                       0/2     Terminating         0          10d
ibm-spectrum-scale-csi-provisioner-0               1/1     Running             0          32m
ibm-spectrum-scale-csi-rgvbq                       2/2     Running             0          38m
ibm-spectrum-scale-csi-v2fdt                       2/2     Running             0          38m
ibm-spectrum-scale-csi-vwsqz                       0/2     ContainerCreating   0          38m
Can you please check if there is issue with archieprt05  from Kubernetes side

I have the csi pod correctly running.  I had to reboot archieprt05.  When I rebooted archieprt05, all of the pods that were assignted to archieprt05 moved to other nodes.  Those pods are still stuck in ContainerCreating for the same reason.  I deleted one of those pods so that the deployment would re-launch the pod.  It still has the same problem.
This shows that all nodes have CSI  driver running
[root@archieprt01 ~] 2020-06-01 10:42:37
kubectl get pods -A -o wide | grep csi
ibm-spectrum-scale-csi-driver   ibm-spectrum-scale-csi-6r2q7                       2/2     Running             0          3h49m   <IP_ADDRESS>      archieprt06
ibm-spectrum-scale-csi-driver   ibm-spectrum-scale-csi-9dbsf                       2/2     Running             0          3h49m   <IP_ADDRESS>      archieprt07
ibm-spectrum-scale-csi-driver   ibm-spectrum-scale-csi-attacher-0                  1/1     Running             0          3h38m   <IP_ADDRESS>    archieprt02
ibm-spectrum-scale-csi-driver   ibm-spectrum-scale-csi-d8zkt                       2/2     Running             0          3h49m   <IP_ADDRESS>      archieprt04
ibm-spectrum-scale-csi-driver   ibm-spectrum-scale-csi-nbh2r                       2/2     Running             0          3h49m   <IP_ADDRESS>      archieprt03
ibm-spectrum-scale-csi-driver   ibm-spectrum-scale-csi-operator-74564b7cd9-nxrln   1/1     Running             0          10d     <IP_ADDRESS>    archieprt02
ibm-spectrum-scale-csi-driver   ibm-spectrum-scale-csi-provisioner-0               1/1     Running             0          3h44m   <IP_ADDRESS>   archieprt03
ibm-spectrum-scale-csi-driver   ibm-spectrum-scale-csi-rgvbq                       2/2     Running             0          3h49m   <IP_ADDRESS>      archieprt02
ibm-spectrum-scale-csi-driver   ibm-spectrum-scale-csi-v2fdt                       2/2     Running             0          3h49m   <IP_ADDRESS>      archieprt09
ibm-spectrum-scale-csi-driver   ibm-spectrum-scale-csi-vwsqz                       2/2     Running             0          3h49m   <IP_ADDRESS>      archieprt05
[root@archieprt01 ~] 2020-06-01 10:42:59
kubectl get pods -A -o wide | grep -vi Running | wc -l
30
This shows the deletion of a pod that is stuck in ContainerCreating.
kubectl delete pod -n test89-namespace                test89-busy-write-deployment1-66b85fc444-4vf45
pod "test89-busy-write-deployment1-66b85fc444-4vf45" deleted
The new pods is still stuck in Container Creating:
kubectl describe pod -n test89-namespace     test89-busy-write-deployment1-66b85fc444-rnttd
What should a customer do if they encounter this type of situation?  Should they delete the deployements and pvc's and try again?  How does one recover from this?

The pod mount will be very slow if they encounter such issue. it might take days to mount because for each attach retry time keep increasing exponentially.
To fix the slowness and timeout of attach/detach one has to do following.
Set disable-attach-detach-reconcile-sync flag on the kube-controller-manager to true
After setting to Archie, all pod come into running state without deleting them.
CSI known issue : https://github.com/kubernetes/kubernetes/issues/84169

Thanks Deepak.  How did you know to do this?  Is this knowledge that a good kubernetes admin would know?

I was looking for error which you were facing and I came across issue having same details.
Frankly I am not sure about whether k8s admin will know such things in advance but I feel one with good Kubernetes admin knowledge will easily find out.

Thanks Deepak.  How did you know to do this?  Is this knowledge that a good kubernetes admin would know?

Thanks Deepak.  This answers my questions.  I read the kubernetes post 84169.  After they gave the workaround they said that the behaviour would be fixed in CSI v1.2.0.    Did we get that fix into our CSI 2.0.0?  Am I misunderstanding something?

As per my understanding 84169 is still not completely fixed.  The issue is being fixed at various level(k8s,CSI Spec, External Attacher) so we need keep checking for all pieces to be checked in for complete fix.
FYI : We are using CSI Spec 1.1.0 for 2.0.0.

Great answer. Thanks


JUBE benchmark configuration for CLOUDSC

This brings in the JUBE benchmark configuration for CLOUDSC, simplifying the execution of variants in a standardized fashion on different systems. It is created in a composable way, allowing to override benchmark definitions or configuration values as needed in platform-specific JUBE configurations.
 These have been used for the last cross-platform study for the reporting over the summer.

Thanks for pointing these out, copy-paste left-overs from older toolchain files. Should be cleaned-up now.


ENYO-2496: Updated Drawers logic to use a single universal icon method…

… independent of property states.
Enyo-DCO-1.1-Signed-off-by: Blake Stephens<EMAIL_ADDRESS>

Closing in favor of #2547


static generating is removing invalid html, but not reporting when linting

Environment

Operating System: Linux
Node Version:     v18.20.2
Nuxt Version:     3.11.2
CLI Version:      3.11.1
Nitro Version:    2.9.6
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      vite, css, modules, routeRules, nitro, delayHydration, colorMode, image, components, devtools
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
N/A
Describe the bug
If i have any invalid HTML such as this....

text here

list item here

list item here

or this...

text here

text here

the pre and ul/li tags within the p tag are invalid. And Nuxt Generate will just remove them. But it does report it at any stage to let me know. When running the Lint tool, it is not reported.
Additional context
No response
Logs
No response

To investigate the issue you reported, I would need a reproduction. Are you sure it's Nuxt that is removing the invalid HTML, and not your browser?
But as for ensuring you produce valid HTML, I would recommend using https://github.com/nuxt-modules/html-validator.

it actually removes the elements from the static HTML files generated ( so accessing directly the page URL ) , but not the JS files for Nuxt when you navigate to the page from another.

I'll wait to see your reproduction 🙏

closing for now - please feel free to provide a reproduction and I'll happily investigate 🙏


Unable to decompose signatures into COSMIC for SBS192 or SBS384

Hello,
I've been trying to decompose de novo signatures I extracted from a sample set into COSMIC signatures. SigProfilerAssignment seems to work fine for SBS96 and SBS288 but I get a very different output for SBS192 and SBS384 (which are the most interesting to my goals on this project): the decomposition plots are not plotted and I get this type of "Custom Signature" plot:

I would like to get the regular SigProfilerPlotting plots and the decomposition into COSMIC plots as an output. Is that possible ? I noticed that it wasn't done in the recent re-analysis of PCAWG data that led to new discussions about SBS92, so maybe it is just not possible at the moment?
Thanks for your help and best regards,
Stephane

Hi Stephane,
There are no supported decomposition plots for SBS192 or SBS384 currently. Please update SigProfilerAssignment to v0.0.33, which now has SBS384 de novo signature plots generated using SigProfilerPlotting.
Please reach out again if you have any questions, thanks!

Hi,
Thanks for the answer and the info about the latest update!


Fixing GDB error if ' exists in path

Addresses issue for the C++ Extension
https://github.com/Microsoft/vscode-cpptools/issues/1554

Otherwise LGTM. :shipit:

        if (path.IndexOf(' ') != -1)

Your fix should be here instead

Refers to: src/MIDebugEngine/Engine.Impl/DebuggedProcess.cs:1324 in b673208. [](commit_id = b673208fee7bf2d263f0216098ffcbc32890e600, deletion_comment = False)

Would I also need to add it in https://github.com/Microsoft/MIEngine/blob/d7e8da83d1fa1e719c949bf1f192147e09752160/src/MIDebugEngine/Engine.Impl/DebuggedProcess.cs#L1335
It currently works in VsCode:
1: (1453) <-1012-symbol-list-lines E:\\weirdfolder'\\main.cpp
1: (1454) ->1012^done,lines=[{pc="0x00401460",line="4"},{pc="0x00401471",line="4"},{pc="0x00401476",line="5"},{pc="0x0040149b",line="6"},{pc="0x004014a0",line="7"},{pc="0x004014a8",line="0"},{pc="0x004014ba",line="7"},{pc="0x004014c0",line="7"},{pc="0x004014cf",line="0"},{pc="0x004014e5",line="7"},{pc="0x004014e8",line="7"},{pc="0x004014ee",line="7"},{pc="0x00401504",line="0"}]


Update developer guide for View command

Add implementation, use cases and testing
Add sequence diagram
Remove terms specific to AddressBook

Codecov Report
Base: 74.27% // Head: 74.27% // No change to project coverage :thumbsup:

Coverage data is based on head (18fe909) compared to base (39b05f6).
Patch coverage: 80.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #152   +/-   ##
=========================================
  Coverage     74.27%   74.27%
  Complexity      648      648
=========================================
  Files           102      102
  Lines          1893     1893
  Branches        224      224
=========================================
  Hits           1406     1406
  Misses          422      422
  Partials         65       65

Impacted Files
Coverage Δ

...main/java/tuthub/logic/commands/CommandResult.java
88.00% <80.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Disconnect from attached running process

Hello, I am working on an Visual Studio Code extension where I need to disconnect from the debugging session before the debugging process has finished and I need to do it from within my extension. I was trying to find how to do this by reading this extension's code, however I couldn't find where you contributed the disconnect button when debugging remotely, no was I sure what you exactly call to disconnect. The closest I got was the disconnectRequest function, however I cant find where it gets called. Anyways, my question for you is how can I request the debugger to disconnect from my code?
Edit: Also, how is it that you guys completely change the debug toolbar to have totally different buttons?

just click the stop button, vscode makes it behave differently if the request type is "attach" so it will call disconnect
The toolbar only has what vscode provides, we can't customize that, there is just features you can enable to show some additional built-in buttons like stepping back/running backwards

Just rechecked: you could just send a direct detach via the debugger console (also possible via extension).
@WebFreak001 as the original question was answered a year ago and @kagonzalez seems to be fine with it, can I suggest to close this question-issue?


{monitor-control-service} Data collection migrate

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

monitor-control-service


Point Cloud Capture on Custom Unreal Engine 5 Plugin

| Camera Model                        | D455 |
| Firmware Version                    | 5.15.1 |
| Operating System & Version  | Windows 11 |
| Platform                                  | PC |
| SDK Version                            | Intel® RealSense™ SDK 2.0 (v2.54.2) |
| Language                                |C/C++|
| Segment			         | Unreal Engine 5 /AR/VR |
Issue Description
Hi, I wrote these codes to generate .ply file from captured point clouds but wait_for_frames(30) generate error like screenshot.

These codes is from our custom Unreal Engine 5 plugin. So, OpenGL related samples are not valid for us.
I can see RGB, depth, infrared frames and distance with C API. But we couldn't find any sample about point cloud with C. So, I wrote another one with C++
I can see attached D455's serial number with UE_LOG
I used AsyncTask because we won't trigger point cloud capture in every frame but also we don't want to freeze main/game thread. But I used FRunnableThread for frame streams and its performance is perfect.

void UFF_RealSenseBPLibrary::RealSense_Point_Cloud(FString In_Path)
{
	AsyncTask(ENamedThreads::AnyNormalThreadNormalTask, [In_Path]()
		{
			rs2::context Rs_Context;
			rs2::device_list Rs_Device_List = Rs_Context.query_devices();
			rs2::device Rs_Device = Rs_Device_List[0];
			const char* DeviceInfo = Rs_Device.get_info(RS2_CAMERA_INFO_SERIAL_NUMBER);

			// I can see attached D455's serial number and it is correct.
			UE_LOG(LogTemp, Warning, TEXT("RealSense - Attached camera serial = %s"), *FString(DeviceInfo));

			rs2::config Rs_Config;
			Rs_Config.enable_device(DeviceInfo);

			rs2::pipeline Rs_Pipeline(Rs_Context);
			Rs_Pipeline.start(Rs_Config);

			rs2::frameset Frameset;
			Rs_Pipeline.wait_for_frames(30);

			/*
			* I tried this, too but wait result comes false.
			const std::chrono::steady_clock::duration StartTime = std::chrono::high_resolution_clock::now().time_since_epoch();
			while (std::chrono::duration_cast<std::chrono::milliseconds>(std::chrono::high_resolution_clock::now().time_since_epoch() - StartTime).count() < 30)
			{
				bool WaitResult = Rs_Pipeline.try_wait_for_frames(&Frameset, 30);
				UE_LOG(LogTemp, Warning, TEXT("RealSense - Wait Result = %s"), WaitResult ? *FString("true") : *FString("false"));
			}
			*/

			// Frameset is NULL
			if (!Frameset)
			{
				AsyncTask(ENamedThreads::GameThread, []()
					{
						UE_LOG(LogTemp, Warning, TEXT("RealSense - Frameset is not valid !"));
					}
				);

				return;
			}

			rs2::depth_frame Frame_Depth = Frameset.get_depth_frame();
			if (!Frame_Depth)
			{
				AsyncTask(ENamedThreads::GameThread, []()
					{
						UE_LOG(LogTemp, Warning, TEXT("RealSense - Depth frame is not valid !"));
					}
				);

				return;
			}

			rs2::video_frame Frame_Color = Frameset.get_color_frame();
			if (!Frame_Color)
			{
				AsyncTask(ENamedThreads::GameThread, []()
					{
						UE_LOG(LogTemp, Warning, TEXT("RealSense - Color frame is not valid !"));
					}
				);

				return;
			}

			rs2::pointcloud PointCloud;
			PointCloud.map_to(Frame_Color);
			rs2::points Points = PointCloud.calculate(Frame_Depth);
			Points.export_to_ply(TCHAR_TO_UTF8(*In_Path), Frame_Color);

			Rs_Pipeline.stop();

			AsyncTask(ENamedThreads::GameThread, []()
				{

				}
			);
		}
	);
}

Hi @ffreality  There is a discussion at https://github.com/IntelRealSense/librealsense/issues/4958 about point cloud generation with C language.

Case closed due to no further comments received.


ClientModel: Rework ClientRequestException API

Addresses https://github.com/Azure/azure-sdk-for-net/issues/40562
Note, currently includes changes to Request that are part of https://github.com/Azure/azure-sdk-for-net/pull/40576 -- will need to merge that branch once it goes into the feature branch.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Core


Refactor [bitrise]

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS against e6602e265ebd17cfcc5c50908b0b64df08a4ca69


Mode and topic changes?

Is there any way i can show the IRC's Mode and topic changes? If not, may this be a feature request

Hey! Unfortunately this is not something you can enable in the project at the moment. I'm also now only maintaining discord-irc for bug fixes and vulnerabilities, as I'm no longer an active user of the project. Accordingly, this enhancement is not likely to be added to the project itself any time soon.
This has been requested before, in https://github.com/reactiflux/discord-irc/issues/345 (mode changes) and https://github.com/reactiflux/discord-irc/issues/220 (topic changes), so I'll close this as a duplicate for now.


Group chat capabilities

Currently, Sydney lacks awareness of being in a group chat and mistakenly assumes all messages are from a single person. To improve this, the following implementation can be adopted:

Check each received message to determine if it belongs to a group or a private chat.
If it is a group chat, Sydney should only respond if it is specifically mentioned (e.g., "@Sydney, what time is it?") or if Sydney's previous message was replied to within a thread (AKA the reply functionality in WhatsApp where messages can be threaded).
Sydney should also be aware of the name of the participant who mentioned it, enabling a coherent conversation.

This approach provides a more semantic and intuitive way to refer to the bot whenever you want a response.
Note: Sydney will not actively read every single message in the group to learn about its context, as this is slow and leads to unpredictable behavior.

This originated from #6. Thanks, @Ryzitos!

This originated from #6. Thanks, @Ryzitos!

OMG I THANK YOU, you are literally the best creator on this platform that I have ever been able to talk to and solve my problems, thank you so much ✨✨✨💪💪

Sorry for the question, I'm very new to the GitHub structure in general, but this is a feature that will be implemented, right? (I got confused and thought it had already been released)

Sorry for the question, I'm very new to the GitHub structure in general, but this is a feature that will be implemented, right? (I got confused and thought it had already been released)

Added in 55b92eb.


Use Localization

Currently all content of this mod is hard-coded, which is not very friendly to users of other languages. I hope that these content can be converted to use language files, so that users can submit translations easily.
PS: If this is done, I will submit a Simplified Chinese translation.

thanks for the suggestion

Completed in https://github.com/rfresh2/XaeroPlus/releases/tag/Forge-1.12.2-126
Language files are located here: https://github.com/rfresh2/XaeroPlus/tree/mainline/src/main/resources/assets/xaeroplus/lang
@mczph If you wish to translate please open a PR or DM me the file(s) on discord :)


postgrest on heroku -- issue with crossdomain requests

I am able to run a postgrest server locally. Both the js front end app and the rails app seems to run fine on my local machine, but I'm running into an error when I try to run it on heroku.
I can't seem to get the API to run properly while running the server on Heroku
This is the error I'm receiving:
XMLHttpRequest cannot load https://api.citizensupported.org/user_details?id=eq.2. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://www.citizensupported.org' is therefore not allowed access. The response had HTTP status code 503.
I'm using the button at https://elements.heroku.com/buttons/begriffs/postgrest to deploy the postgrest server -- I think this recently got upgraded to v<IP_ADDRESS>
Any advice?
I'm not sure if I'm following the right approach to running a postgrest server on heroku.

My apologies, the 0.4 version doesn't work with the old heroku buildpack. That's because the buildpack starts the postgrest executable with command line arguments but the new version is expecting a single argument for the config file.
We need to modify the buildpack to create a config file during deployment -- but to do so conditionally if version 0.4 is desired.

gosh, you're a superstar. thanks for responding so quickly.
what's the right way to work around this until you update the build pack?

what else is missing in the fix-0.4 branch?

the button https://elements.heroku.com/buttons/begriffs/postgrest is not present anymore, is this issue still relevant?


az aks install-connector --name not compatible with Helm 3

az aks install-connector as of CLI version 2.10.0, is not compatible with Helm 3.

az aks install-connector --name MyManagedCluster --resource-group MyResourceGroup
It returns error from command line as --name is not supported in Helm 3.

aks

@HuaRUAN Apologies for the delayed response. I was able to use the most recent version  of the CLI with Helmv3. More Info here. Could you please let me know if you still need assistance on this ? Awaiting your reply.

@HuaRUAN I wanted to do quick follow-up to check if you had a chance to look at my above comment. This github issue is open for quite sometime. Please let us know if you need any further assistance on this. Awaiting your reply.


More transformer v2 refactoring

This brings the other transformers in line with yesterday's update and also extracts the entry filtering to its own method.

LGTM but I'll leave the final judgement to @miyunari ;)
Deployed the branch on staging for testing and it seems to run as expected:
https://github.com/redhatcloudx/transformer/actions/runs/5723343231/job/15507786157


Update reference_policies_condition-keys.md

Issue #, if available:
Description of changes:
Adding missing data for the condition key found in other parts of the IAM documentation.
https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_variables.html
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Can you explain what you mean by only using it from the CLI? A condition key is used in a policy. You can create or edit a policy using the AWS Management Console, the AWS CLI, and the SDK that uses the AWS API.
Specifically, if you use the IAM console:

Choose Policies and then choose Create policy.
On the Visual editor tab, choose the EC2 service.
Then choose All EC2 actions (ec2:*).
For the resources, choose All resources.
For the condition, choose Add condition.
In the Add request condtion dialog box, next to Condition key, choose "aws:UserAgent" from the drop-down list.
Complete the fields for the condition and then save the policy.


Suggestion: Set Keras parameters programmatically instead of via JSON

Instead of having users copy over a JSON config file to run a notebook, why not add the following to every lesson:
from keras import backend as K
K.set_image_data_format('channels_last')
K.set_image_dim_ordering('th')
This works for me without any issue while allowing me to preserve my existing Keras config. I'm using a Tensorflow backend on an NVidia GPU.

Using the Keras JSON config file will help change the backend for all the notebooks without the need to edit each one, so I think in general it's more convenient.
Thanks anyway for your suggestion, which could be particularly useful for changing the backend individually for selected notebooks.
As a side note: if I am not wrong, set_image_dim_ordering is obsolete with Keras 2.

Yes, but it overrides existing work spaces, which means if folks already have Keras setups (like I do) I have to back up my existing config and restore it after executing the notebook. It's fine if everyone is going to use AWS EC2 but it's not so great on a local machine that maybe running several notebooks for a myriad array of classes/MOOC etc.
Having these two lines across different notebooks is no different than the duplicate import statements and as you said, also allows students to change the backend (e.g. 'cntk') with very little pain.

Your point is a good one, however I am not sure how many Fastai students have already their personal Keras setups vs how many are just complete beginners. I could put your suggestion in a note and leave up to the users the choice.


Revert "Added make command to help with minor release docs generation"

Reverts aws/eks-distro#1901

Why are we reverting this? If there are problems with it, is there a reason why we cannot fix them? Is the effort too much to fix them in comparison to the benefit we get from this?


ELI5: can't run the code (3. Run the code: '''python import torch, etc...) on python to install # Controlnet - v1.1 - lineart Version

what seems to be the problem?
Also, they've closed my warning issue without resolving it

Can you post the whole error message? Otherwise it is hard to determine what went wrong


test PR with Github API

Please pull this in!

Docs Build status updates of commit 6dcc7c7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

node-azure-tools.md
:white_check_mark:Succeeded

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.


remove useless code

I'm pretty sure there's a couple files that we can just rip out completely, since we're no longer using them. are we using messages.go anymore? same for some buntdb files when we go through with #40

Done with 2c537caacfb276b0348ce9018d64dc6591912992


Fixed streaming distribution remote

The http entity content is an input stream. Calling toString() on it does not return the content of the stream. This issue is fixed by this patch.
Your pull request should…

[ ] have a concise title
[ ] close an accompanying issue if one exists
[ ] be against the correct branch (features can only go into develop)
[ ] include migration scripts and documentation, if appropriate
[ ] pass automated testing
[ ] have a clean commit history
[ ] have proper commit messages (title and body) for all commits
[ ] have appropriate tags applied

@wsmirnow, is this problem specific to develop?

Yes it is. This fix a bug introduced by #1179


Capture stage for MH Birthday 2019

Remove "Mysterious Anomaly" code as it is no longer relevant.

This implementation drops all birthday location hunts not done in one of the 4 rooms.
It's possible we should perform a "cheese check" since the location details / Larry tip strongly suggests that the stage only matters when quest.items.coggy_colby_cheese.status === "active" is true (i.e. non event cheese shares same pool, excepting SB+'s extra mouse.
I have the associated methods available for after prehunt goes live but won't add that until required via merge conflict.

No need for hunt_details that track the upgrade status of the Break Room:
As far as the QuestBirthday2019 data goes, there's only a few properties of use:
bait_warning: bool/null, whether the user is using coggy (null) or other (true)
factory_atts.can_claim: bool/null, whether a cheese crate is ready to be recovered. probably no influence on attraction or loot
factory_atts.boss_warning: bool/null, unclear if this means only Vincent is attractable, or whether Vincent is now in the pool
items.coggy_colby_cheese.status: "active", "disabled", "", depending on if the event cheese is armed, not owned, or just not armed.


No ouput from "query_tweets_from_user"

twitterscraper.query_tweets_from_user('username')
is returning an empty list

Same problem here:
begin_date = dt.date(2021,5,24)
end_date = dt.date(2021,5,25)

limit = 10
lang = 'english'

tweets = query_tweets("notre dame",
                      begindate=begin_date,
                      enddate=end_date,
                     limit=limit,
                     lang = lang)

tweets  is an empty list ---> []

Did you find any alternative for this?

I am getting the same issue as well.

Twitterscrapper doesnt seem to be working anymore, it seems like Twitter banned it. You can use Scweet instead.

This no longer works ... wow, there are a lot of no-longer-functional Twitter scrapers out there :P This is the second one I have come across.

This no longer works ... wow, there are a lot of no-longer-functional Twitter scrapers out there :P This is the second one I have come across.

Can you suggest something that you found usable?

This no longer works ... wow, there are a lot of no-longer-functional Twitter scrapers out there :P This is the second one I have come across.

Can you suggest something that you found usable?

Scweet

This no longer works ... wow, there are a lot of no-longer-functional Twitter scrapers out there :P This is the second one I have come across.

Can you suggest something that you found usable?

I requested for official API access and itworks pretty well

This no longer works ... wow, there are a lot of no-longer-functional Twitter scrapers out there :P This is the second one I have come across.

Can you suggest something that you found usable?

I requested for official API access and itworks pretty well


// Include var Util = require("Util");

Hello !
He miss "Util"

Thanks for reporting the issue. Util has been removed as we are not using that library anymore.


[SPARK-50511][PYTHON] Avoid wrapping Python data source error messages

What changes were proposed in this pull request?

This PR removes the extra try catch during Python data source creation and planning. This is to avoid the redundancy of having During handling of the above exception, another exception occurred:
AnalysisException: [PYTHON_DATA_SOURCE_ERROR] Failed to create Python data source instance: Traceback (most recent call last):
  File "/Users/allison.wang/oss/spark/python/pyspark/sql/worker/create_data_source.py", line 145, in main
    raise PySparkRuntimeError(
             ^^^^^^^^^^^^^^^^^^
  File "/Users/allison.wang/oss/spark/python/pyspark/sql/datasource.py", line 118, in schema
    raise PySparkNotImplementedError(
pyspark.errors.exceptions.base.PySparkNotImplementedError: [NOT_IMPLEMENTED] schema is not implemented.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/allison.wang/oss/spark/python/pyspark/sql/worker/create_data_source.py", line 151, in main
pyspark.errors.exceptions.base.PySparkRuntimeError: [NOT_IMPLEMENTED] DataSource.schema is not implemented.
 SQLSTATE: 38000

Why are the changes needed?

To improve error messages
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing tests
Was this patch authored or co-authored using generative AI tooling?

No

Merged to master.


Remove the synchronized flag of fillInStackTrace method to improve pe…

…rformance while creating exception instance.
Motivation:
Explain here the context, and why you're making that change.
What is the problem you're trying to solve.
Modification:
Describe the modifications you've done.
Result:
Fixes #.
If there is no issue then describe the changes introduced by this PR.

looks good to me


Update index.md

Practice contribution for training purposes.
Added sentence "Microsoft Learn hosts all documentation for Microsoft products and technologies." to line 16, second par.
Contributor guide pull request
Thanks for contributing to the Microsoft Learn contributor guide. Please read these instructions for processing your pull request (PR). Once you've read this text, delete it and write a brief description of the changes you're proposing.
Quality control

[ ] 1. Successful build with no warnings: Review the build status to make sure all checks are green (Succeeded).

[ ] 2. #Sign-off: Once the PR is finalized and ready to be merged, indicate so by typing #sign-off in a new comment in the PR. Signing off means the document is ready for review and can be published at any time.

Merge and publish

All PRs to this repository are manually reviewed and merged.
Once all feedback on the PR is addressed, we'll merge the PR into the main branch.

Need help?

If you have an open PR, tag the PR reviewers in comment with your question: @carlyrevier, @jehchow
Open an issue in this repo and tag the PR reviewers.

Hi @csnoke23 - This looks great! If this were a real PR, someone at Microsoft would start the review process now. Because this is just practice, I'm going to close this. :) Thanks for being a contributor!


Issues with installing to non alpha version

I have been working on a json-server project. I have used a docker image to create the json-server and deploy it. recently, i had issues with my image. after some time, i figured out the problem. since using npm install / yarn add will always install the latest version, that i was using the alpha version of Json-server. I was able to resolve the issue by setting the stable verion of json-server "0.7.4".
The reason why i have opened the issue is that, i wanted to ask, if you can set the stable version to be "0.7.4" in the npm registry. you could still be able use alpha verions by setting it yourself. example: "yarn add json-server@version". In the future of course, you can set it to the stable verion of "1.x"

Completed? https://www.npmjs.com/package/json-server?activeTab=versions says latest is still alpha.23.

I just closed the Issue, since it is not a problem anymore. Thanks for the help


Strong crypto moved to pysnmpcrypto

This PR moves all SNMPv3 crypto features that rely upon crypto primitives that are not available in Python stdlib to the stand-alone and optional package -- pysnmpcrypto.

Looks good to me! Good call on the 5.0.0 jump; that should make for a simpler upgrade break for consumers.


feature: conditional steps are now reviewed by RC008, RC009

Orb version:
v11.1.0 + including v12
What happened:
First described in #128 by @wyardley, run-steps within conditional steps are not checked by RC008 and RC009
Expected behavior:
This is expected to fail RC008 and RC009
steps:
  - checkout
  - restore-deps
  - run: npm run thing1
  - when:
      condition: << parameters.run-thing2 >>
      steps:
        run: npm run thing2

Additional Information:
This PR fixes issue #132

[ps: if you're using conventional / Angular style commits, might wantfeat vs feature]

Your development orb(s) have been published. It will expire in 90 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link(s):
https://circleci.com/developer/orbs/orb/circleci/orb-tools?version=dev:a73a231c27e75c7129bcd93ad7441c8bff9909c8
https://circleci.com/developer/orbs/orb/circleci/orb-tools?version=dev:alpha

Your development orb(s) have been published. It will expire in 90 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link(s):
https://circleci.com/developer/orbs/orb/circleci/orb-tools?version=dev:bbba88cb095d69635b381168271f067fcccd8d3e
https://circleci.com/developer/orbs/orb/circleci/orb-tools?version=dev:alpha


Update underlying Go SDK to v0.6.0 to align with Open API spec

Blocked by a problem with the Fern SDK generation. See https://github.com/hookdeck/hookdeck-go-sdk/pull/9

v0.6.0 has been released https://github.com/hookdeck/hookdeck-go-sdk/releases/tag/v0.6.0


Resident Keys Support?

Thanks for project, it's very helpful!
Do you have any advice on if it's possible somehow to copy resident keys?
e.g.
$ ssh-add -K -v -S /usr/lib/libwindowsfidobridge.so
Enter PIN for authenticator:
debug1: start_helper: starting /usr/lib/openssh/ssh-sk-helper
debug1: sshsk_load_resident: provider "/usr/lib/libwindowsfidobridge.so", have-pin
debug1: sshsk_open: provider /usr/lib/libwindowsfidobridge.so implements version 0x00070000
Provider "/usr/lib/libwindowsfidobridge.so" returned failure -2
debug1: ssh-sk-helper:  sshsk_load_resident failed: requested feature not supported
debug1: ssh-sk-helper: reply len 8
debug1: client_converse: helper returned error -59
Unable to load resident keys: requested feature not supported

Thank you for the kind words!
windows-fido-bridge doesn't support resident keys right now; I haven't looked at adding support, but as far as I know, Windows' WebAuthn API should support it, so there shouldn't be anything preventing it from being implemented in windows-fido-bridge. Unfortunately, I've become quite busy over the past few months, so I likely won't have time to look into it in the near future. I'll keep this open though to gauge interest and to remind myself when I have a free weekend :)

I have to same error when trying to import my resident key from my Yubikey. +1 on this feature

+1 on this

+1 on resident key support

+1 on this


add user profile data

hi sear
i try to add a php file for user profile but its not working
can you pleas tel me how i can do it
my problem ishere

Member only page - Welcome <?php echo $_SESSION['username']; ?></h2
Member only page - Welcome <?php echo htmlspecialchars($_SESSION['username'], ENT_QUOTES); ?>

i need other field from database email and other field sdv
thank you

You are missing the > in your first
prepare('SELECT email FROM members WHERE username = :username');
$stmt->execute(array(':username' => $_SESSION['username']));
$row = $stmt->fetch(PDO::FETCH_ASSOC);

Then use $row['email'] to use it.


Pre and post deploy migrations

Hi all, I have been looking into how we can run some migrations before a service deployment and a few others after a deployment. For example, if you are adding a new column which your service relies on, it makes sense to run this before deploying your service which utilises this column. The same is true for removal of columns, it makes more sense to run that migration once your service has stopped using the column, post deploy.
Not sure where the best place was to post a feature request/ask if this exists? Thanks anyway!
Which version and edition of Flyway are you using?
v8.5.11
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Docker
Which database are you using? (Type & version)
Postgres

Would callbacks (beforeMigrate for example) work?

Closing until further activity


Syntax highlighting fix in mkdocs

Pull Request Test Coverage Report for Build 875614065

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

Totals

Change from base Build 872262025:
0.3%

Covered Lines:
958

Relevant Lines:
1001

💛  - Coveralls


⚠ GitLab Server has degraded performance

In 98a1839, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 11374 ms

Resolved: GitLab Server performance has improved in d747896.


New GCC packaging -- separating compilers from runtime libraries

We've split up the LLVM toolchain in this manner, which has been great for build times and managing complexity. GCC, however, needs the same treatment, however. We should do this for GCC's own sake, and also because not until both toolchains are so cleaned up can we make vast simplifications to cc-wrapper, etc.
The best precedent for how to do this is the Exherbo distro's packaging of GCC:

compiler: https://git.exherbo.org/arbor.git/tree/packages/sys-devel/gcc
libraries: https://git.exherbo.org/arbor.git/tree/packages/sys-libs

There is also https://github.com/richfelker/musl-cross-make, which is doing what we want to do, but in a more BSD-style, one-big-make-invocation manner.
Lastly, there have also been a few attempts in this direction before on the Nixpkgs side:

libgcc: https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/gcc/libgcc/default.nix
libstdc++: https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/{libraries/gcc/libstdc++/5.nix
https://github.com/NixOS/nixpkgs/pull/40637 which does something somewhat like what this issue proposes.

I have been exploring this. After the buildPhase of gcc.cc as it currently exists, all the of the libraries are split apart:
$ pwd
/tmp/build/x86_64-unknown-linux-gnu
$ ls
libatomic  libgcc  libgomp  libitm  libquadmath  libsanitizer  libssp  libstdc++-v3  libvtv

If we are willing to accept having them all built together, then splitting them into separate components at install time wouldn't be hard. We could have each library as a separate output of gcc.cc. At the very least, this would be a step towards fixing a lot of the issues related to using clang with the GNU C++ standard library.
Everything I said above seems kind of obvious, so there must be some reason why it isn't a great idea.

@danielbarter I would like to separate at build time too, because it makes rebuilding cheap. See https://github.com/NixOS/nixpkgs/pull/132343 I just need to get some other things off my plate so I can get back to it.

That makes a lot of sense. I was experimenting a bit more this morning and building the libraries individually is literally 30 seconds on my machine. Building gcc.cc as it exists today is 30 mins!

@Ericson2314 the exherbo links are broken, would you mind reposting them?
I know you sent them to me already; I opened them in the browser on my workstation and then left town and I won't be back for a few days.  I need to stop using browser tabs as my to-do list.

@amjoseph-nixpkgs sure, I will once I get home.
Also, do note I believe this is incremental. The only reason I didn't merge it yet (with the broken libraries removed) is because I was replacing the old libgcc and libstdc++ packages. We could just leave in place instead and then this would be completely standalone, like building the new bridge next to the old bridge that is to be replaced and then demolished.
I suppose that probably is then best route for this, but we can return to it after your boostrap one :).

I finally fixed the links :)


feat: add onChange handler to proxyWithHistory

Add onChange handler for proxyWithHistory to provide a convenient event without setting up a custom subscribe handler.
helpful in a react render to avoid a hacky useEffect
Interface
const Provider = ({ data,  onChange }) ={
   const state = useRef(proxyWithHistory(data, { onChange })).current;

   return (
    <Context.Provider value={state}>
      {children}
    </Context.Provider>
  );
}

This is no longer needed,
the issue was really that in an isolated state, valtio did not start to subscribe therefore, this would still not solve the problem.
Once valtio is able to subscribe then skipSubscribe +  the custom subscribe is a viable solution.


feat: improve response validation error message

Resolves #274

hi @oliverbutler , could you manually add a note that this PR has breaking change for validateResponse API to changelog on https://github.com/ts-rest/ts-rest/releases/tag/v3.26.1 ?
after bumping ts-rest from v3.18.1 to v3.27.0 for https://github.com/msutkowski/ts-rest-hono, i found out that validateResponse no longer worked as it now accepted appRoute instead of responseType. it'd be helpful for adapter authors to let this change of behavior.


C# support

Will there be C# support in the future?

It would be cool, but I'm not a C# dev and it would not feasible for me to try to add official support since that would require rewriting the whole project. If someone else wants to do it, that would be great!

i used unity for 3 years before switching to godot so i have plenty of experience with c#; maybe someday i'll try adding support


Linux Hardened Kernel Updates 2024-12-14

Closes #364251
NOTE: The following common config options have configuration issues on 6.12 hardened and where lowered to mkDefault on common config + option on hardened config:

CONFIG_DRM_PANIC_SCREEN_QR_CODE
CONFIG_RUST
CONFIG_SCHED_CLASS_EXT

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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.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

[x] Fits CONTRIBUTING.md.

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

What is the issue with sched ext?

Unsure, haven't been able to look at it in detail

I also tried running these changes on v6.12, and I haven't had any issues with it running.
I am however confused by all of the changes to the kernel config. I see the comment Use a lower priority to allow these options to be overridden in hardened/config.nix, but as far as I can tell you're just setting the same the value in both places. If that is the case, would it not be better to not make unnecessary changes?
It seems like maybe the two Rust related config options might actually cause problems to be configured for the hardened profile unconditionally because they are only conditionally defined in the common config.

Those are not the same option yes and yes are different in one regard: one will fail if it cannot be set during config.
As to not change the semantics of the common config but hardened being unable to config with yes hardened ended up with option yes.

I see that now. I was not familiar with that difference in syntax. Thanks for the clarification and figuring this out!

Created a followup tracking issue: https://github.com/NixOS/nixpkgs/issues/365700


beets-check plugin's tests are broken

Describe the bug

running install tests
/nix/store/4kpxs30zfpq2650jnlgcyb5i98nmmh33-beets-unstable-2021-01-29/lib/python3.8/site-packages/beets/mediafile.py:21: UserWarning: beets.mediafile is deprecated; use mediafile instead
  warnings.warn("beets.mediafile is deprecated; use mediafile instead")
............................EE............
======================================================================
ERROR: test_convert_command (test.integration_test.ConvertTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/build/source/test/integration_test.py", line 185, in test_convert_command
    beets.ui._raw_main(['convert', 'ok.ogg'])
  File "/nix/store/4kpxs30zfpq2650jnlgcyb5i98nmmh33-beets-unstable-2021-01-29/lib/python3.8/site-packages/beets/ui/__init__.py", line 1264, in _raw_main
    subcommand, suboptions, subargs = parser.parse_subcommand(subargs)
  File "/nix/store/4kpxs30zfpq2650jnlgcyb5i98nmmh33-beets-unstable-2021-01-29/lib/python3.8/site-packages/beets/ui/__init__.py", line 1094, in parse_subcommand
    raise UserError(u"unknown command '{0}'".format(cmdname))
beets.ui.UserError: unknown command 'convert'
-------------------- >> begin captured logging << --------------------
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: no user configuration found at /build/tmpvcmt5spe/config.yaml
beets: DEBUG: data directory: /build/tmpvcmt5spe
beets: DEBUG: plugin paths:
beets: DEBUG: Sending event: pluginload
beets: DEBUG: library database: /build/tmpvcmt5spe/library.db
library directory: /build/tmpvcmt5spe/libdir
beets: DEBUG: Sending event: library_opened
--------------------- >> end captured logging << ---------------------

======================================================================
ERROR: test_update_after_keep_new_convert (test.integration_test.ConvertTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/build/source/test/integration_test.py", line 192, in test_update_after_keep_new_convert
    beets.ui._raw_main(['convert', '--keep-new', 'ok.ogg'])
  File "/nix/store/4kpxs30zfpq2650jnlgcyb5i98nmmh33-beets-unstable-2021-01-29/lib/python3.8/site-packages/beets/ui/__init__.py", line 1264, in _raw_main
    subcommand, suboptions, subargs = parser.parse_subcommand(subargs)
  File "/nix/store/4kpxs30zfpq2650jnlgcyb5i98nmmh33-beets-unstable-2021-01-29/lib/python3.8/site-packages/beets/ui/__init__.py", line 1094, in parse_subcommand
    raise UserError(u"unknown command '{0}'".format(cmdname))
beets.ui.UserError: unknown command 'convert'
-------------------- >> begin captured logging << --------------------
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: Sending event: database_change
beets: DEBUG: no user configuration found at /build/tmp8xd7b829/config.yaml
beets: DEBUG: data directory: /build/tmp8xd7b829
beets: DEBUG: plugin paths:
beets: DEBUG: Sending event: pluginload
beets: DEBUG: library database: /build/tmp8xd7b829/library.db
library directory: /build/tmp8xd7b829/libdir
beets: DEBUG: Sending event: library_opened
--------------------- >> end captured logging << ---------------------

Name                 Stmts   Miss  Cover
----------------------------------------
beetsplug/check.py     316     19    94%
----------------------------------------------------------------------
Ran 42 tests in 8.415s

FAILED (errors=2)
builder for '/nix/store/1wjywzypgl7y0fg7b1aq0z93j028rym6-beets-check.drv' failed with exit code 1
error: build of '/nix/store/1wjywzypgl7y0fg7b1aq0z93j028rym6-beets-check.drv' failed

Notify maintainers

@lovesegfault
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: beets
# a list of nixos modules affected by the problem
module:

Removed in a2492b0831915aa9a24cdc4ff96b1288241898c7.


update RGT logo

I want this to manually update. @keone plase kindly consider this request.

https://github.com/solana-labs/token-list/commit/c38157bb93cd411ed633686ea783f0d0cecaf66f


Need to register turn runner

I'd like to use turn as my global test runner (i.e. the runner I set in my global .test-unit.yml file), but it doesn't appear that turn registers itself as a runner via AutoRunner.register_runner.

Turn 0.x series will not support Test::Unit 2. But next major series will (may skip to 2.x just to make it very clear). When that happens this issue will be resolved.


Refactor of auth hash method changes auth.info content in custom strategy

Hi,
I've tried to search before and I can't find similar issues. I also don't know if this is an issue with OmniAuth or with the custom strategy, but I think that this could be brought to your attention.
I've tried to update omniauth-cas to OmniAuth 2, but I've got an unexpected error introduced by 7f20a03d92298f59e2f570061498a1d188713f22
If I change the code to the previous version or to:
     def auth_hash
+      info_data = info unless skip_info?
       credentials_data = credentials
       extra_data = extra
       AuthHash.new(:provider => name, :uid => uid).tap do |auth|
-        auth.info = info unless skip_info?
+        auth.info = info_data if info_data
         auth.credentials = credentials_data if credentials_data
         auth.extra = extra_data if extra_data
       end

specs pass again
Configuration

Provider Gem: omniauth-2.0.3
Ruby Version: 2.7.2
Framework: n/a
Platform: macOS

Expected Behavior
The refactor does not change the previous behavior
Actual Behavior
The refactor changes auth.info behavior
Steps to Reproduce

git clone https://github.com/dlindahl/omniauth-cas.git
Relax omniauth dependency in gemspec to allow 2.0
rspec ./spec/omniauth/strategies/cas_spec.rb[1:4:3:1:1:3:4:1]

Failure/Error: expect(subject.name).to eq 'Peter Segel'

       expected: "Peter Segel"
            got: "psegel"

       (compared using ==)

Ref:

#1000
7f20a03d92298f59e2f570061498a1d188713f22
dlindahl/omniauth-cas#62

Hi,
I have an update
This is caused by the custom strategy, which performs a destructive operation on raw_info.
Since extra is now assigned after info, the data in info is not available anymore
https://github.com/dlindahl/omniauth-cas/blob/4ab8a1c9c3333223a547cdd266679b9edf3a0f58/lib/omniauth/strategies/cas.rb#L65-L69
I'm going to close this issue, because the problem should be solved in the custom strategy


#3036 unable to view the 5th page of account activities

General
Closes #181
A variable was not declared. I found it commented declaration in the ProposedOperation.jsx
General
Please make sure the following is done:

Pull request is onto develop
If you haven't already, have a look at

https://github.com/bitshares/bitshares-ui/blob/develop/CODE_OF_CONDUCT.md
https://github.com/bitshares/bitshares-ui/blob/develop/CONTRIBUTING.md

Code Preparation
Please review all your changes one last time before committing

[ ] Check for unused code
[ ] No unrelated changes are included
[ ] None of the changed files are reformatting only
[ ] Code is self explanatory or documented
[ ] All written text is properly translated (english language)

Testing
The branch has been tested on the following browsers (desktop and mobile view)

[ ] Chrome
[ ] Opera
[ ] Firefox
[ ] Safari

User interface changes
Delete this section if there weren't any UI changes. Please make sure you tested your changes in all themes

[ ] Dark
[ ] Light
[ ] Midnight

Please provide screenshots/licecap of your changes below

Accepted


Remove "match-all" and "list" schema options

These options were added a long time ago but they were never documented. As far as I can tell, nobody even knows they exist but I want to check here to see if anyone uses them before we deprecate them.
It appears that match-all is intended to override the default schema (1m for 1w), although I believe most people just use pattern = .* for this instead. I suspect that this option was more relevant back when priority existed.
The list option continues to remain a mystery to me since there's no examples of how it should actually be used.
/cc @nleskiw @drawks @mleinart @jssjr @cdavis

:thumbsup:
On Jan 25, 2015 4:57 PM, "Jason Dixon"<EMAIL_ADDRESS>wrote:

These options were added a long
https://github.com/graphite-project/carbon/commit/401f0436f2eabd2e3122fa297bc3234bfe399f68
time
https://github.com/graphite-project/carbon/commit/59b410cf22ee0fccb3d73aff40c001d9be113c58
ago but they were never documented. As far as I can tell, nobody even knows
they exist but I want to check here to see if anyone uses them before we
deprecate them.
It appears that match-all is intended to override the default schema
https://github.com/graphite-project/carbon/blob/master/lib/carbon/storage.py#L193
(1m for 1w), although I believe most people just use pattern = .* for
this instead. I suspect that this option was more relevant back when
priority existed.
The list option continues to remain a mystery to me since there's no
examples of how it should actually be used.
/cc @nleskiw https://github.com/nleskiw @drawks
https://github.com/drawks @mleinart https://github.com/mleinart @jssjr
https://github.com/jssjr @cdavis https://github.com/cdavis
—
Reply to this email directly or view it on GitHub
https://github.com/graphite-project/carbon/issues/370.

:+1:


Added command to download kubectl via curl

If there's a variable to automatically have the docs show the current/stable release I can put that in the command instead of ${K8S_VERSION}.

This change is

Thanks, @rothgar!

This looks better now IMO.
Feedback welcome.


Azure DevOps support

Great job on creating this repo and getting it to this amazing point!
Not an issue but rather a question.
Any plans on supporting Azure DevOps Pipelines as well?
@joselcaguilar @bahramr
Thanks!

great question @akulich . We got someone signup to help us add ADO pipelines today. we should be showing some progress there soon.

Agreed, we don't use Github


Better documentation on actions

@jcchavezs Can you provide a description here so it can be picked by others?


[CT-1412] test_aliases functional test hanging artifacts

resolves #360
Description
Fix issue where alt test project has hanging dataset/table
spike doc: https://www.notion.so/dbtlabs/Bigquery-Leftover-tests-artifacts-350aa89a047f44b3b3b1967aaff8367e
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[ ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[ ] I have run changie new to create a changelog entry

@McKnight-42 With https://github.com/dbt-labs/dbt-bigquery/issues/360 resolved, is this pull request still relevant? Or can it be closed?

@McKnight-42 With #360 resolved, is this pull request still relevant? Or can it be closed?

I saw your note here with the explanation 👍


Some objects were not cleaned up when closing the scene.

I get this message when we load a new scene in our game.

Some objects were not cleaned up when closing the scene. (Did you spawn new GameObjects from OnDestroy?)

I have a basic camera rig, two controllers hooked up using the SteamVR_Behaviour_Pose behavior to left and right hands. And a head gameobject connected using the old SteamVR_TrackedObject behavior  set to HMD.
Other than that its same logic as before SteamVR 2.0 Have only ported our own abstraction to use the new action SDK

Found the problem. SteamVR_Camera behaviour causes this. Removed it since it's not needed in SteamVR 2?

I believe this has been fixed in recent betas (by not using the camera as you suggest): https://github.com/ValveSoftware/steamvr_unity_plugin/releases/tag/2.2b1


BUG: Difference between macs2 and genrich pileup

For single-end data they seem to be the same :tada:

https://github.com/jsh58/Genrich/issues/39


pagination_per_day_date.py:46: реализовать парсинг даты...

The puzzle 1213-3d56c788 from #1213 has to be resolved:
https://github.com/blablatdinov/tg-quranbot/blob/3d156d0f62748d1a643d6ce7f8957b012f862f57/src/srv/prayers/pagination_per_day_date.py#L46-L46
The puzzle was created by Ilaletdinov Almaz on 02-Sep-24.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 1213-3d56c788 has disappeared from the source code, that's why I closed this issue.

@0pdd the puzzle #1232 is still not solved.

@0pdd the only puzzle #1232 is solved here.


Tag v2.16.0 lists version 2.15.1 in stl/about.py

Looks like you tagged v2.16.0 before bumping the version in stl/__about__.py:
https://github.com/WoLpH/numpy-stl/blob/v2.16.0/stl/__about__.py#L3

Sorry about this extremely slow response... for some reason it seems that the deploy script I'm using has a bug and creates the tag before committing.
I'm not sure what's causing the issue though... the release on pypi is correct and the local tag files I have appear correct too.


OAS type inconsistency

I have noticed a type inconsistency between the OAS docs for the API and the actual usage and example usage of the API.
This is based on the current API spec at https://github.com/FusionAuth/fusionauth-openapi/blob/master/openapi.yaml
This same issue appears across multiple components but for a concrete example in the User component expiry field:
expiry:
"$ref": "#/components/schemas/ZonedDateTime"
The field reference is for a type of ZonedDateTime but the actual type is a numeric (long)
In the example response displayed on this page - https://fusionauth.io/docs/v1/tech/apis/users#reactivate-a-user - you can see that "expiry" is in fact numeric with no timezone representation and not a ZonedDateTime

When using a typed domain such as Java - we do use a ZonedDateTime for all instants which are serialized and de-serialized as an 8 byte integer (long).
I am not an OpenAPI expert, so perhaps I need to do some more research, but since that is a component ref and we do define that component as a 64 bit integer, it seems correct to me.
ZonedDateTime:
  description: A date-time with a time-zone in the ISO-8601 calendar system, such
        as 2007-12-03T10:15:30+01:00 Europe/Paris.
  example: '2007-12-03'
  type: integer
  format: int64

Are you suggesting it would be better if we replaced this
insertInstant:
  $ref": "#/components/schemas/ZonedDateTime"

with this?
insertInstant:
  type: integer
  format: int64

I think there is some benefit to describing these fields as a zoned date / time because it provides some additional context to the type of 8 byte integer we are expecting.

I think the description is incorrect though. That should state that the ZonedDateTime is always Epoch Milliseconds UTC since longs don't have a timezone component.
Is that what you were referring to @JohnCarrollSplit?

Yea, the description is off, I think what you said makes sense though, just describe it as always having the timezone UTC when represented as a long

Fixed under https://github.com/FusionAuth/fusionauth-client-builder/pull/48
Closing.


Labs 2.0 - Menu add-on Proxy

Menu add-on Proxy for all the labs
For the labs we want to add a light weight browser proxy to be able to modify the requests in the browser itself without the need to setup a local HTTP intercepting proxy. The last request done from the application point of view would be visible in the HTTP proxy tab, for example:

From here the user can already modify the content, headers, cookies, GET, POST and so on to make it easier to start testing properly using only the browser as a tool.

Some of the labs still require Burp though, e.g. the ones that need automation and fuzzing. I understand you'd like to make things easier for some labs, but you're already a very busy person :D


Create an tokenizer & lexer

First thing we need is to tokenize the input files and do lexical analysis on them, which is done in the masm-lexer crate.
This is almost done, only small changes need to be made (see comments)

[ ] LexError should be added for unclosed string errors.
[ ] SingleQuote and DoubleQuote should be removed, quote info should be in the DoubleQuoteString and SingleQuoteString types.

[ ] start and end should be replaced with a struct allowing a line, column and an offset, so errors can read current position.


Nippy performance: disable compression but keep header

In reference to #168:
This commit benefits performance (esp. write performance) over a possible minor increase
in serialized data size  (usu. <5% extra size).
Note that by keeping the header, we retain the option of changing compression
strategies later in a fully back and forward compatible way.

NetflixOSS » PigPen » PigPen-pull-requests #14 SUCCESS
This pull request looks good


Where to use "log_stream" variable?

As far as I reviewed the code, there is no resource associated with "log_stream" variable? Why is it exist and required?

Thanks it must have been some remnant of old usage.


Update Song “2023-04-10/index”

Automatically generated by Netlify CMS

👷 Deploy Preview for netlify-nhom-6 processing.

Name
Link

🔨 Latest commit
b659665eb94717092866bdf78684c16ca724ed94

🔍 Latest deploy log
https://app.netlify.com/sites/netlify-nhom-6/deploys/66cf48617774fa0008067653


[Bug report] Some codes are missing when python pip download

line 1070 ~ 1078 are missing in elastalert.py

Can you elaborate on what the problem is? .. I'm not sure.


Version 5 error

Just upgraded from v4.3.1 to v5 and the web developer console report this, just loading the file:
pixi-sound.js:8
Uncaught TypeError: Cannot read properties of undefined (reading 'High')
at pixi-sound.js:8:31811
at pixi-sound.js:8:32482
The library is loaded via CDN:

I just noticed the releases page, ok.
But is there a blog, a new section where breaking changes are announced ?

Info is on the releases page, which has the relevant changes. Are you using PixiJS v7?

No I'm on Pixi 6.5.4
I made the error to link to the latest pixi/sound version, without considering that it could have breaking changes.
I'm now specifying the version and looking to upgrade to 7 when out of alpha.
Thank you.


Add before/after/error handlers for Das extensions

I don't know why the JsonBuilder change is still showing, sorry about that.
I've added an interface called IRestServiceExt that allows for before/after/error handlers for DasService extensions. This way processes that need to do special things at the start and end of thread processing (like the ODA does) can define those hooks while retaining all the Das goodness.

Thanks for the contribution, we will review it for the next OpenNTF release and be in touch.
Padraic

Please note the addition of a change to the manifest.mf. The @PATCH method was not being exported. This is very difficult to diagnose in DAS extensions.

Code delivered to v17