Nondeterministic test TestLinksEtcHostsContentMatch

Description
The test TestLinksEtcHostsContentMatch in integration-cli/ is nondeterministic and leads to randomly failing test suites.
See the output:
FAIL: docker_cli_links_unix_test.go:20: DockerSuite.TestLinksEtcHostsContentMatch

docker_cli_links_unix_test.go:30:
    c.Errorf("container")
... Error: container

How to
Review the test implementation to make it deterministic.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

@icecrime where did you see this failing?

PR about this was merged, should this be closed @icecrime?


[GPU_UTILS] H100 specs

Without sparsity NVIDIA Hopper performance specs:

Technical Specifications
H100 SXM
H200 SXM

BFLOAT16
989.5 TFLOPS
989.5 TFLOPS

FP16
989.5 TFLOPS
989.5 TFLOPS

FP8
1979 TFLOPS
1979 TFLOPS

INT8
1979 TFLOPS
1979 TFLOPS

GPU Memory
80 GB
144 GB

GPU Memory Bandwidth
3.35 TB/s
4.8 TB/s

but this does not match tritonbench/utils/gpu_utils.py.NV_H100. Is this because this dictionary is meant to represent H100 NVL instead of SXM? Still, shouldn't we use the non-sparsity specs?. See xformers device limits.

Thanks for clarifying @xuzhao9, I tend to always use the xformers approach.

I think this is because in our CI infra (uses GCP spot instances), the GPU is H100 PCI-E. cc @adamomainz should we use the same device limit as xformers?

+1 checked it and updated the reference recently see https://github.com/pytorch-labs/tritonbench/blob/66816daabd3647f256802100eec0ed0790eae409/tritonbench/utils/gpu_utils.py#L17
Happy to use the dame device limit as xformers too

@xuzhao9 please take a look at https://github.com/pytorch-labs/tritonbench/pull/80 which should close this issue

Discrepancy has been fixed in  https://github.com/pytorch-labs/tritonbench/pull/80 please reopen if you still find an issue


Improve article 2303.10475 (mfirstuc.sty, dingbat.sty)

Exact location of issue
Article fails to convert.
Problem details
The log reveals:
Conversion complete: 2 warnings; 101 errors; 1 fatal error; 1 undefined macro[\checkmark]; 2 missing files[mfirstuc.sty, dingbat.sty]

So this article needs latexml support for those two latex packages.
DG: Edited the issue description with details. Thanks for the report!

With the latest ar5iv update, the article now gets some HTML generated, but the list of unsupported packages has increased in the latest version on arXiv:

Conversion complete: 710 warnings; 1 error; 1 undefined macro[\checkmark]; 5 missing files[dingbat.sty, inconsolata.sty, functional.sty, mfirstuc.sty, counter.sty]


Tracking internship applications

PR for #225

Checked this PR :

[ ] For duplication.
[ ] For performance.
[ ] Usage of recursive methods, loops, and algorithms.
[ ] For readability and understanding.
[ ] For functions with multiple responsibilities.
[ ] For scope of refactoring.
[ ] For coupling
[ ] For alternative approaches to the implementation.
[ ] For how the change impacts other parts of the system.
[ ] For validations. client side and server side validations are present.

For more insights on code reviews checkout our guidelines.

@bohraji Just figured you'll have to update routes/api.php as well to accommodate the current changes.
I think we should keep the route same but need to check if there are any additional parameters we need to send in the job application API request. Can you list down the modifications if there are any?
Furthermore, I don't see immediate use of Internship module until the proper API calls are set up on the website. We should be targeting that next. Thoughts?

Based on discussion with @bohraji , there are no changes required in api.php whatsoever. The existing functionality is expected to work as before.
I think it's looking good for today's build. The remaining feedbacks are small and can be targeted separately. @bohraji can you create tracking for them?


PDF in lanscape orientation

Summary of problem or feature request
Simply put, I want the PDF generated by DataTables in my Laravel app to be in landscape orientation.
Buttons are defined in main.js as follows:
    window.dtDefaultOptions = {
        retrieve: true,
        dom: 'lBfrtip<"actions">',
        columnDefs: [],
        "iDisplayLength": 100,
        "aaSorting": [],
        buttons: [
            {
                extend: 'copy',
                text: window.copyButtonTrans,
                exportOptions: {
                    columns: ':visible'
                }
            },
            {
                extend: 'csv',
                text: window.csvButtonTrans,
                exportOptions: {
                    columns: ':visible'
                }
            },
            {
                extend: 'excel',
                text: window.excelButtonTrans,
                exportOptions: {
                    columns: ':visible'
                }
            },
            {
                extend: 'pdf',
                text: window.pdfButtonTrans,
                exportOptions: {
                    columns: ':visible'
                }
            },
            {
                extend: 'print',
                text: window.printButtonTrans,
                exportOptions: {
                    columns: ':visible'
                }
            },
            {
                extend: 'colvis',
                text: window.colvisButtonTrans,
                exportOptions: {
                    columns: ':visible'
                }
            },
        ]
    };

If I add orientation: 'landscape' to the 'pdf' section above it does nothing. I've tried many other options and followed many threads but not getting any results. Feels like I'm missing something simple and obvious.
Any assistance is much appreciated.

Operating System: Laragon stack on WIn 10
PHP Version: 7.3.26
Laravel Version: 6
Laravel-Datatables Version: 9

Sorry for the late response. I think you are using a client-side pdf button that is out of the project's scope. Please check on the datatables.net forum instead. Thanks!


Can I deploy this to cloudflare？

I don`t have a vercel account ，can i use cloudflare as an alternative ？If i deploy this project to pages how to set env variables？

I haven't tried it myself, so I'm not sure. As a requirement, Next.js/edge runtime should work on Cloudflare Pages, but it seems like additional configuration might be necessary.
https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/
If you just want to try it out, Vercel also has a free account, which would be easier.

You can deploy on Cloudflare, you can either fork or deploy from local machine
For the fork, your build command should be npx @cloudflare/next-on-pages@1. First build must be failure, since you should set the compatibility_flag with nodejs_compat, after you configured it, rebuild and it will be successful.
For local machine, you should use npx @cloudflare/next-on-pages@1
Then, deploy it, npx wrangler pages publish .vercel/output/static, but you also need to config the compatibility flag.

Updated: https://github.com/miurla/morphic?tab=readme-ov-file#cloudflare-pages


gallery-dl : 1.8.3 -> 1.8.4

Motivation for this change
Things done
updated to 1.8.4, the 1.8.3 containing a crash while writing metadata to file

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@grahamcofborg build gallery-dl

@dawidsowa


TLC

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

Project coverage is 100.00%. Comparing base (46104e5) to head (2bf41f4).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          986       986
  Branches       103       103
=========================================
  Hits           986       986

Flag
Coverage Δ

unittests
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Remove nested renovation configuration

Closes #866

Thanks @rarkins.  I see the other issues, and I'll adjust those too. 👍

@abernix welcome. I think I missed one or two, so it's great if you can locate them. I think here's the full list:

@rarkins No worries at all.  The remaining ones seem to have been graphql-tools, apollo-link and apollo-angular, which I think I've got now (with the exception of the one that's queued in CI still).
Thanks so much for going above and beyond to do those, and for the super helpful automated(?) issue-opening! 🍾


Please add Pro License Incremental License Functionality

Incremental Refresh functionality needs to be enabled for pro license also.

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

ID: fdb026fd-1515-7484-1acd-3d363e143cc8
Version Independent ID: 62650e83-de5c-0323-cacc-31bad6e46361
Content: Incremental refresh in Power BI Premium - Power BI
Content Source: powerbi-docs/service-premium-incremental-refresh.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @davidiseminger
Microsoft Alias: davidi

It is, actually, as per this month's update: https://powerbi.microsoft.com/nl-nl/blog/power-bi-desktop-february-2020-feature-summary/#_Incremental_refresh

Thanks for your comment, @Anmolgan81.
I've assigned this issue to the doc author for review.

Hi. Thanks for this great update. I am on Power BI Pro account and it gives me error when publish the datasets with incremental refresh to myworkspace. It says it need a premium workspace. please help

I am also receiving the same error as Huwei612. I go through the steps to configure the IR and when i'm ready to publish to the service, It throws an error stating "You can only publish datasets with incremental refresh to premium workspace."

seeing the same notification: This dataflow contains entities with active incremental refresh policies, which require Premium to refresh

I get the same error. "You can only publish datasets with incremental refresh to premium workspace."

I believe this issue was related to not having downloaded and installed the latest version of PBI Desktop. I thought i had it but apparently i did not. Once i installed the latest version, the error went away - now i have a new issue! lol

My Incremental refresh is not working when I published the PBI to PBI Services.
Even in the PBI Desktop it does not seems to be working as the complete data refresh is taking more than 2hrs.
Over PBI Services it shows Time out as an error.

Sorry to hear about this (and happy that an update to the latest Desktop release helped!). For the last issue, your best avenue for support / information is going to be from the Power BI Community, found at https://community.powerbi.com. If that doesn't help, you can get support by going to https://support.powerbi.com.
Thanks for the conversation, and your persistence in getting the refresh working for Pro.


Update software_support_lifecycle.md with new OS list

There should probably be some way to automate this, but in the mean time, this is an updated list of OS dates (except LEAP). The EndOfLife.software website also has not been updated, but EndOfLife.date has.

Based on the Git log, this table has not been updated since it was originally created: https://github.com/voxpupuli/voxpupuli.github.io/commit/e4b05abb7ccd15a564d22edd5c379477da3418e7


Problem running one application on the EKS cluster after the deploy of the kubernetes-log4j-cve-2021-44228-node-agent

After the deploy of the kubernetes-log4j-cve-2021-44228-node-agent on the EKS cluster one of our application do not start and show the following logs:
java.nio.file.NoSuchFileException: /dev/shm/Log4jHotPatch.jar
Searching on the web we found a thread related to this and someone from AWS said that this issue is already identified and and will be fixed with the next update.
Thread:
https://github.com/corretto/hotpatch-for-apache-log4j2/issues/43#issuecomment-1011065074
It's possible to know when a new version of the agent will be released?

@heldertsantos published a new version with the latest updates.


Fix small typo "fullfil" in error message displayed in UI

What it solves
Resolves #
Came across a small typo while working on getting our manifest.json file up to spec.

How this PR fixes it
How to test it
Screenshots

I have read the CLA Document and I hereby sign the CLA
recheckcla

Fun fact, in Britain, they spell it with a single l.
Thanks Danny!


Create tests for hasStore()

Mission Control
The DAV project you are looking at is Mission Control. It is the brain in charge of orchestrating missions between DAV users and autonomous vehicles.
How you can help
The Issue
As a project that relies on a large community of contributors, it is very important for us to have good test coverage to make sure changes don't break anything.
The file /server/lib/environment.js isn't tested at all. Create a file /test/specs/lib.environment.spec.js that will test the function hasStore()
Test that hasStore() fulfills these conditions:

returns false if the DAV_ENV environment variable isn't set to 'simulated'

You might want to write the test so that it tests both conditions. You can get the environment variable in node using: process.env.DAV_ENV
You can see how this file should be structured based on the other files in the specs directory.
To run your tests, run npm test from the project's root directory. All tests should pass.

Contributing to Mission Control

[ ] Fork the repository from the Mission Control GitHub page.
[ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/missioncontrol.git
[ ] Make sure you have node.js and npm installed on your machine. You can use this guide for help.
[ ] Install all of the project's dependencies with npm. $ cd missioncontrol; npm install
[ ] Run npm test to run linting checks and all the automated tests and see that they pass.
[ ] Code! code! code!
[ ] Before committing your code, run npm test one last time and make sure no errors (including linting errors) are thrown.
[ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
[ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/missioncontrol) and create a pull request for your changes.
[ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #28)

will have to read a bit more about jest and follow the structure of the other specs but I will try writing this test

Sure @Rob-Rychs, give it a go 👍  If you stuck or need any help feel free to post here. We would be happy to help you out 😄

Hey @Rob-Rychs, do you still intend to take on this issue?

Hi @TalAter, yes I do! thanks for following up

So just so I know I'm on the right track I want to write an if/else statement where:
if (DAV_ENV != 'simulated') we expect hasStore().toBeFalsy()
and then the opposite condition:
else expect hasStore().toBeTruthy()
Is that getting close to the mark? sorry first ever .spec test and not sure
would it be better to do an else if and specifically check that (DAV_ENV = 'simulated')?
Some thoughts and guidance please and thanks

First, a quick note. Since we want to make sure it returns false, I would use toBe(false) rather than toBeFalsy(). The latter would also work if it returns undefined, 0, etc.
Second, we want to have each of our tests self-contained and just test a single condition. In other words, the tests that asserts that it returns false if the DAV_ENV environment variable isn't set to 'simulated', should not also test what happens when the environment is set to simulated (so, no else).
Now, regarding the test itself. It's actually an interesting question of what to test here.
One obvious solution might be to expect(env !== 'simulation' && hasStore === false) (that's pseudocode). But it feels to me like a more correct solution would be not to test for the environment variable as part of the assertion, and just test the thing we are testing.
In other words, I think this would be more correct:
test(`returns false when the DAV_ENV environment variable isn't set to 'simulated'`, () => {
  expect.assertions(1);
  if (process.env.DAV_ENV !== 'simulation') {
    expect(hasStore).toBe(false);
  }
});

It's a subtle difference but it seems like a more correct one. The assertion just tests what we came here to test... and if in the future we change the environment that tests run in, it shouldn't fail on returns false when the DAV_ENV environment variable isn't set to 'simulated' because hasStore didn't break - it functioned correctly, it was the test that failed.
What would happen is that we would get an error saying Expected one assertion to be called but only received zero assertion calls. This would be a good chance for us to add tests for other environments.
This would also leave it up to us to implement a future test for the environment separately, and not tied into the test for hasStore.
This is just my view of the matter. You can expect myView.toBeTruthy(), but not necessarily myView.toBe(the only truth) 😉
P.S. I made a mistake in the task description. hasStore is not actually a function but a constant value. so there's no need to invoke it. Leave the description of the test as is, as I will be refactoring it to a function once you are done adding the test.

Hey @Rob-Rychs,
Let me know if you have further questions.

Looks great, @Rob-Rychs!
Thank you, and thank you for bearing with my idiosyncrasies 😄
Congrats on joining the community, and becoming an open-sourcerer!

@Rob-Rychs I created a follow up issue to refactor hasStore to be a function and not a boolean - #70
Do you want to take that one?

yes please, thanks @TalAter


Use openjdk-*-jre-headless packages for jre images

Figured I may as well create a PR for this change. Feel free to close if you're not interested.
Fixes #21

Here's a list of the actual files added in the Debian openjdk-8-jre package for amd64:
/usr/lib/jvm/java-8-openjdk-amd64/bin/policytool
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytool
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libicedtea-sound.so
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libjsoundalsa.so
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libsplashscreen.so
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/java-atk-wrapper.jar
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/libatk-wrapper.so
/usr/lib/jvm/java-8-openjdk-amd64/jre/man/ja_JP.UTF-8/man1/policytool.1.gz
/usr/lib/jvm/java-8-openjdk-amd64/jre/man/man1/policytool.1.gz
/usr/lib/jvm/java-8-openjdk-amd64/man/ja_JP.UTF-8/man1/policytool.1.gz
/usr/lib/jvm/java-8-openjdk-amd64/man/man1/policytool.1.gz
/usr/share/application-registry/openjdk-8-archive.applications
/usr/share/applications/openjdk-8-java.desktop
/usr/share/applications/openjdk-8-policytool.desktop
/usr/share/doc/openjdk-8-jre
/usr/share/lintian/overrides/openjdk-8-jre
/usr/share/mime-info/openjdk-8-archive.keys
/usr/share/mime-info/openjdk-8-archive.mime
/usr/share/pixmaps/openjdk-8.xpm

Besides those files, the openjdk-*-jre packages pull in the corresponding -headless package and bits necessary to run the GUI.
I was a bit worried at first that it wasn't installing stuff like libpng12-0 anymore, but I satisfied my curiousity with this test program:
import java.awt.image.BufferedImage;
import java.io.File;
import javax.imageio.ImageIO;

public class Test {
	public static void main(String... argz) throws Exception {
		BufferedImage bi = new BufferedImage(100, 100, BufferedImage.TYPE_INT_ARGB);
		File outputfile = new File("test.png");
		ImageIO.write(bi, "png", outputfile);
	}
}

I build it like so:

$ docker run -it --rm -v $(pwd):/src -w /src java:openjdk-8-jdk javac Test.java

And ran it like so:

$ docker run -it --rm -v $(pwd):/src -w /src java:openjdk-8-jre-headless java -cp . Test

It produced an image without any exceptions.

I just discovered that this originally used -headless and changed to the other package less than a week ago in 0b124de91ebd32bcc8977fd2214d36b8fccb615c.
@tianon?

facepalm; good catch

+1 LGTM

LGTM

:sunny:

The diff between what's currently live on the Docker Registry and what's on master looks correct now: https://github.com/docker-library/java/compare/2408508f3b000bf997febbdb90a861185a64a260...58866569ecc3d516467baf83375f3bd4cb0b8229


Connecting to the same session fails [VNC error - problem connecting]

Hello! I hope you're having a great time.
I've added this small config to the bottom of /etc/xrdp/xrdp.ini:
[xrdp1]
name=mysession
lib=libvnc.so
username=ask
password=ask
ip=<IP_ADDRESS>
port=ask-1

I've logged in locally on my laptop but I want to connect remotely to it now, but it fails:

VNC error - problem connecting
some problem
Error connecting to the user session

cat /var/log/xrdp.log
[WARN ] Ignoring obsolete SCP port value '3350'
[INFO ] xrdp_wm_log_msg: sesman connect ok
[INFO ] xrdp_wm_log_msg: Performing login request for shayan
[INFO ] xrdp_wm_log_msg: login was successful - creating session
[INFO ] xrdp_wm_log_msg: session is available on display 14 for user shayan
[INFO ] xrdp_wm_log_msg: Connecting to session
[INFO ] loaded module 'libvnc.so' ok, interface size 4064, version 4
[ERROR] VNC error 1 after security negotiation
[ERROR] VNC error before sending share flag
[ERROR] VNC error before receiving server init
[ERROR] VNC error before receiving pixel format
[ERROR] VNC error before receiving name length
[ERROR] VNC error before receiving name
[ERROR] xrdp_wm_log_msg: Error connecting to user session

cat /var/log/xrdp-sesman.log
[WARN ] Timed out waiting for X server on display 14 to startup
[INFO ] Session started successfully for user shayan on display 14
[INFO ] Starting the xrdp channel server for display 14
[INFO ] Session in progress on display 14, waiting until the window manager (pid 500981) exits to end the session
[WARN ] Timed out waiting for X server on display 14 to startup
[ERROR] There is no X server active on display 14
[ERROR] A fatal error has occurred attempting to start the window manager on display 14, aborting connection
[WARN ] Window manager (pid 500981, display 14) exited quickly (0 secs). This could indicate a window manager config problem
[INFO ] Calling auth_stop_session from pid 500980
[INFO ] Terminating X server (pid 500982) on display 14
[INFO ] Terminating the xrdp channel server (pid 501016) on display 14
[INFO ] X server on display 14 (pid 500982) returned exit code 1 and signal number 0
[INFO ] xrdp channel server for display 14 (pid 501016) exit code 0 and signal number 0
[INFO ] cleanup_sockets:
[INFO ] Process 500980 has exited
[INFO ] Calling auth_end for pid 500980 from pid 500968
[INFO ] ++ terminated session: UID 1000 (shayan), display :14.0, session_pid 500980, ip <IP_ADDRESS>

Doesn't look like the X server is starting. Look further up in the sesman.log for the messages generated when the X server is started.

@matt335672 Hello! Thanks for replying.
Sorry about that, here's the full logs of today:
[INFO ] Socket 13: connection accepted from AF_UNIX
[INFO ] Received system login request from xrdp for user: shayan IP: <IP_ADDRESS>
[INFO ] Terminal Server Users group is disabled, allowing authentication
[INFO ] Access permitted for user: shayan
[INFO ] Received request from xrdp to create a session for user shayan
[INFO ] ++ created session: username shayan, ip <IP_ADDRESS>
[INFO ] Found X server running at /tmp/.X11-unix/X10
[INFO ] Found X server running at /tmp/.X11-unix/X11
[INFO ] Found X server running at /tmp/.X11-unix/X12
[INFO ] Found X server running at /tmp/.X11-unix/X13
[INFO ] Starting session: session_pid 634507, display :14.0, width 1920, height 1080, bpp 32, client ip <IP_ADDRESS>, UID 1000
[INFO ] [session start] (display 14): calling auth_start_session from pid 634507
[INFO ] Starting X server on display 14: Xvnc :14 -auth .Xauthority -geometry 1920x1080 -depth 32 -rfbauth /home/shayan/.vnc/sesman_passwd-shayan@debian:14 -bs -nolisten tcp -localhost -dpi 96
[ERROR] Error calling exec (executable: Xvnc, arguments: Xvnc :14 -auth .Xauthority -geometry 1920x1080 -depth 32 -rfbauth /home/shayan/.vnc/sesman_passwd-shayan@debian:14 -bs -nolisten tcp -localhost -dpi 96) returned errno: 2, description: No such file or directory
[ERROR] Error starting X server on display 14
[ERROR] A fatal error has occurred attempting to start the X server on display 14, aborting connection
[WARN ] Timed out waiting for X server on display 14 to startup
[INFO ] Session started successfully for user shayan on display 14
[INFO ] Starting the xrdp channel server for display 14
[INFO ] Session in progress on display 14, waiting until the window manager (pid 634508) exits to end the session
[WARN ] Timed out waiting for X server on display 14 to startup
[ERROR] There is no X server active on display 14
[ERROR] A fatal error has occurred attempting to start the window manager on display 14, aborting connection
[WARN ] Window manager (pid 634508, display 14) exited quickly (0 secs). This could indicate a window manager config problem
[INFO ] Calling auth_stop_session from pid 634507
[INFO ] Terminating X server (pid 634509) on display 14
[INFO ] Terminating the xrdp channel server (pid 634570) on display 14
[INFO ] X server on display 14 (pid 634509) returned exit code 1 and signal number 0
[INFO ] xrdp channel server for display 14 (pid 634570) exit code 0 and signal number 0
[INFO ] cleanup_sockets:
[INFO ] Process 634507 has exited
[INFO ] Calling auth_end for pid 634507 from pid 500968
[INFO ] ++ terminated session: UID 1000 (shayan), display :14.0, session_pid 634507, ip <IP_ADDRESS>

Looks like you don't have Xvnc installed.
You don't say what you platform is. On Debian/Ubuntu/Kali etc, etc use sudo apt install tigervnc-standalone-server. For other platforms, you'll need to do something different.

@matt335672 Are you sure? I'm on Debian Bullseye (Debian 11.6.0) and:
Linux debian 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux
Uhm, the XRDP works fine when my user is not logged in locally. I just want to be able to connect remotely while the same user is logged in locally, so I don't have to log out the user each time I want to connect via XRDP.
Thank you!

I installed tigervnc-standalone-server but now it just goes back to this error:

@Saya47 - that isn't supported on systemd-based systems - see the FAQ. If you absolutely need that functionality, you'll need to move to Devuan.
The limitation is imposed by systemd. There's some discussion around possible workarounds in #2491 but nothing concrete yet.

I've just updated the FAQ to reference #2491.

Thanks very much @matt335672
So basically RDP on Windows enforces single session per user as well, I was hoping to get better treatment on Linux! But systemd comes to fail us once again! oh well.


Stuck at connecting

Hi,
Cloned master, tried with and without the factoids plugin (master), and I only get this :
[2017-06-29 14:14:26.717495] [info] A connection has been set up successfully and will be started. This may take a while.

(followed by the settings I set)
It doesn't appear to do anything then, it's been several minutes (no connection timeout, either).
Running PHP 7.1 (note: event built on my own via pecl)

Hey, thanks for the report.
Try verifying that the details you've provided are for a secure connection,
and disable the secure flag if they don't (or vice versa) :)
Op do 29 jun. 2017 14:18 schreef Adrien Bertrand<EMAIL_ADDRESS>
Hi,
Cloned master, tried with and without the factoids plugin (master), and I
only get this :
[2017-06-29 14:14:26.717495] [info] A connection has been set up successfully and will be started. This may take a while.
(followed by the settings I set)
It doesn't appear to do anything then, it's been several minutes (no
connection timeout, either).
Running PHP 7.1 (note: event built on my own via pecl)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/WildPHP/Wild-IRC-Bot/issues/83, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABOJfKBjbiAobOJ5u7jNKaiQPyNSCA8jks5sI5X6gaJpZM4OJOM3
.

Well, I did check that, and settings are correct (6667 and not-secured, in my case).
 This was working fine in the previous major version btw.

Hm, that's curious. I have to say the connection code is really ugly and I
want to redo it.
Any chance you could post the connection variables, so I can take a look?
Op vr 30 jun. 2017 13:27 schreef Adrien Bertrand<EMAIL_ADDRESS>
Well, I did check that, and settings are correct (6667 and not-secured, in
my case).
 This was working fine in the previous major version btw.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/WildPHP/Wild-IRC-Bot/issues/83#issuecomment-312243625,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABOJfMliNCK-kIjkSuykl_NZg_Skg6WBks5sJNuQgaJpZM4OJOM3
.

The latest updates in master should give you an error if connecting fails, can you try with that code? :)

Will try as soon as you git add ConnectionDetails.php :P

Oh ooooooooooops :P Sorry, it's been added!

Ah, that was helpful, I guess:
[2017-06-30 17:55:32.767944] [error] An error occurred in the IRC connection:
    message: 'DNS Request did not return valid answer.'
    file: '.../vendor/react/dns/src/Resolver/Resolver.php'
    line: 41

Sure, the IRC server is on a local network, but... that shouldn't have to be an issue...

Hm, what are you using for server parameters? I can connect to ZNC just fine using this:
	znc:
		server: <IP_ADDRESS>
		port: 5000
		secure: false
		nick: FatalException
		user: fatalexception/Botergos
		password: '-STRIP-'
		realname: A WildPHP Bot

Yeah, so I tried disabling the dns resolution in the ConnectorFactory's ctor with the optional $options (it was defaulting to using google's <IP_ADDRESS>, which of course won't resolve the internal domain...), but in the end there still were some dns issues, so I just used the irc server's ip directly and now the whole thing appears to work fine :)
Thanks

Ah, thanks for posting the solution :)
I'll think of a way to perhaps add a switch to disable DNS lookups from the
config.
Op vr 30 jun. 2017 18:06 schreef Adrien Bertrand<EMAIL_ADDRESS>
Yeah, so I tried disabling the dns resolution in the ConnectorFactory's
ctor with the optional $options (it was defaulting to using google's
<IP_ADDRESS>, which of course won't resolve the internal domain...), but in the
end there still were some dns issues, so I just used the irc server's ip
directly and now the whole thing appears to work fine :)
Thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/WildPHP/Wild-IRC-Bot/issues/83#issuecomment-312308002,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABOJfEhokHd-dGZ_X0a0Bk_CJf2EuhWUks5sJRz0gaJpZM4OJOM3
.


Can't use compeonnt from another file

Version
4.5.10
Reproduction link
https://github.com/kumaresan-subramani/Vue3-template-check
Environment info
"vue": "^3.0.5",
    "vue-class-component": "^8.0.0-rc.1",
    "vue-template-compiler": "^2.6.11"
"@vue/cli-plugin-babel": "^4.5.10",
    "@vue/cli-plugin-eslint": "^4.5.10",
    "@vue/cli-service": "^4.5.10",
    "@vue/compiler-sfc": "^3.0.5",
    "babel-eslint": "^10.1.0",
    "eslint": "^6.8.0",
    "eslint-plugin-vue": "^7.4.1",
    "vue-loader-v16": "^16.0.0-beta.5.4"

Steps to reproduce

CLone below sample

https://github.com/kumaresan-subramani/Vue3-template-check

And give npm run serve

it wont render helloworld component

But it is working fine in below compoent

https://stackblitz.com/edit/vue-s4fpy3?file=package.json
What is expected?
Need to redner compeonnt form another file
What is actually happening?
But it not renderign properly

@sodatea - can you sugegst on this

https://github.com/kumaresan-subramani/Vue3-template-check/blob/fc962ebda6488ea453196725a927876b7f95972c/src/App.vue#L26
- import { HelloWorld } from "./components/HelloWorld";
+ import HelloWorld from "./components/HelloWorld.vue";

Don't omit the .vue extension
It's the default export

@sodatea , even after changing this same issue occurs

What issue? I don't see any errors on my machine. The app renders as expected:

Still not working for me
Is there any limitation like node version vue version etc?

What's your node version? And what's the error?

@sodatea ,
node - 10.15.1
it is wokring fine when i use yarn install to install node modules


Add updated CLI commands in rocketpool service docs

prune-eth1, resync-eth1, and resync-eth2 commands were added into the CLI in the last update but wasn't reflected in the docs.

To be fair, the block you're modifying was from v1.1.1 of the CLI as you can see in the version info printed above your updates. It's probably better to update that entire block (and perhaps all of the others) to the output of v1.2.3 if you want to bring those examples up to date. Keep in mind they are just meant to serve as examples though; it's not strictly necessary to update them with every new release.


WFLY-8418 licenses

generate licenses.xml and html
issue: https://issues.jboss.org/browse/WFLY-8418

Retest this please

Retest this please

retest this please


Taiko faucet page does not work when accessed through the faucet link(https://bridge.katla.taiko.xyz/faucet) directly .

Describe the bug
Description of the bug here :
The Taiko faucet page behaves differently and faucet does not work when accessed directly through this link https://bridge.katla.taiko.xyz/faucet . It works normally when we click the main url https://bridge.katla.taiko.xyz and then click on faucet . It throws an unrelated error when accessed through the /faucet url which already has /faucet in the path.

Steps to reproduce
Steps to reproduce here:

Go to https://bridge.katla.taiko.xyz/faucet url and connect to site
Select Horse token
On selecting Horse token it always throws an error saying Destination Chain must be selected which is incorrect error messaging .

Additional context
No response

Thanks for the report, the fix is already waiting for deployment!


Weights for VAN + UperNet

Thanks for the amazing contribution. Are they any plans to share the weights of VAN + UperNet?

Yes, we will share it soon.

Thanks!

updates on this?

Hi! You can use VAN + Light Ham for segmentation, offering SOTA Pareto curves (Params/FLOPs-mIoU curves). Code and checkpoints are available now.


texlab: 3.0.0 → 3.0.1

Motivation for this change
Update to the latest version: https://github.com/latex-lsp/texlab/releases/tag/v3.0.1
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.


Document effects on secrets when memory swap is enabled in 1.22+

This is a Feature Request

What would you like to be added

Add a warning for when memory swap feature is turned on, then kubernetes secrets that was written to tmpfs could be swapped to write to disk.
https://kubernetes.io/docs/concepts/architecture/nodes/#swap-memory
Why is this needed
This security risk should be documented so users are aware of the impact before turning on the alpha feature.
Comments

xref: https://github.com/kubernetes-sigs/secrets-store-csi-driver/issues/707
cc @tomhjp

/sig security
/sig node
We're usually sanguine about not documenting security concerns in full for alpha features (we label the feature as alpha and intend that as a strong hint it's unfinished). We should document this for beta. What I would typically do is run with swap backed by an encrypted file or block device.

/triage accepted
/help

Hey, I am new to the community and interested in contributing.
Can I work on this issue?

Anyone who signs the CLA is welcome to work on any issue in this Kubernetes repo.

/assign

Thanks, @sftim, for the assistance. Can I get some resources that can help me better understand what all and where I need to add?

Hey @sftim @ritazh was this all needed to be done? Should I send a PR?

Done in https://github.com/kubernetes/website/pull/29663
/close


Refactor compilation analysis task setup

This removes a fair bit of duplication and code that had similar purpose but slight behavioural differences. It also stops creating redundant non-type-resolution tasks for KMP since there are now source set analysis tasks created for common & JS source sets.
This will ease future refactoring.

Warnings

:warning:
It looks like this PR contains functional changes without a corresponding test.

  Generated by :no_entry_sign: dangerJS against e19f26e62e5da3d62a88840bf68f0eb8809adcec


feat(fw): use pytest nodeids as test names in json fixtures

More info in this discussion: https://github.com/ethereum/execution-spec-tests/pull/307#discussion_r1345986884
This will also mean removing the tag keyword arguments from tests, which is currently appended to the test names. I think we should add tags though, but not as a name, rather as metadata to allow filtering of tests, by opcode for example, something like tags=("create", "tstore", "tload", "reentrancy").

Additional observation that supports this change:
As of v1.0.6, the test fixture names (the keys in JSON fixture files) only consist of test parameters (and don't include the test function name) which leads to duplicate test IDs (as seen from a client test runner).
For example, these tests:
fill --evm-bin=~/code/github/danceratopz/go-ethereum/build/bin/evm --until=Cancun -k no_outer_selfdestruct --collect-only -q

tests/cancun/eip6780_selfdestruct/test_selfdestruct_revert.py::test_selfdestruct_created_in_same_tx_with_revert[fork=Cancun-no_outer_selfdestruct]
tests/cancun/eip6780_selfdestruct/test_selfdestruct_revert.py::test_selfdestruct_not_created_in_same_tx_with_revert[fork=Cancun-no_outer_selfdestruct]

produce the following fixtures with identical names:
ack no_outer_selfdestruct fixtures

fixtures/cancun/eip6780_selfdestruct/selfdestruct_revert/selfdestruct_created_in_same_tx_with_revert.json
2:    "000-fork=Cancun-no_outer_selfdestruct": {

fixtures/cancun/eip6780_selfdestruct/selfdestruct_revert/selfdestruct_not_created_in_same_tx_with_revert.json
2:    "000-fork=Cancun-no_outer_selfdestruct": {

Another consideration for the rename is that dotnet fails with "=" when filtering via test Name. Although, the doc claims you can escape "=", I couldn't get either of the following to work:
dotnet test src/Nethermind/Ethereum.Blockchain.Pyspec.Test/ -c debug --no-build --no-restore --filter Name~"000-tests/cancun/eip6780_selfdestruct/test_selfdestruct_revert.py::test_selfdestruct_created_in_same_tx_with_revert[fork=Cancun-no_outer_selfdestruct]"

dotnet test src/Nethermind/Ethereum.Blockchain.Pyspec.Test/ -c debug --no-build --no-restore --filter Name~"000-tests/cancun/eip6780_selfdestruct/test_selfdestruct_revert.py::test_selfdestruct_created_in_same_tx_with_revert[fork\=Cancun-no_outer_selfdestruct]"

This hack using the AND operator works:
dotnet test src/Nethermind/Ethereum.Blockchain.Pyspec.Test/ -c debug --no-build --no-restore --filter Name~"000-tests/cancun/eip6780_selfdestruct/test_selfdestruct_revert.py::test_selfdestruct_created_in_same_tx_with_revert[fork&Cancun-no_outer_selfdestruct]"
# -->
Test run for /home/dtopz/nethermind/src/Nethermind/Ethereum.Blockchain.Pyspec.Test/bin/debug/net7.0/Ethereum.Blockchain.Pyspec.Test.dll (.NETCoreApp,Version=v7.0)
Microsoft (R) Test Execution Command Line Tool Version 17.4.1+79d56b02b69a582cd90428878a5e9411ab7538f5 (x64)
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
Running 000-tests/cancun/eip6780_selfdestruct/test_selfdestruct_revert.py::test_selfdestruct_created_in_same_tx_with_revert[fork=Cancun-no_outer_selfdestruct], Network: [Cancun] at 14:15:34.111680

Passed!  - Failed:     0, Passed:     1, Skipped:     0, Total:     1, Duration: 549 ms - Ethereum.Blockchain.Pyspec.Test.dll (net7.0)

The pytest -k flag always had problems with "=", too:
fill --until=Cancun -k 'test_withdrawing_to_precompiles[fork\=Cancun'

results in:
ERROR: Wrong expression passed to '-k': test_withdrawing_to_precompiles[fork\=Cancun: at column 38: unexpected character "="

It doesn't seem possible to esacpe "=" in a -k expression either.
I'd suggest replacing "=" with "_" in our generated parameter strings used in nodeids in L702 here:
https://github.com/ethereum/execution-spec-tests/blob/04591fdb5c02b3532f48e2deb11234f428fd2b01/src/pytest_plugins/test_filler/test_filler.py#L697-L702
https://github.com/ethereum/execution-spec-tests/blob/main/src/pytest_plugins/test_filler/test_filler.py#L697-L702


Consider renaming the gem

Unfortunately hellosign-ruby-sdk is not really a good gem name, hellosign or hello_sign would be much better. :smile:
Currently one needs to add gem 'hellosign-ruby-sdk', require: 'hello_sign' to the Gemfile, since Bundler tries to load lib/GEM_NAME.rb and can't find lib/hellosign-ruby-sdk.rb. If the gem was named hello_sign, lib/hello_sign.rb would be loaded automatically.
An alternative to changing the gem name would be adding a lib/hellosign-ruby-sdk.rb file that requires lib/hello_sign.rb.

Heya @manuelmeurer --
Thanks, and I can see how that could definitely be a pain.
The issue with renaming to hello_sign is that that name is already taken by a third party vendor (https://rubygems.org/gems/hello_sign), so it's not available to us at this moment.
We're checking internally about options here -- we may consider a rename.
Re: the bundler issue -- is this new as of a recent version of bundler?
I haven't seen having to specify the require name in the Gemfile.
Though, as you point out, the name that's required in any ruby script files is hello_sign whereas the name of the gem is hellosign-ruby-sdk. Point taken.

@manuelmeurer -
Per your suggestion (thanks!), I created an additional require-able file hellosign-ruby-sdk.rb that references hello_sign. Should be a nice convenience!
Cheers for that - closing this out for now.

Great! :smile:
Bundler has always worked that way AFAIK. Unless you added require: false to a gem in the Gemfile, it tries to load lib/GEM_NAME.rb from that gem. If it can't find it, nothing is loaded, so it's just a "convenience" thing I guess... :smile:
What do you think about hellosign as the gem name? That was what I was looking for initially when searching for the official gem.

Huh. Well hopefully this will help that case at least.
Our API product head is going to be evaluating whether a change to hellosign would be a good step -- if it looks doable I'm sure we'll consider it. We'd like to avoid breaking anyone's existing implementation as much as possible though, so we'll have to weigh it carefully.
cc @rmelencio


object has no attribute 'get_display_name'

Hi
When i try import, shows error object has no attribute 'get_display_name'

If commit code in admin.py file, then worked
context['fields_list'] = [
            (resource.get_display_name(), [f.column_name for f in resource.get_user_visible_fields()])
            for resource in resources
        ]

Django==4.1.2 django-crispy-forms==1.14.0 django-import-export==3.0.1 django-tinymce==3.5.0 Pillow==9.2.0

Thanks for raising this.  get_display_name() should be a class method of the Resource.  Is there any reason why this method wouldn't be present on your resource object?  Can you post your implementation of MaterialProductType ?

I imported resources, then in the meta part of the admin model, I set resources.get_related_model('your_model')
Refer to the example below, it worked for me. You may try it.
from import_export import resources
import your model

class ModelAdmin(ImportExportModelAdmin):
    list_display = ('id', 'field_1', 'field_2')
    resources.get_related_model('your_model')

# Register your models here.
admin.site.register(ModelAdmin)

This happened to me when I accidentally put Model name instead of resource name in admin.py for resource_class
Hope this helps

Closing due to inactivity


psutil v. 3 compatibility

The /alive call does not work with psutil v. 3 upwards because it seems the get_memory_info method does no longer exist. A fix would be welcome.

Is there a corresponding method for psutil 3?

Idk whether it returns the same information, but this could be a replacement:
http://pythonhosted.org/psutil/index.html?highlight=memory info#psutil.Process.memory_info

We updated the dependencies in the Palladium release 1.0.1. psutil's memory_info is now used.


Exception while deleting Spark temp dir

runlog.txt
I followed the instructions in this document to create a POC. I noted an exception post run (see attachment). Please let me know if it is of a concern and any workaround to avoid it. On a side note, smoke test on your document ask to run mvn and verify. I don't see mvn in any of the software installed. Please tell where to install from and if it is needed at all.
Thanks

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

ID: 0f1dc518-dfe4-b71a-ee04-e8520bbd2f67
Version Independent ID: e04b082c-e52b-3ffb-c69d-10da5dc54528
Content: Get started with .NET for Apache Spark
Content Source: docs/spark/tutorials/get-started.md
Product: dotnet-spark
GitHub Login: @luisquintanilla
Microsoft Alias: luquinta

Hi @gopala000
Thank you for your question and feedback. Regarding the exception while deleting the Spark temp dir, this is a known Spark issue and nothing to worry about. Your application should run successfully. For more information, see this thread.
We're in the process of updating this tutorial in this PR #20264 . You should not have to do a check for mvn. I'll make sure to add this to the set of existing changes. Stay tuned for updates shortly.

Fixed in #20264


Hitting API rate limit

I'm hitting the GitHub API limit because of the notification look ups:

I think instead of automatically fetching all pages of search results, we should fetch just the first and show pagination buttons at the bottom of the tasks list. Then we can load subsequent pages based on user demand.
I think we should continue loading all the pages of notifications, but we should cache the result so we're not continuously refetching them.


Speedview idea: add a gradient behind the indicator, based on which way it's going

A lot of digital dashboard show this effect, where a color-to-transparent-gradient is behind the indicator, as a stylized motion blur. It would be a nice effect to be able to have 3 states:

indicator is not moving: no color behind it
indicator is going to a higher value: the gradient is between the indicator and 0. (or: a different custom indicator image is showing)
indicator is going to a lower value; the gradient is between the indicator and max value (or: a different custom indicator image is showing)

I guess it can be done already by having an OnSpeedChangeListener that changes the indicator image, based on the speed rising or dropping... but maybe there's a nicer way to implement this effect.

Some more examples, as used by Skoda in their app:

It could be a very good addition, but it needs much work.
Thanks for the idea.

No thanks ;-)
Currently doing it by having an imageindicator with built-in gradient, like this:

Done in v1.2.0 beta light effect.


[FLAKE] tests failing on " waited 4m0s but couldn't find running pod matching selector"

There has been a lot of tests failing on  waited 4m0s but couldn't find running pod matching selector recently.
Creating a new project: pumdnyfvww
Running odo with args [odo project create pumdnyfvww -w -v4]
[odo]  •  Waiting for project to come up  ...
[odo]  ✓  Waiting for project to come up [368ms]
[odo]  ✓  Project 'pumdnyfvww' is ready for use
[odo]  ✓  New project created and now using project : pumdnyfvww
Created dir: /tmp/493410141
Running git with args [git clone https://github.com/openshift/nodejs-ex /tmp/493410141/nodejs-ex]
[git] Cloning into '/tmp/493410141/nodejs-ex'...
Running odo with args [odo component create nodejs nodejs --project pumdnyfvww --context /tmp/493410141/nodejs-ex --app app]
[odo]  •  Validating component  ...
[odo]  ✓  Validating component [44ms]
[odo] Please use `odo push` command to create the component with source deployed
Running odo with args [odo push --context /tmp/493410141/nodejs-ex]
[odo] Validation
[odo]  •  Checking component  ...
[odo]  ✓  Checking component [60ms]
[odo]
[odo] Configuration changes
[odo]  ✓  Initializing component
[odo]  •  Creating component  ...
[odo]  ✓  Creating component [196ms]
[odo]
[odo] Pushing to component nodejs of type local
[odo]  •  Checking files for pushing  ...
[odo]  ✓  Checking files for pushing [1ms]
[odo]  •  Waiting for component to start  ...
[odo]  ✗  Waiting for component to start [4m]
[odo]  ✗  waited 4m0s but couldn't find running pod matching selector: 'deploymentconfig=nodejs-app'
Deleting project: pumdnyfvww
Running odo with args [odo project delete pumdnyfvww -f]
[odo] This project contains the following applications, which will be deleted
[odo] Application app
[odo] This application has following components that will be deleted
[odo] component named nodejs
[odo] No services / could not get services
[odo]  •  Deleting project pumdnyfvww  ...
[odo]  ✓  Deleting project pumdnyfvww [6s]
[odo]  ✓  Deleted project : pumdnyfvww
Deleting dir: /tmp/493410141
• Failure [249.085 seconds]
odo push command tests
/go/src/github.com/openshift/odo/tests/integration/cmd_push_test.go:15
  when push command is executed
  /go/src/github.com/openshift/odo/tests/integration/cmd_push_test.go:40
    should not build when changes are detected in a ignored file [It]
    /go/src/github.com/openshift/odo/tests/integration/cmd_push_test.go:168
    No future change is possible.  Bailing out early after 240.561s.

    Running odo with args [odo push --context /tmp/493410141/nodejs-ex]
    Expected
        <int>: 1
    to match exit code:
        <int>: 0
    /go/src/github.com/openshift/odo/tests/helper/helper_run.go:33
------------------------------
odo push command tests when push command is executed
  should be able to create a file, push, delete, then push again propagating the deletions
  /go/src/github.com/openshift/odo/tests/integration/cmd_push_test.go:57

from  https://github.com/openshift/odo/pull/2242#issuecomment-538146265

@kadel It's a flake, i have seen the same issue in other prs too. It would be great if somebody look into the odo code implementation side. cc_ @mik-dass

Can you please change the title to [Flake]Push fails on " waited 4m0s but couldn't find running pod matching selector"

I'm not sure but I think this happens when something's off with the project to which we're trying to do odo push. I saw this in my environment once. I did an odo delete --all, odo create and odo push which fixed this for me.

For the life of me, I can't seem to replicate this.. going to see if this pops back up on the CI side again.

We can try to reproduce it by increasing number of parallel test

Hi, @cdrage do you have any leads to what might be causing this?
There is also https://github.com/openshift/odo/issues/2392 which might be related to this.

@kadel No idea, but I'll investigate and see what may be causing this.. Really difficult to re-produce, but we can at least add some checks make sure the DeploymentConfig is completely deployed.

Been trying to replicate it multiple times but nothing... Here's my script:
#!/bin/bash

set -e

# Delete project and folders
rm -rf backend frontend || true
odo project delete myproject -f || true

git clone https://github.com/openshift-evangelists/Wild-West-Backend backend || true
git clone https://github.com/openshift-evangelists/Wild-West-Frontend frontend || true

odo project create myproject

# Import image
oc import-image openjdk18 \
--from=registry.access.redhat.com/redhat-openjdk-18/openjdk18-openshift --confirm
oc annotate istag/openjdk18:latest tags=builder

# Deploy backend
cd backend
mvn package
odo create openjdk18 backend --binary target/wildwest-1.0.jar
odo push -v 4
cd ..

# Deploy frontend
cd frontend
odo create nodejs frontend
odo push -v 4

# Link both
odo link backend --port 8080

cd ..

Hmm. I'm getting to something. I got a failure to start since PVC was taking too long. We actually do not check for PVC nor "output" anything regarding it...
I'm going to create some output for this at least.
So going to at least
Name:               nodejs-nodejs-ex-uhda-app-1-7vqs6
Namespace:          myproject
Priority:           0
PriorityClassName:  <none>
Node:               ip-172-16-15-175.ec2.internal/<IP_ADDRESS>
Start Time:         Wed, 13 Nov 2019 12:01:26 -0500
Labels:             deployment=nodejs-nodejs-ex-uhda-app-1
                    deploymentconfig=nodejs-nodejs-ex-uhda-app
Annotations:        alpha.image.policy.openshift.io/resolve-names=*
                    kubernetes.io/limit-ranger=LimitRanger plugin set: cpu, memory request for container nodejs-nodejs-ex-uhda-app; cpu, memory limit for container nodejs-nodejs-ex-uhda-app; cpu, memory request for init ...
                    openshift.io/deployment-config.latest-version=1
                    openshift.io/deployment-config.name=nodejs-nodejs-ex-uhda-app
                    openshift.io/deployment.name=nodejs-nodejs-ex-uhda-app-1
                    openshift.io/scc=restricted
Status:             Pending
IP:
Controlled By:      ReplicationController/nodejs-nodejs-ex-uhda-app-1
Init Containers:
  copy-files-to-volume:
    Container ID:
    Image:         <IP_ADDRESS>:5000/openshift/nodejs@sha256:71ff339d7221be9095961a95c5acea25f87f2b9c4c92dbb9b139c9b2940bb9ce
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Command:
      sh
      -c
    Args:

SRC=/opt/app-root
DEST=/mnt/app-root

if [ -f $DEST/.delete-volume ]; then
    rm -rf $DEST
fi
 if [ -d $DEST ]; then
    if [ -f $DEST/.sync-volume ]; then
        if ! [[ "$JUPYTER_SYNC_VOLUME" =~ ^(false|no|n|0)$ ]]; then
            JUPYTER_SYNC_VOLUME=yes
        fi
    fi
     if [[ "$JUPYTER_SYNC_VOLUME" =~ ^(true|yes|y|1)$ ]]; then
        rsync -ar --ignore-existing $SRC/. $DEST
    fi
     exit
fi
 if [ -d $DEST.setup-volume ]; then
    rm -rf $DEST.setup-volume
fi

mkdir -p $DEST.setup-volume
tar -C $SRC -cf - . | tar -C $DEST.setup-volume -xvf -
mv $DEST.setup-volume $DEST

    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     1
      memory:  512Mi
    Requests:
      cpu:        100m
      memory:     256Mi
    Environment:  <none>
    Mounts:
      /mnt from nodejs-nodejs-ex-uhda-app-s2idata (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-99rdz (ro)
  copy-supervisord:
    Container ID:
    Image:         registry.access.redhat.com/openshiftdo/odo-init-image-rhel7:1.0.0
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Command:
      /usr/bin/cp
    Args:
      -r
      /opt/odo-init/.
      /opt/odo/
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     1
      memory:  512Mi
    Requests:
      cpu:        100m
      memory:     256Mi
    Environment:  <none>
    Mounts:
      /opt/odo/ from odo-supervisord-shared-data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-99rdz (ro)
Containers:
  nodejs-nodejs-ex-uhda-app:
    Container ID:
    Image:         <IP_ADDRESS>:5000/openshift/nodejs@sha256:71ff339d7221be9095961a95c5acea25f87f2b9c4c92dbb9b139c9b2940bb9ce
    Image ID:
    Port:          8080/TCP
    Host Port:     0/TCP
    Command:
      /opt/odo/bin/go-init
    Args:
      -main
      /opt/odo/bin/supervisord -c /opt/odo/conf/supervisor.conf
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     1
      memory:  512Mi
    Requests:
      cpu:     100m
      memory:  256Mi
    Environment:
      DEBUG_PORT:                5858
      ODO_S2I_SCRIPTS_URL:       /usr/libexec/s2i
      ODO_S2I_SCRIPTS_PROTOCOL:  image://
      ODO_S2I_SRC_BIN_PATH:      /tmp
      ODO_S2I_DEPLOYMENT_DIR:    /opt/app-root/src
      ODO_S2I_WORKING_DIR:       /opt/app-root/src
      ODO_S2I_BUILDER_IMG:       rhoar-nodejs/nodejs-10
      ODO_SRC_BACKUP_DIR:        /opt/app-root/src-backup
    Mounts:
      /opt/app-root from nodejs-nodejs-ex-uhda-app-s2idata (rw)
      /opt/odo/ from odo-supervisord-shared-data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-99rdz (ro)
Conditions:
  Type              Status
  Initialized       False
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  odo-supervisord-shared-data:
    Type:    EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  nodejs-nodejs-ex-uhda-app-s2idata:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  nodejs-nodejs-ex-uhda-app-s2idata
    ReadOnly:   false
  default-token-99rdz:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-99rdz
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  type=compute
Tolerations:     node.kubernetes.io/memory-pressure:NoSchedule
Events:
  Type     Reason              Age              From                                    Message
  ----     ------              ----             ----                                    -------
  Normal   Scheduled           3m               default-scheduler                       Successfully assigned myproject/nodejs-nodejs-ex-uhda-app-1-7vqs6 to ip-172-16-15-175.ec2.internal
  Warning  FailedAttachVolume  3m (x2 over 3m)  attachdetach-controller                 AttachVolume.Attach failed for volume "pvc-38ce5c02-0637-11ea-b4b9-12d3ba54a54b" : "Error attaching EBS volume \"vol-0cde4c5fcc80f93ff\"" to instance "i-0eb54d0efaf9e2db7" since volume is in "creating" state
  Warning  FailedMount         1m               kubelet, ip-172-16-15-175.ec2.internal  Unable to mount volumes for pod "nodejs-nodejs-ex-uhda-app-1-7vqs6_myproject(3ae2079f-0637-11ea-b4b9-12d3ba54a54b)": timeout expired waiting for volumes to attach or mount for pod "myproject"/"nodejs-nodejs-ex-uhda-app-1-7vqs6". list of unmounted volumes=[nodejs-nodejs-ex-uhda-app-s2idata]. list of unattached volumes=[odo-supervisord-shared-data nodejs-nodejs-ex-uhda-app-s2idata default-token-99rdz]

Another failure I was able to encounter (for my notes..):
To replicate: quickly do a odo delete -f and then odo push and you'll encounter an error with DeploymentConfig complaining regarding the deployer pod going missing...
mkdir -p $DEST.setup-volume
tar -C $SRC -cf - . | tar -C $DEST.setup-volume -xvf -
mv $DEST.setup-volume $DEST

    Environment:        <none>
    Mounts:
      /mnt from nodejs-nodejs-ex-qpfd-app-s2idata (rw)
   copy-supervisord:
    Image:      registry.access.redhat.com/openshiftdo/odo-init-image-rhel7:1.0.0
    Port:       <none>
    Host Port:  <none>
    Command:
      /usr/bin/cp
    Args:
      -r
      /opt/odo-init/.
      /opt/odo/
    Environment:        <none>
    Mounts:
      /opt/odo/ from odo-supervisord-shared-data (rw)
  Containers:
   nodejs-nodejs-ex-qpfd-app:
    Image:      <IP_ADDRESS>:5000/openshift/nodejs@sha256:71ff339d7221be9095961a95c5acea25f87f2b9c4c92dbb9b139c9b2940bb9ce
    Port:       8080/TCP
    Host Port:  0/TCP
    Command:
      /opt/odo/bin/go-init
    Args:
      -main
      /opt/odo/bin/supervisord -c /opt/odo/conf/supervisor.conf
    Environment:
      DEBUG_PORT:               5858
      ODO_S2I_SCRIPTS_URL:      /usr/libexec/s2i
      ODO_S2I_SCRIPTS_PROTOCOL: image://
      ODO_S2I_SRC_BIN_PATH:     /tmp
      ODO_S2I_DEPLOYMENT_DIR:   /opt/app-root/src
      ODO_S2I_WORKING_DIR:      /opt/app-root/src
      ODO_S2I_BUILDER_IMG:      rhoar-nodejs/nodejs-10
      ODO_SRC_BACKUP_DIR:       /opt/app-root/src-backup
    Mounts:
      /opt/app-root from nodejs-nodejs-ex-qpfd-app-s2idata (rw)
      /opt/odo/ from odo-supervisord-shared-data (rw)
  Volumes:
   odo-supervisord-shared-data:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
   nodejs-nodejs-ex-qpfd-app-s2idata:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  nodejs-nodejs-ex-qpfd-app-s2idata
    ReadOnly:   false

Deployment #1 (latest):
        Name:           nodejs-nodejs-ex-qpfd-app-1
        Created:        about a minute ago
        Status:         Failed
        Replicas:       0 current / 0 desired
        Selector:       deployment=nodejs-nodejs-ex-qpfd-app-1,deploymentconfig=nodejs-nodejs-ex-qpfd-app
        Labels:         app.kubernetes.io/instance=nodejs-nodejs-ex-qpfd,app.kubernetes.io/managed-by-version=v1.0.1,app.kubernetes.io/managed-by=odo,app.kubernetes.io/name=nodejs,app.kubernetes.io/part-of=app,app.openshift.io/runtime-version=latest,app=app,openshift.io/deployment-config.name=nodejs-nodejs-ex-qpfd-app
        Pods Status:    0 Running / 0 Waiting / 0 Succeeded / 0 Failed

Events:
  Type          Reason                  Age     From                            Message
  ----          ------                  ----    ----                            -------
  Normal        DeploymentCreated       1m      deploymentconfig-controller     Created new replication controller "nodejs-nodejs-ex-qpfd-app-1" for version 1
  Warning       Failed                  32s     deployer-controller             Deployer pod "nodejs-nodejs-ex-qpfd-app-1-deploy" has gone missing

getting while odo push
X  Waiting for component to start [4m]
X  waited 4m0s but couldn't find running pod matching selector: 'deploymentconfig=frontend-app'


Fix published decklist comparison functionality from the decklist page.

The menu item just wasn't wired up to the javascript to bring up the UI for the comparison.
This fixes #279
Dialog after clicking "Compare with another decklist"

Decklist Comparison View

Deployed to production.


⚠ Roblox Group Api has degraded performance

In 0f9d519, Roblox Group Api (https://groups.roblox.com) experienced degraded performance:

HTTP code: 200
Response time: 5074 ms

Resolved: Roblox Group Api performance has improved in e61efe8.


Floor and floor bw seeps

Added YAMLs and API calls

This PR should not change the llama submodule commit


require NATS username and password. refactored disconnect signal handler

good work. one question is did we just get rid of the signal handler?

@tybalex the signal handler logic is still there https://github.com/rancher/opni-nats-wrapper/blob/3064198ceed3e9c378650ec428a80c513677d487/src/opni_nats/nats_wrapper.py#L87


windows --authonly

FreeRDP returns errorlevel 0 no matter what in windows 7. How can I detect if I have successfully connected to the remote desktop when --authonly option is present?
I tried both "wfreerdp [options] && echo %errorlevel%" and "start /wait wfreerdp [options] && echo %errorlevel%"

@melanholy wfreerdp is a windows gui application which detaches from the terminal. you have to modify it to a console app if you want to do that.

Did this. Still the same

@melanholy you're right, the windows client always returns 0 (see wf_client.c:852) and overall lacks return value checks :/
Currently no windows machine near me, so I can't fix it but I hope this info helps.


document db plugin

Signed-off-by: Sandeep Kumar Verma1<EMAIL_ADDRESS>

Need to do some more changes, closing this


add Flynn as GAMMA lead, remove Mike Morris

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Implements the leadership change proposed in https://groups.google.com/g/kubernetes-sig-network/c/lfeAlMAgTq0
Does this PR introduce a user-facing change?:
NONE

Below is copied from contributors/chairs-and-techleads/leadership-changes.md with the section on where changes need to be made modified to reflect Gateway API project organization.
Leadership Changes
This document covers steps needed to propose changes to SIG/WG/UG leadership.

[x] Discuss the proposed changes with the current leadership.

[x] Send an email to the SIG/WG/UG mailing list and cc the kubernetes-dev
mailing list. At a minimum, the email should contain:

[x] intent to step down as the current lead
[x] if nominating another lead

[x] 1-2 lines about why they are being nominated
[x] contacts to privately reach out to for questions (current leads)
or concerns (current leads + steering-private) about the nomination

[x] if this was discussed in a meeting, link to meeting notes
[x] lazy consensus deadline of at least one week

[ ] If nominating another lead, ensure that they

[ ] are a Kubernetes GitHub org member
[ ] have completed the Inclusive Open Source Community Orientation course

[x] Once lazy consensus has been achieved, update the following
files in the respective repos:

[x] [kubernetes-sigs/gateway-api]: OWNERS_ALIASES

[ ] Update all communication properties used by the community group.
See sig-wg-lifecycle.md for details.

Note: If multiple candidates are running for an open lead position and
lazy consensus cannot be achieved, an election should be held.
SIG Contributor Experience should be contacted to assist with the
administration of the election.
/cc @kflynn

Thanks for everything @mikemorris!
/lgtm
/approve


Fresh wallet adress with USDC-DFI invisible until first DFI arrives

What happened:
My DFI address is invisible on DeFiChain Explorer
What you expected to happen:
My DFI address was visible on DeFiChain Explorer
How to reproduce it (as minimally and precisely as possible):
I created a new wallet on "DeFiChain wallet mobile app" and had 0 coins on it. I transferred some USDC-DFI-tokens to it from "DeFi Wallet desktop app". The tokens arrived and generated DFI (Token) rewards. I still had 0 DFI (UTXO) on it.
Anything else we need to know?:
A mod from Telegram sent me 0,001 DFI to the address. After a couple of minutes the address was visible and worked. This means I had to have DFI (UTXO) on this wallet before it was visible.

@benameless DeFiScan released their address page. You can try to search it from there - https://defiscan.live/address


consolidating some components in developer page

prepareing for new p tag & a tag styles

looks good to me


Add Health Checks to loadbalancers

It doesn't seem like there's a way to configure a health check. I would like to be able to configure a health check and then attach it to a load balancer, or just declare a health check on load balancer creation.

Not sure if this exactly what you are looking but you can configure the health check in the load_balancer_options, for example
{code}                                                                                load_balancer_options lazy {
{
listeners: [{
port: 80,
protocol: :http,
instance_port: 80,
instance_protocol: :http
}, {
port: 443,
protocol: :https,
instance_port: 443,
instance_protocol: :https
}],
health_check: {
healthy_threshold: 2,
unhealthy_threshold: 4,
interval: 12,
timeout: 5,
target: 'HTTPS:443/_status'
},
scheme: 'internet-facing',
subnets: lb_subnet,
security_groups: [
security_group.aws_object.id
]
}
}
{code}

@rgeddis where are you seeing this in the docs? I don't see it in the docs for this repo nor in the aws docs that describe the load balancer creation options.

This answer shouldn't be considered canonical unless it comes from a developer, but the short answer is "a pinch of magic" - The actual call made is configure_health_check which you can see here.  So basically the AWS chef provisioning resource is doing some of the heavy lifting for you by taking the health_check subsection of the load_balancer_options hash out and applying it via configure_health_check (idempotently, if the desired state is different).  It's probably a good idea to have a look at the spec tests to get other examples of resource usage, such as the load balancer specs.  HTH!

Yes that helps, but it should definitely be included in the docs.


[BUG]: SuperDuper is no longer able to connect to my Brooklyn (Super73 can connect to my bike)

Contact Details [Optional]
No response
System Information
Android 10 QKQ1
MUI Global 12.0.5
What happened?
Hi!
The bug just arrived just now (The scan doesn't work, too). Before that, there was another bug: every time I opened the application, I was no longer on the  bike settings page but on the bike names.
Steps to reproduce

...
Relevant log output
No response

Hey @ovnis82
Wrong project :p
https://github.com/blopker/superduper


Remove (or ?) backtick from message

On this line:
https://github.com/Senzing/senzing-tools/blob/main/cmd/root.go#L91
There is a backtick instead of a single quote or use a backtick after the the command so that it is properly formatted for a markdown like inline code block?
Bigger question is should we be using Fprintf to stderr at all?  This would ruin any JSON output.

Pull requests:

https://github.com/Senzing/senzing-tools/pull/111


Google module: Set text for certain family (or better /variant).

Is it possible to set character loading for only one of the families (sometimes you might want to embed light font for certain characters, like numbers as well)?
This is what I'm trying to do (obviously will overwride the first one).
WebFontConfig = {
    google: { families: ['Lato:400,700,400italic,900:latin'] },
    google: { families: ['Ek+Mukta:800:latin'], text: '0123456789' }
};

Thanks

No, that's currently not possible without calling WebFont.load twice. This is mostly because the Google Fonts API only accepts a single text parameter.


[Issue #372] Refactoring Attribute's data members and the enum FieldType

Refactors the Enum FieldType to AttributeType
Refactors the data member fieldType in Attribute to attributeType
Refactors the data member fieldName in Attribute to attributeName
Refactors variable names from fieldName to attributeName
Refactors variable names from fieldType to attributeType

This PR has been opened to address Issue #372

Please include issue 372 number in the subject.  After @zuozhiw approves it, you can do the merge.

@chenlica I added the issue prefix to the PR. @zuozhiw @FlavioBayer Both of you should have a look

I sampled some of the changes, and they look good to me.

lgtm

LGTM.
Please go ahead do the merge.


Start guide in README.md not work

hello.go:5:2: cannot find package "gopkg.in/night-codes/summer.v1" in any of:
/usr/local/Cellar/go/1.11.1/libexec/src/gopkg.in/night-codes/summer.v1 (from $GOROOT)
/Users/andreychernov/go/src/gopkg.in/night-codes/summer.v1 (from $GOPATH)

Fixed


Slack Real Time API

Now supports Slack Real Time API
Removes HTTP adapter
Removes unused Slack config

Docs might need a hand. Also, mentioning the bot using @hal does not work at the moment.

@danryan This is kind of a WIP. Is anything missing?

Fixes #38


This version of Debian is too old and unsupported.

Debian 11 or higher is required to use this installer.
This version of Debian is too old and unsupported.

Which version of Debían are you using?


Use RBAC permissions to show/hide tabs and perspective options

As a user, I expect Overview tabs and perspective options to be shown according to my user's entitlements and RBAC permissions. Items should only be shown if the following conditions are met.

If the user is an org admin, all items are available
An item is shown if the user has RBAC permissions for specific resource types
Sources are populated with data

https://issues.redhat.com/browse/COST-647

Codecov Report

Merging #1713 into master will not change coverage.
The diff coverage is 25.00%.

@@           Coverage Diff           @@
##           master    #1713   +/-   ##
=======================================
  Coverage   78.52%   78.52%
=======================================
  Files         243      243
  Lines        3948     3948
  Branches      763      763
=======================================
  Hits         3100     3100
  Misses        764      764
  Partials       84       84

Impacted Files
Coverage Δ

src/utils/permissions.ts
22.97% <25.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 c642b42...30d4873. Read the comment docs.


VAC's/Untrusted

So im curious, and i need a little help, My accounts keep getting vac banned or untrusted but my friend who uses all my stuff isnt getting it, so im curious as to why this is? im using a custom injector, not the best but i learnt how to make a simple loadlibrary one. any ideas would be appreciated!

From what I can see, you may have a detected injector. You say that your injector is a simple load-library one. I'm assuming it doesn't have the VAC DLL bypass check. That may be the case.

From what I can see, you may have a detected injector. You say that your injector is a simple load-library one. I'm assuming it doesn't have the VAC DLL bypass check. That may be the case.

what would be the best way to implement a VAC DLL bypass check?

You can use Daniel's OneByteLdr found here: https://github.com/danielkrupinski/OneByteLdr in your own injector. Or, alternatively you can download an injector that's pretty undetected and popular with the DLL check bypass already implemented. The name of that injector is CSGhost v2.6

Another very good way would be to add "-allow_third_party_software" to csgo start params and just use cheat engine to inject the dll


Another Issue plus fix for Power BI Desktop Store Version.

Hi,
Not an Issue, just another entry for your page.  We had the following issues with the Power BI Desktop store version.
SYMPTOMS

starting Power BI gives the message " Hmmmm... can't reach this page.  ms-pbi.pbi.microsoft.com's server IP address could not be found.
Application event log message - The description for Event ID 1 from source MSOLAP$AnalysisServicesWorkspace_0822eaf6-5c17-4ef6-8345-635ca73d8982 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

FIX
reinstall WebView2

uninstall webview2 ( standard user can do this)
install webview2 using the bootstrapper from here - https://go.microsoft.com/fwlink/p/?LinkId=2124703 ( standard user can do this)

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

ID: 533d0cd5-b457-863c-f862-49fac672332c
Version Independent ID: f5df6cb3-049a-eff0-4d7b-3c3843927a5e
Content: Resolve issues when starting Power BI Desktop - Power BI
Content Source: powerbi-docs/connect-data/desktop-error-launching-desktop.md
Service: powerbi
Sub-service: pbi-data-sources
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @PaulKlerkx - great idea! I've added your work-around to that article, should show up in a day or two. Thanks!

Fixed!

Thank you, this fixed my issue.


Add manual page

Hi! First of all thanks for your work on u-config, it's a really nice little tool. I intend to package this for Debian, since I find it useful when working on pkg-config files. As also mentioned in the commit message, this is the reason why I wrote this. If there's anything I should change, please let me know.
I've also sent this patch via your mailing list<EMAIL_ADDRESS>

This is great! Thanks, Andrea. That's a nice touch only documenting the
differences in order to minimize maintenance. If it helps with packaging,
I can tag v0.34.0 right away with the new man page.
Out of curiosity, I presume it would be available as a "u-config" command
regardless, but do you also plan to also add it to the alternatives system
as another "pkg-config" provider? Last year @N-R-K extensively tested by
building system packages to shake out bugs and differences from pkg-config
and pkgconf, so it really ought to fit the bill:
@.***%3E
Though that still leaves the matter of "pkg.m4". I don't plan to check in
a copy, nor include it in my releases, but as a pkg-config alternative I
believe you'd need to include a copy in the package.
(And thanks for the mailing list patch! Either that or PR are fine for me.
The redundancy is for the convenience of patch submitters, i.e. anyone can
submit patches to my projects without a GitHub account. An email address
is sufficient.)

On Thu Aug 22, 2024 at 6:40 PM CEST, Christopher Wellons wrote:

This is great! Thanks, Andrea. That's a nice touch only documenting
the differences in order to minimize maintenance. If it helps with
packaging, I can tag v0.34.0 right away with the new man page.

Thanks for the offer, but that's not necessary. I can just ship the man
page as is and drop it in the following release.

Out of curiosity, I presume it would be available as a "u-config"
command regardless, but do you also plan to also add it to the
alternatives system as another "pkg-config" provider? Last year @N-R-K
extensively tested by building system packages to shake out bugs and
differences from pkg-config and pkgconf, so it really ought to fit the
bill:

It's an interesting idea, but I'll avoid it for now. pkgconf provides
extra stuff like pkgconf-personality(5) (and pkg.m4(7), as you've
mentioned) which helps in cross-compiling scenarios. u-config might
still be preferrable when performing native builds though, and users
always have the option of setting the PKG_CONFIG environment variable to
u-config or adding a symlink into /usr/local/bin.

Though that still leaves the matter of "pkg.m4". I don't plan to check
in a copy, nor include it in my releases, but as a pkg-config
alternative I believe you'd need to include a copy in the package.

I was thinking at maybe splitting the m4 part out of the pkgconf package
into a separate one, and have u-config depend on the new package, so
that I don't have to vendor a file which is already in Debian. But
I won't bother the pkgconf maintainer for now, I'll just focus on
initial packaging :)


Scale is not detected.

Hi,
I have a OKOK scale which is not detected by the addon. (https://www.amazon.nl/-/en/Alpina-Smart-Libra-percentage-Bluetooth/dp/B09PRPWRFJ)
I did some measurements with my phone:
UUID: 4127FDAE-C215-D390-632B-656CA4F3B7CA
Manufacturer data:
26c0 1b56 1388 0808 2554 099a 4b3d 1c -> 69.98kg
24c0 0764 1388 0808 2554 099a 4b3d 1c -> 18.92kg
first 8 bytes of the first cluster increases by one for every measurement. (0x26)
Second cluster is weight. 1b56 -> 6998 -> 6998kg
The others I dont know.
Not that familiar with HA addons. Maybe I can change a value somewhere to support this scale?
//edit
i dont seem to be able to connect to the device with any other app/scanner. Only the OKOK app can connect. I see no services advertised in nrf connect.
BLE scanner on IOS does show 1 service to connect... but is also unable to connect.

If you enable debugging for the OKOK scale integration do you see anything being logged?

Enabled debug logging. Only thing in logbook is that it is on the last version.

I got another quite similar okok scale and can confirm @nielskool's observations.
Address: B4:56:5D:37:76:9A
Manufacturer data:
0x10FF C045 1D79 17700A0125B4565D37769A -> 75,45
0x10FF C048 0203 17700A0125B4565D37769A -> 5,15
Anything we can do with this information to support other okok scales? @rrooggiieerr

Are your scales Bluetooth name Chipsea-BLE? If not it's not going to work, if it has the right Bluetooth name then is should log the Address if debug logging is enabled


pilot report warning:"got nil value for route <IP_ADDRESS>" and pod can not work well

Bug description
when the pod is injected with proxy, the pilot report warning and pod can not be working well.
# kubectl get pod -n master
NAME                           READY     STATUS    RESTARTS   AGE
user-59dbc5c585-bpzg5      1/2       Running   6          1h

the pilot log:
2019-04-28T14:14:49.064519Z	info	ads	LDS: PUSH for node:user-c559bf4ff-brcvf.master addr:"<IP_ADDRESS>:33930" listeners:156 317519
2019-04-28T14:14:49.064578Z	warn	ads	RDS: got nil value for route <IP_ADDRESS> for node &{ sidecar [<IP_ADDRESS>] user-c559bf4ff-brcvf.master  master.svc.cluster.local master  map[POD_NAME:user-c559bf4ff-brcvf CONFIG_NAMESPACE:master ISTIO_VERSION:1.1.3 pod-template-hash:711569099 ISTIO_PROXY_SHA:istio-proxy:a169a0c0cd86b51538c240e2d037fa8f7f5860ae ISTIO_META_INSTANCE_IPS:<IP_ADDRESS>,<IP_ADDRESS> istio:sidecar INTERCEPTION_MODE:REDIRECT ISTIO_PROXY_VERSION:1.1.3 app:user] 0xc421f32190 [] [app-index=1,app=user,m-app=user,pod-template-hash=711569099]}: <nil>
2019-04-28T14:14.49.1629151Z	info	ads	ADS: RDS: PUSH for node: user-c559bf4ff-brcvf.master addr:<IP_ADDRESS>:37856 routes:130
2019-04-28T14:14.49.1629201Z   info	ads	Push finished: 1.515309241s {
    "ProxyStatus": {
        "pilot_no_ip": {
            "user-c559bf4ff-brcvf.master": {
                "proxy": "user-c559bf4ff-brcvf.master"
            },
...

the deployment
{
  "kind": "Deployment",
  "apiVersion": "extensions/v1beta1",
  "metadata": {
    "name": "user",
    "namespace": "master",
    "labels": {
      "app": "user"
    }
  },
  "spec": {
    "replicas": 1,
    "selector": {
      "matchLabels": {
        "app": "user"
      }
    },
    "template": {
      "metadata": {
        "labels": {
          "app": "user"
        }
      },
      "spec": {
        "containers": [
          {
            "name": "user",
            "image": "docker.xxx.io/user/user",
            "ports": [
              {
                "name": "http",
                "containerPort": 8080,
                "protocol": "TCP"
              }
            ],
            "resources": {
              "limits": {
                "cpu": "8"
              },
              "requests": {
                "cpu": "500m"
              }
            },
            "livenessProbe": {
              "httpGet": {
                "path": "/health",
                "port": 8080,
                "scheme": "HTTP"
              },
              "initialDelaySeconds": 600,
              "timeoutSeconds": 5,
              "periodSeconds": 5,
              "successThreshold": 1,
              "failureThreshold": 3
            },
            "readinessProbe": {
              "httpGet": {
                "path": "/health",
                "port": 8080,
                "scheme": "HTTP"
              },
              "initialDelaySeconds": 600,
              "timeoutSeconds": 5,
              "periodSeconds": 5,
              "successThreshold": 1,
              "failureThreshold": 3
            },
          }
        ]
      }
    }
  }

And can not find the service's route though "istioctl pc route"
Expected behavior
no warning and the pod is running well.
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version)
istio-1.1.3
How was Istio installed?
helm templte and kubectl apply
Environment where bug was observed (cloud vendor, OS, etc)
Affected product area (please put an X in all that apply)

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience

Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.

Hey @wansuiye, we have made some recent changes for this type of issue. Can you try again on later versions (1.2 preferably, but the changes should be in 1.1.7+)?
If its still not working can you include the config that you have

Presumed fixed in 1.1.7+. Please update if this is not the case


Ensure that @types/* used in emitted declarations are in dependencies

I'm not sure if this is in scope of Knip, but it feels like it could be. In a nutshell, if I have a module like this:
// bar/src/index.ts
import type { Foo } from "foo";
export const bar = (): Foo => ...

And foo comes with a corresponding @types/foo, then I need to make sure that it's actually in dependencies. Otherwise bar/dist/index.d.ts will be broken in any consumer of bar that doesn't have @types/foo in its dependency tree.
The complication I'm seeing is determining whether a @types/* actually ends up being used in dist. And putting all @types/* in dependencies doesn't make sense, obviously. Does TypeScript have an API of any sort for checking this?
More context in this Stack Overflow question.

Yes, I think Knip can help here. Related to #241.

Currently Knip just expects @types/* packages to be in devDependencies (with --production --strict).
So yeah. the issue is that @types/pkg sometimes need to be in dependencies.
More refs:

Ask in TS Discord: https://discord.com/channels/508357248330760243/640177429775777792/1156692609763389562
https://github.com/microsoft/types-publisher/issues/81

To be continued

Any chance you could whip up a repro? One or more cases would be very helpful. Running in strict production mode should "fail" now.

Spent half an hour trying to understand why I can't get my repro to fail, when I realized that Knip actually never complained :joy: Knip is fine with @types/* being anywhere, or missing. This repro currently passes, but needs to fail.

Updated the repro to also include a case without @types/* (it shouldn't report @microsoft/tsdoc as unused).

@alecmev you can often take advantage of duck typing to sever @types dependencies, i.e. define an interface with just your needs in your public API that's compatible with the other package's type. Just doing my part to fight dependency bloat :)
If you know examples of popular npm packages that bundle TS types and put @types in prod dependencies, I'd be interested to hear about them. Packages seem to be all over the place in how they handle the issue of transitive @types deps.

@alecmev you can often take advantage of duck typing to sever @types dependencies, i.e. define an interface with just your needs in your public API that's compatible with the other package's type. Just doing my part to fight dependency bloat :)

@danvk Do you know of examples or ways to basically replace the transitive type deps with a dummy? Just to avoid the Cannot find module 'pkg' error. I'm thinking just any or declare module 'pkg' could do in my case: #283. Still not sure whether that use case is valid to begin with. Interested to hear your thoughts :)

@danvk Do you know of examples or ways to basically replace the transitive type deps with a dummy? Just to avoid the Cannot find module 'pkg' error. I'm thinking just any or declare module 'pkg' could do in my case: #283. Still not sure whether that use case is valid to begin with. Interested to hear your thoughts :)

What I meant was more replacing:
import {SomeType} from 'big-complicated-package';

export function foo(obj: SomeType) { ... }

with:
export interface SomeType {
  just: string;
  fields: number;
  you: boolean;
  careAbout: Date;
}

export function foo(obj: SomeType) { ...  (You should test that your version of the type is compatible with the canonical one in your tests, but then you're in devDependency land.)
For severing transitive dependencies without code changes, that's a messy topic and I have a few thoughts :)

A particularly egregious example is https://github.com/adelsz/pgtyped/issues/451, where a runtime-only dependency (antlr4ts) that has no impact on the type declarations still pulls in 100+ .d.ts files. I asked about this on Stack Overflow. You can use the paths property of your tsconfig.json to stub out declarations for a transitive dependency.
Bloomberg apparently has an internal tool called dts-shake that can handle this in a more systematic way, but they've never gotten around to open sourcing it.

Thanks a lot for chiming in and the references, Dan!
For simple types replacing external types is fine, but I guess in many cases this isn't very ergonomic or sustainable.
Just stumbled upon https://github.com/timocov/dts-bundle-generator. Interesting project! Has a few issues that prevents me from using it for Knip yet, but I'll play with it some more and keep watching it. I guess as long as Knip isn't imported and used programmatically (but only used from CLI) I can get away with it.

Since I haven't had any more reports about this being an issue, I'm going to close it. Separating dependencies and devDependencies is a good best practice in general, and good default baseline for Knip. Also, there are workarounds (e.g. inline, peer deps).

Sorry for two messages, forgot to add:

Since I haven't had any more reports about this being an issue

My suspicion is that most of the time people get lucky and there's a fitting @types/* somewhere else in the dependency tree, and in the unlucky cases, most people never type-check with skipLibCheck: false, so they just live with any.

the cost/impact does not warrant the outcome

I respect that 😉 I do agree that this is somewhat "pedantic" territory.


Cannot connect to any of my servers that have installations of code-server on ubuntu anymore.

I started getting this error yesterday.
I'm unable to connect using tunnel connection to my vscode servers through a browser.
Using SSH from the client still works, but the tunnel that I use when I don't have a locally install vscode client doesn't.
Can't figure out why. I only have an "Opening Remote" notification at the lower left of my window, which is normal, but it should connect after a while. On the server side, the code-server starts without warnings and wakes up properly.
It just never finishes initializing and I need to close the connection after a while.
Version: 1.79.1
Commit: 4cb974a7aed77a74c7813bdccd99ee0d04901215
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: vscode.dev

Are you still using the code-server CLI? Back in December we released the new code CLI which includes tunnels and is the recommended way to connect.
If so, please grab two things:

Run the tunnel via code tunnel --verbose on the server side, and grab logs from when you try to connect
Check for any console errors on vscode.dev

Thanks!

I have the same issue, using SSH started yesterday after upgrade. VSCode Insiders build works fine. Preview release of SSH extension with Stable does not work.

Are you still using the code-server CLI? Back in December we released the new code CLI which includes tunnels and is the recommended way to connect.
If so, please grab two things:

Run the tunnel via code tunnel --verbose on the server side, and grab logs from when you try to connect
Check for any console errors on vscode.dev

Thanks!

Hey that is... I was looking for updates on that and I did find it annoying that it kept wartning me about the old version of my tunnel but when I was checking, there was no update.
However this code-server installation is setup on an ubuntu headless machine which I want to be able to connect to through the web. That code cli version is windows only... or am I missing something... I trully think I'm missing something like a procedure to properly install it using ssh on my ubuntu machine? No GUI on that machine either. it has to be terminal based and only available through tunnel and ssh.

The VS Code CLI si available on all platforms and does not require a GUI. You can get it under the "CLI" heading on all platforms on the downloads page: https://code.visualstudio.com/#alt-downloads

And it's not that right: https://github.com/coder/code-server
Sorry for being so persistent man, but everyone keeps referring to each version as vscode, and code-server and code cli and vscode server... and I'm not sure if these are just similarly named DIFFERENT iterations or simply the one and only vscode.

That project is not something the vs code team has anything to do with. If you're having a problem with it, please open an issue on their repo.

That project is not something the vs code team has anything to do with. If you're having a problem with it, please open an issue on their repo.

I am not using that project. I just asked if it was the same or not.
In any case this: https://code.visualstudio.com/blogs/2022/07/07/vscode-server is related to a project from the vs code team.
This is the one I'm using now and I'm looking for a way to use the latest version. So How will I install this: https://code.visualstudio.com/#alt-downloads on an ubuntu server? The vscode-server project had an install.sh file. The code cli project doesn't have one... or I can't find it.

ah, sorry, misunderstood.
To install that, you would download it directly, uncompress it, and run the CLI. We have a todo to add a nice rustup.rs-like experience for the website.
curl https://code.visualstudio.com/sha/download?build=stable&os=cli-alpine-x64 -o vscode-cli.tar.gz
tar -xvf ./vscode-cli.tar.gz
./code tunnel

ah, sorry, misunderstood.
To install that, you would download it directly, uncompress it, and run the CLI. We have a todo to add a nice rustup.rs-like experience for the website.
curl https://code.visualstudio.com/sha/download?build=stable&os=cli-alpine-x64 -o vscode-cli.tar.gz
tar -xvf ./vscode-cli.tar.gz
./code tunnel

Ok Then. So it’s manual installation in my case I guess.
I saw the download tar and run ./code tunnel part.
I can add here that if you move the executable code to \usr\local\bin(which should also be in your PATH) you won’t need to run./codecommands but straight upcode` from every location. Makes the experience much like having it installed.
That little thing might make a useful addition to that article here that describes how to set up a tunnel: https://code.visualstudio.com/docs/remote/tunnels#_using-the-code-cli
Additionally, I created a run_server and stop_server sh script, aliased them, and have those to start and stop the developing environment. Other people might prefer to have them auto-start or something.
I'm really happy to have my web development environment back!