Codify Initial WebGuide Redesign

After todays Jan 05, 2015 WSG meeting the group came to the concensus regarding the webguide redesign. This is the tentative workflow:

The group reviewed the current mockups and voiced opinions on the largeness of the navigation menu and whether it should be at the top of the page, or the left side of the page. Whether the pages should include images or no images.
Various votes occured this meeting:
-- Should the menu be the Top of the page or Left side navigation: Top:6 Left:4
-- Should the pages contain images: Yes:5 No:4
-- Should the pages show images and have the menu overlay images/text: Yes:6 No:3

With the above notes the WSG group has collectively decided to move forward with the redesign using the current mockup as a template. Having the top menu "open" on the homepage by default and closed into a hamburger on childpages by default. On child pages the menu should overlay any text/images as needed without pushing content around.

The tentative timeline/workflow is:

commence redesign work.
build bootstrap example of redesigned webguide / pick images per pages
get approval from group on final

Eric Mayes will help for redesign with assets from Graphics Identity at UCSB. If images aren't liked on/within the pages then I suggest we display:none the images in mockups to see how they appear at the top of the page.

After the above work is done this template should be an example/basis for the best practices example.

I am closing this issue since it was launched. Thanks everyone.


Extension crashes when using Python 3.12 beta

When used with Python 3.12b1, the Black Formatter extension crashes on startup.
To repro, install Python 3.12b1, create a new venv, and switch to it.
Here's a screenshot of the dialogs that appear in VS Code:

Here's the relevant portion of the "Black Formatter" output logs:
2023-06-16 08:24:40.741 [info] Server: Start requested.
2023-06-16 08:24:41.668 [info] Traceback (most recent call last):
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py", line 41, in <module>
    from pygls import server, uris, workspace
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/pygls/server.py", line 27, in <module>

2023-06-16 08:24:41.685 [info]     from pygls.lsp import ConfigCallbackType, ShowDocumentCallbackType
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/pygls/lsp/__init__.py", line 36, in <module>

2023-06-16 08:24:41.691 [info]     from typeguard import check_type
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/typeguard/__init__.py", line 27, in <module>

2023-06-16 08:24:41.696 [info]     from typing_extensions import Literal
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/typing_extensions.py", line 1174, in <module>

2023-06-16 08:24:41.703 [info]     class TypeVar(typing.TypeVar, _DefaultMixin, _root=True):
TypeError: type 'typing.TypeVar' is not an acceptable base type

2023-06-16 08:24:41.730 [info] [Error - 8:24:41 AM] Server initialization failed.
2023-06-16 08:24:41.730 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-06-16 08:24:41.730 [info] [Info  - 8:24:41 AM] Connection to server got closed. Server will restart.
2023-06-16 08:24:41.730 [info] true
2023-06-16 08:24:41.730 [info] [Error - 8:24:41 AM] Black Formatter client: couldn't create connection to server.
2023-06-16 08:24:41.730 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-06-16 08:24:41.930 [info] Traceback (most recent call last):
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py", line 41, in <module>

2023-06-16 08:24:41.930 [info]     from pygls import server, uris, workspace
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/pygls/server.py", line 27, in <module>
    from pygls.lsp import ConfigCallbackType, ShowDocumentCallbackType
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/pygls/lsp/__init__.py", line 36, in <module>
    from typeguard import check_type
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/typeguard/__init__.py", line 27, in <module>
    from typing_extensions import Literal
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/typing_extensions.py", line 1174, in <module>

2023-06-16 08:24:41.930 [info]     class TypeVar(typing.TypeVar, _DefaultMixin, _root=True):
TypeError: type 'typing.TypeVar' is not an acceptable base type

2023-06-16 08:24:41.952 [info] [Error - 8:24:41 AM] Server initialization failed.
2023-06-16 08:24:41.952 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-06-16 08:24:41.952 [info] [Info  - 8:24:41 AM] Connection to server got closed. Server will restart.
2023-06-16 08:24:41.952 [info] true
2023-06-16 08:24:41.952 [info] [Error - 8:24:41 AM] Black Formatter client: couldn't create connection to server.
2023-06-16 08:24:41.952 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-06-16 08:24:41.952 [error] Server: Start failed: Error: Pending response rejected since connection got disposed
2023-06-16 08:24:42.147 [info] Traceback (most recent call last):
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py", line 41, in <module>

2023-06-16 08:24:42.147 [info]     from pygls import server, uris, workspace
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/pygls/server.py", line 27, in <module>
    from pygls.lsp import ConfigCallbackType, ShowDocumentCallbackType
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/pygls/lsp/__init__.py", line 36, in <module>
    from typeguard import check_type
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/typeguard/__init__.py", line 27, in <module>
    from typing_extensions import Literal
  File "/<redacted>/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/typing_extensions.py", line 1174, in <module>

The black formatter appears to run fine in Python 3.12 if invoked manually.

Created a tracking issue on https://github.com/openlawlibrary/pygls/issues/341 Since this is coming from a dependency of a dependency.

Thanks, I just confirmed that the crash no longer occurs in the prerelease version. I should have checked that first.


Dependencies update

This PR also includes PR #15  and PR #16

@mbaertschi Thank you for your efforts and sorry for the delay on my end! What seems to be missing is the documentation of the trackOriginalValue option in README.md.
I'm happy to merge once that option is documented! 👍

@codepunkt I added a short information about trackOriginalValue in README.md and updated mongoose to v5.0.13 as well.

@mbaertschi Thanks!

Released as 1.3.0


add .idea to .gitignore

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


add fd helper: returns descriptor

similar to the tcpport(s) helper, you pass it a mill tcpsock s to get its fd:
int tcpfd(tcpsock s);

What's the use case for this one?

I was thinking the fds could be convenient for aligning results across sockets outside the library.
I figured I could use fdwait() to know when to do I/O, then use the fd to direct the transfer to the right socket/reference outside somewhere at application-level.

.. well I imagine I need some unique ID representing the connection.
since the process already provisions that with the FD, I figure why not use that?

I figured I could use fdwait() to know when to do I/O, then use the fd to direct the transfer to the right socket/reference outside somewhere at application-level.

Do you need tcpsock at all in that scenario? It looks like you can just use plain old POSIX.

...well I imagine I need some unique ID representing the connection.

Just use tcpsock as the unique identifier.

The reason I don't like this is that tcpsock does its own buffering. So, imagine, that bytes x+0..x+100 are already in the rx buffer. You get the fd and call recv(fd, &buff, 1, 0); You expect to get byte x+0. What you get instead is byte x+101. Same thing applies to the outbound flow.

ok, maybe I need to learn more V8 C++/JavaScript in order to represent tcpsock in JavaScript..
but here's what i wanted to do:
// setup a regular array
static tcpsock ls[255];

// then later (in the same process) inside some v8 wrapper function:
tcpsock s = tcplisten(addr->c_str(), args[1].number);
int fd = tcpfd(s);
ls[fd] = s;

//now return the value back up as a v8::Number to JavaScript land
ret(NanNew<v8::Number>(fd));

then later on I could call back into C++/C and grab the tcpsock using the int fd from its position in the array, assuming I have 10 or 20 connections, an array of 255 is more than enough. Also I noticed that fd numbers tend to be small ints on my system... that could be an erroneous assumption for other systems...

The reason I don't like this is that tcpsock does its own buffering.

I want to use tcpsock. What's the best way to track my tcpsocks? A linked list? I don't think I want to cast it as a struct/V8 object...that just seems like overkill. I want the simplest way to know about tcpsock.

Assuming that fds are going to be from the range (0..255) is not a good idea. Mostly they are, but not necessarily.
In your case I would just put new sockets to the first free position in array ls and use that index as a unique identifier.

that makes sense and sounds better on the off-chance an fd is larger than the array.

thank you


fix: tfsec:ignore: for custom rules doesn't work for shortID

tfsec:ignore: for custom rules doesn't work for shorID's
We can observe in the example that to be able to ignore a custom rule you need to explicitly ignore the LongId.
This creates a lot of confusion as the LongId is automatically generated custom-custom-... and also creates backward compatibility problems with customers who were using the tfsec:ignore:shortCode prior V1.0.0

Thanks @alexandrupopafc


[VNDA] - Add search by type_tags in ProductList loader

Description:
This pull request adds the ability to search for products using type_tags in the ProductList loader on pair with VNDA API. Users can now filter products based on specific tags, enhancing the experience.
Changes Made:

Added support for the type_tags parameter in the ProductList loader.
Implemented mapping and formatting of type_tags in the request.

Additional Information:

This feature aligns with the goal of improving search capabilities, providing users with more flexibility in product searches, and it was a feature required to move on with a internal project to add color variation in the ProductCard.

Code Highlight:
type_tags?: { key?: string; value?: string }[] | undefined

"type_tags[]": props?.type_tags?.map((tag) => ({
        key: tag.key,
        value: tag.value,
      })),

@martinadam75 can you check this type error? Check is failing.

can you check if its ok now @guitavano ?


Gov cloud support

Thanks for contributing to pcf-pipelines. To speed up the process of reviewing your pull request please provide us with:

A short explanation of the proposed change:
Due to the fact gov cloud does not have route53. We have modified the pipeline to support a commercial AWS route 53 by using two providers conditionally

An explanation of the use cases your change solves:
Gov cloud not having route53

Expected result after the change:
Backward compatibility but allows gov cloud to deploy along side with commercial AWS route53

Current result before the change:
PCF pipelines fail with gov cloud due to gov cloud not having route53

Links to any other associated PRs or issues:

[x] I have viewed signed and have submitted the Contributor License Agreement

[x] I have made this pull request to the master branch

[x] I have run all the unit tests

@rotaryczar Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@rotaryczar Thank you for signing the Contributor License Agreement!

Thanks for the pull request.  We are going to be revisiting the approach for how to user pipelines to run a more flexible iaas paving.  We will keep these requirements in play as we look forward to the new direction.


Log line separators

#810 removes \r from log lines.  More generally, line separators should be platform/use-case specific.
How about we simplify otPlatLog() to always assume a single log line at a time?  In other words, format strings passed to otLog*() no longer end with \n.  Instead, otPlatLog() will be responsible for appending the appropriate line separators if necessary.  This would be consistent with other logging infrastructure such as syslog.  If people agree, I'll go ahead and work on an update.

That sounds great to me. The Windows WPP equivalent of these already makes the assumption the log is a single line.


Make Client request Build ID from the Server

This pull request optionally makes the client request the build ID from the server, instead of being informed about it in the server-side render.

would be great to know why this approach can be useful. I couldn't find much context around this.

@chirag04 this is an experimental feature we're playing with -- more information will be announced soon, but this effectively decouples a build from a specific buildId.
This allows you to do interesting things like layering old builds / composing them.


Merge expires_ts into deleted_ts for mysql auto purge

Merge expires_ts into deleted_ts for mysql auto purge

Codecov Report

Merging #2182 (f19544e) into master (ff27a7f) will decrease coverage by 58.14%.
The diff coverage is 0.00%.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I think i totally missed this change here. Why are we not changing PUT and only changes GET and LIST?

I think the idea is we want to preserve old table's data structure during the transition period. So that we can reconcile between old and new ways. Also make it easy to debug when we at least have one thing (the old table) structure fixed for a while. Also see Sophie's comment with the same:
https://github.com/linkedin/ambry/pull/2182#discussion_r949501647

I don't have much context here so i'll skip reviewing this.


multi_block_mode has been removed in the current version?

System Info
NVIDIA -A100
Who can help?
@juney-nvidia
Information

[X] The official example scripts
[ ] My own modified scripts

Tasks

[X] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[ ] My own task or dataset (give details below)

Reproduction
trtllm-build --checkpoint_dir ./c-model/gpt2/fp16/4-gpu
--gpt_attention_plugin float16
--remove_input_padding enable
--paged_kv_cache enable
--multi_block_mode enable
--gemm_plugin float16
--output_dir engines/fp16/4-gpu
Expected behavior
engine build successfully
actual behavior
trtllm-build: error: unrecognized arguments: --multi_block_mode enable
additional notes
https://nvidia.github.io/TensorRT-LLM/performance/perf-best-practices.html#multi-block-mode the best practices docs show s this param but it not work in current

It has been moved to the runtime, so that you don't need to rebuild the engine if you want to switch the option. You can take this as an example: https://github.com/NVIDIA/TensorRT-LLM/blob/main/benchmarks/cpp/gptManagerBenchmark.cpp#L1893

It has been moved to the runtime, so that you don't need to rebuild the engine if you want to switch the option. You can take this as an example: https://github.com/NVIDIA/TensorRT-LLM/blob/main/benchmarks/cpp/gptManagerBenchmark.cpp#L1893

got it, thank you


Add datanode resource limits

It seems like the limits were removed so the data nodes won't be limited too much so I've added a new resources section for the data nodes.

As you can see I already had this code in there, just commented out. I found with limits on memory when you set them and the pod exceeds, then it gets killed. I think the underlying container needs some work to limit the java heap to not exceed a limit so that the pod doesn't.
In my testing, the data nodes would exceed the memory limit pretty regularly and cause the cluster to be restarting always.
Do you have any thoughts? Does your testing show the same?

In my example, there was an environment variable ES_JAVA_OPTS set on the stateful set. That contains -Xmx1024M -Xms1024M for me. So I've set my container limits accordingly. -Xmx1024 should tell the JVM to only have 1Gi of Heap, there will be some other memory depending on how many cores you have so it should be around 1.5Gi max.

oh yeah, it's hardcoded for the data nodes

we should add something you can set that too

Would you mind coding it so that the limits are optional? Maybe if you don't supply value for the limit then it doesn't get set?

I'll change it

@stevesloka This actually brings up an initial observation I had while looking at the project.
What are your thoughts on making:

distinct node type's request/limits customizable but defaulted to something sane
setting the request/limit be the same so you get the "Guaranteed" QOS for K8
JVM settings dynamically tuned off of those defaulted as a % of request/limit

On additional thing to note here, when you add in a "Limit" to a container, this also includes the filesystem cache and the CGroup will cap it.  The implication of this is you will probably want a lower ratio of JVM Heap / Limit than you would expect (ex. maybe 50% of limit goes to the Limit) to provide ES ample headroom for OffHeap storage via the Filesystem Cache.
We ran into a similar issue with our custom grown ES deployment recently and figured I'd throw that out here.

It's pretty easy to write a entrypoint.sh which calculates the java heap size based on the pod's memory request/limits. I've found that making the JVM heapsize 50% of the memory limit/request tends to work fairly well. The pod's entrypoint can get this information as environment variables via the downward API.

Thanks for the feedback, however not setting a limit can result in a negative impact on other pods running in the cluster.  We found that without limiting this, there can be thrashing among the multiple pods on the same node and leads to non-deterministic performance .

I've opened https://github.com/pires/docker-elasticsearch-kubernetes/pull/51 which should help with some of this. Once merged I'll open a PR to this repo that passes everything necessary for the containers to autodetect their memory limit/requests and set their JVM heap size appropriately.
This PR is still needed I think however so that you can control memory limits on a per-component basis.

I opened https://github.com/upmc-enterprises/elasticsearch-operator/pull/120 which is part of the auto-setting the JVM heap size. Still requires the image to have the entrypoint script that I've opened a PR for however.


Opening pyramidal images ob google collab: large_image getTileSource doesn't work on google collab (No available tilesource for ndpi)

I used all of these commands to make sure I have everything that's needed for loading dpi pyramidal images on google collab with no luck so far.
!pip install large_image
!apt update && apt install -y openslide-tools
!pip install openslide-python
!pip install libtiff openslide_python pyvips gdal mapnik pyproj glymur -f https://girder.github.io/large_image_wheels

!pip install large-image-source-openslide
I get the following error:
---------------------------------------------------------------------------
TileSourceException                       Traceback (most recent call last)
<ipython-input-23-0584be72095d> in <module>()
     27 print(os.listdir(ndpi_dir))
     28 print(target_filename)
---> 29 ts = large_image.getTileSource(target_filename)
     30
     31 # print(ts.getMetadata())

1 frames
/usr/local/lib/python3.6/dist-packages/large_image/tilesource/__init__.py in getTileSourceFromDict(availableSources, pathOrUri, *args, **kwargs)
     65         if availableSources[sourceName].canRead(sourceObj, *args, **kwargs):
     66             return availableSources[sourceName](sourceObj, *args, **kwargs)
---> 67     raise TileSourceException('No available tilesource for %s' % pathOrUri)
     68
     69

TileSourceException: No available c for ndpi_images/Li88TDCLAMP.ndpi

I made sure the the file is there, it's loading okay in other platforms using the same command, so it's not the file.
How can I resolve this issue?
Thanks

I'm actually surprised that after repeating this rather desperate exercise of reinstalling everything and restarting the kernels somehow resolved the issue and the slides are loading. I'm still curious how are these things possible? I had all of the requirements installed, I loaded the libraries, and got this very frustrating error.

large_image has different tile sources; if they aren't installed they won't read specific formats.  I would expect the following to work and install all sources (without any need for using apt):
pip install large_image[sources] -f https://girder.github.io/large_image_wheels

Thanks @manthey
The odd issue that I’d like to resolve is that I can load images only after installing and then restarting the session (the compute instance, Google Colab or Saturn Cloud etc). If I don’t restart the session after the installation, it gives the error discussed above. I can keep doing that but I thought it’s inefficient and there must be an explanation and solution. Any thoughts?

This turns out to be an issue with pkg_resources caching information about available packages.  As of python 3.8, the recommended change is to switch from using pkg_resources to importlib.metadata to enumerate entry_points (used to find plugins, such as the tile sources).  For older pythons, there is a backported package.  There will shortly be a PR to do this.
If you are using an older version, you can force Google colab to reload the appropriate information by adding
import pkg_resources
pkg_resources._initialize_master_working_set()

after the !pip install and before trying to load a tile source.


pcluster configure should allow the user to specify the zone

When configuring parallelcluster and asking it to set up the VPC, would it be possible to specify the availability zone to use? For my use case I have an existing EBS volume I'd like to attach, so I need the VPC to be in that zone.

Hi Mark,
unfortunately this is not possible at the moment. I'm going to mark this as a feature request.
What you could do as a workaround is to reuse the same CloudFormation template used by ParallelCluster to create the subnets to create a new CloudFormation stack. That template accepts as input the AZ where to create the subnets.
You can find the template in the CloudFormation console after you let the pcluster configure create the networking for you or simply get it from https://us-east-1-aws-parallelcluster.s3.us-east-1.amazonaws.com/templates/networking/public-private-2.9.1.cfn.json

This issue has been addressed by this commit
It will be part of the 3.0.0 release.

ParallelCluster 3.0.0 has been released. Please try out the new pcluster configure. Cheers!


The example runs no longer function correctly

As of commit 1b1dda8 in the develop branch the example runs of the model do not function correctly. On my Mac the following results are observed:

run_simple_example.sh

output is produced, but has dimension 1x30, instead of the expected 30x30

run_topaz128x128.sh

crashes with a netCDF exception

Both of these examples should run for all of their short run length and produce valid data.

The simple_example runs to completion, but we may need some discussion on the exact values of the fluxes used, mainly Qia.

The topaz128x28 example runs almost to completion, hitting a segfault at the very end of the run. This is caused by the netCDF diagnostic file not being correctly closed. The FileCallbackCloser class solves this and will be included in a near future PR. I'd rather not have to disentangle it (again) for this issue.

PR #426 was merged.


Remove buildout, replace with a manage.py + requirements.txt

Also swaps pylint for flake8

Oop. Needs code from #4


Throwable: Accessing 'IgnoreFilesIndex' during processing 'FilenameIndex'.

Prerequisites

[X] Plugin is in the latest version
[X] Issue was not reported yet
[ ] Stack trace (if provided) contains mobi.hsz.idea.gitignore package name

Description
PHPStorm starts up with the following error:
Throwable: Accessing 'IgnoreFilesIndex' during processing 'FilenameIndex'.
Nested different indices processing may cause deadlock

No stack trace is available, AFAICT.
Steps to Reproduce

Enable the plugin
Restart PHPStorm

Expected behavior: No error message.
Actual behavior: Error message is displayed.
Reproduces how often: All the time, if the plugin in enabled (error stops if plugin is disabled).
Versions
Plugin: 2.1.1
IDE:
PhpStorm 2016.2.2
Build #PS-162.2380.11, built on October 24, 2016
JRE: 1.8.0_112-release-287-b3 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

OS:
Mac OS X 10.12.6

@cviebrock
This issue is caused by IntelliJ itself.
This issue is reported here: https://youtrack.jetbrains.com/issue/IDEA-159135
It was fixed with IntelliJ 2016.2.3
Please update your IDE.


React component with hooks throws error in Vue

When I build the simplest React component I can which uses any hooks, import into a Vue project and attempt to wrap it with applyPureReactInVue, I get errors such as:

If I leave the hooks out, it renders.
I have set rollup options to make 'react' and 'react-dom' external to the React component so that React is not bundled, since the error seems to indicate more than one version of React was found, but this hasn't helped. React component vite config:

Please see repo https://github.com/smimon/veaury-react-hooks-in-vue for simplest reproduction.
"npm install" and "npm run build" in my-react-component folder first to build the component, then "npm install" and "npm run dev" in my-vue-app to see the issue (react component is referenced from a relative path on the file system into the Vue app).
Any help is much appreciated :)

Things I've tried:

importing the component and using it in a simple react app works fine
switching to rollup for the component build config - it produces a much smaller, cleaner output which still works in the React app, but gives the same error with Veuary in the Vue app
downloading 3rd party React components from npm and using them with Veuary in this Vue app works fine

Vue app in my test repo is now using the "my-react-component-rollup" version.

Ok finally got to the bottom of it.
Importing the package from the local file system into my Vue app like this:
"my-react-component-rollup": "file:../my-react-component-rollup"
was creating a symbolic link to the component's folder, which was then in turn picking up the version of React from my component's node_modules folder in addition to the one in the Vue app.
The React app wasn't suffering from this issue however.

@smimon
This problem is actually caused by the fact that the react imported by your react component and the react imported by the vue project are not the same react.
Using the "file:..." file link method is a solution. A better way is to use the Menorepo project. You can use lerna or nx or the standard npm menorepo cli to build and publish

Ok I got it, thanks for taking the time to look.
On Sun, 21 Jan 2024 at 16:11, 天堂里的花大咩（深夜架构师） @.***>
wrote:

@smimon https://github.com/smimon
This problem is actually caused by the fact that the react imported by
your react component and the react imported by the vue project are not the
same react.
Using the "file:..." file link method is a solution. A better way is to
use the Menorepo project. You can use lerna or nx or the standard npm
menorepo cli to build and publish
—
Reply to this email directly, view it on GitHub
https://github.com/devilwjp/veaury/issues/108#issuecomment-1902563748,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR74JBUMVPWJ7SHMAYCL23YPTLUXAVCNFSM6AAAAABCBGRFKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBSGU3DGNZUHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Staff of Traveling visual glitch

After equipping the Staff of Traveling, if I look around, the world renders strangely. (See photos below)
Without moving:

After moving:

This error shows up in minecraft/logs/latest.log:
[20:18:09] [Client thread/ERROR]: ########## GL ERROR ##########
[20:18:09] [Client thread/ERROR]: @ Post render
[20:18:09] [Client thread/ERROR]: 1283: Stack overflow
Here's a complete mod list dump, in case it's helpful: http://pastebin.com/0QMJwxBK

Note: I am using FastCraft, but I am NOT using Optifine

Just checked, and the dimensional anchor causes the same glitch. Strangely, this didn't happen when I first started this world, so it's either due to a recent update or something I did recently in-game.

Note: I am using FastCraft and Optifine

@Cobra1117 , would it be possible for you to create a fresh world, reproduce the issue, and provide the step-by-step instructions you went through to cause the issue?  I'm having difficulty reproducing it.

@kaltinril I'm unable to reproduce the bug. However, I do have some additional info:
1.) I was wrong, and the dimensional anchor doesn't cause the glitch. It's the combination of a dimensional anchor AND the staff of travel. (i.e. when you're holding the staff of travel while there's a dimensional anchor in your view)
2.) This seems to be tied to the state of the anchor. Breaking the block and re-placing it fixes it. It's possible that it was caused by something that changed between versions, as I upgraded fairly recently.
For now, the problem is gone. If it shows up again I'll see if I can figure out more details. (Hopefully the info above helps!)

@MySt1k as well, as he also experienced it

@Cobra1117 @tterrag1098 https://youtu.be/2mUB8SNcCOo

@tterrag1098 We found a solution: it is necessary to rearrange the anchors

More bug does not repeat

I have this same problem in my server world FTB Infinity 1.7, update 1.11.2. However this is happening to me without the use of a staff of traveling. I get the graphical glitches from just using the travel anchors by standing on them.

Tracking under #2898 (I forgot about this one)


NIM-18855: Adding Default UI Validations to Server Config

Description

javax.validation.constraints Annotation error messages are not defaulted from the server and can be configured via PropertyResolver replacement.

Clients can now override and implement their own default validation error messages by providing something like the following

javax.validation.constraints.NotNull.message = VERY IMPORTANT FIELD!

Overview of Changes

Default JSR annotation message is replaced from "{javax.validation.constraints.NotNull.message}" to "${javax.validation.constraints.NotNull.message}"
SpEL Parser resolves this later down the config builder tree.

Type of Change

[ ] New feature

Test Details

N/A
Additional Notes

N/A

You did it @lopezton-anthem!
Thank you for signing the Anthem Opensource Software CLA.

@rakeshnpatel The javax validator framework does allow you to setup different messages for each field. The validator f/w would pick up the messages from properties file in classpath - but thats on the server side.

Is there a way where I can customize/override default messages for my application ?

I am testing this in Petclinic. Something isn't letting the properties in that application override. I will see if I can get it to work.
Ideally it should.

I wasn't able to find any evidence that Spring supports the overriding of application properties when defined in a "parent" jar. (See related stack overflow issue here)
As such I have added "priority" logic to resolve this as follows:

Validation error messages are resolved using the following prioritization order:

Application properties packaged inside client jar (application.properties and YAML variants).
Default message packaged inside client jar (application.properties and YAML variants)
Default messages defined within the Nimbus Framework

I have updated the Pull Request to reflect this.  @soham-anthem @rakeshnpatel can you please review the changes?


Use ReactDOM.render instead of ReactDOM.hydrate in dev

This PR changes ReactDOM.hydrate to ReactDOM.render in dev mode in all the examples, so the user doesn't get Warning: Expected server HTML to contain a matching <div> in <div>., as outlined by @mattyfresh in https://github.com/nozzle/react-static/issues/144.

Great work


strip commit message

I'm using the current version (image id e526ca0ec7f0) with the default template and I get all messages in Telegram with a newline between the commit and the closing 』 character.
I'm not a Go guy but as far as I can understand the plugin is getting the Commit.Message string with a trailing newline. I propose to strip that string of all leading and trailing blanks (spaces, tabs, newlines) before passing it to the template rendering.
This is a sample message in Telegram:

This is the config I am using:
- name: notify_telegram
  image: appleboy/drone-telegram
  settings:
    token: <MY_TELEGRAM_TOKEN>
    to: <MY_TELEGRAM_ID>
  when:
    status: [ success, failure ]

I'm not too sure but this could be similar or related to issue #61 - actually if it was me I'd strip all incoming strings (commit message, author name, etc...)

@lesinigo I made PR for trimming new line https://github.com/drone/drone-template-lib/pull/7 but author don't want accept it. If you need, you can work around it by providing your custom template and trimming it by
{{trimSuffix "\n" commit.message}}

Why not strip it directly in drone-telegram without waiting for drone-template-lib to accept the merge request?

You can make PR to drone-telegram if you want. But in my opinion it`s more proper specify template filters in drone-template-lib. For example, maybe someone want new line in message and it will be stripped be deafult in  drone-telegram and that is not good behaviour

I update the default template like as below:
✅  Build #107 of drone-telegram succeeded.
📝 Commit by appleboy on master:
chore(drone): update default template.
Signed-off-by: Bo-Yi Wu<EMAIL_ADDRESS>🌐 https://cloud.drone.io/appleboy/drone-telegram/107

@appleboy This doesn`t solve problem itself, but looks good for default one view

I update the default template like as below:


Rails/RedundantPresenceValidationOnBelongsTo does not work if config.active_record.belongs_to_required_by_default is false

Rails/RedundantPresenceValidationOnBelongsTo marks an explicit presence validation as an error, even if config.active_record.belongs_to_required_by_default is set to false. In this case removing the validation alters the behaviour of the model. One might argue that setting required: true on the belongs_to would be better, but there are cases where this is not feasible. One example is a model where a relation is only required in some cases with something like
validates :relation, presence: true, if: -> { some_condition? }

In this particular case, autocorrecting the cop leads to the invalid statement
validates :relation, if: -> { some_condition? }

Expected behavior
If config.active_record.belongs_to_required_by_default is set to false, Rails/RedundantPresenceValidationOnBelongsTo should not mark presence validations for belongs_to relations as an error.
Actual behavior
Rails/RedundantPresenceValidationOnBelongsTo marks presence validations for belongs_to relations as an error without considering the value of config.active_record.belongs_to_required_by_default.
Steps to reproduce the problem
Create a rails application and add config.active_record.belongs_to_required_by_default = false to config/application.rb.
Create two models, where the second model has a belongs_to relation to the first. This relation is now not required. Add a presence validation for this relation in the second model. Now run rubocop, the presence validation will now be marked as an error.
RuboCop version
1.24.1 (using Parser <IP_ADDRESS>, rubocop-ast 1.15.1, running on ruby 2.6.5 x86_64-darwin19)
  - rubocop-rails 2.13.1
  - rubocop-rspec 2.7.0

The cop's doc states:

Since Rails 5.0 the default for belongs_to is optional: false unless config.active_record.belongs_to_required_by_default is explicitly set to false. The presence validator is added automatically, and explicit presence validation is redundant.

I can't think of a way for cops to reliably read and parse Rails' configuration files, especially in a multi-app project or a project with engine subdirectories.
Those not adhering to the Rails' default settings, specifically belongs_to_required_by_default should disable the cop in their project's .rubocop.yml:
Rails/RedundantPresenceValidationOnBelongsTo:
  Enabled: false

Personally, I would recommend putting it to .rubocop_todo.yml.

I agree. As the docs say, this setting is intended to "help you migrate all your models to have their associations required by default."
https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#new-framework-defaults

I also agree with @pirj opinion.
NOTE: In the future, it may be possible to develop an implementation that references the Rails standard configuration (e.g.: config/application.rb) created by rails new (which does not include the engine configuration), but it does not currently have that mechanism. And, ideally this Rails/RedundantPresenceValidationOnBelongsTo cop should work in pairs with a new cop who inspects config.active_record.belongs_to_required_by_default = false. Therefore, I will leave it as an enhancement issue, but now it is the expected behavior.

FWIW, we disable it for performance reasons. Validating the record can cause extra db queries if the association isn't already loaded. This is especially a problem when validating a number of records. We instead validate on the association _id and trust the foreign key constraint to ensure that the record is actually there.

Good point and a very interesting observation, @mockdeep.
On a side note, you may like the approach taken in database_validations.
Wondering why does Rails fetch the whole record SELECT * FROM ... WHERE id = ? when a SELECT COUNT(id) FROM ... WHERE id = ? would suffice to make sure the record is there? 🤔
Supposedly this is due to this line in lib/active_model/validations/presence.rb:
record.errors.add(attr_name, :blank, options) if value.blank?

and blank? that would fetch the entire record. I don't see an obvious way of fixing this so that it doesn't fetch the entire record if it's not loaded yet, and rather just checks if it exists in the DB.

Wondering why does Rails fetch the whole record SELECT * FROM ... WHERE id = ? when a SELECT COUNT(id) FROM ... WHERE id = ? would suffice to make sure the record is there?

I think this might be a bit of a philosophical issue. Historically, Rails has put an emphasis on doing many things in application code. They didn't support foreign key constraints in migrations for the longest time. In a way, ActiveRecord is built to help you forget about the underlying database, so validating on an id rather than the record kind of breaks that abstraction. Unfortunately, I think this emphasis means that ActiveRecord lacks some consideration for the actual performance implications of dealing with a database at scale. We do a lot of bulk imports and updates at our company, and we have had to build some of our own tooling to support this and still try to keep the code high level.
I don't want to complain too much, though. AR is a pretty awesome tool, and it's (mostly) getting better. But sometimes I'm surprised when they add a change like this, or when they don't have certain affordances for managing performance.


Build fail (libvim error on OSX 10.12.4)

CC="gcc -Iproto -DHAVE_CONFIG_H   -DMACOS_X -DMACOS_X_DARWIN    " srcdir=. sh ./osdef.sh
gcc -c -I. -Iproto -DHAVE_CONFIG_H   -DMACOS_X -DMACOS_X_DARWIN  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -Wall -Wno-pointer-sign -Wno-cpp -Wno-unused-parameter -Wno-strict-overflow -Wno-return-type -Werror        -o objects/arabic.o arabic.c
error: unknown warning option '-Wno-cpp' [-Werror,-Wunknown-warning-option]
make: *** [objects/arabic.o] Error 1
error: command failed: 'bash' '-c' 'build/build-posix.sh' (exited with 2)
esy-build-package: exiting with errors above...

Getting this error building oni2 from master on OSX 10.12.4
Resolved by removing -Wno-cpp from libvim's Makefile WARN_FLAG

Can this be close now due to onivim/libvim#145?


Different values  between Huge Memory Grant Alert and actual Memory Grant Report

Difference reported between  Best Practices  & Analysis Summary report rule  and actual Memory Grant Report.
Huge Memory Grant found	There are 313 queries with memory grants using > 1 GB of memory. Average grant size = 24.57 GB. The largest grant size found = 28.54 GB. Consider tuning queries to reduce memory usage.
vs.

Rule is using ; tbl_dm_exec_query_memory_grants "-- dm_exec_query_memory_grants --"
PerfStats file , running a select against sys.dm_exec_query_memory_grants directly , no filters.
Report is using ; tbl_Query_Execution_Memory "-- query execution memory --"
....
This should be fixed in the log capture side (Logscout / pssdiag).
Or I can simply change the report definitions to use tbl_dm_exec_query_memory_grants (as those values seems more accurate)
@PiJoCoder any comment on this one ?

I am not biased to either solution because I have worked on both sectionс of code,  though I have not analyzed tbl_Query_Execution_Memory  for accuracy. I do prefer the simpler solution of using tbl_dm_exec_query_memory_grants. But I also think we should update the code in SQL LogScout (PSSDIAG is a minimum maintenance mode). If you have analyzed the code for tbl_Query_Execution_Memory and have reocmmendations, you can make the change yourself. Or if you prefer I can work on it.

@PiJoCoder , I don't want to just replace this with tbl_dm_exec_query_memory_grants as it does not really show text for all queries (mainly if it is ad-hoc ) , yet we have the query text on tbl_Query_Execution_Memory for the same line.
I will work on the capture script on LogScout to make sure these two datasets represent same and accurate data.
Should we keep this one until we complete that ?

@PiJoCoder , I don't want to just replace this with tbl_dm_exec_query_memory_grants as it does not really show text for all queries (mainly if it is ad-hoc ) , yet we have the query text on tbl_Query_Execution_Memory for the same line. I will work on the capture script on LogScout to make sure these two datasets represent same and accurate data. Should we keep this one until we complete that ?

Thank you for the clarification. One thing that comes to mind is could we somehow support backward compatibility? Probably not, once we change the report Data set, but just something to think about.
Yeah, we can keep this item active for now until the SQL LogScout coding is complete. No rush. We can schedule for next wave if that's where it ends up over time.

Closing this to move a step forward in wave3, discussed modifications implemented in LogScout in item 561 and will be available in next release.


Update input-datetime.json

Feature is behind a flag on Firefox Nightly (per https://blog.nightly.mozilla.org/2017/01/18/these-weeks-in-firefox-issue-8/)

Thanks!


Missing step in the tutorial

Description
On the tutorial, Listening and responding to a message part should mention that the bot should be added to the channels first. In the current version, it seems like that the bot is added automatically.
What type of issue is this?

[ ] bug
[ ] enhancement (feature request)
[ ] question
[x] documentation related
[ ] testing related
[ ] discussion

Requirements

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Hi @hm-y 👋   Thanks for bringing this to our attention!
In the paragraph following the code snippet of the section you've linked, it states:

If you restart your app, you should be able to add your bot user to a channel, send any message that contains “hello”, and it will respond.

I can definitely see how this could be missed, given the order of things. In terms of solutions, I'm thinking we could perhaps move that paragraph to sit before the provided code example.
We want to make sure that this issue doesn't arise for anyone else, so if you think the above would help, or had any suggestions for changes on how to make this more apparent to the reader, please let us know!

Hello,
In the previous step, the tutorial says:

After your request URL is verified, scroll down to Subscribe to Bot Events. There are four events related to messages: message.channels (listens for messages in public channels), message.groups (listens for messages in private channels), message.im (listens for messages in the App Home/DM space), and message.mpim (listens for messages in multi-person DMs).
If you want your bot to listen to messages from everywhere it is, choose all four message events. After you’ve added the events you want your bot to listen to, click the green Save Changes button.

I am new to Slack development environment and this part sounds like that the bot will be automatically listening to all channels when I subscribed to message.channels So, I agree that it would be helpful to put these two passages closer to each other.
Thank you.

I completely agree. I think we can better clarify with a change of language and/or the positioning of the existing text.
Thanks again for taking the time to submit this issue! And welcome -- we're happy to have you as part of the development environment. 🙂

Reopening issue to keep track of discussed updates to the documentation


Can't use Module name prefix in record syntax.

Given a module:
module Audio where

defaultTriggers = { timeupdate = False, ended = False }

An error occurs in another module when accessing defaultTriggers:
module AudioTest where

import Audio

myTriggers = { Audio.defaultTriggers | timeupdate <- True }

The error is:
Parse error at (line X, column Y):
unexpected "A"
expecting whitespace, lower case variable or closing bracket '}'

It appears that it is expecting a lower case field name and doesn't know how to handle a field defined in another module.
The work around is to import Audio(defaultTriggers).

Another workaround, using a placeholder variable:
module AudioTest where

import Audio

placeholder = Audio.defaultTriggers
myTriggers = { placeholder | timeupdate <- True }

Alright, I am closing in favor of https://github.com/elm-lang/elm-plans/issues/16 which will track a couple things along these lines. It's good to have them all in one place. Furthermore, I think it's not making sense to have proposals in the elm-compiler repo anymore, so I am laying the groundwork for doing this in a better way. For now, please let me manage elm-plans, no new stuff there!
If there is more to say about this, we should continue the discussion here, not in the elm-plans issue!


A few enhancements related to the hardware module

Move Ram size and Ram type into their own lists
Convert some tuples to lists for uniformity
Modify hardware module related tests to adapt to these changes

Hi! I broke the test suite with my first commit (b01dfe7) and fixed it in my second commit (845f66b). Please consider this as a pair. Thanks!

Thanks!
On Mon, Mar 5, 2018 at 2:12 AM, Líkið Geimfari<EMAIL_ADDRESS>wrote:

Merged #413 https://github.com/lk-geimfari/mimesis/pull/413.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lk-geimfari/mimesis/pull/413#event-1503475951, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABDq5lfwoZhq5rqhP7fU9GOHEjo8gjs8ks5tbOVNgaJpZM4Sbk38
.

@aprasanna Thank you for interest and contributions!

No problem at all! Thank you for being receptive to my contributions :)
On Mon, Mar 5, 2018 at 11:51 AM, Líkið Geimfari<EMAIL_ADDRESS>wrote:

@aprasanna https://github.com/aprasanna Thank you for interest and
contributions!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lk-geimfari/mimesis/pull/413#issuecomment-370484756,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDq5qhjq9ma_-MCQSTVPEMtLrokhwhiks5tbWz3gaJpZM4Sbk38
.


Google Tests Experiment

Closing duplicate of https://github.com/BabylonJS/BabylonNative/pull/1277


⚠ Samsung has degraded performance

In a77a1e3, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2556 ms

Resolved: Samsung performance has improved in 97aa94d.


Calculate G(r) Tab - do not overwrite Qmax upon loading in a new S(Q) for plot

When we load an S(Q) plot, the GUI restores the Qmax along with other options as well. We should keep current state of these variables and instead have a buttong that says something like 'Restore default settings/options'.
It is more common to find a common Qmax and load multiple S(Q) using the same parameters than to restore them and have to re-type them in every time.

To elaborate and show what we mean about the Qmax options, here is a demonstration of what occurs now:

We set a Qmax we want to use for the Fourier Transform to get G(r)

Then, we load in S(Q) files (the multi-selection feature was added in commit https://github.com/neutrons/FastGR/commit/7ec1a9701467b1738be21173e5ce4549b7f37196)

When we load the files in, we lose the Qmax we set and the G(r) produced use the default Qmax of 31.4 (instead of the Qmax=20)

We want to keep the Qmax (and other opitions) set when loading in S(Q) and when we want to restore to the default, have a button to press to do so. Something like 'Restore default setttings'.


python312Packages.nessclient: 1.0.0 -> 1.1.2

Diff: https://github.com/nickw444/nessclient/compare/refs/tags/1.0.0...1.1.2
Changelog: https://github.com/nickw444/nessclient/releases/tag/1.1.2
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 335201 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.ness_alarm
python311Packages.nessclient
python311Packages.nessclient.dist
python312Packages.nessclient
python312Packages.nessclient.dist


NuGet package Id comes through with incorrect case

In packages.config;
<package id="Nancy.Bootstrappers.StructureMap" version="0.20.0" targetFramework="net45" />

Project reference is lowercase as per nuspec id;
<HintPath>..\packages\Nancy.Bootstrappers.StructureMap.0.20.0\lib\net40\Nancy.Bootstrappers.StructureMap.dll</HintPath>

BUT the physical directory is not;

Which means the build fails on (case-sensitive) Mono.
To fix this you usually need to ask the wonderful @JeffHandley to do some voodoo on the nuget server (e.g. https://github.com/Particular/NServiceBus/issues/1271).

This has been sitting here for a while. Is this still a problem?


Error: __dirname is not defined

Hello!
When trying to run semantic-release with this plugin:
npx semantic-release --dry-run --debug

I get the following error:
[semantic-release] › ✘  An error occurred while running semantic-release: ReferenceError: __dirname is not defined
    at file://<root>/node_modules/semantic-release-monorepo/src/log-plugin-version.js:9:47
    at semantic-release-monorepo (file://<root>/node_modules/semantic-release-plugin-decorators/src/wrapStep.js:59:40)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async validator (file://<root>/node_modules/semantic-release/lib/plugins/normalize.js:36:24)
    at async file://<root>/node_modules/semantic-release/lib/plugins/pipeline.js:38:36
    at async Promise.all (index 0)
    at async next (file://<root>/node_modules/p-reduce/index.js:15:44) {
  pluginName: '[Function: semantic-release-monorepo]'
}
ReferenceError: __dirname is not defined
    at file://<root>/node_modules/semantic-release-monorepo/src/log-plugin-version.js:9:47
    at semantic-release-monorepo (file://<root>/node_modules/semantic-release-plugin-decorators/src/wrapStep.js:59:40)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async validator (file://<root>/node_modules/semantic-release/lib/plugins/normalize.js:36:24)
    at async file://<root>/node_modules/semantic-release/lib/plugins/pipeline.js:38:36
    at async Promise.all (index 0)
    at async next (file://<root>/node_modules/p-reduce/index.js:15:44) {
  pluginName: '[Function: semantic-release-monorepo]'
}node:internal/process/promises:289
            triggerUncaughtException(err, true /* fromPromise */);
            ^

Project structure
I'm using Yarn 4, have "type": "module" in each of my package.json files. apps/delivery-options is the only package I'm going to be releasing. It contains a release.config.cjs.
.
├── apps
│   ├── delivery-options <- trying to release this package
│   └── sandbox <- private
├── libs
│   ├── build-vite <- private
│   └── shared <- private
├── nx.json
├── package.json
├── tsconfig.base.json
├── tsconfig.json
└── yarn.lock

Configuration
semantic-release --debug output
  semantic-release:config options values: {
  semantic-release:config   branches: [
  semantic-release:config     '(\\d+)(\\.\\d+)?\\.x',
  semantic-release:config     'master',
  semantic-release:config     'main',
  semantic-release:config     { name: 'alpha', prerelease: true },
  semantic-release:config     { name: 'beta', prerelease: true },
  semantic-release:config     { name: 'next', prerelease: true },
  semantic-release:config     { name: 'rc', prerelease: true }
  semantic-release:config   ],
  semantic-release:config   repositoryUrl: 'https://github.com/myparcelnl/delivery-options.git',
  semantic-release:config   tagFormat: '@myparcel/delivery-options-v${version}',
  semantic-release:config   plugins: [
  semantic-release:config     [ '@semantic-release/commit-analyzer', [Object] ],
  semantic-release:config     [ '@semantic-release/exec', [Object] ],
  semantic-release:config     [ '@semantic-release/release-notes-generator', [Object] ],
  semantic-release:config     [ '@semantic-release/changelog', [Object] ],
  semantic-release:config     [ '@semantic-release/github', {} ],
  semantic-release:config     [ '@semantic-release/git', [Object] ]
  semantic-release:config   ],
  semantic-release:config   analyzeCommits:  [ /* */ ],
  semantic-release:config   fail: [ [ /* */ ],
  semantic-release:config   generateNotes:  [ /* */ ],
  semantic-release:config   success: [ /* */ ],
  semantic-release:config   preset: 'conventionalcommits',
  semantic-release:config   _: [],
  semantic-release:config   'dry-run': true,
  semantic-release:config   d: true,
  semantic-release:config   dryRun: true,
  semantic-release:config   debug: true,
  semantic-release:config   '$0': '<root>/node_modules/.bin/semantic-release'
  semantic-release:config }

Workaround
I've managed to fix this error for now by adding this to the top of my release.config.cjs:
global.__dirname = __dirname;

Thanks for the report! Should be fixed in https://github.com/pmowrer/semantic-release-monorepo/releases/tag/v8.0.2


Update automated-backups-overview.md

Changed the text as the previous versions gives the impression that Geo-Restore is only available on Managed Instance and not Azure SQL DB.

@vtpombei : Thanks for your contribution! The author(s) have been notified to review your proposed change.

The issue that's addressed in the PR appears to be addressed in master. We'll close the PR. If there are outstanding issues or questions, the PR can be reopened.


Refactor cowell

See discussion in gh-1052. Did not run the "slow" tests or the notebooks, they will probably fail.

As expected, MyPy and the slow tests (including the docs) failed. But I actually like how this simplifies the code, and the burden on the user side is only moderate. We could add a helper to assemble several perturbations together (or just leave it like that).

Congrats on this, the implementation is very clean. I really like this new approach, as now the func_twobody is the "true" two-body function. In addition, looks like all the test passed :clap:

Congrats on this, the implementation is very clean. I really like this new approach, as now the func_twobody is the "true" two-body function. In addition, looks like all the test passed :clap:

Merging! Welcome to the future 🚀

Merging! Welcome to the future 🚀


How to redirect another url?

Hi guys, I'm trying to redirect logged out users to home page. I wrote the code below but it didn't work. Do you have any ideas about that?
CROW_ROUTE(app, "/logout")([](const crow::request &req, crow::response &res){
    res.redirect("/");
});

hi, i have the same problem as well.

redirect is just a http status 301 or 302,

the redirect() method just sets the 301 http code and Location header so you need to pass the full URI with host like this res.redirect("http:/");

It worked for me
CROW_ROUTE(app, "/logout")([](const crow::request& req, crow::response& res)
{
    res.redirect("/");
    res.end();
});


lib/minver: bump to 2.3.17

The first version that supports zstd compression, to create the option to eventually switch compression for the binary cache.
It was released one year ago on 2023-11-03 and first shipped in NixOS 23.11.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Changelog added.

Thanks! LGTM. cc @RossComputerGuy for final OK as 24.11 RM.

Apparently I can't read and didn't notice @infinisil was pinged lol. Will wait on him.

Hmm, this is not really what minver is supposed to be used for, it's documented as the "minimum required version for evaluating Nixpkgs". It's arguably even possible to evaluate with Nix 2.3 but substitute with 2.3.17 to use zstd. So is this really the right place to make this change? What happens if we just don't do this? Is there another mechanism that fits better?
Nothing obvious comes to mind, so this might really be the best way of doing it, but I'd like to see a bit more background on why this is needed.

That's fair.
Earlier versions will be unable to substitute, which makes nixpkgs a fairly expensive proposition. The solution is then to upgrade nix, and this kinda achieves the same effect, even though it does not break eval.
That being said, I'm fine with not doing this change, if that means we don't have to wait for minver changes to switch the compression algorithm.

How about we make sure that all versions of Nix that don't support zstd are marked as deprecated in at least supported releases.

What mechanism do you have in mind?

I had lib.warn in mind, but that messes up nix-env :/

Hacky alternative that probably breaks other things: Wrap /bin/nix to print a deprecation warning to stderr before executing the actual Nix binary.

Maybe this bump is the best way after all, because the above options just suck. We'd need to fix nix-env really, but that's a huge effort.

Yeah, I'd be fine with merging if it's the only good option. (curses nix-env from the distance)


Send datasource to grafana for review

@cbmueller What do we need to do before we can submit this?

Should be fine as is.
https://grafana.com/docs/plugins/developing/plugin-review-guidelines/

We don't need the API calls in Check_MK for the review. Do we? They are currently in review and will be added ~tomorrow.
Please check/fix #1 first. Can you please initiate the process like described here?: https://github.com/grafana/grafana-plugin-repository

We’ve merged the needed API calls to the official Check_MK branches.
Upcoming releases, starting with 1.5.0p16, will be able to use the datasource.

See https://github.com/grafana/grafana-plugin-repository/pull/421


[release/1.7] Fix CRI snapshotter root path when not under containerd root

Fixes #10095 in 1.7
This PR backports 4 changes:

https://github.com/containerd/containerd/pull/8417 - Allows proxy plugins to have platforms (not strictly necessary to fix the issue, but I thought it would be less weird to keep this than to take a newer change to ProxyPlugins without the older one)
https://github.com/containerd/containerd/pull/9253 - Allows proxy plugins to have exports (e.g. root)
https://github.com/containerd/containerd/pull/10073 - Exports root paths for a number of snapshotters that didn't already have them
https://github.com/containerd/containerd/pull/9216 - Uses exported root key for snapshotter root if present.

The result of this is that you can tell containerd about a remote snapshotter's root like:
[proxy_plugins.soci]
type = "snapshot"
address = "/run/soci-snapshotter-grpc/soci-snapshotter-grpc.sock"
[proxy_plugins.soci.exports]
root = "/var/lib/soci-snapshotter-grpc"

which will be correctly reported by CRI which unblocks the kubelet from enforcing ephemeral-storage limits and doing image garbage collection.

LGTM
btw just to make sure, this PR doesn't backport https://github.com/containerd/containerd/pull/9152, but rather cherrypicks the closed PR https://github.com/containerd/containerd/pull/9216.

btw just to make sure, this PR doesn't backport https://github.com/containerd/containerd/pull/9152, but rather cherrypicks the closed PR https://github.com/containerd/containerd/pull/9216.

Yes, that's right. I updated the PR description to reflect that.

Thanks!


Fix codebox format

Pretty much all codeboxes in 'src/boxed_primitives' are not formatted correctly.
Instead of:
void main() {
     Boolean b = null;
     System.out.println(b);
     b = true;
     System.out.println(true);
}

They are formatted without the tab before new line in method body:
void main() {
Boolean b = null;
System.out.println(b);
b = true;
System.out.println(true);
}

This is just ugly and bad for readability.

Opened pull-request for this: #40

@


SUBMARINE-712. [WEB] Refactor environment page of Workbench

What is this PR for?
Refactor environment page as below:

What type of PR is it?
[Refactoring]
Todos
What is the Jira issue?
https://issues.apache.org/jira/browse/SUBMARINE-712
How should this be tested?
https://travis-ci.org/github/kobe860219/submarine/builds/756909341
Screenshots (if appropriate)

Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

cc @ByronHsu Could you also help me review this PR?

LGTM


nrf52_bsim: twister yaml: Reduce filtering & fix nrf_rtc_timer driver test for it

nrf52_bsim: twister yaml: Reduce filtering

Two parts:

1)
The nrf52_bsim has had an overall driver filter since
the begining.
But nowadays it supports most of the nrf drivers, so
it can be used to run these drives' tests.
It is actually the only platform which allows running
these drivers in CI without HW (for ex. upstream).

Instead of filtering all drivers, filter only the
drivers which cannot yet be used in this board.

2)
This platform is not a good target to test the
modem drivers, as will not be able to run those until
somebody would want to include models of their respective HW,
for which there is currently no intention.
Build only tests are better suited in native_posix.

Moreover, most of those will fail to build due to their
use of either a GPIO or UART which are not yet supported
in this board.

tests/drivers modem: Add tag modem to ease filtering

Add the "modem" tag, which is already used in other
tests/samples using modems drivers, to ease filtering
of the modem drivers tests if somebody so desires.

tests/drivers/nrf_rtc_timer: Fix for nrf52_bsim

Break two busy wait loops with a Z_SPIN_DELAY
(busy_wait() conditionally compiled for the posix arch)
so this test can also be run in the nrf52_bsim.

& 2 bugs' fixes for bugs in main this CI run uncovered:
drivers/modem sim7080 & ublox-sara: Fix link error

Fix link error when both modems' drivers are enabled
as they both define the same structure but did not
make it static.

This fixes the CI build failure of
tests/drivers/build_all/modem/drivers.modem.simcom_sim7080.build
on particle_boron

drivers/modem/ublox-sare: Fix build warning

Fix the following build warning:
include <fcntl.h> without CONFIG_POSIX_API
is deprecated. Please use CONFIG_POSIX_API
or #include <zephyr/posix/fcntl.h>

Fixes #57435

@rerickson1 The changes in the nrf time test is trivial. You can focus on the modem drivers changes if you want, and let the nrf specific changes for @anangl
@PerMac your blessing on the increased scope for the nrf52_bsim testing will be appreciated :)

Looks good. Fix typo in commit summary drivers/modem/ublox-sare: Fix build warning

Thanks @rerickson1 . Commit msg typo fixed :)


[sync] apache master

Syncing apache/incubator-superset master.
to: @graceguo-supercat @michellethomas @timifasubaa

LGTM


basic workspace overview

Section for extension items will come in subsequent PR. Also needs to be integrated with the command palette (#1957), since it supersedes the workspace menu.
https://user-images.githubusercontent.com/40840436/106213129-06b03080-619a-11eb-90d3-05abb5075e24.mov
current look using PageLayout component for common look-and-feel:

Signed-off-by: Jim Ehrismann<EMAIL_ADDRESS>

@jakolehm @jim-docker I have some overall structure comments.

We shouldn't remove Landing page since it provides friendly and expected step for user before adding new cluster. Now user just goes to empty list. Also thinking about what user will see on the very first app start.
There should be "Add cluster" / "Remove cluster" features added (probably in next PRs, but could be in current one also). Add cluster can get advantage from our blue plus button we're using in Secrets for example

"Workspace overview" item must be added to command palette, because currently there is no way to open it but create new workspace.
Maybe add "Workspaces" item in electron menu along with "Extentions"?
Minor thing: probably better to remove background-color from ItemListLayout for this page - it will look better.

Thanks for your comments @aleksfront:

@jakolehm @jim-docker I have some overall structure comments.

We shouldn't remove Landing page since it provides friendly and expected step for user before adding new cluster. Now user just goes to empty list. Also thinking about what user will see on the very first app start.

I left the friendly elements of the landing page in my first workspace overview iteration, I could add them back here, when the workspace has no clusters.

There should be "Add cluster" / "Remove cluster" features added (probably in next PRs, but could be in current one also). Add cluster can get advantage from our blue plus button we're using in Secrets for example

I used the ItemListLayout add/remove buttons in the second iteration of workspace overview, but we decided to remove them in favour of the Add Cluster button in the clusters menu, and remove menu item (under the vertical ...) beside each cluster item.

"Workspace overview" item must be added to command palette, because currently there is no way to open it but create new workspace.

I've been thinking about this too. It probably should be added o the command palette but I think there should also be a way to get to it from a mouse click. @jakolehm suggested possibly an icon at the top of the clusters menu. I was thinking we could split the workspace status bar elements:

click the workspace icon to get the workspace command palette, click the name (i.e. "default") to go to the workspace overview. I still think it is a little odd that we force a mouse user to bring up the command palette (really meant for a keyboard user) to access workspace functions.

Maybe add "Workspaces" item in electron menu along with "Extentions"?

agreed

Minor thing: probably better to remove background-color from ItemListLayout for this page - it will look better.

will do

I've been thinking about this too. It probably should be added o the command palette but I think there should also be a way to get to it from a mouse click. @jakolehm suggested possibly an icon at the top of the clusters menu. I was thinking we could split the workspace status bar elements...

@jakolehm Maybe we can return workspace menu for mouse users? I'm talking about bottom menu eliminated in https://github.com/lensapp/lens/pull/1957

I've been thinking about this too. It probably should be added o the command palette but I think there should also be a way to get to it from a mouse click. @jakolehm suggested possibly an icon at the top of the clusters menu. I was thinking we could split the workspace status bar elements...

@jakolehm Maybe we can return workspace menu for mouse users? I'm talking about bottom menu eliminated in #1957

#1957 design (and idea) came from @miskun and it follows the same pattern what VS Code has. I would not go back to workspace menu if we are going to push Command Palette further. But let's wait @miskun feedback on this.

I've been thinking about this too. It probably should be added o the command palette but I think there should also be a way to get to it from a mouse click. @jakolehm suggested possibly an icon at the top of the clusters menu. I was thinking we could split the workspace status bar elements...

@jakolehm Maybe we can return workspace menu for mouse users? I'm talking about bottom menu eliminated in #1957

#1957 design (and idea) came from @miskun and it follows the same pattern what VS Code has. I would not go back to workspace menu if we are going to push Command Palette further. But let's wait @miskun feedback on this.

Had a discussion with @miskun about this: we should just put "Workspace: Overview" to the command palette (for now).

Had a discussion with @miskun about this: we should just put "Workspace: Overview" to the command palette (for now).

I think it's a little awkward, but we can start there.

@jim-docker This is looking like it would have potential to fill a gap I've identified through customer feedback: https://github.com/Mirantis/lens-extension-cc/issues/121
But current designs make this look like it's scoped to a single workspace. I would like to see a full overview, across workspaces, of all clusters in all workspaces.
As an extension extending this view, I'd want to highlight specific clusters and workspaces so that I can flag them as "stuff that was just added" when my extension navigates to this overview page after adding a bunch of clusters in a bunch of new workspaces...

@jim-docker This is looking like it would have potential to fill a gap I've identified through customer feedback: Mirantis/lens-extension-cc#121
But current designs make this look like it's scoped to a single workspace. I would like to see a full overview, across workspaces, of all clusters in all workspaces.
As an extension extending this view, I'd want to highlight specific clusters and workspaces so that I can flag them as "stuff that was just added" when my extension navigates to this overview page after adding a bunch of clusters in a bunch of new workspaces...

This PR has specific design requirements meant to coordinate with the workspace command palette functionality. So as is it may not provide what you're looking for. Of course an extension can put basically any content it likes under the workspace overview's cluster list, such as a flat list of all clusters, and their workspace affiliation. Or buttons to take you to other workspaces...
Otherwise I think we'd need to add a new full cluster overview feature.

This PR has specific design requirements meant to coordinate with the workspace command palette functionality. So as is it may not provide what you're looking for. Of course an extension can put basically any content it likes under the workspace overview's cluster list, such as a flat list of all clusters, and their workspace affiliation. Or buttons to take you to other workspaces...

🤔 I'm not sure how I would extend a page like that as an extension, at least not for the use case I'm trying to solve. I'd be interested to see in what ways you anticipate extensions would want to extend this page you're creating. I could see wanting to add columns to show more data for each listed cluster, but to just add seemingly "random" UI to other parts of the page, not sure.
Is this going to be a "master/details" pattern where you select a cluster row and you get a details panel in the lower half of the page that shows more stuff about the selected cluster? That could be interesting to extend as an extension.
Will the list allow CRUD operations on clusters, e.g. select many to delete in one step instead of "right-click + delete + confirm" on each individual cluster from the sidebar? Rename clusters? Move them to other workspaces?

Otherwise I think we'd need to add a new full cluster overview feature.

Yes, please! 😁


Fix all the sample projects

Addresses #12

@markvincze the solution is working perfectly with dotnet run but It is hanging when I try to run with VisualStudio. Could you test in your environment?
Another point that can/should be addressed in another issue is the weird namespace of the HelloController inside ASP.NetCore sample.

I fixed the namespace, but couldn't reproduce the hang, for me it works.
What does it do, actually VS doesn't respond, or it keeps spinning the progress indicator?

@markvincze I tried to clean and change the build configuration but I still can't run it. I think that it could be some machine configuration, as It is working for everyone else I would not spend more time debugging.


Error: No similarly named formulae found.

Unfortunately, the https://github.com/drud/homebrew-ddev gives instructions on updating ddev, but doesn't explain how to install it. So I've just run brew install ddev to get:
Updating Homebrew...
==> Homebrew is run entirely by unpaid volunteers. Please consider donating:
  https://github.com/Homebrew/brew#donations
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).
==> New Formulae
<EMAIL_ADDRESS>                                                                     lychee
==> Updated Formulae
Updated 52 formulae.

==> Tapping homebrew/cask
Cloning into '/opt/homebrew/Library/Taps/homebrew/homebrew-cask'...
remote: Enumerating objects: 566668, done.
remote: Total 566668 (delta 0), reused 0 (delta 0), pack-reused 566668
Receiving objects: 100% (566668/566668), 251.04 MiB | 11.09 MiB/s, done.
Resolving deltas: 100% (400185/400185), done.
Tapped 3900 casks (4,016 files, 269.2MB).
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
Error: No available formula or cask with the name "ddev".
==> Searching for a previously deleted formula (in the last month)...
Error: No previously deleted formula found.
==> Searching taps on GitHub...
Error: No formulae found in taps.

This is happening on a M1 chip MBP.

I just followed the steps on https://www.ddev.com/get-started and it worked for me on M1.

Glad it's working for you. The normal instructions at https://ddev.readthedocs.io/en/stable/#homebrew-macoslinux are the same ones that worked for you.


Step 4: Current flow analysis (and some on step 3.2 and 3.4)

Hi Annie,
I am trying to run current flow analysis and I came across some problems.

similarity_map = out_dir+'MI_data/res_res_MI_compressed_'+file_label+'.npy'
similarity_map_diagonal = out_dir+'MI_data/diagonal_MI_'+file_label+'.npy'
contact_maps = [out_dir+'distance_matrix_semi_bin_'+file_label+'.txt']
additional_interactor_protein_contacts = out_dir+'cofactor_protein_residue_semi_binary_cmap_'+file_label+'.npy'
n_chains=4
source_inds='input_data/inds_sources.txt'
sink_inds='input_data/inds_sinks.txt'
aux_inds='input_data/auxiliary_prot_inds.txt'
compute_current_flow_closeness = False  # False (ie. default) => will compute current flow betweenness.
# Set this to True to compute current flow closeness centrality between each
# source and all sinks instead.
kwargs={
'file_label': file_label,
'out_directory': out_dir,
'n_chains': n_chains,
'n_cores': n_cores,
'similarity_map_diagonal_filename': similarity_map_diagonal,
'normalize_similarity_map': False,
'auxiliary_protein_indices': aux_inds,
'additional_interactor_protein_contacts': additional_interactor_protein_contacts,
'compute_current_flow_closeness': compute_current_flow_closeness
}
CF = allopath.CurrentFlow(similarity_map, contact_maps, source_inds, sink_inds, **kwargs)
CF.run()

I have been recieving this error when I run the script below on python terminal.

Traceback (most recent call last):
File "", line 1, in
File "/sansom/s133/trin2642/Open/Small_box/propeller/CG2AT/MD_1/Flow/allosteric-pathways/allopath/current_flow.py", line 118, in run
self._compute_current_flow_closeness(*self._read_data(contact_map_file))
File "/sansom/s133/trin2642/Open/Small_box/propeller/CG2AT/MD_1/Flow/allosteric-pathways/allopath/current_flow.py", line 454, in _compute_current_flow_closeness
self._set_reduced_inverse_Laplacian(sink_nodes)
File "/sansom/s133/trin2642/Open/Small_box/propeller/CG2AT/MD_1/Flow/allosteric-pathways/allopath/current_flow.py", line 282, in _set_reduced_inverse_Laplacian
L_red_inv = np.linalg.inv(reduced_L)
File "<array_function internals>", line 6, in inv
File "/sansom/s133/trin2642/anaconda3/lib/python3.7/site-packages/numpy/linalg/linalg.py", line 547, in inv
ainv = _umath_linalg.inv(a, signature=signature, extobj=extobj)
File "/sansom/s133/trin2642/anaconda3/lib/python3.7/site-packages/numpy/linalg/linalg.py", line 97, in _raise_linalgerror_singular
raise LinAlgError("Singular matrix")
numpy.linalg.LinAlgError: Singular matrix

I have supplied inds_sinks.txt as
168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188
and inds_source.txt as
7 22 35 36 37 144.

all 4 .npy files are present. The current suspect culprit is
out_dir+'MI_data/res_res_MI_compressed_'+file_label+'.npy
as the only output those aren't boostrap out of step 3.2 is
res_res_MI_part_9my_system.npy and not the rest of the res_res_MI_part_[0,8]my_system.npy. All of these are thought to be required to complete part 3.4 of the tutorial.
So, I made the compressed file by compressing all the res_res_MI_9bootstrap_[0,9]_my_system.npy in step 3.4 and that doesn't seems to work.
If you could help me through this, that would be fantastic!
Best wishes
Will

Hi Will,
Hm, it seems like your reduced Laplacian is singular.
One thing that I noticed (probably not the issue though) is that you set n_chains=4, which means that you should have a homotetrameric protein with symmetric sources and sinks, but your number of input source_nodes and sink_nodes are not a multiple of 4. The source and sink residues should be given by index (zero-based). So they would correspond to "residue" (ie. not "resid") in a VMD selection. Please do check that the selection is correct with mdtraj (traj.topology.residue(residue_index), in some rare cases there are inconsistencies.
To start debugging your problem, I suggest to first look at the contact map to see if it makes sense.
What additional cofactors are you using?

Hi Annie,
My additional cofactor is PIP2 so that is pretty standard I think..
Also, what do you mean by the contact map made sense? The cofactor_protein_residue_semi_binary_cmap_my_system.npy
has dimension of (4, 1316) and the file is not entirely 0 so I think that make sense?
Thank you so much!
Will

Hi Will!
I was thinking that there could be a node that is not connected to the network. One thing you could try is to include the full membrane in the network if e.g. one PIP2 does not interact.
About the MI bootstrapping, I did not understand exactly what the issue was? Did you not get all the output files? Was there an error message?

Hi Annie,
There is no error message. What's the expected output? Is it 10 bootstrap files (the one with dimension of 329,329 and one additional non-bootstrap file.
What do you mean by the node not connected to the network? You mean the source and the sink are not the lipid binding site? Should I specify the source to be residues at the lipid binding site and the sink to be gating residues?
Will

Hi Annie,
When you say include a full membrane to the network, do you mean add POPC to the cofactor file?
Also - if I have 4 PIP2. Do I just specify as:
"resname PIP2" in my cofactor_domain_selection.txt or do I need to have 4 lines of:
"resname PIP2 and resid xxx"
and do I need to specify the whole POPC?
Thank you so much!
Best wishes
Will

Hi Will,
By connected, I mean in terms of the network: if the nodes (residues or lipids) are in contact or not.

When you say include a full membrane to the network, do you mean add POPC to the cofactor file?

Yes, exactly! I had these lines in my cofactor file to specify POPC and PIP2:
resname POPC and name N C11 C12 C13 C14 C15 P O13 O14 O12 O11 C1 C2
resname POPC and name O21 C21 C22 O22 C23 C24 C25 C26 C27 C28 C29 C210 C211 C212 C213 C214 C215 C216 C217 C218
resname POPC and name C3 O31 C31 C32 O32 C33 C34 C35 C36 C37 C38 C39 C310 C311 C312 C313 C314 C315 C316
resname SAPI and name N C11 C12 C13 C14 C15 P O13 O14 O12 O11 C1 C2 C16 O6 O5 O4 O3 O2 OP54 OP53 OP52 OP44 OP43 OP42 P5 P4
resname SAPI and name O21 C21 C22 O22 C23 C24 C25 C26 C27 C28 C29 C210 C211 C212 C213 C214 C215 C216 C217 C218 C219 C220
resname SAPI and name C3 O31 C31 C32 O32 C33 C34 C35 C36 C37 C38 C39 C310 C311 C312 C313 C314 C315 C316 C317 C318

So this specifies three nodes per lipid molecule. Hope this helps!
Best,
Annie

Hi Annie,
It works now! Thank you so much!
Will

Great - I'm happy to hear! :)
Annie


Change Base Map

Describe the problem

The current map is not high contrast, and difficult to read except at oblique angles on screens
It does not have enough street labels, especially at any significant zoom level, making drawing on the map very hard.

Describe the solution
Please change the base map to something like this:
https://www.maptiler.com/maps/#bright//vector/9.45/-86.8215/33.4251 (County lines, clear water features and street labels)
https://www.maptiler.com/maps/#streets//vector/9.45/-86.8215/33.4251 (Street labels, clear water features)
Additional context and instructions
Add any other context or screenshots about the feature request here.

To add to this,
What do you think about allowing the user to select from a list of different base maps (satellite/terrain/etc) Similar to a lot of navigation apps.

Is that an option on Pitney Bose maps we use?

On Sep 19, 2020, at 9:24 PM, Braden Mars<EMAIL_ADDRESS>wrote:
To add to this,
What do you think about allowing the user to select from a list of different base maps (satellite/terrain/etc) Similar to a lot of navigation apps.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/CrisisCleanup/crisiscleanup-3-web/issues/960#issuecomment-695522720, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFKXRJUVEWOQALEOTCX2MLSGVRWPANCNFSM4RTJSJYQ.

@BradenM It might be convenient to allow for Satellite, and, in theory, disaster-specific data imagery as well. For example, sometimes we are able to get access to flood maps that show the furthest extent of the flood. But it is not a high priority compared with other issues.
@arroyoDev It turns out that we are not actually using Pitney Bowes. We still pay $1K per month for Google Maps. Groan.


Error: connect ECONNREFUSED <IP_ADDRESS>:5173

I'm trying to add a container image for cypress/browsers and setting browser as chrome to run Cypress tests in the GHA with cypress-io/github-action@v6 but I'm getting the following error
Error: connect ECONNREFUSED <IP_ADDRESS>:5173
This is my config:
jobs:
  cypress-super-user:
    runs-on: ubuntu-20.04
    container:
      image: cypress/browsers:node-20.18.0-chrome-129.0.6668.89-1-ff-131.0.2-edge-129.0.2792.65-1
      options: --user 1001
    strategy:
      fail-fast: false
      matrix:
        containers: [1, 2, 3, 4]
    timeout-minutes: 180
    steps:
      - name: Checkout 🛎
        uses: actions/checkout@v4
        with:
          token: ${{ steps.generate_token.outputs.token }}
          submodules: recursive
          persist-credentials: false

      - name: Set up Node
        uses: actions/setup-node@v4
        with:
          node-version: 20.18.0

      - name: Install Dependencies
        run: npm i

      - name: Run directory_ui
        run: npm run serve &

      - name: Cypress Tests 🧪
        uses<EMAIL_ADDRESS>        with:
          record: true
          parallel: true
          browser: chrome
          wait-on: "http://localhost:5173/"
          wait-on-timeout: 180
          env: userType=userSuperAdminType
          group: Raidiam - Super Admin
          config: baseUrl=http://localhost:5173

If I remove the container from the job Cypress is able to connect to <IP_ADDRESS>:5173 and all tests pass
Additional Information:
I'm using VUE version 2.7.14 and VITE version 5.4.6
Cypress version 13.15.0

@CaiqueCoelho
You may find the README section Debugging helpful to look at what is going wrong in your workflow. There may be some timing differences between running directly in ubuntu-20.04 compared to running in a container using a Cypress cypress/browsers:node-20.18.0* Docker image, which is based on Debian 12.7.
You mention that you are using VUE version 2.7.14. According to https://v2.vuejs.org/eol/, Vue 2 reached end of life on Dec 31, 2023 and is no longer maintained.

@CaiqueCoelho
Are you expecting any further assistance with your issue?

Closing, since there hasn't been any feedback to the comments and there is no other action that can be taken in the repository concerning this issue.


COMPILATION ERROR - package org.testng.annotations does not exist

While trying to execute build in Jenkins I'm getting following error :

[ ] COMPILATION ERROR - package org.testng.annotations does not exist
[ ] cannot find symbol
symbol:   class Test

Error :
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JIS_Admin.java:[2,30] package org.testng.annotations does not exist
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JBIMS.java:[2,30] package org.testng.annotations does not exist
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/A2ADemo.java:[6,30] package org.testng.annotations does not exist
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/A2ADemo_Admin.java:[2,30] package org.testng.annotations does not exist
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JIS.java:[6,30] package org.testng.annotations does not exist
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JBIMS_Admin.java:[2,30] package org.testng.annotations does not exist
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JIS_Admin.java:[11,10] cannot find symbol
symbol:   class Test
location: class AdmissionToAlumni.JIS_Admin
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JBIMS.java:[11,10] cannot find symbol
symbol:   class Test
location: class AdmissionToAlumni.JBIMS
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/A2ADemo.java:[11,10] cannot find symbol
symbol:   class Test
location: class AdmissionToAlumni.A2ADemo
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/A2ADemo_Admin.java:[11,10] cannot find symbol
symbol:   class Test
location: class AdmissionToAlumni.A2ADemo_Admin
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JIS.java:[11,10] cannot find symbol
symbol:   class Test
location: class AdmissionToAlumni.JIS
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JBIMS_Admin.java:[11,10] cannot find symbol
symbol:   class Test
location: class AdmissionToAlumni.JBIMS_Admin
[INFO] 12 errors
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  1.548 s
[INFO] Finished at: 2021-06-30T12:52:52+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project A2A_Scripts: Compilation failure: Compilation failure:
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JIS_Admin.java:[2,30] package org.testng.annotations does not exist
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JBIMS.java:[2,30] package org.testng.annotations does not exist
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/A2ADemo.java:[6,30] package org.testng.annotations does not exist
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/A2ADemo_Admin.java:[2,30] package org.testng.annotations does not exist
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JIS.java:[6,30] package org.testng.annotations does not exist
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JBIMS_Admin.java:[2,30] package org.testng.annotations does not exist
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JIS_Admin.java:[11,10] cannot find symbol
[ERROR]   symbol:   class Test
[ERROR]   location: class AdmissionToAlumni.JIS_Admin
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JBIMS.java:[11,10] cannot find symbol
[ERROR]   symbol:   class Test
[ERROR]   location: class AdmissionToAlumni.JBIMS
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/A2ADemo.java:[11,10] cannot find symbol
[ERROR]   symbol:   class Test
[ERROR]   location: class AdmissionToAlumni.A2ADemo
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/A2ADemo_Admin.java:[11,10] cannot find symbol
[ERROR]   symbol:   class Test
[ERROR]   location: class AdmissionToAlumni.A2ADemo_Admin
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JIS.java:[11,10] cannot find symbol
[ERROR]   symbol:   class Test
[ERROR]   location: class AdmissionToAlumni.JIS
[ERROR] /C:/Users/Admin/.jenkins/A2A_Scripts/src/main/java/AdmissionToAlumni/JBIMS_Admin.java:[11,10] cannot find symbol
[ERROR]   symbol:   class Test
[ERROR]   location: class AdmissionToAlumni.JBIMS_Admin
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Build step 'Invoke top-level Maven targets' marked build as failure
Finished: FAILURE

It looks like your project is not the same as the smart-home-dashboard so I don't think this is the right place to file an issue. However, it does seem like there's an import error at org.testng.annotations which should instead be testing.


ENH: Update questions format

Fixes #17

@AnirudhDagar Could you please review this and check if it looks good?


Installation Issue with Docker - Missing Info

Hi guys,
I've been through a problem while installing the environment locally.
It happened specifically when running:
docker-compose run web composer build

As we can see here:

I did some research and found that this issue is still open, as we can see here.
In brief, there are two possible solutions for now:

eval $(docker-machine env default)
Assign to .bash_profile the output from eval $(docker-machine env default)

I applied the first option and it worked fine.
Do you guys want me to submit a PR updating the Installation Docs with this info?
Cheers

Sure, go for it! :)

Done @jedrzej, just let me know if is fine for you!

Nice, same thing here, I use the described solution 1). 👍


Provide an ability to redirect stdout and stderr

carton test previously parsed output of tests that were run with wasmer. It's no longer possible to capture their output, I wonder if WAMR itself supports this at all?

As far as I saw, WAMR doesn't provide a way to hook stdout/stderr :cry:
One suggestion: How about launching another carton process in carton test, and execute Wasm binary with WAMR in the spawned process, then capture the output?

In the meantime, I've created https://github.com/bytecodealliance/wasm-micro-runtime/issues/482 to track this in WAMR proper.


Switching between dev (local filesystem) and production (aws s3)

Hey guys,
you removed the hostnames_to_replace config so i need to switch to relative paths of my images.
I am using it with Carrierwave and AWS S3 in production and local file system for local development.
What is you approach to switch between those things with imgix?
Greets and thanks :)

Hi @KillerCodeMonkey,
We decided to remove the hostnames_to_replace functionality as part of an ongoing effort to hone and focus the functionality of our client libraries to unify them and focus on the most important features. We determined that this kind of hostname replacement was a rare enough use case and was relatively trivial for an end-developer to implement directly that it should not be supported as a first-class feature of this library.
You should be able to replicate the old hostnames_to_replace functionality without too much fuss by doing some string manipulation on your URLs before you pass them into any imgix helper functions. Here's how we were doing this previously:
def replace_hostname(source)
  new_source = source.dup

  # Replace any hostnames configured to trim things down just to their paths.
  # We use split to remove the protocol in the process.
  hostnames_to_remove.each do |hostname|
    splits = source.split(hostname)
    new_source = splits.last if splits.size > 1
  end

  new_source
end

Hope this helps. I'm gonna close this ticket, but please re-open if you have any issues or further questions.

Hey there. Thanks for the response. To avoid an additional env variable
that Stores the replace Hostname. I added a View helper, that switchs
between image.path (rails.env.production) and .url (Dev).
On local Dev i Set the imgix source to http://localhost:3000
So when i use imgix viewhelpers i pass the path through my path_per_env
helper.
Jason Eberle<EMAIL_ADDRESS>schrieb am Mi., 24. Okt. 2018,
21:47:

Hi @KillerCodeMonkey https://github.com/KillerCodeMonkey,
We decided to remove the hostnames_to_replace functionality as part of an
ongoing effort to hone and focus the functionality of our client libraries
to unify them and focus on the most important features. We determined that
this kind of hostname replacement was a rare enough use case and was
relatively trivial for an end-developer to implement directly that it
should not be supported as a first-class feature of this library.
You should be able to replicate the old hostnames_to_replace
functionality without too much fuss by doing some string manipulation on
your URLs before you pass them into any imgix helper functions. Here's how
we were doing this previously
https://github.com/imgix/imgix-rails/blob/v2.1.4/lib/imgix/rails/url_helper.rb#L27-L38
:
def replace_hostname(source)
new_source = source.dup
Replace any hostnames configured to trim things down just to their paths.
We use split to remove the protocol in the process.
hostnames_to_remove.each do |hostname|
splits = source.split(hostname)
new_source = splits.last if splits.size > 1
end
new_sourceend
Hope this helps. I'm gonna close this ticket, but please re-open if you
have any issues or further questions.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/imgix/imgix-rails/issues/64#issuecomment-432802860,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACKOYB254HQbu9Df8qwgeZCa-gqcgss3ks5uoMPagaJpZM4XjW0m
.


User should see privacy + terms in same screen

Definition of Done

merge in settings menu privacy and terms
rename to "Privacy Policy & Terms" redirect to the TOU iframe

Verified as done
Checked on Dev environment v0.18.0


Export Destination doesn't let me create a New Folder

The panel that opens up when I click on the Export Destination only allows one to select folders that already exist, but does not let one create a new folder and select that one.
Ideally one could create a new destination folder as well.

Thanks for finding this.
I fixed that in Glyphs (as the script uses API from the python wrapper). I don’t like to copy that code into plugin.