Failed to run on Android Chrome

Execution fails with the following error at the start up (during the warm-up) and when clicking "Guess" button.
A TF.js demo, Emoji Scavenger Hunt, that uses similar features, runs fine on Android Chrome, So, there should be a way to fix it.
Android version tested is 6.0 and TF.js is of version_core: "0.9.1".  I don't have newer Android device, but I'm informed that Android 8.0 device failed to run this demo in the same manner.
Uncaught Error: Failed to compile fragment shader.
    at Object.createFragmentShader (webpack:///./node_modules/@tensorflow/tfjs-core/dist/kernels/webgl/webgl_util.js?:91)
    at GPGPUContext.createProgram (webpack:///./node_modules/@tensorflow/tfjs-core/dist/kernels/webgl/gpgpu_context.js?:166)
    at Object.compileProgram (webpack:///./node_modules/@tensorflow/tfjs-core/dist/kernels/webgl/gpgpu_math.js?:25)
    at eval (webpack:///./node_modules/@tensorflow/tfjs-core/dist/kernels/backend_webgl.js?:775)
    at MathBackendWebGL.getAndSaveBinary (webpack:///./node_modules/@tensorflow/tfjs-core/dist/kernels/backend_webgl.js?:791)
    at MathBackendWebGL.compileAndRun (webpack:///./node_modules/@tensorflow/tfjs-core/dist/kernels/backend_webgl.js?:774)
    at MathBackendWebGL.conv2d (webpack:///./node_modules/@tensorflow/tfjs-core/dist/kernels/backend_webgl.js?:690)
    at environment_1.ENV.engine.runKernel.x (webpack:///./node_modules/@tensorflow/tfjs-core/dist/ops/conv.js?:83)
    at Engine.runKernel (webpack:///./node_modules/@tensorflow/tfjs-core/dist/engine.js?:72)
    at ConvOps.conv2d (webpack:///./node_modules/@tensorflow/tfjs-core/dist/ops/conv.js?:83)

Perhaps GPU runs out memory. This happens on older Android smartphone like Galaxy S5, but works on newer Galaxy S7 and Pixel 2 XL.
Adding tf.setBackend('cpu') as 1st line in window.onload in index.js fixes the crash on Galaxy S5, however recognition gets slow, around 10sec.


LMDB Reading Feature

I would like to see a native feature where LMDB files are read by tensorflow inside the graph. I know it can be done with placeholders but that's suboptimal.
In general, there are three ways of approaching this in TF.
(1) Native Implementation / Custom Data Reader
https://www.tensorflow.org/versions/r0.10/how_tos/new_data_formats/index.html
(2) Python Function Wrapping
https://www.tensorflow.org/versions/r0.9/api_docs/python/script_ops.html
(3) Placeholders
The functionality is neat but I require better performance..
If I were to do this myself, what are from a performance standpoint be the main differences between (1) and (2). In any case, it would be great if (1) ended up in the master branch.

thanks for posting. I think that it would be best to post your questions about relative performance differences between options (1) and (2) to stackoverflow first (tag 'tensorflow').

Thanks Andy.
But the feature request is 'LMDB reading feature', so the question can be considered an extra. Can you open this feature request up again, or are you excluding this from ever being implemented? That would make me sad.

My thinking was that you could first ask the question portion of this issue on StackOverflow (sometimes people may have a solution for you). If nothing useful turns up there, then feel free to enter another feature request (or we can reopen this one).

An open PR implementing the requested feature.
https://github.com/tensorflow/tensorflow/pull/9950


How are semantic segmentation colors picked?

I have been looking at the source to understand how semantic segmentation works. I've been able to figure out most of the process so far:

Each static mesh for each actor is tagged based on its path.
When a mesh is tagged, its custom depth stencil value is set to one of the ECityObjectLabel values and it's allowed to render in the custom depth buffer.
The semantic segmentation camera is set up to use a post processing blendable material GTMaterial defined in the Carla plugin.
The material uses the custom stencil value to determine the emissive color of the material.

Here's what I don't understand: GTMaterial normalizes the custom stencil value, multiplies it with a constant red color and uses that as the emissive color, yet the final result has a variety of hues (reds, greens, purples, blues, etc.)
What am I missing? How are these final colors determined?

Hi @xevo-vstojkovic,
Check out the Cameras and sensors documentation :)
The server provides an image with the tag information encoded in the red channel.
This coloring process is done in the client side with labels_to_cityscapes_palette function.

One problem of using stencil buffer for segmentation is that it limits the number of tags to be no more than 256. If you want to have more tags for segmentation, you can't use stencil buffer for this purpose. Any suggestion for this?

Hi @hrdisaac,
That's one of our main problems right now. Sorry for that.
This is a big limitation and does not allow us to generate instance semantic segmentation and has a performance impact too.
We are waiting to Unreal (or someone) to give us an elegant solution.
Maybe modifying the engine itself, you can do something like generate a custom buffer with this information. We are trying to avoid any engine modification because it may generate problems with some future Unreal updates or with onthers parts of the engine.
Regards.

In order to support more than 256 tags without modifying the engine itself, is it possible to dynamically create a transparent material per static mesh and set a custom parameter on that material and somehow access that custom parameter in the post process pass? Or any way to make use of postprocessinput3 to postprocessinput6 (marked as not usually used by Unreal) to inject the tags? Or create two render targets to render the same material for twice, so in the shader it can use one custom stencil value as the lower bits and the other as the higher bits, then combine them in the shader to render the final color for segmentation?

Hey @hrdisaac,
I've answered your question in the other issue #76 :)

This thread helped me.


Project migrated to Swift 3.

Project migrated to #1 Swift 3 using XCode 8.

https://github.com/coffellas-cto/KSNavigationController/pull/2 was first. thanks for your contribution.


Subtract reward points when killing a friendly unit

When killing a friendly unit, subtracts its reward points.
To implement this, the new method losePoints has been added to the Unit class, which will substract the given points from the unit ~(but doesn't decrement its score under zero)~.
Closes #62

Codecov Report

Merging #87 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #87      +/-   ##
==========================================
+ Coverage    90.4%   90.46%   +0.05%
==========================================
  Files          80       80
  Lines        1011     1017       +6
  Branches      154      156       +2
==========================================
+ Hits          914      920       +6
  Misses         82       82
  Partials       15       15

Impacted Files
Coverage Δ

packages/warriorjs-core/src/Unit.js
100% <100%> (ø)
:arrow_up:

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 594712f...82a7f65. Read the comment docs.

@olistic I've pushed a new version rebased with master.

Thanks @Terseus!


scp -J and sftp -J not working

Hi
I tried to use scp and sftp
but i couldn't
unknown command -J

Can you please give me an example of how you are using it?
This should work by default.


move functionality from Javis to JavisViewer

This PR is meant to move all the interactive and liveviewing parts of Javis to JavisViewer
Closes:
#1

Hi @TheCedarPrince I started working on this, it would be nice if you could merge this PR so we have CI working or give me merge access and I can do it myself.
It is not finished yet but just so we can set up some initial stuff it should be good to go, test locally and it works.

I did not know this but since it is not running here CI runs on my fork! So no rush at all!!

Hey @gpucce , you should now have access to all the things!
Sorry about that!
I thought the @JuliaAnimators/maintainers team has at least maintainer rights by default.
Before we merge this, something I noticed was that accidentally included in this PR was the live streaming functionality.
This is quite different from the JavisViewer and needs to not be merged here...
Not sure where to put the streaming functionality just yet but we should at least keep it back inside of Javis.jl itself.

I can give more of a review later - right now, quite tired!

I was going to ask you if you wanted to move the streaming as well, that I will move back then!!

I think streaming is pretty much basic so better to keep it in base Javis.

Hi @TheCedarPrince this should be the JavisViewer package! If you can review it and let me know if smth is missing i will add it!


Load and decode images on demand

gltf-pipeline currently loads all of a gltf's images using Jimp up-front in https://github.com/AnalyticalGraphicsInc/gltf-pipeline/blob/master/lib/loadGltfUris.js. For texture-heavy models this is a pretty major performance problem, since decoding is slow and also eats an enormous amount of memory. A lot of optimizations in the pipeline also don't do anything with those textures, so we could potentially speed up optimization for a lot of models just by loading images as needed.

No longer a problem in master, which doesn't even include Jimp anymore.


Allow navigation in page chooser modal search

Fixes #5796

After digging a bit deeper, it seems not as simple as I first thought! The modal ajax search returns a HTML response via "wagtailadmin/chooser/_search_results.html" and the explorer ajax returns a JSON response via "wagtailadmin/chooser/browse.html"
I'm not sure why the difference 🤷♂

Closing in favour of #9246. We have been working on new chooser designs for a while, I don’t see ourselves making further gradual improvements to their existing implementation.


VarFieldChecker false positive on var local

VarFieldChecker reported this var local pendingIterator as a var field. We'd like to prohibit var fields but allow var locals, as is suggested by the two checker names.
  def arrayOfResults(in: BufferedIterator[JsonEvent], alreadyInArray: Boolean = false): Iterator[ReportItem] = {
    if(!alreadyInArray) expectStartOfArray(in)
    new Iterator[ReportItem] {
      var pendingIterator: Iterator[JValue] = null
      def invalidatePending() {
        if((pendingIterator ne null) && pendingIterator.hasNext) {
          throw new Exception("Row result was not completely consumed")
        }
        pendingIterator = null
      }
      def hasNext = { invalidatePending(); in.hasNext && !in.head.isInstanceOf[EndOfArrayEvent] }
      def next(): ReportItem = {
        if(!hasNext) Iterator.empty.next()
        if(in.head.isInstanceOf[StartOfArrayEvent]) {
          pendingIterator = JsonArrayIterator[JValue](in)
          UpsertReportItem(pendingIterator)
        } else {
          skipNextDatum(in)
          OtherReportItem
        }
      }
    }
  }

In the above, pendingIterator is a field, it isn't a var local.


Can't put assert inside case statement

Steps to reproduce the issue
test.v
module test(input wire A);
  localparam TEST = 1;
  always_comb begin
    case (A)
      TEST: assert(1);
    endcase
  end
endmodule

Repro command:
yosys -p 'read -sv test.v'
Expected behavior
Output:
Parsing SystemVerilog input from `test.v' to AST representation.
Generating RTLIL representation for module `\test'.
Successfully finished Verilog frontend.

Actual behavior
Fails to parse.
Output:
Parsing SystemVerilog input from `test.v' to AST representation.
test.v:5: ERROR: syntax error, unexpected TOK_ASSERT

Reverting e7a34d3  #699  seems to fix this.

Oops! #864 should fix it. Can someone double-check I didn't break anything else this time around?  ;)


Remove TxBody cli intermediate format

What
Remove support for the TxBody intermediate format
Why
It is no longer possible to create TxBodys in the cli intermediate format since #4303. We should fully drop support as it is unlikely that users have unsigned transactions serialized in the intermediate tx body format lying around. Fully dropping support allows us to clean up the code in cardano-cli.
Personas

[ ] SPOs
[ ] dApp Devs
[ ] Exchanges
[ ] Wallets
[ ] 3rd party tools
[ ] ADA holders

Definition of Done (DoD)

[ ] Acceptance Criteria + User Stories & DoD created and singed-off (by PO, dev & test owners)
[ ] Builds successfully on CI
[ ] Code & Test review (as per Acceptance Criteria)
[ ] There is documentation and/or examples for the new functionality (usage/response)
[ ] Log/record changes on Vnext (or similar depending on what we adopt)
[ ] Ticket number(s) included in PR description
[ ] All Acceptance Criteria met and covered by dev/unit/property/integration tests
[ ] System/E2E automated tests + System Test Engineer Owner Sign-off

NOTE:  Ideally, we should merge only fully implemented and tested features into the master branch.
So all the above steps are required for the PR to be merged.
In order to avoid the PRs becoming stale and requiring to be rebased on master, these can be merged
after a reasonable time (current agreement is 3 days) if the System Test Engineer Owner's sign-off
was not provided (last step in the DoD).

IMPORTANT: Any deviation from the plan should be discussed and agreed as a comment in the Feature file.

Sign-off

[ ] Product Owner
[ ] Dev Owner
[ ] System Test Engineer Owner

Related PRs

PR #4303

Acceptance Criteria
Acceptance Criteria & User Stories define here (or in a separate file (linked here) for a big feature)

Resolved by: https://github.com/IntersectMBO/cardano-api/pull/407/commits/e739675890157bf60956e1c04dcb3e94c0e6e8df


Integrate Escalation

Integrate escalation creation directly from the cell output. Additionally, add a link to view the escalation in the Platform after it is created.
Depends on: https://github.com/stateful/platform/pull/925

Let's get @pastuxso's review on this first, please. I can do a final review and end-to-end test.

@peraltafederico Works fine.

@pastuxso https://github.com/stateful/platform/pull/925 implemented in production, do you want to make a new test before merge it?

@pastuxso stateful/platform#925 implemented in production, do you want to make a new test before merge it?

Yes, let's not merge, please, until I complete a final test. Likely tmrw.


fix diagnostic ticks

I think this should fix the diagnostics ticks so they're queryable? Figured should do this before we forget~

Thanks @jwunderl

Thanks @jwunderl


Fix/fwa upload temp dir

Ticket Number

UCD-984
Description of change

Update the express-fileupload config

update tmpDir
update limits.fileSize
set Helm/k8s to debug uploads by default (future piece to investigate changing internal console.log to using pino)

Checklist

[ ] Requires infrastructure changes
[ ] I have updated the documentation accordingly
[ ] I have merged commits to avoid fixing things in this PR
[ ] New features have tests
[ ] Breaking change (team conversation required)

Important
Please do not merge from master (please only rebase). This keeps the history linear and easier to debug.

Have checked this and it uploads files fine. Obviously, we need to work out what to do with them next, but that's beyond the scope of this ticket


Support for site owner avatar img?

Not sure if I'm missing something, but it looks like this jekyll theme doesn't include code to support an site owner avatar image. Also the example yml file references an avatar image that doesn't exist in the /img/ folder. Otherwise really cool theme design so far!

Hi @asdfhamiltonian, thank you for this first issue.
That is a good suggestion and I was thinking about it when I started the project.
As you can see, this theme is inspired by purecss blog layout and you can find the original version here.
The original one shows author's avatar for every post and it looks pretty good if the blog has several authors, but it will be weird if the blog is single author.
So I do like to add author's avatar at the sidebar, just above the author's name and hide it when screen gets smaller.
How do you think? I'll work on it this weekend and let you know if finished.
Have a nice day,
Renyuan

Hey Renyuan, that sounds good! It could definitely be weird to have an author photo with every post for a multi-author blog. My solution was just to paste a photo into the sidebar section and it seems to work ok for now.
Let me know how it goes, I look forward to seeing what you come up with. Thank you for coming up with this cool Jekyll layout.
Sincerely,
Max

On Sep 7, 2015, at 3:11 AM, Renyuan<EMAIL_ADDRESS>wrote:
Hi @asdfhamiltonian https://github.com/asdfhamiltonian, thank you for this first issue.
That is a good suggestion and I was thinking about it when I started the project.
As you can see, this theme is inspired by purecss blog layout and you can find the original version here http://purecss.io/layouts/blog/.
The original one shows author's avatar for every post and it looks pretty good if the blog has several authors, but it will be weird if the blog is single author.
So I do like to add author's avatar at the sidebar, just above the author's name and hide it when screen gets smaller.
How do you think? I'll work on it this weekend and let you know if finished.
Have a nice day,
Renyuan
—
Reply to this email directly or view it on GitHub https://github.com/renyuanz/leonids/issues/1#issuecomment-138259255.

Hi @asdfhamiltonian,
I did make this change yesterday and it looks like this:

I couldn't come up with a better design at the moment, but if you have any idea just share it here, I'll really appreciate it. :-)
I'll just push it so everyone could see the live demo.
Cheers,
Renyuan

Hi @renyuan,
The update looks cool! I’ll try updating my page to the new design and let you know if I think of anything.
Regards,
Max

On Sep 11, 2015, at 12:40 AM, Renyuan<EMAIL_ADDRESS>wrote:
Hi @asdfhamiltonian https://github.com/asdfhamiltonian,
I did make this change yesterday and it looks like this:
https://cloud.githubusercontent.com/assets/10615036/9809401/2ba99c28-5868-11e5-8f27-a06cae4b03ba.png
I couldn't come up with a better design at the moment, but if you have any idea just share it here, I'll really appreciate it. :-)
I'll just push it so everyone could see the live demo.
Cheers,
Renyuan
—
Reply to this email directly or view it on GitHub https://github.com/renyuanz/leonids/issues/1#issuecomment-139475026.

Hey Renyuan,
I thought I should update you on some feedback I got about the Jekyll
theme. My career advisor for this code school I use said that their
designer didn't like the idea of having the author's photo on the
sidebar (turns out that maybe my idea for this was bad). What I did
instead is add a photo to my about page. They also thought that the
icons for github, linkedin etc. were a bit too small. Hope this
information helps and let me know what you think!
Best,
Max
On 9/11/2015 6:39 PM, Maxwell Hirsh wrote:

Hi @renyuan,
The update looks cool! I’ll try updating my page to the new design and
let you know if I think of anything.
Regards,
Max

On Sep 11, 2015, at 12:40 AM, Renyuan<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Hi @asdfhamiltonian https://github.com/asdfhamiltonian,
I did make this change yesterday and it looks like this:
screen shot 2015-09-11 at 09 32 34
https://cloud.githubusercontent.com/assets/10615036/9809401/2ba99c28-5868-11e5-8f27-a06cae4b03ba.png
I couldn't come up with a better design at the moment, but if you
have any idea just share it here, I'll really appreciate it. :-)
I'll just push it so everyone could see the live demo.
Cheers,
Renyuan
—
Reply to this email directly or view it on GitHub
https://github.com/renyuanz/leonids/issues/1#issuecomment-139475026.

Hey Max @asdfhamiltonian ,
I've the same idea with you. But I got a little busy this month, I'll rework on the avatar design or maybe index page design next month.
Thanks for your advise.
Best,
Renyuan

I'm working on a brand new design of the theme. This issue is closed by now.


[Task]: Add active parameter in Tenant GET and Tenant PUT APIs

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
active parameter to be added in the following APIs

PUT /v1/admin/env
GET /v1/tenants/current

This parameter represents the active color of the button.

PR for this has been raised here: https://github.com/appsmithorg/appsmith-ee/pull/2182


RF: cat

This adds tests for cat and also refactors the command to:

improve readability
fix error handling
use python to print file content to stdout rather than calling cat via a sub process

Fixes #192, #193

Codecov Report
Base: 64.76% // Head: 66.31% // Increases project coverage by +1.54% :tada:

Coverage data is based on head (0cc6e4e) compared to base (3d7e8b3).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #194      +/-   ##
==========================================
+ Coverage   64.76%   66.31%   +1.54%
==========================================
  Files          20       20
  Lines        1212     1223      +11
  Branches      246      247       +1
==========================================
+ Hits          785      811      +26
+ Misses        347      337      -10
+ Partials       80       75       -5

Impacted Files
Coverage Δ

onyo/commands/cat.py
100.00% <100.00%> (+30.76%)
:arrow_up:

onyo/__init__.py
56.25% <0.00%> (-37.50%)
:arrow_down:

onyo/commands/fsck.py
69.10% <0.00%> (+10.56%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

The failure is due to https://github.com/readthedocs/sphinx_rtd_theme/issues/1343
There's no sense in pinning a version to avoid this. Upstream will fix this soon enough, as it's affecting everyone.
The docs build correctly locally. Merging.

Thanks!


LLVM warning in test_spdm_requester/get_certificate.c

When test_spdm_requester/get_certificate.c is compiled with LLVM it produces lots of warnings like
get_certificate.c:1196:13: warning: variable 'hash_size' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]

I will check it.


Logging in from the terminal doesn't work

Keybase GUI Version: 1.0.14-20160316190012+580f36e
12:04 PM ~: keybase version
keybase (keybase.io CLI) v0.8.25
- node.js v0.10.35
- gpg (GnuPG) 1.4.18
- Copyright (C) 2014 Free Software Foundation, Inc.
Identifies as: 'keybase.io node.js client v0.8.25 darwin'

When I log in inside the terminal, the terminal seems to know who I am, but not the rest of the keybase program.
After I have successfully logged in:

When I try dragging a .jpg file into my keybase public directory, I get a prompt for my OSX password, but it doesn't seem to wait for that before erroring:

keybase seems to be pointing at an old Node client instead of the Go client that we switched to.
It looks like you're trying to write to /keybase/public/morpheus.jpg instead of /keybase/public/your_username/morpheus.jpg.

So is this something I can fix on my own, and if so, how should I fix it? Or is it a problem with the client?

Hey @cilphex! Try uninstalling the node client with the instructions at the bottom of: https://keybase.io/download

You can uninstall the node brew client via brew uninstall keybase
Also can you do a keybase log send and post the id so I can see what went wrong?

(If you installed with npm, then you would need to uninstall it that way as @aalness suggested)

@aalness Missed that step - it worked. Thanks!

Sweet! I also stuck some sick art in /keybase/private/alness,craig :)


Unique callback not returning error to the client

Hi,
First up: thanks for building some awesome meteor packages!
Now to the point... I have a field which should be unique in a collection. The problem is, when the unique error is returned by MongoDB and I can properly handle the response to the client, the client is already continuing its business without ever receiving the error.
I've looked into this issue: http://stackoverflow.com/questions/21435978/collection2-insert-using-method-exception-from-unique-constraint-not-caught and https://github.com/aldeed/meteor-collection2/issues/59 (both pretty old already) - I could get the workaround to work, but I was wondering if this is still the right way to do it.
I'm using: meteor 1.0.5, separate instance of mongodb 2.6.8, collection2 2.3.3
I have the following in one of my schemas:
Customer = new SimpleSchema({
        'code': {
            type: String,
            min: 1,
            max: 20,
            optional : false,
            unique : true,
            label : 'Customer Code',
            regEx : App.RegEx.CustomerCode
        }
});

Customers = new Mongo.Collection('customers');
Customers.attachSchema(Customer);

Validation works fine on the client side. Pretty cool stuff. On the client side, I have the following code:
var customer = {
    code : '123456'
};

Meteor.call('addCustomer', customer, function (error, result) {
    if (error) {
        alert('Error');
    } else {
        alert('Nice!');
    }
});

...and the following method on server side:
Meteor.methods({

    addCustomer: function(customer) {
        Customers.insert(customer, function (error, result) {
            if (error) throw new Meteor.Error('insert-error',error);
        });
    }
});

Inserting works fine. Great! Now, I want to insert a customer with the same code to test the unique constraint on the field.
What happens is that the client in this case never receives the error and displays the 'Nice!' alert.
On server side, the callback is properly ran, but the throw never "reaches" the client.
Any idea what might be happening?

In your method, do Customers.insert(customer) (no callback). Methods have to execute synchronously to work properly, and any errors thrown will be in the error argument back on the client. Collection2 attaches a sanitized error with extra information, so that you'll be able to see the validation errors back on the client by examining the error object.

I did as you described and I'm getting a bland code 500 error on the client despite the fact that I'm getting an "E11000 duplicate key error index" exception in the server console.
// see it's synchronous
Contacts.insert({
    userIds: [Meteor.userId()],
    name: name,
    phone: phone,
    email: email,
    createdAt: date
});

// and on the client
Meteor.call('newContact', name, phone, email, (err) => {
    if (err){
        console.log(err);
        alert(err.reason);
    } else {
        $scope.popup.close();
    }
});

And for what its worth thanks for writing and maintaining this awesome package

I have the same issue.


HTTP API debug/pprof/profile behavior is inconsistent with go pprof

Question

The TiKV debug/pprof/profile HTTP API default output format is svg, not protobuf, this behavior is inconsistent with go pprof.
Here is an example:
TiDB
▶ curl http://{TIDB_HOST}:{PORT}/debug/pprof/profile\?seconds\=2 > profile

▶ go tool pprof profile
File: tidb-server
Build ID: 791f27d543701fe824457dcbb60c0b944cf7fdf5
Type: cpu
Time: Sep 1, 2021 at 3:05pm (CST)
Duration: 2s, Total samples = 190ms ( 9.50%)

TiKV
▶ curl http://{TIKV_HOST}:{PORT}/debug/pprof/profile\?seconds\=2 > profiletikv

▶ go tool pprof profiletikv
profiletikv: parsing profile: unrecognized profile format  # Because the format of profiletikv is svg, not protobuf.
failed to fetch any source profiles

# To fix this, I had to specified the format in HTTP Request Header:
▶ curl -H "Content-Type:application/protobuf" http://{TIKV_HOST}:{PORT}/debug/pprof/profile\?seconds\=2 > profiletikv

I think we should fix it. Then it can be compatible with the pprof ecosystem.

I think it's due to https://github.com/tikv/tikv/blob/master/src/server/status_server/mod.rs#L382-L411
Maybe we should test for svg format header, and returns protobuf by default?

I think TiFlash behaviour also need to be updated accordingly. @solotzg What do you think?

I think flame graph is much more useful for tiflash.

I think flame graph is much more useful for tiflash.

We can add query parameters like "type=flamegraph" for a shortcut.

Is this issue still alive?


[Bug] calling for wrong dependency

On curse forge, FirstPersonMod-2.0.2.jar(1.17+) calls for....

TRansliterationLib-1.0.4.jar (1.16)
NotEnoughAnimations-1.0.3.jar (1.16)

Update, i just noticed that FPM calls for NEA, and they might be responsible

Huh it downloaded the 1.16 dependencies for the 1.17 version?

yes, that is currently what it is doing, i tested it on a brand new pack,

Which launcher did you use? On Curse no versions are directly linked as dependency, but just projects. So the launcher has to pick the correct jar for Forge/Fabric and the MC version.

I am using the curse launcher.
fabric-api-0.38.1+1.17.jar
FirstPersonMod-2.0.2.jar
NotEnoughAnimations-1.0.3.jar
Sorry for the lack of information at first... i assumed it was just a wrong dependency lable. Let me know if you need anything else from me,

Huh that's realllly odd. Why would it pull the 1.0.4 of TRansliterationLib when there's a full release for 1.17.
I kinda suspected that the launcher downloaded the 1.16 version of Firstperson because the 1.17 is marked as a Beta, and that it loads the 1.16 dependencies because of that.
I'll keep it in mind, I'm planing to release a new version in the next few days of Firstperson and Transliteration, maybe that will fix it.

This is now resolved. Curse supports selecting multiple modloaders now, perfectly when I'm more or less done making everything 2 jars instead 👀.


add hover feedback for run/reset example buttons

I think we used to have hover feedback for run/reset example buttons but it seems to have disappared. Maybe the button should come to full opacity (background and text) on hover?

#78 Done
Hii @Imccart I created some hover feedback for the run/reset example buttons. On hover, the button will be slightly zoomed(i.e; by scale 1.1), text color changes, full opacity background with some box-shadow effect. Let me know if you want something more.
See PR for #78.

thanks @lasyapriyanka! I think this amount of feedback (4 style properties changing) is inconsistent with the rest of the site. can you update it to only change the opacity of the box, nothing else?

Yeah.. Done. I set the background color to gray with opacity: 100%
Is this alright? @lmccart

closed with #86


[Extensibility Request] emun 362 "Analysis Period Type" reuqest to make extensible

We would like to request making this enum Extensible = true; so that we can add our own custom elements to it to support our processing of an Accounting Year type.  Thank you.

Hello! This enum is extensible:
enum 362 "Analysis Period Type"
{
Extensible = true;
AssignmentCompatibility = true;
value(0; "Day") { Caption = 'Day'; }
value(1; "Week") { Caption = 'Week'; }
value(2; "Month") { Caption = 'Month'; }
value(3; "Quarter") { Caption = 'Quarter'; }
value(4; "Year") { Caption = 'Year'; }
value(5; "Accounting Period") { Caption = 'Accounting Period'; }

}


The doc version display in the top bar  is abnormal

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[x] I'm using the latest version of Docusaurus.
[ ] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[ ] I have read the console error message carefully (if applicable).

Description
The version of the first figure is displayed normally, while the Version 1.1.1 of the second figure is displayed as Next. This problem occurs when I switch from an English document to a Chinese document.

Reproducible demo
No response
Steps to reproduce
1.download the source code git clone -b doc1 https://github.com/Beacontownfc/incubator-linkis-website.git
2.run yarn install
3.run npm run start-zh
Expected behavior
The drop down version number of Chinese docs is the same as that in English.
Actual behavior
The drop down version number of Chinese docs isn't the same as that in English.
Your environment

Public source code: https://github.com/Beacontownfc/incubator-linkis-website
Public site URL:
Docusaurus version used: 2.0.0
Environment name and version (e.g. Chrome 89, Node.js 16.4): Node.js 16.15.0
Operating system and version (e.g. Ubuntu 20.04.2 LTS): windows11

Self-service

[ ] I'd be willing to fix this bug myself.

This is because you have set the translation of the version label as "Next". https://github.com/Beacontownfc/incubator-linkis-website/blob/35e1a9976c40a6aa906249fa8e59156a7e3668bf/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1.json#L3
Just change that to 1.1.1.

This is because you have set the translation of the version label as "Next". https://github.com/Beacontownfc/incubator-linkis-website/blob/35e1a9976c40a6aa906249fa8e59156a7e3668bf/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1.json#L3
Just change that to 1.1.1.

Thank you!!!


V2.1.0

@sawyercade review
Changes:

Support for expunging shards from a blacklisted node
First class support for node exclusion at the simulation level (faster/better simulations)
Made all tempest settings dynamic
The _tempest endpoint now works correctly on non-primary masters
Added a "status" field to _tempest status output
Removed cluster score, risk, and ratio from status output (pretty unless to the average user)
Added a _tempest/rebalance endpoint for forcing a rebalance without tweaking settings
Removed structural hashing and time based backoffs for balancing (too fragile with dynamic settings)

Your assumption about expungeBlacklisted nodes is correct.


add hfetch (my fetch tool)

github page: https://github.com/gentoo-btw/hfetch

nah, hfetch was chaos anyway


ListViewCommandSet not showing anything in SPO

Category

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

Expected or Desired Behavior
I already opened an issue over there but I am not sure how maintained it is, so I am posting here as recommended by the documentation here.
When building a ListViewCommandSet extension using the latest yeoman generator's default configurations with the following commands :

gulp bundle --ship
gulp package-solution --ship

And we deploy the resulting .sppkg file to the app catalog, and we install the app on a site, we should see the list command button appear as expected when navigating in a library.
It really is blocking for me right now because I developed a full extension ready to be deployed in production, but I can only make it work in debug...When deploying the .sppkg nothing works. I must do something wrong, I have a hard time believing it's a production bug in SPO as there would be much more issues like mine, but I can't figure out what I am doing wrong.
Observed Behavior
Nothing happens, both list command buttons do not appear, the script isn't even loaded in the Network tab of the browser. When debugging the extension using the URL query string and gulp serve, everything works perfectly, the load debug scripts modal appears, I can accept, then list extension is loaded and everything works.
However, when I deploy the official .sppkg to the app catalog, everything goes smoothly, I can install the app in my site collection, but once the app is finished installing nothing happens.
Steps to Reproduce

Create a ListViewCommandSet using the latest yeoman generator like here.
Leave everything as is
Deploy the final sppkg to the app catalog (gulp bundle --ship / gulp package-solution --ship)
Add the app to a modern site collection
Once the app is installed, go in a library and notice the list buttons that aren't showing

Finally found the problem. The main issue was totally my fault : The elements.xml was configured the run on list templates 100 and not 101, causing the extension to appear only on lists and not on document libraries.
Now the reason why it took me so long to realize this is because of what looks like a bug in my opinion : The whole time I was debugging the extension while developing it, the extension was working on document libraries even though the custom action is configured to run only on lists. The fact that it was running perfectly fine in debug is quite confusing because I automatically excluded the possibility of such a configuration error.
In my opinion the debug mode should reflect the .sppkg behavior, it should take into account the custom action's configuration to avoid confusion.
Closing this issue!

Thanks for the feedback @spplante .  I'm not sure if there is anything we can do here, in that the debug string basically says "load this assembly" - ignoring the package entirely.  I don't think we even have any reference to the config.  But we'll keep the confusion in mind and see if we can reduce the chance of this happening for others.
Pat.

I could imagine some kind of mechanism that could read the custom action's file before reading the assembly, and based on conditions generated from the custom action config (ie : if currentList.Type == customAction.type) if could load (or not) the assembly. Easier said then done but you get my point 👍


HP Chromebook 14a - doesn't see USB nor SD on Tianocore using RW_Legacy

HP Chromebook 14a (LANTIS/Jasperlake) fails to see SD card and USB stick at boot into alternative bootloader.
Have used both SD and USB to do a chromebook recovery, so I know the drives work at boot time, but going into grub shell and doing ls with no drive, then with SD and USB in turn, shows no new drives.  On one iteration, a (cd0) appeared but ls (cd0)/ showed invalid filesystem.  Normal drives are (hd0,1-12) (hd1) (hd2) and infrequently (cd0)
Have used Kali, Ubuntu. Debian live ISO's using Rufus (dd mode) and etcher, no joy.
Any suggestions?  with LANTIS/Jasperlake, I have no other option except RW_Legacy.

Also, tried to use a Kali live image renamed to .bin as source for recovery USB, no joy.
Dev_boot_usb = 1
dev_boot_legacy = 1
dev_default_boot = 0
dev_boot_signed_only = 0
USB does light up (access) during loading of Tianocore
Normal boot shows SD and USB as /dev/sda or /dev/sdb and can read contents without issue

quite simply, it's a Tianocore bug/issue. I'd (or you'd) need an affected JSL device, a Suzy-Q cable, and a debug build of Tianocore to try and diagnose the issue.

Also, tried to use a Kali live image renamed to .bin as source for recovery USB, no joy.

of course not, Recovery mode only boots a signed ChromeOS image/kernel

I procured an older test chromebook and followed the same process.
HP Chromebook 11 G5 EE - RELM/Braswell
Process worked without any issue on first try.
One difference, the script installed SeaBios, not Tianocore.   Is this expected behavior and if so is there a point where SeaBios is not the best replacement for RW_legacy?
For instance, if I wanted to get the most recent Chromebook that supported SeaBios and were most compatible without going EUFI,, would that cutoff be Kabylake / Amberlake?  This guess just comes from the compatibility matrix, that seems to be where there is a systemic change between RW_legacy and UEFI.
Thanks for the help.

it's not a SeaBIOS/Tianocore issue, most boards have working SD card readers regardless of payload used. The changeover is with boards which use the Alternative Bootloader Menu. Some KBL have it, everything forward from there does.

Just so I understand.
If the issue I faced with a newer Chromebook was a Tianocore issue not recognizing USB nor SD at boot and going to an older Chromebook installed SeaBIOS instead of Tianocore for RW_legacy (or so it appears - same script operation but it appears a different payload was delivered).  Are you saying the real payload the same even with different boot messages or did I bypass the Tianocore issue by having SeaBIOS delivered instead?
In other words, what seems to have changed is a different payload (SeaBIOS) bypassing a Tianocore issue.  The payload difference is triggered by the specific board in the Chromebook, but the problem is not necessarily Tianocore vs. SeaBIOS but I would likely have seen the same problem even if SeaBIOS was installed on the newer one?
Just trying to understand what changed or where the error resides.  If I could get SeaBIOS installed on the newer one, this would not address the issue in your experience?
Thanks again.

Tianocore issue not recognizing USB nor SD at boot

some SD card readers have issues, it depends on the platform/how the SD reader is wired. Every board is different. USB devices will work under Tianocore. Sometimes you have to remove/reinsert from the main menu. Some USB sticks are just temperamental. But it's been tested working on pretty much every single board.

I would likely have seen the same problem even if SeaBIOS was installed on the newer one?

no, SeaBIOS and Tianocore each have their own drivers/init for boot devices, so a problem on one tells you nothing about how the other might behave on the same hardware

If I could get SeaBIOS installed on the newer one, this would not address the issue in your experience?

If SeaBIOS booted on newer platforms I'd offer it. It doesn't. it's 2022, Intel stopped supporting Legacy BIOS/legacy boot years ago. And I don't have the time/interest to try and make it work

Thanks, makes sense.
Appreciate the detailed explanation.

so I recommend retrying on LANTIS with simply removing/reinserting the USB/SD on the main menu, then going into the boot menu

I'll give that a try

Test process:

Start with known good SD and USB with Kali live image.
Boot new Chromebook to Chrome OS
Insert each external device
Result - ChromeOS sees them both
Reboot, leaving both devices in
Choose Alternative Boot Load
Go to grubb command line
ls shows internal device with partitions, three other devices. none of which has a recognizable filesystem (note, with no device, hd0, hd1, hd2 shown, with both devices plugged in, cd0 is added)  No joy booting
Reboot to ChromeOS with both devices
Result - ChromeOS freezes at the splash screen
Remove one device at a time and repeat - get to boot menu, ChromeOS normal boot doesn't like both devices (which are both bootable) inserted at same time.
Repeat process with each device
No joy with SD card - unplug and replug before going into boot menu - no change.
No joy with USB - unplug and replug before going into boot menu - no change.

So if Grub is supposed to autoconfig, that is not happening.  ls from grubb command line never shows any new devices with either plugged in at boot, or unplugged and replugged at first screen.  But if boot to internal drive, both devices are seen and fully accessible.

Note: known good means they boot just fine with the older Chromebook.

Choose Alternative Boot Load
Go to grubb command line

ok, not sure why you're doing that -- that's not how you boot. You need to press ESC when prompted, then go into the Tianocore UEFI menu. Insert the USB/SD, wait a sec, then go into the Boot Menu.
no idea what steps 9-11 are supposed to show, my RW_LEGACY firmware has nothing to do with how ChromeOS behaves.

also, a USB/SD device which boots via Legacy BIOS (SeaBIOS) has no bearing on it booting via Tianocore (UEFI). Linux ISOs should be written as disc images (dd mode).

After using the firmware script, when the Chromebook boots, it goes to a screen saying you are in developer mode - there is no prompt for ESC, that is what I see in the older Chromebook with SeaBios.
So it boots to screen with:
Return to secure mode
Boot from internal disk
Boot from external disk
Select alternate bootloader
That's with pressing no keys.
Go into Select Alternate Bootloader
Then select Tianocore
Get Tianocore screen with Esc for boot settings prompt
No action - then you get error: file /syslinux/vmlinuz.A not found,
then get dumped to Grub screen with 5 options -
local image a,
local image b,
verified image A,
verified image B,
Alternate USB boot.
choose Alternate USB boot, get errorL file /boot/vmlinuz not found
So I go into the grub command line to see what it can see - and all it sees is the local disk and filesystems. Hence my comments.
It always goes to these same menus with these same errors, with both USB and SD inserted before startup, or reinserted at first menu or after verified valid and accessible in ChromeOS and reboot.
Grubb edit shows it is looking at hd0,3 (local disk) for (hd0.3)/boot/vminuz  for the alternate USB Boot.
The other detail is just the process and iterations I did in detail.

After choosing Tianocore, get a brief prompt for Esc.
Get an HP Lantis Boot screen
Boot Menu shows two devices
eMMC device - choose this, dumps to Grub with same failures above.
UEFI shell - This drops me to a shell, exit takes me back to Boot menu
Go back, pick Boot Manager
Change boot order - eMMC or UEFI Shell - if I change the order, then commit, the commit is not persistent
Add boot option - just shows 4 options mapped to the grubb Hd0 disk - partitions 3,5,8,12)
Boot from a file - same options
Note, none of these options change whether or not an SD or USB is present, removed and reinserted, or absent.
So no joy if I hit ESC on Tianocore or just let it go to failure
Looks like the SD and USB is never seen by

on the previous comment, both USB and SD devices are ISO images written using DD and work successfully with no alterations using the older Chromebook and SeaBIOS.

No action - then you get error: file /syslinux/vmlinuz.A not found,
then get dumped to Grub screen with 5 options -

This is a remnant of ChromiumOS, DON'T USE THIS

After choosing Tianocore, get a brief prompt for Esc.

press ESC
wait for settings menu
insert USB/SD
got to boot menu
select USB/SD to boot from

THAT'S IT. don't mess with anything else or any other boot options.

Will do.
Thanks, as always, for the help.

Ran the test.
USB successful when inserted at Tianocore menu, then into Boot menu.   SD card, no such luck.  With the USB, you can see the drive being accessed via lights on reinsert, but with SD of course, no indication that a new device discovery is happening.
But this is a great improvement.
Thanks for making it more clear.

I'd need a debug log to figure out if it's a simple timeout issue with the SD card or something else. Only way to do that is with a debug tianocore build + debug stock firmware + Suzy-Q cable

I ran another test, using a USB hub that had an embedded microSD card reader.
Worked like a charm.
I'd be glad to help and can probably get a Suzy-Q cable if they are still available (not on Amazon that I can find), but I'm not a developer so the diagnostic process may be a bit beyond my experience.

closing as not a script issue


does not render when  has dynamic latLng

The <DivIcon> renders as expected when I pass hard coded values to <Marker latLng={[500,500]}>
But <DivIcon> does not render at all when I pass dynamic values from #each to <Marker latLng={[location.lat, location.lng]}>
Does anyone have any ideas why this is the case and how to fix it or possible work arounds. I have hit a wall.
Hard coded latLng works:
{#each locationArr as location, ii}
	{#if location.meta.lat && location.meta.lng && location.meta.key}
		<Marker latLng={[500,500]}>
			{console.log([location.meta.lat, location.meta.lng]+' '+ii), ''}
			<DivIcon>

					123

			</DivIcon>
		</Marker>
	{/if}
{/each}

Dynamic latLng does not work:
{#each locationArr as location, ii}
	{#if location.meta.lat && location.meta.lng && location.meta.key}
		<Marker latLng={[Number(location.meta.lat), Number(location.meta.lng)]}>
			{console.log([location.meta.lat, location.meta.lng]+' '+ii), ''}
			<DivIcon>

					123

			</DivIcon>
		</Marker>
	{/if}
{/each}

Same happens to me as well

@mugu-fatman I was able to fix this by modifying the Marker.svelte component.
Change line 34 if (icon) marker.setIcon(icon);


Obtain reason for failure?

I've gotten several lightning payment failures, would it be possible to get more info about those from the wallet? For example why did it fail, which node caused it, etc...
What's the difference between refunded and frozen?

I've gotten several lightning payment failures, would it be possible to get more info about those from the wallet?

Yes, once a payment gets failed you can tap on it in a payment list and then "Share debug info" in popup window. The trick is debug info is not persisted anywhere and only accessible at runtime so it can only be obtained once a payment is failed, it won't persist after app restart and "Share debug info" won't be visible then.

What's the difference between refunded and frozen?

Frozen is an off-chain payment which has been in-flight at the moment when channel got broken. It will either be fulfilled off-chain later or refunded on-chain once it's delay gets cleared. When you see a frozen off-chain payment you should also see a pending on-chain refund in a payment list. That refund value should be equal to frozen payment's amount minus on-chain miner fee. Is this the case?

"Share debug info" won't be visible then

That explains why I remember seeing them but don't anymore

equal to frozen payment's amount

I think this is what happened to me, just that it wasn't clear from UI.
Thanks!

I think this is what happened to me, just that it wasn't clear from UI.

Agreed, this is perhaps the most mind-bending part of LN. Perhaps one day I'll come up with a better way to represent them on UI.

Perhaps frozen payment could have a view refund button that would behave
as-if user had clicked the corresponding refund transaction from main
view? So it would switch to popup of refund transaction instead of
frozen transaction.

Thing is, we can't dismiss that frozen off-chain payment until corresponding on-chain refund gets broadcasted because depending on your peer's actions you may get that frozen payment confirmed off-chain (and corresponding on-chain refund will fail then).
And in some very specific conditions you may even get both off-chain payment and on-chain refund confirmed. You will get some free money then at peer's cost.


Ubuntu 21.04 - dotnet will not start without sudo

Description
I have dotnet_sdk 5.0.401 installed as a snap on Ubuntu 21.04. Typing the command "dotnet" gives the following error:

In previous versions, this has worked without requiring elevated privileges.

Configuration

Regression?

Yes, this is a regression. The dotnet command used to work on Ubuntu without requiring sudo.
Other information

I run into the same problem also on Ubuntu 20.04. It seems there may be some packaging problem with the snap of dotnet-sdk 5.0.401 (140). This is a show-stopper.

[Major] The permission of /snap/dotnet-sdk/140/snap/ is 700 on my test VM. This explains why rev 140 regresses to require sudo. (I have checked that the corresponding permission is 755 in 5.0.202 (120)).
[Minor] Why is there a .DS_Store? :> (It's harmless; and FYI it is also in rev 120.)

root@dotnet-sdk-demo:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.3 LTS
Release:        20.04
Codename:       focal

root@dotnet-sdk-demo:~# ls -la /snap/dotnet-sdk/140/snap/
total 7
drwx------  3 root root   53 Sep 10 20:33 .
drwxr-xr-x 12 root root  249 Sep 10 20:33 ..
-rwx------  1 root root 6148 May 12  2020 .DS_Store
drwxr-xr-x  2 root root   39 Sep 10 20:33 command-chain

This and https://github.com/dotnet/core/issues/4446 seem related. Cross-linking.

@leecow can you look at this?


Add accessibility statement

This PR adds the accessibility statement to the accessibility page in the Design System

You can preview this change here:
Built with commit bd487a74900815b7d274792723a5e37f423e8e5f
https://deploy-preview-1068--govuk-design-system-preview.netlify.com

This has been approved by the Head of Product for Portfolio and sent to the accessibility compliance team.
It just needs a final 2i from @m-green

🚀


tpl: Update Hugo time to support optional [LOCATION] parameter

Fixes #7860
This PR adds an optional [LOCATION] parameter to the Hugo time function which will internally utilize Go's ParseInTimezone() functionality to return a time.Time instance that is associated with a specific timezone.

✔ No breaking changes. (Added functionality only)
✔ Documentation updated.

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

@bep @moorereason Hey guys. Mind taking a look? I think I addressed the concerns from the other PR. Thanks.

I pushed a commit to your branch to refactor a few things, but it's essentially the same logic.  I tried to clean up the docs to make it clear that the location is a default.  I also try to use "location" instead of "time zone" since it makes more sense to me, but maybe I'm off base there.  Comments welcome.
@bep, PTAL.

Thanks @moorereason . Minor tweaks. LGTM

Thanks @bep and @moorereason


Opening an existing file

It would be great if you could tear off an existing xlsx-file, for example, ready-made templates, for later recording. Is this possible in the future?

One of the main goals of this library is to be able to stream data to it without having the entire sheet in memory.
What you are asking is conflicting with this goal as it would require loading the template in memory and modifying it there.
To do what you are asking for you are better off using a library that is loads the spreadsheet in memory before saving it.
Here are a few links to other libraries, maybe one of them does what you need:


also write down the xpub for the paper wallet

On this page:
https://btcguide.github.io/setup-wallets/coordinate-multisig-advanced
It says:

We want to verify that the pubkey from this piece of paper has been included in our quorum. Confirm that your Zpub... from the Setup Paper Wallet Step is included on your Cobo Vault (above).

However, we were never instructed to write down the xpub/Zpub in the Setup Paper Wallet step.
This PR adds that instruction

Thanks @mmikeww. What's the thinking behind this step? Xpub info is not designed to be transcribed that way (like bip39 seed phrases), and you need all m of them. Plus they also include paths, root fingerprints, etc. It's an amount of data that really should be saved digitally.
I'd be fine with this as an advanced recommendation for extra redundancy, but as a default rec writing pubkey down for each seed seems counterproductive for non-advanced users. Closing for now.
I'm not sure if the guide properly recommends the new PDF feature but it should and a PR for that would be welcome.

Thanks @mmikeww. What's the thinking behind this step? Xpub info is not designed to be transcribed that way (like bip39 seed phrases), and you need all m of them. Plus they also include paths, root fingerprints, etc. It's an amount of data that really should be saved digitally.
I'd be fine with this as an advanced recommendation for extra redundancy, but as a default rec writing pubkey down for each seed seems counterproductive for non-advanced users. Closing for now.
I'm not sure if the guide properly recommends the new PDF feature but it should and a PR for that would be welcome.

Well the thinking is based on the link linked:
https://btcguide.github.io/setup-wallets/coordinate-multisig-advanced
You want to verify the xpubs on the device itself. Because as you note at the bottom of that link, we assume the computer is malware infected, and so, the PDF export could be malware infected as well.
But the paper wallet has no such 'device' to verify on. So if we had written the xpub/Zpub on paper when we generated it with seedpicker, then we'd have a legitimate copy.

Well the thinking is based on the link linked:
https://btcguide.github.io/setup-wallets/coordinate-multisig-advanced
You want to verify the xpubs on the device itself. Because as you note at the bottom of that link, we assume the computer is malware infected, and so, the PDF export could be malware infected as well.
But the paper wallet has no such 'device' to verify on. So if we had written the xpub/Zpub on paper when we generated it with seedpicker, then we'd have a legitimate copy.

Maybe we want to call out xpub verification (against a malicious specter-desktop) explicitly as a verification step, but I think this is too much/confusing for regular users where it's already kind of implied.
Advanced users are recommended to compare the output against another source (these could probably use an update as well, I'll probably add multiwallet for example over pure CLI scripts):
https://btcguide.github.io/setup-wallets/paper-advanced#verify-seed-generation

Maybe we want to call out xpub verification (against a malicious specter-desktop) explicitly as a verification step, but I think this is too much/confusing for regular users where it's already kind of implied.
Advanced users are recommended to compare the output against another source (these could probably use an update as well, I'll probably add multiwallet for example over pure CLI scripts):
https://btcguide.github.io/setup-wallets/paper-advanced#verify-seed-generation


Addon Postgrest

Description of your changes
This PR Adds Postgrest as an addon

How has this code been tested?

Checklist

I have:

[x] Title of the PR starts with type (e.g. [Addon] , [example] or [Doc]).
[x] Updated/Added any relevant documentation and examples.
[x] New addon should be put in experimental.
[x] Update addon should modify the version in metadata.yaml to generate a new version.

Verified Addon promotion rules
If this pr wants to promote an experimental addon to verified, you must check whether meet these conditions too:

[x] This addon must be tested by addon's e2e-test to guarantee this addon can be enabled successfully.
This addon must have some basic but necessary information.

[x] An accessible icon url and source url defined in addon's metadata.yaml.
[x] A detail introduction include a basic example about how to use and what's the benefit of this addon in README.md.
[ ] Also provide an introduction in KubeVela documentation.
[ ] It's more likely to be accepted if useful examples provided in example dir.

Although we already have the Postgrest operator as an addon, there are potential reasons to consider the need for this new one?

@wangyikewxgm Yes, We do have Postgres-Operator as addon but don't have Postgrest as addon for more please visit https://postgrest.org/en/stable/

@wangyikewxgm Yes, We do have Postgres-Operator as addon but don't have Postgrest as addon for more please visit https://postgrest.org/en/stable/

Can we use this component Definition to create  a postgrest database instance?

@wangyikewxgm I think it will not be possible, as creating a working postgrest instance requires setting parameter PGRST_DB_URI to connect postgrest with running postres successfully and the postgre-operator's component definition is used to create an instance for postgres.
I hope it makes sence to you.


README mistake

https://github.com/raeleus/stripe/blob/187471f57aae3c0e0793077c88207bbdaabd97ee/README.md?plain=1#L28
Should be com.github.raeleus:stripe:1.4.1.  Likes in viewports-sample-project.
The same with other com.github.raeleus.stripe in README.

The new format is correct. This is because there are subprojects for PopColorPicker and FreeTypeSkin. Viewports sample project uses an old version. Thanks for checking though!

Oh I know why I can't use it before. I copy the README single quotation marks version and try to use version number variable, and gradle can't handle it, then I copy the old version double quotation marks so it works.


Add a GitHub action to lint the Markdown.

Add a basic Markdownlint config file.
Lint some Markdown.

@jbampton Thanks so much for these.
I think this could really help improve the docs quality/consistency.
I had a few questions to help me understand how this works:

I didn’t see a change to package.json. Should we make markdownlint-cli a devDependency?
As for the Github action, I take it this will show a success/fail check on PRs. Please confirm if this is the case. Also, will a fail on this action prevent the deploy action? Is that what we want?

cc @ispivey @signalnerve @rita3ko for their thoughts.

I think it is up to you if we add markdownlint-cli as a devDependency.  I have added this feature to some other repos and we did not add it as a dependency.
Yes this shows up as successful or as failed.  You can see it passed for this PR.  It will print out the line numbers of the failures including what failed if it does fail.
This check is separate to the deploy action so a failure on the markdown lint will not prevent the deploy action from working but we could change this if needed.

+1 on this being on PRs only, i don't think it should block deploys
is there a skip rule? if we're managing an internal PR, we don't want to be blocked by linting if we really need to merge something. also don't want those potential issues to get bunched up w/ any potential new linting issues found in external PRs.
thanks, this is super cool btw

This check is separate to the deploy.  So it won't block the deploy action. And it won't block existing PRs just merge them and fixing the linting errors another time.  It will still deploy.
I have it setup as seen in the image below so we can still deploy even if the linting fails in this repo ->
https://github.com/slurpcode/slurp
This is depoying -> https://magic.slurp.workers.dev/  👍

Also there are rules and you can even run --fix for auto fixing simple errors.
markdownlint --help

  Usage: markdownlint [options] <files|directories|globs>

  MarkdownLint Command Line Interface

  Options:

    -h, --help                                  output usage information
    -V, --version                               output the version number
    -f, --fix                                   fix basic errors (does not work with STDIN)
    -s, --stdin                                 read from STDIN (does not work with files)
    -o, --output [outputFile]                   write issues to file (no console)
    -c, --config [configFile]                   configuration file (JSON, JSONC, JS, or YAML)
    -i, --ignore [file|directory|glob]          file(s) to ignore/exclude
    -p, --ignore-path [file]                    path to file with ignore pattern(s)
    -r, --rules  [file|directory|glob|package]  custom rule files

https://www.npmjs.com/package/markdownlint-cli

hey @jbampton !
we've just migrated our content to a new repo: https://github.com/cloudflare/cloudflare-docs (third time's the charm? 🙂). the new repo is actually going to contain all the docs for the other cloudflare products as well, but we're still in the process of migrating all the content over from some of our internal repos.
if there's a way to reopen this, with the linting configured to be restricted to the workers content, would really appreciate you reopening it there.
otherwise, we'll wait until we're done with the migration.
thanks as always for your contributions! going to close this for now.


Update best-practices-onboard-deploy.md

Updated based on the latest developments in collaboration with AT&T

@sherrygonz - can you review the proposed changes?  Note also the warnings fixes called for above.
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@sherrygonz - can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


[CT-627] [Feature] Allow references to input parameters, specifically for dependency handling

Is this your first time opening an issue?

[X] I have read the expectations for open source contributors

Describe the Feature
When dbt projects become large, models are used in many places, and even small failures can bring down business critical portions of the DAG.
To isolate risk, it would be useful if a reference (or source) could take a parameter for what to do if that model fails. Arguments could include, 'proceed', 'skip', where 'skip' is the current default behavior.
For instance, we have a minor ref table that failed and it caused our main fact to fail. However, the little ref is not critical to the fact table, and we would be happy to proceed without that data. However, that ref table is critical to another dimension, so we would want that DAG to skip.
Describe alternatives you've considered
I've considered the tests and built DAG alternatives, but that doesn't allow customization across portions of the DAG.
Who will this benefit?
This will benefit users who have large projects with complex dependencies.
Are you interested in contributing this feature?
No response
Anything else?
No response

@smitsrr There's been a lot of new and recent conversation in https://github.com/dbt-labs/dbt-core/issues/2142, including a comment I see from you! Prompted by those comments, and also your thoughtful issue here, I've just reopened it and left a new comment: https://github.com/dbt-labs/dbt-core/issues/2142#issuecomment-1125917049
One thing I mentioned there:

I'm hesitant to support defining this configuration for the full matrix of parent-child relationships, as I think that can get unwieldy very quickly.

As the person writing the model, I see the intuitive appeal of being able to configure this right within the ref() / source() specification. When these models are actually running in production, I'm worried about the ballooning complexity that comes from so many different behaviors, which would require jumping back through the dbt source code to understand the cause.
I'd much prefer to reason clearly about a model that MUST block downstream builds (if we choose to configure this on the parent), or a model that MUST run (if we choose to configure this the child).

small failures can bring down business critical portions of the DAG

I'd push back slightly on "bring down." One important feature of dbt's modeling paradigm is that, in almost all cases, model builds ought to be idempotent and atomic. (There are precious few exceptions: snapshots; --full-refresh on certain adapters that don't support create or replace or rename-swapping.) If an upstream model build fails, the database views and tables built by downstream models do not go away. They do get stale, over time, if the upstream model continues to fail without recourse. Hopefully that's an unusual occasion, and one where a manual intervention is warranted, to run the critical models while excluding the failing non-critical ones.
I'm definitely open to discussing this more. For now, I see this idea as very closely related to the one in https://github.com/dbt-labs/dbt-core/issues/2142, so I'm going to close this issue to keep the conversation centralized over there.


cla test

@laojiuh, VMware has rejected your signed contributor license agreement. The merge can not proceed until the agreement has been resigned. Click here to resign the agreement. Reject reason:

cla test 0109

@laojiuh, we have received your signed contributor license agreement. It will be reviewed by VMware shortly. Another comment will be added to the pull request to notify you when the merge can proceed.

@laojiuh, your company's legal contact has approved your signed contributor license agreement. It will also be reviewed by VMware, but the merge can proceed.

@laojiuh, VMware has rejected your signed contributor license agreement. The merge can not proceed until the agreement has been resigned. Click here to resign the agreement. Reject reason:

qweqe


Fix#8815/fix clear button aligned arrow

Proposed Changes

Fixes #8815
[x] The clear button should clear the already selected data in the input field
[x] Align the dropdown arrow to be in the center rather than the top of the input field

@ohcnetwork/care-fe-code-reviewers
https://github.com/user-attachments/assets/f10cf8de-cef7-4ac9-95ea-ef1e7c649eef

@rithviknishad @nihal467 the cross button is implemented such that it opens the dropdown on click , do you want to remove this?
current:
https://github.com/user-attachments/assets/879bbbb4-1026-4bb1-9701-6da932d378ca
i have implemented the changes which will not open the dropdown on click of cross button, should i push?
https://github.com/user-attachments/assets/5fc69f78-dc60-4dfb-ad79-3a423c6c740c

@NitinPSingh the cross button is implemented such that it opens the dropdown on click , keep this behavior itself

@nihal467 ok , i havent push that part yet , so the current code will clear the selected and also open the drop-down

all green now

LGTM

@NitinPSingh Please do add a human firendly title for the PR

this wasn't intended right?

something went wrong here i guess let me fix , i create new pr


Add taxonomy template for tag pages

A slightly modified copy of contents from the index.html template so that tag pages are rendered with only relevant articles.
Closes: #75

Thank you!


Add a magical function testinfra_hosts_update to update host list in runtime

This adds a support for optional magical function testinfra_hosts_update to each module, which allows to filter host list after it was created by testinfra.get_hosts before doing an actual test parametrization. Practially, it's allow to filter/update/mangle host list after it was become a list of concrete hosts.
The issue it tries to solve is that testinfra_hosts when used in tests for molecule/ansible environment usually contains group names (as host names are volatile in many molecule usecases), and some tests may requires to be "run_once" for a given group.
The practical scenario is like this (mons is a groups for Ceph monitors):
testinfra_hosts = ["ansible://mons?force_ansible=True"]

def testinfra_hosts_update(host_list):
    return testinfra[host_list[0]]

def test_cluster_OK(host):
   assert 'HEALTH_OK' in host.check_output('ceph -s').stdout

Hi thanks for this. But I think it's a bit too magical :)
Maybe It's better to handle ansible patterns no ? See #602

I thought about it. I really would like ability to specify the hosts-style host list (something like that: ansible://mons[0],mgrs,!foobar, which says 'host #1 from monitors, all mgrs, but not the stuff in foobar group or named foobar'), but I suspect it's hard to implement.
Actually some kind of hook to process the hostlist after it was parsed and processed by Ansible is really welcomed. Ansible inventory is really tricky thing (given the molecule control over inventory), so ability to tweak results are important, I think.
The magicalily of testinfra_hosts_update is on pair with testinfra_hosts, I think. Better naming may be a good idea, though.

@amarao I added some comment on #602 , seems ansible --list-hosts <pattern> resolve hosts from the pattern. In any cases I think we need to implement this. And maybe later on we could add such hook if needed.


Add close method to RubyTcpSender

Match the same functionality that RubyUdpSender has in allowing user of RubyTcpSender to close all sockets.

Thank you very much.


CLOUD-53847 remove premium storage for now

@biharitomi

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2232/


indicate that Factory must be used in the require

It is difficult to realize at first glance at the README that this line is necessary without diving through the source. This change would easily mitigate that problem.

Something like this might be useful, but people use Rosie in different ways. This is correct for Node.js, but if you're using Rosie in the browser this is probably not correct.

@eventualbuddha without this change it is probably correct in the browser, but probably not correct in node. We can track npm/bower installs but not really browser ones, so it's (probably?) impossible to determine which is more likely.
Maybe a good solution would be to have an example folder with some real world examples? The examples on the readme don't all run. For instance one passes in Game to a factory definition, but where does that come from?
Alternatively, we could have a new section under usage to use that line if running under node.
Thoughts?

@blainesch @phishy let me know what you think of my proposed README.


HTML tags inside image alt shouldn't be parsed

http://markdown-it.github.io/#md3={"source"%3A"%23 Issue 579\n\n![text <textarea> text](image.png)\n"%2C"defaults"%3A{"html"%3Atrue%2C"xhtmlOut"%3Afalse%2C"breaks"%3Afalse%2C"langPrefix"%3A"language-"%2C"linkify"%3Atrue%2C"typographer"%3Atrue%2C"_highlight"%3Atrue%2C"_strict"%3Afalse%2C"_view"%3A"src"}}
Currently, any HTML tags are swallowed. The spec is a little light https://spec.commonmark.org/0.30/#images but recommends that the string not be parsed.
See how GitHub will render the raw string:

Ref https://github.com/DavidAnson/markdownlint/issues/579

CM Dingus https://spec.commonmark.org/dingus/?text=%23 Issue 579

![text <textarea> text](image.png)

As far as i remember, tags are parsed in alt, but ignored later for security reasons.

Found a relevant discussion https://github.com/commonmark/commonmark-spec/issues/716 but there is no resolution right now

Let's close this as spec-related. When reference parser updates behaviour, that will be reflected here.

The reference parser already has this behaviour as you showed in the dingus link

Thanks for re-opening!
It is definitely under-speced, but one where this is doing something different than remark, so there are conflicts between Prettier (that uses remark) and Markdownlint that uses this library

The reference parser already has this behaviour as you showed in the dingus link

Which reference parser?
This is commonmark.js (javascript):
$ echo '![text <textarea> text](image.png)' | /home/user/commonmark.js/bin/commonmark

<img src="image.png" alt="text <textarea> text" />

This is cmark (C):
$ echo '![text <textarea> text](image.png)' | /home/user/cmark/build/src/cmark

This is commonmark-hs (haskell):
$ echo '![text <textarea> text](image.png)' | /home/user/.local/bin/commonmark

This behavior is absolutely trivial to fix, but maybe people should first agree on how to fix it.

This is pending too long. Need to decide something
https://github.com/markdown-it/markdown-it/blob/13829a2c7e6c94a2b714bb666f05065b6996bfb4/lib/renderer.js#L301 -  blocking this feature via renderer patch is quite easy. But I agree, such behaviour can be very unexpected for ordinary use. Probably, it would be better add option and disable that by default.
Could you suggest short and verbose option name? Something like imageAttrHtml but more pretty.

Just to be clear, it seems to me that of the options above, "text  text" is the least surprising result (and therefore the best choice in my mind). Is that what you are suggesting to make the default?

My proposal is to disable HTML in  image attrs by default (except commonmark mode). So, by default < and > in text <textarea> text will be escaped.

Solved in master


[question] how to enable function signature on completion menu

Hello, thanks for your work on this plugin. I apologize if this is not the right place to ask this question.
I was wondering if there was an option for this plugin to show the function signature (i.e: parameters and return type, if any). I'm looking for this kind of documentation but I haven't had any luck
This is what I'm currently getting from the plugin:

This is what I would be looking for:

That didn't work for me


Update client.py to support InfluxDB access over reverse proxy

Add 'uri' optional parameter to be able to use reverse proxy !
Can also be done by overloading the existing InfluxDBClient object :
`class InfluxDBClient_RP(InfluxDBClient):
     def __init__(self,**kwarg):
         self.__uri= kwarg.get('uri','')

         if kwarg.has_key('uri'):
             del(kwarg['path'])
         super(InfluxDBClient_RP, self).__init__(**kwarg)

     def request(self, url, **kwarg):
         super(InfluxDBClient_RP, self).request("{0}/{1}".format(self.__uri, url), **kwarg)`

then configure for example apache like this  :
 <Proxy http://localhost:8086/*>       Allow from all  </Proxy>  <LocationMatch "/influxproxy">       ProxyPass http://localhost:8086 retry=0       ProxyPassReverse http://localhost:8086       RequestHeader set X-Forwarded-For %{REMOTE_ADDR}s  </LocationMatch>
finally use the uri param while creating the client :
client = InfluxDBClient_RP(host='myserver.domain.com', uri='influxproxy', port=443, ssl=True, database='somedatabase') client.write_points(points)

'insert code' is not working fine !?

Can you please add a test?

This change is exactly what I need. Let me know if there is anything I can do to help expedite this PR.

A lot of tests are failing with your patch. Could you please update your patch to include:

updated patch to pass existing tests
updated patch to add new tests for reverse proxy
squash your commits into one to ensure clean merge

@aviau UPDATE REQUESTED

Closing stale issue for now. If this is still required please let me know and we can re-open.


Unable to paste in "New Folder" input when saving file (OS X)

This is a repost of an issue posted on atom,
https://github.com/atom/atom/issues/10446
I would like to work on this bug, If someone could help me :)

This is interesting, it actually works in the default app of Electron, but not in Atom, it is probably related to how menu item actions are implemented. I'll reply in the Atom issue.


Portfolio-deployment

Abbas! you have done  good job here! I haven't find any issue with your deoployment.

Hey @Abbas-Aljuaifari your deployment seems to be working fine with pixel perfect features copied from the figma design, it looks great. No issues!

THANKS, GUYS FOR THE NICE FEEDBACK!!


tagged vs default

Has anyone ran into the issue where if you look to pull your own images via tagName, no problem, but pulling down the default images returns a 400 error from Instagram?
I have a website multiple events pages. Some of my events have a tag name and some do not. When they don't have a tag, I simply want to display my feed, whether its most popular, random, most-liked etc. etc.

What do you mean by "default images"?

option get would be unset or set to popular
option sortBy would be unset or set to none
Basically asking it to 'give me whatever you have from my account'. to give you some context, this event has/had a tagName associated with it http://adclubca.staging.wpengine.com/our-events/2016-digital-day/ so we only show that tagName. It is possible that an event may not have any pictures, in which case we simply want to show our feed based on the two options listed above.

The "popular" endpoint is no longer supported by the Instagram API, if your client was created after Nov 17, 2015.


FBP-13. Do not show errors in property fields

Fixes #13

Codecov Report

Merging #104 into master will decrease coverage by 0.00%.
The diff coverage is 23.07%.

@@             Coverage Diff              @@
##             master     #104      +/-   ##
============================================
- Coverage     54.14%   54.13%   -0.01%
- Complexity      575      576       +1
============================================
  Files            80       80
  Lines          3103     3105       +2
  Branches        586      586
============================================
+ Hits           1680     1681       +1
- Misses         1196     1198       +2
+ Partials        227      226       -1

Flag
Coverage Δ
Complexity Δ

#unittests
54.13% <23.07%> (-0.01%)
576.00 <0.00> (+1.00)
:arrow_down:

Impacted Files
Coverage Δ
Complexity Δ

...alb3r/bpmn/intellij/plugin/BpmnPluginToolWindow.kt
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...n/com/valb3r/bpmn/intellij/plugin/CanvasBuilder.kt
56.52% <50.00%> (ø)
4.00 <0.00> (ø)

...intellij/plugin/properties/PropertiesVisualizer.kt
62.50% <66.66%> (-0.66%)
22.00 <0.00> (ø)

...ginjection/FlowableDelegateExpressionUiInjector.kt
58.82% <0.00%> (+5.88%)
7.00% <0.00%> (+1.00%)

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 cb901f3...3d25787. Read the comment docs.


Support for the MTG-B2000 series

Hi,
will you perhaps add support for the MTG-B2000 model in the future?
I tried to connect it with the app but no success on my end.

Seems like this is an always-connected watch, similar to the Ediface ECB-30. I dont have this watch, but if I sent you an APK, can youi test it?

Yes, I will test it and let you know if it works for me.

Ok, great.
Just to be sure, if you have already connected to one watch , you should
press the FORGET button before connecting to the other. The display should
say "No watch".
Regards
On Sat, Nov 30, 2024, 1:14 AM sbstn87 @.***> wrote:

Yes, I will test it and let you know if it works for me.
—
Reply to this email directly, view it on GitHub
https://github.com/izivkov/CasioGShockSmartSync/issues/96#issuecomment-2508850020,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7M37WRQIXECQL7U7VJQIL2DFJTNAVCNFSM6AAAAABSXUHKS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBYHA2TAMBSGA
.
You are receiving this because you commented.Message ID:
@.***>

Yes, I did it and still could not connect.

After a few attempts I have successfully connected the watch.
Hard to say of al the features work fine, as the watch is purely analog, so some of the settings should not be supported.
But it did not crash and the ones I tested worked fine - sending time or setting alarm,

That's great.
Almost all watches can connect to the app, but of course they have
different capabilities. The app adapts to the watch by hiding/ showing some
features. For example, if the watch does not support reminders, the Events
screen will be hidden. I'll look into the capabilities of this watch, and
will add it to the app.
Thanks for testing.
On Mon, Dec 2, 2024, 7:27 AM sbstn87 @.***> wrote:

After a few attempts I have successfully connected the watch.
Hard to say of al the features work fine, as the watch is purely analog,
so some of the settings should not be supported.
But it did not crash and the ones I tested worked fine - sending time or
setting alarm,
—
Reply to this email directly, view it on GitHub
https://github.com/izivkov/CasioGShockSmartSync/issues/96#issuecomment-2511403750,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7M37UPBCMVACTEMURNJUT2DRG2XAVCNFSM6AAAAABSXUHKS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJRGQYDGNZVGA
.
You are receiving this because you commented.Message ID:
@.***>

Done


feature/add support for non-clustered children

Fixes #33
Added a check for a neverCluster prop on children of the map to exclude them from the clustering process. This allows use of child components such as GeoFences and Overlays, with the Cluster Map.

Sorry for the late response.
Thanks a lot for your idea. I'll enhance it a bit in #38 and add tests for this feature!


Add support for svelte

These are the snippets that I copied from vscode-svelte-snippets.
Also if we want extend javascript snippets, we could have this in our config
-- Note this should be before nvim-cmp setup
vim.g.vsnip_filetypes = {
    svelte = { "javascript" },
}

Hey, thanks for this.
You forgot to add the snippets to package.json

My bad, will update it

My bad, will update it


removed spring allow-bean-definition overriding issue

Hello, thanks for this very helpful project! We would like to use it in our system, but it's not possible to use bean overriding in our case. So i would like to contribute and hope, that with your help, we can remove this issue.
I removed default bean definitions from ~core projects. Now configuration looks like spring auto-configurations(base module only defines main interfaces, specific implementations contains beans)
For example to enable client discovery we should include client-discovery-core + client-discovery~ (where actually MetaDataExtender is configured)
Because of that, cluster - standalone -embeded configuration was restructured (not sure, that was correct strategy)
Embeded - is as BaseStandaloneConfiguration(without remote admin and job services) configuration with embeded admin and job services and map repositories (application and job execution event)
Standalone configuration is a BaseStandaloneConfiguration with remote admin services and map repositories (application and job execution event)
cluster-core is a BaseStandaloneConfiguration with cluster features
And InfinispanServerClusterConfiguration is a cluster with Infinispan repostiories and other features.
I tried to save all presented configurations and module dependencies, with a few required changes, due to bean overriding.
But it seems, that we should move to more distinct feature set with autoconfiguration for each of them (for example - base repository + jdbc / map

Hi @sudoHackIn
thank you for your contribution. I will take some time to verify the PR. I will come back to you as soon as possible.


Update .NET framework to v6

Update framework to .NET 6

Pull Request Test Coverage Report for Build dda5a2efa1806ce7998957aff376e05d085ea60b-PR-12

1 of 2 (50.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 87.168%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

VBaseProject.Api/Validators/CustomerValidator.cs
0
1
0.0%

Totals

Change from base Build 9419d3ccbcdeaa5d5b6f14b253b9203fdff5f6cc:
0.3%

Covered Lines:
689

Relevant Lines:
775

💛  - Coveralls


Set correct component name in the devfile metadata

What type of PR is this?
/kind bug
/kind code-refactoring
What does this PR do / why we need it:

Set the correct component name in the devfile metadata
Add integration tests for it.
Do a little cleanup to remove unused arguments.
Move GetComponentTypeFromMetadata from create_helpers.go to component.go : so that the function can be used in both the files without any cyclic dependencies.

Which issue(s) this PR fixes:
Fixes #4815
PR acceptance criteria:

[x] Unit test

[x] Integration test

[ ] Documentation

[ ] Update changelog

[ ] I have read the test guidelines

How to test changes / Special notes to the reviewer:

odo create java-maven mycomp
Check if mycomp is set in devfile.yaml.
Run odo describe.
Check if mycomp is displayed in Name and Maven in Type.
Run odo list.
Check if mycomp is displayed in Name and Maven in Type.

/test prow/psi-kubernetes-integration-e2e

/test psi-kubernetes-integration-e2e

/retest
Reason -
[must-gather      ] OUT Using must-gather plug-in image: registry.redhat.io/openshift4/ose-must-gather:latest
When opening a support case, bugzilla, or issue please include the following summary data along with any other requested information.
error getting cluster version: Get "https://api.ci-op-s21v700v-d028c.origin-ci-int-aws.dev.rhcloud.com:6443/apis/config.openshift.io/v1/clusterversions/version": dial tcp <IP_ADDRESS>:6443: i/o timeout
ClusterID:
ClusterVersion: Installing "" for <unknown>: <unknown>
error getting cluster operators: Get "https://api.ci-op-s21v700v-d028c.origin-ci-int-aws.dev.rhcloud.com:6443/apis/config.openshift.io/v1/clusteroperators": dial tcp <IP_ADDRESS>:6443: i/o timeout
ClusterOperators:
	clusteroperators are missing

When opening a support case, bugzilla, or issue please include the following summary data along with any other requested information.
error getting cluster version: Get "https://api.ci-op-s21v700v-d028c.origin-ci-int-aws.dev.rhcloud.com:6443/apis/config.openshift.io/v1/clusterversions/version": dial tcp <IP_ADDRESS>:6443: i/o timeout
ClusterID:
ClusterVersion: Installing "" for <unknown>: <unknown>
error getting cluster operators: Get "https://api.ci-op-s21v700v-d028c.origin-ci-int-aws.dev.rhcloud.com:6443/apis/config.openshift.io/v1/clusteroperators": dial tcp <IP_ADDRESS>:6443: i/o timeout
ClusterOperators:
	clusteroperators are missing

/test psi-kubernetes-integration-e2e

/retest

/retest
Reason -
 [ssh:Fedora-32-minikube] • Failure [7.824 seconds]
[ssh:Fedora-32-minikube] odo devfile describe command tests
[ssh:Fedora-32-minikube] /home/fedora/amqp_ci_rcv_odo-minikube-pr-build_PR_4927/iTfKg/repo/tests/integration/devfile/cmd_devfile_describe_test.go:16
[ssh:Fedora-32-minikube]   When executing odo describe
[ssh:Fedora-32-minikube]   /home/fedora/amqp_ci_rcv_odo-minikube-pr-build_PR_4927/iTfKg/repo/tests/integration/devfile/cmd_devfile_describe_test.go:33
[ssh:Fedora-32-minikube]     should describe the component when it is not pushed [It]
[ssh:Fedora-32-minikube]
[ssh:Fedora-32-minikube] [Fail] odo devfile describe command tests When executing odo describe [It] should describe the component when it is not pushed
[ssh:Fedora-32-minikube] /home/fedora/amqp_ci_rcv_odo-minikube-pr-build_PR_4927/iTfKg/repo/tests/integration/devfile/cmd_devfile_describe_test.go:63
[ssh:Fedora-32-minikube]
[ssh:Fedora-32-minikube] Ran 196 of 207 Specs in 1431.846 seconds
[ssh:Fedora-32-minikube] FAIL! -- 195 Passed | 1 Failed | 1 Pending | 10 Skipped
[ssh:Fedora-32-minikube]

Passes locally.

/retest

/approve

While odo describe works as you said it should, odo list doesn't. It shows incorrect value for TYPE column.
$ odo describe
Component Name: mynode-123
Type: nodejs

$ odo list
Devfile Components:
APP     NAME           PROJECT     TYPE           STATE
app     mynode-123                 mynode-123     Not Pushed

Before I review this PR again, have you addressed above or is it going to be done in a different PR?

Before I review this PR again, have you addressed above or is it going to be done in a different PR?

Of course, I have. This comment was the reason why I had to do a lot of rework.

@valaparthvi

I would much rather do the refactoring in a separate PR.

Sure. Works for me. Please open separate issues for the test files that you plan to refactor in follow-up PRs. Also update #4741 like others have done so far.

/retest

/retest-required

My tests are failing because an old image of java-springboot is used, the tests are failing locally as well.
@feloy Any thoughts on fixing this?

My tests are failing because an old image of java-springboot is used, the tests are failing locally as well.
@feloy Any thoughts on fixing this?

Nevermind, I understand why this is happening. The copied devfile contains the old image, which is why it is failing.

/test psi-kubernetes-integration-e2e
reason - perhaps a flake
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_odo/4927/pull-ci-openshift-odo-main-psi-kubernetes-integration-e2e/1434517392939028480


modification of the value in a variable, in the handling of pointers

Context: https://tour.golang.org/moretypes/1
at what time the value of variable j is being modified?
package main
import "fmt"
func main() {
i := 34
j := 1200
//declare a pointer
p := &i
fmt.Println(p, " ", *p, " ", i, " ", &i)

p = &j
fmt.Println(p, " ", *p, " ", j, " ", &j)

*p = i

sum:= *p + j
fmt.Println(*p, "+", j, "=", sum)

}

At this line
*p = i
the variable j got modified
*p  refers to the "value at the address p pointing to"
so after executing the above line indirectly (i is equal to j) because assigning i value to j
the expected output is 34 + 34 = 68


Queryfile input removal

Part of https://github.com/quasar-analytics/quasar/issues/1634
Removing everything from queryfile.Input beside formFile as this will require its own attention

@alissapajer dont merge yet - after cassandra being ni master i need to make some changes in this PR, it will be ready tomorrow

ready for review


There is a 6 second buffer and then suddenly disappears.

Have you read the Tutorials?
yes
Have you read the FAQ and checked for duplicate open issues?
yes
If the question is related to FairPlay, have you read the tutorial?

yes
What version of Shaka Player are you using?
4.7.11
What browser and OS are you using?
window
Please ask your question
Why does the current Buffer go from 6.1234 to 2.9455 in 503ms?

I am making the settings below.

streaming: {
    useNativeHlsOnSafari: true,
    bufferingGoal: 5,
    bufferBehind: 5,
    rebufferingGoal: 4,
    lowLatencyMode: true,
    startAtSegmentBoundary: true,
    liveSync: true,
    liveSyncMaxLatency: 5,
    liveSyncMinLatency: 4,
    liveSyncPlaybackRate: 1.1,
    updateIntervalSeconds: 0.5,
    retryParameters: { baseDelay: 1000, timeout: 5000, maxAttempts: 2 },
  },
  manifest: {
    hls: {
      liveSegmentsDelay: 1.2,
    },
    retryParameters: { baseDelay: 1000, timeout: 5000, maxAttempts: 2 },
  },

I don't know.  Please use the bug template and give us the information we need to reproduce the issue.  Please do not skip or delete any fields of the template.  Thanks!


Fix electron runner on Windows

On Windows, we cannot run the electron binary since it is using a shebang, and those aren't supported 😞
We could use something like cross-spawn or we can use node directly to execute the script.

hey! thanks for the PR!
i jest landed https://github.com/facebook-atom/jest-electron-runner/pull/11 that uses execPath
i'll release a new patch in a few

just published<EMAIL_ADDRESS>

Great, thanks!


random build failures on kirkstone with custom TX2 hardware

We have ported the vc_mipi_camera bits for this to the current meta-tegra kernel and latest kirkstone branch => kirkstone-l4t-r32.7.x
The test device has 2 cameras on the CapableRobots baseboard, where the yocto machine is jetson-xavier-nx-devkit-tx2-nx, and most of the time the demo image bits build fine, except when they don't:
| aarch64-oe4t-linux-gcc-ar -rv egldevice/libnvgldemo.a egldevice/nvgldemo_main.o
| r - egldevice/nvgldemo_main.o
| aarch64-oe4t-linux-gcc-ar -rv egldevice/libnvgldemo.a egldevice/nvgldemo_parse.o
| r - egldevice/nvgldemo_parse.o
| aarch64-oe4t-linux-gcc-ar -rv egldevice/libnvgldemo.a egldevice/nvgldemo_shader.o
| aarch64-oe4t-linux-gcc-ar -rv egldevice/libnvgldemo.a egldevice/nvgldemo_texture.o
| r - egldevice/nvgldemo_shader.o
| aarch64-oe4t-linux-gcc-ar -rv egldevice/libnvgldemo.a egldevice/nvgldemo_socket.o
| r - egldevice/nvgldemo_socket.o
| /home/nerdboy/my_stuff/home/hardware/tegra-demo-distro/build/tmp/work/armv8a_tegra-oe4t-linux/l4t-graphics-demos/32.7.3-20221122092958-r0/recipe-sysroot-native/usr/bin/aarch64-oe4t-linux/../../libexec/aarch64-oe4t-linux/gcc/aarch64-oe4t-linux/11.3.0/ar: egldevice/libnvgldemo.a: error reading nvgldemo_shader.o: file truncated
| r - egldevice/nvgldemo_texture.o
| make[1]: *** [<builtin>: egldevice/libnvgldemo.a(egldevice/nvgldemo_socket.o)] Error 1
| make[1]: *** Waiting for unfinished jobs....
| rm egldevice/nvgldemo_os_posix.o egldevice/nvgldemo_texture.o egldevice/nvgldemo_cqueue.o egldevice/nvgldemo_preswap.o egldevice/nvgldemo_main.o egldevice/nvgldemo_shader.o egldevice/nvgldemo_win_egldevice.o egldevice/nvgldemo_parse.o egldevice/nvgldemo_socket.o egldevice/nvgldemo_math.o
| make[1]: Leaving directory '/home/nerdboy/my_stuff/home/hardware/tegra-demo-distro/build/tmp/work/armv8a_tegra-oe4t-linux/l4t-graphics-demos/32.7.3-20221122092958-r0/l4t-graphics-demos/usr/src/nvidia/graphics_demos/nvgldemo'
| make: *** [Makefile:118: ../nvgldemo/egldevice/libnvgldemo.a] Error 2
| make: *** Waiting for unfinished jobs....
| make: Leaving directory '/home/nerdboy/my_stuff/home/hardware/tegra-demo-distro/build/tmp/work/armv8a_tegra-oe4t-linux/l4t-graphics-demos/32.7.3-20221122092958-r0/l4t-graphics-demos/usr/src/nvidia/graphics_demos/ctree'
| ERROR: oe_runmake failed

Once that ^^ happens no amount of cleaning/rebuiilding seems to help and I have no idea what the root cause is.  Help??

After moving that ^^ build dir out of the way, then doing setup-env and copying local.conf/bblayers.conf to the new/clean build dir, tried building the same image again and it works fine.

@sarnold these are typically the types of errors you see when you run out of memory on your build host in my experience.  Doing a clean on the specific image which is failing typically resolves.

Sorry, i thought that was more clear  - I couldn't clean my way out of that one,  only a fresh build dir helped.

It sounds environmental... what are you using for a build host (OS, CPU count, RAM size) and for storage of your build tree (device type, filesystem type, size/occupied/free)?  Are there any kernel errors logged when you run into the problem?

Build host is intel core-i7 with 8 cpu threads and 32 GB ram plus ~130 GB free (for tegra) on nvme ssd.  I have several build trees for rpi, pine64, rockchip, marvell and I don't normally have issues; most of it is "bare" user account, but xilinx needs to build in a VM running bionic as project is stuck on 2020.x release of petalinux.
$ free
               total        used        free      shared  buff/cache   available
Mem:        32732296     4214848     2811928<PHONE_NUMBER>0    28041948
Swap:        4194300       41472     4152828

and
$ df -h
Filesystem                                       Size  Used Avail Use% Mounted on
devtmpfs                                          10M     0   10M   0% /dev
tmpfs                                             16G   68K   16G   1% /dev/shm
tmpfs                                             16G  708K   16G   1% /run
/dev/nvme0n1p3                                   464G  345G   96G  79% /
cgroup_root                                       10M     0   10M   0% /sys/fs/cgroup
/dev/nvme0n1p1                                   973M  383M  536M  42% /boot
/dev/sda1                                        110G  612M  104G   1% /public
tmpfs                                            3.2G  5.7M  3.2G   1% /run/user/1000

The above is post-error on the graphics demos but still building rust-native.

The RAM and free disk space should be enough, I think, although more free disk space would probably be safer. No kernel messages about either OOM or filesystem errors on whichever drive you're running the build from?  Does the filesystem ever hit usage of 90% or more?
The Rust compiler build is pretty resource-intensive, and  CUDA application builds are, too.  I wouldn't expect the graphics demos to be that bad, though - no CUDA there, just EGL.

Hey @sarnold
Any updates about this issue ?

Sorry, got busy with xilinx again and we already gave the tegra customer a workable meta layer for his camera stuff.  I suspect the cause of our build issue was most likely too much distro feature hacking, as I ended up going with less of that and a really light openbox config which seemed stable enough for dev work.

I will close this ticket. You can reopen new one if you have any issue.