predict() from a Prior-sampled chain returns no predictions

Apparently Turing now has a built-in predict function, which is great. Unfortunately, when I run it on a prior-sampled chains object (to do a prior predictive check), it seems to return no predictions:
using Turing
using DataFrames

# Regression model example
@model function lm(y, x)
    # Priors
    σ² ~ InverseGamma(2, 3)  # Sigma
    intercept ~ Normal(0, sqrt(3))  # Intercept
    β ~ TDist(3)

    # Calculate all the mu terms.
    mu = intercept .+ x * β

    # Likelihood
    return y ~ Normal(mu, σ²)
end

chain = sample(lm(0, 0), Prior(), 50000)
pred = predict(lm(0, 0), chain)

Summary Statistics
  parameters   mean   std      mcse   ess_bulk   ess_tail      rhat   ess_per_sec
      Symbol    Any   Any   Float64    Float64    Float64   Float64       Missing

Quantiles
  parameters   2.5%   25.0%   50.0%   75.0%   97.5%
      Symbol    Any     Any     Any     Any     Any

DataFrame(pred)

50000×2 DataFrame
   Row │ iteration  chain
       │ Int64      Int64
───────┼──────────────────
     1 │         1      1
     2 │         2      1
     3 │         3      1
     4 │         4      1
     5 │         5      1
     6 │         6      1
   ⋮   │     ⋮        ⋮
 49995 │     49995      1
 49996 │     49996      1
 49997 │     49997      1
 49998 │     49998      1
 49999 │     49999      1
 50000 │     50000      1
        49988 rows omitted

Is there something I am missing?

In your case you can do
pred = predict(lm(missing, 0), chain)

The current implementation of predict assumes you've effectively un-conditioned the data-variables. The process effectively goes:

Run inference conditioned on y to get your posterior (represented by chain).
You now de-condition y so that it is treated as a random variable.
Using the posterior, i.e. chain, you sample y.

predict does Step 3 for you, but you have to do the de-conditioning yourself (Step 2).
The reason why we've done it this way is because it's completely valid for you to for example do
model = lm(0,0)
model_with_intercept_fixed = model | (intercept = 10.0, )

In this scenario, the conditioned variables are both y and intercept (variables can be conditioned using either arguments or |) and so we predict automatically sampled all variables that are conditioned, then it would both sample y and intercept.
It might make sense to add some functionality to allow the user to fix a variable, e.g. the intercept, while also specifying that it's not to be considered an observation. Once we have that, then we could add a predict with the behavior you expect:)

Interesting, thanks for the clarification!


[Question]: why synonym.Dealer() no pass redis param in init()?

There is a warning log in ragflow/rag/nlp/synonym.py
class Dealer:
    def __init__(self, redis=None):
       ...
       if not redis:
            logging.warning(
                "Realtime synonym is disabled, since no redis connection.")
       ...

And the redis here remains None, it has never been given any arguments.
The init code looks like:
class EsQueryer:
    def __init__(self, es):
        ...
        self.syn = synonym.Dealer()
        ...

So why redis here no given any arguments? This warning log remains forever.

We have not Implemented it. You could finish that in order to set synonyms without restarting service.


Coverity code scan findings

I ran Coverity Code Scans on a project with libosmium dependencies and found a few potential issues related to libosmium.
As always code analysis results should be taken with a grain of salt, some of the issues below are probably false alerts. In theory you should be able to access those results via the project link above. For reference, I have also added a few screenshots below.
btw: it might be worthwhile setting this up on your own as part of a continuous integration toolchain via Travis CI. The Coverity website has some further details on this.

Uncaught Exception:

These are all false positives.

Only because something still has a pointer to something that is destroyed doesn't mean it will actually use that pointer. m_bzstream.next_out is only used in BZ2_bzDecompress().
Objects of Changeset class are always created through ChangesetBuilder which sets the user_size.
add_padding() can not throw, because buffers are allocated in a way that there is always enough memory for the padding.

Thank you for the feedback. Yes, I thought so, though I wanted to make you aware that there are tools out there reporting some potential issues.
Regarding the first issue, m_bzstream.next_out has a longer lifetime than output.data() and probably still lingers around when read() method finishes in whatever state BZ2_bzDecompress() left it here. In theory, another method could try to use that buffer in m_bzstream at a later point in time when it's no longer valid. Method close()  calling BZ2_bzDecompressEnd(&m_bzstream); would come to mind, although implementation specifics are probably different in that case.

Frankly I don't like applications that require me to login to even see things and when you login require rights they don't need. I don't mind if you or somebody else runs those applications though.

Someone from synopsis, the vendor providing coverity, contacted me with the following request:

Before we can approve your project’s submission into SCAN, we need proof that you are a contributor to the upstream project. This requirement is necessary for our responsible disclosure policy.

As Github won't list me as "Contributor", I won't be able to access scan results. If you feel still positive about running those apps, I would mention that to synopsis.

@mmd-osm I am not sure what this means. You can already see those defects, can't you? Can't anybody see the results who is willing to login to coverity?

Oh, I think I forgot to add a bit of more context. So far, I included libosmium in my Overpass API branch and ran coverity on the whole project. I added some of those results to this issue.
Now, to get a better coverage (I only used a rather small part of libosmium with Overpass), I thought to run the whole libosmium make process through the code scan. For the latter, I had to request access, which hasn't been granted yet. The "View Defects" link for libosmium is still inactive:

Ah, okay. That makes more sense now. It also means that everbody can just create a project, include libosmium and then run all the checks they want. So why don't you just do that and then you don't have to ask for any permissions? :-)

Pinged @coverity again with regards to the project approval status, since there hasn't been a response to my email since more than a month now.

I'm closing this one due to lack of feedback from @coverity side.


fix: change deprecated code

There are some functions that are deprecated and will be removed in the next nvim version:
vim.treesitter.parse_query() is deprecated, use vim.treesitter.query.parse_query() instead. :help deprecated
This feature will be removed in Nvim version 0.10
vim.treesitter.query.parse_query() is deprecated, use vim.treesitter.query.parse() instead. :help deprecated
This feature will be removed in Nvim version 0.10
vim.treesitter.get_query() is deprecated, use vim.treesitter.query.get_query() instead. :help deprecated
This feature will be removed in Nvim version 0.10
vim.treesitter.query.get_node_text() is deprecated, use vim.treesitter.get_node_text() instead. :help deprecated
This feature will be removed in Nvim version 0.10

@juliopcrj Thanks! Looks like minor formatting issue, but I can fix that after merge. Thanks for the PR!


CpuDbg x96.exe crashes on application restart

when clicking "<<" icon
shows this window:

Does this problem occur randomly? Or is it a steady occurrence?

randomly, trying to collect clear steps...
BTW, you did a fresh build for x32 ,binary, how about x64 one?


[WIP] Kcov

kcov integration

This change is

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@fe12ec9). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #585   +/-   ##
=========================================
  Coverage          ?   94.74%
=========================================
  Files             ?       26
  Lines             ?     3026
  Branches          ?        0
=========================================
  Hits              ?     2867
  Misses            ?      159
  Partials          ?        0

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@fe12ec9). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #585   +/-   ##
=========================================
  Coverage          ?   94.74%
=========================================
  Files             ?       26
  Lines             ?     3026
  Branches          ?        0
=========================================
  Hits              ?     2867
  Misses            ?      159
  Partials          ?        0

henlo there. don't merge I'll finish tomorow.

bors try

bors r+


Add Global Undo and Redo

It would be nice if VS Code could support global undo and redo like in Visual Studio:

In addition to the typical undo and redo functionality that affects only individual files, the Visual Studio editor includes commands to undo or redo global actions that affect multiple files.

Global actions include renaming a class or namespace, performing a find-and-replace operation across a solution, refactoring a database, or any other action that changes multiple files.

https://msdn.microsoft.com/en-us/library/ee839600(v=vs.100).aspx
Right now it's difficult to undo a search and replace or refactoring because you have to go through every file.
See also: atom/find-and-replace#331

See also: atom/find-and-replace#331

Actually #638


Write a Ruby program to print all prime numbers between two numbers

Description
Write a Ruby program to print all prime numbers between two numbers
Input  : 10 20
Output : 11 13 17 19

How to contribute

Save the solution in PrintAllPrimeNumbersBetweenTwoNumbers.rb file
Add PrintAllPrimeNumbersBetweenTwoNumbers.rb file in print-all-prime-numbers-between-two-numbers folder

!assign


Logging decouple

This decouples FLAnimatedImage from any specific logging libraries, logging is instead handled by passing a block that's invoked when logging should occur to FLAnimatedImage via +setLogBlock:. This resolves issue https://github.com/Flipboard/FLAnimatedImage/issues/107 which was preventing FLAnimatedImage from working in projects that also used Cocoa Lumberjack Logger when built with Carthage.

Discussed a bit in person, going to leave as-si.

:+1:


Add section for experimental custom regex scopes to customization.md

Checklist

[X] I have added tests
[X] I have updated the docs and cheatsheet
[X] I have not broken the cheatsheet

No functionality was changed, so no tests were written
Updated docs, but not cheatsheet (since it's only user settings change, not Cursorless change)
No changes to cheatsheet were made

Once this is merged, I'll update https://github.com/cursorless-dev/cursorless/wiki/Custom-regex-scopes to point to this new section.

Changes made (some outstanding questions), ready for another review. Let me know if any tweaks are needed.


PDF Print display issue

When I attempted to print a markdown document converted using vmd, I ran into some strange display issues. Both l (lowercase) and I (uppercase) are rendered strangely, as shown in the attached image. Additionally, the table header is duplicated at the top of the page, causing it to overlay the page text. The Markdown is properly formatted (ie. spaces beneath headers, etc) as far as I can tell.
This image is an example PDF page, with the middle content cut out:

Yeah, that's weird. Can you attach or link the document so I can reproduce it? Or paste some Markdown text that causes the problem?

As far as I can tell, any text with either l or I causes the issue for me. I've also noticed that the spacing in bulleted lists is somewhat larger than expected (and than GitHub displays it), and code blocks have no background color.
Link to PDF: osgi.pdf
Link to Markdown: Can't attach .md files

Markdown is below

OSGi
OSGi — Open Service Gateway Initiative

OSGi is a Java framework for developing and deploying modular software programs and libraries.

Specification for modular components called bundles, commonly referred to as plug-ins. The specification defines an infrastructure for a bundle's life cycle and determines how bundles will interact.
The second part of OSGi is a Java Virtual Machine (JVM)-level service registry that bundles can use to publish, discover and bind to services in a service-oriented architecture (SOA).

OSGi provides a way that bundles can communicate with each other without being coupled together (interfaces, etc)

Summary
Note: Bundle and plug-in can be used interchangeably; plug-in is preferred by Eclipse, bundle is preferred by OSGi.
Most applications consist of several different parts, called modules or components, which interact with each other through an Application Programming Interface, or API. The API is considered to be the classes/methods which are accessible to other components. A component also has a set of classes/methods that are considered internal. Using an API from another component creates a dependency on the component, as it now requires the other component to be present in order to work correctly. Currently, Java doesn't provide a structured way to describe the various dependencies of a component; rather, every public class can be called from another component.
OSGi is a specification framework that defines a component and service model for creating loosely coupled modular bundles. Each bundle can define its API through a set of exported packages and also specify its own required dependencies.
Bundles
A bundle can define exports or dependencies on other bundles in its manifest file. OSGi prevents access to classes without a defined dependency (except for packages from the Java runtime). Dependencies can be defined as either bundle or package dependencies. Bundle dependencies enable accessing all exported packages from the bundle while package dependencies enable accessing a specific package without worrying what bundle exports it (enabling a later change). The OSGi runtime ensures that all dependencies are present before starting a plugin, activating them if necessary.
Bundle Lifecycle

#
Status
Description

1
Installed
Bundle has been installed

2
Resolved
All bundle dependencies have been resolved

3
Starting
Bundle is starting

4
Active
Bundle has started and is running

5
Stopping
Bundle is stopping

6
Resolved
N/A

7
Uninstalled
Bundle has been uninstalled

NOTE: Bundles must all contain an Activator class that is responsible for managing the bundle's life cycle, including a start() and stop() set of methods. These methods are responsible for handling any necessary preparation or clean up during the beginning and end of the bundle's life cycle.
Declarative Services
A service in OSGi is defined by a standard Java class or interface, composed of the class/interface for which you want to provide a service and the implementation class for the service interface. This enables switching out the service implementation but still using the existing service interface. Services can be dynamically stopped/started, so bundles that use these services must be able to handle this behaviour, typically done by the ServiceListener handlers.
It is good practice to define a service with a bundle that contains only the service interface definition, with another bundle providing the service implementation. This way, the implementation of the service can always be changed at a later time. Since dependent bundles only communicate with the service through the service interface, updating the service implementation should not break existing dependent bundles. For example, if an existing implementation used a SQL database to persist data but the developers wanted to switch to another database vendor, the only requirement would be that the new implementation correctly supports the existing service interface.
This is a code sample with no background color?
//Sample Java code
public void sampleMethod(String input) {
    if (input.equals("test")) {
        return true;
    }
    return false;
}

Declarative Services remove the need for registering and consuming services programmatically. Instead, Declarative Services can be declared by a Component Definition file, which is either manually configured or rendered automatically by Eclipse annotations (which will also update the MANIFEST).
List of Lifecycle Methods (duplicate)

Installed

Bundle has been installed

Resolved

All bundle dependencies have been resolved

This can cause problems?

Starting
Active

Bundle has been started and is running

NOTE: A Service Component Runtime bundle must be installed and activated on the device if using Declarative Services. However, this bundle will likely already be installed as part of the environment.

A bit more research shows that I am having trouble printing all markdown documents to PDFs, not just using your tool. However, the only issue I can replicate is the thick lines on l and I characters. The rest seem to be specific.

I'm also having the table header being duplicated on every page's top section... The Is and ls seem fine, though.
Using latest version (1.29.1), installed via npm on node 8.2.1 (also latest as of this writing).
I'm under Macos Sierra.

I was able to reproduce the problem with older versions of vmd.
Now I have tried it again in vmd 1.31.0 with Electron 1.7.6 and with the markdown document from @kendallroth and the PDF output looks great.
@kendallroth, @lfilho: Can you upgrade vmd to the latest version and try again?

Closing this because I can't reproduce the problem anymore in the latest version of vmd, and due to lack of activity in the issue comments.


Please add support for higher quality videos from xvideos

[x] I've verified and I assure that I'm running youtube-dl 2016.08.13
[x] Searched the bugtracker for similar issues including closed ones
[x] Feature request (request for a new functionality)

Description of the issue, suggested solution and other information
xvideos.com has now started offering videos in higher resolutions (actually, multiple resolutions) via HLS. Currently, youtube-dl is only downloading, via the URLs taken by the regexp, things via straight HTTP.
See, for example, the following video: http://www.xvideos.com/video22833069/anal_queen_from_brazil
The relevant HTML snippet is the following (yes, the indenting is messy):
			<script>logged_user = false;
	var html5player = new HTML5Player('html5video', '22833069');
	html5player.setVideoTitle('Anal Queen From Brazil');
	html5player.setSponsors(false);
	html5player.setVideoUrlLow('http://content.xvideos.com/videos/3gp/c/9/9/xvideos.com_c994677a47070a513b047354f1fb7b1c.mp4?e=1471362685&ri=1024&rs=85&h=0bcedcdb9793f7e4eacc07f95cd14704');
	html5player.setVideoUrlHigh('http://content.xvideos.com/videos/mp4/c/9/9/xvideos.com_c994677a47070a513b047354f1fb7b1c.mp4?e=1471362685&ri=1024&rs=85&h=09235234476a4665c9d89adf40ff80a2');
	html5player.setVideoHLS('http://cdn3-l3-cdn.xvideos.com/32e75581661733b3df6b1d863cd669e602458cf3-1471362685/videos/hls/c9/94/67/c994677a47070a513b047354f1fb7b1c/hls.m3u8');
	html5player.setThumbUrl('http://img-l3.xvideos.com/videos/thumbslll/c9/94/67/c994677a47070a513b047354f1fb7b1c/c994677a47070a513b047354f1fb7b1c.30.jpg');
	html5player.setRelated(video_related);
	html5player.setThumbSlide('http://img-l3.xvideos.com/videos/thumbs/c9/94/67/c994677a47070a513b047354f1fb7b1c/mozaique.jpg');
	html5player.setIdCDN('2');
	html5player.setIdCdnHLS('3');
	html5player.setFakePlayer(false);
	html5player.setDesktopiew(true);
	html5player.setVideoURL('/video22833069/anal_queen_from_brazil');
	html5player.initPlayer();
	</script>

If I manually grab the HLS URL and use ffmpeg with something like (the hashes may, of course, change due to timestamps being embedded in the URLs):
ffmpeg -i http://cdn3-l3-cdn.xvideos.com/c0fcdbe93306559fd86db1dd941faf2376020507-1471361420/videos/hls/c9/94/67/c994677a47070a513b047354f1fb7b1c/hls.m3u8 -c copy -bsf:a aac_adtstoasc -map 0:2 -map 0:3 out.mkv

I determined the substreams/programs in the HLS, manually. It would be nice to have the option of downloading higher quality files via ffmpeg than with pure HTTP. The difference in resolution is huge.
Thanks,
Rogério Brito.
P.S.: I believe that the amount of information that I provided is enough for understanding the problem. If not, please don't hesitate to ask for more details.

Thanks! I will upload this to Debian tomorrow (or by this weekend).
(I'm the package maintainer downstream).


scylla_post_start.py and scylla_configure.py should not exit with 0 when HTTP Error occurs

Related with #498
On current curl() implementation, all exceptions are catched to retrying access and never re-raised.
Because of this, we currently not able to get any HTTP Error related exception.
We should re-raise the exception after all retries are failed.
Or, maybe we don't need to retry for all HTTP Error, since the metadata server may returns specific error code when it's not available.

I was wrong, curl() is actually re-raise exception when HTTP Error received.
However, scylla_post_start.py and scylla_configure.py are catching exceptions and log it as ERROR but it will continue program and always exit with 0.
I think it should at least exit with 1 if Exception catched, or even stop catching Exception and cause Traceback.

BTW, curl() also has problem.
It unconditionally retries HTTP request when error occurs, even HTTP error was 404 Not Found - it unlikely fix by retrying.
I think we should stop retrying when HTTP Error was 400-499 (Client error responses, like 404 Not found or 403 Forbidden).


Cassandra read timeout during recovery

This is more an help request for troubleshooting a production issue than a formal bug report.
On an ActorSystem running with akka 2.4.0-RC3 (and a custom build of 0.4 journal of a couple of weeks ago) with several persistent actors, if after a time, the system restarts and all persistent actors recover, the session-SW always fails with the following error:
2015-10-11 16:46:23,999 [ERROR] c.d.a.l.SessionService - Persistence failure when replaying events for persistenceId [session-SW]. Last known sequence number [28703] - sourceThread=AsyncServer-akka.acto
r.default-dispatcher-31, akkaTimestamp=14:46:23.972UTC, akkaSource=akka.tcp://AsyncServer@<IP_ADDRESS>:2552/user/session-router/sw/session-manager/session, sourceActorSystem=AsyncServer
com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout during read query at consistency QUORUM (2 responses were required but only 0 replica responded)
   at com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:69)
   at com.datastax.driver.core.DefaultResultSetFuture.extractCauseFromExecutionException(DefaultResultSetFuture.java:289)
   at com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:205)
   at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:52)
   at akka.persistence.cassandra.journal.CassandraRecovery$RowIterator.inUse(CassandraRecovery.scala:128)
   at akka.persistence.cassandra.journal.CassandraRecovery$RowIterator.hasNext(CassandraRecovery.scala:138)
   at akka.persistence.cassandra.journal.CassandraRecovery$MessageIterator.fetch(CassandraRecovery.scala:75)
   at akka.persistence.cassandra.journal.CassandraRecovery$MessageIterator.next(CassandraRecovery.scala:63)
   at akka.persistence.cassandra.journal.CassandraRecovery$MessageIterator.next(CassandraRecovery.scala:44)
   at scala.collection.Iterator$class.foreach(Iterator.scala:742)
   at akka.persistence.cassandra.journal.CassandraRecovery$MessageIterator.foreach(CassandraRecovery.scala:44)
   at akka.persistence.cassandra.journal.CassandraRecovery$class.replayMessages(CassandraRecovery.scala:36)
   at akka.persistence.cassandra.journal.CassandraJournal.replayMessages(CassandraJournal.scala:23)
   at akka.persistence.cassandra.journal.CassandraRecovery$$anonfun$asyncReplayMessages$1.apply$mcV$sp(CassandraRecovery.scala:20)
   at akka.persistence.cassandra.journal.CassandraRecovery$$anonfun$asyncReplayMessages$1.apply(CassandraRecovery.scala:20)
   at akka.persistence.cassandra.journal.CassandraRecovery$$anonfun$asyncReplayMessages$1.apply(CassandraRecovery.scala:20)
   at scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
   at scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)
   at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:39)
   at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:399)
   at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
   at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
   at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
   at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout during read query at consistency QUORUM (2 responses were required but only 0 replica responded)
   at com.datastax.driver.core.exceptions.ReadTimeoutException.copy(ReadTimeoutException.java:69)
   at com.datastax.driver.core.Responses$Error.asException(Responses.java:100)
   at com.datastax.driver.core.DefaultResultSetFuture.onSet(DefaultResultSetFuture.java:140)
   at com.datastax.driver.core.RequestHandler.setFinalResult(RequestHandler.java:293)
   at com.datastax.driver.core.RequestHandler.onSet(RequestHandler.java:467)
   at com.datastax.driver.core.Connection$Dispatcher.messageReceived(Connection.java:734)
   at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
   at org.jboss.netty.handler.timeout.IdleStateAwareChannelUpstreamHandler.handleUpstream(IdleStateAwareChannelUpstreamHandler.java:36)
   at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
   at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
   at org.jboss.netty.handler.timeout.IdleStateHandler.messageReceived(IdleStateHandler.java:294)
   at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
   at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
   at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
   at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
   at org.jboss.netty.handler.codec.oneone.OneToOneDecoder.handleUpstream(OneToOneDecoder.java:70)
   at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
   at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
   at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
   at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462)
   at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443)
   at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
   at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
   at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
   at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
   at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
   at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
   at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
   at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
   at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318)
   at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
   at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
   at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
   at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
   at java.lang.Thread.run(Thread.java:745)
Caused by: com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout during read query at consistency QUORUM (2 responses were required but only 0 replica responded)
   at com.datastax.driver.core.Responses$Error$1.decode(Responses.java:61)
   at com.datastax.driver.core.Responses$Error$1.decode(Responses.java:38)
   at com.datastax.driver.core.Message$ProtocolDecoder.decode(Message.java:168)
   at org.jboss.netty.handler.codec.oneone.OneToOneDecoder.handleUpstream(OneToOneDecoder.java:66)
   ... 21 common frames omitted

Before that happens, a lot of the other persistent actors (if not all) have correctly recovered.
This is against a very small cassandra cluster (3 nodes), the persistent actor in question is using snapshots and don't have a lot of messages to recover.
If I remove all those messages, along with the snapshot and the metadata, this actor starts correctly (well it was assumed), and the whole system starts correctly.
What could be the cause for this timeout?
What should I do to troubleshoot this problem (at the plugin level or cassandra level) ?
Note that this problem happened twice, after we got a cassandra node dying from OOM during compaction (troubleshooting in progress), and when the cassandra cluster is back up, I restart the actor system (and then it tries the recovery).
I'll try to simulate the request with tracing enabled to see what can be wrong.
Thanks for helping me.
Brice

... and a custom build of 0.4 journal of a couple of weeks ago ...

have you tried with the released version?
what changes have you made to the plugin?
how big are the snapshots you're writing to Cassandra?
what Cassandra version are you using?

The ReadTimeoutException comes from a static column read and @chbatey mentioned a static-column bug in Cassandra versions < 2.1.6 (see also README). Not sure if this is related, though. Any ideas @chbatey?

There's no changes to the plug-in, it's just a local build of master before you published 0.4 . I will of course try 0.4 as soon as I can. There's only one snapshot of several hundred bytes, and about 500 events to recover after the snapshot.
It's with Cassandra 2.1.9.
I'll try to simulate the requests to see what can be the problem, but I think it's some Cassandra configuration issue. I'll post my findings here.
Thanks!

This is probably not related to akka-persistence-cassandra but to our cassandra cluster.
Running the following query:
SELECT sequence_nr, used FROM messages WHERE
                persistence_id = 'session-SW' AND
                partition_nr = 0
                ORDER BY sequence_nr
                DESC LIMIT 1;

which maps to the findHighestSequenceNr in the recovery code, also times out when run on some node with consistency ONE.
Out of our 3 nodes cluster, only one is able to send back the response in time.
I have no idea why, though.

Right, seems to be related to the Cassandra cluster setup but I'm also not able at the moment to give a hint how to fix that problem. Closing this ticket then ...


Package-lock.json merge conflict when having multiple PRs to approve

After dependabot has found multiple npm packages that needs to be updated (I understand grouping is not yet supported) approving one of those PRs will work but that will invalidate all others due to conflict in package-lock.json.
Is there a way to alleviate this problem?

Automatic merge conflict resolution is a feature that would be available in the server component in the future.
With or without groups, the only way to resolve the merge conflicts is to rerun the pipeline/execution. The ruby script will check for PRs with merge conflicts and resolve them. Remember the merge status must be conflict. This can be triggered by attempting merge or restarting merge.


Upgrade drf-spectacular-sidecar to 2024.3.4

_ No description provided. _

hi @kiblik - in the future, will you please ensure PRs have a description?  I know it is revving a dependency's version, but it would be good to know reasoning, history, and effect it may have in the description in case we need to revisit. Tying it back to the issue and discussion would be good as well.


LiveView peer count is zero and peers list is empty

On the main LiveView page the peer count is always zero and the peers list is always empty even for a node is on Byron and where the block number is incrementing every 20 or so seconds.
My understanding is that this issue is independent of Byron/Shelley.
There is a separate Byron only problem that the Byron mempool stats are not being updated correctly. Since this is correct in Shelley and Bryon is about to be replaced fixing Byron is probably not a high priority.

Is this a bug that we must fix, @erikd, or simply an irritation?  Could you classify it please :)
I assume it hasn't been raised by the Pioneers?
I added the minorfix label for irritants

This might be fixed by changing this config setting to true.
"TraceBlockFetchDecisions": true

@AndrewWestberg I have that set to true already.

This is a bug!
If the configuration is set to LiveView and the rest of the settings are not correctly set for LiveView the program should either exit with a helpful error message or automatically set them so that LiveView works correctly.

Since LiveView is officially deprecated and will be removed from the node very soon, I'm closing this issue. Please check RTView, our new tool for real-time watching for Cardano nodes. You can open an issue here.


[incubator/sparkoperator] Adding securityContext parameter for sparkoperator

What this PR does / why we need it:
Adds securityContext param for sparkoperator chart to allow for the operator to conform to any necessary security requirements.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test

@whitlekx can you give an example of how you configure the securirycontext in a helm install command?

You would have to know what part of the security context you would want, but you could do a helm install . --set securityContext.runAsUser=1000, etc.

Yep!


Fix Broken Links

A number of the 'View in Clay' links I've come across have been broken...but the pattern looks predictable — as far as I can tell, we need to add v2. as a prefix, and they've changed from _ to - in their urls.
See Bar Chart's for example.
(Updated to include broken links across the site)

Referring page
UR
Int.
Ext.
Anchor and link

Liferay Design | Articles, Events, and Resources for the Open Source Design Communityliferay.design/lexicon/core-components/badges/
11
127
19
VIEW IN CLAYclayui.com/docs/components/badges.html404 NOT FOUND

Liferay Design | Articles, Events, and Resources for the Open Source Design Communityliferay.design/lexicon/core-components/icons/
11
127
24
VIEW IN CLAYclayui.com/docs/components/icons.html404 NOT FOUND

Liferay Design | Articles, Events, and Resources for the Open Source Design Communityliferay.design/lexicon/core-components/cards/cards-variation/
11
127
19
VIEW IN CLAYclayui.com/docs/components/cards.html404 NOT FOUND

Liferay Design | Articles, Events, and Resources for the Open Source Design Communityliferay.design/careers/latam/product-designer/
11
11
22
NOFOLLOWIn case we forgot anything, Seth Godin’s list should cover it :)seths.blog/2018/04/missing-from-your-job-office/404 NOT FOUND

Liferay Design | Articles, Events, and Resources for the Open Source Design Communityliferay.design/lexicon/core-components/forms/text-input-localizable/
10
107
19
VIEW IN CLAYclayui.com/docs/components/forms/text-input-localizable.html404 NOT FOUND

Liferay Design | Articles, Events, and Resources for the Open Source Design Communityliferay.design/lexicon/core-components/forms/radio-check-toggle/
10
127
19
VIEW IN CLAYclayui.com/docs/components/forms/radio-check-toggle.html404 NOT FOUND

Liferay Design | Articles, Events, and Resources for the Open Source Design Communityliferay.design/lexicon/core-components/toolbars/management-bar/
10
107
19
VIEW IN CLAYclayui.com/docs/components/toolbars/management-toolbar.html404 NOT FOUND

Liferay Design | Articles, Events, and Resources for the Open Source Design Communityliferay.design/lexicon/core-components/forms/multi-step-form-simplified/
10
127
19
VIEW IN CLAYclayui.com/docs/components/forms/multi-step-form-simplified.html404 NOT FOUND

Liferay Design | Articles, Events, and Resources for the Open Source Design Communityliferay.design/lexicon/core-components/dropdowns/
10
127
19
VIEW IN CLAYclayui.com/docs/components/dropdowns.html404 NOT FOUND

Liferay Design | Articles, Events, and Resources for the Open Source Design Communityliferay.design/lexicon/core-components/forms/text-input/
10
106
19
VIEW IN CLAYclayui.com/docs/components/forms/text-input.html

#
Done?
link
Link Text
Page where found
Server response

1
[ ]
https://www.liferay.com/404

https://liferay.design/articles/2019/increasing-our-ability-to-convert-prospects/
404

2
[ ]
https://assets-liferaydotdesign.wedeploy.io

https://liferay.design/articles/2019/netlify-vs-zeit-vs-github-pages/
bad host

3
[ ]
https://wedeploy.com/blog/discontinuing-wedeploy/

https://liferay.design/articles/2019/netlify-vs-zeit-vs-github-pages/
404

4
[ ]
https://help.figma.com/category/87-prototyping

https://liferay.design/articles/2019/how-to-use-any-clicker-with-figma-presentations/
404

5
[ ]
htttp://www.lexicondesign.io

https://liferay.design/articles/2018/year-one-retrospective-cj/
bad url

6
[ ]
https://www.radicalcandor.com/blog/tag/tip/

https://liferay.design/articles/2018/new-team-assemble/
404

7
[ ]
https://seths.blog/2018/04/missing-from-your-job-office/

https://liferay.design/careers/latam/product-designer/
404

8
[ ]
http://www.terremoto.net/pv7

https://liferay.design/events/tramontana-presentation-sep-2019/
404

9
[ ]
https://liferay.design/team/jeong-christopher

404

10
[ ]
https://www.wallpaper.com/]

https://liferay.design/team/pires-felipe/
404

11
[ ]
https://help.figma.com/article/47-sharing-files-and-projects

https://liferay.design/handbook/tools/figma/
404

12
[ ]
slack://user

https://liferay.design/handbook/tools/github/introduction/
bad url

13
[ ]
https://liferay.design/handbook/work/introduction

404

14
[ ]
https://www.uie.com/brainsparks/2011/10/27/moving-from-critical-review-to-critique/

https://liferay.design/handbook/collaborate/locally/critique/
404

15
[ ]
https://liferay.design/lexicon/news/updates

404

16
[ ]
https://clayui.com/docs/layout/grid.html

https://liferay.design/lexicon/foundations/grid/
404

17
[ ]
https://liferay.design/team/balbas-cassandra

https://liferay.design/articles/2018/81-days-of-liferay/
404

18
[ ]
https://liferay.design/team/wood-jon/iempty.tooliphone.net

404

19
[ ]
https://liferay.design/articles/2019/updates-to-rotisserie

https://liferay.design/handbook/collaborate/locally/forum/
404

20
[ ]
https://liferay.design/handbook/grow/transversal-skills

https://liferay.design/handbook/grow/introduction/
404

21
[ ]
https://liferay.design/handbook/grow/product-design/introduction

https://liferay.design/handbook/grow/introduction/
404

22
[ ]
https://liferay.design/handbook/grow/transversal-skills/introduction

https://liferay.design/handbook/grow/career-paths/evaluations/
404

23
[ ]
https://liferay.design/handbook/grow/transversal-skills/excellence

https://liferay.design/handbook/grow/core-skills/
404

24
[ ]
https://liferay.design/handbook/grow/transversal-skills/collaboration

https://liferay.design/handbook/grow/core-skills/
404

25
[ ]
https://liferay.design/handbook/grow/transversal-skills/impact

https://liferay.design/handbook/grow/core-skills/
404

26
[ ]
https://liferay.design/handbook/grow/transversal-skills/advocacy

https://liferay.design/handbook/grow/core-skills/
404

27
[ ]
https://liferay.design/handbook/grow/transversal-skills/influence

https://liferay.design/handbook/grow/core-skills/
404

28
[ ]
https://liferay.design/handbook/grow/communication-design/strategy

https://liferay.design/handbook/grow/communication-design/
404

29
[ ]
https://liferay.design/handbook/grow/communication-design/environmental

https://liferay.design/handbook/grow/communication-design/
404

30
[ ]
https://liferay.design/handbook/grow/communication-design/production

https://liferay.design/handbook/grow/communication-design/
404

31
[ ]
https://liferay.design/handbook/grow/communication-design/brand-identity

https://liferay.design/handbook/grow/communication-design/
404

32
[ ]
https://liferay.design/handbook/grow/communication-design/media

https://liferay.design/handbook/grow/communication-design/
404

33
[ ]
https://liferay.design/handbook/grow/product-design/strategy

https://liferay.design/handbook/grow/product-design/
404

34
[ ]
https://liferay.design/handbook/grow/product-design/research

https://liferay.design/handbook/grow/product-design/
404

35
[ ]
https://liferay.design/handbook/grow/product-design/interaction

https://liferay.design/handbook/grow/product-design/
404

36
[ ]
https://liferay.design/handbook/grow/product-design/visual

https://liferay.design/handbook/grow/product-design/
404

37
[ ]
https://liferay.design/handbook/grow/product-design/engineering

https://liferay.design/handbook/grow/product-design/
404

38
[ ]
https://liferay.design/pull-requests

https://liferay.design/handbook/contribute/issues/
404

39
[ ]
https://liferay.design/principles/Am I using the correct affordances to solve the problem?

404

40
[ ]
https://clayui.com/docs/components/badges.html

https://liferay.design/lexicon/core-components/badges/
404

41
[ ]
https://clayui.com/docs/components/cards.html

https://liferay.design/lexicon/core-components/cards/
404

42
[ ]
https://clayui.com/docs/components/charts/basic/bar_chart.html

https://liferay.design/lexicon/core-components/charts/chart-bar/
404

43
[ ]
https://clayui.com/docs/components/charts/basic/donut_chart.html

https://liferay.design/lexicon/core-components/charts/chart-doughnut/
404

44
[ ]
https://clayui.com/docs/components/charts/advanced/predictive-forecasting.html

https://liferay.design/lexicon/core-components/charts/chart-forecast/
404

45
[ ]
https://clayui.com/docs/components/charts/basic/pie_chart.html

https://liferay.design/lexicon/core-components/charts/chart-pie/
404

46
[ ]
https://clayui.com/docs/components/dataset-display.html

https://liferay.design/lexicon/core-components/dataset-display/
404

47
[ ]
https://clayui.com/docs/components/dropdowns.html

https://liferay.design/lexicon/core-components/dropdowns/
404

48
[ ]
https://clayui.com/docs/components/forms/form-elements.html

https://liferay.design/lexicon/core-components/forms/
404

49
[ ]
https://clayui.com/docs/components/forms/forms-hierarchy.html

https://liferay.design/lexicon/core-components/forms/forms-hierarchy/
404

50
[ ]
https://clayui.com/docs/components/forms/forms-navigation.html

https://liferay.design/lexicon/core-components/forms/forms-navigation/
404

51
[ ]
https://clayui.com/docs/components/forms/radio-check-toggle.html

https://liferay.design/lexicon/core-components/forms/radio-check-toggle/
404

52
[ ]
https://clayui.com/docs/components/forms/multi-step-form.html

https://liferay.design/lexicon/core-components/forms/multi-step-form/
404

53
[ ]
https://clayui.com/docs/components/forms/multi-step-form-simplified.html

https://liferay.design/lexicon/core-components/forms/multi-step-form-simplified/
404

54
[ ]
https://clayui.com/docs/components/forms/selector.html

https://liferay.design/lexicon/core-components/forms/selector/
404

55
[ ]
https://clayui.com/docs/components/forms/text-input.html

https://liferay.design/lexicon/core-components/forms/text-input/
404

56
[ ]
https://clayui.com/docs/components/forms/text-input-group.html

https://liferay.design/lexicon/core-components/forms/text-input-group/
404

57
[ ]
https://clayui.com/docs/components/forms/text-input-localizable.html

https://liferay.design/lexicon/core-components/forms/text-input-localizable/
404

58
[ ]
https://clayui.com/docs/components/forms/text-input-variations.html

https://liferay.design/lexicon/core-components/forms/text-input-variations/
404

59
[ ]
https://clayui.com/docs/components/icons.html

https://liferay.design/lexicon/core-components/icons/
404

60
[ ]
https://clayui.com/docs/components/labels.html

https://liferay.design/lexicon/core-components/labels/
404

61
[ ]
https://clayui.com/docs/components/modals.html

https://liferay.design/lexicon/core-components/modals/
404

62
[ ]
https://clayui.com/docs/components/navigation/navbar.html

https://liferay.design/lexicon/core-components/navigation/horizontal-nav/
404

63
[ ]
https://clayui.com/docs/components/popovers.html

https://liferay.design/lexicon/core-components/popovers-tooltips/
404

64
[ ]
https://clayui.com/docs/components/progress-bars.html

https://liferay.design/lexicon/core-components/progress-bars/
404

65
[ ]
https://clayui.com/docs/components/stickers.html

https://liferay.design/lexicon/core-components/stickers/
404

66
[ ]
https://clayui.com/docs/components/table/table.html

https://liferay.design/lexicon/core-components/table/
404

67
[ ]
https://clayui.com/docs/css-framework/satellites/timelines.html

https://liferay.design/lexicon/core-components/timelines/
404

68
[ ]
https://clayui.com/docs/components/toolbars/management-toolbar.html

https://liferay.design/lexicon/core-components/toolbars/management-bar/
404

69
[ ]
https://clayui.com/docs/css-framework/satellites/navigation/header.html

https://liferay.design/lexicon/satellite-components/navigation/control-bar/
404

70
[ ]
https://clayui.com/docs/components/sidebar/info-panel.html

https://liferay.design/lexicon/satellite-components/sidebar/infopanel/
404

71
[ ]
https://github.com/liferay-design/lexicon/issues

404

72
[ ]
https://liferay.design/articles/2019/gestalt-principles/

https://liferay.design/articles/best-practices/measured-vs-optical-alignment/
404

73
[ ]
https://liferay.design/articles/ethics-in-design

https://liferay.design/articles/best-practices/dark-patterns/
404

74
[ ]
https://liferay.design/team/kolodziej-karolina

https://liferay.design/articles/best-practices/service-design/
404

75
[ ]
https://liferay.design/web/guest/home/-/loop/people/_patrick.pentz

https://liferay.design/articles/best-practices/illusion-of-completeness/
404

76
[ ]
https://liferay.design/tags/ResearchAndDevelopment

https://liferay.design/articles/best-practices/introducing-designbestpractices/
404

77
[ ]
https://liferay.design/tags/Design

https://liferay.design/articles/best-practices/introducing-designbestpractices/
404

78
[ ]
https://liferay.design/tags/VisualDesign

https://liferay.design/articles/best-practices/introducing-designbestpractices/
404

79
[ ]
https://liferay.design/tags/InsideEngineering

https://liferay.design/articles/best-practices/introducing-designbestpractices/
404

80
[ ]
https://liferay.design/tags/BugbeeFeedback

https://liferay.design/articles/best-practices/introducing-designbestpractices/
404

81
[ ]
https://liferay.design/lexicon/core-components/chart-stacked-bar

https://liferay.design/lexicon/core-components/charts/
404

82
[ ]
https://liferay.design/lexicon/core-components/navigation/breadcrub.html

https://liferay.design/lexicon/core-components/navigation/
404

83
[ ]
https://liferay.design/lexicon/core-components/navigation/.vertical-nav.html

https://liferay.design/lexicon/core-components/navigation/
404

84
[ ]
https://liferay.design/lexicon/core-components/navigation/.horizontal-nav.html

https://liferay.design/lexicon/core-components/navigation/
404

85
[ ]
https://liferay.design/lexicon/satellite-components/sites/buttons/assetToolbar

https://liferay.design/lexicon/satellite-components/sites/buttons/
404

86
[ ]
https://liferay.design/lexicon/satellite-components/sites/buttons/assetTitleBar

https://liferay.design/lexicon/satellite-components/sites/buttons/
404

87
[ ]
https://liferay.design/handbook/grow/career-paths/overview/

404

88
[ ]
https://liferay.design/lexicon-1/patterns/management_bar

https://liferay.design/lexicon-1/patterns/buttons/
404

89
[ ]
https://liferay.design/lexicon-1/patterns/list

https://liferay.design/lexicon-1/patterns/dataset-display/
404

90
[ ]
https://liferay.design/lexicon-1/patterns/card

https://liferay.design/lexicon-1/patterns/dataset-display/
404

Wow! that is a lot. I will fix it asap.
I've just fixed our links in claysite https://github.com/liferay/clay/pull/2930

I will fix our links to clay at least

I've fixed many of the clay links here https://github.com/liferay-design/liferay.design/pull/677
I will have to review more cases
@drakonux

fixed the rest in #780 — the ones for inactive teammates will require more thought, so will close this one out for now


Error HTTP/500: Internal Server Error. Object reference not set to an instance of an object.

Describe the problem
Error HTTP/500: Internal Server Error.
Object reference not set to an instance of an object.
Bravo version
1.0.6 (1.0.8693.18732)
Tabular model
Power BI Desktop, import mode
Power BI
power bi desktop
Steps to reproduce the behavior
No response
Additional context
No response
Screenshots

Anything else ?
Rastro ID: 00-c425e8b155455ce190df5764eccd7e96-15f4d019babcf74b-00

This error is definitely a bug, but unfortunately, we're unable to reproduce it, and we would need a PBIX that allows us to replicate the error. In the meantime we've implemented an update to better identify the location of the error. If you can, please update the program to the latest internal build and replicate the error. This will allow us to gather more details from the application telemetry.
To get the latest internal build, simply change the update channel from Stable to Dev in the Options/About panel, and then follow the provided link to download the installer.


Adding telemetry

If you want to ship this telemetry change, then you also need to bump up the extension version


Check for mistyped/invalid properties

Neither getGeocoder (extra parameter) nor the geocode function of the resulting object validate the input option. It is easy to mistake "apiKey" with "apikey" or add a completely unsupported parameter. It should not fail silently when property is not recognised.

i'm getting something wrong, don't know what:
Error: You must use https http adapter

To avoid this error https is now the default adapter

Yeah I had this error, too. It was working fine with http, and then I had cloned down my project again and suddenly I got that message. I changed to https, but now reverse geocoding doesn't work. Any way I can revert to http? I don't see why this change happened so suddenly for me when it was working fine

Hi you google geocoder ? and are you using api key or not ?

Yesterday I used an api key with http, and yes I was using google geocder. Today, I got the same message but removed the extra two arguments and it works fine with no api key.
geocoder = require('node-geocoder')('google')

instead of
geocoder = require('node-geocoder')('google','http', extra)

although when i changed 'http' to 'https' in the latter, i get no location.

Can I see a reverse call ?
On Wed, Aug 26, 2015 at 3:34 PM, Fahd Sheikh<EMAIL_ADDRESS>wrote:

Yesterday I used an api key with http, and yes I was using google geocder.
Today, I got the same message but removed the extra two arguments and it
works fine with no api key.
geocoder = require('node-geocoder')('google')
instead of
geocoder = require('node-geocoder')('google','http', extra)
although when i changed 'http' to 'https' in the latter, i get no location.
—
Reply to this email directly or view it on GitHub
https://github.com/nchaulet/node-geocoder/issues/78#issuecomment-135022680
.

--
Nicolas Chaulet (Développeur Web)
Contact :
tél : 07 62 16 39 38
mail<EMAIL_ADDRESS>twitter : @n_chaulet <https://twitter.com/n_chaulet>

I have released version 3.0 of node-geocoder and the deprecated call reverse(lat, lng) add be removed the good way to call reverse is now reverse({lat: *, lon: *})

this is what i was using for my api calls
router.post('/api/geocoder', function(req, res) {
  var latitude = req.body.latitude;
  var longitude = req.body.longitude;
  geocoder.reverse({
    lat: latitude,
    lon: longitude
  }, function(err, cityData) {
    if (err) {
      return res.json(500, err);
    } else {
      res.json(cityData);
    }
  });
});

and what error do you have ? are you using just an apiKey or Google Maps API for Work with a clientId ?

the error was only when i included an api key as part of the request for geocoder with https, resulting in no output..with no server apikey everything works fine now, so the error is gone on that part. I do have an api key for google maps in effect.

I was just testing this using an extra.apiKey and it work's fine
Geocoder('google', 'https', extra).reverse({lat: '45.7492277',
    lon: '4.8386345'}, function(err, results) {
    console.log(results);
    console.log(err)
});

you still have the error ?


e2e test case for health probe annotations

Checklist

[x] The title of the PR is clear and informative
[x] If applicable, the changes made in the PR have proper test coverage
[ ] Issues addressed by the PR are mentioned in the description followed by Fixes.

Description
E2E coverage on new health probe annotations including path, hostname, port, status codes

E2E Verification is PASS

E2E Verification is PASS


Does Microsoft FHIR server support the SMART On FHIR authorization workflows?

User story
As a FHIR server Dev and Ops team, I want to authenticate  the server with Crucible. Does Microsoft FHIR server support this feature?
The guild i am following is available in https://github.com/fhir-crucible/crucible.
Acceptance criteria

The server to be tested must declare their compliance with the SMART authorization specification by including security and extension elements in the conformance.. This is detailed in the  Conformance section of https://github.com/fhir-crucible/crucible. How do i achieve it on Azure. Please guide?

https://docs.microsoft.com/en-us/azure/healthcare-apis/use-smart-on-fhir-proxy

Thanks @hansenms for the quick response. Will check and get back on that.


x:net error compiling

What version of Go are you using (go version)?

[opc@webii ~]$ go version
go version go1.14.12 linux/amd64

Does this issue reproduce with the latest release?
 You need Go 1.15 or later. See https://golang.org/pkg/crypto/tls/#Dialer.
If you're stuck on an older Go version, pin older versions of libraries via modules.

Also, see https://golang.org/wiki/Questions.

As mvdan said, you may need to upgrade your Go version. But anyway its looks like Ian decided to keep 1.14 and below able to compile x/net, see #45946. Closing here.

Since this came up five times in 24 hours, I went ahead and patches golang.org/x/net so that it will work with versions of Go before 1.15.  That should fix this problem.  I still strongly encourage everyone to upgrade to a supported version of Go, and I do not promise that this will not break again in the future.


Error on "pnpm run dev" following the doc

Please provide the environment you discovered this bug in.
Following the Getting started doc i created a new analog projectn on a windows 11 machine, with the angular-v16-prerelease variant and with tailwind enabled.

I did a pnpm install that installed thoses dependencies :

Then i did a pnpm run dev.
Which area/package is the issue in?
Don't know / Other
Description
At first it seems to work great :

but on the second part of the script it fails with two errors:

"[plugin angular-compiler] Cannot read properties of undefined (reading 'allowJs')"
"[plugin angular-compiler] Invalid plugin execution order"

Please provide the exception or error you saw
X [ERROR] [plugin angular-compiler] Cannot read properties of undefined (reading 'allowJs')

    node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0/node_modules/@analogjs/vite-plugin-angular/src/lib/compiler-plugin.js:134:62:
      134 │                     const { affectedFiles, compilerOptions: { allowJs }, } = yield compilation.initialize(pluginOptions.tsconf...
          ╵                                                               ^

    at C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0\node_modules\@analogjs\vite-plugin-angular\src\lib\compiler-plugin.js:134:63
    at Generator.next (<anonymous>)
    at fulfilled (C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\tslib@2.4.0\node_modules\tslib\tslib.js:115:62)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

  This error came from the "onStart" callback registered here:

    node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0/node_modules/@analogjs/vite-plugin-angular/src/lib/compiler-plugin.js:114:22:
      114 │                 build.onStart(() => tslib_1.__awaiter(this, void 0, void 0, function* () {
          ╵                       ~~~~~~~

    at C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0\node_modules\@analogjs\vite-plugin-angular\src\lib\compiler-plugin.js:114:23
    at Generator.next (<anonymous>)
    at fulfilled (C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\tslib@2.4.0\node_modules\tslib\tslib.js:115:62)

X [ERROR] [plugin angular-compiler] Invalid plugin execution order

    node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0/node_modules/@analogjs/vite-plugin-angular/src/lib/compiler-plugin.js:183:27:
      183 │                     assert.ok(fileEmitter, 'Invalid plugin execution order');
          ╵                            ^

    at C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0\node_modules\@analogjs\vite-plugin-angular\src\lib\compiler-plugin.js:183:28
    at Generator.next (<anonymous>)
    at C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\tslib@2.4.0\node_modules\tslib\tslib.js:118:75
    at new Promise (<anonymous>)
    at Object.__awaiter (C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\tslib@2.4.0\node_modules\tslib\tslib.js:114:16)
    at C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0\node_modules\@analogjs\vite-plugin-angular\src\lib\compiler-plugin.js:181:38
    at requestCallbacks.on-load (C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\esbuild@0.16.17\node_modules\esbuild\lib\main.js:1426:28)
    at handleRequest (C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\esbuild@0.16.17\node_modules\esbuild\lib\main.js:727:19)
    at handleIncomingPacket (C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\esbuild@0.16.17\node_modules\esbuild\lib\main.js:749:7)
    at Socket.readFromStdout (C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\esbuild@0.16.17\node_modules\esbuild\lib\main.js:677:7)

  This error came from the "onLoad" callback registered here:

    node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0/node_modules/@analogjs/vite-plugin-angular/src/lib/compiler-plugin.js:179:22:
      179 │                 build.onLoad({
          ╵                       ~~~~~~

    at C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0\node_modules\@analogjs\vite-plugin-angular\src\lib\compiler-plugin.js:179:23
    at Generator.next (<anonymous>)
    at fulfilled (C:\Users\Anthony\Desktop\Projets\analog\analog-project\node_modules\.pnpm\tslib@2.4.0\node_modules\tslib\tslib.js:115:62)

  The plugin "angular-compiler" was triggered by this import

    html:C:/Users/Anthony/Desktop/Projets/analog/analog-project/index.html:1:7:
      1 │ import "/src/main.ts"
        ╵        ~~~~~~~~~~~~~~

Build failed with 2 errors:
node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0/node_modules/@analogjs/vite-plugin-angular/src/lib/compiler-plugin.js:134:62: ERROR: [plugin: angular-compiler] Cannot read properties of undefined (reading 'allowJs')
node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0/node_modules/@analogjs/vite-plugin-angular/src/lib/compiler-plugin.js:183:27: ERROR: [plugin: angular-compiler] Invalid plugin execution order

Other information
I did not edit any files from the installation, if you need any more informations feel free to ask me anything.
I would be willing to submit a PR to fix this issue

[ ] Yes
[ ] No

Having the same problem
D:\Projects>pnpm create analog
../.pnpm-store/v3/tmp/dlx-24924          |   +6 +
Packages are hard linked from the content-addressable store to the virtual store.
  Content-addressable store is at: D:\.pnpm-store\v3
  Virtual store is at:             ../.pnpm-store/v3/tmp/dlx-24924/node_modules/.pnpm
../.pnpm-store/v3/tmp/dlx-24924 ../.pnpm-store/v3/tmp/dlx-24924          | Progress: resolved 6, reused 6, downloaded 0, added 6, done: » analog-project
√ Project name: ... testing-analog-js
√ Select a template: » Analog
√ Select a variant: » angular-v16-prerelease
√ Would you like to add Tailwind to your project? ... yes

Scaffolding project in D:\Projects\testing-analog-js...

Initializing git repository:

Done.
 WARN  deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
 WARN  deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
 WARN  deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
 WARN  deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
 WARN  deprecated<EMAIL_ADDRESS>Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
Packages: +1332
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Packages are hard linked from the content-addressable store to the virtual store.
  Content-addressable store is at: D:\.pnpm-store\v3
  Virtual store is at:             node_modules/.pnpm
Progress: resolved 1324, reused 821, downloaded 430, added 1332, done
node_modules/.pnpm/@parcel+watcher@2.0.4/node_modules/@parcel/watcher: Running install script, done in 207ms
<EMAIL_ADDRESS>Running postinstall script, done in 352ms
<EMAIL_ADDRESS>Running postinstall script, done in 1.2s

dependencies:
+ @analogjs/content 0.2.0-beta.3
+ @analogjs/router 0.2.0-beta.3
+ @angular/animations 16.0.0-rc.0
+ @angular/common 16.0.0-rc.0
+ @angular/compiler 16.0.0-rc.0
+ @angular/core 16.0.0-rc.0
+ @angular/forms 16.0.0-rc.0
+ @angular/platform-browser 16.0.0-rc.0
+ @angular/platform-browser-dynamic 16.0.0-rc.0
+ @angular/platform-server 16.0.0-rc.0
+ @angular/router 16.0.0-rc.0
+ @nrwl/angular 15.7.0 (16.0.1 is available)
+ front-matter 4.0.2
+ marked 4.2.12 (4.3.0 is available)
+ prismjs 1.29.0
+ rxjs 7.5.6 (7.8.1 is available)
+ tslib 2.4.0 (2.5.0 is available)
+ zone.js 0.13.0

devDependencies:
+ @analogjs/platform 0.2.0-beta.3
+ @angular-devkit/build-angular 16.0.0-rc.0
+ @angular/cli 16.0.0-rc.0
+ @angular/compiler-cli 16.0.0-rc.0
+ @nrwl/vite 15.7.0 (16.0.1 is available)
+ autoprefixer 10.4.14
+ jsdom 20.0.0 (21.1.1 is available)
+ nx 15.7.0 (16.0.1 is available)
+ postcss 8.4.21 (8.4.23 is available)
+ tailwindcss 3.3.1 (3.3.2 is available)
+ typescript 5.0.2 (5.0.4 is available)
+ vite 4.0.3 (4.3.3 is available)
+ vitest 0.25.8 (0.30.1 is available)

 WARN  Issues with peer dependencies found
.
└─┬ @nrwl/vite 15.7.0
  └─┬ @nrwl/devkit 15.7.0
    └─┬ @phenomnomnominal/tsquery 4.1.1
      └── ✕ unmet peer typescript@"^3 || ^4": found 5.0.2

The integrity of 5409 files was checked. This might have caused installation to take longer.
Done in 31.4s

D:\Projects\testing-analog-js>pnpm run start

><EMAIL_ADDRESS>start D:\Projects\testing-analog-js
> pnpm run dev

><EMAIL_ADDRESS>dev D:\Projects\testing-analog-js
> ng serve

? Would you like to share pseudonymous usage data about this project with the Angular Team
at Google under Google's Privacy Policy at https://policies.google.com/privacy. For more
details and how to change this setting, see https://angular.io/analytics. No
Global setting: not set
Local setting: disabled
Effective status: disabled

The '@analogjs/platform' successfully started.
The server endpoints are accessible under the "/api" path.
  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
X [ERROR] [plugin angular-compiler] Cannot read properties of undefined (reading 'allowJs')

    node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0/node_modules/@analogjs/vite-plugin-angular/src/lib/compiler-plugin.js:134:62:
      134 │ ...         const { affectedFiles, compilerOptions: { allowJs }, } = yield compilation.initialize(plugin...
          ╵                                                       ^

    at D:\Projects\testing-analog-js\node_modules\.pnpm\@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0\node_modules\@analogjs\vite-plugin-angular\src\lib\compiler-plugin.js:134:63
    at Generator.next (<anonymous>)
    at fulfilled (D:\Projects\testing-analog-js\node_modules\.pnpm\tslib@2.4.0\node_modules\tslib\tslib.js:115:62)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

  This error came from the "onStart" callback registered here:

    node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0/node_modules/@analogjs/vite-plugin-angular/src/lib/compiler-plugin.js:114:22:
      114 │                 build.onStart(() => tslib_1.__awaiter(this, void 0, void 0, function* () {
          ╵                       ~~~~~~~

    at D:\Projects\testing-analog-js\node_modules\.pnpm\@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0\node_modules\@analogjs\vite-plugin-angular\src\lib\compiler-plugin.js:114:23
    at Generator.next (<anonymous>)
    at fulfilled (D:\Projects\testing-analog-js\node_modules\.pnpm\tslib@2.4.0\node_modules\tslib\tslib.js:115:62)

X [ERROR] [plugin angular-compiler] Invalid plugin execution order

    node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0/node_modules/@analogjs/vite-plugin-angular/src/lib/compiler-plugin.js:183:27:
      183 │                     assert.ok(fileEmitter, 'Invalid plugin execution order');
          ╵                            ^

    at D:\Projects\testing-analog-js\node_modules\.pnpm\@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0\node_modules\@analogjs\vite-plugin-angular\src\lib\compiler-plugin.js:183:28
    at Generator.next (<anonymous>)
    at D:\Projects\testing-analog-js\node_modules\.pnpm\tslib@2.4.0\node_modules\tslib\tslib.js:118:75
    at new Promise (<anonymous>)
    at Object.__awaiter (D:\Projects\testing-analog-js\node_modules\.pnpm\tslib@2.4.0\node_modules\tslib\tslib.js:114:16)
    at D:\Projects\testing-analog-js\node_modules\.pnpm\@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0\node_modules\@analogjs\vite-plugin-angular\src\lib\compiler-plugin.js:181:38
    at requestCallbacks.on-load (D:\Projects\testing-analog-js\node_modules\.pnpm\esbuild@0.16.17\node_modules\esbuild\lib\main.js:1426:28)
    at handleRequest (D:\Projects\testing-analog-js\node_modules\.pnpm\esbuild@0.16.17\node_modules\esbuild\lib\main.js:727:19)
    at handleIncomingPacket (D:\Projects\testing-analog-js\node_modules\.pnpm\esbuild@0.16.17\node_modules\esbuild\lib\main.js:749:7)
    at Socket.readFromStdout (D:\Projects\testing-analog-js\node_modules\.pnpm\esbuild@0.16.17\node_modules\esbuild\lib\main.js:677:7)

  This error came from the "onLoad" callback registered here:

    node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0/node_modules/@analogjs/vite-plugin-angular/src/lib/compiler-plugin.js:179:22:
      179 │                 build.onLoad({
          ╵                       ~~~~~~

    at D:\Projects\testing-analog-js\node_modules\.pnpm\@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0\node_modules\@analogjs\vite-plugin-angular\src\lib\compiler-plugin.js:179:23
    at Generator.next (<anonymous>)
    at fulfilled (D:\Projects\testing-analog-js\node_modules\.pnpm\tslib@2.4.0\node_modules\tslib\tslib.js:115:62)

  The plugin "angular-compiler" was triggered by this import

    html:D:/Projects/testing-analog-js/index.html:1:7:
      1 │ import "/src/main.ts"
        ╵        ~~~~~~~~~~~~~~

Build failed with 2 errors:
node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0/node_modules/@analogjs/vite-plugin-angular/src/lib/compiler-plugin.js:134:62: ERROR: [plugin: angular-compiler] Cannot read properties of undefined (reading 'allowJs')
node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@16.0.0-rc.0/node_modules/@analogjs/vite-plugin-angular/src/lib/compiler-plugin.js:183:27: ERROR: [plugin: angular-compiler] Invalid plugin execution order

I tried again to create a new application and this time i used npm instead of pnpm, and it worked, so the problem might be with pnpm

Agreed, tried the same with pnpm first then with npm. Pnpm's didn't succeed.
My running environment is:
Macbook: M1,
Pnpm: v8.3.1
Node: v18.16.0
Project configuration:

failed to load config from /Users/tmish/WebstormProjects/analog-project-pnpm/vite.config.ts
Error: Cannot find module '@angular-devkit/build-angular/src/builders/browser-esbuild/angular/aot-compilation'
Require stack:
- /Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular<EMAIL_ADDRESS>- /Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular<EMAIL_ADDRESS>- /Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular<EMAIL_ADDRESS>- /Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/@analogjs+platform@0.1.0-beta.22_@angular-devkit+build-angular<EMAIL_ADDRESS>- /Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/@analogjs+platform@0.1.0-beta.22_@angular-devkit+build-angular<EMAIL_ADDRESS>- /Users/tmish/WebstormProjects/analog-project-pnpm/vite.config.ts
- /Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/vite@4.0.3_@types+node@18.16.3_less<EMAIL_ADDRESS>    at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)
    at Module._load (node:internal/modules/cjs/loader:920:27)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular@15.0.0/node_modules/@analogjs/vite-plugin-angular/src/lib/compiler-plugin.js:18:27)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at _require.extensions.<computed> [as .js] (file:///Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/vite@4.0.3_@types+node@18.16.3_less@3.12.2_stylus@0.55.0/node_modules/vite/dist/node/chunks/dep-0bae2027.js:62080:17)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular<EMAIL_ADDRESS>    '/Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular<EMAIL_ADDRESS>    '/Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/@analogjs+vite-plugin-angular@0.2.0-beta.3_@angular-devkit+build-angular<EMAIL_ADDRESS>    '/Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/@analogjs+platform@0.1.0-beta.22_@angular-devkit+build-angular<EMAIL_ADDRESS>    '/Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/@analogjs+platform@0.1.0-beta.22_@angular-devkit+build-angular<EMAIL_ADDRESS>    '/Users/tmish/WebstormProjects/analog-project-pnpm/vite.config.ts',
    '/Users/tmish/WebstormProjects/analog-project-pnpm/node_modules/.pnpm/vite@4.0.3_@types+node@18.16.3_less<EMAIL_ADDRESS>  ]
}

After resolving of #344 when I create a new project with pnpm and Angular v15 I get this error when I execute "pnpm run dev"
An unhandled exception occurred: Package subpath './package.json' is not defined by "exports" in<EMAIL_ADDRESS>See "/private/var/folders/xc/k1zpqxbs0313j2zvqngz_5p80000gn/T/ng-MGjmVe/angular-errors.log" for further details.

Tried the getting started docs this weekend (via npm run dev) and the demo app is not even working (clicking button does nothing), with this showing up on the console:
caught SyntaxError: The requested module '/node_modules/.vite/deps/@angular_core.js?v=f9aba494' does not provide an export named 'assertInInjectionContext' (at analogjs-router.mjs?v=444d309e:1:161)

Is this an issue on my side? or the code just doesn't work for the last two months?

Tried the getting started docs this weekend (via npm run dev) and the demo app is not even working (clicking button does nothing), with this showing up on the console:
caught SyntaxError: The requested module '/node_modules/.vite/deps/@angular_core.js?v=f9aba494' does not provide an export named 'assertInInjectionContext' (at analogjs-router.mjs?v=444d309e:1:161)

Is this an issue on my side? or is the getting started instruction outdated?

This was an issue when creating a new starter project with Angular v15. The issue has been resolved and will go out with the next release tomorrow

@sugihartolim what version of packages are you on? What did you use to generate the project?

I'm on Angular 15. Should i be using angular 16 instead?
using 'npm init analog' and 'npm create analog'  resulted in  "^0.2.0-beta.16", giving the errors i reported in the previous post.
using 'npm init analog@latest' resulted in "^0.2.0-beta.17",  giving the same errors on console.
On first compile, both versions also show this error message in a popup window:
Cannot read properties of undefined (reading 'getCurrentDirectory')
    at getRootDirs (file:///D:/PROJECTS/analog/node_modules/@angular/compiler-cli/bundles/chunk-ZCBRXUPO.js:78:20)
    at NgCompilerHost.wrap (file:///D:/PROJECTS/analog/node_modules/@angular/compiler-cli/bundles/chunk-M65TNV27.js:7460:22)
    at new NgtscProgram (file:///D:/PROJECTS/analog/node_modules/@angular/compiler-cli/bundles/chunk-M65TNV27.js:7538:32)
    at D:\PROJECTS\analog\node_modules\@analogjs\vite-plugin-angular\src\lib\angular-vite-plugin.js:350:36
    at Generator.next (<anonymous>)
    at D:\PROJECTS\analog\node_modules\tslib\tslib.js:167:75
    at new Promise (<anonymous>)
    at Object.__awaiter (D:\PROJECTS\analog\node_modules\tslib\tslib.js:163:16)
    at buildAndAnalyze (D:\PROJECTS\analog\node_modules\@analogjs\vite-plugin-angular\src\lib\angular-vite-plugin.js:348:24)
    at D:\PROJECTS\analog\node_modules\@analogjs\vite-plugin-angular\src\lib\angular-vite-plugin.js:115:31
Click outside or fix the code to dismiss.
You can also disable this overlay by setting server.hmr.overlay to false in vite.config.js.

You can these steps to get a working setup with pnpm.
To get initial setup

Run the new project command pnpm create analog@latest analog-app
cd analog-app
Create an .npmrc in the root of the project with resolution-mode=highest
Install the dependencies pnpm install
Run the command to serve the app pnpm run dev

To fix the pnpm build command

Install the destr package pnpm install destr --save-dev
Run the command to build the app pnpm build

To fix the pnpm test command

Install the @analogjs/vite-plugin-angular package pnpm install @analogjs/vite-plugin-angular --save-dev
Run the command to test the app pnpm test

We'll look at what we can do make this more seamless for pnpm

Getting error with pnpm, same steps with npm works fine:
An unhandled exception occurred: Package "@analogjs/platform" has no builders defined.
See "/private/var/folders/7h/j6zg943x2zz51t9j56sr6qn80000gn/T/ng-eBE4Mf/angular-errors.log" for further details.
 ELIFECYCLE  Command failed.

Logs:
 andrew@Andrews-MacBook-Air repos % pnpm create analog
.../Library/pnpm/store/v3/tmp/dlx-10461  | Progress: resolved 1, reused 0, downl.../Library/pnpm/store/v3/tmp/dlx-10461  | Progress: resolved 3, reused 2, downl.../Library/pnpm/store/v3/tmp/dlx-10461  | Progress: resolved 4, reused 2, downl.../Library/pnpm/store/v3/tmp/dlx-10461  |   +6 +
.../Library/pnpm/store/v3/tmp/dlx-10461  | Progress: resolved 4, reused 2, downlPackages are hard linked from the content-addressable store to the virtual store.
  Content-addressable store is at: /Users/andrew/Library/pnpm/store/v3
  Virtual store is at:             ../../Library/pnpm/store/v3/tmp/dlx-10461/node_modules/.pnpm
.../Library/pnpm/store/v3/tmp/dlx-10461  | Progress: resolved 4, reused 2, downl.../Library/pnpm/store/v3/tmp/dlx-10461  | Progress: resolved 6, reused 5, downloaded 1, added 6, done
✔ Project name: … example-app
✔ Select a template: › Analog
✔ Select a variant: › angular-v16
✔ Would you like to add Tailwind to your project? … yes

Scaffolding project in /Users/andrew/dev/repos/example-app...

Initializing git repository:

Done. Now run:

  cd example-app
  pnpm install
  pnpm run dev

andrew@Andrews-MacBook-Air repos %  cd example-app
andrew@Andrews-MacBook-Air example-app % pnpm i
 WARN  deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.
 WARN  deprecated<EMAIL_ADDRESS>this package has been renamed to ts-evaluator. Please install ts-evaluator instead
 WARN  deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
 WARN  deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-unicode-property-regex instead.
 WARN  deprecated<EMAIL_ADDRESS>Use your platform's native performance.now() and performance.timeOrigin.
 WARN  deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
Packages: +1575
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Packages are hard linked from the content-addressable store to the virtual store.
  Content-addressable store is at: /Users/andrew/Library/pnpm/store/v3
  Virtual store is at:             node_modules/.pnpm
Progress: resolved 1575, reused 1427, downloaded 56, added 1575, done
<EMAIL_ADDRESS>Running postinstall<EMAIL_ADDRESS>Running postinstall script, done in<EMAIL_ADDRESS>Running postinstall script, done<EMAIL_ADDRESS>Running postinstall script, done in 803ms

dependencies:
+ @analogjs/content 0.2.0 (0.2.11 is available)
+ @analogjs/router 0.2.0 (0.2.2 is available)
+ @angular/animations 16.2.0 (16.2.11 is available)
+ @angular/common 16.2.0 (16.2.11 is available)
+ @angular/compiler 16.2.0 (16.2.11 is available)
+ @angular/core 16.2.0 (16.2.11 is available)
+ @angular/forms 16.2.0 (16.2.11 is available)
+ @angular/platform-browser 16.2.0 (16.2.11 is available)
+ @angular/platform-browser-dynamic 16.2.0 (16.2.11 is available)
+ @angular/platform-server 16.2.0 (16.2.8 is available)
+ @angular/router 16.2.0 (16.2.11 is available)
+ @nx/angular 17.0.0 (17.0.2 is available)
+ front-matter 4.0.2
+ marked 5.0.2 (5.1.1 is available)
+ marked-gfm-heading-id 3.1.0
+ marked-highlight 2.0.1
+ mermaid 10.2.4 (10.3.1 is available)
+ prismjs 1.29.0
+ rxjs 7.5.6 (7.8.1 is available)
+ tslib 2.4.0 (2.6.2 is available)
+ zone.js 0.13.0 (0.14.1 is available)

devDependencies:
+ @analogjs/platform 0.2.0 (0.2.2 is available)
+ @angular-devkit/build-angular 16.2.0 (16.2.9 is available)
+ @angular/cli 16.2.0 (16.2.9 is available)
+ @angular/compiler-cli 16.2.0 (16.2.11 is available)
+ @nx/vite 16.8.1
+ autoprefixer 10.4.14 (10.4.16 is available)
+ jsdom 22.1.0
+ nx 17.0.0 (17.0.2 is available)
+ postcss 8.4.21 (8.4.31 is available)
+ tailwindcss 3.3.1 (3.3.3 is available)
+ typescript 5.0.2 (5.2.2 is available)
+ vite 4.4.8 (4.5.0 is available)
+ vitest 0.32.0 (0.34.6 is available)

The integrity of 3304 files was checked. This might have caused installation to take longer.
Done in 30.3s
andrew@Andrews-MacBook-Air example-app % pnpm dev

><EMAIL_ADDRESS>dev /Users/andrew/dev/repos/example-app
> ng serve

pnpm should work out of the box now with Analog 1.0


import torch2trt_dynamic :plugin not found.

When I try to eval the model in pkg_suage.py, I found:

when I check the problem:

what should I do
Environment:

OS: Ubuntu 20.04
GPU: RTX 3080
CUDA Version 11.3

oh i forgot Install amirstan_plugin !!!


Display Ad Makers

Hi,
Is there a way to display the ad markers in the video timeline like the image below,
or just function to return the list of time offsets for all available ads in a vmap list.

To get array of time offsets(cue points):
var cuePoints = player.ima.getAdsManager().getCuePoints(); // It may also return an empty array
Note that preroll is represented by 0 and postroll is represented by -1.
All other values are represented in seconds.
Hope this helps!

Hello
I would like to see a more detailed example. Otherwise it is not entirely clear where, how and where to insert the code from the answer @onatcelmen   and it is also not entirely clear whether the task was solved
Thank

Hello I would like to see a more detailed example. Otherwise it is not entirely clear where, how and where to insert the code from the answer @onatcelmen and it is also not entirely clear whether the task was solved
Thank

This would be a more detailed example using videojs-markers
player.on('ads-manager', function (response) {
  const { adsManager } = response;
  const cuePoints = adsManager.getCuePoints(); // It may also return an empty array

  const markers = cuePoints.map(time => {
    return { time, text: "Advertisment" }
  })

  video.markers({ markers });
})


Draft: Updated the sources for the GAVs

This PR contains

Adding sources to the GAVs
New GAVs
Use the newly added sources
Update version

Fixes #11

wrong groupId, artifactid
add field for direct, or rebundled dependencies


Marketplace: Download Extension link not visible with Linux useragent

When I open https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint using the following user agent the Download Extension link is not visible:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

When I change my user agent to the following it becomes visible after refreshing the page and works as expected:
Mozilla/5.0 (MSIE 10.0; Windows NT 6.1; Trident/5.0)

This is frustrating as it is the documented way for downloading extensions for installing offline:
https://code.visualstudio.com/docs/editor/extension-gallery#_can-i-download-an-extension-directly-from-the-marketplace

@auchenberg Can you assign this to our friends at the marketplace?

@ramya-rao-a Done.

@SimonBoorer : thanks for reporting this. This has been fixed and will be deployed in coming weeks.


Issue: The parameters passed by the OpenAI function agent seem to have a problem.

System Info
langchain 0.0.200 in Debian 11
Who can help?
@hwchase17
Information

[ ] The official example notebooks/scripts
[X] My own modified scripts

Related Components

[ ] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[X] Agents / Agent Executors
[ ] Tools / Toolkits
[X] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
Pydantic Model:
class SortCondition(BaseModel):
    field: str = Field(description="Field name")
    order: str = Field(description="Sort order", enum=["desc", "asc"])

class RecordQueryCondition(BaseModel):
    datasheet_id: str = Field(description="The ID of the datasheet to retrieve records from.")
    filter_condition: Optional[Dict[str, str]] = Field(
        description="""
            Find records that meet specific conditions.
            This object should contain a key-value pair where the key is the field name and the value is the lookup value. For instance: {"title": "test"}.
            """
    )
    sort_condition: Optional[List[SortCondition]] = Field(min_items=1,
        description="Sort returned records by specific field"
    )
    maxRecords_condition: Optional[int] = Field(
        description="Limit the number of returned values."
    )

OpenAI return parameters:
{
    "datasheet_id": "dsti6VpNpuKQpHVSnh",
    "sort_condition": [
        {
            "field": "Timestamp",
            "direction": "desc" # error key!
        }
    ],
    "maxRecords_condition": 1
}

So, LangChain raise a error:
ValidationError: 1 validation error for RecordQueryCondition
sort_condition -> 0 -> order
field required (type=value_error.missing)
This is source code: https://github.com/xukecheng/APITable-LLMs-Enhancement-Experiments/blob/main/apitable_langchain_function.ipynb
Expected behavior
I use the OpenAI API to define functions, so it will work properly: https://github.com/xukecheng/APITable-LLMs-Enhancement-Experiments/blob/main/apitable_openai_function.ipynb

Fixed by https://github.com/xukecheng/APITable-LLMs-Enhancement-Experiments/commit/2f8048270cca0fa2a8e29968e063ca8c0f38f91a


Our setup process is broken. :-(

I tried for an hour to fix it on the weekend, and couldn't.
I don't recall if 14.04 still worked, but I couldn't get the Docker command working on 15.10.
(This is one reason why progress on #159 is so slow; I don't know how to dig us back out.)

Lucas, can you tell me which branch and command you were running?
Currently the "right" way is to use the data branch sitting in my Pull Request and running:
sudo docker rm -f badssl | true && ;2Cmake docker && sudo docker run -ti -p 80:80 -p 443:443 --name badssl badssl

If I recall master doesn't work very well right now.

@lgarron I checked on this today and you're right. An update in one of the Jekyll dependencies broke Jekyll on Ubuntu:14.04 since it's only running Ruby 2.0. :(

We could select a new base image if wanted.

I tried moving to 15.10, but had trouble getting the dependencies working. Howzabout 16.04? :-P

I thin 16.04 is preferable to 15.10. Want me to work on this migration?

If you could get the Docker command working on Ubuntu 16.04, that would be awesome! I'm blocked on my work here unless I can get that working.

I confirmed 16.04 supports Ruby 2.3 which will work. Will make a PR in the next week!

Thanks to our new cert generation (b02f505f02c31c937f9e69751956bd647ebdb941) and improvements in Docker, this is now much smoother. We have a bit to go, though.

19d2ace3fb47f810436e4a40d478e9f7fd9906bd is not perfect, but I think we're at the point where testing and deployment is not fragile anymore.


Nudge not respecting requiredInstallationDate

My end-users were recently bombarded with an unintentionally aggressive Nudge recently. After rolling back the changes and doing some testing, I noticed that requiredInstallationDate wasn't being honored by Nudge, so it was behaving as aggressively as possible. The screenshots below illustrate this

This is a configuration issue and not a Nudge issue. Please go to the #nudge-jamf channel on the macadmins slack to figure out what is happening.

I'm pretty sure I know what your issue is. There should not be a - between the date and T
You have 2022-08-08-T00:00:00Z which should be 2022-08-08T00:00:00Z
See: https://github.com/macadmins/nudge/blob/main/Example Assets/com.github.macadmins.Nudge.mobileconfig#L88


current_user_saved_albums() not working

hello all,
when I execute
results =  sp.current_user_saved_albums()
I get the error
AttributeError: 'Spotify' object has no attribute 'current_user_saved_albums'
Contrary sp.current_user_saved_tracks() works fine. Does anyone has an idea why?
Thanks for any help

I need to appologise. I got it working. Somehow the installation wieth easy_install dind't really work or I did somthing wrong. I downloaded the package now directly from github and now eherything works just fine.
Thanks for th nice package.


[BUG]: Data in ES indexes are faulty and not consistent with RDBMS

Describe the bug
ElasticSearch indexes will be out of sync with RDBMS due to usage of multiple Kafka topics. Not all of them are being updated in the Indexer.

Reindexing behavior has to be implemented properly.  Reindexing has to be time bound and implemented with a base ES backup in place. Design document is here.
There are three pipelines that write data to ES indices:

Service->Indexer->ES
Service->Transformer->Indexer->ES
Service->Analytics->Indexer->ES

All three are used in some combination and they all overwrite the same index. This is problematic as changes to the DPG indices might cause problems with the solutions layer etc..Separation of indices for dashboarding vs. raw indices as emitted by the services needs to be in place.

A listing of all topics, publishers, consumers and indices is available here. Some topics are being ignored and not used to update Indexes. This can lead to inconsistent data and therefore, problematic reports and dashboards.

Expected behavior
Whenever RDBMS data changes, it should be emitted to a relevant topic; This should then be used to update all the relevant ES indices - wherever the service data is being used.
CC: @atulgupta2024 @devarajd94 @suresh12

@subhashini-egov @manimaarans as part of this fix,

we are sending the complete object to a separate kafka topic for indexer in addition to partial data to persister kafka topic
and consuming that in transformer if we need some change in object before sending to indexer
for others we are directly consuming in indexer
added indexer file for needed topics

Hi @Ramu-kandimalla  @rajeshcherukumalli,
Verified the cases transactions, all are working fine in dpg-dev environment. Verified the transaction logs using the below commands
--kubectl logs svc/transformer -n egov | grep KL-000294-2024
Below are verified transactions,

E-Filing
Join a case
Hearings
Orders
Submissions
Tasks

Hi @subhashini-egov  , The ticket is verified in UAT environment and working as expected .


Still consider install plugindir in bare mode

:notebook_with_decorative_cover: Description
The contents of the install dir should be considered as vendored. In case of relocatable installations that means the path will not contain unintentional plugins. In case of non-relocatable we don't support running VAST from any place that is not the install location.
We should also look for plugins in the install plugindir last, after the locations set in the runtime configurations.
No changelog entry because --bare-mode is an undocumented development feature in the first place.

I think the install plugin dir should still have a higher precedence than the user-specified plugin dirs, i.e., moved above the bare mode check rather than below it.

Doesn't that make it unnecessarily complicated to load a modified version of a plugin that is placed somewhere outside the installed location? I.e. If a plugin is installed in both /custom and /vast/install I would think the user wants to load the custom one.


Incompatible with Kubernetes v1.26

Probably broke some time earlier, but 🤷.  Transcoder pods get created, but the client throws an error, then dies b/c PMS doesn't populate the session directory (as the shim errored out).

Anyone waiting on this merge can just point kubePlex.image to docker.io/cerebus2/kube-plex-shim:0.0.0 and helm update.


AttributeError: module 'tensorflow.contrib.learn' has no attribute 'TensorFlowEstimator'

Hello, I can't figure out why has no attribute.
Using TensorFlow0.12

Hello, I am having the same problem with "no attribute 'TensorFlowEstimator'.
I am using tensorflow 0.12

@mike121 @everett780 did you find solution of this issue?

TensorFlowEstimator in 0.12.1 now has name Estimator see this
if you will see error

TypeError: init() got an unexpected keyword argument 'optimizer'

you can just remove it
optimizer: An instance of tf.Optimizer used to train the model. If None, will use an Adagrad optimizer.

https://github.com/tensorflow/tensorflow/issues/6303
AttributeError: 'module' object has no attribute 'TensorFlowEstimator'
regressor = skflow.Estimator(model_fn=lstm_model(TIMESTEPS, RNN_LAYERS, DENSE_LAYERS))

@qwertmax Do you go through this code? There are several TypeError in this code. Could you give me some advice?

@DylanCheung if I can I'll be happy to help

@qwertmax +1 !

@qwertmax @DylanCheung
I might have (but this is unlikely) gotten a bit further down the road on solving the above issues. Feel free to try the code in my repository; https://github.com/pusj/LSTM-Time-Series-Analysis-using-Tensorflow
...and, feel free to comment on the two issues I've added

@qwertmax @pusj Hi, thank you all very much.
Here is something I am going to share you.
https://github.com/BinRoot/TensorFlow-Book/tree/master/ch10_rnn
Hopefully, it will give an inspiration.
<EMAIL_ADDRESS>this is my email address.
I am working on time series data prediction now.
I wish that we could discuss further.

@DylanCheung , thanks for your initiative! I'd be happy to discuss this further. Thank you for the link, did you have a chance to look at my contribution at https://github.com/pusj/LSTM-Time-Series-Analysis-using-Tensorflow ?

Hi can I have the code for supporting to the uploaded csv file (realMarketPriceDataPT.csv)  ?

it's there.


DataError: Failed to read large IndexedDB value

Hello,
I can't use exilence anymore
DataError: Failed to read large IndexedDB value
what to do?
Thank you for your reply

Please file the issue on exilence. I cannot know by looking at error messages from another application.


[Request] Overlay it over the urlbar or just below it.

I'm attempting to bring classic features back to Mozilla, along with Aero design.

I don't think this is possible with the limitations of the current extensions API

What are the limitations? Can UC scripts do it then? If not, can we move it to a status bar at the bottom instead?

Also, is implementing a function to copy Urls on right clicking over them on megabar popup implementable? I invite you to contribute to my repo
https://github.com/clifford269/FrutigerFX

userChrome.css have more power than extensions to modify stuff outside of the window, but I am not sure how dynamic it can be to replicate the progress bar.

Yeah. UC can be given a go. I've implemented quite a few things that rely on them already.

I'm currently working on how such scripts work and the modules, etc. If you could help me get a headstart, it'd be great. Are you on discord?


Webpack v4.41.5 hangs on recursive re-export

Bug report

What is the current behavior?
When a module contains recursive re-export webpack silently hangs in what seems to be perpetual loop.
If the current behavior is a bug, please provide the steps to reproduce.
Add src/index.js and run webpack:
export * from "./index.js";
export const foo = "bar";

Notice that the command hangs forever. Attaching a debugger points to FlagDependencyExportsPlugin.

What is the expected behavior?
Version 4.41.4 seems to work fine and produces a valid bundle.
This might be related to #10332

Other relevant information:
webpack version: 4.41.5
Node.js version: v12.14.1
Operating System: Windows 10
Additional tools:

Can you try master?

I've applied a patch from #10344 and it seems to address it.


Better error if we cannot query head for sync

Context
I've run into the error: cannot query head for sync: Get \"http://unused.invalid/head\": protocol not supported multiple times and it's almost always that the topic is configured differently. Which the error does not mention.
Proposed change
Include a hint that the topic may be misconfigured in the error.

Codecov Report

Merging #115 (ef39c3c) into main (64d7a32) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #115   +/-   ##
=======================================
  Coverage   64.89%   64.89%
=======================================
  Files          21       21
  Lines        2034     2034
=======================================
  Hits         1320     1320
  Misses        550      550
  Partials      164      164

Impacted Files
Coverage Δ

subscriber.go
79.51% <100.00%> (ø)