mongo setup not working

I am new to this stack and would like my starter to work "out of the box".
I installed mongodb like so:
https://www.howtoforge.com/tutorial/install-mongodb-on-ubuntu-16.04/
When I try to run it I get:
$ npm start

><EMAIL_ADDRESS>start /home/ubuntu/projects/project2
> npm run build && npm run watch

><EMAIL_ADDRESS>build /home/ubuntu/projects/project2
> npm run build-sass && npm run build-ts && npm run tslint && npm run copy-static-assets

><EMAIL_ADDRESS>build-sass /home/ubuntu/projects/project2
> node-sass src/public/css/main.scss dist/public/css/main.css

Rendering Complete, saving .css file...
Wrote CSS to /home/ubuntu/projects/project2/dist/public/css/main.css

><EMAIL_ADDRESS>build-ts /home/ubuntu/projects/project2
> tsc

><EMAIL_ADDRESS>tslint /home/ubuntu/projects/project2
> tslint -c tslint.json -p tsconfig.json

><EMAIL_ADDRESS>copy-static-assets /home/ubuntu/projects/project2
> node copyStaticAssets.js

><EMAIL_ADDRESS>watch /home/ubuntu/projects/project2
> concurrently -k -p "[{name}]" -n "Sass,TypeScript,Node" -c "yellow.bold,cyan.bold,green.bold" "npm run watch-sass" "npm run watch-ts" "npm run serve"

[Node]
[Node] ><EMAIL_ADDRESS>serve /home/ubuntu/projects/project2
[Node] > nodemon dist/server.js
[Node]
[TypeScript]
[TypeScript] ><EMAIL_ADDRESS>watch-ts /home/ubuntu/projects/project2
[TypeScript] > tsc -w
[TypeScript]
[Sass]
[Sass] ><EMAIL_ADDRESS>watch-sass /home/ubuntu/projects/project2
[Sass] > node-sass -w src/public/css/main.scss dist/public/css/main.css
[Sass]
[Node] [nodemon] 1.11.0
[Node] [nodemon] to restart at any time, enter `rs`
[Node] [nodemon] watching: *.*
[Node] [nodemon] starting `node dist/server.js`
[Node] Unhandled rejection MongoError: not authorized on admin to execute command { listIndexes: "sessions", cursor: {} }
[Node]     at Function.MongoError.create (/home/ubuntu/projects/project2/node_modules/mongodb-core/lib/error.js:31:11)
[Node]     at queryCallback (/home/ubuntu/projects/project2/node_modules/mongodb-core/lib/cursor.js:212:36)
[Node]     at /home/ubuntu/projects/project2/node_modules/mongodb-core/lib/connection/pool.js:469:18
[Node]     at _combinedTickCallback (internal/process/next_tick.js:131:7)
[Node]     at process._tickCallback (internal/process/next_tick.js:180:9)
[Node] [nodemon] restarting due to changes...
[Node] [nodemon] starting `node dist/server.js`
[Node] [nodemon] restarting due to changes...
[Node] [nodemon] starting `node dist/server.js`
[Node] [nodemon] restarting due to changes...
[Node] [nodemon] restarting due to changes...
[Node] [nodemon] restarting due to changes...
[Node] [nodemon] starting `node dist/server.js`
[Node] [nodemon] restarting due to changes...
[Node] [nodemon] restarting due to changes...
[TypeScript] 21:13:36 - Compilation complete. Watching for file changes.
[TypeScript]
[TypeScript]
[Node] [nodemon] restarting due to changes...
[Node] [nodemon] starting `node dist/server.js`
[Node] Unhandled rejection MongoError: not authorized on admin to execute command { listIndexes: "sessions", cursor: {} }
[Node]     at Function.MongoError.create (/home/ubuntu/projects/project2/node_modules/mongodb-core/lib/error.js:31:11)
[Node]     at queryCallback (/home/ubuntu/projects/project2/node_modules/mongodb-core/lib/cursor.js:212:36)
[Node]     at /home/ubuntu/projects/project2/node_modules/mongodb-core/lib/connection/pool.js:469:18
[Node]     at _combinedTickCallback (internal/process/next_tick.js:131:7)
[Node]     at process._tickCallback (internal/process/next_tick.js:180:9)

As you can see Mongo is giving me an error.

Also, if you could let me know how to access the app from my laptop's browser that would be great.

Cloned this repo today and MongoDB works fine for me.
MongoDB version: v3.4.9

I agree 👍


Provide a setter for emulator host

Is your feature request related to a problem? Please describe.
When I write an integration test and I use a new emulator instance every test with different port numbers, I need to copy the setup logic from FirestoreOptions.Builder.build to configure the connection.
Describe the solution you'd like
I would like to see a setter for the emulator host value, which overrides the value of FIRESTORE_EMULATOR_HOST.
I tried to implement it to clarify my intention:
commit d5e6586e3ba78f3cda6dec0b6a0fb9dcec807cfb
Author: Tobias Happ<EMAIL_ADDRESS>Date:   2020-08-06 21:31:12 +0200

    feat: add getEmulatorHost for FirestoreOptions
---
 .../google/cloud/firestore/FirestoreOptions.java   | 23 +++++++++++++++++++++-
 1 file changed, 22 insertions(+), 1 deletion(-)

diff --git a/google-cloud-firestore/src/main/java/com/google/cloud/firestore/FirestoreOptions.java b/google-cloud-firestore/src/main/java/com/google/cloud/firestore/FirestoreOptions.java
index a65abca..4542504 100644
--- a/google-cloud-firestore/src/main/java/com/google/cloud/firestore/FirestoreOptions.java
+++ b/google-cloud-firestore/src/main/java/com/google/cloud/firestore/FirestoreOptions.java
@@ -63,6 +63,7 @@ public final class FirestoreOptions extends ServiceOptions<Firestore, FirestoreO
   private final boolean timestampsInSnapshotsEnabled;
   private final TransportChannelProvider channelProvider;
   private final CredentialsProvider credentialsProvider;
+  private final String emulatorHost;

   public static class DefaultFirestoreFactory implements FirestoreFactory {

@@ -117,12 +118,17 @@ public final class FirestoreOptions extends ServiceOptions<Firestore, FirestoreO
     return channelProvider;
   }

+  public String getEmulatorHost() {
+    return emulatorHost;
+  }
+
   public static class Builder extends ServiceOptions.Builder<Firestore, FirestoreOptions, Builder> {

     @Nullable private String databaseId = null;
     @Nullable private Boolean timestampsInSnapshotsEnabled = null;
     @Nullable private TransportChannelProvider channelProvider = null;
     @Nullable private CredentialsProvider credentialsProvider = null;
+    @Nullable private String emulatorHost = null;

     private Builder() {}

@@ -132,6 +138,7 @@ public final class FirestoreOptions extends ServiceOptions<Firestore, FirestoreO
       this.timestampsInSnapshotsEnabled = options.timestampsInSnapshotsEnabled;
       this.channelProvider = options.channelProvider;
       this.credentialsProvider = options.credentialsProvider;
+      this.emulatorHost = options.emulatorHost;
     }

     /**
@@ -189,6 +196,16 @@ public final class FirestoreOptions extends ServiceOptions<Firestore, FirestoreO
       return this;
     }

+    /**
+     * Sets the emulator host to use with this Firestore client.
+     *
+     * @param emulatorHost The Firestore emulator host to use with this client.
+     */
+    public Builder setEmulatorHost(@Nonnull String emulatorHost) {
+      this.emulatorHost = emulatorHost;
+      return this;
+    }
+
     @Override
     @Nonnull
     public FirestoreOptions build() {
@@ -201,7 +218,9 @@ public final class FirestoreOptions extends ServiceOptions<Firestore, FirestoreO
       }

       // Override credentials and channel provider if we are using the emulator.
-      String emulatorHost = System.getenv(FIRESTORE_EMULATOR_SYSTEM_VARIABLE);
+      if (emulatorHost == null) {
+        emulatorHost = System.getenv(FIRESTORE_EMULATOR_SYSTEM_VARIABLE);
+      }
       if (emulatorHost != null) {
         // Try creating a host in order to validate that the host name is valid.
         try {
@@ -290,6 +309,8 @@ public final class FirestoreOptions extends ServiceOptions<Firestore, FirestoreO
         builder.credentialsProvider != null
             ? builder.credentialsProvider
             : GrpcTransportOptions.setUpCredentialsProvider(this);
+
+    this.emulatorHost = builder.emulatorHost;;
   }

   private static class FirestoreDefaults implements ServiceDefaults<Firestore, FirestoreOptions> {

Describe alternatives you've considered
The alternative is to copy the setup logic used in FirestoreOptions.Builder.build but this does unnecessarily increase code duplication and complexity.
Additional information
I would like to contribute to help this feature request get implemented. I am looking forward for your feedback!

Hi @Gerschtli
Thank you so much for helping to make our SDK better!
I think having a host settings on top of env variable is very helpful for integration tests, can you open up a PR if that is OK with you?
Also, changing public API surface requires to be reviewed by our API team (across all SDKs), so the actual approval for you PR might come a bit slow.
Thank you again!

One thing to keep in mind as you are working on this. When an emulator is connected to there is additional setup that has to take place. Hopefully, adding the parameter will be enough and the rest of the code will be just fine, however if not; things to look into:

Ensure that the connection to the emulator is plaintext since the emulator only supports http
Ensure that the credentials pass the necessary headers to allow the emulator to perform admin actions see EmulatorCredentials

FWIW, you can also just use below snippet to setup tests against emulator:
    FirestoreOptions firestoreOptions = FirestoreOptions.newBuilder()
            .setChannelProvider(InstantiatingGrpcChannelProvider.newBuilder()
                    .setEndpoint("localhost:8080")
                    .setChannelConfigurator(
                            new ApiFunction<ManagedChannelBuilder, ManagedChannelBuilder>() {
                              @Override
                              public ManagedChannelBuilder apply(ManagedChannelBuilder input) {
                                return input.usePlaintext();
                              }
                            })
                    .build())
            .setCredentials(new FirestoreOptions.EmulatorCredentials())
            .build();
    Firestore firestore = firestoreOptions.getService();

Thank you for your responses. I will try creating a PR for this.
@wu-hui Yes this works, but why should a user of the library copy-paste this snippet over and over? A more concise API would be easier to understand and maintain.


rendering issues after update

hi, after the update on the CDN happened, I got reports that some rendering doesn't work. initially, i thought it is only due to caching, but it seems to be not the only problem. interestingly, the problem resolved after changing the renderer in the context menu from html-css to svg and then back to html-css. therefore i suspect it could be related to the cookie, hence that the new code has problems reading the older cookie. is this possible?
you can see a screenshot here

this is likely related to some jquery processing, don't worry about it until we have figured it out.

Right.  I read the discussion you link to and rendering into a container with display:none definitely can cause layout problems.  As is pointed out in comment 9 in that conversation, you can't measure the size of elements when they are display:none, so MathJax does its rendering in a separate DIV that it adds at the beginning of the page hoping that the sizes will be right when moved to the correct position on the page.  That turns out not to be the case here.
The solution suggestion in comment 11 looks like it will work properly.


Performance Optimization

Use fasthttp to improve webhook performance
Fix Log level
Add local dockerfile
Add README
Set cpu 10m/50m as default resource allocation for hw-event-proxy

Signed-off-by: Jack Ding<EMAIL_ADDRESS>

/lgtm


Create 599.is-cool.dev.json

Requirements

[x] You have completed your website.
[x] The website is reachable.
[x] You have put a full stop (.) at the end of each of the CNAME, MX and NS records.
[x] The CNAME record doesn't contain https:// or /.
[x] There is sufficient information at the owner field.

Description

Link to Website

I have read the CLA Document and I hereby sign the CLA

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

**CLA助手精简版机器人：**感谢您的提交，我们非常感谢。与许多开源项目一样，我们要求您先签署我们的贡献者许可协议，然后我们才能接受您的贡献。您只需发布与以下格式相同的拉取请求注释即可对 CLA 进行签名。
我已阅读CLA文件，并特此签署CLA
您可以通过在此拉取请求中评论重新检查来重新触发此机器人

yes

我已阅读CLA文件，并特此签署CLA

I have read the CLA Document and I hereby sign the CLA

recheck

recheck in this

I have read the CLA Document and I hereby sign the CLA

pull_request_target

pull_request_target

I have read the CLA Document and I hereby sign the CLA

recheck

Recheck


Remove crypto

I don't believe anyone uses it, and it doesn't really have any benefit as an example or default theme. Perhaps we should include neuron or synapse in its place? (or even @xPaw's custom theme)

Until we have any kind of improvement on theme management (such as my failed https://github.com/thelounge/lounge/commit/a74051666b00e5861a5a4be9af5571f8a0256f76), I would not want to get rid of any theme we currently ship.
Simply loading themes from <lounge_config>/themes on top of the ones we ship would do. Then we can move Crypto to its own repo, mention it's now unmaintained and ask for people to maintain it, and I'd be okay with that.

Closing this. We'll get rid of Crypto when we can easily manage third-party themes :D
And it's not like keeping Crypto around is a major impediment to contributions, at least not now.


BibRecord: detect invalid tag values in datafields and controlfields

Originally on 2010-08-03
BibRecord should check and report invalid values in the tag attribute of datafields and controlfields (when parsing record with correct=1). For eg. the following should report an invalid MARCXML:
<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
<record>
  <controlfield tag="001">1282443</controlfield>
  <datafield tag="005" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">CERN leads the way with novel beam extraction</subfield>
  </datafield>
</record>

since the tag attribute of a datafield cannot be in 000-009. The MARC 21 XML Schema
xmlmarclint and BibUpload would inherit from this enhancement. Side effects should be analyzed (for eg. already erroneous uploaded documents might not be fixable afterwards, see task #224)

There is no PR for this issue, hence closing it as per the legacy code base freeze; it is addressed in master code base differently.


Create powershell-jun-lock

PR Summary

PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[ ] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[ ] Documentation needed
- [ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

Please re-open with some context about what this file is and why it needs to be here.
Also, why does it need to be in the root of the repo?


scope.block.parent is null, trying to reference scope.block.parent.key

Using<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>On OS X, the linter works fine. On our Ubuntu build system, it seems to fail:
[21:04:34][:npmInstall] > eslint . && rm -rf public/js && VAULT_CONFIG=prod NODE_ENV=production webpack
[21:04:34][:npmInstall]
[21:04:56][:npmInstall] /mnt/work/teamcity/agent/work/3add2f360809ff9d/www/vault-server/node_modules/eslint-plugin-react/lib/util/component.js:45
[21:04:56][:npmInstall]     scope.block.parent.key && scope.block.parent.key.name === 'render'
[21:04:56][:npmInstall]                       ^
[21:04:56][:npmInstall] TypeError: Cannot read property 'key' of null
[21:04:56][:npmInstall]     at Object.isReactComponent (/mnt/work/teamcity/agent/work/3add2f360809ff9d/www/vault-server/node_modules/eslint-plugin-react/lib/util/component.js:45:23)
[21:04:56][:npmInstall]     at EventEmitter.ReturnStatement (/mnt/work/teamcity/agent/work/3add2f360809ff9d/www/vault-server/node_modules/eslint-plugin-react/lib/rules/no-multi-comp.js:42:26)
[21:04:56][:npmInstall]     at emitOne (events.js:82:20)
[21:04:56][:npmInstall]     at EventEmitter.emit (events.js:169:7)
[21:04:56][:npmInstall]     at NodeEventGenerator.enterNode (/mnt/work/teamcity/agent/work/3add2f360809ff9d/www/vault-server/node_modules/eslint/lib/util/node-event-generator.js:42:22)
[21:04:56][:npmInstall]     at CommentEventGenerator.enterNode (/mnt/work/teamcity/agent/work/3add2f360809ff9d/www/vault-server/node_modules/eslint/lib/util/comment-event-generator.js:98:23)
[21:04:56][:npmInstall]     at Controller.controller.traverse.enter (/mnt/work/teamcity/agent/work/3add2f360809ff9d/www/vault-server/node_modules/eslint/lib/eslint.js:783:36)
[21:04:56][:npmInstall]     at Controller.__execute (/mnt/work/teamcity/agent/work/3add2f360809ff9d/www/vault-server/node_modules/eslint/node_modules/estraverse/estraverse.js:397:31)
[21:04:56][:npmInstall]     at Controller.traverse (/mnt/work/teamcity/agent/work/3add2f360809ff9d/www/vault-server/node_modules/eslint/node_modules/estraverse/estraverse.js:495:28)
[21:04:56][:npmInstall]     at EventEmitter.module.exports.api.verify (/mnt/work/teamcity/agent/work/3add2f360809ff9d/www/vault-server/node_modules/eslint/lib/eslint.js:780:24)

We were missing grunt-cli in our package list and installed it, now works. Unsure how that would impact anything though since eslint isn't using grunt here. Just wanted to note how we fixed it on our end.

Very weird. I don't really see what's going on here, you should not have any difference between OSX/Ubuntu. Maybe you're linting your node_modules directory and the installed dependencies are not exactly the same ?
I'm closing this issue since the problem seems to be resolved for you. Feel free to reopen it if you encounter the same crash again.


Errors during IPv4 defragmenting

Describe the bug
During testing with the Maxwell Pro, with quite a few IPv4 defragmenting tests errors occurred on the console indicating the error in the IPv4 fragmenting stacks. The list of failing IPv4 fragmenting is given by:
https://github.com/zephyrproject-rtos/test_results/issues?q=is%3Aissue+is%3Aopen++Fragment+IPv4
The testsuite used the echo server sample with the config
The bug is reproduced by feeding fragmented packets to the echo server with the config file of:
https://github.com/hakehuang/zephyr/blob/tcp_ip_testing_maxwell/samples/net/sockets/echo_server/overlay-maxwell.conf
Expected behavior
IPv4 fragmenting should work and running it should not throw errors
Impact
At least a significant portion of the IPv4 fragmenting tests are failing.
Logs and console output
Some logging provide by @hakehuang :
 net_ipv4: Reassembled IPV4 verify failed, dropping id 215
 net_ipv4: no slots available for 0xd7
 net_ipv4: no slots available for 0xd7
…
Or
 net_ipv4: no slots available for 0xc

So I see IPv4 fragmentation Kconfigs are set in that configuration, but NET_IPV4_FRAGMENT_MAX_PKT is not updated from the default of 2, so whilst 16 incoming packets can be fragmented, there can only be 2 fragments per packet. What is actually being used to test here - what is the size of the packets? What is the MTU of the transport? What are the fragment sizes? Because from the linked tests there, nearly all mention 4 fragments, which isn't going to work in the default configuration

So I see IPv4 fragmentation Kconfigs are set in that configuration, but NET_IPV4_FRAGMENT_MAX_PKT is not updated from the default of 2, so whilst 16 incoming packets can be fragmented, there can only be 2 fragments per packet. What is actually being used to test here - what is the size of the packets? What is the MTU of the transport? What are the fragment sizes? Because from the linked tests there, nearly all mention 4 fragments, which isn't going to work in the default configuration

@hakehuang could you please fill in the missing information here from the Maxwell reports?

@hakehuang could you please fill in the missing information here from the Maxwell reports?

@carlescufi
this is the failure reason：
tcp.v4 got no echo response, which is not an expected result.
Datagrams are fragmented into MTU sized chunks, starting at the front of the datagram. The fragments overlap with fragment N+1 overlapping the end of fragment N by 16 bytes (two Network Fragmentation Blocks). E.g. Here is a sequence of NFBs in the fragments each holding 6 NFBs:

pkt 0: ABCDEF
pkt 1:     EFGHIJ
pkt 2:         IJKLMN
...

The MTU is 512. A final short fragment may occur at the end. Fragments are transmitted in order of increasing segment offset.

With the configuration linked above, anything with more than 2 fragments will be discarded.

I took a look at the code and as I understand it that NET_IPV4_FRAGMENT_MAX_COUNT give the maximum number of packets of which fragments can be kept, which each maximally NET_IPV4_FRAGMENT_MAX_PKT fragments,
The required memory space is the product of both for that reason.
For the Maxwell Pro tests can be rather small (4) or something like that, but the number of required NET_IPV4_FRAGMENT_MAX_PKT could be large, like > 16.
Or am I misunderstanding things wrongly?

That sounds about right. I assume it would be running 1 test at a time, with 1 connection (or maybe a few) but if it's trying to test things like reassembly then it will be using many fragments of a small size.

After rethinking, as far as I understand the code of IPv4 and IPv6 fragmenting, they only recombine at the end when all fragments are present, there is no recombination of already adjacent fragments in the meantime?
Is it designed to handle overlapping segments?
I see a lot similarities with the out of order reception logic of TCP.
https://github.com/zephyrproject-rtos/zephyr/blob/a5e04ccd4ab976b99f45d106e3de873fc8dd882a/subsys/net/ip/tcp.c#L770
and
https://github.com/zephyrproject-rtos/zephyr/blob/a5e04ccd4ab976b99f45d106e3de873fc8dd882a/subsys/net/ip/tcp.c#L1860
It took me considerable time to get that to work OK by modifying in the original structure. At the moment is only able to handle a single section of out of order data. I'm not 100% happy with the code structure and I see a lot of similarities with the IP defragmenting. In an ideal case, it would be nice to put the ordering logic into a common piece of code separated from the protocol specifics and use it in TCP, IPv4 and IPv6. This would also help in the testing.

@nordicjm: In the following branch: https://github.com/ssharks/zephyr/tree/net/ip4v_frag_test
I created a few tests that test with customized fragmented packets. Reversed order fragments are processed correctly, similar as 4 fragments, although the stack does not accept overlapping fragments, which are contributing for the most failing tests. Feel free to modify the test or provide feedback.

Correct, it does not work with overlapping fragments. To which I would argue there's not really much point in supporting anyway, the IPv4 RFC is from 1981 - that's 42 years ago, technology has moved on vastly since then, we don't have dial up links or slow serial links between routers these days, I think you would be far stretched to find any sort of networking device released in the past 15 years that has a MTU of less than 1500 bytes. So from my point of view, unless there is a real need for a complex system capable of dealing with overlapping fragments, is support for it really needed? It makes the code use more flash space and work in a more complex way for what is probably not needed, also given that devices these days are even using 64KB jumbo frames.

Correct, it does not work with overlapping fragments. To which I would argue there's not really much point in supporting anyway, the IPv4 RFC is from 1981 - that's 42 years ago, technology has moved on vastly since then, we don't have dial up links or slow serial links between routers these days, I think you would be far stretched to find any sort of networking device released in the past 15 years that has a MTU of less than 1500 bytes. So from my point of view, unless there is a real need for a complex system capable of dealing with overlapping fragments, is support for it really needed? It makes the code use more flash space and work in a more complex way for what is probably not needed, also given that devices these days are even using 64KB jumbo frames.

@ssharks @rlubos could you please assess whether @nordicjm's suggestion to simply not do anything about this since he does not deem it worthwhile is OK with you?

@ssharks @rlubos could you please assess whether @nordicjm's suggestion to simply not do anything about this since he does not deem it worthwhile is OK with you?

Fine by me. IPv6 explicitly forbids handling of overlapping fragments (due to security concerns), so unless there's a strong need to have this feature, I don't see a good reason to implement it merely for the sake of satisfying Maxwell pro.


savings_flexible_product_position() - asset argument is not mandatory

FIX issue #146

Resolved with https://github.com/binance/binance-connector-python/pull/153


vcpkg install --head fails in some environments due to GitHub API rate limits; vcpkg should allow us to provide GitHub credentials for authenticated GitHub API requests

Describe the bug
We're running into issues when using vcpkg install --head anywhere within NVIDIA's corporate VPN, including personal developer workstations and our CI system.
The problem appears to be that vcpkg install --head will attempt to access api.github.com methods unauthenticated (e.g. without providing an authentication token/API key), which fails due to GitHub API rate limits, presumably because there's other things within our corporate VPN that are hammering GitHub APIs.
We recognize this is probably more of our problem than your problem, but we've got no idea how to workaround this.
It is highly unlikely that we'll be able to track down or stop the sources of all the GitHub API requests that are being made elsewhere at NVIDIA and are interfering with our usage of vcpkg.
GitHub's API supports authenticated requests. Authenticated requests not only get a higher API rate limit, but the rate limit is counted per-user, instead of per site/per IP. However, I couldn't find a way to pass a GitHub personal access tokens/etc to vcpkg. Adding a way to pass GitHub personal access tokens/etc to the vcpkg command line tool to be used for all GitHub API requests would solve this issue. I think more than just GitHub personal access tokens should be supported (like GitHub Enterprise credentials or repo credentials if that's a thing), but personal access tokens would be a good start.
$ curl https://api.github.com/repos/pantor/inja/git/refs/heads/master
{"message":"API rate limit exceeded for <IP_ADDRESS>. (But here's the good
news: Authenticated requests get a higher rate limit. Check out the documentation
for more details.)",
"documentation_url":"https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"}
$ curl -u brycelelbach:${GITHUB_AUTH_TOKEN} https://api.github.com/repos/pantor/inja/git/refs/heads/master
{
  "ref": "refs/heads/master",
  "node_id": "MDM6UmVmMTAwMTA5MzAwOnJlZnMvaGVhZHMvbWFzdGVy",
  "url": "https://api.github.com/repos/pantor/inja/git/refs/heads/master",
  "object": {
    "sha": "2ba5783705da8638683f7b7a8b6771a9738d7127",
    "type": "commit",
    "url": "https://api.github.com/repos/pantor/inja/git/commits/2ba5783705da8638683f7b7a8b6771a9738d7127"
  }
}

https://docs.github.com/en/developers/apps/building-github-apps/rate-limits-for-github-apps
https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token
To Reproduce
docker run -i ubuntu:20.04 /bin/bash -s << EOF
apt-get -y update > /dev/null 2>&1
apt-get -y install git curl zip unzip tar g++ > /dev/null 2>&1
git clone https://github.com/microsoft/vcpkg /tmp/vcpkg 2>&1
/tmp/vcpkg/bootstrap-vcpkg.sh
/tmp/vcpkg/vcpkg --head install inja
EOF

Failure logs
$ docker run -i ubuntu:20.04 /bin/bash -s << EOF
apt-get -y update > /dev/null 2>&1
apt-get -y install git curl zip unzip tar g++ > /dev/null 2>&1
git clone https://github.com/microsoft/vcpkg /tmp/vcpkg 2>&1
/tmp/vcpkg/bootstrap-vcpkg.sh
/tmp/vcpkg/vcpkg --head install inja
EOF
Cloning into '/tmp/vcpkg'...
Downloading cmake...
Downloading cmake... done.
Extracting cmake...
Extracting cmake... done.
Downloading ninja...
Downloading ninja... done.
Extracting ninja...
Extracting ninja... done.
Downloading vcpkg tool sources
Building vcpkg-tool...

The data collected by Microsoft is anonymous.
You can opt-out of telemetry by re-running the bootstrap-vcpkg script with -disableMetrics,
passing --disable-metrics to vcpkg on the command line,
or by setting the VCPKG_DISABLE_METRICS environment variable.

Read more about vcpkg telemetry at docs/about/privacy.md
Computing installation plan...
The following packages will be built and installed:
    inja[core]:x64-linux -> 3.2.0 (+HEAD)
  * nlohmann-json[core]:x64-linux -> 3.9.1
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-linux...
Could not locate cached archive: /root/.cache/vcpkg/archives/ef/ef8eae8cfe4cd361bbfa4442a297140dab61a8632529693b94219e95801c42e8.zip
Starting package 1/2: nlohmann-json:x64-linux
Building package nlohmann-json[core]:x64-linux...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/CMakeLists.txt -> nlohmann-json-v3.9.1/CMakeLists.txt...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/LICENSE.MIT -> nlohmann-json-v3.9.1/LICENSE.MIT...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/nlohmann_json.natvis -> nlohmann-json-v3.9.1/nlohmann_json.natvis...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/cmake/config.cmake.in -> nlohmann-json-v3.9.1/cmake/config.cmake.in...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/cmake/pkg-config.pc.in -> nlohmann-json-v3.9.1/cmake/pkg-config.pc.in...
-- Downloading https://github.com/nlohmann/json/raw/v3.9.1/cmake/nlohmann_jsonConfigVersion.cmake.in -> nlohmann-json-v3.9.1/cmake/nlohmann_jsonConfigVersion.cmake.in...
-- Downloading https://github.com/nlohmann/json/releases/download/v3.9.1/include.zip -> nlohmann-json-v3.9.1-include.zip...
-- Extracting source /tmp/vcpkg/downloads/nlohmann-json-v3.9.1-include.zip
-- Using source at /tmp/vcpkg/buildtrees/nlohmann-json/3.9.1-74ced61d52.clean
-- Configuring x64-linux-dbg
-- Configuring x64-linux-rel
-- Building x64-linux-dbg
-- Building x64-linux-rel
-- Installing: /tmp/vcpkg/packages/nlohmann-json_x64-linux/share/nlohmann-json/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /root/.cache/vcpkg/archives/ef/ef8eae8cfe4cd361bbfa4442a297140dab61a8632529693b94219e95801c42e8.zip
Building package nlohmann-json[core]:x64-linux... done
Installing package nlohmann-json[core]:x64-linux...
Installing package nlohmann-json[core]:x64-linux... done
Elapsed time for package nlohmann-json:x64-linux: 6.994 s
Starting package 2/2: inja:x64-linux
Building package inja[core]:x64-linux from HEAD...
-- Downloading https://api.github.com/repos/pantor/inja/git/refs/heads/master -> pantor-inja-master.tar.gz.version...
-- Downloading https://api.github.com/repos/pantor/inja/git/refs/heads/master... Failed. Status: 22;"HTTP response code said error"
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:251 (message):

      Failed to download file.
      If you use a proxy, please check your proxy setting. Possible causes are:

      1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
         to `https://address:port`. This is not correct, because `https://` prefix
         claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
         , etc..) is an HTTP proxy. Try setting `http://address:port` to both
         HTTP_PROXY and HTTPS_PROXY instead.

      2. You are using Fiddler. Currently a bug (https://github.com/microsoft/vcpkg/issues/17752)
         will set HTTPS_PROXY to `https://fiddler_address:port` which lead to problem 1 above.
         Workaround is open Windows 10 Settings App, and search for Proxy Configuration page,
         Change `http=address:port;https=address:port` to `address`, and fill the port number.

      3. You proxy's remote server is out of service.

      In future vcpkg releases, if you are using Windows, you no longer need to set
      HTTP(S)_PROXY environment variables. Vcpkg will simply apply Windows IE Proxy
      Settings set by your proxy software. See (https://github.com/microsoft/vcpkg-tool/pull/49)
      and (https://github.com/microsoft/vcpkg-tool/pull/77)

      Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Call Stack (most recent call first):
  scripts/cmake/vcpkg_from_github.cmake:153 (vcpkg_download_distfile)
  ports/inja/portfile.cmake:1 (vcpkg_from_github)
  scripts/ports.cmake:141 (include)

Error: Building package inja:x64-linux failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `./vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: inja:x64-linux
  Vcpkg version: 2021-07-21-unknownhash

Additionally, attach any relevant sections from the log files above.

https://github.com/microsoft/vcpkg/pull/19077/ may help

Duplicated to #19078.
Since the changes in #19077 have been merged to vcpkg master branch now.
Could you please try to update vcpkg to the latest commit via git pull to rebuild this? @brycelelbach

We could also change --head to not use any github APIs and instead:

Switch over to vcpkg_from_git()
Just directly download master.zip instead of trying to identify+cache the precise commit

#19077 doesn't really fix the primary issue, which is that public ports like inja will fail. #19077 would fix this issue for a private port that already has an auth token parameter in non-head mode.

I very much like the idea of not using GitHub APIs, that'd be much better from my end.


DLC-Link application

Project Abstract
The DLC.link project aims to implement Discreet Log Contracts (DLCs), an innovative technology designed at MIT that allows native Bitcoin integration in a secure, decentralized manner. As Bitcoin does not inherently support smart contracts, financial activities such as lending and trading are currently fraught with risks due to the need for custodians or bridges. DLC.link endeavors to circumvent these limitations by introducing a "trustless bridge" that enables these transactions through on-chain escrow, thereby preventing potential losses due to custodial failures and bridge hacks.
The project's core offerings include a simple wallet integration library for third-party Bitcoin wallets, smart contract libraries on various platforms for seamless integration into web3 decentralized applications, an attestor application for added security and resilience, and developer tooling such as a Health Monitor system and integrated private key vaults. Furthermore, the platform seeks to integrate with the Substrate framework to take advantage of the shared security and interoperability of the Polkadot and Kusama networks. DLC.link aims to revolutionize cross-chain communication, enhance Bitcoin liquidity on other chains, and provide Bitcoin users with increased utility for their assets.
Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[X] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[X] I have read the application guidelines.
[X] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
[X] The software delivered for this grant will be released under an open-source license specified in the application.
[X] The initial PR contains only one commit (squash and force-push if needed).
[X] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I'm closing this application due to inactivity. Let me know if I should reopen it.


DE24835: Only announce the course name when accessing the course link…

…s by giving the anchor an aria-label.

This introduces a host of regressions, unfortunately.


Nechronica: Updated with translation strings and images

Submission Checklist
Required

[X] The pull request title clearly contains the name of the sheet I am editing.
[X] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[X] The pull request makes changes to files in only one sub-folder.
[X] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description
Updated to have i18n translation strings for all fields, labels, and images.
translation.json contains English translation. Original sheet had Korean language. To conform to crowdin source language requirements (and per discussion with Roll20 Support-- see request 151311 in Helpdesk, or ask Miles), I changed the language to English.
Added ko.json, which contains the original Korean language strings. PLEASE PUT THIS IN THE translations/ FOLDER once this sheet has been added to crowdin so that Korean-language users will not have their experience disrupted.
Also moved images from imgur to github and links to images to github.
Did some typo fixes and cleanup, but did not change any attribute names.

Updated sheet.json. Please merge

@mortaine, your sheet.json line should include all the authors' names separated with commas in one string. You currently have three separate strings, which is invalid. I'm also unsure if we can merge the sheet with your ko.json. Our policy says that translation needs to go through crowdin, but that policy is from before a recent upgrade to our translation system. I will confirm for you whether that file can be included in this PR or not.
Once those two things are cleared up, this sheet is good to go!

Thanks. I have fixed the sheet.json file.
For the ko.json translation-- I know translations need to go through Crowdin normally. This sheet was originally submitted in Korean. I do not speak Korean, but had someone translate it into English when I added the translation tags. I put the English into the translation.json file and added the ko.json with the original strings so that existing Korean-language users of this sheet will not have it abruptly change to English on them.
Since I do not speak Korean, I don't think it would be appropriate for me to go through Crowdin and become a Korean translator just so I could submit this one translation file. When I contacted Roll20 Support and hashed it out with Miles, Miles agreed with me that submitting the file separately in this case would be the right way to go about it and the ko.json file would need to be brought into the translations folder manually.

Thanks for the wait, @mortaine! I had to get my own crowdin permissions set up.
Since it's the source language and this update was you initializing translations for this sheet, I can take your korean file and upload it to crowdin manually. The reason we don't typically allow uploads of two-letter language files in PRs is that crowdin will overwrite them whenever anyone makes a change to any language for the sheet. I just didn't want your file to get lost and have Korean users suddenly get that same sudden change to English you were worried about.

@mortaine and it's uploaded!
There are six strings that don't have translations in the file you provided:

Madness
Attack
Add 1 Madness point
Madness Check
Character Information
Roll to attack

If you just want to provide me the strings for those items in a comment here, I can add them manually

Hi, Nora!
Thanks for merging and reaching out for the translation strings. Three of
these should stay as-is, and three of them can be fixed by renaming the
strings in the ko.json file, as follows:
The Character Information string is embedded in an image in the sheet. The
actual text is only shown as an image title; if/when this gets translated
by a Korean translator, overwriting it shouldn't be a problem, and in the
meantime, there is no loss in functionality (the original sheet has no
image titles).
character-info: Character Information
These two strings do not have a Korean equivalent on the sheet. "Attack" is
literally shown in English on the original sheet. "Roll to Attack" is a
title used on a button image-- again, it should be no problem for this to
be overwritten by Crowdin, and there is again no loss in functionality.
attack: Attack
attack-roll: Roll to Attack
These three are due to renaming the string from "insanity" to "madness" in
keeping with the intent of the game-- I must have missed renaming them in
the ko.json file when I did that rename. The strings are in the ko.json
file, but are incorrectly named. These can be fixed this way:
Rename line 15 insanity to madness
Rename line 45 faildescription1insanity to faildescription1madness
Rename line 61 determineinsanity to determinemadness
Thanks!
--Stephanie


Images in Font Documentation

Would be really nice to have images in the font documentation that show what each font looks like.

That sounds like an awesome idea. PRs are welcome!

For sure - once my app gets merged I'll work on this. Should be super easy to do.

Just created a pull request for this.


Py::drop_ref

The documentation for Py currently states that

If a Py<T> is dropped while its thread happens to be holding the GIL then the Python reference count will be decreased immediately. Otherwise, the reference count will be decreased the next time the GIL is reacquired.

(https://docs.rs/pyo3/latest/pyo3/prelude/struct.Py.html#a-note-on-python-reference-counts)
However, Py's drop impl seems to unconditionally call gil::register_decref to defer the decref even when the GIL is currently held (https://docs.rs/pyo3/latest/src/pyo3/instance.rs.html#1010-1014). This may be needed for performance but makes explicit memory management difficult.
In parallel to the explicit Py::clone_ref, I propose adding the following Py::drop_ref method that can be used to explicitly drop a Py if we already hold the GIL:
impl<T> Py<T> {
    pub fn drop_ref(self, py: Python) {
        let _py = py;

        // Safety: we hold the GIL and forget `self` to not trigger a double free
        unsafe { pyo3::ffi::Py_DECREF(self.into_ptr()) };
    }
}

However, Py's drop impl seems to unconditionally call gil::register_decref to defer the decref even when the GIL is currently held (https://docs.rs/pyo3/latest/src/pyo3/instance.rs.html#1010-1014). This may be needed for performance but makes explicit memory management difficult.

Note that gil::register_decref does check if the GIL is held and if so, immediately applies the change, c.f.
https://github.com/PyO3/pyo3/blob/0bb9cab6d312cf308f55204c64381f0fac013493/src/gil.rs#L454
i.e. it does not unconditionally queue up the change in the global REFERENCE_POOL and only applies it on the next acquisition of the GIL and hence managing memory via Py's impl of Drop should already be deterministic.
The drop_ref method you propose would then be a micro-optimization, exactly similar to clone_ref, that mainly avoids calling gil_is_acquired and hence the access to thread-local storage this implies.
Would not open a pull request proposing that addition?

However, Py's drop impl seems to unconditionally call gil::register_decref to defer the decref even when the GIL is currently held (https://docs.rs/pyo3/latest/src/pyo3/instance.rs.html#1010-1014). This may be needed for performance but makes explicit memory management difficult.

Note that gil::register_decref does check if the GIL is held and if so, immediately applies the change, c.f.
https://github.com/PyO3/pyo3/blob/0bb9cab6d312cf308f55204c64381f0fac013493/src/gil.rs#L454-L460
i.e. it does not unconditionally queue up the change in the global REFERENCE_POOL and only applies it on the next acquisition of the GIL and hence managing memory via Py's impl of Drop should already be deterministic.

Woops, my mistake - thanks for the correction :)
I'll submit a PR for the micro-optimisation method still.


Windows support for sdist build

Not for merge, just for checking buildbots

If the buildbots pass, please check if this is mergeable.

Will check.

I have tried to follow your int64_t recommendations, but I must admit I do not fully understand when which should be used, might need another pass.
Just out of curiosity, how does this work on 32-bit Linux, where I think long is 32-bit?
My formatting changes around __extension__ was very bad, I used a macro instead.
I added back the copy-to-sdist script, it will be very hard for others to work with the repo on Windows without it. I made some progress with cmake earlier, perhaps it can go away in the future.
I also added some instructions to the readme.

Now the mac build errored out, perhaps more casts are needed? Will be hard to check since I don't have access to such a environment.
https://travis-ci.org/blue-yonder/turbodbc/jobs/214299096#L1483

Ah, the joys of multi-platforming :-D.
To be completely honest, I am not entirely sure which types are supposed to go where exactly, because the ODBC types are often a mess. It worked with long for a long time, until Windows came along ;-). I think occurrences of SQLPOINTER that may be used as integers (sigh) should be intptr_t, since that represents an integer that is large enough to hold a pointer. I also think that int64_t is the appropriate type for the data exchange stuff, because that's what these types are bound to be. The SQLLEN seems to be something else on OSX again. I'll have to check that.
I am sure it would not work on 32 bit Linux, but the last time I worked with 32 bit Linux system was in 2006, I think. 64 bits is what I am targeting.
There's a few remaining questions for me:

Have you successfully run the integration tests on Windows? If so, with which database/driver?
Not coming from the Windows side, would installing the package be as simple as pip install turbodbc once version 1.1 is pushed to pypi?

Thanks for the changes, I'll see what I can do with the OSX build.

Not coming from the Windows side, would installing the package be as simple as pip install turbodbc once version 1.1 is pushed to pypi?

No, simple answer is because you're only pushing sdists at the moment, and a lot of users are unlikely to have prerequisite headers, maybe, if they have anaconda, but I never looked at this. Best way to ensure it will work like that for windows would be to push a windows bdist_wheel build, which presumably is only possible once travis has been set up with windows builds as well.

It is strange that intptr_t did not trigger the same OSX error, I would assume they are the same size.
It might be good to mention in the readme that only 64-bit is targeted.
Since the CMake build does not yet work, I have not run the tests. (And I can't get them to pass completely on Linux with PostgreSQL either).
For pip install turbodbc to work

Visual C++ 2015 update 3 needs to be installed. (pybind11 has a hard requirement on update 3. This unfortunately excludes the lighter Visual C++ 2015 Build Tools). My guess is that this is somewhat common at least.
Boost need to be installed, bootstrapped and the environment configured so that turbodbc can find it. I imagine this is very uncommon. (If not bootstrapped linking complains about libboost_date_time. When boost date handling goes away, it might be possible to do a source only build.)

In conclusion, without following the readme almost no one will get this working on Windows. If the goal is smooth install experience, a binary wheel is indeed needed.

As it turns out, size is not really the problem. On both OSX and Linux (64 bit), the following types have the same size: long, long long, int64_t, intptr_t, and SQLLEN. However, these types basically have two internal type codes:
On Linux:
type long: l
type long long: x
type int64_t: l
type intptr_t: l
type SQLLEN: l

On OSX:
type long: l
type long long: x
type int64_t: x
type intptr_t: l
type SQLLEN: l

Notice how the type code for int64_t coincides with the type code for SQLLEN on Linux, but differs on OSX, though it uses the same internal representation. On Windows 64 bit I find the following:
type long: long
type long long: __int64
type int64_t: __int64
type intptr_t: __int64
type SQLLEN: __int64

So the end result is this: SQLLEN matches the type code of intptr_ton all three platforms, probably by pure coincidence. It matches the type code of int64_t on two platforms only. The differing type codes essentially prevent automatic casting of pointer types since C++ will consider them separate types. In the interest of avoiding a reinterpret_cast (which would work), I will rework  the type in the buffer thingy to intptr_t.

Thanks for the clarification concerning the status of the Windows build. Experimental seems like a good classification, then.

@TWAC Thanks for all the hard work you put in!

@TWAC It seems like you are not listed as a contributor yet. I guess this may have something to do with the way your git profile on your computer and your Github profile is set up. It would be cool if you could fix that, so people know who to credit ;-).


Add new papers

[ ] Add new papers
Description

Please include a summary of the change and the relevant motivation.
Paper: SPG: Structure-Private Graph Database via SqueezePIR, VLDB 2023 in Yuan Xie Group
[ This paper presents SPG,  a structure-private graph database with SqueezePIR.  SPG is  built on top of Private Information Retrieval (PIR), which securely  hides which nodes/neighbors are accessed.  In addition, this paper propose SqueezePIR, a compression technique to overcome the computation  overhead of PIR.  Based on evaluation, SqueezePIR achieves 11.85× speedup on average with less than 2% accuracy loss when  compared to the state-of-the-art FastPIR protocol]

I have read the CLA Document and I hereby sign the CLA

Thanks for your contribution, you may add your github id to the contributors here: https://github.com/secretflow/secretflow/blob/main/docs/awesome-pets/awesome-pets.md


Switching between JTAG/SWD mode

I am wonder, why I cant find anywhere, how to switch between JTAG/SWD modes. Please can you explain it me? I will use primarily original ST ST-LINK/V2 programmer and I would need to use both modes. Thanks.

The stlink programmers only use SWD (SWO,SWD,SWCLK pins). JTAG is not supported. You should get a different programmer interface (e.g Olimex JTAG) and using OpenOCD application. Or an segger J-Link: https://www.segger.com/products/debug-probes/j-link/.


Add detail_scale and detail_offset properties to BaseMaterial3D

This can be used to adjust the detail texture's offset and scale without having to switch to UV2 for detail mapping. This makes it possible to use lightmapping at the same time as a differently offset or scaled detail texture.
This PR can be remade for 3.x once we agree on this PR's design.
This closes https://github.com/godotengine/godot-proposals/issues/3499.
Testing project: test_basematerial3d_detail_scale.zip
Preview
https://user-images.githubusercontent.com/180032/140591763-a58cd97e-d7d2-474b-9c0e-0f9c494732a7.mp4

Rebased and tested again, it works as expected. I also added PROPERTY_HINT_LINK to the detail_scale property.


trufflehog: 3.63.4 -> 3.63.5

Diff: https://github.com/trufflesecurity/trufflehog/compare/refs/tags/v3.63.4...v3.63.5
Changelog: https://github.com/trufflesecurity/trufflehog/releases/tag/v3.63.5
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 275509 run on x86_64-linux 1

1 package built:

trufflehog


Add Ubuntu packages

Hey, I am the main dev from the Eupnea Project. We are gonna be using keyd in our products and therefore decided to make a keyd package.
Keep in mind that this is not an AUR/PPA/etc... but rather a full repo, hosted on github servers, which includes Eupnea Project specific packages. (The keyd package is not modified in any way)
P.S: Its really time for a new release!
P.P.S: Ill make another PR for rpm packages soon

Unfortunately our use case (running this on Chromebooks) involves re-adding the keyd.quirks file that was removed in 0f2926e1cd15bac90853f8a19a13ddd5a3b1234f. This means our packages do not match upstream anymore.


Fix failing set equality test

Fixes #303

No longer required after this PR: https://github.com/deeplearning4j/DataVec/pull/307
Fix for the aforementioned issue was made in the record reader, instead of modifying the test assumptions.


Internal compiler error when referencing interface member

    Playground link
interface Hello {
  op one(): void;
}

interface World {
  two is Hello.one;
}

Internal Compiler error
File issue at https://github.com/microsoft/cadl
TypeError: Cannot read properties of undefined (reading 'id') at getNodeSymId (https://cadlplayground.z22.web.core.windows.net/libs/@cadl-lang/compiler/index.js:26341:28) at checkOperationIs (https://cadlplayground.z22.web.core.windows.net/libs/@cadl-lang/compiler/index.js:26873:36) at checkOperation (https://cadlplayground.z22.web.core.windows.net/libs/@cadl-lang/compiler/index.js:26817:35) at checkInterfaceMembers (https://cadlplayground.z22.web.core.windows.net/libs/@cadl-lang/compiler/index.js:27887:28) at checkInterface (https://cadlplayground.z22.web.core.windows.net/libs/@cadl-lang/compiler/index.js:27869:9) at getTypeForNode (https://cadlplayground.z22.web.core.windows.net/libs/@cadl-lang/compiler/index.js:26251:24) at checkSourceFile (https://cadlplayground.z22.web.core.windows.net/libs/@cadl-lang/compiler/index.js:27309:13) at Object.checkProgram (https://cadlplayground.z22.web.core.windows.net/libs/@cadl-lang/compiler/index.js:27304:13) at createProgram (https://cadlplayground.z22.web.core.windows.net/libs/@cadl-lang/compiler/index.js:29719:21) at async compile (https://cadlplayground.z22.web.core.windows.net/libs/@cadl-lang/compiler/index.js:30263:12)

I think this gets fixed with https://github.com/microsoft/cadl/pull/703


Add packages for Ubuntu 17.10 Artful Aardvark

Add packages for Ubuntu 17.10 Artful Aardvark
There is no packages available in the repository for Ubuntu 17.10 Artful Aardvark:
https://packages.microsoft.com/repos/microsoft-ubuntu-artful-prod/
Thanks

@rakeshsinghranchi

@leecow is going to publish packages for this very soon.

@leecow did you do this today? I thought I saw some things go by.

Yep, changes are live - https://github.com/dotnet/core/pull/1043


在未登录的情况下不弹出登录界面

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

用Ad block把登录窗口屏蔽就行 不影响使用的


'Return_id_scaling_2NN' now works when the class is initalized with only distance matrices

Thanks @diegodoimo, great enhancement, and I also like the 'single_scale' vs 'multiscale' division and naming.
If you have done all you wanted to do I think we could rebase and merge. Let me know!

Great we can rebase


:bar_chart: migrate GHE from sources to origins

Fix for https://github.com/owid/owid-issues/issues/1564. Adding origins should enable Data pages for GHE.
I didn't spend much time improving the metadata and data pages, so they look pretty terrible. Check out this one for example. There's a long title, no default countries, etc. It's not worse than what it used to be, though. Should we invest time in improving it, or do we just merge it as it is and fix it in the next update?
Changes

use snapshot instead of walden
refactor code
move metadata to origin at snapshot level

Ah, thanks for doing this!
Hmm, yeah, the data pages don't look great, do they? I'm off the rest of the week, but next week I can have a bash at adding some Jinja templating, which wouldn't be much work (just a couple of hours, I guess?) and probably go quite a long way in terms of improving the basic metadata.

That'd be great! This is definitely not urgent.

@Marigold I've had a stab at improving the metadata, I think it's improved enough for this time round, but happy to make some more changes if you think it's worth it.


Initial filter commit + tests

@jmrodri @shawn-hurley Posting a PR to get my filter work into the feature branch; should produce a clean history for the feature branch and we can continue from there. Not looking for a full review, but if there's anything here you think is obviously stupid, call it out and we'll fix it before we continue.

@eriknelson @jmrodri can i merge and we can fix the vet and lint issues after I put my commits on top of this?

@shawn-hurley yep, ACK. I'm not concerned with reds until we merge to master.


[WTD] SCCM Core Inclusion Articles

In support of #1550, here is a list of articles with line numbers of where non gender neutral language is present.


Make SvelteKit compatible with server middlewares

Is your feature request related to a problem? Please describe.
There are a lot of issues that either ask for server side features like SSE, websocket, etc or directly for server side middlewares.
I think the root issue is that the handle hook exposes its own types for request and response, which are not compatible with express middlewares that is the de facto standard in Node.
I get the rationale behind this design, as @Rich-Harris said in #334

it means that the answer to various problems becomes 'use adapter-node, because you can use arbitrary middleware'

However, the current design feels more like making adapter-node a second-class citizen in order to treat every adapter the same.
I recently came across https://github.com/vendia/serverless-express, which seems to contain a solution to this problem.
Describe the solution you'd like
This code converts a request-like object into http.IncomingMessage (there is similar code for http.ServerResponse)
https://github.com/vendia/serverless-express/blob/5cd87c8e7ca3a5e971d26d471cb70a6ac15cc61f/src/request.js#L7-L16
And it's the cornerstone for using middlewares in a serverless environment.
I wonder if it's a good idea to make the handle hook (maybe also endpoints) expose http.IncomingMessage and http.ServerResponse instead? For adaptor-node, the corresponding objects from polka are directly returned, for other adaptors, the aforementioned polyfill is applied.
This should open Svelte Kit to the vast amount of server middlewares that are available.
Describe alternatives you've considered
How important is this feature to you?
Very, not being able use existing middlewares is a deal breaker for many people from the referenced issues.
But it's actually possible to polyfill in userland to use the middlewares.
Additional context

The idea that Rich had suggested was to build a converter between the SvelteKit and Express request and response objects

That works, but if they're convertible, I wonder what's the appeal of exposing the custom types in the first place, and for adapter-node, that seems to mean converting back and forth?

@benmccann Is that suggestion tracked in this repo somewhere? It would make the Firebase adapter (which uses Express APIs) much easier to integrate.

if they're convertible, I wonder what's the appeal of exposing the custom types in the first place

We didn't want to use Express types because not all adapters provide an Express request / response the way adapter-node does.

@benmccann Is that suggestion tracked in this repo somewhere?

I think this is the best issue tracking it

This is a retread of #334.
When this was being discussed internally in March (rather heatedly!), where I believe we landed was that, if someone cared enough about supporting the Express middleware API, there could be a community-maintained interop library between that API and what the handle hook provides. Rich wanted a certain amount of friction in place for using things that needed the middleware API, and forcing this to happen with a third-party library in userland was approximately the amount of friction he said he wanted to have.
The outcome of the conversation at the time was summarized in https://github.com/sveltejs/kit/issues/334#issuecomment-806289525 and I don't know how much of the thinking has changed since then.

Thanks for providing the context @Conduitry.
I think the conclusion in #334 is worth revisiting, given the friction manifested in the current design, and the referenced repo shows that it's possible to expose node request & response types  in a serverless environment, which was not mentioned in #334:

it's not enough to have a way to add middleware to adapter-node, because it doesn't apply to svelte-kit dev and svelte-kit start

If handle provides node types, then middleware lives in userland, so it applies to svelte-kit dev and svelte-kit start

ideally there should be some way to use existing connect middlewares, but we don't want to privilege adapter-node over serverless adapters (or CFW etc, when we get round to it)

If request & response from other adapters are polyfilled, then adapter-node is not privileged (at least not completely, streaming data in serverless is something you simply can't workaround or polyfill).

Rich did bring up another point:

I really don't think multer, formidable and passport are the right answers in 2021.

The future-proof thing to do isn't to throw our hands up and say 'we can't possibly anticipate everything people will need to do, therefore we should abdicate the responsibility to the ecosystem of Express middleware'

This raised a very good question that is using middleware a dogma? Is there some room for innovation here? I really hope there is a positive answer here, but given that middleware is not a standalone thing, that they serve the services that bundle them, I think it's at least extremely hard to come up with something new in this space, and the current lowest common denominator approach definitely doesn't seem like the right answer.
If you accept that middleware is currently the most pragmatic approach, I think it really boils down to two choices:

Provide the lowest common denominator, which is the current approach. This treats every adapter the same, but at the cost of hamstringing more capable adapters.
Provide the greatest common factor, but polyfill the rest and document the discrepancies. This does make some less capable adapters less first-class, but they are not second-class either.

But if I have to be honest (also to provide field report), I initially opened the issue for a GraphQL middleware I want to use, but after some experiment, I realized the isomorphic load & fetch design really prioritizes Restful APIs, so I end up putting graphql behind Restful APIs (i.e., directly calling GraphQL in endpoints), obviating the need for middleware. So I no longer have skin in the game currently, but I do see the need for other services (and would probably need middleware again when I need subscription support in GraphQL).
P.S. should I open a new issue about the friction between isomorphism and GraphQL?

The maintainers have discussed this in depth. Some made the same arguments you're making now. While some of the maintainers agree with you, the decision was made in the other direction. Continuing to push for having Express request and response types directly is not going to change anything because these points have all been considered. Continuing to argue the same point will only bury the suggested solution (https://github.com/sveltejs/kit/issues/1610#issuecomment-851830016) making it less likely that someone will see it and work on creating a converter or facade between SvelteKit and Express request / response types.

Should I open a new issue about the friction between isomorphism and GraphQL?

As far as I'm aware, there isn't any friction between isomorphism and GraphQL. It's hard to give more advice without more details. I would suggest discussing on Discord first and seeing if folks have a solution for the issue you're running into or if there's agreement that there's an issue in SvelteKit

because these points have all been considered

I was not aware of that solely from #334. But I respect the decision the maintainers landed on.

creating a converter or facade between SvelteKit and Express request / response types.

As previously mentioned, my only gripe is that seems to punish adapter-node with double conversions.


Add assumeNoImportSideEffects option to .fusionrc.js

This option allows apps to opt into aggressive tree shaking / import pruning by assuming all import statements are side effect free
This means:

Unused specifiers of import statements can be tree shaken (provided the source module is comprised of simple re-export statements)
Completely unused import statements (all specifiers are unused) can be pruned entirely

We may eventually want to turn on some form of behavior on by default. Also, our custom babel tree shaking babel plugin is redundant once dead branches in LogicalExpressions removed in Webpack itself.

!merge


Recreate certs that have expired

In #3274 we talked about the possibility to replace certs that have expired. This PR sets the lifetime of created certs to 90 days (just like Let's Encrypt) and checks if the certs have expired when calling get_cert().
Things I don't like in this PR and would like to improve before merging:

the existing test "test_expire", the method "expire" and the "expire_queue" should be renamed. This is more like a "overflow" than an "expire". Maybe even switch to lru_cache?
the raise ValueError('Certificate has expired', name) feels kina ugly

Any feedback is greatly appreciated!

This would assume you are running mitmproxy for more than 90 days?! 😄
Instead of raising an exception, you could refactor the try block and prevent the KeyError with a if name in self.certs check instead...

To quote @mhils

I personally have a few long-term monitoring projects running for >90 days.

:smiley:
Gave it a shot and replaced the exceptions with a more simpler if/else. Thanks for the hint!

In the end it was just a simple " and not self.certs[name].cert.has_expired:" added to the already existing "if name"-clause. Could have been so simple in the first place... :roll_eyes:

This looks good, thanks! 🍰

On a closer look, CI uncovered an actual issue: If someone specifies --cert foo.pem on the console, that should always be used, even if the certificate is expired. With the current change, we'd generate a new certificate in these cases, which shouldn't happen.

That's a tricky one! My first idea is to mark the CertStoreEntry of manually specified certs so that the expiration check only affects the ones automatically created. But I'm not quite sure if that's the best way to go. Maybe storing them in another list (certs vs. custom_certs) would be better?

How about adding
def expire_outdated(self) -> None:
    while self.expire_queue[0].cert.has_expired:
        d = self.expire_queue.pop(0)
        self.certs = {
            k: v
            for k, v in self.certs.items()
            if v != d
        }

and calling that in get_cert?

I'm still thinking about ditching the explicit "expire_queue" and using something like collections.deque that discards old entries automatically. Or even lru_cache which would discard entrys that haven't been used for some time and not just start with the ones that were created foremost.

Any progress on this? :)

Unfortunately not. I'm not quite sure how much time I can spend on this in the upcoming weeks. Sorry, guys.

Closing this for now, happy to reopen if there is any progress! 😃


Shift intro and era content upward

I don't have an actual minimum height to target but noticed that the "Go to Map" button can get hidden behind the filmstrip on short-ish windows. There is a line-height: 75px on the #intro h1 that if removed helps a little. Maybe things could get compressed some as well and still look decent.

Squeezed some things to get this reasonable down to 600px or so which hopefully is good enough. We'll see if adjustments are needed once there are real era descriptions.


Support for pinocchio.cppad context

This PR develops the support for pinocchio.cppad context.
The PR makes the following changes in the dependencies of Pinocchio:

Minimum Eigenpy version 2.6.7 is required
pycppad library is added as a dependency.

In addition, the PR uncomments the library libpinocchio_cppad, and fixes minor issues regarding the cppad context

@proyan  -- this PR is very nice. I would include at least one example and (optionally) Python unittest to against pycppad.

@proyan Could you add pycppad within the conda CI?

The windows support would have to be added before this PR passes in CI. I'll handle it soon.

@proyan We should enforce the C++11 standard in the whole project and remove useless enforcing due to dependencies.

project and remove useless enforcing due to dependencies

So we are finally ditching c++98? 🎆

project and remove useless enforcing due to dependencies

So we are finally ditching c++98? 🎆

Yes, we already discussed this point here https://github.com/stack-of-tasks/pinocchio/discussions/1361

Weird, it looks like ROS-CI is using eigenpy 2.6.4
https://github.com/stack-of-tasks/pinocchio/pull/1496/checks?check_run_id=3412324049#step:4:502

Weird, it looks like ROS-CI is using eigenpy 2.6.4
https://github.com/stack-of-tasks/pinocchio/pull/1496/checks?check_run_id=3412324049#step:4:502

@wxmerkt Could you help @proyan on that?
Could you explain us how to proceed to the update on our side?

@wxmerkt Could you help @proyan on that?
Could you explain to us how to proceed to the update on our side?

Apologies, the release has been delayed due to some organisational changes. New releases for 2.6.7 are out now for Melodic & Noetic (https://github.com/ros/rosdistro/pull/30561, https://github.com/ros/rosdistro/pull/30560) - once they are merged we can retrigger the builds

@wxmerkt Could you help @proyan on that?
Could you explain to us how to proceed to the update on our side?

Apologies, the release has been delayed due to some organisational changes. New releases for 2.6.7 are out now for Melodic & Noetic (ros/rosdistro#30561, ros/rosdistro#30560) - once they are merged we can retrigger the builds

Thanks for the quick fix @wxmerkt.

@nim65s It looks like gitlab-ci is broken
ERROR: Preparation failed: failed to pull image "memmos.laas.fr:5000/stack-of-tasks/pinocchio/pinocchio:20.04" with specified policies [always]: Error response from daemon: Get https://memmos.laas.fr:5000/v2/: x509: certificate has expired or is not yet valid (manager.go:205:0s)

How do we fix this?

@nim65s @jcarpent @wxmerkt Any ideas on the failing CI https://github.com/stack-of-tasks/pinocchio/pull/1496/checks?check_run_id=3475044304? I only see warnings, but the CI isn't passing

I guess this is due to a too big compilation unit. Try to comment some of the tests just to validate this hypothesis.

I was rather thinking of commenting some tests within contact-dynamics-derivatives

I don't want to remove too many tests, for now I've broken the unittest into smaller parts. Let's see

I don't want to remove too many tests, for now I've broken the unittest into smaller parts. Let's see

I did not mean removing test. I was just meaning commenting tests to check whether this is the origin of your problems!!!

NOT MSVC should be sufficient, no?

I'm trying to exclude the case where MSVC is used in a non windows setting. I don't know how likely it is, but don't think it is impossible.


Add support for No-IP

Add support to auto-confirm hostnames for DDNS.

Problem: Captcha? -> human intervention needed, automation problematic


How to resume on next after catch?

Thank you for the great library.
I see that catch method is available on Observable. I cannot figure out how to resume after catching an error (exception). From the ReactiveX documentation I see that for some languages this functionality is implemented (if I am not mistaken). Please, advice me how resume on next can be done in PHP?
Thank you in advance.

Oh, I guess I can use retryWhen for this (docs).
Just another question. Say I have bufferWithCount to deal with backpressure (I use amp/mysql to select records from the database and it selects rows much quicker then they are processed). After that I flatMap the buffer portion with Observable::fromArray. Later on I can have an exception during record processing. When I use retryWhen will the stream continue with a new buffer portion (from the begining of the observable) or with the next item in the current portion?
Thank you in advance.
Sorry for polluting your issues.


[FEATURE] - Add a way to route using numeric values instead of instances of IRouteInput/IRouteOutput

The best way (and the agreed on idea) is to create an interface that has an ExecuteSwitchNumeric method. The ExecuteSwitchNumeric method should take 2 ints, and an eRoutingSignalType.  This interface will be implemented on the existing Dm Chassis controller classes.

We should add a new interface called IRoutingNumeric that inherits from IRouting and adds void ExecuteNumericSwitch(ushort input, ushort output, eRoutingSignalType type);
Then the existing IRmcRouting and ITxRouting should inherit from the new IRoutingNumeric

Since its primary use is Simpl I think it make sense to use 3 ints rather than 2 ints and an eNum.
Ideally we offer both options using overrides.

@jtalborough The existing implementation should be followed for consistency and since we don't expose the eRoutingSignalType arguement to the bridge and it's handled in the bridge logic, it doesn't need to be abstracted to a number.


[NFC] Fix deprecation in IntegrationTests/SwiftPMTests.swift

<<< operator is deprecated and should be replaced with .send(_: String)

@swift-ci test


Replace malloc with mimalloc

Using mimalloc instead of malloc improves performance significantly.
Pros: Improved performance with a small change
Cons: It will add an external dependency and slightly increase size of QuickJS binaries.
It has been previously added here: https://github.com/openwebf/quickjs/pull/30
Here's the benchmark I ran after replacing:

Benchmark
Master
Mimalloc
Percent Improvement

DeltaBlue
605
702
15.99%

Crypto
863
906
4.98%

RayTrace
357
963
169.33%

EarleyBoyer
682
1579
131.70%

RegExp
149
220
47.65%

Splay
736
1804
145.76%

SplayLatency
3088
4543
47.16%

NavierStokes
1511
1590
5.24%

PdfJS
2016
2949
46.21%

Mandreel
604
656
8.61%

MandreelLatency
4803
5097
6.13%

Gameboy
5191
5644
8.72%

CodeLoad
8015
13343
66.20%

Box2D
1905
2632
38.03%

Typescript
7088
9413
32.75%

Score (version 9)
1430
2060
43.98%

It could also be opt-in by the way.

We should do new benchmarks when considering something like this, FWIW.

Using a custom allocator is problematic for libquickjs.a due to:

risk of symbol conflicts in the embedding program unless the allocator is completely namespaced off

allocator mixup bugs (allocating with allocator A, releasing with B); maybe not a problem for quickjs but js_malloc and friends are exposed in quickjs.h

Embedders can replace the default allocator. That's something we could do in the qjs executable, although I'm in no rush to do that right now.
Tangentially, I've spotted several places where quickjs mallocs a struct that mallocs a struct that mallocs a struct. There's likely gains to be had by flattening such allocation trees.

So I did some benchmarks and I notice up to 25% improvement.

That's a very significant difference. Another allocator worth trying out is jemalloc.

Already the case:

Embedders can replace the default allocator.

Even though you can replace the default allocator yourself which i have done already, making it default positions quickjs at a much better in terms of performance generally for everyone and in various benchmarks.

While having good benchmark results it would be disingenuous to do that if it turns out it's tricky to use that allocator in all situations.
That said, once I put the docs together, we can have a section where we mention things like this.

@ammarahm-ed I want to benchmark something semi-related to this (using calloc vs malloc + memset to be precise). How did you get the results table from your first post?

@saghul do you have binary or instructions to build I can test.
I have write a benchmark script in https://github.com/gengjiawen/js-engines-playground/tree/main/benchmark

This is the PR: https://github.com/quickjs-ng/quickjs/pull/519
I'll take a look at your scripts, thank you!

@gengjiawen Out of curiosity, where do those benchmarks come from?

@gengjiawen Out of curiosity, where do those benchmarks come from?
Use jsuv install engines，than run ‘node benchmark.js’

Sorry I meant that the actual benchmark itself, is it written by V8? What is its canonical source?

Thank you! I see they are deemed obsolete. Are they still relevant, at least in the case of QuickJS?

Likely so. It’s https://bellard.org/quickjs/bench.html. I think maybe update v9 version.

Gotcha.

I see they are deemed obsolete. Are they still relevant, at least in the case of QuickJS?

The V8 team stopped using them because they're not really representative of real web apps (fair enough) but they're still useful for benchmarking raw engine prowess.


No DIR ( directory )  colors => LS LL

I just install ubuntu 16.10
then install ZSH following this link https://gist.github.com/tsabat/1498393
commands LS, LL, etc

Just updated and affected by this as well.

Read through the git log. Can it be because of some change to lib/theme-and-appearance.zsh?

I'm using default settings, nothing changed

It's strange. The environment variable LS_COLORS looks normal. And when I switch to bash the colors show up normally. I wonder what change happened.

A temporary fix is add the line
alias ls='ls -G --color

after the source $ZSH/oh-my-zsh.sh line in the .zshrc file...

Yes, this work, but I go back to bash until ZSH has an oficial fix to this problem.

Affects me as well on Ubuntu 16.04. I'm using default settings, and it broke after the last update.

ok, tks for workaround solution. :))

ls --color -d . &>/dev/null && alias ls='ls --color=tty' || ls -G . &>/dev/null && alias ls='ls -G'
-> ls='ls -G'
ls -G . &>/dev/null && alias ls='ls -G' ||  ls --color -d . &>/dev/null && alias ls='ls --color=tty'
->ls='ls --color=tty'
zsh execute the command in wrong order?

blame 2d96408

cd ~/.oh-my-zsh
git checkout 1b799e9762067f912c0eb807cd5a55d8f122adfd

-> restart terminal
(temporary fix) working for me
ty to @red15 for poiting out the commit that broke the colors

@red15
`➜  .oh-my-zsh git:(master) git checkout 1b799e9762067f912c0eb807cd5a55d8f122adfd
fatal: reference is not a tree: 1b799e9762067f912c0eb807cd5a55d8f122adfd
`

git revert 40544a1d
works for me.

git revert 40544a1d
Worked for me on one machine, but not another. Since it was installed a short while ago it didn't have the history locally. To fetch the history to be able to do a revert you can run
git fetch --depth=5 origin before running the revert, and everything will be fine. =)


wallet is asked to be unlocked before you can visit external website

When I input external website in the browser url in qt wallet, it asks me to unlock my wallet.  Does this expose my wallet to external risk especially when the shared blockchain object, or maybe wallet object is shared between windows?  Some malicious code hosted on external website might attempt to attack.

The wallet lock status checking is in our qt_play module, it is not exposed to outside, so i think it should be safe currently.
But after we expose blockchain object, there might be potential risk from malicious website.

But I think we can limit the APIs the external website can touch.


copy individual answers for rgraph creation

Change does look good.   But only solves part of #106 right?


Fixing two tiny typos

Fixed two tiny errors I stumbled upon.
A misspelling in README.md and a whitespace error in options.json which could lead to confusion about the name of the tmux config file (... to add totmux.conf --> ... to add to tmux.conf).

The option are autogenerated. You should fix this typo in the home manager project. Thanks for PR.

Ok, will do thanks :)

@mipmip I just looked at the tmux.nix source and it seems that every time there's a linebreak in the file it ends up as a whitespace error on the website. I thought the totmux.conf was a singular error but it happens all over the place.
Here's an example of how it looks in the tmux.nix file:
extraConfig = mkOption {
        type = types.lines;
        default = "";
        description = ''
          Additional configuration to add to
          {file}`tmux.conf`.
        '';
      };

It also happens on other files such as the fuzzel.nix for example.
Do you think this formatting error is on home-manager or could it have something to do with how the options.json is generated?
Because when I view the option through man home-configuration.nix it looks correct.

In that case this should be a parser problem. This shall be addressed when #20 is realized. This is a high priority issue. Will work on this ASAP.

Looking forward to it. This project is really useful.


How to generate random instance id?

I need set port:0 and instanceId: '${spring.application.name}:${spring.application.instance_id:${random.int}}' like in this.
How to do it?
Thanks!

Hello @idilshod87, Property placeholder support is planned for our 2.2.0 release.  W.r.t. the generation of ints, that will likely need to be a separate ticket.

@idilshod87 :
We added to 2.2. of Steeltoe, a RandomValueBase package to Configuration, so you can now use it to generate random values, similar to Spring Boot apps.
Also, we added the PropertyPlaceholder package to Configuration so you can use placeholders in your apps configuration.
Dave


Update capi base image and drop support for <v0.1.6

Signed-off-by: Chuck Ha<EMAIL_ADDRESS>What this PR does / why we need it:
This PR drops support for CAPI < v0.1.6 as there was a panic in the node ref code that prevents these versions from working.
NONE

/hold
holding for testing
/cc @liztio

/hold cancel

/lgtm


Subscription activation and registry service account configuration implementation using available REST APIs

Opened new one from correct branch https://github.com/redhat-developer/podman-desktop-redhat-account-ext/pull/35


match job_id's across ci and hil workflows

Maybe this is enough? This way we avoid the dummy jobs in CI, whilst both jobs being triggered by being in merge_group.

Gonna go with #1331 instead, thanks though!


Update to Go 1.23

Also updates the k8s dependencies to 0.29.8

I tested locally and it correctly terminates the pod if it detects the mount goes bad


test(dm): fix some unstable tests

What problem does this PR solve?

Issue Number: close #5732 close #5733 close #5807
What is changed and how it works?
Check List
Tests

No code

Questions
Will it cause performance regression or break compatibility?

Unit test
Integration test
Manual test (add detailed scripts or steps below)

Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`.

/check-issue-triage-complete

/run-dm-integration-test

PTAL @Ehco1996

/merge

/run-dm-integration-test
/run-verify

/merge

/check-issue-triage-complete

/run-dm-integration-test
/run-verify

/run-dm-integration-test


vueMultiselect: can't remove tags, duplicates them

I am using the field vueMultiSelect, adding tags works well, however deleting tags fails (clicking on x icon):

nothing happens when trying to delete the first existing tag
if you add a tag and try to delete it, a input event is emitted which duplicates tags

For instance:

Starts with Vue.js
Click x on Vue.js ==> tag remains, (BROKEN)
Add Rails.js ==>  Vue.js, Rails.js (OK)
Click x on Rails.js ==> Vue.js, Vue.js, Rails.js (BROKEN)

Here is a link to reproduce the problem
Q: Is this failing because I misconfigured vueMultiselect (eg some options I need to set to prevent this behaviour) or because this is a bug?

Each object in your values array needs to be tracked via an id. See the ‘trackBy’ key in the docs.

Yes indeed, big miss :(


⚠ Jenkins Plugins Artifactory has degraded performance

In 03a6c1a, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1077 ms

Resolved: Jenkins Plugins Artifactory performance has improved in e6495cf after 14 minutes.


CycleGAN error in models.py

In the class GeneratorResNet, in line 49 and line 82, the parameter of nn.ReflectionPad2d should be namely3 but not channels. It should be decided by the kernel size but not the channels.

Yeah, It should be 3 to keep the same shape after using nn.Conv2d(channels, out_features, 7)

In the class GeneratorResNet, in line 49 and line 82, the parameter of nn.ReflectionPad2d should be namely3 but not channels. It should be decided by the kernel size but not the channels.

This change is efficient and correct, especially for multi-channels images (e.g. 1x256x256 or 2x256x256).


message doesnot set sent to read dynamically

when user successfully received the message the message status does not change dynamically "sent" to "read"

working done.......


Use semantic versioning. http://semver.org/

Do we really need it? The basic idea behind Este Universal is just drop in react-native app and it should work without these changes. Feel free to correct me.

It will work, but different services (such as code push) require semantic versioning. Additionally, npm uses semantic versioning.
So no, not required. Up to you.

Do you know whether React Native is going to fix it? Otherwise we need some task for it, to be reusable after React Native update, at least gulp task with manual list of changes.

Ok, I think it's not required right now.


BUG: Failed to guarantee literal content/span integrity

Describe the bug

The CI for the ink! project is logging the following on every run:
$ cargo spellcheck check --cfg=.config/cargo_spellcheck.toml --checkers hunspell --code 1
[/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/cargo-spellcheck-0.8.4/src/config/args.rs:121] segment = "hunspell"
[2021-06-23T16:59:05Z ERROR cargo_spellcheck::documentation::cluster] BUG: Failed to guarantee literal content/span integrity: Regex should match >r"content"<
[2021-06-23T16:59:05Z ERROR cargo_spellcheck::documentation::cluster] BUG: Failed to guarantee literal content/span integrity: Regex should match >r"a"<
[2021-06-23T16:59:05Z ERROR cargo_spellcheck::documentation::cluster] BUG: Failed to guarantee literal content/span integrity: Regex should match >r"b"<
[2021-06-23T16:59:05Z ERROR cargo_spellcheck::documentation::cluster] BUG: Failed to guarantee literal content/span integrity: Regex should match >r"c"<
[2021-06-23T16:59:05Z ERROR cargo_spellcheck::documentation::cluster] BUG: Failed to guarantee literal content/span integrity: Regex should match >r"d"<
[2021-06-23T16:59:05Z ERROR cargo_spellcheck::documentation::cluster] BUG: Failed to guarantee literal content/span integrity: Regex should match >r"e"<

I've also seen some spurious failures and I wonder if they're related to this. For example, I opened a PR in which the spellcheck check passed, but as soon as the PR hit master and the same check ran it failed.
To Reproduce
git clone https://github.com/paritytech/ink
cd ink
cargo spellcheck check --cfg=.config/cargo_spellcheck.toml --checkers hunspell --code 1

Expected behavior
I expect the spellchecker to run without printing any warnings, and to either pass or fail consistently.

Which version is currently in use with ink?

I think there are at least two issues here:
a) the regex to determine the comment type, expected at least one pound character for raw strings which is wrong.
b) traversing seems to be slightly messed up, when I run it locally, I get
error: spellcheck(Hunspell)
   --> /tmp/ink/crates/env/src/chain_extension.rs:58
    |
 58 |    All tuple types that may act as input parameters for the chain extension method are valid.
    |        ^^^^^
    | - tulle, duple, or letup
    |
    |   Possible spelling mistake found.

error: spellcheck(Hunspell)
    --> /tmp/ink/crates/env/src/chain_extension.rs:101
     |
 101 |  All tuple types that may act as input parameters for the chain extension method are valid.
     |      ^^^^^
     | - tulle, duple, or letup
     |
     |   Possible spelling mistake found.

error: spellcheck(Hunspell)
    --> /tmp/ink/crates/env/src/engine/experimental_off_chain/test_api.rs:276
     |
 276 |  Alice, Bob, Charlie, Django, Eve and Frank.
     |                       ^^^^^^
     | - Fandango
     |
     |   Possible spelling mistake found.

error: spellcheck(Hunspell)
    --> /tmp/ink/crates/env/src/engine/off_chain/test_api.rs:292
     |
 292 |  Alice, Bob, Charlie, Django, Eve and Frank.
     |                       ^^^^^^
     | - Fandango
     |
     |   Possible spelling mistake found.
// snip

w/ ink! version 98bf5a9960. So some files are just not checked every time :monocle_face: though this is actually unit tested. If you increase logging with -vvvv you can watch out for 🥞 which is used for the folder traversal, though this is rather mundane to do in a large~ish project.
Investigating...

Note that between the PR CI run and the master run you have two different container versions which could have two different en_US.dic in the image, and as such it's not idempotent anymore.
For this purpose there are two recently (0.8.x) introduced config items which are not use in the ink config as far as I can see:
# If set to `true`, the OS specific default search paths
# are skipped and only explicitly specified ones are used.
skip_os_lookups = false

# Use the builtin dictionaries if none were found in
# in the configured lookup paths.
# Usually combined with `skip_os_lookups=true`
# to enforce the `builtin` usage for consistent
# results across distributions and CI runs.
# Setting this will still use the dictionaries
# specified in `extra_dictionaries = [..]`
# for topic specific lingo.
use_builtin = true

Thanks for looking into this @drahnr!

Note that between the PR CI run and the master run you have two different container versions which could have two different en_US.dic in the image, and as such it's not idempotent anymore.

Good point. However, I believe the only differences between the containers are the version of nightly Rust which is used.

For this purpose there are two recently (0.8.x) introduced config items which are not use in the ink config as far as I can see:
# If set to `true`, the OS specific default search paths
# are skipped and only explicitly specified ones are used.
skip_os_lookups = false

# Use the builtin dictionaries if none were found in
# in the configured lookup paths.
# Usually combined with `skip_os_lookups=true`
# to enforce the `builtin` usage for consistent
# results across distributions and CI runs.
# Setting this will still use the dictionaries
# specified in `extra_dictionaries = [..]`
# for topic specific lingo.
use_builtin = true

Okay, I'll add these to the ink! CI.

Feel free to re-open this if it persists, but with the use_builtin = false and skip_os_lookups = true this should become deterministic. If not, I would appreciate a log with -vvv for both runs so I can diff and maybe gain some additional differences.

... but with the use_builtin = false and skip_os_lookups = true this should become deterministic and independent of the container or OS.

Do you mean use_builtin = true? How else will cargo-spellcheck know what dictionary to use?

Ah yes, my fault!


Recommended behaviour modification when no audio output device is connected

When no audio output device is connected, and the volume is muted or changed via keys ModernFlyouts displays the last volume before device was unplugged, which doesn't change if the increase/ decrease or mute keys are pressed.
If the user doesn't realise the speaker has disconnected, it makes it seem like ModernFlyouts has frozen.
It may be better if this behaviour is modified so when no audio device is connected and the volume keys are pressed, the flyout displays "No connected Audio device" or something similar.

@Samuel12321, Thank you for your suggestions!
Your request has been implemented in fdf6f130f0b1617f16f08893b052b565c812677f

just tested, no flyout appears?

No flyout should appear! that's the correct behaviour (while pressing the volume keys). But if you press the media keys (previous, next, play/pause), you will see a message saying "No Connected Audio Devices" instead of showing the useless volume control

i personally think it should show the no connected audio devices message when volume keys pressed as well.

Yes it should be! But there is no way to detect the volume trigger (when no audio devices are connected) with the current SHELL_HOOK method, we'd need to fallback to the old method (i.e. LL Key Hook) to detect the volume keys even when no audio devices are connected.


Getting a valid, but false Error, Import "Example.R1" could not be resolved error

 Environment data

Language Server version: 2021.9.2
OS and version: win32 x64
Python version (and distribution if applicable, e.g. Anaconda):
python.analysis.indexing: undefined
python.analysis.typeCheckingMode: basic

 Expected behaviour
No Error
 Actual behaviour
Reporting: Import "Example.R1" could not be resolved
Note: The import is needed for some environments, but not others. So, I've wrapped it in a try block.
 Logs

Python Language Server Log
XXX 'Please paste the output from your clipboard'

 Code Snippet / Additional information
try:
import Example.R1
except ImportError:
print("Example.R1 is not needed")

XXX

Duplicate of #32.

I'm so sorry about the duplicate. Thank you so much for the quick pointer to a workable solution.


prop does not work as element attribute

prop attribute does not work, see this codepen
<dtable options="options" rows="data" class="material">
      <column name="iName" prop="name" width="200"></column>
      <column name="iCompany" prop="company" width="200"></column>
</dtable>

Chk out this line: https://github.com/Swimlane/angular-data-table/blob/master/src/DataTableController.js#L54

Great, that did it, thanks :)


Reordered entries

Apparently I can’t do alphabet.

          1 Warning

:warning:
Too many changes (when adding, please keep it to one project per Pull Request)

  Generated by :no_entry_sign: Danger


rows: Convert module to typescript.

Looks good to me, marked to merge once CI passes. Thanks @evykassirer!