Credit where it's due

The README currently says that the Django implementation is used, but I believe the implementation was originally the work of Marcel Hellkamp (@defnull) in bottle.py.
While it will always be tricky to pin down the "true source" of a piece of code, the git histories of bottle and django may be of some help. The cached_property decorator appeared in bottle a month before it appeared in django.
in bottle, Aug 2011: https://github.com/bottlepy/bottle/commit/fa7733e075da0d790d809aa3d2f53071897e6f76
in django, Sept 2011: https://github.com/django/django/commit/5009e45dfe366ebf520eecb49d72d5a11cee1623
Also, your docstring and variables names are exactly identical to Marcel's.
And one last friendly reminder: the licenses of both bottle and django (MIT and BSD, respectively) require a copyright notice to be posted.

https://github.com/mitsuhiko/werkzeug/blame/3c9905f9a490b245dff7fa1d9d60e4b371c02608/werkzeug/utils.py#L658 blames to 2007 the commit is from 2009
i wonder of @mitsuhiko came up with it while experimenting with the descriptor protocol, or if it arose differently
i vaguely recall earlier iterations - for quite a while it was a data descriptor before it got turned into a non-data descriptor

Looks like birkenfeld introduced the function in 2007 https://github.com/mitsuhiko/werkzeug/commit/2fe4c8f24b42ba2d6f75ebe75dbc2ef80561fb8f
He's the one :)

This also means that someone broke the nice properties of the decorator later by turning it into a data descriptor, then fixing it again in werkzeug 0.6, which perhaps explains why alex remembers talking about it with mitsuhiko at a later point.

The code at https://wiki.python.org/moin/PythonDecoratorLibrary#Cached_Properties makes me wish people added more specific date stamps to their code snippets. :P

I was the one, who a wrote and added that code. You can find the exact timestamp when it was added in the page history:
https://wiki.python.org/moin/PythonDecoratorLibrary?action=info
It's revision 103 from 2011-06-08 11:52:04
I probably wrote and used that code in closed-source projects before that. So, I think deserve some credit for the cached_property_ttl too :). At least the implementation is very similar.

In case someone cares, lazy_property was not the first version. The trick with the data only descriptor comes from an earlier codebase but not sure which one. Might have been in the original pocoo project or alternatively in wsgitools or whatever that was called. Original author was probably either Georg or me.

Here's the one from Pyramid (then called repoze.bfg) from 2009: https://github.com/Pylons/pyramid/blob/5babbaf48a71af786d41f59a1f1f7d5272a60a4d/repoze/bfg/decorator.py#L1


Switch to standard state restoration mechanism

I started looking at state restoration because I wanted to fix #547. I didn't quite figure out the best way to implement that but in the process of poking at it I revised the main window restoration approach to use standard state restoration. I noticed in #134 you mentioned wanting to use standard mechanism if possible so I offer this revision in that spirit. I don't think you need to include the manual window frame autosave name stuff either because I think it's automatically handled by AppKit's default state restoration.

This commit broke saving the window state on quit.
Now on every restart the window is reset and appears really small.

@rex4539 Thanks for letting me know. Can you tell me anything more about your system? Is it a 10.14.3 macOS or something else?
Also can you verify that even after you change the window size back to something big, that quitting and reopening NetNewsWire it shows up small again? I wouldn't be surprised if existing saved state from before this commit is not restored.

I'm on 10.13.6
I can verify that changing anything on the window, quitting and relaunching, the app is reset to defaults.

@rex4539 Thanks. I'll take a closer look. I'm on 10.14 so I haven't tested the changes against 10.13.

I am able to reproduce the small window problem described by @rex4539, when I build and run the app on 10.13.

I opened ticket #550 to track the fix for this issue.


file_name is not working

[Please easy english or easy japanese]
Description
Environment

@SayedShalan Please details

close by no response


IOU Participant page search validation

Details
Added search validation for IOU Participant Pages also like as it is in New Chat/Group search pages
Fixed Issues

$ https://github.com/Expensify/App/issues/4690
Tests & QA Steps

Click ➕  FAB icon.
Select New IOU Request/Split options
Enter invalid search input

Fix
A validation message will show for invalid inputs on IOU participant pages search also.
Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

Hi @Santhosh-Sellavel, I've placed this issue on hold as per this update, as we are prioritising issues related to a feature release scheduled for 9/24. As an apology for the delay, we will add a $100 bonus as a thank you for waiting.

@Santhosh-Sellavel Video.
output_file.mp4

Ok, I get it now.

🚀 Deployed to staging by @marcaaron in version: 1.1.8-10 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Add accelerator table

Closes: #1373
Description
Added Accelerator profile table

[X] Render the following columns: Device identifier, display name/description, ennoblement switch, date last modified, action button
[X] Columns (except for action column) must be sortable
[X] include help icons where present in the docs
[X] should include pagination
[X] ellipsis action button should include: edit, delete
[X] hook to fetch accelerator CRDs

How Has This Been Tested?

Add accelerator profile CR's to your cluster.
Login to ODH dashboard with clusteradmin
Navigate to settings < Accelerator profiles
You can see the Accelerator table, with all it's fields, sortable columns, and action buttons.

Test Impact
Added storybook component and integration test.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[x] Included any necessary screenshots or gifs if it was a UI change.
[x] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

@yannnz

@dpanshug I think the test is failing. it could be an aria issue

checked over once more. all looks good


Need published style guide and tooling to enforce

Everyone agrees that from a style perspective, the intent is to have consistency in the code to make it more readable and maintainable.   Update https://github.com/PowerShell/PowerShell/blob/master/docs/dev-process/coding-guidelines.md as needed, but should be enforced by tooling and not by PR comments.

[ ] enforcement on the CI side
[ ] enforcement on the developer side (part of Start-PSPester?)

We already have PR #3504 for CI side and request from @lzybkr for developer side (git commit hooks).

@iSazonov you can close this once that PR is merged.  Thanks!

The PR s problematic - we can't merge it until we fix all files in the repo.
Also I believe we should address git commit hooks in another PR - I never write such hooks.
/cc @lzybkr

@TravisEz13 Could you please comment? I think you have more experience on this and have some ideas about how we can gradually roll out the files that are covered by the formatting checks.

I see GitHub introduce Checks. Can we use this?

I've seen other teams using https://www.codefactor.io/

Screenshots look ver interesting. Can we try this in the repo?

@SteveL-MSFT @daxian-dbw @adityapatwardhan  What do you think?  Can we try codefactor.io?

@TravisEz13 I'm open to trying it out.  I'll set it up.

I am open to trying it as long as it does not block PRs from being merged, at least to begin with.

https://www.codefactor.io/repository/github/powershell/powershell/overview/master

Thanks! Looks great.

Have your own StyleCop rules? No problem, simply add Settings.StyleCop file to the root of this branch.

We can configure rules which we want.

Overall grade is C - Satisfactory.
We could show the status on our main page.
Perhaps we should work now to get into B status.
I selectively reviewed the results of CodeFactor.
Most commonly found Duplicate Code and Complex Method. Others are rare.
Seems we can easily address most of CodeFactor Issues.

Duplication rules should be disabled. - it seems completely useless.

I believe we should disable unneeded rules and fix most of style issues.
Motivation - conservative policy is very good for a closed project, for an open project we have to continuously discuss the style issues that slows code reviews and leads to the perplexity of contributors.

@iSazonov I wouldn't call that rule useless. It shows code reuse where we could refactor to a utility method or something. But refactoring those issues may be high risk.

@iSazonov I wasn't saying we shouldn't disable the rule, just that it wasn't completely useless. :)

We need new policy and roadmap.

I agree it isn't useless, but many of the suggested refactoring to remove duplication is risky.  It would be nice to be able to leave it on as informational if that is an option.

duplication

I see only 519 issue so it's not intrusive and we can leave this as is.

@powercode We're open to trying other tools if you're aware of any.

CodeFactor is only control tool. We could use https://github.com/dotnet/codeformatter but it also requires a lot of effort.

I just think we should do this the other way around. Start with giving people the tools to format the source, and then start to enforce it on pull requests.
This is of course a matter of opinion, but I don't think the gain (if any) in readability and maintainability is worth the hassle.
I'm working on getting a ReSharper profile setup for the project that has formatting options that are at least close to Code Factor. I know it is a commercial tool, but a lot of C# devs has it. That could east the pain a bit.
I installed StyleCop locally, but got lots of errors with spelling, and didn't figure out how to make it use the existing spelling dictionary.
In summary, it is not so much the tool I object to, as the backward order this is introduced in.
Tools first, then checks, not the other way around.

CodeFormatter doesn't work with PowerShell Core csproj files https://github.com/dotnet/codeformatter/issues/256

From @daxian-dbw

About the style rules, @TravisEz13, @adityapatwardhan and I went through all issues reported from CodeFactor a few weeks back, and we got a list of rules that we think should be turned off. Here is the list:
1305: SA1305FieldNamesMustNotUseHungarianNotation
1502: SA1502ElementMustNotBeOnSingleLine
1310: SA1310FieldNamesMustNotContainUnderscore,
1204: SA1204StaticElementsMustAppearBeforeInstanceElements
1009: SA1009ClosingParenthesisMustBeSpacedCorrectly
1501:SA1501StatementMustNotBeOnSingleLine
1513:SA1513ClosingBraceMustBeFollowedByBlankLine
1306:SA1306FieldNamesMustBeginWithLowerCaseLetter
1308:SA1308VariableNamesMustNotBePrefixed
1013:SA1013ClosingBracesMustBeSpacedCorrectly
1500:SA1500BracesForMultiLineStatementsMustNotShareLine
1010:SA1010OpeningSquareBracketsMustBeSpacedCorrectly
1026:SA1026CodeMustNotContainSpaceAfterNewKeywordInImplicitlyTypedArrayAllocation
1008:SA1008OpeningParenthesisMustBeSpacedCorrectly
1311:SA1311StaticReadonlyFieldsMustBeginWithUpperCaseLetter
1025:SA1025CodeMustNotContainMultipleWhitespaceInARow
1012:SA1012OpeningBracesMustBeSpacedCorrectly
1215:SA1215InstanceReadonlyElementsMustAppearBeforeInstanceNonReadonlyElements
1214:SA1214ReadonlyElementsMustAppearBeforeNonReadonlyElements
1210:SA1210UsingDirectivesMustBeOrderedAlphabeticallyByNamespace
1609:SA1609PropertyDocumentationMustHaveValue

The rules about "one parameter per line" for method definition or invocation is not in this list, but in my opinion, we probably should disable that rule because 1) it doesn't bring much benefit -- as long as the parameters are well aligned, there is no readability issue; 2) there are too many instances in our existing code base that are violating that rule, and fixing all doesn't worth the time.
The following document rules make sense for public members, but they are applied to non-public members too, which causes a lot of noise data.
1611:SA1611ElementParametersMustBeDocumented
1615:SA1615ElementReturnValueMustBeDocumented
1606:SA1606ElementDocumentationMustHaveSummaryText

Sample of formatting with codeformatter that I compiled ##7263

@SteveL-MSFT is this okay to close now?

Do we have an omnisharp.json in the repo with the mentioned style rules set for VS Code users? Might be a good idea to do so if we haven't.
Also, I opened another issue already, but codefactor should definitely come back for those edge cases and misc recommendations.

@joeyaiello no, we need to integrate with CI

@vexx32 We have .editorconfig as unified config for all editors.


What does the number mean in the prompt?

Hi, thanks for open-sourcing this awesome work. I noticed that in the prompt (e.g., UV map, (Sci-Fi digital painting:1.3), high quality, best quality), there are numbers such as 1.3. I'm wondering what does it mean? How can we write correct prompt to use the model?

It is used to emphasize prompts. You can find more details on its usage here.

Got it. Thanks for the quick reply!


Add info on caching and private endpoints. Closes #138

Codecov Report

Merging #162 into master will decrease coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #162      +/-   ##
==========================================
- Coverage   34.94%   34.82%   -0.12%
==========================================
  Files         118      118
  Lines        4627     4614      -13
==========================================
- Hits         1617     1607      -10
+ Misses       3010     3007       -3


Feature/10616

This check does mean that checks further down the component test have additional failures so that has had to be updated

This looks good.


Optionally exclude logs and/or result browsers when downloading test results in non-interactive mode

When running XLT mastercontroller in non-interactive mode, download of test results will always include logs and result browsers. This might be fine in most cases but sometimes log files and even result browsers may not be needed and/or users simply want to improve download speed by restricting the amount of test results.
For this reasons, XLT mastercontroller should offer an appropriate command line option (or multiple ones) that can be used to restrict the download to certain data types and is effective in non-interactive mode only, e.g. noLogs and noResultBrowsers. Please notice that noResultBrowsers also implies noLogs.

I suggest to avoid including something indirectly in another option. So noResultBrowsers must not exclude logs, because the name does not imply that. The command line does not have to show the same logic as the UI does. Once implemented we can never change that again easily.
The noDownload option already says download nothing. I suggest to make it clearer what the options do, because noLogs does not indicate anything in regards to a download for instance. Suggestion: noResultBrowserDownload and noLogsDownload which fits noDownload but they are all not really nicely named options.
Please don't forget that there is a commands option that needs different options too.

Thanks for your feedback @rschwietzke .
Then let's start with a single new option named download that takes a comma-separated list of data types as argument. The argument is not optional. Possible values are logs, measurements and resultbrowsers.
In case the option is not given, then all data types will be downloaded. This is equivalent to specifying all data types as option value.
The options download and noDownload are mutually exclusive. XLT mastercontroller will exit with an error in case both were given.


Running TagUI in Git Bash in Windows fails

Various errors occur as Git Bash runs as if it's in linux but it's actually on windows.
So TagUI should not be used in Git Bash on windows.
Maybe the error msg could highlight this possibility.

But how we would tell that they are running on git bash on windows? For me, I errored here:
chrome_command="google-chrome"
if ! type "$chrome_command" > /dev/null; then
  echo "ERROR - cannot find Chrome command \"$chrome_command\""
  echo "update chrome_command setting in tagui/src/tagui and make sure symlink to command is created"; exit 1; fi

Does it make sense to warn them about the possibility of them using git bash on windows here? or is there a better way to check and error out?

Yes this is the expected behaviour by design. For Windows users, run TagUI directly from the command prompt or power shell. Git Bash is not a real Linux environment, it is only a bash shell running in Windows. Thus running TagUI in it will not work.
For now it's sufficient that they search issues and see this issue for solution. Also, from the to use section and the tutorial, there is explicit step to open command prompt. So users who using alternative environments if they follow the steps there they'll be fine.
https://github.com/kelaberetiv/TagUI#to-use
There should be technically possible solution, but not recommend to handle via error handling, because will be opening up a can of worms. To handle this error means we should also handle the situation where Windows users trying to run other Linux shells or VMs on Windows, which may not work as expected.
But it is hard to try to address all those cases. As TagUI already tries to make any new feature or change work for macOS, Linux and Windows, further addressing the sub-cases would make the project much harder to maintain at the gain of making it easier for the minority of users who happen to be using alternative shell in Windows and also never follow the step by step guide in To Use and Tutorial section.

Eg maintaining software across multiple OSes is so challenging that even for unicorn commercial RPA software, they are only supporting Windows OS. None of them has releases for macOS / Linux.

But cross-platform solutions such as Electron, NodeJS, Python etc, is changing this old paradigm, and make it more accessible to develop cross-platform apps that work with minimal localisation.


Update setup.sh

trying to improve setup.sh
modified this file so that a user can remotely execute this without downloading it first
rclone mv command was failing so I modified it to cp -rf. cp will overwrite files in a directory and makes the whole script more robust and it can be used as a "updater" as well.
Rclone command now pulls latest stable.
added "git" to the install list
added command to auto-move git repo contents to users root directory.
hardcoded rclone directory's because the asterisks in or with the variables were failing for me.
Please let me know if any of this is helpful.

I like the changes except for the rclone versioning.
As mentioned in the review I prefer to have the version in the url, to make sure I know what version I'm downloading.
The other changes are very helpful, thank you!


Develop a remote on-boarding process

Parent objective:  #4
Progress: 100%

[x] [P1] Gain feedback on onboarding from every member who joined after the current implementation of onboarding guide
[x] [P1] Have a complete onboarding guide on GitHub

Seems to be done. Our onboarding process is well-defined on GitHub that is very useful for remote people and took into consideration the feedback from members of the last months. Of course, it can be improved at any moment that we find missing information.


Question for my Research Project – Flight Simulator 2024 with Apple Vision Pro

Hello,
I'm currently working on a research project involving Flight Simulator 2024 with the Apple Vision Pro, and I'm trying to implement eye-tracking and hand-tracking.
For hand-tracking, I can see my hands, but I can't seem to interact with or press any buttons or controls in the cockpit. Eye-tracking also doesn't seem to work. I've read a few reports about this issue, but if these features aren't supported, I would like to cite this page as a source.
Your input would be greatly appreciated! I will share the final paper once it's done – it’s a really exciting project! 😊
Thank you <3

Eye tracking is an Apple limitation, technically there's extremely limited support but it's a side-channel exploit based on screen recording, requires the RealityKit (40PPD) renderer, and is basically only good for social VR. SteamVR has yet to expose foveated rendering as well unfortunately.
Hand tracking with SteamVR input 2.0 works by having two separate hand tracking controllers (these will have appropriate icons in the next streamer version) which activate based on a hysteresis--if controller inputs are used, the hand tracking controllers are disabled for 5 seconds or so. However, if the game supports SteamVR skeletal input or XR_EXT_hand_tracking then it will work. Maybe also try disabling SteamVR input 2.0 so that skeletons are sent directly to the main controllers. But ultimately it's up to the game to support it.
If it works with other headsets, it could be a bug with the hand tracking skeleton, I already found a few bugs with the basis vector directions so it wouldn't be the first time, and the XR_EXT_hand_tracking basis vectors are specifically designed for interactions, whereas SteamVR's skeletons are designed for animation. So any errors on our part would possibly result in bugs.


Elementum Music Source

Right now Elementum works great for Movies and TV shows. It's easy to set up as a way to watch TV/movies, and in the process build up a large library of video files.
I would love for this to be expanded to music, as currently there is no Kodi source for music torrent files. How hard would it be to add basic music functionality? Ideally it would support something like Last.FM for tracking listening, but I guess that can come later.
I've never made a Kodi plugin, but I'll start looking at the source. Any tips would be appreciated.

Also, I can't seem to find the developers guide mentioned in the readme

i think there was question like this already, can't find it.
something like
https://github.com/elgatito/plugin.video.elementum/issues/503
but more fresh, iirc.

Ah, yeah I forgot about that, it was me. I'd love to leverage as much of Elementum as possible to do this, but I've got a bit of learning to do.

It is not easy to do that inside of Elementum. Instead, it should be easier to write a python addon that uses some open API (if there is any) to browse music information, and then sends requests to Elementum to download something.


Crash after 1 day

Thread 'tokio-runtime-worker' panicked at 'assertion failed: false', /home/jasl/.cargo/git/checkouts/substrate-7e08433d4c370a21/1404f2a/client/network/src/protocol/notifications/behaviour.rs:1720

https://github.com/AcalaNetwork/Acala/issues/851
Using commit https://github.com/paritytech/substrate/commit/1404f2af4cbe90d35b4c8a1405a9452feb789adc

@tomaka

Note that this is a debug_assert!. It won't happen if you compile with --release.

I'm confident that I fixed this and forgot to link to this issue.


Update maintainers

Update maintainers

@npalm do you want to be a maintainer?

Yes, see #17  @JeroenKnoops


Update test results titles to include service directory and cloud names

When testing with multiple clouds, it can be hard to tell from the coverage view which failures come from which cloud and/or job.

/azp run python - appconfiguration - tests


Revert "Bring back tar vBump"

This is causing a build break in the webmode CI build.  It looks like the version of tar being patched is not completely compatible with gulp-untar and is causing an exception in the nodejs() function in the gulp.reh build script.
// in file .../azuredatastudio/node_modules/gulp-untar/index.js
var parse = require('tar').Parse // import "parse" symbol

// ...

contentsStream
    .pipe(parse()) // call parse like a function but it's a class

Generates this exception
Exception has occurred: TypeError: Class constructors cannot be invoked without 'new'
  at DestroyableTransform._transform (/Users/kburtram/repos/web/azuredatastudio/node_modules/gulp-untar/index.js:25:11)
    at DestroyableTransform.Transform._read (/Users/kburtram/repos/web/azuredatastudio/node_modules/readable-stream/lib/_stream_transform.js:184:10)
    at DestroyableTransform.Transform._write (/Users/kburtram/repos/web/azuredatastudio/node_modules/readable-stream/lib/_stream_transform.js:172:83)
    at doWrite (/Users/kburtram/repos/web/azuredatastudio/node_modules/readable-stream/lib/_stream_writable.js:428:64)
    at writeOrBuffer (/Users/kburtram/repos/web/azuredatastudio/node_modules/readable-stream/lib/_stream_writable.js:417:5)
    at DestroyableTransform.Writable.write (/Users/kburtram/repos/web/azuredatastudio/node_modules/readable-stream/lib/_stream_writable.js:334:11)
    at DestroyableTransform.ondata (/Users/kburtram/repos/web/azuredatastudio/node_modules/readable-stream/lib/_stream_readable.js:619:20)
    at DestroyableTransform.emit (node:events:527:28)
    at DestroyableTransform.emit (node:domain:537:15)
    at addChunk (/Users/kburtram/repos/web/azuredatastudio/node_modules/readable-stream/lib/_stream_readable.js:291:12)
    at readableAddChunk (/Users/kburtram/repos/web/azuredatastudio/node_modules/readable-stream/lib/_stream_readable.js:278:11)
    at DestroyableTransform.Readable.push (/Users/kburtram/repos/web/azuredatastudio/node_modules/readable-stream/lib/_stream_readable.js:245:10)
    at DestroyableTransform.Transform.push (/Users/kburtram/repos/web/azuredatastudio/node_modules/readable-stream/lib/_stream_transform.js:148:32)
    at DestroyableTransform.<anonymous> (/Users/kburtram/repos/web/azuredatastudio/node_modules/gulp-gunzip/index.js:28:14)
    at Gunzip.zlibBufferOnEnd (node:zlib:161:10)
    at Gunzip.emit (node:events:527:28)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
28180

Relevant Lines:
62343

💛  - Coveralls


When Microsoft provides SCIM package support on .NET Standard?

I had to face this issue while adding Microsoft.SystemForCrossDomainIdentityManagement package in my .Net Standard app.
For now, I just moved to .Net Framework but I need .Net Standard support for it.
Warning NU1701 Package 'Microsoft.SystemForCrossDomainIdentityManagement <IP_ADDRESS>' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework '.NETStandard,Version=v2.0'. This package may not be fully compatible with your project.

This issue does not apply to the code in this repository, the target framework is netcoreapp3.1


tsc generating TS5055 error when generating declaration files

I'm consistently getting the following error when compiling any .ts file:
error TS5055: Cannot write file 'dist/[source-file-name].d.ts' because it would overwrite input file.
The compiler should be willing to overwrite the declarations files any time it recompiles.   There are no permissions issues and this seems to be a new problem introduced recently since I moved from a stable ts1.7 release to using typescript@next releases (I'm currently on last night's - i.e. Version 1.8.0-dev.20151210).
I'm using tsc --watch with the following tsconfig.json file:
{
  "compilerOptions": {
    "target": "es6",
    "moduleResolution": "node",
    "module": "commonjs",
    "preserveConstEnums": true,
    "declaration": true,
    "noImplicitAny": false,
    "removeComments": true,
    "noLib": false,
    "sourceMap": false,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "outDir": "./dist"
  },
  "exclude": ["node_modules", "jspm_packages"],
  "filesGlob": [
    "./src/**/*.ts"
  ]
}

(NOTE - the filesGlob above is not appearing correctly due to github reformatting..... it is actually:
./src/[asterix][asterix]/[asterix].ts
just in case you thought I have a bad tsconfig)
Thank you!

I can see a user getting extremely frustrated that we blindly overwrote a file that they won't be able to recover. I think the protection introduced is likely to outweigh the effort in workarounds. Any thoughts @mhegazy?

But I’m asking tsc to generate the file, and it’s a definition file, so it
should be free to do this.    This has certainly been the case until
recently.
Thanks for your quick response,
PB
On Thu, Dec 10, 2015 at 4:56 PM, Daniel Rosenwasser <
<EMAIL_ADDRESS>wrote:

I can see a user getting extremely frustrated that we blindly overwrote a
file that they won't be able to recover. I think the protection introduced
is likely to outweigh the effort in workarounds. Any thoughts @mhegazy
https://github.com/mhegazy?
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/6046#issuecomment-163790152
.

can you add ./dist to the exclude list?

I seem to be missing something.......
The way I have my tsconfig set up, I'm asking tsc to "please generate
definition files for me".
It will generate one when there's not one already there, but then when I
change the .ts file it complains and says "I can't overwrite the one that I
just generated".
A similar argument could be made for the .js files that are emitted by the
compiler (i.e. Even though you changed the .ts file and invoked the
compiler, I can't write a new .js file because there is already one
there).......
..... Again, am I missing something?
On Thursday, December 10, 2015, Mohamed Hegazy<EMAIL_ADDRESS>wrote:

can you add ./dist to the exclude list?
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/6046#issuecomment-163798320
.

You are asking the compiler to overwrite an input file. Seeing as we are planning to support .js files as input files, yes, I would be inclined to say that we should not allow you to overwrite an input file.

After thinking about this a little more, it's probably a situation where you're damned if you do and damned if you don't (i.e. one could see it from either perspective).......
In any event, per @mhegazy's suggestion, simply 'excluding' the dist directory works in my case.   I'm wondering if there will be knock-on effects if/when file globbing patterns are allowed and folks are doing 'in-place' compilation (i.e. same directory).   We'll see.
Thanks for all your help.

No prob, thanks for filing the issue. It's always worth talking over.

Appreciate it - have a nice W/E
On Fri, Dec 11, 2015 at 11:45 AM, Daniel Rosenwasser <
<EMAIL_ADDRESS>wrote:

No prob, thanks for filing the issue. It's always worth talking over.
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/6046#issuecomment-164014740
.

Is there a reasonable workaround for people who need the declaration option to be compatible with in-place compiling?  My workflow is to let Visual Studio handle my typescript build, and then use Visual Studio as my debugger.  So it feels like in-place compiling is the most obvious way for this to work.

@mavericken i do not think this is related to the OP. please file a different issue and provide more information about what you are running into. --d is supported and it emits files next to your sources just like the .js and .map files by default.

While I appreciate the warning, I think we can improve the messaging.  It's a bit of a red herring, much like this discussion.  Here's what I found: I'm working in Windows, not Linux.  Case Sensitivity isnt as much of a big deal here in Windows land.  I made a change to the class because, at first, it was lower cased, but I preferred the class name starting with upper case.  well the previous lower.d.ts was hanging around when i transpiled.  This generated the error.  The transpiler intended to replace a "Lower.d.ts", instead it found a "lower.d.ts".  Once I deleted the "lower.d.ts", this error disappeared.  If you could add this to the exception message, it might help some folks resolve this issue.  Or better yet, make an exception that raises when such a case occurs.  Thanks.  Btw, I wouldnt touch javaScript with a ten-foot pole, but TypeScript has made front-end work less anxiety-ridden.  Thanks, again!

error TS5055: Cannot write file 'dist/index.d.ts' because it would overwrite input file.
index.d.ts is not an input file - its a file I just asked to be created. When I compile a .ts file to javascript, I don't get an error about index.js already existing, so why the error for .d.ts?

@NickGrease the compiler thinks it is an input. can you run tsc --listFiles? do you see it there?
if not, then its a bug, please provide some additional information for us to be able to reproduce it. if you do see it, then one of your files import module "dist" or have a ///<reference to it

In my understanding "--watch" and "--declaration" in combination dosen´t make sense. TSC generates the .d.ts files (--declaration) and triggers right again because --watch watches the declaration-files too (they end on .ts) and fires because they were changed by itself, resulting in a compile loop.
This doesn´t make sense in my eyes. TSC should ignore ".d.ts"-files if the "--declaration" option is activated.

Is there any way to just suppress this check? -- Like a command line argument to turn this off? -- It's causing a lot of trouble.

In my understanding "--watch" and "--declaration" in combination dosen´t make sense. TSC generates the .d.ts files (--declaration) and triggers right again because --watch watches the declaration-files too (they end on .ts) and fires because they were changed by itself, resulting in a compile loop.

This is not accurate. the way this wold happen is as i noted erlier, if your .d.ts file is some how included in your project.

This doesn´t make sense in my eyes. TSC should ignore ".d.ts"-files if the "--declaration" option is activated.

tsc does ignore .d.ts files that it believes it has generated.

So in case of "--declaration" .d.ts-files are no input files, but output-files and should be treated as such.
Unfortunately one cannot exclude "*.d.ts" in the exclude-option. This would be a workaround but in my case it isn´t recognized.

I would be happy to look at your project if you have one to share.

Is there any way to just suppress this check? -- Like a command line argument to turn this off? -- It's clearly causing a lot of trouble.

The check tells you the compiler is about to override an input file. the compiler will not override your input file, cause this would be user data loss..
So either the file is in your input (use tsc --listFiles to know), or it is a bug. if it is the former please exclude the .d.ts file from your input, if it is the later, please file a new issue and share your project.

The directory which has the tsconfig.json file is considered as a root of the application. The "d.ts" files in the root directory or all of its sub directories would be automatically included. if you generate the "d.ts" files in any of the subdirectory of the root, you would see this error. if you generate the "d.ts" file to some other directory outside of the root directory, then you would be fine.
you can change the location of declartion tile by setting the "declarationDir" variable in the tsconfig.json

I got this error when by mistake I managed to import a file from my dist folder in a src file.


Rx >>= operator should be changed to <<=

Problem
The current api por a Rx object could be confused for emit a new value in a Rx implementation
https://github.com/jonataslaw/getx/blob/d942581e47f797647ee7e95a7554a540d0ca0117/lib/src/state_manager/rx/rx_core/rx_impl.dart#L25
// Currently
counter >>= 3; // Is counter injecting data to a const value?

// Should be
counter <<= 3; // A const value is injected to counter

Regardless of whether the feature is completed or tested, the operator should be according to its intention.

@roipeker What do you think?
How did you implement this feature, I'll let you answer that

@jonataslaw, @kranfix I implemented the << feature based on "votes" :D , it was marked as experimental, and since most of devs are already using rx.value or rx() ... I didn't touch it again.
I definitly agree with the << operator, makes more "sense" (although still looks very strange).

I know that it's strange in Flutter, but as an old C++ dev, the << operator is very clear.
std::cout << "some value" << endl;

Where cout is a stream object.

On the other hand, this discussion it not about whether that feature should exist (I would like to), but also whether the operator is best meanwhile or later.

@roipeker If you are agree, will you update it or do you prefer me to send a PR?


[Multiwfn for MacOS] build failure

Operating system
Mac OS, Apple chip
Compiler
No response
Steps to reproduce the behavior
conda install gcc
conda install cmake
conda install openblas
conda install flint
conda install gfortran
conda install arb
git clone --branch source_dist https://github.com/digital-chemistry-laboratory/multiwfn-mac-build.git
cd multiwfn-mac-build
cmake -B build

Failure logs
cmake -B build
-- The Fortran compiler identification is GNU 11.3.0
arm64-apple-darwin20.0.0-gfortran: warning: could not understand version ‘14.00.00’
-- Checking whether Fortran compiler has -isysroot
-- Checking whether Fortran compiler has -isysroot - yes
-- Checking whether Fortran compiler supports OSX deployment target flag
-- Checking whether Fortran compiler supports OSX deployment target flag - yes
-- Detecting Fortran compiler ABI info
-- Detecting Fortran compiler ABI info - failed
-- Check for working Fortran compiler: /opt/anaconda3/bin/arm64-apple-darwin20.0.0-gfortran
-- Check for working Fortran compiler: /opt/anaconda3/bin/arm64-apple-darwin20.0.0-gfortran - broken
CMake Error at /opt/anaconda3/share/cmake-3.26/Modules/CMakeTestFortranCompiler.cmake:59 (message):
The Fortran compiler
"/opt/anaconda3/bin/arm64-apple-darwin20.0.0-gfortran"

is not able to compile a simple test program.
It fails with the following output:
Change Dir: /Users/m/multiwfn-mac-build/build/CMakeFiles/CMakeScratch/TryCompile-maCfQ9

Run Build Command(s):/opt/anaconda3/bin/cmake -E env VERBOSE=1 /usr/bin/make -f Makefile cmTC_0766b/fast && /Library/Developer/CommandLineTools/usr/bin/make  -f CMakeFiles/cmTC_0766b.dir/build.make CMakeFiles/cmTC_0766b.dir/build
Building Fortran object CMakeFiles/cmTC_0766b.dir/testFortranCompiler.f.o
/opt/anaconda3/bin/arm64-apple-darwin20.0.0-gfortran   -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX14.4.sdk -mmacosx-version-min=14.3 -c /Users/m/multiwfn-mac-build/build/CMakeFiles/CMakeScratch/TryCompile-maCfQ9/testFortranCompiler.f -o CMakeFiles/cmTC_0766b.dir/testFortranCompiler.f.o
arm64-apple-darwin20.0.0-gfortran: warning: ‘14.3’ is not valid for ‘-mmacosx-version-min’
Linking Fortran executable cmTC_0766b
/opt/anaconda3/bin/cmake -E cmake_link_script CMakeFiles/cmTC_0766b.dir/link.txt --verbose=1
/opt/anaconda3/bin/arm64-apple-darwin20.0.0-gfortran  -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX14.4.sdk -mmacosx-version-min=14.3 CMakeFiles/cmTC_0766b.dir/testFortranCompiler.f.o -o cmTC_0766b
arm64-apple-darwin20.0.0-gfortran: warning: ‘14.3’ is not valid for ‘-mmacosx-version-min’
ld: -rpath can only be used when targeting Mac OS X 10.5 or later
collect2: error: ld returned 1 exit status
make[1]: *** [cmTC_0766b] Error 1
make: *** [cmTC_0766b/fast] Error 2

CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:2 (project)
Additional context
No response

Conda is not here.

How to deal with this question? Could you do me a favor?
---- Replied Message ----
| From | Kai @.> |
| Date | 09/27/2024 11:56 |
| To | microsoft/vcpkg @.> |
| Cc | sorahiro @.>,
Author @.> |
| Subject | Re: [microsoft/vcpkg] [Multiwfn for MacOS] build failure (Issue #41210) |
Conda is not here.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

The issue doesn't show any connection to vcpgk.
You install from conda.
You clone https://github.com/digital-chemistry-laboratory/multiwfn-mac-build.git.
I suggest reporting your issue there.

Unrelated issue.


Why is every Patchlevel++ commited?

No feature code added. Is there a commit highscore?
The package.json must change in a relationship of a feature and before test, build and deploy.
Or not?

I'm not sure what you're asking - do you mean our versioning strategy, or how we organize our development in commits and pull requests?

I mean this ...
Why changing patch level of deps without new atom feature code? Only in relationship to new code or before code freeze.
sry, but so, we commit sometimes package.jsons without effect ... ???
@izuzak
:arrow_up<EMAIL_ADDRESS>izuzak committed 5 days ago
3595666
@izuzak
:arrow_up<EMAIL_ADDRESS>izuzak committed 5 days ago
4699fa4
@izuzak
:arrow_up<EMAIL_ADDRESS>izuzak committed 5 days ago
d5786a6
@izuzak
:arrow_up<EMAIL_ADDRESS>izuzak committed 5 days ago
2dfc066
@izuzak
:arrow_up<EMAIL_ADDRESS>izuzak committed 5 days ago
951c8e8
@izuzak
:arrow_up<EMAIL_ADDRESS>izuzak committed 5 days ago
9ca97d3
@izuzak
:arrow_up<EMAIL_ADDRESS>izuzak committed 5 days ago
fad937b
@izuzak
:arrow_up<EMAIL_ADDRESS>izuzak committed 5 days ago
1e1c88a
@izuzak
:arrow_up<EMAIL_ADDRESS>izuzak committed 5 days ago
efe815d
@izuzak
:arrow_up<EMAIL_ADDRESS>izuzak committed 5 days ago
b0d38bd
@izuzak
:arrow_up<EMAIL_ADDRESS>izuzak committed 5 days ago
9423af4
@izuzak
:arrow_up<EMAIL_ADDRESS>izuzak committed 5 days ago
39fc1ee
@izuzak
:arrow_up<EMAIL_ADDRESS>izuzak committed 5 days ago
8fe8aec
@izuzak
:arrow_up<EMAIL_ADDRESS>

@martinoppitz Those packages are bundled with Atom. When a bundled package is updated, then you might consider that an update of Atom itself because those packages are a part of the core Atom experience. When we make an update to a bundled package, we need to tell Atom core to use those new versions of packages (otherwise, it will still use to old versions). That's done by updating the dependency version in package.json. Does that answer your questions? If not, can you explain what )exactly_ you expected to see instead and why?


When entering a Sprint, kanban must be auto loaded.

Expected behavior
When entering a Sprint, kanban must be automatically loaded.
Current behavior
No tab is opened unless you click it.

Steps to reproduce

Create a Sprint.
Enter the Sprint.

Checklist

[x] Issue has Labels.
[x] Issue hasscreenshots.
[x] Issue has significant name.

Issue solved #370.


Webhooks doesn't send 'resolved' requests

Hi!
I'm testing alertmanager webhooks. "firing" requests are sent just fine,  but resolved requests are never sent, no matter how long I wait for it.
I tried to set "send_resolved" to true, but it doesn't help (obviously, as true is a default value anyway)

send_resolved: true was not default, at least for me.  which version are you running? and please share your part of a config.

version 0.3.0
config for webhooks looks like:
route:
  receiver: myweb

receivers:
  - name: myweb
    webhook_configs:
    - url: 'http://host:port'
      send_resolved: true # tried both setting this option and removing it

according to their docs it's good. I'm using email_configs, slack_configs, and send_resolved are working as expected.

I just tried version 0.4.2 - still no change. It keeps sending "firing" requests even though the issue is resolved already (and 5 mins have passed after it was resolved).

at some point it stops sending any requests. Could it be that instead of 'resolved' request it sends 'firing', by mistake?

Can you provide more exact steps to reproduce the issue? Ideally with version 0.5.0.
It's hard to make a guess with such little detail.

If you have additional detail, please reopen.

can you post your sanitized config?

Some information have been scrambled for security
global:
  # The smarthost and SMTP sender used for mail notifications.
  #smtp_smarthost: 'localhost:25'
  #smtp_from<EMAIL_ADDRESS>  #smtp_auth_username: 'alertmanager'
  #smtp_auth_password: 'password'
  # The auth token for Hipchat.
  #hipchat_auth_token: '1234556789'
  # Alternative host for Hipchat.
  #hipchat_api_url: 'https://hipchat.foobar.org/'

# The directory from which notification templates are read.
templates:
- '/usr/share/alertmanager/current/template/*.tmpl'

# The root route on which each incoming alert enters.
route:
  # The labels by which incoming alerts are grouped together. For example,
  # multiple alerts coming in for cluster=A and alertname=LatencyHigh would
  # be batched into a single group.
  group_by: ['alertname']

  # When a new group of alerts is created by an incoming alert, wait at
  # least 'group_wait' to send the initial notification.
  # This way ensures that you get multiple alerts for the same group that start
  # firing shortly after another are batched together on the first
  # notification.
  # Premier temps d'attente pour grouper avant premier envoi, réduit au minimum
  group_wait: 1s

  # When the first notification was sent, wait 'group_interval' to send a batch
  # of new alerts that started firing for that group.
  # Aprés premier envoi, on attend au minimum ce temps pour renvoyer une alerte sur ce groupe
  group_interval: 1m

  # If an alert has successfully been sent, wait 'repeat_interval' to
  # resend them.
  repeat_interval: 1m

  # A default receiver
  receiver: default_receiver

  routes:
  # Test receiver
  - receiver: test_receiver
    continue: true

  - receiver: site1_prd
    match:
      site: site1
      env: prd
  - receiver: site1_cae
    match:
      site: site1

  - receiver: site2_prd
    match:
      site: site2
      env: prd
  - receiver: site2_cae
    match:
      site: tls

receivers:
# Void receiver
- name: 'default_receiver'

# Test receiver
- name: 'test_receiver'
  webhook_configs:
    - url: http://xxxxxxxx:8080/prometheus
      http_config:
        basic_auth:
          username: 'xxxxxxxx'
          password: 'xxxxxxxx'
  slack_configs:
    - send_resolved: true
      api_url: https://hooks.slack.com/services/xxxxxxxx
      channel: xxxxxxxx

I have found the beginning of the issue:
The implemented webhook llistener didn't answer 'ok' or with a status 200, therefore the alertmanager generated a "deadline exceeded" error.
Once corrected, I now get resolved alert in webhook.
From that point, I don't know if that's the desired behavior from alertmanager or if it's a bug.

A webhook is expected to respond with a 2xx for successful sends, and a 5xx for retryable requests.
If your webhook never responds or finishes the request, the request should timeout from AM's perspective.


Idea: Allow custom mapping of colours to status

it would be great to be able to choose the colors that you want displayed for each status vs. the pre-defined colours.
Effectively taking some of the work from #56 and making similar options with colour pickers available in settings would allow for custom colouring.

Also adding the ability to select to no colour/off for some statuses. I'd like to only have the light on only if I'm unavailable. Wasting precious electricity telling people to come talk to me.

@isaacrlevin I've created a pull request for my work on customising colours for Philips Hue.
Apologies I've never used github before and haven't written any Microsoft for 20 years. Let me know if anything needs work


File accelerator should be successfully created when datasets are dynamically updated / included

Closed by: https://github.com/spiceai/spiceai/pull/3836


chore(deps): update terraform terraform-ibm-modules/icd-postgresql/ibm to v3.6.2

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/icd-postgresql/ibm (source)
module
patch
3.6.1 -> 3.6.2

Release Notes

terraform-ibm-modules/terraform-ibm-icd-postgresql (terraform-ibm-modules/icd-postgresql/ibm)
v3.6.2
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/cbr/ibm to v1.10.0 (#282) (fef2ceb)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

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


Adding in better error handling

👍 Just need to lower the coverage so we can merge. Then we can reenable tests and increase the coverage back up.


"Step references task '1ESLighthouseEng....' which does not exist." Error

Hi! I read your blog post (linked in the VS Code release notes) and thought it sounded like a thing I should try!
But I get this error:
Job Linux: Step references task '1ESLighthouseEng.PipelineArtifactCaching.RestoreAndSaveCacheV1.RestoreAndSaveCache' at version '1' which does not exist.

which makes me think I'm missing some basic beginner step like "installing" the task or something.
Azure build page: https://dev.azure.com/isomorphic-git/isomorphic-git/_build/results?buildId=847&view=results
Got any suggestions?

I'm happy to hear you're trying out the build task (although sorry to hear the onboarding hasn't been a breeze). Have you installed tasks through the marketplace?

Another step you'll need to take is to have a build variable (ArtifactFeed) that points to the guid of an Azure Artifacts feed in your Azure DevOps instance.

It would be really helpful to point out in the docs that azure artifacts needs to be enabled - not knowing about it made it quite hard to find out how it works

Have you installed tasks through the marketplace?

Aha! That's exactly the kind of step I thought I might be missing. Awesome 😊

Another step you'll need to take is to have a build variable (ArtifactFeed) that points to the guid of an Azure Artifacts feed in your Azure DevOps instance.

OK, so I've created an Artifact Feed but now I'm at a loss how to find it's GUID.

You are all absolutely correct that we can provide better info for onboarding. I've updated the readme to include some more information for onboarding. Let me know if this helps clear things up..

Note: The GUID for your Azure Artifact feed can be found either by using the Azure DevOps rest apis or by creating a build task in the traditional visual designer that references the feed and then selecting "View YAML".

Awesome! Yeah, the onboarding could be polished. I'd love it to simply be baked into the regular "get started with Node" tutorials
Happy to say it was a big win! Cut my npm ci time in half from over a minute to 34s!
https://github.com/isomorphic-git/isomorphic-git/pull/723


add httpString()

Request.toString() method shows headers first and body second.
I wanna see the Request as HTTP protocol like this:

GET https://www.example.com/path
Content-Type: text/plain
Accept-Encoding : compress;q=0.5, gzip;q=1.0
Request body string

I like this addition. 👍from me.

Sorry I missed.

Request.toString() method shows headers first and body second.

Request.toString() method shows body first and headers second.

I dont see anything against this. Let's merge it.


add lsn check before append entry

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 77.77778% with 2 lines in your changes missing coverage. Please review.

Project coverage is 68.08%. Comparing base (1a0cef8) to head (e869041).
Report is 55 commits behind head on master.

Files with missing lines
Patch %
Lines

src/lib/replication/repl_dev/raft_repl_dev.cpp
75.00%
0 Missing and 1 partial :warning:

...rc/lib/replication/repl_dev/raft_state_machine.cpp
50.00%
0 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           master     #535       +/-   ##
===========================================
+ Coverage   56.51%   68.08%   +11.56%
===========================================
  Files         108      109        +1
  Lines       10300    10433      +133
  Branches     1402     1399        -3
===========================================
+ Hits         5821     7103     +1282
+ Misses       3894     2655     -1239
- Partials      585      675       +90

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Revert raise of PointerRelease in TouchesCancelled

… as it introduce multiple other issues and it was only a temp work around
cf. discussion https://github.com/nventive/Uno/pull/865

Only the functional changes should be reverted, the sample should stay.


Add support for argument groups and mutually exclusive groups.

https://github.com/FNNDSC/chris_plugin/blob/edf9a6b1a727af46956f199d1ba90edeb68b568a/chris_plugin/tests/test_parameters.py#L154-L159

https://docs.python.org/3/library/argparse.html#argument-groups
https://docs.python.org/3/library/argparse.html#argparse.ArgumentParser.add_mutually_exclusive_group

hey @jennydaman I'm an outreachy applicant and would like to work on this issue, can you help to get started with this one,
it would be a great help for me

hi @tr-sangale welcome. This issue is open to work on, though it's not a priority and involves some deeper understanding of Python and ChRIS. If I may suggest, https://github.com/FNNDSC/chris_plugin/issues/5 could be a better task.
Anyways, I can still provide some information on this issue. The decorator created by the function chris_plugin.chris_plugin is able to serialize a argparse.ArgumentParser object as JSON in accordance to the ChRIS plugin specification. However, chris_plugin.chris_plugin does not support argument groups nor mutually exclusive argument groups. The objective here is to add support for argument groups.


wkb geozero perf: avoid copy

https://github.com/georust/geozero/pull/171 was merged, so after the next geozero release, we should merge this

Oop https://github.com/georust/geozero/pull/171 still hasn't been released yet

closed by https://github.com/geoarrow/geoarrow-rs/pull/413


Build go in docker, Upgrade CSI Driver and Go version

Issue #, if available: Closes #55
Description of changes: CSI Driver is on Go v1.18, updating dependencies to match.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #85 (9b35281) into main (f043e56) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 9b35281 differs from pull request most recent head 27edac5. Consider uploading reports for the commit 27edac5 to get more accurate results

@@           Coverage Diff           @@
##             main      #85   +/-   ##
=======================================
  Coverage   56.09%   56.09%
=======================================
  Files           7        7
  Lines         574      574
=======================================
  Hits          322      322
  Misses        244      244
  Partials        8        8

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f043e56...27edac5. Read the comment docs.

Experiencing bugs when @danmancuso tried to deploy to an ARM64 cluster. Investigating.


[OSD-22930] Migrate CAD to AWS SDK v2

This PR migrates the codebase to the new AWS SDK version in preparation for easier creation of mocks.
Reference:

https://aws.github.io/aws-sdk-go-v2/docs/migrating/

To better test the code we likely need to refactor a bit more to adhere to the recommendations.

Codecov Report
Attention: Patch coverage is 3.68098% with 157 lines in your changes missing coverage. Please review.

Project coverage is 38.21%. Comparing base (d708d37) to head (1c44ae7).

Files with missing lines
Patch %
Lines

pkg/aws/aws.go
0.00%
151 Missing :warning:

pkg/aws/mock/aws.go
50.00%
6 Missing :warning:

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #307      +/-   ##
==========================================
+ Coverage   37.82%   38.21%   +0.38%
==========================================
  Files          22       22
  Lines        1668     1651      -17
==========================================
  Hits          631      631
+ Misses        997      980      -17
  Partials       40       40

Files with missing lines
Coverage Δ

pkg/investigations/chgm/chgm.go
63.00% <ø> (ø)

pkg/aws/mock/aws.go
59.30% <50.00%> (ø)

pkg/aws/aws.go
0.00% <0.00%> (ø)

/label tide/merge-method-squash

/unlabel tide/merge-method-squash

/remove-label tide/merge-method-squash

/retest

/retest

/retest


Is it possible to run this with web assembly

If not what will be requird for running it with wasm?

Please use https://github.com/pypyjs/pypyjs/issues/145 ;)


Web UI should provide information on client certificates created for workload clusters

User story

As an admin, I want to see which client certificates have been created for workload cluster access, and could still be in use, so that I can adapt RBAC permissions if necessary.

Background
Currently the web UI does not provide information on client certificates for workload cluster access created via the Management API (MAPI). Rest API users were used to getting that information.
The method to create certificates via the MAPI is deprecated (based on Giant Swarm's cert-operator and the CertConfig custom resource). We don't want to invest any effort into additional visibility for certificates created based on this method. Instead, we are looking for a solution that works for the Cluster API generation.
Access to the information should not only be available to the web UI, but also via kubectl.
TODO:

[ ] Look into CSRs with cert-manager for client certificate creation

Duplicate of giantswarm/giantswarm#19161 ?

Yes

These are the options ideas:

List in Happa so as to show all Workload Cluster client certificates and keep track of the key pairs that have been created and could be in use currently
Having metadata and exposing it to the Management API to that we can add it to Grafana and we can add needed alerting when/if needed

Both solutions need some more "Refinement time" to estimate the additional tasks needed.
Thoughts on UI/ Usability:

We already have tab for listing the key pairs in Happa, we can just the rest there, if the effort is low compared to the 2nd option.
Is the 2nd options be better suited for non-happa users ?

We just had a customer ask about this

I'm adding it to discuss further on this Friday (11Feb) Refinement.

Team rainbow thinks this is currently blocked and we need talking with Phoenix and Rocket to find out details about client certs in CAPI. We'll invite to a call.

Internal Slack thread: https://gigantic.slack.com/archives/CNX3Z835G/p1653041370862069

We think that clientcerts should not be signed on the client side and we should reintroduce a way to keep track of the active certificates. Next step is a spike on how we want to do it.
We should ask cabbage what they think about using CSRs.

Blocked by https://github.com/giantswarm/giantswarm/issues/15981 as we cannot display any details as long as we don't know whether/how we would actually create client certificates.

not possible. closing


Error convert miniCPM-V hf to vllm

Hi I triied to convert vllm
 python inference/convert_hf_to_vllmcpm.py --load ./cache/MiniCPM-V/ --save ./cache/MiniCPM-V-vllm

But got the following error:
FileNotFoundError: [Errno 2] No such file or directory: '.cache/MiniCPM-V/pytorch_model.bin'
Thanks

Please confirm that you have downloaded the hf model to ./cache/MiniCPM-V/


Single framework target for all platforms

As described in
http://ilya.puchka.me/xcode-cross-platform-frameworks/

Done in https://github.com/malcommac/SwiftDate/commit/4bcd67ad4d3e0229ac717e1dddd2b5eae6ad3067


Enable and Configure Zone Aware Routing via xDS APIs rather than as a flag

Title:
Configure Zone Aware Routing via xDS APIs rather than as a flag
Description:
Currently to enable zone aware routing Envoy requires using the --service-zone flag. We (Istio) would like to be able to enable and configure zone aware routing via the xDS APIs. I believe this is achievable if the envoy instance looked itself up using the CDS API, retrieving a cluster array with just itself in.

Somewhat related to https://github.com/envoyproxy/envoy/issues/1344.

I'll take this on so that I can get more familiar with API changes

We might want to sync on this at some point soon. I'm going to be enabling locality (zonal) load balancing, which needs to have well defined behavior in the presence of zone-aware routing. The locality load balancing comes from existing EDS definitions.

@mattklein123 Talked with @liamawhite on this. The enhancement of allowing the zone to be supplied via the API call is so that we don't need to restart the container in Istio.
@liamawhite Anything else I'm missing?

Specifically, its the restarting of Envoy. We have a preference for removing as much restarting of Envoy as possible.

@cmluciano @liamawhite I'm sorry I don't understand why Envoy needs to be restarted. Why would the zone of a container ever change once it is started?

Its a timing issue with Kube. When we schedule a pod we don't know which node it's going to run on. We can only retrieve the az of the node once the pod is running, therefore have to restart.

I don't know much about k8s, but it seems odd to me that you can't adjust the params of Envoy when the pod starts running? Potentially via an env var?

So you're suggesting not starting envoy until we can work out the zone?

@liamawhite yes that is what I'm suggesting. Basically all locality information should be available before starting Envoy IMO.

@liamawhite Think we can close this issue for now?

@cmluciano yeah I'm going to close as won't fix since I really don't think this is the right design direction. Let's reopen or discuss on envoy-dev@ if we think otherwise.

Agreed


Add option to specify the font to use

The bundled font may not always be the right choice for a given barcode,
so I've added an option for the user to specify the font to use. Simply
pass the full path to the font file using the font_path option.

Makes perfect sense. Thanks, and apologies for the slowness!


site not working

Oh no.
Error running app. If this keeps happening

It is not running for the time being


Provide error code for simulation related errors

It'll be nice to have customized error code for each of simulation related errors
Currently, one would have to parse through the error message to get the returned variables. See handle_response function in ethers-userop.

It'll be nice to have customized error code for each of simulation related errors
Currently, one would have to parse through the error message to get the returned variables. See handle_response function in ethers-userop.

@da-bao-jian Can you please provide more information about which error codes exactly - the ones returned from JSON-RPC API?
We should follow the specs fully for error codes: https://eips.ethereum.org/EIPS/eip-4337#rpc-methods-eth-namespace . Or do you mean that single error code in the specs can mean different things?

Sorry I should've been more clear on that

Yes the ones returned from Json RPC API
and yes, a single error code can have different things. Primarily I was dealing with insufficient verification/call/pre-verification gas errors. They all have the same error code

Sorry I should've been more clear on that

Yes the ones returned from Json RPC API
and yes, a single error code can have different things. Primarily I was dealing with insufficient verification/call/pre-verification gas errors. They all have the same error code

Ok, got it. Thinking about what would be the best approach, I am not sure if introducing custom codes would be the best approach since it deviates from standard. But maybe structuring the error message in the meaningful way could be the way to go.

What do you recommend for implementation.
I can work on it when my schedule is a little bit better

What do you recommend for implementation.
I can work on it when my schedule is a little bit better

We could do something similar to errors from the entry points: the message should always start with AA(INT) - https://github.com/eth-infinitism/account-abstraction/blob/develop/contracts/core/EntryPoint.sol#L60.
Maybe something like B1 for call gas limit, B2 for preverificationgas ...


Changed label on variant

Changed variant widget in configurator to check for variant name in the following order:

Parent schema's property name
"title" property

Defaults to "Choose variant"
Closes #455

@SindriTh I would let property name be ordered above title

@SindriTh I would let property name be ordered above title

Widget now checks for Parent schema's property name, then looks for title" property

Works, needs beautifying


Need help with downloading o7.

Ozone is deleted from mod browser, Is there any other way to download it?

https://github.com/o7-Fire/Mindustry-Ozone/wiki/Download

I tried it but I can't download any file from there. @Nexity

hmm

click this

https://github.com/o7-Fire/Mindustry-Ozone/actions/runs/696835892

I did.

what pops up?

it should be like this

I can just copy the name but not download the file.

are you on android?

it should be like this

Nothing pops up. I just can't download it.

Mindustry-Core (5).zip
try clicking this and it should work

Works, Thanks.

you're welcome

also we are working on a new mod, so we wont be updating ozone for a while

Good to know.


Key on EOS: No interest picker is shown on first launch

No interest picker is shown on first launch, a starter pack is downloaded automatically. After the download of the starter pack (here Explorer pack) is finished the complete screen is shown - but the show-me button does nothing.

One can use the home icon to get to the Discovery page or restart the app.

This will be resolved once we have completed the following related tasks:

[ ] https://github.com/endlessm/kolibri-explore-plugin/issues/748
[ ] https://github.com/endlessm/endless-key-flatpak/issues/40

Should by fixed by https://github.com/endlessm/kolibri-explore-plugin/pull/793


Notify user when no search results

Is your feature request related to a problem? Please describe.
User should be "toasted" when there are no search results
Describe the solution you'd like
Implement material ui Toast
Additional context
Determine other areas where toasts are needed to express transient states of being on the app.

All done


Add pull request template

Can I add pull request template to this project to enhance the workflow of the repository?

Can I add pull request template to this project to enhance the workflow of the repository?

We don't require this template here.


Ngrok auth token support

it makes ngrok look up an auth token environment variable, which can be used to extend the tunnel limits, even with a free account

Codecov Report

Merging #275 (87dbe2a) into master (2b82985) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #275   +/-   ##
=======================================
  Coverage   30.21%   30.21%
=======================================
  Files          31       31
  Lines        2317     2317
=======================================
  Hits          700      700
  Misses       1617     1617

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2b82985...87dbe2a. Read the comment docs.


Disaster Recovery in BAF

Describe the bug
As a part of DR testing, I was trying to recover the BAF deployments but could not recover BAF(fabric) from a kubernetes level failure.
To Reproduce
Steps to reproduce the behavior:

Install fabric network using BAF with one orderer and two organizations(1 peer)
After successful deployment of BAF, change the kubernetes configuration for all the organizations in the network.yaml to another working kubernetes cluster.
Run the deploy-network.yaml
deploy-network.yaml fails with the below error

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: If you are using a module and expect the file to exist on the remote, see the remote_src option
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Could not find or access './build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem'\nSearched in:\n\t/home/blockchain-automation-framework/platforms/hyperledger-fabric/configuration/roles/create/crypto/peer/files/./build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem\n\t/home/blockchain-automation-framework/platforms/hyperledger-fabric/configuration/roles/create/crypto/peer/./build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem\n\t/home/blockchain-automation-framework/platforms/hyperledger-fabric/configuration/roles/create/crypto/peer/tasks/files/./build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem\n\t/home/blockchain-automation-framework/platforms/hyperledger-fabric/configuration/roles/create/crypto/peer/tasks/./build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem\n\t/home/blockchain-automation-framework/platforms/shared/configuration/../../hyperledger-fabric/configuration/files/./build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem\n\t/home/blockchain-automation-framework/platforms/shared/configuration/../../hyperledger-fabric/configuration/./build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem on the Ansible Controller.\nIf you are using a module and expect the file to exist on the remote, see the remote_src option"}

PLAY RECAP *******************************************************************************************************************************************************************************************************************
localhost                  : ok=309  changed=99   unreachable=0    failed=1    skipped=435  rescued=0    ignored=0

Expected behavior
The deployment of the network should go through.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS: From docker container
Version [e.g. 22]
Cloud environment: AKS
K8S Version: 1.17.11

Additional context
I tried the above test on the same kubernetes cluster the network was deployed on by deleting namespace of an organization (ca, ca-tools, peer, pvc, services..etc are deleted). When I run the deploy-network.yaml after deleting the namespace, I get the beow error
Getting secrets from Vault Server: http://vault-test.eastus.azurecontainer.io:8200
{ "errors": [ "permission denied" ] }
ERROR: unable to retrieve vault login token: {
  "errors": [
    "permission denied"
  ]
}

I did some testing with DR scenarios trying to leverage the BAF's design philosophy of considering K8S cluster as ephemeral. During my earlier testing I noticed that any of the deployed components when it get deleted is automatically deployed by the flux. So, I deleted a namespace org2-net in my network and flux automatically triggered the deployment of all the components in the deleted namesapce, and it got the above mentioned "permission denied" error. I deleted the vault-auth token and re-run the deploy-network.yaml and the error got cleared and CA and peer deployments were successfully completed. Few questions on CA needing the vault-auth

If a CA server restarts for some reason, would it fail to read the vault-auth token just like above?
Is CA server is the only one that needs vault-auth token?

For the actual testing itself, once I cleared the vault-auth token and re-run deploy-network.yaml, CA server and peer got successfully deployed. But the deployment failed with the below error
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: If you are using a module and expect the file to exist on the remote, see the remote_src option
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Could not find or access './build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem'\nSearched in:\n\t/home/blockchain-automation-framework/platforms/hyperledger-fabric/configuration/roles/create/crypto/peer/files/./build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem\n\t/home/blockchain-automation-framework/platforms/hyperledger-fabric/configuration/roles/create/crypto/peer/./build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem\n\t/home/blockchain-automation-framework/platforms/hyperledger-fabric/configuration/roles/create/crypto/peer/tasks/files/./build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem\n\t/home/blockchain-automation-framework/platforms/hyperledger-fabric/configuration/roles/create/crypto/peer/tasks/./build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem\n\t/home/blockchain-automation-framework/platforms/shared/configuration/../../hyperledger-fabric/configuration/files/./build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem\n\t/home/blockchain-automation-framework/platforms/shared/configuration/../../hyperledger-fabric/configuration/./build/crypto-config/peerOrganizations/org1-net/peers/peer0.org1-net/msp/cacerts/ca-org1-net-7054.pem on the Ansible Controller.\nIf you are using a module and expect the file to exist on the remote, see the remote_src option"}

PLAY RECAP *******************************************************************************************************************************************************************************************************************
localhost                  : ok=309  changed=99   unreachable=0    failed=1    skipped=435  rescued=0    ignored=0

How can I overcome this error?
This peer is already part of the channel, what will happen when the joinchannel or anchorupdatepeer jobs gets triggered again?
Again, am I in the right path to test a DR scenario?

I think the DR scenario is wrong.
Because if you change the cluster itself, the volumes will be gone, and then setting up a network is like a new network itself.
If we want to take into consideration the volumes as well, then we need to modify the BAF architecture itself to have their backups as well. Just by saving the certificates, wont recover the network.
@sownak your views on this?

Thanks for your views @jagpreetsinghsasan . But let me just add my experience in recovering a Fabric 1.4.2 network. I had a cluster down scenario when the orderers disk became full. I took a backup of orderer data following this document - https://docs.google.com/document/d/1dEhUpMcqOYfOngDvSlyXL6NIBuTKmhP5s0fr_--U_OA/edit# and I was able to recover the entire cluster although there were multiple problems due to different block heights - the discussion about the same is here - https://chat.hyperledger.org/channel/fabric-questions?msg=QScfyHbu98q9oJsxd.
Assume that I have the orderers data's backup and I think we can do the DR in two steps

Re-run the deploy-network.yaml with the same configuration
Restore the orderer data from a data backup I have so, orderers and peers can sync from the restored data.

Another option is to do a velero backup and restore, which I think would work, but have to test it.

Yes, the orderer backup should work. That's what I was referring to when I said about volume backups. If that is done, then we should be able to achieve DR in BAF as well.
As you have mentioned that it is failing in this case, this looks like a valid bug.
Apart from resolving this bug, we should also have a check for CA's, as we wont need them when we do the redeployment (currently we wont have new certificates in vault, but the CA and its CLI will still come up)

Hi @sivaramsk, just to let you know: I'll be taking up this bug.
As per the discussion above, I'll be tackling it as follows:

Deploy the network on a cluster
Upon deployment completion, scale down the cluster to 0 nodes
After some time, scale it back up and see if the cluster recreates the network properly.

Within the team, we suspect that the bug is caused due to some disks/folders not being mounted to volumes and thus being lost upon downscale of the cluster.
I'll keep you up to date as we go, and please feel free to add any thoughts/experiences you have on this ticket!

Awesome. On a related note, I was also testing BAF with velero backup and restore. I hit a bug with velero restore which got fixed recently - https://github.com/vmware-tanzu/velero/issues/3027. I would test velero approach as well, and will document it.

So far, with the current scope of the story: I have found the following things.

The CouchDB of the Peer is not mounted to a volume, and thus is lost upon downscale of the cluster. I have bound it to a PVC, which in turn is bound to the storageclass.
I have found issues with our Vault in the containers. It does not check if the Vault is reachable or sealed, but still continues starting up. It will try to fetch certificates/secrets from the Vault, can't reach the Vault but continues the deployment leading to missing/empty files. This may cause issues when you upscale the cluster again and the Vault is part of the same cluster. I have created a bug for this (#1179) and this will be picked up in a future sprint.

Together with the backups that you have been researching, we should have a complete DR scenario.
I'll create a PR for this soon. If you have any additional thoughts @sivaramsk, please let us know!

@abevers - quick question on your steps to reproduce. Can you explain what you mean by down-scaling the cluster? Scaling down the deployments to 0? If you take a real world scenario, say you lose access to a whole cluster where one of the org is deployed,

Create a new K8S cluster.
Adjust the network.yaml to point to the new K8S cluster.
Re-run the deploy-network.yaml

Can you clarify whether your steps do the same or different? As for the vault issue you noticed, I think that is true even for a simple restart of CA pod, correct?
I still have not had the time to test the velero backup and restore yet, will update once I had that done.

Hi @sivaramsk, my scenario is not exactly the same. The scenario I have researched is a complete shutdown of the cluster (scaling deployments to 0) and then the same cluster restarting. I think your suggestion of pointing to a new cluster for 1 or more organizations is also very valid. I'll discuss this with the team.


bug: editing a tier label, and saving it, doesn't stick (write a test first?)

confirmed, fix now in foxtrot


TESTS: workaround aggressive optimization

Workaround aggressive optimization of following tests by MWDT toolchain. Although we've faced with this issues with ARC MWDT toolchain such optimization are possible by any other toolchain.
Affected tests:
kernel.common.stack_protection
kernel.common.stack_sentinel
kernel.scheduler.preempt
kernel.memory_protection.protection
libraries.libc.minimal.mem_alloc

kernel.common.stack_protection
The 'stack_smasher' call can be optimized away as its results isn't used anywhere and stack_smasher function has no visible side effects.
kernel.common.stack_sentinel
The memset in the 'blow_up_stack' function can be optimized away as it is called in the end of the function on the buffer
allocated on the stack (so it has 'no' effect on program execution):
void blow_up_stack(void)
{
	char buf[OVERFLOW_STACKSIZE];

	expected_reason = K_ERR_STACK_CHK_FAIL;
	TC_PRINT("posting %zu bytes of junk to stack...\n", sizeof(buf));
	(void)memset(buf, 0xbb, sizeof(buf));
}

kernel.scheduler.preempt
We use several variables (like do_sleep, etc...) to share statuses between threads, however they are not marked as volatile. That may lead to their unexpected optimization (which really happens with ARC MWDT when loop with waiting on the sleep timeout in 'wakeup_src_thread' is optimized away).
kernel.memory_protection.protection
Compiler may optimize away write to address with following readback so we won't trigger fault (that actually happens with arc MWDT toolchain).
libraries.libc.minimal.mem_alloc
As we don't use memory allocated in test_memalloc_max the malloc call can be optimized away.
void test_memalloc_max(void)
{
	char *ptr = NULL;

	ptr = malloc(0x7fffffff);
	zassert_is_null(ptr, "malloc passed unexpectedly");
	free(ptr);
	ptr = NULL;
}

ARC MWDT toolchain optimize it to zassert_ trigger with "malloc passed unexpectedly" message. That breaks the test.

So MetaWare is more clever than the tests :-)
All good changes, just a suggestion to improve the abstraction of the _no_optimization attribute and make it more robust for more toolchains.


Share button (Not working properly)

Share button does work only after clicking on Settings button

@Alja7dali Sorry I pushed a wrong commit. It will fix the next deployment running now.

It is now fixed. Thank you for reporting!


Add support for rails 7

Seems to be working fine with just enabling it. Although I only tested in an app with very little usage of public_activity.

just noticed there is another one already. closing this in favour of https://github.com/chaps-io/public_activity/pull/358


UPDATING SupabaseVector to allow RPC with Filter

Hi, I've looked into the SupabaseVector,
With the help of Greg Richardson @ supabase noticed that it uses the rpc function.
https://github.com/hwchase17/langchainjs/blob/4e7ea758121a5f2844f1d53d73d3ed65e0491c2f/langchain/src/vectorstores/supabase.ts#L78
I've looked to changing it so that it will allow .filter() so that a user can pass into a filter object so that the documents matched, are also filtered based on metadata or whatever really that the user wants to filter within the supabase
However when I was looking into changing it, I've realised that the general Langchain structure is to (i guess) assume that a table (whether its supabase) or a collection (chroma) etc will collect ALL OF THE EMBEDDINGS so changing the logic to allow for filtering (I believe) will go against the structure of all the chains etc.
Is this something that Langchain would potentially consider adopting the ability to filter when making a LLM call etc?
I'm going to give it a go tomorrow but I don't know if it'll be worth while etc!

~~ Searching through issues had lead me to here
https://github.com/hwchase17/langchainjs/pull/905


introducing gstat, a new command to get the git status

the purpose of this command is to get the git status of a local repo in order to parse that status and use in a prompt string. the wt in the data stands for working tree. the idx in the data stands for index. the rest should be self-explanatory. since we don't really want this to fail when run outside of a git tracked folder, we just return -1 on the numeric fields so these could be checked from a script.
from inside a git tracked folder

from outside a git tracked folder

pass folder in on the command line

pipe folder/string in on the command line

TODO:

[ ] fix any bugs found
[ ] i was unable to pipe in bare words, i'm not sure why - maybe it's supposed to be that way

I would add a category to the signature

Good point. It should be required.


Removes the expression cache lookup from the type-checker.

The previous checking accidentally re-introduced the cache lookup
during type-check. The type-check needs to be cache-independent, and
should use the supplied attribute descriptor finder & expression, as
that set of expressions are potentially independent of the cached ones.
What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
This fixes the postsubmit test run issue.
Release note:

NONE

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
e8061d36fe2f6e09d893eeea81d5698fba81ac4e
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/lgtm


add solution for these problems in C++

Add solution for these problems and add their solution links under solution section in readme file
22	Comparison
23	Mathematical Expression
24	Two intervals
25	The last 2 digits

Hey , can you please assign this to me ? I would love to work on this

@ankitkumar0622 please always create your own branch
and before start working in your branch update your branch from master.

ok

Please assign this to me

hey @Shubhamlmp , I have added the solutions of qno. 22 and 23 with better formatting and comments and also created a PR.


perf: Make is_type faster and cleaner

Instead of flattening to find out is_number, we can just check issubclass(int, pytypes) which doesn't require flattening the types list. Only if that passes do we need to look further.

This is similar to #232 which looks to be stuck in review for quite a while. I don't really have the time to rigorously benchmark it, but it is around 10% faster on the workloads I'm using it for. Perhaps it can be accepted as prima facie better than the current master?

@alex-hofsteede I think that thanks to a recent contributor #232 is actually benchmarkable regardless -- will have a look both at this patch and the one there.


Wishlist Database

As a developer
I need to store the content of wishlists
So that I can provide the required data when needed
Assumptions:

...

Acceptance Criteria:
Given ...
When ...
Then ...

I think for database, one thing is the database schema another is how to set up connection in Python.


remove simple Preface from OGC: https://github.com/metanorma/metanorm…

…a-ogc/issues/291
Metanorma PR checklist

[ ] Breaking changes (list related PRs)
[ ] Documentation update required (create task for this)
[ ] External dependency introduced (documentation update need)
[ ] Gem with native library introduced

Thanks @opoudjis !


Add QuickSort Algorithm

Aim
To Add the QuickSort Algorithm in Python
Hello!
I am a proud contributor at GSSoC '23. I would like to the contribute to this project.
@avinashkranjan if you think it is useful then do assign me the issue under GSSoC '23 with the level of the PR as well.

Too Basic, Read the Description of the Project, We don't need algorithms we need scripts.


This is the Demand Response Load Control SDK - initial submission.  I…

…t is an SDK for the development DRLC cluster instances.  A representative delegate instance is found in DRLC.cpp.   Much of this framework was extracted from existing Zigbeen and other work.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Steve Holmgren seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Pulling and reworking pull request with more complete information on the SDK content and format


[PowerToys Run] - Add a Setting for VSCode Plugin to Remoe Extra information from List

Description of the new feature / enhancement
I use Development Container a lot while working on my projects using Docker Containers and noticed that these random Sequences appears after the name of the Directory/File

My proposal is to add a setting specifically for the VS Code plugin that is a check box which would either include (Checked) or exclude (Unchecked) the extra sequence.
Note sure about whether we want to have a default of checked/unchecked, but that can be decided after a discussion.
Scenario when this would be used?
Not really a specific scenario that this is either useful or not useful it just feels like unnecessary information being displayed out sense most of the time the user should know which directory they are accessing via the "Project Folder in "XXXX") section under the name
This would also setup the foundation for future settings that might be useful, such as adding for example the ability to clear out results using a button on the user interface, that can be left for a different feature/task.
Supporting information
No response

@RadhiRasho
Is this a dev container only thing and is this information always useless on dev containers? Then I suggest to go without a setting and ignore this information for dev containers always. (Such a setting will be confusing and we should avoid settings like "show/hide useless information".)

@htcfreek
After looking into the SSH and WSL slide of things I've found that the Random Id Sequence only occurs on SSH and Dev Containers and not on WSL Distros as shown in the images below:
For WSL:

For SSH:

I also believe that the extra bit of information is being brought in from the storage.json side of things where I noticed the same sequence of random characters on the path stored by VS Code:

I think this should be the machine name. But in this encoded version it is not helpful. 🤔 Wonder if we can decode it.

I can look into that if you believe that's the case, that would be a better way of handling it

I can look into that if you believe that's the case, that would be a better way of handling it

As I can see for othe items that position of the title contains the machine name. I don't have such workspaces so I can't test it.

Yeah I tend to use Dev Containers quite often so I noticed it right a way.
I'll know for sure once I have the project running locally.


WorkspaceItem: Decode category fields

Overview
Decode the category (type/ability/doc/test/term) fields that were
recently added to the /getDefinition API.
Also clean up the decoders slight and use the same category decode
across the codebase.

Just curious, are those line numbers in the gutter clickable yet (and they update the URL)?
I think that'll eventually be handy for code review purposes

@pchiusano they are not :( We should definitely support that soon. Added a Github issue: https://github.com/unisonweb/codebase-ui/issues/54


Volcanic SO2 emissions read incorrectly in UFS-GOCART

Volcanic SO2 emissions are read incorrectly in UFS-GOCART. This might be related to inconsistent grid coordinate units when running MAPL with an external grid, and it is connected to MAPL closed issue #680 affecting point source emissions.
The picture below shows the SO2EMVN diagnostic variable as written by History:

Assigning to @bena-nasa

@bena-nasa can you take a look at this?

@WilliamJamieson was trying to teach me how to build and run the test. We had build issues, once those are sorted out a few prints should pinpoint the problem.

I have found the problem. I've made a PR in MAPL to fix this https://github.com/GEOS-ESM/MAPL/pull/736
There was another bug in the implementation. I tested this in the UFS code and it seems to be assigning correctly here is an example:
91: bmaa pet:   91    14     6     72.59999997    -53.02999853     72.28835244    -53.33303965
 91: bmaa pet:   91    14     5     73.50999973    -53.11000053     73.68131709    -53.41511761
 85: bmaa pet:   85    13    16   -135.99999468    -76.05000365<PHONE_NUMBER>7    -75.37749395
 85: bmaa pet:   85    11    22   -112.08000285    -76.27999661<PHONE_NUMBER>9    -75.88858113
 89: bmaa pet:   89     9     1    -99.41999450    -74.32999810<PHONE_NUMBER>1    -74.09423020
 89: bmaa pet:   89     4     4    -90.58000168    -68.85000072<PHONE_NUMBER>7    -68.90359173
 89: bmaa pet:   89     3    20    -57.92999673    -62.09999797<PHONE_NUMBER>1    -61.67727244
 89: bmaa pet:   89     3    18    -60.65000345    -62.97000015<PHONE_NUMBER>2    -62.79584878
 89: bmaa pet:   89     5    19    -55.77000063    -63.58000434<PHONE_NUMBER>9    -63.55781536
 95: bmaa pet:   95    18     1     51.75000059    -46.41999758     51.10834546    -46.43811190
 95: bmaa pet:   95    18     2     50.23000004    -46.09999980     50.05726243    -46.14204542
 95: bmaa pet:   95    12     9     37.94999952    -46.63000199     37.87571656    -46.97591323
 95: bmaa pet:   95    12     9     37.75000134    -46.90000278     37.87571656    -46.97591323
 94: bmaa pet:   94    10    12      3.34999989    -54.41999666      4.04189944    -54.49092890
 60: bmaa pet:   60    24    11   -156.25000293     20.70999929<PHONE_NUMBER>0     20.89429938
  5: bmaa pet:    5    20    17    -14.36999914     -7.94999954<PHONE_NUMBER>8     -7.74277128

The numbers are the processor, the assigned index i,j for that point, the values of the point that needs to be assigned to a grid cell if in the local domain, the value of the center lons/lats at that index. Looks good to me.

Additional changes might be needed to solve this issue. See comment in PR #736.

This is now fixed in develop of MAPL


PyFactoryCreateFile signature is not compatible

I am trying to create an import factory, and am following the tutorial for creating ColladaFactory, however the method the tutorial has shown does not appear to work.
Here is my code
from unreal_engine.classes import PyFactory, StaticMesh, Object, Class

import unreal_engine as ue
class SEModelFactory(PyFactory):

    def __init__(self):
        # inform the editor that this class is able to import assets
        self.bEditorImport = True
        # register the .dae extension as supported
        self.Formats = ['semodel;SEModel']
        # set the UClass this UFactory will generate
        self.SupportedClass = StaticMesh

    def PyFactoryCreateFile(self, uclass: Class, parent: Object, name: str, filename: str) -> Object:
        ue.log_warning('test')
        static_mesh = StaticMesh(name, parent)
        return static_mesh

and here is the output recieved:
LogPython: Warning: Parent PROP: Class<PHONE_NUMBER>/1074266654 128 8 0 ClassProperty 0000023A46DC7D80
LogPython: Warning: Parent UClassProperty = 0000023A46E43600 Class 0000023A46809D00 Object
LogPython: Warning: Parent PROP: InParent<PHONE_NUMBER>/1074266654 128 8 8 ObjectProperty 0000023A46DC7B00
LogPython: Warning: Parent PROP: InName 640/1074266654 128 16 16 StrProperty 0000023A46DC5800
LogPython: Warning: Parent PROP: Filename 640/1074266654 128 16 32 StrProperty 0000023A46DC5800
LogPython: Warning: Parent PROP: ReturnValue<PHONE_NUMBER>/1074266654 1408 8 48 ObjectProperty 0000023A46DC7B00
LogPython: Warning: Function PROP: uclass<PHONE_NUMBER>/1074266654 128 8 0 ObjectProperty 0000023A46DC7B00
LogPython: Warning: Function PROP: parent<PHONE_NUMBER>/1074266654 128 8 8 ObjectProperty 0000023A46DC7B00
LogPython: Warning: Function PROP: name 640/1074266654 128 16 16 StrProperty 0000023A46DC5800
LogPython: Warning: Function PROP: filename 640/1074266654 128 16 32 StrProperty 0000023A46DC5800
LogPython: Warning: Function PROP: ReturnValue<PHONE_NUMBER>/1074266654 1408 8 48 ObjectProperty 0000023A46DC7B00
LogPython: Error: unable to add function PyFactoryCreateFile
LogPython: Error: function PyFactoryCreateFile signature's is not compatible with the parent
LogPython: Error: Traceback (most recent call last):
LogPython: Error:   File "<string>", line 4, in <module>
LogPython: Error: Exception: function PyFactoryCreateFile signature's is not compatible with the parent

Also seeing this, for me in 4.22.
It looks to me like the problem may be the handling of UClass parameters. Note in the log the lines:
LogPython: Warning: Parent PROP: Class<PHONE_NUMBER>/1074266654 128 8 0 ClassProperty 0000023A46DC7D80
...
LogPython: Warning: Function PROP: uclass<PHONE_NUMBER>/1074266654 128 8 0 ObjectProperty 0000023A46DC7B00

Looks to me like the uclass: Class parameter is being mistaken for a UObject rather than UClass, hence the signature mismatch.

Has anyone solved this, I am seeing it with 4.22 and python 3.6


Add Signup/Register page

I want to create a Signup/Register page.. please assign me

@Akshat111111 sir please merge my PR's


fix: governance typing, plus decoded data

:tada: This PR is included in version 1.20.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.20.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: