Journal Entries?

This module is really interesting! Is there a way to port journal entries to discord in even a basic way (perhaps the text of a journal entry and the related image)?
Outside of copy/paste of the journal entry contents into discord manually, a way to export would be amazing. A possible use case is for a module like Forien's Quest Log, which would allow a GM to port the quest contents into a thread or threads.
Not sure how feasible, but thought I would ask.
Thanks!

Have you tried Quick Send to Chat? It can send a journal entry to chat. I don't know how good it will look, but it's a solution. Let me know if it's sufficient to be used with Foundry to Discord. Having a dedicated button to send it to Discord could still be viable, yet a bit labor-intensive, though.

Actually, I've just now found out that it sends the journal entry as a whisper... That's not great. I'll look into this FR and see how viable it is.

Alright. This looks easy to implement, with a small restriction, of course, since we're talking about converting a Journal page to a Discord message:
"Text" type journals will not include images embedded into the html of the text content
For this, I'll add a button to send image popouts directly to discord, like this:

Awesome! I will play around with it!


Export additional layer styles

Drop Shadow
Inner Shadow
Outer Glow
Inner Glow

Based on http://docs.aenhancers.com/matchnames/layer/layerstyles/ .

I found that testing styleElement.isModified is finicky (true if the style was ever touched, regardless of the current state).  Replacing with styleElement.enabled seems to do the trick.


Want a free MySQL database?

 Size Limit IDK, don't use<PHONE_NUMBER>999999999999999999999999999999999999999 YottaBytes Tho Ps - If u want password change, nah

good thing this isnt logged to the public gh logs otherwise you would be COOLED rn :trollface:

dam girhub has edit history


Rachel changes 0628

Changes to fix some css issues, modifications to errors that were resulting in browser alert boxes, minor js changes

Please do not merge line 11.  Video


bug: write_source_files diff_test fails on same-named directory

Bug report in the form of a failing test.
If you use write_source_files to copy a directory in the output tree to a directory in the source tree with the same name, the generated diff_test always fails. The error is "diff_test comparing the same file".
$ bazel test //lib/tests/write_source_files:e_dir-desired_test_test
ERROR: /Users/john/figma/bazel-lib/lib/tests/write_source_files/BUILD.bazel:225:19: in _diff_test rule //lib/tests/write_source_files:e_dir-desired_test_test:
Traceback (most recent call last):
	File "/Users/john/figma/bazel-lib/lib/private/diff_test.bzl", line 56, column 13, in _diff_test_impl
		fail(msg)
Error in fail: diff_test comparing the same file <generated file lib/tests/write_source_files/e_dir-desired>
ERROR: /Users/john/figma/bazel-lib/lib/tests/write_source_files/BUILD.bazel:225:19: Analysis of target '//lib/tests/write_source_files:e_dir-desired_test_test' failed

No way around this one unfortunately since if there are files of the same name in the source tree and the output tree then the label to that file will always refer to the output tree so there is no way to make a diff_test comparing them


Docker-Compose run target example missing

readme contains docker container pytest command. but does not specify how to consume a singer-tap using container.
~/.virtualenvs/tap-something/bin/tap-something | [docker-container???] >> state.json

@AlexanderMann I want to fetch information from third party API server and store into postgres db  incrementally.

Gotchya. If you already have a tap setup, I would recommend installing Target Postgres via the the same virtualenvs process for setting up a tap.
Out of curiosity, how were you hoping that Docker-Compose (not just Docker) would fit into your workflow?

docker v/s virtualenvs. 'docker' for portability and avoid OS enforced package versions.
docker compose v/s docker. I can accomplish it using docker` but then I'll have to do the volume mapping (for postgres data) on command line which is a extra step to remember for transition team.

I pulled and modified this repo to build my workflow. But I get a lot of errors when execute docker-compose up (see modified files  below)
:x: ERRORS

etl_1       | Traceback (most recent call last):
etl_1       |   File "/.virtualenvs/target-postgres/bin/target-postgres", line 10, in
etl_1       |     sys.exit(cli())
etl_1       |   File "/.virtualenvs/target-postgres/lib/python3.7/site-packages/target_postgres/init.py", line 45, in cli
etl_1       |     main(args.config)
etl_1       |   File "/.virtualenvs/target-postgres/lib/python3.7/site-packages/target_postgres/init.py", line 24, in main
etl_1       |     sslcrl=config.get('postgres_sslcrl')
etl_1       |   File "/.virtualenvs/target-postgres/lib/python3.7/site-packages/psycopg2/init.py", line 126, in connect
etl_1       |     conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
etl_1       | psycopg2.OperationalError: could not connect to server: Connection refused
etl_1       | 	Is the server running on host "postgres" (<IP_ADDRESS>) and accepting
etl_1       | 	TCP/IP connections on port 5432?
etl_1       |
etl_1       | INFO BigCommerce API Authorized.
etl_1       | CRITICAL [Errno 32] Broken pipe
etl_1       | Traceback (most recent call last):
etl_1       |   File "/.virtualenvs/tap-bigcommerce/bin/tap-bigcommerce", line 11, in
etl_1       |     load_entry_point('tap-bigcommerce==1.0.1', 'console_scripts', 'tap-bigcommerce')()
etl_1       |   File "/.virtualenvs/tap-bigcommerce/lib/python3.7/site-packages/singer/utils.py", line 225, in wrapped
etl_1       |     return fnc(*args, **kwargs)
etl_1       |   File "/.virtualenvs/tap-bigcommerce/lib/python3.7/site-packages/tap_bigcommerce/init.py", line 125, in main
etl_1       |     start_date=config['start_date']
etl_1       |   File "/.virtualenvs/tap-bigcommerce/lib/python3.7/site-packages/tap_bigcommerce/init.py", line 70, in do_sync
etl_1       |     metadata.get(mdata, (), 'table-key-properties')
etl_1       |   File "/.virtualenvs/tap-bigcommerce/lib/python3.7/site-packages/singer/messages.py", line 260, in write_schema
etl_1       |     bookmark_properties=bookmark_properties))
etl_1       |   File "/.virtualenvs/tap-bigcommerce/lib/python3.7/site-packages/singer/messages.py", line 218, in write_message
etl_1       |     sys.stdout.flush()
etl_1       | BrokenPipeError: [Errno 32] Broken pipe
Files
Dockerfile
FROM python:3.7-slim

RUN apt-get update
RUN apt-get install -y --no-install-recommends build-essential gcc python-dev libpq-dev

RUN python -m venv /.virtualenvs/tap-bigcommerce && /.virtualenvs/tap-bigcommerce/bin/pip install tap-bigcommerce==1.0.1
RUN python -m venv /.virtualenvs/target-postgres && /.virtualenvs/target-postgres/bin/pip install singer-target-postgres==0.2.2

COPY ./singer.io /singer.io

WORKDIR /singer.io

CMD ["sh", "./sync.sh"]

docker-compose.yml
version: "3"

services:
  etl:
    restart: on-failure
    build:
      context: .
    volumes:
      - ./singer.io:/singer.io
    depends_on:
      - postgres

  postgres:
    image: postgres:9.6.15
    environment:
      POSTGRES_USER: pguser
      POSTGRES_PASSWORD: pgpass
      POSTGRES_DB: sample
    volumes:
      - ./postgres-data:/var/lib/postgresql/data

  pgadmin:
    image: dpage/pgadmin4
    restart: always
    depends_on:
      - postgres
    ports:
      - 5050:80
    ## you can change pgAdmin default username/password with below environment variables
    environment:
      PGADMIN_DEFAULT_EMAIL<EMAIL_ADDRESS>      PGADMIN_DEFAULT_PASSWORD: admin

singer.io\sync.sh
#!/bin/sh

tap=/.virtualenvs/tap-bigcommerce/bin/tap-bigcommerce
target=/.virtualenvs/target-postgres/bin/target-postgres

tap_config=/singer.io/bigcommerce_config.json
tap_catalog=/singer.io/bigcommerce_catalog.out.json

target_config=/singer.io/postgres_config.json

$tap -c $tap_config --catalog $tap_catalog | $target -c $target_config

singer.io\postgres_config.json
{
  "postgres_host": "postgres",
  "postgres_port": 5432,
  "postgres_database": "sample",
  "postgres_username": "pguser",
  "postgres_password": "pgpass"
}

@hashg As @AlexanderMann said, the docker-compose file here is intended for the development and testing workflow of target-postgres not it's application. target-postgres is a Singer target, so the workflow laid out in the docs can be applied.


Error: expected timestamp at row X

Hi,
When I run subclean I experience the following error.
Any hints how to solve this?
c:\ProgramData\subclean>subclean.exe subtitle.srt -o subtitle.test.srt
D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:286
      throw this.getError('timestamp', this.state.row, line);
      ^

"rror: expected timestamp at row 2, but received: "00:00:40,908 --> 00:00:45,908
    at Parser.getError (D:\snapshot\subclean\node_modules\←[4msubtitle←[24m\dist\subtitle.cjs.development.js:222:12)
    at Parser.parseTimestamp (D:\snapshot\subclean\node_modules\←[4msubtitle←[24m\dist\subtitle.cjs.development.js:286:18)
    at Parser.parseLine (D:\snapshot\subclean\node_modules\←[4msubtitle←[24m\dist\subtitle.cjs.development.js:242:11)
    at D:\snapshot\subclean\node_modules\←[4msubtitle←[24m\dist\subtitle.cjs.development.js:91:19
    at Array.forEach (<anonymous>)
    at Object.parseSync (D:\snapshot\subclean\node_modules\←[4msubtitle←[24m\dist\subtitle.cjs.development.js:90:44)
    at Subclean.clean (D:\snapshot\subclean\lib\index.js:184:32)
    at Subclean.init (D:\snapshot\subclean\lib\index.js:39:14)
    at Object.<anonymous> (D:\snapshot\subclean\lib\index.js:235:16)
    at Module._compile (pkg/prelude/bootstrap.js:1433:22)

subtitle.zip
I've attached the srt, in a zip file. GitHub doesn't allow srt files.
Thanks for the ultra fast response.

Thank you for the sample.
The issue was the file you sent contained a bizarre number of \r that broke the parser.
This is fixed in 1.2.7, all cases of \r will be stripped before parsing
https://github.com/DrKain/subclean/releases/tag/v1.2.7

I unleashed your script on my library after the fix and all the movies went fine (around 1500) but I caught another timestamp error on a TV show subtitle. I've attached the srt.
Awesome program/script btw! Love it.
D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:286
      throw this.getError('timestamp', this.state.row, line);
      ^

Error: expected timestamp at row 1, but received: "��1 "
    at Parser.getError (D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:222:12)
    at Parser.parseTimestamp (D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:286:18)
    at Parser.parseId (D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:280:12)
    at Parser.parseHeader (D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:259:14)
    at Parser.parseLine (D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:242:11)
    at D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:91:19
    at Array.forEach (<anonymous>)
    at Object.parseSync (D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:90:44)
    at Subclean.clean (D:\snapshot\subclean\lib\index.js:188:32)
    at Subclean.init (D:\snapshot\subclean\lib\index.js:39:14)
(node:5180) UnhandledPromiseRejectionWarning: Error: Command failed: subclean "S:\tvshow\Season x\subtitle.srt" -w
D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:286
      throw this.getError('timestamp', this.state.row, line);
      ^

Error: expected timestamp at row 1, but received: "��1 "
    at Parser.getError (D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:222:12)
    at Parser.parseTimestamp (D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:286:18)
    at Parser.parseId (D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:280:12)
    at Parser.parseHeader (D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:259:14)
    at Parser.parseLine (D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:242:11)
    at D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:91:19
    at Array.forEach (<anonymous>)
    at Object.parseSync (D:\snapshot\subclean\node_modules\subtitle\dist\subtitle.cjs.development.js:90:44)
    at Subclean.clean (D:\snapshot\subclean\lib\index.js:188:32)
    at Subclean.init (D:\snapshot\subclean\lib\index.js:39:14)

    at checkExecSyncError (child_process.js:790:11)
    at execSync (child_process.js:863:15)
    at c:\ProgramData\subclean\subclean.js:23:21
(Use `node --trace-warnings ...` to show where the warning was created)
(node:5180) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (re
[subtitle.zip](https://github.com/DrKain/subclean/files/7388251/subtitle.zip)
jection id: 1)
(node:5180) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

As a final note, you can convert the files manually using Notepad++ if you desire.
Simple open the file and click 'Encoding > Convert to UTF-8", then save.
Subclean should work with the converted file.


[CSM-387] Set syncTip up to date in newWallet

We should wait for https://github.com/input-output-hk/cardano-sl/pull/1226 to be merged into cardano-sl-0.5 first, then merge -s cardano-sl-0.5 here, and then merge it into master, to preserve correct commit history.

Good!


feat: Form design changes

JIRA Ticket: https://jira.splunk.com/browse/ADDON-34131

:tada: This PR is included in version 5.0.0-develop.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Document how bytecode instrumentation and upgrades work

Issue type
Missing information
Problem description
We should document how Gradle does bytecode instrumentation. This is currently used both for detecting problems that would prevent configuration cache from working properly, as well as upgrading the bytecode of plugins built against an older, incompatible version of Gradle.
Context (optional)
No response
Page with the problem
This should be documented internally

A spec
https://docs.google.com/document/d/1g2ouFsYV57_UaWcK-W0hAaXPUX-YbM1NXvthTP2CDQc/edit#heading=h.610fausqnpu6


Dev to Main sync

Date: 10th Feb 2024
Developer Name: @VinayakaHegade
PR Number(s):

#143

Issue Ticket Number:

#140

Frontend Changes

[x] Yes
[ ] No

Database changes

[ ] Yes
[x] No

Breaking changes (If your feature is breaking/missing something please mention pending tickets)

[ ] Yes
[x] No

Tested in staging

[x] Yes
[ ] No

Staging Proof
https://github.com/Real-Dev-Squad/members-site/assets/88454618/69bd8702-0fbf-4669-a782-96808061d199

In case there is no content on the page, this is where the footer is displayed. Have you handled this? Generally, this should be at the end of the page. Please correct me if I'm wrong.

Same in case of mobile.


The Extension Website

@fordnox is the extensions website going to be a thing still or should we remove all references to it from boxbilling until something similar does exist?

@fordnox if you need hosting arrangements for your domain and someone to take over the website. I am a hosting provider and would welcome the opportunity to maintain not only the codebase but the website as well. Let me know your thoughts.

I'm of the opinion that there should be an extensions website for free extensions.
It's an important part of building a user ecosystem for people to be able to find extensions/modules/themes/whatever in one place.
It's part of a bigger issue with website, clarity, documentation, etc. that I think are probably driving away many people at the moment.
If there is not to be an extensions website then any visible references to it should definitely be removed though.

Extensions should be installable via composer. Then this is done, extensions site can be easily created.


WIP adjust codeclimate thresholds

I can't get codeclimate to work locally so I'll adjust the thresholds this way instead

Accidentally manually approved codeclimate and it won't make checks anymore. Have to create a new WIP PR


"Cannot register" warning message

Describe the bug
A warning message pops up, claiming an apparent duplicate registration of the maxLinesToProcess config
To Reproduce
Steps to reproduce the behavior:

Open Development Host for the extension
The warning message Cannot register 'vortex.maxLinesToProcess'. This property is already registered. pops up

Issue was happening only inside of the development host, for some reason it seemed to be attempting to activate the extension twice. After manually uninstalling the extension inside the dev host and reloading the window, everything was fine.
Will reopen if this issue resurfaces sometime in the future.


schutzbot/run_cloud_cleaner: pass BRANCH_NAME instead of CHANGE_ID

CHANGE_ID bug strikes for the 3rd time :-/. Hope this is the last one. Recursive grep does not show any other usage:
$ rg CHANGE_ID
$

#1032 strikes again


Gate usb Suspend/Resume feature with a feature: usb-suspend

Because this is broken in the current version of usb-device, we need to gate this until the upstream fix is published in a version.
Note:
I didn't get to test it yet. It'd be greatly appreciated if reviewer could build one of the example and confirm that it is broken without the gate (you'll need to make the usb host suspend the link, typically by putting a laptop host into sleep/suspend).

confirm that it is broken without the gate

How do we confirm that it is broken, would you expect it to not enumerate on resume?
I've tested it this way (with and without the feature) and it seems fine.
I also tested it with XHCI HSETT, running get descriptor, suspend, get descriptor, resume, get descriptor.
Responds identically in both cases - before suspend descriptor fine, after suspend error, after resume fine.

I was unable to see any difference in behavior between usb-device 0.2.8 and the current git version of usb-device.
Monitoring [fn state(&self) -> UsbDeviceState](https://docs.rs/usb-device/latest/usb_device/device/struct.UsbDevice.html#method.state) only returned Default, Addressed and Configured, never Suspend.
I tried it with both a windows and a linux noteboot. On windows, it didn't work at all because windows just powered down the USB port when suspending the notebook. On linux, I saw no state change on suspend and a sequence of Default, Addressed and Configured on resume, but it didn't matter which version of usb-device I was using.

The way I did test suspend was:

connect the device usb to a laptop
connect the debug probe to my desktop
probe-run the firmware showing the defmt traces (especially on usb_dev.state() changes).
make the laptop enter suspend
monitor the usb dev state move to Suspend.
wake up the laptop
monitor the usb dev state.

So with the feature:

disabled, you should not see the device enter Suspend (as it won't be reported to the usb stack).
enabled with :

usb-device=0.2.8 it should wake up into Default state (that's the broken behaviour).
usb-device=git it should resume to the previous state it was in before entering Suspend.

Yes, that's exactly what I did, but I never saw the usb dev state move to Suspend.

I also used a logic analyser to monitor the bus to make sure the state reported by the drivers (both on the device and dmesg on linux) where consistent with what happened physically on the bus.

With this patch, and the feature not activated, the pico_usb_twitchy_mouse just hangs.
It looks like the usb interrupt fires continuously. Probably because it's activated by setting the INTE.DEV_SUSPEND bit and then never cleared, because suspend() won't get called.

Ah that is a good point. Let me update that PR quickly.

BTW, do you know if https://github.com/rust-embedded-community/usb-device/issues/96 has any practical impact? What use-cases are broken by that bug?

Close :-)
error[E0599]: no method named `dev_resume_from_host` found for struct `pac::usbctrl_regs::inte::BUFF_STATUS_W` in the current scope
   --> rp2040-hal/src/usb.rs:443:22
    |
443 |                     .dev_resume_from_host()
    |                      ^^^^^^^^^^^^^^^^^^^^ method not found in `pac::usbctrl_regs::inte::BUFF_STATUS_W<'_>`

After adding the missing .set_bit(), the patch works as expected, in the following combinations:

usb-device 0.2.8, feature usb-suspend not enabled → Suspend state not visible from firmware
usb-device 0.2.8, feature usb-suspend enabled → Suspend state visible from firmware, wrong state after resume
usb-device from git, feature usb-suspend not enabled → Suspend state not visible from firmware
usb-device from git, feature usb-suspend enabled → Suspend state visible from firmware, correct state after resume

Even with the wrong state after resume, I didn't notice any ill effects. Maybe the linux kernel just works around the non-compliant behavior?

closing in favour of https://github.com/rp-rs/rp-hal/pull/410


Block scalars not parsed correctly if last entry in file

This is parsed successfully (based on this file):
lines: |
    458 Walkman Dr.
    Suite #292
city: Royal Oak

However, this fails with the address lines ("458 Walkman...") being marked as unparsed and no error token:
lines: |
    458 Walkman Dr.
    Suite #292

It doesn't seem to matter what comes after the content - it can be anything as simple as a comment.
Both literal block scalars (|) and folded block scalars (>) seem to behave in the same way.

Can't reproduce this issue.  Could you please double check the indentations and verify if issue still exists?

I no longer have the reproduction for this as I've since switched to using another library sorry.
I'll close this issue.


[BUG]: Fix for failing chromadb-client build

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

Python client build has not been working for a few releases now. Appears that build module is not longer available in default GH runner setup and needs to be explicitly installed

Test plan
How are these changes tested?
Manual test:
python -m pip install -r ./clients/python/requirements.txt && python -m pip install -r ./clients/python/requirements_dev.txt
....
Installing collected packages: sortedcontainers, pypika, websockets, uvloop, sniffio, pyyaml, python-dotenv, pluggy, packaging, opentelemetry-util-http, iniconfig, httptools, h11, click, attrs, asgiref, uvicorn, pytest, hypothesis, anyio, watchfiles, starlette, opentelemetry-instrumentation, opentelemetry-instrumentation-asgi, fastapi, opentelemetry-instrumentation-fastapi
Successfully installed anyio-3.7.1 asgiref-3.7.2 attrs-23.1.0 click-8.1.7 fastapi-0.105.0 h11-0.14.0 httptools-0.6.1 hypothesis-6.92.1 iniconfig-2.0.0 opentelemetry-instrumentation-0.43b0 opentelemetry-instrumentation-asgi-0.43b0 opentelemetry-instrumentation-fastapi-0.43b0 opentelemetry-util-http-0.43b0 packaging-23.2 pluggy-1.3.0 pypika-0.48.9 pytest-7.4.3 python-dotenv-1.0.0 pyyaml-6.0.1 sniffio-1.3.0 sortedcontainers-2.4.0 starlette-0.27.0 uvicorn-0.18.3 uvloop-0.19.0 watchfiles-0.21.0 websockets-12.0

sh ./clients/python/build_python_thin_client.sh
/Users/tazarov/experiments/chroma-experiments/oss/boto3-issue/.venv/bin/python: No module named build

pip install build

Installing collected packages: pyproject_hooks, build
Successfully installed build-1.0.3 pyproject_hooks-1.0.0

./clients/python/build_python_thin_client.sh
* Creating venv isolated environment...
* Installing packages in isolated environment... (setuptools>=61.0, setuptools_scm[toml]>=6.2)
* Getting build dependencies for sdist...
...
Successfully built chromadb-client-0.1.dev1011.tar.gz and chromadb_client-0.1.dev1011-py3-none-any.whl

Documentation Changes
N/A

@HammadB, @beggers TAL. We should be able to rollout a new client release with this fix.

Coordinator tests were fixed in https://github.com/chroma-core/chroma/commit/7dfadf4a1d7a2224d258f100250b574a8b9cde66 so merging this.


Coverage overlap?

How does istanbul handle coverage overlap?
For instance, say I have a unit test, test1.js which covers 100% of src1.js.
The next test, test2.js is actually intended to test src2.js but also ends up indirectly requiring and invoking part of src1.js.
So when both tests complete, src1.js has been covered once completely (by test1.js), and part of it covered twice (by both tests).
In this case, what will be the final coverage of src1.js in the istanbul report? The behavior I see is, if I run istanbul on test1.js in isolation, src1.js shows 100% coverage. But if I run both tests, I see less coverage which I presume (maybe wrong) is the part covered by test2.js. What can be done to make sure istanbul only considers the max coverage?

Apologies, this has nothing to do with overlapping coverage and is not an issue with istanbul. We were using node-jsx with "JS" extension which was clashing with istanbul's require hook and suppressing the coverage. Closing this.


Add required to Wysiwyg

Hello
This adds support for the "required" attribute to the different flavours of the Wysiwyg fields
BR

Merged in e780bcfde8ceed86486c0eee98387bca376db86a, thank you!


Improve loading/parsing speed in 'arrowable' environment

It takes a long time to read a large dataset from a source for the first time.
I created a fresh Docker environment for my dataframe example and found it very time consuming  to pull a large dataset of nycflights13.
If you use red-dataset-arrow, the cache is stored in the arrow file, but the first time you load it, it takes a long time to load and parse because it uses Ruby's CSV.
Is it possible to make the environment extended with red-dataset-arrow use arrow to load and parse?

How about adding Datasets::CSVParser like Datasets::ZipExtractor and extending Datasets::CSVParser in red-datasets-arrow?

Thanks @kou .
I will make a try to add Datasets::CSVParser first!


Remove container creation in load flow for container

1.) Remove creation of container in loader.resolve/container.load. Only use this flow for loading of an existing container.
2.) For creation of container only use loader.createDetached() flow.

I think I need to handle this first: https://github.com/microsoft/FluidFramework/issues/4049. Here we we will load from oldest snapshot when loaderheader.version === null.

@jatgarg Is this PR still relevant?

Closing it with new PR.

Can you link the new PR here?

Yes, in process of opening one.

This PR removes Loader version as null. https://github.com/microsoft/FluidFramework/pull/6358
We have kept some legacy path in container.load() mostly for testing purposes like snapshot tests.


Angular build not creating dist folder on production

Bug Report
Affected Package

 The issue is caused by package @angular/....
Is this a regression?

 Yes, the previous version in which this bug was not present was: ....
Description
 A clear and concise description of the problem...
When building an angular app using a Dockerfile,  ng build --configuration production does not always create a dist folder
my output path is defined as "outputPath": "./dist", in angular.json
Minimal Reproduction

 https://stackblitz.com/...

This is presumably due to #20985.

Downgrading  "@angular-devkit/build-angular": "12.0.0"  as suggested here, solves this in the interim

Duplicate of #20985.

@alan-agius4, Thanks,
However, that posted downgrade did not work, The problem with this issue is that sometimes the dist folder is created sometimes it is not. coincidentally a  downgrade at that time seemed to be the reason why the dist folder was created, subsequent deployments DID NOT create the dist folder.
Marking this as a duplicates assumes you know what is wrong, but I am honestly clueless about the referred issue. This issue was only created out of our frustrations building and deploying angular to staging and production servers as we could not reliably guarantee that all docker images built and deployed had the dist folder in them.

@babarinde, In that case, let me re-open the issue, but we'd require a reproduction to investigate this any further.

Upon further investigations, we noticed that its possible the server building the docker image may have been running out of memory at the point it should have created the dist folder. When we increase memory on server it builds with the dist folder and our deployments are fine.


IntelliSense for String literal types

I have this String literal type example
type TStyles = 'x' | 'y' | 'z';

Using IntelliSense for completion this code will be awesome:
var style:TStyles = '>>> I want to use [CTRL+J] here to offer only valid TStyles values <<<';

duplicate of https://github.com/Microsoft/TypeScript/issues/606


Update Mongodb chart

Signed-off-by: Czékus Máté<EMAIL_ADDRESS>
Description
Updated the MongoDB chart as discussed here: https://github.com/alexellis/arkade/issues/274#issuecomment-1181461452
Motivation and Context

[X] I have raised an issue to propose this change, which has been given a label of design/approved by a maintainer (required) #274

How Has This Been Tested?
Manually running arkade install mongodb then check helm for releases.

Are you a GitHub Sponsor yet (Yes/No?)

[ ] Yes
[X] No

Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Documentation

[ ] I have updated the list of tools in README.md if (required) with ./arkade get -o markdown
[ ] I have updated the list of apps in README.md if (required) with ./arkade install --help

Checklist:

[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I've read the CONTRIBUTION guide
[X] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[X] All new and existing tests passed.

[x] I have tested this on arm, or have added code to prevent deployment

I have tested this on arm, or have added code to prevent deployment

Do they have any form of ARM support like ARM64?


Add anchor escrow example

Closes #269

Since everyone's probably starting with PaulX's tutorial, thought it'd be worth doing an anchor write of it to show how much nicer anchor is in comparison :)
I more or less follow the logic used in this tutorial, with some small changes.

https://paulx.dev/blog/2021/01/14/programming-on-solana-an-introduction/

Awesome. Just some optional comments. I think it's worth addressing them since this example is very instructive, but it's up to you.
Also please run cargo fmt if you haven't already.

Done! Thanks for the feedback.

Let's ship!


Deploy: Remove gunicorn

We try to put all deployment logic in the deploy repository. This app doesn't tightly integrate gunicorn, so the choice of web server should be moved to the deploy repository. OCP uses uWSGI for all its other apps.

Superseded by #62


uncore,power in system view and html improvements

uncore and power in system-wide view of percpu collection
html report readability improvements
more accurate minimum kernel requirements in readme

thanks!


Request for quota resource

What resource do you need?
Terraform Resource Name:
google_cloud_quotas_quota_preference
What is your use case?
I have a crossplane composition we use for creating new accounts in a GCP org with a GKE cluster and some basic resources for workloads. One of these workloads need to run in a GPU instance, but since the default quota for it is set to 0 we would like to increase this by creating a Cloud Quota Request automatically in our composition.
Reference
https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_quotas_quota_preference

Hi @matheusraz,
Thank you for bringing up this; if you want to contribute we appreciate that. This guide may help you: https://github.com/crossplane/upjet/blob/main/docs/adding-new-resource.md


It is not possible to leave an organization

Users should be able to leave an organization, and as an organization owner you should be able to remove a user from the organization.

itsyouonline/identityserver/commit/39355e359685e8c228d555db71571b14251f3426


Fix unicode encoding of pinned report date str

#880

I lowercased time period choices. I can't see where they appear in the OS other than the pinned reports.


Consider switching from gometalinter to golangci-lint

Not a big deal for this project right now, but I hit a few oddities with Go 1.12 in other projects and had to dig into linter issues. Seems like gometalinter is EOL soon.

The gometalinter GitHub project will be archived on 2019-04-07. Releases will still be available for download but no further code will be committed and issues will be read-only.
Switch to golangci-lint.
Many thanks to all contributors, in particular dnephin who has helped me maintain gometalinter for the last year or two.

See also: https://github.com/alecthomas/gometalinter/issues/590

Thanks for the pointer. Definitely something we can look into.

I have https://github.com/ehotinger/containerd/commit/db1288fc54c5b60793fb89ed8ee4fd0fb1946fcb laying around to fix a few tooling issues after updates for myself. I can PR it if people care about it this in the master branch. There's one minor issue with ctr's usage of the progress bar which I made an upstream issue for; didn't bother tracking it down yet.

Update: https://github.com/golangci/golangci-lint/issues/414 was fixed so containerd can be switched without any other issues.

Go ahead and submit a PR for this

@crosbymichael go vet errors on master:
runtime/v1/linux/proc/io.go:266:2: lostcancel: the cancel function is not used on all paths (possible context leak) (govet)
        ctx, cancel := context.WithCancel(ctx)
        ^
runtime/v1/linux/proc/io.go:274:3: lostcancel: this return statement may be reached without using the cancel var defined on line 266 (govet)
                return nil, err


twemproxy only sees one of the memcached servers in the pool

It's my understanding that when a server in the twemproxy pool gets ejected, the other server in the pool should still be available for caching. It seems that when I take out memcached-1 only, the proxy itself becomes unavailable. If I take out memcached-2 from the pool, everything operates normally, except that there doesn't seem to be any indication in the logs that the server leaves or returns to the pool.
I have tested that both memcached servers are available directly. If I put one or the other memcached sever by itself in the pool configuration, they're available using the proxy, but only memcached-1 is available if I have them both in the pool. I've tried ordering them differently and it doesn't seem to make a difference. A tcpdump only ever shows traffic to memcached-1 when they are both in the pool. When nutcracker is restarted, I only see arp traffic going to one of the two servers, but never both.
To reproduce:
(nutcracker version 0.4.1 on centos 7)
/etc/nutcracker/nutcracker.yml
bad_pool:
  listen: <IP_ADDRESS>:22122
  hash: fnv1a_64
  distribution: ketama
  auto_eject_hosts: true
  timeout: 400
  server_retry_timeout: 30000
  server_failure_limit: 3
  servers:
   - <IP_ADDRESS>:11211:1 memcached-1
   - <IP_ADDRESS>:11211:1 memcached-2

telnet <IP_ADDRESS> 22122
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS>.
Escape character is '^]'.
set testing 1 0 3
one
STORED

ssh <IP_ADDRESS>:
sudo systemctl stop memcached

telnet console:
get testing
SERVER_ERROR Connection refused
Connection closed by foreign host.

nutcracker logs for sequence:
[2017-08-18 11:08:46.894] nc_core.c:43 max fds 1024 max client conns 989 max server conns 3
[2017-08-18 11:08:46.894] nc_stats.c:851 m 4 listening on '<IP_ADDRESS>:22222'
[2017-08-18 11:08:46.894] nc_proxy.c:217 p 6 listening on '<IP_ADDRESS>:22122' in memcache pool 0 'bad_pool' with 2 servers
[2017-08-18 11:08:56.457] nc_proxy.c:377 accepted c 8 on p 6 from '<IP_ADDRESS>:41122'
[2017-08-18 11:09:11.595] nc_request.c:96 req 1 done on c 8 req_time 1160.716 msec type REQ_MC_SET narg 2 req_len 24 rsp_len 8 key0 'testing' peer '<IP_ADDRESS>:41122' done 1 error 0
[2017-08-18 11:14:00.115] nc_response.c:118 s 9 active 0 is done
[2017-08-18 11:14:00.116] nc_core.c:237 close s 9 '<IP_ADDRESS>:11211' on event 00FF eof 1 done 1 rb 8 sb 24
[2017-08-18 11:14:06.887] nc_core.c:237 close s 9 '<IP_ADDRESS>:11211' on event FFFFFF eof 0 done 0 rb 0 sb 0: Connection refused
[2017-08-18 11:14:06.887] nc_request.c:96 req 4 done on c 8 req_time 0.597 msec type REQ_MC_GET narg 2 req_len 13 rsp_len 33 key0 'testing' peer '<IP_ADDRESS>:41122' done 1 error 0
[2017-08-18 11:14:06.887] nc_core.c:237 close c 8 '<IP_ADDRESS>:41122' on event FF00 eof 0 done 0 rb 37 sb 41: Operation not permitted

This sounds like expected behavior for the service, which does not retry failed requests against remaining server members. The client will need to respond appropriately to such failures, perhaps by retrying the request.
The "testing" key is mapped to a server in the pool, which would explain why you can deactivate "memcached-2" to no apparent effects, since "memcached-1" is selected to service the request. The pool is configured to eject hosts after 3 errors, so in the testing scenario that you have provided, I would expect the 4th request for key "testing" to evaluate against "memached-2".

Also,   server_retry_timeout: 30000 means it will take 30 seconds before twemproxy attempts to reconnect - until 30 seconds have elapsed all traffic will be sent to the other server.
I think the planned heartbeat/failover patches in  https://github.com/twitter/twemproxy/issues/608 may result in faster reconnections when a server recovers once those changes are merged into twitter/twemproxy, though that may change before the planned 0.6.0 release.

If twemproxy didn't reconnect after more than 30 seconds, the changes planned for 0.6.0 also refactors the reconnection logic significantly, and may end up fixing it.
0.5.x also fixes some memory corruption errors.


How to submit PR

Hello,
I have a PR to submit to solve a use case we faced in my company but I have no permissions to do it (tried to push my branch bu got permission denied).
How can we participate in this cool project?
Thanks!

Oups. Forget about it, just forking. Sorry!


Don't clear the canvas until re-rendering is finished when the scale or rotation is changed (issue 6467)

This regressed in PR #4920.
The main motivation for PR #4920 was to quickly get rid of old canvases when pages are evicted from the PDFPageViewBuffer cache. However it inadvertently broke the use-case where the canvas is used as a preview, on scale or rotation changes, until the re-rendering is finished.
Fixes #6467.
r? @brendandahl
Please note: The second commit is not related to the issue, but it fixes a couple of stylistic issues that I saw while working on this code; easier reviewing with: https://github.com/mozilla/pdf.js/commit/424f62eaed546a1e55c9b4361fa7a58086c00021?w=1.

Thanks for the quick fix.


[Code Completion] Split code completion results into context free part that can be cached and contextual part displayed to the user

This is the first (of two) refactoring part of #40399, which has gotten a little big.
This allows makes the distinction between cachable and non-cachable properties cleaner and allows us to more easily compute contextual information (like type relations) for cached items later.

@swift-ci Please smoke test

@swift-ci Please smoke test Windows

@swift-ci Please test Windows

I refactored the PR to make a cleaner distinction between USR-based and ASTContext-based types. For now ContextFreeCodeCompletionResult stores a CodeCompletionResultType  that is always backed by a ASTContext-bound swift::Type. That design doesn’t allow caching the types yet.
In a follow-up PR I will add the option to back CodeCompletionResultType by a swift::ide::USRBasedType which can be cached and supports computation of convertible type relations by storing the USRs of its supertype. The current WIP of that PR lives at https://github.com/ahoppen/swift/tree/pr/compute-typerelation-for-global-cached-results.

@swift-ci Please smoke test

I have rebased this PR now that https://github.com/apple/swift/pull/40724 is merged and tried to make it as easy to review as possible:

707e6e855bfc3a6cc65c0d71b408bf63ee9b56ab is a super simple refactoring that just pull out a few nested types from CodeCompletionResult to the top-level
e0253ca624e2709c3e4c5a2f88344251c0b72888 performs the actual split into contextual and context-free result bits.

@swift-ci Please smoke test

@swift-ci Please smoke test Windows

@swift-ci Please smoke test Windows

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test


Add gnu tests

Fixes #1431
Run the GNU coreutils tests to monitor compatibility.

Amazing to have this, bravo :)
A few things:

Please don't make the job fail
please fix ```
/usr/bin/python: No module named pyinotify
move-dir-while-traversing.sh: skipped test: python inotify package not installed

* please fix the getlimit issue
* please fix ```inotify-race2.sh: skipped test: can't run gdb``` (installing gdb should be fine)

Amazing to have this, bravo :)
A few things:

Please don't make the job fail
please fix ```
/usr/bin/python: No module named pyinotify
move-dir-while-traversing.sh: skipped test: python inotify package not installed

* please fix the getlimit issue
* please fix ```inotify-race2.sh: skipped test: can't run gdb``` (installing gdb should be fine)

The fix for the getlimits feels nasty, but it's all I can come up with. The getlimits executable is something the GNU coreutils builds, but isn't shipped in the coreutils packages for ubuntu or fedora so it might just be a utility for the tests.

The fix for the getlimits feels nasty, but it's all I can come up with. The getlimits executable is something the GNU coreutils builds, but isn't shipped in the coreutils packages for ubuntu or fedora so it might just be a utility for the tests.

The getlimits trick is failing with:

  CC       src/getlimits.o
In file included from src/getlimits.c:25:0:
src/system.h:43:10: fatal error: configmake.h: No such file or directory
 #include "configmake.h"
          ^~~~~~~~~~~~~~

The getlimits trick is failing with:

  CC       src/getlimits.o
In file included from src/getlimits.c:25:0:
src/system.h:43:10: fatal error: configmake.h: No such file or directory
 #include "configmake.h"
          ^~~~~~~~~~~~~~

That is strange, it would have been building that when running make before. Let me find what provides the header.

That is strange, it would have been building that when running make before. Let me find what provides the header.

The GNU coreutils is what provides that header, it's lib/configmake.h so I'm confused.

The GNU coreutils is what provides that header, it's lib/configmake.h so I'm confused.

We can fix "getlimits" in a follow up PR :)
I won't block on it!

We can fix "getlimits" in a follow up PR :)
I won't block on it!

figured it out

figured it out

Excellent, bravo for the work :)

Excellent, bravo for the work :)


Add explaination on tasks login in the post install file

Pull Request
What does this PR do?
Fixes #108
If a tasks fails inside Meilisearch, they are not logged into the extensions logs as they are asynchronous. Explaination on the matter had to be added in the post install documentation,

bors merge


Reverse proxy proposal !

Reverse proxy should increase the account password, which can enhance security!
Figure:

if connection with client is already estabilished with a password(AES crypted), why another pass for reverse proxy?

Duplicate of #592.


missing pre-requistes

[Enter feedback here]
You need to mention the pre-requites of having Hyper-V installed on the computer
I got an error...
"Mount-VHD : Hyper-V has not been installed on computer "
Hope you can add this to the page....

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

ID: 398aa37a-8b2f-c369-6919-14470ee28a27
Version Independent ID: 7c54bbd8-d0d2-685b-ade9-40d51d07a300
Content: Mount-VHD (Hyper-V)
Content Source: docset/winserver2019-ps/hyper-v/Mount-VHD.md
Product: w10
Technology: windows
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

@NeoGit111
Thank you for your feedback.
Having Hyper-V installed on your machine might not be required as you may want to use it only for remote management of another server with Hyper-V Role. The module is usable on its own for remote management but for local management you need Hyper-Role installed.
Let me know if you have any questions.


Update sensor configuration via action

The github sensor monitor the repository added by the register_org action.  The action has following additional parameters:

repositories: list of repositories to be monitored
event_type_whitelist: list of the type of event to be monitored

https://github.ibm.com/juno/juno/issues/198

About the persistent data, it is using the datastore of the stackstorm.

Yes, the register_org sequence should work.


Wrong link to Format information

The link in

For the Format parameter, see Format Property for more information.

refers to the Format property for XmlPort elements, not the intended page for general formatting information, which is likely to be https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-format-property.

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

ID: c745c7fa-6517-541f-d18a-36226db7fb64
Version Independent ID: f41b2a8c-8545-a5a2-4550-092786b1fde9
Content: System.Format Method - Business Central
Content Source: dev-itpro/developer/methods-auto/system/system-format-joker-integer-string-method.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for catching this. The issue will be fixed with the next doc refresh.

Thanks for catching this. The issue will be fixed with the next doc refresh.


Unable to cancel long running commands by clicking "Cancel" in frontend

Steps to reproduce:

Start a long running command.
Click cancel in the Run Log.
The command created in (1) is cancelled. The finalize_fn is not called. A new instance of the same command appears in the Run Log.

This applies to uod commands. Other cancellable commands include
Watch and
5.0 Info: test
for which cancel and/or force work as intended


add eurostat synonyms #920

closes #920
I have also added 'secondary production of energy' as an alternative term to increase the number of synonyms.
If someone disagrees, I would remove the term again.

I would recommend to do the changes rather in oeo-shared than directly in uo-module.

I am no expert in operations like this. But I would try the following:

Open oeo-shared in a text editor and manually add the following line at the bottom:

Class: <http://purl.obolibrary.org/obo/UO_0000224>

Switch Protége to Add fresh axioms to active ontology.
Open only oeo-shared in Protégé. Find kilowatt-hour in oeo-shared and add there the annotations.
Close Protégé and start it again, open oeo.omn. Now everything should be alright.

I hope that works. If that doesn't that doesn't work, I don't know what to do else.

The change of the catalog file happens from time to time, but I don't think that this is a problem, so I'll approve.


use version number instead of release in .travis.yml

release will change over time, but your REQUIRE file says this package supports julia 0.4 so it should continue to be tested

Will remove nightly here, separately

Could make it an allowed failure, so it runs buts doesn't make your status red


fix: update log level handling

Short Description
This PR updates Maru's logging to match the standard library's log/slog package, and appropriately filters log messages according to levels. Tests included and feedback very welcome.
Long Description
The current implementation of log level handling is misleading because our custom handler doesn't filter by level. The code comment mentions logging functions already being aware if they are allowed to be called, but in practice I have not found that to be true. This is further complicated by Maru's log levels not matching what log/slog uses both in values and in ordering.
Example: slog uses these levels/ordering
const (
	LevelDebug Level = -4
	LevelInfo  Level = 0
	LevelWarn  Level = 4
	LevelError Level = 8
)

(See here for source and long explaination to the numbers used: https://pkg.go.dev/log/slog#Level)
Where as Maru uses these levels/ordering:
const (
	// WarnLevel level. Non-critical entries that deserve eyes.
	WarnLevel LogLevel = iota
	// InfoLevel level. General operational entries about what's going on inside the
	// application.
	InfoLevel
	// DebugLevel level. Usually only enabled when debugging. Very verbose logging.
	DebugLevel
	// TraceLevel level. Designates finer-grained informational events than the Debug.
	TraceLevel
)

(source: src/message/logging.go#L16-L29)
In theory, implementing the Handler interface would have us ignore messages with a lower level than the one set. Maru sets it's default log level to InfoLevel (from Maru's constants, not slog's) which results in a value of 1. However because our InfoLevel is 1 and slog's LevelInfo is 0, then in theory Maru's logger should actually ignore it because it's a lower level. A call to message.SLog.Info() (ex. in utils.go) invokes slog's Info() method, which calls an internal method log() with slog's LevelInfo level which is a value of 0. The log() method calls the handlers Enabled() method to see if it should log the message, which for maru always returns true, and then passes it on to the handlers Handle() method (Maru's Handle() method here) and we print the message, even though we shouldn't because it's a lower value than our default.
The net effect is setting the log level with --log-level has no effect, except for when setting to trace, in which case we output pterm debugging information with lines for errors/traces and debug calls. Otherwise Maru will always output all of the logs from Debug(), Info(), Warn() or Error() regardless of the level set.
This PR updates Maru's log level constants both in values and ordering to match the standard library log/slog package, and implements the Enabled() method in the handler to filter correctly based on level. The net effect of this PR should be benign in that we aren't changing any usage details, but going forward we'll correctly output logs according to the set level.
NOTE: This PR is based off of my other PR (#140) for changing the Makefile with regards to test-unit and test-e2e tests.
Test output:
 ➜ go test ./src/message/... -v -count=1
=== RUN   Test_LogLevel_Diff
=== RUN   Test_LogLevel_Diff/DebugLevel
=== RUN   Test_LogLevel_Diff/InfoLevel
=== RUN   Test_LogLevel_Diff/InfoWarnLevel
=== RUN   Test_LogLevel_Diff/WarnInfoLevel
=== RUN   Test_LogLevel_Diff/InfoTraceLevel
=== RUN   Test_LogLevel_Diff/TraceInfoLevel
=== RUN   Test_LogLevel_Diff/TraceLevel
--- PASS: Test_LogLevel_Diff (0.00s)
    --- PASS: Test_LogLevel_Diff/DebugLevel (0.00s)
    --- PASS: Test_LogLevel_Diff/InfoLevel (0.00s)
    --- PASS: Test_LogLevel_Diff/InfoWarnLevel (0.00s)
    --- PASS: Test_LogLevel_Diff/WarnInfoLevel (0.00s)
    --- PASS: Test_LogLevel_Diff/InfoTraceLevel (0.00s)
    --- PASS: Test_LogLevel_Diff/TraceInfoLevel (0.00s)
    --- PASS: Test_LogLevel_Diff/TraceLevel (0.00s)
PASS
ok      github.com/defenseunicorns/maru-runner/src/message      0.235s

Related

https://github.com/defenseunicorns/uds-cli/issues/916

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Other (security config, docs update, etc)

Checklist before merging

[x] Test, docs, adr added or updated as needed
[x] Contributor Guide Steps followed

@Racer159 thanks again for the review. I applied your feedback and added an ErrorLevel level. I also updated the tests to check for the extra lines of output when using TraceLevel. In hindsight the way I went about checking feels clunky, so if you have ideas on improving it I'm all for it.


Debug messages in e-Internationalization

e-Internationalization creates a lot of debug messages. They do not use a logger but are printed directly to the console. Usually I dont complain about a few lines printed directly to the console but in e-Internationalization it is too much. It prints douzens / hundred of lines on the console so I get lost while working on the code.
Please print these information using a log4j logger and use log level debug. Then everyone can switch on / off this information via configuration.
You can copy the log4j.properties from the broker.

Sorry, I totally agree with you. Those messages were for my testing purpose. Usually I remove all of  them, but this time I forgot. I'm going to delete them

Debug messages deleted

Thanks


res._removedHeader does not exists

I got this error:
TypeError: Cannot set property 'content-length' of undefined
    at ServerResponse.OutgoingMessage.removeHeader (_http_outgoing.js:388:30)
    at ServerResponse.onResponseHeaders (/home/imbolc/0/p/action-loop/node_modules/compression/index.js:202:13)
    at ServerResponse.writeHead (/home/imbolc/0/p/action-loop/node_modules/on-headers/index.js:46:16)
    at ServerResponse._implicitHeader (_http_server.js:157:8)
    at ServerResponse.write (/home/imbolc/0/p/action-loop/node_modules/compression/index.js:83:14)
    at /home/imbolc/0/p/action-loop/node_modules/express-pouchdb/lib/routes/changes.js:64:17
    at process._tickDomainCallback (internal/process/next_tick.js:129:7)

I just fix this with monkey patching of compression/index.js:
      // header fields
      res.setHeader('Content-Encoding', method)
      try {
        res.removeHeader('Content-Length')
      } catch (e) {
        console.log(e)
        if (res._removedHeader === undefined) {
          res._removedHeader = {};
        }
        res.removeHeader('Content-Length')
      }

Do you have any ideas why does it happen and what the right way to fix this?

Hi @imbolc, very weird, I have never seen such an error and our tests have never encountered it, either :/
Would you be able to provide all the following?

The version of Node.js you are using.
The version of this module you are using.
Complete code that has this issue, such that I can copy and paste it into a file and run the server.
Provide the steps I need to perform against your code to cause the error to appear.

@dougwilson I have a feeling this was related to a version of hoodie at the time - sounds like we'll know more soon in the referenced issue.

@dougwilson I think it's safe to assume it wasn't expressjs/compression that was causing the issue, however I'd be keen to hear from @imbolc on this to double check.

The problem is most likely with the hapi-to-express module:
https://github.com/hoodiehq/hoodie-store-server/blob/master/index.js#L73-L76
hapress.res._removedHeader is undefined and that’s the problem, it’s not related to compression, it’s just the place where it blows app because of the res.removeHeader('Content-Length') call

see https://github.com/jakepruitt/hapi-to-express/issues/5

this is not a compression issue, sorry for the noise :)
I resolved the problem that Hoodie had via https://github.com/hoodiehq/hoodie-store-server/pull/60
Thanks for your great work, @dougwilson :wave:

Ah, thanks for the heads-up, @gr2m ! I see that PR was merged as well. It sounds like I can close this issue. Let me know if I should re-open for any reason :)


radio component work in progress

Description:
Please remember that the reviewer may not be as familiar with work being done or the project as you.

Radio component in progress
need to find a way to add values to each radio and add a label text from text component

Run command:
npm run

[ ] This code includes new npm packages/libraries

QA instructions (if applicable):

[ ] Unit tests (if needed)
[ ] Code cleanup (removed dead code, console logs, sorted props, etc)
[ ] Updated ticket with info and linked to this PR

@dlaracarvajal If there are no upcoming changes, please merge it

@dlaracarvajal If there are no upcoming changes, please merge it

I've added new changes. The radio component is done.


sc-5041: sentry implementation on frontend side

Type of change

[x] new feature

Scope of changes
sentry implementation for error tracking  on frontend side
Author checklist

[ ] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[ ]  I have added new test fixtures as needed to support added tests
[ ]  I have moved the associated ShortCut or Jira ticket to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

Codecov Report

Merging #510 (00316e7) into main (88106e3) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 00316e7 differs from pull request most recent head ce2a67d. Consider uploading reports for the commit ce2a67d to get more accurate results

@@           Coverage Diff           @@
##             main     #510   +/-   ##
=======================================
  Coverage   37.46%   37.46%
=======================================
  Files         151      151
  Lines        2389     2389
  Branches      608      608
=======================================
  Hits          895      895
  Misses       1319     1319
  Partials      175      175

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 88106e3...ce2a67d. Read the comment docs.


[async_client] Introduce protobuf to jsonrpc type conversions

Motivation
There is currently no easy way to transform protobuf structs into the legacy rust jsonrpc types. This PR solves this by implementing TryFrom traits for all types.
Test Plan
Added unit tests to cover all conversions.

This PR may have modified JSON-RPC server code.
Breaking changes policy:

Chaning JSON-RPC method signatures or removing/modifying fields
in the response in /V1 will not be accepted.
Adding fields is ok.
Adding a new JSON-RPC method is ok.

Please ensure you have also done the following to update the docs:

Update json-rpc/API-CHANGELOG.md.
Add/update type/method documentation under json-rpc/docs.

LGTM, Thanks!

I don't think this is good path moving forward by providing this converter in diem/json-rpc. I understand why you need it, hence you may keep it in where use it.

Can you please elaborate? I do see value on having an easy conversion mechanism as part of the public api because they are ultimately mirror structs and given both struct sets are part of this crate, this seems the appropriate place to impl the conversion traits.

I don't think this is good path moving forward by providing this converter in diem/json-rpc. I understand why you need it, hence you may keep it in where use it.

Can you please elaborate? I do see value on having an easy conversion mechanism as part of the public api because they are ultimately mirror structs and given both struct sets are part of this crate, this seems the appropriate place to impl the conversion traits.

These view types should be removed eventually, instead of we maintain 2 types and convert them. the problem with converter is, when we need add a new field, the field will be added into the view type before we delete them, hence it also need update the converter, which makes the converter to be tight to a specific version of the code.

hence it also need update the converter

I think that's a reasonable tradeoff for the convenience :) IMO as long as both coexist then the user will likely have the need to convert, unless they want to couple their domain code with protobuffer structs.

hence it also need update the converter

I think that's a reasonable tradeoff for the convenience :) IMO as long as both coexist then the user will likely have the need to convert, unless they want to couple their domain code with protobuffer structs.

Like I said, I understand why you want to do this, but it's just not right place for these, you are free to put these into where use them.

The protobuf types are not rust friendly and require a lot of boilerplate code to be maintained by clients trying to use them. This code is agnostic to any usage of the client and hence it makes sense to stay here along with tests. Anybody else trying to write a rust client would have to go through the same ordeal and write a similar implementation.
As a pure rust project, we should provide first class support for rust-types to clients of the project rather than requiring everyone to write fragile boilerplate code.
I do understand that its a tradeoff to maintain it here, but the benefits significantly outweight the costs.

I think the point is that the Views are legacy code and will be stripped out sooner rather than later.

The protobuf types are not rust friendly and require a lot of boilerplate code to be maintained by clients trying to use them. This code is agnostic to any usage of the client and hence it makes sense to stay here along with tests. Anybody else trying to write a rust client would have to go through the same ordeal and write a similar implementation.
As a pure rust project, we should provide first class support for rust-types to clients of the project rather than requiring everyone to write fragile boilerplate code.
I do understand that its a tradeoff to maintain it here, but the benefits significantly outweight the costs.

The point is I can't promise no breaking change if this is merged.
Once release 1.1 is settled, I will switch server code to use protobuf types, and move view types to where legacy code may use it and likely completely remove them. It can happen anytime in Jan, hence I don't see a reason to merge this change.
I understand you're not interested in other languages, but I don't think rust is special client application language because we implement server by Rust.
It may change when we have a maintainer can focus on Rust language client SDK development.
You are free to maintain a copy of rust view types for a specific version of JSON-RPC API response, which I don't recommend.


To Prod: Change to cloud-hosted-draft-guide-containerize-podman

Updated by github actions, triggered by the draft-guide-containerize-podman repo.

close

SNL not support podman yet


Update Flux version to v0.83.1

We need to update the version of Flux to v0.83.1 on InfluxDB master.
The primary problem with updating the Flux version is redoing the changes that were made as part of the Algorithm W feature work.
Update the Flux version on the above branch and fix the compilation errors using the master branch as a guide for what changes were made. Then update the Makefile to use pkg-config to build the Rust portions of Flux and ensure tests continue to pass. If there are tests that would take a substantial amount of work to fix (greater than 5-10 minutes), skip the test and create an issue to follow up on fixing that test.
This does not include any work for push down changes that were made on the master branch. This issue is only about fixing compilation errors and tests associated with updating the Flux version. This means that work to port new planner rules and the capabilities logic is out of scope.
DOD:

InfluxDB Master builds and passes tests with Flux v0.83.1

The current master is based on the flux backport to 1.x. When I would backport flux from 2.0 to 1.x, I would rsync 3 directories and then reapply patches. I would then save the patches so I could remember what I did since the patches would not cleanly apply.
Here are the patches: https://github.com/influxdata/influxdb/tree/1.8/patches
These patches appear to have already been applied to the master branch and so they don't need to be reapplied, but they can be used as a guide to know what changed and whether it was intentional.


new tmt plan: rpmlint packit.spec

Let's run rpmlint on our spec file - we already do this in ogr.
RELEASE NOTES BEGIN
RELEASE NOTES END

/packit retest-failed

/packit test


adding the required files for static page verification of CFT

Why did u removed appspec.yaml and index.html files from the PR? They still seem to be required.

Please give a link to this workflow results with latest template in dev branch.

https://github.com/sshajiya/aws-waf-solution-template/runs/4308204639?check_suite_focus=true

Please give a link to this workflow results with latest template in dev branch.
https://github.com/sshajiya/aws-waf-solution-template/runs/4308204639?check_suite_focus=true
The above link is the passed workflow log with the existed template in master branch.

With the new template in dev branch is it failing with default parameter values and asking the new sshkey for the ec2 instance.
Here is the link of log result for reference.
https://github.com/sshajiya/aws-waf-solution-template/runs/4308853375?check_suite_focus=true

With the new template in dev branch is it failing with default parameter values and asking the new sshkey for the ec2 instance.

In order to merge your test into master it has to run successfully with latest template version from dev branch. Please make it work and update PR accordingly.


unable to use setLabel and closeLabel together with ng-translate

Hi,
Thanks for the hardworking for this plugin, it is awesome.
I do have problem to use the setLabel and closeLabel settings together with ng-translate. ng-translate will return a promise which means that I cannot get the result immediately(when the directive being init/render). I tried the following two methods, but failed.

Put the entire $scope.timePickerObject = {...} inside the ng-translate promise
Result: ionic-timepicker return error because timePickerObject is missing during init

Put the entire $scope.timePickerObject = {...} outside the ng-translate promise, but keeping $scope.timePickerObject.setLabel and closeLabel inside the ng-translate promise
Result: ionic-timepicker runs fine but setLabel and closeLabel settings are not used since the link fxn only runs once at the beginning and there's where setLabel and closeLabel being aside.

Any good idea to resolve this problem? Adding a watch for setLabel and closeLabel will be pretty inefficient though.
Thanks.

Please use v 0.5.0 to resolve this issue. With this version of component you can configure the component.


Remove deprecated modules

This PR removes the following features/modules:

GelfLayout
log4j-cassandra
log4j-couchdb
log4j-jeromq
log4j-kafka
log4j-layout-jackson-json
log4j-layout-jackson-yaml
log4j-mongodb3
log4j-spring-boot
log4j-spring-cloud-config

and addresses following tickets:

#1951
#1969

Review aid
To ease the review process, I suggest the following approach:

check out the branch locally
diff it against main (grouping by directory helps)
only focus on changes that are outside the deleted features/modules

I also think that the reparenting of log4j-spring-cloud-config-client (commit 0121847af4fbba60a84eb52bc27e49a781cd4e71) should be backported to 2.x. Do you mind doing the cherry-pick after merging this PR?

I also think that the reparenting of log4j-spring-cloud-config-client (commit 0121847) should be backported to 2.x. Do you mind doing the cherry-pick after merging this PR?

@ppkarwasz, implemented this in 3b94a483cb78d17055713ea6facbea53703ab492.


All Inertia requests must receive a valid Inertia response, however a plain JSON response was received.

I'm returning a valid inertia response from controller.
public function getStartedPage()
{
if(Auth::check()){
return redirect('/');
}
return inertia('auth/get-started');
}
And on local machine its working fine, but on production on every inertia link it's returning error in modal pop-up.
"All Inertia requests must receive a valid Inertia response, however a plain JSON response was received."
https://stackoverflow.com/questions/71522603/laravel-inertia-requesting-for-valid-response-on-production-server-however-works

same any solve on this

Or you are using a proxy and overwriting the content type, there is a lot of possible causes and without additional info it's impossible to know which

The issue was solved by reinstalling project on production. Sorry for late comment.

use Spatie\Permission\Exceptions\UnauthorizedException;
In your www/laravel-example/app/Exceptions/Handler.php
class Handler extends ExceptionHandler
{
/**/
public function register(): void
{
$this->renderable(function (\Spatie\Permission\Exceptions\UnauthorizedException $e, $request) {
Session::flash('flash_titulo', 'Unauthorized!!');
Session::flash('flash_variante', 'danger');
Session::flash('flash_mensaje', $e->getMessage());
return to_route('landing_page')->with(['error' => $e->getMessage()]);
});


Remaining Time (entity) on my Washer is not working fine

On Washer, the sensor of remaining time is not working. It said that this entity is not available, but in my LG Thinq app I can see the remaining time.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment details:

Environment: Raspberry Pi4
Home Assistant version installed: The latest of today
Component version installed: 0.33.2
Last know working version: I don't know :(
LG device type and model with issue: Washer F4WV509S1E.ABWQPIS

That sensor is disabled by default. Just enable it in HA.

How can I enable in HA? I'm sorry that I'm a beginner :((

Ok, but this is not a HA help forum, you should ask for this in the community.
Anyway: go to Settings -> Device and Service. Select integration device, select your device and there you can select and enable disabled entities.
I close this issue because not an integration problem.


feat: improve the UnoCSS example

Use UnoCSS from core to be able to configure it since configuring using the CLI does not work on Deno because of some unexpected ESM errors.
Like mentioned, UnoCSS can be configured this way.
Renamed the output file to main.css and ignored it as it is not necessary for it to be pushed.

Hmm, this branch does not seem to be in a working state? Please reopen if this is in error


ENH: sparse: avoid densification on broadcasted elem-wise mult

Fixes #5056 (again).
Now, the only way to get a dense result from sparse.multiply(dense) is when the sparse matrix has only one element and the dense matrix has more than one element.

Is that enough of a regression test? Maybe good to add examples in https://github.com/scipy/scipy/issues/5056#issuecomment-257148393 as a test?

@rgommers: I reworked the logic a bit and added comments to make what's happening more clear. I also added another test matrix, so now we have full coverage on this PR. Removing the isspmatrix check in the unit test (see my first commit's changes) ensures that if any dense output is produced, the call to .todense() will throw an exception and fail the test.
We don't have a test for the "custom object" case, yet, though I'm not sure how useful it would be. This snippet:
class Custom(object):
    def __rmul__(self, other):
        return 'rmul: %s' % other

x = ss.eye(2, format='csr').multiply(Custom())

produces x:
<2x2 sparse matrix of type '<type 'numpy.object_'>'
        with 2 stored elements in Compressed Sparse Row format>

with x.data: array(['rmul: 1.0', 'rmul: 1.0'], dtype=object).
This is in line with the numpy behavior (i.e., np.multiply(np.eye(2), Custom())).

Removing the isspmatrix check in the unit test (see my first commit's changes) ensures that if any dense output is produced, the call to .todense() will throw an exception and fail the test.

Indeed. Tests LGTM.

In it goes. Thanks CJ!


Address UX feedback on GDT result view

Why these changes are being introduced:
This responds to UX feedback on GDT-130 (result view for GDT).
Relevant ticket(s):

GDT-130

How this addresses that need:
This removes result padding in smaller viewports, moves result markers outside of the titles, changes full record link hover/focus color to blue, and removes the visited styling for full record links.
The visited styling remains for 'View online' links in other TIMDEX UI apps, as these are outlinks to the source record. The GDT links go to the full record, which is already indicated as visited in the title link, so it doesn't feel critical to add visited styling to the button as well.
Side effects of this change:
GDT-248 has been opened to address some feedback on the result highlight labels.
Developer
Accessibility

[ ] ANDI or WAVE has been run in accordance to our guide.
[ ] This PR contains no changes to the view layer.
[ ] New issues flagged by ANDI or WAVE have been resolved.
[ ] New issues flagged by ANDI or WAVE have been ticketed (link in the Pull Request details above).
[ ] No new accessibility issues have been flagged.

New ENV

[ ] All new ENV is documented in README.
[ ] All new ENV has been added to Heroku Pipeline, Staging and Prod.
[ ] ENV has not changed.

Approval beyond code review

[ ] UXWS/stakeholder approval has been confirmed.
[ ] UXWS/stakeholder review will be completed retroactively.
[ ] UXWS/stakeholder review is not needed.

Additional context needed to review
E.g., if the PR includes updated dependencies and/or data
migration, or how to confirm the feature is working.
Code Reviewer
Code

[ ] I have confirmed that the code works as intended.
[ ] Any CodeClimate issues have been fixed or confirmed as
added technical debt.

Documentation

[ ] The commit message is clear and follows our guidelines
(not just this pull request message).
[ ] The documentation has been updated or is unnecessary.
[ ] New dependencies are appropriate or there were no changes.

Testing

[ ] There are appropriate tests covering any new functionality.
[ ] No additional test coverage is required.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.872%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
526

Relevant Lines:
532

💛  - Coveralls


no failure when all ants are bad

Adds checks for when all ants get flagged as bad -- tries to still run all the cells that are runnable, but doesn't just completely fail with an obscure error message. It also writes a file with suffix .all_ants_bad which should help scripts down the line to know that file calibration has indeed been run, but couldn't write out calfits etc.

Please don't push evaluated notebooks to this repo... it wastes space and it makes it harder to look at the diffs.


Prepare for next release

Coverage remained the same at 59.034% when pulling fc779d5a89f58783a93fe775bc07031a4df42a16 on feature/prepare-next-release into c7ee8bf9726b95da000206aae5b589656e67e294 on master.


Feature: SMTChecker support (a.k.a support all possible outputs)

Component
Forge
Describe the feature you would like
As of 0.8.4, solidity is depreciating the experimental pragma for SMT Checker as it runs on all files if enabled
pragma experimental SMTChecker;

The new way to configure this is through the JSON config file
"settings.modelChecker.targets": ["underflow", "overflow"]

You have to define which engine it should run as well, see https://docs.soliditylang.org/en/v0.8.11/smtchecker.html#smtchecker-engines
"settings.modelChecker.solvers": ["smtlib2","z3"]

settings.modelChecker.targets=<targets>

And what targets to check
: --model-checker-targets assert,overflow

These options are not configurable currently for forge
Additional benefits would be when using the yul optimizer you would have access to the ReasoningBasedSimplifier
Additional context
No response

Bump to @gakonst now that revm is the default

There are multiple issues covering compiled output already. utilizing the solc binary directly and feeding the compiled output is satisfactory for the use case described here


[api/clients] add per-client subscripton automatically on create

Description
This change ensures that per-client subscriptions are added to each client created via the /clients API endpoint.
Related Issue
Relates to #1596
Motivation and Context
Clients created by posting to /clients API endpoint are not getting per-client subscriptions added automatically, which makes it impossible to silence them individually. Silencing is expected to work for both real and proxy clients.
How Has This Been Tested?
Extended unit test to ensure client subscription is added automatically.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@cwjohnston Thanks a lot


Fix reports authorization

Coverage remained the same at 70.224% when pulling b5547f4c6a307c7ad33751fa0578d2b49c27ebeb on ynurmahomed:route-authorization into 2f13b2556826d0b652f8a16b8547ec01d45966aa on esaude:master.


refactor: changing input processor and interpreter to support more schemas

Description
As more input schemas are to be supported, we need to split out the schemas even more than we are now.
The changes:

It removes the generic Schema and CommonSchema completely and introduces the more specific Draft7Schema and AsyncapiV2Schema.
It changes the originalSchema property from the CommonModel to originalInput - see #86
Refactored the toX functions for Draft7Schema and CommonModel to be more generic, I did not find any way to generalize it anymore between them, so if you have any suggestion, let me know 🙏

Related issue(s)
Related to #360
Fixes #86

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

200 of 208 (96.15%)  changed or added relevant lines in 21 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 93.356%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/models/CommonModel.ts
53
54
98.15%

src/processors/JsonSchemaInputProcessor.ts
38
45
84.44%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
1954

Relevant Lines:
1995

💛  - Coveralls

@magicmatatjahu we can ignore the bug as #379 removes it.

@jonaslagoni I understand that we are still sticking with CommonModel etc? Will this be changed in the future?

For now, however I have started to rework that part, but it is a WIP, as I still need test different things before making some noise around it - https://github.com/asyncapi/modelina/issues/365#issuecomment-922461877

It seems like too much boilerplate to me, but it would take a lot of work to change it and that's the easiest way to do it now... 😅

Yea, exactly, dont have any better alternative at the moment. At least I dont see it.


coverage checks

@bkutil @demmer code coverage checking for this the graphite adapter. We could get 100% coverage but it would require simulating a graphite server and disconnecting/returning error codes on purpose and not something we "must" do right now. With this I've also made the juttle-graphite-adapter minimally compatible with 0.4.0 without actually converting to the new adapter format.

I'm merging this as is and we can discuss any additional changes in a subsequent PR.


NotFoundError: 2 root error(s) found when trying to run the code on Tensorflow 2

I am using the notebook on colab and I want to run it with TF2. However, I come across this error on calling model.fit_generator:
NotFoundError:` 2 root error(s) found.
  (0) Not found: Resource localhost/loss/lambda_3_loss/Variable/N10tensorflow3VarE does not exist.
	 [[{{node loss/lambda_3_loss/AssignAddVariableOp}}]]
	 [[Func/training/Adam/gradients/gradients/norm_6_1/cond_grad/StatelessIf/then/_1694/input/_4425/_2667]]
  (1) Not found: Resource localhost/loss/lambda_3_loss/Variable/N10tensorflow3VarE does not exist.
	 [[{{node loss/lambda_3_loss/AssignAddVariableOp}}]]
0 successful operations.
0 derived errors ignored.

The problem seems to be caused by the custom loss function, since I tried using a simple dummy loss function with no errors.
The changes I've made (to no avail) are these 2:

to include the lines
from tensorflow.python.framework.ops import disable_eager_execution disable_eager_execution()
before creating the model. Before adding these lines I came across this error:

TypeError: Cannot convert a symbolic Keras input/output to a numpy array.
This error may indicate that you're trying to pass a symbolic value to a NumPy call,
which is not supported.
Or, you may be trying to pass Keras symbolic inputs/outputs to a TF API that does not register dispatching,
preventing Keras from automatically converting the API call to a lambda layer in the Functional Model.

to use tensorflow.keras instead of keras, after suggestions from similar github issues and stackoverflow posts.

I am also adding the custom_loss code to include a few changes I made to use TF2 instead of TF1 (basically some tf.compat.v1.* additions).
def custom_loss(y_true, y_pred):
    mask_shape = tf.shape(y_true)[:4]

    cell_x = tf.compat.v1.to_float(tf.reshape(tf.tile(tf.range(GRID_W), [GRID_H]), (1, GRID_H, GRID_W, 1, 1)))
    cell_y = tf.transpose(cell_x, (0,2,1,3,4))

    cell_grid = tf.tile(tf.concat([cell_x,cell_y], -1), [BATCH_SIZE, 1, 1, 5, 1])

    coord_mask = tf.zeros(mask_shape)
    conf_mask  = tf.zeros(mask_shape)
    class_mask = tf.zeros(mask_shape)

    seen = tf.Variable(0.)
    total_recall = tf.Variable(0.)

    """
    Adjust prediction
    """
    ### adjust x and y
    pred_box_xy = tf.sigmoid(y_pred[..., :2]) + cell_grid

    ### adjust w and h
    pred_box_wh = tf.exp(y_pred[..., 2:4]) * np.reshape(ANCHORS, [1,1,1,BOX,2])

    ### adjust confidence
    pred_box_conf = tf.sigmoid(y_pred[..., 4])

    ### adjust class probabilities
    pred_box_class = y_pred[..., 5:]

    """
    Adjust ground truth
    """
    ### adjust x and y
    true_box_xy = y_true[..., 0:2] # relative position to the containing cell

    ### adjust w and h
    true_box_wh = y_true[..., 2:4] # number of cells accross, horizontally and vertically

    ### adjust confidence
    true_wh_half = true_box_wh / 2.
    true_mins    = true_box_xy - true_wh_half
    true_maxes   = true_box_xy + true_wh_half

    pred_wh_half = pred_box_wh / 2.
    pred_mins    = pred_box_xy - pred_wh_half
    pred_maxes   = pred_box_xy + pred_wh_half

    intersect_mins  = tf.maximum(pred_mins,  true_mins)
    intersect_maxes = tf.minimum(pred_maxes, true_maxes)
    intersect_wh    = tf.maximum(intersect_maxes - intersect_mins, 0.)
    intersect_areas = intersect_wh[..., 0] * intersect_wh[..., 1]

    true_areas = true_box_wh[..., 0] * true_box_wh[..., 1]
    pred_areas = pred_box_wh[..., 0] * pred_box_wh[..., 1]

    union_areas = pred_areas + true_areas - intersect_areas
    iou_scores  = tf.truediv(intersect_areas, union_areas)

    true_box_conf = iou_scores * y_true[..., 4]

    ### adjust class probabilities
    true_box_class = tf.argmax(y_true[..., 5:], -1)

    """
    Determine the masks
    """
    ### coordinate mask: simply the position of the ground truth boxes (the predictors)
    coord_mask = tf.expand_dims(y_true[..., 4], axis=-1) * COORD_SCALE

    ### confidence mask: penelize predictors + penalize boxes with low IOU
    # penalize the confidence of the boxes, which have IOU with some ground truth box < 0.6
    true_xy = true_boxes[..., 0:2]
    true_wh = true_boxes[..., 2:4]

    true_wh_half = true_wh / 2.
    true_mins    = true_xy - true_wh_half
    true_maxes   = true_xy + true_wh_half

    pred_xy = tf.expand_dims(pred_box_xy, 4)
    pred_wh = tf.expand_dims(pred_box_wh, 4)

    pred_wh_half = pred_wh / 2.
    pred_mins    = pred_xy - pred_wh_half
    pred_maxes   = pred_xy + pred_wh_half

    intersect_mins  = tf.maximum(pred_mins,  true_mins)
    intersect_maxes = tf.minimum(pred_maxes, true_maxes)
    intersect_wh    = tf.maximum(intersect_maxes - intersect_mins, 0.)
    intersect_areas = intersect_wh[..., 0] * intersect_wh[..., 1]

    true_areas = true_wh[..., 0] * true_wh[..., 1]
    pred_areas = pred_wh[..., 0] * pred_wh[..., 1]

    union_areas = pred_areas + true_areas - intersect_areas
    iou_scores  = tf.truediv(intersect_areas, union_areas)

    best_ious = tf.reduce_max(iou_scores, axis=4)
    conf_mask = conf_mask + tf.compat.v1.to_float(best_ious < 0.6) * (1 - y_true[..., 4]) * NO_OBJECT_SCALE

    # penalize the confidence of the boxes, which are reponsible for corresponding ground truth box
    conf_mask = conf_mask + y_true[..., 4] * OBJECT_SCALE

    ### class mask: simply the position of the ground truth boxes (the predictors)
    class_mask = y_true[..., 4] * tf.gather(CLASS_WEIGHTS, true_box_class) * CLASS_SCALE

    """
    Warm-up training
    """
    no_boxes_mask = tf.compat.v1.to_float(coord_mask < COORD_SCALE/2.)
    seen = tf.compat.v1.assign_add(seen, 1.)

    true_box_xy, true_box_wh, coord_mask = tf.cond(tf.less(seen, WARM_UP_BATCHES),
                          lambda: [true_box_xy + (0.5 + cell_grid) * no_boxes_mask,
                                   true_box_wh + tf.ones_like(true_box_wh) * np.reshape(ANCHORS, [1,1,1,BOX,2]) * no_boxes_mask,
                                   tf.ones_like(coord_mask)],
                          lambda: [true_box_xy,
                                   true_box_wh,
                                   coord_mask])

    """
    Finalize the loss
    """
    nb_coord_box = tf.reduce_sum(tf.compat.v1.to_float(coord_mask > 0.0))
    nb_conf_box  = tf.reduce_sum(tf.compat.v1.to_float(conf_mask  > 0.0))
    nb_class_box = tf.reduce_sum(tf.compat.v1.to_float(class_mask > 0.0))

    loss_xy    = tf.reduce_sum(tf.square(true_box_xy-pred_box_xy)     * coord_mask) / (nb_coord_box + 1e-6) / 2.
    loss_wh    = tf.reduce_sum(tf.square(true_box_wh-pred_box_wh)     * coord_mask) / (nb_coord_box + 1e-6) / 2.
    loss_conf  = tf.reduce_sum(tf.square(true_box_conf-pred_box_conf) * conf_mask)  / (nb_conf_box  + 1e-6) / 2.
    loss_class = tf.nn.sparse_softmax_cross_entropy_with_logits(labels=true_box_class, logits=pred_box_class)
    loss_class = tf.reduce_sum(loss_class * class_mask) / (nb_class_box + 1e-6)

    loss = loss_xy + loss_wh + loss_conf + loss_class

    nb_true_box = tf.reduce_sum(y_true[..., 4])
    nb_pred_box = tf.reduce_sum(tf.compat.v1.to_float(true_box_conf > 0.5) * tf.compat.v1.to_float(pred_box_conf > 0.3))

    """
    Debugging code
    """
    current_recall = nb_pred_box/(nb_true_box + 1e-6)
    total_recall = tf.compat.v1.assign_add(total_recall, current_recall)

    loss = tf.compat.v1.Print(loss, [tf.zeros((1))], message='Dummy Line \t', summarize=1000)
    loss = tf.compat.v1.Print(loss, [loss_xy], message='Loss XY \t', summarize=1000)
    loss = tf.compat.v1.Print(loss, [loss_wh], message='Loss WH \t', summarize=1000)
    loss = tf.compat.v1.Print(loss, [loss_conf], message='Loss Conf \t', summarize=1000)
    loss = tf.compat.v1.Print(loss, [loss_class], message='Loss Class \t', summarize=1000)
    loss = tf.compat.v1.Print(loss, [loss], message='Total Loss \t', summarize=1000)
    loss = tf.compat.v1.Print(loss, [current_recall], message='Current Recall \t', summarize=1000)
    loss = tf.compat.v1.Print(loss, [total_recall/seen], message='Average Recall \t', summarize=1000)

    return loss

For me Python crashes when I use this line:
from tensorflow.python.framework.ops import disable_eager_execution disable_eager_execution()
and this also doesn't help:
yolo_model.compile(loss=custom_loss, optimizer=optimizer, run_eagerly=False)
Using tensorflow.keras instead of keras also doesn't help unfortunately, did you do anything additionaly to those steps described?
The Error I get is also

TypeError: Cannot convert a symbolic Keras input/output to a numpy array. This error may indicate that you're trying to pass a symbolic value to a NumPy call, which is not supported. Or, you may be trying to pass Keras symbolic inputs/outputs to a TF API that does not register dispatching, preventing Keras from automatically converting the API call to a lambda layer in the Functional Model.


What messages cause rpc_result to be sent back?

https://core.telegram.org/mtproto/service_messages#response-to-an-rpc-query
Looking here rpc_result has a result of type Object, I was wondering what messages cause an rpc_result to be sent back, are only a subset of calls considered 'RPC queries' and if so how can I see what this subset consists of?

All functions require response from the server. Functions have separate section in TL-scheme.

All functions require response from the server. Functions have separate section in TL-scheme.

I presume this doesn't include basic mtproto functions like req_pq, req_DH_params and set_client_DH_params since they don't give me rpc_result? So other than those, all other functions will give me an rpc_result?

I presume this doesn't include basic mtproto functions like req_pq, req_DH_params and set_client_DH_params since they don't give me rpc_result? So other than those, all other functions will give me an rpc_result?

Those are requests sent before auth_key is created. They are not related in any way to ordinary MTProto usage phase.

Those are requests sent before auth_key is created. They are not related in any way to ordinary MTProto usage phase.

Thanks!

Thanks!


Revised comparison relational operator articles

Supported by dotnet/samples#523

closing and reopening to start a new build.


Decorfloor - The job location is "Romania" instead of "Bucharest"

ENVIRONMENT: production
URL: https://solr.peviitor.ro
Browser: Microsoft Edge
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:

Open the URL in the browser
Execute Query for "Decorfloor" Company
Check the jobs location
Open https://decorfloor.ro/careers
Check the jobs location

EXPECTED RESULTS:
The job location is "Bucharest" as on the company's website
ACTUAL RESULTS:
The job location is "Romania" instead of "Bucharest"
On the scrapers.peviitor.ro the message "Romania is not a city in Romania" is displayed

Decât un singur job are afișata locația celelalte 2 le-am trecut în Cluj și București unde are firma sediul.


Installing from pip results in ImportError

From googling around on this issue, it seems like setup.py needs to be tweaked to include distribute_setup.py in the source distribution.
$ pip install --upgrade django-exceptional

Downloading/unpacking django-exceptional
  Downloading django-exceptional-0.1.4.tar.gz
  Running setup.py egg_info for package django-exceptional
    Traceback (most recent call last):
      File "<string>", line 14, in <module>
      File "/project/build/django-exceptional/setup.py", line 7, in <module>
        from distribute_setup import use_setuptools
    ImportError: No module named distribute_setup
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):

  File "<string>", line 14, in <module>

  File "/project/build/django-exceptional/setup.py", line 7, in <module>

    from distribute_setup import use_setuptools

ImportError: No module named distribute_setup

I have this issue also, running on Heroku and unable to install any other way.
Any idea if there is a quick fix for this?

I've seen the error mentioned above too. The quick solution for me was:
wget https://github.com/zacharyvoase/django-exceptional/zipball/master -O django-exceptional.zip
pip install django-exceptional.zip

My pull request (#11) should resolve this issue.

I tried the latest http://pypi.python.org/pypi/django-exceptional (0.1.5) and the issue is resolved:
(python2.7)django-exceptional $ pip install --upgrade django-exceptional
Downloading/unpacking django-exceptional
  Downloading django-exceptional-0.1.5.tar.gz
  Running setup.py egg_info for package django-exceptional

Installing collected packages: django-exceptional
  Running setup.py install for django-exceptional

Successfully installed django-exceptional
Cleaning up...


feat: positivity extension for the coercion ℝ → ℂ

From LeanAPAP

I think it does not really matter (as in it won't show up in practice), but mostly I'm not sure how to avoid duplicating the entire positivity extension. I know you make a positivity extension trigger on different inputs, but the match inside would still only work for one of them. @hrmacbeth, do you have advice for me here?

I just went along and tried that. There's basically no use of zero_le_real/zero_lt_real in mathlib and no use of ofReal_ne_zero that has ComplexOrder open (so positivity fails, since it needs a PartialOrder instance on every type). The solution to make this more applicable would be to have the nonzeroness tactic mentioned at @urkud's Rutgers talk.


How can l test the connection migration?

Thanks for your contribution @tbarbette
Can you tell me how to test the connection migration?

Do you mean QUIC connection migration, ie over multipath?  This is not supported for now. If you refer to the previous work of Haoran Yao (https://www.diva-portal.org/smash/get/diva2:1539441/FULLTEXT01.pdf) this is transparent server based migration, so the client is not aware.


Actually skip pages included in the skipPages array when running tests, rather than creating empty 1x1 canvases (issue 8241)

Considering how extremely simple this patch turned out to be, I'm almost worried that I completely misunderstood why the current code looks like it does...
Fixes #8241.

/botio test

I share the confusion about the current code. I really don't see why creating 1x1 empty canvases would be useful. If @brendandahl agrees with this patch, you have my blessing for this as well.

Hmm, I'm not sure what's up with the one "failure" in Chrome on Linux, since everything looks fine...
/botio-linux test

Based on test-run in https://github.com/mozilla/pdf.js/pull/3891#issuecomment-292478504, it seems that there are intermittent failures in Chrome master as well, so at least it doesn't look like the failures are caused by this PR.

Based on the test-run in https://github.com/mozilla/pdf.js/pull/3891#issuecomment-292478504, it seems that there are intermittent failures in Chrome on master as well, so at least it doesn't look like the failures are caused by this PR.


showInThread is working only for first channel

when we are passing more then one channels, showInThread is working only for first channel for other channel failure details shown in main channel instead thread

thanks reporting @Rajkumar502 , I will fix this.

Fixed in https://github.com/ryanrosello-og/playwright-slack-report/pull/52


Race condition causes items to be added twice

When populating the list from remote content, sometimes the callback passed to getCandidates gets called twice in a row so we end up with duplicated items in the list. I suppose the chance of this happening is higher when the server is a bit slow to respond, which is why you didn't notice it.
For instance I'm looking for items containing the word "house" so I decide to type the letters h, o, u and s. What's happening is that I have the time type the letter s before the request for "hou" has completed, so when the keyUp handler handles the s key the list is still empty. After I've typed s, the browser receives responses for both "hou" and "hous" and calls the callback twice with the same results, which causes them to be added twice to the list.
Adding a call to typeAhead.list.clear(); before https://github.com/marcojetson/type-ahead.js/blob/master/src/type-ahead.js#L77 seems to fix it.

Clearing the list may look like a fix but the problem is that the requests are asynchronous and you cannot guarantee the order of the responses. In your example "hou" and "hous" return the same results but they may return different ones.
In your getCandidates implementation you should abort any previous request. I think the library should provide a clearer way to see this, like an onBeforeGetCandidates event or something similar.
I will also update the examples using remote.

Oh right, I didn't think about that.