Gem is missing requires

If you just load a console and do require 'emailable', it's missing a few requires before it will work, specifically just testing Emailable.verify(...) I found that I needed to require uri, net/http, and json. All very logical things, but since plain Ruby environments (outside Rails) won't autoload those, the gem needs to have them as explicit requires.

@burlesona Can you confirm that the require 'uri' is necessary? After opening an irb console things seem to work with only needing net/http and json.

I would guess that net/http itself requires URI, so if you do it in that order then URI is already loaded. When I tried calling Emailable.verify without requiring anything else it failed three times, first because URI was missing, then Net, then JSON.
Sent from my iPhone

On Nov 18, 2021, at 9:01 AM, Evan Berquist @.***> wrote:

@burlesona Can you confirm that the require 'uri' is necessary? After opening an irb console things seem to work with only needing net/http and json.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

@burlesona this has been fixed in 3.1.1. This was unnoticed because our tests had net/http and JSON being required by other dependencies.


Thumbnail maps not showing background

The thumbnail maps aren't showing the background, just gray with a question mark. The task squares seem to show up fine.

Maybe we hit our Mapbox account limit on views?

confirmed that its not account limits.
@kamicut you have any ideas, I tried swapping out the token and nothing seemed to really change.

Strange that it dropped like that. Bug is with the token and map, the site's currently using mb light, not one from the Redcross.
Updating the token to their public one seems to have fixed it for me locally.
PR up here. Should be reviewed before merged.

@dalekunce before you do merge, it would be good to swap out the token (mb's default) with one from the RC account. I'm guessing the reason it didn't work before was because of the extra "+" we originally had to help concatenate a longer string.
If you replace the token here with the RC token it should work. Ping me if it still doesn't for some reason.
https://github.com/MissingMaps/partners/pull/32/commits/d6aca3f7bec2bc721581dc8cb0f99b888a3ca1a9

Looks like it's working now?


Mothroach crates nerf

About the PR
Changed 2 lines of code. Mothroach crates now only contain 2 mothroaches, but the price has been nerfed down to 2000.

Why / Balance
More balanced. Emag Moth can no longer order 20 mothroach crates to crash the server.

Technical details

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes
It's just a few YML, nothing really that much

Changelog

:cl: Avalon

tweak: Due to budget cuts, CentCom is now supplying less mothroaches per mothroach crate.

Okay so basically theres already a PR for this
#22450


Support for changing Server Root Path, both Literal and Relative

When Pode starts the server's root path is set the $MyInvocation.PSScriptRoot path, which defines the base path to the /views, /public and /errors directories.
Normally this is perfectly fine, but there are times when you need to alter the root path to your server because those directories above are located in a further subdirectory - or parent directory. Such a case could be when hosting your Pode server as a module, and the root path is set from the invocation of your module and not the Pode server.

Should be configurable using the pode.json file - as server.root
Support both literal and relative paths (testing if new path exists)

If relative, the path should be joined onto the invocation path (Join-Path)
If literal, use the supplied path instead of the invocation path
If none, just use the already default of the invocation path

How about /routes to auto include .ps1 files.
I do it like this:
$RootPath   = $PSScriptRoot
$RouteFiles = @()
$RoutePath  = (Join-Path -Path $RootPath -ChildPath "Routes")
if (Test-Path $RoutePath) {
    Get-ChildItem -Path $RoutePath -Recurse -Filter *.ps1 | ForEach-Object {
        $RouteFiles += $_.FullName
        Write-Host $_.FullName
    }
}
Server -Threads 2 {
    listen *:8085 http
    engine pode

    $RouteFiles | ForEach-Object {
        . $_
    }
}

That's a pretty neat idea for another feature - though it could be dangerous for people that already have a /routes directory, like yourself 😛
For this change, it's purely to help fix issues where the views/public/errors directories can't be found by Pode because the invocation path gets a little screwy - happens when starting the server within another function within another module, and the /views are one level deeper than the invocation path.

This worked for me! The only strange thing is that the json file has to be in the same path as the script/module calling it. So my json file for pode is in my "public" function directory. Thanks for adding this!

@jeremymcgee73
Ah, of course! I can add a -RootPath parameter to the server function then, same logic as the config just in code 😃


How to write joern script in Intellij IDEA with code completion?

I want to write my own joern script with complex logic.
I notice Intellij IDEA can not resolve symbol , code completion can't work.
Is there anything i need to configure?

That would indeed be nice, albeit I'm not sure about the best way to make that work at the moment. The trick is probably to configure the classpath correctly. I'll give this a try in the next days as well, let me know if you find something in the meantime.
fwiw a workaround is to write the code in the regular joern subprojects in a .scala file and then copy it over. Not ideal, but better than red squiggles all over the place...


It stopped working

With this demo code I was able to make some experiments, but then it stopped working completely.
I restarted the browser, tried with different browsers, restarted the app, removed the lock but nothing works anymore and the browsers is in an infinite loop tills it crashes.
import streamlit as st
from streamlit_server_state import server_state, server_state_lock

with server_state_lock["u1"]:
    if "u1" not in server_state:
        server_state.u1 = 0

server_state.u1 = server_state.u1 + 1

st.write(server_state.u1)

Traceback is
2023-01-26 13:02:04.236 Uncaught app exception
Traceback (most recent call last):
  File "/home/alex/PycharmProjects/test_bluelikon_client_streamlit/venv/lib/python3.8/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 565, in _run_script
    exec(code, module.__dict__)
  File "/home/alex/PycharmProjects/test_bluelikon_client_streamlit/singleuser.py", line 12, in <module>
    st.write(server_state.u1)
  ...
  File "/home/alex/PycharmProjects/test_bluelikon_client_streamlit/venv/lib/python3.8/site-packages/streamlit/runtime/scriptrunner/script_requests.py", line 157, in on_scriptrunner_yield
    return ScriptRequest(ScriptRequestType.RERUN, self._rerun_data)
  File "<string>", line 3, in __init__
RecursionError: maximum recursion depth exceeded while calling a Python object

Any idea?

I think that what happens here (because of streamlit's refresh logic) is that any time the script runs, the increment line is executed, which in turns makes all pages reload (since server state has in fact changed), thus the st.write code is in practice dead code!

I assume it is guaranteed that before page reload the current page is executed completely, so the st.write should be executed too.


propagate exit codes in scripts (close #578)

To resolve #578

I thought I tested this! Maybe I was only testing run-tests.sh? But your fix works for me.
Sorry for "fixing" the builds!

I see! So the issue is the failure of propagating the error code in the pipeline...

@favonia Does this look OK now?

Personally I would declare set -o pipeline upfront, but this is also fine. There are several things I wonder why a default bash does not take as the default setup...


BENCH: simplify benchmark setup, remove benchmarks/run.py

This is a very belated follow-up to https://github.com/scipy/scipy/issues/4789#issuecomment-97829621 to make it more understandable what running the benchmarks actually does.
Autodetection of Python version and tool to use for environment creation should make benchmarks easier to run in a variety of build setups.
Also update dependencies:

six and Tempita are no longer dependencies
upgrade Cython to latest (0.29.18 isn't in conda defaults).

Do you suggest running with runtests.py or with asv directly?

I always use asv directly myself

Do you suggest running with runtests.py or with asv directly?

I think we follow what we do with tests - runtests.py is documented as the default method, because it provides some consistency and tries to make things easier for new contributors. Both should work though. I personally don't use runtests.py.

The one CI failure is unrelated. Everyone seems happy here, so I'll aim to merge this soon unless there are more comments.

Please consider rgommers/scipy#15 before merging.

Forgot to hit the green button on this, it has been good to go for a while. Merging.


Server4 VM not working

@rajesh-rajagopal
Not working
This Vm
rioos@megambomi server:(nodelet-10998-uy2u1-server4-30631.servernet.in)

Fix:-
Ceph storage is full.

Now i removed unwanted storage

@rajesh-rajagopal
working and how to delete unwanted img file and vm id in ceph cmd


Assistant API

Feature Request

Duplicate of https://github.com/RageAgainstThePixel/OpenAI-DotNet/issues/156


Index out of bound

I am getting index out of bound exception. Currently, my usb drive has no partitions. So, is there any other way to get filesystem of a device?
val currentFs = device.partitions[0].fileSystem

What file system is the drive formatted with you are trying to access?

Are you using the java fs module?

I am using Kotlin module.

I tried with java fs module and I am getting same index out of bound exception.


Volatile DB: simulate failed file handle closes

See input-output-hk/ouroboros-consensus#783.

Closing in favour of the issue mentioned in the description above https://github.com/input-output-hk/ouroboros-consensus/issues/783


Update base.yaml for debian:bullseye

add bullseye references

Please add the following dependency to the rosdep database.
Package name:
TODO
Package Upstream Source:
TODO link to source repository
Purpose of using this:
TODO Replace. This dependency is being used for this reason. This is why I think it's valuable to be added to the rosdep database.
Distro packaging links:
Links to Distribution Packages

Debian: https://packages.debian.org/

REQUIRED

Ubuntu: https://packages.ubuntu.com/

REQUIRED

Fedora: https://packages.fedoraproject.org/

IF AVAILABLE

Arch: https://www.archlinux.org/packages/

IF AVAILABLE

Gentoo: https://packages.gentoo.org/

IF AVAILABLE

macOS: https://formulae.brew.sh/

IF AVAILABLE

Alpine: https://pkgs.alpinelinux.org/packages

IF AVAILABLE

NixOS/nixpkgs: https://search.nixos.org/packages

OPTIONAL

openSUSE: https://software.opensuse.org/package/

IF AVAILABLE

Please Add This Package to be indexed in the rosdistro.
ROSDISTRO NAME
The source is here:
http://sourcecode_url
Checks

[ ] All packages have a declared license in the package.xml
[ ] This repository has a LICENSE file
[ ] This package is expected to build on the submitted rosdistro

When opening a PR like this, please provide links to the packages you are adding, otherwise it is more work for us to verify.
For this change, none of these packages appear to be available in Debian Bullseye.  Therefore, I'm going to close this out.

The base.yaml work only under debian buster
In fact, if I try to install:
rosdep install --from-paths src --ignore-src -y --skip-keys "fastcdr rti-connext-dds-6.0.1 urdfdom_headers" --os=debian:bullseye
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
ignition_cmake2_vendor: No definition of [ignition-cmake2] for OS version [bullseye]
ignition_math6_vendor: No definition of [ignition-math6] for OS version [bullseye]
I have  the 2 .deb requred package already installed :
sudo apt install libignition-cmake2-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libignition-cmake2-dev is already the newest version (2.14.0-2~jammy)
sudo apt install libignition-math6-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libignition-math6-dev is already the newest version (6.12.0-2~jammy)
after my  base.yaml patch
rosdep install --from-paths src --ignore-src -y --skip-keys "fastcdr rti-connext-dds-6.0.1 urdfdom_headers" --os=debian:bullseye
#All required rosdeps installed successfully
is possible find it https://packages.debian.org/source/sid/ignition-math

I have the 2 .deb requred package already installed :

OK, sorry.  In that case, please feel free to reopen, but provide links to the packages in the debian database.  Then we can consider adding it.


Type inference with react elements is broken

I just read the article and was excited about better flow performance.
I tried the new flow and was disappointed that obvious cases are not inferred anymore.
Type inference across functions was the greatest feature in comparison to typescript. Now we don't have it.
What is the point of flow then?
https://medium.com/flow-type/asking-for-required-annotations-64d4f9c1edf8
https://flow.org/try/#0JYWwDg9gTgLgBAKjgQwM5wEoFNkGN4BmUEIcA5FDvmQNwBQduEAdqvACLIzLbMAmWSlDgBeOAAoA3nFwALYABs+lZnAC+ASlEA+CXTgz5SlVP0G4fLsgBccaTbgBGdQBozBrHwDmWVLYDaALpuBpp0GvR0WAAekLAyLGxw7FgAbgAyOHzoYuJaIrriZgA8nNy8AkLa7nZSFlYucJ4+6Jo6eubmxXzAqXAA9NWdGmol-WU8WPyCgtURdEA

/cc @samwgoldman

Oh, god. It's broken even for such simple case. This is worst release ever.
https://flow.org/try/#0JYWwDg9gTgLgBAKjgQwM5wEoFNkGN4BmUEIcA5FDvmQNwBQduEAdqvAMImTNbPwC8cABQBvOADdkAGwCuWOAF8AlHH4A+CdLn06WAB6RYcJq3gAFZJT6rhK9cLpw4AHk7gWveJNlZ+IgIwKcAD0anRK9EA

Seems like jsx support is broken, as this https://flow.org/try/#0JYWwDg9gTgLgBAKjgQwM5wEoFNkGN4BmUEIcA5FDvmQNwBQduEAdqvAMImTNbPwC8cABQBvOADdkAGwCuWOAF8AlHH4A+CdLn06WAB6RYcJq3gAFZJT6rhK9cLpw4ncC14xRk2VgBcARmU6JXogA is work perfect.
IMO for now can be used with * type like https://flow.org/try/#0JYWwDg9gTgLgBAKjgQwM5wEoFNkGN4BmUEIcA5FDvmQNwBQduEAdqvAMImTNbPwC8cABQBvOADdkAGwCuWOAF8AXAgCUcfgD4J0ufTpYAHpFhwmreAAVklPhuHqtwunDgAeTuBa94k2Vn4RAEYFOAB6TTpVeiA
Because I think this will be fixed.

Nothing is broken, but the inferred type reaches exports in an input position in a way you might not expect -- through the inferred element type.
An element is an object with the following type:
declare type React$Element<+ElementType: React$ElementType> = {|
  +type: ElementType,
  +props: React$ElementProps<ElementType>,
  +key: React$Key | null,
  +ref: any,
|};

So in the example here:
import * as React from 'react';
const Component = ({ value }) => value;
export default <Component value={1} />

the returned value's type property is the Component function itself. This is how the unannotated props are reaching exports. For example, I could consume this module like so:
import elem from "./foo";
elem.type({ value: "something unexpected" });

Well, I get it. But the noise from change has a bad taste.

Thank you for explanation and really
this
import * as React from 'react';

const Component = ({ value }) => value;

export const Parent = () => (
  <div>
     <Component value={1} />
  </div>
);

works.

This too
import * as React from 'react';

const Component = ({ value }) => value;

export const Parent = (): React.Node => (
  <Component value={1} />
);


Unable to login to account

Hi!
I've been using your software for a while now and it's great.
I can't seem to login to POE anymore. I used to have a Warband and Standard account.
Since the end of warband, I can't seem to login with session ID.
I have deleted all of the "Remove Only" tabs from the account.
The following text appears when logging in:
"Authenticating Frank_Fontaine                                                             [OK]
Loading characters...                                                                       [OK]
Loading Standard Stash Tab 1...
Loading Standard Stash Tab 1...                                                           [OK][OK]
Loading Standard Stash Tab 3...
Loading Standard Stash Tab 3...                                                           [OK][OK]
Loading Standard Stash Tab 4...
Loading Standard Stash Tab 4...                                                           [OK][OK]
Loading Standard Stash Tab 5...
Loading Standard Stash Tab 5...                                                           [OK][OK]
Loading Standard Stash Tab 6...
Loading Standard Stash Tab 6...                                                           [OK][OK]
Loading Standard Stash Tab 7...
Loading Standard Stash Tab 7...                                                           [OK][OK]
[Error] Downloading stash for Standard, details logged to DebugInfo.log, please open a ticket at https://github.com/Stickymaddness/Procurement/issues"
Thanks!

Hi there,
This was due to the recent patch which changed maps to have "tiers".
The new version of Procurement is out, which fixes this issue: https://github.com/Stickymaddness/Procurement/releases/tag/1.9.6
Unfortunately until GGG decide to support the dev community, these type of issues will continue to happen as it is out of our hands. http://i.imgur.com/yrPtajM.jpg


/clean: new command of message about requesting code review from the community

Checks

[X] I have thoroughly read and understand The Odin Project Contributing Guide
[X] The title of this issue follows the command name: brief description of request format, e.g. /help: add optional @user parameter

Do you want to be assigned to this issue?

[X] I would like to be assigned this issue to work on it

Description of the Feature Request
Every day a user pops a message in one of the help channels with the following content: "Hey, can anybody take a look at my code and see if I've implemented it in the most perfect way possible even though I'm still in Foundations?", or some variant like "Hey, can you guys check if my code is clean/performant/how can I shorten it/I feel it's messy/it's ugly" etc.
I think it could be useful to have a bot message with some general ideas like:

Great code comes from experience, so it can be very unproductive to pursue this ideal;
Don't compare your code to others (which might even have edited their solution long after they finished a project);
You don't need the community's blessing to approve your code. Students should have the autonomy to evaluate if they meet the project's criteria by themselves;
Performance is not a problem worth solving for small projects, so that's also a fruitless pursuit;

Something along those lines.
Acceptance Criteria
- [x] New command added to output the relevant message.

Additional information
No response

Thanks for the suggestion, Soffy.
Personally, I feel like such a command may be a little too general in its scope if it were to cover the majority or the suggested use cases. Feels more like general FAQ command and I'd rather not have a command purely because of a commonly asked question, because some questions do benefit from a human response that's tailored to the question - a more personal touch. And this sort of question, while very common I agree, is something I just feel more "right" responding to in person than via a bot command, if that makes sense?
But that is 100% just my own opinion. Would like to hear other thoughts from @TheOdinProject/odin-bot and @TheOdinProject/moderators too.

I see where Mao coming from. We have been adding too many commands lately, and we should start pruning them a little, to not void TOP from that human interaction, that is one of the charms which make TOP unique.
I do see where this information might be helpful, maybe we can add them to one of the earliest lessons if it wasn't there to instruct people about their code cleanless / performance.


Update on MLC Prompt

Hey there,
I think that in this line: https://github.com/iryna-kondr/scikit-llm/blob/6b0d5f5466cb48a9622b6eb8a60dfe9dc0446b2d/skllm/openai/prompts.py#L29 there is a mistake. A new unknown instance can be classified to zero labels as well. However, the current implementation pushes ChatGPT to choose at least on label (category). It should be rephrased as suggested in the PR, or with something similar to this.
Best regards

Hi @iamollas,
To be honest this was more of an intentional behaviour. But maybe we need to re-evaluate the approach. Your fix, however, will not change the final output as even if the model returns no classes, a random class will be assigned during the output validation step.
I was thinking about an alternative idea: allow users to provide an additional hyperparameter, that would add an additional candidate label that could be something like "None of the proposed categories are applicable".

@OKUA1 The last one seems to be the best idea indeed, but for evaluating the performance you have to make changes to the ground truth label vector (y). Many mll datasets contain instances with label vectors containing zeros. Therefore, I propose an alternative modification. Instead of using this code snippet:
https://github.com/iryna-kondr/scikit-llm/blob/6b0d5f5466cb48a9622b6eb8a60dfe9dc0446b2d/skllm/openai/prompts.py#LL30C1-L31C1
to have something like this:
"a single key label and a value corresponding to a binary vector the same size as the number of categories with 0 or 1 values, where 0 indicates an unassigned category and 1 indicates an assigned category.
Consider this, and it's up to you!
Thanks for your answer!

@iamollas
I believe this issue is somewhat related to the one you described.
https://github.com/iryna-kondr/scikit-llm/issues/14
I guess it would be nice to find a uniform solution for both multi class and multi label classifiers.
I am going to close this PR as changing of the prompt might not be required anyway.


Flutter iOS: only executed the native code without entering the main method

The following situations currently only appear on iOS：
I have a flutter project, and recently I found a problem. The code in the main method is often not executed, which means that no flutter code will be executed.
The way of expression is that after starting the App, it stays on the start-up diagram page and there is no obvious error message. Does anyone know why? Even though AppDelegate.m only has basic code, this is the case.
Hope the following is helpful:
stackoverflow
[✓] Flutter (Channel unknown, v1.12.13+hotfix.8, on Mac OS X 10.15.7 19H2,
    locale zh-Hans-CN)
    • Flutter version 1.12.13+hotfix.8 at /Users/lizhuoyuan/Development/flutter
    • Framework revision 0b8abb4724 (8 months ago), 2020-02-11 11:44:36 -0800
    • Engine revision e1e6ced81d
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/lizhuoyuan/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/lizhuoyuan/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 49.0.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] Connected device (1 available)
    • ONEPLUS A5000 • f6f90654 • android-arm64 • Android 9 (API 28)

• No issues found!

Hi @lizhuoyuan,
You seem to be on very old version of Flutter. First of all, upgrade to latest Flutter version and try again to see if it works.
If problem persists, please provide minimal complete code sample that shows the issue along with pubspec.yaml.
thanks.

Sorry, it's the configuration problem of my own file：ios/Runner.xcodeproj/project.pbxproj


Large event fonts on day view

I'm working on an app for older folks and love the calendar, but they can't see the words as the font is too small.  I'm trying to figure out the best path for making the event cells larger so that I can adjust the font to a size they can more ably see.  Would appreciate any pointers in the right direction....

I found the notification in the readme about how to subclass the collection view items and went that route.  I also changed the code in my implementation to scale the font size based on the amount of space available in the event.  Short meetings like 5 minutes long required the smaller fonts.


Help?!

Im absolutely new to both GitHub and Node and therefore I am struggling pretty hard with getting this to work, could you make a more detailed tutorial on how to install it please?
Kind regards
Revi

#27


Use peer dependency for jquery

I think it is a problem to have a dependency to jquery in this project. When installing slick-carousel and also a diffrent jquery version, I will have two diffrent jQueries bundled in my final Javascript file.
Npm already brings a feature called peer dependencies which resolves this problem. It would be great if we can patch the package.json and remove the hard dependency to jquery.

Hey @micha149 thanks for the issue. I appreciate your point; to me it's a question of which is the greater evil, undeclared dependency or potential dependency version overlap. My sense is that it's the former. The v2 branch drops jquery altogether, which is on its way.

A peerDependency is not an undeclared dependency. You will get a warning if you don't have jquery in your projects dependencies or in a wrong version. But you will not end in a mess of multiple jqueries in your project…

If there's a way to just declare a peer dependency and not lose the definitions for build systems that don't use NPM, then I think that'd be great.


Visualisation for InceptionV4

First of all, thank you for implementing this. It works great for AlexNet. I am new to this field so sorry if you do not find question appropriate.
I have downloaded inception v4 weights in .h5 file. Even tried to understand the structure of layers in it. I think visualisation in inception v4 required drastic code modification. Is there any short-cut? Can you help me for implementing visualisation of InceptionV4?
I am actually interested more in knowing filters, which play most important role for classification. Like out of 128 filters on convolution layer, which 10 are actually make my classification done. Can we do this by Visualisation in "Visualising and understand CNN" method?

Reopen if you have any further questions


Possible to use embedded assets with the 'images' button in a rich text field?

Hi,
I have tried to add an embedded asset within a rich text field on a build and none of the embedded assets are appearing in the asset directory.
Is this field usable within a rich text field?
Thanks,
Jay

Unfortunately it's not possible to use these embed codes in rich text fields, and there are no plans to support it. Honestly though, there are better ways to include assets than through rich text fields. Complex content structures with embed codes and text are better suited to Matrix fields.


Tree change onChecked and onUnchecked outputs

Pull Request Test Coverage Report for Build 145

8 of 9 (88.89%)  changed or added relevant lines in 3 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.05%) to 83.634%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/input-file.directive.js
2
3
66.67%

Files with Coverage Reduction
New Missed Lines
%

src/agenda-calendar.component.js
2
90.91%

Totals

Change from base Build 141:
-0.05%

Covered Lines:
2765

Relevant Lines:
3116

💛  - Coveralls


Discussion on API spec - Cell's format in the response

During meeting held on 7th february, open questions were raised:
Cell's format in the response: Currently, API support two different formats of defining the cells in which the requested area is divided for providing the information in the response:

Boundary Cells: The cell is defined by a polygon, composed by the internal area bounded by 4 geo positions. *Same solution as in Location Retrieval API

Geohash Cells: The Coordinates of the cell are representad as a string using the Geohash system. The value length, and thus the cell granularity, is determined by the implementation.

Discussion on which mechanisms to restrict, or how to allow developers to select one of them if multiple are supported.\
(Note that optionality in  one side implies obligatory for the other, in this case forcing developers to support both options)
Participants are invited to provide their view about this issue →

I believe , it is good idea to offer some flexibility to API providers by allowing them to choose one of these cell format that aligns with its network elements's capabilities (or limitations) . API providers should have the autonomy to decide how information will be shared with users—whether through 'Boundary Cells,' 'Geohash Cells,' or a combination of both.
Either users can specify their preferred cell format using the optional parameter  ( example :  '?cellFormat=boundary’ or  '?cellFormat=geohash’ or '?cellFormat=default’ ) otherwise it can be defined using two scopes - one allowing "geohash" parameters to be returned and another allowing only "boundary" parameters to be returned

population-density-data:retrieve:read:geohash
population-density-data:retrieve:read:boundary

Now it is upto provider whether they are offering both scope or only one scope.

It is not very clear how exactly "Boundary Cells" grid looks like and who decides this.
Unlike "Location Retrieval" Ppl density deals with a grid and data aggregation and therefore one should be careful moving "Location Retrieval" approach here.
Using a global grid system like geohash allows to avoid many issues one need to deal with otherwise.

@sachinvodafone agree on the flexibility, but that provides complexity on the provider, and also when aligning solutions among them for providing a common harmonized service to developers. We've been analyzing internally and believe that homogenizing the format is more valuable than flexibility.
@gregory1g Agree, boundary cell proposal was targeted for allowing some more flexibility but after giving it a second though, we believe that using an standard global grid will facilitate the life of developers and also implementations, ensuring that operators provide homogeneous responses.
Proposed WF:  Focusing on standard global geohash cells and eliminate the option of boundary cells, at least in this first version.

Dimetor input: our Aviation customers so far were not interested in a rasterized output format. Instead, they wanted to process GeoJSON, and that's what we implemented too. They naturally think in "volumes of airspace" where something significant happens, like danger zones or restricted zones, and thus their management systems are built with this in mind. An Airspace can be any arbitrarily shaped 3D polygon.
Now for Population Density they were so far interested in such 3D polygons as well, formatted as GeoJSON. They would send to our API which is the maximum population density they are able to accept in a certain area, and they would get back a GeoJSON containing such volumes (there could be more than one) where that condition is not met, i.e., where are too many people. They would then process this like any other restricted airspace where the flight not able to be conducted.

Proposed WF (discussed in the meeting and based on offline discussions):
To focus on standard global geohash cells and eliminate the option of boundary cells, at least in this first version.
New version may consider GEOJSON in the output, as suggested by Dimetor, due to the current support and preference of certain customers.
Issue to be closed, if no further comments are raised before next meeting.

Decision taken, focusing on geohash in first version


GC: OneDrive/SharePoint WebURL Fix

Description
Changes:

Use of ptr package to ensure safe dereferencing of pointers
Update to query to ensure that sharepointIds are part of the response
Alternate method created to obtain originating sharepoint site url

Does this PR need a docs update or release note?

[x] :no_entry: No

Type of change

[x] :sunflower: Feature
[x] :bug: Bugfix

Issue(s)

closes #1747

Test Plan

[x] :muscle: Manual

Tested within our tenant on every site. There were no incidents of a SharePointInfo being created without the resource owner or web URL not being populated within the tenant.


TST: use astropy and h5py nightly builds for bleeding edge CI

failures are due to pytest 8, and solved in #208

This is becoming necessary (not just a convenience) now that contourpy started publishing unpinned nightlies.

Still failing because numpy dev breaks h5py. I think maybe we should just not try to test against numpy dev more than our dependencies do...

ok it's still failing but this time it's really out of our control: the issue is that even h5py nightlies are too old and not compatible with numpy 2.0.0b1 yet. I'd recommend merging this as is.


[Bug] @InjectPersistenceManager not resolved as dependency when other @Inject parameters are present

Environment

Node: 16.14.0
Nest: 8.2.1
Drivine: 2.2.2

Steps to reproduce a Bug

Run nest new test --skip-install
Run cd ./test and npm install @liberation-data/drivine
Import Drivine:

DrivineModule.withOptions(<DrivineModuleOptions>{
  connectionProviders: [
    DatabaseRegistry.getInstance()
      .builder()
      .withType(DatabaseType.NEO4J)
      .protocol("neo4j+s")
      .host("localhost")
      .port(1234)
      .userName("neo4j")
      .password("password")
      .register("neo4j"),
  ],
}),

Generate a module and two services: nest generate module something && nest generate service something && nest generate service something/something2. Move something/something2/something2.service.ts to something/something2.service.ts (ignoring test files)
Inject PersistenceManager using @InjectPersistenceManager and SomethingService using @Inject:

constructor(
  @InjectPersistenceManager("neo4j") private readonly db: PersistenceManager,
  @Inject() private readonly somethingService: SomethingService) {
}

Observe error:

[Nest] 1696  - 31/05/2022, 13:10:40   ERROR [ExceptionHandler] Nest can't resolve dependencies of the Something2Service (PersistenceManager:neo4j, ?). Please make sure that the argument dependency at index [1] is available in the SomethingModule context.

Expected Result
Both the PersistenceManager and SomethingService are injected correctly.
Actual Result
An error occurs, causing Nest to shut down.
Notes
Without @Inject
This bug does not occur when @Inject is not used:
constructor(
  @InjectPersistenceManager("neo4j") private readonly db: PersistenceManager,
  private readonly somethingService: SomethingService) {
}

With @Inject("somethingService")
This bug does not also occurs when using a string with @Inject:
constructor(
  @InjectPersistenceManager("neo4j") private readonly db: PersistenceManager,
  @Inject("somethingService") private readonly somethingService: SomethingService) {
}

They are in the same module, both registered as providers. When I remove the PersistenceManager from the constructor, it works as normal.

Are you able to share code? Doing so can help me get to it faster.

Folder structure
.
└── src/
├── something/
│   ├── something.module.ts
│   ├── something.service.ts
│   └── something2.service.ts
├── app.module.ts
└── main.ts
Files
// main.ts
import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';

async function bootstrap() {
  const app = await NestFactory.create(AppModule);
  await app.listen(3000);
}
bootstrap();

// app.module.ts
import { DatabaseRegistry, DatabaseType, DrivineModule, DrivineModuleOptions } from "@liberation-data/drivine";
import { Module } from "@nestjs/common";
import { AppController } from "./app.controller";
import { SomethingModule } from "./something/something.module";

@Module({
  imports: [
    DrivineModule.withOptions(<DrivineModuleOptions>{
      connectionProviders: [
        DatabaseRegistry.getInstance()
          .builder()
          .withType(DatabaseType.NEO4J)
          .protocol("neo4j+s")
          .host("localhost")
          .port(1234)
          .userName("neo4j")
          .password("password")
          .register("neo4j"),
      ],
    }),
    SomethingModule,
  ],
  controllers: [AppController],
})
export class AppModule {}

// something/something.module.ts
import { Module } from "@nestjs/common";
import { SomethingService } from "./something.service";
import { Something2Service } from "./something2.service";

@Module({
  providers: [SomethingService, Something2Service],
})
export class SomethingModule {}

// something/something.service.ts
import { Injectable } from '@nestjs/common';

@Injectable()
export class SomethingService {}

// something/something2.service.ts
import { InjectPersistenceManager, PersistenceManager } from "@liberation-data/drivine";
import { Inject, Injectable } from "@nestjs/common";
import { SomethingService } from "./something.service";

@Injectable()
export class Something2Service {
  constructor(
    @InjectPersistenceManager("neo4j") private readonly db: PersistenceManager,
    @Inject() private readonly somethingService: SomethingService) {}
}

@NilsMoller Thanks! Can you please zip it up and send to<EMAIL_ADDRESS>

Done. Let me know if there is anything else I can do.

Hello, I've got the same issue where nest can't find the supposed injected PersistenceManager:
...Please make sure that the argument PersistenceManager:default at index [0] is available in the XXXModule context

Hi @jasperblues
I was going to update deps and introduce new config options to make it possible to setup pool size per connection. All went well, including tests.
The problem appeared when I tried to use built version with our app.
The problem happens with providing these singletons:
{ provide: DatabaseRegistry, useFactory: () => DatabaseRegistry.getInstance() },
{ provide: TransactionContextHolder, useFactory: () => TransactionContextHolder.getInstance() }

[Nest] 7179  - 07/02/2022, 12:25:13 AM   ERROR [ExceptionHandler] Nest can't resolve dependencies of the PersistenceManagerFactory (?, TransactionContextHolder). Please make sure that the argument dependency at index [0] is available in the DatabaseModule context.

Potential solutions:
- If dependency is a provider, is it part of the current DatabaseModule?
- If dependency is exported from a separate @Module, is that module imported within DatabaseModule?
  @Module({
    imports: [ /* the Module containing dependency */ ]
  })

I did not locate the problem yet. Will let you know if I'll find why it's the case.

@jasperblues I was able to fix the issue. There are 2 PRs. One with fix only and version bump and other with package updates and new connection options for pool configuration. Second PR includes changes from first as well. But second one drops compatibility with vulnerable or deprecated packages.


win: fix/redo the uv_rwlock implementation

The reader count would not be incremented when a thread successfully
acquired a read lock while another thread also held a read lock.
R=@bnoordhuis
R=@saghul
PS: anyone has an XP and 2k3 VM to run the tests with? I have, but the external hard disk that has it is on a different continent...

Doh. I think I have one, I'll see if I can run the tests.

Actually there are no tests for this -- I'm writing one.

See c410677. Note that this test currently doesn't pass even on newer versions of windows. This seems related to the fact that TryAcquireSRWLockExclusive succeeds when the calling thread already owns the write lock.
@bnoordhuis, @saghul - it would be great if you guys could review this test and make sure it at least passes on unix.

Hello! I traveled to the past and tested this patch with Windows XP and Visual Studio 2008.  Test doesn't pass:
[%  97|+ 240|-  10|T   1|S  14]: thread_rwlock_trylock
`thread_rwlock_trylock` failed: exit code 3
Output from process `thread_rwlock_trylock`:
Assertion failed in .\test\test-mutexes.c on line 81: r == UV_EBUSY

See c410677. Note that this test currently doesn't pass even on newer versions of windows. This seems related to the fact that TryAcquireSRWLockExclusive succeeds when the calling thread already owns the write lock.

That's what the last comment on MSDN seems to suggest. But it shouldn't matter since we don't the fallback on Windows > Vista, right?

@piscisaureus c410677 passes (there you check for EAGAIN or EBUSY), but 29af69d doesn't, since EAGAIN is returned.
On Unix we can get either, so maybe we should use the more relaxed variant.
The test passes on Unix and LGTM, FWIW.

That's what the last comment on MSDN seems to suggest. But it shouldn't matter since we don't the fallback on Windows > Vista, right?

TryAcquireSRWLockExclusive is the modern solution. We use it on Vista and later, which is why this behaviour is problematic. I was able to create a workaround for the double-write-lock scenario, but the same behavior happens when a thread that already has a read lock then tries to acquire the write lock, and that's not so easy to work around (because it would require keeping a list of all threads that own read locks).

(there you check for EAGAIN or EBUSY), but 29af69d doesn't, since EAGAIN is returned.

I don't really understand when unix reports EBUSY and when it does EAGAIN. The linux man pages suggest that EAGAIN is never used, except when more than X (a lot) threads all try to acquire a read lock. @bnoordhuis - can you enlighten me?

Generally speaking, my feeling is that the windows non-fallback rwlock implementation is just semantically incompatible with unix, and we should remove the modern path, and use the fallback implementation everywhere.
Or we could just delete the rwlock stuff outright. It seemed like a good idea at the time maybe, but in this day and age I think it has no place in libuv.

I don't really understand when unix reports EBUSY and when it does EAGAIN.

I think that's something I missed when reviewing 22f004db.  POSIX allows pthreads implementations to return either status code but we should really just report a single one, probably just UV_EBUSY.

TryAcquireSRWLockExclusive is the modern solution.

Ouch.

Generally speaking, my feeling is that the windows non-fallback rwlock implementation is just semantically incompatible with unix, and we should remove the modern path, and use the fallback implementation everywhere.

Fine by me!

Or we could just delete the rwlock stuff outright. It seemed like a good idea at the time maybe, but in this day and age I think it has no place in libuv.

We cannot do that in v1.x...

POSIX allows pthreads implementations to return either status code but we should really just report a single one, probably UV_EBUSY.

We could consolidate the error codes also on the Unix side then.

I've updated the PR - the test and the windows bits are good to land I think, but please review @bnoordhuis and @saghul.

We could consolidate the error codes also on the Unix side then.

I agree, but this PR doesn't address that.

@piscisaureus sorry for the delay! LGTM. I tested in on XP. Here is the CI for the newer ones, just in case: https://ci.nodejs.org/view/libuv/job/libuv+any-pr+multi/150/
I'll make the fix for Unixes.

Damn, the Windows bots are drunk tonight, I'll manually check on Windows 7.

My Windows 7 machine also says yes :-)

Here is the Unix patch for folding EAGAIN and EBUSY into EBUSY: https://github.com/libuv/libuv/pull/535

Thanks for the review, @saghul - just landed this stuff.

Do we want to make a new point release since now this is properly fixed?

Do we want to make a new point release since now this is properly fixed?

/cc @bnoordhuis @piscisaureus ^^

I'd say so.

What @bnoordhuis said.

Okidoki, will do!

@piscisaureus Lockless Inc., implemented a BSD-licensed pthreads layer (header-only) for Windows a few years ago; they also wrote a very detailed article documenting how they implemented the pthreads APIs to be semantically correct in the face of impedance mismatches with the Windows APIs (e.g., TryAcquireSRWLockExclusive): Pthreads on Microsoft Windows
Given the newer Windows APIs like reader-writer locks and condition variables offer better performance than the older, more-heavyweight APIs like mutex, it may be worth seeing if the code reverted by this PR can be fixed by adapting some of the techniques from that article (or, if the libuv license allows for it, just using their header).

@jack-pappas Thanks for the link! It's BSD licensed, but check this out:
A full implementation of this library is on the downloads page. It is licensed under the BSD license. However, be aware that it does use undocumented windows internals for a few of the synchronization primitives. These may be changed by Microsoft in the future, so probably should not be relied on for anything important.

I'm not sure we want to rely on obscure undocumented stuff. Also, we'd need some benchmarks proving that the alternative is actually faster/better :-)


Preload option for excluding dynamic imports

Currently preload will include preloads for dynamic imports which can result in a slower page since everything is being preloaded even what is being requested lazily.
We should reconsider this default, or more clearly have variations of the preload option to optionally include dynamic import preloading.

There was a bug here resulting in incorrect inclusions. This is fixed in https://github.com/jspm/generator/pull/134.
By default htmlGenerate will now only do static preloads. Setting preload = 'all' will then do dynamic import preloading.


Added test-suite and examples to the cabal file

The tests can be run with either stack test or cabal test.
Build the examples with either stack build --flag LambdaNet:examples
or cabal configure -f examples && cabal build.
After that they can be run with stack build && stack exec xor or cabal run xor.

Looks great! Thanks for taking the time to make LambdaNet that much better!


Feedback for “Type Merging Transform”

This tool seems incredibly powerful, but I'm having a hard time putting all the pieces together. Say I have a CompanyService that returns a Company[] (pk on CompanyID).
If I have an Employee.companyID, how do I "join" the Employee to the Company?

Type Merging Transform is for merging the same type from different sources;
Employee is a different type than Company, right?
Have you checked this?
https://the-guild.dev/graphql/mesh/docs/getting-started/combine-multiple-sources

Closing the issue due to the inactivity.
Let us know if you have any further questions.


fix: isMagento2App for version 2.4.5 and following

The Issue
If you run ddev config --auto on the latest Magento 2 version, the project type magento2 is not detected and php is used.
How This PR Solves The Issue
The check is for a string https://hackerone.com/magento in the root SECURITY.md.
(This is odd because that file is often deleted.)
However, the string has been changed to https://hackerone.com/adobe since version 2.4.5 as you can review here: https://github.com/magento/magento2/commit/3cb720f9ed01f3d53ba123fba9c048eb3b73f2b7
Manual Testing Instructions
Install Magento 2 version 2.4.5 or following via CMS Quickstart.
Run ddev config --auto.
See that the project type is still magento2.
Automated Testing Overview
The test for isMagento2App already exists.
Release/Deployment Notes
I don't think so.

This is in draft because the test tarball at https://github.com/ddev/ddev/blob/v1.22.7/pkg/ddevapp/ddevapp_test.go#L152 needs to be updated.
And I don't seem to be able to.

We're trying to create separate repos for those test setups. Would you be willing to update that if I create a repo and give you privileges on it? The basic idea is to have a full repo which is maintained with code, and create the tarball and put it there.
Examples:

https://github.com/ddev/test-shopware6
https://github.com/ddev/test-laravel
https://github.com/ddev/test-silverstripe
https://github.com/ddev/test-drupal
https://github.com/ddev/test-flask-sayhello

(https://github.com/orgs/ddev/repositories?q=test-&type=all&language=&sort=)
I took the liberty of creating the repo, https://github.com/ddev/test-magento2 and giving you maintainer access to it.
I know this is outside the scope of what you signed up for but it would be wonderful if you were willing to take it on.
Basically the old way of providing code as tarballs on a random unmaintained repo was hopeless. This way is at least a bit better.

I also added you to the project so you can restart tests, and sent you an invite to buildkite so you can restart those tests.

What's the philosophy for DDEV supported frameworks regarding versions?
Only support latest release or everything that is maintained?
Adobe supports Magento 2.4.4, 2.4.5 and 2.4.6 but the current check would be different for 2.4.4 and 2.4.5/.6.

In general we want to support the current stable version.
There are situations in TYPO3 where we check for more than one situation and handle it, but normally we want to just stay with the most likely thing people are using. isMagento2App() could certainly check more than one thing.

And thanks for your very important work on this!

@Morgy93 Please review, thanks!

Followup for a better detection is very welcome!


[Feature] Support chat completion stream with tool calls

Motivation
Using chat completion in stream mode with tool calls are becoming more and more popular. While Lmdeploy does support stream and tool, they can't be used at the same time, as Lmdeploy auto sets stream to False when tool is passed and tool_choice is not none.
Related resources
No response
Additional context
No response

Any updates on this?

We will reconsider the feature later.


(maint) Refactor PDB Docker HEALTHCHECK

The previous format can confuse LCOW and result in errors like:
CreateProcess: failure in a Windows system call: Unspecified error (0x80004005)
[Event Detail: failed to run runc create/exec call for container

Puppetserver is using this style with success

Test PASSed


flux completion powershell - Missing "powershell" in commands

In the documentation there is a missing part, the documentation states:
Windows:

cd "$env:USERPROFILE\Documents\WindowsPowerShell\Modules"
flux completion >> flux-completion.ps1

Linux:

cd "${XDG_CONFIG_HOME:-"$HOME/.config/"}/powershell/modules"
flux completion >> flux-completions.ps1
Options

While the flux completion command should be flux completion powershell.
Text should read:
Windows:

cd "$env:USERPROFILE\Documents\WindowsPowerShell\Modules"
flux completion powershell >> flux-completion.ps1

Linux:

cd "${XDG_CONFIG_HOME:-"$HOME/.config/"}/powershell/modules"
flux completion powershell >> flux-completions.ps1
Options

Please have a look at

https://github.com/fluxcd/flux2/pull/3465

Does this look like what you're suggesting?

Hi @kingdonb that is correct! thank you! 🎉👍


Kshreyashree task1 week1

Issue: #1
Make sure to add all the required items as per each issue.

Closed since this looks like a invalid PR.
https://github.com/opencodeiiita/CyberRepo-2077/pull/294/files


Mouse flicking back and forth causing vscode to hang

Does this issue occur when all extensions are disabled?: Unknown yes

VS Code Version:

Version: 1.66.0
Commit: e18005f0f1b33c29e81d732535d8c0e47cafb0b5
Date: 2022-03-30T05:50:41.156Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.4.0-107-generic

OS Version: Ubuntu, XFCE

Steps to Reproduce:
Reproduction case: https://github.com/microsoft/vscode/issues/146993#issuecomment-1131470956
I have no idea how to reproduce, I was clicking around in the file explorer when my mouse started flickering, including an icon on the side. it completely locked up and I had to terminate the process. When terminating it didn't respond to the kill signal, so I had to force it to close.
It seems there is a back-and-forth race condition for setting the pointer style somewhere.
Here is a GIF demonstrating the behaviour observed:

Note that the speed of the flickering was much faster, and it is due to my recording software that you cannot see it flicker fast regularly. I am in fact trying to click on different parts of the application, but as you can see no click is getting through.

I have the same problem here on Arch Linux. It happens after coding for a while, I also have no idea how, and I am forced to kill the process to reopen it again.

@deepak1556 Any progress with this? It is happening quite often for me now.

@joaomoreno I have experienced this crash 10 or so times this week. Is there anything I can do to help you lot collect data on when this happens so that you can debug it?

ping

@Alizter sorry for the delay on this issue, it slipped my notifications. Can you help provide the following data to further debug this issue,

Can you provide crash dump following the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-and-symbolicating-local-crash-reports
Does the issue happen when you run with --disable-extensions ?
Does the issue happen with latest insiders that comes with a newer runtime https://code.visualstudio.com/insiders/ ?

@deepak1556 Will this work when things are closed manually? When this situation happens I have to kill the process myself since VSCode is unresponsive.

It should generate a core dump if you try terminating the process with kill -3 <pid>

OK I managed to reproduce it:
code  --crash-reporter-directory /home/ali/vscode/ --disable-extensions
kill -3 204427

Here is the debug dir:
vscode.tar.gz

Can you also launch with code --verbose and provide the output when the hang happens.

My hand is starting to hurt from clicking now, but here you go.
code_log.tar.gz

Also if it helps, the memory usage of the process goes up about a MB a second, which if left noticed can be very large.
Occasionally when I have been in the lock, I have been able to click frantically the same way I do to produce it and it gets me out. However after some time this becomes impossible, presumably due to the amount of requests that VSCode ends up having to process.

Can you check if the issue repros with code --disable-gpu ? I am unable to repro the issue on my Gnome session will setup Xfce to confirm.

Managed to reproduce it:
 code  --crash-reporter-directory /home/ali/vscode/ --disable-extensions --disable-gpu  --verbose > code_log

code_log.tar.gz
vscode.tar.gz
This time it was a little different however. Now my pointer wouldn't work at all outside the window. I had to use the keyboard to navigate.
I've also gotten better at triggering it. Next to the extension buttons there is a draggable bar which lets you drag out the extension window. You need to click very near to that and the button multiple times and when it starts flickering, stop clicking and it will lock.

Managed to reproduce it:
 code  --crash-reporter-directory /home/ali/vscode/ --disable-extensions --disable-gpu  --verbose > code_log

code_log.tar.gz vscode.tar.gz
This time it was a little different however. Now my pointer wouldn't work at all outside the window. I had to use the keyboard to navigate.
I've also gotten better at triggering it. Next to the extension buttons there is a draggable bar which lets you drag out the extension window. You need to click very near to that and the button multiple times and when it starts flickering, stop clicking and it will lock.
@deepak1556 Would you like to continue on discord or something? This bug is very particular to reproduce, perhaps I can help out by showing you exactly what I am doing.

I just tried your command and have managed to reproduce the bug as well with your method, 3 times in a row. I'll try to avoid it while waiting for it to be fixed, but this is so weird and random that I don't know how to avoid it.

@Speykious What is your system info, I'm curious if we have any overlap?

I use Arch Linux with KDE. Here's some moer precise information just in case

Info
Value

Distro
Arch Linux x86_64

Kernel
Linux 5.17.8-arch1-1

DE
Plasma 5.24.5

WM
KWin

CPU
AMD Ryzen 9 5900HX with Radeon Graphics (16) @ 3.3GHz

GPU
AMD ATI Radeon RX 6700/6700 XT/6750 XT / 6800M

Memory
16 GB

More info: When this bug happens it freezes all VSCode Windows. Is this because the renderer is shared across all of them?

I am using Garuda Linux + KDE and I've had this experience as well.

I have the same problem too.

Archlinux
KDE Plasma
Intel CPU
Nvidia GPUs
32RAM
240 fps monitor

I have a 240 fps monitor and since it can be a visual problem, it may be because of the fps. Who has been able to reproduce it, how many fps do they have?

I indeed didn't mention it but my laptop has a 300 Hz Full HD screen.

I am using 60Hz monitor. And using an Nvidea GPU. However since this problem has been reproduced on an ATI GPU, I don't think it is the cause.

@deepak1556 If you have some time, would you like to debug this together? I can fairly consistently trigger it now.

This is happening to me and my colleague on vscode 1.68.1 and ubuntu 20.04.4, we both have 120hz monitors, nvidia gpus

Same problem here, even with GPU acceleration disabled. It also happens on clean install with no extensions.
My system is:

Info
Value

Distro
Kubuntu 22.04

Kernel
Linux 5.15.0-40-generic

DE
Plasma 5.24.4

Graphics Platform
X11

CPU
16 × AMD Ryzen 7 4800H with Radeon Graphics

GPU
AMD RENOIR / AMD Radeon RX 5500M

Memory
16 GB

Same issue, all instance of code are unresponsive.
vscode 1.69.0, Manjaro/Arch, Linux 5.18.6, Nvidia GPU. KDE / Plasma 5.24.5, AMD Ryzen 5900 series CPU

Same issue here on Debian 11 Linux x64 5.10 with KDE Plasma 5.20.5.
VSCode 1.69.0
Using nvidia 1050 gpu and nvidia driver 515.
During the freeze top shows Xorg and 2 code processes using a lot of CPU:
    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
   1477 root      20   0   25.9g<PHONE_NUMBER>08 S  70.8   2.0 146:04.54 Xorg
1184403 user      20   0   38.7g<PHONE_NUMBER>60 R  70.4   2.5   0:57.93 code
1184355 user      20   0   20.8g<PHONE_NUMBER>20 S  61.8   1.4   0:24.69 code

There was some activity visible in strace and gdb but I couldn't make anything of it.

Happening for me too. VSCodium.
Version:          VSCodium 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-29T12:35:34.859Z)
OS Version:       Linux x64 5.17.15-1-MANJARO
CPUs:             Intel(R) Core(TM) i5-10400H CPU @ 2.60GHz (8 x 2600)
Memory (System):  15.33GB (2.14GB free)
Load (avg):       0, 0, 1
VM:               0%
Screen Reader:    no
Process Argv:     --ms-enable-electron-run-as-node

Same issue.
Version: 1.69.2
Commit: 3b889b090b5ad5793f524b5d1d39fda662b96a2a
Date: 2022-07-18T16:14:10.636Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.15.0-43-generic

Same issue.
Fedora 36, X11, AMD.

Version: 1.69.2
Commit: 3b889b090b5ad5793f524b5d1d39fda662b96a2a
Date: 2022-07-18T16:14:10.636Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.18.13-200.fc36.x86_64

@deepak1556 Hi any update with this? Many more users have come forward experiencing this issue.

Me too. I'm trying to use VS Code version 1.69.0, in Red Hat Linux with XFCE.

Same issue with CentOS Linux 7 KDE 4.14.8
Version: 1.67.2
Commit: c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
Date: 2022-05-17T18:23:40.286Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 3.10.0-957.el7.x86_64

Thought I'd give an update on how to reproduce this bug.
Turns out you don't even need to click anywhere.
Just do the following:

make sure the sidebar is extended
hover over an icon of the sidebar
start moving slowly to the tip of the hover hint
observe

https://user-images.githubusercontent.com/13885008/183107718-52f0c08e-fb83-4cca-ab1d-47c99199968d.mp4

It seems like disabling hardware acceleration solved the issue for me. To disable it, open command palette Ctrl+Shift+P, type Preferences: Configure Runtime Arguments, paste "disable-hardware-acceleration": true and restart VSCode

It seems like disabling hardware acceleration solved the issue for me. To disable it, open command palette Ctrl+Shift+P, type Preferences: Configure Runtime Arguments, paste "disable-hardware-acceleration": true and restart VSCode

I tried this and can still reproduce the bug as per my comment above. Can you try to do that as well?

Disabling hardware-acceleration fixed this issue for me :-)

It seems like disabling hardware acceleration solved the issue for me. To disable it, open command palette Ctrl+Shift+P, type Preferences: Configure Runtime Arguments, paste "disable-hardware-acceleration": true and restart VSCode

I tried this and can still reproduce the bug as per my comment above. Can you try to do that as well?

I can't reproduce this issue in any way after disabling hardware acceleration (or maybe I'm just lucky?). This issue was happening to me randomly, and after enabling hardware acceleration I can't reproduce it even on higher zoom levels.

Unfortunately I can still reproduce the issue when hardware acceleration is disabled.

It seems like disabling hardware acceleration solved the issue for me. To disable it, open command palette Ctrl+Shift+P, type Preferences: Configure Runtime Arguments, paste "disable-hardware-acceleration": true and restart VSCode

I can still reproduce the issue as well when disabling hardware acceleration

It seems like disabling hardware acceleration solved the issue for me. To disable it, open command palette Ctrl+Shift+P, type Preferences: Configure Runtime Arguments, paste "disable-hardware-acceleration": true and restart VSCode

I can still reproduce the issue as well when disabling hardware acceleration

Well, just caught this issue too :(

Thought I'd give an update on how to reproduce this bug. Turns out you don't even need to click anywhere. Just do the following:

make sure the sidebar is extended
hover over an icon of the sidebar
start moving slowly to the tip of the hover hint
observe

vscode-flick.mp4
Things to note in my case:

I could not reproduce it on zoom level 0 or below. Zoom levels 1 and 2 reproduce this bug. Try to increase the zoom level to see if it happens.
From this first point, weirdly enough, staying on zoom level 0 seems to remove this issue, but then it's annoying not being able to use other zoom levels without taking that risk of freezing.
Disabling hardware acceleration didn't change anything.
I built (yarn) and ran (./scripts/code.sh) VSCode from source and couldn't reproduce the bug. The pointer does flick back and forth, but only when it stays still; as soon as I move it a few pixels more it stops flicking. Also, the pointer flicking doesn't block any shortcuts unlike in this demo.

After triggering the blinking taskbar right click vscode and then mouse mouse move to the right click option to move and keep the right click does not release about a few seconds will lift the blinking

Thought I'd give an update on how to reproduce this bug. Turns out you don't even need to click anywhere. Just do the following:

make sure the sidebar is extended
hover over an icon of the sidebar
start moving slowly to the tip of the hover hint
observe

vscode-flick.mp4
Things to note in my case:

I could not reproduce it on zoom level 0 or below. Zoom levels 1 and 2 reproduce this bug. Try to increase the zoom level to see if it happens.
From this first point, weirdly enough, staying on zoom level 0 seems to remove this issue, but then it's annoying not being able to use other zoom levels without taking that risk of freezing.
Disabling hardware acceleration didn't change anything.
I built (yarn) and ran (./scripts/code.sh) VSCode from source and couldn't reproduce the bug. The pointer does flick back and forth, but only when it stays still; as soon as I move it a few pixels more it stops flicking. Also, the pointer flicking doesn't block any shortcuts unlike in this demo.

After triggering the blinking taskbar right click vscode and then mouse mouse move to the right click option to move and keep the right click does not release about a few seconds will lift the blinking

e.g

https://user-images.githubusercontent.com/90960002/183557919-e01bf55a-68c3-4b5c-8c50-f26e9e0a98f4.MP4

The issue is relevant here for a long time already.

https://user-images.githubusercontent.com/44064051/183673210-b5d7e440-407f-4305-957a-48e1ef22291d.mp4

After triggering the blinking taskbar right click vscode and then mouse mouse move to the right click option to move and keep the right click does not release about a few seconds will lift the blinking

It works for me. In my case, just right click the VSCode on the taskbar and hover to the pop-up menu for a few seconds, and you will be able to calm the icon and the mouse cursor down. No neeed to hold the right-click button here.

After triggering the blinking taskbar right click vscode and then mouse mouse move to the right click option to move and keep the right click does not release about a few seconds will lift the blinking

It works for me. In my case, just right click the VSCode on the taskbar and hover to the pop-up menu for a few seconds, and you will be able to calm the icon and the mouse cursor down. No neeed to hold the right-click button here.

Yes, I found it too

I have been seeing this issue for quite a while now as well.  Fedora 35, KDE, AMD, Nvidia GPU
Sometimes I can go days without triggering it some days I end up triggering it 4-5 times.
I will try playing with zoom level to see if I can mitigate until a fix is found.

I have been seeing this issue for quite a while now as well.  Fedora 35, KDE, AMD, Nvidia GPU
Sometimes I can go days without triggering it some days I end up triggering it 4-5 times.
I will try playing with zoom level to see if I can mitigate until a fix is found.
update:
I can reproduce with previously mentioned steps regardless of zoom or hardware acceleration.

Has this been tried https://github.com/microsoft/vscode/issues/146993#issuecomment-1208870695

I have been seeing this issue for quite a while now as well.  Fedora 35, KDE, AMD, Nvidia GPU
Sometimes I can go days without triggering it some days I end up triggering it 4-5 times.
I will try playing with zoom level to see if I can mitigate until a fix is found.
update:
I can reproduce with previously mentioned steps regardless of zoom or hardware acceleration.

Has this been tried #146993 (comment)

I have tried everything except rebuilding from source.  I can easily reproduce the issue with the steps mentioned, however I cannot find any where the right mouse is active to see if the steps to get it out of the spasm will work.  After watching the second video I see that they are running on something with a separate app bar (which I detest, but I digress...).  I did try playing with the menu on the task bar entry and managed to get a notice along the lines of "an instance of vscode is running but not responding....", and then my entire window manager became unresponsive to mouse click events (pointer still moved).  I had to ssh into my desktop and kill vscode to fix that issue.

My knowledge toward windom systems are little.
I guess that the magic behind the menu-on-penel-icon has something to do with some sort of preview feature or "it's this window" hint, and only works on certain combinations of window systems, window-managers and panels.

This bug makes vscode unusable on Linux, I have to killall -9 code every hour or so. Is there a status on this?

@mrcsh @MadaraUchiha The workaround https://github.com/microsoft/vscode/issues/146993#issuecomment-1208870695 found by @morn-0 works on the Openbox window manager. You may want to try that. It would be great for someone to try on different WMs before the issue is solved.

@ShamrockLee the workaround is irrelevant in i3/regolith, since there's no taskbar to right click on. manipulating other tray elements does nothing.

@ShamrockLee the workaround is irrelevant in i3/regolith, since there's no taskbar to right click on. manipulating other tray elements does nothing.

I've got this too on centos7. It troubles. want a fix

I've got this too and have some more info:
it happens much more often when using laptop screen with 120 Hz refresh rate. It is rarely happens on external monitors with only 60 Hz.
It helps to disable KWin compositor: Shift + Alt + F12. (Disable GPU acceleration does not help.)
Disabling compositor is not a solution, just a workaround - because it breaks a lot of other things on desktop.
Archlinux, KDE, laptop with dedicated Nvidia + integrated AMD GPU.

In my case I can fix the problem by locking the pc with super+L in KDE and then login again which fixes the issue for me. However if there is a constant fix anyone found would be very nice.
Archlinux kde EOS, dedicated Nvidia gpu + intel integrated

Interestingly, I just encountered similar bug on SkypeForLinux when navigating the mouse pointer between the (Christmas-specific) reactions to comments.
The above workaround also applies to the Skype bug.
https://user-images.githubusercontent.com/44064051/206318420-2b4437e7-8a0f-4edf-b534-0cd7f252ceeb.mp4

The issue seems to have got mitigated on my laptop. The mouse pointer still flickers on the edge of icons, but that flickering no longer persists after moving the pointer away from such edges.
https://github.com/microsoft/vscode/assets/44064051/cf212034-b8d5-4630-a99a-df0c2be4bca6
Similar mitigation happens to Skype as well.
https://github.com/microsoft/vscode/assets/44064051/42cbb36b-5440-4e77-a29d-a6a1546c4d7e

I've got this too and have some more info: it happens much more often when using laptop screen with 120 Hz refresh rate. It is rarely happens on external monitors with only 60 Hz. It helps to disable KWin compositor: Shift + Alt + F12. (Disable GPU acceleration does not help.) Disabling compositor is not a solution, just a workaround - because it breaks a lot of other things on desktop. Archlinux, KDE, laptop with dedicated Nvidia + integrated AMD GPU.

I've applied such solution, do we have any better idea nowadays?


Debug and fix file upload (>1MB) on the DBS

After some investigations, in frontend we received 413 error which means Content Too Large from Django side. An hypothesis could be that client_max_body_size needs to be increased in the nginx configuration for django server as it is highlighted in this article.

The issue is fixed because the nginx configurations for Django server needed to be increased and now the upload for files larger than 1 Mb works. Tested with 86 Mb file and it worked.


Breaking change: Roslyn analyzer CA2013 - Do not use ReferenceEquals with value types

Breaking change: Roslyn analyzer CA1831 - Use AsSpan or AsMemory instead of Range-based indexers when appropriate
This new Roslyn analyzer will emit a warning if it finds instances where the System.Object.ReferenceEquals method is used to test one or more value types for equality.
Depending on the project's settings, the warning could show up as a build break.
Version introduced
This analyzer is included in .NET 5 Preview 8 SDK and turned on by default.
It can be turn them off by setting the MSBuild flag EnableNETAnalyzers to false.
Old behavior
If the user compared two value types using System.Object.ReferenceEquals, they are boxed before they get passed to the method, which causes the method to return false even if they both represent the same instance of a value type.
New behavior
The user will now see the CA2013 warning suggesting to instead use an appropriate equality operator, such as ==.
Reason for change
Using System.Object.ReferenceEquals to compare value types can lead to wrong results.
Recommended action
Change the code to use an appropriate equality operator, such as ==. This warning is not safe to suppress.
Refer to the documentation for rule CA2013 for a detailed explanation on when to expect this rule violation to be diagnosed.
https://docs.microsoft.com/en-us/visualstudio/code-quality/ca2013
Category

Core .NET libraries

Affected APIs
System.Object.ReferenceEquals when used to compare two value types.

Issue metadata

Issue type: breaking-change

cc @buyaa-n @GrabYourPitchforks @jeffhandley

LGTM


Include knife-supermarket

Add the knife-supermarket gem to Chef Development Kit.

This is a conversation started in https://github.com/chef/knife-supermarket/issues/20

knife-supermarket has already been included in the chefdk, and is being removed again now that knife-supermarket has been merged into chef/chef https://github.com/chef/chef/pull/4896


Standard ipv6

"If you selected the Standard SKU, you do not have the option to select IPv6. You can only create an IPv4 address when using the Standard SKU."
This appears to be outdated? See image.

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

ID: 19d6d70c-eed7-8fdc-e04b-995cabf0a902
Version Independent ID: a33391e9-3023-8212-6246-d64071efc2b5
Content: Create, change, or delete an Azure public IP address
Content Source: articles/virtual-network/virtual-network-public-ip-address.md
Service: virtual-network
GitHub Login: @KumudD
Microsoft Alias: kumud

I think I identified the issue - it must be referring to the SKU of the Load Balancer, not the IP address itself (even though this is the IP address page). PR on #39180.

@dcbrown16 Glad to know that you have self resolved the issue. Thanks for the update.


Fix JS parsing

In the process of fixing JS benchmarks I noticed the parsing of the results wasn't working: https://github.com/apache/arrow/pull/37668#issuecomment-1781790381.
Something may have changed in yarn since the last time we ran these? not sure

build failure unrelated; will come back if we get past that and this change broke something
https://github.com/r-lib/actions/issues/772


macOS: Planned Wipe and Reload, Backing Up Keybase

Hey,
I'm planning on doing a fresh install of Sierra. Can I just backup my /Library/Application Support/Keybase folder and then put it back once I reinstall Keybase from Brew post rebuild? This way it should retain my keys and provisioned system data right?
--Brian

The key directory is $HOME/Library/Application Support/Keybase.  The other stuff is soft state.  In particular, there are config.json and a keybase.*.mpack files that you should keep.

Yep! That's what I figured. Thanks :)
On Saturday, October 29, 2016, Maxwell Krohn<EMAIL_ADDRESS>wrote:

The key directory is $HOME/Library/Application Support/Keybase. The other
stuff is soft state. In particular, there are config.json and a
keybase.*.mpack files that you should keep.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/4756#issuecomment-257126237,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIDOC3j6B-Lc0lA2612k7VlJSbByPmlyks5q4_LOgaJpZM4KkCeo
.

Thanks, my MacBook died on sunday and I was able to recover from Time Machine with this tip.


Used ivy is too old

Hi!
Please look at:
https://groups.google.com/forum/#!topic/play-framework/dRj4VPbFJAA
https://groups.google.com/forum/#!topic/play-framework/xTt5WQMtTY0
And it is possible to find plenty of other similar ones. I guess the root is here:
https://issues.apache.org/jira/browse/IVY-1487
SBT seems to use custom ivy 2.3.0, while the mentioned ivy issue was fixed in 2.4.0. Can the patch be applied to sbt-ivy?

Could you comment on #1920?
Maybe we can revive the discussion.

OK, have moved there.


Link to Wiki missing

Is there a link to the Wiki anywhere? It's referenced in the README, but I can't see a link.
Thanks!

It's the default wiki page:
https://github.com/bitbank2/JPEGDEC/wiki


Prettier setup

Apply two prettier configs,

*.fc
.ts

Use the semi:false for ts.
with option to apply updates to the file

Done


Improve directories in configuration

It's currently not clear that TwigStan scans for both Twig templates and PHP code in directories.
Maybe this should be split up:
parameters:
  twigstan:
    directories:
      twig:
        - templates
      php:
        - src/Controller

Maybe is more clear use php_controllers or only controllers instead of php. In theory twigstan does an analysis for php controller renderpoints and not all php files or am I wrong?

Most of the time yes, but not always. There can be other places that use Twig to render things. For example, for email or notifications. With the new TemplateContextCollector it can be found anywhere.

I see...thank you for explanation :)

If you want to give this a try, please go ahead 😊

I would be happy :)


adding user stories to planning

General Checks

[ ] the branch is up to date with main/master
[ ] the code works when pulled and run locally
[ ] All CI checks pass
[ ] all conflicts are resolved (if any)
[ ] PR has a descriptive title
[ ] PR has appropriate labels and milestones for easy identification
[ ] PR it is assigned to the owner
[ ] reviewers are assigned
[ ] the PR contributes only one focused change
[ ] It is in the appropriate column in the project board (if necessary)
[ ] has short and clear description
[ ] is linked to an issue (if it is related)
[ ] feedback is addressed (if any and if it is appropriate feedback.)

Markdown

[ ] the markdown source is formatted
[ ] spelling and grammar is correct in all text
[ ] The markdown looks correct when you preview the file
[ ] all links and images work

HTML

[ ] pages besides /index.html are stored in /pages
[ ] the code is well-formatted
[ ] the HTML is valid
[ ] there are no inline styles (example: style='color: red;')
[ ] there are no <style> tags with CSS, all styles are hrefs
[ ] there is no inline JavaScript (example: onclick='doSomething()')
[ ] there are no <script> tags with JS, all JS is in an separate file
[ ] ids are used for JavaScript only, not for CSS
[ ] semantic tags are used
[ ] spelling and grammar is correct in all site content

CSS

[ ] the code is well-formatted
[ ] passes all the linting checks

Hi @kiishiakande! Do we have a user story for the sign up feature?
Other than that, it looks great. Just fix a slight misspelling please (credintials should be credentials).  😀

I've just made some changes and added the second user story @cristobal-lopez

good job @kiishiakande , but the feature from line 11 - 15 is a separate feature with a different user story. If possible please make every action a separate user story, Pressing login to the events is a story, pressing sign up to form is a user story, searching a location is a user story. Try to make every single step a user story.


Dependency error to update @angular/material 11 to 12

I am migration my project from Angular 11 to 12, and when I tried to update the @angular/material@12 I had an error with ng-pick-datetime:
$ ng update @angular/material@12

Using package manager: 'npm'
Collecting installed dependencies...
Found 51 dependencies.
Fetching dependency metadata from registry...
                  Package "ng-pick-datetime" has an incompatible peer dependency to "@angular/cdk" (requires "^7.0.0", would install "12.2.13").
✖ Migration failed: Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.
  See "/tmp/ng-3v8GXt/angular-errors.log" for further details.

@dpeliser-zebra you shouldn't be using this version anymore.. use my forked version: https://www.npmjs.com/package/@danielmoncada/angular-datetime-picker

@dpeliser-zebra you shouldn't be using this version anymore.. use my forked version: https://www.npmjs.com/package/@danielmoncada/angular-datetime-picker

@danielmoncada How can we even know? Luckily I was able to reach here after doing lots of npm i, clean, trials and errors and googling... Could you please mention in the main README of ng-pick-datetime or ng-pick-datetime-ex?

@danielmoncada  - that's what I am suggesting. Update the README file, so that others know which package to use.

@paritosh64ce how can I update the README file if you can't edit or merge any PRs? I do not own this repo.


Continuous deployment to hosted site

It would be nice to have a WIP version of the site that is deployed on every merge. We might be a ways off from this.

Consume Storybook package from home application.
Dependabot hook that submits a new PR when new Storybook package has been pushed to upgrade the package(s) in the home app.
Deploy static site when PR is merged to home/main (i.e. Netlify)

agreed!  I'll work on this.

#67


[CP] [CFE][ffi] Support FFI Finalizable transformation of redirecting factories

Commit(s) to merge
cc40e17fd9ae4680371c4a3efb4c4762f33946bd
Target
stable
Prepared changelist for beta/stable
https://dart-review.googlesource.com/c/sdk/+/302202
Issue Description
A redirecting factory is normally encoded as something like
  static factory •({required self::HelperClass bar = #C1}) → self::Bar
    return new self::Foo::•(bar: bar);

which the CFE also expects to recreate its internal state when loading
a dill file.
The Finalizable transformation from FFI can change that to something
like:
  static factory •({required self::HelperClass bar = #C1}) → self::Bar {
    return block {
      final synthesized self::Foo :expressionValueWrappedFinalizable = new self::Foo::•(bar: bar);
      _in::reachabilityFence(bar);
    } =>:expressionValueWrappedFinalizable;
  }

though, which the CFE doesn't understand and subsequently crashes.
What is the fix
The fix makes the CFE understand this transformed version, fixing the crash.
Why cherry-pick
Crashing if for instance using the Realm package.
Risk
low
Issue link(s)
https://github.com/flutter/flutter/issues/124369
Extra Info
No response

Marking this as approved based on @mraleph comment above.  @johnniwinther please remove the approval if you feel otherwise.


Rock Paper Scissor game

PR Description 📜
I build a rock paper Scissor game In which  a person need to select one option out of rock ,Paper And scissor and then computer select Randomly a option out of these three .so if a person win he will get +1 point and if he loss then he will get -1 point and if match draws then he will get 0 points
Fixes #158 issue.

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @lakhan06 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Hey @lakhan06 👋!
@kunjgit here,
We have this annoucement to make 📢!!
We have updated our README 🚀
Make sure you follow proper guideline to raise your next issues !!
Make sure you join our Discord🕹 if you haven't 😇
Thank you 💗!

Thank you  @lakhan06 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Set up CI for the project

The CI should ensure that all tests succeed and preferably check the code coverage.

I'm on this


Lack of Regex Assertions Documentation

https://irclog.perlgeek.de/perl6/2018-05-07#i_16140539

Tison | .ask moritz I found a regex like regex key { <![#\[]> <-[;=]>+ } and wonder what's the different between <![...]> and  <-[...]>. BTW, the former isn't documented.
Tison | It looks like the former is an assertion while the latter really matches something
Tison | our documentation on assertion only shows look-around assertions but no general assertion forms
timotimo | yeah, if you have a ? or ! after the < it becomes a zero-width matching assertion

Check out @TimToady 's comment in the IRC https://irclog.perlgeek.de/perl6/2018-05-08#i_16141345


Possible to add a repeat option for a command?

Would it be possible to implement repeating a single command without specifying it as a sequence and typing the same thing multiple times? Eg: at the moment I have this (because there's no VSCode API command to do the same 🙄):
"cmd.sidebar.minimumWidth": {
  "sequence": [
    "workbench.action.increaseViewWidth",
    "workbench.action.increaseViewWidth",
    "workbench.action.increaseViewWidth",
    "workbench.action.increaseViewWidth",
    "workbench.action.increaseViewWidth",
    "workbench.action.increaseViewWidth",
    "workbench.action.increaseViewWidth",
    "workbench.action.increaseViewWidth",
    "workbench.action.increaseViewWidth",
    "workbench.action.increaseViewWidth",
    "workbench.action.increaseViewWidth",
    (etc...)
  ]
}

but it would be so much more convenient to specify it as something along the lines of:
"cmd.sidebar.minimumWidth": {
  "command": "workbench.action.increaseViewWidth",
  "repeats": 15
}

Many thanks for your efforts on this extension - it's proving very useful!

From the next version:
"View+": {
	"command": "workbench.action.increaseViewWidth",
	"repeat": 2,
},

"View++": {
	"sequence": [
		"workbench.action.increaseViewWidth",
		"workbench.action.increaseViewHeight"
	],
	"repeat": 2,
},

Perfect - thanks for the quick turnaround! 👍


update_timestep leads to NaNs

Hello,
I tried to test the algorithm on CartPole-v1 and, depending on the update_timestep parameter, it crashes due to NaNs in the KL divergence. Is this a bug or is it just a sensitive parameter?
update_timestep = 100 # leads to occasional crashes
update_timestep = 200 # lesser crashes than with 100
update_timestep = 500 # Is stable

Hello,
I tried to test the algorithm on CartPole-v1 and, depending on the update_timestep parameter, it crashes due to NaNs in the KL divergence. Is this a bug or is it just a sensitive parameter?
update_timestep = 100 # leads to occasional crashes
update_timestep = 200 # lesser crashes than with 100
update_timestep = 500 # Is stable

Hi Gianluca,
I'm currently very busy with my PhD application, and I have almost forgotten this project.
Your issue seems to be general, you could try to debug it yourself or with your friends.

Hello,
I tried to test the algorithm on CartPole-v1 and, depending on the update_timestep parameter, it crashes due to NaNs in the KL divergence. Is this a bug or is it just a sensitive parameter?
update_timestep = 100 # leads to occasional crashes
update_timestep = 200 # lesser crashes than with 100
update_timestep = 500 # Is stable

Hi Gianluca,
I'm currently very busy with my PhD application, and I have almost forgotten this project.
Your issue seems to be general, you could try to debug it yourself or with your friends.

Hello YYCAAA,
thank you for your answer. There seems to be an issue with your reward estimation. In the current case, your code just works with full episodes because you never call the critic network with the final state. This needs to be fixed to work properly. This will probably fix the issue.


add Multipart document in .Net SDK

add csharp part of Multipart document

No changes needing a change description found.

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


Allow query result/subscription result window to be cleared

Over time a lot of information can pile up in the result window, especially in the case of subscriptions.
Describe the solution you'd like
A way to clear the result window, perhaps using a button.
Describe alternatives you've considered
Opening new window, but that requires setting up the URLs and queries again (and perhaps some other settings).

That was fast. Nice! Thanks.


events: refactor event distribution

In the course of setting out to add filters and address some cleanup, it
was found that we had a few problems in the events subsystem that needed
addressing before moving forward.
The biggest change was to move to the more standard terminology of
publish and subscribe. We make this terminology change across the Go
interface and the GRPC API, making the behavior more familier. The
previous system was very context-oriented, which is no longer required.
With this, we've removed a large amount of dead and unneeded code. Event
transactions, context storage and the concept of Poster is gone. This
has been replaced in most places with a Publisher, which matches the
actual usage throughout the codebase, removing the need for helpers.
There are still some questions around the way events are handled in the
shim. Right now, we've preserved some of the existing bugs which may
require more extensive changes to resolve correctly.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>

@ehazlett PTAL

NOTE: This should not be merged until the Windows CI has run too ( cc
@crosbymichael, looks like the webhook for appveyor is not enabled
correctly)
On Tue, Jul 25, 2017, 1:31 AM Stephen Day<EMAIL_ADDRESS>wrote:

@ehazlett https://github.com/ehazlett PTAL
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/containerd/containerd/pull/1246#issuecomment-317633791,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APUifno98uW64QY630jaB8c-a_6YQYL-ks5sRX2lgaJpZM4OiFAJ
.

--
Sent from my phone.

@crosbymichael See https://github.com/containerd/containerd/pull/1246#discussion_r129302831 and the TODO I have there. Also, we use the GRPC client interface through the shim. Should be easy enough to clean up in this PR, just wanted to keep the changes scoped for a single PR.

Codecov Report

Merging #1246 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master    #1246   +/-   ##
=======================================
  Coverage   28.37%   28.37%
=======================================
  Files          28       28
  Lines        2841     2841
=======================================
  Hits          806      806
  Misses       1888     1888
  Partials      147      147

Impacted Files
Coverage Δ

task.go
0% <0%> (ø)
:arrow_up:

process.go
0% <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 9434bf9...27ec162. Read the comment docs.

@mlaventure PTAL

LGTM


[Tooling] Provide tooling to update poktroll and cosmos proto files.

Objective
Create a tooling on Makefile that allows us to update poktroll and cosmos protobuf files.
Origin Document

Thanks @jorgecuesta!
Great use of screenshots :)


CI release workflow refactor.

Summary of this proposal
Refactor the workflows to allow releasing on a reusable workflow (commit + push + tag)
as per discussion with @patrick-stephens

Will open a new one in short.


Trying to Download 115th congress .ORD file give 404 error

Just attempted to download 115th Congress ORD file.  I get a 404 error.

Can confirm that we have no ORD files for the 115th (house, senate, or both)

We'll fix this.
On Mon, Jan 9, 2017 at 11:15 PM, Aaron Rudkin<EMAIL_ADDRESS>wrote:

Can confirm that we have no ORD files for the 115th (house, senate, or
both)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/JeffreyBLewis/WebVoteView/issues/107#issuecomment-271503278,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS6Qi8Xcbr1QQP5Rue9dO3w-iE94a0oeks5rQy_9gaJpZM4LfGQ5
.

Data exists now, but this will have to be re-run once the data are fixed by Adam.


Fix script analyzer issues in xWindowsUpdateAgent

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


UIManager.RNGADBannerView is undefined

In the RNAdMobBanner.js, in the loadBanner(), the UIManager.RNGADBannerView is undefined.
Version of "react-native-admob": "^2.0.0-beta.2"
My react-native code is as below:
<AdMobBanner adSize="fullBanner" adUnitID="....."  onAdFailedToLoad={error => console.error(error)} />
I used create-react-native-app rather than react-native init to initialize my app.
Is anyone facing the same problem as I am ?

Have the same problem over here

i faced the same issue .
this is my post : https://github.com/sbugert/react-native-admob/issues/212

+1

react-native link react-native-admob after that restart app.

Since create-react-native-app uses Expo you will have to “eject” to make it work I’m afraid.
https://github.com/react-community/create-react-native-app/blob/master/EJECTING.md

The issue is continuing.

Now I have the same issue


Bridge CRAN downtime periods

CRAN stops accepting submissions for approximately two weeks twice a year (see below). If a CRAN package gets archived before such a downtime and the maintainer does not get time to fix it in time, the archived package has to remain archived over also the CRAN Incoming downtime period.  Also, after such downtimes, there is often a lot of package submissions immediately after CRAN comes back, which delays any unarchiving even further.
Because of this, CRANhaven could extend its 4-week limit, accounting for any such CRAN submission downtime periods. Ideally, this can be fully automated, but it's not clear it that can be done robustly, because the date information is often a manually written note on the CRAN submission page.
Some of the past submission-downtime events are:

2023-12-22 -- 2024-01-08
2023-07-21 -- 2023-08-07
...
2021-12-21 -- 2022-01-03
...
2019-08-09 -- 2019-08-18
...
2018-12-21 -- 2019-01-02
...
2017-12-22 -- 2018-01-03

I have been tracking this too: https://github.com/llrs/blogR/issues/57.
Last December I sent an email asking for it to be posted on the mailing list (and not just the home page of CRAN).
The response I got is was they/he would try to post a message to r-package-devel.


feat: add stripTrailingZero function

#82
Changes:

Moved existing trailZero() as new function stripTrailingZero() for removing both prefix and suffix zeroes.
Added test case with 100% coverage for specified function.
Update readme, validated doctoc

Please let me know what you think, especially the intended behavior for removing zeroes both in front and back, as well as the function name if there's better idea.
Good day.

Sorry, I'll reopen new one again during Hacktoberfest.
I just find out that submission must be from 1 October.


adding the modifyProps helper method to core

this adds the modifyProps method for merging props and fallback props within VictoryComponents. helps support theme usage.
https://github.com/FormidableLabs/victory-chart/pull/242
@boygirl

@ebrillhart :+1: you can release this as a patch


Metrics

Description
Initial script for display of calendar-style monthly heatmap for user metrics
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Change Status

[x] Incomplete/work-in-progress, PR is for discussion/feedback

Checklist

[ x] My code follows the style guidelines of this project
[ x] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[ x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] There are no merge conflicts

Please review and leave comments - I will have to delete this branch w/o merging and create it again with new local changes due to the unintentional inclusion of commits to other files


Update dylan.tmLanguage.json

I think this fixes issue #4

This looks like it fixes the problem I saw.

I can also confirm this fix worked for me


Fixed german translation issues

I fixed the issue mentioned in #429 .
Just compare the screenshots below :)

will clone staging to resolve the conflicts and open a new PR.


Licenses not being picked up correctly

gimie data 'https://github.com/facebookresearch/co-tracker' --format 'json-ld'
returns, among other triples:
"http://schema.org/license": [
{
"@id": "https://spdx.org/licenses/NOASSERTION"
}
I'm not aware of such a license, nor is spdx. In any case, if it believes there is no license, I would not expect a triple at all... Maybe we can put in an exception? Right now there is a if data["licenseInfo"] is not None:  But I guess that doesn't help if gitHub returns some sort of "NOASSERTION".
Not sure why our license grabber is having a hard time with this one, the license.md file clearly states:
Attribution-NonCommercial 4.0 International at the top of page :confused:

Will try to program an exception around this:
Preferably: If NOASSERTION -> Return some kind of "catch all" license if that exists.
Otherwise, NOASSERTION should = None, so that no triple is returned in the case that no license was matched.

https://github.com/SDSC-ORD/gimie/pull/66


Rename dimensions stated in the #define to end with an underscore in all solvers

The solvers for "LaxMPC" and "EquMPC" now use nn_. mm_, etc. to indicate the dimensions used by the solver. That is, these #defines end with a _. All solvers for all MPC formulations should be updated to follow this convention.

This is fixed as of release 'v0.3.10' (bb8406630ea952b0b5ba63e180d0030f91e8390c).