defaultGemConfig.mathematical: fix cross compilation

Motivation for this change
Things done

[x] 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"
[ ] 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)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I suggest also passing strictDeps = true; as that helps determining whether the deps are in the right place.

@FRidh I have no idea about ruby packaging, but I had to add several libraries to buildinputs and add ruby to nativebuildinputs after I enabled strictdeps.

Possible to get this merged?

Thanks!
On Fri, Jul 10, 2020, 1:48 PM Frederik Rietdijk<EMAIL_ADDRESS>wrote:

Merged #91077 https://github.com/NixOS/nixpkgs/pull/91077 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/91077#event-3532445258, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGRJXGO4MEFJMSQ377AFELR22TSVANCNFSM4OCNCKYA
.


Operator namespace name label for network policies missing

The version v1.0.0 does not set a name label. This is required for the network policies created in openshift4-logging.
The namespace can be manually labeled, in example:
oc label ns openshift-operators-redhat name=openshift-operators-redhat

Steps to Reproduce the Problem

Create a new cluster
Deploy openshift-operators as openshift-operators-redhat
No name label is set

Actual Behavior
No name label is set.
Expected Behavior
There must be a name label name=${name of instance}

Can't reproduce this, when compiling the component the resulting namespace object does have label name:
$ cat catalog/manifests/openshift4-operators/openshift-operators-redhat.yaml
apiVersion: v1
kind: Namespace
metadata:
  annotations:
    openshift.io/node-selector: ''
  labels:
    name: openshift-operators-redhat
    openshift.io/cluster-monitoring: true
  name: openshift-operators-redhat
---
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  annotations: {}
  labels:
    name: openshift-operators-redhat
  name: openshift-operators-redhat
  namespace: openshift-operators-redhat


No Image

I am using Mac OS 10.11.6, I got no image, how to solve the problem

happened to be for a bit, but then went away on its own

It happens to me as well (I'm on Ubuntu), although it goes away on its own as @sg-s said.
I have no idea why it's happening: maybe it's a bug in the programs we're calling?

I think it's something to do with dates & timezones.
For instance, I'm in New Zealand (UTC+12), and currently it tries to request the tile 2016/08/06/003000, where as the latest tiles avaliable are for 2016/08/05/223000.
It's trying to request the tiles from tomorrow (or something like that).

@imnofox you are correct, fixed the problem by deleting
line 36        offset_tmp = offset_tmp + timedelta(hours=offset)

Isn't deleting that line just the same as disabling auto_offset in config.py?

@imnofox is right. The issue is still unsolved so I reopened it. I'll work on a fix asap.
Thanks everyone for figuring it out. Really really nice catch!

@boramalper is it a logic issue? I am in New Zealand,  which is 2 hours beyond the himawaripy time, but the code requests IMG base on NZ time which is a future time. I have check the code offset hour is correct, which is 2 hours,

Local time
himawaripy time
Local time

6PM
9PM
11PM

Offset Hours
-3
0
2

11PM - 2hours = 6PM - -3hours = 9PM

line 36        offset_tmp = offset_tmp - timedelta(hours=offset)

It's an issue of himawari8 website itself, sometimes it just didn't have any images.
You can have a try here:
http://himawari8.nict.go.jp/himawari8-image.htm?sI=D531106&sCl=false&sClC=ffff00&sS=4&sNx=1&sNy=0&sL=-167&sT=-534&wW=2497&wH=861&sD=1471056000000
I'm not sure if it's same(black background with "No Image" on it) for you
how to solve it:
if you got a "No Image" response
try to request a more earlier image
20 minutes delayed is near-realtime too

And I have another question about why we need time zone offset ...
you know that himawari8 is a geosynchronous orbit satellite.
it can't capture image of earth on the other side ...

@Detavern because if you didn't, and lived in the Western Hemisphere, with no offset, you'd only see a dark picture during the daytime hours (when you're awake and using your computer)

@sg-s but.. even you awake, looking at the Australia on image with sunshine, you may suddenly realize that the Western Hemisphere is still in dark XD
maybe we need another satellite

yeah, this is a workaround because we don't have access to an equivalent satellite for the western hemisphere.

Hello,
as I've said in #82, this was due to a problem in time logic of himawaripy.
Can you please make a clean installation of v2 (https://github.com/boramalper/himawaripy/tree/v2) and let me know if it fixes your problem?
Thanks!

I assume the problem has been solved, let me know if it still persist. Thanks!


support match expressions in resource flavor

What would you like to be added:
support match expressions in resource flavor
Why is this needed:
maybe some high priority job don't want to run on spot nodes, now we have to add all
nodes except for spot nodes to the one or multiple resource flavors, which is difficult
if we have a large cluster
Completion requirements:
This enhancement requires the following artifacts:

[x] Design doc
[x] API change
[x] Docs update

The artifacts should be linked in subsequent comments.

/assign
This will involve API changes, scheduling logic changes, and test case changes. If necessary, I will submit a KEP for discussion.

support match expressions in resource flavor

Do you assume to add a new member to the following?
https://github.com/kubernetes-sigs/kueue/blob/64434d0ca4c9ecca24494e779d4dc63523ff1496/apis/kueue/v1beta1/resourceflavor_types.go#L36C40-L37

@tenzen-y yes, we can either add a property of v1.matchexpression type in ResourceFlavorSpec or change map[string]string to v1.labelSelector type

change map[string]string to v1.labelSelector type

I think we can not add changes without backward compatibility to API since our API version is beta.
So, as you say, I think we can add a property of v1.matchexpression type in ResourceFlavorSpec .
However, I'm not sure the reason why we should support v1.matchExpressions in resourceFlavor since I think we should add Toleration to Node and create resourceFlavor with Taints in your case.

Also, users can directly add nodeAffinity batch/job. So the workload will be scheduled to Node matched nodeSelector injected by kueue and nodeAffinity specified by users.

cc: @kerthcet

Are nodeTaints in the ResourceFlavor not enough to express this semantics?


Save the complete solution to CSV

Pull request details
Describe the changes made in this pull request
Change the function save_solution_to_file to print the complete solution to files with appropriate names.
Stop saving the output in git.
Use Norse to test save_solution_to_file instead of Tiny, for completeness.
List of related issues or pull requests
Closes #295
Collaboration confirmation
As a contributor I confirm

[ ] I read and followed the instructions in README.dev.md
[ ] The documentation is up to date with the changes introduced in this Pull Request (or NA)
[ ] Tests are passing
[ ] Lint is passing

I will do #490 and #492 before this.

Thanks for the review.

Oh but you didn't check the boxes. >.>


fl_contrast_mode is not exposed

https://www.fltk.org/doc-1.4/group__fl__attributes.html#ga97d26b73ccb60281ea6ae9ab94f4e9df
as far as I can see this API is not available in fltk-rs - its new in 1.4

I've added the api a few days ago and just got around to testing it. You can test it by trying the master branch of fltk-rs:
[dependencies]
fltk = "^1.4"

[patch.crates-io]
fltk = { git = "https://github.com/fltk-rs/fltk-rs" }

I can confirm this works - ty


fix: Resolve vulnerabilities in axios

CI failed during Snyk scan:
Issues with no direct upgrade or patch:
  ✗ Prototype Pollution [High Severity][https://security.snyk.io/vuln/SNYK-JS-AXIOS-6144788] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>  This issue was fixed in versions: 1.6.4
  ✗ Improper Input Validation [High Severity][https://security.snyk.io/vuln/SNYK-JS-FOLLOWREDIRECTS-6141137] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>  This issue was fixed in versions: 1.15.4

For reference from https://security.snyk.io/vuln/SNYK-JS-AXIOS-6144788, we don't actually use the formDataToJSON function. Not as sure about https://security.snyk.io/vuln/SNYK-JS-FOLLOWREDIRECTS-6141137, since that's deep within swagger-ui.
I am curious, is Snyk just failing earlier than dependabot has a chance to upgrade?
Also glad to see you've gotten the hang of modifying / manipulating the yarn.lock file 🙂


ADD:	Added randlistelement code

Added myself to contributors

Is this not better accomplished with random.choice?

Yes random.choice() is also a vailable option (and more obvious perhaps), but getting the element with randrange is quicker as it doesn't create a new range object.
I could add it to the POC, for completeness.
Thx

Given the choice (:wink:) between random.choice(my_alpha_list) and my_alpha_list[random.randrange(len(my_alpha_list))], I'd pick choice() for:

readability - shorter and easier to read/comprehend
maintainability - renaming the array would require only one replacement

In any case, I was curious about your comment about randrange() being "quicker", so I ran some tests, which showed choice() is actually faster by about 300ns.
# test.py
import random

arr = [1] * 10000000

def randrange():
    arr[random.randrange(len(arr))]

def choice():
    random.choice(arr)

# Python 2.7.10
$ python -m timeit -s'import test' 'test.choice()'
1000000 loops, best of 3: 0.975 usec per loop

$ python -m timeit -s'import test' 'test.randrange()'
1000000 loops, best of 3: 1.26 usec per loop

# Python 3.5.1
$ python3 -m timeit -s'import test' 'test.choice()'
1000000 loops, best of 3: 1.49 usec per loop

$ python3 -m timeit -s'import test' 'test.randrange()'
1000000 loops, best of 3: 1.79 usec per loop

@tony19 Yes tests really do confirm that random.choice is quicker than randrange. I actually made my assumptions on https://docs.python.org/2/library/random.html#random.randrange thinking that since it didn't create a range object, it would be faster.
But I didn't actually test it.
Thanks!


chore(deps): update terraform terraform-ibm-modules/landing-zone/ibm to v5.31.1

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/landing-zone/ibm (source)
module
patch
5.31.0 -> 5.31.1

Release Notes

terraform-ibm-modules/terraform-ibm-landing-zone (terraform-ibm-modules/landing-zone/ibm)
v5.31.1
Compare Source
Bug Fixes

deps: update terraform ibm to latest for the landing zone das (#872) (08bacf2)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.7.18 :tada:
The release is available on:

GitHub release
v1.7.18

Your semantic-release bot :package::rocket:


Support futures in from_delayed

This is a bit wonky in that I had to compute before calling assert_eq.
Still this is a common tripping point.
cc @jcrist for review

cc @jcrist can I get a quick yes/no on if you agree with this change?


Import flxanimate on hmm too

so it fixes the action builds

i mean I know that I had to do this but I just didnt wanna "steal" that guy's work
In your opinion should I do it all in my pr?

like i was expecting shadow to use both prs, thats why i didnt do it

but actually at this point i think its better if i do it all in one pr, ty

i hope i wont feel guilty about it💀


feat: add blas/base/scabs1

Description
This RFC proposes to add a routine to compute the sum of the absolute value of the real and imaginary part of a single-precision complex floating-point number as defined in BLAS scalar operations. Specifically adding @stdlib/blas/base/scabs1 is proposed.
Related Issues

Does this pull request have any related issues?

None.
Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

@aman-095 Thanks for making the changes. Anything else needing to be done? If not, you can go ahead and port the changes over to dcabs1 so we can get that one over the finish line, as well.

Thanks, Athan, for reviewing. This seems fine to me. I'm also replicating this in dcabs1 and will push the changes soon.


How are Helm hooks supported with helm Operators?

Type of question
Are you asking about community best practices, how to implement a specific feature, or about general context and help around the operator-sdk?
General context question regarding use of SDK to convert Helm charts to Helm-based Operators.
Question
Are helm hooks supported with Helm-based Operators and how do I convert a Helm chart which is using them to an Operator? Are there limitations and/or pitfalls that I need to be aware of?

The helm operator is based on Helm 3. In this way, I'd recommend you check the Chart Hooks docs to know how to work with. Please, let me know if it answers your question and feel free to raise new issues if you face any problem with.

hi @camilamacedo86, all our charts are currently build for Helmv2.  Will we have to rebuild our charts to support helm v3 now? Thanks.

Hi @mmellin,
I'd recommend you migrate your chart from V2 to V3 and use the latest released version of SDK 0.18 to create your project. In the latest release was removed the automatic migration of Helm releases from v2 to v3. (#2918). More info: Changelog
Also, note that if you try to use an old version of SDK (automatic migration of Helm releases from v2 to v3) you can end up in situations such as for example: Note that the crd-install hook has been removed in favour of the crds/ directory in Helm 3. as described by @joelanford https://github.com/operator-framework/operator-sdk/issues/2647.
See:

That you can use a plugin Helm v3 2to3 plugin to help you with. More info: How to migrate from Helm v2 to Helm v3
Migrating Helm v2 to v3

@joelanford, could you please let me know if I misunderstood or if I am missing something here.

Helm 3 is backwards compatible with Helm 2 charts, so it shouldn't be necessary to upgrade to Helm 3.
The operator-sdk installs, upgrades, uninstalls releases using the Helm libraries, so all hooks should be supported out of the box.
We haven't seen too many questions about chart hooks in the context of a running operator, so there may be some gotchas that we're not aware of.
Are there specific hooks you've tried to use that are not working or doing something unexpected?

Hi @mmellin,
Shows that the information provided above attended your expectation so I am closing this one. However, please feel free to ping us here if you think that it should be re-opened and/or raise new issues.
Also, if you try any specific hook that not work or see that it is doing something unexpected please let us know.


drivers: hwinfo: Exclude GECKO driver on EFR32MG21

The EFR32MG21 doesn't have a RMU and thus the driver isn't relevant for
that SoC series.  Add a Kconfig exclusion so the driver isn't available
on EFR32MG21 SoCs.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

I merged the previous PR thinking this fix was going to end up being more involved, but ended up being simpler than I thought.


pandas.read_hdf

Hi Niels,
Many thanks for this image which is very useful.
pandas.read_hdf requires the tables module.  Would you be able to add
pip install --upgrade tables
to your docker file?
(I have raised this with jupyter as sorting it in the earliest image that imports pandas probably makes most sense.  It might be that they prefer not to add it and this extra module fits quite well with the long list of optional extras at the end of your docker file...
Also, your image does not seem to have a tag (other than latest).  Are you able to give it a tag - so that if you change it we know which image we are pulling?

Hello Alan,
Sorry for the late answer! I just had merged the pull request for the upgrade of "tables".
I tested it locally with this script and it worked fine:
import numpy as np
import pandas as pd

df = pd.DataFrame({
    'A': [1, 2, 3, 4, 5, 1, 2, 3, 4, 5, 1, 2],
    'B': [0, 0, 1, 1, 1, 0, 1, 0, 1, 0, 0, 1],
    'C': [34, 32, 35, 34, 31, 34, 29, 34, 12, 34, 32, 34],
    'D': [11, 15, 22, 15, 9, 15, 11, 15, 14, 15, 13, 15]})

df.to_hdf('/tmp/out.h5', 'results_table', mode='w', data_columns=['A'],
          format='table')

print(pd.read_hdf('/tmp/out.h5', 'results_table', where='A in [1,3,4]'))

Can you pull the latest image, try this script on your side and validate that this is the behavior you expected?

About your docker tag request :

I totally agree, it's a good idea to start tagging future versions of the image! ( Until now I hadn't felt the need because... I was the only one using this image ^^ )
As a result, I just pushed the tag v.0.0 which corresponds to the version before the upgrade of "tables" (your correponded issue), and tag this new version as latest.
So far, I've done it manually. But I think later this week I will push new things to this repository to add a minimal form of CI (Makefile, JenkinsFile ... )!

Besides, I noticed that you cloned this repo and made your own modifications: if you think there are features that could be useful, don't hesitate to fork and propose your own pull request ! ;)
Cheers

Hi Niels,
Thanks.
I’m teaching some students at a University and I had to get an image to them by start of this week - sorry! - otherwise I would have waited for your response.  At the time (last week) I was brand new to docker and I had no idea what to do and did not want to mess up anything in yours.
In my modifications, mainly I deleted quite a few of the extra packages that you load at the end - just to make the code that creates the image easier for me to read.  I also updated some packages (because the jupyter notebook on which it is based has an old version of one of them (pandas I think or sk-learn).  Finally I installed statsmods from master rather than pip because statsmods on pip does not run with the latest version of scripy (it is a known bug).  And actually I could not get tables to work!!  Each time I added it, the build failed!
When I get a chance I will add any useful mods I did to your images and leave it as a pull request.
Very many thanks for your everything.
Regards
Alan

On 4 Jun 2019, at 23:30, Niels Borie<EMAIL_ADDRESS>wrote:
Hello Alan,
Sorry for the late answer! I just had merged the pull request for the upgrade of "tables".
I tested it locally with this script and it worked fine:
import numpy as np
import pandas as pd
df = pd.DataFrame({
'A': [1, 2, 3, 4, 5, 1, 2, 3, 4, 5, 1, 2],
'B': [0, 0, 1, 1, 1, 0, 1, 0, 1, 0, 0, 1],
'C': [34, 32, 35, 34, 31, 34, 29, 34, 12, 34, 32, 34],
'D': [11, 15, 22, 15, 9, 15, 11, 15, 14, 15, 13, 15]})
df.to_hdf('/tmp/out.h5', 'results_table', mode='w', data_columns=['A'],
format='table')
print(pd.read_hdf('/tmp/out.h5', 'results_table', where='A in [1,3,4]'))
Can you pull the latest image, try this script on your side and validate that this is the behavior you expected?
About your docker tag request :
I totally agree, it's a good idea to start tagging future versions of the image! ( Until now I hadn't felt the need because... I was the only one using this image ^^ )
As a result, I just pushed the tag v.0.0 which corresponds to the version before the upgrade of "tables" (your correponded issue), and tag this new version as latest.
So far, I've done it manually. But I think later this week I will push new things to this repository to add a minimal form of CI (Makefile, JenkinsFile ... )!
Besides, I noticed that you cloned this repo and made your own modifications: if you think there are features that could be useful, don't hesitate to fork and propose your own pull request ! ;)
Cheers
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/nielsborie/ml-docker/issues/1?email_source=notifications&email_token=ACQ7P32H3KZLGXCL6VAGMILPY3UH7A5CNFSM4HOQ7G62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW6BYSI#issuecomment-498867273, or mute the thread https://github.com/notifications/unsubscribe-auth/ACQ7P36VKXQAEXQNLCAL2ZLPY3UH7ANCNFSM4HOQ7G6Q.

Hi Alan,
You're welcome, what I did is not a big deal!
I'm going to close this issue, so maybe see soon during a possible pull request!
Regards
Niels


W391 implementation is missing despite being checked off

In a pycodestyle tracking issue https://github.com/astral-sh/ruff/issues/2402 the rule for W391 is checked but this does not exist in the ruff codebase. In fact there is a comment noting this. Can this be unchecked so the tracking and expectations is right and, ultimately, tackled?

Thanks, I unchecked it -- not sure how that happened!


Envoy returns "upstream connect error or disconnect/reset before headers"

@jrajahalme I'm observing the following behaviour:
$ docker run -d --net cilium -l id.foo tgraf/netperf
$ cilium policy import ./l7.json
$ docker exec -ti e0ea107ec814 curl google.com/
upstream connect error or disconnect/reset before headers
[...]

Policy loaded
[{
  "labels": [{"key": "name", "value": "rule1"}],
  "endpointSelector": {"matchLabels": {"id.foo": ""}},
  "egress": [{
    "toPorts": [{
      "ports": [
        {"port": "80", "protocol": "TCP"}
      ],
      "rules": {
        "HTTP": [
          {
            "method": "GET",
            "path": "/"
          }
        ]
      }
    },{
      "ports": [
        {"port": "53", "protocol": "UDP"}
      ]
    }]
  }]
}]

Debug log:
Jan 28 03:55:34 cilium-master cilium-agent[25302]: level=debug msg="RDS_56326:egress:TCP:80_1: Access log message: timestamp:1517140534201396700 http_protocol:HTTP11 cilium_resource_name:\"RDS_56326:egress:TCP:80_1\" cilium_rule_ref:\"PathRegexp(\\\"/\\\") && MethodRegexp(\\\"GET\\\")\" source_security_id:264 source_address:\"<IP_ADDRESS>:53480\" destination_address:\"<IP_ADDRESS>:80\" scheme:\"http\" host:\"google.com\" path:\"/\" method:\"GET\" headers:<key:\"user-agent\" value:\"curl/7.52.1\" > headers:<key:\"accept\" value:\"*/*\" > headers:<key:\"x-request-id\" value:\"e284a5a4-2881-4e40-aeaa-ee69b2c8dffe\" > "
Jan 28 03:55:34 cilium-master cilium-agent[25302]: level=debug msg="Logging HTTP L7 flow record" code=0 header="map[User-Agent:[curl/7.52.1] Accept:[*/*] X-Request-Id:[e284a5a4-2881-4e40-aeaa-ee69b2c8dffe]]" method=GET protocol=HTTP/1.1 type=Request url="http://google.com/" verdict=Forwarded
Jan 28 03:55:35 cilium-master cilium-agent[25302]: level=debug msg="RDS_56326:egress:TCP:80_1: Access log message: timestamp:1517140535205457700 http_protocol:HTTP11 entry_type:Response cilium_resource_name:\"RDS_56326:egress:TCP:80_1\" cilium_rule_ref:\"PathRegexp(\\\"/\\\") && MethodRegexp(\\\"GET\\\")\" source_security_id:264 source_address:\"<IP_ADDRESS>:53480\" destination_address:\"<IP_ADDRESS>:80\" scheme:\"http\" host:\"google.com\" path:\"/\" method:\"GET\" status:503 headers:<key:\"user-agent\" value:\"curl/7.52.1\" > headers:<key:\"accept\" value:\"*/*\" > headers:<key:\"x-request-id\" value:\"e284a5a4-2881-4e40-aeaa-ee69b2c8dffe\" > "
Jan 28 03:55:35 cilium-master cilium-agent[25302]: level=debug msg="Logging HTTP L7 flow record" code=503 header="map[User-Agent:[curl/7.52.1] Accept:[*/*] X-Request-Id:[e284a5a4-2881-4e40-aeaa-ee69b2c8dffe]]" method=GET protocol=HTTP/1.1 type=Response url="http://google.com/" verdict=Forwarded

It is an upstream connection timeout:
[2018-01-31 20:09:59.708][27712][debug][pool] external/envoy/source/common/http/http1/conn_pool.cc:65] creating a new connection
[2018-01-31 20:09:59.708][27712][debug][client] external/envoy/source/common/http/codec_client.cc:23] [C4] connecting
[2018-01-31 20:09:59.708][27712][debug][connection] external/envoy/source/common/network/connection_impl.cc:543] [C4] connecting to <IP_ADDRESS>:80
[2018-01-31 20:09:59.708][27712][debug][connection] external/envoy/source/common/network/connection_impl.cc:552] [C4] connection in progress
[2018-01-31 20:09:59.708][27712][debug][pool] external/envoy/source/common/http/http1/conn_pool.cc:91] queueing request due to no available connections
[2018-01-31 20:09:59.708][27709][debug][upstream] external/envoy/source/common/upstream/original_dst_cluster.cc:35] Adding host <IP_ADDRESS>:80.
[2018-01-31 20:09:59.708][27710][debug][upstream] external/envoy/source/common/upstream/original_dst_cluster.cc:35] Adding host <IP_ADDRESS>:80.
[2018-01-31 20:09:59.708][27711][debug][upstream] external/envoy/source/common/upstream/original_dst_cluster.cc:35] Adding host <IP_ADDRESS>:80.
[2018-01-31 20:09:59.708][27699][debug][upstream] external/envoy/source/common/upstream/original_dst_cluster.cc:35] Adding host <IP_ADDRESS>:80.
[2018-01-31 20:10:00.709][27712][debug][pool] external/envoy/source/common/http/http1/conn_pool.cc:313] [C4] connect timeout
[2018-01-31 20:10:00.709][27712][debug][connection] external/envoy/source/common/network/connection_impl.cc:144] [C4] closing data_to_write=0 type=1
[2018-01-31 20:10:00.709][27712][debug][connection] external/envoy/source/common/network/connection_impl.cc:177] [C4] closing socket: 1
[2018-01-31 20:10:00.709][27712][debug][client] external/envoy/source/common/http/codec_client.cc:70] [C4] disconnect. resetting 0 pending requests
[2018-01-31 20:10:00.709][27712][debug][pool] external/envoy/source/common/http/http1/conn_pool.cc:107] [C4] client disconnected
[2018-01-31 20:10:00.709][27712][debug][router] external/envoy/source/common/router/router.cc:456] [C3][S17103058144325641471] upstream reset

We have a connect timeout of one second:
					ConnectTimeout:  &duration.Duration{Seconds: 1, Nanos: 0},

However, no matter how much I increase this it still happens, which tells me that packets from the proxy to the world are not getting through, need see whats going on the monitor.

However, no matter how much I increase this it still happens, which tells me that packets from the proxy to the world are not getting through, need see whats going on the monitor.

OK, that makes sense. The policy does not allow egress to the outside world.

Just verified on master as of Jan 4th that this same problem is there, and also when using golang proxy. With Oxy the proxy keeps trying for 2 minutes, but the host sends a RST on each SYN-ACK coming back:
tcpdump: listening on enp0s3, link-type EN10MB (Ethernet), capture size 262144 bytes
10:56:11.015634 IP (tos 0x0, ttl 63, id 3186, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.41508 > <IP_ADDRESS>.80: Flags [S], cksum 0xa726 (incorrect -> 0x44ca), seq 923831919, win 29200, options [mss 1460,sackOK,TS val 1868317 ecr 0,nop,wscale 7], length 0
10:56:11.031335 IP (tos 0x0, ttl 64, id 45321, offset 0, flags [none], proto TCP (6), length 44)
    <IP_ADDRESS>.80 > <IP_ADDRESS>.41508: Flags [S.], cksum 0x4562 (correct), seq 969280001, ack 923831920, win 65535, options [mss 1460], length 0
10:56:11.031395 IP (tos 0x0, ttl 64, id 11001, offset 0, flags [DF], proto TCP (6), length 40)
    <IP_ADDRESS>.41508 > <IP_ADDRESS>.80: Flags [R], cksum 0xa0f3 (correct), seq 923831920, win 0, length 0
10:56:12.016841 IP (tos 0x0, ttl 63, id 3187, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.41508 > <IP_ADDRESS>.80: Flags [S], cksum 0xa726 (incorrect -> 0x43cf), seq 923831919, win 29200, options [mss 1460,sackOK,TS val 1868568 ecr 0,nop,wscale 7], length 0
10:56:12.041160 IP (tos 0x0, ttl 64, id 45325, offset 0, flags [none], proto TCP (6), length 44)
    <IP_ADDRESS>.80 > <IP_ADDRESS>.41508: Flags [S.], cksum 0x575f (correct), seq 969472001, ack 923831920, win 65535, options [mss 1460], length 0
10:56:12.041214 IP (tos 0x0, ttl 64, id 11194, offset 0, flags [DF], proto TCP (6), length 40)
    <IP_ADDRESS>.41508 > <IP_ADDRESS>.80: Flags [R], cksum 0xa0f3 (correct), seq 923831920, win 0, length 0
10:56:14.032117 IP (tos 0x0, ttl 63, id 3188, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.41508 > <IP_ADDRESS>.80: Flags [S], cksum 0xa726 (incorrect -> 0x41d7), seq 923831919, win 29200, options [mss 1460,sackOK,TS val 1869072 ecr 0,nop,wscale 7], length 0
10:56:14.047087 IP (tos 0x0, ttl 64, id 45329, offset 0, flags [none], proto TCP (6), length 44)
    <IP_ADDRESS>.80 > <IP_ADDRESS>.41508: Flags [S.], cksum 0x755a (correct), seq 969792001, ack 923831920, win 65535, options [mss 1460], length 0
10:56:14.047152 IP (tos 0x0, ttl 64, id 11588, offset 0, flags [DF], proto TCP (6), length 40)
    <IP_ADDRESS>.41508 > <IP_ADDRESS>.80: Flags [R], cksum 0xa0f3 (correct), seq 923831920, win 0, length 0

Same on db33c9340afaf726186dde57886586ac86b74b9b with Oxy proxy. I wonder if this has ever worked, or if the RST is introduced by a change in the Linux kernel?
To summarize:

Proxy initiates a new connection (TCP SYN) to the destination (google)
Google responds with a correct SYN-ACK (looks the same on tcpdump as the one w/o proxy)
Cilium host responds to Google with TCP RST.

Neither of 2. or 3. is visible in cilium monitor output, but 1. is.
This TCP-level bahavior is the same with both Go and Envoy proxies, but they manifest differently due to different timeouts and other proxy server behavior.
Currently I have no ideas on how to debug this further.

Should have noticed your response a bit earlier :-)
How should the policy be modified to allow traffic to world?

@tgraf IMO would be better drop traffic due to L3 before sending it to the proxy. And have the drop visible in cilium monitor :-)

So the issue is that ToEntities and/or ToCIDR is not yet supported with ToPorts?

IMO would be better drop traffic due to L3 before sending it to the proxy. And have the drop visible in cilium monitor :-)

Agreed. This is what set me off and what made me initially believe this is a proxy bug.


Update validation logic upstream in exportify for mz:is_current and other ints

When we exportify we need to set some values to ints (not JS default strings).
See: https://github.com/whosonfirst/py-mapzen-whosonfirst-export/blob/master/mapzen/whosonfirst/export/init.py#L127-L140

Chatted IRL w @nvkelso, but the py-mapzen-whosonfirst-export repo may not be the best place to add property type checks. The existing exportify code only checks types for two property flags that should be in every record. The ask here is to check property types for properties that are not in all WOF records.
I can still update the exportify code, but it might be best to wire these checks in another way.

Since these are checks that should happen on all documents before they end up in WOF, not just when editing through the WOF Editor, I think it might be better to put these checks in the validator repo, not the export repo. But I'm ok with putting them in the WOF editor for now.

Validated only cries fire, doesn’t fix. So I think for now we fix these in WOF-editor app while general solution is arrived at.
Sent from my handsful device.

On Feb 5, 2020, at 06:02, Ian Dees<EMAIL_ADDRESS>wrote:

Since these are checks that should happen on all documents before they end up in WOF, not just when editing through the WOF Editor, I think it might be better to put these checks in the validator repo, not the export repo. But I'm ok with putting them in the WOF editor for now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Here's a list of properties that should have integer values of either -1, 0, or 1. Eventually, these should each be checked in the validate tools, but it seems best for the wof-editor app to handle these check for now (rather than the exportify or validate code):
Optional properties, existing on some WOF records now, each should have int values of -1, 0, or 1:

mz:hierarchy_label_country
mz:hierarchy_label_county
mz:hierarchy_label_localadmin
mz:hierarchy_label_locality
mz:hierarchy_label_macrocounty
mz:hierarchy_label_macroregion
mz:hierarchy_label_region
mz:is_approximate
mz:is_funky
mz:is_hard_boundary
mz:is_landuse_aoi
mz:is_official
wof:megacity
wof:statistical_gore

Properties that are written to every record through the Exportify tool, each should have int values of -1, 0, or 1:

mz:is_current
mz:hierarchy_label

mz:is_current, mz:is_funky, and mz:hierarchy_label are the only items in that list the editor has fields for, and they will now (as of 7e3aa2b22ad5bf19791894ca0dfb701885ee6a5c) check that the value is an integer -1, 0, or 1.

Working for me, see https://github.com/whosonfirst-data/whosonfirst-data-admin-us/pull/40/files.

:tada:


Added gold icon.

Please accept my pull request. i use your icons in my project. but need gold icon also. I can add .cdr vector file also, so anyone can create another marker.

thanks


Improve support for UIViewController's layout guides

Maybe I'm missing something, but it seems to be impossible to constrain to the top of the bottomLayoutGuide.
One possible solution to this problem would be to expose a constructor for ConstraintItem for UILayoutSupport

@aleffert you should be able to do:
make.top.equalTo(viewController.topLayoutGuide)

@robertjpayne I'm confused. The top of the topLayoutGuide is at the top of the screen, the top of the bottomLayoutGuide is at the top of the toolbar or tab bar.

So, as best I can tell, if you do make.bottom.equalTo(viewController.bottomLayoutGuide) it tries to anchor it to the bottom of the bottomLayoutGuide, which is at the bottom of the screen, not the top of the toolbar, which is what I need.

@aleffert Not sure I follow the specifics, but the support for the layout guides is there in SnapKit you may just need to play around with what you're pinning to what?
Or are you trying to pin a layout guide to something else?

I'm trying to pin a UILayoutSupport to a UIView. In particular, in the attached image, I am trying to anchor the bottom of the red view to bottomLayoutGuide.top. SnapKit, as far as I can tell, does not let me specify an attribute for instances of UILayoutSupport, only UIView. So it only lets me anchor the bottom of the view to the bottom of the UILayoutSupport. I can make this work by casting the UILayoutSupport to a UIView and then using snp_top on the layout guide, but that seems like an implementation detail I'd rather not depend on.

See what you're saying, really what you want is to be able to do something like:
make.top.equalTo(viewController.bottomLayoutGuide.snp_bottom)

Unfortunately this is going to be really difficult because you can't provide extensions to protocols. Have you potentially tried using the iOS 8.0 layout margins instead of the layout guides? I believe they are more robust and are supported by SnapKit.

Unfortunately, I still need to support iOS 7.
One possible solution would be to add functions like snap_top : UILayoutSupport -> ConstraintItem. It's slightly different syntactically, but seems pretty straightforward.
A simpler solution would be to make the ConstraintItem constructor public or, to be a bit more type safe, add a UILayoutSupport specific one.
-Akiva Leffert

On May 15, 2015, at 6:15 PM, Robert Payne<EMAIL_ADDRESS>wrote:
See what you're saying, really what you want is to be able to do something like:
make.top.equalTo(viewController.bottomLayoutGuide.snp_bottom)
Unfortunately this is going to be really difficult because you can't provide extensions to protocols. Have you potentially tried using the iOS 8.0 layout margins instead of the layout guides? I believe they are more robust and are supported by SnapKit.
—
Reply to this email directly or view it on GitHub.

Hmm it'd probably make most sense to add:
snp_topLayoutGuide
snp_bottomLayoutGuide

To UIViewControllers as an extension, these two properties would return a struct that then returns properly configured ConstraintItems.
For now use your UIView dynamic cast, I have a feeling these layout guides are going to be deprecated but if they remain in iOS 9 I'll build support for this into SnapKit.

+1 It would be great to have:
snp_topLayoutGuide
snp_bottomLayoutGuide

Casting to UIView is not a very elegant solution.

Release with v0.12.0:
make.top.equalTo(viewController.snp_topLayoutGuideTop)
make.top.equalTo(viewController.snp_topLayoutGuideBottom)
make.top.equalTo(viewController.snp_bottomLayoutGuideTop)
make.top.equalTo(viewController.snp_bottomLayoutGuideBottom)

How is this called after the Swift 3 migration? Couldn't find it in the migration guide.

Alignment to bottomLayoutGuide top with inset not working.


Custom card with tags

How can we use tags with custom cards?

v1.23.0 should address this.
See example here: https://rcdexta.github.io/react-trello/?selectedKind=React Trello&selectedStory=Card and Lane Styling&full=0&down=0&left=1&panelRight=0


Prettier on save output is different from running format:write for tailwind classes

I only tried for MDX files but the title says everything. This is for this repo itself not the component.

Hi,
I've noticed that Prettier and VSCode behave differently with MDX formatted files.
Fixes #55. Could you test this PR? I believe this will resolve the issue.

I've noticed that Prettier and VSCode behave differently with MDX formatted files.

Hi. I found an issue confirming this.
Running pnpm format gave me a different output for both mdx and jsx files. I figured out that eslint tailwind plugin has different sorting preferences than the prettier plugin. So lint --fix was reordering classes that prettier was already fixing with format in a different way. Turning off the class order rule fixed the issue for jsx files.
mdx still gives a different output on save. Not sure what we can do about it.
I'll make a PR to this branch with my results.


Making spacy parser skip certain words and not assign POS tag to them

How can I ensure that spacy parser skips certain words like meta info like  tags in a sentence :
I have not arranged anything else at present she has another <time> meeting tomorrow

For the above spacy assigns NOUN for  which is wrong as its just a meta tag.

Even if I can add another placeholder say like a special character instead of  it would be OK


How to represent mart data? Kimball dimensional modeling or other?

As pointed out by @willbryant , the current dim and fct mart models don't provide much value in being separated as they each are unique on the same key.
Ex: dim_ga4__sessions and fct_ga4__sessions are unique on session_key and could be joined together without issue.
It may make sense to have a single ga4__sessions model, but I know this is a debate with a lot of facets so it seems worth researching first.
My opinion:
I like the idea of: dim models where there is 1 record for each entity and fct models that contain low-grain events that can be aggregated against the entity. I think our mistake was in pre-aggregating the fct models so now they are entity-grain rather than the grain of the facts themselves.

I agree with this. In fact, this is what I did with the fork that I have deployed on my client with high-volume sites. Separating sessions into fct and dim models adds to the effort needed to create reports and it makes the data less accessible.
I also think that we should include fct_ga4__event_page_view and possibly a fct_ga4__event_scroll model by default because these are the two events that are used to build other models. This would provide package users an example of how we expect them to use the package. It would also make building session and user models more efficient (I know I have been asked to demonstrate this in issue #153 and haven't yet done so, but it does make building those models more efficient and I will demonstrate it when I have the time).
I also think we should discuss the fct_ga4__pages model.  With the high-volume client, who is starting to ramp up the use of the production tables, I switched out the fct_ga4__pages model for a agg_ga4__page_location. I've seen others use agg as a prefix and I've been using it to indicate models that aren't intended to be joined. I have aggregate tables for a number of different dimensions like page_location as well as an agg_ga4__daily table (which is another model that I think we should consider making default) and naming the model after the dimension that it segments on makes it consistent with other single-dimension aggregate models like author (which is obviously custom).
Having agg models isn't strictly Kimballian (?), but storage was expensive when Kimball developed his modeling guidelines. We might want to ask the various communities to hear what others are doing in this respect. Before deploying agg models, reports for the high volume client, who gets 1-3 million events a day, were taking about 40 seconds to load. Now, no one remarks on the report load speed.

Yeah. The other aspect is that BigQuery doesn't index like a Kimball-era database would, so having normalized models doesn't pay off in the same way.

Here's something like what I envision the sessions and users models looking like.

Green represents partitioned tables while yellow represents views.
The idea here is to minimize lookups that hit the base_ga4__events table in favor of fct_ga4__events_page_view and a sessions table that I called here int_ga4__sessions.
I'm not sure if dim_ga4__sessions needs to be a partitioned or if a view will suffice. If it's a view, then it would probably be best to partition all of its parents.
I'd also welcome a discussion on whether we need both the first_last_events and first_last_pageviews models. I've noticed some problems with session attribution in sessions with just sessions_start events because we filter them in stg_ga4__sessions_traffic_sources. These sorts of issues will get worse if we decide to do away with first_last_events and just use first_last_pageviews built later and more efficiently. Maybe that tradeoff is worth it.
For last_non_direct attribution, I'm planning on introducing a lookback_window variable to let people choose how many partitions to check before defaulting to Direct attribution.
If we were to introduce a lookback_window then we could also use it in the users tables. One pattern I've seen in Google Ad Manager exports, for example, is that GAM populates daily partitions with all of the relevant data for that day so, for example, the companies table includes all of the companies that bid on that day and repeating that data on the previous day. If we were to do that with the users table and a lookback window, then the user entry for that day would calculate metrics only using data in the lookback window. The cookie-driven traffic_source would remain the same but it would be the only data point outside the lookback window.
The lookback window would also be good for user stitching between device_key and user_id.
I personally like the idea of having a lookback window setting as it makes me a lot more comfortable with looking up past data which gets expensive quickly on large sites and most of the relevant data is usually in the last few days.
We also might want to leave the lifetime user tables in the package as well and let the people deploying the package decide whether they care more about the efficiency of a lookback window versus having perfect user data.

Just discovered this package, it does a lot of things very well, but 100% the separation of dim_ga4__sessions and fct_ga4__sessions makes no sense to me.
It's also worth pointing out that most companies have been around much longer than they've been using GA 4.  So the company's fact_sessions table is probably fed into by a table full of GA 4 sessions AND a table full of Universal Analytics sessions, and maybe they have Mixpanel or Snowplow or Amplitude sessions as well.  Only the final sessions table is a real fact table.  So I don't think that a sessions table that only has GA 4 sessions needs a fct prefix at all... your GA 4 sessions table is a building block towards a fact table.

Fivetran's packages are probably the most used outside of dbt_utils, and they don't call their shopify orders table fct_orders, but just shopify__orders.  A company might have the shopify_orders table join with a stripe_orders table to create their fct_orders.  It makes sense to me to use the same approach here.


Latest azurestorage explorer doesnot open when icon is clicked after install in win7

Storage Explorer Version:
Platform/OS Version:
Architecture:
Regression From:
Steps to Reproduce:

Expected Experience:

Actual Experience:

Closing due to lack of response. Please open a new issue if you are still having problems.


[Usage]: How to invoke all the tests in vLLM

Your current environment
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: Could not collect
CMake version: version 3.30.0
Libc version: glibc-2.31

Python version: 3.10.14 (main, Apr  6 2024, 18:45:05) [GCC 9.4.0] (64-bit runtime)
Python platform: Linux-6.2.0-26-generic-x86_64-with-glibc2.31
Is CUDA available: True
CUDA runtime version: 12.1.66
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA A100-SXM4-80GB
GPU 1: NVIDIA A100-SXM4-80GB
GPU 2: NVIDIA A100-SXM4-80GB
GPU 3: NVIDIA A100-SXM4-80GB

Nvidia driver version: 525.125.06
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.9.0
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.9.0
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.9.0
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.9.0
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.9.0
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.9.0
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.9.0
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   48 bits physical, 48 bits virtual
CPU(s):                          128
On-line CPU(s) list:             0-127
Thread(s) per core:              2
Core(s) per socket:              32
Socket(s):                       2
NUMA node(s):                    8
Vendor ID:                       AuthenticAMD
CPU family:                      25
Model:                           1
Model name:                      AMD EPYC 7543 32-Core Processor
Stepping:                        1
CPU MHz:                         2794.773
BogoMIPS:                        5589.54
Virtualization:                  AMD-V
L1d cache:                       2 MiB
L1i cache:                       2 MiB
L2 cache:                        32 MiB
L3 cache:                        512 MiB
NUMA node0 CPU(s):               0-7,64-71
NUMA node1 CPU(s):               8-15,72-79
NUMA node2 CPU(s):               16-23,80-87
NUMA node3 CPU(s):               24-31,88-95
NUMA node4 CPU(s):               32-39,96-103
NUMA node5 CPU(s):               40-47,104-111
NUMA node6 CPU(s):               48-55,112-119
NUMA node7 CPU(s):               56-63,120-127
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Mmio stale data:   Not affected
Vulnerability Retbleed:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP always-on, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 invpcid_single hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd amd_ppin brs arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold v_vmsave_vmload vgif v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca fsrm
Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] torch==2.3.0
[pip3] torchvision==0.18.0
[pip3] transformers==4.42.3
[pip3] triton==2.3.0
[conda] Could not collect
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.5.0.post1
vLLM Build Flags:
CUDA Archs: 5.2 6.0 6.1 7.0 7.5 8.0 8.6 9.0+PTX; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    GPU1    GPU2    GPU3    NIC0    NIC1    CPU Affinity    NUMA Affinity
GPU0     X      NV12    NV12    NV12    SYS     SYS     24-31,88-95     3
GPU1    NV12     X      NV12    NV12    SYS     SYS     24-31,88-95     3
GPU2    NV12    NV12     X      NV12    PXB     PXB     8-15,72-79      1
GPU3    NV12    NV12    NV12     X      SYS     SYS     56-63,120-127   7
NIC0    SYS     SYS     PXB     SYS      X      PIX
NIC1    SYS     SYS     PXB     SYS     PIX      X

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

NIC Legend:

  NIC0: mlx5_0
  NIC1: mlx5_1

How would you like to use vllm
This question might be a bit dumb but I wonder how I could install and invoke all the tests in one go for vLLM. I looked for the instructions from the documentation but did not find any. Maybe I missed it. Is there anyone who could give some suggestions about the test framework? Thanks a lot

see https://github.com/vllm-project/vllm/blob/main/.buildkite/test-pipeline.yaml

Thanks let me check it out


Add color-hunt extension

Description

Color Palettes for Designers and Artists
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@pernielsentikaer Thanks for the review.

I woud remove the command Clear Cache and just built it into Search Palettes instead

That sounds good, but I prefer to keep this command for myself, and the search page had lots of actions, so I chose to keep it

I would remove the command Favorite Palettes into Seach Palettes in a new secion in top

Good idea, and I implement it on the latest commit

Can we set it disabledByDefault then, I don't think most of the users knows what it is, and is there a reason why we need to do that in the first place?

LOL, it's just my OCD needs a place to know how many files have been downloaded and the cache size.

@pernielsentikaer Thanks to the review, this problem has been fixed

Should we consider to only have one action for pin/unpin like rest of Raycast? We also have a default shortcut for that in Keyboard.Shortcut.Common.Pin

Good idea and it seems a bug exists, I will fix it ASAP

Previously, every fetch required updating the 'clear' subcommand subtitle, causing significant performance lag due to counting the local files. Therefore, I have removed it and added a new index action.

Should we remove favorites from the normal list, I think it would make sense?

done

Do you mean this?

👌 it has been reverted


brave: 0.56.15 -> 0.57.18

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/brave/versions.
meta.description for brave is: '"Privacy-oriented browser for Desktop and Laptop computers"'.

Checks done (click to expand)

built on NixOS
Warning: no invocation of /nix/store/snq1m3x769ma3blyqvf1ms1lxmlm3wgk-brave-0.57.18/bin/.brave-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/snq1m3x769ma3blyqvf1ms1lxmlm3wgk-brave-0.57.18/bin/brave had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 0.57.18 with grep in /nix/store/snq1m3x769ma3blyqvf1ms1lxmlm3wgk-brave-0.57.18
directory tree listing: https://gist.github.com/c729651e6798e262714ce92cd5985b7d
du listing: https://gist.github.com/994a42d87b83f0c358dee9c81c922d94

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

1 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
brave

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/snq1m3x769ma3blyqvf1ms1lxmlm3wgk-brave-0.57.18 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A brave https://github.com/r-ryantm/nixpkgs/archive/0ee9493e6c9cfb69f3cd0eb7e1798813fb8f5eb2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/snq1m3x769ma3blyqvf1ms1lxmlm3wgk-brave-0.57.18
ls -la /nix/store/snq1m3x769ma3blyqvf1ms1lxmlm3wgk-brave-0.57.18/bin

cc @uskudnik for testing.

From the release note at https://github.com/brave/brave-browser/releases/tag/v0.57.18, it seems to be based on 71.0.3578.80, and so the gtk2 dependency can be dropped.

They actually moved from being based on Muon to Chromium this release.
See: https://brave.com/brave-upgrades

I had to delete ~/.config/BraveSoftware in order execute without a segmentation fault.
I'd like to see if someone who was using this already could reproduce that.

@worldofpeace that announcement post sounds misleading since earlier they had said the same thing on 0.55 https://brave.com/new-brave-browser-release-available-for-general-download/.

Guess they want to keep showing it off :smile:

(digress) aside from the perf improvement relative to vanilla chrome/chromium, I suppose it would be informative to see how Brave fares with chrome/chromium + uBO: https://github.com/gorhill/uBlock/issues/1279.

I was able to run it without segfault, and didn't have to clear the config.

I was able to run it without segfault, and didn't have to clear the config.

In that case I will merge this :sparkle:


IOS - Publishing App fails when package included

The app deploys fine in debug or release to devices from VS2022, but when publishing the app for IOS the IDE shows that the packaging has completed but the progress bar keeps going forever (just tried it over night).  The packaging works fine for Android.  When I look at the archives folder I find that there is an archive there with most of the files there.  In VS 2022 after restarting when I "view archives" no archives appear (I believe VS is throwing an exception).  Deleting the folder for the new archive and restarting VS2022 allows it to return to normal.
The only clue is looking in the Xamarin logs where I see this:
Xamarin.Messaging.Ssh.MessagingService Information: 0 : Agent Build 16.4.7089 is running: 08/08/2023 03:54:18Z
    DateTime=2023-08-08T03:54:18.2976305Z: 08/08/2023 03:54:18Z
Xamarin.VisualStudio.Progress.ProgressReportService Information: 0 : App archive 'Board Game Copilot' completed successfully.: 08/08/2023 03:55:30Z
    DateTime=2023-08-08T03:55:30.7816782Z: 08/08/2023 03:55:30Z
Xamarin.VisualStudio.Progress.ProgressReportService Information: 0 : !App archive 'Board Game Copilot' completed successfully.: 08/08/2023 03:55:30Z
    DateTime=2023-08-08T03:55:30.7816782Z: 08/08/2023 03:55:30Z
Xamarin.VisualStudio.Publishing.Presentation.ViewModels.ArchiveListViewModel Error: 0 : System.IO.FileNotFoundException: Could not find file 'C:\Users\camer\AppData\Local\Xamarin\iOS\Archives\2023-08-07\Board Game Copilot 8-07-23 10.55 PM.xcarchive\Products\Applications\Board Game Copilot.app\Frameworks\RevenueCat.framework\Modules\RevenueCat.swiftmodule\x86_64-apple-ios-simulator.private.swiftinterface'.
File name: 'C:\Users\camer\AppData\Local\Xamarin\iOS\Archives\2023-08-07\Board Game Copilot 8-07-23 10.55 PM.xcarchive\Products\Applications\Board Game Copilot.app\Frameworks\RevenueCat.framework\Modules\RevenueCat.swiftmodule\x86_64-apple-ios-simulator.private.swiftinterface'
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileInfo.get_Length()
   at Xamarin.VisualStudio.IOS.Publishing.IOSProjectArchive.get_Size() in D:\a\_work\1\s\src\Core\VisualStudio.IOS\ProjectSystem\Publishing\IOSProjectArchive.cs:line 233
   at Xamarin.VisualStudio.Publishing.Presentation.ViewModels.BuildViewModel.SetModel(IProjectArchive model) in D:\a\_work\1\s\src\Core\VisualStudio.Publishing\Presentation\ViewModels\BuildViewModel.cs:line 298
   at Xamarin.VisualStudio.Publishing.Presentation.ViewModels.BuildViewModel..ctor(ArchiveViewModel archiveViewModel, IProjectArchive model, IArchiveManager archiveManager, JoinableTaskFactory asyncManager, IEventStream eventStream, IProgressReportService progressReportService) in D:\a\_work\1\s\src\Core\VisualStudio.Publishing\Presentation\ViewModels\BuildViewModel.cs:line 123
   at Xamarin.VisualStudio.Publishing.Presentation.ViewModels.ArchiveListViewModel.<OnNewBuildCompletedAsync>d__60.MoveNext() in D:\a\_work\1\s\src\Core\VisualStudio.Publishing\Presentation\ViewModels\ArchiveListViewModel.cs:line 0
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Xamarin.VisualStudio.Publishing.Presentation.ViewModels.ArchiveListViewModel.<>c__DisplayClass59_3.<<SubscribeToEvents>b__10>d.MoveNext() in D:\a\_work\1\s\src\Core\VisualStudio.Publishing\Presentation\ViewModels\ArchiveListViewModel.cs:line 315: 08/08/2023 03:55:30Z
    DateTime=2023-08-08T03:55:30.8121999Z: 08/08/2023 03:55:30Z

Getting Publish to work again after removing the package was pretty hard.  I had to shut down visual studio, delete all obj and bin folders by hand, then do a clean and rebuild before publish would work again.  After doing this I can verify that removing this package allowed the app to publish again.

I was able to get back to this problem today.  The issue is that the file path is getting too long.  After a bunch of research I figured out that the maximum length for the win32 API call (yes really) called during the build process is 260 characters, in the chunk I shared that was up to 263 characters.  I moved the Archives folder (in VS2022 options) to a shorter folder length and it worked just fine.
I'm not sure I have a great answer on what could change in this code base to fix this...  But at least this is an answer for the next person, this was pretty baffling...

I did start setting up pipelines, but ran into so many MAUI problems that I gave up, I'll have to give it another try. I tried to  track through that issue, but couldn't follow all the related issues, did they actually fix it in .net8?

MAUI problems ? I didnt experience anything other than problems regarding iOS certificates (it took me a while to set it up properly).
Regarding that issue, I have no idea, it went through so many other issues I also lost track of that.

@CameronVetter can I close this issue ? Because it is caused by MAUI itself so we cant do anything with this


[11.x] Applying value Function into the $default value of transform helper

The $default value of the transform function does not pass through the value to allow the execution of a closure to obtain the default value, for example. This PR fixes this by passing $default through the value helper.

Would this be considered a breaking change?

Would this be considered a breaking change?

I strongly believe not, since both value and transform set $default in the same way.

Only if someone is expecting the $default to be a callable, then instead of getting it, they would get the result of its execution.
Which, IMO, is highly unlikeable.

@taylorotwell actually this is unneeded, re-reading my comment, I fell I oversaw it. The transform helper already checks if the $default is a callable, and if so calls it with the $value as a parameter:
https://github.com/laravel/framework/blob/81a0b5b60ff83d7a47177675741c41c1dfe78967/src/Illuminate/Support/helpers.php#L468-L479
The line modified in this PR only adds a function call to the stack call, as $default never be a callable at this point:
// $default is never a callable here
return value($default);

Other than the useless function call, there is no harm in keeping it, so I didn't send a PR to revert it.

@taylorotwell actually this is unneeded, re-reading my comment, I fell I oversaw it. The transform helper already checks if the $default is a callable, and if so calls it with the $value as a parameter:
https://github.com/laravel/framework/blob/81a0b5b60ff83d7a47177675741c41c1dfe78967/src/Illuminate/Support/helpers.php#L468-L479
The line modified in this PR only adds a function call to the stack call, as $default never be a callable at this point:
// $default is never a callable here
return value($default);

Other than the useless function call, there is no harm in keeping it, so I didn't send a PR to revert it.

We're not just talking about callables.

Just to be clear, you did check the value() implementation, right?
https://github.com/laravel/framework/blob/81a0b5b60ff83d7a47177675741c41c1dfe78967/src/Illuminate/Collections/helpers.php#L234-L237
If the $value argument isn't a \Closure, this helper just returns the $value variable.
As the if clause just before the modified line excludes the possibility of $value being a callable, the line modified in this PR adds no value, and worst, just adds a function call.

We're not just talking about callables.

Now you let me curious, I guess we mutually agree that in the modified line, $value will never be a callable, and thus never be a \Closure, which excludes the \Closure path from the value() ternary implementation, right?
So, what are you talking about, then?


[turborepo] prune --docker principle breaks with workspace internal packages dependencies

What version of Turborepo are you using?
1.6.3
What package manager are you using / does the bug impact?
Yarn v2/v3 (node_modules linker only)
What operating system are you using?
Linux
Describe the Bug
Let's say we have the following file structure in a monorepo with yarn workspaces
shared/
  pkg1/
    ...
    package.json
services/
  service1/
    ...
    package.json

package.json
yarn.lock

If services/service1 require shared/pkg1, when using a dockerfile like:
FROM node:18-alpine as source
# ...
WORKDIR /source
COPY . .
RUN yarn turbo prune --scope=service1 --docker

FROM node:18-alpine as runner
COPY --from=source /source/out/yarn.lock .
COPY --from=source /source/out/json .
RUN yarn
COPY --from=source /source/out/full .
# ...

It breaks because yarn will try resolve internal package shared/pkg1 as stated in services/service1/package.json and in yarn.lock.
This really defeat the purpose of this feature and especially the --docker flag because to leverage the docker layer caching in order to avoid re-running RUN yarn, we need to only copy the json folder first, but then RUN yarn will fail because internal package are not present.
This is a pretty common use case in a monorepo.
Expected Behavior
Being able to run yarn properly without loosing ability to leverage docker layer caching
To Reproduce
Data to reproduce are already in the Describe the bug section
Reproduction Repo
No response

Weel, it turns out that it was only caused by the fact that an incorrect version of yarn was running inside my docker container and didn't recognize my workspace configuration correctly. Copying .yarn and .yarnrc.yml over to the json folder fixed it.
Sorry for the noise, and I'm gonna take a nap for my brain to recover now.. :brain:

Glad you got it figured out!


C++ Exception Translation to Lua

It would be desirable to catch exceptions on the lua side via pcall. I did a quick research for my own wrappers (torch-pcl and torch-moveit) and found out that proper error translation is harder than expected.
The best option might be to register a central LuaJIT C-call wrapper (LUAJIT_MODE_WRAPCFUNC, see also  LuaJIT C++ Exception Interoperability). Unfortunately this API does not allow to chain handlers easily. Therefore I would like to ask you regarding your exception handling plans in torch-opencv and whether we should build a common system that would allow to handle exception translations with multiple libraries loaded at the same time?
A more general question is if LuaJIT will stay the lua interpreter of choice for Torch. Since guru @MikePall resigned mid 2015 as the main LuaJIT core-developer the future is a bit unclear here.
The official Error Handling with C API recommendation for the classic Lua C-API is to use setjmp/longjmp. But things become complicated if this is mixed with C++ objects instead of real exceptions (objects are not correctly destoyed). Compilers seem to differ how they handle things here, e.g. see the MSVC note on setjmp.
A very cumbersome way would be to more or less 'automatically' add try-catch blocks around all library calls - I would avoid this if there are any other options.

At least standard Lua seems to be compiled as C++  since 5.1, see http://lua-users.org/wiki/BuildingLua which says:
"By default if lua 5.1 or later is compiled as C++, it will use C++ exceptions to unwind the stack rather than longjmp/setjmp, though this is configurable (at compile time). See luaconf.h near LUAI_THROW/LUAI_TRY for a discussion of this. "
The comment in luaconf.h:
/*
@@ LUAI_THROW/LUAI_TRY define how Lua does exception handling.
** CHANGE them if you prefer to use longjmp/setjmp even with C++
** or if want/don't to use _longjmp/_setjmp instead of regular
** longjmp/setjmp. By default, Lua handles errors with exceptions when
** compiling as C++ code, with _longjmp/_setjmp when asked to use them,
** and with longjmp/setjmp otherwise.
*/

@andreaskoepf maybe you want to take a look at https://github.com/facebook/fbtorch , especially https://github.com/facebook/fbtorch/blob/master/Exceptions.cpp

@soumith Thanks for pointing us to the related fb work! I asked myself whether it would make sense to add an extensible/pluggable C++ exception translator to https://github.com/torch/torch7. I know torch officially is C99 - but being able to make C++ libraries accessible is an important too. Maybe we could create a single tiny C++ library that exports some extern "c" functions to manage the exception translation 'hook'-chain.


Add support for format on save + add documentation for elm-format

I added support for format on save per this request #46 and also added some documentation for elm-format.

@sbrink any feedback on this PR? I believe this PR will also make this extension closer to being "elm-format approved" plugin.
Also, I'm planning to deprecate my elm-format extensions once this PR is merged.

Thanks a lot! :)

Any chance you can publish this to the marketplace? I don't see v0.7.0 in marketplace yet.


Cursor often does not appear after command finished

Repro:
echo "asdf" > blah

After pressing enter, the command is finished, but the cursor does not appear again. It only appears again after pressing a key, e.g. arrow-up

Seems to also happen for other commands that do not include ".

I think it's a bug.


Merge Nehemiah's mods?

Original issue #5557
After more thinking and also requesting information from the users, as well as checking the download stats, it seems that having split these mods apart is far more bother than worth.
Download Info:

KEES_0.3_beta_2.zip (1.70 MiB) - downloaded 68 times. Last updated on 2017-07-27
KeminiResearch_0.2_beta_2.zip (0.87 MiB) - downloaded 43 times. Last updated on 2017-07-27
KerbalLifeScience_0.2_beta_2.zip (3.90 MiB) - downloaded 43 times. Last updated on 2017-07-27
NehemiahIncSciencePack_0.2_beta_2.zip (14.03 MiB) - downloaded 4,434 times. Last updated on 2017-07-27
OrbitalMaterialScience_0.7_beta_2.zip (11.18 MiB) - downloaded 50 times. Last updated on 2017-07-27

As such, I'm wondering whether it's possible to replace the various mods with one new one "Nehemiah Engineering Orbital Science" (NEOS).  I would remove the version files from all the sub-directories.
Thoughts?
If we go ahead with this change, we'd need to:

Mark the old mods as deprecated or replaced-by or something.
Mark the new mod as conflicting with the old mods

I'm presuming that's possible?

This was done in #6071.


Dummy commit to test CI - do not merge

@petedyerarm @prakharbhatt007 Parsec checker fails in this dummy PR as well. Master seems to be broken now.

@petedyerarm This seems like a build environment change. Still see the issue in #69, which reverts latest changes from @prakharbhatt007.


Configuration Loop after iPhone get restored

When an iPhone get restored from an older Backup the corona-warn-app loops at the configuration and will not get to the normal App screen.
Work-A-Round is to delete the App and loose the whole progression.

Please follow up in #754

Hello @MacVille,
thanks for sharing the bug. There is already an ongoing discussion about that in the thread @Ein-Tim mentioned.
@Ein-Tim thanks for your support.
To run the app after your restore process has been finished, please do reinstall the app, as suggested here: https://github.com/corona-warn-app/cwa-app-ios/issues/754#issuecomment-666304765
Thanks,
LMM
Corona-Warn-App Open Source Team


Support Solaris version 11

Get correct values for:
CPU, memory, filesystems, openfiles
Arch:

sparc-32
sparc-64
x86
x64

Nobody is developing SIGAR anymore.  You might wish to search for other alternatives which provide the functionality you request.

thanks


gradle; gvrf-physics; support for the 64bit build

Minor patch after https://github.com/Samsung/GearVRf/pull/1756 was merged. The diff from #1756 was applied and the line endings converted to unix-style.
GearVRf-DCO-1.0-Signed-off-by: Mihail Marinov<EMAIL_ADDRESS>

https://github.com/Samsung/GearVRf/pull/1774/files?w=1 to see the actual diff.


Set invalid proposal in opt function

In some functions, e.g. f = 1/(x+y), there may be some complex variable interaction that is easy to confirm at runtime, which makes the optimization function undefined - e.g. x=-y in the above example.
It would be beneficial to mark the current variable setting as undefined and avoid evaluating it, without influencing the optimization. Right now we can detect those spaces and return +/- np.inf, but this creates an artificial value, which in e.g. BO should impact further optimization (correct me if I am wrong). The alternative option of pre-computing those cases and filtering them out of the search in the first place may not be always tractable with extra-large search spaces.
One option would be to return a value like None that doesn't carry underlying meaning.
Example Code:
from gradient_free_optimizers import RandomSearchOptimizer
def f_function(para):
    # if (para["x"] + para["y"]) == 0:
    #     return None

    loss = 1 / (para["x"] + para["y"])
    return -loss

search_space = {"x": range(-1, 1), "y": range(-1, 1)}

opt = RandomSearchOptimizer(search_space)
opt.search(f_function, n_iter=10)

Hello @23pointsNorth,
if you want to return a value that shows, that the parameters result in an invalid score you could return np.nan.
GFO can handle np.nan (and np.inf) since version 0.2.11.
Does this solve your problem?

but this creates an artificial value, which in e.g. BO should impact further optimization

Bayesian optimization (and all other smbo) filter out np.inf and np.nan from the score-tracking-decorator:
https://github.com/SimonBlanke/Gradient-Free-Optimizers/blob/e7a95503195ea7c0b3590241caf499ea307085f2/gradient_free_optimizers/optimizers/smb_opt/smbo.py#L73-L82

if you want to return a value that shows, that the parameters result in an invalid score you could return np.nan.

That's great, I guess that's the one thing I hadn't checked.
From my small test, np.nan is handled ok (aka ignored) in all of the optimizers similar to the code you've linked to in smbo?

Hello @23pointsNorth,
The code I have linked only works in smbo, but other optimization algorithms have a similar way of ignoring np.nan and np.inf if it is needed.


Add visible notification (or logging) when importing existing projects

What problem does this feature solve?
Run vue ui and import a project - there is no visible way of knowing that your project is importing (so you end up with lots of duplications after you keep pressing import)
The end user experience would be a notification that the project is loading and/or logging on the console to alert the user what is happening.
What does the proposed API look like?
I propose changing the 'import a project' button to a disabled 'importing...' button in the current folder (so you can import others while it is happening). Logging would be nice too...
Open to suggestions though!

You may have tried importing a project which didn't have the node_modules installed. Make sure to run npm install or yarn in it before importing (this will be done for you in a future release).


ENUM requests

Hi,
can you please convert the following into ENUM:

Table 77 "Report Selections" - field "Usage"
Table 179 "Reversal Entry" - field "Entry Type"

Probably superfluously, but just something that should be taken into consideration regarding item 1:
Table 9657 "Custom Report Selection" - field 3 "Usage" seems to use the same Option string as T77 (and therefore should probably use the same enum).

I cannot find any of these new events listed above in the Spring 2019 release? When will they be shipped?
Could we have any example of how to use those event to extend Usage-option with more choice for "Report Selections".

Hi,
Indeed the changes didn't make it for the Spring 2019 release as we discovered unexpected challenges that require more work, because of the way Options are handled in the BaseApp code (see GetNumberOfOptions in Codeunit 10 for instance).
The way to fix it requires some additional features from the platform. Hopefully this will be released in the Fall release, but that depends on the prioritization of our total backlog.
To be clear, the events are not used to extend the usage option. For this, you can refer to https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-extensible-enums and in particular the use of "enumextension".
The events mentionned above are here to help you support all cases where the option is used and where you may want to do the appropriate handling for your new option value.
Most of the events follow the same pattern: subscribe to them and do the appropriate handling for your new extended option value. Here is some kind of pseudocode example:
[Subscriber to one of the events]
LOCAL PROCEDURE OnSomeEvent(VAR SomeVarParamResult : SomeType;SomeOtherUsefulParams: SomeTypes;ReportUsage : Option;VAR Handled: Boolean);
BEGIN
  IF ReportUsage = ReportUsage::MyNewOptionValue THEN BEGIN
    SomeVarParamResult := SomeSpecificHandlingForMyNewOptionValue(SomeOtherUsefulParams);
    Handled := TRUE; // Handled pattern
  END;
END;

@DavidBastide Why is this issue 'Closed' when no solution has been delivered? Waiting untill AFTER the next fall release will delay us even more in moving our code to AL before fall...
We're especially awaiting for the OnBeforeGetPurchDocTypeUsage event in COD229 since we'd like to print purchase invoices / creditmemo via the report selections (~ vendor self-billing in DK)
LOCAL GetPurchDocTypeUsage(PurchHeader : Record "Purchase Header") : Integer
CASE PurchHeader."Document Type" OF
  PurchHeader."Document Type"::Quote:
    EXIT(ReportSelections.Usage::"P.Quote");
  PurchHeader."Document Type"::"Blanket Order":
    EXIT(ReportSelections.Usage::"P.Blanket");
  PurchHeader."Document Type"::Order:
    EXIT(ReportSelections.Usage::"P.Order");
  PurchHeader."Document Type"::"Return Order":
    EXIT(ReportSelections.Usage::"P.Return");
  // NVT-BEGIN: Event requested
  PurchHeader."Document Type"::Invoice:
    EXIT(1000); // Use fictive number in order to avoid errors
  PurchHeader."Document Type"::"Credit Memo":
    EXIT(1001); // Use fictive number in order to avoid errors
  // NVT-END
  ELSE
    ERROR('');
END;

Sorry about the confusion. The issue shouldn't yet have been closed. I seems it was closed by a user and we failed to catch that. Unfortunately we had to abort check-in due to the aforementioned issues. We are working hard to pave the way for our first option to enum conversion, but it has proven itself more tricky (and much more time consuming) than initially anticipated. We're hoping to have a resolution soon, after which we will begin to process the many enum conversion requests registered here on GitHub.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Travis fails on coverage all the time

https://travis-ci.org/AnalyticalGraphicsInc/cesium/builds/598346523?utm_source=github_status&utm_medium=notification
I've been seeing this error very frequently lately.  @mramato?

This is just Firefox being slow, we can up the timeouts to fix it.  I'll open a PR


[FEATURE] LNDHub and/or LNBits integration + Like & Repost Auto-ZAPs right from Amethyst

Is your feature request related to a problem? Please describe.
Let's say I like to send zaps. But to put a Like, make a Repost (Ok - Renotes ;-) and then send a zap, while you still need to open an external wallet (sometimes wait for connection to nodes), then time is spent on sending a zap, then you need to exit the wallet and return back to the feed. At the same time, there are a lot of problems here - different wallets have a different exit back to Amethyst (Zeus opens directly in Amethyst and you need to make a total of 4 clicks to return. There are fewer clicks in the SBW wallet, it opens as an independent application, but you have to wait for connections to nodes). In general, it takes a huge amount of time to make one zap. At the same time, a zoo of applications is obtained if the user has several wallets.
Describe the solution you'd like
In Amethyst, you can build work with a lightweight third-party API, such as LndHub and LNBits. The user can use custodial wallets for zaps (LndHub servers or LNBits Demo site for example), or their own solutions (The plugin LNBank of BTCPay brings the LndHub API and user can install own LNBits server).  At the same time, it is proposed to build the interface in such a way that it is convenient:

Since Amethyst is now a multi-account, it is necessary that at the level of each account you can configure your LndHub URI or LNBits URI in the settings (preferably, in addition to the text field, it is possible to scan the QR code with the URI). For example, a separate item in the left panel, like "Security Filters". I think that it is necessary to separate the "wallets" for outgoing payments, since a user can have a personal wallet for a personal account, and, for example, a second one for a working (corporate) one.
Provide the user with the opportunity to specify separately for Like and Repost the amount in sats, which will be sent automatically if he clicked Like or Repost (Auto-ZAP). You can do this in the likeness of ZAP amounts - click on the icon, hold it and a field will appear to specify the default amount to the site.
In order for the user to see that the Auto-ZAP is active, place a small lightning bolt icon next to the like or repost icon. Disabling Auto-ZAP is also a long press and there is somewhere to make the disable button (for example, checkbox).
For the zaps themselves, the interface remains the same, except that when selecting the amount of sats, the Amethyst automatically has to send a ZAP itself through API, without trying to launch a third-party LN wallet.
Sending should work in a separate thread without blocking the interface.
If the recipient of the ZAPs does not have an LN address to receive, then Like and Repost are quietly processed as normal Like & Repost.
In order for the user to understand that zap has been sent, this can be shown by a yellow lightning icon next to the Like & Repost icon: gray icon - ZAP has not been sent, but default sending is set, and yellow lightning icon - ZAP has been sent. There is probably one inconvenience here - if the feed is updated, we will lose the information that we sent auto-ZAP, for example, for a Like. In this case, it will already look like a "yellow lightning" of a regular zap (as if we sent a regular zap). But I think you can put up with this :) Or immediately show auto-zap as a normal active sent zap.

Bounty (in Bitcoin sats) offered for the implementation
I am ready to pay for the implementation of this feature in the amount of 300K sats for example (as ZAP in Nostr). If it requires more time and effort, I'm even willing to increase the amount to 500K sats. I think someone will join me too ;-)
Additional context
Having read the description of LndHub now, it seems REST API too as LNBits. LndHub is very desirable, since only it of these two is supported by the BTCPay server, which is installed by many people (via the LNBanks plugin, which, among other things, allows you to divide the balance of one Lightning node between different BTCPay accounts, which makes it a good candidate for a custodial wallet solution for users who do not want to install their BTCPay).

Together with https://github.com/vitorpamplona/amethyst/issues/196 makes it a 1300 bounty :)

Custodial solutions should not be acceptable. Thankfully you could build a fully contained self-custodial LN wallet in Amethyst using Breez SDK
I know it wasn't the original request, but if a self-custodial LN wallet is integrated inside Amethyst I will donate 250k sats.
Let's start getting users to using self-custodial LN wallets instead of custodial wallets.

I'll echo @InnocuousFinch and add 250k sats if this is done non-custodially, i.e. via the Breeze SDK linked.

Custodial solutions should not be acceptable. Thankfully you could build a fully contained self-custodial LN wallet in Amethyst using Breez SDK

As far as I know, the Breez wallet has an LND + Bitcoin node inside itself. I am against it, because the user will have to install Breez or have a software copy of all this inside Amethyst. And all this for the sake of a few sats in ZAPs. I can also assume that sending ZAPs will require a connection to the nodes and synchronization with the blockchain before zap. In addition, the user will have to take care of backups (Google Drive?). If this is the F-Droid version of Amethyst, then there will be a problem with this. There will also be a problem for those who don't want to use Google Drive. And many other disadvantages.

As far as I know, the Breez wallet has an LND + Bitcoin node inside itself. I am against it, because the user will have to install Breez or have a software copy of all this inside Amethyst.

You would be incorrect. The user would not need to install anything. The Breez SDK (software development kit) is not Breez Wallet.
The Breez SDK leverages Greenlight, which is both a bitcoin and lightning node hosted for you, and allows you to add a functional, self-custodial Lightning wallet with on-chain interoperability with only a few lines of code. Additionally, the keys to sign transactions stay on the device so the user always retains custody of funds.
Breez SDK was literally built for this type of use case.

There is a NIP-46 equivalent that Alby is trying to design that could help here. Essentially, in the name of micro apps, Nostr clients talk to wallets over a standard Nostr protocol through relays. This means that each LN implementation will have to offer a module that connects to Nostr directly instead of requiring Nostr Clients to use all these different LN interfaces. That could mean a better compatibility layer and better separation between Nostr Clients and Wallet services.

All non-custodial solutions will require the user to take a responsible approach to channel reservation.

This isn't remotely true. If Amethyst used Breez SDK to integrate a LN wallet directly, it would be leveraging Greenlight so users would not need to manage channels. Greenlight is a hosted BTC/LN node so you wouldn't need the node to be on the phone.
This is all handled for you automatically on the back end by the LSP.

Greenlight is a hosted BTC/LN node so you wouldn't need the node to be on the phone.

What exactly does this mean ("Greenlight")? If this node works at the Breez company, then this is a not 100% custodial solution. Tomorrow they will shut down their server, and everyone who worked through the Breeze SDK will stop working. Let's say you can close the channels and return the funds, and then what?
If Greenlight is a software suite that everyone can install on their own server, then the options I have suggested also meet the requirements: you can configure your node on LndHub or LNBits.

It's self-custodial because the keys to spend the bitcoin remain on your device and only on your device. No need to host a node for it to be self-custodial. I've linked Breez SDK and Greenlight links in prior posts. Please do some reading before responding with more FUD about something you do not understand.
Screenshot directly from the Breez SDK website:

There is a NIP-46 equivalent that Alby is trying to design that could help here

Is there no mistake? Now I'm reading what this NIP-46 is for and there is a goal so that the application can sign anything with the Nostr key at the request of any service.

There is a NIP-46 equivalent that Alby is trying to design that could help here

Is there no mistake? Now I'm reading what this NIP-46 is for and there is a goal so that the application can sign anything with the Nostr key at the request of any service.

The idea is to use the same concept between Nostr Client and Wallet.

It's self-custodial because the keys to spend the bitcoin remain on your device and only on your device. No need to host a node for it to be self-custodial

What you have written and quoted - there is no complete understanding. You have already written so much, but you have not answered - where does the node work and whose is it?

It is hosted by Blockstream. Please read: https://blockstream.com/lightning/greenlight/

Remark: in order to build the Breez SDK you need to have access to the Greenlight repository. Greenlight will eventually be open-sourced (with an MIT license), but is not yet public.

This is what I was talking about
https://github.com/getAlby/nips/blob/master/47.md

From the user's point of view, I didn't find any changes in the interface plan. It's just about the internal stuffing in terms of the fact that Amethyst will be able to work with a certain Wallet Connect API, which will be like a proxy? To be honest, I haven't figured anything out yet.

From the user's point of view, I didn't find any changes in the interface plan. It's just about the internal stuffing in terms of the fact that Amethyst will be able to work with a certain Wallet Connect API, which will be like a proxy? To be honest, I haven't figured anything out yet.
P.S. Before answering, I started Googling "Wallet Connect" and found some kind of wallet-application connection protocol. There were a lot of shitcoins and I am very skeptical about your words. But after reading your post in Nostr, I realized that that site and protocol have nothing to do with your implementation. I realized that it was about NIP-47 (I haven't read it yet). It is probably worth clarifying this, otherwise many may be misled.

I zapped your note note1dv6k9mqmlw5ezmzk353hm3kcr6ajhjmluqvgztke5ykp6mjppr3sgvency 200K sats. This is the first main step of your NIP-47 so I decided to send 2/3 of my promised bounty :) Thanks!

oh, hey, thanks! Were you using the code alby provided?

oh, hey, thanks! Were you using the code alby provided?

No. Can you give to me link of code?

Can I close this issue?
Generally speaking, most of what is described here is implemented ("Wallet Caonnect" protocol and one-click zapping (when the Amethyst has only one value zap setting)). I sent the zaps in the amount that I promised (after the first 200K sats I sent them through zap to Nostr, just didn't report it, but I think you got them ;-)


There is a big gap between the results of repeated experiments

Hello, I found that there is a big gap between the results of each training. I use your code and vgg16_ Voc2007.yaml has obtained the results of 52.3, 51.2, 50.2, etc., so it is difficult to determine the benefits after changing the code. Is there any way to reduce this fluctuation and increase the stability of the results？

Hi, I found that upgrading to higher PyTorch version may be the possible reason of unstable training. You could try to incorporate the tricks mentioned here (like bounding box regression / Fast R-CNN branch and use OICR w/ more training iterations) into the PyTorch 0.4.0 version codes for more stable training.

Hi, I found that upgrading to higher PyTorch version may be the possible reason of unstable training. You could try to incorporate the tricks mentioned here (like adding bounding box regression / Fast R-CNN branch and using OICR w/ more training iterations) into the PyTorch 0.4.0 version codes for more stable training.

Thank you. I'm trying to do more iterations before the learning rate drops

Could you share your findings here after you get some numbers?

I do a few more experiments. I change the number of iterations to 75000 and reduce the learning rate at 55000. In other words, 5000 more iterations before reducing the learning rate. The results still fluctuate. 53.0 and 51.3 respectively.
I use 1080Ti and pytorch1.6.0

Thanks for your update. You could try to downgrade to the PyTorch 0.4.0 version of codes for more stable training.

@Glutton-zh Have you solved your problem and achieved stable results?


fix: handle empty object as input

closes #111
3 verifiers trigger an error when an empty object is passed down:
OpenAttestationEthereumDocumentStoreStatus
OpenAttestationDnsTxt
OpenAttestationEthereumTokenRegistryStatus
For all those verifiers the error happens during the test function (which determines if a verifier should run or not)
The plan is to fix those test functions so that the verifiers doesn't run if issuers property (in that case) is not provided => the result for those verifiers will be skipped fragment.
On top of that OpenAttestationHash verifier currently return invalid while it shouldn't run because targethash/merkleroot/data are missing => the plan is to fix this behaviour so that the verifier is skipped in that case.
Also to make sure that verifiers test function handle correctly, we should provide a partial object (deeply)

:tada: This PR is included in version 4.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


socketPath is null in scworker

hi,
i need to access getSocketURL() value, but every time this function returns null.
_socketServer.getPath() retrun null too.

@mnami Nice find. Fixed.
It happened when you used the default socket path/URL '/socketcluster/'.
Note that I took the opportunity to rename the method to worker.getSocketPath() instead of getSocketURL() - URL kind of implies that it's a full URL, but in fact it's just a relative path.
getSocketURL() still works but it has been deprecated and will be removed at some point in the future.


jenkins slave on ubuntu - mode flag missing

mode flag is missing when set to 'exclusive' when launching a slave. I'll submit a fix.

This is fixed in latest release. We had an old version in our git tree. Updated now.


Split job and jobconfig (packit)

Split the JobTriggerType to one related to config and one for actual triggers.

Do not merge this before we are ready in the p-s pull-request otherwise, the p-s code will be broken. (Ideally, merge this one, retest the p-s one and merge it in a short period.)

I'm having difficulties understanding the context of this change: why is it needed, and why is it done the way it is?
Could you capture some of these details in the commit message. (See this explanation, why this is nice to have).

Could you capture some of these details in the commit message. (See this explanation, why this is nice to have).

I don't want to have it in the commit since it's cross-project change and complex and I am not sure if it will be useful to have such long message in the commit.
The context (which I wanted to discuss on the ar-meeting):

By now, we have JobTriggerType which is used in the config as well as for the events we are using in the packit-service.
Some triggers cannot be configured by users (e.g. CoprBuildEnd,..)
Problem 1: We are using one enum for multiple purposes.
Problem 2: It's hard to get the right config for the "fake" triggers.
Problem 3: Current workflow does not support multiple triggers for one action.
Here is a first part of the solution to the problems -- split the enum to two.

(See this
Nice article, I know about it.

Could you capture some of these details in the commit message. (See this explanation, why this is nice to have).

I don't want to have it in the commit since it's cross-project change and complex and I am not sure if it will be useful to have such long message in the commit.

These details should be captured in the commit message especially because there are complex and cross-project.
As for the usefulness:

we would have saved a lot of typing time during this review, if this information would have been in the commit message (I was expecting it and looking for it) :smiley:
could have helped folks not aware of this change coming up (me :confused: ) to have a meaningful contribution to the review process while also catching up with what's going on.
will potentially save a lot of time for someone in the future, trying to re-establish the context of this change in order to fix some issue.
good commit messages will help us immensely with building a community of contributors around Packit, as it will be much easier for outside contributors to understand how the project evolved, without us having to spend super much extra effort to keep some separate set of docs up to date and relevant.
the folks writing the blog posts on Fridays wouldn't need to spend hours reading through all the diffs of all the changes during the week trying to figure out why things happened, so that they can summarise it.

The context (which I wanted to discuss on the arch-meeting):

By now, we have JobTriggerType which is used in the config as well as for the events we are using in the packit-service.
Some triggers cannot be configured by users (e.g. CoprBuildEnd,..)
Problem 1: We are using one enum for multiple purposes.
Problem 2: It's hard to get the right config for the "fake" triggers.
Problem 3: Current workflow does not support multiple triggers for one action.
Here is a first part of the solution to the problems -- split the enum to two.

Very nice explanation, thanks!

(See this

Nice article, I know about it.

These details should be captured in the commit message especially because there are complex and cross-project.

complex +1, cross-project -1
I will add the content of the comment to the git message.

recheck

I'd say it's either a commit message or somewhere in the PR, but I agree with @csomh that it should be written down for the reviewers
well described and explained :mount_fuji:
for the Fiday fun, we should a tool to pre-generate the changelog - since I'm doing it today I may give the script a go


Buffer Overhead Vulnerability

Node Security Project has released a Buffer Overhead Vulnerability advisory  for this project, please see: https://nodesecurity.io/advisories/142 (CVSS high priority) dependency

Overview
concat-stream is a writable stream that concatenates all the data from a stream and calls a callback with the result. By supplying a numeric value to the write function, in certain circumstances it is possible to cause a buffer overread which will read arbitrary memory.
Remediation
Consider using the --zero-fill-buffers command line argument to zero out buffer before using them. Avoid passing numeric values to the write function.
References
https://nodejs.org/api/buffer.html#buffer_the_zero_fill_buffers_command_line_option

I don't think this is valid. This specific case appears to have been addressed almost a year ago in 3e285ba5e5b10b7c98552217f5c1023829efe69e.

@rmg 👍 3e285ba5e5b10b7c98552217f5c1023829efe69e should have corrected this issue
either way very bizarre, likely a bug in NSP since they have already pulled down the advisory