Changing Start or End icon URL breaks mouseout Leaflet event

Hello,
Thank you for your plugin, I use it (and like it) a lot.
I recently had an issue with the mouseout leaflet event and changing startIconUrl or endIconUrl.
In the code below, sometimes (particulary if you move the mouse fast), the mouseout event is not triggered.
If I remove the lines concerning the icons, the mouseout event fires normally.
gpx.on('mouseover', function (e) {
    var layer = e.target;
    layer.options.marker_options.startIconUrl = 'myHoverIconStartUrl';
    layer.options.marker_options.endIconUrl = 'myHoverIconEndUrl';
    layer.reload();
});
gpx.on('mouseout', function (e) {
    console.log('Mouse out !')
    var layer = e.target;
    layer.options.marker_options.startIconUrl = '';
    layer.options.marker_options.endIconUrl = '';
    /* this line below causes the issue */
    layer.reload();
});

Displaying start and end icons on hover is probably a common thing to do with leaflet-gpx.
Maybe there is something I simply do wrong, feel free to add the "question" label in this case.
EDIT : Apparently, it is the layer.reload() that causes the problem. It causes some flickering on reloading and triggers mouseover and mouseout multiple times. So the question would now be : Is it possible to change startIconUrl and endIconUrl without reloading the layer ?
Thank you for your help

Hmm, yeah I definitely would not use layer.reload() to achieve this. L.GPX will fire up events for each marker it adds, including the start and end markers; see:

https://github.com/mpetazzoni/leaflet-gpx/blob/main/gpx.js#L543
https://github.com/mpetazzoni/leaflet-gpx/blob/main/gpx.js#L553

I recommend you grab a reference to the L.Marker objects from those events, and show/hide those instead as necessary.


Add GHF data to fetch module.

Description of the desired feature:

Include the below list of GHF datasets in the fetch module.
Losing et al. 2021
Stal et al. 2020
Burton-Johnson 2020
Shen et al. 2020
An et al. 2015
Martos et al. 2017
Are you willing to help implement and maintain this feature?

Added the following in commit  3dbb5724198d7b6569ecfee4947f54170ab32378:
Losing et al. 2021
Stal et al. 2020
Burton-Johnson 2020
Couldn't get download link to work for Shen et al. 2020.


Transfer files to Googledrive created double folders

Hi,
I transferred data to Googledrive and rclone created the folders that where already on Googledrive a second time with the same name?
Whats wrong there?
And can I move only files and keep folders?
Thanks,
Hyper

I think this is probably #28 - sometimes rclone manages to create duplicates :-(  This has got a lot better over the years but still isn't perfectly fixed.
You can use the rclone dedupe command to help manage the problem, or remove duplicates by hand - rclone doesn't mind.

I just wonder, if it dedupes the folder won't it skip the files in the folder then?
I remember having a duplicate file warning and I did not have dedupe enabled.
Beside that, there was also no duplicate file. Strange thing :)

Just found out google-api allows duplicates, as the name is just an attribute.
One the one side this is really nice, but in this case it sucks :(

dedupe will help you remove the duplicate files.
The duplicate file names are rather annoying but don't happen too often.

Can you post the comand line you used for the transfer too please?

Hello, I also end up with a lot of duplicates. I have discovered that this happen when building file list fails and rclone tray to upload a file that is already on drive (instead of update it).
Increasing  retries have reduced duplicates.
Is it possible to not sync if there are errors when building the list?  Maybe a command  flag  for this option.
Thank you
Roberto

Have you tried the latest release? It will abort if the listing fails and it double check the file doesn't exist before uploading so I hope it might help your issues.

I was using rclone v1.29.  Will download and try 1.30
Thank you

I'm going to close this as we have #28 open to track this issue


Update go samples

Description

Update and Add more samples of using wallet-core functionalities in Go.

Bitcoin, Ethereum, Tron wallet creation.
Btc, Eth transaction creation.
Add sample for some other methods of TWCoinType, TWCoinTypeConfiguration, TWHDWallet, TWMnemonic, ...
Restructure and move the codes that talk to wallet-core to a separate package and make the main file cleaner.

Fixes #1841
Testing instructions

Like before, described in readme.
Types of changes

Bug fix (non-breaking change which fixes an issue)

New feature (non-breaking change which adds functionality)

Checklist

[x] Prefix PR title with [WIP] if necessary.
[x] Add tests to cover changes as needed.
[x] Update documentation as needed.
[x] I have read the guidelines for adding a new blockchain
[x] If there is a related Issue, mention it in the description (e.g. Fixes #<issue_number> ).

@hewigovens

Nice work!, can we reuse proto files in src/proto and generate Bitcoin.pb.go and other files in a script?

Thanks, I think yes but not that easy, it would better if we add go_package='...' to src/proto files. cos protoc-gen-go can't generate easily without that.
I put the command which I compile proto files with inside compile.sh.

@apm-dev I think we can copy the protos to from src to go sample folder in compile.sh, just don't check in duplicate proto file and pb.go

@apm-dev I think we can copy the protos to from src to go sample folder in compile.sh, just don't check in duplicate proto file and pb.go

Could you explain in more detail, please?
What should I do now?

writing bash script inside compile.sh to copy .proto files from src/proto and then compile them inside go-sample?
or updating the tools/generate-files bash script to generate also go protobuf files?

@apm-dev Yes, "writing bash script inside compile.sh to copy .proto files from src/proto and then compile them inside go-sample", I can do it later for you if you prefer

It's OK, I'll do that, Thanks.

@hewigovens Hi, compile.sh completed, now we can run ./compile.sh and all the required proto files in src/proto will be generated inside protos folder.

Yes, I delete others and put them just for example.
I will add an step about generating proto files in readme.

heads up @apm-dev , I've created a PR #1864 to add building of Go sample app to CI, plus do some fixes to the Go sample app.  I also updated the Dockerfile with Go to be able to build sample app inside docker.
Please have a look, I think the fixes you already did in this PR as well.

heads up @apm-dev , I've created a PR #1864 to add building of Go sample app to CI, plus do some fixes to the Go sample app. I also updated the Dockerfile with Go to be able to build sample app inside docker. Please have a look, I think the fixes you already did in this PR as well.

Hi @catenocrypt , I saw that and I think we worked on two different contexts, this PR is about adding some new samples of using TW by golang with some improvements, and #1864 is about fixing some imports and modifying some CI and docker parts.
I think these two PRs can merge together.

Hi @catenocrypt , I saw that and I think we worked on two different contexts, this PR is about adding some new samples of using TW by golang with some improvements, and #1864 is about fixing some imports and modifying some CI and docker parts. I think these two PRs can merge together.

There were some overlapping changes, like TWMnemonic include or -lc++, non-trivial merge, but I have resolved them in #1864 (as this PR has been merged in the meantime)

Hi @catenocrypt , I saw that and I think we worked on two different contexts, this PR is about adding some new samples of using TW by golang with some improvements, and #1864 is about fixing some imports and modifying some CI and docker parts. I think these two PRs can merge together.

There were some overlapping changes, like TWMnemonic include or -lc++, non-trivial merge, but I have resolved them in #1864 (as this PR has been merged in the meantime)

@apm-dev


“Paste” and “paste special” in keyboard accesory view layout

Feature description
It'd be awesome if we had the possibility to have “paste” or “paste special” buttons (currently in the three-dot-menu at the top right) in the row above the keyboard, either to be configured by the user her-/himself, or as a default option.

Hello @necrevistonnezr 👋
Many thanks for your feedback 🙏
If I add two new tokens to Keyboard Accessory Vies Customisation, would it be OK for you?
For example I would implement these tokens :

{PASTE}
{PASTE_PASSWORD}

So I'm planning it 😉

Will be released in a few hours on the beta release.
I will come back to you shortly

Thank you so much @necrevistonnezr for your support about my work 🙏


Screen reader does not read prompt in "No Profiling Target" window

Repro Steps:

Open a solution.
Open the Python Profiling Window
Create a new performance Session
"Start Profiling" will show this dialog

Screen reader reads the title and then jumps to the buttons without narrating the prompt. This is likely a MAS violation.

You need to use CAPS LOCK+LEFT ARROW or CAPS LOCK + RIGHT ARROW to make it read the text.


[WIP] docs: deploy

Codecov Report

Merging #311 (d59b2c1) into docs-rework (e0b38ee) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           docs-rework     #311   +/-   ##
============================================
  Coverage        77.80%   77.80%
============================================
  Files               52       52
  Lines             4673     4673
  Branches           552      553    +1
============================================
  Hits              3636     3636
  Misses            1032     1032
  Partials             5        5

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e0b38ee...d59b2c1. Read the comment docs.


Code release

Hello! @ZhengdiYu
Do you have any plans to release the code?

Hello! @ZhengdiYu
Do you have any plans to release the code?

We will release the code soon recently, Mr Niruo Shan.


Bugfix: Log consumers are now called with exactly one complete log line

Fixes #5843: log consumers are now called with exactly one complete log line
Motivation
Docker logs provide a stream, the frames provided are not necessarily split by newline characters. So it might happen that a frame contains partial log lines.
Changes

Line splitting, partial log buffering and line merging independently of the stream type (RAW, STDOUT, STDERR)
OutputFrame does consistently not contain newline characters (independent of TTY)
ToStringConsumer now adds newlines
Slf4jLogConsumer does not need to remove any newlines

Also fixes #4110, #455

Can someone approve the missing workflows? The code should now be ready.

Sorry to ask again, but now no more checks/tests should fail (hopefully 😁).

I updated the branch on GitHub and now the workflows need approval again.
I don't want to put pressure on you but it would be nice to get a rough estimate of when you plan to incorporate this fix, just that we know if we should add another workaround on our side.

Any updates?

@SgtSilvio thanks for your contribution! I will be taking a look at it next week. Sorry for the delay.

Ping @eddumelendez, just a friendly reminder that we are eagerly waiting on this fix. :slightly_smiling_face:

Can we help in any way to get this merged? I will also take care of updating the PR.
I always thought you were too busy so I did not ping you unnecessarily, but other tickets like https://github.com/testcontainers/testcontainers-java/pull/6239 got merged so what can I do to move this PR forward?
@kiview @eddumelendez

Hi @SgtSilvio, sorry for not yet reviewing and merging. #6239 was a trivial change with minimal effect radius, that's why this got easily merged, while PRs that touch the core of the library sometimes tend to take longer to get reviewed. From the change in CosmosDBEmulatorContainer we can assume this is possibly a breaking change for our users as well, so we will need a bit of time to look into it and prioritize it accordingly.
I will discuss with @eddumelendez when we will find the time to look into this, sorry again and thanks for your patience.

Thanks @kiview, it is perfectly valid feedback if you have any concerns that the changes might be too breaking. Although I rather see this as a broken behavior that was never reliable, and fixing a broken behavior is imho not a breaking change, I can understand if you see this differently.
If you like, I could take another look to restore the old behavior as much as possible and introduce new APIs for the fix instead, for example a method getBytesWithoutNewLine.
My comment was not about putting any stress on you, just about getting any feedback from you how we can help you to get this done.

Any updates? Should I invest more time into it? Can you give me some feedback?

Sorry for the delay on this one. We are doing our best working on new features, triaging new issues/PRs meanwhile taking a look at the backlog.
@SgtSilvio I just noticed there are some conflicts and if you can solve them, it would be appreciated. Also, regarding to We are heavily affected by this bug because of failing/flaky tests. can you tell us more about when are your having this issue? Just asking to get more context.

Hi all,
Is there any updates on this issue?
Just I suspect it affects integration with Podman significantly.
At least, LogMessageWaitStrategy seems isn't working correctly for PostgreSQLContainer on Podman - I've been  forced override it to HostPortWaitStrategy as a workaround.

I just noticed there are some conflicts and if you can solve them, it would be appreciated.

Thanks for your update. I now rebased the branch.

Also, regarding to We are heavily affected by this bug because of failing/flaky tests. can you tell us more about when are your having this issue? Just asking to get more context.

I described our problems in the linked issue https://github.com/testcontainers/testcontainers-java/issues/5843:
The issue happens especially when using a WaitAllStrategy with more LogMessageWaitStrategy.
The second log wait strategy only attaches to the log after the first finished, and then of course gets a lot more data at once, so that log frames may contain multiple and partial log lines.

If you like, I could take another look to restore the old behavior as much as possible and introduce new APIs for the fix instead, for example a method getBytesWithoutNewLine.

I now restored the old behavior of the methods OutputFrame.getBytes and OutputFrame.getUtf8String, and added a new method OutputFrame.getUtf8StringWithoutLineEnding.
@kiview This should now resolve all your concerns about this being a breaking change.

From the change in CosmosDBEmulatorContainer we can assume this is possibly a breaking change for our users as well, so we will need a bit of time to look into it and prioritize it accordingly.

Even the change to CosmosDBEmulatorContainer is now reverted. Tests should pass (though I did not run them yet).

Now all tests should pass

Can someone approve the workflows?

Is anything else required from my side? For example, do you require more comments on the code? Or should I just wait for your review?

Hi team,
Are there any plans about release this fix?

Thanks for your contribution, @SgtSilvio ! and sorry for the long wait on this one. This is finally merged in main branch and will be part of the next release.

@eddumelendez Thanks a lot for this, appreciated! :pray: Now, if we could just get #3018 merged into the next release as well, I would be completely happy... :joy: :wink:

@eddumelendez I'm sorry for disturbance but could you please provide some info. about the nearest release date?
We are waiting this fix impatiently regarding of the Podman usage.

@alexandrklimov The fix is included in https://github.com/testcontainers/testcontainers-java/releases/tag/1.18.0, released last week. :tada:
However, what I don't understand is why we're now seeing \r\n (CR+LF) line endings when calling org.testcontainers.containers.ContainerState#getLogs() on a Tomcat-based container. :thinking: Both the container and the host are Linux-based in this case. String[] logLines = logsString.split( "\n" ), which is why only the \r is present in the strings in this array.

@perlun looked again at my changes, and this must be caused by something else (can't find a way how the code would add a \r).

Is this happening from within a Windows process (JVM running on Windows)?

@kiview Nope, interestingly not. Both the container and the host are Linux-based in this case.
I debugged this a bit and concluded that it comes out as CR+LF all the way here, in org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder#executeAndStream:

And given the fact that HTTP uses CR+LF (not LF only), this is perhaps not so strange after all. :thinking: The data is just propagated from the DockerHttpClient.Response all the way, and this byte buffer contains CR+LF => log lines include CR+LF.
Here's what I think is an approximate description of the history re. this:

The previous version we were using (1.15.1) used LF only here.
I fixed a bug in https://github.com/testcontainers/testcontainers-java/pull/3752 (included in 1.15.2).
1.15.2 had another bug which prevented us from upgrading: https://github.com/testcontainers/testcontainers-java/issues/4110
That bug was in turn fixed by @SgtSilvio (thanks!) in this PR (https://github.com/testcontainers/testcontainers-java/pull/5854).

In other words, this change is very likely not "intentional" but a side effect of how the handling of the log output has changed.

One (seemingly "nasty") way to deal with it would be to let this method silently discard all CR characters. It would probably be a quite easy and reasonable way to fix this, which would make the log lines be more natural for Linux users. (TODO: should we detect Windows and still return CR+LF log lines in that case? :thinking:)
https://github.com/testcontainers/testcontainers-java/blob/2525748a3aca939387040ae5f2cfedbc8469caee/core/src/main/java/org/testcontainers/containers/output/FrameConsumerResultCallback.java#L98-L126

And given the fact that HTTP uses CR+LF

You probably mean that HTTP uses crlf to separate its headers. But the body contains arbitrary bytes as sent by the sender.

Seems to the behavior of tty: https://stackoverflow.com/questions/55034214/why-do-docker-run-t-outputs-include-r-in-the-command-output
So I would say this is expected behavior. A option to normalize line endings to only LF could be added, but please don't change the log output by default.

I'll try that and see, this is obviously a much simpler and better fix than doing any changes in Testcontainers to begin with.

Verified; this fixes the problem with CR+LF. :heavy_check_mark:
I'll let you know in case we see any more (logging/line ending-related) failures, but hopefully this should be the end of it. :+1:


Manual feed refresh button

nice. will test and merge tomorrow hopefully

thanks. I haven't actually tested this myself, it just calls pullUserStatuses()

tested now, seems to work

only concern is refresh spamming, i can add button cooldown if you want

oh hey yeah a cooldown would be great. i know its easy to get around it, but it would do something to stop some people spamming it :)

Okay, cooldown added! Sorry If the code's a bit iffy. first time using js / typescript / whatever this is. As such feedback would be appreciated if you have the time

uhhh i didnt mean to delete those commits is there any way to get them back


Update the color when the luminosity (or radius) changes

-Change it to the appropriate star color if the luminosity is greater than 0
-If luminosity is zero, change the color back to a regular body color
Fix an error I had made in the temperature calculation
Update Body color tests to reflect equation change

[Current coverage][cc-pull] is 100%

Merging [#96][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master        #96   diff @@
==========================================
  Files             6          6
  Lines           413        417     +4
  Methods          75         75
  Messages          0          0
  Branches         85         87     +2
==========================================
+ Hits            413        417     +4
  Misses            0          0
  Partials          0          0

Powered by Codecov. Last updated by [703f317...210d7be][cc-compare]
[cc-base-branch]: https://codecov.io/gh/orbitable/engine/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/orbitable/engine/compare/703f317f93668b3b5f9aa8369afd26108fe95338...210d7be14e2dc3bcdf501a8372b333d59ba92e79
[cc-pull]: https://codecov.io/gh/orbitable/engine/pull/96?src=pr


community: Invalidate sqlalchemy connection

Description:
connection.close() restores the DBAPI connection back to the connection-holding pool but does not actually close it.connection.invalidate() closes the underlying DBAPI connection. It will prevent exceptions such as OperationalError.

Issue: Fixed #15687

closing due to failed checks


change background color of dropdown elements.

Hi. i have a table like this one:

And i want to set a diferent background color for each flag in the dropdowns of the flag columns.  For example, to the "T" flag,  a blue background, a green for "V", etc.
I tried to follow the following example https://bossanova.uk/jexcel/v2/examples/table-styling but it use Jquery and have some bugs/error that i was unable to fix.
i tried to follow the example and got the following error:

Can someone show me a sample on how to change the background color of the dropdown items please ( without jquery) ? Thanks a lot !
( by the way, stackoverflow limits questions to 3 if you dont have reputation and block the user from doing more questions, so this is the only place to get an answer).

You should upgrade to v4 (CE) or v7 (Pro). But you can customize the dropdown classes only using CSS. This error is because you are not initiating the table properly, there are tons of examples on how to do that.
updateSettings has been replaced by updateTable on v3+

Hi,
If you use JExcel Pro, you have a plugin for that (conditional style like Excel) : https://repo.gbonnaire.fr/product/jexcel-plugin-conditionalstyle
But for JExcel CE, you can make style like this :
var myTableElement = document.getElementById('myTable');

var myTable = jexcel(myTableElement, {
      ... your setting ...
      updateTable: function (instance, cell, col, row, value, label, cellName) {
           if(col==1) { // Col Flag, first col = 0
               if(value == "T") { // Value of cell
                    // here cell is an elementHTML
                    cell.style.backgroundColor = "orange"; // color in hexa or name
               } else {
                   cell.style.backgroundColor = "#FFF"; // Blank
               }
          }
      },
});

// example out of jexcel options
myTable.setStyle('B2', 'background-color', 'orange'); // For set style specifics on cell


Mention GeoMakie.jl in Awesome-Geospatial

Hello,
Maybe GeoMakie should be mentioned in
https://github.com/sacridini/Awesome-Geospatial#julia
Kind regards

Would be good, yes. Feel free to make a PR there. I see most of the list is from 3 years ago, could use an update. Some should be removed and some added.

https://github.com/sacridini/Awesome-Geospatial/pull/41 merged


CD Tab Chart

Prepare drafts of the CD Tab chart for DR Sami to approve.

Four different designs of chart have been placed at /en/cdchart. Just need to give Sami access, and let him choose which one he wants. Will close for now.


The exclude options are wrong way round. Remove ANDs

https://github.com/FoodStandardsAgency/lit-fetch/blob/b58af2232ccf4757b86742dcd867af9067584b85/R/mod_filter.R#L37
If I want to exclude any title with X or Y in then I do an internal OR and it doesn't remove them. Simplify this don't need AND just have list of ORs or one box

linked to #36
just have a single box separating terms with OR


docs: Add Inferable as an integration

Hey @marcklingen - sending this as promised :) Would appreciate a review, and happy to reword any part of it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

made some minor edits, sorry for the wait here!


wrappedPromise losing context?

Hi,
Just guessing, but it looks like your wrapping global.Promise fails to carry context at some point.
I'm using mssql and sequelize packages and mssql's request#execute method (which returns a promise) clears the transaction in sequelize's CLS namespace.
here is the code sample: https://github.com/sequelize/sequelize/issues/3434

Performed a new test, and covered that it's not related.


 Called 0 times."

    def assert_called_once_with(_mock_self, *args, **kwargs):
        """assert that the mock was called exactly once and with the specified
            arguments."""
        self = _mock_self
        if not self.call_count == 1:
            msg = ("Expected '%s' to be called once. Called %s times." %
                   (self._mock_name or 'mock', self.call_count))
>           raise AssertionError(msg)
E           AssertionError: Expected 'secure_channel' to be called once. Called 0 times.

.nox/unit-grpc-gcp-3-7/lib/python3.7/site-packages/mock/mock.py:947: AssertionError

And a side note:  there is really no purpose in running with grpcio-gcp on all supported Pythons:  we should trim it back to just 2.7 and 3.6.

Looks like we need a new release of api_core:  the gprc_gcp stuff added in #5533 is not in a release.  @crwilcox Can you do that release?

PR #5865 solves this issue by using development installs of the local packages during nox unit / system test runs.


Native support for the image preview

Currently we need chafa to preview image files, but #186 enables it out of the box, using viuer.
The problem is, that with viuer the preview of gif animation could take a long time, which is really frustrating. This leads to not supporting high-res preview in both iTerm and kitty protocol.
Reading gif as Frames via image crate would be a solution.

viuer's sixel feature does not work on runtime because sixel-sys doesn't provide its own compiled libsixel library: cf. https://github.com/AdnoC/sixel-sys/issues/3
This library seems unmaintained for years.

feature-viuer branch can show the image preview by blocks in any terminal, and if your terminal supports iTerm protocol, even the high-res one. But Many terminals are with libsixel, which is not easily used in Rust code because of the issue above.
I think many user wants the high-res preview if available, so this branch is not completed. I leave this issue open to show the process.
In the current version chafa beautifully supports the image preview well in felix.

Refactored the image preview flow: Now it is supported by default, and if your terminal implements iTerm protocol (i.e. Wezterm) it can show the high-res image.
Furthermore, if your terminal supports sixel or kitty protocol, by installing chafa you have the high-res preview.

Is there any chance that this could work using Tmux & Kitty?
Using Kitty as-is does work perfectly, I get images in high resolution using Chafa.
Using Tmux within Kitty does not work. I'm not sure to understand the intricacies of how does Chafa or those so-called Kitten for displaying images work, but I guess Tmux does something that prevents this behavior.
Do you think that this could be added to Felix? If not, can you explain ways to make it work or alternatives?
Thank you!

Just chiming in to note that tmux passthrough should indeed be working on Chafa master. It will be in the 1.14.0 release in a couple of days. Cheers!

Refactored the image preview flow: Now in feature-viuer branch it is supported by default, and if your terminal implements iTerm protocol (i.e. Wezterm) it can show the high-res image. Furthermore, if your terminal supports sixel or kitty protocol, by installing chafa you have the high-res preview.

I'm on Windows. When I try to build this branch to get iterm previews I get the error:
user@host MINGW64 ~/repos/felix (feature-viuer)
$ cargo install --locked --path .
  Installing felix v2.3.0 (C:\Users\user\repos\felix)
    Updating git repository `https://github.com/kyoheiu/syntect`
error: failed to get `syntect` as a dependency of package `felix v2.3.0 (C:\Users\user\repos\felix)`

Caused by:
  failed to load source for dependency `syntect`

Caused by:
  Unable to update https://github.com/kyoheiu/syntect#b5212417

Caused by:
  failed to clone into: C:\Users\user\.cargo\git\db\syntect-efeee53e6df11ed1

Caused by:
  failed to authenticate when downloading repository

  * attempted to find username/password via git's `credential.helper` support, but failed

  if the git CLI succeeds then `net.git-fetch-with-cli` may help here
  https://doc.rust-lang.org/cargo/reference/config.html#netgit-fetch-with-cli

Caused by:
  failed to acquire username/password from local configuration

I'm able to build the main branch fine however. I'm using Wezterm and have chafa but the image previews don't display for some reason. So, I was looking to use iterm.


Fix row order when decoding interlaced gif

Currently, Avalonia.GIF doesn't appear to be decoding interlaced GIFs correctly. It looks like the original code does the math correctly, but then incorrectly re-uses the same row index for both the raw GIF data as well as the destination bitmap--as a result, the output remains interlaced.
The fix is simple enough, just need to add a counter in order to differentiate between rows from the source GIF data, and rows in the destination bitmap.
Here's an (ancient) sample interlaced gif for testing:
http://www.quarkist.com/ARCH/W1/FRAME_N/LTOPS/ltop07.htm
Note that this is a single frame GIF--the demo project balks at it due to a separate issue; a division by zero in the timing logic around line 134 of GifInstance.cs. For the sake of testing, I just set timeModulus to TimeSpan.Zero since animation logic wasn't relevant here.
(I'm using GifDecoder directly in my project, so I didn't encounter the latter issue until testing for this PR).
Thanks for reading.
—Daniel

@dotnet-policy-service agree


Allow for prediction feedback from users with Anonymous Uploading act…

…ive.

Going to wait on this.


Unable to open the pages of jobs that need retry, recent failures, or pending jobs.

When attempting to open the pages of jobs in the retry queue, the page of recent failures, or the page of pending jobsI am redirected to the error page with the following:
NoMethodError at /jobs
undefined method `job_data' for #<Class:0x0000000a6e9948>

#<Class:0x007f9ba8491ee8>#agent_from_job app/helpers/jobs_helper.rb, line 28 block in

#<Class:0x007f9ba8491ee8>#_app_views_jobs_index_html_erb___211026912930636147_70153260002320 app/views/jobs/index.html.erb, line 23

#<Class:0x007f9ba8491ee8>#_app_views_jobs_index_html_erb___211026912930636147_70153260002320 app/views/jobs/index.html.erb, line 22

block (2 levels) in JobsController#index app/controllers/jobs_controller.rb, line 8

JobsController#index
app/controllers/jobs_controller.rb, line 7

Rails::Rack::Logger#call_with_silence_worker_status
config/initializers/silence_worker_status_logger.rb, line 5

I've just updated my local copy to commit 8dc5387f0b14940af6c728fe4f5c570d325c32ff and run the upgrade process.  What other information would be necessary for troubleshooting?

This only happens when trying to do so from a particular agent's page when multiple agents' pages are open.  When all agents' pages are closed and only the Huginn dash is open, they work.

Stack trace from development.log:
23:13:50 web.1  |   Rendered jobs/index.html.erb within layouts/application (65.8ms)
23:13:50 web.1  | Completed 500 Internal Server Error in 73ms (ActiveRecord: 7.7ms)
23:13:50 web.1  | NoMethodError - undefined method `job_data' for #<Class:0x0000000a6e9948>:
23:13:50 web.1  |   activerecord (4.2.1) lib/active_record/dynamic_matchers.rb:26:in `method_missing'
23:13:50 web.1  |   delayed_job (4.0.6) lib/delayed/performable_method.rb:34:in `method_missing'
23:13:50 web.1  |   app/helpers/jobs_helper.rb:28:in `agent_from_job'
23:13:50 web.1  |   app/views/jobs/index.html.erb:23:in `block in _app_views_jobs_index_html_erb___2110269129306361477_70153260002320'
23:13:50 web.1  |   activerecord (4.2.1) lib/active_record/relation/delegation.rb:46:in `each'
23:13:50 web.1  |   app/views/jobs/index.html.erb:22:in `_app_views_jobs_index_html_erb___2110269129306361477_70153260002320'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/template.rb:145:in `block in render'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/notifications.rb:166:in `instrument'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/template.rb:333:in `instrument'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/template.rb:143:in `render'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/renderer/template_renderer.rb:54:in `block (2 levels) in render_template'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/renderer/abstract_renderer.rb:39:in `block in instrument'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/notifications.rb:164:in `block in instrument'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/notifications/instrumenter.rb:20:in `instrument'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/notifications.rb:164:in `instrument'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/renderer/abstract_renderer.rb:39:in `instrument'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/renderer/template_renderer.rb:53:in `block in render_template'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/renderer/template_renderer.rb:61:in `render_with_layout'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/renderer/template_renderer.rb:52:in `render_template'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/renderer/template_renderer.rb:14:in `render'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/renderer/renderer.rb:42:in `render_template'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/renderer/renderer.rb:23:in `render'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/rendering.rb:100:in `_render_template'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/streaming.rb:217:in `_render_template'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/rendering.rb:83:in `render_to_body'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/rendering.rb:32:in `render_to_body'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/renderers.rb:37:in `render_to_body'
23:13:50 web.1  |   actionpack (4.2.1) lib/abstract_controller/rendering.rb:25:in `render'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/rendering.rb:16:in `render'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:44:in `block (2 levels) in render'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/core_ext/benchmark.rb:12:in `block in ms'
23:13:50 web.1  |   /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/core_ext/benchmark.rb:12:in `ms'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:44:in `block in render'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:87:in `cleanup_view_runtime'
23:13:50 web.1  |   activerecord (4.2.1) lib/active_record/railties/controller_runtime.rb:25:in `cleanup_view_runtime'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:43:in `render'
23:13:50 web.1  |   app/controllers/jobs_controller.rb:8:in `block (2 levels) in index'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/mime_responds.rb:215:in `respond_to'
23:13:50 web.1  |   app/controllers/jobs_controller.rb:7:in `index'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/implicit_render.rb:4:in `send_action'
23:13:50 web.1  |   actionpack (4.2.1) lib/abstract_controller/base.rb:198:in `process_action'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/rendering.rb:10:in `process_action'
23:13:50 web.1  |   actionpack (4.2.1) lib/abstract_controller/callbacks.rb:20:in `block in process_action'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:117:in `call'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:505:in `call'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:92:in `_run_callbacks'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:776:in `_run_process_action_callbacks'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:81:in `run_callbacks'
23:13:50 web.1  |   actionpack (4.2.1) lib/abstract_controller/callbacks.rb:19:in `process_action'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/rescue.rb:29:in `process_action'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/notifications.rb:164:in `block in instrument'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/notifications/instrumenter.rb:20:in `instrument'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/notifications.rb:164:in `instrument'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:30:in `process_action'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
23:13:50 web.1  |   activerecord (4.2.1) lib/active_record/railties/controller_runtime.rb:18:in `process_action'
23:13:50 web.1  |   actionpack (4.2.1) lib/abstract_controller/base.rb:137:in `process'
23:13:50 web.1  |   actionview (4.2.1) lib/action_view/rendering.rb:30:in `process'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal.rb:196:in `dispatch'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_controller/metal.rb:237:in `block in action'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/routing/route_set.rb:43:in `serve'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/journey/router.rb:43:in `block in serve'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/journey/router.rb:30:in `serve'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/routing/route_set.rb:819:in `call'
23:13:50 web.1  |   omniauth (1.2.2) lib/omniauth/strategy.rb:186:in `call!'
23:13:50 web.1  |   omniauth (1.2.2) lib/omniauth/strategy.rb:164:in `call'
23:13:50 web.1  |   omniauth (1.2.2) lib/omniauth/strategy.rb:186:in `call!'
23:13:50 web.1  |   omniauth (1.2.2) lib/omniauth/strategy.rb:164:in `call'
23:13:50 web.1  |   warden (1.2.3) lib/warden/manager.rb:35:in `block in call'
23:13:50 web.1  |   warden (1.2.3) lib/warden/manager.rb:34:in `call'
23:13:50 web.1  |   rack (1.6.1) lib/rack/etag.rb:24:in `call'
23:13:50 web.1  |   rack (1.6.1) lib/rack/conditionalget.rb:25:in `call'
23:13:50 web.1  |   rack (1.6.1) lib/rack/head.rb:13:in `call'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/middleware/params_parser.rb:27:in `call'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/middleware/flash.rb:260:in `call'
23:13:50 web.1  |   rack (1.6.1) lib/rack/session/abstract/id.rb:225:in `context'
23:13:50 web.1  |   rack (1.6.1) lib/rack/session/abstract/id.rb:220:in `call'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/middleware/cookies.rb:560:in `call'
23:13:50 web.1  |   activerecord (4.2.1) lib/active_record/query_cache.rb:36:in `call'
23:13:50 web.1  |   activerecord (4.2.1) lib/active_record/connection_adapters/abstract/connection_pool.rb:649:in `call'
23:13:50 web.1  |   activerecord (4.2.1) lib/active_record/migration.rb:378:in `call'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:88:in `_run_callbacks'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:776:in `_run_call_callbacks'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:81:in `run_callbacks'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/middleware/callbacks.rb:27:in `call'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
23:13:50 web.1  |   better_errors (1.1.0) lib/better_errors/middleware.rb:84:in `protected_app_call'
23:13:50 web.1  |   better_errors (1.1.0) lib/better_errors/middleware.rb:79:in `better_errors_call'
23:13:50 web.1  |   better_errors (1.1.0) lib/better_errors/middleware.rb:56:in `call'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
23:13:50 web.1  |   railties (4.2.1) lib/rails/rack/logger.rb:38:in `call_app'
23:13:50 web.1  |   railties (4.2.1) lib/rails/rack/logger.rb:20:in `block in call'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/tagged_logging.rb:68:in `block in tagged'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/tagged_logging.rb:26:in `tagged'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/tagged_logging.rb:68:in `tagged'
23:13:50 web.1  |   railties (4.2.1) lib/rails/rack/logger.rb:20:in `call'
23:13:50 web.1  |   config/initializers/silence_worker_status_logger.rb:5:in `call_with_silence_worker_status'
23:13:50 web.1  |   quiet_assets (1.1.0) lib/quiet_assets.rb:27:in `call_with_quiet_assets'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/middleware/request_id.rb:21:in `call'
23:13:50 web.1  |   rack (1.6.1) lib/rack/methodoverride.rb:22:in `call'
23:13:50 web.1  |   rack (1.6.1) lib/rack/runtime.rb:18:in `call'
23:13:50 web.1  |   activesupport (4.2.1) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
23:13:50 web.1  |   rack (1.6.1) lib/rack/lock.rb:17:in `call'
23:13:50 web.1  |   actionpack (4.2.1) lib/action_dispatch/middleware/static.rb:113:in `call'
23:13:50 web.1  |   rack (1.6.1) lib/rack/sendfile.rb:113:in `call'
23:13:50 web.1  |   railties (4.2.1) lib/rails/engine.rb:518:in `call'
23:13:50 web.1  |   railties (4.2.1) lib/rails/application.rb:164:in `call'
23:13:50 web.1  |   rack (1.6.1) lib/rack/lock.rb:17:in `call'
23:13:50 web.1  |   rack (1.6.1) lib/rack/content_length.rb:15:in `call'
23:13:50 web.1  |   rack (1.6.1) lib/rack/handler/webrick.rb:89:in `service'
23:13:50 web.1  |   /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/webrick/httpserver.rb:138:in `service'
23:13:50 web.1  |   /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/webrick/httpserver.rb:94:in `run'
23:13:50 web.1  |   /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/webrick/server.rb:295:in `block in start_thread'

Let's see what you're getting.  Would you mind changing agent_from_job in app/helpers/jobs_helper.rb to the following:
def agent_from_job(job)
    begin
      instance = YAML.load(job.handler)
      Agent.find_by_id(instance.job_data['arguments'][0])
    rescue NoMethodError
      raise "Got the following: #{instance.class.to_s) from #{job} that had #{job.handler}"
    rescue ArgumentError
      # We can get to this point before all of the agents have loaded (usually,
      # in development)
      nil
    end
  end

/cc @evaryont and @dsander

I could be caused by an old job which was created before we added the AcitveJob interface. Maybe we should change ArgumentError to StandardError?

@cantino I've made the requested change to app/helpers/jobs_helper.rb and restarted Huginn; it seems to have restarted properly.  I was able to load /jobs successfully but just captured a stack trace in development.log, which I'll post in a following comment.
@dsander I created [mumble] hundred agents prior to the addition of ActiveJob, so that seems like a reasonable hypothesis to test.

16:52:15 web.1  |   Rendered jobs/index.html.erb (14.0ms)
16:52:15 web.1  | Completed 500 Internal Server Error in 22ms (ActiveRecord: 2.9ms)
16:52:15 web.1  |
16:52:15 web.1  | RuntimeError - Got the following: Delayed::PerformableMethod from #<Delayed::Backend::ActiveRecord::Job:0x0000000af41118> that had --- !ruby/object:Delayed::PerformableMethod
16:52:15 web.1  | object: !ruby/class 'Agent'
16:52:15 web.1  | method_name: :run_schedule
16:52:15 web.1  | args:
16:52:15 web.1  | - every_2m
16:52:15 web.1  | :
16:52:15 web.1  |   app/helpers/jobs_helper.rb:31:in `rescue in agent_from_job'
16:52:15 web.1  |   app/helpers/jobs_helper.rb:27:in `agent_from_job'
16:52:15 web.1  |   app/views/jobs/index.html.erb:23:in `block in _app_views_jobs_index_html_erb__841307105909307981_69910460230120'
16:52:15 web.1  |   activerecord (4.2.1) lib/active_record/relation/delegation.rb:46:in `each'
16:52:15 web.1  |   app/views/jobs/index.html.erb:22:in `_app_views_jobs_index_html_erb__841307105909307981_69910460230120'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/template.rb:145:in `block in render'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/notifications.rb:166:in `instrument'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/template.rb:333:in `instrument'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/template.rb:143:in `render'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/renderer/template_renderer.rb:54:in `block (2 levels) in render_template'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/renderer/abstract_renderer.rb:39:in `block in instrument'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/notifications.rb:164:in `block in instrument'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/notifications/instrumenter.rb:20:in `instrument'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/notifications.rb:164:in `instrument'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/renderer/abstract_renderer.rb:39:in `instrument'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/renderer/template_renderer.rb:53:in `block in render_template'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/renderer/template_renderer.rb:61:in `render_with_layout'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/renderer/template_renderer.rb:52:in `render_template'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/renderer/template_renderer.rb:14:in `render'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/renderer/renderer.rb:42:in `render_template'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/renderer/renderer.rb:23:in `render'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/rendering.rb:100:in `_render_template'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/streaming.rb:217:in `_render_template'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/rendering.rb:83:in `render_to_body'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/rendering.rb:32:in `render_to_body'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/renderers.rb:37:in `render_to_body'
16:52:15 web.1  |   actionpack (4.2.1) lib/abstract_controller/rendering.rb:25:in `render'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/rendering.rb:16:in `render'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:44:in `block (2 levels) in render'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/core_ext/benchmark.rb:12:in `block in ms'
16:52:15 web.1  |   /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/core_ext/benchmark.rb:12:in `ms'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:44:in `block in render'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:87:in `cleanup_view_runtime'
16:52:15 web.1  |   activerecord (4.2.1) lib/active_record/railties/controller_runtime.rb:25:in `cleanup_view_runtime'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:43:in `render'
16:52:15 web.1  |   app/controllers/jobs_controller.rb:8:in `block (2 levels) in index'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/mime_responds.rb:215:in `respond_to'
16:52:15 web.1  |   app/controllers/jobs_controller.rb:7:in `index'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/implicit_render.rb:4:in `send_action'
16:52:15 web.1  |   actionpack (4.2.1) lib/abstract_controller/base.rb:198:in `process_action'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/rendering.rb:10:in `process_action'
16:52:15 web.1  |   actionpack (4.2.1) lib/abstract_controller/callbacks.rb:20:in `block in process_action'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:117:in `call'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:505:in `call'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:92:in `_run_callbacks'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:776:in `_run_process_action_callbacks'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/callbacks.rb:81:in `run_callbacks'
16:52:15 web.1  |   actionpack (4.2.1) lib/abstract_controller/callbacks.rb:19:in `process_action'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/rescue.rb:29:in `process_action'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/notifications.rb:164:in `block in instrument'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/notifications/instrumenter.rb:20:in `instrument'
16:52:15 web.1  |   activesupport (4.2.1) lib/active_support/notifications.rb:164:in `instrument'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/instrumentation.rb:30:in `process_action'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
16:52:15 web.1  |   activerecord (4.2.1) lib/active_record/railties/controller_runtime.rb:18:in `process_action'
16:52:15 web.1  |   actionpack (4.2.1) lib/abstract_controller/base.rb:137:in `process'
16:52:15 web.1  |   actionview (4.2.1) lib/action_view/rendering.rb:30:in `process'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal.rb:196:in `dispatch'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_controller/metal.rb:237:in `block in action'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_dispatch/routing/route_set.rb:43:in `serve'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_dispatch/journey/router.rb:43:in `block in serve'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_dispatch/journey/router.rb:30:in `serve'
16:52:15 web.1  |   actionpack (4.2.1) lib/action_dispatch/routing/route_set.rb:819:in `call'
16:52:15 web.1  |   omniauth (1.2.2) lib/omniauth/strategy.rb:186:in `call!'
16:52:15 web.1  |   omniauth (1.2.2) lib/omniauth/strategy.rb:164:in `call'
16:52:15 web.1  |   omniauth (1.2.2) lib/omniauth/strategy.rb:186:in `call!'
16:52:15 web.1  |   omniauth (1.2.2) lib/omniauth/strategy.rb:164:in `call'
16:52:15 web.1  |   warden (1.2.3) lib/warden/manager.rb:35:in `block in call'
16:52:15 web.1  |   warden (1.2.3) lib/warden/manager.rb:34:in `call'
16:52:15 web.1  |   rack (1.6.1) lib/rack/etag.rb:24:in `call'
16:52:15 web.1  |   rack (1.6.1) lib/rack/conditionalget.rb:25:in `call'`block in check_urls'
16:46:40 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:172:in `each'
16:46:40 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:172:in `check_urls'
16:46:40 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:166:in `check'
16:46:40 jobs.1 | /home/drwho/huginn/app/jobs/agent_check_job.rb:7:in `perform'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activejob-4.2.1/lib/active_job/execution.rb:32:in `block in perform_now'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:117:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:117:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:505:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:505:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:498:in `block (2 levels) in around'
16:46:40 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:172:in `each'
16:46:40 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:172:in `check_urls'
16:46:40 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:166:in `check'
16:46:40 jobs.1 | /home/drwho/huginn/app/jobs/agent_check_job.rb:7:in `perform'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activejob-4.2.1/lib/active_job/execution.rb:32:in `block in perform_now'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:117:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:117:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:505:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:505:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:498:in `block (2 levels) in around'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib
/active_support/callbacks.rb:343:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:343:in `block (2 levels) in simple'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activejob-4.2.1/lib/active_job/logging.rb:23:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activejob-4.2.1/lib/active_job/logging.rb:23:in `block (4 levels) in <module:Logging>'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/notifications.rb:164:in `block in instrument'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/notifications.rb:164:in `instrument'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activejob-4.2.1/lib/active_job/logging.rb:22:in `block (3 levels) in <module:Logging>'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activejob-4.2.1/lib/active_job/logging.rb:43:in `block in tag_logger'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/tagged_logging.rb:68:in `block in tagged'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/tagged_logging.rb:26:in `tagged'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/tagged_logging.rb:68:in `tagged'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activejob-4.2.1/lib/active_job/logging.rb:43:in `tag_logger'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activejob-4.2.1/lib/active_job/logging.rb:19:in `block (2 levels) in <module:Logging>'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:441:in `instance_exec'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:441:in `block in make_lambda'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:342:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:342:in `block in simple'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:497:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:497:in `block in around'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:505:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:505:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:92:in `_run_callbacks'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:776:in `_run_perform_callbacks'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:81:in `run_callbacks'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activejob-4.2.1/lib/active_job/execution.rb:31:in `perform_now'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activejob-4.2.1/lib/active_job/execution.rb:21:in `execute'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/activejob-4.2.1/lib/active_job/queue_adapters/delayed_job_adapter.rb:34:in `perform'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/backend/base.rb:94:in `block in invoke_job'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/backend/base.rb:91:in `invoke_job'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:204:in `block (2 levels) in run'
16:46:40 jobs.1 | /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/timeout.rb:91:in `block in timeout'
16:46:40 jobs.1 | /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/timeout.rb:101:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/timeout.rb:101:in `timeout'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:204:in `block in run'
16:46:40 jobs.1 | /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:203:in `run'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:280:in `block in reserve_and_run_one_job'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:280:in `reserve_and_run_one_job'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:187:in `block in work_off'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:186:in `times'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:186:in `work_off'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:150:in `block (4 levels) in start'
16:46:40 jobs.1 | /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:149:in `block (3 levels) in start'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:148:in `block (2 levels) in start'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:147:in `loop'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:147:in `block in start'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/plugins/clear_locks.rb:7:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/plugins/clear_locks.rb:7:in `block (2 levels) in <class:ClearLocks>'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `block in add'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
16:46:40 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:146:in `start'
16:46:40 jobs.1 | bin/threaded.rb:49:in `block (2 levels) in <top (required)>'
16:46:40 jobs.1 | bin/threaded.rb:19:in `safely'
16:46:40 jobs.1 | bin/threaded.rb:46:in `block in <top (required)>'

Another data point: Sometimes I can load the /jobs page and get the stack trace, and sometimes I get the "RuntimeError at /jobs" error page from Rails when I try.  Not sure what the deciding condition is yet.

Since making the change suggested, I've started getting the following runtime error and no /jobs page:

RuntimeError at /jobs

Got the following: Delayed::PerformableMethod from #<Delayed::Backend::ActiveRecord::Job:0x007f2a920057d0> that had --- !ruby/object:Delayed::PerformableMethodobject: !ruby/class 'Agent'
method_name: :run_schedule
args:
- every_5m

@dsander, I assume Delayed::PerformableMethod is the older style?

@cantino Yes

The "Recent Failures" page opens for me pretty reliably.  The "Pending Jobs" (/jobs) page still throws the runtime error:
Got the following: Delayed::PerformableMethod from
    #<Delayed::Backend::ActiveRecord::Job:0x007f37e0815f78> that had ---
    !ruby/object:Delayed::PerformableMethod
object: !ruby/class 'Agent'
method_name: :receive!
args: []

By the way, this happens on commit 1e57f3a4572f041be01e0a533d24c417235ab752.

Can you update after 180b694dbd39f08c41deceba9860961dbc4936d3? I think that commit should fix that issue

Let me give it a go...

Updated to 6a0dcd43ce37def6c196bb72bbf89f0dc4ad278e.  Huginn is up and running.  I've just been able to load the /jobs page once.  Trying it a few times over a few minutes shows that it's much more reliable.  I haven't gotten a single exception yet.
(said to see if I can provoke one... and not so far.)

I haven't been able to reproduce this bug since that time.  Clicking on the "Jobs awaiting retry" button just dumps me to the /jobs page, but I haven't seen this specific bug since my last comment.

Great!


Please publish 2.0

The latest release on npm is 1.0. Please publish the latest version. Thanks!

Ups, not sure how that happened. It has been released now. Thanks for pinging me :)


Create utility for screen capturing similar to lumina-screenshot

What are you thinking for how this will differ from our existing screenshot utility?  Just curious what cool idea you have in mind.

I think zach is referring to a screen capture GUI for recording videos, similar to how screenshot captures a picture.

Can Qt do native video encoding?  I've always done it with ffmpeg, example
ffmpeg -f oss -i /dev/dsp2.0 -f x11grab -s 1920x1080 -framerate 30 -i  :0.0 -acodec libmp3lame -ab 128k -vcodec mpeg4 -b:v 24000k test1.mp4
That could be a simple bash script that just greps the necessary stuff from the machine to figure our sound device and resolution.  A Qt program would be cool as well, though I'm wondering if it'd be more efficient on system resources than ffmpeg directly.  Though doing it through Qt would allow you to specific a screen region instead of the entire screen.

I think the initial idea was to just make a Qt front-end to ffmpeg, so the user could easily pre-select the options that are used, as well as provide a system tray icon for the screen capture to allow the user to see/close the capture as needed.
For example from your ffmpeg command:

Select the screen area by click/drag rather and calculate the geometry for the "-s" flag automatically.
Automatically read/set the X11 display number (":0.0" in your example)
Provide a slider for changing the framerate within reasonable values (10-60?)
and more....


How can this plugin support nested JSON object?

Its working fine with one to one properties in JSON but not with nested JSON object. Is there a way i can use nested JSON and get the localized string?

Hi.
Sorry, but not with the current approach.
The localization library have like core the idea of "I search the key and if I find it, I'll return the value, otherwise I'll return back the key".
This kind of approach can't be compatible with nested dictionaries, because its hypotesis is that the json is a KEY-VALUE type only.


Download more cross builds

r? @brson
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit 33f2718 has been approved by alexcrichton

:hourglass: Testing commit 33f2718 with merge d7e53ff...

:broken_heart: Test failed - cargo-cross-linux

:pushpin: Commit 1303803 has been approved by alexcrichton

@bors: r+

:hourglass: Testing commit 1303803 with merge 62b5992...

:broken_heart: Test failed - cargo-linux-64

@bors: retry
On Mon, Oct 24, 2016 at 10:43 PM, bors<EMAIL_ADDRESS>wrote:

💔 Test failed - cargo-linux-64
https://buildbot.rust-lang.org/builders/cargo-linux-64/builds/1863
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang/cargo/pull/3226#issuecomment-255941912, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAD95LB59lDh7Rb74-7ZAiR2i89gaqgOks5q3ZcdgaJpZM4Kfhkg
.

:zap: Previous build results for cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64 are reusable. Rebuilding only cargo-cross-linux, cargo-linux-32, cargo-linux-64...

:sunny: Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64
Approved by: alexcrichton
Pushing 62b5992f0ebcbb9077fbd1a5d53c0378c67b95d2 to master...


grdcontour Implementation

Implemented Figure.grdcontour that uses grdcontour gmt module
Plots grids to contours, with its own set of distinct inputs from pscontour
Test and Initial Documentation is complete
TODO

[x] Expand Docstring for function.
[x] Review chosen shorthand arguments for consistency with other modules
[x] Refine tests
[x] Regenerate baseline images.

@leouieda Build fails, due to test image mismatches, I suspect the density of features is playing a role, since 2 fail and 2 do not, and the ones that fail are denser contours. I will make a todo to refine the tests, but I suspect regenerating the images on the same machine (like what needed to be done for #212) will help. Not sure how to handle it

@akshmakov I don't know why, but in #212 the image generated on a Mac fails the linux tests but the image I generated on my linux machine passes all tests. Let me know when you're done with the code and I'll regenerate the images on my machine.

@leouieda Finished expanded docs and keyword expansion. Removed WIP Status, ready to merge pending updated baseline plots
Are you on the island right now? Stay safe! :cloud_with_rain:
P.s. Might baseline issue be due to default fonts? I am generating on linux machines as well and they fail on travis due to baseline mismatch, but pass on my machine

@akshmakov thanks again for the contribution! I re-generated the baselines and fixed some code formatting issues. Once CI gods are happy, I'll merge this in!

Thanks @akshmakov! Please feel free to add yourself to the AUTHORS.md file (through another PR).

@leouieda will do on another commit, hopefully for another issue, thank you for the baseline images, I'm happy to contribute!
Is there a style guide that I can review? Would black flag these instances?  I only recently installed and learned to use it, so my future PR's shouldn't be annoying
P.S. I have some suspicion that baseline mismatches may be related to default system fonts.


Scroll user to the selected topic.

Fixes #32601
discussion: https://chat.zulip.org/#narrow/channel/9-issues/topic/.F0.9F.93.82.20auto-scroll.20left.20sidebar.3F

Merged after fixing the zoomed spelling noted above, thanks @amanagr!


"Invalid JSON Schema" bug

b7a1fb97329fa3db395e8fd252afb660e7146d0c introduced a different bug. Debugging in progress with @rkpasia

Error message:
Invalid schema or undefined parsed schema
Something is wrong

Now reverting a282f54 with 926a364833fdde6cd10a554d44e9bed2358e4bb7. Closing.


HTTPS

Hi, How can activate https connection? VoIP can't use via http.

this image is based on nginx, so configure https as you would using nginx
http://nginx.org/en/docs/http/configuring_https_servers.html
https://medium.com/faun/setting-up-ssl-certificates-for-nginx-in-docker-environ-e7eec5ebb418
feel free to submit a pull request with documentation update on the README.md to enable this, ty


Stable Diffusion refiner SDXL1.0

The refiner is what makes SDXL and compatible models great quality.
https://huggingface.co/stabilityai/stable-diffusion-xl-refiner-1.0

You can use it with SD Turbo too.

This is not a very clear issue.
Taking it as a feature request,
I'd like to also mention that incorporating the "ensemble of expert denoisers"[1][2] technique would be very much appreciated.


Serve dev workbench using a domain other than localhost?

Category

[x] Question
[ ] Typo
[ ] Bug
[ ] Additional article idea

Our company does development on VMs.  Each machine has its own subdomain that runs with HSTS.
I was able to add certPath and keyPath easily enough to config/serve.json to get around the HSTS issues, but when accessing the workbench https://[DOMAIN]:4321/temp/workbench.html everything points to localhost.
Is it possible to configure the domain that is used as well for all the resources?
Adding serveConfig.domain to<EMAIL_ADDRESS>throws an error when I attempt to add the key and manually entering the domain throws further problems.
Is there something I'm missing in the initial setup?
Our workaround right now for anyone else with this problem is to port forward 4321 from the VM
e.g. ssh -L 4321:localhost:4321[vm_host]

As this is by design, changing the behavior would fall into the category of a feature request that should be submitted to uservoice at https://aka.ms/spfx-dev-uservoice


chia: 1.3.1 -> 1.5.0

Description of changes

https://github.com/Chia-Network/chia-blockchain/releases/tag/1.5.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

partial redundancy with 3ef7621167df207d13fbe288b78cb9f8573bc465

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1037


About web template

I like the web style, It's design by your self ?
Shall I use it on my app ?

Sure you can ;)


SimTelRunHeader (type=2000)

Playing around with this like:
In [1]: import eventio
   ...: f = eventio.EventIOFile('gamma_test.simtel.gz')
   ...: for o in f:
   ...:     if o.header.type == 2000:
   ...:         break
   ...: o.parse_data_field()

result is a dict

I believe the time should be converted into a real datetime
I think the run_type should be an enum:

Docu for run_type:
   int run_type;             ///< Data/pedestal/laser/muon run or MC run:
                             ///<   MC run: -1,
                             ///<   Data run: 1,
                             ///<   Pedestal run: 2,
                             ///<   Laser run: 3,
                             ///<   Muon run: 4.

No time to work on this for the next hours. Feel free to go on with this.

I fixed the runheader, I don't know where you got those B field and other fields, they are not written in write_hessio_runheader.
No the target is Monte Carlo beach (Awesome) and observer is<EMAIL_ADDRESS>


Unable to ping http://ascoderu.ca/lokole/ using legitimate GitHub assigned token

I am not able to ping Lokole main mail server http://ascoderu.ca/lokole/ dashboard hosted in Azure. This prevents to see Dashboard status and mail transactions between the server and the clients (Box Lokoles).
Note that the server is running, but the communications part is broken.

While opening the ping endpoint looks like it's an SSL certificate issue.

Ok. We hadcthis problème before and you fixed it.

While opening the ping endpoint looks like it's an SSL certificate issue.

Indeed.  Opening any browser to https://mailserver.lokole.ca reveals that Lokole allowed this (paid or unpaid) certificate to lapse:
"This server could not prove that it is mailserver.lokole.ca; its security certificate expired 43 days ago."

How do I renew the certificate
On Sat, Nov 12, 2022 at 1:36 PM A Holt @.***> wrote:

While opening the ping endpoint
https://mailserver.lokole.ca/healthcheck/ping looks like it's an SSL
certificate issue.
Indeed. Opening any browser to https://mailserver.lokole.ca reveals that
Lokole allowed this (paid or unpaid) certificate to lapse:
"This server could not prove that it is mailserver.lokole.ca; its
security certificate expired 43 days ago."
—
Reply to this email directly, view it on GitHub
https://github.com/ascoderu/lokole/issues/599#issuecomment-1312577688,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEH5MM7NAE6D4WGHZF7ZPY3WIAEVBANCNFSM6AAAAAAROSKZSY
.
You are receiving this because you authored the thread.Message ID:
@.***>

This is a business matter:
Clemens Wolff or others hopefully provided you a sheet of passwords and accounts, outlining what's needed for regular upkeep.

This is a business matter:
Clemens Wolff or others hopefully provided you a sheet of passwords and accounts, outlining what's needed for regular upkeep.

Yes. Clemens had provided me with all the passwords

I am not able to ping Lokole main mail server http://ascoderu.ca/lokole/ dashboard hosted in Azure. This prevents to see Dashboard status and mail transactions between the server and the clients (Box Lokoles). Note that the server is running, but the communications part is broken.

This issue was resolved last week. I rebooted the main server in Microsoft Azure cloud and everything returns normal. Now I can ping the Lokole VM and mail transfers from/to internet is working smoothly.


fix: Capture potential missing tail data for session trace

Send buffered session trace data in certain cases when it's being discarded at the tail end of a captured session.

Overview
In the old session trace behavior, it had discarded or not sent remaining session trace nodes when it hit the max duration life of the feature, even though the nodes were added before the max duration time. Likewise, on EoL of the page, session trace would not run final harvest if the buffered nodes is less than the required minimum of 30, which causes that valid data to be amiss. This PR patches both of those issues.
Related Issue(s)
NR-138555
Testing
Workflows listed in bug ticket's AC list should hold true, namely:

trace sends final harvest of < 30 nodes when in standalone
if there are any additional nodes buffered between the max duration point of time and its immediately preceding interval harvest, those are also sent, not discarded

I verified the safari tests that failed in github actions are passing locally. They appear to just be flakey.


Language Support

With this code you can add any language to this program.

That's not how language support should be approached.
-if you want to change something in the code you would have to change all language code
-cannot easily make another language


Add ability to  "Find and Replace" in the selected text only

In Visual Studio there is a feature to "Find an Replace" in the selected text in a file.
It would be very helpful to implement this feature in VS Code as well.
Thanks

CTRL + H --> select the find in selection icon (or ALT+L).
Does this work for you?

Hi, @tsalinger

CTRL + H --> select the find in selection icon (or ALT+L)

No, this does not work.
Please take a look at the attached recording:

Thank you.
Mykola.

Same here. 1.21.0. Reproducible in 100% cases. Setting "editor.find.autoFindInSelection": true doesn't help at all (the match count shows all occurrences in the document, Replace All replaces all occurrences in the document).

Thanks for reporting this issue, it only happens when you run Replace while running Find is good.


[Bug Report] Table filters fail after inserting new rows. (表格中插入新数据后，过滤器会失效)

Element UI version
1.3.7
OS/Browsers version
Ubuntu 14.04 / Chromium 58
Vue version
2.3.4
Reproduction Link
https://jsfiddle.net/xgyz9wex/
Steps to reproduce

User filters out some rows.
Program inserts new rows.

What is Expected?
After inserting new rows, filtered rows shall still be invisible.
What is actually happening?
After inserting new rows, all rows (including filtered-out rows) appear.

have any progress?


[Feature Request] Snippet/Card-like post or pages

Describe the feature you'd like
Hey there, great thanks for making such an extraordinary project! And i can't believe you've been working on it since 2015, that's super long! :) Thank you again!
One thing that had been in my mind when I was searching for personal knowledge base style software, is that it'd be great if i can have the ability to create some card-like or snippet style post, to quickly (in 15 ~ 30 mins) summarize a specific topic I've researched today and put it there properly.
I understand that the original intention of the project is to build some wiki, or book stack, as the name indicated, style software but honestly many people, at least for me, couldn't allocate big portion of time sitting at a table and write some serious blogs or books. I mean if I'm determined to write a book or long post I'll definitely schedule a plan but most of the time I don't write a book. Instead, I'll spend a day learning something and those processed, multi-source integrated knowledge went through my mind and I really like a place to write them down in 100 ~ 200 words, which doesn't fit into a "page" (some people are fine with those "short post" but I'm not).
One possible demonstration of my idea is this project. It has a demo.
Describe the benefits this feature would bring to BookStack users
Well, as I mentioned above, some people just don't have enough, consecutive time to sit down to write a long post. I'm not sure how big the number is but one fun fact is that most (serious) bloggers just don't update a lot, like a handful of articles per year :).  I think this idea might benefit them and encourage them to express ideas in an easier non-pressure way.
Finally, I totally understand that this idea might (somewhat) contradict the intention of this project and if you disagree with it, I'm totally cool. I just wanna put it here and see the possibilities.
btw, are you willing to accept Github Sponsors? To clarify, It definitely doesn't mean "I pay you to add a new feature" loool. It's just, the first time I saw the demo of this project, I was like "shit this project can't die". And I'll for sure recommend it to my boss as a team documentation tool, majorly because it has Azure AD Auth and, again, it's an amazing tool.
Thanks.

Hey there, great thanks for making such an extraordinary project! And i can't believe you've been working on it since 2015, that's super long! :) Thank you again!

Thank you so much!

Finally, I totally understand that this idea might (somewhat) contradict the intention of this project and if you disagree with it, I'm totally cool. I just wanna put it here and see the possibilities.

Thanks for your understanding and the detailed explanation of the benefits you see this bringing.
My thoughts would be that this kind of thing is essentially the management of notes. I don't really want to get deep into fully supporting a shared "notes" system as it'd make it unclear if something should be a page or a note. Additionally I wouldn't want to get deep into the note-taking space especially as there are already many note-taking focused apps out there.
That said, I could possibly see value in having quick-notes at a personal user-level (Not visible to others). We could keep this purposefully simplified so a page is used for anything more complex. They could be called scraps (As in scraps of paper) to fit the theme. This would only really work though if the smaller "scrap" ideas are eventually written into a page otherwise you'd just be using the system as a weak note-taking system. From the sounds of your use-case, you don't have that intention.
I guess a question is, what's wrong with creating pages for the shorter form content? You could just contain all these up in a book so they're all in one place.

My thoughts would be that this kind of thing is essentially the management of notes. I don't really want to get deep into fully supporting a shared "notes" system as it'd make it unclear if something should be a page or a note.

Yeah exactly I get it. That's where I felt might somewhat contradict to this tool. Never mind I'll keep this issue open till 30th Jan. and if nobody really cares I'll close it willingly :) how does that sound to you?

what's wrong with creating pages for the shorter form content?

Um I don't know, I just feel like short content shouldn't be a "blog" or "post", it should be like "sticky notes" or sth, where they all have their places and values. Not sure how other people think about it. Maybe it's just my problem.
But this

You could just contain all these up in a book so they're all in one place.

sounds like a tolerable idea. I can have those short "sticky notes" in one place. Sounds ok. I'll use this approach when the issue is closed. Thanks! :)

Sounds like this isn't an popular idea :). I'll close this issue.

Sounds like this isn't an popular idea :). I'll close this issue.


Iceberg catalog - Query specific snapshot

Feature request
Is your feature request related to a problem? Please describe.

I have an Iceberg table that gets data from kafka. hance I get a lot of commits per day and every commits create a snapshot.
I created MV on Iceberg table and I see on logs on Iceberg Rest server that Starrocks is asking for all snapshots
GET /iceberg/v1/main%7Craw/namespaces/db/tables/table?snapshots=all HTTP/1.1" 200 20159
I can have a lot of snapshots and don't need to get all the information for all of them. it causes high memory on Starrocks CN and Nessie Rest catalog.
Describe the solution you'd like

Would like to control getting only latest or specific snapshot.
Perhaps doing it on the create catalog or support doing it in the query itself.
Describe alternatives you've considered

Additional context

thanks for your issue. this is iceberg spec default behavior. ref: https://github.com/apache/iceberg/blob/main/open-api/rest-catalog-open-api.yaml#L935. If you set the snapshotMode to refs, and it will still access to all snapshots of main branch default. so I think there is currently no way to solve this problem.


[EAGLE-814] fix alertId is null in AlertStreamEvent bug

1

The issue is introduced by https://github.com/apache/incubator-eagle/commit/38ec7fc23d06c77b6e083ad2dfb9c61e729901e0#diff-2bb6be6fb3afdc59db75e1919ad89beaL97 which changed the alertId from AlertPublishEvent initialisation with random UUID to use AlertStreamEvent.alertId. However, AlertStreamEvent.alertId is not always initialised. The fix looks good.


genpy: 0.5.7-0 in 'jade/distribution.yaml' [bloom]

Increasing version of package(s) in repository genpy to 0.5.7-0:

upstream repository: git@github.com:ros/genpy.git
release repository: https://github.com/ros-gbp/genpy-release.git
distro file: jade/distribution.yaml
bloom version: 0.5.20
previous version for package: 0.5.6-0

genpy
* add line about encoding to generated Python files (#41 <https://github.com/ros/genpy/issues/41>)

Do not merge yet - waiting for other releases.


Marker not shown after Marker.setDrawable(Drawable drawable)

Hello, I have updated my local Tangram ES repository to tag 0.9.3 and I have found out that when I set bitmap to Marker through https://github.com/tangrams/tangram-es/blob/8ec65a8b28eb20373e9df6163312508f9ea9c4a7/platforms/android/tangram/src/main/java/com/mapzen/tangram/Marker.java#L122 marker is not shown at all on the map. I have traced that this problem is occurring from commit 1607bec6ecb6b336719c0606b0553f00876602b0. I have tried to find out why is this happening but after several hours I didn't came to a solution. I have also set to marker style "size: auto", it still doesn't solve the problem. Could you please look at this?

Had somebody some time to look into this already? Because this is a broken functionality in latest tagged version 0.9.3.

Hi @rwrx! Could you specify the drawrule used for the Drawable markers? I've added some code for testing which shows point markers with Drawables: https://github.com/tangrams/tangram-es/compare/android-marker-demo?expand=1#diff-0114b8cdd39733d35a3ac58d1f35a4ecR207
Hope this works for you!

Hi @hjanetzek. Thank you. I got it. It does not work when you add "sprite" to a draw rule. I took draw rule specified in that code you mentioned:
"{ style: 'points', color: 'white', size: [50px, 50px], order: 2000, collide: false }"
and added there "sprite: default-marker" rule:
"{ style: 'points', sprite: default-marker, color: 'white', size: [50px, 50px], order: 2000, collide: false }"
and this makes it not working. I am also using setStylingFromString() method. In my style yaml file I have set that default-marker this way under textures:
markers:
    url: images/default-marker.png
    filtering: mipmap
    sprites:
        default-marker: [0, 0, 90, 164]

Also I am mentioning that this worked before that 1607bec commit. So is this a bug or am I missing something that sprites (as a fallback) should not work in this scenario?


Would you support conversion from torch to onnx and ncnn?

As the title mentioned, one of the strength of yolov9 is the relatively high accuracy with smaller size and faster speed, a great tool for embedded devices. I think it would be a nice feature for this project

@henrytsui000 I would like to contribute in this one. Is there any work done on exporting to different formats like onnx, coreml and tflite?

@henrytsui000 I would like to contribute in this one. Is there any work done on exporting to different formats like onnx, coreml and tflite?

Thanks a lot!
You may find some existing code here:
https://github.com/WongKinYiu/YOLO/blob/dc88787a7f6fff89d6e60fb63ee20a4be1721b34/yolo/utils/deploy_utils.py#L11
To be honest, I'm not sure if the code is robust enough, but you can activate it using the following command:
python yolo/lazy.py task=inference task.fast_inference=onnx

Currently, it only supports ONNX and TensorRT.
If you're willing, you can add support for CoreML and TFLite, and help make the code more robust.
Best regards,
Henry Tsui

Thanks for your reply. Gonna check and try to contribute on this next weeks!

@henrytsui000
I think we want to remove the auxiliary branch on all export formats, right?
'''
if self.compiler == "onnx":
return self._load_onnx_model(device)
elif self.compiler == "trt":
return self._load_trt_model().to(device)
elif self.compiler == "deploy":
self.cfg.model.model.auxiliary = {}
'''

Yes, the auxiliary header is only used to train the model

@henrytsui000
Thanks for your reply. I managed to export tflite and now in the progress in getting all things on GPU.
For that, can we get rid of the Conv3d's in the network? Can we rewrite them to be Conv2D in some manner? I think I can find a workaround for those other dimension related problems since they are all in the detection head.
09-11 16:31:08.935 26380 26380 E tflite  : Following operations are not supported by GPU delegate:
09-11 16:31:08.935 26380 26380 E tflite  : CONV_3D: Operation is not supported.
09-11 16:31:08.935 26380 26380 E tflite  : GATHER: Only support 1D indices
09-11 16:31:08.935 26380 26380 E tflite  :
09-11 16:31:08.935 26380 26380 E tflite  : RESHAPE: OP is supported, but tensor type/shape isn't compatible.
09-11 16:31:08.935 26380 26380 E tflite  : SOFTMAX: OP is supported, but tensor type/shape isn't compatible.
09-11 16:31:08.935 26380 26380 E tflite  : TRANSPOSE: OP is supported, but tensor type/shape isn't compatible.
09-11 16:31:08.935 26380 26380 E tflite  : 763 operations will run on the GPU, and the remaining 15 operations will run on the CPU.

Any updates on this? I am trying to export the model to ONNX/Tensorrt as well but I do not see any explicit export file/module other than the unused export inside FastModelLoader in YOLO/yolo/utils/deploy_utils.py
Are we supposed to use the deploy_utils.py inside our custom files to export the model properly right now?