[Bug]: Syncing Dashboard Component stays "On Hold" despite client syncing

Contact Details

Describe the bug!
Client Status Sync stays on "Hold" in the Sync Component, despite logs looking good.
Problem spotted with Nimbus by one of our Discord users named Luc1d
Attach a Screenshot!

Expected Behaviour
The sync component works as intended and shows the current sync status
Help us reproduce your bug!

Install A Node
Go to Control Page
Check Sync Dashboard Component
Check Logs of Clients syncing

Launcher Version
rc.18.1
Desktop OS
MacOS
Node Server OS
Ubuntu 22.04
Affected Service
Nimbus
Relevant log output
-------

Acknowledgment

[X] I looked through the existing bugs of this project

This has nothing to do with Nimbus. If the SyncStatus Widget shows "on hold" then the lowerslot and higherslot are both zero. That means we do not have any data from Prometheus. I spotted this behaviour also when i upgraded my Teku testing node but did not give much attention to it since i usually impair my nodes heavily during development.

Futher versions from Nimbus report stats properly to Prometheus. For execution clients a workaround was possible, therefore they got the separate issue #1274 which is fixed with #1275. Consensus clients needs to report their stats properly - there is no workaround possible.


Request Money - Errors happen when sending money requests back and forth between users

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

A send money request to B
Then B send money request back to A (with same amount - maybe)
Repeat step #1 and #2 few times

Expected Result:
The requests should be send successfully
Actual Result:
There are some errors happens (view more details in thread)
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: n/a
Reproducible in production?: n/a
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/947d9027-0988-4bb6-a701-89b4d024c6bf
Expensify/Expensify Issue URL:
Issue reported by: @tranvantoan-qn
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686888687225899
View all open jobs on GitHub

It happens frequently on my side. The main difference between my account and @kbecciv's is the currency. My currency is VNĐ. When I change my currency to something other than USD (by changing my IP address), I also see other issues happen.
So it may have something to do with currencies. Let's try changing it and then reproduce the issue.

@mountiny @luacmartins Do we have anything like a milestone for clean up issues related to Manual Requests?

I've just been adding them to the main tracking issue and the w3 milestone

there is the wave3 project which is handy, added it there

Hm I'm having a hard time reproducing. Are we adding this to the milestone because you reproduced @mountiny ?

Nope i havent reporduced, havent tried. if you cannot reproduce we can ask qa to check and close if no luck

Ah got it! QA had issues reproducing too initially. Hmm.

@tranvantoan-qn can you help me by expanding the steps you took? let's take this back to the slack thread to nail down the reproduction steps.

@michaelhaxhiu @mountiny
After hours of breaking down the issue step-by-step and creating dozens of new test accounts, I was finally able to figure out the clear steps that caused it to happen (though they don't look the same as the original steps but the output is 100% the same)

Login 2 fresh accounts A and B (not required but fewer data will make the flow easier)
From Account A:
2.1. Send Money request to B with amount = XXX (see video at 0:10)
2.2. On LHN: Click on the chat that says B owes XXX - the ọne with Green Dot (this may be optional) - see video at 0:36
2.3. Logout and login to account A again
2.4. On LHN: Click on the chat that says B owes XXX - the ọne with Green Dot again - (see video at 1:21)
From Account B:
3.1.  Click on the chat that says B owes XXX (see video at 1:31)
3.2. Click the I'll settle up elsewhere button on the header
From Account A: Make another Money request to B with the same amount XXX (see video at 1:50)

Error will appears

Thanks! @michaelhaxhiu are you able to reproduce this with these set of steps?


alternative memory analysis tool

Is your feature request related to a problem? Please describe.
LIme is no longer actively maintained.
Describe the feature you'd like
The main project for memory extraction in linux is no longer actively maintained. Consider an alternative
Additional context
Here is a list of potential candidates: https://github.com/digitalisx/awesome-memory-forensics
https://github.com/504ensicsLabs/LiME?tab=readme-ov-file#project-archived

Hi @slmagus ,
Thanks for creating this issue. Looks like you are right that LiME is a archived project now. We will take a look at this. Thanks!


Problem with the source exclude and include with elasticsearch 5.x

In the class "io.searchbox.core.Search" there is 2 lines to include and exclude fields that aren't compatible anymore with elasticsearch 5, those attributes are deprecated:
We need to replace those 2 lines:
addPatternListToSource(sourceObject, "include", includePatternList);
addPatternListToSource(sourceObject, "exclude", excludePatternList);
with
addPatternListToSource(sourceObject, "includes", includePatternList);
addPatternListToSource(sourceObject, "excludes", excludePatternList);
Not sure how you guys handle compatibility between newer and older versions of ES, we should do something to keep backward compatibility.

Hi Rigregs,
I think we shoud not handle compatibility, we shoud lead users to stick with 2.x version of Jest and fix critical issues over it if any.

So you guys don't plan to support elasticsearch 5.x for now?

No, I mean yes we will support, currently master is at 5.x (not completely operational though). I meant next release will be supporting 5.x without being (now willingly, may work) 2.x compatible. If you need 2.x you need to go with Jest 2.x etc.

That's great, for the moment I create my own version of the search class and change the code to be ES 5.x compatible for the exclude fields, looking forward to see that release ;)


Improve performance of raw tag editor

The detection whether _entityIDs  includes a relation is performed many times inside a loop. Instead this should be done only once (lazy).
Besides I changed the name of the variable to includesRelation because the old name (isRelation) could be misunderstood.

Can we just always use the relation doc lookup for the type= key?  We probably don't need to actually check whether the user has selected a relation at all.
It seems like using type for anything other than the relation type is deprecated:
https://wiki.openstreetmap.org/wiki/Key:type
So it's not like looking up type=someval will return anything meaningful if the user has selected some feature that is not a relation but somehow still has a type tag.

Using type was already part of the old logic which I didn't change.
I can't really answer whether the type check is OK or whether it should work differently or whether it should be dropped altogether. But from a pure UI perspective, I think it's a little bit strange that the tag reference works in any way differently if one of my selected objects happens to be a relation.

I investigated a little bit more:

The type check is very old (> 5 years), but it used to be applied to a single entity. See d8e627b for instance.
Years later (on 2020-01-17) the whole tag editor was change to support multiple selected entities. See eda51f6.

According to taginfo there are still 102.108 nodes (0.06%) and 92.926 ways (0.01%) having the type tag.

The type check basically decides whether uiTagReference is called with { rtype: d.value } or with { key: d.key, value: d.value }. So I checked the code to see what difference this does.
In the end rtype is used by getEntity of modules/services/osm_wikibase.js to decide whether to use:

A link describing the relation type like https://wiki.openstreetmap.org/wiki/Relation:multipolygon
Or a link describing the tag's value like https://wiki.openstreetmap.org/wiki/Tag:highway=motorway
Or - if the value link doesn't exist - a link describing the tag itself like https://wiki.openstreetmap.org/wiki/Tag:highway

So I think this whole logic should be moved to osm_wikibase.js:

uiTagReference should always be called with { key: d.key, value: d.value }.
osm_wikibase.js (and uiTagReference which acts as proxy) should remove the option rtype.
osm_wikibase.js should use the following logic:

If key is 'type': Check whether the Relation:${value} page exists
If not: Check whether the Tag:${key}=${value} page exists
If not: Use the Tag:${key} page

Should I change this PR accordingly?

Your suggestion looks good to me 👍

Done.

Removed the last doc change since all parameters are optional.

@til-schneider Thank you! Definitely nice to simplify this. I was able to make a few more tweaks based on your changes.


Added sigaction_is_default(), sigaction_is_ignore(), and sigaction_current() functions

What does this PR do
Provide safe mechanisms to determine whether a signal's action is the default or ignore.
This covers the majority of real-world calls to sigaction() with a NULL action without needing any unsafe code.
Provide an unsafe way to query the currently installed sigaction.
The decision to add sigaction_current() instead of just exposing the (new) sigaction_inner() function was to avoid any confusion over the semantics of passing in a None sigaction argument (eg: someone thinking that it meant remove or reset the action).
This closes #2172
Checklist:

[x] I have read CONTRIBUTING.md
[x] I have written necessary tests and rustdoc comments
[x] A change log has been added if this PR modifies nix's API

I've also added a (loosely) related/complementary proposal to add safe functions to ignore and restore signals' actions in #2191.


Add full update algorithm

This PR adds the core part of the fast full update (arXiv 1503.05345) algorithm. Compared to simple update, the environment around a bond to be updated is more accurately represented by the CTM tensors, instead of diagonal weight matrices.
Limitations:

The implementation assumes square lattice geometry.
As in simple update, I made some requirements on whether certain virtual spaces of iPEPS tensors are dual spaces.
The current implementation can currently only calculate models with nearest neighbor interaction only. Support for next nearest neighbor terms (see arXiv 1711.07584) will not be implemented in near future.

Things to do before merging:

[ ] Find a robust criterion to change the evolution time step and determine convergence. Currently, the FU stops when the energy is no longer decreasing. However, I feel that this may prevent the algorithm to evolve out from a local minimum. It may be better if some singular value spectrum can be used to determine convergence (as in CTMRG and simple update).
[ ] Add support for bipartite iPEPS (currently for 2 x 2 unit cell, the algorithm cannot keep the bipartite structure).
[ ] Add a non-trivial test or example.
[ ] Improve docstring.
[ ] Use Julia's more advanced logging system.

It might already be possible to achieve something like this by simply restricting the number of iterations in the CTMRG contraction. This is definitely not fully equivalent, so I agree that it would be beneficial to have an abstraction to allow different algorithms there.


Patched to compile on Linux + GCC 6.2.1 20160830

Hi,
I've done two commits. One to make the files compile (most problems were related to including cmath headers) and another to enable successful linking.
I could make a pull request but I think I've made some bad changes too.
Here's my fork:
https://github.com/forcecore/Coloquinte

Hi,
Thanks for your contribution. Sorry, I've not been active in a while. I'll check with newer GCC and fix this - or if you have a pull request I'll be happy too. And I think I can remove the dependency to Lemon.
Gabriel


allow more zoom

sometimes, it would help to be able to zoom in more to see details of bugs, but "+" is disabled at some depth. Would it be possible to increase it by at least 1-2 zoom levels?

I have increased the Zoom level by 3 levels. But keep in mind, that the default Tile Source does not load new Tiles at this Zoom level. You'll have to zoom out for the Tiles to start loading


Add a page for MI Copilot

Description
Currently, there is no dedicated page to provide an overview of MI Copilot, its capabilities, and the steps to sign up. Created this issue to track this.
Version
No response

The MI Copilot page is now live: https://mi.docs.wso2.com/en/latest/develop/mi-for-vscode/mi-copilot/


Spatial correlation

This computes spatial correlations, from code suggested in this PR.
@licode let me know if it looks good, thanks!

LGTM.

thanks! :-)


Pub-Sub Architecture

Investigate pubsub architecture for chat messaging

Conclusions of PubSubTest.scala:

This file uses the akka.actor version of imports (original uses akka.actor.typed)
The DistributedPubSub library works as intended, can be used for the chat app
Ensure that code imported into main code is of akka.actor.typed (a bit different code)
Idea is to use the Receptionist to spawn a DistributedPubSub mediator for each chat room, User actors will subscribe to each mediator to access the chat channels

Pub-Sub cannot be used. Library not allowed.


fix(chart): Time Column configuration doesn't accept Custom SQL

SUMMARY
Superset allows you to add custom SQL to the Time Column configuration on Charts through the UI.
However, that feature is not implemented in the API, and instead throws a wrongly formatted request error.
This PR adds support for custom SQL to the time column configuration.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before:
https://user-images.githubusercontent.com/17252075/172587258-c3ad6292-610c-4990-a479-fd69f90e6742.mov
After:
https://user-images.githubusercontent.com/17252075/172587324-4a284025-42a5-4808-bf1e-38074dde018f.mov
TESTING INSTRUCTIONS

Create a new Chart using the Vehicle Sales Dataset.
On the METRIC configuration, set COUNT(*).
On the TIME COLUMN configuration, switch to the CUSTOM SQL tab and set date_trunc('week', order_date)::date - 1.
Remove any TIME GRAIN if set.
Click on RUN.

The query should run and return data properly.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

@diegomedina248 @rusackas the granularity signature in the function get_sqla_query is useless when the feature flag GENERIC_CHART_AXES has turned on. currently, all column fields(general columns and xaxis columns)  are using the columns field in the get_sqla_query.


Update Link and InlineLink styles

Summary
Updates the Link and InlineLink components to conform to the designs spec'd in the 2023 refactor.
List of notable changes:

Updated link colors
Updated link focus styles

What should reviewers focus on?
Does it match what's in Figma
Steps to test:
Go to the Link and InlineLink stories in Storybook
Supporting resources (related issues, external links, etc):

Figma mocks
Primer Brand branch with Figma component updates
https://github.com/github/primer/issues/2497

Contributor checklist:

[ ] All new and existing CI checks pass
[ ] Tests prove that the feature works and covers both happy and unhappy paths
[ ] Any drop in coverage, breaking changes or regressions have been documented above
[ ] New visual snapshots have been generated / updated for any UI changes
[ ] All developer debugging and non-functional logging has been removed
[ ] Related issues have been referenced in the PR description

Reviewer checklist:

[ ] Check that pull request and proposed changes adhere to our contribution guidelines and code of conduct
[ ] Check that tests prove the feature works and covers both happy and unhappy paths
[ ] Check that there aren't other open Pull Requests for the same update/change

Screenshots:

Please try to provide before and after screenshots or videos

 Before  After

https://github.com/primer/brand/assets/2313998/a6f903c4-721d-4f32-9b02-20c50f40aff7
https://github.com/primer/brand/assets/2313998/c57c47bd-13ae-46e9-81a6-327f43ad5395

https://github.com/primer/brand/assets/2313998/d10cdfc5-068e-45f5-9dfb-e39d24119131
https://github.com/primer/brand/assets/2313998/2c1d7845-d02a-4d2f-b048-1c025f67338a

I'm a little confused why the visual regression testing didn't identify any changes 🤔

I'm a little confused why the visual regression testing didn't identify any changes 🤔

Weird 🤔. I added the "Update snapshots" just in case 🤞

question, is the glow on focus being added intentionally? 👀
could we add the border-radius also in there?

Yes, that’s what was in the mocks. I can open a PR to add a border radius
if the other designers are on board with that.
On Thu, Aug 3, 2023 at 2:56 PM Jesus Sandrea @.***>
wrote:

question, is the glow on focus being added intentionally? 👀
could we add the border-radius also in there?
—
Reply to this email directly, view it on GitHub
https://github.com/primer/brand/pull/368#issuecomment-1664476757, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AARU6DUIYTA7XAZBODJT3MDXTPX7DANCNFSM6AAAAAA3B3TBAI
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Add test cases for cld

Codecov Report

Merging #6 into master will decrease coverage by 0.64%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master       #6      +/-   ##
==========================================
- Coverage   21.53%   20.89%   -0.65%
==========================================
  Files           8        8
  Lines          65       67       +2
  Branches        9        9
==========================================
  Hits           14       14
- Misses         51       53       +2

Impacted Files
Coverage Δ

src/cldFactory.ts
0% <ø> (ø)
:arrow_up:

src/index.ts
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Add support for Python 3.12

Hey Carl =) I'm adding support and releasing a new version! It should be ready in the next hours...


Switch to use stdlib for simple computation

When writing the metrics test, the wrong package was imported. Use rand package from standard library for simple match computation.

Codecov Report

Merging #26 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #26   +/-   ##
======================================
  Coverage    84.1%   84.1%
======================================
  Files           3       3
  Lines         365     365
======================================
  Hits          307     307
  Misses         34      34
  Partials       24      24

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 d58457a...7c15d6b. Read the comment docs.


Add remote ticket option: Originally by Aris Nivorlis

New PR to avoid merge conflict caused by pre-commit.ci
Original changes #653, by @anivorlis

Oh the conflict is gone, no need for this


[occm] Support multiple network names

What this PR does / why we need it:
In some intricate network designs, it is possible to have multiple networks on different hosts. This PR allows the user to specify multiple network names that may be considered public or private on cluster's nodes.
Special notes for reviewers:
I've tried to maintain complete backward compatibility. Due to the way gcfg works, it is possible to specify arrays via repeated use of the same key.
Release note:

[openstack-cloud-controller-manager] Support multiple network names for config options `internal-network-name` and `public-network-name`.

/ok-to-test

@lingxiankong, is that ^ something I can fix?

/test pull-cloud-provider-openstack-check

The pull-cloud-provider-openstack-check job issue should be fixed, if it fails again, please rebase the code.

/lgtm

/approve


Use berks, refactor the things

Remove all cookbooks other than habitat_workstation
Use the Berkshelf (Luke)
Rakefile revamp

add ami:build command
builds now log and AMIs are added to results.yml
add ami:deploy command

generates and deploys a CloudFormation tempalte
list:ips lists the CFN Outputs for IP addresses

Signed-off-by: Seth Thomas<EMAIL_ADDRESS>

Oh and one template for each platform, if you don't want habitat installed setting hab_version=none does the trick.


icons array is not recognized as array

Hey,
found a bug:
My icons array
 "icons": [
        {
            "src": "require(./icons/mt/apple-touch-icon-192x192.png)",
            "sizes": "192x192",
            "type": "image/png"
        },
        {
            "src": "require(./icons/mt/apple-touch-icon-512x512.png)",
            "sizes": "512x512",
            "type": "image/png"
        }
    ],

gets transformed into a object
"icons":{
    "0":{
        "src":"/images/src/common/components/app/icons/mt/apple-touch-icon-192x192.png",
        "sizes":"192x192",
        "type":"image/png"
     },
    "1":{
        "src":"/images/src/common/components/app/icons/mt/apple-touch-icon-512x512.png",
        "sizes":"512x512",
        "type":"image/png"
    }
}

in version v0.2.0.
The version v0.1.2 works fine.

@McMomo thanks for report, should be fixed in 0.3.0


add 'proxy_server' param to jenkins::slave class

The jenkins and jenkins::slave classes should be fully decoupled so
that the jenkins class is not required to be in the catalog for a
"slave only" node.

Makes sense..


Export callback and replaced values

Hello,
i have custom export callback and i want to export as is data from datagrid. When i am using custom export callback i am able get data as is from database without applied renders, replacements, etc..
Is there any way how to get datagrid data with "translated" data?
Or i have to again mannualy replace values in export?

@BigOHenry I think you can define columns separately and then use them in the both datagrid and the callback:
$column = new ColumnText($grid, 'name', 'name', 'Name');

$grid->addColumn($column);

$grid->addExportCallback(..)->setColumns([setColumns]);

But this is not usable right now. Method DataGrid::addColumn() is protected. Also, the notation new ColumnText($grid, 'name', 'name', 'Name') is now really stupid, it would be cool to refactor this code a bit and make it more simple.


[0.12.0] Error parsing query when running multiple queries

I added a new graph in Grafana (2.6.0) with two queries:
SELECT mean("CPU") FROM "DEVICE_2_LIVE" WHERE $timeFilter GROUP BY time($interval)
SELECT mean("MemoryUsage") FROM "DEVICE_2_LIVE" WHERE $timeFilter GROUP BY time($interval)
InfluxDB response:
{
"error": "error parsing query: found SELECT, expected ; at line 2, char 1",
"message": "error parsing query: found SELECT, expected ; at line 2, char 1"
}
If I change the query to:
SELECT mean("CPU") FROM "DEVICE_2_LIVE" WHERE $timeFilter GROUP BY time($interval);
SELECT mean("MemoryUsage") FROM "DEVICE_2_LIVE" WHERE $timeFilter GROUP BY time($interval)
Only the first value is retrieved from database.
Here are some screenshots:

This issue appeared after I updated the InfluxDB to 0.12.0. If I use a single query the graph is displayed. I also tested with Grafana 3.0.0 beta 2 and it's also reproducible.

:+1:

:+1:

Looks like it's connected with that change: https://github.com/influxdata/influxdb/pull/6004

So the break on influx's side was on purpose according to #6004

is there any bug fix for this?

IMHO it's an issue on grafana side not on influxdb side.

:+1:

Closing this since this comment lends me to believe that this is an issue on Grafana's side: https://github.com/influxdata/influxdb/issues/5728#issuecomment-206499641
If anybody has more information about this bug that differs from what is mentioned in that comment thread, please reopen with more information so we can try to reproduce the problem. Thanks.

it seem not only support grafana but also the admin console of influxdb

@emanzx unfortunately I'm not able to reproduce that on my machine. When I use a semi-colon, I get two results. Can you run the same query using the influx binary and see if the result is different?

I try to run on the influx cli.. Seem like it produce two result. But the
admin web interface still not produce two result. I have compile the latest
source. Its still the same, by the way I manage to hack grafana to works by
patching some code and edit angular.js file based on what I found on
google.
On Saturday, April 9, 2016, Jonathan A. Sternberg<EMAIL_ADDRESS>wrote:

@emanzx https://github.com/emanzx unfortunately I'm not able to
reproduce that on my machine. When I use a semi-colon, I get two results.
Can you run the same query using the influx binary and see if the result
is different?
—
You are receiving this because you were mentioned.
 Don’t
be trapped by dogma – which is living with the results of other people’s
thinking. Don’t let the noise of other’s opinions drown out your own inner
voice. And most important, have the courage to follow your heart and
intuition. They somehow already know what you truly want to become.
Everything else is secondary.” - Steve Jobs’ Stanford Commencement Address
http://www.youtube.com/watch?v=UF8uR6Z6KLc
Muhammad al-iman Bin Mohd Zain
Student of Horticultural Sciences
Faculty of Agriculture
Universiti Putra Malaysia
Serdang, Selangor.
013-2823637

Hi,
same issue since I updated influxdb too.
This is why I think the problem is link to influxdb and not grafana.
To have more than one graph on the same panel, I need to delete the 2 others queries and add in the first query 2 more "field" and select the name field.
But after, I can not rename the name fiel with field measurement using "ALIAS BY"
My goal is to have CPU usage System, User, IO wait on the same panel and with correct table legend and not for example "cpu.mean", "cpu.mean_1", "cpu_mean_2"
Regards,

Same here.

It's fixed in Grafana3beta3, see here
https://github.com/grafana/grafana/issues/4533#issuecomment-208962918

@mnietz I know that, but what about grafan 2.6 (debian package) ?
Thank you.

Heyho,
we too need this fixed for grafana 2.6. Any plans?


Container falling with code 100

Unable to find image 'mongodb:latest' locally
docker: Error response from daemon: pull access denied for mongodb, repository does not exist or may require 'docker login'.

This thread might also be helpful https://github.com/docker-library/mongo/issues/123

Closing since this isn't an issue we can alleviate in the image
You could also try asking over at the Docker Community Forums, Docker Community Slack, or Stack Overflow


HAL IoPin trait implementation

IoPin trait is available in embedded-hal 0.2.6 and in 1.0.0 pre release versions.
I think it will be available in HAL release.

Thanks for submitting this PR! I won't have a chance to check this out until later this week, but from a cursory glance everything seems to be in order, and I see no reason not to add support for IoPin.


Use extended ISO format for timestamp for millisecond precision

There are three forks which are just adding millisecond precision. I'm about to do the same.

Thank you so much for your contribution, and sorry for the delay 👍


Issues installing with conda-forge but not pip

When installing cellrank/cellrank2 using conda-forge, even following the directions from your repository with:
conda install -c conda-forge cellrank

I get an ImportError .... : undefined symbol: H5Pget_fapl_direct: error when trying import cellrank as cr in my Jupyter notebook.
However, if I install everything in pip, there's no issues at all.
Thanks!

Sorry for spotting this only now, @jjia1. Can you please check with the latest versions, and if the problem persists, open an issue on the CellRank repo?


Triton Matrix Multiplication example invalid results (return zeros) on Volta

The Triton Matrix Multiplication example kernel (https://triton-lang.org/main/_downloads/d5fee5b55a64e47f1b5724ec39adf171/03-matrix-multiplication.py, with the non-existent HIP specific primitives removed: https://pastebin.com/GxeharnC) returns zeros on Volta GPUs starting from Triton 2.2. The same kernel works perfectly on A series GPUs on the same machine. It also works on Volta with Triton 2.1 (after replacing accumulator = tl.dot(..., accumulator) with accumulator += tl.dot(...)).
The bug only happens with float16. Float32 works well.

Hi @RobertCsordas thank you for the update regarding dtype, this is very helpful, let me check what is going on with float16 on Volta.
Regarding Triton version PyTorch indeed pins the version for the compatibility reasons, but if there is a problem that was fixed in upstream Triton it's very easy to update the pin

also find the same problem,.
my env is cuda11.6, triton 2.3, torch2.3.1, V100GPU

I simplified the matmul code a bit (removed leaky relu) and left just one config to guarantee equivalence, and dumped the PTX with the working 2.1 and the broken 2.2 Triton. Maybe this can help with debugging. Code: https://pastebin.com/S6QyVtxM
Tirton 2.1 ptx (working): https://pastebin.com/6E0wiVbb
Triton 2.2 ptx (broken): https://pastebin.com/XMNJgZYB
I don't speak PTX, but to me it look like the Triton 2.2 PTX is completely missing the code that should call the tensor cores (the 2.1 PTX has a bunch of mma.sync.aligned.m8n8k4 instructions, while the 2.2 one has 0). The invalid 2.2 code is also significantly shorter.

also find the same problem,. my env is cuda11.6, triton 2.3, torch2.3.1, V100GPU

Download the source from https://github.com/triton-lang/triton, check out the right version (e.g git checkout 'release/2.3.x'), find the file called MMAv1.cpp (the location varies with the version), find function convertMMA884, find the line
unsigned numN = mmaLayout.getMMAv1NumOuter(BShape, ALayout.getOpIdx());
and change it to
unsigned numN = mmaLayout.getMMAv1NumOuter(BShape, BLayout.getOpIdx());
Then build the whole thing with pip3 wheel -e python, install with ```pip3 install``, and it will work just fine!


Add shadow DOM method attachShadow()

I could not find the shadow DOM method .attachShadow().
I was watching a video mentioning that Safari 10 supported web components, but my old example using method .createShadowRoot() didn't work in Safari 10. ;-(
https://www.w3.org/TR/shadow-dom/#interface-shadowroot
Thanks for a great website! ;-)

Covered by https://caniuse.com/#feat=shadowdomv1, have added attachShadow as keyword.

attachShadow should fall under http://caniuse.com/#feat=shadowdomv1


refactor: replace all Range with TSNode as much as possible

The Range type should only be used internally. To leverage more upstream API, we should convert it into a TSNode as much as possible.

@clason we could continue our discussion in https://github.com/nvim-treesitter/nvim-treesitter-textobjects/pull/672#issuecomment-2300006562 here.

Some textobjects need the make-range directive to be defined, and then we read them in metadata, so it's impossible to convert these Range into TSNode. Luckily there is already https://github.com/nvim-treesitter/nvim-treesitter-textobjects/pull/612 which attempts to remove usages of this directive. @ ribru17 Is my understanding of this PR correct?

Pretty much, except I think there was a discussion to keep the predicate definition (although now unneeded) for backwards compatibility with user queries

Also I haven't done a thorough review, but is this a fully safe change? Sometimes metadata.range is needed over node:range() because the latter doesn't account for range changes from something like #offset!

I think we always have to check the metadata; the question is just when (do we precompute that or not); that  is the same as for any other query.
The difference here is that the original code uses the "metadata" ranges as primary objects, which could come from nodes or from #make-range!. So if the latter remains supported, we can't switch to a node-centric model. And if we drop support for it, the predicate is useless, and keeping it defined (but not working) would be a worse user experience than removing it (and telling users that relied on it for non-textobjects usage to just copy the old code in their config or plugin).
So the signs are starting to point to a full breaking rewrite on main and freezing master.

The difference here is that the original code uses the "metadata" ranges as primary objects,

Honestly, it is a rather complicated situation. It uses ranges from TSNode primarily, and stores the range from metadata. the range in metadata is a Range4, so only when functions need a Range4(and the range in metadata exists), the range in metadata will be returned, otherwise it will always use the range from TSNode. This part of the code should be a patch added later.
So If #make-range! could be fully removed, #offset! would not be a big problem. Because there are only 15 usages of #offset! and all of them are used to exclude or include some chars, like parenthesis or spaces. This means we still could use TSNode internally instead of Range because these chars should not have an impact on sorting or comparing them.

So the signs are starting to point to a full breaking rewrite on main and freezing master.

Indeed. At least https://github.com/nvim-treesitter/nvim-treesitter-textobjects/pull/612 must be merged before we move on.

Brief summary, three sources of range:

From TSNode:range()
From metadata[capture_id].range, which is created by #offset!, could be treated as modified TSNode:range()
From #make-range!, no relevant TSNode object.

The first two sources could be handled if we use TSNode, but the last one does not.

Because there are only 15 usages of #offset! and all of them are used to exclude or include some chars, like parenthesis or spaces.

In our queries. Experience has taught me the hard way that user configs (and third-party plugins) can be full of all kinds of stuff...

Since the main branch has already broken user configurations, it wouldn't be a particularly big issue if it continues to break user queries, lol.
However, one point I want to discuss is whether, if #make-range! is removed, we can still transition from Range to TSNode while preserving all existing features. The current discussion leads me to believe that this is possible.

Since the main branch has already broken user configurations, it wouldn't be a particularly big issue if it continues to break user queries, lol.

Well, that's not the right way of looking at this. Right now, main is a new plugin that users can but need not use. The breakage will happen when we freeze master and make main the default branch, which is what we are talking about doing.

Yes, that might be a joke that isn't funny, queries could not be synced between two branches after that.
But if we are certain about making this change, we could first remove #make-range in the master branch. This will likely only require changes to the query, because after this, they will become TSNode, and the code on the master branch will still be able to handle them.

But if we are certain about making this change, we could first remove #make-range in the master branch. This will likely only require changes to the query, because after this, they will become TSNode, and the code on the master branch will still be able to handle them.

That would also get quick feedback on outside use of #make-range!. But I'm also OK with making the switch early, but that requires adding some mapping helpers to reduce the unacceptable setup boilerplate  on main (which is the only thing missing before we could declare it as an "early access" replacement for master).

@clason Could you please take a look at e83e3ebed7c82d01ab97f612d3cab2c26e5032bf? Previously, we were using #make-range!, so the corresponding range didn’t have a capture, I think this is why we used iter_matches. However, https://github.com/nvim-treesitter/nvim-treesitter-textobjects/pull/612 removed #make-range!, switching to iter_captures should be safe since now a capture, which is a TSNode, should correspond to the text object we need. I haven’t maintained the queries in this repository, so I’m not 100% sure.

Looks good to me; if this is incorrect, it should fail pretty badly (easy to manually test with one of the quantified captures here).
@ribru17 ?

Oh, I realized there is indeed an issue with this change regarding quantified captures. My previous manual tests were too simple, sorry about that.
Quantified captures don’t combine multiple nodes into a single node; instead, they match these nodes separately while keeping them within the same pattern. Therefore, we need to use iter_matches to handle them.


test: temporarily reduce the sync committee participation limit for sim tests

Motivation
Make the sim tests run more stable.
Description
Related to https://github.com/ChainSafe/lodestar/issues/6432, can't easily identified what's wrong in sync committee participation. Until we fix that issue following configuration will help to keep the sim tests pass.
Steps to test or reproduce

Run sim tests.

Not ideal but better than having sim tests constantly fail

The reference issue with logs are mentioned in the PR. We need to debug and fix the issue separately.
For reference this issue is not new and I observed this behavior many times earlier as well. But in multi_fork test because we have 5 nodes, so low participation for 1 or 2 nodes in few slot does not reduce the epoch participation below 90%. In multi-client test we have only 2 nodes, so why this impact a lot in this test.

But in multi_fork test because we have 5 nodes, so low participation for 1 or 2 nodes in few slot does not reduce the epoch participation below 90%. In multi-client test we have only 2 nodes, so why this impact a lot in this test.

Maybe the runner is just overloaded, and some nodes are resource starved?


IN Cloud Cloud Server

i build this in cloud server.
when i npm start.
it shows as picture.
but it doesn't work.
btw,my cloud server ip doesn't work too

What happens when you try to open the link?

Getting same problem....everything works and runs well but when webcam starts it's not detecting any object

Are there any errors or warnings in the web inspector?

Closing due to inactivity


Updated various elements of Substreams docs

Each header is a general comment that might require further discussions
Prerequisites
prerequisites: this page says “myriad technologies”.. there’s no benefit in having multiple techs, it’s rather scary. Let’s say “uses a few technologies”, and highlight ease of use.
Something like: “Substreams leverages powerful technologies, including:”
the phrase “Substreams can be used by blockchain, subgraph, Rust, JavaScript, Python, and other types of developers.” doesn’t belong there.. we’re talking pre-requisites, not personas.
One would expect instructions in such a page, not just a bulletpoint list of named techs. A bullet-point list of techs might belong to the Substreams overview in the first sections. The “Dependency Installation” already gives those instructions. So there’s nothing left for that page to exist.  I suggest just moving the bullet-point list in “What is Substreams”, under a heading like “Substreams leverages powerful technologies”, and note something about these techs being mature, well documented and widely deployed.
Homepage
Arriving at the home page, I expect to find a clear, concise definition of what Substreams is. Perhaps swapping the first two sentences would do it. It’s more important to understand what it is, than who developed the technology.
The README.md https://github.com/streamingfast/substreams has a good 3-liner intro that we should use for the docs.
I’d also very much like to find here, right after Welcome, somethign exxttreeemly simple that can help bootstrap the mental model for Substreams. Something that includes a 3-lines mapper module, the presence of a Sink, a blockchain node. Something like the diagram in “Conceptual Diagram”.. It makes sense that it be up there.. so people can know where this whole thing fits.
We need at least the first paragraph of https://substreams.streamingfast.io/concept-and-fundamentals/definition on the first page.
Navigation
I’d love to have just two things under “Getting Started”:

Installing the CLI
Quick Start

The “Start Streaming” page has things that belong to a “Basics” section (which exists in the “Chain-agnostic Tutorial”  (to become “Quick Start”).
I shrank the “Start Streaming” section, now it can become the first section in the Quick Start guide.. which makes sense. The fastest way to get started, is to just try it.. and then, write your very first thing.
Right now one needs to navigate and click a lot.. lots of pages, with similar sounding names: “Substreams” (first page), “What is Substreams” (hoped to find that on first page), “Conceptual Diagram” (and that’s not in What is Substreams?), “Fundamentals” (the first three pages didn’t cover the fundamentals?).
Fundamentals could be named “How it works”, as it details some of the lower-level internals. People will want to get more into details in a “How it works” page.. and know what to expect. And we’ll know what to put there. That page can be longer, provided the headings are meaningful. For example “Key Steps” isn’t a meaningful navigation element. Same with “Working with Substreams Fundamentals” .. (working with the page? ooh.. sort of How to work with substreams fundamentals”).
Let's rename "Using the CLI” page -> “CLI Reference”

“Using the CLI” reads more like a tutorial-esque thing.
But this section is about Reference & Specs. More of a declarative format and extensive list-styles.

Let's close this. @abourget will review and will write down in a new issue what he would like to see modified still.


Add survey to coqbot response

@Zimmi48 @achlipala Does the wording in early-feedback.md look good to you?
@Zimmi48 Could you make @coqbot stick the PR/Issue number in the file coqbot.issue-number?

The message wording looks good to me.

See coq/bot#168. If you could review it, that would be great!


fix env vars in assets deployment chart

@theoriginmm please take a look at this

@spiridonovfed
Please, check MINIO_ACCESS_KEY in other microservices

@spiridonovfed
Merging this branch, because we need this fix in env
Please, ensure that S3 fix didn't affect other microservices


Warning if volume leakage is set to value > 1900

The SYR App allows to configure volume leakage values up to 9000 liters.
In this case Wamo repeatedly shows a warning message:

| warn | State value to set for "wamo.0.Device.Profiles.4.PV4" has value "9000" greater than max "1900"
-- | -- | --

Fixed in version v0.4.0


Automatic update of NuGet.Protocol to 4.9.1

NuKeeper has generated a minor update of NuGet.Protocol to 4.9.1 from 4.8.0
NuGet.Protocol 4.9.1 was published at 2018-11-28T00:06:19Z, 8 days ago
1 project update:
Updated NuKeeper.Abstractions\NuKeeper.Abstractions.csproj to NuGet.Protocol 4.9.1 from 4.8.0
NuGet.Protocol 4.9.1 on NuGet.org
This is an automated update. Merge only if it passes tests
NuKeeper: https://github.com/NuKeeperDotNet/NuKeeper

This update of NuGet.Protocol to 4.9.1 was applied manually to NuKeeper.Inspection.csproj in #587
Apply it to the other project to consolidate


Another attempt to make native timer test less flaky

Fix #2802
I'm not sure that there is a way to make this test 100% reliable because it includes multiprocessing, multithreading, and timers.

Could we use the test with Invoke-Item?

The test Debugging.Tests.ps1 use the approach.


[Feature Request] Multiple Slots in Pagination

Existing Component
Yes
Component Name
Pagination
Description
Hi,
Is it possible to use multiple slots in the pagination component?
I would like wrap this layout="prev, jumper, slot, next" with 2 buttons (one from the left side and one from the right side).
Thanks.

Sorry, we have no plan to support this.


Add a bower.json file

Adds a bower.json file so bower can use --save command and correctly
include the smooth-scroll.js file

Sorry. No interest in supporting specific package managers directly.


Date ticks on X-axis do not align with start/end values in the plot line.

For further details, pls see this problem description
I have tried various styler options to no avail eg tick padding, plot size, etc. Any suggestions?

OK, I could determine that it's not really a bug, but it's also not behaving as one would expect. I'm working on a fix. Thanks for reporting this.

OK, there are two issues at play here.

the way that Java Date objects work is not as expected or intuitive. A java.util.Date has no internal timezone and always refers to UTC by spec. You cannot change it inside this object. Therefore you need to give a Date object a long value from the defined epoch relative to UTC. The SimpleDateFormatter uses the local time zone and ends up creating a Date object that is shifted by the number of hours you are from UTC. See the following code for how to deal with this.

https://github.com/knowm/XChart/blob/develop/xchart-demo/src/main/java/org/knowm/xchart/standalone/issues/TestForIssue527.java
I need to update the API across all of XChart to use Java's new Time and Date API and get rid of Date. I'll do that some time in the future.

I added code changing the way that the axis tick labels are calculated so that there are no duplicates like you were reporting. You'll need to use the latest SNAPSHOT jar or wait for 3.7.1.


Stuck trying to upgrade to Transformer 2

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v16.13.1
Amplify CLI Version
8.0.1
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
no
Amplify Categories
api
Amplify Commands
push
Describe the bug
Hi, we were trying to upgrade from GraphQL Transformer 1 to 2.
During the initial deploy, we got the error that our security token had expired.
Upon trying to redeploy, we now get this error:
An error occurred during the push operation: ["Index: 0 State: {\"deploy\":\"deploying\"} Message: Parameters: [OpenSearchEBSVolumeGB, OpenSearchStreamBatchSize, OpenSearchAccessIAMRoleName, OpenSearchStreamingLambdaHandlerName, OpenSearchStreamMaximumBatchingWindowInSeconds, OpenSearchInstanceCount, OpenSearchInstanceType, OpenSearchDebugStreamingLambda, OpenSearchStreamingIAMRoleName, OpenSearchStreamingFunctionName, OpenSearchStreamingLambdaRuntime] do not exist in the template"]

Expected behavior
We don't get that error
Reproduction steps
I don't really know how to include this, but:

Upgrade to graphqltransformer2
amplify push
security expiration token error
amplify push

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

This is a complete production blocker, so any feedback is hugely appreciated.

@josefaidt some more information here:
We've now been able to replicate this on another sandbox environment.

We cloned the production environment and deployed as transformer v1 via amplify push
We migrated the schema.graphql file to v2
We deployed via amplify push
Deploy makes it to the very end. Fails and begins trying to rollback.
We get: security token had expired error
Rollback stops (More on this below)
Try to redeploy via amplify push - get an error message that a deploy is in progress (described here)
Delete deploy-state.json from s3 bucket
Try to redeploy via amplify push
Get this error: An error occurred during the push operation: ["Index: 0 State: {\"deploy\":\"deploying\"} Message: Parameters: [OpenSearchEBSVolumeGB, OpenSearchStreamBatchSize, OpenSearchAccessIAMRoleName, OpenSearchStreamingLambdaHandlerName, OpenSearchStreamMaximumBatchingWindowInSeconds, OpenSearchInstanceCount, OpenSearchInstanceType, OpenSearchDebugStreamingLambda, OpenSearchStreamingIAMRoleName, OpenSearchStreamingFunctionName, OpenSearchStreamingLambdaRuntime] do not exist in the template"]

At this point, we are completely dead in the water. The remote environment does not work and there is nothing we can do to fix it.
Please understand, we are trying to migrate to v2 because we are having this issue.
Not only has this killed two of our sandbox environments which is going to cost us untold hours to reimport the data into (since Amplify doesn't have a mechanism for importing/exporting data), but we have zero confidence to try this process on our production environment given that one hiccup during migration can complete kill the environment.
As for step 6 above, in our particular case, what caused the deploy to fail was the step in the deployment process where Amplify tries to delete the auto created AmplifyDataStore table. We have a permission boundary setup that prevents amplify from deleting tables.
And, yes, we can certainly disable that permission boundary (although we setup that permission boundary because we had a massive issue where Amplify deleted production Tables, so I really don't want to).
However, going back to the above, who knows if something else will happen when running this on production and then we're stuck with a broken app

Hi @CodySwannGT, can you share the contents of cli.json, at the first glance looks that the transformer version rolled back to V1 while the parameters remained the ones for V2, in V1 all the above parameters have Elastic instead of Open

@lazpavel yes. that's exactly right. Somehow (I have no idea how). I got the one environment "cody" to complete deployment to v2.
But then, I checked out a v1 environment, did work, deployed that (as v1). Then switched back to the v2 environment (did some work) and tried to deploy and got pretty much the exact opposite error.
UPDATE_FAILED               apipropswap                  AWS::CloudFormation::Stack Tue Apr 26 2022 10:31:39 GMT-0400 (Eastern Daylight Time) Parameters: [ElasticSearchInstanceCount, ElasticSearchEBSVolumeGB, CreateAPIKey, ElasticSearchInstanceType] do not exist in the template

Attached is our entire amplify directory. To say we're desperate for a fix would be an understatement
amplify.zip

Hi @CodySwannGT, please sent the amplify directory contents to<EMAIL_ADDRESS>we can work to schedule a call to investigate the issue

@lazpavel done. Thank you!

Any update or workaround here? I'm completely stuck


Python: Streamlit samples

Motivation and Context

Description
The change is required to provide a sample Streamlit program that others can use as a reference or starting point for their own Streamlit projects. This change helps developers who are new to Semantic Kernel by providing a working example that demonstrates how to create a Streamlit application. It also serves as a helpful resource specifically for Data Scientists (where streamlit is popular) to work with the semantic kernel. Current Issue
Contribution Checklist

[/] The code builds clean without any errors or warnings
[/] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[/] All unit tests pass, and I have added new tests where possible
[/] I didn't break anyone :smile:

Hi @calapsss, thank you for your contribution. We've had a lot of code change since you created this PR. I'm going to close this particular PR, but if you still want to provide the Streamlit sample, please go ahead and update things accordingly, and open a new PR. Thanks.

Updated.. Created
https://github.com/microsoft/semantic-kernel/pull/5653

Hey @aaronba I checked the link to the branch but it seems to be gone.


Is it possible to use blockContent in a cell?

I would like to put styled text, image, etc as a table content.
It's really great if we could have flexibility in a table content using blockContent.

This has been a long requested feature from the original table https://github.com/rdunk/sanity-plugin-table/issues/15
It has come up at my work, I may experiment with this soon. Do you have any particular requirements @k-yomo ?

Oh I see! Thank you!!
Our use case is to use it as a comparison table in media.
So highlighting text and showing image would be top 2 that we would like to use.

hello @k-yomo, I just introduced a new plugin called Sanity Portable Table that allows for Portable Text cells. Try it out and open an issue for bugs/feedback. PRs welcome!

@rdunk please close this issue, and also let me know if you'd like to chat about Sanity Portable Table

@snorrees @kmelve please close this issue, and also let me know if you'd like to chat about Sanity Portable Table

+1 to this as a need for us. Unfortunately there's a blocking bug in Sanity Portable Table that makes it unusable at the moment and the author stated they're unable to resolve it.


Support referring to an alias in the  index operation

When using roll-over API while benchmarking we use an alias to point to the current "write index"
but we cannot specify an alias name in the index operation definition .
When we do (ex : active-logs is the write alias and apachelogs-1 is the current index)  , we get:
[ERROR] Cannot race. ('Fatal error in load generator [0]', RallyAssertionError('The provided index [active-logs] does not match any of the indices [apachelogs-1].',))
proposed enhancement : allow for 'alias' in the index operation

I do have some limited support for this in my track, which you may be able to use: https://github.com/elastic/rally-eventdata-track

I think it makes sense to add this to core.

Thinking about it again, this should already work if you define your indexing operation in the following way:
{
  "name": "bulk-index-active-logs",
  "operation-type": "index",
  "index": "active-logs",
  "bulk-size": 5000
}

Did you try this already @zumo64?

Closing due to lack of feedback. Please feel free to reopen if there is new information.


decode Polyline

Please add the decoding polyline function as well.

Just started using this library and needed polyline encoding/decoding and I found the polyline node package which does the job.
This may be derailing a bit, but has anyone found a node.js version of v3_epoly.js or a similar way to get a point on a polyline at a given distance ?


Add support for io.spring.dependency-management

When i use io.spring.dependency-management plugin to manage my dependencies, updateOfflineRepository will fail to resolve dependency versions, or spring-platform.
Steps to reproduce:

apply plugin: 'io.spring.dependency-management'
add mavenBom 'io.spring.platform:platform-bom:Brussels-SR6' to imports in dependencyManagement

 registration of listener on 'Gradle.buildFinished' is unsupported


chore: supported node version update

Ticket
https://github.com/VirtusLab-Open-Source/strapi-plugin-navigation/issues/292
Summary
What does this PR do/solve?
Expand on supported to Node v18.
Test Plan
No functionality is introduced.

@cyp3rius hey hey 👋 could you release to npm a new version with this change? That would be nice 😊

Fixed in 2.2.3


FortiGate platform handle VDOM's and changing prompts

I've been working on getting scrapligo work properly on a FortiGate, and I've run into a few issues.
I've created the following bare bones platform:
---
platform-type: 'fortinet_fortios'
default:
  driver-type: 'network'
  privilege-levels:
    exec:
      name: 'exec'
      pattern: '[\w_-]+ [$#]'
      previous-priv:
      deescalate:
      escalate:
      escalate-auth: false
      escalate-prompt:
    configuration:
      name: 'configuration'
      pattern: '^[\w_-]+ \([\w_-]+\)? [$#]'
      previous-priv: 'exec'
      deescalate: "end"
      escalate: # ?? depends on if VDOM's are enabled or not
      escalate-auth: false
      escalate-prompt:
  default-desired-privilege-level: 'exec'
  failed-when-contains:
    - "Command fail"
  textfsm-platform: '' # ignored in go because no ntc-templates
  network-on-open:
    - operation: 'acquire-priv' # targets default desired priv by default
  network-on-close:
    - operation: 'acquire-priv'
    - operation: 'channel.write'
      input: 'exit'
    - operation: 'channel.return'

I have a few issues though, and maybe there's already a solution I just haven't found.
Configuration - and show commands - on fortigates depends on whether or not vdom's are enabled.
If a VDOM is enabled most commands have to follow the below syntax:
config vdom
  edit {{vdom_name}}
    get system interface
    or config system interface

Without VDOM it's just:
get system interface
or config system interface

I can handle that my self - but the fortigate also changes the prompt when doing so - so it starts as "fw-1 #" and ends as "fw-1 (vdom_name) #". I have found opoptions.WithInterimPromptPattern and that does work, but I have to add an explicit "end" to my config snippet above since priv is not automatically reset.
I see no way to get SendConfigs to work as escalate again depends on if vdoms are enabled, or not - Is there any way to get this to work, or should i just "skip" using SendConfigs and do it using SendCommands ?

can you share some output of what things look like in a terminal if you were configuring/showing stuff in both scenarios?
you could have a configuration level configuration and another configuration-vdom maybe, we have some stuff like that for configure vs configure exclusive (XR/junos). im not sure I fully follow the part where you need interim prompt and having to re-escalate though so maybe the example will help me grok it.
in general though, the SendConfig{s} stuff is really just convenience around SendCommand{s} anyway, so if it doesnt fit right/well then I think it seems very reasonable to just use the send commands. again, maybe some terminal output will give me a better idea though, so we'll see!
also just for context -- vdom is something like a firewall context or something? doesnt matter of course, just curious :p

Sure thing - Here's a few examples.
When VDOM's are in use, the following syntax would be use:
fw-2 # config vdom
fw-2 (vdom) # edit fw-inet
current vf=fw-inet:1

fw-2 (fw-inet) # get system interface
== [ ha ]
name: ha   mode: static    ip: <IP_ADDRESS> <IP_ADDRESS>   status: up    netbios-forward: disable    type: physical   netflow-sampler: disable    sflow-sampler: disable    src-check: enable    explicit-web-proxy: disable    explicit-ftp-proxy: disable    proxy-captive-portal: disable    trunk: disable    mtu-override: disable    wccp: disable    drop-overlapped-fragment: disable    drop-fragment: disable
== [ mgmt ]
name: mgmt   ip: <IP_ADDRESS> <IP_ADDRESS>   status: up    netbios-forward: disable    type: physical   netflow-sampler: disable    sflow-sampler: disable    src-check: enable    explicit-web-proxy: disable    explicit-ftp-proxy: disable    proxy-captive-portal: disable    trunk: disable    mtu-override: disable    wccp: disable    drop-overlapped-fragment: disable    drop-fragment: disable

fw-2 (fw-inet) # end
fw-2 #

fw-2 (fw-inet) # config system interface
fw-2 (interface) #

If VDOM's are not used, it would be the following:
fw-2 # get system interface
== [ ha ]
name: ha   mode: static    ip: <IP_ADDRESS> <IP_ADDRESS>   status: up    netbios-forward: disable    type: physical   netflow-sampler: disable    sflow-sampler: disable    src-check: enable    explicit-web-proxy: disable    explicit-ftp-proxy: disable    proxy-captive-portal: disable    trunk: disable    mtu-override: disable    wccp: disable    drop-overlapped-fragment: disable    drop-fragment: disable
== [ mgmt ]
name: mgmt   ip: <IP_ADDRESS> <IP_ADDRESS>   status: up    netbios-forward: disable    type: physical   netflow-sampler: disable    sflow-sampler: disable    src-check: enable    explicit-web-proxy: disable    explicit-ftp-proxy: disable    proxy-captive-portal: disable    trunk: disable    mtu-override: disable    wccp: disable    drop-overlapped-fragment: disable    drop-fragment: disable

With regards to configuration:
When in VDOM mode I guess the config vdom would be equal to conf t on a cisco device, and I would have to add an edit <vdom-name> to all my config - that is workable, and it would be possible to escalate and deescalate from.
When not in VDOM mode there is no single config command:
fw-2 # config
alertemail             Alert email configuration.
antivirus              AntiVirus configuration.
application            Application control configuration.
authentication         authentication
dlp                    DLP configuration.
dnsfilter              DNS filter configuration.
emailfilter            AntiSpam configuration.
endpoint-control       Endpoint control configuration.
extender-controller    FortiExtender controller configuration.
file-filter            file-filter
firewall               Firewall configuration.
ftp-proxy              FTP proxy configuration.
icap                   ICAP client configuration.
ips                    IPS configuration.
log                    Log configuration.
router                 Router configuration.
sctp-filter            SCTP filter configuration.
ssh-filter             SSH filter configuration.
switch-controller      External FortiSwitch configuration.
system                 System operation configuration.
user                   Authentication configuration.
videofilter            videofilter
voip                   VoIP configuration.
vpn                    VPN configuration.
waf                    Web Application Firewall configuration.
web-proxy              Web proxy configuration.
webfilter              Web filter configuration.
wireless-controller    Wireless access point configuration.

fw-2 # config system  interface

fw-2 (interface) #

So I would either have to create a config context for all those + one for VDOM, or just not use the SendConfig command make the the prompt in SendCommand generic to support all possible prompts.
With regards to the interim prompt - It's not needed if I just create a prompt pattern that supports all scenarios like the following: [\w_-]+ (?:\([\w_-]+\)? )?[$#]. But by doing this I miss out on the SendConfig command and automatic deesclation, though not an major issue I was just wondering if there was any better way?
And yes VDOM's are to some extent like contexts, basically "virtual" firewalls with it's own config :)

@patrickfnielsen awesome, thanks for the great detail!
I wonder if this may be a solid opportunity for a not well (or at all???) documented feature/thing "variants".
tl;dr here is that the idea is you have some platform, lets say "acme_os", and that there is some scenario where there are some slight differences, for example (and similar here!) acme-os behaves a bit differently in a multi supervisor type setup. with a variant you can expand the base "acme-os" to add additional privilege levels or to change the "Failed when contains" list or something like that.
so im wondering if the base platform could be "fortigate-fortios" then a variant for "vdom" ; in this case the base platform would not have a configuration level and you would just use send command(s), and the variant would have a configuration level that gets you into "config vdom" mode? but maybe this isn't still very nice since you'd kinda need the name of the vdom?
because we are talking scrapligo and not python we are a little more constrained with how much we can just kinda yolo some stuff :) in python you could write a community platform and that gets you the ability to override methods to basically make this behave way more like you want -- check out the fortigate python platform if you haven't already, Viktor did some cool stuff over there. perhaps an alternative option that gets you the ability to do sorta what Viktor has done is to have a scrapli-fortigate package that accepts a network driver as an argument and then does XYZ, so you could just have a generic driver and then wrap that with your package. maybe it could look like:
type FortiWrapper struct {
	*network.Driver
}

func (w *FortiWrapper) DoStuff() {
	w.SendCommand("foo")
}

func main() {
	p, err := platform.NewPlatform(
		"fortigate_fortios",
		"<IP_ADDRESS>",
	)
	if err != nil {
		panic(err)
	}

	d, err := p.GetNetworkDriver()
	if err != nil {
		panic(err)
	}

	// maybe second arg here is "true/false" for vdom, or you could do options or whatever of course
	// this thing could embed
	fw := FortiWrapper{d}
	fw.SendConfigs("blah")
	fw.DoStuff()
}

This raises a bigger point that ive long wanted to address but just never have had enough of a need: how can we enable scrapli_community like extensions (like Viktor's linked above that adds some methods and overrides some others) in scrapligo. I'm sure there is an answer/way but I surely do not know what it is :D if you have thoughts I am all ears!
Last bits for now:

With regards to the interim prompt - It's not needed if I just create a prompt pattern that supports all scenarios like the following: [\w_-]+ (?:([\w_-]+)? )?[$#]. But by doing this I miss out on the SendConfig command and automatic deesclation, though not a major issue I was just wondering if there was any better way?

I would defo not add all the patterns to the prompt -- you can and it would/could work, but it will be hellaciously slow. this is the slowest part of scrapligo and I was actually tinkering this past weekend too see if there are any easy ways to make the prompt matching a bit more efficient. maybe more to come on that.

Maybe by having the library check for all prompts and detected that the privilege level has been escalated to configuration automatically, but since it knows what level it should be in it could send the deescalate command - Though this might be a lot of work for little gain.

So... this partly falls in line w/ the above comment too -- historically (for better or maybe worse??) we've only ever actually checked/asserted that we are at the correct priv level when a user calls AcquirePriv or calls that in a round about way by calling SendConfig(s). As things stand the "base" prompt pattern actually is always a compiled pattern of all privilege levels (part of why this is hellaciously slow/inefficient!) so we don't actually ever "fail" to find a prompt even if a user escalates/deescalates on their own outside of the "normal" flow of things. So I think doing what you propose actually is fairly trivial (just an acquirePriv call in send command to acquire the default desired privilege similar to what we do in send configs), but... im not sure I love it? Im not sure I have good reasons/thoughts about why at the moment though other than its for sure extra overhead in terms of time/commands to send/parse/etc.. I'll think on this one though and maybe come back with smarter words :p
Ok, sorry for the wall of text. im not actually sure that helped move things along but I think I should quit while im already behind... so let us know what ya think/if that helps at all!

Thanks for the great feedback, it does help and I appreciate it!
I would prefer one platform, as I simply think it's cleaner - and because I dont always know if VDOM's are enabled or not before i connect.
I like the idea of the FortiWrapper - and for now - I think that is what I'm going to go with, as it will allow me to hide some of the VDOM handling away, and also overwrite SendConfigs to use SendCommands.
With regards to scrapli_community like extensions, I could definitely see the use case as well, I'm not 100% sure how we could do it in the best way though - I'll try and think a bit about it and get back to you!
One thing I did consider was to extend the network-on-open commands to be able to capture output, and store that for use by the driver later, though this could also be done by using the FortiWrapper you mentioned.

nice! sounds like a path forward for now at least. ill go ahead and close this but feel free to reopen or hit us up on discord if you wanna pow wow more (network automation hangout or containerlab or srlinux servers)!


bad parse on relative Uri

The uri "g" gets parsed as the authority, but apparently it should be parsed as the path.
val jUri = new java.net.URI("g")
jUri: java.net.URI = g
scala> jUri.getAuthority
res7: String = null
scala> jUri.getPath
res8: String = g

vs
import org.http4s.Uri
val sUri = org.http4s.Uri.uri("g")
sUri: org.http4s.Uri = g/
scala> sUri.authority
res0: Option[org.http4s.Uri.Authority] = Some(g)
scala> sUri.path
res1: org.http4s.Uri.Path = /

This beastly regex copied from https://tools.ietf.org/html/rfc3986#appendix-B also parses "g" as the path:
val R = "^(([^:/?#]+):)?(//([^/?#]*))?([^?#]*)(\\?([^#]*))?(#(.*))?".r
val R(_,scheme,_,authority,path,_,query,_,fragment) = "g"
scheme: String = null
authority: String = null
path: String = g
query: String = null
fragment: String = null

I tried to convert this into a simple reference Uri parser, but got stuck on parsing the subcomponents of Authority.  Then I took a look at Rfc3986Parser but got scared.

java.net.URI is based on an older RFC, so I would not consider it authoritative.  The regex from the RFC makes a more compelling case that we have a problem.

Oh yeah, I didn't even notice.  (RFC 2396 vs 3986)

It looks like an authority has to have a // with it, i.e. //g.
Even foo.com/file should all go into path, but //foo.com/file gets split into authority=foo.com, path=/file.  http://foo.com/file should get split into scheme, authority, and path like we're used to.

I believe this is closed via #191. @refried, if you discover differently, will you please reopen?

LGTM


@sentry/vite-plugin"' has no exported member 'sentryVitePlugin'

After updating @sentry/vite-plugin from version 0.3.0 to 0.4.0 I get this error
Module '"@sentry/vite-plugin"' has no exported member 'sentryVitePlugin'. Did you mean to use 'import sentryVitePlugin from "@sentry/vite-plugin"' instead?
Based on your documentation we should use it like this
import { sentryVitePlugin } from '@sentry/vite-plugin';
But if Import it like this (as suggested by the VS Code), I don't get the error/warning but when running the app it throws an error while the other one works fine
import sentryVitePlugin from '@sentry/vite-plugin';
Expected Result
Everything should work perfectly
Actual Result
It complaines saying that Module '"@sentry/vite-plugin"' has no exported member 'sentryVitePlugin'. Did you mean to use 'import sentryVitePlugin from "@sentry/vite-plugin"' instead?

Hi, this is the plugin is exported like this: https://unpkg.com/browse/<EMAIL_ADDRESS>Can you delete your node_modules, reinstall them and try again? It seems like something weird is going on.

@lforst
Hi, already did it and I still get the warning, but I have updated last night on a personal project and it doesn't complain.
So probably it's some settings that I have on the project that is causing that.
Thanks

Now I remember
There is a difference between the projects, on the one I get the warning we are using ECMAScript Modules. Could this be the reason? But looking at the way it is exported it also uses ECMAScript Modules, right?

Now I remember There is a difference between the projects, on the one I get the warning we are using ECMAScript Modules. Could this be the reason? But looking at the way it is exported it also uses ECMAScript Modules, right?

You should be able to use both ES modules and CJS modules without any issues. The file I shared is esm.

I am also having this issue. This is the first time I've used the plugin so it can't be stale node modules, and I've tried changing my project from ESM to CJS and back and neither worked.

Can any of you provide a repro example we can pull to debug this further? A stackblitz or something like that would also work.


refactor: Fix missing param in README.md file

Fix missing param in README.md file --metadata
Signed-off-by: Tibor Dudlák<EMAIL_ADDRESS>

refactor or docs as commit scope?

I would go for refactor with such small change docs might be included in changelog later.


Conductor not generating PRs when there are no cherrypicks

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
When there is not a new dart version the engine PR is supposed to be skipped on a new release. However if that happens the framework PR is also not generated by conductor and the release engineer needs to manually roll the engine into the framework
Expected results
PR generated by conductor
.

check tip of commit hash and fix conductor


Bump go version to 1.16

Go 1.15 is EOL and 1.17 has been released for about 3 months (https://endoflife.date/go). It should be reasonable to bump required go version to 1.16. I'd like to revert the previous PR (#217).

@disksing Hi, please consider it if the upgrade is not in your schedule, thanks!

LGTM.
By the way, I think we can define the policy explicitly. For example, we can always drop support of an EOL go version. cc @disksing

Thanks @SandyXSD


Ensure relative alchemical protocol definition is consistent with relative alchemical factory

The lambda protocol has been separated out into annihilation/lambda_protocol.py and lambda has been redefined throughout such that
lambda 0 = off, 1 = on
not
lambda 0 = state A, 1 = state B

Just looked at the travis test failures, and am collecting some notes here:

[ ] This message appears a billion times and should be moved to DEBUG or something:

proposal_engine: INFO: Generating atom map...
proposal_engine: INFO: Atom map took 0.002 s

[ ] We need travis to install tqdm:

ImportError: No module named 'tqdm'

[ ] There are lots of errors of residues not found, like

======================================================================
ERROR: Test that the hybrid returns the correct positions for the new and old systems after construction
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/miniconda/envs/test/lib/python3.5/site-packages/nose/case.py", line 198, in runTest
    self.test(*self.arg)
  File "/home/travis/miniconda/envs/test/lib/python3.5/site-packages/perses/tests/test_hybrid_builder.py", line 296, in test_position_output
    topology_proposal, old_positions, new_positions = utils.generate_vacuum_topology_proposal()
  File "/home/travis/miniconda/envs/test/lib/python3.5/site-packages/perses/tests/utils.py", line 895, in generate_vacuum_topology_proposal
    topology_proposal = proposal_engine.propose(solvated_system, top_old, current_mol=current_mol, proposed_mol=proposed_mol)
  File "/home/travis/miniconda/envs/test/lib/python3.5/site-packages/perses/rjmc/topology_proposal.py", line 1959, in propose
    new_mol_start_index, len_new_mol = self._find_mol_start_index(new_topology)
  File "/home/travis/miniconda/envs/test/lib/python3.5/site-packages/perses/rjmc/topology_proposal.py", line 2087, in _find_mol_start_index
    raise ValueError("There must be exactly one residue with a specific name in the topology. Found %d residues with name '%s'" % (len(mol_residues), resname))
ValueError: There must be exactly one residue with a specific name in the topology. Found 0 residues with name 'benzene'

[ ] The test that prints for each torsion, calculate position of atom1 outputs a long string of inscrutable numbers that should be suppressed:

4.470348439570653e-08
4.470348439570653e-08
4.470348439570653e-08
4.4703483489024386e-08
4.4703484469721395e-08

[ ] Haven't seen this failure before:

======================================================================
ERROR: Test that the SmallMoleculeAtomMapper can generate maps that exclude hydrogens
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/miniconda/envs/test/lib/python3.5/site-packages/nose/case.py", line 198, in runTest
    self.test(*self.arg)
  File "/home/travis/miniconda/envs/test/lib/python3.5/site-packages/perses/tests/test_topology_proposal.py", line 114, in test_no_h_map
    kinase = KinaseInhibitorsTestSystem()
  File "/home/travis/miniconda/envs/test/lib/python3.5/site-packages/perses/tests/testsystems.py", line 1841, in __init__
    super(KinaseInhibitorsTestSystem, self).__init__(**kwargs)
  File "/home/travis/miniconda/envs/test/lib/python3.5/site-packages/perses/tests/testsystems.py", line 1766, in __init__
    systems[environment] = system_generators[environment].build_system(topologies[environment])
  File "/home/travis/miniconda/envs/test/lib/python3.5/site-packages/perses/rjmc/topology_proposal.py", line 1832, in build_system
    msg += traceback.format_exc(e)
  File "/home/travis/miniconda/envs/test/lib/python3.5/traceback.py", line 163, in format_exc
    return "".join(format_exception(*sys.exc_info(), limit=limit, chain=chain))
  File "/home/travis/miniconda/envs/test/lib/python3.5/traceback.py", line 117, in format_exception
    type(value), value, tb, limit=limit).format(chain=chain))
  File "/home/travis/miniconda/envs/test/lib/python3.5/traceback.py", line 474, in __init__
    capture_locals=capture_locals)
  File "/home/travis/miniconda/envs/test/lib/python3.5/traceback.py", line 332, in extract
    if limit >= 0:
TypeError: unorderable types: ValueError() >= int()

We are still finding issues with the hybrid alchemical factory, but merging the improvements from this branch so we can consolidate several code changes and continue debugging.


fix mux_admin assets handle

各种 SamplesHandler 里的 mux.Handle 没有额外给到 / 后缀，直接使用会导致 vue.js 等资源文件无法加载，所以应使用 mux_web_vuetify.IndexMux 包裹，其内部对此有补充处理。
他处对 SamplesHandler 的调用均有包裹，mux_admin.SamplesHandler 里有缺失，导致 server/main.go 启动后，demo 跳转后是空白页。

Hi @molon. Thanks for your PR.
PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


If a download is cancelled and is re-tried upon exactly after 2 minutes, the download fails!

Describe the bug
If a download is cancelled and is re-tried upon exactly after 2 minutes, the download fails!

What operating system and which version - MacOS Monterrey Version 12.5 (21G72)
Which version of Rocket.Chat (Server) - 5.0.2
Which version of Rocket.Chat.Electron (Electron/Desktop) - 3.8.8

To Reproduce
Steps to reproduce the behavior:

Start downloading a file
Go to the Download View using the sidebar
Cancel the download
Retry the download after 2 minutes(120seconds)
We can see that the download fails!

The bug
On starting a new download, when we cancel the download and retry it after 2 mins, the S3 download URL seems to be expired and instead a *.xml file is downloaded
Expected behaviour
On starting a new download, when we cancel the download and retry it after 2 mins, a notification stating that "the download has expired, try downloading again from the source" could appear!
Demonstration of the error
https://user-images.githubusercontent.com/72302948/186968809-d3444a94-fca6-4bcc-a50a-ec05cad74a15.mp4

@henit-chobisa  This is an Electron issue? I think that this is a server thing and its because of security of the assets.

@henit-chobisa  This is an Electron issue? I think that this is a server thing and its because of security of the assets.

Hey there @jeanfbrito! We do understand that the expiry time in the S3 download url is set in the server for security purposes.
But on the electron side of things, we've realised that on clicking on the retry button, the initial download url is just reused hence it would be needful to handle the download url expired case (which right now shows an invalid xml file download) on the Electron App and notify the user about it!
It would be awesome if you could go through the issue and the PR we've made in order to get a better context of our thought process 😄

Already replied to the PR. Take a look there.
Em sex., 26 de ago. de 2022 às 16:35, Henit Chobisa <
@.***> escreveu:

@henit-chobisa https://github.com/henit-chobisa This is an Electron
issue? I think that this is a server thing and its because of security of
the assets.
Hey there @jeanfbrito https://github.com/jeanfbrito! We do understand
that the expiry time in the S3 download url is set in the server for
security purposes.
But on the electron side of things, we've realised that on clicking on the
retry button, the initial download url is just reused hence it would be
needful to handle the download url expired case (which right now shows an
invalid xml file download) on the Electron App and notify the user about it!
It would be awesome if you could go through the issue and the PR we've
made in order to get a better context of our thought process 😄
—
Reply to this email directly, view it on GitHub
https://github.com/RocketChat/Rocket.Chat.Electron/issues/2487#issuecomment-1228846652,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI7PCTCYBTQFWS6ZKCBH3TV3EMANANCNFSM57XT5XMA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Atenciosamente,
Jean Brito.


Koji build follow-up: correct url, state and more logging

Fix state and url for build status.
Add missing test file. (Forgot to add when restructuring the commits in the first PR.)

I've also fixed the used target and added a test for it. Please, PTAL


Remove wrench and key icons - have been updated in core

Remove wrench (config -as-code) icon
Remove the key (credentials) icon
Reduce icon size

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[x] Link to relevant issues in GitHub or Jira
[x] Link to relevant pull requests, esp. upstream and downstream changes
[x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

H


Allow configuring replicas for raw deployments

What this PR does / why we need it:
This adds the ability to configure a hard number of replicas when using Raw deployment mode.
The replica count cannot be customized by default, because autoscaling needs to be taken into account. The only two supported autoscalers were the standard HPA (default), and External ones. In both cases, the replicas field of the deployment is assumed to be managed by a third-party controller. Thus, the user didn't have a way to manually manage the replicas of deployed models.
To let users to manually manipulate pod replicas for raw deployments, a new none autoscaler class is added. This new autoscaler class would indicate to KServe controller that there is no autoscaling, and will let users set a hard replica count by using a new replicas field in the InferenceService CRD.
This commit augments only the InferenceService CRD with the replicas field. For InferenceGraph, replicas still won't be user-controllable.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #3514
Type of changes
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Feature/Issue validation/testing:
TODO
Checklist:

[ ] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

Allow configuring replicas in for raw deployments

Re-running failed tests

/rerun-all - rerun all failed workflows.
/rerun-workflow <workflow name> - rerun a specific failed workflow. Only one workflow name can be specified. Multiple /rerun-workflow commands are allowed per comment.

@yuzisun I have this PR that I hope you can review.

related issue #3439

/re-run test-predictor

/rerun-all

/rerun-all


AVX512 support

Hi,
I was just wondering if you are planning to provide support for AVX512 in addition to AVX2, as I am working on KNL and SKL systems and I think AVX512 would give a good speedup.
Thanks,
Al

I am not sure, but given that two GSOC projects are granted maybe the idea to incorporate LIBXSMM somewhere is on the table?
There is optimized code for all flavors of AVX-512 (KNL/KNM and SKX) with specific optimizations beyond AVX-512F. For example, TF 1.1.0 released integration with LIBXSMM wrt our SPMDM domain (SParseMatrix-DenseMatrix multiplication) which targets AVX2 and AVX-512/Core. Though, the main work for TF+LIBXSMM is still ongoing (the non-sparse convolution code).

Forget about GSOC, I have messed this up with tiny-dnn. Sorry.

@al-rigazzi SKX will be supported when I get access to a Skylake Xeon with AVX-512, probably as soon as in the next few weeks. KNL support would need to wait until NNPACK and pthreadpool implements hierarchical blocking and threading, which is WIP.

@Maratyszcza, good to know, I will wait for it to happen.


casemove cases from p2 to p0

Proposed changes
move cases from p2 to p0

run buildall

run external

run feut

run buildall

run buildall

run p0

run external


Broadband - BEAD Challenge Portal

Benefit
Fulfilling GOEO BO's requirement for the BEAD portal
Acceptance
Either:

A plan to help them and their salesforce team build a custom portal OR
GOEO BO identifies a vendor to create one for them.

Notes
October 30

GOEO is obtaining estimates for a portal from Horrocks and Sanborn. UGRC may only be involved insomuch as some data preparation is required.

GOEO hired Horrocks Engineering to build the challenge portal. UGRC's role was that Jake helped GOEO set up their shiny new AGOL org for the data and challenge portal app to live in.


Fix reload page before all file uploaded bug

What problem are we solving?
Fix issue #3518
How are we solving the problem?
Do not reload page before all file uploaded.
How is the PR tested?
Test manually, upload many files include big and small files.
Checks

[ ] I have added unit tests if possible.
[ ] I will add related wiki document changes and link to this PR after merging.

This issue is introduced by 986daecbfea12bffd4eef5b601108639428c0e7a

Actually loadend event should be triggered by browser after the upload request finish (success or error). And loadend event is supported by modern browser such as Chrome, Edge, Firefox, Safari and so on. And for now IE is not supported by Microsoft so I cannot find whether IE support it. Maybe some version of IE cannot trigger the loadend event and the page not refreshed after all file uploaded.

Thanks for the help!
IE is dead. No need to worry about it.


v3.2.alpha2.official Script>File>Open adds an extra // before filename in the scripts list. Save then blanks out the name from list

Godot version:
v3.2.alpha2.official
OS/device including version:
Mac OS X, Mojave
Issue description:
Script>File>Open adds an extra // before filename when hovered over scripts list. When you then Save it  blanks out the filename name from list.
After File>Open  (Notice the // before the filename on the tooltip)

After File>Save  (Notice the blanked out name after the Save)

Steps to reproduce:

Open any script via File>Open and hover over to view the // before then name
Save the script and notice how name disappears.
Also if you try to close it, it gives an error that it was not saved.

Do you have non-default text_editor/script_list configurations in the editor settings? In either case I cannot reproduce this in 3.2.2-stable nor 4.0-dev master anymore.

Cannot reproduce it in 3.5 and 4.0 Beta. Will close.


Wrong validation of PushNotification forms

Describe the Bug

Our service team reported that push notifications are getting sent even if the form validation fails. In this specific case the message was too long and the message couldn't be sent. However, our system sent the notification via firebase and the apps couldn't receive the full message from our API as the objects couldn't get created as of the validation errors...
Expected Behavior

If the form check fails, no PN should be sent.
Actual Behavior

The form fails and no object gets created. However, the PN gets sent via firebase anyways.
Additional Information

Aug 17 16:14:10 DEBUG integreat_cms.cms.forms.push_notifications.push_notification_form - PushNotificationForm validated with cleaned data {'channel': 'news', 'mode': 'ONLY_AVAILABLE'} Aug 17 16:14:10 DEBUG integreat_cms.cms.forms.push_notifications.push_notification_translation_form - PushNotificationTranslationForm submitted with errors: {'text': ['Ensure this value has at most 250 characters (it has 253).']}

Duplicate of #1631


#38 Added Custom Gradient ScrollBar

#38 Solved
Added Gradient ScrollBar shown below

@aakashraj01 Fetch the upstream on your fork and then we're good to go!

Ok @lovishprabhakar doin right now

@lovishprabhakar Done fetch and upstream..Can you now able to merge it

@lovishprabhakar Are you able to merge it ? or is there any issue happened

@aakashraj01 why did you close the Pull Request?
There are no issues, are you working on something or shall I merge this one?

@lovishprabhakar Merge this one ..actually I thought there is some issue in this pr

merging. Good work! @aakashraj01

@lovishprabhakar Thank You so much for merging my contribution...


feature: Show radical color

This is a fantastic project! Thanks so much for sharing this.
ZDT somehow used the data to show radical in red, when present. So this is a feature request..
Looking at the stroke file, ZDT may have identified the radical from the prefix information.
For the character 成 (the example on the main zdt page), the stroke data file prefixes are:
1PR
4PO
1NO
3NO
6PO
2NR
7PR
4PR
2PR
I guess the numbers are direction of stroke. Maybe the second character is related to whether or not the final part of a complete stroke is being drawn (P seems to indicate final, whereas N means there are still additional parts remaining to the stroke). But for radical colorizing purposes it looks like the R of the third character stands for Radical.. (With O meaning non-radical) If that is really so, it shouldn't be too hard to also imitate ZDT's radical coloring feature. In the above example, the reason the first stroke contains an R is that the first stroke of the radical (戈) has been joined with the second stroke of the 方 preceeding it. So since they did not record two separate strokes, the entire first stroke will be red. Checked this theory against 你 as well and it works there too.

This definitely should be possible - thanks for opening the issue! I don't have time in the short term to add this feature but if you or someone else wants to do it and open a PR go for it!


ensure updated config is synced on use of restart command

Initial read configuration was never refreshed as the restart command runs, which means you'd always get potentially stale initial config after a restart.
Also clean up a few init things that I suspect has never been cleaned up after the initial adaption of the LS client example.

Looks great.
The only thing that comes to mind, is how to make it completely explicit that the code that follows createLanguageClient is the global state. (which is preserved on restart).

In fact, there's one other small bit of global state:
let client: LanguageClient;

which is followed by a bunch of commented out code. Then the createLanguageClient function. Then the rest of the global state.


Strawberry Shake generated client code does not include enums that start with an underscore "_"

Product
Strawberry Shake
Version
13.9.14
Link to minimal reproduction
none
Steps to reproduce
Enums that start with an underscore seems to be problematic.  For example,
public enum AccountType
{
    _401k
}

I see it in the schema but not in the strawberryshake generated code and I get a build error.
What is expected?
I expect to see public enum AccountType { _401k } in the strawberry shake generated code
What is actually happening?
Exists in the schema
enum AccountType {
  _401_K
}

Enum doesn't exist in in the strawberry shake generated code.
Also a build error occurs with this error.
Unhandled exception. System.AggregateException: One or more errors occurred. (The specified name is not a valid GraphQL name. (Parameter 'name'))
---> System.ArgumentException: The specified name is not a valid GraphQL name. (Parameter 'name')
at HotChocolate.Utilities.NameUtils.EnsureGraphQLName(String name, String argumentName) in /home/runner/work/graphql-platform/graphql-platform/src/HotChocolate/Core/src/Abstractions/Utilities/NameUtils.cs:line 38
at StrawberryShake.CodeGeneration.Analyzers.Models.EnumValueModel..ctor(String name, String description, IEnumValue value, String underlyingValue) in /home/runner/work/graphql-platform/graphql-platform/src/StrawberryShake/CodeGeneration/src/CodeGeneration/Analyzers/Models/EnumValueModel.cs:line 18
at StrawberryShake.CodeGeneration.Analyzers.DocumentAnalyzer.CollectEnumTypes(IDocumentAnalyzerContext context) in /home/runner/work/graphql-platform/graphql-platform/src/StrawberryShake/CodeGeneration/src/CodeGeneration/Analyzers/DocumentAnalyzer.CollectEnumTypes.cs:line 30
at StrawberryShake.CodeGeneration.Analyzers.DocumentAnalyzer.CreateOperationModel(IDocumentAnalyzerContext context) in /home/runner/work/graphql-platform/graphql-platform/src/StrawberryShake/CodeGeneration/src/CodeGeneration/Analyzers/DocumentAnalyzer.CollectOutputTypes.cs:line 17
at StrawberryShake.CodeGeneration.Analyzers.DocumentAnalyzer.AnalyzeAsync() in /home/runner/work/graphql-platform/graphql-platform/src/StrawberryShake/CodeGeneration/src/CodeGeneration/Analyzers/DocumentAnalyzer.cs:line 55
at StrawberryShake.CodeGeneration.CSharp.CSharpGenerator.GenerateAsync(IEnumerable1 fileNames, CSharpGeneratorSettings settings) in /home/runner/work/graphql-platform/graphql-platform/src/StrawberryShake/CodeGeneration/src/CodeGeneration.CSharp/CSharpGenerator.cs:line 133
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification)
at StrawberryShake.Tools.GenerateCommand.GenerateCommandHandler.GenerateClient(String clientName, String[] documents, CSharpGeneratorSettings settings) in /home/runner/work/graphql-platform/graphql-platform/src/StrawberryShake/Tooling/src/dotnet-graphql/GenerateCommand.cs:line 164
at StrawberryShake.Tools.GenerateCommand.GenerateCommandHandler.ExecuteAsync(GenerateCommandArguments args, CancellationToken cancellationToken) in /home/runner/work/graphql-platform/graphql-platform/src/StrawberryShake/Tooling/src/dotnet-graphql/GenerateCommand.cs:line 124
at McMaster.Extensions.CommandLineUtils.CommandLineApplication.ExecuteAsync(String[] args, CancellationToken cancellationToken)
at StrawberryShake.Tools.Program.(String[] args)
Relevant log output
No response
Additional context
No response

Duplicate of #4771.

Please try version 14.


sir,what's client.bin, could you give us a document

sir,what's client.bin, could you give us a document?
do I must  close my antivirus software ?

https://github.com/quasar/Quasar/wiki/Getting-Started


HBase 2.4

First of all, and a bit of a sidebar, I have a growing suspicion that this fork doesn't need to exist. It seems that its main purpose is to match dependency versions with EMR, but it's possible to do that in our own pom files using the properties that we're modifying in this. I'm going to experiment with that later.

The purpose of this PR is to match our hbase-server version with the jar provided on EMR. While our HBase is listed as 2.2.6, the library code we have from Amazon is for 2.4.1+. There was a breaking change introduced in HBase 2.4.1 which is present in the jars labeled 2.2.6, and this mismatch prevents bulkLoadThinRows() from working.
Specifically what is going on is that a couple of helpers moved from HStore to StoreUtils, eg getChecksumType(). This change was introduced in HBase 2.4.1 via this PR: https://github.com/apache/hbase/pull/2800. If you search that PR's files, you'll see that getChecksumType() moved.
hbase-connectors relies on getChecksumType() and a few other helpers in bulkLoadThinRows(), which we use for the Competitor Historical Migration jobs. With these being out of sync, we can't run the bulk load.
To fix that, this fast forwards and brings in https://github.com/apache/hbase-connectors/pull/88.

This also includes reverting a few things in our local fork that I don't think make much sense:

We were hard coding the version everywhere instead of using ${revision} and setting it once in the parent properties
The version properties were being modified in the pom and the Jenkinsfile

Closing this in favor of https://github.com/sproutsocial/hbase-connectors/pull/11 which I think creates less noise and doesn't lose upstream commits in a rebase.


Break up server package

The server package is growing redundant. It's taking care of halting the program on SIGINT or related reasons, spinning up all goroutines, and standing up HTTP endpoints. The Server object has a Start() func, for crying out loud. This stuff belongs in the main() func. It makes sense to separate these concerns by making new objects for each of these responsibilities. This will improve the readability and maintainability of this codebase.
This PR also introduces a new abstraction layer on top of HTTP handlers: the RouteHandler interface. If an object is a RouteHandler, then it is capable of registering handler funcs that respond to requests on HTTP endpoints with a *mux.Router. This new pattern makes it easy to introduce new HTTP endpoints without the mux initialization section of the codebase growing cluttered and unreadable with loads of HandleFunc() calls.

Would have loved to see tests with this, but it'll be okay for now. I'm not sure if this will be the final iteration of this organization scheme, so I don't wanna invest time writing tests that will need to be refactored in the future.