NeonDbError: db error: ERROR: prepared statement "s675205" does not exist

Steps to reproduce
Execute any insert query.
Expected result
Queries execute correctly
Actual result
NeonDbError: db error: ERROR: prepared statement "s675205" does not exist
Environment
Neon cloud with autoscaling 1-7
Logs, links

After some investigation, it looks like pgbouncer is the problem. I switched from the pooled connection to the direct connection and this are working again

Started seeing this in production since 4am PST today.

START RequestId: 31e8caa3-a553-4b28-b972-526e760fb89b Version: $LATEST
2023-10-30T17:38:34.934Z	31e8caa3-a553-4b28-b972-526e760fb89b	ERROR	NeonDbError: db error: ERROR: prepared statement "s1803523" does not exist
Caused by:
ERROR: prepared statement "s1803523" does not exist
at /var/task/node_modules/@neondatabase/serverless/index.js:1530:11
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async FilingService.listFilings (/var/task/.next/server/chunks/394.js:34:26)
at async Promise.all (index 0)
at async search (/var/task/.next/server/pages/api/search.js:213:34)
at async handler (/var/task/.next/server/pages/api/search.js:264:25)
at async /var/task/node_modules/@sentry/nextjs/cjs/common/wrapApiHandlerWithSentry.js:153:35 {
code: '26000',
sourceError: undefined
}
2023-10-30T17:38:34.934Z	31e8caa3-a553-4b28-b972-526e760fb89b	ERROR	NeonDbError: db error: ERROR: prepared statement "s1803523" does not exist
Caused by:
ERROR: prepared statement "s1803523" does not exist
at /var/task/node_modules/@neondatabase/serverless/index.js:1530:11
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async FilingService.listFilings (/var/task/.next/server/chunks/394.js:34:26)
at async Promise.all (index 0)
at async search (/var/task/.next/server/pages/api/search.js:213:34)
at async handler (/var/task/.next/server/pages/api/search.js:264:25)
at async /var/task/node_modules/@sentry/nextjs/cjs/common/wrapApiHandlerWithSentry.js:153:35 {
code: '26000',
sourceError: undefined
}
2023-10-30T17:38:36.008Z	31e8caa3-a553-4b28-b972-526e760fb89b	ERROR	NeonDbError: db error: ERROR: prepared statement "s1803523" does not exist
Caused by:
ERROR: prepared statement "s1803523" does not exist
at /var/task/node_modules/@neondatabase/serverless/index.js:1530:11
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async FilingService.listFilings (/var/task/.next/server/chunks/394.js:34:26)
at async Promise.all (index 0)
at async search (/var/task/.next/server/pages/api/search.js:213:34)
at async handler (/var/task/.next/server/pages/api/search.js:264:25)
at async /var/task/node_modules/@sentry/nextjs/cjs/common/wrapApiHandlerWithSentry.js:153:35 {
code: '26000',
sourceError: undefined
}
RequestId: 31e8caa3-a553-4b28-b972-526e760fb89b Error: Runtime exited without providing a reason
Runtime.ExitError
END RequestId: 31e8caa3-a553-4b28-b972-526e760fb89b
REPORT RequestId: 31e8caa3-a553-4b28-b972-526e760fb89b	Duration: 1294.55 ms	Billed Duration: 1295 ms	Memory Size: 1024 MB	Max Memory Used: 155 MB

ERROR: prepared statement "s1803523" does not exist

Looks like your are using prepared statements over pooled connections. That is not expected to work with the current pgbouncer: https://neon.tech/docs/connect/connection-pooling#connection-pooling-notes-and-limitations
There are active attempts to fix that on the pgbouncer side: https://github.com/pgbouncer/pgbouncer/pull/845 But it is not fully baked yet: https://github.com/pgbouncer/pgbouncer/issues/974

If there's a prepared statement, it's done by vercel storage?
import { sql } from "@vercel/postgres";
export class FilingService {
async listFilings(ticker: string, limit: number = 100): Promise<IFiling[]> {
const { rows } = await sql      SELECT id, path, ticker, form, period, filing_date       FROM filing_file_2       WHERE ticker = ${ticker}       AND is_entrypoint = true       AND (form = '10-K' OR form = '10-Q')       ORDER BY filing_date DESC       LIMIT ${limit}    ;
return rows.map(asFiling);
}
}

Ok, then the story is a bit different here. Serverless driver (@vercel/postgres imports @neondatabase/serverless -- you can see that in the backtrace) uses our http proxy instead of direct database connection. Http proxy uses extended postgres protocol which uses protocol-level prepared statements and proxy has it's own connection pool.
When you use serverless driver against -pool url you end up with a following configuration: backend -> http proxy -> pgbouncer -> postgres. And since http proxy uses prepared statements pgbouncer sometimes may return an error that you are seeing.
Quick fix: drop -pool, use direct postgres connection
Longer fix: that is a footgun and we should also fix that on our side. E.g. drop -pool when connection is done to http proxy. But keep it in the websockets case.

Our database are managed by Vercel. If I understand correctly from the doc, the only way to move away from pooling is using something like this:
import { QueryResult, QueryResultRow, createClient } from "@vercel/postgres";

class SqlService {
  public async query<T extends QueryResultRow>(query: string, params?: any[]): Promise<QueryResult<T>> {
    const client = createClient();
    await client.connect();
    try {
      const res = await client.query<T>(query, params);
      return res;
    } finally {
      await client.end();
    }
  }
}

But then our performance goes to trash and we're not better off. API that used to be sub-1 second now take 16 seconds.

With Neon you always have two endpoints to connect to, e.g. ep-plain-thunder-3097180.eu-central-1.aws.neon.tech and ep-plain-thunder-3097180-pooler.eu-central-1.aws.neon.tech. You can remove -pooler part from process.env.POSTGRES_URL and end up with the direct database connection.
I understand that it is a footgun, and no much of handles are exposed to you through Vercel.  Above is a temp fix.

@passgoco @edouard-blocktool things are back to normal again and you can use pooled connections as well. We've traced this down to the backward-incompatible change we made. Turns out that pgbouncer works well with anonymous prepared statements and external people depend on that (originally we thought that it shouldn't work at all). Sorry for causing a trouble. We are going to invest some time into building a tests suite that checks compatibility with @vercel/postgres on end-to-end deployment.


Light bulbs not found; error in the log

Logger: homeassistant.components.light
Source: helpers/entity_platform.py:344
Integration: Light (documentation, issues)
First occurred: 19:41:39 (1 occurrences)
Last logged: 19:41:39
Error while setting up dirigera_platform platform for light
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 344, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/dirigera_platform/light.py", line 44, in async_setup_entry
hub_lights = await hass.async_add_executor_job(hub.get_lights)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/deps/lib/python3.12/site-packages/dirigera/hub/hub.py", line 137, in get_lights
return [dict_to_light(light, self) for light in lights]
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/deps/lib/python3.12/site-packages/dirigera/devices/light.py", line 109, in dict_to_light
return Light(
^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/main.py", line 341, in init
raise validation_error
pydantic.error_wrappers.ValidationError: 1 validation error for Light
room
field required (type=value_error.missing)

I tried to call the dump service, but i can't find the output. Tried the logs, but found the error above.

2024-02-28 22:46:08.164 ERROR (MainThread) [homeassistant.components.light] Error while setting up dirigera_platform platform for light
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 344, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/dirigera_platform/light.py", line 44, in async_setup_entry
hub_lights = await hass.async_add_executor_job(hub.get_lights)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/deps/lib/python3.12/site-packages/dirigera/hub/hub.py", line 137, in get_lights
return [dict_to_light(light, self) for light in lights]
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/deps/lib/python3.12/site-packages/dirigera/devices/light.py", line 109, in dict_to_light
return Light(
^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/main.py", line 341, in init
raise validation_error
pydantic.error_wrappers.ValidationError: 1 validation error for Light
room
field required (type=value_error.missing)
2024-02-28 22:46:08.610 DEBUG (MainThread) [custom_components.dirigera_platform] Found 0 env devices to setup...
2024-02-28 22:46:08.610 DEBUG (MainThread) [custom_components.dirigera_platform] Found 0 env entities to setup...
2024-02-28 22:46:08.611 DEBUG (MainThread) [custom_components.dirigera_platform] EnvSensor & Controllers Complete async_setup_entry
2024-02-28 22:46:08.656 DEBUG (MainThread) [custom_components.dirigera_platform] Found 0 motion_sensor entities to setup...
2024-02-28 22:46:08.656 DEBUG (MainThread) [custom_components.dirigera_platform] Found 0 open close entities to setup...
2024-02-28 22:46:08.656 DEBUG (MainThread) [custom_components.dirigera_platform] Binary Sensor Complete async_setup_entry
2024-02-28 22:46:38.129 DEBUG (SyncWorker_24) [custom_components.dirigera_platform] outlet update...
2024-02-28 22:46:51.888 INFO (SyncWorker_5) [custom_components.dirigera_platform] === START Devices JSON ===
2024-02-28 22:46:51.889 INFO (SyncWorker_5) [custom_components.dirigera_platform] --------------

As you would see in the logs there are no devices that it could read from the hub. Possibly the hub was not setup correctly with the integration. The JSON dump is nothing
2024-02-28 22:46:51.888 INFO (SyncWorker_5) [custom_components.dirigera_platform] === START Devices JSON ===
2024-02-28 22:46:51.889 INFO (SyncWorker_5) [custom_components.dirigera_platform] --------------

Funny, the light bulbs work fine in IKEA Smart Home and Apple Homekit, but they don't show up in this integration.


Fixed images being used as a pointStyle not rendering at custom dimensions

Added width + height arguments to ctx.drawImage when using an image as a pointStyle.
Previous functionality meant that images would be drawn at their source file size regardless of whether custom width or height properties were set.

Looks like a good fix. Is there an open issue for this already?

I believe https://github.com/chartjs/Chart.js/issues/3681 is related, but is closed


Building "examples" when the rest of the code is already compiled

I have tried to build the files in the "examples" directory, while the code was already compiled. Here the list of my commands:
mkdir build
cd build
cmake ..
make
but compiling fails.
A working alternative is to build the whole source from scratch and using the -DBuildExamples=ON flag. I am wondering if this can be avoided by a suitable configuration in the "examples" directory.

Hi @luigi-iap , you have to add the option -DBuild Examples=ON to the cmake command.
For example, consider that you  initially compiled with:
$ mkdirbuild; cd build
$ cmake -DIqsPython=OFF ..
$ make
To add the examples, from the $REPO/build/ folder just run:
$ cmake -DBuildExamples=ON ..
$ make
I just tested it with the master branch and it worked.
Executable files are generated in $REPO/examples/bin/ folder.
Gian

Hi Gian,
thanks for your comment! Yes, compiling the code in the first place with  -DBuildExamples=ON is the right thing to do. In this way, if a single file in the examples folder is edited, the make command will compile it and it only. On a related topic, I discussed with @fbaru-dev to document how to add a new file in the example directory (or in a arbitrary location) and have it properly complied, as it can be beneficial for new users. This can be followed up separately, so that this issue can be closed, if you want.
Cheers,
Luigi

Good suggestion!
I created two entries to the Q&A wiki:
https://github.com/iqusoft/intel-qs/wiki/Q&A
One about compiling the examples, and one about adding a new example.
I will close the issue.


No license

Could you add an open source friendly license? This is the closest dynamic inventory script that meets my needs and I would like to redistribute with attribution if possible.

Sure. License coming right up ...

There you go. Actually, I have a much better version that uses JSON instead my weird self-made format for metadata. If you're interested, I push an update.


Enable asserts for Analytics.development(...) constructor

Adding asserts using the development constructor will enable developer's using this package to test against GA4 limitations
First use case should be to check that each event parameter value is less than 100 characters

Looking to using the FileStat object on the homeDirectory instance variable and check that write is enabled

Completed after #96 was merged in


Homepage Issue on mobile (IOS Safari)

Observed/problematic behavior
Entering hangar via IOS Safari results in {search_term_string} being auto-filled into the search bar.
Screenshot (misusing Discord here):
https://cdn.discordapp.com/attachments/683623330254815262/1062459269577986058/image.png
Expected behavior
It stays empty
Steps to reproduce
Open Safari (latest version)
Open Hangar
Other
No response

can't repro, pls include more steps (how did you access hangar, what decide/browser version, does it happen if you just manually enter the url, etc)

(fwiw that search term string thing is a thing for google to display a search box in the SERP, which google right now doesn't even serve)


Move loop trade and verify balances of reserves into one function

Bytecode size only increases 4 compare to current Katalyst branch


Synthesis failed for Google.Cloud.OsLogin.Common

Hello! Autosynth couldn't regenerate Google.Cloud.OsLogin.Common. :broken_heart:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth-Google.Cloud.OsLogin.Common'
Cloning into '/tmpfs/tmp/tmpr8_c_f_2/googleapis'...
Note: checking out 'e7d1b4da09b6faa48a47f3f5c02e4bfd1bc4ae8c'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at e7d1b4da0 chore: set Ruby namespace in proto options
Note: checking out '5077b1e4674afdbbf11dac3f5f43d36285ba53ff'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 5077b1e4 chore: set Ruby namespace in proto options
Switched to a new branch 'autosynth-Google.Cloud.OsLogin.Common-70'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-04-04 22:43:52,057 synthtool > Executing /tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.OsLogin.Common/synth.py.
Skipping microgenerator fetch/build: already built, and running on Kokoro
Building existing version of Google.Cloud.OsLogin.Common for compatibility checking
Generating Google.Cloud.OsLogin.Common
Building new version of Google.Cloud.OsLogin.Common for compatibility checking

Changes in Google.Cloud.OsLogin.Common:
Diff level: Identical

2020-04-04 22:44:03,303 synthtool > Wrote metadata to synth.metadata.
Changed files:
M apis/Google.Cloud.OsLogin.Common/Google.Cloud.OsLogin.Common/Common.cs
 M apis/Google.Cloud.OsLogin.Common/synth.metadata
[autosynth-Google.Cloud.OsLogin.Common-70 23a031c4c] ignored
 2 files changed, 7 insertions(+), 5 deletions(-)
HEAD is now at 23a031c4c ignored
Switched to branch 'autosynth-Google.Cloud.OsLogin.Common'
Previous HEAD position was 5077b1e4 chore: set Ruby namespace in proto options
HEAD is now at 7be2811a fix: Update gapic-generator version to pickup discogapic fixes
Note: checking out '98024617efce32982bd763ad14f00c9bc0819bea'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 98024617e Touch all the synth.metadata files again
Switched to a new branch 'autosynth-Google.Cloud.OsLogin.Common-0'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-04-04 22:44:03,966 synthtool > Executing /tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.OsLogin.Common/synth.py.
Skipping microgenerator fetch/build: already built, and running on Kokoro
Building existing version of Google.Cloud.OsLogin.Common for compatibility checking
Generating Google.Cloud.OsLogin.Common
git detects no change in Google.Cloud.OsLogin.Common; skipping compatibility checking
2020-04-04 22:44:07,094 synthtool > Wrote metadata to synth.metadata.
Changed files:
M apis/Google.Cloud.OsLogin.Common/synth.metadata
HEAD is now at 98024617e Touch all the synth.metadata files again
Switched to branch 'autosynth-Google.Cloud.OsLogin.Common'
Note: checking out 'e7d1b4da09b6faa48a47f3f5c02e4bfd1bc4ae8c'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at e7d1b4da0 chore: set Ruby namespace in proto options
Previous HEAD position was 7be2811a fix: Update gapic-generator version to pickup discogapic fixes
HEAD is now at a62857d2 fix: add proto_package to the artman config of dataproc v1beta2 to make artman smoketest pass.
Switched to a new branch 'autosynth-Google.Cloud.OsLogin.Common-35'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-04-04 22:44:07,774 synthtool > Executing /tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.OsLogin.Common/synth.py.
Skipping microgenerator fetch/build: already built, and running on Kokoro
Building existing version of Google.Cloud.OsLogin.Common for compatibility checking
Generating Google.Cloud.OsLogin.Common
git detects no change in Google.Cloud.OsLogin.Common; skipping compatibility checking
2020-04-04 22:44:10,882 synthtool > Wrote metadata to synth.metadata.
Changed files:
M apis/Google.Cloud.OsLogin.Common/synth.metadata
HEAD is now at e7d1b4da0 chore: set Ruby namespace in proto options
Switched to branch 'autosynth-Google.Cloud.OsLogin.Common'
Previous HEAD position was a62857d2 fix: add proto_package to the artman config of dataproc v1beta2 to make artman smoketest pass.
HEAD is now at 7be2811a fix: Update gapic-generator version to pickup discogapic fixes
Note: checking out 'bbccd6f6bab68a4c087bba2bb6ef6a8a5d585fe8'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at bbccd6f6b docs: change a relative URL to an absolute URL to fix broken links.
Switched to a new branch 'autosynth-Google.Cloud.OsLogin.Common-17'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-04-04 22:44:11,492 synthtool > Executing /tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.OsLogin.Common/synth.py.
Skipping microgenerator fetch/build: already built, and running on Kokoro
Building existing version of Google.Cloud.OsLogin.Common for compatibility checking
Generating Google.Cloud.OsLogin.Common
git detects no change in Google.Cloud.OsLogin.Common; skipping compatibility checking
2020-04-04 22:44:14,840 synthtool > Wrote metadata to synth.metadata.
Changed files:
M apis/Google.Cloud.OsLogin.Common/synth.metadata
HEAD is now at bbccd6f6b docs: change a relative URL to an absolute URL to fix broken links.
Switched to branch 'autosynth-Google.Cloud.OsLogin.Common'
HEAD is now at 7be2811a fix: Update gapic-generator version to pickup discogapic fixes
Note: checking out '2d2058e68e3ce324757a33c430ccd7fa7e8906e6'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 2d2058e68 Update Storage dependencies
Switched to a new branch 'autosynth-Google.Cloud.OsLogin.Common-8'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-04-04 22:44:15,430 synthtool > Executing /tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.OsLogin.Common/synth.py.
Skipping microgenerator fetch/build: already built, and running on Kokoro
Building existing version of Google.Cloud.OsLogin.Common for compatibility checking
Generating Google.Cloud.OsLogin.Common
git detects no change in Google.Cloud.OsLogin.Common; skipping compatibility checking
2020-04-04 22:44:18,537 synthtool > Wrote metadata to synth.metadata.
Changed files:
M apis/Google.Cloud.OsLogin.Common/synth.metadata
HEAD is now at 2d2058e68 Update Storage dependencies
Switched to branch 'autosynth-Google.Cloud.OsLogin.Common'
HEAD is now at 7be2811a fix: Update gapic-generator version to pickup discogapic fixes
Note: checking out '617763f529fd47491bac379abad3f7bac53d3726'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 617763f52 For Secret Manager v1 and v1beta1, noted Secret ID character limitations.
Switched to a new branch 'autosynth-Google.Cloud.OsLogin.Common-4'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-04-04 22:44:19,154 synthtool > Executing /tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.OsLogin.Common/synth.py.
Skipping microgenerator fetch/build: already built, and running on Kokoro
Building existing version of Google.Cloud.OsLogin.Common for compatibility checking
Generating Google.Cloud.OsLogin.Common
git detects no change in Google.Cloud.OsLogin.Common; skipping compatibility checking
2020-04-04 22:44:22,288 synthtool > Wrote metadata to synth.metadata.
Changed files:
M apis/Google.Cloud.OsLogin.Common/synth.metadata
HEAD is now at 617763f52 For Secret Manager v1 and v1beta1, noted Secret ID character limitations.
Switched to branch 'autosynth-Google.Cloud.OsLogin.Common'
HEAD is now at 7be2811a fix: Update gapic-generator version to pickup discogapic fixes
Note: checking out '99d78d13bfbf741d1ac3e3b7508f7078e009007d'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 99d78d13b Add documentation link for Service Directory
Switched to a new branch 'autosynth-Google.Cloud.OsLogin.Common-2'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-04-04 22:44:22,882 synthtool > Executing /tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.OsLogin.Common/synth.py.
Skipping microgenerator fetch/build: already built, and running on Kokoro
Building existing version of Google.Cloud.OsLogin.Common for compatibility checking
Generating Google.Cloud.OsLogin.Common
git detects no change in Google.Cloud.OsLogin.Common; skipping compatibility checking
2020-04-04 22:44:26,028 synthtool > Wrote metadata to synth.metadata.
Changed files:
M apis/Google.Cloud.OsLogin.Common/synth.metadata
HEAD is now at 99d78d13b Add documentation link for Service Directory
Switched to branch 'autosynth-Google.Cloud.OsLogin.Common'
HEAD is now at 7be2811a fix: Update gapic-generator version to pickup discogapic fixes
Note: checking out '0c88ce0da0e66910735643832b237c9f873b05e6'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 0c88ce0da Add a new AuthorizationType for Data Source Definition.
Switched to a new branch 'autosynth-Google.Cloud.OsLogin.Common-1'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-04-04 22:44:26,621 synthtool > Executing /tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.OsLogin.Common/synth.py.
Skipping microgenerator fetch/build: already built, and running on Kokoro
Building existing version of Google.Cloud.OsLogin.Common for compatibility checking
Generating Google.Cloud.OsLogin.Common
git detects no change in Google.Cloud.OsLogin.Common; skipping compatibility checking
2020-04-04 22:44:29,880 synthtool > Wrote metadata to synth.metadata.
Changed files:
M apis/Google.Cloud.OsLogin.Common/synth.metadata
HEAD is now at 0c88ce0da Add a new AuthorizationType for Data Source Definition.
Switched to branch 'autosynth-Google.Cloud.OsLogin.Common'
On branch autosynth-Google.Cloud.OsLogin.Common
nothing to commit, working tree clean
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 484, in <module>
    main()
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 370, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 474, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 284, in synthesize_loop
    synthesize_range(toolbox, synthesizer)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 306, in synthesize_range
    toolbox.patch_merge_version(young)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 146, in patch_merge_version
    comment or self.versions[index].version.get_comment()
  File "/tmpfs/src/git/autosynth/autosynth/git.py", line 95, in commit_all_changes
    subprocess.check_call(["git", "commit", "-m", message])
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['git', 'commit', '-m', 'Add a new AuthorizationType for Data Source Definition.\n\nhttps://github.com/googleapis/google-cloud-dotnet/commit/0c88ce0da0e66910735643832b237c9f873b05e6\ncommit 0c88ce0da0e66910735643832b237c9f873b05e6\nAuthor: yoshi-automation<EMAIL_ADDRESS>  Wed Apr 1 02:27:58 2020 -0700\n\n    Add a new AuthorizationType for Data Source Definition.\n    \n    https://github.com/googleapis/googleapis/commit/17cfae00f2bb51cb1683f017da7e295a1b0f01a8\n    commit 17cfae00f2bb51cb1683f017da7e295a1b0f01a8\n    Author: Google APIs<EMAIL_ADDRESS>  Date:   Tue Mar 31 10:21:11 2020 -0700\n    \n        Add a new AuthorizationType for Data Source Definition.\n    \n        PiperOrigin-RevId: 303992863']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


[RFC] Drop setup scripts and replace with docs

Proposal:
Drop setup scripts in Potential, Gravity and other repos and replace them with playbooks specifying which dependencies need to be installed.
Reasoning
While setup scripts for onboarding new developers like  in Potential or getting set up with Gravity are intended to  be convenient, in practice they  often prove a hinderance to getting a development environment set up, due to differences in platform  (Darwin / Linux) package managers (apt / brew)  or changing dependencies in Homebrew cask / mainline versions of software like Java and Elasticsearch.
This RFC aims to drop these scripts completely, and instead simply  specify which dependencies are required for a given project and let the developer install and configure them by their own methods.
Exceptions:
I  don't see any exceptions - I  think this is an example of overengineering and adopting this would mean we trust our developers to be proficient enough to configure their own workstations.
Additional Context:
See problems recently with Homebrew and Java distributions https://github.com/artsy/potential/pull/353
How is this RFC resolved?
Dropping setup scripts in Potential and Gravity and replacing them with documentation.

I'm on board! My approach to setup is reflected here:
https://github.com/artsy/impulse/blob/7c3a158263ef73566ea1a8a8b9b13e6c39c2d896/bin/setup
This setup script is specific to Impulse and rather than trying to install things for you, merely checks for what the project will need and alerts the developer about how they may want to install it. It's not perfect mind you, but I believe it's on the right track. That part about setting up an upstream remote sorta seems stale, but I digress...
My preference is for setup scripts to be defined on each project and to fail with good errors when things aren't installed that the project depends on, but not to take that extra step of installing them for me.

I like the setup scripts -- for me they've worked the majority of the time, and when they haven't, they still provided me guidance on what I needed to do to complete the setup. The most time I ever spent on a setup script was when I first started, and I didn't know anything about ruby or ruby version managers. I needed a lot of help to get past those steps, but I would have needed help whether I tried to run a script or follow docs.
I'm also afraid that using docs instead of scripts would result in more time spent helping people figure out which dependency they missed while setting things up themselves.

+1 to @jonallured's impulse script! I actually haven't seen that approach before and it makes an enormous amount of sense; most, if not all, setup scripts on artsy repos have failed me in one way or another for any number of reasons.

I'm a big fan of setup scripts, even if Eigen doesn't take full advantage of them 🙈 When I've needed to work in other projects, like Pulse or Gravity, having a script helps me get productive quickly. Even if they fail, I know where they fail and can get that step done manually, and then re-run.
I would be in favour of adopting Jon's approach to scripts, to be more developer-friendly, but I wouldn't want to throw away the value of setup scripts because of one problem installing one dependency.

I like the setup scripts -- for me they've worked the majority of the time, and when they haven't, they still provided me guidance on what I needed to do to complete the setup. The most time I ever spent on a setup script was when I first started, and I didn't know anything about ruby or ruby version managers. I needed a lot of help to get past those steps, but I would have needed help whether I tried to run a script or follow docs.

I sort of agree with this - I have encountered the situation where a setup script doesn't work but it does provide me guidance on what I should do - that said I get into the position running a setup script that it fails halfway through, I change the failed command and install a dependency some other way, then copy-paste the rest of the script into the terminal. At this point I am doing things manually so would have just preferred a doc so give up on running the script.  That's sort of the motivation behind this RFC.
At this point I see running these scripts as a bad idea because it may try and configure something I don't want, i.e. the project may use rbenv while I use rvm or it may try to install a cask version of Java while I have it already installed some other way from some other project, or install a brew version of Postgres where I may have installed it some other way.
I think my problem with these scripts is that they all assume you are starting from a clean slate?

I'm also afraid that using docs instead of scripts would result in more time spent helping people figure out which dependency they missed while setting things up themselves.

I think this time well spent though.  Perhaps an approach to scripts like @jonallured 's script above makes it more pedagogical, which is what I am trying to get at here - more instructive, less automation.

Here's an example of what I see as this anti-pattern in Gravity's setup scripts https://github.com/artsy/gravity/blame/master/script/setup#L16
svn export https://github.com/artsy/docker-images/trunk/elasticsearch/5.6/artsy-similarity-plugin-1.0<EMAIL_ADDRESS>--force

This script assumes you have svn installed and newer versions of Xcode don't - ran into this with @alexpopa-artsy the other day.  Additionally it assumes you want to install our custom similarity plugin to a brew-installed elasticsearch.
What we need to do is download the jar https://github.com/artsy/docker-images/raw/master/elasticsearch/5.6/artsy-similarity-plugin-1.0/artsy-similarity-plugin-1.0.jar and place it in your local elasticsearch's ./plugins directory.  But I think this script obfuscates what we actually need to do here and we would be better off just documenting this.

Totally. for this one for example we could document that this jar is needed, with an example of how to get it using svn and the next dev that does it with wget can add this as an example as well. but the main thing is you need that jar, so if someone is confident they know how to get it, great. if not, they can look at the examples for instructions/inspiration.

I disagree that docs will tend to be more accurate or reliably updated than a script. If you compare our own org's docs to its  code, I think you'll find that--while they both need regular maintenance and can fall out-of-date--code is more likely to receive that care.

Let's assume we are all proficient developers here...

This runs contrary to the principles of safe, fast, high-quality software development. So much of our process (code review, mentorship, incident-handling, style guides, continuous integration...) is designed to converge our work product on the best any of us can produce, rather than assume we'll each produce brilliant work independently, all of the time, in every technical context. Our areas of inexpertise are all different, but we all have them.
We've always tolerated variety in development environments, but we have so many projects and dependencies and stacks that I think it's critical that there be a default and easy way to get any particular project running. The burden to customize should be on those with divergent preferences, not those just trying to get started or get something done. This "default" won't satisfy everyone, but it will allow us to do more diverse and powerful things.
That said, we could make these assumptions more explicit and better support opt-outs. I like the idea in the examples above, of making setup scripts more self-describing. I'd go a step further and recommend that the scripts default to performing the setup steps rather than just describing them (where possible), with the option to skip any particular step. There's a fine line here between making setup scripts more general and dynamic, and doing too much ugly bash-scripting, but I hope we can find a balance of simplicity and flexibility.
Relevant:

Runbook is an interesting approach to this combination of manual and automatic steps.
The Google SRE chapter about Eliminating Toil describes the costs and risks of this sort of manual work, even when it's something we might enjoy.

(Re. using svn to install the custom Elasticsearch plug-in, I hated it too but it appeared to be the most concise, already-available method to download a subdirectory from a github repository. That followed repeated confusion from developers trying and failing to run tests, needing to comment out lines in the source, and at one point mistakenly disabling custom similarity in master.)

Edited the expected outcome of this RFC to be a playbook or other docs on dependency management, because I don't see a silver bullet here in any approach.

I'm a :+1: on removing setup scripts wherever possible and standardizing them where it isn't. Due to being setup scripts (& thus how infrequently they are used) they tend to be one of the most brittle parts of an application setup, and are often run by someone who is new to a repository, possibly obscuring helpful context with a more black-boxed script.
I also agree that most language and version manager installations should be specified as prerequisites and entrusted to the owner of the development environment. In general I disagree that a buggy script is good because it makes you learn something.
If some people like them a more happy medium might be to standardize these where we do use them - maybe using Makefiles (unless there is a better general task runner for unix systems), and

make them as explicit as possible (eg log why a command is running and exactly what it is prior to executing it) - also possible with --dry-run on makefiles
include separate tasks for installing very specific tools as a convenience but not execute them automatically (eg, if sbt is not installed, exit with a helpful message telling the user they need sbt, don't install it for them, but maybe there is a task for doing so)
require they be idempotent & safe to re-run after a failure

Closing this - let's try and adopt in projects a more generalized or flexible approach to setup scripts via Makefiles or Runbooks.  Thanks all!


Disassembler rounds float constants that are near-to-1 up to 1

Example, a float value of 0x1.fffffep-1 is very nearly 1 but is not 1.
It should be displayed in a bit-preserving way, but instead is rounded up to 1.
So we get
OpConstant %float 1
when we should have had
OpConstant %float 0x1.fffffep-1

It seems odd to me to make exact preservation of floating point constants through disassemble -> assemble just an option. I'd say it is a requirement. I don't really see any harm in outputting 0.1f as 0x1.99999ap-4.

Most people aren't wired to read hex floating point very well. It's not the default for any other environment.  I think I'd have a lot of complaints if I flipped the default at this point.
Also, given variability across implementations, it's hard to identify "the" subset of cases that would benefit from bit-to-bit accuracy of hex floats.

Should the disassembler issue warnings when it outputs floating point values that will not assemble to the same bits?

This appears to be fixed by #1306.
This input (from original report)
%float = OpTypeFloat 32
%near1 = OpConstant %float   0x1.fffffep-1

Assembles to a binary that disassembles to this:
; SPIR-V
; Version: 1.3
; Generator: Khronos SPIR-V Tools Assembler; 0
; Bound: 3
; Schema: 0
      %float = OpTypeFloat 32
%float_0_99999994 = OpConstant %float 0.99999994

That then re-assembles to a binary with same binary contents as the original (byte for byte equality).
So I think the problem is resolved.


filter-doc-log.sh: Fix error for empty log file

Running 'make html' in doc/ when doc.log is missing or empty gives the
following error if sphinx-build doesn't write anything on stdout/stderr:
Error in ./scripts/filter-doc-log.sh: logfile "doc.log" not found.
Makefile:84: recipe for target ”html” failed
make: *** [html] Error 1

The problem is that scripts/filter-doc-log.sh tests for the existence of
the log file with [ -s ${LOG_FILE} ], which requires it to be nonempty.
Fix it by using -e instead, which only checks if the log file exists.
scripts/filter-known-issues.py ($KI_SCRIPT) seems to be able to deal
with empty files (and runs quickly).
Fixes #6854
Signed-off-by: Ulf Magnusson<EMAIL_ADDRESS>

Codecov Report

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

@@            Coverage Diff             @@
##           master    #6855      +/-   ##
==========================================
- Coverage   54.89%   54.89%   -0.01%
==========================================
  Files         449      449
  Lines       43328    43328
  Branches     8157     8157
==========================================
- Hits        23785    23784       -1
- Misses      16241    16242       +1
  Partials     3302     3302

Impacted Files
Coverage Δ

kernel/posix/pthread.c
69.5% <0%> (-0.5%)
:arrow_down:

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 d5a2400...9f54b05. Read the comment docs.


Mobile menu doesn't push down hero far enough

Tested on Android mobile device via Firefox browser.
Expanded hamburger menu does not push down our monoLambda title / hero down far enough, and cuts off "We Are".

Good catch, I think we can squeeze it in to #33 since it's still a navBar thing.

We decided that this will be fixed in a new PR.


Add bart.base to README (fixes #2189)

Hi,
I would like to ask what is the pretraining objective to this model.
I cannot find the pretraining objective in the file and the paper.
It will be grateful if you can answer my question.
Best,
Chris Lin


How to train the model with this library?

Hi,
Is there a way to train the model with custom data? Like a text file that can be indexed?

no plan for this. you should try pytorch/tensorflow


Turn on the flows section could be revised

[Enter feedback here]
Turn on the flows
This is a section header but without instruction on how to turn on a flow, granted should be known, but for consistency, should mention that 1 you need to turn them on, and 2 how.

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

ID: 1c74207b-a220-3f22-4f0a-1505c8848770
Version Independent ID: 49a8f967-a8a6-5500-dbd9-256d568d73f9
Content: Set up Innovation Backlog components - Power Platform
Content Source: power-platform/guidance/coe/setup-innovationbacklog.md
Service: power-platform
Sub-service: guidance
GitHub Login: @manuelap-msft
Microsoft Alias: mapichle

Thanks for your comment, @mthenot-msft. This issue has been assigned to the doc author for review.

Thanks for the feedback - we can definitely improve on that section! I have put this on our list for the next docs update!


report generation in crudbooster

how to generate reports in crudbooster. can you show me with the help of example?

did u get it?


Add support for /search/code

Search 3.0.0 support isn't at 100%. This endpoint is missing. If anybody wants very basic support quickly, see my fork. Ideally, we would get a full PR together to submit, but don't have time right now.

This has been implemented recently.


Investigate Edge extension ownership of networking related integration testing

Linked to https://github.com/adobe/aepsdk-edge-ios/issues/408
Task description
Need to investigate the use cases across extensions that depend on Edge Network extension, and see if it is sufficient for Edge Network extension to own all networking related integration testing cases. That is, the ones dealing with NetworkRequest and HttpConnection
Additional implementation details or code snippet(s)
No response

Solved as part of iOS, Edge extension will be testing the APIs contract overall, and other Edge extensions may choose to do additional testing with request/response asserts as needed.


Clean up Synthesis optimizer

change Synthesis._init_optimizer so it expects a string with possible values 'SGD' and 'Adam' or an optimizer object. Then change my code that uses SWA to hand that object directly to it.

then remove SWA and the torchcontrib requirement.

For coarse-to-fine, will need to reset optimizer lr to the initial one: stackoverflow

As part of this, will need to move creation of initial noise (for Synthesis) into __init__ (from synthesis) so that user can pass it to their custom optimizer object. This requires moving seed and we should therefore double-check that optimizer (Adam and SGD at least) don't depend on RNG state

Done with #75


Broken backlink alert sends double messages

Description
Broken backlink alert sends double messages when reporting:

First message is sent when the csv file is uploaded
Second message is sent when the alert is sent

Expected behavior
Post processor should ideally send a single message per site.

:tada: This issue has been resolved in version 1.3.4 :tada:
The release is available on:

v1.3.4
GitHub release

Your semantic-release bot :package::rocket:


Link Datadog Deployment to Configmaps

This commit adds a hash annotation to each of the configmaps in this
chart, as well as the deployment that is dependent on these configmaps.
This will cause the deployment to restart its pods if any of these
configmaps changes.

cc @hkaj for review.

/ok-to-test


Lint/FormatParameterMismatch ignores % if LHS or RHS is not a literal

If the LHS is not a literal, it could evaluate to a format string with any
number of arguments, so we can't count an offense for that. On the other hand,
if the RHS is not a literal, it could evaluate to an array with any number
of arguments, so we can't count an offense for that either.
Fixes #2307.

The code looks good. My remark about literal? was orthogonal to the PR in question. Thanks!


Automated cherry pick of #3813: aws upload image bugfix & huawei change default disk type to SAS

Cherry pick of #3813 on release/2.13.
#3813: aws upload image bugfix & huawei change default disk type to SAS

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.13@74a6040). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.13   #3818   +/-   ##
==============================================
  Coverage                ?   6.92%
==============================================
  Files                   ?     499
  Lines                   ?   84257
  Branches                ?       0
==============================================
  Hits                    ?    5837
  Misses                  ?   77924
  Partials                ?     496

Flag
Coverage Δ

#aFlag
6.92% <0%> (?)

Impacted Files
Coverage Δ

pkg/multicloud/aws/image.go
0% <0%> (ø)

pkg/compute/guestdrivers/huawei.go
9.61% <0%> (ø)

pkg/multicloud/aws/storagecache.go
0% <0%> (ø)

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 74a6040...f2fdbec. Read the comment docs.

/approve

/lgtm

/approve


set_name and init_subclass called in unexpected order

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
The order in which descriptor __set_name__ and model __init_subclass__ methods are called differs from typical Python classes. Typical Python classes trigger __set_name__ methods before calling __init_subclass__ while classes inheriting from Pydantic's BaseModel do so in the reverse order - __init_subclass__ and then __set_name__.
Example Code
from pydantic import BaseModel

class ExampleDescriptor:
    def __set_name__(self, owner, name):
        print("first")

print("--- pydantic ---")

class PydanticParent(BaseModel):
    def __init_subclass__(cls) -> None:
        print("second")

class PydanticChild(PydanticParent):
    _a = ExampleDescriptor()

print("--- no-pydantic ---")

class NoPydanticParent:
    def __init_subclass__(cls) -> None:
        print("second")

class NoPydanticChild(NoPydanticParent):
    _a = ExampleDescriptor()

Printout
--- pydantic ---
second
first
--- no-pydantic ---
first
second

Python, Pydantic & OS Version
             pydantic version: 2.5.3
        pydantic-core version: 2.14.6
          pydantic-core build: profile=release pgo=true
                 install path: /Users/ryanmorshead/.mambaforge/envs/my-env/lib/python3.10/site-packages/pydantic
               python version: 3.10.6 | packaged by conda-forge | (main, Aug 22 2022, 20:38:29) [Clang 13.0.1 ]
                     platform: macOS-14.2.1-arm64-arm-64bit
             related packages: pyright-1.1.338 typing_extensions-4.7.1

Looking at the code, the fact that Pydantic moves things into a __private_attributes__ dict means that there is simply no way for the typical class construction machinery to trigger __set_name__ methods of descriptors in the expected order. With that said it looks like there is a __pydantic_init_subclass__ method that is called in the expected order. So the following works as expected:
from pydantic import BaseModel

class ExampleDescriptor:
    def __set_name__(self, owner, name):
        print("first")

class PydanticParent(BaseModel):
    @classmethod
    def __pydantic_init_subclass__(cls) -> None:
        print("second")

class PydanticChild(PydanticParent):
    _a = ExampleDescriptor()

One way to address this issue without __pydantic_init_subclass__ could be to move things under __private_attributes__ after calling super().__new__ on the metaclass so that the standard class construction machinery could trigger __set_name__ instead of manually having to do so.

Never mind. I just need to declare ignore_types.


Font size in  or  results in tall table cell

How can we reproduce this bug?

or, with Inky PR 60:
<h-line>

What did you expect to happen?
A table cell with a border as defined by $hr-border but no height.
What happened instead?
A table cell with height determined by font-size.
What email clients does this happen in?
All?  Probably need something like font-size:0; in _typography.scss for table.hr th.

@rafibomb


RibbonLoadBalancingHttpClient issue with zuul and secured service

This is similar to https://github.com/spring-cloud/spring-cloud-netflix/issues/1126, but using RibbonLoadBalancingHttpClient instead of RibbonLoadBalancerClient.
When using a zuul proxy + HttpClientRibbonCommandFactory and targeting a secured service, the request is sent to the secured port in plain http.

Does adding ribbon.IsSecure=true to your properties fix it?

It seems not.
I'm getting false at https://github.com/spring-cloud/spring-cloud-netflix/blob/1.1.x/spring-cloud-netflix-core/src/main/java/org/springframework/cloud/netflix/ribbon/apache/RibbonLoadBalancingHttpClient.java#L73
and the configOverride is null in https://github.com/spring-cloud/spring-cloud-netflix/blob/1.1.x/spring-cloud-netflix-core/src/main/java/org/springframework/cloud/netflix/ribbon/apache/RibbonLoadBalancingHttpClient.java#L121 (from https://github.com/Netflix/ribbon/blob/master/ribbon-loadbalancer/src/main/java/com/netflix/client/AbstractLoadBalancerAwareClient.java#L81).
Also, since we will be migrating from http service to https, some servers will only be available in http during the migration, so I can't simply force an entire service (or even all of them in this case) to be https.

I was probably wrong about the ribbon.IsSecure. It does seems to work, but I'm still having the issue I need to be able to rollout the services from http to https. So, need to able to not change all them at the same time.
I'm testing a potential fix (https://github.com/francistb/spring-cloud-netflix/commit/b9b2b857f05d86e4f797888173c4456e2c61e41f), which is similar to how gh-1126 was fixed.

@francistb there have been some fixes regarding this, can you check with Camden.RELEASE?

Finally had some time to test this, and yes, I can confirm the issue has been fixed. Sorry for the delay.
Thanks !


feat(otlp-trace-exporters): Add User-Agent header to OTLP trace exporters

Which problem is this PR solving?
Updates #3291
Short description of the changes

add user agent to otlp grpc trace exporter
add user agent to otlp http/json trace exporter
add user agent to otlp http/proto trace exporter

I tried adding this to the browser exporter but get an error for setting an Unsafe Header.
This should no longer be forbidden but I wasn't sure what I was missing.
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?

[x] Unit tests

Checklist:

[x] Followed the style guidelines of this project
[x] Unit tests have been added
[ ] Documentation has been updated

I believe it is better making the implementations in the base packages (otlp-exporter-base, otlp-grpc-exporter-base and otlp-proto-exporter-base), which also work as the base packages of metrics/logs exporters.

This should no longer be forbidden but I wasn't sure what I was missing.

That depends on browser implementation. Chrome Browser currently doesn't support that.

I believe it is better making the implementations in the base packages (otlp-exporter-base, otlp-grpc-exporter-base and otlp-proto-exporter-base), which also work as the base packages of metrics/logs exporters.

I started there, but because of the way the headers are built currently, I need them added in the individual exporters. The headers for each exporter are intended to override the generic variables. For example, the OTEL_EXPORTER_OTLP_TRACES_HEADERS are used over OTEL_EXPORTER_OTLP_HEADERS for traces, so even if I set it in base it will get clobbered by the trace-specific setup. If I set them in the base packages, I'll have to update each of these constructors anyway. I'm open to trying that if others agree that is the best way to do this.

This should no longer be forbidden but I wasn't sure what I was missing.

That depends on browser implementation. Chrome Browser currently doesn't support that. I think we can just ignore the warnings.

I was getting errors when running tests. It's possible the issue is that I tried overwriting user agent instead of appending 🤔  I'm definitely less familiar with the browser implementations.
        Error: Uncaught AssertionError: 'Refused to set unsafe header "User-Agent"' === 'Request Timeout' (webpack-internal:///../../../node_modules/assert/assert.js:199)

I believe it is better making the implementations in the base packages (otlp-exporter-base, otlp-grpc-exporter-base and otlp-proto-exporter-base), which also work as the base packages of metrics/logs exporters.

I started there, but because of the way the headers are built currently, I need them added in the individual exporters. The headers for each exporter are intended to override the generic variables. For example, the OTEL_EXPORTER_OTLP_TRACES_HEADERS are used over OTEL_EXPORTER_OTLP_HEADERS for traces, so even if I set it in base it will get clobbered by the trace-specific setup. If I set them in the base packages, I'll have to update each of these constructors anyway. I'm open to trying that if others agree that is the best way to do this.

Let's see what we can do after #3748 being fixed which will change the way headers are merged.

This should no longer be forbidden but I wasn't sure what I was missing.

That depends on browser implementation. Chrome Browser currently doesn't support that. I think we can just ignore the warnings.

I was getting errors when running tests. It's possible the issue is that I tried overwriting user agent instead of appending 🤔 I'm definitely less familiar with the browser implementations.
        Error: Uncaught AssertionError: 'Refused to set unsafe header "User-Agent"' === 'Request Timeout' (webpack-internal:///../../../node_modules/assert/assert.js:199)

The test runs a headless chrome browser and would reject if you try to set the user agent on a request. Maybe we should do a try-catch on the send method of otlp-exporter-base.


Robots.txt new states dissalow after indexing OSS still returns urls as result

Hi,
we're adjusting our robots.txt in our sites, so that only the needed parts get indexed.
So we've put a part of page to dissalow. After that we've put the whole host to "select all url to fetch first".
After now the index did it's job. The disallowed URL have this status:
Robots: Disallow
Fetch: Not allowed
Parsing: Parsed
Index: Indexed
And they are still return as results.
Is this a bug or how do I remove disallowed url from the index?

After playing with URL Browser I encountered a new problem.
Now in the result in Render I have only this url. All other that were indexed are gone. I can see this also in the host facet, because it has only one url.

I everything is going downhill, I've had an idea to just delete all and reindex it from start.
Under Runtime->Commands I've truncated all documents and under Crawler->Web->URL browser I've deleted all URL's.
So now I've thought that I've just start the crawler and it would start at the beginning. But he just keeps running like there is nothing to index.
Can you please help me what to do. Because it would not be great to reconfigure it everything from the scratch.
Just to mention it. If i on the first page click info on the index it still states full size of 1,1GB.
Thanks,
Mojster

How's the progress on this issue?
Have you got any suggestions how to avoid this, because this is quite a showstopper.

Solved one part of this.
So after deleting all data from index and URL database, the crawler did not start again from fresh. Today I found out that I should remove all the URLs from 'Pattern list' and put them back again. Now the crawler is working again.
I would mark this as a bug, but there is a simple fix, if you know about it.
But the main bug still persist (URLs marked as deleted, but still exist in index), without a quick workaround.


TrainProperties.yml blockBreakTypes lists grow unbounded duplicating materials

BkCommonLib version: 1.14.4-v2-SNAPSHOT (build: 650)
TrainCarts version: 1.14.4-v2-SNAPSHOT (build: 543)
Spigot version: git-Paper-221 (MC: 1.14.4)

Problem or bug:
Since a few versions (I usually keep TC and the lib updated from the dev builds on a roughly weekly basis) TrainProperties.yml for existing trains gain duplicate blockBreakTypes each time the server is restarted.
I've got a couple of materials (grass, fern, flowers) in blockBreakTypes of DefaultTrainProperties.yml and it appears that since one or two weeks or so it just appends the items to the block break type lists of all carts in TrainProperties.yml causing unnecessary duplicates and blowing up the size.
Expected behaviour:
blockBreakTypes in TrainProperties.yml keeps the same items in the list as before when restarting and doesn't add duplicates.
Steps to reproduce:

add some block types to all blockBreakTypes lists in DefaultTrainProperties.yml, such as - GRASS and - FERN
reload config
place a minecart or train
restart the server a few times
see the lists in TrainProperties.yml grow longer each time by another set of the same materials

This almost certainly has to do with the recent yaml changes, looking into it now

Not a bug in BKCommonLib, but just a bug in TC that always existed but didn't trigger because it created a new file configuration object every time it saves. To optimize it this was changed, and now that bug appears. Thanks for reporting it!
https://ci.mg-dev.eu/job/TrainCarts/544/

That appears to have fixed it. Thank you.


Prevent faulthandler installation on armv7l

There's no faulthandler package on armv7l from berryconda so
do not attempt to install it.

Codecov Report

Merging #3491 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3491   +/-   ##
=======================================
  Coverage   80.59%   80.59%
=======================================
  Files         392      392
  Lines       79592    79592
  Branches     9052     9052
=======================================
  Hits        64150    64150
  Misses      14030    14030
  Partials     1412     1412


added option to negotiate obsolete SSL ciphers (old windows server)

On some old windows servers, the default client SSL Security Level is set too high (2) to allow the SSL negociation and establish an RDP connection.
The unsafe_ssl option added to the RDPTarget allows to lower this level to 0 aka. "Everything is permitted." .
I'm not sure if I added this in the right place, if not, feel free to tell me where it'd be more appropriate :)
Thanks

Awesome! Thank you!


Fixing bug when underscores appear on the rhs of the decimal

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

Comparison is base (d6b43aa) 96.91% compared to head (ad6cd17) 96.91%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #24   +/-   ##
=======================================
  Coverage   96.91%   96.91%
=======================================
  Files          11       11
  Lines        1525     1525
=======================================
  Hits         1478     1478
  Misses         47       47

Flag
Coverage Δ

unittests
96.91% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

lib/fixedpointmath/fixedpointmath/fixed_point.py
88.44% <100.00%> (ø)

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


Unit tests: Ensure non-empty blocks when expected

AddBlocks has a parameter to determine if we want empty blocks or not.
Sometimes we still ended up with empty blocks though.
This corrects that and updates the Simple unit test to check all blocks ave a tx.

Did calling first_client.putTransaction(tx) in Base create empty blocks??

Did calling first_client.putTransaction(tx) in Base create empty blocks??

The problem was that only a single node had the tx when the time for block creation was set. It then depends on which node nominates first and whether the tx was gossiped to other nodes in time.


Fix: fatal error: 'flutter_sms-Swift.h' file not found

Make this package run-able with ios

iOS does not give access to user's messages.
And in the current state the plugin has no iOS functionality.
So I don't think there is any need to make it work on iOS for now.

iOS does not give access to user's messages.
And in the current state the plugin has no iOS functionality.
So I don't think there is any need to make it work on iOS for now.

hi.. thanks for the response, this PR is not intended to make user message accessible, this PR is intended for the package to be able to compile on IOS device, currently if you try to run flutter app in IOS simulator when this package is installed, it does not run and throw fatal error: 'flutter_sms-Swift.h' file not found error. I am currently developing an app that will run in both IOS and android, but sms functionality is only being used on android. hope this can be merged

hi.. thanks for the response, this PR is not intended to make user message accessible, this PR is intended for the package to be able to compile on IOS device, currently if you try to run flutter app in IOS simulator when this package is installed, it does not run and throw fatal error: 'flutter_sms-Swift.h' file not found error. I am currently developing an app that will run in both IOS and android, but sms functionality is only being used on android. hope this can be merged

Got it. My bad.
I'll take a look.
Thanks.

Got it. My bad.
I'll take a look.
Thanks.

I have published a new version with the fix.
telephony: ^0.0.7
Thanks for the PR @blacklizard

I have published a new version with the fix.
telephony: ^0.0.7
Thanks for the PR @blacklizard

Thanks @shounakmulay

Thanks @shounakmulay


where property

@rultor release, tag is 0.0.5

@rultor release, tag is 0.0.5

@yegor256 OK, I will release it now. Please check the progress here


@clr/angular Disabled form control centres the label in 5.2

Describe the bug
Setting a form input control to disabled in version 5.2.0 centres the label. This behaviour looks to come from this commit where the  change in styling is very broad in its scope.
https://github.com/vmware/clarity/commit/20bef1b591170752b0aea9b197731f014a6a83a3
How to reproduce
Behaviour in version 5.02
https://clarity-light-theme-v5-form-alignment.stackblitz.io

Behaviour in version 5.2.0
https://clarity-light-theme-v5-2-form-alignment.stackblitz.io

Expected behavior
Disabling a form control should not affect the alignment of the associated label.
Versions
Clarity project:

[ ] Clarity Core
[x] Clarity Angular/UI

Clarity version:

[ ] v3.x
[ ] v4.x
[x] v5.x

Framework:

[x] Angular
[ ] React
[ ] Vue
[ ] Other:

Framework version:
Angular 11

Also just ran into this annoying issue checking out v5.2, and not only the labels are centred, but the whole controls container, e.g. when select's disabled property changes to true, the whole clr-select-container gets centred.


new: Added color highlighting of quotes and special characters

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

Comparison is base (2515ba8) 94.59% compared to head (a2844a4) 94.80%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #19      +/-   ##
==========================================
+ Coverage   94.59%   94.80%   +0.20%
==========================================
  Files          22       22
  Lines        1647     1712      +65
==========================================
+ Hits         1558     1623      +65
  Misses         75       75
  Partials       14       14

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


Python 3.8 & Ubuntu20.04 support

I was installing the deb binary for Dragonfire, but it kept saying that I need python version less that 3.7. So, I tried the Debian package build instructions, but it errors out after a few seconds. I tried building it from source, but it  didn't create the dragonfire command (I ran it with python3 -m dragonfire), or install most of the required deps. I tried installing the deps manually, but realhud doesn't look like it can be built manually. I then gave up and tried sudo dpkg -i --force-all dragonfire_1.1.1_amd64.deb. This time it built everything, and formed the dragonfire command. Only problem is that when running dragonfire, it tells me it needs deeppavlov==0.7.1, which is incompatible with 3.8. Is there any way we can get it to run under python 3.8 ? Also, it doesn't look like it installs into a virtualenv during manual building, not sure if this is just me or it is supposed be like that.
EDIT my GPU doesn't support CUDA, but I'm hoping that it will work. Not sure if this has any relationship to the problems

Got it. The deeppavlov library seems to only run with CUDA. so this seems to be an error in the README instead of an error in the app, as it only says the CUDA Library is preferred

@Achyut-BK I'm having hard-time to support Ubuntu 20.04 because there are too many dependency issues. I've removed several dependencies and lost some features on 1.2.0 branch. Maybe you can figure out a way to upgrade while preserving the features.

@mertyildiran I can try my luck with it. IDK how well I can do though. I was actually also wondering, can we support more TTS engines, like mycroft does. Mimic2 seems Nice.

I dug around a bit more in the source code. I uninstalled the deb package and built the master branch from source. It still didn't compile the realhud library, so I tried manually compiling the realhud library, and got the following error
xxx@xxx-Lubuntu:~/Dragonfire/dragonfire/realhud$ gcc -shared -pthread -fPIC -fwrapv -O2 -fno-strict-aliasing -I/usr/include/python3.8 -o realhud realhud.c `pkg-config --libs gtk+-3.0` `pkg-config --cflags gtk+-3.0` -w
realhud.c: In function ‘screen_changed’:
realhud.c:173:5: error: unknown type name ‘GdkColormap’; did you mean ‘Colormap’?
  173 |     GdkColormap *colormap = gdk_screen_get_rgba_colormap(screen);
      |     ^~~~~~~~~~~
      |     Colormap
realhud.c: In function ‘expose’:
realhud.c:194:42: error: ‘GtkWidget’ {aka ‘struct _GtkWidget’} has no member named ‘window’
  194 |     cairo_t *cr = gdk_cairo_create(widget->window);
      |                                          ^~

So this seems to be the problem with the builiding of Realhud. I checked the source again, but the compile instructions given there didn't work. I fixed it with
`gcc -shared -pthread -fPIC -fwrapv -O2 -fno-strict-aliasing -I/usr/include/python3.8 -o realhud realhud.c `pkg-config --libs gtk+-2.0` `pkg-config --cflags gtk+-2.0` -w`

But dragonfire is unable to detect the so file. I renamed it realhud.so, copied it to the root Dragonfire directory.
After installing a couple more deps...
I ran into deeppavlov once again.
I tried installing it, and guess what
deeppavlov 0.12.1 requires pydantic==1.3, but you'll have pydantic 1.6.1 which is incompatible.
thinc 8.0.0a11 requires pydantic<2.0.0,>=1.4.0, but you'll have pydantic 1.3 which is incompatible.
bruh.
But at least I fixed that realhud problem I mentioned.
We could probobly fix this using venvs, but this is gonna be a tough fix.

Fixed thinc modulenotfound problem by downgrading it to 7.0.0.
We now suffer from
ImportError: cannot import name 'prefer_gpu' from 'thinc.api' (/home/xxx/.local/lib/python3.8/site-packages/thinc/api.py)

We seem to be in dependency hell. Thinc version 8.0.0a11 is required by spacy, but thinc version 7.0.0 is required for someother scripts.
On installing thinc 7.0.0
spacy 3.0.0.dev12 requires preshed<3.1.0,>=3.0.2, but you'll have preshed 2.0.1 which is incompatible.
spacy 3.0.0.dev12 requires srsly<3.0.0,>=2.1.0, but you'll have srsly 1.0.2 which is incompatible.
spacy 3.0.0.dev12 requires thinc==8.0.0a11, but you'll have thinc 7.0.0 which is incompatible.

with Thinc 8 :
ModuleNotFoundError: No module named 'thinc.v2v'
with Thinc 7:
ImportError: cannot import name 'prefer_gpu' from 'thinc.api' (/home/xxx/.local/lib/python3.8/site-packages/thinc/api.py)
I think this is fixable by downgrading spacy. I will figure out the precise versions later

Fixed the aforementioned problem
pip install spacy==2.3.2 installs spacy and Thinc in a way that is compatible. YAY.
After a couple problems with pyUserInput and missing spacy models, its FINALLY building te AI. So what I'll try doing is installing spacy on  a fresh version of Ubuntu Server, go through installing everythin, and then post python3 -m pip list and the installed packages here.

@Achyut-BK I'm sorry for my late reply.
pip3 install -e . should compile the realhud Python C extension without any problem. We should replace realhud with an Electron based or low-level WebKit API based solution in the future. Replacing it with something else is out of scope of this issue. This commit proves that realhud has no compilation issues on Ubuntu 20.04
I hit that thinc and spacy dependency issue in the past and I thought I've fixed it somewhere though I couldn't find the commit.
It's great that you've overcome all the dependency issues. I'm looking forward to receive your pull request. Remember that it should pass the GitHub workflow in here. Feel free to modify and/or remove the problematic tests located in here.

@mertyildiran That sounds great. However, it seems to have a problem with tensorflow 2 (AttributeError: module 'tensorflow' has no attribute 'orthogonal_initializer' ). Tensorflow 1 may work, but there are no precompiled wheels for TF 1 for python3.8. I don't have the processing power to build the wheels myself. Could yOu help?

@Achyut-BK yeah they drop support for TensorFlow 1.x as of Python 3.8. Therefore we should instead migrate to TensorFlow 2 and replace or remove the models broken in TensorFlow 2.
An alternative approach would be making this project rely on pyenv instead of system packages and use an older Python version like 3.6 or 3.7. But I'm not sure how we can do that. Like; it should install pyenv if it does not exists on the system then it should pyenv install 3.6.10 and then define an environment pyenv virtualenv 3.6.10 dragonfire-env-3.6.10 and finally activate it and use it pyenv activate dragonfire-env-3.6.10. But again I'm not sure how can we achieve this automatically.

@mertyildiran That would actually be good, as currently, when it is using my systems pip, its basically locked all my ML libraries at one version. Not much of a problem for me, but I'm pretty sure this can get annoying if you use these frameworks regularly. Also, if we succeed with pyenv, we could probably try for packaging it as a snap or appimage for anyone who doesn't want to get down and dirty with the source code. Also, we could maybe update the code itself too. I don't now Coding AI, but I can help out with pyenv.

@Achyut-BK it's good to hear that you can help. Distributing with snap, flatpak and appimage is also in the plan. I don't have enough time to focus on this repository right now. If you can fix these dependency issues, I would be so grateful. I'm ready to answer all kinds of questions of yours and help to you using this discussion chain.

In my case, I solved it using Venv. First, compiled Python 3.6 from source. Then created a Virtualenv based on Python 3.6 and installed everything inside Venv. Voila! Not a tecchy guy, i bet you know how to explain it better, but if needed details (despite my english hahaha) count on it.


Crash with System.ArgumentNullException while scanning artifacts

An unhandled exception of type 'System.ArgumentNullException' occurred in mscorlib.dll
Value cannot be null.
System.ArgumentNullException: 'Value cannot be null.
Parameter name: key'

Hi there, this issue is hopefully resolved in the v1.1.1 prerelease. If it has been, please let us know so we can close this issue.


react-tween-state not work in react native?

I am tyring to use react-tween-state  in react native, but when I add var React = require('react-native'); it can't work. You can check this example https://rnplay.org/apps/4FUQ-A .The office example is not work too. Thx

It works for me here?

With react-native v0.7.x it complains that react-tween-state as unknown module.

Really? Can you provide the full error please?

Tried on RN and it works, I'll close this unless there's a clear repro. Thanks!


Unable to validate trust when using entire URL

In version 4.0.0, when the certificate trust is validated with the entire URL, it fails with the following reason:
Error Domain=NSOSStatusErrorDomain Code=-67602 "“*.<redacted>.io” certificate name does not match input" UserInfo={NSLocalizedDescription=“*.<redacted>.io” certificate name does not match input, NSUnderlyingError=0x600002698f60 {Error Domain=NSOSStatusErrorDomain Code=-67602 "Certificate 0 “*.sensiapi.io” has errors: SSL hostname does not match name(s) in certificate;" UserInfo={NSLocalizedDescription=Certificate 0 “*.<redacted>.io” has errors: SSL hostname does not match name(s) in certificate;}}}

However, validation with just the host is successful.
Could this be related to having connect params appended to the URL, for example, when appended by https://github.com/socketio/socket.io-client-swift
Fix in https://github.com/daltoniam/Starscream/pull/721

+1
This fixes for me also the following issue:
[BoringSSL] boringssl_context_handle_fatal_alert(1872) [C71.1:1][0x7f9456801f00] write alert, level: fatal, description: certificate unknown
[BoringSSL] boringssl_context_error_print(1862) boringssl ctx 0x60000087c4e0:<PHONE_NUMBER>77352:error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl_Sim/boringssl-283.60.3/ssl/handshake.cc:369:
[BoringSSL] boringssl_session_handshake_error_print(111) [C71.1:1][0x7f9456801f00]<PHONE_NUMBER>77352:error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl_Sim/boringssl-283.60.3/ssl/handshake.cc:369:
[BoringSSL] nw_protocol_boringssl_handshake_negotiate_proceed(726) [C71.1:1][0x7f9456801f00] handshake failed at state 12288

Hey guys, i'm getting accept header doesn't match errors now. Before i start doing a deep dive into this RFC, any clues why after upgrading i'm getting this validation failure? Perhaps it was a long standing configuration issue that is just exposed now?  I'm not even sure which layer to debug, would this nginx/lb configuration error?
I'm going to start investigating now, but if you have any hints let me know.
public func validate(headers: [String: String], key: String) -> Error? {
        if let acceptKey = headers[HTTPWSHeader.acceptName] {
            let sha = "\(key)258EAFA5-E914-47DA-95CA-C5AB0DC85B11".sha1Base64()
            if sha != acceptKey {
                return WSError(type: .securityError, message: "accept header doesn't match", code: SecurityErrorCode.acceptFailed.rawValue)
            }
        }
        return nil
}

Oh wow, figured it out. Looks like socket.connect() was being called twice (user error), creating a race condition causing key mismatch on the instance.

I have two AWS tokens that I'm trying to pass to our server when connecting, but I keep getting errors;

2020-01-09 14:23:07.730431+0000 teckro[50896:1386042] [BoringSSL] boringssl_context_handle_fatal_alert(1872) [C2.1:1][0x7fe07743ef00] write alert, level: fatal, description: certificate unknown
2020-01-09 14:23:07.730807+0000 teckro[50896:1386042] [BoringSSL] boringssl_context_error_print(1862) boringssl ctx 0x6000024d59d0:<PHONE_NUMBER>98248:error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl_Sim/boringssl-283.60.3/ssl/handshake.cc:369:
2020-01-09 14:23:07.733026+0000 teckro[50896:1386042] [BoringSSL] boringssl_session_handshake_error_print(111) [C2.1:1][0x7fe07743ef00]<PHONE_NUMBER>98248:error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl_Sim/boringssl-283.60.3/ssl/handshake.cc:369:
2020-01-09 14:23:07.733228+0000 teckro[50896:1386042] [BoringSSL] nw_protocol_boringssl_handshake_negotiate_proceed(726) [C2.1:1][0x7fe07743ef00] handshake failed at state 12288
websocket encountered an error: The operation couldn’t be completed. (Network.NWError error 2.)

  func connectSocket() {     var request = URLRequest(url: URL(string: webSocketURL)!)     request.addValue(NetworkManager.shared.accessToken, forHTTPHeaderField: "AccessToken")     request.addValue(NetworkManager.shared.idToken, forHTTPHeaderField: "IdToken")     socket = WebSocket(request: request)     socket?.delegate = self     socket?.connect()   }
The two tokens are from AWS Cognito, and do work fine when using them with HTTPS calls etc.
What am I missing?
Thanks
Jörgen
Xcode 11.3 on Catalina
Build target 12.4

@JorgenTeckro Did this error happen when using the fork mentioned in #721 ?

@patmalt I am just using Starscream via SPD from github.com/daltoniam/Starscream.git (currently 4.0.0 no branch specified).

@JorgenTeckro this issue is about a fix for that issue (including a pull request with the fix). Please try again with the mentioned fork (as the pull request is not merged yet).

@JorgenTeckro this issue is about a fix for that issue (including a pull request with the fix). Please try again with the mentioned fork (as the pull request is not merged yet).

@tfonfara How is that done with SPM? I have only just started using it.

@JorgenTeckro I'm not a SPM pro, but instead of this repo url use the one of the fork (https://github.com/emersonsoftware/Starscream) and instead of a version number I guess you could use .revision to specify the git commit

@JorgenTeckro I'm not a SPM pro, but instead of this repo url use the one of the fork (https://github.com/emersonsoftware/Starscream) and instead of a version number I guess you could use .revision to specify the git commit

@tfonfara Thanks. That solved it. I'm now connecting happily. There is a field in SPM where you can set the commit. Hopefully they will merge it in soon.

@tfonfara Hey, probably not the right place, but I have another question.
When my server timeout the socket connection, I don't seem to get any notification. There is no WebSocketEvent. It's the same with my own socket.

@JorgenTeckro Please open a different issue for what you are experiencing

Fixed in #721


feat: fork deprecated serde yaml and add more string quoting when serialize

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

re https://github.com/crossplane-contrib/function-kcl/issues/78
re https://github.com/crossplane-contrib/provider-upjet-aws/issues/1261

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[x] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

3613 of 6861 (52.66%)  changed or added relevant lines in 23 files are covered.
7 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-1.9%) to 71.401%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

kclvm/third-party/serde_yaml/src/path.rs
17
20
85.0%

kclvm/third-party/serde_yaml/src/loader.rs
71
75
94.67%

kclvm/third-party/serde_yaml/src/libyaml/tag.rs
6
13
46.15%

kclvm/third-party/serde_yaml/src/value/debug.rs
22
33
66.67%

kclvm/third-party/serde_yaml/src/value/partial_eq.rs
0
26
0.0%

kclvm/third-party/serde_yaml/src/value/from.rs
0
29
0.0%

kclvm/third-party/serde_yaml/src/libyaml/emitter.rs
101
135
74.81%

kclvm/third-party/serde_yaml/src/libyaml/parser.rs
81
116
69.83%

kclvm/third-party/serde_yaml/src/libyaml/cstr.rs
30
81
37.04%

kclvm/third-party/serde_yaml/src/libyaml/error.rs
46
111
41.44%

Files with Coverage Reduction
New Missed Lines
%

kclvm/tools/src/LSP/src/request.rs
1
72.02%

kclvm/ast/src/token.rs
1
58.9%

kclvm/ast/src/ast.rs
1
83.55%

kclvm/tools/src/LSP/src/state.rs
1
86.15%

kclvm/sema/src/core/symbol.rs
3
46.54%

Totals

Change from base Build<PHONE_NUMBER>:
-1.9%

Covered Lines:
52618

Relevant Lines:
73694

💛  - Coveralls


Update data_synthesis.py

Closes #353
Please check it @VictorOdede @abhigya-sodani

I am a little confused how this will fix the issue?
the error: TypeError: BaseOnsiteLLM.generate() got an unexpected keyword argument 'temperature', seems like a parameter issue in our BaseOnsiteLLM class in onesite_llm.py.
What was your diagnosis of the root of this problem, maybe that will help me understand better

@abhigya-sodani
I provided code modifications that assumed the temperature argument should be accepted by the generate method. I overlooked the fact that the generate method of the BaseOnsiteLLM class in onesite_llm.py doesn't accept a temperature argument. To resolve that we can modify the generate method in the BaseOnsiteLLM class to accept the temperature argument, something like this:
def generate(self, prompt, max_len, temperature=1.0, **kwargs):
This can, I believe ensure that the generate method can accept the temperature argument when called.

This issue was closed by #366


Make all the external links open in new tab by default

I am raising this issue because many of the links which refers to the external websites gets opened in the same tab upon the Foundry book website  which creates a problem especially when learning something from a tutorial or coding along with a tutorial.
For example,
We can see in the Dockerizing a Foundry project tutorial under the Installation and setup on the fourth paragraph where the link of Ethereum's article is present. If it opens in a  new tab it would be more easier for me to read the whole tutorial as I wouldn't have to switch back and forth between pages.

there must be a mdbook setting for this, but I'm not sure

Believe the only way to accomplish this is with HTML. Open to doing this but would be convenient if there was a way to enforce it.
eg.
[Awesome Foundry](https://github.com/crisgarner/awesome-foundry)

to
Awesome Foundry

the issue is fixed now, thanks for implementing it @onbjerg


Widget replacement for showing marker on map.

Markers on the map were not showing because of a geo position type mismatch . Solved the issue by replacing the form.osmwwidget widget with Django Map Widgets(https://github.com/erdem/django-map-widgets) .

Does this impact the existing entries in the map?

because of a geo position type mismatch

can you be more specific or does it remain a mystery then? :)
Gotta say that I'm not a fan of Google, that's why I went with OSM -- so using GooglePointFieldWidget from the third-party magically works, that's great. But is there a way to get this to work with out-of-the-box Django fields?

I was wondering that too? Can we migrate the data instead of deleting?

On 21 Mar 2018, at 11.47, Benjamin Bach<EMAIL_ADDRESS>wrote:
Does this impact the existing entries in the map?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

yes we can scrap all migrations.
Osm was taking the input in epsg format(there are apparently multiple versions of it), but leaflet js expects the value in lat long format to show them 9n the page.  I tried to keep the osm and just convert the epsg values to latlong using 'pyproj' library, but the results were not same as user input. Because , we need to figure out which version of epsg is actually being used.

Because , we need to figure out which version of epsg is actually being used.

could brute force that? :)
weird_point = models.MapEntry.objects.all()[0].location
while format in formats:
    if pyproj.convert(weird_point, format).y >= 56 and pyproj.convert(weird_point).y < 57:
        print("This is the format")

(it's pseudo code!)

Testing whether it's between 56-57 is because that's where the Danish coords are... but not sure if x or y because of the weird geographical practices :)

Sorry I did not fully understand what you mean by brute forcing the format.
Now, upon further digging on EPSG, as it turns out every coordinate system is referred by a epsg number, fx our familiar latlong system is called epsg 4326.
There are hundreds of them :[http://spatialreference.org/ref/epsg/].
Closest educated guess i can make is the long format we are getting on the website are in epsg 3857 format. So i tried to transform my location from the website into lat long using pyproj library.
Here is the result:
>>> from pyproj import Proj,transform
>>> inp=Proj(init='epsg:3857')
>>> outp=Proj(init='epsg:4326')
>>> lat,lon=transform(inp,outp,7526468.117538152,1508590.9204641692)
>>> print(lat,lon)
67.61141345422804 13.42728338986224

Live code: https://repl.it/repls/GleamingLovelyDatum
the resulting lat long putes me somewhere in norwegian sea!!!
So actually the challenge in converting the existing data is to figure out what the actual epsg is.

@rmahmood19 using brute force means to test all the combinations... with a minimum of real research. Just get cracking :D
>>> from map.models import MapEntry
>>> p = MapEntry.objects.all()[0].location
>>> from pyproj import Proj,transform
>>> out=Proj(init='epsg:4326')
>>> for i in range(2000,7423):
...     try:
...         inp = Proj(init="epsg:{}".format(i))
...         lat, lon = transform(inp, out, 7526468.117538152, 1508590.9204641692)
...         if lat >=56 and lat < 57:
...             print(i)
...     except RuntimeError:
...         pass
...
2394
3004
3043
3266
3411
3413
5123
5554
5922
5963
5971
6163
6171
>>> inp = Proj(init="epsg:2394".format(i))
>>> lat, lon = transform(inp, out, 7526468.117538152, 1508590.9204641692)
>>> lat
56.863689015278695
>>> lon
12.205427181887048


Imageprocessinglabs

When you added a new program / programs , put a cross on the  OS that you have test it on
(Example: [ X ] Windows  )
[ X ] Windows
[  ] Linux Ubuntu
[  ] Mac
[  ] Others  (State here -> xxx )
Assign a reviewer to review your code.

Reopen after pulling latest changes from Master


Generate CLI reference doc programmatically

What is the issue?
Currently the CLI reference doc https://docs.dagger.io/cli/979595/reference is managed/edited manually. This is hard to maintain and keep in sync. It would be nice to have this generated automatically from the source code itself. Thanks to @helderco for this suggestion!

Done in https://github.com/dagger/dagger/pull/6592


Project Form: Job title and Employer fields DB & API work

Related to #99 #119
FEEL FREE TO BREAK THIS TASK DOWN TO SEVERAL PULL REQUEST.
Deliverables
Backend support work for all the scenarios where Job Title and Employer is used in the frontend.
Instructions:

Create position table - fields id, position
Create getPositions API - returns all positions that match any given string. Ex: given string A - return all positions starting from A.
Create addPosition API - a new entry in the position table for when a user adds a new position.
Update /projects/all and projects/all/public APIs to use the position (Job Title) and company (Employer) fields as needed for the frontend.

If you have any questions as @nurmerey for help!

Hi, was assigned this issue. Thank you!


Refactor permission check for canned query

This code here (TODO is follow-on from #808).
https://github.com/simonw/datasette/blob/86dec9e8fffd6c4efec928ae9b5713748dec7e74/datasette/views/database.py#L133-L142
I can improve this with extra code in https://github.com/simonw/datasette/blob/86dec9e8fffd6c4efec928ae9b5713748dec7e74/datasette/default_permissions.py

This is obsoleted by #811.


[Bug] Library UI not themed and not displaying correctly on fedora 37

After todays steam update, the library UI of the launcher is no longer themed and is having issues displaying correctly. I will provide screenshots and system info below

System information:

Intel core i7 6100U
Intel integrated graphics 520
8gb of ram
Fedora 37
Gnome 43.3

Duplicate of #113.
Nothing we can do now if Steam does not inject styles from webkit.css into web UI anymore.
This change was probably intentional to make the behavior more consistent on different platforms, because Windows builds of Steam never allowed to inject styles into the web UI at all.
Maybe something like SFP could work.
Or maybe Valve could add a supported way to override CSS for skins if they still want to support them, but thats very unlikely, considering that they seem to be slowly moving away from VGUI and the web UI is still not skinnable.
The most likely outcome I see is Steam eventually dropping the skin support entirely when they finish the transition from VGUI.

Display issues on your screenshot are likely a Steam bug. Is the window itself scrollable?
The library on your screenshot seems to be cut off at the top, so it may actually be scrolled inside the window.
The latest beta had a few similar bugs, some of them seem to be fixed, but maybe not all of them.


Improve frontend

Add launch.json (contains run configurations so vscode users can run the project instantly without having to configure something)
Make footer collapsable (the footer takes a lot of space so I added a collapse button; the collapsed state will be saved and kept on reload)

Make autocomplete items scrollable

Submit form automatically when pressing enter
Add data folder to .gitignore
Fetch cities from a static file & load them async (speeds up page loading time for users with slow internet & makes main.html easier to edit as it no longer has 10000 lines)
Fix gradient on /more page

Previously:

Now:

Fix indentation of main.html (makes it easier to edit the code)
Add a light shadow to the footer
Add margin on right & left of the horizontal rule on top of the page

Hello SehrGuterCode!
Thank you for your changes to our website.
I don't know how to thank you! You've done a lot of work for me. I wanted to ask if you would like to work with wann-soll-ich-lüften.de. So make updates with me and come up with new things to add. If you want it would be nice if you send me your discord name if you have discord. Then I can write to you about it.
Thank you!
Louis Schuimer
Velbert, May 16th

Hey! My Discord name is DrDoubleNo76#9442 if you want you can add me. But I am not online anymore at this time.
Thank you


Drag and Drop REST Requests in colleciton  not working

Using the Hoppschotch executable, the drag and drop  of requests in collecction folders doesn't work, why?

Hi, could you provide more details about this problem using pictures or videos? This project is just a thin wrapper of hoppscotch-selfhost-web using tauri. Maybe some features like server proxy, cloud storage, account login are missing normally.


@ApiParam not working in interface

I have added @ApiParam annotation in interface method, but it is not working. Please let me know, if it is fixed in v2.8.0.
Below is code sample:
@ApiOperation(value = "Find") ResponseDto find(@ApiParam(value = "Filter Criteria", required = true) String filterCriteria,      HttpServletResponse response);
I am using springfox v2.8.0

@piyushj90 It is not fixed #1575

Could you try to add more @RequestParam annotation, like as @ApiOperation(value = "Find") ResponseDto find(@ApiParam(value = "Filter Criteria", required = true) @RequestParam() String filterCriteria, HttpServletResponse response);?
It works for me.

so which version solves this bug?

the issue is still reproducible for springfox-swagger2:2.9.2

It isnt fixed yet please track #1575

Closing as duplicate of #1575


Enable / Disable Stepper Motors

Hallo,
ist there a way to enable and disable stepper motors using this library?
Kind regards
AR

I don't think so, but you can try and implement it. It shouldn't be that hard. I suggest you start with learning about object oriented programming in C++.
I haven't made any significant changes to this library in 4 years, as it was only part of my final project in highschool.

thx, i think i'll do that.


Fix broken link.

https://ampersandjs.com/docs/#ampersand-model-isnew
to
https://ampersandjs.com/docs/#ampersand-state-isnew

Ah yep, thanks.  Link won't work on the github readme still cause of the way things are built to make the site itself.