list index out of range | spider.py@97

I have some problems. Is it same with #63 or #47 ?
[*] 2017-10-11 22:40 - fetching today's eBooks
[*] configuration file: /root/packtpub-crawler/config/prod.cfg
[*] getting daily free eBook
[*] fetching url... 200 | https://www.packtpub.com/packt/offers/free-learning
[*] fetching url... 200 | https://www.packtpub.com//packt/offers/free-learning?login=1
[-] <type 'exceptions.IndexError'> list index out of range | spider.py@97
Traceback (most recent call last):
  File "script/spider.py", line 97, in main
    packtpub.runDaily()
  File "/root/packtpub-crawler/script/packtpub.py", line 161, in runDaily
    self.__parseDailyBookInfo(soup)
  File "/root/packtpub-crawler/script/packtpub.py", line 93, in __parseDailyBookInfo
    self.info['url_claim'] = self.__url_base + div_target.select('a.twelve-days-claim')[0]['href']
IndexError: list index out of range
[*] no free eBook from newsletter right now
[*] done

Thanks, is a duplicate of #70


Fix usage of api variable in update_imported_docs

This is a follow up to #1458 as I noticed a bug in there. The following code introduced a bug:
if api is None:
    api = api.client.api
    api = api_v1

api is a parameter in the function. When not given it is None, and
it shadows the module import for api.client. Therefore it will raise an
exception ...
Sorry. This PR fixes that.

The code was also already broken in a few other places. I've redone the api usage in projects.tasks and replaced all the dependency injected usage with an explicit call to the API client using the explicit version. That should make it much less confusing and is even better testable as we can use proper mocks and don't need to pass the api client down the stack.


TSify dialog composables

Fixes

Fixes #[issue number] by @[issue author]
Description

Testing Instructions

Checklist

[ ] My pull request has a descriptive title (not a vague title like Update index.md).
[ ] My pull request targets the default branch of the repository (main) or a parent feature branch.
[ ] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

I'm going to put this PR on hold until I've merged https://github.com/WordPress/openverse-frontend/pull/1275 as 1275 updates and fixes some of the initial focus handling to be more robust than it is now and this PR currently has issues with the focus management having changed for some reason.
I can't figure out why it changed as there aren't any runtime changes that would suggest it, so the only thing I can think is that the ariakit utilities copied into this PR are slightly different than the version being pulled from NPM in our pnpm-lock, I just haven't taken the time to manually diff them yet.

@sarayourfriend is the work on this unblocked? It looks like there are a few conflicts, should this draft remain open?

I think this can be rebased and undrafted. The issue that was blocking it was actually one already present in main and Olga found another fix for it.

Sorry, I misremembered what was blocking this. It's still blocked and cannot be undrafted yet.

Dang! What's the current blocker?

Still the same focus management issue. I have no idea how to solve it.

I'm not sure if it's worth focusing on this, or focusing on #1372 :shrug: I think the Ariakit PR has more value long term, but I also don't have the time currently to spend on it that it would need for it to even cover the dialog in a reasonable amount of time.
TSifying these files isn't critical though. There are other workarounds we can use to be able to TSify related files.
Gonna close this PR. Someone else can try this in a different PR or help out with the Ariakit one.


[codebuild] deal with download failed

Make error nicer for download failed. Download failed should not be retry-able.
Test: try building from a PR that doesn't exist (yet)
$ /docker/build-aws.sh --build-init --version pull/7000
Building with SOURCE_VERSION=refs/pull/7000/head TAGS=dev_rustielin_pull_7000
Started build for project libra-init with ID libra-init:0a231b38-6eb8-4843-8839-0ceae028076e. Link to the build https://us-west-2.console.aws.amazon.com/codesuite/codebuild/projects/libra-init/build/libra-init:0a231b38-6eb8-4843-8839-0ceae028076e/
libra-init current phase: QUEUED
libra-init current phase: PROVISIONING
libra-init current phase: PROVISIONING
libra-init current phase: PROVISIONING
libra-init current phase: DOWNLOAD_SOURCE
libra-init current phase: DOWNLOAD_SOURCE
libra-init current phase: DOWNLOAD_SOURCE
libra-init download source failed

$ echo $?
1

thx for doing this

/land

:broken_heart: Test Failed - commit-workflow

/land


Add mind mapping tool XMind.

This is a FOSS project, but this expression is using the binary build.

@vandenoever so... did you get a reply?

No i did not.

so... we sadly close this?
On Wed Jan 21 2015 at 11:24:47 AM Jos van den Oever <
<EMAIL_ADDRESS>wrote:

No i did not.
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/pull/4971#issuecomment-70814669.

@vandenoever Do I understand correctly that you never received any reply about XMind license?

On Saturday 04 April 2015 03:32:58 Michael Raskin wrote:

@vandenoever Do I understand correctly that you never received any reply
about XMind license?

yes, there was no reply.

Pity. I guess we have to close the request then; as-is it seems to be too optimistic about the license, and I am not sure it is not a formal infringement to distribute instructions on altering their proprietary binaries (I mean patchelf in the expressions)


chmod: add uucore's perms feature to Cargo.toml

This PR adds the missing perms feature from uucore to Cargo.toml. I noticed it when I tried to run the chmod tests:
$ cargo test --features=chmod --no-default-features
   Compiling uu_chmod v0.0.28 (/home/dho/projects/coreutils/src/uu/chmod)
error[E0433]: failed to resolve: could not find `perms` in `uucore`
   --> src/uu/chmod/src/chmod.rs:229:23
    |
229 |         .args(uucore::perms::common_args())
    |                       ^^^^^ could not find `perms` in `uucore`
    |

https://github.com/uutils/coreutils/pull/7038 to make sure it doesn't happen again


Add private share support to zrok-share (frontdoor)

nfpm: Modified zrok-share to cater for private temporary and reserved shares, controlled by ZROK_FRONTEND_MODE; Modified env file with additional variable ZROK_FRONTEND_MODE;
See OpenZiti Discourse discussion here.

@stefanadelbert I signed your commits and submitted a new PR: https://github.com/openziti/zrok/pull/652


[Issue #160] feat: add docs link to navbar

Adding a link to docs.paybutton.org in the navbar

ah good catch yeah should be slightly off-black, and yeah good call added some tooltips

The dark mode toggle is also using the darker colour if you think they should all be the same.


Fix Altitude Limitation

Describe problem solved by the proposed pull request
Before if you were above the maximum altitude you could command to go down anymore until the position controller had control overshoot and the vehicle slowly got below the maximum altitude again.
Describe your preferred solution
I tried to simplify the logic:

We're allowed to reach a maximum altitude of home + parameter
If we ever exceed this altitude

make sure we cannot get further up
only allow downwards speed

This results in "bouncing off" the limitation.
Test data / coverage
SITL testing

And rebased in a second step such that you can see the changes under the first for-pushed link.

@julianoes So rebased (1st force-push) and improved naming and comments to be hopefully very clear now (2nd force-push). My SITL test still works perfectly fine.

Good to go, now that thenames and comments are clear?

@dagar does this need test flying by the flight testing team (@Tony3dr) or is that good to be merged?


upgrade react

the 16.5 version of react is way too dated for this starter to be useful

Thanks, I'll do a round of package upgrades and testing soon. It should be safe to upgrade on your projects, though, you don't have to keep the starter's versions.


2.13 Addon Dependency Usage

Hello, I know that this isn't a currently 'supported' use case, but our team has a few addons that use this package to declare the template files for components inside the component file instead of the template file. It's really, really nice for making small components easy to work with when all of the assets are in one file instead of two.
After updating the addons to CLI 2.13, we can no longer use the addons in consuming Apps that are version less than 2.13. This package expects Babel6 to be in use, and the application build errors when trying to consume the 2.13+ addon that has this package as a dependency (rather than dev-depdency).
Is there a way that we can resolve this (other than moving all the templates into .hbs files)? Would be happy to help if hands are needed!
Here is an example of the type of component files we have in the addons:
import Component from 'ember-component';
import hbs from 'htmlbars-inline-precompile';

export default Component.extend({
  state: false,
  tagName: '',

  actions: {
    close() {
      this.send('setFalse');
    },
    open() {
      this.send('setTrue');
    },
    setFalse() {
      this.set('state', false);
    },
    setTrue() {
      this.set('state', true);
    },
    toggleState() {
      this.toggleProperty('state');
    }
  },

  // Layout
  // ---------------------------------------------------------------------------
  layout: hbs`
    {{yield
      state
      (hash
        setTrue=(action 'setTrue')
        setFalse=(action 'setFalse')
        open=(action 'open')
        close=(action 'close')
        toggleState=(action 'toggleState')
      )
    }}
  `

Thanks!

FWIW, I am working on this now.  The basic issue comes down to https://github.com/ember-cli/ember-cli-version-checker/issues/27.

That's awesome 👍

https://github.com/ember-cli/ember-cli-version-checker/pull/41 should unblock the main issue, needs review before landing and releasing as v2.0.0.

https://github.com/ember-cli/ember-cli-htmlbars-inline-precompile/pull/80 should fix things for<EMAIL_ADDRESS>but would love some testers...

I'm in, what should I update to test?

I think you should basically just need to update your nested deps that needed 0.3.x to use v0.3.10 (which I just published).

Works with 0.3.11 👍
Thanks for the uber-fast turnaround.


Chase Hyprland 45.2

Updated flake.lock, fixed breaking changes from https://github.com/hyprwm/Hyprland/commit/67cee4300 and added hyprpm pin

LGTM, thanks!


Move the "ConnectionInner" structure to the protocol crate

This pull request does three things:
1). Move the ConnectionInner object from the x11rb crate to the new x11rb_protocol crate, renaming it Connection. This is in the aims of creating a sans-I/O connection.
2). Split the WriteBuffer object from the ConnectionInner type and move it into the RustConnection type. Output buffering should really be handled by something like std::io::BufWriter, although I'm not aware of one that exists for sendmsg (crate idea?).
3). Move some type aliases and enums into x11rb_protocol and then update the imports throughout.
There's certainly more protocol bits in x11rb that could be moved into x11rb_protocol at this point, and vice versa, but this is a good starting point.

Discarding this pull request and then reopening it for master


Regular expression error in FENCED_BLOCK_RE

The current regular expression doesn't match Termynal code blocks correctly.
For example:
 Welcome

One:

```yaml title="files/one.yml"
--8<-- "files/one.yml"
```

Two:

```yaml title="files/two.yml"
--8<-- "files/two.yml"
```

<!-- termynal -->

```
$ command

Ok!
```

Two blocks are selected when only one should be:
```

Two:

```yaml title="files/two.yml"
--8<-- "files/two.yml"
```

```
$ command

Ok!
```

This leads to errors, for example, when using the pymdownx.snippets extension (--8<-- notation).
example.zip

Fixed in 0.11.1

It broke


⚠ Secret Website 3 has degraded performance

In 064e72b, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 10763 ms

Resolved: Secret Website 3 performance has improved in 15da1b2.


Better leverage h2 via http headers

For the new preview site have a look at the waterfall (note i am using chrome for the below)

Note that despite using h2 there is no Multiplexing. The reason for this is that the response headers contain no rel=preload headers
you may also want to look into dns-prefetch and preconnect headers https://www.keycdn.com/blog/resource-hints/

Great feedback, @SimonCropp, this will require some learning and investigation on our side. Thanks for the heads up! I'll leave this open until we can look into this.

@joelverhagen TBH i am still learning as well :)
BTW check out the http headers (using chrome) on this page https://docs.particular.net/
<https://cdnjs.cloudflare.com>; rel=dns-prefetch, <https://cdnjs.cloudflare.com>; rel=preconnect; crossorigin, </content/js/documentation_v5.js>; rel=preload; as=script, </content/images/menu/transports-icon.svg>; rel=preload; as=image, </content/images/menu/servicepulse-icon.svg>; rel=preload; as=image, </content/images/menu/serviceinsight-icon.svg>; rel=preload; as=image, </content/images/menu/servicecontrol-icon.svg>; rel=preload; as=image, </content/images/menu/samples-icon.svg>; rel=preload; as=image, </content/images/menu/persistence-icon.svg>; rel=preload; as=image, </content/images/menu/nservicebus-icon.svg>; rel=preload; as=image, </content/images/particular_v1.svg>; rel=preload; as=image, </content/images/logo_v1.svg>; rel=preload; as=image, </content/css/style_v6.css>; rel=preload; as=style, <https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/css/bootstrap.min.css>; rel=preload; as=style, <https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/fonts/glyphicons-halflings-regular.woff2>; rel=preload; as=font; crossorigin, <https://cdnjs.cloudflare.com/ajax/libs/jquery/3.2.1/jquery.min.js>; rel=preload; as=script, <https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js>; rel=preload; as=script, <https://cdnjs.cloudflare.com/ajax/libs/clipboard.js/1.7.1/clipboard.min.js>; rel=preload; as=script

we optimise the headers based on browser support for the various headers

been a year, and this was only a suggestion. so closing


Fix logout button on mobile

Move the button to the bottom

make i take this...?

Certainly! I'll assign it to you.

pr made https://github.com/Bot-Rakshit/bm_frontend/pull/121
clsoe this issue


Replace all kubernetes label unsafe characters with -

Otherwise your error looks like this.
[Kubeclient::HttpError]: Deployment.apps \"10-ui\" is invalid: [spec.template.spec.nodeSelector: Invalid value: \"cp4mcm:im/zone-Config Zone\": prefix part a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*'), spec.template.spec.nodeSelector: Invalid value: \"cp4mcm:im/zone-Config Zone\": name part must consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName',  or 'my.name',  or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]')]

Test failed on a space, which I think is url safe.  how did you determine the list of unsafe chars?

This isn't about URL safe but rather DNS-1123 subdomain safe.


Security: Potential leak of az secrets on cmdline.

We are already masking the secrets in the action. Did you find out any specific case where we have secrets leaking on the cmdline ?

https://github.com/Azure/k8s-create-secret/issues/3
You could check this thread for more info

@ds-ms Currently az cli does not have a way to handle this. Environment variables are not supported for authentication and there is no way to login using file. The only way to login using service principal is using :
https://docs.microsoft.com/en-us/cli/azure/authenticate-azure-cli?view=azure-cli-latest#sign-in-with-a-service-principal

In the latest OIDC support added to the login action, we aren't asking for any password information from the user for login. So closing this issue.


CLA already sign for existing organisation do not show 'CLA Not Found' dialog during create organisation flow.

This deployed to Dev, Staging & Prod.

This deployed to Dev, Staging & Prod.

As updated by Asha, this is verified on Staging & it works fine.

As updated by Asha, this is verified on Staging & it works fine.


DNN-7290 revert addition of language specific portal templates

Reverts dnnsoftware/Dnn.Platform#656

merged my own commit as it's breaking installs when a source build is used


[Android] ListView can't scroll when set position:'absolute' in style

I wanna add a
mask layer on the ListView, I wrote JSX like this <View>                 <ListView                     style={{flex:1,position:'absolute',width:300}}                     ....../>                 <Mask ....../>             </View>, now the ListView can't vertical scrolling, BUT the ListItem still can be clicked and the ViewPager rendered by method renderHeader can horizontal scrolling too. It bothered me for a long time. my react-native library's version is 0.12.0, seeking help and very grateful

Try top: 0, bottom: 0 instead of flex:1 with absolute positioning.

@ide Amazing!!!!! it works!!!! thanks a lot

but why  use 'top: 0, bottom: 0' instead of 'flex:1' works!?
I am confused!

@ide you are awesome!

@ide  you are good!


Error while exporting cohesive elements in a hexahedral mesh

Dear Proff. Kristoffer,
Congratulations for such a nice code, Phon!
While exporting cohesive elements using a .inp file from Neper, i get the following error:-

from phon.io.read.read_from_abaqus_inp import read_from_abaqus_inp
from phon.mesh_tools.create_cohesive_elements import create_cohesive_elements
from phon.io.write.export_to_abaqus import export_to_abaqus
mesh = read_from_abaqus_inp("cube_10grains.inp")
create_cohesive_elements(mesh, mesh_dimension=3)
export_to_abaqus("cohesive.inp", mesh, write_2d_elements=False)
Traceback (most recent call last):
File "", line 1, in
File "phon/io/write/export_to_abaqus.py", line 79, in export_to_abaqus
(element_dictionary_inverse[(element_type, "abaqus")] in elements_1d)):
KeyError: ('CPE4', 'abaqus')

I am attaching the .inp file which contains hexahedral elements. Am i making some mistake in exporting?
Many thanks for your time.
cube_10grains.txt

The reason for this is that I don't think abaqus has any  quadrilateral cohesive elements so I haven't added any element name to export it to. Do you have any documentation about quadrilateral cohesive elements in Abaqus?

Dear Proff.,
The documentation of Abaqus 6.10 displays Abaqus's capability of inserting
quadrilateral cohesive elements:-
http://abaqusdoc.ucalgary.ca/books/usb/default.htm?startat=pt01ch02s02aus10.html#usb-int-ielement-cohesive
*Input File Usage:          *Use the following option to specify the
element number and the nodes that define the element:
*ELEMENT http://abaqusdoc.ucalgary.ca/books/key/key-link.htm#usb-kws-melement,
TYPE=name
For example, the following lines create COH3D8 element number 11 that has
node numbers 1, 2, 3, 4, 1001, 1002, 1003, and 1004:
*ELEMENT http://abaqusdoc.ucalgary.ca/books/key/key-link.htm#usb-kws-melement,
TYPE=COH3D8
11, 1, 2, 3, 4, 1001, 1002, 1003, 1004
On Mon, May 9, 2016 at 3:04 PM, Kristoffer Carlsson <
<EMAIL_ADDRESS>wrote:

The reason for this is that I don't think abaqus has any quadrilateral
cohesive elements so I haven't added any element name to export it to. Do
you have any documentation about quadrilateral cohesive elements in Abaqus?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/KristofferC/Phon/issues/10#issuecomment-217818888

Please try with the new Phon, I added a change. Note that I am not 100% sure that the order of the nodes in the cohesive elements are correct  so make sure you check that in Abaqus.

Dear Proff.,
It runs fine now. Many thanks for your help and the latest patch.
Sorry to bring drag into this discussion, but i can't see the cohesive
elements with a finite thickness. (only faces shown). The output after
importing in Abaqus (after hiding the individual grains) is shown below:-
[image: Inline image 1]
As can be seen, the inserted cohesive elements don't have a finite width.
Did i miss an option to prescribe a finite width to the cohesive elements
while parsing and meshing in Phon.? I expect the result to be something
like (with hex elements):- (below images taken from your thesis:- Modelling
of three dimensional microstructures including grain boundary mechanisms)
[image: Inline image 2]     [image: Inline image 3]
I am sorry if this is a basic question. Am i wrong somewhere? Many thanks
for your help.
On Mon, May 9, 2016 at 4:19 PM, Kristoffer Carlsson <
<EMAIL_ADDRESS>wrote:

Please try with the new Phon, I added a change. Note that I am not 100%
sure that the order of the nodes in the cohesive elements are correct so
make sure you check that in Abaqus.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/KristofferC/Phon/issues/10#issuecomment-217833716

The cohesive elements will initially have zero thickness. To get the image in my thesis I applied a force in the normal direction to the cube so that the grains move away from each other. After that the cohesive elements have a finite thickness and the can be seen.

Dear proff.,
Thank you very much for the clarification. The doubt is resolved now.
On May 9, 2016 5:24 PM, "Kristoffer Carlsson"<EMAIL_ADDRESS>wrote:

The cohesive elements will initially have zero thickness. To get the image
in my thesis I applied a force in the normal direction to the cube so that
the grains move away from each other. After that the cohesive elements have
a finite thickness and the can be seen.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/KristofferC/Phon/issues/10#issuecomment-217844594


Update Spine documentation to reflect the current state of things

Because the duration patch has been merged to the Spine module's master and spine-to-godot-scene.py has been in its own repository for, like, six weeks.

Something like "henceforth referred to as" made me think of lawyers, but I force-pushed a close approximation of your proposal.

Yeah, I agree that it's too formal, but I couldn't think of anything better. I think your changes are good though. :slightly_smiling_face:


dbt show

Contributions

[X] I am a PM or subject matter expert at dbt who is responsible for this feature.

Where does this content belong?
New command under https://docs.getdbt.com/reference/dbt-commands
Link to source material
Who will use this feature?

Users who want to see a preview of their model
dbt Cloud under the hood

How can we test or use this feature?
dbt compile --inline "select * from {{ ref('raw_orders') }}"

or
dbt compile --select stg_payments

Awaiting demo for documentation


Fix autologin when password contains backslashes

This PR fixes #596. I also changed the error type returned by Credentials::retrieve() from Error::Unavailable to Error::NoResult, as it seems more appropriate for when the secret can't be read.

We might wanna refactor this, as it doesn't seem like the right solution. I think the issue lies with how serde_json serializes the Credentials struct.

Closing as the issue is unrelated to Spot.


Set default acmesolver image based on arch

Signed-off-by: Lennart Jern<EMAIL_ADDRESS>
What this PR does / why we need it: This detects the architecture and sets the acmesolver container image based on that.
Which issue this PR fixes: fixes #1470
Special notes for your reviewer:
I'm not sure if it's OK to use quay.io/jetstack/cert-manager-acmesolver-amd64 instead of quay.io/jetstack/cert-manager-acmesolver (the case now) for the normal amd64 arch. It makes sense in the way that all archs are treated equally but it may need changes in other places that I'm not aware of (build and push jobs?).
Please bear with me, this is my first pull request to cert-manager :smile:
Release note:

Set default acmesolver image based on arch

Thanks 😄!
/lgtm
/approve


GH-14947 [R] Compatibility with dplyr 1.1.0

Each commit in this PR fixes a breaking/behaviour change described in #14947.
I could not build the dev version of arrow so this is only tested against the CRAN version. Also there might be changes introduced since the last release that require compatibility adjustments. Could someone pick this up from here please?
Closes #14947.

Closes: #14947

I could not build the dev version of arrow

I don't suppose you'd mind elaborating more on this @lionel- ?  Only because we're looking at making the contribution process for Arrow a bit smoother.


Fix syntax errors

This fixes minor syntax errors I found using pod lib lint KSCrash.podspec. Also, removed an unnecessary framework path in the Mac workspace.

Great! Thanks!


Use aws sdk v1 in spark metadata client

Really need to use 1.7.4, which is what Hadoop 2.7.7 used.  But that version is loooooooonnnnggg gone.  So go to 1.12.140, which a version from 2022-01 (which should alleviate some AWS log4j worries).
In any case depend on the provided version, so we get whatever comes with hadoop-aws (which we do need to bring in some cases).

How was this tested (a sanity test)?

Not yet tested.  Will try to rebase #3180 on top of this, to get a better e2e test.  Also ideally some integration testing :-)


Please expand section on Actions Menu

Hi, it looks like the Actions menu section could be expanded. The screenshot is outdated as new actions have been added. Would be great if you could explain what each action does. For example, what will happen if I select "Report clean" action?

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

ID: 89aaa2af-ba47-4e6f-60f3-1b0b95df35f9
Version Independent ID: 8495bb4c-045a-5085-64d9-1b9ae788cfdb
Content: Views in Threat Explorer and real-time detections - Office 365
Content Source: microsoft-365/security/office-365-security/threat-explorer-views.md
Service: o365-seccomp
GitHub Login: @MSFTTracyP
Microsoft Alias: tracyp

Closing this out. Thank you for letting me know.


Produce errors more consistently in operator policy package

Remove errors.go
Make sure error types are not leaked from the checks
Remove extraneous logging

Fixes #662
Signed-off-by: Brad P. Crochet<EMAIL_ADDRESS>

/test 4.8-e2e

/retest

Coverage increased (+0.6%) to 57.849% when pulling 775f7ae198b2593f36966f6e832bc57c36c3cb65 on bcrochet:errors-662 into 315fd5b7c6f7cda6bbc9520743efd8940784a572 on redhat-openshift-ecosystem:main.


SNI routing from sidecar to gateway with virtual services

This PR adds basic SNI routing with matching of sourceLabels and mesh but no L4 attributes. Virtual service hosts must exist in the registry and the match port and destination ports must match.
The aim is to be able to support forcing traffic through the egress gateway using SNI.
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: wikipedia-sni
spec:
  hosts:
  - www.wikipedia.org
  ports:
    - number: 443
      protocol: TLS
      name: tls-port
  resolution: DNS
---
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: istio-egressgateway
spec:
  selector:
    # DO NOT CHANGE THESE LABELS
    # The egressgateway is defined in install/kubernetes/helm/istio/values.yaml
    # with these labels
    istio: egressgateway
  servers:
  - port:
      number: 443
      name: tls
      protocol: tls
    hosts:
    - "www.wikipedia.org"
    tls:
      mode: PASSTHROUGH
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: force-a-to-wiki-through-egress-gateway
spec:
  hosts:
  - www.wikipedia.org
  tls:
  - match:
    - sourceLabels:
        app: a
      gateways:
      - mesh
      sniHosts:
      - "www.wikipedia.org"
    route:
    - destination:
        # use the shortname so the test doesn't depend on istio-system namespace
        host: istio-egressgateway
        port:
          number: 443
  - match:
    - gateways:
      - istio-egressgateway
      sniHosts:
      - "www.wikipedia.org"
    route:
    - destination:
        host: www.wikipedia.org
        port:
          number: 443

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

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS [ijsnellf]

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ff12e828b3ae4818544184f7445e6db3487a4eb3
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.

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

Test name
Commit
Details
Rerun command

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

prow/istio-presubmit.sh
ff12e828b3ae4818544184f7445e6db3487a4eb3
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.

I don't think we should overload protocol specifications in VirtS like this.
Looking at the sample you can't actually differentiate between routing TCP traffic and routing tcp-over-tls-via-SNA traffic. This lack of specificity is likely to be dangerous.
I'd rather we create a separate stanza for 'tcp-tls' in VirtualService to explicitly handle this protocol form. We're going to need to create stanzas for other protocols going forward so this shouldn't be such a big deal.
This would also line up with
https://github.com/istio/istio/pull/6280
@vadimeisenbergibm @rshriram

Refactoring to use https://github.com/istio/api/pull/546...

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

Test name
Commit
Details
Rerun command

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

prow/istio-unit-tests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
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.

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

Test name
Commit
Details
Rerun command

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

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-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.

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

Test name
Commit
Details
Rerun command

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

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

prow/istio-unit-tests.sh
e848f8076350dfa6b0cfd145c44e6bb1d1eb0ff7
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.

@ijsnellf I created a PR to document HTTPS-egress-gateway https://github.com/istio/istio.github.io/pull/1579, see the Direct HTTPS traffic through an egress gateway.
From what I see:

sni_domains is not set for the filterChains of the application pod. So the TCP filter directs all the traffic that arrives to the port 443, to the host of the ServiceEntry.
Redirection to the egress gateway works (again without sni_domains in the filterChains).
For the gateway pod, no tcp proxy to route to the cluster of the destination is defined. The cluster is defined.

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

Needs approval from an approver in each of these files:

pilot/OWNERS [ijsnellf]

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

prow/istio-unit-tests.sh
be3e0daa785be96d1eea4254f39ee30e49ce1233
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

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

prow/e2e-dashboard.sh
be3e0daa785be96d1eea4254f39ee30e49ce1233
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

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

prow/istio-unit-tests.sh
c10447549e1ec5d3cc4cd80b349133448faae87c
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

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

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

prow/istio-presubmit.sh
c10447549e1ec5d3cc4cd80b349133448faae87c
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

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

prow/istio-unit-tests.sh
d3d8c3956c901671c6f321ae7f48ba1030dc6e9d
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

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

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

prow/istio-presubmit.sh
d3d8c3956c901671c6f321ae7f48ba1030dc6e9d
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

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

prow/istio-unit-tests.sh
0cbdf365f7fadc823f0aae2304e1f9f3d8608e42
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

prow/istio-unit-tests.sh
0cbdf365f7fadc823f0aae2304e1f9f3d8608e42
link
/test istio-unit-tests

prow/istio-presubmit.sh
0cbdf365f7fadc823f0aae2304e1f9f3d8608e42
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

prow/istio-unit-tests.sh
0cbdf365f7fadc823f0aae2304e1f9f3d8608e42
link
/test istio-unit-tests

prow/istio-presubmit.sh
0cbdf365f7fadc823f0aae2304e1f9f3d8608e42
link
/test istio-presubmit

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
f74e32727b3ce18815aa1f2778aa7deb51314bc9
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

prow/istio-presubmit.sh
0cbdf365f7fadc823f0aae2304e1f9f3d8608e42
link
/test istio-presubmit

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

prow/istio-unit-tests.sh
39bc39280ebd4c67721983bf84b4596c5a3a73ff
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

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

prow/istio-unit-tests.sh
39bc39280ebd4c67721983bf84b4596c5a3a73ff
link
/test istio-unit-tests

prow/istio-presubmit.sh
39bc39280ebd4c67721983bf84b4596c5a3a73ff
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

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

prow/istio-presubmit.sh
39bc39280ebd4c67721983bf84b4596c5a3a73ff
link
/test istio-presubmit

prow/istio-unit-tests.sh
c8110ee3433a48b6788d563b1d57b8a5236c2a60
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ce70fbd3a5f519e206af75edd0e45bcd964e6378
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
81a7170d004909e884f53a3568dd0bb58c935775
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.

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

Needs approval from an approver in each of these files:

pilot/OWNERS [ijsnellf]
tests/OWNERS

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

Removing the hold - I think it is safe, Shriram confirmed the constant was not used in 0.8.
Would be nice to add more comments - but can be done in separate PR.

/lgtm
/approve

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

Needs approval from an approver in each of these files:

pilot/OWNERS [costinm,ijsnellf]
tests/OWNERS [costinm]

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

New changes are detected. LGTM label has been removed.

added comments

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

Needs approval from an approver in each of these files:

pilot/OWNERS [ZackButcher,costinm,ijsnellf]
tests/OWNERS [costinm]

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

New changes are detected. LGTM label has been removed.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

prow/istio-unit-tests.sh
623c04f06b5b2b3ee5e1c4bbe3abc64c5ddf89ab
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4461e03b9b1282851fcddeb4395dbb2d1571efb6
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
9e4e887fbcc9a4790b8a5eac717f1611339b7bcc
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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4c8a10d4c9d5217ada91fb806cb907152fe5892b
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.

Could you include / paste xDS generated with this change?

which mode? with SNI or with just plain tcp proxy?

@rshriram both would be great ;)

 {
     "version_info": "2018-07-03 13:43:05.9141201 +0000 UTC m=+93.376140292",
     "listener": {
      "name": "<IP_ADDRESS>_19090",
      "address": {
       "socket_address": {
        "address": "<IP_ADDRESS>",
        "port_value": 19090
       }
      },
      "filter_chains": [
       {
        "filters": [
         {
          "name": "mixer",
          "config": {
           "transport": {
            "check_cluster": "outbound|9091||istio-policy.istio-system.svc.cluster.local",
            "network_fail_policy": {
             "policy": "FAIL_CLOSE"
            },
            "report_cluster": "outbound|9091||istio-telemetry.istio-system.svc.cluster.local",
            "attributes_for_mixer_proxy": {
             "attributes": {
              "source.uid": {
               "string_value": "kubernetes://a-675595579f-sdjxx.istio-system"
              }
             }
            }
           },
           "disable_check_calls": true,
           "mixer_attributes": {
            "attributes": {
             "destination.service": {
              "string_value": "headless.istio-system.svc.cluster.local"
             },
             "source.uid": {
              "string_value": "kubernetes://a-675595579f-sdjxx.istio-system"
             },
             "source.namespace": {
              "string_value": "istio-system"
             },
             "destination.service.host": {
              "string_value": "headless.istio-system.svc.cluster.local"
             },
             "context.reporter.kind": {
              "string_value": "outbound"
             },
             "context.reporter.uid": {
              "string_value": "kubernetes://a-675595579f-sdjxx.istio-system"
             }
            }
           }
          }
         },{
          "name": "envoy.tcp_proxy",
          "config": {
           "stat_prefix": "outbound|19090||headless.istio-system.svc.cluster.local",
           "cluster": "outbound|19090||headless.istio-system.svc.cluster.local"
          }
         }
        ]
       }
      ],
      "deprecated_v1": {
       "bind_to_port": false
      }
     },

TCP proxy

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
eada09d770bd24ba2abe963b035225b8ad787d4e
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 no filter chain match?

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

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

prow/istio-unit-tests.sh
1eca080123180357cc3300953c247a82e3374e09
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.

Filter chain match for TCP proxy is useless, as it only supports SNI. Will get you SNI routing in a few moments..

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

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

prow/istio-unit-tests.sh
2cf6cd64b504e8e0b2297e7a4e0ea5bec40f99ef
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.

SNI routing via egress gateway
"dynamic_active_listeners": [
    {
     "version_info": "2018-07-03 21:36:23.514137053 +0000 UTC m=+1081.777744952",
     "listener": {
      "name": "<IP_ADDRESS>_443",
      "address": {
       "socket_address": {
        "address": "<IP_ADDRESS>",
        "port_value": 443
       }
      },
      "filter_chains": [
       {
        "filter_chain_match": {
         "server_names": [
          "www.google.com"
         ]
        },
        "filters": [
         {
          "name": "mixer",
          "config": {
           "transport": {
            "network_fail_policy": {
             "policy": "FAIL_CLOSE"
            },
            "report_cluster": "outbound|9091||istio-telemetry.istio-system.svc.cluster.local",
            "check_cluster": "outbound|9091||istio-policy.istio-system.svc.cluster.local"
           },
           "mixer_attributes": {
            "attributes": {
             "source.namespace": {
              "string_value": "istio-system"
             },
             "context.reporter.uid": {
              "string_value": "kubernetes://istio-egressgateway-c8894555f-l44gw.istio-system"
             },
             "source.uid": {
              "string_value": "kubernetes://istio-egressgateway-c8894555f-l44gw.istio-system"
             },
             "context.reporter.kind": {
              "string_value": "outbound"
             }
            }
           }
          }
         },
         {
          "name": "envoy.tcp_proxy",
          "config": {
           "stat_prefix": "outbound|443||www.google.com",
           "cluster": "outbound|443||www.google.com"
          }
         }

SNI routing via gateway, sidecar config
"listener": {
      "name": "<IP_ADDRESS>_443",
      "address": {
       "socket_address": {
        "address": "<IP_ADDRESS>",
        "port_value": 443
       }
      },
      "filter_chains": [
       {
        "filter_chain_match": {
         "server_names": [
          "www.google.com"
         ]
        },
        "filters": [
         {
          "name": "mixer",
          "config": {
           "transport": {
            "check_cluster": "outbound|9091||istio-policy.istio-system.svc.cluster.local",
            "network_fail_policy": {
             "policy": "FAIL_CLOSE"
            },
            "report_cluster": "outbound|9091||istio-telemetry.istio-system.svc.cluster.local"
           },
           "disable_check_calls": true,
           "mixer_attributes": {
            "attributes": {
             "context.reporter.kind": {
              "string_value": "outbound"
             },
             "context.reporter.uid": {
              "string_value": "kubernetes://a-7c8ff555d8-khgvg.istio-system"
             },
             "source.uid": {
              "string_value": "kubernetes://a-7c8ff555d8-khgvg.istio-system"
             },
             "destination.service": {
              "string_value": "www.google.com"
             },
             "source.namespace": {
              "string_value": "istio-system"
             },
             "destination.service.host": {
              "string_value": "www.google.com"
             },
             "destination.service.namespace": {
              "string_value": "istio-system"
             },
             "destination.service.name": {
              "string_value": "www.google.com"
             }
            }
           }
          }
       },
         {
          "name": "envoy.tcp_proxy",
          "config": {
           "value": {
            "stat_prefix": "outbound|443||istio-egressgateway.istio-system.svc.cluster.local",
            "route_config": {
             "routes": [
              {
               "cluster": "outbound|443||istio-egressgateway.istio-system.svc.cluster.local"
              }
             ]
            }
           },
           "deprecated_v1": true
          }
         }
        ]
       },```

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
fe9c15192934f034f4b2b45e1feaf0d6ee171d60
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ff3ab9394122acd548899d5d1ae273c608ec08a8
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.

merging.. All tests passed. CLA bot stuck


undefined% shown instead of a percent

When downloading a file it shows undefined% instead of a percentage:
Downloading http://someurl/somefile.zip... undefined% undefined% undefined% undefined% Done
It seems that the percentage is not defined here:
https://github.com/Metrime/gulp-download/blob/master/index.js#L33

I think (based on the request-progress documentation) it should be state.percentage*100


Documentation Rendering

The API documentation has headings "common optimizers", "optax transformations", "apply updates", etc. However, the only thing that shows up on the API documentation sidebar in the read the docs is "common optimizers" (tested on chrome and safari).

It seems like each of these headers should also be on the sidebar (since they are not under the concept of common optimizers and represent distinct things).

Hi,
I agree with your observation. Based on the screenshot you provided, it does seem like the API documentation sidebar is missing entries for "Optax Transformations," "Apply Updates," and potentially other headings.
Here are some steps you can take to address this:
Check for configuration errors:
If you have access to the Read the Docs configuration, double-check that the table of contents for the API section is set up correctly. There might be a setting that's causing only "Common Optimizers" to be displayed.
Report the issue:
If you don't have access to the configuration or can't find any issues there, consider reporting the problem to the Optax documentation maintainers. They'll be able to investigate and make the necessary corrections.
Workaround using search:
In the meantime, you can still access the content under those headings using the search functionality within the docs. However, having them directly in the sidebar would definitely improve navigation.
I'll be waiting for your positive response!!!!

Hi! This seems to be a limitation of Sphinx Book Theme. In line 21 of this file, which defines the navigation, titles_only (wrapping the :titlesonly: directive) is set to true.
Unfortunately, the only solution, saving to fork the theme, seems to be to divide api.rst into several files and reference all of them, which can get cumbersome. I don't believe the alternative of having a single "API Documentation" heading in the navigation will look very good?
Let me know how to proceed and I'd love to work on this issue. Thank you!


[ci] [R-package] allow more possibly-lost warnings from valgrind

Contributes to the v4.2.0 release (#6191).
The latest valgrind build showed 1,056 bytes "possibly lost", all from code paths that create threads w/ pthread_create. (https://github.com/microsoft/LightGBM/pull/6191#issuecomment-1846240329)
In the past, CRAN has allowed some of these as false positives. (https://github.com/microsoft/LightGBM/pull/6191#issuecomment-1846502740)
This PR proposes modifying the test script for that job to acknowledge that this set of findings from valgrind are allowed.
Notes for Reviewers
It would be better to suppress specific cases instead of do text-parsing to enforce a maximum number of "possibly lost" reported bytes... but that will take a bit more time to develop. I've documented it in #6231 and put good first issue on it to try to increase the likelihood that someone comes and contributes that.

/gha run r-valgrind

Could I please get a review on this this week? This is the last PR I think needs to be done before we put up release v4.2.0 (#6191). I'd like to get that release out this week, to get that quantized training fix (#5994) out to more users.

Thanks @jmoralez ! I'm going to merge this to continue with testing the release candidate.
For what it's worth, the R package has been up for 11 days now and CRAN has not reported any valgrind issues yet.

https://cran.r-project.org/web/checks/check_results_lightgbm.html


Rust: maybe change slog to tracing?

https://crates.io/crates/tracing
tracing with tracing-opentelemetry or else.

@CherishCai Yes. It is still at a very early stage of development. Things are open to change as long as it makes sense.

@lizhanhui 同学组织下 Rust 客户端的开发嘛，我这边可以领一些任务

发现这个仓库：https://github.com/messense/rocketmq-rs
也很久没维护了，它占用了 crates rocketmq ，或者可以邀请维护者参与到官方仓库开发

@CherishCai 感谢你的关注，为了让社区的同学可以更快速熟悉和参与贡献，我们最近会发布一些任务和具体步骤。你可以先参照其他语言比较成熟的版本先熟悉一下，如果有任何建议和想法，也欢迎随时反馈。
对 rocketmq-rs 这个 repo 的建议，我认为是非常有意义的，我们也会尝试联系对应的开发者。

发现这个仓库：https://github.com/messense/rocketmq-rs 也很久没维护了，它占用了 crates rocketmq ，或者可以邀请维护者参与到官方仓库开发

This is not an issue. The repository author, messense, is willing to transfer the crate as long as there is a need.

@lizhanhui 同学组织下 Rust 客户端的开发嘛，我这边可以领一些任务

I am currently sketching the modular design with very limited bandwidth. Once the design is completed, I would create a bunch of task issues.

Hi, happy to transfer the rocketmq crate to rocketmq-clients maintainers, @aaron-ai doesn't have a crates.io account so I can't transfer it now.

Hi, happy to transfer the rocketmq crate to rocketmq-clients maintainers, @aaron-ai doesn't have a crates.io account so I can't transfer it now.

@messense Sorry, I created crates.io account just now. Could you transfer it to me now?

Done.

另外可以学习借鉴 https://github.com/streamnative/pulsar-rs


Some problems with the current version

Hi,
i have some problems with the current saltstack version.
1. 'NoneType' object has no attribute 'decode'
After i accept the first minion key the dashboard shows this error:
AttributeError at /

'NoneType' object has no attribute 'decode'

Request Method: 	GET
Request URL: 	http://<IP_ADDRESS>/
Django Version: 	1.8.4
Exception Type: 	AttributeError
Exception Value:

'NoneType' object has no attribute 'decode'

Exception Location: 	/opt/saltshaker/dashboard/views.py in index, line 41
Python Executable: 	/usr/bin/python
Python Version: 	2.7.11

the minion subpage is available!
2. Command executing doesn't work
if i try to execute a command:
OperationalError at /execute/minions_shell_result/

(1054, "Unknown column 'command_tag' in 'field list'")

Request Method: 	POST
Request URL: 	http://<IP_ADDRESS>/execute/minions_shell_result/
Django Version: 	1.8.4
Exception Type: 	OperationalError
Exception Value:

(1054, "Unknown column 'command_tag' in 'field list'")

Exception Location: 	/usr/lib/python2.7/dist-packages/MySQLdb/connections.py in defaulterrorhandler, line 36
Python Executable: 	/usr/bin/python
Python Version: 	2.7.11

3. Highstate page doesn't load
If i open the highstate page it generated this error:
ProgrammingError at /states_config/highstate/

(1146, "Table 'saltshaker.states_config_highstate' doesn't exist")

Request Method: 	GET
Request URL: 	http://<IP_ADDRESS>/states_config/highstate/
Django Version: 	1.8.4
Exception Type: 	ProgrammingError
Exception Value:

(1146, "Table 'saltshaker.states_config_highstate' doesn't exist")

Exception Location: 	/usr/lib/python2.7/dist-packages/MySQLdb/connections.py in defaulterrorhandler, line 36
Python Executable: 	/usr/bin/python
Python Version: 	2.7.11

FYI
I'm using Ubuntu 16.04 and salt 2016.3.0+ds-1 from the official repo.
Best regards

please use 2.1.1v
https://github.com/yueyongyue/saltshaker/releases

same problems with version 2.1.1
AttributeError at /

'NoneType' object has no attribute 'decode'

Request Method: 	GET
Request URL: 	http://<IP_ADDRESS>/
Django Version: 	1.8.4
Exception Type: 	AttributeError
Exception Value:

'NoneType' object has no attribute 'decode'

Exception Location: 	/opt/saltshaker-2.1.2/dashboard/views.py in index, line 41
Python Executable: 	/usr/bin/python
Python Version: 	2.7.11
Python Path:

['/opt/saltshaker-2.1.2',
 '/usr/local/lib/python2.7/dist-packages/pip-7.1.2-py2.7.egg',
 '/usr/lib/python2.7',
 '/usr/lib/python2.7/plat-x86_64-linux-gnu',
 '/usr/lib/python2.7/lib-tk',
 '/usr/lib/python2.7/lib-old',
 '/usr/lib/python2.7/lib-dynload',
 '/usr/local/lib/python2.7/dist-packages',
 '/usr/lib/python2.7/dist-packages']

Server time: 	Mo, 13 Jun 2016 07:53:10 +0200

不好意思，当时没发现，这个由于代码冲突导致的，没有及时发现，请使用2.1.2 此问题已经解决

is version 2.1.3 released now?

YES version 2.1.3 is the latest version

same error:
AttributeError at /

'NoneType' object has no attribute 'decode'

Request Method: 	GET
Request URL: 	http://<IP_ADDRESS>/
Django Version: 	1.8.4
Exception Type: 	AttributeError
Exception Value:

'NoneType' object has no attribute 'decode'

Exception Location: 	/opt/saltshaker-2.1.3/dashboard/views.py in index, line 41
Python Executable: 	/usr/bin/python
Python Version: 	2.7.11
Python Path:

['/opt/saltshaker-2.1.3',
 '/usr/local/lib/python2.7/dist-packages/pip-7.1.2-py2.7.egg',
 '/usr/lib/python2.7',
 '/usr/lib/python2.7/plat-x86_64-linux-gnu',
 '/usr/lib/python2.7/lib-tk',
 '/usr/lib/python2.7/lib-old',
 '/usr/lib/python2.7/lib-dynload',
 '/usr/local/lib/python2.7/dist-packages',
 '/usr/lib/python2.7/dist-packages']

Server time: 	Mo, 13 Jun 2016 13:36:31 +0200

very strange

Are you sure ? What is the version of saltstack ?

I have reinstalled the salt-master.
now it works :-/


Components props order matters

Hi, nice lib. But, here is a really confusing behavior:
<Col md={3} sm={6} xs={12}>  - doesn't work
 <Col xs={12} sm={6}  md={3}> - work.
Its the first time ever I see that the order of props has importance. :(

Due to Object.keys() used here
https://github.com/LoicMahieu/react-styled-flexboxgrid/blob/master/src/components/Col.js#L41
We map all keys given in props and generate media queries for each. I think I thought at the time that it is not a good idea... ^^ Depending on keys order is a terrible idea.
We could sort the keys but how? Breakpoints keys come from the config and can be modified by the developper.
I hope find a another solution that hard-code an array with the sorted keys.
Any idea?
I don't think I could find time for implement it so, feel free to propose a pull request ;)


error  :batch_images[i] = image ValueError: setting an array element with a sequence.

File "/home/whj2023/unet3/unet3/data_generator.py", line 79, in getitem
return self.__data_generation(indexes)
File "/home/whj2023/unet3/unet3/data_generator.py", line 144, in __data_generation
batch_images[i] = image
ValueError: setting an array element with a sequence.
why?

@wanghuaiji Kindly share some details about the experiment settings in which you received this error, or you should share Colab with this error so that I can debug it.


bug(forge inspect): different deployedBytecode returned for same artifact (?)

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (f625d0f 2024-04-02T00:16:42.810315000Z)
What command(s) is the bug in?
forge inspect
Operating System
macOS (Intel)
Describe the bug
Given a repository, one person on our team has run
git checkout mainnet-v0.1.0
forge inspect /path/to/contract/contract.sol:contract deployedBytecode > inspectcode
sha256sum inspectcode

which has produced
fa59be8a26904a24c76db7a5dcd95db95ae37a6aaf3679068fda1b6008919688
However , a different team member has checked out to the same commit, with the same foundry version , the same OS , and the same sha256sum version and has produced a different hash
68a0d0563c6caf1f4e64c7d873b5c242cfc812da73987a995625aa9414f936fa
Both were on a clean git tree , of the same commit , same origin , etc.
All foundry configuration files are tracked.
All submodules were clean.
Output files attached, they were also verified to be different using diff
inspectcode1.txt
inspectcode2.txt

I think there is a high likelihood this is unrelated to Forge given the forge inspect simply accesses the generated artifact

This is most likely due to a different solidity metadata hash, which can differ between machines. @RonTuretzky if you set the bytecode hash to none in the foundry config and test again, I suspect the code hashes will then match

This is most likely due to a different solidity metadata hash, which can differ between machines. @RonTuretzky if you set the bytecode hash to none in the foundry config and test again, I suspect the code hashes will then match

Correct! thank you!


Update Envoy to the same version used by Istio 0.8.0 pre-release

Signed-off-by: Romain Lenglet<EMAIL_ADDRESS>

test-me-please

test-me-please

The CI build timed out:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/2623/
For instance, Runtime tests took 1h23, and K8s tests took 1h30 before getting killed.

test-me-please

test-me-please

Needs a rebase due to segfault fix.

While you are at it, this branch has a bit cleaner replacements for the http_connection_manager.h in cilium_l7policy.h & .cc: https://github.com/cilium/cilium/tree/pr/envoy-rebase-2018-04-21

Should also rebuild the v2 API .pb.go files and include changes in them in the PR.

CI build failure:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/2647/execution/node/60/log/
19:55:27 RuntimeValidatedPolicyEnforcement
19:55:27 /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:280
19:55:27   Policy Enforcement Always
19:55:27   /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:280
19:55:27     Always to Never without policy [It]
19:55:27     /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:312
19:55:27
19:55:27     Expected
19:55:27         <bool>: false
19:55:27     to be true
19:55:27
19:55:27     /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/runtime/Policies.go:296

test-me-please

test-me-please

Green build with the updated cilium-builder image:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/2651/

Waiting on a green packer-ci-build build for this branch, then will update with the updated Vagrant VM box version:
https://jenkins.cilium.io/job/cilium/job/packer-ci-build/job/master/57/

Got a green build of the Vagrant box (version 57):
https://jenkins.cilium.io/job/cilium/job/packer-ci-build/job/master/57/
Updated the Vagrantfiles in this PR.

test-me-please

Manually that the dev Vagrant box v57 comes up fine with this branch.

Green CI build:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/2655/

Rebased.

test-me-please


Where to download gts?

Can any kind person tell me where to download the gts in Occ3D? Thank you!

+1

+1

https://drive.google.com/drive/folders/1Xarc91cNCNN3h8Vum-REbI-f0UlSf5Fc

Thank you!
The nuscenes is full or mini?
And lidarseg is downloaded in www.nuscenes.org separately？The nuscenes dataset does not have lidarseg.

Thank you! The nuscenes is full or mini? And lidarseg is downloaded in www.nuscenes.org separately？The nuscenes dataset does not have lidarseg.

Thank you for your interest.For the lidarseg I think you can register and log in to the nuscenes official website www.nuscenes.org, and then find the downloads in nuScenes. We refer to the All dataset, but occworld actually uses the data in occ3, which can be found in https://github.com/Tsinghua-MARS-Lab/Occ3D .


Update virtual-network-peering-overview.md

@lastcoolnameleft : Thanks for your contribution to the Azure documentation! The author, @NarayanAnnamalai, has been notified to review your proposed change.

@lastcoolnameleft  Sorry for the delay. This issue was fixed in a separate PR. Thank you. #please-close


Got some unexcepted chars in original_logs.log

Hi bro, thanks for you Excellent work. I got some problems now.
After my build project, LSP not works. And I found .compile file is empty.
Then I parse my xcodebuild log with the command below and got UnicodeDecodeError.  And I found some unexcepted chars appear in the log file.
When I build with xcodebuild, the chars disappears.
I have no idea about that, any suggestion for this?
 xcode-build-server parse .nvim/xcodebuild/original_logs.log -o .nvim/xcodebuild/.compile

original_logs.log
xcodebuild -workspace xxx.xcodeproj -scheme xxx -configuration Debug > build.log
build.log

If you manually run xcodebuild you don't have this character in logs?

@TMTBO Could you switch to this branch and confirm if it resolves your issue?

Btw. why do you need to run xcode-build-server parse?

Something about Why I need to run xcode-build-server parse:
Because I run Build Project (Clean Build) with xcodebuild.nvim, I cannot get LSP works. And I found that I donnot have a .compile file under .nvim/xcodebuild folder. So I run xcode-build-server parse and got  the error above.
With the new branch, xcode-build-server parse can generate .compile file and LSP works perfectly.
But Build Project (Clean Build) still cannot generate .compile file automaticly.

Thank you very much. I never knows that before. I always think that xcode-build-server only works with .compile file which just like clangd work with compile_commands.json.

On another larger project, I encountered a new problem.
The original_logs.log said ** BUILD SUCCEEDED **. But the xcodebuild.log said  Build Failed. It is actually compiled successfully, and there are compiled app files in the product directory. And it worked fine for me with Xcode.

The plugin prints failed build when there is any error detected. Can you search original_logs logs for error:  phrase?

Yes, there are some fatal error in the logs. It doesn't seem to affect compilation results.

Weird that the build passes with fatal errors :D. Maybe try resolving this issue?

Okay, that's all right. I'll check it out later. Thanks.

I'm closing this ticket, as the initial issue has been resolved. If needed please create a new ticket.


Add sorting functionality to tables

This pull request implements sorting functionality for the tables.

Why there is no filter over "Type"? On the liveness there is such functionality.

there is a typo in filter name "Technology" -> "Type"

Maybe there should also be a sorting on Summary over "Purpose"
Is the sorting over Mkt Share needed? it is the same as Total

is sorting on risks desired? I think sorting over risks should be based on the colors/severity not the name

Decide on the indexes behavior for sorting and filtering, both should be aligned - is this todo resolved?

Maybe on Liveness the "coming soon" should be above "n/a"


cleanup(pubsub)!: inconsistent names in PublisherOptions

BREAKING CHANGE

Fix inconsistent naming for PublisherOptions attributes controlling the
maximum number of messages per batch and the maximum number of bytes per
batch.

Fixes #5196

This change is

/cc: @kamalaboulhosn


abc calendar

Merge after https://github.com/oirom/atcoder_calendar/pull/30 is merged.
Then, create PR to oirom/atcoder_calendar:master.

自分のCloud Functionで動作中


Verify that failover can be performed at the provider level

Show that load balancing will automatically route around a failed provider

Note: the health check interval is currently 60 seconds

Ran a test checking for the rendered-by headers in a loop and scaling Kong to 0. Cloudflare detected it and all traffic started going to only one provider.
https://www.youtube.com/watch?v=2fKI7N7PKV0


Tailwind .font-mono not being applied properly

I see the mono font stack being applied here, but the compiled CSS just contains the font-family: operatormono. If that isn’t installed on your machine, all code examples look like this:

I’m not familiar with Tailwind, so I’m not sure why this isn’t working exactly.

It probably hasn't been published yet.
I'm pretty sure @thetutlage will do it in a while 👍


Hikari CP Connection Pool has active connections, but no processing is done

Hi,
We are using Hikari pool for one of the application. When the application starts up, it starts with 50 connections , active=0, idle =0.
However, after some time the pool status is below:
04:25:50.024 [HikariPool-1 housekeeper] DEBUG com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Pool stats (total=50, active=10, idle=40, waiting=0)
04:25:50.024 [HikariPool-1 housekeeper] DEBUG com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Fill pool skipped, pool is at sufficient level.
04:26:20.024 [HikariPool-1 housekeeper] DEBUG com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Pool stats (total=50, active=10, idle=40, waiting=0)
04:26:20.025 [HikariPool-1 housekeeper] DEBUG com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Fill pool skipped, pool is at sufficient level.
04:26:50.025 [HikariPool-1 housekeeper] DEBUG com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Pool stats (total=50, active=10, idle=40, waiting=0)
04:26:50.025 [HikariPool-1 housekeeper] DEBUG com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Fill pool skipped, pool is at sufficient level.
The 10 active connections, we are not sure as we do not see any processing done for those. Request your help to rectify this
Thanks

Hi @sankeeth-chinta. Are you still facing this issue? If not, please share how you have resolved this.


Adjust recommendation type and reviewers

Signed-off-by: Francesco Murdaca<EMAIL_ADDRESS>Fixes: https://github.com/thoth-station/jupyter-nbrequirements/issues/277

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign sesheta after the PR has been reviewed.
You can assign the PR to them by writing /assign @sesheta in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

Pytest Test failed! Click here
running test
Searching for setuptools>=40.3.0
Reading https://pypi.org/simple/setuptools/
Downloading https://files.pythonhosted.org/packages/6d/38/c21ef5034684ffc0412deefbb07d66678332290c14bb5269c85145fbd55e/setuptools-50.3.2-py3-none-any.whl#sha256=2c242a0856fbad7efbe560df4a7add9324f340cf48df43651e9604924466794a
Best match: setuptools 50.3.2
Processing setuptools-50.3.2-py3-none-any.whl
Installing setuptools-50.3.2-py3-none-any.whl to /workspace/repo/.eggs
writing requirements to /workspace/repo/.eggs/setuptools-50.3.2-py3.6.egg/EGG-INFO/requires.txt

Installed /workspace/repo/.eggs/setuptools-50.3.2-py3.6.egg
running egg_info
creating jupyter_nbrequirements.egg-info
writing jupyter_nbrequirements.egg-info/PKG-INFO
writing dependency_links to jupyter_nbrequirements.egg-info/dependency_links.txt
writing requirements to jupyter_nbrequirements.egg-info/requires.txt
writing top-level names to jupyter_nbrequirements.egg-info/top_level.txt
writing manifest file 'jupyter_nbrequirements.egg-info/SOURCES.txt'
reading manifest file 'jupyter_nbrequirements.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'CHANGELOG.md'
writing manifest file 'jupyter_nbrequirements.egg-info/SOURCES.txt'
running build_ext
Jupyter Require found itself running outside of Jupyter.
jupyter_nbrequirements (unittest.loader._FailedTest) ... ERROR

======================================================================
ERROR: jupyter_nbrequirements (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: jupyter_nbrequirements
Traceback (most recent call last):
  File "/usr/lib64/python3.6/unittest/loader.py", line 462, in _find_test_path
    package = self._get_module_from_name(name)
  File "/usr/lib64/python3.6/unittest/loader.py", line 369, in _get_module_from_name
    __import__(name)
  File "/workspace/repo/jupyter_nbrequirements/__init__.py", line 38, in <module>
    from jupyter_require import execute as executejs
  File "/opt/app-root/lib/python3.6/site-packages/jupyter_require/__init__.py", line 34, in <module>
    from .notebook import link_css
  File "/opt/app-root/lib/python3.6/site-packages/jupyter_require/notebook.py", line 30, in <module>
    from .core import execute_with_requirements
  File "/opt/app-root/lib/python3.6/site-packages/jupyter_require/core.py", line 279, in <module>
    require = RequireJS()
  File "/opt/app-root/lib/python3.6/site-packages/jupyter_require/core.py", line 90, in __new__
    raise EnvironmentError(msg)
OSError: Jupyter Require found itself running outside of Jupyter.

----------------------------------------------------------------------
Ran 1 test in 0.000s

FAILED (errors=1)
Test failed: <unittest.runner.TextTestResult run=1 errors=1 failures=0>
error: Test failed: <unittest.runner.TextTestResult run=1 errors=1 failures=0>

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: harshad16
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 [harshad16]

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


Template registration should allow registration of images with small coverage

Especially for images that do not cover two vertebral levels and for which it is not possible to provide two labels. See related discussion here: https://sourceforge.net/p/spinalcordtoolbox/discussion/help/thread/d93860bf/?limit=25#5d76
This issue could be easily fixed. Indeed, the reason why we want two labels is to compute an affine transformation in order to pre-register the vertebral levels. For images with small coverage, such a pre-registration is not necessary as it wouldn't affect much the images. Therefore, only one label (for exemple, on the inter-vertebral disk) would be necessary.

The solution would be to replace the affine transform by a translation computed between the inter-vertebral disk label provided by the user and the corresponding label in the template. Ideally, we would need to create new labels in the template space for inter-vertebral disks. However, we can also use the middle position between the two surrounding vertebral labels.

I've put some data on sct_issue: 20151011_issue_574

working on it:
https://github.com/neuropoly/spinalcordtoolbox/tree/jca_issue574

fixed in https://github.com/neuropoly/spinalcordtoolbox/pull/1451
it is now possible to register with only one label centered on a disc (use flag -ldisc)


Agent Forwarding

Was looking at how to access on remote machines, is a standard ssh workflow, but might be useful to have it here too.

Thanks @Wheest!


[Fix #12983] Fix false positives for Style/SendWithLiteralMethodName

Fixes #12983.
This PR fixes false positives for Style/SendWithLiteralMethodName using send with writer method name.
Writer methods with names ending in = are always permitted because their behavior differs as follows:
def foo=(foo)
  @foo = foo
  42
end

foo(1)         # => 1
send(:foo=, 1) # => 42

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

I don't think the example code is correct.
send(:foo=, 1) would get corrected to foo=(1) which is a variable declaration! So that method doesn't even get called anymore and in that sense it makes sense for the return value to be 1.

This indicates a method call on self, not a variable declaration:
$ ruby -e "send(:foo=, 1)"
-e:1:in `<main>': undefined method `foo=' for main (NoMethodError)

send(:foo=, 1)
^^^^

$ ruby -e "def foo=(foo); 42 end; p send(:foo=, 1)"
42

Yes, but the previous behaviour of autocorrect would have produced foo=(1) which is not. The example code isn't executable because foo isn't defined.

Ah, I get it. That is a mistake in the example. It has been fixed in https://github.com/rubocop/rubocop/commit/967fe88135188c9d74494cbd4355180c140c4a1a.

Yes, that looks good. Thank!


Feature Request: nrpe + plugins

pfSense includes the nrpe package plus nagios-plugins. We use this extensively to monitor our many pfsense's. It's the last gap between pfsense and opnsense which is blocking us from switching them all over.
See also https://docs.netgate.com/pfsense/en/latest/packages/package-list.html

I think the ports package is already in our build list:
https://github.com/opnsense/tools/blob/85d1d841230b7e4aa5d9ce45fc667e870b24e001/config/19.7/ports.conf#L94
Let's label this help-wanted to see if someone wants to create a plugin for it.

If it's only nrpe I can do this later this year

NRPE isnt much use without some nagios plugins (either nagios-plugins or monitoring-plugins).
pfsense rather unceremoniously dumps the entire nagios-plugins port in, which includes lots of plugins that are irrelevant on a firewall. but on the plus side, you can still use nrpe+plugins to monitor stuff.

Close with latest PR?


ydlidar package is out of date

At least from my personal experience. The version of the ydlidar package that is included in the linorobot is out of date and doesn't work correctly. I was able to solve my problem my using the current package: https://github.com/YDLIDAR/ydlidar_ros. It is called ydlidar-ros while linorobot refers to it as just ydlidar so some renaming was necessary as well.

@pitosalas If your radar is rplidar, it is recommended that you use the latest ros driver package: https://github.com/YDLIDAR/ydlidar_ros_driver

Thanks for this info, I'm also using Ydlidar, and making a machine right now.


[Public Catalog] Right rail "sign up" text shoud link to the New Relic Sign up flow

This text should link to our standard sign up flow. https://newrelic.com/signup

Acceptance Criteria

[x] change text and link correctly
[x] all packs should have this link present.

@jpvajda I wasn't 100% sure on the way this should look, here's what I have so far:

@rudouglas That works. 🧑🎨


Roll Engine from fd6b409f950b to affc4216fe08 (16 revisions)

https://github.com/flutter/engine/compare/fd6b409f950b...affc4216fe08
2020-12-17<EMAIL_ADDRESS>Roll Skia from b64da3907f76 to 81da68af2ecf (7 revisions) (flutter/engine#23142)
2020-12-17<EMAIL_ADDRESS>Roll Skia from 995f0366bd21 to b64da3907f76 (1 revision) (flutter/engine#23135)
2020-12-17<EMAIL_ADDRESS>Roll Skia from 20f1b3462878 to 995f0366bd21 (2 revisions) (flutter/engine#23132)
2020-12-17<EMAIL_ADDRESS>Roll Skia from 7839f66540b6 to 20f1b3462878 (1 revision) (flutter/engine#23129)
2020-12-17<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from TIKHoiQyP... to wu6yV-_BL... (flutter/engine#23127)
2020-12-17<EMAIL_ADDRESS>Roll Skia from 1d89532d5988 to 7839f66540b6 (1 revision) (flutter/engine#23126)
2020-12-17<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from acylwa3i4... to chLTYsKMR... (flutter/engine#23125)
2020-12-17<EMAIL_ADDRESS>Roll Skia from d6f2338ab194 to 1d89532d5988 (1 revision) (flutter/engine#23122)
2020-12-17<EMAIL_ADDRESS>[web] Rich paragraph getBoxesForRange (flutter/engine#23098)
2020-12-17<EMAIL_ADDRESS>Rename PointerState.isDown as per style guide (flutter/engine#23120)
2020-12-17<EMAIL_ADDRESS>[web] Tests for rich paragraph DOM (flutter/engine#23097)
2020-12-17<EMAIL_ADDRESS>Roll Skia from 85fa75616dfe to d6f2338ab194 (3 revisions) (flutter/engine#23119)
2020-12-17<EMAIL_ADDRESS>[web] Switch web-render option default to auto (flutter/engine#23090)
2020-12-16<EMAIL_ADDRESS>Roll Skia from 6f31e27f1e29 to 85fa75616dfe (7 revisions) (flutter/engine#23118)
2020-12-16<EMAIL_ADDRESS>fix crash in FontCollection::init() when FontFamily is empty (flutter/engine#23019)
2020-12-16<EMAIL_ADDRESS>bump fuchsia toolchain to clang-12 (flutter/engine#23067)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from TIKHoiQyPn19 to wu6yV-_BLd6N
fuchsia/sdk/core/mac-amd64 from acylwa3i4p-j to chLTYsKMRF0c
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Gold has detected about 23 untriaged digest(s) on patchset 16.
View them at https://flutter-gold.skia.org/cl/github/72529

Commit queue failed; closing this roll.


'TinDog is an website made to  meet interesting dogs nearby ;)'

here I used the  HTML,CSS,BOOTSTRAP framework and also the jQuery to make website responsive

skills like html,css,bootstrap and jQuery were used to make the website.