Highlighting in REPL (performance)

Hi,
I've been using emacs-tree-sitter for Python highlighting for a couple of months now, and am very happy with it - thanks!
I develop a lot with org-babel and emacs-jupyter, keeping an org-file and REPL open side-by-side, sending code back and forth.
I use the following to get tree-sitter highlighting in the REPL:
(add-to-list 'tree-sitter-major-mode-language-alist '(jupyter-repl-mode . python))
(add-to-list 'tree-sitter-major-mode-language-alist '(inferior-python-mode . python))
(add-hook 'tree-sitter-after-on-hook #'tree-sitter-hl-mode)

I notice that as the REPL buffer grows in length, everything slows down proportionally, the reason for which is tree-sitter. Obviously only a fraction of the output in the REPL is actually code that can be parsed and should be semantically highlighted (although I don't mind the highlighting that is produced even for output).
Occasionally clearing the buffer helps, but would there be an option to make this more performant?

keeping an org-file and REPL open side-by-side

It is known that org-mode highlights works by opening a hidden buffer, pasting the code there, and getting back the text with the highlights (this comes from the Q&A at EmacsConf about tree-sitter) so it is bound to get slower the more you add to it.
I think the workaround for this is to turn off emacs-tree-sitter on your org-mode file. The solution to the performance problem is having org-mode integrate emacs-tree-sitter for their syntax highlight.

Actually the issue is less with org-mode, and more with the REPL.
The org files are fast enough, there is not that much code in them. You could reproduce this without using org-mode at all.
The REPL session has lots of output, and executes a lot more code than is finally written to the org file. Since I hooked tree-sitter to the REPL-mode, I think tree-sitter tries to parse the entire buffer as Python, which must slow it down. It would help already if I could somehow distinguish code from output and parse only that, perhaps occasionally clearing the buffer.

This is an interesting use of tree-sitter-hl!
In theory, it should only re-parse the parts that have changed. Maybe jupyter-repl-mode or inferior-python-mode are doing something special with text changes.
Does it happen when you navigate around the buffer, when you type something, or when you send the code to the buffer?
What are the minor modes enabled in the REPL buffer?
Is it easily reproducible with some Python fragments?
If not, there are several things you can try to troubleshoot it yourself:

M-x profiler-start, use it for a while, M-x profiler-stop.
Trace the parsing and highlighting functions:(progn
  ;; To see whether it parses from scratch too often (last arg is nil).
  (trace-function #'tsc-parse-chunks)
  ;; To see whether it parses incrementally, but with regions that are
  ;; too large (the difference between 3rd and 4th args).
  (trace-function #'tsc-edit-tree)
  ;; To see whether it highlights regions that are too large.
  (trace-function #'tree-sitter-hl--highlight-region))

Add logging advices to parsing and highlighting functions, if the above is too noisy:(define-advice tsc-parse-chunks (:before (_parser _input_fn old-tree) log-full-parse)
  (unless old-tree
    (message "[%s] tsc-parse-chunks full" (buffer-name))))

(define-advice tsc-edit-tree (:before (_tree beg-byte _old-end-byte new-end-byte &rest _) log-edit-size)
  (message "[%s] tsc-edit-tree %s" (buffer-name) (- new-end-byte beg-byte)))

(define-advice tree-sitter-hl--highlight-region (:before (beg end &rest _) log-hl-size)
  (message "[%s] tree-sitter-hl--highlight-region %s" (buffer-name) (- end beg)))

Thanks for the detailed response! I do like the fact that in theory, I can get great syntax highlighting inside the Jupyter REPL with just a hook - and actually bypass a font-lock bug with emacs-jupyter in the process (https://github.com/nnicandro/emacs-jupyter/issues/219) [this issue has a fix that disables traditional font-lock in the REPL buffer, but ts brings it back better].
I have the following modes enabled:
Auto-Compression Auto-Encryption Beacon Column-Number Company Counsel Eldoc
Electric-Indent File-Name-Shadow Font-Lock Global-Eldoc Global-Flycheck
Global-Font-Lock Global-Git-Commit Global-Hl-Line Global-Tree-Sitter
Global-Visual-Line Ivy Ivy-Rich Jupyter-Repl-Interaction
Jupyter-Repl-Persistent Line-Number Magit-Auto-Revert Mouse-Wheel
Override-Global Pdf-Occur-Global Projectile Savehist Shell-Dirtrack Show-Paren
Smartparens Smartparens-Global Transient-Mark Tree-Sitter Tree-Sitter-Hl
Visual-Line Which-Key Winner

That's a lot, but I can isolate the slowdown to tree-sitter.
I just did some more checks, and find that so far I can actually only reproduce this with Jupyter-REPL when dealing with large pandas DataFrames.
To reproduce, I load a simply load a big DataFrame and return it, ie.:
First, separately:
import pandas as pd
df = pd.read_csv("many_rows.csv")

Now:
df

Every time I execute df again, displaying the output takes longer.
After doing this a couple of times, even simple things like python 1+1 will display with delay. Turning tree-sitter-mode off makes it fast again.
I think the lag mainly accumulates when my functions/executions return DataFrame output. (Note that tree-sitter does not actually highlight the output in the Jupyter REPL,  just the code)
The behaviour is different in the normal inferior Python shell: executing the code is instantaneous, tree-sitter highlights the output as if it was Python code, and repeating this many times slows down that buffer in general. (vs. just the apparent execution inside Jupyter-REPL). Again though, turning tree-sitter off makes the buffer speedy again.
I don't have time to trace this myself right now, but hope to get to that still this week.

Hi, sorry it took me a long time to get to this! I've done some profiling now with the code from above (making a large pandas dataframe and repeatedly printing it).
I believe the main problem is that tree-sitter-do-parse is called many times. Here a chunk of the profiler report:
- jupyter-repl-insert-prompt                 232  15%
    - tree-sitter--after-change                 156  10%
        - tree-sitter--do-parse                    156  10%

Note that there are many (intermediate?) actions done by the jupyter REPL that cause tree-sitter to parse:

Almost every jupyter-repl call there leads to a parse (I didn't unfold everything, but you get the gist).
The trace of parse-chunks (trace-function #'tsc-parse-chunks) resulted in 16 individual outputs (I'm not familiar with tracing so I may not properly describe this). 8 when I send press RET to execute the line which will result in printing the dataframe, and another 8 when the dataframe has been printed:
1 -> (tsc-parse-chunks #<user-ptr ptr=0x5606bb9feee0 finalizer=0x7fa35c71a600> tsc--buffer-input #<user-ptr ptr=0x5606c53039e0 finalizer=0x7fa35c71a910>)
1 <- tsc-parse-chunks: #<user-ptr ptr=0x5606b7726ef0 finalizer=0x7fa35c71a910>

Tracing the edit tree does the same (16 outputs), with output like this:
1 -> (tsc-edit-tree #<user-ptr ptr=0x5606b8b927d0 finalizer=0x7fa35c71a910> 42295 42295 42296 #1=(794 . 58) #1# (795 . 0))
1 <- tsc-edit-tree: nil

The highlight-region trace has output such as this, again many entries:
1 -> (tree-sitter-hl--highlight-region 54381 54439 nil)
1 <- tree-sitter-hl--highlight-region: (jit-lock-bounds 54282 . 54609)

Other than the profile report, which leads me to believe that too many REPL actions trigger re-parsing, I don't know how to interpret the output.

Hi, sorry it took me a long time to get to this! I've done some profiling now with the code from above (making a large pandas dataframe and repeatedly printing it).
I believe the main problem is that tree-sitter-do-parse is called many times. Here a chunk of the profiler report:
- jupyter-repl-insert-prompt                 232  15%
    - tree-sitter--after-change                 156  10%
        - tree-sitter--do-parse                    156  10%

Note that there are many (intermediate?) actions done by the jupyter REPL that cause tree-sitter to parse:

Almost every jupyter-repl call there leads to a parse (I didn't unfold everything, but you get the gist).
The trace of parse-chunks (trace-function #'tsc-parse-chunks) resulted in 16 individual outputs (I'm not familiar with tracing so I may not properly describe this). 8 when I send press RET to execute the line which will result in printing the dataframe, and another 8 when the dataframe has been printed:
1 -> (tsc-parse-chunks #<user-ptr ptr=0x5606bb9feee0 finalizer=0x7fa35c71a600> tsc--buffer-input #<user-ptr ptr=0x5606c53039e0 finalizer=0x7fa35c71a910>)
1 <- tsc-parse-chunks: #<user-ptr ptr=0x5606b7726ef0 finalizer=0x7fa35c71a910>

Tracing the edit tree does the same (16 outputs), with output like this:
1 -> (tsc-edit-tree #<user-ptr ptr=0x5606b8b927d0 finalizer=0x7fa35c71a910> 42295 42295 42296 #1=(794 . 58) #1# (795 . 0))
1 <- tsc-edit-tree: nil

The highlight-region trace has output such as this, again many entries:
1 -> (tree-sitter-hl--highlight-region 54381 54439 nil)
1 <- tree-sitter-hl--highlight-region: (jit-lock-bounds 54282 . 54609)

Other than the profile report, which leads me to believe that too many REPL actions trigger re-parsing, I don't know how to interpret the output.

I believe the main problem is that tree-sitter-do-parse is called many times.

Yes, it can be a problem. It also depends on whether these parses are from-scratch or incremental (and if incremental, whether the region to re-parse is too large). The third approach of advising the parsing and highlighting functions would help getting more data on this.

Here a chunk of the profiler report:
- jupyter-repl-insert-prompt                 232  15%
    - tree-sitter--after-change                 156  10%
        - tree-sitter--do-parse                    156  10%

Would it be possible for you to copy the whole profiler report, as text?

making a large pandas dataframe and repeatedly printing it

How large should this be? If you have a CSV file, I can try reproducing this myself.

I believe the main problem is that tree-sitter-do-parse is called many times.

Yes, it can be a problem. It also depends on whether these parses are from-scratch or incremental (and if incremental, whether the region to re-parse is too large). The third approach of advising the parsing and highlighting functions would help getting more data on this.

Here a chunk of the profiler report:
- jupyter-repl-insert-prompt                 232  15%
    - tree-sitter--after-change                 156  10%
        - tree-sitter--do-parse                    156  10%

Would it be possible for you to copy the whole profiler report, as text?

making a large pandas dataframe and repeatedly printing it

How large should this be? If you have a CSV file, I can try reproducing this myself.

I will do this soon and also prepare a test case with which you can reproduce the issue!

I will do this soon and also prepare a test case with which you can reproduce the issue!

Here's the full profiler report:
https://gist.github.com/timlod/6111d2f96357f55b1d2cc1976ac9740f
The advice output is:
[*jupyter-repl[python 3.8.6]-env*] tree-sitter-hl--highlight-region 3
Error during redisplay: (jit-lock-function 53070) signaled (wrong-type-argument number-or-marker-p nil)
[*jupyter-repl[python 3.8.6]-env*] tree-sitter-hl--highlight-region 500 [7 times]
[*jupyter-repl[python 3.8.6]-env*] tree-sitter-hl--highlight-region 203

Now, to reproduce, you can use the following:

Open http://download.geonames.org/export/dump/countryInfo.txt
Copy all text starting at ISO	ISO3	ISO-Numeric	fips	... (do not include the leading # on that line) and write it to a file, e.g. test.tsv
Open a REPL and import pandas as pd
Load the file as df = pd.read_table("test.tsv")
Just display df many times (just type df + RET, maybe 20 or so times)

You should notice the REPL slowing down - at first you may see no delay, later the cell indicator on the left will show a brief [*] before displaying. The slowdown is starker with bigger and varied dataframes, but you should be able to notice it with this test case.
Let me know if this helps!

Here's the full profiler report:
https://gist.github.com/timlod/6111d2f96357f55b1d2cc1976ac9740f
The advice output is:
[*jupyter-repl[python 3.8.6]-env*] tree-sitter-hl--highlight-region 3
Error during redisplay: (jit-lock-function 53070) signaled (wrong-type-argument number-or-marker-p nil)
[*jupyter-repl[python 3.8.6]-env*] tree-sitter-hl--highlight-region 500 [7 times]
[*jupyter-repl[python 3.8.6]-env*] tree-sitter-hl--highlight-region 203

Now, to reproduce, you can use the following:

Open http://download.geonames.org/export/dump/countryInfo.txt
Copy all text starting at ISO	ISO3	ISO-Numeric	fips	... (do not include the leading # on that line) and write it to a file, e.g. test.tsv
Open a REPL and import pandas as pd
Load the file as df = pd.read_table("test.tsv")
Just display df many times (just type df + RET, maybe 20 or so times)

You should notice the REPL slowing down - at first you may see no delay, later the cell indicator on the left will show a brief [*] before displaying. The slowdown is starker with bigger and varied dataframes, but you should be able to notice it with this test case.
Let me know if this helps!

Thanks, I'll check it out.

Thanks, I'll check it out.

Maybe jupyter-repl-mode or inferior-python-mode are doing something
special with text changes.

In jupyter-repl-mode the only text changes that are done are to add a
special text property that distinguishes REPL input from REPL output
and to re-insert newlines, marking them as continuing REPL input to
another line.
In the profiler report that @timlod showed it seems that lots of
parsing calls happen because of text property changes and insertions
that are done to maintain the structure of the REPL buffer.  These
happen around the jupyter-repl-insert-prompt calls that are shown in
the traceback.
I think the main issue is that the REPL buffer contains regions of
output, not meant to be fontified in any programming language, but
tree-sitter nonetheless wants to fontify those regions when it is
called in after-change-functions.
The way that jupyter-repl-mode uses the fontification functions is
that it narrows down to the REPL input cell, the region that is
guaranteed to be in the programming language of the REPL buffer and
allows the fontification function of the language to do what it
needs.
Would there be a way to have tree-sitter work on narrowed
regions of a buffer in a similar way instead of the
whole buffer?

I think the main issue is that the REPL buffer contains regions of output, not meant to be fontified in any programming language, but tree-sitter nonetheless wants to fontify those regions when it is called in after-change-functions.

Yeah, I also think tree-sitter-mode shouldn't be enabled directly in these buffers. It's better for the integration to be done through a new minor e.g. tree-sitter-jupyter-repl-mode (or optionally in jupyter-repl-mode itself).

Would there be a way to have tree-sitter work on narrowed regions of a buffer in a similar way instead of the whole buffer?

That's a useful functionality that I wanted to add, but haven't started yet. There's tsc-set-included-ranges, but for this use case restriction-by-narrowing is probably more suitable.

The way that jupyter-repl-mode uses the fontification functions is that it narrows down to the REPL input cell, the region that is guaranteed to be in the programming language of the REPL buffer and allows the fontification function of the language to do what it needs.

I think I can give a try at implementing the integration. I have some questions to get started:

How do we provide jupyter-repl-mode the fontification function?
How does the fontification function know whether the input cell it's working on is the currently editable cell?
Are there cell-editing hooks, as opposed to before-change-functions and after-change-functions, which run for things like inserting the output cells as well?

How do we provide jupyter-repl-mode the fontification function?

The fontification function is copied over from the value of font-lock-defaults for the major-mode of the REPL language in the function jupyter-repl-initialize-fontification. The only thing jupyter-repl-mode does with the major-mode fontification function is call it on input cell regions, see jupyter-repl-font-lock-fontify-region. So what happens in the case of @timlod is that the major-mode of the REPL language has tree-sitter enabled and the fontification function gets propagated over to the REPL buffer's fontification function. And the tree-sitter fontification function doesn't work because we don't have the necessary buffer local variables set up.

How does the fontification function know whether the input cell it's working on is the currently editable cell?

This is done by marking the currently editable text as being part of an input cell through the field text property. If text has been marked with a field text property of cell-code then it is part of an input cell. The output cell regions don't have such a text property. The marking is done an after-change-functions function. See jupyter-repl-do-after-change and the associated jupyter-repl-after-change. Once the cell code has been marked, the function jupyter-repl-map-cells is used to iterate over regions of input/output cells by the jupyter-repl-mode fontification function. This is how input/output regions are detected by the fontification process.

Are there cell-editing hooks, as opposed to before-change-functions and after-change-functions, which run for things like inserting the output cells as well?

There aren't any hooks for insertions of input/output cells. But I would be happy to look into how they could be added if I had a reason on why they would be needed.
Please let me know if there is any other information that I could provide. Thanks for looking into this.

There aren't any hooks for insertions of input/output cells. But I would be happy to look into how they could be added if I had a reason on why they would be needed.

I mean hooks for edits within an input cell, not new cell insertions. tree-sitter's incremental parsing mode needs to precisely track all text modifications. Cell-editing hooks would help with filtering out uninteresting buffer modifications.
I'm thinking of an integration where the parse tree is associated with the "active input cell", while previous read-only cells are not touched, as they were already highlighted.


Addded PropertySetterRemoved and PropertyGetterRemoved

@PMudra I sent you a message on Gitter. There's an issue with the package deployment.

Thanks for reminding me. I will have a look soon. I guess I have to renew the nuget token.

A new version of the nuget package including these changes has been deployed now: https://www.nuget.org/packages/ApiCheck/1.1.91


Error in class info generation!

Hi, I receive the following error on the client-end regarding a ClassNotFoundException with a JavaFX + Spring Boot project using Dolphin Platform 0.8.13. There are no visible errors on the server side.
[WARNING]
java.lang.RuntimeException: Error in class info generation!
	at com.canoo.dolphin.impl.ClassRepositoryImpl$1.modelStoreChanged(ClassRepositoryImpl.java:71)
	at org.opendolphin.core.ModelStoreListenerWrapper.modelStoreChanged(ModelStoreListenerWrapper.java:57)
	at org.opendolphin.core.ModelStore.fireModelStoreChangedEvent(ModelStore.java:344)
	at org.opendolphin.core.ModelStore.add(ModelStore.java:137)
	at org.opendolphin.core.client.ClientModelStore.add(ClientModelStore.java:66)
	at org.opendolphin.core.client.comm.ClientResponseHandler.handleCreatePresentationModelCommand(ClientResponseHandler.java:116)
	at org.opendolphin.core.client.comm.ClientResponseHandler.dispatchHandle(ClientResponseHandler.java:53)
	at org.opendolphin.core.client.comm.AbstractClientConnector.dispatchHandle(AbstractClientConnector.java:202)
	at org.opendolphin.core.client.comm.AbstractClientConnector.processResults(AbstractClientConnector.java:170)
	at org.opendolphin.core.client.comm.AbstractClientConnector$2$1$1.run(AbstractClientConnector.java:121)
	at com.sun.javafx.application.PlatformImpl.lambda$null$173(PlatformImpl.java:295)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.sun.javafx.application.PlatformImpl.lambda$runLater$174(PlatformImpl.java:294)
	at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:95)
	at com.sun.glass.ui.win.WinApplication._runLoop(Native Method)
	at com.sun.glass.ui.win.WinApplication.lambda$null$148(WinApplication.java:191)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException: com.example.MyDto
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:264)
	at com.canoo.dolphin.impl.ClassRepositoryImpl$1.modelStoreChanged(ClassRepositoryImpl.java:65)
	... 16 more

The com.example.MyDto is a @DolphinBean which contains other @DolphinBean objects. I can see the class file for com.example.MyDto so it is not a missing file problem.
If I try to open the same window that generated the above error (still on the client side), I receive a different error:
[WARNING]
java.lang.NullPointerException: Argument 'classInfo' may not be null
	at java.util.Objects.requireNonNull(Objects.java:228)
	at com.canoo.dolphin.util.Assert.requireNonNull(Assert.java:45)
	at com.canoo.dolphin.impl.AbstractBeanBuilder$1.onEvent(AbstractBeanBuilder.java:61)
	at com.canoo.dolphin.impl.EventDispatcherImpl.onAddedHandler(EventDispatcherImpl.java:109)
	at com.canoo.dolphin.impl.EventDispatcherImpl.modelStoreChanged(EventDispatcherImpl.java:77)
	at org.opendolphin.core.ModelStoreListenerWrapper.modelStoreChanged(ModelStoreListenerWrapper.java:57)
	at org.opendolphin.core.ModelStore.fireModelStoreChangedEvent(ModelStore.java:344)
	at org.opendolphin.core.ModelStore.add(ModelStore.java:137)
	at org.opendolphin.core.client.ClientModelStore.add(ClientModelStore.java:66)
	at org.opendolphin.core.client.comm.ClientResponseHandler.handleCreatePresentationModelCommand(ClientResponseHandler.java:116)
	at org.opendolphin.core.client.comm.ClientResponseHandler.dispatchHandle(ClientResponseHandler.java:53)
	at org.opendolphin.core.client.comm.AbstractClientConnector.dispatchHandle(AbstractClientConnector.java:202)
	at org.opendolphin.core.client.comm.AbstractClientConnector.processResults(AbstractClientConnector.java:170)
	at org.opendolphin.core.client.comm.AbstractClientConnector$2$1$1.run(AbstractClientConnector.java:121)
	at com.sun.javafx.application.PlatformImpl.lambda$null$173(PlatformImpl.java:295)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.sun.javafx.application.PlatformImpl.lambda$runLater$174(PlatformImpl.java:294)
	at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:95)
	at com.sun.glass.ui.win.WinApplication._runLoop(Native Method)
	at com.sun.glass.ui.win.WinApplication.lambda$null$148(WinApplication.java:191)
	at java.lang.Thread.run(Thread.java:745)

Is there anything I should look at in order to isolate the cause of this problem? I'm not sure if the following is related, but I have also recently noticed that I cannot run my JavaFX application directly in Eclipse (the program terminates immediately) but instead have to use mvn compile exec:java.

Hi,
for me the eclipse problem and the CNFE may be results based on the same problem. Maybe something in your maven setup is wrong so that the module that contains the MyDTO class is not on the class path. You can simply check this by creating a MyDTO instance by hand directly in the main method of the client:
public static void main(...) { MyDto instance = new MyDto(); }
If it's not on the class path a CNFE will be thrown, too. Otherwise this is something different and we can have a deeper look.

Thanks for the suggestion. I double checked to see if I could see the common jar in Maven and renamed it to something new like common2 to test if it was being updated and created properly. I setup Eclipse to use a different Maven installation and I found that I needed to run mvn install to make sure that the new common2 showed up after which I was able to use the Dolphin Bean without the CNFE error.
Maybe it's because I am still learning to use Maven but it could be helpful to add that the common package should have the install goal added to make sure updated versions get added to the local repository (where they later get picked up and used by the client and server). At least that is the case when running the server and client in Maven through Eclipse. I think I didn't encounter this problem before because I could run the ClientApplication as a Java Application in Eclipse. And all of that said, now it doesn't seem that the original problem I had with Eclipse not running the ClientApplication has too much to do with this CNFE problem.
That said, I can't replicate this behaviour on my other computer so it may be a problem with my Eclipse workspace.

After some investigation, it turns out that there was a problem with the Nvidia Graphics Driver. Updating to the latest version resolved this issue as suggested by this answer.


Feature Request : Auto close download window after download complete.

Hello,
I would like to suggest a new feature for the project that would automatically close the download window once the download is complete. This would provide a more seamless user experience and reduce the need for manual intervention.
Currently, when a user initiates a download, they have to manually close the download window once the process is finished. This can be inconvenient, especially if the user forgets to close the window or if they have multiple downloads running simultaneously.
I believe this feature would be a valuable addition to the project and would greatly enhance the overall user experience. I'm happy to provide any additional details or feedback as needed.
Thank you for considering this feature request.

it is now optional you can disable it in the settings in the next release


Caffeine-NG expects a different DBus Service Architecture than Hypridle's

I recently switched to hypridle, and wanted to continue using caffeine-ng for idle inhibition. However, while chromium's idle inhibit was successful, caffeine-ng's is not.
Looking at caffeine-ng's code:
...
    def inhibit(self, reason=INHIBITION_REASON) -> None:
        self.__proxy = self.bus.get_object(
            "org.freedesktop.ScreenSaver",
            "/ScreenSaver",
        )
        self.__proxy = dbus.Interface(
            self.__proxy,
            dbus_interface="org.freedesktop.ScreenSaver",
        )
        self.__cookie = self.__proxy.Inhibit("Caffeine", INHIBITION_REASON)

        self.running = True

...

They try to get a ScreenSaver/ object from the root service, then access the org.freedesktop.ScreenSaver interface with inhibit and uninhibit from that. On HyprIdle (and I suspect in the standard), there is instead an org/freedesktop/ object, which then contains the same interface.
If this is more a problem with caffeine-ng, feel free to close this, and I'll open one with them. I suspect this might be some of the reason why others are having some trouble with idle inhibition.

I will note the two linked reference implementations of the interface have both paths.

The /ScreenSaver path seems to be some historic, legacy one. The standard says about the /org/freedesktop/ScreenSaver.
From what I can see in the code, this should be fairly easy to add. Just create another ScreenSaver object in CHypridle::setupDBUS() with the other path. The m_sDBUSState struct would need some changes though, to store more than one object reference (either change it to std::vector or just add another field in the struct as there probably won't be more than 2 anyway).


Unable to use non-shaded client with AuthenticationToken

When using the non-shaded pulsar client enabling AuthenticationToken causes
An attempt was made to call a method that does not exist. The attempt was made from the following location:

    org.springframework.boot.autoconfigure.pulsar.PulsarPropertiesMapper.getAuthenticationParamsJson(PulsarPropertiesMapper.java:90)

The following method did not exist:

    'org.apache.pulsar.shade.com.fasterxml.jackson.databind.ObjectMapper org.apache.pulsar.common.util.ObjectMapperFactory.create()'

The calling method's class, org.springframework.boot.autoconfigure.pulsar.PulsarPropertiesMapper, was loaded from the following location:

A sample project with the problem

Thanks for the report @austek ,
While the ObjectMapperFactory is not shaded, it does indeed look like the returned ObjectMapper is in fact a shaded variant.
This issue is actually in Spring Boot at this point but I will submit a PR to that project under this ticket.

@austek we do recommend using the shaded pulsar client w/ Spring Boot as the Pulsar client uses earlier versions of 3rd party libs that are also used by Spring Boot. You may run into classpath version mismatches.  Regardless, I am going to submit a fix for this issue.

@austek we do recommend using the shaded pulsar client w/ Spring Boot as the Pulsar client uses earlier versions of 3rd party libs that are also used by Spring Boot. You may run into classpath version mismatches. Regardless, I am going to submit a fix for this issue.

I understand the recommendation, however security scans picked up CVEs which needs to be addressed and with shaded dependencies that's not really easy

I understand @austek , it sounds like you are using the unshaded so that you can override the vulnerable dependencies.
Did you file an issue w/ Pulsar on the affected libs? If not, please let me know which ones in particular and I will file an issue and get a fix into Pulsar.
Thanks

@austek the fix has been merged into Spring Boot 3.2.x branch and will be available in Spring Boot 3.2.3 on 2024-11-22.


Please add documentation about Heart of the sky drop

I could not find any information online about how to find Heart of the sky and the ceremonial knife description makes you think it's only your own wings.
For anyone else looking up this:
Hit the dragon on the head with a dipped ceremonial knife and then kill it (using whatever item), at least that's what I understood from reading the source code.

In the future, I pretend to split Winged's Creative Flight into another mod.
Also @GabrielOlvH on this because this was your idea.

In the future, I pretend to split Winged's Creative Flight into another mod.
Also @GabrielOlvH on this because this was your idea.

Is the heart of the sky drop guaranteed/still working? I'm in the latest version of the All of Fabric 3 modpack with version 1.16.5 - 2.1.4 of the Winged Mod and even using the ceremonial knife as described above could not get anything but a regular core of zephry to drop from the dragon - no heart of the sky :(

Could you make a short video to it? I cant figure out how it works


Empty list returned by ListCredentialsForProofRequestAsync for a predicate

ListCredentialsForProofRequestAsync from DefaultProofService  returns empty list for both predicate with restrictions and without restrictions. Not sure if this is a vlid bug, please someone advice

Have you solved this problem as I'm facing the same thing even when my credential is in issued state


[Feature]: Adding a top x search list to front page

Context
A feature request came in for a list of the top searched terms of a given day to be displayed on the front page to give users a potential starting point for their curiosity.
Problem and/or Opportunity
To be able to better serve peoples curiosities (i.e. those people who don't know where to start) a feature was proposed to add a top x search term list to the front page so people had a place to start going down the rabbit hole.  The list should ideally be created from the most searched terms of a given day but can be made a rotating list of terms for the time being.
Proposed Solution
We will look to add a small list of terms that a user can click into that would sit on the landing page but just below the search bar.  For an initial implementation we can look to make it a rotating list of terms given some parameter (maybe time of day) and have each term be a link into its definiton.  Ideally we'd want this feature to be driven by the search terms people are actually looking up on a given day so some effort can be spent to see the different ways that can be achieved.
Testing the changes
Testing the changes will involve adding unit tests, smoke testing the new changes to test it's functionality and making sure that existing functionality isn't broken
Additional Information
No response

Is there any way to fuzzy search arweave graphql API ?

I don't think there is a way just re-reading the documentation.  The way the document suggests searching is to use it to search for transactionId's and then taking that transactionId and querying arweave directly.  I went a slightly different route with my design where i stuck basically everything as a tag (thus metadata) and preform the search that way.  The nature of the data is such that I can get away with storing everything I need as a tag; however, it's not ideal (or at least the way i would do it in web2) since basically the definition is not only the data but part of the metadata as well.  I did that so i can reduce the number of network calls i needed to make so i can live with the trade off.

Archiving this for now but may re-introduce at a later time


chore: bdd-spring-1573695288 to 0.0.1

chore: Promote bdd-spring-1573695288 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Create CONTRIBUTING.md

please add hacktoberfest label to thispull request

please fix this too

@Devansh-Singh-Parmar corrected


bug: wagmi/cli generated contractRead hooks doesn't have typed argument

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.1.14
Current Behavior
when import one of generated hooks there are two different behavior in typescript:
1- useFunctionNameRead({  //there is no type here and you can define any property })
2- useFunctionNameWrite({  //intellisense works fine })
Expected Behavior
currently type of useFunctionNameRead's argument is :
Omit<UseContractReadConfig<readonly [{ readonly type: "event"; readonly inputs: readonly [{ readonly name: "owner"; readonly type: "address"; readonly indexed: true; }, { readonly name: "spender"; readonly type: "address"; readonly indexed: true; }, { ...; }]; readonly name: "Approval"; }, ...; }],...
it should has those types that a default useContractRead has.
Steps To Reproduce
use react and typescript and generate wagmi hook with cli and an erc20ABI and name : ERC20
then add useERC20Name({ hello:"world" }) somewhere and see typescript doesn't complain.
Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
No response

I found the issue in the react.ts file at https://github.com/wagmi-dev/wagmi/blob/main/packages/cli/src/plugins/react.ts. To fix it, I recommend removing as any from the following line, which is repeated several times throughout the file:
config: Omit<UseContractReadConfig<typeof ${contract.meta.abiName}, TFunctionName, TSelectData>, 'abi'${omitted}>${typeParams} = {} as any

https://wagmi.sh/react/typescript#type-inference


Unable to get any functionality out of hyprgrass 0.7, hyprland 0.41.1

Hello again (and sorry to bother you), I am the author of #140. I have now updated to Hyprland 0.41.1 and Hyprgrass (<3) 0.7.0. I am able to compile Hyprgrass, but I am unable to get it to work. By that I mean that none of the bindings that I set seem to be active. I am at a loss. The built-in workspace_swipe gesture does work, so it's not like my touchpad is broken.
I am opening this issue to ask:

Does anything on my config look weird?
Is there anyway that I can provide logs to aid debugging?

Setup
OS: Nixos
relevant flake.nix inputs:
hyprland = {
  type = "git";
  # This revision is a few commits after version 0.41.1
  url = "https://github.com/hyprwm/Hyprland?rev=e0e3c4c6ae15af88ac5fd5ab959adfe45a2e1dca";
  submodules = true;
  inputs.nixpkgs.follows = "nixpkgs";
};
hyprgrass = {
   url = "github:horriblename/hyprgrass?ref=v0.7.0";
   inputs.hyprland.follows = "hyprland";
};

The file where I enable hyprland.
wayland.windowManager.hyprland = {
  enable = true;
  extraConfig = builtins.readFile ./hyprland.conf;
  plugins = [
    pkgs.hy3
    inputs.hycov.packages.x86_64-linux.hycov
    inputs.hyprgrass.packages.x86_64-linux.default
  ];
  settings = {
    exec-once = [
      "${pkgs.dbus}/bin/dbus-update-activation-environment --all"
    ];
  };
  systemd = {
    enable = true;
    variables = ["--all"];
    extraCommands = [
      "systemctl --user stop graphical-session.target"
      "systemctl --user start hyprland-session.target"
    ];
  };
  xwayland.enable = true;
};

Finally, here's my hyprgrass configuration:
plugin:touch_gestures {
  # The default sensitivity is probably too low on tablet screens,
  # I recommend turning it up to 4.0
  sensitivity = 1.0
  # must be >= 3
  workspace_swipe_fingers = 3

  # switching workspaces by swiping from an edge, this is separate from workspace_swipe_fingers
  # and can be used at the same time
  # possible values: l, r, u, or d
  # to disable it set it to anything else
  workspace_swipe_edge = d
  # in milliseconds
  long_press_delay = 400
  # swipe left from right edge
  hyprgrass-bind = , edge:r:l, workspace, +1
  # swipe up from bottom edge
  hyprgrass-bind = , edge:d:u, exec, firefox
  # swipe down from left edge
  hyprgrass-bind = , edge:l:d, exec, pactl set-sink-volume @DEFAULT_SINK@ -5%
  # swipe down from left edge
  hyprgrass-bind = , edge:r:u, exec, pactl set-sink-volume @DEFAULT_SINK@ +5%
  # swipe down with 4 fingers
  # NOTE: swipe events only trigger for finger count of >= 3
  hyprgrass-bind = , swipe:3:u, fullscreen, 1PR ready
  # NOTE: swipe events only trigger for finger count of >= 3
  hyprgrass-bind = , swipe:4:d, killactive
  # swipe diagonally left and down with 3 fingers
  # l (or r) must come before d and u
  hyprgrass-bind = , swipe:3:ld, exec, foot
  # tap with 3 fingers
  # NOTE: tap events only trigger for finger count of >= 3
  hyprgrass-bind = , tap:3, exec, pavucontrol
  # longpress can trigger mouse binds:
  hyprgrass-bindm = , longpress:2, movewindow
  hyprgrass-bindm = , longpress:3, resizewindow
}

hyprgrass is for touch screen mate

Oh, my, god......  This completely went over my head..... I am sorry for wasting your time..... Thank you for the plugin regardless


Unable to use camera node in 3d along with smoothing node

Scene causing the problem with smoothing node added:-

Script attached to Player node (Kinematic Body):-
extends KinematicBody
var constant_speed: Vector3 = Vector3(0, 0, -10)
func _physics_process(_delta):
    constant_speed = move_and_slide(constant_speed)

Output:-

Expected Output:-

As seen in the first output gif the player moves away from the camera which it shouldn't. The expected output is what it should look like.
The following scene without the smoothing node works as expected and gives the expected output:-

First thing to try is to make the smoothing node separate from the physics:
PlayerPhysics(rigidbody)
    CollisionShape
Player(smoothingnode)
    Camera
    Skeleton
        unamed

I've seen a few people make the smoothing node a child of the physics they are linked to. This can sometimes work, but it is very recommended against. I need to emphasize this more in the docs.
The reason being is the smoothing node will interpolate between two target positions, usually in global space, but by putting them below a moving node, the parent movements will be applied to the child AS WELL as the transform for smoothing. This can lead to jitter or worse.
I'm not sure this is the answer to your problem here, I'll try and replicate your problem, but it is worth a go. I'll also modify the docs again to try and make it more clear (this came up recently with another user with similar problem).

I've actually just been trying to replicate this but can't get the problem to occur. Would you be able to zip up the test project and drag it into the issue so I can try it?
While I highly recommend putting the visual representation on a different branch to the physics rep (see the updated docs), I'm not sure it is causing the problem here. It could be something in the setup of the skeleton.

Yes I've got it replicating. Can confirm that the solution is to make sure the SmoothingNode is NOT a child of the physics rep.
Actually this has made me realise I may be able to detect the situation of assigning the smoothing node to a parent or grandparent, and print an error messagebox, and how to fix it. +1
I'll see if this is possible and modify the addon.

Yep it worked. Your addon has been a huge help. Thank you for your time <3.

No problem, it's great to get feedback. :grin:


v1.21.1-1

What's  the reason about this new option? I'm using the Zigbee2mqtt Edge and I saw it in the log: "Option 'availability' does not exist in the schema for Zigbee2mqtt Edge"


Allow let to memoize similar methods in a single block by passing multiple arguments

For some specs I want to instantiate similar but distinct objects.
But instead of doing:
let(:thing) do
   thing = Thing.new
   thing.do_something
   thing
end

let(:another_thing) do
   thing = Thing.new
   thing.do_something
   thing
end

I'd like to be able to do:
let(:thing, :another_thing) do
   thing = Thing.new
   thing.do_something
   thing
end

My instinct is to close this, but I'm going to leave it open for some discussion first.
The reason is that let comes from lisp, in which it is used to bind values to variable names within a scope. What you propose makes it feel more like a factory method, which is conceptually a different animal, and I think this would just make it harder for new users to understand what let means.

That's a valid point.
Maybe I've been using let the wrong way (mostly as memoized factory methods) :)

Having multiple let occurrences of the same value is rare, IMO. I would resort to using a method:
def foo; :foo; end
let(:foo1) { foo }
let(:foo2) { foo }

Or iterate:
[:foo1, :foo2].each do |foo|
  let(foo) { the_repeated_value }
end

You're not doing anything wrong. Technically that's how it works, because Ruby lets us define methods and bind instance variables, but not bind local variables, but let should feel (subjective, I realize) like a local variable binding.


@-mentions are underdocumented

I wanted to play with them but wasn't entirely sure (just from a user's perspective) what I was supposed to do. The only docs I came across were in https://openctx.org/docs/providers/github, which says just:

Then use the @-mention type Github PRs & Issues and search for issues or pull requests to include in context using the followining [sic] possible query examples:

https://github.com/sourcegraph/sourcegraph/issues/1234

But those don't include an @. I tried putting an @ in front of them in my editor and nothing obvious happened. (Yes, I set up the GH Provider.)
And there are no docs I could see about other @-mention types, how they get parsed, assigned to a provider, etc.

I also found the docs confusing, but I found that I had to type "@", then select the "Github PRs" option, and then type those full examples. That's in the VSCode Cody extension.
It would be really nice if you could just type "@1234" to get the relevant context, since it should hopefully know the repo already.


Bad Uri

The browser seems to be more forgiving with malformed links than ruby.
I've got a site that I'm trying to extract urls from and because the url is not properly formed, ruby just borks with a Error when fetching url: bad URI(is not URI?) and stops parsing the rest of the page.
Example:
{
  "expected_update_period_in_days": "2",
  "url": "https://dl.dropboxusercontent.com/u/28950293/test.html",
  "type": "html",
  "mode": "on_change",
  "extract": {
    "url": {
      "css": "a",
      "value": "@href"
    },
    "title": {
      "css": "a",
      "value": "normalize-space(.)"
    }
  }
}

Is there any way to use something like uri_escape available for liquid during the extraction?
At the very least, I think it should ignore the bad uri, and continue trying to parse the rest of the links on the page.

WebsiteAgent automatically parses the url value in a created event as URL, resolving it as a relative URL from the current page, and parsing is done strictly there.  I think we could make it fall back to the original value, while I don't feel like applying uri_escape automatically.
An ugly workaround is to rename the key from url to something different and then make an EventFormattingAgent to transform the value through something like "url": "{{ key | uri_escape | uri_expand(base_uri) }}".

No, uri_escape shouldn't be applied automatically as it might end up double escaping.
I was thinking maybe a flag to set the escape option but then that didn't make much sense either because this seems like a one-off case specifically for extracting url.
The ugly workaround doesn't quite work in this case... The problem is that once the WebsiteAgent comes across the malformed url, it stops extracting. It will only output everything before it encountered the bad url (and nothing after).
If the html is as follows:

google

broken

escaped

Extract should try and process as many as possible, not stop after it finds a bad url. Ignoring the second one and just logging it would suffice I think.

Did you actually try the workaround?  The "rename the key from url to something different" part is essential because WebsiteAgent tries to parse a value as URI only if the key is "url".  WebsiteAgent wouldn't stop after a URI error unless it found a bad URL in the "url" key.

Sorry, I hadn't.
I just did and it does work.

OK, it's my turn to seek for a real fix.  I still think it's an idea to first try parsing a value as URL and if it fails then fall back to escape unescaped characters in it and retry parsing.  What do you think?

I spoke too soon. While the first part works, the second part fails...
It encodes the whole url instead of just the query string.
Unless I misinterpretted something?
Here are my agents:
WebsiteAgent
{
  "expected_update_period_in_days": "2",
  "url": "https://dl.dropboxusercontent.com/u/28950293/test.html",
  "type": "html",
  "mode": "on_change",
  "extract": {
    "item_url": {
      "css": "a",
      "value": "@href"
    },
    "title": {
      "css": "a",
      "value": "normalize-space(.)"
    }
  }
}

EventFormattingAgent
{
  "instructions": {
    "url": "{{item_url | uri_escape | uri_expand(base_uri) }}"
  },
  "mode": "merge"
}

Ah, of course.  uri_escape would escape the colon and slash as well.  What's needed here is something that does what Ruby's URI.escape (which had been deprecated as "misfeature") would do.

Running under Ruby 2.2.2, this issue goes away, and the WebsiteAgent runs as expected:
[
  {
    "url": "http://google.com",
    "title": "google"
  },
  {
    "url": "https://www.google.ca/search?q=some%20query",
    "title": "broken"
  },
  {
    "url": "https://www.google.ca/search?q=some%20query",
    "title": "escaped"
  }
]

I've got a different problem now: unicode characters in url
For a url like this in a site: http://ko.wikipedia.org/wiki/위키백과:대문
I get an error stating URI must be ascii only

Do you know which Gem is producing that error?

It seems the problem is this line.
Comment it out and the agent in the first post works...
Otherwise it gives this error:
I, [2015-07-29T16:11:12.466857 #20]  INFO -- : Fetching https://dl.dropboxusercontent.com/u/28950293/test.html
I, [2015-07-29T16:11:12.681116 #20]  INFO -- : Extracting html at a: ["http://google.com", "https://www.google.ca/search?q=some query", "https://www.google.ca/search?q=some%20query", "http://ko.wikipedia.org/wiki/위키백과:대문", "https://www.google.ca/search?q=위키백과:대문"]
I, [2015-07-29T16:11:12.684229 #20]  INFO -- : Extracting html at a: ["google", "broken", "escaped", "unicode url", "unicode param"]
I, [2015-07-29T16:11:12.685909 #20]  INFO -- : Storing new parsed result for 'AAA - Test Fetch': {"url"=>"http://google.com", "title"=>"google"}
I, [2015-07-29T16:11:12.716302 #20]  INFO -- : Storing new parsed result for 'AAA - Test Fetch': {"url"=>"https://www.google.ca/search?q=some%20query", "title"=>"broken"}
I, [2015-07-29T16:11:12.717489 #20]  INFO -- : Storing new parsed result for 'AAA - Test Fetch': {"url"=>"https://www.google.ca/search?q=some%20query", "title"=>"escaped"}
E, [2015-07-29T16:11:12.718580 #20] ERROR -- : Error when fetching url: URI must be ascii only "http://ko.wikipedia.org/wiki/\u{c704}\u{d0a4}\u{bc31}\u{acfc}:\u{b300}\u{bb38}"
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/uri/generic.rb:1100:in `rescue in merge'
/app/vendor/ruby-2.2.2/lib/ruby/2.2.0/uri/generic.rb:1097:in `merge'
/app/app/models/agents/website_agent.rb:320:in `block (3 levels) in check_url'
/app/app/models/agents/website_agent.rb:317:in `each'
/app/app/models/agents/website_agent.rb:317:in `block (2 levels) in check_url'
/app/app/models/agents/website_agent.rb:315:in `times'
/app/app/models/agents/website_agent.rb:315:in `block in check_url'
/app/vendor/bundle/ruby/2.2.0/gems/liquid-3.0.6/lib/liquid/context.rb:132:in `stack'
/app/app/models/agents/website_agent.rb:279:in `check_url'
/app/app/models/agents/website_agent.rb:266:in `block in check_urls'
/app/app/models/agents/website_agent.rb:265:in `each'
/app/app/models/agents/website_agent.rb:265:in `check_urls'
/app/app/models/agents/website_agent.rb:259:in `check'
/app/app/concerns/dry_runnable.rb:17:in `dry_run!'
/app/app/controllers/agents_controller.rb:53:in `dry_run'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/abstract_controller/base.rb:198:in `process_action'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_controller/metal/rendering.rb:10:in `process_action'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/callbacks.rb:117:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/callbacks.rb:117:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/callbacks.rb:505:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/callbacks.rb:505:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/callbacks.rb:92:in `_run_callbacks'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/callbacks.rb:776:in `_run_process_action_callbacks'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/callbacks.rb:81:in `run_callbacks'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/abstract_controller/callbacks.rb:19:in `process_action'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_controller/metal/rescue.rb:29:in `process_action'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/notifications.rb:164:in `block in instrument'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/notifications.rb:164:in `instrument'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/app/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.2/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/abstract_controller/base.rb:137:in `process'
/app/vendor/bundle/ruby/2.2.0/gems/actionview-4.2.2/lib/action_view/rendering.rb:30:in `process'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_controller/metal.rb:196:in `dispatch'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_controller/metal.rb:237:in `block in action'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/routing/route_set.rb:74:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/journey/router.rb:30:in `each'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/journey/router.rb:30:in `serve'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/routing/route_set.rb:819:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/warden-1.2.3/lib/warden/manager.rb:35:in `block in call'
/app/vendor/bundle/ruby/2.2.0/gems/warden-1.2.3/lib/warden/manager.rb:34:in `catch'
/app/vendor/bundle/ruby/2.2.0/gems/warden-1.2.3/lib/warden/manager.rb:34:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/etag.rb:24:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:38:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/head.rb:13:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/middleware/flash.rb:260:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:225:in `context'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:220:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.2/lib/active_record/query_cache.rb:36:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activerecord-4.2.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:649:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/callbacks.rb:88:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/callbacks.rb:88:in `_run_callbacks'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/callbacks.rb:776:in `_run_call_callbacks'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/callbacks.rb:81:in `run_callbacks'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.2/lib/rails/rack/logger.rb:38:in `call_app'
/app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.2/lib/rails/rack/logger.rb:20:in `block in call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/tagged_logging.rb:68:in `block in tagged'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/tagged_logging.rb:26:in `tagged'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/tagged_logging.rb:68:in `tagged'
/app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.2/lib/rails/rack/logger.rb:20:in `call'
/app/config/initializers/silence_worker_status_logger.rb:5:in `call_with_silence_worker_status'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.2/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/middleware/static.rb:113:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.2/lib/action_dispatch/middleware/ssl.rb:24:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.2/lib/rails/engine.rb:518:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.2/lib/rails/application.rb:164:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.2/lib/rails/railtie.rb:194:in `public_send'
/app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.2/lib/rails/railtie.rb:194:in `method_missing'
/app/vendor/bundle/ruby/2.2.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:576:in `process_client'
/app/vendor/bundle/ruby/2.2.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:670:in `worker_loop'
/app/vendor/bundle/ruby/2.2.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:525:in `spawn_missing_workers'
/app/vendor/bundle/ruby/2.2.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:140:in `start'
/app/vendor/bundle/ruby/2.2.0/gems/unicorn-4.8.3/bin/unicorn:126:in `<top (required)>'
/app/vendor/bundle/ruby/2.2.0/bin/unicorn:23:in `load'
/app/vendor/bundle/ruby/2.2.0/bin/unicorn:23:in `'

Oh wow, that looks like the error is deep in the Ruby standard library.  I wonder if escaping the unicode in some way would help?  Alternatively, we could possibly call to_s on it and then concatenate the strings ourselves instead of using the URI library.

Well, really, the sites should be encoding the urls properly... For my
particular use case, if huginn just skips the bad ones and carries on
trying to extract the rest, it's good enough.
On Jul 29, 2015 7:18 PM, "Andrew Cantino"<EMAIL_ADDRESS>wrote:

Oh wow, that looks like the error is deep in the Ruby standard library. I
wonder if escaping the unicode in some way would help? Alternatively, we
could possibly call to_s on it and then concatenate the strings ourselves
instead of using the URI library.
—
Reply to this email directly or view it on GitHub
https://github.com/cantino/huginn/issues/938#issuecomment-126161290.

You could definitely add a rescue similar to #943

I also have the same error - but with a different setup. I have tried both the RSS and the Website Agent, and the same result (error) - but different failures:
I have upgraded Ruby to 2.2.2 and also updated Huginn to the latest version from Git Master, but no luck.
The RSS agent is as follows:
{
"expected_update_period_in_days": "1",
"clean": "true",
"url": "[     "http://www.teekay.com/rss/pressrelease.aspx\",     "http://www.swireshipping.com/index.php?option=com_content&view=category&id=2&Itemid=27&format=feed&type=rss\",     "http://www.pacificbasin.com/en/global/rss_xml.php?cat=announcement\",     "http://www.ap-group.co.uk/feed/\",     "http://www.imo.org/Pages/PressBriefingsRSS.aspx\",     "http://www.incoships.com.au/rss_news.cfm\",     "http://www.iss-shipping.com/XML/issnewsfeed.xml\",     "http://www.gepowerconversion.com/feed/inspire\",     "http://www.nyk.com/english/release/top_news.xml\",     "http://www.shi.samsung.co.kr/Eng/Rss/pr.aspx\",     "http://feeds.feedburner.com/EcoMarinePowerNews\",     "http://www.brittany-ferries.co.uk/press-office?articleaction=rss\",     "http://www.gtt.fr/feed/\",     "http://panasonic.net/news/rss/topics.xml\",     "http://www.rotork.com/en/media/rss\",     "http://www.imageline.co.uk/news-rss.php?news_id=16\",     "http://www.khi.co.jp/english/news_atom/news.xml\",     "http://www.raytheon-anschuetz.com/?type=9817\",     "http://worldmaritimenews.com/feed\",     "http://maritime-connector.com/news-rss/\",     "http://www.seadiscovery.com/Services/MarineTechnologyNewsXML.aspx\",     "http://www.joc.com/rss/13/all/rss.xml\",     "http://www.rolls-royce.com/press/rss.jsp\",     "http://www.wartsila.com/ss/Satellite?childpagename=WCom%2FUtilities%2FRSS&p=1267106760296&packedargs=locale%3Den%26newstitle%3DAll%2Bnews%2Bfrom%2BW%25C3%25A4rtsil%25C3%25A4%26rsscategory%3Dall%26site%3DWartsila&pagename=WCom%2FCommon%2FThirdPartyWrapper\",     "http://www.mandieselturbo.com/web/rss.aspx\",     "http://www.imo.org/MediaCentre/PressBriefings/_layouts/listfeed.aspx?List={1FC6FB5E-156F-4CF2-A9F2-CCF052B87DAC}\",     "http://www.elabor8.co.uk/feed/\",     "http://j-l-a.com/press-releases?format=feed&type=atom\",     "http://www.businessweek.com/feeds/most-popular.rss\",     "http://www.indiatimes.com/feeds/feeds.xml\",     "http://www.wartsila.com/ss/Satellite?childpagename=WCom%2FUtilities%2FRSS&p=1267106760296&packedargs=locale%3Den%26newstitle%3DMarine%2BSolutions%2BNews%26rsscategory%3DMarine%2BSolutions%26site%3DWartsila&pagename=WCom%2FCommon%2FThirdPartyWrapper\",     "http://www.corporate.man.eu/en/technicalpages/RSS-Feed.html\",     "http://www.daimler.com/rss/5-1-494337.xml\",     "http://www.ship-technology.com/feeds/news-feed.xml\",     "http://www.maritimedenmark.dk/rss.aspx\",     "http://www.channelnewsasia.com/rss/latest_cna_asiapac_rss.xml\",     "http://www.channelnewsasia.com/rss/latest_cna_biz_rss.xml\",     "http://rssfeeds.shell.com/shell_media_releases\",     "http://www.tognum.com/press/press-releases/?type=100\",     "http://maritimeglobalnews.com/rss\",     "http://www.maerskpress.com/rss/Latest-News\",     "http://www.scania.com/_inc/rss.aspx\",     "http://www.chevron.com/news/press/articles.rss\",     "http://www.westfalia-separator.com/home/backend.php\",     "http://blogactiv.eu/feed/rss/\",     "http://www.littelfuse.com/rss.xml\",     "http://www.getransportation.com/index.php?option=com_ijoomla_rss&act=xml&cat=15&feedtype=RSS2.0\",     "http://www.micanti.com/feed/\",     "http://finance.thestandard.com.hk/feed/breaking.xml\",     "http://www.businesswire.com/portal/site/home/news/industry/?vnsId=31121\",     "http://tentea.ec.europa.eu/scripts/rss.php?channel=112470000004394\",     "http://www.kline.co.jp/en/news/news.xml\",     "http://www.agv.gr/?feed=rss2\",     "http://ir.horizonlines.com/corporate.rss?c=188937&Rule=Cat=news~subcat=ALL\",     "http://www.vanoord.com/news/rss.xml\",     "http://www.inmarsat.com/rss/index.htm?type=pressrelease\",     "http://www.tognum.com/index.php?id=1698&type=100&tt_news[category]=20\",     "http://www.zim.com/newsrss.xml\",     "https://www.dynamar.com/news/rss\",     "http://www.minervamarine.com/rss.xml\" ]"
}
The error I get is:
E, [2015-08-17T15:41:07.077118 #20] ERROR -- : Failed to fetch [ARRAY OF URLS AS ABOVE] with message 'bad URI(is not URI?): [     "http://www.teekay.com/rss/pressrelease.aspx",     "http://www.swireshipping.com/index.php':
For the Website agent, I get the following:
{
"expected_update_period_in_days": "1",
"url": "["http://www.teekay.com/rss/pressrelease.aspx\",\"http://www.swireshipping.com/index.php?option=com_content&view=category&id=2&Itemid=27&format=feed&type=rss\",\"http://www.pacificbasin.com/en/global/rss_xml.php?cat=announcement\",\"http://www.ap-group.co.uk/feed/\",\"http://www.imo.org/Pages/PressBriefingsRSS.aspx\",\"http://www.incoships.com.au/rss_news.cfm\",\"http://www.iss-shipping.com/XML/issnewsfeed.xml\",\"http://www.gepowerconversion.com/feed/inspire\",\"http://www.nyk.com/english/release/top_news.xml\",\"http://www.shi.samsung.co.kr/Eng/Rss/pr.aspx\",\"http://feeds.feedburner.com/EcoMarinePowerNews\",\"http://www.brittany-ferries.co.uk/press-office?articleaction=rss\",\"http://www.gtt.fr/feed/\",\"http://panasonic.net/news/rss/topics.xml\",\"http://www.rotork.com/en/media/rss\",\"http://www.imageline.co.uk/news-rss.php?news_id=16\",\"http://www.khi.co.jp/english/news_atom/news.xml\",\"http://www.raytheon-anschuetz.com/?type=9817\",\"http://worldmaritimenews.com/feed\",\"http://maritime-connector.com/news-rss/\",\"http://www.seadiscovery.com/Services/MarineTechnologyNewsXML.aspx\",\"http://www.joc.com/rss/13/all/rss.xml\",\"http://www.rolls-royce.com/press/rss.jsp\",\"http://www.wartsila.com/ss/Satellite?childpagename=WCom%2FUtilities%2FRSS&p=1267106760296&packedargs=locale%3Den%26newstitle%3DAll%2Bnews%2Bfrom%2BW%25C3%25A4rtsil%25C3%25A4%26rsscategory%3Dall%26site%3DWartsila&pagename=WCom%2FCommon%2FThirdPartyWrapper\",\"http://www.mandieselturbo.com/web/rss.aspx\",\"http://www.imo.org/MediaCentre/PressBriefings/_layouts/listfeed.aspx?List={1FC6FB5E-156F-4CF2-A9F2-CCF052B87DAC}\",\"http://www.elabor8.co.uk/feed/\",\"http://j-l-a.com/press-releases?format=feed&type=atom\",\"http://www.businessweek.com/feeds/most-popular.rss\",\"http://www.indiatimes.com/feeds/feeds.xml\",\"http://www.wartsila.com/ss/Satellite?childpagename=WCom%2FUtilities%2FRSS&p=1267106760296&packedargs=locale%3Den%26newstitle%3DMarine%2BSolutions%2BNews%26rsscategory%3DMarine%2BSolutions%26site%3DWartsila&pagename=WCom%2FCommon%2FThirdPartyWrapper\",\"http://www.corporate.man.eu/en/technicalpages/RSS-Feed.html\",\"http://www.daimler.com/rss/5-1-494337.xml\",\"http://www.ship-technology.com/feeds/news-feed.xml\",\"http://www.maritimedenmark.dk/rss.aspx\",\"http://www.channelnewsasia.com/rss/latest_cna_asiapac_rss.xml\",\"http://www.channelnewsasia.com/rss/latest_cna_biz_rss.xml\",\"http://rssfeeds.shell.com/shell_media_releases\",\"http://www.tognum.com/press/press-releases/?type=100\",\"http://maritimeglobalnews.com/rss\",\"http://www.maerskpress.com/rss/Latest-News\",\"http://www.scania.com/_inc/rss.aspx\",\"http://www.chevron.com/news/press/articles.rss\",\"http://www.westfalia-separator.com/home/backend.php\",\"http://blogactiv.eu/feed/rss/\",\"http://www.littelfuse.com/rss.xml\",\"http://www.getransportation.com/index.php?option=com_ijoomla_rss&act=xml&cat=15&feedtype=RSS2.0\",\"http://www.micanti.com/feed/\",\"http://finance.thestandard.com.hk/feed/breaking.xml\",\"http://www.businesswire.com/portal/site/home/news/industry/?vnsId=31121\",\"http://tentea.ec.europa.eu/scripts/rss.php?channel=112470000004394\",\"http://www.kline.co.jp/en/news/news.xml\",\"http://www.agv.gr/?feed=rss2\",\"http://ir.horizonlines.com/corporate.rss?c=188937&Rule=Cat=news~subcat=ALL\",\"http://www.vanoord.com/news/rss.xml\",\"http://www.inmarsat.com/rss/index.htm?type=pressrelease\",\"http://www.tognum.com/index.php?id=1698&type=100&tt_news[category]=20\",\"http://www.zim.com/newsrss.xml\",\"http://www.dynamar.com/news/rss\",\"http://www.minervamarine.com/rss.xml\"]",
"type": "xml",
"mode": "on_change",
"extract": {
"title": {
"css": "item title",
"value": ".//text()"
},
"url": {
"css": "item link",
"value": ".//text()"
},
"description": {
"css": "item description",
"value": ".//text()"
},
"pubDate": {
"css": "item pubDate",
"value": ".//text()"
}
}
}
E, [2015-08-17T15:43:14.839367 #17] ERROR -- : Ignoring a non-HTTP url: "["ESCAPED URL LIST FROM ABOVE"]"

It looks like you have the Array inside of a string.  It should be [ ... ], not "[ ... ]".

Hi there - was there a suggested resolution on this? I updated and started again with a fresh Huginn install in case I'd configured something incorrectly but no dice - the error I'm getting is with non-ASCII characters:
"ERROR -- : Error when fetching url: URI must be ascii only"

I'm not sure where this is at.
I've got it working on my Huginn instance running Ruby 2.2.2 and using this

@haroonis what URL is causing that error?

Thanks for the suggestion @irfancharania Irfan - I'm using a workaround for now. I've named the URL differently so it's not processed as a URL. Not ideal as I then have to append it to the domain name (it's a relative URL) however I'm not set up to recompile the code at the moment (I use Windows mainly!).
@cantino it includes a £ sign which works in the browser but isn't a compliant URL.

Does @irfancharania's #958 PR fix these issues?

I found it a bit tricky to install huginn in the first place so am not sure how I'd go about testing it! It looks to have failed some checks according to that link?

I believe @knu was going to take a look at that PR again.

Just pushed #1125!

Awesome!


Error on npm install, wrong version on npm

1.) Error on install
While doing npm install I get this:
><EMAIL_ADDRESS>install /PROJEKTNAME/node_modules/gulp-spritesmith/node_modules/spritesmith/node_modules/canvassmith/node_modules/canvas
> node-gyp rebuild

Package cairo was not found in the pkg-config search path.
Perhaps you should add the directory containing `cairo.pc'
to the PKG_CONFIG_PATH environment variable
No package 'cairo' found
gyp: Call to './util/has_cairo_freetype.sh' returned exit status 0. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/opt/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:343:16)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:820:12)
gyp ERR! System Darwin 13.4.0
gyp ERR! command "node" "/opt/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /PROJEKTNAME/node_modules/gulp-spritesmith/node_modules/spritesmith/node_modules/canvassmith/node_modules/canvas
gyp ERR! node -v v0.10.35
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok

Maybe duplicate of https://github.com/Automattic/node-canvas/issues/415?
2.) Wrong version on npm
npm has 0.0.2 as current version (see https://www.npmjs.com/package/gulp-spritesmith)

It looks like you are installing the wrong package. This one is gulp.spritesmith:
npm install gulp.spritesmith

gulp-spritesmith can be found here:
https://github.com/otouto/gulp-spritesmith
I opened an issue when we both released at the same time but the author hasn't budged on his request for an unnecessary feature.
https://github.com/Otouto/gulp-spritesmith/issues/3

Thank you for that quick help!
I see that we had "gulp.spritesmith": "^1.4.0", in our packages.json - i updated to 2.4.0 and now i can install it!


Fix transparent titlebar when lost focus on Linux

https://github.com/zed-industries/zed/issues/15112#issuecomment-2249375693

Thanks for the contribution @jlzhjp !


chore(master): release 1.1.71

:robot: I have created a release beep boop
1.1.71 (2023-05-29)
Miscellaneous

deps: lock file maintenance (e637393)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/keywind/releases/tag/v1.1.71 :sunflower:


crosstool_wrapper_driver_is_not_gcc error while building tf v2.8.0 and v2.9.0

Click to expand!
Issue Type
Build/Install
Source
source
Tensorflow Version
v2.8.0
Custom Code
No
OS Platform and Distribution
Ubuntu 20.04 LTS
Mobile device
--
Python version
3.8.10
Bazel version
4.2.1
GCC/Compiler version
GCC 7.5.0
CUDA/cuDNN version
11.2/8.1
GPU model and memory
GTX 1050 2GB Mobile
Current Behaviour?
Well, I expected the build to complete successfully from source. I had already tried with v2.9.0 without success and I have already followed [this](https://www.tensorflow.org/install/source) guide.

Standalone code to reproduce the issue
`
$ git clone https://github.com/tensorflow/tensorflow
$ cd tensorflow
$ git checkout v2.8.0
$ ./configure  # CUDA support -> Y, CUDA compiler -> nvcc, GCC -> /usr/bin/gcc-7
$ bazel build --config=opt -c opt //tensorflow/tools/pip_package:build_pip_package
`

Relevant log output
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=130
INFO: Reading rc options for 'build' from /home/edo/tensorflow/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /home/edo/tensorflow/.bazelrc:
  'build' options: --define framework_shared_object=true --java_toolchain=@tf_toolchains//toolchains/java:tf_java_toolchain --host_java_toolchain=@tf_toolchains//toolchains/java:tf_java_toolchain --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --enable_platform_specific_config --define=with_xla_support=true --config=short_logs --config=v2 --define=no_aws_support=true --define=no_hdfs_support=true --experimental_cc_shared_library
INFO: Reading rc options for 'build' from /home/edo/tensorflow/.tf_configure.bazelrc:
  'build' options: --action_env PYTHON_BIN_PATH=/usr/bin/python3 --action_env PYTHON_LIB_PATH=/usr/lib/python3/dist-packages --python_path=/usr/bin/python3 --action_env CUDA_TOOLKIT_PATH=/usr/local/cuda-11.2 --action_env TF_CUDA_COMPUTE_CAPABILITIES=6.1 --action_env LD_LIBRARY_PATH=/usr/local/cuda-11.2/lib64 --action_env GCC_HOST_COMPILER_PATH=/usr/bin/x86_64-linux-gnu-gcc-7 --config=cuda
INFO: Reading rc options for 'build' from /home/edo/tensorflow/.bazelrc:
  'build' options: --deleted_packages=tensorflow/compiler/mlir/tfrt,tensorflow/compiler/mlir/tfrt/benchmarks,tensorflow/compiler/mlir/tfrt/jit/python_binding,tensorflow/compiler/mlir/tfrt/jit/transforms,tensorflow/compiler/mlir/tfrt/python_tests,tensorflow/compiler/mlir/tfrt/tests,tensorflow/compiler/mlir/tfrt/tests/analysis,tensorflow/compiler/mlir/tfrt/tests/jit,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_tfrt,tensorflow/compiler/mlir/tfrt/tests/tf_to_corert,tensorflow/compiler/mlir/tfrt/tests/tf_to_tfrt_data,tensorflow/compiler/mlir/tfrt/tests/saved_model,tensorflow/compiler/mlir/tfrt/transforms/lhlo_gpu_to_tfrt_gpu,tensorflow/core/runtime_fallback,tensorflow/core/runtime_fallback/conversion,tensorflow/core/runtime_fallback/kernel,tensorflow/core/runtime_fallback/opdefs,tensorflow/core/runtime_fallback/runtime,tensorflow/core/runtime_fallback/util,tensorflow/core/tfrt/common,tensorflow/core/tfrt/eager,tensorflow/core/tfrt/eager/backends/cpu,tensorflow/core/tfrt/eager/backends/gpu,tensorflow/core/tfrt/eager/core_runtime,tensorflow/core/tfrt/eager/cpp_tests/core_runtime,tensorflow/core/tfrt/fallback,tensorflow/core/tfrt/gpu,tensorflow/core/tfrt/run_handler_thread_pool,tensorflow/core/tfrt/runtime,tensorflow/core/tfrt/saved_model,tensorflow/core/tfrt/saved_model/tests,tensorflow/core/tfrt/tpu,tensorflow/core/tfrt/utils
INFO: Found applicable config definition build:short_logs in file /home/edo/tensorflow/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file /home/edo/tensorflow/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:cuda in file /home/edo/tensorflow/.bazelrc: --repo_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --@local_config_cuda//:enable_cuda
INFO: Found applicable config definition build:opt in file /home/edo/tensorflow/.tf_configure.bazelrc: --copt=-Wno-sign-compare --host_copt=-Wno-sign-compare
INFO: Found applicable config definition build:linux in file /home/edo/tensorflow/.bazelrc: --copt=-w --host_copt=-w --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --define=PROTOBUF_INCLUDE_PATH=$(PREFIX)/include --cxxopt=-std=c++14 --host_cxxopt=-std=c++14 --config=dynamic_kernels --distinct_host_configuration=false --experimental_guard_against_concurrent_changes
INFO: Found applicable config definition build:dynamic_kernels in file /home/edo/tensorflow/.bazelrc: --define=dynamic_loaded_kernels=true --copt=-DAUTOLOAD_DYNAMIC_KERNELS
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/tensorflow/runtime/archive/c3e082762b7664bbc7ffd2c39e86464928e27c0c.tar.gz failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException GET returned 404 Not Found
DEBUG: /home/edo/.cache/bazel/_bazel_edo/3e7782b7c78299bfd079af691b99f92d/external/bazel_tools/tools/cpp/lib_cc_configure.bzl:118:10:
Auto-Configuration Warning: 'TMP' environment variable is not set, using 'C:\Windows\Temp' as default
DEBUG: Rule 'io_bazel_rules_docker' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1596824487 -0400"
DEBUG: Repository io_bazel_rules_docker instantiated at:
  /home/edo/tensorflow/WORKSPACE:23:14: in <toplevel>
  /home/edo/tensorflow/tensorflow/workspace0.bzl:108:34: in workspace
  /home/edo/.cache/bazel/_bazel_edo/3e7782b7c78299bfd079af691b99f92d/external/bazel_toolchains/repositories/repositories.bzl:35:23: in repositories
Repository rule git_repository defined at:
  /home/edo/.cache/bazel/_bazel_edo/3e7782b7c78299bfd079af691b99f92d/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in <toplevel>
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/google/XNNPACK/archive/113092317754c7dea47bfb3cb49c4f59c3c1fa10.zip failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException GET returned 404 Not Found
INFO: Analyzed target //tensorflow/tools/pip_package:build_pip_package (450 packages loaded, 36243 targets configured).
INFO: Found 1 target...
ERROR: /home/edo/.cache/bazel/_bazel_edo/3e7782b7c78299bfd079af691b99f92d/external/llvm-project/mlir/BUILD.bazel:3841:11: Compiling mlir/lib/Dialect/SPIRV/IR/SPIRVDialect.cpp failed: (Exit 4): crosstool_wrapper_driver_is_not_gcc failed: error executing command external/local_config_cuda/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -MD -MF bazel-out/k8-opt-exec-50AE0418/bin/external/llvm-project/mlir/_objs/SPIRVDialect/SPIRVDialect.d ... (remaining 136 argument(s) skipped)
x86_64-linux-gnu-gcc-7: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-7/README.Bugs> for instructions.
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 2909.274s, Critical Path: 230.50s
INFO: 13150 processes: 5685 internal, 7465 local.
FAILED: Build did NOT complete successfully

@Scheggetta,
Could you try bazel clean --expunge followed by bazel sync. Also kindly try to install the tensorflow v2.8 with GCC 7.3.1 compiler which is compatible. Thank you!

I'm having difficulties to find GCC 7.3.1 from PPAs for Ubuntu 20.04. As I have written in the first post, also tf v2.9.0 gives the same problem with GCC 9.4.0.
I'm also considering to try compiling tf with docker as witten here. Do you think I will get the same error?

Hi @Scheggetta,From the error traceback, it looks like issue is with compiler. Tf 2.8.0 is tested and configured with GCC 7.3.1. Tf 2.9.0 tested and configured with GCC v9.3.1. Request you to install right version of GCC  and build Tensorflow. Take a look at tested configuration here. Thank you!

Thanks for the comment. Do you have available a link or guide to install GCC 9.3.1? On my system there is GCC 9.4.0 and with sudo apt install gcc-9 I can't install the desired version.

Hi @Scheggetta,
Can you try
sudo add-apt-repository ppa:ubuntu-toolchain-r/ppa
sudo apt-get update
sudo apt-get install gcc-9.3.1 g++-9.3.1

Thank you!

Hi @gadagashwini,
I tried your suggestion but the terminal gives me this error when executing the last command:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package gcc-9.3.1
E: Couldn't find any package by glob 'gcc-9.3.1'
E: Couldn't find any package by regex 'gcc-9.3.1'
E: Unable to locate package g++-9.3.1
E: Couldn't find any package by glob 'g++-9.3.1'
E: Couldn't find any package by regex 'g++-9.3.1'

Am i doing something wrong?

Hi @Scheggetta, Try this sudo apt install gcc-9 g++-9.
I could able find gcc-9 package.

Hi @Scheggetta,From the error traceback, it looks like issue is with compiler. Tf 2.8.0 is tested and configured with GCC 7.3.1. Tf 2.9.0 tested and configured with GCC v9.3.1. Request you to install right version of GCC and build Tensorflow. Take a look at tested configuration here. Thank you!

Hi, but how you said above in a previous post, gcc 9.4.0 is not the right version. I had already tried with gcc 9.4.0 but it didn't work.
Here is my version of gcc:
edo@edo-FX504GD:~$ gcc --version
gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

As you can see, it's the same as yours.

Hi @Scheggetta, I could able build Tensorflow v2.9.1 with GCC v9.4.0 successfully. Thank you

So why do I have this crosstool_wrapper_driver_is_not_gcc error?

Hi @Scheggetta, I could able build Tensorflow v2.9.1 with GCC v9.4.0 successfully. Thank you

Ok, thanks. I am gonna try with v2.9.1.

Hi @Scheggetta, I could able build Tensorflow v2.9.1 with GCC v9.4.0 successfully. Thank you

I tried with this configuration but i get the same error:
Starting local Bazel server and connecting to it...
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=130
INFO: Reading rc options for 'build' from /home/edo/tensorflow/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /home/edo/tensorflow/.bazelrc:
  'build' options: --define framework_shared_object=true --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --enable_platform_specific_config --define=with_xla_support=true --config=short_logs --config=v2 --define=no_aws_support=true --define=no_hdfs_support=true --experimental_cc_shared_library
INFO: Reading rc options for 'build' from /home/edo/tensorflow/.tf_configure.bazelrc:
  'build' options: --action_env PYTHON_BIN_PATH=/usr/bin/python3 --action_env PYTHON_LIB_PATH=/usr/lib/python3/dist-packages --python_path=/usr/bin/python3 --action_env CUDA_TOOLKIT_PATH=/usr/local/cuda-11.2 --action_env TF_CUDA_COMPUTE_CAPABILITIES=6.1 --action_env LD_LIBRARY_PATH=/usr/local/cuda-11.2/lib64 --action_env GCC_HOST_COMPILER_PATH=/usr/bin/x86_64-linux-gnu-gcc-9 --config=cuda
INFO: Reading rc options for 'build' from /home/edo/tensorflow/.bazelrc:
  'build' options: --deleted_packages=tensorflow/compiler/mlir/tfrt,tensorflow/compiler/mlir/tfrt/benchmarks,tensorflow/compiler/mlir/tfrt/jit/python_binding,tensorflow/compiler/mlir/tfrt/jit/transforms,tensorflow/compiler/mlir/tfrt/python_tests,tensorflow/compiler/mlir/tfrt/tests,tensorflow/compiler/mlir/tfrt/tests/ir,tensorflow/compiler/mlir/tfrt/tests/analysis,tensorflow/compiler/mlir/tfrt/tests/jit,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_tfrt,tensorflow/compiler/mlir/tfrt/tests/tf_to_corert,tensorflow/compiler/mlir/tfrt/tests/tf_to_tfrt_data,tensorflow/compiler/mlir/tfrt/tests/saved_model,tensorflow/compiler/mlir/tfrt/transforms/lhlo_gpu_to_tfrt_gpu,tensorflow/core/runtime_fallback,tensorflow/core/runtime_fallback/conversion,tensorflow/core/runtime_fallback/kernel,tensorflow/core/runtime_fallback/opdefs,tensorflow/core/runtime_fallback/runtime,tensorflow/core/runtime_fallback/util,tensorflow/core/tfrt/common,tensorflow/core/tfrt/eager,tensorflow/core/tfrt/eager/backends/cpu,tensorflow/core/tfrt/eager/backends/gpu,tensorflow/core/tfrt/eager/core_runtime,tensorflow/core/tfrt/eager/cpp_tests/core_runtime,tensorflow/core/tfrt/gpu,tensorflow/core/tfrt/run_handler_thread_pool,tensorflow/core/tfrt/runtime,tensorflow/core/tfrt/saved_model,tensorflow/core/tfrt/graph_executor,tensorflow/core/tfrt/saved_model/tests,tensorflow/core/tfrt/tpu,tensorflow/core/tfrt/utils
INFO: Found applicable config definition build:short_logs in file /home/edo/tensorflow/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file /home/edo/tensorflow/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:cuda in file /home/edo/tensorflow/.bazelrc: --repo_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --@local_config_cuda//:enable_cuda
INFO: Found applicable config definition build:opt in file /home/edo/tensorflow/.tf_configure.bazelrc: --copt=-Wno-sign-compare --host_copt=-Wno-sign-compare
INFO: Found applicable config definition build:linux in file /home/edo/tensorflow/.bazelrc: --copt=-w --host_copt=-w --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --define=PROTOBUF_INCLUDE_PATH=$(PREFIX)/include --cxxopt=-std=c++14 --host_cxxopt=-std=c++14 --config=dynamic_kernels --distinct_host_configuration=false --experimental_guard_against_concurrent_changes
INFO: Found applicable config definition build:dynamic_kernels in file /home/edo/tensorflow/.bazelrc: --define=dynamic_loaded_kernels=true --copt=-DAUTOLOAD_DYNAMIC_KERNELS
DEBUG: /home/edo/.cache/bazel/_bazel_edo/3e7782b7c78299bfd079af691b99f92d/external/bazel_tools/tools/cpp/lib_cc_configure.bzl:118:10:
Auto-Configuration Warning: 'TMP' environment variable is not set, using 'C:\Windows\Temp' as default
DEBUG: Rule 'io_bazel_rules_docker' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1596824487 -0400"
DEBUG: Repository io_bazel_rules_docker instantiated at:
  /home/edo/tensorflow/WORKSPACE:23:14: in <toplevel>
  /home/edo/tensorflow/tensorflow/workspace0.bzl:107:34: in workspace
  /home/edo/.cache/bazel/_bazel_edo/3e7782b7c78299bfd079af691b99f92d/external/bazel_toolchains/repositories/repositories.bzl:35:23: in repositories
Repository rule git_repository defined at:
  /home/edo/.cache/bazel/_bazel_edo/3e7782b7c78299bfd079af691b99f92d/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in <toplevel>
INFO: Analyzed target //tensorflow/tools/pip_package:build_pip_package (491 packages loaded, 35351 targets configured).
INFO: Found 1 target...
ERROR: /home/edo/tensorflow/tensorflow/compiler/mlir/tensorflow/BUILD:433:15: Compiling tensorflow/compiler/mlir/tensorflow/ir/tf_ops_a_m.cc failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command external/local_config_cuda/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -MD -MF bazel-out/k8-opt-exec-50AE0418/bin/tensorflow/compiler/mlir/tensorflow/_objs/tensorflow_ops_a_m/tf_ops_a_m.d ... (remaining 235 arguments skipped)
x86_64-linux-gnu-gcc-9: fatal error: Killed signal terminated program cc1plus
compilation terminated.
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 2761.049s, Critical Path: 258.48s
INFO: 11603 processes: 5425 internal, 6178 local.
FAILED: Build did NOT complete successfully

Hi,
since I gave up in making the build work out with GPU support, I decided to stick with CPU only. However, when I try the same commands to compile tf, I get a different error:
Starting local Bazel server and connecting to it...
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=130
INFO: Reading rc options for 'build' from /home/edo/tensorflow/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /home/edo/tensorflow/.bazelrc:
  'build' options: --define framework_shared_object=true --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --enable_platform_specific_config --define=with_xla_support=true --config=short_logs --config=v2 --define=no_aws_support=true --define=no_hdfs_support=true --experimental_cc_shared_library
INFO: Reading rc options for 'build' from /home/edo/tensorflow/.tf_configure.bazelrc:
  'build' options: --action_env PYTHON_BIN_PATH=/usr/bin/python3 --action_env PYTHON_LIB_PATH=/usr/lib/python3/dist-packages --python_path=/usr/bin/python3
INFO: Reading rc options for 'build' from /home/edo/tensorflow/.bazelrc:
  'build' options: --deleted_packages=tensorflow/compiler/mlir/tfrt,tensorflow/compiler/mlir/tfrt/benchmarks,tensorflow/compiler/mlir/tfrt/jit/python_binding,tensorflow/compiler/mlir/tfrt/jit/transforms,tensorflow/compiler/mlir/tfrt/python_tests,tensorflow/compiler/mlir/tfrt/tests,tensorflow/compiler/mlir/tfrt/tests/ir,tensorflow/compiler/mlir/tfrt/tests/analysis,tensorflow/compiler/mlir/tfrt/tests/jit,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_tfrt,tensorflow/compiler/mlir/tfrt/tests/tf_to_corert,tensorflow/compiler/mlir/tfrt/tests/tf_to_tfrt_data,tensorflow/compiler/mlir/tfrt/tests/saved_model,tensorflow/compiler/mlir/tfrt/transforms/lhlo_gpu_to_tfrt_gpu,tensorflow/core/runtime_fallback,tensorflow/core/runtime_fallback/conversion,tensorflow/core/runtime_fallback/kernel,tensorflow/core/runtime_fallback/opdefs,tensorflow/core/runtime_fallback/runtime,tensorflow/core/runtime_fallback/util,tensorflow/core/tfrt/common,tensorflow/core/tfrt/eager,tensorflow/core/tfrt/eager/backends/cpu,tensorflow/core/tfrt/eager/backends/gpu,tensorflow/core/tfrt/eager/core_runtime,tensorflow/core/tfrt/eager/cpp_tests/core_runtime,tensorflow/core/tfrt/gpu,tensorflow/core/tfrt/run_handler_thread_pool,tensorflow/core/tfrt/runtime,tensorflow/core/tfrt/saved_model,tensorflow/core/tfrt/graph_executor,tensorflow/core/tfrt/saved_model/tests,tensorflow/core/tfrt/tpu,tensorflow/core/tfrt/utils
INFO: Found applicable config definition build:short_logs in file /home/edo/tensorflow/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file /home/edo/tensorflow/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:opt in file /home/edo/tensorflow/.tf_configure.bazelrc: --copt=-Wno-sign-compare --host_copt=-Wno-sign-compare
INFO: Found applicable config definition build:linux in file /home/edo/tensorflow/.bazelrc: --copt=-w --host_copt=-w --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --define=PROTOBUF_INCLUDE_PATH=$(PREFIX)/include --cxxopt=-std=c++14 --host_cxxopt=-std=c++14 --config=dynamic_kernels --distinct_host_configuration=false --experimental_guard_against_concurrent_changes
INFO: Found applicable config definition build:dynamic_kernels in file /home/edo/tensorflow/.bazelrc: --define=dynamic_loaded_kernels=true --copt=-DAUTOLOAD_DYNAMIC_KERNELS
DEBUG: Rule 'io_bazel_rules_docker' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1596824487 -0400"
DEBUG: Repository io_bazel_rules_docker instantiated at:
  /home/edo/tensorflow/WORKSPACE:23:14: in <toplevel>
  /home/edo/tensorflow/tensorflow/workspace0.bzl:107:34: in workspace
  /home/edo/.cache/bazel/_bazel_edo/3e7782b7c78299bfd079af691b99f92d/external/bazel_toolchains/repositories/repositories.bzl:35:23: in repositories
Repository rule git_repository defined at:
  /home/edo/.cache/bazel/_bazel_edo/3e7782b7c78299bfd079af691b99f92d/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in <toplevel>
INFO: Analyzed target //tensorflow/tools/pip_package:build_pip_package (481 packages loaded, 28758 targets configured).
INFO: Found 1 target...
ERROR: /home/edo/tensorflow/tensorflow/core/kernels/linalg/BUILD:207:18: Compiling tensorflow/core/kernels/linalg/matrix_square_root_op.cc failed: (Exit 1): gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 266 arguments skipped)
gcc: fatal error: Killed signal terminated program cc1plus
compilation terminated.
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /home/edo/tensorflow/tensorflow/lite/python/BUILD:68:10 Middleman _middlemen/tensorflow_Slite_Spython_Stflite_Uconvert-runfiles failed: (Exit 1): gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 266 arguments skipped)
INFO: Elapsed time: 4384.865s, Critical Path: 562.26s
INFO: 6396 processes: 911 internal, 5485 local.
FAILED: Build did NOT complete successfully

Specifically, gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector ...

Hi @Scheggetta, For the original issue, could you try the workarounds mentioned on similar thread https://github.com/tensorflow/tensorflow/issues/44692#issuecomment-917543931. Thank you!

Hi @Scheggetta, For the original issue, could you try the workarounds mentioned on similar thread #44692 (comment). Thank you!

Ok @gadagashwini, thanks for the tip. I am going to try it soon.

Hi @Scheggetta ,
Could you please spare some time to close the issue if got resolved.Please feel free to comeback if the issue still persists so that we can try for a workaround.
Thankyou!


Lutron Caséta Lights missing

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version): 53
Python release (python3 --version):
Component/platform: Lutron Caséta
Description of problem:
All the lights are missing from Home assistant when I upgraded. The only the that is showing are the scenes I created in lutron app.
Expected:
Lutron lights to be shown.
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:

Try restarting the OS instead of just restarting HASS. I'm about to submit a bug due to Lutron breaking after restarting HASS.

This isn't a configuration.yaml issue. Getting Python errors. This has been broken for over a month - I believe with .55 update. I had everything working perfectly beforehand. No Configuration.yaml changes to the component were done on my end. Can we please fix this? This component is ESSENTIAL to my automations!

There's very little info reported to go on right now. Please post the part of the log with the errors.

https://pastebin.com/YzSELX7c

This issue is a consequence of an API change at lutron. See https://github.com/gurumitts/pylutron-caseta/issues/14.
https://github.com/home-assistant/home-assistant/pull/10286 will fix it.


Refactor merge pipeline

Refactored merge pipelines to be independent of indexing pipelines
Closes https://github.com/quickwit-oss/quickwit/issues/1803

Converting to draft to address @evanxg852000 's point

@fmassot I still need to discuss with Paul. He was busy on fixing  the SplitStore

@evanxg852000 @fmassot  yes it will definitely happen this week. I am slowly flushing my never ending task list.

Closing, this PR became https://github.com/quickwit-oss/quickwit/pull/2178


Re-enable Mac support on CI system

Mac support has been removed from the CI system because C++ code using the PyTorch 1.5.0 C++ API requires building on later Mac images and XCode toolchains than the Azure Pipeline permissions currently allow
I've asked @migueldeicaza for the necessary permissions
Support was removed here:
https://github.com/xamarin/TorchSharp/pull/133/commits/8bb6e939d9475de06240b39e56f945d15ed7770a

This was addressed a while ago.


Extension not working with x64 agent on vsts

Facing this:
A supported task execution handler was not found. The task does not carry an implementation that is compatible with your current operating system 'Windows(X64)'. Contact the task author for more details.

Hi @AhmadHassanSahi,
Thanks for reporting the issue. I don't think the issue is the operating system as i'm running tests on linux, macos and windows but i found that the minimum agent version was incorrectly set on the new version 6 of the task (fix incoming) due to an issue on some Microsoft documentation.
Could you provide me some more information on your environment:

what version of the agent are you running on?
what is the task version you are trying to?

@qetza

Agent Below

I am running Replace Token task 6

Hi @AhmadHassanSahi,
The issue is that the agent 2.181.2 doesn't support node16 execution handler which is the only one supported with the version 6 of the task.
I've already pushed a PR to fix the minimum agent version of the version 6 to 2.206.1.
In your case i see 2 options:

upgrade your agent to at least version 2.206.1
use version 5 of the task which has a minimum agent version of 2.144.0

@qetza  Thankyou for your quick response. I really appreciate it. I have tried with Task Version 5. its running successfully.


Week 1 hacks

Custom homepage
Vocab Page
Python Quiz - extra credit
Bash Notebook
Notes for school - extra credit

I would give Ryan a 3.0!!!. Everything is up to standard or better with extra credit slotted in different areas well done.!!

I would give you a 3.0, all the effort and dedication was put into all sections of work. It met all and more expectations, great job! - Chris A.

I would give Ryan a 3 out of 3 because Ryan met all the requirements for this assignment and he went above and beyond with his custom homepage. Everything is organized and up and running.


Android telegram client scroll down after callback

Hi! I have some problems with android telegram client. If I send a message with a link and callback button for this message, after press callback button client app force scroll down to the end of bot conversation.
This reproduce only in android client and only if a message has a link and callback button.
Maybe anyone one knows what I can do with this?

I think that is a client problem, so you can't do nothing.
But for confirmation wait other responses ;)