Attachments don't display on mobile

I'm using obsidian on mobile and any shared note will display the filenames of attachment, but the attachment can't be viewed from the share note link.
See attachment for visualization of what's being displayed.

I'll need a little bit more info here please - can you share the link to a note which isn't working?
As an example, this is a shared note and you can see the attachments display fine on mobile, so it must be something specific about the data you're sharing:
https://share.note.sx/about

Thanks, I can see the issue, will have it fixed by tomorrow.

Will do after breakfast.

Can you please update to 0.8.2 and test?
I have found and resolved an issue when the image src is http://localhost/....
If it doesn't work for you, please provide a link to your shared note showing the issue.

Can you please update to 0.8.2 and test?
I have found and resolved an issue when the image src is http://localhost/....
If it doesn't work for you, please provide a link to your shared note showing the issue.

You nailed it. Thanks for incredibly quick fix and amazing plugin.


Automatic OpenCL parameters

There are a few parameters that need to be set and optimized when running the code inside an OpenCL kernel. These parameters are sometimes hardware-specific or rayScatteringScene-specific and setting them manually would be a mess for the user. By refactoring the logic of the code a bit, 2 important parameters stand out: (1) the number of work units used to parallelize the OpenCL kernel, which is hardware-specific, and (2) the average number of interactions per photon (IPP) which is used to set the logger size small enough to yield fast kernel time over a predefined optimal number of batches (5). This IPP doesn't depend on hardware, but on the scene and the source used.
OpenCL Config File
Most of the OpenCL related parameters (excludes IPP) are stored in a config.json file. Here are the default values (None parameters are automatically calculated as described below):

DEVICE_INDEX = NONE
MAX_MEMORY_MB = NONE
N_WORK_UNITS = NONE
IPP_TEST_N_PHOTONS = 1000
BATCH_LOAD_FACTOR = 0.2

BATCH_LOAD_FACTOR
Refers to the amount of photons expected to propagate inside a single batch, or more precisely, the size of the logger relative to the total size needed on average to propagate all photons. Trial and error shows that a load factor around 0.2 seems to be optimal (yields around 6-8 batches). It is faster to split the propagation over multiple small batches than to full the device memory every time.
IPP_TEST_N_PHOTONS
Refers to the amount of photons used to estimate the IPP of an experiment. 1k gives a good enough first estimate to set logger size, but anyway, the value is stored and updated with sampling (more on that below).
DEVICE_INDEX
Refers to the OpenCL device the user wants to use. This is set on the first launch. If multiple devices are available, the program asks the user to choose.
MAX_MEMORY_MB
This is the maximum OpenCL device memory the program is allowed to use (possibly limiting the batch logger size or BATCH_LOAD_FACTOR for a given experiment if N is big). This is autoset to the minimum value between 1GB and 75% of the device memory. We limit ourselves to 75% of the device memory because testing sometimes showed out-of-memory errors when going over 85% of total GPU memory, which is probably due to some GPU memory being used somewhere else. Then, we also limit by default to 1GB max since OpenCL CPU device will show max memory as the total RAM on the computer which is way too high and could definitely yield out of memory crashes because of the already high RAM load of our program outside of the OpenCL kernel. The user can still manually increase this value if he wants to, but it will probably not yield any speed improvements since small batches work well.
N_WORK_UNITS
A vague OpenCL term (the definition somewhat depends on the type of hardware), also known as work item. It set's the amount of workers (amount of kernels) that are possibly executed in parallel depending on the hardware... Anyway, the optimal value is hardware-specific and cannot be simply inferred through hardware details. The only way to find the optimal value is through trial and error, so I did that. On first launch if the value is None, the program launches a test script that runs a simple PyTissueOptics experiment multiple times, going through various N_WORK_UNITS values between 128 and 32768 and averaging each case 3 times. It takes around 2 minutes to complete on my device, and I wrapped each propagation call under a timeout decorator to make sure it doesn't get stuck. The test displays a graph of the result to help the user see by himself what amount of work units seems optimal. Then it asks to go for the optimal value tested or enter a custom value.
Average Number of Interactions Per Photon (IPP)
The IPP has to be determined for each experiment. The value will always only depend on the scene properties (objects, materials, etc.) and the source properties (type, position, direction, etc.) except the amount of photons. I decided to harness this and hash each experiment setup (scene and source hash combination - the hash excludes the amount of photons !) and use it in an IPP hash table. So when given a new experiment, the IPP is first unknown and the procedure goes as follow:

A first measure of the IPP is done by propagating a small batch of 1000 photons (IPP_TEST_N_PHOTONS). This is safe and fast to do so, and the logger size is set using a first gross estimate of IPP by assuming an infinite medium with the mean albedo of all the materials present in the scene. This assures that we first overshoot IPP and allow the test to run without memory issue, but also assures it runs fast by limiting the logger size to a relatively small size. This test takes around 1 second for most examples.
With this first IPP estimate (n_samples=1000), the program launches the desired user experiment with an already good logger size and propagates, let's call it, "N_user" photons.
Now that the user propagation is done, the IPP is measured again with greater precision (n_samples=1000 + N_user).
This IPP value is stored in a hash table file (ipp.json) under the hash corresponding to the user experiment setup (again: scene and source properties, excluding number of photons).
If the experiment is run again (with or without the same amount of photons), no IPP test has to be done. The IPP value is directly loaded from the hashtable. After each new propagation on the same experiment hash, the IPP is updated (the hashtable stores the IPP value alongside the number of samples to date for each experiment it has seen).

The hash table file is in the repository and already includes the IPP value for all example experiments. I removed automatic git tracking of this file.
Limitations

I really need to test the N_WORK_UNITS automatic test on other hardware.

Love this! The implementation of the IPP and the N_WORK-UNIT + the graph and the prompt for the user is simple and efficient to show the user the infleunce of the WORK-UNIT on the speed. I love it. However, I dont quite understand why it is always fast no matter the number of work untis. It seems the more the better.


Update cats-core to 2.3.1

Updates org.typelevel:cats-core from 2.1.1 to 2.3.1.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-core" } ]

Applied Migrations

github:typelevel/cats/Cats_v2_2_0?sha=v2.2.0

Documentation:

https://github.com/typelevel/cats/blob/v2.2.0/scalafix/README.md#migration-to-cats-v220

labels: library-update, semver-minor, scalafix-migrations

Superseded by #67.


chore: avoid certain CLI logs showing up in unit test

Description
cleanup the unit tests logs
Motivation and Context
simply want a cleaner unit test log output
How Has This Been Tested?

Types of changes

[x] Chore (change that has absolutely no effect on users)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

nothing I've tried so far seem to remove these extra logs, let's close this for now and maybe revisit later


Build test for the web doesn't include webassembly

https://github.com/cunarist/rust-in-flutter/blob/dbb8bbb59b0c03df74465f96866b40b64c721bf6/.github/workflows/ci.yaml#L70-L72
Building webassembly before web build test is needed like this:
...
      - name: Build Web
        working-directory: example/
        run: |
          dart run rust_in_flutter wasm --release
          flutter build web
...

However, for some reason, dart run rust_in_flutter wasm fails on GitHub CI. This command works well on local, so the reason of this CI behavior is not clear yet.
https://github.com/cunarist/rust-in-flutter/actions/runs/5852524994/job/15864901475

@bookshiyi It seems that there's a room for improvment here 😐

@temeddix yeah! I have tried to add to my test branch and debugging now.
ci.yaml

@bookshiyi It looks like there's a room for improvment here..! 😐

  # For web target
  - name: Setup WASM Toolchain
    if: matrix.target == 'web'
    run: cargo install wasm-pack

I think this might be effective.

Okay :)
Also, let me mention that dart run rust_in_flutter wasm command includes automatic installation of wasm-pack and nightly Rust, so we do not need(and shouldn't) manual installation of wasm-pack or other web-related tools, as can be seen here:
https://github.com/cunarist/rust-in-flutter/blob/dbb8bbb59b0c03df74465f96866b40b64c721bf6/bin/rust_in_flutter.dart#L144-L168

Initially, I did indeed run only the command dart run rust_in_flutter wasm, but GitHub Actions prompted that wasm-pack was missing. That's why I tried to add the step for manually installing wasm-pack.
Thank you for providing this crucial information, and I will continue to troubleshoot the issue.

Happy to hear your progress on that!

Okay :)
Also, let me mention that dart run rust_in_flutter wasm command includes automatic installation of wasm-pack and nightly Rust, so we do not need(and shouldn't add) manual installation of wasm-pack or other web-related tools in the CI.
https://github.com/cunarist/rust-in-flutter/blob/dbb8bbb59b0c03df74465f96866b40b64c721bf6/bin/rust_in_flutter.dart#L144-L168

You are right, some strange issues have arisen here like your description.
I misunderstood your description earlier, and now I am trying to debug.

PR #89

Fixed by #89


[Research] Content Complexity Categorization

Description
For products that enforce rendering budgets, or SLAs for rendering time we need a way to quantify the complexity of content, and assign it a weighted value to represent its cost on the user device.
Explore static analysis approaches for Player content for categorizing based on complexity.
Outcome
This research task should create a new enhancement issue for final implementation, with guidance on approach from this research.

Basic example started in this branch with a couple to-dos

[ ] Get nested bindings/expressions working. Right now since we stop processing them after they are first detected they never fall through to finish the rest of the processing. I mocked out the basic interface for the model/expression evaluator so that might need to get fleshed out a bit more to do more parsing without having to do processing.
[ ] Identify and weight nodes with Template functionality. Templates are a runtime hit for Player to expand the template so we should increase the weight of any nodes within a template (and increase that weight for compound templates) but for that we'll need to be able to determine if any node is the child of a template node which is something we currently can't do as part of the LSP. This is something we'll need to do though in general as we expand validation functionality (related #91 )
[ ] Determine more accurate weighting of node types

Made #162 to track next steps


multiple probes/shanks neural data

hello , I am recording from multiple npx shanks simultaneously in each session . I dont know how to select all lfp and Ap data and add them to aquisition module using nwb-guide ?

Until we add the SpikeGLXConverter option, the workflow you'll have to use is:
Select one AP and one LF Interface from the interface selection page per imec probe
For the source data page on each interface, choose a different AP/LF band from a different probe for each interface
We plan to extend the tutorial to generate multi-probe multi-gate example SpikeGLX format to better showcase this feature

@parviz-gh By the way, we're currently looking for alpha testers to do one-on-one walkthroughs with
If you'd be interested, you can sign up for it here with this link

Hi @parviz-gh, I'm clearing out some old issues
The current release of the GUIDE (v0.0.15) and current main branch support ecephys metadata from multiple recording interface which could correspond to different probes (to be indicated as different devices through the app)
Is it OK if I close this now?


Support File.ReadAllLinesAsync and friends on .NET Core 3 / netstandard2.1

Solves #499, but to do that I added a new netstandard2.1 target. As an example, if you look here, you'll see these async methods were there since netcoreapp2.0 but only available starting with netstandard2.1: https://docs.microsoft.com/en-us/dotnet/api/system.io.file.readallbytesasync?view=netstandard-2.1
I'm not fully sure if this will magically work for the nuget releases, nor if the build server can actually build it (it needs the now-stable preview 8 of .net core 3), but if you want you can merge this after the official .net core 3 release!

The Ubuntu image seems to have the correct .NET Core SDK now. Windows images don't seem to work yet. Let's just hang on :)

Thanks a lot for your contribution!


html api pagination broken

http://amplify.bacalhau.org/api/v0/queue?order=DESC&page=1&perPage=10&sort=meta.submitted

Ah, using the wrong API: http://amplify.bacalhau.org/api/v0/queue?sort=-meta.submitted
Need to update the links to do this/default to this.


Add link to awesome in README.md

I'll think about that. In order to enter in that list this awesome list must change a lil bit.
read more at https://github.com/sindresorhus/awesome/blob/main/create-list.md


[Sidebar] Sidebar left fixed menu (toggle) + top fixed menu

Hello everyone,
i have a top fixed menu which is full size in width and i want to have a left sidebar which open/close on button under this top fixed menu. It works nice when i dont set context in sidebar but on open it also moved top fixed menu to right because the context of sidebar is default set up on BODY. When i use context it works fine that the sidebar toggling under top fixed bar but when i scrolling context this sidebar isnt fixed ... Can someone help me with that?... Sorry for my bad english. Thanks

I'm seeing this as well. The docs say http://semantic-ui.com/modules/sidebar.html#/usage under Using Fixed Content to place the fixed menu as a sibling of the sidebar. But for me this doesn't work with a fixed menu at the bottom.
I think it's because the parent of both the sidebar and the menu gets a pushable class and this performs a css transform. When css transform happens, position: fixed children get positioned relative to the transformed element. So the menu appears at the bottom but does not keep scrolling with the viewport. Thoughts?

Hi @romanmuska, the issue is quite old, and I’ll be closing it as a usage question, but if you think it’s an actual problem with the framework, or you’d like to propose a specific feature request—feel free to provide a test case as per our contributing guidelines (you can fork this JSFiddle), and someone will reopen it.


compile error when using const ocilib::Collection &  as parameter

Hello Vincent.
I have a problem with compiling the code below  . The code is from demo/coll.cpp .
`void print_const_coll_by_index(const ocilib::Collectionocilib::Object & coll)
{
std::cout << "fetch using const index access" << std::endl;
    unsigned int i = 1, n = coll.GetCount();

    for (; i <=n ; i++)
    {
        auto elem = static_cast<ocilib::Object>(coll[i]);
       // some code here
    }
}`

and here is the compile time error :
/usr/local/include/ocilibcpp/detail/Collection.hpp:491:13: error: invalid conversion from ‘const ocilib::Collection<ocilib::Object>*’ to ‘ocilib::CollectionElement<ocilib::Object>::CollectionType*’ {aka ‘ocilib::Collection<ocilib::Object>*’} [-fpermissive]   491 |     return  CollectionElement<T>(this, index);       |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~       |             |       |             const ocilib::Collection<ocilib::Object>*

If i change function declaration and remove const , the code will get compile successfully.

void print_const_coll_by_index(ocilib::Collection<ocilib::Object> & coll)
My OS is fedora  34 and gcc version is 11.2.1
Thanks a lot.

Hi again Vincent.
is there any way for me to change ocilib code and build it again to solve this issue.
I'll be really grateful if you could give me some hint to fix this.
Thanks a lot .

Hi.
I tried to change ocilib code to solve this issue . so here is what i did .
In types.hpp file , i change the constructor and private member of CollectionElement class . so here is the changed code.
`    template
class CollectionElement
{
template
friend class CollectionIterator;
public:

    typedef T ValueType;
    typedef Collection<ValueType> CollectionType;

    CollectionElement();
    CollectionElement(const CollectionType * coll, unsigned int pos);
    operator T() const;
    CollectionElement& operator = (const ValueType& other);
    CollectionElement& operator = (const CollectionElement& other);
    bool IsNull() const;
    void SetNull();

private:

    const CollectionType * _coll;
    unsigned int _pos;
};`

I also changed the implementation of constructor in CollectionElement.hpp file .
and I think it did the trick . It seems that it solved my problem .

Hi,
The code from demo/coll.hpp compiles fine under Windows.
I will check again with GCC (might have forgot to test it under GCC)
If I get same issue, I will address it in v4.7.5
Regards,
Vincent

Hi,
the issue seeems logical - MSVC seems to to detect it.
I will fix differently by adding a const_cast to remove the const on this in Collection::operator [](unsigned int index) const


No module named 'custom_components.frigate.4 on 4.0.0-beta2 with Frigate 0.12.0-beta3

Version of the custom_component
4.0.0-beta2
Configuration

Not sure where to find the config.
Describe the bug
The integration fails to load with an error.
Debug log

I can enable debug logs but there's way too much garbage (it's over 3 MB) so this is what showed in info mode.
2023-01-14 00:17:16.516 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration frigate which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-01-14 00:17:16.519 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration frigate which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-01-14 00:17:16.521 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration frigate which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-01-14 00:17:52.692 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration frigate: Unable to import component: No module named 'custom_components.frigate.4'

Looks like something didn't download right. Suggest redownloading the integration.

Huh I had renamed the old version of the integration instead of deleting it, but deleting it fixed it. Now I'm wondering how it never broke before when I did that.


Fix compile issue in master.

This just fixes the compile error that is currently in master branch. Please make sure that the logic is correct, I just made assumption about what its supposed to be.

Great, thanks! @CharlesWoodhill and @aikixd could any of you have a quick look and check whether the logic is correct?

I'll merge it in the meantime since it breaks the build.
@CharlesWoodhill and @aikixd can still confirm if it was OK, or otherwise submit a PR to adjust this.


Update README.md

cp is not supported on the windows command prompt. I've added copy instead.

Thank you!


cert-manager: download resources into travis cache

fixing one of the issues in https://github.com/IBM/the-mesh-for-data/issues/88 by using a local cache (backed up by travis)
error: unable to read URL "https://github.com/jetstack/cert-manager/releases/download/v0.13.1/cert-manager.yaml", server reported 429 too many requests, status code=429

I would say let's not do this via some caching mechanism but just download the file locally and push it into git.


plss UPDATE

I know that GTA V update was big, but i need mods xD, plss update

Come on, don't make issues to complain about not updating SHVDN (this plugin) before Script Hook V (SHV) is updated.
We need to do some tests because the vehicle class (CVehicle) was changed at least. I can test with RPH and update some vehicle memory offsets, but we should test entire SHVDN system after SHV gets updated.


feat: UI upgrade

+remove yarn, use npm

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


Timeout when attempting to run any docker commands after starting a machine

I am unable to run any docker, docker-compose commands after bringing up a docker machine.  I am able to SSH to the image without any issues and I have confirmed it is running on the IP address listed by docker-machine ip <name>.
Version Info

docker-machine version 0.1.0
Docker version 1.5.0, build a8a31ef
Virtual Box 4.2.28 (also tried 4.3.26)
Mac OS 10.10
docker-machine ip <name>: <IP_ADDRESS>

Trace from docker-compose up -d
Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/compose.cli.main", line 31, in main
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/compose.cli.docopt_command", line 21, in sys_dispatch
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/compose.cli.command", line 27, in dispatch
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/compose.cli.docopt_command", line 24, in dispatch
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/compose.cli.command", line 59, in perform_command
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/compose.cli.main", line 445, in up
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/compose.project", line 184, in up
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/compose.service", line 253, in recreate_containers
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/compose.service", line 122, in containers
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/docker.client", line 519, in containers
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/docker.client", line 81, in _get
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/requests.sessions", line 395, in get
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/requests.sessions", line 383, in request
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/requests.sessions", line 486, in send
  File "/Users/ben/fig/build/docker-compose/out00-PYZ.pyz/requests.adapters", line 387, in send
requests.exceptions.Timeout: (<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x1046ad290>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=60)')

Error from docker ps
docker ps
FATA[0032] An error occurred trying to connect: Get https://<IP_ADDRESS>:2376/v1.17/containers/json: dial tcp <IP_ADDRESS>:2376: i/o timeout

Hi @miskander, I'm assuming you set the environment variables using $(docker-machine env <name>) method?  Could you please print the output of :

docker-machine ls
docker-machine env <name>
env | grep DOCKER

@nathanleclaire Thanks, I did run that after the machine was created. Here is the output of those commands:
docker-machine ls
NAME   ACTIVE   DRIVER       STATE     URL                         SWARM
dev    *        virtualbox   Running   tcp://<IP_ADDRESS>:2376

docker-machine env <name>
export DOCKER_TLS_VERIFY=yes
export DOCKER_CERT_PATH=/Users/USERNAME/.docker/machine/machines/dev
export DOCKER_HOST=tcp://<IP_ADDRESS>:2376

env | grep DOCKER
DOCKER_HOST=tcp://<IP_ADDRESS>:2376
DOCKER_TLS_VERIFY=yes
DOCKER_CERT_PATH=/Users/<username>/.docker/machine/machines/dev

Great, thanks.  Are you behind any kind of VPN or corporate proxy, or have anything funky happening in your networking configuration that you can think of?

So my answer was going to be nope, all is normal and VPN is off as I tried that before. But what I decided to do was test again before I respond since I do use VPN throughout the day. I deleted vboxnet0 interface though before I tried again, and low and behold it works. I probably provisioned the first machine while on VPN and the interface was just funky from that.
Sorry for the superficial issue.

No worries @miskander.  Thanks for reporting!

I've actually had this issue as well, when going from one network to another. Suspend and re-start docker  typically resolves that issue for me.

This solves the issue for me...
$ killall -9 VBoxHeadless && docker-machine restart <env>

This solved the issue for me
docker-machine start dev

Thanks @Telemakhos that sorted my network issues out as well. I didn't have any VPN on my networks but it was still failing.

'docker-machine ls'
'docker-machine restart '
worked for me to resolve error with docker compose connection timeout error.  Thanks

Also, I try to run command:
docker-machine.exe env default

and get i/o timeout
I'm trying to fix it with next command:
docker-machine.exe regenerate-certs default

And got docker-machine message:

This machine has been allocated an IP address, but Docker Machine could not reach it successfully.
SSH for the machine should still work, but connecting to exposed ports, such as the Docker daemon port (usually :2376), may not work properly.
You may need to add the route manually, or use another related workaround.
This could be due to a VPN, proxy, or host file configuration issue.
You also might want to clear any VirtualBox host only interfaces you are not using.

After this I clear unused host-only interfaces directly in VirtualBox after this regenerate certs again and all looks fine for now.
Software:

Windows 10
Virtualbox 5.0.14
Docker-toolbox 1.9.1i

Thank You @nukalasr. It worked for me.

'docker-machine ls'
'docker-machine restart '
worked for me

[root@weikang weikang]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         gateway         <IP_ADDRESS>         UG    100    0        0 eth0
instance-data.e gateway         <IP_ADDRESS> UGH   100    0        0 eth0
<IP_ADDRESS>     <IP_ADDRESS>         <IP_ADDRESS>   U     100    0        0 eth0
<IP_ADDRESS>    <IP_ADDRESS>         <IP_ADDRESS>   U     0      0        0 vboxnet0
[root@weikang weikang]# docker-machine ls
NAME    ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER        ERRORS
myvm1   *        virtualbox   Running   tcp://<IP_ADDRESS>:2376           v18.05.0-ce
myvm2   -        virtualbox   Running   tcp://<IP_ADDRESS>:2376           v18.05.0-ce
[root@weikang weikang]# docker node ls
error during connect: Get https://<IP_ADDRESS>:2376/v1.37/nodes: Gateway Timeout
[root@weikang weikang]#
I got above error following the docker docs,
'docker-machine ls'
'docker-machine restart ' doesn't help.
Docker VM installed on cloud environment, fedora 27.

@telemakhos 'killall -9 VBoxHeadless' this did the trick. After hours of searching, thank you.


Interleaving Datasets Bug Fix

Currently, before interleaving the pubmed_dataset_streamed and law_dataset_streamed datasets, the meta feature isn't being dropped and that's why there's a misalignment in the meta feature causing a ValueError.
Updated the section to drop the meta feature before interleaving the datasets.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Thank you very much for the fix @Shamik-07 ! I was able to reproduce the error on my end and so would you mind propagating the code change (not the text) to all the other languages please?
I think a global find and replace in e.g. VS Code will do this quite easily

I had already propagated it to the code en language and created a PR for the same, i have propagated the same code changes to all the translations available.
Since this PR is for the text, i have also propagated the same changes to the text.


Truncate branchName (if necessary) to meet RFC 1035 criteria

Truncating branch name according to RFC 1035 if necessary
Maximum length is 63 characters.
Read more: https://vercel.com/guides/why-is-my-vercel-deployment-url-being-shortened

Hi, I've encountered an issue with this solution. Overall, it's been working fine, but I've noticed a problem with branches that have "-" in their names, such as "feature/some-functionality-that-describe-branch-name".
While truncating fixes the issue for large branch names, if the truncation ends with "-", it triggers the following error: "Error: Invalid alias. Please confirm that the alias you provided is a valid hostname. Note: For vercel.app, only sub and sub-sub domains are supported."
I believe this feedback could be valuable for improving the tool. Hopefully, you'll find time to address this issue. 😊
I appreciate the effort you put into enhancing the developer experience by providing such tools. However, I've tried explaining this frustration in a support ticket, but unfortunately, no one seemed to understand it.

Thank you for raising this @RobertoArmas
We have released a fix for this


Google Slides

As of 11/05/2021 this system will not display presentations from Google Slides. No ideas as to why currently. Seems like it will display literally anything else in my testing. As I do use this system for work i'm actively troubleshooting.

As of 11/17/2021, Google Slides functionality has returned. After losing my mind troubleshooting and not actually changing anything, it miraculously started working again.


Fix image card responsiveness

What

when image card drops below 320px (unlikely, admittedly) it collapses into a single column but the margins are broken
also the sass is a bit confusing
this commit restructures the sass to make it more readable and fixes this problem
behaviour should be (for standard image card): from 320px two columns, from 640px one column
behaviour is perhaps not ideal (mobile with two columns is a little squished in some cases) but changing it is outside scope
this commit does not change the behaviour, it only fixes the brokenness below 320px

Why
The likelihood of anyone using a device narrower than 320px is very low, but this PR also makes the code more readable. Having said that, I'm not 100% sure I understand the new govuk-frontend V3 mixins for breakpoints and columns.
Visual Changes
Before:

After:

I've checked this in collections (component is used on org pages) and the behaviour appears to be as before but includes the fix.
View Changes
https://govuk-publishing-compo-pr-1055.herokuapp.com/component-guide/image_card

Not unlikely in the future - also since Apple Watch can now open links.
The watch browser can either say it has a screen of 320px wide, or - if we add a meta tag - it will claim to have a screen < 320px wide. More about designing web content for the Apple Watch.


How can I inject codes after entity created

I found I can customize a IStateManager to inject ef core to modify entities. But if a query is under no tracking mode, ef core will not reach IStateManager.
I also found I can customize a IEntityMaterializerSource to reach entity through 'Expression'.
But, I need ef's IServiceProvider where I injected. I need to get value from service and set the value to property of entity.
How can I inject codes where entity have being created with no tracking mode?

I found a solution.
Create a class inherit StateManager and override StartTrackingFromQuery.  Do something with entity we need and return null.
But, we can't tracking entities while querying if we need it to be tracked.

@Kation I think what you are looking for is the ObjectMaterialized event, which isn't implemented yet but is being tracked by issue #626.
All the services you reference are internal code. You can try to get something working with them, but it will likely be quite difficult and may get broken by any update of EF Core, so very much do so at your own risk. Probably IEntityMaterializerSource is the most appropriate service to try this with if you do decide to take this approach.


Troubleshooting and updating documentation for Mac flow while building Sandbox Localdev container

Description:
Troubleshooting and updating documentation for Mac M1 (ARM architecture) flow while building Sandbox Localdev container

PR for this task:
https://github.com/bcgov/platform-services-registry/pull/2209


Support Redhat OS family distribution major version 8

Splits the task according to OS family.
For Redhat family major version 7 installs:
 - libselinux-python
 - libsemanage-python
 - policycoreutils-python

And for major version 8 installs:
 - python3-libselinux
 - python3-libsemanage
 - policycoreutils-python-utils

Addresses #9. The failure here has the knock-on effect of causing the ome.omero_web role to fail on Redhat major version 8.

Hi @sbesson - Apologies that this has been negelected for so long! I have made the following changes:

Remove support for Debian
Put tasks back into main.yml
Add molecule scenario for RockyLinux8
Addressed linting

Thanks @drmatthews. Although I am still periodically involved in the maintenance of these Ansible roles, I have changed affiliation and I think both the specific changes and generally the platform support decision will need the input from some of the OME maintainers who I added as reviewer.
With CentOS 7 becoming officially EOL in June 2024, note in particular https://www.openmicroscopy.org/2023/07/24/linux-distributions.html which highlights OME's roadmap in terms of platform support. Rocky Linux 9 and Ubuntu 22.04 are the two candidates so overall this effort aligns with some of the ongoing audit of the roles spearheaded by @pwalczysko. To the best of my knowledge, it is still undecided if the aim of these roles is to support both environments or focus on the one primarily used by the OME team.

I'll wait for a response from the OME team.

@drmatthews Thank you for this and sorry for the belated response. As stated in https://www.openmicroscopy.org/2023/07/24/linux-distributions.html, the two platforms supported by the OME Team will be Rocky Linux 9 and Ubuntu 22.04. If any additional platforms should be considered, we need an institution to take ownership of the maintenance, not a single individual, otherwise the burden to maintain the new platform will fall on the OME Team.
Hope this position, although very strict, makes sense.
Thanks again
Best wishes
Petr
OME Team


cmd/cue: fmt emits invalid CUE when constraining numbers to be less-than a negative number

What version of CUE are you using (cue version)?
$ cue version
cue version v0.6.0

go version go1.20.6
      -buildmode exe
       -compiler gc
       -trimpath true
     CGO_ENABLED 0
          GOARCH amd64
            GOOS linux
         GOAMD64 v1

Does this issue reproduce with the latest stable release?
Yes, 0.6.0.
What did you do?
# 1st vet succeeds
exec cue vet file.cue
# 1st fmt succeeds
exec cue fmt file.cue
# file is now formatted
cmp file.cue file.cue.formatted
# 2nd fmt fails
exec cue fmt file.cue
# 2nd vet fails
exec cue vet file.cue
-- file.cue --
x: -10
x: > -15
x: < -5
-- file.cue.formatted --
x: -10
x: >-15
x: <-5

I tried to constrain a negative number to be both less-than and greater-than 2 other negative numbers, and found that

the parser treats less-than and greater-than constraints on negative numbers differently, when spaces are removed between the comparison operators and the negative numbers

such that a space is required between the less-than operator and the negative number, but isn't required with the greater-than operator

cue fmt emits CUE that ignores this requirement

(1) feels like a bug, but as there might be some subtle reason for this behaviour I'll let the triager of this Issue file that if needed.
(2) seems to me to /definitely/ be a bug.
I couldn't find existing Issues for either of these.
What did you expect to see?
A passing testscript.
Also, ideally, I'd prefer the form x: <-10 (without the space) to be valid CUE.
What did you see instead?
$ testscript -continue negative-bounds.txtar
# 1st vet succeeds (0.051s)
# 1st fmt succeeds (0.053s)
# file is now formatted (0.002s)
# 2nd fmt fails (0.040s)
> exec cue fmt file.cue
[stderr]
expected operand, found '<-':
    ./file.cue:3:4
[exit status 1]
FAIL: /tmp/testscript487171359/negative-bounds.txtar/script.txtar:8: unexpected command failure
# 2nd vet fails (0.020s)
> exec cue vet file.cue
[stderr]
expected operand, found '<-':
    ./file.cue:3:4
[exit status 1]
FAIL: /tmp/testscript487171359/negative-bounds.txtar/script.txtar:10: unexpected command failure
error running negative-bounds.txtar in /tmp/testscript487171359/negative-bounds.txtar

The two issues are related, but note that one relates to the parser and the other one to the formatter.
Either way I agree that there's at least one bug here.

Note that there's a possibility that <- becomes an operator in some future CUE version, which needs to be taken into account when fixing this issue.


Gardening for @dynamicMemberLookup.

Unify code style of @dynamicMemberLookup and @dynamicCallable implementations.

Use consistent variable names, diagnostic names/messages, doc comments, etc.

Move @dynamicMemberLookup test to test/attr directory.

New consistent naming:

invalid_dynamic_callable_type, invalid_dynamic_member_lookup_type
DynamicCallableCache, DynamicMemberLookupCache
isValidDynamicCallableMethod, isValidDynamicMemberLookupSubscript

This PR is almost NFC. The only user-facing change is a new error message for invalid_dynamic_member_lookup_type.

cc @lattner: could you please review?

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test

This all LGTM, but please fix the attr/attr_dynamic_member_lookup.swift failure.

Sorry, tests failed because I updated the diagnostic message without updating tests.
@swift-ci Please smoke test


LSP server initialization does not respond

This may be a bug upstream, but I haven't been able to reproduce it in VSCode, so I'm reporting here in case this appears to be an obvious problem with LSP-volar.
Reproduce steps:

Unzip volar-starter-with-nodemodules.zip and open it in Sublime.
Open App.vue
Open LSP logs, you should see the initialization request sent, but no response received.

It's worth noting that if you delete node_modules and reinstall it via pnpm i, LSP will work fine.

We should handle that better on the LSP side by not just silently closing the server but this happens because we've received an unexpected payload on stdio. In this case it's
"Error: Cannot find module '@volar-plugins/prettyhtml'

Require stack:
- /Users/rafal/Downloads/volar-starter-with-nodemodules/volar.config.js
- /usr/local/workspace/github/volarjs/vue/node_modules/.pnpm/@volar+language-server<EMAIL_ADDRESS>- /usr/local/workspace/github/volarjs/vue/node_modules/.pnpm/@volar+language-server<EMAIL_ADDRESS>- /usr/local/workspace/github/volarjs/vue/node_modules/.pnpm/@volar+language-server<EMAIL_ADDRESS>- /usr/local/workspace/github/volarjs/vue/node_modules/.pnpm/@volar+language-server<EMAIL_ADDRESS>- /usr/local/workspace/github/volarjs/vue/packages/vue-language-server/out/nodeServer.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:963:15)
    at Module._load (node:internal/modules/cjs/loader:811:27)
    at f._load (node:electron/js2c/asar_bundle:2:13330)
    at Module.require (node:internal/modules/cjs/loader:1035:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/Users/rafal/Downloads/volar-starter-with-nodemodules/volar.config.js:3:9)
    at Module._compile (node:internal/modules/cjs/loader:1141:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1196:10)
    at Module.load (node:internal/modules/cjs/loader:1011:32)
    at Module._load (node:internal/modules/cjs/loader:846:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/Users/rafal/Downloads/volar-starter-with-nodemodules/volar.config.js',
    '/usr/local/workspace/github/volarjs/vue/node_modules/.pnpm/@volar+language-server<EMAIL_ADDRESS>    '/usr/local/workspace/github/volarjs/vue/node_modules/.pnpm/@volar+language-server<EMAIL_ADDRESS>    '/usr/local/workspace/github/volarjs/vue/node_modules/.pnpm/@volar+language-server<EMAIL_ADDRESS>    '/usr/local/workspace/github/volarjs/vue/node_modules/.pnpm/@volar+language-server<EMAIL_ADDRESS>    '/usr/local/workspace/github/volarjs/vue/packages/vue-language-server/out/nodeServer.js'
  ]
}
Content-Length: 1906

"

I suppose that VSCode is either more permissive in handling stdio or it uses nodeipc instead (we can do that yet due to reliance on Python 3.3).
I will still try to make some fix in LSP to surface those issues to the user.

And of course Volar should also post such errors to stderr and not stdout and either close itself or respond with error to initialize.

I see that you are actually using Node IPC for communicating with Volar in VSCode. Such issues don't affect IPC communication.

This is the problem line:  https://github.com/volarjs/volar.js/blob/master/packages/language-server/src/common/utils/serverConfig.ts#L17
I guess I should try to use connection.logger instead of console.log?

Yes. Or console.error but I suppose console.error would not be surfaced anywhere when using IPC so connection.logger seems more appropriate.

Thanks for confirming, I'll track it upstream.

I'll move this to LSP repo to handle this case better. It happened with eslint and other servers before.


Add custom implementation of iter methods.

@ateska What is the best way to test the changes in cysimdjson? I noticed that in Dockerfile, it is being installed from master from GIT.

Relates to: https://github.com/TeskaLabs/cysimdjson/issues/5

@ateska You're right. Should be fixed now.

@ateska Tried something with the native string conversion to Cython. Please check, if it s a proper direction.


BTC Replace by Fee (RBF) feature: Allow a BTC transaction to be replaced with a higher fee

Enabling the RBF feature (allowing transactions to be replaced) is easy, but how to sign and send the same transaction again is a problem. The issue is that when we got the UTXOs to construct a transaction, we got them from the btc-assets-api. And once the transaction is constructed, it no longer contains some required properties for us to "reverse" the whole construction process and convert a Transaction to a PSBT.
For example, how does the process know which output (vout) in the transaction can be altered in order to pay more fees? And besides, what's the dust limit for each output? Since outputs can be normal UTXOs (dust_limit=1,0000) or RGBPP UTXOs (dust_limit=546)._limit=546).
Originally posted by @ShookLyngs in https://github.com/ckb-cell/rgbpp-sdk/issues/37#issuecomment-2020233486
References

https://bitcoinops.org/en/topics/replace-by-fee/

Opt-in Full Replace-by-Fee Signaling
https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki
two ways a transaction can signal that it is replaceable:

Explicit signaling: A transaction is considered to have opted in to allowing replacement of itself if any of its inputs have an nSequence number less than (0xffffffff - 1).
Inherited signaling: Transactions that don't explicitly signal replaceability are replaceable under this policy for as long as any one of their ancestors signals replaceability and remains unconfirmed.

full-RBF allows any transaction to be replaced whether or not it signals BIP125 replaceability.

Bitcoin Core 0.24.0 includes a mempoolfullrbf configuration option that allows enabling full-RBF
See https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-24.0.1.md#notice-of-new-option-for-transaction-replacement-policies

Full RBF
Here's an example of Full RBF processed on testnet. Let's look at the stats:

TX_1:  1 input, 2 outputs, 1 sat/vB fee rate, not sequenced (no Opt-in RBF support)
TX_2: 3 input, 3 outputs, 50 sat/vB fee rate, it referenced the same inputs[0] as TX_1

You can review the TX_2 here: fc081ae0faca52c421e6d7c3e37cb62f4e3ef3701fd4b42ce0bfc4045a3eb817.
The two transactions have the same inputs[0], outputs[0], and outputs[1]. The idea was to not overcomplicate things at first, and just start simple by ignoring the existing inputs/outputs (don't edit them at all) in TX_1. The stretegy gives us the advantage of avoiding unknown issues and still achieving our goal: transaction acceleration.
However, this method also has a disadvantage: In order to construct the RBF transaction (TX_2), the sender must have a balance more than sufficient, and additionally, the sender must have at least one more UTXO in the wallet.
TX_1
Transaction
{
  version: 2,
  locktime: 0,
  ins: [
    {
      hash: <Buffer b4 35 45 08 e6 0a 6b 23 2e a6 68 4a ae ed 97 9d ec 31 03 31 f5 e7 76 c0 1b d2 f2 f1 d3 f4 1f d8>,
      index: 1,
      script: <Buffer >,
      sequence:<PHONE_NUMBER>,
      witness: [Array]
    }
  ],
  outs: [
    {
      script: <Buffer 00 14 db f4 36 0c 07 91 09 8b 0b 14 67 9e 5e 78 01 5d f3 f2 ca ad>,
      value: 1000
    },
    {
      script: <Buffer 00 14 db f4 36 0c 07 91 09 8b 0b 14 67 9e 5e 78 01 5d f3 f2 ca ad>,
      value: 5846
    }
  ]
}

Hex
02000000000101b4354508e60a6b232ea6684aaeed979dec310331f5e776c01bd2f2f1d3f41fd80100000000ffffffff02e803000000000000160014dbf4360c0791098b0b14679e5e78015df3f2caadd616000000000000160014dbf4360c0791098b0b14679e5e78015df3f2caad024730440220051d74a7330739b7c5e33cdac67378ec972e6688d585bc8f4f2b2dc3c45e034d02204b5c6edc230871b5a717453d8c43bd712ef52eab9d596863e54d16b6ce2ebe5e0121037dff8ff2e0bd222690d785f9277e0c4800fc88b0fad522f1442f21a8226253ce00000000

TX_2
Transaction
{
  version: 2,
  locktime: 0,
  ins: [
    {
      hash: <Buffer b4 35 45 08 e6 0a 6b 23 2e a6 68 4a ae ed 97 9d ec 31 03 31 f5 e7 76 c0 1b d2 f2 f1 d3 f4 1f d8>,
      index: 1,
      script: <Buffer >,
      sequence:<PHONE_NUMBER>,
      witness: [Array]
    },
    {
      hash: <Buffer 61 e1 32 7f e8 f2 9b c3 28 fe 1a b1 1a da da 38 2d ec b6 4a be 1a fd 06 91 4f c5 e8 98 b7 39 67>,
      index: 0,
      script: <Buffer >,
      sequence:<PHONE_NUMBER>,
      witness: [Array]
    },
    {
      hash: <Buffer 61 e1 32 7f e8 f2 9b c3 28 fe 1a b1 1a da da 38 2d ec b6 4a be 1a fd 06 91 4f c5 e8 98 b7 39 67>,
      index: 1,
      script: <Buffer >,
      sequence:<PHONE_NUMBER>,
      witness: [Array]
    }
  ],
  outs: [
    {
      script: <Buffer 00 14 db f4 36 0c 07 91 09 8b 0b 14 67 9e 5e 78 01 5d f3 f2 ca ad>,
      value: 1000
    },
    {
      script: <Buffer 00 14 db f4 36 0c 07 91 09 8b 0b 14 67 9e 5e 78 01 5d f3 f2 ca ad>,
      value: 5846
    },
    {
      script: <Buffer 00 14 db f4 36 0c 07 91 09 8b 0b 14 67 9e 5e 78 01 5d f3 f2 ca ad>,
      value: 827110
    }
  ]
}

Hex
02000000000103b4354508e60a6b232ea6684aaeed979dec310331f5e776c01bd2f2f1d3f41fd80100000000ffffffff61e1327fe8f29bc328fe1ab11adada382decb64abe1afd06914fc5e898b739670000000000ffffffff61e1327fe8f29bc328fe1ab11adada382decb64abe1afd06914fc5e898b739670100000000ffffffff03e803000000000000160014dbf4360c0791098b0b14679e5e78015df3f2caadd616000000000000160014dbf4360c0791098b0b14679e5e78015df3f2caade69e0c0000000000160014dbf4360c0791098b0b14679e5e78015df3f2caad02473044022043941307f1541b408c9d97345ece962fac4dca1a586fb8f9bea9117eb6fcaac7022038d2cbe37a31800decde535e6cf366de52ddfdec78ac56259751cd533239d6690121037dff8ff2e0bd222690d785f9277e0c4800fc88b0fad522f1442f21a8226253ce02473044022002cfed86d563c2d488e9af576bc63562720a32e7e8e2b16243abad84b37b15c7022039cdc2de0bb47ab170a1e6f39022d894555b4730cd08185a0588c892792c3c060121037dff8ff2e0bd222690d785f9277e0c4800fc88b0fad522f1442f21a8226253ce02483045022100aede6ebc905c25ae7d8d2316ab7569d946ce4c29c90c77380df96aae8d2ea0070220295ed0d980c65292682663ec8169287b916569772501cb4a018dde5a6adeb4ff0121037dff8ff2e0bd222690d785f9277e0c4800fc88b0fad522f1442f21a8226253ce00000000

TX_1 was replaced by TX_2

Discussion
Let's say TX_1 has an isomophic rgbpp_ckb_tx_virtual. And there is a job of TX_1 in the assets-api's RGB++ CKB transaction Queue, called TX_1's job.
How to automatically add TX_2's job to the RGB++ CKB transaction Queue when TX_1 is replaced by TX_2?

Monitor Bitcoin Mempool, and detect TX_1 Replacement
Continuously monitor the Bitcoin mempool for any new transactions that spend one of the inputs of TX_1.
When a new transaction (TX_2) spending inputs from TX_1 is detected, identify if TX_2 is a replacement for TX_1 based on criteria like higher fee rate, same inputs, etc.

Verify TX_2 Validity
Verify that TX_2 is a valid RGB++ transaction by checking if it contains the right RGB++ commitment.

Add TX_2's Job to Queue
Add a new job for TX_2 to the RGB++ CKB transaction Queue, including the TX_2_txid and the related rgbpp_ckb_tx_virtual, a.k.a TX_1's rgbpp_ckb_tx_virtual.

Why this feature is required?
Sometimes the RBF BTC transaction is submitted by other BTC RBF service providers, not through rgbpp-sdk. in this case, the TX_2's job may not be processed.
This process ensures that when TX_1 is replaced by TX_2 on the Bitcoin network, the RGB++ CKB transaction Queue is automatically updated with the new job for TX_2, allowing for seamless processing of the BTC RBF workflow.
Priority: Low

Monitor Bitcoin Mempool, and detect TX_1 Replacement

Maybe these API can help:

GET Mempool RBF Transactions: https://mempool.space/testnet/docs/api/rest#get-mempool-rbf
GET Mempool Full RBF Transactions: https://mempool.space/testnet/docs/api/rest#get-mempool-fullrbf
GET Transaction RBF History: https://mempool.space/testnet/docs/api/rest#get-transaction-rbf-history


Plan Architecture for Donna

See https://docs.google.com/document/d/1ZPISzJEnbK3d7o9YS_jmvuUUHh2tKESrMbIg89uK-yM/edit#

DNode was recommended for Node.js to Node.js communication: https://github.com/substack/dnode

How about using Babel (ES6 to 5 transpiler) for Node.js source code? See https://babeljs.io/

Rename Cortex plugin to Brain plugin? Hubot just calls it a brain, sounds simple enough.

Since all plugins are registered in the form of:
function(donna) {
   // register plugins
}

would it make sense to omit/remove the donna argument from each of the functions?
For instance, the current registration API for IntentExtractors is as follows:
            // Text to Intent extractor
            donna.registerIntentExtractor({
                name: "test",
                description: "This is a Test Intent Extractor",
                dataTypes: ["text"] // supported input data types
            }, function(donna, input, cb) {
               // Note the `donna` being passed in here!
           });

Should that donna argument even be there? Or simply use the "global" donna that is provided in the initial function(donna) { } wrapper?

Consider this the very basic, first iteration, foundation for Donna.

For more Brain-related terms: http://www.human-memory.net/brain_neurons.html


Add flow-types.el to MELPA

Or some other repository for Emacs packages.

The Emacs package now lives at: https://github.com/flowtype/flow-for-emacs
Please open an issue there if this is still important to you 😊


Error: Cannot find module 'react/lib/React' on React version ^16.2.0

It looks like react-unit has the version of react-test-renderer locked at 15.5.4 which may be incompatible with react version 16.x judging by this stack overflow post: https://stackoverflow.com/questions/46692073/jest-fails-cannot-find-module-react-lib-react-from-reactshallowrenderer-js-a
I did do some mild testing and it looks like upgrading react-test-renderer to version 16.x can resolve this issue.
Error: Cannot find module 'react/lib/React'
    at Function.Module._resolveFilename (module.js:555:15)
    at Function.Module._load (module.js:482:25)
    at Module.require (module.js:604:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (<project_root>/node_modules/react-unit/node_modules/react-test-renderer/lib/shallow/ReactShallowRenderer.js:18:13)
    at Module._compile (module.js:660:30)
    at Object.Module._extensions..js (module.js:671:10)
    at Module.load (module.js:573:32)
    at tryModuleLoad (module.js:513:12)
    at Function.Module._load (module.js:505:3)
    at Module.require (module.js:604:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (<project_root>/node_modules/react-unit/node_modules/react-test-renderer/shallow.js:3:18)
    at Module._compile (module.js:660:30)
    at Object.Module._extensions..js (module.js:671:10)
    at Module.load (module.js:573:32)

Let me know if you have any other questions about my specific system or configuration to help debug this.
p.s. this library looks really cool 👍 looking forward to using it on my projects!

Created a PR that i think should fix the issue: pzavolinsky/react-unit#28

Hi @epfremmer thanks for this contrib!
I've merged your pzavolinsky/react-unit#28 PR and published a new version of react-cucumber with updated deps!
Thanks again,
Cheers!

@pzavolinsky happy to help!


docs updates s6c5a

This PR adds some cleanups to use create / mutate for SC methods and closes #130. There are some other smaller additions for cleaning up tutorials related to this as well as small markdown formatting changes. A few other smaller docs updates are a WIP and will be later added to this branch.

Oh, cool—mind giving me a 👍 on this @brunocalza (these are straightforward updates) and then I can make your changes live, too.


Introducing Dashboard

Dashboard will be the new home page after login.

The work is completed. https://github.com/hydroshare/hydroshare/pull/3301


Property 'compilation' of undefined ProgressPlugin

Error
><EMAIL_ADDRESS>dev /Users/harlequindoyon/Sites/project-nuxt
> nuxt

  nuxt:build App root: /Users/harlequindoyon/Sites/project-nuxt/src +0ms
  nuxt:build Generating /Users/harlequindoyon/Sites/project-nuxt/.nuxt files... +1ms
  nuxt:build Generating files... +54ms
  nuxt:build Generating routes... +7ms
  nuxt:build Building files... +20ms

 ERROR

  TypeError: Cannot read property 'compilation' of undefined

  - ProgressPlugin.js:121 ProgressPlugin.apply
    [project-nuxt]/[webpack]/lib/ProgressPlugin.js:121:19

  - Tapable.js:375 Compiler.apply
    [project-nuxt]/[nuxt]/[tapable]/lib/Tapable.js:375:16

  - webpack.js:33 webpack
    [project-nuxt]/[nuxt]/[webpack]/lib/webpack.js:33:19

  - builder.js:524 compilers.compilersOptions.map.compilersOption
    [project-nuxt]/[nuxt]/lib/builder/builder.js:524:24

  - Array.map

  - builder.js:523 Builder.webpackBuild
    [project-nuxt]/[nuxt]/lib/builder/builder.js:523:39

  - builder.js:168 Builder.build
    [project-nuxt]/[nuxt]/lib/builder/builder.js:168:16

Version
☁  project-nuxt [master] ⚡ vue -V
3.0.1

+1

+1

+1

+1

+1

I have the same issue.

nuxt 1.4 depends on webpack 3, whereas vue cli 3 is using webpack 4.
But nuxt 2 uses webpack 4! So
npm rm nuxt npm i nuxt-edge
can solve this issue


changes

Goal
The goal of this PR is
Closes
Discussion

Checklist

[ ] Chain spec updated
[ ] Custom RPC OR Runtime API added/changed? Updated js/api-augment.
[ ] Design doc(s) updated
[ ] Tests added
[ ] Benchmarks added
[ ] Weights updated

@enddynayn closing this for now, but if there is anything you think should be merged, feel free to re-open.


[CI] add script to generate meta info and upload to s3

I would like to add a meta file to describe the latest xgboost nightly build info including xgboost version and commit id, and then upload it to s3, the file looks like that,
meta.xml
<?xml version="1.0" encoding="UTF-8"?>
<root>
  <version>2.1.0.dev0</version>
  <commit>ee2afb3256ce2f333c0da56408dfc7360bbf8b7a</commit>
</root>

Hi @hcho3 Could you help review it.

Some questions:

Should the meta info be encoded as XML? Why not a JSON?
Can we use a Python script to generate the XML file, to be consistent with other utility scripts in the repo? I can write the equivalent Python script.
Should meta.xml encode the latest nightly version of manylinux2014_x86_64 wheel specifically? Sometimes the CI might break and a nightly build may be available for amd64 but not manylinux2014_x86_64.

Hi @hcho3, It would be great if you can help on that.

I've written a script to generate meta.json like this:
{
    "platform_tag": "manylinux2014_x86_64",
    "version": "2.1.0.dev0",
    "commit_id": "6d65b593c65d130c1d67c6c5a1a1ba13c5b148f6"
}

First, we can wget meta.json and parse it and get the platform/version/commit_id and then compose them with "https://s3-us-west-2.amazonaws.com/xgboost-nightly-builds/master/" to get the download link.

Would it be useful to also include the full name of the wheel file in meta.json too?

Would it be useful to also include the full name of the wheel file in meta.json too?

Hmm, yeah, good idea.


Unable to install development version on MacOS due to requirements

I tried installing the repository requirements using both pip and conda, and I run into troubles with both (see error logs).
I was able to install the development version by removing the specific package version requirements from the requirement.txt file.
The only conflict was to use numpy<2.0, this could either be added to the requirement.txt file, or the project could be made compatible with the latest numpy version (preferable). It seems only a single method is deprecated in numpy 2.0, from running the tests:
AttributeError: `np.string_` was removed in the NumPy 2.0 release. Use `np.bytes_` instead.. Did you mean: 'strings'?

conda_error_log.txt
pip_error_log.txt

This is really an issue with Tensorboard dependency rather than with DRDMannTurb itself; see the below.
Numpy 2.0 API compatibility issue #6869
Update usage of numpy to reflect numpy 2.0 changes #6871
This has been merged and is on their nightly builds, so I believe all will be well with the next release.
Is it fine to temporarily fix numpy<2.0?

Yes that would be fine, also the drdmanturb from the pre-compiled wheel does not pass tests at the moment due to changes in the numpy API, so you could temporarily add numpy<2.0 in setup.py, then eventually replace it with a minimal Tensorboard version.
Also, you could specify in the development installation instructions that re-creating the exact conda environment is not mandatory (if not possible), and that you can just run pip install -e .  to use the development version, and dependencies will be resolved based on  "install requires" in setup.py.

I can redo the wheels once things are more or less finalized.
#103 pins numpy<2.0 in setup.py.
I should have caught this sooner, but our instructions in README were misleading -- the conda spec-file.txt was for Linux64 and therefore doesn't work on macOS (I myself am on an M2), but I didn't really see any clear indication that this was the issue in the error logs conda gave me (which, on my end, were about identical to what you provided in the OP) nor did we indicate that this would be an issue in the instructions. Just "unexpected error occurred".
I have included a more general environment.yml and moved all Conda environment exports under conda_env_files.
(As a sidenote, I am getting notifications about security risks with our dependencies from Dependabot; these are immediately resolved by bumping the versions up with the many PRs it has open currently. I will merge those before redoing the wheel so that tests pass)


Define merge operation in minervaJSON specification

A non-Noctua use case in merging models, e.g. for analysis or visualization.
A naive OWL-level merge will render all model-level annotations at the top level. This is not a massive issue for analysis applications that will ignore these anyway. But it would be useful to retain knowledge of which model each node and edge belonged to.
An alternate way to conceive of a merge is as a collection of models (akin to imports in OWL). The data model would then be:
models : [
  model1,
  ...
]

Where model_N would the current mJSON spec.
Alternatively, we may prefer to merge, but have the merge operation add additional axiom annotations. This may be easiest for retaining 1:1 between OWL and JSON

This should probably be thought about in the light of geneontology/noctua#112.
Another approach would be to simply decorate nodes and edges with metadata and let the client deal (easy enough to sort into different graphs before render, for example).
As well, would need coordination with https://github.com/berkeleybop/bbop-response-barista.


Add Basic Auto Schema Generation Implementation

This PR is basic implementation of a AutoSchema and is still a work in progress.

Thanks, I will work on this as well as discussed.
We will fully implement autoschema in this branch and we will merge to master before v2.


Paso todos los refactors realizados y logica de turnos a Development

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

118 of 118 (100.0%)  changed or added relevant lines in 6 files are covered.
19 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-9.2%) to 90.777%

Files with Coverage Reduction
New Missed Lines
%

repository/IngSoft2-Model/SpaceShipPosition.class.st
19
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-9.2%

Covered Lines:
187

Relevant Lines:
206

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

118 of 118 (100.0%)  changed or added relevant lines in 6 files are covered.
19 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-9.2%) to 90.777%

Files with Coverage Reduction
New Missed Lines
%

repository/IngSoft2-Model/SpaceShipPosition.class.st
19
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-9.2%

Covered Lines:
187

Relevant Lines:
206

💛  - Coveralls


App crashes when video recording starts on Sony Xperia Z5 Compact

Steps to reproduce

Open camera app
Try to capture video

Expected behaviour
Video should be recorded
Actual behaviour
App crashes directly without any logged errors when the recording with the back camera starts. It works with the front camera.
Environment

Node.js version: 5.11.0
React Native version: 0.39.0 and earlier
React Native platform + platform version: Android 6.0
Device: Sony Xperia Z5 Compact

react-native-camera
Version: 0.4.1 and earlier
The app was tested on following devices
-Samsung Galaxy S4: OK
-Samsung Galaxy S5: OK
-Samsung Galaxy S5 Neo: OK
-Samsung Galaxy S7: OK
-Sony Xperia Z5 Compact: FAIL
So the app crashes only on the tested Sony and only when using the back camera. Every tested Samsung devices worked fine.

Do you have a crash log from adb?

No. I was watching logcat while it happened but it wasn't any error message there. The app just crashed. Problem is I don't have access to a Sony so I can't really test it more.

@krillov I have tried using the example code. The camera works fine and saves the images however the video recorder crashes without logging in both the front and back camera. I tried in on a Samsung Galaxy S5. I believe the error is in the startRecording method of the example, specifically here.
   this.camera.capture({mode: Camera.constants.CaptureMode.video})             .then((data) => console.log(data))             .catch(err => console.error(err));         this.setState({           isRecording: 'true'         });
The capture method doesn't seem to accept the capture mode as video and crashes for some reason. I can't seem to get any log in the terminal while running it. Any idea what could be wrong?
React Native Version 0.40.0
React Native Camera 0.6.0

@blaziken105 Sorry, I have no idea. I use exactly the same code as you do. Only difference is I haven't updated to version 0.40 yet. I'm not a JS expert and it has probably nothing to do with the crash but aren't you using string instead of boolean for isRecording?
let options = {
  mode: Camera.constants.CaptureMode.video,
  target: Camera.constants.CaptureTarget.cameraRoll
};
this.camera.capture(options)
.then(data => {
  ...
})
.catch(err => {
  console.log(err)
})

@krillov seems like a typo, its supposed to be a boolean...

This issue is closed because of inactivity.
Furthermore RCTCamera is deprecated now, use RNCamera instead. If this issue is also related to RNCamera, please open a new one.


True double buffer with SPI DMA in ESP32

Hi,
I am creating a lvgl project in ESP32.
Display driver: ST7735S (Max 13MHz SPI CLK)
LCD: 160*128 pixels
ESP32 CLK: 160MHz
Been trying to figure out what can be done to reduce lv_task_handler duration and to increase FPS.
My problem is:

lv_task_handler() last for a really long time (~70ms in my case with 1/4 buffer) and sometimes exceed 100ms if UI is complicated
Tried using screen-sized double buffer with SPI DMA, to render while flushing (as stated in LVGL documents)
-- But after some digging in the lvgl code, I found the following code in lv_refr.c

In every flush callback:

Started SPI DMA
1601282*8/13000000=~25ms to flush the whole screen
lv_disp_flush_ready() called in the DMA complete callback to clear "disp_drv->buffer->flushing = 0"
"while(vdb->flushing);" is called after "lv_refr_vdb_flush();"
Doesnt that make the lv_task_handler() just wait for the SPI DMA to finish?
But the double buffer is supposed to render while SPI DMA is in progress

Also, I failed to put lv_disp_flush_ready() inside SPI DMA callback
Can anyone help to suggest how to implement this?

Hi,
With a screen-sized double buffer, LVGL assumes that the flushing is only the frame buffer address change. It's not the case in your configuration as you need to send the image to the display via SPI.
If you want screen-sized buffers but not "true double buffering" just use screen_size+1 sized buffers.
See the different buffering modes here: https://docs.lvgl.io/latest/en/html/porting/display.html#display-buffer

Hi,
Oh I see!
So if I want to "render and flush in parallel" I should not be using "true double buffer" (2 screen sized buffer).
Instead I should configure the buffers size to screen size +1 to avoid "true double buffer" but still enjoing "rendering and flushing" in parallel?
Thanks for the help anyway, been struggling to understand the buffer configurations


Compatibility with DeepL api (and maybe other translators).

It's great that finally you can have a UWP api of a translator, although personally I like to use DeepL translator (just now I'm using it), and it occurred to me that maybe you can add compatibility with this api and other translators, if possible.

if its possible I think it would awesome if the app could show both Google Translate and DeepL translations to have a rough idea of which one is more accurate!
Theres also papago

That would require your own key. The 500K char limit per month (i'm talking about DeepL) is kind of rough for more users, but it certainly is a possibility to concider later. Thank you so much for the suggestion!


family_circle_plotter error: cannot find symbol

I have not seen this answered elsewhere.
Hello, when I run family_circle_plotter I get this output error and I can't find information on the web to solve my problem. I would be greatful for any advice.
family_circle_plotter.java:303: error: cannot find symbol
Cubic xSpline = new Cubic(Cubic.BEZIER, GX);
^
symbol: class Cubic
Am I missing a required library or something?
Thanks very much in advance

Ok. Do this before running the family_circle_plotter
$ javac Cubic.java
$ javac family_circle_plotter.java

easier: just go to that directory and make


Move .NET Solution to Spec based approach for running unit-tests

This PR contains the necessary work to migrate the current C# Test projects to a Spec based approach, that can be re-used across platforms.
The Spec files were automatically generated based on the assertions of the original Test projects.
The .NET solution references only the new DataDriven Test project and runs all test cases based on the Spec files.
The original (and now deprecated) test projects are still available using the Microsoft.Recognizers.Text.with.Deprecated.Tests.sln

@pcostantini,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


WIP: Static function

move global variables to be allocated inside static function to support compiling LST in CMSSW_13_2 or later. From this CMSSW version, it introduces ROCm backend, and complains about no device found.

Now the global variables in Event.cc and ModuleConnectionMap.cc are put into classes and functions.

This PR is very useful if we want to port the global variables into static functions. Especially the trick it uses to deal with the module map variables can be used as templates for more variables. Unfortunately, this effort didn't go through the end. But all the global variables are documented in the LST Object Building Selections document. For further reference and work to implement this, refer to https://docs.google.com/document/d/1MZqSnR-q8YmWN0X4CZIjjV2mYRVW8UxCZnn1NR34ppw/edit?usp=sharing


Tests failing on PyPy

These tests passed on pypy in #4630, but failed on the release job (https://github.com/pypa/setuptools/actions/runs/10692324985).
Originally posted by @jaraco in https://github.com/pypa/setuptools/issues/4630#issuecomment-2329777151

I also note that PyPy went from 7.3.16 to 7.3.17 between those builds.

What's even more weird is that those tests are run with SETUPTOOLS_USE_DISTUTILS=stdlib, so the failing test should be skipped.
I'm attempting to replicate the issue using act --job test --matrix python:pypy3.10 --matrix platform:ubuntu-latest --matrix distutils:stdlib --container-architecture linux/amd64

The first attempt to repro ran into an issue with some of the workers failing then it just hung:
4.1, subprocess-1.5.2, checkdocs-2.13.0
| Warning: cannot find your CPU L2 cache size in /proc/cpuinfo
created: 8/8 workersWarning: cannot find your CPU L2 cache size in /proc/cpuinfo
initialized: 1/8 workersWarning: cannot find your CPU L2 cache size in /proc/cpuinfo
initialized: 2/8 workersWarning: cannot find your CPU L2 cache size in /proc/cpuinfo
initialized: 3/8 workersWarning: cannot find your CPU L2 cache size in /proc/cpuinfo
initialized: 4/8 workersWarning: cannot find your CPU L2 cache size in /proc/cpuinfo
initialized: 5/8 workersWarning: cannot find your CPU L2 cache size in /proc/cpuinfo
initialized: 6/8 workersWarning: cannot find your CPU L2 cache size in /proc/cpuinfo
8 workers [1525 items]
| ss.s.................................................................... [  4%]
| ........................................................................ [  9%]
| .................................................................x...... [ 14%]
| .....................................................F.................. [ 18%]
| ....................................................................s... [ 23%]
| ..............s.................................X....................... [ 28%]
| ....X........................................s................s.s.s.sss. [ 32%]
| .ss.ss.s................................................................ [ 37%]
| ........................................................................ [ 42%]
| ............x...................x.........x....x........................ [ 47%]
| ............................................................x........x.. [ 51%]
| ..........x[gw4] node down: Not properly terminated
| F
| replacing crashed worker gw4
| Warning: cannot find your CPU L2 cache size in /proc/cpuinfo
collecting: 8/9 workers.[gw6] node down: Not properly terminated
| F
| replacing crashed worker gw6
| Warning: cannot find your CPU L2 cache size in /proc/cpuinfo
10 workers [1525 items] .[gw2] node down: Not properly terminated.s..x.............
| F
| replacing crashed worker gw2
| Warning: cannot find your CPU L2 cache size in /proc/cpuinfo
collecting: 10/11 workers..[gw3] node down: Not properly terminated
| F
| replacing crashed worker gw3
| Warning: cannot find your CPU L2 cache size in /proc/cpuinfo
collecting: 11/12 workers[gw1] node down: Not properly terminated
| F
| replacing crashed worker gw1
| Warning: cannot find your CPU L2 cache size in /proc/cpuinfo
^C[tests/test]   ❌  Failure - Main Run

Not idea what that's all about. Maybe my system went to sleep when I walked away.

It hung again a second time, this time with only two  but again, I walked away during the run. It takes a very long time. I'll try again.
Ugh. Tried again and this time it failed early. I think it may be running low on resources, but I have no idea which.

In https://github.com/pypa/setuptools/actions/runs/10710763767/job/29698171478, I've added some debugging and confirmed that SETUPTOOLS_USE_DISTUTILS=local, so something must be munging the environment.

When I run the test in isolation, the test is skipped as expected. So there is indeed some interference from other tests.

In https://github.com/pypa/setuptools/actions/runs/10710992997/job/29698838140, I added a fixture to check that os.environ['SETUPTOOLS_USE_DISTUTILS'] doesn't change for any given test, and none of the tests failed that check, so how is that possible?

The failure doesn't happen for me locally, even with the same PyPy version.

In https://github.com/pypa/setuptools/actions/runs/10712709409/job/29703544680, I've had some success detecting when the env var changes. It looks like it's one of the tests in test_integration is altering it. That sort-of makes sense, as it's running code from outside the repo within the environment, so it can mutate the environment. But why PyPy only, and why CI only?

In 84a0079ec, I ran the tests sequentially so that the offending test can be identified. The job output implicates test_novaclient (or maybe test_pbr):
setuptools/tests/test_integration.py::test_pbr PASSED                    [ 83%]
setuptools/tests/test_integration.py::test_python_novaclient XFAIL       [ 83%]
setuptools/tests/test_integration.py::test_python_novaclient XFAIL       [ 83%]
setuptools/tests/test_integration.py::test_pyuri ERROR                   [ 83%]

Something else that's odd and interesting - that novaclient test is run twice. Why would it run twice?

In https://github.com/pypa/setuptools/actions/runs/10713178150/job/29704803966, I've proven that it's the test_python_novaclient that's triggering the issue:
py: commands[0]> pytest -p no:xdist -v -k 'pyuri or novaclient'
============================= test session starts ==============================
platform linux -- Python 3.10.14[pypy-7.3.17-final], pytest-8.3.2, pluggy-1.5.0 -- /home/runner/work/setuptools/setuptools/.tox/py/bin/python
cachedir: .tox/py/.pytest_cache
rootdir: /home/runner/work/setuptools/setuptools
configfile: pytest.ini
plugins: checkdocs-2.13.0, ruff-0.4.1, cov-5.0.0, jaraco.vcs-2.4.0, perf-0.15.0, home-0.6.0, xdist-3.6.1, subprocess-1.5.2, jaraco.test-5.4.0, enabler-3.2.0, mypy-0.10.3, timeout-2.3.1
collecting ... collected 1525 items / 1523 deselected / 2 selected
setuptools/tests/test_integration.py::test_python_novaclient XFAIL       [ 50%]
setuptools/tests/test_integration.py::test_python_novaclient XFAIL       [ 50%]
setuptools/tests/test_integration.py::test_pyuri ERROR                   [100%]
==================================== ERRORS ====================================
_________________________ ERROR at setup of test_pyuri _________________________
    @pytest.fixture(autouse=True)
    def check_setuptools_use_distutils():
        import os

        orig = os.environ.get('SETUPTOOLS_USE_DISTUTILS')
>       assert orig == 'stdlib'
E       AssertionError: assert 'local' == 'stdlib'
E
E         - stdlib
E         + local
conftest.py:84: AssertionError

Okay. That test is marked as xfail, and if that tests fails twice (normally, then an error in teardown), then it will be reported twice (as xfail). If I run with --runxfail, the causes are clearer:
FAILED setuptools/tests/test_integration.py::test_python_novaclient - DeprecationWarning: The 'wheel' package is no longer the canonical location...
ERROR setuptools/tests/test_integration.py::test_python_novaclient - RuntimeError: SETUPTOOLS_USE_DISTUTILS changed from stdlib to local.
ERROR setuptools/tests/test_integration.py::test_pyuri - AssertionError: assert 'local' == 'stdlib'

That's why I didn't see the "changed from stdlib to local" sooner - the xfail marker was masking it.
I scanned the novaclient code for the environment variable, but I see nothing referencing it, but I'm seeing now there are other packages involved (dependencies, presumably).

In 99e58a82f, I've confirmed that pyyaml is implicated, and indeed pyyaml sets the variable in its setup.py (ugh). But that still doesn't explain why the issue doesn't occur on other platforms. Maybe it has something to do with wheels and caching?
In any case, I'm mostly uninterested in fixing this test. It's been marked as xfail for some time and is testing a deprecated code path (easy_install), so let's just get rid of it (and probably the other integration tests for easy_install).

For posterity, I pushed the commits for this issue to refs/archive/triage/4632


fix(warm_up_cache): JSON serialization

SUMMARY
A byproduct of https://github.com/apache/superset/pull/23012/, when warming a non-legacy chart it's valid for the error to be a babel form of Empty query? which is not JSON serializable, i.e., json.dumps(...) raises the following error:
TypeError: Object of type LazyString is not JSON serializable

The fix to to use the the base_json_conv serialization method. Having json.dump(...) splattered throughout the code is rather unfortunate as there's no consistency in how payload are serialized. Ideally exceptions should be raised and handled in a uniform way per SIP-41.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS
Added unit test.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

I tried this patch with superset 2.1.0, unfortunately it didn't help, legacy charts don't properly show error message, endlessly showing loading gif, whereas worker show this in its log:
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/ss_venv/lib64/python3.8/site-packages/celery/app/trace.py", line 477, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/ss_venv/lib64/python3.8/site-packages/superset/initialization/__init__.py", line 108, in __call__
    return task_base.__call__(self, *args, **kwargs)
  File "/ss_venv/lib64/python3.8/site-packages/celery/app/trace.py", line 760, in __protected_call__
    return self.run(*args, **kwargs)
  File "/ss_venv/lib64/python3.8/site-packages/superset/tasks/async_queries.py", line 95, in load_chart_data_into_cache
    async_query_manager.update_job(
  File "/ss_venv/lib64/python3.8/site-packages/superset/utils/async_query_manager.py", line 187, in update_job
    event_data = {"data": json.dumps({**job_metadata, **updates})}
  File "/usr/lib64/python3.8/json/__init__.py", line 231, in dumps
    return _default_encoder.encode(obj)
  File "/usr/lib64/python3.8/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib64/python3.8/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/usr/lib64/python3.8/json/encoder.py", line 179, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type LazyString is not JSON serializable

Closing in favor of https://github.com/apache/superset/pull/24671.


⚠ Bofrost.at has degraded performance

In e0776e2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1557 ms

Resolved: Bofrost.at performance has improved in 2a1caf0.


Home screen background change

Is your feature request related to a problem? Please describe.
Choose a dynamic background
Describe the solution you'd like
NA
Describe alternatives you've considered
NA
Additional context
No response

Could you explain more to see how to contribute to the project?


Webpack upgrade

Are there any plans on updating webpack.
Webpack 4 has this --mode switch, which can simplify webpack configuration files.

I tried to update it, but there are some packages that were not working without doing anything. If you can help :) I think that @MarkPieszak would be happy.

@salixzs on my branch, I was able to update pretty much everything in order to make it work. However I have the following message (warning, however, I don't know at what extent it affect the modules):
fail: Microsoft.AspNetCore.NodeServices[0]
      (node:4060) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
fail: Microsoft.AspNetCore.NodeServices[0]
      (node:4060) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead

See my branch if you want to try out/fix it:
https://github.com/Nordes/aspnetcore-Vue-starter/tree/feature/85-webpack-Update
Related to the messages: https://github.com/aspnet/JavaScriptServices/issues/1499

Nice job @Nordes ! :+1:
I think we just need to update ExtractTextPlugin in the package.json
https://github.com/webpack/webpack/issues/6568
If that works we can definitely upgrade it and get those awesome perf boosts 🥇
You guys rock!

You guys are awesome, I come across this problem to come here and see it actively being solved, Fantastic!

@mark actually the extract text plugin is updated on my branch. However, the depreciation warning is regarding NodeServices (link between Dotnet core and node webpack). The warning doesn't stop the application from warning (see link in my previous reply). Later today I'll do some cleanup and if you're OK to have the text plugin in `rc' and the warning stated earlier than I'll do the pull request.

That'd be amazing :+1:
Whatever you think will help !

Thank you for trying. I believe problems will not end as I doubt we can get --mode switch from libraries between aspnet core and webpack (JavaScript services, webpack middlewares etc.)

@salixzs if you look at my branch I use the - - mode development while in dev and production when publishing the app. I don't understand your comment? Basically you could even push it using a dot net environment variable.
Actually I added it in the webpack configuration file (both of them).

Sorry I cannot contribute enough to you. I am just investigating possibilities in my (small) free time.
Also I am doing it from scratch (TypeScript version) just looking in this great repository for reference - how you, smart guys, are doing this.
I was hoping to go more heavy on using --mode switch value in webpack config file, like this:
module.exports = (env, argv) => {
    const isDevBuild = argv.mode === 'development';

when you run this from Visual Studio Build, then this works, because it is added in csproj file, just like in your branck, BUT, when you want those hot reloading bells and whistles, then existing middleman solutions does not provide this switch and webpack is failing.
Of course, it can be handled in webpack config file, but to have nice and clear Webpack 4 solutions - it is yet something we have to wait from other repos to implement,
P.S. I believe you can also remove const OptimizeCSSPlugin = require('optimize-css-assets-webpack-plugin') from webpack config as it is also now done by Webpack, but I may be wrong here (still learning this stuff).

has anyone gotten JavaScriptServices debugging working with webpack4? i doesn't seem to hit the break points. I think it has to do with the way chunking has changed, but not sure. I can still however hit break point in Chrome web developer, but not VS

For debugging vue file (period), it's not so easy. Here's a post from last year: https://forum.vuejs.org/t/debugging-vue-files-with-visual-studio-code/8022/5 . Was it working with the Webpack 2 or it's a regression in this project?

@Nordes thank you, this was exactly what I needed to upgrade to webpack 4.
One small note is that if you update the vue-loader to 15, need to add a plugin to webpack, as per https://vue-loader.vuejs.org/migrating.html#a-plugin-is-now-required

@Nordes @MarkPieszak
I have complied the template provided by dotnet cli with webpack 4. I am just a starter in this, but successfully did it, but need your help on confirming the same.
I removed all the old components which are marked deprecated for webpack 4 except the aspnet-webpack one. Alternative need to find didn't spent much time on it.
Please let me know, if you can help in verifying, i will share the details later for the changes.
Note: - Not using babel yet.

Hi @pank789!!
Can you fork this repository and commit your proposed changes to the forked version so we can take a look?? I'll go ahead and try it on my machine to help verify. :smile_cat:
Let me know if you need any help or have any questions! Feel free to email me (my email is in my profile).
Mikael

hi Mark,
I will do that ,but would some need time as i am having trouble with my
laptop and other one doesnt allow github to be accessed, since have acess
restriction on it.
Thanks
Pankaj N
On Tuesday, July 10, 2018, Mikael Stadden<EMAIL_ADDRESS>wrote:

Hi @pank789 https://github.com/pank789!!
Can you fork this repository and commit your proposed changes to the
forked version so we can take a look?? I'll go ahead and try it on my
machine to help verify. 😸
Let me know if you need any help or have any questions! Feel free to email
me (my email is in my profile).
Mikael
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MarkPieszak/aspnetcore-Vue-starter/issues/85#issuecomment-403704865,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AnGnR3ariBV6JHyKl8seWuY5DbYrUxyNks5uFDuxgaJpZM4Sutdw
.

Np! Just let me know, excited to take a look! @pank789

@MarkPieszak  @Nordes  I have updated my repo with the webpack 4 changes.
I am not aware how you run via the script from the package. json. I did it using vs 2017 build and tested the code is compiling and running fine and debugging in chrome.
I updated remaining libs to latest expect the one related with fontawesome, those have some issue and i am not aware of them at all.
Please check the three files, package.json, webpack.config.js, webpack.config.vendor.js.
Note: i havent work on optimization part, as i am new bie to webpack and JS frameworks.

@Nordes I'm unable to get the debugging to work.
What does your launch.json look like?

I tested the above and it worked on my end, using it for a possible production project