Bring back sets and properties upload dialog when uploading file(s)

I would love for you to work on this. We'd merge it in asap.

Ok, in the end I went to do #1740 (and a few others) before I got your answer here, so they are already different pull requests.
Can you merge those to avoid merge conflicts? I will then have a go on this one too.

I think this will modify the same files, can you merge it before I branch ?
https://github.com/concrete5/concrete5-5.7.0/pull/1755

Ok thanks for the merge, I'm starting at it, but here again seems like a piece of work :/
What I will do, instead of bringing the old dialog, is to give access to the "bulk" menu for recently uploaded files. That will make use of existing dialogs and make it a lot more scalable (and it is quite in line with what I wanted to add to the file manager in the first place). For this I will refactor the menu itself, move a part of it in a controller, and …well remove that legacy tool Download … to move it to a nice route. So in short, my action plan:

Refactor the search element
Move the menu in a nicer way
Have the download tool replaced by a route
Move the 'item[]' param to fID[] instead to harmonize all menus
Have a controller list all menu items
Create a new menu instance for the recently uploaded
Probably some more refactor along the way (seek and destroy Loader::helper for instance) :/

Expect here again a quite big pull request here :/ not sure how long it will take me, but I am now officially working on it :)

Off the top of my head some of those changes sound a little wide ranging. You'll definitely have to add some controllers and routes and views and I can see refactoring some of the bulk and sets interface (as well as merging them into a new dialog) and reworking the file manager upload
Javascript to launch the dialog - but I'm not sure I understand all the menu refactoring. Could you explain what you mean by that?
Sent from my iPhone

On Jan 3, 2015, at 3:51 AM, Florian Delizy<EMAIL_ADDRESS>wrote:
Ok thanks for the merge, I'm starting at it, but here again seems like a piece of work :/
What I will do, instead of bringing the old dialog, is to give access to the "bulk" menu for recently uploaded files. That will make use of existing dialogs and make it a lot more scalable (and it is quite in line with what I wanted to add to the file manager in the first place). For this I will refactor the menu itself, move a part of it in a controller, and …well remove that legacy tool Download … to move it to a nice route. So in short, my action plan:
Refactor the search element
Move the menu in a nicer way
Have the download tool replaced by a route
Move the 'item[]' param to fID[] instead to harmonize all menus
Have a controller list all menu items
Create a new menu instance for the recently uploaded
Probably some more refactor along the way (seek and destroy Loader::helper for instance) :/
Expect here again a quite big pull request here :/ not sure how long it will take me, but I am now officially working on it :)
—
Reply to this email directly or view it on GitHub.

Actually, the way it goes so far, I add a route to the backend controller, and I merge the tool into the controller (adding a download method).
for the menu refactoring (and as preliminary of the next-to-come-feature i wanted to add), the search controller will control a list of menus entries for the bulk actions. Moreover, that menu will be included into an element instead of duplicated twice in the file manager search page.
And yes that is definitely wide ranging, but, sometimes you got to get your sleeves up and dig in :/

(I will probably keep the tool btw, and bridge it to the controller, just adding a deprecated message as I realize that some addons might actually still use it on the marketplace, so I'll just let them know that that tools - as all tools anyway - will disappear in a short time).

If you want to follow my progresses, I created a branch on my side (not ready for pull request yet):
https://github.com/goutnet/concrete5-5.7.0/tree/add-multi-upload-file-properties
I'll push to it from time to time.

I am still working on it, but making good progresses, I will push something tonight before I get to sleep (maybe not completed, but that should give you a good idea).
Here are the major changes I am on:

moved legacy tool "download" to search file backend controller
Created a helper to store file manager menu
Made file manager menu (bulk actions so far) modifiable by application/addons
Turn the bulk menu into a bootstrap drop down with a little form in it
Uploaded files will be a new target on the bulk menu
Added icons to menus

This is what  I meant by sharing the dropdown menu :

After a second thought, I switched to using a btn-group with active class, that now looks like this:

The bones are here, now I need to rework the javascript to make use of that new markup, save the uploaded fIDs into some place and work the automatic selection of buttons.
Next will be rework the context menu so it uses the same helper to be generated (allowing here again application/addons to modify the menu as well), and remove all the legacy tools to move them to routes+controllers (at least the one involved in the menu).

Ok, I just pushed something interesting, it has all the PHP bones, but not the js that goes with it yet.
I also added a styling for "dangerous" actions.
The js is on the way, but for now another screenshot update:

Tell me how you like it.

Pushed the first part of js, the menu is now working as it used to be and is ready for upload.
https://github.com/goutnet/concrete5-5.7.0/tree/add-multi-upload-file-properties
What is left regarding this very issue:

Pull all new fIDs from the upload request
Populate them in the hidden input
Work on the enable/disable of the dropdown
Fix the dropdown not closing itself (for some reason)

What will come next:

refactor the context menu to use the same helper (to make it customizable)
rework the js appropriately
refactor files tools and merge them in the backend controller

Not sure if I will do all of that in the same pull request, but I'll continue tomorrow. I think I am gonna need another 2 or 3 days (1 only if I am very lucky tomorrow :/). Can this make it for <IP_ADDRESS> ?

Well, I got carried away, and just finished the upload related JS, (and it is now 5am :( ).
From now, the dropdown menu opens upon upload with the upload group button selected and allow the user to select the different menus.
I still have a few little js errors to track and fix but we are getting close (mostly the dropdown not closing correctly, if sb want to have a look, I am interested). As for the second part (refactor the context menu), I can do it in a second pull request if you prefer.

I am onto migrating the context menu as well to use the same helper to make it cleaner and customizable. (I still need to update the JS code, but this is on the way).
Here is how the new menus look like :

Alright, the file manager menu is now fully refactored and using the centralized helper. This allow the following:

Full customization of the file manager menu by addons or application
bulk menu actions and file context menu can share the same responders
bonus: new Rescan context menu for single files

What's left is bringing back duplicate (that was disabled on bulk), and moving tools to routes.
other than that is is good to go :)
@aembler do you want me to do the tools refactoring in a later pull request, or do you want me to continue in this one?

Any updates on this one?  This is going to be fairly important to a project I'm starting work on.


Retrieve ReReco workflows and include lumisections data

Scan all Stats2 requests related with ReReco workflows (based on the RequestType).
Include the lumisection information available for the workflow in ReqMgr2, set the lumisection data only for the most recent event record in the history, otherwise set zero.

Update: When a Stats2 request is updated, this also includes the 'Lumis' attribute independent if it is a ReReco request or related to MC


entitlementFrequency option always building with a value of 1

While working on adding options for isBundledAssessment and parentAssessmentTypeId, I noticed that all scans were being started as a Single scan. API v3 changed this to be a string value vs the old integers, so it would make sense for this to be switched to an enum. Will work on this and file a pull request.

Fixed in merge


MEmu sudden adb disconnect

Newest version of MEmu 7.5.5.
Not sure if Android 5.1 or 7.0 VM
The emulator suddenly just disconnects from adb server for some reason
Restarting LabMem connects and runs as normal

Opening MeMu multi-instance manager seems to cause adb connection interruption


Target Expansion

Currently targets are duplicated to support minor difference, e.g.
targets:
  build-amd64:
    after: ...
    watches: ...
    env: ...
    cmds:
      - ...
      - build.sh amd64

  build-arm:
    after: ...
    watches: ...
    env: ...
    cmds:
      - ...
      - build.sh arm

In the example, the only difference is amd64 vs arm, but rest information is duplicated and redundant.
Recommend target expansion:
targets:
  build-[arch:amd64|arm]:
    after: ...
    watches: ...
    cmds:
      - ...
      - build.sh $arch

The target build-[arch:amd64|arm] is expanded to two targets: build-amd64 and build-arm.

The final schema is
targets:
  build-[arch:amd64,arm]:
    after: ...
    watches: ...
    cmds:
      - ...
      - build.sh $[arch]

Resolved in #85


Neo4j

This pull requests includes:
New lncli command to create a snapshot of the channel database.
lncli snapshotchannels
A snapshot of the database is written to <lnddir>/snapshot/graph/<chain>/channel.db
New lnneo4j command line tool to import a snapshot of the channel database to a Neo4j Graph database.
lnneo4j — help
NAME:
 lnneo4j — import a snapshot of your channel databse to neo4j

USAGE:
 lnneo4j [global options] command [command options] [arguments…]

VERSION:
 0.1.1 commit=

COMMANDS:
 help, h Shows a list of commands or help for one command

GLOBAL OPTIONS:
 — lnddir value path to lnd’s base directory (default: “/home/ubuntu/.lnd”)
 — network value either mainnet, testnet, simnet, regtest, etc. (default: “mainnet”)
 — neouser value neo4j user for authentication (default: “neo4j”)
 — neopass value neo4j password for authentication. Required unless neo4j authentication is disabled, e.g. dbms.security.auth_enabled=false is set in neo4j.conf
 — neohost value neo4j hostname (default: “localhost”)
 — neoport value neo4j port number (default: “7687”)
 — help, -h show help
 — version, -v print the version

A tutorial LN guide that can be loaded on the Neo4j browser to investigate the Lightning Network snapshot.
See Lightning Network: Import the topology to the Neo4j Graph database for use and motivation.
I know this is out of the blue, and I apologize if this is not appropriate. I thought I'd share this as it may be of interest to others too.

Hi @Bluetegu thanks for this PR! However, I don't think we'll be able to accept something like this at this point. This is due to the fact that we would now require neo4j in order to build lnd itself. This goes counter with our short-term goal of reducing the surface area of lnd itself. Instead, you can package up cool things like this as external projects, which serve as companions to lnd for those trying to. Also snapshotting the channel state in the naive fashion that this PR does can lead to security issues if users aren't aware of the implications of restoring to dated versions of the channel state.

Hi Olaoluwa, I fully understand the need to focus, especially in a
demanding project like LND; I'll try to contribute to the main effort too
:-). I am interested in the routing aspect of LN, so if there is an effort
in this area that I can help with please let me know. Best, Ron
On Thu, May 31, 2018 at 6:45 PM, Olaoluwa Osuntokun <
<EMAIL_ADDRESS>wrote:

Hi @Bluetegu https://github.com/Bluetegu thanks for this PR! However, I
don't think we'll be able to accept something like this at this point. This
is due to the fact that we would now require neo4j in order to build lnd
itself. This goes counter with our short-term goal of reducing the surface
area of lnd itself. Instead, you can package up cool things like this as
external projects, which serve as companions to lnd for those trying to.
Also snapshotting the channel state in the naive fashion that this PR does
can lead to security issues if users aren't aware of the implications of
restoring to dated versions of the channel state.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lightningnetwork/lnd/pull/1307#issuecomment-393706190,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABdHujit_QlmuL-QElnC0sQBxYi86wQEks5t4HJ3gaJpZM4UU-hc
.


Update init.py

Added missing code to fix the broken charging status
Checklist:

[ x ] The code change is tested and works locally.
[  ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[ x ] There is no commented out code in this PR.
[ x ] I have followed the [development checklist][dev-checklist]

Hi @lundan,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Good here.  is_charging will always be returned by pycarwings2. Thanks!


Make all app settings "safe" or else make it clear in the documentation that you should only set them after registration

The current situation right now is some settings are "special" (:auth_login_path, :auth_unauthenticated_path, :auth_logout_path, :default_strategies, :warden_failure_app), and can be safely set before register Padrino::Warden. Other settings have to be set after the register, or else during registration padrino-warden overwrites these settings, even if you've set them to some specific value.
I don't see a point to this arbitrary split, and making people either
(a) remember which settings are where ("safe", or "unsafe"; or "settable before register" vs "settable only after register")
(b) just set everything after the registration (in which case all of those protections (unless app.respond_to?) just seem pointless)
(c) read the source code to find out
I propose either make all of these settings "safe".... or else have them all not be safe, and then make a specific note about this in the documentation. Would appreciate your thoughts on this.

Sorry for the late response but I'm swamped with college-related stuff. I'll take a look at it this weekend.

got it. Thanks for the update!

I had an internal debate about allowing users to disable sessions and I decided for it. It will render warden useless but I'm assuming you know what you are doing when disabling this.
I also created a wiki page which lists the possible options and default values for them
https://github.com/jondot/padrino-warden/wiki/Options
Do let me know if I messed something up.

Thanks for going through all the settings and doing all that typing, @Quintasan ! Appreciate it. Ditto for the wiki page too.
I don't know if you'll want to do this change, but I was considering that you could iterate over a hash. The advantages are (a) it looks cleaner, (b) it's easier/quicker to see at a glance what all the settings and their defaults are, and (c) it's easier in the future as well (saves on typing!) to add future settings plus their defaults. If you're ok with this, I can do the typing this time and send you a PR :}
{
  # Enable sessions but allow the user to disable them explicitly
  sessions: true,

  auth_failure_path: '/',
  auth_success_path: '/',

  # set :auth_use_referrer to true to redirect a user back to an action
  # protected by 'login'/'authenticate' after successful login
  auth_use_referrer: false,

  auth_error_message: "You have provided invalid credentials.",
  auth_success_message: "You have logged in successfully.",

  ...
}.each do |setting, default|
    app.set setting, default unless app.respond_to? setting
end

Bleh, please do. I'll merge it for the next release.


[cli, flow-legacy] Fix CLI typo for flow-legacy

This typo breaks backwards compatibility with flow users from 0.19.0 because we can no longer use flow-legacy since you can't provide the right CLI argument and the switch statement looks for the correct argument (flow-legacy) instead of the only one you can put on the CLI (flow-leagcy)

👋 The Meteor CLA has been signed. What's the process for getting changes like this in? This is a breaking change for 0.20 as the flow-legacy cannot be run, and the flow (formerly flow-modern is broken with __typename per #443. This is a critical part of my team's workflow (thank you!). Happy to do whatever I can to help.

👋 The changes look great, thanks for the patch!

@kristiehowboutdat released in version 0.20.1!


FE redesign, logo proposal, bypass link

Did a couple of changes for a proposal.

New logo, very simple: WIX with a "canceled" street sign
FE notice page redesign. Changed the text a bit and made everything a bit more tidy
Bypass link. "continue to website and turn off extension" in the notice page turns off the extension.
Added logo to the popup

Thanks @maximocampo :+1:


Remove weather observation section in browser page

Weather data has been added as a regular stat var observations and can be used from the variable hierarchy.

Should we wait till daily data is in?


Improve macro errors

Currently, error handling in macros is basically just the use of .unwrap().
This has worked fine but produces unclear error messages. So it should be improved on.
One alternative is using the proc-macro-error crate.

Completed with 178267c701c233542078c09fe6b19802f9642dbd


Inconsistencies in the handling of public_folder in image paths: Discrepancies between expectations and results

If I use public_folder: /foo

Expectation?: image: /foo/example.jpg
Reality: image: /foo/example.jpg ✅

If I use public_folder: /foo/

Expectation?: image: /foo/example.jpg
Reality: image: /foo//example.jpg 🆗 It is ok because there is the previous option

If I use public_folder: ''.


[WIP] fixed the loop of get cluster by name

currently list cluster api returns all the cluster and ignores filter name=clustername
To fix this behavior, we are also now checking if the returned list entity has same name along with existing check if its a pc entity or not.
Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/ok-to-test


File explorer is not updated after many file changes occur

Hello,
I noticed that sometimes (often ?) the file explorer doesn't get updated (missing files/folder) after creating new files/folders with something like a git pull or using symfony console to generate files.
Refreshing the explorer using the little refresh icon make the files/folders appear.
This is a follow up of this issue https://github.com/Microsoft/vscode/issues/24309

VSCode Version: 1.21
OS Version: Ubuntu 17.10 / Fedora 27

Thanks !

VS Code used to auto-refresh file system changes.  Now, nothing is auto-refreshed.
In the file explorer, I have to press the refresh icon to get externally changes folders and files to appear.
Please fix!

I ran Code --verbose and, whenever I change files somewhere within the folder (current open in Code), I see lines like this fly by in the verbose output:
[5624:0623/174920.757:INFO:CONSOLE(28)] "%c[File Watcher]", source: file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)
[5624:0623/174920.759:INFO:CONSOLE(28)] "%c[File Watcher]", source: file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)
[5624:0623/174920.878:INFO:CONSOLE(28)] "%c[File Watcher]", source: file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)

So, it seems like the VS Code process is away of the file system changes, but nothing ever updates in the VS Code user-interface.

VSCode doesn't handle refresh properly when working on a multi-folder root. I have to manually trigger Files: Refresh Explorer
The files were not in git.

I would also prefer the explorer to refresh automatically. I can't see any benefit of not.
I imagine that this is not done, because the explorer 'jumps' to the open file when refreshed. But I also don't like this behavior. I don't think the scroll should not change when refreshing.
Thanks for your great work!

It's an important bug that can lead to error. I hope it can be fixed as soon as possible.

I agree with @Paviluf.  If I git pull, I expect my explorer within vscode to automatically be updated to reflect the latest changes of my repo. Instead, I don't see those updates reflected until I click the refresh icon in vscode.  The additional step of clicking refresh shouldn't be required. 🕷
This is a standard feature in every other ide.

I've also experienced this after switching branches and pulling latest code. The tree was not updated and it left me confused as to why I couldn't find specific files I knew existed.
VScode 1.17-2
Manjaro Linux, kernel 4.13

@Tyriar shouldn't the new file watcher improve the experience?

@kieferrm there are some issues with the new watcher (here) and some with the older watcher as well (eg. this issue). I think performance is generally better with the new one, supporting multiple roots was easy and it's now using the same watcher on all platforms (before we hand-wrote/owned the Windows one).

vs code 1.20.0 running on ubuntu. auto refresh issue still present.

This is a base functionality for any IDE. Even though it doesn't "break" anything it deserves attention.

That also drove me crazy … until I figured out there was a directory with an accent in its name. 💥
But the refresh only breaks when VS Code is launched from the inside of the directory (or one of its subdirectories).
If the full path from a parent, non-accentuated directory is provided, it works as intended:
cd ~/dév
code .      # FAILS (VS Code will never refresh file explorer and opened files)
code ~/dév  # WORKS

Maybe it's not the same bug for everyone but here on macOS 10.13, this one is constant and reproducible.

Does it work if you use the setting files.useExperimentalFileWatcher": true? (Seen in the issue with (maybe) the same root cause #22266?
With this setting, it also does not auto-refresh, unfortunately (Version 1.21.0-insider a903bd38f, MacOS El Capitan (10.11.6) )
Interestingly, the Git "Source Control" always auto-refreshs, no matter if the experimental file watcher is used or not.

@Dominik-K, what about my previous observation?
Don't you have an accent in the directory path from where you open VS Code?
"files.useExperimentalFileWatcher": true doesn't affect this bug.

@arthurwhite You're lucky that auto-refresh is working on your side (with a workaround). Which VSCode version are you using? No, I don't use accents in folder or file names.
So, you better create a new issue with your specific bug. This one is about auto-refresh not working in general.

Just found out that this happens only if I'm using a workspace. code-insiders --verbose abc.workspace shows these lines:
[99398:0307/192511.104861:INFO:CONSOLE(257)] "%c[IPC Library: Watcher] %cStart watching: [... many folders ...]
Stop watching: []", source: file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js (257)
[99398:0307/192511.105465:INFO:CONSOLE(257)] "%c[IPC Library: Watcher] %c(node:99405) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 uncaughtException listeners added. Use emitter.setMaxListeners() to increase limit", source: file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js (257)

Seems like I have too many folders added to the workspace.

I have the 1.21.0-insider version. But it has been confirmed also on the stable branch.

So, you better create a new issue with your specific bug. This one is about auto-refresh not working in general.

I won't post another duplicate of this issue: the effect of this bug is the same.
Maybe the causes are different from one another. But now, we have at least one tangible path to explore.

Guys, it can be related to https://code.visualstudio.com/docs/setup/linux#_error-enospc
check this params on your pc

Guys, it can be related to https://code.visualstudio.com/docs/setup/linux#_error-enospc

In the latest version you should get a nice notification warning you about file handles pointing to those docs.

Literally just spent like a hour trying to figure out why webpack wasnt building a dist folder.  Just moved from atom.  Wow I can not believe this is not working properly.  Love VSCode this is just a huge piece for me.  Only one I noticed was not updating files that were updated elsewhere.  Like if I am updating packages and they are updated by npm gotta close and reopen file to see that.

switches back to atom for now *

@Tyriar Can you explain to us how that article linked helps those of us on OSX with this issue. I'm not understanding how that fixes this issue.

@dardub that's for Linux, I didn't imply otherwise did I?

@Tyriar Ok. Obviously the link was for Linux, but many of us mentioned that this was occurring on other operating systems as well. So I'm just wondering if there is a solution for other operating systems if there is a solution for Linux users.

@dardub I`ve edited my comment. Now link is correct.

I'm seeing this randomly when switching branches in git.  I can manually refresh and all is OK, but would be nice to have it auto refresh without my intervention.  I tried restarting in verbose mode to see if I could see anything, but now it is fine if I switch back and forth between branches.

People seeing this issue, here is some steps to get more info:
VS Code is using different file watching strategies depending on your OS and your setup.
First thing to check:

[ ] I verified that the issue still reproduces in our insiders version (https://code.visualstudio.com/insiders/)
[ ] I verified that this issue is happening outside of a node_modules folder. Our file watcher ignores this folder!

To find out more about this issue, please first answer this:

[ ] What OS are you on
[ ] Does this happen from an empty workspace, a single-folder workspace or a multi-root workspace?
[ ] Do you have files.useExperimentalFileWatcher: true configured in settings?
[ ] What is your configured files.watcherExclude setting?

Then please answer the following depending on your setup:

[ ] It reproduces with any folder or workspace you open
[ ] The files/folders you open are on your local disk and not on a network share nor a UNC drive
[ ] The files/folders you open are not behind a symbolic link
[ ] The folder(s) opened use the exact same casing as they are on disk
[ ] It reproduces when I make a change to the file from another VS Code window (either from the editor or the file explorer)

Then please attach the output of our development console

run code --verbose from the command line
perform the action that causes you to not see the file change in VS Code
attach the output from the console (Help > Toggle Developer Tools > Console)

Thanks for taking the time to fill out this questionnaire.

Well it seem that it doesn't happen anymore since I removed the symlinks I used to have the folders inside my /home (Desktop, Downloads, etc...) redirected to my other partition /media/Data.

Me it didn't work when I had an accentuated letter in the path of my project folder. It works now that I removed it.

@maximeplante which OS are you on and what was the folder name?

macOS 10.13.4
It won't work if the projet's folder has an accent or if the path to the project folder has an accent.

First thing to check:

[x] I verified that the issue still reproduces in our insiders version (https://code.visualstudio.com/insiders/)
[x] I verified that this issue is happening outside of a node_modules folder. Our file watcher ignores this folder!

To find out more about this issue, please first answer this:

What OS are you on

MacOS Sierra 10.12.6

Does this happen from an empty workspace, a single-folder workspace or a multi-root workspace?

I have no idea what the differences between those things are. simple project structure...?!
vue init webpack foo && cd foo && yarn install && yarn run build -> dist folder doesn't exist.

Do you have files.useExperimentalFileWatcher: true configured in settings?

No

What is your configured files.watcherExclude setting?

Not existing

Then please answer the following depending on your setup:

[x] It reproduces with any folder or workspace you open
[x] The files/folders you open are on your local disk and not on a network share nor a UNC drive
[x] The files/folders you open are not behind a symbolic link
[x] The folder(s) opened use the exact same casing as they are on disk
[ ] It reproduces when I make a change to the file from another VS Code window (either from the editor or the file explorer)
Can't tell...vscode won't allow me to open the same project twice in seperate windows ¯\_(ツ)_/¯

Then please attach the output of our development console
09:11:09.495 console.ts:136 [IPC Library: Watcher] [ADDED] /Users/snwflake/git-repos/nb-GMTool/client/dist/static/js/vendor.11a0744ddf4f449bef76.js.gz
09:11:09.495 console.ts:136 [IPC Library: Watcher] [ADDED] /Users/snwflake/git-repos/nb-GMTool/client/dist/static/mstile-310x310.png
09:11:09.495 console.ts:136 [IPC Library: Watcher] [ADDED] /Users/snwflake/git-repos/nb-GMTool/client/dist/static/android-chrome-512x512.png
09:11:09.496 console.ts:136 [IPC Library: Watcher] [ADDED] /Users/snwflake/git-repos/nb-GMTool/client/dist/static/fonts/opensanssemibold.483351b.ttf
09:11:09.496 console.ts:136 [IPC Library: Watcher] [ADDED] /Users/snwflake/git-repos/nb-GMTool/client/dist/static/fonts/opensansextrabolditalic.51d4b21.woff2
09:11:09.496 console.ts:136 [IPC Library: Watcher] [ADDED] /Users/snwflake/git-repos/nb-GMTool/client/dist/static/fonts/opensansextrabolditalic.cb00b81.woff
09:11:09.496 console.ts:136 [IPC Library: Watcher] [ADDED] /Users/snwflake/git-repos/nb-GMTool/client/dist/static/fonts/opensanssemibolditalic.1e78922.woff2
09:11:09.496 console.ts:136 [IPC Library: Watcher] [ADDED] /Users/snwflake/git-repos/nb-GMTool/client/dist/static/fonts/opensans.d2a705b.ttf
09:11:09.496 console.ts:136 [IPC Library: Watcher] [ADDED] /Users/snwflake/git-repos/nb-GMTool/client/dist/static/fonts/opensansbolditalic.47cf698.ttf
09:11:09.496 console.ts:136 [IPC Library: Watcher] [ADDED] /Users/snwflake/git-repos/nb-GMTool/client/dist/static/fonts/opensans.48aa7ad.woff2
09:11:09.498 console.ts:136 [IPC Library: Watcher] [ADDED] /Users/snwflake/git-repos/nb-GMTool/client/dist/static/fonts/opensansextrabold.0f5ecd4.woff2
09:11:09.498 console.ts:136 [IPC Library: Watcher] [ADDED] /Users/snwflake/git-repos/nb-GMTool/client/dist/static/fonts/opensanssemibold.86dd419.woff2
09:11:09.498 console.ts:136 [IPC Library: Watcher] [ADDED] /Users/snwflake/git-repos/nb-GMTool/client/dist/static/fonts/opensansbolditalic.90b8cd1.woff
09:11:09.501 log.ts:171   ERR [FileWatcher] terminated unexpectedly and is restarted again...
09:11:09.503 ipc.cp.ts:186 IPC "Watcher" crashed with exit code null
(anonymous) @ ipc.cp.ts:186
09:11:09.865 console.ts:136 [IPC Library: Watcher] Start watching: /Users/snwflake/git-repos/nb-GMTool]

I shortened the list a little, since there is a bunch more static stuff.
The explorer doesn't even update the files listed by the watcher. The only file inside dist is the index.html. E.g. not even the fonts listed above are added. Still need to manually refresh...
I feel like this issue should get a lot more attention...

What OS are you on
MAC OS 10.13.5
Does this happen from an empty workspace, a single-folder workspace or a multi-root workspace?
Single folder workspace
Do you have files.useExperimentalFileWatcher: true configured in settings?
Tried with and without
What is your configured files.watcherExclude setting?
It isn't set
It reproduces with any folder or workspace you open
yes
The files/folders you open are on your local disk and not on a network share nor a UNC drive
yes, on local disk
The files/folders you open are not behind a symbolic link
Correct, all local
The folder(s) opened use the exact same casing as they are on disk
yes
It reproduces when I make a change to the file from another VS Code window (either from the editor or the file explorer)
didnt try - I kept it simple
I have not tried insider edition - yet
In a simple project with two folders in the project where folder 1 is in master and both folders are is in a branch...
workspace folder

folder 1
folder 2
master has workspace+folder1
branch has workspace+folder1+folder2

If I checkout the branch and npm install in folder2, then checkout master the result is that folder 2 is not removed and contains node_modules. The files in folder2 are removed.
Refreshing the view does no good, presumably because the folders exists on disk.
However, if I checkout master then checkout branch and then back to master without executing npm install then folder2 is removed
It would seem the presence of node_modules is a factor preventing the folder from being deleted.

FWIW - I've been using vscode on OSX for 18 months or so now.  Just today (on the latest version, 1.24.1), I noticed that the file browser wasn't refreshing.  Looking for the issue led me here and in reading the comments I remembered something.  Recently I had experimented with using a workspace, and that workspace had two folders in it.  I didn't like it so I ditched it and went back to the way I normally work, with one exception.  It used to be I would always run "code ." from the directory I wanted to work in, but now I was using "spotlight" and starting vscode and it just happened to open with the files I wanted so....  Except the auto-refresh we're all talking about here wasn't working.  Closing vscode and going back to "code ." from the directory I wanted to work in "fixed" it.
I put "fixed" in quotes because I gather that's not sufficient for what others want, but maybe that little bit of info will help someone else sort it all out...

I open all my projects with $ code ${pathToProject}, so that doesn't change anything for me.
I also don't use workspaces.

@snwflake And are you having the no-refresh issue, or not?  I'm not sure it's relevant, because I just went back and tested various scenarios involving this to see if I could reproduce the broken state I was in before, and I can't.  So my little anecdote above may very well have been this issue, just presenting in as-if it was related to the way code was opened.

@sfrooster I do.
https://github.com/Microsoft/vscode/issues/28432#issuecomment-396839485

First of all, most of the things VSCode is great!
But this a little of a show stopper for me. I have the same problems on macOS, the file explorer does refresh but far from always, it's not reliable, which is a little annoying. If you are running npm in the built-in terminal, it does not refresh.
Also, if you have a lot of folders open and press refresh the whole view reload and selects the row from the top, but does not scroll to the right position so you lose focus.
https://www.dropbox.com/s/fnx6ie45cppij0a/vscode.mp4?dl=0

I have the same problem, it could at least reload files when you collapse and then expand a folder.

Possibly a duplicate: https://github.com/Microsoft/vscode/issues/46058

Still exists. Watching this issue.

Still exists in OSX. Can anyone help to solve?

Same windows 10

Just adding another +1 to the issue occurring on OSX. I have to quit VS Code to get new generated files (protobufs, mocks, etc) to show up in the tree.

Im on 1.29.1 and after committing files, the folder/file names dont change from green/yellow back to gray.  I have to reload for it to notice that they have been committed.

If it helps anyone, I was in the middle of reporting this and I saw this in my settings:

which obviously meant my file watcher was ignoring everything. Not sure how that got there, but clearly the culprit: I removed it and it's working as expected.
Lesson learned: Always double check your settings!

:1st_place_medal:  I found a solution :boom:
:+1: Settings > Check the "Use Experimental File Watcher" Option...
:man_technologist:  Happy Coding :)

@NomanGul I've had that checked for some time. Makes absolutely no difference.

@pauby What is your vscode current version? (mine is 1.30.1)

@NomanGul 1.30.1

In my vscode auto files and git refresh is not working but after check "Use Experimental File Watcher" It's working

@NomanGul I got that from what you'd said. Earlier in this thread (or it may have been another thread) it was advised to check the 'Experimental' setting so mine has been checked for a while now (I'd say at least 6 weeks) with no effect.

Still exists with and without experimental file watching on MacOS

Problem appeared again on Win 10 with the latest stable Code.

Problem never disappeared on macOS...

Strangely enough for me it has to do with the extension GitLens. I don't think it's an issue with vscode because the file explorer updates correctly on the dev build (macos). Once I disable GitLens on my personal install the file explorer updates correctly. Might be something other extensions trigger as well but for me it was GitLens

VS Code: v1.33.1
Windows: v10.0.18362 x64
External file changes are not refreshed as of today.

I found the same issue a few weeks ago and only now I could investigate it further and found something that might be the culprit, at least on my system.
It seems to have something to do with symbolic links.
VC Code: 1.34.0
Linux: Ubuntu 18.04
A few weeks ago, I moved my files from one disk to another and created a symbolic link (ln -s) with the same name as before, but pointing, obviously, to the new location.
It was around that time that I noticed the change in behavior. I thought it was due to an extension I installed, but removing it didn't solve the problem.
So today, I don't know why, I tried to open the file through the full path, not the symbolic link et voilà, everything worked as expected, that is, i could see the coloring on the side of the changed files and auto sync at the GIT SCM view after saving.
I also noticed that opening through the full path, not the symbolic link, made vscode open the folder as if it was opening a new folder since the previously opened files were all closed.
So it looks like the issue is with vscode not being able to work through symbolic links.
As a workaround: always open folders through their full path / mount point, never through symbolic links.
But I'd really appreciate if it was possible to use symbolic links as it would make my folder path much shorther.

So I'm experiencing the same issue. In my use case I am using a go code generation tool (goa) which overrides generated files if they exists. If I start code in verbose mode I see only the Deleted events from the filewatcher. So I think this all happens to fast. If I modify my makefile and run a rm -rf <generated folder> before I run goa everything is fine. It just gives the file watcher some time to actually notice the file changes or not to miss fs events.
Environment:
Version: 1.35.0
Commit: 553cfb2c2205db5f15f3ee8395bbd5cf066d357d
Date: 2019-06-04T01:13:26.790Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 4.15.0-51-generic

After installing MacOS Catalina, file changes are not reflected to the Explorer and add-ons do not get get that information either.
VSC: 1.40.0
MacOS: 10.15.1 (19B88)

After installing MacOS Catalina, file changes are not reflected to the Explorer and add-ons do not get get that information either.

Same here

Any changes on this issue? I am working via ssh using sshfs (remote filesystem) and after any manipulations performed on connected computer changes doesn't appear on mine( After manually refreshing list of files using corresponding button all appears. It makes me sometimes crazy

i created a new file with "touch blahblah.js" and doesn't show up after changes/saving/etc....

I'm having this issue and the behaviour is exaclty what @marvila commented above. If i open a folder that is a simbolic link, my source control file explorer does not update.
Version: 1.40.2
Commit: f359dd69833dd8800b54d458f6d37ab7c78df520
Date: 2019-11-25T14:54:40.719Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Linux x64 4.12.14-lp151.28.32-default

I have renamed a src folder, and now when I do "Go to File..." there is a lot of dead files there. I tried "Refresh File Explorer" and restarting/reloading VSCode. Neither works, I have to try to navigate file and get the error "Unable to read file" then it will update that file (by removing it from index), but not all files.
Is there a way to force refresh all files? I think the watcher isn't working in Windows.

VS Code: 1.42.0
Ubuntu: 18.04
I was getting that notification "Visual Studio Code is unable to watch for file changes in this large workspace" when I opened a laravel project in VS code, and also my file explorer didn't refresh itself when I added a new file. Then I tried this quick solution here, and my file explorer problem was automatically solved.
It might help someone else that has the same problem as me.

Files are not updated when pulling from origin, even after manually triggering refresh of the explorer. Only old version available, though I can diff the commits with git diff HEAD^ HEAD.
I am forced to clone origin once again.

Having a similar issue. My file list does not update for any terminal actions that create new commands:
Version: 1.47.3 (user setup)
Commit: 91899dcef7b8110878ea59626991a18c8a6a1b3e
Date: 2020-07-23T13:12:49.994Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19041
This is on remote WSL2. I can open the folder locally on the filesystem and it works fine. As a somewhat unrelated note, the Linux build also works fine so this issue appears to be related to the WSL remote functionality.

I'm also facing the similar issue with the VS Code. I'm using laravel framework. and whenever I create any file using make:controller anyfilename , in terminal, the file does not get updated in file system of vs code.
Hoping for this bug to be fixed as soon as possible.

VS Code 1.50.0
Windows 10 with WSL 2 and Ubuntu 18.04.
Still having the issue after trying other changes previously suggested.

Version: 1.50.0 (system setup)
Commit: 93c2f0f
Date: 2020-10-07T06:10:52.432Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19041
Windows 10 with WSL 2 and Ubuntu 18.04.
Still having the issue after trying other changes previously suggested.

probably a wsl 2 issue, I have the same problem with Ubuntu 20.04
I also don't have intellisense for npm modules

Version: 1.51.1
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-10T23:31:29.624Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.4.0-7634-generic
I am having a similar issue using Ubuntu 20.04, but it seems to occur only if the file is named .settings
To reproduce the issue:

Create a file named .settings in the root of the project folder from a terminal using touch.
The VSCode explorer will not show the recently added file.
Clicking the refresh button does not show the file either.

Extensions installed:
code --install-extension brenosolutions.sqlformatter
code --install-extension dbaeumer.vscode-eslint
code --install-extension DotJoshJohnson.xml
code --install-extension eg2.vscode-npm-script
code --install-extension golang.go
code --install-extension HookyQR.beautify
code --install-extension Leopotam.csharpfixformat
code --install-extension ms-azuretools.vscode-docker
code --install-extension ms-dotnettools.csharp
code --install-extension ms-mssql.mssql
code --install-extension ms-python.python
code --install-extension ms-toolsai.jupyter
code --install-extension ms-vscode.cmake-tools
code --install-extension ms-vscode.cpptools
code --install-extension redhat.java
code --install-extension sensourceinc.vscode-sql-beautify
code --install-extension uctakeoff.vscode-counter
code --install-extension VisualStudioExptTeam.vscodeintellicode
code --install-extension vscjava.vscode-java-debug
code --install-extension vscjava.vscode-java-dependency
code --install-extension vscjava.vscode-java-pack
code --install-extension vscjava.vscode-java-test
code --install-extension vscjava.vscode-maven
code --install-extension Zignd.html-css-class-completion

I was having this problem because I was in ~/proj1 which was a symlink to /mnt/d/p/proj1 and I typed code . to open vscode.  When I closed vscode and typed cd /mnt/d/p/proj1 && code . vscode behaved fine, so it's an issue with symlinks (for me).

I had the same issue on Fedora 33, Code 1.51.1.
when I opened a workspace, VSCODE notified me with this message:

Unable to watch for file changes in this large workspace.

this link helped me to fix it:
https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc

Having the same issue in Kubuntu 20.04.1.
I recently migrated to Kubuntu. I was using Manjaro and it did not have this problem.
BTW, I see people do "Reload Window" thing. Don't do that, it's a waste of resource and time. Instead, do "Refresh Explorer" which only, well, refreshes file explorer.

Having the same issue in Kubuntu 20.04.1.
I recently migrated to Kubuntu. I was using Manjaro and it did not have this problem.
BTW, I see people do "Reload Window" thing. Don't do that, it's a waste of resource and time. Instead, do "Refresh Explorer" which only, well, refreshes file explorer.

The same issue on windows 10 wsl using ubuntu remote.

An easy way to recreate the problem, use terminal to create a folder in the current directory:

$ mkdir test

The folder does not show up in vscode untill you hit the refresh icon:

@PaulPCIO That is correct, if you want to follow that issue particluarily subscribe to this: https://github.com/microsoft/WSL/issues/4739
Problem is that plan9 doesn't transfer file change events through the barrier. Practically this means you have to live in WSL file system or Windows file system, trying to mix the two will cause problems with dev tools. Personally I hope Microsoft implements real ext4 or linux compatible driver for Windows so that it won't require that hacky Plan9, instead the WSL could appear as real lettered drive without network mapping.

I think this issue has grown sufficiently enough that imho it is no longer possible to figure out each individuals issue people have with the file watcher in VSCode. If there are no objections I would like to close this one and open individual issues that are then easier to track.
Since this issue is specifically around the explorer not showing changes when they happen, I opened https://github.com/microsoft/vscode/issues/126817 to investigate whether we could simply refresh the explorer automatically in certain situations to make the issue less likely to occur.
Some things I want to make clear:

file watching over network shares or symbolic links is provided without guarantee - they may or may not work but will often most likely not work
operating systems may have specific limits in how many file events they can report and may drop events on pressure - this is not really something VSCode can fix without implementing a custom file watcher on each OS that does not rely on native built ins from the filesystem
VSCode is relying on the operating system to report file events (Windows: FileSystemWatcher, macOS: fsevents, Linux: inotify)

If people have specific issues that are easy to reproduce, then please ping here and we can convert them into individual issues top level and further discuss. Please also be aware of other issues already reported: https://github.com/microsoft/vscode/labels/file-watcher
Thanks!

@bpasero When raising the new issues can you link them to this issue, so we can keep track? As you can appreciate this issue was raised over 4 years ago with no movement.

I will do my best 👍


fix:  [ResizableColumns=true In RTL Direction] in FluentDataGrid

🐛 Bug Report
When Change Direction = RTL And in Data Grid ResizableColumns=true
When Move Mouse Left Or Right To move and change the size of the column, they work in the opposite way
💻 Repro or Code Sample
Company.razor
@page "/Company"
@using AppManager.Common.Resources
@using AppManager.Application.Modules.Company.Dtos
@using AppManager.WebAppV1.Common

@attribute [StreamRendering]

<PageTitle> @AppStringResource.CompanyPageTitle </PageTitle>

<FluentCard MinimalStyle="true" Width="100%" Height="100%">
    <FluentDataGrid TGridItem="CompanyDto" AutoFit="true"
                    ItemKey="dto => { return dto.Id; }"
                    ShowHover="true"
                    Data="@_companies"
                    Items="@_companies?.AsQueryable()"
                    Loading="@(_companies == null)"
                    ResizableColumns=true
                    ResizeType="DataGridResizeType.Exact"
<EMAIL_ADDRESS>
        <SelectColumn TGridItem="CompanyDto"
                      SelectMode="DataGridSelectMode.Single"
                      SelectFromEntireRow="true"
                      Property="dto => dto.Selected"
                      OnSelect="@(e => e.Item.Selected = e.Selected)"
                      Filtered="true"/>

        <TemplateColumn Tooltip="true"<EMAIL_ADDRESS>Align="Align.Center" Sortable="false" Filtered="false" Width="50rem">
            <img class="flag"<EMAIL_ADDRESS>alt="Logo @context.Name" />
        </TemplateColumn>

        <PropertyColumn
            Property="@(p => p.Name)" Sortable="true" Filtered="true"
            IsDefaultSortColumn="true" Align="Align.End" InitialSortDirection="SortDirection.Ascending"/>

        <PropertyColumn Property="@(p => p.EnName)" Sortable="true" Filtered="true"
                        Align="Align.End" InitialSortDirection="SortDirection.Ascending"/>

        <PropertyColumn Property="@(p => p.CodeName)" Sortable="true" Filtered="true"
                        Align="Align.End" InitialSortDirection="SortDirection.Ascending"/>

        <PropertyColumn Property="@(p => p.PhoneNumber)" Sortable="true" Filtered="true"
                        Align="Align.End" InitialSortDirection="SortDirection.Ascending"/>

        <PropertyColumn Property="@(p => p.Fax)" Sortable="true" Filtered="true"
                        Align="Align.End" InitialSortDirection="SortDirection.Ascending"/>

        <PropertyColumn Property="@(p => p.Email)" Sortable="true" Filtered="true"
                        Align="Align.End" InitialSortDirection="SortDirection.Ascending"/>

        <PropertyColumn Property="@(p => p.Address)" Sortable="true" Filtered="true"
                        Align="Align.End" InitialSortDirection="SortDirection.Ascending"/>

        <PropertyColumn Property="@(p => p.Description)" Sortable="true" Filtered="true"
                        Align="Align.End" InitialSortDirection="SortDirection.Ascending"/>

        <TemplateColumn Title="Actions"<EMAIL_ADDRESS>            <FluentButton<EMAIL_ADDRESS>IconEnd="@(new Icons.Regular.Size16.Edit().WithColor(Color.Warning))" />
            <FluentButton<EMAIL_ADDRESS>IconEnd="@(new Icons.Regular.Size16.Delete().WithColor(Color.Error))" OnClick="async () => { await OnDeleteAsync(context.Id); }"/>

        </TemplateColumn>
    </FluentDataGrid>
</FluentCard>

@  Code {
public List<CompanyDto>? _selectedItems { get; set; }
public IReadOnlyList<CompanyDto>? _companies { get; set; }

[Inject] private ICompanyService _companyService { get; set; }
protected override async Task OnInitializedAsync()
{
    var result = await _companyService.GetAllAsync(CancellationToken.None);
    if (result.IsSuccess)
    {
        _companies = result.Data!;
        await InvokeAsync(StateHasChanged);
    }
    await base.OnInitializedAsync();
}

private async Task OnDeleteAsync(Guid id)
{
    //var res = await _companyService.DeleteAsync(id, CancellationToken.None);
}
}

🤔 Expected Behavior
The direction of mouse movement and the direction of changing the size of the columns should be in the same direction
😯 Current Behavior
Currently, they are not in the same direction and in the opposite direction
💁 Possible Solution
🔦 Context
Get Data From Database And display With Data Grid in RTL Direction
🌍 Your Environment
FluentUi :   4.10.2
OS Name:     Windows
OS Version:  10.0.19045
OS Platform: Windows
RID:         win-x64
DotNet       8.0.10 X64
Browser :    Chrome Version 130.0.6723.59 (Official Build) (64-bit)
Editor :     Visual Studio 2022 v17.10.5 X64

hi , thanks for new Release.
i checked and This bug has not been fixed yet and it exists in version 4.10.3

You are probably walking int a script being cached too aggressively. Try forcing a hard refresh.
This is what I am seeing on the live demo site:

yes demo site script being cached too aggressively. i refreshed With Ctrl+F5
but in my project it not fix. i think package Microsoft.FluentUI.AspNetCore.Components.Icons depeendecies on v4.10.2 and when installing [Microsoft.FluentUI.AspNetCore.Components v4.10.3]  and then installing [Microsoft.FluentUI.AspNetCore.Components.Icons v4.10.3] it downgrade package Microsoft.FluentUI.AspNetCore.Components to v4.10.2

But you can update to core package 4.10.3 again after that, right?

I first install Microsoft.FluentUI.AspNetCore.Components v4.10.3
Then install Microsoft.FluentUI.AspNetCore.Components.Icons v4.10.3,  but Microsoft.FluentUI.AspNetCore.Components.Icons 4.10.3 need Microsoft.FluentUI.AspNetCore.Components v4.10.2.
Microsoft.FluentUI.AspNetCore.Components.Icons depend on
Microsoft.FluentUI.AspNetCore.Components v4.10.2 not v4.10.3

It is definitely not relevant to this issue.
In the Icons package I see:

So 4.10.2 or later. No idea why it should downgrade the core page

I checked again and this time I first installed the Icons package version 4.10.3 and then the Core package version 4.10.3.
Again, there was the problem of changing the size of the columns
Steps:

Clear Obj Folder
Clear Bin Folder
Install Core Package v4.10.3
Install Icons Package v4.10.3
Check Version Of Packages Core And Icons (Both 4.10.3 )
Rebuild Solution
Run
Check Js Scripts Of (FluentDivider.razor.js , FluentDataGrid.razor.js )

Test Video : https://files.fm/u/rzarkf3jxj

I checked again and this time I first installed the Icons package version 4.10.3 and then the Core package version 4.10.3.

Again, this has nothing to do with the issue. Please don't mix issues

Again, there was the problem of changing the size of the columns
Steps:

Clear Obj Folder
Clear Bin Folder
Install Core Package v4.10.3
Install Icons Package v4.10.3
Check Version Of Packages Core And Icons (Both 4.10.3 )
Rebuild Solution
Run
Check Js Scripts Of (FluentDivider.razor.js , FluentDataGrid.razor.js )

A local script file being cached has nothing to do with obj/bin folder. You can referee to the demo site to see that it is working as it should. If you are seeing different result, check your code please.


fix errorRx to match other APIError

The pattern {.+"error_code":(\d+),"description":"(.+)"} can match the result of json:
{"ok":false,"error_code":400,"description":"Bad Request: message to edit not found"}

but cannot match the one below:
{"ok":false,"error_code":429,"description":"Too Many Requests: retry after 10","parameters":{"retry_after":10}}

So change it to {.+"error_code":(\d+),"description":"(.+).*"}, which can prevent the nil pointer error from happening
https://github.com/tucnak/telebot/blob/319196b8471500baece223be6acfc94a04280226/util.go#L48-L56

Good catch, but actually your expresssion is also wrong:
{.+"error_code":(\d+),"description":"(.+).*"}
I guess .* pattern should be after description quotes:
{.+"error_code":(\d+),"description":"(.+)".*}

Given this situation, I think we should have some tests for extractOk to be sure that regexp is working well. It'll be awesome if you can write some. Something like TestExtract in api_test.go file.
Also, I fixed middleware poller test to satisfy travis build.

Good catch, but actually your expresssion is also wrong:
{.+"error_code":(\d+),"description":"(.+).*"}
I guess .* pattern should be after description quotes:
{.+"error_code":(\d+),"description":"(.+)".*}

Sorry for my mistake before, thank you for help, in this commit, I try to add some tests for extractOK.

Tests are ok. But maybe it's clearer to use assert.EqualError instead of assert.EqualValues?

Tests are ok. But maybe it's clearer to use assert.EqualError instead of assert.EqualValues?

Thank you for pointing this out, I'm trying to meet this.

Similar PR is already merged: #294


Crash on startup while using profiles in kodi

Today i changed to use two profiles in kodi. Artwork Beef (service) has a startup bug cause it tries to get properties via json which will fail until a profile is loeaded. A condition should be added to check if a profile is loaded etc.

Thanks for the report. I can recreate this in Kodi 18 Leia, is that the version of Kodi you are using?
Artwork Beef is configured to start after profile login, but Leia is starting it on application start as well. I'm working on a PR to Kodi that will resolve this for all add-ons.

And here is the PR to Kodi.
Crashing the service is an extreme reaction from Artwork Beef; other add-ons likely react in a different way or just don't access JSON-RPC until later anyway. While Artwork Beef is in beta I like these errors big and loud so I have a better chance to see them.

That PR was accepted, so this shouldn't happen with new Kodi 18 Leia nightlies.


Qt version check

QOpenGLWidget introduce since Qt 5.4.
https://github.com/coin3d/quarter/blob/6297049ae09920e945d8c63671e1d907ecfa8ebb/include/Quarter/QuarterWidget.h#L42-L47

Thanks for your comment. This should read the other way round. QGLWidget has been removed since Qt6 and therefore cannot be used anymore. As QGLWidget provided some additional features that have not been added to QOpenGLWidget we wanted to stick as long as possible to the QGLWidget.

Thanks for reply. Get the point.


Update to work with solidjs v1.7 and typescript v5

I couldn't get this lib to work with the lest solid js version, so had a go at fixing the issues.
I added prettier and eslint, fixed a bunch of minor issues and updated typescript, rollup, vite, etc... There are still a lot of eslint issues, but the remaining ones are mostly not important.
The demo app now works with the latest solidjs version and the jsx errors are gone, but not tested with anything bigger yet.
Only issue that I dind't find a fix for and I'm not happy with my workaround was this:
export type CreateSpringProps<Props extends object = any> = unknown &
  PickAnimated<Props> extends infer State
  ? Remap<
      ControllerUpdate<State> & {
        /**
         * Used to access the imperative API.
         *
         * When defined, the render animation won't auto-start.
         */
        ref?: SpringRef<State>
      }
    >
  : never

This gives a type error Type 'State' does not satisfy the constraint 'Lookup<any>' so I changed to the following just to get it to compiles, but I'm sure it's not correct:
export type CreateSpringProps<Props extends object = any> = unknown &
  PickAnimated<Props> extends infer State
  ? Remap<
      ControllerUpdate & { // previously: ControllerUpdate<State> & {
        /**
         * Used to access the imperative API.
         *
         * When defined, the render animation won't auto-start.
         */
        ref?: SpringRef // previously: ref?: SpringRef<State>
      }
    >
  : never

Trying to integrate this into an app and I'm finding that the types for <animiated.xxx> children are not correct. This was also the case before this PR, but should also be fixed.
<animated.div>
  <Element />
</animated.div>

This gives the following type error: Type 'Element' is not assignable to type 'number | boolean | Node | (string & {}) | FluidValue<NonObject<Element>, any> | AnimatedStyles<ArrayElement> | null | undefined'
I figure the error could be in this code:
export type WithAnimated = ((Component: any) => any) & {
  // (Component: AnimatableComponent): any;
  [K in keyof JSX.IntrinsicElements]: (
    props: AnimatedProps<
      Merge<JSX.IntrinsicElements[K], { style?: StyleProps }>
    > &
      FluidProps<{
        scrollTop?: number
        scrollLeft?: number
      }>,
  ) => JSX.Element

I tried changing  Merge<JSX.IntrinsicElements[K], { style?: StyleProps }>to Merge<JSX.IntrinsicElements[K], { style?: StyleProps; children: JSX.Element }>` But that didn't help.

Thank you so much @garth I forgot I had such a project, do you want to be a maintainer? I can take this project into a new org (for solid-related libraries, like pmndrs)
Let me know your opinnion.

Thanks for the offer, I don't think I understand enough to be a maintainer yet.... you, or someone more experienced with this kind of tech would still need to verify these changes.
I'm in the process of moving some performance critical stuff from react to solid (since react 18 it became much harder to manage render lifecycles). Other than this lib, I didn't find any other suitable animation libs for solid. So it would be really great to resurrect it if possible.
This PR is still a WIP, probably shouldn't be merged at least until the typing issues are resolved. I'm using the updated version internally via pnpm link.

There's no issuess with verifying, I think you're able to handle that anyways.
Sure, let me know when it's ready.

Why didn't I see this!

@Aslemammad any plans on this being merged?

I'd be happy to assign @garth as a maintainer so this get merged and further work would be done on this repo since I do not maintain it myself anymore.

I would be happy to maintain solid-spring if @garth cannot.


platform: Add Corstone-315 (MPS4_CS315) support

Description

Test Steps

Checklist:

[x] I have tested my changes. No regression in existing tests.
[ ] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run formatting

Compared the files being added to the listed files from ARM-software/CMSIS_5 at the specified hash and can confirm that these are identical except for whitespace and the comment about their origin.

@david-hazi-arm Can you add the missing words to the .github/.cSpellWords.txt file?
I can add it myself if you're okay with me pushing to your branch.

@david-hazi-arm Can you add the missing words to the .github/.cSpellWords.txt file?

Done


Release 2.2.4

https://github.com/vorburger/MariaDB4j/issues/105 is a reminder that I really should deploy a new releast to Maven central ASAP...

I'll try to finally do a new release this week, but before that would like to do the following:

@neeleshs or anyone else wrap up https://github.com/vorburger/MariaDB4j/pull/96
fix the  https://github.com/vorburger/MariaDB4j/issues/88 bug re wrong use of annotations
new dump API should not log entire DB [exec setStdOutLogging(false)]
update the release notes in CHANGES

Would anyone using MariaDB4j and watching this repo reading this be willing to help with any of the above?

We very recently started using MariaDB4J and we could really use the setSecurityDisabled() feature, but I have no idea how to help to deploy a new release of anything to maven central.
So I wonder, would you consider "paying you with pizza" a suitable help? :)

@vorburger any update on this issue? Please let me know what I can help with.

I've just pushed 2.3.0 to Maven central, and it should show up there shortly (takes a few hours):
    (...)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1039/ch/vorburger/mariaDB4j/mariaDB4j-app/2.3.0/mariaDB4j-app-2.3.0.pom.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1039/ch/vorburger/mariaDB4j/mariaDB4j-app/2.3.0/mariaDB4j-app-2.3.0.pom.asc (455 B at 2.4 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1039/ch/vorburger/mariaDB4j/mariaDB4j/2.3.0/mariaDB4j-2.3.0-sources.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1039/ch/vorburger/mariaDB4j/mariaDB4j/2.3.0/mariaDB4j-2.3.0-sources.jar (3.0 kB at 4.9 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1039/ch/vorburger/mariaDB4j/mariaDB4j-core/2.3.0/mariaDB4j-core-2.3.0.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1039/ch/vorburger/mariaDB4j/mariaDB4j-core/2.3.0/mariaDB4j-core-2.3.0.jar.asc (455 B at 2.4 kB/s)
    [INFO]  * Upload of locally staged artifacts finished.
    [INFO]  * Closing staging repository with ID "chvorburger-1039".

    Waiting for operation to complete...
    ........

    [INFO] Remote staged 1 repositories, finished with success.
    [INFO] Remote staging repositories are being released...

    Waiting for operation to complete...
    ..........

    [INFO] Remote staging repositories released.
    [INFO] ------------------------------------------------------------------------
    [INFO] Reactor Summary:
    [INFO]
    [INFO] mariaDB4j-pom ...................................... SUCCESS [  5.931 s]
    [INFO] mariaDB4j-core ..................................... SUCCESS [  9.761 s]
    [INFO] mariaDB4j (all-in-one artifact) .................... SUCCESS [01:32 min]
    [INFO] mariaDB4j-app ...................................... SUCCESS [02:26 min]
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD SUCCESS
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 04:15 min
    [INFO] Finished at: 2018-05-15T23:33:09+02:00
    [INFO] Final Memory: 54M/781M
    [INFO] ------------------------------------------------------------------------

If you are using this project, consider supporting it :heart: by donating via PayPal (one time) or becoming a patreon to sponsor to ensure it is actively developed and maintained in the future!  It's also much appreciate if you Star / Watch / Follow on GitHub.


fix: global import

#72  fix register global components.

@chris-zhu should we change the .netify.toml to apply docs/.vitepress/dist, which confict with netilify

#72 fix register global components.

Do you try to remove OnuResolver from vite.config.ts to test whether the global import works normally ?

yeap，I delete onu-ui  under play/src/modules and add onu in main.ts

#72 fix register global components.

Do you try to remove OnuResolver from vite.config.ts to test whether the global import works normally ?
yeap , I delete onu-ui under the play/src/modules and import onu in main.ts,

app.use(onu)

it's work well

Nice fixed.

Ok, I'll take a look later, I think I can optimize the resolver.

@chris-zhu should we change the netlify.toml to apply docs/.vitepress/dist, which confict with netlify

Updated on #87

@chris-zhu should we change the netlify.toml to apply docs/.vitepress/dist, which confict with netlify

Updated on #87

great, I will update it later if that pr had merged,

@chris-zhu should we change the netlify.toml to apply docs/.vitepress/dist, which confict with netlify

Updated on #87

great, I will update it later if that pr had merged,

done

How's the subsequent refactoring going 😄 . @zyyv

resolver

or say, is any proposal for reslover, I wanna do this 😂

resolver

or say, is any proposal for reslover, I wanna do this 😂

https://github.com/onu-ui/onu-ui/issues/72. Here are some temporary todos that you can refer to.

I updated it in the latest code, but it's still a little weird. Do you think this will be a problem?
https://github.com/onu-ui/onu-ui/blob/75c002a45b9df86ab7f069a258985b2a6b2f724b/packages/onu-ui/src/resolver.ts#L6-L9
https://github.com/onu-ui/onu-ui/blob/75c002a45b9df86ab7f069a258985b2a6b2f724b/packages/onu-ui/package.json#L27-L31

I updated it in the latest code, but it's still a little weird. Do you think this will be a problem?
https://github.com/onu-ui/onu-ui/blob/75c002a45b9df86ab7f069a258985b2a6b2f724b/packages/onu-ui/src/resolver.ts#L6-L9
https://github.com/onu-ui/onu-ui/blob/75c002a45b9df86ab7f069a258985b2a6b2f724b/packages/onu-ui/package.json#L27-L31

All components are already exported in the entry, so adding /components may not be necessary.

I updated it in the latest code, but it's still a little weird. Do you think this will be a problem?
https://github.com/onu-ui/onu-ui/blob/75c002a45b9df86ab7f069a258985b2a6b2f724b/packages/onu-ui/src/resolver.ts#L6-L9
https://github.com/onu-ui/onu-ui/blob/75c002a45b9df86ab7f069a258985b2a6b2f724b/packages/onu-ui/package.json#L27-L31

After restore it. It works fine.

fixed #95

Thank you for the discovery, please forgive me for closing it soon. @priority3


Update ariaDownload for V3 products

Hello @alexfore! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file tools/bin/ariaDownload.py:

Line 45:17: E131 continuation line unaligned for hanging indent
Line 100:15: E131 continuation line unaligned for hanging indent
Line 244:80: E501 line too long (80 > 79 characters)
Line 282:80: E501 line too long (80 > 79 characters)
Line 320:9: E303 too many blank lines (2)
Line 338:29: E126 continuation line over-indented for hanging indent
Line 340:29: E116 unexpected indentation (comment)
Line 341:29: E116 unexpected indentation (comment)
Line 342:29: E116 unexpected indentation (comment)
Line 343:29: E116 unexpected indentation (comment)
Line 344:29: E116 unexpected indentation (comment)
Line 345:29: E116 unexpected indentation (comment)

This was just for testing


Copy process too slow - how to permanently stop?

Hello all,
I've been using this excellent app to copy approximately 1400 folders containing 6800 files. The permissions need to remain intact so I ticked that box. The copy process is so slow that it's been at it for 4 days (ie, 4x 90 minute sessions) and only copied 1124 files. Unfortunately, this is within a work environment and I need to have ALL the folders and files copied by the end of today. Clearly this is not going to happen and a decision has been made to abandon the copying process.
Question: As the copying process restarts automatically every 24 hours, how do I permanently stop the process? Is it as simple as hitting pause and then deleting the app?
I'm grateful for any and all information you can share.
Thank you.
Dan

Yep just press the Pause button in the app. After you get a success message, you should see the copy log pause momentarily.
Deleting the app just amounts to removing permissions, which you are free to do at any time.


Content for scan-status command

Lists all the users in a server with links/invites/profanity in their activity/status.
Feedback on the code is welcome, I can fix things.

What does the neutral check mean?

It will be reviewed by someone else like Juuzoq or Frostii hopefully
it looks good to me but immediatetly after I pull request it maybe, I will be making changes.


Add JSON-LD to the list of minified types

JSON-LD is is a standardized format for providing information about a page and classifying the page content. In my use case I am using it for Google SEO.
In this pull request I've changed the minifier mediaTypes regex to allow for application/ld+json.
I wasn't able to find any tests for this section of code and I'm still pretty new to go so I'm unsure of how to add one.

I suspect you meant to attach this to the JSON minifier?
You can create application/ld+json as a custom mime type in your project and it will be minified. We may add a regexp to catch more JSON variants out of the box, but I think that needs to be less ad-hoc and with tests.


DRAFT add lint for css files

on-going draft to add lint for css files
Signed-off-by: SaeHie Park<EMAIL_ADDRESS>

htmlhint doesn't seem to check valid html attributes or extra spaces (usual html does)
but it does catch missing " like in

<meta nameeee="viewport content="width=device-width, initial-scale=1" />

done


Bump kube-burner version

Signed-off-by: Raul Sevilla<EMAIL_ADDRESS>Description
Changelog:
https://github.com/cloud-bulldozer/kube-burner/releases/tag/v0.17.2
Fixes

/rerun all

/rerun all

Results for e2e-benchmarking CI Tests

Workload
Test
Result
Runtime

router-perf-v2
./ingress-performance.sh
PASS
00:09:47

etcd-perf
./run_etcd_tests_fromgit.sh
PASS
00:02:22

scale-perf
./run_scale_fromgit.sh
PASS
00:11:42

network-perf
GEN_CSV=false ./run.sh
PASS
00:05:40

kube-burner
WORKLOAD=cluster-density ./run.sh
PASS
00:04:02

kube-burner
WORKLOAD=node-density ./run.sh
PASS
00:03:20

kube-burner
WORKLOAD=node-density-heavy ./run.sh
PASS
00:03:59

kube-burner
WORKLOAD=pod-density-heavy ./run.sh
PASS
00:03:41

kube-burner
WORKLOAD=max-services ./run.sh
PASS
00:06:12

kube-burner
WORKLOAD=max-namespaces ./run.sh
PASS
00:06:41

upgrade-perf
./run_upgrade_fromgit.sh
PASS
00:00:37


Add markdown() method to Response class

This implements the feature requested in issue #339. I've added a new markdown() method to the Response class. This method extracts markdown text from the response content, making it easier to work with LLM-friendly formats. used BeautifulSoup and html2text libraries, which are now optional dependencies.

Cool, thanks.
We need to add these dependencies as an optional dependency group in pyproject.toml and add unit tests for this method.
Besides, I would like to add readability-lxml and lxml as another extract engine.


Using libtensorflow-core.a to enable training on Android

I followed : https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/makefile/README.md
to build the tensorflow library for Android. Does the lib file contain all the functionalities to enable training on Android by using c++ to call the library.

This path is effectively deprecated. Is there a reason you cannot use bazel?

I want the whole tensorflow library for android which includes ops for
training as well, hence trying this method. The present process of building
for Android using Android studio or bazel supports only inference, right?
On Thu, Aug 22, 2019 at 10:58 PM Jared Duke<EMAIL_ADDRESS>wrote:

This path is effectively deprecated. Is there a reason you cannot use
bazel?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/31829?email_source=notifications&email_token=AM6VNC7UH3HLYTXQZIPLA53QF3EDHA5CNFSM4IODHRRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD45ZFCY#issuecomment-523997835,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM6VNC3O5GLEMQVP5KUNLQDQF3EDHANCNFSM4IODHRRA
.

try ndk14b , makefile only supports ndk14b as there are headers changes in later ndk, but there is huge performance impact using this ndk , i am trying to compile using latest ndk20 .

Training support with TensorFlow Lite is in active development, @miaout17 can offer additional updates.

Hi @ghost!  Have you checked the recently introduced On-Device training document from the 2.8 version?


Espresso import issues

Details about the quacc environment

quacc version: 0.5.0+
Python version: 3.9+

What is the issue?
There are now several Espresso import issues preventing usage of quacc. See here.
CC @tomdemeyere.
How can we easily reproduce the issue?
# Paste your *minimal* example code here

Will be addressed by https://gitlab.com/ase/ase/-/merge_requests/3201.


Custom legend

Hello,
Is there a way to generate a custom legend? Such as via the generateLegend() function: https://vue-chartjs.org/api/#generatelegend
Or any other way?
Thank you.

We give access to the 'options' object
https://coreui.io/vue/docs/components/charts.html
legend is defined inside the options
https://www.chartjs.org/docs/latest/configuration/legend.html

Hi,
Thanks, I knew about the options object, but I was not sure where/how to reference it. So just for anyone who struggles, here is a solution:
First, you need to assign $ref attribute to the chart component e.g. <CChartDoughnut ref="jobsGraph" :datasets="defaultDatasets" :options="graphOptions" />.
Inside graphOptions object in data() define legendCallback: function (chart) {} (in case you want a custom structure/style for the legend).
And eventually just call/assign (this is the tricky part - it took some time to find the right chart object): this.customLegend = this.$refs.jobsGraph._data.chart.generateLegend(); inside mounted() and pass the HTML code to an element:

Hope this helps ✌

Isn't it simpler to just pass
:options="{legend: ...}"


Knights Tour Problem in Java

Is your feature request related to a problem? Please describe.
Function to calculate and  print all configurations of the chess board representing the route of knight through the chess board.
Describe the solution you'd like
A clear and concise Solution using backtracking .
Do you want to work on it
Yes, I am a GSSOC'21 participant I would like to solve it in Java.

Please assign it to me . @nakul-19 @raksha009 @plazzy99 @tarun26091999 @rish-singhal @yasharth291 @Rohan27s @rudrakshi99

Please assign it to me. @nakul-19 @raksha009 @plazzy99 @tarun26091999 @rish-singhal @yasharth291 @Rohan27s @rudrakshi99, I am a GSSOC'21 participant I would like to solve it in C++

Please assign this to me in Python

@tarun26091999 can u please assign me


Refactor- Fiber, FiberCache and OapIndexType

What changes were proposed in this pull request?

Add toFiberCache function
Add FiberType
AnyIndexType -> OapIndexType
Extract Fiber, FiberCache to new files

How was this patch tested?
Existing tests.

LGTM

Thanks @linhong-intel