update usability/help_panel to 4.x, adding features:

get shortcuts from the quickhelp module, rather than creating them from scratch
make side panel resizable
make panel expandable to full screen
add readme, similar to wiki page
update screenshots, icon

Judging from the screenshot, this looks great.

Unfortunately, after activation, the button does not show up. Not sure whats wrong here :-(

Hmm, strange. Anything in the browser javascript console?

This is in the JS console:
Default extension for cell metadata editing loaded.
main.min.js:23979 Raw Cell Format toolbar preset loaded.
main.min.js:24027 Slideshow extension for metadata editing loaded.
main.min.js:12030 Loaded extension: usability/chrome-clipboard/main
main.min.js:12030 Loaded extension: usability/python-markdown/main
main.min.js:12030 Loaded extension: usability/toc/main
main.min.js:12030 Loaded extension: usability/limit_output/main
main.min.js:12030 Loaded extension: config/config_menu/main
main.min.js:23181 Session: kernel_created (9b9e21a9-a978-4f24-8643-4588fdfa0226)
main.min.js:22502 Starting WebSockets: ws://localhost:8888/api/kernels/f51e2e26-51de-4fdc-99b8-db39128ed085
http://localhost:8888/static/components/bootstrap/js/tooltip.js?v=20151008124651 Failed to load resource: the server responded with a status of 404 (Not Found)
main.min.js:12049 Failed to load extension: Array[1] Error: Script error for: components/bootstrap/js/tooltip(…)(anonymous function) @ main.min.js:12049
main.min.js:22160 Kernel: kernel_connected (f51e2e26-51de-4fdc-99b8-db39128ed085)
main.min.js:12030 Loaded extension: usability/ruler/main
main.min.js:22160 Kernel: kernel_ready (f51e2e26-51de-4fdc-99b8-db39128ed085)
:8888/nbextensions/usability/ruler/main.js?v=20151008124651:32 ruler_color: #808080
:8888/nbextensions/usability/ruler/main.js?v=20151008124651:39 ruler_column: 78
:8888/nbextensions/usability/ruler/main.js?v=20151008124651:44 ruler_linestyle: dashed
main.min.js:12030 Loaded extension: widgets/notebook/js/extension
:8888/nbextensions/widgets/notebook/js/extension.js?v=20151008124651:81 loaded widgets

Ah, OK, it looks like the bootstrap tooltip plugin may not always be
included, then. I'll add some error handling to fix this in a little
while...
On 8 Oct 2015 1:43 pm, "Jan Schulz"<EMAIL_ADDRESS>wrote:

This is in the JS console:
Default extension for cell metadata editing loaded.
main.min.js:23979 Raw Cell Format toolbar preset loaded.
main.min.js:24027 Slideshow extension for metadata editing loaded.
main.min.js:12030 Loaded extension: usability/chrome-clipboard/main
main.min.js:12030 Loaded extension: usability/python-markdown/main
main.min.js:12030 Loaded extension: usability/toc/main
main.min.js:12030 Loaded extension: usability/limit_output/main
main.min.js:12030 Loaded extension: config/config_menu/main
main.min.js:23181 Session: kernel_created (9b9e21a9-a978-4f24-8643-4588fdfa0226)
main.min.js:22502 Starting WebSockets: ws://localhost:8888/api/kernels/f51e2e26-51de-4fdc-99b8-db39128ed085http://localhost:8888/static/components/bootstrap/js/tooltip.js?v=20151008124651 Failed to load resource: the server responded with a status of 404 (Not Found)
main.min.js:12049 Failed to load extension: Array[1] Error: Script error for: components/bootstrap/js/tooltip(…)(anonymous function) @ main.min.js:12049
main.min.js:22160 Kernel: kernel_connected (f51e2e26-51de-4fdc-99b8-db39128ed085)
main.min.js:12030 Loaded extension: usability/ruler/main
main.min.js:22160 Kernel: kernel_ready (f51e2e26-51de-4fdc-99b8-db39128ed085)
:8888/nbextensions/usability/ruler/main.js?v=20151008124651:32 ruler_color: #808080
:8888/nbextensions/usability/ruler/main.js?v=20151008124651:39 ruler_column: 78
:8888/nbextensions/usability/ruler/main.js?v=20151008124651:44 ruler_linestyle: dashed
main.min.js:12030 Loaded extension: widgets/notebook/js/extension
:8888/nbextensions/widgets/notebook/js/extension.js?v=20151008124651:81 loaded widgets
—
Reply to this email directly or view it on GitHub
https://github.com/ipython-contrib/IPython-notebook-extensions/pull/347#issuecomment-146526520
.

@JanSchulz ok, I've pushed a commit which (touch wood) should fix this. Please let me know whether ti works for you...

Yep, it works, but I chromes print preview (ctrl+P) and afterwards printing does not work in "full text mode": I get "Druckvorschau fehlgeschlagen" (printpreview doesn't work) an dthe printing butotn is greyed out :-(
In split screen mode, the keybord shortcuts are printed next to the code, each using up half on the page :-(
Is there a way to generate the page content and open it in a new window (without saving the content to disk)?

Right! Well, progress, I guess.
You should be able to drag the sidebar to take up 90% of the page width, although this isn't a perfect solution, obviously. I get the same problem with Chrome's print-preview failing, though I'm not sure why. I'll look into it if I get time.
As for producing the content in another page... I think this might be possible in pure javascript, rather than a server-side extension, but I'm not sure. generating it from a server-side extension wouldn't be a great plan anyway, really, since it would make loading all the correct extensions and things complicated (since they can define keyboard shortcuts, it affects the help panel). However, since it's not clear what's causing the print-preview problem in the first place, I'd be reluctant to go rushing off trying to implement a javascript solution without knowing yet whether it'll actually help...

@JanSchulz fixed, I think. It turned out to be an issue with Chrome's print previewer being unable to deal with 100% height elements, so just hitting print might have worked anyway. I also fixed an issue where you'd only get a single column of keys when printed, rather than the two you get on screen (since the previewer considers the page only ~500px wide apparently). As before, please let me know whether or not this works for you...

This is much better than before!
Ready to merge, when you are.

Wow, great work. Printing works great! You might wanna upstream this...

Thanks a lot!
@jcb91 I owe you, that was usually half an hour c&p and formatting work in word to get a new shortcut tipsheet... Ping me if you want something done in python...

:)


info.isObject is never true in GeneratedClassCodeTemplate::generateGetArchetypeMacro

https://github.com/jsoysouvanh/Refureku/blob/b5d61a3eeeb2b4bdb19d5851bd2f0cf76caa205d/Refureku/Generator/Source/CodeGen/GeneratedClassCodeTemplate.cpp#L84
Hi! Great library! I have been trying to integrate this library to my engine and but sadly it looks like I can't get the above code to ever be evaluated to true with the following snippet:
// File: Component.hpp
#pragma once
#include <generated/Component.rfk.h>

class RFKClass() IComponentBase : public rfk::Object
{
	public:
		virtual ~IComponentBase() = default;

	IComponentBase_GENERATED
}

File_GENERATED

Removing the conditional to force the generation of getArchetype() solves my problem. But obviously is not the right way. 😅
Thanks!

Hi oyagci!
Thank you for the kind words :)
This usually happens when the parser can't rewind the hierarchy because it has unknown symbols.
Are you sure your parsing settings (inside the toml if you use it, or in the FileParsingSettings directly) are correct ?
Especially the "projectIncludeDirectories" part. It must match exactly the project include directories in your project (so you should at least have the path to the Refureku include directory there).
Let me know if that solves your problem :)


Segmentation fault (core dumped)

After installing manim with
pip install manimgl
I tried to run an example script from the docs, which produced the message
Segmentation fault (core dumped)
Even if I don't put in some script as a parameter, the error message remains the same.
I already tried uninstalling and then reinstalling, and since there is no detailed error message I don't know what other packages could invoke this.
OS System: Ubuntu
manim version: Probably the newest one, so 1.0.0
python version: 3.8.5

see #1387

None of the options worked for me, and the one that worked in that issue, namely
python -m pip install manimpango --no-binary :all: --force
produced an error that asked me to install pkg-config. After installing it using apt-get, now its showing me another error:
https://pastebin.com/NnXVwyPe

@UntacticalPenguin you should install Pango, see https://github.com/manimcommunity/manimpango#linuxmacos

Thanks, it worked!


[Snyk] Upgrade config from 3.3.1 to 3.3.3

Snyk has created this PR to upgrade config from 3.3.1 to 3.3.3.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.
The recommended version was released 2 months ago, on 2020-11-26.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Completed in a previous ticket. Closing.


Simple text tile

This was based off of this PR: https://github.com/concord-consortium/collaborative-learning/pull/1084
It removed extra functions added to tool-tile.tsx, and uses MST to observe and modify the text.
I don't think this should be merged. It just serves as an example of what has to be done for a very basic tile.

There is an updated version of this in the starter-tile branch.
https://github.com/concord-consortium/collaborative-learning/pull/1222


BaudOther(9600) fails where Baud9600 succeeds

I have a program I'm working on where I'd like to specify the baud rate from the command line. I'm using the BaudOther enum. I'm using an FTDI cable and if I use Baud9600 I can configure it properly but if I use BaudOther(9600) it fails. I'm not certain how to debug this further.

@Susurrus I do need to improve the support for non-standard baud rates with BaudOther. In this case, if you're only using fairly standard baud rates, it would be pretty simple to write a function to convert an integer baud rate to the appropriate BaudRate enum variant. I think that would be a useful thing to add to this crate. I'll add something for this in the next release.

That functionality is the whole point of BaudOther() I think already so I don't think there's a need for an additional function; I think there's a need for BaudOther() to work correctly. I'd be happy to chip in here and make or test changes with my hardware, but I don't really know where to start. If you can point me in the right directly maybe I could get BaudOther() to work right.

@Susurrus I believe there's a misunderstanding about the intended purpose of BaudOther. Baud9600, Baud1200, etc. are standard baud rates that are well-supported across many platforms. Using them should be fairly reliable. BaudOther, on the other hand, is provided to access non-standard baud rates (rates that don't have a specific BaudRate enum variant). Non-standard baud rates are system-specific, and so they are less portable and may not always work. Because of that, BaudOther is not guaranteed to work with all baud rates.
If you want to use 9600 baud rate, you really should use the Baud9600 enum variant. The method I'm proposing adding would make enum selection transparent to the user of the library. I'd prefer that, because it encourages correct usage, which increases portability. I should have time to work on it later this week, and I'll try to make the documentation clearer, too.

So if I understand you correctly you'd get rid of the enum completely and switch to using a function that takes in an arbitrary integer instead? I think that would be very beneficial.

Have you been able to use BaudOther() successfully? I'm not certain it works. I have two FTDI cables connected together that I can open and operate successfully at 921600 baud. I can't configure them properly with this library for that baud rate. So currently 9600 and 921600 don't work with BaudOther. Looking at https://github.com/dcuddeback/serial-rs/blob/master/src/posix/tty.rs#L367 it does look like a library error rather than an actual hardware error as there are many more values exposed by the OS-specific enum in termios (https://github.com/dcuddeback/termios-rs/blob/master/src/os/linux.rs#L131).
I'm not sure the best way to write the backend code, but I don't think the best interface for me, as a user of the serial.rs library, is to expose an enum interface for baud rates. They can be any value for a lot of different hardware, and exposing them as enums in the serial.rs API just makes them harder to use since the values are already numbers. I think they only interface should be using a u32 that is them mapped to the proper termios baud rates entirely in the backend. It should be much cleaner for me, the user of this library to do settings.set_baud_rate(921600); than wrapping things in BaudOther().

@Susurrus Did you try any of the seven baud rates that have match patterns using BaudOther in the method that you linked to above? I'd be interested to hear if one of them doesn't work for you. Obviously, any baud rates that aren't implemented there aren't going to work. If OS-specific baud rates (such as 921600 in Linux) is something you need, I can add those pretty easily.
Did you look at the referenced commit? It adds a function to get an appropriate BaudRate variant from an integer. There are several benefits to using an enum over plain integers, so I'm not planning on replacing the BaudRate enum. I explained the portability benefits above and clarified them in the documentation as well. Enums enable more errors to be caught at compile time and give the compiler freedom to optimize. The underlying OS interfaces use symbolic constants, so even if you were using C, you wouldn't be able to treat baud rates as just a number. The BaudRate::from_speed function (added in the commit referenced earlier in this thread) does what you're asking without discarding the benefits of using an enum.

Yes, I tried the 230400 baud rate, and that works fine.
I've tested your feature/integer-baud-rates branch, and it works for me. I did want to suggest you use the Into or From iterators for uint16 and str for BaudRate, instead of adding another function. Then you can just pass an integer or string directly into set_baud_rate and this extra function call wouldn't need to be called explicitly.
As to your second comment, you can still get compile-time errors even when using integers for constants, and for non-constants it can't be done anyways. With these changes you now have 3 interfaces to baud rates: this function that takes integers, specific baud rate enums, and then an enum for non-standard baud rates. The problem with this is that these are somewhat redundant between them, but the code doesn't support one of those code paths so things like baudOther(9600) fails which is surprising to the user. This is why I suggest only exposing integers in this library's API. There's a single, clear way to set the baud rates instead of 3 almost-equivalent ways. This follows from the Principle of Least Surprise and Python's One Right Way approach to things.

@Susurrus

Yes, I tried the 230400 baud rate, and that works fine.

Great. Thanks for confirming.

I've tested your feature/integer-baud-rates branch, and it works for me.

Sounds good. I'll go with that then. I don't want to complicate the API by adding multiple ways to set a serial port's baud rate. The current API provides a single, type-safe way to set the baud rate, and the new constructor makes it easy to convert numeric baud rates to the right enum. Anything else (like parsing strings) is application-specific. Let's agree to disagree about what's the least surprising interface.


Better configuration

Hi,
It would be nice to create a semantic configuration instead of using directly parameters in your service declaration.

Thanks for the hint! I'll take a look into it :+1:


Fix resolveBrick() to this.resolveBricks()

Reproduction steps:

Pass in images props.bricks, later after Masonry is already mounted
Masonry will issue a warning that resolveBricks is not found, this is because resolveBricks is a method within Masonry.

Resolved in v0.1.1.


Hotfix/qx aws secgroupids

这个 PR 实现什么功能/修复什么问题:

添加安全组同步日志
修复仅同步同一vpc底下的一个安全组问题

是否需要 backport 到之前的 release 分支:

release/2.11
release/2.10.0
release/2.9.0
release/2.8.0

/area region
/cc @swordqiu @yousong

Codecov Report

Merging #1860 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1860      +/-   ##
=========================================
+ Coverage     7.6%   7.61%   +<.01%
=========================================
  Files         412     412
  Lines       63666   63657       -9
=========================================
+ Hits         4844    4846       +2
+ Misses      58413   58403      -10
+ Partials      409     408       -1

Flag
Coverage Δ

#aFlag
7.61% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/compute/models/cloudsync.go
0% <0%> (ø)
:arrow_up:

pkg/compute/models/secgroupcache.go
6.38% <0%> (ø)
:arrow_up:

pkg/util/ucloud/instance.go
0% <0%> (ø)
:arrow_up:

pkg/baremetal/tasks/bm_register.go
0% <0%> (ø)
:arrow_up:

pkg/compute/guestdrivers/managedvirtual.go
0% <0%> (ø)
:arrow_up:

pkg/util/aws/instance.go
0% <0%> (ø)
:arrow_up:

pkg/util/seclib2/seclib.go
95.74% <0%> (+4.25%)
:arrow_up:

Continue to review full report at Codecov.

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

/approve
/lgtm


English version

Hi,
Is it possible to have English version of UI?

Hello,
Sorry, it is a project running in China only.
Br/Xing


Failed to create server

Hi, I want to install v2ray on ubuntu 16.04
When I installed it completely, and save new config, service cannot activate.
The error says Active: failed (Result: exit-code)
Screenshot of the error has been attached.

Thanks

Thanks for your help but there's a problem when I want to test configuration file returns command not found the error.
and here is the log:

Finally it's get OK, I have been using wrong uuid in config.
Thanks for your help


Widget should include a field for dtstart

The javascript part of RecurrenceWidget should include a way to add a start date to a rule. Right now none is saved. This leads to a dtstart of datetime.now() when the occurrences are generated.
For most users this is probably not a desired behavior.

For my use-case, it would make sense to have dtstart and dtend as part of the main widget. I'd suggest making this an option that gets passed into the widget. And with an optional keyword argument that can be passed into the model and form field definition. That way it can be backwards compatible for existing users but is easy to add for users that need it.

I have a use case when the admin must specify a recurring set of promo dates that begins on a specific date. For example, every Tuesday for 3 months, starting from 1 of June. Now we need to remember to generate that before the first Tuesday of June to create this properly, and it is a bit awkward.
Solution described by @stefanfoulis would be perfect.

In my current use case it would also make sense to be able to set dtstart directly in the form widget. I like @stefanfoulis backwards-compatible solution. If there is a fair chance of it being merged, I would take a shot at tackling this (optional) feature in a pull request.

Hi @zepp-lee - I'm open to merging something like @stefanfoulis suggests if it can be done without adding too much complication to the JS.

Has this completed being ignored?

If someone has a patch for this that can be merged, without complicating the JS too much, it'll be merged.


Update list of voting members

What does SPOT mean?

Ah, thank you. I would prefer to keep it as it was with the github handles only.


Action Group with Label set doesn't show Label on the UI

Package
filament/tables
Package Version
v3.0.12
Laravel Version
v10.18
Livewire Version
v3.0-beta.7
PHP Version
PHP 8.2
Problem description
When creating an ActionGroup with a label set, doesn't show the label
ActionGroup::make([
                Action::make('a')->label('Action A'),
                Action::make('b')->label('Action B'),
            ])->label('Header Actions Label')

In addition to the above issue, when there are multiple ActionGroups, they stick to each other. They need a margin between them

Expected behavior
As per the documentation here https://filamentphp.com/docs/3.x/actions/grouping-actions#customizing-the-group-trigger-style and the image showcased, the label should show on the ActionGroup

Steps to reproduce
Please refer to the code in the below repository. Class ActionGroupLabelNotDisplayIssue and the following code should help reproduce this issue
    public function table(Table $table): Table
    {
        return $table->query(function () {
            return User::query();
        })->columns([
            TextColumn::make('name'),
            TextColumn::make('email'),
        ])->actions([

        ])->headerActions([
            ActionGroup::make([
                Action::make('a')->label('Action A'),
                Action::make('b')->label('Action B'),
            ])->label('Header Actions Label')
        ]);
    }

Reproduction repository
https://github.com/abishekrsriaanth/filament-test
Relevant log output
No response

->button()


Enchanted Anvils drops improperly

Overview
When an anvil(that is overwritten by Apotheosis, regardless of enchantments) is broken by a Integrated Dynamics/Tunnels World Block Importer, the anvil doesn't drop itself(it doesn't go into the Integrated* network). An existing workaround is to break it with an Integrated * User Simulator set to break blocks instead, then pick it up with a World Item Importer.
This might be caused by non-standard drop handling.
Another issue is when the anvil lands on an incomplete block(Project Red framed wires, Integrated* logic pipes), it drops without the enchantments.
I suspect the issue is here, so I haven't submitted an issue on the Integrated* side yet.
Game Version: 1.12.2
Test
ID network used:
(Chest)(f)---(i)(A)
(Chest) Acts as the inventory of the network.
(f) Item Interface that connects the chest to the network
- A Logic Pipe from Integrated Dynamics
(i) World Block Importer
(A) Apotheosis Enchanted Anvil
Mods
Relevant Mods:

Apotheosis-1.12.2-1.10.5
IntegratedTunnels-1.12.2-1.6.10
IntegratedDynamics-1.12.2-1.1.0
CommonCapabilities-1.12.2-2.4.4

Relevant Mod Dependencies:

CyclopsCore-1.12.2-1.5.1
Placebo-1.12.2-1.6.0

All Other Installed Mods:

jei_1.12.2-<IP_ADDRESS>1
Hwyla-1.8.26-B41_1.12.2
Other Integrated* mods

IntegratedCrafting-1.12.2-1.0.8
IntegratedTerminals-1.12.2-1.0.12
refinedstorage-1.6.15

Majority of the Thermal Series by CoFH

CoFHCore-1.12.2-<IP_ADDRESS>-universal
CoFHWorld-1.12.2-<IP_ADDRESS>-universal
RedstoneFlux-1.12-<IP_ADDRESS>-universal
ThermalCultivation-1.12.2-<IP_ADDRESS>-universal
ThermalExpansion-1.12.2-<IP_ADDRESS>-universal
ThermalFoundation-1.12.2-<IP_ADDRESS>-universal
ThermalInnovation-1.12.2-<IP_ADDRESS>-universal
CodeChickenLib-1.12.2-<IP_ADDRESS>3-universal

TConstruct-1.12.2-<IP_ADDRESS>
Mantle-1.12-<IP_ADDRESS>
AppleSkin-mc1.12-1.0.9

Mods.zip

This is likely caused by the non-standard drop handling, but it is necessary as the drop is dependent on the tile entity.  The breaker would probably experience the same issue with shulker boxes (The same issue the AA breaker (currently) and the Mek digital miner (previously) had).
Not really anything that can be done about it from my end tho.


Update address.json

Site
Urlscan
Screenshot

royal.cash
https://urlscan.io/result/0642a7c5-d981-4032-ab9a-9b548f5f40ae/dom/
https://user-images.githubusercontent.com/97024090/177929405-c2a7bb7d-36ee-432d-a140-9f64a9a6f258.png

prostocash.com
https://urlscan.io/result/caae3a56-a1b2-4bc0-9ac1-43ad75e936cf/dom/
https://user-images.githubusercontent.com/97024090/177929520-c64e87d5-ed7f-4ed8-919f-79e65d04d91f.png

Never seen this kind of phishing kit before, but the sites themselves look sus.
The addresses hold little to no amount, so no one got fooled yet (?)
Let see what others think about it. I'd say leave it for now.


updates to match UI

minor changes to UI. Added a note about break glass accounts, a perfect place to mention it.
Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

I am refreshing this manually.  I need to incorporate a few other changes into the content.


Fix OUT_OF_DEVICE_MEMORY on window resize

Dragging the window edge on Linux causes dozens of XCB_CONFIGURE_NOTIFY events which quickly causes a VK_ERROR_OUT_OF_DEVICE_MEMORY in one of the calls to vkAllocateMemory in VulkanExampleBase::setupFrameBuffer().
This adds a small change to clean up the allocated memory for the multisampleTarget images.

Thanks for your PR, very much appreciated.
One thing I noticed: Multisampling is controlled by settings.multisampling, so deletion has to check for that. Will add that myself after merging.


Auto-generated Paths_xxx is a "member of the hidden package xxx"

I've recently graduated from navigating Haskell code via grep to fast-tags to ghcide. What a change! Thank you for making our lives easier.
Here's a minimal working example of a stack-based library project that leads to an error, and I'm not sure whether it's me or ghcide. It seems like there's a problem with the auto-generated Paths_Repro.hs file of my project.
File:     /home/tlo/repro/src/Repro.hs
Hidden:   no
Range:    3:7-3:18
Source:   not found
Severity: DsError
Message:
  Could not load module ‘Paths_Repro’
  It is a member of the hidden package ‘Repro-0.0.0’.
  You can run ‘:set -package Repro’ to expose it.
  (Note: this unloads all the modules in the current scope.)

I am using the following environment based on GHC 8.8.4.
tlo@carol:~/repro$ stack --version
Version 2.3.3, Git revision cb44d51bed48b723a5deb08c3348c0b3ccfc437e x86_64 hpack-0.33.0
tlo@carol:~/repro$ stack exec -- hie-bios version
hie-bios version 0.7.1 compiled by GHC 8.8.4
tlo@carol:~/repro$ stack exec -- ghcide --version
ghcide version: 0.4.0 (GHC: 8.8) (PATH: /home/tlo/.local/bin/ghcide) (GIT hash: 153536bda11fbf1ebee8434aa981911db73d09b8)

The above hie-bios executable was built together with ghcide (stack install --stack-yaml stack88.yaml hie-bios).
This is my directory layout in ~/repro. data and src are directories.
tlo@carol:~/repro$ tree
.
├── data
├── hie.yaml
├── Repro.cabal
├── Setup.hs
├── src
│   └── Repro.hs
└── stack.yaml

2 directories, 5 files

The .cabal file contains just a library. Note the data directory, which will lead to auto-generation of Paths_Repro.hs. I'm including it as an exposed module.
tlo@carol:~/repro$ cat Repro.cabal
cabal-version:     3.0
name:              Repro
version:           0.0.0

data-dir:          data

library
  default-language: Haskell2010
  hs-source-dirs:   src
  exposed-modules:  Repro, Paths_Repro
  build-depends:    base >= <IP_ADDRESS>

The source code of the library is pretty simple - all it does is import the auto-generated Paths_Repro.hs.
tlo@carol:~/repro$ cat src/Repro.hs
module Repro where

import Paths_Repro

hie.yaml makes the library source code as well as the auto-generated Paths_Repro.hs part of the Repro:lib component.
tlo@carol:~/repro$ cat hie.yaml
cradle:
  stack:
    - path: 'src'
      component: 'Repro:lib'
    - path: '.stack-work/dist'
      component: 'Repro:lib'

stack.yaml is pretty minimal and points to the current directory.
tlo@carol:~/repro$ cat stack.yaml
resolver: lts-16.12
compiler: ghc-8.8.4
compiler-check: match-exact

packages:
  - "."

Setup.hs is pretty minimal, too.
tlo@carol:~/repro$ cat Setup.hs
import Distribution.Simple
main = defaultMain

Let's build. So far, so good.
tlo@carol:~/repro$ stack build
Repro> configure (lib)
Configuring Repro-0.0.0...
Repro> build (lib)
Preprocessing library for Repro-0.0.0..
Building library for Repro-0.0.0..
[1 of 2] Compiling Paths_Repro
[2 of 2] Compiling Repro
Repro> copy/register
Installing library in /home/tlo/repro/.stack-work/install/x86_64-linux/eca3ea2dfcf47802c16cbff074593024128a25b42227008f01d8d58674357ac1/8.8.4/lib/x86_64-linux-ghc-8.8.4/Repro-0.0.0-KYMSFfd0OHq96ZnTxqxItm
Registering library for Repro-0.0.0..

Let's run ghcide. I'm only running it on src to avoid the No prefixes matched error when ghcide skips over Setup.hs. Without src, the error message about Paths_Repro.hs is the same, though.
tlo@carol:~/repro$ stack exec -- ghcide src
ghcide version: 0.4.0 (GHC: 8.8) (PATH: /home/tlo/.local/bin/ghcide) (GIT hash: 153536bda11fbf1ebee8434aa981911db73d09b8)
Ghcide setup tester in /home/tlo/repro.
Report bugs at https://github.com/digital-asset/ghcide/issues

Step 1/4: Finding files to test in /home/tlo/repro
Found 1 files

Step 2/4: Looking for hie.yaml files that control setup
Found 1 cradle
  (/home/tlo/repro/hie.yaml)

Step 3/4: Initializing the IDE

Step 4/4: Type checking the files
[INFO] Consulting the cradle for "src/Repro.hs"
Output from setting up the cradle Cradle {cradleRootDir = "/home/tlo/repro", cradleOptsProg = CradleAction: Stack}
> Configuring GHCi with the following packages: Repro
> /home/tlo/repro/.stack-work/install/x86_64-linux/eca3ea2dfcf47802c16cbff074593024128a25b42227008f01d8d58674357ac1/8.8.4/pkgdb:/home/tlo/.stack/snapshots/x86_64-linux/eca3ea2dfcf47802c16cbff074593024128a25b42227008f01d8d58674357ac1/8.8.4/pkgdb:/home/tlo/.stack/programs/x86_64-linux/ghc-8.8.4/lib/ghc-8.8.4/package.conf.d
[INFO] Using interface files cache dir: /home/tlo/.cache/ghcide/main-1fe712b57e70d0bcc9e2401739aeaa38de845e35
[INFO] Making new HscEnv[main]
File:     /home/tlo/repro/src/Repro.hs
Hidden:   no
Range:    3:7-3:18
Source:   not found
Severity: DsError
Message:
  Could not load module ‘Paths_Repro’
  It is a member of the hidden package ‘Repro-0.0.0’.
  You can run ‘:set -package Repro’ to expose it.
  (Note: this unloads all the modules in the current scope.)
Files that failed:
 * /home/tlo/repro/src/Repro.hs

Completed (0 files worked, 1 file failed)

I don't think that this is right. But maybe I'm misunderstanding things. I would have thought that both, Repro as well as Paths_Repro are a part of the Repro-0.0.0 package. At least that's what I thought my hie.yaml file said. How would hidden packages factor into this?
Checking with hie-bios succeeds (with what I think is an unrelated warning).
tlo@carol:~/repro$ stack exec -- hie-bios check src/Repro.hs
src/Repro.hs:3:1:Warning: The import of ‘Paths_Repro’ is redundant
  except perhaps to import instances from ‘Paths_Repro’
To import instances alone, use: import Paths_Repro()

When I change Repro.cabal to make Paths_Repro an "other" module, then this changes the error message.
tlo@carol:~/repro$ cat Repro.cabal
[...]
  exposed-modules:  Repro
  other-modules:    Paths_Repro
[...]
tlo@carol:~/repro$ stack exec -- ghcide src
ghcide version: 0.4.0 (GHC: 8.8) (PATH: /home/tlo/.local/bin/ghcide) (GIT hash: 153536bda11fbf1ebee8434aa981911db73d09b8)
[...]
File:     /home/tlo/repro/src/Repro.hs
Hidden:   no
Range:    3:7-3:18
Source:   not found
Severity: DsError
Message:  Could not load module ‘Paths_Repro’it is a hidden module in the package ‘Repro-0.0.0’
Files that failed:
 * /home/tlo/repro/src/Repro.hs

Completed (0 files worked, 1 file failed)

It almost looks like ghcide considers Repro.hs and Paths_Repro.hs to live in different packages, no?
In any case, I'm now wondering whether I am missing something, or whether there's an issue with ghcide.

Oh, and for reference: I got the idea to add .stack-work/dist to hie.yaml from #574.

Looks like 5dd52ec introduced the issue about two weeks ago. Versions before that correctly process my example. Isn't git bisect magic?

CC @pepeiborra - that doesn't look like it would have been an expected fallout.

I think this is a cradle problem, unrelated to 5dd52ec. But I might be wrong.
A cabal cradle does the right thing. The cradle generated by gen-hie does it right as well. But the stack cradle wrongly doesn't list the Paths module, and that prevents ghcide from locating them, which leads to the unhelpful error message "this module lives in a package".
Stack cradle
pepeiborra@pepeiborra-mbp ~/s/init [1]> hie-bios flags src/Main.hs
Options: ["-i","-odir=/Users/pepeiborra/scratch/init/.stack-work/odir","-hidir=/Users/pepeiborra/scratch/init/.stack-work/odir","-hide-all-packages","-i/Users/pepeiborra/scratch/init/.stack-work/dist/x86_64-osx-nix/Cabal-<IP_ADDRESS>/build/init","-i/Users/pepeiborra/scratch/init/src","-i/Users/pepeiborra/scratch/init/.stack-work/dist/x86_64-osx-nix/Cabal-<IP_ADDRESS>/build/init/autogen","-i/Users/pepeiborra/scratch/init/.stack-work/dist/x86_64-osx-nix/Cabal-<IP_ADDRESS>/build/global-autogen","-i/Users/pepeiborra/scratch/init/.stack-work/dist/x86_64-osx-nix/Cabal-<IP_ADDRESS>/build/init/init-tmp","-stubdir=/Users/pepeiborra/scratch/init/.stack-work/dist/x86_64-osx-nix/Cabal-<IP_ADDRESS>/build","-I/nix/store/88242sfskrw2mxv2pr4608nwccpw5q41-ghc-8.8.4/include","-I/nix/store/wrjgy3xkjsv7aqlmhhp1977ywmhk6l3q-git-2.28.0/include","-I/nix/store/kqpzwgfw1yw99536haqzg0jsa2lzxmqf-gcc-wrapper-9.3.0/include","-I/nix/store/m5wdi6x3ly0g6l0mibjnin82rbxjyasi-gmp-6.2.0-dev/include","-L/nix/store/88242sfskrw2mxv2pr4608nwccpw5q41-ghc-8.8.4/lib","-L/nix/store/wrjgy3xkjsv7aqlmhhp1977ywmhk6l3q-git-2.28.0/lib","-L/nix/store/kqpzwgfw1yw99536haqzg0jsa2lzxmqf-gcc-wrapper-9.3.0/lib","-L/nix/store/p20ys2ryai7h3hm2bihbk137is598k9z-gmp-6.2.0/lib","-package-id=base-<IP_ADDRESS>","-optP-include","-optP/Users/pepeiborra/scratch/init/.stack-work/ghci/e6487cf6/cabal_macros.h","-ghci-script=/private/var/folders/4m/d38fhm3936x_gy_9883zbq8h0000gn/T/haskell-stack-ghci/35ba5839/ghci-script","-package-db","/Users/pepeiborra/scratch/init/.stack-work/install/x86_64-osx-nix/4373fa4dbae3421908cbd892d447bf0f10a051cba390b6fe5bab7f602d67ca08/8.8.4/pkgdb","-package-db","/Users/pepeiborra/.stack/snapshots/x86_64-osx-nix/4373fa4dbae3421908cbd892d447bf0f10a051cba390b6fe5bab7f602d67ca08/8.8.4/pkgdb","-package-db","/nix/store/88242sfskrw2mxv2pr4608nwccpw5q41-ghc-8.8.4/lib/ghc-8.8.4/package.conf.d"]
ComponentDir: /Users/pepeiborra/scratch/init
Dependencies: ["init.cabal","package.yaml","stack.yaml"]

Cabal cradle
pepeiborra@pepeiborra-mbp ~/s/init> hie-bios flags src/Main.hs
Options: ["-fbuilding-cabal-package","-O0","-outputdir","/Users/pepeiborra/scratch/init/dist-newstyle/build/x86_64-osx/ghc-8.8.4/init-<IP_ADDRESS>/x/init/build/init/init-tmp","-odir","/Users/pepeiborra/scratch/init/dist-newstyle/build/x86_64-osx/ghc-8.8.4/init-<IP_ADDRESS>/x/init/build/init/init-tmp","-hidir","/Users/pepeiborra/scratch/init/dist-newstyle/build/x86_64-osx/ghc-8.8.4/init-<IP_ADDRESS>/x/init/build/init/init-tmp","-stubdir","/Users/pepeiborra/scratch/init/dist-newstyle/build/x86_64-osx/ghc-8.8.4/init-<IP_ADDRESS>/x/init/build/init/init-tmp","-i","-i/Users/pepeiborra/scratch/init/dist-newstyle/build/x86_64-osx/ghc-8.8.4/init-<IP_ADDRESS>/x/init/build/init/init-tmp","-isrc","-i/Users/pepeiborra/scratch/init/dist-newstyle/build/x86_64-osx/ghc-8.8.4/init-<IP_ADDRESS>/x/init/build/init/autogen","-i/Users/pepeiborra/scratch/init/dist-newstyle/build/x86_64-osx/ghc-8.8.4/init-<IP_ADDRESS>/x/init/build/global-autogen","-I/Users/pepeiborra/scratch/init/dist-newstyle/build/x86_64-osx/ghc-8.8.4/init-<IP_ADDRESS>/x/init/build/init/autogen","-I/Users/pepeiborra/scratch/init/dist-newstyle/build/x86_64-osx/ghc-8.8.4/init-<IP_ADDRESS>/x/init/build/global-autogen","-I/Users/pepeiborra/scratch/init/dist-newstyle/build/x86_64-osx/ghc-8.8.4/init-<IP_ADDRESS>/x/init/build/init/init-tmp","-optP-include","-optP/Users/pepeiborra/scratch/init/dist-newstyle/build/x86_64-osx/ghc-8.8.4/init-<IP_ADDRESS>/x/init/build/init/autogen/cabal_macros.h","-hide-all-packages","-Wmissing-home-modules","-no-user-package-db","-package-db","/Users/pepeiborra/.cabal/store/ghc-8.8.4/package.db","-package-db","/Users/pepeiborra/scratch/init/dist-newstyle/packagedb/ghc-8.8.4","-package-db","/Users/pepeiborra/scratch/init/dist-newstyle/build/x86_64-osx/ghc-8.8.4/init-<IP_ADDRESS>/x/init/package.conf.inplace","-package-id","base-<IP_ADDRESS>","-XHaskell2010","src/Main.hs","Paths_init","-hide-all-packages"]
ComponentDir: /Users/pepeiborra/scratch/init
Dependencies: ["init.cabal","cabal.project","cabal.project.local"]

(the implicit cradle gets it wrong too, /cc @jneira )
  Multi Cradle: No prefixes matched
  pwd: /Users/pepeiborra/scratch/init
  filepath:
  /Users/pepeiborra/scratch/init/.stack-work/dist/x86_64-osx-nix/Cabal-<IP_ADDRESS>/build/init/autogen/Paths_init.hs
  prefixes:
  ("./src/Main.hs",Stack {component = Just "init:exe:init", stackYaml = Nothing})
  ("./src/Paths_init.hs",Stack {component = Just "init:exe:init", stackYaml = Nothing})

Thanks for looking into this!
Let me know, if I can help and run more experiments on my end to establish whether this is or isn't related to 5dd52ec.
So far I have "1 file worked" for the preceding commit, 2eb2689.
tlo@carol:~/repro$ stack exec -- ghcide src
ghcide version: 0.3.0 (GHC: 8.8) (PATH: /home/tlo/.local/bin/ghcide) (GIT hash: 2eb26896ae2bf0f33abd74ed76caac3c62c3d51d)
[...]
Completed (1 file worked, 0 files failed)
[INFO] finish: User TypeCheck (took 0.17s)

And I have "1 file failed" for 5dd52ec when running ghcide on the same directory as above.
tlo@carol:~/repro$ stack exec -- ghcide src
ghcide version: 0.3.0 (GHC: 8.8) (PATH: /home/tlo/.local/bin/ghcide) (GIT hash: 5dd52ec0ff35c9617c11cbeb2614584c9ba5f596)
[...]
Files that failed:
 * /home/tlo/repro/src/Repro.hs

Completed (0 files worked, 1 file failed)

Hence my earlier comment about 5dd52ec. Sorry, if this turns out to be a red herring.

@uncle-betty for the shake of completeness, what is the effect in the editor? Do you get the same error opening Repro.hs within it and you dont get diagnostics or hover info in the module?

(the implicit cradle gets it wrong too, /cc @jneira )

The implicit cradle removes all autogen-modules from the cradle, and to be fair i dont know if it can do much more about that in a reliable way.
It could add them for the default lib/exe to mimic the hack described in #574. But it seems the hack does not work anymore, even with an explicit hie.yaml (due to 5dd52ec? the fact is the hack worked for me with an explicit stack hie.yamlat that point).
But if you dont add it in autogen-modules only would left the ugly hack of handle the module named Path_${package_name} if present in the .cabal file.
Not sure if it is a good idea, @Avi-D-coder?

I was never really clear what to do about auto modules. Until an explicit hie.yaml  works for this use case, it's a hie-bios issue.
I suspect hie-bios will need first class support for auto modules or for the build systems that use them.

@jneira - I'm using vim with the vim-lsp plugin. When I put on the cursor on Paths_Repro in the import Paths_Repro directive in Repro.hs, then:

:LspDefinition says No definition found
:LspHover says No hover information found

Thanks again, everyone, for looking into this.

I think I have some more insights.
It seems that 5dd52ec breaks my test case in a different way than current master. To locally resolve an import back in 5dd52ec, it was enough for a .hs file for the imported module to exist in one of the expected directories. In contrast to this, with current master the bar is higher and my issue seems to be caused in the following, different way:

Paths_Repro isn't reported as a target by hie-bios.
For an import to be locally resolved, ghcide still needs to find a corresponding .hs file in one of the expected directories, but on top of that the imported module also needs to have been reported as a target. (See getTargetExists in the rule for GetLocatedImports.) As Paths_Repro isn't a target, things break.

So, where do the targets come from that hie-bios reports? hie-bios harvests the command line arguments passed to ghc for stack repl. These are the options that ghcide obtains by running the cradle via hie-bios. Later ghcide runs addCmdOpts on these options to derive targets from them. To that end, addCmdOpts considers any ghci script from among the command line arguments and scans it for :add directives. The modules discovered in this way are added to the targets returned by addCmdOpts.
It seems like the REPL's  ghci script is created by stack. In my case, it only ontains Repro. So, only Repro is discovered and reported as a target.
Once I realized this, I looked for a workaround. I found that stack seems to put all modules found in hs-source-dirs  into the REPL's ghci script. Thus, adding the directory that holds Paths_Repro to Repro.cabal would be a (super hacky) workaround. And, indeed, the following works. (Note the added hs-source-dirs.)
cabal-version:     3.0
name:              Repro
version:           0.0.0

data-dir:          data

library
  default-language: Haskell2010
  hs-source-dirs:   src
  hs-source-dirs:   .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/autogen
  exposed-modules:  Repro, Paths_Repro
  build-depends:    base >= <IP_ADDRESS>

So, what's the conclusion? I think that it depends on what "target" means.

If the targets are supposed to exhaustively cover all source code files of a project, then I would say that hie-bios is broken. Possibly, it shouldn't just go through the REPL's ghci script, but maybe it should run :show modules in the REPL and parse the resulting output, which would include Paths_Repro.

If the targets are merely to be considered "roots" from which to explore the dependency graph, then maybe ghcide's criterion for local import resolution (i.e., in order to be resolved locally, an import needs to be a target) is a tad too strict.

But then again, I guess that there's a reason why ghcide switched to the stricter criterion. Could someone shed some light on this decision? Based on this, I'd then go and open an issue for hie-bios and suggest something along the lines of :show modules.

The contract between ghcide and hie-bios is that the latter provides a fully exhaustive list of cradles. This assumption is used at various places and is fundamental for correctness. @fendor correct me if I’m wrong.
The ghcide changes to locate modules started in https://github.com/haskell/ghcide/commit/b4589aebe639c9e5368e7b8413f794353aa55a55 which is a few commits earlier than the one you are pointing at. There are further changes later on spread across two or three PRs. These changes are required to prevent subtle bugs in multi package projects with shared import dirs.
Are you able to use the Cabal cradle while the issue gets looked at by the hie-bios team? That one works as expected.

Oh, no rush. I am happy to use the workaround I discovered.
I didn't mean to come off as pushy. Apologies, if I did. I just had some time on my hands today to poke around and learn a little more about the inner workings of ghcide and hie-bios.
Thanks for the information on the guarantees given by hie-bios - and have a good weekend!

@pepeiborra Indeed, that is the contract, but Stack breaks it. Afaict, there is no way to obtain all Targets with stack.
@uncle-betty Awesome detective work, that is exactly what is happening.
The conclusion is in my opinion that stack needs to define the interface we need so that we can support it properly. As a  first step, list the Paths_* module as a target in the ghci-script.

@fendor do we have an upstream Stack ticket saying exactly what information we are missing? And the consequences for Stack users?

I am afraid that maybe there is no direct negative consequences for stack final users, so there won't be much motivation to fix it.
Therefore maybe we should think in a workaround in hie-bios or in implicit-cradle. Afaik hie-bios does not even fires the repl, only collects the flags that cabal would use to fire it so it could not call any repl command.
Maybe hie-bioscould add auto Paths_pack_name to the stack target. It is a pretty stable convention.

I am afraid that maybe there is no direct negative consequences for stack final users, so there won't be much motivation to fix it.

Isn't the consequence for stack users a degraded HLS experience? That seems like a negative consequence.

Maybe hie-bioscould add auto Paths_pack_name to the stack target. It is a pretty stable convention.

That does seem a good idea though.

do we have an upstream Stack ticket saying exactly what information we are missing? And the consequences for Stack users?

No, I think we did not open one yet :/ Ghcide mitigated the issue by discovering modules by itself.

Maybe hie-bios could add auto Paths_pack_name to the stack target. It is a pretty stable convention.

Seems like a good work-around. Not sure though, how we can obtain the package_name :/

I looked into modifying stack and the following is what I could come up with. It's a pretty small change. Maybe polish it a little (I can read Haskell but I can barely write it) and submit it as a proposal when opening a ticket with the stack team? It's a branch off current master.
https://github.com/uncle-betty/stack/compare/master...uncle-betty:hie-bios
Here's how stack determines the modules to be included in the ghci script:

stack collects the modules from the .cabal file.
It then tries to match up the modules with .hs files. However, it only considers source code directories specified in the .cabal file (hs-source-dirs).
Those modules that have a matching .hs file go into the ghci script, the others don't. In particular, the auto-generated .hs files aren't found and thus don't go into the ghci script.

That's why explicitly adding the autogen directory as a source code directory to the .cabal file is a viable workaround.
My proposed changes make stack also check the autogen directories for .hs files, on top of the source code directories. It's basically about passing down the Cabal version to the point where it's needed to generate the autogen directory paths.
I have only superficial knowledge of the stack codebase, but at least I don't seem to have broken any tests in the stack test suite. So, maybe this is actually a viable fix.

Here's a proposal for a plan B: a workaround in hie-bios.
https://github.com/uncle-betty/hie-bios/compare/master...uncle-betty:stack-autogen
This proposal extends the wrapper script by adding the following:

It actually runs GHCi.
It sets the GHCi prompt to __MARK__ framed by two newline characters, so that it always appears on a line by itself.
It issues :show modules.
The easily identifiable __MARK__ prompt allows it to extract the output of :show modules from the overall output generated by the GHCi session: it's the lines between the first and the second __MARK__ line. That's what the awk script extracts.
It greps for modules whose names start with Paths_.
It appends the resulting module names to the command line arguments (as opposed to the GHCi script). This works, because addCmdOpts doesn't only look for modules in GHCi scripts, it also looks for anything among the arguments that doesn't look like an actual option and returns it as a target.

This proposal also fixes the issue for me. As far as I can tell, two more things would be required to make this an actually viable solution for everyone:

I assume that cabal.hs is for... Windows users? This would have to be extended, too.
For Cabal-based builds, there probably is duplication now: Paths_Repro is found in the GHCi script as well as among the command line arguments. So there would have to be deduplication of the targets returned by addCmdOpts, I guess.

In any case, I was just curious to find out what it would take to implement a workaround. I still would prefer the change to stack. Just seems less hacky.
Do you guys have existing relations with the stack people or should I simply go ahead and open a ticket with them, describing the situation and the proposed tweak to stack, and link back to this issue?

Does actually running ghci massively slow down loading up a package? That's my biggest concern - the time to start up a cradle is one of the annoying "does my project work" moments, so extending it is bad.

Oooooh, performance. I should have tried this with something other than my toy example, right?
Turns out that the performance is... hilariously bad! I just fired up ghcide with the modified hie-bios and ran it on the Agda code base - and it takes about 90 seconds for each GHCi run. Nine zero seconds! And there are a lot of GHCi runs involved. Then I want out to get myself a tantuni dinner around the corner, returned home, and it's still running.
Well, then, I guess this one didn't fly. Hooray for plan As (plans A?) instead!

@uncle-betty really great work
If there is no good enough codificable workaround and there is a manual one (although an ungly one) i would go for the right one: patch stack.

Thanks for your kind words. I am glad that I could contribute.
I opened a ticket with stack: https://github.com/commercialhaskell/stack/issues/5392

Alright, the above plan A proposal was accepted and has been merged into the master branch of stack.
Things now work well for me with my toy example as well as the Agda source code. Woohoo! I am a happy camper.
I can't imagine that the change will be part of the upcoming version 2.3.4 of stack, but judging from the version use on master it should be no later than stack version 2.4.0.
For everyone who comes here via a search engine before stack 2.4.0 is released: a workaround is to add to the .cabal file a hs-source-dirs directive for the directory that holds auto-generated files. In the case of my toy example above, this would be .stack-work/dist/x86_64-linux/Cabal-<IP_ADDRESS>/build/autogen. See the discussion above for more details.
Thanks, everyone, for the discussion. This is a great outcome, I think. I'm closing this now.

If you dont minf, i will reopen this to give it more visibility, until the new stack version wih the fix is released
(i am afraid that it is an issue that can be related with the changes made in the patch 😟 )

Thanks for the heads-up. I commented on the stack issue, contemplating a possible way forward.

Just a quick update: stack version 2.5.1 was just released, which contains the fix proposed above to support auto-generated modules.
The stack error reported in commercialhaskell/stack#5407 was resolved by turning the error into a warning. So, the functionality required by ghcide is still there in the official stack release.
I guess now it's official - this is resolved! Woohoo!
Closing.


feat(iroh-net): Log the crate version number

Description
This adds a DEBUG-level log logging the crate version number.
Breaking Changes
None
Notes & open questions
This is not the first log message appearing, the MagicSock and a few
other pieces already have been logging by this time.  Also I'm not
particularly bound to this wording.  Maybe there are other things that
should be added to this line?
Change checklist

[x] Self-review.
[ ] Documentation updates following the style guide, if relevant.
[ ] Tests if relevant.
[ ] All breaking changes documented.

Did you test whether the environment variable reports the version of the crate, even if it's a deep transitive dependency? I.e. I'd like to avoid a case where it reports version "0.1.0", if you compile "my-crate v 0.1.0" which depends on "iroh-net v 0.26.0"

Pretty sure that's fine: https://doc.rust-lang.org/cargo/reference/environment-variables.html


Validate arguments before interpreting query.

We didn't use to validate that all the expected arguments are present before starting to interpret queries. Now we do :)

Ugh I forgot that the interpreted_mode_v3 branch doesn't lint cleanly at the moment 😢  Still need to put in the work to clean that up and merge it into main, let's not block this PR for the sins of the parent branch.
The pytest runs succeeded though!

Ugh I forgot that the interpreted_mode_v3 branch doesn't lint cleanly at the moment 😢  Still need to put in the work to clean that up and merge it into main, let's not block this PR for the sins of the parent branch.
The pytest runs succeeded though!


Set search to match title first

This screen shot is a pretty good example of what I mean

Is there any way to make sure it matches with titles first?

I agree and suppose Atom should be on the top of the results.
I will try to fix it

Is there a way to disable the "recent items" feature at all? It looks like it is causing this issue, as recent items are always prefereed. Maybe an item that has been executed previously could be "tagged" as favorite (and gain a slight score upgrade), but does not appear in its own section.
Using Hain since a few weeks, great work you're doing!

@Fannon I believe we don't need to another option to disable it, but I suppose your suggestion is more useful. I will try. and Thanks for the compliment!

Resolved at 80da941b5ae835afbab5c4fccefb3cd9ddd7ca30

Please verify this is still an issue with v0.6, I believe this has been addressed.  If not, please re-open.


Black squares showing instead of items

Addon Version
Latest
World of Warcraft Version
Classic Era (And SoD/Hardcore)
Describe the bug
When i open my bag, sometimes items are black spots. No idea is showing, its just a black square. When i hover over it the item shows again.
Steps to reproduce
Hard to replicate buy i notice it alot when I add new items in my inventory. Not sure whats going on but any suggestions would be great.

Fixed


Clarity on package setup

So far, it has been quite easy to set the package, but there are a few minor hiccups. I understand this package is quite new and will have more documentation in the future, could you please provide some clarity.

How to set the package to use for multiple apps within the same repository
There is a success page, which is kinda the default the page that it redirects to on successful installation of the app and also when the user opens an app that was already installed. Is there a way to open a different page instead of opening the success page when the app is opened.
Based on the Usage section (https://github.com/culturekings/shopify-app-auth-laravel#usage), are these variables always accessible on the views or should I use it similar to how it is implemented in https://github.com/culturekings/shopify-app-auth-laravel/blob/master/src/Http/Controllers/AuthController.php#L32

Updated readme & code. Should be all working now.

That's what app_name is for in the routes etc, multiple apps.
Not currently. You can set up a redirect on that view if you like so the user never sees the view when it loads, however at the moment each app must have an install success page.
I've beefed out the usage section. Use appName variable in the route to find secret and key in the config file to use for api call.


chore(deps): bump golang.org/x/tools to v0.1.10

Changes

chore(deps): bump golang.org/x/tools to v0.1.10

/kind cleanup
Release Note
N/A
Docs
N/A

@julz this is fixed afaik

yes master is golang.org/x/tools v0.24.0 now, this ancient PR is no longer needed :) closing


Schema design - Schema samples - Session Management - Needs Readme

Create a readme for this example.
Gaming profile in the DynamoDB Documentation, we need a simplified version for this readme.

Hi @tebanieo can you assign this to me? Thanks!

Hi @tebanieo, is there a document that we need a simplified version of for the readme? The initial comment is pointing to a Gaming profile doc, rather than Session Management. Thanks!

I have sent you a private message, please use that as reference.


Console errors in Harvester cluster's provisioning page

Setup

Rancher version: 2.9-head
Rancher UI Extensions:
Browser type & version:

Describe the bug

To Reproduce

Go To Cluster Management
Create a Harvester cluster.
Once the cluster is created, click on Edit Config.

Result
Expected Result

Screenshots

Additional context

unit test is sufficient. moving to done


Update JdbcConnectionSource.java

If the connection is not closed in the releaseConnection(DatabaseConnection connection) method, then the number of unused (idle) connections will accumulate over time, and exceed the max. simultaneous connections to the DB. E.g. in case of PostgreSQL this exception will come up soon, if you use the close() method only in the original implementation of this class. "FATAL: connection limit exceeded for non-superusers"

This is a class which is a single connection data source so the connection is never closed until the connection source is closed.  Are you talking about the JdbcPooledConnectionSource?


Controllers

I want to ask.
I can understand why do so in the Yii1, but why do so in the Yii2, I can not.
Why each controller (file name, class name) to add the word "Controller"?
In the second version Yii, uses a namespace and I don`t see a strong need for this suffix.
Can you explain why made this decision and left the suffix for all controllers?
Thanks in advance for your reply.

One reason for doing this is to be able to locate all controllers by just looking at their file names.

Agree that all controllers are usually lie in the same directory.

I think it is a relic of the past, from which should be abandoned.

I think it is a relic of the past, from which should be abandoned.

Not all because of that. Imagine we remove the Controller suffix. Now a post controller would be named as Post, which is very confusing as we also have Post model class. In our previous discussion, we agreed certain suffixes are helpful, such as Interface, Behavior, even though they are not necessary. Closing this as we don't have plan to make the change.


lowerBoundUpperBoundCal

Issue Id you have worked upon -
Lower Bound - Upper Bound Calculator #544
Briefly explain your program logic -
This tool allows the user to enter set X and set Y, choose whether Z is the intersection or union of set X, Y, and finally output the upper and lower limits of set Z.
Screenshots(Attach 2 screenshots of your own input and output) -

By raising this PR I affirm that -

[x] My code follows the guidelines of this project.

[x] I have performed a self-review of my own code.

[x] I have commented my code.

[x] My code gives the correct output.

[x] I affirm that I strictly follow contributing guidelines and code of conduct.

@amwaiting1,
There is a file mismatch. Kindly the revert the files that are added and add the required file.


Feature Validation for Media query based Show/Hide

Feature Request
https://material.angularjs.org/latest/layout/options
Is there functionality like show hide depending on window sizes implemented like ones in the above link ?

Yes, we provide the same hide-xs and show-xs (or any breakpoint) as those from flex layout.

Closing since its an old issue, and now its deprecated since @angular/flex-layout is out


Add parameters for chatgpt deployment capacity and sku name

To allow for easier use by developers who have quota restrictions, could you add azd env parameters in main.parameters.json for capacity (integer, default to 30) and skuname (string, default to either Standard or GlobalStandard)?
https://github.com/Azure-Samples/agent-openai-java-banking-assistant/blob/main/infra/main.bicep#L56
https://github.com/Azure-Samples/agent-openai-java-banking-assistant/blob/98e8dad88e730764f4eb8bbd956f47d898791aa9/infra/main.bicep#L283
Example:
https://github.com/Azure-Samples/openai-chat-app-quickstart/blob/7d90b9820d3f765cbb3411fae8c7624e521c42f8/infra/main.parameters.json#L32
This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [X] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

@pamelafox  capacity parameter was already there in bicep ( but not in params file). Added both in params and bicep file.

Thanks Davide!


Updates for rpi3/rpi3b+

They still need some polishing but at least it's an improvement over the current repository status with a broken build.

When merging this, please add a symlink rpi3b+ to rpi3bplus . I'm using both links in my slides.


Add WebSocketUpgradeTests to Kitura-NIO

Earlier websockets upgrade was tested only in Kitura-WebSocket-NIO. Adding WebSo
cket upgrade tests to Kitura-NIO by creating dummy WebSocketService and Connecti
on upgrader.

Thanks @harish1992. One more suggestion: Can you please explore the possibility of using NIOWebClientSocketUpgrader to do the client side upgrade? See an example here: https://github.com/IBM-Swift/Kitura-WebSocket-NIO/pull/40/files#diff-98b202bd3cdff8a4a77dc981cb8018a3

Thanks @harish1992. One more suggestion: Can you please explore the possibility of using NIOWebClientSocketUpgrader to do the client side upgrade? See an example here: https://github.com/IBM-Swift/Kitura-WebSocket-NIO/pull/40/files#diff-98b202bd3cdff8a4a77dc981cb8018a3

@pushkarnk thanks for suggestion. NIOWebClientSocketUpgrader automatically populates the web socket upgrade headers, hence upgrade cannot be tested for invalid headers. So we will have to keep the current implementation.

Thanks @harish1992


ERROR in Entry module not found: Error: Can't resolve './src' in 'C:\Idessign'

Do you want to request a feature or report a bug?
yes it is bug

What is the current behavior?
C:\Idessign>webpack
Hash: 18bc2fd105d4883da519
Version: webpack 4.2.0
Time: 108ms
Built at: 2018-3-24 18:56:38
WARNING in configuration
The 'mode' option has not been set. Set 'mode' option to 'development' or 'production' to enable defaults for this environment.
ERROR in Entry module not found: Error: Can't resolve './src' in 'C:\Idessign'
my webpack.config.js
const  webpack = require('webpack'),
path = require('path'),
const APP_DIR = path.resolve(__dirname, "./src/");
const browserConfig ={
entry :
  APP_DIR + 'client/index.js',

output : {
path : BUILD_DIR,
filename : "[name] bundle.js",
publicPath:BUILD_DIR,
},
}
always nothing
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
the compilation
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
Version: webpack 4.2.0
windows 8.1profetionnel

Could you create a sample repository with a small example on how to reproduce this problem? Configuration seems fine.

src folder exists? You are using wrong paths in your configuration.

I have the same question, this is a bug.
Version: webpack 4.2.0
windows 8.1profetionnel

It looks like some paths are misconfigured. I encourage you to ask your question on StackOverflow instead. We try to use the issue tracker for bug reports and feature requests, as well as some discussions, but this appears to be a very localized question.
I’m closing for these reasons.

I have the same problem.It hasn't solved the problem yet, do you have any idea?

@peacecup please open a new issue with the reproduction code in a github repository

the problem comes with<EMAIL_ADDRESS>the configuration it is correct
look my  webpack.config.js
const  webpack = require('webpack'),
path = require('path'),
ExtractTextPlugin = require("extract-text-webpack-plugin"),
nodeExternals = require('webpack-node-externals'),
srcPath = path.resolve(__dirname, "./src/"),
distPath = path.resolve(__dirname, './src/build/');
const HTMLPlugin = require('html-webpack-plugin');
const BUILD_DIR = path.resolve(__dirname , "./src/build/");
// var APP_DIR = path.resolve(__dirname, "src/app");
const APP_DIR = path.resolve(__dirname, "./src/");
const IMG_DIR = path.resolve(__dirname, './public/images');
const browserConfig = {
entry :
APP_DIR + 'client/index.js',
// APP_DIR + '/route/index.jsx',
resolve : {
alias:{
images : IMG_DIR
},
},
output : {
path : BUILD_DIR,
filename : "[name] bundle.js",
publicPath:BUILD_DIR,
},
module : {
    rules : [
        {
            test : /\.(js|jsx)$/,
            include : APP_DIR,
            loader : 'babel-loader',
            exclude: /node_modules/,
            query : {
            presets:[ 'react', 'es2015'],
          }
        },
        {
            test:/\.css$/,
            include: APP_DIR,
            loader:['style', 'css']
        },
        {
            test:/\.scss$/,
            include: APP_DIR,
            use: ExtractTextPlugin.extract({
              fallback: "style-loader",
              use: "css-loader!sass-loader"
            })
        },
        {
          test: /\.(png|jpg|gif)$/,
          use : [
            {
              loader: 'url-loader',
              options:{
                limite:8192
              }
            }
          ]
        }
    ]
  },
  plugins: [
    new ExtractTextPlugin("styles.css"),
    // new HTMLPlugin(),
    new HTMLPlugin(),
  ]

};
but when i run webpack
C:\Idessign>webpack
Hash: 18bc2fd105d4883da519
Version: webpack 4.3.0
Time: 116ms
Built at: 2018-3-28 12:58:19
WARNING in configuration
The 'mode' option has not been set. Set 'mode' option to 'development' or 'production' to enable defaults for this environment.
ERROR in Entry module not found: Error: Can't resolve './src' in 'C:\Idessign'
C:\Idessign>

Yes, configuration is correct, but again, your paths are not:
const APP_DIR = path.resolve(__dirname, "./src/");: src folder doesn't exist.

i have the same problem when use webpack4.2.0. is this problem solved?

it's caused by the error setting of 'script', you can inspect is it error
eg: 'webpack-dev-server --inline --progress --port 8001 --config webpack.dev.js'

@frankshin to help even more people here, if possible create a simple repository, where it is capable to reproduce your problem. This can help even more when they are making tests for it.

Excuse me.
The same problem occurred in my tiny project so I arrived at this page.
I tried to build a smallest project to reproduce it.
here
Thank you for glancing over it.

Same problem. It is not easy to find the source of the problem :/

@Inokinoki webpack searches for src/index.js. The file does not exist.

At https://webpack.js.org/concepts/ is written:
"Since v4.0.0 webpack does not require a configuration file."
Without configuration file, webpack only works if there is a src/index.js file. This information (in bold) could be explicit at docs.

Hi Florent,
Ok, done: #2035
Leandro
On Fri, Apr 13, 2018 at 4:20 AM, Florent Cailhol<EMAIL_ADDRESS>wrote:

@leandrojk https://github.com/leandrojk Would you mind open an issue in
https://github.com/webpack/webpack.js.org?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/webpack/webpack/issues/6858#issuecomment-381047129,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUAx8AoH8m4eTWkg7J31RoLmsDxBIhNks5toFG1gaJpZM4S51xc
.

--
Leandro J. Komosinski

I met this problem too,it took hours to find the problem out,may be you guys are making the same mistake like me, we should use "module.exports" instead of "module.export"

changed file to index.js and worked great!!

For me this error was related to using the old way of loading a config file.
I was using
var myConfig = Object.create(webpackConfig); webpack(myConfig, function (err, stats) { .........
instead of just using the config directly like this
webpack(webpackConfig, function (err, stats) { ..........

I met this problem too.And I think the errorr was:

I met this problem too.And I think the errorr was:

You defined a variable named browserConfig but you didnot assign it to module.exports,it should be this:
module.exports=browserConfig
2.Use module.exports instead of module.export

Just came across this error, while walking through this documentation, https://webpack.js.org/guides/getting-started/
The issue as it turns out is due to the working directory in relation to the npx command. I needed to be in the root of my project before running npx webpack.

ERROR in Entry module not found: Error: Can't resolve './src/index.js' in '<dir>'

^ Would be more clear.

maybe you need to use backslash? '.\src\index.js'

This particular issue I believe has to do with when webpack resorts to its default configuration on Windows it tries to resolve ./src and can't.  It would need to resolve .\src instead.  That's probably a bug.

if for some reason you used utf-8, i.e.: accented characters ( IDN, ex: é ) will also lead to this problem even though the underlying OS ( in this case centos 7 ) file system does not have a problem with it.
If the IDN character is a domain name, you can bypass this bug by converting it to punycode
(xn--...... . tld ).
One thing is for sure, user mishap or not, closing this issue every other week will not make it go away.

try to go up folder, not src.

Hey,first you have to set the mode to development.
In the package.json file , you need to type this :
"scripts": {
"build": "webpack --mode production"
}
then the src problem is you have to create a src folder in which you have to create a index.js file.
then try running npm run build.
It works.

mark

I double @zifn4b and @domainoverflow, I spent hours on Windows trying to solve this but when tried the same project on Ubuntu 16.04 it worked like magic!

and yet @SirajKakeh the issue is closed every other week ..

Why is the issue closed?

For everyone encountering this issue, it is most probably a configuration issue.
If you still think it is a bug, please open a new issue including an example to reproduce the error. Best put it in a GitHub repository.


Error during setup

# python3 setup.py install
...
Best match: ws4py 0.5.1
Processing ws4py-0.5.1.tar.gz
Writing /tmp/easy_install-l7xa9n7j/ws4py-0.5.1/setup.cfg
Running ws4py-0.5.1/setup.py -q bdist_egg --dist-dir /tmp/easy_install-l7xa9n7j/ws4py-0.5.1/egg-dist-tmp-i1gk3rym
  File "build/bdist.linux-x86_64/egg/ws4py/server/tulipserver.py", line 43
    f = asyncio.async(self.handle_initial_handshake())
                ^
SyntaxError: invalid syntax

  File "build/bdist.linux-x86_64/egg/ws4py/async_websocket.py", line 87
    asyncio.async(closeit())
            ^
SyntaxError: invalid syntax

CU,
Arno

Which python version are you running?
I tested setup.py for python3.6.9 and python3.8.5.
Which are the current versions for Ubuntu 18.04 and 20.04 at the moment.

Ubuntu 20.04:
Python 3.8.5 (default, Jul 28 2020, 12:59:40)
Does not seem to affect basic operation. My RIPng test works ;o)

I have been able to replicate the issue on a fresh 20.04 install. But it seems that this is not causing any functions of VNet-manager to fail.
The only related issues I have found were referring to Python3.7 on Debian Buster, which since have been fixed.
This seems like a ws4py issue to me, which as long as it doesn't break any functionality is not a problem.

Stale, closing


[Documentation Bug]: Grammatical Errors/Clarity Issues

Describe the bug ✍
There are a few grammatical errors and unclear sentences. I also noticed the website hosting the games was mentioned, but it was difficult to find a link to the website to view what others have contributed.
Provide step by step information reproduce the bug 📄
View the README.md.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @a-sommer !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

I will work on this issue. Thanks!

Hey @a-sommer 👋!
@kunjgit here,
Hope you are enjoying this hacktober 😀
We are excited to share that we are opening issue from our side where you will be going to add games on our website 🚀
Work on this issue 🔥
and help us building GameZone 💗
if you still haven't joined us join us on Discord
See you soon 😊

i want to work on this issue,kindly assign me this issue @kunjgit

Hello @a-sommer, Time's up!⏰
Sorry for closing your issue!
But it's more than a week since we haven't received anything from your side 😢 .
Come up with new ideas, create a new issue and make sure you finish it within a week! 🔥
All the best! 🚀
Happy Hacking! 💗

Hey @a-sommer ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Cmd to scroll up and down

Use well defined description while adding a technical tip.
Made some changes and merging


Update resources names

Change the names of recently checked in resources.
Description

Minor changes in missing resources names that were recently checked in.

@ranjeshj I will run the pipeline after the certificate PR is merged and this branch is updated

@ranjeshj I will run the pipeline after the certificate PR is merged and this branch is updated

/azp run

/azp run

I've also cherry picked the certificate commit so we can merge it into token experiment.

I've also cherry picked the certificate commit so we can merge it into token experiment.


What node i need use for reading data from OPCDA-server?

Good time of day! I am beginner. Please help!!!
What is the difference between node-red-contrib-opc-da and node-red-contrib-opcda-client?
In my telemetry project, i use OPCDA-server. What node i need use for reading data from OPCDA-server?

Best regards!!!!

Greetings
node-red-contrib-opc-da is part of the OPCDA packages maintained by ST-One. This other node you mentioned, node-red-contrib-opcda-client is a node mantained by @emrebekar that add the possibility of writing to the server. Currently if what you need is reading data from an OPC-DA server, using node-red-contrib-opc-da will be enough. As far as I know both use the same library node-opc-da created by ST-One.
Best regards

Great! I have some problem to connect node-red-contrib-opc-da to OPCDA-Server (LacroixTelemetryOPCServer). I assume that LacroixTelemetryOPCServer only works correctly with the LacroixOPCDA-client. Can you take the time to test node-red-contrib-opc-da with LacroixTelemetryOPCServer? I can configure for you remote access to my test-LacroixTelemetryOPCServer. The data on the OPCDA-server is updated every 15 minutes. IP/log/psw - i am ready to send it to your personal e-mail. I only need your confirmation of correct operation node-red-contrib-opc-da with LacroixTelemetryOPCServer.

Hi Pol-65! I have to do exactly the same. I also have a LacroixTelemetryOPCServer and I want to parse data into MQTT topics. Bumped into this thread by chance and I'm totally astonished as LacroixTelemtryOPCServer doesn't seem to be widely spread. Did you finally manage to connect node-red-contrib-opc-da to LacroixTelemetryOPCServer?


[STYLE]Centering cards related to issue #38

Hi!
Hope this solves the issue #38 for centering the cards, if you have any concerns or suggestion please make sure to tell me! :)
Valeu!

Woops! Closed it by accident haha, sorry!


Can you please add README/Getting-started?

Thanks for publishing this JDBC driver, can you please add some some documentation?

+1

Hi @gkorland!
I have added a detailed README.
Please let me know if you need anything else.

Thanks, looks good! I'll try to follow it.
Do you plan to publish it on Maven repository?

@gkorland
We didn't plan to publish the driver on Maven repository.
However, if the Redis community is interested in this, then we might consider it!


Bugfix remove deprecated findDOMNode method

Currently, we get such a warning:
Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of InputElement which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://reactjs.org/link/strict-mode-find-node
This problem happens because findDOMNode method deprecated. So we don't need to use it.
This PR should solve this problem.

@LEMing yes, of course. There is no problem with building

Would love to have this one merged too 🙂

would be awesome to have that merged :smiling_face_with_three_hearts:

I fully support this MR

can you please consider to merge this

Please put this on live

Please, accept this PR.

Please mege, @sanniassin :)

@sanniassin, could you pretty please merge this?

Please merge this pull request, @sanniassin.

How many people does it take to merge this?

Any news?

@sanniassin Any news? Can we merge?

@sanniassin Can you merge this? We needing a lot.

@sanniassin Can you please merge?

This Pull Request has been open for a while.
@sanniassin Will it be merged?

I'm closing this pr, because author of project does not respond for PR a long time

For those who are using version 2.0.4, here is a fork with the fix https://github.com/zenbill/react-input-mask/pull/1. The bundled files are in the repo too, so just point your package.json to our main branch and you should be ready to go.

There's actually a fundamental reason why this PR can't be merged. It breaks the tests for passing in children:
function Input(props) {
  return (
    <InputMask mask="99/99/9999" value={props.value} onChange={props.onChange}>
      <MaterialInput type="tel" disableUnderline />
    </InputMask>
  );
}


[FLINK-14590][python] Unify the working directory of Java process and Python process when submitting python jobs via "flink run -py"

What is the purpose of the change
This pull request unifies the working directory of Java process and Python process when submitting python jobs via "flink run -py".
Brief change log

Remove working directory setting when creating python process.
Adapt PYTHONPATH creation to support run python process in java working directory.

Verifying this change
This change is already covered by existing tests, such as PythonEnvUtilsTest.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@HuangXingBo Thanks for your review! I have addressed your comments. Please take a look.

Thanks @WeiZhong94 . +1 from my side.

@hequn8128 Thanks for your comments! I have addressed them in the latest commit.


fix: adjust the token-card placeholder by default

Feature Request
Describe the Feature Request

[x] Adjust the placeholders to fill the cards by default. Like the first Image in Additional Context
[x] Adjust also in OfferSummary

Related Code
TokensList
TokenCardsPlaceholder
Additional Context

Closed by #191


[Bug]: Airtime does not increase despite deducting from mpesa when on fuliza

Description
When I buy airtime with the app from mpesa with fuliza, it shows a confirmation message successful, that it has been purchased for account stax, but my airtime never increases in balance. So where does this money go?
Steps to reproduce

Open stax app
Buy airtime
Enter safaricom, amount 2 shillings and continue.
Enter mpesa pin
Submit

Expected result
The airtime is purchased from mpesa, I enter a confirmation whether to accept fuliza or not, and the message returned is for account <my_number>.
Actual result
Once I enter my pin and submit, the app goes ahead and buys the airtime for me and even accepts to use fuliza. The message from mpesa is then returned saying airtime has been bought for account stax, not my number
Link to screenshots/screen recordings
https://drive.google.com/file/d/1rI6TSGutMSsX1ZHYAR-OoMn6JzfblkE_/view?usp=drivesdk
Device name
Huawei y5 2019
Android OS
9
Is your phone dual SIM or single SIM?
Dual SIM
Which telco are you using for this test?
Safaricom
Stax device ID or email address
<EMAIL_ADDRESS>

Related to #690


WIP: Generalized WCS -- try #3

This is a work-in-progress to get the generalized WCS stuff serializing to/from ASDF.
All of this is written against embray/astropy@9307fbafe741 (the compound modeling branch).
There's a few things in modeling that I either don't understand or need improvement:

[ ] Models don't have equality defined, so it doesn't seem to be possible to serialize a model from disk, reload it and compare it against the original.  Is that a hard thing to add?

[ ] I've had to use some private APIs related to compound models (see compound.py below).  Any thoughts about how to provide a public API to what I need?

[ ] modeling only has an AffineTransformation2D.  What would be involved in making it n-dimensional?  In general, I don't think we should have separate classes for different dimensionality, with the exception of the very-specialized projections (TAN, XPH etc.) where n-dimensionality doesn't make sense.

@embray: This has been updated to work with current astropy master and is passing the tests (hooray!).  The one outstanding issue is using the ._tree member of compound models in order to introspect the tree and serialize it to YAML.  (See compound.py for what exactly it does).  Any thoughts about how to make a public API for that?  Maybe just add a property tree that returns _tree?

That might be a start.  How do you feel about the expression tree interface itself?  I think it's fairly easy to use, but part of me wants something "better" where exactly what that is remains undefined.
I'm also increasingly unhappy with how the tree is represented internally.  For a binary tree like this it would be easy to represent the nodes as a flat list rather than a nested data structure, while still providing the same user-level interface.  There are several algorithms that I feel like would be simpler if the tree were represented this way, rather than having to traverse the nodes as is currently necessary.  But that's more of an internal detail...

@embray: On the naming issue: How about this:

&: concatenate
|: compose

@mdboom What is the plan for this PR? I am using it locally but it would be easier if it's merged now, even if things are changed later.

I've been working on it a bit but mainly been sidetracked.  I'm fine with merging it and continuing to improve it incrementally, though.

I'll give Travis-CI a chance to test this, and then merge.

Great! Thanks!
And a question - given an asdf file, I see how I can read/open it, but how can I generate a model object from it?

The work to join jwst_lib.models and ASDF is still ongoing.  It's been the bane of my existence for some time...

Sorry, overloaded term again. How do I generate an astropy.modeling model? For example, given a rotated2d.asdf file (and since there's a schema for it), what is the command to get a modeling.Rotation2D object. I feel like I'm missing something simple.

:laughing: overloading models again...
You would do asdffile.tree['my_model'] to get it (where my_model is just wherever you happened to store the transform in the tree.  The conversion from modeling objects to YAML and back happens automatically.

Here's my asdf file:
#ASDF 0.1.0
%YAML 1.1
%TAG ! tag:stsci.edu:asdf/0.1.0/
--- !core/asdf
smallrotation: !transform/rotate2d
  angle: 2.4
...

I get a dictionary
 rot=pyasdf.AsdfFile.read('rot.asdf')
 rot.tree['smallrotation']
Out[33]: {u'angle': 2.4}

Is my asdf file wrong?

Ah -- it's a bug with this PR.  The transform classes weren't getting imported (and the unit tests did this, so they weren't catching this).  I'll have an update here momentarily.

I think this is working now, but @nden, would you mind double-checking before I merge?

Yep, it works.

I think the name of this method asdffile.tree is confusing. I didn't think it was a bug since it returned a dictionary and I thought it represented the tree of models.

It's the tree of objects stored in the ASDF file.  http://asdf-standard.readthedocs.org/en/latest/tree.html
You can store transforms anywhere in it -- it's just JSON/YAML data structures.  I agree it's not the greatest name -- it's what I've been using to refer to the main heirarchical content of the ASDF file.  Any suggestions?

I guess I expected .tree to return the YAML data structure and something else to create the object, something like "instantiate" which is a terrible name. May be it's just me,  not very good at names.


connect with React

how can i make it backend server and connect it with react through sockets?

You can use Socket.IO with React. See https://socket.io/how-to/use-with-react

Thank you.. I'll go through it

@ShakeelKhalid1913  Have you figured it out?

Yes. I actually found a repository on it. That helped me.

@ShakeelKhalid1913 I started working on it too

Great. how can i help you ?

I might rewrite Tiktok-Chat-Reader with a React front-end. I can upload a repo, can you check it out?

Yea sure.


Support SiteList change in ReqMgr - aggregate all PRs

Fixes #12037
Status
SUPERSEEDED BY: https://github.com/dmwm/WMCore/pull/12120
Description
SUPERSEDES: https://github.com/dmwm/WMCore/pull/12146
With the current change we allow SiteLists related actions for statuses: staging, acquired, running-open in ReqMgr2
Before making a call to central services for changing any of the request parameters, an additional step is executed to
to check which are the allowed parameter modifications for the given status and if the so provided new values from the rest call actually differ from the workflow parameters already defined in central couchdb.
With the current change we no longer ignore all the rest of the request arguments provided with the REST call in the cases of a change of the Request priority. See: https://github.com/dmwm/WMCore/issues/8457#issuecomment-366195086
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
This PR provides a cherry-pick of 3 pull requests that have been recently reverted. Changes have been originally provided by:
https://github.com/dmwm/WMCore/pull/12077
https://github.com/dmwm/WMCore/pull/12108
https://github.com/dmwm/WMCore/pull/12111
And on top of them the following one should be rebased:
https://github.com/dmwm/WMCore/pull/12120
External dependencies / deployment changes
None

NEVER  MERGE
SUPERSEEDED BY: https://github.com/dmwm/WMCore/pull/12120


Update for Swift 1.2

Mentioned in issue #2, app doesn't run in newer version of Swift

Updated and pushed to master


Please link to doc about Additional endpoints not included

Please link to this document about "additional endpoints not listed on this page".  It lists Office365 and Azure URLs required by IT admins.  https://docs.microsoft.com/en-us/microsoft-365/enterprise/additional-office365-ip-addresses-and-urls

duplicate


Update generators.mdx to show latest versions in example

Update the version numbers used in the samples to line up with current latest versions.
fastapi sample references version 0.0.33, which is markedly older than the current 0.3.6. This made it unclear to me if the latest release on fern-python repo is indeed correct to use in the fastapi generator
Please help validate if the versions I entered are indeed correct

Additionally, it would be great if the docs could make it clear that the releases on fern-python correspond to the versions that could be used for all python generators.


Cancelling a VsTask forever hangs

Very similar to https://github.com/microsoft/vssdktestfx/issues/69, except the repro is the following:
    [Fact]
    public async Task CanAwaitCancelled2Task()
    {
        var completionSource = new TaskCompletionSource<bool>();

        IVsTask result = ThreadHelper.JoinableTaskFactory.RunAsyncAsVsTask<bool>(
           VsTaskRunContext.UIThreadNormalPriority,
           async (ct) =>
           {
               await completionSource.Task;  // Comment this out to avoid the hang
               throw new OperationCanceledException();
           });

        await Assert.ThrowsAnyAsync<OperationCanceledException>(
            async () =>
            {
                completionSource.SetResult(true);

                await result;
            });
    }

In MockVSTaskCompletionSource, if I comment out this line the hang is avoided:
    public void SetCanceled()
    {
        this.taskCompletionSource.SetCanceled();
        this.UnderlyingTask.Cancel();  // Comment out this to avoid the hang
    }

I've stepped through this code, but I'm no closer to understanding why commenting out that line fixes this. From all I can see, the only thing that calling this.UnderlyingTask.Cancel does, is trigger the CancellationTokenSource passed to pass the underlying delegate in VsTaskLibraryHelper.RunAsyncAsVsTask.
Any ideas?
@AArnott @BertanAygun

I'll take a look.

There is a race condition here. I've seen it pass under a debugger, but it usually hangs. The critical point appears to be whether result has already completed when await result; is executed.
Still looking...

The continuation was getting canceled... 🤦🏼♂


[CWS] add pool layer of events used in fallback and snapshot

What does this PR do?
This PR adds a pool of *model.Event to be used by the newEBPFEventFromPCE in snapshot and fallback from map/proc paths. The goal here is to reduce the allocation caused by those code paths.
Motivation
Describe how to test/QA your changes
Covered by unit tests
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Telescope search_dirs

Is this option supported? As of right now I can't get it to work.
:lua require'telescope'.extensions.repo.cached_list{search_dirs = {"~/.dotfiles/nvim/.config/nvim/plugin"}}

Hi, thanks for opening this issue!
That seems useful, I’m looking into implementing it.

This is now implemented (#26)


Roll engine c83ec26f351f..51486a5494a8 (3 commits)

https://github.com/flutter/engine/compare/c83ec26f351f...51486a5494a8
git log c83ec26f351fed56341a8959d1d711c7ec2fe423..51486a5494a84ee5b2eef9ae968c13619b03f193 --no-merges --oneline
51486a549 New Plugin API PR2: Introduces ActivityAware, ActivityControlSurface, and ActivityPluginBinding. (flutter/engine#8943)
b3b817a9b Add a minimal set of symbols to the dynamic symbol table for Linux executables (flutter/engine#8937)
96ffc893e Copy the Dart Runner from //topaz into the engine. (flutter/engine#8949)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (chinmaygarde@google.com), and stop
the roller if necessary.

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/4701699441164288

Commit queue failed; closing this roll.


Bug when selecting photo on Samsung Galaxy S4 in google photos app

Sometimes i get the message that there are no photos selected, while i just selected a photo

Can you provide a bit more information, such as your code and specific steps required to reproduce?


RibbonCommandHystrixThreadPoolKeyTests throws compilation error in Eclipse with Oracle JDK 1.8.0_131 on WIndows 10

Hi,
RibbonCommandHystrixThreadPoolKeyTests is throwing compilation error in eclipse and Spring IDE. Getting error AbstractRibbonCommand is a raw type. References to generic type AbstractRibbonCommand<LBC,RQ,RS> should be parameterized
Using

Eclipse (Also tried Spring Took Suite IDE)
Oracle JDK 1.8.0_131
Windows 10

Kindly see the images.

Current code
	public static class TestRibbonCommand extends AbstractRibbonCommand {
		public TestRibbonCommand(String commandKey, ZuulProperties zuulProperties) {
			super(commandKey, null, null, zuulProperties);
		}

		@Override
		protected ClientRequest createRequest() throws Exception {
			return null;
		}
	}

Changing to following fixes the compilation error and the test class RibbonCommandHystrixThreadPoolKeyTests passes all tests successfully. Can someone please confirm if this is the right thing to do - not sure what those tests are doing, haven't done much digging into them.
	public static class TestRibbonCommand extends AbstractRibbonCommand<RestClient, HttpRequest, HttpResponse> {
		public TestRibbonCommand(String commandKey, ZuulProperties zuulProperties) {
			super(commandKey, null, null, zuulProperties);
		}

		@Override
		protected HttpRequest createRequest() throws Exception {
			return null;
		}
	}

Thank you.

Hi. I GUESS that the problem is caused by eclipse java compiler. Eclipse always uses eclipse java compiler(ejc) instead of oracle's javac. The code is compiled without any error on oracle's javac.
I've posted the PR to fix the problem https://github.com/spring-cloud/spring-cloud-netflix/pull/2107.

Great! Thank you @yongsungyoon

Thanks @yongsungyoon

Closed via #2107


Can anyone reproduce the claimed accuracy?

I trained on Resnet using Pascal + SBD, but got an accuracy of 74.5%. All settings are default values.

By using the following settings, I managed to achieve 77.24% at 24 epochs.
Setting:
1 dataset: Pascal + SDB
2 4 gpus, BatchSize = 16
3 Backbone: ResNet
4 —freeze-bn False
5 LR: (replace the function def call(self, optimizer, i, epoch, best_pred) in utils/lr_scheduler.py)
if epoch<10:
lr = 0.007
if epoch >= 10 and epoch <=20:
lr = 0.0007
if epoch >= 21 and epoch <=40:
lr = 0.00007


hidden characters?

When copying sass to be compiled out of either the browser or app, it appears to contain some invisible characters which causes compilation to error. Viewing as raw results in no errors.

I'm not sure I follow. Is this about hubot-slack, or something else Slack related?

As there is no CSS in hubot-slack, marking as off-topic and closing.


Calendar In C

Description 📜
I have prepared a documentation on Calendar In C
This fascinating program prints a calendar of the year on the basis of :

Year
Month by Month in sequential order by inputting Year by the user
Day by inputting Date , Month and Year

Hope you find the Date, Date, Month of your choice! :)
Enjoy the code!
Fixes #7386

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] C/CPP

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Okay sir,

@Suvraneel I have added a description part above the code and some comments in the code as well :)
I have made the required changes. Have a look 👍


Add MRE(Minimal reproducible example) to test library easy and fast

The sample app provides a lot of setup and configuration, which is great!
However, if I just want to quickly test your library and see how it works, there’s no simple, concise example to follow. Instead, I have to dig into the sample app's source code, which includes many settings that I don’t need at the moment, making it overwhelming to try the library for the first time

Hi, thanks for the feedback. You spent time creating this issue, rather than reading the library documentation. First, I won't do the simple sample (the first time you run the sample app, it's simple by default). Second, explore it.


Link readme's installation section to doc/installation; improve installation doc

Related issue (if exists):
#2269 #2492 #2292

Coverage remained the same at 97.612% when pulling e6e8fa120197bfda58be1a49d297305f79248380 on Boshen:installation-doc into e14fa8eb9d4798e6d687100861c782cbe9d41cb1 on ReactiveX:master.

This is related / possible dupe of long hanging https://github.com/ReactiveX/rxjs/pull/2292 . (Not sure why 2292 is stall until now though :/)

LGTM


Port minion registry to generic etcd

Ported minion registry to genericetcd storage
Call validation.ValidateMinionUpdate via nodeStrategy
master and service registry have an interface to node storage instead of registry

And I'm not sure the last commit is right. In #2115 PUT the same body returns 409 , but test cases were updated to return 200 except Node resource.

@dchen1107 : assigning to you, but please feel free to outsource to someone else.

!! Glad you post it today, I was going to do the same thing.
I also plan to add a status store for posting node status later, like this:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/registry/pod/rest.go#L75
Just want to check with you if that is on your radar?

You mean newly implment nodes/status api to update status like here, right?
I don't understand the context, but I can help to do that.

Yes. nodes/status.  I already started looking at it, but contribution welcome!  Let's get this in first though.
Ping me on irc (deyuan) if you plan to work on it.  We don't want dupliate work : )

Please do it. Then, I'll look other registries for porting.

e2e tests passed with a fix.

fyi, I'm already porting replication controller

@smarterclayton Moved MatchMinion to pkg/registry/minion/rest.go, and removed this since e2e tests passed.
@bprashanth Rebased to #5534.
e2e tests passes except for monitoring and cadvisor, but it seems by other problems?

@kazegusuri if it's unrelated flake and you don't see an open issue, please file one. fyi i usually rerun specific tests with ginko when one or two fail https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/devel/development.md

Rebased to HEAD and verfied all e2e passed. PTAL.

one last comment then LGTM

Needs rebase. If possible please merge this PR today - it'll make my life a bit easier.

Rebased to HEAD and verified e2e test passed. Please review again since sourcecode was changed a little.
The main change is stop using node interface and use node registry as is.

Will merge on green