Add location listing

Copy something like the ARD listing view and modify to meet our needs.

Fixed in upcoming commit


World became inaccessable after inserting a resource pack sound into a sound listener

After inserting "minecraft:sfx.error", my resource pack custom sound, into a sound listener, the game crashed the second it was activated and kept crashing at every subsequent attempt at loading the world. I fixed it by removing the sound listener with an external program (in my case, Amulet. MCEdit crashes too)
Crash Logs.txt (Crash logs are separated by lines)

It looks like the sounds identifier wasn't found in the sound registry, resulting in a nullref (this will be fixed)
Are you absolutely sure that the sound was added and loaded correctly ? If it was, it should appear in /playsounds tab-complete

Yes, there's a point in the map where that sound is played through a command block and I have used to multiple times

I'll try looking into it further; hopefully I can figure that out and fix it for the next update

Also a room with that listener is no longer a room I suppose? Everything in the room reset and when I trying to size the room back to where it was, it said that "nothing is focused with a tag 'room' "

alright, figured it out. I was loading sounds improperly, meaning custom resourcepack sounds couldn't ever have worked.. and since I just kinda assumed that if normal sounds work, resourcepack sounds should work as well, I didn't think to test that specifically. I'm very sorry for the inconvenience- It'll be fixed in the next update though

nothing is focused with a tag 'room'
That kinda sounds like it could be a desyncing issue; usually either rejoining the world, or worst case restarting the game should fix that, unless it's caused by something different I'm unaware of


Feature/design v2

The new design!!!!

@pitpalme Here is a summary of the biggest changes we've made:

Add libsass in the requirements.txt to compile sass (add a manage command to compile)
Get rid of bootstrap
Bring the styles to sass files (main.sass includes all others and gets compiled)
Style the page like the new design
Add Bourbon (very lightweight sass mixin library, that helps us take care of any browser prefixes http://bourbon.io/)
Add responsive-nav (small cross-browser js/css library for a nav that collapses to a hamburger menu)

Ok, @pitpalme I believe this branch is ready to be merged. Of course there are a lot of TODOs like making the query work correctly, displaying the correct messages and so on, but design-wise, it's done.
I might have some time this week in the evenings, ping me if you need more CSS / layout stuff to be done!


[BUG] Observing repilca on new IM-r before upgrading of volume

Describe the bug (🐛 if you encounter this issue)
The volumes which are created with previous version appears with the latest version of IM-r before upgrade of volume was triggered.
To Reproduce
Steps to reproduce the behavior:

Install Longhorn v1.3.2
Create volumes, attach to pods and write data into them.
Upgrade Longhorn v1.3.3-rc2 with Automatic Engine Upgrade disabled. Don't upgrade the volumes
Check the volumes, they are on old engine IM but on new replica IM.

Expected behavior
IM-e and IM-r should be updated only after the volumes are upgraded.
Log or Support bundle

[longhorn-support-bundle_5956057a-fd8d-4084-9021-3e0eb221bb8c_2023-04-08T07-41-05Z.zip](https://github.com/longhorn/longhorn/files/11182765/longhorn-support-bundle_5956057a-fd8d-4084-9021-3e0eb221bb8c_2023-04-08T07-41-05Z.zip)
Environment

Longhorn version: v1.3.3-rc2
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: K3s v1.24.6

Number of management node in the cluster: 1
Number of worker node in the cluster: 3

Additional context
I did cordoned the nodes few times.

IM-e and IM-r should be updated only after the volumes are upgraded.

@derekbit @shuo-wu @PhanLe1010  is this true? I thought replicas will be always upgraded except engine process except we upgrade engine.

@c3y1huang can u help check this issue? Thanks.

It is unexpected that replicas move to the new instance managers without engine live upgrade. Lets' me check the reproducing steps.

From the log bundle, let's consider the replica bi-1-r-14652922 currently running on the new instance-manager-r instance-manager-r-eda6de98a40a5bd739f564ebe25858a8:

The new instance manager instance-manager-r-eda6de98a40a5bd739f564ebe25858a8 was created at 2023-04-08T07:29:49Z
There is a replica rebuilding at 2023-04-08T07:37:58Z  objectmeta:
    name: bi-1-e-36af5e7f.1753e58cc64de443
    generatename: ""
    namespace: longhorn-system
    creationtimestamp: "2023-04-08T07:37:58Z"
  involvedobject:
    kind: Engine
    namespace: longhorn-system
    name: bi-1-e-36af5e7f
  reason: Rebuilding
  message: Detected rebuilding replica bi-1-r-14652922 (<IP_ADDRESS>:10000)

It means that after the Longhorn upgrade, one the replica was crashed. As the result, it was recreated on the new instance manager because at this moment the default instance manger is the newer version.
Same thing happens to the replica bi-1-r-86e3375d.
The replica bi-1-r-434db62a didn't crash so it remains on the old replica instance manager
I retried the reproducing step without trigger replica rebuild, the replicas remains in the old instance manager pods
So the behavior is expected.


extension activating

[ ]

Issue Type: Performance Issue

when i run any extenion there pop a error activating extenstion
VS Code version: Code 1.50.1 (d2e414d9e4239a252d1ab117bd7067f125afd80a, 2020-10-13T15:06:15.712Z)
OS version: Windows_NT x64 6.1.7600

Process Info

Extensions (3)

Extension
Author (truncated)
Version

shell
bbe
0.3.0

live-code-runner
lab
4.5.0

cpptools
ms-
1.0.1

That is a normal notification, but it shouldn't remain indefinitely. I suggest you try disabling each of your extensions in turn and restarting VS Code each time to find out which one is causing the problem.

/duplicate https://github.com/microsoft/vscode/issues/108988


Refactor the modal system

Description
Currently, if you look through the index.html, you will see that there are all modals we use at the same time present there, which complicates the HTML structure a lot. While only a few of them should be present at all times, like serverReload modal, which can happen at any time. All others are very situational and could be loaded when needed, based on user actions.
The plan is to create a central modal service, which will operate and load requested modals with ng-include and ng-controller.

Should the autofocus feature be a part of the modal framework (the autofocus input ID should be provided during modal creation) or just inserted into each modal component separately on demand?

A working modal framework was created, now the existing modals should be refactored to use it:

[ ] Restart interpreter
[ ] Delete interpreter
[ ] Update interpreter
[ ] Empty interpreter name
[ ] Empty interpreter group
[ ] Interpreter exists
[ ] Job modal: run all
[ ] Job modal: stop all
[ ] Notebook clear
[ ] Notebook clone
[ ] Notebook commit
[ ] Notebook create
[ ] Notebook delete
[ ] Folder delete
[ ] Paragraph delete
[ ] Delete all warning
[ ] Notebook export
[ ] Notebook import
[ ] Save notebook permissions
[ ] Switch to personal mode
[ ] Switch to collab mode
[ ] Notebook permissions have empty fields
[ ] Discard permissions
[ ] Permissions reminder
[ ] Notebook rename
[ ] Merge folders
[ ] Run all paragraphs
[ ] Run all below
[ ] Run all above
[ ] Server reload

To implement server reload modal, the new modal framework should implement optional "non-closable" feature.

In the subject of multiple modals in one component:
Only the HTML file for now will be split. The modal framework will be provided with different ng-include path to htmls, but same controller name, since currently one controller is working with several modal (example: job modals)

Suggestion: refactor simple modals into a one configurable component.
Several modals in the project have the repeating structure: it is just a warning/information/confirmation window with title, text and button. However, even these simplest modals have their own separate controller and service each. These can be refactored into one universal modal, which will display provided title, text and has one callback to proceed after button is pushed. This will reduce code duplication, the amount of components registered in the system, but will reduce customization possibilities for each individual modal of that type and implementation will become slightly more bulky on the initialization phase. More code will be moved to JS side from HTML.

Status: first iteration of the refactoring is complete with unit tests.  If one user is working with notebook, there is no need for these confirmations.


Feat:empty cart, checkout, continue shopping display twicely

Describe the feature
Empty cart, checkout, continue shopping display twicely
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hello @Anushkabh please assign this issue to me under gssoc 24


green packaging: bundle based on environment variable

Requires Green Packaging
Need to package bundles based on Environment variables. Results in separation of additional functionality for Dev and least core package for Prod.

Dev package includes propTypes, Error Handling checks, Loggers and devtool extensions and integration code for Upcoming standalone Rootz Devtools.
Prod package would consists of core functionalities only, excluding above mentions.

fixed in v2.2.0. Closing the issue


**$$(NEW-UPDATE)Latest,,!!The Ultimate V Bucks Generator 2024-2025 A Complete Review { JWERTY}

)^(NEW-UPDATE)!!The Ultimate V Bucks Generator 2024-2025 A Complete Review [ gzm8]
EXPOSED: The Ultimate Free V-Bucks Generator that Will Make You a Fortnite Millionaire Overnight!   Well, fear not, because we've got the solution you've been searching for!
Introducing the revolutionary Free V-Bucks Generator that is taking the gaming world by storm.  Say goodbye to spending your hard-earned cash on V-Bucks packs – with this generator, you'll never have to worry about running out of virtual currency again.
But wait, it gets even better! Not only will you be able to unlock all the latest skins, emotes, and accessories, but you'll also be able to level up your Battle Pass faster than ever before. Imagine being able to reach Tier 100 in no time at all, all thanks to the magic of the Free V-Bucks Generator.
And the best part? This generator is 100% safe and secure, so you can rest easy knowing that your account will never be compromised. No more worrying about getting banned or having your progress reset – with this tool, you can enjoy all the benefits of free V-Bucks without any of the risks.
So what are you waiting for?  Click the link below to access the Free V-Bucks Generator and start dominating the battlefield today.


How to set MAGMOM tag for different magnetization angles theta and phi

Dear Experts,
I am doing calculations with a magnetic material at different magnetization directions on theta=0 and phi changing from 0,90,45,60,30.
As far i understand, 0,0 angles are describing MAGMOM tag in 0 0 1 direction and 0,90 is for MAGMOM direction 1 0 0.
How can I set the MAGMOM tag for other angles?
Any suggestion or help can solve my problem.

MAGMOM contains 3 numbers for each atom, which specifies mx, my and mz, i.e. the moment components in each direction. If your default global moment axis is rotated, you need to specify mx, my and mz in the original cartesian coordinates.

Thank you very much for your reply.
For all other users, working outside VASP, I find the following link very helpful.
https://www.vasp.at/wiki/index.php/SAXIS


FcmSharp.Requests.Notification missing fields

Hi
With reference to https://firebase.google.com/docs/cloud-messaging/http-server-ref#notification-payload-support would it be possible to add a "sound" property to the FcmSharp.Requests.Notification message?

FcmSharp supports two protocols. The old versions below 2.0 use the Legacy HTTP API you are refering to. The versions from 2.0 on are based on the new v1 protocol (https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages), which has objects like AndroidNotification:  https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages#AndroidNotification. This object contains the sound property.


Fix WatchObject to test predicates on initial GET

This issue was causing the wrong error message in cases where no events ae received after the initial GET.

/lgtm
/approve


Stop using the welcome-screen USB APIs on Windows

We have Change the initial screen so it doesn't offer the USB option.
So, we can drop USB API corresponding Electron code.

Verified with Endless Key app <IP_ADDRESS>.


Don't allow to create two service-offer with the same name ("connector href")

Having multiple offers for the same cloud infrastructure (connector) is allowed and expected.  The offers for a particular cloud infrastructure may differ by flavor, price, SLAs or other characteristics.  The UI needs to render multiple offers sensibly.


Theme settings do not follow the currently set theme

Ironic.

This is not a bug, this is intentional


Edit debug mode attention for new version Werkzeug

Starting from Werkzeug 0.11, the debugger was protected by a PIN.

The wording of this is more awkward than the original.

Is it better now?

Thanks, but I don't find this more useful. The original statement was about how code execution was possible even though the interface itself wasn't useful in production deployments.


"Runtime error processing wasm" when using std::to_string

I'm not sure if I should post this in eosio repo or here, but since I don't see this issue when compiling with the old eosiocpp, I decided to post here.
This modified hello example program reproduces the issue for me:
#include <eosiolib/eosio.hpp>
#include <string>

using namespace eosio;
class hello : public eosio::contract {
  public:
      using contract::contract;

      /// @abi action
      void hi( account_name user, uint64_t i ) {
         std::string str = std::to_string(i);
         print( "Hello, ", name{user});
      }
};

EOSIO_ABI( hello, (hi) )

It compiles fine with this command:
eosio-cpp -o hello.wasm hello.cpp

Sending this action fails and produces this error in the nodeos log:
2018-08-28T15:00:23.226 thread-0   http_plugin.cpp:476           handle_exception     ] Exception Details: 3070002 wasm_execution_error: Runtime Error Processing WASM
final > memory:<PHONE_NUMBER>3709551520 > 65536
    {}
    thread-0  binaryen.hpp:76 trap
pending console output:
    {"console":""}
    thread-0  apply_context.cpp:61 exec_one

Like I already said, compiling the old way, with eosiocpp does not produce this error. And if I don't call std::to_string it works fine as well. So something happens in std::to_string.
Would be good, if someone tried to reproduce. I didn't run the standard build.sh script, to build, because my OS is not supported (Arch linux).
I'm running eosio.wasmsdk v1.1.1 and eosio v1.1.6.

The size explosion from adding std::to_string is expected.  Pulling in standard library functions in general will add a lot to a contract, especially the string manipulation/handling functions.  I don't know why you were going to use to_string in your contract, but as a general design choice you should not be doing any string manipulations, they are very expensive.  As for the reference to the old toolchain, when I compiled this it was smaller because it wasn't linking parts that it needs to function correctly, at least it failed when I actually used that variable.

So that error says that wasm is too big? And you're saying that when you compiled with the old toolchain, it was smaller? Well, for me it is bigger by more than a kilobyte. eosio-cpp compiled version is almost 21kB, whereas eosiocpp version is more than 22kB.

Thanks. Arch linux is rolling release, so I'm not sure what to answer to this question. hello.wasm - compiled with eosio-cpp.
hello1.wasm - compiled with eosiocpp


descendantFocusability="afterDescendants" isn't working

I'm trying to have a button on my items that should handle clicks on it, and consume the event.
Seems like that the touch-event is getting to the ItemTouchListenerAdapter no matter what I do, moreover, seems like that descendantFocusability isn't working and I'm seeing the onItemClick being called before my OnClick method (preventing me from simply ignoring the onItemClick)
Any ideas?

Does it get fine if you do not use ItemTouchListenerAdapter in URV?

If I'm using ItemTouchListenerAdapter I'll get the onItemClick() method called, and then my button's OnClick() called.
When not using ItemTouchListenerAdapter only the button's OnClick() listener gets called, since there's no listener on the entire row touch event.
I would expect it to only call my OnClick listener when touching the button, and the onItemClick when touching the rest of the row.
Currently I have an ugly workaround, where I pass the MotionEvent itself to my OnItemClick, and in it I do the following:
View btn = view.findViewById(R.id.menu);
btn.getGlobalVisibleRect(rect);
if (rect.contains((int) e.getRawX(), (int) e.getRawY())) {
// button was clicked
} else {
// row was clicked
}

So each item cannot have a button with its own OnClickListener?


Code formatter path matching

Title: Code formatter path matching
Description:
The code formatter performs unexpected behavior when provided paths that either do not start with ./ or contain a trailing / due to lack of path normalization. When the formatter is run with arguments that do not meet these requirements, the formatter attempts to run on files that are explicitly excluded.
Repro steps:
Navigate to the root of the envoy project and run either of the following commands:
# Incorrect behavior due to trailing slash
./tools/code_format/check_format.py fix './source/server/admin/'
# Incorrect behavior due to lack of leading ./
./tools/code_format/check_format.py fix 'source/server/admin'

Both commands output ERROR messages regarding the use of std::regex in files excluded in the script by STD_REGEX_ALLOWLIST. Instead the formatter should interpret the paths given and put them into a standard form before proceeding to check for matches against excluded files.
Sample Command & Output:
$ ./tools/code_format/check_format.py fix 'source/server/admin'

ERROR: From source/server/admin/utils.h
ERROR: source/server/admin/utils.h:22: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: From source/server/admin/stats_handler.cc
ERROR: source/server/admin/stats_handler.cc:83: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: source/server/admin/stats_handler.cc:143: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: source/server/admin/stats_handler.cc:177: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: source/server/admin/stats_handler.cc:203: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: From source/server/admin/utils.cc
ERROR: source/server/admin/utils.cc:43: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: source/server/admin/utils.cc:47: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: source/server/admin/utils.cc:49: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: From source/server/admin/prometheus_stats.cc
ERROR: source/server/admin/prometheus_stats.cc:52: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: source/server/admin/prometheus_stats.cc:54: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: source/server/admin/prometheus_stats.cc:83: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: source/server/admin/prometheus_stats.cc:259: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: From source/server/admin/prometheus_stats.h
ERROR: source/server/admin/prometheus_stats.h:30: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: From source/server/admin/stats_handler.h
ERROR: source/server/admin/stats_handler.h:53: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: source/server/admin/stats_handler.h:55: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: source/server/admin/stats_handler.h:63: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: source/server/admin/stats_handler.h:69: Don't use std::regex in code that handles untrusted input. Use RegexMatcher
ERROR: check format failed. run 'tools/code_format/check_format.py fix'

cc @phlax

@DavidPeet8 as a general context i am gradually refactoring envoy's ci/linting tools - this one is on the agenda, but not imminent
wrt to the specific problem that you raise, im not too keen on making any changes to the script myself, but i will happily review a PR to address this issue

/assign


VSCode cannot open Unity C# project

VSCode Version: 1.39.2
OS Version: Windows 10.0.18362 Build 18362

Steps to Reproduce:

Attempt to open C# file from Unity by double clicking on a file
Observe the "thinking" wheel by the cursor for a moment, but VSCode does not launch.

Alternatively:

Open VSCode
Attempt to open Unity C# project by using File -> Open Recent -> {Project Name}
Nothing happens

Alternatively:

Open VSCode
Attempt to open Unity C# project by using File -> Open Folder -> {Project Top Level Directory}
Nothing happens

Alternatively:

Open VSCode
Attempt to open Unity C# project by clicking on the project name in Recent list on Welcome page
Nothing happens

Alternatively:

Open Powershell
Execute code {project-directory}
Command executes, VSCode does not open

Alternatively:

Open Powershell
Execute code --disable-extension {project-directory}
Command executes, VSCode does not open

Does this issue occur when all extensions are disabled?: Yes

I'm able to open folders nested within the project's main directory and then open C# scripts that way way, however there is no Intellisense, error highlighting, linting, etc.

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

@bpasero looking good in the latest insider! Apologies on not testing before opening the issue, but was frustrated on my Saturday. 🍻


Update nf icons in welcome-screen.lua

remove malfunction nerdfonts (icons deleted)

Thank you very much for your contribution, I was wondering what happened to those icons.


add time zone support

To implement Django's Time Zone support, I think JSON Date objects will have to be stored in MongoDB instead of strings. This will make implementing date lookups easier, however, a disadvantage of JSON Date objects is that the finest resolution they support is millisecond, not microsecond.

I propose we store dates as BSON dates even though this type only support milliseconds. From the Django docs:

When support for time zones is enabled, Django stores datetime information in UTC in the database, uses time-zone-aware datetime objects internally, and translates them to the end user’s time zone in templates and forms.

This is the same as a pymongo/MongoDB app; we use and return time-zone-aware datetime objects to the user but only send UTC to the database.


Allow to accept the options as an element attribute

Like there is moment-picker="myDate" can there be the moment-picker-options="{ locale:         'en',
format:         'L LTS',
minView:        'decade',
maxView:        'minute',
startView:      'year',
autoclose:      true,}"

Hi @dhiman252, this could be an interesting feature, but I think that should be more powerful for each user to create its own angular Component, in order to configure several set of datepickers as they want.
You can take inspiration on this comment or just use Moment Picker Provider if you have just configuration for all your pickers.
Thanks :)


Setting time period broken in Isolate transform

It works when you set the time period and then reload the page. But this is very annoying indeed.
Thanks for your massive work improving tessera these days !

Yeah, I've internalized the workaround so I immediately hit command-R after selecting the time range :smile: But obviously, it'd be better if it worked again.

I've been investigating this morning - I initially assumed this was a data loading problem, but it turns out it's some kind of redraw problem in  the flot and 'nvd3' renderers. The query is being reloaded properly with the changed range, and the summation table updates correctly. So does the chart if using the graphite renderer.

D'oh!  Fixed.


we can define any number which is not in our enum.

Bug Report
we expect not to be able to define a role number which is not in our enum, but we can :|
enum Role {
    ADMIN,
    AUTHOR
}

interface User {
    role: Role
}

const user1: User = {
    role: 1234
}

🙁 Actual behavior
Compiles with out any Error.
🙂 Expected behavior
Type 'number' is not assignable to type 'Role'.
Different behavior with String
but this code gives us correct error message:

Type '"c"' is not assignable to type 'Role'.

enum Role {
    ADMIN = 'a',
    AUTHOR = 'b'
}

interface User {
    role: Role
}

const user1: User = {
    role: 'c'
}

Duplicate of #26362, which provides plenty of reasoning for this behaviour. Used search terms: enum number in:title


rework usage of randomness in Dhcp_client

rework usage of randomness in Dhcp_client
Dhcp_client.create used to call into Stdlibrandom (provided by mirage-random <=1.1.0).
Dhcp_client_lwt already depends on Mirage libraries, I added the Mirage_random.C signature, and provide the random xid, if necessary, in Dhcp_client_lwt.
see https://github.com/mirage/mirage/pull/938 for changes in mirage

Thanks for the opam file maintenance as well as the changes here. :)


Dependencies missing

Well, this server is hard to run due dependencies are obsolete and some of system dependencies missing.
After many many bugs to be fixed it ends with error if started as root for electron package.
Is project still alive?
Looks cool :)

Hey, sorry.  This project is exceptionally old now and I'm not surprised dependencies are missing, etc.  It's a good project to look to see how we solved various IMAP issues and for educational usage, but not suitable for actually running as an email client.


Improve JSON format prompt for large chunks & Handle ZeroDivisionError

Description
In this PR there are three different changes
Changes

Fixed a Typo in the filter_question_prompt Instruction from Asses to Assess
Added a try-except block for handling ZeroDivisionError for the filter method in the NodeFilter class
Improved the JSON_FORMAT_INSTRUCTIONS for better output generation
It seems like the LLM sometimes loses track of the imposed instruction for the output, especially for long prompts. So although the output generated for a chunk_size of 512 is perfect, the output for a chunk_size of 1024 has an extra newline. Here parsing fails when using PydanticOutputParser even though the llm has generated an output and there is only an extra '\n' as shown in the instances below.

But by tuning the prompt and adding Please output your response in the demanded json format. at the end of the instruction we get output without '\n'. This output can then be parsed and the context can be considered.

@shahules786 could you check if we can merge this in?

hey @Manav916 we did make some improvements with the v0.2 release - do check it out
closing this for now but I'm really sorry we couldn't merge it 🙁 but at the same time thanks a million for taking the time to raise this, really grateful too and do checkout this form https://docs.google.com/forms/d/e/1FAIpQLSdM9FrrZrnpByG4XxuTbcAB-zn-Z7i_a7CsMkgBVOWQjRJckg/viewform - our way of saying thank you 🙂


Falco versions other than 0.17.1 fail to launch Amazon Linux 2

What happened:
Falco containers using versions other than 0.17.1 (tested with 0.17.0 and 0.18.0) immediately crash because the kernel module can't be downloaded.
Logs from falco container:
* Setting up /usr/src links from host
* Unloading falco-probe, if present
* Running dkms install for falco
Error! echo
Your kernel headers for kernel 4.14.146-119.123.amzn2.x86_64 cannot be found at
/lib/modules/4.14.146-119.123.amzn2.x86_64/build or /lib/modules/4.14.146-119.123.amzn2.x86_64/source.
* Running dkms build failed, couldn't find /var/lib/dkms/falco/0.17.0/build/make.log
* Trying to load a system falco-probe, if present
* Trying to find precompiled falco-probe for 4.14.146-119.123.amzn2.x86_64
Found kernel config at /host/boot/config-4.14.146-119.123.amzn2.x86_64
* Trying to download precompiled module from https://s3.amazonaws.com/download.draios.com/stable/sysdig-probe-binaries/falco-probe-0.17.0-x86_64-4.14.146-119.123.amzn2.x86_64-2a8e59358e4477733a8a706f1784f316.ko
curl: (22) The requested URL returned error: 404 Not Found
Download failed, consider compiling your own falco-probe and loading it or getting in touch with the sysdig community
Tue Nov  5 20:12:11 2019: Falco initialized with configuration file /etc/falco/falco.yaml
Tue Nov  5 20:12:11 2019: Loading rules from file /etc/falco/falco_rules.yaml:
Tue Nov  5 20:12:12 2019: Loading rules from file /etc/falco/falco_rules.local.yaml:
Tue Nov  5 20:12:12 2019: Unable to load the driver. Exiting.
Tue Nov  5 20:12:12 2019: Runtime error: error opening device /host/dev/falco0. Make sure you have root credentials and that the falco-probe module is loaded.. Exiting.

What you expected to happen:
The falco module should have been built or
The pre-built module should exist at https://s3.amazonaws.com/download.draios.com/stable/sysdig-probe-binaries/falco-probe-FALCO_VERSION-x86_64-4.14.146-119.123.amzn2.x86_64-2a8e59358e4477733a8a706f1784f316.ko for versions other than 0.17.1
Log output for version 0.17.1:
* Setting up /usr/src links from host
* Unloading falco-probe, if present
* Running dkms install for falco
Error! echo
Your kernel headers for kernel 4.14.146-119.123.amzn2.x86_64 cannot be found at
/lib/modules/4.14.146-119.123.amzn2.x86_64/build or /lib/modules/4.14.146-119.123.amzn2.x86_64/source.
* Running dkms build failed, couldn't find /var/lib/dkms/falco/0.17.1/build/make.log
* Trying to load a system falco-probe, if present
* Trying to find precompiled falco-probe for 4.14.146-119.123.amzn2.x86_64
Found kernel config at /host/boot/config-4.14.146-119.123.amzn2.x86_64
* Trying to download precompiled module from https://s3.amazonaws.com/download.draios.com/stable/sysdig-probe-binaries/falco-probe-0.17.1-x86_64-4.14.146-119.123.amzn2.x86_64-2a8e59358e4477733a8a706f1784f316.ko
Download succeeded, loading module
Tue Nov  5 20:31:06 2019: Falco initialized with configuration file /etc/falco/falco.yaml
Tue Nov  5 20:31:06 2019: Loading rules from file /etc/falco/falco_rules.yaml:
Tue Nov  5 20:31:07 2019: Loading rules from file /etc/falco/falco_rules.local.yaml:
...

How to reproduce it (as minimally and precisely as possible):
Launch Falco container in an EKS cluster or Amazon EKS-Optimized Linux AMI instance using image falcosecurity/falco:0.18.0 or falcosecurity/falco:0.17.0
Anything else we need to know?:
This is a similar issue to #912 but building the module doesn't work because the headers don't seem to be present, necessitating using a precompiled module.
Environment:

Falco version (use falco --version): 0.17.0 and 0.18.0
Cloud provider or hardware configuration: AWS
OS (e.g: cat /etc/os-release): Amazon EKS-Optimized Linux AMI (Amazon Linux 2 based)
Kernel (e.g. uname -a): 4.14.146-119.123.amzn2.x86_64
Install tools (e.g. in kubernetes, rpm, deb, from source): AWS EKS
Kubernetes version: 1.12
AMI ID: ami-0ee9e136178176e29

/triage support

@kris-nova  , @fntlnz , @leodido ,
I see that there are repeatedly more issues related to pre-compiled Falco Probe KO files in https://s3.amazonaws.com/download.draios.com/stable/sysdig-probe-binaries/index.html in every Falco release.
I think it is better for us if we can build the required ko files on our own for kernels we use.
Can you please point me to the document/code which provides steps to build the .ko files ?

@fntlnz - was just on a call and we are running into this, seems related to what was fixed before with https://github.com/falcosecurity/falco/issues/846

@karthikc911 - I agree that building your own kernel module is the best solution in general.
Building the module from source is documented here, be careful to look at the previous steps, not just make driver.
@frankreno In general the precompiled modules are a subset of what's available out there. We are in the process of making the build script and infrastructure to other contributors out there so that one can just make a PR to add support for a new kernel. Follow more here https://github.com/falcosecurity/test-infra/issues/53

Hi All, a fix for this has been found and will be merged soon, but in the meanwhile, the falco probe for the latest falco version has been uploaded.
upload: output/falco-probe-0.18.0-x86_64-4.14.146-119.123.amzn2.x86_64-2a8e59358e4477733a8a706f1784f316.ko to s3://download.draios.com/stable/sysdig-probe-binaries/falco-probe-0.18.0-x86_64-4.14.146-119.123.amzn2.x86_64-2a8e59358e4477733a8a706f1784f316.ko

@jrobersonaquent ,
I have uploaded the pre-compiled falco kernel modules of falco versions 0.17.0 , 0.17.1 , 0.18.0 for amazon Linux 2 OS to S3 Bucket : https://falco-kernel-modules.s3-us-west-1.amazonaws.com/ .
I have tested all the ko files and everything seems to be working as expected. You can directly use these files with respective falco docker image.
@fntlnz , @krishnan-ramkumar  : We use Amazon Linux 2 AMI for running Kubernetes Clusters. Hence I will be building Falco KO files for latest 3 versions of Falco each time there is a newer kernel version. How can I upload these files to Falco S3 Bucket ? (https://s3.amazonaws.com/download.draios.com/stable/sysdig-probe-binaries/index.html).


Add missing docstrings to fablib module

Resolves #319.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
6 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.008%) to 17.585%

Files with Coverage Reduction
New Missed Lines
%

fabrictestbed_extensions/fablib/fablib.py
6
21.55%

Totals

Change from base Build<PHONE_NUMBER>1:
0.008%

Covered Lines:
1385

Relevant Lines:
5677

💛  - Coveralls


refactor(api): simplify SynchronousAdapter so that it doesn't wrap objects

Overview
The opentrons.hardware_control.adapters.SynchronousAdapter class exists for two purposes:

To allow synchronous interfaces, like the v2 ProtocolContext, to call asynchronous interfaces like the HardwareControlAPI and friends synchronously
To ensure those synchronous calls are run in the Hardware Control dedicated thread, managed by the ThreadManager

It accomplishes this by:

Wrapping up an object with asynchronous methods
Intercepting any calls to that object and sending them through asyncio.run_coroutine_threadsafe

So, a caller (like the ProtocolContext) will be given a HardwareControlAPI object wrapped up in a SynchronousAdapter rather than an actual HardwareControlAPI. This has the following downsides:

Type checking information is completely erased

To some extent, this reduces system safety
It hampers the DX (developer experience) when working in important objects like the ProtocolContext

If some method of the wrapped object returns another asynchronous class instance, that instance then needs to be wrapped in its own SynchronousAdapter

For example: the ProtocolContext must get attached module objects from the HardwareControlAPI and then wrap each of them up in a SynchronousAdapter

This RFC proposes an evolution of the SynchronousAdapter interface to avoid these pitfalls and exchange them for smaller ones.
Proposal
Create a SynchronousAdapter class that takes a loop and gives you an object with a call_sync method.
import asyncio
from typing import Any, Callable, Coroutine, TypeVar
from typing_extensions import ParamSpec

AsyncParamsT = ParamSpec("AsyncParamsT")
AsyncReturnT = TypeVar("AsyncReturnT")

class SynchronousAdapter:
    """An adapter to allow asynchronous function to be called synchronously.

    Args:
        loop: The event loop to run the asynchronous function in.
    """
    def __init__(self, loop: asyncio.AbstractEventLoop) -> None:
        self._loop = loop

    def call_sync(
        self,
        func: Callable[AsyncParamsT, Coroutine[Any, Any, AsyncReturnT]],
        *args: AsyncParamsT.args,
        **kwargs: AsyncParamsT.kwargs,
    ) -> AsyncReturnT:
        return asyncio.run_coroutine_threadsafe(
            func(*args, **kwargs)
            loop=self._loop,
        )

From there, add a method to the ThreadManager to get a SyncAdapter using the managed thread/loop:
class ThreadManager:
    ...
    def create_sync_adapter(self) -> SynchronousAdapter:
        return SynchronousAdapter(loop=self._loop)

Where anything is expecting a SynchronousAdapter[SomethingT], change it to depend on a SynchronousAdapter and a SomethingT. So, taking ProtocolContextImplementation as an example:
class ProtocolContextImplementation(AbstractProtocol):
    def __init__(
        self,
        sync_adapter: SynchronousAdapter,
        hardware: HardwareControlAPI,
        api_version: Optional[APIVersion] = None,
        bundled_labware: Dict[str, LabwareDefinition] = None,
        bundled_data: Dict[str, bytes] = None,
        extra_labware: Dict[str, LabwareDefinition] = None,
    ) -> None:
        ...

    def delay(self, seconds: float, msg: Optional[str]) -> None:
        """Delay execution for x seconds."""
        self._sync_adapter.call_sync(self._hardware.delay, seconds=seconds)

Upsides

Explicit interface rather than implicit interface
Typing information preserved
DX stuff like cmd+click to jump to definition and docstrings on tooltips works in editors like VSCode and PyCharm
The type signatures of module contexts will no longer be a lie that has to be # type: ignore'd
Since SynchronousAdapter only does one thing, alternative implementations can be explored and prototyped

For example, a cross-process ZMQ-based adapter

Downsides

More (keyboard) typing 🙃
Increased risk of doing self._hardware.whatever() without wrapping it in self._sync_adapter.call_sync

Mitigation: if there are unit tests covering the method in question, this mistake will raise errors/warnings
Mitigation: newer versions of mypy can also warn against some variants of this

This makes a ton of sense and will be a great improvement - so glad ParamSpec exists now.
Quite honestly a similar thing should happen with the ThreadManager.

Talked about this with @sfoster1 and we agree that this is a good move. Marking this ticket as a refactor ticket and removing the RFC label

Proposal to make this change in advance of ParamSpec support. I think longer term, the proposal in the original ticket is more flexible and readable, but in the mean time, this should work equivalently:
import asyncio
from typing import Any, Coroutine, TypeVar

AsyncReturnT = TypeVar("AsyncReturnT")

class SynchronousAdapter:
    """An adapter to allow asynchronous function to be called synchronously.

    Args:
        loop: The event loop to run the asynchronous function in.
    """
    def __init__(self, loop: asyncio.AbstractEventLoop) -> None:
        self._loop = loop

    def call_sync(self, coro: Coroutine[Any, Any, AsyncReturnT]) -> AsyncReturnT:
        return asyncio.run_coroutine_threadsafe(coro, loop=self._loop)

class ProtocolContextImplementation(AbstractProtocol):
    def __init__(
        self,
        sync_adapter: SynchronousAdapter,
        hardware: HardwareControlAPI,
        api_version: Optional[APIVersion] = None,
        bundled_labware: Dict[str, LabwareDefinition] = None,
        bundled_data: Dict[str, bytes] = None,
        extra_labware: Dict[str, LabwareDefinition] = None,
    ) -> None:
        ...

    def delay(self, seconds: float, msg: Optional[str]) -> None:
        """Delay execution for x seconds."""
        self._sync_adapter.call_sync(self._hardware.delay(seconds))


Implements RS TCK

This PR implements TCK similar to the https://github.com/reactive-streams/reactive-streams-jvm/tree/master/tck one

@OlegDokuka It would be useful to get a summary of in what aspects it deviates from the JVM TCK, would that be possible to write up, Oleg?

@OlegDokuka It would be useful to get a summary of in what aspects it deviates from the JVM TCK, would that be possible to write up, Oleg?

Yes. Let me finalize the PR and I will do.summary here


Add explicit Numpy imports to docstring

There were no explicit imports for Numpy in these docstrings, which made them incomplete.

Thank you for your desire to contribute to scipy. In the case of all the scipy docstrings it's assumed that numpy has already been imported as import numpy as np.


AWS Lambda Doc Screen Shots are out dated

Description:
$subject
https://apim.docs.wso2.com/en/next/tutorials/create-and-publish-awslambda-api/
Eg:- API Dropdown, Create API


Where did the 2.0.2 hide?

I published a new version recently, but I couldn't publish 2.0.2 because it was already taken. There is no tag for 2.0.2. I can't find it, so I published 2.0.3 and all's well. But I feel like we should tag the 2.0.2 on the right commit or unpublish 2.0.2
I couldn't find the commit that was published as 2.0.2. That's the magic of DVCS ;)

Maybe I can help (if I understood the question correctly):
7d3d5b5
In case I am not correct, some more detail on how I tried to find out, maybe it helps you looking
("magic of DVCS" reminded me of something I read on a mailing list a while ago):
This SO answer has a small shell script that finds git blobs that contain the exact version of a file.
I did npm i<EMAIL_ADDRESS>and ran the script against the index.html. Results: f7a4a45, 7d3d5b5 and eccc209.

7d3d5b5 is where I bumped the version number thinking it's free. After that I published to npm and got a reject saying the version exists.
To me it looks like 2.0.2 was tagged at some point before that and released without pushing the tag. Seems like all changes except the tag and version bump are in the repo.
Anyway, thanks for you for help and great SO link! I'll certainly play with it


Relaunch, Screen is not displayed

When the app is restarted via websocket command relaunch, the screen doesn't get displayed, instead the desktoppanel is displayed with the margins of a regular screen

doesn't happen anymore


How could I cache the Nuget restore task?

Inside my pipe I have a task that restores the nuget packages, could I improve the performance of this task with its extension?

Hi David!
Depending on how many packages you are resolving, you may indeed see some perf gains by adding caching. However, I would recommend using the built in Pipeline Caching tasks as they will soon have all the features of this repository's tasks.
With the built in tasks, you could cache resolved nuget packages like so:
variables:
  NUGET_PACKAGES: $(Pipeline.Workspace)/.nuget/packages

steps:
...
- task: Cache@2
  inputs:
    key: 'nuget | "$(Agent.OS)" | **/*.csproj'
    restoreKeys: |
       nuget | "$(Agent.OS)"
       nuget
    path: $(NUGET_PACKAGES)
  displayName: Cache NuGet packages
...

What if I don't use PackageReferences to manage NuGet dependencies? They are classic applications in the .NET Framework

Does that mean you're using packages.config files to manage nuget dependencies?
variables:
  NUGET_PACKAGES: $(Pipeline.Workspace)/.nuget/packages

steps:
...
- task: Cache@2
  inputs:
    key: 'nuget | "$(Agent.OS)" | **/packages.config'
    restoreKeys: |
       nuget | "$(Agent.OS)"
       nuget
    path: $(NUGET_PACKAGES)
  displayName: Cache NuGet packages
...

That's. I am not using yaml either. Can this task be configured?

Yes. Any task can be configured via yaml or the designer.

I have not noticed a great improvement. It would be like this? Do not?

And the Variables tab:

Your settings are correct. Build time improvements will depend on a variety of factors, mainly: number of packages and the build agent OS. It may absolutely be the case where the difference between having nuget resolve packages and restoring/unpacking a cached artifact will be negligible.

Thank you so much for everything. You have been a great help


RHOARDOC-1739: synced Thorntail sources + updated sync script with new repo address

I took a quick look, even though this is already merged, and there's nothing wrong. Thanks!

@Ladicek Thank you:)


User Manual > Firmware Update links upstream

It is really great you (mebitek) are keeping pace with the documentation along all the updates so nicely. Thanks for all your efforts!
FTFM: https://mebitek.github.io/performer/manual/#appendix-firmware-update
"Download the latest UPDATE.DAT file from https://github.com/westlicht/performer/releases."
-> shouldn't that link point to "https://github.com/mebitek/performer/releases"?
Since the manual covers the forked software I think it may as well refernce itself rather than Simon's OG firmware.

thx for reporting


Need to specify VO explicitly for deployments

At the moment, the VO memberships are obtained from get_user_info https://github.com/AI4EOSC/ai4-papi/blob/master/ai4papi/auth.py#L87. However, if the user has memberships of more than one VO supported by the platform (most of us), it is not clear which VO the deployment belongs to.
Therefore, VO should be explicitly given as a parameter, at least for creating deployment. The authentication process should check if the user has membership of the VO, otherwise it fails.

Hi @tdviet ,
the behaviour you are describing is already implemented:

VO as a parameter here and here
check VO membership is not yet implemented because we are still not deploying to namespaces. But I can write the checks nevertheless to advance some of the work.

Hi @IgnacioHeredia ,
thank you for quick answers (for both issues). I didn't aware that the VO is given in the configuration of the deployment.
In my personal opinion, the explicit VO as an extra parameter of all functions of the deployment module may help:

for the create_deployment(), the deployment configuration is more generic, VO-independent. The CLI/dashboard don't have to modify the deployment configuration because of changing VO.
for the get_deployments() function, without the VO as the parameter, we will have to list all namespaces.

Yes, that could make sense. I'll leave the issue open till this is implemented then.

Done in #16.


✨ Add support for wildcard patterns.

Adds support for wildcard/ignored patterns such as _ or _foo. The trailing name is useful because you can effectively comment ignored bindings. As a simple example consider:
fun always = keep _ignore => keep

Here's another example using the (currently not-implemented) switch syntax:
switch ast on
    | AST.Application _function args => // do something with just `args` here
    | _ => // do something else

Closes #8.

Is there any reason to special-case _ and not just use a normal identifier? Presumably you can choose not to do anything with variables even if not starting _?

A wildcard pattern doesn't introduce a new binding unlike an unused Name pattern. It's the difference between "cant use" and "doesn't use".

The knock-on effect is we can have tooling (or reporting built in the compiler) to catch unused variables without stepping on the toes of patterns that are explicitly ignored.


Bridge Design Audit

This Issue captures a number of UI edits required for the bridge.

[x] Lists should extend to the bottom of the card. Overflow should only be hidden if the bottom of the card is reached.

[x] Unavailable tokens must be disabled. See the disabled state for list items.

[x] There are two different sizes of small all-caps text being used. These both need to be 12px, Bold, Uppercase
[x] "Try another wallet" should open the connect wallet modal
[ ] need to add tooltips to the transaction details.
[x] transaction cards have a max-height of 700px
[x] transaction cards should be align-items: space-between so that the button is sticky to the bottom.
[x] Inputs such as amount need to be in a disabled state until the user is actually able to interact with them. See the inputs page.

@monaiuu using this I feel like hover states are needed for the transaction inputs. Even just a little movement of the arrow icon would help indicate that the element can be interacted with. Thoughts?
I'll continue to add edits as I find them.

A few more edits found for Bridge UI:

In the amount input, users should only be able to input numbers (currently, users can input letters).

When users select a different chain, the wallet-connection modal appears although the user has already connected a wallet. We can remove the wallet-connection modal and have metamask prompt (add-chain or switch chain)

Can you add more screenshots or Figma links for the UI stuff, please? That would be very helpful and save time. Thank you 🙏

[ ] [TASK] If the user has not connected their wallet, the button at the bottom of the transfer and withdraw tabs should prompt the user to connect their wallet, as implemented in the deposit tab.

Closed in #777


[BUG] Using railway postgres with Ponder 0.6.0 results in error: relation "public.kysely_migration" does not exist at character 15

Since the update to 0.6.0+, I have been getting this error when deploying to railway:
2024-10-12 00:19:00.046 UTC [2] LOG:  database system is ready to accept connections
2024-10-12 00:20:32.615 UTC [82] ERROR:  relation "public.kysely_migration" does not exist at character 15
2024-10-12 00:20:32.615 UTC [82] STATEMENT:  SELECT * FROM public.kysely_migration LIMIT 1

To reproduce:

pnpm create ponder and select the reference erc20
create service on railway and follow steps on docs
create pg service on railway and add DATABASE_URL

To see how it was working correctly before, do the same steps as above except use pnpm create<EMAIL_ADDRESS>

Resolved in DMs. The issue was a combination of:

The ERROR:  relation "public.kysely_migration" does not exist at character 15 error was a red herring, that query happens shortly after startup to determine if we need to migrate the sync store from 0.2 -> 0.3
The Railway Postgres viewer made it look like there are no tables / data. This is because it only displays tables (and views?) present in the public schema. We removed the publish schema pattern in 0.6, so the actual tables were only present in the deployment-specific schema.

This will be resolved by the new table layout pattern in 0.7 (#1154). Also, we can likely remove the 0.2 -> 0.3 migration code - that's ancient history.


Spurious messages from unexpected rooms crashes bot

Depending on the logic of the bot, and how resilient it is to messages from unexpected source, this can cause crashes and security leaks.
This is only a problem when not using LISTEN_ON_ALL_PUBLIC but specifying a set of expected rooms.
Thanks to a thorough analysis by @elespike,  this happens because:

our subscriptions are long living, if the bot user has previously subscribed to a room, the bot will continue to receive messages from that room even if ROCKET_CHAT_ROOM does not include it
bot user might (be coaxed into) joining a room AFTER the bot started operation; for example, if someone @ mention the bot in an unexpected public room

2 is especially interesting as it might have security implications in some usage scenarios

@Sing-Li we briefly discussed a proposal for a new feature in Rocket.Chat to add bot controls to room settings. That would cover this kind of scenario, where bots could be locked out of particular rooms. I think it should be resolved on the Rocket.Chat side regardless, so it applies to all bots, not just Hubots.
I'll close this, but if you think it's still a concern, please add an issue in Rocket.Chat core with subj: bots label and I'll follow it up there.


simulation can take forever

If a model is very stiff (e.g. a very high rate of transfer across a membrane), both solvers can end up taking forever to do a simulation step, as they are forced to make the timestep very small.
Todo:

the user should be able to cancel such a simulation (see #274)
this situation should be diagnosed by the GUI and a message displayed to the user explaining the problem

As of #432 Pixel now identifies this situation, stops the simulation and displays info to the user to help them diagnose the source of the problem in their model.


REQUEST: Security Assessment for vsphere-csi-driver

Is this a Kubernetes sub-project?

Yes
Please tell us a bit about your sub-project

vSphere CSI driver is a volume plug-in that runs in a native Kubernetes cluster deployed in vSphere and is responsible for provisioning persistent volumes on vSphere storage.
Repo: https://github.com/kubernetes-sigs/vsphere-csi-driver
Do you have a preferred timeline for completing the security assessment?

Please share any additional or alternate points of contact for this request
@divyenpatel

cc @PushkarJ

/remove-lifecycle stale

/remove-lifecycle stale
@aladewberry this is the next project we could tackle for security self-assessment :)

/assign aladewberry
(Since you have already started to plan on how to proceed on this. Just assigning this to you for posterity)

Quick update - I have a meeting scheduled with @xing-yang next week to get connected and figure out where to start.

@aladewberry happy to sherpa again. just post meeting/slack info here. thanks!

Thank you! I'm still getting up to speed and will reach out when we starting taking steps!

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle rotten

This work in on-going.


Excessive CPU usage while Idling

Type: Performance Issue
My VS-code suddenly started using too much CPU from few days.
I looked up the internet and it said an extension might be doing that, so I un-installed all the extensions infact, I re-installed the new VS-code but issue remain still presist
I did some digging and it seems like that when I open my .md file (just single file WO any extensions) the CPU usage spikes. And, it remain so even after I close the file & VS-code as well. I had to use killall code to bring the CPU down.
I also ran code --status it shows below

CPU %
Mem MB
PID
Process

12
63
172313
electron-nodejs (/usr/share/code/code --ms-enable-electron-run-as-node /usr/share/code/resources/app/extensions/markdown-language-features/server/dist/node/workerMain --node-ipc --clientProcessId=172267)

VS Code version: Code 1.83.1 (f1b07bd25dfad64b0167beb15359ae573aecd2cc, 2023-10-10T23:45:31.402Z)
OS version: Linux x64 5.15.0-86-generic
Modes:

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 x 2400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
2, 1, 1

Memory (System)
15.32GB (4.78GB free)

Process Argv
--unity-launch --crash-reporter-id 670ec1d3-c3be-438a-8764-4b26a3f245d6

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

Process Info
CPU %	Mem MB	   PID	Process
    0	   157	173907	code main
    0	    31	173912	   zygote
    0	   110	173945	     gpu-process
    0	    31	173913	   zygote
    0	     0	173915	     zygote
    0	   188	173973	window [1] (Notes - Visual Studio Code)
    0	    94	175129	window [2] (Issue Reporter)
    0	    47	173950	   utility-network-service
    0	   110	174198	extensionHost [1]
   12	    63	174918	     electron-nodejs (/usr/share/code/code --ms-enable-electron-run-as-node /usr/share/code/resources/app/extensions/markdown-language-features/server/dist/node/workerMain --node-ipc --clientProcessId=174198)
    0	    78	174208	shared-process
    0	     0	175147	     /bin/sh -c /usr/bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0	     0	175148	       /usr/bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0	    63	174209	fileWatcher [1]

Workspace Info
|  Window (Notes - Visual Studio Code)
|    Folder (Notes): 11 files
|      File types: md(4) txt(4) json(2) php(1)
|      Conf files:;

Extensions: none
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263:30856252
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
282f8724:30602487
89544117:30613380
2i9eh265:30646982
showlangstatbar:30737416
0bi6i642:30841073
a2ce3375:30757347
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxptcf:30805731
pythonnoceb:30805159
copilotsettingc:30839828
synctok:30821570
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
pythonmpsinfo:30842941
dsvsc015:30845448

Can you share an example project which causes this issue

In my case, I actually don't use VS-code for project but rather for to edit/manage file formats like md, txt, sql & json.
Among them, like I said when I open my .md file the CPU spikes up.

same issue

@dani0332 Please share some example code which demonstrates the issue so we can investigate

@mjbvz See https://github.com/microsoft/vscode/issues/195756#issuecomment-1767608848

Experiencing a similar issue as issue 2 with markdown file that contains

# symbol
[\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

Originally posted by @penghiang in https://github.com/microsoft/vscode/issues/195756#issuecomment-1767608848
I can reproduce the issue with:
Version: 1.84.0-insider
Commit: f1c3b1dcf85e3b6ddb24b7dce0e4b122e8ce6233
Date: 2023-10-17T05:38:23.658Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 22.6.0

Though, I have mentioned that any markdown file causes this issue. But if you still want the example markdown file, find the attached file. Hopefully that'll suffice
frequent-use-copy.md

I have the same problem as @dani0332, using the same OS (Ubuntu).
Like @dani0332 mentioned:
* Not using any extension at all doesn't solve the problem.

* If visual studio code interface is killed, the process continues to run.

Exactly the same issue my side. Not sure what triggers it.

Similar issue here @ https://github.com/microsoft/vscode/issues/195756
My workaround is to downgrade to v1.80.0.

Thank you for the repo @tamuratak!
This was caused by a catastrophic backtracking in a regular expression. I believe it should by fixed by https://github.com/microsoft/vscode-markdown-languageservice/pull/157 which will be in the first 1.85 insiders builds once those come out later this week
Let me know if you still see this issue in VS Code 1.85+

Downgrading from 1.84.2 to 1.82.3 resolved issue on macOS 14.1.1


[OpenAI-Assistants] Support Assistant v2 API version

https://platform.openai.com/docs/assistants/whats-new
OpenAI announces they have a new Assistant API version.
We need to investigate and support it in our SDK as well.

Spec for Assistants V2 PR is under revision.
In order to start work on this feature there are 2 blockers:

Assistant V1 streaming spec
Assistant V1 streaming in Java (this one is also blocked by the item above)


Added HGRippleRadarView by @HamzaGhazouani

Project URL

https://github.com/HamzaGhazouani/HGRippleRadarView
Category

UI
Description

A beautiful radar view to show nearby items (users, restaurants, ...) with ripple animation, fully customizable
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 1 link issue, a project collaborator will take care of these, thanks :)

Link issue by awesome_bot

Line
Status
Link

2876
302
http://www.ios-blog.co.uk/ redirects tohttp://www.ios-blog.co.uk/cgi-sys/suspendedpage.cgi

  Generated by :no_entry_sign: Danger


Corrected sqlalchemy spatial operator mapping

Closes #7
This PR includes some changes from #8 as #8 has not been merged.

Hi @captaincoordinates
Thanks for this PR. Currently I only see the same changes as in #7
Should there be more?

Hi @captaincoordinates
Thanks for this PR. Currently I only see the same changes as in #7
Should there be more?

@constantinius sorry, I got myself confused. The comment in the description referencing this PR was supposed to be in #10. This PR is only intended to change a single file.


Set Autopilot

I want to enable the autopilot mode for a vehicle. When I run the python script, it does not move .
'''
client = carla.Client('localhost', 2000)
traffic_manager = client.get_trafficmanager(8000)
traffic_manager.set_global_distance_to_leading_vehicle(1.0)
traffic_manager.set_hybrid_physics_mode(True)
traffic_manager.set_synchronous_mode(True)
client.set_timeout(5.0)
world = client.get_world()
blueprint_library = world.get_blueprint_library()
bp = blueprint_library.filter('cybertruck')[0]
print(bp)

spawn_point = random.choice(world.get_map().get_spawn_points())
print(spawn_point);
vehicle = world.spawn_actor(bp, spawn_point)
vehicle.set_autopilot(True, traffic_manager.get_port())

'''

Make sure to check in depth how we do this in spawn_npc.py (or generate_traffic.py in dev) before opening an issue. It's also very well documented on the docs.

I have implemented the same approach as in spawn_npc.py , I use windows, so there is no dev file in my Carla

I use windows, so there is no dev file in my Carla

I believe he was referring to the generate_traffic.py in the dev branch

Hi @anas-abulehia
Your code seems right to me. The only difference to my is that i wrote "world.tick()" after setting the autopilot, to be sure the server recieves the information.

I have added world.tick(), but same it stops
 client = carla.Client('localhost', 2000)     traffic_manager = client.get_trafficmanager(8000)     traffic_manager.set_global_distance_to_leading_vehicle(1.0)     traffic_manager.set_hybrid_physics_mode(True)     traffic_manager.set_synchronous_mode(True)     client.set_timeout(5.0)     world = client.get_world()     blueprint_library = world.get_blueprint_library()     bp = blueprint_library.filter('cybertruck')[0]     spawn_point = random.choice(world.get_map().get_spawn_points())     print(spawn_point);     vehicle = world.spawn_actor(bp, spawn_point)     vehicle.set_autopilot(True, traffic_manager.get_port())     world.tick();

I have added world.tick(), but same it stops
 client = carla.Client('localhost', 2000) traffic_manager = client.get_trafficmanager(8000) traffic_manager.set_global_distance_to_leading_vehicle(1.0) traffic_manager.set_hybrid_physics_mode(True) traffic_manager.set_synchronous_mode(True) client.set_timeout(5.0) world = client.get_world() blueprint_library = world.get_blueprint_library() bp = blueprint_library.filter('cybertruck')[0] spawn_point = random.choice(world.get_map().get_spawn_points()) print(spawn_point); vehicle = world.spawn_actor(bp, spawn_point) vehicle.set_autopilot(True, traffic_manager.get_port()) world.tick();

The world.tick() goes in a while true: loop. Please, check the spawn_npc.py script, this is clearly shown there.


Add retry.Until helper function

This adds a new retry method, that takes a bool function instead of an
error function. Its very common to have functions doing
if cond() { return error } else { return nil }

Now they can just do retry.Until(cond), which is a bit simpler.
I also moved a few examples over to the new syntax to validate the API
makes sense and works.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-helm-tests_istio
a98d85fb5acc26abf8f8758c19f2674d5ee63bc1
link
/test integ-helm-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


[Event Request] Codeunit 5750 "Whse.-Create Source Document" – New Event  “OnSalesLine2ReceiptLineOnBeforeUpdateReceiptLine”

Could we please have a new publisher “OnSalesLine2ReceiptLineOnBeforeUpdateReceiptLine” in Function “SalesLine2ReceiptLine”, Codeunit 5750 "Whse.-Create Source Document”?

    procedure SalesLine2ReceiptLine(WhseReceiptHeader: Record "Warehouse Receipt Header"; SalesLine: Record "Sales Line"): Boolean
    var
        WhseReceiptLine: Record "Warehouse Receipt Line";
    begin
        with WhseReceiptLine do begin
            InitNewLine(WhseReceiptHeader."No.");
            SetSource(DATABASE::"Sales Line", SalesLine."Document Type", SalesLine."Document No.", SalesLine."Line No.");
            SalesLine.TestField("Unit of Measure Code");
…
            if "Bin Code" = '' then
                "Bin Code" := SalesLine."Bin Code";
*** start new code ***
            OnSalesLine2ReceiptLineOnBeforeUpdateReceiptLine(WhseReceiptLine, SalesLine);
*** stop new code ***
            UpdateReceiptLine(WhseReceiptLine, WhseReceiptHeader);
            OnBeforeCreateReceiptLineFromSalesLine(WhseReceiptLine, WhseReceiptHeader, SalesLine);
…
*** start new code ***
    [IntegrationEvent(false, false)]
    local procedure OnSalesLine2ReceiptLineOnBeforeUpdateReceiptLine(var WarehouseReceiptLine: Record "Warehouse Receipt Line"; SalesLine: Record "Sales Line")
    begin
    end;
*** stop new code ***

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


BaseCollector doesn't destruct properly.

Something like
#include <zipkin/zipkin.hpp>

int main() {
  std::shared_ptr<zipkin::Collector> collector;
  collector.reset(zipkin::Collector::create("http://localhost:9411"));
  return 0;
}

will exit via std::terminate. I expect it's because the m_worker thread started from BaseCollector isn't joined upon destruction.

It hard to graceful shutdown collector in it's destructor, I prefer to use Collector::shutdown explicit
.
#include <zipkin/zipkin.hpp>

int main() {
  std::shared_ptr<zipkin::Collector> collector;
  collector.reset(zipkin::Collector::create("http://localhost:9411"));
  collector->shutdown(std::chrono::milliseconds(500));
  return 0;
}

Another option is to return a wrapper like CollectorGuard from Collector::create, which shutdown the collector when it was destroyed, but it need introduce a redundant smart pointer.
At least, we could force to detach the worker thread when Collector destroyed, it may lost some pending messages in the queue without a shutdown or flush.
What's your opinion?

in a lot of zipkin tracers, there's a way to close the async reporter
(collector here I think). This usually gives some try at finishing
in-flight spans, so blocks a little. It isn't usual for the tracer to
self-register a shutdown hook on process exit. This is a deployment choice
that library users could do on their own.


NoSuchMethodError: No virtual method log(Ljava/lang/String;)V in class Lokhttp3/internal/Platform;

it's fine if I delete
HttpLoggingInterceptor logging = new HttpLoggingInterceptor();       logging.setLevel(HttpLoggingInterceptor.Level.BASIC);       builder.interceptors().add(logging);
but if i use okhttp3 logging-interceptor, throw this exception:
java.lang.IllegalStateException: Fatal Exception thrown on Scheduler.Worker thread.                                                                             at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:62)                                                                             at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:423)                                                                             at java.util.concurrent.FutureTask.run(FutureTask.java:237)                                                                             at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:154)                                                                             at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:269)                                                                             at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)                                                                             at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)                                                                             at java.lang.Thread.run(Thread.java:833)                                                                          Caused by: java.lang.NoSuchMethodError: No virtual method log(Ljava/lang/String;)V in class Lokhttp3/internal/Platform; or its super classes (declaration of 'okhttp3.internal.Platform' appears in /data/app/com.ouyangzn.topgithub-2/base.apk)                                                                             at okhttp3.logging.HttpLoggingInterceptor$Logger$1.log(HttpLoggingInterceptor.java:109)                                                                             at okhttp3.logging.HttpLoggingInterceptor.intercept(HttpLoggingInterceptor.java:157)                                                                             at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)                                                                             at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)                                                                             at okhttp3.RealCall.execute(RealCall.java:57)                                                                             at retrofit2.OkHttpCall.execute(OkHttpCall.java:174)                                                                             at retrofit2.adapter.rxjava.RxJavaCallAdapterFactory$RequestArbiter.request(RxJavaCallAdapterFactory.java:171)                                                                             at rx.internal.operators.OperatorSubscribeOn$1$1$1$1.call(OperatorSubscribeOn.java:85)                                                                             at rx.internal.schedulers.CachedThreadScheduler$EventLoopWorker$1.call(CachedThreadScheduler.java:222)                                                                             at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)                                                                             at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:423)                                                                              at java.util.concurrent.FutureTask.run(FutureTask.java:237)                                                                              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:154)                                                                              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:269)                                                                              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)                                                                              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)                                                                              at java.lang.Thread.run(Thread.java:833)

You need to use the same version for all of your OK dependencies. If you don’t, things won't work!

I used the same version:
compile "com.squareup.okhttp3:okhttp:${OKHTTP_VERSION}"
compile "com.squareup.okhttp3:logging-interceptor:${OKHTTP_VERSION}"
OKHTTP_VERSION = 3.2.0
Now i kown, the problem is caused by retrofit, i used :
compile "com.squareup.retrofit2:retrofit:${RETROFIT_VERSION}"
RETROFIT_VERSION = 2.1.0
retrofit 2.1.0 used okhttp3.3.0, so ...
I convert retrofit version to 2.0.2, it's ok.

Do not downgrade Retrofit. Upgrade OkHttp.
On Wed, Sep 7, 2016, 1:52 AM ouyangzn<EMAIL_ADDRESS>wrote:

I used the same version:
compile "com.squareup.okhttp3:okhttp:${OKHTTP_VERSION}"
compile "com.squareup.okhttp3:logging-interceptor:${OKHTTP_VERSION}"
OKHTTP_VERSION = 3.2.0
Now i kown, the problem is caused by retrofit, i used :
compile "com.squareup.retrofit2:retrofit:${RETROFIT_VERSION}"
RETROFIT_VERSION = 2.1.0
retrofit 2.1.0 used okhttp3.3.0, so ...
I convert retrofit version to 2.0.2, it's ok.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/2839#issuecomment-245182274, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEEET1RrHgJuRQa9Lk_Fy5tuLHPXdYyks5qnlE1gaJpZM4J1luG
.

ok , i know, thanks, i was ignore that okhttp's latest version is 3.4.1;

Is there any where to look up which versions work together... I'm getting this with the latest versions of both...

The version of all artifacts from OkHttp should always be the same.
On Wed, Nov 30, 2016 at 4:42 PM Matthew Clark<EMAIL_ADDRESS>wrote:

Is there any where to look up which versions work together... I'm getting
this with the latest versions of both...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/2839#issuecomment-264004637, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEEEaBtBf6Efw47V-xsq5UtUD2iXc05ks5rDe2_gaJpZM4J1luG
.

I meant what versions of OkHttp that work with what versions of retrofit

Every 3.x version of OkHttp should work with every 2.x version of Retrofit,
but in general, we ensure (and recommend) that the latest versions of each
are always working with each other.
On Wed, Nov 30, 2016 at 4:55 PM Matthew Clark<EMAIL_ADDRESS>wrote:

I meant what versions of OkHttp that work with what versions of retrofit
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/2839#issuecomment-264007987, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEEEXOarCVeJwyqtsFAwVUcYW8vyEsmks5rDfC8gaJpZM4J1luG
.

    def RETROFIT_VERSION = "2.1.0"
    compile "com.squareup.retrofit2:retrofit:${RETROFIT_VERSION}"
    compile "com.squareup.retrofit2:converter-gson:${RETROFIT_VERSION}"
    compile "com.squareup.retrofit2:converter-scalars:${RETROFIT_VERSION}"
    compile ("com.squareup.retrofit2:converter-simplexml:${RETROFIT_VERSION}"){
        exclude group: 'xpp3', module: 'xpp3'
        exclude group: 'stax', module: 'stax-api'
        exclude group: 'stax', module: 'stax'
    }

    def OKHTTP_VERSION = "3.4.2"
    compile "com.squareup.okhttp3:okhttp:${OKHTTP_VERSION}"
    compile "com.squareup.okhttp3:logging-interceptor:${OKHTTP_VERSION}"```

but still getting `No virtual method log(Ljava/lang/String;)V in class Lokhttp3/internal/Platform; or its super classes (declaration of 'okhttp3.internal.Platform' appears in /data/app/<package>-2/base.apk)`

When I try to use the logging interceptor:

HttpLoggingInterceptor interceptor = new HttpLoggingInterceptor();
interceptor.setLevel(HttpLoggingInterceptor.Level.BODY);
OkHttpClient client = new OkHttpClient.Builder().addInterceptor(interceptor).build();
    api = new Retrofit.Builder()
            .baseUrl(BASE_URL)
            .client(client)
            .addConverterFactory(SimpleXmlConverterFactory.create())
            .build().create(FeedApi.class);

changed code to
 HttpLoggingInterceptor interceptor = new HttpLoggingInterceptor();
        interceptor.setLevel(HttpLoggingInterceptor.Level.BODY);
        OkHttpClient client = new OkHttpClient.Builder().addInterceptor(interceptor).build();

        try {
            Response resp = client.newCall(new Request.Builder().url(BASE_URL+"/b2w").build()).execute();
            Log.d("MAIN","got resp:"+resp.body().toString());
        } catch (IOException e) {
            e.printStackTrace();
        }

and still getting the same error.

If you run the 'dependencies' task on your module you should be able to see
the resolved versions to make sure they all match.
On Wed, Nov 30, 2016 at 6:24 PM Matthew Clark<EMAIL_ADDRESS>wrote:

changed code to
HttpLoggingInterceptor interceptor = new HttpLoggingInterceptor();
interceptor.setLevel(HttpLoggingInterceptor.Level.BODY);
OkHttpClient client = new OkHttpClient.Builder().addInterceptor(interceptor).
build();
    try {
        Response resp = client.newCall(new Request.Builder().url(BASE_URL+"/b2w").build()).execute();
        Log.d("MAIN","got resp:"+resp.body().toString());
    } catch (IOException e) {
        e.printStackTrace();
    }

and still getting the same error.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/2839#issuecomment-264029309, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEEEaxxaqiyJS_z9w7cTY_J4z4D-e3Rks5rDgXIgaJpZM4J1luG
.

I believe this is what you meant:

and this was the results:

There is a "Gradle Console" tab in Android Studio, check what's there after
running the task. Or you can do it from Terminal: ./gradlew :app:dependencies.
On Fri, Dec 2, 2016 at 9:08 AM, Matthew Clark<EMAIL_ADDRESS>wrote:

I believe this is what you meant:
[image: screen shot 2016-12-02 at 12 07 43 am]
https://cloud.githubusercontent.com/assets/484943/20824551/64d0999a-b823-11e6-9057-af648b7cc403.png
and this was the results:
[image: screen shot 2016-12-02 at 12 02 37 am]
https://cloud.githubusercontent.com/assets/484943/20824539/50171420-b823-11e6-9f4e-1267978f34c5.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/2839#issuecomment-264381207, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA7B3N4SQmXsp_ILvDu5HUHZupRNkjF4ks5rD7XbgaJpZM4J1luG
.

Yeah, it was blank the first run as well...^^;

Here is what I'm hoping is the import info from the command line output:

compile - Classpath for compiling the main sources.
+--- io.realm:realm-android-library:2.2.0
|    +--- io.realm:realm-annotations:2.2.0
|    \--- com.getkeepsafe.relinker:relinker:1.2.2
+--- io.realm:realm-annotations:2.2.0
+--- com.android.support:appcompat-v7:25.0.1
|    +--- com.android.support:support-v4:25.0.1
|    |    +--- com.android.support:support-compat:25.0.1
|    |    |    \--- com.android.support:support-annotations:25.0.1
|    |    +--- com.android.support:support-media-compat:25.0.1
|    |    |    \--- com.android.support:support-compat:25.0.1 (*)
|    |    +--- com.android.support:support-core-utils:25.0.1
|    |    |    \--- com.android.support:support-compat:25.0.1 (*)
|    |    +--- com.android.support:support-core-ui:25.0.1
|    |    |    \--- com.android.support:support-compat:25.0.1 (*)
|    |    \--- com.android.support:support-fragment:25.0.1
|    |         +--- com.android.support:support-compat:25.0.1 (*)
|    |         +--- com.android.support:support-media-compat:25.0.1 (*)
|    |         +--- com.android.support:support-core-ui:25.0.1 (*)
|    |         \--- com.android.support:support-core-utils:25.0.1 (*)
|    +--- com.android.support:support-vector-drawable:25.0.1
|    |    \--- com.android.support:support-compat:25.0.1 (*)
|    \--- com.android.support:animated-vector-drawable:25.0.1
|         \--- com.android.support:support-vector-drawable:25.0.1 (*)
+--- com.android.support:recyclerview-v7:25.0.1
|    +--- com.android.support:support-annotations:25.0.1
|    +--- com.android.support:support-compat:25.0.1 (*)
|    \--- com.android.support:support-core-ui:25.0.1 (*)
+--- com.android.support:cardview-v7:25.0.1
|    \--- com.android.support:support-annotations:25.0.1
+--- com.android.support.constraint:constraint-layout:1.0.0-beta4
|    \--- com.android.support.constraint:constraint-layout-solver:1.0.0-beta4
+--- com.squareup.retrofit2:retrofit:2.1.0
|    \--- com.squareup.okhttp3:okhttp:3.3.0 -> 3.4.2
|         \--- com.squareup.okio:okio:1.9.0
+--- com.squareup.retrofit2:converter-gson:2.1.0
|    +--- com.squareup.retrofit2:retrofit:2.1.0 (*)
|    \--- com.google.code.gson:gson:2.7
+--- com.squareup.retrofit2:converter-scalars:2.1.0
|    \--- com.squareup.retrofit2:retrofit:2.1.0 (*)
+--- com.squareup.retrofit2:converter-simplexml:2.1.0
|    +--- com.squareup.retrofit2:retrofit:2.1.0 (*)
|    \--- org.simpleframework:simple-xml:2.7.1
+--- com.squareup.okhttp3:okhttp:3.4.2 (*)
\--- com.squareup.okhttp3:logging-interceptor:3.4.2
     \--- com.squareup.okhttp3:okhttp:3.4.2 (*)

Any ideas? Btw thanks @artem-zinnatullin for pointing the command line out^^

I have the same problem,but i dont know how to solve it

@Ku-Dou
Cause of this problem is:

mismatch of the okhttp versions inside retrofit and logging interceptor

In order for the logging interceptor to work you will need to use exactly same version numbers in okhttp & logging interceptor.
If you are using Retrofit, you can find the okhttp version inside retrofit from here:
https://github.com/square/retrofit/blob/master/gradle/libs.versions.toml#L17
and use the same version for logging interceptor.


Re-add hash prop for CustomLinkComponent

Describe the bug
Slack thread: https://stoplight-internal.slack.com/archives/C029YQEEALD/p1637705560313100
See conversation on a previous PR: https://github.com/stoplightio/elements/pull/1867#discussion_r755456248
Code that was removed: https://github.com/stoplightio/elements/pull/1867/files#diff-68a5fef9b2c6320bf5ecb0adac2b3c688d957d53fda3d3e978d27b476988a0f4L13

@Nezteb is this a bug or an enhancement?

@Nezteb is this a bug or an enhancement?

I don't know. It depends on what we call "code that was mistakenly removed that shouldn't have been". 😂

OK well, specifically, this issue came up in Raleigh's bug triage meeting to assign it a priority (p/urgent, p/high, etc).
If it's just blocking potential someday NextJS integration and not actually causing anything to be broken for any current modern-day users / customers, then I hesitate to classify it as a bug.


Fix CVE-2018-1152 and CVE-2018-11813

libjpeg-turbo-2.0 is out which fixes this bug but the build system is
completely changed from 1.5.3 to 2.0 and would need Bazel build changes
so backport the patch first.
https://nvd.nist.gov/vuln/detail/CVE-2018-1152
Signed-off-by: Jason Zaman<EMAIL_ADDRESS>

The same patch should work to cherry-pick to 1.10 since its the same version of libjpeg-turbo but not sure what the procedure is.

Damn, there is also CVE-2018-11813
https://github.com/libjpeg-turbo/libjpeg-turbo/commit/909a8cfc7bca9b2e6707425bdb74da997e8fa499
I'll update this PR

Merged both fixes into the patch

@martinwicke @av8ramit in case we roll out a patch release for 1.10, this is also needed.
I will rerun builds to make sure breakages are not flakes.

@gunan ping?

@yifeif, do you think we need to manually import this one?
@perfinion still no way to avoid the patch (by using a more recent libjpeg-turbo source)?

Yea I think so, third_party/jpeg/libjpeg-turbo-1.5.3-cve_fix.patch is a new file under third_party/

@gunan There is a 2.0.0 release which includes the fixes for both of these CVEs. But the jump is from 1.5.3 to 2.0.0 so I assume there would be some porting required (I have not looked into it yet tho). I thought it's best to get these fixes in asap first then looking into porting later can be done at a lower priority. If someone wants to port over to 2.0.0 and run all the tests that'd be a good way to go too.

@gunan I just tested 2.0.0 quickly, they apparently changed their build quite significantly so jpeg.BUILD will require rewriting. I'll look at it more tomorrow and try get it working. the next branch is soon right? at the very least this should be merged before the branch if we cant port to 2.0.0 in time. The patch on top of 1.5.3 is not that long so hopefully merging into the internal repo isnt too much trouble.

https://github.com/tensorflow/tensorflow/pull/21993 replaces this one so closing.


Move JupyterLab under My Apps as Default App

Reference Issues or PRs
N/A
What does this implement/fix?
Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[x] Did you test the pull request locally?
[x] Did you add new tests?

Documentation
N/A
Screenshots

Any other comments?

Updated to display Default App under My Apps as JupyerLab
Updated to disable Edit and Delete actions for Default App
Add/Update Unit Tests
This PR does not remove JupyterLab from Services

@jbouder can the "delete" button be disabled for this? If not lets make an issue to look at this again for the next release.

Added backend changes, should be good to go now.


Plugin request form cam4.com

Please add support for: http://*.cam4.com

If this can help, I write here some informations I found in various forum.
Link: www.cam4.com/modelname
To retrive the chat server:
Code:
http://www.cam4.com/direct?rand=1234567&room=modelname&username=guest
This will return the rtmp url to the chat window, for example rtmp://<IP_ADDRESS>/cam4-cr107.
This url is different for every model.
Then you must connect to the ip address in the url on port 1935 and do all the rtmp handshaking, custom commands, etc. After this you shoulg get the tcUrl to pass to the rtmpdump .


clear() is not clearing the backing array; elements() and getElements() might return cleared elements

Hey, I'm not sure if this is a bug or a feature.
I'm using the LongArrayList, and occasionally I need to clear it.
I have other methods that access the content of the list with LongArrayList#elements() and LongArrayList#getElements().
The issue is that due to LongArrayList#clear() only setting the size, but not actually cleaning up the backing array, and both LongArrayList#elements() and LongArrayList#getElements() not checking the size, only looking at the backing array, will actually return elements even when the size of the list is 0 (for example after clearing).
I would like that a call to LongArrayList#clear() actually clears the backing array, or that the other methods actually check against the supposed size of the list and do not return elements outside of it.
I understand that using LongArrayList#elements() might be hacky and not approved.
I understand that it might be my duty as the caller to check whether the requested range in LongArrayList#getElements() is valid.
If that's the intended way things should be, then a short note in the JavaDoc of both LongArrayList#elements() and LongArrayList#getElements() about being careful using them as they will not check whether the provided arguments fit with the size of the LongArrayList would be helpful.

Digging further around surfaced LongArrayList#trim() which, of course, I totally missed before opening the issue.


[Crash] - [Incompatible] - Crashes LevelZ Datapack when Vanilla Hammers & Inspecio & LevelZ are present

Hey there,
so this bug is very uncommon
when you use LevelZ Mod, Inspecio Mod & Vanilla Hammers Mod -> the Datapack for LevelZ doesnt work
"Maybe some Packets are restricted"
Fabric 1.18.2 - 0.13.3
In this latest.log, i hovered over a "bow" and the game crashes.
This is cause of LevelZ, but this only comes cause the datapack for levelz isnt loaded cause of the combination of vanilla hammers & inspecio
When i use LevelZ with Vanilla Hammers , the Datapack for LevelZ is loaded and all works fine
When i use LevelZ with Inspecio, the Datapack for LevelZ is loaded and all works fine
When i use all 3 (LevelZ , Inspecio & Vanilla Hammers), the Datapack for LevelZ isnt loaded (Packets)
Latest.Log
Crash Report

Inspecio Issue: https://github.com/Queerbric/Inspecio/issues/72

LevelZ Issue https://github.com/Globox1997/LevelZ/issues/117

For some reason the SimpleSynchronousResourceReloadListener doesn't execute the reload method when those three mods are loaded.
Don't know if it has something to do with quilt or your maybe-data ServerResourceManagerMixin.

Should be fixed in the next update - was my fault with the mixin Globox mentioned. Thanks for the report!


Issue 80

This PR provide support for mglyph-like elements. That is, all unknown elements that contain a direct speech attribute (e.g, alt, aria-label) are considered.

Elements found in (inferred) rows are handled as unknown elements with speech.
Those embedded as singletons in token elements (mi, mo, etc.) are treated in their context. E.g.,

<mo><mglyph alt="x"/></mo>

is treated as an operator and spoken as x. Direct speech attributes on the token will supersede the ones in the lower layer.

There is no support for mixed elements yet. Currently it will simply ignore any mglyph. I'll treat  that when I see a real world example.

This handles all examples from issue #80 and the ones I found built by Bruce Miller.

It also handles all the examples given in #165


[csolution] Support multiple component instances

The component subnode instances is described in the specification but it is not yet implemented:
https://github.com/Open-CMSIS-Pack/cmsis-toolbox/blob/main/docs/YML-Input-Format.md#instances
There is also an open discussion in Open-CMSIS-Pack-Spec about this subject:
Handling of Multiple Component Instances #76

RTE library already handles multiple component instances and their config files.
What is not yet implemented:

describing number of instances in cproject.yml file and passing this information to RTE model when selecting components

Do we agree that a component with "MaxInstance>1" and no "attr=config" files in its description is still accepted ?
In such a case, you cannot really link easily the instance and the files associated to it.

@fred-r, sure you can use "MaxInstance>1" without config files as well.
RTE_Components.h is populated with zero-based component indexes, e.g:
/* Keil::File System&MDK-Plus:Drive:Memory<EMAIL_ADDRESS>*/
#define RTE_FileSystem_Drive_MC_0       /* File System Memory Card Drive 0 */
#define RTE_FileSystem_Drive_MC_1       /* File System Memory Card Drive 1 */

Considering the fact that the subnode instances is specified but neither allowed by the Input YAML schema files nor supported by csolution processing this becomes a defect rather than an enhancement.
Note that in the cprj format and the cbuildgen tools already support the attribute instances

We have closed the discussion about changes to the specification and agreed that we would use the existing scope and features as already specified.
We need to ensure that we reflect the specification of instances in the schema of the CMSIS solution project YAML format once the format has been agreed:
current:
components:
  - component: USB:Device
    instances: 2

proposed 2024-02-14 (https://github.com/Open-CMSIS-Pack/cmsis-toolbox/blob/main/docs/setup.md#instance-number)
adding optional instance count [=N] (default 1)
[Cvendor::] Cclass [&Cbundle] :Cgroup [:Csub] [&Cvariant] [=N] [@[~ | >=]Cversion]

components:
  - component: USB:Device=2


Some questions about editing the .lua file.

I saw Support_FriendNames in the .lua file but I am not sure how to use it. Will inputting my friends' name auto pick his servant without the need of specifying the details? Or do I still need to add the images?
Edit: Had another question. Does the script check every class category to find the specified servant? Because I don't think there's any way to input the servant class.

For your first question, you need to take a screenshot of your friend's names.
It's still undocumented, so read this: https://github.com/29988122/Fate-Grand-Order_Lua/issues/212#issuecomment-524125097
For the second, no, the script will only scroll through the active tab of your support list.


Feature/64 readme refresh

Issue #, if available:
#64
Description of changes:
This pull requests refreshes the project readme. The aim of this refresh is to simplify the readme and make it easier and faster for the consumer to understand 1\ what the does and 2\ how it can be consumed.
Much of the content in the previous README has been moved to documents in the docs repo.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing branch due to issues with forked repo and terraform-docs issue. Will reopen from this repo.


Support socksjs?

Please follow:

https://github.com/sockjs/sockjs-client
https://github.com/MrJoes/sockjs-tornado

I think it is possible to connect sockjs-tornado with a Firenado Tornado component.
Let's try to do that on 0.1.3. I think we should try to put the original Tornado handler working here instead the websocket implementation provided by sockjs-tornado.


Sodium Video Settings button doesnt work

https://github.com/piemanau/better-sodium-video-settings/assets/68875386/d6e2a0ee-fd34-432f-94c7-5760a52b6605
Turn on sound to hear me click the butotn
MInecraft Version: 1.20.4
Sodium Version: mc1.20.4-0.5.8
BSVSB Version: 3.0.4
https://pastebin.com/NxZrAsJD

I believe that the 1.20.6 version fixes this issue, however the fabric.mod.json may need to be modified. If youd like it backported I may be able to get around to it at somepoint.


fix fix create tablet timeout #20067

Proposed changes
Issue Number: close #20067
Problem summary
To get tablet's local/remote size need acquire the tablet's meta lock.
But sometimes some operations may hold tablet's meta write lock for a while.
It will cause tablet manager's shards lock was block for so long time.
Do not calcute the tablet's local/remote size in the scope of the tablet manger's shards lock.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[x] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.74 seconds
stream load tsv:          445 seconds loaded<PHONE_NUMBER>9 Bytes, about 160 MB/s
stream load json:         22 seconds loaded<PHONE_NUMBER> Bytes, about 102 MB/s
stream load orc:          59 seconds loaded<PHONE_NUMBER> Bytes, about 17 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          79.1 seconds inserted 10000000 Rows, about 126K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230526095852_clickbench_pr_151168.html

run buildall

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.93 seconds
stream load tsv:          448 seconds loaded<PHONE_NUMBER>9 Bytes, about 159 MB/s
stream load json:         22 seconds loaded<PHONE_NUMBER> Bytes, about 102 MB/s
stream load orc:          59 seconds loaded<PHONE_NUMBER> Bytes, about 17 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          82.0 seconds inserted 10000000 Rows, about 121K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230528130231_clickbench_pr_152222.html

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.65 seconds
stream load tsv:          446 seconds loaded<PHONE_NUMBER>9 Bytes, about 159 MB/s
stream load json:         22 seconds loaded<PHONE_NUMBER> Bytes, about 102 MB/s
stream load orc:          58 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          26.1 seconds inserted 10000000 Rows, about 383K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230528133558_clickbench_pr_152239.html


Create CODE_OF_CONDUCT.md

Fixes #451
By submitting this pull request I confirm I've read and complied with the below declarations.

[x] I have read the Contribution guidelines and I am confident that my PR reflects them.
[x] I have followed the coding guidelines for this project.
[ ] My code follows the skeleton code structure.
[ ] This pull request has a descriptive title. For example, Added {Algorithm/DS name} [{Language}], not Update README.md or Added new code.
[x] This pull request will be closed if I fail to update it even once in a continuous time span of 7 days.

Hi! Thanks for showing interest in contributing to this repository.
Please make sure that you have ticked the points mentioned in PR description correctly.
Thanks again!

@singhpratyush email id used<EMAIL_ADDRESS>

@singhpratyush @aashutoshrathi Update the email please review.


update Edit, Add, Delete sections in UG/DG

Coverage remained the same at 75.873% when pulling 564d1e12eacf5389f3ded532755d6e0d7a26c7c4 on aziziazfar:updateUsageForUGDG into 39653d9c1e5213a36c3d9aece920f3d2072523bf on CS2103AUG2017-T15-B4:master.


Fix REST output for new agreement parameter in utxq/mtxq

Data shows, just isn't fully RESTful

In light of the upcoming 'configurable dualities' this is being closed as the former will redefine the endpoints anyway