Fix cordova 5 build errors

This should fix #66 build issues.
I added the missing translations and left them as English as a default. This will at least let those who use cordova 5 continue to use the plugin until someone fluent can translate the remaining strings.

Fixed formatting in https://github.com/wymsee/cordova-imagePicker/pull/118


[FR] Support the list form of tags and aliases

Hello，can you support the list form of tags and aliases？thanks

Hi you can test it in 0.4.11

Hi you can test it in 0.4.11

Hello，I have tested it, but it doesn't seem to work properly. The recorded video demo is as follows. Is it my improper operation? thanks
https://user-images.githubusercontent.com/61906420/213840591-e6df2fb9-5dae-4d10-8ed2-4b8db92045c6.mp4

You're attachment is an audio file

Your attachment is an audio file

Sorry，I uploaded it again，and the truth is that the list will become the form like “tags: A, B , C” , not is an indented list, thanks
There is the video with .mp4 format, and if you cant see it again, it may be caused by the sever link:
https://user-images.githubusercontent.com/61906420/213901762-3b450771-2968-4a59-930a-31a94e2c765a.mp4
The screenshot：

Hello，I found that only works for the field type something like “... from a list”, but as for "Accept any vaule", it doesnt work.
I think most of  the persons need any vaule for tags and aliases to input，thanks~

core tags and aliases will have their own UI for value modification in the next version of obsidian. I'd rather not conflict with this two specific properties in the plugin


Improving readability of the Pet News page

The whole UI of the website is really appealing and beautiful but i realized that the "pet news" section appears to have the text on a transparent card element and the hover animation realigns itself on hovering.
Solution:
I propose to change the card a little such that:
i) The background of the card while still translucent will appear on a darker semi-transparent background.
ii) The hover card animation would be similar as in enlarging the card element without we aligning of the text which takes away from the user experience.
I am skilled in CSS, Tailwind and Bootstrap therefore i believe i am fit for this issue.
Kindly assign me @yashraj1706 this issue under #SWOC24 @akshitagupta15june

Kindly assign me @yashraj1706 this issue under #SWOC24 @akshitagupta15june


Discuss new naming convention for problem directories on shell server

For example, in the 2018 problem set:

Reversing Warmup 1 - Points: 50
Throughout your journey you will have to run many programs. Can you navigate to /problems/reversing-warmup-1_4_6b2499250c4624337a1948ac374c4934 on the shell server and run this program to retreive the flag?

Thankfully @dmartin's update to our provided browser shell makes these folder names less of an issue (b/c seamless copy and paste), but I still think we could do better.
If anyone cares to comment:

Why do we tack what looks like a hash on the end of the problem name for the folder?
Why is the hash so long? (last five digits would seem more than sufficient)

I believe the naming convention could be improved by:

More clarity that this file is a directory
Pseudorandomness that works with command-line auto-complete

I would like to change folder names to something like:

/problems/reversing-warmup-1_4_directory_alpha_beta

Re hashed sir: From memory, had to do with intent to obscure names of different instances and problems to not be guessable

Yes @hilang-cmu is correct. It is configurable to turn off the long hashes.

@hiliang-cmu @carlislemc nice, glad it already has something for easier access to directories.
I'm going to dub these "cryptographically secure directory names." I'm guessing this novel approach was adopted because it protects access to directories without need to set or manage permissions. It strikes me as an expedient solution, though highly unusual.
I think it's far from most important right now, but I think our participants would benefit a lot from our shell server being navigable like most normative Linux servers and if sensitive resources were protected using permissions instead of cryptographically secure directory names.

In separate issue from this one, we should revisit the problem directory symlinking function (which was performed via a daemon, but disabled in 2018). In some ideal world, a neat set of symlinks should exist in each home directory to the respective hashed directories.

@hiliang-cmu Ah ok. That would help.
Do you think that using permissions instead of secret directory names would be too difficult to be worth it?


feat(docs): page for customizing slugs

Well written Docs page! You covered a complex config in a simple manner. The code examples paired with "this is what it will produce" are very helpful.

Sweet! Highlighting has been added, will auto-merge


Seed Startup Hub

HARVARD BUSINESS REVIEW AFFILIATIONS

offer new entries and access to things we never knew existed before.

As -with Wind- nothing surprises us anymore... NOTHING...
Best,
x._________
PLEASE LOOK TO OUR FOUNDING DOCUMENTS TONIGHT AND TAKE A MINUTE TO READ THE POWERFUL TRUTHS THAT SIT WITHIN THE PREAMBLE TO US DECLARATION OF INDEPENDENCE. ITS THE FIX. A TWO-MINUTE BLURP FIXES WHOLE EARTH
EMPHATIC ABOUT THIS. CONVINCED WITHOUT A SHADOW OF DOUBT.
shh! Listen... Hear it yet? You will!

Source URL:
https://www.seedstartuphub.com/Home/MyAccount
BrowserChrome 84.0.4147.68OSWindows 10 64-bitScreen Size2560x1080Viewport Size2560x888Pixel Ratio@1xZoom Level100%

THE LINKS & MAINSTAY PLAYBOOK

Leveraging Venture Capital
https://www.crunchbase.com/person/c-brennan-poole
https://www.crunchbase.com/organization/chasing-the-wind-llc

with Wind & Professional Platforms
https://linkedin.com/in/oudcollective
https://linkedin.com/in/c-brennan-poole
https://linkedin.com/company/the-wind

CENTERED AROUND PINTEREST
https://www.pinterest.com/withwindllc
SNIPPET OF THE CLOSED NETWORK GROWTH LOOPS
https://my.bio/thewindllc


Does incremental repair using ranges really work?

https://groups.google.com/d/msg/nosql-databases/peTArLfhXMU/IuUYnnUhBgAJ claims it doesn't work.
I was investigating this because I was curious if I could slowly enable incremental repairs using this script.

After reading http://thelastpickle.com/blog/2017/12/14/should-you-use-incremental-repair.html , I'm not sure enabling incremental repair is the best idea :(

Hah, good timing! Unfortunately we are already half-way through with enabling incremental repairs...


Assignment_2 completed

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Submitting Assignment_2 of production
What did you learn from the changes you have made?
learned to build the pipeline
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
None at the moment
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
There were a lot of challenges
How were these changes tested?
Code is tested in VS code
A reference to a related issue in your repository (if applicable)
na
Checklist

[ ] I can confirm that my changes are working as intended

A2 complete


Use puppet-staging to download glance image

This patch is to add facility to stage the image on local location and
optionaly convert it to raw format before uploading to glance.
This patch will solve two problems:

after we support only boot from volume, we need raw images, so this will
convert the images if asked to do so.
it use puppet-staging to stage the image which is internally using
curl/wget which respect global proxies, so it eleminate the need of floating IPs
to ocdb1.

please test this

please test this

please test this

please test this

I would much rather use archive than staging b/c the implementation is a little cleaner and it does a few things that staging doesn't.
I had to implement it as part of the kilo work b/c glance does not support remote downloads in kilo, the patch is here:
https://github.com/bodepd/puppet-rjil/commit/4e09e9c79b11c7416ca097057baf79eed3380581
I can break it up into a separate pull request. Although, it requires that we package some dependencies as packages. I'll go ahead and submit it as a PR and ask @rickysarraf to create those packages.

I will fix the tests tomorrow.

please test this

please test this

this build failed and it might be b/c of this patch, has anyone had time to root cause? I just started looking into it:
glance image-list
(-1, 'Unexpected EOF')

It is the problem with glance client it seems, When we try api calls, it just work.
I send this in deployment channel on friday.
May be it would need to file a bug to appropriate engineering team.
Running glance image-create is not working on builds especially when using local file.

root@ocdb1-testjenkins-puppet-rjil-gate-1616:/opt/staging# glance -d image-create --name harish --disk-format raw --container-format bare --is-public True < cirros.img
curl -i -X POST -H 'Accept-Encoding: gzip, deflate, compress' -H 'x-image-meta-container_format: bare' -H 'Accept: */*' -H 'X-Auth-Token: {SHA1}4361e106557d34d2fd970f1ebcc7547f0f83d2c6' -H 'x-image-meta-size: 41126400' -H 'x-image-meta-is_public: True' -H 'User-Agent: python-glanceclient' -H 'Content-Type: application/octet-stream' -H 'x-image-meta-disk_format: raw' -H 'x-image-meta-name: harish'  --cert None --key None https://image.jiocloud.com:9292/v1/images
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/glanceclient/shell.py", line 590, in main
    args.func(client, args)
  File "/usr/lib/python2.7/dist-packages/glanceclient/v1/shell.py", line 237, in do_image_create
    image = gc.images.create(**fields)
  File "/usr/lib/python2.7/dist-packages/glanceclient/v1/images.py", line 288, in create
    data=image_data)
  File "/usr/lib/python2.7/dist-packages/glanceclient/common/http.py", line 256, in post
    return self._request('POST', url, **kwargs)
  File "/usr/lib/python2.7/dist-packages/glanceclient/common/http.py", line 200, in _request
    **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 455, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 558, in send
    r = adapter.send(request, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 353, in send
    low_conn.send(i)
  File "/usr/lib/python2.7/httplib.py", line 811, in send
    self.sock.sendall(data)
  File "/usr/lib/python2.7/dist-packages/urllib3/contrib/pyopenssl.py", line 353, in sendall
    return self.connection.sendall(data)
SysCallError: (-1, 'Unexpected EOF')
(-1, 'Unexpected EOF')

But using curl is working

root@ocdb1-testjenkins-puppet-rjil-gate-1616:/opt/staging# curl -i 'https://image.jiocloud.com:9292/v1/images' -X POST -H 'Accept-Encoding: gzip, deflate, compress' -H 'x-image-meta-container_format: bare' -H 'Accept: */*' -H 'X-Auth-Token: 54fa51fae31449ab94a64c07d9f5b66d' -H 'x-image-meta-size: 41126400' -H 'x-image-meta-is_public: True' -H 'User-Agent: python-glanceclient' -H 'Content-Type: application/octet-stream' -H 'x-image-meta-disk_format: raw' -H 'x-image-meta-name: c2.img' -T 'cirros.img'
HTTP/1.1 100 Continue

HTTP/1.1 201 Created
Date: Fri, 26 Jun 2015 09:48:42 GMT
Server: Apache/2.4.7 (Ubuntu)
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: Accept, Content-Type, X-Auth-Token, X-Subject-Token
Access-Control-Expose-Headers: Accept, Content-Type, X-Auth-Token, X-Subject-Token
Access-Control-Allow-Methods: GET POST OPTIONS PUT DELETE PATCH
Content-Type: application/json
Content-Length: 476
Location: https://image.jiocloud.com:9292/v1/images/66dc180b-bf9b-428c-9d5f-c03e93ba6ae1
Etag: 0590d15336f919496ccc91b2c0f667bc
X-Openstack-Request-Id: req-9471cbeb-0c9c-4a6c-9da3-eb9af53b17ea
Via: 1.1 image.jiocloud.com:9292
Connection: close

{"image": {"status": "active", "deleted": false, "container_format": "bare", "min_ram": 0, "updated_at": "2015-06-26T09:48:42", "owner": "49c1c74593604c9fa3b792dce0116761", "min_disk": 0, "is_public": true, "deleted_at": null, "id": "66dc180b-bf9b-428c-9d5f-c03e93ba6ae1", "size": 41126400, "virtual_size": null, "name": "c2.img", "checksum": "0590d15336f919496ccc91b2c0f667bc", "created_at": "2015-06-26T09:48:37", "disk_format": "raw", "properties": {}, "protected": false}}root@ocdb1-testjenkins-puppet-rjil-gate-1616:/opt/staging#
root@ocdb1-testjenkins-puppet-rjil-gate-1616:/opt/staging#
root@ocdb1-testjenkins-puppet-rjil-gate-1616:/opt/staging# glance image-list
+--------------------------------------+------------------------------+-------------+------------------+----------+--------+
| ID                                   | Name                         | Disk Format | Container Format | Size     | Status |
+--------------------------------------+------------------------------+-------------+------------------+----------+--------+
| c07ec2c0-4ce3-490e-8d8f-cfff5dc3cc4c | c.img                        | raw         | bare             | 41126400 | active |
| 66dc180b-bf9b-428c-9d5f-c03e93ba6ae1 | c2.img                       | raw         | bare             | 41126400 | active |
| 99806ea1-ddf0-4d34-97ad-e811752ce8c3 | cirros-0.3.3-x86_64-disk.raw | raw         | bare             | 41126400 | active |
+--------------------------------------+------------------------------+-------------+------------------+----------+--------+

BTW, it doesn't seems this bug caused this issue, I see this on some other recent builds too.

really? does glance not work any more? This seems like it would cause all builds to fail, and most builds are passing atm.

glanceclient it seems doesn't work at least on few builds I tested - but in production it is working.

Om was also telling the same.

how can at tests be passing if this is true?

it seems only glance image-create from  local image file is failing which is not used in the builds usually, but this one using it.

@hkumarmk even glance image-list fails, I was thinking that maybe the raw image got inserted into glance and led to this error.

I dont know, but glance image-list was working before (see above comment)

that's exactly what I want to test, that it works, then we run this operation and it breaks.

It seems this is the problem with glance client, I see it is not working on baremetal system where I setup pre-staging for uc.
hkumar@uc1-prestage:~$ glance --debug image-create --name ubuntu2015012401-kernel --disk-format aki --container-format aki --is-public False < images/ubuntu2015012401-kernel
curl -i -X POST -H 'Accept-Encoding: gzip, deflate, compress' -H 'x-image-meta-container_format: aki' -H 'Accept: /' -H 'X-Auth-Token: {SHA1}03315ec09535a5df6988ebee7cdf47d5ec390063' -H 'x-image-meta-size: 5814496' -H 'x-image-meta-is_public: False' -H 'User-Agent: python-glanceclient' -H 'Content-Type: application/octet-stream' -H 'x-image-meta-disk_format: aki' -H 'x-image-meta-name: ubuntu2015012401-kernel'  --cert None --key None https://image-uc.jiocloud.com:9292/v1/images
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/glanceclient/shell.py", line 590, in main
args.func(client, args)
File "/usr/lib/python2.7/dist-packages/glanceclient/v1/shell.py", line 237, in do_image_create
image = gc.images.create(**fields)
File "/usr/lib/python2.7/dist-packages/glanceclient/v1/images.py", line 288, in create
data=image_data)
File "/usr/lib/python2.7/dist-packages/glanceclient/common/http.py", line 256, in post
return self._request('POST', url, **kwargs)
File "/usr/lib/python2.7/dist-packages/glanceclient/common/http.py", line 200, in _request
**kwargs)
File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 455, in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 558, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 353, in send
low_conn.send(i)
File "/usr/lib/python2.7/httplib.py", line 805, in send
self.sock.sendall(data)
File "/usr/lib/python2.7/dist-packages/urllib3/contrib/pyopenssl.py", line 285, in sendall
return self.connection.sendall(data)
SysCallError: (-1, 'Unexpected EOF')
(-1, 'Unexpected EOF')

I used the glance client from my laptop which worked.
hkumar@lap-devops:~$ glance --debug --insecure image-create --name ubuntu2015012401-kernel --disk-format aki --container-format aki --is-public False < /tmp/ubuntu2015012401-kernel
curl -i -X POST -H 'Content-Length: 5814496' -H 'x-image-meta-container_format: aki' -H 'User-Agent: python-glanceclient' -H 'x-image-meta-size: 5814496' -H 'x-image-meta-is_public: False' -H 'X-Auth-Token: ***' -H 'Content-Type: application/octet-stream' -H 'x-image-meta-disk_format: aki' -H 'x-image-meta-name: ubuntu2015012401-kernel' -k -d '<open file '', mode 'r' at 0x7f22392900c0>' https://image-uc.jiocloud.com:9292/v1/images
HTTP/1.1 201 Created
content-length: 492
access-control-allow-methods: GET POST OPTIONS PUT DELETE PATCH
access-control-expose-headers: Accept, Content-Type, X-Auth-Token, X-Subject-Token
via: 1.1 image-uc.jiocloud.com:9292
server: Apache/2.4.7 (Ubuntu)
connection: close
etag: ac66f683972e9e9d2c7209c0a366f65c
location: https://image-uc.jiocloud.com:9292/v1/images/d6cb1dbc-4436-47b1-80e6-21a503e19ee2
date: Thu, 02 Jul 2015 09:55:46 GMT
access-control-allow-origin: *
access-control-allow-headers: Accept, Content-Type, X-Auth-Token, X-Subject-Token
content-type: application/json
x-openstack-request-id: req-02019f76-5499-4491-9ae8-4f881f3cd310
{"image": {"status": "active", "deleted": false, "container_format": "aki", "min_ram": 0, "updated_at": "2015-07-02T09:55:46", "owner": "668c74ed126740e884e9fffb58bcf2be", "min_disk": 0, "is_public": false, "deleted_at": null, "id": "d6cb1dbc-4436-47b1-80e6-21a503e19ee2", "size": 5814496, "virtual_size": null, "name": "ubuntu2015012401-kernel", "checksum": "ac66f683972e9e9d2c7209c0a366f65c", "created_at": "2015-07-02T09:55:20", "disk_format": "aki", "properties": {}, "protected": false}}
+------------------+--------------------------------------+
| Property         | Value                                |
+------------------+--------------------------------------+
| checksum         | ac66f683972e9e9d2c7209c0a366f65c     |
| container_format | aki                                  |
| created_at       | 2015-07-02T09:55:20                  |
| deleted          | False                                |
| deleted_at       | None                                 |
| disk_format      | aki                                  |
| id               | d6cb1dbc-4436-47b1-80e6-21a503e19ee2 |
| is_public        | False                                |
| min_disk         | 0                                    |
| min_ram          | 0                                    |
| name             | ubuntu2015012401-kernel              |
| owner            | 668c74ed126740e884e9fffb58bcf2be     |
| protected        | False                                |
| size             | 5814496                              |
| status           | active                               |
| updated_at       | 2015-07-02T09:55:46                  |
| virtual_size     | None                                 |
+------------------+--------------------------------------+
hkumar@lap-devops:~$ glance --version
<IP_ADDRESS>

please test this

Test FAILed

please test this

Test FAILed

This has merge conflicts. Needs a rebase.
"GitHub pull request #671 of commit b8504ef43837c30da447dc7ecad25680e022dd5b, has merge conflicts."

the rebase was huge. tried doing a PR against hkumar's branch, but lots of changes.. so opening a new one instead.


Basic Authentication not working as intended

Describe the bug
The Basic Authentication implementation in stac-fastapi-elasticsearch is not working as expected. When configuring multiple user credentials through STAC_FASTAPI_ROUTE_DEPENDENCIES, the authentication fails even with valid credentials.
To Reproduce
Steps to reproduce the behavior:

Configure basic auth with multiple users in docker-compose.yml:

- STAC_FASTAPI_ROUTE_DEPENDENCIES=[{"routes":[{"method":"*","path":"*"}],"dependencies":[{"method":"stac_fastapi.core.basic_auth.BasicAuth","kwargs":{"credentials":[{"username":"admin","password":"admin"}]}}]},{"routes":[{"path":"/","method":["GET"]},{"path":"/conformance","method":["GET"]},{"path":"/collections/{collection_id}/items/{item_id}","method":["GET"]},{"path":"/search","method":["GET","POST"]},{"path":"/collections","method":["GET"]},{"path":"/collections/{collection_id}","method":["GET"]},{"path":"/collections/{collection_id}/items","method":["GET"]},{"path":"/queryables","method":["GET"]},{"path":"/queryables/collections/{collection_id}/queryables","method":["GET"]},{"path":"/_mgmt/ping","method":["GET"]}],"dependencies":[{"method":"stac_fastapi.core.basic_auth.BasicAuth","kwargs":{"credentials":[{"username":"reader","password":"reader"}]}}]}]

Start the stac-fastapi-elasticsearch service with basic auth configuration:

docker-compose up -d

Try to access the root endpoint with valid credentials:

curl --request GET \
  --url http://localhost:8080/ \
  --header 'Authorization: Basic YWRtaW46YWRtaW4='

curl --request GET \
  --url http://localhost:8080/ \
  --header 'Authorization: Basic cmVhZGVyOnJlYWRlcg=='

Receive error response:

{"detail":"Incorrect username or password"}

Expected behavior

The API should accept valid credentials from any user configured in the route dependencies
Both "admin:admin" and "reader:reader" credentials should work for their respective configured routes
When a route is configured for multiple users, any of their credentials should work

Environment:

OS: Ubuntu 22.04.4 LTS
Docker version: Docker version 27.1.1, build 6312585
stac-fastapi-elasticsearch version: 3.2.0
Python version: 3.10

any chance you could take a look at this @rhysrevans3 ?

Happy to have a look!

Additional context: It works fine with a single user.

Happy to have a look!

@rhysrevans3
Additional context: It works fine with a single user.

@pedro-cf I've figure out the cause of the issue. As the dependencies (one for admin and one for reader) are separate they both get run and if either fail then the user is denied access. Because they don't know about each other they will fail on any endpoint where both are active.
One solution is to not use "*" and add both credentials to any endpoints that need them. I'll add a note to the auth readme to explain this.
I think a better solution for this is to handle security dependencies separately to other dependencies and have a main security dependency that can check that at least one has a passed.

One solution is to not use "*" and add both credentials to any endpoints that need them. I'll add a note to the auth readme to explain this.

If possible can you share a working example for this solution? for the standard admin + reader user setup

Here's an example where only admin has access to the transaction endpoints, both admin and reader have access to the second set of routes, and all unspecified routes are public.
- STAC_FASTAPI_ROUTE_DEPENDENCIES=[{"routes":[{"method":"/collections","path":["POST"]},{"method":"/collections/{collection_id}","path":["DELETE", "PUT"]},{"method":"/collections/{collection_id}/items","path":[ "POST"]},{"method":"/collections/{collection_id}/items/{item_id}","path":["DELETE", "PUT"]}],"dependencies":[{"method":"stac_fastapi.core.basic_auth.BasicAuth","kwargs":{"credentials":[{"username":"admin","password":"admin"}]}}]},{"routes":[{"path":"/","method":["GET"]},{"path":"/conformance","method":["GET"]},{"path":"/collections/{collection_id}/items/{item_id}","method":["GET"]},{"path":"/search","method":["GET","POST"]},{"path":"/collections","method":["GET"]},{"path":"/collections/{collection_id}","method":["GET"]},{"path":"/collections/{collection_id}/items","method":["GET"]},{"path":"/queryables","method":["GET"]},{"path":"/queryables/collections/{collection_id}/queryables","method":["GET"]},{"path":"/_mgmt/ping","method":["GET"]}],"dependencies":[{"method":"stac_fastapi.core.basic_auth.BasicAuth","kwargs":{"credentials":[{"username":"reader","password":"reader"}, {"username":"admin","password":"admin"}]}}]}]

Hope that helps.

Here's an example where only admin has access to the transaction endpoints, both admin and reader have access to the second set of routes, and all unspecified routes are public.
- STAC_FASTAPI_ROUTE_DEPENDENCIES=[{"routes":[{"path":"/collections", "method":["POST"]},{"path":"/collections/{collection_id}", "method":["DELETE", "PUT"]},{"path":"/collections/{collection_id}/items", "method":[ "POST"]}, {"path":"/collections/{collection_id}/items/{item_id}", "method":["DELETE", "PUT"]}], "dependencies":[{"method":"stac_fastapi.core.basic_auth.BasicAuth","kwargs":{"credentials":[{"username":"admin","password":"admin"}]}}]},{"routes":[{"path":"/","method":["GET"]},{"path":"/conformance","method":["GET"]},{"path":"/collections/{collection_id}/items/{item_id}","method":["GET"]},{"path":"/search","method":["GET","POST"]},{"path":"/collections","method":["GET"]},{"path":"/collections/{collection_id}","method":["GET"]},{"path":"/collections/{collection_id}/items","method":["GET"]},{"path":"/queryables","method":["GET"]},{"path":"/queryables/collections/{collection_id}/queryables","method":["GET"]},{"path":"/_mgmt/ping","method":["GET"]}],"dependencies":[{"method":"stac_fastapi.core.basic_auth.BasicAuth","kwargs":{"credentials":[{"username":"reader","password":"reader"}, {"username":"admin","password":"admin"}]}}]}]

Hope that helps.

Greetings I was testing this setup.
I noticed you set the credentials for reader twice:

but even after removing the second one I am still getting some issues
Reader Request:
curl --request GET \
  --url http://localhost:8084/ \
  --header 'Authorization: Basic cmVhZGVyOnJlYWRlcg=='

Reader Response:
200 OK
{
....
}

Admin Request:
curl --request GET \
  --url http://localhost:8084/ \
  --header 'Authorization: Basic YWRtaW46YWRtaW4='

Admin Response:
{
	"detail": "Incorrect username or password"
}

Additionally if I add:
{
   "path":"/",
   "method":[
      "GET"
   ]
}

to the admin's routes, then both users cannot access "/" and get:
{
	"detail": "Incorrect username or password"
}

Hi @pedro-cf sorry I probably wasn't very clear with my example.
The two route dependencies in my example weren't one for admin and one for reader. It was one for admin only:
{"routes":[{"path":"/collections", "method":["POST"]},{"path":"/collections/{collection_id}", "method":["DELETE", "PUT"]},{"path":"/collections/{collection_id}/items", "method":[ "POST"]}, {"path":"/collections/{collection_id}/items/{item_id}", "method":["DELETE", "PUT"]}], "dependencies":[{"method":"stac_fastapi.core.basic_auth.BasicAuth","kwargs":{"credentials":[{"username":"admin","password":"admin"}]}}]}

and one for admin and reader:
{"routes":[{"path":"/","method":["GET"]},{"path":"/conformance","method":["GET"]},{"path":"/collections/{collection_id}/items/{item_id}","method":["GET"]},{"path":"/search","method":["GET","POST"]},{"path":"/collections","method":["GET"]},{"path":"/collections/{collection_id}","method":["GET"]},{"path":"/collections/{collection_id}/items","method":["GET"]},{"path":"/queryables","method":["GET"]},{"path":"/queryables/collections/{collection_id}/queryables","method":["GET"]},{"path":"/_mgmt/ping","method":["GET"]}],"dependencies":[{"method":"stac_fastapi.core.basic_auth.BasicAuth","kwargs":{"credentials":[{"username":"reader","password":"reader"}, {"username":"admin","password":"admin"}]}}]}

That's why there are two sets of credentials in the second route dependency one for reader and one for admin.
So any routes added to the first route dependency will be admin only and any added to the second will be accessible by both admin and reader.
The reason for this is FastAPI runs all of the dependencies for an endpoint and will raise an error if any fail. So you can only have one Auth dependency per endpoint else they will clash.
Hope this clarifies things 😄


add missing object to reload

Description
Fixes NameError: undefined local variable or method `container' for #<#<Class:0x00000000058b9c50>:0x0000000005686b18> when attempting to reload a container.
Issues Resolved
n/a
Check List

[x] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD

[n/a] New functionality includes testing.
[n/a] New functionality has been documented in the README if applicable
[n/a] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

Nice catch


Rpi pico pkg/dev for the 4 rpi pico variants

SUMMARY

created 4 package/device files for the Raspberry Pi Pico, they are,
Pico (smd)
Pico with headers
Pico W (wireless)(smd)
Pico W with Headers,
needed 4 because the SWD pads are in different places between Pico and Pico W
DATASHEETS / REFERENCES

OPEN QUESTIONS / UNRESOLVED ISSUES

CHECKLIST

[x] I have read and followed the library conventions¹.
[ ] For packages, I followed IPC7351C (see details in library conventions).
[ ] For modified elements, I bumped their version number².
[ ] I already used the new library elements in a design and verified their correctness (optional).
[x] I'm the copyright owner of the added content (i.e. the changes are made by myself, not copied/imported from somewhere else).
[x] I agree to publish all my changes under the CC0 Public Domain License³, allowing everyone to use and modify the content without any restrictions.

¹ Library Conventions: https://docs.librepcb.org/#libraryconventions
² Minor version bump if only metadata was modified (e.g. "0.1" -> "0.1.1"), major version bump if functional changes were made (e.g. "0.1" -> "0.2")
³ CC0 Public Domain License: https://en.wikipedia.org/wiki/CC0

I would love to see this get merged in.


Change from ⋮ to just white space?

Would you take a PR to change the inline test indentation from using ⋮ to just removing the rectangle of white space, similar to https://github.com/janestreet/ppx_expect#whitespace?
I had started on that PR but thought it worth checking first...

I was thinking of this but this will make diffing much harder. We could do it in a way where the leading whitespace of a line is ignored but patched back on the diff.
So for instance the reference value is this:
    foo
      bar

And the comparison value is this:
  foo
  bar

In that case we could patch up the comparison value with all the leading whitespaces of the reference value before doing the diffing.
Otherwise I'm -1 on this change most likely because it will be confusing as hell.

Definitely not worth doing if it makes diffing harder. The intention was to reduce complication by removing the need for an unusual character and any mandate for a specific indentation. The way I'm thinking about it, it wouldn't make diffing harder (but maybe I'm missing something).
It would go from:
    assert_debug_snapshot_matches!(x.dimensions(), @r###"
   ⋮[
   ⋮    (
   ⋮        "x",
   ⋮        3,
   ⋮    ),
   ⋮    (
   ⋮        "y",
   ⋮        2,
   ⋮    ),
   ⋮]
    "###);

to:
    assert_debug_snapshot_matches!(x.dimensions(), @r###"
    [
        (
            "x",
            3,
        ),
        (
            "y",
            2,
        ),
    ]
    "###

So it removes the largest full rectangle of white space from both the result and reference, rather than any space prior to (& including) the ⋮ character.
I'm trying to grok the example above. If the reference value is currently
    ⋮foo
    ⋮  bar

...then we should fail on a value like...
  foo
  bar

Why would we get that unequal white space if the actual value had equal white space? Something to do with the first line of a multi-line string?

Special casing the first line does not work because that makes it impossible for you to have a higher amount of whitespace on the first line than on other:
   foo
  bar
 baz
blah

Is a good example of this.

To be clear on the proposal / functionality in ppx_expect, it's to remove "the largest rectangle of white space in all lines". So
   foo
  bar
 baz
blah

is the same as
    foo
   bar
  baz
 blah

...the later removing a single space from all lines. So it is easy to have different amounts of white space on different lines
Does that make sense?

This could potentially work but we still need to re-introduce the correct amount of whitespace before diffing.

@max-sixty since you asked in #62 what else to work on: i really like the idea of this ticket :)

@max-sixty since you asked in #62 what else to work on: i really like the idea of this ticket :)

This is done! #52 ! Could do with a few more tests etc but let me know if you think it's in the right direction and I'll finish

@max-sixty Yeah. I think overall direction is pretty good. We need to make sure the diffing looks good and there is a good migration path over. But yeah, very much in favour.

OK cool!

We might even be able to improve on this by making a strict whitespace flag on the new settings if we run into any issues. For instance whitespace might play a vital role for such cases: https://github.com/brendanzab/codespan/blob/master/codespan-reporting/tests/snapshots/empty_spans__rich_no_color.snap

Plan for changes:

Existing snapshots will still 'normalize', and so pass
New snapshots will always write with rectangular space (even if the snapshot it's replacing was in the existing format)

@max-sixty i wonder if we can find a way to add something that upgrades all snapshots forcefully to latest. We could have a INSTA_UPGRADE=1 which then forcefully writes back the latest format.  cargo insta test --upgrade could then auto upgrade.

We might even be able to improve on this by making a strict whitespace flag on the new settings if we run into any issues. For instance whitespace might play a vital role for such cases: https://github.com/brendanzab/codespan/blob/master/codespan-reporting/tests/snapshots/empty_spans__rich_no_color.snap

Where would the flag go?
To consider:

It'll have false positives rather than false negatives. i.e. regardless of whitespace, tests will still pass, but won't fail on a difference between

  x

and
x

If it's important, people can always use file snapshots
Where whitespace is important, it's not going to look pretty, e.g.

              let y = "a"`
              assert_snapshot_matches!(x, r###"
test
###");
              let x = ...

@max-sixty into the new settings system:
insta::with_settings!({strict_whitespace = true, {
    ...
}));

It could just render out by prepending the string with a leading character that is otherwise ignored.

@max-sixty i wonder if we can find a way to add something that upgrades all snapshots forcefully to latest. We could have a INSTA_UPGRADE=1 which then forcefully writes back the latest format. cargo insta test --upgrade could then auto upgrade.

I very much agree with this, I was thinking about something similar: when you want to auto accept all changes.
So two ideas:

cargo insta test --accept accepts all changes (or is there a way to do this already?)
cargo insta test --upgrade overwrites with the newest format

What are your thoughts?

Yeah, I think that makes sense adding. Right now we only have cargo insta test followed by cargo insta accept.

@max-sixty into the new settings system:
insta::with_settings!({strict_whitespace = true}, {
    ...
});

It could just render out by prepending the string with a leading character that is otherwise ignored.

Yes we could definitely do that. Do you think it would be useful above doing file snapshots though? Those will still discriminate on white space.

@max-sixty it might be good enough to defer this for now and we just call it out.

Yeah, I think that makes sense adding. Right now we only have cargo insta test followed by cargo insta accept.

OK cool. Do you think there's a simplicity to combining them? Or the ability to --accept is useful without overwriting everything?

I think adding --accept makes sense.


windows server2012: file-error "Searching for program" "No such file or directory" "python"

Hi, I met this problem on my win 2012server. Information is listed below and sorry for the paste format here:

Debugger entered--Lisp error: (file-error "Searching for program" "No such file or directory" "python")
make-process(:name "anaconda-mode" :buffer #<buffer anaconda-mode> :command ("python" "-c" "\nimport os, sys\ndirectory = os.path.expanduser(sys.argv[-1])\nif not os.path.exists(directory):\n    os.makedirs(directory)\n" "~/.emacs.d/anaconda-mode/0.1.11"))
apply(make-process (:name "anaconda-mode" :buffer #<buffer anaconda-mode> :command ("python" "-c" "\nimport os, sys\ndirectory = os.path.expanduser(sys.argv[-1])\nif not os.path.exists(directory):\n    os.makedirs(directory)\n" "~/.emacs.d/anaconda-mode/0.1.11")))
start-process("anaconda-mode" #<buffer anaconda-mode> "python" "-c" "\nimport os, sys\ndirectory = os.path.expanduser(sys.argv[-1])\nif not os.path.exists(directory):\n    os.makedirs(directory)\n" "~/.emacs.d/anaconda-mode/0.1.11")
apply(start-process "anaconda-mode" #<buffer anaconda-mode> "python" ("-c" "\nimport os, sys\ndirectory = os.path.expanduser(sys.argv[-1])\nif not os.path.exists(directory):\n    os.makedirs(directory)\n" "~/.emacs.d/anaconda-mode/0.1.11"))
start-file-process("anaconda-mode" #<buffer anaconda-mode> "python" "-c" "\nimport os, sys\ndirectory = os.path.expanduser(sys.argv[-1])\nif not os.path.exists(directory):\n    os.makedirs(directory)\n" "~/.emacs.d/anaconda-mode/0.1.11")
apply(start-file-process "anaconda-mode" #<buffer anaconda-mode> "python" ("-c" "\nimport os, sys\ndirectory = os.path.expanduser(sys.argv[-1])\nif not os.path.exists(directory):\n    os.makedirs(directory)\n" "~/.emacs.d/anaconda-mode/0.1.11"))
start-pythonic(:process "anaconda-mode" :buffer "anaconda-mode" :sentinel #[514 "\301\300#\207" [#[0 "\302\300\301"\207" ["eldoc" anaconda-mode-eldoc-callback anaconda-mode-jsonrpc] 3] anaconda-mode-ensure-directory-sentinel] 6 "\n\n(fn PROCESS EVENT)"] :args ("-c" "\nimport os, sys\ndirectory = os.path.expanduser(sys.argv[-1])\nif not os.path.exists(directory):\n    os.makedirs(directory)\n" "~/.emacs.d/anaconda-mode/0.1.11"))
anaconda-mode-ensure-directory(#[0 "\302\300\301"\207" ["eldoc" anaconda-mode-eldoc-callback anaconda-mode-jsonrpc] 3])
anaconda-mode-start(#[0 "\302\300\301"\207" ["eldoc" anaconda-mode-eldoc-callback anaconda-mode-jsonrpc] 3])
anaconda-mode-call("eldoc" anaconda-mode-eldoc-callback)
anaconda-mode-eldoc-function()
eldoc-print-current-symbol-info()

I use anaconda3 and do not add its path to environemnt var like PATH.
How can i solve this or, at least, shutdown this yelling .

add to the commet before, I use M-: exec-path to check what $PATH is used in this windows server, after that i manually add the path of anaconda's python.exe to the $PATH, check the Emacs's path again and nothing changed, Backtrace still give this

Debugger entered--Lisp error: (file-error "Searching for program" "No such file or directory" "python")

Thanks for reporting this. It appears due to the code in pythonic.el, and I've filed an issue there on your behalf. I'll close this one because I can't fix it here. :-)

Thanks for your help.

This has apparently been fixed upstream, so maybe try updating your packages. :-)

I'll try, thx~


Dead Project?

New to NvChad and found this project.
Fresh NvChad install and after I mv DevOps.nvim ~/.config/nvim/lua/custom and run nvim +PackerSync I get Not an editor command: PackerSync. Must have been a lot of changes to NvChad since this project was last updated.

New to NvChad and found this project.
Fresh NvChad install and after I mv DevOps.nvim ~/.config/nvim/lua/custom and run nvim +PackerSync I get Not an editor command: PackerSync. Must have been a lot of changes to NvChad since this project was last updated.

I updated the configs with the new version of nvchad and now you can use it


@rend="noname" in

@ajaniak : this doesn't seem to be implemented yet in <div type="translation">. Can you solve that?

I can't find the value noname in the EGD, si I need to know to know its behaviour and how it differs from omitname.

sorry, my encoding error, it should be « omitname ». will check later today if the problem disappears once I use that value, and let you know.
Le 23 nov. 2020 à 10:19, ajaniak <notifications<EMAIL_ADDRESS>a écrit :
I can't find the value noname in the EGD, si I need to know to know its behaviour and how it differs from omitname.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/erc-dharma/project-documentation/issues/106#issuecomment-732032845, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAGMAE5IIIWZXMTLGMZUUU3SRISIVANCNFSM4T6TF55Q.


"certificate has expired" when setting up Temurin Java 11

Description:
When trying to set up a standard Java 11 Temurin distribution with Gradle caching I get an error: "certificate has expired".
Task version:
actions/setup-java@v2
Platform:

[X] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[X] Hosted
[ ] Self-hosted

Repro steps:
Our workflow fails after these standard steps:
steps:
  - uses: actions/checkout@v2
  - name: Setup Java and Dependency Caching
    uses: actions/setup-java@v2
    with:
      distribution: 'temurin'
      java-version: '11'
      cache: 'gradle'

Expected behavior:
The Java distribution gets set up properly.
Actual behavior:
From the workflow log (environment variables are custom and should be irrelevant for this step:
Run actions/setup-java@v2
  with:
    distribution: temurin
    java-version: 11
    cache: gradle
    java-package: jdk
    architecture: x64
    check-latest: false
    server-id: github
    server-username: GITHUB_ACTOR
    server-password: GITHUB_TOKEN
    overwrite-settings: true
    job-status: success
  env:
    GITHUB_PACKAGES_ACCESS_USER: ***
    GITHUB_PACKAGES_ACCESS_TOKEN: ***
    BUILD_AND_PUSH: false
Trying to resolve the latest version from remote
Error: certificate has expired

Dupe of #248


⚠ ClamAV has degraded performance

In 3eacfb6, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 72 ms

Resolved: ClamAV performance has improved in ecc1a90.


Setup instead of requirements.txt

Changes
In order to avoid deployment issues with pip and have one place to trach package, requirements.txt file has been deleted and all package requirements transfered to setup.py. Also added release workflows yml files.
backend/moonstream renamed to backend/moonstreamapi because moonstream name under client library
How to test these changes?
Tested installations and main functions execution.
Related issues

@bugout-dev check

[ ] Release after merge


refactor: GridForm ColorModes + system props

Overview
Updates some final GridForm / Form components to match current ColorMode conventions.
Checkbox needed to be entirely refactored + I split into separate PR here

PR Checklist

[x] Related to designs:
[x] Related to JIRA ticket: GM-210
[x] I have run this code to verify it works
[x] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.63-alpha.17a455.0@codecademy/gamut-labs@19.16.1-alpha.17a455.0@codecademy/gamut@34.14.2-alpha.17a455.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60ec701bdd0de63db8587609--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.63-alpha.6c5c4f.0@codecademy/gamut-labs@19.16.1-alpha.6c5c4f.0@codecademy/gamut@34.14.2-alpha.6c5c4f.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60edc528c125e817a1f82443--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.63-alpha.f6c697.0@codecademy/gamut-labs@19.16.1-alpha.f6c697.0@codecademy/gamut@34.14.2-alpha.f6c697.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60edd3f33c963534800f0f16--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.65-alpha.ba339b.0@codecademy/gamut-labs@19.16.3-alpha.ba339b.0@codecademy/gamut@34.14.4-alpha.ba339b.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60f1ea767e6e2f1262a29345--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.66-alpha.97c7c4.0@codecademy/gamut-labs@19.16.4-alpha.97c7c4.0@codecademy/gamut@34.14.5-alpha.97c7c4.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60f1fdcd0571da2832c0a929--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.66-alpha.781983.0@codecademy/gamut-labs@19.16.4-alpha.781983.0@codecademy/gamut@34.14.5-alpha.781983.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60f20314d73ef700dcd83f6e--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.67-alpha.6ef08a.0@codecademy/gamut-labs@19.16.5-alpha.6ef08a.0@codecademy/gamut@34.15.1-alpha.6ef08a.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60f2099af706db09931b6a90--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.69-alpha.626568.0@codecademy/gamut-labs@19.16.7-alpha.626568.0@codecademy/gamut@35.0.2-alpha.626568.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60f5d53b0016ae092b0ce30f--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.70-alpha.df14e8.0@codecademy/gamut-labs@19.16.8-alpha.df14e8.0@codecademy/gamut@35.1.1-alpha.df14e8.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60f6d6bb889d2400ab2b16c2--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.70-alpha.d1df1e.0@codecademy/gamut-labs@19.16.8-alpha.d1df1e.0@codecademy/gamut@35.1.1-alpha.d1df1e.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60f8990a57a9fd4db8b74794--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.70-alpha.9ce2d8.0@codecademy/gamut-labs@19.16.8-alpha.9ce2d8.0@codecademy/gamut@35.1.1-alpha.9ce2d8.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-kit@0.4.70-alpha.3b1240.0@codecademy/gamut-labs@19.16.8-alpha.3b1240.0@codecademy/gamut@35.1.1-alpha.3b1240.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60f8bc812202da0b12a58e8a--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.71-alpha.48f945.0@codecademy/gamut-labs@19.16.9-alpha.48f945.0@codecademy/gamut@35.1.2-alpha.48f945.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60f8beb6067e720c3b5405c1--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.71-alpha.6bdd20.0@codecademy/gamut-labs@19.16.9-alpha.6bdd20.0@codecademy/gamut@35.1.2-alpha.6bdd20.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60f98a3db6e9530dcfc1a364--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.71-alpha.bb4aef.0@codecademy/gamut-labs@19.16.9-alpha.bb4aef.0@codecademy/gamut@36.0.0-alpha.bb4aef.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60ff2237470ba7534719af95--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.74-alpha.e410c9.0@codecademy/gamut-labs@19.16.12-alpha.e410c9.0@codecademy/gamut@36.0.0-alpha.e410c9.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60ff24623c1ac400b619d57e--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.1-alpha.4cbf61.0@codecademy/gamut-labs@19.16.13-alpha.4cbf61.0@codecademy/gamut@36.0.0-alpha.4cbf61.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61000db6f3b85010ef030504--gamut-preview.netlify.appDeploy Logs


zsh syntax highlighting error

i'm getting an error trying to run the model. looks like one of my iterm plugins is causing it. however, even after removing it I still get the same issue.
(base) ➜  llama-gpt git:(master) ./run-mac.sh --model 13b
/usr/local/share/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh: line 31: alias: -L: invalid option
alias: usage: alias [-p] [name[=value] ... ]
/usr/local/share/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh: line 36: unalias: -m: invalid option
unalias: usage: unalias [-a] name [name ...]

By GPT-4
The error messages you're seeing are coming from the zsh-syntax-highlighting plugin for Zsh, which is intended to provide syntax highlighting for your shell.
The error messages indicate that the -L option for the alias command and -m option for the unalias command are not recognized. These options are typically used in Bash, not Zsh.
This suggests that there might be a conflict between your Zsh configuration and the run-mac.sh script you're trying to run.
Here are a few things you can try to resolve these errors:

Comment out or remove the lines in your .zshrc file that source the zsh-syntax-highlighting.zsh script, then open a new terminal window and try to run the script again.

If you don't want to disable zsh-syntax-highlighting entirely, you can try to temporarily disable it in your current shell before running the script:
unfunction zsh-syntax-highlighting
./run-mac.sh --model 13b

If the above methods don't work, you might want to try running the script in a Bash shell instead of Zsh:
bash run-mac.sh --model 13b

Remember to backup your .zshrc file before making any changes to it, so you can restore your original configuration if necessary.

I tried removing all mention of zsh-syntax-highlighting and then started getting another error: /Users/matthewberman/.oh-my-zsh/oh-my-zsh.sh: line 23: autoload: command not found

@mberman84 can you try
zsh run-mac.sh --model 13b


Add PR template to improve GitHub Community Standards

The GitHub Community Standards for this repo have all the boxes checked, except for a PR template.
Examples from other projects:

https://github.com/json-api-dotnet/JsonApiDotNetCore/blob/master/.github/PULL_REQUEST_TEMPLATE.md
https://github.com/dotnet/aspnetcore/blob/main/.github/pull_request_template.md
https://github.com/dotnet/efcore/blob/main/.github/PULL_REQUEST_TEMPLATE.md
https://github.com/fluentassertions/fluentassertions/blob/develop/.github/PULL_REQUEST_TEMPLATE.md
https://github.com/xunit/xunit/blob/main/.github/PULL_REQUEST_TEMPLATE.md
https://github.com/Humanizr/Humanizer/blob/main/.github/PULL_REQUEST_TEMPLATE.md
https://github.com/App-vNext/Polly/blob/master/.github/pull_request_template.md
https://github.com/icsharpcode/SharpZipLib/blob/master/.github/PULL_REQUEST_TEMPLATE.md

There's some guidance at https://embeddedartistry.com/blog/2017/08/04/a-github-pull-request-template-for-your-projects/ and https://www.gitkraken.com/blog/enhancing-pull-request-descriptions-templates, but I think we should keep it as basic as possible. The longer it gets, the more people are going to dislike it (so delete it all upfront or refrain from opening PRs). I've seen that happen with the issue template at a former open-source project I maintained: once we required more info, people started using the chat instead.
In my opinion, the PR template should just be a basic checklist like https://github.com/json-api-dotnet/JsonApiDotNetCore/blob/master/.github/PULL_REQUEST_TEMPLATE.md. Such a quick reminder helped me on several occasions when I forgot to update the docs.
Feedback welcome!

Adding a PR template is a great idea. I agree that it should be little more than a basic checklist, though I would like to include something that indicates additional content such as a description, summary or general notes could/should be included. Basically something in between what JsonApiDotNetCore and AspNetCore do.
This seems like a good addition to the checklist from Humanizr:
If the code is copied from StackOverflow (or a blog or OSS) full disclosure is included. That includes required license files and/or file headers explaining where the code came from with proper attribution
Is it redundant to have a checkbox for signing CLA? There is a bot that will check for that, but occasionally PRs sit waiting for that step

@TimHess  Thanks for the feedback. I'd like the template to be new-user-friendly, while at the same time not getting in the way too much for regular contributors.
So I've created #852. Please let me know what you think.


Patient/{id}/$everything does not return related Contracts

Describe the bug
Patient/{id}/$everything endpoint does not return related Contracts
FHIR Version?
R4
Data provider?
CosmosDB (Azure API for FHIR)
To Reproduce
Steps to reproduce the behavior:

Create a Patient resource with payload

{
 "resourceType": "Patient",
 "id": "example",
 "text": {
   "status": "generated",
   "div": "
\n\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t\tName	\n\t\t\t\t\t\tPeter James \n              Chalmers ("Jim")\n            	\n\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t\tAddress	\n\t\t\t\t\t\t534 Erewhon, Pleasantville, Vic, 3999	\n\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t\tContacts	\n\t\t\t\t\t\tHome: unknown. Work: (03) 5555 6473	\n\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t\tId	\n\t\t\t\t\t\tMRN: 12345 (Acme Healthcare)	\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t
\n\t\t
"
 },
 "identifier": [
   {
     "use": "usual",
     "type": {
       "coding": [
         {
           "system": "http://terminology.hl7.org/CodeSystem/v2-0203",
           "code": "MR"
         }
       ]
     },
     "system": "urn:oid:<IP_ADDRESS>.5<IP_ADDRESS>",
     "value": "12345",
     "period": {
       "start": "2001-05-06"
     },
     "assigner": {
       "display": "Acme Healthcare"
     }
   }
 ],
 "active": true,
 "name": [
   {
     "use": "official",
     "family": "Chalmers",
     "given": [
       "Peter",
       "James"
     ]
   },
   {
     "use": "usual",
     "given": [
       "Jim"
     ]
   },
   {
     "use": "maiden",
     "family": "Windsor",
     "given": [
       "Peter",
       "James"
     ],
     "period": {
       "end": "2002"
     }
   }
 ],
 "telecom": [
   {
     "use": "home"
   },
   {
     "system": "phone",
     "value": "(03) 5555 6473",
     "use": "work",
     "rank": 1
   },
   {
     "system": "phone",
     "value": "(03) 3410 5613",
     "use": "mobile",
     "rank": 2
   },
   {
     "system": "phone",
     "value": "(03) 5555 8834",
     "use": "old",
     "period": {
       "end": "2014"
     }
   }
 ],
 "gender": "male",
 "birthDate": "1974-12-25",
 "_birthDate": {
   "extension": [
     {
       "url": "http://hl7.org/fhir/StructureDefinition/patient-birthTime",
       "valueDateTime": "1974-12-25T14:35:45-05:00"
     }
   ]
 },
 "deceasedBoolean": false,
 "address": [
   {
     "use": "home",
     "type": "both",
     "text": "534 Erewhon St PeasantVille, Rainbow, Vic  3999",
     "line": [
       "534 Erewhon St"
     ],
     "city": "PleasantVille",
     "district": "Rainbow",
     "state": "Vic",
     "postalCode": "3999",
     "period": {
       "start": "1974-12-25"
     }
   }
 ],
 "contact": [
   {
     "relationship": [
       {
         "coding": [
           {
             "system": "http://terminology.hl7.org/CodeSystem/v2-0131",
             "code": "N"
           }
         ]
       }
     ],
     "name": {
       "family": "du Marché",
       "_family": {
         "extension": [
           {
             "url": "http://hl7.org/fhir/StructureDefinition/humanname-own-prefix",
             "valueString": "VV"
           }
         ]
       },
       "given": [
         "Bénédicte"
       ]
     },
     "telecom": [
       {
         "system": "phone",
         "value": "+33 (237) 998327"
       }
     ],
     "address": {
       "use": "home",
       "type": "both",
       "line": [
         "534 Erewhon St"
       ],
       "city": "PleasantVille",
       "district": "Rainbow",
       "state": "Vic",
       "postalCode": "3999",
       "period": {
         "start": "1974-12-25"
       }
     },
     "gender": "female",
     "period": {
       "start": "2012"
     }
   }
 ],
 "managingOrganization": {
   "reference": "Organization/1"
 }
}

Response payload:
{
    "resourceType": "Patient",
    "id": "6fad1f14-8b8a-4a8e-9223-e5b9329576c8",
   //...
}

Create Contract resource with a subject referencing the Patient

{
                "resourceType": "Contract",
                "meta": {
                    "versionId": "1",
                    "lastUpdated": "2024-06-11T11:26:54.846+00:00",
                    "profile": [
                        "http://hl7.org/fhir/StructureDefinition/Contract"
                    ]
                },
                "subject": [
                    {"reference": "Patient/6fad1f14-8b8a-4a8e-9223-e5b9329576c8"}
                ],
                "identifier": [
                    {
                        "use": "usual",
                        "system": "https://local-system/Id/local-id",
                        "value": "LOCALIDHASHGOESHERE"
                    }
                ],
                "status": "appended"
 }

Response with payload:
{
    "resourceType": "Contract",
    "id": "0ad7d0a8-ceae-4b28-ac5e-d83188649a0b",
   //...
}

Execute GET Patient/6fad1f14-8b8a-4a8e-9223-e5b9329576c8/$everything and iterate through all results
No Contract is included
Contract is returned if searching using GET /Contract?patient=6fad1f14-8b8a-4a8e-9223-e5b9329576c8

Expected behavior
GET Patient/6fad1f14-8b8a-4a8e-9223-e5b9329576c8/$everything includes  related Contract into response
Actual behavior
GET Patient/{id}/$everything does not return related Contracts

@joostas - are you able to perform search on contract resource with reference to patient id of interest?
Search would look like: /Contract?patient=Patient/

@EXPEkesheth yes, if I search using this request GET /Contract?patient=6fad1f14-8b8a-4a8e-9223-e5b9329576c8 contract is returned.

Thanks for information. Have created workitem to investigate further #AB122530


Documentation, SSL issue, stuck on git push line

On https://flynn.io/docs, where the app gets pushed doesn't seem to work after following the manual install doc here: https://flynn.io/docs/installation/manual. I think this is because we've installed the SSL trust cert into the browser but not the system but no mention of this in the docs.

Can you provide the error message you are encountering?

Yep sorry, at first it was timing out. Now getting
remote: Internal server error
fatal: unable to access 'https://git.flynn.flatcar.xyz/example.git/': The requested URL returned error: 500

Hmm, the push is failing on the server side. Please post the debug log collected from a server with sudo flynn-host collect-debug-info.

Logs here:

It looks like you have a firewall enabled that is preventing communication between containers:

Get http://<IP_ADDRESS>:1113/host/jobs: net/http: request canceled while waiting for connection

You're right, I'd put ufw on as a solution to the firewall requirement. Rather annoying that this breaks container comms

Yeah, I don't know anything about ufw, but if you come up with a solution let us know and we can put it in the docs.

Ran across this: https://github.com/docker/docker/issues/1251, seems UFW touches all the iptables chains. Solution for me will be give up and just use iptables.


Add new category DevOps and new awesome list Monitoring.

https://github.com/crazy-canux/awesome-monitoring
DevOps category is used for Develop and Operation, it a new region about how to connect developer and operator work together.  And monitoring list is very import in DevOps, you can monitoring the network, OS, storage and applications.
By submitting this pull request I confirm I've read and complied with the below requirements.
Failure to properly do so will just result in the pull request being closed and everyone's time wasted. Please read it twice. Most people miss many things.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title. For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should include a short description about the list project/theme (not the list itself), and should be added at the bottom of the appropriate category.
The list I added

has been around for at least 30 days,
is the result of hard work and is the best I could possibly produce,
is a non-generated Markdown file in a GitHub repo,
is not a duplicate,
includes a succinct description of the project/theme at the top (example),
includes a project logo/illustration (whenever possible) at the top right of the readme (example). (The logo should link to the project website or any relevant website. The logo should be high-DPI, so set it to maximum half the width of the original image.),
only has awesome items with descriptions (Awesome lists are curations of the best, not of everything),
contains the awesome badge on the right side of the list heading,
has a Table of Contents section named Contents as the first section,
has an appropriate license (Meaning something like CC0, NOT a code licence like MIT, BSD, Apache, etc) (If you use a license badge, it should be SVG, not PNG),
has contribution guidelines,
doesn't include a Travis badge,
has been checked for inconsistent formatting, spelling, and grammar:

Each link description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent naming. For example, Node.js, not NodeJS or node.js.

Add category "DevOps" and new awesome list "Monitoring".

has been checked for inconsistent formatting, spelling, and grammar:

This clearly hasn't been done - there's a typo even in the description (operating system). Also github -> GitHub.
This list needs a lot more work creating better descriptions for items e.g. Check_mk official website. does not tell you what it is and why it's awesome.
Also, please put this under miscellaneous once this is ready to be resubmitted, a new category is only created for two or more items.
Add comment here when requirements are fulfilled.

Hi,
   I think there are some misunderstanding.
   It's not OS, it's MAC OS X.

  Check_mk is a monitoring application, belong to a German company.
  That's why the link is "check_mk official website."

For sure, some description need have more details.


Improve efficiency of Files.walk()

Walking a tree using Files.walk() is slow in the current implementation and likely uses too many calls to S3. The backend implementation may need to be more eager in collecting paths in groups.

Investigations reveal that calling Files.walk() will require many calls to S3 including a Head for every object (to get file metadata). These calls coming from multiple places is resulting in a large number of requests to generate new S3 clients.
A potentially simple way to speed up client creation would be to retain a cache of known regions for clients to prevent having to make a HeadBucket request per client creation.
We could also re-examine the idea of a client pool or cache with appropriate cautions about auto-closed clients.


String comparison: substring Missing text

The SQL example on the row titled "String comparison: substring" shows:
SELECT * FROM dependencies WHERE like "%bcd%"
when it should show:
SELECT * FROM dependencies WHERE name like "%bcd%"
to properly map to the Azure Monitor log query:
dependencies
| where name contains "bcd"

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

ID: 0b938908-1b0f-63e4-6e17-bccd57f8d3e8
Version Independent ID: 7edcd9e5-13ba-f7e4-f7cd-92412a28001f
Content: SQL to Azure Monitor log query cheat sheet
Content Source: articles/azure-monitor/log-query/sql-cheatsheet.md
Service: log-analytics
GitHub Login: @bwren
Microsoft Alias: bwren

@seantleonard Thanks for the feedback. We will work with the content owner to further review and update as appropriate.
@bwren Could you please take a look at it and make necessary corrections?

Signed off on pull request

#please-close


GO:0048775 - GO:0048783

These terms lack a namespace. Is this possibly an OBO-Edit problem?
Reported by: girlwithglasses
Original Ticket: "geneontology/ontology-requests/3185":https://sourceforge.net/p/geneontology/ontology-requests/3185

thanks www.movied.org


Update to Swift 3 Xcode 8b4

Addressed Xcode 8 beta 4 migration issues, updated tests and commented out two tests for you to verify if they're still valid.

@andreyz Thanks for the work. However, some work has already done with beta 4. I will also keep improving the Swift 3 support later.

@onevcat OK. Feel free to cherry-pick changes to tests from this PR, since your other branch isn't Swift 3 compatible tests.


Add support for TextInput clearTextOnFocus and selectTextOnFocus

Please select one of the following

[x] I am removing an existing difference between facebook/react-native and microsoft/react-native-macos :thumbsup:
[ ] I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos :thumbsup:
[ ] I am making a fix / change for the macOS implementation of react-native
[ ] I am making a change required for Microsoft usage of react-native

Summary
TextInput clearTextOnFocus and selectTextOnFocus were never supported on MacOS
https://reactnative.dev/docs/textinput#selecttextonfocus
https://reactnative.dev/docs/textinput#cleartextonfocus-ios
https://github.com/microsoft/react-native-macos/blame/e0e598e19c39bd7cb80b2aefd0ac5f19778721aa/Libraries/Text/TextInput/RCTBaseTextInputViewManager.m#LL62
On iOS, selectTextOnFocus has a custom implementation of selectAll that dispatched a selection.
https://github.com/facebook/react-native/blob/main/Libraries/Text/TextInput/Multiline/RCTUITextView.m#L181-L190
For NSTextInput, selectAll works without needing the custom dispatch.
For NSTextField, the default behavior is to select all when focused. This change added support for removing the selection if selectTextOnFocus is false.
NOTE: Text selection disappears once a MouseDown is received. This is native text input behavior.
This also fixes a bug w/ MultiLineTextInput where the selection box was retained even after losing focus.
https://user-images.githubusercontent.com/96719/202796169-d04156e3-718a-4fd8-9583-0112e16bcf12.mp4
Changelog
[macOS] [Fix] - TextInput support for clearTextOnFocus and selectTextOnFocus
Test Plan
https://user-images.githubusercontent.com/96719/202794592-31c02063-1b18-4047-bf99-6413c01b3325.mp4

Need to fix build error.

Oops, forgot that this still needs to support iOS as well. Will add back the older path and test.

Fixed on iOS
https://user-images.githubusercontent.com/96719/203449900-363ad060-ed39-48c6-89e9-15c567ba9fce.mp4

I don't see anything regarding clearTextOnFocus except enabling it for macOS in RCTBaseTextInputViewManager.m. If this prop just worked as is, can you explicitly mention that?

Pulled your branch and tested the props, selectTextOnFocus worked fine on iOS, but not on macOS :/

Pulled your branch and tested the props, selectTextOnFocus worked fine on iOS, but not on macOS :/

There is some nuance to how this works on desktop. Since the text input can get focus when clicked, the section will also disappear if you click into it.
Slowed down example:
https://user-images.githubusercontent.com/96719/207995918-f9217241-6cee-4ace-96be-8725e3e8b691.mp4
If you tab into either single or multiline text input, it will select the text. Note, you have to reverse-tab to select the multiline text field since the previous text input will capture additional tabs
https://user-images.githubusercontent.com/96719/207995344-d9b6b06f-85d1-4bc6-a8ba-18f78daadfaa.mp4
Clicking on the view, but not focusing the TextInput will also select the text.
https://user-images.githubusercontent.com/96719/207995997-c1af1b2f-0bbb-4916-9e0d-f4e649830493.mp4

@shwanton by the way, you can use Ctrl+Tab to tab in / out of text fields that capture tab


How to improve panda grasp?

Below, I have a video of a motion-planning-based demonstration (please ignore the bad quality, it is what RecordEpisode used by default). The grasp is done using PandaArmMotionPlanningSolver(...).close_gripper(), which evidently sets the panda gripper action to -1. As you can see, while the grasp is successful, the object slips. I see the base Panda agent has properties that can be overwritten - for gripper stiffness, damping, force limit, friction -- none of them seem to be affecting the quality of the grasp. Do you have any recommendations?
https://github.com/user-attachments/assets/02a51126-df36-48c6-835f-6e99e63c449a

It is possible the object might be too heavy, you can try modifying the physical material of the loaded YCB object. The grippers already have a high friction value that should enable it to grasp most things.
It's also possible the grasp is not good, maybe it needs to grab a different part of that bottle.

@dennisushi has your issue been resolved?


Fixed selection filtering for bloom

Right now you can apply certain post process effects to just one feature. The bloom shader doesn't do any check to allow you to apply it to just to the selected feature as you would expect. Bloom post-processing is fixed by adding in the proper selection checks.
This is in reference to https://github.com/AnalyticalGraphicsInc/cesium/issues/7984
I was able to test using this sandcastle

Thanks for the pull request @ProjectBarks!

:heavy_check_mark: Signed CLA found.
:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

@OmarShehata or @lilleyse is this good with you?

This looks good at first glance. It still won't allow you to select entities as features to apply the post processing to (as Brandon notes here https://github.com/AnalyticalGraphicsInc/cesium/issues/7984#issuecomment-520919370) but it's still a useful fix.
@ProjectBarks can you:

Check if any of the other post processing effects are missing a selected snippet like this? Would be good for consistency if it's easy to have them all respect this array.
Post more details about what you've found about why "only some entities/primitives" can be selected? You can put that in the linked issue. I thought it was just that you had to supply a primitive but it sounds like it's not that simple?

Responded in github issue.

@ProjectBarks please merge in master.
Where are we with this, is it just waiting for review?  @lilleyse need to take a look at this or is @OmarShehata comfortable with these changes?

This looks good to me.


Add forwards compat tests

@pakrym I think I may add a few more properties to skip different tests (lot of duplication right now). Besides that, I think this is ready for review.

Add a test that verifies that we use old handler

Use IISTestSiteFixture instead of deploying in test

Test failure https://github.com/aspnet/IISIntegration/issues/1447


InsertAt (issue #306)

any problem with this PR ?

@fsateler all adjusts done! thanks!

@atifaziz remove System.Linq. we are in time for 2.8.0?

@atifaziz renamed to Insert, added readme.md and on release notes. we think are ready for merge.

@leandromoh Thanks!
I know @fsateler is busy so I have gone ahead and merged without awaiting his approval. He had some documentation comments that seem to have been addressed.

:memo: This PR was for issue #306.


max_input_vars in php.ini should be set bigger

Hi,
When using a multi-language plugin, the php variable describing the menu can get big. I add the problem that it was bigger than the php basic limit. So I think this limit should be made bigger by default, something like
max_input_vars = 4000
It will not be a performance issue I think, and could help avoid troubles! In my case, the trouble was that when I tried to save the menu after editing it, it would be cut (i.e. missing some entries).
Best,
Manu

You can create user.ini in htdocs folder, and paste your php setting into it.

@lemartinet Sorry for a delayed reply.
We recommend user fix this own end as suggested by @gagomap .


Update SDK for new API version

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.HardwareSecurityModules

Please DO NOT MERGE! Swagger for this version is reviewed but not merged yet, since feature is still under development! https://github.com/Azure/azure-rest-api-specs/pull/26326


Fix ncgen handling of big data sections

The current ncgen does not properly handle very large
data sections. Apparently this is very uncommon because
it was only discovered in testing the new zarr code.
The fix required a new approach to processing data sections.
Unfortunately, the resulting ncgen is slower than before
but at least it is, I think, now correct.
The added test cases are in libnczarr, and so will
not show up until that is incorporated into master.
Note also that fortran code generation changed, but
has not been tested here.
Misc. Changes

Cleanup error handling in ncgen -lc and -lb output
Cleanup Makefiles for ncgen to remove unused code
Added a program, ncgen/ncdumpchunks, to print
the data for a .nc file on a per-chunk format.
Made the XGetOpt change in PR https://github.com/Unidata/netcdf-c/pull/1694
for ncdump/ncvalidator

Hi Dennis, can you elaborate on "ncgen does not properly handle very large data sections" in terms of what the problem was/how it might manifest?

I can, but it would take a lot of space; its complicated.

Ok, I'll ask you about it offline; I'm curious, but no need to fill things up here.

You are right that the details should be somewhere, but I am not
sure where it should go.

A summary in the release notes in terms of how the error would manifest (data corruption, slow writes, etc) wouldn't go amiss, and we can have a discussion about the technical aspects later, maybe?

ok

See revised RELEASE_NOTES.

Thanks Dennis!


Iterative Doc improvement: Achievement Icons Tutorial Edition

First of all, I removed the submodule from the branch because it was giving me permission errors every time I tried to synchronize the branch, and as we talked about in Discord there doesn't seem to be a reason for it to be there. If something breaks we can revert commit 7ab4d22.
But this pull request is mostly a result of me going through the Achievement Icons tutorial and fleshing it out a little bit, making a few minor adjustments or (what I think are) clarifications, making sure all links are working and valid, and maybe even correcting an error or typo here and there in related files.

You are killing it, friend!  Thank you!


[Fix #11444] Fix a false positive for Lint/ShadowingOuterLocalVariable

Fixes #11444.
This PR fixes a false positive for Lint/ShadowingOuterLocalVariable when using numbered block parameter.
It also fixes the following error as a side effect:
array.each {
  bar = _1
}.each { |bar|
}

% bundle exec rubocop example.rb --only Lint/ShadowingOuterLocalVariable -d
(snip)

Scanning /Users/koic/src/github.com/koic/rubocop-issues/11448/example.rb
An error occurred while VariableForce cop was inspecting /Users/koic/src/github.com/koic/rubocop-issues/11448/example.rb.
undefined method `when_type?' for nil:NilClass
/Users/koic/src/github.com/rubocop/rubocop/lib/rubocop/cop/lint/shadowing_outer_local_variable.rb:86:in `variable_node'

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Looks good. Thanks!


Difference in loading times between lsdb.read_hipscat and pyarrow.dataset.to_table

@troyraen report that loading CosmoDC2 had large difference in loading times between lsdb.read_hipscat and pyarrow.dataset.to_table (see figure below). This is with ADASS tutorial branch.
The definitions are: `` defining "hot" as when the data was last accessed less than 10 minutes prior; "warm" 15min - 1hr prior; and "cold" about 24 hours prior''

We have been unable to recreate this issue. Potentially this is a feature of CosmoDC2 dataset which was not tested yet. Making this ticket to capture this investigation that is turning out somewhat bigger than a simple fix. Same notebook as specified in https://github.com/astronomy-commons/lsdb/issues/121

Interesting that you were unable to reproduce. I suppose there could also be differences in our system setup that affect this. I also wouldn't rule out that it was just some combination of small-number stats and inconsistency across runs on my part. (I kept starting another run because the results kept being curious, but I didn't start out intending to do rigorous testing or record keeping.)
We're planning to regenerate the CosmoDC2 catalog using the new version of hipscat-import, and then we can also update the notebook this code came from to use the new lsdb. I can put the data in an S3 bucket where we can both test against it as soon as I have it, if that's helpful.

Hello @troyraen, thank you so much for the report!
I've tried to reproduce the issue, but with the different catalog and, therefore, different filters applied. It would be really helpful to have the same catalog you use. I can hipscat-import myself, if you point me to the original dataset you use.

Hi @hombit, unfortunately the files used to make this CosmoDC2 hipscat catalog are not publicly available. I checked with some folks internally about releasing them, but ran into some issues. I'm fairly certain I can make them available to you privately for testing. If you're interested, email me (raen[at]ipac.caltech.edu) and I can give you more info about the files and figure out how to transfer.

Thank you @troyraen, I've just written you privately

@hombit Can you shortly summarize the investigation here? I believe that we concluded to close this one without resolving at this stage, as it is due to different best defaults for lsdb and pyarrow?

@nevencaplar yes, I believe it is correct. I've found that in both cases of LSDB/Dask and pyarrow one could optimize number of parallel jobs to go really close to the performance limited by the read-out speed. It doesn't mean that we cannot do better : we can and hopefully will do after migration to dask-expr


fps ulocker not working

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
Im getting no fps unlock only down drop to 40 fps or maybe sometimes 60 Its so flustrating bc i did try everything and there is no help to do this and i tried rfo and it worked and fps unlocker and it worked to so please fix this bug

Have you read through https://github.com/pizzaboxer/bloxstrap/wiki/Roblox-is-still-capped-to-60-FPS-after-raising-the-limiter?

Issue has been awaiting clarification for over a month, closing as stale. If you have anything further to add, just respond and I'll reopen.


OSOE-647: Under Orchard Core 1.6, menu items generated via MainMenuNavigationProvider are prefixed with /Admin in Lombiq.BaseTheme

OSOE-647
Fixes #73

For clarity: Which part of this PR exactly fixes the broken behavior? I some movement around how we access UrlHelper but it's unclear to me how that fixes the problem.

For clarity: Which part of this PR exactly fixes the broken behavior? I some movement around how we access UrlHelper but it's unclear to me how that fixes the problem.

Using IUrlHelper.Content(path) is the actual fix. Or perhaps better described as a workaround, because this means all the tenant-relative URLs are converted into absolute paths, so we have opted out of using the NavigationItem's path resolution.


Setting ClientWebSocketOptions

Trying to set KeepAliveInterval, I am using 3rd parameter to WithUrl() like this:
a => a.WebSocketConfiguration(new ClientWebSocketOptions().KeepAliveInterval = TimeSpan.FromSeconds(3))
And I get
'ClientWebSocketOptions' does not contain a constructor that takes 0 arguments
Taking a look at its referred definition, wich in my case is

Assembly System.Net.WebSockets.Client, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a

I see it has only the default contructor (i.e. no constructor defined)
So I would say it should work...
Can you please, help me?
UPDATE:
When hitting F12 to see the definition of the ClientWebSocketOptions class I also see that System.Net.WebSockets.Client assembly comes from a weird path

xxx.nuget\packages\microsoft.netcore.universalwindowsplatform\6.0.8\ref\uap10.0.15138\System.Net.WebSockets.Client.dll

especially since I am targeting the 16299 Fall CreatorsUpdate Windows version...
If that is the issue than how can I set VS to look in the proper place?

You can't construct the object unfortunately and ClientWebSocketOptions is defined in the base class library.  Like so:
var connection = new HubConnectionBuilder()
    .WithUrl("http://mysite.com/myhub", options => {
        options.WebSocketConfiguration = (webSocketOptions) => {
            webSocketOptions.KeepAliveInterval = TimeSpan.FromSeconds(3);
        };
    })
    .Build();

I'd also be interested in knowing why you need to adjust the keep-alive interval on the WebSocket. This interval is not used for detecting disconnected connections in SignalR. It's part of the WebSocket protocol for preventing a proxy from terminating the connection. Are you seeing a proxy terminating your connections?
Closing this as the question has been answered. Feel free to comment further if you need clarification on something! We can always re-open the issue if there's something to fix here.

Thank you for your reply.
No, I don't see proxies terminating my connection.
As a matter of fact I only want to keep both parties informed if the other one goes offline.
Is enough the KeepAliveInterval option  from AddSignalR on server side?
 services.AddSignalR(
                  options =>
                  {
                      options.KeepAliveInterval = TimeSpan.FromSeconds(3);
                  });

Yes, I would use the SignalR KeepAliveInterval for that. On the client you will also need to set HubConnection.ServerTimeout to a value higher than the keep-alive interval. The ServerTimeout value is how long the client waits between receiving messages before declaring the server disconnected. I recommend setting this to double the KeepAliveInterval, so that you can withstand some network delays. So 6 seconds in your case.
Take note: Network delays can be severe and significant, so the shorter you make your timeouts, the more likely a client or server is to terminate the connection in a high-latency scenario. If you're not very careful you may end up with clients frequently reconnecting because they are timing out due to your short timeouts and network delays.
Also, in 2.1, this will only work for the client detecting the server is disconnected. If the client goes dark, the server will not consider it disconnected until the TCP connection closes (which on Windows is relatively short, but on Linux can be quite a long time). In 2.2 we are adding a similar timeout for the server to detect a disconnected client.

What is the Windows TCP connection timeout (maybe with a link to that info)?
I found all kind of resources online, but I will be more than thankful for an advised information.

I don't have a specific link for you either. In our testing I noticed a timeout within about 15 seconds, but only if we were sending data frequently (which the server-to-client pings will do for you)

Ok, having a result based on some tests it is something to rely on. Thank you for sharing it.
Let's say, that hopefully until the 2.2 release I can live with this.
I have some more questions though:

What are the case here? A 3 seconds ping interval will cause a detection in about 15 seconds.
A longer ping interval will only increase the detection interval, right?
When you say client goes dark, it means:
a) disconnected (like an unplugged ethernet cable)
b) not disconnected, but just not receiving ping replies from it?
If answer to question 2 is b), then for a regular disconnect, the server will receive one of the ConnectionClosed Exceptions?
Just out of curiosity and only if you want to answer it. Is it on purpose that such a detection is not implemented? I see it as something basic, the server to be aware that one of its clients is down.

What are the case here? A 3 seconds ping interval will cause a detection in about 15 seconds.
A longer ping interval will only increase the detection interval, right?

For detecting server disconnection from the client, you completely control the timeout in 2.1, you just set the ServerTimeout value on the HubConnection. Of course, you need to make sure the server's KeepAliveInterval is configured to be lower than the ServerTimeout value, or the server won't ping fast enough and the client will think it's gone even when it's there.
In 2.1, there is no pinging from the client to the server, so there's nothing you can control here. The server's KeepAliveInterval helps you a bit though as most operating systems only reveal that a connection has "gone dark" (see below) when you try to send to it, so if the server is sending pings every  X seconds, and the OS times out connections after Y seconds on no activity, you can expect to know that the client has disconnected in X+Y seconds (the OS will timeout after Y seconds, but the server won't be informed until it send a ping frame, up to X seconds later).

When you say client goes dark, it means:
a) disconnected (like an unplugged ethernet cable)
b) not disconnected, but just not receiving ping replies from it?

Those scenarios are identical in how they manifest. There are two possible ways a TCP connection can be terminated:

One party sends a FIN (Finish) or RST (Reset) frame to the other. This occurs if your process crashes, or the machine is "gracefully" shutdown (i.e. you shut it down through the OS shutdown mechanism)

One party simply "goes dark" and just never sends any more messages. The other party is sending messages but they are never arriving and never being acknowledged. This occurs if you unplug the network cable (since there wasn't a chance for the OS to formally terminate the connection, since the cable was yanked), or if you cut the power to the machine abruptly, or if some intermediary router or proxy fails in the same way (since the intermediary will stop forwarding your messages). Most OSes will forcibly terminate the connection when the other side hasn't acknowledged anything within some time interval, but this varies greatly from OS to OS.

If answer to question 2 is b), then for a regular disconnect, the server will receive one of the ConnectionClosed Exceptions?

For a "standard" disconnect where the client/server disconnects formally (this means the client process either terminated normally or it crashed and the OS will close the TCP connection formally on behalf of the now-crashed process) you'll get informed immediately about the connection termination (via OnDisconnectedAsync on the server or an exception on the client.

Just out of curiosity and only if you want to answer it. Is it on purpose that such a detection is not implemented? I see it as something basic, the server to be aware that one of its clients is down.

Detecting these scenarios is a non-trivial networking problem. You have to approach every networking scenario as though the worst things could happen. Nodes could never properly inform each other than they have disconnected, they may simple stop responding. Since there is no guaranteed way to be informed when a node disconnects, the only way to reliably detect disconnection is to keep asking the client if it is connected and if the client fails to respond, consider it disconnected. This seems trivial between two machines you control on the same network because the latency is very low and everything generally work smoothly. However, as soon as you hit the public Internet, you start seeing all kinds of problems. Network latency varies dramatically from situation to situation.
We simply didn't have the time or resources to implement this right in 2.1. It's something that requires user feedback. We need to know how it works in the real-world before we can really consider the functionality "baked". This is why it's already been implemented in the 2.2 codebase, and will be available in the first preview, so we can get the necessary feedback on how appropriate it is.
It's also possible to implement this kind of timeout yourself in 2.1, though it requires a lot more logic. In OnConnectedAsync you get the connection and you can always start a background process to track how long it's been since the last Hub method was called and terminate the connection if that gets too large. Each Hub method can just update that "time since last method call" value when it is invoked.

Thanks a lot for your in depth answer!

No problem at all!

No, however you can try out our nightly bits https://github.com/aspnet/Home#daily-builds

@BrennanConroy  According to this: https://github.com/aspnet/SignalR/releases/tag/1.0.2 (https://github.com/aspnet/SignalR/pull/2309 -  https://github.com/aspnet/SignalR/commit/736b7f5042b080958304986088cc21a8c43177ae), might be found in 1.0.3 (https://github.com/aspnet/SignalR/releases/tag/1.0.3), right?

No, I don't see how any of those point to that.
https://github.com/aspnet/SignalR/commit/736b7f5042b080958304986088cc21a8c43177ae shows as being in release/2.2 and tag 1.1.0-preview1.

Oh, alright. I missread it.

We do have a preview of 2.2 available now: https://www.npmjs.com/package/@aspnet/signalr . The version is 1.1.0-preview1-35029 (the version numbers differ because '2.2' refers to the version of the whole ASP.NET Core framework, this is the first minor release for SignalR so its package version will be 1.1).

Thank you!
I attempted to try that, but I've seen the implication on server side and decided to wait for the moment.


NIS db need to be updated after adding users

[root@io-install ~]# make -C /var/yp

If this is used - we should have a variable to allow disabling it.
when: arc_frontend_nis

Like this?
In group_vars/grid/grid.yml
arc_frontend_nis: true
and

name: Update NIS DB
command: /usr/bin/make -C /var/yp
delegate_to: install
when: arc_frontend_nis

And to false in defaults

Nice move with delegate btw :)

thanks :)
Solved on e0c09dea1491448f45c4bffd35fd9d3552f4483e


Does not work with Laravel 5.7

When trying to composer require the project there is a conflict with http-foundation versions.
`Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for codemash/laravel-socket ^1.0.0 -> satisfiable by codemash/laravel-socket[1.0.0].
- Conclusion: remove symfony/http-foundation 4.1.x-dev
- codemash/laravel-socket 1.0.0 requires cboden/ratchet ^0.3.5 -> satisfiable by cboden/ratchet[v0.3.5, v0.3.6].
- cboden/ratchet v0.3.5 requires symfony/http-foundation ^2.2|^3.0 -> satisfiable by symfony/http-foundation[2.2.x-dev, 2.3.x-dev, 2.4.x-dev, 2.5.x-dev, 2.6.x-dev, 2.7.x-dev, 2.8.x-dev, 3.0.x-dev, 3.1.x-dev, 3.2.x-dev, 3.3.x-dev, 3.4.x-dev].
- cboden/ratchet v0.3.6 requires symfony/http-foundation ^2.2|^3.0 -> satisfiable by symfony/http-foundation[2.2.x-dev, 2.3.x-dev, 2.4.x-dev, 2.5.x-dev, 2.6.x-dev, 2.7.x-dev, 2.8.x-dev, 3.0.x-dev, 3.1.x-dev, 3.2.x-dev, 3.3.x-dev, 3.4.x-dev].
- Can only install one of: symfony/http-foundation[4.1.x-dev, 2.2.x-dev].
- Can only install one of: symfony/http-foundation[4.1.x-dev, 2.3.x-dev].
- Can only install one of: symfony/http-foundation[4.1.x-dev, 2.4.x-dev].
- Can only install one of: symfony/http-foundation[4.1.x-dev, 2.5.x-dev].
- Can only install one of: symfony/http-foundation[4.1.x-dev, 2.6.x-dev].
- Can only install one of: symfony/http-foundation[4.1.x-dev, 2.7.x-dev].
- Can only install one of: symfony/http-foundation[4.1.x-dev, 2.8.x-dev].
- Can only install one of: symfony/http-foundation[4.1.x-dev, 3.0.x-dev].
- Can only install one of: symfony/http-foundation[4.1.x-dev, 3.1.x-dev].
- Can only install one of: symfony/http-foundation[4.1.x-dev, 3.2.x-dev].
- Can only install one of: symfony/http-foundation[4.1.x-dev, 3.3.x-dev].
- Can only install one of: symfony/http-foundation[4.1.x-dev, 3.4.x-dev].
- Installation request for symfony/http-foundation 4.1.x-dev -> satisfiable by symfony/http-foundation[4.1.x-dev].`

Hey,
It's been over two years since I've written PHP. Unfortunately, time does not allow me nowadays to check into the issue. I'd be more than happy to accept a pull request if this package can be of use to you.
Cheers.


Tags are case sensitive and cause issues

For example if we have the tags Git and git then this will cause issues. For example when making the tag pages we will only get the posts with Git and the git tagged posts don't appear at all in the tag feed.

This is ugly and really needs to be fixed, I don't exactly like forcing the tags to be set entirely in the frontmatter as this seems like it will make it easy for typos and mistakes to creep in.
I see a couple of "solutions"

The stackoverflow way of making tag synonyms https://stackoverflow.com/tags/synonyms  seems best but probably will be painful in Gatsby
Preprocess tags to something like titlecase


Better Compiler Errors

Right now the error messages don't really give lines of code in the user's code, but from the compiler's attempt to read the user's code ast at a certain point. User code should return compiler errors the same way that Elixir does. It would be nice if Elixirscript could reuse what Elixir uses for this.

Since #210 now puts code through Elixir compiler, will get back warnings and errors with line numbers


Data Model Profile - Presentation of the values from the Enumeration Data Type not consistently sorted

Describe the bug
Enumeration values are not shown in any sorted order when used in profiles (for example data model profile). Actually it is unpredictable what we will be shown, different at different times.
To Reproduce
Steps to reproduce the behavior:

Create a data model profile
Create an enumeration type in the profile with some values
Define element in the profile to be of the type created in 1)
Edit Data model that is using data profile created in step 1 multiple times.
Notice that values for the drop down list (matching that enumeration data type) is not showing values in any order. Each time user enters the edit screen, values are shown in a different order.

Expected behavior
Profile field should show values from the enumeration in an alphabetical order, or order specified in the enumeration.
Screenshots
Example of the enumeration:

One data model:

Second data model:

Back to the first data model (second attempt)

MDM Version
CORE/UI: 4.10/6.6.0

@jamesrwelch I assumed this is a UI issue, however we have not had the time to investigate yet.


Workload with sidecar can't be edited

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

Deploy Workload
Add a sidecar to the Workload just created
Edit this Workload

Result:
Unable to edit this Workload, as shown below

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): rancher/rancher:master-head
Installation option (single install/HA):single

Version: master-head (v2.3) (8/13/19)
NOTE: I tried to reproduce in v2.2.7 but could not; this looks like it was just an issue in earlier master-head so there is no way I can go back and try to repro.
v2.2.7 screenshot:

Validation:
Follow the steps and attempt to edit the workload with a sidecar.
This works without any issues I can see the selection screen to chose what I want to upgrade.


Get exception with TestType is not Type

any help?

I changed the code to print only an error and continue a program in a latest commit.
The bug is still there and might be found at other places.

hmmm..
Still can't work.

Worked!, amazing job!


APPLICATION FOR VOLUNTEER OF AIRCASH TEST

Hello, I would like to participate in the AirCash product test as a volunteer.
I have a good command of English and am proficient in Google translation software. Basic knowledge of blockchain; Strong learning ability, like to contact new things; Home office free working hours. I am looking forward to participating in this product test and contributing my meager strength. Thank you very much!

I like to apply as a volunteer for the ongoing test.
On Wed, Sep 22, 2021, 5:00 PM xiaoran911003 @.***>
wrote:

Hello, I would like to participate in the AirCash product test as a
volunteer.
I have a good command of English and am proficient in Google translation
software. Basic knowledge of blockchain; Strong learning ability, like to
contact new things; Home office free working hours. I am looking forward to
participating in this product test and contributing my meager strength.
Thank you very much!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Aircoin-official/AirCash/issues/90, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUORVXGUOEQG6TKN7IR5ZZLUDH4RRANCNFSM5ERVFVSA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Oh, that's cool.

I would like to apply for volunteer.. i have experience being a moderator on a community.

Anyone who applied for the AirCash testing please join the discord channel for test volunteers.
https://discord.gg/eRSY7NtxZA