TypeScript for a server programming language

If you are planning to implement some language to program server logic I suggest to use TypeScript or just JavaScript (someone who knows MTA:SA - I'm talking about Lua implementation they are using into this modification). Using node.js I think it's simple but that language is pretty dope for me and has a lot of nice features. Also TypeScript provides types which is also nice for people who aren't developers (because they will get nice syntax prompting with IntelliSense) and to people who are programming in that language.

Right now, there is no support for scripting mods. When it gets implemented, I plan to add C# as first language. Later on, developers can build wrappers around C# API, which will make it possible to use any language you like.


Global function for setting/verifying informal review

From Amy Hodge, Askbot FAQ:
I set up the option for informal review on all the individual templates— it would be great to have an easy way to verify this is true without opening up every single plan.

This is a great idea and would be something I would use. +1.


add proper whitespace between "edited" and html rendered message

Details

https://github.com/Expensify/App/issues/18241#issuecomment-1530955456
Fixed Issues

$ https://github.com/Expensify/App/issues/18241
PROPOSAL: https://github.com/Expensify/App/issues/18241#issuecomment-1530955456
Tests

Go to Expensify
Open any chat > Send a message like "Hi"
Edit the message and add one or two ` characters at the end (Eg. "Hi `` ")
Click on "Save changes" Icon
Verify that "edited" is not flickering

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

Offline tests

QA Steps

Go to Expensify
Open any chat > Send a message like "Hi"
Edit the message and add one or two ` characters at the end (Eg. "Hi `` ")
Click on "Save changes" Icon
Verify that "edited" is not flickering

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

PR Author Checklist

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Screenshots/Videos

Web

https://user-images.githubusercontent.com/71884990/236538148-a3616828-f5de-4819-b0aa-b15edd1be0cb.mov

Mobile Web - Chrome

https://user-images.githubusercontent.com/71884990/236538182-b4c6ddc0-b24e-420f-8ac0-f01be49471f4.mov

Mobile Web - Safari

https://user-images.githubusercontent.com/71884990/236538208-b327451a-d2cc-4c03-9508-d0b1cbac6a35.mov

Desktop

https://user-images.githubusercontent.com/71884990/236538297-978c4758-05f1-434b-aa6c-2bf8177e4e3c.mov

iOS

https://user-images.githubusercontent.com/71884990/236538309-f520fda6-d4a4-46d6-b5e9-503e230731bb.mov

Android

https://user-images.githubusercontent.com/71884990/236538342-85a2c0cd-f5b4-406f-81f8-aebcad779919.mov

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

🚀 Deployed to staging by https://github.com/iwiznia in version: 1.3.12-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/roryabraham in version: 1.3.12-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/iwiznia in version: 1.3.12-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Display a message when 6bin server couldn't connect

We should display something to warn the user that 6bin is usable when 6bin server / 6brain has a problem.
It should be a display mode where the user can't do anything with the interface

Closed by #28


Document DbStats::fragmented_bytes

What does DbStats::fragmented_bytes measure? I couldn't figure it out. For example, I expected it to be low for a freshly created database, but on a database with no insertions, fragmented_bytes was 16346.

It measures the number of unused bytes in allocated pages. It includes internal metadata pages, like the btree of table names, so I'd expect it to be 4k - epsilon for an empty db. Did you create any tables before checking the fragmented bytes?

There are two tables, one which will have an entry per block, and one which will have an entry per output, and they're both empty. This is what the stats look like for a new 1MiB database:
blocks indexed: 0
outputs indexed: 0
tree height: 1
free pages: 61
stored: 0 bytes
overhead: 38 bytes
fragmented: 15.96 KiB

I think my disk has 4KiB blocks:
$ diskutil info /Volumes/Root | grep 'Block Size'
   Device Block Size:         4096 Bytes
   Allocation Block Size:     4096 Bytes

But fragmented is suspiciously close to 16KiB, and 1MiB / 64 (which is close enough to 61) == 16KiB. Is it possible that for some reason redb is using 16KiB pages?

I just checked, and sysconf(_SC_PAGESIZE) does indeed return 16384, so the fragmented value make sense.
Is there a disadvantage to setting the page size to be smaller? It seems like it would reduce fragmentation.

Ya, it will reduce fragmentation. It might not be that much though, once you start writing data into the tables. The downside is that it could hurt performance, but I haven't experimented with it

I think maybe my mental model might be wrong.
When redb allocates space for an b-tree node, can it put multiple nodes inside of a single page, or does it have to allocate a page per node? And same question for keys and values, can it store multiple keys and values inside of a single page, or does it need to allocate a page for each?

So there are two different types of pages that come into play:

OS pages: the page size your OS uses
redb pages: these are dynamically sized in powers of two. The minimum size is configured when you create the database, and defaults to the OS page size

b-tree nodes map 1:1 to pages, and redb uses some heuristics to try and fit them into the smallest page size. For example, it will split any leaf pages with > 1 entry that exceeds the configured minimum page size.
A node can store many keys & values, up to BTREE_ORDER which is a constant in btree_base.rs and currently defined to be 40. I may remove that constant at some point, and just store as many as can fit in a page.

Okay, that makes sense. It’s too bad that the word page is overloaded to
mean both OS page and b-tree page, but those are the standard terms, so it
can’t really be helped.
So if key/value pairs are small, relative to the minimum page size, then
all pages will be the minimum size, and it’s only when keys and values are
larger will redb make larger allocations.
On Sat, Feb 19 2022 at 4:48 PM, Christopher Berner @.***>
wrote:

So there are two different types of pages that come into play:

OS pages: the page size your OS uses
redb pages: these are dynamically sized in powers of two. The
minimum size is configured when you create the database, and defaults to
the OS page size

b-tree nodes map 1:1 to pages, and redb uses some heuristics to try and
fit them into the smallest page size. For example, it will split any leaf
pages with > 1 entry that exceeds the configured minimum page size.
A node can store many keys & values, up to BTREE_ORDER which is a
constant in btree_base.rs and currently defined to be 40. I may remove
that constant at some point, and just store as many as can fit in a page.
—
Reply to this email directly, view it on GitHub
https://github.com/cberner/redb/issues/176#issuecomment-1046133745, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAPGIQRXYZHSB4SGDY6JLU4A26PANCNFSM5OXMHDJQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


PR: Import sys for confpage

The confpage is missing an import and is thus not displayed in the spyder settings.
  File "/usr/lib/python3.8/site-packages/spyder/app/mainwindow.py", line 3175, in show_preferences
    widget = plugin._create_configwidget(dlg, self)
  File "/usr/lib/python3.8/site-packages/spyder/plugins/base.py", line 117, in _create_configwidget
    configwidget.initialize()
  File "/usr/lib/python3.8/site-packages/spyder/preferences/configdialog.py", line 72, in initialize
    self.load_from_conf()
  File "/usr/lib/python3.8/site-packages/spyder/preferences/configdialog.py", line 327, in load_from_conf
    checkbox.setChecked(self.get_option(option, default, section=sec))
TypeError: setChecked(self, bool): argument 1 has unexpected type 'str'
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/spyder/app/mainwindow.py", line 3175, in show_preferences
    widget = plugin._create_configwidget(dlg, self)
  File "/usr/lib/python3.8/site-packages/spyder/plugins/base.py", line 117, in _create_configwidget
    configwidget.initialize()
  File "/usr/lib/python3.8/site-packages/spyder/preferences/configdialog.py", line 72, in initialize
    self.load_from_conf()
  File "/usr/lib/python3.8/site-packages/spyder/preferences/configdialog.py", line 327, in load_from_conf
    checkbox.setChecked(self.get_option(option, default, section=sec))
TypeError: setChecked(self, bool): argument 1 has unexpected type 'str'
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/spyder/app/mainwindow.py", line 3175, in show_preferences
    widget = plugin._create_configwidget(dlg, self)
  File "/usr/lib/python3.8/site-packages/spyder/plugins/base.py", line 117, in _create_configwidget
    configwidget.initialize()
  File "/usr/lib/python3.8/site-packages/spyder/preferences/configdialog.py", line 71, in initialize
    self.setup_page()
  File "/usr/lib/python3.8/site-packages/spyder_terminal/confpage.py", line 50, in setup_page
    elif sys.platform.startswith('linux'):
NameError: name 'sys' is not defined

@steff456 please review.

Thanks @bnavigator !


I checked, but I can not send it.
Is it possible?

Still looking for.


clickhouse-cli: init at 0.3.6

Motivation for this change
Add clickhouse-cli
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build clickhouse-cli

Duplicate of #118862.


Add Text2Image UI

Description
Add Text2Image UI.
Issues
n/a.
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)
[ ] Others (enhancement, documentation, validation, etc.)

Dependencies
depend on the UI test complete.
Tests
CI pass.

@WenjiaoYue,
Please fix pre-commit issue.


Fix Null Reference exception encountered when batch is null upon orig…

What:

Fix NullReferenceException that happens whilst calling BatchLogError Gateway.

Why:

Whenever a legitimate error happens during the nightly process, if the batch remains, for some reason, set to null, the original error never gets reported to the batch log error & the process failure message gets obscured by this secondary null reference error.

As Adam has pointed out, we have the foreign key blocker when it comes to this patch solution to a dirty problem.
The proper solution will require more thought than there was (since the making of the PR) and is time available.


Updated with links to previous releases

Provides a link for visitors to see current and previous versions of Drill

Looks good! Thank you!

For older releases a single link to http://archive.apache.org/dist/drill would be better (you won't have to update this very time there is a release).

Agreed. We do need a single place for showing the releases. I'll work with Bridget to change at both places.

@kkhatua / @parthchandra  should we close the PR or what other work should be done?

@arina-ielchiieva  I'll change the PR as suggested by Parth. Since Bridget does the merges for gh-pages repo, I'll ask her to close the PR.

@kkhatua any update on this?

Closing this for now. Will reopen as part of a broader set of changes for the website.


Locations say "last update: June 03, 2016 by" blank

Like, they say "by" blank. If they HAVE been edited by a user, the username is displayed.

Can you give me a region/location example?
You don't see this happening in 4.0.0?

Region: Portland.
Location: Union Barrel.
I can't confirm whether it was happening in 4.0.0, because I don't have that installed right now. But I didn't think it was... could be wrong.

Just downgraded and checked... appears to be an issue in 4.0.0.

Ok, I'll change the title.

https://github.com/scottwainstock/pbm-ios/commit/91c3c6ba73ff0d9da36ea830f50aef85e72bb236

I'm still seeing this on iphone and ipad.
Example location: It's Game Time, in the Los Angeles region. The "last update" in the location info still has "by "
Another example, but this time on machine comments: Pinz Bowling Center, in LA. The "past conditions" on some of the machines say "by " still. But strangely, one of them does not (Pirates of the Caribbean).

Here's what I see right now:

...seems right. You see something else? Pirates doesn't have the "by" because it was created pre-user system.

Yes, that's what I see when looking at the location details. But when I click the machine name to view past conditions, I see:

Oh yeah ok, got it.

On Aug 5, 2017, at 09:42, RyanTG<EMAIL_ADDRESS>wrote:
Yes, that's what I see when looking at the location details. But when I click the machine name to view past conditions, I see:
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

And here's what it looks like for a location's "last update" date (the other screenshots were showing machine comment dates):

https://github.com/scottwainstock/pbm-ios/commit/8fefecc953344a9d9d4bcca92444d950e0ca3814

New build notification should have just gone out.
On Sat, Aug 5, 2017 at 12:25 PM, RyanTG<EMAIL_ADDRESS>wrote:

And here's what it looks like for a location's "last update" date (the
other screenshots were showing machine comment dates):
[image: img-4671]
https://user-images.githubusercontent.com/632682/28998140-265e3bae-79d9-11e7-893a-ecd2fb2ae404.PNG
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/scottwainstock/pbm-ios/issues/135#issuecomment-320465323,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAK-LdjypSHpIesxhYlu6Ih9TmQQHHeQks5sVMHDgaJpZM4MiByH
.

Looks fixed on the "last update" for locations. But still not fixed for past machine comments. Mustang and Ghostbusters are Pinz in los angeles still show "by".
Perhaps it's not worth continuing to work on this, given that these comments are relics of the past and will eventually be phased out.

Can you exit and re-enter the region? Part of this was a json parsing issue. So, you need the app to retry parsing the initial region load.

On Aug 5, 2017, at 16:34, RyanTG<EMAIL_ADDRESS>wrote:
Looks fixed on the "last update" for locations. But still not fixed for past machine comments. Mustang and Ghostbusters are Pinz in los angeles still show "by".
Perhaps it's not worth continuing to work on this, given that these comments are relics of the past and will eventually be phased out.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I changed regions, and reinstalled the app, and I'm still seeing that. The "by" is gone for you?

Yeah. I reinstalled in the emulator and it all seemed fine. I'll check again.

On Aug 5, 2017, at 18:09, RyanTG<EMAIL_ADDRESS>wrote:
I changed regions, and reinstalled the app, and I'm still seeing that. The "by" is gone for you?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Jesus christ, OK... looks like it's still broken.

https://github.com/scottwainstock/pbm-ios/commit/f8672201828493fb70c335b0fe7706fea56cad04

Victory.
Thanks for fixing it! I'm going to close this. So all the 4.0.2 issues are resolved!


IBM block storage CSI Integration with IBM Cloud Satellite Storage

GHE issue: #26

can you also provide example pvc / pv and app pods per the readme - https://github.com/IBM/ibm-satellite-storage/blob/develop/.github/README_TEMPLATE.md#deploying-an-app-that-uses-your-storage-configuration

can you also provide example pvc / pv and app pods per the readme - https://github.com/IBM/ibm-satellite-storage/blob/develop/.github/README_TEMPLATE.md#deploying-an-app-that-uses-your-storage-configuration

All pvc / pv/ app pods/ storageclass/ secret/ snapshot ect. examples with commands and outputs can be found in our Documentation. objects examples, using examples

tested (through API with storageclass) and working.


Error 403 from "librealsense.intel.com" on Ubuntu 21

I followed these instructions: https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md
Had success on a testbench running an older Ubuntu but not on my Ubuntu 21.10 workstation.
terminal dump:
yuqi@yuqi:~$ export http_proxy="http://<IP_ADDRESS>:20171"
yuqi@yuqi:~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-key F6E65AC044F831AC80A06380C8B3A55A6F3EFCDE || sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-key F6E65AC044F831AC80A06380C8B3A55A6F3EFCDE
[sudo] password for yuqi:
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.QtBL9KP8d6/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-key F6E65AC044F831AC80A06380C8B3A55A6F3EFCDE
gpg: key C8B3A55A6F3EFCDE: ""CN = Intel(R) Intel(R) Realsense", O=Intel Corporation" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
yuqi@yuqi:~$ sudo add-apt-repository "deb https://librealsense.intel.com/Debian/apt-repo $(lsb_release -cs) main" -u
Repository: 'deb https://librealsense.intel.com/Debian/apt-repo impish main'
Description:
Archive for codename: impish components: main
More info: https://librealsense.intel.com/Debian/apt-repo
Adding repository.
Press [ENTER] to continue or Ctrl-c to cancel.
 Done
E: Failed to fetch https://librealsense.intel.com/Debian/apt-repo/dists/impish/InRelease  403  Forbidden [IP: <IP_ADDRESS> 443]
E: The repository 'https://librealsense.intel.com/Debian/apt-repo impish InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
yuqi@yuqi:~$ sudo apt-get install librealsense2-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package librealsense2-dkms is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'librealsense2-dkms' has no installation candidate
yuqi@yuqi:~$ sudo apt-get install librealsense2-utils
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package librealsense2-utils
yuqi@yuqi:~$

I tried with and without proxy, same result. (In China if it makes a difference)
yuqi@yuqi:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 21.10
Release:	21.10
Codename:	impish
yuqi@yuqi:~$ cat /proc/version
Linux version 5.13.0-22-generic (buildd@lgw01-amd64-012) (gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #22-Ubuntu SMP Fri Nov 5 13:21:36 UTC 2021

Hi @CyberFoxHax  The librealsense SDK currently supports up to Ubuntu 20.04 (Focal).  You are the first RealSense user who has reported trying to use it with Ubuntu 21.
If you build librealsense from source code with CMake using the RSUSB backend method instead of building with packages then it will not be dependent on Linux versions or kernel versions and will not require patching.  https://github.com/IntelRealSense/librealsense/issues/6689#issuecomment-648758973 has instructions for performing an RSUSB backend installation.

Hi @CyberFoxHax  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.

Busy period. Set up a Windows environment for Realsense. This is a temporary workaround, i'll try to build from source in a few weeks.

Okay, thanks very much @CyberFoxHax for the update.  I look forward to your next report.  Good luck!

Hello @MartyG-RealSense, I came across this thread as I'm trying to install the SDK on Linux Mint which is running Ubuntu v21.2. I noticed the SDK only runs on v20 and v22, is there a reason why v21 got skipped?

Hi @szymonborkowski  I am not aware of the development reasons for going from 20.04 to 22.04 but there has not been any demand from the RealSense community for 21.2 support.
You should be able to use the SDK with 21.2 if you build it from source code with CMake with the build flag -DFORCE_RSUSB_BACKEND=TRUE included in the CMake build instruction though.  This is because an RSUSB build of the SDK bypasses the kernel and so it is not dependent on Linux versions or kernel versions and does not need to be kernel patched.
Instructions for an RSUSB build can be found at https://github.com/IntelRealSense/librealsense/issues/9931#issuecomment-964289692


Fix --manifest-path Cargo.toml

Fixes #928.
Observation

--manifest-path ./Cargo.toml works
--manifest-path Cargo.toml does not:Unable to run the check command: 'cargo check' at ''

Cause

path.parent() yields an empty string for Cargo.toml

Proposed solution

path.canonicalize().parent().

Why this is a problem

--manifest-path Cargo.toml is an accepted flag for normal cargo. In my case it caused an error in combination with minimal-versions, which adds --manifest-path Cargo.toml to the command:cargo minimal-versions msrv verify

which fails without this PR, and succeeds with it.

@foresterre would you mind releasing a .21 with it soon? I kind of need it for the CI of a project of mine :)

Absolutely. Thanks again!
(GitHub release), crates.io


Deleting a snowflake_user and their associated snowlfake_role_grant causes an error

Provider Version
$ terraform version
Terraform v0.14.11
+ provider registry.terraform.io/aidanmelen/snowsql v0.2.1
+ provider registry.terraform.io/chanzuckerberg/snowflake v0.25.36

Describe the bug
When you delete a snowflake_user and their associated snowflake_role_grant, you'll get an error. The user and the grant are both deleted successfully, but you still get an error.
Expected behavior
The user and the role grant should be deleted without an error.
Code samples and commands
locals {
  staff = [
    "aperson",
    "bperson",
    "cperson",
  ]
}

resource "snowflake_role" "humans" {
  name    = "HUMANS"
  comment = "A role."
}

resource "snowflake_user" "humans" {
  for_each             = toset(local.staff)
  name                 = upper(each.key)
  login_name           =<EMAIL_ADDRESS>  disabled             = false
  display_name         = upper(each.key)
  email                =<EMAIL_ADDRESS>  password             = null
  default_role         = snowflake_role.humans.name
  must_change_password = false
}

resource "snowflake_role_grants" "grants" {
  role_name  = snowflake_role.humans.name
  users      = [for user in local.staff : upper(user)]
  depends_on = [snowflake_user.humans]
}

Additional context

Apply the above infrastructure which will create a role, three users, and it will grant three users access to the role.
Delete bperson from the staff list.
Run an plan and Terraform will propose that it's going to drop the user and their role grant, as expected.

  # snowflake_role_grants.grants will be updated in-place
  ~ resource "snowflake_role_grants" "grants" {
        id        = "HUMANS"
      ~ users     = [
          - "BPERSON",
            # (2 unchanged elements hidden)
        ]
        # (2 unchanged attributes hidden)
    }

  # snowflake_user.humans["bperson"] will be destroyed
  - resource "snowflake_user" "humans" {
      - default_role         = "HUMANS" -> null
      - disabled             = false -> null
      - display_name         = "BPERSON" -> null
      - email                =<EMAIL_ADDRESS>-> null
      - has_rsa_public_key   = false -> null
      - id                   = "BPERSON" -> null
      - login_name           =<EMAIL_ADDRESS>-> null
      - must_change_password = false -> null
      - name                 = "BPERSON" -> null
    }

Plan: 0 to add, 1 to change, 1 to destroy.

Run an apply and you'll get this error:

Error: 002003 (02000): SQL compilation error:
User 'BPERSON' does not exist or not authorized.

  on test.tf line 26, in resource "snowflake_role_grants" "grants":
  26: resource "snowflake_role_grants" "grants" {

The user and their grant are both deleted as expected, so you shouldn't get any error.

Any updates on this one?
I have the same issue.


Fix the handling of multibyte characters

Motivation
refs: https://github.com/Shopify/ruby-lsp/pull/2021#issuecomment-2110394331
When a Ruby file contains multibyte characters (like Japanese, Chinese, emoji, etc), the go to definition and hover features do not work correctly. Because the document referencing logic does not properly handle multibyte characters when calculating offsets.
This commit fixes the issue by:

Modifying document referencing to properly handle multibyte characters when mapping between positions and offsets
Adding test cases to verify go to definition work with multibyte characters

Implementation

Modified RubyLsp::Document and RubyLsp::Requests::Request to calculate locations considering multibyte characters. This change utilizes the API implemented in Prism by https://github.com/ruby/prism/pull/2406.
By passing the encoding when creating the Index, the index will be built taking multibyte characters into account.

Automated Tests

I added some tests for the definition and RubyLsp::RubyDocument.
Manual Tests

The definition jump for the following code snippet from https://github.com/shopify/ruby-lsp/issues/1347 works in this branch, but does not function correctly in the main branch.
class Test
  TEST = 'test'

  def method1
    # テスト
    pp TEST
  end
end

cc @kddnewton in case you have any views on the Prism usage here.

It appears that from 'be648a6' onwards, it no longer works correctly on VSCode.
I'll try to fix it. I would appreciate any advice you can provide.

@vinistock
I would appreciate it if you could kindly provide your comments on this PR. Should we wait for the implementation of ResourceUri?


Servers are not opening up in default as well as port 80

Port 80
{ Error: bind EINVAL ::1:80
at state.handle.lookup (dgram.js:242:18)
at process._tickCallback (internal/process/next_tick.js:63:19)
at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
errno: 'EINVAL',
code: 'EINVAL',
syscall: 'bind',
address: '::1',
port: 80 }
{ Error: bind EINVAL fe80::24cf:241b:39c1:4cee:80
at state.handle.lookup (dgram.js:242:18)
at process._tickCallback (internal/process/next_tick.js:63:19)
at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
errno: 'EINVAL',
code: 'EINVAL',
syscall: 'bind',
address: 'fe80::24cf:241b:39c1:4cee',
port: 80 }
// Default Port
{ Error: bind EINVAL ::1:3478
at state.handle.lookup (dgram.js:242:18)
at process._tickCallback (internal/process/next_tick.js:63:19)
at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
errno: 'EINVAL',
code: 'EINVAL',
syscall: 'bind',
address: '::1',
port: 3478 }
{ Error: bind EINVAL fe80::24cf:241b:39c1:4cee:3478
at state.handle.lookup (dgram.js:242:18)
at process._tickCallback (internal/process/next_tick.js:63:19)
at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
errno: 'EINVAL',
code: 'EINVAL',
syscall: 'bind',
address: 'fe80::24cf:241b:39c1:4cee',
port: 3478 }

I'm getting the same issue. It's strange because it was working for me a while back and I haven't changed anything about my setup. It sounds like a permissions issue. Or perhaps the port is already in use.

Looks like this is only a warning because it was unable to bind to certain ips. It's still binding to the ips I need them to because I get the correct results on https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/.
I did have to whitelist the port on my firewall though.

this error indicate that the port can't be bind, maybe use by an other instance of your project or an other application.
warning you are using ipv6 that is not supported by node-turn


Select unit testing library

This has been previously discussed on the  5 Calls wiki and in the development channel on Slack.
I have spend time prototyping unit test options. Jest -- my favored choice -- and Mocha work well, but have not been able to implement an in-browser solution despite working on it for a few days. I know that in-browser testing is favored by some in this group and is what we have done in the Choo repo, but I -- and a vast majority of the React community -- believe that end-to-end tests should fill that niche. Our end-to-end tests should copy over from the Choo repository without major changes.
Any in-browser unit testing solution needs to be able to work with a variety of browsers, not just a headless browser like PhantomJS.
We should also make sure that the unit testing library we use is compatible with our Continuous Integration environment.
Comments and suggestions are welcome.

Since there has not been any discussion of alternatives, I'm going to implement a few tests in Jest. You should see a PR with this code in the next few days.

PR #11 implementing initial jest-enzyme unit testing has been merged into master


Fix leaky subscriptions in the Project Selector

Another step toward finishing #24.
Note: This currently contains the quickfix for the homescreen. This change can be ignored and will go away once #72 is merged into issue-24/master.

Note: This currently contains the quickfix for the homescreen. This change can be ignored and will go away once #72 is merged into issue-24/master.

If you set "base" to the PR with the homescreen change it'll disappear from the diff (click Edit next to PR desc).

Note: This currently contains the quickfix for the homescreen. This change can be ignored and will go away once #72 is merged into issue-24/master.

If you set "base" to the PR with the homescreen change it'll disappear from the diff (click Edit next to PR desc).

Good to know, thanks!


Parsing problem

I got an error "option doesn't allow an argument"
when run a command from readme:
pve-autosnap --daily --storage=local --leave=3
parse-options: option '--storage' doesn't allow an argument
parse-options: option '--leave' doesn't allow an argument
but it passes when I run it as shown below:
pve-autosnap --daily --storage local --leave 3

I think I repaired it some time ago:
https://github.com/michabbs/pve-autosnap/commit/2abccefe79a526e51ef97ce1651a0c2414752a27


Camera frustum planes computation bug?

Hello,
I was looking at this portion for the code and it seems like the cross product computation for the top and bottom planes might be off.
Shouldn't the last two cross products look as follows?
...

# top
torch.cross(
    frustum_corners[5] - frustum_corners[1], # top right far - top right near
    frustum_corners[0] - frustum_corners[1] # top left near - top right near
),
# bottom
torch.cross(
    frustum_corners[6] - frustum_corners[2], # bot left far - bot left near
    frustum_corners[3] - frustum_corners[2] # bot right near - bot left near
)

...

I'm assuming the frustum corners correspond to the following (in pixel+depth coordinates which are transformed to world coordinates before computing the planes):
corners = np.array(
        [
            [0, 0, min_depth], # 0 - top left near
            [width, 0, min_depth], # 1 - top right near
            [0, height, min_depth], # 2 - bottom left near
            [width, height, min_depth], # 3 - bottom right near
            [0, 0, max_depth], # 4 - top left far
            [width, 0, max_depth], # 5 - top right far
            [0, height, max_depth], # 6 - bottom left far
            [width, height, max_depth], # 7 - bottom right far
        ]
    )

I'm just checking but any clarification would be much appreciated!

Hi @AmineElhafsi,
thanks for the spot, this was a bug. The code didn't include top and bottom planes and led to more points selected. Since this part is preparing for neighbor search, I expect it has minimum effect on the pipeline.

Got it - thanks!


some remote extensions disappear in vscode

Type: Bug
Some remote extensions disappear in vscode after reloading vscode window. Those extensions exist on remote disk.
vscode window:
remote gitlens / ccls extensions disappear

remote:
gitlens / ccls extensions exist in: ~/.vscode-server/extensions

VS Code version: Code 1.74.2 (e8a3071ea4344d9d48ef8a4df2c097372b0c5161, 2022-12-20T10:29:14.590Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No
Remote OS version: Linux x64 3.10.107-1-tlinux2_kvm_guest-0056

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8 x 3000)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.78GB (19.10GB free)

Process Argv
--crash-reporter-id 887f76a1-42a5-4491-a127-ae98a413d02b

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: <IP_ADDRESS>

OS
Linux x64 3.10.107-1-tlinux2_kvm_guest-0056

CPUs
AMD EPYC 7K62 48-Core Processor (8 x 2595)

Memory (System)
15.35GB (14.16GB free)

VM
0%

Extensions (15)

Extension
Author (truncated)
Version

better-cpp-syntax
jef
1.17.2

vscode-language-pack-zh-hans
MS-
1.74.12140931

remote-ssh
ms-
0.102.0

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.72.0

vscode-remote-extensionpack
ms-
0.24.0

remote-explorer
ms-
0.4.0

remote-server
ms-
1.1.0

vscode-todo-highlight
way
1.0.5

t-extension
bkd
0.0.4

bazel-code
Dev
0.1.9

docker
vsc
1.0.0

yaml
vsc
1.0.0

highlight-trailing-white-spaces
yba
0.0.2

vscode-proto3
zxh
0.5.5

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
2e4cg342:30602488
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
showlangstatbar:30730054
azdwalk:30721579
pythonms35:30701012
pythonfmttext:30731395
fixshowwlkth:30730052
showsbindicator:30730056

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.78.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

We're seeing the identical issue. It's not always the same extensions that go missing.

Please try upgrading to the latest version and checking whether this issue remains.

I updated VSCode to 1.78.1 two weeks ago, and so far this issue has not occurred again.

Glad that you are not seeing this issue after updating. Please reopen the issue if you see it again with necessary info to reproduce.


POC Are Web-Component Wrapper Libraries needed?

Discussed in https://github.com/GovAlta/ui-components/discussions/293

Originally posted by tarynlaramie December 23, 2021
it may be possible that the Angular wrapper library is not needed. will scaffold a demo angular app to do a poc. Kevin has cycles and will do POC
preliminary discovery for React indicates that React probably requires the wrapper library
[] scaffold angular demo app
[] do poc

Through POC discovered that in order for these components to be user-friendly for teams we will need wrappers for both Angular and React libraries.


DragPreview not working on MS Edge

Hi
DragPreview example seems not working on MS Edge.
Currently on a project needs to build custom text preview while dragging.
Is there any workaround to achieve it on MS Edge?
Thanks

I was having trouble with this in my app and the only workaround I could find was to make the entire preview the drag source for IE.
`export function usingIE (windowOverride = window) {
const ua = windowOverride.navigator.userAgent
const edge = ua.indexOf('Edge/')
const ie11 = ua.indexOf('Trident/')
const ie10 = ua.indexOf('MSIE ')
return edge > -1 || ie11 > -1 || ie10 > -1
}`

+1

Any update on this?

Take a look at http://gaearon.github.io/react-dnd/docs-drag-source-connector.html at the "captureDraggingState" option.
Try something like this:
class Whatever extends Component {
    componentDidMount() {
        this.props.connectDragPreview(getEmptyImage(), {
            // IE fallback: specify that we'd rather screenshot the node
            // when it already knows it's being dragged so we can hide it with CSS.
            captureDraggingState: true,
        });
    }

    componentWillUpdate(nextProps) {
        this.aboutToDrag = nextProps.isDragging && !this.props.isDragging;
    }

    render() {
        const isUsingEdgeOrIE = ???; // @rfogar2's method is a good way to figure this out
        const style = this.aboutToDrag && isUsingEdgeOrIE && { display: 'none' };
        return
Drag me
;
    }
}

As a side note, the function @rfogar2 posted is good but probably shouldn't be called "usingIE". Treating Edge and IE the same is a bad idea because they're totally different browsers. IE uses the (terrible) Trident layout engine and Edge uses EdgeHTML. EdgeHTML is a fork of Trident, but with all legacy IE code removed and the majority of its source code rewritten. It complies with modern standards quite well and mostly behaves the same as Gecko and Blink. Of course, this particular case is a poor example of that.

Still getting this issue even when using connectDragPreview.

Hi, there is easy workaround, if you mean to change the draggable node and treat a parent like DragPreview.
const DndContainer = ({connectDragSource}) => {
  return connectDragSource(

 e.preventDefault()}>

 e.stopPropagation()}>
        Drag Me Here!

  )
}

It's all about handling mouseDown properly.

This does not work. I'm using a custom DragLayer and Edge simple does not handle this. Any workaround. Spent at least 16 hours on this.

Having the same issue.  Using connectDragPreview with getEmptyImage.
Is there any news on this?

Here is my solution, if you only want to hide the native preview image. (same as getEmptyImage)
// previous code (only work in chrome)
@DragSource(DragType, dragSpec, cnt => ({
  cntDragSource: cnt.dragSource(),
  cntDragPreview: cnt.dragPreview(),
}))
class Whatever extends Component {
    componentDidMount() {
      this.props.cntDragPreview(getEmptyImage());
    }
    render() {
        const { cntDragSource } = this.props;
        return cntDragSource(
Drag me
);
    }
}

// solution
@DragSource(DragType, dragSpec, cnt => ({
  cntDragSource: cnt.dragSource(),
  cntDragPreview: cnt.dragPreview(),
}))
class Whatever extends Component {
    componentDidMount() {
      this.props.cntDragPreview(getEmptyImage());
    }
    render() {
        const { cntDragSource } = this.props;
        return (
}>
            Drag me
            {connectDragSource(
)}

);
    }
}

add css to make .drag-tigger fill the container node.
/* The `.drag-tigger` node has't any UI style, just a transparent mask. so the preview image is transparent too */
.drag-trigger {
  position: absolute;
  pointer-events: all;
  top: 0;
  left: 0;
  right: 0;
  bottom: 0;
}

Hope this help.:smile:

Here is my solution, if you only want to hide the native preview image. (same as getEmptyImage)
// previous code (only work in chrome)
@DragSource(DragType, dragSpec, cnt => ({
  cntDragSource: cnt.dragSource(),
  cntDragPreview: cnt.dragPreview(),
}))
class Whatever extends Component {
    componentDidMount() {
      this.props.cntDragPreview(getEmptyImage());
    }
    render() {
        const { cntDragSource } = this.props;
        return cntDragSource(
Drag me
);
    }
}

// solution
@DragSource(DragType, dragSpec, cnt => ({
  cntDragSource: cnt.dragSource(),
  cntDragPreview: cnt.dragPreview(),
}))
class Whatever extends Component {
    componentDidMount() {
      this.props.cntDragPreview(getEmptyImage());
    }
    render() {
        const { cntDragSource } = this.props;
        return (
}>
            Drag me
            {connectDragSource(
)}

);
    }
}

add css to make .drag-tigger fill the container node.
/* The `.drag-tigger` node has't any UI style, just a transparent mask. so the preview image is transparent too */
.drag-trigger {
  position: absolute;
  pointer-events: all;
  top: 0;
  left: 0;
  right: 0;
  bottom: 0;
}

Hope this help.😄

This is the only solution that has worked for me consistently on Edge so far.


Markdown grammar contains invalid Oniguruma token [^]

VS Code Version: All
OS Version: All

This line in the Markdown grammar is an invalid Oniguruma pattern. The behavior for TextMate grammars when an invalid pattern is encountered (dutifully reproduced by vscode-textmate) is to silently fail, causing the regex to never match. So whatever it's intended to do is not happening.
The error in this pattern is the use of [^]]. From context, it's easy to figure out that the author meant for this to mean "match any character except ]"). However, that's not what it's doing. There are several different ways that different regex engines interpret this:

Most regex engines would say that, because ] is the first token within the (negated) character class, it is a literal ]. So, this would be a char class that matches any char except ]. This is what the author intended.
JavaScript in Unicode-aware mode (with flag u or v) would say this is a negated empty char class followed by an unescaped ], with the unescaped ] being an error.
JavaScript in Unicode-unaware mode (without flag u or v) would say this is a negated empty char class followed by a literal ]. So, this would match any char plus a following ].
Oniguruma uses the same interpretation as JavaScript in Unicode-unaware more (that this is a negated empty char class followed by a literal ]) except that, in Oniguruma, an empty char class is an error.

To fix this, the [^]] should be replaced with [^\\]] (escaped backslash since it's in a JS string). It will then run in Oniguruma.

Oniguruma does correctly parse [^]] as a inserted character with a single character ]
I assume it must be another part of the regex that isn't making it match as you expect
normally an invalid regex cause vscode-textmate to fail completely until the end of the line or file

Ugh! Thanks @RedCMD, and sorry for the invalid report. I believe some old versions didn't allow it, but I just tested Oniguruma 6.9.8 via vscode-oniguruma 2.0.1 and indeed it allows [^]] (although [] and [^] produce "empty char-class" errors as I described, and of course unescaped ] within a char class at any position other than as the first char ends the char class).

I believe some old versions didn't allow it

I believe soo too

vscode-main 1.95.3  ⇛  vscode-textmate 9.1.0  ⇛  vscode-oniguruma 1.7.0  ⇛   oniguruma 6.9.8


"コードの書式設定" is translation error.

VSCode Version:1.4.0
OS Version: windows10

"Format Code" => "コードの書式設定"
This Japanese translation is strange.This sentence means "configure coding format"
I found a same issue but request was rejected and issue has closed.
(https://github.com/Microsoft/vscode/pull/5296)
Correct translation is here :
"Format Code" => "コードのフォーマット"

@lukaschal Please recheck current translations of "Format Code"

Waiting for linguistic input.

@nemu626 Please, is it possible to add ENU and JPN screenshots for better context ?

@lukaschal

Fixed as suggested.
SRC: Format Code
NEW TGT: コードのフォーマット


Bot ARM deployment: Need a message about missing capabilities (in progress)

A couple of Bot Service ARM deployment capabilities are missing

Arm template export is missing bot service resources

Consider alternative. E.g. in the meantime export, edit as follows (or we don’t have a workaround at the moment)?

Service update via Arm template is not working. In the meantime, please use az cli commands to update Azure resources.

Related:  BUG 29052.

@scheyal - not clear what the ask is here. Could you submit a PR with the changes you'd like to see?

Closing per email conversation w/ Eyal.


Add MacOS Arm64 Agents Setup and AMI IDs

Description
Add MacOS Arm64 Agents Setup and AMI IDs
Issues Resolved
https://github.com/opensearch-project/opensearch-build/issues/4670
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Waiting for https://github.com/opensearch-project/opensearch-ci/pull/477


Speedup CI by running all appraisals in one travis job

Currently ci is running 1 hour 15 minutes in average. This should significantly improve this time. Let's see, if I'm correct.

Ok, speedup is not as significant, because I was fooled by travis' ci namings - 1 hour 15 min is sum across all jobs, while actual run time is near 16 minutes on average.
This change reduces runtime to less than 5 minutes (> 3 times speedup).
@grzuy Wdyt, is this change worth it?

@grzuy Wdyt, is this change worth it?

I think it doesn't.
At least, as of today, don't see the TravisCI build time as something we need to fix.
Thank you for taking a stab at this anyway!
Might be helpful in the future.

Yes, if it was really 1.15 hour, then we would definitely need to fix that 😀


Two issues in send_command

https://github.com/johnmehr/gitup/blob/6e3578902887b5d4d4dd1d1a9d669689241299ab/gitup.c#L950

BUFFER_UNIT_SMALL + want_size bytes is allocated, but up to BUFFER_UNIT_LARGE could be filled up.

Host: github.com is hardcoded into request.

Thank you for finding these!  I just pushed out an update that corrects the bugs.

Sorry about that!  Those were leftovers from some code I decided to remove for now.  One of the things I really want gitup to be able to do is repair a local tree in case files are deleted so that after every update, the local tree is always in a usable state.


Is wsl, VSCode now hogs the prompt

Type: Bug
VSCode has started hogging the prompt in wsl and not running as a background (?) task.  Can we please revert this behaviour?
VS Code version: Code 1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:55:25.390Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.83.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Fixed in 1.83 already, please update vscode


C419 introduce invalid python since v0.5.3

HI,
Since v0.5.3 and the changes made in https://github.com/astral-sh/ruff/pull/12364, ruff autofix introduced breakage in my code.
The following was autofixed from this:
timedelta_list = [dt.timedelta(days=2),dt.timedelta(days=1)]
res = sum(
    [
        delta
        for delta in timedelta_list
        if delta
    ],
    dt.timedelta(),
).total_seconds()

to this
timedelta_list = [dt.timedelta(days=2),dt.timedelta(days=1)]
res = sum(
    delta
        for delta in timedelta_list
        if delta,
    dt.timedelta(),
).total_seconds()

Thanks, we need to parenthesize in those cases.

Thanks, we need to parenthesize in those cases.
Yes exactly! Thanks for the quick response!

Sorry about that -- will try to fix soon.

No worries, thanks for the great work on this tool all-together.
I don't know if it's enough to yank the v0.5.3 given that every user with this rule already selected might be affected automatically when upgrading ?

I think I'll just cut a new release today with the fix (#12422).

It's also a preview-only behavior I think, so it's less urgent.


Better GL context initialization

Fixes #3519 for real this time
Fixes #3534
Drops X11 dependency :tada:
PR checklist:

[x] make succeeds (on *nix)
[ ] make reftests succeeds
[x] tested examples with the following backends: GL

The quad example runs, but the tests crash with SIGSEGV for me:
0x00007ffff76b9a80 in ?? ()
(gdb) bt
#0  0x00007ffff76b9a80 in ?? ()
#1  0x00007ffff780bd4e in ?? () from /usr/lib/libxcb.so.1
#2  0x00007ffff780c19e in ?? () from /usr/lib/libxcb.so.1
#3  0x00007ffff780cee9 in xcb_send_request () from /usr/lib/libxcb.so.1
#4  0x00007ffff781ef04 in xcb_query_extension () from /usr/lib/libxcb.so.1
#5  0x00007ffff780fe51 in xcb_prefetch_extension_data () from /usr/lib/libxcb.so.1
#6  0x00007ffff78b4793 in ?? () from /usr/lib/libEGL_mesa.so.0
#7  0x00007ffff78b3ac8 in ?? () from /usr/lib/libEGL_mesa.so.0
#8  0x00007ffff78aeb23 in ?? () from /usr/lib/libEGL_mesa.so.0
#9  0x00007ffff78aac3d in ?? () from /usr/lib/libEGL_mesa.so.0
#10 0x00007ffff78aac8a in ?? () from /usr/lib/libEGL_mesa.so.0
#11 0x00007ffff78a5298 in ?? () from /usr/lib/libEGL_mesa.so.0
#12 0x0000555555b989ad in khronos_egl::initialize (display=...) at /home/kvark/.cargo/registry/src/github.com-1ecc6299db9ec823/khronos-egl-2.2.0/src/lib.rs:756
#13 0x0000555555b319c7 in <gfx_backend_gl::window::egl::Instance as gfx_hal::Instance<gfx_backend_gl::Backend>>::create () at src/backend/gl/src/window/egl.rs:70
#14 0x00005555559cb0c7 in reftest::Harness::run (self=0x7fffffffe0e8, name=..., disabilities=...) at src/warden/src/bin/reftest.rs:103
#15 0x00005555556fdb1c in reftest::main () at src/warden/src/bin/reftest.rs:237

Anyhow, let's proceed. We can fix all the things at once.
bors r+


Losts of duplicated tasks created?

we currently have 5 machines to run sidekiq with sidekiq-scheduler enabled. but the situation is every worker will start a scheduled job at time which means that there will be 4 duplicated jobs created.
how can I solve this?

I use sidekiq-unique-jobs to ensure uniqueness, but seems it fails with sidekiq-scheduler

Could you please provide more info about the unique job configuration?
On the meantime you can enable the scheduler only on one machine.
Sidekiq::Scheduler.enabled = !!ENV['USE_SCHEDULER']

And configure that variable on only one of the machines.

@elpic problem solved, it's the sidekiq-unique-jobs fault. it doesn't inject server middleware to sidekiq so the uniqueness check only works on client side.

@doomsplayer,
Could you explain a bit more? How did you fix it?
By the looks of it, sidekiq-unique-jobs should inject sidekiq-unique-jobs/server/middleware.

Ah it’s too long ago and I do not quite remember it. I left the company so
there’s no way for me to checkout the exact commit. But IIRC, I manually
inject the middleware for server at that time. I suspect the issue is
related to the initialization order.
On Thu, Sep 21, 2017 at 9:14 PM Joakim Nylén<EMAIL_ADDRESS>wrote:

@doomsplayer https://github.com/doomsplayer,
Could you explain a bit more? How did you fix it?
By the looks of it, sidekiq-unique-jobs should inject
sidekiq-unique-jobs/server/middleware.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/moove-it/sidekiq-scheduler/issues/70#issuecomment-331345616,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA88zjl-PY6RZOy9pKkwrKWDj73o8vwFks5skzQ1gaJpZM4Gs2VS
.

--
Young Wu
Data Scientist
MSc @ SFU Database System Lab
a: 8888 University Dr, Burnaby, BC V5A 1S6, Canada
w: wooya.me  e<EMAIL_ADDRESS>https://cn.linkedin.com/in/wooya


Yosegi-45 The heap size of PrimitiveCell is large in write processing.

What is the necessity of this update? What is updated?
A large amount of memory required for write processing.
In the current code, an instance of Cell consumes Heap.
   1:        308131       11870736  [C
   2:        526893        8430288  jp.co.yahoo.yosegi.message.objects.IntegerObj
   3:        526893        8430288  jp.co.yahoo.yosegi.spread.column.IntegerCell
   4:        308109        7394616  java.lang.String
   5:        457938        7327008  jp.co.yahoo.yosegi.spread.column.StringCell
   6:        434261        6948176  jp.co.yahoo.yosegi.message.objects.StringObj
   7:         20947        6861712  [Ljava.lang.Object;
   8:          5632        5431032  [B
   9:         64791        1554984  java.lang.Double
  10:         69871        1117936  java.lang.Integer

Create instance at requested timing without caching Cell instance.
This reduces the heap size required to cache the number of elements * 16 bytes.
   1:        249410        9509632  [C
   2:        396763        6348208  jp.co.yahoo.yosegi.message.objects.IntegerObj
   3:        249388        5985312  java.lang.String
   4:        341288        5460608  jp.co.yahoo.yosegi.message.objects.StringObj
   5:         17019        4873384  [Ljava.lang.Object;
   6:          4204        4106448  [B
   7:         48519        1164456  java.lang.Double
   8:         53580         857280  java.lang.Integer
   9:         48519         776304  jp.co.yahoo.yosegi.message.objects.DoubleObj
  10:         10778         431120  java.util.LinkedHashMap$Entry

How did you do the test? (Not required for updating documents)
Added unit tests to new classes.

How to test describe is only a comment.
It would be appreciated if you could consider it during the next test making.
After your checking my comment, I will process next.

@yohto
Thanks for the review, and the advice about the test.
I changed the method name of the test.
Can you request a review again?

It conformed to "coding conventions".
https://github.com/yahoojapan/yosegi/blob/master/docs/code_conventions.md
@yohto
Please review again.


HYC-65 verifier lib

What does it do?
Documents and implements CI for verifier contract lib.
Any helpful background information?
Does not automatically publish packages, must be tagged and published manually by team.

Full project CI is broken, should be fixed on issue HYC-78.


Why is the minimum sdk level 14? Can you use 9?

I'd like to support old devices (min 9 api level), but I can't.

It is generally better to support API 14 and above.
But in your case i understand that you need API 9.
It is related with the animations.
I will see today what can I do about this issue.
I will keep you posted.

I forked patternview-project and changed min sdk level on 9. It built successfully. Can you upload new version with fixed level in maven central?

You need to make pull request of your fork.
And if everything is allright I will merge it and upload it to maven.

from version 1.0.2


Feature/UI redesign footer #861

Redesign Footer&Header
What does this PR do?

Resolve #861

Steps to test

make start
navigate to http://localhost:3000/ and see footer&header

CheckList

[ ] Follow proper Markdown format
[ ] The content is adequate
[ ] The content is available in both english and spanish
[ ] I Ran a spell check

See attached images:

See images for colapsed sidebar


Running Mocha Tests

I am trying to run Mocha tests and provided the environment variables when I execute them:
AWS_LAMBDA_FUNCTION_NAME=Lambda AWS_EXECUTION_ENV==AWS_Lambda_nodejs8.10 mocha 'Tests/**/*.js'
But I get the following error:
Error: Cannot find module 'iltorb'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:580:15)
    at Function.Module._load (internal/modules/cjs/loader.js:506:25)
    at Module.require (internal/modules/cjs/loader.js:636:17)
    at require (internal/modules/cjs/helpers.js:20:18) ...

Is there a way to run these tests?

@waqas-syed Can you retry with the extra = in AWS_EXECUTION_ENV removed?

My bad, I fixed it and I now have new findings. I am testing on 2 environments and getting different errors, I will go by them one-by-one:
AWS Cloud9(Linux):
The module '/home/ec2-user/environment/deploy-api/node_modules/chrome-aws-lambda/source/iltorb/build/bindings/iltorb.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
Error: The module '/home/ec2-user/environment/deploy-api/node_modules/chrome-aws-lambda/source/iltorb/build/bindings/iltorb.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:717:18)
    at Module.load (internal/modules/cjs/loader.js:598:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
    at Function.Module._load (internal/modules/cjs/loader.js:529:3)
    at Module.require (internal/modules/cjs/loader.js:636:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (/home/ec2-user/environment/deploy-api/node_modules/chrome-aws-lambda/source/iltorb/index.js:10:40)
    at Module._compile (internal/modules/cjs/loader.js:688:30)...

Now I tried npm rebuild chrome-aws-lambda --update-binary, deleted and reinstalled npm dependencies, even downgraded node version from 10.16.0 to 10.14.1, but nothing helped.

Mac OS:
With node version = 10.14.1, I am getting different problem on Mac:
dlopen(/Users/syedwaqas/Documents/Repos/deploy-api/node_modules/chrome-aws-lambda/source/iltorb/build/bindings/iltorb.node, 1): no suitable image found.  Did find:
        /Users/syedwaqas/Documents/Repos/deploy-api/node_modules/chrome-aws-lambda/source/iltorb/build/bindings/iltorb.node: unknown file type, first eight bytes: 0x7F 0x45 0x4C 0x46 0x02 0x01 0x01 0x00
        /Users/syedwaqas/Documents/Repos/deploy-api/node_modules/chrome-aws-lambda/source/iltorb/build/bindings/iltorb.node: unknown file type, first eight bytes: 0x7F 0x45 0x4C 0x46 0x02 0x01 0x01 0x00
Error: dlopen(/Users/syedwaqas/Documents/Repos/deploy-api/node_modules/chrome-aws-lambda/source/iltorb/build/bindings/iltorb.node, 1): no suitable image found.  Did find:
        /Users/syedwaqas/Documents/Repos/deploy-api/node_modules/chrome-aws-lambda/source/iltorb/build/bindings/iltorb.node: unknown file type, first eight bytes: 0x7F 0x45 0x4C 0x46 0x02 0x01 0x01 0x00
        /Users/syedwaqas/Documents/Repos/deploy-api/node_modules/chrome-aws-lambda/source/iltorb/build/bindings/iltorb.node: unknown file type, first eight bytes: 0x7F 0x45 0x4C 0x46 0x02 0x01 0x01 0x00
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:717:18)
    at Module.load (internal/modules/cjs/loader.js:598:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
    at Function.Module._load (internal/modules/cjs/loader.js:529:3)
    at Module.require (internal/modules/cjs/loader.js:636:17)
    at require (internal/modules/cjs/helpers.js:20:18)

Lastly, I am giving the name of the Lambda function as it is provided in template.yaml, like AWS_LAMBDA_FUNCTION_NAME=VericacheGeocachingScan but I also tried AWS_LAMBDA_FUNCTION_NAME=VericacheGeocachingScan/index.handler but didn't help.
Hope this gives more insight.

@waqas-syed This is why I asked about your environment.
This package is specifically targeting nodejs8.10 AWS Lambda environment, if you deviate from it, this kinds of errors are to be expected. The bundled iltorb is incompatible with your Node.js versions.
What you can try doing in this case is drop the AWS_EXECUTION_ENV entirely and add iltorb:
npm install iltorb --save-dev

Alternatively, you can consider downgrading your Node.js version to match AWS Lambda version (8.10).

@waqas-syed With the 1.20.0 version, this package should now work using the native Brotli module of Node 10.16.0+, so no need for bundled iltorb dependency on your local system (Chrome binary might still not be compatible though), for that refer to the Local Development Wiki page.


added: auto detect placement

Added ability auto detecting direction for open calendar. Closed #695 #347

Coverage decreased (-2.4%) to 97.566% when pulling 9c4ec257f52d2647bb332fab88a207e3214a0271 on adenvt:auto-placement into de0fc75fe6f6572eebf47f94da20716ab7690cff on charliekassel:master.

@adenvt this would be swell to have.  Any idea how we get this merged?

@charliekassel Are you able to have a look?

@tooolbox i think it because coverage too low, but i dont know how to increase it, i'm not very good at unit testing. Maybe someone can help me write the test.


Enhance match struct with the matched_string field

Add the field matched_string to Match struct. This field will store the code snippet matched by the rule.

I totally agree to what u say. I think we should not do this.
I was leaning towards usability over performance. But i feel this will get really bad when we capture these large constructs like class or file.
With storing references comes lifetimes :|

Another problem is that, we are using this Match struct for our python bindings too.
And pyo3 library doesnt support struct with lifetimes.

In the case of edits/rewrites, I wonder what would happen if there is no matched string.
I may be misunderstanding, but we might not be able to get the original match content if rewrites (e.g., delete a function) happen.

yes. And Diego makes a good point too. If we dont do this eagerly we will not be able to report it at all.

I think I am gonna merge this. It might have performance implications (in memory) but I guess its alright. Neither do we have any benchmarks to empirically prove how bad it is. @lazaroclapp  what do u think ? (I know u have already accepted the PR)

I think I am gonna merge this. It might have performance implications (in memory) but I guess its alright. Neither do we have any benchmarks to empirically prove how bad it is. @lazaroclapp what do u think ? (I know u have already accepted the PR)

I think this makes sense to me, given the complications involved in designing something that would work well with deletions (I am sure there is some involved copy-on-write way to handle it, but it feels like premature optimization). Separate from this PR, a good question is whether we have any way to measure internally Piranha's memory usage. But, also, I wouldn't worry too much about it unless we start seeing issues, since it's not like Piranha is running during a standard build or anything like that. It is very much an "off main pipeline" tool 🙂

Thanks a lot. I will merge this PR.
Filed the issue https://github.com/uber/piranha/issues/322 to track this.


Resolver type error

Hi, I'm using graphql-code-generator v0.10.1.
When query root is defined in snake case, the resolver type name is not generated properly.
schema:
snake_case_root_query(
  arg: snake_case_arg
): snake_case_result

generated type:
export type Snake_case_root_queryResolver = Resolver<
  snake_case_result,
  Snake_case_root_queryArgs  # <- NG
>;

export interface SnakeCaseRootQueryArgs {  # <- OK
  arg: snake_case_arg
}

@kamilkisiela 👍

This is still an issue for me in 0.10.5.

@rogersp that's because all is pascalCased


iOS: on iOS 8, open in safari doesn't work

Another user claims it happens on iOS 9 as well. Both iPhones.


[Feature] Here's a map I made

Hello, I just thought I'd share this project I did in me free time:
https://sacovidmap.netlify.com/

My code is open source so anyone who who's working on anything related may use as much of it as they want:
https://github.com/webdevan/covid-map
Disclaimer: I'm not a scientist, so use this at your own risk.
I'm using the cumulative cases CSVs in this repo and should update automatically when new data is merged (if the structure changes my map will break!). I might submit an issue to discuss how we can structure the data in a way that can scale (because it is likely to keep expanding and evolving so getting some standards and structure going would be helpful).
Anyway, just wanted to put this out there so that people can use it, and if there's any feedback let me know.

Thank you @webdevan


TOOL-Remove-StringSpecialCharacter - Minus sign in regex

If  SpecialCharacterToKeep contains minus sign the result is wrong. For example:
Remove-StringSpecialCharacter -String "wow#@!`~)(|?/}{-=+" -SpecialCharacterToKeep "","","-","/" returns  wow/_*
The solution is to escape minus sign. Something like this:  IF ($Character -eq "-") {$Regex +="-"} else {$Regex += [Regex]::Escape($Character)}
Other problem is that the forward slash in front of the special characters seems unnecessary in line $Regex += "/$character"

Thanks @hegedusg ! Great input! Should have thought of it!
Will update the code this week-end! Really appreciated!

Whoups forgot about this one. Correct in this commit: https://github.com/lazywinadmin/PowerShell/commit/c45d1a7733c66c27fdd4d3c309da6cc3d031fd80
Thanks again @hegedusg


Split one model's different parts on different gpus

🚀 Feature

Motivation

Related to this torch Model Parallel tutorial:
https://pytorch.org/tutorials/intermediate/model_parallel_tutorial.html

In my case, I have a simplified large model like this:
class MyLargeModel(pl.LightningModule):
    def __init__(self):
        super().__init__()
        # a large backbone like bert
        self.bert = Bert().to("cuda:0")

        # a very very large classifier layer with 6 million classes
        self.classifier = nn.Linear(768, 6_000_000).to("cuda:1")

    def forward(x):
        emb = self.bert(x.to(self.bert.device))
        score = self.classifier(emb.to(self.classifier.device))
        return score

self.classifier is so large that it must be on another gpu.
However, if I simply set pl.Trainer:
trainer = pl.Trainer(
    ...
    gpus=2,
    ...
)

It will copy the model on two gpus (and both will raise CUDA out of memory), rather than split it on two gpus.

Pitch
A easy way to manually split one model on different device like the tutorial above.

Alternatives

Additional context

PyTorch Lightning has support for FairScale, see here. You can add define the model as
self.model = nn.Sequential(Bert(), Linear(10, 20)) # __init__()
...
...
self.model(x) # forward()
...
plugin = RPCSequentialPlugin(balance=[1, 1])
trainer = Trainer()

Hey @dalek-who,
I won't recommend to use RPCSequentialPlugin  as it will be soon depreciated.
Instead, you can DeepSpeed Integration: https://pytorch-lightning.readthedocs.io/en/stable/advanced/multi_gpu.html?highlight=deepspeed#deepspeed.
 It can also be used on only 1 gpu with activation_checkpointing and cpu_offload.
Give it a try and give us feedback.
Best,
T.C

@tchaton Can you provide a simple DeepSpeedPlugin example for my case like RPCSequentialPlugin ?

Oh, I wasn't aware of the deprecation. Sorry about that.

Hey guys )
Regarding the deprecation of the RPCSequentialPlugin this is being done within #6152 with more information coming in the following weeks on how you can leverage FSDP instead for simpler balancing of the model across GPUs! No need to be sorry @vballoli we'll make this clearer in the follow week!
DeepSpeed Stage 3 offers the same practice which we already have within Lightning. A minimal example of how all this can work can be found here: https://github.com/SeanNaren/minGPT/tree/stage3
Regarding a layer (in this case self.classifier) being too large to fit onto one GPU, we offer a hook called configure_sharded_model within the LightningModule, which is built just for this.
https://pytorch-lightning.readthedocs.io/en/latest/advanced/multi_gpu.html#shard-model-instantly-to-reduce-initialization-time-memory
We are planning on a refresh in the documentation to make it easier to find these tidbits, as things have become a bit complex in the ecosystem.
For a small example:
class MyLargeModel(pl.LightningModule):
    def __init__(self):
        super().__init__()
        # a large backbone like bert
        self.bert = Bert()

    def configure_sharded_model(self):
        # a very very large classifier layer with 6 million classes, is now sharded instantly onto all GPUs
        # Using DeepSpeed Stage 3
        self.classifier = nn.Linear(768, 6_000_000)

    def forward(x):
        emb = self.bert(x)
        score = self.classifier(emb)
        return score

trainer = pl.Trainer(
    gpus=4,
    plugins='deepspeed_stage_3'
)
trainer.fit(model)

DeepSpeed Stage 3 shards the model across all GPUs, but configure_sharded_model allows this to happen instantly, saving memory and allowing you to instantiate really large layers. More information about Stage 3 here: https://pytorch-lightning.readthedocs.io/en/latest/advanced/multi_gpu.html#shard-model-instantly-to-reduce-initialization-time-memory

@SeanNaren which torch and pytorch-lightning version should I use?

Dear @dalek-who,
You should you PyTorch 1.3.0rc1 and latest PyTorch.
Best,
T.C


Add a model for multinomial logistic regression

Here are some suggested changes:

Rename the output_type parameter to prediction_method with the following options, that mostly match the sklearn predictor method names:

predict
predict_proba
decision_function
predict_onehot (return a 0-1 vector)

Change the get_error method to always work on the probabilities.  For 0/1 return values, the error would also just be 0 or 1 which is not very informative

Rename the output_type parameter to prediction_method with the following options, that mostly match the sklearn predictor method names:

predict
predict_proba
decision_function
predict_onehot (return a 0-1 vector)

Change the get_error method to always work on the probabilities.  For 0/1 return values, the error would also just be 0 or 1 which is not very informative

This is more involved than I thought.
Doing it for the logistic regression is easy but it has to also work for the pipeline.

@bzfwunde I removed this predict_class parameter as we had discussed and reworked the Janos example.
It has to do some compromises for the example but it's the best I could think off.


Add ISL/OSL CLI arg aliases

Input sequence length (ISL) and output sequence length (OSL) are becoming very common paths for users, so add them as aliases to shorten the args --synthetic-input-tokens-mean and --output-tokens-mean.
We plan to simplify the CLI args when GenAI-Perf goes GA. We may also switch to config files. For now, this will aid usability for users who prefer using these aliases.

LGTM


ollama list flags help

There is no obvious way of seeing what flags are available for ollama list
ollama list --help
List models

Usage:
  ollama list [flags]

Aliases:
  list, ls

Flags:
  -h, --help   help for list

There's actually only the -h flag for ollama list right now. Was there anything in particular that you were looking for?

Yes there are several things that could be improved upon. Currently ollama list will display
Name,ID,Size and modified in the current format with no variation.  This is problematic.

Name is case sensitive alphabetical using -I or --ignorecase for ignore case would make it case insensitive alphabetical
currently the size of the model is in human readable format which uses things like  637 MB, 4.1 GB. If I want to send it through a sort program that is a problem.  I propose using the -s or --size  of bytes, otherwise the default is human readable.
The modified column has things like 6 days ago, or 8 weeks ago which is good for humans, but not so good for other things.  I propose -t or --time in the HH:MM:SS format and -ts or --seconds in the total number of seconds format
There is no default sorting method.  I propose -o or --order followed by the column number or negative column number for reverse sorting.
Lastly -h or --help to show the command options.

In Linux at least command output is usually in bytes and -h is used for "human readable" or MB/GB type output.
I also would like to see a sort/order option to be able to sort by the various list columns.
Another useful option would be a flag to change the output format.  While the table is a good default, it might be helpful to offer other options like JSON, CSV, etc...

came across this as i wanted to list my models by name not  by modified date.
Feels like name, size, modified ascending and descending would be the full set?

Came here to post that we need to be able to sort based on name.  (I also think modified and size too) in both ascending and descending order.
I'd also like to see a shortcut for list (and other commands) be also added -
ollama l

Seems intuitive imo.

@haydonryan you can use ollama list | sort to sort by name.


Force regenerate

Now, ffjson can decide if the input file is newer than the output file, or not. If the input file is newer then ffjson works in the usual way. Otherwise, it skips the process, but users can use the force-regenerate option, which always regenerates the _ffjson file.

awesome, thank you

you're welcome, but the last test failed. I'm looking for the error, but I'm not sure, what the reason of failure is. can you help me with this?

@kipal It looks like they only failed on Golang tip, not 1.5.  Not sure whats up with it.


[Suggestion] option to limit the channel identifier item thing to items without NBT?

I hope this isn't asking too much; I'm only asking because while giving factions on a server the option to store their items is wonderful, it's very easy to create lots of storage channels if you have the resources (and by simply renaming a piece of paper).
But if you limit it down to unenchanted/unnamed items it creates a risk factor of someone discovering your channel and I think that would be pretty cool :)

This will be done, because I need to provide mod users with a way to limit the number of active channels anyway

After The Flattening it became feasible to treat channels as exclusively the item ID of whatever you put in the channel slot. For example minecraft:diamond or minecraft:red_wool. This could be a config setting.

@LoganDark, could you elaborate, please?

@LoganDark, could you elaborate, please?

Before The Flattening (1.13), many items used damage values to mean completely different items, like the golden apple & enchanted golden apple, or all colors of wool having the same ID with a different damage value. But now everything has its own ID, i.e. golden_apple vs enchanted_golden_apple, red_wool vs blue_wool, dirt vs podzol and so on.
Therefore the item ID on its own has become unique enough (as of >=1.13) to be usable as a channel on its own, without having to take into account item damage or NBT (including name or enchantments).
Obviously the ability to make such a unique item that it can't be copied is a very cool idea (i.e. you store all your key items in your ender chest and you're the only one with those items). I don't want that functionality to disappear. I was simply offering an idea for how you could implement a resolution to this issue.
That way, the nether chest wouldn't reject items without NBT, it would just act as if there was no NBT at all.
One unresolved concern is how existing storages will be accessed if items with NBT were used to store them before the setting was enabled.

Oh, yeah, gotcha. I meant to implement the thingy this exact way


[Tests-Only] Run litmus CI for both owncloud and ocis storage

@butonic this PR runs litmus tests on both owncloud and ocis storage. owncloud passes (like it already did). ocis storage fails:
old webdav:
https://cloud.drone.io/cs3org/reva/2525/3/5
...
10. move_coll.............
10. move_coll............. FAIL (collection COPY `/remote.php/webdav/litmus/mvdest/' to `/remote.php/webdav/litmus/mvdest2/', depth infinity: 500 Internal Server Error)

11. move_cleanup..........
11. move_cleanup.......... pass

12. finish................
12. finish................ pass
<- summary for `copymove': of 13 tests run: 12 passed, 1 failed. 92.3%

new webdav:
https://cloud.drone.io/cs3org/reva/2525/5/5
...
10. move_coll.............
10. move_coll............. FAIL (collection COPY `/remote.php/dav/files/4c510ada-c86b-4815-8820-42cdf82c3d51/litmus/mvdest/' to `/remote.php/dav/files/4c510ada-c86b-4815-8820-42cdf82c3d51/litmus/mvdest2/', depth infinity: 500 Internal Server Error)

11. move_cleanup..........
11. move_cleanup.......... pass

12. finish................
12. finish................ pass
<- summary for `copymove': of 13 tests run: 12 passed, 1 failed. 92.3%

Is there a known issue with copying/moving a collection/folder?

I cherry-picked from PR #1177 into here - to demonstrate that litmus now passes for ocis storage.

Now litmus fails in a different way: https://cloud.drone.io/cs3org/reva/2566/3/5
13. propreplace...........
13. propreplace........... FAIL (PROPPATCH on `/remote.php/webdav/litmus/prop2': 500 Internal Server Error)

14. propget...............
14. propget............... FAIL (Property {http://example.com/neon/litmus/}prop9 had value value9, expected newvalue9)

15. propnullns............
15. propnullns............ pass

16. propget...............
16. propget............... pass

17. propremoveset.........
17. propremoveset......... FAIL (PROPPATCH remove then set)

18. propget...............
18. propget............... FAIL (No value given for property {http://example.com/neon/litmus/}removeset)

This is after PR #1177 "fix ocis move" was merged.

PR #1179 fixed the fails. I rebased, so this should pass now.

@ishank011 CI  should pass here now - please review.