Keywords Trigger Snippet Insertion Prematurely

Description:
When using the snippet feature in Raycast, the snippet gets inserted as soon as the keywords are typed. This behavior interrupts the normal flow of typing and can be frustrating for users who need to complete their input before the snippet should be inserted.
Steps to Reproduce:
1.	Open Raycast and go to the snippet feature.
2.	Type in the keywords for a specific snippet.
3.	Observe that the snippet gets inserted immediately after typing the keywords.

Expected Behavior:
The snippet should only be inserted when the user confirms the insertion, such as pressing a specific key or completing the keyword input with a defined action.
Actual Behavior:
The snippet is inserted prematurely as soon as the keywords are typed, without any additional confirmation from the user.
Environment:
•	Raycast version: 1.80.0
•	OS: 14.5（23F79）

Hey @yucchi-p! This repository is for issues related to the ray.so ecosystem. Support questions are better asked in the community Slack or by emailing<EMAIL_ADDRESS>To answer your question, you can assign a modifier, such as !td.


Each Child in a list should have a unique "key" prop.

Background:
The ApiDetails.jsx component has a map that needs to pass the key prop to the elements it's iterating through.
Objective:

Fix this error message that is originating in the ApiDetails.jsx component, the path to the component is /site/src/components/ApiDetails.jsx

Hint: <React.Fragment>...</React.Fragment>

react.development.js:220 Warning: Each child in a list should have a unique "key" prop.

Check the render method of `ApiDetails`. See https://reactjs.org/link/warning-keys for more information.
    at ApiDetails (webpack-internal:///./src/components/ApiDetails.jsx:8:20)
    at eval (webpack-internal:///../node_modules/.pnpm/@mdx-js+react@1.6.22_react@17.0.2/node_modules/@mdx-js/react/dist/esm.js:154:30)
    at section
    at eval (webpack-internal:///../node_modules/.pnpm/@mdx-js+react@1.6.22_react@17.0.2/node_modules/@mdx-js/react/dist/esm.js:154:30)
    at wrapper (webpack-internal:///../node_modules/.pnpm/@mdx-js+react@1.6.22_react@17.0.2/node_modules/@mdx-js/react/dist/esm.js:149:25)
    at eval (webpack-internal:///../node_modules/.pnpm/@mdx-js+react@1.6.22_react@17.0.2/node_modules/@mdx-js/react/dist/esm.js:154:30)
    at MDXContent (webpack-internal:///./api/web5-js/index.mdx:19:1339)
    at MDXProvider (webpack-internal:///../node_modules/.pnpm/@mdx-js+react@1.6.22_react@17.0.2/node_modules/@mdx-js/react/dist/esm.js:139:46)
    at MDXContent (webpack-internal:///../node_modules/.pnpm/@docusaurus+theme-classic@2.4.1_react-dom@17.0.2_react@17.0.2_typescript@5.1.6/node_modules/@docusaurus/theme-classic/lib/theme/MDXContent/index.js:13:25)
    at div

Picking Up This Issue:

If you'd like to work on this, please comment "picking this up" below, and I'll assign the issue to you

Questions:

If you need assistance or clarification, feel free to comment below.
Feeling overwhelmed? Join our #hack-together channel and collaborate with a buddy.
New to open-source? Check out our Hacktober #getting-started channel.
Leaderboard: Check your ranking after finishing this task.

Resources:

Docusaurus Documentation: Familiarize yourself with how Docusaurus works. Here's the official documentation.
Creating a Pull Request: If you're new to GitHub and unsure how to create a pull request, follow this step-by-step guide.

Remember, communication is key! If you have any questions or face any challenges, we're here to help so please don't hesitate to reach out.
Good Luck! 🍁

@dayhaysoos I would like to work on this.

@dayhaysoos picking this up

@pateldivyesh1323 yay! I'l assign it to you now.
I'd also like to note that Hacktoberfest officially kicks off on October 1st. Contributions made before the event may not be eligible for the challenge. However, feel free to start working on it, but I'd recommend holding off on submitting your PR until the event begins.

to be eligible for Hacktoberfest's official prizes make sure you're registered, registration opens September 26th.

Reach out if you need any help 🥳

@rishabhpathak359 Hey there! Thanks for your enthusiasm to contribute. 😊 Someone got in just a bit ahead of you on this issue, but don't worry! We have other open Hacktoberfest tagged issues that you might find interesting.

developer.tbd.website
web5-js
dwn-server
dwn-sdk-js

Also, we'll be adding more issues throughout the month of October, so there will be plenty of opportunities to jump in. If for any reason the current assignee can't proceed with this one, I'll definitely keep you in mind and reach out. keep an eye on our events-and-updates channel in discord. Thanks for being a part of our Hacktoberfest journey!


Hints Documentation

Hi @cicr99, let me know if this become available again, I would love to help!


disconnect on .update() returns a P2035 error code with 1 element

Bug description
The disconnect operation field on .update() method results in:
PrismaClientKnownRequestError:
Invalid `db_helper_1.db.audience.update()` invocation in
.../jobs/out/models/audiences.js:19:36

  16 };
  17 exports.connectCustomersToAudience = connectCustomersToAudience;
  18 const disconnectCustomersFromAudience = async ({ audienceId, customersId, }) => {
→ 19     return db_helper_1.db.audience.update(
Assertion violation on the database: `too many bind variables in prepared statement, expected maximum of 32767, received 32768`
    at An.handleRequestError (.../node_modules/@prisma/client/runtime/library.js:174:6929)
    at An.handleAndLogRequestError (.../node_modules/@prisma/client/runtime/library.js:174:6358)
    at An.request (.../node_modules/@prisma/client/runtime/library.js:174:6237)
    at async bruh (.../jobs/out/index.js:84:5) {
  code: 'P2035',
  clientVersion: '4.15.0',
  meta: {
    database_error: 'too many bind variables in prepared statement, expected maximum of 32767, received 32768'
  }
}

How to reproduce
Use disconnect in the .update() method to disconnect some records.
With the DEBUG="*" variable, there is some output about the call:
  prisma:client  Prisma Client call: +706ms
  prisma:client  prisma.audience.update({
  where: {
    id: 'cliu3rn7z0001fwn5963n9s15'
  },
  data: {
    customers: {
      disconnect: [
        {
          id: 'clionpeff005efwc1qf8eofr3'
        }
      ]
    }
  }
}) +1ms
  prisma:client  Generated request: +0ms
  prisma:client  mutation {
  updateOneAudience(
    where: {
      id: "cliu3rn7z0001fwn5963n9s15"
    }
    data: {
      customers: {
        disconnect: [
          {
            id: "clionpeff005efwc1qf8eofr3"
          }
        ]
      }
    }
  ) {
    id
    description
    status
    filters
    name
    createdAt
    updatedAt
    deletedAt
    shopifyDomain
  }
}
 +1ms
  prisma:client:libraryEngine  sending request, this.libraryStarted: true +104ms
  prisma:client:request_handler  PrismaClientKnownRequestError: Assertion violation on the database: `too many bind variables in prepared statement, expected maximum of 32767, received 32768`
    at Bs (.../node_modules/@prisma/client/runtime/library.js:31:5919)
    at rr.buildQueryError (.../node_modules/@prisma/client/runtime/library.js:109:903)
    at rr.request (.../node_modules/@prisma/client/runtime/library.js:108:4165)
    at async An.request (.../node_modules/@prisma/client/runtime/library.js:174:5887)
    at async main (.../jobs/out/index.js:84:5) {
  code: 'P2035',
  clientVersion: '4.15.0',
  meta: {
    database_error: 'too many bind variables in prepared statement, expected maximum of 32767, received 32768'
  }
} +0ms

Expected behavior
The customers should be disconnected from the audience.
Prisma information
model Customer {
  id                    String    @id @default(cuid())
  audience              Audience[]
}

model Audience {
  id          String         @id @default(cuid())
  customers   Customer[]
}

export type CustomersToAudience = {
  audienceId: string;
  customersId: string[];
};

export const disconnectCustomersFromAudience = async ({
  audienceId,
  customersId,
}: CustomersToAudience) => {
  return db.audience.update({
    where: {
      id: audienceId,
    },
    data: {
      customers: {
        disconnect: customersId.map((id) => ({ id })),
      },
    },
  });
};

Environment & setup

OS: Arch Linux
Database: PostgreSQL (on Docker)
Node.js version: v20.3.0

Prisma Version
prisma                  : 4.15.0
@prisma/client          : 4.15.0
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 8fbc245156db7124f997f4cecdd8d1219e360944 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 8fbc245156db7124f997f4cecdd8d1219e360944 (at<EMAIL_ADDRESS>Format Wasm             : @prisma/prisma-fmt-wasm 4.15.0-28.8fbc245156db7124f997f4cecdd8d1219e360944
Default Engines Hash    : 8fbc245156db7124f997f4cecdd8d1219e360944
Studio                  : 0.484.0

Can you please turn on query logging (https://pris.ly/d/logging) and see what query it is trying to execute before and when it crashes?

I tried to log the queries but it logged just a bunch of BEGIN, SELECT and COMMIT. The problematic UPDATE was not being printed.
I just tried again and the query works with no change in the configuration 🤔. I'll do other tests.


add the workflows filter

Closed in favor of other ticket  that's been linked to Linear Ticket

https://github.com/RelevanceAI/relevance-workflows-core/pull/49


Can't find deployment on AWS web console?

I was able to successfully deploy my flask-based API to AWS and I know have an API Gateway url (wooot!). I logged into the AWS web dashboard to look at some information on these services and how I'm using them (API Gateway + Lambda) and I can't find them anywhere. When I run zappa status in my local terminal it does show these services are being used and I can confirm the API is reachable via a curl command.
So where are they? I'm logging into the same account/email address I used to create the IAM User and Group that creates the service.
Context
I'm running zappa from python 3.6, using a virtual environment. Everything is looks fine. This is what I get when I type zappa status (I've censored some of the values):
Status for model-api-dev:
	Lambda Versions:      11
	Lambda Name:          ***************
	Lambda ARN:           arn:aws:lambda:us-east-***************
	Lambda Role ARN:      arn:aws:iam::***************
	Lambda Handler:       handler.lambda_handler
	Lambda Code Size:     74550112
	Lambda Version:       $LATEST
	Lambda Last Modified: 2020-09-16T17:40:10.537+0000
	Lambda Memory Size:   512
	Lambda Timeout:       30
	Lambda Runtime:       python3.6
	Lambda VPC ID:        None
	Invocations (24h):    0
	Errors (24h):         0
	Error Rate (24h):     Error calculating
	API Gateway URL:      ***************.us-east-1.amazonaws.com/dev
	Domain URL:           None Supplied
	Num. Event Rules:     1
	Event Rule Name:      model-api-dev-zappa-keep-warm-handler.keep_warm_callback
	Event Rule Schedule:  rate(4 minutes)
	Event Rule State:     Enabled
	Event Rule ARN:       ***************:rule/model-api-dev-zappa-keep-warm-handler.keep_warm_callback

Expected Behavior
I would expect if I logged into AWS I would see something in the API Gateway dashboard.
Actual Behavior
I don't see anything.
 I was in the wrong region.


Faild to get Cumb

From Friday night it doesn't work when I want to get the close price from Yahoo.
Error obteniendo los precios diarios en Yahoo del instrumento :FER.MC, error: Failed to get crumb
Error calculando los pivots semanales Sequence contains no elements
Error obteniendo los precios diarios en Yahoo del instrumento :AENA.MC, error: Failed to get crumb
Error calculando los pivots semanales Sequence contains no elements
Error obteniendo los precios diarios en Yahoo del instrumento :IBE.MC, error: Failed to get crumb
Error calculando los pivots semanales Sequence contains no elements
Error obteniendo los precios diarios en Yahoo del instrumento :MRL.MC, error: Failed to get crumb

I have try to connect with VPN from USA and I have the same error.
Thnaks

@algo0749  Can you please include more details for your issues such as the code you are using so I can help you look into this? Also please try the new version 1.6.5 that fixes similar issues for certain yahoo methods which might fix your issue

Thank you for your help.
From what I see, it's Yahoo that has changed its policies and that's why it has stopped working. In Europe, having to accept a cookie every time you access a new website is a nuisance.
It has now been solved with your new version.
Thanks again.

No problem and glad it is working for you


add CESMAC university

<EMAIL_ADDRESS>https://cesmac.edu.br/

@sirlucasm Pull request merged. Thank you!

@sirlucasm Pull request merged. Thank you!

thanks


Home page - No link add on Read and Sign the manifesto button

Thank you for taking the time to file a Feature Request report.
The issue needs to be fixed
In the home page hero section, there is a button read and sign the manifesto. there is no link added to this button. I think when the user clicks on this button then the page must be redirected to the manifesto page.

How to fix it
I can add the link to the manifesto page on the read and sign the manifesto button (on the home page).
Please assign me this issue to fix.

We don't have this feature yet so right now we can't redirect the user anywhere.


Fix typo in Overview.md

Minor change typo (explicit instead of explict) in What Casbin does: line four (4).

@bousbissikouceila could you fix the DCO?  this is solution: https://github.com/casbin/casbin-website/pull/123/checks?check_run_id=1031947730.

Sorry for the bother of not signing off my commit I used github editor to make this little typo fix.
@nodece  I did signed it off at last but as I saw that @hsluoyz already merged the change so there was no need for another pull request. Till the next time.
@nodece @hsluoyz thanks


[stable/kong] Added support for service annotations

This is a fairly simple change, to add support for annotations on the admin and proxy services for Kong.  Defaults to no annotations in 'values.yaml, with commented out examples provided.

/assign @unguiculus

/assign @shashiranjan84

/ok-to-test

/lgtm


There was a problem synchronizing your bot to Skype.

Bot Info

SDK Platform:
SDK Version:
Active Channels:
Deployment Environment:

Issue Description

Code Example

Reproduction Steps

Expected Behavior

Actual Results

Same issue persists when u deploy the code base from VS

@pushos can you provide a screenshot of the behavior you're seeing? Are you still seeing this behavior?

Closing due to inactivity and that the underlying issue has been addressed.
Linking resolved issues: #4584 and #4550 for more details.


Better build error message when not enough memory free

When building with the ./build.sh script if you don't have enough free memory then CORES will be set to 0 on this line:
https://github.com/EOSIO/eosio.wasmsdk/blob/master/build.sh#L71
This is later passed on to make as make -j 0, which throws an error because -j must be greater than zero. It would be nice if the build failed early with a nice error message instead.
FYI I ran into this issue while building in a Docker container and fixed it by allocating more memory to the container (with the --memory flag).

Resolved by PR #44


feat: add couchbase 4.2.5 release

update couchbase with release 4.2.5

:tada: This PR is included in version 1.406.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix: patchesStrategicMerge is deprecated use patches

What this PR does / why we need it:
The patchesStrategicMerge field is no longer supported and has been replaced with the patches field in the Kustomization file.
Which issue(s) this PR fixes
Fixes # FLPATH-477
Change type

[ ] New feature
[x] Bug fix
[ ] Unit tests
[ ] Integration tests
[ ] CI
[ ] Documentation
[ ] Auto-generated SDK code

Impacted services

[ ] Workflow Service
[ ] Notification Service

Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.

Thank you! @gciavarrini

/lgtm


need tiles for sound emojis

Micro:bit can play 10 sound emoji. We need graphics for the 10 emoji (see assets.ts), which currently just point to existing images:
            this.reg[TID_MODIFIER_EMOJI_GIGGLE] = icondb.tile_page_1
            this.reg[TID_MODIFIER_EMOJI_HAPPY] = icondb.tile_page_2
            this.reg[TID_MODIFIER_EMOJI_HELLO] = icondb.tile_page_3
            this.reg[TID_MODIFIER_EMOJI_MYSTERIOUS] = icondb.tile_page_4
            this.reg[TID_MODIFIER_EMOJI_SAD] = icondb.tile_page_5
            this.reg[TID_MODIFIER_EMOJI_SLIDE] = icondb.tile_value_1
            this.reg[TID_MODIFIER_EMOJI_SOARING] = icondb.tile_value_2
            this.reg[TID_MODIFIER_EMOJI_SPRING] = icondb.tile_value_3
            this.reg[TID_MODIFIER_EMOJI_TWINKLE] = icondb.tile_value_4
            this.reg[TID_MODIFIER_EMOJI_YAWN] = icondb.tile_value_5

Where can I find the existing images to reference? And how do users access these in the microcode interface? Lastly, is there somewhere I can hear what they sound like?

@clkantner  - try this MakeCode program to play with the sounds: https://makecode.microbit.org/_Yy9WcA8j0hFf
There don't appear to be any artwork associated, but maybe ask Richard.
You should build locally to see the user interface with latest mods. Click on the speaker icon to get the list of options (currently, reusing other images, no emojis, as mentioned above.  Please see instructions at https://github.com/microcode/makecode  on how to build locally.  Let me know if you have any questions.

Sorry I think I might need some help to build it... I have VS code installed, and Eric showed me how to go to localhost but it's an error right now... "can't reach page" when I go to http://<IP_ADDRESS>:7001/ . Also I don't understand the instructions, what does "mkc serve" do? When I ran it, it said it doesn't exist? "command not found: mkc" Sorry I don't really know what to do, or would it be okay to make the pixel art separately in my own program and add it in later? Or maybe I can go into the office later this week if you or Eric are there!! Thank you for your patience.

Try npx mkc serve. npx is smarter about finding node-installed utils.

Thank you so much, now I can go to http://<IP_ADDRESS>:7001/ and I see the simulator. But it's showing me the older version I think... is there a way to get the newest version in here? Do I download it? But then will it overwrite my changes?

git pull in the folder will grab latest source. mkc should be able to rebuild it on the fly, if it's running.

@clkantner - one more thing regarding artwork. I do the following:

create 16 x 16 artwork using arcade.makecode.com
copy the code from the JavaScript view
paste into assets.ts
make sure it works locally
git commit and push

Can we add these instructions to README.md?

will do.


Upgrading azure-documentdb version from 1.16.2 to latest 2.x

Spring Data Cosmos 2.1.7 is using the older version of azure-documentdb (1.16.2), so we cannot use new features, and moreover we cannot use some libraries that needs 2.x version, like the latest documentdb-bulkexecutor.
Overriding the version of azured-documentdb to the latest, we could face some issues.
Is there a way to check compatibility among these versions?

azure-documentdb has announced deprecation. It will be deprecated in Jan 2020.
Spring-data cosmosdb is moving away from azure-documentdb.
2.1.7 release introduced ReactiveCosmosReporitory based on cosmosdb v3 SDK and also uses cosmosdb v3 SDK  for implementation of DocumentDbRepository.
Since the deprecation will happen in Jan 2020, we still plan to support it.
I can update the version of azure-documentdb in spring release <IP_ADDRESS> if that works for you guys.

@apescione Good move, regarding BulkExecutor, as far as I know, there is one in .Net, but not in java. We are building BulkExecutor for Azure Cosmos V3, or probably V4. It will take some time, might be available in early - mid November.
I will close this issue now.


Stretching mechanism

Stretching mechanism to get "fill" effect like JWPlayer

@johndyer Done. This branch has now only the src files modified. Thanks and let me know when you merge it

Great! Lemme do some testing on this.

Great! I'm fixing right now the tabs you mentioned

@johndyer I completed the changes for tabs. Thanks for pointing it out

I downloaded your branch, opened up /test/test.html and set stretching: 'fill', and all the players (audio and video) collapsed and were not visible on screen. Using responsive or none or '' seems to work. Could you check on the fill mode?

@johndyer The 'fill' mode works if the video tag is actually enclosed within a div or other container with fixed dimensions. I added to your #video-container tag a dimension of width:700px and height:500px, and it worked. I'm gonna create a demo file for this. Let me know if it works for you

I'd like to have it "fail" in a better manner than completely hiding the video (and/or audio). It'd probably be better if there isn't a height specified on the container just to use the default sizing.

@johndyer OK let me work on that. I might have it ready tomorrow, so we can move forward with this

@johndyer Done. Please review it and let me know your thoughts on this. Thanks again

Is it good to be merged, @johndyer?

Thanks!


Front-end implement user table component for the delegated admin scenario

Describe the task
As a delegated admin, I want to see a table of users that I am managing.
Acceptance Criteria

[ ] On the front end, display a list of the users I am managing
[ ] Reuse the "user table" component

Additional context

this task should be done after 1184 is completed.

Closing as this is covered off under #1184


Data Pipeline Architecture Overview

We should groom over some of our scripts that

scraps data from known data sources
cleans said data
populates our DB with said data

and answer the following questions:

[ ] what are the capabilities of our current scripts?
[ ] what are some capabilities we'd like to see in our data scripts in the near future?
[ ] what is the frequency at which our scripts are running now?
[ ] what is the ideal frequency to run our scripts? (daily? weekly? monthly?)
[ ] what is the volume of data we're getting as input?

These are fairly essential questions for planning for the implementations of our pipeline in the future. @mbonsma , @cemyld ?

Here is the target data pipeline, referring to what we currently have:
Input: NCBI accession number (i.e. NC_000853).

If that accession isn't already in the database, download genome from NCBI (acc2gb.py).
Add to organism table (basically just the populate_organism function with minor modificaitons)
Run genome through CRISPRfinder using the standalone program.
Parse CRISPRfinder output into repeats, spacers, and locusspacerrepeats. (See http://phageparser.herokuapp.com/ for current tables.) We don't have a parser for this step yet, assuming their format is now different.

In any order:

Populate organismselfspacers using populate_selftargets.py

Run genome file through HMMER to detect cas proteins - @cemyld, is this step documented anywhere?
Add to casproteins and organismcas using populate_casgenes.py

Populate antiCRISPR tables (not yet created) using some version of anticrisprblast.py


Observatory's timeline tracing is not working properly

"Refresh" button is not working reliably. Usually, I have to refresh the web page multiple times to get the trace refreshed and loaded.
"Save" button does not work at all. It shows "Cannot save an empty timeline" even if there's a
non-empty timeline trace. See also b/141889413

How to reproduce: (1) flutter run in flutter_gallery; (2) open the observatory URL, go to timeline, check all boxes, and touch the phone to generate some trace events; (3) click "Refresh"; (4) click "Save"
This makes performance debugging very inconvenient as we can no longer save and share traces.

CC @flar @devoncarew @sivachandra

I think this is why all of the devicelab performance tests stopped working...

@kenzieschmoll @jacob314 - is the same workflow supported in DevTools?

This started with https://github.com/dart-lang/sdk/commit/68dede011e81de04ffc826f42732b8ce620bc52d
@bkonyi

This same workflow is supported in DevTools. In the current state we support a frame based timeline, but will support a timeline not broken down by frames in the future.

I'll take a look today. There was a pretty major refactor in the timeline code, so I wouldn't be surprised if something was missed / broken.


Bug: Electrum-Verge Ignores Proxy Settings For DNS

Issue Template
Prerequisites

[X ] Are you running the latest version?

2.4.1 win32
User Story:

"I'm submitting a ... "

[ X] bug report

Expected Behavior
DNS Resolution via proxy when proxy is set.
Current Behavior
Name resolution ignores proxy settings and directly connects to first google then system nameservers.
Possible Solution
Temporary: Block non-proxy requests with firewall,  Use raw IP address in electrum settings.
Steps to Reproduce (for bugs)

Steps :

Set Proxy Settings
Start Electrum-verge
Observe direct outbound UDP attempts to nameservers

sounds like you dont have administrator access/permission on your system. have you tried editing the proxy in the electrum .conf file instead of doing this through the GUI?

The proxy settings were/are set in the electrum-xvg gui.
The config file properly reflects the proxy settings.
"proxy": "socks5:<IP_ADDRESS>:9050",
The GUI has proper write access and is writing to the config file.  The user-level is not the issue.
When started, electrum-xvg sends UDP requests on port 53 directly from electrum-xvg to Google's <IP_ADDRESS> DNS.
Mainline Electrum 2.9 branch doesn't send any non-proxied requests like this.
I beleive the problem lies in gui/qt/version_getter.py
The requests module looks to be sending a GET to http://electrum-verge.xyz/version without using the proxies parameter.
https://github.com/vergecurrency/electrum-xvg/blob/master/gui/qt/version_getter.py
def run(self):
    try:
        res = requests.request("GET", "http://electrum-verge.xyz/version")
    except:
        print_error("Could not retrieve version information")
        return

should be
def run(self):
    proxies = {'http': 'http://<IP_ADDRESS>:9050', 'https': 'http://<IP_ADDRESS>:9050'}
    try:
        res = requests.request("GET", "http://electrum-verge.xyz/version", proxies=proxies)
    except:
        print_error("Could not retrieve version information")
        return

http://docs.python-requests.org/en/master/user/advanced/

SOCKS
New in version 2.10.0.
In addition to basic HTTP proxies, Requests also supports proxies using the SOCKS protocol. This is an optional feature that requires that additional third-party libraries be installed before use.
You can get the dependencies for this feature from pip:
$ pip install requests[socks]
Once you've installed those dependencies, using a SOCKS proxy is just as easy as using a HTTP one:
proxies = {
'http': 'socks5://user:pass@host:port',
'https': 'socks5://user:pass@host:port'
}
Using the scheme socks5 causes the DNS resolution to happen on the client, rather than on the proxy >server. This is in line with curl, which uses the scheme to decide whether to do the DNS resolution on the >client or proxy. If you want to resolve the domains on the proxy server, use socks5h as the scheme.

Assuming this GET is the source of the DNS request,
the fix is probably something like:
def run(self):
    try:
        proxystr = self.config.get('proxy').split(':')
        proxyproto = proxystr[0]
        proxyport = proxystr[-1]
        proxyip = proxystr[-2]
        _proxy = proxyip + ':' + proxyport
        if 'socks5' in proxyproto:
            proxies = {'http': 'socks5h://' + _proxy, 'https': 'socks5h://' + _proxy}
        elif 'http' in proxyproto:
            proxies = {'http': 'http://'+_proxy, 'https': 'http://'+_proxy}
        elif 'socks4' in proxyproto:
            #requests doesn't do socks4
            proxies = None
        res = requests.get("http://electrum-verge.xyz/version", proxies=proxies)
    except:
        print_error("Could not retrieve version information")
        return

well, we arent going to be supporting the clearnet electrum wallet/servers much longer, and i find it strange, that the electrum tor wallet doesnt have this issue. maybe its because it isn't getting a version..  (however community members may or may not run their own)

spring cleaning and closing issues -- please re-open if you feel it is important and maybe someone else can assist. As @justinvforvendetta  said, this specific wallet won't be available much longer.


Fix test_omnisci_array_null tests

As in title.
Just wondering why this test did not fail before.

https://github.com/omnisci/omniscidb-internal/pull/5465 fixed the omniscidb bug.
The reason for non-failure is that the tests were wrong.


[3.5] Mark Navigation/Navigation2D nodes as deprecated

Mark Navigation/Navigation2D nodes as deprecated. They already just redirect calls to the NavigationServer and have no longer a real purpose. In Godot 4.0 both nodes are already removed for good reasons outlined here #46786 or discussed here #691

Thanks!

In 3.5rc5 i tried using only NavmeshInstance and direct server calls, but it seems that's not possible as something in the NavmeshInstance node still expects there to be a Navigation node; atleast that's what i gathered by looking at the source (i'm not very versed in c++) when it didn't work for me, and i also tried replicating everything that seemed logical from the Navigation node source code.
Can you confirm that the deprecation actually means there's a way to make it work without the Navigation node in 3.5?

@Flavelius
The NavigationMeshInstance node uses the default navigation map of the Viewport world object from get_world()->get_navigation_map() if no Navigation node is found.
You can also make updates with the NavigationServer API directly should any of the navigation related nodes bug out for whatever reason. If you cannot make it work might want to open a dedicated issue for it.

There is no example in assets ? I'm very confused by this new change.


[BUG] Azure.Search throws when retreiving a SearchIndexer

Describe the bug
Retrieving a SearchIndexer using Azure.Search.Documents.Indexes.SearchIndexerClient.GetIndexerAsync throws an exception
Expected behavior
No exception should be thrown
You can see the problem is
"mappingFunction": {
"name": "base64Encode",
"parameters": null
}
which has "parameters": null
and:
https://github.com/Azure/azure-sdk-for-net/blob/Azure.Search.Documents_11.1.1/sdk/search/Azure.Search.Documents/src/Generated/Models/FieldMappingFunction.Serialization.cs
if (property.NameEquals("parameters"))
{
    Dictionary<string, object> dictionary = new Dictionary<string, object>();
    foreach (var property0 in property.Value.EnumerateObject())
    {

has this accessed without a check, which throws the exception below. (In the version on the master branch there is an additional check which will still throw an exception).
This file is tagged as autogenerated, but I'm not clear how so I haven't sent a PR (feel free to point me in the right direction).
Actual behavior (include Exception or Stack Trace)
System.InvalidOperationException
HResult=0x80131509
Message=The requested operation requires an element of type 'Object', but the target element has type 'Null'.
Source=System.Text.Json
StackTrace:
at System.Text.Json.JsonElement.EnumerateObject()
at Azure.Search.Documents.Indexes.Models.FieldMappingFunction.DeserializeFieldMappingFunction(JsonElement element)
at Azure.Search.Documents.Indexes.Models.FieldMapping.DeserializeFieldMapping(JsonElement element)
at Azure.Search.Documents.Indexes.Models.SearchIndexer.DeserializeSearchIndexer(JsonElement element)
at Azure.Search.Documents.IndexersRestClient.d__19.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()    at Azure.Search.Documents.Indexes.SearchIndexerClient.<GetIndexerAsync>d__48.MoveNext()    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
To Reproduce
I do not know exactly how to reproduce this -- the indexer was created using the old Microsoft.Azure* libraries. Since this is an actual object that exists in Azure I believe I should be able to retrieve it however it was created.
Here is the request and response as logged for the GetIndexerAsync call:
[Informational] Azure-Core: Request [a01498a3-1a94-47c0-a207-4aaa9d976cb6] GET https://xxx.search.windows.net/indexers('file-upload-indexer')?api-version=2020-06-30
Accept:application/json; odata.metadata=minimal
api-key:REDACTED
x-ms-client-request-id:a01498a3-1a94-47c0-a207-4aaa9d976cb6
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Search.Documents/11.1.1,(.NET 5.0.2; Microsoft Windows 10.0.19042)
client assembly: Azure.Search.Documents
[Informational] Azure-Core: Response [a01498a3-1a94-47c0-a207-4aaa9d976cb6] 200 OK (00.3s)
Cache-Control:no-cache
Pragma:no-cache
ETag:W/"0x8D85A6D49BB7052"
client-request-id:a01498a3-1a94-47c0-a207-4aaa9d976cb6
x-ms-client-request-id:a01498a3-1a94-47c0-a207-4aaa9d976cb6
request-id:a01498a3-1a94-47c0-a207-4aaa9d976cb6
elapsed-time:228
OData-Version:4.0
Preference-Applied:REDACTED
Strict-Transport-Security:REDACTED
Date:Thu, 21 Jan 2021 16:43:04 GMT
Content-Type:application/json; odata.metadata=minimal
Expires:-1
Content-Length:1204
[Verbose] Azure-Core: Response [a01498a3-1a94-47c0-a207-4aaa9d976cb6] content: {"@odata.context":"https://xxx.search.windows.net/$metadata#indexers/$entity","@odata.etag":""0x8D85A6D49BB7052"","name":"file-upload-indexer","description":null,"dataSourceName":"file-upload-datasource","skillsetName":null,"targetIndexName":"file-upload-index","disabled":false,"schedule":{"interval":"PT2H","startTime":"0001-01-01T00:00:00Z"},"parameters":{"batchSize":null,"maxFailedItems":-1,"maxFailedItemsPerBatch":null,"base64EncodeKeys":null,"configuration":{"failOnUnsupportedContentType":false,"failOnUnprocessableDocument":false,"indexStorageMetadataOnlyForOversizedDocuments":true}},"fieldMappings":[{"sourceFieldName":"metadata_storage_size","targetFieldName":"fileSize","mappingFunction":null},{"sourceFieldName":"metadata_storage_path","targetFieldName":"key","mappingFunction":{"name":"base64Encode","parameters":null}},{"sourceFieldName":"metadata_storage_content_type","targetFieldName":"contentType","mappingFunction":null},{"sourceFieldName":"metadata_storage_last_modified","targetFieldName":"lastModified","mappingFunction":null},{"sourceFieldName":"metadata_storage_name","targetFieldName":"name","mappingFunction":null}],"outputFieldMappings":[],"encryptionKey":null}
Environment:

Name and version of the Library package used: Azure.Search.Documents 11.1.1, Azure.Storage.Blobs 12.8.0
Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects):

The project is targeting .NET Core 5
PS C:\Users\mark> dotnet --info
.NET SDK (reflecting any global.json):
Version:   5.0.102
Commit:    71365b4d42
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.19042
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\5.0.102\
Host (useful for support):
Version: 5.0.2
Commit:  cb5f173b96
.NET SDKs installed:
3.1.100 [C:\Program Files\dotnet\sdk]
3.1.101 [C:\Program Files\dotnet\sdk]
3.1.400 [C:\Program Files\dotnet\sdk]
3.1.404 [C:\Program Files\dotnet\sdk]
5.0.101 [C:\Program Files\dotnet\sdk]
5.0.102 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.All 2.1.24 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.24 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.24 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

IDE and version : Visual Studio 16.8.4

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

This can be reproduced by creating an index using the current Azure.Search.Documents as follows:
            var indexer = new SearchIndexer(IndexerName, DataSourceName, IndexName)
            {
                Schedule = new IndexingSchedule(new TimeSpan(2, 0, 0)), // 2h
                FieldMappings =
                {
                    new FieldMapping("metadata_storage_size")
                    {
                        TargetFieldName = "fileSize"
                    },
                    new FieldMapping("metadata_storage_path")
                    {
                        TargetFieldName = "key",
                        MappingFunction = new FieldMappingFunction("base64Encode")
                    },
                    new FieldMapping("metadata_storage_content_type")
                    {
                        TargetFieldName = "contentType"
                    },
                    new FieldMapping("metadata_storage_last_modified")
                    {
                        TargetFieldName = "lastModified"
                    },
                    new FieldMapping("metadata_storage_name")
                    {
                        TargetFieldName = "name"
                    }
                },
                Parameters = new IndexingParameters()
                {
                    // Just ignore errors
                    MaxFailedItems = -1,
                    Configuration =
                    {
                        // don't fail if the content type is unsupported, just index the metadata
                        { "failOnUnsupportedContentType", false },
                        // carry on if the content type of the document can't be determined
                        { "failOnUnprocessableDocument", false },
                        // don't entirely skip gigantic documents
                        { "indexStorageMetadataOnlyForOversizedDocuments", true }
                    }
                }
            };
            await searchIndexerClient.CreateIndexerAsync(indexer, cancellationToken);

This will throw after creating the indexer with the same exception as outlined above (where the parameters collection for base64Encode is null).

@Mohit-Chakraborty could you take a look?

It seems like FieldMappingFunction[parameters] needs to be marked as "x-nullable":true in the REST spec.

@dereklegenzoff, can someone from the Search team comment on this please.

The parameters section is allowed to be null. See this doc for a few examples. @Mohit-Chakraborty - I'll send a mail to the relevant team to see if we can make that swagger update or not.

Workaround: pass in an empty array instead of null.

You can't work around retrieving an existing search indexer that way though -- this bug was actually encountered by trying to fetch a search indexer that had been created by the previous version of the Azure wrappers (v11, Microsoft.Azure.Storage) after upgrading to the current version.  The only solution I found there was to drop and recreate the search indexer (for me, not a big issue, but potentially expensive for a big index).

@Mohit-Chakraborty could you confirm that this has been addressed in the latest library?


refactor checkbox with label

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/7531
Tests

Run npm run storybook
Try submitting the form
Check if shows error

[x] Verify that no errors appear in the JS console

QA Steps

[x] Verify that no errors appear in the JS console

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web
https://user-images.githubusercontent.com/83179295/153957705-075c09b2-46c5-447a-857d-642fa7c83719.mov
without margin left-

with margin left-
https://user-images.githubusercontent.com/83179295/153959144-2271e08b-11a3-454b-a8bb-50814c3f33e7.mov
Mobile Web

Desktop

iOS

Android

Still having issues with desktop app. Will try again after sometime.

@thesahindia to test on desktop, merge main from upstream into your branch.
And temporarily create a .env file with USE_WEB_PROXY= true and USE_NRGOK=false

@rushatgabhane, tried both but still it's not showing anything.

@thesahindia i can't toggle the checkbox.

@rushatgabhane, hadn't implemented that because of getting error while testing due to the regression. It should work now.

hadn't implemented that because of getting error while testing due to the regression. It should work now.

Nope, it doesn't work. I'm unable to toggle checkbox in storybook.
Are you sure it's not due to the regression in TextInput https://github.com/Expensify/App/pull/7318#issuecomment-1040509733

Nope, it doesn't work. I'm unable to toggle checkbox in storybook. Are you sure it's not due to the regression in TextInput #7318 (comment)

Yeah I think it might be due to the regression as I had tested and it was working fine.

@thesahindia please merge main before you work on the changes requested. Thanks so much

@thesahindia please merge main before you work on the changes requested. Thanks so much

@rushatgabhane, sure and sorry for the delay. I was waiting to get clarification about adding translation but didn't see it was resolved (don't know why I didn't get a notification for it 🤷♂)

Commenting since I can't edit the PR
PR Reviewer Checklist

[x] I verified the PR has a small number of commits behind main
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the testing environment is mentioned in the test steps

[x] I verified testing steps cover success & fail scenarios (if applicable)
[x] I checked that screenshots or videos are included for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors related to changes in this PR
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified comments were added when the code was not self explanatory
[x] I verified any copy / text shown in the product was added in all src/languages/* files (if applicable)
[x] I verified proper naming convention for platform-specific files was followed (if applicable)
[x] I verified style guidelines were followed
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components are not impacted by changes in this PR (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified the UI performance was not affected (the performance is the same than main branch)
[ ] If a new component is created I verified that a similar component doesn't exist in the codebase

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

⚠ @thesahindia we have an issue. getInputIDPropTypes needs to be renamed to validateInputIDProps
Please create a follow-up PR.

🚀 Deployed to staging by @tgolen in version: 1.1.42-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

Edit: I've created a PR to fix this because it's 3 AM for you

Thanks for the help 😃

🚀 Deployed to production by @chiragsalian in version: 1.1.42-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Typing is slow and buggy

I believe this is related to the hack that prevents fixes the system beep. It might also be related to the javascript hacks.
Lately I've having issues typing. When I press some letters in the message box I get no reaction. Sometimes the "Type a message" placeholder remains ghosted over the field even when I have text there. Restarting the or choosing Reload fixes the problem… for a bit.
I don't have any screenshots right now, posting this as soon as possible so that other people who might have this issue can see this. I'll post screenshots when it happens again.

I've had slow text as well. Sometimes when I type it doesn't seem to register like normal or takes a few seconds to appear.

I am having similar experiences. Haven't been able to consistently reproduce or dig deeper yet.

Unfortunately I can't reproduce.
To debug this, set boolean default key main.js/disable to YES and relaunch the app. This disables any modifications to messenger.com — if typing is still slow the issue lies with messenger.com and/or webkit and/or the event logic in FBMApplication. Otherwise the issue is in main.js and we should start investigating there.

Btw, after I upgraded to Yosemite this issue is largely gone, I think it may be a Mavericks-specific bug.

I had this issue for the first time today after updating to 0.8. Hadn't seen it before today and I've been running the software for about a week.

I had this issue for the first time today after updating to 0.0.8.

Me too, and I'm using Yosemite, so I don't think it's Mavericks specific. I actually have Mavericks on another machine with Messenger 0.0.8, and I haven't seen it there, yet.

I tried
defaults write me.rsms.fbmessenger "main.js/disable" -bool YES

on my machine with Yosemite. I can't even type any message, I only get the beep sound on keypresses.

This newest issue is Facebook's fault, I can reproduce it on Safari.

I opened #137 and pretty much think this is the same issue.

The issue that was Facebook's fault has been resolved I think. messenger.com on Safari works fine now.

@rsms wasn't this confirmed to be Facebook's issue and is now fixed?

Closing this for now. Sounds like it was an issue with messenger.com
If someone can repro in latest release of Messenger.app, please comment and we'll reopen.


bind9: also block 'query failed (REFUSED)'

a small ride along

Can you also include the generated tests?


feat: Add an option --tf-version to terraform_docs, terraform_fmt, and terraform_validate

Enables the use of a version parameter which is in turn used by tfenv to dynamically switch the version of terraform being used at runtime.
This feature is intended for users who may have more than one version of Terraform in use. Running terraform fmt can produce wildly different results depending on the version of Terraform being used, and by allowing the version to be set in the hook configuration, pre-commit can switch to the proper version, run the hook, and then switch back to the previously configured version to restore the original system state.
Please let me know if you have any questions at all. I did modify terraform_fmt.sh pretty extensively to look like the other shell scripts since it now needs to accept a parameter.

Hi @svvitale !
Thanks for the proposal. I am not sure we need to parameterize each hook separately but instead...
I think we can have another hook named something like use_terraform_version which will configure the Terraform version based on:

tfenv from .terraform-version or via args.
tfswitch (https://tfswitch.warrensbox.com/ - I use this one myself and like it more). We don't need to support it right away but good to plan in advance.

Sample config:
hooks:
  - id: use_terraform_version
    args: ['--tfenv --version=min-required']
    # args: ['--tfswitch --version=latest']
    # args: ['--tfenv --version=0.12.18']
    # args: ['--tfswitch --version="^0.12"']
    # args: ['--tfswitch --version="^0.12"']

The final PR will be much smaller.
What do you think?

Hi @antonbabenko! Thanks so much for the quick reply, I'm glad to hear that you would get some value out of this feature as well.
tfswitch looks really slick, I may actually move our usage to that instead.
I didn't realize that hooks were executed in sequential order, although that makes sense now that you highlighted it.  I think this is a MUCH better approach that isolates it from current and future hook code. My only concern is that I'd like to ensure that the previously configured terraform version is restored after the hooks complete. I suppose that can be an additional (and optional) hook that users can place at the end of their hooks list.
This approach would also not be compatible with the fail_fast option, but that could be called out in the docs.
Let me know if you agree with the "restore" option and I'll get to work on the rest. Thanks again for taking the time to look through this.

Perfect!
There are some cases like the one you described (fail_fast) but even more often I run pre-commit run -a terraform_fmt which will have to be prefixed with use_terraform_version.
I agree it will be fine as long as we have use_terraform_version and restore_terraform_version at the end.

Relates #188

Close as too outdated. Simpler to create a new branch with specified changes than try to resolve conflicts

Is there any possibility to stick with terraform 1.5.7 for terraform_validate?
@MaxymVlasov @antonbabenko

Sure. Install terraform 1.5.7 locally and use it for validation proposes.

@MaxymVlasov does docker image use latest terraform version?
Im using GitLab CI/CD Pipeline and wondering if I should use a decent version or simply install required terraform version before triggering pre-commit run.
e.g:
precommit:
  image: ghcr.io/antonbabenko/pre-commit-terraform:latest
  script:
    - <----------- INSTALL TF here?
    - pre-commit run --all-files

You can build your own docker image with any tool version, including terraform
Check the Docker section at https://github.com/antonbabenko/pre-commit-terraform?tab=readme-ov-file#1-install-dependencies


Update example.env

Please provide enough information so that others can review your pull request:

Explain the details for making this change. What existing problem does the pull request solve?

.//


Adds a command-line argument to support choosing a specific merged PR

I'm on the side of  we shouldn't support arbitrary repos e.g. danger local --pr=artsy/eigen#11 as the file system isn't going to match the expectations of danger, a merged PR at least will have an approximation of the current file system ( though, obviously it may have changed since then, but that should be pretty obvious to the user. )
So this just adds a way to pass a single id along via danger local --use-merged-pr=11
Fixes https://github.com/danger/danger/issues/134

This needs documentation, but looks good!

Agreed, updated


fix #18

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

两个commit分开两个PR吧，毕竟是两个不同的事情，同时testcase跑不过，你看下

两个commit分开两个PR吧，毕竟是两个不同的事情，同时testcase跑不过，你看下

跑不过原因是项目使用了Unsafe而它被声明未来可能会删除
Warning:  /home/runner/work/fastjson2/fastjson2/core/src/main/java/com/alibaba/fastjson2/util/UnsafeUtils.java:[4,16] sun.misc.Unsafe is internal proprietary API and may be removed in a future release

理论上与提交的commit没联系

这个是warning，现在是能跑过的

com.alibaba.fastjson2.codec.JSONBTableTest2
这个testcase有问题，我已经修复，你重新提交吧


Add Telegram attribute to Model

Add new telegram attribute field for Person Model.
Updated AddCommand and EditCommand to work with the new telegram attribute field.
Updated test code to work with the new telegram attribute field.
Updated test json files to work with the new telegram attribute field.

Fixes #46 .

Codecov Report

Merging #49 (6ce36de) into master (3df62e4) will increase coverage by 0.50%.
The diff coverage is 78.57%.

@@             Coverage Diff              @@
##             master      #49      +/-   ##
============================================
+ Coverage     72.74%   73.24%   +0.50%
- Complexity      412      425      +13
============================================
  Files            71       72       +1
  Lines          1273     1312      +39
  Branches        132      139       +7
============================================
+ Hits            926      961      +35
- Misses          313      315       +2
- Partials         34       36       +2

Impacted Files
Coverage Δ

.../java/seedu/address/logic/commands/AddCommand.java
100.00% <ø> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
20.00% <0.00%> (ø)

src/main/java/seedu/address/ui/PersonCard.java
0.00% <0.00%> (ø)

...java/seedu/address/logic/commands/EditCommand.java
95.00% <77.77%> (-0.95%)
:arrow_down:

...main/java/seedu/address/model/person/Telegram.java
80.00% <80.00%> (ø)

...c/main/java/seedu/address/model/person/Person.java
98.07% <88.88%> (+0.20%)
:arrow_up:

...a/seedu/address/logic/parser/AddCommandParser.java
100.00% <100.00%> (ø)

...ain/java/seedu/address/logic/parser/CliSyntax.java
87.50% <100.00%> (+1.78%)
:arrow_up:

.../seedu/address/logic/parser/EditCommandParser.java
93.54% <100.00%> (+0.44%)
:arrow_up:

...in/java/seedu/address/logic/parser/ParserUtil.java
97.82% <100.00%> (+0.26%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

LGTM 👍 for the other attributes going forward are we going to use attribute-specific variable names (e.g. handle for Telegram) or just value for the value stored by the attribute?

I think we should use attribute-specific variable names as it is more descriptive. I will update the github attribute name after this branch is merged.


As a client I do not want to automatically export shipments when 'Afhalen in winkel' is selected

Is your feature request related to a problem?
When 'Afhalen in winkel' is selected by the customer, it will automatically export after payment. It should not export as it is not necessary to create a label.
Describe alternatives you've considered
For now the shipping method 'Afhalen in winkel' is linked to a label without barcode (letter) so I don't create barcodes I do not use.

In version 4.13.1 we added a function that the orders that are using "local_pickup" will be excluded for the MyParcel export.
I will close the issue as it was fixed in an earlier version of the plugin


How to get shape information of a node?

Hi,
I am debugging an attention s2s model and I would like to know the shape of a node. For example:
alphas = mx.sym.SliceChannel(data=alpha, num_outputs=self.seq_len, axis=1, name='_sliced_alpha')
sums = []
for idx in range(self.seq_len):
    h = attended[idx]
    weight = alphas[idx]
    weighted_h = mx.sym.broadcast_mul(h, weight, name='_weighted_h_{0}'.format(idx))
    sums.append(weighted_h)
weighted_sum = mx.sym.Concat(*sums, dim=1, name='_weighted_sum_1')
weighted_sum = mx.sym.sum(data=weighted_sum, axis=1, name='_weighted_sum_2')
return alpha, weighted_sum

How can I get the shape of nodes such as weighted_sum and weighted_h ?
Thank you.

sym.infer_shape


React support

I've struggled trying to make react work with rollup.
If you find it useful, here is how I solved it.
It would be useful for others if you put a tip at the end of your post. Or you could push it in a branch here for reference.

Thanks for putting this up — I'll add a note to the post. Out of curiosity, did you try Babel's React preset? That could avoid the JSX stuff, which would make the setup even simpler.

@wesleycoder how would you feel about sending this in as a pull request? I'll put it on another branch and link to it from the README as a variation on the initial repo. I have #5 open right now to add an Express server, so we'd have two setup variations to start.

Sure, I'll send the PR soon.

May I send the PR to the master branch or will you create another branch in which I'll send the PR?
It is ready to send.

@wesleycoder I just created a branch called alt-config/react. Can you send the PR against that one?
Thanks!


[security] Allow to config web server's cipher and protocols.

cherry pick from #13354

Hi @Lico-Tom,
Could you have time to check the CI?

Closed as stale.


Final local io_remove call in dask_io_remove

For whatever reason, we have seen some cases on NFS; where, after having removed the whole file/directory in parallel, we still seem to be unable to recreate the same file/directory locally and write to it. This last call to io_remove on the node hosting the Jupyter Notebook server exists to make sure that the file/directory is really removed before we might try to recreate it. This way even if NFS was slow to remove the file/directory on the Jupyter Notebook server node for some reason, we make sure this is done. Hopefully this also informs NFS of this fact in the process. Thus it should be a non-issue to create the file/directory on our node.

Have not seen much need for this. Removal seems to already be dealt with well using the current strategy. So closing this out. Can always reopen if a need arises.


EXT-1403-nicer-error-message-to-replace-the-one-from-the-failing-fieldtype-wrapper-js

What?
Nicer error message from failing fieldtype-wrapper.js.
Replaces the uncaught error from https://github.com/storyblok/field-plugin/issues/107

with

Why?
When a client upload code to the field plugin editor, Storyblok will serve a document with a script that contains that code. But the content of the script element will not be exactly the code that the client uploaded; it will be appended with a code snippet from Storyblok. For example, the if the client uploads
console.log('hello')

Storyblok will serve a document with
<script type="text/javascript">
  console.log('hello')

  var customComp = window.Storyblok.vue.extend(window.storyblok.field_types['sb-dummy'])
  window.Storyblok.vue.component('custom-plugin', customComp)
  window.StoryblokPluginRegistered = true
</script>

This last part causes an error to be thrown. The only way to prevent these last three lines from being executed is by throwing an error before it's executed.
For Storyblok internals, see the feature requests:

Quick fix: https://storyblok.slack.com/archives/C03QMNGV3U1/p1682414222741019
Permanent fix: https://storyblok.slack.com/archives/C03QMNGV3U1/p1680270175282369

How to test? (optional)
Build one of the templates and upload the export bundle to the field plugin editor. You should see the new error message instead, and the app should load normally.

Once this is merged, we should reply in https://github.com/storyblok/field-plugin/issues/107


Clickhouse migrations tools

Original issue https://github.com/openedx-unsupported/tutor-contrib-clickhouse/issues/22

@regisb @bmtcril
Some issue I've found with alembic:

Alembic doesn't support clickhouse officially.
The package that does support clickhouse (clickhouse-sqlalchemy) doesn't support it well. Example, clickhouse tables needs an engine, but this one is not automatically added when migrations are generated. this was automatically generated: https://github.com/openedx/tutor-contrib-aspects/pull/99/files#diff-5757d3accb389de96650dfa78df377b6fba0cbb699a27058cc68a9b43d6e50bdR35-R38
It doesn't support multiple databases. Alembic does but clickhouse-sqlalchemy doesn't https://github.com/openedx/tutor-contrib-aspects/pull/99/files#diff-ba9a8e25b7d1284464cb663540f4bca7ffc9922058a1e57ee3ec3ec870c3cb2cR22
If we need a to write most of the migration tool manually, why don't just use raw sql statements?

Based on my experience with Alembic I think this would be the right approach.

Solved by https://github.com/openedx/tutor-contrib-aspects/pull/99


How to add passwordless-sms-auth?

We would like to extend the solution to uses SMS as alternative way for a passwordless email auth using cognito. The goal is that the user can choose either email or sms for getting the secret code. How can we tell the lambda that the request from cognito was made by email or sms?

Interesting question! No really easy way to do this I'm afraid, as you can't pass instructions along in the signIn call that could be accessed by the createAuthChallenge trigger. Thoughts that come to mind to someway get there:

save the choice (email or SMS) in a DynamoDB table and read it from the createAuthChallenge trigger to know what to do.
provide the choice (email or SMS) as validation meta data in the signIn call. Then use a PreAuthentication Lambda trigger (that has access to the meta data) to write the choice to the user's attributes in Cognito and read from there in the createAuthChallenge trigger to know what to do.

Interested to hear what route you guys end up taking.

Was this resolved? Can the issue be closed?

Hi @ottokruse. We're also looking to add that exact use case. We want to give the choice to our users to get code by sms or email.

We've played with cognito sign-in aliases, but it seems that it's one or the other
We've played with PreAuthTrigger. We wanted to update a custom attribute based on ClientMetadata passed in from Auth.signIn, but as you've said it's not called for custom auth. Btw, is that a known bug at AWS ?

We're not sure yet how we'll solve this. Updating a DynamoDB table seems overkill for something like that. It seems very unnatural to have no way to transmit some meta data from the client to our custom auth flow triggers. Any more insights since your last message ? @marcschroeter Have you solved it ?
It seems many people want to do similar use cases.(https://github.com/aws-amplify/amplify-js/issues/5318)

Is it always either email or sms? Then you could make a user attribute out if it in Cognito, that you store while registering the user. User attributes are available in the custom auth lambda's.
What company do you work for? I can add you to the internal feature request to Cognito team, that does help. Send me a DM on Twitter if you want: @ottokruse

@ottokruse Any update on this?
We have a very similar problem. We would like to send the auth code via SMS at first. But some users are unable to receive SMS, so we want to offer them a fallback via Email instead.

Here is a solution that allows the user to choose SMS or email. It does not use DynamoDB but rather a more sophisticated custom auth flow:
https://github.com/ottokruse/amazon-cognito-passwordless-email-auth/tree/email-or-sms
It's rough but it works. We'll make it more proper and include docs at some point, but for now you can check out the code to see a way to do it. You can deploy it in the exact same manner as the repo here.
The trick the solution uses is to add an additional challenge in the custom auth flow, "CHOOSE_EMAIL_OR_SMS", that will allow to client to respond with clientMetadata with the choice "email" or "sms". Interestingly, if you include clientMetadatain the RespondToAuthChallenge call this clientMetadata is visible in the custom auth lambda's, and therefore you can get it all to work.
Note, the Cognito custom auth docs do mention:

clientMetadata
One or more key-value pairs that you can provide as custom input to the Lambda function that you specify for the define auth challenge trigger. You can pass this data to your Lambda function by using the ClientMetadata parameter in the AdminRespondToAuthChallenge and RespondToAuthChallenge API operations.

Thanks for the update! For us it comes a bit too late, as we have already implemented a different solution, similar to your earlier "DynamoDB" suggestion, but using the Cognito user pool itself to store the user's choice. It works, but I like this new solution using the additional "CHOOSE_EMAIL_OR_SMS" challenge better. Will keep it in mind for the next time something like this comes up.


node backend does not support taproot

Background
with v0.15.1-beta update
Your environment

lnd v0.15.1-beta
btcd 0.22.0-beta
debian 11.2

Steps to reproduce
just start lnd
Expected behaviour
lnd up
Actual behaviour
lnd                   | 2022-08-30 22:35:21.841 [ERR] LTND: unable to create partial chain control: node backend does not support taproot
lnd                   | 2022-08-30 22:35:21.841 [ERR] LTND: Shutting down because error in main method: error creating wallet config: unable to create partial chain control: node backend does not support taproot
lnd                   | 2022-08-30 22:35:21.864 [INF] LTND: Shutdown complete
lnd                   |
lnd                   | error creating wallet config: unable to create partial chain control: node backend does not support taproot
on your doc :
https://github.com/lightningnetwork/lnd/pull/6798. https://github.com/lightningnetwork/lnd/pull/6826, the officially supported versions of bitcoind are: 21, 22, and 23.
nothing about btcd ?

You want this version for btcd: https://github.com/btcsuite/btcd/releases/tag/v0.23.1
Which docs are you referring to?

For what I see there have been more version tagged in btcd but there is no official releases of them? 0.22.0-beta is from last year so for sure does not have the taproot changes included. Latest one is v0.23.1 which is taproot compatible. I do not remember when it was included v0.22.1 or v0.23.0 @Roasbeef

the release was updated 1 mn ago :-) I 'm testing

btcd@btcd:/opt/btcd$ ./bin/btcd --version
btcd version 0.23.1-beta
but same error, I don't see any option about taproot, am I blind ?

You want this version for btcd: https://github.com/btcsuite/btcd/releases/tag/v0.23.1
Which docs are you referring to?

https://github.com/lightningnetwork/lnd/blob/v0.15.1-beta.rc1/docs/release-notes/release-notes-0.15.1.md

reminder for me, never update a server before sleeping 🤣

What is the output for client.GetBlockChainInfo() when you hit your btcd (v0.23.1) server? Doesn't it include taproot under resp.SoftForks.Bip9SoftForks ?

weird with getblockchaininfo method -> {"jsonrpc":"1.0","result":null,"error":{"code":-32603,"message":"limited user not authorized for this method"},"id":"1"}
I don't find anything on https://github.com/btcsuite/btcd/blob/master/docs/json_rpc_api.md#JSONAuth
but curl works because getinfo :
{
  "jsonrpc": "1.0",
  "result": {
    "version": 230100,
    "protocolversion": 70002,
    "blocks": 751931,
    "timeoffset": -1,
    "connections": 8,
    "proxy": "",
    "difficulty":<PHONE_NUMBER>3493.773,
    "testnet": false,
    "relayfee": 1e-05,
    "errors": ""
  },
  "error": null,
  "id": "1"
}

found!!! I used rpclimited creds....with rpcuser  creds it's up ! is it ok about my solution ?

It looks ok, taproot key is there so lnd v0.15.1-beta should not complain about it :eyes:
Does it still complain after restarting it pointing to the btcd version 0.23.1-beta?

only ok with not rpclimiteduser but rpcuser, you saved my sleep and my server, thank you for the support


Dropdown Menu with objects for value

Description
DropDown Menu Cannot handle equality between objects, because it's using === for equality checking.
https://github.com/callemall/material-ui/blame/master/src/DropDownMenu/DropDownMenu.js#L396
This is the line that is checking the equality between the selected value of the dropdown and its children.
If you agree with me that this is a good feature to have, I can make the changes and create a PR.

True, that's on purpose, we have already been rejection PR trying to change that behavior for performance reason. Users should be able to provide consistent object reference. Thanks for the suggestion 👍 .


add test for new abort_unwind function

Seems like a good thing to have an explicit test for.
Cc https://github.com/rust-lang/rust/issues/130338

@bors r+

:pushpin: Commit 1b5ec29ae6ec3e3a9b89a683aec4fa5f87f78596 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 1b5ec29ae6ec3e3a9b89a683aec4fa5f87f78596 with merge 1144096c8b5f162e6f342df6689a8330c8c88c49...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 1144096c8b5f162e6f342df6689a8330c8c88c49 to master...


web-pdb just hangs on FireTV

I don't know if this is expected, but I have searched all the docs and can't find any mention of it and I can't find anywhere else to ask. web-pdb works perfectly for me on a Windows 10 laptop, but any calls to web_pdb.set_trace() when my app is running on FireTV (Android fork) just results in a hang with no web-pdb popup and no access via the 5555 port.
Is web-pdb supposed to be compatible with Android/FireTV?

No idea. Android systems have their quirks regarding permissions and such.

Closing since nothing can be done here.


Update logos in hypothesis plugin page

The page is displaying old ore no logos at all. See https://wordpress.org/plugins/hypothesis
We should update this to use up-to-date branding.
Same goes for the generic WordPress account we created: https://profiles.wordpress.org/hypodev/

Updated logos for both the plugin and the WordPress account.


Issues installing / launching with latest raspbian bullseye

I have tried a few times now to install older version of python (3.7/3.8) but it would appear that something fails during mariner install and then again when launching that causes the Python errors "Could not find platform independent libraries" and all proceeding errors associated with such.  Will this software run on Python 3.9? Is there a quick workaround to point it to the proper installation?
EDITED to add : There is a clear fix here in the Issue reports, it's just buried under "can't connect"
https://github.com/luizribeiro/mariner/issues/481#issuecomment-968325624

Fixed here #493

Recompiling python is not a fix.

Recompiling python is not a fix.

currently the code only works with 3.7, when it is totally updated to 3.9 the problem can be solved. Raspbian bullseye uses version 3.9 as a base


General interest question

Hi there, I'm scouting for a protocol to use for efficient transfer of statsd type events sometime next year, do you think tarpc would be a good fit? I'm still in the conceptual stages, but a high-level view would be:

connection/session  per topic (host.cpu.load)
batched/compressed series of counters as efficiently packed as possible

Theoretically with tokio/mio under the hood I might be able to get something like that spun up? I'm really interested in efficient transmission.

That certainly sounds like something you could incorporate tarpc into. Generally speaking, tarpc should be suitable for any kind of request-response style networking. There is still a lot of churn in tokio right now, which is why there hasn't been a tokio-based tarpc release yet. I expect there will be one in the coming weeks.

Closing due to inactivity. Feel free to reopen if you have more questions!


Refactor how we store user-selected data

This PR contains work that

extracts the user-selected Category, Goal, Behavior, and Action objects from the CompassApplication into a container UserData class--a single instance of which is stored in the CompassApplication instead.
UserData should do a better job of keeping the hierarchy of content up-to-date when something is added or removed.
Adds a GetUserDataTask which pulls all of the user-selected data from the /api/users/ endpoint in one request
Simplifies the MainActivity by removing a bunch of unnecessary callbacks, and...
Simplifies the CategoryFragment and MyGoalsFragment classes by removing unnecessary listeners.

It looks good :+1:


Nested Web.config files are not treated as Content for publishing and transforming

As I switch our old WebForms projects to leverage publishing, I noticed that only the root web.config files are properly considered for deployment, transformed and copied on publish, while web.config files inside of other folders in the project (used usually for setting Location-based permissions) are completely ignored.
I believe it should be possible to treat these nested web.config files the same way as the root one so that they properly participate in the publishing pipeline.
I've not yet worked around this issue, so suggestions on how to do so besides manually marking each individual file as Content in Visual Studio are welcome.

You probably want something like
<ItemGroup>
    <Content Include="**\Web.config" Exclude="Web.config" />
</ItemGroup>

This is one of the advantages of the SDK style project.
I would always use a location tag in the root web.config, instead of one in each folder, as otherwise you may end up with odd behavior as not all information is inherited. There is some special stuff in place for razor views where you need a customized web.config in the Views folder already in the Razor SDK.
<location path="some/plugin/location/handler.ashx">
  <system.web>
    <httpRuntime maxRequestLength="1048576" executionTimeout="600" />
  </system.web>
  <system.webServer>
    <security>
      <requestFiltering>
        <!-- 500MB in bytes, default is 30000000 or approx. 28.6102 Mb-->
        <requestLimits maxAllowedContentLength="1073741824" />
      </requestFiltering>
    </security>
  </system.webServer>
</location>
<location path="some/plugin2/location/otherhandler.ashx">
  <system.web>
    <pages validateRequest="false" />
    <httpRuntime requestValidationMode="2.0" executionTimeout="600" />
  </system.web>
</location>

You probably want something like
<ItemGroup>
    <Content Include="**\Web.config" Exclude="Web.config" />
</ItemGroup>

This appears to have done the trick, thanks!
Do you know what would be needed to also support transformations on these non-root web.config files? I assume just the above is not enough?

I would always use a location tag in the root web.config, instead of one in each folder, as otherwise you may end up with odd behavior as not all information is inherited.

Thanks for the advice, but this would not scale well for this particular project. This is a legacy WebForms project with over a thousand pages in a multitude of folders, and we have permission management everywhere. If we concentrated all of them in the main file (or even if it was isolated in a dedicated file linked via configSource, it would be completely unmaintainable, especially as this project has multiple feature teams handling it at the same time each with their own pages and folders.
Having native support for these nested web.config files would be really nice for this use case.

Do you know what would be needed to also support transformations on these non-root web.config files? I assume just the above is not enough?

Are you talking about including publish profile transforms for msdeploy, or configuration transforms like debug / release etc?
The section of the SDK that deals with this is https://github.com/CZEMacLeod/MSBuild.SDK.SystemWeb/blob/add70be345fd8a988c3a659bd9b482a6988087fd/src/MSBuild.SDK.SystemWeb/Sdk/MSBuild.SDK.SystemWeb.DefaultItems.props#L9-L24
You might be able to something along the lines of
  <ItemGroup Condition="'$(EnableWebFormsDefaultItems)'=='true'">
    <Content Include="**\Web.config" />
    <None Include="@(_WebConfigConfigurations->'**\Web.%(Identity).config')">
      <DependentUpon>%(RelativeDir)\Web.config</DependentUpon>
    </None>
    <Content Include="**\Web.*.config" Exclude="@(None)" />
  </ItemGroup>

Thanks for the advice, but this would not scale well for this particular project. This is a legacy WebForms project with over a thousand pages in a multitude of folders, and we have permission management everywhere. If we concentrated all of them in the main file (or even if it was isolated in a dedicated file linked via configSource, it would be completely unmaintainable, especially as this project has multiple feature teams handling it at the same time each with their own pages and folders.

Fair enough. As I said - it should work - but I've had issues with this approach in non-sdk projects, let alone with the hacks the SDK does. If you get it to work for you, all the better.

Having native support for these nested web.config files would be really nice for this use case.
You might need to tweak the DependentUpon line above, but refer to https://learn.microsoft.com/en-us/visualstudio/msbuild/msbuild-well-known-item-metadata?view=vs-2022 if what I gave doesn't work.

You might need to adjust the line to be something like
<None Include="@(_WebConfigConfigurations->'**\Web.%(Identity).config')" Condition="EXISTS('@(_WebConfigConfigurations->'**\Web.%(Identity).config')'"> to work around #67 or you could implement something like the fix in #68

Do you know what would be needed to also support transformations on these non-root web.config files? I assume just the above is not enough?

Are you talking about including publish profile transforms for msdeploy, or configuration transforms like debug / release etc? The section of the SDK that deals with this is
https://github.com/CZEMacLeod/MSBuild.SDK.SystemWeb/blob/add70be345fd8a988c3a659bd9b482a6988087fd/src/MSBuild.SDK.SystemWeb/Sdk/MSBuild.SDK.SystemWeb.DefaultItems.props#L9-L24
You might be able to something along the lines of
  <ItemGroup Condition="'$(EnableWebFormsDefaultItems)'=='true'">
    <Content Include="**\Web.config" />
    <None Include="@(_WebConfigConfigurations->'**\Web.%(Identity).config')">
      <DependentUpon>%(RelativeDir)\Web.config</DependentUpon>
    </None>
    <Content Include="**\Web.*.config" Exclude="@(None)" />
  </ItemGroup>

I was referring to the normal transforms, using Web.Debug.config/Web.Release.config etc. We are currently not doing any XML transforms on non-root web.config files, but I know they are supposed to work on the legacy project format. If someone could implement that in this SDK it would be more complete/closer to the full capabilities of the legacy project.
Perhaps your suggestions above could help someone implementing it directly in the SDK.
Your initial suggestion unblocked me to get our publish pipeline going, but I added it to our project with a note in hopes that this is implemented as part of the SDK in the future and we can then remove the customization:
  <ItemGroup>
    <!--
      HACK:

      Adds all nested `web.config` files manually. Ideally, this should be handled by the SDK, but it only
      considers the root `web.config` file at the moment.

      More information here:
      - https://github.com/CZEMacLeod/MSBuild.SDK.SystemWeb/issues/83
    -->
    <Content Include="**\Web.config" Exclude="Web.config" />
  </ItemGroup>

Thankfully we've only had to add this to a single project thus far out of the 8 projects we have currently using this SDK.


PR for https://github.com/danieleteti/loggerpro/issues/92

PR for refactoring for Issue #92
Re factored file rotation:

moved functionality into own helper object with base interface to define behaviour
provide two concrete implementations:

Rotate by file count
Rotate by file date

Tidied up the LogFileFormat checks to use an enumeration
Moved file maintenance methods (Delete / Rename) to the  helper objects

Added code to address the issue mentioned in https://github.com/danieleteti/loggerpro/issues/47


[Relay] Sendto failed with code -1 for char 5 and length 1464.

Hello. When connecting to the server via a relay, notification data is sent to the log. What does this mean?

Please provide your code and steps to reproduce including the full console output

https://pastebin.com/nvgcQTsb

First I run the script on the command line
After that, I connect to my server via a relay
During the connection, the following warnings are sent to the terminal

Looks like there is no connection to the server. Try a different server.
We should however not attempt to send packets where there is no connection, so this should be fixed.

But still, I connect to the destination server and the packets are sent.

Try a different server.

There is no such problem when connecting to other servers (except to the server The Hive because I can't connect to it at all).

Try a different server.

There is no such problem when connecting to other servers (except to the server The Hive because I can't connect to it at all).

i am pretty sure because they not allowing client to be joined with an proxy

Please provide your code and steps to reproduce including the full console output

I get that error too but it still lets me join and nothing breaks just logs that

https://pastebin.com/nvgcQTsb

First I run the script on the command line
After that, I connect to my server via a relay
During the connection, the following warnings are sent to the terminal

I experience this aswell when using the same code (Connecting to any realm or IP/Server), although it only occurs when I use a VPN if this is any help.

https://pastebin.com/nvgcQTsb

First I run the script on the command line
After that, I connect to my server via a relay
During the connection, the following warnings are sent to the terminal

I experience this aswell when using the same code (Connecting to any realm or IP/Server), although it only occurs when I use a VPN if this is any help.

yea i noticed that aswell

Please provide all the code if you can reproduce the issue locally. The only issue here is not logging a connection close event. It's possible you did not listen for the correct close event or did not set conLog to console.log for debug connection logging.

Using the code below for client
const client = bedrock.createClient({
  host: 'localhost',   // optional
  port: 19131,         // optional, default 19132
  username: 'Notch',   // the username you want to join as, optional if online mode
  offline: true      // optional, default false. if true, do not login with Xbox Live. You will not be asked to sign-in if set to true.
})

let sendTime = null
let receiveTime = null
let allTimes = []
let times = 0

function sendHello () {
  client.write('text', {
    type: 'chat', needs_translation: false, source_name: client.username, xuid: '', platform_chat_id: '',
    message: `Hello world !`
  })
}

client.on('spawn', () => {
  console.log('I spawned! Sending hello world...')
  sendHello()
  sendTime = Date.now()
})

client.on('text', (packet) => { // Listen for chat messages and echo them back.
  receiveTime = Date.now()
  console.log(`Latency: ${receiveTime - sendTime}ms`)
  allTimes.push(receiveTime - sendTime)
  times++
  if (times < 10) {
    sendTime = Date.now()
    sendHello()
  } else if (times === 10) {
    console.log('Average is:', allTimes.reduce((a, b) => a + b, 0) / allTimes.length)
  }
})

and for Relay
const {Relay} = require('bedrock-protocol')
const relay = new Relay({
  /* host and port for clients to listen to */
  host: '<IP_ADDRESS>',
  port: 19131,
  // logging: true,
  offline: true,
  version: '1.20.0',
  /* Where to send upstream packets to */
  destination: {
    host: '<IP_ADDRESS>',
    port: 19130,
    offline: true
  }
})
relay.conLog = console.debug
relay.listen()

This is what I get directly connected to vanilla server:
I spawned! Sending hello world...
Latency: 58ms
Latency: 61ms
Latency: 62ms
Latency: 61ms
Latency: 63ms
Latency: 62ms
Latency: 61ms
Latency: 61ms
Latency: 62ms
Latency: 63ms
Average is: 61.4

Connected via proxy, with minimal batching:
I spawned! Sending hello world...
Latency: 134ms
Latency: 184ms
Latency: 191ms
Latency: 186ms
Latency: 186ms
Latency: 157ms
Latency: 169ms
Latency: 153ms
Latency: 126ms
Latency: 124ms
Average is: 161

So we can see that the overhead is about ~2.62x, which seems OK, but definitely not great. With default batching delay it's a bit higher, but that can be fixed. I don't see anything else obvious to optimize here. Since the Relay is really designed for debugging purposes and not maximum optimization, you can look into writing your own Relay on top of the Client and Server classes and optimizing as is necessary.

Seems like similar issue to #426 - server is closing the connection, subsequent messages fail to send. Please reopen if you have more information to add.

@extremeheat got the same error, when using createClient(deviceCode login).
My code:
	const client = await createClient({
		authflow: new Authflow(gamertag, authflow_cache_manager, authflow_options),
		username: gamertag,
		viewDistance: 1,
		connectTimeout: 10_000,
		skipPing: true,
		host: "geo.hivebedrock.network",
		port: 19132,
		offline: false
	});
	console.log("Connecting to The Hive..");

	client.on("error", logger.error);
	client.on("spawn", () => {
		logger.success("Joined Hive");
		setTimeout(() => {
			client.disconnect();
			logger.success("Left Hive");
		}, 1000 *mt_rand(5, 15));
	});
	client.on("disconnect", console.log)

Console:
Connecting to The Hive..
sendto failed with code -1 for char 5 and length 1464.
sendto failed with code -1 for char 5 and length 1464.
sendto failed with code -1 for char 5 and length 1464.

Process finished with exit code 0


Prevent printing to stdout in test_extending.py

Codecov Report

Merging #2856 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #2856      +/-   ##
=========================================
- Coverage   86.11%   86.1%   -0.01%
=========================================
  Files         324     324
  Lines       67588   67587       -1
  Branches     7592    7592
=========================================
- Hits        58201   58197       -4
- Misses       8173    8175       +2
- Partials     1214    1215       +1

Thanks for the fix. Merging.


Experiment of Minitest

I give up to adopt Minitest because Travis error in Scala 2.11 test can't be resolved.


The extension host terminated unexpectedly 3 times in the last 5 minutes.

This error is currently display when I open my HTML project on VSCode. I recently added some extensions like "Live Sass Compiler" and the error appear after that. Please how to fix ?

Merci d’avoir créé ce numéro!
Cependant, comme la description n’est pas en anglais, il nous est difficile de travailler dessus. Si vous le pouvez, veuillez modifier ce numéro pour qu’il soit en anglais. Veuillez ne pas ajouter un nouveau commentaire ou créer un nouveau numéro, mais plutôt modifier le problème existant.
Malheureusement, les services de traduction automatique ne sont pas en mesure de gérer le langage technique nécessaire pour communiquer efficacement sur les problèmes logiciels, nous vous recommandons donc de trouver un traducteur humain qui connaît notre technologie pour aider à traduire.
Sinon, ce problème a été marqué comme nécessitant une traduction et un membre de la communauté peut être en mesure d’aider à le traduire.

Thanks for creating this issue!
Unfortunately, as the description is not in English, it's hard for us to work on. If possible, please edit the original issue to be in English.
In our experience, automatic translation services are not able to handle the technical language needed to effectively communicate about software issues, so we recommend finding a human translator who is familiar with our technology to help.
Otherwise, we have marked this as needing translation and a community member may be able to help out.

All extensions execute together on a single nodejs process, so in order to narrow down the possible problematic extension, please try the following:

run F1 > Help: Start Extension Bisect
(this will restart VS Code with half of your extensions disabled)
try to do the steps which reproduce the problem
if the problem reproduces, click "This is bad" (this narrows down the problematic extension to the half which was enabled)
if the problem does not reproduce, click "Good now" (this narrows down the problematic extension to the half which was disabled)
these steps will repeat until the problematic extension is found

initial
step
final

I ran into this error too, and completed the bisect. For me, it appears to be an issue with the CircleCI extension (1.9.0):
Extension Bisect is done and has identified circleci.circleci as the extension causing the problem.
As far as I can tell, it's been happening since I updated to VSCode 1.76.2. If it makes any difference, I'm on macOS 12.6.3 Intel.

Can you please follow the steps in https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues to get at more details around the crash and attach the result here? Thanks!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


nuqs is not compatible with nextjs 15  and some other packages are not compatible with react19 ( rc )  version

im using pnpm
after installing packages with pnpm install so many unmet peer dependencies   issues thrown

resolved with adding
"pnpm": {     "overrides": {       "@types/react": <EMAIL_ADDRESS>      "@types/react-dom": <EMAIL_ADDRESS>      "react": "$react",       "react-dom": "$react-dom"     }   }
to package.json


GET /resources Route should take query params for language and category

The original vision of routes was flawed. We originally wanted to have routes called GET /categories/{category} and GET /languages/{language} to get all of the resources for a category and language. After some discussion, @wimo7083 and I decided that it makes much more sense to have the single route for GET /resources take optional query parameters specifying the category and language. So a valid request to this endpoint can take page, page_size (these two are addressed in #21) as well as language and category. So the request might look something like this:
GET /resources?category=books&language=ruby&page=2&page_size=5
This issue will be considered fixed when the query params for language and category are accepted by the endpoint and return the filtered results.

agreed. I will update #28 to do this instead.

This was fixed in #42


Improve the pageSize entry in the document properties dialog, by also displaying page names and orientation

These patches, which were quickly thrown together, attempts to implement the remaining requests from issue #6990. Please refer to the individual commit messages for additional details.

/botio-linux preview

/botio unittest

Really nice improvement. Thanks!