text:
CalDAV Integration

CalDAV Integration
Hey there,
I recently found your App in the Gnome Software center and I love it. It's simple, and does what it has to do.
The only thing I'd wish for is an integration with the Nextcloud Tasks App. It would help me sync everything across my devices, so I wanted to ask if there are any plans for something like that.

Hello! I've never used Nextcloud before, so I don't really know how it works. I will look into that! Syncing is a good idea, so I can try to make it work.

Hello! I've never used Nextcloud before, so I don't really know how it works. I will look into that! Syncing is a good idea, so I can try to make it work.

You could integrate it with GNOME (which supports Nextcloud Tasks) like Endeavour (https://gitlab.gnome.org/World/Endeavour) does.

I actually stopped using Endeavour because it constantly crashes. Literally, it closes when it's idle.

Hello! I've never used Nextcloud before, so I don't really know how it works. I will look into that! Syncing is a good idea, so I can try to make it work.

You could integrate it with GNOME (which supports Nextcloud Tasks) like Endeavour (https://gitlab.gnome.org/World/Endeavour) does.

I actually stopped using Endeavour because it constantly crashes. Literally, it closes when it's idle.

Same here. That, and the fact that sync also doesn't work properly, is the reason I thought about this one here.

Second the GNOME integration. Endeavor simply doesn't work. The only other simpler client is "Remembrance" but it hasn't been touched by the dev since May, and it only syncs with Microsoft ToDo.

Probably this should be renamed to CalDAV support? Nextcloud Tasks doesn't have an API per-se.

Little update on the issue. I'm planning to add Nextcloud sync in the next couple of updates. I'll try to add Todoist sync option too.

That is great news :)
Keep it up!

Little update on the issue. I'm planning to add Nextcloud sync in the next couple of updates. I'll try to add Todoist sync option too.

If you're integrating CalDAV, will this work for the default provider in GNOME, or only specifically enabled services?

I think this will be a setting for each provider, because not everyone is using GNOME, and this way I can make sync with multiple providers at the same time if needed.

Hi, thank you for you app :) it would be nice supporting also Google Keep, if possible :+1:

Hi, thank you for you app :) it would be nice supporting also Google Keep, if possible 👍

You can open new issue for it, I'll look into that.

Hello everyone! I've pushed all of the sync code into main branch. I think it's working now, but if you can test it and report any problems, I would be happy to fix them :) You can use instruction in the README for that. Logs located at ~/.var/app/io.github.mrvladus.List.Devel/data/list/log.txt and ~/.var/app/io.github.mrvladus.List.Devel/data/list/log.old.txt for previous launch of the app.

Hello everyone! I've pushed all of the sync code into main branch. I think it's working now, but if you can test it and report any problems, I would be happy to fix them :) You can use instruction in the README for that. Logs located at ~/.var/app/io.github.mrvladus.List.Devel/data/list/log.txt and ~/.var/app/io.github.mrvladus.List.Devel/data/list/log.old.txt for previous launch of the app.

Awesome, thanks!
I just started testing it – as I understand it, Errands will NOT synchronize with currently existing calendars/lists, but it will use only “Errands” calendar that is created (if it doesn't exist) during first sync, correct?
If yes – is that the final approach/design, or maybe do you plan in some future to operate on multiple calendars/lists (including sync currently existing ones)?

Correct! It will only use Errands calendar. It is not a full CalDAV client for now :) Because it only has one list of tasks. But I have plans to add creation of multiple lists and therefore it would be possible to do full sync of calendars.

I am just testing it and it works very smoothly!
Thank you so much, a tool like that was really missing from the gnome desktop (since endeaver is broken beyond repair).
Some ideas for improvement:

Add a button to test the nextcloud connection below the settings.
Automatically try to add https:// to the server URL if the user does not enter it
For as long as you don't have that option to sync multiple lists, let the user specify that one list to sync (enter a name, default option could be Errands)

Also, are you planning to implement some of the caldav task attributes like priority, start date, end date, % completed and so on?
It would be nice to make use of the colors somehow. Maybe have an optional connection high priority = red, medium = yellow or so.

Thank you for feedback!

Add a button to test the nextcloud connection below the settings.

Added Test button

Automatically try to add https:// to the server URL if the user does not enter it

Added, but only http:// (not everyone setting up SSL)

For as long as you don't have that option to sync multiple lists, let the user specify that one list to sync (enter a name, default option could be Errands)

Added calendar name field

Also, are you planning to implement some of the caldav task attributes like priority, start date, end date, % completed and so on? It would be nice to make use of the colors somehow. Maybe have an optional connection high priority = red, medium = yellow or so.

I didn't think about that, but it's not difficult to implement in the future

Wow thank you, that was quick. :+1:

I've added sync option for "Other CalDAV Provider" for anything other than Nextcloud, but be careful - it needs full DAV url, for example: https://www.google.com/calendar/dav/

Sorry for the late answer to this thread, but i was a bit busy the last week. I now tried sync the first time and it works like a charm! If I encounter any bugs I'll open an issue!

Thousand thanks for integrating this! I was looking for a years for an app like that :purple_heart: :pray:
Just downloaded the latest release via flathub and tried to connect to my nextcloud; entered the Data and clicked on Test; got the following error:

(which doesn't really say much)
also the newly appeared sync button in the main window doesn't do much/anything: task list stays empty
same when I switch Sync Provider from Nextcloud to CalDav.
Would love to provide some logs; is there any way to do so?

logs at ~/.var/app/io.github.mrvladus.List/data/list/

Hi,
I would like to report a bug in the Nextcloud sync - after configuring it in Preferences and clicking "Test" button,  "Connected" message pops up, but in the log I found the following:
[DEBUG] Initialize sync provider
[INFO] Initialize Nextcloud sync provider
[INFO] Connected to Nextcloud server at 'https://<domain>/remote.php/dav/'
[ERROR] Can't connect to Nextcloud server at 'https://<domain>/remote.php/dav/'

I am using fresh Flatpak installation of Errands v45.0.3 on Kubutnu 23.04. Nextcloud version is 27.1.1.

@dehahost it's fixed in 45.0.4. Update will be on flathub in a couple hours

awesome! thank you @mrvladus :rocket:
when I try to connect now (provider=nextcloud) I receive a connected notice. However, I still need to test it since I don't see any tasks or lists yet when I sync, but this could also be a problem on my end.
just for understanding: does Errands support multiple lists (= multiple calDAV calendars) at the moment? or will it try to find a "default" task list on nextcloud instead?

@moedn
In the next release I'll make sync button appear in the header bar as soon as sync provider is selected so it won't be necessary to test connection or reload the app.
For now it only supports one calendar, by default it will create calendar named "Errands" if calendar name field is empty. You can change or create calendars by changing this field. I will work on this. Multiple calendars support is the next major release priority.

Awesome! multiple calendars support would be a crucial feature for me :pray:
just wanted to test it on a nextcloud calendar, but for some reason the app refuses to load now; opened a new issue on this (#81)

Little update on the issue. I'm planning to add Nextcloud sync in the next couple of updates. I'll try to add Todoist sync option too.

is Todoist sync list on the upcoming features list?

@i2sage not yet. For now I'm focused on full CalDAV integration. I'm still planning to do it in the future ;)

authors: Baumistlustig Julian4711 LSeelig dehahost ekasprzak gremo i2sage moedn mrvladus rafaelmardojai snydox

repo: mrvladus/Errands


text:
Custom input-ipc-server setting breaks the script

I am using custom input-ipc-server settings.
input-ipc-server=\\.\pipe\mpvsocket
I get this error.
Error: connect ENOENT \\.\pipe\\.\pipe\mpvsocket
Immersive (another script that I use) also apparently depends on these settings but it works fine.

I just published a new version that should fix the issue.
npm install --global webtorrent-mpv-hook@1.3.2

Tested just now and I can confirm that it's working. Thanks.

source: gharchive/issue

repo: mrxdst/webtorrent-mpv-hook

license: Unlicense

license_type: permissive

license_source: github-api


text:
Superclasses, Children and unexpected results (self is not what it should be)

Hi there!
First, thanks a lot for your work! :green_heart:
Problematic Script
require "docile"

class Parent
  attr_reader :children

  def initialize
    @children = []
  end

  def add_child(clazz, &block)
    child = clazz.new
    children << child

    Docile.dsl_eval(child, &block) if block
    child
  end
end

class CustomParent < Parent
  def do_stuff
    add_child Parent do
      wanna_be_custom
    end
  end

  def wanna_be_custom
    add_child CustomParent
  end
end

parent = CustomParent.new
parent.do_stuff

p parent.children

Actual Output
Both Children are added to the main parent/within the block self isn't shifted to the child
[#<Parent:0x000055794759c598 @children=[]>, #<CustomParent:0x00005579475ab7a0 @children=[]>]

Expected Output
the main parent has one child, which itself then has the CustomParent as a child. (within the block self correctly is the child)
[#<Parent:0x000055d997c50460 @children=[#<CustomParent:0x000055d997c5b658 @children=[]>]>]

This output can currently be achieved in 2 ways:

inline wanna_be_custom

  def do_stuff
    add_child Parent do
      add_child CustomParent
    end
  end

in add_child, instead of instantiating the passed in class just use self.class (yes this changes semantics but might give a hint as to the source of this)

  def add_child(clazz, &block)
    child = self.class.new
    children << child

    Docile.dsl_eval(child, &block) if block
    child
  end

Might be related to https://github.com/ms-ati/docile/issues/31 but it's marked fixed :man_shrugging:
edit: After a good night sleep I finally realized that of course this is about self being the wrong thing so much like #31 ;)

Hi @PragTob, thanks for such a thorough and well-researched bug report! And such an appreciative and friendly tone 😃! I'll be happy to take a look and see if I can help

@PragTob this is tricky because it's at the intersection of a couple different behaviors of docile, isn't it?
Observing that wanna_be_custom is only defined on CustomParent,  but NOT defined on Parent: what is the expected behavior of CustomParent#do_stuff:
add_child Parent do
  wanna_be_custom
end

In english, I'm reading this as:

Create an instance of the class Parent, and treat it as a DSL
Call wanna_be_custom from that DSL, which is NOT a method of Parent

In this case, docile has a feature which is called "falling back to block context", which is to go back to where the block was defined, and see if the missing method was available there.
In this case, it is going back to the instance of CustomParent where do_stuff was called, and successfully finding wanna_be_custom there.
Based on my current understanding, this appears to be expected behavior, and is covered by the unit specs here: https://github.com/ms-ati/docile/blob/master/spec/docile_spec.rb#L123-L208

The intent of the code working this way, is that it's possible to extract "helper methods" from the call site of a DSL block, if that makes sense. Are you seeing this differently -- is there a way to change the test case to more closely match a real-world use case you are seeing?

Or is the feature request here:
Given a block context and a DSL object which BOTH implement the same method foo (in this case #add_child)
When we call a helper method that falls back to the block context (in this case #wanna_be_custom)
And the helper method itself calls the method foo which exists in both block and DSL contexts
Then we expect the helper method's call of method foo to target the DSL object rather than its current  fallback block context

Sorry, I know this can be made clearer above, we'll need to adopt some clearer terminology here. But is this where the difference in expectation stems from?

@ms-ati hey, thanks for the great work and all the work investigating it :)
It might be too specific of a use case to have it solved in a general library. In my specific use case what I want is that even if the method is defined only in the "parent" that it should be called but the children should still be added to the "child".
Let me look up my test case...
basically this (taken from: https://github.com/matestack/matestack-ui-core/commit/ac16b3e865ec9285acc024970f7ce297ae4d523a):
          def body
            button do
              warning_text
            end
          end

          def warning_text
            plain "WARNING! WARNING!"
          end
        end

It's an HTML DSL. Within the button (child) I want to call a method defined in the parent warning_text and its children should be added to the button (child).
I think in the end your description from above may be right, as in the end both methods resolve to add_child (i.e. button is defined roughly as add_child ButtonClass, *args, &block - same thing for every other DSL).
So... that might be the feature request in there.
But no hurries/worries I have it implemented & working myself right now. It might be too specific of a use case anyhow (although I had hoped docile would magically solve it all for me :grin: ) as the DSL I'm trying to reimplement right now does have its specifics.
Anyhow, thanks a lot for your help! :green_heart: :tada: :dancer:

Thanks @PragTob. Ok, I understand the feature request. This issue is ONLY when a helper method defined in the block's context calls an instance method which is available in both the DSL and block's contexts.
The feature request is, in these cases, to choose to call the DSL object's method from the call-site in the block's context helper method instead of the method with the same name int he block's context.
Yes?

Also: I would like for Docile to be useful for what you are attempting to build in matestack - a powerful multi-level DSL - so I am motivated to dig into this with you, and see if Docile can be more helpful without breaking any other use cases.

@PragTob The challenge to this feature request is that our current implementation of falling back from helper methods in the block's context, back into the DSL object, is based on instrumenting method_missing, see: https://github.com/ms-ati/docile/blob/master/lib/docile/fallback_context_proxy.rb#L51-L62

I vaguely plan for a future Docile 2.0 to be based on never instrumenting method_missing, or in any way mutating the contexts, and instead to use the technique of purely constructing new proxy objects that are based on the methods of the DSL and block contexts. This would be easier to solve with that putative future implementation 🤷♂
But for now, I can noodle a bit on seeing if there's a way to make this work in the current implementation.

@ms-ati thanks a bunch!
The plans for Docile 2.0 sound exciting and are vaguely how I thought it already worked tbh (I didn't really dig into the code base yet, just saw the construction of some proxy objects and thought that was a very neat and cool way to go about it :ok_hand: ).
Thanks a lot, and as always - no pressure this is all OSS/free time activity :)

Tagging this issue as a feature request intended for Docile 2.0

Tagging this issue as a feature request intended for Docile 2.0

authors: PragTob ms-ati

repo: ms-ati/docile

license: mit

license_source: bigquery


text:
🛑 Do53 Roost IPv6 TCP is down

In b1a517a, Do53 Roost IPv6 TCP (http://107.189.10.142:9205) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Do53 Roost IPv6 TCP is back up in 270afe3 after 37 minutes.

repo: mschirrmeister/upptime-loopx

license: MIT


text:
🛑 Do53 Roost IPv4 UDP is down

In 22d5be6, Do53 Roost IPv4 UDP (http://107.189.10.142:9202) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Do53 Roost IPv4 UDP is back up in 42cb56c after 30 minutes.


text:
setting meta infos

close #66
📄 What I've done
setting meta infos for sharing and etc.
⛱ Major Changes

Add infos in public > index.html
Do you think we need to care about SEO?

🙋 Review Points

need to check after deploy

When it comes to SEO, is it necessary to put keywords in the meta tag? Is it a story that comes out of a question?
I think most of the searchable content we have will be in the name of Icon, so SEO won't be very important in our project, but... wouldn't it be nice to have it?!

When it comes to SEO, is it necessary to put keywords in the meta tag? Is it a story that comes out of a question?
I think most of the searchable content we have will be in the name of Icon, so SEO won't be very important in our project, but... wouldn't it be nice to have it?!

Ok, then I will note this in notion and pass through :)

source: gharchive/pull-request

authors: msdio userJu

repo: msdio/stackticon


text:
Add get! function

Add the get! function and adds a test of both get and get!.
Matt, I think you said something about a conversion being needed, but I reasoned that the Dictionaries library will handle this internally? Or did you mean a conversion of the edge or vertex types?

Ideally we would rely on whatever conversion is done by Dictionaries.jl.

Yes, great. That's what I thought too.

Looks good, thanks!

authors: emstoudenmire mtfishman


text:
🛑 https://scout.ps is down

In 233bac4, https://scout.ps (https://scout.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://scout.ps is back up in 84d16cb.

repo: mtitservice/site


text:
🛑 https://ftp.mtit.pna.ps is down

In f01a9a5, https://ftp.mtit.pna.ps (https://ftp.mtit.pna.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://ftp.mtit.pna.ps is back up in e71c8da.


text:
🛑 https://www.perc.ps is down

In c400a27, https://www.perc.ps (https://www.perc.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://www.perc.ps is back up in e796dd5.


text:
🛑 https://detulkarm.edu.ps is down

In 4fedd7e, https://detulkarm.edu.ps (https://detulkarm.edu.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://detulkarm.edu.ps is back up in fed5ab6.


text:
🛑 https://www.perc.ps is down

In 727036e, https://www.perc.ps (https://www.perc.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://www.perc.ps is back up in 54a475a.


text:
🛑 https://palcp.ps is down

In 90762ac, https://palcp.ps (https://palcp.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://palcp.ps is back up in 5c242e8.


text:
Unable to run ludusavi error on Playnite 10.32

Playnite, ludusavi, and the plugin are all the latest version & ludusavi runs standalone just fine, but playnite can no longer backup any saves with it, always giving the same error of unable to run ludsavi.

Hi! I'm not able to reproduce this. Could you upload a copy of your extensions.log from Playnite?

extensions.log
extensions.00000.log
I found two of them.
in extensions.00000.log I found some related entries to ludusavi, here you go:
07-11 20:19:28.205|DEBUG|LudusaviPlaynite#LudusaviPlaynite:Ludusavi could not be executed
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at LudusaviPlaynite.LudusaviPlaynite.RunCommand(String command, String args)
   at LudusaviPlaynite.LudusaviPlaynite.InvokeLudusaviDirect(Invocation invocation, Boolean standalone)
07-11 20:19:28.205|DEBUG|LudusaviPlaynite#LudusaviPlaynite:Ludusavi exited with -1 and invalid JSON content
System.ArgumentNullException: Value cannot be null.
Parameter name: value
   at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
   at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
   at LudusaviPlaynite.LudusaviPlaynite.InvokeLudusavi(Invocation invocation)

Could you try opening Command Prompt and running these commands?
set RUST_BACKTRACE=1
C:\Games\ludusavi.exe --try-manifest-update find --api --backup -- "Baldur's Gate III"

That's the last command that failed in extensions.log:
30-12 16:12:56.526|DEBUG|LudusaviPlaynite#LudusaviPlaynite:Running Ludusavi: --try-manifest-update find --api --backup -- "Baldur's Gate III"
30-12 16:12:58.985|DEBUG|LudusaviPlaynite#LudusaviPlaynite:Ludusavi exited with 101 and invalid JSON content

Here's what came up.

(c) Microsoft Corporation. All rights reserved.

C:\Users\Dark>set RUST_BACKTRACE=1

C:\Users\Dark>C:\Games\ludusavi.exe --try-manifest-update find --api --backup -- "Baldur's Gate III"
thread 'main' panicked at src\scan\layout.rs:442:44:
called `Result::unwrap()` on an `Err` value: Error { kind: InvalidData, message: "stream did not contain valid UTF-8" }
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

C:\Users\Dark>
C:\Users\Dark>set RUST_BACKTRACE=1

C:\Users\Dark>C:\Games\ludusavi.exe --try-manifest-update find --api --backup -- "Baldur's Gate III"set RUST_BACKTRACE=1
thread 'main' panicked at src\scan\layout.rs:442:44:
called `Result::unwrap()` on an `Err` value: Error { kind: InvalidData, message: "stream did not contain valid UTF-8" }
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

C:\Users\Dark>C:\Games\ludusavi.exe --try-manifest-update find --api --backup -- "Baldur's Gate III"

After a few tries, nothing comes up anymore.

Thanks, that narrows it down. Somehow, one of the mapping.yaml files from your backups got into an invalid state, but I'm not sure how that could be. Do you have any other scripts/plugins that might have modified the backup folder?
Since it suddenly started working, it seems that the file either disappeared or got fixed, so you should be okay for now, but let me know if you still have any issues in Playnite.
I'll definitely update Ludusavi so that this kind of error doesn't make the whole program crash. I'm just not sure how the issue appeared in the first place.

Well, it still doesn't work on my end even if if the cmd does, I still get the same errors in Playnite regardless of which game I'm trying to backup.
If it's any hint to how this happened, I think it started happening around the same time I re-attached several storage drives that weren't in use prior to installing ludusavi/playnite, one of which had an older version of ludusavi on it (without playnite).

Update, your hint about mapping.yaml got me to figure out that changing the directory in which saves are stored (from C:\Users\Dark\ludusavi-backup to C:\Users\Dark\ludusavi-playnite) seems to fix it fully for me, now backing up works via Playnite just fine!
I'm not sure if I should close the issue since my problem was resolved or leave it open since the root of it is still to be fixed though!
I'll leave it open for you to do with it as you see fit, thank you for helping out with this. :)

Glad you found a solution that works for you :)
If you'd still like to troubleshoot your original backups and get them working, then you can try this build with a fix for the "did not contain valid UTF-8" crash:
ludusavi-v0.22.0-post.6+4489f49-win64.zip
If you still see issues in Playnite with that build, then I'd like to see the updated extension.log from Playnite and a copy of %APPDATA%\ludusavi\ludusavi_rCURRENT.log (if it exists).

Sure, I'll try it out and set the old backups! Will update when I do.

Update, the new build works with the old backups, so all is well!

Great! Thanks for confirming.
If you're curious which specific backup is corrupted, then %APPDATA%\ludusavi\ludusavi_rCURRENT.log should have a line like Ignoring unloadable mapping: with the path to the relevant game. I can try to help salvage it if you send me the game backup folder, or if you're not too worried about it, then you could just delete the folder for that game's backups.

Ah, it was a random save game for Metro 2033, that's totally fine with me to get rid of but thank you for the offer! Your software is the best at keeping backups of my saves really. :)

authors: Darkcitrus mtkennerly

repo: mtkennerly/ludusavi-playnite


text:
Add "Run Query" button to the Editor Groups bar for SQL files

It would be nice to have a ▶-like button on the right corner of the editor groups bar to execute the current SQL file.
I also made this keybind to quickly execute the command, as there is no default one, also a nice addition for a future version.
{
	"key": "f5",
	"command": "SQLTools.executeQueryFromFile",
	"when": "editorFocus && editorLangId == sql"
}

I would rather prefer:
{
        "key": "F5",
        "command": "sqltools.executeQuery",
        "when": "editorHasSelection && editorFocus && editorLangId == 'sql'"
    },
    {
        "key": "F5",
        "command": "sqltools.executeQueryFromFile",
        "when": "editorHasSelection == false && editorFocus && editorLangId == 'sql'"
    }

Then, when we have something selected it will run only the selection, else it will run the whole file.
I agree this is almost a must have feature, since F5 is pretty much the standard for running/debugging code. Since debugging doesn't make sense for SQL, F5 is pretty safe keybinding.

authors: caiohamamura cesarep

repo: mtxr/vscode-sqltools


text:
format the sql with inline values

Issue Type

[ ] Bug
[x] Enhancement
[x] Feature Request
[ ] Question
[ ] Other

Prerequisites (For bugfixes)

[x] Are you running the latest version?
[ ] Did you check the logs?
[ ] Did you check the Setup?

Description
I've get the sql command like insert a(k,k,k) values (a,a,a),(b,b,b),(c,c,c);
Once I formatted the sql commands, it ran out
insert into
  a (
    k,
    k,
    k
  )
values
  (
    a,
    a,
    a
  ),
  (
    b,
    b,
    b
  );

is there anyways to format the commands to
insert into a(k,k,k) values
(a,a,a),
(b,b,b);

Steps to Reproduce (For bugfixes)

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Versions

Version:v0.13.0
OS: MacOS
SGDB: MySQL

You can get this information from executing SQLTools: Version from VSCode Quick Open.

 New card

Will be fixed in v0.15.1 as seen here:

authors: favorinfo mtxr


text:
docs: use gofmt to integrate

we can simply use gofmt and go mod tidy to migrate :D

One issue here is that the package name in coral is still defined as cobra (to minimize the changes and merging effort). This change would expect the package to be named coral however.

One issue here is that the package name in coral is still defined as cobra (to minimize the changes and merging effort). This change would expect the package to be named coral however.

ah, right, let me fix that

repo: muesli/coral


text:
Getting ListItemText to inherit color is a pain

[x] This is a v1.x issue (v0.x is no longer maintained).
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

I wish it were this easy:
<ListItemText color="inherit">Inherited Color</ListItemText>

Current Behavior

I have to do:
<ListItemText><Typography color="inherit">Inherited Color</Typography></ListItemText>

This is a pain.  I could create a wrapper component that inherits the color, but that would also be a pain.  Most Material UI components make it nice and easy to inherit the color.
Context

I have a sidebar containing <ListItems> with a dark background, so I want all of the <ListItemText> to be white, and it would be nice to be able to just inherit the white foreground color of the sidebar.
Your Environment

Tech
Version

Material-UI
v1.2.1

I have to do:

You also have to add disableTypography .

Ah, I hadn't even tried, I was just guessing.  So it takes even more text to do.
As a side note, I wish there were some magic way to reference the JSS class name for the ListItemText and Typography within the styles for my sidebar...then I could override the color there and it would be fairly clean.  Maybe I can eventually think of a way to make that possible and propose it as a new feature in JSS.

So I'm basically wishing we could add a color property to ListItem that gets forwarded to the primary Typography it renders.  However, we would also need to handle the color in the case that disableTypography is true.  What do you think?

@oliviertassinari at the very least it would be helpful to have primaryProps and secondaryProps, in the same vein as inputProps on an Input component.

I wish there were some magic way to reference the JSS class name for the ListItemText and Typography within the styles for my sidebar

If I understand correctly what you are looking for. This should work:
<ListItemText classes={{ primary: 'your class' }} />

it would be helpful to have primaryProps and secondaryProps

I have no objection to adding a primaryTypographyProps and secondaryTypographyProps property 👍 .

@oliviertassinari but you're not open to a color prop that gets forwarded to the typography?  I have a working clone of ListItemText that does that in my own project, so I could PR it pretty quickly...

@oliviertassinari by the way, rendering <Typography> inside of <ListItemText disableTypography> would probably confuse the heck out of people who are just getting started in a project that uses Material UI:
<ListItemText disableTypography>
  <Typography color="inherit">Test</Typography>
</ListItemText>

It's not very elegant.  We could check if the user passed in their own <Typography> and if so, not require them to use disableTypography.

@jedwards1211 No, I think that it's too specific. Yeah, you can clone or wrap the component.

by the way, rendering  inside of  would probably confuse the heck out of people who are just getting started in a project that uses Material UI:

It's a good point. We might even make this behavior the default, so people don't have to provide disableTypography at all.

I agree with @oliviertassinari that primaryTypographyProps and secondaryTypographyProps` properties is the way to go for flexibility.
If we added color, we'd also then need secondaryColor, and there might still be the need for the typography props for some other use-case, so we potentially end up with four new properties.

Okay.  I wish there could be a PrimaryListItemText component, but unfortunately there would be no magic way to make the secondary text display underneath the primary text in an API like this:
<ListItem>
  <PrimaryListItemText color="inherit">Primary</PrimaryListItemText>
  <SecondaryListItemText>Secondary</SecondaryListItemText>
</ListItem>

Am I not using this correctly? I get console log error: React does not recognize the primaryTypographyProps prop on a DOM element...
<List>
  ...
  <ListItemText
    primary="Hello"
    primaryTypographyProps={{ variant: 'title' }}
  />
 ...
</List>

authors: NAisaac jedwards1211 mbrookes oliviertassinari

repo: mui-org/material-ui


text:
TextField cursor position defaults to beginning of value when input label is clicked

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

When clicking the label of an input that has a value, the input's cursor will appear at the beginning of the value. A second click/action is required to move the cursor to the end of the value to edit it.
Expected Behavior 🤔

When the label of a field is clicked, the input's cursor should default to the end of the value, if one exists.
Steps to Reproduce 🕹

Steps:

Go to the TextField demo page
Click on the label of a non-disabled, editable input that has a value.
Notice that the cursor defaults to the beginning of the value, instead of the end.

Context 🔦

We're using Material UI inputs for all of our forms, and are looking to make editing behavior as consistent as possible.
Your Environment 🌎

Tech
Version

Material-UI
v4.11.0

React
16.13.1

Browser
Chrome 86.0.4240.80

TypeScript
4.0.3

Thanks for the report :+1:

When the label of a field is clicked, the input's cursor should default to the end of the value, if one exists.

This is indeed the behavior for native inputs on pristine inputs. But once the select range changes, clicking the label restores the range.
Restoring is already working with Material-UI inputs. It's just that the range is different for pristine inputs. Though it might be caused by something different (e.g. controlled vs uncontrolled?).
Either way, we need to identify what is responsible for changing the selection range. The actual label-click behavior is working correctly.

Not sure on Chrome 86, after a hard refresh.

export default function FormPropsTextFields() {
  return (

      label
      <input type="text" id="bar" defaultValue="bar" />

  );
}

On Safari and Firefox it selects the whole input text.

Not sure, on Chrome 86 after a hard refresh:

The point is not to force a particular behavior but try to avoid changing the selection range on pristine text fields. We could never reproduce nor we should we override native behavior.

nor we should we override native behavior

Yes, agree, I believe the TextField behavior is identical to the native label + input one.

It looks like an issue with our documentation, not the component itself. The behaviors are identical on https://codesandbox.io/s/angry-tdd-fh4qq?file=/src/App.js.

It looks like an issue with our documentation, not the component itself. The behaviors are identical on codesandbox.io/s/angry-tdd-fh4qq?file=/src/App.js.

Interesting. The demo cloned in codesandbox works correct as well. I also tried https://material-ui.com/components/text-fields/#form-props in an incognito window and had the same issue (suspecting it was auto-fill related).

It has something to do with the server-side rendering.

Enjoy: https://codesandbox.io/s/determined-noyce-vc2tq?file=/pages/NoSsr.js, a bug for React.

I think that we can close, it looks like the native behavior: same on https://getbootstrap.com/docs/4.5/components/forms/#server-side.

It has something to do with the server-side rendering.

Yes! There's a difference between <input value="foo" /> in plain HTML and a client-side rendered <input defaultValue="foo" />: https://codesandbox.io/s/serverless-field-jokfq?file=/src/index.js
Related react issues: https://github.com/facebook/react/issues/18404, https://github.com/facebook/react/issues/14904, https://github.com/facebook/react/issues/12762
This is best raised against the React repo. The correct behavior would be to not modify the selection and keep the cursor at the start for mounted inputs. So the opposite of what you would expect.

@eps1lon @oliviertassinari Thanks for taking the time to check this out and for the info about SSR.

authors: eps1lon oliviertassinari zachbradshaw


text:
[material-ui] CSS rule "& > *" not working for some components after the migration from v4 to v5

Steps to reproduce
I have to migrate an old Mui code from v4 to v5. There are some old CSS rules for direct children (& > * ) that are not being applied. I'll provide some summarized codes below fore before/after the migration (v4  -> v5):
Before:
...
import { makeStyles } from '@material-ui/core/styles'
import DialogContent from '@material-ui/core/DialogContent'
import DialogTitle from '@material-ui/core/DialogTitle'
import Checkbox from '@material-ui/core/Checkbox'
import Grid from '@material-ui/core/Grid'
...

const useStyles = makeStyles((theme) => ({
    grid: {
        display: 'flex',
        justifyContent: "center",
        padding: "1em"
    },
    item: {
        marginTop: "0.2em",
    },
    buttons: {
        display: 'flex',
        justifyContent: "center",
        '& > *': {
            margin: theme.spacing(1)
        }
    }
}))

...
const FeedbacksForm = (props) => {
    ...
    const classes = useStyles()
    ...

    return (
        <Dialog
            open={openForm}
            maxWidth='md'
            fullWidth={true}>
            <DialogTitle className={classes.title}>Edit Feedback</DialogTitle>
            <DialogContent>
                <Grid container spacing={3} direction="row" justify="center" className={classes.grid}>
                    <Grid item xs={12} className={classes.buttons}>
                        <Button
                            variant="contained"
                            disabled={!buttonsEnabled}
                            onClick={handleClickCancel}
                            startIcon={<CancelIcon />}
                            >
                            Cancel
                        </Button>
                        <Button
                            variant="contained"
                            disabled={!buttonsEnabled}
                            onClick={handleClickSave}
                            startIcon={<SaveIcon />}
                            >
                            Save
                        </Button>
                    </Grid>
                </Grid>
            </DialogContent>
        </Dialog>
...

After (the the buttons' margin are not working):
...
import { makeStyles } from 'tss-react/mui'
...
const useStyles = makeStyles()(theme => {
    return {
        grid: {
            display: 'flex',
            justifyContent: "center",
            padding: "1em"
        },
        item: {
            marginTop: "0.2em"
        },
        buttons: {
            display: 'flex',
            justifyContent: "center",
            '& > *': {
                margin: theme.spacing(1)
            }
        }
    }
})

...
...
const FeedbacksForm = (props) => {
    ...
    const { classes } = useStyles()
    ...

The current workaround I've found is to provide the margin directly to the buttons through sx={{ margin: theme => theme.spacing(1) }}:
<Grid container spacing={3} direction="row" justify="center" className={classes.grid}>
    <Grid item xs={12} className={classes.buttons}>
         <Button
             sx={{ margin: theme => theme.spacing(1) }}
             variant="contained"
             ....

Is this migrated code right ?
Current behavior
Margins not applied in v5 when the parent rule CSS & > * is defined
Expected behavior
Margins should be applied
Context
Migration from v4 to v5
Your environment
 System:
    OS: Linux 6.6 Alpine Linux
  Binaries:
    Node: 20.11.1 - /usr/bin/node
    npm: 10.2.5 - /usr/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: Not Found
  npmPackages:
    @emotion/react: ~11.11.4 => 11.11.4
    @emotion/styled: ~11.11.5 => 11.11.5
    @mui/base:  5.0.0-beta.40
    @mui/core-downloads-tracker:  5.15.15
    @mui/icons-material: ~5.15.15 => 5.15.15
    @mui/lab: ~5.0.0-alpha.170 => 5.0.0-alpha.170
    @mui/material: ~5.15.15 => 5.15.15
    @mui/private-theming:  5.15.14
    @mui/styled-engine:  5.15.14
    @mui/styles: ~5.15.15 => 5.15.15
    @mui/system:  5.15.15
    @mui/types:  7.2.14
    @mui/utils: ~5.15.14 => 5.15.14
    @types/react:  18.3.0
    react: ~17.0.2 => 17.0.2
    react-dom: ~17.0.2 => 17.0.2
    typescript:  5.4.5

Search keywords: migration

Hey, thanks for opening the issue! Could you provide a minimal reproduction? It helps us troubleshoot. A live example would be perfect. This StackBlitz sandbox template may be a good starting point.

I've found out the cause...  this example I've shared is a simplified version of the real production code. What changes is that those buttons are actually custom buttons defined with withStyles. e.g:
import { withStyles } from 'tss-react/mui'

export const PrimaryButton = withStyles(Button, theme => ({
    root: {
        color: white,
        backgroundColor: purple,
        '&:hover': {
            backgroundColor: darken(purple, 0.10)
        }
    }
}))

The margin defined by the <Grid> container for its direct children (those custom buttons) works in v4, but doesn't work in v5. If I replace a custom button by a default <Button>, the margin works in v5. I am missing any new property or configuration that should also be added when calling withStyles  ?

@vinifmor It's interesting that it doesn't work. Could you create a minimal StackBlitz showing the issue with your custom Button and the & > * selectors before and after?

authors: ZeeshanTamboli danilo-leal vinifmor

repo: mui/material-ui


text:
[joy-ui][Modal] Is it expected for actions to be presented inverted?

Steps to reproduce
Link to live example: https://codesandbox.io/p/sandbox/lucid-tereshkova-hyfyys?file=%2Fsrc%2FDemo.tsx%3A44%2C52
Steps:

Click in the button to open the modal
Press Tab to navigate between the actions

Current behavior
The options are presented inverted relative to how they were defined in the code.
Expected behavior
I don't know if this is expected but pressing Tab should move the focus forward. For instance, with the focus in "Archive", the next focusable element is the "Discard notes" button. The Material Design modal behaves like that.
If it's a bug, I think it's just the case of aligning the buttons with justify-content: flex-end instead of flex-direction: row-reverse.
Context
No response
Your environment

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Search keywords: joy modal actions

Seems to be a bit of both. You can change the tab order by passing orientation="horizontal" prop value, but the alignment then starts from left.
So this is the final change to work around the current issue -
<DialogActions
  orientation="horizontal"
  sx={{ justifyContent: "flex-end" }}
>
...

@m4theushw I was thinking, maybe to address the issue with actions appearing in the wrong order in the modal, we could try adjusting the button alignment. It might help if we ensure the Tab key navigation moves the focus forward logically through the actions/buttons.

Hey @m4theushw, nice to see a familiar face :)

If it's a bug, I think it's just the case of aligning the buttons with justify-content: flex-end instead of flex-direction: row-reverse.

I would definitely consider this a bug, and what you propose makes sense. I am marking it as a "good first issue", so whoever wants can take it!

Hey @m4theushw, nice to see a familiar face :)

If it's a bug, I think it's just the case of aligning the buttons with justify-content: flex-end instead of flex-direction: row-reverse.

I would definitely consider this a bug, and what you propose makes sense. I am marking it as a "good first issue", so whoever wants can take it!

The behavior is intended because I think tab should focus on the primary action first.


text:
[material-ui][Menu] Let buttons opening menus have an activated state

Summary
If having a couple of buttons, each opening a menu. It is confusing to me which button the menu is connected to as they do not have any visual indication.
Examples
Material Design has an Activated state which could be used to cover this.
Here is a sandbox with how this could be visualized: https://codesandbox.io/p/sandbox/menu-buttons-activated-state-yfpm57
Images from the sandbox above:
Activated state styling

Compared to existing default styling

Motivation
I want to make the connection between the button and the menu easier to understand, this might be useful if there are multiple menus next to each other, especially if they use icons instead of text.
While it is easy to implement in an application using MUI, I think the concept is important enough to warrant including it in MUI itself.
Search keywords: button menu activated

Thanks for the report @fredrikcarlbom!
@zanivan @aarongarciah, what do you think? Should we provide this out of the box? or would it be better to just have a demo on achieving it?

@DiegoAndai @zanivan if it's trivial to implement, I'd advocate for implementing it in v6.

authors: DiegoAndai aarongarciah fredrikcarlbom


text:
[material-ui][Typography] Deprecate paragraph prop

[x] I have followed (at least) the PR section of the contributing guide.

Resolves #42382, resolves #16926

thanks so much for the instructions @aarongarciah. Happy to make those changes later today.

Hey @walston! Did you have a chance to take a look? We want to land this on v6, which should be out in the next few weeks.

oh dang. I'd love that. Apologies, got caught up with a company onsite. I can spend some time working through these things next week. Top of my priorities list now!

@walston in this case, I think a codemod doesn't make sense because there's no direct replacement for the paragraph behavior:

Renders as a <p> element.
Adds margin-bottom: 16px.

We could codemod number 1 with component="p", but we can't codemod number 2 because we can't possibly know what other styles are developers applying to the component instance and we might break their UIs. In this case, I think it makes sense to provide the instructions on how to migrate.
Even if it was possible, you could ask us to pick it up if you can't do it.

@aarongarciah I'm working with @walston to get this over the finish line :)

We could codemod number 1 with component="p", but we can't codemod number 2 because we can't possibly know what other styles are developers applying to the component instance and we might break their UIs. In this case, I think it makes sense to provide the instructions on how to migrate.

For 1: I don't think we event need to add the component prop, since <Typography> renders as a <p> by default. Unless a developer overrides this setting it would probably result in a lot of redundant code. Is there a way to check for this?
For 2: Would we want to suggest adding mb={2} for Typography elements that need margin? I'm still confused about MUI's preferences between mb and sx props for margins.

Hey @arronhunt! Thanks for working on this.
From your comment I'm not sure if you're working on a codemod or not. Just in case, I think we shouldn't spend time in a codemod. Instead, we can focus on writing clear guidance on what changed in the Migrating from deprecated APIs page given we can't possibly know users' intent and where the styles are coming from.

For 1: I don't think we event need to add the component prop, since  renders as a  by default. Unless a developer overrides this setting it would probably result in a lot of redundant code. Is there a way to check for this?

The tag being rendered by Typography depends on the variant and some other props. Typography renders a <p> in these scenarios:

variant="body1" (body1 is also used when no variant is passed)
variant="body2"
paragraph
component="p" or component={MyCustomComponent} (that renders a <p>)
variant="any_variant" paragraph
variant="any_variant" component="p"

It's fine to omit component="p" if no variant is passed or if the variant is already rendering a <p> (body1 and body2). See this demo for more info https://mui.com/material-ui/react-typography/#usage.

For 2: Would we want to suggest adding mb={2} for Typography elements that need margin? I'm still confused about MUI's preferences between mb and sx props for margins.

We'll remove system props (e.g. mb={2}) so it's recommended to use the sx prop. See this RFC and this in-progress PR if you want to know more.

Hey @arronhunt @walston! Let me know if you need any help.

@aarongarciah I just pushed updates to the docs, using sx props to set bottom margin for paragraphs. I agree that a codemod isn't necessary and we can rely on the upgrade instructions. Would love your feedback!

Thank you so much, @walston and @arronhunt. I'll be making some last finishing touches before merging.

@DiegoAndai I thought about the codemod, but I though it wouldn't be good because:

marginBottom could be applied to an element from anywhere without the codemod noticing:

A custom class name
A global class name
Inline styles
A parent element overriding child styles
etc.

Some people might don't want to use the sx prop.

Code wise it would look good but we could be breaking UIs by adding marginBottom ourselves. In that case, I think it's better to let users handle it. wdyt?

marginBottom could be applied to an element from anywhere without the codemod noticing, and we could intefere with users's styles:

Right, but if they were using the paragraph prop, they would expect this marginBottom to be applied to the element. So it should continue to work as they had it before the codemod.

Some people might don't want to use the sx prop.

That's fair. We could add the codemod and add the option to skip codemods in a follow-up PR if someone doesn't want to run it.

Right, but if they were using the paragraph prop, they would expect this marginBottom to be applied to the element. So it should continue to work as they had it before the codemod.

Can we ensure the same specificity?

@DiegoAndai tbh I'd love to know how many people rely on paragraph to know if it's worth spending time on the codemod 😅

So, I'm a designer and therefore not super familiar with codemods, but is there an existing pattern for providing them but make running them optional? I could see it being beneficial for those who have a lot of paragraph props and aren't using any specific margin styles. Otherwise, as a consumer of MUI, I like @DiegoAndai's idea of adding the comment to the migration instructions.

@\DiegoAndai tbh I'd love to know how many people rely on paragraph to know if it's worth spending time on the codemod 😅

@aarongarciah Anecdotally, our team has been relying on it for styling. It's actually what caused me to want to come here and fix the bad pattern lol.

@arronhunt we'll probably provide a codemod, but if you want to contribute it you're more than welcome. Right now, we're focused on making Material UI compatible with React 19.
You can find codemod examples in the mui-codemod package. For example, the one for the Divider component, which removes the light prop and adds sx={{ opacity: 0.6 }} (docs).

We could add the codemod and add the option to skip codemods in a follow-up PR if someone doesn't want to run it.

@DiegoAndai what did you have in mind for this? I'll be working on the codemod.

Remove paragraph prop if found, and:

Add sx={{ marginBottom: 2 }} if there's no sx prop
Add marginBottom: 2 to sx if there's sx prop

@DiegoAndai this would only be 16px if they haven't modified the default theme spacing (8px by default)

@DiegoAndai I just added a commit with the codemod. I went with 16px instead of 2 for the marginBottom value.
One doubt: should we cater for the mb shortcut being present in the object passed to sx?

I need to update the migration guide.

Ready for review.

@DiegoAndai I just updated the codemod to cater for mb, too. Ready for a final review.

Thanks @walston @arronhunt for working on this!

authors: DiegoAndai aarongarciah arronhunt walston


text:
[examples] Freeze examples dependency range

Make sure we can continue to easily run the examples on v5 once we release v6 as stable. This can help spot regressions.

To addon this, I think the README of the examples should be updated to point to v5.x too. For example:
diff --git a/examples/material-ui-cra-ts/README.md b/examples/material-ui-cra-ts/README.md
index dfd9da114d..dbb9c7cdbb 100644
--- a/examples/material-ui-cra-ts/README.md
+++ b/examples/material-ui-cra-ts/README.md
@@ -7,7 +7,7 @@ Download the example [or clone the repo](https://github.com/mui/material-ui):
 <!-- #default-branch-switch -->

 ```bash
-curl https://codeload.github.com/mui/material-ui/tar.gz/master | tar -xz --strip=2 material-ui-master/examples/material-ui-cra-ts
+curl https://codeload.github.com/mui/material-ui/tar.gz/v5.x | tar -xz --strip=2 material-ui-5.x/examples/material-ui-cra-ts
 cd material-ui-cra-ts

@@ -22,19 +22,19 @@ or:

-
+
-
+
The idea behind the example
This example demonstrates how you can use Material UI with Create React App in TypeScript.
It includes @mui/material and its peer dependencies, including Emotion, the default style engine in Material UI v6.
-If you prefer, you can use styled-components instead.
+If you prefer, you can use styled-components instead.
What's next?

You now have a working example project.
-You can head back to the documentation and continue by browsing the templates section.
+You can head back to the documentation and continue by browsing the templates section.

authors: oliviertassinari siriwatknp


text:
[docs] Mention Toolpad in Example projects section

'Example projects' made more sense over Discover more -> 'Related projects' as the placement for Toolpad.
Also linked example folder from Toolpad repo.
Preview: https://deploy-preview-44391--material-ui.netlify.app/material-ui/getting-started/example-projects/

On what's the right place for linking Toolpad, it feels like it's the exact same case as https://github.com/mui/material-ui/pull/44315#discussion_r1827036286.

So if we want to proceed, I think we need to rewrite this whole section:

Did these changes. Removing /examples should be ok as all links take the user to their respective example folders.


text:
Remove jsdocs rules

We're not relying on them right now and they're not working at the moment anyway.
They should use FunctionDeclaration in contexts instead of TSFunctionType. Not sure why these are configured for TSFunctionType, perhaps an older AST format that's not used anymore by @typescript-eslint/parser?

ok, understood what this is for. We're still not using it, but we may as well keep it. Working as intended

repo: mui/mui-toolpad


text:
大佬，在19.07官方源码中用官源的luci 18.06杂交，编译不成功。在固件中安装你编译好的ipk，X86固件下，无法改MAC

大佬，在19.07官方源码中用官源的luci 18.06杂交，编译不成功。在固件中安装你编译好的ipk，X86固件下，无法改MAC，请大佬指点

没有安装依赖rgmac
编译也需要先编译openwrt-rgmac，再编译luci

是要先编译好openwrt-rgmac吗，我有git clone openwrt-rgmac包下来，编译的时候也有选中，一起编译不行。

我再试试，先单独编译openwrt-rgmac

我再试试，先单独编译openwrt-rgmac

rgmac 本身是bash脚本, 各平台都没差别, 可以直接用 release 分支里的预编译包

authors: lllrrr lllrrr2 muink

repo: muink/luci-app-change-mac


text:
Listening Owl Carousel 2 Events

How to listen to Owl Carousel 2 Events?
I have tried something like this:
ngAfterViewInit() {
  const owl = $(this._elementRef.nativeElement).find('owl-carousel-child').data('owl.carousel');
  owl.on('onResize, onResized, onInitialize, onInitialized, onChange, onChanged, onDrag', console.log);
}

But nothing triggered

Instead of listening to Owl Carousel events you can pass the callback in options input.

@mujtaba01 Could you provide an example, please?
I tried to catch the "changed" event with no luck:
owlOptions = {
  changed: callbackFunction
}

Thank you.

Thank you! it works.


text:
Explain all the mapping operator options

Explain and compare all the mapping operator options.

DataWeave is no longer documented in this repo. Hence, we're "moving" this PR to docs-dataweave via https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE00000uo1MgYAI/view. We'll reference this closed PR when we work on the content.

authors: dukesphere ethanport

repo: mulesoft/docs-mule-runtime


text:
数据库好像请求不了

该项目并没有数据库

authors: heichiyihao mumuy


text:
Updated the ticket percent outline string for the Tuya extension to a…

… constant

Proposed change

Changed the ticket percent outline string in the Tuya extension to a constant in order to improve maintainability.
Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Deprecation (breaking change to happen in the future)
[ ] Breaking change (fix/feature causing existing functionality to break)
[x] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[x] The code change is tested and works locally.
[x] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the development checklist
[ ] I have followed the perfect PR recommendations
[x] The code has been formatted using Black (black --fast homeassistant tests)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
[ ] Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

[ ] I have reviewed two other open pull requests in this repository.

Kishor Peneff Group 10
2: The current way of defining the icon via a string is cumbersome in case the icon is to be changed in the future as all instances of the string have to be changed.
3: By changing the string to a constant, it only needs be updated in one place in order to change the icon for all instances in the file.

looks good

authors: KishFalk munterkalmsteiner

repo: munterkalmsteiner/core


text:
TreeView toggling when typing

Details
Atom v1.18.0
Platform: macOS Sierra
Brief description
When I toggle/enable the Split Diff when I have a project opened and type anything, it is toggling the TreeView almost immediately on keystroke. When this happens, the focus is then taken away from the editor, and instead placed on the TreeView.
I don't believe this behavior was happening prior to the 1.18.0 release

Did you mean to close this?

Yes, I just fixed this in master and will push out an update relatively soon.

Ah, my bad. Didn't see the commit message

repo: mupchrch/split-diff


text:
Paste image wrong ?

When paste image, every image looks like an attached image
optional settings
    "pasteImage.namePrefix": "${currentFileNameWithoutExt}_",
    "pasteImage.prefix": "/",
    "pasteImage.path": "${projectRoot}/img",
    "pasteImage.basePath": "${projectRoot}",

On the Finder of MacOS, copy a image file would only copy the icon of file, you have to open file and then copy image.

thanks

authors: MamoruMachida mushanshitiancai

repo: mushanshitiancai/vscode-paste-image


text:
After HA TTS, speakers begin playing queue even when previously "off" in MA

What version of Music Assistant has the issue?
2.0.0b88
The problem
This has been around in at least the last 3 beta versions (since I started testing MA again for v2.0.0b85), and still exists in b88.
If your queues have anything in them, but are NOT playing/connected to speakers (GHome/chromecast in my case), and you send a TTS to a speaker, MA will begin playing back the queue for that speaker or group.
It does this even with Auto Play/Power On disabled. Individual speakers or groups will exhibit the same behavior respectively. The only way to prevent the issue is to completely empty the queue for the device or group. Even then, MA still assumes connection to the speaker after TTS plays and just sits Idle.
Ideally, if MA isn't already playing, it should never connect to and start playback after a TTS, even with Auto Play enabled.
Of course, if music was already playing and a TTS comes in, it should play the TTS and then resume the music. This functionality DOES work, but perhaps a little too well. 🤣
How to reproduce

send a TTS, for example:

service: tts.cloud_say
data:
  entity_id: media_player.den_speaker
  message: The Front Door has been unlocked.
  cache: true

after the TTS, MA assumes control of/connects to the speaker and begins playing the queue, if there is one, or just sits idle otherwise

Relevant log output
No notable logs
Additional information

HAOS via OVA

MA Add-on container via HACS (UVloop=true)

Core 2024.1.5

Supervisor 2023.12.1

Operating System 11.4

Frontend 20240104.0

YT Music source

GHome speakers with Auto Play/Power On = false (toggling makes no difference)

Normal HA Cloud TTS service

What version of Home Assistant Core are your running
2024.1.5
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Linux

TTS is not yet implemented. This is therefore expected behaviour

But this shouldn't have anything to do with TTS?? MA is starting playback on its own when it shouldn't. I'll have to stop using MA entirely until resolved, if that is truly the case.

Are you targeting the MA entity with your TTS?

Are you targeting the MA entity with your TTS?

Nope! I know TTS isn't supported in the MA entity. This is TTS to the HA Cast entity.
Then, MA takes over with its entity and begins playing the queue, even if it was completely stopped and disconnected previously.

MA Integration? It is the latest available in HACS: 2024.1.0

How have you got your TTS configured. For example my configuration.yaml has
tts:
  - platform: google_translate
    service_name: google_say

I pay for HA Cloud and use HA's TTS, not Google.

No extra yaml needed.

OK I don't have the behaviour you are describing. I have tried cloud_say and google_say.
And this actualy should not work

Of course, if music was already playing and a TTS comes in, it should play the TTS and then resume the music. This functionality DOES work, but perhaps a little too well.

I would look carfefully again at what you have setup as what you are descriibing is opposite to what should happen and what is happening here. If you try and send a TTS to the MA entity you should get an error. If the MA entity is playing and you send a TTS to the equivalent HA entity the MA entity should pause and the TTS played and then nothing else. Look to see if you have an automations that might be interfering.

I know of every facet of my HA deployment and am far from a novice user (software engineer, as well). I can link an input_text directly to a cloud_say trigger and replicate it at will.
I have tested it both ways:

Nothing is playing in MA...

TTS using cloud_say is sent to a HA Cast speaker entity and it plays to completion
MA will then start playing the existing Queue of the device via the obvious MA speaker entity
If no queue exists/is empty, MA still latches onto the speaker entity and sits idle

Music is playing in MA...

Music stops
TTS using cloud_say is sent to the HA Cast speaker and it plays to completion
MA latches onto its entity again and resumes the queue

That said, it is symptomatic of the same exact bug:

MA is latching onto MA speaker entity after HA cast entity is finished playing TTS from cloud_say and resuming any existing queue on that device

It may be a bug with the Auto Play/Power On option in the Player settings, but it happens even when the option is turned off.
I'm trying to think of the simplest way for you to reliably replicate it...or what might be missing from my description in your attempts. All I'm doing to make it happen is having a queue existing for a player in MA and sending any cloud_say TTS to the HA entity. The rest just happens on MA's side on its own. Unfortunately, debug is not revealing what is actually triggering the playback, just that it has happened. I have no automations involving MA at all; I only just started using it again (v1 never worked for me) about a week ago. There are automations that send HA Cast TTS cloud_say, which is how I discovered the bug...music just started playing out of nowhere after a routine notification. Then I dug deeper by firing off manual cloud_say triggers and it happened on every speaker and group I targeted. TTS then music starts, unless queue is empty.

In your test system, did you playback your Queue at any point before trying to trigger the bug? If you loaded the Queue with music but never played anything before testing the TTS, you would not be replicating my live setup entirely. You must have played music from the queue at some point in the past, even if not presently, to trigger the bug. A totally fresh boot-up, even with filled Queue will not expose the bug until after you have played music from the container.

Here is full debug from the moment the TTS is sent:
2024-01-29 01:40:12.854 DEBUG (Thread-6) [music_assistant.providers.chromecast.Den Speaker] Received cast status - app_id: CC1AD845 - volume: 0.5
2024-01-29 01:40:12.856 DEBUG (MainThread) [music_assistant.event] player_updated bcee11ff-62c9-cf71-89e1-ab775183653f
2024-01-29 01:40:12.880 DEBUG (zeroconf-ServiceBrowser-_googlecast._tcp-22) [music_assistant.providers.chromecast] Discovered new or updated chromecast CastInfo(services={ServiceInfo(type='host', data=('[::ffff:a0a:d09]', 8009)), ServiceInfo(type='mdns', data='Google-Home-Max-bcee11ff62c9cf7189e1ab775183653f._googlecast._tcp.local.'), ServiceInfo(type='host', data=('10.10.13.9', 8009))}, uuid=UUID('bcee11ff-62c9-cf71-89e1-ab775183653f'), model_name='Google Home Max', friendly_name='Den Speaker', host='10.10.13.9', port=8009, cast_type=None, manufacturer=None)
2024-01-29 01:40:12.995 DEBUG (Thread-6) [music_assistant.providers.chromecast.Den Speaker] Received media status update: UNKNOWN
2024-01-29 01:40:13.062 DEBUG (Thread-6) [music_assistant.providers.chromecast.Den Speaker] Received media status update: IDLE
2024-01-29 01:40:13.286 DEBUG (Thread-6) [music_assistant.providers.chromecast.Den Speaker] Received media status update: PLAYING
2024-01-29 01:40:13.289 DEBUG (MainThread) [music_assistant.event] queue_updated bcee11ff-62c9-cf71-89e1-ab775183653f
2024-01-29 01:40:13.295 DEBUG (MainThread) [music_assistant.event] player_updated bcee11ff-62c9-cf71-89e1-ab775183653f
2024-01-29 01:40:13.305 DEBUG (Thread-6) [music_assistant.providers.chromecast.Den Speaker] Received media status update: PLAYING
2024-01-29 01:40:13.308 DEBUG (MainThread) [music_assistant.webserver] [140356494441616] Handling command music/item_by_uri
2024-01-29 01:40:13.879 DEBUG (zeroconf-ServiceBrowser-_googlecast._tcp-22) [music_assistant.providers.chromecast] Discovered new or updated chromecast CastInfo(services={ServiceInfo(type='host', data=('[::ffff:a0a:d09]', 8009)), ServiceInfo(type='mdns', data='Google-Home-Max-bcee11ff62c9cf7189e1ab775183653f._googlecast._tcp.local.'), ServiceInfo(type='host', data=('10.10.13.9', 8009))}, uuid=UUID('bcee11ff-62c9-cf71-89e1-ab775183653f'), model_name='Google Home Max', friendly_name='Den Speaker', host='10.10.13.9', port=8009, cast_type=None, manufacturer=None)
2024-01-29 01:40:14.288 DEBUG (Thread-6) [music_assistant.providers.chromecast.Den Speaker] Received media status update: PLAYING
2024-01-29 01:40:14.290 DEBUG (MainThread) [music_assistant.audio] Using cached streamdetails for ytmusic://track/WZddZRXmN8A
2024-01-29 01:40:14.297 DEBUG (MainThread) [music_assistant.providers.chromecast] Enqued next track (Alanis Morissette - Limbo No More) to player Den Speaker
2024-01-29 01:40:14.330 DEBUG (Thread-6) [music_assistant.providers.chromecast.Den Speaker] Received media status update: PLAYING
2024-01-29 01:40:15.030 DEBUG (Thread-6) [music_assistant.providers.chromecast.Den Speaker] Received cast status - app_id: CC1AD845 - volume: 0.5
2024-01-29 01:40:15.033 DEBUG (Thread-6) [music_assistant.providers.chromecast.Den Speaker] Received media status update: IDLE
2024-01-29 01:40:15.034 DEBUG (MainThread) [music_assistant.event] queue_updated bcee11ff-62c9-cf71-89e1-ab775183653f
2024-01-29 01:40:15.035 DEBUG (MainThread) [music_assistant.event] player_updated bcee11ff-62c9-cf71-89e1-ab775183653f
2024-01-29 01:40:15.041 DEBUG (MainThread) [music_assistant.webserver] [140356494441616] Handling command music/item_by_uri
2024-01-29 01:40:15.050 DEBUG (MainThread) [music_assistant.streams] Got GET request to /bcee11ff-62c9-cf71-89e1-ab775183653f/single/31d9d86533dc41fdb2840ea5c8df44cf.flac from 10.10.13.9
headers: <CIMultiDictProxy('Host': '10.10.3.0:8096', 'Connection': 'keep-alive', 'User-Agent': 'Mozilla/5.0 (X11; Linux aarch64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.225 Safari/537.36 CrKey/1.56.500000 DeviceType/SmartSpeaker', 'Range': 'bytes=0-', 'Accept-Encoding': 'identity;q=1, *;q=0', 'Accept': '*/*', 'CAST-DEVICE-CAPABILITIES': '{"audio_assistant":true,"bluetooth_supported":true,"display_supported":false,"hi_res_audio_supported":false,"remote_control_input_supported":false,"touch_input_supported":false}', 'Accept-Language': 'en-US,en;q=0.9')>

2024-01-29 01:40:15.051 DEBUG (MainThread) [music_assistant.audio] Using cached streamdetails for ytmusic://track/WZddZRXmN8A
2024-01-29 01:40:15.051 DEBUG (MainThread) [music_assistant.streams] Start serving audio stream for QueueItem ytmusic://track/WZddZRXmN8A to Den Speaker
2024-01-29 01:40:15.097 DEBUG (MainThread) [music_assistant.audio] start media stream for: ytmusic://track/WZddZRXmN8A
2024-01-29 01:40:16.034 DEBUG (zeroconf-ServiceBrowser-_googlecast._tcp-22) [music_assistant.providers.chromecast] Discovered new or updated chromecast CastInfo(services={ServiceInfo(type='host', data=('[::ffff:a0a:d09]', 8009)), ServiceInfo(type='mdns', data='Google-Home-Max-bcee11ff62c9cf7189e1ab775183653f._googlecast._tcp.local.'), ServiceInfo(type='host', data=('10.10.13.9', 8009))}, uuid=UUID('bcee11ff-62c9-cf71-89e1-ab775183653f'), model_name='Google Home Max', friendly_name='Den Speaker', host='10.10.13.9', port=8009, cast_type=None, manufacturer=None)
2024-01-29 01:40:16.035 DEBUG (MainThread) [music_assistant.event] queue_updated bcee11ff-62c9-cf71-89e1-ab775183653f
2024-01-29 01:40:16.044 DEBUG (MainThread) [music_assistant.webserver] [140356494441616] Handling command music/item_by_uri
2024-01-29 01:40:17.408 DEBUG (Thread-6) [music_assistant.providers.chromecast.Den Speaker] Received media status update: PLAYING
2024-01-29 01:40:17.410 DEBUG (MainThread) [music_assistant.event] queue_updated bcee11ff-62c9-cf71-89e1-ab775183653f
2024-01-29 01:40:17.411 DEBUG (MainThread) [music_assistant.event] player_updated bcee11ff-62c9-cf71-89e1-ab775183653f
2024-01-29 01:40:17.421 DEBUG (MainThread) [music_assistant.webserver] [140356494441616] Handling command music/item_by_uri
2024-01-29 01:40:17.907 DEBUG (Thread-6) [music_assistant.providers.chromecast.Den Speaker] Received media status update: BUFFERING
2024-01-29 01:40:18.415 DEBUG (Thread-6) [music_assistant.providers.chromecast.Den Speaker] Received media status update: PLAYING

This is by design - at least until we finish support for TTS/announcements, which should come in one of the next betas.
Until then I don't consider this a bug as we do not yet support announcements

It isn't a bug that MA starts playback all on its own when no direct interaction with its entities occurs? That really makes no sense to me. Action on HA's own entities shouldn't be acted upon by an idle MA unless the Auto Play/Power On option is selected. TTS isn't touching MA and MA shouldn't in any way act upon that.
Since I rely on TTS for a visually impaired member of the household, I'll have to suspend all testing and disable the Add-on until this is addressed. I can't have MA randomly deciding on its own to start blasting music through my house. 🤷🏻♂

I have seen the same behavior and it took me a while to figure out that MA is causing it. I too hope this will be considered a bug since MA is causing music to play when I am targeting indeed a non-MA mediaplayer with a non-MA service call.

authors: OzGav TheWebMachine freakshock88 marcelveldt

repo: music-assistant/hass-music-assistant


text:
Added process_orphaned_albums_and_artists

Remove albums and artists that are orphans
Would fix bugs https://github.com/music-assistant/hass-music-assistant/issues/2362 and https://github.com/music-assistant/hass-music-assistant/issues/2167

Ran the pre-commit script (took a while to figure out how to run it in the dev container..)
Fixed formatting and shortened the lines by splitting the query strings.

repo: music-assistant/server


text:
build: reduce version number to 2 levels

As discussed in #https://github.com/music-encoding/music-encoding/issues/1125#issuecomment-1564512842, the version number should be reduced to only 2 levels. Semantic versioning with three levels does not really fit for schema development.
I'd suggest to do the transformation during the release of v5, and not before, since reducing 5.0.0-dev to 5.0-dev could potentially break already existing data etc.
So during the release, we would merge 5.0.0-dev into 5.0, and then make 6.0-dev the new development version.

Closed with #1300

repo: music-encoding/music-encoding


text:
Fix links to docs

In the README all the links were pointing at the wrong location
so when you tried to view them on GitHub they resulted in a 404.
Fixes #1

@eropple - is this an acceptable PR?

I don't work at Mux anymore, sorry. cc @jaredsmith

@jaredsmith - is this a acceptable PR? Or is this repo abandoned?

No, this repo is not abandoned.  I've just been a bit busy this week, and it's taken me longer than expected to respond.
The short answer is that the PR isn't quite correct -- the README.md file gets auto-generated from the mustache template in gen/templates/README.mustache, so any changes made directly to the README.md file would get overwritten the next time we regenerated the code (and, by extension, the README.md file).  The proper way to fix this would to fix it in the gen/templates/README.mustache file.  I'll try to get to that before the end of the week.

Thanks @jaredsmith I am happy to do the work if you point me in the right direction. I assume the apiDocPath needs amending, but I am not sure that is present in the repository.

Closing as it doesn't seem like a priority.

authors: baynezy eropple jaredsmith

repo: muxinc/mux-csharp


text:
How to run this project

Hi mveril, I tried to run SampleConsole, but an error was reported. The prompt was that the xxx namespace could not be found in MobileDeviceSharp

Hello @ChaseYI
Sorry for the delay ! I had manny work. so I didn't see your message before.
On my side I don't observe any issue about it currently. The only Issue I was able to observe is when we don't copy the ilibmobiledevice  runtime native dependencies corresponding to your platform (from the runtimes directory) to the root of your app. It's also the reason why I have difficulties to provide nuget packages #7. Can you provide me more information about your issue like a stack trace, the full message or a screen capture.

authors: ChaseYI mveril

repo: mveril/MobileDeviceSharp


text:
Fix an example

Hi!
I've found that in ui.rs one import is missing - I've got compilation errors on my local machine when I've copy&pasted the example.
New import resolves the issue.

Oh, indeed. And it compiles for this project, since egui here is one of the dependencies..
Nice catch, thank you!


text:
Status Clientbound Response

The server should respond with a Response packet. Note that Notchian servers will for unknown reasons wait to receive the following Ping packet for 30 seconds before timing out and sending Response.

implemented in 1387ab6 and b7a487d

authors: cyrilGrandjean mwath

repo: mwath/mcli


text:
function name incorrect?

aws lambda update-function-code --function-name gdal_translate --zip-file fileb://lambda-gdal_translate.zip
should be
aws lambda update-function-code --function-name lambda-gdal_translate --region us-east-1 --zip-file fileb://lambda-gdal_translate.zip

done


text:
Add dismiss drag progress property

I think it would be nice, if there was an API that exposes current drag offset state. So I've implemented this.
One of the use cases for that is to animate translucency of a Composable using alpha. I've added an example of this to the sample.
https://user-images.githubusercontent.com/44653764/146892278-5b566704-7351-483f-a433-5d73ae2161b3.mp4

Property name changed to dismissDragProgress.
I don't think we need to show this in the sample so reverted that part.

Btw if you want to set the alpha of an Image, setting the alpha parameter is more efficient than using an alpha modifier.


text:
Fix promise name in Cache 'n' Fetch example code

I think this is change is correct but let me know if I'm instead misunderstanding how this should work. 😅

Good catch & thanks!

authors: interstateone mxcl

repo: mxcl/PromiseKit


text:
Module not found: Error: Can't resolve 'fs'

Module not found: Error: Can't resolve 'fs' in '/Users/js/code/react/react-boilerplate/node_modules/shelljs/src'
Issue Type

[x] Bug (https://github.com/mxstbr/react-boilerplate/blob/master/.github/CONTRIBUTING.md#bug-reports)
[ ] Feature (https://github.com/mxstbr/react-boilerplate/blob/master/.github/CONTRIBUTING.md#feature-requests)

Description
I've used this boilerplate successfully in the past.  First I tried it with yarn installed.  Then, I uninstalled yarn and tried again.  Same error both times.
Building the Webpack DLL...
Hash: f64cd94e521a0c2f99ea
Version: webpack 2.1.0-beta.25
Time: 4360ms
                      Asset     Size  Chunks             Chunk Names
reactBoilerplateDeps.dll.js  3.32 MB       0  [emitted]  reactBoilerplateDeps
chunk    {0} reactBoilerplateDeps.dll.js (reactBoilerplateDeps) 2.79 MB [entry] [rendered]
    [2] dll reactBoilerplateDeps 12 bytes {0} [built]
     + 736 hidden modules

ERROR in ./~/shelljs/src/common.js
Module not found: Error: Can't resolve 'fs' in '/Users/js/code/react/react-boilerplate/node_modules/shelljs/src'
 @ ./~/shelljs/src/common.js 6:9-22
 @ ./~/shelljs/shell.js
 @ dll reactBoilerplateDeps

ERROR in ./~/shelljs/src/cd.js
Module not found: Error: Can't resolve 'fs' in '/Users/js/code/react/react-boilerplate/node_modules/shelljs/src'
 @ ./~/shelljs/src/cd.js 1:9-22
 @ ./~/shelljs/shell.js
 @ dll reactBoilerplateDeps

ERROR in ./~/shelljs/src/ls.js
Module not found: Error: Can't resolve 'fs' in '/Users/js/code/react/react-boilerplate/node_modules/shelljs/src'
 @ ./~/shelljs/src/ls.js 2:9-22
 @ ./~/shelljs/shell.js
 @ dll reactBoilerplateDeps
(truncated)

Steps to reproduce
git clone --depth=1 https://github.com/mxstbr/react-boilerplate.git
npm run setup

Versions

Node/NPM:

$ yarn --version
0.17.9
$ npm --version
3.10.9
$ node --version
v7.2.0

Browser: NA

I got same issues:
$ npm --version
3.10.8
$ node --version
v7.0.0

How about if you run yarn directly e.g.
rm -rf node_modules yarn`
Or did you do that already?

When I run npm run setup I has the same issue. Although both yarn install and npm i finish successfully.
yarn v0.17.10
node v7.0.0
npm 3.10.8

How about after installing with yarn? Can you successfully run:
npm start?
What about
npm run start:production?
The only thing npm run setup gets you over just yarn is a clean git repo, which you can do for yourself. (delete .git and git init)

Yes, I'm able to run npm start
The problem seems to lead into webpack.dll build run by:
exec('cross-env BUILDING_DLL=true webpack --display-chunks --color --config internals/webpack/webpack.dll.babel.js');

Same issue too while running npm run build:dll. I've also tried deleting node_modules, didn't change it.
Node v7.1.0
Yarn v0.17.10
npm v3.10.9

Hi, I am using react-boilerplate v3.3.3 with Node v6.9.2 with npm v3.10.9.
I added a new dependency (Raven v1.1.1) and when I run npm run build:dll facing the same Error.
Here is the stack error:
`
Building the Webpack DLL...
Hash: da2f8f7db2b0a2adbac2
Version: webpack 2.1.0-beta.25
Time: 7106ms
Asset     Size  Chunks             Chunk Names
reactBoilerplateDeps.dll.js  4.04 MB       0  [emitted]  reactBoilerplateDeps
chunk    {0} reactBoilerplateDeps.dll.js (reactBoilerplateDeps) 3.48 MB [entry] [rendered]
[6] dll reactBoilerplateDeps 12 bytes {0} [built]
+ 875 hidden modules
ERROR in ./~/raven/lib/utils.js
Module not found: Error: Can't resolve 'fs' in '/Users//Documents/workspace//web_app/node_modules/raven/lib'
@ ./~/raven/lib/utils.js 3:9-22
@ ./~/raven/index.js
@ dll reactBoilerplateDeps
ERROR in ./~/raven/lib/breadcrumbs.js
Module not found: Error: Can't resolve 'pg' in '/Users//Documents/workspace//web_app/node_modules/raven/lib'
@ ./~/raven/lib/breadcrumbs.js 132:13-26
@ ./~/raven/lib/client.js
@ ./~/raven/index.js
@ dll reactBoilerplateDeps
ERROR in ./~/lsmod/index.js
Module not found: Error: Can't resolve 'fs' in '/Users//Documents/workspace//web_app/node_modules/lsmod'
@ ./~/lsmod/index.js 2:9-22
@ ./~/raven/lib/utils.js
@ ./~/raven/index.js
@ dll reactBoilerplateDeps
`

I found the error for myself at least, the docs didn't state all that well. You just need to add the conflicting package to dllPlugin.exclude: [] in your package.json file.

I re-cloned the repo and no longer get this error.  Not sure if it's due to a recent commit or something on my local machine.

Closing because I can no longer replicate.  git clone + yarn works for me now.

One of the things that can cause this bug is adding packages to the wrong dependency section. For instance yarn add gulp will add it to dependencies instead of devDependencies.

I'm having this problem as well

I just had the same problem from a fresh clone of the repo.
I had to add this to the "webpack.base.babel.js" config:
node: {
    fs: 'empty',
    child_process: 'empty',
  },

I found the workaround here: https://github.com/webpack-contrib/css-loader/issues/447

I ended up trying @sebelga 's solution, but it still didn't work – I found another suggestion on a different GH issue and this is what ended up working for me.
In your webpack.config.*.js file, add the following to plugins after new webpack.DllPlugin({}):
new webpack.IgnorePlugin(/your_package_name_here/). For me, it was yarn that was blowing stuff up.
Hope this helps!

Thanks @coleclayman!  I had no luck with what seemed like an endless stream of other suggested fixes but your approach worked for me (in my case it was a host of packages but |ing them all in the RE in IgnorePlugin was the fix

authors: FoxxMD coleclayman ggprod giautm gihrig joelfsreis joshmeads jshumakerpruitt juanibiapina sebelga sublimeye

repo: mxstbr/react-boilerplate


text:
[Bugfix] Fix postal validation

I missed limiting the length on the postal field. We had one entry with a full postal - I've updated that in the prod DB.

I'm going to merge this since we're currently allowing lower case postals.

repo: my-covid-story/www


text:
🛑 Website Load Balancers is down

In c398dc7, Website Load Balancers ($WEB_SERVER) was down:

HTTP code: 522
Response time: 15525 ms

Resolved: Website Load Balancers is back up in 441d0cf.

repo: myavsuper/upptime


text:
🛑 Video CDN is down

In 5004383, Video CDN ($VOD_SERVER) was down:

HTTP code: 200
Response time: 332 ms

Resolved: Video CDN is back up in d9fc94d.


text:
插入带有逻辑删除标识的实体时报错

实体
@Table(value="brand")
@Getter
@Setter
@ToString
public class Brand{
    @Id(keyType = KeyType.Auto)
    private Integer id;
    private String code;
    private String name;

    @Column(isLogicDelete = true/*, jdbcType = JdbcType.INTEGER*/)
    private Boolean del;
}

db
CREATE TABLE demo.brand (
	id serial4 NOT NULL,
	code bpchar(2) NULL,
	"name" varchar(50) NULL,
	del int4 NULL,
	CONSTRAINT brand_pk PRIMARY KEY (id)
);

问题描述
查询时正常，插入时报如下错误
Error updating database.  Cause: org.postgresql.util.PSQLException: 错误: 字段 "del" 的类型为 integer, 但表达式的类型为 boolean
Hint: 你需要重写或转换表达式
Position: 88

数据库为postgres
实体中无论是否配置 jdbcType 都是一样的结果
插入前无论设置 brand.setDel(Boolean.FALSE) 还是保持为 null 都是一样的结果

请指点一二，是我哪里用错了？
多谢

修改你的 del 字段类型为 int 类型，或者 修改你的数据库类型为 tinyint 1 类型。

authors: jianghongzhe yangfuhai

repo: mybatis-flex/mybatis-flex


text:
Chrome Tab is closing when clicking on cancel through printing window

when i launch the printing function everything works fine but when i click on cancel the chrome tab that contains the vue app closes

yup it closes too when you hit print/save

@melWiss any solution on this? Thanks in advance.

to not block you, i remember that i fixed it like this:
function openWindow(url, name, props) {
    let windowRef = null;
    windowRef = window.open(url, name, props);
    if (!windowRef.opener) {
        windowRef.opener = self;
    }
    windowRef.focus();
    return windowRef;
}

function printElement(el) {
    let defaultName = '_blank',
        defaultSpecs = ['fullscreen=yes', 'titlebar=yes', 'scrollbars=yes'];
    let name = defaultName, specs = defaultSpecs;

    specs = !specs.length ? specs.join(',') : '';

    const element = window.document.getElementById(el);

    const url = '';
    const win = openWindow(url, name, specs);

    win.document.write(`
        <html>
          <head>
            <title>${window.document.title}</title>
          </head>
          <body>
            ${element.innerHTML}
          </body>
        </html>
      `);

    setTimeout(() => {
        win.focus();
        win.print();
        win.close();
    }, 1000);

    return true;
}

export default printElement;

authors: melWiss schrockinteractive

repo: mycure-inc/vue-html-to-paper


text:
🛑 Grambling Enterprise is down

In c80ec5a, Grambling Enterprise (https://grambling.ent.sirsi.net/client/en_US/grambling/search/results?te=) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Grambling Enterprise is back up in e3c6e08.

repo: myqua/LOUIS-upptime


text:
Pooled connections run into error

We create connections using a pool. If the connection obtained from the pool is in error, how do we fix that connection? In the below code, the connect function takes a command callback which expects a good connection to be passed to it. This connection comes from a pool. How should I structure my code to handle the error. The documentation at  shows only how to log the error and not how to recover. I do not want to report an error. My application should remain always-running and hence should recreate connections that fail.
exports.createPool = function createPool(dbConfig)
{
        logger.debug('Creating pool');
        pool = mysql.createPool(dbConfig);
};

exports.connect = function connect(command)
{
        pool.getConnection(     function(err, conn){
                if(!err)
                {
                        conn.on('error', function(err) {
                                logger.error(err); // 'ER_BAD_DB_ERROR'
                        });
                        command(conn);
                }
        });
};

I get logs saying:
[Sat Jun 02 2018 02:59:52 GMT+0550] [ERROR] app.js - {
        "fatal": true,
        "code": "PROTOCOL_CONNECTION_LOST"
}

If you have a pool connection and you get any error with fatal = true like in your example, the only thing you can do is call .release() on that connection and get a new one using .getConnection

Yes. But I come to know of the fatal only in the 'error' event. Even if I release the connection, how do I give a new connection to the calling program?

You should also see the error in the callback to anything you do on the connection like .query()

Right, once there is a fatal error, the connection is useless (your particular error is that the TCP connection is closed). You jave to call .getConnection() to get a new, good connection and then call the .query() on that new connection.
The tickCallback is something from Node.js core. I don't know the details on it, but you could always also on their issue tracker to understand it better.

authors: dougwilson yashgt

repo: mysqljs/mysql


text:
Proper use of dialogService.ShowOpenFileDialogAsync

I'm using Avalonia 11.05 with .net7 the result.OpenReadAsync() is working with desktop and Android but not with the Web platform.
how can I check if the file is loaded successfully?
And in the case of larga file, how I can read the file uploading status.
private async Task OpenFileAsync()
{

    var settings = GetSettings(false);
    var result = await _dialogService.ShowOpenFileDialogAsync(this, settings);

    if (result?.Path != null)
    {
        using var stream =  result.OpenReadAsync();

        ReadExcel(stream.Result);
    }

}

I've just fixed the Web demo so it at least runs... it's going to require a little bit of work

Browser app really isn't behaving well.
Posted some issues there
https://github.com/AvaloniaUI/Avalonia/issues/14065

I managed to make it work with the browser and I added the upload status
this is my code `maybe you  need to remove some extra code that I add for my specific needs'
var ms = new MemoryStream();
var settings = GetSettings();
var result = await _dialogService.ShowOpenFileDialogAsync(this, settings);
IProgress<long> progress = new SynchronousProgress<long>(value =>
{
    ProgressBarCurrentValue = value;
    StatusText = value.ToString();
});

if (result?.Path != null)
{

    StatusText = result.Name;
    using var stream = result.OpenReadAsync();
    StatusText += " Open Read Done";
    //await stream.Result.CopyToAsync(ms);
    await stream.ContinueWith(async t =>
    {

        StatusText += " getting the result";
        var streamResult = t.Result;
        StatusText += " Result size: " + streamResult.Length + " starting copy to memory";
        await streamResult.CopyToAsync(ms, progress, source.Token, 1024);
        StatusText += "Done";
        ms.Position = 0;
        StatusText += " size:" + ms.Length;
        await ReadExcel(ms).ConfigureAwait(false);

    });

}

Oh perfect!
I'll add this to the samples.

btw where do you get your source.Token?

btw where do you get your source.Token?

static readonly CancellationTokenSource source = new ();

you just created your own to have a cancel button?

You just created your own to have a cancel button?

yes, but I have not implemented it yet.


text:
Add multitouch support

Hi, these changes should enable multi-touch support, so that elements can be individually dragged at the same time, when using a multi-touch device.
I've tested this successfully on Chrome for Android. On Firefox for Android, scroll and zoom aren't being prevented (a separate issue?) I unfortunately do not have an iOS device to test with.
This adds a few conditional statements in the event handlers, but it didn't seem to impact performance when testing on my laptop. The original tests all pass, and everything in the demo is functioning as I would expect it to (The "Active Drags" counter is fun to watch, now)
I would like to add unit tests for this, but I'm not sure how to simulate this situation - everything depends on how the state of each component changes.
There might be a more performance-savvy way to do this by having one set of touch event listeners per app, but that would take a significant refactoring and might not be in line with the philosophy of React.
Please let me know what you think!

Hey, this is pretty nice. Thanks for the contribution.
I agree that this is the right way to do it. Any other approach essentially relies on globals.

Thanks! If we were using ES6 classes instead of React.createClass, it might make sense to have the event listeners be static class variables, enforcing one instance of each for the whole class. The single listener could be added with the first drag from any component, and removed with a drop as long as no other component is dragging... but determining that would also probably require global state.
I guess in the worst case, one ten-fingered person will be dragging ten items at once. There will be ten listeners that each fire the handleDrag ten times. That's definitely not ideal, but... at least most people don't have more than ten fingers!

authors: STRML YottaSecond

repo: mzabriskie/react-draggable


text:
0.10.0 Error Cannot read property 'split' of undefined

Expected Behavior

Please describe what should happen

Actual Behavior

Describe what actually happens

/home/matt/Projects/freljord/node_modules/hard-source-webpack-plugin/lib/TransformNormalModulePlugin.js:236
        JSON.stringify([resolveKey.context, resolved.resource.split('?')[0]])
                                                              ^
TypeError: Cannot read property 'split' of undefined
    at NormalModule.needRebuild4 [as needRebuild] (/home/matt/Projects/freljord/node_modules/hard-source-webpack-plugin/lib/TransformNormalModulePlugin.js:236:63)
    at Compilation.addModule (/home/matt/Projects/freljord/node_modules/webpack/lib/Compilation.js:308:27)
    at factory.create (/home/matt/Projects/freljord/node_modules/webpack/lib/Compilation.js:567:37)
    at factory (/home/matt/Projects/freljord/node_modules/webpack/lib/NormalModuleFactory.js:405:6)
    at hooks.afterResolve.callAsync (/home/matt/Projects/freljord/node_modules/webpack/lib/NormalModuleFactory.js:155:13)
    at AsyncSeriesWaterfallHook.eval [as callAsync] (eval at create (/home/matt/Projects/freljord/node_modules/tapable/lib/HookCodeFactory.js:24:12), <anonymous>:6:1)
    at resolver (/home/matt/Projects/freljord/node_modules/webpack/lib/NormalModuleFactory.js:138:29)
    at /home/matt/Projects/freljord/node_modules/hard-source-webpack-plugin/lib/TransformNormalModuleFactoryPlugin.js:133:17
    at process.nextTick (/home/matt/Projects/freljord/node_modules/webpack/lib/NormalModuleFactory.js:342:9)
    at process._tickCallback (internal/process/next_tick.js:112:11)
error Command failed with exit code 1.

Is an error being thrown?

Include a stack trace if an error is occuring

Steps to Reproduce

Steps to create a minimal reproduction or a link to a repository containing the same
Any other information you find helpful reproducing an issue

Operating System, Node, and NPM dependency versions
Ubuntu 18.04
Node 9.8.0

"devDependencies": {
    "add-asset-html-webpack-plugin": "^2.1.3",
    "awesome-typescript-loader": "^5.2.0",
    "clean-webpack-plugin": "^0.1.19",
    "css-loader": "^0.28.11",
    "extract-text-webpack-plugin": "^4.0.0-beta.0",
    "file-loader": "^1.1.11",
    "fork-ts-checker-webpack-plugin": "^0.4.2",
    "hard-source-webpack-plugin": "^0.10.0",
    "html-webpack-plugin": "^3.2.0",
    "husky": "1.0.0-rc.9",
    "lint-staged": "^7.2.0",
    "node-sass": "^4.8.3",
    "postcss-loader": "^2.1.5",
    "sass-loader": "^7.0.3",
    "style-loader": "^0.21.0",
    "tsconfig-paths-webpack-plugin": "^3.1.4",
    "tslint": "^5.10.0",
    "typescript": "^2.9.2",
    "uglifyjs-webpack-plugin": "^1.2.7",
    "webpack": "^4.14.0",
    "webpack-cli": "3.0.8",
    "webpack-dev-middleware": "^3.1.2"
  },
  "dependencies": {
    "@types/immutable": "^3.8.7",
    "@types/lodash": "^4.14.110",
    "@types/node": "^10.5.1",
    "@types/prismjs": "^1.9.0",
    "@types/qs": "^6.5.1",
    "@types/react": "^16.4.6",
    "@types/react-copy-to-clipboard": "^4.2.5",
    "@types/react-dom": "^16.0.6",
    "@types/react-redux": "^6.0.3",
    "@types/react-router": "^4.0.27",
    "@types/react-router-dom": "^4.2.7",
    "@types/redux-logger": "^3.0.6",
    "@types/redux-thunk": "^2.1.0",
    "antd": "^3.6.5",
    "autoprefixer": "^8.6.4",
    "axios": "^0.18.0",
    "body-parser": "^1.18.3",
    "express": "^4.16.3",
    "http-proxy-middleware": "^0.18.0",
    "immutable": "^3.8.2",
    "lodash": "^4.17.10",
    "prismjs": "^1.15.0",
    "qs": "^6.5.2",
    "react": "^16.4.1",
    "react-copy-to-clipboard": "^5.0.1",
    "react-dom": "^16.4.1",
    "react-markdown": "^3.3.4",
    "react-redux": "^5.0.7",
    "react-router": "^4.3.1",
    "react-router-dom": "^4.3.1",
    "redux": "^4.0.0",
    "redux-logger": "^3.0.6",
    "redux-thunk": "^2.3.0"
  }

There is no such issue in v0.9.0

I have the same problem with v.0.10.0

Same problem too :)

I have a fix inbound for this.

Fix is merged in. Closing.
Thank you everyone for opening and commenting on this issue.

authors: aldarund blackbird91 mzgoddard yuqingc

repo: mzgoddard/hard-source-webpack-plugin

license: isc


text:
🛑 mziyut.com is down

In a4e6c64, mziyut.com (https://mziyut.com) was down:

HTTP code: 500
Response time: 88 ms

Resolved: mziyut.com is back up in 5486245 after 9 minutes.

repo: mziyut/upptime


text:
Add examples for get with range requests

We got some simple examples, but we still need some examples how to request ranges for individual blobs, or ranges of children of collections.
Especially focusing on the whole topic of blocks and bytes.
While doing this we might also want to reexport some more stuff from bao-tree.

I think the API still needs to get better, but the iroh-gateway example does range requests.


text:
netcheck::tests::test_udp_blocked failure

seen here https://github.com/n0-computer/iroh/actions/runs/7253050090/job/19758824459

and again here https://github.com/n0-computer/iroh/actions/runs/7253555147/job/19760392300

Sadly these logs are useless: let's try and improve them again: https://github.com/n0-computer/iroh/pull/1902

Logs with more logging:
https://github.com/n0-computer/iroh/actions/runs/7273863276/job/19818670553
https://github.com/n0-computer/iroh/actions/runs/7273863276/job/19818672125

fixed on f2e1c44

authors: divagant-martian flub