Ruff linter/formatter first setup

Setting up Ruff (the same tool used in Mitiq), so we don't have to care about linting and formatting (new lines, unused vars, etc..) in each PR, and we can focus on the important things.
Notes:

The Python version requirement introduced in https://github.com/unitaryfund/metriq-gym/pull/21 was too strict, I am now allowing patch versions of Python 3.12 – error was Current Python version (3.12.7) is not allowed by the project (3.12).  (cc @willzeng)
After this PR is merged we should all install the pre-commit hook as specified in the README
Files in /metriq_gym/hardware don't go through Ruff, because they are copied verbatim from https://github.com/qiskit-community/qiskit-device-benchmarking/ and the less we touch them, the easier it will be to keep them in sync with upstream (until we get to create our original versions of those benchmarks)

Great add!
Will Zeng
President
Unitary Fund - because evolution is unitary
Unitary Fund https://unitary.fund/ | Linkedin
https://www.linkedin.com/company/unitary-fund/ | X
https://x.com/home?lang=en | Discord
https://discord.com/invite/unitary-fund-764231928676089909
On Mon, Nov 11 2024 at 12:26 PM, Vincent Russo @.***>
wrote:

@.**** approved this pull request.
One minor request for longer line length for formatter but LGTM!
In pyproject.toml
https://github.com/unitaryfund/metriq-gym/pull/22#discussion_r1836994101
:

@@ -21,6 +21,13 @@ metriq-client = { git = "https://github.com/unitaryfund/metriq-client.git", bran
matplotlib = "^3.9.2"
qiskit-experiments = "^0.7.0"

+[tool.poetry.group.dev.dependencies]
+ruff = "^0.7.3"
+pre-commit = "^4.0.1"
+
+[tool.ruff]
Can we add:
line-length = 120
80 is annoyingly conservative
—
Reply to this email directly, view it on GitHub
https://github.com/unitaryfund/metriq-gym/pull/22#pullrequestreview-2427818773,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHZDAQYWPUGYMDV2XLVP4T2ADSEHAVCNFSM6AAAAABRSH5JV6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDIMRXHAYTQNZXGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Implement DNA builder

ds DNA is beyond the scope of polyply at the moment. Merging #150 will be as far as the current code goes.


Cannot test when QUnit is asynchronously loaded through RequireJS

This may be related to https://github.com/gruntjs/grunt-contrib-qunit/issues/19 but it looks different.
I've been using the QUnit RequireJS demo here, which successfully runs both in the browser and through this grunt task. However, when I modify that version to load asynchronously, it works in the browser, but not in Grunt.
I ran Grunt --debug and noticed the following error message halfway through:
[D] ["phantomjs","inject","C:\\Users\\C\\Desktop\\qunit-require-
master\\node_modules\\grunt-contrib-qunit\\phantomjs\\bridge.js"]
[D] ["phantomjs","error.onError","ReferenceError: Can't find variable: QUnit",[{
"file":"C:\\Users\\C\\Desktop\\qunit-require-master\\node_module
s\\grunt-contrib-qunit\\phantomjs\\bridge.js","line":14,"function":""},{"file":"
C:\\Users\\C\\Desktop\\qunit-require-master\\node_modules\\grunt
-contrib-qunit\\phantomjs\\bridge.js","line":58,"function":""}]]

If I attach logs to each function, it's clear that bridge.js is running before QUnit is fully injected.

See previous comment. Will close since issue seems to be resolved or invalid.

Update: I think the problem here was that bridge.js was injected into Phantom as a synchronous script, so it only worked when QUnit was loaded synchronously.
It looks like async functionality was added by this commit, which I'll have to try sometime.


[zh-cn] sync control-plane-node-communication deployment

content/zh-cn/docs/concepts/architecture/control-plane-node-communication.md
content/zh-cn/docs/concepts/workloads/controllers/deployment.md

/lgtm

/approve


[1.3.13] Module project file can include functions and permissions for 'other types'

 Issue by kbrandwijk
Tuesday Sep 12, 2017 at 14:22 GMT
Originally opened as https://github.com/graphcool/cli/issues/234

The project file can define hooks and permissions for Types that are not part of the module. This relates to how Types will be defined for modules, but I think a module should be self-contained. Every permission, rp hook or anything should be on a type that's part of the module schema.
Of course, that would require the Type merging from the other issue.

 Comment by timsuchanek
Wednesday Sep 13, 2017 at 09:20 GMT

In the current implementation, we don't do any checking at all. When  implementing the checks we should consider this

graphcool module has been replaced by graphcool add-template: #720.


Classname Select hides behind the Navigator

During the human race's perpetual battle with z-index, the ominbar's classname select menu fell victim to the navigator.

I love z-index PRs - almost as much as their inevitable sequels :D

More sequels than the Fast and Furious franchise :weary:


Auto-completion: Mark optional params

obtaining the default value of an optional param do not seem easy at all, but it's easy to identify if the param is optional. So off it goes! :balloon:

cc @andypetrella

indeed, very hepful.
Now, I think we need to check 2.11 because it looks like that it's not really working on this version :-S.
Not sure though :-)

this fixed travis builds for both scala 2.10 & 2.11.


[Frontend design] Federation experience - View Federation Relationships

Implement a view of list of federated servers:

A new route/ page at the top navbar for Federation (See Image below)
A sub link that shows Federation Relationships and another sublink to create a Federation Relationship
This issue focuses on the first sub link, which is viewing the already-created Federation Relationships
Use backend apis bundle show/list and federation list (See [here])(https://github.com/spiffe/tornjak/blob/82214acb79108329cc6e61c4e65231771dea6800/api/agent/server.go#L982-L990)

Helpful documents:
ppt on federation - https://ibm.enterprise.slack.com/files/WAJG4N7SP/F07NTKS7Y4F/24-06-06-spiffe.pptx
Documentation on creating federation using Tornjak based apis - https://github.com/maia-iyer/spire-demos/blob/main/tornjak_api_federation/README.md
Example code on how the agent, entry and cluster apis are deigned in the frontend

/assign @sestuna117


[FLUX] shuttle-3-diffusion (finetune/lora)

would finetuning or lora training work with this on sd3 branch?
https://huggingface.co/shuttleai/shuttle-3-diffusion

would finetuning or lora training work with this on sd3 branch?
https://huggingface.co/shuttleai/shuttle-3-diffusion

Hello, may I ask if you have succeeded?


RuntimeError: Class values must be smaller than num_classes.

Hello,
I am getting the following error message when running on GPU:
Traceback (most recent call last):
  File "/home/.../RoseTTAFold2NA/network/predict.py", line 345, in <module>
    pred.predict(inputs=args.inputs, out_prefix=args.prefix, ffdb=ffdb)
  File "/home/.../RoseTTAFold2NA/network/predict.py", line 225, in predict
    self._run_model(Ls, msa_orig, ins_orig, t1d, t2d, xyz_t, xyz_t[:,0], alpha_t, "%s_%02d"%(out_prefix, i_trial))
  File "/home/.../RoseTTAFold2NA/network/predict.py", line 233, in _run_model
    seq, msa_seed_orig, msa_seed, msa_extra, mask_msa = MSAFeaturize(
  File "/home/.../RoseTTAFold2NA/network/data_loader.py", line 116, in MSAFeaturize
    raw_profile = raw_profile.float().mean(dim=0)
RuntimeError: CUDA error: device-side assert triggered CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.

Or when running on CPU:
Traceback (most recent call last):
  File "/home/.../RoseTTAFold2NA/network/predict.py", line 345, in <module>
    pred.predict(inputs=args.inputs, out_prefix=args.prefix, ffdb=ffdb)
  File "/home/.../RoseTTAFold2NA/network/predict.py", line 225, in predict
    self._run_model(Ls, msa_orig, ins_orig, t1d, t2d, xyz_t, xyz_t[:,0], alpha_t, "%s_%02d"%(out_prefix, i_trial))
  File "/home/.../RoseTTAFold2NA/network/predict.py", line 233, in _run_model
    seq, msa_seed_orig, msa_seed, msa_extra, mask_msa = MSAFeaturize(
  File "/home/.../RoseTTAFold2NA/network/data_loader.py", line 115, in MSAFeaturize
    raw_profile = torch.nn.functional.one_hot(msa, num_classes=NAATOKENS)
RuntimeError: Class values must be smaller than num_classes.

Do you have any idea what might cause this and how to fix?
Thanks!

I got the same problem, I didn't find the solution yet.

Same here, though I'm getting @adimil 's 'CPU' error when I'm running on GPU:
RoseTTAFold2NA/network/parsers.py:116: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
msa[msa == "U"] = 30
Running on GPU
Traceback (most recent call last):
File "RoseTTAFold2NA/network/predict.py", line 374, in
pred.predict(inputs=args.inputs, out_prefix=args.prefix, ffdb=ffdb)
File "RoseTTAFold2NA/network/predict.py", line 250, in predict
self.run_model(Ls, msa_orig, ins_orig, t1d, t2d, xyz_t, xyz_t[:,0], alpha_t, same_chain, mask_t_2d, "%s%02d"%(out_prefix, i_trial))
File "RoseTTAFold2NA/network/predict.py", line 256, in _run_model
seq, msa_seed_orig, msa_seed, msa_extra, mask_msa = MSAFeaturize(
File "RoseTTAFold2NA/network/data_loader.py", line 118, in MSAFeaturize
raw_profile = torch.nn.functional.one_hot(msa, num_classes=NAATOKENS)
RuntimeError: Class values must be smaller than num_classes.

How do I fix the "Class values must be smaller than num_classes." error?
msa size: torch.Size([6142, 1064])
num_classes: 32
It looks like I need to either reduce the msa size or increase NAATOKENS drastically... that does not sound right?

Hello,  can you try the latest version?  This was a bug where 32 was hardcoded.  If this does not work, can you post your MSA?

@fdimaio I downloaded the package last week, so I just updated network/parsers.py and restarted predict.py.
I'm not getting the error from https://github.com/uw-ipd/RoseTTAFold2NA/issues/15
Running on GPU
Traceback (most recent call last):
File "RoseTTAFold2NA/network/predict.py", line 374, in
pred.predict(inputs=args.inputs, out_prefix=args.prefix, ffdb=ffdb)
File "RoseTTAFold2NA/network/predict.py", line 160, in predict
msa_i, ins_i = parse_fasta(a3m_i, rna_alphabet=is_rna, dna_alphabet=is_dna)
File "RoseTTAFold2NA/network/parsers.py", line 119, in parse_fasta
assert (np.all(msa<=31))
AssertionError

RNA MSA attached.
tRNA_Glu.afa.gz

@fdimaio something is amiss with parsers.py . I have checked that my RNA alignment only contains allowed characters:
perl -ne 'next if /^>/; print unless /[UCGA-]+/' tRNA_Glu.unfilter.afa
returns nothing. Sequences are fine.
I added a few debugging statements to parsers.py. This is the output:
Running on GPU
is RNA alphabet? True
max value : 89
largest values out of all rows :
[30 30 30 31 31 89 31 31 30 30 30 89 30 31 30 30 31 30 89 89 89 82 30 30
30 30 30 89 89 87 31 30 30 89 31 31 31 30 30 30 31 30 83 82 89 30 31 89
30 82 30 30 30 75 89 30 30 82 31 89 30 31 30 83 30 31 86 66 83 30 82 31
77 31 31 27]
File "RoseTTAFold2NA/network/parsers.py", line 125, in parse_fasta
assert (np.all(msa<=31))
AssertionError
How can a value in msa be > 31 when the alphabet array index ranges from 0 to 31?

Fixed this issue with a quick and dirty hack:
# remove RNA sequences with illegal characters from alignment
perl -ne ' if (/^>/) {$h = $_} else { if (/^[ NUCGA-]+$/i) {print $h, $_} }' my_crappy_RNA_file.afa  > tRNA_Glu.afa

now fighting https://github.com/uw-ipd/RoseTTAFold2NA/issues/13 ;-)


TypeError:

TypeError: undefined is not a function (evaluating '_styledComponents2.default.div(_templateObject)')
package.json -
"dependencies": {
"expo": "^25.0.0",
"prop-types": "^15.6.1",
"react": "16.2.0",
"react-native": "0.52.0",
"react-navigation": "^1.5.9",
"styled-components": "^3.2.5"
}
file -
import React, {Component} from 'react';
import {
    Platform,
    StyleSheet,
    Text,
    View,
    ListView,
    ScrollView,
    FlatList,
    Dimensions,
    Button,
    TouchableOpacity,
    TouchableHighlight,
    TouchableNativeFeedback,
    TextInput,
    WebView,
    Image
} from 'react-native';

import styled from 'styled-components';

class Authorization extends Component {

    render() {

        const div = styled.div`box-shadow: 10px 5px 5px black;`;

return (<Div/>)

}

node -v
v8.4.0
npm -v
4.6.1

On React Native we’re switching over to a different module which aliases and wraps all react Native components: https://www.styled-components.com/docs/basics#react-native
So instead of doc you would use View

Getting this error ---->
TypeError: styled_components__WEBPACK_IMPORTED_MODULE_2__.default.View is not a function
package.json -
"dependencies": {
"expo": "~36.0.0",
"react": "~16.9.0",
"react-dom": "~16.9.0",
"react-native": "https://github.com/expo/react-native/archive/sdk-36.0.0.tar.gz",
"react-native-error-boundary": "^1.1.0",
"react-native-web": "~0.11.7",
"styled-components": "^5.0.1",
"react-native-svg": "9.13.3"
},
import React from "react";
import styled from "styled-components";
const City = props => (

{props.text}

);
const Container = styled.View  margin-left: 5px;;
const Image = styled.Image  margin-left: 5px;   width:36px;   height: 36px;;
const Text = styled.Text  margin-left: 5px;;
export default City;

@anmol-raj getting the same error, did you find a solution for this?

I found the solution here: https://github.com/styled-components/styled-components/issues/1542#issuecomment-561023152
just import styled from 'styled-components/native';


[New WTFBin]: SenseIR Executes Encoded PowerShell

Contributor Name: Adam Ponce @adamcysec
Application/Executable: SenseIR.exe
WTF Behavior Description: Microsoft Defender Advanced Threat Protection uses SenseIR.exe to launch Powershell scripts that then uses .NET function [System.IO.File]::Open() to read another Powershell script into memory for execution. The second Powershell script executed has it's parameters passed in as base64 encoded text.
Link to Documentation of Behavior: I was unable to find detailed documentation for SenseIR.exe. I did find documentation indicating SenseIR.exe is a component Microsoft Defender for Endpoint.
Please provide any images for additional evidence.
The Powershell script executed by SenseIR.exe:

I've censored part of the base64 parameters as decoding the text would reveal sensitive info for my org.

& {
$OutputEncoding = [Console]::OutputEncoding = [System.Text.Encoding]::UTF8

$scriptFileStream = [System.IO.File]::Open('C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Downloads\PSScript_{76F8D82D-0DBC-45D2-B6DB-B948001BBB49}.ps1', [System.IO.FileMode]::Open, [System.IO.FileAccess]::Read, [System.IO.FileShare]::Read)

$calculatedHash = Get-FileHash 'C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Downloads\PSScript_{76F8D82D-0DBC-45D2-B6DB-B948001BBB49}.ps1' -Algorithm SHA256

if (!($calculatedHash.Hash -eq 'c2c9226f709e38f67c4777b7a5e0c6a2c40ae87076b65a5a02e846419b3e4ef7')) {
exit 323

}

Start-Transcript -Path 'C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Temp\PSScriptOutputs\PSScript_Transcript_{76F8D82D-0DBC-45D2-B6DB-B948001BBB49}.txt'

. 'C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Downloads\PSScript_{76F8D82D-0DBC-45D2-B6DB-B948001BBB49}.ps1' -ParamsAsBase 64 0 wIAAB + LCAAAAAAAAANMkMtyokAARf + FbaYj3XTTYFUWCKiooAQVcciigVYRAeURoyn / fRgzi1neqvs4db8FL2ZFwSut2tdCX / gOhVGbJqHQDwWRMsiosgM0JhxgFnOgiDwCSRzBCKuJzBIYCr9CwWbxIS249RPDmMRqFPNdIlPKZUKUzq7KiCc0iThElOAdS2j8f1QvO4a4Scui7jp + dxQG37H21IxYw6 / s1tl █████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████BK8sYaI7KX7gjVtxbuj83HtsQ3vNSQ611cZzr1gI91P1iDqjS3J0bRidTv03JpKntFzm4Te1Hw + sT5J9i5 + TvzRRV8fbd9e4NMiOy6xt3Gux8E6kjZzy / vaWUZ2N6eVd6rs8WJ9Vyb47F3m721Kp5MWkc3LthzNnEIp62BWZXwmN7a / tNfTyl5WvXfHEOXUi + █████████████████████████████████████████████████████████████ / nMHV7GWDVLY / H9fHIDustF7jm3rpu60mVlvqkKwpR / f6clsPXb70SnWhk4OqBXD / AsmqpM0wz4lZbOe2VrBqkF3xsUZuLpqLBkE63LZuGmXBlu3z1vUdS1bEyfXtTXj8AQAA / 8 DACOv3o / TAgAA -IsCompressed True
}

not sure it's wtf, that's how the RCE feature of their cloud-ish EDR is supposed to work. not pristine engineering, but how would you have it run custom powershell scripts & commands remotely without touching the disk ? (it's doable, but it's not my problem :D)

not sure it's wtf, that's how the RCE feature of their cloud-ish EDR is supposed to work. not pristine engineering, but how would you have it run custom powershell scripts & commands remotely without touching the disk ? (it's doable, but it's not my problem :D)

I pointed out the .NET code because i don't see .NET code used often in Powershell. $scriptFileStream uses .NET code to store a filestream, but then the filestream variable isn't used, so i don't fully understand why it's defined.
The more wtf feature is the encoded Powershell parameters. Normally we see encoded Powershell commands, but script PSScript_{76F8D82D-0DBC-45D2-B6DB-B948001BBB49}.ps1 actually defines a -ParamsAsBase64 parameter and contains code to decode the b64 parameters passed to it. Note the boolean parameter -IsCompressed indicates the b64 parameters are also compressed.

Thanks for your patience! Added in d83a37e

For the archives, the IsCompressed parameter indicates that the base64 payload ( a JSON usually, starts with ey ) is compressed. They use gzip with a 4-bytes uint32 header. You can spot the gzip prefix 1f 8b 08 00  00 00 00 00 00 03.
$ head -n 1 xx | base64 -d | dd bs=4 count=1 status=none | python3 -c 'import sys,struct;print(struct.unpack("<I",sys.stdin.buffer.read(4))[0])'
716
$ head -n 1 xx | base64 -d | dd bs=4 count=1 status=none | hd
00000000  cc 02 00 00                                       |....|
00000004
$ head -n 1 xx | base64 -d | hd | head -n 4
00000000  cc 02 00 00 1f 8b 08 00  00 00 00 00 00 03 4c 90  |..............L.|
00000010  4b 73 a2 40 14 46 ff 0b  5b 43 e8 07 cd c3 aa 2c  |Ks.@.F..[C.....,|
00000020  9a 87 44 a3 18 1f c9 a0  43 16 d8 dd 28 20 a8 80  |..D.....C...( ..|
00000030  82 a6 fc ef 43 9c 59 4c  d5 5d dc c5 fd be 73 ea  |....C.YL.]....s.|
$ head -n 1 xx | base64 -d | dd bs=4 skip=1 status=none | gzip -d | file -
/dev/stdin: JSON data
$ head -n 1 xx | base64 -d | dd bs=4 skip=1 status=none | gzip -d | json .
bash: json: command not found
$ head -n 1 xx | base64 -d | dd bs=4 skip=1 status=none | gzip -d | jq .
{
  "ScannerArgs": "{\"Guid\":\"someguidetc..
$ head -n 1 xx | base64 -d | dd bs=4 skip=1 status=none | gzip -d | jq '.ScannerArgs|fromjson'
{
  "Guid": "someguid2",
  "MachineId": "someid5",
  "MachineConnections": [
    {
      "DefaultGatewayMac": "00-00-0C-00-00-00",
      "AdapterId": "{someguid}",
      "NetworkNames": [
        "redactedad.example.org"
      ]
    }
  ],
  "ExpirationDateTime": "2024-11-14T13:50:38.7893268Z"
}
$

I've seen these JSON either contain one machine, or several IpsToScan. jq '.ScannerArgs|fromjson|select(.IpsToScan)|.IpsToScan|split(",")[]' -r.
Also, this is applicable for scripts under  C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Downloads\ , but there's also DataCollection running 1000 times ( literally ) more scripts, without parameters this time.


Armira's (multiple) changes

curtsies/init.py : updated version, meant to remove comment; will update soon
examples/chat.py : re-worded the print statement on line 68
examples/demo_fullscreen_with_input.py : added escape to avoid keyboard interrupt
examples/demo_input_paste.py : added escape to avoid keyboard interrupt
examples/demo_input_timeout.py : added escape to avoid keyboard interrupt
examples/demo_window.py : added escape to avoid keyboard interrupt
examples/initial_input.py : added escape to avoid keyboard interrupt
examples/initial_input_with_cursor.py : added escape to avoid keyboard interrupt
examples/snake.py : added "enter to start"; slowed down snake
examples/times.txt : updated automatically as a result of running other code

By the way, the failing test here is not your fault, I think we just have a flakey test.

This has been merged! I combined some of the commits but otherwise didn't change anything from this PR.


amp-geo sample

Docs: https://github.com/jpettitt/amphtml/blob/e58583e8d11e6a9a0a1e719fc3e2ad7dcf220020/extensions/amp-geo/amp-geo.md
Sample: https://github.com/ampproject/amphtml/blob/master/examples/amp-geo.amp.html

It's live.


causes permissions issue on servers

The yarn.lock file causes permissions issues on openshift clusters and prevents the build from executing. It was previously removed, still appears to be causing the same issue.

@mfrances17 it should be fixed with this commit: https://github.com/integr8ly/tutorial-web-app/pull/123/commits/6f80ba80db7e6ca3a75e18b8836385ab77c25116
could you try if it's now working please?

@mfrances17 was it the build from the yes-no-buttons branch (https://circleci.com/gh/integr8ly/tutorial-web-app/240)?
Because the fixing commit is not in that branch yet.

@dlabaj Ok, happy to take another look after the deadline.

@mfrances17 was it the build from the yes-no-buttons branch (https://circleci.com/gh/integr8ly/tutorial-web-app/240)?
Because the fixing commit is not in that branch yet.

I'm not sure what you mean. The build on OpenShift points to master, and I kicked off the build after your commits were in. Previous builds were ok once we deleted the yarn.lock file. It failed this morning. It's probably not fixed.

@pb82 Thanks Peter that would be great.  Here's the issue I created https://github.com/integr8ly/tutorial-web-app/issues/126.  Not sure why it keeps happening.

Thanks @pb82... I'm sure we'll figure it out eventually. Let me know if you want me to take a look, too.

@mfrances17 Ah sorry, you're right we only create the images from master after merging. In that case it's strange because I could see a successful image build after my PR. Anyway, i'll try to figure it out once we have more time.


[INLONG-3524][Manager] Add 'describe' and 'list' command

Title Name: [INLONG-3524][Manager] Add 'describe' and 'list' command
Fixes #3524
Modifications
Add 'describe' and 'list' command
Verifying this change
Usage: inlong-admin [options] [command] [command options]
  Options:
    -h, --help
      Get all command about inlong-admin.
  Commands:
    describe      Display details of one or more resources.
      Usage: describe [options]
    list      Displays main information for one or more resources.
      Usage: list [options]

@haifxu add bin/inlongctl to relate this module.


Upgrade Infinispan container image version to 14.0.22.Final for test-…

…infra module
Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

/component-test infinispan

/component-test infinispan


Warning: Set availability failed with response Rejected Project EV Apex 75

Good Morning,
I have got this integration setup, but I don't seem to get a current draw of power to the car show, also I keep getting notifications on HA saying Warning: Set availability failed with response Rejected
The availability and charge control work, but nothing else seems to be correct or updated.

can you check the HA logs and grep for OCPP messages?
$ grep ocpp  /config/home-assistant.log
Maybe the charger's firmware does not enable any measurands out of the box. If it doesn't, you might try the following:
go to developer tools  -> services
find: Open Charge Point Protocol (OCPP): Configure charger features
paste the following:
service: ocpp.configure
data:
ocpp_key: MeterValuesSampledData
value: Current.Import,Current.Offered,Energy.Active.Import.Interval,Energy.Active.Import.Register,Power.Active.Import,Power.Offered,Temperature,Voltage
If that works, you might want to create an automation which which re-applies it every time charger restarts

I seem to be getting the correct Power active now anyway removed and re-added but still getting Warning: Set availability failed with response Rejected everytime I activate the charger.
When i carry out what you stated i get

I have the same issue. I reinstalled the previous v0.5.5.


Feat: add support for replacing internal cert management

Signed-off-by: kerthcet<EMAIL_ADDRESS>
What type of PR is this?
/kind feature

What this PR does / why we need it:
Add DisableInternalCertManagement to Component Config as an option for end-users to choose whether to use the internal cert management or a third-party one like cert manager.
Which issue(s) this PR fixes:

Fixes https://github.com/kubernetes-sigs/kueue/issues/266
Special notes for your reviewer:
None

squashed

/hold cancel


add distribution

Sorry for the delay - is it possible you could rebase this PR?  Thanks
Otherwise I can merge it by hand.

Thanks, sorry for the delay - I resolved the conflict and merged


Gauntlet with combat enchants shows in weapons but not in mining tools

https://sky.shiiyu.moe/stats/AetherSword/Cucumber
The gauntlet should display both in weapons and mining tools, but in this case it only shows in the weapons section.
Maybe it's because it has weapon enchants?
Also


[Pages] Guidelines: Layout

Elements-Grid
A designer / developer can discover the new IDL Elements guidance for the 2x Grid as it relates to both Product and Editorial.
Design and Content

[x] Overview Tab: redesign layout and create/update and usage guidance

Bring over guidance from IDL 2x Grid page (actually same guidance as is on Carbon for TT)

[ ] Code Tab: Work in Progress (will probably be ghosted at launch)

Remove irrelevant or out of date guidance @joshblack
Add new guidance or expand on existing guidance @joshblack

[x] Images: update all exhibit images with new styles / create assets

Development

[ ] All Tabs:

Make sure we have components built to accommodate this layout (see issue: https://github.com/carbon-design-system/carbon-website/issues/293)
Nothing should be new here... just structured list and code snippet

Grid Elements v10
Sketch File
https://ibm.box.com/s/1s2zg8bdbsufd8usuk0h9kbqhb68ia5n

This Overview tab content was already updated for Carbon for the TT, it should be almost exactly the same; it's the only elements content that mirrors IDL site exactly
Grid code page is a work in progress between Chiu and @joshblack; will most likely be an inactive tab for launch

Image Exports
https://ibm.box.com/s/11efxwy2q5pjd4sskvyjj74c65bdjf4k

[Dev] todo:

[ ] Take out component spacers (those live on its own page "Spacing")
[ ] Update images, make sure they are the correct size as spec'ed above
[ ] Add in video examples

@carbon-design-system/ui


Update introduction.md

there was a typo (grammatical mistake)

@hanishtharwani123 please don't spam the repo. check the contribution guidelines & other open pull request before creating one

Typo and grammatical error are two different thing

Ok

Ok, understand
On Fri, May 26, 2023, 1:46 PM Gokulraj Puviyarasu @.***>
wrote:

Typo and grammatical error are two different thing
—
Reply to this email directly, view it on GitHub
https://github.com/wormhole-foundation/xdapp-book/pull/120#issuecomment-1563993641,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY6G57KLRLUYNQHBEL2EJBLXIBRELANCNFSM6AAAAAAYN2QUS4
.
You are receiving this because you were mentioned.Message ID:
@.***>


Reader not working

Hi,
I'm using a Wemos D1 and a RFID-RC522 reader.
If I use it with example program from Arduino IDE everything works well and stable.
Same wiring.
I can adjust everything in the WebUI.
No scanning in any log, no relay.
I already tested different versions.
How can I test more?

Tried again with new D1, worked.
No idea why.


Upload files >100mb

@cdmayer, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;


ReactDefaults ?

Current Defaults trait full fills general needs , what about ReactDefaults which contains react specific helpers .
trait ReactDefaults extends Defaults {

  implicit override def register: Register = ???

}

its good to have register which will prefix class names with react component name , at this moment i am not sure weather its possible or not!

I considered making a ReactDefaults but realised there was nothing in the defaults that needed changing.
Prefixing class names with the React component name is... I don't see how that's possible. In order to make that possible we would need to address the larger problem of best practices for styled generic components. How to solve that is unclear at this point. It would be best for us all to explore our own ideas in our different codebases and share experiences in, say, 2 months or so.
I'll close this for now; we can reopen in future.


Ignore checksums when gradle-versions-plugin is running

dependencyUpdates task resolves dependency updates, so it makes sense to ignore checksums when the task is active.

Fixed in https://github.com/vlsi/vlsi-release-plugins/commit/05f33550e41866c6e037d2e32b96174743e0b3ed


Refactor Endpoint API

Allow reads to complete immediately
Unify read/write signatures
Simplify memory management to allow future optimization work

@nicolasnoble - heads up

Reverted due to some build failures


check failed error when trainning on model Inception-v3 512x512

I followed the tutorial and succeed tranning a detector with my own dataset using VGG16_reduced 300x300. And I got the right result using  demo.py deploy.py evaluate.py so I think my data format and evrioment are correct. But when I extend the experiments to use model Inception-v3 512x512，"Check failed" error occurred.
The spot looks like this:
[11:27:41] C:\workspace\opensource\incubator-mxnet\src\io\iter_image_det_recordio.cc:281: ImageDetRecordIOParser: C:\workspace\opensource\mxnet-ssd\data\train.rec, use 7 threads for decoding..
[11:27:43] C:\workspace\opensource\incubator-mxnet\src\io\iter_image_det_recordio.cc:334: ImageDetRecordIOParser: C:\workspace\opensource\mxnet-ssd\data\train.rec, label padding width: 350
[11:27:45] C:\workspace\opensource\incubator-mxnet\src\io\iter_image_det_recordio.cc:281: ImageDetRecordIOParser: C:\workspace\opensource\mxnet-ssd\data\val.rec, use 7 threads for decoding..
[11:27:46] C:\workspace\opensource\incubator-mxnet\src\io\iter_image_det_recordio.cc:334: ImageDetRecordIOParser: C:\workspace\opensource\mxnet-ssd\data\val.rec, label padding width: 350
INFO:root:Start training with (gpu(0)) from pretrained model C:/workspace/opensource/mxnet-ssd/model/ssd_inceptionv3_512
[11:27:47] C:\workspace\opensource\incubator-mxnet\src\nnvm\legacy_json_util.cc:190: Loading symbol saved by previous version v0.12.0. Attempting to upgrade...
[11:27:47] C:\workspace\opensource\incubator-mxnet\src\nnvm\legacy_json_util.cc:198: Symbol successfully upgraded!
Using mxnet as:
<module 'mxnet' from 'C:\Users\owl\Anaconda3\envs\dl27\lib\site-packages\mxnet-1.0.0-py2.7.egg\mxnet_init_.pyc'>
Warning: using pre-installed version of mxnet may cause unexpected error...
(export MXNET_EXAMPLE_SSD_DISABLE_PRE_INSTALLED=1) to prevent loading pre-installed mxnet.
Traceback (most recent call last):
File "train.py", line 148, in
tensorboard=args.tensorboard)
File "C:\workspace\opensource\mxnet-ssd\train\train_net.py", line 354, in train_net
monitor=monitor)
File "C:\Users\owl\Anaconda3\envs\dl27\lib\site-packages\mxnet-1.0.0-py2.7.egg\mxnet\module\base_module.py", line 464, in fit
allow_missing=allow_missing, force_init=force_init)
File "C:\Users\owl\Anaconda3\envs\dl27\lib\site-packages\mxnet-1.0.0-py2.7.egg\mxnet\module\module.py", line 308, in init_params
_impl(desc, arr, arg_params)
File "C:\Users\owl\Anaconda3\envs\dl27\lib\site-packages\mxnet-1.0.0-py2.7.egg\mxnet\module\module.py", line 296, in _impl
cache_arr.copyto(arr)
File "C:\Users\owl\Anaconda3\envs\dl27\lib\site-packages\mxnet-1.0.0-py2.7.egg\mxnet\ndarray\ndarray.py", line 1876, in copyto
return _internal._copyto(self, out=other)
File "", line 25, in _copyto
File "C:\Users\owl\Anaconda3\envs\dl27\lib\site-packages\mxnet-1.0.0-py2.7.egg\mxnet_ctypes\ndarray.py", line 92, in _imperative_invoke
ctypes.byref(out_stypes)))
File "C:\Users\owl\Anaconda3\envs\dl27\lib\site-packages\mxnet-1.0.0-py2.7.egg\mxnet\base.py", line 146, in check_call
raise MXNetError(py_str(_LIB.MXGetLastError()))
mxnet.base.MXNetError: [11:27:54] c:\workspace\opensource\incubator-mxnet\src\operator\tensor../elemwise_op_common.h:123: Check failed: assign(&dattr, (*vec)[i]) Incompatible attr in node  at 0-th output: expected [84], got [8]
The parameters I use is shown below:
--gpus 0 --batch-size 16 --lr 0.001 --class-names head --num-class 1 --epoch 1 --network vgg16_reduced --pretrained C:/workspace/opensource/mxnet-ssd/model/vgg16_reduced --data-shape 512
This works fine. But when I change the network and pretrainedpath to
--gpus 0 --batch-size 16 --lr 0.001 --class-names head --num-class 1 --epoch 215 --data-shape 512 --network inceptionv3 --pretrained C:/workspace/opensource/mxnet-ssd/model/ssd_inceptionv3_512
Then I got the error above.
According to the error log, it is most likey that my num_class is not set correct. It used the origin model  of 20 detection classes instead of my own 1 class.
I checked the args after args = parse_args(), no problems.
I searched 0-th output in ssd_inceptionv3_512-symbol.json but nothing matched. And I searched output num 84 still found nothing.
My main doubt is either my parameters or the json config. I am new to mxnet and ssd, not that familiar with mx.symbol api, trying to print the args out. Anything would be helpful, thanks.

If you have different number of classes, we call it fine-tune task. You can checkout --finetune argument.
The reason is convolutional channel will need to be replaced to fit the new class numbers.

Thanks a lot! It works for me for now.
First I change the model name from mxnet-ssd/model/ssd_inceptionv3_512-0215.params to mxnet-ssd/output/exp1/ssd-0001.params, so as the .json file.
Then I used the parameters as below and no error occured
--gpus 0 --network inceptionv3 --data-shape 512 --class-names head --num-class 1 --batch-size 32 --finetune 1
I'd check the trained model and tell if this way trained model ok. Thanks again.

@zhreshold thanks,  it solved my question well.


Update home page

#228

@jag3773 Fixed. As a heads up, the old links came from the wiki, so maybe we also want to change the links there?

Instead of maintaining the separate Wiki page, can we have a persistent link to this page your creating?  If so, then I'd like to replace the link in the header for "About DCS" to point at that internal page.  Does that make sense?

The reason we didn't have a link to the home page before is because the Gogs (Gitea) router has the Home page only available for those who are not signed in. This would either require a change to the router (which I didn't make to avoid conflicts with upstream should anything change) or create another page like the home page, but that would mean two would have to be maintained still....

I'll merge this for now and create a new issue for the About page.


Save Data on Geodes

There are a lot of geodes that spawn if the option is set.Maybe we want to limit this to say 25 and needs to be at least 125 blocks out from spawn ?

Can do - or add a scaling config option (0-100% geode frequency). Then just do something like:
if (new (int)Math.round(Math.random()*100) > Config...geodeFrequency) { return; }
So at 50%, that means that half the geodes would spawn for example. Super quick and easy, don't have to persist any data etc

Plus, it means no matter how far out you go you can still find geodes, just like other structures/features

Done


[turborepo] baseUrl set in tsconfig/nextjs.json doesn't work in apps that extend it

What version of Turborepo are you using?
1.6.3
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Linux
Describe the Bug
I am moving a few Next.js projects to Turborepo and in those projects I am using absolute imports like this:
// project-root/tsconfig.json
{
  // ...
  "compilerOptions": {
    // ...
    baseUrl: "."
  }
}

In Turborepo, when I set baseUrl in packages/tsconfig/nextjs.json like above and extend it in the projects in the apps directory like this:
{
  "extends": "tsconfig/nextjs.json",
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"],
  "exclude": ["node_modules"]
}

The absolute imports don't work. They only work when I set it in the tsconfig.json of each project:
{
  "extends": "tsconfig/nextjs.json",
  "compilerOptions": { "baseUrl": "." },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"],
  "exclude": ["node_modules"]
}

Expected Behavior
For each project inside the apps directory to be able to use absolute imports when extending the tsconfig/nextjs.json package.
To Reproduce
Set baseUrl in packages/tsconfig/nextjs.json and try to use absolute imports in a project that extends it.
Reproduction Repo
No response

is the problem same? docs:build: error TS6053: File 'tsconfig/nextjs.json' not found.
why the file is not found

is the problem same? docs:build: error TS6053: File 'tsconfig/nextjs.json' not found. why the file is not found

Sorry, I don't understand what you mean.

This and baseurl simple doesn't work in packages. Only relative imports. Build fails if using absolute imports

Running into the same issue— seems like baseUrl isn't included when extending the base tsconfig.

This is an issue with the way TypeScript works rather than Next.js. Will close because of that.


Add 1.6 version

This patch adds the 1.6 version of the dashboards.

@amnonh please add a short explanation of Grafana tags in the README


Automatically select uploaded images

Problem:
When a user clicks to select an image from a field and uploads a new image, the uploaded image does not get automatically selected and the user has to search for it and select it. On a folder containing a lot of images, the only option is to use the search toolbar since they order alphabetically.
Solution:
When a user upload a single image, the preview modal could open and the user can select it with a single click.
If the user uploads more than one image, ideally all of them should be selected and shown in a modal for confirmation (like the same modal the user sees while uploading them)

Hi @miagg
Thanks for the idea, however it's not planned for the time being. We would love a PR for this though !
All the best,
Charaf

@miagg Have you since worked on this feature? I am currently in need of the same functionality.


format code

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: IanCao
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: zackbutcher
If they are not already assigned, you can assign the PR to them by writing /assign @zackbutcher in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @IanCao. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
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.

I signed it!

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: howardjohn, IanCao
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [howardjohn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@IanCao: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/e2e-bookInfoTests-trustdomain.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test e2e-bookInfoTests-trustdomain-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/e2e-bookInfoTests-trustdomain.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test e2e-bookInfoTests-trustdomain-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/e2e-bookInfoTests-trustdomain.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test e2e-bookInfoTests-trustdomain-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/release-test.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test release-test-master

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. I understand the commands that are listed here.

/test release-test-master

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/e2e-bookInfoTests-trustdomain.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test e2e-bookInfoTests-trustdomain-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/integ-galley-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-galley-k8s-presubmit-tests-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/e2e-bookInfoTests-trustdomain.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test e2e-bookInfoTests-trustdomain-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/integ-galley-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-galley-k8s-presubmit-tests-master

prow/release-test.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test release-test-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/e2e-bookInfoTests-trustdomain.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test e2e-bookInfoTests-trustdomain-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/integ-galley-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-galley-k8s-presubmit-tests-master

prow/release-test.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test release-test-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

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. I understand the commands that are listed here.

/retest

@IanCao: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

/ok-to-test

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-trustdomain.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test e2e-bookInfoTests-trustdomain-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/release-test.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test release-test-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-multicluster-e2e-master

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. I understand the commands that are listed here.

Looks like a legimiate test failure:
Flag --export has been deprecated, This flag is deprecated and will be removed in future.
apiVersion: authentication.istio.io/v1alpha1
kind: MeshPolicy
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"authentication.istio.io/v1alpha1","kind":"MeshPolicy","metadata":{"annotations":{},"labels":{"app":"security","chart":"security","heritage":"Tiller","release":"istio"},"name":"default","namespace":""},"spec":{"peers":[{"mtls":{"mode":"PERMISSIVE"}}]}}
  generation: 1
  labels:
    app: security
    chart: security
    heritage: Tiller
    release: istio
  name: default
  selfLink: /apis/authentication.istio.io/v1alpha1/meshpolicies/default
spec:
  peers:
  - mtls:
      mode: PERMISSIVE
error: error parsing /tmp/kubedelete515603622.yaml: error converting YAML to JSON: yaml: line 2: mapping values are not allowed in this context
authn_policy_test.go:49: command failed: "error: error parsing /tmp/kubedelete515603622.yaml: error converting YAML to JSON: yaml: line 2: mapping values are not allowed in this context\n" exit status 1

failure was fixed in another PR, was not related to this one
/test istio-pilot-e2e-envoyv2-v1alpha3-master

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-multicluster-e2e-master

prow/e2e-dashboard.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test e2e-dashboard-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-multicluster-e2e-master

prow/e2e-dashboard.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test e2e-dashboard-master

prow/e2e_pilotv2_auth_sds.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio_auth_sds_e2e-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-multicluster-e2e-master

prow/e2e-dashboard.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test e2e-dashboard-master

prow/e2e_pilotv2_auth_sds.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio_auth_sds_e2e-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

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. I understand the commands that are listed here.

/retest

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-multicluster-e2e-master

prow/e2e_pilotv2_auth_sds.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio_auth_sds_e2e-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-multicluster-e2e-master

prow/e2e_pilotv2_auth_sds.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio_auth_sds_e2e-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-lint.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-lint-master

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. I understand the commands that are listed here.

/test istio-lint-master

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-lint.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-lint-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-lint.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-lint-master

prow/racetest.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-racetest-master

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. I understand the commands that are listed here.

/test istio-lint-master

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/racetest.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-racetest-master

prow/istio-lint.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-lint-master

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. I understand the commands that are listed here.

/retest

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/racetest.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-racetest-master

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/racetest.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-racetest-master

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. I understand the commands that are listed here.

@IanCao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-new-install-k8s-presubmit-tests-master

prow/racetest.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test istio-racetest-master

prow/integ-mixer-k8s-presubmit-tests.sh
0695d4f60138454022e6dfa7647d0791105e31de
link
/test integ-mixer-k8s-presubmit-tests-master

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. I understand the commands that are listed here.

/test istio-racetest-master


FlatList when set horizontal={true} ,ItemSeparatorComponent can't be shown correctly

#
Is this a bug report?
Maybe yes

Have you read the Contributing Guidelines?
yes
Environment

Environment:
OS:  window 10
Node:  8.1.3
Yarn:  0.27.5
npm:  5.0.3
Watchman:  NO
Xcode: NO
Android Studio:  NO
Packages: (wanted => installed)
react-native: 0.49.3 => 0.49.3
react: 16.0.0-beat.5 => 16.0.0--beat.5
Target Platform: Android
Steps to Reproduce

(Write your steps here:)
1.Set <FlatList horizontal={true}/>
2.Use ItemSeparatorComponent={} set separator
Expected Behavior

I want to see the ItemSeparatorComponent is shown correctly!
Actual Behavior

if ItemSeparatorComponent has no height ,it won't be shown,

but when set height to ItemSeparatorComponent ,it will be shown below the data!

Reproducible Demo

demo:
let data = [];
for (let i = 0; i < 100; i++) {
  data.push({key: i, num: i});
}

space(){
    return(<View style={{height: 50, width: 2, backgroundColor: 'black'}}/>)
}

render() {
    return (
      <View style={{height: 50, backgroundColor: 'lightgreen'}}>
        <FlatList
          data={data}
          ItemSeparatorComponent={this.space}
          horizontal={true}
          renderItem={({item}) =>
            <Text style={{fontSize: 20, textAlign: 'center'}}>{item.num}</Text>
          }
        />
      </View>
    )
  }

This issue should be fixed with v0.50, see #15865.
Can you try it with the release candidate?

@dgruseck OK，I’ll try it later!


After the recent update yfinance stopped working on all servers

yfinance is not working correctly across all servers, some instances are returning the following error message.
return Ticker(ticker).history(period=period, interval=interval,

File "/home/alexanderzograf/.local/lib/python3.8/site-packages/yfinance/base.py", line 157, in history
data = data.json()
File "/usr/lib/python3.8/site-packages/requests/models.py", line 897, in json
return complexjson.loads(self.text, **kwargs)
File "/usr/lib/python3.8/site-packages/simplejson/init.py", line 518, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.8/site-packages/simplejson/decoder.py", line 370, in decode
obj, end = self.raw_decode(s)
File "/usr/lib/python3.8/site-packages/simplejson/decoder.py", line 400, in raw_decode
return self.scan_once(s, idx=_w(s, idx).end())
simplejson.errors.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

https://github.com/ranaroussi/yfinance/issues/764#issue-941000623


Use main_syntax variable to detect embedded syntax

Our syntax file can be loaded in two ways: as a top-level syntax (e.g. when we're in a 'graphql' buffer) and embedded within an outer ("main") syntax (e.g. within a 'javascript' buffer).
The syntax file has some conditional behavior when it's embedded (such as not setting syn sync), to avoid infecting the outer context.
We were previously using a custom b:graphql_nested_syntax variable to differentiate these cases. There is a more "standard" convention for this that uses a main_syntax global variable, so this change switches the code to use that approach instead.
This adds some additional housekeeping steps to our embedding procedure, so this change also introduces a graphql#embed_syntax() helper function that we now use in all of our filetype-specific syntax extension files.

See also:

#71
#72 (which wasn't setting main_syntax)
#73


Repeal the 'unofficial-' prefix

We are considering repealing the 'unofficial' prefix as documented at https://learn.microsoft.com/en-us/vcpkg/contributing/maintainer-guide#add-cmake-exports-in-an-unofficial--namespace
The original intent remains the same: we don't want to create 'vcpkg lock in' and expose things the same way things would be exposed from the system. However, since creating this policy, we have observed several upstreams adopt CMake bindings we authored for them wholesale, or ones substantially similar to ones we author. Once this happens, it creates its own kind of lock-in, as all customers who wrote the 'unofficial-' name effectively only work with vcpkg, creating the exact situation we were trying to avoid.
As a result, we are strongly considering removing this rule from the maintainer guide and replacing it with a general one saying, more or less, don't try to create lock-in and author CMake bindings and targets such that they would be adoptable upstream in outside-of-vcpkg-contexts if that upstream would so choose.
However, this is a major change in policy so we want contributors' opinion before proceeding. What are folks thoughts?
https://github.com/microsoft/vcpkg-docs/pull/376

/cc @dg0yt @Neumann-A @autoantwort @Osyotr @Thomas1664 @cenit @talregev @talregev

I like the idea because

all customers who wrote the 'unofficial-' name effectively only work with vcpkg.

I have a questions:

don't try to create lock-in and author CMake bindings and targets such that they would be adoptable upstream in outside-of-vcpkg-contexts if that upstream would so choose

This mean they will write targets in general way?
vcpkg will must wait for upstream approval?
Can we write in general way and suggest it to upstream without a must to wait for them?
This is effects only targets as I understand. All other patch that we do for upstream in vcpkg will remain the same.

This mean they will write targets in general way?

If it's possible to make bindings that work both inside and outside of vcpkg, that's preferred, yes.

vcpkg will must wait for upstream approval?

No. We are usually worried about making sure we don't 'speak for' upstream but we consider build system bindings and behavior kind of our table.

Can we write in general way and suggest it to upstream without a must to wait for them?

Of course it's always nice to give upstream an FYI but for adding build system bindings where they do not exist in the same places we would add unofficial ones, we would add ones without the unofficial prefix.

This is effects only targets as I understand. All other patch that we do for upstream in vcpkg will remain the same.

Yes. Basically, the farther away you get from build system specific edits the more we are going to want to see upstream in the loop.

This is effects only targets as I understand. All other patch that we do for upstream in vcpkg will remain the same.

Yes. Basically, the farther away you get from build system specific edits the more we are going to want to see upstream in the loop.

In addition to targets (unofficial::<PORT>::), this also affects package names (unofficial-<PORT>). Which is a major element in dependency resolution.

We are considering repealing the 'unofficial' prefix

I'm mildly against.
Basically, it is much worse to have hidden lock-in than to have obvious lock-in.
"unofficial" is a strong marker.
Considerations:

Most significantly, the vendored config packages are no longer easy to identify.
This will become a source of trouble when upstreaming CMake config patches for reverse dependencies. Regardless of being pushed from vcpkg or pulled by the projects.
As an extra complication, this is mostly an issue for static library linkage which is less popular in the POSIX-focused open-source world.
vcpkg strictly installs either static or shared libs. A uniform target name is desired and feasible.
In contrast, some projects prefer to install static and shared libs side by side. They can't use the same name.
Mitigation: Provide the uniform name as an ALIAS or INTERFACE based on<EMAIL_ADDRESS>Many contributors (and many upstreams) have difficulties in arriving at good choices both for package names and target names.
In particular, the value of namespaces and of qualifying as a drop-in replacement for official Find modules isn't understood.
vcpkg is biased to choose port names based on repo names. There is a significant number of ports where the package names or target names chosen by upstream does differ from the port name, e.g. by CapiTalization or lib prefixes.
It is fairly easy to move from unofficial to official names once upstream offers them.
It is fairly easy to provide polyfill in the ports.

This mean they will write targets in general way?

If it's possible to make bindings that work both inside and outside of vcpkg, that's preferred, yes.

vcpkg will must wait for upstream approval?

No. We are usually worried about making sure we don't 'speak for' upstream but we consider build system bindings and behavior kind of our table.

Can we write in general way and suggest it to upstream without a must to wait for them?

Of course it's always nice to give upstream an FYI but for adding build system bindings where they do not exist in the same places we would add unofficial ones, we would add ones without the unofficial prefix.

This is effects only targets as I understand. All other patch that we do for upstream in vcpkg will remain the same.

Yes. Basically, the farther away you get from build system specific edits the more we are going to want to see upstream in the loop.

I am vote in favor to that good change and remove unofficial and try to create changes that works inside and outside vcpkg.

What about all the ports that have unofficial targets?

to create changes that works inside and outside vcpkg

... they must be applied outside vcpkg.
That's my point: With "unofficial", I can tell that I cannot expect them to work outside. Without "unofficial", it will be try-and-error.

Once this happens, it creates its own kind of lock-in, as all customers who wrote the 'unofficial-' name effectively only work with vcpkg, creating the exact situation we were trying to avoid.

What is the problem here? If the lock in is a conscious decision it is ok. It is not your problem at that point any more.
What, however, will become your problem if you provide targets with conflicting names/namespaces. You don't now what is out in the wild and if any targets conflict with an already existing one it becomes a problem for you and the user. As such having some kind of vcpkg specific prefix is mandatory to avoid conflicts
The whole argument also feels survivorship biased. Have you looked at what conan and spack users do? E.g. you can take a look at something like https://docs.conan.io/2/reference/tools/cmake/cmakedeps.html#conan-tools-cmakedeps however wasn't one of the complains of conan the prefixed targets provided by conan?
I wouldn't mind if vcpkg would have an extra port similar to https://github.com/KDE/extra-cmake-modules providing the additional stuff and people make a conscious decision to lock in on vcpkg has a dep tool.
However, I also think that there is more important stuff like fixing FindPkgConfig for multi config. Nearly everything has pc files, so why not fix that?

From a user perspective, the use of the unofficial- prefixed CMake packages creates confusion for developers, distro maintainers, and hobbyists who want to maintain a 'pure system lib' build of a project that uses vcpkg for developer convenience. Especially if their distribution does not ship the dependency at all. Which leads us to consider providing a separate build script for those developers if they don't want to pull in an entire vcpkg build tree, and supply the system deps themselves...
I'm not sure if using vcpkg only for developer convenience rather than a library/application distribution strategy is the expected use case of vcpkg, but that's how we're using it. That is, run our script that builds a vcpkg install root for you instead of installing 20+ more system dependencies that may differ versions between distros. (And instead of using a docker container for most development, yuck).
As one example, the nixpkgs maintainer for our application opened a PR to specifically look for a dependency (skia) via a pkgconfig setup that they are maintaining themselves. https://github.com/LadybirdBrowser/ladybird/pull/382/files
It's possible that our interaction with the unofficial- package here is expected for skia though, as the upstream for skia seems to expect you to pull them in as a vendored package via gn or bazel files, rather than CMake :man_shrugging: .

Most significantly, the vendored config packages are no longer easy to identify.
This will become a source of trouble when upstreaming CMake config patches for reverse dependencies. Regardless of being pushed from vcpkg or pulled by the projects.

Example: In #40249, I patch mongo-c-driver to using unofficial-utf8proc. With the prefix, me and reviewers immediately know that this patch cannot be upstreamed.

thanks for adding me to the discussion.
In the past i'd have said forget the unofficial prefix and that's it (i wrote many CMakeLists.txt here and even modules originally [ffmpeg] that created target without any unofficial prefix). But others pointed out good arguments against it. I'd take the chance to discuss the topic on even a broader scale. For example, if not upstream-able for any reason, why not creating a cmake module and make it work also outside vcpkg environment, for better usage everywhere? just throwing random ideas to say that if we revisit this decision, let's consider it on the broadest perspective

But others pointed out good arguments against it.

Against using the prefix or against repealing the prefix?
(I fail to see strong arguments against using a prefix.)

why not creating a cmake module and make it work also outside vcpkg environment, for better usage everywhere?

cmake module (i.e not config): No.
Reason: Config mored provides the more powerful search procedure. This is strongly desired.
work also outside vcpkg environment: No.
Reason: Exported unofficial config is most useful due to encoding build-time configuration (dependencies, binary names, multi-config installation layout).

A find modules which chainloads suitable configs via
find_package(skia NAMES unofficial-skia nix-skia conan-skai system-skia)

might be a different story.

But others pointed out good arguments against it.

Against using the prefix or against repealing the prefix? (I fail to see strong arguments against using a prefix.)

against repealing the prefix. Sorry for the bad wording, the "but" at the beginning of the phrase was supposed to write something contrary to the previous phrase (that was against using the prefix).

why not creating a cmake module and make it work also outside vcpkg environment, for better usage everywhere?

cmake module (i.e not config): No.
Reason: Config mored provides the more powerful search procedure. This is strongly desired.
work also outside vcpkg environment: No.
Reason: Exported unofficial config is most useful due to encoding build-time configuration (dependencies, binary names, multi-config installation layout).

A find modules which chainloads suitable configs via
find_package(skia NAMES unofficial-skia nix-skia conan-skai system-skia)

might be a different story.

I know pros and cons of modules and configs. But instead of having a config that works only inside vcpkg because for whatever the reason it is not upstream-able, I think that a good designed module, that takes into consideration the possibility of offloading library search to config if available (because it detects vcpkg-custom-built libraries that export unofficial targets) and at the same time works also in case the library is provided in other ways, gives more value and might reach the same goals that @BillyONeal and the vcpkg team are targeting

We are considering repealing the 'unofficial' prefix

I'm against. This actually hides the problem but not solve it.
Maybe changing the unofficial prefix to vcpkg prefix is what we need.
I'm curious why vcpkg was not chosen as the prefix.
I agree with most of @dg0yt 's points

OK, we are convinced by @dg0yt and will not make this policy change. We should probably adopt a similar 'unofficial' policy for .pc files Soon :TM:


p2p: limit the number of routines(to handle new peers) during peer discovery

Initially proposed by @Wondertan :
We need to limit the number of possible routines. Some adversaries could create bots advertising them as "full" which would eventually over spawn the number of routines. The problem would also be visible on big networks in normal operation, but it is still there.
The easiest solution: just do a buffered throttling channel. Write to it once handling started and read on the finish. This way the buffer of the chan would be a limit of concurrent routines/handlers/connectors.
A bit more work, while more efficient is to preallocate a limited number of workers who rcv handling jobs from findPeers.
Supplement for #599

We rewrote discovery, and we now have a goroutine limit there, so closing
#2117


Update BlameableEventSubscriber.php

👋
This PR fixes deprecation on doctrine bundle.
1x: Method "Doctrine\Common\EventSubscriber::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "Knp\DoctrineBehaviors\EventSubscriber\BlameableEventSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.

Please let me know if I missed something, I'd be glad to help.

Thank you :+1:

Thank you :+1:


How to properly visualize hours on input field

i have this issue, the time is properly formatted but the value showed is not in 24h format...
how can i solve this?

Try providing dateFormat attribute with value as "MM/dd/yyyy HH:mm a" to DatePicker

@shreekeshmurkar this add PM but is not 24h (it would be better to see  e.g. 14:45

@justoverclockl I have tried providing value to dateFormat along with timeFormat and Got following DatePicker.

Is this you want ?

damn, is HH not hh.....thanks! i figured it out now :D


Make the configmap watcher a bit more robust.

If the channel got closed we silently dropped updates.

/test pull-tekton-chains-build-tests

/test pull-tekton-chains-unit-tests

/test pull-tekton-chains-integration-tests

/lgtm


Issue with pull, push and commit

Describe the bug
I created a new document in Insomnia designer and cloned a git repository. I switched to a branch and then created an API request. Now I am trying to push that onto my branch. As I click on push button it starts loading and remains same forever. Nothing get pushed. Also same problem with pull also. Also when I click on commit button it shows me nothing to commit.
To Reproduce
Steps to reproduce the behavior:

Create a new document with a git repository cloned to it
Checkout some branch other then master
Create an API request on debug mode of Insomnia designer
Now try to commit push or pull

Expected behavior
It should show me my changes on commit window and I should be able to push the changes.
Desktop (please complete the following information):

OS: Windows 10 pro 64 bit
Installation Method: Downloaded application for windows and installed Insomnia designer
App Version: 2020.3.3

Additional info to this issue:

git server is a self-hosted: GitLab
the branch is Not protected

Ah, self-hosted GitLab strikes again.
I merged https://github.com/Kong/insomnia/pull/2432 recently, and there is a beta release (2020.4.0-beta.4) coming hopefully tomorrow that includes this PR, which may help you debug. You can upgrade to the beta channel from Preferences if you'd like to try it, but please note this is beta and not stable.

Also when I click on commit button it shows me nothing to commit.

I find this to be the interesting one, as the git server shouldn't affect your ability to commit within the app.
Could you please try the following steps, with the console (View > Toggle Devtools > Console) open so that you can see git logs.

Create a blank document in designer
Create a request
Create a blank git repository in GitLab
Click "Setup Git Sync" in designer, and link your newly created repository
Commit -> this should show changes
Push -> you should see your commit in github

Please report back on findings 🎉

Also when I click on commit button it shows me nothing to commit.
I think this is related to the long time one have to wait to see changed requests like reported here: #2457

I think this is related to the long time one have to wait to see changed requests like reported here: 2457

Ah, gotcha. So you do, eventually, see changes in the commit dialog? You'll notice that I have put the accepted label on 2457, we'll get onto it when we get a chance.
In that case, with the upcoming beta release, please try those steps and report back. I'm hopeful that the additional logging that has recently been added will help to determine why push/pull isn't working for you.

Ah, self-hosted GitLab strikes again.
I merged #2432 recently, and there is a beta release (2020.4.0-beta.4) coming hopefully tomorrow that includes this PR, which may help you debug. You can upgrade to the beta channel from Preferences if you'd like to try it, but please note this is beta and not stable.

Also when I click on commit button it shows me nothing to commit.

I find this to be the interesting one, as the git server shouldn't affect your ability to commit within the app.
Could you please try the following steps, with the console (View > Toggle Devtools > Console) open so that you can see git logs.

Create a blank document in designer
Create a request
Create a blank git repository in GitLab
Click "Setup Git Sync" in designer, and link your newly created repository
Commit -> this should show changes
Push -> you should see your commit in gitlab, or an error message in console

Please report back on findings to help me reproduce it 🎉

yes It worked for me. Now I'll check again for my project. Thanks a lot

Its working If i create a new blank document. But it is not working if I create new API request in existing document which I synced from gitlab repository

Hmm, that's interesting. A couple of questions:

Could you provide any information on what your document looks like? A few/a lot of requests, how many commits in the repository, whether you created the repository or you cloned an existing repository with the .insomnia directory.

Since the reproduction steps at the top of this issue are now out of date, would you be able to try reproduce what you are seeing, with a new document, in order to help me reproduce the issue that you're seeing?

It feels like you've hit an edge case of some sort, that's not necessarily related to your git provider, and I'd really like to get to the bottom of it. Thanks, @gautamtyagi81!

Yes @develohpanda . I cloned existing repository in insomnia designer which has already around 80 API requests.

I created a new folder in which I created 2 API requests. I tried with just 1 commit. I tried to push in existing branch which was made during development and fetched in insomnia designer.
I did not create the repository. It is existing project in gitlab and I was given access. There is only one repository which we are using for code (in phpstorm) and for API requests (in insomnia)
I am trying to commit in a branch which I created from git bash and pushed to remote and checked out in Insomnia.
I tried it with the beta version you have mentioned but still getting same issue. I can commit the changes but can not push.

I delete my document and cloned the repository again. Then I added my requests and then commit
Commit goes fine but when I pushed then I got this error
TypeError: Cannot read property 'request' of undefined
at httpPlugin (file:///C:/Users/91989/AppData/Local/insomnia-designer/app-2020.4.0-beta4/resources/app.asar/bundle.js:175820:19)
at async Function.discover (C:\Users\91989\AppData\Local\insomnia-designer\app-2020.4.0-beta4\resources\app.asar\node_modules\isomorphic-git\dist\for-node\isomorphic-git\index.js:6453:15)
at async Object.getRemoteInfo (C:\Users\91989\AppData\Local\insomnia-designer\app-2020.4.0-beta4\resources\app.asar\node_modules\isomorphic-git\dist\for-node\isomorphic-git\index.js:8429:20)
at async GitVCS.canPush (file:///C:/Users/91989/AppData/Local/insomnia-designer/app-2020.4.0-beta4/resources/app.asar/bundle.js:33209:24)
at async GitSyncDropdown._handlePush (file:///C:/Users/91989/AppData/Local/insomnia-designer/app-2020.4.0-beta4/resources/app.asar/bundle.js:193521:17)

Hi
I wanted to do a test also on my side using the beta 2020.4.0-beta.4, but with this version as soon as I start ( fresh AppData Insomnia folder and fresh clone) when I want to commit all of the requests are set to changed to be staged and committed :-O and if I try to rollback nothing happens

when I want to commit all of the requests are set to changed to be staged and committed :-O and if I try to rollback nothing happens

I literally just came across this 😮
We've published 2020.4.0-beta.6 just now. I think there must be something curious with your repository, let me know if the new beta helps otherwise we'll need to dig further again to atleast try to reproduce this.

Hi, I'm getting the same error. Using a private repo but I'm able to pull code, just not push changes.

Hi @anthros-niccolo, do you see anything in the Developer Console when trying to push changes? (View > Toggle DevTools)

@develohpanda I'm running into this currently and can't push or pull any code to a private repo. My info:
Version: Insomnia 2021.5.3
Release date: 9/13/2021
OS: Darwin x64 20.5.0
Electron: 11.2.3
Node: 12.18.3
V8: <IP_ADDRESS>-electron.0
Architecture: x64
node-libcurl: libcurl/7.73.0 OpenSSL/1.1.1k zlib/1.2.11 brotli/1.0.9 zstd/1.4.9 libidn2/2.1.1 libssh2/1.9.0 nghttp2/1.42.0

And the error I'm seeing in the developer console tools:
[ErrorModal] TypeError: Cannot read property 'request' of undefined     at Object.request (bundle.js:130995)     at async Function.discover (/Applications/Insomn…-git/index.cjs:6559)     at async Object.getRemoteInfo (/Applications/Insomn…-git/index.cjs:9343)     at async GitVCS.canPush (bundle.js:87139)     at async GitSyncDropdown._handlePush (bundle.js:309511)

Hi @tom-at-bowntie! Sorry to hear that. Looking at the stack trace this appears to be an issue within the git library we use and in the past this has often been attributed to permissions issues. A few questions, as you don't see anything extra in the console logs:

Which git provider are you using?
Does sync work for you with a public repository?
With the same credentials, are you able to push to the same branch from git in the command line? (This should help identify whether the issue is within Insomnia or a permissions issue with your specific account/provider).

Hey @develohpanda!
Which git provider are you using?
A: I'm using github with a private repo. It had worked previously, and I had suspicions that it could be the dev-generated access token. I attempted to generate a new access token with full permissions and am encountering the same error.

Does sync work for you with a public repository?
I tried going through the setup git sync process again, and attempting to even link it is returning the same stack trace:
TypeError: Cannot read property 'request' of undefined     at Object.request (file:///Applications/Insomnia.app/Contents/Resources/app.asar/bundle.js:130995:27)     at async Function.discover (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/isomorphic-git/index.cjs:6559:13)     at async _fetch (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/isomorphic-git/index.cjs:7251:22)     at async _clone (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/isomorphic-git/index.cjs:7628:42)     at async Object.clone (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/isomorphic-git/index.cjs:7751:12)     at async Object.shallowClone (file:///Applications/Insomnia.app/Contents/Resources/app.asar/bundle.js:309737:5)     at async GitRepositorySettingsModal.onSubmitEdits [as _onSubmitEdits] (file:///Applications/Insomnia.app/Contents/Resources/app.asar/bundle.js:168922:25)
With the same credentials, are you able to push to the same branch from git in the command line? (This should help identify whether the issue is within Insomnia or a permissions issue with your specific account/provider).
I actually wanted to attempt to manually push from the CLI, but was unable to locate where in the MacOS filesystem the .insomnia directory was located for my project?

Thanks for that info! Did this start happening for you after a recent update of Insomnia, or just randomly now? I've tried with one of my repos and cloning seemed to work fine with the existing token I had, but I'll try a few more iterations.
Regarding the .insomnia directory, that folder doesn't actually exist on the file system. I was just wondering whether the credentials & token work outside of Insomnia.

Hello, I am also noticing issues with git pull in Insomnia. It's just stuck in 'loading' state and I cannot seem to update the branch:

Using macOS v12.3.1 with Insomnia:
Version: Insomnia 2022.4.0
Build date: 6/9/2022
OS: Darwin arm64 21.4.0
Electron: 18.1.0
Node: 16.13.2
V8: <IP_ADDRESS>-electron.0
Architecture: arm64

Hi @basarito
Do you see the same behavior with our latest release located here: https://github.com/Kong/insomnia/releases/tag/core%402022.6.0-beta.4

I am having issues with committing while having an spec in the Design tab. When trying to commit I get this error:
/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/yaml/dist/parse-cst.js:331 Uncaught (in promise) YAMLSyntaxError: All collection items must start at the same column     at Collection.parse (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/yaml/dist/parse-cst.js:331:24)     at /Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/yaml/dist/parse-cst.js:1605:29     at Document.parseContents (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/yaml/dist/parse-cst.js:622:26)     at Document.parse (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/yaml/dist/parse-cst.js:685:19)     at Object.parse (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/yaml/dist/parse-cst.js:1723:18)     at parseDocument (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/yaml/dist/index.js:43:24)     at Object.parse (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/yaml/dist/index.js:55:15)     at oP.stat (ne-db-client.ts:194:35)     at async FileSystem.lstat (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/isomorphic-git/index.cjs:4324:21)     at async status (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/isomorphic-git/index.cjs:13077:19)     at async git-staging-modal.tsx:106:22
If i remove the spec and only keep the debug and test content then committing works fine. This also still doesn’t work on Insomnia 2022.7.0-beta.5


[Automation] Generate Fluent Lite from eventgrid#package-2024-06-preview

[Automation] Generate Fluent Lite from eventgrid#package-2024-06-preview

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure.resourcemanager:azure-resourcemanager-eventgrid


implement auth service property for loggedIn state

should just return a boolean not an observable

Closed in https://github.com/schuldners-liste/app/commit/5bf73d85cbe18c6b06c0158c6a8d9db910d41863


change: [M3-8450] - Lower Events historical data fetching to 7 days

This PR is a replacement for https://github.com/linode/manager/pull/10785 which had become difficult to rebase.
It is essentially the same PR including fixes and cleanup for the new e2e tests.
Description 📝
This change optimizes Cloud Manager's event querying by reducing the historical data range.
Specifically, it limits the event query timeframe from the current 90 days to a more focused 7-day period.

This is true for the default Cloud Manager query that also populates the Notification Center
The /events page still queries 90 day and isn't affected by this PR

This adjustment aims to improve query performance and reduce unnecessary data retrieval while still providing relevant recent event information.
Changes  🔄

Previously we fetched the first 100 events but returned almost 500 results/records. These events pull from the last 90 days. Now we're returning events from the last 7 days.

Target release date 🗓
Next Release: 9/16/2024
How to test 🧪

[!note]
We are working to have this fully covered via E2E tests in an upcoming PR cc: @jdamore-linode

Prerequisites

Checkout branch and observe you network tab

Verification steps

Go to http://localhost:3000/events
Observe that initial load returns at most 25 events
As you scroll observe subsequent queries fetch next 25
Ensure there aren't any redundant events
Ensure you're able to reach the end of your events list (90 days worth of events)

As an Author I have considered 🤔
Check all that apply

[x] 👀 Doing a self review
[ ] ❔ Our contribution guidelines
[x] 🤏 Splitting feature into small PRs
[x] ➕ Adding a changeset
[x] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[x] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

@jdamore-linode is it worth adding an assertion to verify that the in-progress event is actually included in the response, to ensure that the increased polling rate is indeed triggered by the presence of an in-progress event? May not be necessary, but wanted to check

@jdamore-linode is it worth adding an assertion to verify that the in-progress event is actually included in the response, to ensure that the increased polling rate is indeed triggered by the presence of an in-progress event? May not be necessary, but wanted to check

@jaalah-akamai If these were end-to-end tests using real events we'd definitely do that, but we're already implicitly doing this since we're defining the mocked responses, and setting them up not to contain an in-progress event in one test and to contain an in-progress event in the other (which, iirc, is basically the only real difference between the two tests -- I think I literally copy/pasted them when I wrote them since we were in such a rush at the time, but in reality it might make sense to parameterize them or something since that might kind of highlight at a glance what the difference between the two flows is)

@jdamore-linode How do you feel about moving forward with either skipping the test for now until we have a better handle on it. We now have very few days for this to sit in dev and the only test issue seems irrelevant to the purpose of this PR