Support "Avro Old List Structure" in Parquet reader

I'm kinda parroting back concepts here that I don't fully understand, so please bear with me.
When outputting Parquet sample data with the Nifi ParquetRecordSetWriter, data that had started life as JSON arrays was written in a format that zq (as of commit c1360a8) choked on. These two are one such example:
dns.parquet.gz
http.parquet.gz
The error message is:
$ zq -t -i parquet dns.parquet
dns.parquet: LIST element (Answers) should have 1 child

Looking the zq code for where this error came from led me to https://github.com/apache/parquet-format/blob/master/LogicalTypes.md#lists, which in turn inspired me to fiddle with the knobs in the ParquetRecordSetWriter. Through trial and error, I stumbled onto this setting:

That setting normally defaults to True, and the attachments above that zq choked on were generated when that was set to True. When I change it to False as is shown here, now the outputs are the attachments shown below, which zq reads without complaint.
dns.parquet.gz
http.parquet.gz
At some point we should investigate this further and confirm if we need to enhance the variations we support such that we might be able to read the default output from Nifi without problems.

@philrz I think the title should be "old" list structure, no?  With that setting set to false, we are not writing the old structure which means we are writing the new structure and that works.  But with that setting true, we are writing the old structure and that does not work.  Do I have that right?

@aswan: Indeed, I think you're right.

I revisited this one during an old issue scrub just to see if it maybe got magically fixed. As it turns out, it got a little worse: I confirmed via binary search that starting at Zed commit 3f05294 that's associated with the Parquet rewrite in #2227 (cc: @nwt), now when attempting to read the test data with the "old list structure" format, instead of an error message it's now a crash.
$ zq -version
Version: v0.29.0-156-g3f05294b

$ zq -f tzng -i parquet dns-old-list-structure.parquet
panic: runtime error: index out of range [0] with length 0

goroutine 1 [running]:
github.com/brimsec/zq/zio/parquetio.newType(0xc0001381b8, 0xc0000a2000)
	/Users/phil/work/zed/zio/parquetio/type.go:47 +0x30c
github.com/brimsec/zq/zio/parquetio.newRecordType(0xc0001381b8, {0xc0002c6b00, 0x19, 0x0})
	/Users/phil/work/zed/zio/parquetio/type.go:16 +0x9e
github.com/brimsec/zq/zio/parquetio.NewReader({0x1903ec0, 0xc0001381c0}, 0x0)
	/Users/phil/work/zed/zio/parquetio/reader.go:28 +0x8f
github.com/brimsec/zq/zio/detector.lookupReader({0x1903ec0, 0xc0001381c0}, 0xc0001381b8, {0x7ffeefbffa26, 0xc00021f798}, {{0x7ffeefbffa1e, 0x7}, {0x1, 0x80000, 0xa00000}, ...})
	/Users/phil/work/zed/zio/detector/lookup.go:92 +0x6b0
github.com/brimsec/zq/zio/detector.OpenFromNamedReadCloser(0x0, {0x37e1c18, 0xc0001381c0}, {0x7ffeefbffa26, 0x1e}, {{0x7ffeefbffa1e, 0x7}, {0x1, 0x80000, 0xa00000}, ...})
	/Users/phil/work/zed/zio/detector/file.go:46 +0x170
github.com/brimsec/zq/zio/detector.OpenFileWithContext({0x1911270, 0xc00013c008}, 0x203000, {0x7ffeefbffa26, 0x1e}, {{0x7ffeefbffa1e, 0x7}, {0x1, 0x80000, 0xa00000}, ...})
	/Users/phil/work/zed/zio/detector/file.go:33 +0x178
github.com/brimsec/zq/zio/detector.OpenFile(...)
	/Users/phil/work/zed/zio/detector/file.go:21
github.com/brimsec/zq/cli/inputflags.(*Flags).Open(0xc0001ffbc0, 0xc00021fe18, {0xc00013a170, 0x1, 0x1784d46}, 0x1)
	/Users/phil/work/zed/cli/inputflags/flags.go:91 +0x170
main.(*Command).Run(0xc0001ffba0, {0xc00013a170, 0x1, 0x1})
	/Users/phil/work/zed/cmd/zq/zq.go:158 +0x62b
github.com/mccanne/charm.(*instance).run(0xc000163420, {0xc00013a130, 0x1d82f40, 0xc000068738})
	/Users/phil/.go/pkg/mod/github.com/mccanne/charm@v0.0.3-0.20191224190439-b05e1b7b1be3/instance.go:53 +0x19b
github.com/mccanne/charm.(*Spec).ExecRoot(0xc0000001a0, {0xc00013a130, 0x5, 0x5})
	/Users/phil/.go/pkg/mod/github.com/mccanne/charm@v0.0.3-0.20191224190439-b05e1b7b1be3/charm.go:77 +0x68
main.main()
	/Users/phil/work/zed/cmd/zq/main.go:9 +0x5f

I've confirmed that with current Zed GA tagged v1.3.0 this issue still remains. However, the new Parquet library that should come with the changes for #4226 may magically fix this, so I've created a dependency as a reminder to check that when it's done.
$ zq -version
Version: v1.3.0

$ zq -i parquet dns-old-list-structure.parquet
panic: runtime error: index out of range [0] with length 0

goroutine 21 [running]:
github.com/brimdata/zed/zio/parquetio.newType(0x17106a0?, 0xc0000c6600?)
	/Users/phil/work/zed/zio/parquetio/type.go:46 +0x2e6
github.com/brimdata/zed/zio/parquetio.newRecordType(0x29fdfb60?, {0xc000262400, 0x19, 0x17fd9d8?})
	/Users/phil/work/zed/zio/parquetio/type.go:15 +0xa5
github.com/brimdata/zed/zio/parquetio.NewReader(0x100b7fd?, {0x29fdfb40?, 0xc0003900e0?})
	/Users/phil/work/zed/zio/parquetio/reader.go:28 +0x79
github.com/brimdata/zed/zio/anyio.lookupReader(0xc0000ca720, {0x29fdfb40?, 0xc0003900e0}, {{0x7ff7bfeff9b6, 0x7}, {0x0, 0x80000, 0x40000000, 0x0}, 0x0})
	/Users/phil/work/zed/zio/anyio/lookup.go:46 +0xaa8
github.com/brimdata/zed/zio/anyio.NewFile(0x0?, {0x29fdfb18?, 0xc0003900e0}, {0x7ff7bfeff9be, 0x1e}, {{0x7ff7bfeff9b6, 0x7}, {0x0, 0x80000, 0x40000000, ...}, ...})
	/Users/phil/work/zed/zio/anyio/file.go:54 +0x19e
github.com/brimdata/zed/zio/anyio.Open.func1()
	/Users/phil/work/zed/zio/anyio/file.go:31 +0x17a
created by github.com/brimdata/zed/zio/anyio.Open
	/Users/phil/work/zed/zio/anyio/file.go:22 +0x28e

Verified in Zed commit deea4a4.
The Parquet format that could not be read previously is now readable.
$ zq -version
Version: v1.7.0-50-gdeea4a47

$ zq -i parquet dns-old-list-structure.parquet
{_path:"dns",ts:1.521835106346483e+09,uid:"CVjl7O3baEWuwy9z7h",id_orig_h:"<IP_ADDRESS>",id_orig_p:48895,id_resp_h:"<IP_ADDRESS>",id_resp_p:53,proto:"udp",trans_id:25071,rtt:0.0008471012115478516,query:"ise.wrccdc.org",qclass:1,qclass_name:"C_INTERNET",qtype:1,qtype_name:"A",rcode:0,rcode_name:"NOERROR",AA:false,TC:false,RD:true,RA:true,Z:0,answers:["ise.wrccdc.cpp.edu","<IP_ADDRESS>"],TTLs:[3213.,42813.],rejected:false}
{_path:"dns",ts:1.521835106550864e+09,uid:"CK8Y7O3sMvrW8K3jAj",id_orig_h:"<IP_ADDRESS>",id_orig_p:25682,id_resp_h:"<IP_ADDRESS>",id_resp_p:53,proto:"udp",trans_id:32379,rtt:0.0010280609130859375,query:"ise.wrccdc.org",qclass:1,qclass_name:"C_INTERNET",qtype:1,qtype_name:"A",rcode:0,rcode_name:"NOERROR",AA:false,TC:false,RD:true,RA:true,Z:0,answers:["ise.wrccdc.cpp.edu","<IP_ADDRESS>"],TTLs:[3213.,42813.],rejected:false}
{_path:"dns",ts:1.521835107572815e+09,uid:"CWfcAe1JxOK6ySGqg1",id_orig_h:"<IP_ADDRESS>",id_orig_p:65313,id_resp_h:"<IP_ADDRESS>",id_resp_p:53,proto:"udp",trans_id:40411,rtt:0.000843048095703125,query:"pagead2.googlesyndication.com",qclass:1,qclass_name:"C_INTERNET",qtype:1,qtype_name:"A",rcode:0,rcode_name:"NOERROR",AA:true,TC:false,RD:true,RA:true,Z:0,answers:["<IP_ADDRESS>"],TTLs:[0.],rejected:false}
{_path:"dns",ts:1.521835108206925e+09,uid:"CahmAl1YJk8G8ZRkx8",id_orig_h:"<IP_ADDRESS>",id_orig_p:50444,id_resp_h:"<IP_ADDRESS>",id_resp_p:53,proto:"udp",trans_id:51310,rtt:0.0006799697875976562,query:"img03.en25.com",qclass:1,qclass_name:"C_INTERNET",qtype:1,qtype_name:"A",rcode:0,rcode_name:"NOERROR",AA:true,TC:false,RD:true,RA:true,Z:0,answers:["<IP_ADDRESS>"],TTLs:[0.],rejected:false}
{_path:"dns",ts:1.521835108259995e+09,uid:"CiXa3Vdju3WPYCYea",id_orig_h:"<IP_ADDRESS>",id_orig_p:59419,id_resp_h:"<IP_ADDRESS>",id_resp_p:53,proto:"udp",trans_id:5540,rtt:0.0011110305786132812,query:"d16u07fvuodaqr.cloudfront.net",qclass:1,qclass_name:"C_INTERNET",qtype:1,qtype_name:"A",rcode:0,rcode_name:"NOERROR",AA:false,TC:false,RD:true,RA:true,Z:0,answers:["<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>"],TTLs:[180.,180.,180.,180.,180.,180.,180.,180.],rejected:false}
{_path:"dns",ts:1.521835108275232e+09,uid:"CJbycPYKdHFUatqT8",id_orig_h:"<IP_ADDRESS>",id_orig_p:53533,id_resp_h:"<IP_ADDRESS>",id_resp_p:53,proto:"udp",trans_id:53336,rtt:0.022866010665893555,query:"e5211.dscb.akamaiedge.net",qclass:1,qclass_name:"C_INTERNET",qtype:28,qtype_name:"AAAA",rcode:0,rcode_name:"NOERROR",AA:false,TC:false,RD:true,RA:true,Z:0,answers:["2600:1406:3:383::145b","2600:1406:3:380::145b"],TTLs:[20.,20.],rejected:false}
{_path:"dns",ts:1.521835108472163e+09,uid:"CHEGm52ZEuDizHUbla",id_orig_h:"<IP_ADDRESS>",id_orig_p:56577,id_resp_h:"<IP_ADDRESS>",id_resp_p:53,proto:"udp",trans_id:5534,rtt:0.0009570121765136719,query:"hm.baidu.com",qclass:1,qclass_name:"C_INTERNET",qtype:1,qtype_name:"A",rcode:0,rcode_name:"NOERROR",AA:true,TC:false,RD:true,RA:true,Z:0,answers:["<IP_ADDRESS>"],TTLs:[0.],rejected:false}
{_path:"dns",ts:1.521835108492593e+09,uid:"C8EaBf3Vmkqgvu9JJj",id_orig_h:"<IP_ADDRESS>",id_orig_p:64234,id_resp_h:"<IP_ADDRESS>",id_resp_p:53,proto:"udp",trans_id:53213,rtt:0.0006020069122314453,query:"img03.en25.com",qclass:1,qclass_name:"C_INTERNET",qtype:1,qtype_name:"A",rcode:0,rcode_name:"NOERROR",AA:true,TC:false,RD:true,RA:true,Z:0,answers:["<IP_ADDRESS>"],TTLs:[0.],rejected:false}
{_path:"dns",ts:1.521835109548778e+09,uid:"CCIFlX3wAQaekXmWs2",id_orig_h:"<IP_ADDRESS>",id_orig_p:26388,id_resp_h:"<IP_ADDRESS>",id_resp_p:53,proto:"udp",trans_id:20882,rtt:0.0011548995971679688,query:"pkg.cdn.trueos.org",qclass:1,qclass_name:"C_INTERNET",qtype:28,qtype_name:"AAAA",rcode:0,rcode_name:"NOERROR",AA:false,TC:false,RD:true,RA:true,Z:0,answers:["pkg.pcbsd.scaleengine.net","pcbsd-pkg.secdn.net","2001:470:1:63a::3:81"],TTLs:[77305.,173.,173.],rejected:false}
{_path:"dns",ts:1.521835109553831e+09,uid:"CiBlLh3i6wWc34BaRa",id_orig_h:"<IP_ADDRESS>",id_orig_p:37584,id_resp_h:"<IP_ADDRESS>",id_resp_p:53,proto:"udp",trans_id:50067,rtt:0.0007789134979248047,query:"safebrowsing.google.com",qclass:1,qclass_name:"C_INTERNET",qtype:1,qtype_name:"A",rcode:0,rcode_name:"NOERROR",AA:false,TC:false,RD:true,RA:true,Z:0,answers:["sb.l.google.com","<IP_ADDRESS>"],TTLs:[21558.,258.],rejected:false}

Thanks @nwt!


How to get event logs

Hello,
I would like to get event logs via HTTP API and tried below string, but it does not work.
http://<IP_ADDRESS>/event
What is a correct way to get event logs including CoAP message logs?
Thanks.

Keep in mind the HTTP/REST API of Leshan Server Demo is just a demo and this API is not really design to be reused.
Anyway, http://your.leshan.server.demo/event/[ep=clientEndpoint]  is a server-sent event API. So you should respect this "protocol" (e.g. Accept should be "text/event-stream")

I just tested it with curl and it works for me :
curl http://localhost:8080/event/ep\=myendpoint -H Accept:text/event-stream
I do an observe request on /3/0/13 which is observable on my demo device and I get this periodically :
event: COAPLOG
data: {"timestamp":1523020038355,"incoming":true,"type":"NON","code":"2.05","mId":3069,"token":"[414f10ae40a236c2]","options":"Content-Format: \"application/vnd.oma.lwm2m+tlv\" - Observe: 201","payload":"Hex:c40d5ac77106"}

event: NOTIFICATION
data: {"ep":"myendpoint","res":"/3/0/13","val":{"id":13,"value":"2018-04-06T15:07:18+02:00"}}

I close this one as it works for me.
Feel free to reopen it if needed.


Determine whether validation can and should be added to the PDF

Can we add field validation to the PDF?
Is it necessary if we have validation in the HTML at the point of data entry?
Would adding validation to the PDF create new problems such as needing to add code to handle situations where the PDF validation fails?

Isn't the PDF effectively readonly? If not, my understanding was that whatever they type in the new PDF won't get reflected in the QR code anyway?


Update with latest icy_engine

Latest wasn't building for me - requires https://github.com/mkrueger/icy_engine/pull/1
Also snuck in a fix for apt-get install

It's tricky to build.

Software is a nightmare to deploy these days. It seems I can't really target any platform 100%.
Maybe with the exception of osx on my machine where I set up the code signing.


Uncaught ImportError in _types.py line 11

Aider version: 0.65.1
Python version: 3.11.10
Platform: Linux-5.15.0-122-generic-x86_64-with-glibc2.31
Python implementation: CPython
Virtual environment: No
OS: Linux 5.15.0-122-generic (64bit)
Git version: git version 2.25.1
An uncaught exception occurred:
Traceback (most recent call last):
  File "aider", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "main.py", line 887, in main
    coder.run()
  File "base_coder.py", line 758, in run
    self.run_one(user_message, preproc)
  File "base_coder.py", line 801, in run_one
    list(self.send_message(message))
  File "base_coder.py", line 1179, in send_message
    litellm_ex = LiteLLMExceptions()
                 ^^^^^^^^^^^^^^^^^^^
  File "exceptions.py", line 55, in __init__
    self._load()
  File "exceptions.py", line 58, in _load
    import litellm
  File "__init__.py", line 22, in <module>
    from litellm.proxy._types import (
  File "_types.py", line 11, in <module>
    from pydantic import BaseModel, ConfigDict, Extra, Field, Json, model_validator
ImportError: cannot import name 'model_validator' from 'pydantic' (/home/tom/.pyenv/versions/3.11.10/lib/python3.11/site-packages/pydantic/__init__.cpython-311-x86_64-linux-gnu.so)

Fixed it with updating pydantic:
➜  x_twitter_composio git:(main) ✗ pip install -U pydantic
Requirement already satisfied: pydantic in /home/tom/.pyenv/versions/3.11.10/lib/python3.11/site-packages (1.10.19)
Collecting pydantic
  Using cached pydantic-2.10.2-py3-none-any.whl.metadata (170 kB)
Requirement already satisfied: annotated-types>=0.6.0 in /home/tom/.pyenv/versions/3.11.10/lib/python3.11/site-packages (from pydantic) (0.7.0)
Requirement already satisfied: pydantic-core==2.27.1 in /home/tom/.pyenv/versions/3.11.10/lib/python3.11/site-packages (from pydantic) (2.27.1)
Requirement already satisfied: typing-extensions>=4.12.2 in /home/tom/.pyenv/versions/3.11.10/lib/python3.11/site-packages (from pydantic) (4.12.2)
Using cached pydantic-2.10.2-py3-none-any.whl (456 kB)
WARNING: Error parsing dependencies of gym: Expected matching RIGHT_PARENTHESIS for LEFT_PARENTHESIS, after version specifier
    opencv-python (>=3.) ; extra == 'all'
                  ~~~~^
WARNING: Error parsing dependencies of torchsde: .* suffix can only be used with `==` or `!=` operators
    numpy (>=1.19.*) ; python_version >= "3.7"
           ~~~~~~~^
Installing collected packages: pydantic
  Attempting uninstall: pydantic
    Found existing installation: pydantic 1.10.19
    Uninstalling pydantic-1.10.19:
      Successfully uninstalled pydantic-1.10.19
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
supabase 0.7.1 requires python-semantic-release==7.32.1, which is not installed.
gotrue 0.5.4 requires httpx<0.24.0,>=0.23.0, but you have httpx 0.27.2 which is incompatible.
gotrue 0.5.4 requires pydantic<2.0.0,>=1.9.1, but you have pydantic 2.10.2 which is incompatible.
spacy 3.0.6 requires pydantic<1.8.0,>=1.7.1, but you have pydantic 2.10.2 which is incompatible.
spacy 3.0.6 requires typer<0.4.0,>=0.3.0, but you have typer 0.13.1 which is incompatible.
supabase 0.7.1 requires httpx<0.24.0,>=0.23.0, but you have httpx 0.27.2 which is incompatible.
postgrest-py 0.10.3 requires httpx<0.24.0,>=0.23.0, but you have httpx 0.27.2 which is incompatible.
postgrest-py 0.10.3 requires pydantic<2.0.0,>=1.9.0, but you have pydantic 2.10.2 which is incompatible.
fastai 2.5.3 requires torch<1.11,>=1.7.0, but you have torch 2.5.1 which is incompatible.
thinc 8.0.3 requires pydantic<1.8.0,>=1.7.1, but you have pydantic 2.10.2 which is incompatible.
aider-chat 0.65.1 requires numpy==1.26.4, but you have numpy 2.1.3 which is incompatible.
aider-chat 0.65.1 requires scipy==1.13.1, but you have scipy 1.14.1 which is incompatible.
unstructured-client 0.28.0 requires pydantic<2.10.0,>=2.9.2, but you have pydantic 2.10.2 which is incompatible.
unstructured-client 0.28.0 requires python-dateutil==2.8.2, but you have python-dateutil 2.9.0.post0 which is incompatible.
dstack 0.18.28 requires pydantic<2.0.0,>=1.10.10, but you have pydantic 2.10.2 which is incompatible.
langchain 0.3.8 requires numpy<2,>=1.22.4; python_version < "3.12", but you have numpy 2.1.3 which is incompatible.
dspy-ai 2.4.9 requires joblib~=1.3.2, but you have joblib 1.4.2 which is incompatible.
llama-index-core 0.12.1 requires pydantic<2.10.0,>=2.7.0, but you have pydantic 2.10.2 which is incompatible.
knowledge-storm 1.0.0 requires numpy==1.26.4, but you have numpy 2.1.3 which is incompatible.
langchain-community 0.3.8 requires numpy<2,>=1.22.4; python_version < "3.12", but you have numpy 2.1.3 which is incompatible.
langchain-community 0.3.8 requires SQLAlchemy<2.0.36,>=1.4, but you have sqlalchemy 2.0.36 which is incompatible.
pydantic-duality 1.2.4 requires pydantic<2.0.0,>=1.9.2, but you have pydantic 2.10.2 which is incompatible.
Successfully installed pydantic-2.10.2


Troubleshoot upstream git issues

Its great we can set the upstream git via the Keptns Bridge or the UI - but - there is not much of troubleshooting details when setting hte upstream fails. The only thing the user sees is "Git Upstream URL could not be set". and that is true when the URL is wrong or not reachable, when the username is wrong or the token invalid
We need better error messaging - both as response to the action of updating the project as well as in the uniform screen in the log section. If the configuration service has an upstream but it cant reach it we should highlight this as an error

I need to extend this request.
It is also possible that an already defined Git Upstream is broken, e.g: tokens became invalid, url no longer reachable ..
This is a critical error because the configuration service cannot deliver any resource any more as it constantly runs into errors when requesting fiels bc the git upstream is not reachable
we had a situation where the complete keptn project was unusable but it was not obvious to the user as there was no error indication except in the configuration-service logs which said
Could not add upstream repository while updating project dynatrace: failed to set upstream: Error executing command git push --set-upstream http://kxxxxxxx/keptn/dynatrace.git master: exit status 128 remote: invalid credentials from <IP_ADDRESS> fatal: Authentication failed for 'http://xxxxx/keptn/dynatrace.git/' Keptn requires an uninitialized repo

Decision by the team
The configuration-service and shipyard-controller should report internal errors via the /event endpoint.
UI changes will be implemented in #tbd


Leaks on Xcode 8.3

I use Instruments to check leaks.
It is OK on Xcode 8.2.1，but it will leaks on Xcode8.3.
My English is poor，hope you understand.

Related to #363 note that this is an instruments bug but if you watch your app's memory over a long period of time it will never grow.

Closing this as I don't believe this is an issue and it's misleading to anyone looking at the issue tracker!

Thanks for your answer!


fix(a11y): resolve sidebar, find, toolbar missing aria-expanded and aria-controls state

In testing, screen readers such as JAWS have trouble understanding the expanded state of the buttons that expand hidden menus due to lacking aria-expanded attribute. Also, given that the buttons do not contain the controlled/shown element, they should also define the aria-controls attribute with associated element id per https://www.w3.org/TR/wai-aria-1.1/#aria-expanded
This fixes adds these requirements for the sidebar, find, and secondary toolbar buttons.

/botio-linux preview

Looks good to me with an amended commit message.

@Snuffleupagus per @timvandermeij commit message amended. Cheers!

Thank you for improving this!


chore(STONEO11Y-99): Alerting rule for Pods Not Ready

Created a new alerting rule for pods not ready.
Added related unit test cases.

/test

@yftacherzog @hmariset @avi-biton Does anyone know why some checks haven't been completed for this PR? Is it showing half success and half still checking?

@yftacherzog @hmariset @avi-biton Does anyone know why some checks haven't been completed for this PR? it is showing half success and half still checking.

Not sure. There's some sort of leftover legacy app that was there as well. It might be that this is the one that did not complete. In that case, it should not block the merge. Our tests seem to be working as far as I can tell.

@yftacherzog @hmariset @avi-biton Does anyone know why some checks haven't been completed for this PR? it is showing half success and half still checking.

Not sure. There's some sort of leftover legacy app that was there as well. It might be that this is the one that did not complete. In that case, it should not block the merge. Our tests seem to be working as far as I can tell.

Understood. Ty

@gbenhaim Do you know what might be the issue here with the additional required test?

/test


[FEAT] Show buffered video

Could be nice to see a "buffered" progress bar as well on the seek bar, Like how Youtube shows how much of the video is actually loaded on the web browser.

yes, I do agree with you ( @Spiderjockey02 )

I was actually able to successfully implement this. I'll add the code to this comment on the weekend.


Handle some edge cases?

Example, running on host without "free" command ends with Warning/Deprecations.
$ php php-fpm-tuner.php
sh: 1: free: not found
PHP Deprecated:  preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /var/www/php-fpm_tuner/php-fpm-tuner.php on line 17

Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /var/www/php-fpm_tuner/php-fpm-tuner.php on line 17
PHP Warning:  Undefined variable $freeMemory in /var/www/php-fpm_tuner/php-fpm-tuner.php on line 21

Warning: Undefined variable $freeMemory in /var/www/php-fpm_tuner/php-fpm-tuner.php on line 21
sh: 1: ps: not found
PHP Deprecated:  preg_match_all(): Passing null to parameter #2 ($subject) of type string is deprecated in /var/www/php-fpm_tuner/php-fpm-tuner.php on line 25

Deprecated: preg_match_all(): Passing null to parameter #2 ($subject) of type string is deprecated in /var/www/php-fpm_tuner/php-fpm-tuner.php on line 25
pm.max_children = 0
start_servers = 0
min_spare_servers = 0
max_spare_servers = 0

What's the free replacement on that system? What the system is?

Docker container ;-)
I think about handle like:
if shell_exec "command free" === false then echo "Free command is not available on this system. Cannot tune FPM."

Alpine?

Debian 12 Slim
https://hub.docker.com/layers/library/php/8.2-fpm/images/sha256-dab0a1456cbcce4a7b19b541474a7a77cd1de8a5998fa3aab2ee52dee132b86e?context=explore

Could be replaced with /proc/meminfo result
        if (preg_match('~MemFree:\s+(\d+)\s+~', shell_exec('cat /proc/meminfo'), $matches)) {
            $freeMemory = $matches[1] / 1024;
        }

Yes. Would you like to prepare a pull request?


Trim Docker images again for production images

In #2347 we introduced changes leading to faster incremental dockerfile builds but also to bigger resulting images.
We should probably use the version with smaller resulting images for production and the other version for development.
@bobrik

:+1:


Complete <=1.12 block support

This is a 'super issue' covering all work for pre-flattening blocks.
Feel free to try and knock something off this list!
Blocks in 1.12 and prior are stored with numeric IDs rather than names. For example, blocks with an ID of 3 are dirt blocks. This doesn't fit with the current Chunk and Block in fastanvil. Since 1.12 is no longer receiving updates, we translate the old numeric IDs into their Block equivalents on demand, rather than pollute the current Chunk/Block types with 1.12 logic.
Along with the numeric IDs, there is also 4 extra bits of information called the data value that tell you more about a given block. For example, wooden logs have a numeric ID of 17, and the two smallest bits determine if it is oak, spruce, birch or jungle logs. There is also another wooden log block with ID 162 for the other log types.
Relevant code is in fastanvil/src/java/pre13, in particular the pre13_block_names::modern_block function.
The Minecraft Wiki contains all the necessary information in it's Pre-flattening page.
TODO basics:

[x] Basic block IDs

TODO Data value extraction:

[ ] Wood Planks
[ ] Stone
[ ] Dirt
[ ] Saplings
[ ] Water and Lava
[ ] Sand
[x] Wood
[x] Leaves
[ ] Wool, terracotta, stained Glass and carpet
[ ] Torches and Redstone Torches
[ ] Slabs
[ ] Fire
[ ] Sandstone
[ ] Red Sandstone
[ ] Beds
[ ] Grass
[ ] Flowers
[ ] Large Flowers
[ ] Piston
[ ] Piston Extension
[ ] Stairs
[ ] Redstone Wire
[ ] Daylight Sensor
[ ] Crops
[ ] Farmland
[ ] Banner
[ ] Door
[ ] Rails
[ ] Ladders, Furnaces, Chests, Trapped Chests
[ ] Sign
[ ] Dispenser and Dropper
[ ] Hopper
[ ] Levers
[ ] Pressure Plates
[ ] Buttons
[x] Snow
[ ] Cacti and Sugar Canes
[ ] Jukebox
[ ] Pumpkins and Jack o'Lanterns
[ ] Cake
[ ] Redstone Repeater
[ ] Redstone Comparator
[ ] Trapdoors
[ ] Stone Bricks
[ ] Prismarine
[ ] Sponge
[ ] Brown and red mushroom blocks
[ ] Pumpkin stem and Melon stem
[ ] Vines
[ ] Fence Gates
[ ] Nether Wart
[ ] Brewing Stand
[ ] Cauldron
[ ] Nether Portal
[ ] End Portal Frame
[ ] Cocoa
[ ] Tripwire Hook
[ ] Tripwire
[ ] Cobblestone Walls
[ ] Flower Pots
[ ] Heads
[ ] Block of Quartz
[ ] Coal
[ ] Anvil
[ ] Observer
[ ] Maps
[ ] Structure Block
[ ] Chorus Flower
[ ] End Rod
[ ] Glazed Terracotta

Working through some of these.  Created a macro for the coloured blocks which seems to work (from some testing in the Rust playground), assuming this is ok?
macro_rules! coloured_block {
    ($a:expr, $b:expr) => {
        {
            let col = match $b & 0b1111 {
                0 => "white",
                1 => "orange",
                2 => "magenta",
                3 => "light_blue",
                4 => "yellow",
                5 => "lime",
                6 => "pink",
                7 => "gray",
                8 => "light_gray",
                9 => "cyan",
                10 => "purple",
                11 => "blue",
                12 => "brown",
                13 => "green",
                14 => "red",
                15 => "black",
                _ => unreachable!(),
            };
            Block {
                name: format!("minecraft:{col}_{}", $a),
                encoded: format!("minecraft:{col}_{}|", $a),
                archetype: BlockArchetype::Normal,
            }
        }
    }
}
// ...
        "carpet" => {
            coloured_block!("carpet", data_value)
        }

Great, I've merged the PR you made and ticked off soem of the things in the list. Cheers!


other option for convenience

Could you please add these features to be available in the command palette, if it's easy to implement :

check for update for non-beta plugin
update non-beta plugin
update non-beta theme
access changelog for beta and non-beta plugin

Thank you very much for everything.

Sorry for the long delay in responding. For now, I am not going to take this plugin down that path. Updates can have bugs and users should be aware of what is being updated.  I also think about this from a security standpoint. I don't want to bypass Obsidian's approach to plugins too much.
Having said that, you can add any plugin to BRAT and it will update it.  So instead of registering a plugin through the community plugin browser, do so directly in BRAT and it will auto-update.


HIVE-27351: Hive metastore metrics is not getting initialised even if metrics is enabled

What changes were proposed in this pull request?

Use configured value of hive.service.metrics.hadoop2.component
Why are the changes needed?

hive metasore metrics is not getting enabled
Does this PR introduce any user-facing change?

No
How was this patch tested?

Build the hive after the change, replaced related jar, started metastore verified that metrics sink is started

I think it needs to be retriggered.

where is the PR for master branch?

where is the PR for master branch?
This issue is already fixed in master branch. HIVE-19989 fixed the issue.
I have skipped recordName change from "general-metadata" to "General" because this change will introduce backward incompatibility in a minor version, other than this, changes in this PR are exactly same as  HIVE-19989

Looks failed test cases are not related to this PR change.


Cannot read property 'func' of undefined

Any idea about this issue?

it is because the old version is using the built in Proptypes that was removed in react 16. This repo is already updated, but the npm version is not. So you will have to download it via this repo.

I have updated the npm package. Let me know if the issue isn't resolved.

Hi,SiDevesh the package update works fine, now it is working.
Thanks!!!


Adrian p setup.js

In case that you already have a .env

what does this do exactly?

It's a very simple edit. Because I was trying to run the script and nothing happened. I explained on the chat.


pug support

Thanks for creating this awesome project. I'm a pug lover but unfortunately it seems not working with pug. It would be even more fantastic combined with pug. The long class names in pug could turn into line-break attributes thus make it more readable.
Does there any plan to support pug?
Many thanks.

https://github.com/antfu/unocss/tree/main/packages/extractor-pug

Was about to file an issue saying that UnoCSS classes only work in Pug templates if they've already been used in HTML templates, but @unocss/extractor-pug is the solution! Thank you @antfu 🙏


More panic output:
goroutine 20 [running]:
net/http.(*conn).serve.func1(0xc8200f2980)
	/home/dgryski/work/src/cvs/go/src/net/http/server.go:1389 +0xc1
github.com/martine/gocairo/cairo._cgoCheckPointer0(0x89fbe0, 0xc8200de8a0, 0xc8204b4f90, 0x1, 0x1, 0x876840)
	??:0 +0x4d
github.com/martine/gocairo/cairo.(*Surface).WriteToPNG(0xc820178058, 0x7faf32cfc160, 0xc8200f0cc0, 0x0, 0x0)
	/home/dgryski/work/src/cvs/gocode/src/github.com/martine/gocairo/cairo/cairo.go:63 +0x202
...

Thanks for the report!
It's because I pass one of these through C:
type writeClosure struct {
	w   io.Writer
	err error
}

and I guess that's no longer allowed.
I'm not exactly sure how they expect me to wrap an API like this
http://cairographics.org/manual/cairo-PNG-Support.html#cairo-surface-write-to-png-stream
in Go 1.6.  Apparently I can't use any Go pointers in callbacks?  But functions like this are pretty common in C code, so there must be some way.

Probably need to ask Ian on golang-nuts..  I'm sure lots of people will be hit by this.

I got a comment from Ian himself!  The design doc suggests this pattern:

One safe approach is: Go code that wants to preserve funcs/pointers stores them into a map indexed by an int. Go code calls the C code, passing the int, which the C code may store freely. When the C code wants to call into Go, it passes the int to a Go function that looks in the map and makes the call. An explicit call is required to release the value from the map if it is no longer needed, but that was already true before.

I will write a patch this weekend hopefully.

Were you able to find a solution?

I talked to Ian separately.  The fix unfortunately is to use a map of pending writes.  I haven't had time to work on this but I hope to get to it soon.
See
https://github.com/martine/gocairo/blob/master/cairo/util.go#L39
E.g.
var closures = map[int]*writeClosure{}
var closuresLock sync.Mutex

// Then when calling into the C API from our wrapper, something like:
closuresLock.Lock()
closures[x] = &writeClosure{...}
closuresLock.Unlock()
C.cairo_whatever(..., x)
closuresLock.Lock()
delete(closures, x)
closuresLock.Unlock()
...

and similarly on the other side we look up the closure with a key.

This is what Ian suggested anyway.  Pretty gross.

Is that conversation public?  I don't understand how a mutex would change things.  (The mutex is needed for concurrent map access, but the writeClosure would still contain a Go pointer.)

Yes, but instead of passing the writeClosure to C, you pass the key (an integer) to the entry in the map.

How would you reference the map from C?

Please let me know if 6a6533955940440d0f265d97843462a03f516674 (on master) fixes the problem.  I wrote it blind (I don't have Go 1.6 locally) but I think it should work.

Oops, and to answer the earlier question, no the conversation wasn't public.  But the design doc from when they made this change had a sentence or two about doing this.

Yup; works here.  Thanks!

You're the first user of this library I've heard from, so please feel free
to make feature requests etc. if you have any!

Everything works here, too.  Thank you, @martine!

@martine The only feature I'm missing is svg output. I'll file a bug for that.


How to create a custom tokenizer. By Extending FTS5

i have this issue too

This is not possible at the moment. It would require additional java and JNI code to support this.

This is not possible at the moment. It would require additional java and JNI code to support this.

How's it going?


Feature Flag - moving to install section

Consider adding the enabling section into the install/upgraade section of the docs.

Closing this issue because it is addressed by https://github.com/rancher/docs/pull/2114


A dialog that allows the creation of 'releases' in a completely manual way

Demo
simplescreenrecorder-2023-01-25_22.47.59.webm
General Notes and Questions:

In the demo, you can see that no cases are visible. This is because I give the release-creating user a "Member" role. Should this be something else, like "DataOwner"?
I changed the appearance of the vertical tabs because I found the previous appearance confusing :sweat_smile:
I remember @andrewpatto said the dialog should ask for PIs' email addresses, but this discussion says to prefer the term "applicant" or "data recipient" (which is more consistent with the rest of Elsa): https://github.com/umccr/elsa-data/discussions/35
I might be confounding a release with an application, both in the UI and in my variable names, so I'd be glad to hear feedback on that

This PR closes #79.

Overall PR looks spot on to me. Only issue outstanding is the one about PossibleUser v real User.
And there is a bit of work we need to do on user permission modelling (i.e. DataOwner v PI etc) - but I think we need a bigger picture discussion on that with AG - so wouldn't hold up this PR.


Not cleaning up on cancel

It seems like when a job is cancelled, either via manual cancel or though timeout, dependant services (like db, redis, etc), and sometimes the main test process if its stuck, get just left behind on the test hosts (this understandably severely impacts memory availability and such)

I believe this is tied to https://github.com/buildkite/agent/issues/389. Once that is fixed, this will stop happening.

This should be fixed on the most recent stack thanks to the new beta agent having this fixed too.


add optional version number to constructor

This PR allows the user of this library to provide a version number when constructing an ElementalClient so all calls to the api will have that version number included.
For example, calling:
const client = new ElementalClient('https://elemental-server.example.com', { 'X-API-Key': 'aSecretKey' }, 'v<IP_ADDRESS>');
client.presets().create({...}).then(console.log);

Would make a POST request to https://elemental-server.example.com/api/v<IP_ADDRESS>/presets and log the output to the console.
This allows the user of this library to upgrade the software on an Elemental server without fear of API changes breaking existing workflows.

Codecov Report

Merging #40 into master will increase coverage by 0.48%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #40      +/-   ##
==========================================
+ Coverage   98.15%   98.64%   +0.48%
==========================================
  Files           4        4
  Lines         217      221       +4
  Branches       33       35       +2
==========================================
+ Hits          213      218       +5
+ Misses          4        3       -1

Impacted Files
Coverage Δ

lib/resource.js
100% <100%> (ø)
:arrow_up:

lib/live-event.js
100% <100%> (ø)
:arrow_up:

lib/main.js
98.91% <100%> (+1.08%)
:arrow_up:

Continue to review full report at Codecov.

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

I like the idea of checking for this. At present, I believe we're relying on the server to return an error and then we're handling it like any other server error.
Maybe it makes sense to do a sanity check in the constructor though? Perhaps making a request to /system_status.xml to check that the server is online and the version, if provided, is compatible?


NullReferenceException triggered when setting ParseACL to new ParseObject.

Getting a NullReferenceException when I am trying to set the ParseACL to an instantiated ParseObject.
The following line causes the issue for me in the Parse .NET SDK 1.6.2:
var po = new ParseObject("Table");
po.ACL = new ParseACL(ParseUser.CurrentUser);
This code is run after user is authenticated. ParseUser.CurrentUser is not null.

Confirmed bug. PR coming shortly.

As a temporary work around until the next SDK version is released, you can create a concrete subclass of ParseObject, and register that, and then the ACL, ObjectId, CreatedAt, and UpdatedAt properties will work properly once again.

Can you give an example of the fix...


nvmedit nvm2json fails with "TypeError: Cannot read property 'lwr' of undefined"

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
What causes the bug?
npx @zwave-js/nvmedit nvm2json --in .\NVM_2022-02-08.bin --out nvm.json
What do you observe?
TypeError: Cannot read property 'lwr' of undefined
at nvmObjectsToJSON (C:\Users\cdhaw\AppData\Roaming\npm-cache_npx\20300\node_modules@zwave-js\nvmedit\build\convert.js:149:35)
at nvmToJSON (C:\Users\cdhaw\AppData\Roaming\npm-cache_npx\20300\node_modules@zwave-js\nvmedit\build\convert.js:552:17)
at Object.handler (C:\Users\cdhaw\AppData\Roaming\npm-cache_npx\20300\node_modules@zwave-js\nvmedit\build\cli.js:41:40)
What did you expect to happen?
Successful execution of this command.
Device information
Manufacturer: Zooz
Model name: ZST10-700
Node ID in your network: 1
How are you using node-zwave-js?

[X] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[ ] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version:
nvmedit : 8.11.4
zwavejs2mqtt: 6.5.0
zwave-js: 8.11.2
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
No, it never worked anywhere
If yes, where did it work?
No response
Attach Driver Logfile
TypeError: Cannot read property 'lwr' of undefined
at nvmObjectsToJSON (C:\Users\cdhaw\AppData\Roaming\npm-cache_npx\20300\node_modules@zwave-js\nvmedit\build\convert.js:149:35)
at nvmToJSON (C:\Users\cdhaw\AppData\Roaming\npm-cache_npx\20300\node_modules@zwave-js\nvmedit\build\convert.js:552:17)
at Object.handler (C:\Users\cdhaw\AppData\Roaming\npm-cache_npx\20300\node_modules@zwave-js\nvmedit\build\cli.js:41:40)

Interesting... Can you send me the .bin file so I can check it out? Either post here or via e-mail.


Licensing requirements

Hi, I would like to use the YoloV4 part of your repo code for production code. Are there any licensing requirements for this?

Hello,
Thanks for concerning my project.
I have just added MIT License to the project.
As in MIT License, you can use the project freely.
Good luck.

Hi. Thanks a lot for the help!


added support for kqueue

Hi,
I added a little ternary switch in order to use Kqueue on BSD platforms.

An even better solution was committed in 98855fea634aa1c427c18841cf14fa3777201c4b.
Closing.


Add prefix option to input component

What
Add a prefix option to the input component
Why
Users were entering data which was unusable, i.e entering text when we desired numbers. This change will help us indicate to users how we would like them to input data.
Visual Changes
BEFORE

AFTER

Trello

The prefix (and suffix) should have a minimum width which is the height of the input and the text aligned centre. Currently, the text is quite constrained and difficult to read if you have visual impairments.
For example:

NB. In the example screenshot, I have used min-height: 40px and text-align: center.

Hi Simon, I was able to achieve the desired effect by being more explicit with the padding in the styling. Is this better?


Fix link to example

The previous link to example is broken
What this PR does:
The previous link to examples is broken

@olegsu I am really sorry about not looking at this earlier, quite frankly idk how I missed it. Sorry!
I think this link was already updated so I will close this PR, but if you find any other issues please open another PR, I won't miss it :) Thanks!


<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^15.5.4 || ^16.1.1 but none is installed. You must install peer dependencies yourself.

<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^15.5.4 || ^16.1.1 but none is installed. You must install peer dependencies yourself.
pls update the dependency

Duplicate of #2105.


Enable text selection on header cells

This PR enables text selection on Tabulator headers by adding extra CSS. Since the table currently does not support sorting or reordering, this change does not interfere with any existing header functionality.
Resolves #16

Tested and works! Thanks a lot!
Am excited for this to be merged and released, @adamviola!


Review and Add feedback on Blog page.

Blog page

Improve Ui for blog detail page, full width of image, 5% container margin for text
Comment textarea below button.
comment at below and top we have form for comment.
Blog card improvement some place like button is not showing.
Change the color of already liked blog to red.


python311Packages.license-expression: 30.1.0 -> 30.1.1

Diff: https://github.com/nexB/license-expression/compare/refs/tags/v30.1.0...v30.1.1
Changelog: https://github.com/nexB/license-expression/blob/v30.1.1/CHANGELOG.rst
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.


Add Topics

You might get more traffic if you add some topics to the project (and your other ones!).

Thanks for the suggestion! Added.


Is Privacy Proxy source code open source?

I realize we are talking about chrome and not chromium, but in your policies do you plan to make the sources of the server code in which it runs available to the opensource community?
thank you for your reply

I realise that I am Mr. Nobody, but more than a month later, even an answer like 'No, it won't be' would be fine.
Sorry, I don't mean to troll, but I didn't expect this from google.

I realize we are talking about chrome and not chromium, but in your policies do you plan to make the sources of the server code in which it runs available to the opensource community?
thank you for your reply

If your intention with open sourcing backend is security or privacy, thats obviously usless since google can use any code they want.
I dont know what use a google chrome proxy could have otherwise for the open source community

Hi, sorry for the delay in replying here. The majority of the software here is open-source as part of the Chromium and Envoy Proxy projects, but some components are closed-source.

The majority of the software here is open-source as part of the Chromium and Envoy Proxy projects, but some components are closed-source.

Thank you for your reply, but I meant the server counterpart necessary for operation, the one directly connected to the publicly visible client part in chromium.
Anyway, I get the hint, so no, it is not public. a pity in my opinion.
@eastoid the aim is for learning and for testing and possible use in chromium as well without using google resources, since the various related configurations can be modified without rebuild.


enable stopping of web server without using a signal

In go-micro/server/server.go, function Run, I find this code to stop the server:
	ch := make(chan os.Signal, 1)
	signal.Notify(ch, syscall.SIGTERM, syscall.SIGINT, syscall.SIGKILL)
	log.Logf("Received signal %s", <-ch)

This code relies on syscall.SIGTERM and might interact with other parts of the application.
Is it possible to expose a Stop function, which will send to the channel directly.
In the short run we are looking for a very simple fix.
For example a new run function with a signature:
RunWithStopChannel(ch <-channel)

where we have access to the channel will do for us.

If you're looking to signal the service to stop, please see the context cancellation example https://github.com/micro/examples/blob/master/shutdown/main.go

Thanks a lot for the quick response. Just to make sure we are talking about the same thing.
In go micro there is a micro server (the example you sent) and the web service (the example I sent).
Would the solution apply to the webservice as well?

The sample code you've provided is just the server package within go-micro. If you look at the top level micro service code you'll see it's using that server. If you're talking about the go-web repo that's entirely different.

Yes, thank you. Talking about  go-web. That's the wrong place I guess.


Pass token string as prop doesnt work

Html File
<manager name="MyName" token="{{ token }}"></manager>

With vue-loader I created a custom component (below), which I use in my html file (above)
Component
<template>

{{ token }}

{{ name }}

</template>

I pass a token (a very long string) as a prop to my component. It seems, that Vue cannot handle such large strings, because the output of token is empty. For short string I got no problems - the name prop is shown.
Output

MyName

name="`MyName"
or name="MyName" ？
On Mon, Oct 19, 2015, 19:50 Simon<EMAIL_ADDRESS>wrote:

With vue-loader I created a custom component (below), which I use in my
html file (above)

I pass a token (a very long string) as a prop to my component. It seems,
that Vue cannot handle such large strings, because the output of token is
empty. For short string I got no problems - the name prop is shown.

MyName

``
—
Reply to this email directly or view it on GitHub
https://github.com/vuejs/vue/issues/1443.

That ` was a typo!

Sorry, I replied to the old issue email sent automatically sent from github...

The isssue is kind of solved.
In my original code is use accessToken as prop name. In that case, it couldn't set the property, but if I do it like in my example, it does work.

http://rc.vuejs.org/guide/components.html#camelCase_vs-_kebab-case


use Node.js 16

When using the action lately, I get the following warning in my GitHub workflows:
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: Sibz/github-status-action, Sibz/github-status-action
Could you please update the project so that it uses Node.js 16?

please update the project to nodejs 16

@Sibz

https://github.com/Sibz/github-status-action/pull/36

I really appreciate @Sibz making this action available, and I use it across several projects. Would love to get this updated so we can continue to use it!

Sorry to bump, but I think this should be closed. This being open gave me the false impression that this was still an issue 😅

It looks like changes for this were merged with #36.  Is it possible to get a release with this new node16 version?

@mjhipp @mackaybeth sorry for delays, I've been out of action for a few months. Just catching up on things now, however I am a bit overwhelmed so can't get back to this right away.

For those waiting to use the Node16, you can use this version while we wait for this release.

Can we get a Node 16 release please?

@aayusharyan Can we get a Node 16 release please?

You can use this one here V2 while waiting for the V1 release...

For those waiting to use the Node16, you can use this version while we wait for this release.

I tried but got this error:

Error: Unable to resolve action<EMAIL_ADDRESS>unable to find version `v1.1.9`

@kasir-barati, there is no version 1.1.9, the current version is 1.1.13
You can see the existing versions here: https://github.com/guibranco/github-status-action-v2/releases

At this point we are on to needing Node 20. While updating for node 16 last year, and Node 20 this month, I have replaced a few outdated actions with a simple gh cli call. For this action, you would replace this:
  - name: Update commit status using marketplace action
    uses: Sibz/github-status-action@v1
    with:
      authToken: ${{secrets.GITHUB_TOKEN}}
      context: 'Test run'
      description: 'Passed'
      state: 'success'
      sha: ${{github.event.pull_request.head.sha || github.sha}}

with this:
    - name: Update commit status using gh cli api
      shell: bash
      env:
        GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
      run: |
        gh api "/repos/${{ github.repository }}/statuses/${{ github.event.pull_request.head.sha || github.sha }}" \
          -f state="success" \
          -f context="Test run" \
          -f description="Passed"


ensure master-dist retains Travis dist file commit history

changes Travis to build to merge master and new dist build into master-dist branch, as opposed to removing existing build history
fixes #281

Looks good to me

I was hoping we didn't need to merge, but that's fine. Thanks for trying it.
LGTM

@dlabrecq would you like a similar PR in core p.f.?

@dlabrecq would you like a similar PR in core p.f.?

Yes please. I believe we will have the same issue there.

@dlabrecq roger that.


Future of Duo-Strength  - add old  UI site

Hi Toran
Since  Duo-Strength  does not work with the new UI
Please  add https://www-internal.duolingo.com/learn to the list of sites

@alexseyk Thanks for bringing this to my attention, I'll add this now and get a release out as soon as I can: v2.1.0

Published v2.1.0 to all the stores. Approved for Opera, pending review for Chrome and Firefox.

Firefox now approved.

https://www-internal.duolingo.com/ now redirects to https://www.duolingo.com/learn. 😢
Is there any other workaround to still access the old Duolingo interface and thus use this great extension?

If you use Firefox.... block https://www.duolingo.com/learn then https://www-internal.duolingo.com/  or https://join.duolingo.com/  will show you the tree.


[Core] Add instance attributes

Concepts describe high level details but we need a way to describe specific instances of that particular concept.
It can be an external structure but somehow accessible by the Knowledge base.

It can be made but I don't think it is really needed, using inheritance is possible to create instances copying all the attributes from a previous concept.


refactor(storage): do not aware of keyspace in state table

Signed-off-by: Bugen Zhao<EMAIL_ADDRESS>What's changed and what's your intention?
With the prefixed_range introduced in #3217, we can make the cell-based table & state table not aware of keyspace prefix with ease.
Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)

Close #3212

May conflict with https://github.com/singularity-data/risingwave/pull/3238.

make Keyspace::prefixed_key private?

We're still using it in write_batch.rs. Maybe we can make this a submodule of keyspace so that we can make it private.


Fix/294 media manager styling

Q
A

Branch
master

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Tests pass?
yes

Fixed issues
chameleon-system/chameleon-system#294

License
MIT

Fixes some issues and styling in pickImageMode and adds the breadcrumb

Thanks @pixeljunkie


clipper2: 1.2.2 -> 1.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/AngusJohnson/Clipper2/releases.
meta.description for clipper2 is: Polygon Clipping and Offsetting - C++ Only
meta.homepage for clipper2 is: https://github.com/AngusJohnson/Clipper2
Updates performed

Version 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 1.2.3_DLLs in filename of file in /nix/store/mx8rl6vy8nkds95syh327pvily4dj8m4-clipper2-1.2.3_DLLs

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
clipper2

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mx8rl6vy8nkds95syh327pvily4dj8m4-clipper2-1.2.3_DLLs \
  --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 clipper2 https://github.com/r-ryantm/nixpkgs/archive/38fb90366e332ea3582170c494b47b5e1a89ec00.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/38fb90366e332ea3582170c494b47b5e1a89ec00#clipper2

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mx8rl6vy8nkds95syh327pvily4dj8m4-clipper2-1.2.3_DLLs
ls -la /nix/store/mx8rl6vy8nkds95syh327pvily4dj8m4-clipper2-1.2.3_DLLs/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.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

clipper2

Maintainer pings
cc @cadkin for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/AngusJohnson/Clipper2/releases.
meta.description for clipper2 is: Polygon Clipping and Offsetting - C++ Only
meta.homepage for clipper2 is: https://github.com/AngusJohnson/Clipper2
Updates performed

Version 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 1.3.0 with grep in /nix/store/7gvws1gkhjp7i1ws55rlxs5s0wkh03mb-clipper2-1.3.0
found 1.3.0 in filename of file in /nix/store/7gvws1gkhjp7i1ws55rlxs5s0wkh03mb-clipper2-1.3.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
clipper2

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7gvws1gkhjp7i1ws55rlxs5s0wkh03mb-clipper2-1.3.0 \
  --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 clipper2 https://github.com/r-ryantm/nixpkgs/archive/1cc547974e925ab61042c7caeb5e2b5a38224704.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1cc547974e925ab61042c7caeb5e2b5a38224704#clipper2

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7gvws1gkhjp7i1ws55rlxs5s0wkh03mb-clipper2-1.3.0
ls -la /nix/store/7gvws1gkhjp7i1ws55rlxs5s0wkh03mb-clipper2-1.3.0/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.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

clipper2

Maintainer pings
cc @cadkin for testing.

@cadkin Hi, wonder if it is possible to merge this. manifold (openscad-unstable dependency) requires this update to fix some bugs.

can we make this ready and merge it?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3507


Screen coordinates of a control on a design surface

How can I find the screen coordinates of a control on a design surface (given the control’s name)? I need solutions for every design surface - XAML, Winforms, Maui, etc.

@MillerMark For XAML we have a separate github repo for designer extensibility related questions: https://github.com/microsoft/xaml-designer-extensibility
I encourage you to ask your question(s) there. There won't be a solution for Maui though, since we don't even have a designer for Maui.

Closing since this is an issue for the designer extensibility repo.


Provide a sensor for "next evu event"

A minutes timer number or timestamp with the next evu event.
If the evu is active its the time when the evu ends.
If the evu is not active its the time when the next evu starts.
For example my evu time slots are:

10:43-12:46
16:42-18:44

Example values:

At 10:00 the value is 43 minutes.
At 11:00 the value is 106 minutes.
At 13:00 the value is 222 minutes.

in my case, the evu is only applicable on monday till friday. but the EVU attributes (especially "time until next evu event") is also count on sunday and saturday. is it possible to add a day related evu state?


Link to Slack in README.md has expired

Clicking the link in the README shows:

@fpgmaas https://join.slack.com/t/delta-users/shared_invite/zt-2nbwhrv7l-Kn~N4kPn7YfhGRUTJDyZYw

@dennyglee @rtyler  can you create a permanent invite link?

@ion-elgreco i wish but it's really expensive to pay for Slack Business/Premium due to our size.  I try to remind myself to renew the Slack weekly so apologize for missing that.  It should be updated now.


AR refresh() with relations

What steps will reproduce the problem?
$video = Video::find()->andWhere(['id' => $videoId])
->with(['videoType',  'videoThumbnails'])
->one();

// DATA IS GOOD
$videoArray = $video->toArray([], ['videoType', 'videoThumbnails']);

// do some video manipulations

// now refresh video object
$video->refresh();

// NO RELATIONS!
$videoArray = $video->toArray([], ['videoType', 'videoThumbnails']);

//WORKAROUND
$video->videoType;
$video->vdeoThumbnails;

// DATA IS GOOD NOW
$videoArray = $video->toArray([], ['videoType', 'videoThumbnails']);

What is the expected result?
repopulate existing/fetched relations
What do you get instead?
nothing
Additional info
| ---------------- | ---
| Yii version      | 2.0.13

I think the issue is in #15522

@samdark Shouldn't we have tests for this? I don't see how this is related to #15522.

it is not related
my point is currently all relations get unset on refresh at BaseActiveRecord.php
    protected function refreshInternal($record)
    {
        if ($record === null) {
            return false;
        }
        foreach ($this->attributes() as $name) {
            $this->_attributes[$name] = isset($record->_attributes[$name]) ? $record->_attributes[$name] : null;
        }
        $this->_oldAttributes = $record->_oldAttributes;
        $this->_related = [];  // <--- RESET HERE
        $this->afterRefresh();

        return true;
    }

Currently I don't see any easy solution for this usecase because information about relations (from active query) are not passed to active record, so repopulate relations with proper conditions looks impossible.
Maybe you should ignore my issue and just make some kind of warning.
Currently , in whole project I have only 2 places with such workaround.
regards


Error on List function of Consumption Usagedetails

import path 'services/consumption/mgmt/2018-03-31/consumption'
--pseudo code
List, err := usageClient.List(ctx, expand, filter, skipToken, &top, "")
if err != nil {
	log.Println("Error In Getting Usage List : ")
	log.Println(err.Error())
	log.Println("")
	break
}

getting this error after first iterations using next token.
using top value as 1000
consumption.UsageDetailsClient#List: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="400" Message="id query parameter is not a valid Guid (Request ID: 80c46708-2afa-4d1a-b155-f1c692bd0fa6)"

My internal subscription doesn't have access to this functionality so I can't repro this yet.

Any update on this? I'm getting similar error when trying to request consumption data with more than 1000 results. Fails on the second page (page.Next()) with following error:
consumption.UsageDetailsClient#listNextResults: Failure responding to next results request: StatusCode=400 -- Original Error: autorest/azure: error response cannot be parsed: "The request is badly formed."  error: invalid character '<' looking for beginning of value

We're working on getting a repro still, sorry for the delay!
cc @parisa-naeimi

Any updates here ? What was the resolution or workaround ?

Sadly there hasn't been any resolution yet.  :(  If you have a repro it would help out to set AZURE_GO_SDK_LOG_LEVEL to Debug and provide the complete request/response so we can investigate.  Note that this requires go-autorest version v10.15.0 or greater to work.

Enabled the debug logs.
User-Agent: Go/go1.10.3 (amd64-darwin) go-autorest/v11.4.0 Azure-SDK-For-Go/v25.1.0 consumption/2019-01-01
Authorization: **REDACTED**
(2019-02-25T14:23:56.6790713-08:00) INFO: RESPONSE: 400 https://management.azure.com//subscriptions/<subscriptionId>//providers/Microsoft.Consumption/usageDetails?%24expand=properties%2FmeterDetails&%24filter=properties%2FusageStart+eq+%272019-02-01T00%3A00%3A00Z%27+and+properties%2FusageEnd+eq+%272019-02-14T00%3A00%3A00Z%27&%24skiptoken=317C313030307C313030307C46616C73657C547275657C30&api-version=2019-01-01
Expires: -1
Session-Id: cbb0bdba-61c9-467c-92b4-e607b8e352c3
Odata-Version: 4.0
X-Ms-Correlation-Request-Id: e0a5d84d-9427-40a8-b9dd-9cee7d34b4ed
X-Ms-Client-Request-Id: dd96dc44-f717-4129-bf3e-0538db98f29c
X-Content-Type-Options: nosniff
X-Ms-Routing-Request-Id: WESTUS:20190225T222356Z:e0a5d84d-9427-40a8-b9dd-9cee7d34b4ed
Date: Mon, 25 Feb 2019 22:23:56 GMT
Cache-Control: no-cache
Content-Type: application/json; odata.metadata=none
X-Ms-Request-Id: b3daed2c-f032-4ad6-9d98-b76ccda277df
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Ms-Ratelimit-Remaining-Subscription-Reads: 11996
Pragma: no-cache
Content-Length: 126
Access-Control-Allow-Origin: *
{"error":{"code":"400","message":"id query parameter is not a valid Guid (Request ID: b3daed2c-f032-4ad6-9d98-b76ccda277df)"}}
ERRO[0011] Error during usage listconsumption.UsageDetailsClient#List: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="400" Message="id query parameter is not a valid Guid (Request ID: b3daed2c-f032-4ad6-9d98-b76ccda277df)"
exit status 255```

PS: I have noticed that the skiptoken seems to be a little different than what it was returning last week. The response of my first call (without the skiptoken ofcourse) is returning first 1000 results correctly but the second call with the skiptoken set is returning the above error.

The skiptoken is being parsed from the Response().NextLink.
For eg, skiptoken is being set to "317C313030307C313030307C46616C73657C547275657C30" for the Response().NextLink below:
https://management.azure.com/subscriptions/<subscriptionID>/providers/Microsoft.Consumption/usageDetails?$expand=properties/meterDetails&$filter=properties/usageStart eq '2019-02-01T00:00:00Z' and properties/usageEnd eq '2019-02-14T00:00:00Z'&api-version=2019-01-01&sessiontoken=9:12577158&$skiptoken=317C313030307C313030307C46616C73657C547275657C30&skiptokenver=v1&id=d36f096f-7044-4c4e-8238-35e8a12da276

Let me know if you need more info.

Thanks this is helpful.  Can you please post the code you're using?

Code snippet below:
usageClient := consumption.NewUsageDetailsClient(*res.SubscriptionID)

        usageClient.Authorizer = authorizer

        filterStr := "properties/usageStart eq '2019-02-01T00:00:00Z' and properties/usageEnd eq '2019-02-14T00:00:00Z'"

    next:
        ctx := context.Background()
        usageList, err := usageClient.List(ctx, "/subscriptions/"+*res.SubscriptionID+"/", "properties/meterDetails", filterStr, skiptoken, nil, "")
        if err != nil {
            logrus.Error("Error during usage list", err)
            os.Exit(-1)
        }

        skiptoken = ""
        if usageList.Response().NextLink != nil {
            if *usageList.Response().NextLink != "" {
                splitStrRegexp := regexp.MustCompile("\u0026")
                splitStr := splitStrRegexp.Split(*usageList.Response().NextLink, -1)
                for _, v := range splitStr {
                    skiptokenRegexp := regexp.MustCompile("skiptoken=")
                    skiptokenStr := skiptokenRegexp.Split(v, -1)
                    if len(skiptokenStr) > 1 {
                        skiptoken = skiptokenStr[1]
                    }
                }
            }
        }

        printValues(usageList.Values())

        for true {
            if skiptoken == "" {
                break
            }
            goto next
        }

Another code snippet that I tried out today using NextWithContext(). I am not sure if I am using it the right way though. It returned a different error.
usageClient := consumption.NewUsageDetailsClient(*res.SubscriptionID)

        usageClient.Authorizer = authorizer

        filterStr := "properties/usageStart eq '2019-02-01T00:00:00Z' and properties/usageEnd eq '2019-02-14T00:00:00Z'"
        fmt.Println("filterStr=", filterStr)

        ctx := context.Background()
        usageList, err := usageClient.List(ctx, "/subscriptions/"+*res.SubscriptionID+"/", "properties/meterDetails", filterStr, skiptoken, nil, "")
        if err != nil {
            logrus.Error("Error during usage list", err)
            os.Exit(-1)
        }

        printValues(usageList.Values())

        for usageList.NotDone() {
            err = usageList.NextWithContext(ctx)
            if err != nil {
                fmt.Println(err, "Could not go to move to next result page")
                return
            }
            printValues(usageList.Values())
        }

The request and response as below:
Content-Type: application/json
User-Agent: Go/go1.10.3 (amd64-darwin) go-autorest/v11.4.0 Azure-SDK-For-Go/v25.1.0 consumption/2019-01-01
Authorization: **REDACTED**
(2019-02-26T17:50:22.7493430-08:00) INFO: RESPONSE: 400 https://management.azure.com/subscriptions/<subscriptionid>/providers/Microsoft.Consumption/usageDetails?$expand=properties/meterDetails&$filter=properties/usageStart eq '2019-02-01T00:00:00Z' and properties/usageEnd eq '2019-02-14T00:00:00Z'&api-version=2019-01-01&sessiontoken=22:12415896&$skiptoken=317C313030307C313030307C46616C73657C547275657C30&skiptokenver=v1&id=7f41b78c-486e-453e-92c5-f912e31a6091
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Wed, 27 Feb 2019 01:50:22 GMT
Content-Length: 311
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii">

Bad Request

HTTP Error 400. The request is badly formed.

consumption.UsageDetailsClient#listNextResults: Failure responding to next results request: StatusCode=400 -- Original Error: autorest/azure: error response cannot be parsed: "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01//EN\"\"http://www.w3.org/TR/html4/strict.dtd\">\r\n<TITLE>Bad Request</TITLE>\r\n<META HTTP-EQUIV=\"Content-Type\" Content=\"text/html; charset=us-ascii\">\r\n
Bad Request
\r\n

HTTP Error 400. The request is badly formed.
\r\n\r\n" error: invalid character '<' looking for beginning of value Could not go to move to next result page

Error occurred when i was trying to get usage of enterprise account using csp rest api.  got correct values when  i used rest api specified in below  link
https://docs.microsoft.com/en-us/rest/api/billing/enterprise/billing-enterprise-api-usage-detail

Error occurred when i was trying to get usage of enterprise account using csp rest api. got correct values when i used rest api specified in below link
https://docs.microsoft.com/en-us/rest/api/billing/enterprise/billing-enterprise-api-usage-detail

^Not using for an enterprise account.

@edesai thanks I was going to suggest you use the methods on the returned page type to iterate over the results.
It looks to me that the problem here is the query params in the returned URL for the next link aren't properly encoded.  In the consumption/models.go file could you replace the existing method with this version.
func (udlr UsageDetailsListResult) usageDetailsListResultPreparer(ctx context.Context) (*http.Request, error) {
	if udlr.NextLink == nil || len(to.String(udlr.NextLink)) < 1 {
		return nil, nil
	}
	u, err := url.Parse(*udlr.NextLink)
	if err != nil {
		panic(err)
	}
	q, err := url.ParseQuery(u.RawQuery)
	if err != nil {
		panic(err)
	}
	u.RawQuery = q.Encode()
	return autorest.Prepare((&http.Request{}).WithContext(ctx),
		autorest.AsJSON(),
		autorest.AsGet(),
		autorest.WithBaseURL(u.String()))
}

This will properly encode the query parameters and will prove/disprove my theory.

That did the work! Thanks. So how does this work .. will a new version come out with the fix ?

So to summarize I think there are several issues here.

The List API taking just a skip token isn't sufficient (you need to pass the ID and likely the skip token version as well).
Parsing the skip token out of the next URL is not user-friendly (there might be some ways to simplify this, like getting the skiptoken value directly from the HTTP response object but it's still not ideal).
The nextLink URL provided by the service doesn't encode the query params so it's effectively useless.
I would like to avoid having to always round-trip the nextLink URL like this as most services return a valid URL so I will follow up with the service team about getting it fixed.  I'll also bring up the other points to see what can be done about them.
As for a more immediate fix it will depend on how fast the service team can turn around fixing the nextLink URL.  I'll discuss with my team and follow up.

Im having the same issue using the python SDKs. (ConsumptionManagementClient)
b'{"error":{"code":"400","message":"id query parameter is not a valid Guid (Request ID: ab3d3db2-42d3-40db-bea3-e99d1cb692ec)"}}'
What was the solution so that I can try to reproduce it?

Already two years. I still get this problem. Any update on this?

I'm sending a PR for this bug: https://github.com/Azure/azure-sdk-for-go/pull/12641
fix id missing for consumption

1. when requesting the usage detail api with consumption package, it's ok
for the first request, but it will failed when request for the next page
with only skiptoken. The return error:
{"error":{"code":"400","message":"id query parameter is not a valid Guid
    (Request ID: xxxxxxx
    consumption.UsageDetailsClient#List: Failure responding to request:
    StatusCode=400 -- Original Error: autorest/azure: Service returned
    an error. Status=400 Code="400" Message="id query parameter is not a
    valid Guid (Request ID: xxxxxxx
Add another parameter id from the nextLink will fix this bug.

2. this error also happens in the "try it" document page:
https://docs.microsoft.com/en-us/rest/api/consumption/usagedetails/list#code-try-0
it will respond the same error if didn't provide the id parameter

Sorry for the delay, I have a fix to encode the query parameters in autorest.WithBaseURL().

The query params fix is in module autorest/v0.11.8 if somebody can try it out.

@jhendrixMSFT It doesn't works for me. Still respond the same error:
consumption.UsageDetailsClient#List: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="400" Message="id query parameter is not a valid Guid (Request ID: 95ba4e09-0a08-4c1a-ae43-d6a23e15e8cb)"
my related go.mod
require (
¦   github.com/Azure/azure-sdk-for-go v46.4.0+incompatible
¦   github.com/Azure/go-autorest/autorest v0.11.8 // indirect
¦   github.com/Azure/go-autorest/autorest/azure/auth v0.5.2
¦   github.com/Azure/go-autorest/autorest/to v0.4.0 // indirect
¦   github.com/Azure/go-autorest/autorest/validation v0.3.0 // indirect
)

@hotsnow thanks for trying it out.  Would you mind stepping through the code to see if the query params aren't getting encoded for some reason?  Maybe there's something else at work here.  I don't have a repro of this at present (working on it).

Per offline conversation with @hotsnow this has been resolved.
I've opened an issue about the missing skiptokenver and id query params in the swagger for manual paging.
https://github.com/Azure/azure-rest-api-specs/issues/11351


[CommandPropertyToAttributeRector] Also get other attribute values (fix #305)

The unit test fails because argument key are removed, should we add these keys by default what is the best practice for this?
phpstan
fails because ```  src/Rector/Class_/CommandPropertyToAttributeRector.php:35

'#Class cognitive complexity is 63, keep it under 50#'``` any idea how i can make this less complex?

Thank you very much!

Any chances to get this shipped in the next release?

The unit test fails because argument key are removed,

The keys should be kept. The code should not be changed at all and refactor() should return null.

any idea how i can make this less complex?

This means a service should be extracted

Any chances to get this shipped in the next release?

Not sure when i'm able to finish this up, i only need to make the class less complex still

You can create another service, and inject into construct method, then use the service

You can create another service, and inject into construct method, then use the service

I created a CommandHelper class to move some functions let me know if that is okay

Let's merge it so we have faster feedback 👍

Thank you @JohJohan


Add init for custom selectors only

I do not want to enable FancySelect for all select elements on the page. How can I enable it for a specific selector, for example select[id="custom"]?
Respectively, all styles should to affect only elements with the specified selector, not all standard select elements. Add this feature please.

Set the global FancySelectAutoInitialize variable to false before including the FancySelect JavaScript to your page:
<script> const FancySelectAutoInitialize = false; </script>
<script src="fancyselect.min.js"></script>

Then call FancySelect.replace() with your desired element as argument:
const target = document.getElementById('my-custom-element');
FancySelect.replace(target);

Thanks, it works perfectly. What if I need to do this for multiple elements on a page?


Add new zip and zipToObject methods for arrays

Description
This PR introduces new zip and zipToObject methods, similar to Lodash's zip and zipObject methods, respectively. Funny enough, Lodash's zip literally just calls unzip under the hood for some weird reason. As a result, there's no point in having a separate unzip alias.
This PR also skips implementing zipWith, as it could be easily implemented by reducing the result of zip using .reduce(). If there's a really strong want for it I can always circle back and try to implement it, though the pattern Lodash uses for it (a rest parameter followed by a callback) isn't a great pattern in TypeScript.
Breaking: this PR renames the existing zip function for objects to the much more appropriate name assign!!
Checklist

[x] Changes are covered by tests if behavior has been changed or added
[x] Tests have 100% coverage
[x] If code changes were made, the version in package.json has been bumped (matching semver)
[x] If code changes were made, the yarn build command has been run and to update the cdn directory

Resolves
If the PR resolves an open issue tag it here. For example, Resolves #34
Resolves #154

@rayepps You mentioned 10.x being breaking, so I bumped the version of this to 10.0.0. Let me know if you don't wanna make that jump yet lol.

Hey @Nickersoft v10 is perfect 👍 also, this PR is perfect 🎉 great typing (simple & correct), simple function implementations, all the doc strings are updated, great simple tests. I really appreciate it!!!!
Just had one comment about possibly extending the zipToObject function, let me know what you think about that and then ✅

@rayepps Good to land? 😃

Ah right, forgot about it being a new major version – cool! I'll keep my eye peeled for a new release

Hey @Nickersoft I'm putting the v10 release together 🚀 but in preperation I did some cleanup and it caused conflicts 😬 apologies for that. So I can merge it for v10, can you

pull master and rebase (should be quick and easy, you'll end up deleting the cdn/.version file)
reset the version in package.json so there is no change to it in this PR

Again, apologies, still working out all the kinks on process 😅

@rayepps Sorry just realized I didn't reset the package version when I merged with master – should be all set now! Excited to see this go out 🥳


NameError: name 'long' is not defined When Using Python 3

When using Python 3 instead of Python 2.7 the following error appears when invoking the grandfatherson.dates_to_delete function:
File "/usr/local/lib/python3.4/dist-packages/grandfatherson/__init__.py", line 220, in dates_to_delete
    firstweekday=firstweekday, now=now)
  File "/usr/local/lib/python3.4/dist-packages/grandfatherson/__init__.py", line 204, in dates_to_keep
    firstweekday=firstweekday, now=now)
  File "/usr/local/lib/python3.4/dist-packages/grandfatherson/__init__.py", line 172, in to_keep
    filters.Minutes.filter(datetimes, number=minutes, now=now) |
  File "/usr/local/lib/python3.4/dist-packages/grandfatherson/filters.py", line 55, in filter
    if number < 0 or not isinstance(number, (int, long)):
NameError: name 'long' is not defined

The current recommendation when migrating from Python 2.7 to Python 3 is to use an int instead of a long.

bump

In python 2 (on a 64bit platform), isinstance(int(2**66), int) == False. However, since the minimum filter is seconds, I think we can limit people to that bound in python 2.7.

Should be fixed in version 1.3: https://pypi.python.org/pypi/GrandFatherSon/1.3

fuk yes 👍  I can now use your awesome package directly via pip
thank you


fix: enable intergation test

Enabling integration testing workflow just for testing.

Hi @bonyfusbouvet, @vehecap ,
The issue has been resolved now. Please approve the pull request.


Add Gitter.im badge to ReadMe

Codecov Report

Merging #472 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #472   +/-   ##
=======================================
  Coverage   80.11%   80.11%
=======================================
  Files          37       37
  Lines        2509     2509
  Branches      155      155
=======================================
  Hits         2010     2010
  Misses        453      453
  Partials       46       46

Continue to review full report at Codecov.

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


Add newline character for c

Is it possible to add new line character for debug print in C ?
fprintf(stderr, "DEBUGPRINT[1]: .....: keys=%d", keys);
become
fprintf(stderr, "DEBUGPRINT[1]: ....: keys=%d\n", keys);

Thank you for spotting this, this was a mistake. Fixed now I think - let me know if you see any issues.


KeyError: 'tabs_stack'

Describe the bug
context
Hi, Sphinx Tabs friends! I'm trying to convert my docs to use sphinx-tabs instead of sphinx-inline-tabs because I think your tabs are rendered in a slightly more user-friendly way.
FYI, I'm building Sphinx using nox and venv environments and that might possibly be a factor.
When I try to build my Sphinx docs with your extension (running version 3.3.1), I get a build error with a KeyError exit code (see error message below).
expectation
The Sphinx docs build should succeed, not fail. I seem to be able to do this exact same process on a different doc set using the same tools, so I don't know why I only get this bug in this environment.
bug
I get this error message when the Sphinx build fails:
Exception occurred:
  File "/my-directory/lib/python3.10/site-packages/sphinx_tabs/tabs.py", line 143, in run
    tabs_id = self.env.temp_data["tabs_stack"][-1]
KeyError: 'tabs_stack'
The full traceback has been saved in /tmp/sphinx-err-m8zbbkt6.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!

problem
This is a problem for people building Sphinx docs because the build fails. Basically this one error prevents me from building my entire doc set. I'm also not super great at parsing and reading Python yet, so I don't know how to troubleshoot it myself. I'll get there.
Is it maybe some sort of packaging dependency that is having an error or is it a code problem?
Reproduce the bug
I can provide the error log if you need!
List your environment
I use the latest Sphinx that builds my docs using nox inside of a virtual environment (venv).

Hi @barbaricyawps, please could you provide a link to your project docs or a minimal example in markdown/rst that causes the same error?

Please also review the example usage in our documentation, as it differs from sphinx-in line-tabs. It's possible that you're not wrapping 'tab' directives in a '' tabs' directive.

Thanks so much for your reply! Here's the project that I'm hoping to switch from inline tabs to sphinx-tabs: https://gitlab.com/saltstack/open/docs/salt-install-guide
I'll double-check. We use sphinx-tabs on another project: https://gitlab.com/saltstack/open/docs/salt-user-guide
Because of that repo, I definitely know I can get it to work with the correct syntax. I'll double-check, though!

Sorry, both of those links are to the second project that uses sphinx-tabs.
If the syntax does appear to be correct, please can you point me to an example using sphinx-tabs that is failing to build?

No worries 😊
Thanks for sharing the additional links! I'm afraid I can't really help without seeing an example of the sphinx-tabs rst that reproduces the error (don't worry about the rendered version). You could share:

A link to your working branch, if you push it up to the remote on GitLab
A GitHub Gist containing an example of the sphinx-tabs rst that is failing to build
A pasted code block here, showing sphinx-tabs rst that is failing to build

Note that for 2 or 3 you'll need to ensure that specific example doesn't build on it's own (i.e. When building only that page, with all other pages deleted). In doing this, you'll probably find the troublesome rst anyways 😁
I don't think this is causing your issue, but just to note that the sphinx-tabs guidance in the last set of links above could be made more concise using the 'code-tab' directive instead of nesting 'code-block' inside of a standard 'tab'.

I'm assuming that the syntax error was found here, so closing the issue for now. Please feel free to comment again if the issue remains and you'd like further help


Selector of Gateway custom resource is not bound by namespace

Bug description
The documentation for Gateway custom resources states:

selector: One or more labels that indicate a specific set of pods/VMs on which this gateway configuration should be applied. The scope of label search is restricted to the configuration namespace in which the the resource is present. In other words, the Gateway resource must reside in the same namespace as the gateway workload instance.

However, this is not the case. The default istio-ingressgateway workload in the istio-system that comes with the Helm chart setup can be configured with Gateway resources in any other namespace.
I would consider this a security risk as it violates the namespace isolation. However, this bug/feature is even used in the bookinfo example application:

https://istio.io/docs/examples/bookinfo/#determine-the-ingress-ip-and-port
https://raw.githubusercontent.com/istio/istio/release-1.4/samples/bookinfo/networking/bookinfo-gateway.yaml

Expected behavior
Gateway custom resources should only configure workloads in the same namespace.
Steps to reproduce the bug
Install istio with the helm chart. Create a test namespace and create a Gateway in that namespace that defines a HTTP server on port 12345, use selector istio: ingressgateway:
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: testgateway
  namespace: test
spec:
  selector:
    istio: ingressgateway
  servers:
  - hosts:
    - '*'
    port:
      name: http
      number: 12345
      protocol: HTTP

Notice that the istio-ingressgateway pods in the istio-system namespace will start to listen on port 12345.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.7", GitCommit:"6c143d35bb11d74970e7bc0b6c45b6bfdffc0bd4", GitTreeState:"clean", BuildDate:"2019-12-16T16:32:54Z", GoVersion:"go1.12.14", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.9-eks-c0eccc", GitCommit:"c0eccca51d7500bb03b2f163dd8d534ffeb2f7a2", GitTreeState:"clean", BuildDate:"2019-12-22T23:14:11Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

$ helm version
version.BuildInfo{Version:"v3.0.2", GitCommit:"19e47ee3283ae98139d98460de796c1be1e3975f", GitTreeState:"clean", GoVersion:"go1.13.5"}

$ istioctl version --remote
client version: 1.4.0
control plane version: 1.4.0
data plane version: 1.4.0 (7 proxies)

How was Istio installed?
With helm.
Environment where bug was observed (cloud vendor, OS, etc)
AWS EKS 1.14.

I don't understand,if this is a bug,that mean we should deploy every loadbalanced gateway for every namespace insteaded of a share ingress gateway like regular ingress controller did,that sounds ridiculous since it eally kind of wasted of public ip. Or did I misunderstanding something?

That sounds not conveniences if compare to how we configure ingress resource.why we need to isolated Gateway resources in istio ingress workload namespace.

I think this is a bug, we just haven't find any bandwidth to address. I remember this was mentioned mulitple times in networking WG meeting. not sure if anyone is working on that actively though...
@rshriram might know a bit more though.

There is a flag to switch behavior; PILOT_SCOPE_GATEWAY_TO_NAMESPACE. The problem is we will break 99% of users if we change this in a release, even our demos rely on this scoping

@howardjohn Thanks for the pointer.
So we do have the flag PILOT_SCOPE_GATEWAY_TO_NAMESPACE to enforce the namespace boundary. The questions is can we make it true by default. Changing it in 1.7 will break our customers if they don't follow the instructions. I think in 1.7, we should update the security best practice to instruct enabling PILOT_SCOPE_GATEWAY_TO_NAMESPACE, and change our demos so that they are not misleading. We may change the default behavior in 1.8.

I would like to point out the Ingress behaves the same way as the default (cross namespace). A common workflow is for app teams to deploy Ingress+certs in their own namespace, without access to ingress-namespace. Granted, this doesn't even work in Istio today since the certs aren't searched cross-namespace..

I think the best security practice is enforcing that the ingress gateway pod, ingress gateway certs and gateway configuration should all be in the same namespace. This requires setting PILOT_SCOPE_GATEWAY_TO_NAMESPACE=true today, and I hope this can be the default in 1.8.
With that said, we may offer an option for cross-namespace Ingress gateway. This breaks the security boundary between namespaces, while offering convenience for single-tenant use cases (I'm seeing customers asking for it). This requires ingress gateway to load ingress gateway keys and certs from different namespaces, which we don't support today.

I think its useful to look at other providers:

ingress-gce - just Ingress. There is no LB running in cluster. Read secrets from Ingress namespace (only)
ingress-nginx - just Ingress. There is a deployment running in cluster. Read secrets from Ingress namespace (only). No plans to change - see https://github.com/kubernetes/ingress-nginx/issues/2170
cert-manager - integrates with Ingress and creates secret in the Ingress namespace (see https://cert-manager.io/docs/usage/ingress/). This doesn't work with Istio Ingress but works with every other Ingress
contour - Supports Ingress with standard secret scoping. Also supports CRD IngressRoute which can delegate cross namespace ie secretName: somenamespace/somesecret. This is controlled by a TLSCertificateDelegation resource which allows declaring which namespaces can access a cert
Ambassador - TBD, looking into it
Istio

Supports Gateway in any namespace, but certs only in deployment namespace
Supports Ingress in any namespace, but certs only in deployment namespace
with PILOT_SCOPE_GATEWAY_TO_NAMESPACE=true, supports Gateway in deployment namespace, and certs only in deployment namespace

Things to note here based on the above - this may not be 100% accurate as there are other Ingress providers I missed:

Istio is the only Ingress provider not implementing the Ingress spec correctly - I confirmed with the k8s networking team, cross namespace secret reference is not following the Ingress spec.
Istio is the only provider that doesn't allow cross namespace deployment <-> certificate


feat(#38): non-relevant.ts

close #38

PR-Codex overview
This PR refactors constructor parameters in multiple classes to improve readability and consistency. It introduces a new Titled class for composing title and body strings.
Detailed summary

Refactored constructor parameters in multiple classes for consistency and readability
Introduced Titled class for composing title and body strings
Added NonRelevant class to handle non-relevant bug reports and close the related GitHub issue

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@h1alexbel OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@h1alexbel Done! FYI, the full log is here (took me 6min)


Default Tab not working with SSR

🐛 Bug report
Current behavior
I'm building a site with gatsby and using the reakit Provider component in my layout to make my reakit components SSR-friendly. Now, I have a page with two tabs on it and I set the selectedId to have a default selection. If I run the page, I see that tab (though the TabList disappears if I do Ctrl+Shift+R), but in the static html the contents of that TabPanel are not there. So, the SSR'd version of the page has essentially no contents other than the Tab list.
Steps to reproduce the bug
Use code like the following in a gatsby page:
export default () => {
  const tabs = useScrollableTabState({ selectedId: "tab-1" })
  return <div>
    <TabList {...tabs} aria-label="Manuscript Tabs">
      <Tab {...tabs} id="tab-1">Translation</Tab>
      <Tab {...tabs} id="tab-2">Source Image</Tab>
    </TabList>
    <TabPanel {...tabs}>Tab 1</TabPanel>
    <TabPanel {...tabs}>Tab 2</TabPanel>
  </div>
}

Expected behavior
During SSR, the component should render the contents of tab-1, and continue to show that tab when the page is hydrated at runtime.
Possible solutions
I was able to get a partial solution by doing
  const isSSR = typeof window === "undefined"

and then
  <TabPanel {...tabs} visible={isSSR || tabs.currentId === "tab-1"}>Tab 1</TabPanel>

But then I get the contents of tab-1 in SSR and the contents disappear when I first hydrate the page at runtime!
Environment
Please, run the command below inside your project directory.
$ npx envinfo --system --binaries --browsers --npmPackages "{react*,reakit*}"

  System:
    OS: Linux 5.4 NixOS 20.09 (Nightingale) 20.09beta1411.95d26c9a9f2 (Nightingale)
    CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
    Memory: 1.44 GB / 15.52 GB
    Container: Yes
    Shell: 3.1.2 - /run/current-system/sw/bin/fish
  Binaries:
    Node: 12.18.4 - /run/current-system/sw/bin/node
    Yarn: 1.22.5 - /run/current-system/sw/bin/yarn
    npm: 6.14.6 - /run/current-system/sw/bin/npm
  Browsers:
    Firefox: 82.0
  npmPackages:
    react: ^16.13.1 => 16.14.0
    react-device-detect: ^1.14.0 => 1.14.0
    react-dom: ^16.13.1 => 16.14.0
    react-helmet: ^6.0.0 => 6.1.0
    react-icons: ^3.11.0 => 3.11.0
    react-stickynode: ^3.0.4 => 3.0.4
    react-zoom-pan-pinch: ^1.6.1 => 1.6.1
    reakit: ^1.2.1 => 1.2.5

It would be great if you could provide a minimal reproduction in the form of a repo. No worries if not but it would help others look into it faster.

You have to pass tabId to TabPanel:
<TabPanel {...tabs} tabId="tab-1">Tab 1</TabPanel>


RFC 0211: routing shouldn't be exclusively key-focused

The way 0211 is currently written, all routing is specified in terms of keys. I think this is too narrow. It may be reasonable to do intra-domain routing from Alice's cloud agent to her edge agents using keys, but at least inter-domain routing from Alice's agency to her cloud agent will likely use DIDs.
@devin-fisher @TelegramSam

Would it be a DID or would it be a DID-url? (DID with key reference) Is this something we want to specify the difference between?

It would be a DID. I am saying that when Alice wants to send to Bob, she routes to Bob's DID. She may encrypt for Bob's edge agent(s), but encryption and routing are not the same (though they are highly related).
I'm going to write some more about this logical difference in the new RFC about routing.

@dhh1128 @devin-fisher @TelegramSam @kdenhartog was this topic discussed elsewhere? We share Daniel's concerns as well.

The to field of the Forward message accepts DIDs with and without key references. The route-coordination RFC seems to be misaligned with this fact.
Any updates on this?

We went with keys initially, as allowing either plain DIDs or DID URIs (that point to keys) adds complexity. Now might be the right time to expand to something more expressive. We'll need to consider the solutions to the edge cases that this brings up.

Continue issue here: https://github.com/decentralized-identity/didcomm-messaging/issues/26


Finn pip install overwrites existing finn-base install

Related Gitter discussion: https://gitter.im/xilinx-finn/community?at=60dad875effd491d8c8ec7bc
For some (?) users, the finn pip install in "finn_entrypoint.sh" (pip install --user -e $FINN_ROOT) re-installs finn-base from the official main branch even though a different finn-base installation (e.g. at a different commit hash or mounted from a local finn-base clone) already exists.
Finn-base is currently listed as dependency in "setup.cfg" to make the readthedocs build work:
install_requires = finn-base @ git+https://github.com/Xilinx/finn-base#egg=finn-base
Curiously, this was never a problem for me; the finn-base requirement is satisfied by other versions without issue.

Hi @fpjentzsch, this issue is solved in the new releases. finn-base got deprecated and the source code is now in qonnx and finn.


Replace CircularProgress with Loading

depends on https://github.com/vivid-planet/comet-starter/pull/28
Replaces all usages of <CircularProgress /> with the new <Loading /> component

is the admin generator already using that?

@nsams I created a PR for that https://github.com/vivid-planet/comet/pull/1316