fix the background color of the sidebar on 'medium' sized devices

Proposed changes
This fixes #11366 by adding the background color for the correct class name. It
seems that .sidebar-home used to be used a lot, but I couldn't find its usage
anywhere (when loading up the docs app), so I stuck to using .sidebar, which
seemed to work :smile:
Unreleased project version (optional)

Related issues (optional)
Fixes #11366

Thanks @ingshtrom. Looks like the issue still exists

Oops! I fixed this, and then noticed that the header and side-bar changes color (black navbar, and darker sidebar) at the lowest resolutions. I fixed that, but maybe it was purposeful. Please let me know if it was and I can roll that back.

Thank you @ingshtrom. It looks fine to me. @StefanScherer Do you mind taking another look when you get a chance? Thanks.

Oh, man.... I also noticed the search input changes based on the size of the screen... I'll fix that too.

PTAL. I think I got it this time. Mobile portrait and landscape are looking good. Just making a desktop screen smaller is looking good.


Add client info collecting

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ x ] Requirement

Requirement or improvement
There is a situation  that we have many nodes would submit the data to central service, there were be slowly or fast, we did't found the slowly request where does it from? Why does it be slowly?
If we can collect the original datas from request, the client ip, that it will be a easy way to  improve our system.
Otherwise,  we are also like to collect the stacktrace when a exception thrown.
Sincerely hope that features will be provided.
Best wish to Skywalking Team!
Thanks!

Thanks for your feedback. It is exciting to have this, considering .net agent project is so young.
Let me clear about your proposals.

What do you mean about original data? http request parameter? If so, have you considered that, this is a high payload features. Do you system have resources, e.g. CPU, memory, network, for this.
Exception stack should be collected by agent, if there is no catch to just log the exception.This needs @liuhaoyang 's confirm.
Apache SkyWalking backend show every service and server( node) performance, which may could help you find out the pattern, whether some service or server have a long latency.

Collect the exception messages and http request logs are already in the plan.

@wu-sheng
Thanks for your reply.

What do you mean about original data? http request parameter? If so, have you considered that, this is a high payload features. Do you system have resources, e.g. CPU, memory, network, for this.

Yes, hope to consider set a configuration to turn on/off the request parameter.
Also, My I know got the Content-Length or Request headers has more effect for service  performance?

Exception stack should be collected by agent, if there is no catch to just log the exception.This needs @liuhaoyang 's confirm.

As @liuhaoyang  remind before, we will trace the exception at next version.

Apache SkyWalking backend show every service and server( node) performance, which may could help you find out the pattern, whether some service or server have a long latency.

It's more convenient to help us improve service performance. Thanks for your contributions.
Regards.

I have already supported record http request logs and exception stacks in https://github.com/OpenSkywalking/skywalking-netcore/pull/42.

Yes, hope to consider set a configuration to turn on/off the request parameter.

@carterHe Someone used to ask for this in SkyWalking-java. I am open to those settings, but I have to say, implement these requires a lot of time. So this depends on the community.


Add support for Wildcard Types in Feign Client.  Fixes gh-1676

Codecov Report

Merging #1926 into master will increase coverage by 0.03%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1926      +/-   ##
=========================================
+ Coverage   75.67%   75.7%   +0.03%
=========================================
  Files         209     209
  Lines        6343    6343
  Branches      794     794
=========================================
+ Hits         4800    4802       +2
+ Misses       1203    1201       -2
  Partials      340     340

Impacted Files
Coverage Δ

...ork/cloud/netflix/feign/support/SpringDecoder.java
60% <0%> (ø)
:arrow_up:

...a/server/EurekaServerInitializerConfiguration.java
79.31% <0%> (+6.89%)
:arrow_up:

Continue to review full report at Codecov.

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

@ryanjbaxter Yea, makes sense.  Updated the PR


Enable self-hosted kubelet updates by default

Self-hosted kubelet updates were disabled because Flatcar Stable is shipping a runc version with a bug that caused updates to be unstable.
When a Flatcar Stable release with a newer runc is out, we should validate it and enable self-hosted kubelet updates by default.

A new Flatcar Stable release with an updated runc is expected next week.


Should we complete the fee waiver even if the party is not indigent?

Might need more discussion. It seems answer is mostly no, except maybe if the party requests an attorney (possibly a different indigency standard?)

Maybe leave as is for now. It would be rare to not "qualify" since it just asks you if you can afford to pay if you are over income, and then generates the supplement.


No need to import built in Types

Use built in type hints to reduce import penalty

We extract to B logic to another library. So can you fix conflicting files, so we can review and merge it?

Why can't I find that file? Where is it?

Not release now, will release soon.

@yuvalabou  Here is the to B logic library https://github.com/tuya/tuya-connector-python


Timeseeking doesn't work in IE

Had to do a talk in IE due to no other browser being installed (yeah that's sad)
But i realised seeking/selecting time does not work in player.
Seems like IE's event is returning NAN values.

This has been recently fixed.


It is possible to show progress when I post JSON with application/json content-type?

I tried to post a large json (contain base64 image string) by using
Alamofire.request(.POST, "https://httpbin.org/post", parameters: parameters, encoding: .JSON,).progress {  (bytesWritten, totalBytesWritten, totalBytesExpectedToWrite)  in }.
I understand that I can use upload or formdata to achieve that. I wonder to know if we can use the request function to do that instead of upload().

You certainly can use the request method to do this, but I would encourage you to use upload instead. The reason is that the request method progress tracking only reports downloading progress of the response data. It will not report upload progress.
The upload APIs will report the upload progress to the server and do not report download progress of the server's response data. Because of this, I'm sure you'd prefer the upload APIs in this situation.
Cheers. 🍻


Add terrain splines

Description
Can you add terrain splines and terrain slopes, similar to the terrain tools in Unreal?

What specifically do you mean by terrain splines and terrain slopes? Slopes can already be created with the slope tool. Isn't this a duplicate of #280 or #129.

Oh, sorry. I didn't see where the terrain spline is. You can refer to this website: https://dev.epicgames.com/documentation/en-us/unreal-engine/landscape-splines-in-unreal-engine

Duplicate #280

OK. Thank you.


Replicate metadata standards from CWL recommendation

Feature Request
Desired behaviour
We should duplicate the metadata recommendations from the CWL tutorial on the Dockstore site for the time-being.

Documented at https://staging.dockstore.org/docs/best-practices for now


Chrome set up issue in AWS

Hi I have done all the proper set up in AWS.  But when I started running it  by the below command but not getting anything on terminal.
universe) $ cd ~
(universe) $ git clone https://github.com/openai/universe-starter-agent.git
(universe) $ cd ~/universe-starter-agent
(universe) $ python train.py --num-workers 2 --env-id gym-core.PongDeterministic-v3 --log-dir /tmp/vncpong
$ tmux a
Can anyone help me on this.

Need more detail. What do you see after running tmux a? What does docker ps show?

Attached the o/p that I am seeing after running tmux a

I have gone through the blog but nowhere it is mentioned about the setup in AWS.
I have done the setup in AWS without any hussle.
But if you could provide more information about how to start and run it there.
It will be very helpful. Any links comments are welcome.
Thanks,
Rajeev

Looks like it's working. Tmux lets you switch between the different views, and starts with htop. Type ^B  to switch views, listed at the bottom. ^B 1 will show you one of the worker outputs (w-0). More tmux commands at http://manpages.ubuntu.com/manpages/precise/en/man1/tmux.1.html

Ok understood that part, Still have these 2 question.

I am not able to see any video. Can you tell me When I run this file  What are the additional step I have to do to see the video?

2.> To connect to the vnc I have used  http://localhost:6006/.
Here in the place of local host, I am giving the IP address of AWS currently running instance Public IP.
And added port 6006 also in the security.
But still not able to connect to vnc.

It's tricky to make Docker containers listen on external ports. It's easier to use ssh to forward the ports. From your local machine, run
$ ssh -L 6006:localhost:6006 -L 12345:localhost:12345 <aws instance>

and leave that ssh connection open. Then tell your VNC client connect to localhost:6006. TurboVNC works best. And to see the Tensorboard, point your browser to localhost:12345.
I'm surprised if you got port 6006 using universe-starter-agent: ports 5900 .. 5920 are more likely. You can check by running docker ps on the AWS machine -- it should show port assignments.


Rename the genres filter on the image search

This makes the label consistent with how data is shown on pages.
Closes https://github.com/wellcomecollection/wellcomecollection.org/issues/8097

@alexwlchan This is 'Done' but I'm not seeing the change on https://wellcomecollection.org/images. Does it need deploying or something?

Yes, presumably we haven't done a deployment. I'll do that now.

Appearing now.


Custom plugin not discovered locally

Deployment Method

[ ] Installer
[X] Docker Development
[ ] Docker Production
[ ] Bare metal Development
[ ] Bare metal Production
[ ] Digital Ocean image
[ ] Other (please provide a link Steps to Reproduce

Describe the problem*
I am trying to develop a plugin locally but it's not being discovered when running development server in Docker.
This is the folder structure:

And this is the contents of testplugin.py:
from InvenTree.plugin.plugin import InvenTreePlugin
from plugin.mixins import NavigationMixin

class TestPlugin(NavigationMixin, InvenTreePlugin):

    NAME = "TestPlugin"
    TITLE = "Test Plugin"
    VERSION = "1.0"

    NAVIGATION = [
        {'name': 'TestPlugin', 'link': '', 'icon': 'fas fa-box'},
    ]

    NAVIGATION_TAB_NAME = "Test Plugin Nav"
    NAVIGATION_TAB_ICON = 'fas fa-plus'

and setup.py:
import setuptools

setuptools.setup(
    name="inventree-test-plugin",

    version='1.0',

    packages=setuptools.find_packages(),

    entry_points={
        "inventree_plugins": [
            "InvenTreeTestPlugin = testplugin.testplugin:TestPlugin"
        ]
    },

    include_package_data=True,
)

Steps to Reproduce
Install locally via files above. Plugin doesn't show in the navigation bar and it's also not in the settings menu to be enabled.
Relevant log output
No response

Hello, I guess this is related to #5827 . Try putting the file directly in the plugins folder or try installing it as an editable pip package.

Moving it to the plugins folder directly doesn't seem to have any effect.

@arepp23 can you show the new folder structure?

@SchrodingersGat I've tried this:

and all files inside /plugins:

and for both it just continually loops through "Reloading plugins" when I launch the app without ever finishing

and for both it just continually loops through "Reloading plugins" when I launch the app without ever finishing

Ok, that is interesting. Are you running the latest InvenTree codebase?
If there are any messages from the server logs which could indicate why it is infinitely looping, that would be great

Not that I can tell:
a/plugins.txt
2023-11-06 18:10:45 inventree-inventree-dev-worker-1  | Plugin Registry: Reloading plugins
2023-11-06 18:10:45 inventree-inventree-dev-worker-1  | Collecting plugins
2023-11-06 18:10:45 inventree-inventree-dev-worker-1  | Added plugin directory: '/home/inventree/data/plugins' as '/home/inventree/data/plugins'
2023-11-06 18:10:48 inventree-inventree-dev-worker-1  | usage: manage.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
2023-11-06 18:10:48 inventree-inventree-dev-worker-1  |    or: manage.py --help [cmd1 cmd2 ...]
2023-11-06 18:10:48 inventree-inventree-dev-worker-1  |    or: manage.py --help-commands
2023-11-06 18:10:48 inventree-inventree-dev-worker-1  |    or: manage.py cmd --help
2023-11-06 18:10:48 inventree-inventree-dev-worker-1  |
2023-11-06 18:10:48 inventree-inventree-dev-worker-1  | error: invalid command 'qcluster'
2023-11-06 18:10:49 inventree-inventree-dev-worker-1  | Loading config file : /home/inventree/data/config.yaml
2023-11-06 18:10:49 inventree-inventree-dev-worker-1  | Using Python virtual environment: /home/inventree/data/env
2023-11-06 18:10:50 inventree-inventree-dev-worker-1  | Python version 3.10.13 - /home/inventree/data/env/bin/python3
2023-11-06 18:10:50 inventree-inventree-dev-worker-1  | 2023-11-07 00:10:50,505 INFO DB_ENGINE: django.db.backends.postgresql
2023-11-06 18:10:50 inventree-inventree-dev-worker-1  | 2023-11-07 00:10:50,505 INFO DB_NAME: inventree
2023-11-06 18:10:50 inventree-inventree-dev-worker-1  | 2023-11-07 00:10:50,505 INFO DB_HOST: inventree-dev-db
2023-11-06 18:10:50 inventree-inventree-dev-worker-1  | 2023-11-07 00:10:50,518 INFO InvenTree running with DEBUG enabled
2023-11-06 18:10:50 inventree-inventree-dev-worker-1  | 2023-11-07 00:10:50,518 INFO MEDIA_ROOT: '/home/inventree/data/media'
2023-11-06 18:10:50 inventree-inventree-dev-worker-1  | 2023-11-07 00:10:50,518 INFO STATIC_ROOT: '/home/inventree/data/static'
2023-11-06 18:10:55 inventree-inventree-dev-worker-1  | Skipping plugin loading sequence
2023-11-06 18:10:57 inventree-inventree-dev-worker-1  | Waiting for database...
2023-11-06 18:10:59 inventree-inventree-dev-worker-1  | Database connection successful!
2023-11-06 18:11:00 inventree-inventree-dev-worker-1  | Python version 3.10.13 - /home/inventree/data/env/bin/python3
2023-11-06 18:11:00 inventree-inventree-dev-worker-1  | 2023-11-07 00:11:00,766 INFO DB_ENGINE: django.db.backends.postgresql
2023-11-06 18:11:00 inventree-inventree-dev-worker-1  | 2023-11-07 00:11:00,766 INFO DB_NAME: inventree
2023-11-06 18:11:00 inventree-inventree-dev-worker-1  | 2023-11-07 00:11:00,766 INFO DB_HOST: inventree-dev-db
2023-11-06 18:11:00 inventree-inventree-dev-worker-1  | 2023-11-07 00:11:00,774 INFO InvenTree running with DEBUG enabled
2023-11-06 18:11:00 inventree-inventree-dev-worker-1  | 2023-11-07 00:11:00,774 INFO MEDIA_ROOT: '/home/inventree/data/media'
2023-11-06 18:11:00 inventree-inventree-dev-worker-1  | 2023-11-07 00:11:00,775 INFO STATIC_ROOT: '/home/inventree/data/static'
2023-11-06 18:11:05 inventree-inventree-dev-worker-1  | Loading InvenTree plugins
2023-11-06 18:11:05 inventree-inventree-dev-worker-1  | Installing plugins from plugins file
2023-11-06 18:11:05 inventree-inventree-dev-worker-1  | Running pip command: /home/inventree/data/env/bin/python3 -m pip install -r /home/inventree/data/plugins.txt
2023-11-06 18:11:16 inventree-inventree-dev-worker-1  | Plugin Registry: Reloading plugins
2023-11-06 18:11:16 inventree-inventree-dev-worker-1  | Collecting plugins
2023-11-06 18:11:16 inventree-inventree-dev-worker-1  | Added plugin directory: '/home/inventree/data/plugins' as '/home/inventree/data/plugins'
2023-11-06 18:11:20 inventree-inventree-dev-worker-1  | usage: manage.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
2023-11-06 18:11:20 inventree-inventree-dev-worker-1  |    or: manage.py --help [cmd1 cmd2 ...]
2023-11-06 18:11:20 inventree-inventree-dev-worker-1  |    or: manage.py --help-commands
2023-11-06 18:11:20 inventree-inventree-dev-worker-1  |    or: manage.py cmd --help
2023-11-06 18:11:20 inventree-inventree-dev-worker-1  |
2023-11-06 18:11:20 inventree-inventree-dev-worker-1  | error: invalid command 'qcluster'
2023-11-06 18:11:21 inventree-inventree-dev-worker-1  | Loading config file : /home/inventree/data/config.yaml
2023-11-06 18:11:21 inventree-inventree-dev-worker-1  | Using Python virtual environment: /home/inventree/data/env
2023-11-06 18:11:21 inventree-inventree-dev-worker-1  | Python version 3.10.13 - /home/inventree/data/env/bin/python3
2023-11-06 18:11:22 inventree-inventree-dev-worker-1  | 2023-11-07 00:11:22,052 INFO DB_ENGINE: django.db.backends.postgresql
2023-11-06 18:11:22 inventree-inventree-dev-worker-1  | 2023-11-07 00:11:22,052 INFO DB_NAME: inventree
2023-11-06 18:11:22 inventree-inventree-dev-worker-1  | 2023-11-07 00:11:22,052 INFO DB_HOST: inventree-dev-db
2023-11-06 18:11:22 inventree-inventree-dev-worker-1  | 2023-11-07 00:11:22,064 INFO InvenTree running with DEBUG enabled
2023-11-06 18:11:22 inventree-inventree-dev-worker-1  | 2023-11-07 00:11:22,064 INFO MEDIA_ROOT: '/home/inventree/data/media'
2023-11-06 18:11:22 inventree-inventree-dev-worker-1  | 2023-11-07 00:11:22,064 INFO STATIC_ROOT: '/home/inventree/data/static'
2023-11-06 18:11:23 inventree-inventree-dev-server-1  | Database connection successful!
2023-11-06 18:11:23 inventree-inventree-dev-server-1  | Python version 3.10.13 - /home/inventree/data/env/bin/python3
2023-11-06 18:11:23 inventree-inventree-dev-server-1  | 2023-11-07 00:11:23,974 INFO DB_ENGINE: django.db.backends.postgresql
2023-11-06 18:11:23 inventree-inventree-dev-server-1  | 2023-11-07 00:11:23,974 INFO DB_NAME: inventree
2023-11-06 18:11:23 inventree-inventree-dev-server-1  | 2023-11-07 00:11:23,975 INFO DB_HOST: inventree-dev-db
2023-11-06 18:11:23 inventree-inventree-dev-server-1  | 2023-11-07 00:11:23,982 INFO InvenTree running with DEBUG enabled
2023-11-06 18:11:23 inventree-inventree-dev-server-1  | 2023-11-07 00:11:23,982 INFO MEDIA_ROOT: '/home/inventree/data/media'
2023-11-06 18:11:23 inventree-inventree-dev-server-1  | 2023-11-07 00:11:23,983 INFO STATIC_ROOT: '/home/inventree/data/static'
2023-11-06 18:11:27 inventree-inventree-dev-worker-1  | Skipping plugin loading sequence

error: invalid command 'qcluster'

That is a bit of a red flag. So the logs are from the worker instance which show the error - does the server container boot OK?

Seems like no:
23-11-06 18:32:18 inventree-inventree-dev-server-1  | Loading InvenTree plugins
2023-11-06 18:32:18 inventree-inventree-dev-server-1  | Installing plugins from plugins file
2023-11-06 18:32:18 inventree-inventree-dev-server-1  | Running pip command: /home/inventree/data/env/bin/python3 -m pip install -r /home/inventree/data/plugins.txt
2023-11-06 18:32:28 inventree-inventree-dev-server-1  | Plugin Registry: Reloading plugins
2023-11-06 18:32:28 inventree-inventree-dev-server-1  | Collecting plugins
2023-11-06 18:32:28 inventree-inventree-dev-server-1  | ADDING /PLUGS
2023-11-06 18:33:01 inventree-inventree-dev-worker-1  | error: invalid command 'qcluster'
2023-11-06 18:32:28 inventree-inventree-dev-server-1  | Added plugin directory: '/home/inventree/data/plugins' as '/home/inventree/data/plugins'
2023-11-06 18:33:02 inventree-inventree-dev-worker-1  | Loading config file : /home/inventree/data/config.yaml
2023-11-06 18:33:02 inventree-inventree-dev-worker-1  | Using Python virtual environment: /home/inventree/data/env
2023-11-06 18:32:31 inventree-inventree-dev-server-1  | usage: manage.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
2023-11-06 18:32:31 inventree-inventree-dev-server-1  |    or: manage.py --help [cmd1 cmd2 ...]
2023-11-06 18:32:31 inventree-inventree-dev-server-1  |    or: manage.py --help-commands
2023-11-06 18:32:31 inventree-inventree-dev-server-1  |    or: manage.py cmd --help
2023-11-06 18:32:31 inventree-inventree-dev-server-1  |
2023-11-06 18:32:31 inventree-inventree-dev-server-1  | error: invalid command 'runserver'
2023-11-06 18:32:33 inventree-inventree-dev-server-1  | Loading config file : /home/inventree/data/config.yaml
2023-11-06 18:32:33 inventree-inventree-dev-server-1  | Using Python virtual environment: /home/inventree/data/env
2023-11-06 18:32:33 inventree-inventree-dev-server-1  | Python version 3.10.13 - /home/inventree/data/env/bin/python3
2023-11-06 18:32:33 inventree-inventree-dev-server-1  | 2023-11-07 00:32:33,770 INFO DB_ENGINE: django.db.backends.postgresql
2023-11-06 18:32:33 inventree-inventree-dev-server-1  | 2023-11-07 00:32:33,770 INFO DB_NAME: inventree
2023-11-06 18:32:33 inventree-inventree-dev-server-1  | 2023-11-07 00:32:33,771 INFO DB_HOST: inventree-dev-db
2023-11-06 18:32:33 inventree-inventree-dev-server-1  | 2023-11-07 00:32:33,782 INFO InvenTree running with DEBUG enabled
2023-11-06 18:32:33 inventree-inventree-dev-server-1  | 2023-11-07 00:32:33,782 INFO MEDIA_ROOT: '/home/inventree/data/media'
2023-11-06 18:32:33 inventree-inventree-dev-server-1  | 2023-11-07 00:32:33,782 INFO STATIC_ROOT: '/home/inventree/data/static'
2023-11-06 18:32:40 inventree-inventree-dev-server-1  | Skipping plugin loading sequence
2023-11-06 18:32:42 inventree-inventree-dev-server-1  | Waiting for database...
2023-11-06 18:32:44 inventree-inventree-dev-server-1  | Database connection successful!
2023-11-06 18:32:45 inventree-inventree-dev-server-1  | Python version 3.10.13 - /home/inventree/data/env/bin/python3
2023-11-06 18:32:45 inventree-inventree-dev-server-1  | 2023-11-07 00:32:45,293 INFO DB_ENGINE: django.db.backends.postgresql
2023-11-06 18:32:45 inventree-inventree-dev-server-1  | 2023-11-07 00:32:45,293 INFO DB_NAME: inventree
2023-11-06 18:32:45 inventree-inventree-dev-server-1  | 2023-11-07 00:32:45,293 INFO DB_HOST: inventree-dev-db
2023-11-06 18:32:45 inventree-inventree-dev-server-1  | 2023-11-07 00:32:45,300 INFO InvenTree running with DEBUG enabled
2023-11-06 18:32:45 inventree-inventree-dev-server-1  | 2023-11-07 00:32:45,300 INFO MEDIA_ROOT: '/home/inventree/data/media'
2023-11-06 18:32:45 inventree-inventree-dev-server-1  | 2023-11-07 00:32:45,301 INFO STATIC_ROOT: '/home/inventree/data/static'
2023-11-06 18:32:50 inventree-inventree-dev-server-1  | Python version 3.10.13 - /home/inventree/data/env/bin/python3
2023-11-06 18:32:50 inventree-inventree-dev-server-1  | 2023-11-07 00:32:50,944 INFO DB_ENGINE: django.db.backends.postgresql
2023-11-06 18:32:50 inventree-inventree-dev-server-1  | 2023-11-07 00:32:50,944 INFO DB_NAME: inventree
2023-11-06 18:32:50 inventree-inventree-dev-server-1  | 2023-11-07 00:32:50,945 INFO DB_HOST: inventree-dev-db
2023-11-06 18:32:50 inventree-inventree-dev-server-1  | 2023-11-07 00:32:50,952 INFO InvenTree running with DEBUG enabled
2023-11-06 18:32:50 inventree-inventree-dev-server-1  | 2023-11-07 00:32:50,952 INFO MEDIA_ROOT: '/home/inventree/data/media'
2023-11-06 18:32:50 inventree-inventree-dev-server-1  | 2023-11-07 00:32:50,952 INFO STATIC_ROOT: '/home/inventree/data/static'
2023-11-06 18:32:55 inventree-inventree-dev-server-1  | Loading InvenTree plugins
2023-11-06 18:32:55 inventree-inventree-dev-server-1  | Installing plugins from plugins file
2023-11-06 18:32:55 inventree-inventree-dev-server-1  | Running pip command: /home/inventree/data/env/bin/python3 -m pip install -r /home/inventree/data/plugins.txt

Can you let me know the git commit hash you are running from?


Noir Contracts: Can TransparentNote of the non_native_token_contract conform to the NoteInterface?

Ideally, we should be able to design every custom note to adhere to the NoteInterface:
use crate::note::note_header::NoteHeader;

struct NoteInterface<Note, N> {
    deserialise: fn ([Field; N]) -> Note,

    serialise: fn (Note) -> [Field; N],

    compute_note_hash: fn (Note) -> Field,

    compute_nullifier: fn (Note) -> Field,

    dummy: fn () -> Note,

    get_header: fn (Note) -> NoteHeader,

    set_header: fn (&mut Note, NoteHeader) -> (),
}

The motivation for this, is that an ordinary (not advanced) user can write notes without having to mention the Aztec context or the abi. This is because the Set, Singleton and ImmutableSingleton types take care of pushing-to and pulling-from the context, abis, and trees, by wrapping custom notes.
Currently, the TransparentNote deviates from this pattern. I don't fully understand the example, but would like to understand if the note could be made to conform to the pattern, or if there's something fundamental that's been overlooked in designing the NoteInterface.
Tagging @Maddiaa0 who I think designed this contract and note :)

Closed as this is being done in #1194


Fixup graph paths for cached inputs

This PR corrects a small bug introduced by https://github.com/E3SM-Project/polaris/pull/225. When inputs are cached, we need to point to the mesh step rather than the init step for the graph files. Doesn't hurt to point to the mesh step when inputs are not cached either.

Testing
Icos cosine bell convergence test has been tested with cached inputs on chrys with intel, impi.


minor error in danish translation

just a minor error in the Danish translation in the first paragraph it says 13:1 chats instead of 1:1

Dokumentoplysninger
⚠ Undlad at redigere denne sektion. Det er påkrævet til docs.microsoft.com ➟ GitHub-problemlinkning.

ID: eb41d287-f954-dc84-782c-de8fa3c1ea0d
Version Independent ID: 0081aa8b-87dd-aef2-aaeb-61caa8f20351
Content: Teams arbejdsproces i eDiscovery (Premium) - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/teams-workflow-in-advanced-ediscovery.md
Service: o365-seccomp
GitHub Login: @v-tophillips
Microsoft Alias: v-tophillips

@TinaMcN Can you take a look?

@v-tophillips logged a bug for the translation vendors to fix.  The article is currently machine translated and it's being sent now for human translation which should fix the problem.  @DrLippert thank you for reporting the issue and please let us know if you notice any translation issues in other Danish articles.

@TinaMcN i conformed with english article , and i found
Teams 1:1 chats is mentioned, but i could not able to edit danish article.

@DrLippert The Danish article has been fixed now.  Thanks again for telling us about the problem.

https://docs.microsoft.com/da-dk/microsoft-365/compliance/teams-workflow-in-advanced-ediscovery?view=o365-worldwide#where-teams-content-is-stored
Please close this issue if it looks ok for you.

@TinaMcN . I too checked  now , issue is fixed


Texture atlas preprocessing & the art production pipeline.

In order to make Bevy a tier 1 engine for 2D games, a better texture atlas art production pipeline is needed.
Requirements:

It should be possible to drop texture atlas source art into a directory and have the asset preprocessor rebuild the atlas.
In this sense, the individual source art is uncooked and the atlas is a cooked (shippable) asset.
More texture atlas services should be exposed through this preprocessing (and the underlying API).
Preprocessing should be resilient to bad data, communicating the nature of the error without panics. Cooking content should be a viable runtime development activity by non-programmers on the team.

Additional Features:

The atlas preprocessor should be configurable.
Option: Trim whitespace. To pack efficiently, the asset preprocessor should be able to trim whitespace and record in metadata the amount trimmed so that the original UVs can be reconstructed.
Option: Rotate images. To pack efficiently, the asset preprocessor should be able to rotate images 90deg and record in the metadata the rotation bit so that the original UVs can be reconstructed.
Option: Paginated atlases. It should be possible to specify the max texture size of an atlas and, if the source art exceeds this arrangement, produce additional atlas pages. Meta data would track this and use the appropriate texture binding at render time.
Option: Resampling rules. It may be useful to be able to specify resampling rules for input images before they are written to the atlas.

Many of these are features of the Esoteric atlas packer, which is very good.

Attacking this work probably breaks down into these steps.

Research what needs to be done for "N-to-one" asset processing in assetv2. This means that a single output file is produced as a result of any file in a tracked directory changing (modify/add/delete). This may require a PR to file down any rough edges.

Get preprocessing and loading working with basic bevy texture atlases using existing features and minimal or no metadata. So we can modify / add / delete and get a functional bevy texture atlas on the other end.

Add the advanced configuration features once the simple model is in place and working. (probably a PR per feature)

Related PR/issue: https://github.com/bevyengine/bevy/pull/11873 / https://github.com/bevyengine/bevy/issues/11634

Found my way at this issue and wanted to just comment on a few low-hanging fruit I noticed.
First, TextureAtlasLayout includes a map from the atlas back to the original images, but this feels like a mistake. By itself, TextureAtlasLayout is a very simple structure that could be made de/serializable, but having asset IDs embedded directly inside it complicates things. IMHO, this should be instead delegated to another type, TextureAtlasSources, which is generated when an atlas is generated, but isn't needed if the atlas is loaded directly.
Second, while the TextureAtlasBuilder is nice, it feels like the majority of the settings for packing a texture atlas should be located in a struct which can also be de/serialized, so it can be used for the input to an asset processor.
Third, there could probably easily be a dedicated asset processor for texture atlases (there aren't any at the moment, but this could be the first!) based upon the above two types.
Finally, it's very weird that the type TextureAtlas doesn't refer to the entire atlas, but a texture on the atlas. It would make sense to have a TextureAtlas type storing the actual atlas asset (including the image), and an AtlasTexture to store the reference to the specific asset and an index.
Would be more than happy to implement a couple of these, after I look more into the code. Just figured I'd star the discussion before I do, since I think it's worth making sure I didn't misread anything.

@clarfonthey I have largely worked around Bevy’s texture atlases to get something usable for my game. My current workflow is custom but pretty good! I agree with your raised issues, and there are even more problems. It might even warrant its own working group.


Separate OpenSearch instance selection from the "Encryption" parameter

Is your feature request related to a problem? Please describe.
Separate OpenSearch instance selection from the "Encryption" parameter.
Describe the feature you'd like
A new parameter "OpenSearchInstanceType" or the like that allows selection of OpenSearch instance types independent of Encryption.
The "Encryption" parameter should still control whether the OpenSearch domain is encrypted.
Additional context
Modern OpenSearch instance types all support encryption at rest, and there's no reason I shouldn't be able to encrypt data a rest to comply with corporate policies while running a smaller-than-production sized domain.

Hi @dthvt
Thank you for reporting this. We are looking into this and will update after analysis

Hi @dthvt
Thank you for your contribution. We are planning to include this in upcoming release.
We'll keep you updated on progress

Hi @dthvt
This change has been incorporated in release v5.5.0
Thanks for your contribution


Merge feature/FORGE-439 into develop

Upgraded the plugin code to brXM v15 and Camel v3.19.0
Also recreated a cleaner working demo from a v15 archetype.

update maven skin to 3.2.1. David released a new version like a week ago with the fixed ribbon.


[HUDI-7970] Move methods from HoodieTableConfigUtils to HoodieTableConfig

Change Logs
In HUDI-7902, we will modify the config value hoodie.table.partition.fields to also store partition type. This PR aims to make sure that the getter and other functions accessing this field remain consistent in behaviour with the new value type.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level (write none, low medium or high below)
low
Documentation Update
NA
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

The reader side change has already been handled as part of https://github.com/apache/hudi/pull/11638. I am using this PR to address the comments here and some other minor changes


Colour issue

Name of Defective Feature
Goal Indicator Warning Color
Goal indicators are remaining blue even after feature is switched off
System Settings (Required)
ToolKit Version:2.0.2
Operating System (Mac/Windows/Etc):Mac
Browser (Chrome/Firefox/Safari):Chrome
Browser Version:63.0.3239.132
Other Extensions:
Export of Toolkit Settings (Bottom Left of Settings Page)

Settings Export

[paste settings here]

Steps to Reproduce the Behavior

Expected Behavior

Actual Behavior

@ajbarry2018 please paste your Toolkit settings in the 'Settings Export' area of the issue.

@ajbarry2018 I'm going to close this issue as we really need an export of your settings to properly triage. If you're still having the issue, please edit your ticket with the settings attached and reopen. Thanks!

I guess I'm having a similar issue. After I installed the toolkit I did briefly turn on goal indicators but found them confusing and turned them off. However, now apparently random entries in the categories column are colored light blue and some entries in the budget column are colored light green. Different categories and/or budgets are colored blue/green in different months. I've gone back to check and see if some feature is turned on that might be doing this and I can't see any. I've also refreshed the screen and restrarted Firefox and logged out and logged back into YNAB, but the behavior remains.

@jpekelny If you'll paste an export of your settings this Issue can be reopened. Without an export of your settings we cannot diagnose the problem.

@dbaldon Perhaps this is a separate bug, but when I press on Import/Export settings, all that happens is that the entire screen gets grayed out. If I press on this button again, it goes back to its original state. No Import/Export seems to actually happen. I'm using Firefox.

Well, now the Import/Export worked for some reason. Here it is.
[{"key":"AccountsDisplayDensity","value":"0"},{"key":"AccountsEmphasizedOutflows","value":true},{"key":"AccountsStripedRows","value":false},{"key":"AutoDistributeSplits","value":false},{"key":"AutomaticallyMarkAsCleared","value":false},{"key":"BetterScrollbars","value":"1"},{"key":"BudgetCategoryFeatures","value":true},{"key":"BudgetProgressBars","value":"both"},{"key":"BudgetQuickSwitch","value":false},{"key":"CalendarFirstDay","value":"1"},{"key":"CategoryActivityCopy","value":true},{"key":"CategoryActivityPopupWidth","value":"0"},{"key":"ChangeEnterBehavior","value":false},{"key":"CheckCreditBalances","value":false},{"key":"CheckNumbers","value":false},{"key":"ClearSelection","value":false},{"key":"CollapseSideMenu","value":true},{"key":"ColourBlindMode","value":false},{"key":"CompactIncomeVsExpense","value":false},{"key":"CreditCardEmoji","value":true},{"key":"CurrentMonthIndicator","value":true},{"key":"CustomFlagNames","value":true},{"key":"DaysOfBuffering","value":true},{"key":"DaysOfBufferingHistoryLookup","value":"0"},{"key":"DisableToolkit","value":false},{"key":"DisplayTargetGoalAmount","value":"0"},{"key":"DisplayTotalMonthlyGoals","value":true},{"key":"DisplayUpcomingAmount","value":true},{"key":"EasyTransactionApproval","value":true},{"key":"EditAccountButton","value":"0"},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"EnterToMove","value":true},{"key":"FilterCategories","value":true},{"key":"GoalIndicator","value":true},{"key":"GoalWarningColor","value":false},{"key":"GoogleFontsSelector","value":"0"},{"key":"HideAccountBalancesType","value":"0"},{"key":"HideAgeOfMoney","value":false},{"key":"HideHelp","value":false},{"key":"HideReferralBanner","value":false},{"key":"HideTotalAvailable","value":false},{"key":"HighlightNegatives","value":false},{"key":"ImportNotification","value":"0"},{"key":"IncomeFromLastMonth","value":"0"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":false},{"key":"LinkToInflows","value":true},{"key":"MonthlyNotesPopupWidth","value":"0"},{"key":"NavDisplayDensity","value":"0"},{"key":"Pacing","value":"0"},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"0"},{"key":"QuickBudgetWarning","value":true},{"key":"ReconciledTextColor","value":"0"},{"key":"RemovePositiveHighlight","value":false},{"key":"RemoveZeroCategories","value":true},{"key":"ResizeInspector","value":false},{"key":"ResizeSidebar","value":false},{"key":"RightClickToEdit","value":true},{"key":"RowHeight","value":"0"},{"key":"RowsHeight","value":"0"},{"key":"RunningBalance","value":"1"},{"key":"SeamlessBudgetHeader","value":false},{"key":"SetMultipleFlags","value":true},{"key":"ShowCategoryBalance","value":false},{"key":"SpareChange","value":false},{"key":"SplitTransactionAutoAdjust","value":true},{"key":"SquareNegativeMode","value":true},{"key":"StealingFromFuture","value":true},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":false},{"key":"ToBeBudgetedWarning","value":false},{"key":"ToggleMasterCategories","value":false},{"key":"ToggleSplits","value":false},{"key":"ToggleTransactionFilters","value":"0"},{"key":"ToolkitReports","value":true},{"key":"TransactionGridFeatures","value":true},{"key":"ViewZeroAsEmpty","value":true},{"key":"l10n","value":"0"},{"key":"options.dark-mode","value":true}]


Form View - Add FormViewTests.testCase_1_1

Adds the first Form View UI test case.

Taking this back to draft until #377 is merged. No need to review again just yet. The example view changes may be able to drop off entirely.

The test view has been updated to work with the new Core API. Ready for review once again.


Implicit features due to target-specific optional dependencies are not added in current version

@obi1kenobi Upgrading to v0.18 results in a failing semver check despite this crate not having received any significant changes. Could you look into this?

Originally posted by @thomaseizinger in https://github.com/libp2p/rust-libp2p/issues/3469#issuecomment-1432218666
Affected crate: libp2p_uds version 0.17, repro commit 5b4eab7bafe6cba8fea6c806027ea680662b7cc6
Its Cargo.toml contains the following block:
[target.'cfg(all(unix, not(target_os = "emscripten")))'.dependencies]
async-std = { version = "1.6.2", optional = true }
libp2p-core = { version = "0.38.0", path = "../../core" }
log = "0.4.1"
futures = "0.3.1"
tokio = { version = "1.15", default-features = false, features = ["net"], optional = true }

This implicitly defines features named async-std and tokio. These features are enabled in the baseline, but for some reason are not enabled in the "current":
[dependencies.libp2p-uds]
path = "/.../rust-libp2p/transports/uds"
features = []
default-features = false

@tonowak would you mind taking a look at this, since you're much more familiar with this code?
I'm surprised that our feature-detection code seems to detect different features when loading a crate's information via the registry (as in the baseline) versus from a local Cargo.toml manifest (as in the current version).

I'll release this in a patch version in the morning (my time), because releasing right before going to bed sounds like a recipe for staying up for half the night, just like deploying prod at 5pm on a Friday 😅

Released in https://github.com/obi1kenobi/cargo-semver-checks/releases/tag/v0.18.2 — sorry for the inconvenience and thanks for bearing with us while we fixed this!


WIP: support holes

Thanks for doing the heavylifting!. Here's some very crude support for holes. Hopefully it helps as a starting point to something nicer :)

Thanks! (Sorry for the delay in merging.)


👷 Add Test Coverage to Respository PRs

This PR connects uploads results of our tests to codecov.

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Build Docker Images on Github CI

Description

Build Docker Images on Github CI and push them to Github Packages.
Packages will live at https://github.com/orgs/QuantConnect/packages
Related Issue

Motivation and Context

Makes the builds faster and provides alternative for DockerHub (DockerHub has rate limiting for image pulls)
Requires Documentation Change

None
How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which improves implementation)
[x] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

Thanks for the PR @itsbalamurali! Closing for now so we implement pushing to GH together with current Lean image pushing to docker hub.


rpc tests failing randomly on Travis

The following rpc tests appear to fail randomly on Travis:

cfund-paymentrequest-state-accept-expired-proposal.py (fixed via #418)
cfund-proposal-state-accept.py (fixed via #418)
coldstaking_spending.py (related to #377)
merkle_blocks.py (fixed via #423)
wallet.py
wallet-hd.py

afaik problems with the first 2 tests is related to time.time() being inconsistent with block times, which result in a long running time and can cause assert fails immediately after the while loop. fixed
Problems with the second 2 tests are related to transaction fees.

new tests related issue: https://github.com/navcoin/navcoin-core/issues/519


clear payment fields after inline edit

Critical Changes
Changes

When a row with a matched payment is edited so the payment no longer matches, the matched record field clears.

Issues Closed
New Metadata
Deleted Metadata

**lurch: attach W-029111

Tracking W-029111


Fixes #152: Avoid CORS issue when reading appstore.json from Github repository

Ok to review

Reviewed and put into upstream/152 pending potential more revisions: https://github.com/redhat-kontinuity/catapult/commit/40818f3452a91f8f8a6b24e2f84f673b2d171b6a

Issues identified and discussed on linked commit; awaiting new commits to address them before PR merge.

7c90f05aac62b4c7bbc888e1bb123df9e2d2f531


[OTHER] add category name to the url

What would you like to share or ask?
Hi, I want to add the category name in the URL when the dropdown button gets clicked. For example, when user would visit https://linkshub.dev/languages then it should redirect to the open source section and open the open-source dropdown by default
Currently:

Should be like this:

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)

There can be two ways.

The user doesn't want this to open, so he directly goes to the respective URL (which he/she already knows). In this case, it would be bad UX.

It opens up, and the user can navigate to other sections by seeing the subcategories within that section. This is more general and I would believe would increase UX.

I prefers second option.

There can be two ways.

The user doesn't want this to open, so he directly goes to the respective URL (which he/she already knows). In this case, it would be bad UX.
It opens up, and the user can navigate to other sections by seeing the subcategories within that section. This is more general and I believe this would increase UX.

I prefer second option.

the first one is how it looks like currently, and the second one is about what i wanna do in there

There can be two ways.

The user doesn't want this to open, so he directly goes to the respective URL (which he/she already knows). In this case, it would be bad UX.

It opens up, and the user can navigate to other sections by seeing the subcategories within that section. This is more general and I believe this would increase UX.

I prefer second option.

I prefer the second option too @Anmol-Baranwal and @rupali-codes.

@Anmol-Baranwal could you please elaborate more on the second option?

@Anmol-Baranwal could you please elaborate more on the second option?

Imagine you're navigating a website with a sidebar. This sidebar serves as a navigational hub, providing you with quick access to various sections of the website. Now, let's focus on a specific scenario: you want to explore the "Icons" section of the website.

Scenario A: Sidebar Stays Closed
In this case, if the sidebar remains closed even when you access the "/icons" route:

You would need to manually open the sidebar, which adds an extra step in your navigation process. This can be frustrating, especially if you're not familiar with the site's layout.

Scenario B: Sidebar Automatically Opens to Subcategory
Now, let's consider the enhanced scenario where the sidebar automatically opens to the "Icons" subcategory when you visit the "/icons" route:

By automatically expanding the sidebar to the relevant subcategory, you're saving users time and effort. They can immediately see the available options related to icons without the need to manually interact with the sidebar.

Opening to the "Icons" subcategory visually guides users, showing them where they are and how to proceed. It's like walking into a store and finding the section you're interested in immediately visible.

Users don't need to remember to open the sidebar or figure out which section they're in. The website proactively supports their journey, reducing cognitive load and improving the overall user experience.

Incorporating this behavior aligns with the UX principle of reducing friction and making navigation as seamless as possible.

@Anmol-Baranwal i see, thats exactly what i was saying :)


Make ffi public?

I'd like to use some features of rust-rocksdb that currently don't exist in this wrapper. The only way for me to do this is to implement them in a fork. This is a problem because:

One of the API's (a no-copy iterator) has a safety issue that isn't trivial to fix at the moment, so it can't be merged upstream
I can't use a fork as I'd like to publish my crate to cargo. I'd like to avoid publishing my own version of rust-rocksdb as a crate too

A solution to this may be to expose some more parts of the wrapper to the public:

Make the ffi module public (I, obviously, could just use rocksdb-sys directly, but I think it's nicer to access it through rocksdb::ffi)
Make db::ReadOptions public
Add .inner() getter methods to all the types that have an .inner attribute. Eg, DB, Snapshot, DBIterator, etc.

This would allow developers to use APIs that are not yet supported by this wrapper in their own code, and also directly integrate with the existing types.
What do you think?

I'm in favor of exposing rocksdb::ffi as public. Historically I've hit a number of annoying issues with wrapper libraries that excessively hide functionality. I'm also in favor of adding an unsafe, well-documented no-copy iterator method for those who would benefit from the use case.

Surely the solution here is simply to import the sys crate directly, if you want the ffi functionality? That sounds much cleaner, to me.

I'd like to make sure I'm always using a compatible -sys crate with the rocksdb crate. Problem is that if I use the -sys crate directly i'd have to specify a direct dependency to it in the Cargo.toml for my project so have to make sure it's a compatible version when updating rocksdb (which is a minor annoyance).

Hmm, fair point, I suppose... is this convention though? I don't see any other crates doing this.

There are a couple cases where this is done, nix comes to mind.  We use it at work for re-exporting types.  E.g. the core of our utility libraries are codegen'd from protobufs or whatever, and the easiest way to stay in sync is have the utility libraries re-export the codegen'd functionality.

I feel the real issue here is that this crate doesn't expose sufficient functionality. I think in the past few months we have been making good strides towards improving the situation (eg. #209, #212, #238, #240, #246, #248, #253, #263). I actually like the pressure of GitHub issues stating that functionality is not accessible as a motivating force to improve this crate.  Exposing the FFI might mean we will get fewer of those issues (or PRs) since a workaround exists.
I propose we close this issue and continue working toward exposing more functionality.
/cc @aleksuss @vitvakatu

There haven't been any objections to my proposal. I'm going to close and we can revisit if someone feels otherwise.


How can I get the RioBus using ionic 1?

I am a newbie...

This is an Ionic 2 project, you can't run it as Ionic 1. However, if your interest is about using the API to have access to the data, the documentation is in https://github.com/RioBus/proxy/wiki/REST-API.
But, unfortunately, it's in portuguese and does not have any official translation to english.

Thanks for your reply!


Create an android application using github API

Description

Your app must use Github API
You can use any language for android - Java/ kotlin/ flutter
You can create beginner friendly application with your own idea, and designs
Please use appropriate comments to self describe your code
Add necessary readme.md, images
Already existing Github clone apps will consider as spam.

You can comment below to get assigned to this issue.

Hey @henrikhorbovyi please update your progress here, so we'll know, you are still working on same issue

I'll open a PR soon


Add toltec hooks

Fixed c-quoted string handling with escaped unicode characters
Added reload_oxide_apps hook
Added patch_rm2fb hook
Added install_lib hook
Load included hooks automatically
Change standalone version to use pyinstaller so that user hooks will work
Build standalone with python 3.12
Test python 3.11 and 3.12
Add build for pip packages
Add logic to upload pip packages to pypi
Update version number to 0.3.0

One concern, I just realized, is that custom hooks will not have the full stdlib available due to how pyinstaller optimizes things. I've solved this before by generating a stdlib zip file to include that is automatically added to the path. I think for now we'll just leave it out until there is a need.

I'll leave this open for comment until the new year, and then I'll merge.


Add thingId validator

A thingId is a type prefix: tN and a base36 number separated by an underscore.
t3_1 is a valid thingId that previously didn't meet the length requirement.
:eyeglasses: @ajacksified

tests pls https://github.com/reddit/snoode/tree/master/test

after lunch!

:haircut: tests added

:nail_care:

:haircut: didn't add the consts as class members because i didnt see a use case, but they're at least defined as private consts now.

:haircut: removed specific type prefixes since they can be different per install.

:fish:

da68efe49f2f4c5ee45c547913ac375f3c9ff668


Road network, admin names on the local units map

We display now the local units on the map as points. Unfortunately, the point cloud is not really useful without visual context:

I suggest to create a new mapbox style that displays road network and municipality/admin names on the base map. These should appear only above a certain zoom level (tbd). If possible, greyscale.

This is a good idea @tovari! @davidmuchatiza are you able to create a new style?

This is a good idea @tovari! @davidmuchatiza are you able to create a new style?

Let me give it a try on Mapbox Studio.


Add the root selector button to the import destination.

It is too annoying to cut and paste IDs.

code looks reasonable to me
LGTM :+1:


Add 4 random number generation blocks

Add 4 random number generation blocks.
One for each of these godot's functions:

randi
randi_range(from,to)
randf
randf_range(from,to)

The Allow edits by maintainers checkbox is checked so I suppose you should be able to merge.

@jfcharron merged! I tested placing a sprite in a random vertical position and it worked like a charm:

I have converted the blocks to the new definition format, which uses resources. In case you want to contribute new blocks, this is now the way to do it. It is nicer because the definitions can be edited in the editor directly:

Thanks!


Setup Fail after npm install

Hi, I got the following error running bin/server --port 1234 after npm install
server.listen(argv.port, () => {
                          ^
SyntaxError: Unexpected token )
    at Module._compile (module.js:439:25)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at `node.js:902:3`

Does it related to babel runtime that could not resolve ES6? Could you please give some instructions to solve this? thanks a lot.

Just a newer version of node. v6 should work


Replace tree-walk interpreter with bytecode interpreter

fn big() do
  fn sub1() do
    x =: 7
    sub2()
  end
  fn sub2() do
    y =: x
  end
  x =: 3
  sub1()
end


Switch locale from ja_JP to ja

Our CI for the ansible build for this service started failing in March 2023 because upstream OJS changed their locale names. Japanese is now "ja" instead of "ja_JP".
See this issue for details: https://github.com/pkp/pkp-lib/issues/8598
When we upgrade we'll need to:

[ ] Change the locale specified in our local Japanese translation
[ ] Update the ansible role to copy that file to the correct location
[ ] Update the ansible role to point to the latest version of the translations (we are going to pin it to an older version in order to fix the CI build)

This is the stanza we'll need to upgrade in ansible:

- name: ojs | clone translation repository
  ansible.builtin.git:
    repo: 'https://github.com/pkp/pkp-lib.git'
    dest: /opt/pkp-lib
    version: '3_3_0-14'


Go 1.22

First of all, thank you for your great work on this project! ❤ Having a PPA for Go is fantastic. Are you planning to release packages for Go 1.22 too?

Yes, as soon as I have the time. Last weeks were busy - sorry for the delay, but it will happen soon.

Packages for 1.22 are now in the ppa. Will be bumped to default after a little testing. Closing.

That’s great, thanks a lot!


How to force target version for packages installed with NPM?

On NodeOS we have found that node-gyp uses the headers same version of the Node.js executable that's running it, that makes not possible to use a different version of the one installed by the user. The docs and the code shows that's possible to define the target version to use when using node-gyp as a command line executable or as a library, but it doesn't say nothing about how to set the target Node.js version when installing a package by executing npm install, so I ask, there's any way to set the target version in that use case, for example by using an environment variable? Maybe a config flag on npm itself?

pull request would be great if better docs are desired


Toggle button selection issue

Need to look into why toggle groups are no longer showing the selected state or changing the mouse. Noticed it in the tilemap tool

This is fixed.


Vendorize scotty.

Please don't merge this PR yet. Travis isn't catching failing tests!

Ok everything is good now.

How does this pin us to specific Git commits for problem packages?

The goal of this PR is to enable anyone to build scotty.
They would do this:
git pull github.com/Symantec/scotty
cd $GOPATH/src/github.com/Symantec/scotty
make getdeps
go get -t ./...

I can put these directions in the README.md file in another pull request.
If we come across a problem dependency, I will need to figure something out.


Edge Agent deploy automation

I'm in the process of containerising my RPi based theatre actuators and sensors, and as part of that, i'm pre-baking the OS image using https://github.com/RPi-Distro/pi-gen/
I'm interested in having that universal image have the EDGE_KEY built in, and I would love any one of my co volunteers to be able to use that same image on any random RPi - and when they have issues, for me to do something in the portainer web UI to accept their new node.
IDK how to make this DOS-safe-ish

The Edge key is different for each endpoint. If you have multiple endpoints, you'll need multiple Edge keys to differentiate each environment.
At the moment, you or you co volunteers would need to register their endpoint in Portainer first before being able to deploy the agent on their remote environment.
I reckon that at the moment you'd need to provide a script to automate the creation of the endpoint + deployment of the agent. Something that would issue a HTTP API query to the Portainer instance to generate the endpoint and then deploy the agent with the Edge info available in the response.

oooo, can you expand a little wrt "edge key is different for each endpoint" - what implications does that have for nodes (like most of mine) that are moved to different locations, and so change IP's, routes and timezones?
wrt auto-join security - yeah, I'm basically assuming that an agent registers, and is put into a "pending admin approval state" - which would normally be done by the installer via api / webui (and only if the auto-join feature is enabled)
in my case, its not life threatening, its theatre, so DDOS isn't a huge concern

The Edge key contains the information that the agent can use to connect to a Portainer instance and is associated to a specific endpoint identifier.
You can find more information about the Edge agent in the two following posts:

https://www.portainer.io/2019/07/portainer-edge-agent/
https://www.portainer.io/2019/07/how-does-the-edge-agent-work/


[DOCS] Possible typo Apache Spark vs. Apache Storm

This PR is to act as a fix for https://github.com/elastic/elasticsearch/issues/14439.

Thanks. Merged in master and 2.x


[Contact] feature - accept the files on dock icon

solved https://github.com/namhokim/cocoa_app/pull/34

fixed https://github.com/namhokim/cocoa_app/pull/35


Inference demo.py

0%|          | 0/76 [00:00<?, ?it/s]
Traceback (most recent call last):
File "/data3/shenbaoyue/code/FastInst-try-maskattention/demo/demo.py", line 123, in
img = read_image(path, format="BGR")
File "/data3/shenbaoyue/code/FastInst-try-maskattention/detectron2/detectron2/data/detection_utils.py", line 180, in read_image
with PathManager.open(file_name, "rb") as f:
File "/data3/shenbaoyue/anaconda3/envs/fastry/lib/python3.8/site-packages/iopath/common/file_io.py", line 1012, in open
bret = handler._open(path, mode, buffering=buffering, **kwargs)  # type: ignore
File "/data3/shenbaoyue/anaconda3/envs/fastry/lib/python3.8/site-packages/iopath/common/file_io.py", line 604, in _open
return open(  # type: ignore
IsADirectoryError: [Errno 21] Is a directory: '/'
进程已结束,退出代码1
How can I resolve this error when I configure the parameters to run demo demo. py? The training process is normal. I have tried to solve it online but it has not been successful. I would greatly appreciate it if I could receive assistance

I have resolved the issue and the input needs to be a list.


Use conformance test artifacts

Instead of looking in the jspecify sibling project directory for conformance test inputs and dependencies, use the distributed artifacts produced by it.
Depends on https://github.com/jspecify/jspecify/pull/420.
Part of #107.

This probably needs to wait until #114 is merged.


Add return 0 to silence error

without the return 0 I am getting a
Script run function returned unexpected value
error when tryihg to run the script

The changes look good.
Thanks for contributing!


set swap assets from url query params

Added code that checks URL query params for the source and destination chainID and asset symbols within the SwapWidget component. One minor optimization here would be to pass the query string args into the page component from static props, but I left it as-is (using next/router).
It would also make more sense to put this logic outside of the SwapWidget itself, but I left it inside the component for now because the onAssetChange callbacks are coming from the useSwapWidget hook, which is itself currently encapsulated within the component.
Examples
http://localhost:3000?from=juno-1_glto&to=injective-1_inj
http://localhost:3000?from=osmosis-1_juno&to=juno-1_osmo

Any thoughts?

this feature is added in #271


Wrong numbers for bullet points

In this section, the numbering of bullet points is broken:

fixed!


Add stack transformations

Description

Fixes #478
Checklist

[ ] I have added tests that prove my fix is effective or that my feature works

[x] I have updated the CHANGELOG-PENDING file with my change

[ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version

Thank you.

only skimmed the tests lmk if you want me to read into those. Looks thorough though.
No need, they were mostly copied/translated from existing tests.

Should I remove DestroyOnCleanup?

I've remove copy and DestroyOnCleanup.


ImageFolder Dataset: make_dataset with the same (sorted) order.

When creating the dataset using ImageFolder, different machines can have different orders of images.
This may not be an issue for the training set, but when I want to compare the validation results among different machines (especially when I want to ensemble the softmax outputs of validation set), different orders of images can be annoying.
A simple modification can solve the problem: currently the make_dataset function uses for target in os.listdir(dir):, we can simply change it to for target in sorted(os.listdir(dir)):.
Since the loading procedure can be shuffled, I have not found creating the dataset with a sorted order has any drawbacks. Actually, it will be much easier for the users when they want to ensemble the outputs of the full dataset among different machines (where os.listdir(dir) might produce different orders of results`).

Also, it is difficult to reproduce the results on different machines. Even setting random seed will not produce the same ordered shuffle in training because the original order of data are different.

merged and fixed. thanks!


add get button

Adds a field to enter the board-id under the board
Adds a get button under the board
When user clicks get button, the board name above the board will be filled and the board notes will populate the board.
At the moment I don't know any boardid that has board_notes, and there is no 'note' component so it's just a text dump

As discussed, this will be done in a new way. So, closing this PR


Update README with correct Helm repo link

Waiting for GH Secret to be added to repo before merging, so publish action can succeed.


Proxmox 6.1 lxc container unable to define "complete" resource

Every time I rollout a lxc container it keeps detecting changes.
Am I missing something here or is this intended behavior?
Also, because I can't set the rootfs before creating the container this prevents me from changing the disk size on first boot.
  ~ resource "proxmox_lxc" "lxc-test" {
        arch                 = "amd64"
        bwlimit              = 0
        cmode                = "tty"
        console              = true
        cores                = 1
        cpulimit             = 0
        cpuunits             = 1024
        force                = false
        hostname             = "hostname"
        id                   = "hostname/lxc/103"
        ignore_unpack_errors = false
        memory               = 1536
        onboot               = true
      + ostemplate           = "local:vztmpl/centos-7-default_20171212_amd64.tar.xz"
        ostype               = "centos"
      + password             = "rootroot"
      + pool                 = "terraform"
        protection           = false
        restore              = false
      - rootfs               = "local-lvm:vm-103-disk-0,size=4G" -> null
      ~ start                = false -> true
      ~ storage              = "local" -> "local-lvm"
        swap                 = 128
        target_node          = "node"
        template             = false
        tty                  = 2
        unique               = false
        unprivileged         = true
        unused               = []

        network {
            bridge   = "vmbr0"
            firewall = false
            gw       = "<IP_ADDRESS>"
            hwaddr   = false
            ip       = "<IP_ADDRESS>/24"
            ip6      = "dhcp"
            name     = "eth0"
            rate     = 0
            tag      = 30
            type     = "veth"
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.```

I'm seeing the same behavior on PVE 5.4. Some params like ssh_public_keys also cause an "Error: 400 Parameter verification failed" when I reapply the original spec, which is probably a separate issue. I'll troubleshoot a bit more and will share any findings.
Regarding initial rootfs sizing, I've found that this works:
rootfs = "local-lvm:20"

(size in GB)

Yes it seems a couple of things should possibly be ignored on updates since they only apply during initial creation?
I've added a few manually to the lifecycle ignore_changes, but it doesn't resolve at least rootfs wanting to re-apply everytime because it changes to a direct location after creation.
  lifecycle {
      ignore_changes = [
          "ostemplate",
          "ssh_public_keys",
          "password"
      ]
  }


Return ISpecimenBuilderNode in ISpecimenBuilderTransformation

The current implementation of the ISpecimenBuilderTransformation used in fixture.Behaviors collection is following:
public interface ISpecimenBuilderTransformation
{
    ISpecimenBuilder Transform(ISpecimenBuilder builder);
}

While this interface looks cool, internally we implicitly expect that transformation returns an instance of ISpecimenBuilderNode rather than ISpecimenBuilder:
https://github.com/AutoFixture/AutoFixture/blob/6e1765747245d45c6659006f14e680568aec42e3/Src/AutoFixture/SingletonSpecimenBuilderNodeStackAdapterCollection.cs#L195-L197
and a test:
https://github.com/AutoFixture/AutoFixture/blob/6e1765747245d45c6659006f14e680568aec42e3/Src/AutoFixtureUnitTest/SingletonSpecimenBuilderNodeStackAdapterCollectionTest.cs#L318-L325
That point confused me each time I created my own behaviors because I got a feedback at run time only and needed to rework my code.
In this PR I'm changing the interface to transform ISpecimenBuilder to ISpecimenBuilderNode, so we have guarantee type safety at the compile time:
public interface ISpecimenBuilderTransformation
{
    ISpecimenBuilder Transform(ISpecimenBuilder builder);
}

This is a breaking change which will affect the existing user behaviors. Users will need to change the signature of the implementation in their code. However, that shouldn't be an issue as they returned ISpecimenBuilderNode instances in any case.
While it's a breaking change in API, I believe that it worth it as user experience will be much better.
We are totally fine to accept this breaking change as we are still working on the major version, so SemVer is not violated - we are still on the v3 -> v4 boundary.
@moodmosaic @adamchester What do you think about the suggested change? Let's discuss if you have objections.

I'm impressed, BTW, for all those things―big and small―you were able to spot in this fairly sized codebase!
:1st_place_medal:

Otherwise, if we target this to v4, we could take this PR as-is...

This PR targets v4. Currently the master branch is for the already released v4 RC1 and the upcoming v4 RTM - we no longer support releases of v3. The reason why I followed this way was the namespace change, so it would be a hell to merge from master to v4. Therefore, I kept only single branch - master, which corresponds to the v4 now. So now it's technically impossible to fire a PR for the v3 😄

I'm impressed, BTW, for all those things―big and small

Thanks 😊 It's awesome to see how great the AutoFixture becomes without all those annoying issues.

Yeah, as long as v4 isn't officially out, then, perhaps this one can be taken as-is, without Obsolete attributes.


Adjust drip list funding splits (by Thu 2024-07-25)

https://github.com/elimu-ai/web3-wiki/blob/main/DRIP_LIST_FUNDING_SPLITS.md

[x] Content Creation 🎶🎙
✔ Hindi: off-chain | on-chain
✔ Tagalog: off-chain | on-chain
[x] Engineering & AI/ML 👩🏽💻📱
✔ webapp: off-chain | on-chain
[x] Distribution & Data Collection 🛵💨
✔ website: off-chain | on-chain

@nya-elimu can you assign this issue to me?

@charanbhatia This issue has been closed already.


VM scale set extension fails

[Enter feedback here]
I am trying to create a simple VM scale set from my local machine. The extension script fails. However in Azure cloud shell it works.
Extension script
az vmss extension set --publisher Microsoft.Azure.Extensions --version 2.0 --name customScript --resource-group venkirg123 --vmss-name venkiscaleset --settings '{"fileUris":["https://raw.githubusercontent.com/Azure-Samples/compute-automation-configurations/master/automate_nginx.sh"],"commandToExecute":"./automate_nginx.sh"}'
Error message
ValidationError: Deployment failed. Correlation ID: 4956e922-4e5d-4c45-a271-a0c1f3a464ae. VM has reported a failure when processing extension 'customScript'. Error message: "Enable failed: failed to get configuration: error reading extension configuration: error parsing settings file: error parsing json: json: cannot unmarshal string into Go struct field handlerSettings.publicSettings of type map[string]interface {}"
More information on troubleshooting is available at https://aka.ms/vmextensionlinuxtroubleshoot
Azure Cli version used
azure-cli                         2.12.1
core                              2.12.1
telemetry                          1.0.6

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

ID: d8d7fa25-452b-cee5-cc7c-6498c68785b3
Version Independent ID: 522c1636-a429-5ab1-03e7-401ef308d98d
Content: Quickstart - Create a virtual machine scale set with Azure CLI - Azure Virtual Machine Scale Sets
Content Source: articles/virtual-machine-scale-sets/quick-create-cli.md
Service: virtual-machine-scale-sets
Sub-service: cli
GitHub Login: @ju-shim
Microsoft Alias: jushiman

@venkateshkuppusamy
As mentioned in the document, the CLI commands are expected to run on Cloud Shell (BASH) prompt.
From the error, the reason is with the shell not able to interven (in terms of interpolations, etc) with the string you want to pass to the command.
However, if you still want to run from your local machine (cmd prompt) with Azure CLI command you may have to change the command as below, I have tested it in my local and it is working as expected.
az vmss extension set --publisher Microsoft.Azure.Extensions --version 2.0 --name CustomScript --resource-group vikas-test --vmss-name vikas-ss --settings "{\"fileUris\":[\"https://raw.githubusercontent.com/Azure-Samples/compute-automation-configurations/master/automate_nginx.sh\"],\"commandToExecute\":\"./automate_nginx.sh\"}"
Hope this helps.

Thanks for bringing this to our attention. We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


Render 1D Tracks with SVG

It would be awesome if it's possible to render 1D Tracks with SVG. This would enable crisp printing for publications.

All tracks can be exported as SVG now :)


 It would be even better if the level building was the part of the whole building process (there was an issue about that somewhere)

there was an issue about that somewhere

#763

@rexim you should close it as svg2rect is irrelevant at this point

@The-Renaissance yap! Thank you very much!


Test in now-released Node 10 instead of Node 9

Also update engines.
Closes #1660

Warnings

:warning:

This PR modified package.json, but not package-lock.json - Perhaps you need to run npm install?

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS

Would it be worth just using node:latest instead?

That's not a bad idea! I'll switch it over for now. We'll always have to push new Docker images when there's a new Node version, but it's one less thing to edit each time.


rewrite to use nbio/httpcontext instead of map and locks

Hi Mat
I watched your London gopher talk and became aware of the response package. Great talk BTW.
I like the respond package, but what I didn't like, was the usage of locks in the options handler.
I rewrote the package to use https://github.com/nbio/httpcontext for contexts. It stores the request context directly in the http.Request by mutating the request.Body, avoiding the use of a global mutex and per-request teardown.
And it passes your tests :-)

Very cool - I wonder if it’s worth benchmarking the two solutions so we can understand the difference under load?

On 30 Sep 2015, at 13:10, Rene Zbinden<EMAIL_ADDRESS>wrote:
Hi Mat
I watched your London gopher talk and became aware of the response package. Great talk BTW.
I like the respond package, but what I didn't like, was the usage of locks in the options handler.
I rewrote the package to use https://github.com/nbio/httpcontext https://github.com/nbio/httpcontext for contexts. It stores the request context directly in the http.Request by mutating the request.Body, avoiding the use of a global mutex and per-request teardown.
And it passes your tests :-)
You can view, comment on, or merge this pull request online at:
https://github.com/matryer/respond/pull/3 https://github.com/matryer/respond/pull/3
Commit Summary
rewrite to use nbio/httpcontext instead of map and locks
File Changes
M respond.go https://github.com/matryer/respond/pull/3/files#diff-0 (53)
Patch Links:
https://github.com/matryer/respond/pull/3.patch https://github.com/matryer/respond/pull/3.patch
https://github.com/matryer/respond/pull/3.diff https://github.com/matryer/respond/pull/3.diff
—
Reply to this email directly or view it on GitHub https://github.com/matryer/respond/pull/3.

I did a small Test with https://github.com/rakyll/boom and it didn't show any meaningful differences.


fix: custom button component to fix inconsistency

Related Issue
Closes: #644
Describe the changes you've made ✍

Have created a custom Button component, with the following props:

variant: solid (default) | outline
to: null (default) - pass the to prop with url to use this button as a Link
size: null (default) | sm - used in the navbar
...rest: rest button props can be passed

Replaced the buttons with the Button component
Commented some unused code to avoid linting errors

This is is just for previewing the button styles

@IAmTamal about the size of the button on the banner (hero section), do I have to reduce the size of buttons everywhere or just on the banner?

@IAmTamal about the size of the buttons on the banner (hero section), do I have to reduce the size of buttons everywhere or just on the banner?

Just on the home screen. You can compare it to the currently deployed site


Support for Israel(Tel Aviv) Region "il-central-1"

The solution deployment is failing in Israel(Tel Aviv) Region "il-central-1"
Version: 1.3.2
Released: 11/2023
Additional context
Resource handler returned message: "Access denied for operation 'AWS::CloudFront::Distribution: You don't have permission to access the S3 bucket for CloudFront logs: tlv-video-on-demand2-logs6819bb44-hi0kc3kp3sgr.s3.il-central-1.amazonaws.com If you're using IAM, you need s3:GetBucketAcl and s3:PutBucketAcl permissions to create a distribution or to update log settings for an existing distribution. In addition, the S3 ACL for the bucket must grant you FULL_CONTROL. (Service: CloudFront, Status Code: 403, Request ID: 9055e875-32a7-47b2-8bb6-3c2755592765)'." (RequestToken: 6edcdc85-1361-d6a9-8dd3-6fd77c8752a4, HandlerErrorCode: AccessDenied)

Thank you for your suggestion @veltz-avi. We will consider your feedback to support the solution in the "il-central-1" region in the future, however AWS Elemental MediaConvert is currently not supported in the region.
You can check the list of AWS Services Available by Region here: https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/?p=ngi&loc=4


Standardize License Information in file 'pkg/controllers/v1alpha1/dat…

This pr is to standardize License information in file 'pkg/controllers/v1alpha1/dataprocess/suite_test.go'

/lgtm

/lgtm
/approve


Predicting on One Sentence whose Target is Not Known using Convolutional Seq2Seq

Suppose we are translating from French to English.
So in rnn based encoder-decoder model, we initialize trg sentence as string of  tokens.
Can you please explain how this will be executed in convolution based encoder-decoder module?
In rnn based model we feed the predicted token at time-step t-1  (th) to t (th) step in decoder to get the token at t (th) . I am little bit confused about how this will be done in convolution based decoder.

Yeah, the inference for these non-recurrent models is a bit different.
I'll admit I haven't implemented inference for it yet but I believe the way it works is in a giant loop. In the first iteration of the loop, trg is just a sequence starting with an <sos> token and a few padding tokens(?). You pass the input sentence and this dummy target sentence into the model, then you see what it predicted for the token after the <sos> token (ignoring all other predictions afterward). Say it predicted "the". You then do the second iteration of the loop, however now your trg is <sos> the. You then feed those two into the model again, only caring about it what it predicts for after "the" - say "man". You then do a third iteration of the loop, feeding in <sos> the man. You keep doing this until the model outputs an <eos> token or you've reached some maximum number of tokens generated or some other stopping condition.
Let me know if that sounds sensible or not!
The only thing I am not 100% sure about is if the model will sometimes change it's earlier predictions when predicting future words. For example you could feed in "the man sat on the" and it might output "the woman sat on the floor". Do you just ignore the fact that "man" changed to "woman"? Or maybe it won't ever do this!
I'm hoping to finish the conv seq2seq and the transformer notebooks without inference first, and then go back and write the inference code. Hopefully will be done by the end of this month (maybe)!

According to my intuition in Convolution Seq2Seq teacher forcing ratio is 1.0 while training and maybe that's why it is performing really well on test and validation because we have a trg sentence. Let me know if you think the same.
Yeah, I was also thinking about the giant loop for inferencing if there is no trg sentence present.
I will try writing the code for inferencing using convolution Seq2Seq and analyze the outputs. I will update you if there exists a situation ("man" and "woman" example) like this.
It will also help us to understand the model better and if we are not getting the desired results we can maybe go through their https://github.com/facebookresearch/fairseq . And may even contact the people who published the paper about this.

Yeah, this model will always have a teacher forcing ratio of 1.0 so the validation/test perplexity are lower than they should be. Running the tutorial 3 model with a constant teacher forcing ratio of 1.0 gives the following results:
Epoch: 01 | Time: 0m 55s
	Train Loss: 4.556 | Train PPL:  95.218
	 Val. Loss: 3.598 |  Val. PPL:  36.537
Epoch: 02 | Time: 0m 55s
	Train Loss: 3.314 | Train PPL:  27.492
	 Val. Loss: 2.838 |  Val. PPL:  17.080
Epoch: 03 | Time: 0m 55s
	Train Loss: 2.583 | Train PPL:  13.242
	 Val. Loss: 2.256 |  Val. PPL:   9.545
Epoch: 04 | Time: 0m 55s
	Train Loss: 2.041 | Train PPL:   7.700
	 Val. Loss: 1.948 |  Val. PPL:   7.012
Epoch: 05 | Time: 0m 54s
	Train Loss: 1.665 | Train PPL:   5.285
	 Val. Loss: 1.819 |  Val. PPL:   6.167
Epoch: 06 | Time: 0m 55s
	Train Loss: 1.381 | Train PPL:   3.977
	 Val. Loss: 1.757 |  Val. PPL:   5.796
Epoch: 07 | Time: 0m 55s
	Train Loss: 1.160 | Train PPL:   3.189
	 Val. Loss: 1.768 |  Val. PPL:   5.860
Epoch: 08 | Time: 0m 54s
	Train Loss: 0.990 | Train PPL:   2.691
	 Val. Loss: 1.763 |  Val. PPL:   5.832
Epoch: 09 | Time: 0m 55s
	Train Loss: 0.849 | Train PPL:   2.337
	 Val. Loss: 1.783 |  Val. PPL:   5.947
Epoch: 10 | Time: 0m 55s
	Train Loss: 0.735 | Train PPL:   2.086
	 Val. Loss: 1.817 |  Val. PPL:   6.152

So pretty similar overall. Ideally, I should be comparing BLEU scores instead of perplexity - but have not got around to implementing this yet - and these scores should be done without any teacher forcing - which I can do once inference for the conv. seq2seq model is ready.

@kuldeep7688 In case you are still interested, the convolutional sequence to sequence tutorial now has inference added.


Add placeholder endpoint for server-specific compatibility checks.

This is the server-side part to zulip/zulip-mobile#3158.
@gnprice
@zulipbot add "area: mobile"

I merged the first two commits.  I'm also wondering if we should set a special code for "client too old" so that clients don't need to do parsing of strings (though note that the current string isn't tagged for i18n).

I'm going to close this for now since it's merge-conflicted pretty badly and we're uncertain about the feature; feel free to resubmit once that's been figured out @jackrzhang!


Design Database Schema for Snowboard Tricks and UML's diagram ( sequences, classes, use cases)

completion time: 2days .
Create ULM's diagram to outline the database schema needed for storing snowboard tricks, user information, and discussions. Include tables for tricks, users, comments, and any necessary relationship tables. Consider fields like trick_id, name, description, category, created_at, and updated_at for tricks.

finished diagram classes

finished diagram class, diagram use case and diagram sequence.


Match style of golang-http / java template

We should move from "req" to "event, context" in the same style as the Golang template.
Example: https://github.com/openfaas-incubator/golang-http-template
This will enable us to take advantage of the HTTP abilities of the of-watchdog which we can't currently do.
Alex

Thanks @kturcios how far did you get?


Create a .env file for storing secrets

Secrets like the MongoDB URI are present in the index.js file and can be accessed by anyone. It is preferred to create a .env file for storing such variables.

Thanks for the catch!
This repo is just for a quick demo, so I didn't add in a .env even though I previously installed dotenv - although not adding it is definitely bad practice, I'll be dropping the database inside 48 hours. Hopefully I don't get pwned until then!


Database management UI

This snapshot error appears to be due to the node version change, who's worried? 🙂

Cool, thanks again :+1:
On Mon, 17 Aug 2020 at 16:10, LachlanStuart<EMAIL_ADDRESS>wrote:

@LachlanStuart commented on this pull request.
In metaspace/graphql/schemas/moldb.graphql
https://github.com/metaspace2020/metaspace/pull/638#discussion_r471505115
:

@@ -29,7 +29,7 @@ input CreateMolecularDBInput {
isPublic: Boolean! = False
groupId: ID!
fullName: String

description: String

description: String # JSON-based rich text, in a format defined by tiptap (https://tiptap.scrumpy.io/)

@richardgoater https://github.com/richardgoater Yes.
Migrations shouldn't be changed once they've been merged or deployed.
They're only automatically executed the first time an environment sees
them, so changing a migration that's already in master would mean that
everybody who has run that version of master would have to manually revert
it and re-apply it.
The only exception is when there's an error that has prevented the
migration from running anywhere - it's fine to edit & fix migrations in
such cases.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/metaspace2020/metaspace/pull/638#discussion_r471505115,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAK5BWJ2G7JUJVRXJUVX2JLSBE24XANCNFSM4O2V2PVA
.

@richardgoater Do we still need this branch or it can be deleted?


Modify Query class to let it use the new class diagram code

The new code added from the class diagram refactorization needs to be integrated into the original pipeline of Deeprank-GNN.

Almost done. I'm using the following branch: https://github.com/deepRank/deeprank-GNN-2/tree/add-features-to-query


force ssl

Recently I noticed that http://railsschool.org was no longer redirecting to https://railsschool.org. This PR changes the config file to force SSL.

Closing this because it did not fix the issue


Pointer downX and downY not updated on right mouse click

Version
3.55.2
Description
You can test in the example i provided bellow that clicking with the left mouse populates correctly downX and downY but it's not the case when clicking with mouse right.
Example Test Code
https://codesandbox.io/s/phaser-3-template-forked-5in2cg?file=/index.js

This is correct, as per the documentation: "X coordinate of the Pointer when Button 1 (left button), or Touch, was pressed, used for dragging objects."


Image Uploader - Can't handle server response

Hi,
I'm getting issue with the
image upload process. I'm able to send POST request for image uploading to my server, but my frontend can't handle the server's response and it gives me error "Can't read property 'messages' of undefined ".
Please let me know how can I handle the server's response so that Jodit editor can show my image.
Jodit Version:  3.1.xxxxx
Code
uploader: {
  url: `${Config.API_URL}/${Config.API.pictures}`,
  prepareData: function (data) {
    const file = data.getAll('files[0]')[0];
    data.append('file', file, file.name);
  },
  process: function (resp) {
    console.log(resp)
    debugger
    return {
        path: resp.imagePath,
        baseurl: `${Config.API_URL}/${resp.imagePath}`,
        files: resp.files || [],
        path: resp.path || "",
        error: resp.error,
        msg: resp.msg || ""
    };
  },
}

Screenshot

Server response JSON
{
"id":"0449546014b111a86b708704c178d949",
"category":null,
"tag":null,
"imagePath":"resources/hinhanh/0449546014b111a86b708704c178d949.JPG",
"imageOriginName":"Capture.JPG"
}

Hi all,
Please ignore this, I was able to upload and view my image after editting the response from my backend follow below example.
{
  "success": true,
  "time": "2019-04-21 22:17:02",
  "data": {
    "baseurl": "https://xdsoft.net/jodit/files/",
    "messages": [],
    "files": [
      "Capture.JPG"
    ],
    "isImages": [
      true
    ],
    "code": 220
  }
}


fix pdf generator not found

fix pdf generator not found
fix uom unit undefined if not found

Coverage remained the same at 59.181% when pulling e219ebb7efce68463ad7315b33add9c230063db7 on vfenk:dev into 7b47a8f1627fe5f39260ccc836a23ac6545f0358 on danliris:dev.