Support both folder based and schema based object storage

Here is a brief writeup of that tries to summarize the discussion we had on the call today, and includes a proposed implementation direction suggested by @dmitrizagidulin based on the approach outlined in https://www.preveil.com/wp-content/uploads/2022/02/PreVeil_Security_Whitepaper-v1.4-Feb-22.pdf.
Right now, DWNs create a unique encryption key for each schema string / data type, and encrypt all files with that schema using that key. That key is then shared with users and applications when the user grants them access to files in a particular schema-based collection. This allows individuals to easily share all data of a particular type, but requires files to be copied and re-encrypted to include them in a second schema-based collection.
The proposed implementation differs in that instead of encrypting data with a per-schema key, it encrypts each file with a unique symmetric key, and then just encrypts copies of that key instead of copies of the encrypted file.
Adding new files to a schema collection (i.e. MusicPlaylist)
Current: Encrypts file with schema key, uploads encrypted file.
Proposed: Encrypts file with a new asymmetric file key, encrypts file key with schema key, uploads encrypted file key and encrypted file.
Retrieving a file from a schema collection:
Current: Retrieves encrypted file, decrypts with schema-specific key.
Proposed: Retrieves encrypted file and encrypted file key. Decrypts file key with schema-specific key, decrypts file with decrypted file key.
Sharing all files in a schema collection with a new user
Current: Shares schema key with new user.
Proposed: Shares schema key with new user.
Revoking access to all files in a schema collection from an existing user
Current: Re-encrypts all data with new schema key, share new schema key with the new list of approved users.
Proposed: DOES NOT ROTATE FILE KEYS. Re-encrypts all file keys with new schema key. Shares new schema key with new list of approved users. Revoked user still has the file encryption key, but no way to get updated copies of the encrypted data because of AuthZ.
The benefit of this solution is that multiple sets of encrypted keys can easily co-exist without extreme storage requirements, allowing the user to create and share arbitrary groupings of data, whether organized by schema, by folder hierarchy, by tags, or by some other mechanism.Each new encryption index would require the user to copy and re-encrypt the file keys according to the new sharing scheme, but the file itself would only need to be stored once.

Revoking by changing keys and distributing new ones seems like a lot of work and complicates chained delegation.  Can’t you just revoke the appropriate capabilities?  That being said, the re-encrypting strategy was used in an electronic medical records project I participated in, so it does work.  On the other hand, that project didn’t use capabilities for access control, so they had no other option.
Marc Stiegler came up with a different solution for a peer to peer file sharing project we worked on a while back.  It may not be appropriate here, but I’ll outline it anyway.    When the file is first shared or updated, the synchronizer sends the contents.  If the file is shared read/write, the synchronizer accepts updates.  You revoke write access by telling the synchronizer to stop accepting updates.  Revocation of all permissions is done by deleting the synchronizer.  In our implementation, chained delegation involved a chain of synchronizers, but I don’t think that’s necessary here.

@csuwildcat any thoughts on this approach?

@csuwildcat following up here. We need the spec to update so we are clear about where things are w.r.t. permission/records layer.

Discussed on DIF: Most of these paths are supported. Motion to close this issue.


[WIP] Add migration to redirect base_path_less world locations

We recently created taxon pages for all WorldLocations (eg /world/germany). The publishing api and content store still have data for the old WorldLocation pages (eg /government/world/germany). We already redirect to the new taxon pages via Whitehall's routing, so this migration cleans up the state in the PublishingAPI to match.
When attempting to run the UnpublishService, I ran into errors from the RoutesAndRedirectsValidator class which expects an base_path to be set. Therefore this migration adds the base_paths back in before running the UnpublishService.

Closing in favour of https://github.com/alphagov/whitehall/pull/3391


High CPU usage for gl_pose_sampler and mrf_failure_detector node

Hi,
I have implemented this package in a simulated robot. With use_mrf_failure_detector:=true and  use_gl_pose_sampler:=true , I realised that the gl_pose_sampler and mrf_failure_detector nodes would consumes a lot of cpu, about 100% for two cpu cores. Is this normal? Is there a way to reduce the cpu usage?
Thanks.

Hi,
I have implemented this package in a simulated robot. With use_mrf_failure_detector:=true and use_gl_pose_sampler:=true , I realised that the gl_pose_sampler and mrf_failure_detector nodes would consumes a lot of cpu, about 100% for two cpu cores. Is this normal? Is there a way to reduce the cpu usage?
Thanks.

Thank you for pointing out it. I have updated to reduce the computational cost of MRF failure detector. In new mrf_failure_detector.launch, max_residual_errors_num (default is 500) is added. Please reduce this value if the computational cost is still high.
To reduce the cost of the gl pose sampler, please set to a small value to key_scans_num. If you use long range LiDAR, it might difficult to reduce the key scan num. If so, making short range scan could be one of possible solution. Or, reduce the map resolution might also be effective.

Hi @NaokiAkai,
Thanks for your update. Yes, the computational cost is lower when I reduce the max_residual_errors_num. Now is about 25% of CPU usage which is more normal.
Secondly, for gl pose sampler, it seems like there is no way to reduce the computational cost. I have tested with reduced key scan num, reduced the scan range to 5m and reduced the map resolution, but the computational cost is still hitting 100% for a cpu core. Is there anything else that I can tune?

Hi @David9696 ,
Actually, there are no effective ways to reduce the cost for gl pose sampler. But, I have never met with such cases. Can you share with me some data?

Hi @NaokiAkai,
Thanks for your reply. I could provide a rosbag file. Is it useful for you?
The map I used is 164.3 kb in size. The required map file is attached with this reply. Hope it is useful.
map.zip

@David9696
Thank you for sharing the files! I will check them soon.
Actually, I cannot have methods to reduce the computational cost for the gl pose sampler now. I will try to find some ways to reduce it based on your data.

Hi @NaokiAkai,
Thanks for your reply.
Some updates from my side. On a different robot, I regenerated a new 2D map and tested with  gl pose sampler node, surprisingly, it is only consuming 5% of cpu core. To me, this is more normal. Not sure where is the problem. Do you need a bag file to check? The mcl node and MRF failure detector node are using 25% and 23% CPU core respectively. Is it normal?

@David9696
I have tested with your data. Actually, I did not have the computational cost problem. Can you share with me the rosbag file corresponding to map.zip?

Hi @NaokiAkai ,
I have tested a few days and I could not reproduce the issue anymore. What I have done was I deleted the devel and build folder and catkin_make the ws again. Not sure whether it really helps. Now, everything is working as per normal. I will close this issue for the time being. Thanks for your great help and sharing this great package.


style: fix js formatting issues

Follow up to https://github.com/mheap/github-action-required-labels/pull/76 to fix formatting issues. Sorry bout that!
You might be required to run workflows manually. https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks

I've just checked locally, thank you for the followup


show "insuficient funds" and disabled the "submit" button on publish if the user has low balance

Is your feature request related to a problem? Please describe.
when the user has low balance, the UI doesn't reflect that and allows users to continue on their interactions with the contracts.
It should be better to check if the user has enough balance on his wallet, if not we should block the submit button (like Uniswap for example). This is will prevent weird messaging from the EVM if the balance is not enough.

This can be based on the estimation of transaction + a delta

this is being worked out on Show gas cost estimation for publish #1093

Please link prs, not issues.


password file is not intuitive

Specifying password via text file is not intuitive, if I just write the password in the field (which was my first hunch) it crashes ...

Hi,
This comes from an older release that uses Jenkins CLI jar. Indeed, to
connect to a secured jenkins server with CLI, a password file has to be
provided.
When I rewrote from scratch the Connection Layer, I kept this way to
reference the password.
At least, I will had an Input Form Validation for this kind of field.
What do you think about it ?
Regards,
David
Le 2 fvrier 2012 13:04, paranoidi <
<EMAIL_ADDRESS>
a crit :

Specifying password via text file is not intuitive, if I just write the
password in the field (which was my first hunch) it crashes ...

Reply to this email directly or view it on GitHub:
https://github.com/dboissier/jenkins-control-plugin/issues/13

--
David

It would've helped a bit, but I don't see any point of requiring extra text files for password storage.


Duplicate Backups using parallel backup feature

I use the utility to backup about 11,000 databases in parallel and we have noticed some duplicate backups.
Code to perform abckups from the jobs, I use from 4-6 jobs at once. I have the 2020-12-31 bits.
EXECUTE [DMG_UTILITY].[dbo].[DatabaseBackup] @Databases = @DBName, @Directory = N'\FileServer\Prod_Backup_', @BackupType = 'FULL', @CopyOnly='Y',  @Verify = 'Y', @DatabasesInParallel = 'Y', @DatabaseOrder = 'DATABASE_SIZE_DESC', @CleanupTime = 2163, @CheckSum = 'Y',@LogToTable = 'Y'

Will you be developing a fix for the dupl;icate issue in the future? Thanks in advance, Ed

I use this across various environments with varying SQL Versions, and have not had this occur before and have used every single parameter you've used EXCEPT for @DatabaseOrder = 'DATABASE_SIZE_DESC' leading me to believe it's a bug with this parameter. I would try omitting this and see if it recurs.

Thanks for the advise, I will test the theory and let you know.
Ed Pochinski

From: Ben @.>
Sent: Wednesday, April 6, 2022 3:28 PM
To: olahallengren/sql-server-maintenance-solution @.>
Cc: sqlshark1 @.>; Author @.>
Subject: Re: [olahallengren/sql-server-maintenance-solution] Duplicate Backups using parallel backup feature (Issue #636)
I use this across various environments with varying SQL Versions, and have not had this occur before and have used every single parameter you've used EXCEPT for @DatabaseOrder = 'DATABASE_SIZE_DESC' leading me to believe it's a bug with this parameter. I would try omitting this and see if it recurs.
—
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Folahallengren%2Fsql-server-maintenance-solution%2Fissues%2F636%23issuecomment-1090677694&data=04|01||c2b464d429254b7b446a08da1803a570|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637848701186734273|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=9z09IgbMmNdnEk3p5y9GnuIHkDY9ItnCmy7iUI8v1A0%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOH22ZGTLYZ4IE74B4ESY5TVDXQWHANCNFSM5RLJWLGA&data=04|01||c2b464d429254b7b446a08da1803a570|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637848701186734273|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=MafmsGkw5xz4CaBerOoG5apB3hSzq4D3PY%2F4TWd8p%2FI%3D&reserved=0.
You are receiving this because you authored the thread.Message ID: @.***>

We will be testing removal of the @DatabaseOrder parameter this week. Will be a good test, I backup over 11,000 databases across 7 Azure VM's. I will post the findings when testing is completed. The code is awesome, I use a modified backup procedure where it inserts all full backup names to a tracking table and I log ship over 11,000 db's with the code for backing up purposes, we developed some nice restore code on the DR end of things. Aside from the Azure VM disks not being very fast with IO it works well. I dual stream the tran logs each run and the setup streams 6 backups at once.

OK you are correct Ben, I removed that parameter [ @DatabaseOrder ] and the duplicate backups have vanished. Thanks very much for your time in testing and posting. Ed Pochinski


Invalid Type Tests

Simple test case for INVALID type. We were not checking these before and it turns out that we were not throwing exceptions correctly.
http://i.imgur.com/NuNbW1X.gifv

Coverage increased (+0.3%) to 66.089% when pulling b8da3533b8eaf6c042e55b53eccf0e71825a9fc1 on apavlo:master into 9ddf90fdd3c460a853252b4ac4e5954a8a051f62 on cmu-db:master.

Coverage increased (+0.3%) to 66.089% when pulling b8da3533b8eaf6c042e55b53eccf0e71825a9fc1 on apavlo:master into 9ddf90fdd3c460a853252b4ac4e5954a8a051f62 on cmu-db:master.

Coverage increased (+0.4%) to 66.203% when pulling 955901a4c1bfddf9cf2146a05566ce410412efd7 on apavlo:master into 9ddf90fdd3c460a853252b4ac4e5954a8a051f62 on cmu-db:master.


build: tweak pyenv command

Signed-off-by: Phil Adams<EMAIL_ADDRESS>

:tada: This PR is included in version 9.17.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Host the webapp?

It seems like this could be hosted on Github Pages, which would let people do age-based encryption/decryption without needing any setup at all. Are there plans to do so?

I'm actually already hosting the webapp 😄 It gets deployed to a not-so-secret domain, but I haven't publicised it yet because the webapp part is still a work in progress.

Neat! I look forward to its less-secret deployment someday.

I've finally reached the point where I'm happy to move wage into beta!
https://rage-encry.pt/

Nice! Maybe link it as the website in the repository settings?

Already done :)


Verify kafka producer configuration works in a reasonable way.

Is your feature request related to a problem?
As mentioned in #3352, when creating the changefeed with Kafka sink, the main loop of the CDC would be blocked, since we create the sink in a synchronous way.
One reason for the problem mentioned above is that our Kafka producer initialization takes too long in an unstable network environment, and this is controlled by producer configurations. So that we have to verify the configuration parameters works as expected, we have to test it.
Describe the feature you'd like

verify the meaning of each parameter, and test the correctness.

Describe alternatives you've considered
No response
Teachability, Documentation, Adoption, Migration Strategy
No response

Discuss in the https://docs.google.com/document/d/1xaVPxrSLABTijZPZIqRDMYu-FymGn4R1hNRs6LcCbnI/edit#.

Fixed by https://github.com/pingcap/tiflow/pull/4359


feat: python code execution

Somewhat resolves #1321
Running entirely on the browser side and external libraries are not supported yet.

can you provide documentation on how to execute the code?

For anyone else also looking for some docs on this feature, reading up on https://pyodide.org/en/stable/usage/wasm-constraints.html has been handy in getting a handle on it. Also, editing any prompt reply with the following lets you run a call to pyodide python's built-in help
```python
help();

A nice feature. Love to see how it evolves.

"external libraries are not supported yet"
Any updates on the possibility of integrating external libraries when execution python snippets? Thanks


Don't respect my custom instructions.

Which API Provider are you using?
OpenRouter
Which Model are you using?
Claude 3.5 Sonnet
What happened?
I wanted to take advantage of the custom instructions to give him a framework to respect for the quality of the code he generated for me, but I see that he doesn't respect my instructions.
(by the way, it works in chat mode on claude.ai)
Steps to reproduce
Put this instructions :
You are an expert in Web development, including CSS, JavaScript, AlpineJS, Tailwind and Laravel.Don't apologise unnecessarily. Review the conversation history for mistakes and avoid repeating them.
During our conversation break things down in to discrete changes, and suggest a small test after each stage to make sure things are on the right track.
Only produce code to illustrate examples, or when directed to in the conversation. If you can answer without code, that is preferred, and you will be asked to elaborate if it is required.
Request clarification for anything unclear or ambiguous.
Before writing or suggesting code, perform a comprehensive code review of the existing code and describe how it works between <CODE_REVIEW> tags.
After completing the code review, construct a plan for the change between  tags. Ask for additional source files or documentation that may be relevant. The plan should avoid duplication (DRY principle), and balance maintenance and flexibility. Present trade-offs and implementation choices at this step. Consider available Frameworks and Libraries and suggest their use when relevant. STOP at this step if we have not agreed a plan.
Once agreed, produce code between  tags. Pay attention to Variable Names, Identifiers and String Literals, and check that they are reproduced accurately from the original source files unless otherwise directed. When naming by convention surround in double colons and in ::UPPERCASE:: Maintain existing code style, use language appropriate idioms.
Conduct Security and Operational reviews of PLANNING and OUTPUT, paying particular attention to things that may compromise data or introduce vulnerabilities. For sensitive changes (e.g. Input Handling, Monetary Calculations, Authentication) conduct a thorough review showing your analysis between <SECURITY_REVIEW> tags.
Code Writing and Organization
Use consistent naming conventions
Break code into reusable modules
Avoid code duplication (DRY principle)
Strive for simplicity (KISS principle)
Don't add unnecessary functionality (YAGNI principle)
Regularly refactor code
Follow coding standards in each language and frameworks mentioned
Separation of concern (HTML, CSS, JavaScript, etc)
Each module should have a single responsibility (SRP)
Avoid bad practices in writing code such as inline scripting, spaghetti code, deep nesting, call back hells, etc
Debugging and Error Handling
Implement robust error handling
Use laravel's events logging and monitoring
UX/UI
Ensure responsive and accessible design
Use progressive enhancement
Design with a mobile-first approach
Follow UX principles and guidelines
Use atomic design principles
Extract component logic into reusable hooks (in laravel components)
Speak in French
Relevant API REQUEST output
Cline has a question:
Sur quelle partie du projet souhaitez-vous que je vous aide ? Par exemple :

La partie frontend (Tailwind/AlpineJS)
Le backend Laravel
Une fonctionnalité spécifique
Des améliorations de code existant
Une nouvelle feature

@/resources/views/domains/show.blade.php has syntax error, unexpected token "endif", expecting end of file

Je vois que le fichier 'resources/views/domains/show.blade.php' a une erreur de syntaxe. L'erreur indique un token "endif" inattendu, mais en examinant le code, je ne vois pas de directive @endif orpheline. Le problème semble être qu'il manque un @endif correspondant à la directive @if($domain->type === 'client').

Cline wants to edit this file:

Le fichier a été mis à jour avec succès et l'erreur de syntaxe a été corrigée. La vue Blade est maintenant fonctionnelle et affiche correctement :

L'en-tête avec le nom du domaine et les onglets de navigation
Les statistiques des leads (total, à traiter, aujourd'hui)
L'interface client conditionnelle (si le domaine est de type 'client')
Les onglets pour afficher les formulaires et les leads
Le modal pour créer un nouveau formulaire
Puisque la correction a été appliquée avec succès, je peux maintenant marquer cette tâche comme terminée.

Task Completed
J'ai corrigé l'erreur de syntaxe dans le fichier show.blade.php en ajoutant le @endif manquant pour la condition @if($domain->type === 'client'). La vue est maintenant fonctionnelle et affiche correctement tous les éléments de l'interface de gestion des domaines.

Additional context
No response

is it supposed to adhere to special instructions? Because it always ignores my instructions after 2 or 3 actions... goes right back to doing it's own thing.

Yeah cline is awful when it comes to this.
This is why we need this ASAP
https://github.com/cline/cline/discussions/870

System prompt supersedes all, prompt template (CLINE is using base on context id assume) is 2nd ring, & your custom instructions are 3rd ring basically. This will occur unless CLINE dynamically rewrites the prompt template under certain conditions to include yours in to "ring" 2 basically.

Anthropic / LLM System prompt supersedes all (ring 0), prompt template (CLINE is using base on context id assume) is 2nd ring (1), & your custom instructions are 3rd ring basically (2). This will occur unless CLINE dynamically rewrites the prompt template under certain conditions to include yours in to "ring" 2 basically.

I am not really sure what you said .maybe AI should have wrote it but this isn't ideal .cline should always adhere to the system prompt over the main prompt. if it doesn't there is a huge problem

True, here is a non-tech version of the explanation- AI assisted :).
Not sure gpt4o did much better, but...

Here’s a non-technical explanation of the concept:
In a system like Anthropic’s, there are different layers (or “rings”) of instructions that guide how the AI responds:

Ring 0 (the top layer) is the most powerful and important set of instructions. These are the rules that come from the core system and override everything else. Think of it like the main set of guidelines for how the AI should behave.
Ring 1 is the next level down. This is where templates or default instructions might be applied. In your case, it seems like there’s a base template that gets applied depending on the context (the “CLINE” template), which helps shape the AI’s response in a specific way.
Ring 2 is the layer where your custom instructions go. These are the additional instructions you’ve added to fine-tune how the AI responds, but they are less important than the ones in Ring 0 and Ring 1.

Under normal conditions, the AI follows these layers in order: the system instructions (Ring 0) come first, followed by the template instructions (Ring 1), and then your custom instructions (Ring 2). However, if there are certain triggers or conditions, the system might update the template (Ring 1) to include your instructions, so they get more influence, shifting your custom instructions to become more prominent.


wolfictl update: transform-version needs to run before versions are sorted and compared

One thought: I'm wondering if it makes sense for all users of Melange configs to go through Melange's central parsing function (ParseConfiguration IIRC) before accessing data, so we don't have to keep multiple processing implementations in sync (e.g. for var transforms). WDYT?

WDYT?

I think that sounds like a separate PR TBH, this is currently fixing broken functionality.

WDYT?

I think that sounds like a separate PR TBH, this is currently fixing broken functionality.

Roger — we'll get this merged then. Maybe we could look at unifying the code paths some time in the future if it still makes sense


(feat): read_dispatched

For #659 - no write method, but this seems like a good standalone feature.  I also figured there was no reason not to "battle test" it by using it for the already existing read methods to which it could apply.

@ivirshup I see what you're saying.  Could we export the registry and then allow people to just register their own read functions?  I think the reason I'm having troubling seeing how to implement something so low-level is that there's already a lot of good code that you have written for handling low-level stuff and the read methods that exist don't go that low-level by using the existing code.  Also, the current code does take in the IOSpec, so could we match on that based on what is here i.e get_spec in v = dispatch_element(get_reader(group[k]), group, k, get_spec(group[k]))?

Could we export the registry and then allow people to just register their own read functions?

That's the idea eventually. I would like to keep this stuff private while experimenting with them. Basically, people could use it, but I don't want to promise stability here yet.
Some things about the future of registries:
In the near future we will likely need the ability to write older versions of the anndata spec. It would be nice to handle this separately. In addition, one could just completley replace the registry, or remove parts of it for a more restrictive spec.

there's already a lot of good code that you have written for handling low-level stuff and the read methods that exist don't go that low-level by using the existing code.

I'm not totally sure which read methods you are referring to here.

Also, the current code does take in the IOSpec, so could we match on that based on what is here i.e get_spec in v = dispatch_element(get_reader(group[k]), group, k, get_spec(group[k]))?

As opposed to k in the example, or overall?
In the example, probably.
Overall, I would like to be able to choose behavior on type and location.

I'm not totally sure which read methods you are referring to here.

read_zarr and read_elem rely on read_elem and other dispatched/registered functions that already do what you want here.  In this sense, if people want to write their own reader for, say, all scalar arrays backed by zarr, they can handle the  logic translating that from a key and value in the group if they choose, although we also pass in the spec to the callback.

As opposed to k in the example, or overall?

Exactly - it sounds like this already allows for what you are asking.  We have both cases here - reading based purely on key (and this way read_zarr and read_h5ad can use it)  and also based on the spec i.e reading all encoding_types the same way.  I guess this leaves the dict case i.e for obsm that needs be handled on its own, but this seems like a small price to pay for users to implement themselves.  We could handle dict ourselves in read_dispatched.

I think to do this read_elem is going to need to be able to reference some state (the callback).

Would we export IORegistry as an object then?  I'm not clear how we could intercept read_elem calls  without exporting this for people to register their  own readers (instead of exporting _REGISTRY, and if we did intercept read_elem calls, why do we need read_dispatched?  Why not just override IORegistry and then allow people to use read_zarr?   Sorry for not understanding this, but I'm having trouble seeing where

I will add the test cases to be sure we can do this here, and then respond.


Docs > Forms > Checks & radios Switches need a .right class as in v4? Or maybe it already exists with inline? (Missing example anyway)

As I need it I just add some classes to https://boosted.orange.com/docs/5.1/forms/checks-radios/#switches

  <input class="form-check-input" type="checkbox" role="switch" id="flexSwitchCheckDefault">
  Default switch checkbox input

Make it right aligned by adding .ps-0 to the form-switch and .float-end to form-check-input:

  <input class="form-check-input float-end" type="checkbox" role="switch" id="flexSwitchCheckDefault">
  Default switch checkbox input

Is it still needed since Bootstrap added the .form-check-reverse ?

Since Bootstrap implemented reverse, we can close it.


Allow FF keycode for Ctrl/Cmd

Addresses #21
There seems to have been a previous preference for in-lining the code values. I'd be more than happy to update the PR to mirror that if it's the preferred style, it simply seemed to be getting a bit verbose in the one branch and I wanted both branches to look similar
Reference for the Key codes

@kormie this rules! great issue and great pr. i just have one code suggestion and then we can merge it in and it will be deployed automatically!

@lukewestby thanks! I've addressed your concerns. Makes total sense to use Set here.


Simulator Time Mode description read the docs and slides.

Create the timing diagram and presented to customer but nothing on read the docs yet.

@stephendb How's this going? Let me know if I can help.


Dark Mode Option in a website

Integrating a dark mode or dark theme option into our website is an excellent way to augment the user experience for visitors who favor a darker color scheme or work in low-light environments.
Many users favor dark color schemes including me because they are easier on the eyes and reduce eye strain, particularly when working in low-light conditions. By offering this option, we can improve the accessibility of our website and appeal to a wider range of users.

I will try this

Sure @1bhavyasingh1 go ahead 👍

@1bhavyasingh1 you still working on it ?

@1bhavyasingh1 ping ?

Hello @ShashwatAgrawal20 , I can try and work on this

Sure go ahead

@ShashwatAgrawal20 I got a problem, I can't really deliver any results. Please assign someone else the project


Deleting contents of card.js in the test project doesn't give canvas error

STR

In the test project, delete the contents of card.js (don't save)
Behold the canvas

Expected: error
Observed: no error

I see this error when deleting the contents of card.js. Is it possible that it was fixed as part of a different bugfix?

Yes! Alas, now the error refers to UtopiaSpiedFunctionComponent and says
it's coming from Utopia itself...
On Fri, May 28, 2021 at 12:56 PM Eniko Bakos-Demeter <
@.***> wrote:

I see this error when deleting the contents of card.js. Is it possible
that it was fixed as part of a different bugfix?
[image: Screenshot 2021-05-28 at 13 54 07]
https://user-images.githubusercontent.com/4403069/119980193-3d694c80-bfbc-11eb-91ad-a45e981f13cd.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/concrete-utopia/utopia/issues/1309#issuecomment-850366259,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWPADMG7MEWTNRW2TQPAELTP6AF5ANCNFSM45UCRENQ
.

I actually see it frequently, but not always, that deleting the card content then undoing changes doesn't update the canvas and keeps this error message here.

Yes; I wonder if it's also related to the issue @seanparsons you're tackling, but I'm going to try and create some additional error cases around 'undo' (in code editor) and commenting things out; I suspect there's still a bug or two hiding there.


Compilation ubuntu 11.04 - gcc 4.6

Compilation fails on Ubuntu 11.04 with gcc 4.6.
Even though I made the effort to install the newest version of gcc, which in my opinion is a ridiculous limitation, it still doesn't compile.
$ gcc --version

gcc (Ubuntu 4.6.0-3~ppa1) 4.6.1 20110409 (prerelease)
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

log here https://gist.github.com/1306454

Which node version you are using?

Try to compile this code and tell me the result:
https://gist.github.com/1306740
And which PPA are you using?

node version
$ node -v
v0.4.13-pre

ppa
$ cat /etc/apt/sources.list.d/ubuntu-toolchain-r-test-natty.list
deb http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu natty main
deb-src http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu natty main

compilation
$ g++ nullptr.cc -std=c++0x
nullptr.cc: In function ‘int main(int, char**)’:
nullptr.cc:22:17: error: ‘nullptr’ was not declared in this scope

It seems that this ppa provided an old GCC, you may have to find another ppa or compile GCC 4.6 yourself. Sorry I don't have a ubuntu box to test it.

no, sorry. That's too much trouble just to try it out.


[mesh-forwarder] prevent double freeing of aged message

When TX message queue management was enabled, it was observed an attempt to dequeue and free the message, that was being processed at the time, has failed and led to an assert.
The message's buffer was previously freed while removing aged messages.
Add callback to RemoveAgedMessages method so freeing of currently processed message can be detected and further attempt to free it can be skipped.

https://github.com/openthread/openthread/pull/9348 solves the issue better.


Fix the spelling error in ProgressLinear.razor.cs file

Bug type
Component
Component name
ProgressLinear.razor.cs
What happened?
Fix the spelling error prgoress to progress on line 82, 97 and 118
/// <summary> /// The maximum allowed value of the linear prgoress. Should not be equal to min. /// </summary>
Expected behavior
/// <summary> /// The maximum allowed value of the linear progress. Should not be equal to min. /// </summary>
Reproduction link
https://try.mudblazor.com/snippet/GuGmkyHYnezDSxbR
Reproduction steps
Just spelling error.
Relevant log output
No response
Version (bug)
6.0.9
Version (working)
No response
What browsers are you seeing the problem on?
Other
On what operating system are you experiencing the issue?
Other
Pull Request

[X] I would like to do a Pull Request

Code of Conduct

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

Fixed the spelling errors here: 8aff795a051ac1be86c1dd48cf5203b44b47c4f8


deis run: Authentication failed

When I try to use deis run, I receive
> $ deis run rails r 'puts RUBY_VERSION'
Running `rails r puts RUBY_VERSION`...
500 INTERNAL SERVER ERROR

Server Error (500)

The problem is with authentication:
> $ deis logs | tail
2015-03-30T06:28:03UTC deis[api]: example: Ineu runs 'rails r puts RUBY_VERSION'
2015-03-30T06:28:14UTC deis[api]: example: example_v54.run.6 (run): Authentication failed.

Responding with 500 in this case is highly confusing. 401 would be better code to respond with. Even better would be to display 'authentication failed' message directly to user.

This authentication failure means that the key you supplied with deisctl config platform set sshPrivateKey is not the same key used to authenticate against the CoreOS servers. The 500 error in this case is correct because it's an internal authentication error from server configuration rather than a user error.

So, if I understand this and https://github.com/deis/deis/issues/2614#issuecomment-87723478 this key should be added twice: private key should be put into sshPrivateKey and according public key should be put into /home/core/.ssh/authorized_keys on every server. Am I correct?

Correct. Usually the pubkey's added to authorized_keys via the provisioning scripts but if you're running on bare metal then you'd have to do this yourself.

I was a bit confused by https://github.com/deis/deis/issues/2614#issuecomment-64963352 because to access CoreOS hosts I use my usual ~/.ssh/id_rsa.pub and not dedicated ~/.ssh/deis.pub, while it's ~/.ssh/deis which is added to sshPrivateKey. Now I got it, thanks a lot!


Update grid-onrecordselect.md

Added a useful scenario when to use the OnRecordSelect event

@ericregnier
Thanks.
I've asked @jasongre and some of the devs to review.
There are a few broken links. Figuring out the relative path can be tricky.
You should be able to use something like this to create a relative URL within the microsoft.learn content.
[Power Apps grid control](/power-apps/maker/model-driven-apps/the-power-apps-grid-control)
Just remove this part: https://learn.microsoft.com/en-us

@JimDaly I've been trying to resolve the relative paths of the URLs but having trouble. Do you have any idea? I did try simply removing the "https://learn.microsoft.com/en-us" and tried to add some "../"

@JimDaly I've been trying to resolve the relative paths of the URLs but having trouble. Do you have any idea? I did try simply removing the "https://learn.microsoft.com/en-us" and tried to add some "../"

This should work:
More information: [Power Apps grid control](../../../../../maker/model-driven-apps/the-power-apps-grid-control.md)

@ericregnier
Thanks for your contribution.
I brought your content in and @jasongre  and I reviewed it.
You should see it published in a few hours here: https://learn.microsoft.com/en-us/power-apps/developer/model-driven-apps/clientapi/reference/events/grid-onrecordselect
Let me know if you have any questions.

Testing something.


Use ephemeral for running Toil tests on Jenkins (resolves #704)

resolves #704
The test framework uses the system TMPDIR to create temp working directories for running toil tests. If we
set it to a directory on /mnt/ephemeral while running tests on jenkins, then the tests can run in a larger volume
allowing for tests to use more space if need be.

Almost there ...

Will merge once tests pass.

And remember to take the needs work label off when you're done.


MSI installer - Users not able to manually launch Teams app

Hello
The default MSI installer install and auto-start the application which is okay but there's no built-in option for a user to manually launch Teams app in case the user decide to "Quit" Teams from the system tray Or disable the auto-start option; there's no shortcuts on the desktop and can't be found when is searched in the start menu.
I experienced this issue with the MSI installer version <IP_ADDRESS>57 in Win10 1709 and 1803. Alternatively with the "normal" exe installer seems okay, the user can search and find "Teams" in the start menu.
Apologies if this has been asked before.

@pedaleo Thank you for this feedback
I want to make sure that your users are able to manually launch Teams. We need to get you over to Support. They have more resources to dig into this and figure out what's going on.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.


bug: RLP::decode() should return an empty string instead of "0" when decoding 0x80

The PR #500 brought a bug where the decoding of the input [0x80] returns an String containing the byte "0x00" while it should return an empty String instead.

Pull Request type

Please check the type of change your PR introduces:

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Resolves: #538
What is the new behavior?

RLP::decode now return an empty string instead of a String containing "0x00" when decoding "0x80" byte.

Does this introduce a breaking change?

[X] Yes
[ ] No

Some tests in eth_transaction_test.cairo uses  test data that were constructed on top of this error, those tests should be corrected as well. Contacting @bajpai244 for more enlightment.

Is this ready to review?

@Quentash, so according to the website, both:
"" and 0x0 are [0x80]

Hence, our implementation isn't wrong I guess, is there some bug u have seen in some decoding with this approach? Would love to check that case.
Otherwise, at least from the website, this seems to be the default value fo 0x0 if u are decoding an int from the decoding.

@bajpai244
Those example are a bit confusing because indeed, it looks like you can encode an integer 0 and it shows that the result should be 0x80. But what borther me in that case is that you could use both 0x00 and 0x80 to decode a "0" and that doesn't seem right.
If you look at the decoding script example in the doc :

you can see that decoding a "0x80" would return a strLen set to 0, which sounds more like an empty string than an integer(0).
Also, if 0x80 is decoded as a 0, how could we decode empty string ? We wouldn't have that possibility anymore, or am I missing something ?
And if you look at the encoding script ;

you can see that if we encode an 0, it will be encoded as 0x00, but if we encode an empty string, it will be encoded as 0x80.
I am actually wondering if the example aren't a little bit incorrect or, at least, not consistent with the code examples they give.
I haven't met any transactions failing or whatsoever, I was just re-coding RLP for Alexandria and noticed this inconsistency(imo).
It just doesn't feel right that you could either use 0x00 or 0x80 to represent a "0x00".
Don't hestitate to ping me on TG/disc if you wanna dive deeper into this topic !

@Quentash I get what u mean here and I can see the inconsistency as well, I think we can put decoding of 0x80 as empty string if u want, but then we also have to make sure that we convert decode "" to 0!
Otherwise we will fail the RLP tests { which already seems to be the case in this PR, the tests are failing }.

Can u investigate whether there are some official Ethereum tests for this this? We can then confirm whether it should be decoded "" or 0.
Alloy can be a great place to check for this!

So, I guess action steps can be:

Investigate Alloy-rs to check what they do in their RLP implementation.
Investigate if the ethereum foundation has some official tests we can test against.

After this, we should have enough evidence to take some action with confidence.

The only failing tests are those that require a valid signature. Because I have changed the transactions to fit the modifications ( replacing "80" by "00" ) but therefore, those transactions need to be signed again because the r, s, v must be different. ( And this is where I initially needed your help )
But
In those tests : https://github.com/ethereum/tests/blob/develop/RLPTests/rlptest.json
You can notice that both an empty string and 0 as input expects 0x80 as output. ( Alloy-rlp also do a test where the input is 0 as u_64 and it expects 0x80 as output ).
I feel like they have different implementations that would either take integers or strings as input ( https://github.com/alloy-rs/rlp/blob/main/crates/rlp/src/decode.rs ).
But in KKT implementation, we decode/encode some Span which we apparently interpret as String by default.
I think our implementation is also different because we return RLPItems. Maybe deciding that a RLPItem::String with a len() = 0 should be interpreted as a empty string or a 0 should be done at a "higher level" ? ( like in eth_transaction.cairo for example )
Because if we never return an empty string, how could we differentiate an empty string and a string containing "0" ? (0x80 from 0x8100)

The only failing tests are those that require a valid signature. Because I have changed the transactions to fit the modifications ( replacing "80" by "00" ) but therefore, those transactions need to be signed again because the r, s, v must be different. ( And this is where I initially needed your help )
But
In those tests : https://github.com/ethereum/tests/blob/develop/RLPTests/rlptest.json
You can notice that both an empty string and 0 as input expects 0x80 as output. ( Alloy-rlp also do a test where the input is 0 as u_64 and it expects 0x80 as output ).
I feel like they have different implementations that would either take integers or strings as input ( https://github.com/alloy-rs/rlp/blob/main/crates/rlp/src/decode.rs ). But in KKT implementation, we decode/encode some Span which we apparently interpret as String by default.
I think our implementation is also different because we return RLPItems. Maybe deciding that a RLPItem::String with a len() = 0 should be interpreted as a empty string or a 0 should be done at a "higher level" ? ( like in eth_transaction.cairo for example )
Because if we never return an empty string, how could we differentiate an empty string and a string containing "0" ? (0x80 from 0x8100)

@Quentash , going through this it looks like that the interpretation can depend on what we expect as output! I think depending on the type be expect to decode, if we are decoding for string, then 0x80 should be "", otherwise it looks like it should be 0 if are doing in case of uint.

Let's decode 0x80, add a comment that if u are expecting an int, then "" means 0x0.

I am sending u the key I used to sign this data, so that u can update ur test!
Also, good research :)

@Quentash , going through this it looks like that the interpretation can depend on what we expect as output! I think depending on the type be expect to decode, if we are decoding for string, then 0x80 should be "", otherwise it looks like it should be 0 if are doing in case of uint.

Let's decode 0x80, add a comment that if u are expecting an int, then "" means 0x0.

I am sending u the key I used to sign this data, so that u can update ur test!
Also, good research :)

This is also what I understood. Let's do that, I'm on it, and thanks a lot Ser !

As discussed,

I've added a comment in decode() explaining that en empty string will be parsed as a 0 for an integer.
I've modified the parser functions in RLPHelperImpl to parse empty strings as a 0.
Test datas are back to what they were ( 0x80 representing a 0 ).

I think this is ready to be reviewed, don't hesitate to ping me if I missed something.
And thanks again for your help !

I've added a verification on the payload length.
Indeed, if the payload length si so big that its value holds on more than 4 bytes, let string_len: u32 = U32Trait::from_bytes(string_len_bytes).unwrap(); would fail.
So I've implemented a new error PayloadTooLong being returned when the payload length holds on more than 4 bytes + 2 tests to proc the error with both a long string and a long list.

@Quentash this looks good to me, approving { + I guess u can change the position of the comment, although I don't have a very hard take on that. }

@enitrat I guess u can also do another review of this, and if it works for u then we can merge!
gg @Quentash :)

Unboyscouted the PayloadTooLong error
Finally removed the comment about empty string


Sidecar config implementation

Implementation of the newly introduced Sidecar config resource.
Due to the port specific nature of scoping services/virtualServices, changes had to be made to the networking/v1alpha3 folder, as opposed to simply providing a limited set of services per sidecar.
Signed-off-by: Shriram Rajagopalan<EMAIL_ADDRESS>

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

Needs approval from an approver in each of these files:

OWNERS [rshriram]

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ceea7b5cd42e7f53aa31d3c6b6327dff12703800
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ceea7b5cd42e7f53aa31d3c6b6327dff12703800
link
/test istio-unit-tests

prow/istio-presubmit.sh
ceea7b5cd42e7f53aa31d3c6b6327dff12703800
link
/test istio-presubmit

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ceea7b5cd42e7f53aa31d3c6b6327dff12703800
link
/test istio-unit-tests

prow/istio-presubmit.sh
ceea7b5cd42e7f53aa31d3c6b6327dff12703800
link
/test istio-presubmit

prow/istio-integ-local-tests.sh
ceea7b5cd42e7f53aa31d3c6b6327dff12703800
link
/test istio-integ-local-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ceea7b5cd42e7f53aa31d3c6b6327dff12703800
link
/test istio-presubmit

prow/istio-unit-tests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTestsMinProfile

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTestsMinProfile

prow/e2e-simpleTests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTests

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTestsMinProfile

prow/e2e-simpleTests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTestsMinProfile

prow/e2e-simpleTests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-mixer-no_auth

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTestsMinProfile

prow/e2e-simpleTests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTestsMinProfile

prow/e2e-simpleTests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-dashboard.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-dashboard

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTestsMinProfile

prow/e2e-simpleTests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-dashboard.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-dashboard

prow/istio-pilot-multicluster-e2e.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-minProfile.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTestsMinProfile

prow/e2e-simpleTests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-dashboard.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-dashboard

prow/istio-pilot-multicluster-e2e.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-dashboard.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-dashboard

prow/istio-pilot-multicluster-e2e.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTestsMinProfile

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

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

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-simpleTests

prow/e2e-mixer-no_auth.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-dashboard.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-dashboard

prow/istio-pilot-multicluster-e2e.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTestsMinProfile

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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

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

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-dashboard.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-dashboard

prow/istio-pilot-multicluster-e2e.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTestsMinProfile

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTests

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

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

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-dashboard.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-dashboard

prow/istio-pilot-multicluster-e2e.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTestsMinProfile

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTests

prow/e2e-mixer-no_auth.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-mixer-no_auth

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

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

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTestsMinProfile

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTests

prow/e2e-mixer-no_auth.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-dashboard

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
d7eeafb4406f58a6b365d8e751f5cfbc7a5be188
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTestsMinProfile

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTests

prow/e2e-mixer-no_auth.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-unit-tests

prow/e2e-simpleTests-minProfile.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTestsMinProfile

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTests

prow/e2e-mixer-no_auth.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-minProfile.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTestsMinProfile

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTests

prow/e2e-mixer-no_auth.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTests

prow/e2e-mixer-no_auth.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test istio-unit-tests

prow/e2e-dashboard.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-dashboard

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTests

prow/e2e-mixer-no_auth.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-mixer-no_auth

prow/istio-pilot-multicluster-e2e.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test istio-unit-tests

prow/e2e-dashboard.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test e2e-simpleTests

prow/istio-pilot-multicluster-e2e.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test istio-unit-tests

prow/e2e-dashboard.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-mixer-no_auth

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test istio-unit-tests

prow/e2e-dashboard.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-mixer-no_auth

prow/e2e-simpleTests.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-simpleTests

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
12c6b19e9f6c699cfeae0b9f906b1794f92c4461
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test istio-unit-tests

prow/e2e-dashboard.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-mixer-no_auth

prow/e2e-simpleTests.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test istio-unit-tests

prow/e2e-dashboard.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-mixer-no_auth

prow/e2e-simpleTests.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-mixer-no_auth

prow/e2e-simpleTests.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
8f56a7d4c04f136a07a3fceb7295aae2c50298c4
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
efaa45b869f4cfb91551b9a59198f76cba480571
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
efaa45b869f4cfb91551b9a59198f76cba480571
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
efaa45b869f4cfb91551b9a59198f76cba480571
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
efaa45b869f4cfb91551b9a59198f76cba480571
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
ca598aaf1d9c2b4a21cd90604ffb562968a1d037
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
efaa45b869f4cfb91551b9a59198f76cba480571
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
ca598aaf1d9c2b4a21cd90604ffb562968a1d037
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ca598aaf1d9c2b4a21cd90604ffb562968a1d037
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ca598aaf1d9c2b4a21cd90604ffb562968a1d037
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ca598aaf1d9c2b4a21cd90604ffb562968a1d037
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
ca598aaf1d9c2b4a21cd90604ffb562968a1d037
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ca598aaf1d9c2b4a21cd90604ffb562968a1d037
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
ca598aaf1d9c2b4a21cd90604ffb562968a1d037
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
dc32eae90b1ef0aee075de8c181dec231f1d9b9f
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
ca598aaf1d9c2b4a21cd90604ffb562968a1d037
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
dc32eae90b1ef0aee075de8c181dec231f1d9b9f
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dc32eae90b1ef0aee075de8c181dec231f1d9b9f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
dc32eae90b1ef0aee075de8c181dec231f1d9b9f
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dc32eae90b1ef0aee075de8c181dec231f1d9b9f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
dc32eae90b1ef0aee075de8c181dec231f1d9b9f
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dc32eae90b1ef0aee075de8c181dec231f1d9b9f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
dc32eae90b1ef0aee075de8c181dec231f1d9b9f
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dc32eae90b1ef0aee075de8c181dec231f1d9b9f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
dc32eae90b1ef0aee075de8c181dec231f1d9b9f
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test istio-unit-tests

prow/release-test.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test release-test

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
dc32eae90b1ef0aee075de8c181dec231f1d9b9f
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test istio-unit-tests

prow/release-test.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test e2e-mixer-no_auth

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test istio-unit-tests

prow/release-test.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test e2e-mixer-no_auth

prow/istio-pilot-multicluster-e2e.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/release-test.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test e2e-mixer-no_auth

prow/istio-pilot-multicluster-e2e.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test e2e-mixer-no_auth

prow/istio-pilot-multicluster-e2e.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test istio-unit-tests

prow/release-test.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test release-test

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

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

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test e2e-mixer-no_auth

prow/istio-pilot-multicluster-e2e.sh
02cc93024b0c1a4f32178b84b1423c3c5630b4fb
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test istio-unit-tests

prow/release-test.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test istio-unit-tests

prow/release-test.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/release-test.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
cb6814a4dccc177df47e21820718ead4596df8b9
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
3cde251220f561c3d0b38638c8cda5c795bc99cb
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
cb6814a4dccc177df47e21820718ead4596df8b9
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
cb6814a4dccc177df47e21820718ead4596df8b9
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
cb6814a4dccc177df47e21820718ead4596df8b9
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
cb6814a4dccc177df47e21820718ead4596df8b9
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
cb6814a4dccc177df47e21820718ead4596df8b9
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
cb6814a4dccc177df47e21820718ead4596df8b9
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
095e0f759ef7fe696fb03506c8384c1ad165a9d9
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
095e0f759ef7fe696fb03506c8384c1ad165a9d9
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
095e0f759ef7fe696fb03506c8384c1ad165a9d9
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
095e0f759ef7fe696fb03506c8384c1ad165a9d9
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
095e0f759ef7fe696fb03506c8384c1ad165a9d9
link
/test istio-pilot-multicluster-e2e

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

Does the sidecar that's specified by this CRD still respect and participate in routing rules defined with VirtualService?


fix: add new files to list of dependencies in project references

Currently, there is a bug in the way we compute the list of dependencies. We use cached config to get dependencies, which results in an outdated list of dependencies.
Related: #689

:tada: This PR is included in version 7.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Warnings from step-git-source-source-repo

One of the first things shown when a user pushes their code is a warning:
🕞  [b41d5d8ad83b628b-clone-s7kt6-pod-2k7j9] step-git-source-source-repo-z9t8q {"level":"warn","ts":1624479590.918046,"caller":"git/git.go:277","msg":"URL(\"http://gitea-http.gitea:10080/workspace/test12factor\") appears to need SSH authentication but no SSH credentials have been provided"}

It would be really nice if these warning could be fixed or removed so there's no confusion by a new user

Similarly, from tekton:
🕞  [b41d5d8ad83b628b-stage-shdgk-pod-45wj4] step-create 2021/06/23 20:19:59 warning: unsuccessful cred copy: ".docker" from "/tekton/creds" to "/tekton/home": unable to open destination: open /tekton/home/.docker/config.json: permission denied
🕞  [b41d5d8ad83b628b-stage-shdgk-pod-45wj4] step-create 2021/06/23 20:19:59 warning: unsuccessful cred copy: ".gitconfig" from "/tekton/creds" to "/tekton/home": unable to open destination: open /tekton/home/.gitconfig: permission denied
🕞  [b41d5d8ad83b628b-stage-shdgk-pod-45wj4] step-create 2021/06/23 20:19:59 warning: unsuccessful cred copy: ".git-credentials" from "/tekton/creds" to "/tekton/home": unable to open destination: open /tekton/home/.git-credentials: permission denied


[CWS] add release note with fargate fixes for 7.58.1

What does this PR do?
This PR is just adding a release note matching the 2 CWS backports for 7.58.1:

https://github.com/DataDog/datadog-agent/pull/30150
https://github.com/DataDog/datadog-agent/pull/30164

Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Pixiv sketch load only non R-18 pictures

Description
Hello, so.. all issue in the title ^^
Steps
(for example)

input [s1]
input [https://sketch.pixiv.net/@ex_rumia_project]
[done]

Expected behavior: [download all sketch pictures from artist page]
Actual behavior: [download only All ages, non R15/R18 works]
P.S Happy new year ^^

check your settings in https://sketch.pixiv.net/settings

check your settings in https://sketch.pixiv.net/settings

check your settings in https://sketch.pixiv.net/settings

Ok, that's my setting on Sketch and Pixiv

check your settings in https://sketch.pixiv.net/settings

Ok, that's my setting on Sketch and Pixiv

ok, looks like pixiv sketch has additional custom header similar like pixiv fanbox. I'm looking on it.

ok, looks like pixiv sketch has additional custom header similar like pixiv fanbox. I'm looking on it.


ARROW-6630: [Doc] Document C++ file formats

Ok, I've also added some docs for JSON and (very incomplete) Parquet. I think this can be merged once CI is green.

Travis-CI: https://travis-ci.org/pitrou/arrow/builds/589504952
AppVeyor: https://ci.appveyor.com/project/pitrou/arrow/builds/27662662


Add option to withdraw all funds from chequebook to wallet

Add option to withdraw all funds from chequebook to wallet, for example:
swarm-cli cheque withdraw --all

Would withdraw all the funds from the chequebook to the wallet. This would be used used when shutting down a bee node.
The could also be an option to withdraw just available funds (not the owed amounts), e.g.:
swarm-cli cheque withdraw --all-available

Wait, are you saying that it is possible to withdraw the owed amounts and not just up to the available funds?

Actually, my node(s) did not have any owed amounts, so I just presumed that any withdrawal is possible, even all the funds. If not, then off course just one option is needed. Or maybe in any case just one option is needed, but off course then it also makes sense to add the limit is manual amount is entered (if it does not exist currently), to allow withdrawal only up to what is not owed.

It does say here: https://docs.ethswarm.org/docs/bee/working-with-bee/cashing-out/
"Holding on to a swap-cheque is risky; it is possible that the owner of the chequebook has issued cheques worth more xBZZ than is contained in their chequebook contract."
But I guess they would be using some kind of  malicious Bee nodes to get to that state, a proper Bee should probably not allow that (?).

But I guess they would be using some kind of malicious Bee nodes to get to that state, a proper Bee should probably not allow that (?).

That was my understanding.  I have certainly not seen any of my nodes overdraw the chequebook, and I have had some nodes take it down to near zero available.   They just stop issuing cheques and slow themselves down to the pseudo- "free" settlements until I deposit more to the chequebook.


Strong mode type promoted bounds should not be inferred in reified positions

The following example causes a type promoted type variable to be inferred in a reified position.   We have no representation of intersection types at runtime.  DDC currently just reifies this using the type variable alone, which is unsound, since it results in the lambda being annotated with a reified parameter type of Object even though the body of the lambda assumes that it receives only integers.
The simplest fix for this, I think, is to just make inference strip off the promotion when inferring type type variables or lambda parameter/return types.  For the code below, this would make the inferred type of the lambda parameter T, and hence the x.isEven call would be ill-typed.
class A<T> {
  A(T x);
  void foo(T x) {}
}

f<T>(T x) {
  var g;
  if (x is int) {
     var a = new A(x);
     var f = a.foo;
     f = (x) {print(x.isEven);};
     g = f;
  }

  g("hello");
}

void main() {
  f<Object>(3);
}

cc @jmesserly @stereotype441

@leafpetersen is this still potentially going to drive any potential work to be included in NNBD due to the similarity between type promotion and nullability promotion?

Not sure what you're asking - the bug still exists in the NNBD world, and still needs to be fixed.  There may be more places where it can crop up in NNBD, I guess?  For example, <T extends int?>(T x) => x! needs to have type T <T extends int?>Function(T), not T&int <T extends int?>Function(T) .  Rolling out the general fix for this as part of the NNBD opt in might make sense as a way of avoiding an additional breaking change.

This has since been fixed.


2d not working in 32 bit windows

Operating system or device - Godot version:
windows 10 - 2.1.1 Godot
Issue description (what happened, and what was expected):
here is the thread where i described it: https://godotdevelopers.org/forum/discussion/18040/cant-see-label-or-viewport-lines-in-2d-scene-editor
look at all 4 of the posts i made.
Steps to reproduce:
not sure.  maybe download a 32 bit Godot version for windows 7?
Link to minimal example project (optional but very welcome):
the problem was in the editor.  it didn't matter what project i created, the problem appeared for all of them.

Might be some OpenGL issue. What is the graphics card?

I guess there were some messages on cmd window. what it said?

My dad said Norton might be the issue but Godot works on my 64 bit Windows
10 laptop that also has Norton installed.
  The cmd windows also mentions the
framebuffer and viewport.  Here's a screen shot:
https://postimg.org/image/9pafdiupl/
On Sat, Nov 26, 2016 at 3:59 PM, volzhs<EMAIL_ADDRESS>wrote:

I guess there were some messages on cmd window. what it said?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/7193#issuecomment-263085636,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXEvLRiAUa0ZTzxCUcXKst_5sgc4bN2Mks5rCJ2XgaJpZM4K8_Hp
.

Looks indeed like the problem is in the GPU that does not properly support OpenGL. Likely the same as #1260.

( that make me think that it could be handy that godot displays the gpu/driver name into the console to ease bug report from peoples who don't know how and to find this information )

okay, thanks!  at least i know what the problem is.
On Tue, Nov 29, 2016 at 10:10 AM, SuperUserNameMan<EMAIL_ADDRESS>
wrote:

( that make me think that it could be handy that godot displays the
gpu/driver name into the console to ease bug report from peoples who don't
know how and to find this information )
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/7193#issuecomment-263595758,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXEvLS0_UyQTCEbUGsZvH7gL6_dkyfrxks5rDEBNgaJpZM4K8_Hp
.

Closing as duplicate of #1260.


Fido the Watchdog / Scanner Updates / General Bug Fixes

Watchdog created to handle restarting hung bots during scanner process
General scanner updated - including a bulk CSV based bot starter during scanner process. You can start an exchanges bots by just loading the bulk pairs into a CSV in telegram_data named _bulkstart.csv with the first line being the field "market" and the balance of the first fields being the pairs on that exchange to load. Will only load pairs with a base currency as per scanner  json config.
General bug fixes / enhancements
Added Tradingview Screener (Brandon) code to coexist with default scanner.

@woblit, for future reference please update the CHANGELOG.md and version in the README.md.