Unable to connect to internet and update channels upon creating NixOS WSL2 instance

Bug description

I tried to update the nix channels as instructed, but was unable to connect to internet to update.
To Reproduce
Steps to reproduce the behavior:
Install NixOS-WSL and open a new nixOS shell.
Read welcome message and then try to update with sudo nix-channel --update
Attempts to resolve
I tried to add google and cloudflare dns servers manually, but still no resolution.
Logs
[nixos@nixos:~]$ nixos-wsl-welcome
Welcome to your new NixOS-WSL system!

Please run `sudo nix-channel --update` and `sudo nixos-rebuild switch` now, to ensure you're running the latest NixOS and NixOS-WSL versions.

If you run into issues, please report them on our Github page at https://github.com/nix-community/NixOS-WSL or come talk to us on Matrix at #wsl:nixos.org.

❄ Enjoy NixOS-WSL! ❄

Note: this message will disappear after you rebuild your system. If you want to see it again, run `nixos-wsl-welcome`.

[nixos@nixos:~]$ sudo nix-channel --update
warning: error: unable to download 'https://nixos.org/channels/nixos-23.11': Couldn't resolve host name (6); retrying in 290 ms
warning: error: unable to download 'https://nixos.org/channels/nixos-23.11': Couldn't resolve host name (6); retrying in 585 ms
warning: error: unable to download 'https://nixos.org/channels/nixos-23.11': Couldn't resolve host name (6); retrying in 1002 ms
warning: error: unable to download 'https://nixos.org/channels/nixos-23.11': Couldn't resolve host name (6); retrying in 2308 ms
error: unable to download 'https://nixos.org/channels/nixos-23.11': Couldn't resolve host name (6)

[nixos@nixos:~]$ cat /etc/resolv.conf
# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
# [network]
# generateResolvConf = false
#nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>

[nixos@nixos:~]$ sudo cat /etc/wsl.conf
[automount]
enabled=true
mountFsTab=false
options=metadata,uid=1000,gid=100
root=/mnt

[boot]
command=
systemd=true

[interop]
appendWindowsPath=true
enabled=true

[network]
generateHosts=true
generateResolvConf=true
hostname=nixos

[user]
default=nixos

[nixos@nixos:~]$ ping -c 2 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.

--- <IP_ADDRESS> ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1079ms

[nixos@nixos:~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1280 qdisc mq state UP group default qlen 1000
    link/ether ...{REDACTED}... brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/20 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 ...{REDACTED}.../64 scope link
       valid_lft forever preferred_lft forever

[nixos@nixos:~]$ cat /etc/resolv.conf
# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
# [network]
# generateResolvConf = false
#nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>

[nixos@nixos:~]$ ping -c 2 google.com
ping: google.com: Temporary failure in name resolution

WSL version

C:\Users\{REDACTED_USER}>wsl -l -v
  NAME                   STATE           VERSION
* NixOS                  Running         2
  Ubuntu-22.04           Stopped         2
  docker-desktop-data    Stopped         2
  docker-desktop         Stopped         2

C:\Users\{REDACTED_USER}>wsl -v
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.3996

Are you able to access the internet from another WSL distro? As you can't ping <IP_ADDRESS> it's likely an issue with WSL, not NixOS, because it shouldn't usually touch the network interface setup

Are you able to access the internet from another WSL distro? As you can't ping <IP_ADDRESS> it's likely an issue with WSL, not NixOS, because it shouldn't usually touch the network interface setup

I have checked for connectivity in my Ubuntu WSL distro and my NixOS WSL distro and they both seem to have the same issue. I have followed standard instructions on the WSL and net re: setting .wsl and .wslconfig config files and haven't been able to find any resolution.

Sorry but we cannot offer generic WSL support. If it is also broken in Ubuntu then this is not a NixOS WSL specific issue. Please seek the wider Internet for more help.

I am experiencing a similar issue, except other distros in WSL do work. I think it might be something funky with the network I'm on because I've had better luck using my home network in the past. When I go into my work's office, I can no longer use NixOS in WSL, but Ubuntu works out of the box.
Can anyone give me guidance on how I might troubleshoot this and what I should be looking for? I can't ping any addresses from the NixOS side.

fix WSL networking in corporate environments: https://gist.github.com/machuu/7663aa653828d81efbc2aaad6e3b1431
TLDR:
sudo bash -c 'echo -e "[network]
generateResolvConf = false" > /etc/wsl.conf
rm /etc/resolv.conf
echo -e "options timeout:1 attempts:1 rotate
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>" > /etc/resolv.conf
chattr -f +i /etc/resolv.conf'
#From <https://github.com/microsoft/WSL/issues/5420>

I'm pretty skeptical of this solution because it isn't a DNS issue: my resolv.conf already has cloudflare's nameservers specified.
Instead, it is the complete inability to ping any external server when using internet from that location. This is by IP, not domain name. I can take the same device back home and everything works fine, so it is definitely something with this specific network. That being said, it only affects NixOS-WSL and there is not much willpower from the organization to dig into this issue with me as a result.
I understand this is a volunteer community that can't devote significant resources to solving my work problems, but it seems there's some issue with the networking in NixOS-WSL that fails in this setup. I consider myself fairly savvy, but I'm not sure where to look to troubleshoot it, just that I know it isn't DNS.

@justinrubek you could try setting networking.firewall.enable = false; and see if that helps. Besides that, I don't really see a way in which NixOS touches the network configuration that could result in it not working, while other distros do. If that doesn't help, try cheking for diffrences in the outputs of ip a and ip r between NixOS and a working distro


merge applicable javadoc improvements from commits 07e67291fe62826332…

…880f4feedb948976273700, f26cbab7cca9d6e71a35b701b19046277a85989a and e4b737224f204d3b7a343ea805f03fb204f4db02 from master into 2.x

Integrated, thanks.


Super class that extends from Presented*****Layout

There is no multiple inheritance, but I would like to know if somehow it's possible to create a base class that extends from any of the Presented****Layouts.

I'm not sure I understand. Can you write a sample code, even if it's not compiler-valid?

So I have two different Views
public class SearchGridMusicView extends PresentedLinearLayout
public class HomeView extends PresentedScrollView
And I want to create a base class for both
public class BaseView extends PresentedLinearLayout,PresentedScrollView
So I can use it like
public class SearchGridMusicView  extends BaseView
public class HomeView extends BaseView

Yeah this is the problem with inheritance (and Android relies much on it), because it's not flexible at all.
The only easy fix I see is for your 2 views to have the same base layout, like a FrameLayout. And then each one adds its custom layout LinearLayout and ScrollView.
The drawback would be that Android will render a useless FrameLayout, but the cost is negligible.
I don't know what's in your BaseView class, but it may be possible to apply the composition pattern rather than inheritance. Also, if you are a Kotlin user, you would may be able to use Traits to solve this :)


Android: Expose textBreakStrategy on Text and TextInput

Android has a text API called breakStrategy for controlling how paragraphs are broken up into lines. For example, some modes support automatically hyphenating words so a word can be split across lines while others do not.
One source of complexity is that Android provides different defaults for breakStrategy for TextView vs EditText. TextView's default is BREAK_STRATEGY_HIGH_QUALITY while EditText's default is BREAK_STRATEGY_SIMPLE.
In addition to exposing textBreakStrategy, this change also fixes a couple of rendering glitches with Text and TextInput. TextView and EditText have different default values for breakStrategy and hyphenationFrequency than StaticLayout. Consequently, we were using different parameters for measuring and rendering. Whenever measuring and rendering parameters are inconsistent, it can result in visual glitches such as the text taking up too much space or being clipped.
This change fixes these inconsistencies by setting breakStrategy and hyphenationFrequency to the appropriate values during measuring.
Test plan (required)
Verified the textBreakStrategy prop works in a test app. Also, my team's app uses this change.
Adam Comella
Microsoft Corp.

Looks great! Just a question about the default value:
It looks like Android's default text break strategy is SIMPLE:
https://github.com/android/platform_frameworks_base/blob/master/core/java/android/widget/TextView.java#L743
What do you think of defaulting to simple in React Native? This way:

We're not changing the behavior for everyone
We're not introducing a potential perf hit for everyone. I tried searching the Android docs for how expensive using the HIGH_QUALITY text break strategy is but couldn't find anything.

I fixed two tiny things in the docs, hope you don't mind: https://github.com/facebook/react-native/pull/11007/commits

@mkonicek

I fixed two tiny things in the docs, hope you don't mind: https://github.com/facebook/react-native/pull/11007/commits

That's fine with me. Thanks!

It looks like Android's default text break strategy is SIMPLE: https://github.com/android/platform_frameworks_base/blob/master/core/java/android/widget/TextView.java#L743. What do you think of defaulting to simple in React Native?

Despite the code you've referenced, I'm pretty sure TextView defaults to BREAK_STRATEGY_HIGH_QUALITY and EditText defaults to BREAK_STRATEGY_SIMPLE. I implemented the PR such that RN matches these defaults. Here's my evidence:

The Android docs for setBreakStrategy indicate that these values are the defaults.
styles.xml in the Android source agrees with the docs (my Android experience is limited so I'm not sure if/when this file is used):

TextView's breakStrategy
EditText's breakStrategy

Here's the commit which introduced the breakStrategy feature. The defaults described in its commit message match the currently stated defaults from the docs.

Don't know how I missed this in the Android docs, sorry!

The default value for TextView is BREAK_STRATEGY_HIGH_QUALITY

@facebook-github-bot shipit

There is a merge conflict in TextInput.js now, sorry about that! Can you rebase please?

@mkonicek I rebased my branch on master and pushed. One of the conflicts was from one of my other PRs.

Thanks @rigdern!
The Circle CI test failure looks related:
TextInputTestCase failed:
E/AndroidRuntime( 2456): Process: com.facebook.react.tests, PID: 2456
E/AndroidRuntime( 2456): java.lang.NoSuchMethodError: android.widget.EditText.getBreakStrategy
E/AndroidRuntime( 2456): 	at com.facebook.react.views.textinput.ReactTextInputShadowNode.measure(ReactTextInputShadowNode.java:109)
...

I'm hoping the documented way to run tests locally still works? http://facebook.github.io/react-native/docs/testing.html#integration-tests-android

Travis failure here looks like garbage, I'll rerun it. AFAICT only flaky tests and merge problems are preventing this from being accepted now....

@lacker You mentioned merge problems so I just rebased on master and pushed. Is there anything else you need from me before this can be merged?

No I will merge as soon as Circle/Travis look ok.

@lacker Travis passed but CircleCI is still pending for some reason. It has been 2 days since I pushed so it seems like something went wrong and CircleCI will never run on my change. Is there a way to kick a CircleCI build? Should I just push again?
Here's the list of all of the CircleCI builds for this PR: https://circleci.com/gh/facebook/react-native/tree/pull%2F11007. You can see the last one was from a change I pushed 10 days ago.

Argh.  Yeah, can you try just pushing again?

@lacker yay, CircleCI finally ran on this PR. Both Travis and Circle are now done.

OK it looks like the FB-internal continuous integration is failing because there is a test which explicitly constructs a ReactTextUpdate using the old signature. I'd like to just kind of move on with this though. How about adding a constructor which keeps the old signature as well?

@lacker The iOS build failed on Travis but this PR adds an Android-only feature. I suspect the Travis failure is unrelated to my change. How do you want to handle this?

Yeah Travis was broken yesterday. Our sync script insists that the tests pass so let me just rerun travis and once that works I will land this.


Progress towards Leptos 0.7.0-alpha

This PR makes progress towards updating leptos-use for Leptos 0.7 (now on 0.7.0-alpha).
Given the extensive nature of these changes, this PR may be impractical from a review standpoint. However, it may at least be useful as a point of reference for what needs to be done.
There are four main blockers at the moment:

It appears queue_microtasks is not yet implemented in 0.7
watch is not yet implemented in 0.7 as noted here on Discord.
There is no equivalent to leptos::ev::Custom. This may simply be an oversight, as it appears to be very simple.
The HtmlElement struct has gotten much more complicated and I'm not sure what the best approach is for managing ElementMaybeSignal-related code.

With all this in mind, it seems like the most helpful way forward would be implementing the missing items in 1-3, and that might be pretty easy!
In any case, I hope this helps!

queue_microtask has just been added!
https://github.com/leptos-rs/leptos/pull/2703

So far everything seemed very good. So I merged. I'm very glad that you do this major port! So do whatever is most comfortable for you and open the next PR with any progress you have 👍🏼


POSIX metadata and version-controlled file sharing

See https://github.com/docker/pinata/issues/44

This functionality can be provided by stevvooe/contintuity.

Is this done? Rejected as a feature? What's the status?

This is not fully done but Irmin let's you now store metada with the nodes: https://github.com/mirage/irmin/blob/master/lib/irmin.mli#L1009-L1024
For the Git backend, this just exposes the symlink/exec/dir attributes. We can imagine more expressive metadata, but this is not yet done. Should I re-open that issue to keep track of that?

If you want to store and export POSIX file systems from a datakit repository, I think this isn't yet complete. It's cool that Irmin now has git's minimal metadata so perhaps this issue should track that. Perhaps open another ticket for full POSIX metadata if you think that's a worthwhile development direction?

I'm reopening the issue until a full end-to-end implementation come to live.

It's cool that Irmin now has git's minimal metadata

The metadata object can be anything, not just the Git's metadata (which are the currently only one implemented). Just a matter of instantiating the functor differently :p


Metal: vertex descriptor is built without using the location information

This is the code that creates Metal vertex descriptors:
https://github.com/gfx-rs/gfx/blob/a571ae5a15b2fd7bdd457c9d2d6189167ccfbf54/src/backend/metal/src/device.rs#L1011-L1014
The expected behavior is that the location in the vertex shader matches the location in the attributes array; instead this code fills the array from 0 to count-1, which doesn't work for vertex shaders that have 3 input attributes with locations 0, 2, 4. The array index should instead use VkVertexInputAttributeDescription::location.

@zeux this is an unbelievably precise definition of a bug, almost carrying a fix in it self :). Thank you for chasing this down! Fix is on the way.

Thanks! FWIW based on cursory inspection CTS doesn’t seem to cover this, I filed https://github.com/KhronosGroup/VK-GL-CTS/issues/121 for this as well.


Menu bar is frozen when launching the app on macOS

Hi, I found an issue on macOS 10.15.
When I launch the example apps, the window will be focused but the menu bar will be frozen.
Nothing will happen when I put the mouse cursor on the apple icon.
So, to use the menu bar, I need to click another window or the desktop once and click the app window again.
I found some related posts on stackoverflow.

Cocoa application menu bar not clickable
Top Left Menu Bar Is Frozen when Main Window Shows Up

So, I tried to use [uiprivNSApp() activateIgnoringOtherApps:YES]; on uiInit but it did't work.
I also tried to use it with the app delegate like this but it didn't work.
-(void)applicationWillFinishLaunching:(NSNotification *)aNotification
{
    [uiprivNSApp() setActivationPolicy:NSApplicationActivationPolicyRegular];
}

-(void)applicationDidFinishLaunching:(NSNotification *)notification
{
    [uiprivNSApp() activateIgnoringOtherApps:YES];
}

Anyone know how to solve this issue?

I can't reproduce this issue, menu correctly receives events on first try for me.

Hmm, the menu bar is wonking fine on my wxWigets app. So, I thought it's a libui issue...
Here is my environment.

OS: 10.15.5
Arch: x86_64
Compiler: Apple clang 12.0.0
Python: 3.10.6
Meson: 1.2.1
Meson Options: None (I mean, used default options)

And I made sure it can pass the unit tests.
I'm running mac on Windows with VirtualBox, so the VM might be the cause.
But I think there is a workaround because other GUI libraries are working fine.

I'm running mac on Windows with VirtualBox, so the VM might be the cause.

Yes and that's an unsupported environment, so I can't really investigate any further..

But I think there is a workaround because other GUI libraries are working fine.

If you can figure out a simple fix, we'll take another look at this issue.

I found another post about the menu bar. and it solved my problem.
Why doesn't activate(ignoringOtherApps:) enable the menu bar?
So, it's an issue of macOS 10.15.
and the policy setting should be defined in applicationDidFinishLaunching.
@implementation uiprivAppDelegate

...

-(void)applicationDidFinishLaunching:(NSNotification *)notification
{
    [NSApp setActivationPolicy:NSApplicationActivationPolicyRegular];
}

@end

And I noticed wxWidgets is using the same method!
wxWidgets/src/osx/cocoa/utils.mm at master · wxWidgets/wxWidgets

I found out Eclipse has the same method.
eclipse.platform.swt/bundles/org.eclipse.swt/Eclipse SWT/cocoa/org/eclipse/swt/widgets/Display.java at master · eclipse-platform/eclipse.platform.swt
I found it in tk as well.
tk/macosx/tkMacOSXInit.c at main · tcltk/tk
So, it should be applied to libui as well?
I'll send PR later.

I think I figured why I can't reproduce this issue: you're calling Cocoa APIs directly in your app.
Calling activate before setting an activation policy is what triggers the freeze. If activate is never called, menu works normally.
Related PR that enables activation by default: https://github.com/libui-ng/libui-ng/pull/100

And I noticed wxWidgets is using the same method!
wxWidgets/src/osx/cocoa/utils.mm at master · wxWidgets/wxWidgets

The wxWidgets approach looks best to me: none of these hacks should be necessary if we detect that we're running in a proper .app bundle !

Calling activate before setting an activation policy is what triggers the freeze. If activate is never called, menu works normally.

No, the master branch will make menu frozen, so activateIgnoringOtherApps was not the cause.
Just moving setActivationPolicy to applicationDidFinishLaunching resolved the issue in my case.
You can see my commit for the fix.
https://github.com/matyalatte/libui-ng/commit/e5923a7902f69d46cc0944a655a5b22fd947b9bc
As I posted before, eclipse and tk (and maybe wxWidgets as well?) had the same issues and they moved the policy setting to the app delegate to fix the issues.
So, I think it's a proper way to fix.

The wxWidgets approach looks best to me

Yeah, so I should edit the app delegate like this?
-(void)applicationDidFinishLaunching:(NSNotification *)notification
{
	CFURLRef url = CFBundleCopyBundleURL(CFBundleGetMainBundle());
	CFStringRef path = CFURLCopyFileSystemPath (url, kCFURLPOSIXPathStyle);
	CFRelease(url);

	if (!CFStringHasSuffix(path, @".app")) {
		/* don't use setActivationPolicy outside this function
		 * or the menu bar won't work properly on macOS 10.15
		 * see https://github.com/libui-ng/libui-ng/issues/225
		 *
		 * don't check for a NO return;
		 * something (launch services?) causes running from application bundles to always return NO
		 * when asking to change activation policy, even if the change is to the same activation policy!
		 * see https://github.com/andlabs/ui/issues/6 */
		[uiprivNSApp() setActivationPolicy:NSApplicationActivationPolicyRegular];
	}
}

Yeah, so I should edit the app delegate like this?

Yes, that looks mostly right. Few nits I see there:
BOOL/YES/NO not bool/true/false on Darwin.
Missing CFRelease(path);, leaks?
Comment style is //

Also needs a comment to explain the edge case:
} else if ([uiprivNSApp() activationPolicy] == NSApplicationActivationPolicyAccessory) {
		// The app is an agent app that runs in the background and doesn't appear in the Dock.
		activate = true;
}

I sent the PR for the fix!

Missing CFRelease(path);, leaks?

Idk how CFStringRef will work cause I just coiped the wxWidgets code.
But should I report it to the wxWidgets team?

But should I report it to the wxWidgets team?

No I think the wxWidgets code is safe. The smart pointer appears to release when it is out of scope:
wxString app = wxCFStringRef(path).AsString();

wxCFStringRef(WX_NSString ref)
        : wxCFRef< CFStringRef >((WX_OSX_BRIDGE_RETAINED CFStringRef) ref)
    {
    }

 ~wxCFRef()
    {   reset(); }

    void reset()
    {
        wxCFRelease(m_ptr);
        m_ptr = nullptr;
    }


Deployment not found?

Does this occur consistently?
Repro steps:

Action: azureFunctions.deploy
Error type: 404
Error Message: Deployment '696e0315e46f4fdbb520055f46ad6c20' not found.
Version: 1.0.1
OS: darwin
OS Release: 19.6.0
Product: Visual Studio Code
Product Version: 1.51.1
Language: en

Call Stack
new RestError extension.bundle.js:46:109835
extension.bundle.js:48:167633
processTicksAndRejections task_queues.js:94:5

Please add repro steps


Installation of v0.3.0 failed under Linux due to missing ordered-namespace

When I installed v0.3.0 via pip:

pip install Jupyter-Video-Widget

the ordered-namespace package wasn't installed. I had to do a separate:

pip install ordered-namespace

before installing the video widget.
The repo history here shows ordered-namespace was added to requirements.txt relatively recently.
Perhaps this problem will be solved by cutting a new release for the Python Package Index.

@stevesimmons thanks for letting me know.  I'll fix this when I get home this evening.


Windows glider source code??

Hi again! Could you open the windows project too?? That could be easily compiled with winemaker on linux... Thanks anyway.

I don't have the Windows sources. :-(


Re-enable arrow tests

Currently, some arrow tests are failing because of weird behaviour around timestamps, so we've disabled them.
Tests disabled  in https://github.com/palantir/spark/pull/326/commits/52cbda2e67cf37346f0ca7f90a2f5a8659447d1d

As part of https://issues.apache.org/jira/browse/SPARK-26032 in https://github.com/apache/spark/pull/23021, these tests were moved and reenabled


Az/custom annotation

@azhavoro What is wrong? Also no problems are reported in UI.
2018-12-26 15:29:41,834 DEBG 'rqworker_low' stderr output:
/home/django/cvat/apps/auto_annotation/model_loader.py:30: DeprecationWarning: from_ir() method of IENetwork is deprecated. Please use IENetwork class constructor to create valid IENetwork instance
network = IENetwork.from_ir(model=self._model, weights=self._weights)
[2018-12-26 15:29:41,834] ERROR cvat.server.task_6: exception was occurred during auto annotation of the task
Traceback (most recent call last):
File "/home/django/cvat/apps/auto_annotation/views.py", line 242, in create_thread
update_progress=update_progress,
File "/home/django/cvat/apps/auto_annotation/views.py", line 199, in run_inference_engine_annotation
"detections": model.infer(frame),
File "/home/django/cvat/apps/auto_annotation/model_loader.py", line 44, in infer
_, _, h, w = self._input_layout
TypeError: 'openvino.inference_engine.ie_api.InputInfo' object is not iterable

@nmanovic IE python API changes are cause of issue. I've added fix and it works with R3 and R5. I suggest specify supported version of OpenVINO in documentation at least.


Error running the python script

curl https://gist.githubusercontent.com/nondanee/f157bbbccecfe29e48d87273cd02e213/raw | python
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3304  100  3304    0     0   8787      0 --:--:-- --:--:-- --:--:--  8763
vscode 1.46.0 x64
Traceback (most recent call last):
  File "<stdin>", line 60, in <module>
  File "/Users/xiaoweiz/anaconda3/lib/python3.7/urllib/request.py", line 222, in urlopen
    return opener.open(url, data, timeout)
  File "/Users/xiaoweiz/anaconda3/lib/python3.7/urllib/request.py", line 531, in open
    response = meth(req, response)
  File "/Users/xiaoweiz/anaconda3/lib/python3.7/urllib/request.py", line 641, in http_response
    'http', request, response, code, msg, hdrs)
  File "/Users/xiaoweiz/anaconda3/lib/python3.7/urllib/request.py", line 569, in error
    return self._call_chain(*args)
  File "/Users/xiaoweiz/anaconda3/lib/python3.7/urllib/request.py", line 503, in _call_chain
    result = func(*args)
  File "/Users/xiaoweiz/anaconda3/lib/python3.7/urllib/request.py", line 649, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 404: Not Found

看了下现在没问题
你再试试呢
60 行是 https://gist.github.com/nondanee/f157bbbccecfe29e48d87273cd02e213#file-helper-py-L60
访问的是 https://raw.githubusercontent.com/Microsoft/vscode/1.46.0/.yarnrc
可能是当时 vscode 仓库 1.46.0 的 tag 还没打

VS Code crashes after running the script to replace ffmpeg.dll. Seems to be related to #86

#86 should be fixed, please check #87

No, the solution in #87 doesn't work any more.
vscode 1.46.0
electron 7.3.1
Here's the header of the crash report.
System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    DYLD, [0x5] Code Signature

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: @rpath/libffmpeg.dylib
  Referenced from: /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework
  Reason: no suitable image found.  Did find:
	/Applications/Visual Studio Code.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libffmpeg.dylib: code signature in (/Applications/Visual Studio Code.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libffmpeg.dylib) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.

Does manual replacement work? https://github.com/nondanee/vsc-netease-music/issues/87#issuecomment-610687595

No.

Hello
The latest vscode compatible version is 1.45.1


CUDA runs out of memory

Has anyone run into a running out of GPU memory issue when running the imagine command? Below is the error I get.
RuntimeError: CUDA out of memory. Tried to allocate 2.00 MiB (GPU 0; 6.00 GiB total capacity; 4.47 GiB already allocated; 716.80 KiB free; 4.48 GiB reserved in total by PyTorch)

I tried to use both gc.collect() and torch.cuda.empty_cache() but neither worked.

I just reduced num_layers to 16 (I've got 8 GB of dedicated memory). However it would be nice to use the shared memory too (if it's possible here).

I just reduced num_layers to 16 (I've got 8 GB of dedicated memory). However it would be nice to use the shared memory too (if it's possible here).

Has anyone run into a running out of GPU memory issue when running the imagine command? Below is the error I get.
RuntimeError: CUDA out of memory. Tried to allocate 2.00 MiB (GPU 0; 6.00 GiB total capacity; 4.47 GiB already allocated; 716.80 KiB free; 4.48 GiB reserved in total by PyTorch)

I tried to use both gc.collect() and torch.cuda.empty_cache() but neither worked.

You can check your GPU's memory usage with nvidia's CLI tool nvidia-smi which is provided with the cuda toolkit.
This unfortunately comes with the territory. The code runs best on a graphics card with 16 GiB. If you've got less than that, here are some parameters you can change to lower your VRAM usage.
decrease --image_width
This one lowers memory usage a lot. I've even done this on a 16 GiB colab instance just so I could run 64 hidden layers on a 256px image. Just keep in mind that 512 is a decent default. You'll probably want to decrease in multiples of 8 I assume, but I dunno, maybe it doesn't matter. At any rate the obvious tradeoff here is that you'll get a less detailed output.
lower --batch_size (default is 4).
increase --gradient_accumulate_every (default is 4).
This will generate more images before calculating the loss and running backpropagation (the memory intensive bit). Each images loss is divided by the e.g. the default, 4, because we don't want to punish the network without giving it a chance to change.
decrease --num_layers (default is 32)
This one is basically a requirement on a GPU with less than 16 GiB of memory. The default of 32 is meant for Colab users and is honestly a bit high considering the consumer GPU space doesn't tend to have cards more than 8 GiB of vram. Lowering to 16 will get you below 8 GiB of vram but the results will be more abstract and silly. If you do decrease this value make sure you only do it as much as you need and no more, because more hidden layers seems to help quite a bit.

Has anyone run into a running out of GPU memory issue when running the imagine command? Below is the error I get.
RuntimeError: CUDA out of memory. Tried to allocate 2.00 MiB (GPU 0; 6.00 GiB total capacity; 4.47 GiB already allocated; 716.80 KiB free; 4.48 GiB reserved in total by PyTorch)

I tried to use both gc.collect() and torch.cuda.empty_cache() but neither worked.

You can check your GPU's memory usage with nvidia's CLI tool nvidia-smi which is provided with the cuda toolkit.
This unfortunately comes with the territory. The code runs best on a graphics card with 16 GiB. If you've got less than that, here are some parameters you can change to lower your VRAM usage.
decrease --image_width
This one lowers memory usage a lot. I've even done this on a 16 GiB colab instance just so I could run 64 hidden layers on a 256px image. Just keep in mind that 512 is a decent default. You'll probably want to decrease in multiples of 8 I assume, but I dunno, maybe it doesn't matter. At any rate the obvious tradeoff here is that you'll get a less detailed output.
lower --batch_size (default is 4).
increase --gradient_accumulate_every (default is 4).
This will generate more images before calculating the loss and running backpropagation (the memory intensive bit). Each images loss is divided by the e.g. the default, 4, because we don't want to punish the network without giving it a chance to change.
decrease --num_layers (default is 32)
This one is basically a requirement on a GPU with less than 16 GiB of memory. The default of 32 is meant for Colab users and is honestly a bit high considering the consumer GPU space doesn't tend to have cards more than 8 GiB of vram. Lowering to 16 will get you below 8 GiB of vram but the results will be more abstract and silly. If you do decrease this value make sure you only do it as much as you need and no more, because more hidden layers seems to help quite a bit.

@afiaka87 Thanks for your detailed response, that is very helpful. I will check out the Colab notebook, thanks. I've been using an EC2 to play around with this, but that gets expensive pretty quickly.

@afiaka87 Thanks for your detailed response, that is very helpful. I will check out the Colab notebook, thanks. I've been using an EC2 to play around with this, but that gets expensive pretty quickly.

@jnelson16  I've been using an EC2 to play around with this, but that gets expensive pretty quickly.

No kidding! Colab is still the cheapest possible option, but I've found vast.ai to have really good pricing and some awesome RTX 3090 (24 GiB VRam) instances. I don't think they have any security guarantees whatsoever though, so that's the tradeoff. But if you're just generating stuff with deep-daze, it can be awesome.

@jnelson16  I've been using an EC2 to play around with this, but that gets expensive pretty quickly.

No kidding! Colab is still the cheapest possible option, but I've found vast.ai to have really good pricing and some awesome RTX 3090 (24 GiB VRam) instances. I don't think they have any security guarantees whatsoever though, so that's the tradeoff. But if you're just generating stuff with deep-daze, it can be awesome.

@afiaka87 hello I am new to AI, so new that I literally learned all this last night. I tried running the deep daze but also ran out of memory just like @jnelson16. I tried typing in
decrease --image_width
and
--image_width
but it seems I have the wrong syntax. Would you mind explaining how I would type these commands into my terminal to get the right outcome?

Hello i get this strange error the hole time ,but there is still spaces on my gpu ram left .
I tried using --numlayers 16 but the error is still the same
RuntimeError: CUDA out of memory. Tried to allocate 128.00 MiB (GPU 0; 4.00 GiB total capacity; 2.47 GiB already allocated; 0 bytes free; 2.49 GiB reserved in total by PyTorch)


Why not try regression too?

Hey I was wondering if we can use the same code to perform regression:

use distance the distances from gzip to create a distance matric
perform kernel-ridge regression similar to https://www.qmlcode.org/index.html

If it works for classification, I expect it to work for regression as well.
Depends of course on the quantity too. For some quantities such as atomization energies I would
suggest to first transform the molecule to a representation vector such as the Coulomb Matrix before pairwise compressing
the representation vectors.
I can test and contribute this if there is interest. Would also be interested in collaborating!.
Best,
Jan Weinreich PostDoc in  LMCD @ EPFL

Hey Jan... I just saw your message now. I implemented a fairly naive kNN regression (just taking the mean of the k nearest neighbours). It does an ok job compared to fairly basic baselines. See the results in the updated readme.
I'm very open to collaborate---feel free to add whatever you think would be cool :-).

thanks ! looks great. I will do some more careful benchmarking with the kernel ridge regression example too (see pull request). One thing that would be interesting is also to investigate if gzip lowers the offset of the learning curve or if it simply has a larger slope.
typically a lower offset means more information bias is included in the model architecture (eg through transfer learning or better representations). So studying learning curves might gives us a little more insight as well as to understanding who gzip does !


build: Add Konflux pipeline activation through a label

Once PR is created with some branch name, it may be handy to enable Konflux builds on demand.
Inspiration from https://pipelinesascode.com/docs/guide/authoringprs/#using-the-body-and-headers-in-a-pipelines-as-code-parameter and https://github.com/google/cel-spec/blob/master/doc/langdef.md#list-of-standard-definitions.

Figured that body.pull_request.labels look the following way:
    "labels": [
      {
        "color": "ededed",
        "default": false,
        "id":<PHONE_NUMBER>,
        "name": "do-not-merge/work-in-progress",
        "node_id": "LA_kwDODLkO9s74QHBc",
        "url": "https://api.github.com/repos/stackrox/scanner/labels/do-not-merge/work-in-progress"
      },
      {
        "color": "D55C85",
        "default": false,
        "description": "Tells (Konflux) Renovate bot to calm down and not send more updates to this PR.",
        "id":<PHONE_NUMBER>,
        "name": "stop-updating",
        "node_id": "LA_kwDODLkO9s8AAAABoIFzAA",
        "url": "https://api.github.com/repos/stackrox/scanner/labels/stop-updating"
      },
      {
        "color": "B0FE49",
        "default": false,
        "description": "Enable Konflux builds in this PR",
        "id":<PHONE_NUMBER>,
        "name": "konflux-build",
        "node_id": "LA_kwDODLkO9s8AAAABs2KjRA",
        "url": "https://api.github.com/repos/stackrox/scanner/labels/konflux-build"
      }
    ],

Is the pipeline also triggered when you add or remove the label? From what I can see in the history of this PR, you added the label, then pushed https://github.com/stackrox/scanner/pull/1593/commits/53b0dcc45ba26d795cd65af8fe45687988b0883f, for which Konflux started to run.

The pipeline does not start after I just add the label. Something needs to be committed to the PR branch. This works similar to our existing labels in stackrox project.

The pipeline does not start after I just add the label. Something needs to be committed to the PR branch. This works similar to our existing labels in stackrox project.

GHA and OSCI can be triggered just by adding the label, e.g. backport release-4.5 labels work like that.
might be a question for #konflux-users.

Following up here https://redhat-internal.slack.com/archives/C05TS9N0S7L/p1723107909357619

/test scanner-db-slim-build


Roll Flutter Engine from e0900f83a0c8 to 1e562ddcc607 (7 revisions)

https://github.com/flutter/engine/compare/e0900f83a0c8...1e562ddcc607
2024-12-02<EMAIL_ADDRESS>Replace outdated wiki URLs in pull request template (flutter/engine#56824)
2024-12-02<EMAIL_ADDRESS>[impeller] makes UniformBindData 15% faster and adds unit test (flutter/engine#56844)
2024-12-02<EMAIL_ADDRESS>Roll Skia from dd70c8e1c38f to d7751d3d6ff4 (36 revisions) (flutter/engine#56898)
2024-12-02<EMAIL_ADDRESS>Roll Dart SDK from 5785058c9bb1 to 46630dbefbbd (12 revisions) (flutter/engine#56897)
2024-12-02<EMAIL_ADDRESS>switched reactor to absl::flat_hash_map (flutter/engine#56845)
2024-12-02<EMAIL_ADDRESS>Sped up SubpixelGlyph::Equal (flutter/engine#56851)
2024-12-02<EMAIL_ADDRESS>[Impeller] dont cache glyph layout if atlas is invalid. (flutter/engine#56879)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


_forceTransfer is using private variables from the ERC20 contract

The _forceTransfer prevents the contract from compiling because.
DeclarationError: Undeclared identifier.
require(_value <= _balances[_from]);
In order for this to work, the ERC20 contract would have to implement the _forceTransfer method, but it is not part of the standard. Any idea what is the best pattern for implementing this ?

The base ERC20 contract must be overriden in order to implement the _forceTransfer method by either changing the scope of the _balances variable from private to internal, or by moving the internal _forceTransfer method into the ERC20 contract and adding return super._forceTransfer(_from, _to, _value); in the forceTransfer method inside the AtomicDSS contract. The production version implements both of these changes... hope this helps.


Fix spelling

ISSUE TYPE

Docs Pull Request

Hello @jbampton ,
Thanks again for the PR!
Thank you for contributing to BotKube. Could you please fill out this form, so we can send the well deserved awesome swags :slightly_smiling_face:
Team BotKube


[Bug] unexpected lines_offsets when updates event

follow below Examples:
#[test]
fn test_line_offsets() {
    let mut text_document = full_text_document();
    text_document.update(
        &[TextDocumentContentChangeEvent {
            range: Some(Range {
                start: Position {
                    line: 0,
                    character: 0,
                },
                end: Position {
                    line: 0,
                    character: 0,
                },
            }),
            range_length: None,
            text: "0:1332533\n0:1332534\n0:1332535\n0:1332536\n".to_string(),
        }],
        1,
    );
    assert_eq!(text_document.line_offsets[0..4], vec!(0, 10, 20, 30));

    text_document.update(
        &[
            TextDocumentContentChangeEvent { range: Some(Range { start: Position { line: 1, character: 10 }, end: Position { line: 2, character: 10 } }), range_length: None, text: "1:6188912\n1:6188913\n1:6188914\n1:6188915\n1:6188916\n1:6188917\n1:6188918\n1:6188919\n1:6188920\n".to_string() },
        ],
        2
    );
    assert!(text_document
        .get_content(None)
        .to_string()
        .starts_with("0:1332533\n0:1332534\n1:6188912\n1:6188913\n"));
    // Apparently text_document.line_offsets should be [0, 10, 20, 30] ......
    // panic!
    //   left: `[0, 10, 30, 40]`,
    //   right: `[0, 10, 20, 30]`'

    assert_eq!(text_document.line_offsets[0..4], vec!(0, 10, 20, 30));
}

There are some bugs in line_offsets update logic.

Actually,  The  examples haven a invalid Position - Position { line: 1, character: 10 }
In the debug process, we can see the line_1 only include [10] - [19]

In original design, the language server believe all message that sent by client is valid.
So we haven't to solve this situations.

While this seems that this is what VS Code sends, I'm trying to find something in the spec that says using the index after a newline is invalid:
https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#position
That said, the thing that would probably unblock me is updating FullTextDocument::position_at() to use the start of the next line when offset corresponds to \n.
@mroch did you look at this at all when introducing position_at()?

I see that the Rust position_at() implementation mirrors the TypeScript one in VS Code:
https://github.com/microsoft/vscode-languageserver-node/blob/f2ff7d55464a1f58f978cb6635bd8865f050553c/textDocument/src/main.ts#L281-L301
Note that if you have a string of with N characters "abc", there are N+1 possible cursor positions:

before a
between a and b
between b and c
after c

so a 3-character string has 4 possible cursor positions, so I'm not convinced by your screenshot that the specified Position is invalid.

I just ran the following to test out the equivalent TypeScript code:
$ mkdir /tmp/lsptest
$ cd /tmp/lsptest
$ yarn
$ yarn add vscode-languageserver-node
$ node

Then in the Node shell:
> var vs = require('vscode-languageserver')
> var doc = vs.TextDocument.create('', 'text', 1, "0:1332533\n0:1332534\n0:1332535\n0:1332536\n")
> event = {range: {start: {line: 1, character: 10}, end: {line: 2, character: 10}}, text: "1:6188912\n1:6188913\n1:6188914\n1:6188915\n1:6188916\n1:6188917\n1:6188918\n1:6188919\n1:6188920\n"}
> doc.update(event, 2)
> doc
FullTextDocument {
  _uri: '',
  _languageId: 'text',
  _version: 2,
  _content: '1:6188912\n' +
    '1:6188913\n' +
    '1:6188914\n' +
    '1:6188915\n' +
    '1:6188916\n' +
    '1:6188917\n' +
    '1:6188918\n' +
    '1:6188919\n' +
    '1:6188920\n',
  _lineOffsets: undefined
}
> doc.getLineOffsets()
[
   0, 10, 20, 30, 40,
  50, 60, 70, 80, 90
]

Hmm, though as @mroch pointed out to me via chat, this seems even stranger, since it looks like the entire document contents have been replaced even though event should be treated as an incremental update?

Weird, when I look at what is actually in my node_modules folder, I find this implementation for update():
    FullTextDocument.prototype.update = function (event, version) {
        this._content = event.text;
        this._version = version;
        this._lineOffsets = undefined;
    };

Looking at applyEdits() instead now...

OK, I have a better repro. Run this script via node in a folder where you have run yarn add vscode-languageserver-node:
var vs = require("vscode-languageserver");
var doc = vs.TextDocument.create(
  "",
  "text",
  1,
  "0:1332533\n0:1332534\n0:1332535\n0:1332536\n"
);
var event = {
  range: { start: { line: 1, character: 10 }, end: { line: 2, character: 10 } },
  text: "1:6188912\n1:6188913\n1:6188914\n1:6188915\n1:6188916\n1:6188917\n1:6188918\n1:6188919\n1:6188920\n",
};

// This does not work?
// doc.update([event], 2);

var textEdit = {
  range: event.range,
  newText: event.text,
};

var result = vs.TextDocument.applyEdits(doc, [textEdit]);
console.log(result);

I get:
0:1332533
0:1332534
1:6188912
1:6188913
1:6188914
1:6188915
1:6188916
1:6188917
1:6188918
1:6188919
1:6188920
0:1332536

Note also these docstrings:
https://github.com/microsoft/vscode-languageserver-node/blob/f2ff7d55464a1f58f978cb6635bd8865f050553c/textDocument/src/main.ts#L146-L174

@bolinfest TextDocument from vscode-languageserver is deprecated, try using vscode-languageserver-textdocument
var vs = require("vscode-languageserver-textdocument");
var doc = vs.TextDocument.create(
  "",
  "text",
  1,
  "0:1332533\n0:1332534\n0:1332535\n0:1332536\n"
);
var event = {
  range: { start: { line: 1, character: 10 }, end: { line: 2, character: 10 } },
  text: "1:6188912\n1:6188913\n1:6188914\n1:6188915\n1:6188916\n1:6188917\n1:6188918\n1:6188919\n1:6188920\n",
};

// now this works
vs.TextDocument.update(doc, [event], 2);

console.log(doc);

FullTextDocument {
  _uri: '',
  _languageId: 'text',
  _version: 2,
  _content: '0:1332533\n' +
    '0:1332534\n' +
    '1:6188912\n' +
    '1:6188913\n' +
    '1:6188914\n' +
    '1:6188915\n' +
    '1:6188916\n' +
    '1:6188917\n' +
    '1:6188918\n' +
    '1:6188919\n' +
    '1:6188920\n' +
    '0:1332536\n',
  _lineOffsets: [
      0,  10,  30, 40,  50,
     60,  70,  80, 90, 100,
    110, 110, 120
  ]
}

lineOffsets: [0,  10,  30, ...] ??
so, i think this is also broken upstream

Fixed by #31


Include missing event type name fix (#287) for patch release

Summary
This PR fixes the issue of webhook payloads that do not include a issue_event_type_name for a jira:issue_updated event.
0/5 on keeping this release small and including just this commit here. I'd like to get this out quick as it's causing Jira servers with older versions to not work with the plugin (legacy webhooks and channel subscriptions).
Here's all of the new commits on master since 2.1 release: https://github.com/mattermost/mattermost-plugin-jira/compare/fdba0d10e3da8e1171d26d2f7dbc1021e41b31f2...master in case the team thinks we should include another fix in the patch.
Ticket Link
https://mattermost.atlassian.net/browse/MM-17682
https://mattermost.atlassian.net/browse/MM-17750
https://github.com/mattermost/mattermost-plugin-jira/issues/277
https://github.com/mattermost/mattermost-plugin-jira/issues/272

@levb I did a manual cherry-pick and had a conflict with manifest (not sure how since I based off of v2.1.0). Do we have automation on cherry-picking for this repo?

this would be for the next (5.14.3?) dot-release if/when we make one

@levb We're not currently working on a dot release, so will need to understand if we want a dot release for this specific issue.

How urgent is this issue? Does this affect all Jira plugin users?
Have customers or community reported this?

@amyblais This issue is affecting customers that are using older versions of Jira Server (seen happening on 7.1.8). It's not a regression, but it is making the plugin webhook events not work in general for a small number of users.
There has been one customer report of the issue, and another that I am unsure if is from a customer or community. If there is not a dot release on the way, could we release the patch without prepackaging into the application?

@amyblais At this point it should probably go into 5.15 only. However, since the plugin release is "de-coupled" once we have it published, and the 5.15 Makefile updated, I recommend that we CP it into the 5.14 branch, just in case there is indeed another 5.14.x release, for other reasons.


xActiveDirectory: Documentation how to run manual integration tests

As part of the PR #170 integration tests are introduced. THose integration tests cannot be run in AppVeyor as the unit test are, because of the limitation on the AppVeyor build worker.
We should provide a simple guide to how to run the integration tests so they build a lab (when prerequisites are meet).
I suggest we start with Hyper-V and assume there are clean VM's that can be used. Mostly because I have that environment available, and it's part of Windows 10. 🙂
We could add other environments to manual integration tests, like Test-Kitchen, LabBuilder, Lability, etc., and clouds like Azure, AWS, GCP.

I was thinking about the same in the last week. I wanted to do something based on Docker and DSC/ Hyper-V with DSC.
I lean more toward Docker - but that's just me.

Can we run a domain controller in docker? I thought we couldn’t do that yet. If we can then I agree docker is the way to go.

That is something i want to try. For testing should be ok- with persistent storage i guess it would work. I’ll report how is my testing going.

If it works, then we could actually run tests in AppVeyor since we can run docker containers there. And the test framework supports running tests in a container.


updated README.md

Summary
updated readme.md
Issue(s) Addressed
closes #263

All left aligned please. And make sure every emojis are bouncing and animated if possible like the open source wala muscle And instead of :- make it :
There are other content changes, i'll let you know after some time may be tomorrow @Meetjain1

sure

All left aligned please. And make sure every emojis are bouncing and animated if possible like the open source wala muscle And instead of :- make it :
There are other content changes, i'll let you know after some time may be tomorrow @Meetjain1

done with these  changes ,let me know about the other changes @krishnaacharyaa

Can we add contributing guidelines even here?

And discord link is invalid

@krishnaacharyaa have a look now , I think I have completed all the changes you want .

Can we add contributing guidelines even here?

I dont think that we can do this by editing readme.md file

Why is there some space in the right side not used in the contributions section? can we make it a little small, only a little @Meetjain1

okk done

Looks very nice, GSSoC label , i am thinking can we make it little revealing? may be adding it in the important links? what do you feel and how about having 🔗 than gem in the links emoji section @Meetjain1

adding that jam of link , but gssoc label important links mai hmm.. ok link kaunsi du gssoc mai ? gssoc 24 ki ?

Looks very nice, GSSoC label , i am thinking can we make it little revealing? may be adding it in the important links? what do you feel and how about having 🔗 than gem in the links emoji section @Meetjain1

adding that jam of link , but gssoc label important links mai hmm.. ok link kaunsi du gssoc mai ? gssoc 24 ki ?

No we'll have to figure out, the gssoc has deployed our project in their some website, that link we'll have to put or else if you feel link mei doesn't look good.
Convert the existing description like table of 2 columns ,
GSSOC logo | description
logo should span across 2 rows got it? @Meetjain1

@krishnaacharyaa have a look now , I think no changes required now 🙃

@Meetjain1 , the link wala why did you change? I am not able to click anything?
The previous one the content was all good, the blue underline and proper links and stuff,
I wanted you to just change the heading from 💎 to 🔗. Rest all looks really good.
Once this is done. kindly raise fresh PR which follows contributing guidelines, so that i can close this as soon as possible. so that you get your points.

@Meetjain1 , the link wala why did you change? I am not able to click anything?
The previous one the content was all good, the blue underline and proper links and stuff,
I wanted you to just change the heading from 💎 to 🔗. Rest all looks really good. Once this is done. kindly raise fresh PR which follows contributing guidelines, so that i can close this as soon as possible. so that you get your points.

arae mujhe laga aap ye change krne ko bole thae

The previous one was good bro! Blue underline just heading Kindly change
Once you raise new PR which follows the contributing guidelines I'll merge this
Even I'm eager to get this changes in 😍😊
No more changes hopefully @Meetjain1

The previous one was good bro! Blue underline just heading Kindly change
Once you raise new PR which follows the contributing guidelines I'll merge this
Even I'm eager to get this changes in 😍😊
No more changes hopefully @Meetjain1

Haash ok 👍

@krishnaacharyaa pr title checker ka issue aaraha hai kya hai ye ?

@Meetjain1 slow down your horses, 5th time I'm saying take your time and raise new PR reading the 5 points in contributing guidelines.
Once your PR follows the commits and PR title according to guidelines will merge this.

@Meetjain1 pardon me, missed the new PR!. Closing this


Upgrade?

Hello, this looks great.  Sorry if this is not the place to ask, but I am new to development.
If I already have some of these tools installed, will these scripts just reconfigure them?
I'm worried I may have misconfigured some Homebrew and NPM installs, and some directories may be out of place due to problems with my $PATH / bash profile.
Cheers

No problem, issues are a great place to ask questions! 😄
Yes, the script will override your preferences and settings since it is intended for fresh installs on new computers.
If you want to use the settings within the repo, I would clone it and then edit it your heart's desire so it fits your $PATH and doesn't reconfigure it a different way than intended.
Hope this helps and apologies for late reply!


HTTP 502 response half of the time

Some of the requests work, some dont. I'm using nomad. I have tagged my service with
	tags = ["urlprefix-/foo", "test-app"]	 . Consul shows that everything is healthy. Sorry bit less information. I'm just looking into Nomad and trying out this loadbalancer and not experienced. Maybe someone can help me. Thanks

fabio is logging:
invalid log msg: 2018/12/08 20:49:57 http: proxy error: dial tcp <IP_ADDRESS>:29526: connect: connection refused
invalid log msg: 2018/12/08 20:49:58 http: proxy error: dial tcp <IP_ADDRESS>:21078: connect: connection refused
invalid log msg: 2018/12/08 20:49:58 http: proxy error: dial tcp <IP_ADDRESS>:21078: connect: connection refused
invalid log msg: 2018/12/08 20:49:58 http: proxy error: dial tcp <IP_ADDRESS>:21078: connect: connection refused

however I'm checking consul and they are healthy.

What do the health checks do? Can you share the Nomad job specification?
What is registry.consul.checksRequired set to?

I figured it out. Consul was pointing to <IP_ADDRESS> its local and I have 3 node cluster on vagrant so it tried to access some random ports on local that arent existant. I had to put address_mode = "driver" to the nomad service and it got the right interface addresses. Thanks for trying to help btw @pschultz


Mapveu/sidebar new

sidebar resize works

changed blue background color to none for sidebar pane's title & text color to be gray (fig.)
added an icon to display resizable (same icon to popbio map/mapveu v1) (fig.)
organizing files to be much simpler: two story files, single core file, and tab contents files
converted customized core lib (SidebarReactCore.tsx) to function component
applied prettier
moved story files to /stories and adjusted paths

Loving the look and feel DK.  The blue bar was a problem and now isn't!
One thing I want to help you sort out is the merge with master, because the fixture files have been removed. Could you have a go at updating SidebarResizeLib.stories.tsx to use
import {
  getSpeciesDonuts,
} from './api/getMarkersFromFixtureData';

(use DonutMarkers.stories.tsx AllInOneRequest as a guide)
and I'll help if you run into any problems?

Loving the look and feel DK. The blue bar was a problem and now isn't!
One thing I want to help you sort out is the merge with master, because the fixture files have been removed. Could you have a go at updating SidebarResizeLib.stories.tsx to use
import {
  getSpeciesDonuts,
} from './api/getMarkersFromFixtureData';

(use DonutMarkers.stories.tsx AllInOneRequest as a guide)
and I'll help if you run into any problems?

@bobular I have applied the new approach to the sidebar story

Thanks DK - that's great - all set to merge.
The Sidebar Tab container components will likely change when we develop the actual application ;-)

Thanks DK - that's great - all set to merge.
The Sidebar Tab container components will likely change when we develop the actual application ;-)

@bobular yes I agree with your thought 👍 We will see :)


Fix deploy with corepack

Add corepack enable and package install before fly deploy in deploy job.

Closes #146


slickSetOption not working with arrows

slickSetOption not working with arrows

I have used slick with the option 'arrows:false' on the DOM ready.
$('.slider-info').slick({
arrows:false
});

I want to show/enable arrows on the click of the button.
I have used the below option on the click event

$('.slider-info').slick('slickSetOption', 'arrows', true);
$('.slider-info').slick( 'refresh' );
It is not working/enabling arrows by the above code.
It works fine with slickSetOption
$('.slider-info').slick('slickSetOption', 'slidesToShow', 3);
$('.slider-info').slick( 'refresh' );
Is there anything i am missing out?

just hide the buttons with display:none and show them when you click on your button?


fix the get_template_info method in overload_method template

fix #9162

maybe also need to fix the same issue for overload_attribute and bound_function. not sure about these.

_OverloadAttributeTemplate._resolve() method directly returns sig.return_type. I feel this is different with types.BoundFunction(MethodTemplate, typ) in _OverloadMethodTemplate._resolve() method. Hard to apply the same fix, so ignore overload_attribute for now.

The new test case is copy-and-modify from #8396

Ready for review now! @sklam

Hi, @gmarkall . I think this's ready for review, and I already added a test for this.

If https://github.com/numba/numba/pull/8396 is included in 0.59rc, then this PR should also be included. That PR needs this one, I think.

I pushed a commit to resolve merge conflict


Workloads pods not visible

Thanks for this extension (and thank you for the presentation at KubeCon 2019)
I succeed to run the extension but I can't see my workloads this is what I see :

cluster name

namespaces

namespace1
namespace2

nodes : OK
workloads

Pods : nothing :(

Is it normal that i don't see my pods ?
My environment :

kubectl
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean",
BuildDate:"2019-03-25T15:53:57Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.3", GitCommit:"435f92c719f279a3a67808c80521ea17d5715c66", GitTreeState:"clean",
BuildDate:"2018-11-26T12:46:57Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
vscode : 1.34.0
kubernetes extension version : 1.0.0
kubernetes : rancher 2.1.3

By default the extension uses the default namespace. You may need to right-click on a namespace and activate that namespace as the selected namespace. If that still doesn't work, please let us know.

Hi @TristanFAURE - were you able to resolve your issue by right clicking the namespace you'd like to view pods in?

Hello
Thank you for your answers !
I have no possibility to test before 11th June. But as soon as I have the connection back I'll let you know

You were right it is working ! You can close the ticket

Thanks!


iOS 16 issues?

This is an email that I got:

I got some users reporting  app was not working to find the ESP devices anymore. Investigating I realized they updated iPhones iOS version from 15 to iOS 16 and this is the issue. For some reason your lib is not working anymore on iOS 16.

I couldn't verify it yet, but in case someone is able to provide more info, this ticket would be the right place.

Please also check #37 and the README part "Breaking change in iOS 14.6".
Some user see the breaking change with iOS 16 but the entitlements are required since 14.6.


Bluetooth: samples: Add ISO connected benchmark sample

Add a sample that measures packet loss in a connected
ISO setup.
Signed-off-by: Emil Gydesen<EMAIL_ADDRESS>

Hi there! I'm wondering how this PR has passed CI when build of the sample fails in other PRs, e.g. https://buildkite.com/zephyr/zephyr/builds/34583.
Reason of failure is this option CONFIG_BT_ISO=y from prj.conf. The config entry is defined as hidded in subsys\bluetooth\KConfig.

this was reverted, please submit a new PR with a working sample.


Capture the installed packages for updates only when required

Description of the new feature/enhancement
In a nutshell a similar mechanism to cup all -y from Chocolatey.
At this stage if I define a baseline config with a list of packages and rerun the script, it forces a reinstall of everything.
As a user when I use winget install mypackage the system should not download the whole package is already installed (unless I force).
As a user when I use winget install mypackage the system should propose a new version upgrade if available (unless I specify a version).
Proposed technical implementation details (optional)
Capture the currently installed package, e.g. manifest copy, to compare to the install request for comparison of the locally stored version if existing.

Hey @ManuInNZ, thanks for reporting this request. It seems to overlap a lot with already existing issues though:

#119
#153
#216
#291

So consider closing this issue and adding your feedback to one of the other issues instead :-)


Enhance and polish vulnerabilities welcome page

We should make it as fancy, as SAVE welcome page

@sanyavertolet implemented it


incorrect link Installing Kubernetes with kOps

This is a Bug Report
Page Link : https://kubernetes.io/docs/setup/production-environment/tools/kops/
Incorrect Link in Whats Next
At Point
Follow kOps community discussions on Slack: community discussions.
What would you like to be added
Change Link :https://github.com/kubernetes/kops#other-ways-to-communicate-with-the-contributors to https://kubernetes.slack.com/archives/C3QUFP0QM
Why is this needed
This change will help readers to find relevant Slack Channel

/kind bug
/language en

/sig docs

I would like to work on this issue
/assign

/assign

Raised PR in  #42295

Hi @nikhilchauhangithub, Please try to look for the Assignees list before assigning any issue to yourself.

/close
As the issue is solved.


commit assets into the repository

Trying to load assets via NPM apparently didn't work very well. This switches back to commiting them to the repository.

@benpatterson, can you review this as well? I just copied all the assets into the repository -- I can trim it down, if you'd like.

For some reason I thought we had bootstrap in this repo originally?
I'm ok committing all this, though. 👍


Gizmo elements are affected by Environment and Camera effects, and they affect scene lighting

Tested versions
4.3 Stable
Any 3.x and 4.x
System information
Windows 10 22H2
Issue description
Gizmo elements are being affected by World Environment and Camera effects, such as DOF, SSR, SDFGI, and more. They are also affected by overall sky lighting in the scene. It seems, they are being rendered as some sort of emissive materials.
Which makes very inconsistent UI experience within Godot editor. Instead, all scene UI and controllers (grid, gizmo) should not be affected by any rendering settings or effects.

(Gizmo just lit up the whole interior on the right)

(Gizmo elements are being blurred out by DOF)
Steps to reproduce
Use any Godot 3/4 version and add World Environment or Camera Attributes to define DOF, SSR, SDF, etc. These features will change the look of Gizmo and Grid. But also Gizmo and Grid will affect the scene elements (they are emissive, and they are being reflected).
Minimal reproduction project (MRP)
Not required

For comparison, such elements are not being affected by lighting or DOF in any other major engine, they are just there as separate entities. Obviously, they are not impacting light and not being reflected:

Thank you for reporting, this is a missing feature, see:

https://github.com/godotengine/godot-proposals/issues/2138

Consolidating there


Partial masking

Given I have this body
{
  "cardNumber": "1111-2222-3333-4444"
}

I want to turn it into this
{
  "cardNumber": "****-****-****-4444"
}

I.e. I don't want to mask it completely, but I do want to mask it somehow to hide the sensitive data.
I suggest that BodyFilters and QueryFilters have this method:

 public static *Filter replaceStringProperty(
    final BiFunction<String, String, String> replacement
) {
    return ...;
}

So that I can do this:
*Filters.replaceStringProperty(
    (name, value) -> {
        if (shouldMaskPartiallyPredicate.test(name)){
            return maskPartially(value);
        }
        if (shouldMaskFullyPredicate.test(name)){
            return "***";
        }
        return value;
    };
);

Sounds like a useful extension. We have something like that for headers already, if I remember correctly. API looks also good. Do you care to implement it?

I probably will but not sure when

Switched jobs, now I most likely won't do this one

Hey @whiskeysierra , this is something I can work on. I need this function especially in Json Body filter to replace body value to hash of that value rather than a generic replacement parameter. Adding a function here to do the replacement would be a helpful extension IMO. Will send out a pull request soon.

Follow up issue is #851


Major crash issue @kpwn

After my phone is sitting for a while i go to cydia and the phone crashes and reboots. I have to hardreset the phone for yalu to work again @kpwn

this is a issue that will be fixed in next commit.

@kpwn is it fixed?

it is


Move emailotp to plugins

Fixes https://github.com/wso2/product-is/issues/11176
Depends on the release of v4.0.0 of emailOTP

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/572826544

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/572826544
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/572841259

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/572841259
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/572841259

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/572841259
Status: success


This fix tooltip text align

What do you think about fix behavior of ctx.fillText for align: 'center' or align: 'right' ? It's not working as expected.
I tried to solve this problem: change x coordinate depending on the alignment at Title, Body and Footer.
This solves #1977

Coverage decreased (-0.2%) to 71.645% when pulling 6728d33dbf96ffce39327a04f5cb5399849a12cd on sashamjolnir:patch-1 into b50c281684f40b55f6168503a73f6e09ca02d17f on nnnick:v2.0-dev.

Hmm, I'm not sure about this. I agree that it eliminates the issue, but it also makes the alignment options useless.
The alignment options, if i remember correctly, were intended to allow customization of how the tooltip behaved around points. There were (they still might exist) some internal alignment strings and these options were supposed to set those.

According to documentation, tooltip text alignment options (*Align, *-title,body,footer) are only for text inside tooltip. I think this pull request doesn't changes tooltip position or tooltip behavior.
May be we should try to create new options to text alignment inside tooltip, because sometimes sometimes it's necessary and with this option we cannot achieve it (issue pics)

You're correct that this is meant for the text. The issue I have is that by simply fitting the text no matter the alignment, the alignment options don't do anything because the text will always draw in the same place. My thought was that the text would be shifted by the alignment change, but that the tooltip would follow the text.
I think you are right that we need different options though.

Em, by the way, I didn't found some alignment options, that rules position of tooltip (top, bottom, left or right) relative to point (at line chart). You mean this title, body, footer Alignment option used to use for that?

I had meant this stuff: https://github.com/nnnick/Chart.js/blob/master/src/core/core.tooltip.js#L339-L396

Was this issue resolved in #2416?

@zachpanz88 no.
What I want is to align text inside tooltip. Because tooltip option bodyAlign: 'center', or titleAlign: 'center', is working not as I expect. See MDN Canvas
Examples
titleAlign: left;
bodyAlign: left
![left left]
(https://cloud.githubusercontent.com/assets/8746547/15122102/266790a4-1626-11e6-8b2e-502050cbd6c7.png)
titleAlign: left;
bodyAlign: center
![left center]
(https://cloud.githubusercontent.com/assets/8746547/15122106/29e9b630-1626-11e6-89d8-b5ea1232526e.png)
titleAlign: center;
bodyAlign: left
![center left]
(https://cloud.githubusercontent.com/assets/8746547/15122110/2d31690a-1626-11e6-84f4-9850c99d7a72.png)
titleAlign: center;
bodyAlign: center
![center center]
(https://cloud.githubusercontent.com/assets/8746547/15122128/49decff2-1626-11e6-9828-504a066e19e8.png)
Thank you for responses and this great library.

Closing because out of date

so this bug #1977 is still unresolved.

We could be open to accepting a PR if it was based off of the current code in the master branch


Can't create multiple port forwarding rules at once

ISSUE TYPE

Bug Report

COMPONENT NAME
UI

CLOUDSTACK VERSION
4.16.0

CONFIGURATION
XCP-NG 8.2
Advanced Zone
OS / ENVIRONMENT
Oracle Linux 8.4 - Management server, MYSQL 8.0.26
XCP-NG 8.2 - hypervisor
SUMMARY
Can't add multiple port forwarding rules at once for 1 VM
STEPS TO REPRODUCE
Add first port forwarding rule and add it to VM
Try to add second rule to this VM

EXPECTED RESULTS
User can add both rules

ACTUAL RESULTS
After U add first rule U can't add second. Only switching between VM's allow U add second rule on VM which U want.

@edikevich
do you use vpc or isolated network ?
can you share some error logs ?

Hi.
Have same problem with VPC and Isolated networks. After I add first rule I can't push "OK" button when create second rule.
I don't have any errors in management server logs.

@edikevich
I see, thanks. It seems to be a UI bug.
If you refresh the page, you should be able to add port forwarding rule.

Thx. Yes I found how to avoid it but when U create  more than 5 rules is realy annoyed:(

Fixed in https://github.com/apache/cloudstack/pull/5690


[ui-cve] Upgrade mime in the ace editor source for CVE-2017-16138

What changes were proposed in this pull request?
This PR is to fix the CVE on gitHub by dependabot (https://github.com/cloudera/hue/security/dependabot/26)
This involves upgrading mime (used as a dependency by ace-editor) version from 1.2.x to 1.4.1
How was this patch tested?
Changed version of mime from 1.2.x to 1.4.1 and no changes in the files were seen.
Please review Hue Contributing Guide before opening a pull request.

And did you manually test Editor after the upgrade and build? Do we know/how when this mime packe is used by the Editor?

And did you manually test Editor after the upgrade and build? Do we know/how when this mime packe is used by the Editor?

There were no code changes after the build so no change to the actual code that the Hue editor uses.

@bjornalm
The editor (Hue UI) was working fine after this change too.
I think you wanna ask about below only:
ace-editor has a dependency on mime (present in just one place here in package.json)

mime is used in ace-editor (internally) in a file called static.js. The file static.js is responsible for creating a backend server. That file or the backend server created for ace-editor has nothing to do with Hue.
So, we don't use mime directly at all in the Hue editor.So, we are all good here.


Component: Radio Button | Negative

Figma:
https://www.figma.com/file/xZ0IW0MJO0vnFicmrHiKaY/Components-Post?type=design&node-id=7777%3A33876&mode=design&t=xVjboB9gCTmSBwof-1
Story Book
https://next.design-system.post.ch/?path=/docs/components-forms-radio-button--docs
Comments:

Ad new Type: Negative

Negative Variants have been added.

Closing as won't implement


wont create a certificate if client name has a "space"

in linux doing something like "cd Hey You" wont work it wil tell u no such file or directory ,same with files
if you want it to work youl have to use "cd Hey\ You"
same when a client enters a name that has a space in it lets say "Yaseen Eltii"
it will say Finished but you wont find a .cert file you should add a note there :))

It's already there:
echo "Tell me a name for the client cert"
echo "Please, use one word only, no special characters"
read -p "Client name: " -e -i client CLIENT

A proper approach would be to introduce input validation and error checking everywhere, not just with the client name. But that would take many hours of work and testing, so it will not happen for now.


Header changes from Remove method dispatch from md

These are the header changes from https://github.com/ARMmbed/mbed-crypto/pull/185
When https://github.com/ARMmbed/mbed-crypto/pull/185 is merged, update the submodule-updating commit in this PR to point to the new development in crypto, then merge this PR.

This PR isn't needed now that we don't duplicate crypto header files between Mbed TLS and Mbed Crypto.


ng serve - not working

Hi Guys,
I have the latest angular-cli + lastest npm. I try runing "ng serve" and get the following error:
Anyone else having similar issue?
Cannot read property 'config' of null TypeError: Cannot read property 'config' of null     at Class.run (/Users/rodrigo/Downloads/angular-oauth2-oidc-master/node_modules/@angular/cli/tasks/serve.js:51:63)     at check_port_1.checkPort.then.port (/Users/rodrigo/Downloads/angular-oauth2-oidc-master/node_modules/@angular/cli/commands/serve.js:121:26)     at <anonymous>     at process._tickCallback (internal/process/next_tick.js:188:7)
Cheers

My bad! i hadn't noticed the "sample" folder.....


FIX Altering ID of authenticator tabs to resolve ID conflict

Currently when using multiple authenticators it uses a template called Security_MultiAuthenticatorTabbedForms.ss: https://github.com/silverstripe/silverstripe-framework/blob/4.2/templates/SilverStripe/Security/Security_MultiAuthenticatorTabbedForms.ss
The problem is the tab IDs are set to the form name, but the default rendering of the LoginForms also uses the form name as the ID of the form. This results in duplicate IDs (which makes an invalid DOM).
This PR alters the ID (and prior reference) of the tabs so they are suffixed with _Tab.

well... is this a breaking change? what's the impact on existing themes / users of this change?

Considering there was always and ID conflict I can't imagine anyone was actually using this ID to provide styling or tie in JS. Additionally, the multi-authenticator default styling is not very... feature complete... I highly doubt anyone would be affected by this change.

ok - deferring to @robbieaverill

I'm happy with the change, but I'll leave it for another core team member to agree with me before merging it =)


FROM/layer-extraction on ltsc2019 fails: link operation for Windows/INF/basicrender.inf on cross-platform building from Linux

Describe the bug
COPY commands have been working normally for years with our lts2019 windows container build on Agones, but started failing today with an error message of:
Dockerfile.windows:18
--------------------
  16 |     FROM mcr.microsoft.com/windows/servercore:${WINDOWS_VERSION}
  17 |
  18 | >>> COPY ./bin/sdk-server.windows.amd64.exe /agones/sdk-server.exe
  19 |     COPY ./bin/LICENSES ./bin/dependencies-src.tgz /agones/
  20 |
--------------------
ERROR: failed to solve: failed to compute cache key: mount callback failed on /tmp/containerd-mount3356703247: link /tmp/containerd-mount3356703247/Windows/INF/basicrender.inf /tmp/containerd-mount3356703247/Windows/System32/DriverStore/FileRepository/basicrender.inf_amd64_efdc64af60c69a6d/basicrender.inf: no such file or directory
make: *** [Makefile:619: build-agones-sdk-image-windows-ltsc2019] Error 1

Where ${WINDOWS_VERSION} is ltsc2019
To Reproduce
To reproduce this, just try copying something in:
ARG WINDOWS_VERSION=ltsc2019
FROM mcr.microsoft.com/windows/servercore:${WINDOWS_VERSION}

COPY ./emptyfile /emptyfile

(Assuming you have a buildx builder already)
❯ touch emptyfile
❯ docker buildx build --platform windows/amd64 --builder windows-builder-ltsc2019 --tag=windows-test .
[+] Building 18.6s (6/6) FINISHED                                                                                docker-container:windows-builder-ltsc2019
 => [internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 156B                                                                                0.0s
 => [internal] load metadata for mcr.microsoft.com/windows/servercore:ltsc2019                                                                                0.1s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 28B                                                                                0.0s
 => [1/2] FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:3c97a5c1c32ddb346c190f00a588da6e682a9a8160869f4969edfd7c6e4d1c03                                                                                18.3s
 => => resolve mcr.microsoft.com/windows/servercore:ltsc2019@sha256:3c97a5c1c32ddb346c190f00a588da6e682a9a8160869f4969edfd7c6e4d1c03                                                                                0.0s
 => => extracting sha256:0dd0445527a5079720e935502b31de927b8e22e5ca358026cf0bc8845c5ba5ce                                                                                18.3s
 => ERROR [2/2] COPY ./emptyfile /emptyfile                                                                                0.0s
------
 > [2/2] COPY ./emptyfile /emptyfile:
------
WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
Dockerfile:4
--------------------
   2 |     FROM mcr.microsoft.com/windows/servercore:${WINDOWS_VERSION}
   3 |
   4 | >>> COPY ./emptyfile /emptyfile
   5 |
--------------------
ERROR: failed to solve: failed to compute cache key: mount callback failed on /tmp/containerd-mount1556330329: link /tmp/containerd-mount1556330329/Windows/INF/basicrender.inf /tmp/containerd-mount1556330329/Windows/System32/DriverStore/FileRepository/basicrender.inf_amd64_efdc64af60c69a6d/basicrender.inf: no such file or directory

Expected behavior
The image should build 😃
Configuration:

Edition: ltsc2019
Base Image being used: mcr.microsoft.com/windows/servercore
Container engine: docker, Running on Linux (debian).
Container Engine version both 24.x and 26.x

Additional context
You can see a full build output from the Agones build pipeline here: https://console.cloud.google.com/cloud-build/builds/70b984e2-132b-4d1a-915a-862cb03f4830;step=16?e=13803378&project=agones-images
Using the previous SHA of @sha256:6fdf140282a2f809dae9b13fe441635867f0a27c33a438771673b8da8f3348a4 worked.

Also possibly worth noting ltsc2022, works still. We tested it!

which image is Using the previous SHA of @sha256:6fdf140282a2f809dae9b13fe441635867f0a27c33a438771673b8da8f3348a4 worked. in reference too?

which image is Using the previous SHA of @sha256:6fdf140282a2f809dae9b13fe441635867f0a27c33a438771673b8da8f3348a4 worked. in reference too?

mcr.microsoft.com/windows/servercore:ltsc2019

For reference, we have this PR now in place to unblock CI: https://github.com/googleforgames/agones/pull/3829

Tried it myself on a build node I have been using for years, though I have updated docker buildx since:
docker buildx version
github.com/docker/buildx v0.12.1 30feaa1a915b869ebc2eea6328624b49facd4bfb

I did use this version before KubeCon, and I did use mcr.microsoft.com/windows/servercore:ltsc2019 as a base image for the presentation where I talked about building Windows images. So, I think the image is the issue (Microsoft publishes a new image monthly).

This looks to be an issue with the image patches released Yesterday (May 14th). Work around is use April's patch images as done in https://github.com/microsoft/Windows-Containers/issues/493#issuecomment-2112937642

Adding link to the slack discussion where we narrowed it down to the patch release https://kubernetes.slack.com/archives/C0SJ4AFB7/p1715733067064539

/cc @profnandaa

UPDATE: we've been investigating this issue, a few things worth noting:

The issue not actually with COPY but it is happening at the tail-end of FROM and so the reporting just estimates to the next line on the Dockerfile.
The issue is to do with extraction of the latest delta layer on ltsc2019:=> extracting sha256:0dd0445527a5079720e935502b31de927b8e22e5ca358026cf0bc8845c5ba5ce

There's only one "offending" file Windows/INF/basicrender.inf (and its hardlinks); it so happens that on the TAR header (metadata), it's referenced as lowercase basicrender.inf, when the actual file in the layer is BasicRender.inf. Since Windows is not case-sensitive when it comes to files, this issue is only evident when the link operation is done on Linux (which is case-sensitive). Therefore, it reports as file-not-found. RCA is still going on to fix the issue.

PS. will be nice to re-tittle the issue to FROM/layer-extraction on ltsc2019 fails: "mount callback failed"

Hello, is there any plan / timeline to fix Windows images to be usable on Linux? We as Kubernetes community cannot release our images based on the mcr.microsoft.com/windows/servercore:ltsc2019@latest tag. It's not super critical, at least now, but you never know when a CVE comes and we will need to release images immediately.

@jsafrane -- a fix is currently going through validation; will update here once we release.

hi, @profnandaa, can I gently ask you about a rough ETA for a fix?

Sure, this is now fixed:
#5 [1/3] FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647
#5 resolve mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647 0.0s done
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 15.73MB / 573.97MB 0.2s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 54.53MB / 573.97MB 0.5s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 93.32MB / 573.97MB 0.8s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 131.07MB / 573.97MB 1.1s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 168.82MB / 573.97MB 1.4s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 206.57MB / 573.97MB 1.7s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 244.32MB / 573.97MB 2.0s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 284.16MB / 573.97MB 2.3s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 322.96MB / 573.97MB 2.6s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 362.81MB / 573.97MB 2.9s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 401.60MB / 573.97MB 3.2s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 442.50MB / 573.97MB 3.5s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 480.25MB / 573.97MB 3.8s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 519.05MB / 573.97MB 4.1s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 559.94MB / 573.97MB 4.4s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 573.97MB / 573.97MB 5.2s done
#5 extracting sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e
#5 extracting sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 62.4s done
#5 DONE 67.6s

Guards have been put in place to prevent similar issues from happening in future.
Anyone else can ACK and we can proceed to close the issue.

I might be doing something wrong, but 41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647 does not work for me.
Dockerfile.reproduce:
FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647
RUN echo hello world > file

Build output:
docker build -f Dockerfile.reproduce  --platform=windows/amd64 .
[+] Building 458.1s (4/5)                                                                                docker:default
 => [internal] load build definition from Dockerfile.reproduce                                                                                0.0s
 => => transferring dockerfile: 202B                                                                                0.0s
 => [internal] load metadata for mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => ERROR [1/2] FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647                                                                                457.9s
 => => resolve mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647                                                                                0.0s
 => => sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647 375B / 375B                                                                                0.0s
 => => sha256:f44fdada7eb2e71f80c964b2759421f4f7645a2df97a12aa82f66a8d50410414 596B / 596B                                                                                0.0s
 => => sha256:b51a50ce03f12744163cde05017bec7149d704963fe41aed4b4a78472a98a3f8 788B / 788B                                                                                0.0s
 => => sha256:cb524f6f22159378ea820d234d80ca09b79c2f0cc91315eeef11904e3ff36a21 1.60GB / 1.60GB                                                                                410.6s
 => => sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 573.97MB / 573.97MB                                                                                219.4s
 => => extracting sha256:cb524f6f22159378ea820d234d80ca09b79c2f0cc91315eeef11904e3ff36a21                                                                                38.1s
 => => extracting sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e                                                                                8.5s
------
 > [1/2] FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647:
------
WARNING: current commit information was not captured by the build: git was not found in the system: exec: "git": executable file not found in $PATH
Dockerfile.reproduce:1
--------------------
   1 | >>> FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647
   2 |
   3 |
--------------------
ERROR: failed to solve: failed to register layer: link /Files/Program Files/common files/Microsoft Shared/Ink/en-US/micaut.dll.mui /Files/Program Files (x86)/common files/Microsoft Shared/ink/en-US/micaut.dll.mui: no such file or directory

Fedora 39, with docker-ce-27.0.3-1.fc39.x86_64.
I tried plain mcr.microsoft.com/windows/servercore:ltsc2019, the same result (and the same SHA).

@jsafrane I got the same error as you when trying building Windows images with docker build on MacOS.
Try using docker buildx instead:
docker buildx build -f Dockerfile.reproduce --platform windows/amd64 .

docker buildx build -f Dockerfile.reproduce --platform windows/amd64 .

Same error as docker build.

I should have looked more closely to your Dockerfile.reproduce: you can't use RUN instructions if you want to build Windows images on another host than Windows. (See for example https://stackoverflow.com/a/71910784/4074148)
Example of a working Windows Dockerfile built on MacOS:
FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647
COPY README.md README.md

Docker did not even reach RUN, it's stuck at unpacking layers from FROM. It fails with COPY too.

sorry about that, reopening to investigate.

It must be some issue in my setup. I can see that Kubernetes is able to build Windows images on Linux based on 41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647 and that's what matters to me (logs, search for the SHA there). It was failing with the old image.
/close


cilium unstable, crashing every few minutes/hours

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Every few minutes/hours, Cilium will crash and restart. It works briefly (connectivity test passes, no visible issues with cluster networking) and then crashes again.
Cilium Version
cilium-cli: 0.12.11 compiled with go1.19.3 on darwin/arm64
cilium image (default): v1.12.2
cilium image (stable): v1.12.5
cilium image (running): v1.13.0-rc2

Kernel Version
Linux adenine 6.0.10 #1-NixOS SMP PREEMPT_DYNAMIC Sat Nov 26 08:27:56 UTC 2022 x86_64 GNU/Linux
Kubernetes Version
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.3", GitCommit:"434bfd82814af038ad94d62ebe59b133fcb50506", GitTreeState:"clean", BuildDate:"2022-10-12T10:49:09Z", GoVersion:"go1.19.2", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
File size too large for GitHub, uploaded to https://ocf.berkeley.edu/~njha/tmp/cilium-sysdump-20230105-114355.zip
Relevant log output
panic: addr is not a valid IP address

goroutine 1688 [running]:
github.com/cilium/cilium/pkg/ip.MustAddrFromIP(...)
	/go/src/github.com/cilium/cilium/pkg/ip/ip.go:971
github.com/cilium/cilium/pkg/fqdn.(*DNSCache).LookupIP(0xc000db3920, {0x0?, 0x50?, 0x8?})
	/go/src/github.com/cilium/cilium/pkg/fqdn/cache.go:450 +0x154
github.com/cilium/cilium/daemon/cmd.(*Daemon).GetNamesOf(0x0?, 0x1b2d2de?, {0x0, 0x0, 0x0})
	/go/src/github.com/cilium/cilium/daemon/cmd/hubble.go:343 +0x69
github.com/cilium/cilium/pkg/hubble/parser/seven.(*Parser).Decode(0xc0016b41e0, 0xc0014236b0, 0xc0033ac480)
	/go/src/github.com/cilium/cilium/pkg/hubble/parser/seven/parser.go:98 +0x310
github.com/cilium/cilium/pkg/hubble/parser.(*Parser).Decode(0xc001252600, 0xc0022c9580)
	/go/src/github.com/cilium/cilium/pkg/hubble/parser/parser.go:128 +0x2fd
github.com/cilium/cilium/pkg/hubble/observer.(*LocalObserverServer).Start(0xc004240a20)
	/go/src/github.com/cilium/cilium/pkg/hubble/observer/local_observer.go:128 +0xf4
created by github.com/cilium/cilium/daemon/cmd.(*Daemon).launchHubble
	/go/src/github.com/cilium/cilium/daemon/cmd/hubble.go:173 +0x129c

Anything else?
I suspect something like a workload in the cluster poisoning the cache or something, because at first this was only happening on one node, and now it has slowly spread to three nodes.
Looks like it has something to do with Hubble-- I'll try turning off Hubble and seeing if that works for now.
Code of Conduct

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

Hm, this definitely seems like a regression with the v1.13 version of the code. It seems that some conversion of an IP address is causing a panic. The code path suggests the IP is coming from the Hubble flows, so are you able to capture Hubble output (via hubble observe) as the issue occurs and provide it here?
It's possible that it might be some case of IPv4-in-IPv6 or vice versa formatted IP that causing an issue.

Could you filter out the connection for streaming the Hubble logs via grep -v or using Hubble's filtering logic? Also, please avoid passing -4 or -6 so that we don't filter out potentially useful output.

Okay, here we go: log2.log -- output of hubble observe -n cilium
crash happened at...
Jan  8 02:20:53.678 [hubble-relay-d5bffcc85-cmpxt]: Error "rpc error: code = Unavailable desc = error reading from server: EOF" on 1 nodes: adenine

There doesn't look to be anything relevant in that log 🤔

Yeah, I think we won't see the offending IP in the Hubble logs, because Hubble is crashing before it stores the offending flow in the ring buffer.
What might help getting the offending event identified is disabling Hubble and running cilium monitor (which doesn't do much flow post-processing) in the affected pod.
But regardless of actual IP, we probably should not use MustAddrFromIP in DNSCache.LookupIP and error out gracefully instead.

I've opened a potential fix here: https://github.com/cilium/cilium/pull/22994
I see two reasons why MustAddrFromIP can panic: Some IPv4-in-IPv6 issues, or the IP was nil (which can happen if net.ParseIP cannot parse the IP).
The latter case would occur here:
https://github.com/cilium/cilium/blob/ba1fd7dc9325286b8ce9fefe998d4b810e1647be/pkg/hubble/parser/seven/parser.go#L93
It seems, the previous code was fine with dealing with nil IPs. Thus, my PR restores the old behavior where GetNamesOf gracefully deals with nil values. It remains to be determined however, why we cannot parse the IP address in the first pace, and secondly, if Hubble should avoid calling into other functions with a nil IP.

@nikhiljha Would you be able to follow @gandro's suggestion here to disable Hubble and fetch the cilium monitor -t l7 output on any node that was previously affected by the panic?

I've been running cilium monitor -t l7 on two nodes for a while but it doesn't have any log output. This is running on #22994. I'll try again on -rc3 with hubble disabled tomorrow.


Usage link 404 error

hi the link you gave in the Readme dont load has a 404 error. is there a way you can put online or in the Readme.
it will be cool.

Done (a12aa54). Sorry for the inconvenience!


Proxy settings not implemented

The library is unusable when a proxy server is required. The code simply provides no method to transfer proxy settings. (E.g. Indy HTTP supports it, but there's no interface to access it from the Ntfy library code). Please add a method:
function Proxy(const AServer, APassword, AUsername: string; const APort: Integer): IRequest;

(Code example taken from RESTRequest4D.Request.Contract)

@bcp-software, Commits are here


When drinking stacked tea, two get consumed

When you have more than one tea cup in the same hotbar slot, and drink it, after a short delay, a second one will also get consumed.

What's the mod version? Is it the latest edition? I can't reproduce what you say.

But I can't actually reproduce it. I think it may be because of mod conflict. Could you provide more information?

I can reproduce with only TeaStory installed, but it doesn't happen 100% of the time.

For example, here I filled my hotbar with many teas, and I drank one each.  As long as I leave that same hotbar slot selected, there is a chance that after a short delay another one will get consumed.  You can see here, that I have drank two in some slots instead of one.

OK. I reproduced it. And I know how to deal with it. I will fix the bug soon. Thank you!

Strangely, I seem to still have this issue on 3.2.5-B4.1118-1.12.2, though it appears to happen a bit less often?

Well no, just rng

I‘ll try again next week. It's time that I should go to school.

I think the only way to solve this is to set the max stack size to 1, which is like what Tea the Story used to do.

Just like soup. I don't have better solution.


TOOL: Display "Applicant Name" as a column under the "Applications" tab

Description: As an admin, I want to see who submitted the application without having to open it.
Acceptance Criteria:

Display the "Applicant Name" on the table.

We will be looking at this in user testing
We will ask users in testing about