text:
Unable to Expose to 0.0.0.0

Hey there,
Thank you so much for this project!! 4 little instructions to install, WAY simpler than the native way!
Currently, I am trying to host this in a container for my local network, however the way this is setup natively:
127.0.0.1:8888
Doesn't allow it to be exposed to my network
Changing the config file to be 0.0.0.0:8888 and 0.0.0.0 port 8888 allows me to get to the User Manager through the /uc/admin page, but going to ipaddress:8888 in my web browser, where Outline should appear, shows a blank dark-themed screen
Is there another way to expose this application to the network?
Thank you!

Update, changing to my local IP works locally (instead of  0.0.0.0:8888, use localip:8888, in my case 10.1.10.100:8888), however I am trying to assign this to a domain @ notes.mydomain.com, and while I can load this on my local net, trying to load on notes.mydomain.com loads the blank page again, while the UC Admin can be accessed just fine
I've got an NGINX proxy manager on a different server that is pointing back to this instance

I'm trying to do exatcly the same. Have you found a solution to this? Thanks

Bump

这个问题我也遇到了   但是，这个nginx代理就会出问题。外网访问 ，但是无法绑定域名。

I found how to fix this,
Combined with the resolution in here of adding  user: 0:0 // add this line <---------------------------- This line does not exist, add it to wk-outline in the Docker Compose and what I'm about to post here, this should work for you all, too
FULL STEPS OF HOW I SET THIS UP:
~~
Create an Ubuntu / Debian Container / VM
Install Updates and Upgrades
Install Docker, Make, and Nano
Clone the Git
Clone the config.sh from scripts/config.sh.example
Nano the config.sh
Then, “Make Install”
Commands:
Start Off:
cd /
mkdir outlineserverfolder
Apt-get update && apt-get upgrade -y
Apt install make && apt install nano
Install Docker:
apt-get install ca-certificates curl gnupg
install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg
echo \   "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian \   $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \   sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
apt-get update
apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin docker-compose
Install Outline from Github:
outline-docker-compose-master.zipcd directory/where/outlinedata/is/stored (/outlineserverfolder in this case)
git clone https://github.com/vicalloy/outline-docker-compose.git
cd outline-docker-compose
cp /scripts/config.sh.sample scripts/config.sh
nano scripts/config.sh
OutlineConfig: URL= (PublicFacingURL:PublicFacingPort[PORT REQUIRED!])notes.mydomain.com:443 PORT= 3000
NginxConfig: URL=0.0.0.0 (Ties Nginx Container to the Host IP) PORT = 8888
CTRL + O to save, CTRL + X to exit nano
Run the MakeFile to Install and Setup the Server:
make install
Other Commands:
docker ps ~ Will show Docker Containers
docker exec -it  /bin/bash ~ executes /bin/bash on container, CTRL+P+Q to exit
make install ~ Installs and Sets Up the server
make start ~ Starts all associated containers
make stop ~ Stops all associated containers
make clean ~ Clears data from all containers
make clean-data ~ Clears All Container .env Variables and All Container Data, also Deletes Containers
Notes regarding- Outline Config: URL = PublicFacingURL:PublicFacingPort
The URL and domain that you are using to host this with the port of the site. Essentially, if you host this at notes.yourdomain.com via cloudflare, and you’re pointing it back to an NGINX proxy, the service itself will host on the NginxConfig host, 0.0.0.0, and is accessible via port 8888, so redirect from notes.yourdomain.com to the IP Address of the Outline host on port 8888, ensure 443 and 80 are open in your firewall, and in the configuration, when it is asking for the OutlineConfig URL, ensure that you list both the domain URL and the port utilized (if using HTTP, port 80, if HTTPS, port 443) in the Outline Config, the port is a required element
How this is setup:
Docker Host: 192.168.1.100
Config File:
                OutlineSection ~ URL: notes.mydomain.com:443 PORT: 3000

                NginxSection    ~ URL: 0.0.0.0 PORT: 8888

                Leave the Rest Alone

Nginx Proxy Manager:
Add a HTTP Redirection Host to 192.168.1.100:8888 from notes.mydomain.com
               WebSocket Support + Block Common Exploits + Cache
               SSL > Request New SSL Certificate

Firewall(s):
              NAT Forward port 80/443 to Nginx Proxy Manager

              If multiple firewalls / routers / layers to network, push port through to each until host reached

Access:
             For Internal Useage / Testing, 192.168.1.100:8888 will get to the site

             For Public Access / Useage, notes.mydomain.com should get to the site

             For User Management, 192.168.1.100:8888/uc/admin/auth/user/

                            NOTE: USER MUST HAVE LISTED EMAIL ADDRESS OR SIGN-IN WILL FAIL

In this current state, photos will fail to upload anywhere. Within the docker-compose.yml,
wk-outline:
image: outlinewiki/outline:${OUTLINE_VERSION}
command: sh -c "yarn db:migrate --env production-ssl-disabled && yarn start"
environment:
- DATABASE_URL=postgres://user:pass@wk-postgres:5432/outline
- DATABASE_URL_TEST=postgres://user:pass@wk-postgres:5432/outline-test
- REDIS_URL=redis://wk-redis:6379
- AWS_S3_UPLOAD_BUCKET_NAME=outline-bucket
env_file:
- ./env.outline
- ./env.oidc
volumes:
- ./data/outline:/var/lib/outline/data
user: 0:0 // add this line <---------------------------- This line does not exist, add it to wk-outline
restart: unless-stopped
depends_on:
- wk-postgres
- wk-redis
##BEGIN MINIO
- wk-minio
##END

I wrote an entire document on Outline for how to host Outline, sorry if the formatting isn't great, but this is basically every step I took

What you'll need to do is set the config.sh outline URL to the PUBLIC FACING URL:443 or :80, depending on if HTTP or HTTPS, if using LetsEncrypt with your NGINX Proxy Manager, set it to your notes.yourdomain.com:443. Leave the PORT option at 3000

Then, for the NGINX config, I have it hosted on 0.0.0.0, to ensure that if you navigate to the local domain, 192.168.1.100:8888, it still works and still redirects fine, so that the 127.0.0.1 cannot access issue is gone, but with the outline url set to notes.yourdomain.com:443 PORT3000 you should be able to redirect through Proxy Manager to it just fine without needing advanced flags or location flags

The only thing I am now working on is blocking access to the /uc/admin site through proxy manager, and though I am struggling to figure that out, this is not an NGINX Proxy Manager Github, so I'll figure that one out

@giovannipollo @Codename-11 @hardingCheng

Please ping me if anyone has issues with understanding that, I just copy pasted from my Outline page

Thanks it works!
Following the documents of @7ekhed , I did the following things.
clone git
git clone https://github.com/vicalloy/outline-docker-compose.git
cd outline-docker-compose
cp scripts/config.sh.sample scripts/config.sh

Change configuration
nano scripts/config.sh

URL=<my_url>:8888
HTTP_IP=0.0.0.0

Change configuration - 2
nano scripts/templates/docker-compose.yml

volumes:
- ./data/outline:/var/lib/outline/data
user: 0:0 // add this line <---------------------------- This line does not exist, add it to wk-outline
restart: unless-stopped

Install and run
make install

Anyone has tried this approach with traefik? I tried numbers on configuration to use traefik as reverse proxy but it would only work temporarily then nginx would result in worker process 23 exited with code 0

Thank you all, especially @7ekhed & @sheepvs5 !
I spend several hours to try to fix it.
Got it to work now. 🤝🏼

Mine still not working.
I have no problem open it with local ip:8888
http://192.168.1.227:8888
then I set up nginx reverse proxy with my own domain name pointing to my local ip and port 8888
the nginx proxy manager is running on a different server on my local network:

config.sh file URL 但and HTTP_IP was set like below:

but when I go to https://docs.stonelab.me
I can open the page, but it brought to the following page with a button Using OenID to continue, then nothing working from there. I think it might be the authentication issue?

repo: vicalloy/outline-docker-compose


text:
Add an option for displaying the track enveloppe

For track shapes that are very different from a triangle, I'd like to know what's the geometric enveloppe of my track. (The enveloppe is like a giant rubber band wrapped around the track.)
Would it be possible to add an option for displaying the enveloppe and its length?
For example, a small button with a lasso in it, below the other green buttons in the top-right corner of the map, would show/hide the enveloppe on the map, and a message box somewhere with the enveloppe length and its opening lengths. (The opening length is the distance between the start and end waypoints.)

Not sure what you exactly mean ? Do you have an exemple / known OSS implementation ?

Here's an example of a flight track, where I manually added the enveloppe in green.

What is the purpose ?

The purpose is to get an evaluation of the track length that is more realistic than with the standard geometric shapes now used for distance scoring.
With a fixed number of sides (3 for FAI triangles, or even 4 as were allowed in the past by French CFD rules), many "interesting" tracks (those with many extrema, or with convex shapes like a circle) do get widely under-evaluated. The example image above shows that well on such a track, with the green enveloppe much longer than the blue FAI triangle. On the other hand, tracks with just 3 points will often have an enveloppe almost identical to their FAI triangle. This is the case for most of the top tracks in the CFD this year.
I proposed that idea publicly last spring in a letter that was published in the #166 issue of Parapente Mag.
Then last week, I was happily surprised to learn that a Paramotor association had adopted it and implemented it for their own distance scoring. See their new rule here:
[http://cfdm.forumperso.com/t141-reglement-de-la-cfdm]
And here's an example of a paramotor track with the enveloppe shown.
[http://cfdm.forumperso.com/t130-0001-13-08-16-julien-heyl-79-6-km-homologue]
So now my request is to add that capability to VisuGps as an optional feature. People who don't care will see no change. And people interested can visualize their envelopes, and get its length, by clicking on a button.
Note that I've heard that many graphic libraries do already have functions for drawing envelopes. If you do use such a library, this may be relatively easy to implement. Else it'll be more work. I'm a developer, so I volunteer to contribute if needed.

Looking at your ex your previous reasoning does not seem valid.
If the question is how to better reflect "real" distance for recreational pilots, may be there are better options ? (ie more segments).
I'll probably be quite busy for the 2 coming weeks but nappy to discuss this after.

source: gharchive/issue

authors: JFLarvoire vicb

license: mit

license_type: permissive

license_source: bigquery


text:
Image alt attributes needed

Images are not labeled with alt attributes

Resolved

license: MIT

license_source: github-api


text:
🛑 SC storefront productend is down

In 55d0fc5, SC storefront productend (https://shop.line.me/@024azltq/product/319384970) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SC storefront productend is back up in f7e9822.

repo: vichaos/upptime


text:
Code link isn't saved

https://arxiv.org/abs/1707.05821v1

Fixed in #160


text:
Results in NeuralQA inconsistent with same model running on HF

I've tested a model that I've deployed on NeuralQa vs one deployed on HF and noticed that the same inputs are yielding different outputs even though it's using the exact same model. This can of course be attributed to a few things but I can't seem to identify the culprit.
Here's the context:
Question:
Are your handsets locked or unlocked?
Corpus:
['No, all our handsets are unlocked.','Since your SIM isn’t working in your handset while other SIM cards are, it might be an issue with your handset provider; or the mobile phone could be locked, meaning it only accepts SIM cards from a particular service provider. Please contact the handset dealer for more assistance.']
The following returns 'unlocked' which is the correct response:
See Demo on HuggingFace
I've configured the exact same model in NeuralQA (with relsnip disabled) and the result is 'locked' even though I'm feeding exactly the same inputs.
Here my log:

0:No, all our handsets are unlocked.
[{'answer': 'unlocked', 'took': 0.35032129287719727, 'start_probability': '0.92030567', 'end_probability': '0.00026586326', 'probability': '0.460418697912246', 'question': 'Are your handsets locked or unlocked?', 'context': 'no, all our handsets are  unlocked '}]
1:Since your SIM isn’t working in your handset while other SIM cards are, it might be an issue with your handset provider; or the mobile phone could be locked, meaning it only accepts SIM cards from a particular service provider. Please contact the handset dealer for more assistance.
[{'answer': 'locked', 'took': 0.5319299697875977, 'start_probability': '0.9462091', 'end_probability': '0.007203659', 'probability': '0.48030819557607174', 'question': 'Are your handsets locked or unlocked?', 'context': 'since your sim isn ’ t working in your handset while other sim cards are, it might be an issue with your handset provider ; or the mobile phone could be  locked , meaning it only accepts sim cards from a particular service provider. please contact the handset dealer for more assistance'}]

As you can see the 2nd answer gets a higher probability but that doesn't really make sense as it's exactly the same model.
The main difference is that the NeuralQA model is feeding the corpus content independently while in the HF example, we're feeding the entire corpus.
Any ideas on why this is happening?

Could this be related to #39

@jvence ,
Yup, it is definitely related to #39 .The solution will be to rewrite that piece using the HF approach.
Its part of some work to convert the entire lib to use pytorch. See #53 .
Hoping to have some updates in the coming week or so.

Yes further testing with multiple models does confirm that the results given by NeuralQA are way off the ones returned by HF face model. Hope this can be resolved soon as it's critical to us. Thank you

Hi @victordibia, just checking in to see if there's any update on this? Seems like a pretty critical issue. Thanks

Noticed something interesting. Running the following through a model

Sentence: My name is Jean
Question: what is your name?
answer= {'answer': '', 'took': 1.0392448902130127, 'start_probability': '0.9280809', 'end_probability': '1.2582249e-06', 'probability': '0.46404171642723213'}

The start probability is very high but the actual probability is only 0.46. Is this normal?

@victordibia Is this project still maintained? We have not heard from you for a while. Hope everything is ok.

@victordibia It's a shame that this is no longer maintained. What are you plans vis-a-vis this project?

authors: jvence victordibia

repo: victordibia/neuralqa


text:
Fix for issue 224

Removed "singularize" from menu in layouts/partials/nav.html

Super!

source: gharchive/pull-request

authors: thegreatluke victoriadrake

repo: victoriadrake/hugo-theme-introduction


text:
Update zio, zio-streams, zio-test, ... to 2.1.13

About this PR
📦 Updates

dev.zio:zio
dev.zio:zio-streams
dev.zio:zio-test
dev.zio:zio-test-magnolia
dev.zio:zio-test-sbt

from 2.1.12 to 2.1.13
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 56.67%. Comparing base (7e37845) to head (5c00a5c).
Report is 123 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #533      +/-   ##
==========================================
- Coverage   56.84%   56.67%   -0.18%
==========================================
  Files          35       38       +3
  Lines        1752     1775      +23
  Branches      233      237       +4
==========================================
+ Hits          996     1006      +10
- Misses        756      769      +13

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

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests

Superseded by #540.

authors: codecov-commenter scala-steward

repo: vigoo/desert


text:
Using TableViewCell as Subview

Hi,
I use Storyboards, and I have a prototype cell defined in a TableView. It's a header cell that summarises the rest of the table.
I am wanting to use this prototype cell as the subview of a SCLAlertView, i.e. so that it shows the summary of the table on the view underneath the alertView.
I tried using:
let cell = tableView.dequeueReusableCell(withIdentifier: "header") as! PayHeaderTVC

and then modifying the cell's properties:
        cell.lblItemsMarked.text = "\(itemsMarkedCount)"
        cell.lblTotalMarking.text = markingTotal.Currency()

and then finally calling alertView.customSubview = cell, but when the alertView shows, the subview does not.
Any ideas?
Cheers
Saf

UITableViewCell is not supposed to be used outside of UITableView. You can create your own custom view and use it as a subview of your cell's contentView and as alertView.customSubview (not the same instance of course, two different instances).

authors: algrid sarfrazb

repo: vikmeup/SCLAlertView-Swift


text:
Add button to get ABI while viewing an account card

Next to the account history button

hi can i clone full code for rework another blockchain?

hi can i clone full code for rework another blockchain?

authors: YudaAdiPratama vikxx


text:
🛑 Booking is down

In 1ff0739, Booking ($SITE_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Booking is back up in 2395935 after 7 minutes.

repo: villekulla-nma/monitor-booking


text:
[vim9script] Weird class X not found on interface X error

Steps to reproduce
To reproduce, source this script:
vim9script

class Parent
  public this.value = 0
endclass

def Test_get_parent_member()
  var parent = Parent.new(9)
  assert_equal(9, parent.value)
enddef

class Child extends Parent
endclass

Test_get_parent_member()

Running the above script results in class Parent not found on interface Parent. If the definition of the Child class is removed, then the code runs fine.
Expected behaviour
The code should run fine and the test should not fail.
Version of Vim
9.0.1321
Environment
macOS 13.2
Apple Terminal
xterm-256color
ZSH 5.8.1
Logs and stack traces
No response

I think this issue is fixed by https://github.com/vim/vim/commit/74cc13cc402fa4df9033fbbc0643b1b403525950.  Can you try to reproduce this issue with the latest Vim version?

Thanks, indeed the issue appears to be fixed!

authors: lifepillar yegappan

repo: vim/vim

license: Vim


text:
Add eob to 'fillchars'

Is your feature request related something that is currently hard to do? Please describe.
I want to hide the tildes after the last line of buffers.
Setting EndOfBuffer highlight to show fg and bg in same color is a way, but in some terminal emulators with background transparency which is not applied to texts (e.g. iTerm2), the tildes come back visible.
This was discussed in neovim/neovim#2067, and now NeoVim has option eob for 'fillchars'. I want Vim to have same ability.
Describe the solution you'd like
Add eob option to 'fillchars' to change the tildes, that is compatible with NeoVim.
Describe alternatives you've considered
Adding option to hide tildes?

I'm verry sorry this is duplicate of #3820. I've only searched with listchars.
closing.


text:
WIP: Update menu translations for Italian / Italiano

Developers who know the language are now needed to help complete this PR.  The menu translation items template is generated by https://github.com/adaext/vim-menutrans-helper. I've scanned all the menu items and created a fairly completed template. It haven't been updated for years, many new items would be added except items inmenu.vim.

@chrisbra this is already translated

This seems to be maschine translated with some errors. I am not including this. Closing.

authors: adaext chrisbra ronin49


text:
Make autoload/dist/vim.vim work properly when lacking vim9script support

:return cannot be used outside of :function in older Vims lacking Vim9script support or in Neovim, even when evaluation is being skipped in the dead :else branch.
Instead, use the pattern described in :h vim9-mix, which uses :finish to end script processing before it reaches the Vim9script stuff.

yeah, thanks. Makes sense.

authors: chrisbra seandewar


text:
Update span create or get from ctx

make sure that the span can be changed in user code by getting the active span from the context.
All changes are added based on the origin of the span(cox or new)

Not going to push this code since I've changed it in a commit to main directly 035f3c4a37e3a84adeb357b343a7ae3a4f0ade6a

repo: vincentfree/opentelemetry-http


text:
Importing Application Error

Hi Vincent,
Thought I would give this a try and am struggling to import the application into my environment.  I get the following error:

Regards

Hi Vincent : I re-downloaded the APEX SQL file and now seems to be working.  Very odd.
Apologies

repo: vincentmorneau/apex-pwa


text:
[RFC-15][HUDI-1325] Merge updates of unsynced instants to metadata table

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
There can be the possibility that the dataset timeline and the metadata table timeline become out of sync. When trying to read from the metadata table while the timeline is out of sync you would get incorrect values for getAllFilesInPartition and getAllPartitionPaths.
This change provides a way to overcome this scenario by reading unsynced timeline instants and merging it with existing metadata table records to get the most up to date state of the file system
JIRA: https://issues.apache.org/jira/browse/HUDI-1325
Brief change log

The logic of converting timeline metadata to metadata table records was directly tied to the commit phase in FSBackedMetadataWriter. Refactored this logic to a utility class HoodieTableMetadataTimelineUtil
Created a scanner HoodieMetadataMergedInstantRecordScanner which handles conversion of timeline instants to metadata records and merges results
Added third step in FSBackedTableMetadata.getMergedRecordByKey which uses the new scanner mentioned to fetch the HoodieRecord associated with the desired key from the unsynced timeline instants and merge it with the record from the metadata table
When converting rollback operation to metadata table records there was logic that re-read from the metadata table to ensure any files being deleted as part of roll back existed.

// Rollbacks deletes instants from timeline. The instant being rolled-back may not have been synced to the
// metadata table. Hence, the deleted filed need to be checked against the metadata.

This doesn't make sense since all instants are processed in serial order so there would never be the case where a rollback was being written before an instant earlier on the timeline was already synced. Removed this logic because it created circular dependency when implementing timeline merging

Changed the validate metadata step in tests to use the metadata reader FSBackedTableMetadata. By default when metadata writer FSBackedTableMetadataWriter is initialized it syncs all instants to the metadata table. By using the reader we can simulate metadata table being out of sync.
Modified initMetaClient in test base class to allow table type to be passed in since table type is always set as COPY_ON_WRITE if using this method to initialize the meta client

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@rmpifer I was looking for this in apache/hudi :). and totally missed that it's here.
Can we retarget this to apache/hudi/rfc-15?

Codecov Report

Merging #6 (75a3352) into rfc-15 (7f84b12) will decrease coverage by 0.06%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             rfc-15       #6      +/-   ##
============================================
- Coverage     43.79%   43.73%   -0.07%
  Complexity     3379     3379
============================================
  Files           573      575       +2
  Lines         24400    24438      +38
  Branches       2445     2449       +4
============================================
  Hits          10687    10687
- Misses        12692    12730      +38
  Partials       1021     1021

Flag
Coverage Δ
Complexity Δ

hudicli
27.48% <0.00%> (+0.35%)
0.00 <0.00> (ø)

hudiclient
24.74% <0.00%> (+0.41%)
0.00 <0.00> (ø)

hudicommon
51.64% <0.00%> (-0.95%)
0.00 <0.00> (ø)

hudihadoopmr
33.05% <ø> (ø)
0.00 <ø> (ø)

hudispark
67.19% <ø> (ø)
0.00 <ø> (ø)

huditimelineservice
64.43% <ø> (ø)
0.00 <ø> (ø)

hudiutilities
69.38% <ø> (ø)
0.00 <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ
Complexity Δ

...hudi/metadata/HoodieBackedTableMetadataWriter.java
4.01% <0.00%> (+1.34%)
4.00 <0.00> (ø)

...pache/hudi/metadata/HoodieBackedTableMetadata.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...data/HoodieMetadataMergedInstantRecordScanner.java
0.00% <0.00%> (ø)
0.00 <0.00> (?)

...hudi/metadata/HoodieTableMetadataTimelineUtil.java
0.00% <0.00%> (ø)
0.00 <0.00> (?)

authors: codecov-io rmpifer vinothchandar

repo: vinothchandar/hudi


text:
Unable to run pypdfocr.exe ver 0.9.0

Hi,
I am unable to run pypdfocr.exe 0.9.0 on Windows 7 x64. This is the error message that I get:
This version of pypdfocr.exe is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher.

I have tested on windows 7 x64 and it runs fine for me.  Are you sure you're on 64-bit?  Have you tried an older version of pypdfocr (like 0.8.3) and does that also not work?

Closed, unable to reproduce

authors: violetsolutions virantha

repo: virantha/pypdfocr


text:
Request For Cardboard Button On Player Screen

Description
Hello Viro team,
I would like to ask for a feature that already existing in Google VR Video (Or in youtube). There you will see that there is a cardboard button (a cardboard icon ^_^ ).
The cardboard button/icon will display when the video play in mono mode (still 360 and users move their phone around to see), user click on it to switch to VR mode. Does it sound promising?
Or you think that tapping on the screen to switch mode is good enough?
Thanks.

Hello @dthian ,
What do you think about this request?

The cardboard button/icon will display when the video play in mono mode (still 360 and users move their phone around to see), user click on it to switch to VR mode. Does it sound promising?

The above sounds like an awesome video application that developers can build.  Sure, you can use the Viro platform sdk to build this experience - we should be able to support this case.

What do you think about this request?

Unfortunately, Viro is not a dev shop at the moment - our main focus is to add support and fix issue that are found on the platform, and we are not an "applications building team", but more like a "Frameworks team". One thing you can try is to reach out to other devs in our Slack channel and see if they might be willing to build such an application for you.

Thank @dthian for your information.

authors: dthian tuananhcwrs

repo: viromedia/viro


text:
Change CLI backend option to ValueEnum

Change the CLI to receive backends as a positional
argument with values listed in a ValueEnum.
Current '--help' output:
A virtio-sound device using the vhost-user protocol.

Usage: vhost-user-sound --socket <SOCKET> --backend <BACKEND>

Options:
      --socket <SOCKET>  vhost-user Unix domain socket path
      --backend <BACKEND>  audio backend to be used [possible values:
      null, pipewire, alsa]
  -h, --help             Print help
  -V, --version          Print version

If a wrong backend is given, it give hints:
$ cargo run -- --socket /tmp/sound.sock --backend nul
error: invalid value 'nul' for '<BACKEND>'
  [possible values: null, pipewire, alsa]

  tip: a similar value exists: 'null'

Add a test to verify (minimally) the backend argument.
Last commit adds rstest crate to have multiple cases in a parametrized test.
Last commit outputs:
running 4 tests
test tests::test_cli_backend_arg::case_2_pipewire ... ok
test tests::test_cli_backend_arg::case_3_alsa ... ok
test tests::test_cli_backend_arg::case_1_null_backend ... ok
test tests::test_sound_config_setup ... ok

test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

But if the dependency is not desired, the commit can be omitted.

Fixed the build issue by tweaking the conditional compilation of the cfg attribute for the match block:
        #[cfg(not(all(
            feature = "null-backend",
            feature = "pw-backend",
            feature = "alsa-backend"
        )))]
        _ => Err(Error::AudioBackendNotSupported),

Does not look great, but I couldn't come with a cleaner correct option. Hopefully it is ok though :)

Fixed the build issue by tweaking the conditional compilation of the cfg attribute for the match block:
        #[cfg(not(all(
            feature = "null-backend",
            feature = "pw-backend",
            feature = "alsa-backend"
        )))]
        _ => Err(Error::AudioBackendNotSupported),

Does not look great, but I couldn't come with a cleaner correct option. Hopefully it is ok though :)

What about as was before this series, I mean applying this patch:
diff --git a/crates/sound/src/audio_backends.rs b/crates/sound/src/audio_backends.rs
index bd13c37..dea74f9 100644
--- a/crates/sound/src/audio_backends.rs
+++ b/crates/sound/src/audio_backends.rs
@@ -17,13 +17,7 @@ use self::alsa::AlsaBackend;
 use self::null::NullBackend;
 #[cfg(feature = "pw-backend")]
 use self::pipewire::PwBackend;
-use crate::{device::ControlMessage, stream::Stream, BackendType, Result};
-#[cfg(not(all(
-    feature = "null-backend",
-    feature = "pw-backend",
-    feature = "alsa-backend"
-)))]
-use crate::Error;
+use crate::{device::ControlMessage, stream::Stream, BackendType, Error, Result};

 pub trait AudioBackend {
     fn write(&self, stream_id: u32) -> Result<()>;
@@ -64,11 +58,6 @@ pub fn alloc_audio_backend(
         Pipewire => Ok(Box::new(PwBackend::new(streams))),
         #[cfg(feature = "alsa-backend")]
         Alsa => Ok(Box::new(AlsaBackend::new(streams))),
-        #[cfg(not(all(
-            feature = "null-backend",
-            feature = "pw-backend",
-            feature = "alsa-backend"
-        )))]
         _ => Err(Error::AudioBackendNotSupported),
     }
 }

Okay, in this case we will have warning: unreachable pattern, so I think your solution is the only one available, or we should suppress the warn(unreachable_patterns)

Okay, in this case we will have warning: unreachable pattern, so I think your solution is the only one available, or we should suppress the warn(unreachable_patterns)

I think it might be better to suppress the warning for that line by putting a nice comment explaining why. Otherwise every time we add a backend we have to edit these lines.
WDYT?

I think it might be better to suppress the warning for that line by putting a nice comment explaining why. Otherwise every time we add a backend we have to edit these lines.
WDYT?

I was tempted of doing that as I was trying to make it work. But I wanted to present the other option first.
I think suppressing the warning is best for this case, it is justified and will make it more maintainable. Let's go for that!

Another option now that I think of it, is to have the enum variants conditional in the declaration.

Another option now that I think of it, is to have the enum variants conditional in the declaration.
Nah, it complicates the no-features case. But it may be a nice change if we ever tweak the compiler to use at least the Null backend in any case (if it is possible).
I'll leave it as is.

Another option now that I think of it, is to have the enum variants conditional in the declaration.

Do you mean in pub enum BackendType ?
It could make sense.
Should we also avoid the default?

Do you mean in pub enum BackendType ?
It could make sense.
Should we also avoid the default?

Yes, the BackendType. And yes, we would have to avoid the default. That would've been fine, but
also it would leave the enum with no values with no-features case. And that makes some parts of
the code unreachable...
Kindof a mess to fix. But also proves that is not a good idea to compile with no features I guess :)
Let's keep it in the back of our heads for the future.

Do you mean in pub enum BackendType ?
It could make sense.
Should we also avoid the default?

Yes, the BackendType. And yes, we would have to avoid the default. That would've been fine, but also it would leave the enum with no values with no-features case. And that makes some parts of the code unreachable... Kindof a mess to fix. But also proves that is not a good idea to compile with no features I guess :)

I'm start thinking the same :-)
So maybe we should always compile the null backend.
Disable it will save just few bytes, nothing more since it doesn't have any dependency.

Let's keep it in the back of our heads for the future.

Sure, feel free to open an issue here for tracking it.

Another option now that I think of it, is to have the enum variants conditional in the declaration.

Nah, it complicates the no-features case. But it may be a nice change if we ever tweak the compiler to use at least the Null backend in any case (if it is possible). I'll leave it as is.

However, I think it makes sense, partly because now we print all as possible values, even if not enabled.
$ cargo build --no-default-features --features=null-backend
$ target/debug/vhost-user-sound --socket /tmp/sock --backend gstreamer
error: invalid value 'gstreamer' for '--backend <BACKEND>'
  [possible values: null, pipewire, alsa]

For more information, try '--help'.

But I agree that we can do it later by removing the feature to disable null-backend to simplify the code.

However, I think it makes sense, partly because now we print all as possible values, even if not enabled.

Right, that is a good point.

But I agree that we can do it later by removing the feature to disable null-backend to simplify the code.

I don't mind handling this myself in a follow-up PR :)

authors: aesteve-rh stefano-garzarella

repo: virtio-sound/vhost-device


text:
Viosock: Remove Coinstaller Stuff from the INF File

The driver is installed in the Driver Store (DIRID 13) instead of the System Drivers directory (DIRID 12).

Is the protocol not registered?

[VirtioSocket_Device_CoInstaller_AddReg]
HKR,,CoInstallers32,0x00010000,"viosocklib.dll,ViosockCoInstaller"
==>
The old INFs  will register the protocol through the ViosockCoInstaller interface.

[VirtioSocket_Device_CoInstaller_AddReg] HKR,,CoInstallers32,0x00010000,"viosocklib.dll,ViosockCoInstaller" ==> The old INFs will register the protocol through the ViosockCoInstaller interface.

Ah, OK, I missed that. I will improve the PR.

@MartinDrab
The build failed
C:\EWDK11\Program Files\Microsoft Visual Studio\2019\BuildTools\MSBuild\Microsoft\VC\v160\Microsoft.CppBuild.targets(436,5): error MSB8013: This project doesn't contain the Configuration and Platform combination of Debug|Win32. [C:\workspace\VirtIO-EWDK-11-21H2-SDV\viosock\installer\viosock-installer.vcxproj]

@MartinDrab https://learn.microsoft.com/en-us/windows-hardware/drivers/install/using-an-extension-inf-file did you try to check "Extension INFs"?

@MartinDrab https://learn.microsoft.com/en-us/windows-hardware/drivers/install/using-an-extension-inf-file did you try to check "Extension INFs"?

I came across them several days ago when working on another (unrelated) issue. I did not have time to look at them in more detail and possibly use them, however, I hope to get to it shortly.

@MartinDrab
We merge https://github.com/virtio-win/kvm-guest-drivers-windows/pull/1087 to switch to the new EWDK. For now, we just disable viosock build for Win11.

@MartinDrab We merge #1087 to switch to the new EWDK. For now, we just disable viosock build for Win11.

OK. I hope to work on this PR shortly and finish it. I apologize for this inconvenience.

@MartinDrab We merge #1087 to switch to the new EWDK. For now, we just disable viosock build for Win11.

OK. I hope to work on this PR shortly and finish it. I apologize for this inconvenience.

Not a problem. Disabling the build is not a complicated task. This is more problem for companies that release viosock.

@MartinDrab We merge #1087 to switch to the new EWDK. For now, we just disable viosock build for Win11.

OK. I hope to work on this PR shortly and finish it. I apologize for this inconvenience.

Not a problem. Disabling the build is not a complicated task. This is more problem for companies that release viosock.

Hello,
I hope I overcame issues regarding the co-installer and the socket WSP installation from the INF file. In the end, I decided to separate the WSP installation into a special service since it is possible to install and start it from the INF file. Other possibilities seem to be problematic:

WDK complains about the co-installer even when it is used only on old versions of Windows 10,
the AddSoftware directive is not supported on old versions of Windows 10.

I hope this should finally pass the tests and build successfully also with new (E)WDKs.

@MartinDrab
Thanks for your work.
Unfortunately, the build failed again.
Please also revert https://github.com/virtio-win/kvm-guest-drivers-windows/commit/f7646006430f40014373cc747bb75a0d7f2cf1c2 and update buildAll.bat (https://github.com/virtio-win/kvm-guest-drivers-windows/commit/ad1aed4601ba937625263c54720fbf316685a3e5 disabled Win11 for viosock)
add rem NO WIN11 build for viosock for now
if errorlevel 1 goto :fail
call tools\build.bat viosock\sys\viosock.vcxproj "Win10_SDV Win11_SDV" %*
if errorlevel 1 goto :fail
call tools\build.bat viosock\wsk\wsk.vcxproj "Win10_SDV Win11_SDV" %*
if errorlevel 1 goto :fail
call tools\build.bat viosock\viosock-wsk-test\viosock-wsk-test.vcxproj "Win10_SDV Win11_SDV" %*

authors: MartinDrab YanVugenfirer kostyanf14 xuehuihui

repo: virtio-win/kvm-guest-drivers-windows


text:
Did not import style as expects

I think it is a bug of https://github.com/ant-design/babel-plugin-import .
import with alias:
import { TimePicker as ATimePicker} from 'ant-design-vue'

What it generated below. It does not processed by babel-plugin-import, it's not load-on-demand, and no style is loaded
__webpack_require__.r(__webpack_exports__);
/* harmony import */ var ant_design_vue__WEBPACK_IMPORTED_MODULE_0__ = __webpack_require__(/*! ant-design-vue */ \"./node_modules/ant-design-vue/dist/antd.min.js\");
/* harmony import */ var ant_design_vue__WEBPACK_IMPORTED_MODULE_0___default = /*#__PURE__*/__webpack_require__.n(ant_design_vue__WEBPACK_IMPORTED_MODULE_0__);
const autoImports = []

autoImports.push({fullName: 'AButton', tag: 'a-button', component: ant_design_vue__WEBPACK_IMPORTED_MODULE_0__[\"Button\"]})

autoImports.push({fullName: 'APagination', tag: 'a-pagination', component: ant_design_vue__WEBPACK_IMPORTED_MODULE_0__[\"Pagination\"]})

autoImports.push({fullName: 'AAffix', tag: 'a-affix', component: ant_design_vue__WEBPACK_IMPORTED_MODULE_0__[\"Affix\"]})

autoImports.push({fullName: 'ABreadcrumb', tag: 'a-breadcrumb', component: ant_design_vue__WEBPACK_IMPORTED_MODULE_0__[\"Breadcrumb\"]})

autoImports.push({fullName: 'AAutoComplete', tag: 'a-auto-complete', component: ant_design_vue__WEBPACK_IMPORTED_MODULE_0__[\"AutoComplete\"]})

autoImports.push({fullName: 'AInputNumber', tag: 'a-input-number', component: ant_design_vue__WEBPACK_IMPORTED_MODULE_0__[\"InputNumber\"]})

autoImports.push({fullName: 'ADatePicker', tag: 'a-date-picker', component: ant_design_vue__WEBPACK_IMPORTED_MODULE_0__[\"DatePicker\"]})

autoImports.push({fullName: 'ATimePicker', tag: 'a-time-picker', component: ant_design_vue__WEBPACK_IMPORTED_MODULE_0__[\"TimePicker\"]})

autoImports.push({fullName: 'ACalendar', tag: 'a-calendar', component: ant_design_vue__WEBPACK_IMPORTED_MODULE_0__[\"Calendar\"]})

autoImports.push({fullName: 'AXyz', tag: 'a-xyz', component: ant_design_vue__WEBPACK_IMPORTED_MODULE_0__[\"Xyz\"]})

autoImports.push({fullName: 'AAbc', tag: 'a-abc', component: ant_design_vue__WEBPACK_IMPORTED_MODULE_0__[\"Abc\"]})

/* harmony default export */ __webpack_exports__[\"default\"] = (function (Component) {
  const c = Component.options.components
  autoImports.forEach(i => {
    if (c[i.fullName] == null) c[i.fullName] = i.component
  })
});

Because the generated file was not processed by babel-plugin-import, so it not their bug.
const autoImports = []
import { Button as AButton } from 'ant-design-vue'
autoImports.push({fullName: 'AButton', tag: 'a-button', component: AButton})
import { Pagination as APagination } from 'ant-design-vue'
autoImports.push({fullName: 'APagination', tag: 'a-pagination', component: APagination})
import { Affix as AAffix } from 'ant-design-vue'
autoImports.push({fullName: 'AAffix', tag: 'a-affix', component: AAffix})
import { Breadcrumb as ABreadcrumb } from 'ant-design-vue'
autoImports.push({fullName: 'ABreadcrumb', tag: 'a-breadcrumb', component: ABreadcrumb})
import { AutoComplete as AAutoComplete } from 'ant-design-vue'
autoImports.push({fullName: 'AAutoComplete', tag: 'a-auto-complete', component: AAutoComplete})
import { InputNumber as AInputNumber } from 'ant-design-vue'
autoImports.push({fullName: 'AInputNumber', tag: 'a-input-number', component: AInputNumber})
import { DatePicker as ADatePicker } from 'ant-design-vue'
autoImports.push({fullName: 'ADatePicker', tag: 'a-date-picker', component: ADatePicker})
import { TimePicker as ATimePicker } from 'ant-design-vue'
autoImports.push({fullName: 'ATimePicker', tag: 'a-time-picker', component: ATimePicker})
import { Calendar as ACalendar } from 'ant-design-vue'
autoImports.push({fullName: 'ACalendar', tag: 'a-calendar', component: ACalendar})
import { Xyz as AXyz } from 'ant-design-vue'
autoImports.push({fullName: 'AXyz', tag: 'a-xyz', component: AXyz})
import { Abc as AAbc } from 'ant-design-vue'
autoImports.push({fullName: 'AAbc', tag: 'a-abc', component: AAbc})

export default function (Component) {
  const c = Component.options.components
  autoImports.forEach(i => {
    if (c[i.fullName] == null) c[i.fullName] = i.component
  })
}


text:
NetworkTransform with clientAuthority set true cannot be moved by server when no client has authority

When you have a game object with a NetworkTransform with clientAuthority set to true, it can only be moved by clients with authority. When no client has authority (i.e. the server has authority), it cannot be moved by the server.
Is this intentional behaviour?
I would expect the server to be able to move the object when no client has authority. This was the behaviour in previous versions of Mirror.
I believe the issue is in NetworkTransformBase where the serverBuffer is used when clientAuthority is set and current client has no authority on this line.
Demonstration Project
I've set up a simple project with the smallest amount of code. There's only empty player objects and a cube that moves vertically when the server has authority.
Start up a build as the client and the unity editor as host. The cube is being moved automatically by the server (when connection to client is null).
When clientAuthority on the Network Transform is checked then the cube stops because the server is not able to move the cube (that's the bug).
Uncheck clientAuthority and the cube moves.
https://user-images.githubusercontent.com/1922279/172066366-6160c7be-ac2b-482f-afac-6551ccd1ad4c.mp4
Desktop (please complete the following information):

OS: Windows
Build target: Windows
Unity version: 2021.1.25f
Mirror branch: release version 66

Many thanks in advance!

FYI I don't need tis answering anymore but leaving for posterity.

Hello
I updated Mirror in a project and having that problem now too. I also figured out that moving objects around on the multiple clients has problems. It seams that they have different last states that replace the object when the authority is lost. That leads to the problem that objects are not on the same position on the different devices.
@brainwipe  May i ask how you solved the problem?
Would it make sense to turn on and off the clientAuthority on all clients+server at runtime when needed?
Mirror Version 66.0.9
Unity 2021.3.1f1
Tested devices: Mac Book, Windows 10, Oculus Quest 2


text:
NetworkTransform should sync Scale

Seeing as how NetworkTransform is meant as an easy way to sync the Transform properties of a GameObject, it seems odd that Position and Rotation were included, but Scale was left out.

I will need this in my game eventually. I'll try to push it with a ClientRPC. Can probably use existing interpolation pretty easy.

bump for this 👍

@Reelix @davoodkharmanzar should be doable. please submit a pull request if you want that change and we will merge it :)

authors: AnthonE Reelix davoodkharmanzar vis2k


text:
Allow multiple host checks

This is based on @Forever-Young's work in https://github.com/vishnubob/wait-for-it/pull/22.  I just rebased on top of latest.

Hey @bwolfe
You can use the Wait4X, It's already supported multiple host checking.
Example:
wait4x tcp 1.1.1.1:80 1.1.1.1:53 --log-level debug

authors: atkrad bwolfe

repo: vishnubob/wait-for-it


text:
model not removed from aimodels-lock.json when removed

I think in this case we remove the model, and the credentials are independent and would remain

confirmed

repo: visioninit/aimm


text:
TypeError: Cannot read private member from an object whose class did not declare it when I use setData()

<template>

</template>

I use vue3 + vis-network. When I use on to register the event, I hope I can setData when the event is triggered. This problem occurs.
I tried adding nextTick approach
  canvas.value?.setData(newData);

 ↓

  canvas.value?.on('click', (params) => {
            console.log(params);
            nextTick(() => {
                canvas.value?.setData(newData);
            });
        })

error message from
Uncaught (in promise) TypeError: Cannot read private member from an object whose class did not declare it
at __classPrivateFieldGet (weak-map.js:1:18)
at Proxy.clear2 (selection-accumulator.ts:138:5)
at Proxy.unselectAll (SelectionHandler.js:369:32)
at Network.setData (Network.js:398:25)
at VisDDD.vue:27:23
at runtime-core.esm-bundler.js:2679:88
at callWithErrorHandling (runtime-core.esm-bundler.js:158:18)
at callWithAsyncErrorHandling (runtime-core.esm-bundler.js:166:17)
at hook.__weh.hook.__weh (runtime-core.esm-bundler.js:2659:19)
at flushPostFlushCbs (runtime-core.esm-bundler.js:325:40)
became
Uncaught (in promise) TypeError: Cannot read private member from an object whose class did not declare it
at __classPrivateFieldGet (weak-map.js:1:18)
at Proxy.clear2 (selection-accumulator.ts:138:5)
at Proxy.unselectAll (SelectionHandler.js:369:32)
at Network.setData (Network.js:398:25)
at VisDDD.vue:30:31
I also got this from Stackoverflow
https://stackoverflow.com/questions/76961106/is-visjs-network-supported-by-vue3
Saw the same question
I'm facing a bit of a problem and I'm hoping someone can lend me a hand. Would really appreciate your help. Thanks a ton!

Do not use ref, simply define a variable using let or const, and there will be no error accessing private member variables or methods

authors: Wuwuyiaewu humingxian

repo: visjs/vis-network


text:
Check ports in TrackingServer app

in v0.9.8, Layers app is not getting connection to tracking server --> mayber due to port / protocol issues ?

issue was related to missing address property when request to start broadcast --> fixed in layers app

repo: visualengineers/reflex


text:
ensure status in Draft|Published

ensure only Draft|Published are shown
WRT https://github.com/zazuko/cube-creator/wiki/LINDAS-Specifics#needed-attributes-that-a-cube-shows-up-on-visualizeadminch
there are rare cases with different status i.e. https://s.zazuko.com/m6iuJB which shouldn't be shown
nb: this PR also makes results more consistent with https://github.com/visualize-admin/visualization-tool/blob/eef59af39594123bacc535484df6654550830fa1/app/rdf/queries.ts#L69-L74
cc @bprusinowski

Thanks @Rdataflow, LGTM! Side note: I think this situation technically shouldn't happen, looking at the below screenshot? Maybe it could be possible with some custom pipeline? 🤔

@bprusinowski it's likely due to a combination of legacy project and code in C-C that doesn't expire deprecated cubes properly :+1:

authors: Rdataflow bprusinowski

repo: visualize-admin/visualization-tool


text:
Allow overriding task data and taskrc file on the command line

Currently, taskrc file location is overridable in vit config.ini file (and indirectly via TASKRC envvar)
[taskwarrior]

# Full path to the Taskwarrior configuration file. Tilde will be expanded to the user's home directory.
# NOTE: This setting is overridden by the TASKRC environment variable.
#taskrc = ~/.taskrc

TaskWarrior gives two ways to override config file and data location, via command-line or environment:

Config file
Data location

Command-lineargument
rc:config_file
rc.data.location:data_directory

Environmentvariable
TASKRC=config_file
TASKDATA=data_directory

See CONFIGURATION FILE AND OVERRIDE OPTIONS section in task(1) manpage for details.
Overriding manually the environment via TASKRC and TASKDATA (used by TaskWarrior) before launching vit works currently, and shown data/used config are correct.
What would be useful it to be able to specify those via vit command line, as task does:

task rc.data.location:alternateDataLocationDirectory rc:alternateTaskrcConfFile ...

This would allow for instance to have completely separate environments, without having to rely on contexts (where it's a soft separation).
Linked issues: #257 and #235

See https://github.com/scottkosty/vit/issues/257 for the suggestion there, perhaps a single --default-args switch?

See #257 for the suggestion there, perhaps a single --default-args switch?

Yes, a --default-args would do, to pass to every taskwarrior command.
Care should be taken to respect precedence of options, so they are applied by increasing precedence: config.ini -> environment variable -> command line option
E.g. taskrc option in config.ini -> TASKRC -> --default-args rc:...

I've abandoned the idea of a --default-args approach, too complicated.
I've also abandoned the idea of any VIT-specific overrides for task data, see https://github.com/vit-project/vit/issues/257#issuecomment-691721253 for more.
I'd still consider adding a CLI arg that would allow overriding the task data location -- this is reasonably straightforward, compliments the existing config file option, and allows for more flexibility for those using more complex setups.

authors: fdela thehunmonkgroup

repo: vit-project/vit


text:
I have jQuery, Bootstrap, jQuery-ui which one should I use?

Hi, with jQuery + bootstrap + jQuery-ui (all are latest versions at time of writing), the following errors were encountered for each package used:
Bootstrap error: popover is not defined
jQuery error: $.fn.editableutils is undefined
jQuery-ui error: $.fn.editableutils is undefined
Can you kindly advise which package I should use?
The initialization used is very simple:
$('#edit').editable();
P.S. it works when I remove jQuery-ui, I have no idea why?

I just have had the same error.
Solution was to move the wysihtml5 files (meaning -  and

Basically all css should be loaded first.
Then the javascript libraries.
Not mixed.
And - see jQuery - the jquery.js has to be the first, then the jquery-ui.
Same goes for bootstrap.

authors: BlueManLine clw osworx

repo: vitalets/x-editable


text:
Manifest file is not put in the correct location

I am using Laravel + Vue to build an application. In order to get the service worker to generate in the correct location I am using the following configuration.
{
    injectRegister: 'null',
    outDir: 'public/',
    scope: '/',
    base: '/',
    buildBase: '/',
    workbox: {
        globPatterns: ['**/*.{js,css}'],
        navigateFallback: null,
    },
}

However this leaves the manifest.webmanifest file in /public/build/manifest.webmanifest.
I tried adding the manifest.publicPath option to the config but it doesn't work and when doing a global search of the source code I don't see any usages of it.
How would I either get the manifest.webmanifest file to be put in /public/ instead of /public/build/ or get the file url in the sw.js to use /build/manifest.webmanifest instead of /manifest.webmanifest?

@userquin I do see that there are some weird settings to the laravel plugin but it seems like the manifest file is getting put in the wrong location.
Do you have any suggestions?

@likeadeckofcards the laravel plugin is setting the Vite outDir to that folder, check my comment in this issue https://github.com/vite-pwa/vite-plugin-pwa/issues/467#issuecomment-1427998051

authors: likeadeckofcards userquin

repo: vite-pwa/vite-plugin-pwa


text:
feat: upgrade mdx

This gives us type safety for MDX options.
Not sure if we want to wait until MDX 2.0 is officially released?

Whoops, I forgot to check on the status of #6 :)

repo: vitejs/vite-plugin-react-pages


text:
Automated releases

Automated releases save us the hassle of manually cutting releases and updating a changelog, and users get the latest changes as soon as they're merged.
More info: https://intuit.github.io/auto/

All change logs are already automated. Publishing each package is as simple as running yarn release. I don't trust automated releases.

All change logs are already automated. Publishing each package is as simple as running yarn release. I don't trust automated releases.

What's there to not trust?
Opening a terminal, navigating to your vite clone, and running yarn release is enough friction to discourage you from doing it every time you merge a PR. And what if a maintainer without publish privileges merges a PR while you're focused on other projects? Ideally, fixes and features are immediately available once merged, so users don't have to wait arbitrary amounts of time.

What's there to not trust?
Opening a terminal, navigating to your vite clone, and running yarn release is enough friction to discourage you from doing it every time you merge a PR. And what if a maintainer without publish privileges merges a PR while you're focused on other projects? Ideally, fixes and features are immediately available once merged, so users don't have to wait arbitrary amounts of time.

That's exactly what I don't like: the fact that things can be released without me being aware of it.

That's exactly what I don't like: the fact that things can be released without me being aware of it.

repo: vitejs/vite


text:
PostCSS dependencies are not registered correctly in some cases

~Describe the bug~
~It's hard to explain this one without referring to the reproduction: https://github.com/bradlc/vite-module-bug~
~In this example main.js is registered as a PostCSS dependency, but editing it does not trigger a CSS rebuild. I am not too familiar with the vite codebase but the issue seems to be related to this section of code:~
const depModules = new Set(
  [...deps].map((file) => moduleGraph.createFileOnlyEntry(file))
)

~Should this be checking for an existing module, something like this?~
const depModules = new Set(
  [...deps].map((file) => moduleGraph.getModuleById(file) ?? moduleGraph.createFileOnlyEntry(file))
)

~Again, I am not familiar with the code so I might be way off here, but this change seemed to help in my testing.~
~Reproduction~
~https://github.com/bradlc/vite-module-bug~
Describe the bug
The above example seems to have been fixed by e048114 but the issue is still preset for .vue files.
When registering a .vue file as a PostCSS dependency the CSS is not rebuilt when that file changes.
Reproduction
https://github.com/bradlc/vite-vue-bug
System Info
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
System:
  OS: macOS 11.2.3
  CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Memory: 489.48 MB / 32.00 GB
  Shell: 5.8 - /bin/zsh
Binaries:
  Node: 16.0.0 - /var/folders/qw/ffpg9q8n6sgdyqlt84m2pxmr0000gn/T/fnm-shell-8843510/bin/node
  Yarn: 1.22.10 - /var/folders/qw/ffpg9q8n6sgdyqlt84m2pxmr0000gn/T/fnm-shell-8843510/bin/yarn
  npm: 7.10.0 - /var/folders/qw/ffpg9q8n6sgdyqlt84m2pxmr0000gn/T/fnm-shell-8843510/bin/npm
Browsers:
  Chrome: 91.0.4472.77
  Chrome Canary: 93.0.4536.0
  Firefox: 88.0.1
  Safari: 14.0.3
  Safari Technology Preview: 14.2
npmPackages:
  vite: ^2.3.7 => 2.3.7

Used package manager: npm

Quick follow-up after a bit more testing: the same issue occurs when registering .vue files as dependencies, but the small change I made (moduleGraph.getModuleById(file)) did not help in that case. Perhaps Vue modules are more complex?

I believe this same issue is present for svelte files in sveltekit. Having issues getting JIT working with TailwindCSS in SvelteKit.

I believe this same issue is present for svelte files in sveltekit. Having issues getting JIT working with TailwindCSS in SvelteKit.

@joshpierce The problem had been logged in the tailwindcss's document, use TAILWIND_MODE=watch while using JIT mode. hope helps.

The updated repro works fine with latest dep versions and actual Tailwind JIT also seems to be working just fine with Vue files. Closing.

authors: beetaa bradlc joshpierce yyx990803


text:
builtin-modules doesn't include fs/promises causing vite failing to recognize builtin module

Describe the bug
fs/promises isn't included in the array given by builtin-modules package but it is in import { builtinModules } from 'module';:

This cause Vite to give this error:
Failed to resolve import "fs/promises" from "src\routes\api\get-file-content.ts". Does the file exist?
Error: Failed to resolve import "fs/promises" from "src\routes\api\get-file-content.ts". Does the file exist?
    at formatError (C:\workspace\m7d\vite\packages\vite\dist\node\server\pluginContainer.js:173:46)
    at TransformContext.error (C:\workspace\m7d\vite\packages\vite\dist\node\server\pluginContainer.js:169:19)
    at normalizeUrl (C:\workspace\m7d\vite\packages\vite\dist\node\plugins\importAnalysis.js:126:26)
    at async TransformContext.transform (C:\workspace\m7d\vite\packages\vite\dist\node\plugins\importAnalysis.js:259:57)
    at async Object.transform (C:\workspace\m7d\vite\packages\vite\dist\node\server\pluginContainer.js:374:30)
    at async Object.transformRequest (C:\workspace\m7d\vite\packages\vite\dist\node\server\transformRequest.js:122:29)
    at async instantiateModule (C:\workspace\m7d\vite\packages\vite\dist\node\ssr\ssrModuleLoader.js:44:10)

Reproduction
Use import "fs/promises".
I'll provide a repo in the next days.
System Info
System:
    OS: Windows 10 10.0.19042
    CPU: (16) x64 AMD Ryzen 9 4900H with Radeon Graphics
    Memory: 17.22 GB / 31.42 GB
  Binaries:
    Node: 16.2.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 7.13.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1023.0), Chromium (91.0.864.59)
    Internet Explorer: 11.0.19041.1

Used Package Manager
npm
Logs
Failed to resolve import "fs/promises" from "src\routes\api\get-file-content.ts". Does the file exist?
Error: Failed to resolve import "fs/promises" from "src\routes\api\get-file-content.ts". Does the file exist?
    at formatError (C:\workspace\m7d\vite\packages\vite\dist\node\server\pluginContainer.js:173:46)
    at normalizeUrl (C:\workspace\m7d\vite\packages\vite\dist\node\plugins\importAnalysis.js:126:26)
    at async TransformContext.transform (C:\workspace\m7d\vite\packages\vite\dist\node\plugins\importAnalysis.js:259:57)
    at async Object.transform (C:\workspace\m7d\vite\packages\vite\dist\node\server\pluginContainer.js:374:30)
    at async Object.transformRequest (C:\workspace\m7d\vite\packages\vite\dist\node\server\transformRequest.js:122:29)
    at async instantiateModule (C:\workspace\m7d\vite\packages\vite\dist\node\ssr\ssrModuleLoader.js:44:10)

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

My temporary workaround is to specify fs/promises as external in the rollup options:
// vite.config.js
import { defineConfig } from "vite";

export default defineConfig({
  build: {
    rollupOptions: {
      external: ["fs/promises"],
    },
  },
});

chaunqisun's workaround doesn't seem to work with current SvelteKit ie- adding that config to svelte.config.js > kit > vite
still cannot import fs/promises without Svite throwing JSON error
@sveltejs/kit 1.0.0-next.1
svelte 3.42.6

authors: chuanqisun drschwabe raythurnevoid


text:
feat: environment api config options rework

Description
Building on top of:

https://github.com/vitejs/vite/pull/17753

For reference, before #17753, we had:

environment.config is the top level config (i.e. environment.config.root)
environment.options is the ResolvedEnvironmentOptions, equivalent to environment.config.environments[environment.name] (i.e. environment.options.resolve.conditions)

The motivation for #17753 is that environment.config being the top level config (the shared config instance that has the default values) is error prone environment.config.resolve.conditions should never be used. We discussed deprecating these defaults from ResolvedConfig and then removing them but that will take a while. We could make the type of environment.config more strict even if the default options are in the object, but there are other issues.
Having the top level config as environment.getTopLevelConfig() brought two things to the spotlight:

Most of the access for the config is for root and base. It would be good to have a more ergonomic way to access these instead of environment.getTopLevelConfig().root
We may make other config options per-environment in the future. Every time we do it, users will need to move from config.flag to environment.options.flag

This PR leaves environment.getTopLevelConfig() for when the shared instance is needed, and removes environment.options in favor of environment.config that has type ResolvedConfig & ResolvedEnvironmentOptions (maybe the type could be improved). It is currently implemented as:
    this.config = new Proxy(
      options as ResolvedConfig & ResolvedEnvironmentOptions,
      {
        get: (target, prop: keyof ResolvedConfig) => {
          if (prop === 'logger') {
            return this.logger
          }
          if (prop in target) {
            return this._options[prop as keyof ResolvedEnvironmentOptions]
          }
          return this._topLevelConfig[prop]
        },
      },
    )

This solves the two issues above and avoids confusion. environment.config always returns the configuration for this environment (it doesn't matter if the options are per-environment or shared). There are no longer issues with users accessing the defaults by mistake.
Notes: The PR also changes the ssr flag for EnvironmentOptions introduced at https://github.com/vitejs/vite/pull/16471/commits/90185f793247023e5d2464ff38fe8929582acf28 because it collides with the ssr object in ResolvedConfig. This was confusing in that commit already but I couldn't came up with a better name. We discussed with @sheremet-va and settled down on renaming it to consumer: 'client' | 'server' for now.

Proxy looks good to me. If environment.config.xxx would suffice for most of the cases, when would users need to go environment.getTopLevelConfig().xxx?

We still have many internal APIs that take a ResolvedConfig instead of an environment. So in that cases you can use environment.getTopLevelConfig() to get the shared instance. I think a lot of these APIs did that just because it was a more comfortable way to access root and base though, and probably later on they could be reworked. We have some other cases were we use the config as the key of a cache (the fs tree cache for example).
environment.getTopLevelConfig().xxx would not be a pattern we see used.


text:
test(css): fix postcss cleanid test

Description
fixes test of #7827
It was failing because #7807 minifies the content and comments were removed.
Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Thanks for the quick fix! ❤

authors: patak-dev sapphi-red


text:
JSDOM 23.0.0 atob endless recursion

Describe the bug
We have a test case that uses JSDOM and tests a function that calls "atob".
Since the upgrade to JSDOM 23.0.0, this test hangs.
Reproduction
A very short way to reproduce this is
import {JSDOM} from "jsdom";
import {populateGlobal} from "vitest/environments";

const jsdom = new JSDOM()
populateGlobal(global, jsdom.window)

atob("dGVzdAo=")

It yields the error
[DOMException [InvalidCharacterError]: The string to be decoded contains invalid characters.]

which is a bit misleading, as JSDOM throws this whenever the global "atob" throws any error.
Adding a 'console.log' statement to JSDOM's "atob" implementation shows that "atob" calls itself, resulting in an endless recursion.
System Info
System:
    OS: macOS 13.6
    CPU: (10) arm64 Apple M1 Pro
    Memory: 2.64 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.16.0 - ~/.asdf/installs/nodejs/18.16.0/bin/node
    Yarn: 1.22.19 - ~/.asdf/installs/nodejs/18.16.0/bin/yarn
    npm: 9.5.1 - ~/.asdf/plugins/nodejs/shims/npm
    bun: 0.6.7 - ~/.bun/bin/bun
  Browsers:
    Brave Browser: 118.1.59.117
    Chrome: 119.0.6045.159
    Safari: 17.0
  npmPackages:
    @vitest/ui: 0.34.6 => 0.34.6
    vite: 5.0.2 => 5.0.2
    vitest: 0.34.6 => 0.34.6

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Work-around for now is to provide atob global in test.setupFiles:
import { atob as NodeAtob } from "buffer";
globalThis.atob = NodeAtob;

Looks like JSDOM now relies on Node's atob: https://github.com/jsdom/jsdom/pull/3625/files#diff-b5cd5c96785357dc930f47c18b45d1626b467e8c16068720a31c0cfc0d8344d3L18

There is now a related issue at JSDOM: https://github.com/jsdom/jsdom/pull/3625

This is an issue with how Vitest overrides globals, so I would expect it to be fixed on our side. Happy-dom also had a similar problem with setTimeout at one point

As a workaround, You can also do this in your setup file.
globalThis.atob = (b64Str: string) => Buffer.from(b64Str, `base64`).toString(`binary`);

Reference

import { atob as NodeAtob } from "buffer";
globalThis.atob = NodeAtob;

This worked for me, but I have to put the line into a beforeAll block.

Fixed in da7949dcd056a00c39ed6a163562cedd463a6ca8

authors: AriPerkkio DercilioFontes nils4cosee sheremet-va

repo: vitest-dev/vitest


text:
fix(vitest): allow testing unandled rejection/exception

Description
Fixes #5796

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
[ ] Ideally, include a test that fails without this PR but passes with it.
[ ] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

[ ] Run the tests with pnpm test:ci.

Documentation

[ ] If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

[ ] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

Just in case anyone else comes across this looking for an example of how to test for an unhandled rejection or exception, some examples from the test file
test('can test unhandled rejection', async () => {
  const fn = vi.fn()

  const promise = new Promise<void>((resolve) => {
    process.on('unhandledRejection', () => {
      fn()
      resolve()
    })
  })

  Promise.resolve().then(() => {
    throw new Error('unhandled rejection')
  })

  await promise

  expect(fn).toHaveBeenCalledTimes(1)
})

test('can test unhandled exception', async () => {
  const fn = vi.fn()

  const promise = new Promise<void>((resolve) => {
    process.on('uncaughtException', () => {
      fn()
      resolve()
    })
  })

  nextTick(() => {
    throw new Error('unhandled exception')
  })

  await promise

  expect(fn).toHaveBeenCalledTimes(1)
})

authors: longzheng sheremet-va


text:
feat: loading animation for beforeEach, beforeAll, afterEach, afterAll

fix: #338 Loading animation for beforeEach, beforeAll, afterEach, afterAll.
interface Task add hooks and use hooks save suite/test hook exec state.

Seems good, thanks!

authors: AlaaZorkane poyoho


text:
Add a warning about cluster_dns and service_cidr in examples

As mentioned in #351.
There is already a note about that in the README, but I thought it might help to have it proeminently in the sample configuration as well.

Ah you did it already and it's just text, so I can merge now :) Thanks!

authors: jpetazzo vitobotta


text:
Reputation system

Refactor User Profile, add an integer field to store the user's reputation
Accepted answer: +10 reputation
Liked article: +5 reputation
Favorited question: +3 reputation
Liked feed: +1 reputation
Answer up vote: +1 reputation
Display reputation on users profile page and on feed/question pages
@gissues:{"order":50,"status":"inprogress"}

This issue is too old now, closing it and adding it to #66

authors: sebastian-code vitorfs

repo: vitorfs/bootcamp


text:
No connectin with MySQL

Hi we try to install but is say "No connectin with MySQL" we use vestacp with mysql
but if try to phpmyadmin work if try with remote software its work but not in hopebilling
with localhost or public ip
thx for helping

Now he wave : Warning: Illegal string offset 'db_host' in

repo: vityabond/hopebilling


text:
Ugly way to find out if running in deferred task?

Currenty (in viur-core >= 3.3.0) this is the only valid way to find out if code is running within a deferred task:
getattr(utils.currentRequest.get(), "DEFERRED_TASK_CALLED", False)

Becuase DEFERRED_TASK_CALLED is only a member of the Request when it was invoked from a deferred task (@CallDeferred).
In viur-core < 3.3.0, the variable DEFERRED_TASK_CALLED was also mispelled DEFERED_TASK_CALLED, which was fixed by #508.
This issue is a request for providing a flag is_deferred (likely to isDevelopmentServer) in the current Request object, to decide whether code is executed within a deferred call or not.

Resolved by #556

repo: viur-framework/viur-core


text:
datamodel: update documentation for getPropType

documentation indicates that getPropType() returns a name (string), but it actually returns the type instance (or None). update the documentation to reflect this.
feel free to close this issue and open a bug that the documentation was correct and the implementation wrong, and i'll take a stab at fixing that.

returning the name (a string) is as easy as:
-return self.getDataType( pdef[1].get('ptype') )
+return self.getDataType( pdef[1].get('ptype') ).name

repo: vivisect/synapse


text:
Билд под macOs High Sierra

Делал все, как сказано в readme.
brew install dub dmd curl openssl mpv
С этим проблем не возникло.
brew install homebrew/dupes/ncurses
Error: homebrew/dupes was deprecated. This tap is now empty as all its formulae were migrated.
Зато это работает:
brew install ncurses
brew doctor brew link ncurses -force
тоже особо проблем нету, только в .bash_profile добавил:
export PATH="/usr/local/opt/ncurses/bin:/usr/local/sbin:$PATH"
git clone https://github.com/vk-cli/vk cd vk git checkout VER dub build
Первый раз:
dub build Running pre-generate commands for vk... version string: 0.7.6 Performing "debug" build using dmd for x86_64. ncurses ~master: target for configuration "minimal" is up to date. vk ~master: building configuration "debug"... source/app.d(378,84): Deprecation: integral promotion not done for -to(1), use '-transition=intpromote' switch or -cast(int)(to(1)) Reticulating splines... Linking... Undefined symbols for architecture x86_64:   "__D9vkversion14currentVersionxAya", referenced from:       __Dmain in vk.o       __D5utils7initdbmFZv in vk.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Error: linker exited with status 1 dmd failed with exit code 1.
Если написать dub build еще раз:
Running pre-generate commands for vk... version string: 0.7.6 Performing "debug" build using dmd for x86_64. ncurses ~master: target for configuration "minimal" is up to date. vk ~master: building configuration "debug"... source/app.d(378,84): Deprecation: integral promotion not done for -to(1), use '-transition=intpromote' switch or -cast(int)(to(1)) Reticulating splines... Linking... To force a rebuild of up-to-date targets, run again with --force.
Пробуем запустить:
`object.Exception@std/process.d(3339): Environment variable not found: LANG
4   vk                                  0x0000000102db0fda pure @safe void std.exception.bailOut!(Exception).bailOut(immutable(char)[], ulong, const(char[])) + 126
5   vk                                  0x0000000102db0f56 pure @safe bool std.exception.enforce!().enforce!(bool).enforce(bool, lazy const(char)[], immutable(char)[], ulong) + 106
6   vk                                  0x0000000102eb09dd @safe immutable(char)[] std.process.environment.opIndex(const(char[])) + 89
7   vk                                  0x0000000102e20f5f void localization.setEnvLanguage() + 27
8   vk                                  0x0000000102daebc0 void app.init() + 52
9   vk                                  0x0000000102da3f39 _Dmain + 769
10  vk                                  0x0000000102e6e12f void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])).runAll().__lambda1() + 39
11  vk                                  0x0000000102e6dfbf void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])).tryExec(scope void delegate()) + 31
12  vk                                  0x0000000102e6e09a void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])).runAll() + 138
13  vk                                  0x0000000102e6dfbf void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])).tryExec(scope void delegate()) + 31
14  vk                                  0x0000000102e6df2d _d_run_main + 485
15  vk                                  0x0000000102da4341 main + 33
16  libdyld.dylib                       0x00007fff55a83014 start + 0
17  ???                                 0x0000000000000000 0x0 + 0
`

LANG="en_US.UTF-8" ./vk  ?

LANG="en_US.UTF-8" ./vk

Работает :D

repo: vk-cli/vk


text:
Function "Hello" does not presented in serverless.yml

When I try to execute the step functions in offline, i got the error 'Function "Hello" does not presented in serverless.yml'
Below is the console output
Serverless: Preparing....
Serverless: Trying to find state "hellostepfunc" in serverless.yml
Serverless: Building StepWorkFlow
Serverless: Function "Hello" does not presented in serverless.yml

My serverless.yml is below
package:
  exclude:
    - node_modules/**

provider:
  name: aws
  runtime: nodejs8.10
  stage: dev
  region: ap-southeast-2

functions:
  hello:
    handler: hello.hello
  bye:
    handler: bye.bye

stepFunctions:
  stateMachines:
    hellostepfunc:
      events:
        - http:
            path: hello
            method: POST
      definition:
        Comment: "An example app using step-functions and api gateway"
        StartAt: Hello
        States:
          Hello:
            Type: Task
            Resource: "arn:aws:lambda:#{AWS::Region}:#{AWS::AccountId}:function:${self:service}-${opt:stage}-hello"
            Next: Bye
          Bye:
            Type: Task
            Resource:  "arn:aws:lambda:#{AWS::Region}:#{AWS::AccountId}:function:${self:service}-${opt:stage}-bye"
            End: true
custom:
  stepFunctionsOffline:
    stepOne: hello
    stepTwo: bye

plugins:
  - serverless-step-functions
  - serverless-pseudo-parameters
  - serverless-offline
  - serverless-step-functions-offline```

Hi @anandrajj .
Sorry for long response.
Yes, because your settings are not correctly specified for plugin.
In section stepFunctionsOffline you need to specify object like [name of step function]: [name of function in serverless yml.]
In your case it should be
custom:    stepFunctionsOffline:       Hello: hello       Bye: bye


text:
[Umbrella Issue] Add support for io-related methods

This is an umbrella issue for IO support.  The following examples show what the implementation could look like:
Read input
var val string = e.IO.ReadIn("prompt")

File
var file File = e.File.Open("path")

Alias
var string val := e.ReadIn(<prompt>)
var lines []string =  e.Cat(<file path>)
var file File = e.Open("path")

Write output
Write output
e.IO.Write("string") // writes to stdout
e.IO.Write("string", path)

File output
var file File = e.File.Open("path")
file.Write("data")

Implemented in release https://github.com/vladimirvivien/gexe/releases/tag/v0.1.0

repo: vladimirvivien/gexe


text:
Improve logging of array parameters in BasicBinder

Before:
binding parameter [3] as [ARRAY] - [[Lcom.xxx.yyy.zzz.xxx.api.SampleTriggers;@5c3ef336]

Now:
binding parameter [3] as [ARRAY] - [[PURCHASE_CONFIRMATION]::SampleTriggers[]]

Thanks for the Pull Request. I'll review it when I have some time.

I reopened it because I thought the issue was about truncating the array. I'll integrate it without truncation.

The purpose of truncation was to avoid possible megabytes of data logged as nobody can know the array lengths in general.

But you are right, it was mainly not about truncation.

Thanks, I merged it.

authors: dpolivaev vladmihalcea

repo: vladmihalcea/hibernate-types


text:
using vllm to answer in Qwen-7B-Chat, there is a recurring issue of answers being repeated multiple times,

When using vllm to answer in Qwen-7B-Chat, there is a recurring issue of answers being repeated multiple times, which is not present when not using vllm.
GPU: 2  T4
MODEL: Qwen-7B-Chat
PROMPT:  <指令>根据已知信息，简洁和专业的来回答问题。如果无法从中得到答案，请说 \n"根据已知信息无法回答该问题，请使用随手拍进行提问，随手拍使用路径：手机移动办公-工作台-数字直通车"。不允许在答案中添加编造成分，答案请使用中文，结果以markdown的形式输出。</指令>\n\n<已知信息>问题：是否可以先开户、后面再补上门核实和法人开户意愿核实工作？ 答案：上门核实可以后补，法人开户意愿核实需要提前或同步完成。\n问题：客户签约财资需要哪几个步骤（大步骤，具体的步骤可以参考操作文档） 答案：1、客户确认签约财资的方案；\n2、上级单位与下级单位完成账户使用授权（如无下级单位或关联单位，则跳过这一步）；\n3、在前台签署相关协议，录入系统；\n4、经办行引导客户登录财资，并协助客户配置相关设置及参数；\n问题：营业执照刚刚注册好，工商系统还查不到，能开户吗？ 答案：在风险可控的情况下，确定客户开户信息真实，可以开户。</已知信息>\n\n<问题>企业开户流程</问题>

INFO 11-20 08:54:05 async_llm_engine.py:370] Received request 8b2eab1b928747abb9d544a6b2a5a37a: prompt: '<|im_start|>system\nYou are a helpful assistant.<|im_end|>\n<|im_start|>user\n<指令>根据已知信息，简洁和专业的来回答问题。如果无法从中得到答案，请说 \n"根据已知信息
无法回答该问题，请使用随手拍进行提问，随手拍使用路径：手机移动办公-工作台-数字直通车"。不允许在答案中添加编造成分，答案请使用中文，结果以markdown的形式输出。</指令>\n\n<已知信息>问题：是否可以先开户、后面再补上门核实和法人开户意愿核实工作？ 答案：上门核实可以后补，法人开户意愿核实需要提前或同步完成。\n问题：客户签约财资需要哪几个步骤（大步骤，具体的步骤可以参考操作文档） 答案：1、客户确认签约财资的方案；\n2、上级单位与下级单位完成账户使用授权（如无下级单位或关联单位，则跳过这一步）；\n3、在前台签署相关协议，录入系统；\n4、经办行引导客户登录财资，并协助客户配置相关设置及参数；\n问题：营业执照刚刚注册好，工商系统还查不到，能开户吗？ 答案：在风险可控的情况下，确定客户开户信息真实，可以开户。</已知信息>\n\n<问题>企业开户流程</问题><|im_end|>\n<|im_start|>assistant\n', sampling params: SamplingParams(n=1, best_of=1, presence_penalty=0.0, frequency_penalty=0.0, repetition_penalty=1.0, temperature=0.0, top_p=1.0, top_k=-1, min_p=0.0, use_beam_search=False, length_penalty=1.0, early_stopping=False, stop=['<|im_start|>', '<|endoftext|>', '<|im_end|>'], ignore_eos=False, max_tokens=7908, logprobs=None, prompt_logprobs=None, skip_special_tokens=True, spaces_between_special_tokens=True), prompt token ids: None.2023-11-20 08:54:05 | INFO | httpx | HTTP Request: POST http://127.0.0.1:20002/worker_generate_stream "HTTP/1.1 200 OK"
INFO 11-20 08:54:05 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.0 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 9.4%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:10 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 27.2 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 13.6%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:15 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.9 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 18.3%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:20 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.7 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 22.5%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:25 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.7 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 27.2%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:30 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.7 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 31.4%, CPU KV cache usage: 0.0%
2023-11-20 08:54:31 | INFO | model_worker | Send heart beat. Models: ['Qwen-7B-Chat']. Semaphore: Semaphore(value=4, locked=False). call_ct: 1. worker_id: bc0bc8a3.
2023-11-20 08:54:31 | INFO | controller | Receive heart beat. http://127.0.0.1:20002
2023-11-20 08:54:31 | INFO | stdout | INFO:     127.0.0.1:57204 - "POST /receive_heart_beat HTTP/1.1" 200 OK
INFO 11-20 08:54:36 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.5 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 35.6%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:41 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.4 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 40.3%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:46 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.8 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 44.5%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:51 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.5 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 48.7%, CPU KV cache usage: 0.0%
INFO 11-20 08:54:56 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 26.3 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 53.4%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:01 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.9 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 57.6%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:06 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.9 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 61.8%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:11 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.8 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 66.0%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:16 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.7 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 70.2%, CPU KV cache usage: 0.0%
2023-11-20 08:55:16 | INFO | model_worker | Send heart beat. Models: ['Qwen-7B-Chat']. Semaphore: Semaphore(value=4, locked=False). call_ct: 1. worker_id: bc0bc8a3.
2023-11-20 08:55:16 | INFO | controller | Receive heart beat. http://127.0.0.1:20002
2023-11-20 08:55:16 | INFO | stdout | INFO:     127.0.0.1:57220 - "POST /receive_heart_beat HTTP/1.1" 200 OK
INFO 11-20 08:55:21 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.7 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 74.3%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:26 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.5 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 78.5%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:31 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.6 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 82.7%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:36 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.7 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 86.9%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:41 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.2 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 91.1%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:46 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.1 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 95.3%, CPU KV cache usage: 0.0%
INFO 11-20 08:55:51 llm_engine.py:624] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 25.5 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 99.5%, CPU KV cache usage: 0.0%

same problem

repo: vllm-project/vllm


text:
vllm.engine.async_llm_engine.AsyncEngineDeadError

2023-12-19 18:11:16 | ERROR | stderr |
2023-12-19 18:11:16 | ERROR | stderr | The above exception was the direct cause of the following exception:
2023-12-19 18:11:16 | ERROR | stderr |
2023-12-19 18:11:16 | ERROR | stderr | Traceback (most recent call last):
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/uvicorn/protocols/http/httptools_impl.py", line 426, in run_asgi
2023-12-19 18:11:16 | ERROR | stderr |     result = await app(  # type: ignore[func-returns-value]
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/uvicorn/middleware/proxy_headers.py", line 84, in call
2023-12-19 18:11:16 | ERROR | stderr |     return await self.app(scope, receive, send)
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/fastapi/applications.py", line 1106, in call
2023-12-19 18:11:16 | ERROR | stderr |     await super().call(scope, receive, send)
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/starlette/applications.py", line 122, in call
2023-12-19 18:11:16 | ERROR | stderr |     await self.middleware_stack(scope, receive, send)
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/starlette/middleware/errors.py", line 184, in call
2023-12-19 18:11:16 | ERROR | stderr |     raise exc
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/starlette/middleware/errors.py", line 162, in call
2023-12-19 18:11:16 | ERROR | stderr |     await self.app(scope, receive, _send)
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 79, in call
2023-12-19 18:11:16 | ERROR | stderr |     raise exc
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 68, in call
2023-12-19 18:11:16 | ERROR | stderr |     await self.app(scope, receive, sender)
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/fastapi/middleware/asyncexitstack.py", line 20, in call
2023-12-19 18:11:16 | ERROR | stderr |     raise e
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/fastapi/middleware/asyncexitstack.py", line 17, in call
2023-12-19 18:11:16 | ERROR | stderr |     await self.app(scope, receive, send)
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/starlette/routing.py", line 718, in call
2023-12-19 18:11:16 | ERROR | stderr |     await route.handle(scope, receive, send)
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/starlette/routing.py", line 276, in handle
2023-12-19 18:11:16 | ERROR | stderr |     await self.app(scope, receive, send)
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/starlette/routing.py", line 69, in app
2023-12-19 18:11:16 | ERROR | stderr |     await response(scope, receive, send)
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/starlette/responses.py", line 270, in call
2023-12-19 18:11:16 | ERROR | stderr |     async with anyio.create_task_group() as task_group:
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 597, in aexit
2023-12-19 18:11:16 | ERROR | stderr |     raise exceptions[0]
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/starlette/responses.py", line 273, in wrap
2023-12-19 18:11:16 | ERROR | stderr |     await func()
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/starlette/responses.py", line 262, in stream_response
2023-12-19 18:11:16 | ERROR | stderr |     async for chunk in self.body_iterator:
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/miniconda3/envs/pytorch21/lib/python3.10/site-packages/fastchat/serve/vllm_worker.py", line 113, in generate_stream
2023-12-19 18:11:16 | ERROR | stderr |     async for request_output in results_generator:
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/vllm-gptq/vllm/engine/async_llm_engine.py", line 435, in generate
2023-12-19 18:11:16 | ERROR | stderr |     raise e
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/vllm-gptq/vllm/engine/async_llm_engine.py", line 429, in generate
2023-12-19 18:11:16 | ERROR | stderr |     async for request_output in stream:
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/vllm-gptq/vllm/engine/async_llm_engine.py", line 70, in anext
2023-12-19 18:11:16 | ERROR | stderr |     raise result
2023-12-19 18:11:16 | ERROR | stderr |   File "uvloop/cbhandles.pyx", line 63, in uvloop.loop.Handle._run
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/vllm-gptq/vllm/engine/async_llm_engine.py", line 37, in _raise_exception_on_finish
2023-12-19 18:11:16 | ERROR | stderr |     raise exc
2023-12-19 18:11:16 | ERROR | stderr |   File "/root/vllm-gptq/vllm/engine/async_llm_engine.py", line 32, in _raise_exception_on_finish
2023-12-19 18:11:16 | ERROR | stderr |     raise AsyncEngineDeadError(
2023-12-19 18:11:16 | ERROR | stderr | vllm.engine.async_llm_engine.AsyncEngineDeadError: Task finished unexpectedly. This should never happen! Please open an issue on Github. See stack trace above for the actual cause.

https://github.com/vllm-project/vllm/issues/2239 duplicated


text:
Could we support Fuyu-8B, a multimodel llm?

Hi,
Fuyu 8B is a multimodel llm model, could we support it in vllm?
https://www.adept.ai/blog/fuyu-8b
It seems to me current vllm only could support pure text, so for this kind of multimodel mixing with image, how could we handle it?
Thx~

now we added supported for llava, this is welcomed!

I would like to work on this model. But it seems that the persimmon used as language model in Fuyu-8B hasn't been supported.
Maybe we can support it first?


text:
[New Model]: Request to support xai-org/grok-1 (314B parameters with MOE architecture)

The model to consider.
https://huggingface.co/xai-org/grok-1
With int8 quantization, this model can be hosted on 8 GPUs with 80GB memory, a node of H100 or A100. After a high-level look at the code, I am seeing xai has the model architecture implemented via JAX and its code couples model architecture and implementation details such as int8 quantization and sharing across GPUs.
I saw a twitter post about the tricky implementation differences in Gemma's implementations. So, I wonder if someone familiar with JAX is planning to port it to PyTorch and validate, so that it can be integrate with vLLM with additional optimization for MOE architecture.
The closest model vllm already supports.
Mixtral 8x7B.
What's your difficulty of supporting the model you want?

its source code is in JAX, instead of PyTorch
It requires quantization; otherwise, it won't work on most GPUs, including H100/A100. Here, I assume cpu offloading is not of considerations to avoid notable impact on efficiency
Its MOE component require additional optimization for inference efficiency

HF Version
https://huggingface.co/keyfan/grok-1-hf
untested, wasn't able to run it on 8xA10

PyTorch 移植是第一步！

I saw that grok-1 already has a torch version(https://huggingface.co/hpcai-tech/grok-1), which has been considered to be available in modelscope. I wonder when vllm will support it?

authors: ai-jz nivibilla uRENu