Tibble printing

Is still messed up. The lock file has the latest version of tibble so I'm not sure what's going on.

omg... I think the font import issue in #14 fixed this.

Just a heads up...it looks like the tibble are printing fine in the deploy preview for #14: https://5fa03c6e360045000853099c--nervous-golick-ef3308.netlify.app/.
But I'm still seeing the weird issue in the published deploy (after merging #14): https://5fa040d2ebc8420a18b219a5--nervous-golick-ef3308.netlify.app/welcome.html.
Very strange. I wonder if this is more of an issue with Netlify? Maybe a closer look through the deploy logs could help.

This is the issue that will not go away. It's so bizarre. The actual deploy was fine earlier but now is not. Must have been the most recent merge. I don't get it.

🤪 🤪 🤪
I'll try to look into this some more, and if I don't find anything maybe it's worth crowdsourcing on Stack Overflow or RStudio Community?

Sure. I did check in with Alison about it before and she said she'd seen it. But updating tibble didn't seem to fix it.

ah, right! it does indeed seem likely to be an issue with {tibble} bc just glancing through it looks like all the other types of output are printing fine. I'll dig through that repo and community forums to see if others are having similar issues at the moment

This.... seems to be fixed currently?

I think this is fixed. At least it is right now. I'm going to close it for the time being and hope it is truly fixed.


Question: Comparison between this and other archival products

See:

https://github.com/webrecorder/webrecorder
https://github.com/webrecorder/pywb
https://github.com/webrecorder/warcio

Are they compatible with one another?
Do they produce the same format, or are they different in nature?

22120 is able to archive everything you browse by hooking into the browser directly. Then offline, you can use your browser as normal, and your browser still works like you're online -- for the pages you've already browsed.
The archive format in 22120 is simple JSON files, organized by directory that represents their origin. There is 1 JSON file for every resource the origin serves you.
More information about it is in the README
See: https://github.com/dosyago/22120 for instructions on how to install from the source, or from npm and for the latest binaries see here:
https://github.com/dosyago/22120/releases/latest

@crislin2046 hold on, I am asking for a comparison, not just what they do since ArchiveBox and others are too similar.

I don't know that much about ArchiveBox so my contribution to the comparison is to share what I know. Other people can then compare with ArchiveBox based on that, using what they know! 😄

https://github.com/pirate/ArchiveBox#comparison-to-other-projects
https://github.com/pirate/ArchiveBox/wiki/Web-Archiving-Community#Web-Archiving-Projects

@pirate thanks foe the explanation, but could you describe how WARC differs from the native ArchiveBox format?

There isn't really an "ArchiveBox format", it does produce some JSON index files, but really the main output is the output of the tools that it calls to archive each site, e.g.:

png: screenshot of the site
pdf: pdf version of the site
html: DOM dump of the site rendered in chrome after 2s of JS execution
WARC: wget WARC archive (same format as pywb output and other tools)
wget archive: static html + assets as archived by wget, it's normal html, not any proprietary format
media: e.g. mp3s, movies, git code repositories, etc are all raw fiels, not in any proprietary format

You can find more info here: https://github.com/pirate/ArchiveBox/wiki/Usage#Disk-Layout


iOS 12.2 fatal crash

With iOS 12.2 all apps crashes with this plugin
019-03-04 12:30:09.349866+0100 MiApp[447:68531] Apache Cordova native platform version 4.5.5 is starting.
2019-03-04 12:30:09.350620+0100 MiApp[447:68531] Multi-tasking -> Device: YES, App: YES
2019-03-04 12:30:09.383522+0100 MiApp[447:68531] CDVWKWebViewEngine: trying to inject XHR polyfill
2019-03-04 12:30:09.404853+0100 MiApp[447:68531] *** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<WKWebViewConfiguration 0x121d0fca0> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key _alwaysRunsAtForegroundPriority.'
 Do you have the background plugin installed?

Try the following in the Plugins>AppBackgroundMode.m file ----
(void) swizzleWKWebViewEngine
{
if (![self isRunningWebKit])
return;
Class wkWebViewEngineCls = NSClassFromString(@"CDVWKWebViewEngine");
SEL selector = NSSelectorFromString(@"createConfigurationFromSettings:");

SwizzleSelectorWithBlock_Begin(wkWebViewEngineCls, selector)
^(CDVPlugin *self, NSDictionary *settings) {
    id obj = ((id (*)(id, SEL, NSDictionary*))_imp)(self, _cmd, settings);

    if ([settings objectForKey:@"wksuspendinbackground"]) {
        NSLog(@"exist");
    } else {
        [obj setValue:[NSNumber numberWithBool:YES]
               forKey:[APPBackgroundMode wkProperty]];
    }

    [obj setValue:[NSNumber numberWithBool:NO]
           forKey:@"requiresUserActionForMediaPlayback"];

    return obj;
}
SwizzleSelectorWithBlock_End;

}

i'm going to try

cool I made the change in the platform>ios section

Same error. I uninstalled the background plugin and not working. The error is in this plugin cordova-plugin-ionic-webview

I think keep the background plugin installed and then apply the code. Which folder did you apply the code?

I apply directly to xcode.
Later I tried removing the background plugin and not working too
So the error is on the cordova-plugin-ionic-webview

mmm.. try updating the plugin to version 4.0.0

I'm using 4.0.0

This was fixed in both latest of 4.x and 2.x. If you are still seeing the crash you either aren’t on the new version, or have another plugin with the same bug.

I'm on version 4 -->
cordova plugin list -->
...
cordova-plugin-ionic-webview 4.0.0 "cordova-plugin-ionic-webview"
.....

Removing plugin cordova-plugin-ionic-webview works fine

Removing this -->   [obj setValue:[NSNumber numberWithBool:YES]
forKey:[APPBackgroundMode wkProperty]]; works

yes 100% that line causes the app to crash. That's why I added a condition around it.
if ([settings objectForKey:@"wksuspendinbackground"]) {         NSLog(@"exist");     } else {         [obj setValue:[NSNumber numberWithBool:YES]                forKey:[APPBackgroundMode wkProperty]];     }
Although I'm not sure what else might break by removing that line. Anyway good stuff!


Make use of AzDO service connections to pull AzDO repos

Consider refactoring the tarball creation logic and how it handles authenticating to AzDO repos.  During CI, it is hypothesized that AzDO service connections can be used instead of the current implementation that adds credentials into the url as done here.  When considering alternative solutions, keep in mind we still want to have a way for devs to build a tarball locally targeting AzDO repos.

[Triage] This is obsolete with the introduction of the VMR.


Pointing the packaged setup wizard (in each release) to the release.

Currently, the setup wizard has a flag for users to specify which release or branch to use.
https://github.com/GoogleCloudPlatform/forseti-security/blob/explain-pre-release/scripts/gcp_setup/setup_forseti.py
But if users were to follow the setup documentation, this flag is not mentioned, would not be used, and would then just default to point to master, which can cause the setup to bork as master's code base moves ahead and out of sync with the DM templates.
http://forsetisecurity.org/docs/quickstarts/forseti-security/index.html
https://github.com/GoogleCloudPlatform/forseti-security/blob/master/scripts/gcp_setup/environment/gcloud_env.py#L784
Some options:
1: The documentation can be updated to tell users how to use this flag.
2: The setup wizard can prompt user to enter this.
3: Track the version in the forseti_conf.yaml, which will be updated before each release.
3: When release is created, the packaged setup wizard is pointed to the release.

I'll take this in 2 steps.

Update documentation, first.
Default the setup wizard to the release version, which involves the following:

Fix the setup.py version import to use execfile instead of importing the version from g.c.security
Import that version into the setup wizard. I prefer not to have to update so many places to track the release version. (Right now we update deploy-forseti.yaml.sample as well as g.c.s.init; I would like to keep it that way.)

I will only address step 1 in #478 and in a separate PR for documentation.

Since step 1, then step 2 is not needed as we have to moved to the git release flow, where master is the latest release version.  So, no changes would be needed.


Unable to compile tf2_ros dashing

In file included from /opt/ws_moveit/src/geometry2/tf2_ros/src/static_transform_broadcaster.cpp:36:0:
/opt/ws_moveit/src/geometry2/tf2_ros/include/tf2_ros/static_transform_broadcaster.h: In instantiation of ‘tf2_ros::StaticTransformBroadcaster::StaticTransformBroadcaster(rclcpp::node_interfaces::NodeTopicsInterface::SharedPtr) [with AllocatorT = std::allocator<void>; rclcpp::node_interfaces::NodeTopicsInterface::SharedPtr = std::shared_ptr<rclcpp::node_interfaces::NodeTopicsInterface>]’:
/opt/ws_moveit/src/geometry2/tf2_ros/src/static_transform_broadcaster.cpp:41:63:   required from here
/opt/ws_moveit/src/geometry2/tf2_ros/include/tf2_ros/static_transform_broadcaster.h:67:76: error: no matching function for call to ‘create_publisher<MessageT, std::allocator<void>, PublisherT>(std::__shared_ptr<rclcpp::node_interfaces::NodeTopicsInterface, (__gnu_cxx::_Lock_policy)2>::element_type*, const char [11], rmw_qos_profile_t&, bool, std::shared_ptr<std::allocator<void> >)’
     publisher_ = rclcpp::create_publisher<MessageT, AllocatorT, PublisherT>(
                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
       node_topics_interface.get(), "/tf_static",
       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       custom_qos_profile, false, std::make_shared<AllocatorT>());

Solved using the pre-installed version.

This preinstalled version should not be enough

I'm reworking the current Docker image to be able to compile the current master against dashing. We should have a look in our port, the status of this certain package.


Interactive editing memory shows "I'm sorry, Something happened with my server connection..."

Steps to reproduce
Click on scrapbook.
Click on Memory bar.
Click on desired Memory.
Memory popup is open.
Click on rotating teal shadow text.
Memory popup is closed.
Ensure Active: "" above the chat is shown to the user.
Update the memory to add new content to the memory.
Actual result:
Chat window shows "I'm sorry, Something happened with my server connection, please type try again to try again."
Expected result:
Chat window should indicate user that the memory is updated.
100% reproducible with v.0.0.21
Refresh the memories
Memory is updated although above message is shown to the user. This part is working as expected.

FYI @Mookse .

@Vudum Great catch and a deep issue where I've miscoded the way I manage calls when they are sequential to OpenAI; this is a larger fix that will also address something with relive memories - this might take me the week to fix, but I'm on it

options, discovery

manage linear calls inside of MyLife (which makes it more extensible to less functional models)
address closure of mRunFinish and requires_action


[Bug]: The guidelines menu is toggling on the right instead of left

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
on clicking the guidelines icon which is on the left side, the menu opens on the right side of the screen. It leads to a bad user experience.
Hence, the position needs to be on the right while it should also close from the same position.
Expected behavior
Menu should open as pop-up on the same place as the menu icon from the icon or as a side menu bar
Add ScreenShots
No response
On which device are you experiencing this bug?
Chrome, Windows
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[ ] I'm a SSOC'24 contributor
[X] I want to work on this issue

please assign me the issue so that i can work on it


Does not work.

Script does not work. Cannot be installed via pip, and when running the executable, the example of "wudz-lit -f "C:\file.txt" -s -d -x 100" just shows the help menu.

All issues fixed and releases updated.


Hindley-Milner type signatures

Should there be a small section describing Hindley-Milner type signatures? I am just recently getting into the world of functional programming and know that at first I was confused about all these "strange comments" in the code.

Yes there must be, I am guessing you are reading Dr.Boolean's book ;) ?

Yeah, I just finished it a couple weeks ago. It was an interesting read, and definitely piqued my interest in functional programming.

:+1:

Problem is that there's not really a standard for the signatures in JS. The examples I've seen have been an adaptation from Haskell or F# or just off-the-cuff.

It's far, far too large for here, and still not finished, but I just created a document explaining how Ramda uses these.

@CrossEye wow!

There's a small section in the document on type signatures now. Can we resolve?
https://github.com/hemanth/functional-programming-jargon#type-signatures

Thanks @jethrolarson


Passing in2.test

Im closing #501 and opening this one with the new issues
To be able to pass in2.test the following statements must all raise an error (due to t1 is not defined).

The test looks really fine. Ill see if I can replicate the issue from the test.


Calculate ner - performance differences in LocText branches (develop, feature/speed_up_relation_pipeline)

While calculating ner performance on following branches, we found differences and they are in corresponding text file.
Case 1: develop
Case 2: feature/speed_up_relation_pipeline
The FALSE NEGATIVE (fn) and FALSE POSITIVE (fp) information details are in the attachment.
fp_fn_develop.txt
fp_fn_feature_speed_up_relation_pipeline.txt
Case 1
LocText: develop
nalaf: feature/Keep_Exploration
Case 2
LocText: feature/speed_up_relation_pipeline
nalaf: feature/Keep_Exploration

Thanks @MadhukarSP

@MadhukarSP FYI it is to be expected (or rather I'm glad of the fact) that the latest branch has improved performance because I was tinkering the code a bit precisely to improve the localization results.
Good finding. This is very important stuff.
Please proceed with the subtask 2 of #37

@MadhukarSP I don't understand the cases you put -- you repeat cases? (case 1, case 2, case 1, ...)
Please put the exact commit hashes of git for nalaf and LocText for all the cases

Done


iOS compile fails (xcode) with undefined symbols for draco::Encoder

I'm having issues building for iOS:
error: undefined symbol: draco::Encoder::EncodeMeshToBuffer(draco::Mesh const&, draco::EncoderBuffer*)
error: undefined symbol: draco::Encoder::SetEncodingMethod(int)
error: undefined symbol: draco::Encoder::EncodePointCloudToBuffer(draco::PointCloud const&, draco::EncoderBuffer*)
error: undefined symbol: draco::Encoder::SetAttributeQuantization(draco::GeometryAttribute::Type, int)
error: undefined symbol: draco::Encoder::SetSpeedOptions(int, int)
error: undefined symbol: draco::Encoder::Encoder()

The project also includes the decoder which does not seems to have any such issues.
It also seems suspicious that the  decoder is 10mb but the encoder is 256kb?
(Note: this is after applying the fix here to ensure the library is included
Perhaps the binary isn't correct?

I am having the same error for Wasm and I think you are right, the size is too small.
After adding some source files to the draco_unity_enc_plugin target in the CMakeLists.txt file, it started to work.
I am pretty sure that is not the better solution, but it is a workaround. I hope @atteneder fixes it in a better way.
You can see the workaround in this commit: https://github.com/EvergineTeam/draco/commit/adc8866ce142e616412fd6111b6794df031bd6d0

+1 for the Wasm build failing to link. Multiple errors for multiple symbols like:
Library\Bee\artifacts\WebGL\build\debug_WebGL_wasm\build.js: undefined symbol: _ZN5draco7Encoder15SetSpeedOptionsEii (referenced by top-level compiled C/C++ code)
UnityEditor.GenericMenu:CatchMenu (object,string[],int)

@gabrielgt any chance you can share the prebuilt wasm .a files - would be greatly appreciated! Having trouble to build it from sources on my end

@gabrielgt managed to get Github Actions running by forking and triggering the action myself. It works, thank you!

K here is the thing, I wanna use the encoder in a swift project. So I tried adding the libdracoenc.a and also found it weird its only 200kb. Yeah it wont compile. THanks @ZelimDamian and @gabrielgt I am learning to use github actions now to build it. I need to get the ios binary

Heads-up: The library build was to blame. A fix for version 5 is in the making.

Please transition to Draco for Unity, the successor of this repository/package. That should fix this problem.


Contradictory guidance regarding presenter role assignment caveat

The following guidance is contradictory. It says the create method will be accepted but the role isn't applied, then it immediately says the create method will be rejected with a 400.
Assigning the presenter or coorganizer role to users who are not registered in Azure Active Directory is not currently supported. Such requests will be accepted by the [create onlineMeeting](https://docs.microsoft.com/en-us/graph/api/application-post-onlinemeetings.md) method, but the role will not be applied when the participant joins the online meeting. The [create onlineMeeting](https://docs.microsoft.com/en-us/graph/api/application-post-onlinemeetings.md) method will reject the request and return a 400 Bad Request error.

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

ID: 4ab98f77-bf6f-4ce6-c189-dec2444a1bac
Version Independent ID: ec5464a8-4def-9074-6e50-0b737b41b631
Content: Known issues with Microsoft Graph - Microsoft Graph
Content Source: concepts/known-issues.md
Product: non-product-specific
Technology: microsoft-graph
GitHub Login: @MSGraphDocsvTeam
Microsoft Alias: MSGraphDocsVteam

Closing as the known issue was resolved. Thanks.


Sporadic crashes when installing/removing/updating packages

https://openrepos.net/comment/23760#comment-23760

BTW, I have not experienced this issue anymore, lately (maybe since Storeman 0.0.24 or so).
Although I am performing all actions purely sequentially (i.e. doing nothing while the repos are refreshed, doing nothing else while an application is installing etc.), older Storeman versions used to crash regularly for me when installing or removing apps.
Still I always found the corresponding app to be properly installed (or uninstalled) after such a crash.

Seems to be fixed

Ack, as I continue not to experience "Crashes while installing or uninstalling software", even though I started using Storeman doing things in parallel (Refreshing repos, installing software, Reading / writing comments, etc.) with v0.0.26.
It is doing all that nicely: Thanks.


Can't launch on Ubuntu 18.10 : Segmentation fault (core dumped)

Hello! I just installed the .deb and I tried to run it.

System info :
OS: Ubuntu 18.10 x86_64
Kernel: 4.18.0-10-generic
Uptime: 4 hours, 11 mins
Packages: 2076 (dpkg), 41 (snap)
Shell: bash 4.4.19
Resolution: 1920x1080
DE: GNOME 3.30.1
WM: GNOME Shell
WM Theme: Adwaita
Theme: Adwaita-dark [GTK2/3]
Icons: Yaru [GTK2/3]
Terminal: gnome-terminal
CPU: Intel i5-3570K (4) @ 4.100GHz
GPU: NVIDIA GeForce GTX 660 Ti
Memory: 5184MiB / 7921MiB

I'll close this as it is unrelated to the newer version we're working on. Thanks for checking @skomaromi!


Raspbian not completely booting after pishrink

Hi,
i created a new imagefile from raspbian (all updates installed) with rpi-clone and tested it. Works.
Then I tried to shrink it with PiShrink (file was then around 5G) wrote this to the SD.
If I now try to boot with this SD-Card I see the 4 Raspberries, then the splash screen and then no graphical UI.
I can also ssh to the Raspberry and see that e.g. the lightdm process is running but I do not get the normal UI via HDMI and also not via xrdp.
Has somebody an idea what happens there? What can I do to change that behavior?
Thanks and Kind Regards,
Marco

Closing stale issue, feel free to re-open with more details

Hi, I've the same problem.
Raspbian 12 desktop 32 bits.
No GUI, no access to desktop on the screen.
Only an underscore blinking at the top left corner of the screen.
I can access to the Rpi through ssh.
The config.txt is exactly the same.
Any Idea ?


PowerShell-function (or micro-module containing a single function) to easily download symbols

Parametersets for either a specified version or a given app.json file. If neither is specified, start from current folder to find app.json.

Of the approved PowerShell verbs, Get appears to make the most sense, closely followed by Use. So:
Get-ALSymbols -Country ... -Version ... -Directory ...


get access to nuxt-i18n State from plain js

Hi, I try to get access to nuxt-i18n State from plain js file:
from Vue components it looks like:
this.$i18n.locale // state data

from plain js I can't access to namespaced nuxt-i18n data
Importing vuex only have access to mapState, mapGetters functions. How to get access to namespaced nuxt-i18n state?

This question is available on Nuxt community (#c379)

@rchl How can i do that, when i'm include nuxt-i18n as a module in nuxt.config?

I'm not sure what you want to do. Please describe your problem better.

@rchl
I put nuxt-i18n as a module inside the nuxt.config of my project,  wich means that it can be globally accessible (right?).
I know maybe have no much sense but I NEED to do that.
Wanna do something like this:
const createStore = () => {
    return new Vuex.Store({
      state: {
        services: [
          {
            id: 2,
            imageLink: '/img/services/desarrollo_web_sitios',
            title:  $t('Langkey'),
          }
       ]
    }
  })
}`

You probably can't do it this way.
You would need to commit that string later, for example from nuxtServerInit or a nuxt plugin.


Add Floor Selector web component

Incomplete features:

The '1px overlay'
The animation could be improved

A readme file and a floor-selector.json file is missing.
The readme file will be auto-generated when running the project, and the json file should be manually created.
Some of the content of the readme file should also be auto-generated, but we need to write thorough documentation for each prop available on the component. See other components for inspiration.

@ammapspeople fixed added ✅

There's a short scrollbar glitch when opening the floor selector. Can we prevent that?
https://github.com/MapsPeople/web-ui/assets/50314165/9dee29b7-eab2-491d-b8f0-0e9d925b7130


StableDiffusionPipelineExplainer enable_attention_slicing()

Version 0.3.0 of the 🤗 Difusers introduces enable_attention_slicing, and I wonder if there's a way to implement this in the explainer. Below is the code that I used and it ran out of CUDA memory:
# Import pipeline
import torch
from diffusers import StableDiffusionPipeline

torch_device = "cuda" if torch.cuda.is_available() else "cpu"

pipe = StableDiffusionPipeline.from_pretrained(
    "CompVis/stable-diffusion-v1-4",
    use_auth_token = True,
    revision = "fp16" if torch_device != "cpu" else None,
    torch_dtype = torch.float16 if torch_device != "cpu" else None)

pipe.to(torch_device)

pipe.enable_attention_slicing() # attention optimization for less memory usage

# Pass pipeline to the explainer class

from diffusers_interpret import StableDiffusionPipelineExplainer

explainer = StableDiffusionPipelineExplainer(pipe)

prompt = "photograph, piggy, corn salad"

with torch.autocast(torch_device):
    output = explainer(prompt,
                       guidance_scale=7.5,
                       num_inference_steps=17)

output.image

Attention slicing is fully compatible with the explainer :)
However it is normal that you run out of GPU memory, because the attributions calculation is pretty expensive.
I recommend you add the arguments I used in this notebook.
Enabling gradient_checkpointing helps.
explainer = StableDiffusionPipelineExplainer(
    pipe,

    # We pass `True` in here to be able to have a higher `n_last_diffusion_steps_to_consider_for_attributions` in the cell below
    gradient_checkpointing=True
)

Also, reducing n_last_diffusion_steps_to_consider_for_attributions, height and width decrease GPU usage.
prompt = "A cute corgi with the Eiffel Tower in the background"

generator = torch.Generator(device).manual_seed(2023)
with torch.autocast('cuda') if device == 'cuda' else nullcontext():
    output = explainer(
        prompt,
        num_inference_steps=50,
        generator=generator,
        height=448,
        width=448,

        # for this model, the GPU VRAM usage will raise drastically if we increase this argument. feel free to experiment with it
        # if you are not interested in checking the token attributions, you can pass 0 in here
        n_last_diffusion_steps_to_consider_for_attributions=5
    )

Thank you for your reply ☺
Once I've passed the argument gradient_checkpointing = True,  all 51 inference steps went through without memory constraint. Not surprisingly, CUDA ran out of memory soon after the Calculating token attributions... prompt apppeared.
I've then passed the argument n_last_diffusion_steps_to_consider_for_attributions = 0, but this appeared from explainer.py line 194:

NotImplementedError: Only `attribution_method='grad_x_input'` is implemented for now

On the other hand, passing the argument to 1 or None yielded out of CUDA memory after all the inference steps.

I've then passed the argument n_last_diffusion_steps_to_consider_for_attributions = 0, but this appeared from explainer.py line 194:

NotImplementedError: Only attribution_method='grad_x_input' is implemented for now

Yes, that's my bad... I added a new patch version to fix that.

On the other hand, passing the argument to 1 or None yielded out of CUDA memory after all the inference steps.
To clarify, n_last_diffusion_steps_to_consider_for_attributions=None will calculate attributions for the entire diffusion process while n_last_diffusion_steps_to_consider_for_attributions=0 will not compute attributions at all. I need to write documentation on this!

If with n_last_diffusion_steps_to_consider_for_attributions=1 you are still running out of memory (and using gradient checkpointing and attention slicing), that means that your GPU is just not big enough to compute the gradients for an image of (512, 512) 😞
I suggest using cpu instead or reducing the image size. On Colab it works with a (448, 448).
This stable diffusion model is still pretty big, I'm still looking for more ways to require less GPU VRAM.

Yes, that's my bad... I added a new patch version to fix that.

Thank you very much, and this feature is working as intended!


why not using domains?

Why is async listener not using domains? Using domains, all the context passing just works. The wrappers are just needed to tap into the different events, but even if one wrapper is missing, other wrappers down the line will continue to function.
What I mean is to replace the state that is stored in glue.js with a domain that is created for code that enters an async listener scope.

Domains are deprecated afaik.

Yes, they are deprecated. They are also made of pain and malice. I don't really want to get into a big, long rant about them. I'll just say they are not a good API.

I am confused. Looking up the holy google search about nodejs and domains you only get documents about how cool those are and why you should use them see here. Only when looking for node.js domain deprecation we find discussions in the node forums that domains are deprecated. Even in the node APIs domains are not marked as deprecated, rather as an unstable API.
If not using domains, that only leaves async-listener as an option to track an async flow and attach stuff to it - like long stack traces, "request scope data", profiling metrics, request IO metrics, etc. And async-listener itself does scary things with native promises.
Are there other options? Other ways to tap into the event loop?

Keep in mind that node 0.12 is really, really old and soon to be replaced by io.js. Have a look at the io.js domain docs to see the deprecation warning.
I'd agree that having to resort to userland monkey-patching is rather sad, and is a big part of why I helped start the tracing working group. But, unfortunately, there is no other adequate option currently. The async-listener module is intended as a polyfill for the AsyncListener API that used to be in node, backing domains, but it ended up getting ripped out and is currently being replaced gradually by async_wrap, though it is not ready yet. The module needs to have a relatively wide version support, so brand new APIs can only be used with an appropriate fallback, which is what the ugly bits of this module are for.
Also of note is that promises are managed by the microtask queue in V8, which domains can't interact with and therefore can cause some very unexpected behaviour.
If and when some better, more stable API for tracking stack movement comes into existence, we'll certainly be looking into updating this module to use that instead. Until then, it's probably best to continue using the gross monkey-patching and avoid domains.
 I'm all too familiar with what lurks beneath these seemingly innocuous APIs.


Avatars

Look for a new avatar package and use that for the commentsBox.

utilities:avatar
Which is still the same giturl as bengott:avatar (https://github.com/bengott/meteor-avatar)
"I've forked @bengott's Avatar package to take over maintenance until he has time to come back to it. -Sacha"
So basically renaming the used package should "solve" the issue, will just allow to use a more updated version of the same bengott package.

Thanks for the information, I updated the package and released a new verison 0.2.9


No styling for hr makes them invisible

hr tags aren't visible with the recent theme updates.
Adding something like this to the theme css has been my workaround, but would be great to have a fix upstream.
.markdown-preview-view hr {
    border: none;
    border-top: 1px solid var(--text-faint);
}

.markdown-source-view hr {
    border: none;
    border-top: 1px solid var(--text-faint);
}

If you want you can make a pr. Or else I'll do so.

@Mangeshrex Hi. Was the intention to merge the PR as well, or was this issue closed for a separate reason?

the pr fixed this issue right ?

the pr fixed this issue right ?

The PR needs to be merged before the fix is available to others. I don't have permission to do that, you need to merge it.

i will merge the pr, if there's any further issue, feel free to reopen this issue.

Thanks 🙏


Analyzer fatal crash

I have a project where the analyzer completely fails, this is what I get from the log file

Webstorm 11.0.3
Windows 10
SDK 1.15
Angular 2 beta 14
(unable to provide sources)

AnalysisException: Cannot compute RESOLVED_UNIT for D:\dev\ext\intersentia\frontend\dart\taurus_search\web\main.dart in D:\dev\ext\intersentia\frontend\dart\taurus_search\web\main.dart
Caused by Unexpected exception while performing InferInstanceMembersInUnitTask for source C:\Users\frank\AppData\Roaming\Pub\Cache\hosted\pub.dartlang.org\async-1.10.0\lib\src\typed\stream.dart
#0      AnalysisTask._safelyPerform (package:analyzer/task/model.dart:339)
#1      AnalysisTask.perform (package:analyzer/task/model.dart:229)
#2      AnalysisDriver.performWorkItem (package:analyzer/src/task/driver.dart:274)
#3      AnalysisDriver.performAnalysisTask (package:analyzer/src/task/driver.dart:249)
#4      AnalysisContextImpl.performAnalysisTask.<anonymous closure> (package:analyzer/src/context/context.dart:1132)
#5      _PerformanceTagImpl.makeCurrentWhile (package:analyzer/src/generated/utilities_general.dart:212)
#6      AnalysisContextImpl.performAnalysisTask (package:analyzer/src/context/context.dart:1130)
#7      PerformAnalysisOperation.perform (package:analysis_server/src/operation/operation_analysis.dart:371)
#8      AnalysisServer.performOperation (package:analysis_server/src/analysis_server.dart:864)
#9      Future.Future.delayed.<anonymous closure> (dart:async/future.dart:228)
#10     _rootRun (dart:async/zone.dart:891)
#11     _CustomZone.run (dart:async/zone.dart:790)
#12     _CustomZone.runGuarded (dart:async/zone.dart:696)
#13     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:721)
#14     _rootRun (dart:async/zone.dart:895)
#15     _CustomZone.run (dart:async/zone.dart:790)
#16     _CustomZone.runGuarded (dart:async/zone.dart:696)
#17     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:721)
#18     Timer._createTimer.<anonymous closure> (dart:async-patch/timer_patch.dart:16)
#19     _Timer._runTimers (dart:isolate-patch/timer_impl.dart:385)
#20     _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:414)
#21     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:148)

Caused by IllegalArgumentException: argumentTypes.length (1) != typeFormals.length (0) null
#0      FunctionTypeImpl.instantiate (package:analyzer/src/dart/element/type.dart:690)
#1      InstanceMemberInferrer._inferExecutable (package:analyzer/src/task/strong_mode.dart:291)
#2      List.forEach (dart:core-patch/growable_array.dart:254)
#3      InstanceMemberInferrer._inferClass (package:analyzer/src/task/strong_mode.dart:235)
#4      InstanceMemberInferrer.inferCompilationUnit.<anonymous closure> (package:analyzer/src/task/strong_mode.dart:98)
#5      List.forEach (dart:core-patch/growable_array.dart:254)
#6      InstanceMemberInferrer.inferCompilationUnit (package:analyzer/src/task/strong_mode.dart:96)
#7      InferInstanceMembersInUnitTask.internalPerform (package:analyzer/src/task/dart.dart:2850)
#8      AnalysisTask._safelyPerform (package:analyzer/task/model.dart:329)
#9      AnalysisTask.perform (package:analyzer/task/model.dart:229)
#10     AnalysisDriver.performWorkItem (package:analyzer/src/task/driver.dart:274)
#11     AnalysisDriver.performAnalysisTask (package:analyzer/src/task/driver.dart:249)
#12     AnalysisContextImpl.performAnalysisTask.<anonymous closure> (package:analyzer/src/context/context.dart:1132)
#13     _PerformanceTagImpl.makeCurrentWhile (package:analyzer/src/generated/utilities_general.dart:212)
#14     AnalysisContextImpl.performAnalysisTask (package:analyzer/src/context/context.dart:1130)
#15     PerformAnalysisOperation.perform (package:analysis_server/src/operation/operation_analysis.dart:371)
#16     AnalysisServer.performOperation (package:analysis_server/src/analysis_server.dart:864)
#17     Future.Future.delayed.<anonymous closure> (dart:async/future.dart:228)
#18     _rootRun (dart:async/zone.dart:891)
#19     _CustomZone.run (dart:async/zone.dart:790)
#20     _CustomZone.runGuarded (dart:async/zone.dart:696)
#21     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:721)
#22     _rootRun (dart:async/zone.dart:895)
#23     _CustomZone.run (dart:async/zone.dart:790)
#24     _CustomZone.runGuarded (dart:async/zone.dart:696)
#25     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:721)
#26     Timer._createTimer.<anonymous closure> (dart:async-patch/timer_patch.dart:16)
#27     _Timer._runTimers (dart:isolate-patch/timer_impl.dart:385)
#28     _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:414)
#29     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:148)

#0      AnalysisContextImpl.computeResult (package:analyzer/src/context/context.dart:668)
#1      AnalysisContextImpl.resolveCompilationUnit2 (package:analyzer/src/context/context.dart:1234)
#2      AnalysisServer.getResolvedCompilationUnits.<anonymous closure> (package:analysis_server/src/analysis_server.dart:723)
#3      runWithWorkingCacheSize (package:analysis_server/src/operation/operation_analysis.dart:35)
#4      AnalysisServer.getResolvedCompilationUnits (package:analysis_server/src/analysis_server.dart:718)
#5      AnalysisDomainHandler.getNavigation.<anonymous closure> (package:analysis_server/src/domain_analysis.dart:140)
#6      _rootRunUnary (dart:async/zone.dart:902)
#7      _CustomZone.runUnary (dart:async/zone.dart:798)
#8      _Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:551)
#9      _Future._propagateToListeners (dart:async/future_impl.dart:637)
#10     _Future._propagateToListeners (dart:async/future_impl.dart:515)
#11     _Future._completeWithValue (dart:async/future_impl.dart:424)
#12     _Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:479)
#13     _rootRun (dart:async/zone.dart:895)
#14     _CustomZone.run (dart:async/zone.dart:790)
#15     _CustomZone.runGuarded (dart:async/zone.dart:696)
#16     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:721)
#17     _microtaskLoop (dart:async/schedule_microtask.dart:41)
#18     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
#19     _Timer._runTimers (dart:isolate-patch/timer_impl.dart:394)
#20     _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:414)
#21     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:148)

I've now updated my pubspec file to target async v1.9.0 and everything works again,
seems like async v1.10.0 is causing trouble
@nex3

I wasn't able to reproduce this with a small example. Was strong mode enabled?

Yes that is enabled, I've tried without strong mode and it still failed

I've just been able to reproduce this in a mini-project:
import 'package:async/src/typed/stream.dart';

void main() {
  TypeSafeStream stream;
}

It may be strong mode after all? I did turn that off, but maybe the analyzer just didn't kick in again?
This is my full .analysis.options file:
analyzer:
 strong-mode: true
 exclude:
     - web/orm_init.dart
linter:
  rules:
    - always_declare_return_types
    - annotate_overrides
    - avoid_empty_else
    - avoid_init_to_null
    - avoid_return_types_on_setters
    #- camel_case_types
    #- constant_identifier_names
    - empty_constructor_bodies
    - hash_and_equals
    - library_names
    - library_prefixes
    #- non_constant_identifier_names
    - package_api_docs
    - package_names
    - package_prefixed_library_names
    - prefer_is_not_empty
    - slash_for_doc_comments
    - sort_unnamed_constructors_first
    - super_goes_last
    - type_annotate_public_apis
    - type_init_formals
    - unnecessary_brace_in_string_interp
    - unnecessary_getters_setters

Retried in the mini-example, it is only occurring with strong-mode true

I'm not sure why, but I'm still not able to reproduce the problem. I created an empty package, duplicated your .analysis_options file (minus the exclusion, because that directory doesn't exist for me), and pasted the text into test.dart. I verified that strong mode is enabled and that the lints are running. Here's my pubspec.yaml, in case it might be different in some interesting way:
name: test_pkg
version: 0.0.1
description: A test package.
dependencies:
  async: 1.10.0

I've pulled in the async lib from GitHub and loaded it into Webstorm,
same issue so I started digging =>
in the troubled class I started removing methods one by one until the analyzer was happy again,
turns out this one (for example, there's more like it) gave me the problem:
Stream/*<S>*/ expand/*<S>*/(Iterable/*<S>*/ convert(T value)) =>
      _stream.expand(_validateType(convert));

I proceeded to strip all Type comments from the file and everything works fine again.
Closer inspection,
The file uses the commented type , yet S is not a valid type, only T is defined when you look at the class signature:
class TypeSafeStream<T> implements Stream<T>
finally, writing this:
Stream/*<T>*/ expand(Iterable/*<T>*/ convert(T value)) =>
      _stream.expand(_validateType(convert));

is making the analyzer happy for me, yet adding the extra type after expand makes it crash again:
Stream/*<T>*/ expand/*<T>*/(Iterable/*<T>*/ convert(T value)) =>
      _stream.expand(_validateType(convert));

I can confirm this issue. Using dartanalyzer 1.15.0 and async 1.10.0 = analyzer crash.
Using dartanalyzer 1.15.0 and async 1.9.0 works fine.
Also worth noting is that async 1.10.0 does NOT crash dartanalyzer version 1.14.2. It seems to be specific to dartanalyzer 1.15.0 and async 1.10.0

Dartanalyzer 1.16.0 and async 1.10.0 works fine. The bug seems to have been fixed in 1.16.0.

It is indeed fixed on 1.16, unfortunately there's also a windows webstorm bug that causes dartium to never load.
The async lib for example was updated and released prior to the 1.16 launch, or this webstorm fix, in short my development environment is in limbo until I can update properly to 1.16.

@frankpepermans sounds like #26260. The issue in WebStorm only appeared because of this bug in pub. This is already workign for me in bleeding edge (Linux).
Can you load the app in Dartium if you load it directly from pub serve without the WebStorm proxy?

Haven't tried yet, sticking with 1.15 for the time being. The 1.16 issue is understandable, and it won't take long to fix I assume, however having updated pub dependecies that cause bugs with previous sdk versions is not.
I'll test with the 1.16 release later on, again I can work around most issues if needed, but I've just sold Dart internally at a client and it's not pleasant to explain why things are breaking the whole time :)

OK, as the analyzer problem is fixed, I'm closing the issue.


mj-spacer doesn't work

Hello @ramilS
Can you provide more information ? Client, MJML to reproduce, ...
Thanks

sorry. U can close this issue. It didn't work in 'mj-text', but outside of this component it's working

Got the same issue.
Inside my browser the spacer is respected - but inside the mail its not.
Using the latest version of MJML 3.3.3
Problem occurs in all Clients
MJML:
<mj-section padding="0">
	<mj-column>
		<mj-spacer height="40px" />
	</mj-column>
</mj-section>

Output:

```

Well it works fine here, how did you send your email ?

I'm using Cleverreach as a Mailingprovider.
But it's also not working within the Litmus Builder

As you can see : https://litmus.com/checklist/emails/public/2198551 it works fine for https://mjml.io/try-it-live/BynuJH9o-

@Skinwalker can you make sure you don't have an option like Inline CSS toggled?

@ngarnier Inline CSS Option is off

works now - haven't changed anything ...
even inside litmus editor ...
¯_(ツ)_/¯


Automatic colour scheme

Hey @larsgw, thanks again for writing censordle!
Finally found time to add this since it was bothering me. I (especially) play on mobile, and often outdoors or on the train, and the dark theme is a bit of a contrast struggle for me in heavy daylight.
This PR is split into two commits: one replacing the colours used with CSS variables (so you can be sure they're all the same colours), the second commit adding a 'light' theme, and then using the automatic toggle for dark theme based on the user's system/browser preferences, which is quite well supported.
Image with very minor spoilers for 2023-07-01 (e.g. a country name's prevalence)
Please ignore the yellow, that is from my OS.

Thank you very much for the contributions! I just got back from a trip, I'll take a look at these PRs in the coming days.


msftncsi.com is needed for windows phone 10

please remove msftncsi.com from hosts file. This domain is accessed to check if there is internet connection on windows phone 10.

Please take this up with Dan Pollock at someonewhocares.org.


ToC and preview updates for 1.5

ToC and preview updates for 1.5

We don't need to wait for OSS CI tests.


add more permissions for metering-report-server

fix "Failed to watch" errors in metering-report-server pod

/lgtm


Optimize JS code with V8 tricks

Continuing from https://github.com/jerive/bipf-napi/issues/1#issuecomment-985868777
@jerive I noticed that in test/perf.js, sometimes seekKey(buffer, start, target) is called with buffer = 0 and that's what causes a deopt. We could do two things: (1) check why is buffer = 0 being passed to this function in the perf.js, and not pass that (invalid) arg, (2) put a if (Buffer.isBuffer(buffer)) check in the implementation, although this will likely impact performance a tiny bit.

at seekKey (/home/jerome/dev/bipf/index.js:235:11)
    at Array.eval (eval at createSeekPath (/home/jerome/dev/bipf/index.js:336:10), <anonymous>:6:11)
    at /home/jerome/dev/bipf/index.js:452:27
    at Object.<anonymous> (/home/jerome/dev/bipf/test/perf.js:166:3)


Google Analytics

Hello, please add support Google Analytics

@YurchukV
You can use Google Analytics as Swift Package via Firebase.
Here is the document for introduction in the Firebase SDK repository.
https://github.com/firebase/firebase-ios-sdk/blob/c0df01d5f0141dfe7d6d48efceb086219171a1cd/SwiftPackageManager.md
If you want to use AdMob and Analytics, you can setup each this repository and Firebase repository as Swift Package.


Implement Battle Attack Websockets

Implement demux web socket to execute the type of attack animation on the screen (neutral, fire, water etc)

This should comprise this:

When you battle I noticed it now gets a nice little reaction. I was thinking though is there a way to get the reaction to happen after it has been approved in scatter? As the reaction happens after I choose the attack but then scatter pops up, needs to be approved and then the damage is published so there's a good bit of a gap there.

Also being hold by #89 with new demux updates... (actually version 1.4.0)


Hints from @nchanged about the issue:

oh var i = 'function' == 'function' && require;
http://fuse-box.org/page/configuration#usejsnext

Repo with error reproduced: https://github.com/Martaver/fuse-box-examples/tree/master/examples/react-code-splitting
Steps to reproduce:

Clone repro repo and run it with node fuse (QuantumPlugin is enabled by default)
Open localhost:4444 - Observe error in debugger trying to load the page.

Error is:
vendor.js:15160 Uncaught ReferenceError: require is not defined
    at e (http://localhost:4444/static/vendor.js:15160:45)
    at http://localhost:4444/static/vendor.js:15164:6
    at i (http://localhost:4444/static/vendor.js:15122:26)
    at $fsx.f.(anonymous function) (http://localhost:4444/static/vendor.js:15138:2)
    at Object.$fsx.r (http://localhost:4444/static/api.js:73:9)
    at $fsx.f.(anonymous function) (eval at <anonymous> (http://localhost:4444/static/api.js:44:33), <anonymous>:19:37)
    at Object.$fsx.r (http://localhost:4444/static/api.js:73:9)
    at http://localhost:4444/static/api.js:45:39
    at XMLHttpRequest.request.onreadystatechange (http://localhost:4444/static/api.js:16:17)

Offending line in source is:
var i = 'function' == 'function' && require;

@Martaver it's quite difficult with this webpack build,
useJsNext fixes it, but it breaks something else in your case?! Could you point out what exactly does it break?

Oh now I see, react router module relies on a non-standard es6

Ok, there is a solution, not the prettiest but what can one do if people don't follow standards.
fuse.register("typescript-collections", {
    main: "dist/lib/index.js",
    homeDir: "node_modules/typescript-collections",
    instructions: " "
})

instructions is required, therefore it's an empty string with one symbol, don't mind that it will be fixed.

By default, that library points to umd.js which is package.json main property. And it is bundled with webpack
Toggling useJsNext reads other properties like js:next and module which in our case is pointing to
dist/lib/index.js (es6 module) It works just fine but doesn't really work with react-router heresy source code.  Register overrides a package. You can set a different entry point, as well as include some files which were not mentioned in require statements (like bundle HTML files and such)

I see... so really, is the problem that react-router is too behind the times, or that typescript-collections is too ahead of the times... :-/

Or both...
Either way, thanks mate, appreciate it!

I have the same issue with reactstrap-tether - https://www.npmjs.com/package/reactstrap-tether.
I fixed it by doing this hack in fuse config:
 alias: {
      "reactstrap-tether": ''
    }

I still get a does not provide a module error but the app is not blocked and everything is working.


Fix typos in Evaluator docstrings

This PR fixes two typos in the imports of the Evaluator examples.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Fonts for Filter and Link looks inappropriate of other elements

Fonts for Filter and Link looks inappropriate of other elements

this will be fixed as part of PR https://github.com/fabric8io/fabric8-planner/pull/1149

@mindreeper2420 thanks !

@naina-verma you should be able to see the corrected view now on the latest Master. I'll be adding future PRs to address some other differences as well.


Feature/expose min max

This is a (very rough) prototype of metric multiplexing, that would allow us to close #244.
I've implemented those "virtual metrics", such as you see on the screenshot:

Note that we're just exposing the metrics that were previously available from Cassandra, but were not exposed in any way (we were almost making a shortcut to mean and the rest of metrics were just hidden).
Please note that currently tests are not yet passing and branch is not very stable. I just wanted to chat about the idea with @pyr and @tehlers320 before I proceed with it further. If you have alternative syntax (or a different idea alltogether), I'm open for suggestions.

For now, at least tests are working. Might be still rough at the corners. Also, I'd still work to improve the code a bit.

This seems like a fine fine for now. ideally we could pass the agg= parameter from grafana, but that would require building a cyanite plugin in grafana, let's do that once we don't need graphite-api anymore.

Right. For that we would need to have more complete set of aggregate functions, right?

I'm quite happy with current PR state, so I'd merge it and move to index problem over the weekend.


Bubble not connected

I am experiencing a problem where the bubble is not connected to the bar as is shown in your animated gif.

I am using code from your example project.

The effect is enabled when you run on device only.
It is because the simulator uses CPU to render the effect which leads to dropped frames.
See isAnimationAllowed method


Issue 26749

Follow-up of #6825.

Updates test cases
Adjusts deprecation warning texts
Adds corner case addressed by #6825, providing a workaround for ticket 26749

As it's intended to be a temporary workaround for v1.10, I based the change on top of stable.1.10.x, but I can move it back to master if needed. I can also merge the two commits.

Right, flake8… beware, I amended my commit to add a few blank lines.
In case you hit a conflict, overwrite my changes I'll do them again.

buildbot, add to whitelist.

Yes, for future reference, please send the pull request against master and let the committer backport it. Since there aren't likely to be conflicts it doesn't matter too much. We can cherry-pick to merge it.

Alright, I need your input on the warning message and I'll improve the change.
=> Do you want the commits to be squashed? And perhaps rebased on master?

I'd add the semantics to the release notes. No strong opinion about the warning message, I guess. "instead" implies removing use_for_related_fields to me.
Squashing is fine. Don't need to rebase on master since that would require opening a new PR.

Squashed, and added a note for the behavior into the release notes.
Now it's described there, I feel comfortable with reverting the warning message, and I did so.

merged in f4afb85d7e900123fa8f88110adc011ab184e153, thanks!


A mention of Hacktoberfest?

I just had a thought that a mention of Hacktoberfest, https://hacktoberfest.digitalocean.com/ , might be useful?
It's a good way of getting to learn how to use Git(hub) and a good way of getting into supporting Open Source projects.
Also, who can't find use for another (free) t-shirt and some more (again free) laptop stickers? ;)

Yeah, that is a cool idea

That only lasts this month right?

Yeah - it lasts for one month. Register, submit five PR's and one the month is up you get a t-shirt and some stickers. A good way of 'bribing' people to look at projects and give assistance.
Some projects have done quite well out of tagging them with hacktoberfest too.

I wonder if I can add this book to that list :)


Block theses types of ads

Could you get this to block ads where it opens new taps if I click somewhere on a website as it opens new virus links. Here is an example Website.  If I click anywhere on website is opens new website by itself. Could you get JavaScript to run evey 5 secounds
https://bizzstreams2u.online/

See https://github.com/MarcellPerger1/adblock-bookmarklet/issues/46#issuecomment-2176959800

Still opens new taps and doesn't blocks


Update quit.vim

Description
Please explain the changes you made here.
Checklist

[x] I have read
CONTRIBUTING
guidelines.

CHANGELOG:

[ ] Updated
[ ] I will update it after this PR has been discussed
[ ] No need to update

KEYBINDINGS:

[x] Updated
[ ] I will update it after this PR has been discussed
[ ] No need to update

PLUGINS:

[ ] Updated
[ ] I will update it after this PR has been discussed
[x] No need to update

Great! What do you think about using this action as spc q r instead of spc q R and moving InvalidateCache to spc q R
i.e.
let g:WhichKeyDesc_Quit_InvalidateCache = "<leader>qR invalidate-cache"
nnoremap <leader>qR    :action InvalidateCaches<CR>
vnoremap <leader>qR    <Esc>:action InvalidateCaches<CR>
let g:WhichKeyDesc_Quit_Restart = "<leader>qr restart"
nnoremap <leader>qr    :action RestartIde<CR>
vnoremap <leader>qr    <Esc>:action RestartIde<CR>

Please Take A Look

Awesome! can you update CHANGELOG and KEYBINDINGS, too?
In changelog I would say that now spc q r just restarts the IDE without invalidating the cache, too.
While in keybindings I would change spc q R to Invalidate cache.
What do you think? Tell me if you have some doubts. Thanks.

Also, can you rename the PR to something more meaningful? Because that will be the commit message.

That's great, can you please review again?

Thank you so much!


Allow specifying tar URL

Currently, the script assumes the end-user wants homebrew to download the tarball of the repo at the latest version. My CI pipeline already builds binaries for all major OS's and attaches them to a Github release. It would be much better to have homebrew download the compiled binary in my case and then just run a bin install command.

This is probably something we can incorporate here. Can you provide a link to one of your projects where you'd like to do this so I can see it in action?
To clarify, do you just have a single binary that you'd want to install, is it standalone or in a zip or tarball attached to the release?

You can see an example of the release workflow here: https://github.com/jmgilman/vaultssh/blob/master/.github/workflows/release.yml
That produces a release like this: https://github.com/jmgilman/vaultssh/releases/tag/v0.1.0
If the goal is to follow after goreleaser, I actually have a Go version of this binary that I've used goreleaser with and it produces the below formula:
# This file was generated by GoReleaser. DO NOT EDIT.
class Vssh < Formula
  desc "A small CLI wrapper for authenticating with SSH keys from Hashicorp Vault"
  homepage "https://github.com/jmgilman/vssh"
  version "0.1.2"
  bottle :unneeded

  if OS.mac?
    url "https://github.com/jmgilman/vssh/releases/download/v0.1.2/vssh_0.1.2_Darwin_x86_64.tar.gz"
    sha256 "07de706b33a2b9fc776bcf4c549e4a7e61acc493202125aa2141808f17ad915a"
  elsif OS.linux?
    if Hardware::CPU.intel?
      url "https://github.com/jmgilman/vssh/releases/download/v0.1.2/vssh_0.1.2_Linux_x86_64.tar.gz"
      sha256 "e6e77895da5b87debef8231463f65b490127ea815f9b6fc67d2ff155830d8197"
    end
  end

  def install
    bin.install "vssh"
  end
end

Notice how it differentiates the architecture and provides hardlinks to the different artifacts and then just uses bin.install to avoid building on the end user's machine. In my case, Rust compiling can be pretty intensive and takes upwards of five minutes on my Macbook Pro.

I see, so you're building your own tarballs?
So really, there's two requests here: 1) to support platform specific install targets and 2) to support a user provided tar url from the latest release (so that you could pass it into each install target)?

Potentially, yes. I suppose it primarily depends on the targeted use case of the action. With the default behavior of downloading the tarball of the repository is the underlying assumption that most users of the action will be installing shell scripts or files from other scripted languages? As far as I know, it's unusual for a Homebrew package to default to compiling on a user's machine - usually, the default behavior is downloading a precompiled binary and then an alternative method of compiling from source is also offered.
So, the real question here is how does this action intend on supporting compiled binaries?

At the moment, I suppose the project does assume that there are ready to ship assets residing in the repo already (this has worked for my initial use case of simple shell scripts that don't really need any build process); however, I suppose that this is not ideal for actual binaries as the only option to use this action with the current behavior would be to keep copies of your binaries to distribute in the git repo which isn't ideal for various reasons.
With that being said, I'm open to keeping what I just mentioned as the fallback or default behavior with the ability of the user to overwrite this behavior. Do you have a vision for how you'd want to be using this action assuming it had this capability? Meaning, how best would you define which tarball to pull from in the workflow config? Would you have your release tarball always be named the same across various releases and versions and we could just go to the most recent release to grab the tarball and the user would provide the name of the tarball?

The way I'm currently solving this is with templates. A workflow like this in the source repository is responsible for building the formula. The last step dispatches to this workflow which creates a PR with the compiled template.
Not ideal really, but it works in the meantime. As for a solution using what exists here - it's not unreasonable to assume a fairly static naming structure for the tarballs. The only thing that would change in the download URL would be the release version. The hardest part is building a working formula that can support more than one platform (i.e. Linux, Mac, M1 Mac). The go-releaser package manages it but I haven't looked into how they are doing it.

Ah gotcha, thanks for the added context! I'm a bit short on time at the moment to look into this in-depth. Feel free to continue adding thoughts here or take a crack at a PR that would solve this. I'll circle back around to this in the future and take another look.

I've circled back to this and done a bit of research on how GoReleaser does this. Basically they allow your to specify a "pattern" or "template" URL where it will inject the correct values based on the platform/OS etc when building the formula file. I'm doing a bit of preliminary work surrounding the checksum logic that will make introducing this new feature here easier. Once that's complete I'll work on a way to allow users to specify a tar URL - still need to do a bit of research but I think I know how we'll go about this here.

Did some more digging into how this occurs for GoReleaser and am still a bit confused at how they seem to infer on what needs to be built.
My proposal is to add a new yaml section of which OSs to build for (macOS, Linux, and Windows only for now), the list specified will have a separate OS target in the generated formula, and the binary URL names will need to follow a pattern (something like containing the OS name in the URL, etc). This allows the user to specify which of the 3 they want to include while keeping the fallback of the default URL.
Do you only need to differentiate between OSs for now? I don't necessarily want to dive into all the different hardware combinations at this point if it can be avoided.

I'm getting pretty close I believe to having this implemented. I'm running after an issue with brew audit on the generated formula, then I'll need to end to end test this and document it and it should be good to go. The beauty is this should keep the current behavior while extending the options users have to specify which OS/Archs they have binaries for. It will need to follow a specified pattern, but I'll make sure it's documented in the README.

@jmgilman this has been released! Thanks for your patience and sorry it took so long (hopefully this can still benefit you). You can now pass various new booleans in the workflow yaml:
          target_darwin_amd64: true
          target_darwin_arm64: true
          target_linux_amd64: true
          target_linux_arm64: true

Doing so will have the workflow look for those tar archives on your most recent release. You'll need to follow the pattern detailed in the README for the URL; however, it should pretty much match the one you gave as an example above (you cannot at present specify a custom URL).
I'd highly encourage turning on debug mode and skipping the commit and maybe even running it locally (or running it dry on CI a couple times) prior to using the new matrix build targets to ensure the formula builds the way you are looking for. I did a bunch of end to end tests which seemed to get the right result along with a bunch of unit tests but would love any feedback you have in production. Best!


Output text from provisioning scripts

Description
It would be awesome if I could see the output of the provisioning scripts in the shell. I know I can look into the serial.log but having it directly visible when I start the box would be very helpful to me.

https://github.com/lima-vm/lima/issues/960


Fix merge map losing source content

Please provide a description of this PR:
Fix https://github.com/istio/istio/issues/42533

In response to a cherrypick label: new pull request created: #42539

In response to a cherrypick label: new pull request created: #42540


Remove template parameter from template README files

We have noticed that people think they have to provide the -t parameter every time they run azd up.  So, isntead of using -t in the README, we tell them to get the code, and then run azd up

Repoman Generation Results
Repoman pushed changes to remotes for the following projects:
Project: todo-csharp-cosmos-sql
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-csharp-cosmos-sql -b pr/235

View Changes | Compare Changes

Project: todo-csharp-mongo
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-csharp-mongo -b pr/235

View Changes | Compare Changes

Project: todo-csharp-sql
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-csharp-sql -b pr/235

View Changes | Compare Changes

Project: todo-nodejs-mongo-aca
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-aca -b pr/235

View Changes | Compare Changes

Project: todo-nodejs-mongo-swa-func
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-swa-func -b pr/235

View Changes | Compare Changes

Project: todo-nodejs-mongo
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo -b pr/235

View Changes | Compare Changes

Project: todo-python-mongo-aca
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-python-mongo-aca -b pr/235

View Changes | Compare Changes

Project: todo-python-mongo-swa-func
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-python-mongo-swa-func -b pr/235

View Changes | Compare Changes

Project: todo-python-mongo
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-python-mongo -b pr/235

View Changes | Compare Changes

Repoman Generation Results
Repoman pushed changes to remotes for the following projects:
Project: todo-csharp-cosmos-sql
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-csharp-cosmos-sql -b pr/235

View Changes | Compare Changes

Project: todo-csharp-mongo
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-csharp-mongo -b pr/235

View Changes | Compare Changes

Project: todo-csharp-sql
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-csharp-sql -b pr/235

View Changes | Compare Changes

Project: todo-nodejs-mongo-aca
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-aca -b pr/235

View Changes | Compare Changes

Project: todo-nodejs-mongo-swa-func
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-swa-func -b pr/235

View Changes | Compare Changes

Project: todo-nodejs-mongo
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo -b pr/235

View Changes | Compare Changes

Project: todo-python-mongo-aca
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-python-mongo-aca -b pr/235

View Changes | Compare Changes

Project: todo-python-mongo-swa-func
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-python-mongo-swa-func -b pr/235

View Changes | Compare Changes

Project: todo-python-mongo
Remote: azure-samples
Branch: pr/235
You can initialize this project with:
azd init -t Azure-Samples/todo-python-mongo -b pr/235

View Changes | Compare Changes


NVDA reports selection changes when moving by character or line in mark mode

Windows Terminal version
1.15.2003.0
Windows build number
22621.105
Other Software
NVDA 2022.2.1
Steps to reproduce

Open terminal
Press Ctrl+Shift+M
press left arrow

Expected Behavior
NVDA says: >
Actual Behavior
Nvda says: >, > selected, space unselected

In Narrator the behavior is even worse, mark mode with up/down arrow is basically unusable
The underlying issue is likely as follows. When moving through a normal text editor with an UIA implementation, that impl only fires selection events when selecting with shift+arrows, with the mouse or something else that involves text selection. On the contrary, Terminal seems to fire selection events for cursor movement as well. IMO mark mode in Terminal should behave similar to conhost in that it does not fire selection events for cursor movement.

CC @codeofdusk  @carlos-zamora

Pretty sure this is #13447?

Yes, it is. Sorry for the duplicate. I should change my searching heuristics probably.
I will use the area accessibility label in the future.


Update whatrustisit URL

I get a security warning when clicking this badge. Re-adding the www fixes the issue.

imo this should be filed as an issue in the badboy/whatrustisit repository, which appears to be the source for the website. It's a configuration issue with the site, after all.


Transfer base64 data to external files.

Transfer base64 data to external files. Reducing reading size of spec file. :)

Codecov Report

Merging #18 (c31312d) into master (acf01e0) will decrease coverage by 0.93%.
The diff coverage is 91.66%.

@@             Coverage Diff             @@
##            master      #18      +/-   ##
===========================================
- Coverage   100.00%   99.06%   -0.94%
===========================================
  Files            3        4       +1
  Lines          205      213       +8
===========================================
+ Hits           205      211       +6
- Misses           0        2       +2

Impacted Files
Coverage Δ

spec/support/file_fixture.rb
75.00% <75.00%> (ø)

spec/qrcode_pix_ruby_spec.rb
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Great insight! 💡
So much better and organized 📚


background-image doesn't work in *.module.less but work in *.module.css

使用CSS Modules时background-image可以在*.module.css中正常，*.module.less无法加载文件
Version
3.0.0-beta.11
Reproduction link
no
Steps to reproduce
file structure
-- assets
--    bg-login.svg
-- login.js
-- login.module.css
-- login.module.less

login.module.css
.login {
    background-image: url('./assets/bg-login.svg');
}

rename to login.module.less
What is expected?
show the background image
What is actually happening?
This dependency was not found:

* assets/bg-login.svg

To install it, you can run: npm install --save assets/bg-login.svg

Hi, thanks for submitting this issue! As our time is limited, we need you to put a reproduction link to a repository where we can find your project and diagnose what the problem is. Thank you for your understanding!

@Akryum I am sorry, please wait,  i will add  the codesandbox link

@Akryum
https://github.com/zlab/vue-cli-issues
App.vue
// work
<style module>

// doesn't work
<style module lang="less">

This seems to be a known gotcha of less-loader.
There's isn't anythign we can do abou that, really.


[BUG] Remove airgapped mode's usage of the deprecated containers names argument.

Describe the bug
Some air-gapped mode code still uses the deprecated container_names argument. This should be updated so that the images are fetched dynamically, without requiring manual image tag configuration. https://github.com/cncf/cnf-testsuite/blob/main/src/tasks/utils/cnf_manager_airgap.cr#L32
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

OS [e.g. Linux, iOS, Windows, Android]
Distro [e.g. Ubuntu]
Version [e.g. 18.04]
Architecture [e.g. x86, arm]
Browser [e.g. chrome, safari]

How will this be tested? aka Acceptance Criteria (optional)
(optional: unnecessary for things like spelling errors and such)
Once this issue is address how will the fix be verified?
Additional context
Add any other context about the problem here.

NOTE: you can enable higher logging level output via the command line or env var. to help with debugging
# cmd line
./cnf-testsuite -l debug test

# make sure to use -- if running from source
crystal src/cnf-testsuite.cr -- -l debug test

# env var
LOGLEVEL=DEBUG ./cnf-testsuite test

Also setting the verbose option for many tasks will add extra output to help with debugging
crystal src/cnf-testsuite.cr test_name verbose

Check usage documentation for more info about invoking commands and logging

Closing as CNTI Test Catalog group is discussing removing airgapped support


hot fixes

default card list order to order by title
add 'alpha release' alert

Not sure about the Husky issue. I'm up to date with yarn packages. Not getting any linting errors.

Ah! I'm am pushing commits using VS Code built-in git integration. I wonder if that is bypassing it. Lemme try command line push.

@jvoros When you push a commit, do you see the tests being ran? Every commit to this project, no matter what branch is active, should trigger a pre-commit hook which runs the tests.
If not, which version of git do you have installed?

Nah. Command line push worked too, with same leading zeroes.

Nah, meaning, no you don't see the tests being ran?
What version of git is installed on your system? Are you on a mac?

No tests being run...
git version 1.9.5 (Apple Git-50.3)
:confounded:
I spent an hour the other day trying to force my terminal to use updated git. I've got 2.something somewhere on my system.

@jvoros That's probably why. Apply git is extremely behind actual git...
The current version of git is 2.12.2.

Use homebrew and install the real git from the dupes tap

Codecov Report

Merging #158 into master will decrease coverage by 0.2%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #158      +/-   ##
==========================================
- Coverage   77.41%   77.21%   -0.21%
==========================================
  Files          15       15
  Lines         372      373       +1
  Branches      103      103
==========================================
  Hits          288      288
- Misses         84       85       +1

Impacted Files
Coverage Δ

app/App.tsx
0% <ø> (ø)
: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 a319cb9...c6ce7c6. Read the comment docs.


Trigger Update DB from selected branch

instead of always hardcoding main!
Related: COMPOSER-2227

Notes:

I was going to document something but then reallized what I wanted to do won't work anyway so closed the PR.


os: File.Sync() for Darwin should use the F_FULLFSYNC fcntl

What version of Go?
1.10 or tip
What operating system and processor architecture?
darwin, *
What is the matter?
According to this and other sites, fcntl(fd, F_FULLFSYNC) is necessary for proper fsync on MacOS (OS X): https://danluu.com/file-consistency/
Github search finds no uses of "F_FULLFSYNC" in the src tree.
If there is a rationale for the present implementation, it should be documented in File.Sync() with directions on how to invoke the fcntl variant.

Since this issue threatens data loss/corruption, please consider fixing it in 1.11.x and 1.10.x

Thank you for reporting this issue @networkimprov! It is triaged for 1.12 as 1.11 is scheduled to be released in just a few days. It has also been like this since forever. However we'll definitely consider it as an early candidate for Go1.12 when the tree opens up in the next few weeks. If you are interested in submitting a CL, please feel free, it'd be great to have your contribution in the Go project and community, otherwise we'll get it in for Go1.12.

I'm not proposing 1.11.0 as a target; rather 1.11.1 & 1.10.4 or the minor releases that appear after a fix lands on tip.
Do you have guidance on where fcntl should be called for Darwin File.Sync()?

The question is whether we should do it in syscall.Fsync or os.File.Fsync.  I guess I would lean slightly toward the former, but happy to hear comments.

I'm not proposing 1.11.0 as a target; rather 1.11.1 & 1.10.4 or the minor releases that appear after a fix lands on tip.

A backport I believe warrants something that has plagued previous versions or results for memory corruption, but I'll defer to others on whether this qualifies too -- in this case potential file corruption might qualify :)

The question is whether we should do it in syscall.Fsync or os.File.Fsync. I guess I would lean slightly toward the former, but happy to hear comments.

@ianlancetaylor I too was leaning towards it going in to syscall.Fsync since perhaps we can minimally make it

// As per /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/usr/include/sys/fcntl.h
const FULLFSYNC = 51
func Fsync(fd int) error {
     _, err := fcntl(fd, FULLFSYNC, 1)
    return err
}

so in full
+// As per /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/usr/include/sys/fcntl.h
+const FULLFSYNC = 51
+
+func Fsync(fd int) error {
+       _, err := fcntl(fd, FULLFSYNC, 0)
+       return err
+}
+
 // SockaddrDatalink implements the Sockaddr interface for AF_LINK type sockets.
 type SockaddrDatalink struct {
        Len    uint8
@@ -332,7 +340,6 @@ func Uname(uname *Utsname) error {
 //sys  Fstat(fd int, stat *Stat_t) (err error) = SYS_FSTAT64
 //sys  Fstatat(fd int, path string, stat *Stat_t, flags int) (err error) = SYS_FSTATAT64
 //sys  Fstatfs(fd int, stat *Statfs_t) (err error) = SYS_FSTATFS64
-//sys  Fsync(fd int) (err error)
 //sys  Ftruncate(fd int, length int64) (err error)
 //sys  Getdirentries(fd int, buf []byte, basep *uintptr) (n int, err error) = SYS_GETDIRENTRIES64
 //sys  Getdtablesize() (size int)

Also happy to hear what comments others have.

On the other hand, thinking about it further, most of the syscall functions simply implement that operation on the system, rather than trying to present a unified cross-system API.  So that suggests that maybe syscall.Fsync on MacOS should just implement the fsync system call, and that we should make the fcntl call in os.File.Sync, or, really, internal/poll/Fd.Fsync.  I'm not sure.

I'm not proposing 1.11.0 as a target; rather 1.11.1 & 1.10.4 ...

A backport I believe warrants something that has plagued previous versions or results for memory corruption, but I'll defer to others on whether this qualifies too -- in this case potential file corruption might qualify :)

Note that this can hurt end-users without the Go developer ever realizing it: User does xyz in app, OS crashes (or hw fails), user sees odd behavior in app after restart and restores from backup (losing today's work), user assumes problem was due to hw or os.

+const FULLFSYNC = 51

It's already defined in tree:
https://github.com/golang/go/search?q=f_fullfsync&unscoped_q=f_fullfsync
Agreed you should leave MacOS fsync available in case anyone needs it.

Cool, thanks for the discussion @networkimprov and @ianlancetaylor!

Surely. Have you decided where the fix should live?

@odeke-em the 1.12 tree is open; can we get this CL posted?

@networkimprov thank you for the ping and reminder! For sure, let's get the ball rolling. I am in the process of submitting a CL.

In regards to backporting this fix to Go1.11 and earlier, what do y'all think @ianlancetaylor @andybons?
Also perhaps we need to add this to Go1.12 release notes?

This is not a new problem.  I don't see a need to backport.

Roger that! The rationale that @networkimprov proposed, which I thought was reasonable was that because it is an underlying problem that has existed since Go1.0, it'd be nice to have it in the latest Go release since it can lead to disk memory corruption and affects many databases, folks that need flushes to permanent storage. However, as we've all noticed, no one had frantically reported this bug during previous Go cycles hence doesn't meet the bar for a backport.

This can hurt end-users without the Go developer ever realizing it:

user does xyz in app; OS crashes or hw fails
user sees odd app behavior after restart and restores from backup, losing this week's work
user assumes problem was due to hw or OS

I plan to release two apps near-future which rely on os.File.Sync() for crash protection, and MacOS is widely used by my audience.
Not Go-related, but my Git repo was corrupted last week due to a hw failure.

@ianlancetaylor could you consider cherry-picking this for 1.11.1, given the report from a bbolt db user on MacOS?
https://github.com/etcd-io/bbolt

Couldn't bbolt handle this by making the syscall directly? From Go 1.12 onwards they can go back to a plain (*os.File).Sync().

@mark-rushakoff, probably they could. Bleve is also affected and they don't use the bbolt fork yet; hopefully they'll switch if bbolt applies the workaround. Wish I knew who else depends on os.File.Sync :-(
@ianlancetaylor, yes that was the report I meant. I hope you won't fault me for asking.

Regarding the 1.12 release notes:

"Note that this might have a negative performance impact."

I'd suggest adding that File.Sync() prior to 1.12 is broken on MacOS, and may cause data loss/corruption.

That would imply that calling File.Sync could in itself cause data loss/corruption, which is not the case.
I think the current release notes text is clear enough.

What do you think of https://golang.org/cl/155038?
(I really think we are spending too much time on this.  It's a bug fix.)

LGTM @ianlancetaylor. Thanks for rewording it.

That would imply that calling File.Sync could in itself cause data loss/corruption
True. Maybe "File.Sync() prior to 1.12 is ineffective on MacOS, and cannot prevent data loss/corruption on system crash/power-off."

It's a bug fix with broad impact among database packages, including etcd bbolt, syndtr goleveldb, dgraph badger, and bleve.

Thanks, I'm going with what I've got.

I'm definitely late to the conversation, but I wanted to document my frustration with the decision of not backporting this fix.
We now need to replace all the calls to os.File.Sync to instead call a FileSync function for which we provide two implementations.
Once is very straight forward:
file_sync.go
// +build !darwin go1.12

package y

import "os"

// FileSync calls os.File.Sync with the right parameters.
// This function can be removed once we stop supporting Go 1.11
// on MacOS.
func FileSync(f *os.File) error {return f.Sync()}

The second one for now simply logs about this potential issue.
file_sync_darwin.go
// +build darwin,!go1.12

package y

import (
	"log"
	"os"
)

func FileSync(f *os.File) error {
	log.Printf("WARNING: This Sync operation might lead to data corruption or loss")
	log.Printf("WARNING: See this issue for more information: https://golang.org/issue/26650")
	return f.Sync()
}

Making this function do the right thing requires interacting with syscall package in ways it seems it's not designed to (according to this change). Before calling the syscall.Syscall(syscall.SYS_FCNTL, ...) we need to first call incref which is not exported, and then pass the system's file descriptor which is also hidden.
Could you, at least, provide a clear way of how to implement this function correctly?
I'm afraid I'll hack something that works but eventually will figure out something is missing.
Thanks

@campoy I understand your frustration, but there was no good solution here.  Making this change has led to multiple bug reports about significant performance changes, changes due to now using the correct behavior.  It would have been inappropriate to make a change that led to multiple bug reports in a minor release.
The code you show above looks correct and fine for a file on local disk.  I'm not sure there is a fully correct to call fsync for an NFS file in Go 1.11 on Darwin.  The incref is not an issue because you are calling the Fd method.

Thanks for the confirmation, @ianlancetaylor!
I think that just keeping my code in this issue should be enough to help others wondering how to fix it on their own codebases.
The PR fixing this issue for badger is https://github.com/dgraph-io/badger/pull/871.


Documentation change

Type of issue
Grammatical mistake
Documentation change
Change the documentation to :

title: Dev Home for Windows Developers
description: Dev Home is a new control center for Windows providing the ability to track your workflows and coding tasks using customizable widgets, set up your dev environment, connect to your developer accounts and tools (such as GitHub), and install apps and packages all in one place.
ms.date: 02/20/2024
ms.topic: overview
What is Dev Home?
Dev Home is a new control center for Windows providing the ability to monitor projects in your dashboard using customizable widgets, set up your dev environment by downloading apps, packages, or repositories, connect to your developer accounts and tools (such as GitHub), and create a Dev Drive for storage all in one place.

Use the centralized dashboard with customizable widgets to monitor workflows, track your dev projects, coding tasks, Azure DevOps queries, GitHub issues, pull requests, available SSH connections, and system CPU, GPU, Memory, and Network performance.
Use the Machine configuration tool to set up your development environment on a new device or onboard a new dev project.
Use Dev Home extensions to set up widgets that display developer-specific information. Create and share your custom-built extensions.
Create a Dev Drive to store your project files and Git repositories.

[!div class="nextstepaction"]
Install Dev Home (Preview)

Dev Home Machine configuration
To set up a new machine or onboard a new project with Dev Home, select Machine configuration. Dev Home can manage everything you need to get to your machine's development environment to a ready-to-code state, whether you want an end-to-end setup process, want to use a WinGet Configuration file, or just want to perform a quick step, like cloning a Git repository, installing a specific application, or adding a Dev Drive to improve the performance of your project's storage volume.
Learn more about how to get started with the Dev Home Machine configuration tool.

Dev Home dashboard widgets
Monitor your workflows using customizable widgets on the Dev Home dashboard. By default, Dev Home provides widgets for:

GPU: Monitor the performance of your machine's GPU.
SSH keychain: Lists the SSH connections available in your ssh/.config file. Select one of these SSH items to open that connection in Windows Terminal.
Memory: Monitor the performance of your machine's memory.
Network: Monitor the performance of your machine's network.
CPU: Monitor the performance of your machine's CPU.
GitHub: The Dev Home GitHub extension can be connected to your GitHub credentials to provide both customizable widgets and notifications.
Azure DevOps: The Dev Home Azure extension can be connected to your Azure account to provide customizable widgets for queries and pull requests.

System widgets
The Dev Home system widgets can provide real-time information on:

Memory: Amount in use, total available, total committed, total cached, paged pool, non-paged pool.
Network: Bandwidth measurements, including total kilobits per second for both sending and receiving data, along with the network name.
CPU: Total utilization, speed, and active processes.
GPU: Total utilization, temperature, and graphics chip name.

GitHub extension widgets
The Dev Home GitHub extension enables you to connect your GitHub account to Dev Home and create customized widgets that integrate with your GitHub repositories. To connect your GitHub account to Dev Home and begin creating GitHub widgets:

Once you've installed Dev Home, the GitHub extension will be available by default, but you will need to log-in to your GitHub account to gain access to the integrated features. Currently Dev Home supports only a single GitHub account. (See the DevHome Extension repo on GitHub for updates on adding support for multiple accounts.)

Select Add a widget from the top-right of your Dev Home dashboard. A list of widget options will appear that you can pin and then customize to your preference.

Learn more about the Dev Home GitHub extension and how to create customized widgets and set up Windows notifications.

Dev Home extensions
Dev Home extensions power the functionality of Dev Home's customizable widgets. By default, Dev Home includes the GitHub extension, but you can also create and share your custom-built extensions.
Learn more about Dev Home extensions, including how to create customized GitHub widgets, set up GitHub notifications, create custom ADO widgets, or build and share your own Dev Home extensions.
Dev Home Azure extension
The Dev Home Azure extension provides integration with Azure DevOps directly into Dev Home and provides customizable widgets to allow you to display your queries and pull requests. To connect your Azure account to Dev Home and begin creating Azure Developer Operations (ADO) widgets:

Install the Dev Home Azure extension from the Microsoft Store. Once installed, if your machine is connected to a work account already, Dev Home will connect automatically. Otherwise, you can sign into your Azure account in Dev Home's account settings.

Select Add a widget from the top-right of your Dev Home dashboard. A list of widget options will appear that you can pin and then customize to your liking.

Dev Home open source repos
Both Dev Home and Dev Home GitHub extension are open source and welcome your contributions.

Dev Home repository on GitHub.
Dev Home GitHub extension repository on GitHub
Dev Home Azure extension repository on GitHub

You can also contribute to the open source documentation for Dev Home by visiting the Windows Dev Docs open source repo on GitHub.

Sorry @skanda890 -- Where is the grammatical mistake you're pointing out here? Closing this issue, but please feel welcome to reopen and clearly identify where you see a mistake.

Sorry @skanda890 -- Where is the grammatical mistake you're pointing out here? Closing this issue, but please feel welcome to reopen and identify where you see a mistake.

Just change it to this and if you want to check where, then edit the current document using Grammarly, and see for yourself, since it is a YAML document ignore the so called YAML mistakes, and correct the spelling and grammar mistakes.


Expose hostport information on failed test

Expose hostport information on failed test
This will allow us to troubleshoot what messages came from which nodes
in error detail page.
Example output of the test I am currently working on, with this
information enabled:
not ok 68 The gossip should contain a flagged tombstone
  ---
    operator: ok
    expected: true
    actual:   false
    at: Array.validateEventBody [as 8] (/home/uber/ringpop-node/test/ringpop-common/test/ringpop-assert.js:147:11)
  ...
============== error details ===============

{
  "body": {
    "checksum": 702129473,
    "changes": [
      {
        "id": "79b38878-3003-4d1c-ae3f-5a3637e4c819",
        "address": "<IP_ADDRESS>:10489",
        "status": "alive",
        "incarnationNumber":<PHONE_NUMBER>877
      }
    ],
    "source": "<IP_ADDRESS>:10489",
    "sourceIncarnationNumber":<PHONE_NUMBER>877
  }
}

============================================

============== node index : hostport ===============
sut: <IP_ADDRESS>:10489
0 => <IP_ADDRESS>:30193
1 => <IP_ADDRESS>:57251
2 => <IP_ADDRESS>:39071
3 => <IP_ADDRESS>:43446
====================================================

I also tried to show which node the message came from for output to be even more helpful, but couldn't figure out in 1 hour. So I thought to propose this, to get started with.

LGTM

lgtm


Remark requests don't preserve newlines

When a student types in a remark request, even if they hit Enter the newlines are not preserved. This makes remarks difficult to process.
@wkwan We have had a request to patch this ASAP. Can you please look into this one?

Sure, I'll do it this week.


Ardougne Hard Diary - Icon in Wrong Place

The Quest Helper icon for the Ardougne Hard Diary - Monastery Poison Ivy is on the Tree Gnome Village fruit tree patch, not the Ardougne Monastery bush patch which is further north east of the Village (by the monastery).

The icons are working correctly.
This occurs when the 'Tree Gnome Village Palm ..' has not been checked as complete. If you manually check the box for that step it moves onto the 'Monastery Poison Ivy' step with an arrow pointing to the correct patch (the Ardougne Monastery Bush patch).


CS API anchor link to #receiving-notifications is broken

Bits of the spec link to https://matrix.org/docs/spec/client_server/r0.5.0#receiving-notifications, but this anchor no longer exists.

Looks like the rst2html converter decided to not do it for some reason :/


synchronized(Any, () -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3

@baronha\react-native-multiple-image-picker\android\src\main\java\com\reactnativemultipleimagepicker\GlideEngine.kt: (148, 9): 'synchronized(Any, () -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3
but i check my project use Kotlin 1.48
thanks!!

@Hi @anhoangzeus. Check last version(0.4.5). If this is still happening, please leave a comment below. There are some small changes in the setup for Android. Check README.


Create the code architecture for the game's UI

This is the idea I have right now:
[ ] Create a UIObject superclass for UI objects
[ ] Create a UICorner class for the corners
[ ] Create a UISide class for the sides
[ ] UI objects should have a customizable size. It should support both absolute size and relative size
[ ] UICorner objects should be anchored to their assigned corner of the screen
[ ] UISide obejcts should be anchored to their assigned side of the screen
[ ] It should be possible to have a second UISide extruding from the first
[ ] UICorner and UISide should never overlap
[ ] Convert the already existing UI elements (i.e. the End Turn button) into one of the new UI objects
[ ] Create some example UI objects for testing/showcase
EDIT: for maximum customizability, this should be a lot more generic.

[x] Create a GameUI class for the game's UI
[ ] Have the GameUI take care of its children's signals (e.g. _on_end_turn)
[ ] The GameUI should be able to be changed without problems
[ ] Create two example UI scenes for testing/showcase

This issue is still relevant: currently, we have a chat UI, an End Turn button UI and a popup UI that isn't yet generalized.
These UI elements are hard-coded to be where they currently are.
I want to be able to easily add, move and remove UI elements, so that the player can do it too in the future.
In other words, it should be possible to customize the UI's layout. That's what this issue should be titled


Removed anti-tempering rules

-Removed anti-tempering rules
The usage of anti-tempering tools are responsible to make an application more secure. The lines that I deleted were doing exactly the opposite of it. They were creating findings based on an implementation against tempering, so it don't make sense since the goal of a SAST is to promote a more secure development.
If the tools (like DexGuard) aren't secure, this kind of verification should be in other tool like SCA, because this kind of analysis go beyond the scope of a SAST.
The goal of this commit is to reduce the creation of unnecessary findings which of would be classified as False-Positive by the end-user.

@gustavomarinhozup try run tests in your local machine and fix then :)

Rebase and Sync with main branch too


Updated package locks and goldens.

I was working on another branch that needed a good old nuking and updated babel stuff which generates different output needing updated goldens and I thought I'd separate that out into this separate PR where I just npm run nuke and npm run update-goldens for review.  So here is that PR.

I'm having a side-thought which is, do we have enough coverage on non-minified build output so we can ensure updated babel compilers are doing the right thing before the output gets transformed into ¯\_(ツ)_/¯...

Obviated by https://github.com/Polymer/tools/pull/594


find powerOFaNumber.cpp

This program takes input from user and finds the power of the given number

hello @Shubhamrawat5


Synthesis.playground > Drum Synthesizers fails

Running the playground fails with the following error message:
error: Drum Synthesizers.xcplaygroundpage:29:60: error: missing argument for parameter 'channel' in call
snare.play(noteNumber: 60, velocity: randomVelocity)
^
, channel: <#MIDIChannel#>

This is fixed on the develop branch and will be in the next release, but you can see the easy fix:
https://github.com/AudioKit/AudioKit/blob/develop/Playgrounds/AudioKitPlaygrounds/Playgrounds/Synthesis.playground/Pages/Drum Synthesizers.xcplaygroundpage/Contents.swift


409 Confilct on importing client role that is already present in Keycloak but not in state

Describe the bug
If import.state is enabled and you're trying to import realm file that contains clients section where some of clients have defaultRoles defined (e.g., USER role), and the same role additionally defined in roles.client section, you will get the following error:
2021-04-24 22:41:43.501 ERROR 6280 --- [           main] d.a.k.config.KeycloakConfigRunner        : HTTP 409 Conflict
2021-04-24 22:41:43.505  INFO 6280 --- [           main] d.a.k.config.KeycloakConfigRunner        : keycloak-config-cli running in 00:03.033.

If the desctiption above is a little bit confusing, please check test-realm.json in the archive attached below.
To Reproduce
Try to import file test-realm.json from this archive test-realm.zip
Expected behavior
The attached file was obtained from a huge realm representation that has been previously configured via Keycloak UI and exported from Keycloak as json with Export groups and roles and Export clients enabled. So, if you're needed to import such a realm with keycloak-config-cli, there should be no errors, as if you do this with Keycloak UI import fuction.
Environment (please complete the following information):

Keycloak Version: 12.0.4
keycloak-config-cli Version: 3.2.0
Java Version: openjdk 15, but it's not relevant

Additional context
PR to fix this issue: #395

@jkroepke hey :) is there a date for the next release which fixes this bug? kind regards julian

@atbostudio
No new issues seen since this. I released 3.3.1


trouble to create slack token

in https://pingme.lmno.pk/#/services?id=slack
I know I need  a "token" and a channel id to send message via pingme to slack.
the channel id iseasy to find URL ( click any of your channels , and get this URL  https://app.slack.com/client/{ team_id} /{ channel_id } , is that correct ? )
but how to create a token ?
I try to create a token in apps

but which is the token pingme need ??
I try all these values in pingme , but always return
chc@hq39:~$ pingme slack -t "xxxxxxx758.373xxxxxxxx" --channel "D*****P32" --msg "test"
2022/06/29 15:10:53 failed to send message to Slack channel '' at time '': invalid_auth: send notification
chc@hq39:~$

is there any instructions to guide to create a valid token and get the channel id in slack for pingme ??

You have to create a bot token and use that to send messages.
You can find more info about it here : https://slack.com/help/articles/115005265703-Create-a-bot-for-your-workspace

yeah , I find the way to create the valid token in slack some days ago just after I creating this issue.
I think it might be helpful to add the slack URL to README , what dou you think ?


Add link to OpenAPI page on the UI

Closes #1147

It is the import Link from "next/link"; that is prepending /view/. Lets just use the Link component from material-ui and add this new value directly to actions to prevent the jumpiness of adding another element post mount.
Notably this swap only makes sense because all these pages link to the outside and won't benefit from client side rendering.

Sounds good to me