log show ip already released， but subnet status still show it is in using

kube-ovn 1.12.3
kube-ovn 1.12.4
Bug Report
log show ip already released， but subnet status still show it is in using
Expected Behavior
log show ip already released， the subnet status should show it is not in using
Actual Behavior

Steps to Reproduce the Problem

Additional Info

Kubernetes version:
Output of kubectl version:
(paste your output here)

kube-ovn version:
(paste your output here)

operation-system/kernel version:
Output of awk -F '=' '/PRETTY_NAME/ { print $2 }' /etc/os-release:
Output of uname -r:
(paste your output here)

IP is reserved for VM if --keep-vm-ip is set to true.

ip is also removed， i will fix it like this later


GW190425 example fails due to a relative binning error

The GW190425 example currently fails with the following error that is related to relative binning:
Traceback (most recent call last):
  File "/home/mjwill/git_repos/bilby/examples/gw_examples/data_examples/GW190425.py", line 118, in <module>
    likelihood = bilby.gw.likelihood.RelativeBinningGravitationalWaveTransient(
  File "/home/mjwill/git_repos/bilby/bilby/gw/likelihood/relative.py", line 148, in __init__
    self.compute_summary_data()
  File "/home/mjwill/git_repos/bilby/bilby/gw/likelihood/relative.py", line 334, in compute_summary_data
    stop = masked_frequency_array[end_idx]
IndexError: index 62977 is out of bounds for axis 0 with size 62977

I suspect this means there's a bug in the relative binning likelihood.

I've checked, and this example still ran in v2.2.2, so I believe this bug was introduced in https://github.com/bilby-dev/bilby/commit/103a5127b3f896e924fd77e3bbcbbc9b404fb9ca#diff-b8983bc349cc3e1bc4986b6de834bf9493ef07528d022f86510032dce710718bR219.
@adivijaykumar do you have any insight into this?

Is this addressed by #48?

Ah, I'd missed that. I think it is.

Closing this since #48 has been merged.


More tests

Current coverage is 69.23%

Merging #46 into master will increase coverage by +9.23% as of 3d17c04

@@            master     #46   diff @@
======================================
  Files            2       3     +1
  Stmts           10      13     +3
  Branches         0       0
  Methods          0       0
======================================
+ Hit              6       9     +3
  Partial          0       0
  Missed           4       4

Review entire Coverage Diff as of 3d17c04

Uncovered Suggestions

+15.38% via ...utils/ApolloUtils.js#17...18
+15.38% via ...utils/ApolloUtils.js#5...6

Powered by Codecov. Updated on successful CI builds.


Possible bug with index signatures and the ? : operator

TypeScript Version:  2.1.5
Code
//Example 1
const foo: { x: number } | {} = { x: 1 };
const bar: { [index: string]: never } = foo; //compile error

//Example 2
const foo2: { x: number } | {} = true ? { x: 1 } : {};
const bar2: { [index: string]: never } = foo2; //ok

Expected behavior:
Both examples should behave the same way, since the types are the same.
Actual behavior:
The first example gives a compile error:
bug.ts(2,7): error TS2322: Type '{} | { x: number; }' is not assignable to type '{ [index: string]: never; }'.
  Type '{ x: number; }' is not assignable to type '{ [index: string]: never; }'.
    Property 'x' is incompatible with index signature.
      Type 'number' is not assignable to type 'never'.

The second example compiles fine. I'm not sure, but I don't think it should.

Typescript uses the assigned type of foo and foo2 because it can track their assignments in the current scope. So foo2 is fine because its type is {}, which is indeed assignable to { [index: string]: never }; it doesn't have any properties that could violate the constraint. foo fails because its type is { x: number }.

I don't understand how foo2 has type {}. What if you replace true with Math.random() < 0.5, would that change anything? How is the type { x: number } | {} compatible with { [index: string]: never }

Oh, looks like the type of ?: is more complicated than I thought. Looking at the code, I see (in getBestChoiceType) that if the whenTrue type is assignable to the whenFalse type, it returns the whenFalse type. And vice-versa. If neither are assignable, then the type is the union of the whenTrue | whenFalse.
{ x: number } is assignable to {}, so the ternary's type is {}, regardless of whether we can constant-fold the conditional.
(The spec in section 4.20 just says that the type is the union of whenTrue | whenFalse. I think with, subtype reduction, that is equivalent to the rule I described above. It's just less efficient.


[enhancement]: Intergrate Instruct Pix2Pix

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
No response
What should this feature add?
A few days ago a new project has been released that allows to edit an image using text prompts without inpainting.
https://github.com/timothybrooks/instruct-pix2pix
Other Stable Diffusion UI already started to integrate it:
https://www.reddit.com/r/StableDiffusion/comments/10kbyro/nmkd_stable_diffusion_gui_190_is_out_now/
It would be incredible to have this functionality as a part of InvokeAI.
Alternatives
No response
Aditional Content
No response

Do you have colab link for Pix2Pix? it looks interesting

This one should work:
https://colab.research.google.com/github/huggingface/notebooks/blob/main/diffusers/InstructPix2Pix_using_diffusers.ipynb
Also, the repo description has a link to the demo.

thanks 😁

that does look like a very convenient way to do things, simple and effective :D

Is there any news?

Yes, implementation of this feature is still highly desirabe.

yes please! <3

Any update on this? It would indeed be awesome to have it working on InvokeAI


Fix some broken images.

Pokemon like sinistcha-masterpiece who have the same home image for both forms are broken when using the masterpiece form. Probably a similar issue for the pre-evo + the polteageist line. Maushold-family-of four is also broken

Closed in 1933e10


Add Support for Solr Authentication

Currently, we assume that Solr is accessible to the REST API / backend without any authentication. We should consider minimally supporting Solr's Basic Authentication for anyone who wishes to require authentication into Solr.
https://lucene.apache.org/solr/guide/8_7/basic-authentication-plugin.html
Solr also supports a number of other Authentication Plugins, but it appears most plugins are not yet supported in SolrJ (which we use).
Workaround
Currently, if you install Solr with Basic Authentication enabled, you'll end up seeing Error 401 require authentication errors from Solr.  If you encounter that, the workaround is to set AuthType="None" in your solr.conf.  Just be sure that your Solr is secured in another way, often behind a firewall.  The Solr maintainers recommend that Solr never be publicly available on the web.

some Solr installations utilize a solr.in.sh script to set options as environment variables. A possible location for such a script on an RHEL/CentOS/AmazonLinux machine will be at /etc/default/solr.in.sh

In reading more about the Basic Auth plugin for Solr, it seems you can

use SolrJ’s PreemptiveBasicAuthClientBuilderFactory to add basic authentication credentials to all requests automatically

https://solr.apache.org/guide/8_1/basic-authentication-plugin.html#global-jvm-basic-auth-credentials
I.e. it may be possible to hard wire the credentials for all requests... Now, if you're wondering what the point of that exercise would be, I join you in wondering. But, it's definitely worth checking out.

Moving this to the 7.2 board, as this is very low priority (until we have users requesting this as a feature).


Do we need more than 1 external IPs for the Cloud NAT

In regards to:
https://github.com/terraform-google-modules/terraform-google-vault/blob/cfcd7b52e6bd77146544d9f952e8deda31953f3d/network.tf#L23
I think IPs are global, and Cloud NATs are regional (multizone), so I dont completetly understand why we want two NAT IPs for outbound traffic... probably Im missing something, but just in case we can change this...

IPs are globally routable, but these IPs in particular are regional IPs (they live within a region), but the main reason is for higher availability. You can safely change that to 1 and everything will still work.


add resource embedding section and rust-embed

Also what's the purpose of this when there's !include_bytes and !include_str?

Oops typo. Well I was learning rust and decided to do this as a learning practice. Man! I thought there should be a possible way to include files using macro. But this maybe has better use case as it can dynamically also load files(todo) for debugging purposes maybe and is useful for serving files through http.

Actually, it would be nice to have a wrapper around include_bytes! and include_str!, so you could do something like asset!("data/foo.bin") or asset_str!("styles/bar.css").
This should be implemented as a compiler plugin though.

@suhr Thanks I'll try to figure that out --> using compiler plugins that is

Done! Anyone want to look at to.
https://github.com/pyros2097/rust-embed
I've implemented it as a compiler plugin/macro
let asset = embed!("examples/public".to_owned());
asset("/index.html".to_owned()).unwrap();


Wall Breaker Game

I would implement a wall breaker game in js.
please assign this issue to me @geekymeeky

Sure. Go ahead @nikhv

Closed via #31


GraphQL Saved Queries Fail when " in the query

Environment

Python version: 3.7
Nautobot version:  1.1.0-beta.2

Steps to Reproduce

Create a query with quotes in it
Click on Execute on the right hand section of the page

query {
  sites(name: "Location2") {
    name
    circuit_terminations {
      circuit {
        cid
      }
    }
  }
}

Expected Behavior
Query to run

Observed Behavior
Error:
{
  "errors": [
    {
      "message": "Syntax Error GraphQL (2:15) Unexpected character \"&\".\n\n1: query {\n2:   sites(name: "Location2") {\n                 ^\n3:     name\n",
      "locations": [
        {
          "line": 2,
          "column": 15
        }
      ]
    }
  ]
}

I found the same issue. For clarity, this is not on the graphiql page, but when executing from within the graphqlquery view:  extras/graphql-queiries/<slug>

Django is escaping the characters automatically due to it being within a Javascript block is my understanding. That means the quotes that are in the saved query turn into ". I have #707 opened for a fix, but more or less a discussion to see what the best fix is since this is user provided data.

Since we can easily jump to GraphiQL to execute the query with the Open in GraphiQL button , is it really worth it to have another option to execute the query directly ? The GraphiQL is interface is much better in my opinion
My preference would be to remove the response panel altogether from this page and maybe bring down the Open in GraphiQL  button to make it even more explicit

IMO, I think it is nice to be able to do a quick validation that the query just saved is working as expected from the interface where it is created. I think these two interfaces (execute button and graphiql) serve different useful purposes.
I see the workflow as:

use graphiql to develop working query
save the query in nautobot
validate it is working as expected

The third step for me would be the execute button, and without that option, I would have to use some external tool to execute the query for validation.


[move-only-object] Teach move only object verifier how to emit proper errors for closure/defer uses

Specifically, we error if one consumes a value at all in side a closure/defer and do not make a distinction in between no escape, defer, and escaping closures. This is just to make a sane base model that we can then build on top of.
rdar://103313305

@swift-ci smoke test

@swift-ci smoke test

Windows failed in LLVM


Don't access s_renderInfo from the Unity thread, instead read from s_…

…lastRenderInfo. Appears to fix the random Unity crashes.

@russell-taylor added. Is that the correct way to use the mutex?

The lock_guard is a good way to do it.  Why did it get changed back to manual locking and unlocking?

yeah, you definitely want to use lock_guard instead of this last commit.

Looks good.  The only remaining issue is that the code may get inconsistent views for the left and right eyes if the value is read in between those.  If predictive tracking is doing its job well, the estimates should be close to consistent.

Added mutex around other s_lastRenderInfo accesses that were missed. Getting confident that this minimally resolves the random crashing we were seeing. Working on https://github.com/OSVR/OSVR-Unity/issues/208 to make sure other crashing issues aren't related.

Ok, confirmed that it wasn't causing another crashing issue. Merging.


Namespace - why is the amount not displayed in dashoard

After creating the namespace, why is the amount not displayed in the dashboard instead showing N/A

@surekabpm in amount column is presented amount transferred for Transfer Transaction. Namespace creation is not Transfer Transaction.
I'm closing as not a bug


Exception InvalidBody will not thrown (at 0.3.3/0.4.0)

Since version 0.3.3 and 0.4.0 the validator will not throw an InvalidBody Exception.
Version 0.3.2 throws this validation exception.

Could you please provide more details on which schema and data you are trying to validate?

I can give you just some code snippets:
schema.yaml:
components:   schemas:     prescription:       properties:         exampleTyp:           type: string           enum:             - VALID             - STILLVALID
using functions:
ValidatorBuilder -> fromYamlFile and ServerRequestValidator -> validate
until test data:
`$data = [
'exampleTyp' => 'INVALID',
];
$this->expectException(InvalidBody::class);`
Output: (for version 0.3.3 and 0.4.0)
Failed asserting that exception of type "OpenAPIValidation\PSR7\Exception\Validation\InvalidBody" is thrown.

Components are just re-usable parts of schema,actually there is no schema defined in your sample. Consider re-check your actual schema/
We already have the test for case you are talking about
https://github.com/thephpleague/openapi-psr7-validator/blob/5d2a74ed7b94511c89b5c79a00835b72844fd012/tests/Schema/Keywords/EnumTest.php#L30-L48

I wrote a short example test for you. Please try this yaml schema and the used methods.
public function testValidateFromYamlContentWithInvalideBody(): void
    {
        $filePath = __DIR__.'/../fixtures/schema.yaml';
        $contentYaml = file_get_contents($filePath);

        $url = '/api/test/create';
        $headers = new Headers();
        $headers->addHeaders(['Content-Type' => 'application/json']);

        $data = [
            'exampleTyp' => 'INVALID',
        ];

        $request = (new Request())->setMethod(Request::METHOD_POST)
                                      ->setUri($url)
                                      ->setHeaders($headers)
                                      ->setContent(json_encode($data))
                                      ->setPost(new Parameters([]));

        $serverRequest = Psr7ServerRequest::fromZend($request);

        $serverRequestValidator = (new ValidatorBuilder())->fromYaml($contentYaml)->getServerRequestValidator();
        $this->expectException(InvalidBody::class);
        $serverRequestValidator->validate($serverRequest);
    }

openapi: 3.0.0
paths:
  /api/test/create:
    post:
      description: 'Test'
      operationId: api.prescription.create
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/prescription'
      responses:
        '200':
          description: 'ok'
components:
  schemas:
    prescription:
      properties:
        exampleTyp:
          type: string
          enum:
            - VALID
            - STILLVALID

Yea, now looks valid. , I've rewrote the test to match ours in #34 .
@cebe, looks like there is no default type=object for components schema now. Explicitly adding prescription.type: object makes the test pass, but I think type is object by default for schema with properties, isn't ?

@cebe, looks like there is no default type=object for components schema now. Explicitly adding prescription.type: object makes the test pass, but I think type is object by default for schema with properties, isn't ?

I could not find anything about a default value of type in OpenAPI 3.0.2, also not in the JSON schema specifications.
The only thing that comes close is

An empty schema is a JSON Schema with no properties, or only unknown properties.
https://tools.ietf.org/html/draft-wright-json-schema-00#section-4.4

But this seems to be more about the type of the schema itself instead of the type of validated data.

https://tools.ietf.org/html/draft-wright-json-schema-validation-00#section-4.2
Validation keywords that are missing never restrict validation.  In
some cases, this no-op behavior is identical to a keyword that exists
with certain values, and these values are noted where known.

following this part, a missing "type" should mean that the validated data can be of any type, it does not restrict validation. Assuming a default value of object would be wrong as far as I see.

So for the current issue you should validate all properties if the input data is an object, but not validate the type of the input data. Also, ignore properties if the input data is not an object:

https://tools.ietf.org/html/draft-wright-json-schema-validation-00#section-4.1
Most validation keywords only limit the range of values within a
certain primitive type.  When the primitive type of the instance is
not of the type targeted by the keyword, the validation succeeds.

@cebe So you'd better consider this as won't fix?

nope, the current schema does not restrict the type of input data, so validation has to check the type of input data to decide how to proceed with the validation. If the input data is an object, you must validate the properties, but if the input data is not an object, the validation does not fail.

Hm, I've got your point. So we should infer data type if schema does not restrict it.


Git: All changes are Committed, even if some are unselected

Issue Type: Bug
In Source Control: Git tab, I have a changes in 12 files.
I select 10 out of 12 files (with ctrl+click), enter a Commit message, and press Commit command.
Observed: all 12 changes are commited
Expected: only the 10 selected changes should be committed
Use case: I worked on 2 different issues and I want to commit them separately, with 2 separate Commit messages.  First commit is 10 files and second commit is remaining 2 files.
VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:13:36.375Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-5700HQ CPU @ 2.70GHz (8 x 2694)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.92GB (5.16GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

debugger-for-chrome
msj
4.11.1

Unfortunately, selecting + committing doesn't do anything. After selecting, you must stage them by clicking on any of the + (Stage) inline actions. Once staged, only those changes will be committed.


[Bug]: error message is illegal when invalid arguments given

ODC version
ODC422
OB version
Oceanbase410
What happened?
When running PL, a string is passed as the input parameter but an int is actually required, and the interface is 401.

What did you expect to happen?
execute normally
How can we reproduce it (as minimally and precisely as possible)?
Run PL
create procedure `testBug26143` (IN `I` int(11)) BEGIN
SELECT I * 10;
END;

Anything else we need to know?
No response
Cloud
No response

pass


0.12.2 duplicated results for a measurement, possible query or storage issue

Bug report
Hi All, as requested here a bug report: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/influxdb/t-Cq2TYngJA/2T0ljku6BQAJ
And with the info repeated:
There are no tags associated with this measurement, so any re-writes should overwrite the existing point.
I am using tags on a meta data table (measurement) which is unrelated to this measurement.
> show tag keys
name: EIGEN_META_DATA
---------------------
tagKey
ITEM_NAME

name: METADATA
--------------
tagKey
tag

So using the CliTool:
> SELECT * FROM "egtesta-c1" WHERE time ><PHONE_NUMBER>000ms AND time <<PHONE_NUMBER>000ms ORDER BY time LIMIT 10001
name: egtesta-c1
----------------
time			status	value_EIGAI
1451610000000000000	OK	5.995811366641718
1451610000000000000	OK	5.995811366641718
1451613600000000000	OK	-2.9888508672566587
1451613600000000000	OK	-2.9888508672566587
1451617200000000000	OK	25.077066449318792
1451617200000000000	OK	25.077066449318792
1451620800000000000	OK	31.851006703756894
1451620800000000000	OK	31.851006703756894
1451624400000000000	OK	9.170833664095454
1451624400000000000	OK	9.170833664095454
1451628000000000000	OK	26.800614221779156
1451628000000000000	OK	26.800614221779156
1451631600000000000	OK	5.511991831356866
1451631600000000000	OK	5.511991831356866
1451635200000000000	OK	-21.149676035207094
1451635200000000000	OK	-21.149676035207094
1451638800000000000	OK	-13.184388185819813
1451638800000000000	OK	-13.184388185819813
1451642400000000000	OK	-5.454241981957935
1451642400000000000	OK	-5.454241981957935
1451646000000000000	OK	-28.34448642251391
1451646000000000000	OK	-28.34448642251391

Not every measurement is exhibiting this:
> SELECT * FROM generatedTag9_ANALOG limit 10
name: generatedTag9_ANALOG
--------------------------
time			status	value_EIGAI
1451602800000000000	OK	91.63689704262038
1451602805000000000	OK	91.62940625834233
1451602810000000000	OK	91.62244134904466
1451602815000000000	OK	91.61600244732924
1451602820000000000	OK	91.61008967578343
1451602825000000000	OK	91.6047031469779
1451602830000000000	OK	91.5998429634644
1451602835000000000	OK	91.59550921777381

I am wondering if there is crosstalk between databases created in influx? I have definitely seen measurements show up on the Internal database (not on this version, yet), and disappear again.
I have made a backup of the data files (just copying .influxdb folder (I'm on OSX)) to another location); I will shortly blow this db away  (upgrade to v13?) (duplicates break our api), but I have a backup should you need it for diagnosis.
Cheers!
Ian

If you take a backup, be sure to include any directories under ~/.influxdb such as the meta directory as they may be useful for loading the data.

yep thats the one I have :)

@ianlutzeigen Would you be able to test a nightly that includes #6668?

Also, if you have a script to reproduce the duplicates, that would be very helpful.

Sorry, I don't have such a script; I do tend to delete loads of test data and re-write as I go about my business; just the nature of how I am writing code around influx, so I do not have a specific reproducible script. I will keep and eye on it... don't think I am in a position to explicitly test it at this moment.

I am also seeing this behavior, but cannot get it to happen again with test/anonymized data, or without using our proprietary loading script.  heres a sample output though:
`> select * from test_stats order by time desc limit 50
name: test_stats
time                    field1  field2  field3  field4  id      tag1    tag2
1463776920147478000     139999                          3147478 12      0
1463776920147478000     139999                          3147478 12      0
1463776533147477000     39900                           3147477 8       1
1463776443147476000     34999                           3147476 6       0
1463776360147475000     3995                            3147475 1       0
1463776254147474000     19995                           3147474 1       0
1463776214147473000     2990                            3147473 1       0
1463776209147472000     12995                           3147472 1       0
1463776165147471000     81495                           3147471 1       0
1463775800147470000     28995                           3147470 6       0
1463775695147465000     21490                           3147465 1       0
1463775630147464000     3995                            3147464 1       0
1463775319147463000     174294                          3147463 8       1
1463775290147462000     242900                          3147462 12      0
1463775290147462000     242900                          3147462 12      0
1463775254147461000     99999                           3147461 12      0
1463775254147461000     99999                           3147461 12      0
1463775195147460000     1995                            3147460 1       0
1463775025147459000     166416                          3147459 1       1
1463774988147458000     119800                          3147458 8       0
1463774899147457000     119900                          3147457 12      0
1463774899147457000     119900                          3147457 12      0
1463774823147456000     62995   1       1               3147456 1       0
1463774822147455000     9900    1       1               3147455 1       0
1463774817147454000     26998   1       1               3147454 6       0
1463774778147453000     97183   1       1               3147453 6       0
1463774578147452000     278775                          3147452 1       1
1463774557147451000     69999   1       1               3147451 1       0
1463774433147450000     9999    1       1               3147450 1       0

`

@jwilder, I have a file and steps that will add duplicated results. This requires you to have jq installed, but I figure thats pretty normal.
Basically, what I am doing is dropping and re-creating a database, adding in some data, then proving there are no duplicates with the first SELECT.
Then, we drop the measurement, and add the exact same data back in, again checking the SELECT to see that we have some non-unique random-ints or times.
curl -i -X POST http://localhost:8086/query --data-urlencode "q=DROP DATABASE test_data"
curl -i -X POST http://localhost:8086/query --data-urlencode "q=CREATE DATABASE test_data"

curl -X POST curl -i -X POST 'http://localhost:8086/write?db=test_data&precision=u' --data-binary @bad_data.line

curl -sS -GET 'http://localhost:8086/query?db=test_data' --data-urlencode 'q=SELECT randomint FROM "test_data" order by time desc limit 50'  | jq -C '[foreach .results[0].series[0].values[] as $item ([[],[]];  $item[1])]|sort' | uniq -c |  grep -v '^ *1 '

curl -i -X POST http://localhost:8086/query --data-urlencode "db=test_data" --data-urlencode "q=DROP MEASUREMENT test_data"

curl -i -X POST 'http://localhost:8086/write?db=test_data&precision=u' --data-binary @bad_data.line

curl -sS -GET 'http://localhost:8086/query?db=test_data' --data-urlencode 'q=SELECT randomint FROM "test_data" order by time desc limit 50'  | jq -C '[foreach .results[0].series[0].values[] as $item ([[],[]];  $item[1])]|sort' | uniq -c |  grep -v '^ *1 '

curl -sS -GET 'http://localhost:8086/query?db=test_data' --data-urlencode 'q=SELECT randomint FROM "test_data" order by time desc limit 50'  | jq -C '[foreach .results[0].series[0].values[] as $item ([[],[]];  $item[0
[influx_test_case.zip](https://github.com/influxdata/influxdb/files/293927/influx_test_case.zip)

])]|sort' | uniq -c |  grep -v '^ *1 '

And attached is a data file.

@brewneaux Can you reproduce this with the latest nightlies?

Yes, built from source minutes ago on OSX, I still experience this issue.  However, I'm also finding that it is not EXPLICITLY related to dropping measurements.  I'm have a script that populates a lot of back data, and that also causes the issue on a completely fresh install (deleted the .influxdb folder). Writing about 125k points about as fast as it will take them also causes the issue.

To elaborate, so far I have experienced the problem on 0.12, 0.13, master as of 2016-06-01, and it does NOT happen on 0.9.

I have got EXACTLY the same issue regularly on InfluxDB 0.13
installed on Ubuntu Server 16.04 (4GB RAM, 2 CPU)
My tests results below - the same data has been inserted into fife databases:
db1.rp.measurement1 - 263471 data points
db1.rp.measurement2 - 13191 data points
db2.rp.measurement1 - 263471 data points
db2.rp.measurement2 - 13191 data points
db3.rp.measurement1 - 263471 data points
db3.rp.measurement2 - 17034 data points (3843 duplicates)
db4.rp.measurement1 - 263471 data points
db4.rp.measurement2 - 13191 data points
db5.rp.measurement1 - 263471 data points
db5.rp.measurement2 - 26727 data points (13536 duplicates!)
I've made above test many times, ALWAYS with some duplicates.
For double sure I inserted CSV data dump from InfluxDB  into MySQL where I have access full SQL
and I definitely we have duplicates, not separate series using different tag values.
I use influx -import -path command on localhost for inserting data from files containing 5000 data rows or less, all data files contains DML section for choosing database and retention policy.
Inserts into all databases are made basically in the same time (during a few minutes) by using two celery workers. Due to other data processing process, CPU usage was quite high (between 50% and 90%)
If required I can provide more information including inserted data files, data dumps etc.
I hope this issue can be solved quickly as many queries starts to be useless when data set
contains duplicates.

@pga32 Can you reproduce with 1.0beta?

I already made similar tests on version 1.0.0-beta1 by using six separate databases.
All measurements was without duplicates!
Additionally I added for deeper tests a few times more data - results was also without duplicates,
but I noticed something suspect:
When I've checked counts of records directly after inserts in 4 of 12 used measurements
I had a slightly different result of count(). 15 minutes later when I made
again the same queries, count() for all measurements was correct and the same in all databases.

I'm still getting this on 1.1.0~n201606070800.

Still occuring on 1.1.0~n201606270800

should we expect the fix for this to be in 13.1 ? I am hanging out for a stable release that does not have this problem. Thanks! :)

apologies the  13.1 I was looking at was telegraph, not influx

#7027 may fix this

Duplicate of #6946


UDP bind error: Address family not supported by protocol

Hi ,
Context
Host Machine:

ubuntu 20.04
ROS noetic
pf_lidar_ros_driver at main branch, commit 88bebcc7
IP: <IP_ADDRESS>
mask: <IP_ADDRESS>

Device:

Type: OMD30M-R2000-B23-V1V1D-HD-1L
Address mode: static
IP: <IP_ADDRESS>
mask: <IP_ADDRESS>
Gateway: <IP_ADDRESS> or <IP_ADDRESS> (tried with both)
FW: 1.62
HW: 1.72
PFSDP: 1.04

Ping

Ping is ok from host machine to the device

ISSUE
From the host machine, I do:

Edit the pf_lidar_ros_driver/src/pf_driver/config/r2000_params.yaml as:

R2000:
  transport: "udp"
  scanner_ip: "<IP_ADDRESS>"
  port: "3000" # optional
  device: "R2000"
  start_angle: -1800000
  max_num_points_scan: 0
  packet_type: "C"
  scan_topic: "/scan"
  frame_id: "scanner_link"
  watchdogtimeout: 60000
  watchdog: true

roslaunch pf_driver r2000.launch
and I get:

... logging to /home/beta/.ros/log/67512ddc-1357-11ef-962f-9cb6d0e16137/roslaunch-maupas-237492.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://<IP_ADDRESS>:42357/

SUMMARY
========

PARAMETERS
 * /r2000_node/R2000/device: R2000
 * /r2000_node/R2000/frame_id: scanner_link
 * /r2000_node/R2000/max_num_points_scan: 0
 * /r2000_node/R2000/packet_type: C
 * /r2000_node/R2000/port: 3000
 * /r2000_node/R2000/scan_topic: /scan
 * /r2000_node/R2000/scanner_ip: <IP_ADDRESS>
 * /r2000_node/R2000/start_angle: -1800000
 * /r2000_node/R2000/transport: udp
 * /r2000_node/R2000/watchdog: True
 * /r2000_node/R2000/watchdogtimeout: 60000
 * /r2000_node/device: R2000
 * /robot_description: <?xml version="1....
 * /rosdistro: noetic
 * /rosversion: 1.16.0

NODES
  /
    r2000_node (pf_driver/ros_main)
    robot_state_publisher (robot_state_publisher/robot_state_publisher)
    rviz (rviz/rviz)

ROS_MASTER_URI=http://<IP_ADDRESS>:11311

process[robot_state_publisher-1]: started with pid [237508]
process[r2000_node-2]: started with pid [237509]
process[rviz-3]: started with pid [237510]
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-beta'
[ INFO] [/r2000_node]: Device found: R2000
terminate called after throwing an instance of 'boost::wrapexcept<boost::system::system_error>'
  what():  bind: Address family not supported by protocol
[r2000_node-2] process has died [pid 237509, exit code -6, cmd /home/beta/ros_ws/install/lib/pf_driver/ros_main __name:=r2000_node __log:=/home/beta/.ros/log/67512ddc-1357-11ef-962f-9cb6d0e16137/r2000_node-2.log].
log file: /home/beta/.ros/log/67512ddc-1357-11ef-962f-9cb6d0e16137/r2000_node-2*.log

It seems there is a problem at socket binding, but the provided IP address seems to be correct v4, so I do not understand the message "Address family not supported by protocol".
Any help will be highly appreciated,
Thanks,
Andreu

Hi Patrick!
Setting transport to "tcp" works ok ... I guess data transfer through tcp adds some extra traffic.
Please, let me know why "udp" is the default transport setting and which implications may have to set it tio "tcp"
THanks
Andreu

Hi
yes it is good to have tcp working because we can unblock our development, but as you point, we'd prefer to work with udp, so let's try to fix the thing...
The print statement of the Local Endpoint seems very suspicious:
[ INFO] [/r2000_node]: Device found: R2000
address, port: <IP_ADDRESS>, 3000
Local Endpoint IP, Port: 19:9cbf:759:ed4f:800c:e41c:a57f:0%3180489729, 11801
terminate called after throwing an instance of 'boost::wrapexcept<boost::system::system_error>'
  what():  bind: Address family not supported by protocol
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-beta'
[r2000_node-2] process has died [pid 75951, exit code -6, cmd /home/beta/ros_ws/install/lib/pf_driver/ros_main __name:=r2000_node __log:=/home/beta/.ros/log/4677694e-1755-11ef-b1b9-9cb6d0e16137/r2000_node-2.log].
log file: /home/beta/.ros/log/4677694e-1755-11ef-b1b9-9cb6d0e16137/r2000_node-2*.log

My output:
beta@maupas:~$ $sysctl net.ipv6.conf.all.disable_ipv6
net.ipv6.conf.all.disable_ipv6 = 0
beta@maupas:~$ $sysctl net.ipv6.conf.default.disable_ipv6
net.ipv6.conf.default.disable_ipv6 = 0
beta@maupas:~$ $sysctl net.ipv6.conf.all.disable_ipv6
net.ipv6.conf.all.disable_ipv6 = 0

Seems everything related to ipv6 is set to false

Setting the three ipv6.conf params to 1
Switch off/on interface
run the pf_driver with the same error
Check after running the pd_driver that ipv6.conf params are still to 1 (just in case)

ok!
thanks, let me know if you need some testing from our side.
Meanwhile we are working with tcp transport type.
thanks!

Hi!
One bad news and one good news:

The bad is your code does not work. the reported output was similar.

the good is that I've found the bug. The problem is in the line:

udp::endpoint local_endpoint = local_endpoint = udp::endpoint(ipv4_any, stoi(port));

which is something I felt weird ... and effectively it is risky ,since depending on what is executing first, things can be wrong. Split it better as:
udp::endpoint local_endpoint;
local_endpoint = udp::endpoint(ipv4_any, stoi(port));

and every thing works !
You may be come back to the initial version and just fix that line.
Thanks for the support


Alternative solution to fix infinite loop on img.onerror

This is an alternative to #586 .

I don't know if 20 attempts is too many or too few, but overall the change looks good to me.

@superdump @stefanalund I think we should merge this one.

Will do soon.


Cleanup Scraper

Type Annotations, more output/progress, etc.

@mliu59 to Type and comment

@dqian3 can we close this?


Basic remote interface error message localization support

The locale ("en", "de", "en_US", ...) is added as an optional parameter named "locale" to each remote interface operation, as a hint for rascsi on the preferred language to use for error messages. Not for logging, just for error messages returned by the remote interface, which potentially end up in a client UI.
This change is backwards compatible, because the core will fall back to English when no locale information is passed. English will also be used for unknown locales or to the best locale match, e.g. "en" instead of "en_US".
rasctl supports an new '-z LOCALE' parameter.
rasctl -l
Error: Authentication failed
>rasctl -l -z de
Error: Authentifizierung fehlgeschlagen
>rasctl -z en_US -i 3 -c a  5 -f image
Error: Device type required for unknown extension of file 'image'
>rasctl -z de -i 3 -c a  5 -f image
Error: Gerätetyp erforderlich für unbekannte Extension der Datei 'image'

Note: The string "Error:" with rasctl is always in English because it is added by the client, not server.

@akuker @rdmark This is a working/tested feature branch for localizing error messages returned by the protobuf interface. Only the authentication failure message is currently localized (English and German), because that's the most relevant one from my perspective.
Client usage is simple, just pass the optional "locale" parameter with each command, and if there is a localized error message for that language it willl be used, with English being the fallback.

@uweseimet - Thank you very much for starting these changes!

@akuker Still, the maintenance problems I mentioned in your ticket is not gone, and is a very realistic one
My PR just addresses error message localization in the backend. The web UI is a different issue. Any my app is liocalized (English/German) anyway.

@uweseimet I added Swedish string localizations, if you didn't mind.

@uweseimet How about implementing the -z option for rascsi as well, to be able to start the process in localized mode?

@rdmark Yes, this probably makes sense. If the client sends a locale this would override the server setting.
Note that rascsl uses the locale from your environment as default, i.e. if your locale is German anyway there is no need to use -z, unless you want a different message language than German.

@rdmark Just added -z for rascsi, but only for console messages, not for the log. Should the log also contain localized messages?

@uweseimet I would suggest not localizing log messages.

@rdmark OK, then the current code should do what we want.

@uweseimet Yes, and with the "locale" parameter for protobuf commands, I think we have what's needed for the client to request the locale that it needs.


the live display is not reset after a CYLCE_TO_DIE

seems to be working sometimes actually, need more test


Audit unsafe in read-fonts

Enumerate them all and get reviews

Okay, so I've looked into this a little bit, and the current API does need some modifications.
For the record, the only tricky bit of unsafe in the codebase is the code for reading references and slices from raw bytes. The reference version looks like this (and the array version is fundamentally similar):
https://github.com/googlefonts/fontations/blob/087db1f531f87fdeb5e3c5ba003b8190432f31c9/read-fonts/src/font_data.rs#L105-L131
As mentioned in the comment at the top of that first wrapper function, there is a problem with the current API, and the use of the FixedSize trait, here.
Put simply, FixedSize does not fully capture the constraints we want.
To refresh everyone's memory:

we have a concept of Scalar types, which are types that can be read from a fixed length of raw bytes.
There is a helper, BigEndian<T>, where T: Scalar. BigEndian<T> is basically a typed byte slice of fixed length, where the length is the number of bytes required to represent T.

For these APIs: we want to only support unsafe casts for BigEndian<_> types, as well as for packed, unaligned structs where all members are BigEndian<_> types. We should have some additional marker trait, (CastSafe or something) that we implement only for BigEndian<T> and for structs containing only BigEndian members, and this trait should used to constrain these unsafe methods.


[Docs/Building.md] Added some Arch Linux specific build instructions, no change to cppcheck as I haven't tested it yet.

Spent a few minutes trying to compile, ran into an issue with CMake not finding my openssl install.  This just adds the command to install dependencies, ninja, and a one-line change under configuration for a quick fix to the issue.

Huh, Déjà vu. Try develop. Arch should work on develop without anything extra I think.

Haven't had any issues as of recent on develop

Haven't had any issues as of recent on develop

Yeah, I've been away from the project for a little while, but I definitely remember coming across this and fixing it.

superceded by current develop changes and the existence of the AUR package etterna
reopen if issue is present on latest develop branch and the requested changes are made


fix identifier metadata on Hebart2023

this needs to be simultaneously updated in the database

travis failing because of the issue identified in https://github.com/brain-score/vision/pull/674


Avoid ThreadLocals to be more looom friendly

The current behaviour for the pooled buffer allocation path (on Netty 4.1, but on 5 is similar) include 2 loom unfriendly ops:

in order to NOT use a cache, we still use a ThreadLocal operation -> https://github.com/netty/netty/blob/b61d7d40f40e3a797e8a60cd567f849a9799c771/buffer/src/main/java/io/netty/buffer/PooledByteBufAllocator.java#L537
Recyclers uses thread local regardless the previous decision

I see 2 fixes here:

being able to determine if a thread shouldn't use any  cache without any thread local method (and sadly checking if current thread is a "used" event loop thread will still use another thread local ops :"/ )
PoolThreadCache(heapArena, directArena, 0, 0, 0, 0) should be a singleton (using a specialized children, if possible) for v threads
recyclers shouldn't be used with v threads for the same problem

The last is a problem we have right now as well with non-virtual and non-event loop threads as well (nudge nudge @chrisvest ): non event loop threads shouldn't use recycler(s) in the form of ThreadLocal::get ops or they will end up creating unecessary objects again.

Sadly, while working on this I've just found that the changes I've made for https://github.com/netty/netty/issues/12621 can be dangerous, I'm opening a new issue to track this.

@chrisvest
I've created a branch to show a potential solution to the problem (see https://github.com/franz1981/netty/tree/4.1_loom_fix), but right after I remembered your solution at https://github.com/netty/netty/pull/13075 - can you please check if https://github.com/netty/netty/issues/13204 can  still happen with your changes, from a logical perspective?

at the same time I've opened a sibling issue at https://github.com/quarkusio/quarkus/issues/33102

Out of curiosity, is there any way to create a thread local on the carrier thread and use it when on a virtual thread? I feel like there should still be a way to leverage platform/carrier thread-local even when using virtual thread...

is there any way to create a thread local on the carrier thread and use it when on a virtual thread? I feel like there should still be a way to leverage platform/carrier thread-local even when using virtual thread...

yes, but is an internal JDK API, see https://github.com/FasterXML/jackson-core/issues/919 and the JDK code at https://github.com/openjdk/jdk/blob/861cc671e2e4904d94f50710be99a511e2f9bb68/src/java.base/share/classes/sun/nio/ch/Util.java#L56 but it can hides subtle un-expect behaviours really
eg

a virtual thread use this per-carrier thread local to create X
the virtual thread perform some blocking operation and is virtually parked
it is then unparked but another carrier is ready to continue it
it "release" X into a different carrier from the original one (making the pools unbalanced? depends)

@trustin Amazing answer to this question: https://stackoverflow.com/questions/75047540/is-it-possible-to-create-a-threadlocal-for-the-carrier-thread-of-a-java-virtual

I believe that the adaptive allocator, thanks to #14279 can already benefit of a proper virtual-thread friendly allocator; sadly this is not the sole fast-thread local usage which can happen on worker thread, but i'll reopen a new one as we will find new ones to fix (in the hot path, clearly).


flutter based wayland compositor like qtwayland

Use case
Using Qt, we can make compositor server on embedded system. Recently I'm considering flutter new app framework to make system UI on embedded device. But, I can't find appropriate solution for compositor server like qtwayland.
Anyone knows some solution for building flutter wayland compositor server ?
I'm checking two options, but it looks performance is not good and I'm not sure wlroot is maintained.
https://github.com/roscale/zenith https://github.com/PlayPulseCom/flutter_wlroots
Proposal
I'm wondering whether there is any official plan for supporting the wayland server feature like qtwayland.

What's the licensing on QT?
Looking at the qtwayland repo the are no protocol files short of two, which would indicate they are using standard Wayland protocols.
Wlroots is active, as is Weston.
This embedder supports Wayland and is used in Automotive Grade Linux (AGL) variety of embedded use cases involving Wayland; is actively supported:
https://github.com/toyota-connected/ivi-homescreen


Fix startup failure issue caused when dynamic proxy is turned on and …

…druid-spring-boot-starter dependency is used

Ⅰ. Describe what this PR did
Fix startup failure issue caused when dynamic proxy is turned on and druid-spring-boot-starter dependency is used
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #2043 into develop will decrease coverage by 0.04%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             develop   #2043      +/-   ##
============================================
- Coverage      55.35%   55.3%   -0.05%
+ Complexity      2506    2504       -2
============================================
  Files            445     445
  Lines          14838   14847       +9
  Branches        1749    1751       +2
============================================
- Hits            8213    8211       -2
- Misses          5863    5872       +9
- Partials         762     764       +2

Impacted Files
Coverage Δ
Complexity Δ

...ta/spring/annotation/GlobalTransactionScanner.java
45.08% <0%> (-3.6%)
17 <0> (ø)

...in/java/io/seata/server/session/GlobalSession.java
84.54% <0%> (-0.49%)
67% <0%> (-1%)

...o/seata/server/coordinator/DefaultCoordinator.java
48.01% <0%> (-0.4%)
27% <0%> (-1%)

@lizwmaster add issue to describe to what happened and the reason why happened.


[ITensors] [ENHANCEMENT] Fix bug in MPO(::OpSum) when on-site operator has no blocks

This PR makes a few improvements:

Fixes bug in MPO(::OpSum, ...) when on-site operators have no blocks (fixes #962).
Add splitblocks keyword argument to MPO(::OpSum, ...) constructor. This defaults to splitblocks=true, since I've found it improves the performance of DMRG in general.
Allow specifying the element type of the output MPO with MPO(::Type, ::OpSum, ...), for example MPO(Float32, opsum, sites) to use single precision.
Improve overloading interface for "Qudit"/"Boson" types (fixes #957).

@emstoudenmire please let me know if you are in favor of these changes.
Checklist:

[x] My code follows the style guidelines of this project. Please run using JuliaFormatter; format(".") in the base directory of the repository (~/.julia/dev/ITensors) to format your code according to our style guidelines.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have added tests that verify the behavior of the changes I made.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] Any dependent changes have been merged and published in downstream modules.

Codecov Report

Merging #963 (758a3fc) into main (1f47c73) will increase coverage by 0.07%.
The diff coverage is 81.03%.

:exclamation: Current head 758a3fc differs from pull request most recent head 8ff5f96. Consider uploading reports for the commit 8ff5f96 to get more accurate results

@@            Coverage Diff             @@
##             main     #963      +/-   ##
==========================================
+ Coverage   66.50%   66.58%   +0.07%
==========================================
  Files          90       91       +1
  Lines        9444     9451       +7
==========================================
+ Hits         6281     6293      +12
+ Misses       3163     3158       -5

Impacted Files
Coverage Δ

src/ITensors.jl
100.00% <ø> (ø)

src/physics/site_types/electron.jl
81.96% <ø> (-0.61%)
:arrow_down:

src/physics/site_types/fermion.jl
98.30% <ø> (-0.09%)
:arrow_down:

src/mps/mps.jl
91.50% <50.00%> (ø)

src/physics/site_types/qudit.jl
84.00% <65.21%> (-1.19%)
:arrow_down:

src/physics/site_types/aliases.jl
88.88% <88.88%> (ø)

src/physics/autompo/opsum_to_mpo_generic.jl
95.48% <100.00%> (+0.17%)
:arrow_up:

src/physics/autompo/opsum_to_mpo_qn.jl
99.35% <100.00%> (+<0.01%)
:arrow_up:

src/physics/site_types/generic_sites.jl
89.47% <100.00%> (ø)

src/ITensorChainRules/ITensorChainRules.jl
84.61% <0.00%> (-7.70%)
:arrow_down:

... and 5 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

There's some mysterious test failure on Windows, but I think it is unrelated to this PR so I'm going to merge.


Is the support for D-Link DWA-131 (rtl8192eu) planned in the future builds?

Hello! I am a PowKiddy v10 owner on ArkOS_RGB10_v2.0_09292024.img and I have an issue with the recommended dongle (TP-Link Archer T2U Nano) - it overheats the type-c adapter very quickly. I tried experimenting with different dongles and adapters, and found out that D-Link DWA-140 didn't heat things up. But this thing is huge. So I went and bought DWA-131, which is smaller and it doesn't have 5ghz support, so it shouldn't be too "heavy".
But ArkOS doesn't seem to recognize it on Powkiddy v10 :(
I checked it on my linux mint laptop and there it works out of the box. So is it possible to add the support for this model in the future?

Did the T2U Nano get very hot on your Linux Mint laptop as well?  Also, have you looked at any of these other adapters that are confirmed compatible? https://github.com/retrogamehandheld/oga/wiki/Frequently-Asked-Questions#what-wifi-adapters-work

It's not the dongle that's getting hot, it's the typeA>typeC adapter. I had the exact same issue with my previous device (Anbernic rg351p), and I just replaced the stock adapter with another one: the issue went away. So with PKv10 I bought the very same adapter as before, but the issue remained. I am pretty sure it's a hardware issue.
I guess even if ArkOs supported rtl8192eu, it wouldn't guarantee to not overheat the adapter, buuut I could try an alternative OS on a separate SD card and see if
a) dwa-131 is supported
b) and if yes, does it overheat the A>C adapter
That alternative OS is not very good from my experience. But I will still do it for science!

Ok, so I tried an alternative OS, and it does support dwa-131, but it heats up the type A > type C adapter all the same, so it wouldn't matter. I guess I need to find a better adapter.
So if there are no plans of dwa-131 support, I guess the issue may be closed


Add clickhouse-ingress.md doc

In this PR, we add clickhouse-ingress.md document to guide user to set up Flow Aggregator and Ingress when they want to expose ClickHouse by using Ingress.

/theia-test-e2e


While building the UI Image, encounter Node version error

WHile running docker-compose build command, I am encountering following error,
ERROR: failed to solve: process "/bin/sh -c yarn install" did not complete successfully: exit code: 1 ERROR: Service 'conductor-ui' failed to build : Build failed
I think it is because yarn is expecting Node version > 16 in [/docker/ui/Dockerfile]()
Details
Conductor version: 3.13.6
Persistence implementation: N/A
Queue implementation: Postgres
Lock: Redis
Workflow definition:
Task definition:
Event handler definition:
To Reproduce
Steps to reproduce the behavior:

Go to '/deploy' directory
RUn command 'docker-compose build'
See error

Expected behavior
TO build the image without errors

answer at https://github.com/Netflix/conductor/issues/3674


Unable to install dlib by pip on Brew Python or to build from source (mac 10.12)

For pip install dlib, the errors are below
Collecting dlib
Using cached dlib-19.1.0.tar.gz
Building wheels for collected packages: dlib
Running setup.py bdist_wheel for dlib ... error
Complete output from command /usr/local/opt/python/bin/python2.7 -u -c "import setuptools, tokenize;file='/private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" bdist_wheel -d /var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/tmpw7DHX3pip-wheel- --python-tag cp27:
running bdist_wheel
running build
Detected Python architecture: 64bit
Detected platform: darwin
Configuring cmake ...
-- The C compiler identification is AppleClang <IP_ADDRESS>00042
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00042
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Warning at /usr/local/Cellar/cmake/3.7.1/share/cmake/Modules/FindBoost.cmake:744 (message):
Imported targets not available for Boost version 106300
Call Stack (most recent call first):
/usr/local/Cellar/cmake/3.7.1/share/cmake/Modules/FindBoost.cmake:848 (_Boost_COMPONENT_DEPENDENCIES)
/usr/local/Cellar/cmake/3.7.1/share/cmake/Modules/FindBoost.cmake:1435 (_Boost_MISSING_DEPENDENCIES)
/private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/dlib/cmake_utils/add_python_module:73 (FIND_PACKAGE)
CMakeLists.txt:6 (include)
-- Boost version: 1.63.0
-- Found the following Boost libraries:
--   python
-- Found PythonLibs: /usr/local/opt/python/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib (found suitable version "2.7.13", minimum required is "2.6")
-- USING BOOST_LIBS: /usr/local/lib/libboost_python-mt.dylib
-- USING PYTHON_LIBS: /usr/local/opt/python/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib
-- C++11 activated.
-- Enabling SSE4 instructions
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE
-- Looking for png_create_read_struct
-- Looking for png_create_read_struct - found
-- Looking for jpeg_read_header
-- Looking for jpeg_read_header - found
-- Searching for BLAS and LAPACK
-- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.29.1")
-- Checking for module 'cblas'
--   No package 'cblas' found
-- Checking for module 'lapack'
--   No package 'lapack' found
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of void*
-- Check size of void* - done
-- Found LAPACK library
-- Found CBLAS library
-- Looking for cblas_ddot
-- Looking for cblas_ddot - found
-- Found CUDA: /usr/local/cuda (found suitable version "8.0", minimum required is "7.5")
-- Looking for cuDNN install...
CMake Error at /private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/dlib/cmake_utils/test_for_cudnn/find_cudnn.txt:10 (get_filename_component):
get_filename_component unknown component
/usr/local/cuda/lib/libcublas_device.a
Call Stack (most recent call first):
/private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/dlib/CMakeLists.txt:462 (include)
-- Building a CUDA test project to see if your compiler is compatible with CUDA...
-- Checking if you have the right version of cuDNN installed.
CMake Error at /private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/dlib/cmake_utils/test_for_cudnn/find_cudnn.txt:10 (get_filename_component):
error: cmake configuration failed!

Failed building wheel for dlib
Running setup.py clean for dlib
Failed to build dlib
Installing collected packages: dlib
Running setup.py install for dlib ... error
Complete output from command /usr/local/opt/python/bin/python2.7 -u -c "import setuptools, tokenize;file='/private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-Q9g81O-record/install-record.txt --single-version-externally-managed --compile:
running install
running build
Detected Python architecture: 64bit
Detected platform: darwin
Removing build directory /private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/./tools/python/build
Configuring cmake ...
-- The C compiler identification is AppleClang <IP_ADDRESS>00042
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00042
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Warning at /usr/local/Cellar/cmake/3.7.1/share/cmake/Modules/FindBoost.cmake:744 (message):
Imported targets not available for Boost version 106300
Call Stack (most recent call first):
/usr/local/Cellar/cmake/3.7.1/share/cmake/Modules/FindBoost.cmake:848 (_Boost_COMPONENT_DEPENDENCIES)
/usr/local/Cellar/cmake/3.7.1/share/cmake/Modules/FindBoost.cmake:1435 (_Boost_MISSING_DEPENDENCIES)
/private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/dlib/cmake_utils/add_python_module:73 (FIND_PACKAGE)
CMakeLists.txt:6 (include)
-- Boost version: 1.63.0
-- Found the following Boost libraries:
--   python
-- Found PythonLibs: /usr/local/opt/python/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib (found suitable version "2.7.13", minimum required is "2.6")
-- USING BOOST_LIBS: /usr/local/lib/libboost_python-mt.dylib
-- USING PYTHON_LIBS: /usr/local/opt/python/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib
-- C++11 activated.
-- Enabling SSE4 instructions
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE
-- Looking for png_create_read_struct
-- Looking for png_create_read_struct - found
-- Looking for jpeg_read_header
-- Looking for jpeg_read_header - found
-- Searching for BLAS and LAPACK
-- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.29.1")
-- Checking for module 'cblas'
--   No package 'cblas' found
-- Checking for module 'lapack'
--   No package 'lapack' found
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of void*
-- Check size of void* - done
-- Found LAPACK library
-- Found CBLAS library
-- Looking for cblas_ddot
-- Looking for cblas_ddot - found
-- Found CUDA: /usr/local/cuda (found suitable version "8.0", minimum required is "7.5")
-- Looking for cuDNN install...
CMake Error at /private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/dlib/cmake_utils/test_for_cudnn/find_cudnn.txt:10 (get_filename_component):
get_filename_component unknown component
/usr/local/cuda/lib/libcublas_device.a
Call Stack (most recent call first):
/private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/dlib/CMakeLists.txt:462 (include)
-- Building a CUDA test project to see if your compiler is compatible with CUDA...
-- Checking if you have the right version of cuDNN installed.
CMake Error at /private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/dlib/cmake_utils/test_for_cudnn/find_cudnn.txt:10 (get_filename_component):
error: cmake configuration failed!
----------------------------------------

Command "/usr/local/opt/python/bin/python2.7 -u -c "import setuptools, tokenize;file='/private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-Q9g81O-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/
At first I got an error about CMAKE_PREFIX_PATH so I set it to /usr/local/cuda but I still the same error
CUDA & CUDNN certainly both exist in /usr/local/cuda/lib
libcublas.8.0.dylib@  libcufftw.dylib@	      libnppi.8.0.dylib@     libnppif_static.a@    libnpps.dylib@
libcublas.dylib@      libcufftw_static.a@     libnppi.dylib@	     libnppig.8.0.dylib@   libnpps_static.a@
libcublas_device.a@   libcuinj.8.0.dylib@     libnppi_static.a@      libnppig.dylib@	   libnvToolsExt.1.dylib@
libcublas_static.a@   libcuinj.dylib@	      libnppial.8.0.dylib@   libnppig_static.a@    libnvToolsExt.dylib@
libcuda.1.dylib@      libculibos.a@	      libnppial.dylib@	     libnppim.8.0.dylib@   libnvblas.8.0.dylib@
libcuda.dylib*	      libcurand.8.0.dylib@    libnppial_static.a@    libnppim.dylib@	   libnvblas.dylib@
libcudadevrt.a@       libcurand.dylib@	      libnppicc.8.0.dylib@   libnppim_static.a@    libnvgraph.8.0.dylib@
libcudart.8.0.dylib@  libcurand_static.a@     libnppicc.dylib@	     libnppist.8.0.dylib@  libnvgraph.dylib@
libcudart.dylib@      libcusolver.8.0.dylib@  libnppicc_static.a@    libnppist.dylib@	   libnvgraph_static.a@
libcudart_static.a@   libcusolver.dylib@      libnppicom.8.0.dylib@  libnppist_static.a@   libnvrtc-builtins.8.0.dylib@
libcudnn.5.dylib@     libcusolver_static.a@   libnppicom.dylib@      libnppisu.8.0.dylib@  libnvrtc-builtins.dylib@
libcudnn.dylib@       libcusparse.8.0.dylib@  libnppicom_static.a@   libnppisu.dylib@	   libnvrtc.8.0.dylib@
libcudnn_static.a@    libcusparse.dylib@      libnppidei.8.0.dylib@  libnppisu_static.a@   libnvrtc.dylib@
libcufft.8.0.dylib@   libcusparse_static.a@   libnppidei.dylib@      libnppitc.8.0.dylib@  stubs@
libcufft.dylib@       libnppc.8.0.dylib@      libnppidei_static.a@   libnppitc.dylib@
libcufft_static.a@    libnppc.dylib@	      libnppif.8.0.dylib@    libnppitc_static.a@
libcufftw.8.0.dylib@  libnppc_static.a@       libnppif.dylib@	     libnpps.8.0.dylib@
For build from source, the error is also around CUDA/CUDNN but it fails in nvcc
[  0%] Building NVCC (Device) object dlib_build/CMakeFiles/dlib.dir/dnn/dlib_generated_cuda_dlib.cu.o
nvcc fatal   : redefinition of argument 'std'
CMake Error at dlib_generated_cuda_dlib.cu.o.Release.cmake:222 (message):
Error generating
/repo/dlib/python_examples/build/dlib_build/CMakeFiles/dlib.dir/dnn/./dlib_generated_cuda_dlib.cu.o
make[2]: *** [dlib_build/CMakeFiles/dlib.dir/dnn/dlib_generated_cuda_dlib.cu.o] Error 1
make[1]: *** [dlib_build/CMakeFiles/dlib.dir/all] Error 2
make: *** [all] Error 2
FYI, I've just installed/built/ran Torch with nn support in last few days so CUDA & CUDNN both work fine.
Thanks for any help!

The error you get isn't about cuda, it's this:  CMake Error at /private/var/folders/j0/0zny89t96fn1zhn4r3bzjmk00000gn/T/pip-build-BrwHgk/dlib/dlib/cmake_utils/test_for_cudnn/find_cudnn.txt:10 (get_filename_component): get_filename_component unknown component
I'm not sure how that happens unless you have an ancient version of cmake that doesn't support get_filename_component.

Do you have multiple versions of cmake installled? One that's really old?  I would try building with cmake by itself and see what errors you get.

I just pushed a commit that should fix the redefinition of argument 'std' error.

I have brew cmake 3.71.  I could try build with cmake later.
Build from source now gets much farther - thanks!  But I get this.
[100%] Linking CXX shared library dlib.so
Undefined symbols for architecture x86_64:
"dlib::pixel_traitsdlib::rgb_pixel::num", referenced from:
void get_numpy_ndarray_parts<dlib::rgb_pixel, 3>(boost::python::api::object&, dlib::rgb_pixel*&, dlib::array<dlib::rgb_pixel, dlib::memory_manager_stateless_kernel_1 >&, long (&) [3]) in object_detection.cpp.o
void get_numpy_ndarray_parts<dlib::rgb_pixel, 3>(boost::python::api::object&, dlib::rgb_pixel*&, dlib::array<dlib::rgb_pixel, dlib::memory_manager_stateless_kernel_1 >&, long (&) [3]) in shape_predictor.cpp.o
void get_numpy_ndarray_parts<dlib::rgb_pixel, 3>(boost::python::api::object&, dlib::rgb_pixel*&, dlib::array<dlib::rgb_pixel, dlib::memory_manager_stateless_kernel_1 >&, long (&) [3]) in correlation_tracker.cpp.o
void get_numpy_ndarray_parts<dlib::rgb_pixel, 3>(boost::python::api::object&, dlib::rgb_pixel*&, dlib::array<dlib::rgb_pixel, dlib::memory_manager_stateless_kernel_1 >&, long (&) [3]) in gui.cpp.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [dlib.so] Error 1
make[1]: *** [CMakeFiles/dlib_.dir/all] Error 2
make: *** [all] Error 2

Hmm.  Try putting
constexpr auto num = dlib::pixel_traits<T>::num;
at line 151 in dlib/python/numpy.h and then replace all the references to pixel_traits::num with the locally declared num.

Try the latest code.  I think this might be fixed now.

That did it.  Thanks!

No problem :)

I have been trying to install dlib on virtual machine(UBUNTU 16.04 LTS) but the machine hangs after running setup.py file (from https://github.com/davisking/dlib). It executes till 79% and then nothing happens and eventually machine stops to work.

Please help me to install dlib for python 2.7

Maybe you are running out of RAM.  But in any case, if GCC crashes your computer it isn't because of dlib.

Thanks davisking, increasing RAM worked.
But I am again stucked!
While running a face detection python file,
Traceback (most recent call last):
File "detect.py", line 9, in
face_detector = dlib.get_frontal_face_detector()
AttributeError: 'module' object has no attribute 'get_frontal_face_detector'
I just installed dlib and then tried running the file in virtual environment. Please help me!

Thnaks davisking, increasing RAM helped me.
But I am again stucked into a problem.
While running face detection python file on ubuntu but i get the following error -
Traceback (most recent call last):
File "detect.py", line 9, in
face_detector = dlib.get_frontal_face_detector()
AttributeError: 'module' object has no attribute 'get_frontal_face_detector'
please help!


Emoji generator final

Now i have fixed all emoji's ,i have used random to place one set of eyes, nose, mouth, i even created graaph of sinx for one of the mouths so now i think i cant add anything else so please approve.
thank you
![Screenshot 2023-12-27 103910]

(https://github.com/hackclub/blot/assets/86531335/155ac8f2-b33f-43bb-b5ee-49ce7b0852e7)

These look a bit too much like collections of lines and polygons instead of emojis.
This example shows using similar primitive shapes but in a way where the overall picture being drawn starts to come out more.

One feature that contributes to this is the placement of the eyes being very high and the mouth and nose sometimes being misaligned. I also think all of the facial features may look better as outlines to give some thickness to them instead of a single stroke.


\Fruitcake\Cors\ServiceProvider does not exist in package

According to vendor/fruitcake/laravel-cors/src/CorsServiceProvider.php the readme is referencing a file which has been renamed to CorsServiceProvider.php.

Thanks, updated in https://github.com/fruitcake/laravel-cors/commit/719be21aa7ba9ac0e48b273e71bb2886b80e868e


Support []string and []*string as sensitive fields

What problem are you facing?
Tring to generate a CRD with sensitive field type []*string fails with:
panic: cannot generate crd: cannot build types for User: cannot build the types: got type "[]*string" for field "Passwords", only types "string" and "*string" supported as sensitive

config.Store.SetForResource("aws_elasticache_user", config.Resource{
		ExternalName: config.ExternalName{
			DisableNameInitializer: true,
		},
		Sensitive: config.Sensitive{
			CustomFieldPaths: []string{
				"passwords", // interestingly this field is not marked as sensitive in tf schema
			},
		},
		UseAsync: true,
	})

How could Terrajet help solve your problem?
Support []string and []*string as sensitive fields

In GCP, I got the following for google_storage_bucket_object:
panic: cannot generate crd for resource google_storage_bucket_object: cannot build types for BucketObject: cannot build the Types: got type "[]github.com/crossplane-contrib/provider-tf-gcp/apis/storage/v1alpha1.CustomerEncryptionParameters" for field "CustomerEncryption", only types "string" and "*string" supported as sensitive

However, I believe this is different than the above cases since here as struct type is marked as sensitive. I think it would be enough/safe just to ignore it as long as the parameters of the struct are marked as sensitive, which we would need to handle indeed.

@turkenh are you planning to support map[string]*string as well?


Workaround for cut context menu

Resolved / Related Issues
Items resolved / related issues by this PR.

Alternative workaround for issue #5555

Details of Changes
Add details of changes here.

Current workaround for #5555 is to set the context menu AppBarButtons MinWidth to a large value. This results in a context menu being always large. This solution only sets MinWidth if needed.

Validation
How did you test these changes?

[x] Built and ran the app

@gave92 can you resolve the merge conflict?


xplat: remove --with-intl argument

@dotnet-bot test Windows x64_release please

I just remembered on this, aren't CI changes supposed to be made to master-ci? @MSLaguana @dilijev

master-ci is a branch where we can test CI changes, but the changes themselves need to be made to the appropriate branch.


Ditch django_compressor in favour of a Node-based bundling setup

As of version 2.0, django_compressor now depends on the packages rjsmin and rcssmin, which include native extensions and are thus non-trivial to install on Windows (see https://groups.google.com/d/msg/wagtail/-CDQcHk5F9M/aL_DbhjdCQAJ). Additionally, there have been reports of bugs in rjsmin's compression (specifically, SimpleMDE uses the regex /^ *-+:*$/ which rjsmin incorrectly compresses to /^*-+:*$/), and our current django_compressor setup doesn't allow specific addons/apps using the insert_editor_js hook to opt out of compression. Finally, it's an extra thing that end users of Wagtail need to configure (or at least, be aware of) when deploying.
The main reason for using django_compressor (SASS compilation) has already been superseded by our Node toolchain, and minification/bundling is something else that could certainly be done just as well (or better) through Node. The one thing we'd lose would be the dynamic 'discovery' of bundled assets based on {% compress %} tags - and thus the ability for third-party modules to insert themselves into those bundles via insert_editor_js - but it's probably a good thing for maintainability for our bundles to be defined statically in a gulp config (or similar), and for third-party modules to deal with minification themselves if they consider it important.

See also #1143

This may be a little out of date, however, for people that would still like to use django-compressor in Windows, I'd like to point out that you can easily install it using the --install-option="--without-c-extensions" pip parameter:
(venv) C:\progr\py\test>pip install --install-option="--without-c-extensions" django-compressor
You are using pip version 6.1.1, however version 8.0.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Collecting django-compressor
  Using cached django_compressor-2.0-py2.py3-none-any.whl
Collecting django-appconf>=0.4 (from django-compressor)
  Using cached django_appconf-1.0.1-py2.py3-none-any.whl
Collecting rcssmin==1.0.6 (from django-compressor)
  Using cached rcssmin-1.0.6.tar.gz
Collecting rjsmin==1.0.12 (from django-compressor)
  Using cached rjsmin-1.0.12.tar.gz
Collecting six (from django-appconf>=0.4->django-compressor)
  Using cached six-1.10.0-py2.py3-none-any.whl
Installing collected packages: six, django-appconf, rcssmin, rjsmin, django-compressor
  Running setup.py install for rcssmin
  Running setup.py install for rjsmin
Successfully installed django-appconf-1.0.1 django-compressor-2.0 rcssmin-1.0.6 rjsmin-1.0.12 six-1.10.0

This is just for completeness, I also think that moving to node-js tools for building your js/css is the way to go :+1:

This is awesome. Thanks so much for your great work on this! :+1:  Any idea when this will make it into a release? (I was having some issues with django-compressor in my docker-based deploy setup, so right now I'm pulling and building master from github :open_mouth: )

Fixed in #2132


Snap

Why Snap?
Snap is a proprietary service, that is only accessible through the proprietary service from Canonical.
Since people who are using Linux, especially developers, are doing so since they love to embrace the open-source principles, does it sound weird to choose from multiple possible options the only one that is specifically non-free.
This seems contrary to the aim, to bring .Net to all platforms since this distribution tactic does not go well with a significant amount of contributors.
My distribution does not support snap at all.
General
Alternatives are Flatpak, AppImage, and Guix, less accessible and known ones, like: pkgsrc, Nix, Habitat and even systemd itself.
So from 5 or more valid options, does .Net use the only one that depends on a non-free service.
I dont get it.
A vast majority of the distributions do provide years-old and very outdated versions of .Net, since this is part of their "release strategy" and so, they are more or less chanceless to install any of the products without using a non-free service or compiling on their own.
This excludes a part of the community.
Is the most popular option (seemingly) the most sane one or maybe just that one with the highest marketing budget?

cc @leecow @rbhanda for that feedback
@ShalokShalom what distro are you using?

Speaking as a Fedora developer, I am not sure .NET (Core) is suitable for Flatpak on Linux. I spoke to some Flatpak developers and Flatpak is all about running graphical applications. That's not a use case supported by .NET (Core) on Linux really. The Flatpak developers suggested that if we want to develop/deploy server-like applications, containers (docke/podman) are a better fit than Flatpak.

cc @leecow @rbhanda for that feedback
@ShalokShalom what distro are you using?

KaOS


[App]: define_metrics does not work with media type keys

Current Behavior
Assume the following code:
        wandb.define_metric("custom_step")
        wandb.define_metric("image_0", step_metric='custom_step')
        wandb.log(
            {
                'custom_step' : steps,
                'image_0': wandb.Image(image),
            }
        )

Then wandb can't show the custom metric vs media type plot, it will show with default step (current wandb step) instead.
Expected Behavior
        wandb.define_metric("custom_step")
        wandb.define_metric("metric_0", step_metric='custom_step')
        wandb.log(
            {
                'custom_step' : steps,
                'metric_0' : 0,
            }
        )

this works well.
Steps To Reproduce
Define the custom metric with the code above, then try to log the images, to see plotted image against custom metrics.
Screenshots
No response
Environment
OS: Linux / Windows *all
Browsers: Chrome / Microsoft Edge
Version: 0.15.12
Additional Context
Related : https://github.com/wandb/wandb/issues/6077

Internal GitHub User commented:
Current Behavior
Assume the following code:
        wandb.define_metric("custom_step")
        wandb.define_metric("image_0", step_metric='custom_step')
        wandb.log(
            {
                'custom_step' : steps,
                'image_0': wandb.Image(image),
            }
        )

Then wandb can't show the custom metric vs media type plot, it will show with default step (current wandb step) instead.
Expected Behavior
        wandb.define_metric("custom_step")
        wandb.define_metric("metric_0", step_metric='custom_step')
        wandb.log(
            {
                'custom_step' : steps,
                'metric_0' : 0,
            }
        )

this works well.
Steps To Reproduce
Define the custom metric with the code above, then try to log the images, to see plotted image against custom metrics.
Screenshots
No response
Environment
OS: Linux / Windows *all
Browsers: Chrome / Microsoft Edge
Version: 0.15.12
Additional Context
Related : https://github.com/wandb/wandb/issues/6077

Hi @aria1th ,
Thank you for writing in, we will review the codes you provided and will get back to you.

Hello @aria1th ,
Yes, it's true. Weights & Biases uses the internal step counter as the default x-axis for your plots. If you want to use a custom metric as the x-axis, you can use the wandb.define_metric function to specify the metric you want to use as the x-axis. However, this only applies to scalar metrics and not media types.
We can also create a feature request for this case if you would like.

@JoanaMarieL Thank you for the reply!
Sure, the feature would be great. We can think about some asynchronous inference while training is running background.
(Also, inference can go slow, so it may end after actual training is done... but currently if we end the training, there is no way to attach media results. Are there way to bypass this?)

Hi @aria1th ,
I would like to clarify the last statement, do you mean to attach the media results after the actual training end?

@JoanaMarieL Yes, I once tried to attach results after end of training - for example, I assigned the thread to call the inference, but since accelerator.end_training() was called before inference end the stuff, it was not able to attach results.
Of course the best solution is to not call end_training if inference is not done, but if some bypass behaviors / queue / reservation is available, it would be far convenient.

@aria1th , can you give this a try:
by resuming run:  [https://docs.wandb.ai/guides/runs/resuming#resume-guidance]
You can resume then add media results or upload them as artifacts to the same run.
It works like this:
start a run and log
run = wandb.init(entity, project)
run.log(...)
run_id = run.id
run.finish()

resume the run run_id anytime and log more data

run = wandb.init(entity, project, id= run_id, resume='must')
run.log(..)
run.finish()

@JoanaMarieL I'm using the following code in accelerator environment, but seems there is some problem:
        global run_id
        if run_id is None:
            run_id = wandb.run.id
        # resume if stopped
        wandb.init(id=run_id, resume="must")

This function is called every inference. Somehow, the first inference (with run didn't finish) worked, but later ones didn't work - it had problem while waiting wandb.init(id=run_id)
Actually, it failed to resume the run as I checked -

I tested if resume works with "allow", "must", but seems like it didn't work, it has thrown error after 90 seconds.

Full code snippet:
import wandb
wandb.login(key=wandb_api_token)

# 2. Start a new run
wandb.init(project='test')

run_id = wandb.run.id

run = wandb.run

run.log({'acc': 0.9, 'loss': 0.2}) #test

run.finish()

run = wandb.init(id=run_id, resume="allow") # throws CommError

@aria1th , let us review the information provided and will get back to you.

Hi @aria1th ,
please try to modify this part by adding entity and project like this: [wandb.init(entity="entity_name",project='proj',name="test")]
# 2. Start a new run
wandb.init(project='test')

let us know the result after you try again

@JoanaMarieL Thanks for the response!
I successfully resumed the run and logged the metrics with the following code snippet:
import wandb
wandb.login(key=API_KEY)

wandb.init(entity="user_name",project='proj_test',name="test_name")

wandb.log({'acc': 0.9, 'loss': 0.2}) #test

args = run.project, run.entity, run.name, run.id

run.finish()

# Note, this may interrupt main training process run - so we need to check 'finished' before calling this

run = wandb.init(resume="must", project=args[0], entity=args[1], name=args[2], id= args[3])

run.log({'acc': 0.9, 'loss': 0.2}) #test

run.finish()

Unfortunately, media types are not available with custom steps - which is the only problem.

Hello @aria1th
We're glad that this works now for you. And as for the custom steps using Media Types, we will file this as a Feature Request. For now we will mark this as resolved. Feel free to reach us out again for any concerns.

@JoanaMarieL Thank you for the information!
Custom steps for media types would indeed be very useful!
In the meantime it'd be great to add a note in the documentation, indicating that the step_metric  argument of define_metric only works for scalar type metrics. I ran into this issue and was investigating whether the run was maybe not syncing properly.

Thank you for flagging @vmichals , we'll definitely include this to our documentation.


⚠ Bofrost.com has degraded performance

In 29ae46c, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1063 ms

Resolved: Bofrost.com performance has improved in cf3f9d1 after 6 minutes.


pkgsStatic.laminar: fix build

Add "capnproto" into nativeBuildInputs so build system has access to capnp(1).

btw on next bump consider fixing the version number:
result/bin/laminarc --help
laminarc version xx-unversioned


Add Flysight V2 Support

TODO:

[x] Parse device track information
[x] Parse device sensor information
[ ] Ensure separate pathways are available for both V1 & V2 devices
[ ] Testing, testing, we love testing

Closes: #8

I don't know why mypy is failing, I'm assuming some CI build oddity since local is fine


ForEach-Object -Parallel: consider changing the semantics of the -TimeoutSeconds parameter to apply to each thread or provide a new switch / parameter that does

Summary of the new feature / enhancement
The current semantics of the -TimeoutSeconds parameter are arguably unhelpful:

The -TimeoutSeconds interval is applied to the runtime duration of the overall, typically throttled and therefore "batched" invocation[1] rather than to the runtime of each thread.

Therefore, a timeout can occur even if each individual thread completed in less than the specified timeout. A simple example:

          # This times out when the 3rd thread runs, because - due to ThrottleLimit 2 -
          # it only starts after 1.5+ seconds, after the first 2 threads
          # have finished.
          1..4 |
            ForEach-Object -TimeoutSeconds 2 -ThrottleLimit 2 -Parallel {
              Start-Sleep -MilliSeconds 1500
              $_ # Pass the input object through.
            }

When a timeout occurs, the command terminates overall.

This means that threads for any remaining pipeline input then never even get to launch.

In the above example, only 1 and 2 print; input 4 never gets processed, because processing of 3 caused the timeout and therefore termination of the entire command.

Applying the specified timeout:

on a  per-thread basis...
... and continuing processing of the inputs even if a single thread times out

is arguably much more sensible.
Therefore, I suggest implementing the latter:

Either:  By simply  changing the meaning of the current -TimeoutSeconds parameter, assuming it amounts to a bucket 3 change.

Or:  By introducing a separate parameter / additional switch parameter as an opt-in to the proposed semantics.

[1] More accurately, only a fixed number of threads are allowed to run at a time, based on the -ThrottleLimit arguments, which defaults to 5. If more threads are needed, they have to wait until "slots" open up, which happens when currently executing threads finish.
Proposed technical implementation details (optional)
The following shows the desired semantics expressed in PowerShell code, applied to a slightly modified version of the example above, which provokes a timeout for the 3rd input object:
# Use -AsJob to receive a job that allows monitoring the threads individually.
# Note that -AsJob cannot be combined with -TimeoutSeconds
$job =
  1..4 |
    ForEach-Object -AsJob -ThrottleLimit 2 -Parallel {
      if ($_ -eq 3) {
        # Provoke a timeout error for this specific input.
        Start-Sleep -MilliSeconds 2500; $_
      } else {
        Start-Sleep -MilliSeconds 1500; $_
      }
    }

# Receive job output in a polling loop, and terminate child jobs
# that have run too long.
$timeout = 2
do {
  Start-Sleep -Milliseconds 500 # Sleep a little.
  # Get pending results.
  $job | Receive-Job
  # If any child jobs have been running for more than N seconds,
  # stop (terminate) them.
  # This will open up slots for more threads to spin up.
  foreach ($childJob in $job.ChildJobs.Where({ $_.State -eq 'Running' })) {
    if (([datetime]::now - $childJob.PSBeginTime).TotalSeconds -ge $timeout) {
      Write-Verbose -Verbose "Stopping job with ID $($childJob.Id) due to running longer than $timeout seconds..."
      $childJob | Stop-Job
    }
  }
} while ($job.ChildJobs.Where({ $_.State -in 'NotStarted', 'Running' }))

Output:
1
2
4
VERBOSE: Stopping job with ID 4 due to running longer than 2 seconds...

Note:

Input 4 was still processed, despite the thread for input 3 having timed out.

The ID value of the child job isn't really meaningful except to distinguish it from other child jobs; if you want to know what input object caused the timeout, you'll have to echo it as part of the script block (at the start, before a timeout can occur) - the job object doesn't contain this information.

Or:  By introducing a separate parameter / additional switch parameter as an opt-in to the proposed semantics.

This seems like a useful addition.  I think people want timeout for each, and aggregate time out.

#18027


Sending mails via sendgrid not working

Hello,
I am trying to send alerts via SendGrid. However, it doesn't work for some reason. Here are the last log entries from switchboard.log:
2022-09-30T14:00:44+0000 [channel_dns#info] Query: <TRIGGERING_IP> sent <Query <DNS_TOKEN_URL> A IN>
2022-09-30T14:00:44+0000 [channel_dns#info] Unable to format event {'log_namespace': 'channel_dns', 'log_level': <LogLevel=info>, 'log_logger': <Logger 'channel_dns'>, 'log_time':<PHONE_NUMBER>.738958, 'log_source': None, 'log_format': {'src_ip': '<TRIGGERING_IP>', 'src_data': {}}}: Log format must be unicode or bytes, not {'src_ip': '<TRIGGERING_IP>', 'src_data': {}}
2022-09-30T14:00:44+0000 [switchboard#error] Exception occurred in switchboard dispatch:
2022-09-30T14:00:45+0000 [channel_dns#info] Query: <TRIGGERING_IP> sent <Query <DNS_TOKEN_URL> AAAA IN>

This is my switchboard.env:
#CANARY_MAILGUN_DOMAIN_NAME=
#CANARY_MAILGUN_API_KEY=
#CANARY_MANDRILL_API_KEY=
CANARY_SENDGRID_API_KEY="<SENDGRID_API_KEY>"
CANARY_PUBLIC_IP=<CANARY_PUBLIC_IP>
CANARY_PUBLIC_DOMAIN=<CANARY_PUBLIC_DOMAIN>
<EMAIL_ADDRESS><EMAIL_ADDRESS>CANARY_ALERT_EMAIL_SUBJECT=SubjectLine
#CANARY_IPINFO_API_KEY=

CANARY_TOKEN_RETURN=fortune

CANARY_WEB_IMAGE_UPLOAD_PATH=/uploads

LOG_FILE=switchboard.log

# Default protocol to use in notification links. If you don't use LetsEncrypt, set to http
PROTOCOL=https
ERROR_LOG_WEBHOOK=
CANARY_WG_PRIVATE_KEY_SEED="<CANARY_WG_PRIVATE_KEY_SEED>"

The token gets triggered properly, I checked that.
Do you have any ideas?

Edit: The API key works when it's being used with curl

Edit 2: The sender mail matches the one registered in SendGrid. It's the same one I used for the curl requests, where it worked

Hi @gearanach,
Thanks for reporting this issue. Just a quick check. Are you still experiencing this issue? Did you try using:
CANARY_SENDGRID_API_KEY=<SENDGRID_API_KEY>

without the '' (quotes).
Please also note we have made some big changes for canarytokens. So please pull the latest code before trying again

Hi @jayjb
it's been fixed, though I don't remember how we did it.
Kind regards,
Gearanach


render should not fail silently

It would be a big help with debug if render would not fail silently, but instead simply print the exception raised etc.
Perhaps this is some setting in reactjs?  Otherwise I am thinking that we could add a method render_debug to the component class, which calls render and prints any error message.
render_debug would be called by the API if it was available AND some kind of config switch was set.

added this to my currently open PR

@catmando I'm assuming this has long since been implemented, so I'll close it. Reopen if not.

This issue was moved to reactrb/reactrb#34


Update on susie break the code

The merging of genoFile and phenoFile and many subsequent operation depends on the colnames. Setting header = 0 will produce error. WIll add fix header to pd.read_csv when have time
genoFile = pd.read_csv(genoFile, sep = "\t", header=0)

if len(phenoFile) != len(covFile):
    raise ValueError("Number of input phenotypes files must match that of covariates files")
if len(phenoFile) != len(phenotype_names):
    raise ValueError("Number of input phenotypes files must match the number of phenotype names")
## pos and covar are condition specific, this way when there is no phenotype file, there is na in the corresponding column.
phenoFile = [pd.read_csv(x, sep = "\t", header=0).assign(pos = lambda y:y['#chr']+':'+y['start'].astype("str")+'-'+
                                              y['end'].astype("str")).assign(cov_path = z, cond = a ).drop(columns = ["#chr","start","end"]).rename(columns = {"ID":"#id"})
             for x,z,a in zip(phenoFile,covFile,phenotype_names)]
for i in range(len(phenoFile)):
    genoFile = genoFile.merge(phenoFile[i], on='#id', how='left', suffixes = (f'{i}_x', f'{i}_y'))

Mistaken on the behavior of pd.read_csv, i thought header = 0 is the same as header = False

This commit still break thing, so I will reopened the ticket
https://github.com/cumc/xqtl-pipeline/commit/cbbc77a6bd5e6d32e9da1be92113530e321ddea8

Fixed.


Failed to validate domain.yml - intents are true/false?

Rasa Core version: 0.11.8
Python version: 3.6.6
Operating system (windows, osx, ...): Windows
Issue:
When running the command:
python -m rasa_core.train -d domains/domain.yml -s stories/story.md -o models/model_test/dialogue --epochs 200
an error appears stating that my domain.yml file couldn't be validated and that there is a schema error.
I've attached the error message, my domain file, data file, and stories file. I had to change the file type to upload them, I have them as yml for domain and md for the others.

domain.txt
story.txt
data.txt

I will add that this doesn't seem to stop the intents from triggering

Thanks for raising this issue, @MetcalfeTom  will get back to you about it soon.

Hi!  Thanks for uploading the data, I think I have found the problem.
Could you try renaming the intents yes and no to mood_affirm and mood_deny in all three of your data files?  You can keep the training examples in data.md, just rename the intent label.

Thanks that fixed it! So just to clarify, are "yes" and "no" key words or something? So it gets confused when I use them?

Great to hear!
Exactly that - the problem is that YAML automatically maps a bunch of strings (like on, off, yes, no) to boolean values

Issue:
When running the command: python train_online.py
i am getting following error. Please help me to fix this:
In most other cases you should consider using 'safe_load(stream)'
data = yaml.load(stream)
ERROR:pykwalify.core:validation.invalid
ERROR:pykwalify.core: --- All found errors ---
ERROR:pykwalify.core:[u"Value '-location' is not a list. Value path: '/entities'"]
Traceback (most recent call last):
File "train_online.py", line 39, in
run_weather_online(nlu_interpreter)
File "train_online.py", line 25, in run_weather_online
action_endpoint=action_endpoint)
File "/usr/local/lib/python2.7/dist-packages/rasa_core/agent.py", line 198, in init
self.domain = self._create_domain(domain)
File "/usr/local/lib/python2.7/dist-packages/rasa_core/agent.py", line 636, in _create_domain
return Domain.load(domain)
File "/usr/local/lib/python2.7/dist-packages/rasa_core/domain.py", line 89, in load
return cls.from_yaml(read_file(filename))
File "/usr/local/lib/python2.7/dist-packages/rasa_core/domain.py", line 93, in from_yaml
cls.validate_domain_yaml(yaml)
File "/usr/local/lib/python2.7/dist-packages/rasa_core/domain.py", line 129, in validate_domain_yaml
raise ValueError("Failed to validate your domain yaml. "
ValueError: Failed to validate your domain yaml. Make sure the file is correct, to do sotake a look at the errors logged during validation previous to this exception.

my domain.yml file is :
slots:
location:
type: text
intents:

greet
goodbye
inform_ct

entities:
-location
templates:
utter_greet:
- 'Hello! How can I help?'
utter_goodbye:
- 'Talk to you later.'
- 'Bye bye :('
utter_ask_keyword:
- 'Please give keywords'
actions:

utter_greet
utter_goodbye
utter_ask_keyword
action.ActionWeather
utter_ct


GmsCore not installable due to microG GMS

I am unable to install GmsCore since I already have it installed for MicroG, which yt revanced doesn't pick up

Got it to work by installing it via ADB


give an uniform check for release process

give an uniform check for release process, fixed #2538

This change is


Multiple random reaction responses

Try4se "if we say thanks ninbot, I think it should say you're welcome or no problem or a random thing from the list meaning that"

just add a list of positive, thankful responses and a list of negative, spiteful responses and pick one at random whenever someone says good bot or bad bot respectively


Parker/issue 513/use snippets in benefits table

Do you think you'd also be able to update the google docs when this is finalized?

@knod I agree - my comments were very minor to begin with and I didn't mean for the dollar sign thing to turn into a long discussion! In any case it should be easy enough to make the pre- and post-number snippets whatever they need to be in each language to get the desired result.
(Although looks like now this has merge conflicts that need resolving.)

I can clean this up at the end of the afternoon today or during the meeting tonight.

I rebased on dev and fixed the whitespace mistake you pointed out.

Looks like there's a problem with the package-lock.json (in this and some other PRs). Can you try deleting that file, running npm install to regenerate it, and committing the result?

@ethanbb : With past experiments, that doesn't fix the problem with package-lock.json because of all the npm nonsense. You end up having to basically undo the changes. Usually I'd say just go back to dev and redo the changes, but someone else had this problem and I ended up looking it up. This is approximately what I found, though I haven't gotten a chance to test it yet:

Be on your branch and make sure you don't have any other changes right now
git checkout -b test-fix (to make a new branch to test out whether this will work)
git fetch upstream-name-you-have dev
git checkout upstream-name-you-have/dev -- package-lock.json
git add package-lock.json
git commit
If that works, do it on the actual PR branch.

Got some of this from https://stackoverflow.com/a/215731.
Tell me how it goes!

@knod Ah makes sense. Although supposedly this PR doesn't modify package-lock.json, so couldn't it be the file on dev that's broken?
As a data point, my PR that involved installing some new packages is now working in Travis. So hopefully at least it's a transient issue.

@ethanbb : I did an npm install for dev locally and pushed it to the CfB repo. That seemed to fix it. That does need to be pulled in here.

Oh, there are two approvals! Nevermind, I'll just merge then.