refactor: export every utils types and functions

The purpose of this PR is to export all types and functions that are exported from their file. So that new types and functions are also exported

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Syllabus - Class canceled on Monday 2/16

We have class now, correct?

Yes that is correct.

b635dd9 resolved this.


[Draft]Updated audio notification to handle failures

Thank you for your contribution. Before submitting this PR, please include:
Id of the task, bug, story or other reference.
Description
Include a description of the problem to be solved
Solution Proposed
Detail what is the solution proposed, include links to design document if required or any other document required to support the solution
Acceptance criteria
Define what are the conditions to consider the PR has achieved the intended goal
Test cases and evidence
Include what tests cases were considered, any evidence of testing for future references, to identify any corner cases, etc
Sanity Tests

[ ] You have tested all changes in Popout mode
[ ] You have tested all changes in cross browsers i.e Edge, Chrome, Firefox, Safari and mobile devices(iOS and Android)
[ ] Your changes are included in the CHANGELOG

A11y

[ ] You have run the Automated Accessibility Check and have no reported issues

Please provide justification if any of the validations has been skipped.

Modern browsers dont allow the auto-play until there is a user interaction on the window. Try granting the autoplay permissionspolicy to grant the autoplay support to the iframe containing the livechatwidget. This may be blocking the playback and thus the error above. Please refer to: https://developer.mozilla.org/en-US/docs/Web/Media/Autoplay_guide#:~:text=Autoplay availability,and its document Opens in new window or tab. Since I am unable to reproduce this scenario, the DOMexception will be a bandaid fix which is not a good solution. This is certainly needs to be handled on the portal side.


Autobuy failed at last step

Hi.
Using a Mac, and ran the latest commit for
whole_foods_delivery_autobuy.py
(3d289a8f13aadd2f9f29e042dcddc4adee4f1187)
It worked well, except when it got to the end, it did not perform the final click for "place order." I had to do it manually (manual click worked, and order was placed).
This is what was shown on the screen as the script was running:
refreshed
SLOTS OPEN! 2
Clicked open slot
Selected slot and continued to next page
Payment method selected
Found a slot but it got taken, run script again. 2

Note that I added the "2" after "Found a slot but it got taken, run script again." on line 79 so I could tell where the script stopped.

Ah! Thank you for writing down the issue so well! It worked for me a while back. Did it work for you after this try?

Hi. This happened on 4/27 using the latest code. I haven't tried it since (maybe I'll order again this week or next).
I noticed that you commented out lines 59, 67 and 71 in favor of lines 60, 66, and 72, respectively. I wonder if that has something to do with it, or whether this issue I had was a fluke. I'll let you know what happens when I try running it again.


Calendar / Datepicker not available

Hello,
Is that the integration in F7-Vue of the calendar/datepicker component is planned ?
Thank's !

No plans at the moment, as they are mostly just JS components, but will think about it

Ok, no problem. I'm going to try using the calendar JS component in a F7-Vue page.
I keep you in touch.


fix: update controls with rule that make use of KubeletInfo

Overview
This PR update controls that were using legacy resources (KubeletCommandLine, KubeletConfigurations) with the updated rules that makes use of KubeletInfo.
Additional Information
Here are the commands that I used.
Which are the legacy rules? (rules that still use KubeletCommandLine and KubeletConfigurations):
grep -E 'KubeletConfiguration|KubeletCommandLine' -rnw rules/ -l | grep raw.rego | cut -d '/' -f2

Are they used in some control? (apparently not, since all the rules found with this command ends with -updated):
for rule in $(grep -E 'KubeletConfiguration|KubeletCommandLine' -rnw rules/ -l | grep raw.rego | cut -d '/' -f2); do grep -rnw controls/ -e $rule ; done

Related issues/PRs:
Related PRs:

https://github.com/kubescape/host-scanner/pull/46
https://github.com/kubescape/kubescape/pull/1247
SUB-1078

Checklist before requesting a review
put an [x] in the box to get it checked

[x] My code follows the style guidelines of this project
[ ] I have commented on my code, particularly in hard-to-understand areas
[x] I have performed a self-review of my code
[ ] If it is a core feature, I have added thorough tests.
[x] New and existing unit tests pass locally with my changes

Great. Let's delete the 4 old rules so we don't use them by accident, wdyt?

Great. Let's delete the 4 old rules so we don't use them by accident, wdyt?

Yes, totally agree


idea: Highlighting the HTTP API Spec on Apiary

Idea: Let's have a blogpost about the HTTP API Spec currently up on Apiary.
Writer: @RichardLitt

Started!


IOS PROBLEM: Invariant Violation: Invariant Violation: [....

After installing on iOS simulator I see this error:
Invariant Violation: Invariant Violation: [177,"RCTView",1,{"height":56,"width":56,"borderRadius":28,"backgroundColor":4294185791,"shadowColor":4278190080,"shadowOpacity":0.3,"shadowRadius":"<>","shadowOffset":{"height":1,"width":0},"zIndex":1}] is not usable as a native method argument
This error is located at:
in RCTView (at View.js:45)
in View (at ActionButton.react.js:337)
in RCTView (at View.js:45)
in View (at createAnimatedComponent.js:151)
in AnimatedComponent (at ActionButton.react.js:464)
in ActionButton (at withTheme.js:12)
in ThemedComponent (at TaskList.js:594)
in RCTView (at View.js:45)
in View (at TaskList.js:592)
in RCTView (at View.js:45)
in View (at TaskList.js:515)
in TaskList (created by ConnectFunction)
in ConnectFunction (at ToDo.js:59)
in tasks (created by SceneComponent)
in SceneComponent (at SceneMap.tsx:16)
in RCTView (at View.js:45)
in View (at SceneView.tsx:92)
in SceneView (at TabView.tsx:165)
in RCTView (at View.js:45)
in View (at createAnimatedComponent.js:217)
in AnimatedComponent (at Pager.tsx:667)
in PanGestureHandler (at Pager.tsx:659)
in Pager (at TabView.tsx:126)
in RCTView (at View.js:45)
in View (at TabView.tsx:125)
in TabView (at ToDo.js:50)
in RCTView (at View.js:45)
in View (at Template.js:56)
in Template (created by ConnectFunction)
in ConnectFunction (at ToDo.js:49)
in ToDo (created by ConnectFunction)
in ConnectFunction (at SceneView.js:9)
in SceneView (at StackViewLayout.tsx:899)
in RCTView (at View.js:45)
in View (at createAnimatedComponent.js:151)
in AnimatedComponent (at StackViewCard.tsx:93)
in RCTView (at View.js:45)
in View (at createAnimatedComponent.js:151)
in AnimatedComponent (at screens.native.js:59)
in Screen (at StackViewCard.tsx:80)
in Card (at createPointerEventsContainer.tsx:95)
in Container (at StackViewLayout.tsx:971)
in RCTView (at View.js:45)
in View (at screens.native.js:83)
in ScreenContainer (at StackViewLayout.tsx:383)
in RCTView (at View.js:45)
in View (at createAnimatedComponent.js:151)
in AnimatedComponent (at StackViewLayout.tsx:379)
in PanGestureHandler (at StackViewLayout.tsx:372)
in StackViewLayout (at withOrientation.js:30)
in withOrientation (at StackView.tsx:103)
in RCTView (at View.js:45)
in View (at Transitioner.tsx:267)
in Transitioner (at StackView.tsx:40)
in StackView (at createNavigator.js:61)
in Navigator (at createKeyboardAwareNavigator.js:12)
in KeyboardAwareNavigator (at createAppContainer.js:429)
in NavigationContainer (at App.js:59)
in Provider (at App.js:57)
in App (at withExpoRoot.js:20)
in RootErrorBoundary (at withExpoRoot.js:19)
in ExpoRootComponent (at renderApplication.js:35)
in RCTView (at View.js:45)
in View (at AppContainer.js:98)
in RCTView (at View.js:45)
in View (at AppContainer.js:115)
in AppContainer (at renderApplication.js:34)
And this one:
Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in %s.%s, the componentWillUnmount method,
in Icon (at Icon/index.js:79)
in Icon (at withTheme.js:12)
in ThemedComponent (at TaskList.js:551)
in RCTView (at View.js:45)
in View (at createAnimatedComponent.js:151)
in AnimatedComponent (at TaskList.js:550)
in RCTView (at View.js:45)
in View (at TaskList.js:543)
in RCTView (at View.js:45)
in View (at createAnimatedComponent.js:151)
in AnimatedComponent (at TouchableOpacity.js:282)
in TouchableOpacity (at ModalDropdown.js:170)
in RCTView (at View.js:45)
in View (at ModalDropdown.js:114)
in ModalDropdown (at TaskList.js:526)
in RCTView (at View.js:45)
in View (at createAnimatedComponent.js:151)
in AnimatedComponent (at CenterElement.react.js:166)
in TouchableWithoutFeedback (at CenterElement.react.js:165)
in CenterElement (at withTheme.js:12)
in ThemedComponent (at Toolbar.react.js:464)
in RCTView (at View.js:45)
in View (at createAnimatedComponent.js:151)
in AnimatedComponent (at Toolbar.react.js:450)
in Toolbar (at withTheme.js:12)
in ThemedComponent (at TaskList.js:516)
in RCTView (at View.js:45)
in View (at TaskList.js:515)
in TaskList (created by ConnectFunction)
in ConnectFunction (at ToDo.js:59)
in tasks (created by SceneComponent)
in SceneComponent (at SceneMap.tsx:16)
in RCTView (at View.js:45)
in View (at SceneView.tsx:92)
in SceneView (at TabView.tsx:165)
in RCTView (at View.js:45)
in View (at createAnimatedComponent.js:217)
in AnimatedComponent (at Pager.tsx:667)
in PanGestureHandler (at Pager.tsx:659)
in Pager (at TabView.tsx:126)
in RCTView (at View.js:45)
in View (at TabView.tsx:125)
in TabView (at ToDo.js:50)
in RCTView (at View.js:45)
in View (at Template.js:56)
in Template (created by ConnectFunction)
in ConnectFunction (at ToDo.js:49)
in ToDo (created by ConnectFunction)
in ConnectFunction (at SceneView.js:9)
in SceneView (at StackViewLayout.tsx:899)
in RCTView (at View.js:45)
in View (at createAnimatedComponent.js:151)
in AnimatedComponent (at StackViewCard.tsx:93)
in RCTView (at View.js:45)
in View (at createAnimatedComponent.js:151)
in AnimatedComponent (at screens.native.js:59)
in Screen (at StackViewCard.tsx:80)
in Card (at createPointerEventsContainer.tsx:95)
in Container (at StackViewLayout.tsx:971)
in RCTView (at View.js:45)
in View (at screens.native.js:83)
in ScreenContainer (at StackViewLayout.tsx:383)
in RCTView (at View.js:45)
in View (at createAnimatedComponent.js:151)
in AnimatedComponent (at StackViewLayout.tsx:379)
in PanGestureHandler (at StackViewLayout.tsx:372)
in StackViewLayout (at withOrientation.js:30)
in withOrientation (at StackView.tsx:103)
in RCTView (at View.js:45)
in View (at Transitioner.tsx:267)
in Transitioner (at StackView.tsx:40)
in StackView (at createNavigator.js:61)
in Navigator (at createKeyboardAwareNavigator.js:12)
in KeyboardAwareNavigator (at createAppContainer.js:429)

Thanks for report. Now app is unstable in ios devices and emulators. In january/february we planning publish this app in App Store, then this errors should be fixed.


NodeJS 9000 not working, trying to fix it

Info:

Docker version ($ docker --version): <IP_ADDRESS>-mac81 (29211)
Nodedock commit ($ git rev-parse HEAD): master
System info (Mac, PC, Linux): Macbook 10.14.3
System info disto/version: 12" 2017

Issue:
cp env-exmaple .env
docker-compose up -d nginx mysql

after that, can't use 9000 port to access nodejs service
I added
ports:
        - "9000:9000"
        - "9229:9229"

to docker-compose.yml NodeJs Section
then work

nodedock uses a nginx server in front of the node application. So every commucition from the host to the node container has to go through the nginx container. This has a bunch of advantages which are describes in this article.
This is why you cannot access node with port 9000, on your host. You need to use the port of the nginx container. (80 -> NGINX_HOST_HTTP_PORT)

@WillieOng-HK what are the services running can you run docker-compose ps  adding ports in node service indeed work for me.


Commonalities r2.1

Problem description
For milestone M2 Commonalities should publish Release Candidate
Expected action
The release PR for r2.1 needs to be prepared, when scope of the version 0.5 (documented in #273) is covered.
Additional context
For meta-release Spring25 the target date for M2 is planned for 7th of December 2024: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14560849/Meta-release+Spring25#Milestone-status

Update from Release Management - create a first pre-release (alpha) with merged PRs (agreed in the meeting on Nov 25th) by the end of November.
The M2 can be then shifted to cover the full scope defined in #273


The function "PushBack" is lost in List container

CppCommon/include/containers/list.inl:16:9: error: use of undeclared identifier 'PushBack'

maybe it is list::push_back

Thanks a lot! Fixed


Log when publishing Ivy or Maven metadata with known incompatible features from Gradle

Features like constraints, platforms or declared capabilities are not
supported in the ivy.xml file format.
Features like dynamic versions, with latest.<status> or 1.+, and capabilities are not
supported in the pom.xml file format.

I have marked this as WIP because it needs further testing and possible coverage of other cases.
However I am interested in feedback on the approach, the perceived value for user and the logging of that information at LIFECYCLE level.
I had a look at using SingleMessageLogger but the presence of the stacktrace makes it really scary IMO. And similarly for a WARN level logging.
And if as a user you do not care, due to your usage pattern - pom consumed by Gradle only for example - these notifications are just noise.

This is complete given its intended scope.
For ivy-publish, will log when any of the following is declared:

Capabilities
Constraints
Platforms
Dependencies without version

For maven-publish, will log when any of the following is declared:

Capabilities
Dependencies using + in the version
Dependencies using latest.<level> where level is neither release nor integration


Suggestion: Try a more flexible versioning system

At the moment, it seems like the z in x.y.z is incremented every release so far. This can lead to a bit of versioning confusion in cases where APLP updates to a new MC release and later on updates the bundled Groovy version on a previous MC release as mentioned in the repo's readme.
For example, 1.0.2 is for 1.19 and uses Groovy 4.0.3, while 1.0.1 is for 1.18.2 and uses Groovy 4.0.1. If a new release was made for 1.18.2 with Groovy 4.0.3, it's not obvious what the version should be for that. 1.0.2 again? 1.0.4?
I'd like multiple MC versions to be actively supported by APLP as I eventually intend on maintaining mods written in Groovy that target at least Current + LTS Forge versions, and happy to PR as needed to help with that.
I suggest changing the versioning system to be more flexible in this regard. There's multiple ways you could do it, but here's one idea:

Bump major when:

Upgrading to a new major Groovy version (e.g. 4.0.0 -> 5.0.0)
A major APLP API breakage for mod devs (e.g. removal of @Mod annotation in favour of @Mojo, significant change of how to setup the buildscript like in APLP 1.0.1 -> 1.0.2)

Minor:

Bump if existing APLP version doesn't work on a new MC/Forge release and the fix would break compat with older MC/Forge versions

Patch:

Bugfixes
New features
Groovy version bump aside from major version (e.g. 4.0.1 -> 4.0.2)

Samples/Demo:

1.0.1 (bugfix for APLP on MC 1.18.2)
1.1.0 (new release compatible with MC 1.19's breaking changes)
1.0.2 (Groovy patch version bump for APLP on MC 1.18.2)
1.1.1 (Groovy patch version bump for APLP on MC 1.19)

Another idea would be prepending the APLP version with the MC version, like some mods do (e.g. 1.18.2-1.0.2). Or you could simply copy Forge's versioning system and have major bumped every MC version and breaking changes possible during minor version 0. Of course, if you have any better ideas in mind feel free to go with those.

Fixed in v1.1.0


Rework documentation of std.format.write : formattedWrite

I moved a public unittest, that's about grouping to package, because I think, that's something, that is relevant for other functions of std.format to. It even does not use formattedWrite directly. I will cope with that later, when reworking the package docs.
I renamed the template parameter A to Args for consistency with format and sformat. While at other places it is common to use single letters as template parameters, throughout std.format they are descriptive.
I changed the order of the two overloads, like I did with format and sformat because I think, for beginners the one without template parameters is better comprehensible. For the same reason I did not use idiomatic D for the first example.
The output range is named a writer here, I guess that is for historic reasons. In the docs I named it an output range. I think, users will immediately know, what an output range should be able to do, while a writer might not be so clear.
The description of the return value is currently not correct. First of all, I can't see any good use for this. But as it's there, at least it should give something useful. The current behavior would probably be best described as: The largest positional argument used if positional arguments appear and the number of arguments formatted else. I suggest to use the description I provided, file a bug report and change this.

I noticed, that the return value is used by format for deciding, if an Exception is thrown. So I reworded it's description.

removed trailing spaces


CSI driver status

Are there any timelines for when a CSI driver might surface? CSI has been GA in kubernetes since Jan. 2019, and CSI spec has been 1.0 since Nov. 2018.

A CSI driver for Nimble will be made available for BETA and Tech Preview shortly. Please work with your Nimble/HPE rep to be included in the program.

Is there same plan for 3PAR?


Changes to support almond-cloud

Pull Request Test Coverage Report for Build 1167

363 of 428 (84.81%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 78.348%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/ast/program.ts
3
4
75.0%

lib/type.ts
3
4
75.0%

lib/legacy-prettyprint.ts
330
393
83.97%

Totals

Change from base Build 1166:
0.1%

Covered Lines:
10660

Relevant Lines:
13109

💛  - Coveralls


Roadmap Discussion

I'll fill this out more later, just creating a "placeholder" issue to discuss the roadmap for this fork.

I recently started using redux-little-router instead of react-router. Its has much cleaner design & integrates extremely well with redux-saga. Something you can consider.


Upgrade containerd to v1.5.4

Depandabot is complaining about github.com/containerd/containerd, this upgrade should make the warning go away.

Thanks!


Dependency Guidelines

We'd like to consume the current Patternfly CSS based on Bootstrap 3, with the hopes of adopting Patternfly 5 CSS  in the future.
Do you have thoughts about integrating third party components such as ng2-bootstrap?

Initial site framework has been created - dependencies are currently patternfly and ngx-bootstrap (for dropdowns, etc).  Moving to closed.


Upgrading to 0.7.1 throws Error: GUID must provide "serialize" function

Describe the bug
Upgrading to serverless-appsync-simulator version 0.7.1 has caused the following error to be thrown when running the local server:
Error: GUID must provide "serialize" function. If this custom Scalar is also used as an input type, ensure "parseValue" and "parseLiteral" functions are also provided.

To Reproduce
Upgrade to 0.7.1. Use these dependencies as well
"serverless": "^1.60.0",
"serverless-appsync-plugin": "^1.1.2",
"serverless-appsync-simulator": "^0.7.1",
"serverless-offline": "^5.12.1",

And create a graphql schema making use of only ID, String, Int, Float types and types based off of enums.
We're also using various aws decorators like @aws_subscribe
Expected behavior
The api should start successfully and not die on the error listed above
Screenshots

Additional context
I apologize for not providing more info, but I'm not sure where exactly this error is coming from. I'm moreso sharing because I cannot find any information elsewhere, and am wondering if anyone else has the same issue

I also got the same error when upgrading from 0.7.0 to 0.7.1.

@brno32 Thanks for opening this issue.
As I understand, you are not using any custom scalar like GUID in your project?
Error seems to come from node?modules/src/scalars.GUID.ts which I don't know what this is.
It looks like it is from this module https://www.npmjs.com/package/src but looking at the source, I doubt it.

Thanks @FilipPyrek for confirming this.
I am not getting this error on  my side.
Any idea on on to reproduce?

I can see in my package-lock.json:
"serverless-appsync-simulator": {
    "version": "0.7.1",
    "resolved": "https://registry.npmjs.org/serverless-appsync-simulator/-/serverless-appsync-simulator-0.7.1.tgz",
    "integrity": "sha512-onos8JKuuoy9Dcux+VEWPHvm9su6dninGH18UOEqY/3jUmAOSFPpsYgPhZ4zLsdhZXuxbgFVNvxZjtm6ckMk/A==",
    "dev": true,
    "requires": {
        "amplify-appsync-simulator": "^1.23.3",
        "amplify-nodejs-function-runtime-provider": "^1.1.5",
        "aws-sdk": "^2.720.0",
        "axios": "^0.19.2",
        "cfn-resolver-lib": "^1.1.6",
        "dataloader": "^2.0.0",
        "lodash": "^4.17.19",
        "merge-graphql-schemas": "^1.5.8"
    },

And I saw there: "amplify-appsync-simulator": "^1.23.3",
Then I also found in the same package-lock.json this:
"amplify-appsync-simulator": {
    "version": "1.23.9",
    "resolved": "https://registry.npmjs.org/amplify-appsync-simulator/-/amplify-appsync-simulator-1.23.9.tgz",
    "integrity": "sha512-iC9bzW3KMb33VlNJ6QN9oSwDzMUnKlvlNHfT9PXP15lY7jl1hXoKqbh0SrJw1UJl2kILWinQZQgVBrAII85Cow==",
    "dev": true,

We can see there "version": "1.23.9",,
When I took a look at node_modules/amplify-appsync-simulator/package.json I could really see there version 1.23.9.
When I tried removing this 👆 record in package-lock.json and removed node_modules and reinstalled dependencies, it got back with version 1.23.9.
And according to amplify-appsync-simulator/CHANGELOG.md I can see that in version 1.23.9 was a change in appsync scalars.

And I can see in the stack trace:
Error: GUID must provide "serialize" function. If this custom Scalar is also used as an input type, ensure "parseValue" and "parseLiteral" functions are also provided.
      at invariant (...X.X.X.X.X...node_modules/graphql/jsutils/invariant.js:19:11)
      at new GraphQLScalarType (...X.X.X.X.X...node_modules/graphql/type/definition.js:407:73)
      at Object.<anonymous> (...X.X.X.X.X...node_modules/src/scalars/GUID.ts:8:42)
      at Module._compile (internal/modules/cjs/loader.js:1158:30)
      at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
      at Module.load (internal/modules/cjs/loader.js:1002:32)
      at Function.Module._load (internal/modules/cjs/loader.js:901:14)
      at Module.require (internal/modules/cjs/loader.js:1044:19)
      at require (internal/modules/cjs/helpers.js:77:18)
      at Object.<anonymous> (...X.X.X.X.X...node_modules/amplify-appsync-simulator/src/schema/appsync-scalars/index.ts:6:1)
      at Module._compile (internal/modules/cjs/loader.js:1158:30)
      at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
      at Module.load (internal/modules/cjs/loader.js:1002:32)
      at Function.Module._load (internal/modules/cjs/loader.js:901:14)
      at Module.require (internal/modules/cjs/loader.js:1044:19)
      at require (internal/modules/cjs/helpers.js:77:18)
      at Object.<anonymous> (...X.X.X.X.X...node_modules/amplify-appsync-simulator/src/schema/index.ts:5:1)
      at Module._compile (internal/modules/cjs/loader.js:1158:30)
      at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
      at Module.load (internal/modules/cjs/loader.js:1002:32)
      at Function.Module._load (internal/modules/cjs/loader.js:901:14)
      at Module.require (internal/modules/cjs/loader.js:1044:19)
      at require (internal/modules/cjs/helpers.js:77:18)
      at Object.<anonymous> (...X.X.X.X.X...node_modules/amplify-appsync-simulator/src/index.ts:3:1)
      at Module._compile (internal/modules/cjs/loader.js:1158:30)
      at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
      at Module.load (internal/modules/cjs/loader.js:1002:32)
      at Function.Module._load (internal/modules/cjs/loader.js:901:14)
      at Module.require (internal/modules/cjs/loader.js:1044:19)
      at require (internal/modules/cjs/helpers.js:77:18)
      at Object.<anonymous> (...X.X.X.X.X...node_modules/serverless-appsync-simulator/lib/index.js:3:32)
      at Module._compile (internal/modules/cjs/loader.js:1158:30)
      at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
      at Module.load (internal/modules/cjs/loader.js:1002:32)
      at Function.Module._load (internal/modules/cjs/loader.js:901:14)
      at Module.require (internal/modules/cjs/loader.js:1044:19)
      at require (internal/modules/cjs/helpers.js:77:18)
      at requireServicePlugin (...X.X.X.X.X...node_modules/serverless/lib/classes/PluginManager.js:26:10)
      at ...X.X.X.X.X...node_modules/serverless/lib/classes/PluginManager.js:126:20
      at Array.map (<anonymous>)
      at PluginManager.resolveServicePlugins (...X.X.X.X.X...node_modules/serverless/lib/classes/PluginManager.js:123:8)
      at PluginManager.loadAllPlugins (...X.X.X.X.X...node_modules/serverless/lib/classes/PluginManager.js:110:15)
      at ...X.X.X.X.X...node_modules/serverless/lib/Serverless.js:96:35
      at tryCatcher (...X.X.X.X.X...node_modules/bluebird/js/release/util.js:16:23)
      at Promise._settlePromiseFromHandler (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:547:31)
      at Promise._settlePromise (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:604:18)
      at Promise._settlePromise0 (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:729:18)
      at Promise._fulfill (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:673:18)
      at Promise._resolveCallback (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:466:57)
      at Promise._settlePromiseFromHandler (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:559:17)
      at Promise._settlePromise (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:604:18)
      at Promise._settlePromise0 (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:729:18)
      at Promise._fulfill (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:673:18)
      at PromiseArray._resolve (...X.X.X.X.X...node_modules/bluebird/js/release/promise_array.js:127:19)
      at PromiseArray._promiseFulfilled (...X.X.X.X.X...node_modules/bluebird/js/release/promise_array.js:145:14)
      at Promise._settlePromise (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:609:26)
      at Promise._settlePromise0 (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:729:18)
      at Promise._fulfill (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:673:18)
      at Promise._resolveCallback (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:466:57)
      at Promise._settlePromiseFromHandler (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:559:17)
      at Promise._settlePromise (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:604:18)
      at Promise._settlePromise0 (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:729:18)
      at Promise._fulfill (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:673:18)
      at PropertiesPromiseArray.PromiseArray._resolve (...X.X.X.X.X...node_modules/bluebird/js/release/promise_array.js:127:19)
      at PropertiesPromiseArray._promiseFulfilled (...X.X.X.X.X...node_modules/bluebird/js/release/props.js:78:14)
      at Promise._settlePromise (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:609:26)
      at Promise._settlePromise0 (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (...X.X.X.X.X...node_modules/bluebird/js/release/promise.js:729:18)
      at _drainQueueStep (...X.X.X.X.X...node_modules/bluebird/js/release/async.js:93:12)
      at _drainQueue (...X.X.X.X.X...node_modules/bluebird/js/release/async.js:86:9)
      at Async._drainQueues (...X.X.X.X.X...node_modules/bluebird/js/release/async.js:102:5)
      at Immediate.Async.drainQueues [as _onImmediate] (...X.X.X.X.X...node_modules/bluebird/js/release/async.js:15:14)
      at processImmediate (internal/timers.js:456:21)

that the error comes also through amplify-appsync-simulator/src/schema/appsync-scalars/index.ts which is the exact file which was updated in the new version 1.23.9.
So according to my findings it seems that https://github.com/aws-amplify/amplify-cli/pull/5705 caused this issue. 🤔  🤷♂

Thanks for these detailed info @FilipPyrek
I had the version of amplify-appsync-simulator locked to 1.23.7.
I forced-upgraded it. Now using 1.23.9
However, I am still not reproducing the error.
What troubles me is that I cannot find the following file in my node_modules:
node_modules/src/scalars/GUID.ts
are you?

What do you see when you run the following command?
npm ls graphql-scalars
or
yarn why graphql-scalars

IMO the issue with node_modules/src/scalars/GUID.ts could be incorrect source maps.
Because I can see the same path /src/scalars/GUID.ts in graphql-scalars
Output of npm ls graphql-scalars:
api@ /Users/filippyrek/projects/buttonize/buttonize/api
└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>
Also I can see that 25 days ago was added GUID to  graphql-scalars. And I can see that the serialize function is really missing there https://github.com/Urigo/graphql-scalars/blob/master/src/scalars/GUID.ts .

When upgrading to 0.7.1 I can also see this change in package-lock.json
"graphql-scalars": {
-	"version": "1.2.6",
+	"version": "1.4.1",
-	"resolved": "https://registry.npmjs.org/graphql-scalars/-/graphql-scalars-1.2.6.tgz",
+	"resolved": "https://registry.npmjs.org/graphql-scalars/-/graphql-scalars-1.4.1.tgz",
-	"integrity": "sha512-k/88kZVXIuUKQuVLokokkKU2lnFEZ9aTn7O0fDweJpISd0pP5fQU1wzPN0jarH4Lnadr4092PfyIUtCcKzkeAw==",
+	"integrity": "sha512-QCT9sHYkEns9jp3fYqzmoUtS7GiWn+IKrWvSKYDrGOEqlUVP66DDtR0HQmebIbnaSuww239drYnq6JNP0VIDTg==",
	"dev": true
},

IMO the issue with node_modules/src/scalars/GUID.ts could be incorrect source maps.

yes, this is also what I figured out.
I am also on the same versions now
└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>
Still no error on my side.
I suspect it might be schema-related.
Are you using any particular scalar in your schema?

My schema is quite simple
schema {
	query: Query
	mutation: Mutation
}
type Query {
	triggers(organisation: ID!, namespace: ID!): [Trigger!]!
	namespaces(organisation: ID!): [String!]!
}
type Mutation {
	runTrigger(id: ID!): TriggerRunResponse!
}

type Trigger {
	id: ID!
	arn: String!
	label: String!
}

type TriggerRunResponse {
	message: String
	error: String
}

I tried replacing ID with String, but that didn't help.

Thanks.
Still no luck on my side after creating a fresh new project.
I suspect there is some kind of incompatibility in you package-lock.json
could you try to

rm -rf node_modules
rm package-lock.json  (keep a copy of it just in case)

then npm install again and see if the problem persists.

My findings:
I cloned graphql-scalars and I added console.log(GraphQLGUIDConfig) to GUID.ts file to see what is value of GraphQLGUIDConfig and I ran tests.
I got this:
{
    name: 'GUID',
    description: 'A field whose value is a generic Universally Unique Identifier: https://en.wikipedia.org/wiki/Universally_unique_identifier.',
    serialize: [Function: serialize],
    parseValue: [Function: parseValue],
    parseLiteral: [Function: parseLiteral]
}

when I did it in node_modules of the project and then I started serverless-appsync-simulator, I got this:
{
  name: 'GUID',
  description: 'A field whose value is a generic Universally Unique Identifier: https://en.wikipedia.org/wiki/Universally_unique_identifier.',
  astNode: undefined,
  _scalarConfig: {
    name: 'UUID',
    description: 'A field whose value is a generic Universally Unique Identifier: https://en.wikipedia.org/wiki/Universally_unique_identifier.',
    serialize: [Function: serialize],
    parseValue: [Function: parseValue],
    parseLiteral: [Function: parseLiteral]
  }
}

Which is quite strange.
I'm going to proceed to package-lock suggestion of yours @bboure

I found it!
It caused by graphql versions mismatch.
I've had installed one dependency which used graphql version 0.13.2 and I can see that _scalarConfig is present in that old version: https://github.com/graphql/graphql-js/blob/5f50543f7608d52403b1440d1a617626f412a63f/src/type/definition.js#L454
So graphql-scalars was using that old version becuase in they have graphql^0.13.0 in their peerDependencies: https://github.com/Urigo/graphql-scalars/blob/master/package.json#L71
I will create an issue in graphql-scalars.
🙈 Thanks for help and sorry for bothering you @bboure

Great job!
graphql version mismatch was also in my suspicions.
What is your dependency that is using an old version of graphql ?
It might be worth suggesting them to upgrade too

It was this old deprecated package @conduitvc/appsync-emulator-serverless. So in this case there is nobody to notify.
But anyway installation of that package served as a hotfix of some other issue.. but the issue was already fixed so I just removed it and it works okay.

Here is the issue in graphql-scalars: https://github.com/Urigo/graphql-scalars/issues/578

Thanks for feedback @FilipPyrek
@brno32 Does that help into fixing your issue?

I removed aws-appsync from my dependencies, which in turn removed graphql^0.13.0. I upgraded to 0.7.1 of this package and can confirm the issue is gone. Thanks!

Great thanks @brno32
Closing this issue


Longest Consecutive Duplicate String

Hello !, I am a participant of hacktober fest 2021 , I would like to add this important question regarding strings.
Problem statement:  Given a lowercase alphabet string s, return the length of the longest substring with same characters.
Constraints:
0<=n<=100000 , where n is length of string s.
Example cases:
Example 1:
s = "abbbba"
Output: 4
Explanation: The longest substring is "bbbb".
Example 2:
s = "aaabbb"
Output: 3
Explanation: The longest substring is either 'aaa' or 'bbb'.
Please assign me this issuse.

I would like this problem.please assign this to me

They are not considering dsa,cp,algorithm repository :(
all the pr will not be considered in hacktoberfest but your contribution will be for lifetime, this will help many students to practice dsa .
Thank you for your contribution :)


Tried this - clearly I am not smart enough to understand what is happening

Chad level documentation.

Blake & Cameron

I'm not sure I know what is going on either

Error has to do with self cert generation on windows, will need to do some troubleshooting to iron out this issue


[WIP] feat: Add reserved managed kafka generation

Description
Related to https://issues.redhat.com/browse/MGDSTRM-8738.
Implements the addition of the concept of reserved managed kafka instances. A reserved kafka instance is a ManagedKafka that contains the label bf2.org/deployment with the value set to reserved.
The agent-cluster's 'kafkas' endpoint now returns a list of reserved managed kafka instances based on dynamic scaling configuration attributes when dynamic scaling is enabled.
Additional remarks:

The number of reserved ManagedKafka instances that is returned depends on the reserved_streaming_units attribute defined for each instance type in the dynamic scaling configuration (implemented in PR https://github.com/bf2fc6cc711aee1a0c2a/kas-fleet-manager/pull/1144). Only the supported instance types in the cluster are evaluated.
Each reserved ManagedKafka instance has its own dedicated namespace in the data plane cluster
a reserved ManagedKafka instance naming schema is: reserved-kafka-<instance_type>-<kafka_number> where kafka_number goes from 1..<number_of_reserved_streaming_units_for_the_given_instance_type>
The K8s namespace of a ManagedKafka instance is the same as its name. The K8s object name is also the same as its name
If fleet manager is not in autoscaling mode an empty list is returned
If the data plane cluster is not in 'ready' state an empty list is returned
If the data plane cluster is 'ready' but there are no 'ready' strimzi versions an error is returned

Verification Steps

Checklist (Definition of Done)

[ ] All acceptance criteria specified in JIRA have been completed
[ ] Unit and integration tests added that prove the fix is effective or the feature works (tested against emulated and non-emulated OCM environment)
[ ] Documentation added for the feature
[ ] CI and all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer
[ ] All PR comments are resolved either by addressing them or creating follow up tasks
[ ] Required metrics/dashboards/alerts have been added (or PR created).
[ ] Required Standard Operating Procedure (SOP) is added.
[ ] JIRA has been created for changes required on the client side

In any case if we were to do any comparison the ID comparison seems a little bit fragile.

I agree. We are eliminating the reserved ones based on the id format. It should be okay if we do not change the id format of the reserved and real kafkas. For real kafkas, I can't see of a change anytime soon, but for reserved kafka I do not know so if that changes we might need to "remember" updating the status update method as well.

If we were to improve that maybe it would be a good idea for the data plane to send us back if it is a reserved kafka or not? (as we do when we provide that info to them)

I do not know if the data plane sends back the labels. A quick check on the managed kafka cr, there is nothing in the .Status that indicates this.

In any case if we were to do any comparison the ID comparison seems a little bit fragile.

I agree. We are eliminating the reserved ones based on the id format. It should be okay if we do not change the id format of the reserved and real kafkas. For real kafkas, I can't see of a change anytime soon, but for reserved kafka I do not know so if that changes we might need to "remember" updating the status update method as well.

If we were to improve that maybe it would be a good idea for the data plane to send us back if it is a reserved kafka or not? (as we do when we provide that info to them)

I do not know if the data plane sends back the labels. A quick check on the managed kafka cr, there is nothing in the .Status that indicates this.

What I was proposing is for them to send that information in case it is not being sent

When we expect in a test a function to end with en error, I believe we should check what error we received, to avoid having the test succeed because some totally unrelated error has happened

I don't think that's the case to all tests. It totally depends on what are you interested in testing. Also the case you described does not apply. If you check for an error (any) it will fail if there's any error (even unrelated ones)

When it is possible, I believe we should run the tests in parallel (t.Parallel())

This would be the ideal scenario but it makes me think that the cognitive load to evaluate this is potentially big. I am wondering if we should only worry about this when we know the test is time consuming and we are hitting performance problems.

I don't think that's the case to all tests. It totally depends on what are you interested in testing. Also the case you described does not apply. If you check for an error (any) it will fail if there's any error (even unrelated ones). It is also infeasible to test all possible error combinations. Specially when the method you are testing calls other methods each of those possibily returning different errors at different levels.

I don't agree. The role of a good Unit test is to be repeatable and predictable.
If you expect a function to end with an error in a test, that error must be exactly one and you should be able to know what error you are expecting.
If you are not able to predict what is going to happen, then I think the unit test fails its mandate.

I don't think that's the case to all tests. It totally depends on what are you interested in testing. Also the case you described does not apply. If you check for an error (any) it will fail if there's any error (even unrelated ones). It is also infeasible to test all possible error combinations. Specially when the method you are testing calls other methods each of those possibily returning different errors at different levels.

I don't agree. The role of a good Unit test is to be repeatable and predictable. If you expect a function to end with an error in a test, that error must be exactly one and you should be able to know what error you are expecting.
If you are not able to predict what is going to happen, then I think the unit test fails its mandate.

My comment still applies. I can't see a reliable, feasible and maintainable way to test this, aside from not being interested on testing specific errors in this test (or others)

My comment still applies. I can't see a reliable, feasible and maintainable way to test this, aside from not being interested on testing specific errors in this test (or others). If the type of the error being returned was relevant to the consumer of the method then I would agree testing the type would be desirable, but that's not always the case. There is no contract in the method about what errors and when those happen.

If you are expecting an error to happen, that means that you exactly know what is wrong and why. It doesn't matter the contract. If I call a method with a wrong username, I expect to receive a wrong username error, not a 'malformed URL' error because, maybe, I sent a wrong parameter from inside my test.
This is my opinion.

If you are expecting an error to happen, that means that you exactly know what is wrong and why. It doesn't matter the contract.

I don't think that's accurate. The contract does matter. If the methods your method is consuming do not specify the set of errors returned in the contract and you don't check all of them then it becomes infeasible for your method to have a contract about the methods it will return unless you overwrite all the errors returned with your own errors.

If I call a method with a wrong username, I expect to receive a wrong username error, not a 'malformed URL' error because, maybe, I sent a wrong parameter from inside my test.
I don't necessarily agree with this. It all depends on what are you interested in testing. The specific error or an error occurrence.

I don't think that's accurate. The contract does matter. If the methods your method is consuming do not specify the set of errors returned in the contract and you don't check all of them then it becomes infeasible for your method to have a contract about the methods it will return unless you overwrite all the errors returned with your own errors.

In a given situation, the error returned will be just one, and that is what the unit test does: it runs method in a controlled environment to make the outcome predictable, so you just have to check one error.

I don't necessarily agree with this. It all depends on what are you interested in testing. The specific error or an error occurrence.

I believe that is inaccurate. Suppose I test a login function passing a wrong username. The login function is:
func login(url string, username string, pwd string)

and I make an error in my test, passing http:/myloginurl.com, baduser, badpassword.
If I just test for the function to return an error, my test will succeed, but it didn't test what it was supposed to.
I strongly believe that if in a test I expect a function to return an error, then I know what error I'm expecting, otherwise means I have no control of the environment my test is running into.
However, as I said, this is just my opinion.

Just one comment: I think that if we expect an error to occur during the tests, we should check that the error is the one we are expecting, to avoid it being an unrelated error and having the test pass without really testing what it was supposed to do.
Other than that, great job! Thanks @miguelsorianod !

Thanks for the review :+1:
Regarding testing and error checking, I am not convinced about it for the mentioned reasons above, but I am more than willing to explore this concern together at some point, probably with some sample case to see what are the implications.


Fix "Areas of expertise" popup in user/search_recommenders

 Correct a bug: the hyperlink behind "Area of expertise" in the page to suggest recommender does not work


Do you want to consider upgrading your python scripts?

Hi,
I find it very hard to execute your scripts.
Are you working on any packages that allow us to do cf-nucleosome analysis?
Thank you.

Hello wlwtan,
Thanks for your interest in our work.  I am sorry to hear that you are
having difficulty executing our scripts.  I know that several of the
datasets and software packages that we used at the time have since been
updated to newer versions, and I would strongly recommend that you consider
using updated datasets from Human Protein Atlas or GTEx (among others) if
you are considering studying nucleosome footprints in cfDNA.
At this time, we have no plans to upgrade our python or R scripts.
Best regards,
Matthew Snyder
On Mon, Jul 27, 2020 at 6:39 AM wlwtan<EMAIL_ADDRESS>wrote:

Hi,
I find it very hard to execute your scripts.
Are you working on any packages that allow us to do cf-nucleosome analysis?
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/shendurelab/cfDNA/issues/6, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABN4KBAYXCFPI35GZVX7KNTR5V7QRANCNFSM4PIY274A
.

Dear Synder,
Thanks for your prompt response.
I have generated my own pilot datasets and was hoping to be able to use your algorithms to look for cell free nucleosome signature, and subsequently infer the cell type origin.
To be specific, im stuck at the stage of nucleosome calling.
Specific questions:
how do you decide the region to look at for nucleosome signatures? TSS? Or is there an updated unbiased way of doing that? Have you tried if usual peak calling algo would work?
Thank you.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Matthew Snyder<EMAIL_ADDRESS>Sent: Tuesday, July 28, 2020 2:38:12 AM
To: shendurelab/cfDNA<EMAIL_ADDRESS>Cc: TAN Lek Wen Wilson<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [shendurelab/cfDNA] Do you want to consider upgrading your python scripts? (#6)
Hello wlwtan,
Thanks for your interest in our work. I am sorry to hear that you are
having difficulty executing our scripts. I know that several of the
datasets and software packages that we used at the time have since been
updated to newer versions, and I would strongly recommend that you consider
using updated datasets from Human Protein Atlas or GTEx (among others) if
you are considering studying nucleosome footprints in cfDNA.
At this time, we have no plans to upgrade our python or R scripts.
Best regards,
Matthew Snyder
On Mon, Jul 27, 2020 at 6:39 AM wlwtan<EMAIL_ADDRESS>wrote:

Hi,
I find it very hard to execute your scripts.
Are you working on any packages that allow us to do cf-nucleosome analysis?
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/shendurelab/cfDNA/issues/6, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABN4KBAYXCFPI35GZVX7KNTR5V7QRANCNFSM4PIY274A
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/shendurelab/cfDNA/issues/6#issuecomment-664568823, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKG2NC2TXPRHA6AU4TR35H3R5XCRJANCNFSM4PIY274A.
This e-mail and any attachments are only for the use of the intended recipient and may contain material that is confidential, privileged and/or protected by the Official Secrets Act. If you are not the intended recipient, please delete it or notify the sender immediately. Please do not copy or use it for any purpose or disclose the contents to any other person.

Thank you, I have resolved this.

Thank you, I have resolved this.

hi sir：
do you have any faster method to call  wps of deep wgs data ？

No, not at this point.


Breaks windows

I have no idea what installs this, but this forces me to use WSL after 30 mins of googling.

Wait doesn't exist on windows.


Added a test logger

Hello,
I have created a TestLogger. I hope that you feel that this fits inside your package. I know that Monolog has a TestHandler but I believe this is better for the following reasons:

Simpler initialization of Logger inside tests.  More properties that I have to maintain inside my code... etc etc.
Faster tests since it does minimal work. It skips all the extra work that it is made by Logger class.
Inside the TestHandler you have the getRecords function. Even if I retrieve all the records when I need to do simple asserts I can not.. Check this:

$this->assertSame(['level' => 'warning', 'message' => 'that', ['context' => []], $records[0]];

The record contains a lot of extra information that in my case they are not needed.
 So I don't need to have all these information like formatted etc etc.
All I need to test is that the API of the LoggerInterface class is called correctly.

Could you move this inside a Monolog\Test\ namespace (but still in src/)? If you also wanna help out by taking care of https://github.com/Seldaek/monolog/issues/1197 at the same time that'd be even better :)

On the other hand, I kinda wonder if this doesn't belong more in the psr/log package as it doesn't have anything monolog specific really

O had the same dilemma also if I should commit it here or on the PSR. Checking PSR now again I just saw this namespace Psr\Log\Test so yes I believe it could fit in there. check the PR https://github.com/php-fig/log/pull/57
Thank you.

Ok gonna close this here then.

Hi @Seldaek do you think that this could be added in here now that the TestLogger is removed from psr/log ?

@gmponos as there is still nothing specific to Monolog in that TestLogger (the monolog-specific way is to use the TestHandler of Monolog), you can maintain that in its own package.


Add operators/software

Astra Trident
VAST CSI Driver - https://github.com/vast-data/vast-csi
Vsphere driver operator
Vault Secrets Operator
AVI Operator? https://avinetworks.com/docs/latest/load-balance-k8s-openshift-master/

add SR_IOV operator


Update IPs, Add OLT-XGS at NN1936 & NN584

discussion

Updating one of the existing three OLTs' IPs
Adding XGS-OLT (hopefully their API is the same, but they're running the same firmware) units for Olmsted NN584 and 165 Broome NN1936

Could you attach a sample output text file? The instructions in the readme should be up to date, and running the report should be possible from anywhere inside the mesh IP space

Good README instructions, very easy to set up.
I encountered some issues and implemented fixes for them:

Removed the log spam connectionpool.py:1099: InsecureRequestWarning: Unverified HTTPS request is being made to host 'unifi.nycmesh.net'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#tls-warnings
Added error handling around missing keys for ONU name and notes. Now instead of blocking the whole report, it will log the issue and continue
Added error handling for ConnectionTimeout exceptions, for example when an OLT's IP is wrong. Now instead of blocking the whole report, it will log the skip and continue
Removed the 410 Grand construction hack as requested in Slack

CLI output:
-> % mesh-support-report
Fetching Devices Info from UFiber endpoint https://<IP_ADDRESS>/api/v1.0
Fetching Devices Info from UFiber endpoint https://<IP_ADDRESS>/api/v1.0
Fetching Devices Info from UFiber endpoint https://<IP_ADDRESS>/api/v1.0
Device Details object [{'detail': '', 'error': 1, 'message': '.wifi.networks.key: string length (0) must be between 8 and 63', 'statusCode': 400}] was missing the notes section
Device Details object [{'detail': '', 'error': 1, 'message': '.wifi.networks.key: string length (0) must be between 8 and 63', 'statusCode': 400}] was missing the name section
Device Details object [{'detail': '', 'error': 1, 'message': '.wifi.networks.key: string length (0) must be between 8 and 63', 'statusCode': 400}] was missing the notes section
Device Details object [{'detail': '', 'error': 1, 'message': '.wifi.networks.key: string length (0) must be between 8 and 63', 'statusCode': 400}] was missing the name section
Fetching Devices Info from UFiber endpoint https://<IP_ADDRESS>/api/v1.0
Fetching Devices Info from UFiber endpoint https://<IP_ADDRESS>/api/v1.0
**Daily Impaired Devices Report - Wednesday, October 30, 2024 @ 14:13**

UISP - Currently In Outage (new last 7 days)
nycmesh-189-omni (offline since 2024-10-30 @ 13:51)
nycmesh-427-omni (offline since 2024-10-30 @ 11:56)
nycmesh-lbe-4801 (offline since 2024-10-30 @ 06:40)
nycmesh-4801-omni (offline since 2024-10-26 @ 08:54)
nycmesh-303-omni / Dekalb (offline since 2024-10-25 @ 09:53)

UNIFI - Currently In Outage (new last 7 days)
Marcy_4801_West (Parks & Public places) (offline since 2024-10-30 @ 06:41)
1st floor 1 (507 - Clemente) (offline since 2024-10-28 @ 15:58)

UFIBER - Currently In Outage
410-10C (nycmesh-1932-olt3)
410-15D (nycmesh-1932-olt3)
410-15C (nycmesh-1932-olt3)
410-02A (nycmesh-1932-olt3)
410-20E (nycmesh-1932-olt3)
410-25B (nycmesh-1932-olt3)
70:a7:41:34:69:dc (nycmesh-1932-olt2)
70:a7:41:35:8e:d1 (nycmesh-1932-olt2)
460-22G (nycmesh-1932-olt2)
70:a7:41:3b:5a:28 (nycmesh-1932-olt2)
70:a7:41:3e:c4:b5 (nycmesh-1932-olt2)
460-03C (nycmesh-1932-olt2)
460-22E (doorknock no answer 04-10-2023) (nycmesh-1932-olt2)
78:45:58:9a:d4:b0 (nycmesh-1932-olt2)
460-Roof (nycmesh-1932-olt2)
460-4D? (nycmesh-1932-olt2)
d0:21:f9:a0:42:cc (nycmesh-1932-olt2)
460-07H (nycmesh-1932-olt2)
460-07C (nycmesh-1932-olt2)
131-25D (nycmesh-1934-olt1)
131-13C (nycmesh-1934-olt1)
131-12H (nycmesh-1934-olt1)
MISSING_DEVICE_NAME (nycmesh-1934-olt1)
131-09F (nycmesh-1934-olt1)
131-04B (nycmesh-1934-olt1)
70:a7:41:3b:56:e4 (nycmesh-584-olt-xgs)
West-18P-1G-Bernie (nycmesh-584-olt-xgs)
70:a7:41:3b:5c:40 (nycmesh-584-olt-xgs)
70:a7:41:3e:c5:f5 (nycmesh-584-olt-xgs)
working XGS ONU 20240820 (nycmesh-584-olt-xgs)
e4:38:83:ef:12:2e (nycmesh-584-olt-xgs)
e4:38:83:ef:b9:78 (nycmesh-584-olt-xgs)
e4:38:83:ef:bc:03 (nycmesh-584-olt-xgs)
e4:38:83:ef:bc:2a (nycmesh-584-olt-xgs)
East-15B-1G-Erik (nycmesh-584-olt-xgs)

UFIBER - Poor Experience (< 100%)
78:45:58:9a:c7:e8 (nycmesh-1932-olt3) (80%)
460-19B (nycmesh-1932-olt2) (80%)
460-12F (nycmesh-1932-olt2) (77%)
MISSING_DEVICE_NAME (nycmesh-1934-olt1) (80%)

UFIBER - Poor Signal (< -28 dBm)
-- None --

Ignored Issues - All Sources
nycmesh-3461-af60lr-5916 (maintenance mode)
nycmesh-527-west (maintenance mode)
410-08C (unplugs some times)
131-07H (unplugs sometimes)

Not uploading to slack. Set the environment variable SLACK_ENABLED=True to enable automatic posting to slack


Remove ViewBag feature completely

Developers use ViewBag for convenience, but I think it contributes greatly to unwanted performance issues. Force us to use ViewData and Model if necessary.
Thanks.

@sefacan thanks for contacting us.
Unfortunately we aren't likely to do this ever. When we write frameworks we need to make trade-offs and sometimes we build features (like ViewBag) that improve the experience at the cost of performance.
We understand your concerns, but at the same time we value the ease of use ViewBag provides. If you have problems with it in your specific scenario, we would love to see some data on how much it affects performance.
If its significant in any of your scenarios, you could write your own Analyzer to prevent its usage.
I understand this is not probably the answer you expect, but we value more not breaking existing customers than taking out features, even if they are not as good as other alternatives with regards to some specific trait.
Hope that helps.


Show more sources than malacards

Val wanted 'PomBase' as the source of our annotations and 'cancer census' as the source for the entries with cancer_census qualifier

This is going to take a bit of time because the mapping code will need changing to handle the qualifier.
Should "PomBase" and "Cancer census" be links?  If so what should they link to?

I think the plan is to create a PB_REF to link to for "PomBase". The code already copes because of the existing PB_REF for modification annotations in Artemis (example rho3 farnesylated - https://www.pombase.org/gene/SPAC23C4.08).

The code already copes because of the existing PB_REF for modification annotations in Artemis

I had no idea page existed.  I'll make issue about loading PB_references.txt

I had no idea page existed. I'll make issue about loading PB_references.txt

LOL, yes, it would be good to see the abstract on the pub page(s).

I think the plan is to create a PB_REF to link to for "PomBase".

That makes sense.
If we can change qualifier=cancer_census in the contig files to db_xref=<something> it will make things quite a bit simpler.

If we can change qualifier=cancer_census in the contig files to db_xref= it will make things quite a bit simpler.

I guess @ValWood would know if there's a publication to use; if not, I think we could do yet another PB_REF pretty easily (I'm happy to massage any pile of text into a PB_REF entry).

cancer census = cosmic  https://cancer.sanger.ac.uk/census
citation
https://academic.oup.com/nar/advance-article/doi/10.1093/nar/gky1015/5146192

I wonder if we could make a "micropublication" describing the curation/mapping /source of  the disease gene mappings , or it it would be too long.
(i.e the  announcment sort of size, with a short method?)

cancer census citation
https://academic.oup.com/nar/advance-article/doi/10.1093/nar/gky1015/5146192

= PMID:30371878

Ohh, that way we could acknowledge my two students too? That would be really nice for them :-)
On Fri, 14 Dec 2018 at 14:54, Midori Harris <notifications<EMAIL_ADDRESS>wrote:
cancer census citation
https://academic.oup.com/nar/advance-article/doi/10.1093/nar/gky1015/5146192
= PMID:30371878
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/pombase/website/issues/1072#issuecomment-447348548, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMI00ulCSDbLwbAEZ32C7cjp84gRdpZlks5u47uOgaJpZM4ZTRLH.
--
Antonia Lock, PhD
PomBase Biocurator, http://www.pombase.org
Department of Genetics, Evolution and Environment,
The Darwin Building,
University College London
London WC1E 6BT, UK

I've changed qualifier=cancer_census in the contig files to db_xref=PMID:30371878

Which reference should be used for the manually curated disease associations in the contig file that didn't have qualifier=cancer_census?

Which reference should be used for the manually curated disease associations in the contig file that didn't have qualifier=cancer_census?

That's what we'll use a new PB_REF for. I'm hoping Val and/or Antonia can give me some text, because if I make it up I'm likely to get something wrong ;)

It only needs to be short.
Something along the lines:
Unless Antonia has anything to add.
Disease associations curated by PomBase curators based on orthology to human disease genes.
(@Antonialock  Future student projects can summarize  their 'findings' in a micropublication. Or  you could could create a micropub  as a co author with the previous project students....we will need to enable doi for  display and curation of micropubbut that is in the pipeline)

OK, I have stuck in some text and the other bits to create PB_REF:0000003 (pb-ref 2 is a blurb on manual ortholog creation). If you spot anything wrong with either one, edit pombe-embl/supporting_files/PB_references.txt or tell me what to change.
@kimrutherford, will the new PB_REF be deployed automagically or should I put it in the contig files?


undo/redo implementation

Current Plan: create a service that subscribes to the observables in workflow-graph to tell when events occur, then store the opposite action in an undo stack to undo(for example, if user creates an operator, we want to push an action that deletes that operator onto the stack). For now, will focus on undoing/redoing actions relating to operators and links.

use a filter to make it so pressing buttons only undoes/redoes when focused on the workflow editor

Undo/redo is implemented in #722


Canceling an operation leaves the clock running

When you cancel a request, the text "Processing..." remains and the clock keeps running:

Fixed when merging pull request


When finetuning llava-internlm2 (with dinov2), xtuner suddenly exits without error

I am fintuning llava-internlm2 (but replacing clip with dinov2, see #297). I finish the pretraining phase successfully. But during the finetuning phase, xtuner will suddenly quits without any error reported:

I monitor the RAM used with the top command, and there isn't an OOM error. Since the dataloading is not finished, I guess it is not a problem of Dinov2.
My command is
xtuner train llava_internlm2_chat_7b_qlora_clip_vit_large_p14_336_lora_e1_gpu8_finetune_copy.py --deepspeed deepspeed_zero2

the modified config file and the log is attatched.

Hi! Please modify the map_num_proc to 1 and try again
https://github.com/InternLM/xtuner/blob/26d333f83bcd84122ffe68459dbbe292a80b5c03/xtuner/dataset/huggingface.py#L29

The problem is solved! But then it reports "no enough CUDA memory". I am using a 4090 and set batch size = 1. Is it normal?

Yes. 24GB is not enough for fine-tuning. Because the length of fine-tuning's data are much longer than those for pre-training.

I switch to A6000 on vast.ai (A6000 has 48GB RAM). When I finetune with a single A6000, it's fine. But when I use 4 A6000 gpu, the program is stuck here:

All GPU are utilized but the GPU memory is not much allocated:

The command is still
xtuner train llava_internlm2_chat_7b_qlora_clip_vit_large_p14_336_lora_e1_gpu8_finetune_copy.py --deepspeed deepspeed_zero2
The log is 20240128_073714.log.
There was an error about multi-process communication:
Error: mkl-service + Intel(R) MKL: MKL_THREADING_LAYER=INTEL is incompatible with libgomp.so.1 library.
Try to import numpy first or set the threading layer accordingly. Set MKL_SERVICE_FORCE_INTEL to force it.

When I export MKL_SERVICE_FORCE_INTEL=1, the error message does not show up again.

After half an hour I get:
[E ProcessGroupNCCL.cpp:828] [Rank 3] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=1, OpT
ype=BROADCAST, Timeout(ms)=1800000) ran for 1806937 milliseconds before timing out.
[E ProcessGroupNCCL.cpp:828] [Rank 2] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=1, OpT
ype=BROADCAST, Timeout(ms)=1800000) ran for 1806980 milliseconds before timing out.
[E ProcessGroupNCCL.cpp:828] [Rank 1] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=1, OpT
ype=BROADCAST, Timeout(ms)=1800000) ran for 1807185 milliseconds before timing out.
[E ProcessGroupNCCL.cpp:455] Some NCCL operations have failed or timed out. Due to the asynchronous nature
 of CUDA kernels, subsequent GPU operations might run on corrupted/incomplete data.
[E ProcessGroupNCCL.cpp:460] To avoid data inconsistency, we are taking the entire process down.
[E ProcessGroupNCCL.cpp:455] Some NCCL operations have failed or timed out. Due to the asynchronous nature
 of CUDA kernels, subsequent GPU operations might run on corrupted/incomplete data.
[E ProcessGroupNCCL.cpp:460] To avoid data inconsistency, we are taking the entire process down.
[E ProcessGroupNCCL.cpp:455] Some NCCL operations have failed or timed out. Due to the asynchronous nature
 of CUDA kernels, subsequent GPU operations might run on corrupted/incomplete data.
[E ProcessGroupNCCL.cpp:460] To avoid data inconsistency, we are taking the entire process down.
WARNING:torch.distributed.elastic.multiprocessing.api:Sending process 12534 closing signal SIGTERM
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: -6) local_rank: 1 (pid: 12535) of binary: /opt/conda/bin/python
Traceback (most recent call last):                                                               [12/1967]
  File "/opt/conda/bin/torchrun", line 33, in <module>
    sys.exit(load_entry_point('torch==2.0.1', 'console_scripts', 'torchrun')())
  File "/opt/conda/lib/python3.10/site-packages/torch/distributed/elastic/multiprocessing/errors/__init__.
py", line 346, in wrapper
    return f(*args, **kwargs)
  File "/opt/conda/lib/python3.10/site-packages/torch/distributed/run.py", line 794, in main
    run(args)
  File "/opt/conda/lib/python3.10/site-packages/torch/distributed/run.py", line 785, in run
    elastic_launch(
  File "/opt/conda/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 134, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/opt/conda/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 250, in launch_ag
ent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
============================================================
/opt/conda/lib/python3.10/site-packages/xtuner/tools/train.py FAILED
------------------------------------------------------------
Failures:
[1]:
  time      : 2024-01-28_08:07:25
  host      : 08cdfabdfec3
  rank      : 2 (local_rank: 2)
  exitcode  : -6 (pid: 12536)
  error_file: <N/A>
  traceback : Signal 6 (SIGABRT) received by PID 12536
[2]:
  time      : 2024-01-28_08:07:25
  host      : 08cdfabdfec3
  rank      : 3 (local_rank: 3)
  exitcode  : -6 (pid: 12537)
  error_file: <N/A>
  traceback : Signal 6 (SIGABRT) received by PID 12537
------------------------------------------------------------
Root Cause (first observed failure):
[0]:
  time      : 2024-01-28_08:07:25
  host      : 08cdfabdfec3
  rank      : 1 (local_rank: 1)
  exitcode  : -6 (pid: 12535)
  error_file: <N/A>
  traceback : Signal 6 (SIGABRT) received by PID 12535
============================================================

NPROC_PER_NODE=4 xtuner train XXX
Add NPROC_PER_NOD=4 to use multi-gpu DDP training.

I forgot to mention it...The full command is NPROC_PER_NODE=4 xtuner train llava_internlm2_chat_7b_qlora_dinov2_large_p14_336_lora_e1_gpu8_finetune_copy.py --deepspeed deepspeed_zero2

There will be the problem with NPROC_PER_NODE=4. If I simply use xtuner train llava_internlm2_chat_7b_qlora_dinov2_large_p14_336_lora_e1_gpu8_finetune_copy.py --deepspeed deepspeed_zero2, the program can successfully run with single A6000. @LZHgrla

@StarCycle
It seems that it is an error during the loading of model.
How many GPUs were used for pre-training? 1 or 4?

Thank you. The problem has been solved by switching to another docker image (even in the same machine)...Perhaps there are some problems with the docker image


Window ignoring window rule

Already reported ? *

[X] I have searched the existing open and closed issues.

Regression?
No
System Info and Version
 System/Version info
Hyprland, built from branch main at commit 0f594732b063a90d44df8c5d402d658f27471dfe  (props: bump version to 0.43.0).
Date: 2024-09-08
Tag: v0.43.0, commits: 0f594732b063a90d44df8c5d402d658f27471dfe

flags: (if any)

System Information:
System name: Linux
Node name: chronos
Release: 6.6.52
Version: #1-NixOS SMP PREEMPT_DYNAMIC Wed Sep 18 17:24:10 UTC 2024

GPU information:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation AD104 [GeForce RTX 4070 Ti] [10de:2782] (rev a1) (prog-if 00 [VGA controller])
10:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev cb) (prog-if 00 [VGA controller])
NVRM version: NVIDIA UNIX Open Kernel Module for x86_64  560.35.03  Release Build  (nixbld@)  Thu Sep 19 05:55:13 UTC 2024

os-release: ANSI_COLOR="1;34"
BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"
BUILD_ID="24.11.20240921.9357f4f"
DOCUMENTATION_URL="https://nixos.org/learn.html"
HOME_URL="https://nixos.org/"
ID=nixos
IMAGE_ID=""
IMAGE_VERSION=""
LOGO="nix-snowflake"
NAME=NixOS
PRETTY_NAME="NixOS 24.11 (Vicuna)"
SUPPORT_URL="https://nixos.org/community.html"
VERSION="24.11 (Vicuna)"
VERSION_CODENAME=vicuna
VERSION_ID="24.11"

plugins:

======Config-Start======

Config File: /home/iain/.config/hypr/hyprland.conf: Read Succeeded
# Monitors
monitor = desc:GIGA-BYTE TECHNOLOGY CO. LTD. G34WQC A 21442B000619,3440x1440@144,0x0,1
monitor = desc:LG Electronics 23MP65,1920x1080@60,3440x0,1

# Workspaces
workspace=1, monitor:desc:GIGA-BYTE TECHNOLOGY CO. LTD. G34WQC A 21442B000619, default:true
workspace=2, monitor:desc:LG Electronics 23MP65, default:true

# Window Rules
windowrulev2 = workspace special:magic, title:(1Password)
windowrulev2 = workspace 2, class:(vesktop)
windowrulev2 = workspace 1, title:(.*)

# Startup services
exec-once=systemctl --user start keyboard.service
exec-once=systemctl --user start media_keys.service
exec-once = [workspace special:magic silent] 1password

# For all categories, see https://wiki.hyprland.org/Configuring/Variables/
input {
    kb_layout = gb

    follow_mouse = 2
    sensitivity = 0 # -1.0 - 1.0, 0 means no modification.
}

general {
    # See https://wiki.hyprland.org/Configuring/Variables/ for more

    gaps_in = 5
    gaps_out = 10
    border_size = 2
    col.active_border = rgba(4CAF50F2) rgba(00ff99ee) 45deg
    col.inactive_border = rgba(595959aa)

    layout = dwindle

    # Please see https://wiki.hyprland.org/Configuring/Tearing/ before you turn this on
    allow_tearing = false
}

decoration {
    # See https://wiki.hyprland.org/Configuring/Variables/ for more

    rounding = 10

    blur {
        enabled = true
        size = 3
        passes = 1
    }

    drop_shadow = yes
    shadow_range = 4
    shadow_render_power = 3
    col.shadow = rgba(1a1a1aee)
}

animations {
    enabled = yes

    # Some default animations, see https://wiki.hyprland.org/Configuring/Animations/ for more

    bezier = myBezier, 0.05, 0.9, 0.1, 1.05

    animation = windows, 1, 7, myBezier
    animation = windowsOut, 1, 7, default, popin 80%
    animation = border, 1, 10, default
    animation = borderangle, 1, 8, default
    animation = fade, 1, 7, default
    animation = workspaces, 1, 6, default
}

dwindle {
    # See https://wiki.hyprland.org/Configuring/Dwindle-Layout/ for more
    pseudotile = yes # master switch for pseudotiling. Enabling is bound to mainMod + P in the keybinds section below
    preserve_split = yes # you probably want this
}

master {
    # See https://wiki.hyprland.org/Configuring/Master-Layout/ for more
}

gestures {
    # See https://wiki.hyprland.org/Configuring/Variables/ for more
    workspace_swipe = off
}

misc {
    # See https://wiki.hyprland.org/Configuring/Variables/ for more
    force_default_wallpaper = -1 # Set to 0 or 1 to disable the anime mascot wallpapers

    # DPMS stuff
    mouse_move_enables_dpms=true
    key_press_enables_dpms=true
}

# Window Rules
# windowrulev2 = workspace 2, class:(WebCord)

# Keyboard Shortcutes
# See https://wiki.hyprland.org/Configuring/Keywords/ for more
$mainMod = SUPER

# Example binds, see https://wiki.hyprland.org/Configuring/Binds/ for more

bind = $mainMod, C, killactive,
bind = $mainMod, M, exit,
bind = $mainMod, V, togglefloating,
bind = $mainMod, P, pseudo, # dwindle
bind = $mainMod, J, togglesplit, # dwindle
bind = $mainMod, F, fullscreen,

# Move focus with mainMod + arrow keys
bind = $mainMod, left, movefocus, l
bind = $mainMod, right, movefocus, r
bind = $mainMod, up, movefocus, u
bind = $mainMod, down, movefocus, d

# Switch workspaces with mainMod + [0-9]
bind = $mainMod, 1, workspace, 1
bind = $mainMod, 2, workspace, 2
bind = $mainMod, 3, workspace, 3
bind = $mainMod, 4, workspace, 4
bind = $mainMod, 5, workspace, 5
bind = $mainMod, 6, workspace, 6
bind = $mainMod, 7, workspace, 7
bind = $mainMod, 8, workspace, 8
bind = $mainMod, 9, workspace, 9
bind = $mainMod, 0, workspace, 10

# Move active window to a workspace with mainMod + SHIFT + [0-9]
bind = $mainMod SHIFT, 1, movetoworkspace, 1
bind = $mainMod SHIFT, 2, movetoworkspace, 2
bind = $mainMod SHIFT, 3, movetoworkspace, 3
bind = $mainMod SHIFT, 4, movetoworkspace, 4
bind = $mainMod SHIFT, 5, movetoworkspace, 5
bind = $mainMod SHIFT, 6, movetoworkspace, 6
bind = $mainMod SHIFT, 7, movetoworkspace, 7
bind = $mainMod SHIFT, 8, movetoworkspace, 8
bind = $mainMod SHIFT, 9, movetoworkspace, 9
bind = $mainMod SHIFT, 0, movetoworkspace, 10

# Example special workspace (scratchpad)
bind = $mainMod, S, togglespecialworkspace, magic
bind = $mainMod SHIFT, S, movetoworkspace, special:magic

# Scroll through existing workspaces with mainMod + scroll
bind = $mainMod, mouse_down, workspace, e+1
bind = $mainMod, mouse_up, workspace, e-1

# Move/resize windows with mainMod + LMB/RMB and dragging
bindm = $mainMod, mouse:272, movewindow
bindm = $mainMod, mouse:273, resizewindow

# Volume
bind=,XF86AudioRaiseVolume,exec,wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%+
bind=,XF86AudioLowerVolume,exec,wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%-
bind=,XF86AudioMute,exec,wpctl set-mute @DEFAULT_AUDIO_SINK@ toggle

# Mic
bind=ALT,XF86AudioRaiseVolume,exec,wpctl set-volume @DEFAULT_AUDIO_SOURCE@ 5%+
bind=ALT,XF86AudioLowerVolume,exec,wpctl set-volume @DEFAULT_AUDIO_SOURCE@ 5%-
bind=ALT,XF86AudioMute,exec,wpctl set-mute @DEFAULT_AUDIO_SOURCE@ toggle

# Play/Pause
bind=,XF86AudioPlay,exec,playerctl play-pause

# Applications
$terminal = kitty
$fileManager = dolphin
bind = $mainMod, Q, exec, $terminal
bind = $mainMod, E, exec, $fileManager
# bind = $mainMod, space, exec, /home/iain/.nix-profile/bin/rofi -show drun
bind = $mainMod, space, exec, /home/iain/.nix-profile/bin/wofi --allow-images --show drun
bind = $mainMod, x, exec, /home/iain/.config/wofi/powermenu.sh
bind = $mainMod, l, exec, sleep 1 && hyprctl -i 0 dispatch dpms standby
bind = , Print, exec, /home/iain/.config/scripts/screenshot.sh

======Config-End========

Description
When launching Balder's Gate 3 from steam the launcher opens on the LG Electronics 23MP65,1920x1080@60,3440x0,1 monitor. Even when I created the rule
windowrulev2 = workspace 1, title:(.*) it will take focus to workspace 1 then immediately the window appears on workspace 2 on the 2nd monitor.
I originally just wanted the windows to open on my GIGA-BYTE TECHNOLOGY CO. LTD. G34WQC A 21442B000619,3440x1440@144,0x0,1 However, the rules only accept id or DP-1 and these seem to change sometimes with my system (e.g. DP-1 changed to DP-2 no idea why)
The 2nd monitor commonly gets id of 0 which I don't know of a way of forcing the main monitor to be 0 instead.
Window details after it appears
Window 18a2c200 -> LariLauncher:
	mapped: 1
	hidden: 0
	at: 3800,130
	size: 1200,820
	workspace: 2 (2)
	floating: 1
	pseudo: 0
	monitor: 1
	class: steam_app_1086940
	title: LariLauncher
	initialClass: steam_app_1086940
	initialTitle: LariLauncher
	pid: 47240
	xwayland: 1
	pinned: 0
	fullscreen: 0
	fullscreenClient: 0
	grouped: 0
	tags:
	swallowing: 0
	focusHistoryID: 1

How to reproduce
I'm not entirely sure how to cleanly reproduce.
I just open steam and launch BG3
Crash reports, logs, images, videos
No response

considering it's xwayland, I'd guess that the XWayland server forces the position of the window opening

I assumed it might be that and opening on whatever monitor is id 0. Is there a way to reliable get my ultrawide monitor to be id 0 to test that?

Ahh, took some more searching but I never realised that Xwayland listens to xrandr settings for stuff like primary monitor. So setting that has got the windows opening on my ultrawide at least.
Kinda sucks that it's not easily controllable through rules, but that's more an Xwayland problem I guess.

more like X in geenral


Reviewed and provideed feedback on partner's Assignment 1, focusing o…

…n missing values in the list
What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
I reviewed my partner's Assignment 1, specifically focusing on handling missing values in the list.
What did you learn from the changes you have made?
I learned how small adjustments can improve the robustness of a solution.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
I considered using a different algorithm but decided to refine the current approach by focusing on handling missing values more effectively.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
I overcame this by testing with various input scenarios.
How were these changes tested?
The changes were tested by running the code with different input lists to ensure missing values were correctly identified.
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

Hi Tianyi,
Thank you so much for your help and your patience. I also plan to complete
all assignments and homework for the Deep Learning module on time.
Thank you so much again
Best,
Marjan
On Fri, Nov 22, 2024 at 2:02 PM Tianyi Liu @.***> wrote:

@.**** approved this pull request.
Hi Marjan!
Thank you for completing and submitting your ADS A2.
All your ADS assignments have been completed. Thank you for your
participation, and I wish you all the success in your future endeavours.
Thanks,
Tianyi [LS]
—
Reply to this email directly, view it on GitHub
https://github.com/marjanrajabi437/algorithms_and_data_structures/pull/2#pullrequestreview-2455420226,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKSZRPYK4ECU3NKHUCFTUWT2B55T3AVCNFSM6AAAAABR6DBR52VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDINJVGQZDAMRSGY
.
You are receiving this because you authored the thread.Message ID:
<marjanrajabi437/algorithms_and_data_structures/pull/2/review/2455420226@
github.com>

--
Marjan Rajabi
PhD in Statistics
Statistical Researcher & Data Scientist
Phone:<PHONE_NUMBER>


Added api for static functions in py

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 88.372%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1140

Relevant Lines:
1290

💛  - Coveralls


use alias for command

fix #156385

According to my research, BASH_COMMAND is replaced with its definition when it gets executed. This is what i've come up with as a workaround

new idea: save the aliases in an array and cycle through them - I don't like this idea though because ppl could have many and that could be slow

According to my research, BASH_COMMAND is replaced with its definition when it gets executed. This is what i've come up with as a workaround
one issue w this approach is if someone runs the full path, it'll be changed to the alias if re-run. I don't think that's a big problem though

We might be confusing absolute path with alias? The main place the issue shows up for me is because I have git pointing at hub:

So if you run:
alias myalias=echo
myalias "hello world"

You end up seeing this:

@Tyriar this is how i'm reproducing it https://github.com/microsoft/vscode/issues/156385#issuecomment-1209630415
is that correct?

I got kind of close by turning off alias resolution, resolving it myself but that fell apart when trying it actually run it and get $? working correctly. It also required not unsetting setting shopt -u expand_aliases but also setting shopt -s extdebug which probably has performance problems and other unforeseen consequences. This was my prototype:
__vsc_preexec() {
	# echo "  __vsc_preexec BASH_COMMAND=$BASH_COMMAND, $BASH_ARGC, ${BASH_CMDS[@]}"
	# echo "  inside"

	__vsc_initialized=1
	if [[ ! "$BASH_COMMAND" =~ ^__vsc_prompt* ]]; then
		__vsc_current_command=$BASH_COMMAND
	else
		__vsc_current_command=""
	fi

	# The unresolved alias is stored, resolve the alias ourselves since expand_aliases is disabled
	#local resolvedAlias=$(alias $BASH_COMMAND 2> /dev/null)
	local lhs=$(echo $BASH_COMMAND | cut -d ' ' -f1)
	local rhs=$(echo $BASH_COMMAND | sed 's/.* //')
	echo "lhs=$lhs"
	local resolvedAlias=${BASH_ALIASES[$lhs]}
	if [ "$resolvedAlias" = "" ]; then
		resolvedAlias=$lhs
	fi
	echo "resolved: $resolvedAlias $rhs"
	__vsc_resolved_command="$resolvedAlias $rhs"
	__vsc_command_output_start
}

shopt -u expand_aliases
shopt -s extdebug

		__vsc_preexec_all() {
			__vsc_resolved_command="$BASH_COMMAND"
			if [ "$__vsc_in_command_execution" = "0" ]; then
				__vsc_in_command_execution="1"
				builtin eval ${__vsc_dbg_trap}
				__vsc_preexec
			fi

			eval "$__vsc_resolved_command"
			# exitCode=$(eval "$__vsc_resolved_command")
			# (exit ${exitCode})
			return 1 # cancels the original command
		}

Because of all the downsides in attempting to do something clever like that, I suggest we step back and try solve the problem in a less perfect but much simpler way, such as:

Reading the buffer to check for the alias
Adding both the aliased and non-aliased version whenever a command is run

I think 1 should be easy enough and end up with pretty good results, especially considering we can typically rely on bash being non-Windows and that it's not the end of the world if it fails anyway. If we do this, let's only do it when IsWindows is not set.
One idea that is probably overkill to prevent extra work and only do this check on aliases is to run bash -ic "alias" or bash -ilc "alias" once per session in a separate shell when bash shell integration is activated. Let's keep that in our back pocket for now.


Bind to UIDatePicker count down duration

I'm using a UIDatePicker to select a time interval via the countDownDuration property. It would be nice to be able to bind to this value in addition to date.
viewModel.time.bidirectionalBind(to: timePicker.reactive.countDownDuration)

A simple bind work around is:
_ = timePicker.reactive.controlEvents(.valueChanged).observeNext { value in
  viewModel.time.value = timePicker.countDownDuration
}


Failed to connect to the server: tls: first record does not look like a TLS handshake

What happened:
My supervisor could not connect to the server
env: CentOS 8
opentelemetry-collector-contrib version: v0.112.0
opamp version: build from commit #307
my supervisor config
server:
  endpoint: ws://<IP_ADDRESS>:4320/v1/opamp
  tls:
    # Disable verification to test locally.
    # Don't do this in production.
    #insecure_skip_verify: true
    insecure: true
    # For more TLS settings see config/configtls.ClientConfig

capabilities:
  reports_effective_config: true
  reports_own_metrics: true
  reports_health: true
  accepts_remote_config: true
  reports_remote_config: true

agent:
  executable: /usr/bin/otelcol-contrib

storage:
  directory: .

supervisor log:
[root@yptjkcshj-Linux-005 opamp]# ./opamp-supervisor --config supervisor.yaml
2024/10/25 11:25:56 Supervisor starting, id=0192c1b5-990d-7695-b5a1-463fa45d5cab, type=io.opentelemetry.collector, version=1.0.0.
2024/10/25 11:25:56 Starting OpAMP client...
2024/10/25 11:25:56 OpAMP Client started.
2024/10/25 11:25:56 Starting agent /usr/bin/otelcol-contrib
2024/10/25 11:25:56 Failed to connect to the server: tls: first record does not look like a TLS handshake
2024/10/25 11:25:56 Connection failed (tls: first record does not look like a TLS handshake), will retry.
2024/10/25 11:25:56 Agent process started, PID=4147985
2024/10/25 11:25:56 Agent is not healthy: Get "http://localhost:13133": dial tcp [::1]:13133: connect: connection refused
2024/10/25 11:25:57 Agent is not healthy: Get "http://localhost:13133": dial tcp [::1]:13133: connect: connection refused
2024/10/25 11:25:57 Failed to connect to the server: tls: first record does not look like a TLS handshake
2024/10/25 11:25:57 Connection failed (tls: first record does not look like a TLS handshake), will retry.
2024/10/25 11:25:57 Agent is not healthy: Get "http://localhost:13133": dial tcp [::1]:13133: connect: connection refused
2024/10/25 11:25:58 Failed to connect to the server: tls: first record does not look like a TLS handshake
2024/10/25 11:25:58 Connection failed (tls: first record does not look like a TLS handshake), will retry.
2024/10/25 11:25:58 Agent is not healthy: Get "http://localhost:13133": dial tcp [::1]:13133: connect: connection refused
2024/10/25 11:25:59 Failed to connect to the server: tls: first record does not look like a TLS handshake
2024/10/25 11:25:59 Connection failed (tls: first record does not look like a TLS handshake), will retry.
2024/10/25 11:26:00 Agent is not healthy: Get "http://localhost:13133": dial tcp [::1]:13133: connect: connection refused
2024/10/25 11:26:01 Failed to connect to the server: tls: first record does not look like a TLS handshake
2024/10/25 11:26:01 Connection failed (tls: first record does not look like a TLS handshake), will retry.

my otelcol-contrib config:
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: <IP_ADDRESS>:4317
      http:
        endpoint: <IP_ADDRESS>:4318
  prometheus:
    config:
      scrape_configs:
        - job_name: 'otel-collector'
          scrape_interval: 5s
          static_configs:
            - targets: ['<IP_ADDRESS>:19100']

processors:
  batch:
    timeout: 5s
    send_batch_size: 100000
  transform:
    log_statements:
      - context: log
        statements:
          - set(severity_text, "TRACE") where severity_number == 1
          - set(severity_text, "DEBUG") where severity_number == 5
          - set(severity_text, "INFO") where severity_number == 9
          - set(severity_text, "WARN") where severity_number == 13
          - set(severity_text, "ERROR") where severity_number == 17
          - set(severity_text, "FATAL") where severity_number == 21

exporters:
  clickhouse:
    endpoint: tcp://<IP_ADDRESS>:9000?dial_timeout=10s
    create_schema: true
    database: otel
    async_insert: true
    ttl: 72h
    compress: lz4
    timeout: 5s
    retry_on_failure:
      enabled: true
      initial_interval: 5s
      max_interval: 30s
      max_elapsed_time: 300s
    username: "default"
    password: "123"
    cluster_name: cluster_3S_1R
    table_engine:
      name: "ReplicatedMergeTree"

    logs_table_name: otel_logs

    traces_table_name: otel_traces

    metrics_tables:
      gauge:
        name: "otel_metrics_gauge"
      sum:
        name: "otel_metrics_sum"
      summary:
        name: "otel_metrics_summary"
      histogram:
        name: "otel_metrics_histogram"
      exponential_histogram:
        name: "otel_metrics_exp_histogram"
  debug:
    verbosity: detailed

extensions:
  opamp:
    server:
      ws:
        endpoint: ws://<IP_ADDRESS>:9321/v1/opamp
        tls:
          insecure: true
    instance_uid: 01BX5ZZKBKACTAV9WEVGEMMVRZ

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [clickhouse]
    logs:
      receivers: [otlp]
      processors: [batch, transform]
      exporters: [clickhouse]
    metrics:
      receivers: [otlp, prometheus]
      processors: [batch]
      exporters: [clickhouse]
  extensions: [opamp]
  telemetry:
    logs:
      level: "debug"

With this change https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35363, the tls section would be conditionally loaded. Is your opamp server configured to use TLS?

With this change open-telemetry/opentelemetry-collector-contrib#35363, the tls section would be conditionally loaded. Is your opamp server configured to use TLS?

hi, where can I view my server config? I just built the server and put the binary file on the server to run it, without making any configuration changes.

Do you have your own server implementation, or do you use the example https://github.com/open-telemetry/opamp-go/tree/main/internal/examples/server as your OpAMP server?

Do you have your own server implementation, or do you use the example https://github.com/open-telemetry/opamp-go/tree/main/internal/examples/server as your OpAMP server?

I built the example server's code，the only personal change is that i changed the ui's port in /opamp-go/internal/examples/server/uisrv/ui.go, from 4321 to 9321

That explains it. If it's a production, please fix the tls config to use proper certs and update the endpoint to use the wss protocol. If you are experimenting, you can set insecure_skip_verify: true and change the endpoint to wss://<IP_ADDRESS>:4320/v1/opamp

That explains it. If it's a production, please fix the tls config to use proper certs and update the endpoint to use the wss protocol. If you are experimenting, you can set insecure_skip_verify: true and change the endpoint to wss://<IP_ADDRESS>:4320/v1/opamp

It works, thanks a lot!

Hi @srikanthccv
I have added the same insecure_skip_verify: true In my config file but still i am getting the error.
2024/11/12 10:05:23 Failed to connect to the server: tls: first record does not look like a TLS handshake
2024/11/12 10:05:23 Connection failed (tls: first record does not look like a TLS handshake), will retry.
My Supervisor file is
server:
endpoint: wss://...:4321/v1/opamp
tls:
insecure_skip_verify: true
agent:
executable: /usr/bin/otelcol-contrib

Are you using the same example server from here https://github.com/open-telemetry/opamp-go/tree/main/internal/examples/server?

@srikanthccv is their anything i am missing here, my opamp server is running on ec2 machine with the same above example server

my opamp server is running on ec2 machine with the same above example server

@priyeshsingh550, you are probably trying to connect to the server using the EC2 instance's public IP/hostname, but the example server's self-signed certificate is only valid for <IP_ADDRESS> and localhost. This could be solved by regenerating the certs EC2 IP/hostname to the alt_names sections. Please remember that it is an example server and is not meant to be used for anything beyond simple testing.


added spaceless to base template

Issue Reference
This PR addresses the Issue : Fixes #426
Summarize
This PR adds spaceless to base template which reduces the rendered html footprint, ie; minor amount bandwidth saved.

Looks good. Tested.

Yep. Looks good


Converting a list to a set

I am trying to convert a Python list to a Python set in Rust. I’ve found two ways to do it, but they feel like workarounds. Is there is a better way?
Calling eval:
    let list: &PyAny = list;
    let set: &PyAny = py.eval("set", None, None)?.call((list,), None)?;

Calling unsafe functions:
    let list: &PyAny = list;
    let set_object: PyObject = unsafe {
        PyObject::from_owned_ptr_or_panic(py, PySet_New(list.as_ptr()))
    };
    let set: &PyAny = &set_object.as_ref(py);

You should be able to get the set type using PySet::type_object(), then call it with the list as argument via the  object protocol.

As this has been answered, closing for now.


Bound RT #2 - Request Bound Refresh Token

This PR:

Adds stk_jwk attribute to /token request body in AuthorizationCodeClient in order to request bound refresh tokens from ESTS
Adds an msal-browser sample to test refresh token binding
Extends AuthorizationCodeClient tests to include stkJwk in every test request

Codecov Report

Merging #3505 (82241e0) into bound-rt-stk (8d90c0e) will decrease coverage by 3.86%.
The diff coverage is 91.66%.

Flag
Coverage Δ

*Carryforward flag

msal-angular
95.81% <ø> (ø)

Carriedforward from 80e1ba0

msal-browser
84.55% <ø> (?)

Carriedforward from 80e1ba0

msal-common
83.32% <91.66%> (?)

Carriedforward from 80e1ba0

msal-core
73.02% <ø> (?)

Carriedforward from 80e1ba0

msal-node
78.39% <ø> (ø)

msal-react
93.77% <ø> (ø)

Carriedforward from 80e1ba0

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files
Coverage Δ

.../msal-common/src/client/AuthorizationCodeClient.ts
85.31% <66.66%> (ø)

lib/msal-common/src/client/BaseClient.ts
75.86% <100.00%> (ø)

...msal-common/src/request/RequestParameterBuilder.ts
92.03% <100.00%> (ø)

...mon/src/telemetry/server/ServerTelemetryManager.ts
94.59% <0.00%> (ø)

...sal-common/src/cache/entities/AccessTokenEntity.ts
83.78% <0.00%> (ø)

lib/msal-common/src/logger/Logger.ts
86.88% <0.00%> (ø)

...ib/msal-common/src/cache/entities/AccountEntity.ts
73.86% <0.00%> (ø)

...msal-common/src/cache/entities/ThrottlingEntity.ts
100.00% <0.00%> (ø)

lib/msal-browser/src/event/EventType.ts
100.00% <0.00%> (ø)

lib/msal-common/src/client/RefreshTokenClient.ts
75.94% <0.00%> (ø)

... and 92 more


Missing functions from docs

Some of these are for binding developers only, but still worth mentioning somewhere I think:

[x] add
[x] subtract
[x] multiply
[x] divide
[x] fdiv
[x] fmod
[x] import_database
[x] show_databases
[x] #1145
[x] array_intersect
[x] constant_or_null
[x] count_if
[x] #1144
[x] date_add
[x] https://github.com/duckdb/duckdb-web/pull/1176
[x] enable_profile
[x] disable_profile
[ ] all_profiling_output
[ ] pragma_detailed_profiling_output
[ ] pragma_last_profiling_output
[x] ilike_escape
[x] not_ilike_escape
[x] repeat_row
[x] #1177
[x] #1178

Some of these are aliases for functions that are documented, but they should still be recorded somewhere

array_intersect has also been added back #1150 😉

@Mause thanks for collecting these, it was super helpful!

@Mause thanks for collecting these, it was super helpful!

This list was generated by the Check Docs job - latest run is https://github.com/duckdb/duckdb-web/actions/runs/6992021674


Amend Users factories according to new permissions

Also, use the amended factories in some controller specs.

see codevise/pageflow#504


Feature Request : copy startup.jl when updating

Hi,
I just updated from 1.8.1 to 1.8.2 and the whole juliaup/julia-1.8.1+0.x64 folder is gone, with my startup.jl script.
I think copying that file over to the new folder would be a reasonable behaviour, or maybe show a prompt asking if we want to keep that file ?

Maybe I'm misunderstanding but if you simply put your startup.jl into ~/.julia/config it will always be used (irrespective of what juliaup does and which julia version is used).

As a user you should treat the whole .julia/juliaup folder as read-only, or rather all its content being managed by Juliaup. For user provided startup files, use the location that @carstenbauer recommended.