Issue in unpacking tensor or list of tensors

Description
While passing pred to self.criterion in https://github.com/ibro45/lighter/blob/bc91f0aee316e4c72c0f5984df7e2605202bcc40/lighter/system.py#L252, the code breaks if anything other than a tuple, list that can be unpacked is passed. If a scalar tensor is passed, it would break as well.
Steps to Reproduce
Run the code with anything other than tuple or list predictions
Expected outcome
The reason this doesn't work is python tries to unpack the object before evaluating the conditional expression
Attached a sample below and the error,
import torch

def test1(a):
    print(a)

def test2(a, b):
    print(a, b)

val_tuple = (2, 3)
val_dict = {
    "a": 2,
    "b": 3
}
val_scalar = torch.Tensor(2)

test2(*val_tuple if isinstance(val_tuple, (list, tuple)) else val_tuple)
test1(*val_scalar if isinstance(val_scalar, (list, tuple)) else val_scalar)
test1(*val_dict if isinstance(val_dict, (list, tuple)) else val_dict)

The output of this is,

2 3
Traceback (most recent call last):
  File "test.py", line 19, in <module>
    test1(*val_scalar if isinstance(val_scalar, (list, tuple)) else val_scalar)
TypeError: test1() takes 1 positional argument but 2 were given

Potential Solution
Keep the system consistent with only pred being passed to the model and the model or a wrapper can handle the input type

The fact that they're one-liners is what causes the issue. Specifically, the asterisk does apply on the variable right after it, but over the whole statement. Essentially, it's not *val_scalar, but * over the whole thing val_scalar if isinstance(val_scalar, (list, tuple)) else val_scalar
This fixes it.
import torch

def test1(a):
    print(a)

def test2(a, b):
    print(a, b)

val_tuple = (2, 3)
val_dict = {
    "a": 2,
    "b": 3
}
val_scalar = torch.Tensor(2)

# Tuple
if isinstance(val_tuple, (list, tuple)):
    test2(*val_tuple)
else:
    test2(val_tuple)

# Tensor scalar
if isinstance(val_scalar, (list, tuple)):
    test1(*val_scalar)
else:
    test1(val_scalar)

# Dict
if isinstance(val_dict, (list, tuple)):
    test1(*val_dict)
else:
    test1(val_dict)


"Top Authors"

we can add top authors based on either sum of views count from all posts of a particular user.
This will be shown in index page side widget.
For more queries feel free to ask
Thank you! Keep contributing.

Hi, I want to work on this, can you assign it to me?

Hello @Mellowor, I have assigned this issue to you
For reference,

there is a 'posts' table that has "post_views_count" , "post_author"
"users" table has "username" and "user_firstname" "user_lastname"

For each post_author you have to sum the views from all posts and show the top authors names in order

Hi, thanks for assignation and advice.

Hi, thanks for assignation and advice.

Mention Not :)

Hi, I already am familiar with code and make it run locally. Tomorrow I work on top authors. I also want to ask you if i could add time filter (for example Top Author for past day, week, year)?


hero_replaceViewController don't want the navigationbar animation

Notice that when grid to list or list to grid, cell or item animation is perfect.
But in my project I need to make it like one page, so i don't need the navigation bar animation .
How can I do this?
The pic is view controller pushing.

Thats the default UIKit behavior. You can however, replace the entire UINavigationController with another one containing the gridView.

closing out old issues, feel free to reopen


feat: new frontend system

🚨 Proposed changes

Please review the guidelines for contributing to this repository.

[[Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.]]
⚙ Types of changes
What types of changes does your code introduce? Put an x in the boxes that apply

[ ] New feature (non-breaking change which adds functionality)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
[ ] Refactor

Do you have any idea when this MR will be released?


Prebuild Entity DateTimeV2 Bug

DateTimeV2 converts back wrong values if no complete date is given
For example :"XXXX-04-15" is still returned as "2019-04-15"
and also if month is missing it just randomly picks one....
Another example:
"Dienstag 11:00 uhr" (Tuesday 11 o Clock)got recognized but translated to
2020-02-11 instead of  2020.03.13
the timex output is completely screwed here XXXX-WXX-2.
The Time is also completely missing
"Mittwoch 12:00 uhr" (Wednesday 11 oclock"
2020-02-12 instead of 2020-03-18
And sometimes when saying "18.4"
i sometime get "XXXX-04-18" and sometimes "04-18""
The Response seems completely random at times-.-

@jhakulin is there anybody in particular who could help with this isssue?

@SOliasS If you can please send us the repro steps ?
Thanks

@amitkumarshukla What steps do you need?
Do you want other/ more example which times support is missing?

@amitkumarshukla any Update?

It's not completely clear to me where the result is getting mangled.
From the question I'm assuming you've got an intent with an entity of type DateTimeV2 in it and are trying to recognize it.
When the date comes back wrong, is it wrong in the intent JSON returned, or in the recognized speech that's on the result.getText()?
Can you send an example of the text from the result and the JSON for what's in the LanguageUnderstandingServiceResponse_JsonResult for the entity?
I'm trying to disambiguate if the problem is in the speech->text pipeline or in the text->LUIS result pipeline.

There were two diffrent problems i think...
I think the First one is working now "15.4" => 15.04.2020
{
"query": "15.4.",
"topScoringIntent": {
"intent": "None",
"score": 0.231632113
},
"entities": [
{
"entity": "15.4.",
"type": "builtin.datetimeV2.date",
"startIndex": 0,
"endIndex": 4,
"resolution": {
"values": [
{
"timex": "XXXX-04-15",
"type": "date",
"value": "2020-04-15"
},
{
"timex": "XXXX-04-15",
"type": "date",
"value": "2021-04-15"
}
]
}
},
{
"entity": "15",
"type": "builtin.number",
"startIndex": 0,
"endIndex": 1,
"resolution": {
"value": "15"
}
},
{
"entity": "4",
"type": "builtin.number",
"startIndex": 3,
"endIndex": 3,
"resolution": {
"value": "4"
}
}
]
}
The Second one is still broken "Dienstag 11 Uhr" results in strange results"2020-02-11" instead of "26.05.2020" here the problem seems that the Time is recognized as a date and it tries to find a tuesday which matches instead of recognizing that it is a day and a time combined....
{
"query": "dienstag 11:00 uhr",
"topScoringIntent": {
"intent": "None",
"score": 0.296005666
},
"entities": [
{
"entity": "dienstag 11",
"type": "builtin.datetimeV2.date",
"startIndex": 0,
"endIndex": 10,
"resolution": {
"values": [
{
"timex": "XXXX-WXX-2",
"type": "date",
"value": "2020-02-11"
},
{
"timex": "XXXX-WXX-2",
"type": "date",
"value": "2020-08-11"
}
]
}
},
{
"entity": "11",
"type": "builtin.number",
"startIndex": 9,
"endIndex": 10,
"resolution": {
"value": "11"
}
},
{
"entity": "00",
"type": "builtin.number",
"startIndex": 12,
"endIndex": 13,
"resolution": {
"value": "0"
}
}
]
}

When using numbers instead of Dates it is working as expected
{
  "query": "15.4. 11:30 uhr",
  "topScoringIntent": {
    "intent": "None",
    "score": 0.6714722
  },
  "entities": [
    {
      "entity": "15.4. 11:30 uhr",
      "type": "builtin.datetimeV2.datetime",
      "startIndex": 0,
      "endIndex": 14,
      "resolution": {
        "values": [
          {
            "timex": "XXXX-04-15T11:30",
            "type": "datetime",
            "value": "2020-04-15 11:30:00"
          },
          {
            "timex": "XXXX-04-15T11:30",
            "type": "datetime",
            "value": "2021-04-15 11:30:00"
          },
          {
            "timex": "XXXX-04-15T23:30",
            "type": "datetime",
            "value": "2020-04-15 23:30:00"
          },
          {
            "timex": "XXXX-04-15T23:30",
            "type": "datetime",
            "value": "2021-04-15 23:30:00"
          }
        ]
      }
    },
    {
      "entity": "15",
      "type": "builtin.number",
      "startIndex": 0,
      "endIndex": 1,
      "resolution": {
        "value": "15"
      }
    },
    {
      "entity": "4",
      "type": "builtin.number",
      "startIndex": 3,
      "endIndex": 3,
      "resolution": {
        "value": "4"
      }
    },
    {
      "entity": "11",
      "type": "builtin.number",
      "startIndex": 6,
      "endIndex": 7,
      "resolution": {
        "value": "11"
      }
    },
    {
      "entity": "30",
      "type": "builtin.number",
      "startIndex": 9,
      "endIndex": 10,
      "resolution": {
        "value": "30"
      }
    },
    {
      "entity": "4.",
      "type": "builtin.ordinal",
      "startIndex": 3,
      "endIndex": 4,
      "resolution": {
        "value": "4"
      }
    }
  ]
}

Thanks, the JSON was extremely helpful.
We're making progress tracking this down.

The root cause looks to be an issue in the text recognizer LUIS is using. I've opened https://github.com/microsoft/Recognizers-Text/issues/2123 to track it and will work to get it triaged.
Thanks for the help here.


Duplicate example on keyIsPressed reference page

Most appropriate sections of the p5.js website?
Reference
What is your operating system?
Windows
Web browser and version
Chrome 131.0.6778.86
Actual Behavior
There is a duplicated example. The first and second examples are identical.
Expected Behavior
I was expecting to see unique examples, so I kept looking for a difference, and found none. The redundant example could be deleted, or else a third unique example could replace it.
Steps to reproduce
Just go to https://p5js.org/reference/p5/keyIsPressed/ and you can see the issue.
Would you like to work on the issue?
Yes

Hi, can I work on this issue? I have a PR ready!


Make cobra args help info to uppercase.

.

/retitle dry-run cli flag to use uppercase
/ok-to-test
/lgtm

@yanggangtony  would you please update the docs by running the make commands?

@a7i
Thanks for the review and quick response.
Rebased it.

/lgtm
/approve
Thank you for your contribution!


Cannot be played when Z and X keys are browser shortcuts!

In Firefox, Vivaldi and probably in all browsers based on the Chromium core, at least, the game cannot be played because Z and X are the keys used to go to the last/next page in active tab history. Otherwise, they will be ignored by the browser, and not passed to whatever script is running in a site, except to writing in forms.
A bad solution is to change 4 lines in the archive src/configs/gameConfig.js to be:
[...]
        Z: {
            CODE: 90,      // change the letter inside these single quotes
            KEY: 'Q',
        },
        X: {
            CODE: 88,
            KEY: 'W',      // change the letter inside these single quotes
        },
        COMMA: {
            CODE: 188,
            KEY: '1',      // change the letter inside these single quotes
        },
        DOT: {
            CODE: 190,
            KEY: '2',      // change the letter inside these single quotes
        },

[...]

Thanks for the info. I'll see if I have the time to look at this soon. This is an easy fix, if you want to get it running locally, but we have an issue for configurable keymaps #1, that should be a more permanent solution.


Update OGNL 3.1.x build configuration, enhance unit test and cleanup restore method

Update OGNL 3.1.x build configuration, enhance unit test and cleanup restore method.
pom.xml changes:

updated maven-surefire-plugin 2.3 -> 2.22.1
updated maven-clean-plugin 2.1.1 -> 2.6.1
updated junit 4.9 -> 4.12
updated easymock 2.3 -> 2.5.2
added defaultGoal to build

Code changes:

added additional tests to PrivateMemberTest (relevant to PR#58/PR#59/PR#60)
minor cleanup for DefaultMemberAccess restore method

LGTM 👍

Do you plan to port some of those changes to the master branch?

I will push a new release


Increment docs to 1.19.2

Path to page with content (do not include domain name):
/en/os
What content is incorrect?
1.19.2 was released on Feb 26, docs are on 1.19.1
What should the content say or communicate?
update the version meta data to reflect 1.19.2

Closed by #443


Tracing

Implement tracing where needed

we've added a tracing interceptor for all api calls (REST and GRPC). We can add more where needed but for the beginning this should be enough.


Kernel CI/CD should run with driver verifier enabled

These issues should have been caught in Kernel CI/CD by the driver verifier but weren't caught.
https://github.com/microsoft/ebpf-for-windows/issues/1087
https://github.com/microsoft/ebpf-for-windows/issues/1085
https://github.com/microsoft/ebpf-for-windows/pull/1084
Need to investigate why.

@Alan-Jowett @shankarseal wasn't this fixed by PR #1375 ?
If not, what is remaining?

This bug is outdated and be closed. DV is indeed enabled on all test VMs. I logged into each of the test VMs in all the selfhost runner machines and ensured that DV is enabled for ebpfcore and netebpfext drivers.
#1375 was about KMDF and this bug is asking for driver verifier to be enabled.


Parallelization

This change is

#687  👈
dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @spapinistarkware and the rest of your teammates on  Graphite

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.02%.

Additional details and impacted files
@@            Coverage Diff             @@
##              dev     #687      +/-   ##
==========================================
+ Coverage   89.94%   90.02%   +0.08%
==========================================
  Files          75       75
  Lines        9645     9727      +82
  Branches     9645     9727      +82
==========================================
+ Hits         8675     8757      +82
  Misses        889      889
  Partials       81       81

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Compete with python -m SimpleHTTPServer

Often times I want a self-contained ad-hoc server that I could get within an instant and setup in the current directory within an instant.
Some ideas:

have a curl / wget install script grab the right bin and shove it into /usr/local/bin/caddy (I've done this before)
serve http from the current folder with indexes when no config exists
also serve local https (bundle-in certs for localhost.caddyserver.com) for easy development

Currently there are a few node packages that partially do this. Obviously python kinda does it. It would be nice to have an easy-to-share 0-dep bin to handle it and perhaps caddy can fit in that space.

That's been the purpose of Caddy from day one. When you run caddy in any directory, it defaults to serving static sites from that directory, complete with support for index files. And unlike Python's SimpleHTTPServer, it actually honors the Range header.

It doesn't serve directory indexes is what I meant.

I'll work on an installer script and give you arm-compiler arm bins.
We could put a
cur -fsSL  caddyserver.com/install | bash
On the homepage?

Oh, directory indexes. Just place a Caddyfile with browse somewhere in it - or if you prefer to stay purely on the command line, you can pipe it in: echo "localhost\nbrowse" | caddy - something like that.
As for the installer script, I love piping scripts from the Internet into bash :smile: That aside, is this just for the ARM binaries? If so, I can just make the cross-compile work. There's a trick to getting them to work on older RasPis - I've done it before - just have to remember what it is.

Install script for caddy + caddy-browse (with indexes): https://github.com/mholt/caddy/issues/142


Image chooser tags are click enabled but do not function as expected

When selecting a tag from the image chooser the tag text will be placed in the search field to search the title but not the tag.

This issue seems related to torchbox/wagtail#278. It is unclear if this behavior is intended but it feels like a bug or an incomplete implementation of tag search.
Wagtail 0.8.4
Django 1.7.1

As per @davecranwell's comment on https://github.com/torchbox/wagtail/issues/278#issuecomment-73481293, the 'Search term' field should be searching tags as well as title - so the UI behaviour here is correct, and the problem (if confirmed...) is entirely within #278. Therefore, closing this as a duplicate.


 tag rendering

The keyboard tag doesn't render right in Documenter.jl. An issue has been opened there:
JuliaDocs/Documenter.jl#299

Choose just to use standard code rendering until this is fixed upstream.


Fix typos in tests

Last one I swear

no worries, keep them going ;)  having them all in one PR is easier maybe, but all these changes are welcome so :+1:

Putting all in one PR


Osmosis IBC hook

for https://github.com/hyperledger-labs/yui-ibc-solidity/issues/219
based on https://github.com/hyperledger-labs/yui-ibc-solidity/pull/215

@bluele may you have a look? we also did internal review too.
next step could be adding e2e tests that when middleware app stack is used instead of ics20 app, it works as before.

ping :) any changes needed?


command-> param, param2, param3 should be valid EMD.

TODO: 'command -> someParameter' should be valid EMD.

The current implementation is command -> // someParameter,  but it's very common to forget entering the '//'. This is not good because les and webeventstorming.com fail silently (or sometimes confusingly). Suggest that it might be better to fall forward and make both the command-> // parameter and the command-> parameter syntax valid EMD.

Looks like it's already the case.


Move License

Done to demostrate how CODEOWNERS works

Notice the reviewers now. TADA ✨

Notice the reviewers now. TADA ✨ @natashaarmbrust

Oops I didn’t make it clear enough I guess. I didn’t intend for you to merge this PR down :/


felix config not set if delay between nodes > 0.25s (RTD 0.5s)

RTD > 0.5s between controller and compute node.
Nova-compute sets up the VM, but the routes and iptables aren't configured.
felix logs:
2015-04-16 12:41:35,126 [ERROR][3] calico.felix.fetcd 97: Failed to retrieve ready flag from etcd, waiting...
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/calico/felix/fetcd.py", line 92, in wait_for_ready
timeout=10).value
File "/usr/lib/python2.7/dist-packages/etcd/client.py", line 344, in read
self.key_endpoint + key, self._MGET, params=params, timeout=timeout)
File "/usr/lib/python2.7/dist-packages/etcd/client.py", line 582, in api_execute
return self._handle_server_response(response)
File "/usr/lib/python2.7/dist-packages/etcd/client.py", line 598, in _handle_server_response
etcd.EtcdError.handle(**r)
File "/usr/lib/python2.7/dist-packages/etcd/init.py", line 142, in handle
raise exc(msg)
EtcdException: Unable to decode server response
and if I query etcd from the command line on the compute node:
ubuntu@calico-vm22:/var/log/calico$ etcdctl ls
Error:  501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0]

This problem appears to be in the underlying etcd communication layer. I suspect (but do not know) that raft does not like having 500ms latency between communicating nodes.

Not sure how to triage this, I think we need to be progressing it in the background but I don't think we need to fix it for 0.16 or 0.17.  @Lukasa, any opinion?

Agreed, I think it's non-urgent.

I'm extremely confident that this is to do with the leader election timeout, which by default is 1s: exactly twice the latency that causes this problem.

Proxies aren't involved in leadership elections, only true cluster members are, so I don't think that's related.
On the other hand, the code in https://github.com/coreos/etcd/blob/master/Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/requests.go#L157-167 only allows a request to be outstanding for 100ms before cancelling it and it only allows two retries.  I'm not sure if the response from the first request arriving after the second request would be treated as a response to the second request, which would explain how I was able to read/write keys at 100ms latency.  Failing to reach both peers returns an ErrCodeEtcdNotReachable which leads to the error message @DaveLangridge reported.

My findings from testing etcd at various latencies:
Default Settings
Time between heartbeat messages (equal to “time to wait for votes during election”) = 100ms
Time before starting election = 1000ms
Test Architecture
Three etcd nodes, with netem adding latency to the inter-node flows (i.e. all network hops are delayed by the given latency + real latency).  I tested leadership elections by killing the current leader and seeing if a new leader could be elected successfully.
Results

10ms – No issues seen, cluster-health reported healthy, leadership elections were successful
20ms – No issues seen, cluster-health reported healthy, leadership elections were successful
100ms – No issues seen, cluster-health reported healthy, leadership elections were successful
150ms – Elections succeeded, cluster-health reported unhealthy, no explanation why…?  Cluster health didn’t recover when I lowered the latency, I had to force another election to recover the cluster.
200ms – Spammy logs, cluster-health reported unhealthy, leadership elections never completed

We recommend deploying your etcd cluster in a single datacenter, where latency should not be an issue.  In addition, we think etcd have made the timeouts longer/configurable, resolving this issue.


Update mofax in PyPI

Thank you @gtca and other maintainers for the useful package! It really helps to make sense of MOFA output in Python.
It seems that the version of mofax in PyPI is slightly old (v0.3.2, dated 22 Sept 2020). I see from setup.py that the current version in this github is v0.3.4.
Is it possible to update the version in PyPI to be more current so it can be easily installed using pip install? Thanks a lot.

Hey @joewandy, thanks for your feedback.
I've uploaded an even more recent one, v0.3.6, to PyPI. In case there are any new issues with it that you might encounter, please reach out!


Cherry-Pick  Eliminate Warning Messages

Description
Describe what changed in this PR at a high level.
Issue
Add a link to the issue here.  Consider using
closing keywords
if the this PR isn't for a story (stories will be closed through different means).
Checklist

[ ] I have added tests to cover my changes
[ ] I have added logging where useful (with appropriate log level)
[ ] I have added JavaDocs where required
[ ] I have updated the documentation accordingly

Note: You may remove items that are not applicable

Closing to fix the partial signed commit


request for documentation - install and run commands

do I have to do anything else besides "gatsby develop" to get lambda functions to work locally? I installed this hackathon starter but I get an error when trying to hit the lambda thats on the main page.
> [HPM] Error occurred while trying to proxy request hello from localhost:8000 to http://localhost:9000 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)

Ok got it working.
I ended up running npm run develop in one terminal window, and then npm run start:lambda in another.
It might be worthwhile (esp for beginners) if you added a section to the main README which describes how to install and run locally.

wanna send in a PR? :)

would be my first :), will give it a shot after I read up on how to do it

awesome!!!! just do it, no fear, i'll guide you if anythings wrong

hey friends, i have just released a big update to this starter. it should fix many problems. please have a look and open a new issue if anything is outstanding.


Multiselect fold-out visually below other content

Reproduction Link
Not applicable
Steps to reproduce
Have besides the multiselect component, another component that loads its contents dynamically (axios).
Desired behaviour
Show the select fold-out on top of the other component's results.
Actual behaviour
As the other component renders last, it will always render on top of the multiselect.
A picture says more than a thousand words...

Already tried
Z-index (e.g. -10) on result cards.
Result: elements become unclickable as they render behind the parent div
Z-index (e.g. 10) on multiselect__select classes (e.g. active)
Result: works when done in Firefox DOM inspector, but not when applied to code. Which I assume has to do with the later rendering of the results component.
Any ideas?

Wrap the component inside a div with position: relative and some higher z-index.


Rexray breaks partitioning on host after upgrade

Summary
We see the issue on CentOS 4.4.112-1.el7.elrepo.x86_64 with Docker version  18.03.0-ce
once installing rexray plugin and restarting the instance it will boot up with read only on /dev/pts
with message: PTY allocation request failed on channel 0
--- If you googled and see this message login to your server using the following command:
ssh user@host "/bin/bash -i"
once inside the machine run:
sudo -S mount devpts /dev/pts -t devpts
this will give fix your host until you will reboot ( then partitions will be updated again )
disclaimer - above worked for me , on the specific version , this is only what i did on my own personal server and not a solution i offer to any reader here and if your server will die, deleted, become skynet its on your own risk.
Version
plugin is latest version installed with "docker plugin install rexray/efs" no /usr/bin/rexray file exist
verified on a new instance and after reboot issue persists

Hi, i have the same problem on a DO Droplet with Ubuntu 16.04.4 LTS and Docker 18.03
To reproduce:
$ mount | grep pts
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
$ sudo docker plugin install rexray/dobs:latest
Plugin "rexray/dobs:latest" is requesting the following privileges:
 - network: [host]
 - mount: [/dev]
 - allow-all-devices: [true]
 - capabilities: [CAP_SYS_ADMIN]
Do you grant the above permissions? [y/N] y
latest: Pulling from rexray/dobs
929948b23cbd: Download complete
Digest: sha256:954b4befc1fa8faf6ed335833c78b561e6ed53cd981f408cb823fa48f2fe4760
Status: Downloaded newer image for rexray/dobs:latest
Installed plugin rexray/dobs:latest
$ mount | grep pts
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
$ cat /etc/fstab
LABEL=cloudimg-rootfs   /        ext4   defaults        0 0
LABEL=UEFI      /boot/efi       vfat    defaults        0 0
```

Then when i logout and connect again via ssh i am greeted by the message:

´´´
PTY allocation request failed on channel 0
´´´
 I have to remove the rexray plugin and reboot the instance to be able to login properly again.

Very interesting. Have you been able to test any other docker plugins to see if they produce the same result? My feeling is that this is more likely related to Docker managed plugins than REX-Ray.

I am seeing a similar issue on my Ubuntu 16.04 based install with the same versions as codestation. However I am using s3fs plugin which I am installing using the command:
docker plugin install rexray/s3fs
S3FS_ACCESSKEY=ACCESSKEYHERE
S3FS_SECRETKEY=SECERETKEYGOESHERE
Based on clintkitson's comment about I have also tested a different docker volume plugin - "vieux/sshfs" and I am not seeing the same problems.
Note that I have also tested on a development Ubuntu 17.10 box and have the same issues with devpts.
I'm not sure what else to try.   The plugin is working great except for this issue.

Can I ask that you try two more things? 1) can you try an additional REX-Ray plugin with same distro 2) can you try running REX-Ray standalone and running the s3fs driver?

Hi,
I came across this issue few days ago in Ubuntu 16.04 in AWS with the exact same behavior described in the issue summary. In my case I found devpts was mounted 3 times instead of 1 as it normally should be. I had to force an interactive shell and after checking mount found this:
ubuntu@ip-10-0-0-233:~$ mount | grep devpts
mount | grep devpts
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)

I am using rexray ebs and efs plugins and install them with the following command:
docker plugin install rexray/ebs --grant-all-permissions REXRAY_PREEMPT=true EBS_USELARGEDEVICERANGE=true
docker plugin install rexray/efs --grant-all-permissions REXRAY_PREEMPT=true

As described above, the only fixes I have found for this issue is either remount devpts or uninstall rexray plugin.

So what I've found out is that this is not an issue that was introduced into rexray on update. This is likely an issue with kernel version or some core library version. I though that rollbacking rexray to an earlier release will fix the problem, but I went as far as 0.9.0 from year ago and the issue still persists. I have a second machine, where there's no problem, and it uses a slightly older AMI, build on the same exact version of CentOS. The difference is in the kernel version:
Working rexray: 3.10.0-693.11.6.el7.x86_64
PTY problem rexray: 3.10.0-693.21.1.el7.x86_64

I continued investigating and testing possible workaround for the issue. Same as @bandrzejczak I tested rolling back to previous versions all the way back to 0.10.2 ( around 7 months old version) without any success. During this time I found that prior installing rexray plugins I only have a devpts entry:
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)

Right after installing rexray/ebs I find the entries have been triplicated for devpts and any new connection attempts will get PTY allocation request failed on channel 0 message and won't get a prompt. A couple entries are added to /proc/mounts and they remain there even when plugin is uninstalled.
Unlike CentOS, I have tested with Ubuntu with kernel version 4.4.0-1035 (latest), 4.4.0-1022 (09/17), 4.4.0-1016 (07/17) and 4.4.0-57 (12/16) with same results. I am using a script to install several packages and updates along with the plugins so next step in my investigation will be to suppress updates and see if that along with older kernel version works.

Thanks for investigating this.
On Fri, Apr 20, 2018 at 4:00 PM Hebert_Cuellar<EMAIL_ADDRESS>wrote:

I continued investigating and testing possible workaround for the issue.
Same as @bandrzejczak https://github.com/bandrzejczak I tested rolling
back to previous versions all the way back to 0.10.2 ( around 7 months old
version) without any success. During this time I found that prior
installing rexray plugins I only have a devpts entry:
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
Right after installing rexray/ebs I find the entries have been triplicated
for devpts and any new connection attempts will get PTY allocation
request failed on channel 0 message and won't get a prompt. A couple
entries are added to /proc/mounts and they remain there even when plugin
is uninstalled.
Unlike CentOS, I have tested with Ubuntu with kernel version 4.4.0-1035
(latest), 4.4.0-1022 (09/17), 4.4.0-1016 (07/17) and 4.4.0-57 (12/16) with
same results. I am using a script to install several packages and updates
along with the plugins so next step in my investigation will be to suppress
updates and see if that along with older kernel version works.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rexray/rexray/issues/1197#issuecomment-383243331, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABVMMchM7tk0fOi0S3UyV1bLW9u0AGn1ks5tqmiOgaJpZM4TAG8c
.

I also have this issue : see https://github.com/rexray/rexray/issues/1208
If I remember correctly it started after an update (with an update to its kernel I believe) to ubuntu 16 about 1 or 2 months ago.

Hi all,
After testing with older versions of both rexray and kernel with the same Ubuntu 16.04 with and without any update packages I ended up with the same result of rexray adding extra entries of devpts. I can conclude that older kernel in Ubuntu is not making any difference. I tried several different (and rather dirty) things like adding an umount/mount commands to rc.local, umount all devpts entries and mount only one or delete duplicate entries from mountinfo and reboot without success. The only workaround so far remains manually umount/mount devpts.
@clintkitson I will appreciate any input or suggestion to keep digging on this issue.

Thank foybfor looking into this. Would you care to elaborate on the workaround?

@basz workaround steps:

ssh to your instance with rexray plugin prompt issue either normally or forcing interactive shell (use "/bin/bash -i" at the end of your ssh command).
type sudo umount /dev/pts.
type sudo mount devpts /dev/pts -t devpts.
ctrl+C to end the session and ssh normally.

Hello! Working with @HebertCL.
Found out that it looks like a Docker bug, not Rexray.
We were installing latest stable Docker CE version. After downgrade to 17.12.1~ce-0~ubuntu everything works fine with both latest Ubuntu distributive and Rexray plugins
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | apt-key add - apt-key fingerprint 0EBFCD88 echo "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" > /etc/apt/sources.list.d/docker.list apt-get update -y && apt-get install -y docker-ce=17.12.1~ce-0~ubuntu

Any news on issue resolution?


Add Blake2 algorithm

Add Blake2 algorithm benchmarking. Use BouncyCastle, AlphaZero, and JBlake2. Also improve how the BouncyCastle benchmarks run to reduce unnecessary work.

Thanks @MariusVolkhart. Just one request, can you please add a reference to the use of the thirdparty directory to the "License" section of README.md?


”Lazuri”, ”Bercu”, ”Nisipeni” are listed in the drop-down menu

Description:
When user writes ”Lazuri”, ”Bercu”, ”Nisipeni” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Lazuri"

Expected results
The location appears in the drop-down menu as "Sat Lazuri, SATU MARE (Lazuri)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Bercu"

Expected results
The location appears in the drop-down menu as "Sat Bercu, SATU MARE (Lazuri)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Nisipeni"

Expected results
The location appears in the drop-down menu as "Sat Nisipeni, SATU MARE (Lazuri)".


curlopt_httpheader in behat.yml

Hello,
I'm looking for the best way to add headers to goutte/guzzle requests. Problem is that most environments are getting https but the termination of ssl is on the loadbalancers and not the webservers. So when I try to connect to http://projecthostname it redirects me to https://projecthostname but the non-javascript tests are being run on the machine themselfs (drupal api driver) and the localhost doesnt respond except the 'x-forwarded-proto' header is added...
Any idea how to make this happen?
Thanks,
Trogie

this has nothing to do with Behat itself, as it does not deal with Goutte or Guzzle in any way (and so has no idea where they are configured)

Yes I knew this was probably not the best place to put it but as there are so many different projects...
Thanks

Yeah, but as I don't know which project relying on Guzzle you are using, I cannot help you


Update links in setup.py

To improve the PyPI page for Flask-Autoindex at
https://pypi.org/project/Flask-AutoIndex/

I was thinking we could add Project URLs now too, like:
diff --git a/setup.py b/setup.py
index 3cb10f4..ad1b3f0 100644
--- a/setup.py
+++ b/setup.py
@@ -32,6 +32,10 @@ setup(
     license='MIT',
     author='RIGAUDIE David',
     url='https://flask-autoindex.readthedocs.io',
+    project_urls={
+        'Documentation': 'https://flask-autoindex.readthedocs.io',
+        'Source': 'https://github.com/general03/flask-autoindex',
+        },
     description='The mod_autoindex for Flask',
     long_description=__doc__,
     packages=['flask_autoindex'],


Show how many targets a spell can target

On the effects, it only shows for example "Change ATTACK by 2 on targets", but it doesn't show how many targets that it can target. It should say "Change ATTACK by 2 on 1 targets" or "Change ATTACK by 2 on 1 to 5 targets" etc.

card('E.M.P.') {
	"Electromagnetic pulse that damages electronic circuitry."
	manaCost 8
	// damage 1 to 10 Mechs on the Battlefield
	spell {
		targets 1 to 10 cards {
			creatureType "Mech"
			zone "Battlefield"
		}
	}
	afterPlay {
		damage 2 on targets
	}
}

Spells specify the number of targets in the spell {} clause. Do you want filters specific to a particular effect? If a spell targets 2 cards and it has an effect on 1 targets, which of the targets should the effect be applied to?

"Change ATTACK by 2 on 1 to 5 targets" is the auto-generated description of a spell. targets 2 cards and an effect on 1 targets should not be possible, the DSL should remain as it is: damage 2 on targets
This issue is about including the number of targets in the auto-generated description. No change needs to be done on the DSL itself.

I see, I thought you were talking about changing the DSL syntax.


vision modules for golems

i don't really understand how the vision modules are supposed to work for the golems. i have a golem with a seal set to harvest and collect crops, and since I gave him a vision module in theory it should work for my whole farm (within 48 block range). but it only seems to work within the 8x8x8 range restricted by the seals themselves
what's the point of being able to add an extra module for them  if they're still restricted by the seal range?

Don't you mean "thirty-six seals", since a 48x48 area translates into a 6x6 grid of 8x8-area seals? ;)
Also, some golem applications are not restricted by seals. Golem Logistics, for example, allow you to order a nearby golem to go fetch an item from storage for you. Having extra range on such golem assistants is very useful.

Yup, the range is how far the golem will travel to perform something.


I met a problem that bothered me a lot，It's about validation

My info depends on other schema，
I need to rely on info for rendering。
but，If info exists, it will be validated。
Because this is a logic of dynamic processing, info may exist or may not exist depending on the operation of the page。
So, when I don't need the info, I remove the info。
But my page rendering will rely on info, embarrassing。
In short, I hope to skip the verification of info in some way
**" version": "6.12.4" **

Fields are only validated if present, they are not required without "required" keyword. The schema fragment looks incorrect though - please review.

I know what you're talking about. My problem now is that the info field may have content or may not have content, which is determined by page operation. But my page rendering depends on this info field. Now there is a situation that I do not have the specific content of this info field due to page operation, but my info references other schemas. At this time, if the info field exists, the verification will be run. So I had to delete the info and send it to the server. However, my page will retrieve the data stored before by the server next time. At this time, there may be no info field, so the page crashes.
So I wish I had an info field, but in some cases I could skip validation

Fields are only validated if present, they are not required without "required" keyword. The schema fragment looks incorrect though - please review.

I know what you're talking about. My problem now is that the info field may have content or may not have content, which is determined by page operation. But my page rendering depends on this info field. Now there is a situation that I do not have the specific content of this info field due to page operation, but my info references other schemas. At this time, if the info field exists, the verification will be run. So I had to delete the info and send it to the server. However, my page will retrieve the data stored before by the server next time. At this time, there may be no info field, so the page crashes.
So I wish I had an info field, but in some cases I could skip validation

If you don't want the field validated when it is present, you need a separate schema that does not validate this field (you could modify the schema in your code).

If you don't want the field validated when it is present, you need a separate schema that does not validate this field (you could modify the schema in your code).

The way I deal with it now is to check whether the received data contains the info field in the code. If it is, I will skip it. If not, I will supplement it. But I think it is too low to be expanded and customized. I want to find a better way. Do you have any better suggestions?


Space should be reduced between "flexible learning for open" and "education"

Describe the bug
Space should be reduced between "flexible learning for open" and "education" as they are the part of the same heading or line.
Screenshots

@Chaitanyassr I think you have increased the font size above 1.2. I am saying this because it is inline till font size=1.2.
Moreover if we go above font size> 1.5 then the ul list of News, Resources. UI Options also gets disoriented.

The default preview with default presets in the preferences box doesn't push the 'education' word to the next line.


class B extends A calls A.extended(B) when A.extended is a function

It'd be useful if CoffeeScript could invoke a callback on a class after it's subclassed with the extends keyword.
With such a callback, you could implement a base class that propagates its class methods to subclasses:
class Base
  @extended: (subclass) ->
    for key, value of @
      subclass[key]: value

class Element extends Base
  @fromHTML: (html) ->
    node: # ...
    new @(node)

class MyElement extends Element
  # ...

MyElement.fromHTML("<div>...</div>")

You could also implement a test case class that collects its subclasses and runs them automatically:
class TestCase
  @subclasses: []
  @extended: (subclass) ->
    subclass.extended: TestCase.extended
    TestCase.subclasses.push subclass

class BaseTest extends TestCase
  # ...

class ElementTest extends TestCase
  # ...

for testCase in TestCase.subclasses
  TestRunner.run testCase

I've just been pointed to this ticket from: https://github.com/jashkenas/coffee-script/issues/1762 ...what do you guy's think this?


Convert CG private APIs to use proper naming convention

@DHowett-MSFT this should be easy to handle as part of your core graphics work.


Content page refactoring

Hi Phil,
Here is the refactoring of the _content_page template which I did at railscamp. Added since then are specs unit testing the SectionPresenter and SectionSetPresenter classes. Although this may duplicate test coverage slightly, I wasn't quite game to remove any of the request specs for pages, as they are still likely to catch potential problems. The new specs however mock out everything else and take less than a second to run, so it shouldn't be a problem to have the slightly duplicated test coverage.
The remaining ruby code in _content_page is mostly just to organise and check the potential parameters passed into the template. Typically these parameters are not used anywhere in the refinerycms git repository, so I presume they are mainly for other engines, such as the blog or whatever. If any of them are genuinely not needed, then removing them would simplify the code a lot.
This line looks particularly worrying:
allowed_to_use_fallback = !local_assigns[:show_empty_sections] && !local_assigns[:remove_automatic_sections]
Either of those two local parameters have the same effect, and that effect essentially forces the section to use the override html, or nothing at all. This is a direct refactoring and is how it was before (although it didn't used to be clear that's how it worked before). Perhaps replacing that with a single local assign would be better, as long as other engines conformed to it.
Craig

(Phil asked me to review the code)
Besides those two comments that I left, it's super clean. Nice work.

@craigambrose: Great work! Having so much logic in this one partial was a wart on refinery and I'm glad to see you taking the initiative to clean it up. I made some inline comments, but those were mostly minor quibbles with coding style.
The one major thing that I think you missed is getting rid of the content_page partial altogether. I'd rather see all of the logic moved to a helper method, like this:
module Refinery
  module ContentPageHelper
    def content_page_for(page, options={})
      ContentPagePresenter.new(page, options).to_html
    end
  end
end

This way all of the logic would be moved out of the views into something easier to test, like you've already done.

Getting rid of the entire partial would be amazing actually.. that way you could just override the method to render pretty much anything you wanted or use the defaults that would be crazily well tested.
Basically, as I explained to @craigambrose at Rails Camp NZ, the whole /refinery/content_page thing was just "a way to get what we wanted to do done" and by no means a good solution. So I'm thrilled that you guys are helping to eliminate by far the ugliest part of Refinery.

Thanks guys. I'll resubmit tomorrow with the changes from this thread.
@phiggins: Replacing the partial altogether sounds like a pretty good idea. Certainly based on the codebase in the refinerycms repository itself that would seem fine. What about other engines though? Is anything else using this partial directly?
I basically like the example helper above. This partial is not a good candidate for being a partial, since it's basically just a giant ruby method. I'm certainly quite happy to make that change.

That way we can keep the conversation open!
I don't care how many commits it ends up being, I'm not the kinda
person to request you squash commits. I kinda like the history. :)

Re: removing the partial.. Other extensions can adapt. :-)

Other engines (blog, at least) are using this partial. Changing its use within refinery itself, and then changing the partial to use the helper and emit a deprecation message might be a good path to take forward.

@phiggins It's either that or just open heaps of pull requests. ;-)

For the record I think the deprecation's a better idea. We did the
same in the menu for 1.0.x and it was remarkably helpful.

Hi guys,
I've implemented all the changes in this thread, including renaming SectionSetPresenter to ContentPage and encapsulating the array, except for refactoring the partial itself out of existence. I'll get to that tonight I hope.
Thanks for all the discussion on this patch. I've been working by myself for the last five years, so I don't get much of that. :)
Craig

Nice work @craigambrose!

Folks, I need some advice.
I don't really like the name of Refinery::Pages::ContentPage. It's better than SectionSetPresenter, but the name really just comes from that template, and what is a "content page" exactly anyway? We already have a Page class. A ContentPage sounds like a particular type of Page (ie, one with content or something). Instead, what this class is really doing is taking a page, and providing the ability to render it as html. So, possibly it's a PagePresenter.
I was just about to do a rename to PagePresenter when I noticed that we already have one. It's in pages/app/presenters/refinery, which is probably a great place to put presenters like my two classes. I can't see it being referenced anywhere, but I gather it's part of a general presenter system and presumably used implicitly based on name. It's base class provides some general functionality for encapsulating another model ala the decorator pattern.
So, are my two classes (currently ContentPage and SectionPresenter) actually presenters? Should I pop them in the presenters dir? Can I combine my ContentPage class with the existing PagePresenter? Note that my ContentPage class, while used basically to present a Page is not implemented in a decorator pattern way (it builds itself from the page but doesn't store the page internally). I could change that.
Thoughts anyone?

Names are always best made by saying what something is in plain language.

what this class is really doing is taking a page, and providing the ability to render it as html.

Sounds like an HtmlPresenter to me, maybe HtmlPresenter.from_page(page)?

Thanks Steve. I hadn't considered naming it from that end of it's job (it does indeed present html) mainly because presumably we'll have lots of objects that present things as html. Thus, I'd been inclined to name more based on what it was presenting. PageHtmlPresenter would also be fine (or HtmlPagePresenter). Perhaps though, given this is a web app, we can assume presenters present HTML unless stated otherwise.

Is ContentPresenter not acceptable?

What about PageContentPresenter ?

I think ContentPresenter is good because then later we can make everything use that and then it won't need to have an associated @page attribute anymore (the eventual goal!)

I could split into into two classes. A ContentPresenter base class that has most of the functionality, and a PagePresenter subclass that has the Page specific bits.

That would probably work quite well, you know. Then people could make their own specific presenters that inherited ContentPresenter and Just Worked (tm).

Hey guys, if I move the logic out of the _content_page partial and into a helper, where does that helper go? Anywhere I put it I seem to still get two failing request specs, which occur in the admin backend when trying to preview a page. How do I get my helper method to get loaded for the admin action?

In the admin pages controller put something like this
helper Refinery::Pages::ContentHelper <-- or whatever it's called

Is there a Refinery::AdminHelper this could be included in? Technically it
doesn't need to be included in the controller...

true that, but I am not aware of one

Would like to get this merged in the next day or two if possible.

Yeah, I'm conscious that this needs to be in for the release. I'm just working on the helper methods and tests to remove the last stuff in the partial template. I've got very little time for that today though. I'll try and get it done later tonight or tomorrow afternoon.

Sure thing.
Thanks for all the hard work you've put into this. I'm really excited :-)

Right guys, I think I'm done. I haven't removed the _content_page template, but it's down to two lines. I think it's good to leave it in, in case people want to override it and wrap it with more html or something.
I've added some comments to the classes and helper methods that I created. I don't normally comment my own work, but this is an open source project, so I presume they will be useful. I haven't commented all my methods or anything, so it's certainly not at the standard of documentation for a public interface (not sure if this really is a public interface, some of it could be used by other engines).
I have stuck to using the lib directory for my presenter classes, not /pages/app/presenters, as the latter directory seems to be used specifically for objects which get implicitly loaded to decorate a model of the same name as the current controller. My classes are also basically decorators, but need to be explicitly loaded with a few other options.
The comment on the mailing list about getting refinery to work with bootstrap has me a little concerned that it's currently a bit hard to change the markup used to wrap the sections and content pages. Obviously deface could be used for this, but I think maybe it should be configurable in refinery itself. I don't think that should holdup this pull request though (or the refinery 2.0 release).

This merge is sponsored by fine whisky

So far I see two issues with this change.
One, the other engines like blog and inquiries and such need to be told about the helper Refinery::Pages::ContentPagesHelper.  They are using the core partial for content_page and will now need to include the helper in any controller that eventually uses the partial.  This doesn't really feel right.
Two, unless I must something that needed to be changed after this pull request, I am not seeing interpreted html on the page, but the html text itself.

Bugger, and here I was thinking this was all done and dusted. :)
Good point on issue 1. I'll fire it up with the blog engine and take a look. I've split the helper method, and the presenter classes, into ones that are specific to a Page object (from the pages engine) and ones that aren't, so I guess the non-page-specific stuff needs to move into refinery core. I presume that the Blog and Enquiry engines don't use a page object (but I haven't checked yet, will look).
Regarding the second problem, that sounds nasty. It did work for me. I gather you're saying that it's displaying escaped html (lots of angle bracket tags and stuff visible in the browser). Is that for a page displayed via the pages engine, or is this in the Blog or some other engine?
thanks
Craig

I'm seeing escaped html rendered from engines and from the pages.  Tracking another bug at the moment or I would look at it for you.  Soon hopefully.
The first problem really does look like an encapsulation problem.  Adding the helper to the controller in the engine fixes it since they do use an @page object.  However they don't all use an application controller so you have to find where the content_page partial is used and make sure the controller using it knows about the helper.

Has anyone else noticed the un-escaped html.  I want to make sure it isn't just something about my local configuration before I dive to deeply to fix it.  I guess I can just create a test app from the github code instead of my local copies but I hate to put too much effort into this if it isn't a real problem.
Any thoughts on the helper issue?  Pretty much all the admin controllers I've seen inherit from ::Refinery::AdminController.  Is there any similar consistency with the front end controllers.  The couple I looked at seem inconsistent.  Maybe the best fix is making all the engine controllers inherit from the refinery base class and make the helper available there.

I have also noticed it and have also been bitten by the helper issue in refinerycms-blog

For the unescaped html, there's probably a simple solution like using h or .html_safe in the right places. This can be tested for with some capybara specs like in refinerycms-blog.
For the helper issue, it's probably best to include the helper in another helper that rails will use automatically, like ApplicationHelper or something.

I think I mean raw instead of h.

Submitted fix for the html escaping issue:
https://github.com/resolve/refinerycms/pull/1350
I tested it just with a unit test (spec), not at the integration test level (which might have been a good idea in hindsight. Anyway, all working.


is there at least some indication of the transition or the status of the windows power profile change? in the tray, or pop-up...

Hi,
No User Interface elements exist for Legion Watcher.
I suggest looking at Lenovo Toolkit as some of the ideas here are being integrated into it .


e2e/cypress:fixed cypress

Fixed known issues test cases
Release Note
NONE

/e2e-test

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard

/e2e-test

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard


Fix knapsack coverage in queue mode

So the previous attempt at solving this wasn't quite working, and seems to be due to forked processes exiting and clobbering the coverage.
This change ensures we get a new coverage file per process, and also ensures that the sever processes spun up by capybara et al, get their coverage recorded.

Uhh, well that's a definite fail. Coverage through the floor.


Improve linker performance

When compiling complex code such as revm, the linker takes quite some time to create the final powdr asm file.
We should find ways to improve both time and memory.

@chriseth I think you did some work here? Should just try again soon, and write some benchmarks.


Adding A New Camera Angle to the Project

These are the existing camera angles in the project. Apart from this i would also like to add the panoramic view to the project.
Thank you

Please assign this issue  to me under #gssoc'24 . Please also add the labels gssoc and level to this issue.
Thank you.

I have fixed the issue #140 and also raised a PR for the same #170 thereby adding the desired feature - a new camera angle to the project.


Websocket issue

Fixes #896

There are three places we have to handle this issue.

At the time when the chrome process crashes or gets killed by some other process (other than Taiko). This can be done by adding a listener for exit event. Here we can make sure that subsequent openBrowser call does not result in OpenBrowser cannot be called again as there is a chromium instance open. error.

Before every call to CDP domain API. Here we can check for connection availability before making the call to the CDP domain.

If somehow the above two cases are not enough to handle the WebSocket is not open: readyState 3 (CLOSED) error. We can try to handle it in https://github.com/getgauge/taiko/blob/3c0e34ecf36d90bdb0d329a139ae64e0d0a306e3/lib/taiko.js#L3180

If somehow the above two cases are not enough to handle the WebSocket is not open: readyState 3 (CLOSED) error. We can try to handle it in https://github.com/getgauge/taiko/blob/3c0e34ecf36d90bdb0d329a139ae64e0d0a306e3/lib/taiko.js#L3180

This will be redundant I feel, if the call to domains are handled then this should also be handled as the only way  we make websocket calls are using them

if the call to domains are handled then this should also be handled as the only way we make websocket calls are using them.

It's not really handeling the websocket closed  error. It just do a check before making the call to CDP domain. So, if after that check browser crashes we still need to handle that.

If browser or page crashes when the api is executing it just hangs giving no response.
> openBrowser()
 ✔ Browser opened
> goto("google.com")
 ✔ Navigated to URL http://google.com
> text("sdfgsfd").exists()

close the browser manually after entering the last api.

all api hangs after a page crash
client().Page.crash() will be better if taiko can report that to user.


Detect DNS caching issues caused by site recreation

Came up a few times of forum, e.g. here.
This can happen when a function app is deleted, and another one with the same name is created shortly after.
We should add simple detection logic: e.g. try to hit the scm site with no authentication. If you get a 404 instead of 401, it’s a pretty safe bet that it’s resolving to the wrong stamp.

Any suggestions on the wording of the error?
How about this We are unable to reach your function app. This could happen if DNS resolution fails to resolve to the right place.  You can either flush your local DNS cache, or try again in 15 minutes.

Message sounds reasonable.

small issue here is that we don't actually get the 404, we get a CORS error. What I do right now is I query ARM for the site, if CORS settings are missing, that means it's a CORS error and I display CORS is not configured for this function app. Please add {{URL}} to your CORS list.
If I find the CORS setting, I assume it's the DNS issue and display We are unable to reach your function app. This could happen if DNS resolution fails to resolve to the right place. You can either flush your local DNS cache, or try again in 15 minutes.
however if the site is down for any reason we will still get CORS error even though CORS is configured correctly. Right now it matches the check for DNS as you can see from above.
Possible solutions:

check the scm endpoint. If we assume that the DNS cache for both the main site and scm site will expire at the same time, then we can send a request to the scm site. If it returns 503 (scm CORS happen on the frontEnd, so even if the site is restarting or down for any reason, we will still get correct CORS response) then it's the site restarting or down. If we get another CORS error, that mean it's the DNS issue

Add a pass through API on the backend that we call in these situation to figure out what's CORS and what's not.

Thoughts?


Add Project Structure section and enhancement

Enhancement

Create django directory
Add default README.md in django directory

Changes

Add Project Structure section

I request services for code that connect to third party services, manager for reusable queryset with Django Manager.

I request services for code that connect to third party services, manager for reusable queryset with Django Manager.

Oh you already have manager file, so only services.py

Thank you all krubbb P'


Valid icon on select

Fixes #1342
Actually wondering if we need to continue upgrade this file or reset the file to the Bootstrap one and apply changes to it since our mindset changed on validation icons.
Apply Bs solution on valid state only. I think that textareas already have a valid state.

@louismaximepiton Some conflicts here to resolve 🙏

LGTM! @MewenLeHo I let you double-check the latest modifications before merging it.

Looks good but I found two possible problems :
In responsive, the valid icon goes behind the text:

If the text written in the textarea is long enough to have a scroll bar then the valid icon goes partially behind it:

In responsive, the valid icon goes behind the text on small screen:

Resolved by #1306.

And in desktop, if the text written in the textarea is long enough to have a scroll bar then the valid icon goes partially behind it (may depend of the browser):

Bootstrap seems to have the same issue 🤷


Add option to change the name of the precompiled header output file

Right now, only the folder path of the precompiled header file can be modified. The file name is forced to use the project's name.
This pull request introduces a configuration option to modify the file name. In my case, this allows me to share the precompiled header file between multiple projects. This was not possible before because of the reason mentioned above.

Merged, thanks!


fira: 4.106 -> 4.202

Motivation for this change
Upstream update...5 years ago
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Upstream update...5 years ago

Maybe a good idea to update on stable if it's really that out of date.


fix(dropdowns): RTL for .dropdown-menu-*

Attempt to fix #34088

@ferhado 's initial CodePen, using this PR's CSS RTL output: https://codepen.io/ffoodd/pen/ExWvdoY
and RTL Cheatsheet still works fine: https://deploy-preview-34124--twbs-bootstrap.netlify.app/docs/5.0/examples/cheatsheet-rtl/#dropdowns

Any concern, @twbs/js-review —or does it look safe to you?

Sorry for the ping, Rohit just answered in the issue :)


[virtio-block] Request support for multi-stage resume of Windows to speed up hibernate/resume

I have a Windows11 guest booted with QEMU and Virtio-blk device, it hibernates very slow (about several minutes) and the resume phase is single-stage(so resume time is longer). After I change the block device to nvme, it hibernates very fast(about several seconds) and the resume phase is two-stages(resume is very fast).
I don't know why virtio-block does not support the multi-stage resume, we'd better support it to have a much better user experience.
FYI:

the multi-stage resume of Windows: https://learn.microsoft.com/en-us/windows-hardware/test/weg/delivering-a-great-startup-and-shutdown-experience#resume-phase
To see whether multi-stage resume is enabled, we can go to Windows registry path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power, if the NoMultiStageResumeReason item is 0, then multi-stage resume is enabled.

@zkq Thanks for reporting the issue. Please kindly notice that S3 and S4 is not officially supported by qemu [1],  So I am afraid this also won't be virtio-win drivers' priority.
[1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_virtualization/assembly_feature-support-and-limitations-in-rhel-9-virtualization_configuring-and-managing-virtualization#unsupported-features-in-rhel-9-virtualization_feature-support-and-limitations-in-rhel-9-virtualization,

@vivianQizhu
There are still some users who are running virtio-blk driver on top of different VMMs and even FPGA implemented virtio HBA(s). This feature can be nice to have, in addition to the other stuff like v3 DMA support etc.
Cheers,
Vadim.

@vrozenfe
Agree. This feature is very valuable, @vivianQizhu  please consider to add it into development plan.

@vrozenfe @zkq Thanks, sure it is nice to have, I mean it won't be on high priority list. Cheers.

@vivianQizhu @vrozenfe
Hi, A good news that I have written some demo code and the vio-block driver supports MultiPhaseResume now. But the boot time is still very slow:

Before MultiPhaseResume is supported, the first resume phase (executed by single vCPU) consumes about 10 seconds, then it enters windows desktop quickly.
After MultiPhaseResume is supported, the first resume phase (executed by single vCPU) consumes less about 1 second, then the second resume phase (executed by all vCPUs) still consumes much time. This is abnormal.

And another issue of vio-block driver is about hibernate. When I start hibernate, all vCPUs run 100% for 1~2 minutes before windows writes hibernate file into disk. As I can see with NVME virtual device, the hibernate and resume process both are very fast. I guess the issue of vio-block for hibernate and resume are same as the problem looks similar.
Do you have any idea how to solve these issues?

@zkq can you please share a demo code?


Display the correct library imports for all packages on pub.dartlang.org

Currently, the package view pub.dartlang.org always displays the example import as 'import "package:packagename/packagename.dart"'. Some packages don't have a library with the same name as the package, though, and for those packages this import example will fail. We should display one or more valid imports for these packages instead, or at least an import string that has an obvious placeholder.

This issue has been moved to dart-lang/pub#187.


pd_client: fix monitoring unit typo

Signed-off-by: HunDunDM<EMAIL_ADDRESS>
What problem does this PR solve?

pd_client: fix monitoring unit typo

Related changes

Need to cherry-pick to the release branch

Check List
Tests

No code

Release note

No release note

/lgtm

/merge


Build a custom version of libcurl that is statically linked

Libcurl (very annoyingly!) has a thread-unsafe startup function, curl_global_init.
Currently, this library recommends that curl be initialized very early in the program.  But that still isn’t safe.  A user could fail to initialize this library and then experience a data race (= undefined behavior) later on.
Rust has no way to ensure that a function is called before any threads are launched.  Initializing libcurl from a static initializer can cause deadlocks on Windows.  Is there a solution?

Could you clarify the unsafety here? Invocations of the initialization function should be synchronized.

AFAIK there's no known unsafety here, so I'm going to close this, but please let me know if I'm wrong!

@alexcrichton The unsafety appears if another thread is already using one of the libraries that libcurl uses, and which has a thread-unsafe initialization, such that both threads try to initialize libcurl (or a dependency thereof) simultaneously.

Indeed! Other crates I've worked in solve this by exposing a shared init function in the sys crate to call into, and I could add that to curl as well if needed!

The problem is that we can't ensure that the init func is called first,
since Rust lacks life before main() (and on Windows the loader lock means
that there is no good way to do this).  So we need a private copy of
libcurl (and its dependencies) that we know nobody else will be using.
On May 9, 2017 7:11 PM, "Alex Crichton"<EMAIL_ADDRESS>wrote:

Indeed! Other crates I've worked in solve this by exposing a shared init
function in the sys crate to call into, and I could add that to curl as
well if needed!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alexcrichton/curl-rust/issues/157#issuecomment-300327491,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGGWB20ygcLbB8xgmMy7l8sELg3xXU3cks5r4PKcgaJpZM4M5GRO
.


Update To Latest Version

Update To 1.21

Had some fun playing survival with friends, but it's now out.


BranchUniversalObject's initializers should not be nullable

BranchUniversalObject's initializers are now marked as returning a nullable object. This is incorrect and makes creating these objects annoying in Swift. BranchUniversalObject's initializers all return a nonnull object if [super init] does, and -[NSObject init] returns a nonnull object, so BranchUniversalObject's initializers will never return nil. I don't think <objc/NSObject.h> has nullability annotations, but -[NSObject init] definitely returns nonnull (specifically, it's implemented as return self), and the Swift overlay module explicitly makes it nonnull.

Thanks for the feedback Kevin - We'll get this patched for the release next week!

Merged in here for next release https://github.com/BranchMetrics/ios-branch-deep-linking/pull/451

This has been resolved in v0.12.10. Thanks so much for your contributioN!


[BUG] Example projects are built when Face_Detector project is imported into another project

Example projects build even when Face_Detector is not the main project
When importing face_detector.cpp into another project, CMake builds the example code. This should be default off according to the CMakeLists file.
To reproduce
Import the project into another CMake project:
cmake_minimum_required(VERSION 3.1...3.14)

project(test_project VERSION 3.11.5 LANGUAGES CXX)

include(FetchContent)
FetchContent_Declare(
        face_detector.cpp
        GIT_REPOSITORY https://github.com/CLFML/Face_Detector.Cpp.git
        GIT_TAG main
)
FetchContent_MakeAvailable(face_detector.cpp)
add_executable(demo ${CMAKE_CURRENT_LIST_DIR}/src/demo.cpp)
target_link_libraries(demo PUBLIC CLFML::face_detector)

src/demo.cpp:
int main(int argc, char *argv[])
{

}

After building you will still find the face_roi_demo example in the build directory. Even though no one asked it to compile.
Cause
It is probably caused by a typo somewhere in the CMakeLists that detects whether this project is the Main project.

great!


add maintainers

Add @KrisThielemans @paskino @casperdcl as people who are happy to maintain repo (so they get push permissions)

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


syft test build

Make a test image build to add the syft arg and verify manually.
After verifying this, the syft arg will be added to the other image builds.

/hold
Doing a bit of testing on the side before making this change

/unhold


Displaying results from external REST endpoint.

We need to display results returned by a separate service, in a Grav page. This would be helpful for personalizing documentation. For example: our own system keeps track of everything about our users, including name, email, API key, etc. When a user browses to a Grav page, and if he is logged in, we want Grav to call our system's REST endpoint to fetch the user info, then render the info on the Grav page, if necessary.
This would help personalize documents, and create a cohesive UX for users. For example, this would allow a Grav page to say: "Please use this API key: 123456-abcde for your application", without the user having to do anything else.
Currently, many documentation systems ask you to log into a separate dashboard to get pieces of info, then get back to the documentation again, like: "Please log into your dashboard, do A, do B, ..., find the API key, ...", which isn't the best, IMHO.
I guess in order to implement such a feature, I would need to:
1 install the Grav login plugin;
2 upon generating a Grav page, if the user is logged in, call the REST endpoint;
3 instantiate Twig variables with the result so that they are rendered.
Is this a feasible way to approach this?
Thanks!

I'm using this one: https://github.com/Mashape/unirest-php , it should take care of calling to the external site. With some local caching (only fetch once per session), the site should remain fast enough.
Displaying the data depends on where you want to show it. The easiest approach would be to register your object/class into the Grav CI container and just call it from the template file.


Default screenshot for all localize

Issue Description
How i can upload screenshot just only for en-US  then use it for all localize that i active in metadata

@lifez  you should look at the new screenshot manager on iTunes Connect, I believe it will handle it for you. This is out of fastlane's scope.

As far as I know, if you only provide iPhone 6 Plus screenshots to deliver/fastlane, it will automatically use the same screenshots for all device sizes 👍

@jcampbell05 On itune connect it need to check checkbox on language that need to use en-US screenshot
I think delivery shoud do it instead ?

@KrauseFx On itune connect it need to check checkbox on language that need to use en-US screenshot
I think delivery should do this for provide default screenshot ? ?

@lifez sorry, I'm not sure I understand the question

@KrauseFx Sometime I want to use en-US screenshot apply to all localize that i active
Currently workflow is -> upload en-US screenshot by deliver and check to use en-US screenshot for each of localize in iTuneConnect website

Yeah, you'll have to do that using iTunes Connect, deliver doesn't currently do that for you


Add in Verkle Proof Benchmark

I added in a quick benchmark for Verkle proofs, I was also getting benchmark times of ~2 hours and occasional hangs on 10,000,000 items (M1 Pro 32 GB of RAM), so I reduced that to make it more manageable while iterating on the library. I'm not sure how to write an edit benchmark or what you meant by that (inserting over values or stem updating?) so I was hoping you would be able to tackle that

squash and merge as always ofc


Components doesn't work in Brave browser

Please provide the environment you discovered this bug in.
Hi All,
i didn't find any specification a about browser support. I took a look around in the components section and Accordion failed to open in this Brave Version 1.61.109 Chromium: 120.0.6099.144 (Official Build) (64-bit).
In Opera work all fine. Opera One(version: 105.0.4970.21)
Cheers!
Which area/package is the issue in?
accordion
Description
Component doesn't open on click event
Please provide the exception or error you saw
ERROR TypeError: Cannot read properties of null (reading 'firstChild')
    at S9 (vendor-e35b74e6.js:7:96783)
    at I9 (vendor-e35b74e6.js:7:96992)
    at al (vendor-e35b74e6.js:7:96300)
    at K9 (vendor-e35b74e6.js:7:106763)
    at hi (vendor-e35b74e6.js:7:106097)
    at Hi (vendor-e35b74e6.js:7:106601)
    at template (accordion.page-bc7ee3e4.js:1:2488)
    at Uv (vendor-e35b74e6.js:7:63551)
    at $d (vendor-e35b74e6.js:7:82071)
    at kD (vendor-e35b74e6.js:7:81875)

Other information
No response
I would be willing to submit a PR to fix this issue

[ ] Yes
[ ] No

@elite-benni I think that's from our recent changes. We should probably add checks for this as we rely on a browser API directly

I will have a look at it.

I just downloaded the latest Version of Brave, which should be the same as you have.
Version 1.61.109 Chromium: 120.0.6099.144 (Offizieller Build) (64-Bit)
Cannot see any errors on click and it opens just as expected.
Do you get the error on the docs site https://www.spartan.ng/components/accordion?
Is it possible that an extension is causing this error?

I can confirm that the issue was caused by a browser extension.
Thank you for conducting the investigation!

Closing this as this seems fixed! Thanks @elite-benni!


[ Refactor ] Format and Lint / Fix Typings

[x] setup formatter and linter
[x] Add workflow for frontend
[x]  fix typing

This work is so impressive!!
When I try this version, the speed of loading/refreshing is so much faster!
but, activating Reset To White is not working...

Thanks, it's working.
The only issue we have now is this:


A_CONST and NULL/empty string

These 2 queries output the exact same tree:
SELECT ''

SELECT NULL

I think there is a bug in the handling of A_CONST with empty string values.
Here is the output for reference:
https://gist.github.com/zhm/715a15c1b4d89a6d9807

I actually think I see the bug here https://github.com/lfittl/libpg_query/blob/master/patches/01_output_nodes_as_json.patch#L145
But I'm not sure if it's intentional to handle another case.

I think you are right that it should return an empty string - I'll make that change, wanted to re-arrange something with that patch anyway :)

I'll close this since you fixed it in #5 :tada:


Option to disable scrub-looping

Is your feature request related to a problem? Please describe.
Beeing able to scrub back and forth by moving the mouse on screen is my favorite thing about mrv2. However, if you scrub beyond the end of a video, it will simply loop back to the start of the video. This can be quite useful, but there are cases where i would prefer to not have this behavior and instead lock the scrubbing range to the start and end of the video.
Describe the solution you'd like
Either introduce a new setting to disable/enable scrub looping (preferred solution), or disable it when "Looping Mode" is set to "Stop".

Try these new v1.2.2 betas which should fix both the scrub behavior (when loop is off) and some fullscreen/presentation issues:
.exe:
https://mega.nz/file/yeY0mbiL#DlWmaGGPKb58JOpEOrDRfiumvW_U1HranRrK5CASkNU
.zip:
https://mega.nz/file/fK5k2R5S#3sYCKj6fay3lRdHOhIbWUU3U3ilWtV7CbM52TsiENuc

Works beautifully! Both problems solved then.


Add ability to show metric measurements in dump1090.

Ask the user if they wish to use metric or imperial measurements when setting up dump1090-mutability. If this can be made possible securely add the ability to the administration panel as well.

metric good....  although I seem to recall one of the feeders requires the user to input the receiver elevation in some strange unit which I cant quite recall... was it hands, or perhaps feet? ;)

Changes to dump1090's configuration should have no effect on any other altitude setting.

Added to dump1090-mutability setup script in commit 3801d8b379ec1373c554420d5d4ad2d2905875c6.


Perform build using multiple processes

Hey folks,
is multiprocess build of a single target possible? I mean something like map/reduce pattern for multiprocess chunk generation and their subsequent reduction done in parallel?

You might want to check out happypack.

@bebraw This solution looks interesting, but it's still on the early stage of development now

@devlato Yeah. If you have multiple configurations, parallel-webpack might work.

@bebraw I'm already using it, but it speeds up nothing with my webpack configuration, so the idea from my original question is to generate chunks in parallel using multiple processes as it's done in happypack, but happypack is not ready yet for practical use

@devlato Ah, ok then. It's definitely a hard problem. 👍

Closing as solutions were presented.
Please use Stack Overflow for these kind of questions.


Comprehensive test suite with py.test

While I'm hesitant to buy in to py.test in per-module unit-tests I do think that it would be worth experimenting on a comprehensive test suite.  The current solution in https://github.com/ContinuumIO/blaze/blob/master/blaze/compute/tests/test_comprehensive.py could be improved.

@ltransom you've had some thoughts along these lines.  Thoughts on this approach?

I have a PR up that refactor the existing comprehensive test suite into a py test friendly version using parametrized fixtures


Appstudio update test-custom-default-branch-jiou

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-mijr-on-pull-request-
creating pipelinerun test-annotations-mijr-on-pull-request- in namespace build-e2e-kwli-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wadk-on-pull-request-
creating pipelinerun test-simple-build-wadk-on-pull-request- in namespace build-e2e-kwli-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-lqle-on-pull-request-
creating pipelinerun test-simple-build-lqle-on-pull-request- in namespace build-e2e-kwli-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-gcoj-on-pull-request-
creating pipelinerun test-annotations-gcoj-on-pull-request- in namespace build-e2e-kwli-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nyrh-on-pull-request-
creating pipelinerun test-simple-build-nyrh-on-pull-request- in namespace build-e2e-kwli-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ufgi-on-pull-request-
creating pipelinerun test-simple-build-ufgi-on-pull-request- in namespace build-e2e-kwli-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-yrqk-on-pull-request-
creating pipelinerun test-annotations-yrqk-on-pull-request- in namespace build-e2e-kwli-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-mcmm-on-pull-request-
creating pipelinerun test-simple-build-mcmm-on-pull-request- in namespace build-e2e-kwli-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-vchz-on-pull-request-
creating pipelinerun test-annotations-vchz-on-pull-request- in namespace build-e2e-kwli-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-uqzm-on-pull-request-
creating pipelinerun test-simple-build-uqzm-on-pull-request- in namespace build-e2e-kwli-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


Release branch v1.3.1

Minor Release
This is a minor release with new features, some performance improvements, and various bug fixes.
Added

Support the hosts file as a source for resolving hostnames.
Including the OS version in the DoH header.
Including the client's IP address when ctrld is an upstream of dnsmasq.

Improved

Making PTR lookup failures less noisy for users.
Upgrading quic-go to v0.38.0
ctrld now generates a working default configuration in both cd and local mode.
Using /etc/version to detect a UniFi Gateway.
The general performance and stability of ctrld:

All upstreams are monitored to prevent high resource consumptions in case of outage.
Guarding against DNS loops.

Fixed

Service restart loop in EdgeOS.
Using Control D bootstrap DNS for the OS resolver, fixed #59.
Fix the default route IP address with the public interface.
Fix the setting of DNS so that it takes effect in some cloud providers with systemd-resolved.

Been waiting on this one


fix: No more "thanks for using Mirror" Debug.Log on built headless/standalone instances.

MrGadget and I discussed this in the developer channel of the Discord. Basically, Mirror shouldn't be advertising itself outside of the Editor, mainly because the message takes up 4 - 5 lines (consisting of the "Thanks for using Mirror" text, then some line breaks and the Debug.Log stacktrace).
Other network libraries keep quiet in built applications and only emit warnings/errors unless they're on debug mode or initializing (ie. "SomeNetworkLibX v1.0 initializing on Win64")
We simply wrap the thank you with a check to ensure that it only gets emitted if we're on something that's not a server instance or a standalone instance.

why :((

Heh, I knew this was going to happen.
I'll happily compromise if you let me have a bool that says "Advertise Mirror" in the NetworkManager. That way people can have it on if they want Mirror advertisments in their logs. 😛
...Which might even lead to an April Fools developer joke later down the track, we'll see.
Okay, jokes aside, it's just a minor nitpick I know, but I guess at the end of the day it's only one line of code and when my server instance boots I have a lot of diagnostic and startup info that gets broken up because Mirror toots its own trumpet. Apparently MrG thought it was supposed to only trigger on development builds, and be silent in non-dev builds at some point?

I think we should keep it for now.
Originally I added this for debugging so it's obvious that someone uses Mirror and not UNET.
That might still be useful these days.


Uniquify people doesn't propagate?????

I have uploaded in the past a great number of data form a spreadsheet therefore creating many "ghost" authors.
These are gradually being replaced with the real ones.
By successfully using UNIQUIFY PEOPLE I expected to get rid of all ghost names in the auto-complete for example in the "New Source" module.
But the ghosts persist there -- how do I get rid of them?

@adrik29 can you list a couple of examples that should be gone?

Yes, for example, all ghost Seisho Suzuki in my project have been merged.

However, when I try to edit a source all ghost reappear:

I see these are Suzuki's that you created.  So either the merge failed, or there were more than you merged?

What is the ID of the "real" Suzuki?

What is the ID of the "real" Suzuki?

It is 457:

Are all the Suzuki's that you created initially the same?  If so I will experiment with the remainders?

They are the same PERSON. There is only one Suzuki who worked on Opiliones, although it is a fairly common surname.
And yes, they were all created simultaneously when I made my huge initial upload en 2018.

@adrik29 I suspect you only merged the first 100 and that there were more to merge (based on dates). I.e. you may have to repeat the search, only 100 results at a time are returned.
I merged the remainder.

mjy -- ah -- I never knew there was this 100 items limit!
So I should refresh because it said ALL the ghost Suzuki had been merged into the real one = that means it found ZERO Suzuki after the initial merging.

But it doesn't work anyway:

I never had an issue merging large number of authors, but sometimes you have to do it multiple times. In cases like this, it works easies if you first merge those, which are unused or have a single use, and than merge them to a currated one.
If this task is updated, please take #2050 into account

I just missed the hundreds more, has to be repeated again with reminders.
Notice the years get more recent as the old records are merged.
On Sun, May 2, 2021, 1:15 PM Dmitry Dmitriev @.***>
wrote:

I never had an issue merging large number of authors, but sometimes you
have to do it multiple times. In cases like this, it works easies if you
first merge those, which are unused or have a single use, and than merge
them to a currated one.
If this task is updated, please take #2050
https://github.com/SpeciesFileGroup/taxonworks/issues/2050 into account
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/SpeciesFileGroup/taxonworks/issues/2215#issuecomment-830849539,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAFQSE4C3OTDXKRF4ANSYDTLWJFZANCNFSM4364PJQA
.

I believe there is an error when you try to merge 100s of people.  Perhaps some records fail.  When I try 5 or so batches, it works.  When I try 100, at least some fail.

Related: https://github.com/SpeciesFileGroup/taxonworks/issues/2218

Wow -- this takes much more work than I first thought. Anyway, I like a lot the direction that you guys are guiding TW to.
The tools are improving a lot and at least we in the Opiliones Project are always perfecting the database...


Feature:  Custom DHCP/BOOTP options for Kea DHCP

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Is your feature request related to a problem? Please describe.
In migrating from ISC DHCP to Kea DCHP one feature is still missing for me -- the ability to add custom DHCP/BOOTP options. (As defined here). For example I'm using option 43 (Vendor Specific Information) to assist in adoption of new Ubiquiti network equipment.  Kea seems to have the ability documented here.
Describe the solution you like
The ability to add custom DHCP/BOOTP option similar to the current ISC DHCP interface.
Describe alternatives you considered
Giving up and staying with ISC DHCP until it no longer is offered. :)
Additional context
That's it, thanks for considering!

same as https://github.com/opnsense/core/pull/7361#issuecomment-2112933052 ?

Wow, sorry I didn't think to search the PRs.   That would definitely take care of my need, and looks more elaborate than the current ISC DHCP/BOOTP options implementation -- where you just add raw number, type, value combinations.   I'll just follow that issue.  Thanks!

@Codelica no problem, on our end we just were not able to reach a functional state, we kept the code in a separate branch. When we know what the [kea] configuration should look like and there are people confirming it actually works, it shouldn't be a huge deal to finish the work.

There is Kea 1.6.0 in the pipeline, but I'm a bit reluctant to pull this in for 24.1.x. It might change things, but it might also bring new issues.


Where can I find the demo and how can I open the editor?

Hello,
could you please add a demo project to the solution?
After applying the .ngI18nconfig  file, I can not figure out how to open the editor.
Is it possible to have only the .ngI18nconfig  and the .xlf files in one folder
and open the folder with vscode in order to edit the files using the editor?
An example of the folder structure:
<Folder>
    <.ngI18nconfig>
    <somefile.en-IE.xlf>
    <somefile.ro.xlf>

Ctrl+Shift+P - start typing "Angular i18n" and run the command.


Update jasync-common, jasync-mysql, ... to 2.1.19

Updates

com.github.jasync-sql:jasync-common
com.github.jasync-sql:jasync-mysql
com.github.jasync-sql:jasync-postgresql

from 2.0.8 to 2.1.19.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.jasync-sql" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.jasync-sql" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #2698.


Error when building

I copied the full example, but I get this error when building:
Error	LNK2019	unresolved external symbol _main referenced in function "int __cdecl invoke_main(void)" (?invoke_main@@YAHXZ)	HdrTest	C:\Users\natan\Desktop\HdrTest\MSVCRTD.lib(exe_main.obj)	1

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

ID: eda99bc7-483b-e53c-1035-886f4d0955f4
Version Independent ID: a6fdba4d-53e4-9f1a-2352-bc68ef491069
Content: Walkthrough: Create a traditional Windows Desktop application (C++)
Content Source: docs/windows/walkthrough-creating-windows-desktop-applications-cpp.md
Product: visual-cpp
Technology: cpp-windows
GitHub Login: @mikeblome
Microsoft Alias: mblome

I have tried changing the subsystem to Windows

As outlined here https://stackoverflow.com/questions/33400777/error-lnk2019-unresolved-external-symbol-main-referenced-in-function-int-cde
But that did not solve the problem.

Going back and choosing under Application type, Desktop application solved the problem. Note that there is no "Windows Application" anymore as the docs suggest.

@natanfudge
Thanks for reporting the issue. I've updated the wording to mention the Desktop application choice, and fixed an analysis issue in the code. The changes should be live tomorrow.


Add source location to TemplateBody

Description of changes
Partially resolves #521 by adding source info onto TemplateBody. This source info is then added onto InvalidActionApplication validation errors that did not previously have a source range.
More work we could do later would be adding source information onto each scope constraint for more precise error reporting, but this is a substantial amount of extra work.
Issue #, if available
Checklist for requesting a review
The change in this PR is (choose one, and delete the other options):

[x] A backwards-compatible change requiring a minor version bump to cedar-policy (e.g., addition of a new API).

I confirm that this PR (choose one, and delete the other options):

[x] Updates the "Unreleased" section of the CHANGELOG with a description of my change (required for major/minor version bumps).

I confirm that cedar-spec (choose one, and delete the other options):

[x] Does not require updates because my change does not impact the Cedar formal model or DRT infrastructure.

Should we think about wrapping TemplateBody in some sort of Node? Or do we want consistency like what do for error types?


update plugins to work with updated go-plugin

Signed-off-by: Steve Kriss<EMAIL_ADDRESS>Turns out #1303 introduced some runtime breaking changes.  the GRPCPlugin interface exported by go-plugin changed -- added context and broker fields.  Unfortunately, it wasn't a compile-time error due to how the types work.  I updated our implementations and added type checks for the future.
cc @carlisia

updated


Make key generic

But probably the cmp function is also needed.
Thank you for this library!

Thank you for this @data-man!
I will take a proper look at this later today, but looks good so far.

Thanks for the PR! I'll think of a nice API to provide a cmp function.


Clean up IOS code to use Extensions

IOS Classes need to be cleaned up, into a more standard:
class Name { }
extension Name : Protocol1 {}
extension Name : Protocol2 {}
style.

Unsure whether it's worth while to separate out RCTEventEmitter as that would require all the functions that use sendEvent to be pulled out as well.   Seems like it's not worth the "best practice" so I'll leave it as is for now.