Make dash a valid identifier

Why isn't dash ("-") a valid identifier? For example I cannot get the data when I specify a filter like sc_host_name.my-pc
My json:
{
  "sc_host_name":{
    "my-pc":{
      "ip":"<IP_ADDRESS>"
    }
  }
}

I get an error
/usr/local/rvm/gems/ruby-2.2-head/gems/jmespath-1.1.3/lib/jmespath/parser.rb:41:in `parse': expected :eof got identifier (JMESPath::Errors::SyntaxError)
        from /usr/local/rvm/gems/ruby-2.2-head/gems/jmespath-1.1.3/lib/jmespath/caching_parser.rb:25:in `block in cache_expression'
        from /usr/local/rvm/gems/ruby-2.2-head/gems/jmespath-1.1.3/lib/jmespath/caching_parser.rb:23:in `synchronize'
        from /usr/local/rvm/gems/ruby-2.2-head/gems/jmespath-1.1.3/lib/jmespath/caching_parser.rb:23:in `cache_expression'
        from /usr/local/rvm/gems/ruby-2.2-head/gems/jmespath-1.1.3/lib/jmespath/caching_parser.rb:16:in `parse'
        from /usr/local/rvm/gems/ruby-2.2-head/gems/jmespath-1.1.3/lib/jmespath/runtime.rb:51:in `search'
        from /usr/local/rvm/gems/ruby-2.2-head/gems/jmespath-1.1.3/lib/jmespath.rb:33:in `search'

If I add - to the VALID_IDENTIFIERS in lexer.rb it works like a charm.

Can you provide a sample expression to demonstrate the issue?  Here is what I attempted:
require 'jmespath'

JMESPath.search("\"-\"", { "-" => true })
#=> true

JMESPath.search('"-"', { "-" => true })
#=> true

Please note, that according to the JMESPath grammar, the dash character needs to be expressed as a quoted identifier.

- is not valid in unquoted identifiers as it is used for negative numbers. We also might add support in the future for addition, subtraction, etc, which would preclude us from allowing dashes in unquoted identifiers. In order to work around this, you will need to quote the identifier e.g., "foo-bar".

Indeed if you quote it's ok

Closing as a non issue as this is currently to the spec.


Improve k8s short-circuit documentation

Made the explanations more explicit
Highlight where domain socket must be mounted

Closes #9574

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4754/
Test PASSed.

@ZacBlanco not cherry-picking this to branch-2.0 as there is no helm and the domain socket default host path is different.

alluxio-bot, merge this please.

If I cherry pick in a new PR with the relevant changes mentioned would you merge that one too?


ImageLists and Menus

Hi,
It is not a big issue, but all of editor's ImageList and PopupMenu properties are typed as "final" types as TImageList and TPopupMenu. It would be very useful to change those types to TCustomImageList and TCustomPopupMenu in order to make you editor compatible with third party component sets.
Thanks!

PopupMenu comes from TControl class, I won't create my own over it. TImageLists are changed to TCustomImagelists.


Added the About & PS Section

I've added the about and problem statement section to index.html with the footer.
For better UX, I've implemented the particle.js theme.
Little change in style.css for footer font.

Deploy Preview: Summer Hacks Preview PR#11


Weird behavior with checkboxes in table layout

It used to work well on v5.2 i believe.
Expected Behavior
By clicking a checkbox or it's label, it has to get toggled.
Actual Behavior
When having multiple rows on a table, by clicking any checkbox it has a chance to randomly toggle some previous checkbox !
Steps to Reproduce the Problem

Fresh installation of laravel
Fresh installation of orchid 5.3 | 5.4
Seeding User table by adding factory(\App\User::class, 20)->create(); to DatabaseSeeder.php and running php artisan db:seed
Replacing first Column of UserListLayout.php with below code

TD::set('id', 'ID')
                ->render(function (User $user){
                    return CheckBox::make('users[]')
                        ->value($user->id)
                        ->placeholder($user->getNameTitle())
                        ->checked(false)
                        ->render();
                }),

Specifications

ORCHID Version:5.3 , 5.4
Laravel Version: 5.8
PHP Version:7.2
Database Version: SQlite

Screen capture

This is a problem because all your fields have the same name.
https://github.com/orchidsoftware/platform/issues/874
An earlier example
i will try to solve it as soon as possible

Did you manage to reproduce the problem after the update?

just checking..

Works well, Thanks!


Add branch and release guidance in contributing.md

@tushargupta51 @brentschmaltz @bgever
I added a CONTRIBUTING.md with branch, build, test, and contribution information. I added a link to it in the readme.md. This will go into master so it's on the repo landing page. This addresses #402.
When we create new branches, we'll need to make sure to keep this up to date.

Hi @polita, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Polita Paulus). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

Alright, I fixed the 3.x assembly list. @tushargupta51 and @brentschmaltz, can you take a look?

@polita You might need to rebase against master again since @brandwe recently updated readme with security reporting section. :shipit:


Spyder --> Error: It seems the symlink source is not there

https://github.com/caskroom/homebrew-cask/blob/master/Casks/spyder.rb is giving me troubles...
$ brew cask install spyder # generates...
==> Downloading https://bitbucket.org/spyder-ide/spyderlib/downloads/spyder-2.3.4-py2.7.dmg
######################################################################## 100.0%
Error: It seems the symlink source is not there: '/opt/homebrew-cask/Caskroom/spyder/2.3.4/Spyder.app'

I did the usual brew cask cleanup and brew cask doctor but still no success.  It is just me?
@ccordoba12 mentioned in https://github.com/caskroom/homebrew-cask/pull/8130 that Spyder is released in both Python2 and Python3 versions but Cask only seems to have a formula for the Python2 version.

The most recent release appears to be 2.7-only. I am not sure whether future versions will remain so; we could use feedback from the Spyder maintainers to decide on a course of action.

I'm sorry for not releasing more dmg's for Python 3. They are only working correctly on 10.7, which is where I generate them.
On other Mac versions, it's not possible to start Python nor IPython consoles, which is a major drawback for our users.
We think that's caused by a bug in py2app, but we're still investigating about it :-)

@ndr-qef The fix above did not solve the problem when I made that change to /usr/local/Cellar/brew-cask/0.53.3/Casks/spyder.rb and tried the install again.
@ccordoba12 An alternative to py2app is PyInstaller which makes .exe on Windows and .app on Macs.

@ccordoba12, thanks for your reply. It is certainly sensible to only provide releases which work on recent OS X versions.
We will keep our package on Python 2 for the near future; later on, we can reconsider the problem according to your recommendations.
@cclauss, the cask works on my machine. Could you run brew update and attempt the conventional brew cask install spyder?

That works!  Thanks much!

Hey guys, I released a new dmg for Python 3 which, according to two different sources, is working correctly now.
But I'd like to ask you to demand for this one a Mac version higher than or at least equal to 10.9. It won't work on older versions, so I don't want to deal with bug reports for them :-)
However, our Python 2.7 dmg works with 10.7 and higher :-)
Thanks.


Integrate with piston_image

The task of loading an image into a gfx-rs texture can be streamlined. We could have a gfx_image repository here to provide some bridging functions.

There is a library used in Hematite: https://github.com/pistondevelopers/gfx_texture

Btw, it is also used in gfx_graphics.

@bvssvni thanks! It may need some work, but this is exactly what I wanted.


Automatic reservation of subnets and ip addresses

In our setup a central function of an ipam system is to handle the reservation of free ip addresses and subnets, this is crucial for fully automated server provisioning workflows. So please have a look at the ip reservation functions of tools like phpipam and especially nipap and generously steal concepts from them and adapt them accordingly ;)

This is way to broad to mark as a feature request. Could you please enumerate the specific workflow you'd like to see?

In PHPIPAM we have a "free IP's" tool that breaks down what free prefixes are available amongst our aggregates
When provisioning it's nice to know what block you can grab and go with

I'll gladly try to precise my intention. If I'm going to add a new server to a subnet, I don't want to search manually for a free ip in that subnet but instead have the ability to add a entry to netbox and let netbox pick the first free ip in that subnet, return it to the caller and in the same atomic transaction add an entry to the netbox database so that ip is not free anymore.
Have a look at nipap's "add from-prefix" command for inspiration: https://spritelink.gitbooks.io/nipap-user-guide/content/cli/add_a_prefix.html
This workflow could also be implemented for subnets, which is especially helpful for ipv6 setups. The use case would be "give me the first free /64 from this /56 and reserve it for me".
Hopefully this makes it clear.
(My dream scenario would be the different open source dcim/ipam tools being able to interact with each other and combine their best features, so one could combine the snmp discovery of netdot, the ipam engine of nipap with the polished interface and integration of the different subsystems of netbox. But I fear that is no a very realistic vision.)

+1. this would be great. it's nice to see what's specifically available, reserved, blocked, in use, and not guess based on what's not listed in the IPAM. in my experience, you absolutely cannot count on others to mark an IP used if they provision a server or appliance.

I think this was the original issue before https://github.com/digitalocean/netbox/issues/289 and was completed with v1.4.1

This issue also deals with marking IP addresses as reserved, which has not yet been implemented.

I agree the "let netbox pick the first free ip in that subnet" feature exists as of v1.4.1

I'm going to close this out as it seems to have been addressed by annotating available prefixes and IPs. I'm not sure that a blind "give me the first free IP" in a given prefix is particularly useful. But if we did implement something like that, it would be an API endpoint.


Missing validation for method parameters

All methods should accept parameters as object key-value pairs and validation to be added for all parameters.

Validations added


octoblox 0.5.0rc delegation issues & query

i've noticed the recent development and support for delegation domains.  my company has same same setup, we've got lots of delegations, very interested in this.
i've tested the v0.5.0rc against our infoblox, have got a bit of API issues, just wondering what's the Infoblox version, API version the octoblox code is targeted? or what it should be using?
my infoblox setup as follows:
NIOS: 8.6.1-421583
WAPI version: v2.12.1
i've got a couple of issues/errors
ISSUE 1: soa_default_ttl error
ERROR InfoBloxProvider[infoblox_dele] InfoBlox.request: 400 GET zone_delegated {'params': {'fqdn': 'sub1.apitest', '_return_fields+': 'soa_default_ttl'}, 'allow_redirects': True} { "Error": "AdmConProtoError: Unknown argument/field: 'soa_default_ttl'",
  "code": "Client.Ibap.Proto",
  "text": "Unknown argument/field: 'soa_default_ttl'"
}

reading from WAPI documentation, zone_delegated only has delegated_ttl attribute to display.  soa_default_ttl is only available for zone_auth API calls
https://ipam.illinois.edu/wapidoc/objects/zone_delegated.html?highlight=zone_delegated#zone_delegated
do you use a different WAPI version? or do i have to change my configuration in any way?
ISSUE 2: zone_format value
i've also got the FORWARDING error
ERROR InfoBloxProvider[infoblox_dele] InfoBlox.request: 400 POST zone_delegated {'data': None, 'json': {'fqdn': 'sub1.apitest', 'zone_format': 'FORWARDING', 'delegate_to': [{'name': 'ns1.sub1.apitest', 'address': '<IP_ADDRESS>'}, {'name': 'ns2.sub1.apitest', 'address': '<IP_ADDRESS>'}]}} { "Error": "AdmConProtoError: Invalid value for zone_format (\"FORWARDING\") valid values are: FORWARD, IPV4, IPV6",
  "code": "Client.Ibap.Proto",
  "text": "Invalid value for zone_format (\"FORWARDING\") valid values are: FORWARD, IPV4, IPV6"
}

again it looks like i'm using the wrong WAPI version, the valid values are FORWARD, IPV4 and IPV6 only.
also regarding the configuration.  we've got more than 50 different delegation. i'm not sure if i'm interpreting the v0.5.0 design correctly? does this imply that i'll have a very large config-file, and one for each unique delegation set plus lots of empty yaml zones for delegations? or you've got a different way of configuring this?
providers:
  config:
    class: octodns.provider.yaml.YamlProvider
    directory: ./config
    default_ttl: 3600
    enforce_order: True
  infoblox_delegated_1:
    class: octoblox.InfoBloxProvider
    endpoint: infoblox.example.com
    username: admin
    password: env/INFOBLOX_PASSWORD
    create_zones: true
    zone_type: zone_delegated
    new_zone_fields:
      delegated_to:
        - name: ns1.test.example.com
          address: <IP_ADDRESS>
        - name: ns2.test.example.com
          address: <IP_ADDRESS>
      restart_if_needed: true
  infoblox_delegated_2:
    class: octoblox.InfoBloxProvider
    endpoint: infoblox.example.com
    username: admin
    password: env/INFOBLOX_PASSWORD
    create_zones: true
    zone_type: zone_delegated
    new_zone_fields:
      delegated_to:
        - name: ns1.test.example2.com
          address: <IP_ADDRESS>
        - name: ns2.test.example2.com
          address: <IP_ADDRESS>
      restart_if_needed: true
  infoblox_delegated_3:
    ...
  infoblox_delegated_4:
    ...
  infoblox_delegated_N:

Version 0.5.0rc2 should address your concerns. It has moved the delegation logic to a separate provider class.
Handling of delegated zones within InfoBlox is a tricky problem. On one hand there is a desire to make it follow the expected OctoDNS pattern of putting the glue records in the parent domain. On the other there is the need to support the ns_group field which separates the management of zones and their NS records from the CI/CD process. It is the latter option which then permits complex administration tasks to be carried out by the InfoBlox admins without needing to involve the CI/CD system for fear of breaking something. This is also why only zone creation is supported.
As for the issue of having repeat configuration here is an example using yaml anchors which shows how common config can be de-duped.
providers:
  config:
    class: octodns.provider.yaml.YamlProvider
    directory: ./config
    default_ttl: 3600
    enforce_order: True
  infoblox: &infoblox_config
    class: octoblox.InfoBloxProvider
    endpoint: infoblox.example.com
    username: admin
    password: env/INFOBLOX_PASSWORD
    create_zones: true
    new_zone_fields:
      grid_primary:
        - name: infoblox.example.com
      ns_group: default
      restart_if_needed: true
      soa_default_ttl: 3600
      view: default
      use_grid_zone_timer: true
  delegated:
    <<: *infoblox_config
    class: octoblox.DelegatedProvider
    new_zone_fields:
      delegated_to:
        - name: ns1.test.example.com
          address: <IP_ADDRESS>
        - name: ns2.test.example.com
          address: <IP_ADDRESS>
      view: default

zones:
  example.com.: &infoblox
    sources:
      - config
    targets:
      - infoblox
  other1.example.com.: *infoblox
  other2.example.com.: *infoblox
  test.example.com.: &delegated
    sources:
      - config
    targets:
      - delegated
  test2.example.com.: *delegated
  test3.example.com.: *delegated

To address the empty zone files, version 0.5.0rc3 adds the EmptySource class which simply reports no records.
The following is all that is required for delegated zones. No other files required.
providers:
  empty:
    class: octoblox.EmptySource
  delegated:
    class: octoblox.DelegatedProvider
    endpoint: infoblox.example.com
    username: admin
    password: env/INFOBLOX_PASSWORD
    create_zones: true
    new_zone_fields:
      delegated_to:
        - name: ns1.test.example.com
          address: <IP_ADDRESS>
        - name: ns2.test.example.com
          address: <IP_ADDRESS>
      view: default

zones:
  test.example.com.: &delegated
    sources:
      - empty
    targets:
      - delegated
  test2.example.com.: *delegated
  test3.example.com.: *delegated

Version 0.5.0 will be released and this issue closed at the end of next week unless anymore issues are reported.


Add T&T records endpoints

The query is a little complex at one point. Is there a cleaner way to do do scoping? Is there any other way to assign variables in Reql?

@nick-drozd For the most part, you can save variables normally and REQL will reference them. But do let's you keep everything in the same query, so that may or may not work. I'll keep my eye out for any obvious refactors.

The /records and /records/:recordId endpoints differ slightly from what's in the design doc.

The doc has

      "properties": {
        <property name>: [
          {
            "timestamp": <integer, seconds>,
            "value": <a value matching the property's "type">
          }
        ]
      }
    },

whereas these endpoints have
test-track-and-trade_1  |             "properties": [
test-track-and-trade_1  |                 {
test-track-and-trade_1  |                     "name": "species",
test-track-and-trade_1  |                     "values": [
test-track-and-trade_1  |                         {
test-track-and-trade_1  |                             "timestamp":<PHONE_NUMBER>,
test-track-and-trade_1  |                             "value": "trout"
test-track-and-trade_1  |                         }
test-track-and-trade_1  |                     ]
test-track-and-trade_1  |                 },

This is because I couldn't figure out how to the key to evaluate rather than get converted to a string.
"But haven't you heard the good news?" you say. "ES6 has computed property keys. Just wrap the key in brackets and it will evaluate as usual."
I tried that, but Reql mangles the names:
test-track-and-trade_1  |         "properties": [
test-track-and-trade_1  |             {
test-track-and-trade_1  |                 "var_169(\"name\")": [
test-track-and-trade_1  |                     {
test-track-and-trade_1  |                         "timestamp":<PHONE_NUMBER>,
test-track-and-trade_1  |                         "value": "trout"
test-track-and-trade_1  |                     }
test-track-and-trade_1  |                 ]
test-track-and-trade_1  |             },

Anyway, if there's an easy way to fix this, I'll do it, but I don't think it's a huge difference.

I think, instead of:
...
'properties': propertyValues
              .map(propertyValue => r.expr({
                'name': getName(propertyValue),
                'values': propertyValue('values').pluck('value', 'timestamp')
              }))
...

you could do
...
'properties': propertyvalues.reduce((properties, propertyValue) => {
   properties[getName(propertyValue)] = propertyValue('values').pluck('value', 'timestamp')
}).default({})
...

@nick-drozd The pre-ES6 way to use an evaluated key is to do it in two statements. One creating the object, and the other setting the key. In other words:
const newObj = (key, value) => {
  const obj = {}
  obj[key] = value
  return obj
}

Hideous, I know, but ES6 niceties mostly don't seem to work in ReQL. You should be able to abstract this into a function or some such.

@nick-drozd Seems to work well, but I would like to see the properties updated to match the spec if possible.

I agree with @delventhalz about the properties


Str documentation should be explict about it using unicode minus

Currently the documentation for the str constructor does not mention that the unicode minus sign "\u{2212}" is used when converting negative numbers. This can be problematic to users expecting a regular behaviour for that function when scripting.
Adding something like "When converting numerical types the produced string uses the unicode minus sign ("−" U+2212) instead of the ascii minus sign ("-" U+002D)." to the docstring would be enough to prevent people from losing time debugging this odd behaviour.

Note that Typst allows using U+2212 in place of U+002D in code for the unary and binary minus signs, as well as in -=.

I stumbled on this while trying to define a dictionary that held information that I wanted to display for items indexed with negative values. Doing myDict.at(str(-1)) surpisigly wasn't able to access the key in let myDict = ("-1" : "value"). Now that I know str doesn't produce "-1" but "−1" I can update the dictionary to use it (or wait on https://github.com/typst/typst/issues/3324).


vscode-fhs run from nix develop cannot launch terminal or extensions with binaries

Describe the bug
vscode-fhs fails to launch the terminal process (and other extension issues) if launched from within a nix develop session.
Steps To Reproduce
Steps to reproduce the behavior:

Add vscode-fhs to your configuration.nix
Run git clone https://github.com/breakds/flake-example-hello-repeater
Run nix develop
Run code .
 Instead the bash process dies.
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
This also impacts cmake from the CMake Tools extension. The same problem manifests in the Nix Env Selector extension as missing symbols from nix-shell.
Notify maintainers

@eadwu @Synthetica9 @maxeaubrey @bobby285271
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
these 4 paths will be fetched (0.03 MiB download, 0.15 MiB unpacked):
  /nix/store/4ybkncn05qbhgbdxg9sxdgpm1jpdx76w-gcc-wrapper-10.3.0
  /nix/store/83l8wwrx7xs3mh9sbbj6whmyx8y4cz36-stdenv-linux
  /nix/store/c4k3fcsp5cqg9v0rpac9qbqmbkm6a7pk-binutils-wrapper-2.35.2
  /nix/store/wsjfqi1r5f6r9jvxm8kji8q0cdahfjpl-expand-response-params
copying path '/nix/store/wsjfqi1r5f6r9jvxm8kji8q0cdahfjpl-expand-response-params' from 'https://cache.nixos.org'...
copying path '/nix/store/c4k3fcsp5cqg9v0rpac9qbqmbkm6a7pk-binutils-wrapper-2.35.2' from 'https://cache.nixos.org'...
copying path '/nix/store/4ybkncn05qbhgbdxg9sxdgpm1jpdx76w-gcc-wrapper-10.3.0' from 'https://cache.nixos.org'...
copying path '/nix/store/83l8wwrx7xs3mh9sbbj6whmyx8y4cz36-stdenv-linux' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.34, NixOS, 22.05 (Quokka), 22.05.20220417.1ffba9f`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.8.0pre20220411_f7276bc`
 - channels(root): `"nixos"`
 - channels(jkolb): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

I have the same issue
 - system: `"x86_64-linux"`
 - host os: `Linux 5.17.3, NixOS, 22.05 (Quokka)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.7.0`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

I noticed this issue upgrading nixpkgs from rev 1d08ea2bd83abef174fb43cbfb8a856b8ef2ce26 to rev 30d3d79b7d3607d56546dd2a6b49e156ba0ec634
I was getting a libc error undefined symbol: __nptl_change_stack_perm.

I started having the exact same issue with code depending on libX11.so.6.
Initially I'll get GLIBC_2.34 no found (required by ...-libX11-1.7.2/lib/libX11.so.6.
Then if I add pkgs.glibc to the environment ( v2.34 ), I get a crash during resolution exactly like yours: undefined symbol: __nptl_change_stack_perm. From what I could tell in the glibc sources this is a system call, I only saw it mentioned in glibc 2.35, but I didn't dig to find out if it was "new in 2.35"; if that's the case symbol versioning in glibc itself really dropped the ball.
Still, I'm not sure how libX11.so.6 would depend on glibc-2.35 since it's not available in nixpkgs, and literally everything on my box was installed using nix.

I'm wondering if we need to be explicit about glibc versions somewhere. I'm not sure how to solve this and it makes vscode unusable.

I'm pretty sure that this is a libc mismatch.
ldd --version on my system reports: 2.34
Once in the nix develop it reports 2.32

Have any of you figured out a workaround?

I can add that if instead of specifying vscode-fhs in the environment system packages you specify vscode-with-extensions.override with the extensions explicitly listed, the terminal launches in vscode.  I'm also able to run nix commands inside of the integrated terminal of other projects that were failing due to glibc errors previously so I'd say its a step in the right direction, though managing extensions like this is not the most pleasant.
Not entirely familiar with Nix so if you know of gotchas with this method please let me know.

VSCode extension is on user's home $HOME/.vscode/extensions as per this SO. Anyone know why the vscode package doesn't allow extension installation?

I'm unable to reproduce this and the terminal works fine with:

system: "x86_64-linux"
host os: Linux 5.15.59, NixOS, 22.11 (Raccoon), 22.11.20220814.b02538b
nixpkgs rev: 5efc8ca954272c4376ac929f4c5ffefcc20551d5

In case this is helpful, I only see this issue when most of my packages are from one branch (e.g. 22.05) and my vscode-fhs is from unstable.  When using vscode-fhs from 22.05 also, I don't see this issue.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/vscode-c-cpptools-and-clangd-not-working/21902/6

In case this is helpful, I only see this issue when most of my packages are from one branch (e.g. 22.05) and my vscode-fhs is from unstable. When using vscode-fhs from 22.05 also, I don't see this issue.

I can very much confirm this is the case - I switched my project flake to use unstable and the default vscode.fhs environment worked correctly.

Is there potentially a roundabout way to fix this in which the binary is wrapped with its own libraries to avoid this issue? I have run many binaries inside of vscode-fhs but only recently did I see one that didn't work. This of course at the cost of having multiple versions of the same library taking up space on the nix store


Update pub.dartlang.org with latest markdown

Hi,
The markdown package was updated, and fixed a bug relevant to pub.dartlang.org. Specifically: https://github.com/dart-lang/markdown/issues/41
It will fix https://github.com/dart-lang/pub-dartlang-dart/issues/28
Thanks for the help!

Fixed in b7a701b77ef0c1eddc9a5f147cb5c21fe37e5d56, updated to version 0.8.0 of package:markdown.


FIX-#2164: Fix tests for BaseOnPython: test___repr__, test_dtype_empty

Signed-off-by: Maria Rubtsova<EMAIL_ADDRESS>
What do these changes do?

[ ] commit message follows format outlined here
[ ] passes flake8 modin
[ ] passes black --check modin
[ ] signed commit with git commit -s
[ ] Resolves #2164 ?
[ ] tests added and passing
[ ] module layout described at docs/developer/architecture.rst is up-to-date

OmniSci query compiler also imports base _get_axis and uses it in its own axis-getter functions [1] [2] to default to pandas when it's operating with unsupported data (with the changes in this branch default-to-pandas behaviour is identical to the regular OmniSci _get_index/columns flow).
OmniSci backend tests of working with unsupported data located at the TestBadData class, at the moment it doesn't have explicit tests for df.index and df.columns, they should be added in order to check whether the changes in base._get_axis has no effect on the OmniSci backend. If these tests will be green, then this special-casing in _get_index and _get_columns should be removed

Also, to add to my review above - why are we adding some special corner-case handling in the tests instead of fixing the bugs which make those test fail?..

@vnlitvinov We adding some special corner-case because this problem will be solved with future version pandas. Just now default Series in Pandas is float64, but in Modin - object. More details in this issue - https://github.com/modin-project/modin/issues/3142

@dchigarev I added tests in modin/experimental/engines/omnisci_on_ray/test/test_dataframe.py and they pass.

@dchigarev I added tests in modin/experimental/engines/omnisci_on_ray/test/test_dataframe.py and they pass.

That means that this special casing at _get_index and _get_columns was redundant and so can be safely removed. Even more, now we can completely remove these methods. They only used as the getters of the index and columns properties, I believe we can replace _get_index/_get_columns -> get_axis(0/1) here.

As described here https://github.com/modin-project/modin/pull/3141#discussion_r662146492, the root cause is bug in PandasFrame.to_pandas method. It affected all engines (reproducer is below, tested on Ray engine):
import modin.pandas as pd
import pandas

ser = pd.Series()
index = pandas.date_range(
    "1/1/2000", periods=len(ser.index), freq="T"
)
ser.index = index

print(f'Index: {ser.index}')
print(f'Index after to_pandas: {ser._query_compiler.to_pandas().index}')

Output
Index: DatetimeIndex([], dtype='datetime64[ns]', freq='T')
Index after to_pandas: Index([], dtype='object')

Output after Maria's fix:
Index: DatetimeIndex([], dtype='datetime64[ns]', freq='T')
Index after to_pandas: DatetimeIndex([], dtype='datetime64[ns]', freq='T')

Possible, need to add testing of such cases.

I was mostly wondering why we dropped the index for non-empty columns in an empty dataframe... there has to be a reason. :)
Also, adding this

Output after Maria's fix:
Index: DatetimeIndex([], dtype='datetime64[ns]', freq='T')
Index after to_pandas: DatetimeIndex([], dtype='datetime64[ns]', freq='T')

as a test would be a great addition to this PR 😄

Why did we solve not to add test described here https://github.com/modin-project/modin/pull/3141#issuecomment-872258328?

@prutskov , good notice! Please, add this one-line change in a separate PR.


Turn off Open babel for python 3.6 until its fixed

Matching issues is openbabel/openbabel#372. I'm keeping an eye on it.

This correctly deals with the OpenBabel problem for now. We can rebuild this once the bug is fixed


Game prints 'Stage specified' even if no stage was specified.

The console print is incorrect and that is annoying when debugging.
"Kiwi.Game: Stage specified, but is not a valid option. Set to NONE." is printed even if no stage is specified. It should print, "Kiwi.Game: Stage scaling not specified, defaulting to NONE." and "Kiwi.Game: Stage scaling specified, but {value} is not a valid option. Set to NONE." as error text.

@RaniSputnik Updated it in the latest version thanks!
Turns out it was due to an incorrect conditional which always evaluated to true. Doh


Boot Failure am335x_evm.sh (20200303 BeagleBone Blue)

Device: BeagleBone Blue | TI_*_RoboticsCape
Patch: https://github.com/RobertCNelson/boot-scripts/pull/111/commits/998da50b049777995720cd1f0cc123494e77647c

Fixed pushed.
cd /opt/scripts/
git pull


Intelligente drievoudige warmtepomp

Intelligent Heat Pump
devices.json
snapshot.json

Thanks for the JSON! Found small bug and added the devices mentioned ad the Cloud plugin.


Send static item to root menu

How would I move a static item out of its menu and into the "root" menu?
item(type="*" find="Edit with IDLE 3.*" parent=????????)

Moving child items to the parent level is not supported yet.


Add adding components

It's done or draft?

It's done or draft?

Oh, no. It's still under development


run the command: ros2 run micro_ros_setup build_agent.sh failed

Issue template

Hardware description:  vmware Ubuntu20.04
RTOS: arduino_esp32
Installation type:  micro_ros_setup
Version or commit hash:  version of micro-ROS used: foxy

Steps to reproduce the issue

Sorry for my poor English!
I followed the install tutorial for the micro_ros setup. https://manzurmurshid.medium.com/how-to-connect-teensy-3-2-with-micro-ros-and-ros2-foxy-6c8f99c9b66a and https://github.com/micro-ROS/micro_ros_setup/tree/foxy
All commands were performed perfect until this command:  ros2 run micro_ros_setup build_agent.sh
The terminal output as below:

Expected behavior
Actual behavior
Additional information

Could you provide instructions for replicating this issue?

Just tested it and on a fresh ros:foxy docker and its working, Are you using a ros:foxy docker or how did you install ROS?
Could you also share your output for apt list --installed | grep fastrtps?

I tested it on a fresh ros:foxy docker and it works!
But I'm still curious why it is not work in my ubuntu20.04...
The output for apt list --installed | grep fastrtps as below.


pull-secret is double-quoted

The Convert pullsecret to JSON in ansible-ipi-install/roles/set-deployment-fact/tasks.main cause the pull secret defined as
pullsecret: '{"auths": ... }'

to end up with one extra layer of quoting, failing the playbook when the pull-secret file is used on the provisioner.

Please use pullsecret as is - without any quotes @rvansa and let me know how it goes

@smalleni I have installed OCP now (disabling the conversion) but I perceive the pull-secret as an opaque string, therefore pasting it as such. Putting the JSON straight into YAML seems awkward.
Maybe a check if the pullsecret is string or object would satisfy any use case.

Ack. I think we had to make that change with something related to exporting these group_vars/all.yml as environment variables for tools like jenkins. We used to require a '' before that?
I like your idea, do you mind sending a PR?

Created https://github.com/redhat-performance/JetSki/pull/174


dubbo server,don't show Icon！

we build service with virtual ip on the same linux server.different service use different ip.but the agent    send host ip to collector,and the dubbo provider send the virtual ip to collector.may be this cause the dubbo server icon don't show.
the code is :
agent send:
  final InetAddress thisIp = InetAddress.getLocalHost();    hostIp = thisIp.getHostAddress();
dubbo provider send:
  String host = localAddress == null ? null :              localAddress.getAddress() == null ? localAddress.getHostName()                      : NetUtils.filterLocalHost(localAddress.getAddress().getHostAddress());         if (host == null || host.length() == 0) {             return NetUtils.getLocalHost();         }

#5879 Dubbo plugin is missing the remote address
It seems to be related to the above issue.
This problem is fixed in 1.8.5 and 1.9.0.

@emeroad hi,don't like this.i have remote address.i here ,it don't show icon.the virtual ip isn't same the hostip.
i use 1.8.4,i see the code like has modified.

the remote address of #5876 means Pinpoint-Host header.
Include the caller address in the trace header(Pinpoint~~) because it cannot be mapped to the IP where a proxy exists, such as L4.
The problem has been fixed in 1.8.5, so test with 1.8.5.

@emeroad ok,i wait 1.8.5 release.


Implement the fx-var element. VARIABLES!!!

This brings variables!
By traversing over the DOM at an early point we get hold of all the variable elements. These are
given to all the 'normal' UI components in a way that they only have access to the preceding
variables. Variables are updated on refresh.
TODO

Unit tests!
The behaviour for actions
More examples

Making a draft PR already to show off the progress. Don't integrate yet please

ah cool - like it. we should maybe add some cases to the demo like using it in model
<fx-var name="foo" value='my_very_long_XPath'>
<fx-var name="bar" value='another_very_long_XPath'>

<fx-bind ref="$foo" required="$bar">

I updated this PR with some unit tests for variables. It's ready to review. Don;t hesitate to reach out if you have any questions!

that looks very good to me - however we're missing a test for the use of fx-var inside of an action block - maybe even looped one. Code looks like it could work but testcase would be better ;)

Hey there! I just added a few tests for exactly that. Turns out I made a few small mistakes earlier, but all's well now!

@DrRataplan hurrah! what a step forward. Will merge asap


.rules[0].logging: block count changed from 0 to 1.

Confirmation

[X] This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
[X] I have searched the issue tracker and my issue isn't already found.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
latest 4.44.0
Affected resource(s)
cloudflare_ruleset
Terraform configuration files
resource "cloudflare_ruleset" "zone_custom_firewall_rules" {
  zone_id     = data.cloudflare_zone.zone_id.id
  name        = "tf-mid-global-custom-firewall-rules"
  description = "tf-mid-global-custom-firewall-rules"
  kind        = "zone"
  phase       = "http_request_firewall_custom"

  dynamic "rules" {
    for_each = var.AUTH_HEADERS_EXEMPTION
    iterator = prod_auth_header_rules
    content {
      action = "skip"
      action_parameters {
        phases = ["http_ratelimit"]
      }
      expression  = replace(local.exempt_auth_header_expression, "{AUTH_HEADER}", prod_auth_header_rules.value)
      description = "tf-mid-skip-auth-header-${prod_auth_header_rules.key}"

    }
  }
}

Link to debug output
https://gist.github.com/VarshneyPrince/0796ef47344fd97e955da36b860e400d
Panic output
Error: Provider produced inconsistent result after apply
When applying changes to module.cloudflare-rules-module.cloudflare_ruleset.zone_custom_firewall_rules, provider "module.cloudflare-rules-module.provider["registry.terraform.io/cloudflare/cloudflare"]" produced an unexpected new value: .rules[0].logging: block count changed from 0 to 1.
This is a bug in the provider, which should be reported in the provider's own issue tracker.
Expected output
Resource gets created without any error.
Actual output
Resource gets created but with error.
Error: Provider produced inconsistent result after apply
When applying changes to module.cloudflare-rules-module.cloudflare_ruleset.zone_custom_firewall_rules, provider "module.cloudflare-rules-module.provider["registry.terraform.io/cloudflare/cloudflare"]" produced an unexpected new value: .rules[0].logging: block count changed from 0 to 1.
This is a bug in the provider, which should be reported in the provider's own issue tracker.
Steps to reproduce

Add this cloudflare_ruleset resource
Add multiple dynamic firewall rules
tf apply

Additional factoids
No response
References
No response

Already added the information there.

I have the same issue

Here it is simple configuration for clean CF zone WAF setup:
% ls
main.tf

% cat main.tf
terraform {
  required_providers {
    cloudflare = {
      source  = "registry.terraform.io/cloudflare/cloudflare"
      version = "4.45.0"
    }
  }

  backend "http" {

  }
}

provider "cloudflare" {
  api_token = "API-TOKEN"
}

resource "cloudflare_ruleset" "custom_rules_builder" {
  name = "Custom rules"
  kind = "zone"
  description = "Zone custom rules created by Terraform"
  zone_id = "ZONE-ID"
  phase = "http_request_firewall_custom"

  rules {
    expression  = "(cf.bot_management.verified_bot)"
    description = "Verified Bots"
    action      = "skip"
    action_parameters {
      ruleset  = "current"
    }
  }
}

% terraform apply
cloudflare_ruleset.custom_rules_builder: Refreshing state... [id=ID-HIDEN]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with
the following symbols:
  + create

Terraform will perform the following actions:

  # cloudflare_ruleset.custom_rules_builder will be created
  + resource "cloudflare_ruleset" "custom_rules_builder" {
      + description = "Zone custom rules created by Terraform"
      + id          = (known after apply)
      + kind        = "zone"
      + name        = "Custom rules"
      + phase       = "http_request_firewall_custom"
      + zone_id     = "ZONE-ID"

      + rules {
          + action       = "skip"
          + description  = "Verified Bots"
          + enabled      = true
          + expression   = "(cf.bot_management.verified_bot)"
          + id           = (known after apply)
          + last_updated = (known after apply)
          + ref          = (known after apply)
          + version      = (known after apply)

          + action_parameters {
              + ruleset = "current"
              + version = (known after apply)
            }
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

cloudflare_ruleset.custom_rules_builder: Creating...
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to cloudflare_ruleset.custom_rules_builder, provider
│ "provider[\"registry.terraform.io/cloudflare/cloudflare\"]" produced an unexpected new value: .rules[0].logging:
│ block count changed from 0 to 1.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

any workarounds to this issue? v4.47 is still encountering the same error when adding new rules.

the logging field is only optional in the sense of the schema constraints. the service returns the logging value so you will need to provide it as part of your configuration - https://developers.cloudflare.com/waf/custom-rules/skip/api-examples/#skip-a-phase-and-do-not-log-matching-requests

Would it be possible to get this added to the documentation somehow? I just came across the same issue and was left utterly confused as there is no mention of the logging configuration being required.
It being returned by the API response feels more like an implementation detail which I'd expect the Terraform provider would take care of or would there would be a note that it's required in certain circumstances (with some examples of when).


MPV always opens with Anime4K enabled.

Describe the bug
Title, I deleted all my scripts to see if the source of the error originated from one of them but it happened nonetheless.
Expected behavior
Opens without automatically enabled.
Desktop (please complete the following information):

OS: [e.g. Windows 11 Enterprise]
Version [22H2]
GPU/Version (RTX 3060 Laptop GPU]
Media Player and Version [MPV v0.36]

This is due to the mpv.conf template file in your config folder. You can disable it by deleting the file or removing the glsl line from your mpv config file.

Mode A is automatically enabled, if you use our template (this can be change in mpv.conf).

You can disable it by deleting the file or removing the glsl line from your mpv config file.

How do I choose which one it starts with? I would like it to use A + A (HQ) by default, I always have to switch


Build apprtc build_apprtc failed (Ubuntu 14.04)

After main setting ...
Source all the routines
source android/build.sh
Install any dependencies needed
install_dependencies
Pull WebRTC
get_webrtc
Have problem when - Building the libraries on building apprtc:
terminal closed with error that cann't  find some directory.
Using revision:  633c9f1.

Same problem, like in other issues:https://github.com/pristineio/webrtc-build-scripts/issues/162

First problem was like other issues https://github.com/pristineio/webrtc-build-scripts/issues/162After manually adding that files to directory  - process go on. But

Full error message in link issues #162  said, that script cann't find some google_play_service folders. Fixed by manually adding all files from my sdk to that folder.


Use Dashy Dashboard in place of Hajimari

I have personally chosen to use Dashy Dashboard as my landing page. I see that Hajimari utilizes helm and that replaced the initial use of Homer. So it is possible to use another landing page with the right know-how.
Dashy:
https://github.com/Lissy93/dashy
This looks like it would be what we need to utilize:
https://github.com/Lissy93/dashy/discussions/45#discussioncomment-897961
Describe the solution you'd like:
Provide optional install of Dashy Dashboard vs Hajimari
Anything else you would like to add:
I have not come across anything Helm related for Dashy. I'm not sure if that is a dealbreaker.
Additional Information:
Switch from homer to hajimari:
https://github.com/vladzaharia/template-cluster-k3s/commit/201e8eca43ad9458e8e2fa03815340cdac13c379
Initial implementation of homer:
https://github.com/k8s-at-home/flux-cluster-template/commit/3501d5a9ed789f022a4f77df7ec8d537e5d3a6a1

Hajimari works with the Kubernetes API to auto create the dashboard from ingress annotations. You are free to use whatever you like and expand your cluster in anyway you see fit but I'll not be switching this out, sorry.


Feature Request: Restricting server-side access

Hi,
sorry if it's a naive request, but... would it be possible to have a (default, even) URL blacklist for what can be accessed using browservice?
To be more concrete, I would like to

restrict access to my local subnet (OK, this can be done with iptables etc. - maybe not as important)
restrict access to the file:// protocol (more important if you can't afford a single server/VM/container for this service alone)

I get the hint from the documentation - trust between client and browservice needs to be mutual - and I keep this in mind when running it. If it's possible to achieve restrictions (especially forbid file:// access) with chrome-sandbox, I would still welcome it!

less paranoia with existing setups and workarounds (dedicated user, docker containers etc.)
possibly even giving a browservice URL to friends on the same LAN
or God forbid, even on the Internet behind a reverse proxy

Ok, the last one will probably always be a bad idea! :-) But is there something that can be done code-side to increase browservice's inherent security?
Are there workarounds (against file access) that I'm not aware of, that may be documented?
Kind regards
Wolf

URL blacklist is definitely doable; in this thread the creator of CEF (magreenblatt) says that it could be done in an OnBeforeBrowse handler. However, I am not sure it is sufficient; Chromium is full of features, and some of them could still be used to gain access to the files on the local computer. It would require a very extensive knowledge of the browser (which I don't have) to have some certainty that a set of restrictions is sufficient. While adding URL filters to Browservice is technically possible (and probably quite easy to do; you can of course try it), I probably don't want to do that, as it give a false sense of security and steer users towards unsafe setups.
Thus, I recommend keeping the simple security model: the only people you should allow to connect to a Browservice instance are those people who you would allow to operate a normal web browser in the user account running Browservice. The design of Browservice is not really well suited for multi-user setups; for example, the browser cookies and clipboard is shared between all the browser windows. Thus I would still recommend having separate instances run as separate users/VMs/LXC containers. I think these kinds of robust barriers should give you less paranoia than sharing a browser between multiple users.
Out of curiosity: What does it mean that you can't afford a container for this service? At least LXC/LXD containers are typically very lightweight. In my RasPi 4 setup, I run Browservice in an LXC container.

URL blacklist is definitely doable; in this thread the creator of CEF (magreenblatt) says that it could be done in an OnBeforeBrowse handler. However, I am not sure it is sufficient; Chromium is full of features, and some of them could still be used to gain access to the files on the local computer. It would require a very extensive knowledge of the browser (which I don't have) to have some certainty that a set of restrictions is sufficient. While adding URL filters to Browservice is technically possible (and probably quite easy to do; you can of course try it), I probably don't want to do that, as it give a false sense of security and steer users towards unsafe setups.
Thus, I recommend keeping the simple security model: the only people you should allow to connect to a Browservice instance are those people who you would allow to operate a normal web browser in the user account running Browservice. The design of Browservice is not really well suited for multi-user setups; for example, the browser cookies and clipboard is shared between all the browser windows. Thus I would still recommend having separate instances run as separate users/VMs/LXC containers. I think these kinds of robust barriers should give you less paranoia than sharing a browser between multiple users.
Out of curiosity: What does it mean that you can't afford a container for this service? At least LXC/LXD containers are typically very lightweight. In my RasPi 4 setup, I run Browservice in an LXC container.

Closing due to lack of activity; please create a new issue if you want to continue on this topic.


Click on ".." folder in Godot editor FileSystem dock does not indicate if the folder is clicked.

Godot version:
Stable 3.0
OS/device including version:
Linux Mint 18.3 Cinnamon 3.6.7 64-bit
4.13.0-21-generic
Issue description:
In the Godot editor, clicking on the ".." folder in a subfolder does not highlight the folder, meaning you cannot tell if you clicked on it. In the second screenshot, the ball icon is clickable, but not the folder next to it:

Steps to reproduce:

From the Godot editor, descend into a subfolder from the filesystem dock.
Click on the ".." folder.

@guilhermefelipecgs I would consider behaviour that breaks the user's expectations, being that every folder in the dock would be selectable, as a bug and not a feature.

I agree, I put this reference just to remind those who will work on it that the change may cause some errors that need to be fixed.


CSS imports in layouts persist, even if layouts do not

This problem occurs in the preset:
npx @preset/cli apply laravel:inertia
When I use <inertia-link> to navigate to a new vue component, which happens to be assigned to a new layout template, the CSS of the old components layout template persists in the properties of the new component, if the css is imported with @import statement in the layout. The old CSS, which should be removed, can be observed in the browser dev tools.
This applies only to the imported CSS, not to the CSS written directly to the layouts. The layout's HTML behaves as usual.
One example of this happening is when I switch between frontend and backend of my app, which have different css files imported.

@innocenzi Hey, I've closed it because I couldn't replicate for a moment but now I managed to replicate. May I just ask about layouts and inertia? Are layouts an integral part of inertia.js or do they belong to your setup?

Sure, persistent layouts are a thing in Inertia: https://inertiajs.com/pages#persistent-layouts
My initial setup doesn't provide an easy way to use them though. You can check out the Inertia Discord server, where you can ask such questions. Additionally I've just answered one with a snippet for persistent layouts too: invitation, snippet link.
Regarding your CSS issue, it most likely belongs in the Vite serveur in #help. :)


hotfix for calendar_spec.js (used data now returns 20 events)

fixes #3532

@sdetweil can you please merge (or at least approve) this because @rejas is unresponsive?

merged, i could not approve


Can't generate the Lexer.java  when I flow the TagTokenizer.java's comment

I flow the common ,use mvn jflex:generate under the folder sitmesh, maven tell me it's success, but where is
my Lexer.java

you can found it

Use Gradle instead.
Don't execute a clean and jar command simultaneously (e.g. ./gradlew clean jar will not work).  If you need to run clean, do it separately

./gradlew clean
./gradlew jar


Deprecate the TC dispatcher in favor of the new TCX link type

The new TXC feature will allow users to more easily control the priority between various TC programs, and is now part of the mainstream kernel.  We should hop on this bandwagon and use the TCX infrastructure to maintain priority ordering between TC programs we maintain rather than maintaining a custom dispatcher.
This will require us to add TCX support to aya first! (see https://github.com/cilium/ebpf/issues/1117 for an example)

Is this what we want, or do we want to continue to support both TC and TCX?

We will continue to support both TC and TCX.


Simple kernels for Det1D and Values1D

These are needed for some 1D Remhos runs.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#2843
@vladotomov
@tzanio
@tzanio + @camierjs
2/18/22
⌛due 3/4/22
⌛due 3/11/22

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Merged in next for testing...


PyTorch exceptions when running train.py or test.py

Hello,
Thank you for maintaining this project. I am trying out the test.py and train.py scripts with the kitti dataset from NVIDIA Jetson AGX Xavier and running into an error I am having trouble resolving. Shortly after I get to these log lines, an exception is thrown:
2021-06-07 22:59:42,230   INFO  **********************Start training kitti_models/CaDDN(default)**********************
epochs:   0%|                                                                                | 0/80 [00:02<?, ?it/s]

This is the command: python train.py --cfg_file cfgs/kitti_models/CaDDN.yaml --batch_size 2
That exception is this:
Traceback (most recent call last):                                                                              | 0/1856 [00:00<?, ?it/s]
  File "train.py", line 198, in <module>
    main()
  File "train.py", line 170, in main
    merge_all_iters_to_one_epoch=args.merge_all_iters_to_one_epoch
  File "/home/dpwolfe/repo/CaDDN/tools/train_utils/train_utils.py", line 93, in train_model
    dataloader_iter=dataloader_iter
  File "/home/dpwolfe/repo/CaDDN/tools/train_utils/train_utils.py", line 19, in train_one_epoch
    batch = next(dataloader_iter)
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 363, in __next__
    data = self._next_data()
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 989, in _next_data
    return self._process_data(data)
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 1014, in _process_data
    data.reraise()
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/torch/_utils.py", line 395, in reraise
    raise self.exc_type(msg)
KeyError: Caught KeyError in DataLoader worker process 0.
Original Traceback (most recent call last):
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/torch/utils/data/_utils/worker.py", line 185, in _worker_loop
    data = fetcher.fetch(index)
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/torch/utils/data/_utils/fetch.py", line 44, in fetch
    data = [self.dataset[idx] for idx in possibly_batched_index]
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/torch/utils/data/_utils/fetch.py", line 44, in <listcomp>
    data = [self.dataset[idx] for idx in possibly_batched_index]
  File "/home/dpwolfe/repo/OpenPCDet/pcdet/datasets/kitti/kitti_dataset.py", line 424, in __getitem__
    data_dict = self.prepare_data(data_dict=input_dict)
  File "/home/dpwolfe/repo/OpenPCDet/pcdet/datasets/dataset.py", line 129, in prepare_data
    'gt_boxes_mask': gt_boxes_mask
  File "/home/dpwolfe/repo/OpenPCDet/pcdet/datasets/augmentor/data_augmentor.py", line 112, in forward
    data_dict = cur_augmentor(data_dict=data_dict)
  File "/home/dpwolfe/repo/OpenPCDet/pcdet/datasets/augmentor/data_augmentor.py", line 84, in random_image_flip
    images = data_dict["images"]
KeyError: 'images'

While going through the setup process, I've needed to use some slightly different versions of dependencies declared in the requirements file. I've done this to use available pre-built versions for aarch64 and avoid having to build them myself. Those are:
numpy 1.19.5 instead of 1.20.1
scikit-image 0.18.0rc1 instead of 0.18.1
scipy 1.5.4 instead of 1.6.1
tifffile 2020.9.3 instead of 2021.2.26
I've also needed to make a couple major version changes that I'm concerned might be the problem:
kornia 0.5.3 instead of 0.2.2 since 0.2.2 was not readily available for aarch64
torch 1.6.0 since kornia 0.5.3 requires >= 1.6.0
Hardware and Environment:
NVIDIA Jetson AGX Xavier
Jetpack 4.5  (Ubuntu 18.04)
Python 3.6 (using miniforge)
CUDA Version: 10.2
My conda list output
# packages in environment at /home/dpwolfe/miniforge3/envs/open-pcdet:
#
# Name                    Version                   Build  Channel
_openmp_mutex             4.5                       1_gnu    conda-forge
absl-py                   0.12.0                   pypi_0    pypi
ca-certificates           2018.03.07                    0    c4aarch64
cachetools                4.2.1                    pypi_0    pypi
certifi                   2020.12.5                pypi_0    pypi
chardet                   4.0.0                    pypi_0    pypi
cycler                    0.10.0                   pypi_0    pypi
dataclasses               0.8                      pypi_0    pypi
decorator                 4.4.2                    pypi_0    pypi
easydict                  1.9                      pypi_0    pypi
future                    0.18.2                   pypi_0    pypi
google-auth               1.27.1                   pypi_0    pypi
google-auth-oauthlib      0.4.3                    pypi_0    pypi
grpcio                    1.36.1                   pypi_0    pypi
idna                      2.10                     pypi_0    pypi
imageio                   2.9.0                    pypi_0    pypi
importlib-metadata        4.5.0                    pypi_0    pypi
kiwisolver                1.3.1                    pypi_0    pypi
kornia                    0.5.3                    pypi_0    pypi
ld_impl_linux-aarch64     2.35.1               h02ad14f_2    conda-forge
libblas                   3.8.0               17_openblas    conda-forge
libcblas                  3.8.0               17_openblas    conda-forge
libffi                    3.3                  h884eca8_2    conda-forge
libgcc-ng                 9.3.0               he1ea209_19    conda-forge
libgfortran-ng            7.3.0                h6bc79d0_0    c4aarch64
libgomp                   9.3.0               he1ea209_19    conda-forge
liblapack                 3.8.0               17_openblas    conda-forge
libllvm10                 10.0.1               he513fc3_3    conda-forge
libllvm12                 12.0.0               h6293a0b_1    conda-forge
libopenblas               0.3.10          pthreads_hb3c22a3_4    conda-forge
libstdcxx-ng              9.3.0               h1ed1776_19    conda-forge
llvm-tools                12.0.0               h6293a0b_1    conda-forge
llvmdev                   12.0.0               h6293a0b_1    conda-forge
llvmlite                  0.35.0           py36h2826d25_1    conda-forge
markdown                  3.3.4                    pypi_0    pypi
matplotlib                3.3.4                    pypi_0    pypi
ncurses                   6.2                  h7fd3ca4_4    conda-forge
networkx                  2.5                      pypi_0    pypi
numba                     0.52.0           py36ha63b481_0    conda-forge
numpy                     1.19.5           py36hdc1b780_1    conda-forge
oauthlib                  3.1.0                    pypi_0    pypi
openssl                   1.1.1k               hf897c2e_0    conda-forge
pcdet                     0.3.0+150b7ba             dev_0    <develop>
pillow                    8.1.2                    pypi_0    pypi
pip                       21.1.2             pyhd8ed1ab_0    conda-forge
protobuf                  3.15.3                   pypi_0    pypi
pyasn1                    0.4.8                    pypi_0    pypi
pyasn1-modules            0.2.8                    pypi_0    pypi
pyparsing                 2.4.7                    pypi_0    pypi
python                    3.6.13          h468538b_0_cpython    conda-forge
python-dateutil           2.8.1                    pypi_0    pypi
python_abi                3.6                     1_cp36m    conda-forge
pywavelets                1.1.1                    pypi_0    pypi
pyyaml                    5.4.1                    pypi_0    pypi
readline                  8.1                  h1a49cc3_0    conda-forge
requests                  2.25.1                   pypi_0    pypi
requests-oauthlib         1.3.0                    pypi_0    pypi
rsa                       4.7.2                    pypi_0    pypi
scikit-image              0.18.0rc1                pypi_0    pypi
scipy                     1.5.4                    pypi_0    pypi
setuptools                49.6.0           py36h704843e_3    conda-forge
six                       1.15.0                   pypi_0    pypi
spconv                    1.2.1                    pypi_0    pypi
sqlite                    3.35.5               h43e6a2a_0    conda-forge
tensorboard               2.4.1                    pypi_0    pypi
tensorboard-plugin-wit    1.8.0                    pypi_0    pypi
tensorboardx              2.1                      pypi_0    pypi
tifffile                  2020.9.3                 pypi_0    pypi
tk                        8.6.10               ha99a2a3_1    conda-forge
torch                     1.6.0                    pypi_0    pypi
torchvision               0.9.1                    pypi_0    pypi
tqdm                      4.58.0                   pypi_0    pypi
typing-extensions         <IP_ADDRESS>                  pypi_0    pypi
urllib3                   1.26.3                   pypi_0    pypi
werkzeug                  1.0.1                    pypi_0    pypi
wheel                     0.36.2             pyhd3deb0d_0    conda-forge
xz                        5.2.5                h6dd45c4_1    conda-forge
yolk3k                    0.9                      pypi_0    pypi
zipp                      3.4.1                    pypi_0    pypi
zlib                      1.2.11               h7b6447c_2    c4aarch64

Also, if I run python test.py --cfg_file cfgs/kitti_models/CaDDN.yaml --batch_size 2 --ckpt ../checkpoints/caddn.pth I will get the following:
2021-06-07 23:16:09,131   INFO  Loading KITTI dataset
2021-06-07 23:16:09,576   INFO  Total samples for KITTI dataset: 3769
2021-06-07 23:16:13,328   INFO  ==> Loading parameters from checkpoint ../checkpoints/caddn.pth to GPU
2021-06-07 23:16:16,395   INFO  ==> Checkpoint trained from version: pcdet+0.3.0+0000000
2021-06-07 23:16:18,141   INFO  ==> Done (loaded 229/229)
2021-06-07 23:16:18,239   INFO  *************** EPOCH no_number EVALUATION *****************
eval:   0%|                                                                                | 0/1885 [00:00<?, ?it/s]

Followed by this error:
Traceback (most recent call last):
  File "test.py", line 199, in <module>
    main()
  File "test.py", line 195, in main
    eval_single_ckpt(model, test_loader, args, eval_output_dir, logger, epoch_id, dist_test=dist_test)
  File "test.py", line 63, in eval_single_ckpt
    result_dir=eval_output_dir, save_to_file=args.save_to_file
  File "/home/dpwolfe/repo/CaDDN/tools/eval_utils/eval_utils.py", line 57, in eval_one_epoch
    pred_dicts, ret_dict = model(batch_dict)
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/dpwolfe/repo/OpenPCDet/pcdet/models/detectors/caddn.py", line 11, in forward
    batch_dict = cur_module(batch_dict)
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/dpwolfe/repo/OpenPCDet/pcdet/models/backbones_2d/map_to_bev/conv2d_collapse.py", line 34, in forward
    voxel_features = batch_dict["voxel_features"]
KeyError: 'voxel_features'
Exception ignored in: <bound method tqdm.__del__ of <tqdm.std.tqdm object at 0x7f849ebb70>>
Traceback (most recent call last):
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/tqdm/std.py", line 1143, in __del__
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/tqdm/std.py", line 1297, in close
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/tqdm/std.py", line 1490, in display
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/tqdm/std.py", line 1146, in __str__
  File "/home/dpwolfe/miniforge3/envs/open-pcdet/lib/python3.6/site-packages/tqdm/std.py", line 1448, in format_dict
TypeError: 'NoneType' object is not iterable

Have you seen these errors before or do you know if they're caused by the change in one of the dependencies, such as pytorch 1.6.0 instead of 1.4.0?
I greatly appreciate your help. The next path for me otherwise is to unwind my setup and rebuild it with torch 1.4.0 (NVIDIA provides it) since the exception originates from torch. I'll also have to see if I can build kornia 0.2.2 for aarch64.
Thank you!

Hello!
If you look at your error log you can actually see the issue
File "/home/dpwolfe/repo/OpenPCDet/pcdet/datasets/augmentor/data_augmentor.py", line 84, in random_image_flip

It looks like your environment is using the source code from OpenPCDet rather than CaDDN, which currently are slightly different (Currently working on updating this repo to be in line with OpenPCDet.) It might be that you are using the same conda environment for both, and you installed OpenPCDet more recently so this code is being used.
If you are already using the OpenPCDet repo, my recommendation is to stick with the CaDDN implementation over there. However, if you only require CaDDN then I would recommend to use this source code here and just ensure that these are in separate virtual environments.

Thank you again @codyreading! This worked great along with the path mentioned in #23.


Install different opencv version for arm devices

Fixes broken requirements for ARM devices (rpi2/3/zero)

Thanks.
Will test calibration script using this on Rpi and get back.

Merged, otherwise can't be used on RPIs.


Disable content_set check in ocp4/rebuild jobs

The certificate has expired. Temporarily disable it to unblock build. The check will likely be moved to the validator.
Please enter the commit message for your changes. Lines starting

/lgtm


Wrap the crane command to make it easier to use with Zarf

Description
This wraps the crane command so that it is easier to use more directly with Zarf
Related Issue
Fixes #1186
Type of change

[X] New feature (non-breaking change which adds functionality)

Checklist before merging

[X] Documentation has been updated as necessary (add the needs-docs label)

This is a great short-term add, I was actually thinking maybe we should just add a more top-level command to interact with artifacts/assets zarf deploys.  Something like zarf artifact images orzarf assets images. I think it should probably be view-only since mutation would break the nature of declarative packages. Also zarf artifact repos. Thoughts?

I think that could make sense, though we would likely need to pull that info from the zarf state instead of the actual service.  Doing that for git repos might get tricky across git hosts.

There's a lint error in tools.go. Also, since we're adding custom logic outside of just crane, we should add a test for this. Fortunately we also need this function in the src/test/e2e/21_connect_test.go test, so might be able to just drop it in there.

Fixed


(MODULES-2185) Fix withenv execution under Puppet 2.7

When executing a command with environment variables, the withenv helper
under Puppet 2.7 is on Puppet::Util::Execution and on 3.0 to 3.3, it's
on Puppet::Util.

@domcleal thanks for the contribution, but can this please be targeted against master? If we end up doing another 4.4.x release we'll pull it over, but likely the next release will be something else.

@mhaskel thanks, if you're doing another 4.4.x, it'd be much appreciated since it's a regression.  I've opened #664 against master to replace this PR.


Wear and Remove

The commands which DON and REMOVE clothing cause problems.
I have altered the script for each, and this seems to be a dirty fix (for now).
  <command name="wear">
    <pattern>put #object# on; wear #object#; put on #object#; don #object#; wear #object#</pattern>
    <scope>inventory</scope>
    <multipleobjects type="script">
      game.pov.currentcommandpendingobjectscope = ScopeInventory()
    </multipleobjects>
    <script>
      if (TypeOf(multiple) = "undefined") {
        multiple = false
      }
      if (multiple and ListCount(object) = 0) {
        msg ("You've nothing to wear.")
      }
      else {
        foreach (obj, object) {
          f = _DoWear(obj)
        }
        UpdateArmour
      }
    </script>
  </command>

  <command name="remove">
    <pattern>take #object# off; remove #object#; take off #object#; doff #object#</pattern>
    <scope>inventory</scope>
    <multipleobjects type="script">
      game.pov.currentcommandpendingobjectscope = ScopeInventory()
    </multipleobjects>
    <script>
      if (TypeOf(multiple) = "undefined") {
        multiple = false
      }
      if (multiple and ListCount(object) = 0) {
        msg ("You've nothing to take off.")
      }
      else {
        foreach (obj, object) {
          f = _DoRemove(obj)
        }
      }
      UpdateArmour
    </script>
  </command>

I was being extra silly!
Adding var multiple = false to the game.js in the source code seems to fix TAKE, DROP, WEAR, and REMOVE for all versions of Quest.


Update Orange3 to 3.36.2

orange3 3.36.2
Destination channel: {defaults}
Links

PKG-4174
Upstream repository
Relevant dependency PRs:

url-normalize > requests-cache > orange-canvas-core > orange-widget-base > orange3
xgboost > orange3

Explanation of changes:

Updated version and hash
Updated dependencies
Added patch to replace imp module with importlib
Updated redirecting urls
Added pip check
Added abs.yaml to be removed PRIOR to merge

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_8emnl3jncp/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:62: python_build_tool_in_run: The python build tool pip is in run depends
clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:73: python_build_tool_in_run: The python build tool setuptools is in run depends

===== ERRORS =====

clone/recipe/meta.yaml:0: missing_tests: No tests were found.
clone/recipe/meta.yaml:1: missing_pip_check: For pypi packages, pip check should be present in the test commands
clone/recipe/meta.yaml:1: missing_imports_or_run_test_py: Python packages require imports or a python test file in tests.
===== Final Report: =====
3 Errors and 5 Warnings were found

Since this is a GUI application, have you tested basic functionality when running on osx, windows or linux?

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_12e4vz3zth/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:73: python_build_tool_in_run: The python build tool setuptools is in run depends
clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:62: python_build_tool_in_run: The python build tool pip is in run depends

===== ERRORS =====

clone/recipe/meta.yaml:1: missing_imports_or_run_test_py: Python packages require imports or a python test file in tests.
clone/recipe/meta.yaml:0: missing_tests: No tests were found.
clone/recipe/meta.yaml:1: missing_pip_check: For pypi packages, pip check should be present in the test commands
===== Final Report: =====
3 Errors and 5 Warnings were found

Since this is a GUI application, have you tested basic functionality when running on osx, windows or linux?

I have successfully tested that basic functionality to launch works via terminal with orange-canvas command and the tile and functionality works via Anaconda Navigator as well. 😄

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_973wg37mxx/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:73: python_build_tool_in_run: The python build tool setuptools is in run depends
clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:62: python_build_tool_in_run: The python build tool pip is in run depends

===== ERRORS =====

clone/recipe/meta.yaml:0: missing_tests: No tests were found.
clone/recipe/meta.yaml:1: missing_imports_or_run_test_py: Python packages require imports or a python test file in tests.
clone/recipe/meta.yaml:1: missing_pip_check: For pypi packages, pip check should be present in the test commands
===== Final Report: =====
3 Errors and 5 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_7e3ibx2qm3/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:62: python_build_tool_in_run: The python build tool pip is in run depends
clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:73: python_build_tool_in_run: The python build tool setuptools is in run depends
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:0: missing_tests: No tests were found.
clone/recipe/meta.yaml:1: missing_pip_check: For pypi packages, pip check should be present in the test commands
clone/recipe/meta.yaml:1: missing_imports_or_run_test_py: Python packages require imports or a python test file in tests.
===== Final Report: =====
3 Errors and 5 Warnings were found


Add Evaluation based on query and response

Hi,
I have added an evaluation based on the query and response.
Action Items:

Prompt Engineering for query and response evaluation.
Adding example notebook.

Thank you.

also can you merge the main branch? the diff on the evaluation/base.py file isn't showing


Add testcafe parameter that allows user to interact with the page during tests run

Are you requesting a feature or reporting a bug?
I'm requesting a feature.
What is the current behavior?
Currently, when a test is executed, manual interaction with the page isn't allowed. As I understand it's intentional behavior and it's really preferable in most cases. However, I have several tests where I need a human operator to determine whether a test has passed or failed (like video playback artifacts or smooth switch between player renditions). So, I add two buttons on a page ('pass' and 'fail') for an operator to press according to the result.
What is the expected behavior?
As I see it from my perspective, I would add a parameter to testcafe (like --allow-manual-interaction) which allows user to interact with the page. I would like to make a PR if you can give me a hint where to start from.
How would you reproduce the current behavior (if this is a bug)?
N/A
Provide the test code and the tested page URL (if applicable)
N/A
Tested page URL:
Test code

Specify your

operating system: N/A
testcafe version: N/A
node.js version: N/A

Hi @Andgoncharov,
Take a look at the Client-Side Debugging topic. TestCafe shows the Unlock page button when the test is stopped on the t.debug() action. Also you can use the --debug-mode option and unlock the page by using this button.
Does it meet your needs?

Hi @AlexanderMoskovkin,
Thanks for your answer, I've tried your suggestion and it's almost perfect, except the fact that I need to click two buttons (Unlock page and Resume) for every test. I think it's enough for me, I have not so many of such tests for now. So thank you again.
As of making it even more convenient, what do you think about adding the parameter I proposed before?  I could do that by analogy the Unlock page button. Will you accept such PR?


Include RPC error message somewhere in eth error object body.

MetaMask returns some useful errors!  This would be a great thing to standardize around, error codes for the clients.
"User denied signature" is a very good example of a useful error to be aware of as a UI.

WIll be adding more support soon. Thanks!


fixup! TestStandard/read_only_csi_volume

Description
This PR fixup e2e test check for env var TestStandard/read_only_csi_volume
The logic was removed in prev PR, so here we remove check from test.
How can this be tested?
make test/e2e/standard
Checklist

[x] Unit tests have been updated/added
[x] PR is labeled accordingly with a single label
[x] I have read and understood the contribution guidelines

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (34684dd) 64.79% compared to head (706701b) 64.79%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2582   +/-   ##
=======================================
  Coverage   64.79%   64.79%
=======================================
  Files         249      249
  Lines       16368    16368
=======================================
  Hits        10605    10605
  Misses       4954     4954
  Partials      809      809

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Epic: Ingress bugs

@kyessenov commented on Mon Oct 09 2017
Context: production readiness proposal and plan
The feature “cluster ingress” is identified as incomplete test coverage. As a measure to reach Istio production quality in 0.3, this issue is opened to track the progress of providing sufficient test coverage for the feature in question.
This issue is initially assigned to the working group leads.
Recommendations:

Come up with a test plan for how the feature should be tested. Identify and document (in this issue, or a separate document this issue will link to) test cases and whether each will be covered by an integration test (with some level of mocking and/or starting up selected components in test environment), or end to end test (aka system test, which brings up the whole Istio to exercise the feature; currently live in the istio/istio repo).
If you expect the test plan is complex and controversial, consider having it formally reviewed.
State an ETA in the issue, and assign this to a developer who will execute the test plan.
Execute the test plan as the highest priority for 0.3.
For any bug or defect identified by the new test cases, file a new issue and link it from this one.
Close this issue only when the test plan is completely executed, and all additional issues identified in step 3 are fixed.

If you see a risk of not fixing this issue by end of 0.3, please contact<EMAIL_ADDRESS>as soon as possible. We will also periodically ping the issue for update.

@rshriram commented on Fri Oct 13 2017
https://github.com/istio/pilot/issues/730
https://github.com/istio/pilot/issues/484
https://github.com/istio/pilot/issues/533
https://github.com/istio/pilot/issues/731
https://github.com/istio/pilot/issues/805
https://github.com/istio/pilot/issues/926
https://github.com/istio/pilot/issues/969
https://github.com/istio/pilot/issues/1021
https://github.com/istio/pilot/issues/1389
https://github.com/istio/pilot/issues/1367
https://github.com/istio/pilot/issues/1234
https://github.com/istio/pilot/issues/1021
https://github.com/istio/istio/issues/1024
https://github.com/istio/pilot/issues/1478
https://github.com/istio/istio/issues/585

@rshriram commented on Wed Oct 11 2017
just FYI @smawson ^^^

@linsun commented on Wed Oct 11 2017
subscribe

@ZackButcher assigning this to you as you are the owner of Ingress on go/istio-schedule. please reassigng as appropriate if you are not working on this P0.

This can be closed given that people seem to have happily adopted the gateway (See mailing list traffic). Gateway + VirtualService solves all the issues that ingress was facing.


slide-start, slide-pass and slide-stop events not typed correctly

Hi, first of all thanks for creating the library!
When registering event listeners on the sliderInstance, getting the current slider number using event.detail throws a type error.
I also cannot type it myself, since this also throws an error.
Variant 1:
Using event without type declaration directly.
sliderInstance.addEventListener('slide-pass', (event) => {
  console.info(`Passing slide ${event.detail}.`);
});

Error:

Variant 2:
Providing types myself
sliderInstance.addEventListener('slide-start', (event: { detail: number }) => {
  console.info(`Started sliding towards slide ${event.detail as number}.`);
});

Error:

Update: I'm using sliderInstance.slide now which is correctly typed


match new baidu returned json

I believe baidu had changed their API a bit(also considering their recent UI change, this is very likely to be true)
I tweaked around so that the tool downloaded the thing I wanted. Someone might want to reuse my code to make it more robust though :)
Awesome work btw!

good job!

:+1:


Question: Using nvm, how does process.execPath returns iojs when initiated with 'node' on Travis-CI?

Travis-CI (which uses nvm) possesses a peculiar, but interesting behavior with iojs job: if you run node <command>, it pipes it to iojs. To wit:
# with iojs (v1.2.0) job
iojs -p process.execPath
# will return: /home/travis/.nvm/versions/io.js/v1.2.0/bin/iojs
node -p process.execPath
# will also print the same! instead of /whatever/p/a/t/h/node

How does this happen? If it is due to nvm, I would really appreciate could you point to the location of responsible code.
Thanks in anticipation.
PS: I am trying to explain it here: https://github.com/appveyor/ci/issues/139.

This is due to io.js itself - node is just a symlink to iojs. This will happen with any io.js install, installed via any method.

@ljharb, thanks for your answer. :+1:


cannot find symbol import android.support.v4.graphics.PaintCompat;

react-native-svg/android/src/main/java/com/horcrux/svg/TSpanShadowNode.java:23: error: cannot find symbol
import android.support.v4.graphics.PaintCompat;
^
symbol:   class PaintCompat
location: package android.support.v4.graphics

I am also facing this issue. Did you figure it out?

no..i could not

Have you tried building in android studio? seems you're missing this from your gradle configuration https://github.com/react-native-community/react-native-svg/blob/master/android/build.gradle#L38
And what SDK version are you using, have you tried 25? https://github.com/react-native-community/react-native-svg/issues/511#issuecomment-344567146

I've removed appcompat from the dependencies, shouldn't be an issue anymore.

I am having the same problem still.
package.json:
"react": "16.3.1",
"react-native": "0.55.2",
"react-native-svg": "^6.1.0"
android build.gradle:
compileSdkVersion 23
buildToolsVersion "23.0.1"
The error is in the TSpanShadowNode.java where it can't find that import package.

@john1jan were u able to overpass this issue?

@suhabaobaid Can you try upgrading? The latest version shouldn't even have the dependency.


Support Basic HTTP Authentication

NANOPAY-#1282 #time 1h
This will greatly simplify things for the interac integration team.

@kgrgreer @eatonk Outside of a general code review, can you think of any issues with supporting this?

Looks like a good idea to me. Just some style issues. Also, update the DIG doc. Thanks


Go: Update module path

After the move of the repository from Elastic to Open Telemetry the module path in go.mod needs to be updated, so that package from this repository can be imported and used.

We can do this in a new PR, but we should also update the paths in README.md, tools/coredump/README.md and AUTHORS.md.

Let's do this in another PR. The changes in README.md touch changes made in one of the commits removed before the repo transfer. Maybe @bobrik wants to re-apply his (amended) PR!?


extension error when trying to install eslint

I'm using Brackets 1.11 and if I try to install eslint I get an "Extension error" message. I tried a clean install of Brackets and installing node.js but that didn't help. If I leave the extension installed anyway and restart brackets, I get this error in the console:
ErrorNotification.js:122 [Extension] failed to load /Users/alvin/Library/Application Support/Brackets/extensions/user/zaggino.brackets-eslint - Error: Preference brackets-eslint.gutterMarks was redefined

Brackets 1.11 includes this extension by default. You can try uninstalling the one in your user extensions.

Cool! I was wondering why the "zaggino" prefix was removed in the preferences.


Upgrade to Django 3?

Upgrade to Django 3 and possibly also upgrade our other libraries?

Working on this in the django3 branch: https://github.com/jonfroehlich/makeabilitylabwebsite/tree/django3

Current build libraries with Django 2.1.15:
$ pip3 list

Package                                   Version
----------------------------------------- ---------
beautifulsoup4                            4.9.1
bibtexparser                              1.0.1
certifi                                   2020.6.20
cffi                                      1.14.0
chardet                                   3.0.4
cryptography                              2.9.2
Django                                    2.1.15
django-appconf                            1.0.4
django-ckeditor                           5.9.0
django-extensions                         2.0.7
django-image-cropping                     1.2.0
django-js-asset                           1.2.2
django-sortedm2m                          1.5.0
django-sortedm2m-filter-horizontal-widget 1.3.2
djangorestframework                       3.11.0
easy-thumbnails                           2.5
future                                    0.18.2
google-api-python-client                  1.5.3
httplib2                                  0.18.1
idna                                      2.10
oauth2client                              3.0.0
Pillow                                    6.2.0
pip                                       20.1.1
psycopg2                                  2.8.5
pyasn1                                    0.4.8
pyasn1-modules                            0.2.8
pycparser                                 2.20
pyOpenSSL                                 19.1.0
pyparsing                                 2.4.7
pytz                                      2020.1
requests                                  2.24.0
rsa                                       4.6
setuptools                                47.1.1
simplejson                                3.17.0
six                                       1.15.0
soupsieve                                 2.0.1
uritemplate                               0.6
urllib3                                   1.25.9
Wand                                      0.4.4
wheel                                     0.34.2
xmltodict                                 0.11.0
WARNING: You are using pip version 20.1.1; however, version 21.3.1 is available.
You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.

Django 3.2.10 is now on the test server. Have only run into one problem so far:
https://github.com/makeabilitylab/makeabilitylabwebsite/issues/974

It's now on production too and seems to be working great. Whew!


[styled IconButton] with style property boxShadow and value utility (theme) =>  causes className mismatch on SSR

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

On a Next.js application with @mui, when creating a styled version of the IconButton component and changing the style property boxShadow while using the theme =>  utility I get the following error:
Warning: Prop `className` did not match. Server: "MuiButtonBase-root MuiIconButton-root MuiIconButton-sizeMedium css-18s2z38-MuiButtonBase-root-MuiIconButton-root" Client: "MuiButtonBase-root MuiIconButton-root MuiIconButton-sizeMedium css-bapl2w-MuiButtonBase-root-MuiIconButton-root"

This means this specific context triggers this render mismatch and I have no idea why it happens. I only able to only reproduce it with what I described above.
Expected Behavior 🤔

No className mismatch.
Steps to Reproduce 🕹
I first reproduced the problem on my environment and then also reproduced on the latest release.
Codesandboxes:
Version I have the problem v5 beta3: https://codesandbox.io/s/mui-beta3-iconbutton-ssr-classname-mismatch-11gpp?file=/pages/index.js
Latest release v5 rc0: https://codesandbox.io/s/mui-rc0-iconbutton-ssr-classname-mismatch-vst5l?file=/pages/index.js
Steps:

Create a styled version of the IconButton component
Changing the style property boxShadow while using the theme =>  utility

Context 🔦

I want to render the component using SSR (Next.js) without getting this mismatch error.
Your Environment 🌎

`npx @mui/envinfo`
  System:
    OS: Windows 10 10.0.19042
  Binaries:
    Node: 14.17.1 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 7.18.1 - ~\AppData\Roaming\npm\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.1023.0), Chromium (92.0.902.84)
  npmPackages:
    @emotion/react:  11.4.0
    @emotion/styled:  11.3.0
    @types/react:  17.0.6
    react:  17.0.2
    react-dom:  17.0.2
    typescript:  4.3.5

For now the only property I could reproduce was boxShadow. But it doesn't need to have a value from theme.
const IconButton = styled(MuiIconButton)(() => ({
  boxShadow: (theme) => "none"
}));

This triggers the same warning. The problem might be the utility function, I don't know.

It only happens with styled. The sx property doesn't have the same problem:
<Box
  sx={{
    border: (theme) => "none"
  }}
>

No warning in this case.

@italodeandra you should use this syntax:
const BoxStyled = styled(Box)(({ theme }) => ({
  border: "none",
  // some styles that depend on the theme
}));

Can you reproduce the problem with this code snippet?

Sorry @mnajdova, I made it confusing. I only showed border: (theme) => "none" here as an example to prove that you don't need to actually use the value from the theme.
What I need is exactly the code from the codesandbox:
const IconButton = styled(MuiIconButton)(() => ({
  boxShadow: (theme) => theme.shadows[1]
}));

And this throws the mismatch error.

Oh, I now get what you mean. I shouldn't use the utility on the styled!
Let me try.

Yep. Sorry about that. It was a lack of attention since I knew that. I copied this line from somewhere and forget that I shouldn't use the function utility.


Manage IIS Webite task should not hardcode certstorename=MY

Please refer to this post:
https://developercommunity.visualstudio.com/content/problem/239273/iis-webapp-manage-release-task-uses-wrong-certific.html
I agree and was just "bitten" by this.

This is unfortunate as it makes automated deployments for ssl sites impossible when you put your certificate in WebHosting

This is unfortunate as it makes automated deployments for ssl sites impossible when you put your certificate in WebHosting

2 years and this hasn't been fixed?  Why is this considered an "enhancement"?  This is a bug as a configurable value is hard-coded that makes using standard deployment practices impossible.

Is there any update on this. 4 years open and I've also just been bitten by it


+3373*, +3374* and +33700* not recognized as french mobile phone numbers

Hello,
This is a follow-up of #11 . According to https://github.com/googlei18n/libphonenumber/issues/11#issuecomment-65489376 french mobile phone numbers must start with 6 or 7[5-9], however 7[3-4] and 700 should also be recognized as such.
The official plan can be found here http://www.arcep.fr/index.php?id=8146&L=1 (looks like it's only available in french, sorry)
Cheers

Thanks for letting us know Renaud! We will work on fixing this.
Cheers,
Shaopeng
On 11 May 2015 at 11:43, Renaud Drousies<EMAIL_ADDRESS>wrote:

Hello,
This is a follow-up of #11
https://github.com/googlei18n/libphonenumber/issues/11 . According to #11
(comment)
https://github.com/googlei18n/libphonenumber/issues/11#issuecomment-65489376
french mobile phone numbers must start with 6 or 7[5-9], however 7[3-4] and
700 should also be recognized as such.
The official plan can be found here
http://www.arcep.fr/index.php?id=8146&L=1 (looks like it's only available
in french, sorry)
Cheers
—
Reply to this email directly or view it on GitHub
https://github.com/googlei18n/libphonenumber/issues/688.

This change will be in the upcoming libphonenumber 7.0.7.

Thanks!

Thanks! This is in libphonenumber 7.0.7.


click the icon in Chrome, nothign happens

I downloaded the extension and updated the options successfully, but when I go to my website (or any website) and CLICK the "Check my links" icon in my toolbar, nothing happens. I also tried reverting to just the default plugin options, still nothing happens.

I haven't been able to reproduce, but we can look at a few things to hopefully pinpoint the issue.
First, we can check the Chrome version via: chrome://help/
Next, we can open two consoles to see if there are any errors.
1 - Press F12 to open the console on the current page you intend on checking
2- In another tab, Navigate to
chrome://extensions/ (Please note the version of the Check My Links extension too)
Click on the background page view of Check My Links - Inspect views: background page
Now, watch to see if any errors are logged while you click the Check My Links icon in either console.
Thanks

Thanks for getting back to me. I did as you asked and here are the versions
of each software:
Chrome Version 57.0.2987.133
[image: Inline image 1]
and I follow through F12 to "view source" for the page I want to check
links on, BUT i have no idea what you mean by this
"Click on the background page view of Check My Links - Inspect views:
background page
Now, watch to see if any errors are logged while you click the Check My
Links icon in either console."
ᐧ
Jana Sunshine
323-898-6199 |<EMAIL_ADDRESS>| Skype: j.sun.inc
https://mail.google.com/mail/u/0/#
On Thu, Apr 27, 2017 at 5:34 PM, Kyle Ladd<EMAIL_ADDRESS>wrote:

I haven't been able to reproduce, but we can look at a few things to
hopefully pinpoint the issue.
First, we can check the Chrome version via: chrome://help/
Next, we can open two consoles to see if there are any errors.
1 - Press F12 to open the console on the current page you intend on
checking
2- In another tab, Navigate to
chrome://extensions/ (Please note the version of the Check My Links
extension too)
Click on the background page view of Check My Links - Inspect views:
background page
Now, watch to see if any errors are logged while you click the Check My
Links icon in either console.
Thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ocodia/Check-My-Links/issues/65#issuecomment-297875859,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aaw1XMYcJsvAspMQmzAV4QcFh9L9Yv0sks5r0TP_gaJpZM4NJONu
.

https://youtu.be/j9VZw9ERh7Y
Used "F12" to bring up the developer tools in the current window (Also is Ctrl + Chift + I)- I am on the console tab
lol, I didn't expect to find a 404 on Android.com, but I guess that is a good demo of the intended functionality.