force:package:version:create:report command with --json flag returns array of statues

Summary
If you execute the force:package:version:create:report with the --json flag, the result will be something like the following.
{
  "status": 0,
  "result": [
    {
      "Id": "08c1O000000fxTTQAZ",
      "Status": "InProgress",
      "Package2Id": "0Ho1O000000GmaESAP",
      "Package2VersionId": null,
      "SubscriberPackageVersionId": null,
      "Tag": null,
      "Branch": null,
      "Error": [],
      "CreatedDate": "2019-06-01 06:10"
    }
  ]
}

The issue is that the result attribute is showing as a JSON Array and not a JSON Object.  The implication is that there can be multiple package version create processes.
This was originally reported in January 2018 on the "Unlocked Packages and Managed 2GPs" Trailblazer Group.  Bug ticket W-4621618 was opened for this issue.
I can confirm that it is still occurring and needs to be fixed.
Steps To Reproduce:

See summary above

Expected result
JSON attribute result should be a JSON Object
Actual result
JSON attribute result is returned as a JSON Array

It should be noted that the force:package:version:create command with the --json flag produces the same type of JSON object for the package version create process but the result attribute of the overall response in this command is simply the package version create process response JSON object and not a JSON array containing the package version create process response.
{
  "status": 0,
  "result": {
      "Id": "08c1O000000fxTTQAZ",
      "Status": "InProgress",
      "Package2Id": "0Ho1O000000GmaESAP",
      "Package2VersionId": null,
      "SubscriberPackageVersionId": null,
      "Tag": null,
      "Branch": null,
      "Error": [],
      "CreatedDate": "2019-06-01 06:10"
    }
}

@sfdc-db-gmail can you please take a look at this issue? I think it is a packaging bug.


Add options to reduce manual work in e2e JetStream benchmark tests.

Description
Add the inference_server and inference_benchmark_test configs so folks don't have manually modify those files for benchmark testing.
The default behavior shouldn't change. For testing, folks can override the config values to control the behavior of the server.
Tests
TBD
Checklist
Before submitting this PR, please make sure (put X in square brackets):

[ x] I have performed a self-review of my code.
[ x] I have necessary comments in my code, particularly in hard-to-understand areas.
[x] I have run end-to-end tests tests and provided workload links above if applicable.
[x] I have made or will make corresponding changes to the doc if needed.

Tested manually in cluster to have verified the change. Can someone approve the PR? Thanks.


Fix build on CI

Fix build on CI

@dtantsev this task is yours. Please - give a voice when you started

@vkuchyn i've just started. Bug method found. I'll try to fix

@vkuchyn: fixed. Please, review


Graph theory in Nit

As mentioned in issue #1386, I would like to introduce a graph theory module in Nit.
The pull request is not finished yet, but I would like your input about what is already done.
@Morriar : any comment about the documentation style is welcome!

@privat and @R4PaSs: Thank you both for the review, this really helps!
Comments I agree with:

[ ] Should be AbstractDigraph[V] instead of AbstractDigraph[V: Object]
[ ] No newline in to_s
[ ] Call escape_to_dot in to_graphviz
[ ] Use a more efficient data structure for the queue in a_shortest_path
[ ] HashSet[V] instead of HashMap[V, Bool]
[ ] Change loop-end by while-do-end in a_shortest_path and distance methods
[ ] index_to_vertex: HashMap[Int, V] should be index_to_vertex: Array[V]
[ ] Remove useless QueuePair class
[ ] Rename to_graphviz by to_dot
[ ] One-line short functions

Comments I would like to discuss:

Additional class for preds and succs. @privat: I see your point, but since these variables are private, I feel that an additional indirection is not necessary and would make the code less efficient for a small gain in readability. The concrete class HashMapGraph should not be touched much after defining the basic operations. I would tend to keep it as it is now.
fun vertices: RemovableCollection[V] could make users invalidate the data structure. I agree that the user should not have the possibility to change the data structure. @privat: What would be the best solution? Clone it? Or maybe this is a case where a read-only iterator should be provided to iterate over each vertex.

Other idea: distinguish the read and the readwrite interface (as it is done with some collections for instance).
This way, most algorithms could be implemented in the read version (because they only need to query the graph) thus allowing ad hoc user-defined subclasses to only provide the query methods (I'm not sure if what I am saying is clear).
A use case could be some specific user data classes witch can be seen as a graph (eg a graph of wiki pages in a wiki engine). Then the user can chose to implement a view of this data structure (a view is a thin object that fulfill a specific interface but redirect the queries to real objects). While the view can redirect has_vertex or has_arc to the real data structure, it will be unpratical to have to implement add_vertex and cie because adding a vertex must pass trough the real data structure.

Updated task list:

[ ] Should be AbstractDigraph[V] instead of AbstractDigraph[V: Object]
[ ] No newline in to_s
[ ] Call escape_to_dot in to_graphviz
[ ] Use a more efficient data structure for the queue in a_shortest_path
[ ] HashSet[V] instead of HashMap[V, Bool]
[ ] Change loop-end by while-do-end in a_shortest_path and distance methods
[ ] index_to_vertex: HashMap[Int, V] should be index_to_vertex: Array[V]
[ ] Remove useless QueuePair class
[ ] Rename to_graphviz by to_dot
[ ] One-line short functions
[ ] Change vertices method's signature (should return Collection[V])
[ ] num_vertices and num_arcs should be abstract methods
[ ] Divide the services between read-only and read/write

Updated task list:

[ ] index_to_vertex: HashMap[Int, V] should be index_to_vertex: Array[V]
[ ] num_vertices and num_arcs should be abstract methods
[ ] Divide the services between read-only and read/write

Pull request is now almost finished.
I took into account all comments below. I also changed arcs so that they now store values by default (Arc[V] is now Arc[V,A]). I documented each function.
To make the contribution smaller, I also removed one of the concrete implementation, which was not working anymore. I plan to add it later.
The only elements remaining now are the following:
[ ] Document the two modules
[ ] Remove the digraph_test.nit file
I'm also dissatisfied with the add_arcs function:
# ~~~
# import digraph
# var g = new HashMapDigraph[Int, nullable Int]
# var arcs = new Array[Arc[Int, nullable Int]]
# arcs.add(new Arc[Int, nullable Int](0, 1))
# arcs.add(new Arc[Int, nullable Int](1, 2))
# arcs.add(new Arc[Int, nullable Int](1, 2))
# g.add_arcs(arcs)
# assert g.num_arcs == 2
# ~~~
fun add_arcs(arcs: Collection[Arc[V, A]])
do
        for a in arcs do add_arc(a.source, a.target, a.value)
end

Do you have any idea how one could add multiple arcs in one line, something like:
import digraph
var g = new HashMapDigraph[Int, nullable Int]
g.add_arcs([[0,1],[1,2],[2,3]])

seems a good idea, but I would have to check if each small lists has 2 or 3 elements according to whether there is a value on the arc or not.

@privat : Thank you for the good comments. I'll update a fix soon.

Maybe the Digraph abstraction can implement some kind of collection.
I'm thinking at some useful services like is_empty or iterator.

nice. I do not see more things to say.

@privat: A last question. I decided to bound the generic type V by Object, since allowing nullable objects would make some algorithms more complicated for almost no gain. Does it seem reasonable to you?

Object instead of nullable Object is fine enough

A lot of nitunits are failing. You should consider checking them with the nitunit tool.

@privat: I know. But I can't use nitunit right now since it's broken on MacOS (same bug as in issue #1623).

Sorry, I was wrong, it actually works, this was a different problem. I mean, there is still the bug of issue #1623, but it doesn't prevent me from using nitunit.

@privat: I've got an error that I don't know how to fix. Now, all unit tests pass except for 3 due to the same error:
abstract_digraph.nit:141,2--153,0: ERROR: nitunit.abstract_digraph.abstract_digraph::AbstractDigraph.abstract_digraph::AbstractDigraph::arcs_itera
tor (in .nitunit/abstract_digraph-10.nit): Runtime error: Uninitialized attribute _graph (abstract_digraph.nit:527)
-------------------------------------------------
--   Stack Trace   ------------------------------
-------------------------------------------------
` fatal_exit
` abstract_digraph#ArcsIterator#graph (abstract_digraph.nit:527)
` NEW_abstract_digraph__ArcsIterator
` abstract_digraph#AbstractDigraph#arcs_iterator (abstract_digraph.nit:141)
` abstract_digraph-10#standard::Sys#main (.nitunit/abstract_digraph-10.nit:6)
` main
-------------------------------------------------
 (error)
                # Returns an iterator over the arcs of this graph
                ^

As I understand it, it says that the graph attribute of ArcsIterator is not initialized when I call it from the method arcs_iterator of AbstractDigraph. However, it is not the case, since I call it with self as an argument for graph. What am I missing here?

@ablondin this is a common error about object initialization when the initial value of an attribute rely on the value of another attribute. The order of the initialization is therefore important.
The current specification about object construction is that attributes with a default value are initialized before attributes that are user-initialized.
In your code, ArcsIterator::graph is user-initialized, but ArcsIterator::sources_iterator have a default value. therefore sources_iterator is initialized first.
Unfortunately it requires graph that is not yet initialized.
For more details, the initialization of attributes with a default value is done in a C function called NEW_$classname that is the first step of object construction.
You can see in the stack trace that graph is invoked by NEW_abstract_digraph__ArcsIterator. It means that an attribute with a default value called graph before the first step of initialization is finished. It is then easy to look in the definition of the class if there is some attributes that use graph in their default value.
There is several way to solve this problem. A simple one is to remove the default value from sources_iterator and manually initializes it in the init; so something like:
private var sources_iterator: Iterator[V] is noinit
init do
   sources_iterator = graph.vertices_iterator
end

Another solution is to use the unpopular annotation lateinit.
private var sources_iterator: Iterator[V] = graph.vertices_iterator is lateinit

This annotation explains that the default value has to be computed in the second step of the initialization, with user-initialized attributes.
The first reason that this annotation is unpopular is that the order of attributes in the class is important: sources_iterator must be declared after graph (or else you will have the same error).
The second reason that this annotation is unpopular is that it might cause un-POLA side effects in subclasses that tries to use the autoinit annotation.

A small update:

Iterators working
Classes renamed
Minor restructuration

The only remaining point is adding module documentation!

great!

@Morriar: I started documenting the module. It is not complete yet, but I have some questions before I can continue.

How can I reference a picture to be included in the documentation. I tried it (check in the header of the digraph.nit file, where I follow the Markdown syntax), but it doesn't work.
How can I add a link to some class. For instance, if I want to tell the reader to look at class X for further details, how can I create a real link to the documentation of this class?
I first documented the module in a README file, but I don't know where to find the result of this particular file when I generate the documentation with nitdoc. Where should I look?
How much should I document the class? I can write a small tutorial on graph theory, but maybe it's too much...

@ablondin:

Images are recognized by markdown like you used them, but for now we don't import external files into the outputed documentation. An easy workaround would be to link directly the image to Github.

There is three possible ways to do that:

[[MyClass]]
`MyClass`
MyClass

Feel free to commit a beta version of the documentation if you want us to give an eye.
The three do the same thing but only the first one is implemented in READMEs right now :)

READMEs are used as the default documentation for a group.
For example, the standard/README.md is rendered as http://nitlanguage.org/doc/stdlib/group_standard.html
If you want to access the generated API documentation (not the one from the readme) you should check at http://nitlanguage.org/doc/stdlib/api_group_standard.html

When documenting classes, the most usefull informations are:

What does this class?
How can I instantiate this class (example)?
What are the main methods to look at.

In your case, I guess that the small tutorial on graph theory can be written in the module documentation since it's the one that introduce all the concepts in the module.

Thanks @Morriar. Could you elaborate more about linking images on Github? I'm not sure I understand what you mean? Using an absolute link? I think the links on Github change with the version, so that I wouldn't be safe...

@ablondin You can use the link to master one the project is merged it should be stable enough untill we know what to do with external resources files.
https://github.com/privat/nit/blob/master/my/file.png

Just pushed another version, which should be final. Here are the latest changes:

I moved the part computing the strongly connected components with Tarjan's method to a private class, to avoid creating private attributes for any digraph, even if it doesn't use the method;
I squashed all commits to a single one;
I finished documenting the module (@Morriar: could you check it again if you have time);
I added a license;
I removed useless whitespaces.

Pretty and cool, +1

There are two failed checks and I don't understand them...

"Signed-off", which is in the commit?!?
The license added in the header seems to make nitunit fail. Why is it wrong? I copied/pasted the header of another file, so it should be ok, right?

For the header, remove the dash at Line 16. Sorry Imiss this in the review.

for the signed-off-by issue: the author is

Signed-off-by: Alexandre Blondin Massé<EMAIL_ADDRESS>
but the signed-off-by line is

Signed-off-by: Alexandre Blondin Massé<EMAIL_ADDRESS>
Since the the email is not the same, jenkins complains

+1 for me

Reroll:

@Morriar: I took your comments about documentation intro consideration. Please tell me if it seems ok to you;
License check should be ok now;
Signed-off-by should be ok also.

Tests are fine, I was playing with #1639 that has a side effect on the last run

Reroll:

Last typo suggested by Morriar
Removed useless png file from directory.

Finally, all tests pass!


RNWeb: Add touch handling and fix render loop

On the road to #200 !

Added touch events
Fixed rendering by introducing requestRedraw and fixed render loop
Fixed initial props (mode)
Fixed redraw when Skia Values change

This PR is based upon #554 (identifier on touch points) so wait with review until that one is merged into main to reduce the number of changes in this PR!

Can we write test for this feature?

Looks fantastic.
The render loop improvement look great.
Part of this PR, you could make the webapp content non scalable in index.html:
<meta name="viewport" content="width=device-width, user-scalable=no">


Add iOS debug symbols to release assets

Is your feature request related to a problem? Please describe.
It would be beneficial to users if we include the iOS debugging symbols (dSYM file) in our release assets. This would allow users to better debug stack traces from crashes they encounter when using the MapLibre library.
Describe the solution you'd like
The release build process (for iOS) should include generating the debugging symbols (dSYM file) and the symbol file should be included in the published release assets.
Describe alternatives you've considered
The alternative would be for the user to download the source from the release and build the debug symbols, but they won't match the release binary exactly unless the UUID matches, which would take a number of factors (e.g. XCode version, Mac OS version)  as well as some non-deterministic factors such as build timestamps and number of cores on build system.
So I believe building/publishing the matching debug symbols for our release binaries is the best path forward for our users.
Additional context
This request is specifically for iOS, but we should look at doing the same for our other supported platforms as well.

https://github.com/bazelbuild/rules_apple/blob/master/doc/common_info.md#output-groups-output_groups

I can distribute these files alongside releases:
  bazel-bin/platform/ios/MapLibre.dynamic_dsyms/MapLibre_ios_device.framework.dSYM/Contents/Resources/DWARF/MapLibre_ios_device
  bazel-bin/platform/ios/MapLibre.dynamic_dsyms/MapLibre_ios_device.framework.dSYM/Contents/Info.plist
  bazel-bin/platform/ios/MapLibre.dynamic_dsyms/MapLibre_ios_simulator.framework.dSYM/Contents/Resources/DWARF/MapLibre_ios_simulator
  bazel-bin/platform/ios/MapLibre.dynamic_dsyms/MapLibre_ios_simulator.framework.dSYM/Contents/Info.plist`

@cgalvan iThe iOS dSYM file is about 150MB and the one for the simulator is 300MB. Do you need both?

@louwers We should only need the dSYM file for device. When running in simulator we should be able to already get proper debugging.


added batch-faq.md

@laurenhughes - if you decide you want to keep this content, we'll need to move the commits to the private repository so we can use Acrolinx, validation, and staging. thanks.

@Jak-MS - Thanks for looking into the PR. Please let me know if any changes required.

Coordinating internally
#please-close


Training loss is NaN now.

When will the latest version of the code and data processing code be released?

Thanks for your interest. Is the training loss NaN at the beginning, what dataset did you use? The latest version of the code may not be released so soon. We will prioritize the release of data processing code and the integration of ConsisID into diffusers.

Thanks for your interest. Is the training loss NaN at the beginning, what dataset did you use? The latest version of the code may not be released so soon. We will prioritize the release of data processing code and the integration of ConsisID into diffusers.

I downloaded your dataset and processed it appropriately, using CogvideoX-5B-I2V to initialize the weights，which bs is 5 and lr is 3e-7. It has loss in the initial training, but NaN appears after about 500 iterations. Is it because I processed the data wrong? And “fail to detect face using insightface, extract embedding on align face“ occurs during training。

Oh, I see. This may be a problem with MM-DiT. The training is very unstable because the activation value of the middle layer may be very large, resulting in loss NaN. You can try turning on EMA, gradient accumulation, increasing batchsize, and reducing the learning rate. Another method is to add a regularization term to the output of the middle layer.

fail to detect face using insightface, extract embedding on align face this warning cannot be avoided because facexlib may not be able to detect the face, and the code will automatically skip this training sample.

or you can try to train only LoRA instead of all parameters.

Oh, I see. This may be a problem with MM-DiT. The training is very unstable because the activation value of the middle layer may be very large, resulting in loss NaN. You can try turning on EMA, gradient accumulation, increasing batchsize, and reducing the learning rate. Another method is to add a regularization term to the output of the middle layer.

we have release the data processing code

When will the latest version of the code and data processing code be released?

we have release the data processing code, please refer to here for more details.

or you can try to train only LoRA instead of all parameters.

Oh, I see. This may be a problem with MM-DiT. The training is very unstable because the activation value of the middle layer may be very large, resulting in loss NaN. You can try turning on EMA, gradient accumulation, increasing batchsize, and reducing the learning rate. Another method is to add a regularization term to the output of the middle layer.
Hi! If train only LoRA instead of all parameters, what is the demanded amount of training data and the number of training iterations?

Thanks for your interest. Is the training loss NaN at the beginning, what dataset did you use? The latest version of the code may not be released so soon. We will prioritize the release of data processing code and the integration of ConsisID into diffusers.

I downloaded your dataset and processed it appropriately, using CogvideoX-5B-I2V to initialize the weights，which bs is 5 and lr is 3e-7. It has loss in the initial training, but NaN appears after about 500 iterations. Is it because I processed the data wrong? And “fail to detect face using insightface, extract embedding on align face“ occurs during training。

Hi! Have you solved this problem? I meet the same issue and wonder which way to avoid loss NaN.

Thanks for your interest. Is the training loss NaN at the beginning, what dataset did you use? The latest version of the code may not be released so soon. We will prioritize the release of data processing code and the integration of ConsisID into diffusers.

I downloaded your dataset and processed it appropriately, using CogvideoX-5B-I2V to initialize the weights，which bs is 5 and lr is 3e-7. It has loss in the initial training, but NaN appears after about 500 iterations. Is it because I processed the data wrong? And “fail to detect face using insightface, extract embedding on align face“ occurs during training。

Hi! Have you solved this problem? I meet the same issue and wonder which way to avoid loss NaN.

You may need to construct a higher dataset to continue finetuning ConsisID, or have a larger batch size. Since ConsisID is trained on a higher quality internal dataset, if it continues to be trained on the ConsisID-Preview-Data, it is likely to get worse.

Or you can load the ckpt of CogVideoX-5B-I2V for training IPT2V from scratch. (Instead of load ConsisID-Preview for continue finetuning.)

Some solutions can refer to https://github.com/PKU-YuanGroup/ConsisID/issues/31.

Thanks for your interest. Is the training loss NaN at the beginning, what dataset did you use? The latest version of the code may not be released so soon. We will prioritize the release of data processing code and the integration of ConsisID into diffusers.

I downloaded your dataset and processed it appropriately, using CogvideoX-5B-I2V to initialize the weights，which bs is 5 and lr is 3e-7. It has loss in the initial training, but NaN appears after about 500 iterations. Is it because I processed the data wrong? And “fail to detect face using insightface, extract embedding on align face“ occurs during training。

Hi! Have you solved this problem? I meet the same issue and wonder which way to avoid loss NaN.

I try a larger batch size and solve this problem.


Visual range isn't reporting correctly

As per rogueticket-467, visual range isn't calculating properly for the green mark icon. See the images below.
Important to note:
the icon shows the lack of visuals, although the opponent is inside the range
no enemy EWS or jamming except c3 slave(destroyed)
enemy lance consist
grasshoper ghr-c with c3 (destroyed)
hollander II bzk-f5 - no ews or stealth
griffin grf-3m - no ews or stealth
archer arc-2r - no ews or stealth
Also, another my mech can use the shared visual from LAM(it has related equipment ), and see a chance of hitting the mech with a red eye icon before moving

Fixed in 1.0.0


Cannot calibrate tracker pose correctly

Hello,
I cannot calibrate tracker pose correctly. Everytime, the tracker's location is ok in xz position, but the z position is completely off. Here is my setup : http://imgur.com/0UP5lnZ and http://imgur.com/iTOiw9R
After calibration, here is what i have (the psmove is still attached to the hmd) : http://imgur.com/Aw0fQXJ
The pseye is correctly calibrated, but his estimated position is far too low.

I came across this issue too when I was writing up the camera calibration docs on Friday. The calibration mat method now works, but the HMD coregistration method is still broken (issues between using the raw HMD transform data vs. Chaperone Relative transform data from SteamVR ). I'll try and get that fixed by EOD Sunday and get a new binary release up.

Alpha release #2 is up with fixes that should ake care of the issue you were seeing.


get_revision doesn't work properly with multiple sources in the repository

I had to change the 'get_revision' method to work properly iterate over the revisions in a changeset and return the max (latest) one:
    def get_revision(self):
        maxRevision = 0
        try:
            for set in self._data["changeSet"]["revisions"]:
                maxRevision = max(set["revision"], maxRevision)
            return maxRevision
        except KeyError:
            return maxRevision

A key error was also produced sometimes, not sure why this was.

First of all, can you post the traceback, that would be very helpful.
Which source-control system were you using? How did you set it up?
I wonder if zero is the best default (e.g. in case that no SCM system is being used), perhaps we ought to throw a custom exception. Any suggestions on this?
Lastly, you have a variable called "set" - that's unintentional, right?

We're using SVN.  I'll see if I can grab a traceback of the KeyError, but the cause is the lack of the 'revision' key in the 'set' dictionary.
I should probably set the default to "None", not 0, but I was just trying to get things running first.  I chose 0 because the revision number is typically an int.  I'm not sure if you want to make this work for git as well, but I don't have a git repo in Jenkins to test against.
As for the use of the variable 'set', that really rubbed me the wrong way too.  I'm afraid that came from the jenkinsapi package (https://github.com/salimfadhley/jenkinsapi/blob/master/jenkinsapi/build.py#L36).

As for the variable, that's definitely our fault. We need to fix that!
If you are not in any desperate hurry for a fix, lets wait a moment for other members of the team to weigh-in on this issue.
It occurred to me that the get_revision function ought to return a dict of repo-name to version number. If no repository information is available then we should raise a new kind of Exception.
The reason I object to zero as a default is that in some SCM systems it might be a valid revision number for an (empty) repo.

Sure, I agree, make it work for general cases.
I'm not in a hurry, I have a fix in place at the moment.  It would be nice to have it fixed in the package.
Also, it'd be nice if the API had a 'get_last_good_revision' method.  I wrote my own and can share if it others want it.
It also occurs to me that git might have to be a special case here.  I'm not sure if you have a quick/easy way to get the most recent revision in the same way since git uses hashes.

In my original Google Code version I had a "get_last_good_build" function.
I've got no objection to a helper-function which gets the last good revision. I think we'd have to make sure that the case for multi-repo is handled consistently with that of single-repo, especially the return type.

Hey,
Thanx for the report. Can you open a pull request for the additional method ? last_good_revision sounds reasonable, but could also be called by doing get_last_good_build().get_revision()
We definitly need to fix the use-case with multiple repositories, I'll see if we can create a test project to test against.
Would you happen to know which revision is exported as the SVN_REVISION env var by jenkins?
It would make the most sense to follow jenkins behaviour in the default case and maybe expose an additional method in the api to get at a revision dictionary for multiple repos for all non-default cases.....
Your input is highly appreciated, I'd like this to work for as many use-cases as we can get it to work......

I prefer get_last_good_build().get_revision()
Kavehv, It would be nice to get a release out early next week, so feel free to follow Ramon's advice and I will get it all pushed out.

Unfortunately, the SVN plugin for Jenkins doesn't export SVN_REVISION when there are multiple SVN sources (not sure why).  Instead, it exports SVN_REVISION_n where n is the number of the SVN source for the build.
As far as last_good_revision(), my workaround was to do exactly what you'd mentioned, get_last_good_build().get_revision().
Did you want me to open a pull request for the method I posted here or the last_good_revision() method?


Can I make a list of tags on a page?

How to make a list of tags on a page? Or it is not available yet? Thanks.

+1 here
I was trying to use instruction https://blog.many-monkeys.com/adding-a-tags-page-to-ghost-blog/ but stuck because there is no site-nav.hbs file in theme.
Maybe there is any method to create custom tag page with all tags on site?

+1 here
I was trying to use instruction https://blog.many-monkeys.com/adding-a-tags-page-to-ghost-blog/ but stuck because there is no site-nav.hbs file in theme.
Maybe there is any method to create custom tag page with all tags on site?

I think this theme hasn't supported this feature yet. We can write our own tags page, but it needs a little bit of coding.

@gaolingxiao We don't have any page for listing tags on our themes. There are numbers of tutorials for this topic which users can follow and include on their sites.
@koznov The important part of the tutorial is the following section which loops through the available tags and outputs them with post counts.
{{#get 'tags' limit='all' include='count.posts' order='count.posts desc'}}
    {{#foreach tags}}
        {{!-- The tag below includes the markup for each tag - partials/tag-card.hbs --}}
        {{> "tag-card"}}
    {{/foreach}}
{{/get}}

site-nav.hbs isn't something that is mandatory. For example, you can copy page.hbs to page-tags.hbs (as in the tutorial) and replace {{#post}}{{/post}} part with the code above.

Why you don't add authors and tags pages by default although it is not complex? I think this will make more funtional this theme. Does it effect SEO?

Why you don't add authors and tags pages by default although it is not complex? I think this will make more funtional this theme. Does it effect SEO?


Gen csr improvements

There are other methods to approach this but I felt this would provide the maximum flexibility without over-complicating the CSR YAML format.

@vogelpi please take a look

@weicaiyang please take a look

One question - from my impression of this code, this legalizes the write-values to the registers, would it be difficult to expand this to actually do the same for the expected response values?
To make an example: write b'01 to a bitfield that accepts only b'11 or b'00,
In this case we could (depending on cpu behavior) read a value where there is no change to the bitfields as the written value is not a legal value.

One question - from my impression of this code, this legalizes the write-values to the registers, would it be difficult to expand this to actually do the same for the expected response values?

It already does this. The legalized value is used by gen_csr_test to predict the next read value of the CSR.
However the python fragment has no access to the old field value and it should do as according to the RISC-V spec:

Implementations can return any legal value on the read of a WARL field when the last write was of
an illegal value, but the legal value returned should deterministically depend on the illegal written
value and the architectural state of the hart.

Really it should have access to all other field and CSR values too. For now I think we should keep it simple and I'll add something that gives the python fragment access to the old field value. Should anyone need something more sophisticated they can open a new PR to add it.


Seek with negative offset does not work

Hi,
seeking to an offset relative to the end of the file does not work, sample code is here: https://gist.github.com/6353f5a1b5861d89844976f72be91ce9
The code uploads a file to a bucket, then calls Seek(-100, 2) and then reads 100 byte.
Expected behavior: Read the last 100 bytes
Observed behaviour: Reads the first 100 bytes
When tracing is on, I can see that the GET request does not have a range header:
GET /bucket-5577006791947779410/file-8674665223082153551 HTTP/1.1
Host: <IP_ADDRESS>:9000
User-Agent: Minio (linux; amd64) minio-go/2.0.1
Authorization: AWS4-HMAC-SHA256 Credential=**REDACTED**/20160808/us-east-1/s3/aws4_request, SignedHeaders=expect;host;x-amz-content-sha256;x-amz-date, Signature=**REDACTED**
Expect: 100-continue
X-Amz-Content-Sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
X-Amz-Date: 20160808T185713Z
Accept-Encoding: gzip

HTTP/1.1 200 OK
Content-Length: 169484
Accept-Ranges: bytes
Content-Type:
Date: Mon, 08 Aug 2016 18:57:13 GMT
Last-Modified: Mon, 08 Aug 2016 18:57:13 GMT
Server: Minio/RELEASE.2016-07-13T21-46-05Z (linux; amd64)
Vary: Origin
X-Amz-Request-Id: 2A93L1VEPYM5D891

thanks!


fix(components): autoprefixer warning by using flex-start instead of start

Fixes #3003
Replace align-items: start with align-items: flex-start in packages/components/src/components/ScalarCodeBlock/ScalarCodeBlock.vue.

For more details, open the Copilot Workspace session.

🙏


WIP: packages: Add spec files and update scripts

This commit adds the necessary spec files and scripts in order to be able to create
packages in OBS (Open Build System).
Fixes #15

@erick0z -- any updates here?  Its been a few days, and really want to make sure we get this in good shape and merged ASAP.

@egernst this is a huge PR, @jcvenegas and I are fine tuning the scripts and preparing the CI. This PR is almost complete, it just need some minor changes.

sed 's/<EMAIL_ADDRESS>linux-container.install
sed: can't read linux-container.install: No such file or directory

@bergwolf  @sboeuf @laijs @egernst  what is the default qemu will provide qemu-vanilla or qemu-lite?
IMO we should use as default  qemu-lite, but let me know.

@erick0z we need to change the package name of linux-container to kata-linux-container or kata-kernel
Is it enogh to change the package spec name or we need something else?

@erick0z got
docker: Error response from daemon: OCI runtime create failed: qemu-vanilla-system-x86_64: warning: Number of hotpluggable cpus requested (240) exceeds the recommended cpus supported by KVM (160)
qemu-vanilla-system-x86_64: -device virtio-9p-pci,disable-modern=true,fsdev=extra-9p-kataShared,mount_tag=kataShared: 'virtio-9p-pci' is not a valid device model name: unknown.

in alpha repo using  qemu-vanilla

@erick0z and @jcvenegas  https://github.com/kata-containers/documentation/pull/61

Hi @erick0z, @jcvenegas - this is looking good - just a few relatively minor and quick fixes remain I think?
Also, we could consider defer fixing the hard-coded architecutre in files like debian.control for the time being to allow us to have a workable system for a single arch atleast. wdyt @egernst?

@jodh-intel @egernst  please take a new look, I still need to remove the arch hard-coded bits from the golang installation.
But after 100 commits, we now have 74 and not more than 130  :)
we probably could reduce even more the amount of files, but at this point makes me wonder if is easier rewrite it in go or keep refactoring.
One big missing thing is to try to use the yaml from runtime repository.  But that could go in other PR. I am trying to reduce the complexity of this PR.
So for new PRs we should

Use yaml from runtime  ( nice to not need to modify paste versions and hashes in versions.txt)
Fix build for fedora 28 and ubuntu 18 (both are broken due to gcc newer versions and qemu), just need to add a patch to qemu.
Fix Centos builds, recently all the centos builds fails due to linker errors.
Have a solution for qemu package for distros that had old gcc versions.


Style Guide

relevant notes from colin & itamar's audit during the retreat

We can keep a running doc but will wait until it's a burning need to dedicate resources here.

https://www.notion.so/dualityxyz/The-Way-of-Duality-28ed9f59d8ab46019ce37390b4cb5d3a


Pin all lower-level libs to latest versions

:+1:

http://manhattan.ci.chef.co/job/chef-build/264/

Merged as 18f0ee2354ae2539bf63956ef99a37a188ef67eb


Add Conflux eSpace (chain ID 1030)

Description
This PR adds a new chain (eth clone) for the Conflux eSpace, a fully EVM-compatible subsystem of the Conflux blockchain. Users can add Conflux eSpace to Metamask through https://chainlist.org/.
Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[X] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)
[ ] Tests
[ ] Documentation
[ ] Other (for changes that might not fit in any category)

Additional comments
Note that there is a separate app for the original Conflux Core which is not compatible with Metamask.

Closing in favor of #289.


loosing .uns metadata when concatenating

I was facing some problems with metadata in .uns, when I realised that we currently don't seem to have any mechanism that automatically transfers uns labels into obs before concatenating adatas when calling DatasetGroup.adata
I'm wondering whether we should just by default move all uns to obs before concatenating adatas. Couldn't we just add a call to self._set_metadata_in_adata(allow_uns=False) before this line:
https://github.com/theislab/sfaira/blob/58aadc6f9678f83f37587e1eceb6aaea99faa717/sfaira/data/base/dataset_group.py#L318
what do you think @davidsebfischer ?

I think streamline would be better for that? We could just call streamline inside of .adata before concatenating.

we do call streamline a couple of lines up. however streamline doesn't move uns items to obs as far as I can see right now

we do call streamline a couple of lines up. however streamline doesn't move uns items to obs as far as I can see right now

We can just make that optional for format == "sfaira" too and use it in concatenate?

like have another input argument for .streamline(format=="sfaira", allow_uns=False)?

would the cellxgene streamlining respect this attribute as well or should this always be false for cellxgene streamlining?

Cellxgene streamlining needs allow_uns=False because the cellxgene object format is narrowly defined on this. I would not optimise this interface too much though because they might be merged in the future: https://github.com/theislab/sfaira/issues/200.


Switching between VSCode windows with any custom app switcher causes high CPU usage

VSCode Version:
1.18.0
OS Version:
MacOS Sierra 10.12.6

Steps to Reproduce:

Open two VSCode windows (e.g two different projects)
Use any non-default window switcher (Witch, Contexts, etc)
Switch from one VSCode window to another

As soon as you do it for the first time VSCode Helper process with --type renderer will start eating CPU like crazy.
Disabling all extensions or cleaning user config does not help.
I have tested it with Atom and it has the same bug.
So maybe it's Electron issue?
I'm surprised not to find more reports of this. Native cmd-tab is very clunky to use with multi-space and multi-window workflow.
Reproduces without extensions: Yes

related: #41557
Also happens when window-switching (not app-switching) with Karabiner-Elements.
Doesn't happen when switching with CMD+` or via Expose (both are OSX-native).
CPU goes back to normal when a top System Menu Bar item is clicked (no menu command / second menu click is necessary).
I have tried to find this in Electron Issues but could not.
Any ideas how to best debug this? A config in launch.json (secondary VSCode), or via Xcode? I have the PID of the helper process + I'm running from sources.

Initial Electron debug & issue created: https://github.com/electron/electron/issues/12606

@squareduck if you could add a reproduction to that Electron issue with the Window-switcher you are using, it may be easier than what I provided (I assume)


dynastyscans: Modify tests & code to get coverage

Removed a redundant URL slash stripping and changed the tests to test the scraper with a redundant slash in the URL to get 100% coverage

Codecov Report

Merging #44 into master will increase coverage by 0.12%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #44      +/-   ##
==========================================
+ Coverage   97.62%   97.75%   +0.12%
==========================================
  Files          16       16
  Lines        1517     1515       -2
==========================================
  Hits         1481     1481
+ Misses         36       34       -2

Impacted Files
Coverage Δ

cum/scrapers/dynastyscans.py
100% <ø> (+3.4%)
:white_check_mark:

cum/scrapers/batoto.py
94.57% <0%> (-0.78%)
:x:

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 a6bc761...f008663. Read the comment docs.


ABSPATH & Multiple Folder Paths conflict on WordPress.com, Pressable

[X] I've read the guidelines for Contributing to Roots Projects
[X] This request isn't a duplicate of an existing issue
[X] I've read the docs and followed them (if applicable)
[X] This is not a personal support request that should be posted on the Roots Discourse community

I'm Joshua, a support engineer for Automattic. I focus primarily on WordPress.com and our hosted platform.
Recently, we were reviewing some errors related to some WordPress.com sites and found that multiple sites that used software from https://roots.io were having issues due to an extra theme path set using ABSPATH.
We're not sure if this is a user configuration issue or if something that your tools add for your users.
Below, I cover what we found and some notes about ABSPATH on WordPress.com and Pressable.
Issue
We found that some site themes were constructed using tools that https://roots.io/ provide.
It appears that something adds a mu-plugin to the sites calledregister-theme-directory.php.
On each site, this set an improper directory using ABSPATH.
In order to get some functions and features working properly on these sites we had to modify this file to find the directory properly.
We wanted to let you know in the event that this is something that your tools add for your users.
More on ABSPATH
We cover ABSPATH on WordPress.com a bit more at https://wordpress.com/support/incompatible-plugins/#using-abspath-read-on
As mentioned, the plugin under wp-content/mu-plugins/register-theme-directory.php was incorrectly trying to set the default theme directory using ABSPATH.
On WordPress.com, the WordPress Core files are symbolically linked to another location on the platform. In other words, they are not in the site root, as is the case with a standard WordPress install. Due to this, using ABSPATH to locate files in the site can result in errors.
ABSPATH can be used when pointing to Core files, but it will not function correctly if used to locate files/folders within the wp-content directory.
For example, the following on WordPress.com will not work:

if (!defined('WP_DEFAULT_THEME')) {
register_theme_directory(ABSPATH . 'wp-content/themes');
}

However, if it is necessary, it could be changed to:

if (!defined('WP_DEFAULT_THEME')) {
register_theme_directory(WP_CONTENT_DIR . '/themes');
}

This is what was done in this situation. With WP_CONTENT_DIR, files/folders in the site root can be successfully accessed.
For more on ABSPATH, you may want to review one of Automattic's other partners at https://pressable.com/knowledgebase/abspath-and-pressable/ for a more technical overview of properly using ABSPATH.
Issues & Questions
Let us know if you have any additional issues or questions. We'll be happy to help!
Feel free to reply here or use our contact form at https://wordpress.com/support/developers/
Also, if your team needs a WordPress.com Business plan testing environment for testing your tools on, let me know! I'll see if we can coordinate that.

Thanks for the report.
Unfortunately it's not as simple as switching to WP_CONTENT_DIR. Bedrock points the content dir to /app:
https://github.com/roots/bedrock/blob/a3d36b26e8c784139fc68855d03c199647e78fec/config/application.php#L55-L56
This is not the same as ABSPATH . 'wp-content/themes' and would defeat the purpose of the mu-plugin. Here are the paths:

ABSPATH => /web/wp/wp-content/themes
WP_CONTENT_DIR => /wep/app/themes

The ABSPATH usage  is needed to get the location of the themes directory included in WP core (which gets installed by Composer) and not the site's actual content dir.

Below, I cover what we found and some notes about ABSPATH on WordPress.com and Pressable.

it seems like a WP site that was originally created with bedrock was migrated onto a platform where the bedrock structure is no longer used. in this case the register-theme-directory.php mu-plugin shouldn't be used anymore


TypeStr() does not type ASCII characters

With RobotGo 0.70.0 on Arch Linux both TypeStr() and TypeStrDelay() output different chars. TypeStr() seems to drop ASCII chars entirely.
robotgo.TypeStr("山达尔星新星军团, galaxy. こんにちは世界.")
>> 山达尔星新星军こんにちは世
robotgo.TypeStr("hello")
>>

robotgo.TypeStrDelay("山达尔星新星军团, galaxy. こんにちは世界.", 1000)
>> q, galaxy. SkaoL.
robotgo.TypeStrDelay("hello", 1000)
>> hello

Just ran into this using Xubuntu 18.04 LTS and using go version go1.10.4 linux/amd64. Very annoying :(.
The good news is that KeyTap() does work, so a workaround is wrapping KeyTap() into another function:
func DaniTypeStr (str string, interval int){
	for _, v := range str {
		robotgo.KeyTap(string(v))
		time.Sleep(time.Duration(interval) * time.Millisecond)
	}
}
//DaniTypeStr("banana", 300)


perf(remix-server-runtime): use faster alternative to jsesc

Closes: #3854

[ ] Docs
[x] Tests

Testing Strategy:

used a faster version of jsesc to serialize the server handoff very much inspired by what next.js has done here. created a benchmark here (which i also included serialize-javascript and js-string-escape libraries in the comparison for additional points of reference).
results from my machine:
cpu: AMD Ryzen 9 5950X 16-Core Processor
runtime: node v16.16.0 (x64-linux)

benchmark                 time (avg)             (min … max)       p75       p99      p995
------------------------------------------------------------ -----------------------------
escapeHtml             18.35 ms/iter   (17.29 ms … 29.15 ms)  17.98 ms  29.15 ms  29.15 ms
jsesc                    260 ms/iter  (236.51 ms … 340.8 ms) 266.27 ms  340.8 ms  340.8 ms
js-string-escape      103.71 ms/iter  (84.82 ms … 120.28 ms) 107.83 ms 120.28 ms 120.28 ms
serialize-javascript   40.98 ms/iter    (39.17 ms … 49.9 ms)  41.14 ms   49.9 ms   49.9 ms

summary
  escapeHtml
   2.23x faster than serialize-javascript
   5.65x faster than js-string-escape
   14.17x faster than jsesc

the single test failure seems unrelated. i'm also seeing it happen in other prs e.g. https://github.com/remix-run/remix/runs/7671223447?check_suite_focus=true

Going to have to double check, but I believe the serialization method needs to be consistent across machines / runtimes. I.e, serialize(obj) should return the same thing on the server and in the browser. JSON.stringify alone will not suffice here as it does not take into account key order during serialization leading to possible mismatchs on hydration.

Going to have to double check, but I believe the serialization method needs to be consistent across machines / runtimes. I.e, serialize(obj) should return the same thing on the server and in the browser. JSON.stringify alone will not suffice here as it does not take into account key order during serialization leading to possible mismatchs on hydration. Going to need something like json-stable-stringify

according to mdn, https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#description:

Enumerable properties are visited using the same algorithm as Object.keys, which has a well-defined order and is stable across implementations. For example, JSON.stringify on the same object will always produce the same string, and JSON.parse(JSON.stringify(obj)) would produce an object with the same key ordering as the original (assuming the object is completely JSON-serializable).

so my guess is that it would be fine. next.js seem to be getting away with just using JSON.stringify (and JSON.parse on the client).

@jacob-ebey i've added additional benchmarks with json-stable-stringify and some other stable JSON.stringify packages i've found. according to my understanding though (see prior comment), they shouldn't be necessary in this day and age.


Changing branches does not work

Hi,
I'm currently running dotmesh on ubuntu 18.04 with the following docker distro:
Client: Docker Engine - Community
 Version:           19.03.1
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        74b1e89
 Built:             Thu Jul 25 21:21:05 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.1
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.5
  Git commit:       74b1e89
  Built:            Thu Jul 25 21:19:41 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

and switching between branches does not change the state of the app. I also noticed that when I run dm list, I do not have a container listed. I am happy to try to fix this with more guidance.
  DOT           BRANCH    SERVER            CONTAINERS  SIZE       COMMITS  DIRTY
* moby_counter  branch_a  e70342d0c7b32c72              38.50 kiB  1        14.50 kiB

The one in the kata tutorial does have a container listed but it uses an older version of docker.
Thanks!

Can you show the output of docker ps -a?


Add auto-generate sample for DataLakeStore and DataShare

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


default amplify function runtime versions should be the same as aws lambda latest runtime versions

Is this feature request related to a new or existing Amplify category?
function
Is this related to another service?
Lambda
Describe the feature you'd like to request
Amplify CLI currently has these default runtimes:
https://docs.amplify.aws/cli/function/#supported-lambda-runtimes
They are not the same as the AWS lambda latest supported runtimes.
For example, the Amplify CLI defaults to NodeJS version 14.x but AWS Lambda defaults to NodeJS version 16.x.
Describe the solution you'd like
Amplify CLI should stay up-to-date with the AWS Lambda defaults.
Describe alternatives you've considered
Manually altering the cloud-formation-template of the Amplify CLI output.
Manually changing the runtime from the AWS Lambda console.
Additional context
No response
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this feature request

Would this feature include a breaking change?

[ ] ⚠ This feature might incur a breaking change

Hey @renschler :wave: thanks for raising this, and you make a valid point! I'll mark this as a functions feature request for the team to evaluate further 🙂

duplicate of https://github.com/aws-amplify/amplify-cli/issues/11252
closing the issue to prevent any miscommunications and better track this.


Annotations set on a node are not shown on the UI and labels get deleted

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Create a cluster.
Go to Cluster--> Nodes --> Edit --> Labels & Annotations
Add an Annotation.

Expected Result:
Annotations set should be seen on the UI.
Labels set should NOT get deleted.
Actual Result:

In the API request sent, you will see the annotation set.
In the API request sent, Labels is not passed.
Click on Nodes --> Edit --> Labels & Annotations, the labels section is blank and the annotation you set above, will NOT be available.

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): rancher-master - Commit id: 85dedb19b
Installation option (single install/HA): single

Annotation cannot set is not a UI issue.
After clicking edit and add a new annotation: test: "test", respond is 200 status code but in the response body lack of test: "test".

Verified on latest master-head - commit id: 0fed88523
Steps:

Create a cluster.
Go to Cluster--> Nodes --> Edit --> Labels & Annotations
Add an Annotation.
In the API request sent, you will see the annotation set.
In the API request sent, Labels is passed.
Click on Nodes --> Edit --> Labels & Annotations, the labels section is NOT blank anymore, and has the required set of labels.
The annotation you set above, is NOT available.
on kubectl - kubectl get nodes  -o json -- you will NOT see the annotation set

0fed88523 doesn't have the change. Please try to pull the master-head again

verifying on master-head - commit id: a98b70f17
Steps:

Create a cluster.
Go to Cluster--> Nodes --> Edit --> Labels & Annotations
Add an Annotation.
In the API request sent, you will see the annotation set.
In the API request sent, Labels is passed.
Click on Nodes --> Edit --> Labels & Annotations, the labels section is NOT blank anymore, and has the required set of labels.
The annotation you set above, is available.
on kubectl - kubectl get nodes -o json -- you will see the annotation set


Enforce animated layers are always on top

This issue comes from https://github.com/CartoDB/cartodb/issues/7342.
Basically, animated layers will always be rendered on top of other layers (in the map) and we should somehow "enforce"/visually inform users about this in the list of layers. In the editor, we did this by:

Ensuring there's only one "torque" layer per map.
Preventing layers from being drag&dropped above "torque" layers.
Informing users that "torque" layers have to be on top and providing a link to move a layer to the top.

@saleiva @urbanphes, I don't think we have design for this yet... do we?

and heatmap layers!

assigned to follow this one

Here de visual design.

We reserved a this place to put this kind of layers that doesn't move.
cc/ @saleiva

I miss the equivalent of this one on the style form

with the new UI I propose we move the layer automatically. It will be
understood once we have the indicator designed by @urbanphes
2016-07-21 12:24 GMT+02:00 javi santana<EMAIL_ADDRESS>
I miss the equivalent of this one on the style form
[image: screen shot 2016-07-21 at 12 23 42 pm]
https://cloud.githubusercontent.com/assets/30147/17019716/078c831e-4f3e-11e6-87bf-4f057b61806b.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/cartodb/issues/8975#issuecomment-234215411,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIENSMDTelwZQx3-21KY_w9FlWk9IMtks5qX0jYgaJpZM4JPn9J
.

--
Sergio Alvarez Leiva

And also I think we should inform (like the screenshot that @javisantana sent us) when you select animated.

Then I'd use the notifier, but I'd not add another step to the styling workflow since changing the layer order in this case would require to go to the prev. screen

@piensaenpixel taking care of updating the visual language for animated/heatmap layers

Ok. Behaviour implemented in this PR, commits:
https://github.com/CartoDB/cartodb/commit/98d4c87ded1faf3abaea0a8578e6170d9f0a20e9
https://github.com/CartoDB/cartodb/commit/9a1b384b4e68e7c1de4270caf42b0772842ab5a2


RTMPT streaming to red5 doesn't work

I'm trying to stream from Example iOS app to red5 server using rtmpt but the app crashes right after the broadcast is started.
Crashes in RTMPConnection.listen() with EXC_BAD_ACCESS (code=2)
I'm using XCode 8.3.2, iPhone 7 & Red5 Server 1.0.9
Here's the logs:
2017-05-29 19:45:35.757 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPTSocket.swift:259] doRequest > Optional(http://<IP_ADDRESS>:5080/fcs/ident2)
2017-05-29 19:45:35.848 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPTSocket.swift:259] doRequest > Optional(http://<IP_ADDRESS>:5080/open/1)
2017-05-29 19:45:35.849 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPTSocket.swift:185] didIdent2(data:response:error:) > Optional([]):Optional(<NSHTTPURLResponse: 0x17403c500> { URL: http://<IP_ADDRESS>:5080/fcs/ident2 } { status code: 404, headers {
    "Cache-Control" = "no-cache";
    Connection = "Keep-Alive";
    Date = "Mon, 29 May 2017 16:45:35 GMT";
    "Transfer-Encoding" = Identity;
} })
2017-05-29 19:45:35.863 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPTSocket.swift:259] doRequest > Optional(http://<IP_ADDRESS>:5080/idle/NC90BHFCGRG3H/0)
2017-05-29 19:45:35.864 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPTSocket.swift:199] didOpen(data:response:error:) > [78, 67, 57, 48, 66, 72, 70, 67, 71, 82, 71, 51, 72, 10]:Optional(<NSHTTPURLResponse: 0x17002e620> { URL: http://<IP_ADDRESS>:5080/open/1 } { status code: 200, headers {
    "Cache-Control" = "no-cache";
    Connection = "Keep-Alive";
    "Content-Length" = 14;
    "Content-Type" = "application/x-fcs;charset=ISO-8859-1";
    Date = "Mon, 29 May 2017 16:45:35 GMT";
} })
2017-05-29 19:45:35.886 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPTSocket.swift:259] doRequest > Optional(http://<IP_ADDRESS>:5080/send/NC90BHFCGRG3H/1)
2017-05-29 19:45:35.887 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPTSocket.swift:209] didIdle0(data:response:error:) > Optional([1]):Optional(<NSHTTPURLResponse: 0x17403cf00> { URL: http://<IP_ADDRESS>:5080/idle/NC90BHFCGRG3H/0 } { status code: 200, headers {
    "Cache-Control" = "no-cache";
    Connection = "Keep-Alive";
    "Content-Length" = 1;
    "Content-Type" = "application/x-fcs;charset=ISO-8859-1";
    Date = "Mon, 29 May 2017 16:45:35 GMT";
} })
2017-05-29 19:45:35.902 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPTSocket.swift:123] listen(data:response:error:) > Optional(3074 bytes):Optional(<NSHTTPURLResponse: 0x170038420> { URL: http://<IP_ADDRESS>:5080/send/NC90BHFCGRG3H/1 } { status code: 200, headers {
    "Cache-Control" = "no-cache";
    Connection = "Keep-Alive";
    "Content-Length" = 3074;
    "Content-Type" = "application/x-fcs";
    Date = "Mon, 29 May 2017 16:45:35 GMT";
} }):nil
2017-05-29 19:45:35.913 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPTSocket.swift:259] doRequest > Optional(http://<IP_ADDRESS>:5080/send/NC90BHFCGRG3H/2)
2017-05-29 19:45:35.930 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPTSocket.swift:123] listen(data:response:error:) > Optional(257 bytes):Optional(<NSHTTPURLResponse: 0x170035bc0> { URL: http://<IP_ADDRESS>:5080/send/NC90BHFCGRG3H/2 } { status code: 200, headers {
    "Cache-Control" = "no-cache";
    Connection = "Keep-Alive";
    "Content-Length" = 257;
    "Content-Type" = "application/x-fcs";
    Date = "Mon, 29 May 2017 16:45:35 GMT";
} }):nil
2017-05-29 19:45:35.934 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPConnection.swift:484] listen > RTMPChunk{size:128,type:zero,streamId:2,message:Optional(RTMPUserControlMessage{type:user,length:6,streamId:0,timestamp:0,payload:6 bytes,event:streamBegin,value:0}),fragmented:false,_data:12 bytes}
2017-05-29 19:45:35.941 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPConnection.swift:484] listen > RTMPChunk{size:128,type:zero,streamId:3,message:Optional(RTMPCommandMessage{type:amf0Command,length:225,streamId:0,timestamp:0,payload:225 bytes,objectEncoding:0,commandName:_result,transactionId:1,commandObject:Optional([:]),arguments:[Optional(["data": Optional([]), "code": Optional("NetConnection.Connect.Success"), "description": Optional("Connection succeeded."), "mode": Optional(1.0), "level": Optional("status"), "capabilities": Optional(33.0), "fmsVer": Optional("RED5/1,0,9,0")])],serializer:AMF0Serializer{bytes:[],position:0,reference:lf.AMFReference}}),fragmented:false,_data:12 bytes}
2017-05-29 19:45:35.942 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPTSocket.swift:259] doRequest > Optional(http://<IP_ADDRESS>:5080/send/NC90BHFCGRG3H/3)
2017-05-29 19:45:35.966 [Verbose] [com.cerebralgardens.xcglogger.defaultInstance] [main] [RTMPTSocket.swift:123] listen(data:response:error:) > Optional(155 bytes):Optional(<NSHTTPURLResponse: 0x17403cee0> { URL: http://<IP_ADDRESS>:5080/send/NC90BHFCGRG3H/3 } { status code: 200, headers {
    "Cache-Control" = "no-cache";
    Connection = "Keep-Alive";
    "Content-Length" = 155;
    "Content-Type" = "application/x-fcs";
    Date = "Mon, 29 May 2017 16:45:35 GMT";
} }):nil

Looks like it falls into infinite loop with position being 0 in listen(data.advanced(by: position))
Any ideas on how to fix this?

+1

for whatever reason only one video frame gets pushed to red5
@shogo4405 @geeee

this PR
https://github.com/shogo4405/lf.swift/pull/237
helps red5 survive for 15 minutes, still gets some weird packets from lf.swift

@shogo4405 RTMPTSocket locking/synchronization is not very obvious which i believe leads to weird packets being sent to red5 on which it chokes


Translations update from Weblate

Translations update from Weblate for mattermost-languages-shipped/mattermost-webapp.
Current translation status:

/release-note-none


Add "with detailed calculation" to title

to differentiate from other page with same title but lack of detailed
calculation.
This addresses the overview of articles as can be seen from
https://oscovida.github.io/category-all.html

Codecov Report

Merging #115 into master will decrease coverage by 0.35%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #115      +/-   ##
==========================================
- Coverage   69.21%   68.86%   -0.36%
==========================================
  Files           4        4
  Lines         799      790       -9
==========================================
- Hits          553      544       -9
  Misses        246      246

Impacted Files
Coverage Δ

oscovida/oscovida.py
65.77% <0.00%> (-0.43%)
: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 e8a400c...d615c49. Read the comment docs.

Offline LGTM


Getting the activations from the last-position token

Hi there,
Thanks for your great work. I have a question regarding how you extract the last token - I see from the code that you extract the last 4 tokens and do a average pooling to get the activations rather than the last single token,
task_latents = forward_trace.residual_stream.hidden[:, :, -4:, :].mean(2,keepdim=False) #[:, :, -1, :] # get last token
https://github.com/shengliu66/ICV/blob/8cdce613cc5d2c44a1afecb8f8db81c4cb41c7c5/tasks/base.py#L279C46-L279C136?plain=1
Is there any mismatch with the description of the paper? And how to choose the hyperparameter that how many tokens to be used?

你的邮件我受到非常感谢配合

Hi,
Thank you and sorry for the late response, we tried both the last token and the average of the last few tokens, and it worked similarly.


Write status error

Is your feature request related to a problem? Please describe.
Is it possible to write response with HTTP status code and body as json(by default is html)
Describe the solution you'd like
res.set_status_code(StatusCode::NOT_FOUND)
     .render(Json(e))

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
I'm new to salvo, using doc: https://salvo.rs/book/core/response/#write-status-error

Error format is depend on your request's accept content type.
When your request's accept content type is json, the returns page is json.
Default error pages supports page format: xml, plaintext, json, html.

@chrislearn thx, that is great


Release 0.5.0

@andy-armstrong @AlasdairSwan @bjacobel

:+1:
FYI, we agreed that release PRs only need one reviewer, so you can go ahead and merge.

Sounds good!


Restart pycsw web process

What
Restart the pycsw web process rather than having to manually restart it.
After this deployment docs will need to be updated - https://docs.publishing.service.gov.uk/manual/data-gov-uk-deployment.html#csw, as will be automatic.

It would be good to add here a link to the PR that updates the docs

There isn't a PR yet, also no harm in restarting the workers, will create the PR now for review


Timeline fix

Fixes Timeline::set_tracks(nullptr) leads to bad state #851
Summarize your change.
Sets _tracks to a new Stack() if the incoming pointer is null
Reference associated tests.
Added a new test in test_tracks_set_null_tracks in tests/test_timeline.py

Addresses https://github.com/PixarAnimationStudios/OpenTimelineIO/issues/851

@davidbaraff Replaced this PR with https://github.com/PixarAnimationStudios/OpenTimelineIO/pull/961/files which rebases the change on top of the latest commits.


Access to external storage

Allow internal file browser to scan external storage (like SD cards) and list the files

Is there any kind of workaround other than copying to internal? Symlink maybe?

Added in v2023.1.2


[Browser Bookmarks] Extension fav icons don't match browser fav icons

Extension
https://www.raycast.com/raycast/browser-bookmarks
Description
The old (private) extension handled this nicely, I assume by reading from the browser's favicon DB instead of raycast's getFavIcon.
There are two main places where I've found getFavIcon to be worse than the (assumed) old approach.

Urls behind authentication
Url redirects

Steps To Reproduce
Use-case 1:

Bookmark a url behind authentication (my repro case: https://.atlassian.net)
Search for the bookmark in the bookmark browser extension, the displayed icon is the fallback.

Use-case 2:

Bookmark a url with a redirect (my repro case: https://mail.google.com)
Search for the bookmark in the bookmark browser extension, the displayed icon is the fallback.

Current Behaviour
Icon displayed by bookmark browser extension is the fallback icon.
Expected Behaviour
Icon displayed by bookmark browser extension matches the fav icon in my browser.

In my limited test, using https://icon.horse/ was significantly better than https://www.google.com/s2/favicons. However it has the downside of not being free 😆

Thanks for flagging this issue. Would you like to work on it? I can provide some guidance on how to contribute to this extension so that you can open a pull request. You can contact me here or in the Slack community if you need further help.

@thomaslombart is this worth re-opening?


v2.0.1 doesn't work with UglifyJs

The error is:
ERROR in bundle.js from UglifyJs
SyntaxError: Name expected [bundle.js:113484,4]

Downgrading to v1.3.20 seems to work again
No idea what is causing this yet

It doesn't seem to like this line: https://github.com/marcuswestin/store.js/blob/eccd5cdcdce45a1e054de25eab2d2cdd2ed1e507/src/store-engine.js#L1

It is not related to Webpack, I run into the same error in Browserify + uglifyify.
Error: Uncaught, unspecified "error" event. (SyntaxError: Name expected while parsing file: ..node_modules/store/src/store-engine.js (line: 1, col: 4, pos: 4)

Error
    at new JS_Parse_Error (eval at <anonymous> (..node_modules/uglify-js/tools/node.js:28:1), <anonymous>:1547:18)
    at js_error (eval at <anonymous> (..node_modules/uglify-js/tools/node.js:28:1), <anonymous>:1555:11)
    at croak (eval at <anonymous> (..node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2094:9)
    at as_symbol (eval at <anonymous> (..node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2745:27)
    at vardefs (eval at <anonymous> (..node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2513:25)
    at var_ (eval at <anonymous> (..node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2527:27)
    at eval (eval at <anonymous> (..node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2270:30)
    at eval (eval at <anonymous> (..node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2141:24)
    at eval (eval at <anonymous> (..node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2909:23)
    at Object.parse (eval at <anonymous> (..node_modules/uglify-js/tools/node.js:28:1), <anonymous>:2920:7))
    at Readable.emit (events.js:144:17)
    at Labeled.<anonymous> (..node_modules/read-only-stream/index.js:28:44)
    at emitOne (events.js:77:13)
    at Labeled.emit (events.js:169:7)
    at Labeled.<anonymous> (..node_modules/stream-splicer/index.js:130:18)
    at emitOne (events.js:82:20)
    at Labeled.emit (events.js:169:7)
    at Deps.<anonymous> (..node_modules/stream-splicer/index.js:130:18)
    at emitOne (events.js:77:13)
    at Deps.emit (events.js:169:7)

#180 fixes it for me

@hyperknot good to know 👍

@joeduncan I'm actually using
"store": "marcuswestin/store.js#a08441",

In production now :-)

@hyperknot try 12153c87a7922e00e09c2eb7423a7b2720b86e11 - i missed the plugins ;)

@joeduncan thanks.

Right, of course - I was originally building just for compiled builds and figures ES5/6 features would be kosher. I totally see why that's not the case. I'll review, pull, test and release shortly!


Timeline message graph

Is your proposal related to a problem?
Some kafka topics have very different producer activity over time, and troubleshooting or investigating message traffic is often useful.
Describe the solution you'd like
In the messages view, above the message list I would like a timeline with a bar diagram indicating produced message volume over time. Selecting portions on the graph would adjust which offset the messages list starts from

Describe alternatives you've considered
Linking to a grafana dashboard, preferably directly from the UI
Additional context

Hey, thanks for the suggestion. We're planning on implementing this within #942.


Fix e2e test testTraceflowValidation for IPv6-only cluster

The test case was making the assumption that every Pod always has an IPv4 address, which is not the case for IPv6-only clusters.
To simplify the test case, we use the Pod's namepspace/name to define the Traceflow destination, instead of the Pod's IP address.

/test-e2e
/test-ipv6-only-e2e
/test-ipv6-e2e

I cannot assign @shi0rik0, so tagging here

Relevant tests are passing. I am merging this to fix CI.


Improving Connecting Page fresh user experience

[ ] Use the default user/password when clicking connect unfilled
[ ] Rename the Host field to GraphD Host: Port or other things that make sense of this w/o reading docs, or provide hints

A couple of fresh users had been blocked in this phase as I know :).

i will add placeholder in the host input box. As for more hints, I plan to add it in a better way in the next version of the UI revision