Allow multiple containers and all for umount

Signed-off-by: TomSweeneyRedHat<EMAIL_ADDRESS>Allow the capability to umount one to n containers or to umount all mounted containers at once.  Based on the recent Buildah PR:  https://github.com/projectatomic/buildah/pull/825
Test output:
 podman mount cf65022366da
/var/lib/containers/storage/overlay/ddc2d608f62f3b3f8f71122335812dfe5a3ec28d4feec8dd0e63ed416948250e/merged
# podman mount 913228bb56b2
/var/lib/containers/storage/overlay/a2352119c4dd3ed83da832ce06d1f0f23623355a591b17dff50fc3b669377bd8/merged

# podman umount --all
913228bb56b27979414108dbe91a2c348cca480f6267fee592fb9556888bd6d9
cf65022366da87138803cb399130a6c1ac3c2ddd82f82b23190a5b602b631f60

# podman mount cf65022366da
/var/lib/containers/storage/overlay/ddc2d608f62f3b3f8f71122335812dfe5a3ec28d4feec8dd0e63ed416948250e/merged
# podman mount 913228bb56b2
/var/lib/containers/storage/overlay/a2352119c4dd3ed83da832ce06d1f0f23623355a591b17dff50fc3b669377bd8/merged

# podman umount cf65022366da 913228bb56b2
cf65022366da87138803cb399130a6c1ac3c2ddd82f82b23190a5b602b631f60
913228bb56b27979414108dbe91a2c348cca480f6267fee592fb9556888bd6d9

# podman mount cf65022366da
/var/lib/containers/storage/overlay/ddc2d608f62f3b3f8f71122335812dfe5a3ec28d4feec8dd0e63ed416948250e/merged
# podman mount 913228bb56b2
/var/lib/containers/storage/overlay/a2352119c4dd3ed83da832ce06d1f0f23623355a591b17dff50fc3b669377bd8/merged

# podman umount cf65022366da badd 913228bb56b2 not here
cf65022366da87138803cb399130a6c1ac3c2ddd82f82b23190a5b602b631f60
913228bb56b27979414108dbe91a2c348cca480f6267fee592fb9556888bd6d9
ERRO[0000] error unmounting container badd: no container with name or ID badd found: no such container
error unmounting container badd: no container with name or ID badd found: no such container
ERRO[0000] error unmounting container not: no container with name or ID not found: no such container
error unmounting container not: no container with name or ID not found: no such container
ERRO[0000] error unmounting container here: no container with name or ID here found: no such container
error unmounting container here: no container with name or ID here found: no such container

LGTM
@baude @mheon @umohnani8 @giuseppe @TomSweeneyRedHat PTAL

LGTM. Thanks @TomSweeneyRedHat !

My waffling for this and the one on Buildah is printing out the error lines like:
ERRO[0000] error unmounting container not: no container with name or ID not found: no such container

I'm thinking we might want drop the logrus.error calls, happy to hear other opinions.
Once this gets merged, I'll work on adding the multi container mounts, that too was recently added to Buildah.

Can you add a check to see if it is mounted before attempting an unmount?

if mounted, _ := ctr.Mounted(); mounted {
ctr.Unmont()
}

I'm a bit confused as to why we want this. Unmount all is going to fail for
running containers, and only really makes sense with podman mount, so I
don't know if I see much of a point to this.
It might also conflict with the mount sessions work I'd eventually like to
get merged.
On Wed, Jun 27, 2018, 14:12 Daniel J Walsh<EMAIL_ADDRESS>wrote:

if mounted, _ := ctr.Mounted(); mounted {
ctr.Unmont()
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/projectatomic/libpod/pull/1012#issuecomment-400779115,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHYHCPvlFdIHj0HtAF4EK9dnHHwbFC1Pks5uA8sJgaJpZM4U6Hp4
.

The root of this came from the Buildah test folks.  They just found it a lot easier to be able to remove the mounts from all the containers rather than specifying one at a time.  If I were able to add a check to see if the container was running and ignore it is so, would that be better?
I don't know if it helps or not with the session work, but I didn't remove the ability to remove one container at a time.

I'd feel a lot better if we only allowed containers that are not running to
be unmounted, sure.
I think we can avoid conflicts with sessions too, on second thought.
On Wed, Jun 27, 2018, 15:04 Tom Sweeney<EMAIL_ADDRESS>wrote:

The root of this came from the Buildah test folks. They just found it a
lot easier to be able to remove the mounts from all the containers rather
than specifying one at a time. If I were able to add a check to see if the
container was running and ignore it is so, would that be better?
I don't know if it helps or not with the session work, but I didn't remove
the ability to remove one container at a time.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/projectatomic/libpod/pull/1012#issuecomment-400794829,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHYHCPyVuqtuqzfbjPNqNVTQOtbPJiL1ks5uA9dEgaJpZM4U6Hp4
.

@TomSweeneyRedHat You had one extra logrus.Error, getting rid of that should fix it

Repushed.  I kept the logrus with the exception of the last one and trashed the write utility.  Error output now looks like:
# podman umount 6bc14f73db9f bad1 8c046b5cbfe0 bad2 772145f69401 bad3 cf65022366da
6bc14f73db9fee537724da299e76bf42610744464237007664a6faa7c114085b
8c046b5cbfe090391f562b02bff68e1705f954b42f7cec8640c757d1d6433c3f
ERRO[0000] error unmounting container bad1: no container with name or ID bad1 found: no such container
772145f69401b2cb9e56c5e36ddf2fa7e398791bdb210b4910f893e33a0e5014
ERRO[0000] error unmounting container bad2: no container with name or ID bad2 found: no such container
cf65022366da87138803cb399130a6c1ac3c2ddd82f82b23190a5b602b631f60
error unmounting container bad3: no container with name or ID bad3 found: no such container

The last error is doesn't look like the others, I think that's OK.  It does get the message across.

LGTM

LGTM

LGTM. Let's merge once tests green.

@rh-atomic-bot r=
@mheon When you want to merge on green, just do the above command.  Humu will block if a test fails, Then you don't have to remember to come back and merge it later.

@rh-atomic-bot retry

I love it when Homu chokes on a release day. Gives me the warm and fuzzies every time. Or maybe the warm part is the fever talking...


Rethink JSEnv implementation APIs

Notably AbstractNodeJSEnv and ExternalJSEnv can probably be improved. Notably use less inheritance.

Other things that can be improved, IMO:

Get rid of the synchronous APIs (jsRunner). All our JS envs support asynchronous runs. In general, it's always possible to implement an asynchronous API on top of a synchronous API anyway.
The arbitrary distinction between arguments given to {js,async,com}Runner and those given to their run/start methods. IMO all the arguments should go to the method in JSEnv, and that method should start immediately the runner. A JSRunner would always be running or stopped (but not yet-to-be-started).

IMO all the arguments should go to the method in JSEnv, and that method should start immediately the runner.

Not 100% convinced about that one. Can be hard if you need two runners that communicate with each other. Mainly because you can't get references to both without starting them (and messages already piling up).
An API like this is OK for apparently immutable things like Future.apply. But for things that have state (as in ComJSEnv.send) this can lead to very difficult setup sequences. Maybe we can add some final helper methods that do this?

How does the current scheme fare better for that use case? AFAICT, if you call send() before start(), you just block. You might just as well buffer your messages yourself if you have a use case of communicating between two runners.

Stuff to also add:

Expected thread safety guarantees.
Exact exception semantics (what get's thrown when, send after close, receive after close, send while close, receive while close).

I have given this quite some thought and think something like this would be sufficient:
trait JSEnv {
  val name: String // should really be stable -> val.

  def start(files: List[VirtualJSFile], console: JSConsole, logger: Logger): JSRun
}

trait JSRun {
  // Future completes if run completes.
  def future: Future[Unit]

  // Stops run without interrupting an operation. I.e. it inserts a `stop` operation on the event-loop.
  // Idempotent, async.
  def stop(): Unit

  // Forcefully stops the run. If the run is not stopped, will make run fail with error.
  // Idempotent, async.
  def kill(): Unit

  // Send a message to the JS end, async.
  // "Eventually throws" if the run is completed.
  def send(msg: String): Unit

  // Blocking receive. Throws if the run is completed but buffers incoming messages since completion.
  def receive(): String
  def receive(timeout: Duration): String

  // Immediate receive. "eventually throws" if the run is completed.
  def tryReceive(): Option[String]
}

Notes:

No "unstarted" state anymore (as you mentioned, indeed much cleaner).
No "close" concept anymore (was in practice always the same than stop). Note that JS-side will not be allowed to "close" anymore. It can just terminate in this case.
Com API is required: in practice any serious JSEnv needs to implement the Com API, otherwise it can't be used for testing.
"Eventually throws" means that if the run is completed and you call this method repeatedly at some point it will start throwing and always throw from there.

Could we make receive() methods non-blocking? Something like returning a Future[String]? Concurrent receive() calls would be put in a queue, so that they are first-come first-served. (gives good semantics, although in practice a reasonable user will always want to sequence their calls to receive()). The receive(timeout) would be unnecessary.
That would give us an API that we can potentially cross-compile one day.
Also, what is the purpose of tryReceive()?

tryReceive() receives a message if it does not need to block, otherwise returns None. If message reception fails, it throws, just like receive. Can be used to implement event-loop style code (useful if you need to interact with something that is not multithreaded).
The difficulty with receive(): Future[String] is essentially what happens in this case:
List.fill(5)(x.receive())

Now the JSEnv needs to retain a list of "requested receives", also getting ordering correct is hard. Essentially we'd need a reactive stream for this :-/
But I do see the appeal of us being able to cross-compile the API. How do other async APIs handle message interfaces? I'd really like to not go down the callback route here :S

What I mean by "getting ordering correct" is that if you want to receive messages in a loop (which is what you want most of the time), you need to be very careful for your calls to receive to be in a proper order such that incoming messages don't get reordered.
So to continue the example:
List.fill(5)(x.receive()).map(_.foreach(println))  // oops, I just nuked ordering :S

That's what I meant by the first-come first-served semantics in case of concurrent receive()s.
The only good solution is callback-based at the core. On top of that one can build reactive streams or Observables or things like that. But essentially it's a callback. And we definitely don't want to depend on some streaming library in the core, so I'd say callback.
The callback version also makes tryReceive() unnecessary, since as a user of the API, if you want a tryReceive(), you can build it yourself on top of the callback and some mutable state. There's no need to push the requirement to provide it to the JSRuns.

oops, I just nuked ordering :S

Yes, hence what I was saying about a "reasonable" consumer of the API, which should probably sequence calls to receive() in all cases.
This is a non-issue with a callback-based API, though.

Yeah, but a callback-based API is dangerous in JVM land for deadlocks and call-stack explosions, no? For example, is a callback allowed to call send on the same runner? Also, would you put the callback in the start call then?

hence what I was saying about a "reasonable" consumer of the API

I know. But with a future based API like this, a "reasonable" consumer of the API is strange to write:
def loop(): Unit = {
  // When and how do I abort this "loop"
  x.receive().onComplete { x => doStuff(x); loop() }
}

:-/ I need to think about this more...

Yeah, but a callback-based API is dangerous in JVM land for deadlocks and call-stack explosions, no?

I don't see why. Not any more than other solutions.

For example, is a callback allowed to call send on the same runner?

Yes, definitely. With lockless algorithms or reentrant locks, this shouldn't be a problem.

Also, would you put the callback in the start call then?

Probably.
I think we need two start methods anyway. One that enables Com and one that doesn't. It's orthogonal to this issue; we'll want a start without com for the run task and other stuff.

With lockless algorithms or reentrant locks, this shouldn't be a problem.

Just FTR: send and receive will not be lockless for all JSEnvs. For example the NodeJSEnv needs to write multiple things into a stream for a send. The only way to make this lockless is by adding more threads with a message queue. But fair enough about the re-entrant locks.

Not any more than other solutions.

I don't think this is entirely true. In a fully asynchronous solution with an execution pool, the call-stack gets freed and operations that can execute independently do execute independently. In a call-back based solution things might be tied together more than necessary (imagine two envs that mutually call each others send handler on receive. In that case there might be a thread holding locks for both envs. This wouldn't happen in a stream or future based solution).
Not sure either of them are relevant though :P

I think the problematic situation you describe can be avoided by specifying that x.send() must complete in a finite time even if x.onReceive does not. In practice this means that send() cannot call onReceive() itself. Instead it must make sure that the call to onReceive is queued up for asynchronous execution.

Instead it must make sure that the call to onReceive is queued up for asynchronous execution.

Yeah, a stream or future based solution would essentially ensure this. Maybe it is indeed sufficient if we just require this from the implementation.

I think we need two start methods anyway. One that enables Com and one that doesn't.

Fair enough. But do we have two different JSRun traits then? We can of course drop the send method (receive will be replaced by callback), but what about the stop method? stop is essentially only implementable with a com and usually only reasonable with a com (otherwise how do you know when to stop).
So we would have:
trait JSEnv {
  val name: String // should really be stable -> val.

  def start(files: List[VirtualJSFile], console: JSConsole, logger: Logger): JSRun

  def startWithCom(files: List[VirtualJSFile], onMessage: String => Unit,
    console: JSConsole, logger: Logger): JSComRun
}

trait JSRun {
  // Future completes if run completes.
  def future: Future[Unit]

  // Forcefully stops the run. If the run is not stopped, will make run fail with error.
  // Idempotent, async.
  def kill(): Unit
}

trait JSComRun extends JSRun {
  // Stops run without interrupting an operation. I.e. it inserts a `stop` operation on the event-loop.
  // Idempotent, async.
  def stop(): Unit

  // Send a message to the JS end, async.
  // "Eventually throws" if the run is completed.
  def send(msg: String): Unit
}

Was hoping to avoid having two JSRun traits but if we want a setup with and one without com it's probably unavoidable. It's still much simpler than what we have now.
Also: Any thought on the argument count? startWithCom has quite a lot of arguments :S
WDYT?

That looks good, I think.
Maybe you can bundle console and logger into a Config object. They are not essential parts of the API and they can have good defaults (console forwards to stdout, and logger is a NullLogger). That would reduce the number of arguments to startWithCom (and start) and would allow binary and source compatible improvements to those configuration things.

Two things are not fully done yet with this:

How to handle the event loop with non-com runs? I.e. what happens if the event loop is empty but stuff could be added.
How to handle modules / libraries / etc.

Other thing TODO on this: Provide a way to release resources of the runner (i.e. close or similar). That must be called by the user (see scala-js/scala-js-env-selenium#77).

Ok, I think we can go even simpler:
trait JSRun {
  // Future completes if run completes.
  def future: Future[Unit]

  // Stops the run and releases all the resources.
  // This *must* be called to "close" the runner.
  //
  // Whether or not this makes the run fail or not is up to the implementation.
  // However, in the following cases, calling `stop` may not fail the run:
  // - `future` is already completed when `stop` is called.
  // - This is a `JSComRun` and the event loop inside the VM is empty.
  // Idempotent, async.
  def stop(): Unit
}

trait JSComRun extends JSRun {
  // Send a message to the JS end, async.
  // "Eventually throws" if the run is completed.
  def send(msg: String): Unit
}

This solves the following:

How to handle the event loop with non-com runs
We use stop in sbt run by allowing some means of interruption by the user (^C, or maybe enter, depending on what is feasible). This is easy, since we do not redirect stdin to the VMs.

Provide a way to release resources of the runner
stop does this now.

We are left with module handling. Essentially we need to solve two problems:

How does the JSEnv know how it has to load stuff / prepare stuff for loading (i.e. do the files require each other internally, if yes, which one is the "main", or should it just include everything like <script>)? This depends on the module style of the SJS code.
How can generated code know how to load stuff (does it need to require, global scope, etc.). While this is a big concern for notably our test adapter, it might be better solved entirely outside of JSEnv.

Two questions:

Should we call stop close instead so that we can implement AutoCloseable?
Is it worth to specify send to throw? It might be easier for everybody to just say "never throws".

TODO at this point:

Answer questions above.
Figure out module stuff.
Clarify expected message delivery guarantees (ordered, exactly once, no intermittent message dropping, dropping messages at the "end of the run" is OK).

Just a quick update of where this is in my head:

stop should probably be called close.
send should not throw.
I do not believe that we can/want to solve the module mess with this. However, I'd like to find an interface that we can adjust to a better solution as we go forward. Since this is an interface that we expect others to implement this might be non-trivial. Ideas below.
Message delivery guarantees:

If p1 sends exactly m_1, ..., m_n and p2 receives m_k (k <= n) but not m_{k+1}, p2 must receive exactly m_1, ..., m_k in this order.
If p1 sends an infinite number of messages, p2 receives an infinite number of messages.

For module forward evolution, I am considering something like:
sealed trait Input {
  def filesToExplicitlyLoad: List[VirtualJSFile]
}

object Input {
  final case class Fileset(files: List[VirtualJSFile]) extends Input {
    def filesToExplicitlyLoad: List[VirtualJSFile]
  }
}

We could then later extend this to hold files that do not need to be explicitly loaded but available. The referring to loaded code is unsolved by this (and probably should remain unsolved, it's not the JSEnv's responsibility).

Developing further on this idea. We could have this:
/** Input files to a [[JSEnv]]
 *
 *  This trait is open to inheritance, however, we only provide compatibility guarantee
 *  for inheritance in patch versions. Minor versions may break code inheriting from
 *  this trait (by adding methods).
 *  Usage of the interface will retain full compatibility (i.e. methods will not go away).
 */
trait Input {
  /** Files to be explicitly loaded by the JSEnv into the global scope.
   *  How additional files needed by modules are loaded is deliberately unspecified
   *  by this method since, at the time of writing, we did not know how to do it.
   */
  def filesToLoad: List[VirtualJSFile]
}

And later, this might be evolved into:
trait Input {
  /** Files to be explicitly loaded by the JSEnv into the global scope.
   *  How additional files needed by modules are loaded is deliberately unspecified
   *  by this method since, at the time of writing, we did not know how to do it.
   */
  def filesToLoad: List[VirtualJSFile]

  def mainFile: VirtualJSFile
  def availableModules: List[VirtualJSFile with RelativeFile]
}

The one thing I do not at all like about this is that it completely fails to model that most of the time, whether module support is needed or not is almost a property of the JSEnv. So pretending that the JSEnv can do both, or that we can provide both (with the same files) is a lie. I don't like lies :-/

Maybe the Input with only filesToLoad should really be SimpleInput, that all JSEnvs are supposed to be able to deal with. And then later we add an unrelated ModuleEnabledInput, which can be consumed by subclasses of JSEnv that extend some ModuleEnabledJSEnv?

So this is essentially similar than what we had with async/com environments until we realized that really any serious environment needs to support both (or runtime failure is enough).
Now in this case it's actually the other way around: The JSEnvs really only support one style at the moment. Node.js does not really support non-module includes (and the efforts to export things in the top-level scope rather than object have shown this).
So in practice, it seems that developers chose one inclusion style and stick with it (or we encourage this by having a ModuleKind setting).
So currently we are in the state where at compile time, we can be agnostic of whether we are in a module or not (@JSExport works for both, @JSImport has a fallback). However, at link time, one has to make a decision and that is fine.
But that in turn means that it is probably not too much to ask from developers to use a JSEnv that supports the module style they are using. Probably in practice they already do that.
Now how to model this is another question :)

Indeed, that's a good point.
If a run-time failure is enough, then maybe declare the methods for all inclusion styles right in JSEnv, as concrete and throwing an UnsupportedOperationException. Then each JSEnv can choose to override the ones it supports. If we add one more in the future, it will be a new concrete method in a class, which is binary compatible.

Hmmm... In that case why not just make an ADT Input with a private constructor (so specifically not sealed). Prudent users will add a default clause in their implementations, others will just get a MatchError which is not that bad.
An ADT seems notably easier to deal with if we have to construct and pass inputs before we pass them to the JSEnv (think for example in the test adapter, but probably also in the sbt plugin).
So it would look something like this:
/** Input to a [[JSEnv]] */
abstract class Input private[scalajs] ()

object Input {
  /** The given files are to be loaded into the global scope in the order given. */
  final case class FilesToLoad(files: List[VirtualJSFile]) extends Input
}

For the time being, Node.js can support FilesToLoad with a comment saying that this is a lie. Once we can transition Node.js to a better scheme (with actual module support), we can still support FilesToLoad but warn or maybe even require to set an option. Alternatively, depending on the speed we can swtich, we might even fully drop support for FilesToLoad in Node.js (of course we will always be able to support FilesToLoad with 0 or 1 files :)).
WDYT?

Yes that makes sense. It looks good to me.

There is still one open point about how to handle stdin/stdout/stderr or JSConsole.
Things that are clear so far:

We should drop the JSConsole abstraction and use an stdin/stdout/stderr abstraction instead.
stderr should not go to the logger anymore (see #3206).
JSRun should not expose the streams, but they should be put in the Config for start.
The default should be the equivalent of java.util.ProcessBuilder#inheritIO.

Things that are unclear:

How to design the Config such that this does not put an unnecessary threading burden on the JSEnv implementation.

I'm afraid there seems to be no clean way of doing what we want to do for stream handling in JSEnvs (at least for external envs, which seems to be the majority). ProcessBuilder allows us to inherit IO, which would cover the default behavior. However, there is no way of specifying a stream to input. Further, we cannot put an arbitrary stream in non-blocking mode (only sockets support this IIUC), so processing the stream forwarding on a shared thread-pool is not an option either.
The options I can currently think of are (cons are in bullets):

Add a "output stream sink" to the config which is essentially a set once variable.

Config becomes mutable and cannot be shared.

Force external envs to spawn threads to forward IO in case a special stream is requested.

Threads are likely to cause performance penalties.
Config becomes mutable due to stream closing semantics.

Do not allow stream forwarding at all.

API very limited to SJS's use case.
We cannot add stream forwarding later in a backward compatible manner.
It will be hard to test JSEnvs if we cannot easily capture their output.

Expose the streams on JSRun, if inheritIO behavior (via Config?) was not triggered.

Not very streamlined usage.
Not type safe or a lot of path dependent type magic.

Always just expose the streams on JSRun let it be the callers problem.

Does not support SJS's use case which would be happy with inheritIO.
SJS will need to add threads on its end, likely causing performance penalties.

None of them are really good. @sjrd any ideas?

Have you considered the following variant of (1): have an option in the Config which is a callback, something like:
class Config(...) {
  ...
  def withOnPipeOpened((Option[InputStream], Option[InputStream]) => Unit): Config = ...
}

The JSRun that starts a process where either the stdout, the stderr or both are not inheritIO will invoke that callback with the two relevant streams given by Process.getInputStream() and getErrorStream().
That should prevent the Config from becoming mutable per se, although of course the event is likely tied to one particular invocation, but that's the caller's problem, if they should something else than inheritIO.

Fair enough. I guess that'll do. I wonder though if we need to make them optional.

Not necessarily, but then we cannot quite offer to support inheritIO for stdout while piping stderr, or vice versa.

Fair enough. I'll come up with something.


removed file command dependency, file -i behaviour is not consistent across the platforms

ls is fast enough but can be substituted with exa. #19

Hey @chshbh great work, and thanks for explaining to me how your PR works! I have a few changes I'd like to make. I hope you don't mind me pushing to your branch and then merging it--don't worry, you will get the credit for it.

Ah darn, I don't have permissions to push to your branch. Can you give them to me, please? https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork

Ah darn, I don't have permission to push to your branch. Can you give them to me, please? https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork

I think you can edit my commit.

Hey @chshbh , sorry I decided to just open my own PR and fix it because this bug was live and I didn't want people to not have a working file preview for too long.
I want to thank you again for filing the issue and writing this PR, which I based my fix off off! I gave you credit in the commit.


Add copy support

Is to possible to add 'copy' button to the code blocks?
I found examples here how to implement that

@WingLim Thank you for such a quick response!
But this button appears only on first code block entry and its doesn't copy anything

@WingLim Thank you for such a quick response!
But this button appears only on first code block entry and its doesn't copy anything

Can you show me the page of the bug you mention?

markdown
Open your terminal and run:
$ hugo new site blogg
$ git init

This will create a new hugo site and initialize git repository in it.
Then you have to choose a theme to use in your blog. There you can find list of themes.
Pick one, click on it and you'll see a button Download, click on it.
Click on green Code button, choose HTTPS and click copy button
Go to your project's folder
$ cd blogg

Add your theme as git submodule and to config.toml
$ git submodule add git@github.com:WingLim/hugo-tania.git themes/hugo-tania
$ echo theme = \"hugo-tania\" >> config.toml

Now you should be able to preview you site.
$ hugo serve

You will see output like
Web Server is available at http://localhost:1313/ (bind address <IP_ADDRESS>)

Open the address in your browser and you should see your landing web page.

I am using this theme in my blog, you can try to compile the file and see the problem
https://github.com/Friedrich42/murrr.space/blob/post/how-to-create-tech-blog/content/posts/how-to-create-a-tech-blog.md

This issue is because hugo only add .highlight class to codeblock like this:
```bash
$ hugo new site blogg
$ git init
```

The bash or any other language is required


Update fix_esri_polygon for fixed gdal

https://trac.osgeo.org/gdal/ticket/5538 has now been fixed, but fix_esri_polygon() throws an error with newer GDAL releases, because it assumes the passed geometry is a Polygon, not a MultiPolygon.

We have a trusty branch that deals with this: d62927d3 and expects that 1.11.2 of GDAL is installed. That does that work for you?

Sure, no worries! I thought we'd built all those branches into packages, but obviously not.

Great.


Server returned an unknown response.

Detailed description of the problem
Can't seem to get lychee to upload photos on an old Ubuntu server running php 5.6 (intentionally old php version). Didn't run into any issues getting the dependencies installed and Diagnostics doesn't alert me of any critical issues. I have uncommented all of the lines in provided .htaccess for "large files" according to the  FAQ https://github.com/electerious/Lychee/blob/master/docs/FAQ.md
Steps to reproduce the issue
After selecting an image to upload photo from top-right menu. Seems to occur whether I grab image from disk or from a URL.
Output of the diagnostics (Settings => Diagnostics)
Diagnostics
-----------
Warning: Dropbox import not working. No property for dropboxKey.
Warning: You may experience problems when uploading a large amount of photos. Take a look in the FAQ for details.
No critical problems found. Lychee should work without problems!

System Information
------------------
Lychee Version:  3.1.5
DB Version:      030102
System:          Linux
PHP Version:     5.6
MySQL Version:   50633
Imagick:         1
Imagick Active:  1
Imagick Version: 1655
GD Version:      2.2.3
Plugins:

Browser and system
client: Chrome Version 56.0.2924.87 (64-bit)  on Macintosh 10.10.5
server: Ubuntu 14.04.4 LTS using php 5.6 acquired through http://ppa.launchpad.net/ondrej/php/ubuntu (downgrade for testing other php software)
==> /var/log/apache2/error.log <==
[Fri Feb 10 15:51:02.503597 2017] [:error] [pid 28585] [client <IP_ADDRESS>:65427] PHP Fatal error:  Uncaught exception 'ImagickException' with message 'no decode delegate for this image format `/home/testserver/web/dev/kk-17/lytest/uploads/big/59d16398bc1005f6f94498814a5eeda0.jpg' @ error/constitute.c/ReadImage/544' in /home/testserver/web/dev/kk-17/lytest/php/Modules/Photo.php:313\nStack trace:\n#0 /home/testserver/web/dev/kk-17/lytest/php/Modules/Photo.php(313):
Imagick->readimage('/home/testserver...')\n#1 /home/testserver/web/dev/kk-17/lytest/php/Modules/Photo.php(226): Lychee\\Modules\\Photo->createThumb('/home/testserver...', '59d16398bc1005f...', 'image/jpeg', 1920, 1080)\n#2 /home/testserver/web/dev/kk-17/lytest/php/Access/Admin.php(234): Lychee\\Modules\\Photo->add(Array, '0')\n#3 /home/testserver/web/dev/kk-17/lytest/php/Access/Admin.php(44): Lychee\\Access\\Admin::uploadAction()\n#4
/home/testserver/web/dev/kk-17/lytest/php/index.php(71): Lychee\\Access\\Admin::init('Photo::add')\n#5 {main}\n  thrown in /home/testserver/web/dev/kk-17/lytest/php/Modules/Photo.php on line 313, referer: http://<IP_ADDRESS>/dev/kk-17/lytest/

Chrome console - not sure it's very helpful
http://i.imgur.com/NjzFb3f.png

This issue will be closed because I'm not actively working on Lychee anymore. The repository of Lychee will stay available, but the main development continues under the Lychee Organisation. A fork maintained by the community. Important issues have been migrated. Feel free to re-add your issue(s) when necessary.


fix: add the missing metadata field to the example-user for keycloak

lgtm

Were in the process of creating our applications in our deployment environment for the next release (release-1.0.gamma) which all changes will go into. Can you switch the branch you are trying to merge into to be release-1.0.gamma. Thank you for the change!

Done :)


Use bullets instead of index

Codecov Report

Merging #64 into master will decrease coverage by 1.28%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #64      +/-   ##
==========================================
- Coverage   77.87%   76.60%   -1.27%
==========================================
  Files           8        8
  Lines         393      393
==========================================
- Hits          306      301       -5
- Misses         68       73       +5
  Partials       19       19

Impacted Files
Coverage Δ

gui/drawer.go
92.00% <100.00%> (ø)

attacker/attacker.go
59.62% <0.00%> (-9.61%)
:arrow_down:

Continue to review full report at Codecov.

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


xwayland: use strerror(...) instead of %m

Previously, any error would be masked by an internal isatty call:
24:31:48.174 [DEBUG] [wlr] [xwayland/selection/incoming.c:386] XCB_SELECTION_NOTIFY (selection=277, property=278, target=256)
24:31:48.174 [ERROR] [wlr] [xwayland/selection/incoming.c:30] write error to target fd: Inappropriate ioctl for device

Done, wasn't aware it existed :)

Done, wasn't aware it existed :)


input-date-range: style tweaks: add "to" and wrapping

Similar to the PRs for input-date-time-range and input-time-range. For this one, the axe tests and sometimes the unit tests were failing with the error ResizeObserver loop limit exceeded. There did seem to be an additional run of the ResizeObserver happening for the parent node. I have not yet been able to figure out why (looks like it's somewhat related to additional resizing happening because input-date is using input-text where as input-time does not but don't know much more). I have not seen this error in testing on the demo. Some research suggests it's safe to suppress this error, but open to ideas on why this would be happening.

Been in meetings all afternoon but I can put up these visual diff tests next if you want them checked before merging


Enabling monitoring

When I look in Operations table I only see Workspace Configuration operations. My workspace does not have the _LogOperation function built-in. I suspect that I need to enable data collection and I suspect that I can do that in Azure portal. But we are using terraform so I would also need to know if there is a way to configure it there so that it stays turned on. It would be great if this document addressed those issues as well, as I can't seem to find it online anywhere.
Edit: Additionally, for my specific case, we are running services in kubernetes cluster, if that makes any difference in how we configure or collect agent data.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: b6d511e9-3132-c830-8f68-086ec8577480
Version Independent ID: a5ff4b87-395a-3a8a-afda-acdd3f74d528
Content: Monitor health of Log Analytics workspace in Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/logs/monitor-workspace.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @guywi-ms
Microsoft Alias: guywild

@lygasch
Thanks for your feedback! We will investigate and update as appropriate.

@lygasch thanks for raising this issue.
The _LogOperation should be available in all Log Analytics workspaces.
What happens when you try to run the function?
CC: @MeirMen

@lygasch, based on the referenced doc, contains error messages and warnings that occur in your workspace. Therefore, you are right that if you do not see any entry for other categories, it would mean that there are no other issues reported.
Regarding the "workspace capacity", I would suggest using the usage table. For details are available here - Analyze usage in a Log Analytics workspace
Please let us know if you have any questions.

@lygasch, We will now proceed to close this thread as we have not heard back from you. If there are further questions regarding this matter, please tag me in your reply and reopen the issue. We will gladly continue the discussion.


Implement createrawtransaction RPC method

Motivation
This is required for zcashd deprecation.
More details about this method can be found here: https://zcash.github.io/rpc/createrawtransaction.html

I created a draft PR for this issue here: https://github.com/ZcashFoundation/zebra/pull/9017. Test will be submitted in the next commit.


Make Platformatic Docker Image a multi-stage build

So we can avoid some of the size.

currently the size of the image is 680 MB


Feature/debug mode

:boom::lock: remember to turn off debug mode in production
:sparkles::children_crossing: added debug mode and crash on failure:

debug_mode setting (default: True) determines whether to display exception traceback in web (only works if default error fallback is used)
crash_on_failure (default: False) determines whether to terminate the process when an exception occurs (for security reasons it is adivsed to turn on in prod)

@raspitim merging this without review since it should work i think :O

will change message to read "You are seeing this message because your application runs in DEBUG MODE" for further clarification


Color can only be changes globally not for a single symbol

does work:
\colorlet{background}{yellow}
\colorlet{foreground}{blue}
\blocksignal[forward] at (0,0) label);

does not work:
\blocksignal[forward,foreground=blue,background=yellow] at (0,0) label);

work around:
\colorlet{foreground}{blue}
\blocksignal[forward] at (0,0) label ();
\colorlet{foreground}{black}


Fix references to storage management API in comments

Just noticed a bunch of managers created based on StorageManager didn't have all their comments updated.

@RikkiGibson,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


element.animate() returning type Animation instead of documented AnimationPlayer

Demo: https://dartpad.dartlang.org/f4ad8d86e1b01d901950
Working as of Dart 1.12.2
Stopped working, Dart 1.13.0+
Part of the Web Animation API.

The spec, and the underlying browser behaviour changed. See https://developer.mozilla.org/en-US/docs/Web/API/Element/animate
This should be fixed when we (very shortly) update the HTML library to be based on Chrome 45 IDL instead of Chrome 39, as part of the Dartium roll. But the fix is that the documented type will become Animation.

Clearing out 1.15 milestone as the last full push to dev has happened. If any changes are required before 1.15 is shipped, please file a merge request

Closed in dev channel new sdk/lib generated from 45 IDLs are checked into bleeding edge.


Directions function issue

iPhone XR
To replicate:
Load search page: family.services.govt.nz
Invoke a search with a street address (eg 1 Viewmont Drive, Harbourview, Lower Hutt)
Select “Directions” link in one of the results
Expected result:
Maps program opens, displaying starting address as a string, and provider’s address as a second string.
Actual result:
Maps program opens, displaying starting address as a pair of latitude, longitude coordinates, and providers’ address as a pair of latitude, longitude coordinates

Released to UAT.
Uses addresses to generate map directions rather than lat/long

userAddress is now passed through to more components, and to the service page

This has been tested on desktop, should also work on iPhone but that hasn't been confirmed yet

Cheers @lamorrison and @Br3nda!  Paul and I tested this on our respective phones this afternoon.  The address that shows up in the Get Directions appears in its full state immediately, but then appears to truncate to a shortened version.
Immediate display:

Truncated display:

However this is a huge improvement over the addresses appearing as latitude/longitude values for iPhone, so reckon this is fine.
@choirboy07 - feel free to comment further

Agree, it's a great improvement - the truncation is now a "nuisance factor" - if it is an easy fix to keep the full address that would be good.


test loss

Hello, I directly used unmodified code for training and testing. I found that during model testing, the test loss became increasingly large. When epoch reached 6, the test loss reached 6000, while when epoch was 1, the test loss was only 30+. Is there an overfitting phenomenon? What is the reason for this phenomenon? I would greatly appreciate it if you could provide me with an answer

I have the same problem.
1、When I useresnet18 backbone, test_loss is increasing to 10000+( accumulating loss? ), but seg_roc_auc actually  is decreasing.
2、It seems that there is no problem with wide_resnet50_2.


Can't connect to puppetdb (ERROR:pypuppetdb.api:Not Found <IP_ADDRESS>:8080 over HTTP)

apt-cache policy puppetdb
puppetdb:
Installed: 2.3.8-1puppetlabs1
Candidate: 2.3.8-1puppetlabs1
Version table:
ss -tlnp | grep :8080
LISTEN     0      50         ::ffff:<IP_ADDRESS>:8080                    :::*      users:(("java",11983,17))
telnet localhost 8080
Trying <IP_ADDRESS>...
Connected to localhost.
Escape character is '^]'.

[Fri Jun 17 13:34:42.661654 2016] [:error] [pid 4779] ERROR:pypuppetdb.api:Not Found <IP_ADDRESS>:8080 over HTTP.

What is here the problem?

What version of PuppetBoard have you installed?
Version 0.0.5 is the latest version that supports PuppetDB < 3.0

Hi,
i tested it with 0.0.5 and the same behavior.

Please ensure that your server isn't holding onto cached or pre-compiled code and submit your logs.

Hi, I had the same problem and I reinstalled  puppetboard forcing version 0.0.5 (because my puppetb is actually < 3.0)  and now is working, many thanks for the advise of compatibility
Cheers

Closing this ticket as it involves known compatibility issues.


Fixed prune path [ros2]

In testing we saw disappearing via points and jumping to goal directly when robot is near the goal. To fix this bug, tf_->transform() arguments should be given correctly  when transforming robot pose into the plan frame.

#291 supersedes


Operation failed with code 243

Describe The Bug
USER: andreasberger
DIR: /usr/local
CMD: npm install -g<EMAIL_ADDRESS>
[..................] \ idealTree:lib: sill idealTree buildDeps
[..................] \ idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps
[..................] / idealTree:lib: sill idealTree buildDeps

npm ERR! code EACCES
npm ERR! syscall open
npm ERR! path /Users/andreasberger/.npm/_cacache/tmp/fa790b1b
npm
ERR! errno -13
npm ERR!
npm ERR! Your cache folder contains root-owned files, due to a bug in
npm ERR! previous versions of npm which has since been addressed.
npm ERR!
npm ERR! To permanently fix this problem, please run:
npm ERR!   sudo chown -R 501:20 "/Users/andreasberger/.npm"
npm ERR! Log files were not written due to an error writing to the directory: /Users/andreasberger/.npm/_logs
npm ERR! You can rerun the command with --loglevel=verbose to see the logs in your terminal
Operation failed with code 243.
You can download this log file for future reference.
See https://github.com/homebridge/homebridge-config-ui-x/wiki/Troubleshooting for help.
Logs
No response
Config
No response
Homebridge UI Version
v4.55.1
Homebridge Version
Homebridge v1.7.0
Node.js Version
v20.12.0
Operating System
macOS
Environment Info
{"label"=>"Using hb-service?"}
Raspberry Pi Model
None

try deleting this folder /Users/andreasberger/.npm and then trying this installation again.

I am having the same issue but am very new to any of this. Can you help me with error code 243?

I am having the same issue, any fix??

try deleting this folder /Users/andreasberger/.npm and then trying this installation again.

Wanted to tell anyone seeing this, that this comment helped solve my code 243 error after trying to reinstall homebridge

try deleting this folder /Users/andreasberger/.npm and then trying this installation again.

Worked for me too! Thx!

how can I deleting this folder?


"Warning: config file not found"

Hi. whenever I start my PoB the text "Warning: config file not found" pops up in the green boot window. The PoB window opens, but remains black and is not respoding. restarting and reinstalling doesnt help
EDIT: added more detailed description of teh problem

That warning has nothing to do with the problem, and will always appear; it is quite harmless.
The only thing I can suggest at the moment is updating or re-installing your display driver; that often solves issues like this.

I already did that multiple times. I even completely reinstalled windows and its not working :\

had the problem myself when i had pob on second monitor in full screen! fixed it with opening the Launch.lua in a texteditor and put the vid_resizeable from 3 to 2 (and had vid_mode changed from 8 to 6 but i guess that wont do any difference)

ok can narrow it down to second monitor, vid_resizable 3, that are the problem parts on my system ^^ hope you find the problem :p

i did not find the file, but after reinstalling and not starting it in fullscreen it starts everytime and i havent encountered a blackscreen so far. thanks a lot man :)

np ;) and the launch.lua file is located directly in the first directory, maybe openarl can fix that, but i guess its just a minor and systembased problem with low priority. i didnt dig too deep into the program, just using it ;)


Android impl for canShareVia (peek=true) seems not correct

SocialSharing.java implementation for canShareVia looks like if were not correct:
  private boolean doSendIntent(final CallbackContext callbackContext, final String msg, final String subject, final JSONArray files, final String url, final String appPackageName, final boolean peek) {

    ...

          if (activity != null) {
            if (peek) {
              callbackContext.sendPluginResult(new PluginResult(PluginResult.Status.OK));
            } else { ... }
          }
        } else {
          if (peek) {
            callbackContext.sendPluginResult(new PluginResult(PluginResult.Status.OK));
          } else { ... }
        }

Just from reading the code, I see the problem that when peeking whether "we can", it always returns OK on Android. I admit I haven't tested it, but it should be worth having a second look at it and fix or comment it. Of course I may be wrong...

Please test and reopen if it is a problem, thanks.


Left IC2 Config error

Required Info

Camera Model
D410

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win 11

Kernel Version (Linux Only)
-

Platform
PC

SDK Version
2.54.1

Language
-

Segment
Robot

Issue Description
Hi, I previously used Intel RealSense Viewer, but recently it stopped working.
Error in console:

[Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\common\notifications.cpp:511 - Left IC2 Config error

When turning on streaming there is "No Frames Received" info.
Updating the firmware didn't help, When trying "Hardware Reset", console shows:

[Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\sensor.cpp:661 - acquire_power failed: MFCreateDeviceSource(_device_attrs, &_source) returned: HResult 0x80070003: "The system cannot find the path specified."
[Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\error-handling.cpp:96 - Error during polling error handler: MFCreateDeviceSource(_device_attrs, &_source) returned: HResult 0x80070003: "The system cannot find the path specified."

Hi @hermattt  Can you check the camera privacy settings in Windows please to ensure that pernission for applications to access the camera is set to On.  Instructions for doing so can be found at https://github.com/IntelRealSense/librealsense/issues/3381#issuecomment-503424789

It was set to on.

If you are using a D410 depth module, please next check that the interposer (the floppy cable or rigid board that joins the Vision Processor D4 and Depth Module together) is fully seated in the 50-pin connectors and is not only partially inserted.

It is fully seated. (Reconnected, no difference)

Commercial flexible cable made by Kinova (their Gen3 robot).

When it was working, I installed old (in that time it was new), but now tried it and it didn't work. I updated to newer release using Intel.RealSense.Viewer.exe version.
Installing new version Intel.RealSense.SDK-WIN10 did not help.
rs-hello-realsense.exe opens console for 20 seconds and exits with no output.

What is the product in the picture above, please?  Is it a RealSense D415 camera that has been opened and its camera board disconnected?

Thanks very much for the confirmation that it is an opened-up Kinova Gen 3 with a D410 depth module.
The information listing in the Viewer looks fine.
Kinova Gen 3 can work with the RealSense SDK, as demonstrated by the case at https://github.com/IntelRealSense/librealsense/issues/11993 and your own experiences with the Viewer.
Intel are unable to provide technical support though for products not manufactured by Intel that incorporate RealSense technology, unfortunately.  The proper place to seek support for such products will be the manufacturer, which in this instance is Kinova.
https://www.kinovarobotics.com/reach-us/customer-support
It looks as though the Intel firmware driver enables the Vision Processor and D410 camera boards to be recognized by Intel software such as the Viewer.  It likely would not recognize the particular Omnivision RGB sensor that Kinova are using as it is a different model from the Omnivision sensors used for RGB by Intel-made RealSense cameras, which is why the firmware identifies it as D410 (depth and infrared streams only, no RGB stream).
In summary, Intel cannot provide replacement components if there is a hardware fault because it is a Kinova product.  Kinova might not replace the parts because if the Kinova was still within its sales warranty period then opening it up would have likely invalidated the warranty.
I would recommend reconnecting the D410 board to the interposer cable and then trying to run a calibration of the sensors to see if it clears the problem that you are experiencing (though the calibration will probably fail if streaming cannot be started).   If that does not work then purchasing replacement Vision Processor D4 V1 / RealSense D410 boards might be the only solution.  I think that the problem is more likely to be with the D410 board than the Vision Processor D4, as there is not an apparent problem with accessing the camera details stored on the D4.

Hi @hermattt  Do you have an update about this case that you can provide, please?  Thanks!

Looking under microscope there are 2 elements that seem to be broken on D4 card.

I`m waiting for D4 board, if it won't help, I will buy camera module.
Is there any board view of that board so I could check what are those damaged components?

There is not a fully annoted diagram available of the components on the D4 V1 board.  The main components of the V1 though will be the D4 chip, an EEPROM flash memory component for storing the camera firmware driver, the USB components and an Image Signal Processor (ISP) chip for handling color data processing.

So, I can't get to know, what those red marked components are?

There is not an available diagram that identifies those parts, unfortunately.


Create an Empty SAPUI5 Project

Tutorials: https://developers.sap.com/tutorials/sapui5-101-create-project.html
While adding deployment configuration I am getting following error:
{"message":"@sap/fiori:app generator failed - {"message":"Could not update method 'validate' in 'cfDestination' question in generator '@sap/fiori:app' - evaluateMethod() e.trim is not a function","stack":"TypeError: evaluateMethod() e.trim is not a function\n at /extbin/npm/globals/lib/node_modules/@sap/generator-fiori/generators/deployment-generator/deploy/index.js:574:192947\n at Object.t.validateDestinationQuestion (/extbin/npm/globals/lib/node_modules/@sap/generator-fiori/generators/deployment-generator/deploy/index.js:574:192955)\n at u.validate (/extbin/npm/globals/lib/node_modules/@sap/generator-fiori/generators/deployment-generator/deploy/index.js:574:191874)\n at v. (/tmp/vscode-unpacked/yeoman-ui-1.1.57.vsix/extension/dist/extension.js:193:116235)\n at Generator.next ()\n at /tmp/vscode-unpacked/yeoman-ui-1.1.57.vsix/extension/dist/extension.js:193:110451\n at new Promise ()\n at r (/tmp/vscode-unpacked/yeoman-ui-1.1.57.vsix/extension/dist/extension.js:193:110196)\n at v.evaluateMethod (/tmp/vscode-unpacked/yeoman-ui-1.1.57.vsix/extension/dist/extension.js:193:115982)\n at o. (/tmp/vscode-unpacked/yeoman-ui-1.1.57.vsix/extension/dist/extension.js:515:3404)\n at Generator.next ()\n at /tmp/vscode-unpacked/yeoman-ui-1.1.57.vsix/extension/dist/extension.js:515:2068\n at new Promise ()\n at r (/tmp/vscode-unpacked/yeoman-ui-1.1.57.vsix/extension/dist/extension.js:515:1813)\n at o.handleRequest (/tmp/vscode-unpacked/yeoman-ui-1.1.57.vsix/extension/dist/extension.js:515:3159)\n at /tmp/vscode-unpacked/yeoman-ui-1.1.57.vsix/extension/dist/extension.js:186:63780\n at /theia/node_modules/@theia/core/lib/common/event.js:176:33\n at CallbackList.invoke (/theia/node_modules/@theia/core/lib/common/event.js:191:39)\n at Emitter.fire (/theia/node_modules/@theia/core/lib/common/event.js:318:29)\n at WebviewsExtImpl.$onMessage (/theia/node_modules/@theia/plugin-ext/lib/plugin/webviews.js:71:44)\n at RPCProtocolImpl.doInvokeHandler (/theia/node_modules/@theia/plugin-ext/lib/common/rpc-protocol.js:291:23)\n at RPCProtocolImpl.invokeHandler (/theia/node_modules/@theia/plugin-ext/lib/common/rpc-protocol.js:276:41)\n at RPCProtocolImpl.receiveRequest (/theia/node_modules/@theia/plugin-ext/lib/common/rpc-protocol.js:240:31)\n at RPCProtocolImpl.receiveOneMessage (/theia/node_modules/@theia/plugin-ext/lib/common/rpc-protocol.js:209:22)\n at /theia/node_modules/@theia/plugin-ext/lib/common/rpc-protocol.js:101:109\n at /theia/node_modules/@theia/plugin-ext/lib/common/rpc-protocol.js:316:17\n at /theia/node_modules/@theia/core/lib/common/event.js:176:33\n at CallbackList.invoke (/theia/node_modules/@theia/core/lib/common/event.js:191:39)\n at Emitter.fire (/theia/node_modules/@theia/core/lib/common/event.js:318:29)\n at /theia/node_modules/@theia/plugin-ext/lib/hosted/node/plugin-host.js:148:25\n at step (/theia/node_modules/@theia/plugin-ext/lib/hosted/node/plugin-host.js:48:23)\n at Object.next (/theia/node_modules/@theia/plugin-ext/lib/hosted/node/plugin-host.js:29:53)\n at /theia/node_modules/@theia/plugin-ext/lib/hosted/node/plugin-host.js:23:71\n at new Promise ()"}"}

Hi @morimehul ,
This issue has been reproduced by the SAP Fiori tools team, as well as reported by customers. We are currently working on a fix. We will keep you updated.
Kind regards,
Conrad (SAP Fiori tools team)

Hi @morimehul
I see that my colleagues have closed their ticket investigating the issue. Could you please try it again?
Thanks and regards,
Conrad (SAP Fiori tools team)

Thanks @cjbernal
Working fine  now.
Cheers
Mehul


Update py and cryptography

Update dependencies for January release of safety-db
cryptography = "^3.3.1" # safety (pyup.io-39252)
Cryptography 3.3 no longer allows loading of finite field Diffie-Hellman parameters of less than 512 bits in length. This change is to conform with an upcoming OpenSSL release that no longer supports smaller sizes. These keys were already wildly insecure and should not have been used in any application outside of testing.
py = "^1.10.0" # safety (pyup.io-39253 / CVE-2020-29651)
A denial of service via regular expression in the py.path.svnwc component of py (aka python-py) through 1.9.0 could be used by attackers to cause a compute-time denial of service attack by supplying malicious input to the blame functionality. See CVE-2020-29651.

Thanks :+1:
I decided to do this in #224 instead, to avoid the unrelated bump to coverage (some Poetry quirk?) and to avoid adding direct dependencies (updated only the lock file instead).

Thanks :+1:
I decided to do this in #224 instead, to avoid the unrelated bump to coverage (some Poetry quirk?) and to avoid adding direct dependencies (updated only the lock file instead).


More consistent http flakiness handling

Context
This is a follow up to #7333. There are several things we can do to improve handling of flakiness:

expose public options for the internal flags related to http connections or connectivity retries
investigate whether we can move the retry strategy deeper, for example at the ExternalResource level, so that more areas of Gradle can benefit from smarter retry strategies
investigate whether build cache connectivity issues should be handled differently, and potentially with different build options
investigate whether build cache requests should use ExternalResource too as to benefit from generic improvements in that area

Just to make sure I am understanding this correctly: It is currently (as of 5.3.1) not possible for users to configure the retry/backoff parameters described in https://github.com/gradle/gradle/pull/7333#issue-221948232 (org.gradle.internal.repository.max.tentavies and org.gradle.internal.repository.initial.backoff).

It is possible, just not supported.

Thanks a lot for the quick reply!
OK, so when I set the total number of attempts to 1 by adding the system property
-Dorg.gradle.internal.repository.max.tentatives=1
to my command line options it does indeed disable any retries.
But when I add the following line to gradle.properties
org.gradle.internal.repository.max.tentatives=1
I don't see any effect.
Is that what because it is an internal property or am I doing something wrong?
But in any case, I was now able to do what I wanted to, so thanks again!
(BTW: You had a typo in the first property name in your other comment which I linked to above).

You can set system properties from a gradle.properties file: https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_system_properties

Ah, yes - I don't know I missed that in the manual... Thanks a lot!
systemProp.org.gradle.internal.repository.max.tentatives=1
Incidentally, setting it via org.gradle.jvmargs=-Dorg.gradle.internal.repository.max.tentatives=1 did work after all. I just had a typo in there... :-(


DWD Harvester action is failing

Hi GDK-Team! Hi @Jaszkowic!
today the magdeburg-giesst DWD Harvester failed. And I've noticed that the GDK DWD harvester failed too. Establishing the database connection doesn't work anymore. And you seemed to have fixed the issue. Could you tell me what you did to fix that?
Jens

Hi @JensWinter, indeed, we also had troubles with connecting to the databases. The reason for this is that Supabase has changed how we can directly connect to the database:

We’re deprecating PgBouncer and migrating all projects to our Supavisor connection pooler. Go grab the pooler connection string in your project’s Database Settings.

Changing the environment variables for the DWD Harvester to point to the new database endpoint worked for us.

Hey thanks for your hint.
Oh, and I thought I did that and it didn't work.
Well, obviously it's not enough to just change the server name. I forgot to set up the correct user name as well. Now it's working. Thanks again. 😃


can this be used with a react app?

I'm very new to this, apologies if this is a silly question but I'm quite lost.
I want to create a react app in a single html file.  Is it possible?

Thanks.  I'm very new to this stuff and am not sure how to get it working from a basic react app (created using yarn create react-app my-app).  Do you know of a detailed example that would help?

I can leave you my webpack.config if that will help? I am not sure exactly because we do not use React. I had to do a lot of trial and error to get it to work because there wasn't very many examples of how I use it.

Thanks, if you could gist it that might be helpful. I think this is a react specific problem though.

https://gist.github.com/SovietFrontier/d6d88147affd6a69e7baa97ce32dee79
Have at it.

Think I got it working.  For future reference (using react 16.7.0 & yarn 1.10.1)...
Create a react app:
npx create-react-app my-app
cd my-app
yarn build

All good?  Cool, run eject so that you have access to the webpack config:
yarn eject
rm -rf build node_modules
yarn build

Add this project and update webpack:
yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>
Edit config/webpack.config.js:
const HtmlWebpackPlugin = require('html-webpack-plugin');
const HtmlWebpackInlineSourcePlugin = require('html-webpack-inline-source-plugin'); <--- add this
...
plugins: [
  new HtmlWebpackPlugin(
    Object.assign(
      ...
      isEnvProduction
        ? {
            inlineSource: '.(js|css)$', <-- add this
            minify: {
              ...
  ),
  ...
  isEnvProduction &&
    shouldInlineRuntimeChunk &&
    new HtmlWebpackInlineSourcePlugin(HtmlWebpackPlugin), <--- add this
    new InlineChunkHtmlPlugin(HtmlWebpackPlugin, [/runtime~.+[.]js/]),
    ...

Run rm -rf build && yarn build && serve -s build - the index.html you load should now contain all the js and css stuff inline.  Note that the static files are still created in the build dir, but they aren't used by the page.

Think I got it working. For future reference (using react 16.7.0 & yarn 1.10.1)...
Create a react app:
npx create-react-app my-app
cd my-app
yarn build

All good? Cool, run eject so that you have access to the webpack config:
yarn eject
rm -rf build node_modules
yarn build

Add this project and update webpack:
yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>
Edit config/webpack.config.js:
const HtmlWebpackPlugin = require('html-webpack-plugin');
const HtmlWebpackInlineSourcePlugin = require('html-webpack-inline-source-plugin'); <--- add this
...
plugins: [
  new HtmlWebpackPlugin(
    Object.assign(
      ...
      isEnvProduction
        ? {
            inlineSource: '.(js|css)$', <-- add this
            minify: {
              ...
  ),
  ...
  isEnvProduction &&
    shouldInlineRuntimeChunk &&
    new HtmlWebpackInlineSourcePlugin(HtmlWebpackPlugin), <--- add this
    new InlineChunkHtmlPlugin(HtmlWebpackPlugin, [/runtime~.+[.]js/]),
    ...

Run rm -rf build && yarn build && serve -s build - the index.html you load should now contain all the js and css stuff inline. Note that the static files are still created in the build dir, but they aren't used by the page.

thanks so much for posting this! works like a charm!

Thx a lot ! It also works with yarn add html-webpack-plugin@next instead of yarn add<EMAIL_ADDRESS>To know more, this is related : https://github.com/jantimon/html-webpack-plugin/issues/1068


chore: release 2.6.3

:robot: I have created a release *beep* *boop*
2.6.3 (2024-06-25)
Bug Fixes

deploy: errors count in progress report not updating (46ada1c)
deploy: helm rollback not adding release metadata to created resources (bfd3924)
deploy: ignore false recreation errors during StatefulSet tracking (a7fb885)
deploy: rollback error not showed (be32b2a)
deploy: some STS and DS pods not tracked and their errors ignored (d1a5758)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/werf/werf/releases/tag/v2.6.3 :sunflower:


Support in Browser

Needs to be compiled to system module and with outFile option in tsconfig.

I don't see the point myself as it would add overhead to pages for no good reason; this is a tool for the development build.


Keep comments of the variable in d.ts

Description
Could we keep comments of the variable in d.ts, like unjs/unbuild ?
However I haven't looked at the unjs/untyped implementation, so I don't know if this is possible.
Suggested solution
No idea.
Alternative
No response
Additional context
No response
Validations

[X] Read the FAQ.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Comments will be keeped in declaration files. You need to provide a reproduction to show how the comments disappeared.

I assume it is related to #132, but that is not a valuable workaround.
We export types e.g. like this:
<script lang="ts">
export interface MyCompProps {
  /** JSDoc comment */
  myprop1: string
}
</script>

<script setup lang="ts">
defineProps<MyCompProps>()
</script>

That way other devs can also import these TS types and reuse them for their needs

当我像这样声明props
未经编译时，导入MyCompoment.vue，在vue文件template里，鼠标移动到props上，能够显示注释信息。
经过编译后，开发者在vue文件template里，鼠标移动到props上只能显示其类型，而不显示注释信息。
props.ts
export const myProps = {
   /**
     * @description 我的props
     */
    myprop: {
      required: false,
      type: String
    }
}

MyCompoment.vue
<script lang="ts" setup>
import { myProps } from './myProps';

defineOptions({
  name: 'MyCompoment'
});

const props = defineProps(myProps);
</script>

Duplicate to #373 (more details), so I close this issue.


Fix Object.assign() errors in IE11

Object.assign() throws errors in IE11, use babel-plugin-transform-object-assign to fix.

TIL that IE doesn't have Object.assign(), thanks for the PR :)


advanced highlighting

The implementation still lacks advanced handling of the operations
flags, inline wave assignments and mixed assignments in the variable
declarations:
examples of missing features:
Make/N=(32/8, 14/var)/O/I root:testwave/WAVE=wv
String one = "1", two, three //comments

	FindValue/TXOP=4/TEXT=(findme) here
	Make/FREE/N=(4/5)/T wv
	Make/FREE/N=((4/5), number)/T wv


[5.0] Allow collections of primitives to be imploded

So that we can do this:
collect([1, 2, 3])->implode('-'); // 1-2-3

You can revert your change made on the test file.

You can revert your change made on the test file.

?

He only change the array syntax, according to the rest of the test file is not correct.
We change all lines or no one.


[PIRK-33] : Create release profiles to facilitate Pirk releases

Tested a release:perform goal with profile = "signed_release".

+1
There is one typo in the scm section that we need to change to remove 'nifi' and change to the correct pirk repo:
<scm> 		<connection>scm:git:git://git.apache.org/nifi.git</connection> 		<developerConnection>scm:git:https://git-wip-us.apache.org/repos/asf/incubator-pirk.git</developerConnection> 		<url>https://git-wip-us.apache.org/repos/asf?p=incubator-pirk.git</url> 		<tag>HEAD</tag> 	</scm>
I can change it as I merge (pls let me know if this is not the correct protocol - just trying to make it easy)...

I can fix that, will update the PR in a few mins.

Updated the PR, thanks for the feedback

OK - will merge


Adding py3.5, linux 32 and win 32

Can you merge with develop? The build won't pass unless you have: https://github.com/Anaconda-Server/anaconda-client/pull/307

let's ee

yay!!! :100: @dsludwig

:+1:


Change default aspect for past tense

fixes https://github.com/rossmeissl/verbs/issues/15
@rossmeissl maybe make a (minor) release before merging this?

3.0.0 has been released. Thanks again @nerixim !


feat: OnboardingCard

Description
[ What changed? Feel free to be brief. ]
Checklist

[ ] The base branch of this PR is dev, rather than main
[ ] The relevant docs, if any, have been updated or created

Screenshots
[ For visual changes, include screenshots. ]
Testing
[ For new or modified features, provide step-by-step testing instructions to validate the intended behavior of the change. ]

@sestinj good catches/tweaks here 👍


no such package '@png_archive//

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): 'Build from source on Windows' TensorFlow Official Website
TensorFlow version:
Python version: 3.6.5
Installed using virtualenv? pip? conda?: using cmd.exe
Bazel version (if compiling from source): 0.21.0
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

Describe the problem
I was trying to build TensorFlow from source in order to solve "Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2" problem.
Although I installed Bazel properly and added necessary environment variables, everytime I tried to build pip packages, which is "bazel build --config=opt //tensorflow/tools/pip_package:build_pip_package", an error called "Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted: no such package '@png_archive//'" always occurs.
I also referred to some issues on the same problem, but none of them solved my problem. Is there anything I need to do? Or should I just install it through pip and ignore "Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2" this message?
Provide the exact sequence of commands / steps that you executed before running into the problem
C:\tensorflow>python ./configure.py
WARNING: The following rc files are no longer being read, please transfer their contents or import their path into one of the standard rc files:
nul
WARNING: Running Bazel server needs to be killed, because the startup options are different.
WARNING: --batch mode is deprecated. Please instead explicitly shut down your Bazel server using the command "bazel shutdown".
INFO: Invocation ID: 2c23affd-49a0-4cde-94b2-236aa0a37d76
You have bazel 0.21.0 installed.
Please specify the location of python. [Default is C:\Users\wltjd\AppData\Local\Programs\Python\Python36\python.exe]:
Found possible Python library paths:
C:\Users\wltjd\AppData\Local\Programs\Python\Python36\lib\site-packages
Please input the desired Python library path to use.  Default is [C:\Users\wltjd\AppData\Local\Programs\Python\Python36\lib\site-packages]
Do you wish to build TensorFlow with XLA JIT support? [y/N]: y
XLA JIT support will be enabled for TensorFlow.
Do you wish to build TensorFlow with ROCm support? [y/N]: N
No ROCm support will be enabled for TensorFlow.
Do you wish to build TensorFlow with CUDA support? [y/N]: N
No CUDA support will be enabled for TensorFlow.
Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is /arch:AVX]:
Would you like to override eigen strong inline for some C++ compilation to reduce the compilation time? [Y/n]:
Eigen strong inline overridden.
Preconfigured Bazel build configs. You can use any of the below by adding "--config=<>" to your build command. See .bazelrc for more details.
--config=mkl            # Build with MKL support.
--config=monolithic     # Config for mostly static monolithic build.
--config=gdr            # Build with GDR support.
--config=verbs          # Build with libverbs support.
--config=ngraph         # Build with Intel nGraph support.
--config=dynamic_kernels        # (Experimental) Build kernels into separate shared objects.
Preconfigured Bazel build configs to DISABLE default on features:
--config=noaws          # Disable AWS S3 filesystem support.
--config=nogcp          # Disable GCP support.
--config=nohdfs         # Disable HDFS support.
--config=noignite       # Disable Apacha Ignite support.
--config=nokafka        # Disable Apache Kafka support.
--config=nonccl         # Disable NVIDIA NCCL support.
C:\tensorflow>bazel build --config=opt //tensorflow/tools/pip_package:build_pip_package
WARNING: The following rc files are no longer being read, please transfer their contents or import their path into one of the standard rc files:
c:\tensorflow/.bazelrc
Starting local Bazel server and connecting to it...
WARNING: Option 'experimental_shortened_obj_file_path' is deprecated
INFO: Invocation ID: 61281b1e-9316-4ac5-9241-238712f7de45
ERROR: Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted: no such package '@png_archive//': Traceback (most recent call last):
File "C:/tensorflow/third_party/repo.bzl", line 106
_apply_patch(ctx, ctx.attr.patch_file)
File "C:/tensorflow/third_party/repo.bzl", line 73, in _apply_patch
_execute_and_check_ret_code(ctx, cmd)
File "C:/tensorflow/third_party/repo.bzl", line 52, in _execute_and_check_ret_code
fail("Non-zero return code({1}) when ...))
Non-zero return code(256) when executing '?C:\msys64_2\usr\bin\bash.exe -l -c "patch" "-p1" "-d" "C:/users/wltjd/_bazel_wltjd/xv6zejqw/external/png_archive" "-i" "C:/tensorflow/third_party/png_fix_rpi.patch"':
Stdout:
Stderr: java.io.IOException: ERROR: src/main/native/windows/processes-jni.cc(383): CreateProcessW("C:\users\wltjd_bazel_wltjd\xv6zejqw\external\png_archive?C:\msys64_2\usr\bin\bash.exe" -l -c ""patch" "-p1" "-d" "C:/users/wltjd/_bazel_wltjd/xv6zejqw/external/png_archive" "-i" "C:(...)): ??? ??? ?? ? ????.
INFO: Elapsed time: 14.881s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (319 packages loaded, 8559 targets configured)
Fetching @swig; fetching 8s
Fetching @grpc; fetching 7s
Fetching @cython; fetching 7s
Fetching @eigen_archive; fetching 6s
Fetching @llvm; fetching 5s
Fetching @icu; fetching 4s
Fetching @boringssl; fetching 4s
Fetching @png_archive; fetching
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

You can safely ignore the warning message and continue to use TensorFlow.

same problem! Have you solved it?

Hi, I encountered with the same problem(maybe?), and turned to find that the patch command can only be used in the MSYS2 command terminal, otherwise you need to set the environment. I try the build command in the MSYS2 terminal and it worked fine. Hope helps someone!


Performance degraded after validation was added

This is probably similar to https://github.com/openstreetmap/iD/issues/5971.
I noticed that round about the time when validation where added, the editing in Berlin is really slow. This is for both the public version as well as http://preview.ideditor.com/master/#background=Berlin-2018&disable_features=boundaries&map=20.45/52.48086/13.44218.
How can we help figure out what is going on? Would one of those Google Chrome rending-graphs help? I don't know much about them, so I would need a tutorial what to provide.
My system did not change recently, so it's either updates to the OS, Chrome or iD that change the performance.
MacBook Pro (Retina, Mitte 2012), 2,3 GHz Intel Core i7, 16 GB 1600 MHz DDR3
Operating System Mac OSX 10.14.x
Web Browser Chrome 71.0.3578.98
Update

Its really bad when I type my commit message. I type and nothing happens and then the text appears all at once.
Would screen-videos help?

Yeah this is #5971 - I don't think it should have been closed.

How can we help figure out what is going on? Would one of those Google Chrome rending-graphs help? I don't know much about them, so I would need a tutorial what to provide.

Yes, profiling in the Google Chrome dev tools would be very helpful.

From my own testing on this, the degraded performance is almost entirely due to the crossing ways check. iD currently revalidates everything you've edited after every further change, so if you're editing long roads or such this can add up fairly quickly. We have #5901 to only revalidate features you've actually edited since the last validation. We should do that soon.

Yeah this is #5971 - I don't think it should have been closed.

Oops.

#4731 might be related

This is much better now after #6140 ..

@bhousel I used the preview system some more and first thought its just the changeset comment field (the separate issue I created) but now I feel big performance issues in other places.
I tried to debug it better this time.
Location: http://preview.ideditor.com/master/#background=GEOSN-DOP-RGB&disable_features=boundaries&id=w151467550&map=19.97/50.99388/12.80095
Video: https://www.dropbox.com/s/azpnxtrdlqly35u/id-performance-reflow.mov?dl=0
There are quite a few seconds between clicking something and being able to use it.
To me it looks like one issue is query?
First edit (outside the video):

Details of the video and after:


Adds route and controller for missed update user list api

Date: 9 Dec 2023
Developer Name: @Ajeyakrishna-k

Issue Ticket Number:-

#1699

Description:
Adds a route and controller function which returns discord Id of users who are active with tasks but have not filled in progress updates on task details page.
Docs:

https://github.com/Real-Dev-Squad/website-api-contracts/pull/173

Is Under Feature Flag

[x] Yes
[ ] No

Database changes

[ ] Yes
[x] No

Breaking changes (If your feature is breaking/missing something please mention pending tickets)

[ ] Yes
[x] No

Is Development Tested?

[x] Yes
[ ] No

Add relevant Screenshot below ( e.g test coverage etc. )

@Ajeyakrishna-k can you resolve the merge conflicts please.

@Ajeyakrishna-k can you resolve the merge conflicts please.

Done!


Throw an error if using array-like data

We do not support array-like data (numeric, sequential ids can't be used for concurrent edits) so throw an error if someone tries to load them into a synchronized array in AngularFire.

Is this any different from #509 which you also opened? If so, let's just close this guy. I think we can do something better than just throwing an error here. Or at least we should try to.

I think this is the correct answer. Let's close the other.

Right before firing the initial $loaded() event, we will check if angular.isArray(snapshot.val()), and if so, throw a synchronous error explaining that AngularFire does not support arrays in this way.


Breaking change between v4 and v5 with the as prop

I updated from styled-components v4 to v5 and ran into a strange issue with the as prop. I have a styled NavLink that I thought I'd slap a as="a" href="..." on to have it link to another site. This works just fine in v4 but doesn't on v5.
The workaround isn't difficult, but I thought I'd create an issue anyway because it was unexpected.
Environment
See CodeSandbox
Reproduction
Here is an example app on styled-components v4:
https://codesandbox.io/s/sc4-nilej?file=/src/App.tsx
Here it is on v5:
https://codesandbox.io/s/sc5-bor2r?file=/src/App.tsx
Steps to reproduce
Upgrade from v4 to v5
Expected Behavior
It not to crash.
Actual Behavior
It crashes

I'm happy to accept changes for the docs on styled-components' website repository. But I think there's not really any resolution to this. Breaking changes do happen between major versions due to small changes of the implementation. For this change, we don't really have a test that guarantees consistent behaviour, so it's possible that it has changed a little.
In general, I see that you're basically doing styled(X).attrs({ as: Y }) and are then expecting the as="..." prop to still work. That said though, I see this as a major edge case, which I wouldn't expect to see. Hence, I don't think it has been covered and has probably changed a little.
There's not really any way forward to resolve this or address any part of this issue though. In other words, no change in this repository has any chance of resolving this, as it's related to an upgrade that has already been implemented and happened with an edge case that I'd say has no clearly defined behaviour, which makes this issue open-ended potentially. So, I'll close this for now, but happy to discuss resolutions here. I do think though that this is an "expected" change, in so far as its' cause is a specific syntax that, while possible, is not meant to be used in such a way.


Move to EmbeddedUtilities repo

Rename the repo to EmbeddedUtilities.

Renaming repo is only possible for owner, not members. Specified another assignee.

Renamed. I guess this can be closed now.

In order to work properly, the new URL should be set on local clones. Technically it still works, but if someone creates a repository with the old name, the redirect will break. This can be done by executing the following command in the local repo.
$ git remote set-url origin new_url


RipMe freezes when ripping subreddits

Ripme version: 1.7.93
Java version: OpenJDK version 11.0.8
Operating system: Linux Mint 19.3 Cinnamon

Exact URL you were trying to rip when the problem occurred: This has happened on every subreddit I have tried to rip.
Please include any additional information about how to reproduce the problem: Attempt to rip any image and/or gif-based subreddit.

Expected Behavior
RipMe downloads all images/gifs from a subreddit.
Actual Behavior
RipMe downloads a majority of the subreddit's images/gifs but then perpetually remains "pending" on the remaining images/gifs.

I have the same issue, but in my case it seems to only apply to specific subreddits. Usually it gets stuck on the 99% mark with only a couple images pending, but I've seen it freeze up towards the beginning or halfway as well.
I've noticed that it gets stuck on the following subreddits;

/r/AnimeWallpaper
/r/ChurchOfSenko
/r/Megumin

Other subreddits (for example, /r/Gamindustri), seem to rip just fine. From what I can tell, it doesn't matter if you rip a subreddit for the first time or if you've already ripped it in the past, as it'll get stuck regardless.
I'm running RipMe v1.7.93, Java 1.8.0_261, on Windows 10 version 2004.


Update README.md

Summary
Fix intra page link for PHPDocs for models
Checklist

[x] Update the README.md

Thanks


Update Management.Compute from 9.1.0 to 9.2.0

Hi @hyonholee, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (hylee). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

let us merge it after https://github.com/Azure/azure-sdk-for-net/pull/978 gets in first


Travis: Use an unreleased version of Codecov to fix reporting

As can be seen at [1] our coverage reporting has been broken for a long
time already. This is presumably due to [2] as we get a similar error in
the log [3]. So try to address the issue with an unrelased version of
the Codecov script which has [4] merged.
[1] https://codecov.io/gh/heremaps/oss-review-toolkit/
[2] https://github.com/codecov/codecov-bash/issues/133
[3] https://travis-ci.com/heremaps/oss-review-toolkit/builds/133415353#L3318
[4] https://github.com/codecov/codecov-bash/pull/200
Signed-off-by: Sebastian Schuberth<EMAIL_ADDRESS>

Unfortunately the error remains to be there: https://travis-ci.com/heremaps/oss-review-toolkit/builds/133520512#L3736. I'll investigate this later.

This indeed fixes coverage reporting, see https://travis-ci.com/heremaps/oss-review-toolkit/builds/133629525#L3325.


Milestone 2: add, remove, edit functionality

Hi,
I am done with all requirements for this project.
No linter errors.

Add a new ToDo task with enter key. (task is added in local storage)
Remove task with 'trash' icon which changes previous 'dots' icon on editing task text content.
(task is removed from local storage)
Editing text content on click, changing field background and icons.
Ids are sorted and removing random tasks, still sorted.
Thank you!
Update: checkboxes fixed and edit now is working properly.

To the next reviewer, kindly approve the project as all the requirements for this milestone have been met. I made a mistake and required changes that were not for this milestone, kindly confirm that. Thanks.
@VuDej I apologize for the misunderstanding.

STATUS: APPROVED  ✔

Hi @VuDej ,
Your project is complete! Congratulations!  🎉💯🌟

Cheers..Happy coding!..and keep soaring higher! 💻 🍷 🚀

As described in the Code reviews limits policy you have 2 more limited reviews per this project. If you think that the code review was not fair, you can request a second opinion using this form.


Module "BM25_doc_ranker" not in found

When I run the command: PYTHONPATH=src python src/baseline/retriever/build_db.py --db_path data/feverous_wikiv1.db --save_path data/feverous-wiki-docs.db, I get the following error:
Traceback (most recent call last):
  File "src/baseline/retriever/build_db.py", line 19, in <module>
    from baseline.drqa.retriever import utils
  File "/home/martin/FEVEROUS/src/baseline/drqa/retriever/__init__.py", line 24, in <module>
    from .BM25_doc_ranker import BM25DocRanker
ModuleNotFoundError: No module named 'baseline.drqa.retriever.BM25_doc_ranker'

It seems that it is looking for the module BM25_doc_ranker, but this module does not seem to exist in the repo.

Hi Martin, thanks! A dependency issue resulting from last commit. Fixed now.


godot_variant_new_bool has a out-argument as "p_v" instead of e.g. "r_v"

Generally gdnative_api is pretty consistent with labelling out-arguments as "r_...", except for this one. I use the prefix to distinguish between in and out-arguments when generating bindings

Fixed in a833b61828765207eabcb6d1ec5f131477389b52


work-around fix for connection migration

Summary of the changes (Less than 80 chars)

Detail 1
Detail 2

Fixes #bugnumber (in this specific format)

Could you describe the issue in the PR a little bit more? This helps us track the issue in the future.


Internal Sharding

Starting with v12.0.0 add an option for internal sharding. This would be different than the traditional sharding manager, in that your one Discord Client/process would handle sharding with discord rather than spawning multiple processes with their own Discord Client instances each.
Benefits:

Memory for small/mid sized bots would be less than the sum of traditional sharding shards due to the following reasons:

The base instance of your bot with all dependencies before anything is cached, is not duplicated for each shard.
Users which are shared with guilds of different shards aren't duplicated across caches (because it is one collection for users, instead of one for each shard).

It is easier and more efficient to manage, in that to perform simple tasks you do not have to broadcast eval to all shards, and do the computations to eliminate duplications from your results. For instance, getting the number of unique users your bot has across all shards.
It is easier to implement for the bot dev. Work In Progress implementations/PRs from @GusCaplan has been as easy as setting the client option shardCount to an integer (number of shards) or as the string 'auto' to automatically determine how many internal shards should be created.
Still has the benefit of Traditional sharding over not sharding, in which if a websocket disconnects or receives a 1000 code and cannot reconnect or resume, the other shards remain up and unaffected by the outage.

Drawbacks:

Not viable for large/very large bots due to the single threaded nature of JavaScript. Such bots should use traditional sharding.

Sizes in this issue are based on the frequency of events handled, not via number of guilds.

This seems good, shouldn't be too hard to implement once the WebSocket rewrite is merged into master as it's mainly just a case of creating more WebSocketConnections 👍

So will bots be auto-shardingnow or will the option to turn on / off internal sharding be a thing?

+1

this is being handled by #1501

@DiscordDonut That would probably be true. I don't see any reason why it would be turned off by normal.

It would be turned off by default because it's dumb.

Is this still in progress?

look at the Internal Sharding branch, this branch is currently in testing of some bots from D.js staff and after they are sure that it works correct without bugs they will merge it into master.


cloudsql-proxy container in initContainers

Can I use cloudsql-proxy container in initContainers ?
(to be sure that an app container runs after cloudsql-proxy container is ready)
I tried to apply it.. but it does not work.
The state of the container is running, but ready status of status.initContainers is false.
NAME   READY   STATUS  RESTARTS  AGE
pod-name-~~~~~~~~~~~~   0/1  Init:0/1 0  18m

and kubectl describe pod
Init Containers:
  cloudsql-proxy:
    Container ID:	docker://206df4f386eed57b39817b3acc834d05b348dd5189016f99697f17862fc9034a
    Image:		gcr.io/cloudsql-docker/gce-proxy:1.11
    Image ID:		docker-pullable://gcr.io/cloudsql-docker/gce-proxy@sha256:5c690349ad8041e8b21eaa63cb078cf13188568e0bfac3b5a914da3483079e2b
    Port:		<none>
    Command:
      /cloud_sql_proxy
      --dir=/cloudsql
      -instances=devsisters-web:asia-northeast1:web=tcp:3306
      -credential_file=/secrets/cloudsql/credentials.json
    State:		Running
      Started:		Thu, 01 Feb 2018 15:08:49 +0900
    Ready:		False
    Restart Count:	0
    Limits:
      cpu:	1
    Requests:
      cpu:		30m
    Environment:	<none>
    Mounts:
      /cloudsql from cloudsql (rw)
      /etc/ssl/certs from ssl-certs (rw)
      /secrets/cloudsql from cloudsql-instance-credentials (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-lgdl4 (ro)

and kubectl get pod pod-name-~~~~~ --template '{{.status.initContainerStatuses}}'
[
  map [
    ready:false
    restartCount:0
    state: map [
      running: map [
        startedAt:2018-02-01T06:08:49Z
      ]
    ]
    containerID: docker://206df4f386eed57b39817b3acc834d05b348dd5189016f99697f17862fc9034a image:gcr.io/cloudsql-docker/gce-proxy:1.11
    imageID: docker-pullable://gcr.io/cloudsql-docker/gce-proxy@sha256:5c690349ad8041e8b21eaa63cb078cf13188568e0bfac3b5a914da3483079e2b
    lastState: map[ ]
    name:cloudsql-proxy
  ]
]

@KrustyHack Thank you!!
I already solved this issue by idea 1.
But I didn't know that Idea 2 is possible because I didn't know dns-pod-service T^T.
I think Idea 2 is better. I'll apply it to my apps.


Add nasm and yasm assemblers?

I frequently run into projects that require nasm and/or yasm assemblers to build, so this could be a useful addition, plus it only weighs about 20MB on the Debian image.

Do you have a couple open source example projects you could share
(especially for posterity's sake)?

The largest open-source project i've ran into that requires it would be ffmpeg and its defendant library, libx264, both of which require them to compile.

https://git.ffmpeg.org/gitweb/ffmpeg.git
https://git.videolan.org/?p=x264.git

Interesting -- I hadn't really considered this being a base for building software generically; here's the description of what buildpack-deps contains that we use on https://hub.docker.com/_/buildpack-deps/:

It includes a large number of "development header" packages needed by various things like Ruby Gems, PyPI modules, etc. For example, buildpack-deps would let you do a bundle install in an arbitrary application directory without knowing beforehand that ssl.h is required to build a dependent module.

(See also the "What's included?" section further below, which goes into more detail.)
Are there any popular language modules (Gems, etc) which require nasm or yasm for building?

Closing for now, but to be clear, if we can find a ~decent number of example language modules using nasm or yasm I'm open to rediscussing:

Are there any popular language modules (Gems, etc) which require nasm or yasm for building?


[Model Update]: PayloadEntity incorrect in TimeSeriesReference

Update Reason
PayloadEntity in model TimeSeriesReference should extend TimeSeriesEntity.
example:
:PayloadEntity a bamm:Entity;
samm:extends samm-e:TimeSeriesEntity ;
MS1 Criteria

[ ] The model that should be updated exists
[ ] The referenced use case exists
[ ] The potential updates are discussed with all stakeholders
[ ] A decision on versioning was made in consensus with the affected parties according to the guidelines.
[ ] The potential update will be either

[ ] backward compatible or
[ ] a (chain of) migration strategy(-ies) from all non-deprecated previous versions to the new model will be developed

[ ] A modeling steward has been assigned

@TobiasHamacherDLR could you please check this request.Entity declaration needs to be corrected. I have specified the solution also.

Model Deprecated.


Parallel tests

Coverage increased (+0.1%) to 83.212% when pulling 1a6c8f86572291911237e3df620a6959545f6527 on rust-av:parallel_tests into 66b4cd97db77ac5be38088f4048060b83fd7bcd1 on xiph:master.

Ok, this way seems to make travis happy, I'd squash and merge.

squash please

I'd push it today if nobody is against it.

Please do


OCPQE-17759 fix get advisory issue on 4.12

this issue is introduced by OCPQE-17717, in 4.12 build data, it does not have parent assembly defined. so no inherited assembly. in OAR CLI code, we need to add this json key check, thanks for reporting this

/approve


Remove loglevel

Remove loglevel
Replace usage of loglevel with console

There's not really a point to this dependency; I think it's a leftover from when the various messages were logged in the extension inpage script.

@whymarrh it's already impossible for consumers to (in a general way) influence what the provider logs, and I think that's a good thing. If we ever were to use info and/or debug logging in this package, loglevel would of course be useful, but we don't, and I don't know of any plans to do so.
Our only usage of log in the extension's inpage script, meanwhile, are a couple of useless debug messages that we could also get rid of: https://github.com/MetaMask/metamask-extension/blob/develop/app/scripts/inpage.js/#L76-L80
In short, I believe I understand the benefits you are suggesting, but they seem highly hypothetical to me. If the need to control the logging that happens in production arises, we can always reintroduce loglevel at that time.

it's already impossible for consumers to (in a general way) influence what the provider logs
We literally do this today in the inpage script though 😕 That's what setDefaultLevel does.

Note that we're not the only consumers of this package. Our recommendations to extensions that want to interact with MetaMask is to use this package, for example.

I do agree that we should try to drop this as a dependency (both here and in inpage.js), but the idea of passing in the log object as a parameter to allow consumers to conditionally disable logs is not without merit.

Ah, my apologies, confusion over the overloaded (just in my brain?) term "consumers".
I was reading and using it in the sense of API consumers, not consumers of the package. 🤦
I'll follow up with a PR that implements my understanding of Whymarrh's suggestion of a constructor argument.


[Bug Report] Cannot seek in long network videos

First, thanks for the awesome work!
The problem arises when you play long network video. Seeking in the video is not working it just continues to play.
Flutter (Channel stable, 3.7.11, on macOS 13.3.1 22E772610a darwin-x64, locale en-GB)

Can you provide more information:

Do you have the same behavior with media_kit_test?
What size / length is the video stream?
What format / codec the video stream use?
Does the server distributing the video stream support seeking? (e.g. 206 Partial Content...)

media_kit_test behave correctly no issues there
Video is streamed from google apis photos library so whethever that gives

will get more info when i get to it.

media_kit_test behave correctly no issues there

Copy the SeekBar from media_kit_test into your app, your problem might be a bad implementation in your UI.

Bug in your code then.


Update specs2-core, specs2-scalacheck to 5.0.6

Updates

org.specs2:specs2-core
org.specs2:specs2-scalacheck

from 5.0.0 to 5.0.6.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (5.0.0).
You might want to review and update them manually.
build.sbt

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.specs2" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Coverage decreased (-2.8%) to 91.975% when pulling 405b4a118b678b21fc664e8a0157f48e0297e809 on scala-steward:update/specs2-core-5.0.6 into 6d0e09cb4eba1784601b6b114c1126fde31dd7e8 on iheartradio:master.