[openssl] Build error

Host Environment

OS: Windows 10 version 20H2(OS Build 19042.1348)
Compiler: revision

To Reproduce
Steps to reproduce the behavior:
./vcpkg install openssl:x64-windows
Failure logs
C:\src\vcpkg\vcpkg>.\vcpkg install openssl:x64-windows
Computing installation plan...
The following packages will be built and installed:
openssl[core]:x64-windows -> 1.1.1l#4

vcpkg-cmake[core]:x64-windows -> 2021-12-05
vcpkg-cmake-config[core]:x64-windows -> 2021-12-01
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
A suitable version of git was not found (required v2.32.0). Downloading portable git v2.32.0...
Downloading git...
https://github.com/git-for-windows/git/releases/download/v2.32.0.windows.2/PortableGit-<IP_ADDRESS>-32-bit.7z.exe -> C:\src\vcpkg\vcpkg\downloads\PortableGit-<IP_ADDRESS>-32-bit.7z.exe
Extracting git...
A suitable version of powershell-core was not found (required v7.2.0). Downloading portable powershell-core v7.2.0...
Downloading powershell-core...
https://github.com/PowerShell/PowerShell/releases/download/v7.2.0/PowerShell-7.2.0-win-x86.zip -> C:\src\vcpkg\vcpkg\downloads\PowerShell-7.2.0-win-x86.zip
Extracting powershell-core...
Restored 0 packages from C:\Users\z0120097\AppData\Local\vcpkg\archives in 249.9 us. Use --debug to see more details.
Starting package 1/3: vcpkg-cmake:x64-windows
Building package vcpkg-cmake[core]:x64-windows...
-- Installing: C:/src/vcpkg/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake
-- Installing: C:/src/vcpkg/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake
-- Installing: C:/src/vcpkg/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake
-- Installing: C:/src/vcpkg/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_get_vars.cmake
-- Installing: C:/src/vcpkg/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/cmake_get_vars
-- Installing: C:/src/vcpkg/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/cmake_get_vars/CMakeLists.txt
-- Installing: C:/src/vcpkg/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg-port-config.cmake
-- Installing: C:/src/vcpkg/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\z0120097\AppData\Local\vcpkg\archives\8d\8d2010820bd33284289f5952b84f9c1b4953294d5f125e1f060ba4039144917a.zip
Installing package vcpkg-cmake[core]:x64-windows...
Elapsed time for package vcpkg-cmake:x64-windows: 149.8 ms
Starting package 2/3: vcpkg-cmake-config:x64-windows
Building package vcpkg-cmake-config[core]:x64-windows...
-- Installing: C:/src/vcpkg/vcpkg/packages/vcpkg-cmake-config_x64-windows/share/vcpkg-cmake-config/vcpkg_cmake_config_fixup.cmake
-- Installing: C:/src/vcpkg/vcpkg/packages/vcpkg-cmake-config_x64-windows/share/vcpkg-cmake-config/vcpkg-port-config.cmake
-- Installing: C:/src/vcpkg/vcpkg/packages/vcpkg-cmake-config_x64-windows/share/vcpkg-cmake-config/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: C:\Users\z0120097\AppData\Local\vcpkg\archives\67\67de742a530e776a8b02bdbfede4c84be1519e9ca7fcba459d13801ccf5b4dec.zip
Installing package vcpkg-cmake-config[core]:x64-windows...
Elapsed time for package vcpkg-cmake-config:x64-windows: 131.7 ms
Starting package 3/3: openssl:x64-windows
Building package openssl[core]:x64-windows...
-- Downloading https://www.openssl.org/source/openssl-1.1.1l.tar.gz;https://www.openssl.org/source/old/1.1.1/openssl-1.1.1l.tar.gz -> openssl-1.1.1l.tar.gz...
-- Downloading https://strawberryperl.com/download/<IP_ADDRESS>/strawberry-perl-<IP_ADDRESS>-32bit.zip -> strawberry-perl-<IP_ADDRESS>-32bit.zip...
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'manifests' = off
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Downloading https://strawberryperl.com/download/<IP_ADDRESS>/strawberry-perl-<IP_ADDRESS>-32bit.zip
Error: Failed to download from mirror set:
https://strawberryperl.com/download/<IP_ADDRESS>/strawberry-perl-<IP_ADDRESS>-32bit.zip: failed: status code 403

[DEBUG] D:\a_work\1\s\src\vcpkg\base\downloads.cpp(705)
[DEBUG] Time in subprocesses: 0 us
[DEBUG] Time in parsing JSON: 1 us
[DEBUG] Time in JSON reader: 0 us
[DEBUG] Time in filesystem: 726 us
[DEBUG] Time in loading ports: 0 us
[DEBUG] Exiting after 2.568 s (2560988 us)
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:84 (message):
  Failed to download file with error: 1
  If you use a proxy, please check your proxy setting. Possible causes are:

  1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
     to `https://address:port`. This is not correct, because `https://` prefix
     claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
     , etc..) is an HTTP proxy. Try setting `http://address:port` to both
     HTTP_PROXY and HTTPS_PROXY instead.

  2. You are using Fiddler. Currently a bug (https://github.com/microsoft/vcpkg/issues/17752)
     will set HTTPS_PROXY to `https://fiddler_address:port` which lead to problem 1 above.
     Workaround is open Windows 10 Settings App, and search for Proxy Configuration page,
     Change `http=address:port;https=address:port` to `address`, and fill the port number.

  3. You proxy's remote server is out of service.

  In future vcpkg releases, if you are using Windows, you no longer need to set
  HTTP(S)_PROXY environment variables. Vcpkg will simply apply Windows IE Proxy
  Settings set by your proxy software. See (https://github.com/microsoft/vcpkg-tool/pull/49)
  and (https://github.com/microsoft/vcpkg-tool/pull/77)

  Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Call Stack (most recent call first):
scripts/cmake/vcpkg_download_distfile.cmake:309 (z_vcpkg_download_distfile_show_proxy_and_fail)
scripts/cmake/vcpkg_find_acquire_program.cmake:622 (vcpkg_download_distfile)
ports/openssl/portfile.cmake:12 (vcpkg_find_acquire_program)
scripts/ports.cmake:142 (include)
Error: Building package openssl:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with git pull and .\vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+openssl
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[openssl]+Build+error
including:
package: openssl[core]:x64-windows -> 1.1.1l#4
vcpkg-tool version: 2021-12-09-724cea8b33cbf06c645f5095fa29773697da9761
vcpkg-scripts version: 772fe6cbc 2021-12-22 (3 hours ago)
Additional context
Tried git pull and the package is already up to date.

Please use proxy or directly download [this file](https://strawberryperl.com/download/<IP_ADDRESS>/strawberry-perl-<IP_ADDRESS>-32bit.zip) and put it to VCPKG_ROOT/downloads then try again.
Please note this file is huge.

Can you please provide some details on how to use proxy?

@ksh7393 It's in the message:
  1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
     to `https://address:port`. This is not correct, because `https://` prefix
     claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
     , etc..) is an HTTP proxy. Try setting `http://address:port` to both
     HTTP_PROXY and HTTPS_PROXY instead.

  2. You are using Fiddler. Currently a bug (https://github.com/microsoft/vcpkg/issues/17752)
     will set HTTPS_PROXY to `https://fiddler_address:port` which lead to problem 1 above.
     Workaround is open Windows 10 Settings App, and search for Proxy Configuration page,
     Change `http=address:port;https=address:port` to `address`, and fill the port number.

  3. You proxy's remote server is out of service.

  In future vcpkg releases, if you are using Windows, you no longer need to set
  HTTP(S)_PROXY environment variables. Vcpkg will simply apply Windows IE Proxy
  Settings set by your proxy software. See (https://github.com/microsoft/vcpkg-tool/pull/49)
  and (https://github.com/microsoft/vcpkg-tool/pull/77)

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.


Promise-based workflow is now available

My proposal of promise-based workflow.
To keep the code simple, I introduced an additional dependency (event-to-promise).
The change seems to satisfy Derek's requirement mentioned here.
I mirrored the tests to show that both promise-based and event-based workflows are available.

Let's go with dependency
On Tue, Jul 24, 2018, 11:37 PM Serge Medvedev<EMAIL_ADDRESS>wrote:

@serge-medvedev commented on this pull request.
In package.json
https://github.com/perezd/riemann-nodejs-client/pull/28#discussion_r204995279
:

},
"repository": {
"type": "git",
"url": "git://github.com/perezd/riemann-nodejs-client.git"
},
"dependencies": {

"node-protobuf": "^1.4.3"

"node-protobuf": "^1.4.3",
"event-to-promise": "^0.8.0"

So, are we going to leave this dependency as is OR to copy-paste the code?
I vote for the first option.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/perezd/riemann-nodejs-client/pull/28#discussion_r204995279,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABQdoQk3FfzIasIWRwMy-K1bfEf1_8Kks5uKBIygaJpZM4VcOlG
.

That seems to be it: are we ready to merge this PR?

A question about future plans: what do you think about deprecation the event-based workflow in favor of combined promise- and callback-based one (like in MongoDB or Elasticsearch)? We could do so in the next major release (2.0.0?), still maintaining the last version with support of event-based workflow.

Why limit? Emitter feels like the right paradigm normally, when using udp
what does a callback do for us?
On Wed, Jul 25, 2018, 11:52 PM Serge Medvedev<EMAIL_ADDRESS>wrote:

A question about future plans: what do you think about deprecation the
event-based workflow in favor of combined promise- and callback-based one
(like in MongoDB or Elasticsearch)? We could do so in the next major
release (2.0.0?), still maintaining the last version with support of
event-based workflow.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/perezd/riemann-nodejs-client/pull/28#issuecomment-407995489,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABQdhFko6DZ0-wd5e87DoWvYUeBn36kks5uKWcVgaJpZM4VcOlG
.

what does a callback do for us?

It will tell if the message was successfully sent (no DNS issues, for example).
It seems to be not too useful but is great from the point of view of uniformity when working with both TCP and UDP.
I'm not completely against Emitter interface but I don't like those warnings about 'too many listeners and possible memory leaks' Node yields (they're seen in tests, both old and new). Doesn't our abstraction seem to be a bit leaky, if we make user add something like: emitter.setMaxListeners(0) to prevent those?
I don't exclude the possibility that it's just me, who doesn't understand Emitter and cannot work with it properly.

Sure, for better or worse, many people are relying on the existing API that we have, I wouldn't be OK with removing it. I'm OK with adding additional APIs or options for working with stuff, but not removal.

Got it. Let's move on.

And before you merged this PR...
Seems to me that I see an issue in my code: what if user doesn't want to use promises and there's an error (in a send call) which is supposed to be handled by error event?
Since I return a promise, it will end up with 'unhandled rejection error'. It's just a warning now but may lead to Node crash in the future.
Have to fix it. What about letting that flag 'options.returnPromise' to determine promise usage in all places?

That is fine, sadly I've merged it, so can you send another PR?
On Fri, Jul 27, 2018 at 11:53 AM Serge Medvedev<EMAIL_ADDRESS>wrote:

And before you merged this PR...
Seems to me that I see an issue in my code: what if user doesn't want to
use promises and there's an error (in a send call) which is supposed to
be handled by error event?
Since I return a promise, it will end up with 'unhandled rejection error'.
It's just a warning now but may lead to Node crash in the future.
Have to fix it. What about letting that flag 'options.returnPromise' to
determine promise usage in all places?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/perezd/riemann-nodejs-client/pull/28#issuecomment-408508562,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABQdujmZUcsrqWRlEZbj4b9fmElzL4mks5uK2GbgaJpZM4VcOlG
.

Of course, there it is: #29 .


Docker-compose example on README doesn't work

I took the example docker-compose.yml from README.md and only added version number to top (tried with 2.1 as well). I also tried :latest tag.
➜  cat docker-compose.yml
version: '3'

services:
  site:
    command: jekyll serve
    image: jekyll/jekyll:3.5
    volumes:
      - $PWD:/srv/jekyll
      - $PWD/vendor/bundle:/usr/local/bundle
    ports:
      - 4000:4000
      - 35729:35729
      - 3000:3000
      -   80:4000
➜  docker-compose run site jekyll new site
su-exec: new: No such file or directory

I am unfamiliar with su-exec which seems to be causing issues here.
I'm using Docker for Mac:
Version 17.09.0-ce-mac35 (19611)
Channel: stable
a98b7c1b7c

Removing bundler volume fixes the issue. Ofc you'll loose caching ability then.

You only lose caching long enough to generate your Gemfile via Jekyll.  This is expected behavior really, and I deemed it unnecessary to complicate life by adding a secondary service just to run new since it's something only done once.  If it's a problem I think I would rather remove the new example rather than add an extra one-time service, or to remove the caching example entirely as you don't even need caching if you are running jekyll new because we provide every dependency Jekyll would want, and some on-top of that to reduce the need for caching.

I'm open to suggestions as well if you have any.

Closing in favor of #189.


Changes to reduce CPU requests for TDS systems

Summary and Scope
Edit customizations.yaml during fresh install to apply lower CPU requests for some services requests larger than needed on TDS/3 worker systems.
Issues and Related PRs

Partially Resolves CASMINST-3688

Testing
Validated the merge of yaml looks correct (craystack)
Tested on:

craystack

Test description:
Yaml looks good, will need to validate final chart impacts on a fresh install 1.2 system (with SMA installed)
Risks and Mitigations
None
Pull Request Checklist

[ ] Version number(s) incremented, if applicable
[ ] Copyrights updated
[ ] License file intact
[ ] Target branch correct
[ ] CHANGELOG.md updated
[ ] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

backport release/1.0

\backport release/1.0

/backport release/1.0


Using display in a notebook requires a kernel be selected that has IPython installed

Have a cell like so:
display('foo')

You'll get an error in VS code until you actually install IPykernel into the selected kernel:

From a notebook user's point of view this feels like a bug. You never have to import anything to use display.
I feel like display should be treated like a system library and not a 3rd party library that needs an environment for it to be recognized.
For a notebook user, display is equivalent to print which doesn't require a kernel to be setup.

There are other symbols exposed by IPykernel other than display (ex. display_pretty). Will we special case those also?
Could there be issues where our special-case view of IPykernel is out-of-sync (different version, different symbols) with the version they will eventually install?

There are other symbols exposed by IPykernel other than display (ex. display_pretty). Will we special case those also?

Yeah everything that's default included in a notebook. Essentially a notebook does from IPython import * at the top of every cell.

Could there be issues where our special-case view of IPykernel is out-of-sync (different version, different symbols) with the version they will eventually install?

Not very likely in my opinion. This is like typesheds being out of date with the system libraries. IPython display hasn't changed in a long time. Maybe more overloads are added as time goes on.

I agree. If it doesn't lead to errors at runtime, I think ideally we wouldn't show it as an error.
I understand reservations against special casing individual modules, but what would be the implications of special casing the entire package? This would be coming from the point of view that we want to provide 1st class Jupyter notebooks support and Jupyter has a strong dependency on IPykernel.

If we had a 'typeshed' module for IPython and we shipped it next to the other ones, the changes shouldn't be too bad? We have to treat IPython like builtins I think.

Pyright already provides the ability for a user to extend builtins.pyi.  See this documentation for details. This same mechanism could be used to inject IPython symbols into builtins.

We're planning to add type stubs for IPython, as it would be enough to take care of this problem given there's no explicit imports. We should also document all the typestubs we bundle in Pylance in a single place, to make it more easily accessible.

This issue has been fixed in prerelease version 2023.5.51, which we've just released. You can find the changelog here: CHANGELOG.md


Feat/support flow event

Codecov Report

Merging #5 (df84a34) into master (5060794) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master       #5      +/-   ##
==========================================
+ Coverage   99.46%   99.49%   +0.02%
==========================================
  Files           8        8
  Lines         558      589      +31
==========================================
+ Hits          555      586      +31
  Misses          3        3

Impacted Files
Coverage Δ

trazer/__init__.py
100.00% <ø> (ø)

trazer/export.py
88.88% <ø> (ø)

tests/test_trace_events.py
100.00% <100.00%> (ø)

trazer/trace.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5060794...df84a34. Read the comment docs.


Implement rtd

Add documentation to Read The Docs
http://wagtailtrans.readthedocs.io/en/latest/index.html

Coverage remained the same at 79.773% when pulling 68a8c70ea82487f5c282d20124496fd55f46b9bb on implement-rtd into 3390e1a3a76585d4a3456b488a497f1ab2e9c540 on master.

Coverage remained the same at 79.773% when pulling 68a8c70ea82487f5c282d20124496fd55f46b9bb on implement-rtd into 3390e1a3a76585d4a3456b488a497f1ab2e9c540 on master.


Please re-license under a more liberal license

Please consider using a different license for this great product!
First and foremost, this is a library which is designed to be used by other applications.
I would love to use this in my closed source Electron application, but neither the GPL nor LGPL would allow this.
Please consider any of the BSD, ISC, MIT or Apache licenses as used by the vast majority of the NPM world.

Re-licensed!

Many many thanks!


check hashcode before calling equals on two terms

@andreistefanescu please review

After talking to Yilong, I am going to hold off on making this change until I get a chance to do more thorough profiling information on whether this is likely to be a uniform optimization, or if it will slow some cases down.


Adding Property to Object in Array Not Working

Version: 1.3.1
[x] Issue:
Trying to add a property to objects that are unfortunately pretty deep into the state tree. Instead of having the property added to the object it replaces the entire object i.e I lose all other properties on the object. I am doing something wrong but not sure what it is. The problem occurs for the SET_LAYOUT_AREA case in the following reducer:

   const Pages = (state = {isFetching: false,collection: {},current: null}, action) =>
     produce(state, draft => {
    switch(action.type){
      case RECEIVED_PAGE:
        draft.isFetching = false;
        draft.collection[action.page.id] = action.page;
        draft.currentPage = action.page.id;
        return;
      case SET_CURRENT_PAGE:
        draft.current = action.id;
        return;
      case SET_LAYOUT_AREA:
        draft.collection[action.id].layout_json.forEach((boxLayout, idx) => {
          boxLayout.area = action.layouts[boxLayout.uid];
        });
        return;
      default:
        return;
  }
});

Expected behavior:  I expect it to return the original object with an added property of area. ex:
[{existingProp1: data, existingProp2 :data, area: 1234}...]
Observed behavior:  I observed that it only returns the area property and I lose all other properties:
 [{ area: 1234}....]
[x] Occurs when using Proxies (use setUseProxies(true))

Closing for the lack of a reproduction


Rearchitect xIPAddress, xDNSServerAddress and xDefaultGatewayAddress

The resources were modified in the following ways:

Test-Properties function removed and logic moved into Test-TargetResource and/or Set-TargetResource so that code to test state is not called twice. As per recommendation from @tysonjhayes in #22.
Parameter test logic removed into Test-ResourceProperties function with additional checking for IPv6 parameters.
Additional Pester tests added to each resource - including some IPv6 specific tests.
"Lightbulb" changes suggested by ISESteroids interface.
Attempt to mimic code style of new xFirewall resource.
Code reviews gratefully accepted :)

Gave it a quick glance, looks good so far, going to block some time in a few hours to go into this in detail. Thanks for the work!

OK - I'm going to hold off making comments about the unit tests until we've addressed some of my other comments as if we take them would change what we expect the tests to do. :laughing: So no sense in spending to much time on them right now.
Overall I think these are good changes, I think we can make some improvements on the logic but this is exactly what I was looking for in a refactor for these functions. Thanks a bunch!

OK, I think I've made all the changes as per your comments (hopefully I didn't miss any :) ). It also highlighted a couple of logic problems in the Test-ResourceProperty function (and Pester tests) that I have fixed, mainly relating to ensuring IPv6 addresses are tested correctly. I tried to make sure any comment on one resource was reflected in all the other resources as I try to go for consistency. :)
Great to get to work on these :) Cheers.

Hi @tysonjhayes - I've made the modifications to the xDefaultGatewayAddress resource, but before I go putting the same changes into the other resources I thought I'd run this one past you to make sure it was going in the right direction :) I pretty much replicated the method/code from the xWebAdministration resources you linked to.
I also refined the try/catch blocks in the Set-TargetResource so that there is no all encompassing try/catch, instead there are individual try/catches round the actual cmdlets that do the work so the resource provides more specific feed back when errors occur.
If you're OK with the changes to this resource, I'll replicate them in the others.

Forgive me as I'm going over Gateway with a fine tooth comb, currently this only returns Address if it finds a value, given null is an acceptable value of a Default Gateway (in this case it would be no gateway defined) wouldn't it make sense to return null as the value in Get-TargetResource? Just a thought. :+1:

So my only thoughts at this point continue to be around the use of try/catch, if its needed, and if we should be throwing our own errors.
Specifically the way I'm thinking about it as such:
try
{
    throw 'some easily found error on bingoogle/stack overflow'
}
catch
{
    throw 'an exception that only occurs in our code but we didn't actually write the function'
}

With the example I gave, if Get-NetRoute throws an exception it'll be a "known" exception that a user could find other examples of, by rethrowing the exception we'll lose that information and may obscure resolution of the issue as debugging can be quite painful on these scripts (source: I've done it while developing a bunch of these).
I'm not saying we need to change it, just something that keeps coming to mind while I look at this code.
As it stands this looks good to continue forward with to the rest of the resources, thanks for all of the hard work!

I completely get what you're saying - why bother wrap any miscellaneous errors with a try/catch as we're just obfuscating the original error. I'd bow to your experience here and say that I should remove the try/catches around these specific cmdlets and just make sure they've got -ErrorAction Stop parameter on each cmdlet - just let any cmdlet errors be handled natively. I'll do this today :)

Bow to my experience?
You're making me out to be like this:

Instead of how I feel:

Feel free to tell me no. :laughing:

Hahaha LOL! :) I think I'm just mainly "borrowing" the best style elements and DSC Resource best practices based on what I'm seeing in the other DSC xResources - for better or for worse. So I'm definitely in this boat:

Still, I think these discussions are definitely the best ways of nutting out some good "best practices" - unless someone must wiser has already done this somewhere?

Just wanted to follow up @PlagueHO did you have a chance to work on the changes?

Doh! I did, but I pushed them to my Dev branch, where as the PR is for my Rearchitect-xIPAddress-xDefaultGatewayAddress branch. Have merged them now. Sorry about that.

@PlagueHO that merge only seems to have changes for the readme.md (unless I'm missing something). Also didn't pass the appvoeyor tests.

GitHub being helpful actually put the changes I made to remove the try/catches in the date/time order that I actually made them - so it slotted the commit message in quite a bit earlier. So the changes are in there, but you'll need to scroll way up to see the commit. You can see it with an ID version 61723c0 between the pictures. :) The Readme.md change was just to trigger an AppVeyor rebuild. The AppVeyor failure is a bit of a pain - it's the one where it fails to download the DSCTools module randomly and a rebuild just needs to usually be triggered. But I can only do that by checking something in. I'll do that now. Sorry about that!

Yes, the failure is quite annoying I'm seeing it over in xWebadministration as well (https://github.com/PowerShell/xWebAdministration/issues/52) and am talking to people about trying to get it solved. It's clogging up quite a bit of work.
This looks way better, and way cleaner. I'll merge this once we get AppVeyor to pass the tests. :+1:

Doh! I logged the DSCResources.Test issue in with the DSCResource.Tests project before seeing your comments about talking to people. That will would be awesome to get that one resolved - I'm sure half my commits are "dummies" :)

@PlagueHO one last thing, can we update the README.md to include these changes so we can get it communicated once we update the resource again?

Excellent point! And done! :+1:

And Merged. Thanks for all of the hardwork.

A pleasure! I'll get onto issue #25 later on today :)


RE #18483 - Making the EMG.Extensions.Logging.Loggly awaitable

Update EMG.Extensions.Logging.Loggly package and remove Thread.Sleep instances with new flush method.

@diaconu96vi FYI, I've created a new version of the templates: https://github.com/emgdev/templates/releases/tag/v3.1.2


feat(refactor): removal of SCAN FIELD action and refactoring of refetch feature

Define your request
As discussed in #632 SCAN FIELD action is redundant. After its removal, refetching and throttling feature will require some refactoring to provide better UX for users.
-- fill in the line below:
** discord username: Göksenin#7758 **
Define the alternatives you have in mind

'SCAN FIELD' action and throttling info section will be removed

Fetching new dataset will be integrated to moveend action of map

Extra context
Add some extra context or screenshot pertaining to said feature request.

can take this once approved


is_paused option in DAG edit fails

Both the "is paused" and "scheduler lock" buttons on DAG edit (i.e. the (i) button from the homepage) fail to work for me.
I think this is due to airflow/www/views.py setting them as disabled.  For "is_paused" this was done in a27d11068dcd6d46703d27f2d4d25911f0b9693a  FYI.
For pausing the on/off button on the home screen works fine and seems to do exactly the same thing.
Doesn't fix scheduler lock, but perhaps removing is_paused (or hiding it until a better non-flickering solution is found would be a good idea.  Not that I see any flickering FWIW.

Adding an image of the disabled controls mentioned above : Image below of the screen launched by clicking the info button on the Home Screen.

all of this is meant to be read-only. is_paused should be interacted with in the main DAGs page, and scheduler_lock will be used by the different schedulers  to not step on each other's toes.

Aaaah!  That'd explain it :-D  Trying to figure out how to make that obvious.
Whilst you get here by clicking on "(i)" info button, the URL is /edit/ and the save/save&continue/cancel buttons could be replaced wth just "OK".
https://github.com/airbnb/airflow/issues/174 you actually mention this too if I've read it correctly :-)

Yeah we should just deprecate this page and use the DAG details page for all this.


pluggable logger

Would you be open to accepting a PR that makes the actual logger a pluggable? So I can wrap my projects logger in an interface that I give to hc, this way your logs end up within the logging the controlling project maintains?
Default behaviour would be exactly as is today
If so, I can look to do a PR, just wanted to test the water first.
thanks

If you logger is a log.Logger, can change the hap logger like this.
import(
    hclog "github.com/brutella/hc/log"
    "log"
)

var mylogger *log.Logger
hclog.Debug = &hclog.Logger{mylogger}
hclog.Info = &hclog.Logger{mylogger}


processing doesn't update status

Currently the table is not being updated with status: "processing"

Also, the conditional shows the button even while is processing.


Live 21 Nov 16

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

aspnetcore/hosting/aspnet-core-module.md
:white_check_mark:Succeeded

Details

aspnetcore/hosting/directory-structure.md
:white_check_mark:Succeeded

Details

aspnetcore/performance/caching/response.md
:white_check_mark:Succeeded

Details

aspnetcore/security/authentication/accconfirm.md
:white_check_mark:Succeeded

Details

aspnetcore/tutorials/first-mvc-app/details.md
:white_check_mark:Succeeded

Details

aspnetcore/tutorials/first-mvc-app/start-mvc/sample2/src/MvcMovie/Controllers/MoviesController.cs
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

Details

aspnetcore/hosting/aspnet-core-module.md
:white_check_mark:Succeeded

Details

aspnetcore/hosting/directory-structure.md
:white_check_mark:Succeeded

Details

aspnetcore/performance/caching/response.md
:white_check_mark:Succeeded

Details

aspnetcore/security/authentication/accconfirm.md
:white_check_mark:Succeeded

Details

aspnetcore/tutorials/first-mvc-app/details.md
:white_check_mark:Succeeded

Details

aspnetcore/tutorials/first-mvc-app/start-mvc/sample2/src/MvcMovie/Controllers/MoviesController.cs
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


If node_modules is a symbol link, node-gyp fail to resolve path in include_dirs

If node_modules is a symbol link, node-gyp rebuild fails.
Sample error (npm-symlink-0/node_modules is a symbol link to ../npm-symbol-link-0-modules):
> rm -rf node_modules/* && npm install

><EMAIL_ADDRESS>install /Users/hax/r/sandbox/npm-symlink-test/npm-symlink-0/node_modules/canvas
> node-gyp rebuild

gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
module.js:442
    throw err;
    ^
Error: Cannot find module 'nan'
    at Function.Module._resolveFilename (module.js:440:15)
    at Function.Module._load (module.js:388:25)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at [eval]:1:1
    at Object.exports.runInThisContext (vm.js:54:17)
    at Object.<anonymous> ([eval]-wrapper:6:22)
    at Module._compile (module.js:541:32)
    at node.js:333:29
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
gyp: Call to 'node -e "require('nan')"' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/local/nvm/versions/node/v6.2.0/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:305:16)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12)
gyp ERR! System Darwin 14.5.0
gyp ERR! command "/usr/local/nvm/versions/node/v6.2.0/bin/node" "/usr/local/nvm/versions/node/v6.2.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/hax/r/sandbox/npm-symlink-test/npm-symlink-0-modules/canvas
gyp ERR! node -v v6.2.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok

Current workaround:
Make sure symbol link target path have a parent with the same name of package name.
For example,
ln -s  ../any_path/npm-symlink-0/any_path node_modules

That's not a node-gyp bug.  The binding.gyp of the module that you're trying to build executes node -e 'require("nan") and that is the command that fails, i.e., it's node's built-in require() function that chokes on the symlink.  Check the main nodejs/node bug tracker, there are a few open bugs about that.


iPad Scanner Native SDK

ITS-Pro time category: https://its-pro.ucsd.edu/browse/MA-74
This is complete when:

[x] The iPad app implements the native Scandit SDK
[ ] Tested successfully on iPad

IPad app implements Scandit SDK, and is able to scan and submit barcodes while rejecting invalid barcodes. Currently isn't able to recognize duplicate barcodes.

After testing the app more thoroughly using the following smoke test we have found few issues.
When a staff member successfully suits a scan the scanner still displays MyStudentChart instead of MyUCSDChart

When the user logs in and scans a barcode successfully the app logs the user out by navigating back to the login screen. However, if you look at the screen it has a back navigator on the top left.

Once you tap that screen it takes you back to the scanner even though the user is logged out.

If the user taps back one more time the app will redirect you back to the original login screen with the user's credentials already inputted into the fields.

This is not the expected behavior.
TODO:

[ ] Make sure the auto logout navigates the user back to the login screen without having the back arrow
[ ] Update the successful submission screen so that it reflects staff submission too (MyStudentChart and MyUCSDChart)

After testing the app more thoroughly using the following smoke test we have found few issues.
When a staff member successfully suits a scan the scanner still displays MyStudentChart instead of MyUCSDChart

When the user logs in and scans a barcode successfully the app logs the user out by navigating back to the login screen. However, if you look at the screen it has a back navigator on the top left.

Once you tap that screen it takes you back to the scanner even though the user is logged out.

If the user taps back one more time the app will redirect you back to the original login screen with the user's credentials already inputted into the fields.

This is not the expected behavior.
TODO:

[ ] Make sure the auto logout navigates the user back to the login screen without having the back arrow
[ ] Update the successful submission screen so that it reflects staff submission too (MyStudentChart and MyUCSDChart)

Task was completed with this commit hash4423ae1d447ab777a18db0465137641e25c37c6b.
PR can be found here.

Task was completed with this commit hash4423ae1d447ab777a18db0465137641e25c37c6b.
PR can be found here.


ClickOnce deployment failing

When selecting the parameter -e ClickOnce=Y the script nicely creates a ClickOnce deployment.
Output:
.
.
Create Web Site
Create NAV Web Server Instance
Create http download site
Create ClickOnce Manifest
Container IP Address: <IP_ADDRESS>
Container Hostname  : 9f88718660a7
Web Client          : https://9f88718660a7/NAV/WebClient/
ClickOnce Manifest  : http://9f88718660a7:8080/NAV

Files:
http://9f88718660a7:8080/certificate.cer
.
.

However, when trying to run the deployment, an error appears stating that the deployment could not be started.
Excerpt from the logfile:
ERROR DETAILS
	Following errors were detected during this operation.
	* [11-8-2017 12:45:40] System.Deployment.Application.InvalidDeploymentException (Zone)
		- Deployment and application do not have matching security zones.
		- Source: System.Deployment

I will check this

@ptijsma - I suppose the error comes from the log of the manifest you run on your host (or pc or whatever). Do you use Google Chrome to open the link? Have you tried to open the page from IE/Edge for example?

I can confirm that like for @Koubek it only worked with IE for me, not with Chrome. And it looks like you used nated networking to access the ClickOnce deployment. Did you access it from a second machine using exposed or directly on the Container host? That can lead to a situation where you download the initial file from the container host and then it tries to download the application from the URL/hostname of the Container itself and ClickOnce doesn't like that mismatch. But if I remember correctly that error message is slightly different

Maybe I should .zip the clickonce manifest, then you could automate the download and host it on a file share or like, if the container hosted option provides problems?

NAT networks are generally problems for many applications served to outside. I have seen many with the problems.
If anyone insists to run sth. on NAT network and publish it outside, the ideal way to avoid some of the problems is mapping the ports on the same numbers (host_id : container_port - both should have the same value). To achieve it (and be able to run more than one container) you need the option to specify the port numbers that will be used internally in the container for each service.
What remains is the hostname inside the package... The manifest points to the containers hostname so if you want to access using the same package from outside (not from the **docker host**) you are in troubles. This won\t work right now.
The best way and the most logical one is using transparent networking in the cases, you need to publish to the outer world (even on the LAN).

I agree with @Koubek, I don't see a good way to get this done with nat networking in a "distributed" scenario where you have a Docker host and other machines as clients. In a "dev" scenario where you e.g. have the Container running on your local laptop and want to connect to it, this should still work fine. Therefore from my point of view we should probably document a bit more about it but we have two valid scenarios (distributed with transparent network and "same machine" with nat) and users just need to understand which one they can use
@ptijsma does it work for you with distibuted / transparent or "same machine / NAT setup in IE?

I'm running it on my local laptop (since my main purpose for Docker containers is to find out if I can easily distribute demo environments of our ISV product amongst our consultants and being able to update them)
I've just tried running the ClickOnce from IE and this indeed did the Trick.
Still strange it doesn't work from Chrome though. In the end it's still just an application manifest being executed.

I have explained the problem of the nat and the ports (mapping and publishing). And I told that there was also a problem of the hostname. You can access using container name / container hostname from your host. In case you need for any reason access the container behind nat from your LAN, you would need to adjust ClickOnce publishing process and inject the hostname you would like to use via an env variable. The ClickOnce generator should be able to accept this variable and set Server value use this instead of using the container`s $hostname.
But this should be possible, you can try it.
@freddyk - I am not sure if this approach is really necessary to implement in the base image. I still recommend accessing via transparent networks in these scenarios. You should decide and eventually close the issue.
@ptijsma - Is this acceptable solution for you (using transparent networks or eventually create your own overrides/solution)?

I was thinking about it a little bit more and I think we would need this approach in case we want support Docker Swarm. This approach is actually pretty same we would use for overlay networks and multi-node swarm solution that should be published to the outer world.
I will send you a proposal that would be tested on both, nat and overlay networks (the second one on the swarm).

Hi @Koubek
I think the workaround will work, Going forward we should only use Web Client anyway, but for now Windows Client is a must. And since we know it'll be EOL in the (near) future anyways, a workaround will do fine :-)

Closing the issue

Thank you for the post.
I was struggling with this, but as soon as I tried IE it worked fine.


Clean up improperly imported categories

The base image contains a number of categories whose names begin with private/ or private-, primarily on methods in the RB* and IDB* packages. Confusingly, some of these methods are also marked public. Since Dolphin can assign multiple categories to a method, it seems like a method in e.g. private/transforming should instead be private and in category transforming. If this seems reasonable, I can go ahead and make a PR for the change. For reference, the full list of such categories is:

private/accessing
private helpers
private/transforming
private / actions
private/methods
private/changes
private-replacing
private/variables

Originally we deliberately preserved these as is in order to minimise change when importing/exporting the code. That is probably no longer relevant, so I think it would be fine to remap them to represent the categorisation properly.

Fixed by #863


Trim line before its been added to the license_lines

Fix for #2

Apologies created and merged before checking github for your PR. Thanks a lot for submitting.

NP! Testing your solution now.


Enable eslint rule to use 4 spaces indent

Now we have https://eslint.org/docs/rules/indent rule enabled and set to 4 spaces
Also this PR fix all indentation errors

Codecov Report

Merging #146 into master will not change coverage.
The diff coverage is 25%.

@@          Coverage Diff           @@
##           master    #146   +/-   ##
======================================
  Coverage    75.1%   75.1%
======================================
  Files          25      25
  Lines        1458    1458
  Branches      230     230
======================================
  Hits         1095    1095
  Misses        363     363

Impacted Files
Coverage Δ

src/tekton/task.ts
88.23% <ø> (ø)
:arrow_up:

src/tools.ts
94.44% <0%> (ø)
:arrow_up:

src/tkn.ts
77.93% <0%> (ø)
:arrow_up:

src/util/download.ts
100% <100%> (ø)
:arrow_up:

src/tekton/clustertask.ts
88.23% <100%> (ø)
:arrow_up:

src/tekton/pipelinerun.ts
100% <100%> (ø)
:arrow_up:

src/tekton/pipelineresource.ts
97.29% <100%> (ø)
:arrow_up:

src/util/progress.ts
100% <100%> (ø)
:arrow_up:

src/pipeline/pipelineExplorer.ts
57.14% <39.13%> (ø)
:arrow_up:

src/util/MultiStepInput.ts
6.49% <4%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d13ee99...cf631be. Read the comment docs.


k8s-1.13-net-next CI: K8sServicesTest Bookinfo Demo Tests bookinfo demo

/home/jenkins/workspace/Cilium-PR-K8s-1.13-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:514
DNS entry is not ready after timeout
Expected
    <*errors.errorString | 0xc001e0c2a0>: {
        s: "DNS 'productpage.default.svc.cluster.local' is not ready after timeout: 7m0s timeout expired",
    }
to be nil
/home/jenkins/workspace/Cilium-PR-K8s-1.13-net-next/src/github.com/cilium/cilium/test/k8sT/Services.go:2937

https://jenkins.cilium.io/job/Cilium-PR-K8s-1.13-net-next/418/
500d4631_K8sServicesTest_Bookinfo_Demo_Tests_bookinfo_demo.zip
Split out of #13833 as suggested in https://github.com/cilium/cilium/issues/13833#issuecomment-758292182. This is a different failure which occurs on net-next, not GKE. The root cause seems to be something else.

Also hit by @jrajahalme in #14370 (also see https://github.com/cilium/cilium/issues/13833#issuecomment-757166485): https://jenkins.cilium.io/job/Cilium-PR-K8s-1.13-net-next/387/testReport/junit/Suite-k8s-1/13/K8sServicesTest_Bookinfo_Demo_Tests_bookinfo_demo/
30d72f45_K8sServicesTest_Bookinfo_Demo_Tests_bookinfo_demo.zip

Also hit by @jrajahalme in #14370 (also see https://github.com/cilium/cilium/issues/13833#issuecomment-757166485): https://jenkins.cilium.io/job/Cilium-PR-K8s-1.13-net-next/387/testReport/junit/Suite-k8s-1/13/K8sServicesTest_Bookinfo_Demo_Tests_bookinfo_demo/
30d72f45_K8sServicesTest_Bookinfo_Demo_Tests_bookinfo_demo.zip

Similar variant hit with K8sIstioTest Istio Bookinfo Demo Tests bookinfo inter-service connectivity in https://github.com/cilium/cilium/pull/16672.
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.21-kernel-4.9/878/

Similar variant hit in #16774:
13:43:02  [[ATTACHMENT|f3269436_K8sKafkaPolicyTest_Kafka_Policy_Tests_KafkaPolicies.zip]]
13:43:02  11:43:02 STEP: Running AfterAll block for EntireTestsuite K8sKafkaPolicyTest
13:43:02  11:43:02 STEP: Removing Cilium installation using generated helm manifest
13:43:02
13:43:02  • Failure in Spec Setup (BeforeEach) [513.543 seconds]
13:43:02  K8sKafkaPolicyTest
13:43:02  /home/jenkins/workspace/Cilium-PR-K8s-1.17-kernel-4.9/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:482
13:43:02    Kafka Policy Tests
13:43:02    /home/jenkins/workspace/Cilium-PR-K8s-1.17-kernel-4.9/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:482
13:43:02      KafkaPolicies [BeforeEach]
13:43:02      /home/jenkins/workspace/Cilium-PR-K8s-1.17-kernel-4.9/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:518
13:43:02
13:43:02      DNS entry of kafka-service is not ready after timeout
[2021-07-06T11:43:02.898Z]     Expected
[2021-07-06T11:43:02.898Z]         <*errors.errorString | 0xc0002a8750>: {
[2021-07-06T11:43:02.898Z]             s: "DNS 'kafka-service.default.svc.cluster.local' is not ready after timeout: 7m0s timeout expired",
[2021-07-06T11:43:02.898Z]         }
[2021-07-06T11:43:02.898Z]     to be nil
13:43:02
13:43:02      /home/jenkins/workspace/Cilium-PR-K8s-1.17-kernel-4.9/src/github.com/cilium/cilium/test/k8sT/KafkaPolicies.go:141

and
13:45:26  K8sHubbleTest
13:45:26  /home/jenkins/workspace/Cilium-PR-K8s-1.17-kernel-4.9/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:482
13:45:26    Hubble Observe
13:45:26    /home/jenkins/workspace/Cilium-PR-K8s-1.17-kernel-4.9/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:482
13:45:26      Test FQDN Policy with Relay [It]
13:45:26      /home/jenkins/workspace/Cilium-PR-K8s-1.17-kernel-4.9/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:518
13:45:26
13:45:26      "app2-5cc5d58844-wjbzt" cannot curl fqdn target "vagrant-cache.ci.cilium.io"
[2021-07-06T11:45:26.341Z]     Expected command: kubectl exec -n<PHONE_NUMBER>44k8shubbletesthubbleobservetestl3l4flow app2-5cc5d58844-wjbzt -- curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 20 http://vagrant-cache.ci.cilium.io -w "time-> DNS: '%{time_namelookup}(%{remote_ip})', Connect: '%{time_connect}',Transfer '%{time_starttransfer}', total '%{time_total}'"
[2021-07-06T11:45:26.341Z]     To succeed, but it failed:
[2021-07-06T11:45:26.341Z]     Exitcode: 28
[2021-07-06T11:45:26.341Z]     Err: exit status 28
[2021-07-06T11:45:26.341Z]     Stdout:
[2021-07-06T11:45:26.341Z]      	 time-> DNS: '0.000000()', Connect: '0.000000',Transfer '0.000000', total '5.008592'
[2021-07-06T11:45:26.341Z]     Stderr:
[2021-07-06T11:45:26.341Z]      	 command terminated with exit code 28
[2021-07-06T11:45:26.341Z]
[2021-07-06T11:45:26.341Z]
13:45:26
13:45:26      /home/jenkins/workspace/Cilium-PR-K8s-1.17-kernel-4.9/src/github.com/cilium/cilium/test/k8sT/hubble.go:291

Test run: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.17-kernel-4.9/267/
f3269436_K8sKafkaPolicyTest_Kafka_Policy_Tests_KafkaPolicies.zip
92854bf0_K8sHubbleTest_Hubble_Observe_Test_FQDN_Policy_with_Relay.zip
Github refuses to accept the test results zip file.

This last report is another case of https://github.com/cilium/cilium/issues/16717#issuecomment-871748370. The original report in this issue wasn't. Given the timings, I suspect the report by Chris was also https://github.com/cilium/cilium/issues/16717#issuecomment-871748370.

Hit again in #16801, but for deathstar:
DNS entry is not ready after timeout
Expected
    <*errors.errorString | 0xc002b805d0>: {
        s: "DNS 'deathstar.default.svc.cluster.local' is not ready after timeout: 7m0s timeout expired",
    }
to be nil

service exists:
        {
            "apiVersion": "v1",
            "kind": "Service",
            "metadata": {
                "annotations": {
                    "kubectl.kubernetes.io/last-applied-configuration": "{\"apiVersion\":\"v1\",\"kind\":\"Service\",\"metadata\":{\"annotations\":{},\"name\":\"deathstar\",\"namespace\":\"default\"},\"spec\":{\"ports\":[{\"port\":80}],\"selector\":{\"class\":\"deathstar\",\"org\":\"empire\"},\"type\":\"ClusterIP\"}}\n"
                },
                "creationTimestamp": "2021-07-09T07:56:18Z",
                "name": "deathstar",
                "namespace": "default",
                "resourceVersion": "29806",
                "uid": "012ad11a-01bd-4e45-ac68-23e8925748c5"
            },
            "spec": {
                "clusterIP": "<IP_ADDRESS>",
                "clusterIPs": [
                    "<IP_ADDRESS>"
                ],
                "ipFamilies": [
                    "IPv4"
                ],
                "ipFamilyPolicy": "SingleStack",
                "ports": [
                    {
                        "port": 80,
                        "protocol": "TCP",
                        "targetPort": 80
                    }
                ],
                "selector": {
                    "class": "deathstar",
                    "org": "empire"
                },
                "sessionAffinity": "None",
                "type": "ClusterIP"
            },
            "status": {
                "loadBalancer": {}
            }
        },

So kube-dns should return the clusterIP <IP_ADDRESS> but apparently it does not.

@jrajahalme Do you have a link to the Jenkins build and maybe the artifact?

@pchaigno https://jenkins.cilium.io/job/Cilium-PR-K8s-1.21-kernel-4.9/1035/testReport/Suite-k8s-1/21/K8sKafkaPolicyTest_Kafka_Policy_Tests_KafkaPolicies/
15430c59_K8sKafkaPolicyTest_Kafka_Policy_Tests_KafkaPolicies.zip

kafka-service has no ClusterIP after 7+ minutes:
NAMESPACE           NAME            TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE     SELECTOR
cilium-monitoring   grafana         ClusterIP   <IP_ADDRESS>    <none>        3000/TCP                 58m     app=grafana
cilium-monitoring   prometheus      ClusterIP   <IP_ADDRESS>   <none>        9090/TCP                 58m     app=prometheus
default             kafka-service   ClusterIP   None            <none>        9092/TCP                 7m38s   app=kafka
default             kubernetes      ClusterIP   <IP_ADDRESS>       <none>        443/TCP                  52m     <none>
kube-system         kube-dns        ClusterIP   <IP_ADDRESS>      <none>        53/UDP,53/TCP,9153/TCP   61m     k8s-app=kube-dns

app=kafka POD is up:
	 532        Disabled           Disabled          2025       k8s:app=kafka                                                            fd02::1e5   <IP_ADDRESS>    ready
	                                                            k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=kafkaTestApp

kafka-service has no ClusterIP after 7+ minutes:

This would be expected, ClusterIP: None in spec designates headless service. So the service spec is OK, butt kube-dns should respond with backend POD IPs, which did not happen in this case.
Also unsure if cilium service list should show headless services or not (it is not showing anything for kafka-service in this case).

@pchaigno https://jenkins.cilium.io/job/Cilium-PR-K8s-1.21-kernel-4.9/1035/testReport/Suite-k8s-1/21/K8sKafkaPolicyTest_Kafka_Policy_Tests_KafkaPolicies/
15430c59_K8sKafkaPolicyTest_Kafka_Policy_Tests_KafkaPolicies.zip

Checking the iptables drops shows it's another case of https://github.com/cilium/cilium/issues/16717#issuecomment-871748370. The fix for that flake was merged this morning so rebasing should catch it :-)

Hit similar issue https://github.com/cilium/cilium/issues/17350 on net-next. From the kubectl get svc output I can clearly see that the svc has been provisioned, but the following is failing:
cmd: "kubectl exec -n kube-system log-gatherer-f5xst -- dig +short deathstar.default.svc.cluster.local @<IP_ADDRESS>" exitCode: 0 duration: 245.284621ms stdout:

time="2021-09-07T11:48:45Z" level=debug msg="output of dig () did not return an IP" serviceName=deathstar serviceNamespace=default

Unfortunately, the hubble relay logs are empty. So it's not clear what happened with the DNS request. Also, I don't see any CT entry for log-gatherer -> any coredns POD (ack <IP_ADDRESS> cilium-bpf-ct-list-global.md | grep ':53 '; socket LB is used).
flake.zip

OK, I was wrong that the hubble logs were empty ^^ (was confused by the empty hubble-relay file). Anyway:
time="2021-09-07T11:41:45Z" level=debug msg="running command: kubectl -n default get service deathstar -o json"
cmd: "kubectl -n default get service deathstar -o json" exitCode: 0 duration: 52.447837ms stdout:
{
    "apiVersion": "v1",
    "kind": "Service",
    "metadata": {
        "annotations": {
            "kubectl.kubernetes.io/last-applied-configuration": "{\"apiVersion\":\"v1\",\"kind\":\"Service\",\"metadata\":{\"annotations\":{},\"name\":\"deathstar\",\"namespace\":\"default\"},\"spec\":{\"ports\":[{\"port\":80}],\"selector\":{\"class\":\"deathstar\",\"org\":\"empire\"},\"type\":\"ClusterIP\"}}\n"
        },
        "creationTimestamp": "2021-09-07T11:41:39Z",
        "name": "deathstar",
        "namespace": "default",
        "resourceVersion": "41711",
        "selfLink": "/api/v1/namespaces/default/services/deathstar",
        "uid": "5cb7bab8-d0b7-4667-bae2-217da5f89051"
    },
    "spec": {
        "clusterIP": "<IP_ADDRESS>",
        "ports": [
            {
                "port": 80,
                "protocol": "TCP",
                "targetPort": 80
            }
        ],
        "selector": {
            "class": "deathstar",
            "org": "empire"
        },
        "sessionAffinity": "None",
        "type": "ClusterIP"
    },
    "status": {
        "loadBalancer": {}
    }
}
time="2021-09-07T11:41:45Z" level=debug msg="running command: kubectl exec -n kube-system log-gatherer-f5xst -- dig +short deathstar.default.svc.cluster.local @<IP_ADDRESS>"
cmd: "kubectl exec -n kube-system log-gatherer-f5xst -- dig +short deathstar.default.svc.cluster.local @<IP_ADDRESS>" exitCode: 0 duration: 161.149686ms stdout:

time="2021-09-07T11:41:45Z" level=debug msg="output of dig () did not return an IP" serviceName=deathstar serviceNamespace=default

and the relavant Hubble flow:
{
  "flow": {
    "time": "2021-09-07T11:41:45.773943509Z",
    "verdict": "FORWARDED",
    "ethernet": {
      "source": "6a:8d:dc:a6:d8:5a",
      "destination": "7e:53:ff:ae:2a:41"
    },
    "IP": {
      "source": "<IP_ADDRESS>",
      "destination": "<IP_ADDRESS>",
      "ipVersion": "IPv4"
    },
    "l4": {
      "UDP": {
        "source_port": 58099,
        "destination_port": 53
      }
    },
    "source": {
      "identity": 6,
      "labels": [
        "reserved:remote-node"
      ]
    },
    "destination": {
      "identity": 28560,
      "namespace": "kube-system",
      "labels": [
        "k8s:io.cilium.k8s.policy.cluster=default",
        "k8s:io.cilium.k8s.policy.serviceaccount=coredns",
        "k8s:io.kubernetes.pod.namespace=kube-system",
        "k8s:k8s-app=kube-dns"
      ],
      "pod_name": "coredns-5495c8f48d-h94cf"
    },
    "Type": "L3_L4",
    "node_name": "k8s1",
    "event_type": {
      "type": 4,
      "sub_type": 4
    },
    "trace_observation_point": "TO_OVERLAY",
    "interface": {
      "index": 390,
      "name": "cilium_vxlan"
    },
    "Summary": "UDP"
  },
  "node_name": "k8s1",
  "time": "2021-09-07T11:41:45.773943509Z"
}

Meanwhile in pod-kube-system-coredns-5495c8f48d-h94cf-coredns.log:
2021-09-07T11:41:45.827754260Z 2021-09-07T11:41:45.827Z [INFO] <IP_ADDRESS>:58099 - 41796 "A IN deathstar.default.svc.cluster.local. udp 76 false 4096" NXDOMAIN qr,aa,rd 146 0.000303615s

The question is why it's NXDOMAIN?

Yet another instance, but this time:
/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:465
DNS entry of kafka-service is not ready after timeout
Expected
    <*errors.errorString | 0xc00177c930>: {
        s: "DNS 'kafka-service.default.svc.cluster.local' is not ready after timeout: 7m0s timeout expired",
    }
to be nil
/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test/k8sT/KafkaPolicies.go:121

https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/1448/testReport/junit/Suite-k8s-1/16/K8sKafkaPolicyTest_Kafka_Policy_Tests_KafkaPolicies/
Same symptoms:
2021-09-15T16:27:15.084437262Z 2021-09-15T16:27:15.084Z [INFO] <IP_ADDRESS>:44790 - 60739 "A IN kafka-service.default.svc.cluster.local. udp 80 false 4096" NXDOMAIN qr,aa,rd 150 0.000162242s


where can i find the plugins using document of konga

where can i find the plugins using document of konga,such about trafic policy plugins

you can see the plugins available in kong in the INFO menu of konga and when yo select a service or a route in the PLUGINS menu


Avoid a very expensive clone in compute_block_importances

This clone, which was introduced in #1871,
was responsible for 40% of allocations
within rav1e. Although counterintuitive,
removing the frame data from the map
and reinserting it at the end of the iteration
is better because it avoids this clone.
Gives about a 4% speedup over master
with 1 tile on 720p test clip.

Coverage increased (+0.003%) to 75.634% when pulling 65ff381b3b063fd435500afa33ffe06e4d7a5b50 on shssoichiro:revert-fi-cloning into b3d0c06772ed12d990f20bb6bb900df1d79b9581 on xiph:master.


Unable to upload the IPA File | App Distribution halted  | APK is not zip aligned | CI Blocked

Issue Description
Unable to upload the IPA file to Firebase distribution when I am passing the values through Fastlane Environment variables
Configuration
firebase_app_distribution(
          app: ENV["FIREBASE_APP_ID"],
          firebase_cli_token: ENV["FIREBASE_CLI_TOKEN"],
        )

This works when i pass the values directly and only happens in case of android.
Complete verbose output
...
.........
[12:02:05]: Successfully exported and compressed dSYM file
[12:02:05]: Successfully exported and signed the ipa file:
[12:02:05]: /Users/mac/workspace/test/builds/Test.ipa
[12:02:05]: ---------------------------------------
[12:02:05]: --- Step: firebase_app_distribution ---
[12:02:05]: ---------------------------------------
[12:02:05]: Authenticating with --firebase_cli_token parameter
[12:02:06]: 🔐 Authenticated successfully.
[12:02:08]: ⌛ Uploading the IPA.
+------------------------------------+-------------------------------------------------------------------------------+
|                                                    Lane Context                                                    |
+------------------------------------+-------------------------------------------------------------------------------+
| PLATFORM_NAME                      | ios                                                                           |
| LANE_NAME                          | ios distribute                                                                |
| SIGH_PROFILE_TYPE                  | ad-hoc                                                                        |
| MATCH_PROVISIONING_PROFILE_MAPPING | {"com.test.abc"=>"match AdHoc                              |
|                                    | com.test.abc"}                                             |
| IPA_OUTPUT_PATH                    | /Users/mac/workspace/test/builds/Test.ipa          |
| XCODEBUILD_ARCHIVE                 | /Users/mac/Library/Developer/Xcode/Archives/2021-07-04/Test    |
|                                    | 2021-07-04 11.49.22.xcarchive                                                 |
| DSYM_OUTPUT_PATH                   | /Users/mac/workspace/test/builds/Test.app.dSYM.zip |
+------------------------------------+-------------------------------------------------------------------------------+
[12:02:21]: App Distribution halted because it had a problem uploading the IPA: There's been an error processing your app because of an archiving issue. Use zipalign in your build process and try again. Learn more at https://developer.android.com/studio/command-line/zipalign If this problem continues, contact Firebase support.
Additional information about this error:
APK is not zip aligned.

+------+---------------------------+-------------+
|                fastlane summary                |
+------+---------------------------+-------------+
| Step | Action                    | Time (in s) |
+------+---------------------------+-------------+
| 1    | load_json                 | 0           |
| 2    | match                     | 4           |
| 3    | gym                       | 768         |
| 💥   | firebase_app_distribution | 16          |
+------+---------------------------+-------------+

[12:02:21]: fastlane finished with errors

[!] App Distribution halted because it had a problem uploading the IPA: There's been an error processing your app because of an archiving issue. Use zipalign in your build process and try again. Learn more at https://developer.android.com/studio/command-line/zipalign If this problem continues, contact Firebase support.
Additional information about this error:
APK is not zip aligned.

Environment
fastlane-plugin-firebase_app_distribution (0.2.9)

Library
Version

fastlane
2.187.0

fastlane-plugin-firebase_app_distribution
0.2.9

ruby
ruby 2.7.3p183 (2021-04-05 revision 6847ee089d) [x86_64-darwin20]

Update

Opened the support ticket with Firebase support as well.

What did you do to fix it? @shrmaky

@KryptKode - actually i was not sending correct firebase appid.
For android app i was setting ios app id, and I understand that this error is misleading.

Thanks, @shrmaky. It worked. 🎉

@shrmaky I did the same mistake. thanks a lot.


Add makeshift baker

Can you post instructions for use here so I can set it up in the wiki?
Thanks.

Here are the instructions:
Terrain3D does not yet have a proper implementation for navmeshing and colliders. However, there is a workaround solution- a multithreaded navigation baker that will bake the entire terrain at once. Here's how to use it:

Create a ChunkBaker node, and place all of the geometry you want to be included in the bake as children underneath it, like you would a regular NavigationRegion3D. This includes the terrain you wish to bake.
Provide a template navmesh resource. Set it up as you would any conventional bake, apart from a few settings:

In Geometry > Parsed Geometry Type, select Static Colliders or Both.
In Filters > Baking AABB, change the w, h, and d values to select the size of the chunks that will be baked. Only the w and d values matter, but the h value should be tall enough to encompass the entire height of your terrain. The larger the chunk size, the more time it will take for each chunk to bake, but longer each chunk will take. A good starting point is (64, 512, 64).

Provide the rest of the settings.

Bake Path: This is the folder where it will dump the baked navmesh once complete.
Terrain: This a reference to the terrain node you want to bake.
Bake Region: This is the region (Large square you can add in the terrain menu) you want to bake, referred to by index. -1 will bake all regions. Index 0 is the center.
Pretty Print: Bake progress will be printed in a fancy way into the output as the bake progresses. Godot will rarely be running smooth enough to watch this go by in-editor, however, so if you want to save the processing time required to print, you can safely turn it off.

Hit the "Bake terrain navigation" button at the top. Godot will freeze for a bit as the scene geometry is parsed on the main thread. Then, your computer will become barely usable for a few minutes, as all cores will be maxed to get the bake done as soon as possible. On an 8 core Ryzen 7 5800X, one region of high complexity took 30 seconds to a minute. Each region is done sequentially, so bake time scales linearly with regions. Godot will become unstable during the bake.
Once the bake is finished, It has created a resource file in your bake path. This is a large bundle of the navmeshes your chunks have created. There is no need to include this in an exported game.
Create a NavmeshBundleUnpacker node in your scene, It requires one resource: the bundle you just created. Assign it to the node, and hit "Unpack". After some time, you will find it has created a small army of NavigationRegion3Ds, each corresponding to a baked chunk. Your terrain navmesh is now in the scene. You bundle is no longer necessary to keep, if you don't want to.

The baking process is now complete. Congrats!

Superseded by #253 which has been merged. Thanks for the initial work. I'll credit you both in the release notes.

Good, nobody has to use it anymore.


Brazilian emergency and public utilities numbers are invalid

Imported from Google Code issue #377 created by fabiojmendes on 2013-11-13T18:09:39.000Z:

What steps will reproduce the problem?
Here are the test cases:
@Test
public void testEmergency() throws Exception {
    PhoneNumberUtil phoneUtil = PhoneNumberUtil.getInstance();
    //190 in brazil is equivalent to EUA's 911
    PhoneNumber phone = phoneUtil.parse("190", "BR");
    assertTrue(phoneUtil.isValidNumber(phone)); //fails
}

@Test
public void testPublicServices() throws Exception {
    PhoneNumberUtil phoneUtil = PhoneNumberUtil.getInstance();
    //Directory assistance
    PhoneNumber phone = phoneUtil.parse("102", "BR");
    assertTrue(phoneUtil.isValidNumber(phone)); //fails
}

@Test
public void testServiceProviderNumber() throws Exception {
    PhoneNumberUtil phoneUtil = PhoneNumberUtil.getInstance();
    //Cable TV service provider
    PhoneNumber phone = phoneUtil.parse("10621", "BR");
    assertTrue(phoneUtil.isValidNumber(phone)); //fails
}

What is the expected output? What do you see instead?
A valid number
What version of the product are you using? On what operating system?
libphonenumber 5.8
Java JDK 1.7_45
Please provide any additional information below.
Here is the document that list all the emergency and public utilities numbers:
http://www.anatel.gov.br/Portal/exibirPortalPaginaEspecial.do?codItemCanal=746&codCanal=277
I think its something like 1\d{2,3} for the basic ones and 10[356]\d{1,2} for the ones with a possible extension.
I dont fell confident to contribute to the metadata just yet but I'll try.
Nevertheless, I'll be happy to help testing and translating the document I just linked.

Fixed meanwhile.

Except 102 :)

We've accepted this issue and will fix it in an upcoming release.

Fixed meanwhile.


add persistent volume in chart

Add possibility to use persistent volume with this chart

I close this PR because a lot change occured since the last fork


Is there a way to disable the authorization step (sign in/log in) on label-studio?

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Given that label-studio is deployed on a containerized environment like kubernetes,
It's not hard to imagine that one may already be authorized by container orchestrator or another pod to access label-studio pod.
Therefore, additional log in on label-studio is no longer needed
(only one person or an approved group can access the label-studio pod)
Describe the solution you'd like
A clear and concise description of what you want to happen.
In that case, Can we disable authorization process in the current label-studio?
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Disable authorization in server start with a flag
Additional context
Add any other context or screenshots about the feature request here.

This would be very useful for my use case, as well: I want to use label-studio in a docker-compose environment where all endpoints are already protected with basic-auth, so the login is redundant. I also want to automatically create a user, project and task. The way it works right now, I see no way to do this, since I need to manually create a first user and login to get my auth token before I can use the HTTP API.
I'd really like a way to fully disable auth, both for login and API calls.

@coldtomatojuice

Can we disable authorization process in the current label-studio?

How do you distinguish annotators if there is no auth? Who performed the annotation A and who performed the annotation B?
@salmenf
You can create a user using this command line call:
https://labelstud.io/guide/signup.html?from_search=create user#Create-an-account
Also you can create a project and a task via API:
https://api.labelstud.io/#operation/api_projects_create
https://api.labelstud.io/#operation/api_tasks_create
The bottleneck is the login, yes. Maybe we have to implement it via token, something like:
http://localhost:8080/user/login?user_token=<token>

@makseq
Thanks for the tips! Exactly, the login is the issue, some automatic login via HTTP would be great!
I don't think your suggestion works in my case, though, if I'm understanding it right: If I can login only via token, how do I get the token automatically (without the UI)? There's this API method (https://labelstud.io/api#operation/api_current-user_token_list), but it requires a token to get the token. Rather, I'd need to login via username and password to be able to get the token with the API method.

how do I get the token automatically (without the UI)

check this branch please: https://github.com/heartexlabs/label-studio/pull/1065

Excellent, thanks! That branch and the login via token would solve my use case completely.


Fix build with clang-{10,11}

Newer clang versions report several "Wimplicit-int-float-conversion"
warnings. In this commit, implicit int-to-float conversions are turned
into explicit static_casts in local code; violations in third-party
headers are suppressed by compiler pragma.

Sorry about that. I thought the second CI check simply isn't working as it runs on internal domain, now after a fix I see its actually green :)
I realized the previous approach is maybe to complicated given the driver is in maintenance mode, so I decided to just add this kind of warning to the list of disabled warnings for clang.

Thanks!


An idea for the "plugin" approach - use repo2docker config files

One thought - what if we tried to completely co-opt the "repo2docker" config file structure. E.g. repo2docker goes from repository -> Dockerfile -> image. This tool could look for the same repository files (except for a Dockerfile) and install the environment specified in it. That way we're not telling people to use a new pattern of interaction. You could do tljh-config install path_to_repo or something?

I agree! I think it should be a plugin itself rather than be part of tljh cor.e


docs: update  CriEnabled field in the doc of deploy kubernetes with PouchContainer

Ⅰ. Describe what this PR did
update  CriEnabled field in the doc of deploy kubernetes with PouchContainer
Ⅱ. Does this pull request fix one issue?

fixes #2381
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@hellolijj could you please to sign the CLA? thanks

In the cli code of info command, there is code:
	fmt.Fprintln(os.Stdout, "LxcfsEnabled: ", info.LxcfsEnabled)
	fmt.Fprintln(os.Stdout, "CriEnabled: ", info.CriEnabled)
	if info.RegistryConfig != nil && (len(info.RegistryConfig.InsecureRegistryCIDRs) > 0 || len(info.RegistryConfig.IndexConfigs) > 0) {
		fmt.Fprintln(os.Stdout, "Insecure Registries: ")

In which there is CriEnabled rather than IsCRIEnabled . So LGTM

It is the documentation update. And the doc CI passes. So merging.
Thanks @hellolijj  for your contribution. And congratulations to be a PouchContainer contributor.


Add whitelist to CLI

It would be interesting to launch purifycss with whitelist from the CLI. For example:
purifycss src/css/main.css src/css/bootstrap.css src/js/main.js --whitelist button-active *modal* --out src/dist/index.css

Yes, please. When is this feature coming into CLI?

I think this issue can be closed now.

Perfect!

And for those who are wondering how whitelisting with multiple classes works: Here's an more complex example ;-)
´´´
purifycss "./dist//styles.*.css" "./src/index.html" "./src/app//.ts" "./src/app/**/.html" --min --info --rejected --whitelist body* sg-select sg-icon sg-flyout sg-pagination sg-toast sg-image-cropper cdk- sg-button sg-checkbox sg-input sg-form-field sg-file-loader sg-user-img transition dimmer --out "./dist/"
´´´


Fix issue with public state

Fixes issue with maintaining and showing the public state when you update the user account info.

@HadleyKing will leave for you to merge when you are ready; I'm going to stop committing to this MR.


added ads.txt

Description

Related Issues

🔮 Deploy Preview for melvinvivas canceled.
🔨 Explore the source changes: 4875080e8df7bce0df5f7a331ddab1637c450f0b
🔍 Inspect the deploy log: https://app.netlify.com/sites/melvinvivas/deploys/611ba252a6752b0008899c7e


Flexbox bug with brand padding

Original writeup: https://github.com/intuit/Ignite/pull/66#issuecomment-423918705

Ok so an update, I think I've narrowed it down, and AFAICT it's a bug related to the fallback display property on .navbar-item. This was happening on master as well, so it's not something I introduced in this branch. It's just more noticeable on this branch because of the element changes (which reduce padding slightly).
The easiest way to repro is to:
Open dev tools on the side of the window
Shrink the viewport slightly larger than the 768 breakpoint
Close dev tools
Reopen dev tools
And the issue is present. As soon as you reload the page, it resolves. Here's what it looks like happening in real time on this branch:

And this is what is looks like happening on the master branch

It's up to you whether or not you want to proceed with merging this. I'm going to open up a separate issue for this problem.

I have a strong hunch that the issue has to do with the webkit fallback settings on the display property of the .navbar-item class.

Specifically, the -webkit-box. The reason for that hunch, is, when loading the window, the navbar-item is 123.16px wide and during the bug the width is 105.69px. After reloading the page to reset the width back to 123.16px, if you disable the css declaration display: flex (which activates the fallback, display: -webkit-box, the width drops down to 105.69px, the same width that's present during the above bug.
But unlike when the bug is present, when that fallback is activated the spacing between the logo and the header is reduced, so the padding is shrinking proportionately

This issue is almost like the fallback declaration is getting combined with the display: flex declaration. Super weird stuff. It's worth investigating whether this is a bug present in bulma or if it's something specifically with the styles defined in Ignite. The navbar is using hardly any custom styles and is basically stock bulma.

Let me look into this, please assign this to me.

Hey @hipstersmoothie, I have raised PR for the fix here #106
Please review.


Add library MoviebaseApp/trakt-api to README

Add the new Kotlin library to the README.
https://github.com/MoviebaseApp/trakt-api

Thank you @rectifyer! 🙂


Document Antrea public interfaces

We should publish (on antrea.io) auto-generated documentation for Antrea's public interfaces.
These public interfaces include:

CRDs (NetworkPolicies, Traceflow, ...)
APIServices other than controlplane, which is meant to be consumed internally by Antrea; since integrated solutions may want to consume controlplane as well, it could be a good idea to generate the documentation for it as well, potentially with a disclaimer that this is not considered a public API (in particular, when it comes to the deprecation policy)

This is part of the effort to obtain a passing CII best practices badge: https://github.com/vmware-tanzu/antrea/issues/989
Ideally, the auto-generated documentation should look like the one for the K8s API: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.19/
Some suggestions on how to generate the documentation:

follow the K8s model: generate the OpenAPI spec (for K8s: https://github.com/kubernetes/kubernetes/blob/master/api/openapi-spec/swagger.json, which is generated by https://github.com/kubernetes/kubernetes/blob/master/hack/update-openapi-spec.sh) and from there generate the web documentation for K8s: https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-apidocs)
use a 3rd party project, https://github.com/ahmetb/gen-crd-api-reference-docs, which is used by other projects in the K8s ecosystem, e.g. Knative, cert-manager

The 1st solution requires running a K8s apiserver and connecting to it to retrieve the OpenAPI specs. It requires a complete validation schema for all the Antrea CRDs, which we do not have yet (but the plan is to reach that milestone by 0.11). I haven't looked at how it would work for APIServices. My guess would be that we would need to run the Antrea apiserver as well (so essentially we would need to deploy Antrea in a K8s cluster, just for the sake of generating the documentation...) and retrieve the OpenAPI specs through the aggregation layer. Not 100% sure what else would be needed for the OpenAPI specs to be served correcly.
The 2nd solution should work well for all the Antrea APIs. It may not be as flexible as generating a full-fledged OpenAPI spec (like swagger.json for K8s) but it could be a good place to start. gen-crd-api-reference-docs generates a HTML file for each API group, that we can add to the antrea.io website (it will pick up the CSS from the website). My plan is to prototype this solution first. The only issue is that gen-crd-api-reference-docs does not seem very well documented.

Submitted a PR to add a wrapper script around gen-crd-api-reference-docs: https://github.com/vmware-tanzu/antrea/pull/1507
The generated API reference doc is already available on the Antrea website: https://antrea.io/docs/master/api-reference/. I see some room for improvement, in particular I don't think we have quite enough comments in the Go source.


Technical Documentation ???

I saw the youtube video for the application it's pretty neat. Great job!
Can you please tell very briefly a line or two what programming language you are using ?
What the over all tech stack looks like ? Can plugins be written for this application ?

Thanks for your kind words @sheecegardezi :)
I use Flutter toolkit which is based on Dart language. Flutter is very good tool to create apps which would work on multiple platforms. Linux support is still in alpha stage though.
In July, Google and Canonical released blog post about collaboration so developers can create snap versions of their Flutter apps.
Accidentally I started to learn Flutter about that time and, as I use Ubuntu, I decided to create few basic apps as a way to learn. One of the apps is this one. It was supposed to be a rather simple so I never though about providing a way to write plugins for it. I plan to add some more features but I don't think it will become something very advanced.


[PHP 8.4] Fixes for implicit nullability deprecation

Fixes all issues that emit deprecation notices on PHP 8.4 for implicit nullable parameter type declarations.
See:

RFC
PHP 8.4: Implicitly nullable parameter declarations deprecated

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
N/A

Thanks for contributing. Is that a backwards compatibility break for the case of inheritance?

Hi @samdark , thanks for the response.
Both string $v = null and ?string $v = null are considered "nullable" for inheritance, so yes, this is not a BC break.
However I just realized Yii also has to support PHP 5.4 through 7.0 as well, which have no nullable type support, so this change is breaking on those versions.

I will close this PR because we can not merge this as-is unless we either bump the minimum version to 7.1 (or drop these type declaration).

You can target the pull request for 2.2 branch which is PHP8+

Thank you! I rebased for 2.2.

@samdark AFAIK we had plans to increase min PHP version in v2.0.50 to 7.3. Something changed in that matter? If not, we could still merge this PR to master.

Won't this be a BC break anyway because of signature mismatch?

Quite fortunately it's not a BC break. If there any sub classes extending our classes, they will need the nullability fix to avoid the deprecation, but they will still be compatible.

https://3v4l.org/i7dQn#v7.3.33

Could go into master then. @Ayesh sorry to ask but could you rebase it back? :)

No problemo, I opened #20133 separately targeting master branch. It will fail because it still builds on PHP <= 7.0, but contains all places I found to trigger the deprecation notice.

Closing since it will be merged from master into 2.2.


126.client negotiated permissions hashcash

This is a combination of the "hybrid approach" and "client-decides negotiation", as per #11 discussion.

This already looks a lot better (but expect some bike shedding once it's marked ready for review).

Although it some cases it might be more work for the server

I've thought about this as well. The point is: challenges need to be cheap to create and to verify, independently of the number of supported methods. Otherwise the server would open a pre-verification DOS attack vector that we absolutely don't want (getting DOSed using DOS prevention, lol).
Regarding the choice options from a server perspective, they can:

Choose which methods they provide
Choose the parameters on how difficult they are
Kind of choose which answers are accepted (there is always the possibility to veto and error out)

Yeah, I think all that sounds reasonable.
The thing the server is "losing" by not being the final chooser is that it might be in a better position to know which method will give the client the best experience .. but also that's pretty ill-defined, and anyway the client could also be taught when to choose which option (instead).
So, I think privacy wins out here and we should paint this bikeshed instead of the other bikesheds currently being erected ;)
I'll clean up the text a bit more and then un-Draft the PR so we can decide the colours.
If @warner has time / inclination it would be great to get input from him since some of this is at least based off designs we'd discussed together.

Looks great to me.

I think something like "permission" fits the best. Should we converge on "Usage permission" or so..? (And yeah should probably drop "abilities" since that was kind of specific to the "server chooses" design).

I filed https://github.com/magic-wormhole/magic-wormhole-protocols/issues/13 regarding releases.

okay, thanks for the review and suggestions. I've commited them all .. is this now just waiting for #13 / v1.0 before merging...?

Yeah, having some more time for additional input would be good

@warner any input?

FCP is over. Thank you Warner for giving valuable input. The remaining discussion points need to be addressed before this can be merged. Unless major changes are made to the proposal, there won't be another FCP period before merging.

https://github.com/magic-wormhole/magic-wormhole-protocols/pull/12/commits/ecd02caadc9d873aaca7a08882eb3831c3c17296 re-words things to have a separate submit-permissions message.

Weird, I can't "reply" to your last comment (about TLS) .. you mean expand on warner's text to include any method, not just "bearer-token"?
I mean, it's still up to server-operators to assess their threat-model etc but really all connections should just be TLS because there's no downside to that that I can see...

p.s. I did proof-of-concept level implementations of this spec in the server and client to make sure it makes sense and actually-works :)

Weird, I can't "reply" to your last comment (about TLS)

Yes, GitHub is really awkward when it comes to adding comments to existing discussions within a review. If you want answer, you have to unfold the initial discussion point by Warner on this.

Generally, this looks really good as it is now. Please squash all the commits into one and give it a good commit message (including references to both the issue and the pull request, but also enough information to be useful alone). I'll then do a (hopefully) final re-read of the whole file before merging.

Please squash all the commits into one

I did this .. but I personally find keeping things un-squashed / edited serves future-me best (note too that there is an opportunity for you to summarize differently if you want in the merge-commti to main)

Thank you for the contribution and your persistence on it.

but I personally find keeping things un-squashed / edited serves future-me best

Adding commits as they go is really useful for reviewing, but I like to keep some semantic to them in the end. I don't mind having multiple commits + merge commit per se, but I don't think back-and-forth changes and typo fixes are worth keeping.

I suppose the "worth keeping" bit comes down to why future-me/us looks back at individual commits on a branch. I used to aggressively rebase/squash branch history but found that a common reason I looked down an old branch's history was to figure out what happened, why things changed (e.g. if I remember writing something a different way).
Anyway, probably way less useful on a "mostly text" PR like this (as you point out), just trying to justify my opinion ;)


TODO list for porting from Windows to Linux

Below a list of all Windows specific system calls. In parenthesis the likely replacement in terms of Standard C++ or Linux specific system calls. A checked box means that the replacement has been tested. Memory and File I/O can be tested on Windows under Visual Studio. The rest on Windows under MinGW or on Linux under g++.
Memory

[x] VirtualAlloc (std::aligned_alloc)
[x] VirtualFree (std::free)

File I/O

[ ] CreateFile (std::fopen)
[ ] GetFileSize (std::ftell)
[ ] SetFilePointer (std::fseek)
[ ] ReadFile (std::fread)
[ ] CloseHandle (std::fclose)

Bit twiddling

[ ] _BitScanForward  (__builtin_ctz)
[ ] _BitScanReverse (__builtin_clz)
[ ] _BitScanForward64 (__builtin_ctzll)
[ ] _BitScanReverse64 (__builtin_clzll)
[ ] __popcnt ( __builtin_popcount)
[ ] __popcnt64 ( __builtin_popcountll)

Threading

[x] InitializeCriticalSection (not used)
[x] EnterCriticalSection (not used)
[x] LeaveCriticalSection (not used)
[ ] _InterlockedExchange

System information

[ ] __cpuid
[ ] SYSTEM_INFO.dwPageSize (return 4096)
[ ] SYSTEM_INFO.dwAllocationGranularity
[ ] MEMORYSTATUS.dwAvailPhys

I think I can eliminate a few of these issues.
The 3 CriticalSection functions are #if'd out and not used. We don't need to port them.
get_page_size() is only needed for Windows because of FILE_FLAG_NO_BUFFERING. For Linux it can return 4096.

I'm not sure about AllocationGranularity. If it is trying to mimic the behavior of VirtualAlloc then the granularity can be set to 4096.

Added solutions to the table for _InterlockedExchange, __cpuid, SYSTEM_INFO.dwPageSize, and MEMORYSTATUS.dwAvailPhys

I would prefer to have a solution for _InterlockedExchange  that depends on the Standard Library header <thread>  rather than yet another platform dependent compiler intrinsic.


Implement support for enum ordering

Fix for #1833
Also updated enum error messages to return the enum name (current code just outputs *ast.TypeName inside the error string)

@kyleconroy fixed the tests (they were failing due to the version bump in main) if you are able to reapprove the worklow to rerun them?


Set default "button" in power dropdown to display the status and not be a button

The power dropdown's default view in the Linode page should be the status. The dropdown should contain all actions.

We should probably do the same for the list and grid views as well. But that can be a separate task.


What does task do?

In the example1.py
https://github.com/luciansmith/sedml-script/blob/d891645d0b3f89ff190fc7e719659c8e229c07da/example1.py#L8
task is not used.  What does it do?

As a work in progress, it was going to represent the equivalent of a SED-ML L1 'task'.  However, it looks like I never actually used tasks that way, and they instead ended up migrating to methods on 'model' objects instead.


Connect-MSCommerce - no option for passing authentication credentials

In the cmdlet Connect-MSCommerce, the only valid parameters I can see are

ClientId
RedirectUri
Resource

There is no parameter to pass credentials for sign in via scripts. This is important as we need to ensure this can be configured via automatic scripts.
How can the Connect-MSCommerce cmd be used via a script with no interactive log on? Sample script below fails
$adminuser = $env:GAUsername
$password = ConvertTo-SecureString $env:GAPassword -AsPlainText -Force

$GlobalAdmin = New-Object System.Management.Automation.PSCredential ($adminuser, $password)

Connect-MSCommerce -Credential $GlobalAdmin

Script output is
Connect-MSCommerce : A parameter cannot be found that matches parameter name 'Credential'.

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

ID: 5082f7ed-ad40-04c1-5c6c-59e67b253257
Version Independent ID: 3d8b109d-285c-952f-2fa4-9fa244c2a3f9
Content: Use AllowSelfServicePurchase for the MSCommerce PowerShell module
Content Source: microsoft-365/commerce/subscriptions/allowselfservicepurchase-powershell.md
Service: o365-administration
GitHub Login: @cmcatee-MSFT
Microsoft Alias: cmcatee

Looking for an update - New Viva Self-service trial experience just announced for my tenant and I need to turn this off ASAP.
Standard user accounts should not have privileged access roles, we need to run this module with vaulted credentials, non-interactive.


feature extract and multi-gpu on ec2

Hello everybody,
1.
i have one folder full of images from many classes. Is it possible to train model via digits without labels. or, the labels are important for the train?  the images are not place in folders that fit to thier classes (just one folder). Now, i dont care about the classification issue becuase my goal is to get the features from the hidden layer (or other layer that will give me vector which willrepresent the image). So, how its gonna be and what are my options?
2.
I have g2.2xlarge instance on ec2 but i consider to upgrade it to the bigger g2.8xlarge . This one would work properly with digits 2.0?
Much thanks,
Yarin

@yarin05 you can use DIGITS to train a model without labels (i.e. unsupervised learning). However you need to optimise your model against a loss function. You may have a look at the auto-encoder example in Caffe but I am not sure how useful that would be for the purpose of your task. Also you might find this thread interesting, it seems like RBM support in Caffe is still work in progress.
DIGITS would be able to make good use of your g2.8xlarge as it supports multi-GPU training with Caffe.

@gheinrich thanks for answering, notice that digits block you if the folder doesnt have at least 2 subdierectories. I changed my database but still much curious for this ability with digits

If you create a classification dataset you need at least two classes. However you can provide your own LMDB image database to DIGITS in order create a generic (a.k.a. other) dataset. You can use the generic dataset to do unsupervised learning.

@yarin05 we've added several examples/walkthroughs at /examples/. Take a look and see if any of them are helpful for you.

thank you very much! i already solved my case but the examples improved my
code.
2015-12-11 21:35 GMT+02:00 Luke Yeager<EMAIL_ADDRESS>
@yarin05 https://github.com/yarin05 we've added several
examples/walkthroughs at /examples/
https://github.com/NVIDIA/DIGITS/tree/master/examples. Take a look and
see if any of them are helpful for you.
—
Reply to this email directly or view it on GitHub
https://github.com/NVIDIA/DIGITS/issues/355#issuecomment-164028815.


Uncaught (in promise) TypeError: Cannot read property 'data' of undefined     at http://localhost:8000/js/main.js:36439:51     at Array.forEach (native)     at VueComponent.getObjectValue (http://localhost:8000/js/main.js:36438:22)     at VueComponent.getObjectValue (http://localhost:8000/js/main.js:25841:27)     at VueComponent. (http://localhost:8000/js/main.js:36201:39)

@DamanDev First, check that your API endpoint does return the data.


Changeset not visualised at all, no warning of any kind appeared, no progress bar anywhere

I'm submitting a bug report.
Brief Description
Visualisation for https://osmcha.org/changesets/96926700/ failed without error.
What is the motivation / use case for this feature?
I tried to look at https://osmcha.org/changesets/96926700/ to see whatever it looks like upload after long drive across country or baseless random answers.
What  is the current behaviour, (attach relevant screenshots) ?
No visualization appeared, unlike say https://osmcha.org/changesets/96926600/

(second screen is a victim of another, already reported, bug - but at least something shows up)
What  is the expected behaviour ?
I see changed elements on a map
When does this occur ?
Always
How do we replicate the issue ?

Open https://osmcha.org/changesets/96926700/
Login with OSM account

Please tell us about your environment:
Firefox 84.0 on Ubuntu 20.04 flavor Lubuntu
Other Information / context:
https://overpass-api.de/achavi/?changeset=96926703 also failed, but with a clear error at least

@matkoniecz we had a problem on the frontend, but it's fixed now and the changeset can be visualized. Thanks for the report.

@matkoniecz we had a problem on the frontend, but it's fixed now and the changeset can be visualized. Thanks for the report.

For me it is still failing, in exactly the same way.
I tried to flush browser cache.

For me it is still failing, in exactly the same way.
I tried to flush browser cache.

Using the tag changes tab you can zoom to each feature. We'll make some improvements soon to make it easier to visualize changesets with huge bbox.

Using the tag changes tab you can zoom to each feature. We'll make some improvements soon to make it easier to visualize changesets with huge bbox.

Thanks! I hoped that at least clusters will be shown at zoomed out scale, so I would be able to judge whatever edit was based on blind guessing or is it looking like effect of surveying on a trip.

Thanks! I hoped that at least clusters will be shown at zoomed out scale, so I would be able to judge whatever edit was based on blind guessing or is it looking like effect of surveying on a trip.