Add I2S driver for LPC devices

Add I2S driver for LPC devices. This PR was tested using the tests inside tests/drivers/i2s.
The LPC DMA driver was also updated to improve DMA efficiency.
The tests were updated to account for loopback over separate I2S ports versus the same port. The default setting for the tests should have the original behavior.

NOTE:

I am unable to pass the below test in test_i2s_states.c.

/** @brief Verify all failure cases in RUNNING state.
*
* - Sending START, PREPARE trigger in RUNNING state returns failure.
*/
void test_i2s_state_running_neg(void)

I think it is an issue with the test as the test is underflowing resulting in the I2S TX Channel to not be in the RUNNING state.

I am seeing an MPU Fault – Data Access Violation when running the tests in user mode, test code below:

              /* Now run all tests in user mode */
              ztest_test_suite(i2s_user_loopback_test,
                                           ztest_user_unit_test(test_i2s_tx_transfer_configure_0),
                                           ztest_user_unit_test(test_i2s_rx_transfer_configure_0),
                                           ztest_user_unit_test(test_i2s_transfer_short),
                                           ztest_user_unit_test(test_i2s_transfer_long),
                                           ztest_user_unit_test(test_i2s_rx_sync_start),
                                           ztest_user_unit_test(test_i2s_rx_empty_timeout),
                                           ztest_user_unit_test(test_i2s_transfer_restart),
                                           ztest_user_unit_test(test_i2s_transfer_tx_underrun),
                                           ztest_user_unit_test(test_i2s_transfer_rx_overrun));
              ztest_run_test_suite(i2s_user_loopback_test);

              ztest_test_suite(i2s_user_states_test,
                                           ztest_user_unit_test(test_i2s_tx_transfer_configure_1),
                                           ztest_user_unit_test(test_i2s_rx_transfer_configure_1),
                                           ztest_user_unit_test(test_i2s_state_not_ready_neg),
                                           ztest_user_unit_test(test_i2s_state_ready_neg),
                                           ztest_user_unit_test(test_i2s_state_running_neg),
                                           ztest_user_unit_test(test_i2s_state_stopping_neg),
                                           ztest_user_unit_test(test_i2s_state_error_neg));
              ztest_run_test_suite(i2s_user_states_test);

cc @hakehuang

Is there a use case for I2S Tx or Rx only?

Yes, I think so.

Is there a use case for I2S Tx or Rx only?

Yes,   I2S DMICs.

Anything else needed for this PR?

Looks good overall. Most of my comments are suggestions, few are real issues.
Could you improve "drivers: dma: Update the LPC DMA driver " commit message. It's not clear what has changed and why.
I haven't finished testcase review yet.

I have the below in the commit message:
    1. Update the SDK API's called in the configure implementation
    2. Update the dma_reload implementation

I have the below in the commit message:
    1. Update the SDK API's called in the configure implementation
    2. Update the dma_reload implementation

Yes, it is not clear why the changes were required and how this new implementation is better than the old one. One would need to review the diff to understand what has changed.

I have the below in the commit message:
    1. Update the SDK API's called in the configure implementation
    2. Update the dma_reload implementation

Yes, it is not clear why the changes were required and how this new implementation is better than the old one. One would need to review the diff to understand what has changed.

Got, I have updated the commit message. The I2S tests were failing due to the incorrect DMA implementation.

I am unclear why the build is failing.

Let's make the following changes to the title line of the following commits:
"tests: i2s: Update I2S loopback tests" -> "tests: i2s: Update i2s_api test"
"tests: i2s: Update I2S State test" -> "tests: i2s: Fix i2s_states_test test suite"
And remove from the commit messages mentions of Kconfig option to configure ports as master or slave.

Done

@galak @mnkp please revisit

API meeting 2021.03.23:

No firm conclusion, though options would be:

Add a format parameter of sorts to the config function, or a function that returns the required sample size in bytes
Treat the read/write functions in this driver as device-specific and so add i2s_lpc_read/write

Reach out to the SoF folks to try and see how common this occurrence may be

@mwasko @marc-hb fyi
Generally I2S IP also supports TDM and PCM audio formats. This means the config structure has to be able to cope with more than just I2S and should be capable to describe a TDM hardware data format. e.g. the config should be able to

Set rate for MCLK, BCLK and FRAME.
set clock providers for MCLK, BCLK and FRAME.
Set the frame size, num channels, sample valid bits (as this can be less than (frame size / num channels)).
TDM valid slots for tx and rx.
timing between FRAME being asserted wrt BCLK and data MSB. e.g. is MSB sent as FRAME is asserted or N BCLKs after. This is usually defined by a mode e.g. DSP_A, DSP_B, I2S_LEFT_JUSTIFIED etc.
Some space for flags and quirks specific to IP.

i.e from SOF general DAI (digital audio interface) config with the Intel SSP IPC config (specific to Intel SSP)

/*
 * DAI Configuration.
 *
 * Each different DAI type will have it's own structure and IPC cmd.
 */

#define SOF_DAI_FMT_I2S		1 /**< I2S mode */
#define SOF_DAI_FMT_RIGHT_J	2 /**< Right Justified mode */
#define SOF_DAI_FMT_LEFT_J	3 /**< Left Justified mode */
#define SOF_DAI_FMT_DSP_A	4 /**< L data MSB after FRM LRC */
#define SOF_DAI_FMT_DSP_B	5 /**< L data MSB during FRM LRC */
#define SOF_DAI_FMT_PDM		6 /**< Pulse density modulation */

#define SOF_DAI_FMT_CONT	(1 << 4) /**< continuous clock */
#define SOF_DAI_FMT_GATED	(0 << 4) /**< clock is gated */

#define SOF_DAI_FMT_NB_NF	(0 << 8) /**< normal bit clock + frame */
#define SOF_DAI_FMT_NB_IF	(2 << 8) /**< normal BCLK + inv FRM */
#define SOF_DAI_FMT_IB_NF	(3 << 8) /**< invert BCLK + nor FRM */
#define SOF_DAI_FMT_IB_IF	(4 << 8) /**< invert BCLK + FRM */

#define SOF_DAI_FMT_CBP_CFP	(0 << 12) /**< codec bclk provider & frame provider */
#define SOF_DAI_FMT_CBC_CFP	(2 << 12) /**< codec bclk consumer & frame provider */
#define SOF_DAI_FMT_CBP_CFC	(3 << 12) /**< codec bclk provider & frame consumer */
#define SOF_DAI_FMT_CBC_CFC	(4 << 12) /**< codec bclk consumer & frame consumer */

#define SOF_DAI_FMT_FORMAT_MASK		0x000f
#define SOF_DAI_FMT_CLOCK_MASK		0x00f0
#define SOF_DAI_FMT_INV_MASK		0x0f00
#define SOF_DAI_FMT_CLOCK_PROVIDER_MASK	0xf000

/** \brief Types of DAI */
enum sof_ipc_dai_type {
	SOF_DAI_INTEL_NONE = 0,		/**< None */
	SOF_DAI_INTEL_SSP,		/**< Intel SSP */
	SOF_DAI_INTEL_DMIC,		/**< Intel DMIC */
	SOF_DAI_INTEL_HDA,		/**< Intel HD/A */
	SOF_DAI_INTEL_ALH,		/**< Intel ALH */
	SOF_DAI_IMX_SAI,                /**< i.MX SAI */
	SOF_DAI_IMX_ESAI,               /**< i.MX ESAI */
};

/* general purpose DAI configuration */
struct sof_ipc_dai_config {
	struct sof_ipc_cmd_hdr hdr;
	uint32_t type;		/**< DAI type - enum sof_ipc_dai_type */
	uint32_t dai_index;	/**< index of this type dai */

	/* physical protocol and clocking */
	uint16_t format;	/**< SOF_DAI_FMT_ */
	uint8_t group_id;	/**< group ID, 0 means no group (ABI 3.17) */
	uint8_t reserved8;	/**< alignment */

	/* reserved for future use */
	uint32_t reserved[8];

	/* HW specific data */
	union {
		struct sof_ipc_dai_ssp_params ssp;
		struct sof_ipc_dai_dmic_params dmic;
		struct sof_ipc_dai_hda_params hda;
		struct sof_ipc_dai_alh_params alh;
		struct sof_ipc_dai_esai_params esai;
		struct sof_ipc_dai_sai_params sai;
	};
} __attribute__((packed));

/* SSP Configuration Request - SOF_IPC_DAI_SSP_CONFIG */
struct sof_ipc_dai_ssp_params {
	uint32_t reserved0;
	uint16_t reserved1;
	uint16_t mclk_id;

	uint32_t mclk_rate;	/* mclk frequency in Hz */
	uint32_t fsync_rate;	/* fsync frequency in Hz */
	uint32_t bclk_rate;	/* bclk frequency in Hz */

	/* TDM */
	uint32_t tdm_slots;
	uint32_t rx_slots;
	uint32_t tx_slots;

	/* data */
	uint32_t sample_valid_bits;
	uint16_t tdm_slot_width;
	uint16_t reserved2;	/* alignment */

	/* MCLK */
	uint32_t mclk_direction;

	uint16_t frame_pulse_width;
	uint16_t tdm_per_slot_padding_flag;
	uint32_t clks_control;
	uint32_t quirks;
	uint32_t bclk_delay;	/* guaranteed time (ms) for which BCLK
				 * will be driven, before sending data
				 */
} __attribute__((packed));

Thanks @lgirdwood for a detailed explanation. The problem here is more specific. When we send audio data to the I2S driver we place it in a large buffer and pass to the driver using one system call. So far the I2S API assumed that the data are always packed in an optimum way. E.g. an 8-bit sample will require one byte of storage, that is to send 16 8-bit samples we will need a buffer of size 16. However, the LPC driver in this PR is not able to cope with such data. Its DMA engine can do 32-bit transfers only. It can transfer one 32-bit sample or two 16-bit samples at minimum.
We were wondering how such hardware limitations are dealt with in case of SOF. Does the application need to query the data layout supported by the driver? You only support one specific data layout?
ALSA library has snd_pcm_format_physical_width() function which lets the application figure out the sizeof a single data sample.

Thanks @lgirdwood for a detailed explanation. The problem here is more specific. When we send audio data to the I2S driver we place it in a large buffer and pass to the driver using one system call.

I would just pass the pointer and bytes in this call (we do). The DMA and I2S are configured with other calls first as this allows for continuous playback..
So far the I2S API assumed that the data are always packed in an optimum way. E.g. an 8-bit sample will require one byte of storage, that is to send 16 8-bit samples we will need a buffer of size 16. However, the LPC driver in this PR is not able to cope with such data. Its DMA engine can do 32-bit transfers only. It can transfer one 32-bit sample or two 16-bit samples at minimum.

We were wondering how such hardware limitations are dealt with in case of SOF. Does the application need to query the data layout supported by the driver? You only support one specific data layout?

The HW link formats are defined in the pipeline topology and programmed by the DAI drivers when streams are in use. This can also mean the pipeline will react to use case input format from a media player and align this format with the I2S configuration (i.e. via SRC or format conversion).
Generally, if an application tries to open a PCM device where the HW format is incompatible with the HW AND no conversion is possible we will fail.

ALSA library has snd_pcm_format_physical_width() function which lets the application figure out the sizeof a single data sample.

We have something similar to ALSA (disclaimer: I'm also an ALSA developer) in that we frame_size parameter for the audio PCM data that corresponds to the number of channels * sample size (frame_format) e.g.
/* stream PCM frame format */
enum sof_ipc_frame {
	SOF_IPC_FRAME_S16_LE = 0,
	SOF_IPC_FRAME_S24_4LE,
	SOF_IPC_FRAME_S32_LE,
	SOF_IPC_FRAME_FLOAT,
	/* other formats here */
};

i.e. Stereo S24_4LE is 2 * 4 bytes = 8 bytes frame size.  Please note we dont have 8bit formats, this would sound terrible. 16 bit stereo is pretty much the default supported by all codec HW.
This is all that is needed for copying data from memory to memory (i.e. host to DSP). To copy data to peripherals over TDM, PCM or I2S protocols you also need to include a HW frame_size which may be larger that the PCM data frame size (i.e. we have I2S running with 64BCLKs per FRAME for stereo 16bit PCM will mean the link will have 16 unused BCLKs for L and R - HW frame_size is 64 and PCM frame_size is 32..

I would just pass the pointer and bytes in this call (we do). The DMA and I2S are configured with other calls first as this allows for continuous playback..

@lgirdwood So you mean something like:
static inline int i2s_write(const struct device *dev, void *mem_block, size_t size, size_t sample_size)

where sample_size is either 8-bit or 16-bit?
The main question we are trying to deal with is how to communicate to the driver the format that the data is provided in (eg. for 8-bit samples, whether they all come packed together or each is placed in a 16-bit word in memory), or, alternatively, communicate to the application what format the driver expects. In the former, the driver would fail if the sample_size is set to a value not supported by the hardware, in the latter the driver would "trust" that the application has provided the data in the right format.

@lgirdwood So you mean something like:
static inline int i2s_write(const struct device *dev, void *mem_block, size_t size, size_t sample_size)

where sample_size is either 8-bit or 16-bit?

Better to configure sample format in another I2S  API call before you call this write(). I would probably use ALSA API for guidance here e.g.
https://www.alsa-project.org/alsa-doc/alsa-lib/group___p_c_m.html#gabc748a500743713eafa960c7d104ca6f
Btw, ALSA has two flavors of write() -  blocking and non blocking. I'm assuming your version will block ? I'm also assuming that your API is not using DMA and directly programming the audio data to the I2S port FIFO ? (otherwise it's better to use a circular audio buffer).

@mnkp I have rebased and updated this PR to address all pending issues. Should we add a separate issue for the new I2S API.

Thanks, looks good. I still have some comments though.
I propose to rearrange commits a bit. I think we could squash all the following three commits into one:

soc: Add I2S support for MXRT600
drivers: i2s: Add support for I2S driver for LPC devices
drivers: i2s: Update LPC I2S Flexcomm driver for DMA

since the driver will not work without SoC support, and the update to the 2 DMA descriptors for RX is an integral part of the driver.
Also we need to make sure that the commit updating the DMA driver is placed in git history before the commit introducing I2S driver.

I have rearranged the commits and squashed the driver folder commits. I would prefer to keep the soc folder commit separate as I have separate commits per folder.

@mnkp @galak The build is failing with the below message
 DT_INST_FOREACH_STATUS_OKAY(I2S_MCUX_FLEXCOMM_DEVICE)
      |             ^~~~~~~~~~~~~~~~~~~~~
/workdir/zephyr/drivers/i2s/i2s_mcux_flexcomm.c:919:13: error: Macro is deprecated [-Werror]

What do you recommend I use in place of DT_INST_FOREACH_STATUS_OKAY

This is probably due to device_pm_control_nop now being deprecated. See #34682

@mnkp @galak The build is failing with the below message
 DT_INST_FOREACH_STATUS_OKAY(I2S_MCUX_FLEXCOMM_DEVICE)
      |             ^~~~~~~~~~~~~~~~~~~~~
/workdir/zephyr/drivers/i2s/i2s_mcux_flexcomm.c:919:13: error: Macro is deprecated [-Werror]

What do you recommend I use in place of DT_INST_FOREACH_STATUS_OKAY

This is probably due to device_pm_control_nop now being deprecated. See #34682

Thank you.

@mnkp I think I have addressed all comments, can you please check.


Help

Filling the help page would make it easier for users to use the bot properly

For this, the help.json is already uploaded!


Add Reflection to support custom Spark Implementation at Runtime

Signed-off-by: Ahmed Hussein<EMAIL_ADDRESS>Fixes #1360
Adds a workaorund to run against open source Spark and custom Spark implementation that overrides the constructors of Graph objects.
This PR also should improve performance on Databricks environment.
Before the change, we used to try to call normal Spark API, then catch the java exception, finally load the constructor method and call it with correct arguments.
After the change, the tools detects the runtime, and uses reflection everytime to call the constructor. This way, it reduces the overhead on each object allocation.

When using the python tools CLI, we download the open source Spark and provide that to the JAR tool. This will happen even if are running the tools inside Databricks env.
In that case, do we need a follow up on python side to use custom runtime jars instead of open source Spark?

We have the issue https://github.com/NVIDIA/spark-rapids-tools/issues/1359 to allow customers to specify their own dependency.
The open source works fine in DB. So, we can leave it as it now.
The trick with setting the dependencies for each individual CSP is that we have to redefine the yaml configuration assuming the user is running on a cluster node and for each one, set the path of the SPARK jars on the local disk.
Currently, we do not need to do all that unless we learn that it affects the QualX significantly (which does not at the moment)


Specified values for fields "Name" and  "PhysicalContext" in Voltages

In profiles the values for fields "Name" and  "PhysicalContext" in Votages are provided,
"Voltages": [
			    {
				    "PropertyRequirements": {
					    "Name": "VRM1 Voltage",
					    "SensorNumber": {},
					    "Status": {},
				    	"ReadingVolts": {},
					    "PhysicalContext": "VoltageRegulator"
				    }
			    }
		    ],

Should those values be specified?

Yes, they are specific.  One of the reasons the Power and Thermal model are being deprecated from PowerSubsystem and ThermalSubsystem.  The proposed baseline1.1 updates the baseline with PowerSubsystem and ThermalSubsystem - #50

I see, so the merge will resolve the issue.

I may have read the issue incorrectly.  The values should be specified in the response from the managed node.  This means that the Voltages array object should have an element whose Name and Physical Context properties have the values specified.  The profile syntax is clunky when prescribing array elements.

Fixed in v1.0.3

Hi, @jcleung5549
I think we are still not on the same page, when in comes to this issue. The validator still returns an error, because the Voltage field has specified values for fields "Name" and "PhysicalContext". I understand, that the values for the fields are required specific, but I think it should be done differently - setting "Values" property, as done below:
"Voltages": {
          "PropertyRequirements": {
             "Name": {
              "Values": [
                "VRM1 Voltage"
              ]
            },
             "SensorNumber": {},
             "Status": {},
             "ReadingVolts": {},
             "PhysicalContext": {
              "Values": [
                "VoltageRegulator"
              ]
            }
          }
	},


Add support for Python 3.7

Add support for Python 3.7, which needs Xenial and sudo on Travis CI (https://github.com/travis-ci/travis-ci/issues/9815).

Upgraded Python syntax with pyupgrade.

MIght as well change the syntax; we don't support 2.6 anymore. Thanks!


My esp32 HW-607 can no longer be programmed after using this library.

Hi, I recently programmed my esp32 with the imageFromWiFi example from this library, it loads fine without any problem. The problem already arises when I want to use another code or modify the existing one, it does not recognize the BOOT button that is necessary for the esp32 to receive the new code.
At first I thought it was the hardware so I switch to another new esp32 I test it with another code and it works fine, when I go back into the imageFromWiFi example and compile it, the same thing happens to me again.
I need help with this problem as I have 2 useless esp32s.
I share the URL that shows us the configuration of the esp32 pins.
https://blog.robberg.net/esp32/

problema resuelto.....


Disable torcx on boot time

Hi,
I'm trying the new 1492.1.0 alpha since I had problems running stable and beta on our Xenserver 7.1 (NMI problem) to setup a k8s test cluster.
I'm running the coreos installer with the cloudconfig I used before, but when I need to restart dockerd with systemd it fails with the following message:
Aug 03 10:03:15 nestene systemd[1]: Starting Docker Application Container Engine...
Aug 03 10:03:15 nestene env[5633]: /usr/bin/env: '/run/torcx/bin/dockerd': No such file or directory
Aug 03 10:03:15 nestene systemd[1]: docker.service: Main process exited, code=exited, status=127/n/a
Aug 03 10:03:15 nestene systemd[1]: Failed to start Docker Application Container Engine.

Is there a simple way to disable torcx or to fix this ?
Thanks

I'm not able to reproduce this on the same alpha version as yours. However, this is not the right place for issue investigation. Can you please report this failure at https://github.com/coreos/bugs/issues and includes all of the following:

your (redacted) clouconfig
 sudo journalctl -b 0 -t /usr/lib64/systemd/system-generators/torcx-generator
sudo systemctl status docker
sudo ls -lah /run/torcx/**
cat /run/metadata/torcx
cat /run/torcx/profile.json

The output of those can be quite big, feel free to attach them via a gist/pastebin (and make sure to redact sensitive info).
I'm now going to close this ticket but I will folllow up your report on coreos/bugs, feel free to cc me there once done.


Fix absolute path expressions

Can you add the following tests:

input: document-node{<!--comment--><element/>} -> preceding::node() of element should be the comment and following-sibling::node of comment should be element.
input: document-node{<element/>} -> ancestor-or-self:node() of element should be both element and the document node

That way we can cover this new behaviour since the QT3 tests don't appear to cover them


unpacked problem

Executing memory patches...
Initializing modules...
Processing...
Cleanup...
Applied patches:
StringFixer: Success
ResourceResolver: Failed (Init error: Could not find resolver type)
AssemblyResolver: Failed (值不能为 null。
参数名: source)
Writing new assembly...
Done.

Please follow the bug report template.


[Feature][Plugin] New plugin for Gitea

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Gitea is an open-source software package for hosting software development version control using Git as well as other collaborative features like bug tracking, code review, kanban boards, tickets, and wikis.
Use case
Gitea plugin
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thanks for your contribution!

It seems it's still under development


Remove/rewrite superjson

Problem: too big json data on client. This is the result of Date serialization from SSR. Diff btw SSR and CSR 200+ ms in TFP. This is the big performance issue.
Experiment #1728

https://github.com/taskany-inc/issues/tree/custom-transformer


24 FPS support for filmmaking use case

It looks like Intel is now interested in promoting filmmaking as a use case for the RealSense cameras:
https://support.intelrealsense.com/hc/en-us/community/posts/360035016413-RealSense-technology-and-the-Ncam-Mk2-Camera-Bar
Will they provide support for it but adding industry standard framerates like 24 FPS?
Previously they said it was possible to add through firmware, but it would be too confusing for developers to add another enumeration to the SDK.
https://github.com/IntelRealSense/librealsense/issues/2865
If they are now promoting this they should seriously reconsider.

Hi @sam59
People have been talking about 24 fps support.
There are actually several frame rates: 24 FPS, 23.98 FPS and 25 FPS.
Could you please elaborate what is the frame rate you are looking for and what is your application?
We are gathering the feedback and scoping the effort.
Thanks,

23.98 is the most common framerate used for film, television and streaming production right now.
24.00 is an older standard that comes from celluloid film cameras. 25.00 is a standard framerate sometimes used in Europe and Asia.
23.98 would be my recommendation as it would get the most use from filmmakers, and allow the RealSense cameras to be used in film and television production.
As for my own use case, I am developing a small light field camera using an array of RealSense devices.

Hi @sam59
Thanks for the great feedback!

We will implement this, but the schedule is not available at this moment yet.

@RealSenseCustomerSupport Thank you for the update, very exciting news!
If you need someone to beta test the firmware I would be very interested., I would be able to test it with a multicamera RealSense setup, and I am also ready to test syncronization with external 3rd party cinema cameras.

Hi @Hi @sam59 Could you please confirm the 24 fps request is for depth camera, right? Not RGB camera.

The priority is the depth camera. Is there an issue getting the RGB camera to run at 23.98fps as well?
If it is not possible to get the RGB camera to run in sync, the depth camera can still be synchronized with an external camera running at 23.98.
However having the RGB color run at the same framerate would greatly increase the usability of the device, and reduce the complexity and cost for end users.

@sam59 we just released a new feature we call Genlock. It allows you to make our cameras slave to almost any external signal, so you can get your 23.98fps for example. Please check it out and see if it will work for you.
https://www.intelrealsense.com/depth-camera-external-sync-trigger/

@sam59 Do you have a chance to try out the Genlock? Is there any issue?

@sam59 Do you have a chance to try out the new Genlock feature?


Added  "Get all the available earnings data of a specific symbol" Function

Codecov Report

Merging #28 into master will decrease coverage by 6.96%.
The diff coverage is 14.28%.

@@           Coverage Diff           @@
##           master   #28      +/-   ##
=======================================
- Coverage   81.96%   75%   -6.97%
=======================================
  Files           2     2
  Lines          61    68       +7
=======================================
+ Hits           50    51       +1
- Misses         11    17       +6

Impacted Files
Coverage Δ

yahoo_earnings_calendar/scraper.py
74.62% <14.28%> (-7.04%)
:arrow_down:

Continue to review full report at Codecov.

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

Thanks @dkadyrov !


Corpus integration?

just a feature suggestion; would be useful for someone learning arabic to have each word linked to the correponding corpus link (eg first word of http://quran.com/1:1 to http://corpus.quran.com/wordmorphology.jsp?location=(1:1:1)). Maybe linked via the translation tooltip?

Salam!
We do get this data in the api, just not using it unfortunately. We just need to figure out how to present it.

What about when adding the users portal, there could be an option to enable an "advanced interface "for people who want multiple tafaseer in arabic and english + grammar information shown ?

Great idea! Let's add this as an option for the cookie first? Then with user auth we can go deeper?

Agreed. I think releasing tafaseer is a higher priority than the corpus display. However maybe they should be activated from the same place & API route? =)


NIC Driver binding refactoring

moves uio_hv_generic out of the binding function, hoists it to the initialization function above.
The enabling function now checks whether the driver has been loaded or not, it only loads it if it has been loaded already.

moves uio_hv_generic out of the binding function, hoists it to the initialization function above. The enabling function now checks whether the driver has been loaded or not, it only loads it if it has been loaded already.

Please add the details in the commit message. The commit message is easier to view in code history.


add rehype-slug and rehype-prism to website

I highly encourage changing this.

Adds rehype-slug for consistent heading ids

Adds @mapbox/rehype-prism to highlight code blocks

Removes the need for prism-react-renderer and react-addons-text-content

Updates gatsby-mdx to v0.6 which introduces mdx v1

Thanks @BarryThePenguin! @Noviny could you please have a look over this and approve if you're happy with it.

Might this also fix https://github.com/keystonejs/keystone-5/issues/1271 ?

Might this also fix #1271 ?

Should do 👍 Adding rehype-slug aligns the TOC links with the generated slugs


Call to a member function prepare() on null when migrating

When I run php artisan tenancy:migrate, the first website migrated successfully, but the next one throws an exception :
ayoub:stock ayoubbougsid$ php artisan tenancy:migrate
Migrating: 2020_01_12_110036_add_variant_to_sell
Migrated:  2020_01_12_110036_add_variant_to_sell
Migrating: 2020_01_12_110036_add_variant_to_sell

In Connection.php line 452:

  Call to a member function prepare() on null

I tried to debug the internal code, but without success, couldn't figure out why this happening.

Can you provide more details?
Did you check the logs?

Closing this issue due to inactivity.
If you feel like your issue has not been properly addressed yet, or if you still need more information, please reopen this issue 😄
If you require help with a different issue, please open a new issue.
You can also find Tenancy related help & resources on:

Our Website
Our forums
Our Discord Server


Search sound effects and musics online

US: Game background sound and effects #89
PREREQUISITES:
None
GODOT:

Search for free copyright music for:

background music

Search for free copyright sound effects for:

clickable hexagon effect
clicked hexagon effect
clicked answer

BOUNDARIES:
1- What this task handles is to search and download music and sound effects for the game importing them also on godot project
OUTCOMES:
1- Music files in the godot project

When picked, discuss all the sounds you might need


Tasks 6 and 7 uploaded to Superposition Workbook

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

I brushed up presentation for task 6 a bit, will continue on task 7 tomorrow. One comment about the image Task6OutputHadamardasControl.png - could you please update it to say "flip" instead of "swap"? Swap is a two-qubit gate, and I'm worried that using it will confuse the reader instead of enlightening them...
Tagging @jimcristofono who authored the picture.


TypeException When Running with PyCharm Debugger

Hello qasync maintainers,
Love the library! I am running into an issue that I don't know if it's an issue with PyCharm or an issue with the library.  I figured I'd post here for insight.
When running a qasync application with the pycharm debugger, this exception is triggered right away, specifically the if not callable(callback) if-statemenet.
    def call_later(self, delay, callback, *args, context=None):
        """Register callback to be invoked after a certain delay."""
        if asyncio.iscoroutinefunction(callback):
            raise TypeError("coroutines cannot be used with call_later")
        if not callable(callback):
            raise TypeError(
                "callback must be callable: {}".format(type(callback).__name__)
            )

The example code:
import sys
import asyncio

from qasync import QEventLoop, QApplication, asyncClose, asyncSlot
from PySide6.QtWidgets import QWidget, QVBoxLayout, QLabel

class MainWindow(QWidget):
    def __init__(self):
        super().__init__()

        self.setLayout(QVBoxLayout())
        self.lbl_status = QLabel("Idle", self)
        self.layout().addWidget(self.lbl_status)

    @asyncClose
    async def closeEvent(self, event):
        pass

    @asyncSlot()
    async def onMyEvent(self):
        pass

if __name__ == "__main__":
    app = QApplication(sys.argv)

    event_loop = QEventLoop(app)
    asyncio.set_event_loop(event_loop)

    app_close_event = asyncio.Event()
    app.aboutToQuit.connect(app_close_event.set)

    main_window = MainWindow()
    main_window.show()

    with event_loop:
        event_loop.run_until_complete(app_close_event.wait())

To trigger the fault, inside pycharm run the debugger on this file.
For extra debug information:

python 3.11
pyside6-essentials 6.6.1
qasync 0.27.1

EDIT: Realized I didn't provide the full stack-trace, my apologies:
Connected to pydev debugger (build 233.13763.11)
Traceback (most recent call last):
  File "/Users/ogi/Developer/qasync-example/problem.py", line 37, in <module>
    event_loop.run_until_complete(app_close_event.wait())
  File "/Users/ogi/.pyenv/versions/doppkit/lib/python3.11/site-packages/qasync/__init__.py", line 394, in run_until_complete
    future = asyncio.ensure_future(future, loop=self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Applications/PyCharm.app/Contents/plugins/python/helpers-pro/pydevd_asyncio/pydevd_nest_asyncio.py", line 156, in ensure_future
    return loop.create_task(coro_or_future)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/ogi/.pyenv/versions/3.11.4/lib/python3.11/asyncio/base_events.py", line 436, in create_task
    task = tasks.Task(coro, loop=self, name=name, context=context)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Applications/PyCharm.app/Contents/plugins/python/helpers-pro/pydevd_asyncio/pydevd_nest_asyncio.py", line 390, in task_new_init
    self._loop.call_soon(self, context=self._context)
  File "/Users/ogi/.pyenv/versions/doppkit/lib/python3.11/site-packages/qasync/__init__.py", line 481, in call_soon
    return self.call_later(0, callback, *args, context=context)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/ogi/.pyenv/versions/doppkit/lib/python3.11/site-packages/qasync/__init__.py", line 459, in call_later
    raise TypeError(
TypeError: callback must be callable: Task
python-BaseException

This issue was introduced in PyCharm Debugger 2023.3.3.
It's caused by debugger hooks found in pydevd_nest_asyncio.py file, which monkey-patches the default asyncio.Task implementation (also used by qasync), resulting in this behaviour.
Rolling back to PyCharm 2023.2.5 fixes the issue.

I think the debugger works in a newer version, 2023.3.1, I believe the breakage started at 2023.3.2.  I'd be happy to open an issue in the pycharm bug tracker but I don't think I could explain the issue sufficiently (or in a way that won't make them point the finger back at this library).

Need to identify what's causing this behaviour and there's something qasync can do to avoid rasing an exception. Unfortunately I don't use pycharm so not able to reproduce this.

Need to identify what's causing this behaviour and there's something qasync can do to avoid rasing an exception. Unfortunately I don't use pycharm so not able to reproduce this.

Happy to try and drop into a debugger (heh) before the exception is raised and explore some, but I'm not sure what I should be looking for.

Hi guys, I can confirm what j9ac9k wrote. The breakage started with version 2023.3.2 and it also holds with version 2023.3.3

I think the debugger works in a newer version, 2023.3.1, I believe the breakage started at 2023.3.2. I'd be happy to open an issue in the pycharm bug tracker but I don't think I could explain the issue sufficiently (or in a way that won't make them point the finger back at this library).

Pycharm 2023.3.3 enabled asyncio support for the debugger, which was actually disabled before, even though the appropriate files were included with pydevd.
This issue at the JetBrains YouTrack platform actually describes the same problem happening with uvloop, another custom asyncio loop implementation.
At the current point, the only solution is to disable asyncio support for the debugger (which was disabled before in the first place, so It won't be a big loss for those who have only encountered the issue just now).
This can be done by following the steps described here.
In short:

Open PyCharm
Use Shift + Shift (Search Everywhere)
In the popup type: Registry... (with ...) and press Enter
Find Registry... in the list of results and click on it.
In the new popup find python.debug.asyncio.repl line and uncheck the respective checkbox
Press Close.
Restart the IDE.
PROFIT

Nice find on the existing issue elsewhere, it's a little disheartening that so many posts are about them not being able to replicate the issue.
Given there is a respective issue is already reported upstream, a workaround is posted, and this issue is present with another async library, I'm going to close out the issue.  Sorry for the noise, but thanks for pointing out the upstream issue @kormax

https://youtrack.jetbrains.com/issue/PY-62467
Upstream issue marked as fixed, but fixed version isn't specified... so assuming it it will be resolved in the next release?


Reverse stereo for oligomycin A

Hi
CHEBI:28285 cross-references KEGG:C11311 (and vice-versa) but the stereochemistry of both molecules looks inverted: front and back stereos are inverted.
KEGG:C11311 looks more similar to CHEBI:95353 but is not linked to that one.
So what is the right oligomycin A structure?

Hi,
The structures of all the oligomycins in ChEBI were recently updated and are now in agreement with crystallographic evidence. The structures of oligomycin A in ChEBI is in agreement with the X-ray crystal structure of this compound and I have also now added a 3D structure of this compound to this entry.
We map to other databases based on chemical names and InChi Keys and for this reason CHEBI:28285 has been mapped to KEGG C11311 entry. You will need to contact KEGG directly in order to update the structure in KEGG.

The structure found in CHEBI:95353 was loaded into CHEBI from the LINCS database. It seems that this particular structure has been deprecated in LINCS so I have marked this ChEBI entry as deleted.


Improve search status

Discord or Telegram handle
Discord: letu02#5055
Is your feature request related to a problem? Please describe.
Didn't know status of search DAO, only show status at bottom on tab Export
Describe the solution you'd like
Move search status to top of page

Thank you for the feedback, we will further discuss it here:

#78


move logic to settings creator

Responding to your comment here:

weird we are taking a SettingsCreator object, decomposing to a dict, only to then reconstruct a new SettingsCreator"

I agree.
We need to deal with two things - when settings come into the linker we:

'learn' about the sql_dialect (if not already set e.g. if loading from serialised .json)
'learn' about a linker_uid (if not already set)

The linker_uid is straightforward - if it doesn't exist, we create one.
The sql_dialect is more complex but I propose we don't deal with it in this PR or the requier_settings one.  I've put some TODOs here.
I think we need to decide:

Whether we support 'incompatible sql_dialects whatsoever (when the one specified in the settings is different to the db api)
If so, where is it dealt with.  e.g. should the settingscreator know about the existence of both and push the problem down to the ComparisonLevelCreator, BlockingRuleCreator etc.

If you agree with this approach, we can merge this all into splink4_dev and I'll create a separate issue for the above

If you agree with this approach, we can merge this all into splink4_dev and I'll create a separate issue for the above

Yeah sounds good to me.


BCnearest bug

Here's an minimal example. Sorry for the format:

1d linear interpolation + BCnearest extrapolation. Values higher than the grid look fine but values below the bottom value of the grid are all wrong.
Any suggestions?
Edit: Version 0.3.2 (2014-10-21 22:05 UTC)

Sorry for the slow response, and of course for the bug. I'm traveling now and for the next week, and am unlikely to have time to debug this myself anytime soon. It presumably comes down to a couple of functions in src/interp.jl. Do you know about @which? That should make it more straightforward to find the call chain.

Here's a self-contained example and some @which output. I hope this might help.
I have a hard time reading/understanding Julia polymorphism so I'm not sure which of the methods gets called next. Sorry!
julia> using Grid

julia> x = -1.0:0.2:1.0
-1.0:0.2:1.0

julia> y = vec([ 1.0 2.0 3.0 3.0 3.0 3.0 5.0 7.0 5.0 5.0 6.0 ])
11-element Array{Float64,1}:
 1.0
 2.0
 3.0
 3.0
 3.0
 3.0
 5.0
 7.0
 5.0
 5.0
 6.0

julia> ff = CoordInterpGrid(x, y, BCnearest, InterpLinear)
11-element CoordInterpGrid{Float64,1,BCnearest,InterpLinear,(FloatRange{Float64},)}:
 #undef
 #undef
 #undef
 #undef
 #undef
 #undef
 #undef
 #undef
 #undef
 #undef
 #undef

julia> @which CoordInterpGrid(x, y, BCnearest, InterpLinear)
CoordInterpGrid{R<:Range{T},T<:FloatingPoint (coord::R<:Range{T},A::Array{T<:FloatingPoint,1},args...) at /home/gmihalac/.julia/v0.3/Grid/src/coord.jl:24

julia> ff[-2.3]
0.5

julia> @which ff[-2.3]
getindex{T}(C::CoordInterpGrid{T,1,BC<:BoundaryCondition,IT<:InterpType,R},x::Real) at /home/gmihalac/.julia/v0.3/Grid/src/coord.jl:36

julia> ff[ -3.0:0.1:-2.0  ]
11-element Array{Float64,1}:
 1.0
 0.5
 1.0
 0.5
 1.0
 0.5
 1.0
 0.5
 1.0
 0.5
 1.0

julia> @which ff[ -3.0:0.1:-2.0  ]
getindex{T,R<:Number}(G::AbstractInterpGrid{T,1,BC<:BoundaryCondition,IT<:InterpType},x::AbstractArray{R<:Number,1}) at /home/gmihalac/.julia/v0.3/Grid/src/interp.jl:274

Whatever the problem is, it seems to happen exclusively when extrapolating to the left of the grid. I also tried a case where both bounds of the grid were positive and the problem persists.

What I do is create variables with the same names as the arguments of the functions holding the inputs I want to test, then start copy/pasting the code into the REPL. That way you're effectively executing the function line-by-line.
Of course, when Keno's debugger gets merged, this will get easier.

We've seen this before (see plots in #31) but I don't think we really investigated it though (at least the discussion in that issue doesn't indicate we did). It's likely that there's some subtle bug in the implementation of the wrap function (or one of the ones used with it), but I think a main reason we didn't invest any time in this was that we discovered it right around the time we started focusing on Interpolations.jl instead.
Interpolations.jl is, unfortunately, 0.4-only, and it also doesn't have anything corresponding to CoordInterpGrid yet (although that is trivial to implement, especially if you don't need derivatives), so it's understandable if you don't want to use that just yet. However, there are solutions to these problems in the pipeline.

@tlycken Thank you for the reply! I don't know whether the cluster people here would be open to installing a 0.4 snapshop, otherwise I would gladly try it. At this point I'm contemplating a C or Fortran rewrite (horrible, I know) since I suspect this extrapolation behavior is messing with convergence.

Instead of a complete rewrite in a different language, you could quite easily wrap InterpGrid in a type that works for your use case (constant extrapolation):
type InterpGridBugfix{T<:FloatingPoint, N, BC<:BoundaryCondition, IT<:InterpType} <: AbstractInterpGrid{T, N}
    g::InterpGrid{T, N, BC, IT}
end

import Base.getindex
function getindex(itp::InterpGridBugfix, xs...)
    # these lines can probably be done more efficiently, but this will
    # hopefully clarify the idea enough for you to optimize if you need to
    clamped = similar(xs)
    for i in 1:length(xs)
        clamped[i] = clamp(xs[i], 1, size(itp.g, i))
    end
    return itp.g[clamped...]
end

The idea is simply that you wrap the indexing operation with a method that makes sure you never actually extrapolate, which lets you avoid the bug in Grid.jl. If you, for example, only need 1D interpolation objects, you can make it even simpler:
Base.getindex(itp::InterpGridBugfix, x) = itp[clamp(x, 1, size(itp.g,1))

Constructing one of these objects is really simple - you just pass it the InterpGrid instance. However, you might need to use an explicit constructor of CoordInterpGrid to be able to work it that way.

I've also noticed this bug. Although it seems from the discussion that effort is being focused on Interpolations.jl and 0.4, I thought I'd record things here.
I'm using BCfill, and I see the same problem. An additional detail I've noticed is that if the negative(/left-of-the-grid) values are expressible as integers, the bug disappears and the call to getindex() behaves as expected. Perhaps that might shed some light?

@agbristol Thank you! I'm still holding out hope for some fix here, since 0.4 and its libraries are far from "production ready" and it's doubtful I can get the cluster people here to install it for me.

@agbristol For BCfill, it's possible to construct a similar workaround as what I proposed for BCnearest, so you could implement that yourself if you're in a hurry. The basic principle is that you wrap the InterpGrid in your own type, define a new indexing method that handles the extrapolation for you, and only intex into the InterpGrid with indices that are inside the domain.
However, the info you provided about indexing working for integer indices is valuable. I'll see if I can find the root cause and fix it, rather than force verbose workarounds on you :)

I was looking into this a little bit over the weekend.  I was getting close to a fix, but I didn't have much time.  To save you some digging, there's one issue here at interp.jl#611 (needs to also check ix==1 && ifx < 1 - I think iswrap would be more accurately named isoob (out-of-bounds)).  But that doesn't entirely fix it - there is still a bug in how this information is used in set_position (interp.jl#408).  I may have a chance to finish this up tonight if you don't beat me to it.

@mbauman Thanks a whole bunch! It's dinner time in Sweden, so you have an hour or two on me. What do you say, shall we race to a PR? ;)

@mbauman @tlycken any hope for this? Thank you for all your time and effort!

I don't really have time to work on this, but I've pushed my incomplete WIP to a branch on my fork.  It at least points a direction on where some of the problems are.  Anyone is welcome to move the branch to this repo, add commits, etc.

See #57

Will Pkg.update() update with the fix? I can't seem to get the package to update. Or do we need timholy to do something on the server-side? Thank you very much for fixing this!

@gaabriel #57 hasn't been merged, so the fix isn't actually pushed or released yet. I don't think there are any big hurdles to clear to get it done, though, so I hope to have time for pushing these today.

@gaabriel I just merged the other PRs and tagged a new version, so as of now, Pkg.update() should give you these fixes.

Great! Thank you very much for all the work, all! Now I just hope this helps with my convergence issues.

@tlycken, thanks a bunch. Can you also do git push --tags?

@timholy Ah, sorry - Pkg.publish() failed, so I just pushed the changes to METADATA manually, but forgot to do that. Should be fixed now.

Thanks!


Features/design

Placeholders will be added later

This looks really nice, I agree with everything Maksim said. I am unable to do work from home right now so I will have a look at it at paf tomorrow.

One more thing, I would also sort the categories in the same order in the posts as in the category selector:

Scrap my previous comment about having to log in before having access to the forum. It seems to work now! I wonder why it didn't work previously.
Nice addition of show/hide pw. And awesome touch adding the link to the repo in the footer!
The wrong error message seems to be displayed on comments (string is 1824 characters long):

Also, I think you forgot maxLength here:
// Inside CommentForm.tsx
          <ReactTextareaAutosize
            id={"comment-text"}
            className={"textarea textarea-bordered w-full"}
            value={text}
            onInput={(e) => setText(e.currentTarget.value)}
            required
            rows={1}
           // Probably add maxLength{length} here
          />

Also it would be nice if the posts were updated when the user creates a new post and clicks on the home button, right now they would have to refresh the page.

The wrong error message seems to be displayed on comments (string is 1824 characters long)

Yeah, max length is 1000, not 10000. This pull request is about the design, so this bug should be fixed in another pull request.

Also it would be nice if the posts were updated when the user creates a new post and clicks on the home button, right now they would have to refresh the page.

This is a feature, not a bug :)
The main page is pre-fetched after initial load, before user creates the post. This makes navigation instant. Right now the whole home page is server-side rendered. Of course, we can call router.prefetch("/") to pre-fetch again the updated version of the homepage after post creation, but I think it's better to implement client-side post data fetching instead, like we do for comments. This wlll be a part of #52.


[DISCUSSION] Exploring 126

Investigating https://github.com/benevbright/react-navigation-collapsible/issues/126

Closing as issue has been found.


cmd/bosun: InfluxDB query support

Here is an updated PR from the original 'influxdb-query' branch. It adds support for an influx function that can perform a query against InfluxDB and return the results as a seriesSet. It also adds support for triple quoted strings in expressions so that InfluxDB queries make full use of single and double quotes.
Other small changes where made from the original PR:
Manipulating the InfluxQL AST instead of string manipulations
Removed the format parameter since it required that the expression double list desired tags. Seems like the original reason for having it was to get around a bug in InfluxDB and is no longer necessary. See influxdb/influxdb#3059
Now squashed with all changes.

Thanks for squashing the commits. We usually prefer things get squashed before merging, and I see you already used the cmd/bosun: prefix. I'll take a look today and see if I can get I running.
Also for future reference you can force push the squashed commits to an existing branch instead of opening a new PR. A new PR is only needed if you are deviating from the original goal or want to reset the discussion. Using the existing PR can help keep all the comments in one place.
I'll let you know how much progress I get on this later today.

First off, some notes from how I did my testing:
#Install influxdb using RPM
wget https://s3.amazonaws.com/influxdb/influxdb-0.9.3-1.x86_64.rpm
yum localinstall influxdb-0.9.3-1.x86_64.rpm
service influxdb start

#create influxdb user (required by grafana) and opentsdb database
/opt/influxdb/influx
CREATE USER grafana WITH PASSWORD 'grafana'
CREATE DATABASE opentsdb

#Install telegraf for metrics https://influxdb.com/blog/2015/06/19/Announcing-Telegraf-a-metrics-collector-for-InfluxDB.html
wget http://get.influxdb.org/telegraf/telegraf-0.1.7-1.x86_64.rpm
yum localinstall telegraf-0.1.7-1.x86_64.rpm
service telegraf start

#update /etc/opt/influxdb/influxdb.conf config file
[meta]
  dir = "/var/opt/influxdb/meta"
  hostname = "ny-gbraylx01.ds.stackexchange.com"
...
[opentsdb]
  enabled = true
  bind-address = ":4242"
  database = "opentsdb"
  retention-policy = ""

#Restart influxdb and point an instance of scollector at it:
service influxdb start
scollector -h ny-gbraylx01.ds.stackexchange.com:4242

#Clone repo and build bosun from branch
git remote add influxdb git@github.com:influxdb/bosun.git
git checkout squashed_influxdb-query
go build bosun.org/cmd/bosun

#edit conf file and run bosun
cd $GOPATH/src/bosun.org/cmd/bosun
echo influxHost = ny-gbraylx01.ds.stackexchange.com:8086 > influxdb.conf
./bosun -c influxdb.conf

Using the above I now have:
InfluxDB admin page at http://ny-gbraylx01.ds.stackexchange.com:8083/
opentsdb service at http://ny-gbraylx01.ds.stackexchange.com:4242/
grafana datasource working using http://ny-gbraylx01.ds.stackexchange.com:8086/
a quick test on the bosun expression page shows the following returns the expected data:
influx("telegraf","select value from cpu_percentageIdle group by cpu","5m","")
I will continue testing and let you know if I find any issues.

Triple quotes give an error: I patched that in parser.go in my branch at https://github.com/giganteous/bosun/tree/squashed_influxdb-query

Ideally influxHost should support a full URL if provided, so that a secure https://host:port can be used if everything is configured correctly. Currently if I use influxHost = http://ny-gbraylx01.ds.stackexchange.com:8086 I get "influx: did not get a valid result from InfluxDB".

Triple quotes doesn't appear to work correctly. Error message is expr: invalid syntax. (I see giganteous made a patch already)

There is a debug writeline at https://github.com/influxdb/bosun/blob/squashed_influxdb-query/cmd/bosun/expr/influx.go#L189 that should be removed.

Also when starting it has an odd "web.go:121: tsdb host:" in the log file.

[root@ny-gbraylx01 bosun]# cls;./bosun -c ./influxdb.conf
2015/09/01 22:25:04 enabling syslog
2015/09/01 22:25:04 info: bolt.go:118: RestoreState
2015/09/01 22:25:04 info: bolt.go:231: RestoreState done in 1.539129ms
2015/09/01 22:25:04 info: web.go:120: bosun web listening on: :8070
2015/09/01 22:25:04 info: web.go:121: tsdb host:

This doesn't need to be addressed in this PR but we may want to improve the logging of which backends are being used and what their settings are (tsdbHost, graphiteHost, influxHost, logstashElasticHosts)
We should probably make a docker image for testing. I'm happy to file an issue for tracking and work on this next week.
I'll chat with Craig about this and see when we can merge it.

@giganteous thanks for the patch. I have applied it and updated this PR

The updated PR LGTM. The following expressions work on my local instance:
influx("telegraf","select value from cpu_percentageIdle group by host,cpu","5m","")
influx("opentsdb",'''SELECT value from "os.mem.percent_free" group by host''',"5m","")

I'll merge this and create issues for tracking some followup items (how to guide, docker image, etc). If you find any problems please create an Issue/PR using the influxdb label.
Thanks @nathanielc and @giganteous!

I am getting below error while trying to start bosun.
sudo ./bosun -c conf/bosun.conf
2015/10/19 07:03:14 enabling syslog
panic: runtime error: index out of range [recovered]
panic: runtime error: index out of range [recovered]
panic: runtime error: index out of range
goroutine 1 [running]:
bosun.org/cmd/bosun/conf.errRecover(0xc820115c60)
/go/src/bosun.org/cmd/bosun/conf/conf.go:185 +0xbb
bosun.org/cmd/bosun/expr/parse.(*Tree).recover(0xc820293490, 0xc820115350)
/go/src/bosun.org/cmd/bosun/expr/parse/parse.go:191 +0x8d
bosun.org/cmd/bosun/expr.influxTag(0xc82025dec0, 0x4, 0x4, 0xc820293490, 0x0, 0x0)
/go/src/bosun.org/cmd/bosun/expr/influx.go:28 +0x224
bosun.org/cmd/bosun/expr/parse.(*FuncNode).Tags(0xc8201a9e00, 0x1, 0x0, 0x0)
/go/src/bosun.org/cmd/bosun/expr/parse/node.go:137 +0x73
bosun.org/cmd/bosun/expr.tagFirst(0xc8202a0440, 0x1, 0x1, 0xf91803, 0x0, 0x0)
/go/src/bosun.org/cmd/bosun/expr/funcs.go:44 +0x47
bosun.org/cmd/bosun/expr/parse.(*FuncNode).Tags(0xc8201a9d80, 0xc820293490, 0x0, 0x0)
/go/src/bosun.org/cmd/bosun/expr/parse/node.go:137 +0x73
bosun.org/cmd/bosun/expr/parse.(*BinaryNode).Check(0xc820017ec0, 0xc820293490, 0x0, 0x0)
/go/src/bosun.org/cmd/bosun/expr/parse/node.go:275 +0x3ce
bosun.org/cmd/bosun/expr/parse.(*Tree).parse(0xc820293490)
/go/src/bosun.org/cmd/bosun/expr/parse/parse.go:243 +0xb5
bosun.org/cmd/bosun/expr/parse.(*Tree).Parse(0xc820293490, 0xc820017c20, 0x58, 0xc8202a0420, 0x2, 0x2, 0x0, 0x0)
/go/src/bosun.org/cmd/bosun/expr/parse/parse.go:233 +0xdf
bosun.org/cmd/bosun/expr/parse.Parse(0xc820017c20, 0x58, 0xc8202a0420, 0x2, 0x2, 0xc820293490, 0x0, 0x0)
/go/src/bosun.org/cmd/bosun/expr/parse/parse.go:113 +0x9c
bosun.org/cmd/bosun/expr.New(0xc820017c20, 0x58, 0xc8202a0420, 0x2, 0x2, 0x0, 0x0, 0x0)
/go/src/bosun.org/cmd/bosun/expr/expr.go:67 +0xac
bosun.org/cmd/bosun/conf.(*Conf).NewExpr(0xc820294000, 0xc820017c20, 0x58, 0x4)
/go/src/bosun.org/cmd/bosun/conf/conf.go:1125 +0xc2
bosun.org/cmd/bosun/conf.(*Conf).loadAlert(0xc820294000, 0xc82025da80)
/go/src/bosun.org/cmd/bosun/conf/conf.go:822 +0x1416
bosun.org/cmd/bosun/conf.(*Conf).loadSection(0xc820294000, 0xc82025da80)
/go/src/bosun.org/cmd/bosun/conf/conf.go:513 +0xeb
bosun.org/cmd/bosun/conf.New(0x7ffc1b5bd7f6, 0xf, 0xc820264a00, 0x243, 0xc820294000, 0x0, 0x0)
/go/src/bosun.org/cmd/bosun/conf/conf.go:368 +0xf7f
bosun.org/cmd/bosun/conf.ParseFile(0x7ffc1b5bd7f6, 0xf, 0xb, 0x0, 0x0)
/go/src/bosun.org/cmd/bosun/conf/conf.go:331 +0xe3
main.main()
/go/src/bosun.org/cmd/bosun/main.go:86 +0x201
goroutine 17 [syscall, locked to thread]:
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1696 +0x1
goroutine 5 [runnable]:
text/template/parse.lexText(0xc820080080, 0xf97190)
/usr/local/go/src/text/template/parse/lex.go:237 +0x37e
text/template/parse.(*lexer).run(0xc820080080)
/usr/local/go/src/text/template/parse/lex.go:206 +0x52
created by text/template/parse.lex
/usr/local/go/src/text/template/parse/lex.go:199 +0x15d
goroutine 6 [runnable]:
os/signal.loop()
/usr/local/go/src/os/signal/signal_unix.go:20
created by os/signal.init.1
/usr/local/go/src/os/signal/signal_unix.go:28 +0x37
goroutine 7 [runnable]:
text/template/parse.lexText(0xc820080200, 0xf97190)
/usr/local/go/src/text/template/parse/lex.go:237 +0x37e
text/template/parse.(*lexer).run(0xc820080200)
/usr/local/go/src/text/template/parse/lex.go:206 +0x52
created by text/template/parse.lex
/usr/local/go/src/text/template/parse/lex.go:199 +0x15d
goroutine 8 [runnable]:
text/template/parse.lexText(0xc820080300, 0xf97190)
/usr/local/go/src/text/template/parse/lex.go:237 +0x37e
text/template/parse.(*lexer).run(0xc820080300)
/usr/local/go/src/text/template/parse/lex.go:206 +0x52
created by text/template/parse.lex
/usr/local/go/src/text/template/parse/lex.go:199 +0x15d
goroutine 11 [runnable]:
text/template/parse.lexText(0xc8201a9200, 0xf97190)
/usr/local/go/src/text/template/parse/lex.go:237 +0x37e
text/template/parse.(*lexer).run(0xc8201a9200)
/usr/local/go/src/text/template/parse/lex.go:206 +0x52
created by text/template/parse.lex
/usr/local/go/src/text/template/parse/lex.go:199 +0x15d
goroutine 14 [runnable]:
text/template/parse.lexText(0xc8201a9500, 0xf97190)
/usr/local/go/src/text/template/parse/lex.go:237 +0x37e
text/template/parse.(*lexer).run(0xc8201a9500)
/usr/local/go/src/text/template/parse/lex.go:206 +0x52
created by text/template/parse.lex
/usr/local/go/src/text/template/parse/lex.go:199 +0x15d
goroutine 16 [runnable]:
bosun.org/cmd/bosun/conf/parse.lexSpace(0xc820274d20, 0xf95aa8)
/go/src/bosun.org/cmd/bosun/conf/parse/lex.go:166 +0x1be
bosun.org/cmd/bosun/conf/parse.(*lexer).run(0xc820274d20)
/go/src/bosun.org/cmd/bosun/conf/parse/lex.go:135 +0x52
created by bosun.org/cmd/bosun/conf/parse.lex
/go/src/bosun.org/cmd/bosun/conf/parse/lex.go:128 +0xdf
goroutine 18 [runnable]:
text/template/parse.lexText(0xc8201a9c00, 0xf97190)
/usr/local/go/src/text/template/parse/lex.go:237 +0x37e
text/template/parse.(*lexer).run(0xc8201a9c00)
/usr/local/go/src/text/template/parse/lex.go:206 +0x52
created by text/template/parse.lex
/usr/local/go/src/text/template/parse/lex.go:199 +0x15d
goroutine 19 [runnable]:
text/template/parse.lexText(0xc8201a9d00, 0xf97190)
/usr/local/go/src/text/template/parse/lex.go:237 +0x37e
text/template/parse.(*lexer).run(0xc8201a9d00)
/usr/local/go/src/text/template/parse/lex.go:206 +0x52
created by text/template/parse.lex
/usr/local/go/src/text/template/parse/lex.go:199 +0x15d
goroutine 20 [runnable]:
bosun.org/cmd/bosun/expr/parse.lexItem(0xc82025de40, 0xf95d98)
/go/src/bosun.org/cmd/bosun/expr/parse/lex.go:193 +0x4c1
bosun.org/cmd/bosun/expr/parse.(*lexer).run(0xc82025de40)
/go/src/bosun.org/cmd/bosun/expr/parse/lex.go:163 +0x52
created by bosun.org/cmd/bosun/expr/parse.lex
/go/src/bosun.org/cmd/bosun/expr/parse/lex.go:156 +0xc9
My config file looks like
influxHost = <IP_ADDRESS>:8086
smtpHost = mail.stackoverflow.com:25
emailFrom =<EMAIL_ADDRESS>template cpu {
body = `Alert definition:
Name: {{.Alert.Name}}
Crit: {{.Alert.Crit}}
    Tags:{{range $k, $v := .Tags}}
    {{$k}}: {{$v}}{{end}}
    `
    subject = cpu idle at {{.Alert.Vars.q | .E}} on {{.Tags.host}}

}
notification default {
email =<EMAIL_ADDRESS>next = default
timeout = 1h
}
alert mubble.influx.os.high.cpu {
$q = avg(influx("metrics_db",'''select value from cpu_value GROUP BY host''', "5m", ""))
warn = $q > 20
crit = $q > 1
}
What is wrong in the configuration?

This bug is fixed if you compile from master if I'm not mistaken.


Styling the checkbox list

Replaces CheckboxComboCheckbox in the DirectorShotDetailView with a MenuButton with styling. Class is rather volatile due to some javaFX issues concerning who/what starts running first, but in this specific case it works just fine.
Also adds checkboxes to Creation modal views, so instruments can be selected more easily.

Looks good!

Closed for now due to unforeseen test issues.

2 small comments, please take a look

Looks good!


Support size_px

Added size_px support - the only caveat is... that the current implementation using $gtk.calcstringbox keyword arguments means that the minimum supported DR version now is 5.27... I'm also not sure about the performance implications of using a **splat instead of directly writing the arguments
Alternatively I have another version in #16 which is a bit more involved

Closing in favour of #16


Support for Any Chord?

I have a keymap that heavily relies on chord called Chord Heavy, and while I think that it's great, the discoverability of key chords kinda sucks because of the following issue in VSCode that hasn't been addressed: https://github.com/microsoft/vscode/issues/3969
I think that this extension could do wonders for key chord discoverability if it could just be invoked whenever you start executing a chord. This extension has the potential to become VSCode's very own which-key with a little imagination :)

In think this one is amazingly handled by VSpaceCode

In think this one is amazingly handled by VSpaceCode


MAINT: loosen mypy ignore in QMC

Nightly is failing on
scipy/stats/_qmc.py:529: error: Incompatible types in assignment (expression has type "ndarray[Any, Any]", variable has type "List[int]")  [assignment]
30
scipy/stats/_qmc.py:1154: error: Invalid index type "Tuple[slice, slice]" for "ndarray[Any, dtype[floating[_64Bit]]]"; expected type "Union[SupportsIndex, _SupportsArray[dtype[Union[bool_, integer[Any]]]], _NestedSequence[_SupportsArray[dtype[Union[bool_, integer[Any]]]]], _NestedSequence[Union[bool, int]], Tuple[Union[SupportsIndex, _SupportsArray[dtype[Union[bool_, integer[Any]]]], _NestedSequence[_SupportsArray[dtype[Union[bool_, integer[Any]]]]], _NestedSequence[Union[bool, int]]], ...]]"  [index]

This PR loosen the ignore as we had trouble here in the past. Seems like the API is not stable on mypy/NumPy yet to really rely on that.
https://github.com/scipy/scipy/pull/14653/checks?check_run_id=3802509474

Thanks @tirthasheshpatel for the quick review as well 😉
And now we have other workflow failing -_-

Looks like a UNU.RAN test is failing! I will take a deeper look and try to see what's causing this.

GH is having some trouble with actions atm, hopefully it's linked.


Wrong value range for IoPinService.prototype.pinAnalog

Hey,
MicroBit has an analog write for a range 0-1023. However, when I want to write a value bigger than 255 to the analog pin (pin0 in my case), an error is thrown that the value is not within a correct range. I believe, there is a mistake in the library which assumes that value range for analog write is within 0-255.

The service is constrained to 8-bits, so the 10-bit values are scaled: https://lancaster-university.github.io/microbit-docs/ble/profile/#about-the-io-pin-service


Create builder to simplify index creation

Not actual any more

Index Java API is not very clear and handy for the new user about the meaning of parameters in index creation methods. Also, those parameters are very verbose so it is recommended to create builder methods for indexes. It will be a small handy addition to Java API.

Hi,
Since 3.0 there was a plan to remove the manual index, so we could allow the create of the index only from the schema, that has a slimmer and more clear API.
Regards

Hi, agree. But let's keep this issue open so we will not forget it.


Fix compiler bug with builtin map functions

Could you add the test contract for proof of inclusion that triggered the problem?

Test case added

Rebased on fixed master.

Tracked by https://www.pivotaltracker.com/story/show/159790883

Release note line "Fixes compiler bug with builtin map functions" seems good enough. I plan to update PR once other PRs merged.

I backed up 99c5258b as branch minor-compiler-bug-bak

I added release notes line, rebased, force-pushed.
TODO:

[ ] After PR #1446 merged, edit target branch to master
[ ] Squash-and-merge


Set up MVVM structure using MVVM toolkit package

Using this tutorial or the video in YT watch later.


After upgrade xcode 11.4 even simple app is created with flutter create won't work crashed

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

Hi @nikhil19rathore99
can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you

Hi @nikhil19rathore99
can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you

Hi @nikhil19rathore99
can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you

Solved !! after using flutter upgrade
it fixed Thanks for you concern


Samsung S10+: Pdp with many thumbnails does not fit on the screen

Environment Details
Spartacus: beta release
Browser: Chrome
Device: Samsung galaxy S10+
Happens on: https://spartacus.c39j2-walkersde1-d4-public.model-t.cc.commerce.ondemand.com
Steps to Reproduce
Go to the pdp of product 1934795
Actual Result
Looks disproportionate.
The first thumbnail is cut and it spreads over the storefront on top (white portion).

Tested on ccv2. I see this now.

the storefront spacing issue is fixed.
But the thumbnails still cut?

Tested on dev17 (with iphone 8+).
Verified that without the fix (on ccv2), it looks like this:

And with the fix (on dev17), it looks like this:


qa: harden the p2p-policy test

As brought up in #3001
The p2p-policy test has a number of issues because it is a real-time relay test that can at the moment not be mocked and it is insufficiently hardened against signature length variation.
This PR makes 2 changes to the test to make it more reliable:

Increase the maximum wait time for transactions to be relayed to 2 minutes instead of 30 seconds. This gives us more certainty that the PoissonNextSend() function doesn't schedule outside of our window. See net_processing.cpp for the source that causes us to wait: https://github.com/dogecoin/dogecoin/blob/f132f56ac3b39102cd6c3cc476b12b498b412f3e/src/net_processing.cpp#L3099
Whenever we sign a transaction with an unexpected signature length (this is caused by us not having implemented low-R signing), retry constructing the transaction (with a different input). Fees are changed to be 100% exact. I have also increased the pool of usable inputs to 20, so that we are less likely to end up in endless loops.

Note that this makes the test potentially take a longer time to complete, so we move it up in the list of the test runner, to
be triggered early.
I have tested this with the following bash script that iterates over the test 100 times:
start=$(date "+%s");
mkdir -p /tmp/testtest-$start/logs;
for i in {0..100}; do
  echo -n "$i: ";
  time=$(date "+%s");
  python3 qa/rpc-tests/p2p-policy.py --tracerpc > /tmp/testtest-$start/logs/$i.log 2>&1 && echo -n 'yay ' || echo -n 'nay ';
  echo in $(($(date "+%s") - $time))s;
done > /tmp/testtest-$start/results.txt

Before this PR, the test would fail 2-4 times per 100 runs. Now, it consistently has failed 0 out of 100 runs for me.
Marked urgent because this blocks #3001, which should be in before we refresh translations.

I've uploaded debug logs from these failures as a gist.

Opened #3004 to look at the test logs. Merging this now.


kube-plex runs transcode as root, not plex UID/GID.

As far as I can figure out, the elastic-transcoding pod gets started by the kube-plex shim with the entrypoint overidden as the call to the transcoder, not the normal PMS entrypoint. 0 This makes sense, as we don't want to run the whole server, just the transcode job. Additionally, the plex user in the transcode pod is the default, not whatever's been passed via PLEX_UID/PLEX_GID to the PMS pod. (The plex user is altered to match these variables during the first-time setup of the PMS container 1)
This means that the transcoder is running as root, while plex might be running as some other user.
This breaks using remote NFS PVs for persistent transcode storage, as the transcode pod attempts to access the mount using the root user, which might be (for the sake of security) mapped to another user/nobody on the NFS server side.
Somehow, we need to modify the plex user and group within the transcode pod to match the values the server is running, and start the transcode job running as that user.
I have some experimental code 2 to do this, by modifying the entrypoint of the transcode pod to usermod/groupmod the plex user to the provided values, and su the transcode command to be run as that user, but it seems mildly prone to breakage, since in order to run multiple commands as the entrypoint I had to set bash as the entrypoint.
I'm happy to work on a solution, if anyone has any recommendations for a less brittle way to implement this. (Init containers?

Hi JSteeleIR,
Did you manage to make this work? I applied your commit  to mine. A transcode pod get spun up but it shows loads of connections errors.

Hey zenety,
Glad to hear you got it working!
Those logs initially make me think that maybe the arg rewrite in [0] isn't replacing the localhost parameter with the pmsInternalAddress. But you say that setting the 'allowed without auth' subnet fixed the problem?

Hi,
I have the same error in output but the transcoding works.
 I exec'ed in to the container and was able to curl my machine's address, but <IP_ADDRESS> doesn't seem to respond.

Haven't had a whole lot of time to loop back to this lately, but hoping to get back to it sometime soon.
@djerfy  Any chance that setting the "list of IP addresses and networks that are allowed without auth" that @zenety mentioned above solves the problem? It's interesting that transcoding works, even with the error messages. I wonder if this loopback connection might just be used for debug logging or something, though that definitely also occurs as part of the "transcode status" conversation that 0 sets up for by rewriting the args passed to the transcode binary.
@Stackout Which container did you exec into? The PMS one or the transcode-generated one? .

Hi! Im also having some of the same issues as some of you have. Curling <IP_ADDRESS>:32400 from the kube-plex gives me an unauthorized error, the transcoder however, gets a connection refused at <IP_ADDRESS>:32400. Curling the node IP of the kube-plex from the transcoder works fine with no authorization errors.
My helm setup looks like this:
helm install ./charts/kube-plex --name plex --set claimToken=claim-XXXX --set service.type=LoadBalancer --set persistence.data.claimName=nfs-pvc-movies --set persistence.transcode.claimName=nfs-pvc-transcode --set persistence.transcode.enabled=true --namespace default
Ive tried setting the plex authorized networks to <IP_ADDRESS>/0 with no luck.
Transcoding was working yesterday, but i think the last plex update broke something. I used the same exact helm command.
This is with JSteeleIRs fork of the repo as i am using NFS mounts.
Hope i can help in some way.


Connection closed by remote host fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

Hi mate. Its my first experience with linux and codes. I want learning how to write telegram bots and i found your project. When im trying to do first step "git clone git@github.com:ilyarolf/aiogramshopbot.git -b feature/sqlalchemy-sqlcipher" i got error
kex_exchange_identification: Connection closed by remote host
Connection closed by unknown port 65535
fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
Any idea how to fix it?

Hi @baz0okq , have you generated ssh keys? What linux distro are you using?

I read from many sources that problem with SSH keys but I have no idea how to generate them )))
I use tails.

@baz0okq You can generate ssh keys with the command "ssh-keygen"

I created keys with command
ssh-keygen
Then start ssh agent with command
eval "$(ssh-agent -s)"
After i add keys to ssh agent with command
ssh-add
Now as i understand i should add public key to github and i ****ed up nothing work :(

I want try add ssh key from terminal to github but i give up.
I write command cat ~/.ssh/id_ed25519.pub and put it through browser and finally cloning repository

Now i cant do - pip install -r requirements.txt
As i understand i must install python?
after many attempts i install python 3.9.2 but cant ulgrade it to the 3.12 and after installing python anyway i cant do this command

Successfully install pip3 and when writing command pip3 install -r requirements.txt

Soon my brain 💥
Can you tell me which programs should be preinstalled to allow me complete your manual step by step?)

@baz0okq All your questions are very superficial and there are answers on google, you can also use phind.com language model to get help at some stage. Everything works fine on python 3.9.6.


Refactor m-meta-header

Refactors m-meta-header to handle different screen sizes better and to have a more uniform structure.
Changes

Refactor m-meta-header

Testing

Check out the meta header in https://deploy-preview-1757--cfpb-design-system.netlify.app/design-system/foundation/headings#meta-header and resize to mobile

@anselmbradford
The indent on the second line in “Office of Research Publication” (“Publication”) looks like it needs to move in slightly more in order to left align with the first line of text (“Office”).

Also the horizontal gap between the icons and headings looks a little tight. Can we increase that gap slightly?

The second line in “Office of Research Publication” (“Publication”) looks like it needs to move in slightly more in order to left align with the first line of text (“Office”).

It is aligned, but because of the curve of the O and the straight edge of the P it looks a little off. Unfortunately, not much we can do here because we don't know what these beginning letters may be (and moving it would make an H and a P look misaligned, for example).

Also the horizontal gap between the icons and headings looks a little tight. Can we increase that gap slightly?

Increase this to 5px.

Fixes https://github.com/cfpb/design-system/issues/1730


Center of players is at the bottom of the model

At low distance settings this makes players only disappear if you look at the legs or only hides them while sneaking. Would there be a way to make it uniform across the player model? Or just making the center at the middle of the model would already be a great improvement.

I'll see about this. I'm working on an update to make armor and capes fade out as well (harder than it sounds) so this will probably be in with that as well.


pdf support

I'm always frustrated when I have to manually download the images and then convert them into pdf.
Would be great to have a button which can convert the copies into a single pdf file.

Hii you can download it as PDF. There is download as PDF button in tool

You can also generate multiple images at once by adding larger text that overflows from page

works


Missing docs for gravity argument

The gravity argument was introduced in #52 but there are no docs in the args reference for it.

Updated the readme to reflect this, cheers @johnbillion!


INVALID_COUNTRY_CODE and INVALID_GENDER are the same error code.(1027)

I was just wondering if this was just a typo or if the correct codes where not known?

The codes were extracted from the Android app. I have not checked them
yet.

Here in the next few days I'll try creating an account with purposely in valid genders and country codes(I assume that's where those errors would popup?) and see what I get.


Feature: providing users options to update cart.

An overiew can be seen in red mark in the below image. this will enhance customer convienence.

hey @maadi7 yes you can work on this. This issue is already assigned but whoever does it first i will accept it.

hey @maadi7 issue has been resolved . I am closing this now.


Implement editor refactor from IOT/Alexa repository

This PR pulls a subset of the functionality from the IOT/Alexa repositories that refactors the YaFormEditor/YaBlocksEditor into separate Designer and Block editors that have shared functionality needed for a range of programmable entities.
Change-Id: I69831cfe43892dae14e7c85298ef3a7d65f4fc02

@SusanRatiLane I believe this covers all of the refactor necessary in core to support grouping design/code editors for entity types. In particular, take a look at the logic changes in DesignToolbar (you may want to compare with the alexa-editor branch) to see how the designer/block editor pairs are grouped together.

@SusanRatiLane I believe this covers all of the refactor necessary in core to support grouping design/code editors for entity types. In particular, take a look at the logic changes in DesignToolbar (you may want to compare with the alexa-editor branch) to see how the designer/block editor pairs are grouped together.

Does this include the performance refactors we discussed, or is that a separate set of changes?

@SusanRatiLane Those will come as a separate pull request, or possibly multiple, since there were 6 changes stacked on a single branch, and some are rather large.

@ewpatton This is now merged with master, but attempts to open a project throw an error that CircularProgress is an unknown component. I assume this means that something involving the port of Kodular components did not make it into the merge.

@ewpatton Component icons do not load on the palette on this branch, though the icons do appear on the source tree when a component is placed on a form.


Does it work with double quotes?

After testing npm-check v5.5.1 on my local project I see I didn't found import "package-name" when using double quotes.

I had the same issue with single quotes: My index.ts contains
import * as Webdriver from 'selenium-webdriver';

where npm-check tells me

selenium-webdriver      😕  NOTUSED?  Still using selenium-webdriver?
Depcheck did not find code similar to require('selenium-webdriver') or import from 'selenium-webdriver'.
Check your code before removing as depcheck isn't able to foresee all ways dependencies can be used.
Use --skip-unused to skip this check.
To remove this package: npm uninstall --save selenium-webdriver

The installed version is 5.5.2.

I have been seeing the same issue but for back-ticks. The string is not doing interpolation at all, but I am in the habit of using the back-ticks regardless.
const { success, failure } = require(`@pheasantplucker/failables`)

Causes the NOTUSED warning.
const { success, failure } = require('@pheasantplucker/failables')

Note the change from back-ticks to single quotes. This works just fine and results in no warnings from npm-check.
Installed version is 5.7.0.


Milestone: create an upstream PR

[x] Add back the pyo3 bindings, so we can build both Python version and JS version at the same time
[x] Allow loading of embeddings via an argument. This is needed to make the resulting WASM blob smaller, as it is currently inlined during build.
[ ] Examine the possibility of reintroduction of multithreading (not sure, if that is even needed however due to the sheer perf. difference between other JS libraries)
[x] Feature parity match - adding special tokens support etc.
[x] Investigate better packaging support for browsers and other runtimes.
[ ] Create a more lightweight WASM build
[x] Add CI build steps for testing integrations with bundlers etc

Resolved in https://github.com/openai/tiktoken/pull/50


pkcs12_format_test.c at 3.0.6 fails on NonStop ia64 in PUT thread build

This is a new breakage in the threaded versions (POSIX User Threads) with the following consistent reproducible test failure. The test was run after both 64-bit and 32-bit versions were built and tested. EGD was used successfully for unthreaded tests but failed here:
    # ERROR: (int) 'ERR_peek_error() == 0' failed @ /home/jenkins/.jenkins/workspace/OpenSSL-3.0_Pipeline/test/pkcs12_format_test.c:777
    # [-2147479637] compared to [0]
    # 000000006CFD7C800001000400000000:error:80000FAB:system library:file_ctrl:Resource temporarily unavailable:/home/jenkins/.jenkins/workspace/OpenSSL-3.0_Pipeline/crypto/bio/bss_file.c:326:calling fflush()
    # 000000006CFD7C800001000400000000:error:10080002:BIO routines:file_ctrl:system lib:/home/jenkins/.jenkins/workspace/OpenSSL-3.0_Pipeline/crypto/bio/bss_file.c:328:
    # 000000006CFD7C800001000400000000:error:80000FAB:system library:file_ctrl:Resource temporarily unavailable:/home/jenkins/.jenkins/workspace/OpenSSL-3.0_Pipeline/crypto/bio/bss_file.c:326:calling fflush()
    # 000000006CFD7C800001000400000000:error:10080002:BIO routines:file_ctrl:system lib:/home/jenkins/.jenkins/workspace/OpenSSL-3.0_Pipeline/crypto/bio/bss_file.c:328:
    # 000000006CFD7C800001000400000000:error:80000FAB:system library:file_ctrl:Resource temporarily unavailable:/home/jenkins/.jenkins/workspace/OpenSSL-3.0_Pipeline/crypto/bio/bss_file.c:326:calling fflush()
    # 000000006CFD7C800001000400000000:error:10080002:BIO routines:file_ctrl:system lib:/home/jenkins/.jenkins/workspace/OpenSSL-3.0_Pipeline/crypto/bio/bss_file.c:328:
    # OPENSSL_TEST_RAND_ORDER=1666410019
    not ok 4 - pkcs12_create_test
# ------------------------------------------------------------------------------
../../util/wrap.pl ../../test/pkcs12_format_test => 255
not ok 1 - test pkcs12 formats
# ------------------------------------------------------------------------------
# Looks like you failed 1 test of 13.80-test_pkcs12.t ...................
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/13 subtests

The configuration used is:
Command line (with current working directory = .):

    perl ./Configure nonstop-nse_64_put --prefix=/usr/local-ssl3.0 --openssldir=/usr/local-ssl3.0/ssl no-fips --with-rand-seed=egd threads -D_REENTRANT

Perl information:

    perl
    5.26.3 for NSE-W-nonstop_kernel

Enabled features:

    aria
    async
    autoalginit
    autoerrinit
    autoload-config
    bf
    blake2
    bulk
    cached-fetch
    camellia
    capieng
    cast
    chacha
    cmac
    cmp
    cms
    comp
    ct
    deprecated
    des
    dgram
    dh
    dsa
    dso
    dtls
    dynamic-engine
    ec
    ec2m
    ecdh
    ecdsa
    egd
    engine
    err
    filenames
    gost
    idea
    legacy
    loadereng
    makedepend
    md4
    mdc2
    module
    multiblock
    nextprotoneg
    ocb
    ocsp
    padlockeng
    pic
    pinshared
    poly1305
    posix-io
    psk
    rc2
    rc4
    rdrand
    rfc3779
    rmd160
    scrypt
    secure-memory
    seed
    shared
    siphash
    siv
    sm2
    sm3
    sm4
    sock
    srp
    srtp
    sse2
    ssl
    ssl-trace
    static-engine
    stdio
    tests
    threads
    tls
    ts
    ui-console
    whirlpool
    tls1
    tls1-method
    tls1_1
    tls1_1-method
    tls1_2
    tls1_2-method
    tls1_3
    dtls1
    dtls1-method
    dtls1_2
    dtls1_2-method

Disabled features:

    acvp-tests          [cascade]        OPENSSL_NO_ACVP_TESTS
    afalgeng            [not-linux]      OPENSSL_NO_AFALGENG
    asan                [default]        OPENSSL_NO_ASAN
    asm                 [no asm_arch]    OPENSSL_NO_ASM
    buildtest-c++       [default]
    crypto-mdebug       [default]        OPENSSL_NO_CRYPTO_MDEBUG
    devcryptoeng        [default]        OPENSSL_NO_DEVCRYPTOENG
    ec_nistp_64_gcc_128 [default]        OPENSSL_NO_EC_NISTP_64_GCC_128
    external-tests      [default]        OPENSSL_NO_EXTERNAL_TESTS
    fips                [option]
    fips-securitychecks [cascade]        OPENSSL_NO_FIPS_SECURITYCHECKS
    fuzz-afl            [default]        OPENSSL_NO_FUZZ_AFL
    fuzz-libfuzzer      [default]        OPENSSL_NO_FUZZ_LIBFUZZER
    ktls                [default]        OPENSSL_NO_KTLS
    md2                 [default]        OPENSSL_NO_MD2 (skip crypto/md2)
    msan                [default]        OPENSSL_NO_MSAN
    rc5                 [default]        OPENSSL_NO_RC5 (skip crypto/rc5)
    sctp                [default]        OPENSSL_NO_SCTP
    trace               [default]        OPENSSL_NO_TRACE
    ubsan               [default]        OPENSSL_NO_UBSAN
    unit-test           [default]        OPENSSL_NO_UNIT_TEST
    uplink              [no uplink_arch] OPENSSL_NO_UPLINK
    weak-ssl-ciphers    [default]        OPENSSL_NO_WEAK_SSL_CIPHERS
    zlib                [default]
    zlib-dynamic        [default]
    ssl3                [default]        OPENSSL_NO_SSL3
    ssl3-method         [default]        OPENSSL_NO_SSL3_METHOD

Config target attributes:

    AR => "ar",
    ARFLAGS => "qc",
    CC => "c99",
    HASHBANGPERL => "/usr/bin/env perl",
    RANLIB => "ranlib",
    RC => "windres",
    bn_ops => "SIXTY_FOUR_BIT_LONG RC4_CHAR RC4_CHUNK DES_INT DES_UNROLL BF_PTR",
    build_file => "Makefile",
    build_scheme => [ "unified", "unix" ],
    cflags => "-g -O2 -Wextensions -Wnowarn=203,220,272,734,770,1506 -Wbuild_neutral_library -Wverbose -Wtarget=tns/e -Wsystype=oss -Wlp64 -WIEEE_float",
    cppflags => "",
    defines => [ "OPENSSL_BUILDING_OPENSSL", "OPENSSL_VPROC=\$(OPENSSL_VPROC)", "_XOPEN_SOURCE", "_XOPEN_SOURCE_EXTENDED=1", "_TANDEM_SOURCE", "B_ENDIAN", "_TANDEM_ARCH=2", "_PUT_MODEL_", "_REENTRANT", "_THREAD_SUPPORT_FUNCTIONS" ],
    disable => [  ],
    dso_scheme => "DLFCN",
    enable => [ "egd" ],
    ex_libs => "-lrld -lput",
    includes => [  ],
    lflags => "-Weld=\"-set systype oss\" -Weld=\"-set floattype ieee_float\"",
    lib_cflags => "",
    lib_cppflags => "",
    lib_defines => [  ],
    module_cflags => "",
    module_cxxflags => undef,
    module_ldflags => "-Wshared",
    multilib => "64-put",
    perl => "/usr/bin/perl",
    perl_platform => "Unix",
    shared_argfileflag => "-Weld_obey=",
    shared_cflag => "",
    shared_defflag => "-Weld_obey=",
    shared_defines => [  ],
    shared_extension => ".so",
    shared_ldflag => "-Wshared",
    shared_rcflag => "",
    shared_target => "nonstop-shared",
    sys_id => "TANDEM",
    thread_defines => [  ],
    thread_scheme => "(unknown)",
    unistd => "<unistd.h>",

Recorded environment:

    AR =
    BUILDFILE =
    CC =
    CFLAGS =
    CPPFLAGS =
    CROSS_COMPILE =
    CXX =
    CXXFLAGS =
    HASHBANGPERL =
    LDFLAGS =
    LDLIBS =
    OPENSSL_LOCAL_CONFIG_DIR =
    PERL =
    RANLIB =
    RC =
    RCFLAGS =
    WINDRES =
    __CNF_CFLAGS =
    __CNF_CPPDEFINES =
    __CNF_CPPFLAGS =
    __CNF_CPPINCLUDES =
    __CNF_CXXFLAGS =
    __CNF_LDFLAGS =
    __CNF_LDLIBS =

Makevars:

    AR              = ar
    ARFLAGS         = qc
    CC              = c99
    CFLAGS          =
    CPPDEFINES      = _REENTRANT
    CPPFLAGS        =
    CPPINCLUDES     =
    CXXFLAGS        =
    HASHBANGPERL    = /usr/bin/env perl
    LDFLAGS         =
    LDLIBS          =
    PERL            = perl
    RANLIB          = ranlib
    RC              = windres
    RCFLAGS         =

NOTE: These variables only represent the configuration view.  The build file
template may have processed these variables further, please have a look at the
build file for more exact data:
    Makefile

build file:

    Makefile

build file templates:

    Configurations/common0.tmpl
    Configurations/unix-Makefile.tmpl

@rsbeckerca Could you please try #19483?
Although even with this fix it would be interesting to find out which exact commit between 3.0.5 and 3.0.6 caused this regression. Would you be able to bisect?

@rsbeckerca Could you please try #19483?
Although even with this fix it would be interesting to find out which exact commit between 3.0.5 and 3.0.6 caused this regression. Would you be able to bisect?

Going to test with #19483 and then do a bisect between 3.0.5 and 3.0.6 to find this one. Please stay tuned. It will take a while.

@rsbeckerca any findings?

@t8m I have 3 steps left. Here is what has happened so far - I'm currently at build/test 54ba0f1625:
# bad: [75a6bc17f32505421a78476a972d4d9b74f303b6] Prepare for release of 3.0.6
# good: [ad4910fad22d57c6d685b0ca83bdb7b2bf69d8fd] Prepare for release of 3.0.5
git bisect start 'openssl-3.0.6' 'openssl-3.0.5'
# skip: [9bd968d42e77e2e7e00756cc7bef0817bf8322e1] APPS: ecparam: Support setting properties
git bisect skip 9bd968d42e77e2e7e00756cc7bef0817bf8322e1
# bad: [79eeaf97dd2ab5153875ea92699fe1b421869aa6] OpenSSL::config: determine the MSVC target architecture by asking cl
git bisect bad 79eeaf97dd2ab5153875ea92699fe1b421869aa6
# good: [66627cdfc2450a3604ca23d8a4c9b02de2132b44] Add test for EC_KEY_set_private_key()
git bisect good 66627cdfc2450a3604ca23d8a4c9b02de2132b44
# good: [b4934a9533a1cf290f7f967edf5cfc028967778d] Add an EVP demo for key encoding using EC
git bisect good b4934a9533a1cf290f7f967edf5cfc028967778d
# skip: [67f58eaac17d16020da8503493dbbe77c80698f5] Check that sk_SSL_CIPHER_value returns non-NULL value.
git bisect skip 67f58eaac17d16020da8503493dbbe77c80698f5
# good: [3e7ecb8627a585c05de4cfb8420609ae30c1d91a] Maximum return value of BIO_ctrl_(w)pending is SIZE_MAX
git bisect good 3e7ecb8627a585c05de4cfb8420609ae30c1d91a

@rsbeckerca is DJGPP defined on this platform?? It seems crazy to me as that is a compiler environment targeting the MS-DOS. If it is not defined then I cannot really understand how 8a7e4f1 and preceding commits could really break the test for you.

@rsbeckerca is __DJGPP__ defined on this platform?? It seems crazy to me as that is a compiler environment targeting the MS-DOS. If it is not defined then I cannot really understand how 8a7e4f1 and preceding commits could really break the test for you.

That is what is perplexing me as well. __DJGPP__ is not defined on the platform. The bisect log is showing that commit, however.


higher upper limit

no need to autoscale the container for the trial users
but the content node can grow large with large feeds!

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Do we allow this under the current quota?

for a dev deployment, n=1:
container: 20.09 + 80.009 + 500.0003 = 0.267
content: 20.09 + 1280.009 + 10000.0003 = 1.632
sum = $1.9, quota is $2/hour
so will fit in quota. mem/disk ranges could be even higher as one will most likely not max both these resources at the same time


adds valueRowCount property

as discussed in https://github.com/andreypopp/react-textarea-autosize/pull/205

Would this satisfy your use case? The thing I'm worried about that you probably will have to depend on ref to read this info, because it's not tightly correlated to height so it might change without onHeightChange firing.

Yes. This fixes our problem

The thing I'm worried about that you probably will have to depend on ref to read this info, because it's not tightly correlated to height so it might change without onHeightChange firing.

Not sure if I understand. How would it change without me changing the value itself, and consequently triggering onHeightChange ? Plus, I don't think it would be a problem since I only update the state of the parent component when onHeightChange is fired.
handleHeightChange = (_, innerComponent) => {
    this.setState({
      textareaRowCount: innerComponent.rowCount,
      contentRowCount: innerComponent.valueRowCount,
    });
  };

It can change if u i.e. have reached maxRows or minRows but type more text (or delete lines in second case) - then you won't be notified about new valueRowCount because height won't change.

but it should be fine at this point since I just need to know if the content is smaller or bigger than 1 row

I've decided also to expose this in this.props.onChange - https://github.com/andreypopp/react-textarea-autosize/commit/582b796b19941f819b9142541f0ebc984243e8f5
I need to figure out some bundlers inconsistencies before releasing this though, hopefully should take no more than few days.

thanks @Andarist. We are looking forward for the release

I've released new major version, please check it out.


Add pool variable and user env variables to test resources environment. Fix storage windows pool.

Change to support https://github.com/Azure/azure-sdk-tools/pull/8371 setting pool data

/azp run net - template - tests

/azp run net - storage - tests


nfc_manager_ndef doesn't exist on pub.dev

I need to run the latest dev version (4.0.0-dev) because otherwise, I would run into some Android Gradle issues.
When I bumped the package to the latest I learned that the NDEF stuff was extracted to a subpackage (though, why?) named nfc_manager_ndef, which was stated here: https://pub.dev/packages/nfc_manager/versions/4.0.0-dev#handling-the-nfctag-instance
But that package is not available on pub.dev. I tried importing it via the GitHub URL, but it complained about how I cannot import a GitHub package that relies on a package from pub.dev, or something like that.
So the short question: is there a planned date for when nfc_manager_ndef will be uploaded to pub.dev?

@okadan any update?

@Dohmanlechx Sorry for the delay. I plan to publish the dev version soon (probably within a month).


[BUG] All Rapyd transactions go through redirection flow

Bug Description
It bugs out when you do a non-three-ds transaction that gives response as require_customer_action instead of succeeded for a successful transaction.
Expected Behavior
Non-3DS transactions should not go through redirection flow.
Actual Behavior
Every transaction made goes through redirection flow
Steps To Reproduce
Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.

Set connector to Rapyd
Do a non-3DS transaction

Context For The Bug

Environment
Are you using hyperswitch hosted version? Yes
Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

Are you willing to submit a PR?
No, I don't have time to work on this right now

On checking the logs, the connector is enforcing 3DS verification for every transaction made and we can do nothing about it.


Ensure that we can use ssh force commands with role

This seems fine, but it's a little unclear to me what this fixes. Would you mind providing a short example?

This seems to have gone stale, closing.


how to solve this problem?

after i start the custom game,it crash and show this

This is a workshop tools problem and unfortunately I am not able to do anything about it. Please visit dev.dota2.com and report this problem there.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-28-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3963

Questions ?
Please refer to the Backport tool documentation


FromZeros boxed slice method supports slice DSTs

Makes progress on #29

Codecov Report
Attention: Patch coverage is 86.27451% with 7 lines in your changes missing coverage. Please review.

Project coverage is 87.76%. Comparing base (02dc876) to head (d16421a).
Report is 2 commits behind head on main.

Files with missing lines
Patch %
Lines

src/lib.rs
86.00%
7 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1478      +/-   ##
==========================================
- Coverage   87.83%   87.76%   -0.08%
==========================================
  Files          15       15
  Lines        5623     5638      +15
==========================================
+ Hits         4939     4948       +9
- Misses        684      690       +6

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


Removing models does not alert experiments

Right now the model used is determined by the llm string and the llm_provider_id. If we change the available llm models (e.g., because a provider is deprecating old models), the experiment is never alerted / there is no check.
Possible solutions:

When we edit a provider we could check the old set of models against the new and for any that have been removed we could generate an error / warning to go and update the experiment to first remove dependency on the model that is getting removed.

That solution is a little annoying for the user unless in the same edit-provider UI we allow them to select a replacement. For example, imagine the case where we're removing llama-3 and adding llama-3.1. The steps would be:

Edit the provider to remove llama-3 and add llama-3.1
Get an error that projects X, Y, Z are all reliant on llama-3 so we can't remove them yet
Change the edit to just add llama-3.1
Go manually update all projects relying on the old model
Return to the edit provider screen to remove llama-3

An alternative:

Edit the provider to remove llama-3 and add llama-3.1
Get an error that projects X, Y, Z are all reliant on llama-3 so we can't remove them yet. Ask for a replacement model that will be applied to all experiments that are affected
Confirm replacement and be done.

Option 2 is deffs better UX. +1 for that


Update the log warning of UDF compiler

Signed-off-by: remzi<EMAIL_ADDRESS>Close #5104.
Update the log warning. Delete the content of how to enable udf compiler.

build

build