Path bug + lintfile() should throw an error when a file is not found

Currently if the lintfile() method does not find a file, this is silently ignored and it seems like the file contains 0 errors. This should not be the case. If a file is not found, an error should be thrown specifiying the failing file path.
You might wonder how it might not be able find a file, since the file list is build from a glob pattern. Well I think this is a bug (although maybe not an easy one to solve).
Suppose have you the following file structure:
package.json
src/
src/tsconfig.json
src/**/*.ts

package.json contains the following script:
"tslint": "tsconfig-lint --use-glob src"

tsconfig contains the following glob pattern:
"filesGlob": "**/*.ts",

this results in file entries like
    "files": [
        "./form/dropdown/scripts/dropdown.ts",
        "./form/modal-popup/scripts/modal-popup-controller.ts",

But the current working dir for tsconfig-lint is the root folder (where package.json is located) and not 'src' so none of the files is found by the linter.
I was able to solve this by putting tsconfig.json also in the root folder, but had to dig into the code to figure out why it was not working. So getting an error, specifying that a file was not found would make this more obvious.
A fix for the path issue would of course be better. The paths are now relative to the location of tsconfig.json and this works fine for tsc, but not for the linter (which should also use the location of tsconfig as CWD).

The right solution is to fix the path issue, I will look into that. As for the file not found issue, that is a little bit more tricky to determine, but I'll see what I can do.

This is in<EMAIL_ADDRESS>


Don't assume one return means function can be inlined. (#2018)

We might need to consider the case where a return is inside of a selection construct.  for example
OpFunction
...
OpSelectionMerge %m
OpBranchConditional %true %bb %m
%bb = OpLabel
OpReturn
%m = OpLabel
OpUnreachable
...
OpFunctionEnd

If that is the only return, then inlining will generate invalid code as well.

Sorry. I missed this comment. Will respond shortly.

Changed to WIP. I am going to add a couple test cases.
Note changes to a couple existing tests: these do not require a single-trip loop wrapper and under the new regime, the loop is no longer generated.

Looks like the CI site went down. I can't look at any results, passing or failing. When I can look at passing results, I will resubmit.


[META] Facilitate operational Drupal scripts

"Operational" scripts such as installation, update, and search indexing of a Drupal site are some of the mostly commonly run tasks after the main build process, and so far we've artfully dodged any acknowledgement of them in this toolchain.
Benefits of a Grunt Connection

grunt help would be a central list of all standardized practice CLI tools for a project.
--timer and other instrumentation built into grunt would be applicable.
Easier integration with other sets of tasks, such as a single command to build & install, or a watch task that re-indexes search.
Potential standardized interface for common development tasks across projects.
Detection of a default drush alias (depending on implementation, could also be done in Bash)

How Scripts are Implemented
Since we have the goal of keeping GDT (and node in general) from becoming a production requirement, I don't think we should re-implement these sorts of operations as grunt tasks. Instead, for general portability I think these should be open-ended shell scripts for ease of implementing any given procedure.
By wrapping some simple scripts in a general grunt-shell wrapper, we can produce some default scripts and lean on the Drush alias for some of the basic customization. Longer-term, I think we'll want to use #35 (yeoman generator) to initialize scripts and possibly a drush alias file for the project in a way that can be customized later.
Example Install Script
Command
grunt install

bin/install.sh pseudo-code
drush $ALIAS site-install -yv
drush $ALIAS uli

Next Steps

Add a bin/ directory to the examples folder with a basic install and update script
Create a bootstrap script that sets up some common parameters and auto-detects a Drush alias

Uses the parent directory name of the code repository as a default alias. So if grayside.example.com/code-repo/Gruntfile.js is the path to the gruntfile, the alias assumed would be @grayside.example.com.

Add a task to load the contents of a bin/ directory as grunt tasks. This should include default descriptions for all tasks loaded this way, with a general fallback for tasks not explicitly described.

I had the sudden insight that:

Alias detection should be pluggable, with a few default options like "hostname" or "parent directory", but ultimately the ability for project implementations to specify it via code in the Gruntfile.
GDT should move the shell shiv into active code with a similar model of pluggable script detection. A few key things will be passed as arguments to the scripts, such as the drush alias.
Go forth and set up initial scripts in https://github.com/phase2/generator-gadget.

Closing old issues that I do not expect to be tackled in the context of this project.


No option to match dots

Minimatch's options param is not exposed, so right now copy-webpack can't ignore files like '.eslint' using a pattern like '*/'
function shouldIgnore(pathName, ignoreList) {
  var matched = _.find(ignoreList, function(glob) {
    return minimatch(pathName, glob, {
      matchBase: true,
      dot: true
    });
  });

@kevlened,
Could you expose this option? I'd like to include files prefixed with a dot.
Thank you!


Migration guide: Testing asynchronous error handling

Documentation Related To Component:
https://github.com/ReactiveX/rxjs/blob/master/docs_app/content/guide/v6/migration.md
Please check those that apply

[ ] typo
[ ] documentation doesn't exist
[X] documentation needs clarification
[X] error(s) in example
[ ] needs example

Description Of The Issue
Regarding this example code:
it('should emit an error on subscription', (done) => {
  source$.subscribe({
    error(err) {
      expect(err.message).toEqual('some message');
    }
  });
});

The done function is mentioned but not used. It should be called at least:
it('should emit an error on subscription', (done) => {
  source$.subscribe({
    error(err) {
      expect(err.message).toEqual('some message');
      done();
    }
  });
});

This would work, but there is still the problem that this test times out instead of failing instantly when the Observable emits a value instead of throwing an error.
In Jasmine, something like this would be better, wouldn’t it?
it('should emit an error on subscription', (done) => {
  source$.subscribe(
    done.fail,
    (err) => {
      expect(err.message).toEqual('some message');
      done();
    }
  });
});

Due to the creation date and missing responses for so long, I assume we can close this one.
@cartant please let me know if I'm wrong

@biophoton If the problem is still there and hasn't been addressed, we should fix it. The lack of responses should just been seen as people being busy with other, higher-prioriity tasks, that's all.

Thx @cartant!
Just to make it clear, my intention here is not to put pressure in it. What I try is find old issues that could get closed.
I will consider your answer in further comments! 🙏🙏🙏❤


Dev branch

Overview

add telemetry support
filter sniffer from being sniffed
several corrections while testing it

Additional Information

Any additional information that may be useful for reviewers to know
-->

Also, I'm failing to understand what in this code blocked you from delivering the first version of it for testing.
Please point me toward the bugs you had and how you fixed them.
I did not detect any unitests added that indicate a bug has been fixed.


Python: Support DefaultAzureCredential for AzureAI Inference

Motivation and Context
In recent work, the DefaultAzureCredential path was added for AzureOpenAI, but was missed for AzureAI inference.

Description
Adding support for default azure credential for AzureAI inference and its tests.

Contribution Checklist

[X] The code builds clean without any errors or warnings
[X] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[X] All unit tests pass, and I have added new tests where possible
[X] I didn't break anyone :smile:

Python Unit Test Overview

Tests
Skipped
Failures
Errors
Time

2428
1 :zzz:
0 :x:
0 :fire:
1m 32s :stopwatch:


[FEATURE] Remove deprecated allow-node-drain-with-last-healthy-replica

After discussing with @PhanLe1010 and @khushboo-rancher . Let's make a conclusion for this and this will apply for any deprecation case.

Keep node-drain-policy and allow-node-drain-with-last-healthy-replica together for 1.3.3 and 1.4.2, because we will not prefer removing an existing function from any patch release. However, need to emphasize the below items:

There is an overlapping between both. allow-node-drain-with-last-healthy-replica has been deprecated in 1.3.3 and 1.4.2, so encourage users to use node-drain-policy.
allow-node-drain-with-last-healthy-replica will be respected first for compatibility.

Any deprecated feature will be removed from the next feature release, so allow-node-drain-with-last-healthy-replica will be removed from 1.5.0.

Originally posted by @innobead in https://github.com/longhorn/longhorn/issues/5549#issuecomment-1477313619

cc @longhorn/qa

@PhanLe1010 Need to update the doc or related test cases as well.

@PhanLe1010 Need to update the doc or related test cases as well.

PR was created https://github.com/longhorn/website/pull/719 @innobead

@PhanLe1010 merged. Let's move to ready-for-testing if all ready. Thanks.

Under testing, will keep update the result in this comment
Environment

Longhorn version: v1.5.0-rc1

cluster info

K8S version: v1.25.9 +rke2r1
master1 + worker3

Test steps
Scenario 1: The setting allow-node-drain-with-last-healthy-replica is not exist

Fresh installation with Helm
- [PASS, 20230606] verify the setting is gone

Upgrade with kubectl command
- [PASS, 20230606] verify the setting is gone


fix: use installed version of lint-staged

I'm not getting this in VSCode 🥹
 ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command "lint-staged" not found
husky - pre-commit script failed (code 254)

pnpx works, though....


4 X P40 is not enough?

I have tried to reproduce your results with 4X P100 but meet such errors.
I am wondering whether anyone could give me some hints.
loss_rpn_bbox_fpn6: 0.014951
INFO train_net_step.py: 443: Save ckpt on exception ...
INFO train_net_step.py: 135: save model: Outputs/e2e_panet_R-50-FPN_2x_mask/ckpt/model_step1506.pth
INFO train_net_step.py: 445: Save ckpt done.
Traceback (most recent call last):
  File "tools/train_net_step.py", line 425, in main
    net_outputs = maskRCNN(**input_data)
  File "/root/miniconda3/lib/python3.6/site-packages/torch/nn/modules/module.py", line 477, in __call__
    result = self.forward(*input, **kwargs)
  File "/teamscratch/msravcshare/yuyua/code/segmentation/PANet/lib/nn/parallel/data_parallel.py", line 111, in forward
    outputs = self.parallel_apply(replicas, inputs, kwargs)
  File "/teamscratch/msravcshare/yuyua/code/segmentation/PANet/lib/nn/parallel/data_parallel.py", line 139, in parallel_apply
    return parallel_apply(replicas, inputs, kwargs, self.device_ids[:len(replicas)])
  File "/teamscratch/msravcshare/yuyua/code/segmentation/PANet/lib/nn/parallel/parallel_apply.py", line 67, in parallel_apply
    raise output
  File "/teamscratch/msravcshare/yuyua/code/segmentation/PANet/lib/nn/parallel/parallel_apply.py", line 42, in _worker
    output = module(*input, **kwargs)
  File "/root/miniconda3/lib/python3.6/site-packages/torch/nn/modules/module.py", line 477, in __call__
    result = self.forward(*input, **kwargs)
  File "/teamscratch/msravcshare/yuyua/code/segmentation/PANet/lib/modeling/model_builder.py", line 144, in forward
    return self._forward(data, im_info, roidb, **rpn_kwargs)
  File "/teamscratch/msravcshare/yuyua/code/segmentation/PANet/lib/modeling/model_builder.py", line 215, in _forward
    loss_mask = mask_rcnn_heads.mask_rcnn_losses(mask_pred, rpn_ret['masks_int32'])
  File "/teamscratch/msravcshare/yuyua/code/segmentation/PANet/lib/modeling/mask_rcnn_heads.py", line 101, in mask_rcnn_losses
    masks_pred.view(n_rois, -1), masks_gt, weight, size_average=False)
  File "/root/miniconda3/lib/python3.6/site-packages/torch/nn/functional.py", line 1651, in binary_cross_entropy_with_logits
    loss = input - input * target + max_val + ((-max_val).exp() + (-input - max_val).exp()).log()
RuntimeError: CUDA error: out of memory

I used 8 * P40 for this experiment with 2 images on one P40. P40 is with 24GB memory compared with the 16GB memory of P100. Maybe you can use smaller image size or smaller batch size.


Select Templating Engine

Which template Engine we should use here?

Haml

Erb

Slim

My vote is for erb.  I've never felt compelled to switch since I can easily understand what is happening in a erb document and typing an element then pressing tab in visual studio code creates the markup for me.  If one of you can write a compelling reason I could be convinced to try one of the others.

@Exellin I'm convinced that over time, I can get you to see why slim can be super fast and powerful and clean.
Now isn't the time, but after our whole team knows erb and understands views and controllers and such, we can try a few views slim or even haml and you can see what makes them so powerful, imho.

Seems reasonable to start with ERB and switch to HAML/Slim.


Appveyor reports NS_ERROR_FILE_NOT_FOUND warnings on PR builds

~1. The build does not install the runtime store and Travis tests fail with the following:~
ASP.NET process exited without listening for requests.
[xUnit.net 00:03:53.1964560]       Output:
[xUnit.net 00:03:53.1966060]       Error: Error:
[xUnit.net 00:03:53.1967550]         An assembly specified in the application dependencies manifest (3a3a8d81df5f425fb0f78a747f1d57b4.deps.json) was not found:
[xUnit.net 00:03:53.1968950]           package: 'Microsoft.AspNetCore.Antiforgery', version: '2.0.1'
[xUnit.net 00:03:53.1970390]           path: 'lib/netstandard2.0/Microsoft.AspNetCore.Antiforgery.dll'
[xUnit.net 00:03:53.1971820]         This assembly was expected to be in the local runtime store as the application was published using the following target manifest files:
[xUnit.net 00:03:53.1975090]           aspnetcore-store-2.0.3.xml

https://travis-ci.org/aspnet/templating/jobs/330125248#L1803

The Appveyor build reports a warning

addons.xpi	WARN	Error parsing extensions state: [Exception...

Hi @SteveSandersonMS. Have you tried it out? Any findings? Thanks!

@jbagga, please follow up on this one to make sure it's handled. Thanks!

This will be handled as part of https://github.com/aspnet/templating/issues/277.


properly handle verification error

Alexa team wanted this error in 400 status code, so catching it in the same Verification error class will make it easier to use Flask global exception to return 400 instead of 500 internal error.

what you're saying is that alexa sends over a test json without cert and signature and asked you to return 400 on it?

yep

their email:
Issues with skill endpoint validation

The skill end-point is not validating the signatures for incoming requests and is accepting requests with an incorrect certificate URL. Please make sure that your signature validation is correct.  To reject an invalid request with an invalid signature or certificate, the skill should respond with HTTP status code 400 (Bad Request) in the response.

Please refer to the following documentation on how to build your Alexa Skill as a web service and validate requests and signatures.
https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/developing-an-alexa-skill-as-a-web-service#verifying-the-signature-certificate-url

thank you for this PR. At this point, i have a different idea in mind to handle this at the extension level.

@johnwheeler Is this the reason why there's many 400 errors in the logs or is that because of me?


transformerAttributifyJsx caused vite Pre-transform error

UnoCSS version
0.63.4
Describe the bug
Running transformerAttributifyJsx with solid-sonner produces the following error:
[vite] Pre-transform error: /Users/_/Desktop/ui/node_modules/.pnpm/solid-sonner<EMAIL_ADDRESS>Unexpected token, expected "," (440:58)

  438 |         return;
  439 |       }
> 440 |       toastRef?.style.setProperty("--swipe-amount", "0px=""");
      |                                                           ^
  441 |       setSwiping(false);
  442 |     }}
  443 |     onPointerMove={(event) => {

I checked solid-sonner/dist/dev.jsx, transformerAttributifyJsx may be converting this code
toastRef?.style.setProperty("--swipe-amount", "0px");

into
toastRef?.style.setProperty("--swipe-amount", "0px=""");

After uninstalling transformerAttributifyJsx, vite was successfully compiled.
Reproduction
https://stackblitz.com/edit/unocss-unocss-j46jgm?file=src%2FApp.tsx
System Info
No response
Validations

[x] Read the Contributing Guidelines.
[x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[x] The provided reproduction is a minimal reproducible example of the bug.

@XHanL  transformerAttributifyJsx transforms files from node_modules, you can temporarily add this configuration to skip.
// uno.config.ts
transformers: [
  transformerAttributifyJsx({
    exclude: [/node_modules/],
  }),
],

@XHanL transformerAttributifyJsx transforms files from node_modules, you can temporarily add this configuration to skip.
 uno.config.ts
transformers: [
transformerAttributifyJsx({
    exclude: [/node_modules/],
  }),
],

When using it in VitePress, I still get an error when I add this configuration


Create a warning for outdated plugins

We're planning to icebox a few plugins. The JSvm is extremely nice, but it's too difficult to maintain two different node forks right now. Most contracts shouldn't even need the custom JSvm. We'll reintroduce these plugins eventually (or if community members want to maintain them). Users will be recommended to use our up.sh script.

@smartcontracts Is this ready to be merged?

I actually think we should update our tutorial/docs before making this merge. Will be very confusing for end-users otherwise.


Ui enhancement and implement clickable personListPanel

As shown in the images below, the font size and the font colour of the view panel has been change to make it more easily readable (for both dark and light theme).

Besides, the person list panel on the left is now clickable such that the person details panel on the right will also update accordingly.

Codecov Report

Merging #92 (d1c33dc) into master (6703fc7) will decrease coverage by 0.19%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master      #92      +/-   ##
============================================
- Coverage     68.73%   68.54%   -0.20%
  Complexity      440      440
============================================
  Files            76       76
  Lines          1433     1437       +4
  Branches        143      143
============================================
  Hits            985      985
- Misses          411      415       +4
  Partials         37       37

Impacted Files
Coverage Δ

src/main/java/coydir/ui/MainWindow.java
0.00% <0.00%> (ø)

src/main/java/coydir/ui/PersonListPanel.java
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Export to PDF Tools

Requested for the PF2E for use with Pathfinder Society. Need to map specific data from the PFS tab to fillable form fields. Should make this generic enough while I'm at it other systems can support it if desired.

Security is an issue with all of this. Still investigating solutions.


Exit Transition not executed if no Enter Transition is specified

Please see http://try.websharper.com/snippet/0000Da
This is broken in both WS 3 and WS 4
See also #120 for a project you can use to repro locally in WS 4:

Comment out all but one transition attributes (to work arounf #120)
Verify that transitions work
Now, comment out the call to Transition.Enter - exit transition is not performed.

Re-tested this with Zafir.UI.Next <IP_ADDRESS>-beta7 - still an issue.


(latest version) write method does not work

I have the issue here..
I only would like to write single point, so I may need the write method. (instead of write_points)
And my JSON body is like:
json_body = {
                "measurement": "message",
                "tags": {
                    "tag1": "99999",
                    "tag2": "99999"
                },
                "fields": {
                    "field1": 9999,
                    "field2": 99999
                },
                "time":<PHONE_NUMBER>893587000
            }

With calling method:
client.write(json_body, protocol=u'json')

And I got error:
  File "/usr/local/lib/python2.7/dist-packages/influxdb/line_protocol.py", line 121, in make_lines
    for point in data['points']:
KeyError: u'points'

It is really weird that def write() has to call:
if protocol == 'json':
    data = make_lines(data, precision).encode('utf-8')

where make_lines:
for point in data['points']:

If I would only want to write 1 single point, then my json(dict) shall naturally look like:
json_body = {
"measurement": "message",
"tags": {
"tag1": "99999",
"tag2": "99999"
},
"fields": {
"field1": 9999,
"field2": 99999
},
"time":<PHONE_NUMBER>893587000
}

Thanks for raising this, and sorry for the delay in getting back to you. Will look at this and address ASAP.

Thanks,
Currently, for your write, it says it requires a dict, so if we try this:
json_body = {
                "measurement": "message",
                "tags": {
                    "tag1": "99999",
                    "tag2": "99999"
                },
                "fields": {
                    "field1": 9999,
                    "field2": 99999
                },
                "time":<PHONE_NUMBER>893587000
            }

Then in client.write(), we shall call this function client.write([json_body]) (it works!), which becomes a list again...

For sanity, can you please confirm the version of the app you're using? I've dug into this some more and the main issue is the order of your data entry...to be fair, this is not documented properly at the moment, sorry! :/
The new syntax is expected as follows, where the tags are listed outside of all points for which they are applicable (which include the required fields and optional time):
    json_body = {
        "tags": {
            "empty_tag": "",
            "none_tag": None,
            "integer_tag": 2,
            "string_tag": "hello"
            },
        "points": [
            {
                "measurement": "test",
                "fields": {
                    "string_val": "hello!",
                    "int_val": 1,
                    "float_val": 1.1,
                    "none_field": None,
                    "bool_val": True,
                    },
                "time":<PHONE_NUMBER>000000000,
                }
            ]
        }

    ret = newClient.write(json_body, params={'db': 'sebtest'})
    print ret

Also, you don't need to specify the protocol unless you're sending the official line protocol; the default is expecting json data.
Do you want to give this another shot with the revised format and let us know?

I think I am using the latest version of the client. (apt-get install)．
IMO, the best format shall be:
json_body = {
                "measurement": "message",
                "tags": {
                    "tag1": "99999",
                    "tag2": "99999"
                },
                "fields": {
                    "field1": 9999,
                    "field2": 99999
                },
                "time":<PHONE_NUMBER>893587000
            }

just like a normal json (dict).
And therefore we can use newClient.write(json_body). (for now I have to call it like oldClient.write([json_body]) even for writing 1 record.
To be frankly speaking, the design of
    json_body = {
        "tags": {
            "empty_tag": "",
            "none_tag": None,
            "integer_tag": 2,
            "string_tag": "hello"
            },
        "points": [
            {
                "measurement": "test",
                "fields": {
                    "string_val": "hello!",
                    "int_val": 1,
                    "float_val": 1.1,
                    "none_field": None,
                    "bool_val": True,
                    },
                "time":<PHONE_NUMBER>000000000,
                }
            ]
        }

is confusing since in InfluxDB, we only have time, tags, field, measurement. (no border to add points here. )

The standard, supported method for writing data to InfluxDB (and the TICK stack) is to write line protocol. The JSON endpoint is deprecated, but support remains in clients like influxdb-python to help users seamlessly cut over. This is why you see the client calling make_lines before actually formatting the http request. The limitation of the old schema is the ability to write multiple points, aka lines or groups of measurements in one json_body. With the new setup, you can define multiple points that get converted to proper line protocol and get sent to the backend. In all cases, tags are optional but points are required; the new structure would allow you to define a particular tagset across a heap of measurements if you wanted.
In either scenario you should not need to pass your json_body as a list. The default expectation is json and will parse the data accordingly (provided it's valid syntax and matches the new structure).

Hi,
Thanks for the reply.
May I ask that,

How can I upgrade InfluxDB-Python so that I can catch up with this new setup?
for method write, is it always connecting and disconnecting the DB all the time? If I may have loop to sequentially insert data into InfluxDB, will it be too inefficient?

Thanks,

We've actually added the instructions to update in the README, but you can also do it as listed here.
For your second question, the connections that are established are not long-running TCP connections. Instead you're creating an HTTP POST that has the keep-alive header set but only for the duration of the write itself. Each call to the write function is idempotent and returns when a retcode is received for the HTTP POST. In InfluxDB, the retcode is any one of the following:

Here is an example:
23:21:30.086209 IP (tos 0x0, ttl 64, id 663, offset 0, flags [DF], proto TCP (6), length 432)
    localhost.localdomain.52844 > localhost.localdomain.d-s-n: Flags [P.], cksum 0xffa4 (incorrect -> 0xdf53), seq 381:761, ack 174, win 350, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 380
E<EMAIL_ADDRESS>.......RPOST /write?db=sebtest HTTP/1.1
Host: localhost:8086
Connection: keep-alive
Accept-Encoding: gzip, deflate
Accept: text/plain
User-Agent: python-requests/2.17.3
Content-type: application/octet-stream
Content-Length: 115
Authorization: Basic cm9vdDpyb290

test,integer_tag=2,string_tag=hello bool_val=True,float_val=1.1,int_val=1i,string_val="hello!"<PHONE_NUMBER>000000000

23:21:30.100862 IP (tos 0x0, ttl 64, id 59040, offset 0, flags [DF], proto TCP (6), length 225)
    localhost.localdomain.d-s-n > localhost.localdomain.52844: Flags [P.], cksum 0xfed5 (incorrect -> 0x5b62), seq 174:347, ack 761, win 359, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 173
E<EMAIL_ADDRESS>...&....HTTP/1.1 204 No Content
Content-Type: application/json
Request-Id: 95ce2f30-6202-11e7-8016-000000000000
X-Influxdb-Version: 1.2.4
Date: Thu, 06 Jul 2017 04:21:30 GMT

23:21:30.100912 IP (tos 0x0, ttl 64, id 664, offset 0, flags [DF], proto TCP (6), length 52)
    localhost.localdomain.52844 > localhost.localdomain.d-s-n: Flags [.], cksum 0xfe28 (incorrect -> 0x51dc), seq 761, ack 347, win 359, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0
E..4..@.@.:*.........l.........F...g.(.....
...&...&

@aviau READY TO CLOSE

Hello,
I'v tried a lot of times but I still get error Below. Could you please help me about that?
Here is code and error
payload = {
"measurement": "virtualmachine",
"tags": {
    "name": name,
    "instanceUuid": instanceUuid
},
"time": datetime.datetime.now().isoformat(),
"fields": {
            "version": version,
            "template": template,
            "memorySizeMB": memorySizeMB,
            "numCpu":numCpu,
            "numEthernetCards": numEthernetCards,
            "numVirtualDisks": numVirtualDisks,
            "committedStorage": committedStorage,
            "uncommittedStorage": uncommittedStorage,
            "powerState":powerState,
            "tools_version": tools_version,
            "ip_address": ip_address,
            "hostName": hostName,
            "vmPathName": vmPathName,
            "guestFullName": guestFullName
}

}
print payload
client.write([payload])
Traceback (most recent call last):
File "influxdb/test.py", line 107, in
print_vm_info(child)
File "influxdb/test.py", line 92, in print_vm_info
client.write([payload])
File "/usr/local/lib/python2.7/dist-packages/influxdb/client.py", line 315, in write
data = make_lines(data, precision).encode('utf-8')
File "/usr/local/lib/python2.7/dist-packages/influxdb/line_protocol.py", line 126, in make_lines
static_tags = data.get('tags')
AttributeError: 'list' object has no attribute 'get'

Same problem here at latest version. No fix yet.


Support .NET Core

Let me know how I can help out with this. I'm playing with HALight at the moment, but I'd really like to be able to use this and see Argolis up and running on Core also.
I do realize that's likely a non-trivial task though :)

I got this far: 9f506f211453db4fc7fd958bf79e10fb79e6ecd7. Mostly by removing the NullGuard and fixing up some reflection (plus hacking out the Impromptu Interface stuff). I'm about 99% certain it isn't correct, but the test project has 306 errors at the moment...

 Without forking and even creating a branch? :)

About .NET Core, maybe initially it's enough to only have the actual library migrated and leave test project on full .NET?

It's a shame that Fody doesn't work in .NET Standard/Core yet (see Fody/Fody#206). I'm using Fody plugins extensively in my various projects.

I'd feel much more confident about having some tests running especially in light of https://github.com/NuGet/json-ld.net/issues/11. By knowing just enough about json-ld to be dangerous I mean that I'm at the point that I don't know what I don't know, but on the plus side, I do know that what I don't know is >> what I do know.
I think one of the bigger issues at the moment is I haven't tried to untangle the paket/nuget/project.json mess, so a lot of errors are likely the result of missing dependencies. It was very late last night when I got library building so I didn't have the energy to deal with the test project (US, eastern time).
I've noticed you do seem to like Fody :) I've avoided it due to some extremely poor experiences with PostSharp, although from reading up on Fody it looks like they may have avoided some of my biggest objections.

I'm looking at the repo now and it appears that the commit is in my fork in
the net-core branch. I just pasted the commit hash into the message and it
appears as though GitHub is showing it as of it's part of your repo. If you
look at the commit history, it shouldn't be there. Seems like a UI issue.
You had me scared for a minute there...
 Without forking and even creating a branch? :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/wikibus/JsonLD.Entities/issues/11#issuecomment-277198336,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABuMQhIBs5-R1S2ZwbhTja1YJ8j7lAuHks5rYu4jgaJpZM4L1NbQ
.

I'd feel much more confident about having some tests running

Ofc, you'd still run tests against .NET Framework 4.6. It has to count for something

the paket/nuget/project.json mess

Which version dotnet are you using? According to these tweets, paket should work fine with project.json. I'm more concerned about replacing dependencies which don't target .NET Standard/Core yet.

I've noticed you do seem to like Fody :)

I certainly do. I use a number basic plugins on a regular basis. I'm curious what's your beef with PostSharp.

You had me scared for a minute there...

Yea, I'm guessing GitHub stores forks as branches and not physical clones. It would explain why unmerged commits are accessible through "my" URLs. It also explains why it's possible to merger PRs even after a fork has been deleted.

Ofc, you'd still run tests against .NET Framework 4.6. It has to count for something

Yeah... it's still early (or late) and that didn't occur to me :) Of course I'm doing my dev on OS X at the moment, so I can't run the 4.6 tests myself (my day job is in a locked-down corporate environment where they're just starting to think that maybe there's something to this open source thing after all).

Which version dotnet are you using? According to these tweets, paket should work fine with project.json.

I need to create a project.json first with the correct packages listed. The mess is more having to figure out how they interact, and getting comfortable with paket. So far I've run into a few issues that I don't 100% understand how I got around. In particular, it was pulling the wrong version of Newtonsoft.Json (6.x instead of 9.x) and complaining it didn't support .Net Core, which is true for 6.x, even though 9.x was listed explicitly somewhere, and when I removed the paket.lock file and tried to regenerate it, it complained they were out of sync, and then eventually I managed to get things building, but, as I said, I don't really know how/why. I'll pay closer attention tonight and see if I can learn a bit more about it.

I'm curious what's your beef with PostSharp. What kind of bad experiences have you had?

2 (and a half?) things really. In one case we experienced really poor performance, but that may have had to do more with intercepting every single method entry and exit and logging it than PostSharp itself. Then, once you've added it to your project it's nearly impossible to eradicate it when you decide you no longer want to use it. There's also the issue that it needs to be installed (as in full installer installed) on any system that wants to build the project. And then there's the issue that I can't see exactly what it's doing to my code. And that makes me nervous, no matter how much test coverage I have. Fody seems to have addressed all of those concerns, so it's just the lack of Core support that's a major issue.

Yea, I'm guessing GitHub stores forks as branches and not physical clones.

http://stackoverflow.com/a/6286877/173225 explains it pretty well, but I think the issue we see here is probably a UI implementation detail since my best guess is that git is still able to treat the fork as a sort of branch since it forked from a specific commit and they're just failing to account for the commit being in a different repo.

Bump. Still no plans for supporting .netstandard?


Add support for RimWorld 1.5

Initial work has been done to fix mod building for RimWorld version 1.5.
Not thoroughly tested for bugs.

Cool cool cool. I was also looking at this.
Did you check and verify the rename dialogs work? That is of course the biggest chunk of code change here. 1.5 using a template in Dialog_Rename with an interface makes it awkward because the policies need the type info from the dialog so I am right now giving up myself but it's nice to see this

Yeah dialogs and renaming works, if I tested this correctly..

Many thanks for these updates TheLonerD.  We can ask the community to test this.

Added 1.5 to 1.5 branched. Did some smoke testing and released to steam. It seems everything is working fine.
Added full support for new reading policy feature from 1.5 base game.
I haven't bought the new DLC so I can't be sure if everything works fine.

Not really, did some smoke test and played with it couple minutes
I can ask the community to test this.
Yes please. Better to ask community to heavily test this mod in 1.5, we can fix any bugs that might be in there.


MemberExpression over ObjectExpression ({ x: 1 }.x) should throw

Hello! This is JavaScript behaviour in browser when I run { x: 1 }.x:
SyntaxError: Unexpected token '.'
But jsep allows this kind of expressions. Is it bug or feature?

@grimalschi - are you using the latest version of @jsep-plugin/object? v1.1.0 was just released, which added member expression support.
I did a quick test:
"{ x: 1 }.x" =>

 {
  "type": "MemberExpression",
  "computed": false,
  "object": {
    "type": "ObjectExpression",
    "properties": [
      {
        "type": "Property",
        "computed": false,
        "key": {
          "type": "Identifier",
          "name": "x"
        },
        "value": {
          "type": "Literal",
          "value": 1,
          "raw": "1"
        },
        "shorthand": false
      }
    ]
  },
  "property": {
    "type": "Identifier",
    "name": "x"
  }
}

Exacty. It gives me an AST, but correct behaviour in this case is to throw.
This is what browser write { x: 1 }.x in console.
It works in jsep, but gives and error in browser :)

{x: 1}['x'] - should work
{x: 1}.x - should throw an Error
This is specific case when you make MemberExpression with computed: false over ObjectExpression

I wonder if this is purely a browser console issue? Because they are both valid expressions in javascript and in node.
// node:
console.log({x: 1}.x); // 1
console.log({x: 1}['x']); // 1

// firefox/chrome:
<script>
  console.log({x: 1}.x); // 1
  console.log({x: 1}['x']); // 1
</script>

similarly, typing into the debug console: const a = { x: 1 }; console.log(a.x); works. Just as typing just "a" into the console will display the value of a, but would be invalid javascript within a script.

Looks like I was wrong, sorry

All good :-)


Reviewing and organizing c++ unit-test

In GitLab by @cmastalli on Jul 18, 2019, 17:34
null

In GitLab by @cmastalli on Jul 18, 2019, 17:38
closed


Cannot use kubectl get nodes

1 使用命令启动rancher-server,
docker run -d --restart=unless-stopped
-p 80:80 -p 443:443
-v /data:/var/lib/rancher/
-v /root/var/log/auditlog:/var/log/auditlog
-e AUDIT_LEVEL=3
rancher/rancher:v2.2.2
2 增加etcd,controller, worker 3个节点，正常启动
3 在rancher集群界面，点击 执行kubectl命令，然后执行 k get nodes,在console报错如下：
Run kubectl commands inside here
e.g. kubectl get all

k get nodes
E0510 01:50:42.088422      38 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
E0510 01:50:42.171000      38 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
E0510 01:50:42.250789      38 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
E0510 01:50:42.332578      38 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
E0510 01:50:42.411621      38 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
error: the server doesn't have a resource type "nodes"

Same here:
# Run kubectl commands inside here
# e.g. kubectl get all
> kubectl get pods
E0514 16:17:18.135296      49 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
E0514 16:17:18.182983      49 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
E0514 16:17:18.215725      49 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
E0514 16:17:18.250081      49 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
E0514 16:17:18.283006      49 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
error: the server doesn't have a resource type "pods"

I have single server/node install
I started having this bug when migrating to rancher 2.1.6 with kubernetes 1.11
I just did a fresh install ubuntu 18.04 / docker 1.18 / rancher 2.2.3 / kubernetes 1.13
but I still have this issue
(I am running rancher server behind nginx with letsencrypt certificates)

When encountering issues using kubectl, please supply logs using kubectl -v9, in this case, kubectl -v9 get pods.
Let me know if you can supply this so we can investigate.

Hi @superseb
Thanks for following this.
Here are the full logs :
> kubectl -v9 get pods
I0622 10:04:29.344941      61 loader.go:359] Config loaded from file /nonexistent/.kube/config
I0622 10:04:29.345475      61 loader.go:359] Config loaded from file /nonexistent/.kube/config
I0622 10:04:29.345999      61 round_trippers.go:419] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.12.7 (linux/amd64) kubernetes/6f48297" -H "Authorization: Bearer kubectl-shell-user-ttbg5:5kr827lhq84nlhdbxqkvxg9qbndd6wc9cqs4c2g2m54wqcpzrkgtff" 'https://my.rancher.server:8989/k8s/clusters/c-v9tre/api?timeout=32s'
I0622 10:04:29.379799      61 round_trippers.go:438] GET https://my.rancher.server:8989/k8s/clusters/c-v9tre/api?timeout=32s 200 OK in 33 milliseconds
I0622 10:04:29.379828      61 round_trippers.go:444] Response Headers:
I0622 10:04:29.379840      61 round_trippers.go:447]     Content-Type: application/json
I0622 10:04:29.379850      61 round_trippers.go:447]     Content-Length: 137
I0622 10:04:29.379860      61 round_trippers.go:447]     Connection: keep-alive
I0622 10:04:29.379870      61 round_trippers.go:447]     Server: nginx/1.15.12
I0622 10:04:29.379880      61 round_trippers.go:447]     Date: Sat, 22 Jun 2019 10:04:29 GMT
I0622 10:04:29.380105      61 request.go:942] Response Body: {"kind":"APIVersions","versions":["v1"],"serverAddressByClientCIDRs":[{"clientCIDR":"<IP_ADDRESS>/0","serverAddress":"<IP_ADDRESS>:6443"}]}
I0622 10:04:29.380457      61 round_trippers.go:419] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.12.7 (linux/amd64) kubernetes/6f48297" -H "Authorization: Bearer kubectl-shell-user-ttbg5:5kr827lhq84nlhdbxqkvxg9qbndd6wc9cqs4c2g2m54wqcpzrkgtff" 'https://my.rancher.server:8989/k8s/clusters/c-v9tre/apis?timeout=32s'
I0622 10:04:29.390636      61 round_trippers.go:438] GET https://my.rancher.server:8989/k8s/clusters/c-v9tre/apis?timeout=32s 200 OK in 10 milliseconds
I0622 10:04:29.390666      61 round_trippers.go:444] Response Headers:
I0622 10:04:29.390676      61 round_trippers.go:447]     Connection: keep-alive
I0622 10:04:29.390684      61 round_trippers.go:447]     Server: nginx/1.15.12
I0622 10:04:29.390692      61 round_trippers.go:447]     Date: Sat, 22 Jun 2019 10:04:29 GMT
I0622 10:04:29.390701      61 round_trippers.go:447]     Content-Type: application/json
E0622 10:04:29.390782      61 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
I0622 10:04:29.390986      61 cached_discovery.go:111] skipped caching discovery info due to Unexpected error &errors.errorString{s:"unexpected EOF"} when reading response body. Please retry.
I0622 10:04:29.391352      61 loader.go:359] Config loaded from file /nonexistent/.kube/config
I0622 10:04:29.391745      61 round_trippers.go:419] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.12.7 (linux/amd64) kubernetes/6f48297" -H "Authorization: Bearer kubectl-shell-user-ttbg5:5kr827lhq84nlhdbxqkvxg9qbndd6wc9cqs4c2g2m54wqcpzrkgtff" 'https://my.rancher.server:8989/k8s/clusters/c-v9tre/api?timeout=32s'
I0622 10:04:29.404287      61 round_trippers.go:438] GET https://my.rancher.server:8989/k8s/clusters/c-v9tre/api?timeout=32s 200 OK in 12 milliseconds
I0622 10:04:29.404322      61 round_trippers.go:444] Response Headers:
I0622 10:04:29.404335      61 round_trippers.go:447]     Server: nginx/1.15.12
I0622 10:04:29.404343      61 round_trippers.go:447]     Date: Sat, 22 Jun 2019 10:04:29 GMT
I0622 10:04:29.404350      61 round_trippers.go:447]     Content-Type: application/json
I0622 10:04:29.404357      61 round_trippers.go:447]     Content-Length: 137
I0622 10:04:29.404372      61 round_trippers.go:447]     Connection: keep-alive
I0622 10:04:29.404655      61 request.go:942] Response Body: {"kind":"APIVersions","versions":["v1"],"serverAddressByClientCIDRs":[{"clientCIDR":"<IP_ADDRESS>/0","serverAddress":"<IP_ADDRESS>:6443"}]}
I0622 10:04:29.404857      61 round_trippers.go:419] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.12.7 (linux/amd64) kubernetes/6f48297" -H "Authorization: Bearer kubectl-shell-user-ttbg5:5kr827lhq84nlhdbxqkvxg9qbndd6wc9cqs4c2g2m54wqcpzrkgtff" 'https://my.rancher.server:8989/k8s/clusters/c-v9tre/apis?timeout=32s'
I0622 10:04:29.416049      61 round_trippers.go:438] GET https://my.rancher.server:8989/k8s/clusters/c-v9tre/apis?timeout=32s 200 OK in 11 milliseconds
I0622 10:04:29.416093      61 round_trippers.go:444] Response Headers:
I0622 10:04:29.416111      61 round_trippers.go:447]     Server: nginx/1.15.12
I0622 10:04:29.416137      61 round_trippers.go:447]     Date: Sat, 22 Jun 2019 10:04:29 GMT
I0622 10:04:29.416157      61 round_trippers.go:447]     Content-Type: application/json
I0622 10:04:29.416179      61 round_trippers.go:447]     Connection: keep-alive
E0622 10:04:29.416259      61 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
I0622 10:04:29.416306      61 cached_discovery.go:111] skipped caching discovery info due to Unexpected error &errors.errorString{s:"unexpected EOF"} when reading response body. Please retry.
I0622 10:04:29.416321      61 shortcut.go:89] Error loading discovery information: Unexpected error &errors.errorString{s:"unexpected EOF"} when reading response body. Please retry.
I0622 10:04:29.416435      61 round_trippers.go:419] curl -k -v -XGET  -H "Authorization: Bearer kubectl-shell-user-ttbg5:5kr827lhq84nlhdbxqkvxg9qbndd6wc9cqs4c2g2m54wqcpzrkgtff" -H "User-Agent: kubectl/v1.12.7 (linux/amd64) kubernetes/6f48297" -H "Accept: application/json, */*" 'https://my.rancher.server:8989/k8s/clusters/c-v9tre/api?timeout=32s'
I0622 10:04:29.436760      61 round_trippers.go:438] GET https://my.rancher.server:8989/k8s/clusters/c-v9tre/api?timeout=32s 200 OK in 20 milliseconds
I0622 10:04:29.436846      61 round_trippers.go:444] Response Headers:
I0622 10:04:29.436885      61 round_trippers.go:447]     Server: nginx/1.15.12
I0622 10:04:29.436926      61 round_trippers.go:447]     Date: Sat, 22 Jun 2019 10:04:29 GMT
I0622 10:04:29.436959      61 round_trippers.go:447]     Content-Type: application/json
I0622 10:04:29.436996      61 round_trippers.go:447]     Content-Length: 137
I0622 10:04:29.437017      61 round_trippers.go:447]     Connection: keep-alive
I0622 10:04:29.437365      61 request.go:942] Response Body: {"kind":"APIVersions","versions":["v1"],"serverAddressByClientCIDRs":[{"clientCIDR":"<IP_ADDRESS>/0","serverAddress":"<IP_ADDRESS>:6443"}]}
I0622 10:04:29.437703      61 round_trippers.go:419] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.12.7 (linux/amd64) kubernetes/6f48297" -H "Authorization: Bearer kubectl-shell-user-ttbg5:5kr827lhq84nlhdbxqkvxg9qbndd6wc9cqs4c2g2m54wqcpzrkgtff" 'https://my.rancher.server:8989/k8s/clusters/c-v9tre/apis?timeout=32s'
I0622 10:04:29.448576      61 round_trippers.go:438] GET https://my.rancher.server:8989/k8s/clusters/c-v9tre/apis?timeout=32s 200 OK in 10 milliseconds
I0622 10:04:29.448616      61 round_trippers.go:444] Response Headers:
I0622 10:04:29.448625      61 round_trippers.go:447]     Server: nginx/1.15.12
I0622 10:04:29.448630      61 round_trippers.go:447]     Date: Sat, 22 Jun 2019 10:04:29 GMT
I0622 10:04:29.448636      61 round_trippers.go:447]     Content-Type: application/json
I0622 10:04:29.448644      61 round_trippers.go:447]     Connection: keep-alive
E0622 10:04:29.448721      61 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
I0622 10:04:29.448769      61 cached_discovery.go:111] skipped caching discovery info due to Unexpected error &errors.errorString{s:"unexpected EOF"} when reading response body. Please retry.
I0622 10:04:29.448914      61 round_trippers.go:419] curl -k -v -XGET  -H "User-Agent: kubectl/v1.12.7 (linux/amd64) kubernetes/6f48297" -H "Authorization: Bearer kubectl-shell-user-ttbg5:5kr827lhq84nlhdbxqkvxg9qbndd6wc9cqs4c2g2m54wqcpzrkgtff" -H "Accept: application/json, */*" 'https://my.rancher.server:8989/k8s/clusters/c-v9tre/api?timeout=32s'
I0622 10:04:29.463943      61 round_trippers.go:438] GET https://my.rancher.server:8989/k8s/clusters/c-v9tre/api?timeout=32s 200 OK in 15 milliseconds
I0622 10:04:29.463975      61 round_trippers.go:444] Response Headers:
I0622 10:04:29.464403      61 round_trippers.go:447]     Content-Length: 137
I0622 10:04:29.464418      61 round_trippers.go:447]     Connection: keep-alive
I0622 10:04:29.464428      61 round_trippers.go:447]     Server: nginx/1.15.12
I0622 10:04:29.464439      61 round_trippers.go:447]     Date: Sat, 22 Jun 2019 10:04:29 GMT
I0622 10:04:29.464465      61 round_trippers.go:447]     Content-Type: application/json
I0622 10:04:29.464633      61 request.go:942] Response Body: {"kind":"APIVersions","versions":["v1"],"serverAddressByClientCIDRs":[{"clientCIDR":"<IP_ADDRESS>/0","serverAddress":"<IP_ADDRESS>:6443"}]}
I0622 10:04:29.464802      61 round_trippers.go:419] curl -k -v -XGET  -H "User-Agent: kubectl/v1.12.7 (linux/amd64) kubernetes/6f48297" -H "Authorization: Bearer kubectl-shell-user-ttbg5:5kr827lhq84nlhdbxqkvxg9qbndd6wc9cqs4c2g2m54wqcpzrkgtff" -H "Accept: application/json, */*" 'https://my.rancher.server:8989/k8s/clusters/c-v9tre/apis?timeout=32s'
I0622 10:04:29.474145      61 round_trippers.go:438] GET https://my.rancher.server:8989/k8s/clusters/c-v9tre/apis?timeout=32s 200 OK in 9 milliseconds
I0622 10:04:29.474176      61 round_trippers.go:444] Response Headers:
I0622 10:04:29.474188      61 round_trippers.go:447]     Server: nginx/1.15.12
I0622 10:04:29.474212      61 round_trippers.go:447]     Date: Sat, 22 Jun 2019 10:04:29 GMT
I0622 10:04:29.474223      61 round_trippers.go:447]     Content-Type: application/json
I0622 10:04:29.474232      61 round_trippers.go:447]     Connection: keep-alive
E0622 10:04:29.474307      61 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
I0622 10:04:29.474354      61 cached_discovery.go:111] skipped caching discovery info due to Unexpected error &errors.errorString{s:"unexpected EOF"} when reading response body. Please retry.
I0622 10:04:29.474483      61 round_trippers.go:419] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.12.7 (linux/amd64) kubernetes/6f48297" -H "Authorization: Bearer kubectl-shell-user-ttbg5:5kr827lhq84nlhdbxqkvxg9qbndd6wc9cqs4c2g2m54wqcpzrkgtff" 'https://my.rancher.server:8989/k8s/clusters/c-v9tre/api?timeout=32s'
I0622 10:04:29.487852      61 round_trippers.go:438] GET https://my.rancher.server:8989/k8s/clusters/c-v9tre/api?timeout=32s 200 OK in 13 milliseconds
I0622 10:04:29.487889      61 round_trippers.go:444] Response Headers:
I0622 10:04:29.487899      61 round_trippers.go:447]     Server: nginx/1.15.12
I0622 10:04:29.487907      61 round_trippers.go:447]     Date: Sat, 22 Jun 2019 10:04:29 GMT
I0622 10:04:29.487919      61 round_trippers.go:447]     Content-Type: application/json
I0622 10:04:29.487930      61 round_trippers.go:447]     Content-Length: 137
I0622 10:04:29.487937      61 round_trippers.go:447]     Connection: keep-alive
I0622 10:04:29.488163      61 request.go:942] Response Body: {"kind":"APIVersions","versions":["v1"],"serverAddressByClientCIDRs":[{"clientCIDR":"<IP_ADDRESS>/0","serverAddress":"<IP_ADDRESS>:6443"}]}
I0622 10:04:29.488397      61 round_trippers.go:419] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.12.7 (linux/amd64) kubernetes/6f48297" -H "Authorization: Bearer kubectl-shell-user-ttbg5:5kr827lhq84nlhdbxqkvxg9qbndd6wc9cqs4c2g2m54wqcpzrkgtff" 'https://my.rancher.server:8989/k8s/clusters/c-v9tre/apis?timeout=32s'
I0622 10:04:29.497271      61 round_trippers.go:438] GET https://my.rancher.server:8989/k8s/clusters/c-v9tre/apis?timeout=32s 200 OK in 8 milliseconds
I0622 10:04:29.497298      61 round_trippers.go:444] Response Headers:
I0622 10:04:29.497309      61 round_trippers.go:447]     Server: nginx/1.15.12
I0622 10:04:29.497319      61 round_trippers.go:447]     Date: Sat, 22 Jun 2019 10:04:29 GMT
I0622 10:04:29.497327      61 round_trippers.go:447]     Content-Type: application/json
I0622 10:04:29.497336      61 round_trippers.go:447]     Connection: keep-alive
E0622 10:04:29.497427      61 request.go:853] Unexpected error when reading response body: &errors.errorString{s:"unexpected EOF"}
I0622 10:04:29.497499      61 cached_discovery.go:111] skipped caching discovery info due to Unexpected error &errors.errorString{s:"unexpected EOF"} when reading response body. Please retry.
F0622 10:04:29.497530      61 helpers.go:119] error: the server doesn't have a resource type "pods"
>

You are showing a single install but the response from the configured server-url (my.rancher.server:8989) is coming from NGINX. Can you share the details on your setup including configs? Does it work when you configure server-url to point to the container directly?

Hi,
It took me a while to find the time to investigate again and I just found the problem.
Everything was fine when connecting directly to rancher skipping nginx.
I use a default one server install with rancher master deployed behind nginx using docker compose:
Nginx conf was the following
upstream rancher {
    server rancher-server:80;
}

server {
    listen 443 ssl;
    server_name my.rancher.server;

    ssl_certificate /etc/letsencrypt/rancher-server/cert.pem;
    ssl_certificate_key /etc/letsencrypt/rancher-server/key.pem;

    access_log /var/log/nginx/access.log;
    error_log  /var/log/nginx/error.log;

    location / {
        proxy_set_header Host $http_host;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Port $server_port;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass http://rancher;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        # This allows the ability for the execute shell window to remain open for up to 15 minutes.
        # Without this parameter, the default is 1 minute and will automatically close.
        proxy_read_timeout 900s;
        proxy_buffering off;
    }
}

I remember not being able to use config as describe in rancher doc because nginx was crashing.
With last nginx docker I could use config from doc.
I just added
    map $http_upgrade $connection_upgrade {
        default Upgrade;
        ''      close;
    }

and
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection $connection_upgrade;

and removed
        proxy_buffering off;

It works fine now.
Thanks again and sorry for waking up this old issue.


Print character of an ASCII value

Description
ASCII value is the numeric representation of a character. For example, the ASCII value of the character 'A' is 65. The ASCII value of the character 'a' is 97. The ASCII value of the character '0' is 48. The ASCII value of the character ' ' is 32.
Input  : 65
Output : A

Program added successfully :tada:
Thanks for your contribution :hugs:


ng update fails for custom schematic with "An unhandled exception occurred: Cannot find module"

🐞 Bug report
Command

[ ] new
[ ] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[x] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?
Yes, the previous version in which this bug was not present was: ~10.2.1 (and possibly anything less than 11.1.4)
Description
When running ng update my-package the process fails with the following error (full stacktrace included below):
An unhandled exception occurred: Cannot find module 'my-package'

Our package depends on Angular 10.x, so this is being run in an Angular 10 workspace.
I believe this is a bug in the latest Angular CLI because:

We tested this update command when we released the new version of our schematics package on 2021-01-29 and it worked back then, but now it does not (with no changes to our package)
When running ng update the Angular CLI will check the version of the CLI installed locally and if it is not the latest version then it will install the latest version in a tmp dir and use that to run the update
A new version of the CLI has been released since we last saw this working, so that's the only thing that's changed
If you run NG_DISABLE_VERSION_CHECK=1 ng update ... to disable the ‘use latest CLI’ behaviour and instead use the locally-installed v.10 of the CLI, then the migration completes successfully.

🔬 Minimal Reproduction

Create a custom schematic and publish two versions, with some migrations
Install the old version of the package containing the schematic in an Angular 10 project
Run ng update custom-schematic-package-name

🔥 Exception or Error

An unhandled exception occurred: Cannot find module 'my-package'
Require stack:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /private/var/folders/4y/f65lmpz57ls14s3sxyd_r7tw0000gp/T/angular-cli-packages-ueI9pk/node_modules/@angular/cli/bin/ng
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:957:15)
    at Function.resolve (internal/modules/cjs/helpers.js:83:19)
    at UpdateCommand.run (/private/var/folders/4y/f65lmpz57ls14s3sxyd_r7tw0000gp/T/angular-cli-packages-ueI9pk/node_modules/@angular/cli/commands/update-impl.js:493:45)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async UpdateCommand.validateAndRun (/private/var/folders/4y/f65lmpz57ls14s3sxyd_r7tw0000gp/T/angular-cli-packages-ueI9pk/node_modules/@angular/cli/models/command.js:139:28)
    at async Object.runCommand (/private/var/folders/4y/f65lmpz57ls14s3sxyd_r7tw0000gp/T/angular-cli-packages-ueI9pk/node_modules/@angular/cli/models/command-runner.js:204:24)
    at async default_1 (/private/var/folders/4y/f65lmpz57ls14s3sxyd_r7tw0000gp/T/angular-cli-packages-ueI9pk/node_modules/@angular/cli/lib/cli/index.js:80:31)

🌍 Your Environment

$ ng version
Your global Angular CLI version (11.1.1) is greater than your local version (10.2.2). The local Angular CLI version is used.

I have narrowed it down and it appears in 11.1.3 and still exists through to latest (11.2.0 at time of writing).

I see that the error messages have been updated in v12 which is nice but unfortunately didn't really help resolve the problem. But I do have more information.
It appears that the package that is causing the error to be thrown doesn't contain an entry file (it's a package that only contains schematics, so one wasn't needed) and wasn't being detected as a package. I'm fairly sure this isn't a change in the behaviour of require.resolve since I used the same node version for all of my tests.
Adding a "main" entry in the package.json pointing to a dummy index.js file to the published package seems to have fixed the problem (at least in future versions - the already published packages are still broken).
I still believe this is a regression bug, as the same package (without the entry file) has worked with all previous Angular CLI versions.


Revert "chore: release v0.1.0"

Reverts korosuke613/zenn-metadata-updater#3

Codecov Report

Merging #4 (213e4a0) into main (f890899) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #4   +/-   ##
=======================================
  Coverage   87.03%   87.03%
=======================================
  Files           1        1
  Lines          54       54
  Branches       17       17
=======================================
  Hits           47       47
  Misses          7        7

Continue to review full report at Codecov.

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


Using OpenThread CoAP API on ESP BR Router (TZ-1044)

Question: Using OpenThread CoAP API on ESP BR Router
Hi,
I am currently working with the ESP BR router and attempting to utilize the OpenThread CoAP API to send a CoAP message to the cloud. However, I am encountering some errors in the process.
Details:

Device: ESP BR Router
API: OpenThread CoAP API
Objective: Send a CoAP message to a cloud service

Issue:
When I try to send a CoAP message using the OpenThread CoAP API, I am receiving an error. Here are the specific details of the error message and the relevant portion of my code:
void coap_send_mess(void)
{
    otError error = OT_ERROR_NONE;
    otMessage *p_request;
    otMessageInfo message_info;

    otInstance *p_instance = esp_openthread_get_instance();

    otIp6Address synt_ipv6_addr;
    otIp4Address tmp_ipv4_addr;
    const char *aAddress = "167, 99, 85, 188";

    memset(&message_info, 0, sizeof(message_info));

    otIp4AddressFromString(aAddress, &tmp_ipv4_addr);

    if (OT_ERROR_NONE != otNat64SynthesizeIp6Address(esp_openthread_get_instance(), &tmp_ipv4_addr, &message_info.mPeerAddr))
    {
        printf("Error synthesizing IPv6 address from IPv4 address\n");
    }

    char buf[OT_IP6_ADDRESS_STRING_SIZE];
    otIp6AddressToString(&message_info.mPeerAddr, buf, OT_IP6_ADDRESS_STRING_SIZE);
    printf("Address [%s]\n", buf);

    do
    {
        p_request = otCoapNewMessage(p_instance, NULL);
        if (p_request == NULL)
        {
            printf("Failed to allocate message for CoAP Request\r\n");
            break;
        }

        otCoapMessageInit(p_request, OT_COAP_TYPE_NON_CONFIRMABLE, OT_COAP_CODE_POST);

        error = otCoapMessageAppendUriPathOptions(p_request, "brhc");
        if (error != OT_ERROR_NONE)
        {
            printf(" error otCoapMessageSetPayloadMarker\r\n");
        }

        error = otCoapMessageSetPayloadMarker(p_request);
        if (error != OT_ERROR_NONE)
        {
            printf(" error otCoapMessageSetPayloadMarker\r\n");
        }
        uint8_t command = 5;
        error = otMessageAppend(p_request, &command, sizeof(command));
        if (error != OT_ERROR_NONE)
        {
            break;
        }

        message_info.mPeerPort = OT_DEFAULT_COAP_PORT;

        error = otCoapSendRequest(p_instance, p_request, &message_info, NULL, NULL);
    } while (false);

    if (error != OT_ERROR_NONE && p_request != NULL)
    {
        printf("Failed to send CoAP Request: %d\r\n", error);
        otMessageFree(p_request);
    }
    else
    {
        printf(" sent CoAP Request: \r\n");
    }
}

Error Message:
E (53629) OPENTHREAD: Failed to Send UDP message, err: -12
 sent CoAP Request:

I would appreciate any guidance or insights on what might be causing this issue and how I can successfully send a CoAP message to the cloud using the OpenThread CoAP API on the ESP BR router.
Thank you in advance for your help!
Best regards,
Cedric

Hi, @cedriczou13 Your issue is more like this question in our BR docs: https://docs.espressif.com/projects/esp-thread-br/en/latest/qa.html#q1-why-can-t-i-access-the-host-from-the-br-device-using-the-ping-command.
You can call the ot APIs to create a COAP message and add the detailed information you like in the message. But for sending this message to the cloud on BR device, using any openthread APIs is not a reasonable choose. There is a WiFi(or Ethernet) interface on the BR, so the better choose is using the lwip UDP API to send the COAP message.
BTW, your code might work for the other thread end devices to access the cloud via a NAT64-enabled thread BR. I mean in your thread network, this code might work on the device which only has the thread netif. The message will be forward to cloud via BR. Only a risk here: if the function coap_send_mess is not processed in the ot task, you need to acquire the ot lock before calling OT APIs. Please refer to here: https://github.com/espressif/esp-idf/blob/master/components/openthread/include/esp_openthread_lock.h#L48.
And I have a question: Does the BR device have to access the cloud through COAP request? Or your project just needs the BR forward these requests from Thread ED to cloud?

@cedriczou13 Do you have any update on this issue?


Update Mesh-Example.png

Pink crop top
Changes

Checks
By submitting your pull request for review, you agree to the following:

[ ] This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
[ ] I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
[ ] To the best of my knowledge, all proposed changes are accurate.

Hi @Jayden34567, this request does not appear to be valid, or the image is corrupted. If that doesn't seem accurate, please respond with what you're attempting to update.


ARTEMIS-4303 Fix windows service

When installing artemis on windows as a service, if your chosen installation path contained a space, then an extra escape character (%) was being inserted in the generated
artemis-service.xml, causing the service to fail to start. This fix changes the value of ARTEMIS_INSTANCE_ETC_URI in that file from "artemis.instance.etc.uri.windows" to "artemis.instance.etc.uri" to get rid of that unnecessary escape character.

I have no way to test this.. but the changes are ok... merging it


#include  is not available on all C++ platforms.

#include  found in openthread.cpp is not available on all platforms.  A more portable way for initializing and assignment memory to the ThreadNetif needs to be provided to make Openthread more portable.

The solution for this could be to create a platform API that returns a pointer to a allocated and initialized ThreadNetif object.  Something like;
ThreadNetif *otPlatAllocThreadNetif(void);
This would allow the platform to not only invoke the constructors on the ThreadNetif, but also to choose from which memory resource the ThreadNetif object will be allocated.

Fixed in #118.


What are those rationales for collecting the training datasets?

@njucckevin Hello! Thank you for open-sourcing this great work.
I'm a bit curious about how you collected the training data samples from public data sources.
The paper mentions "We collect approximately 300k web pages from the latest Common Crawl repository to serve as our training data for web UI.". Could you please provide some hints about how you selected the ~300k pages from Common Crawl? Did you consider the popularity or complexity of the selected web pages?
I would appreciate it if you could provide some hints. Thanks!

We first randomly select several cdx files from Common Crawl to get the candidate URL sets (more than 50M URLs). Since these URLs contain a large number of duplicate top-level domains, to ensure the diversity of websites and layouts, we keep only one URL for a top-level domain. For example, if www.google.com/news has been selected, URLs like www.google.com/shopping will not included. Finally, we got about 300k URLs with different top-level domains. Beyond the above, we didn't check for popularity and diversity of the web pages.
Let me know if you have any other questions.

Got it. Thank you very much for your reply! @njucckevin


Only apply user-select hack if drag is started

Previously the user-select hack is applied whenever mouseDown on an
element matching the selector, with the right kind of click.
If the onStart method returns false then the drag is aborted, but
the user-select hack is still applied. Because the drag is not running,
the hack is not unapplied on mouseUp. This leads to a whole series of
";user-select: none;; user-select: none;; ..." appearing on the body tag
and the inability to select text on the page until a valid drag happens.
This commit moves the hack application to after the last short circuit
to ensure dragging is actually happening before disabling selection.
I've added a test case and also a box on the example page.

Nice work! I've seen this bug before but didn't have the time to track it down. Solid PR, and thanks for not committing built files.


Display git message warning for 50 character

Git message is not showing in win 10 vs code after 50 characters. This is working fine on my win 7 machine.

VSCode Version: 1.14.2
OS Version: Windows 10

Steps to Reproduce:

Type git message longer than 50 characters
50 character limit message not showing

Reproduces without extensions: Yes

Probably related:
#21144
#18807
#2718

Yeah, I couldn't find that one, duplicate of #21144, thanks @rmunn


Cannot debug single XCTest in 1.11.2

Trying to debug just the testFoo test in the following example executes no tests.
import XCTest

class MyTests: XCTestCase {
    func testFoo() {
        print("x")
    }
}

This was working on 1.11.1. I assume this issue was caused by https://github.com/swiftlang/vscode-swift/pull/1086.

Verified with 0d3185f


User List of Anime

Hi, your project looks much nicer to use than the shitty XML API of MyAnimeList and seems to be updated very often :D  But I'm not sure but it seems there is no way to still fetch user data/user anime list with it right ?
Do you plan to integrate it later in the project ?
I could use your apiary.io api with Kitsu light JSON:API framework : https://github.com/wopian/kitsu/tree/master/packages/kitsu

Yes I've seen this request in MAL forums but were saying it was undocumented (back in 2013) xD I can't even look at MAL API documentation page more than a minute without burning my eyes so I'm very glad to find other projects like this :)
Still thanks for the advice :) , I'll follow your development

Indeed, what's worse is going through MAL's HTML. 🤮
Likewise, will follow yours as well. :)
Good day!


improve documentation for 2.0

Currently readme refers to manpage for the 2.0 setup.  But manpage lacks any instructions on installation and any note about periodic/ setups which seems to be covered (probably for 1.x branch) at https://github.com/zfsnap/zfsnap/wiki/zfSnap-periodic.conf .  So it is unclear (for a zfsnap newbee) on how zfsnap should be setup "properly".

As a matter of fact, I am said newbie and would really like to install and use zfsnap, but have really no clue at all how to install this.
First I tried to copy the manpage to the .../man/man8/ folder and run man zfsnap, but the output looks like crap (no linefeeds, etc.) so that is not the way to go I guess...
Now I guess that I can copy the sbin/* files to /sbin, but with the other folders I have no clue.
So I can do nothing but totally agree with the comment above and hope that someday someone will write a short writeup how to install this. I mean, this might really be a good script, but if you can't install it, people are not really encouraged to use it - and that might be a shame...

Thanks for the feedback. Writing a makefile is on my todo list.
BTW, which OS are you on? I'm surprised the man page didn't render well. It's mandoc, so some linux's /might/ struggle, but I have yet to see one.
---Alex

Hi,
Thanks for the reply. The OS is Omni-OS (uname -a: SunOS omni-server 5.11
omnios-8c08411 i86pc i386 i86pc)
The output of the file looks like (direct copy/paste from terminal - from
start):
| creates and deletes rolling ZFS  snapshots  [em]  usually  with
cron.   main advantages are its portability and that all informa-
tion needed for snapshot management is kept in the snapshot  name
itself.     zfsnap    snapshots    are    in    the   format   of
pool/fs@[prefix]Timestamp--TimeToLive The prefix is optional  and
is  quite  useful  for  filtering; Timestamp is the date and time
when the snapshot was created; and TimeToLive (TTL) is the amount
of  time the snapshot will be kept until it's ready for deletion.
The majority of functionality is implemented at the  layer.  How-
ever,  a  few options can be passed to directly.  Print a summary
of command[hy]line options and  then  exit.   Print  the  version
number  and exit.  operates only on snapshots and will destroy or
create a pool or filesystem.  Most actions are performed by using
a  All  options and arguments passed to a are operated on as they
are  read  This  provides  the  flexibility  needed  for  complex
scenarios,  but  also  has the capacity to bite you if you're not
paying attention. Remember, is provided for a reason.   Only  one
can  be  passed  per  invocation  of By default, will only delete
snapshots whose TTLs have expired. However, options are  provided
to override that behaviour with more aggressive approaches.  Only
snapshots created by will be considered for deletion.  Delete all
zfsnap  snapshots [em] regardless of their TTL expiration [em] on
all ZFS file systems that follow this switch.  Force  delete  all
snapshots  in all pools exceeding regardless of their TTL expira-
tion.  See  for   more   information.    Print   a   summary   of
command[hy]line  options  and  then  exit.  Dry[hy]run. Perform a
trial run with no actions actually performed.  Use for  snapshots
after  this  switch.  Don't use a prefix for snapshots after this
switch.  Operate recursively for snapshots on all ZFS  file  sys-
tems  that  follow  this  switch.  Do not operate recursively for
snapshots on all ZFS file systems that follow this switch.   Skip
pools that are resilvering.  Skip pools that are scrubbing.  Ver-
bose output.  The purpose of is simple: to create snapshots.  Set
how  long the snapshot should be kept. If not set, the default is
one  month.  See  for  more  information.   Print  a  summary  of
command[hy]line  options  and  then  exit.  Dry[hy]run. Perform a
trial run with no actions actually performed.  Use for  snapshots
after  this  switch.  Don't use a prefix for snapshots after this
switch.  Create recursive snapshots of all ZFS file systems  that
follow  this  switch.  Create non[hy]recursive snapshots for each
ZFS file system that follows this switch.  Skip  pools  that  are
resilvering.   Skip  pools  that  are scrubbing.  Verbose output.
Round  snapshot  creation  time  down   to   00   seconds.    The
This was the result of:

copying the man8/zfsnap.8 file to the corresponding man directory

executing "man zfsnap"

It makes no difference whether I execute it in 'screen' or directly from
the terminal.
It must be noted that both times, I ran it from within a ssh session, ran
from the OSX client (standard terminal, standard ssh implementation).
Cheers,
Jeroen

On Mon, Feb 23, 2015 at 4:12 PM, Alex Waite<EMAIL_ADDRESS>wrote:

Thanks for the feedback. Writing a makefile is on my todo list.
BTW, which OS are you on? I'm surprised the man page didn't render well.
It's mandoc, so some linux's /might/ struggle, but I have yet to see one.
---Alex
—
Reply to this email directly or view it on GitHub
https://github.com/zfsnap/zfsnap/issues/54#issuecomment-75559556.
--
De niet-brutalen hebben de andere helft...

@Bimmerboy I can't reproduce your problem with the manpage on OmniOS. Granted the man program is a bit odd in OmniOS, so to view the manpage when it's not installed yet do: MANPATH=man/ man zfsnap
But both man and mandoc correctly render the manpage.
Is this this a problem for you?
---Alex

@Bimmerboy I elected not to write a make file, but I did write some documentation in an INSTALL file, to make things a bit easier on those installing by hand.
If you follow it and still have questions, let me know, and I'll do my best to improve the documentation further. :-)
---Alex


Tagging releases

Hi,
I wanted to create an issue, but it seems to be impossible on this repo. So creating an empty pull request hoping that someone will read this.
We are in the process of creating Conda packages for EnsEMBL perl modules, but, for reproducibility issues, we need to have tagged release archives with stable urls, as can be done automatically by GitHub.
See https://bioconda.github.io/contributor/linting.html#uses-vcs-url for the reasons why.
Currently only branches are available on the ensembl repos, so we are blocked, and can't finish these Conda packages.
Would it be possible to (automatically?) create githhub releases for each EnsEMBL releases? Or maybe there are some archives available at some stable url elsewhere?

ping @jvanheld

Coverage remained the same at 81.483% when pulling e9750328c65f8020e5691e9f55e4cb9a7f671a93 on abretaud:patch-1 into e98e194921d300fdd52a341d5ba6f905c4d69520 on Ensembl:release/98.

We would need releases also for these repos:

https://github.com/Ensembl/ensembl-compara
https://github.com/Ensembl/ensembl-funcgen.git
https://github.com/EnsemblGenomes/ensemblgenomes-api.git
https://github.com/Ensembl/ensembl-variation.git

Hello Anthony,
Internally, we are looking to initiate discussions on our release branching/tagging etc. We cannot put a time frame around this. But we will aim to take use cases like yours into consideration.
Thanks,
Ameya

Dear Ameya,
Thanks for your answer.
We had some mail exchanges with Andy and Bruno in the mean time about our request to have tags and/or releases of the github repository.
We understand that the establishment of a general policy for tags/releases requires some evaluations of the pros and cons, periodicity, ensuring the procedure etc.
However, we are currently completely blocked for the conda packaging of RSAT because we need at least one tag in order to be able to produce a first set of Ensembl packages in the Bioconda channel.
Would it make a problem to already produce a git tag on the current release of Ensembl, so we could already package a first version of Ensembl API, finalise our RSAT packaging ?
Best regards,
Jacques van Helden
Institut Français de Bioinformatique (IFB)
http://www.france-bioinformatique.fr
French node of the European ELIXIR bioinformatics infrastructure
https://elixir-europe.org/about-us/who-we-are/nodes/france
<EMAIL_ADDRESS>https://orcid.org/0000-0002-8799-8584

On 28 Nov 2019, at 17:00, Ameya Chaubal<EMAIL_ADDRESS>wrote:
Hello Anthony,
Internally, we are looking to initiate discussions on our release branching/tagging etc. We cannot put a time frame around this. But we will aim to take use cases like yours into consideration.
Thanks,
Ameya
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Ensembl/ensembl/pull/448?email_source=notifications&email_token=ACT3M2VBFQEBGUAFJB7STA3QV7TKZA5CNFSM4JQC7EVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFM7UKY#issuecomment-559544875, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACT3M2QZ64XRN2VTG6I6W7DQV7TKZANCNFSM4JQC7EVA.


Add ASP.NET support

There's a lot left to do before undrafting, but I said I'd open a draft PR today!
I want to have #!aspnet enable the ASP.NET environment I set up in UseAspNet(). I also want to move this out of the C# Kernel so it can be used with other languages.
I'm still experimenting heavily with what the inner loop should look like, but you can get a feel for the current experience by looking at https://github.com/halter73/AspNetNotebooks/blob/master/AspNetMin.ipynb.

In my opinion, the really cool thing about this is being able to modify an ASP.NET web app, make a request, and see the response along with any diagnostic output in a fraction of a second without leaving the notebook. This is possible because we don't have to restart the process, host or server to deploy changes. I might do a quick video demo once this is a little more polished.

I think this is finally ready to merge! I've updated the PR to minimize the impact on the kernels themselves. This does add an optional declared Type parameter to DotNetKernel.SetVariableAsync(), but it shouldn't cause any problems for people taking dependencies on the Kernels like before when I changed the C# kernel's TFM from netstandard2.1 to net5.0.

⬆📅 I addressed the PR feedback and added more tests.

@jonsequitur The PR builds are consistently hanging after printing Running tests: D:\a\1\s\artifacts\bin\Microsoft.DotNet.Interactive.Tests\Release\net5.0\Microsoft.DotNet.Interactive.Tests.dll [net5.0|x64] This is the same on Windows and Linux. Locally, when I run dotnet test -c Release in src\dotnet-interactive.Tests which appears to be the test project behind Microsoft.DotNet.Interactive.Tests.dll, all 120 tests pass in 24 seconds. Any idea what's going on?

@jonsequitur The PR builds are consistently hanging after printing Running tests: D:\a\1\s\artifacts\bin\Microsoft.DotNet.Interactive.Tests\Release\net5.0\Microsoft.DotNet.Interactive.Tests.dll [net5.0|x64] This is the same on Windows and Linux. Locally, when I run dotnet test -c Release in src\dotnet-interactive.Tests which appears to be the test project behind Microsoft.DotNet.Interactive.Tests.dll, all 120 tests pass in 24 seconds. Any idea what's going on?

We've been seeing this issue in our CI builds for a few weeks. It's not related to your PR.
Have you rebased recently?

We've been seeing this issue in our CI builds for a few weeks. It's not related to your PR.
Have you rebased recently?

@jonsequitur In my last commit, I added #!aspnet-stop so I could call it from AspNetCoreTests.DisposeAsync() and that looks to have fixed the issues with the test project hanging on AzDO. Should I merge this now?

@jonsequitur In my last commit, I added #!aspnet-stop so I could call it from AspNetCoreTests.DisposeAsync() and that looks to have fixed the issues with the test project hanging on AzDO. Should I merge this now?


MetalLB can work in MacOS

Contrary to canonical/multipass#1298, #908 -
I have MetalLB working on MacOS just fine, and my config looks similar-ish to the config generated by microk8s.
Caveats:

metallb doesn't respond to regular ICMP ping, from MacOS or from within the Linux VM
arping doesn't seem to work, even from inside the Multipass Linux VM.  This kinda indicates that MacOS isn't really the problem on that one.

chris@mandalore   ~  curl http://<IP_ADDRESS>
<!doctype html>

  <meta charset="utf-8">
  <title>Kashti</title>

  <link rel="apple-touch-icon" sizes="128x128" href="assets/images/icons/default/apple-touch-icon.png">
  <link rel="icon" type="image/png" sizes="32x32" href="assets/images/icons/default/favicon-32x32.png">
  <link rel="icon" type="image/png" sizes="16x16" href="assets/images/icons/default/favicon-16x16.png">

  <base href="/">

  <meta name="viewport" content="width=device-width, initial-scale=1">
  <link rel="icon" type="image/x-icon" href="favicon.ico">
<link rel="stylesheet" href="styles.56bbad704999d16e724b.css">

  <app-root></app-root>

 chris@mandalore   ~  kubectl get svc brigade-server-kashti -n brigade-system
NAME                    TYPE           CLUSTER-IP       EXTERNAL-IP     PORT(S)        AGE
brigade-server-kashti   LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>   80:31538/TCP   25m

 chris@mandalore   ~  kubectl get configmap -n metallb-system config -o yaml --export
Flag --export has been deprecated, This flag is deprecated and will be removed in future.
apiVersion: v1
data:
  config: |
    address-pools:
    - name: default
      protocol: layer2
      addresses:
      - <IP_ADDRESS>-<IP_ADDRESS>
kind: ConfigMap
metadata:
  annotations:
    fluxcd.io/sync-checksum: 64a621d53c13252b2b280090f14f999639501b7a
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","data":{"config":"address-pools:\n- name: default\n  protocol: layer2\n  addresses:\n  - <IP_ADDRESS>-<IP_ADDRESS>\n"},"kind":"ConfigMap","metadata":{"annotations":{"fluxcd.io/sync-checksum":"64a621d53c13252b2b280090f14f999639501b7a"},"labels":{"fluxcd.io/sync-gc-mark":"sha256.NIaJeDs6KJDSCWGRnkxjLiQ59w_zuuD52O_bGy9jD84"},"name":"config","namespace":"metallb-system"}}
  creationTimestamp: null
  labels:
    fluxcd.io/sync-gc-mark: sha256.NIaJeDs6KJDSCWGRnkxjLiQ59w_zuuD52O_bGy9jD84
  managedFields:
  - apiVersion: v1
    fieldsType: FieldsV1
    fieldsV1:
      f:data:
        .: {}
        f:config: {}
      f:metadata:
        f:annotations:
          .: {}
          f:fluxcd.io/sync-checksum: {}
          f:kubectl.kubernetes.io/last-applied-configuration: {}
        f:labels:
          .: {}
          f:fluxcd.io/sync-gc-mark: {}
    manager: kubectl
    operation: Update
    time: "2020-04-11T02:35:45Z"
  name: config
  selfLink: /api/v1/namespaces/metallb-system/configmaps/config

If I have some time tomorrow, I'll provide more examples, and possibly make an attempt to see if this works with the microk8s plugin, as I would expect it to
CC/ @candlerb for information/discussion

Actually, I just got arping working from the host, but only when I specify the interface:
 chris@mandalore   ~  sudo /usr/local/Cellar/arping/2.21_1/sbin/arping -i bridge100 <IP_ADDRESS>
ARPING <IP_ADDRESS>
60 bytes from ca:3b:cc:0e:10:69 (<IP_ADDRESS>): index=0 time=7.856 msec
60 bytes from ca:3b:cc:0e:10:69 (<IP_ADDRESS>): index=1 time=824.000 usec
60 bytes from ca:3b:cc:0e:10:69 (<IP_ADDRESS>): index=2 time=1.899 msec
^C
--- <IP_ADDRESS> statistics ---
3 packets transmitted, 3 packets received,   0% unanswered (0 extra)
rtt min/avg/max/std-dev = 0.824/3.526/7.856/3.093 ms
 chris@mandalore   ~  sudo /usr/local/Cellar/arping/2.21_1/sbin/arping -i bridge100 <IP_ADDRESS>
ARPING <IP_ADDRESS>
60 bytes from ca:3b:cc:0e:10:69 (<IP_ADDRESS>): index=0 time=2.856 msec
60 bytes from ca:3b:cc:0e:10:69 (<IP_ADDRESS>): index=1 time=601.000 usec
60 bytes from ca:3b:cc:0e:10:69 (<IP_ADDRESS>): index=2 time=414.000 usec
^C
--- <IP_ADDRESS> statistics ---
3 packets transmitted, 3 packets received,   0% unanswered (0 extra)
rtt min/avg/max/std-dev = 0.414/1.290/2.856/1.110 ms

non working arping, but arp is in the table on laptop
chris@mandalore   ~  sudo /usr/local/Cellar/arping/2.21_1/sbin/arping <IP_ADDRESS>
arping: libnet_init(LIBNET_LINK, <null>): libnet_ifaddrlist(): SIOCGIFADDR: dev=en5: Operation not permitted
 chris@mandalore   ~  arp -a | grep 196.168.54
 chris@mandalore   ~  arp -a | grep 192.168.54
 chris@mandalore   ~  arp -a | grep 192.168.64
? (<IP_ADDRESS>) at fa:ff:c2:d0:67:64 on bridge100 ifscope permanent [bridge]
? (<IP_ADDRESS>) at ca:3b:cc:e:10:69 on bridge100 ifscope [bridge]
? (<IP_ADDRESS>) at ca:3b:cc:e:10:69 on bridge100 ifscope [bridge]
? (<IP_ADDRESS>) at ca:3b:cc:e:10:69 on bridge100 ifscope [bridge]
? (<IP_ADDRESS>) at ff:ff:ff:ff:ff:ff on bridge100 ifscope [bridge]

Remember this is a problem with multipass specifically.
FWIW, I have now switched from multipass to Virtualbox for another networking reason (multipass VM was unable to access remote site via Cisco Anyconnect VPN client).  I haven't tried metallb since the switch, but I've never had issues with ARP with Virtualbox.

@candlerb yes, this is macos > multipass > microk8s > metallb
The only differentiator may be that I installed metallb manually, rather than using the addon.

Versions:
multipass v1.1.0
microk8s 1.18/stable channel
metallb v0.8.2 (I should probably update to 0.9.3)
macos 10.15.4

I have confirmed I can replicate this metallb working with the microk8s addon version of metallb, as well:
 chris@mandalore   ~/src/cscheib-fluxcd/workloads     master   kubectl get configmap -n metallb-system -o yaml config --export
Flag --export has been deprecated, This flag is deprecated and will be removed in future.
apiVersion: v1
data:
  config: |
    address-pools:
    - name: default
      protocol: layer2
      addresses:
      - <IP_ADDRESS>-<IP_ADDRESS>
kind: ConfigMap
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","data":{"config":"address-pools:\n- name: default\n  protocol: layer2\n  addresses:\n  - <IP_ADDRESS>-<IP_ADDRESS>\n"},"kind":"ConfigMap","metadata":{"annotations":{},"name":"config","namespace":"metallb-system"}}
  creationTimestamp: null
  managedFields:
  - apiVersion: v1
    fieldsType: FieldsV1
    fieldsV1:
      f:data:
        .: {}
        f:config: {}
      f:metadata:
        f:annotations:
          .: {}
          f:kubectl.kubernetes.io/last-applied-configuration: {}
    manager: kubectl
    operation: Update
    time: "2020-04-11T17:10:39Z"
  name: config
  selfLink: /api/v1/namespaces/metallb-system/configmaps/config

 chris@mandalore   ~/src/cscheib-fluxcd/workloads     master   curl -i http://<IP_ADDRESS>
HTTP/1.1 307 Temporary Redirect
Content-Type: text/html; charset=utf-8
Location: https://<IP_ADDRESS>/
Date: Sat, 11 Apr 2020 17:11:46 GMT
Content-Length: 58

<a href="https://<IP_ADDRESS>/">Temporary Redirect.

 chris@mandalore   ~/src/cscheib-fluxcd/workloads     master   curl -i http://<IP_ADDRESS>
HTTP/1.1 200 OK
Server: nginx/1.16.0
Date: Sat, 11 Apr 2020 17:11:48 GMT
Content-Type: text/html
Content-Length: 980
Last-Modified: Wed, 14 Aug 2019 20:50:55 GMT
Connection: keep-alive
ETag: "5d54742f-3d4"
Accept-Ranges: bytes

<!doctype html>

  <meta charset="utf-8">
  <title>Kashti</title>

  <link rel="apple-touch-icon" sizes="128x128" href="assets/images/icons/default/apple-touch-icon.png">
  <link rel="icon" type="image/png" sizes="32x32" href="assets/images/icons/default/favicon-32x32.png">
  <link rel="icon" type="image/png" sizes="16x16" href="assets/images/icons/default/favicon-16x16.png">

  <base href="/">

  <meta name="viewport" content="width=device-width, initial-scale=1">
  <link rel="icon" type="image/x-icon" href="favicon.ico">
<link rel="stylesheet" href="styles.56bbad704999d16e724b.css">

  <app-root></app-root>

I'll rebuild this single-node cluster from scratch in a little while and verify that I can replicate all of this again.

Then I guess it might be because I'm on macOS 10.14.6 (due to not having time to replace all 32-bit apps)

@candlerb out of curiosity, did you have any loadbalancer services created during your testing?
metallb is only responding to IP addresses that have an active LB service assigned to them:
ARP from an IP within the MetalLB range, backed by a service:
chris@mandalore   ~/src/cscheib-fluxcd/workloads     master   sudo /usr/local/Cellar/arping/2.21_1/sbin/arping -i bridge100 <IP_ADDRESS>
ARPING <IP_ADDRESS>
60 bytes from ca:3b:cc:0e:10:69 (<IP_ADDRESS>): index=0 time=6.749 msec
60 bytes from ca:3b:cc:0e:10:69 (<IP_ADDRESS>): index=1 time=2.095 msec
^C
--- <IP_ADDRESS> statistics ---
2 packets transmitted, 2 packets received,   0% unanswered (0 extra)
rtt min/avg/max/std-dev = 2.095/4.422/6.749/2.327 ms

ARP failure from an IP within the MetalLB range, not backed by a service:
 chris@mandalore   ~/src/cscheib-fluxcd/workloads     master   sudo /usr/local/Cellar/arping/2.21_1/sbin/arping -i bridge100 <IP_ADDRESS>
ARPING <IP_ADDRESS>
Timeout
Timeout
Timeout
Timeout
^C
--- <IP_ADDRESS> statistics ---
5 packets transmitted, 0 packets received, 100% unanswered (0 extra)

@candlerb out of curiosity, did you have any loadbalancer services created during your testing?

Yes, as you'll see at https://github.com/ubuntu/microk8s/issues/908 (see kubectl describe service www4).  You can see both the LB address and the pod address it was forwarding to.
Also, the multipass ARP issue I was able to reproduce without microk8s, just by adding IP aliases to VMs: see https://github.com/canonical/multipass/issues/1298

@candlerb the one thing I didn't see you try in your ip alias experiment is specifying the interface with arping.  I was not able to get arping to work properly without specifying the interface (bridge100) from the MacOS side.
This is the procedure I've used to replicate my environment multiple times:
multipass launch --name primary --mem 4G --disk 40G
multipass exec primary -- sudo snap install microk8s --classic --channel=1.18/stable
multipass exec primary -- sudo usermod -a -G microk8s ubuntu
multipass exec primary -- sudo chown -f -R ubuntu ~/.kube
multipass exec primary -- sudo iptables -P FORWARD ACCEPT
multipass exec primary -- /snap/bin/microk8s.enable dns metallb:<IP_ADDRESS>-<IP_ADDRESS>

From there, remaining steps to test/replicate would be:

create any deployment
expose deployment as a service of type LoadBalancer
query the service to see which IP it received (almost certainly <IP_ADDRESS>)
arping -i bridge100 <ip.ad.dr.ess>
multipass exec primary -- sudo ip addr add <IP_ADDRESS>/24 dev enp0s2
with bridge100: arping -i bridge100 <IP_ADDRESS>
without bridge100: arping <IP_ADDRESS>

my arping results with adding an ip via the ip addr method:
 chris@mandalore   ~/src/argocd-demo     master   sudo /usr/local/Cellar/arping/2.21_1/sbin/arping -i bridge100 <IP_ADDRESS>
ARPING <IP_ADDRESS>
60 bytes from ca:3b:cc:0e:10:69 (<IP_ADDRESS>): index=0 time=163.000 usec
60 bytes from ca:3b:cc:0e:10:69 (<IP_ADDRESS>): index=1 time=508.000 usec
60 bytes from ca:3b:cc:0e:10:69 (<IP_ADDRESS>): index=2 time=173.000 usec
^C
--- <IP_ADDRESS> statistics ---
3 packets transmitted, 3 packets received,   0% unanswered (0 extra)
rtt min/avg/max/std-dev = 0.163/0.281/0.508/0.160 ms

 chris@mandalore   ~/src/argocd-demo     master   sudo /usr/local/Cellar/arping/2.21_1/sbin/arping <IP_ADDRESS>
arping: libnet_init(LIBNET_LINK, <null>): libnet_ifaddrlist(): SIOCGIFADDR: dev=en5: Operation not permitted

the one thing I didn't see you try in your ip alias experiment is specifying the interface with arping

I think I tried this, I can't remember for sure.  However, what I definitely did record is that arping the VM primary address from macOS works fine; only arping for the alias fails (and surely it shouldn't be necessary to bind in the second case if the first works).
I then documented a more fundamental problem at https://github.com/canonical/multipass/issues/1298 which means this is irrelevant anyway:

I build two VMs under multipass
I add an alias to one of the VMs
I arping the alias from the other VM

That doesn't work, and it should.  Both VMs have only a single interface, so there's definitely no need to bind arping to an interface.  And as I said before, this problem is nothing to do with microk8s, since I haven't even installed microk8s in those two VMs.
If the above works for you, then most likely something has changed in macOS between 10.14 and 10.15.

I can confirm that MetalLB works fine for me with microk8s, multipass and MacOS 10.15. Apple must have changed HyperKit networking in Catalina 10.15 vs. Mojave 10.14, but this does work for me.

Could the ARP problem have something to do with the fact that metallb uses DNAT?
http://linux-ip.net/html/nat-dnat.html

In a devilishly subtle difference, netfilter DNAT does not cause the kernel to answer ARP requests for the NAT IP, where iproute2 NAT automatically begins answering ARP requests for the NAT IP.

I don't think so.  As mentioned above, HyperKit networking is broken in macOS 10.14 anyway.  Two HyperKit VMs on the same network can't ARP for each other's IP aliases.  This problem reproduces without even bringing metallb into the equation.
I think this issue can be closed, as it's nothing that microk8s or metallb can fix.

Or before closing you might want to update the note which was added in https://github.com/canonical-web-and-design/microk8s.io/pull/205/files to say that this only applies to some versions of macOS.


Text Boxes for use when publishing tasks

It is really helpful to be able to add inert text to a task (e.g. for detailed instructions). Right now, it seems, this can't be done with the Daemo task publisher unless you host the text externally.
It would be great to have a built in solution.

duplicate


TreeServer.handleGetDirectory does not subscribe to child parameters

Per the Ember+ specification, a getDirectory on a Node indicates

that a consumer is interested in the entities below the node the command has been sent for.  That means, that parameters belonging to this node should report value changes to the consumer automatically.

Currently it seems TreeServer.handleGetDirectory() only creates a subscription for Matrix and Parameter elements when the getDirectory is called directly on the Matrix/Parameter, but not for child Matrix/Parameter elements when called on a Node.
Checking if element.getChildren() returns an array and then subscribing to all elements within the array seems to be a crude fix.

I have added a fix in 1.7.23


CompletableFuture Issue - Occationally,

After adopting CompletableFuture and Stream API under Hibernate JPA for oracle database queries, from my observation, occasionally one failed request(timeout) is going to cause massively failure with below exception:
2016-11-01 11:28:48 DEBUG LogicalConnectionImpl:226 - Obtaining JDBC connection
2016-11-01 11:28:48 DEBUG SqlExceptionHelper:139 - Could not open connection [n/a]
com.alibaba.druid.pool.GetConnectionTimeoutException: wait millis 60001, active 12, maxActive 160
No findings yet for root cause, however, found an similar, expert, please help look in if not too much.
Much appreciated!
Reference:
https://issues.apache.org/jira/browse/HBASE-15560?focusedCommentId=15275490&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15275490
Ben Manes added a comment - 08/May/16 06:19
Druid was recently struck by JDK-8078490 - Missed submissions in ForkJoinPool. This caused the cache to stop evicting because the asynchronous task was never run due to a race in the executor. The result was either a memory leak (2.2.6) or halting due to the back pressure (2.3.0). The solution if you are running on an older JDK8 release is to use a different executor (e.g. same-thread). This critical bug effected 8u40 - 8u60 (current is 8u92) and broke any FJP usage, such as CompletableFuture. I confirmed this fix with Doug Lea when investigating.

After upgrading to latest jdk 8U112 for one of the app, the issue seems gone, keep an eye on it, still though...

Per observation, so far so good, marked as resolved.


[firebase_crashlytics] web support

Web support for Firebase Crashlytics is currently missing. As Flutter for web is more mature, we should add web support for firebase_crashlytics. This would be useful especially for logging Exceptions and Errors within the web app.

Currently, on web, Crashlytics#onError method has no implementation.
Error: MissingPluginException(No implementation found for method Crashlytics#onError on channel plugins.flutter.io/firebase_crashlytics)

I think I read on another issue that Dart supports Crashlytics from within, so there isn't a big need to use Crashlytics outside of the main flutter app.
So I think this can be closed.

Hello. Crashlytics only currently supports Android, iOS and Unity therefore we can't bridge web support as no underlying SDK exists.
I'd advise adding an upvote here and submitting a feature request.
Closing this as it isn't actionable.