text:
default: stdin: is not a tty

Output of cgywin:
Suriyaa@Suriyaa ~
$ git clone https://github.com/SuriyaaKudoIsc/suriyaaos.git
Cloning into 'suriyaaos'...

Suriyaa@Suriyaa ~
$ cd suriyaaos

Suriyaa@Suriyaa ~/suriyaaos
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'lucid32'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: suriyaaos_default_1469191963305_9937
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version o                                                                                f
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you                                                                                see
    default: shared folder errors, please make sure the guest additions within t                                                                                he
    default: virtual machine match the version of VirtualBox you have installed                                                                                on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 4.2.0
    default: VirtualBox Version: 4.3
==> default: Mounting shared folders...
    default: /vagrant => C:/Users/Suriyaa/suriyaaos
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty

Error is here:
==> default: stdin: is not a tty

Possible answer at https://github.com/mitchellh/vagrant/issues/1673#issuecomment-17237843.

Read http://stackoverflow.com/questions/24421541/vagrant-up-fails-with-stdin-start-ssh-stderr-stdout-errors.

It works! No default: stdin: is not a tty issue!
Output:
Suriyaa@Suriyaa ~/Downloads
$ git clone -b SuriyaaKudoIsc-default-stdin-tty --single-branch https://github.com/SuriyaaKudoIsc/suriyaaos.git
Cloning into 'suriyaaos'...

Suriyaa@Suriyaa ~/Downloads
$ cd suriyaaos

Suriyaa@Suriyaa ~/Downloads/suriyaaos
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'lucid32'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: suriyaaos_default_1469193217778_79585
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 4.2.0
    default: VirtualBox Version: 4.3
==> default: Mounting shared folders...
    default: /vagrant => C:/Users/Suriyaa/Downloads/suriyaaos
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: Ign http://security.ubuntu.com lucid-security Release.gpg
==> default: Ign http://security.ubuntu.com/ubuntu/ lucid-security/main Translation-en_US
==> default: Ign http://security.ubuntu.com/ubuntu/ lucid-security/restricted Translation-en_US
==> default: Ign http://security.ubuntu.com/ubuntu/ lucid-security/universe Translation-en_US
==> default: Ign http://security.ubuntu.com/ubuntu/ lucid-security/multiverse Translation-en_US
==> default: Ign http://security.ubuntu.com lucid-security Release
==> default: Ign http://us.archive.ubuntu.com lucid Release.gpg
==> default: Ign http://us.archive.ubuntu.com/ubuntu/ lucid/main Translation-en_US
==> default: Ign http://us.archive.ubuntu.com/ubuntu/ lucid/restricted Translation-en_US
==> default: Ign http://us.archive.ubuntu.com/ubuntu/ lucid/universe Translation-en_US
==> default: Ign http://us.archive.ubuntu.com/ubuntu/ lucid/multiverse Translation-en_US
==> default: Ign http://us.archive.ubuntu.com lucid-updates Release.gpg
==> default: Ign http://security.ubuntu.com lucid-security/main Packages
==> default: Ign http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Translation-en_US
==> default: Ign http://us.archive.ubuntu.com/ubuntu/ lucid-updates/restricted Translation-en_US
==> default: Ign http://us.archive.ubuntu.com/ubuntu/ lucid-updates/universe Translation-en_US
==> default: Ign http://us.archive.ubuntu.com/ubuntu/ lucid-updates/multiverse Translation-en_US
==> default: Ign http://security.ubuntu.com lucid-security/restricted Packages
==> default: Ign http://security.ubuntu.com lucid-security/main Sources
==> default: Ign http://security.ubuntu.com lucid-security/restricted Sources
==> default: Ign http://security.ubuntu.com lucid-security/universe Packages
==> default: Ign http://security.ubuntu.com lucid-security/universe Sources
==> default: Ign http://us.archive.ubuntu.com lucid Release
==> default: Ign http://us.archive.ubuntu.com lucid-updates Release
==> default: Ign http://security.ubuntu.com lucid-security/multiverse Packages
==> default: Ign http://security.ubuntu.com lucid-security/multiverse Sources
==> default: Ign http://security.ubuntu.com lucid-security/main Packages
==> default: Ign http://us.archive.ubuntu.com lucid/main Packages
==> default: Ign http://us.archive.ubuntu.com lucid/restricted Packages
==> default: Ign http://us.archive.ubuntu.com lucid/main Sources
==> default: Ign http://us.archive.ubuntu.com lucid/restricted Sources
==> default: Ign http://us.archive.ubuntu.com lucid/universe Packages
==> default: Ign http://us.archive.ubuntu.com lucid/universe Sources
==> default: Ign http://security.ubuntu.com lucid-security/restricted Packages
==> default: Ign http://security.ubuntu.com lucid-security/main Sources
==> default: Ign http://security.ubuntu.com lucid-security/restricted Sources
==> default: Ign http://security.ubuntu.com lucid-security/universe Packages
==> default: Ign http://security.ubuntu.com lucid-security/universe Sources
==> default: Ign http://security.ubuntu.com lucid-security/multiverse Packages
==> default: Ign http://security.ubuntu.com lucid-security/multiverse Sources
==> default: Ign http://us.archive.ubuntu.com lucid/multiverse Packages
==> default: Ign http://us.archive.ubuntu.com lucid/multiverse Sources
==> default: Ign http://us.archive.ubuntu.com lucid-updates/main Packages
==> default: Ign http://us.archive.ubuntu.com lucid-updates/restricted Packages
==> default: Ign http://us.archive.ubuntu.com lucid-updates/main Sources
==> default: Ign http://us.archive.ubuntu.com lucid-updates/restricted Sources
==> default: Ign http://us.archive.ubuntu.com lucid-updates/universe Packages
==> default: Err http://security.ubuntu.com lucid-security/main Packages
==> default:   404  Not Found [IP: 91.189.88.161 80]
==> default: Err http://security.ubuntu.com lucid-security/restricted Packages
==> default:   404  Not Found [IP: 91.189.88.161 80]
==> default: Err http://security.ubuntu.com lucid-security/main Sources
==> default:   404  Not Found [IP: 91.189.88.161 80]
==> default: Err http://security.ubuntu.com lucid-security/restricted Sources
==> default:   404  Not Found [IP: 91.189.88.161 80]
==> default: Err http://security.ubuntu.com lucid-security/universe Packages
==> default:   404  Not Found [IP: 91.189.88.161 80]
==> default: Err http://security.ubuntu.com lucid-security/universe Sources
==> default:   404  Not Found [IP: 91.189.88.161 80]
==> default: Err http://security.ubuntu.com lucid-security/multiverse Packages
==> default:   404  Not Found [IP: 91.189.88.161 80]
==> default: Err http://security.ubuntu.com lucid-security/multiverse Sources
==> default:   404  Not Found [IP: 91.189.88.161 80]
==> default: Ign http://us.archive.ubuntu.com lucid-updates/universe Sources
==> default: Ign http://us.archive.ubuntu.com lucid-updates/multiverse Packages
==> default: Ign http://us.archive.ubuntu.com lucid-updates/multiverse Sources
==> default: Ign http://us.archive.ubuntu.com lucid/main Packages
==> default: Ign http://us.archive.ubuntu.com lucid/restricted Packages
==> default: Ign http://us.archive.ubuntu.com lucid/main Sources
==> default: Ign http://us.archive.ubuntu.com lucid/restricted Sources
==> default: Ign http://us.archive.ubuntu.com lucid/universe Packages
==> default: Ign http://us.archive.ubuntu.com lucid/universe Sources
==> default: Ign http://us.archive.ubuntu.com lucid/multiverse Packages
==> default: Ign http://us.archive.ubuntu.com lucid/multiverse Sources
==> default: Ign http://us.archive.ubuntu.com lucid-updates/main Packages
==> default: Ign http://us.archive.ubuntu.com lucid-updates/restricted Packages
==> default: Ign http://us.archive.ubuntu.com lucid-updates/main Sources
==> default: Ign http://us.archive.ubuntu.com lucid-updates/restricted Sources
==> default: Ign http://us.archive.ubuntu.com lucid-updates/universe Packages
==> default: Ign http://us.archive.ubuntu.com lucid-updates/universe Sources
==> default: Ign http://us.archive.ubuntu.com lucid-updates/multiverse Packages
==> default: Ign http://us.archive.ubuntu.com lucid-updates/multiverse Sources
==> default: Err http://us.archive.ubuntu.com lucid/main Packages
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid/restricted Packages
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid/main Sources
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid/restricted Sources
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid/universe Packages
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid/universe Sources
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid/multiverse Packages
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid/multiverse Sources
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid-updates/main Packages
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid-updates/restricted Packages
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid-updates/main Sources
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid-updates/restricted Sources
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid-updates/universe Packages
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid-updates/universe Sources
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid-updates/multiverse Packages
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: Err http://us.archive.ubuntu.com lucid-updates/multiverse Sources
==> default:   404  Not Found [IP: 91.189.91.23 80]
==> default: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/lucid-security/main/binary-i386/Packages.gz  404  Not Found [IP: 91.189.88.161 80]
==> default:
==> default: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/lucid-security/restricted/binary-i386/Packages.gz  404  Not Found [IP: 91.189.88.161 80]
==> default:
==> default: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/lucid-security/main/source/Sources.gz  404  Not Found [IP: 91.189.88.161 80]
==> default:
==> default: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/lucid-security/restricted/source/Sources.gz  404  Not Found [IP: 91.189.88.161 80]
==> default:
==> default: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/lucid-security/universe/binary-i386/Packages.gz  404  Not Found [IP: 91.189.88.161 80]
==> default:
==> default: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/lucid-security/universe/source/Sources.gz  404  Not Found [IP: 91.189.88.161 80]
==> default:
==> default: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/lucid-security/multiverse/binary-i386/Packages.gz  404  Not Found [IP: 91.189.88.161 80]
==> default:
==> default: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/lucid-security/multiverse/source/Sources.gz  404  Not Found [IP: 91.189.88.161 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid/main/binary-i386/Packages.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid/restricted/binary-i386/Packages.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid/main/source/Sources.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid/restricted/source/Sources.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid/universe/binary-i386/Packages.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid/universe/source/Sources.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid/multiverse/binary-i386/Packages.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid/multiverse/source/Sources.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid-updates/main/binary-i386/Packages.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid-updates/restricted/binary-i386/Packages.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid-updates/main/source/Sources.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid-updates/restricted/source/Sources.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid-updates/universe/binary-i386/Packages.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid-updates/universe/source/Sources.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid-updates/multiverse/binary-i386/Packages.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/lucid-updates/multiverse/source/Sources.gz  404  Not Found [IP: 91.189.91.23 80]
==> default:
==> default: E: Some index files failed to download, they have been ignored, or old ones used instead.
==> default: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: The following extra packages will be installed:
==> default:   bridge-utils cpu-checker dpkg-dev fakeroot g++ g++-4.4 libaio1 libasound2
==> default:   libdirectfb-1.2-0 libflac8 libice6 liblzma1 libogg0 libpulse0 libpython2.6
==> default:   libsdl1.2debian libsdl1.2debian-alsa libsm6 libsndfile1 libstdc++6-4.4-dev
==> default:   libsysfs2 libts-0.0-0 libvorbis0a libvorbisenc2 libxi6 libxtst6 patch
==> default:   qemu-common qemu-kvm seabios tsconf unzip vgabios x11-common xz-utils
==> default: Suggested packages:
==> default:   debian-keyring debian-maintainers g++-multilib g++-4.4-multilib gcc-4.4-doc
==> default:   libstdc++6-4.4-dbg grub-legacy-doc mdadm libasound2-plugins pulseaudio
==> default:   libstdc++6-4.4-doc make-doc diffutils-doc mol-drivers-macosx openbios-sparc
==> default:   kvm-pxe ubuntu-vm-builder uml-utilities
==> default: The following packages will be REMOVED:
==> default:   grub-pc
==> default: The following NEW packages will be installed:
==> default:   bridge-utils build-essential cpu-checker dpkg-dev fakeroot g++ g++-4.4 grub
==> default:   libaio1 libasound2 libdirectfb-1.2-0 libflac8 libice6 liblzma1 libogg0
==> default:   libpulse0 libpython2.6 libsdl1.2debian libsdl1.2debian-alsa libsm6
==> default:   libsndfile1 libstdc++6-4.4-dev libsysfs2 libts-0.0-0 libvorbis0a
==> default:   libvorbisenc2 libxi6 libxtst6 make nasm patch qemu qemu-common qemu-kvm
==> default:   seabios tsconf unzip vgabios x11-common xz-utils zip
==> default: 0 upgraded, 41 newly installed, 1 to remove and 36 not upgraded.
==> default: Need to get 16.7MB of archives.
==> default: After this operation, 48.4MB of additional disk space will be used.
==> default: WARNING: The following packages cannot be authenticated!
==> default:   x11-common make bridge-utils libstdc++6-4.4-dev g++-4.4 g++ liblzma1
==> default:   xz-utils patch dpkg-dev build-essential cpu-checker fakeroot grub libaio1
==> default:   libpython2.6 libasound2 libsysfs2 tsconf libts-0.0-0 libdirectfb-1.2-0
==> default:   libogg0 libflac8 libice6 libsm6 libvorbis0a libvorbisenc2 libsndfile1 libxi6
==> default:   libxtst6 libpulse0 libsdl1.2debian-alsa libsdl1.2debian nasm seabios vgabios
==> default:   qemu-common qemu-kvm qemu unzip zip
==> default: E:
==> default: There are problems and -y was used without --force-yes
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Suriyaa@Suriyaa ~/Downloads/suriyaaos
$

See #6 for the default: There are problems and -y was used without --force-yes issue.

repo: SuriyaaKudoIsc/suriyaaos


text:
Add version information + Split off MPV control from youtube player so we can use MPV more

(untested right now)

ow nice :+1:

source: gharchive/pull-request

authors: SvenWiltink vansante

repo: SvenWiltink/go-MusicBot

license: mit

license_type: permissive

license_source: bigquery


text:
CamoAnimMaker errors in SDK3 for worlds

The script references components specific to the "Avatars" version of SDK3, meaning in SDK2 & SDK3 for Worlds the toolset will spew tons of errors into the console and not allow building the project until the file is manually deleted.

The tool is to be removed in Version 2.4 packages and moving forward, but will remain available in github itself. As it was only experimental, for a very specific use case, and more often than not caused unwanted errors.

source: gharchive/issue

license: MIT

license_source: github-api


text:
Readme

A visually appealing README is crucial because it serves as the first impression of the project. It enhances user engagement, making it easier for newcomers to understand the project's purpose and functionalities. By incorporating visual elements like GIFs and diagrams, we can simplify complex concepts, provide clear instructions, and ultimately encourage more users to explore and contribute to the project.
Hi,
I hope this message finds you well. I’m eager to contribute to the project and would love to take on the task of enhancing the README. I have already successfully completed one README task, where I made it more interactive and visually appealing by adding GIFs to demonstrate key features.
Please let me know if you can assign this task to me. I’m looking forward to your feedback and am excited to contribute further!
Thank you!
Best regards,
Eshal :)

already done


text:
🛑 swift-ast-explorer.com is down

In f02838a, swift-ast-explorer.com (https://swift-ast-explorer.com) was down:

HTTP code: 503
Response time: 673 ms

Resolved: swift-ast-explorer.com is back up in 74257fb after 27 minutes.


text:
🛑 swiftfiddle.com is down

In 22bed00, swiftfiddle.com (https://swiftfiddle.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: swiftfiddle.com is back up in ba6bda8 after 4 hours, 23 minutes.


text:
Assets Catalogs 与 I/O 优化

推荐收录
链接
https://juejin.im/post/5cb74d786fb9a068773948fc

刚刚想自荐文章，看到已经有同学帮忙推荐了，感谢。
另外谈一下与这篇文章相似的问题，的确是很碰巧大家共同关注到这个问题，我这篇文章起因也是项目中采用了在 Folder 中存放图片导致加载缓慢的问题，在那篇文章里是QQ阅读，这我这里是WiFi管家和手机管家，那么这个问题应该是鹅厂一些旧项目不愿尝试新功能的通病了。说回文章，那篇文章和我一样同样有参考Reverse engineering the .car file format (compiled Asset Catalogs)这篇文章，但是它的涉及广度比我的大，还从BOM文件与内存映射方面去分析，而我的文章则是更多从 CoreUI 框架的源码实现上去分析，理解整个加载流程的区别，所以如果真的想深入了解 Assets Catalogs 与 I/O 优化的东西，应该两篇文章结合着去看，产生自己的思考会比较好

repo: SwiftOldDriver/iOS-Weekly


text:
技术面试最后反问面试官的话

推荐收录
链接
https://github.com/yifeikong/reverse-interview-zh

面试就像相亲，你需要用心准备一些问题，好足够了解对方，才能找到适合自己的对象。本文列了一些提问，帮助你更好的了解招聘方。

authors: ParsifalC raozhizhen


text:
Disable drag direction

Helpful lib, thank you!
I would like to disable left-to-right dragging as the app uses this for navigation, photo-browser style - the table using the swipe cells is on the rightmost set, so we can have right-to-left dragging for cell actions, while preserving left-to-right to navigate.
Reading docs: I do not see this feature available. Is it supported?
If not, can I send a PR?

Looking at the code (pan gesture recognizer), it appears this would not be easily achievable.

repo: SwipeCellKit/SwipeCellKit


text:
🛑 CEPI Gateway is down

In a210c12, CEPI Gateway (http://api-cau-prod.switch.com.uy/api/health/liveness) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEPI Gateway is back up in ae28b07.

repo: Switch-Software-Solutions/status-page


text:
Added Profile.vue. Get User and Delete User must be implemented in th…

…e backend.

Great job!

repo: SycSin/MyRecipes


text:
default docker image is for arm64 only

 ✔ Container web-app
                                        Created0.8s
 ! iris The requested image's platform (linux/arm64/v8) does not match the detected host platform (linux/amd64/v2)
 and no specific platform was requested 0.0s
Attaching to web-app
web-app  | [INFO] Executing command /home/irisowner/irissys/startISCAgent.sh 2188...
web-app  | [INFO] Writing status to file: /home/irisowner/irissys/iscagent.status
web-app  | Reading configuration from file: /home/irisowner/irissys/iscagent.conf
web-app  | ISCAgent[40]: Starting

i added a dedicated dockerfile for AMD64  for Window, Linux,
part of ma PullRequest

done

repo: SylvainGuilbaud/todo-list


text:
Remove Collection selection from Submit page

This part is confusing, so lets go ahead and remove it.  Will also allow submit to open faster since can be long list sometimes.

I have removed it.  Should the "options" drop-down menu still be there?  Should submit to existing collections have the drop down menu?

Yes but option depend on whether submitting to old or new collection. See submit page on sbh.
Chris
Sent from my iPhone

On Sep 18, 2017, at 11:40 PM, Michael Zhang notifications@github.com wrote:
I have removed it. Should the "options" drop-down menu still be there? Should submit to existing collections have the drop down menu?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

You don’t need the dropdown, but you need an option to select “Overwrite Existing Objects”.  If not selected, then the overwrite_merge parameter to submit should be “0”, and if it is selected, it should be “1”.

On Sep 18, 2017, at 11:40 PM, Michael Zhang notifications@github.com wrote:
I have removed it. Should the "options" drop-down menu still be there? Should submit to existing collections have the drop down menu?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/SynBioDex/SBOLDesigner/issues/174#issuecomment-330435079, or mute the thread https://github.com/notifications/unsubscribe-auth/ADWD9-lohHK1Q4h8pOKjpKeDCW4Xn9usks5sj1PVgaJpZM4PPEGE.

Done.

repo: SynBioDex/SBOLDesigner


text:
Crowd AI Plant Disease Prediction

Hi @TAHIR0110  ,
I hope you're doing well. I've addressed the issue #211  and created a pull request to resolve it.
Could you please review the PR and let me know if any adjustments are needed?
Best regards,
Tanisha Garg

@TAHIR0110 Please check the level labels again before merging and assign it according to my PR work.

@TAHIR0110 Please merge

@Atharv714 @TAHIR0110 Please assign me this and update the level because you have merged it without assigning and giving the level labels due to which it is not showing in my leaderboard.

@Atharv714 @TAHIR0110 Assign me this so that I can get points in my leaderboard.


text:
Added pulmonary infection detection model

Fixes Issue #203
Added Pulmonary infection detection model

Please level the PR @Atharv714  :)
The issue was level2


text:
[Bug] memory crash

mage run or docker-compose up --build
mac 13.3.1  M2 chip
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x39 pc=0x100ce5690]
goroutine 87 [running]:
github.com/docker/buildx/builder.(*Builder).Validate(0x101ee58a0?)
github.com/docker/buildx@v0.10.4/builder/builder.go:111 +0x20
github.com/docker/buildx/builder.New({0x101ee58a0?, 0x14000170500}, {0x0, 0x0, 0x140003d0ab0?})
github.com/docker/buildx@v0.10.4/builder/builder.go:101 +0x290
github.com/docker/compose/v2/pkg/compose.(*composeService).doBuildBuildkit(0x140002ec840, {0x101ed4d80, 0x14000660190}, 0x0?, {0x1016872b3, 0x4})
github.com/docker/compose/v2/pkg/compose/build_buildkit.go:36 +0x68
github.com/docker/compose/v2/pkg/compose.(*composeService).build.func1({0x101ed4d80, 0x14000660190}, {0x14000427390, 0x3})
github.com/docker/compose/v2/pkg/compose/build.go:112 +0x5b4
github.com/docker/compose/v2/pkg/compose.(*graphTraversal).run.func1()
github.com/docker/compose/v2/pkg/compose/dependencies.go:127 +0x5c

I believe this may be specific to the M2 chip, since I've run the same command on my M1 with no issue.
Are you using Docker Desktop? https://tutorials.tinkink.net/en/mac/how-to-use-docker-on-m1-mac.html

yes docker desktop

also whats the recommended server to use? AWS
Amazon 2
Ubuntu
?

gui docker no longer exists either in compose yaml
gui:
build:
context: ../
dockerfile: build/Dockerfile-gui

@jdutchak you might need to try docker-compose stop &&docker-compose up --build --remove-orphans again since the error seems related to docker-compose itself
the GUI is being removed here - https://github.com/TBD54566975/ssi-service/pull/450
as for where to run - we're planning on supporting all major clouds. have tested on AWS internally

are the swagger docs being removed too?

more accurately I should say the streamlit gui is deprecated in favor of https://github.com/TBD54566975/ssi-admin-ui
we have yet to integrate that into our docker-compose here https://github.com/TBD54566975/ssi-service/issues/454
swagger was moved to be served from the service itself, so need for a special binary. docs could be better perhaps. you can view it as of https://github.com/TBD54566975/ssi-service/commit/817610d1ff91ea1061b7328c752df273a91e757e by sending a request to /swagger

authors: decentralgabe jdutchak


text:
replace standard editor with lvlibp

load time is horrible, lvlibp is easy to try and might help

doesn't seem to help, lv spends as much time recompiling links in the ppl as it does loading the classes normally

repo: TBDFramework/TagEditorCore


text:
feat(component): add indexes components

新增indexes组件。用于页面中信息快速检索，可以根据目录中的页码快速找到所需的内容。

🤔 这个 PR 的性质是？

[ ] 日常 bug 修复
[x] 新特性提交
[ ] 文档改进
[ ] 演示代码改进
[ ] 组件样式/交互改进
[ ] CI/CD 改进
[ ] 重构
[ ] 代码风格优化
[ ] 测试用例
[ ] 分支合并
[ ] 其他

🔗 相关 Issue

💡 需求背景和解决方案

📝 更新日志

fix(组件名称): 处理问题或特性描述 ...

[ ] 本条 PR 不需要纳入 Changelog

☑ 请求合并前的自查清单
⚠ 请自检并全部勾选全部选项。⚠

[x] 文档已补充或无须补充
[x] 代码演示已提供或无须提供
[x] TypeScript 定义已补充或无须补充
[ ] Changelog 已提供或无须提供

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@e739689). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             main    #106   +/-   ##
======================================
  Coverage        ?   6.70%
======================================
  Files           ?     286
  Lines           ?    3191
  Branches        ?     818
======================================
  Hits            ?     214
  Misses          ?    2977
  Partials        ?       0

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 e739689...ce7e341. Read the comment docs.

authors: codecov-commenter shiyanZhang

repo: TDesignOteam/tdesign-mobile-react


text:
Can't connect as a second user

When I connect using my own account, everything works fine, but when I try in my tablet with my "Tablet" account/person, the HA-SIP fails as below:

I tried to remove all extensions except tablet but the issue remains. Very weird. If you want to debug on my side, I can show on Discord.

It can't match the logged in user with any user in extensions. Are you sure you're logged in as tablet, and the person entity is correct?

Yes, I'm sure!

This is the code where it defines the logged in user. Could be useful.
${this.config.extensions.map(extension => {
    var stateObj = this.hass.states[extension.entity];
    var isMe = (this.hass.user.id == this.hass.states[extension.person].attributes.user_id);
    if (isMe) { this.user = extension; }

Maybe a refresh? Because it's a new entity.

I tried everything already, lol. Also, I wish I knew how to debug this to check which value is inside of these fields...

Ok now I think I found how to debug. One sec.

Debugging cards is indeed hard. I log the values and rebuild.

user_id for the person Tablet is undefined. But when it iterates as my user, it's set.

Wow, just found the issue:

I think. Checking...

Yes, worked. I don't know how the hell this happened, but whatever... Thank you for the tip on debugging!

Nice, never found that problem. I will add it in the wiki.

Wait, how did you use the Tablet user if it isn't allowed to log in?

Exactly! That's what I don't understand. But my gut feeling is that I had an user called tablet (that's how I logged in) and then a person called tablet, but they were not linked.

I was thinking that too. Same name, different ID.


text:
Support for handling IBM float trace headers

Added a check for fields that are of type Ibm32 in the HeaderIndexer. Included another case in test for test_transforms.py.

@ta-hill this looks good. Can we add one more test for SegyFile with a mock SegyFile with a ibm header to ensure the transform integrates properly with SegyFile?

actually never mind, I'll merge this. I am wanting to refactor the tests anyways. thanks!

authors: ta-hill tasansal

repo: TGSAI/segy


text:
我跟您提过了一个issue，但是为什么不见了？有谁可以解释一下嘛？

System Info / 系統信息
我跟您提过了一个issue，但是为什么不见了？有谁可以解释一下嘛？
Who can help? / 谁可以帮助到您？
我跟您提过了一个issue，但是为什么不见了？有谁可以解释一下嘛？
Information / 问题信息

[ ] The official example scripts / 官方的示例脚本
[X] My own modified scripts / 我自己修改的脚本和任务

Reproduction / 复现过程
none
Expected behavior / 期待表现
是目前功能不支持还是误删？还是说我之前提问的bug与本库不相关？

#460 issue属于 #394中提到的讨论区问题，官方没有办法复现或者进行维护，至于其他最近issue，我们没有看到

#460 issue属于 #394中提到的讨论区问题，官方没有办法复现或者进行维护，至于其他最近issue，我们没有看到

好的谢谢您


text:
cogvlm模型微调报错（使用Captcha Images数据集）

System Info / 系統信息
系统：
centos8,
cuda:12.1
GPU:A6000*4
Who can help? / 谁可以帮助到您？
No response
Information / 问题信息

[ ] The official example scripts / 官方的示例脚本
[ ] My own modified scripts / 我自己修改的脚本和任务

Reproduction / 复现过程
在完成环境配置后，模型加载完成之后，报错信息如下：
File "/root/anaconda3/lib/python3.11/site-packages/torch/distributed/distributed_c10d.py",line 3439,in barrier
work=default_pg.barrier(opts=opts)
torch.distributed.DistBackendError:NCCL error in :../torch/csrc/distributed/c10d/ProcessGroupNCCL.cpp:1691,unhandled system error (run with NCLL_DEBUG=INFO for details),NCCL version 2.19.3
ncclSystemError:System call (e.g. socket,malloc) or external library call failed or device error.
Last error:
Error while creating shared memory segment /dev/shm/nccl-ENPWQG (size 4194656)
其中，我的shell脚本i信息为：
#! /bin/bash
export PATH=/usr/local/cuda/bin:$PATH
export LD_LIBRARY_PATH=/usr/local/cuda/lib64:$LD_LIBRARY_PATH
NUM_GPUS_PER_WORKER=4
MP_SIZE=1
script_path=$(realpath $0)
script_dir=$(dirname $script_path)
main_dir=$(dirname $script_dir)
MODEL_TYPE="/root/CogVLM/cogvlm-chat-v1.1"
VERSION="base"
MODEL_ARGS="--from_pretrained $MODEL_TYPE
--max_length 1288
--lora_rank 10
--use_lora
--local_tokenizer /root/CogVLM/vicuna-7b-v1.5
--version $VERSION"
Tips: If training models of resolution 244, you can set --max_length smaller
OPTIONS_SAT="SAT_HOME=~/.sat_models"
OPTIONS_NCCL="NCCL_DEBUG=info NCCL_IB_DISABLE=0 NCCL_NET_GDR_LEVEL=2 LOCAL_WORLD_SIZE=$NUM_GPUS_PER_WORKER"
HOST_FILE_PATH="hostfile"
train_data="./archive_split/train"
valid_data="./archive_split/valid"
gpt_options="
--experiment-name finetune-$MODEL_TYPE
--model-parallel-size ${MP_SIZE}
--mode finetune
--train-iters 800
--resume-dataloader
$MODEL_ARGS
--train-data ${train_data}
--valid-data ${valid_data}
--distributed-backend nccl
--lr-decay-style cosine
--warmup .02
--checkpoint-activations
--vit_checkpoint_activations
--save-interval 200
--eval-interval 200
--save "./checkpoints"
--eval-iters 10
--eval-batch-size 1
--split 1.
--deepspeed_config test_config_bf16.json
--skip-init
--seed 2023
"
run_cmd="${OPTIONS_NCCL} ${OPTIONS_SAT} deepspeed --master_port 16666 --hostfile ${HOST_FILE_PATH} finetune_cogvlm_demo.py ${gpt_options}"
echo ${run_cmd}
eval ${run_cmd}
set +x
请问我该如何解决这个问题呢
Expected behavior / 期待表现
因为是在不联网环境里进行配置的，所以不知道是否是相关依赖有所问题

NCCL error
run with NCLL_DEBUG=INFO for details
Error while creating shared memory segment /dev/shm
我认为是NCCL配置的的问题，采用NCLL_DEBUG=INFO查看具体原因，
shared memory的问题？查看英伟达官网NCCL环境变量配置
https://docs.nvidia.com/deeplearning/nccl/user-guide/docs/env.html

经过对docker容器的共享内存的重分配，上述问题已经解决。但是在运行finetune_cogvlm_lora.sh脚本时，会频繁打印一句提示:Keyword arguments {'add_special_tokens':False} not recognized
我并未在代码里面找到相关的代码，请问这个错误是模型选择的问题吗？（我目前使用的模型是sat版本的cogvlm-chat-v1.1）

repo: THUDM/CogVLM


text:
how is the score related with alignment?

From the paper, this metric seems a general purpose score measuring human preference. If I am only interested in image text alignment, it this metric suitable?

DPOK: Reinforcement Learning for Fine-tuning Text-to-Image Diffusion Models (https://arxiv.org/pdf/2305.16381.pdf), this paper has explored it. In Appendix C (Investigation on ImageReward), the result is as follows.

thanks

repo: THUDM/ImageReward


text:
Dismatch batch size between query_layer and key_layer

When flash_attn_func is called, I see query_layer have different batch size with key_layer and value_layer. Since cat layer operation pads key_layer and value_layer with extra one row/colum, then after view operation, key_layer and value_layer should have larger batch size than query_layer. Is this intended and flash_attn_func support this kind of usage, or is it a bug?
@yzy-thu cc.

Sorry, I have some misunderstanding for the code, I'll close it since I have understood it.

repo: THUDM/Inf-DiT


text:
[PDP-2827] update latest changes for recipe and scripts

changes

fix the typo
update the recipe

So the changes are

for certificates
We remove the need for using AWS ACM to manually create certificate before deploy CP. We always create certificate using cert-manager.

for Azure storage
We remove the need to manually create storage account before deploy CP.

for ingress
We add kong support and secondary domain

repo: TIBCOSoftware/platform-provisioner


text:
🛑 TKS US Corporate Website is down

In d296159, TKS US Corporate Website (https://www.tkschecksusa.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TKS US Corporate Website is back up in f8d4ad9.

repo: TKS-IT/status-page


text:
2D・3Dグラフ描画

https://threejs.org/examples/#webgl_marchingcubes
https://threejs.org/examples/#webgl_modifier_simplifier

よく考えたら2Dの方がすぐに実装できそうなので，まとめてこのissueで対処する．


text:
How do I enumerate the List?

If I use a key to display the list number and go to page 2, it resets and go back to 1, for sure.
But, there is any option to continue counting on every page?
I would like to keep couting the row number when I change the page.
Page 1:
1. item 1
2. item 2
3. item 3

Page 2:
4. item 4
5.item 5

...

@fmcdigital You can use the current page value and the number of items per page to calculate the item's order across all pages:
<li v-for="(item, index) in paginated('items')">
  {{ paginate.items.page * 3 + index + 1 }}. {{ item }}
</li>

In this example, I'm assuming that your paginated list is named items and the number of items per page is 3.

Yes, I already solved it, thanks for help :)

authors: TahaSh fmcdigital

repo: TahaSh/vue-paginate


text:
User guide on the website is not the latest

Under github.io, the document of options is not the latest.

Comparing to configuration.md

Options
options.confirm_new_project (default: false)
If true, the user will be asked for confirmation before creating a new project. The option can be overriden in the command line with --confirm-new-project flag.
options.confirm_new_tag (default: false)
If true, the user will be asked for confirmation before creating a new tag. The option can be overriden in the command line with --confirm-new-tag flag.
options.date_format (default: %Y.%m.%d)
Globally configure how dates should be formatted. All python's strftime directives are supported.
options.log_current (default: false)
If true, the output of the log command will include the currently running
frame (if any) by default. The option can be overridden on the command line
with the -c/-C resp. --current/--no-current flags.

Maybe you forgot to re-build the doc after #306?

Yes, for now, the documentation update is still a manual process usually done after each release, not each merge event. We need to automate this (see #78). Closing this as duplicate.

authors: hiiwave jmaupetit

repo: TailorDev/Watson


text:
FEAT: Add gitHub actions workflow for greeting new issues

Feature Request
Description
I would like to propose adding a new GitHub Actions workflow to the repository. The purpose of this workflow is to automatically generate a greeting message whenever a new issue is raised. This would help in acknowledging the issue submitter promptly enhancing their engagement with the project.
The workflow will be defined in a greetings.yml file within the .github/workflows directory.
This will streamline the issue management process and improve community interactions.
example:

please assign this issue to me under gssoc'24

repo: TailoredUI/TailoredUI


text:
fix(TDI-40819): Null values in dynamic schema

fixed null values in tSnowflakeOutput with dynamic schema after update
to new driver version

What is the current behavior? (You can also link to an open issue here)
After upgrade to new driver empty string values became escaped and empty string values now are used in case values for some of the fields are absent in tSnowflakeOutput
What is the new behavior?
If value for the field is absent - use null value which will be parsed as an empty string in new version of snowflake-jdbc.
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:
Sonar results

authors: build-talend-common olhava

repo: Talend/components


text:
Suggestion: Drop the 1 block cable and go "redstone (a)like"

Disclaimer: I can well understand if this gets rejected, but that never stopped me from suggesting :)
I really like this mod, the whole idea alone of exploring the Void itself intrigues me (it helps if you're a vivid and enthusiastic Minecraft player).
Here's my concern: cables are common. A generator, cables, maybe batteries. Seen that, done it....
Why not go back to basics? Sure, it will limit us players but I'm sure I can come up with reasoning (lemme think)..  But I think you might want to consider to set yourself even more apart by utilizing redstone mechanics, so no more cables but a conduit which needs to be placed down (like redstone dust) in order to make it work. Yes I realize all too well: an infusion altar on top of a power generator is going to be tricky if not impossible. Who ever said wielding void energy was easy in the first place? Considering the obsticles of even visiting the Void I think it would add up to not making this too easy.
"Voidic power is used to empower the voidic machines. Its essense is so powerful that it cannot be harnassed by anything known to man and therefor needs to be placed down on the ground. By doing so it will cut down into the very essence of the material and render it useless".
My idea is a black (vs red) speck trail on the blocks which represents the dark energies.
Ok, so another added suggestion: if possible render any associated block void (pun intended).
If placed on a block it should render that block useless. So if the void or the underlying block gets removed both get removed and that'll be the end of it. I know I'm repeating myself: who said trying to wield void energy should be easy? ;)
Just my 2 cents of course.

A neat concept, I'll keep it in mind. Though the reason I decided for the look that it has now is it's supposed to closely resembles the Void Crystal Block which, I guess you can call this lore if you want to, is basically a conduit for the void itself.

Closing due to deprecation

authors: ShelLuser Tamaized

repo: Tamaized/VoidCraft


text:
docs: updating docs-field-api removing old doc and updating to new pr…

Changelog

I noticed that the docs for the FieldOptions were outdated and some properties didn't exist anymore, added the new ones and remove old
https://github.com/TanStack/form/blob/main/packages/form-core/src/FieldApi.ts#L35-L42 updated mainly these ones

This is incredible, especially with how quick you moved on this! Thank you so so much.

This is incredible, especially with how quick you moved on this! Thank you so so much.

For sure! Let me know if there are other docs I could help with. 💪🏽

authors: crutchcorn enyelsequeira

repo: TanStack/form


text:
Queries are persisted with cacheTime of 0

Describe the bug
cacheTime and queryKey don't seem to behave how i would expect when using a persister.
Your minimal, reproducible example
https://codesandbox.io/s/persister-cachetime-55qnu4?file=/src/index.jsx:1108-1561
Steps to reproduce

Open codesandbox link
Read BUG: comments in useQuery hook options
Refresh page repeatedly using the refresh button in the browser preview

Note that the even though we've specified cacheTime: 0 that the resolved value is persisted and used in the new page render
Note that changing queryKey value will persist the previous value indefinitely. This creates cache bloat - it's effectively creating a memory leak as these values will continue to be deserialized on subsequent application loads

Expected behavior

cacheTime: 0 does not serialize the values into persisted storage.
Queries that specify cacheTime: 0 do not use cached values in subsequent unmounts/mounts

How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome 109.0.5414.119

TanStack Query version
4.23.0
TypeScript version
No response
Additional context
No response

// BUG: I would not expect this to be stored in persistant cache.

I think you're misunderstanding what cacheTime is for, which is one of the reasons why we will rename it in the next major version to gcTime. As long as your query is actively used, we will not remove it. with cacheTime: 0, the query will be removed from the cache as soon as it gets unused, which, in your example app, doesn't happen at all.
// BUG: Try changing this cache key and watch the old
// cached query persist indefinitely.
Yeah I think this is a bug. I've looked in the code and we only ever trigger a garbage-collection for a query if the last observer has been removed. We need to find a better way to do this for queries that have been put into the cache via hydration 🤔

I think if we would just call scheduleGc() in the constructor of the Query, this would be fixed. In case we have observers, this doesn't do anything, but it would make sure that queries that are created and never fetch will be removed in due time

I think you're misunderstanding what cacheTime is for, which is one of the reasons why we will rename it in the next major version to gcTime

I’ll admit that it definitely has confused me a number of times and I often go back to your blog post to clear it up. However in this case I think where I see it as a bug is as a consumer the persister is effectively a cache in my eyes, so when we say ‘cacheTime: 0’ my expectation is this wouldn’t be persisted in a cache.

you can exclude queries that have no cacheTime by filtering them out when dehydrating:
<PersistQueryClientProvider
  client={queryClient}
  persistOptions={{
    persister,
    dehydrateOptions: {
      shouldDehydrateQuery: (query) => !!query.options.cacheTime,
    },
  }}
>

if we fix the second bug, what will happen if you don't do this is:

the query will be persisted
when the query is restored and there are no observers, it will be removed instantly. This implies that you somehow have a global cacheTime of 0 set because without that, the defaults of 15 minutes would be taken because query options are not persisted - just data.

@TkDodo just to follow up: i integrated your fix into my local and it does indeed seem to clear up the stale queries not being gc'ed in the persisted cache. Thanks for this!  🎉
I also tried your shouldDehydrateQuery suggestion and it mostly works, but sometimes i was still seeing it serialized. The reason was query.options.cacheTime would be equal to the default cache time specified at the client level instead of 0. It's incredibly hard to reproduce though so i haven't been able to file a bug. Seems like some sort of race condition.

authors: TkDodo ianschmitz

repo: TanStack/query


text:
suspense() won't resolve when initial enabled is set to false

Describe the bug
When enabled is initially set to false, the suspense() function will never resolve. One scenario where this is relevant is when you want useQuery to execute only on the client site.
const { data,  } = useQuery({
  queryKey: ['TEST'],
  queryFn: async () => {
    // ....
  },

  //  Disabled when on the server site or due to other factors
  enabled: process.client,
});

if (process.client) {
  await suspense();
} else {
  onServerPrefetch(suspense);
}

If you execute this code, you'll notice that the web request never completes because suspense() never gets resolved.
Your minimal, reproducible example
https://stackblitz.com/edit/nuxt-starter-et73sx?file=app.vue,plugins%2Fvue-query.ts
Steps to reproduce

Open reproduction
Click Open in New Tab ()
page request never ends suspense() is never resolved.

Expected behavior
If the query is disabled, suspense() should resolve immediate
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome
Version: 4.32.6

Tanstack Query adapter
vue-query
TanStack Query version
v4.32.6
TypeScript version
No response
Additional context
No response

Related issue https://github.com/TanStack/query/issues/4924
It was done on purpose to support two use-cases.
There are easy ways to prevent suspending on the server when query is disabled, so I do not think we need to change it.

Oh! I didn't even notice this issue! That does seem very reasonable. Thank you.

authors: DamianOsipiuk Mini-ghost


text:
Wiki's code snippets contain raw html special symbols

The page "Hello world" contains raw > and & symbols.

Fixed, thanks for reporting. :+1: :cat2:

authors: LazyMechanic TankOs

repo: TankOs/SFGUI

license: Zlib


text:
🛑 Edge Adventures is down

In 20a82f3, Edge Adventures (https://www.edgeadventures.uk) was down:

HTTP code: 500
Response time: 682 ms

Resolved: Edge Adventures is back up in 2df1630.

repo: Tartan-Web-Design/monitoring


text:
Make SFX for Hovering Over A Menu Option

It is probably the most subtle sound of all the UI menus. But when the player hovers over a menu option, the stretching of flesh is heard.
Basically imagine holding someone's flesh in your hand, maybe you cut off someone's face. And then you stretch it like bacon strip. How would the muscle stretch, and how would it sound. It won't sound loud, but it would sound a little squishy, and the stretching of the meat would tighten its smaller particles in a hold to keep the flesh intact.
A good example of this could be tightening of a rope. Like how the rope makes this stretching yet tightening noise when its stretch to its limits. Something like that, but with imagine, a string of flesh.
Basically to put into a single sentence, "Naked meat on a meat hook, barely holding on from falling."

UI_Select.zip @Hhk187 @vitormaduro

repo: Team-Awkward-Smile/Epilogue


text:
Релиз v1.2

Подробные изменения

+ Возвращены модерационные команды. Теперь Вы снова сможете наказывать участников, используя бота. Однако, контекстные меню не вернуться. Я их хочу использовать для других целей

+ Сделаю очередную попытку восстановить работу интеграции с Boticord API, при этом не дудося их переподключениями WebSocket'а.

~ request запросы переписаны на aiohttp.

~ /buttonrole переписан. Теперь вместо необходимости страдать, указывая в правильном порядке роли для выдачи в слеш-команде, будет работать меню для выбора ролей. У - удобство.

~ В /botinfo теперь используется библиотека, которая определяет дистрибутив на основе ядра Linux.

~ Статистика бота теперь не будет (не должна) сбрасываться после перезагрузки.

~ Теперь участники, занесённые в чёрный список, будут видеть причину занесения и срок (если указано).

~ Использование app_commands.Range вместо проверки на длину аргумента вручную. Теперь Вам банально Discord не даст нарушить лимиты длины строки или числа.

~ Команда mad.debug и некоторые команды из cogs/tools.py перенесены в отдельный ког.

~ Произошло избавление от нескольких MongoClient() в разных кусках кода.

- Удалены команды: /ping, /outages, /version.

Чеклист
Поставьте x в квадратных скобках, чтобы поставить галочку.

[x] Изменённый код должен быть протестирован.

[ ] Я также обновил changelog.md для показа изменений.

[x] Поправка исправляет запрос #17.
[x] Поправка добавляет что-то новое.
[x] Поправка исправляет баг #17.
[ ] Поправка не изменяет код (редактирование README, орфографические исправления, т.д.).

@Tumpa-Prizrak, сделай review пж)))

Это совсем не 1.2. Больше выглядит как какое-нибудь 0.7
Убери todo. Оно совсем не надо в мейн ветке
Пропиши changelog таки. Это важно
Убери этот "на него немного так забили, поэтому необязательно" в contributing
На винде не работает. У меня в ветке это пофикшено, но здесь - он будет орать варнингами и ошибками
Тебе ещё нужен migrating? Как будто его уже можно убрать

В main ветке уже v1.2 Pre-Release, ты о чём?
А чем оно мешает? Ничем. Но я его уберу.
changelog сделаю. Покопаюсь в 70 коммитах.
Окей.
Кхм... Строка в README.md ни о чём не говорит?
Нужен.

У тебя написано, что он может не работать, так как ты его не тестил. Я потестил - не работает. Укажи это
Остальное окей

Прошу, @Tumpa-Prizrak.

repo: Team-MadBot/MadBot


text:
Tests/backend

I have added the test cases for all the apps.  If you feel any more test is  needed for a particular function please comment down #67.
cc: @SID262000

Can you retry running the linters on the above files. Thanks
cc: @AryanGupta0007

@SID262000 the linters have no effect on the test files

Looks like this PR has merged conflicts. Please resolve them, which will allow us to merge this into the main.
Cc: @AryanGupta0007

Creating a new PR then. @SID262000

repo: TeamCodeArena/DeliverEase


text:
🛑 hostux.net is down

In 8af3276, hostux.net (https://piped-api.hostux.net/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hostux.net is back up in 57a44c9 after 11 minutes.

repo: TeamPiped/piped-uptime


text:
🛑 lunar.icu is down

In 240848f, lunar.icu (https://piped-api.lunar.icu/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: lunar.icu is back up in bd7344c after 8 minutes.


text:
🛑 drgns.space is down

In f66c402, drgns.space (https://pipedapi.drgns.space/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: drgns.space is back up in 90d6d42 after 14 hours, 38 minutes.


text:
🛑 projectsegfau.lt in is down

In 2c26f7f, projectsegfau.lt in (https://pipedapi.in.projectsegfau.lt/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: projectsegfau.lt in is back up in ea8b2f1 after 27 minutes.


text:
🛑 kavin.rocks (Official) is down

In 9b838d8, kavin.rocks (Official) (https://pipedapi.kavin.rocks/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kavin.rocks (Official) is back up in f8e727f after 8 minutes.


text:
🛑 il.ax is down

In 6cfd0cc, il.ax (https://pa.il.ax/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: il.ax is back up in cddcbf0 after 13 minutes.


text:
🛑 privacydev.net is down

In f716e93, privacydev.net (https://api.piped.privacydev.net/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: privacydev.net is back up in 54cc138 after 16 minutes.


text:
🛑 il.ax is down

In 0e97327, il.ax (https://pa.il.ax/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: il.ax is back up in 1fb1ade after 10 minutes.


text:
🛑 kavin.rocks (Official) is down

In 2793fd6, kavin.rocks (Official) (https://pipedapi.kavin.rocks/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kavin.rocks (Official) is back up in 647ff81.


text:
🛑 adminforge.de is down

In 9fa08dd, adminforge.de (https://pipedapi.adminforge.de/healthcheck) was down:

HTTP code: 502
Response time: 468 ms

Resolved: adminforge.de is back up in b12ac62.


text:
🛑 frontendfriendly.xyz is down

In dcf255f, frontendfriendly.xyz (https://pipedapi.frontendfriendly.xyz/healthcheck) was down:

HTTP code: 502
Response time: 275 ms

Resolved: frontendfriendly.xyz is back up in 156492e.


text:
🛑 privacydev.net is down

In a8ba5a3, privacydev.net (https://api.piped.privacydev.net/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: privacydev.net is back up in 06d6a7f.


text:
🛑 esmailelbob.xyz is down

In 2c980ce, esmailelbob.xyz (https://pipedapi.esmailelbob.xyz/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: esmailelbob.xyz is back up in c04ae3e.


text:
🛑 privacydev.net is down

In b2e1377, privacydev.net (https://api.piped.privacydev.net/healthcheck) was down:

HTTP code: 502
Response time: 5459 ms

Resolved: privacydev.net is back up in f3201aa after 16 minutes.


text:
🛑 dc09.ru is down

In 30c08b2, dc09.ru (https://ytapi.dc09.ru/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: dc09.ru is back up in c78661b after 18 minutes.


text:
[BUG] StepF2 BPM-based "warps" don't treat notes as fakes, can cause erraneous misses

Is there an existing issue for this?

[X] I have searched the existing issues and none matched.

Operating System
Windows and Linux
CPU
AMD Ryzen 5 4500U (Windows), Intel Core 2 Duo E7600 (Linux)
GPU
Radeon integrated graphics (Windows), GeForce 210 (Linux)
Storage
NVMe SSD (Windows), SATA SSD (Linux)
Game Version
4.18.1
Game Mode
pump
Theme
Tested with the latest versions of Infinitesimal and Soundwaves
Describe the problem
This one is difficult to narrow down because of how bizarrely the gimmicks and effects are recreated in StepF2 official simfiles, but as far as I'm able to tell, notes within StepF2/StepP1 style "warps" (sections where the BPM is set to 100000000.000 instead of using actual real warps) are not treated as fake notes which can cause the player's health bar to immediately drain and fail them out. Can provide the SSC if needed.
Example (at 1:28 in case the timestamped link doesn't work): https://youtu.be/1BwgnzSIqmE?t=88
Describe what should happen
The intended behavior is as follows, with the section in question starting at 1:22 in case the timestamp in the link doesn't work (the misses were my fault, each note is completely possible to hit properly)
https://youtu.be/dl7bQSc6Z1M?t=82
Relevant Log output
ProjectOutfox.MainLog.2022-12-27--15.15.54.log
ProjectOutfox-Infinitesimal-rewrite.ThemeLua.2022-12-27--15.15.56.log
ProjectOutfox.Crash.2022-12-27--15.15.54.log
SSC:
1676 - Siromaru + Cranky - Conflict.zip

This should be fixed in a21, do confirm for me bro

fixed in 042

repo: TeamRizu/OutFox


text:
Multi echo compatibility

Add Multi echo compatibility

Fix the merge conflict but still need to test the code

That way you don't have to edit

Sup has added line 29: self.multi_echo = False/True to set the multi_echo option.


text:
🛑 Douanes is down

In 6088dc8, Douanes (http://www.douane.gov.ma) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Douanes is back up in 043144d.

repo: TebbaaX/DownTime-Score


text:
Feat/debug support

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] Implemented tests for new features.
[x] I tested the features already implemented.
[x] Added usage examples in the readme.

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


text:
Question: properly handle message processing failure

General question about Squiss and I guess SQS more generally:
How would you properly handle "business logic" errors ? I mean errors happening at the developer level (not SQS ones) and which are not "temporary" errors where the message should simply kept in queue to be retried (for instance, due to a network timeout error). An example would be a message containing a line from a CSV file, where the message consumer would parse the line and transform it to a JSON object. Let's say, the CSV line does contain an incorrect number of column: I would like consumer to properly fail, attach the error somehow (eg. "Invalid number of columns found") to the message and move the message somewhere (where it won't be retried automatically, it won't make sense since it will fail over and over again) to allow the developer to analyse/fix the error (either fixing the message content or the consumer logic).
Is this something that could be done using message attributes (to attach the error message)? are we allowed to "edit" attributes of an existing message?
Thanks for your heads up

Hey Loris! There are two good options here:
Traditionally, this sort of thing would be handled with a dead letter queue. In the SQS console, you can configure your main queue to say that if a message is received a certain maximum number of times, it should be pushed into a different queue and deleted from the main one. At my company we allow our messages to be received two times before pushing to the dead-letter. We allow for one retry in case a node fails or we forcibly restart/redeploy, but if we don't successfully delete the message that time (or willfully .keep() or .release() it), it goes to the dead letter for human review. If we discover an error in our codebase and wish to re-process all messages in the dead-letter after fixing it, we simply configure the dead-letter queue to use the main queue as ITS dead-letter, with a max receive of 1. Then, simply polling the dead-letter re-introduces those messages back to the main queue.
The above solution doesn't allow you to attach an error message; in SQS, all messages are immutable. There would be no way to attach new information without sending an entirely new message. But, it's nice because it catches all the errors that you couldn't possibly anticipate. If you did anticipate the error and want to attach it, your thought of using message attributes sounds like a great idea as long as those attributes aren't core to your application logic and would cause corruption if a message with an error attribute were to be re-processed. What you'd do in that case is send a new message directly into your dead-letter with the error attribute attached (which you can do with either a second instance of Squiss, or by using the AWS SQS client directly-- which is available as a property of the Squiss instance). Then, when you review that queue, you know that any message lacking an error attribute is one that failed without an anticipated error.
Hope this helped! Let me know if that solves your conundrum.

Hey @TomFrost
Thanks a lot for the deep and clear response! really appreciate it! Both options are great and have their pros/cons. I do like how you set a the main queue as a dead-letter queue to its dead-letter queue, pretty clever! I will let you know how I end up implementing it, but the first option looks simpler and should be enough for our needs: business logic errors should be quite rare, so we could just check for failed jobs in the dead-letter queues, and look for the error messages in our server logs.
Thanks again.

Sure thing! Good luck :)

authors: TomFrost loris

repo: TechnologyAdvice/Squiss

license: isc


text:
Command '/opt/odoo/common/build.d/250-postgres-client' returned non-zero exit status 100. error when running invoke img-build --pull command

Describe the bug
Below is the error when running the invoke img-build command
[+] Building 20.3s (9/9) FINISHED                                                                                docker:default
 => [odoo internal] load .dockerignore                                                                                0.0s
 => => transferring context: 159B                                                                                0.0s
 => [odoo internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 108B                                                                                0.0s
 => [odoo internal] load metadata for ghcr.io/tecnativa/doodba:16.0-onbuild                                                                                1.4s
 => [odoo 1/1] FROM ghcr.io/tecnativa/doodba:16.0-onbuild@sha256:5f61091c3c97079cfbb3e69598518b00996c2edabc10617d78e0661cb242fde4                                                                                0.0s
 => [odoo internal] load build context                                                                                0.0s
 => => transferring context: 946B                                                                                0.0s
 => CACHED [odoo 2/1] RUN groupadd -g 1000 odoo -o     && useradd -l -md /home/odoo -s /bin/false -u 1000 -g 1000 odoo     && mkdir -p /var/lib/odoo     && chown -R odoo:odoo /var/lib/odoo /qa/artifacts     && chmod a=rwX /qa/artifacts  0.0s
 => CACHED [odoo 3/1] COPY --chown=root:odoo ./custom /opt/odoo/custom                                                                                0.0s
 => CACHED [odoo 4/1] RUN [ -d ~root/.ssh ] && rm -r ~root/.ssh;             mkdir -p /opt/odoo/custom/ssh             && ln -s /opt/odoo/custom/ssh ~root/.ssh             && chmod -R u=rwX,go= /opt/odoo/custom/ssh             && sync   0.0s
 => ERROR [odoo 5/1] RUN /opt/odoo/common/build && sync                                                                                18.7s
------
 > [odoo 5/1] RUN /opt/odoo/common/build && sync:
0.488 doodba WARNING: Not aggregating code repositories
0.545 doodba INFO: No installable requirements found in /opt/odoo/custom/dependencies/apt_build.txt
0.545 doodba INFO: No installable requirements found in /opt/odoo/custom/dependencies/apt.txt
0.545 doodba INFO: No installable requirements found in /opt/odoo/custom/dependencies/gem.txt
0.545 doodba INFO: No installable requirements found in /opt/odoo/custom/dependencies/npm.txt
0.545 doodba INFO: Executing: ['pip', 'install', '--no-cache-dir', '-r', '/opt/odoo/custom/dependencies/pip.txt']
0.992 Collecting git+https://github.com/OCA/openupgradelib.git@master (from -r /opt/odoo/custom/dependencies/pip.txt (line 1))
0.992   Cloning https://github.com/OCA/openupgradelib.git (to revision master) to /tmp/pip-req-build-fspudfpb
0.994   Running command git clone --filter=blob:none --quiet https://github.com/OCA/openupgradelib.git /tmp/pip-req-build-fspudfpb
5.451   Resolved https://github.com/OCA/openupgradelib.git to commit 8b0c22b7ca6c23aeb692d6116276c9d6a7e49aae
5.453   Preparing metadata (setup.py): started
7.788   Preparing metadata (setup.py): finished with status 'done'
7.931 Collecting unicodecsv
8.094   Downloading unicodecsv-0.14.1.tar.gz (10 kB)
8.099   Preparing metadata (setup.py): started
8.411   Preparing metadata (setup.py): finished with status 'done'
8.464 Collecting unidecode
8.509   Downloading Unidecode-1.3.8-py3-none-any.whl (235 kB)
8.609      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 235.5/235.5 kB 2.4 MB/s eta 0:00:00
8.664 Collecting jingtrang
8.708   Downloading jingtrang-0.1.2-py2.py3-none-any.whl (1.3 MB)
9.173      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.3/1.3 MB 2.9 MB/s eta 0:00:00
9.181 Requirement already satisfied: lxml in /usr/local/lib/python3.10/site-packages (from openupgradelib==3.7.2.dev6+g8b0c22b->-r /opt/odoo/custom/dependencies/pip.txt (line 1)) (4.6.5)
9.228 Collecting cssselect
9.271   Downloading cssselect-1.2.0-py2.py3-none-any.whl (18 kB)
9.284 Building wheels for collected packages: openupgradelib, unicodecsv
9.285   Building wheel for openupgradelib (setup.py): started
9.951   Building wheel for openupgradelib (setup.py): finished with status 'done'
9.951   Created wheel for openupgradelib: filename=openupgradelib-3.7.2.dev6+g8b0c22b-py2.py3-none-any.whl size=82152 sha256=729dda9b8835881da6f4bd14d4f1a8e7aec462b3b975cb47d0318fb77c8be324
9.951   Stored in directory: /tmp/pip-ephem-wheel-cache-dc7b53q9/wheels/0e/86/10/b55bcaefed40982d4e0ce60c702a7fb00921ca2683612dde64
9.955   Building wheel for unicodecsv (setup.py): started
10.36   Building wheel for unicodecsv (setup.py): finished with status 'done'
10.36   Created wheel for unicodecsv: filename=unicodecsv-0.14.1-py3-none-any.whl size=10746 sha256=3cc832845f9bfa0293eb510339f35d270796b4d47c023b590d4ffbb0f9259121
10.36   Stored in directory: /tmp/pip-ephem-wheel-cache-dc7b53q9/wheels/9c/ea/66/8e45247b09052a933eb1a680b7c64802298faba58aac9b346b
10.36 Successfully built openupgradelib unicodecsv
10.83 Installing collected packages: unicodecsv, unidecode, jingtrang, cssselect, openupgradelib
11.15 Successfully installed cssselect-1.2.0 jingtrang-0.1.2 openupgradelib-3.7.2.dev6+g8b0c22b unicodecsv-0.14.1 unidecode-1.3.8
11.15 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
11.40
11.40 [notice] A new release of pip is available: 23.0.1 -> 24.2
11.40 [notice] To update, run: pip install --upgrade pip
11.86 Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
11.94 Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
11.97 Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
12.00 Get:4 http://deb.debian.org/debian bookworm/main amd64 Packages [8787 kB]
12.07 Get:5 http://apt.postgresql.org/pub/repos/apt bookworm-pgdg InRelease [129 kB]
13.24 Get:6 http://apt.postgresql.org/pub/repos/apt bookworm-pgdg/main amd64 Packages [357 kB]
13.50 Get:7 http://deb.debian.org/debian bookworm-updates/main amd64 Packages [2468 B]
13.51 Get:8 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages [188 kB]
14.52 Fetched 9718 kB in 3s (3217 kB/s)
14.52 Reading package lists...
14.98 W: http://apt.postgresql.org/pub/repos/apt/dists/bookworm-pgdg/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
18.50 Use of uninitialized value $value in substitution (s///) at /usr/share/perl5/Debconf/Format/822.pm line 65, <__ANONIO__> line 1.
18.50 Use of uninitialized value $item in hash element at /usr/share/perl5/Debconf/DbDriver/File.pm line 88, <__ANONIO__> chunk 1.
18.52 Use of uninitialized value $value in substitution (s///) at /usr/share/perl5/Debconf/Format/822.pm line 65, <__ANONIO__> line 1.
18.52 Use of uninitialized value $item in hash element at /usr/share/perl5/Debconf/DbDriver/File.pm line 88, <__ANONIO__> chunk 1.
18.52 debconf: delaying package configuration, since apt-utils is not installed
18.58 dpkg: unrecoverable fatal error, aborting:
18.58  fgets gave an empty string from '/var/lib/dpkg/diversions'
18.59 E: Sub-process /usr/bin/dpkg returned an error code (2)
18.59 Traceback (most recent call last):
18.59   File "/opt/odoo/common/build", line 30, in <module>
18.59     subprocess.check_call(command)
18.59   File "/usr/local/lib/python3.10/subprocess.py", line 369, in check_call
18.59     raise CalledProcessError(retcode, cmd)
18.59 subprocess.CalledProcessError: Command '/opt/odoo/common/build.d/250-postgres-client' returned non-zero exit status 100.
------
failed to solve: process "/bin/sh -c /opt/odoo/common/build && sync" did not complete successfully: exit code: 1

Affected versions: 16.0
Steps to reproduce the behavior:

Run copier copy gh:Tecnativa/doodba-copier-template ~/path/to/your/subproject
Then run invoke img-build pull

Expected behavior

It should build successfully.

Additional context

Postgres versions: 15 or 14

There's still no support on the template for PG 16:
https://github.com/Tecnativa/doodba-copier-template/blob/acda9a8c7096f7bc7e10fe74a5febe73eb0878b0/copier.yml#L375

There's still no support on the template for PG 16:
https://github.com/Tecnativa/doodba-copier-template/blob/acda9a8c7096f7bc7e10fe74a5febe73eb0878b0/copier.yml#L375

Sorry that is a typo on my part I tried using PG 14 and 15.

Please check all the previous steps to be sure that your environment has all the correct parameters and pre-requirements. Maybe it was a temporary glitch. Have you tried again?

I retry the command it was ok now.

authors: dtorreskaertech pedrobaeza

repo: Tecnativa/doodba-copier-template


text:
Не работает

Не открывает женскую одежду

можно ссылку?

Привет. Почини пожалуйста профиля :(
Или можешь подсказать как самому запустить все это? Я пробовал через node.js по гайду, все запустил, зашел на 192.168.. а профиля точно также не грузятся.

локально профили не посмотреть будет - база данных у меня хранится

authors: 1817444 Tehzombie-secret Worserw

repo: Tehzombie-secret/Marketplace-previewer


text:
Setup Error: pod install

Dependency manager (Carthage, CocoaPods, SPM, Manually):

What did you do?

I added pod 'Desk360LiveChat' and info.plist requirements but ı face to face this problem and to solve tired!  "[!] Unable to find the Xcode project"

Do you have advise ?

Hi @Erdicem
Can you please share a snippets of your Podfile if possible? it will help us understand your issue quickly
seems there is a problem in your Podfile structure/syntax

are you trying to build the Sample app attached with this repo? because seems this is an exact copy of the Example pod file
if this is the case you need to navigate to the desk360-live-chat folder:
run xcodegen to generate the Xcode Project
then run pod install to install the pods

a better way

create your own project
init Pods
add pod 'Desk360LiveChat' to your Podfile
install
and you should be good to go.

and I did not see LiveChat.xcodeproj  file.
How I can solve this problem ?

please run xcodegen first

Of course, but this project run Xcode 13 version ?

yeah there is no limitation of Xcode version


text:
Add Strong Name.

Add to .csproj
<SignAssembly>true</SignAssembly>
<AssemblyOriginatorKeyFile>key.snk</AssemblyOriginatorKeyFile>

and add key.snk in project properties.
like this:

The strong name makes your library more useful (sometimes required for modules or extensions).

we are not planning to release a signed version. it doesn't add any benefit but has many downsides. you can sign it on your side in your ci/cd pipeline if you need to.
generally signing is neither recommended nor needed for modern .NET applications.


text:
Please allow to specify custom (local) telegram server url

I would like to request/propose a feature
I want to use local telegram bot api server (https://core.telegram.org/bots/api#using-a-local-bot-api-server), but api.telegram.org urls are hardcoded in client. Also TelegramClient ignores baseUrl of HttpClient.
Please allow to specify custom server url.

This feature is not yet available in official released package. It is available in preview through CI/CD feed: https://dev.azure.com/tgbots/Telegram.Bot/_packaging?_a=connect&feed=Telegram.Bot%40Local
API 5.1 support added in Telegram.Bot 16.0.0-ci.* packages.


text:
SendPhotoAsync

private bool pictureSend(string messagetosend)
{
bool success = true;
string Token = Convert.ToString(txtToken.Text);
string ChatIDChannel = Convert.ToString(txtChatID.Text);
string phototosend = "C.\image.jpg";
var Bot = new Telegram.Bot.TelegramBotClient(Token);
using (var stream = System.IO.File.Open(phototosend, FileMode.Open))
{
FileToSend fts = new FileToSend();
fts.Content = stream;
fts.Filename = phototosend.Split('\').Last();
Bot.SendTextMessageAsync(ChatIDChannel, messagetosend);
//Bot.SendPhotoAsync(ChatIDChannel, fts, messagetosend);
}
}
SendTextMessageAsync works but SendPhotoAsync don't work. Is something in my Code wrong or should it work like that?

@morph1 read https://github.com/TelegramBots/telegram.bot/blob/develop/ISSUE_TEMPLATE.md

hi,
I think @tgbots_dotnet group not exists in telegram, is your group changed ?
I have to important question:
1- await bot.SendPhotoAsync(TargetChatId, F, Title); Freeze and "never" go do next line, but last week it work fine, but this days it freeze ! and even dont raise any error !
but when i make a url with query string and put in Web browser it work fine !
2- how can i get the command that your dll send to telegram bot?
thanks .


text:
Error: Can't find npm module 'react'. Did you forget to call 'Npm.depends' in package.js within the 'modules-runtime' package?

I am getting this error after a fresh install of Nova  on OSX.My meteor version is 1.3.1.
Error: Can't find npm module 'react'. Did you forget to call 'Npm.depends' in package.js within the 'modules-runtime' package?

Did you run npm install?

I just run meteor . Sorry. I didn't recognize my  npm install command has not finished successfully.it is ok now. thanks

authors: SachaG naysumyat

repo: TelescopeJS/Telescope


text:
Issue backslash not removed from annotation

The generator leaves backslashes \ on annotation
@c_header "
#define SIMPLE_CLICK \"Simple Click\""

should generate
#define SIMPLE_CLICK "Simple Clic"

but the result is
#define SIMPLE_CLICK \"Simple Click\"

I checked, and the same happens for all string literals. E.g. if I make a property
property test : String = "\"Some string\""

It will generate this C-code:
t_var.Test_test_var = "\"Some string\"";

But in that case it actually makes sense, since we are adding the outer "" back.
So, maybe the actual fix would be to treat annotation values different from string literals? In a way, it isn't really a string literal...

Or, another thought:
We could (should?) unescape the string literals when we parse it (since the backslashes are not really a part of the actual string we want), and escape it back when we generate the code.
This might be even more correct, if you consider languages that doesn't use "" to express string literals.
You could choose to use single quotes in e.g. JavaScript...

I know it has been some back and forth changes in the way we by default escape quotes in annotations, extern expressions and maybe string literal. I guess we should indeed treat string literals different from annotations. @ffleurey what is now the (un)escaping strategy in:

String literal,
annotation, and
extern?

authors: brice-morin jakhog madkira

repo: TelluIoT/ThingML


text:
Feature request: Set advanced settings on disks

It would be a good extension to this provider, if the advanced settings on disks can be set.
From Proxmox manual:

Details
aio=<native | threads>
    AIO type to use.
backup=<boolean>
    Whether the drive should be included when making backups.
bps=<bps>
    Maximum r/w speed in bytes per second.
bps_max_length=<seconds>
    Maximum length of I/O bursts in seconds.
bps_rd=<bps>
    Maximum read speed in bytes per second.
bps_rd_max_length=<seconds>
    Maximum length of read I/O bursts in seconds.
bps_wr=<bps>
    Maximum write speed in bytes per second.
bps_wr_max_length=<seconds>
    Maximum length of write I/O bursts in seconds.
cache=<directsync | none | unsafe | writeback | writethrough>
    The drive’s cache mode
cyls=<integer>
    Force the drive’s physical geometry to have a specific cylinder count.
detect_zeroes=<boolean>
    Controls whether to detect and try to optimize writes of zeroes.
discard=<ignore | on>
    Controls whether to pass discard/trim requests to the underlying storage.
file=<volume>
    The drive’s backing volume.
format=<cloop | cow | qcow | qcow2 | qed | raw | vmdk>
    The drive’s backing file’s data format.
heads=<integer>
    Force the drive’s physical geometry to have a specific head count.
iops=<iops>
    Maximum r/w I/O in operations per second.
iops_max=<iops>
    Maximum unthrottled r/w I/O pool in operations per second.
iops_max_length=<seconds>
    Maximum length of I/O bursts in seconds.
iops_rd=<iops>
    Maximum read I/O in operations per second.
iops_rd_max=<iops>
    Maximum unthrottled read I/O pool in operations per second.
iops_rd_max_length=<seconds>
    Maximum length of read I/O bursts in seconds.
iops_wr=<iops>
    Maximum write I/O in operations per second.
iops_wr_max=<iops>
    Maximum unthrottled write I/O pool in operations per second.
iops_wr_max_length=<seconds>
    Maximum length of write I/O bursts in seconds.
iothread=<boolean>
    Whether to use iothreads for this drive
mbps=<mbps>
    Maximum r/w speed in megabytes per second.
mbps_max=<mbps>
    Maximum unthrottled r/w pool in megabytes per second.
mbps_rd=<mbps>
    Maximum read speed in megabytes per second.
mbps_rd_max=<mbps>
    Maximum unthrottled read pool in megabytes per second.
mbps_wr=<mbps>
    Maximum write speed in megabytes per second.
mbps_wr_max=<mbps>
    Maximum unthrottled write pool in megabytes per second.
media=<cdrom | disk> (default = disk)
    The drive’s media type.
queues=<integer> (2 - N)
    Number of queues.
replicate=<boolean> (default = 1)
    Whether the drive should considered for replication jobs.
rerror=<ignore | report | stop>
    Read error action.
scsiblock=<boolean> (default = 0)
    whether to use scsi-block for full passthrough of host block device
 secs=<integer>
    Force the drive’s physical geometry to have a specific sector count.
serial=<serial>
    The drive’s reported serial number, url-encoded, up to 20 bytes long.
shared=<boolean> (default = 0)
    Mark this locally-managed volume as available on all nodes.
 size=<DiskSize>
    Disk size. This is purely informational and has no effect.
snapshot=<boolean>
    Controls qemu’s snapshot mode feature. If activated, changes made to the disk are temporary and will be discarded when the VM is shutdown.
ssd=<boolean>
    Whether to expose this drive as an SSD, rather than a rotational hard disk.
trans=<auto | lba | none>
    Force disk geometry bios translation mode.
werror=<enospc | ignore | report | stop>
    Write error action.
wwn=<wwn>
    The drive’s worldwide name, encoded as 16 bytes hex string, prefixed by 0x.

Especially I'm interested on setting speed limits for disks.
Hopefully, anyone can implement this. :grinning:

Hello @cospeedster
I will have a look, I'm interested too.
I think mbps, mbps_rd and mbps_wr are enough, what is your opinion?

Hi @V-Paranoiaque,
I'll need these four:

mbps_rd
mbps_rd_max
mbps_wr
mbps_wr_max

Additional to this, it would be very helpful, if we can set the vcpus optional in the resource. Maybe you can look at it, too?

vcpus looks easier to implement, but maybe better @cospeedster to create a second issue

Okay, I'll do this shortly. You're right! ;-)

I opened it here Telmate/terraform-provider-proxmox#120.

I have added the 5 options @cospeedster, waiting your validation before making the PR
https://github.com/V-Paranoiaque/terraform-provider-proxmox/tree/feature/mbps

@V-Paranoiaque
As far as I can evaluate this, it looks good for me. Sadly, I'm not so familiar with go. Am I right that something need to be changed on the API?
Is the following right?
If i just set mbps it will affect mbps_rd and mbps_wr. So I have the choice to set just mbps or  mbps_rd and mbps_wr?

No need to modify the API, it's just an extra parameter who will be generated automatically.
I suppose, I have used the documentation.

Okay, that sounds great!

https://github.com/Telmate/terraform-provider-proxmox/pull/125

Setting does not work on disk0 for me.
On additional disks it works.
For example, I set:
      mbps_rd      = 250
      mbps_rd_max  = 250
      mbps_wr      = 250
      mbps_wr_max  = 250

For disk0
https://github.com/Telmate/proxmox-api-go/pull/72

This worked for me! Thank you!

authors: V-Paranoiaque cospeedster

repo: Telmate/terraform-provider-proxmox