Version 2.3.3 is broken

### Issue type
[x] Bug report
### Environment
(netbox-venv) ***:/opt/netbox-2.3.3$ python --version
Python 3.5.2
(netbox-venv) ***:/opt/netbox-2.3.3$ pip --version
pip 10.0.1 from /opt/netbox-venv/lib/python3.5/site-packages/pip (python 3.5)
Following pip install -r requirements.txt package list:
asn1crypto==0.24.0
bcrypt==3.1.4
certifi==2018.4.16
cffi==1.11.5
chardet==3.0.4
click==6.7
coreapi==2.3.3
coreschema==0.0.4
cryptography==2.2.2
Django==1.11.13
django-cors-headers==2.2.0
django-debug-toolbar==1.9.1
django-filter==1.1.0
django-js-asset==1.1.0
django-mptt==0.9.0
django-tables2==1.21.2
django-timezone-field==2.1
djangorestframework==3.8.2
drf-yasg==1.7.4
flex==6.13.2
future==0.16.0
graphviz==0.8.3
idna==2.6
inflection==0.3.1
itypes==1.1.0
Jinja2==2.10
jsonpointer==1.14
jsonschema==2.6.0
lxml==4.2.1
Markdown==2.6.11
MarkupSafe==1.0
natsort==5.3.2
ncclient==0.5.3
netaddr==0.7.18
openapi-codec==1.3.2
paramiko==2.4.1
Pillow==5.1.0
psycopg2-binary==2.7.4
py-gfm==0.1.3
pyasn1==0.4.3
pycparser==2.18
pycryptodome==3.6.1
PyNaCl==1.2.1
pytz==2018.4
PyYAML==3.12
requests==2.18.4
rfc3987==1.3.7
ruamel.yaml==0.15.37
six==1.11.0
sqlparse==0.2.4
strict-rfc3339==0.7
swagger-spec-validator==2.1.0
uritemplate==3.0.0
urllib3==1.22
validate-email==1.3
xmltodict==0.11.0
Gunicorn setup
gunicorn (version 19.8.1)
gunicorn_config.py
command = '/usr/bin/gunicorn'
pythonpath = '/opt/netbox-2.3.3/netbox'
bind = '<IP_ADDRESS>:8001'
workers = 3
user = 'www-data'
Trying to run:
(netbox-venv) ***:~$ sudo gunicorn -c /opt/netbox-2.3.3/netbox/gunicorn_config.py netbox.wsgi
Results in:
[2018-05-30 09:47:19 +0000] [7104] [INFO] Starting gunicorn 19.8.1
[2018-05-30 09:47:19 +0000] [7104] [INFO] Listening at: http://<IP_ADDRESS>:8001 (7104)
[2018-05-30 09:47:19 +0000] [7104] [INFO] Using worker: sync
[2018-05-30 09:47:19 +0000] [7107] [INFO] Booting worker with pid: 7107
[2018-05-30 09:47:19 +0000] [7108] [INFO] Booting worker with pid: 7108
[2018-05-30 09:47:19 +0000] [7111] [INFO] Booting worker with pid: 7111
[2018-05-30 09:47:20 +0000] [7111] [ERROR] Exception in worker process
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/gunicorn/arbiter.py", line 583, in spawn_worker
worker.init_process()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/workers/base.py", line 129, in init_process
self.load_wsgi()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/workers/base.py", line 138, in load_wsgi
self.wsgi = self.app.wsgi()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/app/base.py", line 67, in wsgi
self.callable = self.load()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/app/wsgiapp.py", line 52, in load
return self.load_wsgiapp()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/app/wsgiapp.py", line 41, in load_wsgiapp
return util.import_app(self.app_uri)
File "/usr/local/lib/python3.5/dist-packages/gunicorn/util.py", line 350, in import_app
import(module)
File "/opt/netbox-2.3.3/netbox/netbox/wsgi.py", line 8, in
application = get_wsgi_application()
File "/usr/local/lib/python3.5/dist-packages/django/core/wsgi.py", line 13, in get_wsgi_application
django.setup(set_prefix=False)
File "/usr/local/lib/python3.5/dist-packages/django/init.py", line 27, in setup
apps.populate(settings.INSTALLED_APPS)
File "/usr/local/lib/python3.5/dist-packages/django/apps/registry.py", line 108, in populate
app_config.import_models()
File "/usr/local/lib/python3.5/dist-packages/django/apps/config.py", line 202, in import_models
self.models_module = import_module(models_module_name)
File "/usr/lib/python3.5/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "/opt/netbox-2.3.3/netbox/dcim/models.py", line 21, in
from extras.rpc import RPC_CLIENTS
File "/opt/netbox-2.3.3/netbox/extras/rpc.py", line 6, in
import paramiko
File "/usr/local/lib/python3.5/dist-packages/paramiko/init.py", line 22, in
from paramiko.transport import SecurityOptions, Transport
File "/usr/local/lib/python3.5/dist-packages/paramiko/transport.py", line 57, in
from paramiko.ed25519key import Ed25519Key
File "/usr/local/lib/python3.5/dist-packages/paramiko/ed25519key.py", line 22, in
import nacl.signing
File "/usr/local/lib/python3.5/dist-packages/nacl/signing.py", line 19, in
import nacl.bindings
File "/usr/local/lib/python3.5/dist-packages/nacl/bindings/init.py", line 17, in
from nacl.bindings.crypto_box import (
File "/usr/local/lib/python3.5/dist-packages/nacl/bindings/crypto_box.py", line 27, in
crypto_box_SEEDBYTES = lib.crypto_box_seedbytes()
AttributeError: cffi library '_sodium' has no function, constant or global variable named 'crypto_box_seedbytes'
[2018-05-30 09:47:20 +0000] [7111] [INFO] Worker exiting (pid: 7111)
[2018-05-30 09:47:20 +0000] [7107] [ERROR] Exception in worker process
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/gunicorn/arbiter.py", line 583, in spawn_worker
worker.init_process()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/workers/base.py", line 129, in init_process
self.load_wsgi()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/workers/base.py", line 138, in load_wsgi
self.wsgi = self.app.wsgi()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/app/base.py", line 67, in wsgi
self.callable = self.load()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/app/wsgiapp.py", line 52, in load
return self.load_wsgiapp()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/app/wsgiapp.py", line 41, in load_wsgiapp
return util.import_app(self.app_uri)
File "/usr/local/lib/python3.5/dist-packages/gunicorn/util.py", line 350, in import_app
import(module)
File "/opt/netbox-2.3.3/netbox/netbox/wsgi.py", line 8, in
application = get_wsgi_application()
File "/usr/local/lib/python3.5/dist-packages/django/core/wsgi.py", line 13, in get_wsgi_application
django.setup(set_prefix=False)
File "/usr/local/lib/python3.5/dist-packages/django/init.py", line 27, in setup
apps.populate(settings.INSTALLED_APPS)
File "/usr/local/lib/python3.5/dist-packages/django/apps/registry.py", line 108, in populate
app_config.import_models()
File "/usr/local/lib/python3.5/dist-packages/django/apps/config.py", line 202, in import_models
self.models_module = import_module(models_module_name)
File "/usr/lib/python3.5/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "/opt/netbox-2.3.3/netbox/dcim/models.py", line 21, in
from extras.rpc import RPC_CLIENTS
File "/opt/netbox-2.3.3/netbox/extras/rpc.py", line 6, in
import paramiko
File "/usr/local/lib/python3.5/dist-packages/paramiko/init.py", line 22, in
from paramiko.transport import SecurityOptions, Transport
File "/usr/local/lib/python3.5/dist-packages/paramiko/transport.py", line 57, in
from paramiko.ed25519key import Ed25519Key
File "/usr/local/lib/python3.5/dist-packages/paramiko/ed25519key.py", line 22, in
import nacl.signing
File "/usr/local/lib/python3.5/dist-packages/nacl/signing.py", line 19, in
import nacl.bindings
File "/usr/local/lib/python3.5/dist-packages/nacl/bindings/init.py", line 17, in
from nacl.bindings.crypto_box import (
File "/usr/local/lib/python3.5/dist-packages/nacl/bindings/crypto_box.py", line 27, in
crypto_box_SEEDBYTES = lib.crypto_box_seedbytes()
AttributeError: cffi library '_sodium' has no function, constant or global variable named 'crypto_box_seedbytes'
[2018-05-30 09:47:20 +0000] [7107] [INFO] Worker exiting (pid: 7107)
[2018-05-30 09:47:20 +0000] [7108] [ERROR] Exception in worker process
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/gunicorn/arbiter.py", line 583, in spawn_worker
worker.init_process()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/workers/base.py", line 129, in init_process
self.load_wsgi()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/workers/base.py", line 138, in load_wsgi
self.wsgi = self.app.wsgi()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/app/base.py", line 67, in wsgi
self.callable = self.load()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/app/wsgiapp.py", line 52, in load
return self.load_wsgiapp()
File "/usr/local/lib/python3.5/dist-packages/gunicorn/app/wsgiapp.py", line 41, in load_wsgiapp
return util.import_app(self.app_uri)
File "/usr/local/lib/python3.5/dist-packages/gunicorn/util.py", line 350, in import_app
import(module)
File "/opt/netbox-2.3.3/netbox/netbox/wsgi.py", line 8, in
application = get_wsgi_application()
File "/usr/local/lib/python3.5/dist-packages/django/core/wsgi.py", line 13, in get_wsgi_application
django.setup(set_prefix=False)
File "/usr/local/lib/python3.5/dist-packages/django/init.py", line 27, in setup
apps.populate(settings.INSTALLED_APPS)
File "/usr/local/lib/python3.5/dist-packages/django/apps/registry.py", line 108, in populate
app_config.import_models()
File "/usr/local/lib/python3.5/dist-packages/django/apps/config.py", line 202, in import_models
self.models_module = import_module(models_module_name)
File "/usr/lib/python3.5/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "/opt/netbox-2.3.3/netbox/dcim/models.py", line 21, in
from extras.rpc import RPC_CLIENTS
File "/opt/netbox-2.3.3/netbox/extras/rpc.py", line 6, in
import paramiko
File "/usr/local/lib/python3.5/dist-packages/paramiko/init.py", line 22, in
from paramiko.transport import SecurityOptions, Transport
File "/usr/local/lib/python3.5/dist-packages/paramiko/transport.py", line 57, in
from paramiko.ed25519key import Ed25519Key
File "/usr/local/lib/python3.5/dist-packages/paramiko/ed25519key.py", line 22, in
import nacl.signing
File "/usr/local/lib/python3.5/dist-packages/nacl/signing.py", line 19, in
import nacl.bindings
File "/usr/local/lib/python3.5/dist-packages/nacl/bindings/init.py", line 17, in
from nacl.bindings.crypto_box import (
File "/usr/local/lib/python3.5/dist-packages/nacl/bindings/crypto_box.py", line 27, in
crypto_box_SEEDBYTES = lib.crypto_box_seedbytes()
AttributeError: cffi library '_sodium' has no function, constant or global variable named 'crypto_box_seedbytes'
[2018-05-30 09:47:20 +0000] [7108] [INFO] Worker exiting (pid: 7108)
[2018-05-30 09:47:20 +0000] [7104] [INFO] Shutting down: Master
[2018-05-30 09:47:20 +0000] [7104] [INFO] Reason: Worker failed to boot.

Seriously? You closed this? What's missing from the template?

File "/usr/local/lib/python3.5/dist-packages/nacl/signing.py", line 19, in
import nacl.bindings
File "/usr/local/lib/python3.5/dist-packages/nacl/bindings/init.py", line 17, in
from nacl.bindings.crypto_box import (
File "/usr/local/lib/python3.5/dist-packages/nacl/bindings/crypto_box.py", line 27, in
crypto_box_SEEDBYTES = lib.crypto_box_seedbytes()
AttributeError: cffi library '_sodium' has no function, constant or global variable named 'crypto_box_seedbytes'

This is not a bug in NetBox, it is a problem with your installation environment. That is why I closed the ticket with the suggestion that you post to the mailing list for assistance.

The installation environment is the result of installing the requirements provided by netbox. That was a clean venv, with nothing in it before I started.


mimir_alertmanager_config - child routes to inherit global parameters

when working with https://registry.terraform.io/providers/fgouteroux/mimir/latest/docs/resources/alertmanager_config#child_route I noticed that the child routes seem not to inherit global settings, this unnecessarily complicates the config
example of the current requirements:
  route {
    global {
      pagerduty_url = "https://events.pagerduty.com/v2/enqueue"
      resolve_timeout = "5m"
    }

    group_by = ["alertname", "instance"]
    group_wait = "10s"
    group_interval = "1m"
    repeat_interval = "1h"
    receiver = "default"

    route {
      group_wait = "10s"
      group_interval = "1m"
      repeat_interval = "1h"
      receiver = "aaa"
    }
    route {
      group_wait = "10s"
      group_interval = "1m"
      repeat_interval = "1h"
      receiver = "bbb"
    }
    route {
      group_wait = "10s"
      group_interval = "1m"
      repeat_interval = "1h"
      receiver = "ccc"
    }
  }

example of config with inheriting enabled:
  route {
    global {
      pagerduty_url = "https://events.pagerduty.com/v2/enqueue"
      resolve_timeout = "5m"
    }

    group_by = ["alertname", "instance"]
    group_wait = "10s"
    group_interval = "1m"
    repeat_interval = "1h"
    receiver = "default"

    route {
      receiver = "aaa"
    }
    route {
      receiver = "bbb"
    }
    route {
      receiver = "ccc"
    }
  }

Indeed, according to the doc:

A route block defines a node in a routing tree and its children. Its optional configuration parameters are inherited from its parent node if not set.

This will require to remove default parameters of child route and merge the root route parameters.

Okay, thank you. I will try this and let you know.

I tested things.
In my config I have no parameters such as group_interval defined at child_route level. So according to the previous post the config parameters should get inherited from the global level:
resource "mimir_alertmanager_config" "mimir_alertmanager_main_config" {
  count = var.alertmanager_all_alerts_enabled == true ? 1 : 0

  global {
    pagerduty_url = "https://events.pagerduty.com/v2/enqueue"
    resolve_timeout = "5m"
  }

  route {
    group_by = ["alertname", "instance"]
    group_wait = "10s"
    group_interval = "1m"
    repeat_interval = "1h"
    receiver = "xyz"

    child_route {
      matchers = [
        - "severity = xyz"
        - "team = xyz"
      ]
      receiver = "xyz"
    }
	}
}

however they are not inherited:
│ Error: Missing required argument
│
│   on alertmanager.tf line 289, in resource "mimir_alertmanager_config" "mimir_alertmanager_main_config":
│  289:     child_route {
│
│ The argument "group_interval" is required, but no definition was found.

This behaviour is consistent with provider's docs: https://registry.terraform.io/providers/fgouteroux/mimir/latest/docs/resources/alertmanager_config#child_route
Required:
group_interval (String) How long to wait before sending a notification about new alerts that are added to a group of alerts for which an initial notification has already been sent.

However in my case I have ~40 child routes, 99% of those do not require their parameters to differ from the global ones. So for the simplicity of the config, can't a change be made for these parameters to actually get inherited from the globals (unless explicitly defined on child routes level)?

@shybbko it should be fixed with the https://github.com/fgouteroux/terraform-provider-mimir/pull/29. No need to repeat each param in child_route as it will take them from the route config.

Yup, looks like v0.2.6 of the provider fixed the issue. Thank you! <3


Crashes

It appears that Discord rolled something breaking out that the bot can't handle. Updating discordpy might solve it.

Fixed.


tailwind 3.1.7 does not exist, plugin not required in top of generate…

…d config
Hit these issues when installing this for a new project. Tests still do not pass, even with these changes.
1) test updates on install (TailwindTest)
     test/tailwind_test.exs:33
     Assertion with == failed
     code:  assert Tailwind.run(:default, ["--help"]) == 0
     left:  137
     right: 0
     stacktrace:
       (ex_unit 1.13.4) lib/ex_unit/capture_io.ex:272: ExUnit.CaptureIO.do_capture_gl/2
       (ex_unit 1.13.4) lib/ex_unit/capture_io.ex:230: ExUnit.CaptureIO.do_with_io/3
       (ex_unit 1.13.4) lib/ex_unit/capture_io.ex:106: ExUnit.CaptureIO.capture_io/1
       test/tailwind_test.exs:37: (test)

  2) test run with pre-existing app.css (TailwindTest)
     test/tailwind_test.exs:27
     Assertion with == failed
     code:  assert Tailwind.run(:default, []) == 0
     left:  137
     right: 0
     stacktrace:
       (ex_unit 1.13.4) lib/ex_unit/capture_io.ex:272: ExUnit.CaptureIO.do_capture_gl/2
       (ex_unit 1.13.4) lib/ex_unit/capture_io.ex:230: ExUnit.CaptureIO.do_with_io/3
       (ex_unit 1.13.4) lib/ex_unit/capture_io.ex:106: ExUnit.CaptureIO.capture_io/1
       test/tailwind_test.exs:28: (test)

This has been fixed in 0.1.8. Thanks!


Can't connect to multiple servers

When I try, weechat becomes really laggy to the point where it's unusable. Not really sure how to fix this.
why does weechat not support python 3 so I can use asyncio

also I accidentally deleted the old repo so @heyitsmeuralex your comment is gone :(
I still have it in an open tab, so here's what you said:

As a workaround, you can only have a websocket open to the current buffer's server at once, and for all others poll /api/channel-list?sessionID= to figure out if you have any unread notifications in a particular channel.

Then I said

I guess that could work - closing and opening websockets every time the user switches buffers seems like it would be slow though 🤔

accidentally deleted

...Github forces you to type in the name of the repo before allowing you to kill it :shipit: 🤔

ok, maybe it wasn't entirely accidental. I deleted the repo, thinking it would fix a problem I was having. It didn't 📦
...computers are hard

update: I made it so weechat is now usable when connecting to multiple servers! it's slow, and you can't receive messages in weecent, but it works and you can send messages.
when two servers are loaded, core fills up with 10000+ of these error messages:
11:25 python: stdout/stderr: Traceback (most recent call last):
11:25 python: stdout/stderr:   File "/home/david/.weechat/python/weecent.py", line 89, in timer_cb
11:25 python: stdout/stderr:     message_data = xd[server]['socket'].recv()
11:25 python: stdout/stderr:   File "/usr/local/lib/python2.7/dist-packages/websocket/_core.py", line 293, in recv
11:25 python: stdout/stderr:     opcode, data = self.recv_data()
11:25 python: stdout/stderr:   File "/usr/local/lib/python2.7/dist-packages/websocket/_core.py", line 310, in recv_data
11:25 python: stdout/stderr:     opcode, frame = self.recv_data_frame(control_frame)
11:25 python: stdout/stderr:   File "/usr/local/lib/python2.7/dist-packages/websocket/_core.py", line 323, in recv_data_frame
11:25 python: stdout/stderr:     frame = self.recv_frame()
11:25 python: stdout/stderr:   File "/usr/local/lib/python2.7/dist-packages/websocket/_core.py", line 357, in recv_frame
11:25 python: stdout/stderr:     return self.frame_buffer.recv_frame()
11:25 python: stdout/stderr:   File "/usr/local/lib/python2.7/dist-packages/websocket/_abnf.py", line 340, in recv_frame
11:25 python: stdout/stderr:     self.recv_header()
11:25 python: stdout/stderr:   File "/usr/local/lib/python2.7/dist-packages/websocket/_abnf.py", line 288, in recv_header
11:25 python: stdout/stderr:     header = self.recv_strict(2)
11:25 python: stdout/stderr:   File "/usr/local/lib/python2.7/dist-packages/websocket/_abnf.py", line 375, in recv_strict
11:25 python: stdout/stderr:     bytes_ = self.recv(min(16384, shortage))
11:25 python: stdout/stderr:   File "/usr/local/lib/python2.7/dist-packages/websocket/_core.py", line 427, in _recv
11:25 python: stdout/stderr:     return recv(self.sock, bufsize)
11:25 python: stdout/stderr:   File "/usr/local/lib/python2.7/dist-packages/websocket/_socket.py", line 80, in recv
11:25 python: stdout/stderr:     bytes_ = sock.recv(bufsize)
11:25 python: stdout/stderr:   File "/usr/lib/python2.7/ssl.py", line 756, in recv
11:25 python: stdout/stderr:     return self.read(buflen)
11:25 python: stdout/stderr:   File "/usr/lib/python2.7/ssl.py", line 643, in read
11:25 python: stdout/stderr:     v = self._sslobj.read(len)
11:25 python: stdout/stderr: ssl.SSLWantReadError: The operation did not complete (read) (_ssl.c:1754)
11:25 =!= python: error in function "timer_cb"

fantastic

correction: not 10000+ error messages, 10000+ lines. the error message is 26 lines. 10000 / 26 =<PHONE_NUMBER>15, so I'm getting<PHONE_NUMBER>15+ error messages.


Flex Layout

Preparation

[x] Existing defect backlog reviewed/evaluated, prioritized, and selected
[x] Functional requirements defined: functional test script is defined/written (not coded) and signed off by Dev, Design, ADA and Product leads
[x] Non-functional requirements defined (e.g. controlled vs. uncontrolled)
[x] Existing enhancements backlog reviewed/evaluated, prioritized, and selected
[x] Usability testing plan defined or deemed unnecessary
[x] Examples needed to properly demonstrate component features are defined and signed off by Dev, Design, ADA and Product leads

Development

[x] Component implemented in/ported to TypeScript
[x] 3rd-party dependencies removed
[x] JSS converted to CSS
[x] CSS upgraded to use characteristics
[x] Selected defects resolved
[x] Component API finalized
[x] Necessary refactoring completed
[x] Selected enhancements added

Testing

[x] Functional test script is implemented in Cypress and passes
[x] Code not covered by the functional test script is identified and reviewed by Dev & Design leads
[x] QA (v1-2 visual regression) test passes
[x] Automated Axe tests added and pass

Examples

[x] All examples present in TK1 are implemented as stories in Odyssey (ported from BitBucket)
[x] All examples needed are implemented as stories (either ported from BitBucket or created net new)

Deployment

[x] Codemods for migration created and verified

Reviews/Signoff

[x] Dev production review
[x] Design review
[ ] Product signoff
[ ] ADA review

Documentation

[x] Dev docs content provided
[x] TK1→Odyssey migration guide provided
[ ] Design docs provided
[x] Consolidated documentation produced by combining dev content, migration guide, and design docs
[x] Consolidated documentation published on Storybook
[x] Consolidated documentation reviewed and updated according to user feedback

Figma symbols

[ ] New Odyssey Figma symbol created
[ ] Figma symbol references updated to use new Figma symbol

Suggested changes from Jira 9455 has been implemented.
There is only design consideration left about separators. When a. Page is zoomed in and it reflows, separators appear on the right which do not have any function (they do not separate anything) as they are at the end. Please see screenshots below.

Hi @maj-stella, I've changed the default wrap value to false as discussed https://flex-layout-nowrap-by-defaul.uitk.pages.dev/?path=/story/core-layout-flexlayout--default-flex-layout

@maj-stella please see the below link for the changes on responsiveness:
https://layout-examples-ada-update.uitk.pages.dev/?path=/story/core-layout-flexlayout--default-flex-layout

I'm signing Flex Layout off; however the following examples 'Flex Layout Simple Usage', Flex Layout Composite' and 'Flex Layout Nested' need to be revisited when components which are used in Flex Layout are developed. Currently those components are not accessible.
Also I recommend design review when separators are used in zoom in 400% screen.


Fix-Keep date picker open when selecting time, month, year in Table widget filters

Description
Keep date picker open when selecting time, month, year in Table widget filters
Fixes #4277
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: fix/table-date-filters

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
51.98 (0.02)
33.66 (0.02)
30.01 (0.02)
52.64 (0.01)

:green_circle:
app/client/src/components/designSystems/blueprint/DatePickerComponent2.tsx
28.17 (0.39)
3.17 (0)
5.88 (0)
27.54 (0.4)

:green_circle:
app/client/src/utils/helpers.tsx
55.35 (1.89)
30.14 (4.11)
25.93 (3.71)
48.8 (1.6)

/ok-to-test sha=c2e9a20

@vicky-primathon Now im able to set day, time, month and year working as expected

@vicky-primathon please clear all conflicts here


Schema validation - ignore certain warnings?

Hello!
I just started using your extension to update my book, and I'm seeing a lot of validation errors that I believe should be correct. For example, the first is using @component which should be valid:

The second is using slate element, which although I don't see in the manual any more, I hope it's still available:

The rest of the warnings are reasonable things I should fix this summer.  If these are valid, is there a mechanism to ignore certain validation warnings?
Thanks!

The validation is done with vscode-xml by using a rng schema I think.
It is not possible to ignore some errors. The proper fix is to fix the rng schema

Thanks! I'll look into that

@jmhammond, the official schema is lagging behind a bit.  If you search vs code settings for pretext, you should see an option to use the experimental or development schema.  That will reduce the number of errors you see.
If you still see errors that you think shouldn't be, do let me know and I'll try to update the experimental schema with them.

Please note that vscode-xml provides an easy mean to open schema from xml and  edit it. If you save the schema, xml validation will be retrigered.
To open the schema and go where the validation rule is declared as xml, you open contextual menu from the xml node and clixk on go to type definition


Support numpy types

Pass in a np.mean(my_numpy_array) value to wiz.res() and it'll work fine. However, Pylance complains that we don't have a matching overload for res which is true. We should allow numpy types, e.g. numpy.float64 and so on since numpy is so widely used in scientific research. Maybe there's a generic numpy number type that one could employ.
Note that "it'll work fine" is of course only true if the user has installed numpy (which is reasonable when they pass in a numpy value). But we should check for that and issue an error if that is not the case (suggest that user should install numpy).

Feel free to check this issue out @paul019


What are external sets, internally?

At various points, we would like to quantify internally not over all types, but over "locally locally constant sheaves" (?). For example, naively we would say a general (not necessarily quasi-compact) open proposition is one of the form $\exists (i : I), f(i) \ne 0$, where $I$ is some type and $f : I \to R$. But if we allow all types, then every proposition $P$ is open (take $I = P$ and $f$ constantly $1$). Instead we restrict to finite types.
But how about the following more general notion. (I think we discussed something like this at SAG 2 with @iblech.) We define what it means for a (0-truncated) type $I$ to be external. It is a general fact that $I$ is the filtered colimit of $[n]$ over all $n : \mathbb N$ and maps $[n] \to I$. Say $I$ is external if this colimit is preserved by the functor $(-)^X$ for every affine scheme $X$. I think this means that any map $X \to I$ factors through $[n]$ for some $[n]$, and that two maps $X \to [n] \to I$ and $X \to [m] \to I$ are equal only if there is a common co-refinement $X \to [k] \to I$ (via maps $[n] \to [k]$, $[m] \to [k]$ making everything commute). For example $\mathbb N$ (by boundedness) and any finite set should be external.
I don't know if this is exactly the right definition. But my question is: can we use some definition like this to go beyond finiteness restrictions in SAG, to define general opens and perhaps general schemes (not necessarily finitely presented)?

First thoughts:

I like this proposed definition!
Your definition would not generalize to sites which have non-finite coverings. For instance we don't have boundedness in toposes over such sites. But this need not block us. In all the sites we study (Zariski, and perhaps etale, fppf, ...), all coverings are finite.

Let me also, just for reference, share other proposed conditions I know of:

A set I is external iff for every f.p. R-algebra A, the canonical map Hom(Spec(A), I_discrete) → I^Sp(A) is bijective, where Spec(A) is the pointfree spectrum of A, I_discrete is I regarded as a discrete pointfree space and Sp(A) is the usual SAG-spectrum.
A set I is external iff the free module R⟨I⟩ is strongly quasicoherent.

Sorry if this is a silly question - what is the intuition for "external"?


Write doc on cancelling death animations:

Sure I guess. If you're gonna mention me also mention MrPengoiun since he dug around the decompiled Java code to find the formula for me.
Might also be worth mentioning that the rotation needs to be applied to a bone parent to all other bones, with a pivot at [0,0,0], and the animation should only start when  !query.is_alive

"rotation" : [ 0, 0, "Math.min(Math.sqrt(Math.max(0, query.anim_time * 20 - 0.5) / 20 * 1.6), 1) * -90" ]


The selected emails are wrong.

Hey,
I detected an issue related to this: https://github.com/KartikTalwar/gmail.js/issues/417
I had to fix removing your code here: https://github.com/appfluence/gmail.js/commit/86f4e0992ae2b2a6f7cc082ce965356e0da871aa
Could you tell me the reason to include these lines?
`// tentative fix for https://github.com/KartikTalwar/gmail.js/issues/417
             if (api.check.is_google_apps_user()) {

                 url += "&search=" + "inbox";

             } else {

                 url += "&search=" + "mbox";

           }`

There's lots of discussion around these lines here in various issues, including #417.
For me personally, this is code I never use myself, so I really have no opinion on these, expect from what I'm told from people using and testing them (on several accounts, gmail, gsuite, old, new, etc).
And until now, this has supposedly been the best way to get reliable results for this function.
If that's no longer the case, feel free to issue a PR on these matters, but please note we will need to have some test-data/reports that shows that it works consistently across all the above-mentioned configurations, because we don't want to risk breaking stuff for others.
If you create such a PR, please CC @ other people from those issues so they too can assist testing.

reason because I didn't a PR with changes, I can't justify that this is the best solution

I can completely sympathize.

For now, I will continue working in other branch

That's absolutely fair.
But what you could do if you want to stay on mainline gmail.js and seamlessly get bug-fixes and improvements without having to maintain your own fork is this...
How about you extend the api.get.visible_emails() functions with an optional search/query-parameter which takes precedence over the specific code-section you've pasted above:
            } else {
                if (customInboxQuery) {
                    url += "&search=" + customInboxQuery;
                }
                // tentative fix for https://github.com/KartikTalwar/gmail.js/issues/417
                else if (api.check.is_google_apps_user()) {
                    url += "&search=" + "inbox";
                } else {
                    url += "&search=" + "mbox";
                }
            }

That way, you get to control the behaviour you want in your extension without having the huge burden of proving that is the one correct way everyone should do it.
It's not perfectly clean, but I'd like to avoid fragmentation in the gmail.js ecosystem as much as possible, and would consider that a decent compromise.
If you think that sounds OK, feel free to issue a (much smaller) PR for that change and I will review it quickly.

Thanks @josteink , I agree with you. I like so much that proposal.
Doing PR now.


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
15 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
9 seconds
sanity-inspect-image

✅ Succeeded
8 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
16 seconds
clair-scan

✅ Succeeded
13 seconds
sbom-json-check

✅ Succeeded
16 seconds
sanity-label-check

✅ Succeeded
16 seconds
sanity-optional-label-check

✅ Succeeded
6 seconds
show-summary


Exclude information about the repo and owner

This would seem to fall into the category of "if these values are unsafe, we have bigger problems to deal with"

Thanks @funnelfiasco! I think this is going to be similar to https://github.com/woodruffw/zizmor/pull/128 -- excluding repository_id and repository_owner_id seems 100% right to me, but I need to think about the others.
(AFAIK repo/owner information is probably safe, but URL quoting/escaping isn't always super consistent, and there may be funny things that someone can do with Enterprise deployment URLs.)

Of course GitHub doesn't provide documentation on what's actually possible, but in the case of these values there's nothing an attacker could do to modify them. So even if it's possible and someone names their repository Robert'); DROP TABLE Students;-- then plenty of other things will probably break before they ever get to running a GitHub workflow.

Of course GitHub doesn't provide documentation on what's actually possible, but in the case of these values there's nothing an attacker could do to modify them.

I think that's right, except for in the fork context -- in that context the attacker controls all of these, but I agree that there's still no injection risk with them (I suppose someone could name their GitHub account reboot or something like that, but they still don't have the escape primitives needed).
Given that, I'm good with this. Thanks for the PR!


Jest snapshot problem with component Fade

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
When Fade component has in={true}, Jest fails to render it with message TypeError: Cannot set property 'webkitTransition' of undefined
Stack trace:
      at Object.handleEnter [as onEnter] (node_modules/@material-ui/core/Fade/Fade.js:66:33)
      at Transition.performEnter (node_modules/react-transition-group/cjs/Transition.js:282:16)
      at Transition.updateStatus (node_modules/react-transition-group/cjs/Transition.js:253:14)
      at Transition.componentDidMount (node_modules/react-transition-group/cjs/Transition.js:195:10)
      at commitLifeCycles (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12078:22)
      at commitLayoutEffects (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:15276:7)
      at HTMLUnknownElement.callCallback (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:11616:14)
      at Object.invokeGuardedCallbackDev (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:11665:16)
      at invokeGuardedCallback (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:11718:31)
      at commitRootImpl (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:15012:9)
      at unstable_runWithPriority (node_modules/react-test-renderer/node_modules/scheduler/cjs/scheduler.development.js:815:12)
      at runWithPriority (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:2038:10)
      at commitRoot (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:14853:3)
      at finishSyncRender (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:14346:5)
      at performSyncWorkOnRoot (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:14318:9)
      at node_modules/react-test-renderer/cjs/react-test-renderer.development.js:2088:24
      at unstable_runWithPriority (node_modules/react-test-renderer/node_modules/scheduler/cjs/scheduler.development.js:815:12)
      at runWithPriority (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:2038:10)
      at flushSyncCallbackQueueImpl (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:2083:7)
      at flushSyncCallbackQueue (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:2071:3)
      at scheduleUpdateOnFiber (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:13696:9)
      at scheduleRootUpdate (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:16931:3)
      at updateContainerAtExpirationTime (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:16959:10)
      at updateContainer (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:16979:10)
      at Object.create (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:17722:5)
      at Object.<anonymous>.test (src/components/CircleNumber.test.tsx:14:6)

Expected Behavior 🤔
Test should be able to render a composite component containing <Fade in={true}/>.
Steps to Reproduce 🕹
Steps:
import React from "react";
import renderer from "react-test-renderer";
import { Fade } from "@material-ui/core";

test("Fade should render correctly", () => {
   const tree = renderer
    .create(
        <Fade in={true}>

some text

        </Fade>)
    .toJSON();
  expect(tree).toMatchSnapshot();
});

Context 🔦
Snapshot testing with Jest as explained here: https://jestjs.io/docs/en/snapshot-testing
Your Environment 🌎

Tech
Version

Material-UI
v4.5.1

React
v16.9.0

Jest
v24.9.0

Duplicate of #17119. An update of our documentation is welcome.

@oliviertassinari I followed your comment, but still get the same error:
import React from "react";
import renderer from "react-test-renderer";
import { Fade } from "@material-ui/core";

test("Fade should render correctly", () => {
  const tree = renderer
    .create(
      <Fade in={true}>

some text

      </Fade>,
      {
        createNodeMock: node => document.createElement(node.type as any);
      }
    )
    .toJSON();
  expect(tree).toMatchSnapshot();
});

@alexiwonder Oh right, sorry, we track this problem in:
https://github.com/mui-org/material-ui/blob/cec2f0caf91f5ea235e1a62a8c6c2493075927ef/packages/material-ui/src/Fade/Fade.test.js#L33-L34

If anyone is still facing this issue, try checking out the documentation and using one of the test utils there.
This helped me for my case, I created a render HOC to use for each test that had a MaterialUI component.
import React from 'react';
import Theme from '../../components/App/shared/ThemeProvider';
import { BrowserRouter as Router } from 'react-router-dom';
import { createRender } from '@material-ui/core/test-utils';

export const withMaterial = (Component: any, props?: any) => {
  const render = createRender();
  return render(
      <Router>
        <Theme>
          <Component {...props} />
        </Theme>
      </Router>
    );
};

Can this be done without enzyme? I am using Jest.

I found a solution to mock the Fade component in Material UI.
jest.mock('@material-ui/core', () => {
  const materialUI = jest.requireActual('@material-ui/core');
  return {
    ...materialUI,
    Fade: jest.fn(({ children }) => children),
  }
});

describe('Component', () => {
  const { ThemeProvider } = jest.requireMock('@material-ui/core');

  it('renders correctly', () => {
    const tree = renderer.create(
      <ThemeProvider theme={theme}>
        <Component />
      </ThemeProvider>,
    ).toJSON();
    expect(tree).toMatchSnapshot();
  });
});

Correct solution: https://github.com/mui-org/material-ui/issues/17119#issuecomment-524266401

I'm still getting this error with implementing solution from https://github.com/mui-org/material-ui/issues/17119#issuecomment-524266401
I'm unit testing a component with react-test-renderer.
My component is using a few material-ui components:
import Drawer from '@material-ui/core/Drawer';
import AppBar from '@material-ui/core/AppBar';
import Toolbar from '@material-ui/core/Toolbar';
import Divider from '@material-ui/core/Divider';

Partial test code:
const tree = renderer.create(<Navbar />, {
  createNodeMock: (node: ReactHTMLElement<HTMLElement>): HTMLElement =>
    document.createElement(node.type)
});

...
...

const as = tree.root.findAllByType('a');

// Error is thrown here
act(() => {
  as[0].props.onClick(e); // Should open Mui Drawer
});

Error:
TypeError: Cannot set property 'webkitTransition' of undefined

      103 |
      104 |       // Open mobile drawer
    > 105 |       act(() => {
          |       ^
      106 |         as[0].props.onClick(e);
      107 |       });
      108 |

      at node_modules/@material-ui/core/Fade/Fade.js:100:33
      at Object.onEnter (node_modules/@material-ui/core/Fade/Fade.js:84:11)

@oliviertassinari I'm still getting this error when implementing solution from #17119 (comment)
I'm unit testing a component with react-test-renderer.
My component is using a few material-ui components:
import Drawer from '@material-ui/core/Drawer';
import AppBar from '@material-ui/core/AppBar';
import Toolbar from '@material-ui/core/Toolbar';
import Divider from '@material-ui/core/Divider';

Partial test code:
const tree = renderer.create(<Navbar />, {
  createNodeMock: (node: ReactHTMLElement<HTMLElement>): HTMLElement =>
    document.createElement(node.type)
});

...
...

const as = tree.root.findAllByType('a');

// Error is thrown here
act(() => {
  as[0].props.onClick(e); // Should open Mui Drawer
});

Error:
TypeError: Cannot set property 'webkitTransition' of undefined

      103 |
      104 |       // Open mobile drawer
    > 105 |       act(() => {
          |       ^
      106 |         as[0].props.onClick(e);
      107 |       });
      108 |

      at node_modules/@material-ui/core/Fade/Fade.js:100:33
      at Object.onEnter (node_modules/@material-ui/core/Fade/Fade.js:84:11)

I've tried mocking Fade as well, but that is throwing another stack of errors. Although it was working for a while until a recent Mui version upgrade I believe.
jest.mock('@material-ui/core/Fade');

ForwardRef(Fade)(...): Nothing was returned from render. This usually means a return statement is missing. Or, to render nothing, return null.

      103 |
      104 |       // Open mobile drawer
    > 105 |       act(() => {
          |       ^
      106 |         as[0].props.onClick(e);
      107 |       });
      108 |

at reconcileChildFibers (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:5475:23)
at reconcileChildren (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:7984:28)
at updateForwardRef (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:8050:3)
at beginWork (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:10015:16)
at performUnitOfWork (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:13800:12)
at workLoopSync (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:13728:5)
at renderRootSync (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:13691:7)
at performSyncWorkOnRoot (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:13404:18)
at node_modules/react-test-renderer/cjs/react-test-renderer.development.js:2537:26
at unstable_runWithPriority (node_modules/scheduler/cjs/scheduler.development.js:646:12)
at runWithPriority (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:2486:10)
at flushSyncCallbackQueueImpl (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:2532:9)
at flushSyncCallbackQueue (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:2519:3)
at batchedUpdates (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:13459:7)
at Object.act (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:15280:14)

it worked well for me:
jest.mock('@material-ui/core/Fade');
My dependencies:
"enzyme": "~3.11.0",
"enzyme-adapter-react-16": "1.15.6",
"enzyme-to-json": "~3.6.1",
"jest": "~26.6.3",
"jest-enzyme": "~7.1.2",
"react": "~16.7.0",
"react-dom": "~16.7.0",
"react-router-redux": "~4.0.8",
"react-test-renderer": "~16.7.0",


Optionally include Pages in serialized organizations

Reference: #2318
Just stuck pages into the org serializer's can_include. Index methods aren't authenticated and therefore won't show you pages from private projects or orgs.
EXTRA CREDIT: I took the opportunity to actually extract out the page controller stuff from the org and project controllers into it's own concern.
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

Didn't find a more magical way to define those methods, did add a comment. The require_authentication line seems to run in a slightly different context than the rest of the included block (self = controller vs. the Pages include itself), making using the constants bit squirrely.
It's all working now, though moving forward I might rather have two similar lines than one awkward one.


2 simultaneous lighthouses crashes the LH driver

Testing the main branch, the 01bsp_lighthouse project.
When placed in front of a 1 lighthouse in mode 1, it works as expected.
When placed in front of 2 lighthouses in mode 1 and mode 3 respectively, it crashes after a few seconds.

Here is a capture from a logic analyzer, the red line are successful SPI interruptions.
After a certain amount of time, the code doesn't crash, nor throws a Hardfault, the SPI interruptions just stop happening.
The crash always occurs when 2 sweeps overlap and arrive at the same time at the diode receiver.
Shown here:

Here you can see the system in normal operation when the 4 pulses are separated:
![image](https://github.com/DotBots/DotBot-firmware/assets/11748427
Not all sweep overlaps cause a crash, but all crashes occur on a sweep overlap.
Here is the file with the logic analyzer capture:
2LH_crash.zip

Bug seems to be related to the SPI interrupting itself.
If the envelope signal jitters too much, the SPI transfer can stop prematurely.

(A full transmission takes 16us, this one was cut in half.)
After this occur, following SPI transmissions become abruptly shortened despite no longer having any jitter in the envelope line.

Sometimes the SPI reconvers from this state and continues working normally, and sometimes it crashes completely, which leads to the behavior mentioned in the last comment

I wonder if there is a way of automatically shutting down either the PPI or the GPIOTE while an SPI transmission is occuring, so that they can't retrigger the SPI while it is already transmitting

Fix 1:  Configure the PPI only to start the SPI transfer when the Envelope pin goes down, and not stop it if the Envelope pin goes Up
Result: Didn't work, perhaps made it worse.

Now the final transfer always completes, but if another request to initiate a transfer arrives while a transfer is currently in progress, the SPI peripheral crashes, the interrupt won't trigger, and no further SPI transfers will occur.
fix1_capture.zip

Fix 2:
Put both PPI channels (activate on Envelope negative edge, and activate on end of SPI transmission) on a group.
The envelope signal going LOW causes the SPI to begin a transmission, and  the PPI group to disable itself.
This prevents jitter in the envelope line to trigger multiple simultaneous SPI transmissions.
The end of the SPI transmission, triggers the PPI group to enable itself.
Kind of worked

The code no longer crashes, but SPI transmissions don't trigger as often as they should.

It triggers only once every 2 or 3 LH revolutions.
Logic analyzer capture data:
fix2_capture.zip

Fix 3:
The same PPI that triggers the SPI transfer when the Envelope signal goes low also disables itself (the PPI disables the PPI).
This prevents spurious flickering in the Envelope line to trigger multiple simultaneous SPI transfers.
The PPI is reenabled in the SPI ISR once it's safe to do so.
This works, and catches every single pulse, no crashes.
Tested with 4 simultaneous lighthouses.


Dungeon/Skyblock Extras

IGNORE FOR NOW
This is currently just a draft for anyone to help and commit to
For a short explanation, the plan for this is to implement Ether Warp Routes, Extra Blocks, and Command Waypoints in dungeons and out of dungeons. Also the user should be able to split it up into categories that also can get loaded of links.
Done:

Find a way to create etherwarp routes without getting banned

WIP:

Make Commands usable outside of dungeons
Base Command Waypoints
Base Extra Blocks

Planned:

Add a good looking Gui for managing categories
Make Categories loadable from a Url
Add a faster way for finding room rotations
Base Ether Warp Routes
Gui for selecting current block for edit mode
Find out if Command Waypoints would fall under cheat because its just like Skytils key shortcut but location dependent
Custom GUIs maybe?

work on this all you want but just so i tell you now, this will not be merged to odin, we are not adding autoroutes

first of why not and secondly what about extra blocks and command waypoints or only extra blocks?

I don't see an issue with extra blocks and command thing


Basic Get-Sources fails

$sources = Get-Sources -Offset 0 -Limit 250
fails with:
ConvertFrom-Json: /Users/rob.buskens/.local/share/powershell/Modules/PSSailpoint/1.0.3/cc/src/PSSailpointCC/Private/CCApiClient.ps1:269:16
Line |
269 |          return ConvertFrom-Json $Response
|                 ~~~~~~~~~~~~~~~~~~~~~~~~~~
| Cannot convert the JSON string because it contains keys with different casing. Please use the -AsHashTable switch instead. The key that was
| attempted to be added to the existing key 'userauth.mergeColumns' was 'UserAuth.mergeColumns'.
Having inspected the result of the call, it looks like a valid JSON collection.
Rob

Hey @rob-buskens-sp,
I updated the SDK to use the -AsHashTable switch when calling ConvertFrom-Json. This will allow both casings to be present within the PSObject.
It should be fixed with https://github.com/sailpoint-oss/powershell-sdk/commit/5df140c64e9dde6f6871643df67f7685f79baa99


fix empty check to work with d3 4.x

just checking for obj keys no longer works with d3 4.x. Need a better way...

created new d3 specific checks


chore: add support for OSSF scorecard reporting

Main Changes
This pipeline will proactively report the status of the project (every day and when a push is done to master branch) including critical fields (CI-Tests, Contributors, Dependency-Update-Tool, Webhooks) that are missing while running via OSSF cron jobs.
Context
Changes related

It's also possible that some repositories in your organization are already being automatically tracked by OpenSSF in this CSV file via weekly cronjob. One caveat: Automatically tracked projects do not include https://github.com/ossf/scorecard/issues/3438 in their analysis (CI-Tests,Contributors,Dependency-Update-Tool,Webhooks).
Source: openssf-scorecard-monitor documentation

Team discussion related

Ref: https://github.com/expressjs/security-wg/issues/2
Report: https://kooltheba.github.io/openssf-scorecard-api-visualizer/#/projects/github.com/pillarjs/encodeurl/commit/5f2205efe622fc7972c4e45ed7cbe7f8d652c299

I found my answer here: https://github.com/ossf/scorecard/blob/d58bfb03aab496807d8489e09da9883928465f59/docs/checks.md#pinned-dependencies 😓
Seems like a GitHub Actions "lock file" would be a nice feature to simplify future updates.

A heads up, but I'm already seeing this:

CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/

Sorry I didn't see your messages before @blakeembrey. Thanks for reviewing!

Need review i believe..


Transfer transaction failing

Description
Adding a to account in the table is not working. The accept button does not perform an action.

Steps to reproduce
See above
Additional context
Error log:
2022-06-06 22:22:12.094 [JavaFX Application Thread] ERROR com.hedera.hashgraph.client.core.exceptions.Log4j2UncaughtExceptionHandler.uncaughtException(Log4j2UncaughtExceptionHandler.java:42) - Uncaught exception Hedera Client Runtime: Bad account format: Address "0.0.45912654 " cannot be parsed on thread Thread[JavaFX Application Thread,5,main]
2022-06-06 22:22:12.427 [JavaFX Application Thread] ERROR com.hedera.hashgraph.client.core.exceptions.Log4j2UncaughtExceptionHandler.uncaughtException(Log4j2UncaughtExceptionHandler.java:40) - ERROR: uncaught exception occurs, check app.err log file for details.
Message: Hedera Client Runtime: Bad account format: Address "0.0.45912654 " cannot be parsed
2022-06-06 22:22:12.427 [JavaFX Application Thread] ERROR com.hedera.hashgraph.client.core.exceptions.Log4j2UncaughtExceptionHandler.uncaughtException(Log4j2UncaughtExceptionHandler.java:42) - Uncaught exception Hedera Client Runtime: Bad account format: Address "0.0.45912654 " cannot be parsed on thread Thread[JavaFX Application Thread,5,main]
2022-06-06 22:22:49.140 [JavaFX Application Thread] ERROR com.hedera.hashgraph.client.core.exceptions.Log4j2UncaughtExceptionHandler.uncaughtException(Log4j2UncaughtExceptionHandler.java:40) - ERROR: uncaught exception occurs, check app.err log file for details.
Message: Hedera Client Runtime: Bad account format: Address "0.0.45912654 " cannot be parsed
2022-06-06 22:22:49.141 [JavaFX Application Thread] ERROR com.hedera.hashgraph.client.core.exceptions.Log4j2UncaughtExceptionHandler.uncaughtException(Log4j2UncaughtExceptionHandler.java:42) - Uncaught exception Hedera Client Runtime: Bad account format: Address "0.0.45912654 " cannot be parsed on thread Thread[JavaFX Application Thread,5,main]

Hedera network
other
Version
0.11.0-alpha.1
Operating system
No response

An error message should be displayed to the user


创建supervisor失败

是我的pip版本低吗   我升级也升级不了
`+ mkdir -p /usr/local/kcptun/bin

wget -O /usr/local/kcptun/bin/jq --no-check-certificate https://github.com/stedolan/jq/releases/download/jq-1.5//jq-linux64
--2019-03-08 00:41:39--  https://github.com/stedolan/jq/releases/download/jq-1.5//jq-linux64
Resolving github.com... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to github.com|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/5101141/65ac1c64-43ac-11e5-9195-46846013b9a3?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190307%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190307T165303Z&X-Amz-Expires=300&X-Amz-Signature=60e94c5e3f2aedec48d4251202f13d6119368971e07a187ef4bb8d3be691b5a3&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B filename%3Djq-linux64&response-content-type=application%2Foctet-stream [following]
--2019-03-08 00:41:42--  https://github-production-release-asset-2e65be.s3.amazonaws.com/5101141/65ac1c64-43ac-11e5-9195-46846013b9a3?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190307%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190307T165303Z&X-Amz-Expires=300&X-Amz-Signature=60e94c5e3f2aedec48d4251202f13d6119368971e07a187ef4bb8d3be691b5a3&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B filename%3Djq-linux64&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com... <IP_ADDRESS>
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3027945 (2.9M) [application/octet-stream]
Saving to: “/usr/local/kcptun/bin/jq”

100%[=======================================================================================================================================================================================================>] 3,027,945   3.49M/s   in 0.8s
2019-03-08 00:41:44 (3.49 MB/s) - “/usr/local/kcptun/bin/jq” saved [3027945/3027945]

sha256sum -c
echo 'c6b3a7d7d3e7b70c6f51b706a3b90bd01833846c54d32ca32f0027f00226ff6d  /usr/local/kcptun/bin/jq'
/usr/local/kcptun/bin/jq: OK
wget -O kcptun-v20190109.tar.gz --no-check-certificate https://github.com/xtaci/kcptun/releases/download/v20190109/kcptun-linux-amd64-20190109.tar.gz
--2019-03-08 00:41:46--  https://github.com/xtaci/kcptun/releases/download/v20190109/kcptun-linux-amd64-20190109.tar.gz
Resolving github.com... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to github.com|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/52595226/c375ae80-1466-11e9-826d-06c102b14023?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190307%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190307T165307Z&X-Amz-Expires=300&X-Amz-Signature=e658b29fb010e5b0c711e5f88eb5d57b532199bee3a7c1c8c69ba2960e5a99d2&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B filename%3Dkcptun-linux-amd64-20190109.tar.gz&response-content-type=application%2Foctet-stream [following]
--2019-03-08 00:41:47--  https://github-production-release-asset-2e65be.s3.amazonaws.com/52595226/c375ae80-1466-11e9-826d-06c102b14023?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190307%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190307T165307Z&X-Amz-Expires=300&X-Amz-Signature=e658b29fb010e5b0c711e5f88eb5d57b532199bee3a7c1c8c69ba2960e5a99d2&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B filename%3Dkcptun-linux-amd64-20190109.tar.gz&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com... <IP_ADDRESS>
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4884590 (4.7M) [application/octet-stream]
Saving to: “kcptun-v20190109.tar.gz”

100%[=======================================================================================================================================================================================================>] 4,884,590   4.45M/s   in 1.0s
2019-03-08 00:41:49 (4.45 MB/s) - “kcptun-v20190109.tar.gz” saved [4884590/4884590]

sha1sum -c
echo '1cb077f0ca3872b5c641d7780f133225dfa77c0d  kcptun-v20190109.tar.gz'
kcptun-v20190109.tar.gz: OK
mkdir -p /var/log/kcptun
chmod a+w /var/log/kcptun
tar -zxf kcptun-v20190109.tar.gz -C /usr/local/kcptun
sleep 3
pip install --upgrade pip
DEPRECATION: Python 2.6 is no longer supported by the Python core team, please upgrade your Python. A future version of pip will drop support for Python 2.6
/usr/lib/python2.6/site-packages/pip/vendor/urllib3/util/ssl.py:339: SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
SNIMissingWarning
/usr/lib/python2.6/site-packages/pip/vendor/urllib3/util/ssl.py:137: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
InsecurePlatformWarning
Requirement already up-to-date: pip in /usr/lib/python2.6/site-packages
You are using pip version 9.0.3, however version 19.0.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
pip install supervisor
DEPRECATION: Python 2.6 is no longer supported by the Python core team, please upgrade your Python. A future version of pip will drop support for Python 2.6
Collecting supervisor
/usr/lib/python2.6/site-packages/pip/vendor/urllib3/util/ssl.py:339: SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
SNIMissingWarning
/usr/lib/python2.6/site-packages/pip/vendor/urllib3/util/ssl.py:137: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
InsecurePlatformWarning
/usr/lib/python2.6/site-packages/pip/vendor/urllib3/util/ssl.py:137: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
InsecurePlatformWarning
/usr/lib/python2.6/site-packages/pip/vendor/urllib3/util/ssl.py:137: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
InsecurePlatformWarning
Downloading https://files.pythonhosted.org/packages/ba/65/92575a8757ed576beaee59251f64a3287bde82bdc03964b89df9e1d29e1b/supervisor-3.3.5.tar.gz (421kB)
100% |████████████████████████████████| 430kB 1.0MB/s
Collecting meld3>=0.6.5 (from supervisor)
/usr/lib/python2.6/site-packages/pip/vendor/urllib3/util/ssl.py:137: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
InsecurePlatformWarning
Downloading https://files.pythonhosted.org/packages/b6/ae/e6d731e4b9661642c1b20591d8054855bb5b8281cbfa18f561c2edd783f7/meld3-1.0.2-py2.py3-none-any.whl
Installing collected packages: meld3, supervisor
Running setup.py install for supervisor ... done
Successfully installed meld3-1.0.2 supervisor-3.3.5
You are using pip version 9.0.3, however version 19.0.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
mkdir -p /etc/supervisor/conf.d
++ command -v supervisord
ln -s /usr/bin/supervisord /usr/local/bin/supervisord
++ command -v supervisorctl
ln -s /usr/bin/supervisorctl /usr/local/bin/supervisorctl
++ command -v pidproxy
ln -s /usr/bin/pidproxy /usr/local/bin/pidproxy
echo_supervisord_conf
创建 Supervisor 配置文件失败!`

你可以试试用
pip uninstall -y -r <(pip freeze)

来删除所有 pip 安装的软件，再重新安装

wget -O kcptun-v20190109.tar.gz --no-check-certificate https://github.com/xtaci/kcptun/releases/download/v20190109/kcptun-linux-amd64-20190109.tar.gz
--2019-03-08 03:43:08--  https://github.com/xtaci/kcptun/releases/download/v20190109/kcptun-linux-amd64-20190109.tar.gz
Resolving github.com (github.com)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/52595226/c375ae80-1466-11e9-826d-06c102b14023?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190308%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190308T084308Z&X-Amz-Expires=300&X-Amz-Signature=b8e7a22aedda7d31ace97513f5c47dcb4018ba26a2fdac94c45ca6ee6d5d5b2c&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B filename%3Dkcptun-linux-amd64-20190109.tar.gz&response-content-type=application%2Foctet-stream [following]
--2019-03-08 03:43:09--  https://github-production-release-asset-2e65be.s3.amazonaws.com/52595226/c375ae80-1466-11e9-826d-06c102b14023?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190308%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190308T084308Z&X-Amz-Expires=300&X-Amz-Signature=b8e7a22aedda7d31ace97513f5c47dcb4018ba26a2fdac94c45ca6ee6d5d5b2c&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B filename%3Dkcptun-linux-amd64-20190109.tar.gz&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)... <IP_ADDRESS>
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4884590 (4.7M) [application/octet-stream]
Saving to: ‘kcptun-v20190109.tar.gz’

kcptun-v20190109.tar.gz                                        100%[====================================================================================================================================================>]   4.66M  2.51MB/s   in 1.9s
2019-03-08 03:43:11 (2.51 MB/s) - ‘kcptun-v20190109.tar.gz’ saved [4884590/4884590]

sha1sum -c

echo 1cb077f0ca3872b5c641d7780f133225dfa77c0d  kcptun-v20190109.tar.gz
kcptun-v20190109.tar.gz: OK

tar -zxf kcptun-v20190109.tar.gz -C /usr/local/kcptun

sleep 3

pip install --upgrade pip
DEPRECATION: Python 3.4 support has been deprecated. pip 19.1 will be the last one supporting it. Please upgrade your Python as Python 3.4 won't be maintained after March 2019 (cf PEP 429).
Requirement already up-to-date: pip in /usr/local/lib/python3.4/dist-packages (19.0.3)

pip install supervisor
DEPRECATION: Python 3.4 support has been deprecated. pip 19.1 will be the last one supporting it. Please upgrade your Python as Python 3.4 won't be maintained after March 2019 (cf PEP 429).
Collecting supervisor
Using cached https://files.pythonhosted.org/packages/ba/65/92575a8757ed576beaee59251f64a3287bde82bdc03964b89df9e1d29e1b/supervisor-3.3.5.tar.gz
Complete output from command python setup.py egg_info:
Supervisor requires Python 2.4 or later but does not work on any version of Python 3.  You are using version 3.4.2 (default, Feb  7 2019, 06:08:06)
[GCC 4.9.2].  Please install using a supported version.

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-283z2664/supervisor/
错误: 安装 Supervisor 失败，
请尝试使用
pip install supervisor
来手动安装。
我也一样不行

@2huYa0 什么系统，python 版本

@2huYa0 什么系统，python 版本

DeBian8，python3.4/2.7都不行

我刚才试了一下，Debian 8 默认的 python 版本为 2.7.9
可以正常安装

我刚才试了一下，Debian 8 默认的 python 版本为 2.7.9
可以正常安装

感谢回复！刚刚把系统重置后，可以正常安装了，可能是之前安装的有冲突。谢谢您！


get and set of array values not working in amplify-velocity-template

The implementation of set and get methods of an array in velocity is not working like in the real environment.
These lines should be replaced by an implimentation like:
if (id === 'get' && !baseRef[id]) {
    return baseRef[this.getLiteral(property.args[0])];
} else if (id === 'set' && !baseRef[id]) {
    return baseRef[this.getLiteral(property.args[0])] = this.getLiteral(property.args[1]);
}

May related: https://github.com/shepherdwind/velocity.js/pull/132

@MainAero Thank you for bringing this to our attention. We would appreciate an pull request as we are not merging the upstream to our implementation.

@MainAero - we're about to create a PR for this but wanted to make sure if you want to contribute to provide you an opportunity to do so. Happy to address this either way.

@renebrandel thanks I created a PR for that.
As we are currently working on a typescript based test util for Appsync which enables you to write functional / integration test for your vtl resolvers I guess we might open a few PR's.

Cc @yuth


 But maybe that is planned like this.

What do you think about adding a method to Block that gets called when a block is placed at the top/bottom/left/right of it?

You'll want to look at the Block  class, specifically the onPlace method which is called when a block is placed. From that method you can check the tiles around you.

But is it the best way to just check if the placed block is a grass block and then check if the block under is also a grass block? (everything in onPlayer)

Regarding @AppPhil 's last statement, this seems like a function you'd eventually apply to many blocks, so it might be best to write more reusable code for it instead of hard coding each.
One possibility could be a setReplaceNearby(direction, replaceType, newType) (bad name) function so blocks could set a type which would be replaced by another type if said block is colliding in the specified location. So for this case, it could be setReplaceNearby(down, grassType, dirtType) in the grass block code which would cause grass blocks under other grass blocks to be replaced with dirt.
Of course, this is pointless if the functionality won't be reused.

Good idea, I don't see a problem with adding this functionality. It would still need to be used within onPlace though. This method could lie in the Chunk class and be used when needed for easy replacements like you suggest!

When I create a class GrassBlock that extends Block and I use this for the grass block in the BlockManager all the blocks are black under the grass blocks. I don't know why I just got a GrassBlock class looking like this:
public class GrassBlock extends Block {     public GrassBlock(BlockType type, Drawable drawable, float lightBlockingAmount, boolean collides, boolean transparent, float initHealth, float resistance) {         super(type, drawable, lightBlockingAmount, collides, transparent, initHealth, resistance);     } }

It looks like this:

Very strange. It must be something to do with initializing the block once it's set in the chunk. I will need to look at the Chunk code to see, but I'm pretty sure the bug is originating somewhere in there.

You're right. Commenting out those lines fixes the issue and it breaks torches that are placed. But I'm not sure what you mean how to fix that.

Does it break them when you place them in the game, when the world is loaded, or both?

Only when the world is loaded.

Wait I found out that it happens with the latest version that's here on GitHub so it weren't my changes that did that.

What do you mean exactly? What part of the problem was happening in the last version?

I think the light is broken after loading a world.

Interesting. I will have to take a look, but if I remember accurately it was generating the light correctly. As for the problem on hand however, the code that you commented out was done so that other blocks would have special properties initialized. In this case, the only block that this was applied to was the LightBlock. If you take notice, it was calling the onPlace method which, for a LightBlock, initializes the light on the world. Take a look at the method that this block of code is resides in and you'll notice that it is only called when a Chunk is first generated or loaded from within the ChunkManager. Because not every Block needs special values initialized when it first loads, what the code is doing, calling the onPlace method, is not a good idea. Instead what needs to be done is a new method needs to be created in the Block class, onLoad(ChunkManager chunkManager, Chunk chunk, int chunkTileX, int chunkTileY). This method will be called only when a Block is first loaded into a Chunk through either generation or loading from a saved game. The body of it will be empty in the Block class, but in the LightBlock class, the body of the onPlace method should be copied into the onLoad method (even better, it should be copied to a separate, private method that is called from onPlace and onLoad). If you read through the LightBlock's onPlace method you'll see that all it's doing is generating light. In order to implement this method in the Chunk, you simply need to replace the three lines you commented out with a call to the Block's onLoad method.

Yes now it works with the latest version from GitHub. I don't know what was wrong there. Sorry for that.

Great. Once it's all ready be sure to submit a pull request!

Now I've done what you said but after loading the world the torches only light up one block (their position) and not the blocks near them.

Can you commit your code to your forked repository so I can take a look at it?

Here it is: https://github.com/AppPhil/TerraLegion

Okay so from that commit it looks like you only created the GrassBlock class. You never actually used it. You also never implemented the onLoad functionality that I was explaining above. If it's too confusing I will be able to fix it later tonight so it's no problem at all. The reason that the grass block probably isn't replacing blocks under it is because you never actually set the BlockType.GRASS to an instance of the GrassBlock class. In the BlockManager you need to replace the Block instantiation with a GrassBlock.

Wait. That replacing worked for me. I think I have not commited everything. Oh yes wait I will update...

Here are the other changes: https://github.com/AppPhil/TerraLegion/commit/7b51790feb3728f790b17fc9090a057b879a7d8c

Strange that the light still doesn't generate correctly. If you want to do some investigative work you can debug from the point that LightUtils.extinguishLight method is called and figure out why it is only generating light on the one block. I'll try testing it out later tonight as well. Also, make sure that in the BlockManager you create a GrassBlock rather than a Block for the BlockType.GRASS. Once that is done, submit a pull request and we can close this issue.

Are you sure with LightUtils.extinguishLight? Because that's called in the onBreak method.

Oh my bad, yes I meant the calculateChunkLight. My mistake.

While debugging I found out that the process gets stopped here: https://github.com/jmrapp1/TerraLegion/blob/1030fe0be7483a22488b2a64444c0a2f0df64c04/core/src/com/jmrapp/terralegion/game/utils/LightUtils.java#L38 so before the light is correctly set.

I think it might be not working fine because Chunk.getLightValue() return 1.0 for positions of LightBlocks so the applyLight() method thinks there is already light. But I reallly don't know how to fix that. I tried it for hours today...

The lighting algorithm is a very hard algorithm to debug because it's recursive. You have to keep track of what Block it is looking at and it almost requires you to draw it out to understand where you're at. I'll take a look at it later today to see what I can find.

I found out that the light is only not working after loading a world when it is placed in a topChunk.

Interesting. The only different thing, light related, that has to do with the top chunk is that the "sun" lighting is applied. So it may have to be with that. One case that would be an issue is when the lighting is applied, it won't cast it if the light on the block is higher than the light trying to be applied. This is the case you found when debugging. The strange thing is, a block shouldn't have any light value when loaded. The light is applied by the "sun" or torches.


Is there any reason not to make ./INSTALL markdown?

Ok, if none I think I'll go ahead and just do it :)

Fixed by #5576


fix weight quantization

Weight threshold calculation should always be assuming signed quantization

Add a unit tests that checks the quantizer are always signed.

Add a unit tests that checks the quantizer are always signed.

Maybe we should just add a TODO for now until an initial exporter version is out, so things like that can be easily checked.


fix #1017 and test

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

Thanks!
This is tracked as part of the internal incident in the linked issue.
The code owner will get back to you.

Thanks 1337micro for this solution.
We will merge it asap
Kind Regards,
Elena

@1337micro thanks for your contribution.
It has been included into 2e3dcc7be6f0f38238fef306d6a31cacdea2d9cd which has already been merged.
Therefore I am closing this PR.


remove unused _pin_memory property in PinMemory class

Please read through our contribution guide prior to
creating your pull request.

If you are adding a new node, ensure you read that section in the contribution guide, as it includes requirements for
functionality and testing.

Fixes #{issue number}

Not related

Changes

Add privateuse1 situation support for _pin_memory property in PinMemory class

Thanks @FightingZhen for the PR! Can you elaborate more on your use-case for this?

I assume it's to get parity with this: https://github.com/pytorch/pytorch/blob/main/torch/utils/data/_utils/pin_memory.py#L31 .
side note @divyanshk we need to do a sync for stateful_dataloader, updating our tests and code to match pytorch core's dataloader v1

@FightingZhen any ideas on how to test this? Looks like this PR in pytorch/pytorch landed without tests: https://github.com/pytorch/pytorch/commit/3460b2b7d36eb80cd1c30f0c8f6a7cc849bf339b

Starting an internal CI run to run GPU tests

Wonder if there was a change to CI runners that broke determinism, the broken tests seem to be related to controlled randomness. Either way, I ran the tests after deleting and everything seems to pass so we should be good

@andrewkho The CI looks finished, I'm not sure whether the above failed jobs is related with my modification or not, can this PR be merged? :)

@FightingZhen yup please go ahead and merge, thank you for your contribution!

@divyanshk can you help me merge this pr? thanks :)


[Bug] Dependency conditions for the last 24 hours of the dependent task did not take effect

Search before asking

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

What happened
As shown in the figure, the dependent shell node has been successfully executed, and the workflow where this dependent task is located has been outputting the log that the corresponding instance was not found

What you expected to happen
Depends on the workflow in which the task executes successfully instead of getting stuck in a running state
How to reproduce

Anything else
No response
Version
2.0.x
Are you willing to submit PR?

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

Code of Conduct

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

please help me review  @SbloodyS


back ground

hey i trying to make the background from black to transparent....were would i do that in the js files

Hi! Sorry for a really late reply on this one! I did not notice it.
You can get a transparent background by modifying the code like the top answer on this post on Stack Overflow: https://stackoverflow.com/questions/20495302/transparent-background-with-three-js


Fix github typo

Thanks, man.

So, ProtocolBuffers is already v3 and supports the Any type. I'm surprised by this unexpected interest in the repository. The gopb3any was designed before v3 to cover the cavity. Does the gopb3any make any sense now?

Maybe not, but I came across this while I was learning about protocol buffers and it did help my understanding a bit


updated readme.md

changed Resources-for-Developers to Top-Javascript-Resources-for-Developers

@all-contributors please add lucifer955

@all-contributors please add lucifer955 for Documentation


Auto-completion suggest private module

Rust-analyzer auto completion suggest private module.
Example:

Files tree of MyLib is simple : lib.rs and private_submodule.rs are sibling.
lib.rs contains mod private_submodule;
In the integration tests of MyLib:

extern crate MyLib;
[test]
fn visibility() {
    MyLib::private_submodule // This should not be suggested
}```

Duplicate of #824.


Xcode 14.3.0 is missing

Description
Our team needs Xcode 14.3.0 but it seems to be missing from the macOS 13 runner.
Below is the output from my action.
As you can see, where are asking for 14.3, but we're getting 14.3.1.

Run sudo xcode-select -switch /Applications/Xcode_"$XCODE_VERSION".app
sudo xcode-select -switch /Applications/Xcode_"$XCODE_VERSION".app
xcodebuild -version
shell: /bin/bash -e {0}
env:
SCHEME: GlobalCommunicationPlatform
SDK_VERSION: 16.4
XCODE_VERSION: 14.3
DEVICE: iPhone 14 Pro
Xcode 14.3.1
Build version 14E300c

Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[X] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Version: 20230924.1
Is it regression?
Yes. I don't know when this started happening.
Expected behavior
Xcode 14.3.0 should be executed.
Actual behavior
Xcode 14.3.1 is executed.
Due to prebuilt dependencies, we need 14.3.0.
Repro steps
Try using the following GitHub Action:
name: Run unit tests

on: [pull_request]

env:
  SCHEME: "GlobalCommunicationPlatform"
  SDK_VERSION: "16.4"
  XCODE_VERSION: "14.3"
  DEVICE: "iPhone 14 Pro"

jobs:
  test:
    runs-on: macos-13

    concurrency: # used to cancel previous runs if there is any in progress
      group: ${{ github.head_ref }}
      cancel-in-progress: true

    steps:

    - name: Select Xcode Version
      run: |
        sudo xcode-select -switch /Applications/Xcode_"$XCODE_VERSION".app
        xcodebuild -version

Hey there,
I totally get where you're coming from, but unfortunately, we can't install Xcode 14.3.0 directly. We aim to keep things up to date, so we only maintain the latest patch for each minor version of Xcode.
If you're experiencing issues with Xcode 14.3.1, I'd recommend checking if there's a specific problem you're encountering. Sometimes, it might not be related to the Xcode version itself, but rather some other factors like system configurations or dependencies.
Feel free to share more details about the problem you're facing with 14.3.1, and we'll do our best to assist you in resolving it. Maybe we can find a solution that works for you with the latest version.
Thanks for your understanding.


[wip] Disable kvstore in tests and examples

This change is

test-me-please

test-me-please

test-nightly

Coverage increased (+0.01%) to 44.14% when pulling 02a3b1c8ca4af5c63f1ff99ee8ec14f579399c8d on raybejjani:no-kvstore into 030ceacbcccf4048062db29457491122f0afc0a1 on cilium:master.

test-me-please

test-me-please

test-nightly

test-me-please

test-me-please

test-me-please

test-me-please


Pin openstack-ops to 1.3.2

Thank you for submitting a pull request to this project!
Once all check jobs have passed and the pull request has received a
sufficient number of reviews, the repository's gate jobs can be triggered by
adding a comment of :shipit: to this pull request.
When the gate jobs have completed successfully, this pull request will get
merged automatically.


[SUGGESTION] Output location (instead of file) for exporting

Example: packwiz modrinth export -ol .. would put the .mrpack in the parent directory.

You can give this low priority as I've found a way around this


Improve the encoder

Give P_np as an input to the encoder along with x_ng

And D_nc

The rationale is that the encoder can do a better job of stripping out perturbation and covariate information if it knows which perturbations and fixed effect covariates are applicable for each cell.


Race result ignored.

There are races that don't generate the results.

There are races that don't generate the results.
Then I use the same settings and everything seems to be ok.
http://clubcsr.ddns.net:8780/results
BTW, in CM everything seems to be all ok.

Are there possibilities to import and reconstruct the results from these jsons?
CM

Results files aren't written by the acServer executable if you stop if early. You must wait until the wait time has completed before you stop the assetto corsa server. There is nothing we can do to prevent this - just need to be careful when starting new events/stopping running ones.
As for reconstructing from content manager, this is way beyond the scope of server manager.


Update JSON Schema Validator Documentation with 'additionalProperties' Configuration

Description:
Response validation is not working correctly when using the following schema in the API definition.
schema:
    required:
        - Items Inventory
    type: object
    properties:
        Items Inventory:
            type: array
            items:
                type: object
                properties:
                    id_businesscom:
                        type: string
                    id_customer:
                        type: string
                    qty_purch_order:
                        type: number
                    last_purch_order:
                        type: string
                    next_delivery:
                        type: string
                    not_deliverable:
                        type: boolean
                    inventory_in_pieces_Total:
                        type: number
                    gtin:
                        type: string

The reason is that the following request is accepted by the API, even though there are some properties in the request that were not specified in the above schema.
{
    "Items Inventory": [
        {
            "id_businesscom": "234.895.AA",
            "id_customer": "",
            "qty_purch_order": 0.0,
            "last_purch_order": "",
            "next_delivery": "",
            "not_deliverable": false,
            "inventory_in_pieces_Total": 29.0,
            "inventory_in_pieces_B2B": 29.0,
            "inventory_in_pieces_B2C": 0,
            "gtin": "8099999999999"
        }
    ]
}

Solution is to use the above schema with 'additionalProperties: false' as follows, in order to prevent the acceptance of additional properties other than those specified in the schema.
schema:
    required:
        - Items Inventory
    type: object
    properties:
        Items Inventory:
            type: array
            items:
                type: object
                properties:
                    id_businesscom:
                        type: string
                    id_customer:
                        type: string
                    qty_purch_order:
                        type: number
                    last_purch_order:
                        type: string
                    next_delivery:
                        type: string
                    not_deliverable:
                        type: boolean
                    inventory_in_pieces_Total:
                        type: number
                    gtin:
                        type: string
                additionalProperties: false

Add 'additionalProperties' configuration in the documentation[1] along with a yaml format example, as this is a common requirement.
[1] https://apim.docs.wso2.com/en/4.1.0/design/api-security/api-request-response-schema-validation/json-schema-validator/#enabling-the-json-schema-validator

Example yaml - https://github.com/OAI/OpenAPI-Specification/blob/main/schemas/v3.0/schema.yaml#L36


NO-JIRA: node_controller: change newTargetNodeState assignment and rename to triggerStatusApplyError

@bertinatto  IOUs from https://github.com/openshift/library-go/pull/1821

/lgtm
/approve


Intersphinx cross-referencing does not work naively

I am improving CuPy's documentation and hit this issue...
Let's say I want to reference arange from the array API. Ideally, I would expect this should work out of box:
# conf.py
# ...
intersphinx_mapping = {
    ...
    'array_api': ('https://data-apis.org/array-api/2021.12/', None),
    ...
}
# ...

and in anywhere (rst files or docstrings) I could just do
:func:`array_api.arange`

to link to arange. Unfortunately, this does not work, nor does the global version (removing the array_api prefix). Instead I must do this following due to this repo's structure:
:func:`signatures.creation_functions.arange`

This is quite confusing and counter-intuitive. I could work with it, but I am wondering if we could do better, say re-organizing the Python stub files such that array_api.arange works, so opening this issue to collect feedbacks and suggestions.

cc @steff456

We should fix this, the signatures part should be removed.

I've been trying to fix this issue without major luck. I'll give it another check to see if I can remove the signatures and also shorten the amount of writing in a cross reference.

Also in __init__.py we need to import all functions to provide a flat namespace (except for the extension modules).

@kgryte Is there a way we can "backport" the fix #430 to v2021? It only fixed the draft version but not the latest (or 2021.12) version. Try comparing the outputs and you'll see:
python -m sphinx.ext.intersphinx https://data-apis.org/array-api/draft/objects.inv
python -m sphinx.ext.intersphinx https://data-apis.org/array-api/latest/objects.inv

@leofang Yes, this should be possible. Will see what I can do.


Add fushoku ressentiment by Imperial Circus Dead Decadence

Song Name
fushoku ressentiment
Artist Name
Imperial Circus Dead Decadence
Source
Youtube
Youtube Link
https://youtu.be/Y1BIFydkcIQ?si=w-RiC64AL1B5O2Bs
Song ID
1262293
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 94786454

reject
duplicate request, see issue 984


Minor Scss syntax issues breaking a few Vuetify Styles

_content.scss : line 11, "--wrap" should be "__wrap"
theme.scss: lines 5 & 12 have an extra space. ".application .theme--dark.#{$name}" should be ".application.theme--light.#{$name}" and .application.theme--dark.#{$name}

Hey! Sorry I've been really busy lately so the package has fallen behind the development of Veutify. I'm working on catching it back up right now. Those changes were introduced in<EMAIL_ADDRESS>so once this package catches up it should be all fixed. Just keep an eye out for the newer versions! Thanks!


baseUrl does not seem to work in source attribute

Example:

 		<WebView
 			originWhitelist={['*']}
 			mixedContentMode={'always'}
 			onMessage={onMessage}
 			javaScriptEnabled
 			automaticallyAdjustContentInsets
 			source={{
 				html: generateTheWebViewContent(),
 				baseUrl: `${url}`,
 			}}
 		/>

The baseUrl for the webview is returned as about:srcdoc

If this is true, it may be what is causing the inability to display other languages or UTF8 chars within the web version of the WebView as well.


Removed image generation inside the training step.

It was overwriting the image grid generated in on_epoch_end. I also made adversarial_loss a static method.

Thanks for the PR! I think it depends if we'd like to log the image whilst training + at the epoch end as well. Any thoughts here? An alternative would be to log with two separate names like generated_image_epoch and generated_image_step or something.

Happy to help! I think generating a sample at every step would be overkill. On my machine, I get around 17 iterations per second. You couldn't even see most of the generated images. But there is another problem. Since global_step is always 0 when calling add_image in training_step, tensorboard only show's the 0th image and never updates it. I am not sure if this is expected behavior, or a bug on the tensorboard side. In this state, you can only see updated image from on_epoch_end for a fraction of a second before it gets overwritten by the 0th training_step sample.
On a side note, here is no reason for generated_images in this section to be an instance variable.

Understood, I think it makes sense then to remove the per train step image and stick with just the final epoch image then!

There are a number of other small problems with this example. An unused import OrderedDict, use of nn.Sigmoid, which causes an error when trying to use 16-bit precision, vs no sigmoid and binary_cross_entropy_with_logits. Hyperparameters were not set in accordance with the best practices in the documentation. There is no separation between program level args, model args, and training args and it is impossible to set training flags from command line (such as --precision=16).
I have fixed all of these.  Sorry, I don't have a lot of experience contributing to an open-source project.

Make a separate PR for this, always better to make smaller PRs that fix things over time to reduce bugs appearing!

This fix was included in #4233 and it is now merged.


[Bug]: Serenity bot crashes due to excessive logs

What happened?
Serenity projects emit way too many log lines since #864, and can lead a bot to crash (not 100% confirmed).
The excessive logs are due to functions annotated with #[instrument] (spans) are set to INFO by default.
I think we can compromise by having the minimum level increased in the Shuttle log consumer for spans,
but it would be awesome if this was separately configurable with #842 (set separate span and event levels, per crate)
Version
v0.17.0
Which operating system(s) are you seeing the problem on?
Linux, In deployment
Which CPU architectures are you seeing the problem on?
x86_64, In deployment
Relevant log output
2023-05-31T02:03:10.586481275Z  INFO {shard="Shard { shard_info: ShardInfo { id: 0, total: 1 }, .. }"} serenity::gateway::bridge::shard_runner: [span] recv
2023-05-31T02:03:10.586582375Z  INFO serenity::gateway::shard: [span] do_heartbeat
2023-05-31T02:03:10.586616675Z  INFO {shard="Shard { shard_info: ShardInfo { id: 0, total: 1 }, .. }"} serenity::gateway::bridge::shard_runner: [span] recv_event

Duplicate declaration

[X] I have searched the issues and there are none like this.

I agree with this. Even though my bot isn't crashing, I am concerned about the ever expanding log file. These "span" log messages take up hundreds of lines of space in the file.
Besides, it makes hosting shuttle more expensive 😔.

Thanks for getting to the bottom of this @jonaro00! If the #842 param takes a RUST_LOG string, would that resolve this? If we can't get that over the line for the next release we could also  change the minimum level in the spans consumer as you suggested, since IIRC only tide users were affected by missing logs before #864. And we have very few tide users (I reported the initial bug).

From what I understand, the RUST_LOG only targets events by defaults, and not spans. Not sure how complex the difference is.
I'll try lowering the span log level.


minio: 2023-03-13T19-46-17Z -> 2023-03-24T21-41-23Z

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/minio/minio/releases.
meta.description for minio is: An S3-compatible object storage server
meta.homepage for minio is: https://www.minio.io/
meta.changelog for minio is: https://github.com/minio/minio/releases/tag/RELEASE.2023-03-24T21-41-23Z
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2023-03-24T21-41-23Z with grep in /nix/store/6dnyh2ks0p0vdz0y5pp3s081572zq64b-minio-2023-03-24T21-41-23Z
found 2023-03-24T21-41-23Z in filename of file in /nix/store/6dnyh2ks0p0vdz0y5pp3s081572zq64b-minio-2023-03-24T21-41-23Z

Rebuild report (if merged into master) (click to expand)

186 total rebuild path(s)

186 package rebuild(s)

First fifty rebuilds by attrpath
apacheHttpdPackages.mod_tile
apacheHttpdPackages_2_4.mod_tile
arrow-cpp
arrow-glib
cloudcompare
databricks-sql-cli
easyocr
entwine
gdal
gmt
gplates
grass
haskellPackages.hgdal
home-assistant-component-tests.environment_canada
intensity-normalization
khoj
libLAS
mapcache
mapnik
mapproxy
mapserver
merkaartor
minio
mysql-workbench
napari
octavePackages.mapping
ome_zarr
openai-full
openai-whisper
openorienteering-mapper
paraview
parquet-tools
pdal
perl534Packages.Tirex
perl536Packages.Tirex
postgresql11JitPackages.postgis
postgresql11Packages.postgis
postgresql12JitPackages.postgis
postgresql12Packages.postgis
postgresql13JitPackages.postgis
postgresql13Packages.postgis
postgresql14JitPackages.postgis
postgresql14Packages.postgis
postgresql15JitPackages.postgis
postgresql15Packages.postgis
postgresqlJitPackages.postgis
postgresqlPackages.postgis
python310Packages.apache-beam
python310Packages.aplpy
python310Packages.autofaiss

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6dnyh2ks0p0vdz0y5pp3s081572zq64b-minio-2023-03-24T21-41-23Z \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A minio https://github.com/r-ryantm/nixpkgs/archive/ed520fb76a2add7b59d45442752159dfbd4608ea.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6dnyh2ks0p0vdz0y5pp3s081572zq64b-minio-2023-03-24T21-41-23Z
ls -la /nix/store/6dnyh2ks0p0vdz0y5pp3s081572zq64b-minio-2023-03-24T21-41-23Z/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @edolstra @bachp for testing.

Do we need an backport of this to the 22.11 channel? Due to this?
https://github.com/minio/minio/security/advisories/GHSA-2pxw-r47w-4p8c

@shyim If we backport this to 22.11 we will brake existing installations as minio changed their storage formate in an incompatible way with no migration path. See https://github.com/NixOS/nixpkgs/issues/199318 for details.
Maybe we could just mark the 22.11 version as insecure or broken to make users aware of the issue.


Add labels to slider

Fixes #61
Slider is fixed for different alternatives. Can be used with marks (the steps labels) or without.
With a label that follows the Thumb, and both of the above can be automatically positioned over or below the slider
For delegation we are currently using the one in the 1st image below

Fixed: