Submitting Collectible Ids

I've added a list of collectibles to the documentation for use as reference of what has been available on PlayStation Stars to either earn or buy. This list can be viewed at https://andshrew.github.io/PlayStation-Stars/collectibles-reference.
The list is incomplete and would benefit from people submitting the ids for any missing collectibles.
To assist with this I've created a tool which allows you to submit your list of earned collectibles and compare them against what is already indexed on the site. If it identifies any new collectibles then it would be appreciated if you could paste their ids as a comment on this issue.
How to use the Collectibles Parser to submit missing collectible ids

Log in the the PlayStation Store.
In the same browser, access the User Earned Collectibles PlayStation Stars API endpoint.
Select the entire JSON response and copy this. There is no user identifiable data contained within this data.
Access the Collectible Parser, and paste the JSON copied in the previous step into the text box.
After pasting your response a table will be generated showing the collectibles which you have earned.
Click the Check Collectibles button at the top of the table to compare against what is indexed on the site.
If you have any collectibles which are not indexed on the site a message will appear above the table, and the table view will be filtered to only display these collectibles.
Click the Copy Ids to Clipboard button to automatically copy the ids of the listed collectibles to your clipboard, these can then be pasted as a response on this issue.

If submitting collectibles please ensure to include their unique id. This is used to automatically retrieve information about the collectible from the PlayStation Stars API. The data for collectibles which have been indexed so far can be accessed here.

Thanks for creating this. I've managed to get the ID of a new collectible. Will keep posting if I find any more.
["10bfa748-0d44-51aa-bc47-cfe14b5a1847"]

Thanks @Macrike I've added that one.

Got some more for you:
["73a87881-fe22-53b1-84eb-4985e424b730","d9d28010-8350-59d5-a100-ccf4402cbee5","827b9779-076c-5789-a438-9f84fd73ee5a","2ce62f14-c517-5c13-9483-af288fff53cf","f0ebc7f1-f9db-5f49-aba9-1737584cdeec","ef2e1596-e8be-5728-bd90-0ec2d929ef4a","4cafcb18-053d-500c-8871-9e28ed0a723a","b5195a53-a74d-5c7e-ad58-33fc99c38fa0"]


Resource with ID ending with Microsoft.DBforPostgreSQL/servers/deletedserver does not exist

The resourceId instruction here looks for an ID that does not exist in the Activity Log

IOW, there is no resource with ID of the form of
/subscriptions/ffffffff-ffff-ffff-ffff-ffffffffffff/resourceGroups/TargetResourceGroup/providers/Microsoft.DBforPostgreSQL/servers/deletedserver
The step 6. of the instructions confirm that by displaying use of correct resource ID (placeholder):
/subscriptions/ffffffff-ffff-ffff-ffff-ffffffffffff/resourceGroups/SourceResourceGroup-Name/providers/Microsoft.DBforPostgreSQL/flexibleServers/SourceServer-Name
that to be used as value for sourceServerResourceId in the request body.
Since the instructions apply to disaster recovery, it is important to make them rock solid, otherwise users may be panicking trying to find a resource with ID that ends with .../Microsoft.DBforPostgreSQL/servers/deletedserver :)

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

ID: 748bb09a-b4be-34aa-bcde-91bce6244f5a
Version Independent ID: 0f88c945-ddf5-2eb1-357f-8b751ea2eccf
Content: Restore a dropped Azure Database for  PostgreSQL - Flexible Server
Content Source: articles/postgresql/flexible-server/how-to-restore-dropped-server.md
Service: postgresql
Sub-service: flexible-server
GitHub Login: @kabharati
Microsoft Alias: kabharati

@mloskot Thank you for your feedback. We will review and make an update if appropriate.

https://github.com/kabharati Could you please help with some clarification. I have tried to test that from my end and this is the resource Id showing after clicking on the JSON tab,
"resourceId": "/subscriptions/ffffffffffffffffffffffffffffffffff/resourceGroups/oury-rg/providers/Microsoft.DBforPostgreSQL/flexibleServers/ourytest", which is different to
Select the Delete PostgreSQL Server event, then select the JSON tab. Copy the resourceId and submissionTimestamp attributes in JSON output. The resourceId is in the following format: /subscriptions/ffffffff-ffff-ffff-ffff-ffffffffffff/resourceGroups/TargetResourceGroup/providers/Microsoft.DBforPostgreSQL/servers/deletedserver.

@Oury-MSFT FYI, I have actually exercised the instructions in this document to recover from disastrous deletion of the service, so I can empirically confirm that this document shows wrong value of the resourceId.
So, I can confirm /subscriptions/ffffffffffffffffffffffffffffffffff/resourceGroups/oury-rg/providers/Microsoft.DBforPostgreSQL/flexibleServers/ourytest is the correct value for resourceId that you are supposed to put in the request body.

@Oury-MSFT  @mloskot  - I agree there is typo the  value is shared by both of you is correct. I have updated the doc and it should reflect by EOD

@kabharati Thank you for updating the doc.
@mloskot We've made some recent changes to the content that address this. I'll now proceed to close this issue.

[heart]         Oury Ba reacted to your message:

From: kabharati @.>
Sent: Friday, January 12, 2024 9:20:45 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Mention @.>; Comment @.>; Assign @.***>
Subject: Re: [MicrosoftDocs/azure-docs] Resource with ID ending with Microsoft.DBforPostgreSQL/servers/deletedserver does not exist (Issue #118775)
@Oury-MSFThttps://github.com/Oury-MSFT @mloskothttps://github.com/mloskot - I agree there is typo the value is shared by both of you is correct. I have updated the doc and it should reflect by EOD
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/118775#issuecomment-1889964365 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS2IVSG5OGQ66KIVIGPF7TDYOGSK5BFKMF2HI4TJMJ2XIZLTTGBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVE3TANBWGU3TKNJSURXGC3LFVFUGC427NRQWEZLMQKSXMYLMOVS2SOBTGY3TAMRXGQZKI3TBNVS2S2DBONPWYYLCMVWIFJLWMFWHKZNJHAZTMNZQGMYTSM5ENZQW2ZNJNBQXGX3MMFRGK3ECUV3GC3DVMWUTQMZWG4YDIOJZGSSG4YLNMWUWQYLTL5WGCYTFNSBKK5TBNR2WLKRRGQYDIOBZGU2TMMFENZQW2ZNJNBQXGX3MMFRGK3ECUV3GC3DVMWVDGOBZGM4DCMRSGE32I3TBNVS2S2DBONPWYYLCMVWKY43VMJVGKY3UL52HS4DFVREXG43VMVBW63LNMVXHJJTUN5YGSY3TTCBKI5DZOBS2U4TFOBXXG2LUN5ZHTJLWMFWHKZNIG4ZDMOBVGAZDNAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDEMBXG4YTCMZWGEYIFJDUPFYGLJLMMFRGK3FFOZQWY5LFVE3TANBWGU3TKNJSQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKJYGM3DOMBSG42DFAVEOR4XAZNFNRQWEZLMUV3GC3DVMWUTQMZWG4YDGMJZGOBKI5DZOBS2K3DBMJSWZJLWMFWHKZNJHAZTMNZQGQ4TSNECUR2HS4DFUVWGCYTFNSSXMYLMOVS2UMJUGA2DQOJVGU3DBAVEOR4XAZNFNRQWEZLMUV3GC3DVMWVDGOBZGM4DCMRSGE32O5DSNFTWOZLSUZRXEZLBORSQ.
You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Error loading Rust wasm module

When I use wasm_bindgen I get error: Error loading Rust wasm module 'hello_wasm': TypeError: WebAssembly Instantiation: Import #0 module="__wbindgen_placeholder__" error: module is not an object or function
My code:
use wasm_bindgen::prelude::*;

// Import the `window.alert` function from the Web.
#[wasm_bindgen]
extern "C" {
    fn alert(s: &str);
}

// Export a `greet` function from Rust to JavaScript, that alerts a
// hello message.
#[wasm_bindgen]
pub fn greet(name: &str) {
    alert(&format!("Hello, {}!", name));
}

Sorry to bump into old issue, but to just clarify does using wasm-bindgen results in generating invalid WASM module unless you run some extra tooling?

Depending on wasm-bindgen in your Rust crate will generate a Wasm module that won't work correctly. It's technically still valid.
You have to run it through a post-processor, in this case wasm-bindgen-cli, to prepare it for proper consumption by a browser.


Fix microphone A/V setup test for Chrome/Safari

Current mic test https://github.com/cwilso/volume-meter/ and https://webaudiodemos.appspot.com/volume-meter/.
Works for me on macos desktop firefox, but not macos desktop chrome or safari.

OK, seems like this is working chrome for some others and it's just my machine?

Seems to tun off when

Loading links in a new tab helps: https://github.com/conix-center/ARENA-core/commit/e7e14a5d8ebde98d5ba5afb54cd4e378b8557d43

Not sure this is 100% related to this specifically, but there are some weirdness with browser navigating/refreshing some of the UI pages page, since the selected fields will keep to whatever you had them as (without triggering select change events).
For example, when you choose one of the dropdowns, the handler on change sets that selected device-id as active mic input. If you nav back and forth, the av page may load without the input device set.


chore(build): use yarn and add release script

Coverage remained the same at 88.747% when pulling 5c452f081378f3a8df3772cfa1baa9a8ec16e9bd on chore/use-yarn into 4148418b3c646986467fca3bff7b53efda147332 on master.

Coverage remained the same at 88.747% when pulling 58e698a60a3eb57c747ee822048c3615f3518547 on chore/use-yarn into 4148418b3c646986467fca3bff7b53efda147332 on master.


Abandon the STUN method to achieve a higher success rate of direct connection.

Consider using the method introduced in https://www.jordanwhited.com/posts/wireguard-endpoint-discovery-nat-traversal/ for NAT traversal and abandon STUN in order to increase the success rate of direct connection.

Thanks for sharing the URL @kaowul. We have a few plans to increase the success rate of direct connections, and your link will be helpful

Can you guys share the link?

I’d like to have the link too

@rgl @diegocn @kaowul since v0.20.0, we've updated our core connectivity layer and removed our proxy dependency for most connection types. Now mostly relayed connections are using it.


mulltiple view based on packages program

I have module1 that has
---a function that gives matplotlib output based on input(id) #button #dropdownlist for id
I have module2 that
-- a function that gives matplotlib with based on three input and input id #button #dropdownlist for id # three options
i have module 3
-- i have two functions that one function gives matplotlib with two inputs
-- An the other have generate some kind of output file when based on inputs given to the first function..
two buttons for id, output file generation.
ALL these module are simple python programms
I need to just plug these python module into main Flet app,
i can have a seperate view for each of these modules. just by clicking button(module1,module2,module3) on main view page of the appp...I DONT HAVE idea how to create those user controls dynamically.But YES one thing is sure, we are supposed to submit button, clear btn, textfield and dropdown , checkboxes.
for example view1 for module1 should dropdown   foor id, one input text field , clciking at sumbit btn, i should get output, and clear btn to clean the matplotlib graph.
for example view2 for module2 should dropdown   foor id, 3 checkboxes  , clciking at sumbit btn, i should get output, and clear btn to clean the matplotlib graph.
so how do we get this done, in FLET

It is possible to have mutiple flet apps under the main fletApp..
Is possible to open PyQt5 Ui popup window when clicking a button from Flet Ui Elevated Button


Allow willTransitionTo() to get the current path/params/query that will be transitioned from

After working on my auth flows, I realized the ideal behavior for my site in most cases is simply to transition back to whatever page the user was on before logging in.
So ideally in the willTransitionTo() hook of my login route, I simply save off the path/params/query being transitioned from.  However, I can't get that from the State mixin since of course willTransitionTo() is a static lifecycle method.   I can't even use window.location.href because it's already the URL of the new route.   I guess I could use the HTML5 history API or do something with a Location listener, but to me it just seems like plain common sense that if I'm being told I'm about to transition to something, I should be able to find out easily what I'm transitioning from as well.  I don't want to have to mix in a willTransitionFrom() into every single route in my application.
Thanks!

I think it will eventually become apparent that saving and retrying a transition only handles a limited number of authentication flows.  At least in the case of my single-page app, certain routes will render differently depending on the user's authorization status (rather than a given route being simply forbidden or not).
For instance, in my app, one dialog shows as read-only if the user isn't authorized to modify certain data; but I'm trying to make it where they can click a link to the dialog to go to the login page, and once they log in it will redirect them back to the page with the dialog, which (if they logged in as a user with write permissions) will no longer be read-only.  Implementing this flow is not convenient with the hooks react-router currently provides.

the auth flow example does this.

No, reopen.  The auth flow example is different.  It uses willTransitionTo() on each page that needs authorization.  I'm talking about putting willTransitionTo() on the login page itself, to save off whatever page is being transitioned from.  This way even if the user manually clicks the login link it will save what page they're coming from.  The auth flow way of doing things only works when it automatically redirects the user to the login page.
Once again, why not just provide the route being transitioned from to willTransitionTo() hooks?

You can wrap all your authed routes in a parent route, and only do it in one place: https://github.com/rackt/react-router/issues/1157#issuecomment-113184641

Maybe I'm not explaining well, because that's not what I'm to achieve.  Here is the corollary of what I was saying:

The user begins on route A that doesn't require authorization
The user clicks the login link
The user logs in
The user is redirected back to route A

And then if they started from paroutege B that doesn't require auth, it would redirect them back to that, etc.
In other words when the program redirects or the user navigates to login from any route besides login/logout, it saves what route they were on and goes back to it after login.

ah I gotcha, sorry, I'm cruising through tickets, perhaps too quickly.
We've been talking about adding location.referrer on our location objects.
I've opened a ticket for it at #1353

Okay, cool, that would work!

what for example, I want to consume a query parameter and redirect to the same path with the query parameter removed? I can see myself needing the getQuery() method in willTransitionTo


Suicide detection

Suicide-Detection
The Suicide Detection aims to prevent suicide attempts by analyzing the frames and detecting the chances of it happening. The files for the working of the model is kept in Suicide_Detection folder, which is under the main directory.
The main motive is not to provide full-fledged webcam app, but to provide the tools that can be implemented in the same. demo.py demonstrates the working of the main module, i.e., detect.py as a sample. detect.py can be imported by any script, and can be used to perform detections provided it uses OpenCV.
Implements #11
Requirements
requirements.txt in the Suicide_Detection folder contains the necessary libraries for the working of the model.
Working
demo.py should not be used for official purposes and is only added for the demonstration of the model. It is because the implementation is highly unoptimized. IT IS NOT RECOMMENDED TO PERFORM rope_detection AT EVERY ITERATION OF WHILE LOOP DIRECTLY AS IT MAY BLOCK THE OTHER PROCESSES. Use of threading or detection after every X frames is recommeded, especially on CPU.
detect.py contains all the necessary functions for the working, and can be implemented with further optimization.
It must be kept in mind that the predictions of the rope have to be optimized by the needs of the script. It is inefficient and slow especially in CPU, and methods like threading or generators have to be used to prevent the blocking of the script. Furthermore, the code has to be developed in the way that the threading or generators does not generate errors, or override the detections before the next detection is done.
The threat is divided in three levels:
Warning:
When a rope is identified above a person's head.

Danger:
It is followed by the Warning, in addition, the hands are detected near the rope.

Critical Danger:
The hands are ignored in this step. When the head and the rope is detected near.

Model
The models used for face and hands detection are provided by mediapipe library.
The model used for detecting ropes is YOLOv8 which uses YOLO Architecture, and used widely for object detection. The training files and the inference files are ignored to keep the size of the repository as low as possible.
Suicide_Detection\Model\Model_Data\logs\runs\detect\...\weights contains best.pt and last.pt. The former has the best results while the latter is updated at the last epoch. Any of them can be used as a valid model.
Suicide_Detection\Model\Model_Data\logs\runs\detect contains two folder. SuicideDetection and SuicideDetection2, the former trained with 640x640 px images for 50 epochs with batch_size as 64, and the latter with 480x480 images for 20 epoches with batch_size as 128.
If the rope is not getting detected, try keeping it closer to the camera or decreasing the confidence value in detect.py under detect function and conf parameter of model.predict. One of the downsides of YOLO is to predict small images due to multiple convolutional layers.
The mAP50 and mAP50-95 of both the models are:

SuicideDetection: 80.137% and 58.819% respectively.
SuicideDetection2: 75.47% and 52.43% respectively.

Model Stats
SuicideDetection (640x640 px)

SuicideDetection2 (480x480 px)

@TAHIR0110 Can you also add the gssoc and level3 label in the pull request, which were added in the issue #11? The program manager of GSSoC has advised to add the gssoc and level tags in both the issues as well as the PRs for the leaderboard.

@TAHIR0110 Please can you also add gssoc label? I apologize for asking for it numerous times but this was posted by the Program Manager,
"We are final stage on leaderboard updates.
I noticed few things PA's not mentioned lables on PR.
like gssoc, level1, level2, level3
gssoc24,GSSoC'24, gssoc
These are the labels.
with level1,level2, level3
recommended to use gssoc. Make sure this is assigned to issues and PR as well."

@TAHIR0110 Can you remove the white spacing in level 3. From level 3 to level3. It is not getting counted in the leaderboard.

@TAHIR0110 Another request. They posted three things to be checked.

Successful merge. (Tick)
Assignees. (Not Tick)
Labels. (Tick)

Can you also add me as an assignee in this pull request? I am an assignee in the issue but not in the PR.
If after that also my score is not updated, I will let the GSSoC team handle the issue.


Possible issue with typings where the parameters can be null.

Seems that the checker is not picking up on a libraries typings where the parameters can indeed be null.
Don't pass nullish arguments to a function that expects a non-nullish type.eslint[strict-null-checks/all](file:///all)

Are non-imported functions working correctly? For example does adding this not generate a warning?:
function foo(value: {value: number} | null) {}
foo(null);

First off, thanks for your work on this plugin @JaroslawPokropinski.
Just ran into this as well with a slightly different usage (function param initializers), and I can confirm it doesn't work for non-imported functions. Here's a trivial example:

In that example, TS tweaks the type of foo from what we defined it as to const foo: (bar?: number) => number because of the bar = 2 initializer.

Hello @doytch, have you been able to find the root cause of this issue ?
I'm also have this other issue (that look familiar).

That’s an odd one. But no, I never found a solution.
What I ended up doing is stopping use of this plugin in our org and used an interesting little feature in VSCode instead since almost all of us use it.
I added a nested tsconfig in our codebase. That is, if our normal tsconfig was at the project root ~, I put a new tsconfig in ~/src.
That tsconfig simply inherited the main tsconfig but turned on strictNullChecks. Absolutely nothing uses a nested tsconfig file by default - except VSCode’s TS server.
So that showed everybody errors during development but didn’t break builds. That may or may not meet your requirements (and I thiiink we might’ve been relying on undocumented VSCode behaviour so it’s not reliable long-term), but just figured I’d throw it out there.

That's a freaking awesome tips you got right there, thank you for sharing this, I think I will go for this too.
The ratio simplicity / efficiency is right where I need it to be.
Have a great day!


Restore BLS signature checks on constraints for devnet

Closes #72. This PR re-introduces BLS signatures checks on the forked relay following the procedure specified in the related issue.
Signatures are produced in the sidecar by finding validator data for the current epoch and retrieving the private key of the validator of the current slot.
It also introduces a feature flag in the sidecar called "demo" just to start separating the concerns. For now it's set to default.
While it's a bit unclear how these changes be impactful given recent development of both commit-boost and the registry, this is still a piece of functionality missing from the original demo and nice to have. Eventually we can keep it in a separate branch.

Closing this as outdated, will serve as a reference for future PRs if needed


Error sending updates to mint

Sent 1 updates to Mint
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 377, in _make_request
    httplib_response = conn.getresponse(buffering=True)
TypeError: getresponse() got an unexpected keyword argument 'buffering'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/mintapi/api.py", line 396, in close
    self.driver.find_element_by_id('link-logout').click()
  File "/usr/local/lib/python3.7/site-packages/selenium/webdriver/remote/webelement.py", line 80, in click
    self._execute(Command.CLICK_ELEMENT)
  File "/usr/local/lib/python3.7/site-packages/selenium/webdriver/remote/webelement.py", line 633, in _execute
    return self._parent.execute(command, params)
  File "/usr/local/lib/python3.7/site-packages/selenium/webdriver/remote/webdriver.py", line 319, in execute
    response = self.command_executor.execute(driver_command, params)
  File "/usr/local/lib/python3.7/site-packages/selenium/webdriver/remote/remote_connection.py", line 376, in execute
    return self._request(command_info[0], url, body=data)
  File "/usr/local/lib/python3.7/site-packages/selenium/webdriver/remote/remote_connection.py", line 399, in _request
    resp = self._conn.request(method, url, body=body, headers=headers)
  File "/usr/local/lib/python3.7/site-packages/urllib3/request.py", line 72, in request
    **urlopen_kw)
  File "/usr/local/lib/python3.7/site-packages/urllib3/request.py", line 150, in request_encode_body
    return self.urlopen(method, url, **extra_kw)
  File "/usr/local/lib/python3.7/site-packages/urllib3/poolmanager.py", line 322, in urlopen
    response = conn.urlopen(method, u.request_uri, **kw)
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 380, in _make_request
    httplib_response = conn.getresponse()
  File "/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1321, in getresponse
    response.begin()
  File "/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 296, in begin
    version, status, reason = self._read_status()
  File "/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 257, in _read_status
    line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
  File "/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/socket.py", line 589, in readinto
    return self._sock.recv_into(b)
KeyboardInterrupt

I'm hoping this is resolved now; please reopen if you continue to have issues w/ the latest version!


display required message on Cache-Busting setting description with Stateless is enabled.

When Stateless mode is enabled, we need to enable/enforce the Cache-Busting setting.

[ ] Update the Cache-Busting setting with the following message...

Required by Stateless Mode. Override with the WP_STATELESS_MEDIA_CACHE_CONTROL constant. Prepends a random set of numbers and letters to the filename. This is useful for preventing caching issues when uploading files that have the same filename.

[ ] "Required by Stateless Mode. Override with the WP_STATELESS_MEDIA_CACHE_CONTROL constant." should be bold.

[ ] link WP_STATELESS_MEDIA_CACHE_CONTROL to https://github.com/wpCloud/wp-stateless/wiki/Constants#wp_stateless_media_cache_control

Should Look Like This


[ISSUE 432] Added GitHub issue and pr template

https://github.com/DozerMapper/dozer/issues/432

https://github.com/DozerMapper/dozer/issues/427


In-memory ledger and regression tests

add in-memory ledger to state
add --ledger-cadence server flag to customize how often ledgers are persisted
add file writing regression tests
add many blocks regression test

Fixes https://github.com/Granola-Team/mina-indexer/issues/382 and https://github.com/Granola-Team/mina-indexer/issues/381

@Isaac-DeFrain It's always nice to leave a reason for closing a PR that has seemingly-valuable stuff in it.

Looks like it was superseded by this PR: https://github.com/Granola-Team/mina-indexer/pull/387


ESC-Key should not overwrite clipboard by default.

ESC-Key does not overwrite clipboard.
Exactly Ctrl-U overwrites clipboard.

Bash Features - Command Line Editing

unix-line-discard (C-u)
Kill backward from the cursor to the beginning of the current line. Save the killed text on the kill-ring

I am going to keep NYAGOS compatible with Bash.


Self Hosted VSTS Container Agents updated here: 👇

We've published a 100% legacy compatible VSTS Self-Hosted Agent Container.
Enjoy!

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

ID: b31d4f6c-d16d-2ba1-1294-6aa94e328046
Version Independent ID: 88aec599-4410-697d-1002-1c41b1c17bb6
Content: Run a self-hosted agent in Docker - Azure Pipelines
Content Source: docs/pipelines/agents/docker.md
Product: devops
Technology: devops-cicd-agents
GitHub Login: @steved0x
Microsoft Alias: sdanie

Hi @azilber - thanks for your input. I'm going to close this issue because there are no documentation actions for us to take -


setup the development environment

As a  developer
I need a development environment
So that i can work on the features
I will be needing the development environment so that I can work on the following features in the sprint
Given i am a developer
When i will be get the devolopment env
Then i will be able to work


BUG:1.0.2 version selection space prevents idea operation

Usage environment:
nebula-graph-database-support:1.0.2
idea:2023.3.2
windows:11
memory:64g
idea-Xmx:32768m

Problem 1: Choosing a space will result in the idea being unable to operate
Problem 2: Unable to execute ngql

Thank you very much for your feedback.What is your nebula version.The current plug-in uses Nebula-Client 3.6 version, which may be incompatible with your nebula server

We use Nebula Client version 3.5

发件人: @.*** @.> 代表 awang12345 @.>
发送时间: 2024年1月15日 19:07
收件人: nebula-contrib/nebula-console-intellij-plugin @.>
抄送: HarLin @.>; Author @.***>
主题: Re: [nebula-contrib/nebula-console-intellij-plugin] BUG:1.0.2 version selection space prevents idea operation (Issue #5)
Thank you very much for your feedback.What is your nebula version.The current plug-in uses Nebula-Client 3.6 version, which may be incompatible with your nebula server
―
Reply to this email directly, view it on GitHubhttps://github.com/nebula-contrib/nebula-console-intellij-plugin/issues/5#issuecomment-1893004584, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHCG65MWZJ5F7APR7KCMJ5LYOXVIZAVCNFSM6AAAAABB23ISPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJTGAYDINJYGQ.
You are receiving this because you authored the thread.Message ID: @.***>

What is your nebula version? I execute success in 3.6 use your statement

[cid:e8716c34-73f5-4dcc-9b8f-d3b1405e7fd3]
nebula version 3.4.1

发件人: @.*** @.> 代表 awang12345 @.>
发送时间: 2024年1月15日 21:54
收件人: nebula-contrib/nebula-console-intellij-plugin @.>
抄送: HarLin @.>; Author @.***>
主题: Re: [nebula-contrib/nebula-console-intellij-plugin] BUG:1.0.2 version selection space prevents idea operation (Issue #5)
What is your nebula version? I execute success in 3.6 use your statement
―
Reply to this email directly, view it on GitHubhttps://github.com/nebula-contrib/nebula-console-intellij-plugin/issues/5#issuecomment-1893112848, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHCG65LFV34WOF5IQJ3DNUDYOYIY7AVCNFSM6AAAAABB23ISPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJTGEYTEOBUHA.
You are receiving this because you authored the thread.

Ok. I'll try using the same version nebula

I'm execute statement  with 3.4.1 nebula with console  error occurred.It should be that nebula does not currently support this statement.I will optimized the error details in a later version
(root@nebula) [basketballplayer]> match p=(v)-[]-() return p limit 10
[ERROR (-1005)]: Scan vertices or edges need to specify a limit number, or limit number can not push down.

Thank you very much for your use. If you have any improvements or bugs in the future, I will follow up as soon as possible

Yes, my Ngql is incorrect. Thank you correcting me.

发件人: @.*** @.> 代表 awang12345 @.>
发送时间: 2024年1月15日 22:42
收件人: nebula-contrib/nebula-console-intellij-plugin @.>
抄送: HarLin @.>; Author @.***>
主题: Re: [nebula-contrib/nebula-console-intellij-plugin] BUG:1.0.2 version selection space prevents idea operation (Issue #5)
Thank you very much for your use. If you have any improvements or bugs in the future, I will follow up as soon as possible
―
Reply to this email directly, view it on GitHubhttps://github.com/nebula-contrib/nebula-console-intellij-plugin/issues/5#issuecomment-1893153912, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHCG65O7VWVE54XW3MK6OV3YOYOMHAVCNFSM6AAAAABB23ISPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJTGE2TGOJRGI.
You are receiving this because you authored the thread.Message ID: @.***>

Current issues:

Unable to select space, which will cause the idea to be unresponsive
The Chinese display is still abnormal
[cid:f3a32f47-6e31-4bb2-acbb-b94aedaee34f]

发件人: @.*** @.>
发送时间: 2024年1月15日 23:04
收件人: nebula-contrib/nebula-console-intellij-plugin @.>
主题: 回复: [nebula-contrib/nebula-console-intellij-plugin] BUG:1.0.2 version selection space prevents idea operation (Issue #5)
Yes, my Ngql is incorrect. Thank you correcting me.

发件人: @.*** @.> 代表 awang12345 @.>
发送时间: 2024年1月15日 22:42
收件人: nebula-contrib/nebula-console-intellij-plugin @.>
抄送: HarLin @.>; Author @.***>
主题: Re: [nebula-contrib/nebula-console-intellij-plugin] BUG:1.0.2 version selection space prevents idea operation (Issue #5)
Thank you very much for your use. If you have any improvements or bugs in the future, I will follow up as soon as possible
―
Reply to this email directly, view it on GitHubhttps://github.com/nebula-contrib/nebula-console-intellij-plugin/issues/5#issuecomment-1893153912, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHCG65O7VWVE54XW3MK6OV3YOYOMHAVCNFSM6AAAAABB23ISPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJTGE2TGOJRGI.
You are receiving this because you authored the thread.Message ID: @.***>

The Chinese display is still abnormal
You can execute stetment "SHOW CHARSET" to show your nebula charset.The current plugin reads the string and decodes it in utf-8.It is possible that the data stored in nebula is not utf-8 encoded
Unable to select space, which will cause the idea to be unresponsive
Space can't be selected because there is a process to load the metadata, which takes a lot of time depending on the number of Spaces, tags, and edges you have.I'm really sorry for the bad experience caused to you. I have recently optimized the UI interaction in this area

The encoding I am using is utf-8
[cid:89d4d7e3-9884-4ee3-bb18-8bceddd0ade2]

发件人: @.*** @.> 代表 awang12345 @.>
发送时间: 2024年1月15日 23:14
收件人: nebula-contrib/nebula-console-intellij-plugin @.>
抄送: HarLin @.>; Author @.***>
主题: Re: [nebula-contrib/nebula-console-intellij-plugin] BUG:1.0.2 version selection space prevents idea operation (Issue #5)
The Chinese display is still abnormal
You can execute stetment "SHOW CHARSET" to show your nebula charset.The current plugin reads the string and decodes it in utf-8.It is possible that the data stored in nebula is not utf-8 encoded
Unable to select space, which will cause the idea to be unresponsive
Space can't be selected because there is a process to load the metadata, which takes a lot of time depending on the number of Spaces, tags, and edges you have.I'm really sorry for the bad experience caused to you. I have recently optimized the UI interaction in this area
―
Reply to this email directly, view it on GitHubhttps://github.com/nebula-contrib/nebula-console-intellij-plugin/issues/5#issuecomment-1893182387, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHCG65JSWQPIKL4MLDKZ2OTYOYSFDAVCNFSM6AAAAABB23ISPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJTGE4DEMZYG4.
You are receiving this because you authored the thread.Message ID: @.***>

Does your use the official  nebula-conole to exuete statement is still abnormal?

[cid:339c7bce-8fda-42e0-9eef-7c42511c5ac8]
[cid:3591c540-ba24-4ed1-9936-845c65ae21ca]
I have no problem using Nebula console

发件人: @.*** @.> 代表 awang12345 @.>
发送时间: 2024年1月15日 23:26
收件人: nebula-contrib/nebula-console-intellij-plugin @.>
抄送: HarLin @.>; Author @.***>
主题: Re: [nebula-contrib/nebula-console-intellij-plugin] BUG:1.0.2 version selection space prevents idea operation (Issue #5)
Does your use the official nebula-conole to exuete statement is still abnormal?
―
Reply to this email directly, view it on GitHubhttps://github.com/nebula-contrib/nebula-console-intellij-plugin/issues/5#issuecomment-1893195457, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHCG65I2R6LQLKCAX4R4QFLYOYTT5AVCNFSM6AAAAABB23ISPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJTGE4TKNBVG4.
You are receiving this because you authored the thread.Message ID: @.***>

I went to see the nebula-console source code for the solution. I will fix this as soon as possible. Thanks again for your feedback

Hi.Plugin version 1.0.3 has been released. The above problem has been optimized. You can go to the plugin market to update the use.Thank you for using.


Update main dependencies

This change updates the main dependencies, mostly Fastly and OpenTelemetry.
The Node engine is now the current long term support release.
The compile command is now instead the more standard build command and is tested by the GitHub action.
@opentelemetry/api-metrics is now in @opentelemetry/api.
opentelemetry/sdk-metrics-base is now @opentelemetry/sdk-metrics.
Exporter types were in @opentelemetry/exporter-trace-otlp-http and are now in @opentelemetry/otlp-transformer.
.instrumentationLibrarySpans was renamed to .scopeSpans.
instrumentationLibraryMetrics was renamed to scopeMetrics.
SINGULAR was renamed to GAUGE.
Added new methods to MockedRequest.
aggregationTemporality was renamed to temporalityPreference.
Removed MetricProducer.
Types were moved to @opentelemetry/otlp-transformer.
Extend {} for ExportItem and ServiceRequest.

This was addressed as part of a series of commits to main.


Dynamic Resizing of CarouselViewControl has issues

I have my CarouselView inside AbsoluteLayout, which looks like this
<AbsoluteLayout>
    <CarouselViewControl AbsoluteLayout.LayoutFlags="All"
                                         AbsoluteLayout.LayoutBounds="0,1,1,0.25
                                         x:Name="CarouselViewControl" />
</AbsoluteLayout>

then in the source code I change the bounds in source as below during runtime,
    AbsoluteLayout.SetLayoutBounds(this.CarouselViewControl, new Rectangle(0f,1f,1f,0.75f));

The position of CarouselViewControl is updated to be correct location, but size does not change.
I tested with Other simple controls, they behave as expected, so I suspect it is issue with CarouselViewControl.
Thank you for time!

Why to wrap the Carousel into AbsoluteLayout in the first place? If it is the only element, you don't need the AbsoluteLayout. Use a Grid or ContentView or nothing.

I have other controls in AbsoluteLayout. I want to be able to pull up the CarouselView from bottom, then slide left/right for more information. In the example I have given, to make it simple I removed all other objects.

Is this solved?

Hey sorry for the late reply. The issue itself is not fixed. But I was able to find a work-around, instead of resizing the CarouselView, I change the Y position of it.


Data density too low

I understand that data density and tile sizes are conflicting issues but I think that the data/feature density in osm2vectortiles is still too low. ZL = zoom level.
Some Examples:
ZL 5 osm2vectortiles vs ZL 6 Google

Missing in oms2vectortiles:

[x] ZL5 Landuses (Forests)
[ ] ZL5 Roads
[x] ZL5 Cities/Places

(In return the regional borders could be pushed down one ZL IMHO.)
ZL 6 osm2vectortiles vs ZL 6 Mapbox Street v7

[x] ZL6 Cities/Places

ZL 7 osm2vectortiles vs ZL 7 Mapbox Street v7

[ ] ZL7 Cities/Places

ZL 8 osm2vectortiles
Data density ok I guess.
ZL 9 osm2vectortiles vs ZL 9 Mapbox Street v7

[ ] ZL9 Cities/Places
[ ] ZL9 Landuse residential

ZL 10 osm2vectortiles vs ZL 10 Mapbox Street v7

[x] ZL10 Cities/Places
[x] ZL10 Roads

ZL 11 osm2vectortiles vs ZL 12 Google Maps

[x] ZL11 Trains
[ ] ZL11 Small rivers

ZL 12 osm2vectortiles vs ZL 12 Mapbox Street v7

[ ] ZL12 Minor roads
[ ] ZL12 Water bodies
[ ] ZL12 Cities/Places

ZL 14+ osm2vectortiles

[x] ZL14 House numbers (for use in ZL17+)

(It even seems as if the stylings of ZLs in old raster maps and ZLs in osm2vectortiles would correspond, yet as vector tiles are 4x the size of raster tiles zoom levels do not correspond. What is ZL6 in the Mapbox GL world is ZL7 in the world of raster maps and with Google Maps.)

Thanks for the really detailed comparison.

I understand that data density and tile sizes are conflicting issues but I think that the data/feature density in osm2vectortiles is still too low. ZL = zoom level.

How did you do the screenshots? Are you comparing the http://dev.vectortiles.osm2vectortiles.org.

The good thing is that down to z8 or z9 we can easily rerender everything if we want to improve something since it is not that many tiles.

ZL 5 osm2vectortiles vs ZL 6 Google

Cannot see immediate differences on z5.
http://dev.vectortiles.osm2vectortiles.org/#5.12/46.119/8.030

ZL 6 osm2vectortiles vs ZL 6 Mapbox Street v7

The problem here is that we tested too much with Switzerland where the scalerank is mostly set for the important places. We can add more place labels but then mostly the client is responsible for filtering them by localrank.
What I do now in https://github.com/osm2vectortiles/osm2vectortiles/commit/807c7a986da46b1b51bc201dac32a6921d25b673 to improve density on z6 and z7 is to allow all town and city (even if no scalerank)
but I then limit the data to localrank < 40.

ZL 7 osm2vectortiles vs ZL 7 Mapbox Street v7

ZL14 House numbers (for use in ZL17+)

We have the house numbers. The style is just not displaying them.
@manuelroth Want to talk a look at the other proposals?

Great! I didn't know http://dev.vectortiles.osm2vectortiles.org/ - I had used our own styling plus http://osm2vectortiles.org/maps/ to check data density.
Seems that you have solved most of the issues already. I have updated the list accordingly. Mainly in ZL7, 9 and 12 I still see problems.

ZL 5 osm2vectortiles vs ZL 6 Google
Roads on z5 are fine now:

ZL 11 osm2vectortiles vs ZL 12 Google Maps
The rivers in Allmendingen are tagged as waterway=stream. Mapbox shows stream from zoom level 13 on. So we won't show them already from zoom level 11. However I found out that waterway=river are already shown from zoom level 7 on. Implemented this in the following pull request https://github.com/osm2vectortiles/osm2vectortiles/pull/298 .
ZL 12 osm2vectortiles vs ZL 12 Mapbox Street v7
Bigger water polygons are as of PR https://github.com/osm2vectortiles/osm2vectortiles/pull/299 show from zoom level 11 on. Minor roads are also visible.

Great that you are caring about these details, guys!
One thing mentioned in a checkbox but not illustrated yet: I think landuse=residential is important (even if Mapbox doesn't seem to agree). Two screenshots from http://Maptoolkit.net (our old raster rendering), look at the grey areas:
ZL9 Raster (= ZL 8 Vector):

ZL11 Raster (= ZL10 Vector):

There are two problems left here which is the city label density #308 and landuse residential #307 which will continue in separate issues since they are larger features.
The other things in this issue have already been resolved by @manuelroth (thanks!!).
BTW @muesliq nice article about Google Maps label placement http://www.justinobeirne.com/essay/what-happened-to-google-maps.

One thing mentioned in a checkbox but not illustrated yet: I think landuse=residential is important (even if Mapbox doesn't seem to agree).

at z8 what you generally want is built up place polygons, not landuse=residential


GH-31 ST Nucleo-WL55JC binary decoder

Issue #, if available:
#31
Description of changes:
Added a payload decoder for the ST Nucleo-WL55JC development board.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks a lot Greg, your contribution is highly appreciated!


Updates dependencies

Django 1.9.7
Also testing for Django 1.10a1
Updated packages
Fixes some 1.10 incompatibilities

[Current coverage][cc-pull] is 96.62%

Merging [#175][cc-pull] into [master][cc-base-branch] will increase coverage by <.01%

@@             master       #175   diff @@
==========================================
  Files            40         40
  Lines          2725       2726     +1
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           2633       2634     +1
  Misses           92         92
  Partials          0          0

Powered by Codecov. Last updated by [2e062a2...1b09ad5][cc-compare]
[cc-base-branch]: https://codecov.io/gh/Koed00/django-q/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/Koed00/django-q/compare/2e062a2ba9e32efd2ba35ca8ad03f1331625aabb...1b09ad53aaac5fd2f66005830492d680634528b6
[cc-pull]: https://codecov.io/gh/Koed00/django-q/pull/175?src=pr


how can I use serene in an empty asp.net mvc project

can i use serene code generator and serene library in my custom mvc project with
custom template without using serene project template

I think i already answered this in Serene


Add a loading indicator when enter is pressed on login/sign up page or when user presses the the login/signup button

Show a loading indicator that replaces the login button with a button that has a circular loading indicator in between.

State change:
[ Login ] ----> user clicks the button or presses enter -> form validation -> [    O   ]     (button dims a bit and circular loading is shown inside the button)

Hi
I want to work on this issue.
Please assign this to me.

@ayushi0809 Do let me know if you're facing any issues or if more context is needed.

React components are not rendering .
Home page is a blank white screen

Can you check if there's any error in the browser console or the terminal and maybe share that here along with the screenshot?

Yes

I am not able to understand this error


Adding Quartz Composer

Fixes #2343

@ankurp Please the requirements to add a new language in Linguist as per the contribution guidelines.

@pchaigno Will do

:flags: flagging this as stale :flags:


Textual corrections

Found some typos, then some more going through all examples, so I fixed them.
feel free to include or reject.

HI @rob040
This fixes are always very welcome!
As you've noticed, I often reverse the letters of words :fearful:
Without also considering my "far from perfect" English.... :disappointed:

no worries. nobody is perfect, me neither.
To me its also an exercise in getting used to git...
There is one more push, that apparently does not amend the PR automatically.


Discussion: CoC Violations & Accountability : Node's future

So this is going to be a little unorganized, but this is in regards to the TSC vote, and frankly I don't think they should have been the ones that made that decision.
https://github.com/nodejs/TSC/issues/310
How can we have CoC accountability when that apparently doesn't even extend to the core contributors of a project? There are MULTIPLE conduct violations. What does one have to do to actually have any repercussions?
I'm frankly appalled and confused why this decision was left up to a select few, though I'm not surprised the outcome given the lack of diversity and representation on the TSC.
So what can we do? If anything? I want Node to be a welcoming and helpful community, and I want people to feel safe.

Code of Conduct: https://github.com/nodejs/TSC/blob/master/CODE_OF_CONDUCT.md

To be clear, I want this to be a discussion that's not limited to just members of the CommComm. Since we are here to support the community, I want to hear from everyone.

Thanks Rachel for opening this issue. I’d add are also hear to represent the community, including the members who left Node core because of the actions for Rod and others in the past. We hear you.
Do Meeting Notes or a recording of the TSC vote exist? Is it known who voted what and who abstained?

Do Meeting Notes or a recording of the TSC vote exist? Is it known who voted what and who abstained?

The vote was a confidential vote. I don't know who voted for what, and I'm not sure anyone does given the tool we used.

@gr2m in the issue posted by James, it says

There are 13 members of the TSC. 10 members voted, two abstained, and Rod did not participate.

The vote came down 60% against removing Rod from the TSC and 60% against asking Rod to voluntarily resign.

Which basically just says to me, and the ENTIRE community, that the majority of the people making the technical decisions don't care about anyone involved in the project but themselves. This will 100% hurt the Node community.

It's very difficult to see this sort of stuff happen: there are those of us who have tried to do the work in the past to prevent this from happening, and people like Rod were directly responsible from preventing those efforts from taking root. There is a subset of the Node community, now growing in number as other leave, that believe meritocracy is the way to run things, and that harassment and CoC violations are justified as long as someone has enough technical contributions.
As far as concrete stuff goes: it's important for Node.js to have a public enforcement process, and for any internal leadership organizations to follow that as closely as possible. Folks that openly advocate against CoC complain that they can be used to ban random people for slip-ups but what we're seeing is that when you lack an enforcement process, what actually happens is that the people you like get away with it, and the people you don't get banhammered at a moment's notice.
This is pushing contributors away. I can say that as far as any communities I'm in, Node.js feels like an unsafe project to participate in for anyone in marginalized situations. I've had many conversations with very capable and talented developers who have outright told me they won't participate due to Node.js defending certain actors: Rod being one of them. Choosing to not remove or even make participation conditional on drastic changes in observed behavior is an active decision by Node to create a community that excludes others.

This will very negatively affect the community in the long term if we don’t correct it, if a committee like the TSC can simply vote to make exemptions from its own rules for one of its members. This is frankly corrupt.

So this is going to be a little unorganized, but this is in regards to the TSC vote, and frankly I don't think they should have been the ones that made that decision.

We shouldn't have been the ones but by technicality that is the way the written rules work, as of the current time. 😞

This is incredibly corrupt and the mis-use of science to protect anyone from being accountable for the actions and behavior is ridiculous. I have bipolar disorder, but I understand rules and how my actions effect other people.
We need more diversity in open-source, and this is one of the reasons there's so little.

Edited to add in the photo of the information that was removed because it was "unfair to Rod" because frankly, Rod's behavior is unfair to countless numbers of individuals from preventing them from wanting to contribute to the project. And he should absolutely be held accountable for his actions.

We have a pull request out that I've requested we wrap up @rachelnicole that partially answers this in regards to CoC accountability. We've(TSC/moderation folks/CommComm) long recognized that the TSC being assigned escalation of Moderation isn't something they as a group alone would like to be responsible in dealing with. That pull request is here. This actually makes us, CommComm, also responsible and also means we have voice to help make it better. Prior, only collaborators had view of Moderation and that doesn't match up with how a Code of Conduct and reporting guidelines get worked out, especially in escalation.
In regards to a vote, this is one vote, from one committee. There are other groups, such as the CTC, the CommComm, and the Board of Directors who are capable and can also voice what they'd like to see happen for moderation and leadership guidelines. This communicates our values, as a community. The vote on the TSC voices the decision of the TSC.

To all CommComm members, lets review this Moderation issue asap. https://github.com/nodejs/TSC/pull/276/files

I'm really not sure why @jasnell removed the list of issues from the other post—if they weren't enough to remove him then why is anyone upset about describing them?
As for the community as a whole, to be honest reading through the CoC again I wonder if it's a bit vague and hard to enforce for anything outside of obvious harassment. The things originally described in the other post feel obviously out of line to me for a community leader like a "steering committee" member, but looking through the existing CoC I'm not sure if I can point to the relevant parts?
At any rate, I'd like to see Node do better.

They were removed at the request of multiple collaborators who felt publishing the list unfairly targeted Rod for harassment.

@jasnell if they felt his actions would warrant harassment, I find it odd that they are okay enough with the actions to have voted the way they did. Especially since they weren't speculations on actions, it's the clear set examples of his behavior.

Stuff like this is why I've felt zero motivation to contribute lately. 😑

@jasnell if a Code of Conduct violation has no repercussions how does that protect anyone else from harassment? Can you elaborate on that?
So far I'm seeing only Rod being protected, members of underrepresented groups quitting the committee and frankly, disappointing actions reflecting poorly on the inclusion and diversity of the Node project. Decisions like this are a slap for women, people of color and other underrepresented groups, showing there's no real commitment to challenging the status quo within Node and the tech community in general. This doesn't make them feel like there's respect and consideration for their safety. There's no free pass out of Code of Conduct for anyone, nor there ever should be. Code of Conducts aren't PR stints, but carefully written and implemented precaution mechanisms that should be effectively enforced if need be.

There's no free pass out of Code of Conduct for anyone

Would you say this is acceptable behavior by a Community Committee member? I think that this sentiment would be classified as harmful and in violation of your CoC.

I've been stuck on a Metra train that was shut down from somebody jumping. I admit this is the only reason I am making a stand here. (I am pro CoC, please do not take this as inflammatory)
Suicide should not be taken lightly, and certainly should never be wished upon anyone.

Given the issues that were reported to the tsc for consideration, there was not consensus that those represented a code of conduct violation. There were clear moderation policy issues that had been dealt with in accordance to the moderation policy. Thus far, while there are quite a few people speaking in very general terms about Code of Conduct violations, there has been absolutely no clear identification to the tsc what the specific violations were.
Additionally, those who submitted the complaint did not frame it as a Code of Conduct issue. Rather, it was framed as a "Is This How A TSC Member Should Act" issue in general. The set of bullet points I posted originally constitute the extent of the context that was provided to the TSC for consideration beyond calls for specific mitigating actions and statements about what the result would be if those specific actions were not taken. Specifically, an ultimatum was given that if Rod was not forcibly removed from the TSC, certain members of the TSC would resign. No other option or course of action was acknowledged as being acceptable to the individuals making the complaint.
With regard to at least one of the specific issues raised, there is significant disagreement among TSC members that tweets that do not, on their face, have anything to do with Node.js, posted to a personal twitter account fall under the TSCs oversight in any way other than those already documented in our moderation guidelines. We just simply do not have a documented policy or precedent that we can fall back on. I can easily say that I don't like it so I think the poster should be banned, but I am not the Benevolent Dictator of Node.js, nor do I want to be, and I have no authority whatsoever to take unilateral action.
It was agreed by everyone directly involved in the discussion, including those that have resigned from the tsc, that our existing policies required a vote given that we lacked consensus, and the requirements for such a vote are spelled out clearly in the charter we are bound to. So after we gave tsc members time to review the complaint and provide their feedback, we called for a vote. While that may seem like I'm hiding behind policy, I am not. I'm saying that there's literally no other process we could have followed.
In short: the TSC DID execute on our established code of conduct enforcement guidelines. There are just many who disagree with the outcome and who feel that the current enforcement policies are inadequate.
We do have a process for changing those policies, and there are already efforts in the pipeline for changing those. Improved moderation guidelines, mediation, escalation and even complete restructuring of the tsc body have been on the table for discussion for quite some time and are efforts that I have strongly endorsed or initiated. I invite everyone to actively participate in those efforts.

@jakeNiemiec you know that Myles wasn't telling people to kill themselves, and in the comment to him he further clarified what his intentions were.
In the issues we're specifically addressing, IMO, there were violations. Though as @jasnell elaborates above, the people who were making the decisions worked in accordance with the way things were set up, which is what a lot of us don't agree with.
Which is what I'm hoping this thread will encourage people to talk about, and if you're involved in any of the relevant committees please work to help make changes to prevent this type of thing from happening this sort of way again.

Note: non-contributor but heavy Node user.
My team and I rely on Node every single hour of our workdays. It gives me great pause that rely on a software project that does not care to enforce its CoC.
Further, it's an embarrassment to see this behavior coming from an org with such a prominent place in the modern web dev toolchain. The whole situation makes me wonder if we should be using something different.
It'd be far better for the TSC to provide oversight and thereby grant a plurality of its current and prospective contributors the dignity of a safe, professional space.

@rachelnicole I know he was being hyperbolic, but saying "[insert any group here] people, step in front of a bus" is unacceptable, even as a joke.
Interactions like this just perpetuate the notion that CoCs are used to bully people who are not part of the 'in-group'. (which is unfortunate)
If you are serious about CoC enforcement, lead by example: acknowledge the clear violation of your CoC instead of brushing it off.

@jakeNiemiec From what I can see, Myles deleted the original tweet, wrote a follow-up with much less problematic language, and tried to engage with you to better clarify intent, even going so far as to thank you for pointing out the problematic language.

If you genuinely feel like that action was a CoC violation that merits investigation, I would suggest that you look at the Enforcement guidelines and report the incident through normal channels.
Right now, it feels like a weird attempt at derailing conversation.

Written before @brianarn posted: thank you. I agree. Added this anyway, because I think it sheds some more light on the derail.
The internet is not the right venue for discussing miscommunications like this, because tone does not come across at all.
@jakeNiemiec I hear you. That was a very unfortunate phrase for you to hear. Please know that I do not think that @MylesBorins was joking - he was referencing the phrase throw under the bus, but from a perspective of altruism. He was not advocating suicide, from my perspective, but actively using your privilege to take a fall when others can't.
These sorts of difficulties do fall under the Code of Conduct, and would be a great examples for a proper moderation board to take a look at. While I understand your reading, I think that this was just a misunderstanding. For more context, please read Myles' blogpost about stepping down, where he gives a great example of someone who uses his privilege to make a statement, even if it hurts. I can't think of a better way to lead by example.

I think there's a good amount of missed connections going on in this conversation, besides the one I brought up above. I want to take a moment to thank @rachelnicole, @jasnell, @jakeNiemiec, @hackygolucky, @thefoxis, and the others here for jumping in as they are.
There two points I want to highlight in case they get lost:
From @jasnell:

In short: the TSC DID execute on our established code of conduct enforcement guidelines. There are just many who disagree with the outcome and who feel that the current enforcement policies are inadequate.

We do have a process for changing those policies, and there are already efforts in the pipeline for changing those. Improved moderation guidelines, mediation, escalation and even complete restructuring of the tsc body have been on the table for discussion for quite some time and are efforts that I have strongly endorsed or initiated. I invite everyone to actively participate in those efforts.

From @hackygolucky:

In regards to a vote, this is one vote, from one committee. There are other groups, such as the CTC, the CommComm, and the Board of Directors who are capable and can also voice what they'd like to see happen for moderation and leadership guidelines. This communicates our values, as a community. The vote on the TSC voices the decision of the TSC alone.

Everyone: let's work on fixing our Code of Conduct and the way disputes are adjucated. This vote does not have to stand as an example of Node, frozen forever in a weird, damaging "well it can't be fixed" stasis.

@jakeNiemiec this is getting off-topic, feel free to open a separate issue if you see the need to.
If the TSC followed all the processes in place then the processes are broken.
The result from the TSC vote which resulted in protecting an individual who repeatedly harassed members in the Node community to the point that they left and never came back anywhere close.
If this decision by the TSC has no consequences, any rules put in place to create and grow a safe place will loose all their meaning. And as member of CommComm I see it as my responsibility to act if I see the community being threatened to become a hostile place.

Right now, it feels like a weird attempt at derailing conversation.

I'll stop commenting since I see what you mean.
Feel free to remove my comments. It just seemed like any enforcement of a CoC requires a Twitter firestorm to get the ball rolling.

It just seemed like any enforcement of a CoC requires a Twitter firestorm to get the ball rolling.

You're not wrong. That's part of what @gr2m is getting at, and others have raised the same concerns (on Twitter). This is what happens when the processes in place, and private admonitions, fail.
It would be great to have a very clear, bullet-pointed post about where to go from here. How can I, as an enraged person (and me specifically, on CommComm), help to fix the current process. @MylesBorins calls for a merging of the TSC and the CTC. On what door can I nail this thesis? Can someone more experienced in Node.js land help me by writing this? (Happy to help draft it with you).

FWIW, I agree that the choice of words from Myles was not great. It's referencing a common phrase, but that common phrase has always been a bit problematic. It's easy to use out of habit, if you aren't careful.
Myles was good about it in that he immediately acknowledged his mistake when called out and made the effort to apologize and correct it. I know he meant well, but I know that from the context of knowing him personally. Some internet stranger could easily have misinterpreted the intent of his words. This is the core of most issues we as a community face: a lack of either context or clarity in how we communicate publicly. We can not be vague about issues like this or we alienate our community.

@jakeNiemiec hello again. My original choice of language in that tweet was quite unfortunate. I am very grateful you called it out, and was more than happy to remove it and take accountability for my mistake.
To me, that experience was a perfect use of moderation by you, and the correct response to moderation by me.
That contract is important.
At this point, if we were in the Node.js moderation process, the issue would be considered resolved.
Here is the section in the moderation guidelines outlining the steps we would follow when moderating post. Keep in mind that there is a different process in place for collaborator < > collaborator moderation. One thing that is totally acceptable in any moderation is dealing with things privately, and is often a way these matters can be sorted in an amicable way.
It appears that my original comment made it hard to trust me, that is totally fair. I'm simply asking that you give me the benefit of the doubt. I'll do my best to do better next time 👍🏽

I am upset that there is a lack of accountability for hostility whilst acting in the capacity of a steward of the community. Beyond broken processes, internal conflicts, and the efforts to fix them, I am upset that a group of people had to vote at all on whether or not to hold a person with authority accountable for causing harm to the community.
It is clearly evident to me that the the behavior laid out is counter to building a healthy and open node community. An opinion bolstered by those involved finding the behavior aggregious enough to “protect” Rod from having his comments speak for themselves. Which, despite happening online and in a (semi) public forum, have been made unavailable to the community.
Whether working through imperfect processes or not, there are several charges I would absolutely expect to influence decision making about node at all levels. I believe how this situation was handled fails each of these:

Work in the interest of the growth of Node, ipso facto the growth of the community
Rebuff behavior that is counter to the growth of the community
Promote open discussion around difficult topics

Specifically, these are things which should be upheld no matter the topic if Node is serious about building a top notch community. By all the people here lending their time, thoughts and hard work, I think its pretty clear that Node is serious about it! These actions detailed here are indicative of people being human and fallible when handling a difficult topic.
I understand there are processes in place and my guides are too simple. It is my assertion that these processes are set up to serve those larger goals, and so they maintain their relevance. .
I believe TSC made mistakes by:

Reading the CoC as a black and white tax code instead of a set of guidelines which exists to protect the community from harm of many kinds
Voting in favor of harmful behavior, where they had a chance to lead by example
Removing publicly shared information about a decision that concerns the broader community, from a place meant specifically for distributing information to the community. Thereby choosing to protect a single authority figure from potential backlash for their comments made in a public forum.

Moving forward I would like to see:

Node foundation leadership comment and apologize on the failings of this issue and the way the community was alienated in the immediate aftermath, with a plan to be better starting immediately
A CoC that is actually worth the bytes its stored in
The specifics of the issue that was voted on made publicly available (@jasnell plz restore the comment for all concerned to reference, even though ppl wont have perms to view)
Rod to be removed from the TSC

Ultimately, I think the world deserves the best Node possible, and the above are necessary first steps towards it.

I'm not sure where the image in the original issue is but it doesn't look like it's from anywhere public.

@benjamingr The image is from the original text of https://github.com/nodejs/TSC/issues/310, which was public and later edited.

Thanks for the clarification. As a collaborator that was confusing.

This is the core of most issues we as a community face: a lack of either context or clarity in how we communicate publicly. We can not be vague about issues like this or we alienate our community.

As a simple user of node, not a contributor or member or whatever to any committee or governing body; As someone who cares about the effects of a CoC on a community to bolster the capacity of that community by reinforcing positive interactions and redirecting or removing negative; As a community organizer myself who sees very little of the challenges of this and other larger communities but takes direction from their progress and motivation from their successes, it is disheartening to see this observation, as it seems at least with this core issue (nevermind the tangents) it is definitely not the case. Yes, sometimes in wildly threaded and active conversations it can be difficult to discern what's really happening. Yes, sometimes people say things that never occurred to them to be damaging. It speaks volumes though, of the precision with which certain members of the community respond to such issues, and the empathy that guides them.
With this core issue though, there was a TSC member who the committee voted to keep, who clearly advocated against a process by which they must abide yet they feel they ought to be exempt from. That seems pretty clear so far. Then after informing the community about these goings-on internally, useful context was removed which specifically pointed out compounded bad actions by this member. This was removed because it was felt that specifically pointing out violations of a code members ought to be required to adhere to and explicitly outlining bad actions of another constituted harassment. All the while, several committee members had to go to the extent of resigning in order to make a statement loud enough about how awful this is... and it's STILL being backed up by "this was the only choice we had"? Seems a woefully inadequate response. It's interesting to watch history get rewritten, and I'm glad the internet exists to continue to provide context and clarity even in situations where folks think they can "correct" the record. The only thing vague about this issue is why information that clarifies the issue ever got to be removed in the first place. The void left when toxic persons attempt to defend their behavior and the only thing they have to show for it is a recorded version of events redacted to suit their narrative resonates loudly for those fortunate enough to even have seen a pre-redacted version just hours ago. There is no attempt here on the part of the TSC to empathize or adjust for a more diverse future -- the very thing a CoC exists to facilitate; there seems only defense and justification of actions.
I get that this is not the only committee in node, and I'm grateful for y'all in this thread who are members elsewhere in the project and advocating for better. I've gone back and forth in my head on whether or not I should post this, but @rachelnicole said she wanted participation from all. So, thanks to her and all who are actively trying to make this situation better for the community and are focused on healing. If there's anything I can do to assist in your efforts, please don't hesitate to ask.

There is no attempt here on the part of the TSC to empathize or adjust for a more diverse future -- the very thing a CoC exists to facilitate; there seems only defense and justification of actions.

For the benefit of anyone not following the endless stream of notifications that is the Nodejs org, these PRs (related to TSC and governance) were either started or rapidly progressed since yesterday:

https://github.com/nodejs/TSC/pull/319
https://github.com/nodejs/TSC/pull/318
https://github.com/nodejs/TSC/pull/317 and https://github.com/nodejs/node/pull/14973
https://github.com/nodejs/TSC/pull/276
https://github.com/nodejs/TSC/pull/219
https://github.com/nodejs/node/pull/14981

were either started or rapidly progressed since yesterday:

And reflect conversations that have been ongoing for months.

@gibfahn & @jasnell thanks for adding those for more insight for people that are confused about the entire process / changes to be made in general, as I'm still definitely trying to still figure out how a lot of things work myself this is v valuable to know.

@jasnell For further clarification, these issues that @gibfahn linked to, is it only members of the TSC that can comment with suggestions or +1-ing to the things outlined? Or is it open to any individual members / other working group members / anyone?

@jacobroufa I just meant to imply that we need to put more care into how we communicate with each other to ensure context is not lost and that misunderstanding does not arise. It's easy to misinterpret the intention behind words on a screen, so it's important we think about what we say and how we say it. That is not to say that people should be punished for vagueness or the occasional error in choice of words, but that we should always strive to do our best at communicating in a clear and inclusive way.

@jasnell For further clarification, these issues that @gibfahn linked to, is it only members of the TSC that can comment with suggestions or +1-ing to the things outlined? Or is it open to any individual members / other working group members / anyone?

@rachelnicole I'm not TSC (yet--sure seems like that's going to change with the CTC merger) but I comment all the time in those repos as do others.  They can lock issues if they don't want commentary from non-TSC. I think people should feel free to comment. And if I'm wrong, you can totally blame me.
( IMO, please no '+1' comments that have no other content, but feel free to use thumbs-up emoji responses in their place.)

I'll echo @Trott comments. Comments/feedback is always welcome.

@rachelnicole @Trott The TSC repo is open for anyone to comment. In fact, I start here by almost exclusively commenting in the TSC repo.

Comment is not only welcome by all, but anyone is and always has been welcome to open pull requests that offer specific recommendations and changes to the governance policies. The requirement for landing those is at least one TSC member signoff and no open objections. Every policy that the TSC follows is reviewable and open to suggested modification by the community and has been since the Foundation was launched.

Here is some good insights by Mikeal: https://twitter.com/mikeal/status/900007597088022529

I'm bewildered by your reasons for a fork. Does your first bullet point actually fault him for apologizing to someone without begging for everyone's permission first?

@vxbinaca you are literally the first person in this whole issue to mention anything about forking node which leads me to believe (and based off some light searching) you were led here from somewhere discussing what's happening with the Code of Conduct discussion, (Iikely reddit or hn).
So please don't comment unless you have anything actually useful to bring to the conversation.

@vxbinaca As @rachelnicole mentioned, if you'd like to keep on topic to the issues in the description above, we're happy to engage. Anything else, such as the fork discussion that you've introduced, would need to be opened in a new thread per Node.js' guidelines around moderation and derailment of discussions.

if you'd like to keep on topic to the issues in the description above, we're happy to engage.

@hackygolucky @rachelnicole In line with this, I second @vxbinaca's other question, directed at this portion of the description above:

How can we have CoC accountability when that apparently doesn't even extend to the core contributors of a project? There are MULTIPLE conduct violations. What does one have to do to actually have any repercussions?

Can we clarify what the 'core contributors' actually did and what specific conduct violations occurred?
As you mentioned, these issues (and this issue) will be reaching a broader audience soon. It is important that the transgressions are clear, and not a screen-cap of a comment with links no one can follow.

@jakeNiemiec this has already been discussed at length by collaborators, there is more information and an addendum added by @jasnell at issue https://github.com/nodejs/TSC/issues/310#issuecomment-324174390

// Correct me if I'm misunderstanding(bow).
In my understanding, CommComm recognizes that it has authority and responsibility for community activities, it could overwrite the result of the voting at TSC ex-post facto.
I referred this section: Section 6. Node.js Foundation Operations.

The CC is responsible for vetting organizations that will be supported through means such as monetary sponsorship, promotion, resource provisioning, etc. for example requirements such as the organization in question having and executing a Code of Conduct or not conflicting with Node.js Foundation’s goals and priorities.

Did the meeting and the voting about that happen at CommComm? If it was held but could change nothing, then CommComm should have a right permission to overwrite results of votings at TSC if TSC makes a wrong decision related to the community activities. As an example of the concrete action, I think we could establish some specific penalties such as apology or expulsion from the org, in CoC.

it could overwrite the result of the voting at TSC ex-post facto.

No, this is not correct. The CommComm does not have review authority over the TSC. Both the TSC and CommComm are independent entities chartered separately by the Node.js Foundation Board. Both are bound to follow their respective charters as approved by the Foundation. The CommComm can certainly offer it's opinion on the TSC decision (and I invite it to do so) but it cannot override the TSC's decision.

@watilde I believe that part of the governance refers to organizations that Node directly supports, like code with initiatives such as Code & Learn, Node School, Node Together, etc. And doesn't extend jurisdiction to adjacent committees such as the CTC, or TSC.

What @rachelnicole said ;-)

I read https://github.com/nodejs/TSC/issues/310#issuecomment-324174390

These details are accessible to anyone who is a member of the Node.js GitHub Organization

(and collaborators)

@jakeNiemiec this has already been discussed at length by collaborators

@rachelnicole Any non-collaborator only gets a vague idea of what happened. How about some transparency? Why is this issue even open to the public if we don't get details on what happened?

@jakeNiemiec ... the Node.js Foundation Board of Directors is in the process of preparing a public statement that should (hopefully) provide greater context and insight. I originally posted that issue with the details included because I strongly feel that the transparency is necessary (I still do). I pulled it because of significant feedback that posting it was unfair. I have since consulted with members of the community and the Node.js Foundation Board and have landed on the temporary compromise of having the contextual details available in the private repo. I'm still working the issue and personally still prefer full transparency.
The issue was posted publicly because the TSC charter requires that a public issue be opened when these kinds of matters come up. The charter is less clear on exactly what level of detail those issues require which is a gap that I'm currently working to fix. My personal preference would be full transparency on all issues, including full transparency on who voted and in which way.

@rachelnicole @jasnell Thanks for the clear explanation! I could get the right understanding :)
Since CommComm is a good place to hear opinions from the communities, I thought that it would be nice if there were seats at the time of voting like this time if the topic is related to the community instead of very technical stuff.

@watilde i'm pretty sure that's what they're trying to do in regards to the proposed remerger of TSC / CTC & the establishment of the Moderation group with more representation across the board. We'll probably see more progress and updates about things as Issues & PR's start getting closed.

i'm pretty sure that's what they're trying to do

Yep. There are a couple of open relevant threads:

The proposed changes to the Moderation Policy establishes a separate Moderation Team staffed by both the CommComm and TSC. It will be the responsibility of this Moderation Team to initiate moderation actions as opposed to the current arrangement managed solely by the TSC.

The proposed changes to the GitHub org management policy establishes that CommComm members may be added as Owners in the GitHub org, allowing them to perform actions such as adding/removing members from teams or even banning in accordance to the moderation guidelines. Membership in this group would be subject to approval from both the TSC and CommComm

The proposed changes to Working Group oversight would allow Working Groups chartered under the TSC a process of vacating TSC decisions and requesting that matters be revisited. This would not extend to CommComm working groups, but it does provide an additional layer of oversight that is needed.

the Node.js Foundation Board of Directors is in the process of preparing a public statement that should (hopefully) provide greater context and insight.

@jasnell  I could not find any information on conduct violations in the statements released today:
https://github.com/nodejs/board/issues/67
https://github.com/nodejs/node/issues/15011
As far as I can tell, either:

a. There was some offencive/scandalous event and it was discussed "offline" amongst the parties here.
OR
b. This is a witch hunt in reaction to a fair vote*. From "the accused's" radio silence on the matter, a defamation lawsuit would not surprise me (depending on your local laws, you can't make accusations based on private facts)

(*: The misconduct is being treated as a foregone conclusion, no uninvolved layman will sympathise with "we all need to punish this person. Trust us they did bad things we can't tell you about.")
Despite what the answer to the above is, withholding an official list of accusations has led to (less than reputable) media/individuals either smearing the members who left after the vote or making wild, hyperbolic accusations about "the accused".(at least partly because there were no concrete conduct violations to point to).
No matter who you agree with or what side you are on: the Node.js community loses
So I ask again (as per the issue description above):
What specific conduct violations occurred?
@jasnell @rachelnicole: I am all for an inclusive CoC, but my persistence comes from the fear that I, or someone I know, will be targeted based on secret transgressions.

It was discussed publicly, however the details were removed from the post due to fears that they'd encourage targeted harassment. (Personally, I disagree with that response. I think the accountability is necessary.)

As I have said in follow up posts in twitter, the issues reported to the TSC included Moderation Policy violations (some acknowledged, some contested) and concerns around tweets that the individual posted to their personal twitter feed that several peers on the TSC felt were not becoming of a TSC member. At least three TSC members further indicated that they no longer felt comfortable working with this individual due to what they perceived to be a long running pattern of behavior that was not becoming of a TSC member. The specific issues raised to the TSC were never framed as CoC violations by the individuals making the claims so we never framed them as such to the TSC body.

Re: the comment witch hunt in reaction to a fair vote. There is certainly a significant degree of truth in this statement. From the moment I posted the notice, even before I redacted the specific list of issues reported, a barrage of posts to social media were made that, in my opinion, were complete gross mis-characterizations of the actual events that occurred. There has long been an unhealthy back and forth between specific individuals in this community that has led to ongoing challenges. This is hardly the first incident and, unfortunately, not likely to be the last. No one side of the discussion deserves more blame than the other and unfortunate decisions on methods of interaction, methods of approaching issues, and methods of communication have been made by more than just this one individual in question. My general recommendation is to ignore the hyperbolic vitriol on Twitter and not to give in to the artificial sense of urgency it creates.
Removing the list of issues as I did, which was done as a response to individuals who felt publishing the list was unfair and would be further damaging, had the opposite effect of what was intended by those who had requested that I remove them. At this point in time, I do regret having removed those.
At this point in time, my focus is on ensuring that the processes are in place to deal more effectively with  these kinds of disputes, ensuring that there is both fairness and accountability throughout -- not only for the individuals being accused of wrong doing, but accountability of those reporting issues, to ensure that the possibility of abusing the system is lessened. Over the nodejs/tsc repo there are a number of open pull requests the update guidelines for all of this that do exactly that.
No system is perfect and I think it's safe to say that Psychology and Mediation Skills are not commonly taught in CompSci 101 so we're all pretty much learning as we go here.

@jasnell you are scooping me again. I was looking for the right forum and right words to say just that.
I can not agree with you more!

No system is perfect and I think it's safe to say that Psychology and Mediation Skills are not commonly taught in CompSci 101 so we're all pretty much learning as we go here.

That might be a good sign that it would be helpful to have the Foundation (which I assume would have the resources) provide that kind of expertise, rather than going with “we don’t know any better because we’re not professionals”.

I'm closing this thread now as I feel the constructive conversation has tapered out, and we can wait on the additional statements from the board.
If anyone has anything else they'd like to discuss, please feel free to open your own issue.

the constructive conversation has tapered out

Are you seriously kidding me? Finally a good di

@jakeNiemiec We've got some great progress happening in regards to the reasons this issue was opened in other PRs, such as adjusting moderation guidelines, the teams, and how we execute Codes of Conducts, but the conversation happening isn't addressing the issue as filed. Please file an issue that addresses your concern directly or hop on one of the appropriate issues or comments. We've got a lot of activity this week in the comments, so it's especially important for us to keep these focused in scope.

@jakeNiemiec no, I'm not.
Feel free to open your own issue for additional concerns that are relevant to the questions you're asking, as they're separate from what this issue was opened for.

@jakeNiemiec we do what we can, it is all on our free time besides our day-to-day job. I understand you are upset, but please remain constructive, the phrase "Are you seriously kidding me" is a personal attack and is not helping your cause. Please create a separate issue

@hackygolucky

the conversation happening here, today, isn't addressing the issue as filed.

@rachelnicole

...they're separate from what this issue was opened for

The filed issue is Discussion: CoC Violations & Accountability, we are discussing the CoC Violations with @addaleax, @refack and @jasnell providing good discussion. You immediately locked and stamped that out.  I sure would not feel safe having you in a position of leadership with this kind of behavior.

@rachelnicole I'm taking the "unlock" at you still leaving room for discussion.

That might be a good sign that it would be helpful to have the Foundation (which I assume would have the resources) provide that kind of expertise, rather than going with “we don’t know any better because we’re not professionals”.

I strongly believe that https://github.com/nodejs/TSC/pull/276 (the TSC requesting to hand over Moderation responsibilities to a new dedicated Moderation team, and appoint a Mediator as the final jurisdiction) is an excellent solution for the problem of "CoC Violations & Accountability".

@jakeNiemiec can I ask you to rephrase your last comment? I think I understand your intent, but it comes off as a personal attack.

Going to lock this conversation. Not going anywhere productive with the issue at hand, and - as suggested - other discussions can and should happen in other issues.
❤

@refack no the unlock was because we aren't supposed to lock conversations unless it's been reviewed by the moderation team, so it was a mistake.
And @jakeNiemiec no. The thread was opened for what we can do as a community going forward, it wasn't opened to question whether you thought a supposed violation is a 'witch hunt'. That conversation would be more important and relevant in a discussion about actual content of a Code of Conduct, which are happening elsewhere.

@refack Thanks, see edit above.

it wasn't opened to question whether you thought a supposed violation is a 'witch hunt'.

@rachelnicole Please read it again, I was not saying that. I am only asking what what the violations were. No source seems to have a clear answer.

The thread was opened for what we can do as a community going forward

I will rephrase: What happened in those private issues that we need to move forward from?
(Please do not take my frustration as an attack. It seems like there are different teams that I am unaware of...like I am speaking the wrong language or just being outright ignored.)

Noted for discussion in Moderation. Locking again.
Want to restate: if you are interested in having discussions about Node.js and what the CommComm can do to help, please don't hesitate to open an issue.
❤

Locking a thread is not uncommon in the Node.js repos. If someone is not heeding requests after derailment of a topic happens(this happens quite often, and that doesn't mean you are a terrible person), then moderation is requested because the sheer velocity of an argument can cause a breakdown in communication. Sometimes locking is used as a cooldown mechanism.
Thanks for being patient y'all.
If it wasn't explained already, the image listing grievances in this issue was removed by @rachelnicole because our policies handling moderation and conduct do not have us publicly listing out reports. Requests for moderation and administering those requests occur in a repo where collaborators can try to tackle the conflict as it is occurring and attempt to reach out to the parties privately. We don't have a policy of publicly documenting a person's behavior, and it is also kind to protect those who were potentially harmed in said behavior(because they often become targets), but also that the person in potential violation sees some pretty serious ramifications, too.


errorAudioEngine

First of all I love this project you are amazing!
Android works fantastic but when I call:
SpeechToText.instance.StartRecording("say something...");
on iOS I get:
errorAudioEngine Description: (null)
in Xcode and nothing else happens. The result callback is never called. Any ideas?

which version of iOS you are using? if your version is 13.2.x.
Please check this link: https://forums.developer.apple.com/thread/125279

yeah I am on 13.2 thanks so much for checking into it sorry I missed that. I will wait for the update.

this issue still happens on 13.3, any idea why?

ignore this feature on 13.3, or use google API instead


[HAC 267] Update createStore to pass in sharedScope object over function

We introduced a breaking change in the latest SDK while adding the sample app in this PR. This should resolve the issue around the sharedScope object.
See https://issues.redhat.com/browse/HAC-267

/retest

/retest

/retest

/retest

@florkbr the prow is failing because of missing type, here is a PR to re-export it once again https://github.com/openshift/dynamic-plugin-sdk/pull/89

@karelhala sorry - I forgot I had this open! I've published your changes in alpha7 and bumped in this PR. Please re-review!


Changed hash

https://github.com/jlobos/instagram-web-api/blob/e85a0f603e5be9e147606feed73a5057d74c5c60/lib/index.js#L204
the new hash should be 9b498c08113f1e09617a1703c22b2f32
otherwise this method will return (from yesterday): {"message": "execution failure", "errors": [{"message": "execution error", "locations": []}], "data": {"hashtag": null}, "status": "fail"}
@jlobos

thanks, i had this problem and solved it thanks to you
how did you get this hash?

This hash stopped working for me. Do you have a new one?


Update pom property fabric8.archetypes.release.version to 2.2.180

[merge]

ok to test

[merge]

fixed in a separate PR


Extend rule to_text to support upto the 5th(fifth) occurences.

Hi Can I get this merged to master


Beta Release - v0.03-beta.0

[x] #93
[x] #96
[x] #90

[ ] Integrate

[x] #88
[x] #85
[x] #82

[ ] Integrate

[x] #76

[ ] Integrate

[x] #72

[ ] Integrate

[x] #70

[ ] Integrate

[x] #69
[x] #64
[x] #58
[x] #53 - (parts I am doing for this release are done. I should really split this issue up.)
[x] Cloth Map

[x] #97

[x] Randomize Mantras
[x] Randomize Rune locations
[x] Dungeons and shrines more thematically placed
[x] Randomize Word of Passage
[x] Load for encoded parameters
[x] #25
[x] Start with sextant
[x]  #104

[ ] Integrate

[x]  #107

[ ] Integrate

Bugs

[x] #95
[x] #86
[x] #66
[x] Spirituality Shrine in the wrong place

Oh boy. Only integration of all the ones that required game code changes and then updating all the byte offsets.


A problem about position embedding

Hi,
In the process of reading the code, I wonder whether transtrack really needs to use position embedding. Where are position embedding used in your work? Whether position embedding is not used at the encoder end, but only at the decoder end. In addition, is it unnecessary to use mask in the field of image processing?
Thank you.

Hi~

The position embedding is used in the encoder, lvl_pos_embed_flatten.
In our implementation, the position embedding is not used in the decoder. We set query_pos as NONE,  query_embed.
Mask is used to set the padding area as zero. mask


ng-attr-infinite-scroll does not work

I am trying to have the scrolling function run after my list, that is shown to the user, loads from the server to avoid an infinite loop if the browser window is big enough (no scrolling is needed). So I am assigning infinite-scroll after the list is loaded. My problem is that the command ng-attr-infinite-scroll  does not work.
Error: Syntax Error: Token '{' invalid key at column 2 of the expression [{{vm.scroll}}] starting at [{vm.scroll}}].
It works if I remove the infinite-scroll dependency.

You should post some code to look at.

looks like a dupe of #220


Add java args to 2.2.0 manifest

Signed-off-by: Sayali Gaikawad<EMAIL_ADDRESS>Description
2.2.0 build were failing for opensearch component due to missing java args. Adding it in this PR
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Maybe take up https://github.com/opensearch-project/opensearch-build/issues/2044? :)

Hey @dblock , @peterzhuamazon is gonna look into it.


Add a name_to_register routine to convert names into register numbers

This PR adds a converse of register_name, i.e. a function that converts a string register name into a register number. It's useful for debugger command-line interfaces.
Please let me know if this needs a test case.

I haven't looked at what gdb/lldb do, but you may not even want to use the DWARF register numbers in user interface code

Yes, more likely these are going to be used only as helper methods and not directly in the UI code.
Thanks for the review!


TFLite Named Inputs and Outputs

Using models with multiple inputs and outputs it would be helpful to have the names of the input and output channels available inside the Java and C++ APIs for TFLite.
System information

TensorFlow version (you are using): latest
Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state.
The model inputs and outputs can be listed and queried by size but not by name (no argument to get name of a Tensor or get input/output tensor names from an Interpreter. It would be very helpful for using models if you could get the names of the inputs and outputs particularly since many models have multiple of each (that are often not discriminated by size).
Will this change the current api? How?
It would just at methods .getInputNames and .getOutputNames to the org.tensorflow.lite.Interpreter class or add .name to the org.tensorflow.lite.Tensor class
Who will benefit with this feature?
It would make it a lot easier to have backward compatible models (newer versions predict more features and code doesn't always have to use all of the outputs a model provides). It would also allow reusing the same model for different applications and have the code select the output with the correct name rather than hard coding an output index to take or checking by output size (my current solutions).
Any Other info.

With the interpreter class in python you can easily get names
# Load TFLite model and allocate tensors.
interpreter = tf.lite.Interpreter(model_path=str(tflite_path))
interpreter.allocate_tensors()

# Get output tensors.
output_details = interpreter.get_output_details()
for c_output_details in output_details:
    print(c_output_details['name'])


[Script]: Open website by speaking

Aim
I would to automate any website opening just speaking using PYTHON program
Details

Adding speaking functionality
Adding website opening functionality
Adding background working of the program

Record

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

@avinashkranjan @1e9abhi1e10 @Yashbhadiyadra sir, please assign this project to me

@avinashkranjan @1e9abhi1e10 @Yashbhadiyadra sir, please assign this task to me so that to create pull request and contribute in GSSoC'23

@avinashkranjan @1e9abhi1e10 @Yashbhadiyadra sir, please assign this project to me to contribute under GSSoC'23 program

@avinashkranjan @1e9abhi1e10 @Yashbhadiyadra sir, i am ready with the project and want to create a pr. Please assign it to me

@avinashkranjan @1e9abhi1e10 @Yashbhadiyadra sir, i please assign this project to me so to create a valuable pull request and contribute under GSSoC'23 program

/assign


Update changelogs

There have been releases but not updates on the changelog.

@zxqfl?

So, Codota does the updating now, but the changelog is still really outdated...?

Yeah, cc. @amircodota @nimrod-codota

Hey @lovesegfault, thanks for heads up on this one
See https://github.com/codota/TabNine#230---235-febuary-10-2020 for the updated changelogs

The changelog hasn't been updated since this was closed.

please update the changelog.