Publishing big files times out

The Issue
Youtube sync is struggling to publish certain big files due to the RPC call timing out on publish.
Usually the files that are being published are close to 1GB in size.
Steps to reproduce

Find a 1GB file to publish
Start publication
Fail publication after ~7 minutes (or even more at times)

Expected behaviour
The file should publish
Actual behaviour
After a few minutes the request is cancelled:
from ytsync:
DEBU[19:45:33] 5A3bDWI0rVI deleted from disk (/tmp/ytsync559635775/5A3bDWI0rVI/working-on-projects-drawing.mp4)
INFO[19:45:33] 5A3bDWI0rVI took 5m28.500751264s
ERRO[19:45:33] error processing video: publish error: Post http://localhost:5279: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
INFO[19:45:33] This error should not be retried at all
ERRO[19:45:33] Video failed after 1 retries, skipping. Stack: error processing video: publish error: Post http://localhost:5279: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

from lbrynet:
2018-06-15 19:40:36,309 INFO     lbrynet.daemon.Daemon:2152: Publish: {'claim_address': u'bG9aSaeUtm6i3Cs6A2F6tidAbmLcSCmztH', 'channel_id': None, 'name': u'working-on-projects-drawing', 'claim_dict': {'version': '_0_0_1', 'claimType': 'streamType', 'stream': {'version': '_0_0_1', 'metadata': {'description': u'\nhttps://www.youtube.com/watch?v=5A3bDWI0rVI', 'license': u'Copyrighted (contact author)', 'author': u'SirCrumble', 'title': u'Working on Projects{Drawing}', 'language': u'en', 'version': '_0_1_0', 'thumbnail': u'https://berk.ninja/thumbnails/5A3bDWI0rVI'}}}, 'channel_name': u'@SirCrumble', 'bid': Decimal('0.01000000000000000020816681711721685132943093776702880859375'), 'file_path': u'/tmp/ytsync559635775/5A3bDWI0rVI/working-on-projects-drawing.mp4', 'change_address': u'bG9aSaeUtm6i3Cs6A2F6tidAbmLcSCmztH'}
2018-06-15 19:40:36,454 INFO     lbrynet.daemon.Publisher:25: Starting publish for working-on-projects-drawing
2018-06-15 19:45:31,228 INFO     lbrynet.core.Wallet:1187: Send claim: working-on-projects-drawing for 0.01000000000000000020816681711721685132943093776702880859375: 080110011af301080112ab01080410011a1c576f726b696e67206f6e2050726f6a656374737b44726177696e677d222c0a68747470733a2f2f7777772e796f75747562652e636f6d2f77617463683f763d35413362445749307256492a0a5369724372756d626c65321c436f7079726967687465642028636f6e7461637420617574686f722938004a2968747470733a2f2f6265726b2e6e696e6a612f7468756d626e61696c732f354133624457493072564952005a001a41080110011a307d6b92ed1af44efda4bf60792098be9ed7e0f57db6ee2503d9885f7ad02f3cfb9b5849b80b398db034a06f6a59dd00ed2209766964656f2f6d7034
2018-06-15 19:45:46,130 INFO     lbrynet.daemon.Daemon:732: Success! Published to lbry://working-on-projects-drawing txid: 9ef15cc5702f45c09874eada2493db9ae1de8da673d699ee699e98b6f730bfd9 nout: 0
2018-06-15 19:45:49,013 INFO     lbrynet.daemon.Daemon:728: Reflected new publication to lbry://working-on-projects-drawing

After timing out there is no way to know whether the publication actually goes through or not. At times it does.
System Configuration
{
  "build": "release",
  "desktop": "Unknown",
  "distro": {
    "codename": "Xenial Xerus",
    "id": "ubuntu",
    "like": "debian",
    "version": "16.04",
    "version_parts": {
      "build_number": "",
      "major": "16",
      "minor": "04"
    }
  },
  "lbrynet_version": "0.20.0",
  "lbryschema_version": "0.0.16rc2",
  "lbryum_version": "3.2.2rc1",
  "os_release": "4.4.0-1052-aws",
  "os_system": "Linux",
  "platform": "Linux-4.4.0-1052-aws-x86_64-with-Ubuntu-16.04-xenial",
  "processor": "x86_64",
  "python_version": "2.7.12"
}

perhaps allowing the client to call publish and have it return immediately could solve the issue.
Obviously we would need a method to poll the daemon for publication statuses in order to understand when a video is published. (preferably a pub/sub channel too)

Sounds like https://github.com/lbryio/lbry/issues/854 is the fix for this too.
Can we isolate this to daemon load while publishing? Can you throttle down the # of concurrent publishes?

after some more digging we found out that this issue is unrelated to lbrynet. It seems to be a timeout parameter set in lbry.go which were' going to bump up now.


Epic Weaweworks

https://github.com/kubewarden/kubewarden-controller/issues/806
https://github.com/kubewarden/kubewarden-controller/issues/805
Figure out rate-limiting for artifacthub.io when we request info for policies
Blogpost

Rate-limiting for artifacthub.io:

UI does http request for every policy = 37 official + 4 unofficial = 41 requests when I click Create policy button
Artifacthub returns 429 Too Many Requests after 10 clicks...  > ~400 requests
Artifacthub then blocks requests for 75s, after which limit is reset
If we import all 144 weaweworks policies we will have 185 in total, which would trigger limit in 3 clicks

Considering this numbers I think we need to adapt UI as part of this.

Good reasoning @kravciak, let's talk about that with @jordojordo


[WFCORE-1209] validate operation request in BatchRunHandler to fix invalid attribute ignoring in batch

https://issues.jboss.org/browse/WFCORE-1209 "CLI did not throw any error message and just ignored the invalid attribute while using in batch mode.If we use same CLI command in non-batch mode it throws exception."
Move validateRequest() and replaceFilePathsWithBytes() into Util class to allow BatchRunHandler validate operation request in BatchRunHandler as OperationRequestHandler does.

@aloubyansky please approve

Looks good to me, thanks!


Runtime: add runtime version, set it to 1

Refs #720
The corresponding compiler PR is https://github.com/globalizejs/globalize-compiler/pull/34
I did it this way so that if you're directly using compiler.compile, it'll work without changes.
The compiler will also work without the change in globalize.js.

I'm closing this PR, because https://github.com/globalizejs/globalize/pull/719#issuecomment-404961144 was solved using an approach that doesn't require this. Thanks a lot and sorry for the delay.


hub pull-request default base branch should be the same as in the web interface

after creating a pull-requestwithout explicitly give the branch name it creates using base master and my default branch to create PR using the web interface uses base develop. shouldn't it use the same default branch option?

Please see https://github.com/github/hub/issues/814#issuecomment-75489117

Closing as duplicate of the above issue


get_facets behavior

get_facets needs to behave much more like query in that if you give it :fqtext / fqfield etc combinations it will build your query for you.
Also verify that facets => true does not have to be hand entered each time using get_facets, but that may be due to configuration of the app that I am using.  Investigate that.
Perhaps also look into a way of getting both a query and facets at the same time rather than sending two requests, though it would change the response format for query a bit, though not too much hopefully.

facet => true just needs to be changed to facets => "true" to work
but now "facet.mincount" => "1" and "facet.limit" => "-1" are not being defaulted in another project so there is still something weird going on

I believe this ended up being due to a symbols vs strings merging mixup, and should be good to go on the latest branch (not testing, just lazily closing since I'm the only one using this repo)


Getting Instruction access fault

BUG DESCRIPTION
I am developing a custom application for porting the firmware from Renesas to Zephyr-based ESP32C3. I am facing the runtime error after some parts of the code execution.
 You need to edit this issue to include the information requested in https://github.com/zephyrproject-rtos/zephyr/blob/main/.github/ISSUE_TEMPLATE/001_bug_report.md


(Chroe) setup verson number in fullstory

add version to fullstory in analytics.js

@sirpy current version of the app from package.json?

see how its done in other analytics

@sirpy we already set the version to the logs in analytics.js line 71. Amplitude.setVersionName(Config.version).
Config.verion is defined as - process.env.VERSION || 'v0',

@sirpy
the solution for this task is:
in analytics.js at line 87 add appVersion prop in userVars object (second argument)
FS.identify(emailOrId, { appVersion: Config.version })
Here are docs for Fullstory's identify method - https://help.fullstory.com/hc/en-us/articles/360020828113-FS-identify-Identifying-users

ok


format java, xhtml files (2 spaces as tab)

https://jenkins.ivyteam.io/job/ivy-project-demos/job/feature%252Fformat/


gpio issue in 1.1.6 and no gpio-node in 2.0.0-pre

This is the gpio-node in version 1.1.6, after deploying it pops up Error: node not deployed.
When I use version 2.0.0-pre, there's no gpio nodes. What's wrong with it? Did I screw up?

The dir, SmartNode/node-red/node_modules/node-red-contrib-smartnode/gpio, does exist.

Which verison of system you use? You can just paste the name of system image here.
And also tell me your hardware, is it the breakout board(small one), or the board for arduino(big one)?

Linux Username 3.10.17-poky-edison+ #1 SMP PREEMPT Fri Jun 19 12:06:40 CEST 2015 i686 GNU/Linux
I'm using the big one.

Maybe because the mraa version 0.9.0 is too old, I try upgrade to the newest 1.6.1, some other nodes disappear, but 1.5.0 works fine.

Looks like your system image is too old, you can download the latest image from this page: https://software.intel.com/en-us/iot/hardware/edison/downloads.
and you can find the download link on Intel® Edison Module Firmware Software Release 3.5
->Latest Yocto Poky image* at the middle.
Please try upgrade system version and reinstall the lastest smartnode :)

I try upgrade the latest system image, and install the latest stable smartnode(http://repository.smartnode.io/download/Stable/SmartNode-2.0.0-pre.install), GPIO comes back! Thanks so much.
However, in Neural Networks,  multiInData, dataCollect and ouputJudge is lost :（


How to remove prompt in promptless CN

I am trying to do promptless training for ControlNet.
I am wondering what is the correct way to remove the prompt during model training on my dataset.
I need to train it for image2image task with conditional image
Should I pass empty string here?

or should i remove it completely from RETURN statement?

@williamyang1991
@lllyasviel
@eltociear
@camenduru

Original ControlNet paper: "In the training process, we randomly replace 50% text prompts ct with empty strings. This approach increases ControlNet’s ability to directly recognize semantics in the input conditioning images (e.g., edges, poses, depth, etc.) as a replacement for the prompt."

I have read this, but how to do it?
should i provide a json file with 50% empty string?
Also, i want to experiment when all prompts are empty, do not know if that possible using the way that i have sent?
@geroldmeisinger

line 23: prompt = random() >= 0.5 ? "" : item['prompt']

this line of code gonna replace 50% by random string? what does it (random) mean here?
Also, if i am trying to remove the prompt completely-> replace 100% of prompts by empty string! can i do the same by changing the number from 0.5 to 1.0? i want to see the results if i remove the prompt...
@geroldmeisinger
@williamyang1991
@scarbain
@lllyasviel

50:50 chance to use empty string
how long does it take for you to train a controlnet? couldn't you just try?
did you already successfully train a controlnet without "extras"?

actually it takes long time each epoch takes about 6h, so i stopped it with epoch25. I do not know why it takes this a lot of time? despite that i am using GPU

How many epochs does it have?

So i can understand that, if i replace 0.5 with 1.0 that means 100% chance of using empty string? please confirm for me if i understand you correctly.

@geroldmeisinger

Hi,I wonder what does prompt.json look like,I didn't seen this file in the repository. Because my dataset doesn't have prompt..

@KhawlahB
Hi， Any conclusion of the question?

Also, if i am trying to remove the prompt completely-> replace 100% of prompts by empty string! can i do the same by changing the number from 0.5 to 1.0? i want to see the results if i remove the prompt...


Support env memory overrides to start-tc-server (daggy 4.3.10)

Currently -Xms2g -Xmx2g is hardcoded.

In discussion with Gary, we're having second thoughts about this...
I'm re-checking with the gateway team about what problem they were having with using JAVA_OPTS , which should override the hard-coded value.


What if the detection doesn't work?

I think you should provide a link to what to do or how to troubleshoot if the detection doesn't work. I just setup ATP and the detection hasn't worked on two different machines. The detection command in the onboarding when run in powershell (disappears as it should) but nothing gets reported to the portal.
Please provide some links or documentation to troubleshooting these kinds of issues.

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

ID: e1a58ecc-aa01-3b7a-c1f7-a039063c7c38
Version Independent ID: b1b9a0ef-fd7e-96e2-730d-01158fb93eee
Content: Run a detection test on a newly onboarded Microsoft Defender ATP device - Windows security
Content Source: windows/security/threat-protection/microsoft-defender-atp/run-detection-test.md
Product: w10
Technology: windows
GitHub Login: @mjcaparas
Microsoft Alias: macapara

Hello @pctsltd ,
there is no article in Microsoft docs that helps to troubleshoot the described issue.
I would recommend to create a topic in Microsoft Support portal.
Thank you

Closing via #8078


remove 'Scenario: ' prefix from expected output

This is related to the PR #82 in cucumber-ruby-core that addresses issue #768.
Test::Case#name was changed to only output the name of the Scenario or Scenario Outline, not "Scenario: name"
This PR changes the expected output to reflect that change.  As noted in the other PR, I think this makes the output more compact while still being meaningful, but I could also prepare a change to keep the existing behavior in cucumber.
This PR will most likely fail the Travis build, as it's dependent on the other PR in cucumber-ruby-core.

Thanks! Shall we try getting the build to pass as we discussed?
I was thinking that we could add some extra logic here to use a branch for fetching the core if:
ENV['CI'] == true

and
`git rev-parse --abbrev-ref HEAD` != master

The name of the branch could, as you suggested, be conventionally the same in both PRs. Will that work, do you think?

To remove the keyword form the listing of failing scenarios, will make the behavior of Cucumber v2.0 different from Cucumber v.1.3.x with respect to this (feature from v1.3.x). As the general idea of Cucumber v2.0 is to be backward compatible, isn't it better to still include the keyword in this listings?

Discussion here: https://twitter.com/mattwynne/status/563597525446569984

Yes @brasmusson you're right.

The change will need to be somewhere in the https://github.com/cucumber/cucumber/blob/master/lib/cucumber/formatter/legacy_api/adapter.rb to prepend the keyword to that string.

Is the Ast Facade the correct place?
https://github.com/cucumber/cucumber/blob/master/lib/cucumber/ast/facade.rb#L67
I think we might need to expose keyword on the test case?

@mattwynne I'll try some things in here and see if there is an extra check that will resolve the gem from git by branch name.  If it it works, I think it could be pretty nice.

On the test case output, it seems like maintaining existing behavior is important.  I think I can work on that.

@mattwynne - I was trying to add the branch dependency to get this passing as currently committed.
I think I was incorrect about the context Travis-CI uses to run the build.  I thought maybe I had a good way to get the PR owner/creator (in this case me), but I'm not sure if that's available once the build script is running bundler.  I don't think that's available from the git command at this point.
I wonder if travis-ci knows the name of who submitted the PR and happens to expose it in an environment variable.
As is, this doesn't work yet.

@richarda for now, I'd say just change the git URL in the Gemfile to point to your fork / branch, and see if that makes it work. We can always revert that commit before merging this PR.

@mattwynne This got a little messy.  I can clean up the commits when this is finished, but for now, if you run these two branches locally, the tests should pass.  I'm having trouble getting the Travis build to pull from my fork / branch.
More to the point of all this, looking at the net changes, there a few simple changes and some new unit test expectations that seem to implement the original request and maintain backward compatibility.

@mattwynne I reacted too quickly.  There aren't any build issues.  I needed to updated my core fork to meet the 1.1.0 version dependency in the cucumber Gemfile.  So the real discussion is probably about the changes in this commit.
Do you think there is a better way or a better place to format this string?
There are no changes to any tests because we are maintaining existing behavior for backwards compatibility.
And you won't want the commit that changes the Gemfile.

Closed by ebb08f73ff2f83a061ccf214c0b52c08016b1655


Make a backup copy of all the METS in the METS file share

Because the METS got modified by the bagger, we can't do a byte-for-byte check that every METS file got uploaded correctly. We could do an in-depth check, but that's a lot of work to cover what seems like an unlikely scenario.
We do have some indications that the METS survived the transformation with the important bits intact:

We compared the IIIF presentation manifests of every bag, and they all matched
We know the correct bags were created
We know the METS/ALTO references are internally consistent (#4289)

So the plan is to compress all those files up (they should compress fairly neatly) and stick them in an S3 bucket with some notes about what they're being kept for. If and only if we discover there was an issue with the bagger, we can go back and do the more in-depth work to patch it from the pre-migration METS.
Over time the two will gradually drift apart; in a couple of years we can delete those backup copies – we're assuming that any issues will have been exposed by then.
For #4187.

Done!


Add Bluemap support like Dynmap

Bluemap is like Dynmap and is a new project that seems to be much lighter on the resources. I've been using it for local testing and it's been great. Would a PR be welcomed in the coming weeks to get this added to the chart in the way DynMap is?

That sounds great.

Technically, the "dynmap support" is just an ancillary service & ingress and would universally work with anything which requires another port.
Just set your minecraftServer.dynmap.containerPort and minecraftServer.dynmap.service.port values from the default 8123 to 8100.

Right, would it make sense to just do some clever renamings?

Right, would it make sense to just do some clever renamings?

Yeah, I'm sure we could essentially just find and replace the word dynmap with something a little more generic. It doesn't affect functionality for now though.

Hey @hyperbolic2346, I just remembered we pondered in #37 whether we should go generic or dynmap specific. Now a second scenario has showed up to tip the other way, so I'm wondering if you mind a renaming/repurpose of the changes added in #38 or add generic container port, service, and ingress declarations alongside dynmap?

@itzg I agree that a generic approach would be useful to support something other than just dynmap.  Do you think it's likely that we would need to consider more than one of these extra things being used at a time?
Making it support n-number of additional sidecars/services/ingresses introduces a lot more complexity IMO.
Perhaps we look to make what we have use a more generic name (as you suggest above) and wait to consider supporting multiple concurrent sidecars until they are needed?

For what it's worth, and to @billimek point bluemap is supporting running it outside of your game server i.e server/plugins like in a sidecar though the quality isn't as great yet (can't see live players last I checked).
https://github.com/BlueMap-Minecraft/BlueMap/wiki/Directly-hosting-BlueMap-with-external-webservers

For what it's worth, and to @billimek 's point bluemap is supporting running it outside of your game server i.e not server/plugins like in a sidecar though the quality isn't as great yet (can't see live players last I checked). Also doesn't have a container yet
https://github.com/BlueMap-Minecraft/BlueMap/wiki/Installation#on-the-cli--standalone

I think building a container for Bluemap would be out of the scope of this project, but I'm sure a feature request could be opened to support it once it exists

I agree. Just a generic service in the chart here would suffice.


why isn't coverage working?!

@rogelioLpz could you investigate why coverage isn't working properly?

Already fixed


Pending Scan Logic in Mac Class Interferes with Any Active Scan

In Mac::Scan if the state isn't currently kStateIdle then it ends up setting the mPendingScanRequest variable which will be used after the current task is complete.
It also sets all other mScan* variables which could currently be in use by a different scan. I believe all those variables need to be duplicated to save for the pending scan, and then copied to the active scan variables when it is no longer pending.
Additionally, if either of the scans are started twice while a not kStateIdle the second scan will overwrite the pending variable state.

In my reading of Mac::Scan, the following checks are performed before making any side effect:

mState is neither kStateActiveScan nor kStateEnergyScan (i.e. a scan operation is not currently in progress.
mPendingScanRequest is kScanTypeNone (i.e. a scan operation is not currently pending).

Can you detail the code path that would lead to conflicts?

Ah, you are right. I looked for a state check in openthread.cpp, but somehow glanced over the first lines of Mac::Scan. Sorry for the false alarm.


Download Appium Logs using API or CLI

I am running appium test from Azure DevOps in Appcenter, After the test is completed I want to download the Appium logs from App Center. Any API or CLI is available to download the Appium Logs from AppCenter

Hi there 👋
Have you tried the command appcenter test download? You can download the test report by using this command.

i tried appcenter test download, but i am getting the appium logs i am triggering and found API to get the mobile logs but couldn't find the logs for Appium

using this API i was able to get the links to download the logs related to Test that I ran
https://api.appcenter.ms/v0.1/apps/{owner_name}/{app_name}/test_runs/{test_run_id}/report


[Feature]: Save-EvergreenApp add Custom Useragent for Custom Apps

What is your feature request?
There are some packages which block a automated download via powershell and  so the save-evergreenapp function. For example Filezilla.
Invoke-WebRequest (gea Filezilla).URI
Invoke-WebRequest:
403 Forbidden
When giving the useragent for IE for example, download works:
Invoke-WebRequest (gea Filezilla).URI -UserAgent ([Microsoft.PowerShell.Commands.PSUserAgent]::InternetExplorer)
So it would be nice to add a function to give a custom useragent to the function, and specify this in the app manifest :-)
Have you tested against the current version?

[x] Yes, I've updated Evergreen and tested against the current version.

Have you reviewed the documentation?

[x] Documentation at: https://stealthpuppy.com/evergreen/

Done. Available in 2212.709

nice thanks a lot :-)


Implementation of ECU Reset method

Implementation of the ECU reset service and its container and method factory classes.

Basic code has been written. The current test ODX file lacks any reset specified other than hard reset, so the testing has currently been limited to that - this should be fine for all other reset types other than enableRapidPowerShutDown - this latter type has an extra parameter return (powerDownTime), which has currently not been tested.
Currently includes the basic positive test cases to cover hard reset with or without response suppression, and positive testing of the negative response cases. Negative test cases (e.g. handling of an invalid negative response), has not been added yet (currently considered low priority).

Requires a fix for enablePowerShutDown handling - doing this next.

help


Unable to debug "ERR_BAD_SSL_CLIENT_AUTH_CERT"

Trying to sign in to Mattermost Desktop using Smart Badge with certificate. I'm getting the following error message:

I've tried debugging via Developer tools for application wrapper and current server but neither return any useful details. Security sections are all showing items as valid.
Sign in works fine from Chrome. How can this be debugged and fixed?

@Willyfrog @lieut-data @devinbinnie @jgilliam17 this seems to have started around https://github.com/mattermost/desktop/pull/1169. Ideas?

is this with the latest version?
that code is for handling certificate problems, do you see any error being raised or in the console logs?

@Willyfrog yes this is with 4.5.0. I do not see any further errors in Developer tools for application wrapper and current server. Should I be looking for logs somewhere else?

if you look where the config is saved (depends on OS and install method), there might be some extra logs.
Do you get a dialog like the one shown here: https://github.com/mattermost/desktop/pull/1148#issuecomment-575390778
in the network tab, are there differences between the one on the desktop (current server) and the one on chrome?

@Willyfrog Yes...

then get prompted for PIN
then get

App Wrapper dev tools show

I found a file at %localappdata%\programs\mattermost-desktop with [0619/183653.213:ERROR:registration_protocol_win.cc(131)] TransactNamedPipe: The pipe has been ended. (0x6D). Not finding any other logs with details in meaningful details in C:\Users\xxxx\AppData\Roaming\Mattermost

A couple of things to try:

disable antivirus/firewall and try to connect. if it does connect, you'll need to configure it to allow SSL connections with mattermost app.
go to the APPDATA/Mattermost directory and remove anything that is not a *.json file. that way you'll keep your config but remove any cached data that might be corrupted.

@Willyfrog I will try the troubleshooting ideas in the morning. In the mean time worth noting it used to work but I'm not sure the exact version nor if it's strictly caused by a new version or something else . Also worth noting is that only smart badge login fails and I can still login using using username and password. Many people in my company have reported the same issue. The hidden URL isn't a Mattermost server URL but rather the URL that processes the certificate for authentication. The only reason I called out #1169 is because it looks to be recently changed code related to certificate auth.

FYI there is a similar report here https://github.com/mattermost/mattermost-server/issues/14863.

@Willyfrog

disable antivirus/firewall and try to connect. if it does connect, you'll need to configure it to allow SSL connections with mattermost app.

Disabling this is prevented on my system.

go to the APPDATA/Mattermost directory and remove anything that is not a *.json file. that way you'll keep your config but remove any cached data that might be corrupted.

Still not working

did it work previously? (which versions? any 4.4.X?)

I uninstalled and starting installing versions going backwards until I found one that works. Works in 4.3.2 but 4.4.0 does not work.

what makes you think it is related to #1169 ?

Added in 4.4.0 but could be unrelated.

@Willyfrog @amyblais this is causing issues for a significant number of users for us. How can we help get this prioritized? Note about this worked in 4.3.2 and stopped working in 4.4.0.

The dev team is working on investigating this,

@bbodenmiller would you be open to run one of the versions found here: https://app.circleci.com/pipelines/github/mattermost/desktop/1329/workflows/388b9766-3df9-4ce5-a927-5dc651db4e6e/jobs/6845/artifacts
it has a small fix (which might help or not with your problem) and some extra logging around the process of authenticating via client certificate so it would be great to run it from a terminal (let me know if you need any help with that)

@amyblais thank you! @Willyfrog can do in ~12 hours or so.
How would I go about running it from terminal? I normally run setup exe so I assume you mean just unzip files and launch Mattermost.exe from command prompt so we can get logs to command prompt?

@amyblais thank you! @Willyfrog can do in ~12 hours or so.
How would I go about running it from terminal? I normally run setup exe so I assume you mean just unzip files and launch Mattermost.exe from command prompt so we can get logs to command prompt?

Yes, also make sure you have exited any other mattermost app before running this one.
Bear in mind that the logs will contain sensitive information, so feel free to contact me on the community server to send them

i've created this PR which doesn't show the certificate request if there is only one valid certificate: https://github.com/mattermost/desktop/pull/1354
can you check if this one works? you can find a build in the artifacts section of circleci's build: https://app.circleci.com/jobs/github/mattermost/desktop/6908

@Willyfrog that test build works! Verified on two machines. Just to make sure nothing else changed I also verified that https://app.circleci.com/pipelines/github/mattermost/desktop/1329/workflows/388b9766-3df9-4ce5-a927-5dc651db4e6e/jobs/6845/artifacts still does not work on those machines as well. So it seems something must be flawed in the current handleSelectCertificate logic? 🤔 Also I think the UX is better when it doesn't prompt for cert if there is only one... but I imagine you want to solve the issue such that selecting does work when needed.

but I imagine you want to solve the issue such that selecting does work when needed.

the problem is that if it's asking you the pin number for the certificate, there isn't anything else left for us to do. It is already being managed by electron or the OS so I'm not aware of anything we can do to prevent that.
i'll reconvert the PR to be a proper one so it is available for the next version :)

the problem is that if it's asking you the pin number for the certificate, there isn't anything else left for us to do. It is already being managed by electron or the OS so I'm not aware of anything we can do to prevent that.

@Willyfrog Not sure I'm following... it doesn't ask for the pin until after a certificate is selected. I'd think that when certificate is selected it should kick of normal process that happens when there is only 1 certificate but it seems like somehow it's being treated differently?

exactly, and it shouldn't. Once the certificate is selected, we ask electron to take care of it, so it asks you the pin number.

@Willyfrog any ideas when https://github.com/mattermost/desktop/pull/1354 might be able to be released?

I'm afraid I dont have a timeline for that, my guess is september, but that's quite broad

Also very interested in this fix - is there a way to find out the release time more accurately? Or even make sure it's soon?

we created a dot release containing this PR. Would you mind to give it a spin and see if everything works as expected? You can find the RC in the release page

Final release is here: https://github.com/mattermost/desktop/releases/tag/v4.5.3.


Added new location for docker bosh release

@dpb587-pivotal CFCR maintains that repository. I am not sure if you still need to support old link. My understanding was that you'll check the load and eventually delete the old link when it is not accessed anymore.

What we typically do is just stop following/listing the original repository, if that's okay with you? If you know your users are tracking bosh.io for the release, you'll just want to make sure they're aware it will stop listing new versions.

I went ahead and removed the cf-platform-eng/docker-boshrelease release; they should still be accessible on bosh.io for existing consumers, but cloudfoundry-incubator/docker-boshrelease should be recommended for new consumers and versions.
Let me know if that becomes an issue for some reason and we can restore it for a grace period.

FYI, a few semi-recent versions needed to be skipped due to missing golang packages. I think we discussed those package/blob issues in Slack or somewhere previously.


Error in pyproject.toml:  {...} is not valid under any of the given schemas

[project] section with anything in it causes the following problem:
[project]

{} is not valid under any of the given schemas

[project]
name = "hello"

{"name":"hello"} is not valid under any of the given schemas

Additionally, it seems that
    "evenBetterToml.schema.associations": {
        "pyproject.toml": "https://json.schemastore.org/pyproject.json",
    },

Does not force detection either

It is because you missed "version" key: https://github.com/tamasfe/taplo/issues/316

@tamasfe should this one be closed as a duplicate? we have #316 where the path seems clear to me: patching. Please comment on what you think is necessary with the situation

Yes this looks like a duplicate. I'll take a look at #316 when I'll have access to a computer in a few weeks. Thanks for helping triaging the issues!


Add query param chat init

I see the what from the title but not the "why". Could you add context regarding what this achieves in the PR description please? 🙏

The new invite flow via w3mv2 is slick, great stuff ✨ 🚀

Minor UX: would be dope if we automatically close web3Modal when the chat invite comes through (i.e. on chat_invite) if it's not overly complicated.
Initially took me a moment to realise there was a chat invite there until I closed the modal myself.


Allow newer versions of jQuery as peer dependency

The current peer dependency specification doesn't allow versions of jQuery in the 2.x or 3.x lines, both of which are (I believe) compatible with this plugin. This updates package.json to allow them.

It also says that in the "requirements" https://github.com/ichord/At.js#requirements

thanks.


CardPool desync: Disappearing cards

Following #606
I have identified at least one other scenario:

Without letting go, drag & drop a card (1) to an other column and back to its original place. I don't think we are handling any events at this point, this is all sortablejs-vue3.
Remove the card above it (2), either by drag & drop or by click.
The DOM element of the card (1) is deleted. The card object is still present in the associated column (see card count on top of the column)

I don't understand why this happens.
The issue is detectable though. As a first workaround I'll force a re-render of the component when a desync. is detected.

Workaround in 0092fdfb438da029a2d46dca8d6b24f90c70ac30.

Somehow, this can still happen. See the case of the disappearing Palace Jailer here:
https://www.youtube.com/watch?v=iJ9HXRFfldU&t=719s
No luck reproducing it yet.

Still no clue of what happened in the previous clip.
Hopefully b3f0eac12605f55583259a6938b3cbc1a9d2a4b2 will help recover from similar issues.


Updated Dockerfile to use an alpine (busybox) source.

I updated the Dockerfile to use an alpine-linux source, which is based on busybox.
This drastically reduces the image size from 943MB to 296MB.
Updated Docker.md as well to run with --rm to remove the container on exit.

Thanks.


presto-admin catalog command not found

This is not an issue but I recently downloaded the online installer, I can't seem to find the catalog add command. Am I missing something?
[ec2-user@ip-172-31-1-29 bin]$ sudo ./presto-admin catalog add hive
Warning: Command not found:
catalog add hive
[ec2-user@ip-172-31-1-29 bin]$ sudo ./presto-admin --version
presto-admin 1.4.2
OS: AWS EMR

presto-admin 1.4.2

this is very old. The newest is 2.5.1. I am therefore closing the issue.
BTW I don't think Facebook Presto team maintains presto-admin project.
I would suggest that you consider migrating away from it.
For AWS, you can use Starburst Presto packaged for AWS (https://www.starburstdata.com/presto-aws-cloud/) which does not depend on presto-admin.


Why do u apply anti-adv method to generate initial cam seeds, I reproduce your implementation and find that your real initial cam seeds are worse than baseline without anti-adv method? Can u explain this?

Maybe, this paper propose no new methods for WSSS. Your improvement is brought by cvpr2020 anti-adv method.

It is an auxiliary module for generating cams. If you want to perform our method in another mode, maybe you should readjust the hyper-parameters.

To be fair, applying your method to baseline, the cams quality becomes worse while I try to reproduce. But implementing anti-Adv the cams quality becomes better than baseline, but noting that this improvement does not come from your method. I am so confused why your method works for nothing even hampering the performance. because your method is just for paper writing but works nothing??? Hope you can explain and re-implement your released code for right reproducement

What I want to say is that the story A works for nothing but just for paper writing while story B actually works but it has already been published, and you just steal it from others??


Fix teardown in SQLite File spec

Pull Request Description
Fixes teardown of SQLite spec. There used to be only connection.close, but we also have to call connection.drop_table for every created table.
This causes problems only in [SQLite File] tests. These are backed by a sqlite file and some tables are persistent in that table. It is possible, that before tests are run, this file is non-empty and contains garbage from previous runs.
Important Notes
Should fix https://github.com/enso-org/enso/actions/runs/7724599547/job/21057063900#step:10:7243 that was triggered when Table_Tests were run on a non-clean runner.
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

This causes problems only in [SQLite File] tests. These are backed by a sqlite file and some tables are persistent in that table. It is possible, that before tests are run, this file is non-empty and contains garbage from previous runs.

While cleaning up seems the right thing to do, for this particular case it seems that a more robust solution would be to ensure that file.delete_if_exists is called before the first SQLite File test is run - that would ensure that even if a previous run did not clean something up (e.g. because it failed fatally with OOM or was terminated by a signal), the new run still gets a clean working environment. Cleaning afterwards is good and recommended, but ensuring the initial environemnt is clean seems even better.
Can we add a delete_if_exists to init?

Can we add a delete_if_exists to init?

@radeusgd Sure, good idea. Added in f4163b790d65bb1db5caacef8e9a7f69b0e85997

Deleting the SQLite file before a connection is made is not a good idea. It causes failures like https://github.com/enso-org/enso/actions/runs/7741741366/job/21109332981?pr=8918#step:8:15352 for tests that create multiple connections. Let's revert https://github.com/enso-org/enso/pull/8918/commits/f4163b790d65bb1db5caacef8e9a7f69b0e85997 and merge the PR. We will address other issues related to teardowns once some more transient failures occur.

Deleting the SQLite file before a connection is made is not a good idea. It causes failures like enso-org/enso/actions/runs/7741741366/job/21109332981?pr=8918#step:8:15352 for tests that create multiple connections. Let's revert f4163b7 and merge the PR. We will address other issues related to teardowns once some more transient failures occur.

 GitHub**Fix teardown in SQLite File spec · enso-org/enso@f5587b6**Hybrid visual and textual functional programming. Contribute to enso-org/enso development by creating an account on GitHub.

I still think it is a good idea, as argued before. It just has to be done at the proper place - it should be done once before all SQLite tests run, not on every connection being established.


Move Dockerfile to root directory

Hi @yarncraft, thanks for the PR. It's easier to fix this on my end, though, because I have to modify some internal mappings file (that's where the mistake was made, I believe.) So I'll close this and the other PR. However, can you please confirm that the current installation instructions are correct for this new location?

Hi @yarncraft, thanks for the PR. It's easier to fix this on my end, though, because I have to modify some internal mappings file (that's where the mistake was made, I believe.) So I'll close this and the other PR. However, can you please confirm that the current installation instructions are correct for this new location?

Ah I see! Ok that's fine, I will guide you through #161 afterwards


New term request: photoconversion evidence

reference: https://www.ncbi.nlm.nih.gov/pubmed/28574633
Suggested relations:
is_a fluorescence evidence
is_a imaging assay evidence
is_a protein assay evidence

Hi again @Pimmelorus - for this term, I also need:

PMID(s) or other source(s) for a definition
The name of the group/project this term is for

Thanks again!

Hello @rctauber
This term is for the Synapse Gene Ontology group.

As with the other term, I want to make sure I get the specific application correct. What is being labeled with the fluorescent proteins? Or is it just a broad term for any sort of labeling with this type of fluorescent protein?
Sorry for all the questions - I'm trying to get an idea of what this assay is about, so we can be sure to categorize it based on that, rather than just the methods applied.

General: The basic principle is that the spectral emission properties of fluorescent proteins (e.g., mEosFP, tdEosFP, Dendra, Dronpa, Kaede, KikGR, mOrange) can be shifted (send out a different color of light upon excitation) once they are irradiated by ultraviolet or blue light.
Application: When these fluorescent proteins are attached to native protein in a cell, this technique can be used to track mobility of protein from a given start position in the cell (exposed to ultraviolet or blue light). [ref: Scientific Reports volume 5, Article number: 11771 ]

We also have the term fusion protein localization evidence with the definition:

A type of protein localization evidence resulting from the fusion of a protein of interest to a labeling protein which has enzymatic activity or fluorescence properties.

If we're looking at the application you suggested, it seems like this term could be a child of that. If it's not necessarily protein localization, though, I'll place it as a child of protein assay evidence.

Again, I personally do not like to mix technique with application. photoconversion evidence may be used for other applications as well. What I request is a tern term that describes the general type of evidence. You are free to create a child that incorporates fusion protein localization evidence, but I will not be using it.

Seems like photoconversion evidence should be child of fluorescence evidence (under direct assay), and then fusion protein photoconversion localization evidence could be derived and placed under fusion protein localization evidence (as per ref: Scientific Reports volume 5, Article number: 11771)

Great, thanks @Pimmelorus and @ivanerill
I'll move forward with photoconversion evidence as a child of fluorescence evidence, with a suggested definition:

A type of fluorescence evidence where a molecule tagged with a fluorescent protein is exposed to ultraviolet or blue light to shift the spectral emission properties for visualization.

I'm going to add this term in so it gets pushed with the release today. If you have any issues with the definition, please let me know and we can change it! The ID will be ECO:0007017, and ECO:0007018 for the manual assertion child.

Closing this issue - please let me know if you have any other questions!


[FLINK-6097][table] Guaranteed the order of the extracted field refer…

…ences as input order.
Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your pull request. For more information and/or questions please refer to the How To Contribute guide.
In addition to going through the list, please provide a meaningful description of your changes.

[x] General

The pull request references the related JIRA issue ("[FLINK-6097] Guaranteed the order of the extracted field references as input order.")
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message (including the JIRA id)

[ ] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[x ] Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

HI, @KurtYoung Thanks for your attention to this PR. Good question, the purpose of this change is just like this JIRA's description:
I want ProjectionTranslator # identifyFieldReferences  to guaranteed the order of the extracted field references same as input order. using Set just want to eliminate duplicate field references, and List also can do this, it is no harm to keep the ProjectionTranslator # identifyFieldReferences method's output order consistent with input.
If the disorder results of  ProjectionTranslator # identifyFieldReferences can work, then the orderly results must also work very well, because the order is also a  situation of disorder.
What to you think?
Thanks,
SunJincheng

HI, @KurtYoung Thanks for your attention to this PR. Good question, Here I glad share why I notice this method：
When we try to implement OVER window TableAPI, The first version of the prototype to achieve，we do not consider the table field will be out of order when we implement translateToPlan method，then we set outputRow field from inputRow according to the Initial order of the table field index.
At the beginning, the projections in the select statement less than 5 columns It works well.But Unfortunately when the count of projections bigger than 4 (>=5), we got the random result. Then we debug the code, we find that ProjectionTranslator # identifyFieldReferences method uses theSet temporary save field, when the number of elements in the Set is less than 5, the Set takes the Se1, Se2, Se3, Se4 data structures. When the number of elements is greater than or equal to 5, the Set takes HashSet # HashTrieSet and which will cause the data to be out of order. So we thought 2 approach to solve this problem：
Let ProjectionTranslator # identifyFieldReferences method guaranteed the order of the extracted field references same as input order.
We add the input and output field mapping.
At last we using approach#2 solve the problem. This change is not necessary for the problem i have faced. But I feel it is better to let the output of this method in the same order as the input, it may be very helpful for other cases, though I am currently not aware of any. I am ok with not making this change, but we should add a comment instead to highlight that the potential output of the current output. Otherwise, some people may not pay attention to this and assume it is in order.
Thanks,
SunJincheng

Hi @sunjincheng121, thanks for explaining the issue, but I did not completely understand the problem. The ProjectionTranslator is working on Table API expressions and LogicalNodes which are translated into Calcite RelNodes and RexNodes. The RelBuilder works with names not positions, so shouldn't field positions and layout be handled by Calcite?

Can you close this PR as well @sunjincheng121?
Thanks!


Large file txt error Invalid string length

VSCode Version: 1.19.0
OS Version: Windows 10 Pro

Steps to Reproduce:
There is a large txt file containing 2060391 lines, with a total size of 813 mb, when trying to save it in csv format, it writes an error: Invalid string length

Reproduces without extensions: Yes

/duplicate https://github.com/Microsoft/vscode/issues/32503


Remote JWKS fetch failing

It goes http/port 80 and won't respect cluster configuration so remote JWKS fetch is failing always

Fixed. it was just that it was going for IPv6. Forced it for IPv4 lookup and fixed the issue. Scheme is just misleading here


chore(vault): configure clusterissuer and private certificate

Type
Enhancement

Description

Updated the default cilium_version in Terraform variables.
Added a reference to a ConfigMap named eks-mycluster-0-vars in clusters/mycluster-0/infrastructure.yaml.
Added platform-private-gateway-certificate.yaml to the resources list in infrastructure/base/gapi/kustomization.yaml.
Created a new Certificate resource named private-gateway-certificate with issuer reference to vault.
Updated infrastructure/base/gapi/platform-private-gateway.yaml by removing the cert-manager.io/cluster-issuer: private-ca annotation and updating certificateRefs name.
Updated security/base/cert-manager/kustomization.yaml resources list by removing self-signed-clusterissuer.yaml and adding vault-clusterissuer.yaml.
Removed self-signed-clusterissuer.yaml file content, including ClusterIssuer and Certificate resources.
Added a new ClusterIssuer named vault with Vault server configuration and AppRole authentication in security/base/cert-manager/vault-clusterissuer.yaml.

Changes walkthrough
Relevant filesConfiguration changes

variables.tfUpdate Cilium version in Terraform variables

terraform/eks/variables.tf

Updated the default cilium_version from "1.14.5" to "1.14.6".

+1/-1

platform-private-gateway.yamlUpdate platform private gateway configuration

infrastructure/base/gapi/platform-private-gateway.yaml

Removed cert-manager.io/cluster-issuer: private-ca annotation.
Updated certificateRefs name from platform-private-tls to  private-gateway-tls.

+1/-3

kustomization.yamlUpdate cert-manager kustomization resources

security/base/cert-manager/kustomization.yaml

Removed self-signed-clusterissuer.yaml from the resources list.
Added vault-clusterissuer.yaml to the resources list.

+1/-1

self-signed-clusterissuer.yamlRemove self-signed cluster issuer and related certificate

security/base/cert-manager/self-signed-clusterissuer.yaml

Entire file content removed, including ClusterIssuer and  Certificate resources.

+0/-31

Enhancement

infrastructure.yamlAdd ConfigMap reference in infrastructure.yaml

clusters/mycluster-0/infrastructure.yaml

Added substituteFrom section to postBuild to reference a  ConfigMap named eks-mycluster-0-vars.

+3/-0

kustomization.yamlAdd private gateway certificate to kustomization resources

infrastructure/base/gapi/kustomization.yaml

Added platform-private-gateway-certificate.yaml to the resources   list.

+1/-0

platform-private-gateway-certificate.yamlAdd new private gateway certificate

infrastructure/base/gapi/platform-private-gateway-certificate.yaml

Added a new Certificate resource named private-gateway-certificate   with issuer reference to vault.

+17/-0

vault-clusterissuer.yamlAdd new Vault cluster issuer

security/base/cert-manager/vault-clusterissuer.yaml

Added a new ClusterIssuer named vault with Vault server   configuration and AppRole authentication.

+17/-0

 ✨ Usage guide:
Overview:
The describe tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.
When commenting, to edit configurations related to the describe tool (pr_description section), use the following template:
/describe --pr_description.some_config1=... --pr_description.some_config2=...

With a configuration file, use the following template:
[pr_description]
some_config1=...
some_config2=...

  Enabling\disabling automation

When you first install the app, the default mode for the describe tool is:

pr_commands = ["/describe --pr_description.add_original_user_description=true"
                         "--pr_description.keep_original_user_title=true", ...]

meaning the describe tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description.

Markers are an alternative way to control the generated description, to give maximal control to the user. If you set:

pr_commands = ["/describe --pr_description.use_description_markers=true", ...]

the tool will replace every marker of the form pr_agent:marker_name in the PR description with the relevant content, where marker_name is one of the following:

type: the PR type.
summary: the PR summary.
walkthrough: the PR walkthrough.

Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

  Custom labels
The default labels of the describe tool are quite generic: [Bug fix, Tests, Enhancement, Documentation, Other].
If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases.
Examples for custom labels:

Main topic:performance - pr_agent:The main topic of this PR is performance
New endpoint - pr_agent:A new endpoint was added in this PR
SQL query - pr_agent:A new SQL query was added in this PR
Dockerfile changes - pr_agent:The PR contains changes in the Dockerfile
...

The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases.
Note that Labels are not mutually exclusive, so you can add multiple label categories.
Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

  Inline File Walkthrough 💎
For enhanced user experience, the describe tool can add file summaries directly to the "Files changed" tab in the PR page.
This will enable you to quickly understand the changes in each file, while reviewing the code changes (diffs).
To enable inline file summary, set pr_description.inline_file_summary in the configuration file, possible values are:

'table': File changes walkthrough table will be displayed on the top of the "Files changed" tab, in addition to the "Conversation" tab.
true: A collapsable file comment with changes title and a changes summary for each file in the PR.
false (default): File changes walkthrough will be added only to the "Conversation" tab.

  Utilizing extra instructions
The describe tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project.
Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description.
Examples for extra instructions:
[pr_description]
extra_instructions="""
- The PR title should be in the format: '<PR type>: <title>'
- The title should be short and concise (up to 10 words)
- ...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

  More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs 💎: Generate docstring for new components introduced in the PR.
/generate_labels 💎: Generate labels for the PR based on the PR's contents.
/analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the describe usage page for a comprehensive guide on using this tool.

/describe


Darkplaces-2017 for Quake I

Project link: http://icculus.org/twilight/darkplaces/files/
Project license: GPLv2
Does it work on 64-bit only Linux: YES
Is source code available?: YES
Is source code stored in Git?: NO
List of Steam AppIds of supported games:
https://store.steampowered.com/app/2310/QUAKE/
https://store.steampowered.com/app/9040/QUAKE_Mission_Pack_1_Scourge_of_Armagon/
https://store.steampowered.com/app/9030/QUAKE_Mission_Pack_2_Dissolution_of_Eternity/

Additional information
I suggest to take darkplacesengine20170829beta1.zip which is the recommended version to run the famous mod Quake 1.5 and 20170829beta1 is the one in AUR. (2018 versions have issues).
I also suggest to name it Darkplaces-2017.
Because there is a capital letter in the folder "Id1", the command -game Id1 must be specified.
The command should look like this:
./darkplaces-linux-x86_64-sdl -game Id1

There are also 2 Missions Packs:
https://store.steampowered.com/app/9040/QUAKE_Mission_Pack_1_Scourge_of_Armagon/
https://store.steampowered.com/app/9030/QUAKE_Mission_Pack_2_Dissolution_of_Eternity/
Mission Pack 1 add the folder hipnotic
To run it: ./darkplaces-linux-x86_64-sdl -game Id1 -game hipnotic
Mission Pack 2 add the folder rogue
To run it: ./darkplaces-linux-x86_64-sdl -game Id1 -game rogue
PS: these 2 packs are missing in the list  of supported games with vkquake

There are also 2 Missions Packs:
https://store.steampowered.com/app/9040/QUAKE_Mission_Pack_1_Scourge_of_Armagon/
https://store.steampowered.com/app/9030/QUAKE_Mission_Pack_2_Dissolution_of_Eternity/
Mission Pack 1 add the folder hipnotic
To run it: ./darkplaces-linux-x86_64-sdl -game Id1 -game hipnotic
Mission Pack 2 add the folder rogue
To run it: ./darkplaces-linux-x86_64-sdl -game Id1 -game rogue
PS: these 2 packs are missing in the list  of supported games with vkquake

For this, would prefer to have the game to continue, as it'll make it easier to create and debug the engine, since I'm building it from scratch (compared to the other where I was upgrading an existing one).
I'll be on the lookout for it on sale, one of the few id games I seem to not own :)

For this, would prefer to have the game to continue, as it'll make it easier to create and debug the engine, since I'm building it from scratch (compared to the other where I was upgrading an existing one).
I'll be on the lookout for it on sale, one of the few id games I seem to not own :)

Can't you use the binaries in the archive?

Can't you use the binaries in the archive?

Can't you use the binaries in the archive?

If it's an open source project, I prefer to compile it from source. That helps to keep it in a known compatibility state, and normally (doesn't seem like it as much here) it ends p being easier to keep up to date in case of any changes.

Can't you use the binaries in the archive?

If it's an open source project, I prefer to compile it from source. That helps to keep it in a known compatibility state, and normally (doesn't seem like it as much here) it ends p being easier to keep up to date in case of any changes.

I now own the original quake (not the expansions) so I'll work on this when I get a chance. For the expansions, I'll need some help for testing, unless I end up buying them at some point.

I now own the original quake (not the expansions) so I'll work on this when I get a chance. For the expansions, I'll need some help for testing, unless I end up buying them at some point.

I've added the mission packs to vkquake and added darkplaces-2017 as an option for quake and the mission packs.

I've added the mission packs to vkquake and added darkplaces-2017 as an option for quake and the mission packs.


Minor Bug Fix node.py

Check for buffer size to have enough data, before extracting m length.
Maximum size of message has been set to 500 KB.

Closes a vulnerability of unlimited msg sizes..allows us to set a user configurable max_blocksize setting in the future..


Dynamic arguments should work with modifiers

What problem does this feature solve?
Related to: https://github.com/vuejs/vue/issues/9417
Since Vue 2.6, using dynamic arguments I can conditionally add a keydown event:
@[keydownEvent]="handleKeydown"

What I'm unable to do is attach a keydown event with modifiers, since they do not appear to be working with dynamic arguments in Vue 2.6.6. To restrict the example above to just Enter keydown events, I have to write the logic into the handler instead of using the existing Vue modifiers:
@[keydownEvent]="keydownMods($event, handleKeydown)"

methods: {
    keydownMods(e, callback) {
      if (e.code === 'Enter') {
        e.preventDefault();
        callback();
      }
    }
}

What does the proposed API look like?
Allow for the existing v-on modifiers to be used with dynamic arguments:
@[keydownEvent].enter.prevent="handleKeydown"

This already works http://jsfiddle.net/q2xrs1dh/
Next time, please provide a repro

Turns out this was related to having multiple keydown events assigned. Works fine with .enter unless you also have a .space.
http://jsfiddle.net/78e5cvpf/

yeah because they are all applied so it will never trigger because the keyup event can only have one key


Starting jobs locally and on remote host can not be done with a single command

Summary of the new feature / enhancement
Problem
In the case I have multiple servers where I want to run a scriptblock, including the server I am connected on, I am forced to write this over explicit code :
if ($computer -like $env:computername ) {   $Jobs += start-job -ScriptBlock $ScripBlock } else {   $Jobs += Invoke-Command -ComputerName $computer -AsJob -ScriptBlock $ScripBlock }
Reason

Start-job does not allow to run jobs on remote host
Invoke-Command -ComputerName $env:computername -asjob -ScriptBlock $ScripBlock

Requires to be "ran as administrator" to function

OR

throws an error  OpenError: [Hostname] Connecting to remote server Hostname failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.

Invoke-Command -AsJob -ScriptBlock { dir } does not match required parameter set

Conclusion
This is not new to powershell and I have always found complexity into writing scriptblocks that could run on multiple servers, including the local server I am connected on
Proposed technical implementation details (optional)
As start-job does not require to "run as administrator" I feel like there shouldn't be any restrictions into being able to run

Invoke-Command -AsJob -ScriptBlock { dir } which could be, somehow, an alias of start-job
Invoke-Command -AsJob -ScriptBlock { dir } -computername $env:computername
without having to use the 'log on as adaministrator' switch

I have always found complexity into writing scriptblocks that could run on multiple servers

kasini3000 site mirror:(https://github.com/kasini3000/kasini3000)
win,linux devops automation batch script framework.(It is similar to Puppet，Ansible，pipeline)
Open source, free, cross-platform
English manual: https://gitee.com/chuanjiao10/kasini3000/blob/master/docs/kasini3000_manual.xlsx
kasini3000_agent_linux Shell script,one click install powershell on linux,modify sshd_config for PsRemote.
The technology, protocol, or feature keyword supported by "kasini3000":
Offline installation of win, linux, master, node and all libraries.
winrm, ssh, rsync between win and linux, batch telnet, batch sftp, batch ftp-sync, batch sftp-sync, sqlite, remote object transfer,
batch database client, picture alarm, balloon alarm, sound alarm, WeChat alarm , Dingding alarm.
Support from win, linux master sodo login to linux node.
Free support for 1 batch of linux2winrm. Another batch of linux2winrm is supported for a fee.
The remote command line from the master to node supports only bash in the Linux node, but no pwsh is installed. But this is not recommended.
Q: I already have my .py, .sh, .pl, .bat scripts, why use your framework?
A: The framework provides these functions:
Kasini3000 provides multi-process and multi-thread engine; automatic remote transfer of ps1 scripts and code blocks;
timed task engine; remote value transfer of objects; Batch modify win node, linux node password.
linux master to win node:
depened OMI ,this has some little bugs,for none english script name.
two ways :
one free ,use foreach + c:\ProgramData\kasini3000\k_run_ip_port_l2w_user_pwd.ps1
two 20$ , depened 【nodelist.csv】 , batch by sqlite.

The administrator restriction is on the remoting (WinRM) endpoint for security and is set by default.  It is possible to remove the admin constraint from the endpoint but not advisable.  It is interesting that the credentials used to log onto the remote machines work, but fail for the local machine case.  Start-Job does not connect to a WinRM endpoint like Invoke-Command, and instead connects to a local child process with the same user account as the parent process, so there are no security concerns as with WinRM endpoints which can accept off-box connections.
I am not sure it is worth adding the ability to create a local job to Invoke-Command -AsJob.  It seems better to create a helper function that makes the decision to start an off-box WinRM job connection or a local job connection.


How to load secrets in to environment variable on Linux POD

I am using the below things. However, I need to be able to load these secrets onto env variable. It is not working at all. Could you please help us how to achieve that?
apiVersion: v1
kind: Pod
metadata:
labels:
app: nginx-flex-kv
name: nginx-flex-kv
namespace: ns-gdprhub-kc
spec:
containers:

name: nginx-flex-kv
image: nginx
imagePullPolicy: Always
command: ["sh", "-c"]
args: ["export KEYCLOAK_USER=$(cat /kvmnt-kc/gdpr-key-cloak-admin-user)",
"export KEYCLOAK_PASSWORD=$(cat /kvmnt-kc/gdpr-key-cloak-admin-user-pwd)"]
volumeMounts:

name: secrets-store-inline-gdprhub-kc
mountPath: /kvmnt-kc
readOnly: true
volumes:

name: secrets-store-inline-gdprhub-kc
csi:
driver: secrets-store.csi.k8s.io
readOnly: true
volumeAttributes:
secretProviderClass: "azure-scp-gdprhub-kc"

apiVersion: secrets-store.csi.x-k8s.io/v1alpha1
kind: SecretProviderClass
metadata:
name: azure-scp-gdprhub-kc
namespace: ns-gdprhub-kc
spec:
provider: azure
parameters:
usePodIdentity: "false"
useVMManagedIdentity: "true"
userAssignedIdentityID: "{{kubeletid_clientId}}"
keyvaultName: "{{key_vault}}"
#cloudName: "AzurePublic"
objects:  |
array:
- |
objectName: gdpr-key-cloak-admin-user
objectAlias: gdpr-key-cloak-admin-user
objectType: secret
objectVersion: "{{kc-admin-user-ver}}"
- |
objectName: gdpr-key-cloak-admin-user-pwd
objectAlias: gdpr-key-cloak-admin-user-pwd
objectType: secret
objectVersion: "{{kc-admin-user-pwd-ver}}"
- |
objectName: gdpr-sql-kc-db-user-name
objectAlias: gdpr-sql-kc-db-user-name
objectType: secret
objectVersion: "{{kc-db-user-name-ver}}"
- |
objectName: gdpr-sql-kc-db-user-pwd
objectAlias: gdpr-sql-kc-db-user-pwd
objectType: secret
objectVersion: "{{kc-db-user-pwd-ver}}"
resourceGroup: "{{key_vault_rg}}"
subscriptionId: "{{subscription_id}}"
tenantId: "{{tenant_id}}"

Can you please help asap we need to do pre prod deploymnet..

Can you PTAL at: https://github.com/kubernetes-sigs/secrets-store-csi-driver#optional-sync-with-kubernetes-secrets looks like you are missing the secretObjects fields

I wrote an example:
`---
apiVersion: "v1"
kind: "ConfigMap"
metadata:
name: "mssql-config-map"
namespace: default
labels:
app: mssql
data:
MSSQL_PID: "Developer"
ACCEPT_EULA: "Y"
apiVersion: "v1"
kind: "Service"
metadata:
name: "mssql" #$(service name).$(namespace).svc.cluster.local
labels:
app: mssql
spec:
clusterIP: "None"
ports:

port: 1433
name: "mssql"
selector:
app: "mssql"
release: "mssql"

apiVersion: v1
kind: Service
metadata:
name: mssql-lb
labels:
app: mssql
spec:
selector:
app: mssql
ports:
- protocol: TCP
port: 1433
targetPort: 1433
type: LoadBalancer
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: mssql
labels:
app: mssql
release: mssql
spec:
serviceName: "mssql"
selector:
matchLabels:
app: "mssql"
release: "mssql"
replicas: 1
updateStrategy:
type: OnDelete
template:
metadata:
labels:
app: "mssql"
release: "mssql"
spec:
nodeSelector:
"beta.kubernetes.io/os": linux
terminationGracePeriodSeconds: 180
volumes:
- name: secrets-store-inline
csi:
driver: secrets-store.csi.k8s.io
readOnly: true
volumeAttributes:
secretProviderClass: "azure-sync"
containers:
- name: mssql
image: mcr.microsoft.com/mssql/server:2017-latest
resources:
{}
ports:
- containerPort: 1433
name: mssql
envFrom:
- configMapRef:
name: mssql-config-map
env:
- name: MSSQL_PID
valueFrom:
configMapKeyRef:
name: mssql-config-map
key: MSSQL_PID
- name: ACCEPT_EULA
valueFrom:
configMapKeyRef:
name: mssql-config-map
key: ACCEPT_EULA
- name: SA_PASSWORD #env variable to create
valueFrom:
secretKeyRef:
name: mssql #k8s secret name. (kubectl get secret). this is auto synced during creation and deletion of the POD
key: mssql #this must match the kv configuration in the yaml under secretObjects
volumeMounts:
- name: mssql-pvc
mountPath: /var/opt/mssql
- name: secrets-store-inline
mountPath: "/mnt/secrets-store"
readOnly: true
volumeClaimTemplates: #default is standard storage. managed-premium is ssd
- metadata:
name: mssql-pvc
spec:
storageClassName: default
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 4Gi
`
snippet of provider configuration
`provider: azure
secretObjects:                          # [OPTIONAL] SecretObject defines the desired state of synced K8s secret objects

secretName: mssql                     # name of the Kubernetes Secret object
type: Opaque
data:

objectName: "mssql-secret"           # name of the mounted content to sync. This could be the object name or object alias
key: mssql                           # data field to populate. This must match in deployment yaml for key
parameters:
useVMManagedIdentity: "true"
userAssignedIdentityID: "34d6ef86-9846-4e8e-aa6d-f2ac23908abc"
keyvaultName: "jrkeyvaultdemo"               # the name of the KeyVault
objects: |
array:

|
objectName: mssql-secret
objectType: secret       # object types: secret, key or cert`

Thank you. I shall try this.

@iamsoorya Were you able to successfully load the secrets as env variables based on the examples @jrudley provided?

Yes, the code has worked. However,  last friday, I tried to use the latest version 11 and version 6,it failed. However, I am happy to continue with older version.
Thanks for solving our issue. It has helped to use to application to user acceptance testing.

@iamsoorya Do you have the logs for the failure when you tried with the latest version?

@iamsoorya Closing this issue. Please feel to free reopen with logs if you hit any issue while trying out with the latest releases.

@aramase  is syncing vault with k8s secrets the only way to load  secrets as env variables? To lower the attack surface, it would be preferable to store minimum of secrets in etcd

@aelmanaa if you do not want to sync with k8s secrets, another option is to set the environment variable before the main process starts in your container. For example:
spec:
  containers:
  - name: nginx-kv
    image: nginx
    command: ["/bin/sh", "-c", "export SECRET=$(cat /mnt/secrets-store/mysecret); echo $SECRET; nginx -g 'daemon off;'"]
    volumeMounts:
    - name: test
      mountPath: /mnt/secrets-store
      readOnly: true

@ritazh This example will be a good addition to our docs for users who don't want to sync as Kubernetes secret.

@ritazh @aramase
I'm having trouble getting this command to execute correctly. I can get the secrets to mount correctly into the volume, but when I export them via command, the environment variable remains empty once I shell into the container. I've tried the base level command option, as well as the lifecycle poststart hook. Same results. If I run the command via shell on the pod, the environment variable gets set correctly.
Does this method no longer work, or is there a better way to get the secrets from the volume into environment variables?

I'm facing the same problem as @dmradford, secrets mount correctly and kubectl exec integration-ws-5b6868fcb8-57fg2 -- ls /mnt/secrets-store/  gives me the right secrets but unable to create env vars from those secrets.

@dmradford @sagark23 The supported way for setting the env var with the CSI driver is to sync the mounted content as Kubernetes secrets and reference those as environment variables in the pod spec:
https://azure.github.io/secrets-store-csi-driver-provider-azure/configurations/sync-with-k8s-secrets/
https://azure.github.io/secrets-store-csi-driver-provider-azure/configurations/set-env-var/
We'll try out the above command and add it as an alternative option after validation.

Hi @aramase : Will it be also possible to mount nginx tls certificate as env for nginx ingress pods

Any update on how to set the env var without using Kubernetes secrets?
I also can confirm that the command @ritazh posted does not work, sadly.

Hi @aramase : Will it be also possible to mount nginx tls certificate as env for nginx ingress pods

Hey @shubhammicrosoft1, Could you try this?


Publish Zod to jsr

This pull-request adds a jsr.json file to deno/lib to publish Zod to JSR.
I also added a simple step to the GitHub release workflow to update the "version" specifier using the one from package.json.
The only thing I believe that would have to be set-up for automatic releases is OIDC-based publishing to JSR.
I published a sample package to jsr:@prgm/zod.
This should close #3300.

Any update on this PR?

Is there anything that blocks this from happening? I'd be happy to spend time on this if that helps in any way


Feature: Ability to specific Consumer Group for Source Connector

Feature description
Users should be able to specify the Consumer Group ID to be used by the Source Connector (and the underlying Kafka Consumer).
This will enable some valuable use cases such as scaling via multiple Conduit instances as well as recovery (where I can create a new instance and have it continue where the previous consumer ended).

Maybe we can add the additional details in this ticket: https://github.com/ConduitIO/conduit/issues/142, since it was already triaged?

@ahmeroxa :+1: we did move some connector specific issues into the respective repos, so we may do that for this one too.


How to use a relay openai_key in llms/OpenAI

I can't use the relay openai_key correctly beacause I don't know how to set the base_url. It seems that there is no way  to change base_url in documents.
Here are codes:
async queryDocument(query) {
try {
const docs = await this.store.similaritySearch(query);
const llm = new OpenAI({
openAIApiKey:process.env.Open_API_KEY,
base_url:"https://api.132999.xyz/v1/",
temperature: 0.5
});
const chain = loadQAStuffChain(llm);
const answer = await chain.call({
input_documents: docs,
question: query,
});
return answer.text;
} catch (e) {
throw e;
}
}

const fields = {
modelName: "gpt-3.5-turbo-instruct",
openAIApiKey: process.env.Open_API_KEY,
configuration: {
baseURL: "https://api.132999.xyz/v1/",
}
};
const embeddings = new OpenAIEmbeddings(fields);
Is it same as the langchain/embeddings/openai? It doesn't work yet.


Add soak test workflow.

Ok for review but let me merge since it has dependency on https://github.com/open-telemetry/opentelemetry-lambda/pull/48

Only difference vs integration tests workflow is

names use git sha
Delete layers from terraform before destruction if soak test passes

As a followup we would add https://github.com/aws-observability/aws-otel-lambda/pull/19/files#diff-93dcdebadcc088e25be16bdc7166019b0b5b58a35d5cef13c97ba78909814632 in


websocket module can use websocket6.0?

Probably a dupe of #1264 but hard to tell based on the fact that there's no description.


Does Miri install into the correct rustup toolchain if it's not the default?

The current nightly doesn't have Miri, so I installed a nightly from a few days back to run nightly. I forgot to install rust-src, which Miri thoughtfully prompted me:
cargo +nightly-2019-08-01 miri --bin hash_file src/lib.rs
It seems you do not have the rust-src component installed. I will run `rustup component add rust-src`. Proceed? [Y/n]

Since it says what it would run, I assumed that it would not secretly run  rustup component add rust-src --toolchain nightly-2019-08-01 and canceled it. Would it have installed the component in the right toolchain for me?

It definitely would have run what it says.
But in an ideal world, rustup would set the right env var inside the commands it executes so that nested rustup invocations also apply to that toolchain. I will do some digging.

I tested this, and it seems to work fine. Looks like rustup is doing the right thing.

That's a good rustup.


BigQuery Storage v1Beta2 : PERMISSION_DENIED on TABLES_UPDATE_DATA despite having correct IAM role

I follow more or less the example in the official doc to tryout the v1b2 API, and I do get the above error despite having the right roles
2021-10-28 18:05:39.424  INFO 80223 --- [        Gax-108] c.g.c.b.storage.v1beta2.StreamWriterV2   : Received done callback. Stream: projects/xxxxxxx/streams/Cic2MzhjYTEyYS0wMDAwLTJkNzYtYmQ5MC0zYzI4NmQ1MDI4ZmE6czA Final status: com.google.api.gax.rpc.PermissionDeniedException: io.grpc.StatusRuntimeException: PERMISSION_DENIED: Permission 'TABLES_UPDATE_DATA' denied on resource 'projects/xxxxxxx' (or it may not exist).
[Obfuscated project/resource name]
Jar deployed =  google-cloud-bigquerystorage-2.0.2.jar, which is the managed version from the BOM (spring-cloud-gcp-starter-bigquery)
The code is execute with the active account here below
mbp:~ kgoderis$ gcloud auth list
      Credentialed Accounts
ACTIVE  ACCOUNT
*<EMAIL_ADDRESS>
I verified access through the Policy Troubleshooter of GC Console:

and obviously, the resource does exist. Adding data via the legacy streaming API works perfectly well
What might I be missing here?

Were you able to initialize the client without any issue? This happens only when you're trying to stream data?

Hi, following up on this?

Hi @kgoderis, here you have a temporally fix by adding the '"x-goog-request-params"' header
Also there is the BEAM issue and a PIT case related to that


Add keyboard shortcuts.

Use by default the same keybindings as oblogout:
cancel = Escape
lock = K
logout = L
restart = R
shutdown = S

See https://github.com/nikdoof/oblogout/blob/master/data/oblogout.conf

Great idea, Thank you!

Your're welcome! Thanks to you for merging it.


Respect UnsafeValueTypeAttribute

See https://github.com/dotnet/corert/pull/3002#pullrequestreview-27491644

@davidwrighton Do we also need a tracking issue on the TFS side for NUTC?


Restore 'grpc' extra for testing on Python 2.7.

Bump minimum required 'grpc' version to 0.13.1, which supports UCS-4 and UCS-2 builds on Linux.
Closes #1572.

time .tox/py27/pip install gcloud[grpc] call trades off about one second on my machine, in exchange for some DRYness (maintaining the pinned grpcio version only in setup.py).  Until we can just make grpcio an unconditional dependency, that seems like a reasonable tradeoff:  it might even help people figure out how to satisfy the optional dependency.

I am big time :-1: on adding any unnecessary time to running our test suite. Running tests is one of the biggest barriers to contributing.

On my machine, with this change:
$ time tox -e py27
GLOB sdist-make: /home/tseaver/projects/agendaless/Google/src/gcloud-python/setup.py
py27 inst-nodeps: /home/tseaver/projects/agendaless/Google/src/gcloud-python/.tox/dist/gcloud-0.12.0.zip
py27 installed: -f file:///home/tseaver/.pip/wheels,cffi==1.5.2,cryptography==1.3.1,enum34==1.1.2,futures==3.0.5,gcloud==0.12.0,googleapis-common-protos==1.1.0,grpcio==0.13.1,httplib2==0.9.2,idna==2.1,ipaddress==1.0.16,linecache2==1.0.0,nose==1.3.7,nose-exclude==0.4.1,oauth2client==2.0.1,protobuf==3.0.0b2.post2,pyasn1==0.1.9,pyasn1-modules==0.0.8,pycparser==2.14,pyOpenSSL==16.0.0,rsa==3.4.2,six==1.10.0,traceback2==1.4.0,unittest2==1.1.0
py27 runtests: PYTHONHASHSEED='4256048390'
py27 runtests: commands[0] | pip install gcloud[grpc]
Requirement already satisfied (use --upgrade to upgrade): gcloud[grpc] in /home/tseaver/projects/agendaless/Google/src/gcloud-python
----------------------------------------------------------------------
# elided
Ran 1835 tests in 0.864s

OK
___________________________________ summary ____________________________________
  py27: commands succeeded
  congratulations :)

real	0m8.512s
user	0m7.338s
sys	0m0.975s

With explicit dependencies:
$ time tox -e py27
GLOB sdist-make: /home/tseaver/projects/agendaless/Google/src/gcloud-python/setup.py
py27 inst-nodeps: /home/tseaver/projects/agendaless/Google/src/gcloud-python/.tox/dist/gcloud-0.12.0.zip
py27 installed: -f file:///home/tseaver/.pip/wheels,cffi==1.5.2,cryptography==1.3.1,enum34==1.1.2,futures==3.0.5,gcloud==0.12.0,googleapis-common-protos==1.1.0,grpcio==0.13.1,httplib2==0.9.2,idna==2.1,ipaddress==1.0.16,linecache2==1.0.0,nose==1.3.7,nose-exclude==0.4.1,oauth2client==2.0.1,protobuf==3.0.0b2.post2,pyasn1==0.1.9,pyasn1-modules==0.0.8,pycparser==2.14,pyOpenSSL==16.0.0,rsa==3.4.2,six==1.10.0,traceback2==1.4.0,unittest2==1.1.0
py27 runtests: PYTHONHASHSEED='1552785647'
# elided
Ran 1835 tests in 0.861s

OK
___________________________________ summary ____________________________________
  py27: commands succeeded
  congratulations :)

real	0m7.543s
user	0m6.394s
sys	0m0.947s

which is a net cost of one second:  hardly worth arguing about.

I understand the DRY objection but the whole point of using tox is avoiding calling pip install in these cases. The check/install/run flow is not optimized for us manually calling pip install.

The "wart" (invoking the extra explicitly) will go away once we can safely just depend on grpcio for all supported Python versions.  And again, we are talking about one second of wall clock time here per Python 2.7 tox environment:  compared to the possibility of having the pinned grcpio version drift between setup.py and tox.ini, that seems like a good tradeoff.

OK go ahead and merge


track external Istiod promotion WIs to beta

Low priority ones are not part of the beta criteria:
Process:

[ ] supportability review (M)

Features/Fixes:

[ ] enable CRD flag (M) @irisdingbj

(WIP) https://github.com/istio/istio/pull/27115

[ ] proper API for istiod custom host (M) @linsun
[ ] external istiod secret reload (L) @irisdingbj
[ ] vm integration (L)
[ ] Finish multi-network simplification (eliminate need for MeshNetworks)

(Merged, #25554) Implement Simplify Multi-network Configuration
(WIP) Implement Decouple Cross-Network Gateways from Clusters

[x] Add a cross-cluster-gateway deployment to use instead of istio gateway

E2E Testing:

[ ] external istiod upgrade test for single cluster (H)
[ ] external istiod single cluster install test and simple istio functionality test (H) @irisdingbj
[ ] external istiod multicluster install test and simple istio functionality test (M) - Depends on multicluster beta graduation
[ ] external istiod single cluster no loss of function on istioctl commands (H) @esnible
[ ] Convert Telemetry E2E tests to be “multicluster-aware” @gargnupur

#26888

[ ] Convert Security E2E tests to be "multicluster-aware"

#25054

[ ] Convert Networking E2E tests to be "multicluster-aware @stevenctl

#24581

Docs:
Each task here also includes providing an automated test for the document on istio.io.

[x] New multicluster install docs @nmittler
[x] Update plug-in CA docs @nmittler
[ ] Task for cluster-local services
[ ] Task for how to drain a cluster
[ ] Task for removing a cluster
[ ] external istiod install documentation (H) @linsun
[ ] external istiod upgrade documentation (H) @linsun

cc @ostromart @irisdingbj @esnible @sdake @costinm @nmittler @stevenctl

@linsun can you clarify why external istiod is on this list at all? I thought we had agreed that external istiod (i.e. config cluster) would not be part of multicluster beta (i.e. istio 1.8)?

@linsun I've reworked this significantly.  This seemed to be missing a lot of items from https://docs.google.com/document/d/1eskMB7OUwSvL_keTsQa3BWRmHAmGkWwUWsKCfBLk1V4/edit#.

@linsun why is VM integration part of this? VMs are a different team.

@nmittler regarding your q for vm integration... it was only listed as (low priority) because during external istiod beta promotion doc review, @costinm indicated he is interested in working on this.

My concern with "no loss of function on istioctl commands" is proxy-status.  When istioctl connects to istiod it gets a random pod.
Most or all of the fix for this must be done on the server side.  There is no approved design for this and the issue has been stuck for a long time without concensus.

Thanks @esnible!  On the bright side, I don't use proxy-status very often these days.  So istioctl ps currently works with external istiod if I configure xds-server or endpoint, does it connect to a random external istiod vs each of the istiod?  Any major issue with connecting to a random istiod in the past (even for in cluster istiod)?  I haven't heard much complaint about it.
Also, Is #24703 same as the new troubleshooting API?

istioctl can be told to use the XDS version of proxy-status.  It doesn't look up the XDS endpoint so it fails if the user is doing an external control plane canary.  It doesn't consult all the Istiods so it may fail if there are >1 istiod pod.
Work can be done on the client if we need to support external control plane canary.  I can do that work.
My current idea for the server is a work-around.  Cloud providers can redirect traffic on the control plane cluster so that traffic from istioctl goes to a "facade" microservice instead of real istiod.  This facade microservice would invoke all the Istiod pods and combine the results.  This work could be contributed to the Istio Ecosystem if there was interest in making proxy-status work with external high available >1 pod istiod.

We don't know if we need external istiod canary atm.  We do know we will recommend users to use revision upgrade to upgrade from in cluster istiod to external istiod.  (see https://github.com/istio/istio/issues/29304).
@esnible do you see any other issue if we don't need external istiod canary?
cc @rvennam for input.


Roll engine eb7abf28e439..46b2e3d9a313 (2 commits)

git@github.com:flutter/engine.git/compare/eb7abf28e439...46b2e3d9a313
git log eb7abf28e439..46b2e3d9a313 --no-merges --oneline
2019-10-10<EMAIL_ADDRESS>Roll src/third_party/skia 76826fc91c0a..fe23b1de9ed0 (4 commits) (flutter/engine#13050)
2019-10-10<EMAIL_ADDRESS>Ignore thread leaks from Dart VM in tsan instrumented builds. (flutter/engine#13049)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Auto-roller completed checks. About to merge.


Exporting pipeline logs to backends other than elastic

Describe your use-case which is not covered by existing documentation.
Hello, first of all thanks for the awesome plugin! It solves a lot of problems when it comes to observability in Jenkins.
I have a question, the page "Build Logs" mentions that pipeline logs can be stored in backends other than elastic:
https://github.com/jenkinsci/opentelemetry-plugin/blob/master/docs/build-logs.md#can-pipeline-logs-be-stored-in-other-backends-than-elastic
But how to set that up? I have an otel-collector instance running with the following config:

otel-config.yml
receivers:
  otlp:
    protocols:
      grpc:
      http:
        cors:
          allowed_origins:
            - "*"

processors:
  batch:
  memory_limiter:
    check_interval: 1s
    limit_percentage: 65
    spike_limit_percentage: 20
  resourcedetection:
    detectors: [gcp]
    timeout: 10s

exporters:
  logging:
    logLevel: info
  googlecloud:
    retry_on_failure:
      enabled: false
    log:
      default_log_name: otel-collector

service:
  pipelines:
    metrics:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [googlecloud]
    traces:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [googlecloud]
    logs:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [googlecloud]

I don't see any errors but I also don't see any logs. It's not clear to me if pipeline logs are pushed to the OTLP endpoint by default; when setting up a "Custom Observability Backend", there is no choice given as to where the pipeline logs should be stored.
Would it be possible to clarify this in documentation?
Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.
See above

Please see updated documentation https://github.com/jenkinsci/opentelemetry-plugin/blob/master/docs/build-logs.md#can-pipeline-logs-be-stored-in-other-backends-than-elastic
Please note that there is a limitation in the visualization, it's explained in the docs. Contributions are welcome to fix the gap.

Hello @vlad-ivanov-name, it's a limitation of Jenkins APIs that prevented us from offering the option to store the pipeline logs both in the observability backend and in the Jenkins home.

Thanks for the feedback @vlad-ivanov-name . Contributions to retrieve logs from Google Cloud are welcome. I'll be happy to assist any contributor to implement this.


Backing up the WAL

Hi @drmingdrmer do you guys back up the WAL or the snapshot somewhere in datafuse ? I am trying to figure out how to make it easy for us to stream the WAL to S3 so that if we lose the nodes we can bootstrap the cluster without losing the source of truth of the data in the state machine

In databend, we just export all of the log and the snapshot to a file and backup it. The following is the server side export implementation:
https://github.com/databend/databend/blob/313b40ed3ff1cfe001bc6e2f806773d9001861d0/src/meta/service/src/store/store_inner.rs#L394

@drmingdrmer Do you do this in a continuous basis for databend or is this happens after every couple of hours?

@drmingdrmer Do you do this in a continuous basis for databend or is this happens after every couple of hours?

It is a cronjob and is executed by schedule. It is not a incremental backup :(

Hi @drmingdrmer, would you be open to incorporating that logic into openraft? This way, users wouldn't have to replicate the same work.

Just my 2c: I don't think there is a generic way to back up logs. We'll also back up to S3, but that's just one of the options. We must support 5 different hyperscalers, all with different APIs. From openraft POV, the log is continuous and how you cut it for backup is your beer. In our case, once a log segment is filled, it can be backed up. Once openraft tells us to purge, it's removed locally (unless the backup didn't yet finish).


package.json and tsconfig.json files are written as a single line

When creating a project, the package.json and tsconfig.json files are written to a single line
Expected: Both json files should be printed multiline
Steps to reproduce:

Create a new project with any settings
Note that the package.json and tsconfig.json files that are written exists on a single line.

Fixed on v1.0.3

Perfect, thank you!


Create def bit_at(n, bit):     return (n>>bit) & 1

you have not used any extension with your file.
use correct file extension.
Your file name should be solutionByPreeti.py
Closing this pull request. You can add another PR for the question


In Light mode, it is recommended to remove or improve the white border. This seems too coordinated. Also allow custom fonts and background colors? Can the CMD window be opened by default?

Environment
Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Expected behavior

Actual behavior

In Light mode, it is recommended to remove or improve the white border. This seems too coordinated.
Also allow custom fonts and background colors? Can the CMD window be opened by default?
Light 模式下建议将白色边框去除或改进，这个看起太协调了，
另外可以允许自定义字体和背景色？可以自定义默认开启CMD窗口吗？

 This seems too coordinated.

You can change the border color across all of Windows in the Personalization settings.

Also allow custom fonts and background colors?

You can set any color scheme you want in the Settings file. You can set any fontFace you want in the Settings file.

Can the CMD window be opened by default?

You can set any "default profile" you want in the settings file.

Although it can be achieved more, but it is not very aspect, should not be bundled with the system
------------------ 原始邮件 ------------------
发件人: "Dustin L. Howett<EMAIL_ADDRESS>发送时间: 2020年5月4日(星期一) 凌晨4:24
收件人<EMAIL_ADDRESS>抄送: "青春！"<395053994<EMAIL_ADDRESS>主题: Re: [microsoft/terminal] In Light mode, it is recommended to remove or improve the white border. This seems too coordinated. Also allow custom fonts and background colors? Can the CMD window be opened by default? (#5721)
In Light mode, it is recommended to remove or improve the white border. This seems too coordinated.
You can change the border color across all of Windows in the Personalization settings.
Also allow custom fonts and background colors?
You can set any color scheme you want in the Settings file. You can set any fontFace you want in the Settings file.
Can the CMD window be opened by default?
You can set any "default profile" you want in the settings file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Don't show custom errors pane if it is disabled in settings

It is quite annoying to see opened errors pane with "No issues" label for non-dart or even for dart projects on the first editor launch.

thanks! lgtm


Chronos with Symfony2

Hi all,
I have an issue with my chronos. Chronos calls a command from Symfony which calls a Symfony's service. But it returns an error "file get content is empty".
When i remove the Symfony's service, i have a job success. Otherwise i have job failure.
Anyone can help me ?

Hey,
we are running Chronos with Symfony Console. And it works very well.
I want to help you, but your issue contains to less information.
Can you please post your Job definition and an example source code?
The Mesos + Chronos Version as well, please
Maybe this can help.

Hey, I think it is not a problem anymore, 1 year after it can be closed, right?

Hello,
Yes, the issue can be closed !
2015-10-02 0:04 GMT+02:00 Diogo Gomes<EMAIL_ADDRESS>
Hey, I think it is not a problem anymore, 1 year after it can be closed,
right?
—
Reply to this email directly or view it on GitHub
https://github.com/mesos/chronos/issues/231#issuecomment-144862469.


[vcpkg_acquire_msys] Use Mirrors

This PR adds mirrors to vcpkg_acquire_msys() to handle when the primary source is down.
The sourceforge mirror is not used because it only keeps the latest packages, whereas the other mirrors appear to have the same contents as the primary source.

Still not working for protobuf:arm64-windows


ERROR about "Build a MediaPipe Android example."

System information (version)
Linux OpenCV = 4.2.0
Operating System / Platform = Windows 64 Bit WSL2(ubuntu20.04)
Android OpenCv =4.2.0
Android SDK = latest
Android NDK = r21e
Detailed description
I successfully ran a c++ example of Hello World in WSL. However, when I tried to build a MediaPipe Android example in WSL, I encountered an error.
ERROR: /home/jim/.cache/bazel/_bazel_jim/9ded6e7e7b0b353b7548db4c7484a645/external/android_opencv/BUILD.bazel:14:12: SolibSymlink<EMAIL_ADDRESS>failed: missing input file 'external/android_opencv/sdk/native/libs/arm64-v8a/libopencv_java3.so', owner: '@android_opencv//:sdk/native/libs/arm64-v8a/libopencv_java3.so'
ERROR: /home/jim/.cache/bazel/_bazel_jim/9ded6e7e7b0b353b7548db4c7484a645/external/android_opencv/BUILD.bazel:14:12: SolibSymlink<EMAIL_ADDRESS>failed: 1 input file(s) do not exist
Target //mediapipe/examples/android/src/java/com/google/mediapipe/apps/objectdetectiongpu:objectdetectiongpu failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /home/jim/.cache/bazel/_bazel_jim/9ded6e7e7b0b353b7548db4c7484a645/external/android_opencv/BUILD.bazel:14:12 SolibSymlink<EMAIL_ADDRESS>failed: 1 input file(s) do not exist
INFO: Elapsed time: 0.328s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
FAILED: Build did NOT complete successfully
I have not found relevant solutions so far.

Hi @Javacr, Could you provide the complete steps to reproduce the issue and more details about the issue. Thank you!

Hi @Javacr, Could you provide the complete steps to reproduce the issue and more details about the issue. Thank you!

Thank you for your reply. I have solved the problem, the main reason is that I use android opencv 4 in WORKSPACE. When I changed to Android OpenCV 3, the APK build was successful.

Hi @Javacr, Good to hear that the issue has been resolved. Could you move this issue to close status as it doesn't need further assistance. Thank you!


Build a delete_prefix in C and compare speeds

11.8.7. Optimal Loading of Row Keys
When performing a table scan where only the row keys are needed (no families, qualifiers, values or timestamps), add a FilterList with a MUST_PASS_ALL operator to the scanner using setFilter. The filter list should include both a FirstKeyOnlyFilter and a KeyOnlyFilter. Using this filter combination will result in a worst case scenario of a RegionServer reading a single value from disk and minimal network traffic to the client for a single row.
http://hbase.apache.org/0.94/book/perf.reading.html