Can not use in vue 2 project

export 'Teleport' (imported as 'Teleport') was not found in 'vue-demi'

I'm confused about use @unoverlays/vue or @unoverlays/vue-v2?

In @unoverlays/vue-v2 package, there is not a named export useOverlayMeta.

Hello, vue2 has not been disclosed yet
Yes, vue2 projects cannot use the useOverlayMeta method instead of using the mixinOverlayMeta method
"I am still preparing the API and documentation for vue2, and I hope they can be helpful for some old projects."

https://unoverlays.vercel.app/en/guide/support-vue2.html


how to format a date field?

from a C# datetime value to jsgrid field value, format of date is like : 2016-09-15T11:34:33.6567475+02:00
how can i set date field format ?

Important point: js-grid doesn't have date field. It's just an example in docs.
Since this date field is your custom field, you are free to do formatting yourself. Search for the answer how to set C# datetime to jQuery datepicker, e.g. this one http://stackoverflow.com/questions/24184073/working-with-datetime-date-picker

@tabalinas  thanks a lot.

insertTemplate: function (value) {
return this._insertPicker = $("").datepicker({defaultDate: new Date(),dateFormat: "yy-mm-dd"});
            },

            editTemplate: function (value) {
                return this._editPicker = $("<input>").datepicker({ dateFormat: "yy-mm-dd" }).datepicker("setDate", new Date(value));

            },


Remove result set from google sheets SplitInfo

Returning the entire split as split info can put memory pressure on the coordinator if results are large.

Currently the SheetsSplit is just like VALUES, with the content computed on the coordinator.
Does it make sense to send it to workers at all?
cc @puneetjaiswal

CI failed -- https://github.com/prestosql/presto/issues/2797

Instead of reading it from coordinator can we move it to worker ?

CI failed -- #2797

seems unrelated to this change.
	at io.prestosql.plugin.hive.util.TestThrottledAsyncQueue.testThrottleEmptyQueue(TestThrottledAsyncQueue.java:114)

Merged, thanks!

I merged as a good improvement.
This doesn't address the underlying problem still -- the data should be accessed on worker(s).
Would be good to fix this too.


Investigate / Create firewall rules for Power BI On-premises Data Gateway

Based on the following Support Ticket (https://citz-do.atlassian.net/jira/servicedesk/projects/PCS/queues/custom/25/PCS-21), we have determined that a firewall Application Rule should be created, to allow the various domains through.
These will be generalized such as: *.microsoft.com, *.powerbi.com, *.windows.net, etc.
The following list describes the FQDNs used by the gateway. These endpoints are required for the gateway to function: https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-communication#ports

This will first be applied in FORGE, and then in LIVE.

The following list describes FQDNs used by the gateway. These endpoints are required for the gateway to function:
(Source: https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-communication#ports)

The following list describes FQDNs used by the gateway. These endpoints are required for the gateway to function:
(Source: https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-communication#ports)

Tracking in Jira
https://citz-do.atlassian.net/browse/PCS-21


Please invite me to the Recode-Hive GitHub Community Organization

Name
PRIYESH SINGH
Discord Username (if applicable)
No response
Additional Context
No response

Invitation sent to join the GitHub Organisation. Welcome to the community 🎉
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see. You can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/recodehive/people


Minor tidy and tweak

Took your code and made some tweaks, just sending it back out of courtesy. Feel free to ignore it.

Added commenting all over the shop, to make me happy
Made is_locked a property
Added Py3 type hints
Changed the timeout check logic to agree with my world view
Added force_release option to release method, which deletes rogue locks
Changed exit parameters to generic *args, **kwargs

Opps, comparator the wrong way round


Tweak the home page using animations, neomorphic design and doodles to give a cool outlook!

Is your feature request related to a problem? Please describe.
Not as such, but the home page is quite pant, and not attractive. Being just a single page, the page must be designed specifically to give a modern feel.
Describe the solution you'd like.
Me being a UI/UX engineer, would like to use Tailwind CSS, neumorphic design and graphical doodles to markup a cool web interface.
Describe alternatives you've considered.
Any other CSS framework would take a toll on deadlines, but Tailwind is fast, lightweight and easy to work on the go.
Add any other context or screenshots about the feature request here.
Myself being a GSSOC '22 contributor would like to work on this issue.

Sure @dasgupta002

@dasgupta002 any Update regarding your modifications??

Doing the finishing touches, would push my changes today itself!

I would like to work on this issue. Could you assign this to me?

I would like to work on this issue. Could you assign this to me for GSSoC'23

Sure @alivia-ansari


[x] I have searched the issue tracker and believe that this is not a duplicate.

Make sure you run commands with -v flag before pasting the output.
Steps to reproduce

pdm install -v in checkout of this commit: https://github.com/copier-org/copier/pull/357/commits/5ffe2d096837c21466400145d812dc03470f1ca4
Actual behavior

Traceback (most recent call last):
  File "/var/home/yajo/.local/bin/pdm", line 8, in <module>
    sys.exit(main())
  File "/var/home/yajo/.local/pipx/venvs/pdm/lib64/python3.9/site-packages/pdm/core.py", line 73, in __call__
    return self.main(*args, **kwargs)
  File "/var/home/yajo/.local/pipx/venvs/pdm/lib64/python3.9/site-packages/pdm/core.py", line 112, in main
    raise err.with_traceback(traceback)
  File "/var/home/yajo/.local/pipx/venvs/pdm/lib64/python3.9/site-packages/pdm/core.py", line 108, in main
    f(options.project, options)
  File "/var/home/yajo/.local/pipx/venvs/pdm/lib64/python3.9/site-packages/pdm/cli/commands/install.py", line 39, in handle
    actions.do_sync(
  File "/var/home/yajo/.local/pipx/venvs/pdm/lib64/python3.9/site-packages/pdm/cli/actions.py", line 123, in do_sync
    candidates.update(project.get_locked_candidates())
  File "/var/home/yajo/.local/pipx/venvs/pdm/lib64/python3.9/site-packages/pdm/project/core.py", line 315, in get_locked_candidates
    if section != "__all__" and section not in package["sections"]:
KeyError: 'sections'

Expected behavior

No failure.
Environment Information
# Paste the output of `pdm info && pdm info --env` below:
PDM version:        1.3.1
Python Interpreter: /usr/bin/python (3.9.1)
Project Root:       /var/home/yajo/mydevel/copier
{
  "implementation_name": "cpython",
  "implementation_version": "3.9.1",
  "os_name": "posix",
  "platform_machine": "x86_64",
  "platform_release": "5.10.12-200.fc33.x86_64",
  "platform_system": "Linux",
  "platform_version": "#1 SMP Mon Feb 1 02:40:52 UTC 2021",
  "python_full_version": "3.9.1",
  "platform_python_implementaiton": "CPython",
  "python_version": "3.9",
  "sys_platform": "linux"
}

try generating the lock file again?

Actually it happens while generating it (1st time pdm install ever). I ran it with -v:

➤ pdm install -v
Lock file does not exist, trying to generate one...
======== Start resolving requirements ========
        backports.cached-property<2.0.0,>=1.0.0; python_version < "3.8"
        colorama<1.0.0,>=0.4.3
        iteration-utilities<1.0.0,>=0.10.1
        jinja2<3.0.0,>=2.11.2
        packaging<21.0,>=20.4
        pathspec<1.0.0,>=0.8.0
        plumbum<2.0.0,>=1.6.9
        pydantic<2.0.0,>=1.7.2
        Pygments<3.0.0,>=2.7.1
        pyyaml<6.0.0,>=5.3.1
        pyyaml-include<2.0,>=1.2
        questionary<2.0.0,>=1.8.1
        typing-extensions<4.0.0,>=3.7.4; python_version < "3.8"
        autoflake<2.0,>=1.4
        black<21.0,>=20.8b1
        flake8<4.0.0,>=3.8.4
        flake8-bugbear<21.0.0,>=20.1.4
        flake8-comprehensions<4.0.0,>=3.2.3
        flake8-debugger<4.0.0,>=3.2.1
        mypy<1.0,>=0.790
        pexpect<5.0.0,>=4.8.0
        pre-commit<3.0.0,>=2.7.1
        pytest<7.0.0,>=6.1.1
        pytest-cov<3.0.0,>=2.10.1
        pytest-xdist<3.0.0,>=2.1.0
        mkdocs-material<6.0.0,>=5.5.2
        mkdocs-mermaid2-plugin<1.0.0,>=0.5.0
        git+https://github.com/pawamoy/mkdocstrings.git@master#egg=mkdocstrings
        git+https://github.com/pawamoy/pytkdocs.git@master#egg=pytkdocs
        Adding requirement backports.cached-property<2.0.0,>=1.0.0; python_version < "3.8"
        Adding requirement colorama<1.0.0,>=0.4.3
        Adding requirement iteration-utilities<1.0.0,>=0.10.1
        Adding requirement jinja2<3.0.0,>=2.11.2
        Adding requirement packaging<21.0,>=20.4
        Adding requirement pathspec<1.0.0,>=0.8.0
        Adding requirement plumbum<2.0.0,>=1.6.9
        Adding requirement pydantic<2.0.0,>=1.7.2
        Adding requirement Pygments<3.0.0,>=2.7.1
        Adding requirement pyyaml<6.0.0,>=5.3.1
        Adding requirement pyyaml-include<2.0,>=1.2
        Adding requirement questionary<2.0.0,>=1.8.1
        Adding requirement typing-extensions<4.0.0,>=3.7.4; python_version < "3.8"
        Adding requirement autoflake<2.0,>=1.4
        Adding requirement black<21.0,>=20.8b1
        Adding requirement flake8<4.0.0,>=3.8.4
        Adding requirement flake8-bugbear<21.0.0,>=20.1.4
        Adding requirement flake8-comprehensions<4.0.0,>=3.2.3
        Adding requirement flake8-debugger<4.0.0,>=3.2.1
        Adding requirement mypy<1.0,>=0.790
        Adding requirement pexpect<5.0.0,>=4.8.0
        Adding requirement pre-commit<3.0.0,>=2.7.1
        Adding requirement pytest<7.0.0,>=6.1.1
        Adding requirement pytest-cov<3.0.0,>=2.10.1
        Adding requirement pytest-xdist<3.0.0,>=2.1.0
        Adding requirement mkdocs-material<6.0.0,>=5.5.2
        Adding requirement mkdocs-mermaid2-plugin<1.0.0,>=0.5.0
        Adding requirement git+https://github.com/pawamoy/mkdocstrings.git@master#egg=mkdocstrings
Preparing isolated env for PEP 517 build...
Collecting poetry-core
  Using cached poetry_core-1.0.2-py2.py3-none-any.whl (424 kB)
Installing collected packages: poetry-core
Successfully installed poetry-core-1.0.2
        Adding requirement git+https://github.com/pawamoy/pytkdocs.git@master#egg=pytkdocs
Preparing isolated env for PEP 517 build...

Collecting poetry-core
  Using cached poetry_core-1.0.2-py2.py3-none-any.whl (424 kB)
Installing collected packages: poetry-core
Successfully installed poetry-core-1.0.2
Resolving: mkdocstrings 0.14.0
        New pin: mkdocstrings 0.14.0
======== Ending round 3 ========
        Adding requirement cached-property<2.0.0,>=1.5.2; python_version < "3.8"(from pytkdocs 0.10.1)
        Adding requirement dataclasses<0.9,>=0.7; python_version == "3.6"(from pytkdocs 0.10.1)
        Adding requirement typing-extensions<<IP_ADDRESS>,>=<IP_ADDRESS>; python_version < "3.8"(from pytkdocs 0.10.1)
Resolving: pytkdocs 0.10.1
        New pin: pytkdocs 0.10.1
======== Ending round 4 ========
        Adding requirement pyflakes<2.3.0,>=2.2.0(from flake8 3.8.4)
        Adding requirement pycodestyle<2.7.0,>=2.6.0a1(from flake8 3.8.4)
        Adding requirement mccabe<0.7.0,>=0.6.0(from flake8 3.8.4)
        Adding requirement importlib-metadata; python_version < "3.8"(from flake8 3.8.4)
Resolving: flake8 3.8.4
        New pin: flake8 3.8.4
======== Ending round 5 ========
        Adding requirement ptyprocess>=0.5(from pexpect 4.8.0)
Resolving: pexpect 4.8.0
        New pin: pexpect 4.8.0
======== Ending round 6 ========
Resolving: pyflakes 2.2.0
        New pin: pyflakes 2.2.0
======== Ending round 7 ========
Resolving: click 7.1.2
        New pin: click 7.1.2
======== Ending round 8 ========
Resolving: mypy-extensions 0.4.3
        New pin: mypy-extensions 0.4.3
======== Ending round 9 ========
Resolving: pycodestyle 2.6.0
        New pin: pycodestyle 2.6.0
======== Ending round 10 ========
Resolving: cached-property 1.5.2
        New pin: cached-property 1.5.2
======== Ending round 11 ========
Resolving: typing-extensions <IP_ADDRESS>
        New pin: typing-extensions <IP_ADDRESS>
======== Ending round 12 ========
Resolving: colorama 0.4.4
        New pin: colorama 0.4.4
======== Ending round 13 ========
        Adding requirement MarkupSafe>=0.23(from jinja2 2.11.3)
Resolving: jinja2 2.11.3
        New pin: jinja2 2.11.3
======== Ending round 14 ========
Resolving: pathspec 0.8.1
        New pin: pathspec 0.8.1
======== Ending round 15 ========
        Adding requirement pypiwin32; platform_system == "Windows" and platform_python_implementation != "PyPy"(from plumbum 1.7.0)
Resolving: plumbum 1.7.0
        New pin: plumbum 1.7.0
======== Ending round 16 ========
        Adding requirement prompt-toolkit<4.0,>=2.0(from questionary 1.9.0)
Resolving: questionary 1.9.0
        New pin: questionary 1.9.0
======== Ending round 17 ========
        Adding requirement flake8>=3.0.0(from flake8-bugbear 20.11.1)
        Adding requirement attrs>=19.2.0(from flake8-bugbear 20.11.1)
Resolving: flake8-bugbear 20.11.1
        New pin: flake8-bugbear 20.11.1
======== Ending round 18 ========
        Adding requirement setuptools>=18.5(from mkdocs-mermaid2-plugin 0.5.1)
        Adding requirement beautifulsoup4>=4.6.3(from mkdocs-mermaid2-plugin 0.5.1)
        Adding requirement mkdocs>=1.0.4(from mkdocs-mermaid2-plugin 0.5.1)
        Adding requirement jsbeautifier(from mkdocs-mermaid2-plugin 0.5.1)
        Adding requirement pyyaml(from mkdocs-mermaid2-plugin 0.5.1)
        Adding requirement mkdocs-material(from mkdocs-mermaid2-plugin 0.5.1)
        Adding requirement requests(from mkdocs-mermaid2-plugin 0.5.1)
        Adding requirement pymdown-extensions>=8.0(from mkdocs-mermaid2-plugin 0.5.1)
Resolving: mkdocs-mermaid2-plugin 0.5.1
        New pin: mkdocs-mermaid2-plugin 0.5.1
======== Ending round 19 ========
Resolving: toml 0.10.2
        New pin: toml 0.10.2
======== Ending round 20 ========
Resolving: dataclasses 0.8
        New pin: dataclasses 0.8
======== Ending round 21 ========
Resolving: mccabe 0.6.1
        New pin: mccabe 0.6.1
======== Ending round 22 ========
        Adding requirement PyYAML<6.0,>=5.3.1(from pyyaml-include 1.2.post2)
Resolving: pyyaml-include 1.2.post2
        New pin: pyyaml-include 1.2.post2
======== Ending round 23 ========
        Adding requirement flake8!=3.2.0,<4,>=3.0(from flake8-comprehensions 3.3.1)
        Adding requirement importlib-metadata; python_version < "3.8"(from flake8-comprehensions 3.3.1)
Resolving: flake8-comprehensions 3.3.1
        New pin: flake8-comprehensions 3.3.1
======== Ending round 24 ========
        Adding requirement pytest>=4.6(from pytest-cov 2.11.1)
        Adding requirement coverage>=5.2.1(from pytest-cov 2.11.1)
Resolving: pytest-cov 2.11.1
        New pin: pytest-cov 2.11.1
======== Ending round 25 ========
        Adding requirement execnet>=1.1(from pytest-xdist 2.2.1)
        Adding requirement pytest>=6.0.0(from pytest-xdist 2.2.1)
        Adding requirement pytest-forked(from pytest-xdist 2.2.1)
Resolving: pytest-xdist 2.2.1
        New pin: pytest-xdist 2.2.1
======== Ending round 26 ========
        Adding requirement click>=3.3(from mkdocs 1.1.2)
        Adding requirement Jinja2>=2.10.1(from mkdocs 1.1.2)
        Adding requirement livereload>=2.5.1(from mkdocs 1.1.2)
        Adding requirement lunr[languages]==0.5.8(from mkdocs 1.1.2)
        Adding requirement Markdown>=3.2.1(from mkdocs 1.1.2)
        Adding requirement PyYAML>=3.10(from mkdocs 1.1.2)
        Adding requirement tornado>=5.0(from mkdocs 1.1.2)
Resolving: mkdocs 1.1.2
        New pin: mkdocs 1.1.2
======== Ending round 27 ========
        Adding requirement future>=0.16.0(from lunr 0.5.8)
        Adding requirement six>=1.11.0(from lunr 0.5.8)
        Adding requirement nltk>=3.2.5; python_version > "2.7"(from lunr 0.5.8)
        Adding requirement lunr==0.5.8(from lunr 0.5.8)
Resolving: lunr 0.5.8
        New pin: lunr 0.5.8
======== Ending round 28 ========
        Adding requirement future>=0.16.0(from lunr 0.5.8)
        Adding requirement six>=1.11.0(from lunr 0.5.8)
Resolving: lunr 0.5.8
        New pin: lunr 0.5.8
======== Ending round 29 ========
        Adding requirement importlib-metadata; python_version < "3.8"(from Markdown 3.3.3)
Resolving: Markdown 3.3.3
        New pin: Markdown 3.3.3
======== Ending round 30 ========
        Adding requirement Markdown>=3.2(from pymdown-extensions 8.1.1)
Resolving: pymdown-extensions 8.1.1
        New pin: pymdown-extensions 8.1.1
======== Ending round 31 ========
Resolving: future 0.18.2
        New pin: future 0.18.2
======== Ending round 32 ========
Resolving: ptyprocess 0.7.0
        New pin: ptyprocess 0.7.0
======== Ending round 33 ========
        Adding requirement click(from nltk 3.5)
        Adding requirement joblib(from nltk 3.5)
        Adding requirement regex(from nltk 3.5)
        Adding requirement tqdm(from nltk 3.5)
Resolving: nltk 3.5
        New pin: nltk 3.5
======== Ending round 34 ========
        Adding requirement typing>=3.6; python_version < "3.7"(from backports.cached-property 1.0.1)
Resolving: backports.cached-property 1.0.1
        New pin: backports.cached-property 1.0.1
======== Ending round 35 ========
Resolving: Pygments 2.8.0
        New pin: Pygments 2.8.0
======== Ending round 36 ========
        Adding requirement attrs>=19.2.0(from pytest 6.2.2)
        Adding requirement iniconfig(from pytest 6.2.2)
        Adding requirement packaging(from pytest 6.2.2)
        Adding requirement pluggy<1.0.0a1,>=0.12(from pytest 6.2.2)
        Adding requirement py>=1.8.2(from pytest 6.2.2)
        Adding requirement toml(from pytest 6.2.2)
        Adding requirement importlib-metadata>=0.12; python_version < "3.8"(from pytest 6.2.2)
        Adding requirement atomicwrites>=1.0; sys_platform == "win32"(from pytest 6.2.2)
        Adding requirement colorama; sys_platform == "win32"(from pytest 6.2.2)
Resolving: pytest 6.2.2
        New pin: pytest 6.2.2
======== Ending round 37 ========
        Adding requirement importlib-metadata>=0.12; python_version < "3.8"(from pluggy 0.13.1)
Resolving: pluggy 0.13.1
        New pin: pluggy 0.13.1
======== Ending round 38 ========
Resolving: py 1.10.0
        New pin: py 1.10.0
======== Ending round 39 ========
Resolving: iniconfig 1.1.1
        New pin: iniconfig 1.1.1
======== Ending round 40 ========
Resolving: attrs 20.3.0
        New pin: attrs 20.3.0
======== Ending round 41 ========
        Adding requirement six(from livereload 2.6.3)
        Adding requirement tornado; python_version > "2.7"(from livereload 2.6.3)
Resolving: livereload 2.6.3
        New pin: livereload 2.6.3
======== Ending round 42 ========
Resolving: six 1.15.0
        New pin: six 1.15.0
======== Ending round 43 ========
        Adding requirement pyparsing>=2.0.2(from packaging 20.9)
Resolving: packaging 20.9
        New pin: packaging 20.9
======== Ending round 44 ========
Resolving: appdirs 1.4.4
        New pin: appdirs 1.4.4
======== Ending round 45 ========
Resolving: atomicwrites 1.4.0
        New pin: atomicwrites 1.4.0
======== Ending round 46 ========
        Adding requirement py(from pytest-forked 1.3.0)
        Adding requirement pytest>=3.10(from pytest-forked 1.3.0)
Resolving: pytest-forked 1.3.0
        New pin: pytest-forked 1.3.0
======== Ending round 47 ========
        Adding requirement pywin32>=223(from pypiwin32 223)
Resolving: pypiwin32 223
        New pin: pypiwin32 223
======== Ending round 48 ========
Resolving: typing <IP_ADDRESS>
        New pin: typing <IP_ADDRESS>
======== Ending round 49 ========
        Adding requirement cfgv>=2.0.0(from pre-commit 2.10.1)
        Adding requirement identify>=1.0.0(from pre-commit 2.10.1)
        Adding requirement nodeenv>=0.11.1(from pre-commit 2.10.1)
        Adding requirement pyyaml>=5.1(from pre-commit 2.10.1)
        Adding requirement toml(from pre-commit 2.10.1)
        Adding requirement virtualenv>=20.0.8(from pre-commit 2.10.1)
        Adding requirement importlib-resources; python_version < "3.7"(from pre-commit 2.10.1)
        Adding requirement importlib-metadata; python_version < "3.8"(from pre-commit 2.10.1)
Resolving: pre-commit 2.10.1
        New pin: pre-commit 2.10.1
======== Ending round 50 ========
Resolving: cfgv 3.2.0
        New pin: cfgv 3.2.0
======== Ending round 51 ========
        Adding requirement apipkg>=1.4(from execnet 1.8.0)
Resolving: execnet 1.8.0
        New pin: execnet 1.8.0
======== Ending round 52 ========
Resolving: apipkg 1.5
        New pin: apipkg 1.5
======== Ending round 53 ========
        Adding requirement mkdocs>=1.1(from mkdocs-material 5.5.14)
        Adding requirement Pygments>=2.4(from mkdocs-material 5.5.14)
        Adding requirement markdown>=3.2(from mkdocs-material 5.5.14)
        Adding requirement pymdown-extensions>=7.0(from mkdocs-material 5.5.14)
        Adding requirement mkdocs-material-extensions>=1.0(from mkdocs-material 5.5.14)
Resolving: mkdocs-material 5.5.14
        New pin: mkdocs-material 5.5.14
======== Ending round 54 ========
        Adding requirement mkdocs-material>=5.0.0(from mkdocs-material-extensions 1.0.1)
Resolving: mkdocs-material-extensions 1.0.1
        New pin: mkdocs-material-extensions 1.0.1
======== Ending round 55 ========
        Adding requirement soupsieve>1.2; python_version >= "3.0"(from beautifulsoup4 4.9.3)
Resolving: beautifulsoup4 4.9.3
        New pin: beautifulsoup4 4.9.3
======== Ending round 56 ========
Resolving: nodeenv 1.5.0
        New pin: nodeenv 1.5.0
======== Ending round 57 ========
        Adding requirement dataclasses>=0.6; python_version < "3.7"(from pydantic 1.7.3)
Resolving: pydantic 1.7.3
        New pin: pydantic 1.7.3
======== Ending round 58 ========
Resolving: soupsieve 2.2
        New pin: soupsieve 2.2
======== Ending round 59 ========
Resolving: iteration-utilities 0.11.0
        New pin: iteration-utilities 0.11.0
======== Ending round 60 ========
Resolving: pyyaml 5.4.1
        New pin: pyyaml 5.4.1
======== Ending round 61 ========
        Adding requirement zipp>=0.4; python_version < "3.8"(from importlib-resources 5.1.0)
Resolving: importlib-resources 5.1.0
        New pin: importlib-resources 5.1.0
======== Ending round 62 ========
Resolving: zipp 3.4.0
        New pin: zipp 3.4.0
======== Ending round 63 ========
        Adding requirement typed-ast<1.5.0,>=1.4.0(from mypy 0.812)
        Adding requirement typing-extensions>=3.7.4(from mypy 0.812)
        Adding requirement mypy-extensions<0.5.0,>=0.4.3(from mypy 0.812)
Resolving: mypy 0.812
        New pin: mypy 0.812
======== Ending round 64 ========
        Adding requirement six>=1.13.0(from jsbeautifier 1.13.5)
        Adding requirement editorconfig>=0.12.2(from jsbeautifier 1.13.5)
Resolving: jsbeautifier 1.13.5
        New pin: jsbeautifier 1.13.5
======== Ending round 65 ========
Resolving: editorconfig 0.12.3
        New pin: editorconfig 0.12.3
======== Ending round 66 ========
        Adding requirement wcwidth(from prompt-toolkit 3.0.16)
Resolving: prompt-toolkit 3.0.16
        New pin: prompt-toolkit 3.0.16
======== Ending round 67 ========
Resolving: wcwidth 0.2.5
        New pin: wcwidth 0.2.5
======== Ending round 68 ========
        Adding requirement zipp>=0.5(from importlib-metadata 3.6.0)
        Adding requirement typing-extensions>=3.6.4; python_version < "3.8"(from importlib-metadata 3.6.0)
Resolving: importlib-metadata 3.6.0
        New pin: importlib-metadata 3.6.0
======== Ending round 69 ========
Resolving: pywin32 300
        New pin: pywin32 300
======== Ending round 70 ========
        Adding requirement appdirs<2,>=1.4.3(from virtualenv 20.4.2)
        Adding requirement distlib<1,>=0.3.1(from virtualenv 20.4.2)
        Adding requirement filelock<4,>=3.0.0(from virtualenv 20.4.2)
        Adding requirement six<2,>=1.9.0(from virtualenv 20.4.2)
        Adding requirement importlib-resources>=1.0; python_version < "3.7"(from virtualenv 20.4.2)
        Adding requirement importlib-metadata>=0.12; python_version < "3.8"(from virtualenv 20.4.2)
Resolving: virtualenv 20.4.2
        New pin: virtualenv 20.4.2
======== Ending round 71 ========
Resolving: distlib 0.3.1
        New pin: distlib 0.3.1
======== Ending round 72 ========
Resolving: filelock 3.0.12
        New pin: filelock 3.0.12
======== Ending round 73 ========
Resolving: joblib 1.0.1
        New pin: joblib 1.0.1
======== Ending round 74 ========
Resolving: pyparsing 2.4.7
        New pin: pyparsing 2.4.7
======== Ending round 75 ========
Resolving: typed-ast 1.4.2
        New pin: typed-ast 1.4.2
======== Ending round 76 ========
Resolving: MarkupSafe 1.1.1
        New pin: MarkupSafe 1.1.1
======== Ending round 77 ========
Resolving: tornado 6.1
        New pin: tornado 6.1
======== Ending round 78 ========
Resolving: identify 1.5.14
        New pin: identify 1.5.14
======== Ending round 79 ========
Resolving: coverage 5.4
        New pin: coverage 5.4
======== Ending round 80 ========
        Adding requirement chardet<5,>=3.0.2(from requests 2.25.1)
        Adding requirement idna<3,>=2.5(from requests 2.25.1)
        Adding requirement urllib3<1.27,>=1.21.1(from requests 2.25.1)
        Adding requirement certifi>=2017.4.17(from requests 2.25.1)
Resolving: requests 2.25.1
        New pin: requests 2.25.1
======== Ending round 81 ========
Resolving: chardet 4.0.0
        New pin: chardet 4.0.0
======== Ending round 82 ========
Resolving: idna 2.10
        New pin: idna 2.10
======== Ending round 83 ========
Resolving: certifi 2020.12.5
        New pin: certifi 2020.12.5
======== Ending round 84 ========
Resolving: urllib3 1.26.3
        New pin: urllib3 1.26.3
======== Ending round 85 ========
Resolving: tqdm 4.57.0
        New pin: tqdm 4.57.0
======== Ending round 86 ========
Resolving: regex 2020.11.13
        New pin: regex 2020.11.13
======== Ending round 87 ========
Resolving: setuptools 53.0.0
        New pin: setuptools 53.0.0
======== Ending round 88 ========
Finish resolving
======== Resolution Result ========
Stable pins:
                   autoflake 1.4
                       black 20.8b1
             flake8-debugger 3.2.1
                mkdocstrings 0.14.0
                    pytkdocs 0.10.1
                      flake8 3.8.4
                     pexpect 4.8.0
                    pyflakes 2.2.0
                       click 7.1.2
             mypy-extensions 0.4.3
                 pycodestyle 2.6.0
             cached-property 1.5.2
           typing-extensions <IP_ADDRESS>
                    colorama 0.4.4
                      jinja2 2.11.3
                    pathspec 0.8.1
                     plumbum 1.7.0
                 questionary 1.9.0
              flake8-bugbear 20.11.1
      mkdocs-mermaid2-plugin 0.5.1
                        toml 0.10.2
                 dataclasses 0.8
                      mccabe 0.6.1
              pyyaml-include 1.2.post2
       flake8-comprehensions 3.3.1
                  pytest-cov 2.11.1
                pytest-xdist 2.2.1
                      mkdocs 1.1.2
             lunr[languages] 0.5.8
                        lunr 0.5.8
                    markdown 3.3.3
          pymdown-extensions 8.1.1
                      future 0.18.2
                  ptyprocess 0.7.0
                        nltk 3.5
   backports.cached-property 1.0.1
                    pygments 2.8.0
                      pytest 6.2.2
                      pluggy 0.13.1
                          py 1.10.0
                   iniconfig 1.1.1
                       attrs 20.3.0
                  livereload 2.6.3
                         six 1.15.0
                   packaging 20.9
                     appdirs 1.4.4
                atomicwrites 1.4.0
               pytest-forked 1.3.0
                   pypiwin32 223
                      typing <IP_ADDRESS>
                  pre-commit 2.10.1
                        cfgv 3.2.0
                     execnet 1.8.0
                      apipkg 1.5
             mkdocs-material 5.5.14
  mkdocs-material-extensions 1.0.1
              beautifulsoup4 4.9.3
                     nodeenv 1.5.0
                    pydantic 1.7.3
                   soupsieve 2.2
         iteration-utilities 0.11.0
                      pyyaml 5.4.1
         importlib-resources 5.1.0
                        zipp 3.4.0
                        mypy 0.812
                jsbeautifier 1.13.5
                editorconfig 0.12.3
              prompt-toolkit 3.0.16
                     wcwidth 0.2.5
          importlib-metadata 3.6.0
                     pywin32 300
                  virtualenv 20.4.2
                     distlib 0.3.1
                    filelock 3.0.12
                      joblib 1.0.1
                   pyparsing 2.4.7
                   typed-ast 1.4.2
                  markupsafe 1.1.1
                     tornado 6.1
                    identify 1.5.14
                    coverage 5.4
                    requests 2.25.1
                     chardet 4.0.0
                        idna 2.10
                     certifi 2020.12.5
                     urllib3 1.26.3
                        tqdm 4.57.0
                       regex 2020.11.13
                  setuptools 53.0.0
Extracting package metadata
🔒 Lock successful
Changes are written to pdm.lock.
Traceback (most recent call last):
  File "/var/home/yajo/.local/bin/pdm", line 8, in <module>
    sys.exit(main())
  File "/var/home/yajo/.local/pipx/venvs/pdm/lib64/python3.9/site-packages/pdm/core.py", line 73, in __call__
    return self.main(*args, **kwargs)
  File "/var/home/yajo/.local/pipx/venvs/pdm/lib64/python3.9/site-packages/pdm/core.py", line 112, in main
    raise err.with_traceback(traceback)
  File "/var/home/yajo/.local/pipx/venvs/pdm/lib64/python3.9/site-packages/pdm/core.py", line 108, in main
    f(options.project, options)
  File "/var/home/yajo/.local/pipx/venvs/pdm/lib64/python3.9/site-packages/pdm/cli/commands/install.py", line 39, in handle
    actions.do_sync(
  File "/var/home/yajo/.local/pipx/venvs/pdm/lib64/python3.9/site-packages/pdm/cli/actions.py", line 123, in do_sync
    candidates.update(project.get_locked_candidates())
  File "/var/home/yajo/.local/pipx/venvs/pdm/lib64/python3.9/site-packages/pdm/project/core.py", line 315, in get_locked_candidates
    if section != "__all__" and section not in package["sections"]:
KeyError: 'sections'

It is caused by some circular dependencies in the docs section. You can temporarily workaround it by pdm lock in the current project directory and then you can install successfully

That unlocked my problem. I also stopped installing some deps from git because of the dependency conflict they introduce (affects poetry too, see https://github.com/copier-org/copier/issues/362). Thank you!
Maybe the error message could be more helpful here.


#[serde(default="false")] failed to parse path: "false"

Code:
#[macro_use]
extern crate serde_derive;
extern crate serde;

#[derive(Deserialize)]
struct A {
  #[serde(default="false")]
  a: bool,
}

fn main() {
    println!("Hello, world!");
}

Link to playground:
https://play.rust-lang.org/?gist=8792a9fd44c0fff060f54e8f3b5281c3&version=stable

It seems you can work around it by creating a constant that is set to false.

Thanks! We are tracking this in #368.

For anyone coming across this and #368 has not been merged, a workaround can be:
#[macro_use]
extern crate serde_derive;
extern crate serde;

fn default_as_false() -> bool {
    false
}

#[derive(Deserialize)]
struct A {
  #[serde(default="default_as_false")]
  a: bool,
}

fn main() {
    println!("Hello, world!");
}

Link to playground:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2015&gist=12e58011d3cb46ba08e849e8a20592d5

@erichschroeter FWIW you can use bool::default which is false -- no need to roll your own function
#[derive(Deserialize)]
struct A {
  #[serde(default="bool::default")]
  a: bool,
}

Also noting this seems to work:
#[derive(Deserialize)]
struct A {
  #[serde(default)]
  a: bool,
}

for anyone craving a more or less clean solution it can be achieved with const generics
Playground
The behavior is a bit off, but deterministic
Should I add a PR with those?


Create Learning Resources Markdown

Create a core textbook md file
Create a exam prep guide md file

Learning resources file is here on dev: https://github.com/RConsortium/R-Certification-WG/blob/dev/Curriculum/Exam Readiness/Learning Resources.md
Please add any material you feel is relevant and we can organize later.


Lodash and moment.js really necessary?

We just managed to integrate vuex-orm in our project, but had to determine that it adds ~1mb in vendor-files by adding complete lodash.js and moment.js.
Is this really necessary?

Hi! Thank you so much for using Vuex ORM!
Vuex ORM uses lodash and moment but I too agree that it doesn't need complete lodash.js and moment.js.
The reason why this is happening is because me lacking the knowledge of bundling TypeScript...
Do you know any way to add only required functions from lodash or moment? Or would it make difference if I move those library to peer dependencies in package.json?

Thanks for your reply.
I never touched TypeScript, so i can't help you with that.
For lodash in ES6, you could just use import debounce from 'lodash/debounce' to only get debounce and required additional functions.
The problem with moment.js is mainly, that it adds all localizations, even if you need only one. For your project, that might be necessary, since you need to support all languages as well, but i might ask, if you need that date-mutation at all, or if you could handle the developer such things?
For examle, we already use date-fns in our project to parse and transform dates...

For lodash in ES6, you could just use import debounce from 'lodash/debounce' to only get debounce and required additional functions.

Ahah. That is easy. OK I'll do that.

if you need that date-mutation at all, or if you could handle the developer such things? For examle, we already use date-fns in our project to parse and transform dates...

You have good point. date-mutation is just "nice to have" feature and definitely not the must. I wasn't thinking so deeply about this but I agree that Vuex ORM should have little dependencies as possible.
So, I'm thinking to add more general mutation feature and remove moment from this package. Something like below.
import Model from 'vuex-orm/lib/Model'
import moment from 'moment'

class Post extends Model {
  static entity = 'posts'

  static fields () {
    return {
      // Pass callback to the attribute to mutate data.
      published_at: this.attr('1985-10-10', value => moment(value))
    }
  }

  // Or we could add such thing as a method separately...?
  static mutations () {
    return {
      published_at (value) {
        return moment(value)
      }
    }
  }
}

The above will do same as current this.date but now mutation behavior is up to developer. This way maybe you could use date-fns in similar way too.
So I'll first fix lodash issue and then remove moment from the project. Let me know if you have any advise on general mutator approach (the example of new API above).

@CinKon Just wanted to let you know that I released v0.9.0 which includes breaking change on import syntax. From version 0.9.0, you must use following syntax.
// Instead of these...
import Database from 'vuex-orm/lib/Database'
import Model from 'vuex-orm/lib/Model'

// Now you have to...
import { Database } from 'vuex-orm'
import { Model } from 'vuex-orm'

Also you must call install method when registering Vuex ORM as a plugin to the Vuex.
import VuexORM from 'vuex-orm'

store = new Vuex.Store({
  plugin: [VuexORM.install(database)]
})

I've updated the docs as well. Sorry for the inconvenience.

Please take care of your documentation ;)
store = new Vuex.Store({
  plugin: [VuexORM.install(database)]
})

This wont work.
Either
store = new Vuex.Store({
  plugin: VuexORM.install(database)
})

Or
store = new Vuex.Store({
  plugins: [VuexORM.install(database)]
})

I found this inconsistency in your gitbook as well.

But thanks for the update 👍

import { install as VuexORMInstall, Database } from 'vuex-orm'

const database = new Database()
database.register(User, user)

store = new Vuex.Store({
  plugins: [VuexORMInstall(database)]
})

For completeness ;)
With this, eslint goes crazy (Caution: VuexORMalso has a named exportinstall. Check if you meant to write import {install} from 'vuex-orm' instead)
import VuexORM, { Database } from 'vuex-orm'

store = new Vuex.Store({
  plugins: [VuexORM.install(database)]
})

Wow, thank you for the fix! (as always). I've updated the doc and published.

OK, I've removed moment and introduced a new way to define mutator and released 0.10.0! You can find docs at https://revolver-app.gitbooks.io/vuex-orm/model/mutators.html.
This has reduced the bundle size to about half before moment. I hope it helps reducing your project bundle size as well :)

Thanks for your fast fixes!


Bundles still prompt for installation with NeoBundleFetch

Say a bundle x depends on bundle y, if I understand correctly from the doc I can use NeoBundleFetch to register y, and NeoBundleCheck should not prompt for installing y?

This is especially needed if y is a non-vim plugin, which is what NeoBundleFetch is for.
It seems that if I create an empty dir x in ~/.vim/bundle, the installation prompt goes away, but y can be a non-vim plugin installed somewhere else.

Minimum vimrc to reproduce:
set nocompatible
filetype off
set runtimepath+=$HOME/.vim/bundle/neobundle.vim/
call neobundle#begin('$HOME/.vim/bundle')
NeoBundleFetch 'Shougo/neobundle.vim'
NeoBundleFetch 'davidhalter/jedi'
NeoBundle 'davidhalter/jedi-vim', {
\ 'depends' : ['davidhalter/jedi'],
\ }
NeoBundleCheck
call neobundle#end()
filetype plugin indent on

Say a bundle x depends on bundle y, if I understand correctly from the doc I can use NeoBundleFetch to register y, and NeoBundleCheck should not prompt for installing y?

No.  It installs y.
NeoBundleFetch does not add it to the 'runtimepath'.

yes I understand it does not add it to rtp. I think that indicates the bundle is available somewhere else and NeoBundle should not try to install it? From the help documentation, the example is NeoBundleFetch 'davidhalter/jedi', if I use NeoBundleFetch to register it, but cannot use it in the dependencies, then what is the use case for NeoBundleFetch?

I think that indicates the bundle is available somewhere else and NeoBundle should not try to install it?

If so, you should specify the path.

then what is the use case for NeoBundleFetch?

Most use case is to update neobundle by neobundle.


Update list of incompatible mods

We have to update the modinfo

There are new incompatible mods we (should) known
Some of the mods get new Ids when published on Steam Workshop

Furthermore, we should work on some kind of alert mechanism for when incompatible mods are loaded (in my experience, the game doesn't actually respect mods you mark as incompatible). I believe there is a somewhat convenient mechanism for querying which mods are attached to a save-game, so comparing that against a list of incompatible mods and hooking it up to a popup window shouldn't be too difficult


docker-machine config chokes when run against non-running machine

When the machine is running everything is cool:
$ docker-machine config dev
--tls --tlscacert=/Users/nathanleclaire/.docker/machines/.client/ca.pem --tlscert=/Users/nathanleclaire/.docker/machines/.client/cert.pem --tlskey=/Users/nathanleclaire/.docker/machines/.client/key.pem -H tcp://<IP_ADDRESS>:2376%

But with non-running machines, everything goes haywire:
$ docker-machine stop dev

$ docker-machine config dev
FATA[0000] Error getting machine url: host is not running

Yikes!  That shouldn't ever get thrown into a subshell.

What would we expect the behaviour to be? Nothing? Something to stderr?

Hmm that's a good question.  I guess nothing?  Technically this behavior is the same for any command that throws an error when you run as a subshell.
Personally I think that's the right error.  You are asking for a config of something that is not running.
@nathanleclaire thoughts?

What would we expect the behaviour to be? Nothing? Something to stderr?

It should be the same output as when the machine is running.  Now, this might be a little tricky, since in our current implementation a machine's IP address disappears when a machine is stopped due to the way that the store save mechanics work.  I'd argue that this shouldn't be the case; instead each machine should get a statically assigned IP address at create time which isn't freed up until the machine is destroyed.  That would make stuff like this possible.

Personally I think that's the right error. You are asking for a config of something that is not running.

It's the wrong error if we want users to know what's actually happening with the way the current workflow is set up.  Otherwise, docker just barfs because the user is passing invalid input to the CLI and leaves them with no idea what might have gone wrong (it will spit out help text and Error: Command not found: time="2015-02-02T11:00:16-08:00").
A machine doesn't need to be running for clients to attempt to connect to it.  A hanging docker version is something which is universally accepted as an idiom for "the daemon is not responding".  That's what should happen in this case.  "Oh, my docker version is hanging, so the daemon must not be running".
Curious what @bfirsh thinks as well.

If we want to leave the user without knowing there is an error and just rely on the Docker CLI to tell us, fine.  @bfirsh ?

My crazy idea: It should be the same output as when the machine is running. Now, this might be a little tricky, since in our current implementation a machine's IP address disappears when a machine is stopped due to the way that the store save mechanics work. Perhaps each machine could get a statically assigned IP address at create time which isn't freed up until the machine is destroyed. That would make stuff like this possible.

@nathanleclaire we can only assign local machines static IPs, for remote drivers that can't have static IPs or there is a charge, this would be difficult. Also, a stopped instance on some providers will have different IPs when they come back up.
I think leaving Docker CLI to tell us there's an error is fine.

@sthulb Right on, that might be more trouble than it's worth and I think I have a decent idea for a compromise.

Another idea for this issue: https://github.com/docker/machine/pull/482

Closing as #482 is merged.


Can't reuse id for multiple elements :(

Hi great work!!
I can't seem to use the same id for multiple elements on the same page. The first one shows up and the rest are the normal browser controlled tooltips

i am guessing you are looking for a javascript tooltip library and not what this repo is for. even still, its not typically common to use the same id for html elements.


Fixes #2118: force element is to be lowercase: mixing case causes c…

…onfusion and breaks style shimming for type extensions.

LGTM


GitHub Templates

Description
Added some templates for github Issues and Pull requests. This makes it so that when creating a PR or issue to the repository there are some pre-defined templates that users can follow. This also helps us to moderate the repository better as it ensures that people are reading the template and filling in information that we need to see.

Closing in favor of #16


pull request for e2e test at 11/17/2016 12:26:03

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Automatic serialisation & deserialisation of actions and state

You can do a surprising amount with introspection in Swift, these functions can encode a struct or class to and from a [String: Any]:
https://github.com/davidlawson/SwiftKVC/blob/master/SwiftKVCTests/SwiftKVCTests.swift#L60-L98
The only disadvantage is that you would need to keep an array of Action.Type around for the deserialisation process. Perhaps nicer than code generation though?
A Swift JSON library (e.g. SwiftyJSON – using NSJSONSerialization uses non-Swift objects) or equivalent could then be used to persist the data.
(This may also work well for serialising state as well as actions.)
Another similar library: https://github.com/sagesse-cn/swift-serialize
Limitations with this approach:
– deserialisation requires there to be an init method with no parameters (created by default if initial values are provided)
– serialisation does not support implicitly unwrapped optionals
– deserialiser requires array of action types to work
– seems to be fighting the language a bit

@davidlawson Thanks a lot for sharing. The approach is really clever, but as some of the limitations show also fairly fragile. I would also expect this to break fairly frequently, as Swift is updated.
I personally still feel code generation would be a better option but I'm very happy to have a discussion about it :smiley:

I agree! Another option I've looked into is https://github.com/evermeer/EVReflection. It works well with Swift but unfortunately it requires that the objects serialised/deserialised subclass EVObject which is a subclass of NSObject.

And another option :) https://github.com/tomlokhorst/swift-json-gen

Going the reflection route with Mirror might be a solution. Its 100% swift and part of the core libs.

(If we support this in the main lib, we would be using Codable nowadays. My suggestion for posterity: implement a ReplaceAppState action yourself and use whatever you like)


Not able to transliterate digraphs.

Hi @malexer
I can't seem to make this package work with digraphs. I've created two dictionaries, to convert from Croatian (Latin) to Serbian (Cyrillic) and vice versa, from Serbian to Croatian. In each of them there are three specific points involving digraphs:
# Croatian to Serbian
(LJ|Lj) -> Љ / lj -> љ
(NJ|Nj) -> Њ / nj -> њ
(DŽ|Dž) -> Џ / dž -> џ

# Serbian to Croatian
Љ -> Lj / љ -> lj
Њ -> Nj / њ -> nj
Џ -> Dž / џ -> dž

Now, converting from Serbian to Croatian works as expected (for instance, љ is always correctly substituted with lj). However, the opposite direction never works (lj will always get substituted with лј, which is wrong).
For reference, here are all my dictionaries' files:

Croatian to Serbian:

croat_serb.sublime_commands
croat_serb.dict

Serbian to Croatian:

serb_croat.sublime_commands
serb_croat.dict

Can you please help me find a solution?

Hi @tomicakorac
Originally I was targeting the single task: transliterate the Cyrillic text into latin.
The opposite direction was not implemented mainly because sometimes it is hard to do it by a simple substitution.
Considering your case, for "Croatian to Serbian" there are:
"j" -> "j"
"l" -> "л"
"lj" -> "љ"

If we see "lj" chars in a word which option should we choose: "љ" or "лj" ?
We need some more extended rules here, simple mapping is not enough unfortunately.
May be I am missing something?
There might be some additional rules I am not aware about as I don't speak Croatian and Serbian. i.e. some priority rules:

"lj" -> "љ" is always used first
"j" -> "j" and "l" -> "л" are applied then.

Do you have any such additional rules described somewhere?

Hi again and thank you very much for such a quick reply!
You're not missing anything actually, you were spot on!
In Croatian language, the combinations: lj, nj and dž will always mark one sound each. That's why they're digraphs, and not just any ordinary combination of two letters. Even more, in Croatian alphabet they exist as stand-alone letters, even though they're written using two letters: ...,i,j,k,l,lj,m,n,nj,o,.....
On the other hand, Serbian and Croatian are not two separate languages. They are essentially one and the same language with no differences whatsoever, except one: Croatian uses Latin script, whereas Serbian uses Cyrillic. Accordingly, for each letter in Croatian (Latin), there is a corresponding letter in Serbian (Cyrillic).
All this means that, when transliterating from Croatian to Serbian, each and every combination of lj, nj and dž will always be substituted with љ, њ and џ, respectively. As a result of this, you will never find in Serbian any of such combinations: лј, нј, дж. They do not exist.
Logically enough, the same is true in the opposite direction.
For upper case Croatian, forms Lj, Nj, Dž are preferred.
Finally, please note that Serbian (Cyrillic) language uses this letter: Јј, which is exactly same as Latin Jj, but it uses a separate Unicode point.
Please let me know if I can be of any more help.

I have added two-side transliteration.
Note: there are two separate mappings because:

Croatian -> Serbian: "đ" and "dj" both transliterated to "ђ"
Serbian -> Croatian: it seems that "ђ" is always transliterated as "đ"

Is it correct?

Oh, I'm very sorry for missing that one. Well you're almost right. When transliterating from Croatian to Serbian:

đ should always be transliterated as ђ;
dj should always be transliterated as дј;

Transliterating from Serbian to Croatian, the same rules apply, but obviously in the opposite directions: ђ > đ, дј > dj.
The confusion that both đ and dj can and should be transliterated as ђ is incorrect. This confusion originates from Slovene language, which does not have the letter đ, but instead writes dj for the same voice. However this is irrelevant for our problem, because Slovene language is quite different to Serbocroatian, and could not be meaningfully transliterated in the first place.
Thank you very much for your effort Alex!

Thanks for your explanation!
I have updated the mapping.
There is a unittest with pangram to verify that transliteration is working but you can also verify from your side as a native speaker as well.
Thanks!


[Feature]: Test runner (watch mode) should support toggling silent on/off

🚀 Feature Proposal
Working on SPAs I find myself using the "watch" test runner mode a lot.
Most of the time I don't want all the noise that comes from disabling silent mode, but occasionally I do (e.g. when working with react-test-library I want to see the output of screen.debug())
Proposing adding a new option to
Watch Usage
 › Press a to run all tests.
 › Press f to run only failed tests.
 › Press o to only run tests related to changed files.
 › Press p to filter by a filename regex pattern.
 › Press t to filter by a test name regex pattern.
 › Press q to quit watch mode.
 › Press Enter to trigger a test run.

e.g.
 › Press s to enable silent mode (silent mode is currently OFF)

Motivation
Avoid having to wait to restart & wait for recompilation
Example
No response
Pitch
Because switching silent mode on/off would benefit lots of developers

https://github.com/jest-community/jest-watch-toggle-config should work for this?

@SimenB I couldn't make it work with that plugin (I'm using Jest 27.5.1 if it matters). The plugin doc says

Boolean settings available for configuration through watch plugins, as of Jest 23.4.1, include bail, collectCoverage, noSCM, notify, onlyFailures, passWithNoTests and verbose.

So sounds like Jest isn't exposing silent as configurable.

(and if it doesn't cover it, a PR would bee great)

Are you suggesting a PR to add toggling support for that setting to Jest directly or a PR to expose the setting as toggleable only (so that the plugin can toggle it)?

Hey!
Did you get a chance to look into exposing the silent flag?


Jenkins with CentOS 7 and 8

Add Centos 7-specific Dockerfile. The latest version is now CentOS 8, but CentOS 7 is still supported.
It is the same dockerfile as centos with the "from" of CentOS 7.
I would like to have continuity in CentOS 7 --start-after 2,199
$ docker run --rm -ti jenkins/jenkins:2.198-centos cat /etc/centos-release
CentOS Linux release 7.7.1908 (Core)

$ docker run --rm -ti jenkins/jenkins:2.199-centos cat /etc/centos-release
CentOS Linux release 8.0.1905 (Core)

@slide, your merge into centos7 need modify the labels in Jenkinsfile.
Because exists in the commit exists the files Dockerfile-openj9 and Dockerfile-openj9-jdk11 and modify the Makefile, but the last need is the labels not?

I merged from master to take care of conflicts because the openj9 PR modified the same lines as this PR.

now why wait to merge?


feat: INT-2313 added the /mocha/vitest/recipe

Current dependencies on/for this PR:

main

PR #525   👈

This stack of pull requests is managed by Graphite.


'Automatic' main-wrapper margin may be applied incorrectly in some situations

For most services, the spacing for the main wrapper depends on whether there is an element in the 'beforeContent' block (such as breadcrumbs or a phase banner)
In #1371 we made a change to try and make it easier to get this spacing correct, by automatically applying a greater margin if the main-wrapper is the :first-child of its parent.
There are situations where this doesn't apply though which we may not have considered. For example, some admin or case-working systems may have additional navigation inside the main block, which they want to remain close to the header.
In the case of GOV.UK Pay, who tested a pre-release of 3.0 for us, they have an interface that looks like this:

When they first upgraded, the new :first-child rule made it look like this:

In order to defend against this, they had to add their own :first-child rule to their stylesheet:
.govuk-main-wrapper--with-phase-banner:first-child {
  padding-top: 5px;
}

We should consider reverting this 'automatic' behaviour or perhaps making it something that can be opted into or opted out of through the use of a modifier.
Alternatively, in this specific case the secondary navigation should not be inside the main-wrapper (and thus the main-wrapper would not be a :first-child and would not get the increased padding, which seems correct) – in which case maybe we just need to add better guidance around what should go inside the main-wrapper.

It does seem like a navigation bar like that should not be within the main element, what do you think @jonheslop?
I'd be OK with reverting this behaviour if we think it's going to cause grief for a lot of people.

We've spoken to @jonheslop and we're going to go with a modifier that adds this automatic behaviour, to ensure we don't make breaking changes.
We'll will want to document this new feature by changing the current guidance: https://github.com/alphagov/govuk-design-system/issues/887


UNC

Maybe I am not understanding properly but will this allow a user to browse a share using a unc path without entering credentials if they are logged into a domain  joined machine with credentials that have permissions?

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

ID: fba964be-3f77-d80c-f1a5-35bb1430bb8f
Version Independent ID: fe70b11e-10fe-5a8c-1fad-b22a83693503
Content: Enable Active Directory authentication over SMB for Azure Files
Content Source: articles/storage/files/storage-files-identity-auth-active-directory-enable.md
Service: storage
Sub-service: files
GitHub Login: @roygara
Microsoft Alias: rogarana

@erik5starg Thanks for your question. We are checking on this and will respond to you soon.

Also, what happens if we are using the email as the login attribute to Azure AD because our on-prem upn is not routable? Which account would they use when prompted for credentials?

@erik-jansen Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused.
Azure Files supports identity-based authentication and access control. You can choose one of two ways to use identity-based access control: Active Directory (AD) (preview) or Azure Active Directory Domain Services (Azure AD DS) (GA). AD supports authentication using AD domain joined machines, either on-premises or in Azure, to access Azure file shares over SMB.  For more details, see
https://docs.microsoft.com/en-us/azure/storage/files/storage-files-active-directory-overview
There is a video in this article it give some idea how we can use AD authentication supports on Azure files :https://azure.microsoft.com/en-in/blog/preview-of-active-directory-for-authentication-on-azure-file/

How does this behave when you are using mail as the login attribute because your upn is non routable?

On Apr 6, 2020, at 3:40 AM, SumanthMarigowda-MSFT<EMAIL_ADDRESS>wrote:

Closed #51391.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Frontend: when emitting loaded module trace file, also emit a JSON file tracking Objc method calls issued from the source code

@swift-ci please smoke test

Thank you for the comments, Ben! Will address via a follow-up PR. Regarding the exact content/details of this tracing file, we are still discussing with clients to settle the details.


Overriding 'in' and 'out' properties of edge breaks inV()/outV()

Hello,
Out of curiosity, I created an edge class with associated properties 'in' and 'out', both of Decimal type.
Although it is possible to create edges of this kind, and query them for given vertexes with outE()/inE(), it does not seem possible to query the vertexes associated with such an edge; inV() and outV() both result in:
java.lang.ClassCastException: java.math.BigDecimal cannot be cast to com.orientechnologies.orient.core.db.record.OIdentifiable [ONetworkProtocolHttpDb]
Should these be reserved names for edge properties? Or is there alternative state that inV() and outV() implementations should use?
Tested on 2.0.12

Same ClassCastException with attempts to delete edge for edges of this class.

Hi @TropicalPenguin
there is no specific check on this right now, but I strongly discourage to override "out" and "in".
There is not way, currently, to let outV() and inV() use another field name.
The proposed solution for this issue is to just add a control and throw an exception in case a use tries to define out and in properties on an edge class with different types, or just if he tries to store values that are not links on these properties

This is very low priority, overriding of out/in would break the graph model, so just don't do that. We need a check for that. Thanks for reporting.


Failed to update weights to vLLM

Anyone has any clue on this error?
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148] Error executing method start_worker_execution_loop. This might cause deadlock in distributed execution.
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148] Traceback (most recent call last):
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/vllm/worker/worker_base.py", line 140, in execute_method
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]     return executor(*args, **kwargs)
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]     return func(*args, **kwargs)
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/vllm/worker/worker.py", line 286, in start_worker_execution_loop
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]     while self._execute_model_non_driver():
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/vllm/worker/worker.py", line 295, in _execute_model_non_driver
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]     data = broadcast_tensor_dict(src=0)
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/vllm/distributed/communication_op.py", line 284, in broadcast_tensor_dict
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]     torch.distributed.broadcast_object_list(recv_metadata_list,
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/torch/distributed/c10d_logger.py", line 75, in wrapper
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]     return func(*args, **kwargs)
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/torch/distributed/distributed_c10d.py", line 2649, in broadcast_object_list
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]     broadcast(object_sizes_tensor, src=src, group=group)
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/torch/distributed/c10d_logger.py", line 75, in wrapper
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]     return func(*args, **kwargs)
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]   File "/opt/conda/envs/ptca/lib/python3.10/site-packages/torch/distributed/distributed_c10d.py", line 2144, in broadcast
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148]     work.wait()
(RayWorkerWrapper pid=4183, ip=<IP_ADDRESS>) ERROR 06-03 23:13:39 worker_base.py:148] RuntimeError: [../third_party/gloo/gloo/transport/tcp/unbound_buffer.cc:81] Timed out waiting 1800000ms for recv operation to complete

what is your vllm version?

vllm version is 0.4.3
nvidia-nccl-cu12==2.20.5

vllm version is 0.4.3 nvidia-nccl-cu12==2.20.5

vllm version is 0.4.3 nvidia-nccl-cu12==2.20.5

do you use our docker container (https://github.com/OpenLLMAI/OpenRLHF/tree/main/dockerfile) and NCCL between multiple nodes (such as IB)?


acquireLeadership to go to maintenance mode does not have a corresponding destroy

When ehcache is put to maintenance mode it does an acquireLeadership..but there is no corresponding call to abandonLeadership. This may cause the VoltronReadWriteLockEntity once the cluster tier manager for a given entity identifier is destroyed.
This may cause problems such as follows;
If a client disconnection is slow, another client may not be able to do a maintenance hold as the server may not release the lock until the disconnect event reaches the server

A second side effect of this bug is that even after a cache manager with a given identifier is destroyed, its corresponding VoltronReadWriteLockEntity will remain in the system, causing an entity leak in the platform (esp. if the same identifier is not reused for the same cache manager).


add generics for record services

type Pet = {
  name: string;
  type: 'dog' | 'cat' | 'bird';
};

type MyCollections = {
  pets: Pet;
};

const client = new Client<MyCollections>();

const pet = await client.collection("pets").getOne("123");
pet.type = 'bird';

// typeof pet is Pet

@anbraten I don't think this is needed since we already have support for generics:
interface Task {
  // type the collection fields you want to use...
  id:   string;
  name: string;
}

pb.collection('tasks').getList<Task>("RECORD_ID") // -> results in Promise<ListResult<Task>>
pb.collection('tasks').getOne<Task>("RECORD_ID")  // -> results in Promise<Task>

(this is documented in https://github.com/pocketbase/js-sdk#custom-record-types)

@ganigeorgiev I am using those generics from getList and getOne at the moment. This PR would enhance the typing as the key tasks of collection('tasks') would select the corresponding type and all nested functions like getList, subscribe would directly use it.

@anbraten I don't think this is a good idea since it will restrict the client usage to a single Collection. Please note that the SDK works with other services too, not just collections and it will be confusing to specify a single collection during instantiation - https://github.com/pocketbase/js-sdk#services


Release of v18.0.3

This release is scheduled for Tue  6 Feb 2024

Prerequisites for Release

[x] Notify the community on Slack.
[x] Make sure the release notes summary is prepared and clean.
Make sure backport Pull Requests are merged, list below.

[ ] #283

Make sure release blocker Issues are closed, list below.

Pre-Release

[x] Code Freeze.

https://github.com/frouioui/vitess/pull/290

[x] Create Release PR.

https://github.com/frouioui/vitess/pull/292

[x] Create new GitHub Milestone.

https://github.com/frouioui/vitess/milestone/6

Release

[x] Merge the Release PR.

https://github.com/frouioui/vitess/pull/292

[x] Tag the release.

https://github.com/frouioui/vitess/releases/tag/v18.0.3

[x] Update release notes on main.

https://github.com/frouioui/vitess/pull/293

[x] Go back to dev mode on the release branch.

https://github.com/frouioui/vitess/pull/294

[x] Update the website documentation.
[x] Make sure the release is benchmarked by arewefastyet.
[x] Docker Images available on DockerHub.
[x] Close current GitHub Milestone.

https://github.com/frouioui/vitess/milestone/5

Post-Release

[x] Notify the community on Slack for the new release.
[x] Twitter announcement.
[ ] Close this Issue.

Release completed.


Add Private dependency to Manifest

Fix SR-105. Added privateDependencies to thePackage Manifest.
The privateDependencies are fetched only when building this package manually with swift-build command.
 package = Package(
    privateDependencies: [
        .Package(url: "../PrivateLib", majorVersion: 1)
    ])

swift-build will fetch and build PrivateLib
The privateDependencies are not fetched recursively. If you specify a package as a dependency that has privateDependencies, this privateDependencies wont be fetched.
let package = Package(
    dependencies: [
        .Package(url: "../Foo", majorVersion: 1)
    ])

// Foo Manifest.swift
let  package = Package(
    name: "Foo"
    privateDependencies: [
        .Package(url: "../PrivateLib", majorVersion: 1)
    ])

swift-build will fetch and build Foo  but I wont fetch PrivateLib

Can you rebase your changes instead of having a merge commit as part of the PR?
Can we get an update to the documentation to describe this feature? At some point we are going to need some kind of "Package.swift" reference guide which is an exhaustive list of all of the things we support.
One worry, and I'm ok with merging w/o having a clear plan here: how do we ensure that a package is correct and it builds without its private dependencies? As currently scoped it seems like this feature can only be used by test targets, and it assumes we never build test targets of dependencies.

Good point, I though a bit about that too. Maybe in future it would be better to link the privateDependencies against some private target and not the mainApp target. This way when person would try to import and use private things in the public main target it will not build.
:+1: I will fix rebasing and documentation.

In the long run, I think it might be better to break out a "test" area of Package.swift (relates to @mxcl's proposal for testing support in SwiftPM) which would provide a unified way to add both test dependencies and allow adding other attributes and options in the distant future. This will be more forward thinking and offer more extensibility in the future.
For example, the approach that we was going to use in CocoaPods [1] was to have an entire specification that defines testing:
Pod::Spec.new do |spec|
  spec.name = 'URITemplate'

  spec.test_spec do |test_spec|
    test_spec.source_files = 'URITemplateTests.swift'
    test_spec.dependency 'Quick'
  end
end

Where the "test specification" has a lot of properties similar to the root specification itself.
I can see in the future, there may be need for other attributes such as source files and source file excludes similar to that available for the root package itself in SPM.
let package = Package(
  name: "Example",
  test: TestTarget(
    dependencies: [
      ...
    ],
    exclude: ["Tests/X.swift"]
  )
)

As another example, in the future there may be the ability to explicitly depend on an Apple framework in Package.swift. This is mentioned within the documentation for Package.swift. I could see that a user may want to be able to depend on specific Apple modules just within the tests:

We will add explicit support for system dependencies in the future.

let package = Package(
  name: "Example",
  test: TestTarget(
    systemDependencies: ["CoreData"]
  )
)

I personally don't like the name privateDependencies. I like the approach of npm, where the same feature is called devDependencies.
This leaves the private word available for packages that are actually private as opposed to public, such as proprietary code hosted as a private github repo or behind similar login walls.

+1 on devDependencies vs privateDependencies.
@kylef I agree with your general points about carving out a special area for tests (and imagine we will want a TestTarget like thing as part of the testing proposal). I don't quite see how that conflicts with this proposal though.
This feature only added things to the package dependencies area -- it didn't address the existing issue that Target's can't refer to which part of the package dependencies they actually depend on (which is something we will need to solve). Once we had done that, all targets would presumably be able to refer to the private dependencies, or not.
Based on the discussion here, though, it starts to sound like this should be discussed with a proposal before we start picking up an implementation... given that this feature currently is really limited to being useful with tests, I think we should lump some of that discussion into the testing proposal discussion.
Thoughts?

Agree on renaming. I've fixed that and added documentation as well.
I still see the situation when devDependency would be valuable.
Example: sourceCode generators like Natalie, debugging and diagnostic tools and etc.
The testing dependencies are a bit similar to devDependency with some extra functionality (should the tests be ran when fetching package and etc.) But I don't see why this PR would conflict with further development of "Swift Testing" proposal

I don't find the current proposal suggestive that the dependencies are only for tests.
However I also think it would be tedious to force deps for tests to be specified inside test-targets, it seems likely to me you would want a test dependency for more than one test target, maybe all of them and then having to specify the dependency 3 times is tedious. Certainly we should support per-target dependencies because sometimes you need that or at least sometimes you want to be certain that some dependency isn't getting built into your tests with the associated possible global state modifications that may occur.
So, at least for now something like devDependencies seems good to me, but I'd prefer a name that indicates more clearly that these dependencies are only for tests.

Any suggestions what should be changed/fixed and what is the next steps?

It is foreseeable that dependencies would provide binaries that we could execute as part of the build, however we really want to avoid that, to avoid the hell that is current build-systems like autoconf/cmake.
So for now a name that indicates strictly test deps is preferable.
testDependencies is a little ugly, but I'd be happy with that.

I've renamed to the testDependencies

Thanks, I'll check out and review.

I've removed that. Now we jest fetch and build the testDependencies


Build issue google-vr-*

Hello,
I can not build the framework since the last update, it seems that something with google-vr went wrong.
Would be really great if you could fix that problem or let me know if it's a local problem.
Thank you...
The log:
`Error:A problem occurred configuring project ':framework'.

Could not resolve all dependencies for configuration ':framework:_debugCompile'.
Could not find :google-vr-base:.
Searched in the following locations:
file:/C:/tools/devTools/Android/studio/gradle/m2repository//google-vr-base//google-vr-base-.pom
file:/C:/tools/devTools/Android/studio/gradle/m2repository//google-vr-base//google-vr-base-.aar
https://jcenter.bintray.com//google-vr-base//google-vr-base-.pom
https://jcenter.bintray.com//google-vr-base//google-vr-base-.aar
file:/C:/Users/user/AppData/Local/Android/Sdk/extras/google/m2repository//google-vr-base//google-vr-base-.pom
file:/C:/Users/user/AppData/Local/Android/Sdk/extras/google/m2repository//google-vr-base//google-vr-base-.aar
Required by:
trunk:framework:unspecified
Could not find :google-vr-common:.
Searched in the following locations:
file:/C:/tools/devTools/Android/studio/gradle/m2repository//google-vr-common//google-vr-common-.pom
file:/C:/tools/devTools/Android/studio/gradle/m2repository//google-vr-common//google-vr-common-.aar
https://jcenter.bintray.com//google-vr-common//google-vr-common-.pom
https://jcenter.bintray.com//google-vr-common//google-vr-common-.aar
file:/C:/Users/user/AppData/Local/Android/Sdk/extras/google/m2repository//google-vr-common//google-vr-common-.pom
file:/C:/Users/user/AppData/Local/Android/Sdk/extras/google/m2repository//google-vr-common//google-vr-common-.aar
Required by:
trunk:framework:unspecified`

Hi,
Could you please let us know what files do you have under your GVRf/Framework/framework/src/main/libs folder? Please ensure you have the very latest versions of the gradle files.

Hi,
I have the following files in the libs folder
drwxrwxr-x+ 1 user Kein        0  8. Aug 13:21 armeabi-v7a
-rw-rw-r--+ 1 user Kein   604140  6. Aug 16:23 google-vr-base.aar
-rw-rw-r--+ 1 user Kein   341690  6. Aug 16:23 google-vr-common.aar
-rw-rw-r--+ 1 user Kein   190432 12. Mai 09:45 gson-2.2.4.jar
-rw-rw-r--+ 1 user Kein   175292 12. Mai 09:45 jline-android.jar
-rw-rw-r--+ 1 user Kein   126805 12. Mai 09:45 jnlua-android.jar
-rw-rw-r--+ 1 user Kein   729759 19. Mai 13:44 js.jar
-rw-rw-r--+ 1 user Kein    42131 12. Mai 09:45 jsr223.jar
-rwxrwxr-x+ 1 user Kein 10894256 12. Mai 09:45 libassimp.so
-rwxrwxr-x+ 1 user Kein   133064 12. Mai 09:45 libjnlua.so
-rwxrwxr-x+ 1 user Kein     6351 16. Jun 18:46 SystemUtils.jar
-rwxrwxr-x+ 1 user Kein     4107 16. Jun 18:46 VrApi.jar
-rwxrwxr-x+ 1 user Kein    17918 16. Jun 18:46 VrAppFramework.jar

Ok, looks like you've got the files. The build is fine as far as I know. Are you building just the framework project or a project where you have your app and the framework is included as a module? If it is the latter could you try adding the flatDir section to your project's build.gradle file:
allprojects {
    repositories {
        jcenter()
        flatDir {
            dirs 'src/main/libs'
        }
    }
}

Does the latest build (from 3 days ago) still support Eclipse?
I had to download it to get the changes for eyepicking but it now also won't build properly:
**** Build of configuration Default for project Framework ****

G:\Dev\AndroidNDK\ndk-build.cmd -j16 OVR_DEBUG=0 NDK_DEBUG=0
Android NDK: There is no Android.mk under ./jni
Android NDK: If this is intentional  please define APP_BUILD_SCRIPT to point
G:/Dev/AndroidNDK/build/core/add-application.mk:214: *** Android NDK: Aborting...    .  Stop.
Android NDK: to a valid NDK build script.

**** Build Finished ****

I didn't change anything since the last version (June 23rd) and I did copy the 3 jar files into the "lib" folder again.

I will look into fixing the Eclipse build temporarily but eventually Eclipse will not be supported.
You can copy the ./GVRf/Framework/backend_oculus/src/main/jni/Android.mk file to ./GVRf/Framework/framework/src/main/jni/Android.mk and try again.

@liaxim Thanks but unforunately it didn't work:
http://pastebin.com/8QUuLDat
I remember getting similar errors before a few months ago when I first tried to get it to run. I didn't manage to make it work back then but a new version a few days later fixed it.
I already tried importing my project into Android Studio but got really annoyed with all the errors nobody knows anything about that I gave up after an hour. So I'm really thankful for every version that still works with Eclipse!

The Android Studio builds works pretty well. I do recommend you start using it instead. I can help with any issues you may encounter.
Back to the Eclipse build: it is pretty complicated to get it to work since we have a dependency to Google VR now and Google VR uses .aar files. Google doesn't produce libraries Eclipse can use. So we can't build with Eclipse anymore.
If you do insist on using Eclipse I can give you instructions how to manually configure Eclipse but you will also have to comment out the fallback to Google VR. Which means your framework build would break on phones without Oculus.
--
I can't promise anything but we can explore applying selectively some changes to the 3.0.1 release.

I already opened a new thread on StackExchange, so hopefully someone can help me with importing my project in Android Studio there.
The GVRf version I've been using for almost the last two months has been working fine so far. I only downloaded the new version to get the new samples for eyepicking (eyepicking, pickandmove) to work like it's recommended in the developer guide.
I'll try the old way first and open a new issue if it shouldn't work.
Is it possible to download the last version that is still fully compatible with Eclipse (including the samples)?

Thank you again @liaxim  - you hint with including the allprojects code worked.
Sorry, for the inconvenience - it was a mistake in my gradle configuration.
The issue can me closed if @Nathipha's issue is solved, too...

@Nathipha https://github.com/Samsung/GearVRf/releases/tag/v3.0.1 is the last release with official Eclipse support. You can either download it from that link or execute "git checkout v3.0.1" in your framework repo directory.
I created a 3.0.1 release for the samples. You can either download it or execute "git checkout v3.0.1" in your demos repo directory.
Bear in mind that these releases are from the start of June.

@liaxim Thank you.
@QKnows Yes, sorry, you can close it.


Proposed changes to cellular anatomical entity from COB meeting

id: GO:0110165
name: cellular anatomical entity
namespace: cellular_component
def: "A part of a cellular organism that is either an immaterial entity or a material entity with granularity above the level of a protein complex but below that of an anatomical system. Or, a substance produced by a cellular organism with granularity above the level of a protein complex." [GOC:kmv]
subset: gocheck_do_not_annotate
subset: goslim_pir
is_a: GO:0005575 ! cellular_component

Can we remove the "either an immaterial entity or a material entity", everything in GO is material.
I suggest also explicitly ruling out virion components here as well
We also had discussion about the label, some found it to be a little abstract, but alternatives like "subcellular structure" don't sufficiently rule out complexes and virion components.

How about "cellular anatomical structure"?

I think the original label was to align with CARO.


Number of rows for different dates

When fitting a bayesian model, I got this error:

In metab_fun(specs = specs, data = data, data_daily = data_daily,  :
Modeling failed: dates have differing numbers of rows; observations cannot be combined in matrix

I see in the code that you are looking at a table of the day length data. My UTC datetimes are all equally spaced, and there are 96 obs per day (except for the first and last days in the data set, easy to trim off). I use:
convert_UTC_to_solartime(date.time=dd$DateTime_UTC, longitude=md$lon[1], time.type="apparent solar")
to get the solar.time. Most dates get 96 intervals, but 2 get 95 and two get 97, which I assume is an artifact of the calculation and this particular location. For now I am dropping those days.
I can think of two possibilities:

let metab run but automatically drop the dates with less than the mode of observations per day (with a warning that those dates were dropped because of incorrect dimensions)
modify convert_UTC_to_solartime to recognize when this happens (I think in most cases it would only cause the nobs per day to go up or down by one) and do something (like, would metab accept something like "2016-12-21 24:00:06" instead of "2016-12-22 00:00:06"?)

Let me know if you want me to try to implement a solution.

Thanks for submitting this as a GitHub issue, Aaron.
For more abrupt differences in resolution, e.g., from hourly measurements to 15-minute measurements, I've recently added the required_timestep argument to specs. If you set this to a non-NA value, this will discard days that don't have the numeric timestep you specified, automating the process you described above.
But for your current case (and in general), you should use "mean solar" instead of "apparent solar" for inputs to metab() - that will get you exactly even intervals and exactly 96 obs per day. The "apparent solar" option should be reserved for calculating light.

Very good, that makes perfect sense. Thank you!


fix count errors

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


[BUG] - Toggle Button Icon is not at the button center

Describe the bug
When using the <ngx-mat-timepicker-field> the toggle icon is not at the center of the toggle button.
In the Image you can roughly see that the icon is not centered. the top of the icon touches the green line.
To Reproduce
simply using:
<ngx-mat-timepicker-field [defaultTime]="'11:11 AM'"></ngx-mat-timepicker-field>
or stackblitz
Expected behavior
The green line should intersect the icon in the middle. If that is the case the icon is centered!
Screenshots

Desktop (if execution):

OS: Linux Mint
Browser: Chrome

** Versions

ngx-mat-timepicker version [ ^13.0.0]
"material-design-icons": "^3.0.1",
@angular/core version ^13.2.2
@angular/material version [^13.2.2]
typescript version [^4.5.5]

As you can see in the demo the button is centered.
So it's a problem with your style.

I don't know mate, I don't know what you used, I should inspect your site...the blitz isn't working also...


Fix colors problem

#19 @jorgerojas26  check this solution for the colors problem

Yeah, i thought about solving this the same way, but then i found a better way. I'll close this PR without merging it because i think i found a much better solution for this.


Can't access the documentation

Documentation at https://twurple.github.io/ is not accessible.

The root URL is now accessible, and its canonical URL is https://twurple.js.org (but the "old" URL still redirects).


Outlook adding padding to right side of images

So somehow, Outlook 2013, 2016 and 2019 are adding about 20 px of space to the right of center aligned images.
Reproduction Steps:

Creation section with smaller than full width image and align center
Test in litmus for the above versions

Expected behavior:
Images to be aligned in the center
Observed behavior:
Images off center by about 20 px
Screenshots and GIFs
https://imgur.com/a/xV4eJ4x
MJML version:
4.0.3
Email clients the bug is seen on:
Outlook 2013, 2016 and 2019
MJML Section Code
      	<mj-column>
        	<mj-image src="http://cenergy.stellarblast.com/brookwood/09-006-214/workshopText.png" padding-top="0" padding-bottom="30px"></mj-image>
          <mj-image src="http://cenergy.stellarblast.com/brookwood/09-006-214/brookwoodVideo.png" padding="0" href="http://brookwoodfarms.com/workshop/index.html#workshop"></mj-image>
          <mj-image src="http://cenergy.stellarblast.com/brookwood/09-006-214/invited.png" width="243px" padding-top="50px;"></mj-image>
          <mj-text padding="10px 70px" css-class="mobile-padding">
          	Join us September 26-27th, in Lawrenceville, GA for a free, one-on-one workshop. We’ll review your menu, share new, craveable dishes that are packed with profit, and give you information to craft a menu your customers will love.

This session can help you grow your sales by incorporating barbeque in new, exciting ways. Don’t miss this free opportunity to grow your business. Reserve your time NOW!
          </mj-text>
          <mj-image href="http://brookwoodfarms.com/workshop/rsvp.html" src="http://cenergy.stellarblast.com/brookwood/09-006-214/rsvpNow.png" align="center" padding-bottom="20px" width="104px"></mj-image>
        </mj-column>
      </mj-section>```

This is a known bug when you have a background image in your section. Padding is applied twice inside a VML section, resetting it to 0 should fix it

On 27 Aug 2018, at 23:10, Hookeo<EMAIL_ADDRESS>wrote:
So somehow, Outlook 2013, 2016 and 2019 are adding about 20 px of space to the right of center aligned images.
Reproduction Steps:
Creation section with smaller than full width image and align center
Test in litmus for the above versions
Expected behavior:
Images to be aligned in the center
Observed behavior:
Images off center by about 20 px
Screenshots and GIFs
https://imgur.com/a/xV4eJ4x
MJML version:
4.0.3
Email clients the bug is seen on:
Outlook 2013, 2016 and 2019
MJML Section Code
  	<mj-column>
    	<mj-image src="http://cenergy.stellarblast.com/brookwood/09-006-214/workshopText.png" padding-top="0" padding-bottom="30px"></mj-image>
      <mj-image src="http://cenergy.stellarblast.com/brookwood/09-006-214/brookwoodVideo.png" padding="0" href="http://brookwoodfarms.com/workshop/index.html#workshop"></mj-image>
      <mj-image src="http://cenergy.stellarblast.com/brookwood/09-006-214/invited.png" width="243px" padding-top="50px;"></mj-image>
      <mj-text padding="10px 70px" css-class="mobile-padding">
      	Join us September 26-27th, in Lawrenceville, GA for a free, one-on-one workshop. We’ll review your menu, share new, craveable dishes that are packed with profit, and give you information to craft a menu your customers will love.

This session can help you grow your sales by incorporating barbeque in new, exciting ways. Don’t miss this free opportunity to grow your business. Reserve your time NOW!

```
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@iRyusa Thanks for that.  What padding should I set to 0?

Every padding left & right inside your section (column/text/image) should be set to 0, this is a known issue with vml but we didn't find any fix for this particular case

Cool.  Thank you for the help!


Investigate PSA - Private Service Access - specified CIDR range over defaults - for values.yaml reporting

Uday q: Getting the PSA connect address range (specified over default)
I am working out several canaries SaaS/FaaS/IaaS - and need a PSA for the connection between the bastion and a cloud SQL instance - used the default but will switch to specifying and add the kcc yaml around this in https://github.com/cloud-quickstart/wiki/blob/main/solutions.md#vpc

merge with
#178


[Docs]: README on Kurtosis Repo has WARN-level logs in output

Where did you see an issue in our documentation?
No response
Description of the issue
Output README on main repo was run by someone on an outdated version of Kurtosis, so it has WARN level logs.
WARN[2023-02-10T13:32:32-03:00] You can manually upgrade the CLI tool following these instructions: https://docs.kurtosis.com/install#upgrading```

Closing now that #112 is merged.


System requirements for pandas.load_parquet

system crashes when i load pandas.load_parquet(bertffn_crossentropy.zip)
Can you tell system specifications of the system to load this file ?
I'm running this in my laptop

Can you make a colab notebook which reproduces there error? It could be that you are feeding a zip file instead of uncompressing it.

Can you tell me the file format of bertffn_crossentropy, When extracted ?
Is it Parquet File ?
I can't uncompress it to see what's in it. Archive zip file is damaged can you provide proper one.


Save Password-Button

The Wallet has to be unlocked at every startup under Windows 10.
In Linux it is not like this (?)
Please add a "remember Password" to enhance the comfortability of this program

This is intentional behavior.  "Remembering" your passwords means writing it to disk in plaintext, which would allow malware or bad actors to trivially steal your wallet.

Is it possible that the behavior seems different on Linux because siad is not being closed when the GUI is exiting?

Yes, that is precisely why.  This was fixed in https://github.com/NebulousLabs/Sia-UI/pull/386, but did not make the 1.0.2 release

This does bring up a good point, do we want siad to quit when Sia-UI closes? I see quite a few advantages if it does not:

Users don't have to retype their passwords as often.
They don't have to remember to relaunch Sia-UI every 3 months or so to renew contacts, their computer just needs to be on.
Until we figure out the issue causing file corruption, limiting the quit/launch cycle could reduce the likelihood of the issue.
Users won't have to wait for the block chain download every time they open Sia-UI.
Hosts don't need to keep the UI open (which could be annoying).

For experienced users these things won't matter, but they could be the key factor in whether a new member sticks with the platform or not.
Also as for the issue of storing passwords on disk... right now given how long the passwords are I'd wager that 90%+ of users just copy the seed to a text file. We really aren't giving users any security advantage in that case, just shifting the blame.

The decision we came to regarding siad and Sia-UI lifecycle coupling was to bind siad's lifetime to the lifetime of the UI (assuming Sia-UI started siad, which is the case in the vast majority of users), because users wouldn't have an easy way to quit Sia otherwise.  That, however, doesn't mean that the UI has to quit when it closes.  The behavior as it stands is to keep running in the tray and provide a tray menu to manage the lifecycle of siad.  All of the advantages of keeping siad running apply, except users also have the ability to immediately show the UI or quit Sia from their system tray.
While most users are probably simply using a text file, we should try to do everything we can to encourage correct security practices.  Implementing plaintext password storage into the app, even if optional, would be engineering insecurity into the platform.
@DavidVorick thoughts?

Well I just think it should be there - even my online banking software saves the password for good reason.
What if there is really an attacker on my computer. If I enter my Password every time he can simply watch my keyboard (a keylogger is written with getasynckeystate in 10 minutes).
Also I think that almost all users use textfiles to store their password as you also mentioned, If I understood you right.
I am looking forward to a maybe weak encrypted but usable and as save as it is now - password-saving mechanism, what do you think?

@ma68546 it's far, far more likely that the attacker gets a chance to scan your computer for password files than it is that they get a chance to install a keylogger onto your system. Furthermore, a keylogger requires analyzing the output and figuring out which blobs of text are passwords.
A keyfile on the other hand, if we implemented one, would be programatically saved to disk. Most likely, we'd use a single file that always had the password in the same place, regardless of what machine you are on. That's really easy to scan automatically, and now an attack only needs to compromise your userspace filesystem instead of needing to compromise the admin account on your machine (keyloggers need admin access before they can be installed).
If a user is using their own text file to save their passwords, at least that text file is going to have a semi-random name and reside on a semi-random location on-disk.
I'm not sure how the UI handles remembering the password, but even if it is sitting in plaintext in memory, you still have to read application memory and know the layout of the Sia program in order to find it. Some operating systems will deliberately randomize the locations of objects in memory to make this harder (though I'm pretty sure if your OS was doing this you'd be aware of it - OpenBSD, FreeBSD, and hardened linux all have the ability to do this, but most people don't run any of those). More importantly though, you need admin access to a machine to read the memory of another program that's running.
The AES idea is basically just wrapping a stronger password with a weaker password, which doesn't really fit the spirit of protecting the user's funds. If the user doesn't want to remember the password themselves, they should really be using a secure password manager like KeePass. KeePass can remember your password, store it securely, and then has a master password that you use to protect everything.
@johnathanhowell I think it makes perfect sense to encourage sane password behavior in our users. We should not compromise on the fact that we don't save the password for the user, and we should not compromise on the password strength (well... if we can figure out a way to compress it to 16 bytes instead of 32, that'd be fine. And actually, I know just how to do that, while preserving compatibility. Heh. Use a 16 byte seed that you hash to get the 32 byte seed that the wallet expects. Problem solved.).
I think telling people to use a password manager to manage the somewhat-ungainly Sia password is the best option. It throws security to a system that's designed to do security well.

@DavidVorick I really agree with you, that it is a super important task, to save the users data and his money aswell.

How did your first testusers react when you told them that they have to remember a 32 Byte password?

How about Programming a password Manager where the user can choose his own password let's say minimum 8 chars? I did this before, it is quite simple. Then you have a encrypted password and the attacker has to sniff your keyboard to get it. He will have root-access always if he is on your system already. Under Windwos he needs root access to search for a Password-Plaintext.txt file anyway.

You may agree, that our biggest goal is, to get all the normal users to use Sia.
How about copying the success of other products? How about making sia as comfortable as the Mist wallet of ethereum? or like the Boxcryptor for Dropbox?

Let's Make this software work for the dummy User! for the Dropbox User!
Let's make Sia Big!
What do you say?

Hey @ma68546, thanks for your feedback!
To build off of what @DavidVorick and @johnathanhowell have said, it's also important to note that the password is the same as the wallet's seed in the UI. It is important to write down this seed somewhere safe so that your wallet is recoverable should you lose access to your machine. It is tempting to let users choose their own password, but decoupling the password and seed doesn't encourage the user to write down the seed. In fact we've already seen a large number of users click through the wallet creation steps without ever writing down the seed. I'm worried that adding a "remember password" button would only increase the number of users that click through without writing it down.
I do agree it is not convenient. There is a usability / security tradeoff and it is often difficult to find the right balance. I think Sia often leans towards security, but we'll continue trying to find the right balance.

Decentralized systems operate in much more hostile environments than centralized systems like Dropbox. They are also more secure. But, if you forget your password, there's no reset button.
I am cautious to allow users to easily engage in activities that put them at high risk. Most users don't even realize that they are close to losing everything. We had dozens of miners exposing their wallet keys over the open Internet  and it's hard to blame the victim.
It is okay if you want to make an alternate ui or wallet plugin. But I feel everything that comes out of Sia officially should weigh heavily on the side of security, because at our core that's what we are about.

Dear @DavidVorick and @VoidingWarranties ,
thank you for the detailled Information and your patience, I really know about that issues and totally agree with you, that Sia must be safe.
I think you also agree with me, that the seed must be save. Storing the seed in plaintext seems to be unsave, right?
Have you tried the solution that Ethereum uses with the mist wallet?
They encrypt the private keys with a master password.
So they are using a password manager.
Here the solutions:
C#: http://www.codeproject.com/Articles/15750/Simple-Password-Manager-Using-System-Security  (about 80 LOC)
C++:
https://github.com/michalmuskala/pass_manager
should not be this a good solution to our problem?
also user defined pws are much more safe. Users can use upper and lower case, numbers and special characters!
How about that system to at least ease the access ?

also user defined pws are much more safe. Users can use upper and lower case, numbers and special characters!

The passwords generated by Sia are cryptographically as strong as you can get. The primary reason that we do the password generation for the user is because users have a strong track record of generating insecure passwords.
The passwords generated by Sia have 256 bits of entropy. A secure password only needs 128 bits, and the fact that we use 256 is actually a bug. Adding more numbers, special characters, length, etc. would certainly add more entropy, but the extra entropy is completely unnecessary. A 1024 bit password is equally strong to a 128 bit password - they are each essentially unbreakable.

closing this for now, though acknowledging that there's a lot of user pressure for a user-settable password.


Remove cache bust from preview links

https://trello.com/c/THjwpcKs/695-remove-cache-busting-in-frontend-and-publisher

Looks good, just needs a rebase

Looks good, just needs a rebase

Done :)

Needs another rebase. Otherwise MWA 👍

Needs another rebase. Otherwise MWA :+1:

I think I accidentally turned that on in the GitHub branch permissions. I've turned it off now.