No compiler error on missing return statement when using if branch

#TypeScript Version:  2.1.6
Code
private someFunction(): string {
    if (false) {
      return "a value"
    }

    //wrong code which does an assignment or declaration instead of returning a value
   "b value"
  }

private callerFunction(): void {
    //prints undefined
    console.log(someFunction())
}

Expected behavior:
Typescript compiler giving an error that a return statement is required for non void types.
Actual behavior:
Code is executed and nothing is returned, giving undefined values.
The compiler doesn't see that a return type is missing when the if branch is skipped.

Not sure if it is necessary or not in this case, but do you have strictNullChecks enabled? It's possible, if you have strictNullChecks off, that it's allowing the branch that returns nothing because it has at least one branch that returns string (even if unreachable).

strictNullChecks are disabled AFAIK, I don't see them in my compiler flags. But if I may nitpick, shouldn't the compiler then ignore it always ? If the return keyword is removed in the if branch the compiler gives a useful error : A function whose declared type is neither 'void' nor 'any' must return a value. I find this behaviour rather ambiguous :)

noImplicitReturns will also give an error on a function like that

Fair enough closing this issue. Setting the right compiler flags gives the expected behaviour.
Thx guys !


Fix duplicate locals

When a local is assigned twice in a method body, the ClassGenerator will also try to add it twice as a local to the body, which is not possible in Soot.
The first commit in this PR adds a test that replicates the issue, and the second commit fixes the issue by preventing the addition of duplicate locals.

Codecov Report

Merging #219 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #219      +/-   ##
============================================
+ Coverage     65.17%   65.23%   +0.05%
- Complexity      389      390       +1
============================================
  Files            52       52
  Lines          1160     1162       +2
  Branches        198      199       +1
============================================
+ Hits            756      758       +2
  Misses          321      321
  Partials         83       83

Impacted Files
Coverage Δ
Complexity Δ

...ine/testgenerator/jimpleevosuite/ClassGenerator.kt
84.21% <100%> (+0.57%)
34 <0> (+1)
:arrow_up:

Continue to review full report at Codecov.

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


toc不能定位当前阅读位置

Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)

打开任意博客有概率能够复现。
2. What did you expect to see? (Required)
右侧toc始终能够定位阅读位置。
3. What did you see instead (Required)
时常出现右侧toc不能高亮目前阅读位置。
4. What is your repo version? (Required)
HEAD

Ctrl + F5后高亮会恢复正常。


Package icon no longer works in 1.12

Category

[x] Bug

Describe the bug
In 1.11 release it was possible to package an icon for your SP package in the app catalog. Now with 1.12 this fails and doesn't package correctly.
Steps to reproduce
Basically Chris Kents article https://thechriskent.com/2017/06/19/sharepoint-framework-app-icon/

run Yo and create a ReactJS webpart
Modify the package-solution.js to add the "icon-path" attribute
copy a png icon into 'sharepoint/images/icon.png'
gulp bundle
gulp package-solution
upload to app catalog

ERROR happens
message:
Invalid SharePoint App package. Error: Specified part does not exist in the package.
Packaging an icon for the app is still possible
Environment details (development & target environment)

Your Developer Environment: Windows 10
Target Environment:  SharePoint Online]
Framework:  | Node.js v12]
Browser(s): [e.g. Chrome v79 | Safari v22 | FireFox v31 | IE v11 | Edge | Chromium Edge v79]
Tooling: [e.g. VS Code | SPFx v1.12.0
Additional details: The more context you can provide, the easier it is (and therefore quicker) to help.

This issue is intended to be part of the upcoming 1.2.1 patch release. Currently we recommend to keep on using 1.11 until further notice. We do apologize the inconvenience.

Thanks for the report @weshackett. We've identified the regression in tooling and are validating a fix.

@weshackett can you confirm this issue is fixed in 1.12.1-rc.0 suite of packages e.g<EMAIL_ADDRESS>

Ping for external validation this issue has been resolved.

Happy for this to be closed


Bug: [v4] Using getSnapshot before machine is initialized messed up spawned actors

Description
When using actor.getSnapshot() before the initial transition, spawned actors in the entry action stay deferred. If you look at the console log in the code sandbox, you'll see that the entryRef stays deferred. Replacing the actorRef.getSnapshot() with undefined in the useEffect fixes it.
Expected result
Using getSnapshot() should not affect spawned actors in entry action
Actual result
Using getSnapshot() breaks spawned actors in entry action
Reproduction
https://codesandbox.io/s/eloquent-maria-vthtmm?file=/src/index.js
Additional context
xstate: v4.38.2
@xstate/react: v3.2.2

It's an unfortunate byproduct of the old implementation that is quite hard to change right now. This has already been fixed in the upcoming v5.
In v4 you could try to use a helper like this to read the current state of the actor:
https://github.com/statelyai/xstate/blob/e87600ea450fa19b71d2051fac3c6c54fb9d486e/packages/xstate-react/src/utils.ts#L25-L31
The problem is that you read that snapshot before the actor gets started and it only gets started in the useEffect in the Provider (and that's higher in your React tree so it gets executed after your own effect)

No worries, this isn't a major issue and I'm able to work around it for now 😄

Even though this is still an issue - it's pretty impossible to actually fix this in v4 right now. So I'm going to close this for housekeeping purposes. We hope to release v5 very soon and that resolves this issue entirely.


Various Test Improvements

Type of pull request
This PR makes changes to the test structure and introduces a basic fuzz test harness, as well as fixing a few panics that were tripped while writing the tests.
Overview of pull request
This PR follows through on the majority of https://github.com/PeterPierinakos/vanilla-rustlang-server/issues/5#issuecomment-1164972312. In particular, it moves the integration tests to become unit tests, completely removes the TestServer struct, adds a fuzz harness to detect panics that can be reached from outside, changes the hardcoded buffer sizes to be dynamically sized, and makes a few changes from what I assume to be the correct non-panicking behavior. In particular, I embedded the default media/ error pages into the binary, rather than simply panicking when they are not present- they are still possible to override (though there isn't a test case for that yet.) I decided to remove one of the existing test cases, because I don't think there's anything to do server-side for CORS checks, and I believe it would be easier to remove it than to reimplement the checks (another case where a future test would be good.) The base unit tests now cover roughly 65% of the codebase by the same metric as earlier, almost doubling previous coverage. As far as fuzzing, I ran it for roughly an hour with no crashes, and am currently reasonably confident that it is difficult for external requests to cause a panic at this point.
I'm leaving this as separate commits right now to simplify reviewing it in parts, but would be happy to squash the changes into a single commit or multiple smaller commits if desired.
Future possibilities
I did not end up writing any integration tests for this PR. After making the changes I did, I think that going forward, the best course of action would be to move most of the server's unit tests back to being integration tests, but using a third party HTTP client over a socket rather than attempting to create a request by hand. The tests that remain as unit tests should be the ones that e.g. test an empty body and providing broken unicode. I've spent long enough not submitting this PR that I decided to leave it as is, but there are also some additional tests that would be good to write:

Check for specific headers (i.e. CORS)
Check that only the configured verbs are accepted
With a multithreaded server, send two requests, then read them in reverse order (the first shouldn't prevent the second from finishing)
If desired, I can redo the hack in the server unit tests to use once_cell, or even just replace it with a static junk path (I don't think it's ever used, so it would be fine to hardcode it to "nonexistent").

I've been testing the changes and I have found some problems. Here are some of the most notable ones:

(This first one is your highest priority.) The server doesn't respond to any of my requests when I run it from your fork and I try to send a request to the server using curl http://localhost:80. Doesn't matter if I run as root or not. This seems to be caused by read_stream and some of the changes you made to it.
At line 21 of file.rs, you try to access the media files which shouldn't be accessed by the program. You can imagine the media files as "stage 1" of implementing the static files because after you put them there you are supposed to run ./setup.sh which will copy all of them to /var/www/static/ (the default static path), so you are supposed to access them via that. The changes made to media/ should be local.
Some of the changes you have done are redundant. For instance, changing the match statement to an if ... else ... statement inside response.rs is unnecessary, so you should probably revert that change.
read_error_file hard checks for if the filename is any of the 4 error pages. The logic is already handled by the beginning of create_file_response, so I believe that this change is also redundant and should be reverted to the function's original state.

I'm willing to squash the commits as one once you fix and address the following issues and do some of the changes I suggested. I'm fine with some of the other minor issues such as the Box::leak in the fuzz_serve_request, but the ones I mentioned above should be fixed before merging.

(This first one is your highest priority.) The server doesn't respond to any of my requests when I run it from your fork and I try to send a request to the server using curl http://localhost:80. Doesn't matter if I run as root or not. This seems to be caused by read_stream and some of the changes you made to it.

Yep, I realized this would happen after I slept- I replaced read with read_to_end, which works fine in tests and avoids possible truncation, but isn't actually correct because HTTP doesn't close the stream until the reply is sent- I'll update that once I'm done typing here.

At line 21 of file.rs, you try to access the media files which shouldn't be accessed by the program. You can imagine the media files as "stage 1" of implementing the static files because after you put them there you are supposed to run ./setup.sh which will copy all of them to /var/www/static/ (the default static path), so you are supposed to access them via that. The changes made to media/ should be local.

The reason I did this was that the program was originally crashing when they were missing, which I ran into during testing (since my workstation isn't a server, I reconfigured it to a local directory and thought that would be sufficient.) I believed the most useful behavior was to have an easily-available version of the files. IMO, even with misconfiguration, the server should never panic, especially as a result of a runtime condition. I'll revert that for now, but consider fixing that in the future.

Some of the changes you have done are redundant. For instance, changing the match statement to an if ... else ... statement inside response.rs is unnecessary, so you should probably revert that change.

It does have a purpose- it makes it possible to move responsibility for reading the error files into the other function, which allows not returning a file. It'll be reverted as well.

read_error_file hard checks for if the filename is any of the 4 error pages. The logic is already handled by the beginning of create_file_response, so I believe that this change is also redundant and should be reverted to the function's original state.

See above.

The reason I did this was that the program was originally crashing when they were missing, which I ran into during testing

Yeah, this is intentional because I wanted to have a directory which would kind of work as a "development environment" so that you can test your changes and not have them apply when you rerun the server. This may be improved in the future, but it currently works.
Just inform me when you commit the read_to_end bug fix and I'll merge to main 👍

By the way, I will fix the runtime panics in a future commit of mine (#9)

Could you specify on what file and line the bug occurs in more detail so that I can take a look myself? By the way, I ran the tests on my local machine with your new changes and they worked just fine so I'm not sure why CI failed.

P.S. During writing this I just thought that we could write special tests specifically for CI that would use the media/ directory and wouldn't be used by normal end users.

This is the closest to what I expected. If you look in src/structs/server.rs line 276, I was hoping it would use tests/static and therefore avoid crashing. The problem here is that user configuration affects tests, which is usually not a good thing. /var/www/static or similar definitely should continue to be the default path, it would be really weird to default to having to install the site within the source code. Running setup.sh before launching tests is a working band-aid if you think that is the best way to go, but it doesn't always help. On my machine, the local tests failed after I reset configuration.rs (I had it set to the test files directory and a rootless port for debugging ease).
In short, I think the problem is that the configuration leaks into the find_file function, and it should somehow avoid being directly dependent upon the installed settings.

I think 54378b74433972ffbc07b874cf4cc0ebc1fb4229 should temporarily the CI issue. Because the configuration is a whole different topic and not very related to why this PR was initially created, I am now closing this issue as we have finally managed to integrate tests into the codebase. If any issue with this change persists after merging, feel free to create a new issue. Going to approve and merge now.


[os_net_setup] Fix delete commands and restore is_vlan_transparent

As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running

/approve

/lgtm


Building jar  throws build WARNING

➜  logs cat egeria-20191011151432-std.log| grep -C2 'JAR will be empty - no content was marked for inclusion!'                             <<<
15:14:48,922 [INFO]
15:14:48,922 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ developer-resources ---
15:14:49,049 [WARNING] JAR will be empty - no content was marked for inclusion!
15:14:49,067 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/developer-resources/target/developer-resources-1.1-SNAPSHOT.jar
15:14:49,115 [INFO]
--
--
15:16:49,721 [INFO]
15:16:49,721 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ access-services-connectors ---
15:16:49,722 [WARNING] JAR will be empty - no content was marked for inclusion!
15:16:49,724 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/adapters/open-connectors/access-services-connectors/target/access-services-connectors-1.1-SNAPSHOT.jar
15:16:49,730 [INFO]
--
--
15:20:46,523 [INFO]
15:20:46,523 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ asset-lineage-client ---
15:20:46,524 [WARNING] JAR will be empty - no content was marked for inclusion!
15:20:46,525 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/access-services/asset-lineage/asset-lineage-client/target/asset-lineage-client-1.1-SNAPSHOT.jar
15:20:46,528 [INFO]
--
--
15:22:11,834 [INFO]
15:22:11,835 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ design-model-client ---
15:22:11,835 [WARNING] JAR will be empty - no content was marked for inclusion!
15:22:11,837 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/access-services/design-model/design-model-client/target/design-model-client-1.1-SNAPSHOT.jar
15:22:11,840 [INFO]
--
--
15:22:22,427 [INFO]
15:22:22,427 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ data-science-client ---
15:22:22,428 [WARNING] JAR will be empty - no content was marked for inclusion!
15:22:22,429 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/access-services/data-science/data-science-client/target/data-science-client-1.1-SNAPSHOT.jar
15:22:22,433 [INFO]
--
--
15:22:32,860 [INFO]
15:22:32,860 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ dev-ops-client ---
15:22:32,860 [WARNING] JAR will be empty - no content was marked for inclusion!
15:22:32,863 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/access-services/dev-ops/dev-ops-client/target/dev-ops-client-1.1-SNAPSHOT.jar
15:22:32,868 [INFO]
--
--
15:22:47,562 [INFO]
15:22:47,562 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ digital-architecture-client ---
15:22:47,564 [WARNING] JAR will be empty - no content was marked for inclusion!
15:22:47,565 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/access-services/digital-architecture/digital-architecture-client/target/digital-architecture-client-1.1-SNAPSHOT.jar
15:22:47,570 [INFO]
--
--
15:23:47,810 [INFO]
15:23:47,810 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ information-view-client ---
15:23:47,811 [WARNING] JAR will be empty - no content was marked for inclusion!
15:23:47,813 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/access-services/information-view/information-view-client/target/information-view-client-1.1-SNAPSHOT.jar
15:23:47,818 [INFO]
--
--
15:24:16,014 [INFO]
15:24:16,014 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ it-infrastructure-client ---
15:24:16,015 [WARNING] JAR will be empty - no content was marked for inclusion!
15:24:16,018 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/access-services/it-infrastructure/it-infrastructure-client/target/it-infrastructure-client-1.1-SNAPSHOT.jar
15:24:16,021 [INFO]
--
--
15:24:29,787 [INFO]
15:24:29,787 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ project-management-client ---
15:24:29,788 [WARNING] JAR will be empty - no content was marked for inclusion!
15:24:29,790 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/access-services/project-management/project-management-client/target/project-management-client-1.1-SNAPSHOT.jar
15:24:29,794 [INFO]
--
--
15:24:37,103 [INFO]
15:24:37,103 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ security-officer-client ---
15:24:37,104 [WARNING] JAR will be empty - no content was marked for inclusion!
15:24:37,105 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/access-services/security-officer/security-officer-client/target/security-officer-client-1.1-SNAPSHOT.jar
15:24:37,107 [INFO]
--
--
15:24:48,416 [INFO]
15:24:48,416 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ software-developer-client ---
15:24:48,417 [WARNING] JAR will be empty - no content was marked for inclusion!
15:24:48,418 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/access-services/software-developer/software-developer-client/target/software-developer-client-1.1-SNAPSHOT.jar
15:24:48,422 [INFO]
--
--
15:25:51,327 [INFO]
15:25:51,328 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ data-privacy-client ---
15:25:51,329 [WARNING] JAR will be empty - no content was marked for inclusion!
15:25:51,330 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/access-services/data-privacy/data-privacy-client/target/data-privacy-client-1.1-SNAPSHOT.jar
15:25:51,333 [INFO]
--
--
15:27:23,690 [INFO]
15:27:23,690 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ security-sync-services-api ---
15:27:23,691 [WARNING] JAR will be empty - no content was marked for inclusion!
15:27:23,693 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/governance-servers/security-sync-services/security-sync-services-api/target/security-sync-services-api-1.1-SNAPSHOT.jar
15:27:23,696 [INFO]
--
--
15:27:28,094 [INFO]
15:27:28,094 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ stewardship-services-api ---
15:27:28,094 [WARNING] JAR will be empty - no content was marked for inclusion!
15:27:28,096 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/governance-servers/stewardship-services/stewardship-services-api/target/stewardship-services-api-1.1-SNAPSHOT.jar
15:27:28,099 [INFO]
--
--
15:27:28,260 [INFO]
15:27:28,260 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ stewardship-services-client ---
15:27:28,261 [WARNING] JAR will be empty - no content was marked for inclusion!
15:27:28,263 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/governance-servers/stewardship-services/stewardship-services-client/target/stewardship-services-client-1.1-SNAPSHOT.jar
15:27:28,271 [INFO]
--
--
15:27:32,380 [INFO]
15:27:32,380 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ stewardship-services-spring ---
15:27:32,381 [WARNING] JAR will be empty - no content was marked for inclusion!
15:27:32,382 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/governance-servers/stewardship-services/stewardship-services-spring/target/stewardship-services-spring-1.1-SNAPSHOT.jar
15:27:32,385 [INFO]
--
--
15:27:57,488 [INFO]
15:27:57,488 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ data-platform-services-api ---
15:27:57,488 [WARNING] JAR will be empty - no content was marked for inclusion!
15:27:57,489 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-implementation/governance-servers/data-platform-services/data-platform-services-api/target/data-platform-services-api-1.1-SNAPSHOT.jar
15:27:57,495 [INFO]
--
--
15:31:10,651 [INFO]
15:31:10,652 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ website ---
15:31:10,652 [WARNING] JAR will be empty - no content was marked for inclusion!
15:31:10,653 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-publication/website/target/website-1.1-SNAPSHOT.jar
15:31:10,656 [INFO]
--
--
15:31:28,328 [INFO]
15:31:28,328 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ open-metadata-tutorials ---
15:31:28,329 [WARNING] JAR will be empty - no content was marked for inclusion!
15:31:28,330 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-resources/open-metadata-tutorials/target/open-metadata-tutorials-1.1-SNAPSHOT.jar
15:31:28,335 [INFO]
--
--
15:31:28,486 [INFO]
15:31:28,486 [INFO] --- maven-jar-plugin:3.1.2:jar (default-jar) @ open-metadata-labs ---
15:31:28,487 [WARNING] JAR will be empty - no content was marked for inclusion!
15:31:28,490 [INFO] Building jar: /Users/jonesn/IdeaProjects/egeria/open-metadata-resources/open-metadata-labs/target/open-metadata-labs-1.1-SNAPSHOT.jar
15:31:28,497 [INFO]

This is an indication that the projects in question are not code containing components but just packaging of other components.
Having packaging=pom may be appropriate for these components (needs testing for impact)

Closing - we're pretty much pushing the boundaries of maven, and have made further changes in this area ie with the way assemblies are generated, to get closer to best practice. Closing


Chirpstack compile issue - "cross: No such file or directory"

Hi,
I am trying to compile Chirpstack from source with nix.
With entering nix-shell, I execute "make dev-dependencies", from the log I can see these lines:
"cargo install cross --version 0.2.5
Updating crates.io index
Downloaded cross v0.2.5
Downloaded 1 crate (228.9 KB) in 0.59s
Installing cross v0.2.5
Updating crates.io index"
So I believe cross has been installed.
But when executing "make debug-amd64" (under ./chirpstack subfolder), it reports error:
"cross build --target x86_64-unknown-linux-musl
make: cross: No such file or directory
make: *** [Makefile:6: debug-amd64] Error 127"
Is this caused by some path configuration error? Please help instruct how to solve.
Many thanks.

I plan to find the path to cross and add it to $PATH.
However, a simply searching finds many cross binaries, as below:
"/usr/share/icons/DMZ-White/cursors/cross
/usr/share/icons/redglass/cursors/cross
/usr/share/icons/DMZ-Black/cursors/cross
/usr/share/icons/Yaru/cursors/cross
/usr/share/icons/whiteglass/cursors/cross
/usr/share/icons/handhelds/cursors/cross
find: '/tmp/.mount_arduinAuMx8Q': Permission denied
/nix/store/hwqz0b3d0wcyjvb4fda1wf8lhj4vaa4m-source/pkgs/test/cross
/nix/store/hwqz0b3d0wcyjvb4fda1wf8lhj4vaa4m-source/pkgs/stdenv/cross
/nix/store/i1w4m7alrgg7vwgcylkycwbq7cr5rvk4-nixpkgs/nixpkgs/pkgs/test/cross
/nix/store/i1w4m7alrgg7vwgcylkycwbq7cr5rvk4-nixpkgs/nixpkgs/pkgs/stdenv/cross
/nix/store/w8lqwhvjx7q0xqpmzyi82j5ka2iqkhxf-source/pkgs/test/cross
/nix/store/w8lqwhvjx7q0xqpmzyi82j5ka2iqkhxf-source/pkgs/stdenv/cross
/nix/store/ly9xsm1yyyha1fa3phh0k3b9lw7bsnh9-cargo-cross-0.2.5/bin/cross
/snap/gtk-common-themes/1534/share/icons/Adwaita/cursors/cross
/snap/gtk-common-themes/1534/share/icons/Breeze_Snow/cursors/cross
/snap/gtk-common-themes/1534/share/icons/DMZ-Black/cursors/cross
/snap/gtk-common-themes/1534/share/icons/DMZ-White/cursors/cross
/snap/gtk-common-themes/1534/share/icons/Yaru/cursors/cross
/snap/gtk-common-themes/1534/share/icons/breeze_cursors/cursors/cross
/snap/gtk-common-themes/1534/share/icons/handhelds/cursors/cross
/snap/gtk-common-themes/1534/share/icons/redglass/cursors/cross
/snap/gtk-common-themes/1534/share/icons/whiteglass/cursors/cross
/snap/gtk-common-themes/1535/share/icons/Adwaita/cursors/cross
/snap/gtk-common-themes/1535/share/icons/Breeze_Snow/cursors/cross
/snap/gtk-common-themes/1535/share/icons/DMZ-Black/cursors/cross
/snap/gtk-common-themes/1535/share/icons/DMZ-White/cursors/cross
/snap/gtk-common-themes/1535/share/icons/Yaru/cursors/cross
/snap/gtk-common-themes/1535/share/icons/breeze_cursors/cursors/cross
/snap/gtk-common-themes/1535/share/icons/handhelds/cursors/cross
/snap/gtk-common-themes/1535/share/icons/redglass/cursors/cross
/snap/gtk-common-themes/1535/share/icons/whiteglass/cursors/cross
find: '/run/user/1000/doc': Permission denied
find: '/run/user/1000/gvfs': Permission denied
/root/chirpstack/cross
/root/.cargo/bin/cross
/root/.cargo/registry/index/index.crates.io-6f17d22bba15001f/.cache/cr/os/cross
/var/lib/docker/overlay2/1c46b04daee139d15e18d06aa2798a2ce16c9800e0b583620a231e051856a437/diff/usr/share/icons/Adwaita/cursors/cross
find: '/proc/10925/task/10925/net': Invalid argument
find: '/proc/10925/net': Invalid argument
/home/songfan/ChirpStack_source/concentratord/chirpstack-concentratord/cross
/home/songfan/ChirpStack_source/chirpstack/chirpstack/cross
/home/songfan/ChirpStack_source/mqtt-forwarder/chirpstack-mqtt-forwarder/cross
/home/songfan/.cargo/bin/cross
/home/songfan/.cargo/registry/index/index.crates.io-6f17d22bba15001f/.cache/cr/os/cross"
Please may I know which one is corret to use? (maybe "/nix/store/ly9xsm1yyyha1fa3phh0k3b9lw7bsnh9-cargo-cross-0.2.5/bin/cross"?)

I'm not sure if I can help you with this, this seems to be related to your local setup and not to be an issue with the ChirpStack build commands. Note that the CI workflow is using the same commands, without the issue that you describe:
https://github.com/chirpstack/chirpstack/blob/master/.github/workflows/main.yml#L71
I'm closing this issue as I don't think this is an issue that can be solved by any code-change in this repository. If you are unable to solve it, I would recommend searching the community forum for a solution: https://forum.chirpstack.io/


Enhancement Enable relative path for OpenID Provider

Hello,
We have made a few derivations on our copy from the upstream.
We want to share them with you so if you find them useful you can also benefit from the code changes.
This is the 2nd of 4 changes.
Motivation:
Enable Membrane to start on a relative path,
so it can be chained under another reverse proxy such as Ngnix.

A little bit on detail for this one as well:
We're running membrane as reverse-proxy, SSL Terminator, webserver and OIDC Provider.
Since our software contains a web client we wanted to provide that one under /, while restrictive network policies of customers as well as CORS considerations prompted us towards making the OIDC provider accessible under the same port as everything else.
This change request allows you to put the login into OIDC anywhere (while not removing the ability to place it under /).
This allows us to have the following endpoint structure:
/ - web client
/api - Backend endpoints
/auth - Login service (login mask, callback, well-known config etc.)


Refactor Repository and Namespaces

Refactor actions to include:

Dependabot
CodeQL
Codecov

Add global.json
Update license to 2022
Split .editorconfig into .editorconfig + .globalconfig
Use file-scoped namespaces
Change test namespaces

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@33ad1cf). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             main        #3   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?        15
  Lines           ?       351
  Branches        ?         0
========================================
  Hits            ?       351
  Misses          ?         0
  Partials        ?         0

Continue to review full report at Codecov.

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


Sub-titles for headings in Publish page are shown as gray.

The Issue
Sub-titles for headings in Publish page are shown as gray.
Steps to reproduce

Open publish page in app

Expected behaviour
They should be black, as gray color gives the feel that the button/option is disabled.
System Configuration
Latest app running from master
Screenshots
https://imgur.com/a/Te3bR

@hackrush01 do you mean the form labels? Or the text directly below the headers?
@btzr-io this did make me notice that we have both form-row__label and form-field__label, which are now styled the same way as of https://github.com/lbryio/lbry-app/commit/45b2bc6aa852d24a196d358fd10a8c31e3384d8b

@kauffj I mean the sub-labels, like File, Title, Thumbnail URL, Description in attached image 1, and Free, Choose Price and Deposit in attached imaged 2. Also, I seem to recall they were proper in the earlier releases.

@btzr-io thought you may be interested in this feedback. Perhaps the color of help text is not appropriate for form labels.

Hover states give the input line more opacity, helping make text fields more noticeable on desktop.
https://material.io/guidelines/components/text-fields.html#text-fields-states


[Feature Draft/Discussion] sssss4ss - super simple shamir secret sharing for seedsigner?

This is very much a rough draft, or even worse, just some notes. However I wanted to share them to see if there might be demand for a adding feature like this to seedsigner. Feedback and comments welcome!!
See the gist here: simple shamir secret sharing
TL;DR:
Shares are valid 24-word BIP39 mnemonics. The master secret is a valid 12-word BIP39 mnemonic.
From the user perspective everything they need to store and handle in the physical world is simply a valid BIP39 mnemonic thereby achieving maximum (currently) interoperability when it comes to loading stored entropy from the physical world into these devices.
Devices do not need to add share-specific scanning flow or learn how to recognize more types of QR codes since all shares are valid 24-word BIP39 mnemonics. Of course this has benefits and drawbacks. Maybe the drawbacks outweigh the benefits, but it has been an interesting exercise to think through regardless.

As a quick example, take the following 3 shares which are each valid BIP39 24-word mnemonics,
> aim lamp birth embark airport convince pepper rib submit perfect uncover unfair legal polar mind unknown put health organ happy struggle current horse inmate
> cake occur sweet glow vicious model invest sick tennis input hero middle drastic cushion excess armor burst disease economy devote satoshi scrap game dust
> deal tray slot uncle sign toss hurdle beauty cheap imitate north zoo total discover siege travel nice future pudding furnace brief once miracle session

and any 2 of the 3 shares can be combined to recover the valid BIP39 12-word mnemonic
= abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon about

Rather than use GF(2^128) as the underlying field for the secret sharing, for simplicity this example used the field Z_p where p = 2^128 - 159. As such, there is a probability of approximately 2^(-120) that a randomly selected bitstring of length 128 will be greater than p (so, in practice, this is not really an issue).
Here is the uncommented code and test demonstrating the above. If there is any interest, I would be happy to clean that code up with some comments so that it might be easier to use as a reference.

Supporting Codex32 BIP93 would be better as the strings are easier to transcribe and type in.

I do agree that supporting codex32 would probably be better, if nothing else because it (presumably) is more researched/tested than the concoction presented in the linked gist. But I am not sure I follow what you mean regarding the strings being easier to transcribe. Transcribing english words, at least for most people, is easier than transcribing a bech32 string I think.
Maybe we need a bech32 alphabet which consists of words, rather than single characters/symbols?

But I am not sure I follow what you mean regarding the strings being easier to transcribe. Transcribing english words, at least for most people, is easier than transcribing a bech32 string I think.
Maybe we need a bech32 alphabet which consists of words, rather than single characters/symbols?

It's less characters. The average word in BIP39 is 5-6 characters so 60-72 vs 48. And BIP39 has no error correction, while codex32 can detect 8 substitutions and correct 4.
I wrote the first wallet software to create and recover codex32 seed backups: https://github.com/BenWestgate/Bails/
In my testing, I can write a 48 character codex32 string in 45 seconds and type it on a qwerty keyboard in 30 if I go fast and let the error correction fix any typo. It feels pretty ergonomic, I've had boomers test it as well with similar comparative ease vs bip39 mnemonics.
If it were absolutely required to use words (trying to turn a codex32 string into a brain wallet/share for example) the SLIP39 wordlist is 10-bits and can directly encode 2 bech32 characters. However writing and typing this is much more labor than 48 bech32 characters, but it would be easier to memorize these SLIP39 words in a pinch.

I wrote the first wallet software to create and recover codex32 seed backups: https://github.com/BenWestgate/Bails/

Very cool! Thanks for sharing. Maybe trying to get a prototype of  Codex32/BIP93 into seedsigner would be a good start then, like you suggested, especially since you have already implemented it.

In my testing, I can write a 48 character codex32 string in 45 seconds and type it on a qwerty keyboard in 30 if I go fast and let the error correction fix any typo. It feels pretty ergonomic ...

Interesting, and good to know you have had success with the testing. Did you find that there was a sweet spot as to the number of characters you would remember/transcribe at a time?

Maybe trying to get a prototype of Codex32/BIP93 into seedsigner would be a good start then, like you suggested, especially since you have already implemented it.

https://github.com/BlockstreamResearch/codex32/pull/58#issuecomment-1807456977

Interesting, and good to know you have had success with the testing. Did you find that there was a sweet spot as to the number of characters you would remember/transcribe at a time?

4 characters is a common standard that fits in the working memory of most.
Recommendations for wallet developers were compiled here:
https://github.com/BlockstreamResearch/codex32/blob/master/docs/wallets.md
There is no corresponding document of recommendations for creating codex32 backups electronically. I will write a draft for that soon.

why not just support slip39 shares?

why not just support slip39 shares?

As I said in the gist, it would be better to use something like codex32 or slip39 and would be great if devices like seedsigner had support for those.


[Bug] IOSResolver build issue

[REQUIRED] Please fill in the following fields:

Unity editor version: 2019.4.19f1
Firebase Unity SDK version: 7.1
Source you installed the SDK: Unity Package Manager
Problematic Firebase Component: Analytics (Auth, Database, etc.)
Other Firebase Components in use: Auth, Realtime Database, Messaging, Crashlytics, Dynamic Links, Remote Config, Analytics
Additional SDKs you are using: Admob
Platform you are using the Unity editor on: Mac and Windows
Platform you are targeting: iOS and Android
Scripting Runtime: IL2CPP

[REQUIRED] Please describe the issue here:
(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)
MissingMethodException: System.Collections.Generic.IEnumerable`1<string> Google.IOSResolver.GetXcodeTargetGuids(object,bool)
Firebase.Editor.XcodeProjectPatcher.OnPostProcessAddGoogleServicePlist (UnityEditor.BuildTarget buildTarget, System.String pathToBuiltProject) (at Z:/tmp/tmp.RemzflXQPx/firebase/app/client/unity/editor/src/XcodeProjectPatcher.cs:318)
System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at <9577ac7a62ef43179789031239ba8798>:0)
Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation.
System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at <9577ac7a62ef43179789031239ba8798>:0)
System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) (at <9577ac7a62ef43179789031239ba8798>:0)
UnityEditor.Build.BuildPipelineInterfaces+AttributeCallbackWrapper.OnPostprocessBuild (UnityEditor.Build.Reporting.BuildReport report) (at /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:177)
UnityEditor.Build.BuildPipelineInterfaces+<>c__DisplayClass17_0.<OnBuildPostProcess>b__1 (UnityEditor.Build.IPostprocessBuildWithReport bpp) (at /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:433)
UnityEditor.Build.BuildPipelineInterfaces.InvokeCallbackInterfacesPair[T1,T2] (System.Collections.Generic.List`1[T] oneInterfaces, System.Action`1[T] invocationOne, System.Collections.Generic.List`1[T] twoInterfaces, System.Action`1[T] invocationTwo, System.Boolean exitOnFailure) (at /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:391)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr) (at /Users/bokken/buildslave/unity/build/Modules/IMGUI/GUIUtility.cs:197)

Steps to reproduce:
Run Build for iOS

Can you give some more detail? Were you able to reproduce this the quickstart project? What steps did you follow to build the app?

I just ran into the same, @programmermattsrum. I wonder how you resolved it?
MissingMethodException: System.Collections.Generic.IEnumerable`1<string> Google.IOSResolver.GetXcodeTargetGuids(object,bool)
Firebase.Editor.XcodeProjectPatcher.OnPostProcessAddGoogleServicePlist (UnityEditor.BuildTarget buildTarget, System.String pathToBuiltProject) (at Z:/tmp/tmp.RemzflXQPx/firebase/app/client/unity/editor/src/XcodeProjectPatcher.cs:318)
System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at <567df3e0919241ba98db88bec4c6696f>:0)
Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation.
System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at <567df3e0919241ba98db88bec4c6696f>:0)
System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) (at <567df3e0919241ba98db88bec4c6696f>:0)
UnityEditor.Build.BuildPipelineInterfaces+AttributeCallbackWrapper.OnPostprocessBuild (UnityEditor.Build.Reporting.BuildReport report) (at /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:158)
UnityEditor.Build.BuildPipelineInterfaces+<OnBuildPostProcess>c__AnonStorey2.<>m__1 (UnityEditor.Build.IPostprocessBuildWithReport bpp) (at /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:398)
UnityEditor.Build.BuildPipelineInterfaces.InvokeCallbackInterfacesPair[T1,T2] (System.Collections.Generic.List`1[T] oneInterfaces, System.Action`1[T] invocationOne, System.Collections.Generic.List`1[T] twoInterfaces, System.Action`1[T] invocationTwo, System.Boolean exitOnFailure) (at /Users/builduser/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:356)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr) (at /Users/builduser/buildslave/unity/build/Modules/IMGUI/GUIUtility.cs:179)


Is this project dead?

Hello, I love this game. It's too good to play without having to install anything. Continue working on it, it could become a very complex but easy to play game!

Well... i notice that there are people on the lead board on the games website. I play this game sometimes too!

Technically, the development of this game has been dead since years. But as the author said, he will still merge PRs that would improve the game.


Support void* (Pointer[None]) parameters in bare lambdas

Unlike conventional FFI functions, bare lambdas @{(...)} do so far not support Pointer[None] parameters, Pony's equivalent of void*, despite the fact that like the former these lambdas are strictly intended for use with FFI calls and callbacks.
Therefore, code like this failed to compile:
use @wglGetProcAddress[@{()}](name: Pointer[U8] tag)

class GlExt
    let glBufferData: @{(GLenum, GLsizeiptr, Pointer[None] tag, GLenum)}

    new create() =>
        glBufferData = @wglGetProcAddress[@{(GLenum, GLsizeiptr, Pointer[None] tag, GLenum)}]("glBindBuffer".cstring())

...

let maxParticles: ISize = 1000
var particles: Array[F32] = [] // holds Vector3f {float, float, float} particles
//fill particle array
for i in Range[ISize](0, maxParticles) do
    particles.push(sr.frand()) // x
    particles.push(sr.frand()) // y
    particles.push(sr.frand()) // z
end
...

glExt.glBufferData(GLArrayBuffer(), maxParticles * ISize(12), particles.cpointer(), GLStaticDraw()) // <- type error

This commit adds to the bare lambdas the same lenience that conventional FFI functions enjoy regarding the type compatiblity of  Pointer[None] with all other Pony Pointer[A] types, so that the code above now compiles.

Please change the test to a ponyc-run test. We only do error messages tests now that aren't ponyc-run.
Let me know if you need any help getting oriented with the ponyc-run tests.

Like Sean mentioned, can you add the test to the runner? It would also make sense to test that partial application also works with this change, like so:
use @printf[I32](fmt: Pointer[None] tag, ...)

actor Main
  new create(env: Env) =>
    let cb = this~print()
    cb("Hello, world!\n".cstring())

  fun @print(fmt: Pointer[None]) =>
    @printf(fmt)

Thanks for the test. It does run and print hello world. I am not familiar enough with the test suite to know if the actual output needs to be captured here or if I should simply add an exit code that matches the .txt file.  Also, I struggled a bit to understand

We only do error messages tests now that aren't ponyc-run.
The compile test I had proposed was not an error message test. Should I simply add an exit code test for that one too, i.e., move both tests to the libponyc-run suite?

@ergl I combined the test you suggested for the bare functions with one for bare lambdas. It only produces the expected exit code if both pass. Ok so?

I'd prefer separate tests


Perl6 to Raku

fix link of nqp in github
Perl means Perl 5, no ambiguity now, so change perl5 to perl only

Great! Thank you!


@VersionedPactUrl should blow up if nothing to filter

If there is nothing to filter (e.g. ${app.version}) when using @VersionedPactUrl, this is a sign that you should either be using the default @PactUrl or you have temporarily replaced the tokens with hard coded values to test locally.
@VersionedPactUrl blowing up is a safe reminder of this and I have found this to cause issues in the past.

Please assign this to myself as I don't have permission to do so.

Good catch, that should throw an exception.

I will work on this.


Expand **

When I type **/myfile, oh-my-zsh should expand it to folderA/folderB/blabla/myfile

Have you lost interest on this? If so, please close the issue.


Fix assertions on exception messages

I realized while working on a feature on this repo that we've been misusing assert_raises. We have a bunch of tests that assume the second arg will be asserted as the error message, whereas it is in fact just used as the assertion failure message. I wrote most of these mistakes myself, but I don't think I'm the only one with the misimpression (it was actually originally suggested to me by a reviewer). This PR fixes the misuse, introduces a helper with the desired behaviour, and tries to prevent future confusion.

I see the value of the override but we should keep it mind that we could no longer use the last argument feature

True, and it would be easy enough to make that possible. Pushed another commit that lets you use a kwarg if you're using that feature on purpose. LMK what you think. Here are some examples:
  def test_assert_raises
    assert_raises(StandardError, "foobar") do
    end
  end

  1) Failure:
RunnerTest#test_assert_raises [test/unit/kubernetes-deploy/runner_test.rb:10]:
Please use assert_raises_msg to check the exception message,
or use the msg keyword argument to specify a message to use when the assertion fails.

  def test_assert_raises
    assert_raises(StandardError, msg: "This is an error message.") do
    end
  end

  1) Failure:
RunnerTest#test_assert_raises [test/unit/kubernetes-deploy/runner_test.rb:10]:
This is an error message.
StandardError expected but nothing was raised.

  def test_assert_raises
    assert_raises(StandardError) do
    end
  end

  1) Failure:
RunnerTest#test_assert_raises [test/unit/kubernetes-deploy/runner_test.rb:10]:
StandardError expected but nothing was raised.

Great idea!
What about using message instead of msg? That would keep parity with other test helpers at Shopify that use message as a keyword argument.

Pushed another commit that makes this a duplicate of what I just proposed in core.


Fix Get-Help not working with YamlCreate

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

https://github.com/Trenly/winget-pkgs/issues/194

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@Trenly


Compiler crash in uiua v0.11

Reporting as per error message, full error below.
The application panicked (crashed).
Message:  index out of bounds: the len is 0 but the index is 0
Location: /home/username/.local/share/rust/cargo/registry/src/index.crates.io-6f17d22bba15001f/uiua-0.11.1/src/array.rs:386
Backtrace omitted.
Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Error:
The compiler has crashed!
Hooray! You found a bug!
Please report this at http://github.com/uiua-lang/uiua/issues/new or on Discord at https://discord.gg/9CU2ME4kmn.
Uiua version 0.11.1
code:
∵△ □ []

NB: the code  (∵△ □ []) seems to behave properly in uiua pad

Apologies for the comment spam and closing/reopening the issue: I'm bad at github ui.

This was fixed a little while ago.
You can download a dev release if you like from here.


ode for input

Hi,
I have an ode for the input in my model. See below as an example. Is there any way to define u(t) as an input in such a case? Thanks.
ode = @ODEmodel(
x1'(t) = -(a01 + a21) * x1(t) + a12 * x2(t) + u(t),
x2'(t) = a21 * x1(t) - a12 * x2(t) - x3(t) / b,
x3'(t) = x3(t),
u'(t) = -kd*u(t),
y(t) = x2(t)
)

So I guess that you would like to reflect the fact that it is known, right? Then you can just add an output for it y2(t) = u(t).
Does this sound like what you had in mind?

Thanks for your reply!
The input is known but it is not an observable. In my model the input is a drug that binds to other species and also gets degraded.   For example, see the following two equations, the drug binds to the receptor R and forms a complex RL. These are just two equations out of 23 odes from my model. I want to assess the identifiability provided that the drug is an input.
R'(t) = - kasRLdrug(t)R(t) + kdisRLRL(t),
drug'(t) =  - kasRLdrug(t)R(t) + kdisRLRL(t) - kd_drug*drug(t),

Thank you for clarifying ! I am bit confused by possible meaning of know but now observable. From what you describe it sounds to me that there is a known input flow of the drug (which is an input not satisfying any equations) and there is the total concentration of the drug in the organ which influenced by this input flow but also by other species (as you describe). So wouldn't it make sense to have here one input and one state ?

Thanks. I think you may be right, I should include the input as an observable since it is known and have odes for that. Just few questions though, in the following example, including the input u(t) makes it fully identifiable, so how does the input affects identifiability?
ode = @ODEmodel(
x1'(t) = k * (1 - x1(t) - x2(t)) + u(t),
x2'(t) = r * (1 - x1(t) - x2(t)),
y(t) = x1(t)
)
Also, I understand that local meaning finite interval, so what interval specifically is used in the local method?

including the input u(t) makes it fully identifiable, so how does the input affects identifiability?

It allows you to perturb the trajectory and thus extract more information. Another way to put this is that this input breaks the symmetries of the model: without it you could apply any linear operator with (1, 1) being eigenvector to (x1, x2) and preserve the output (hence, nonidentifiability). With this input this does not work.

Also, I understand that local meaning finite interval, so what interval specifically is used in the local method?

Local here means that, for generic input-output data, there will be only finitely many possible parameter values. In other words, that parameter value is unique locally in small neighbourhood. Technically, the algorithm to check this relies on the Hermann-Krener observability criterion. The specific algorithm follows the paper by Sedoglavic.

Thanks, that helps. I wanted to know if it is possible to get this finite interval for each parameter but looking at those papers I guess it might be difficult task.
Also, fyi, I am facing similar issue as reported under "Stuck at "Computing IO-equations"" while using the global method.  I get "Problem in the Flint-Subsystem" after "[ Info: Computing IO-equations".

@jigiisc
Computing IO-equations is typically the bottleneck. If it is fine for you to share the model with me, I can look at it and maybe propose a workaround. (if you do not want to post it here, you can email it to<EMAIL_ADDRESS>


Scalability tests for Kueue for the scheduler

What would you like to be added:
Scalability tests (involving thousands of workloads) for Kueue scheduler, oriented on the performance of the Kueue algorithms.
Why is this needed:
Determine the performance of Kueue algorithms for scheduling and preemption at large scale.
It can be handy to verify there is no regression when working on Fair sharing or Hierarchical cohorts features.
Completion requirements:
This enhancement requires the following artifacts:

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

The artifacts should be linked in subsequent comments.

I think it does not require KEP, since there is no API change. However, there are some non-obvious decisions, so I prepared an initial design doc, shared with batch-wg.

/assign @trasc
/cc @alculquicondor @mwielgus

Additionally (it might be a follow up issue) we would like to have a higher-level of scalability tests using a framework such as kwok. Since both layers of testing would cover slightly different use-cases (focus on algorithms vs focus on e2e throughput) we may add both.


Checkbox text is fuzzy and ugly

Not quite sure how to fix this, maybe custom checkbox items

Fixed in db757aa


为什么我无法获取到 v2 版本

go get -u github.com/panjf2000/ants/v2
package github.com/panjf2000/ants/v2: cannot find package "github.com/panjf2000/ants/v2" in any of:
        /usr/local/go/src/github.com/panjf2000/ants/v2 (from $GOROOT)
        /Users/xxx/Desktop/go/gin/src/github.com/panjf2000/ants/v2 (from $GOPATH)

go get -u github.com/panjf2000/ants/v2
package github.com/panjf2000/ants/v2: cannot find package "github.com/panjf2000/ants/v2" in any of:
        /usr/local/go/src/github.com/panjf2000/ants/v2 (from $GOROOT)
        /Users/xxx/Desktop/go/gin/src/github.com/panjf2000/ants/v2 (from $GOPATH)


Define TIKI SDK UI Flow

Define the UX flow in the TIKI SDK UI and create stories for implementing it.

Flow
#166 , #167, #168, #169, #170


Fix TravisCI GitHub setup

TravisCI build statuses haven't been showing up on GitHub recently.
The lack of feedback has resulted in the TravisCI build being broken for several days. The PhysFS upgrade broke it, as the config it's using installs too old of a package for PhysFS.
We should look into fixing the build statuses for TravisCI.
Additionally, we might consider scrapping the Linux builds on TravisCI. They're much slower than the CircleCI equivalents. Additionally, they require much more effort to maintain.
The MacOS builds on TravisCI are still useful. We should maintain those for now.

TravisCI build statuses seem to be updating again. I'm going to assume it was a temporary service outage.
Current TravisCI builds have been passing. Anything that broke during the outage has since been fixed.
Builds on TravisCI continue to be slow. That's probably not fixable though, at least not other than using a different CI platform. I'm going to go ahead and close this.


boards: frdm_k64f: Enable pullup for CAN0_RX pin

This commit enables the pullup on CAN0_RX pin (PORTB 19).
The pullup ensures that the CAN controller initializes even
without a transceiver connected.
Fixes #18320.

How can we get in a situation on that board where no CAN transceiver is connected?

@henrikbrixandersen the board has no onboard transceiver. The plain board causes problems.


Update GTO docs to match 0.3.0

@dberenbaum @omesser can you approve this please? Removing outdated parts of GTO/MLEM docs here.

Thanks @dberenbaum! Applied your feedback. The UG still feels like a mix of everything to me (finding right artifacts version, CI/CD, DVC annotations, GTO config, GTO tags convention), but not sure if this is a substantial problem.

Thanks for suggestion @dberenbaum, looks good to me. Applied it. Let's get this approved and merged then!

Updated the page (first paragraph + fixed the link). Please TAL @dberenbaum

Looks good @aguschin!


Create Profile page

High priority, small task.

Profile component might need some optimizing, but it works as intended.


User Preferences, forgets Editor Theme v7.2 and v7.3

In User Preferences, Editor Theme choice is not being persisted.
https://github.com/gchq/stroom/assets/28703366/95a05527-d44a-4fa7-a4c9-463fbf761fce

Fixed in 7.2.10


update kubernetes dependency to v1.23

What this PR does / why we need it:
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

/teat all

/test all

/test openstack-cloud-csi-cinder-e2e-test

/test openstack-cloud-csi-cinder-e2e-test

/test openstack-cloud-csi-cinder-e2e-test

Summarizing 3 Failures:

[Fail] [sig-storage] [cinder-csi-e2e] CSI Volumes [Driver: cinder.csi.openstack.org] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral [It] should create read/write inline ephemeral volume
/root/pkg/mod/k8s.io/kubernetes@v1.23.0/test/e2e/storage/testsuites/ephemeral.go:428

[Fail] [sig-storage] [cinder-csi-e2e] CSI Volumes [Driver: cinder.csi.openstack.org] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral [It] should support multiple inline ephemeral volumes
/root/pkg/mod/k8s.io/kubernetes@v1.23.0/test/e2e/storage/testsuites/ephemeral.go:428

[Fail] [sig-storage] [cinder-csi-e2e] CSI Volumes [Driver: cinder.csi.openstack.org] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral [It] should support two pods which have the same volume definition
/root/pkg/mod/k8s.io/kubernetes@v1.23.0/test/e2e/storage/testsuites/ephemeral.go:428

from e2e seems some changes are needed , might be worthy to dig into whether some new features added/removal since 1.23...

/test openstack-cloud-controller-manager-e2e-test

Summarizing 3 Failures:

[Fail] [sig-storage] [cinder-csi-e2e] CSI Volumes [Driver: cinder.csi.openstack.org] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral [It] should create read/write inline ephemeral volume
/root/pkg/mod/k8s.io/kubernetes@v1.23.0/test/e2e/storage/testsuites/ephemeral.go:428

[Fail] [sig-storage] [cinder-csi-e2e] CSI Volumes [Driver: cinder.csi.openstack.org] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral [It] should support multiple inline ephemeral volumes
/root/pkg/mod/k8s.io/kubernetes@v1.23.0/test/e2e/storage/testsuites/ephemeral.go:428

[Fail] [sig-storage] [cinder-csi-e2e] CSI Volumes [Driver: cinder.csi.openstack.org] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral [It] should support two pods which have the same volume definition
/root/pkg/mod/k8s.io/kubernetes@v1.23.0/test/e2e/storage/testsuites/ephemeral.go:428

from e2e seems some changes are needed , might be worthy to dig into whether some new features added/removal since 1.23...

Thanks. I dont see much of changes . Investigating if anything amiss

/test openstack-cloud-csi-cinder-e2e-test

commit a40d2eb18c7a256f33b4839a3a46172321128aa8
Author: Patrick Ohly<EMAIL_ADDRESS>Date:   Thu Oct 14 18:01:09 2021 +0200

    storage validation: accept generic ephemeral volumes as volume device

    Raw block devices are possible with generic ephemeral volumes, so rejecting a
    pod with that combination is wrong.

seems this is the main error
Message: "Pod \"inline-volume-tester-5rw6d\" is invalid: spec.containers[0].volumeDevices[0].name: Invalid value: \"my-volume-0\": can only use volume source type of PersistentVolumeClaim for block mode",

the above PR is latest change of test between 1.22/23, not sure that's the reason..

commit a40d2eb18c7a256f33b4839a3a46172321128aa8
Author: Patrick Ohly<EMAIL_ADDRESS>Date:   Thu Oct 14 18:01:09 2021 +0200

    storage validation: accept generic ephemeral volumes as volume device

    Raw block devices are possible with generic ephemeral volumes, so rejecting a
    pod with that combination is wrong.

seems this is the main error
Message: "Pod \"inline-volume-tester-5rw6d\" is invalid: spec.containers[0].volumeDevices[0].name: Invalid value: \"my-volume-0\": can only use volume source type of PersistentVolumeClaim for block mode",

the above PR is latest change of test between 1.22/23, not sure that's the reason..

@jichenjc yes, those tests are added in 1.23 only and yes its failing with above error. But we dont pass those values from driver , and in the code it seems to be creating fine. https://github.com/kubernetes/kubernetes/blob/ab69524f795c42094a6630298ff53f3c3ebab7f4/test/e2e/storage/framework/volume_resource.go#L136
@jichenjc Could you please also look at it if anything amiss from the driver side

@ramineni yes, I am also checking it :) let's exchange info in case anything new found

/test openstack-cloud-csi-cinder-e2e-test

/test openstack-cloud-controller-manager-e2e-test

/test openstack-cloud-csi-manila-e2e-test

@jichenjc @lingxiankong looks like issue to be k3s doesnt support to install 1.23 yet I suppose.
@lingxiankong could you please check?

@jichenjc @lingxiankong looks like issue to be k3s doesnt support to install 1.23 yet I suppose.

oh.. https://github.com/k3s-io/k3s/releases
don't have 1.23 yet, maybe we can keep an eye and wait for a while

/test openstack-cloud-controller-manager-e2e-test

/test openstack-cloud-csi-cinder-e2e-test

/override openlab/cloud-provider-openstack-multinode-csi-migration-test
/override openlab/cloud-provider-openstack-acceptance-test-keystone-authentication-authorization
/override openlab/cloud-provider-openstack-acceptance-test-e2e-conformance-stable-branch-v1.21
/override openlab/cloud-provider-openstack-acceptance-test-e2e-conformance-stable-branch-v1.20
openlab/cloud-provider-openstack-acceptance-test-e2e-conformance-stable-branch-v1.19

/override openlab/cloud-provider-openstack-acceptance-test-e2e-conformance-stable-branch-v1.19
/override openlab/cloud-provider-openstack-acceptance-test-e2e-conformance

/test openstack-cloud-csi-manila-e2e-test

@gman0 @gouthampacha could you check manila failure if available. Thanks

@ramineni thanks for pinging, but I'm on a vacation. I can take a look later next week though.

@ramineni do you know if there any cmd flag changes in klog? It's failing on log verbosity setting:
Error: unknown shorthand flag: 'v' in -v=2

/hold
This missed feature freeze. We need to discuss whether or not these make sense to land after feature freeze.

We need to discuss whether or not these make sense to land after feature freeze.

@sdodson what's the feature freeze ? CPO is still catch up with 1.23 k8s release so not sure the meaning of feature freeze, thanks

Error: unknown shorthand flag: 'v' in -v=2

is there special usage of manila plugin? I think OCCM/CSI cinder both use -v in various places ?

/hold cancel
Sorry I didn't realize this was an upstream repo

unknown shorthand flag

@gman0 i dont understand , where do you see this error. I cant seem to find error in logs

@gman0 Did u test manila plugin in local setup with upgrade to 1.23 kk . This is blocker for release .

Yes I tested this PR (in a v1.23 cluster too) and -v that's being passed from the Helm chart is causing klog to fail -- it doesn't seem to recognize this option anymore.

Yes I tested this PR (in a v1.23 cluster too) and -v that's being passed from the Helm chart is causing klog to fail -- it doesn't seem to recognize this option anymore.

Regarding the -v issue, you'll have to use the new cli.Run() function from "k8s.io/component-base/cli".
See https://github.com/kubernetes/kubernetes/pull/105076/.

@mandre thank you for this info! Most of the projects in this repo needs an update it seems.

Most of the projects in this repo need an update it seems.

That would be just cmd/openstack-cloud-controller-manager/main.go if I'm not mistaken. We should update similar to what was done in https://github.com/kubernetes/kubernetes/pull/105076/files#diff-553e5a7eabe071db91dd2467db6a7fb68bcddf2506ebbf7fccb9335ea632fd94 for example.

@mandre It looks like it's actually all projects except occm :) @ramineni could you please allow write access to this PR so I can push commits here?
This is what it looks like with patches applied https://gist.github.com/gman0/0256a99b2a7678a375ec581f09131e01

@mandre It looks like it's actually all projects except occm :) @ramineni could you please allow write access to this PR so I can push commits here?
This is what it looks like with patches applied https://gist.github.com/gman0/0256a99b2a7678a375ec581f09131e01

I dont see option to give write access . Please push another PR if you have changes ready , I can close this one

@ramineni according to https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork it should be right here on the PR, in the right vertical menu/bar thing.

/lgtm

/test openstack-cloud-csi-cinder-e2e-test

/test openstack-cloud-csi-cinder-e2e-test

/test openstack-cloud-csi-manila-e2e-test

./test openstack-cloud-keystone-authentication-authorization-test

@ramineni could you update k8s.io deps to 1.23.1? after that I can approve this PR but need to know what is status of those failing tests. Should those work or is it ok to skip

@jichenjc openstack-cloud-keystone-authentication-authorization-test , this test is not up right? ill override it?

/override openlab/cloud-provider-openstack-acceptance-test-e2e-conformance

/override openlab/cloud-provider-openstack-acceptance-test-e2e-conformance-stable-branch-v1.19
/override openlab/cloud-provider-openstack-acceptance-test-e2e-conformance-stable-branch-v1.20
/override openlab/cloud-provider-openstack-acceptance-test-e2e-conformance-stable-branch-v1.21
/override openlab/cloud-provider-openstack-multinode-csi-migration-test

/override openlab/cloud-provider-openstack-acceptance-test-keystone-authentication-authorization

/cc @lingxiankong

ill override it?

yes , please

/test openstack-cloud-controller-manager-e2e-test

/approve

/override openstack-cloud-keystone-authentication-authorization-test

/test openstack-cloud-csi-manila-sanity-test


[Question] How can I reply using an O365ConnectorCard?

System Information (Required)

SDK Language: .NET/C#
SDK Version: <IP_ADDRESS>
Development Environment: Self-hosted IIS

Issue Description
I made a custom bot for my company. I have tried replied with ThumbnailCard, now I want to reply with O365ConnectorCard. I have installed Microsoft.Bot.Connector.Teams 0.5.6, but O365ConnectorCard does not offer a ToAttachment() method so I don't know how to add it to the Activity.
Most of my code is from CustomBot sample applecation.
Code Example
N/A
Steps to Reproduce the Issue
N/A
Expected Behavior
Reply in thread with a O365ConnectorCard.
Actual Results
I don't know how to do it...

@DSakura1987 What channel(s) are you using with your bot?
The O365 actionable message concept exists in Bot Framework, but we use a different name for it: Adaptive Cards.
You can achieve something similar using the Adaptive Cards JSON spec to configure card actions that interact with your O365 webhooks.

If I understand it correctly, custom bot only lives in teams as a webhook-like thing, right? I always manually add it to a team.
Let me try the Adaptive Cards. Hope it works as I expected - have sections and other functions as O365ConnectorCard.

Hi @nwhitmont , I just tried sending back this payload as the body, but the card does not show in the channel. do I need to fill more fields?
{
  "title": "Task(s) Summary",
  "text": null,
  "summary": null,
  "themeColor": null,
  "sections": [
    {
      "title": null,
      "text": null,
      "activityTitle": "Product Backlog Item 1",
      "activitySubtitle": null,
      "activityText": null,
      "activityImage": null,
      "facts": [
        {
          "name": "State",
          "value": "New"
        },
        {
          "name": "Assigned to",
          "value": "Somebody "
        }
      ],
      "images": null,
      "potentialAction": [
        {
          "name": "View Product Backlog Item 1",
          "target": [
            "someUrl"
          ],
          "@type": "openUrl"
        }
      ]
    }
  ],
  "$schema": "http://schema.org/extensions",
  "type": "MessageCard"
}

Update:
Some fun facts:

The payload needs summary or text field to be sent with a Connector.

The server replied 200 even I missed both fields. A bug for Teams dev team?

The fixed payload does not work with custom bot.

@DSakura1987 Thanks for the update.  What do you mean by "the fixed payload does not work with custom bot"?

Oh, when I added text field, connector works fine, but my custom bot still
replies nothing.
Nils<EMAIL_ADDRESS>16:13写道：

@DSakura1987 https://github.com/dsakura1987 Thanks for the update. What
do you mean by "the fixed payload does not work with custom bot"?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotBuilder/issues/3012#issuecomment-310517078,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEN5EroYxlePGoKhXmpeIPXZgRqWW3pvks5sGubZgaJpZM4OCrt_
.

@DSakura1987 Can you post your complete bot code so we can better assist you?

I've used the O365ConnectorCard in Teams as a reply. You just need to create you own ToAttachment function as there is none supplied. This is how the framework does it:
public static Attachment ToAttachment(this O365ConnectorCard card) {             return CreateAttachment(card, O365ConnectorCard.ContentType);         }
    `private static Attachment CreateAttachment<T>(T card, string contentType) {
        return new Attachment {
            Content = card,
            ContentType = contentType
        };
    }`

Thanks @BehnamEmamian ! That works but I still have a small issue with potentialAction in a section object. Does it work? My card showed without the buttons.
Here is the JSON my bot sent:
{
   "type": null,
   "id": null,
   "timestamp": null,
   "localTimestamp": null,
   "serviceUrl": null,
   "channelId": null,
   "from": null,
   "conversation": null,
   "recipient": null,
   "textFormat": null,
   "attachmentLayout": "carousel",
   "membersAdded": [],
   "membersRemoved": [],
   "topicName": null,
   "historyDisclosed": null,
   "locale": null,
   "text": null,
   "speak": null,
   "inputHint": null,
   "summary": null,
   "suggestedActions": null,
   "attachments": [
      {
         "contentType": "application/vnd.microsoft.teams.card.o365connector",
         "contentUrl": null,
         "content": {
            "title": "2 Task(s)",
            "text": null,
            "summary": "Tasks",
            "themeColor": null,
            "sections": [
               {
                  "title": "Task 11411",
                  "text": "Iteration: .....",
                  "activityTitle": null,
                  "activitySubtitle": null,
                  "activityText": null,
                  "activityImage": null,
                  "facts": [
                     {
                        "name": "State",
                        "value": "To Do"
                     },
                     {
                        "name": "Found In",
                        "value": "None"
                     },
                     {
                        "name": "Assigned To",
                        "value": "None"
                     }
                  ],
                  "images": null,
                  "potentialAction": [
                     {
                        "name": "View Task 11411",
                        "targets": [
                           {
                              "os": "default",
                              "uri": "REMOVED"
                           }
                        ],
                        "@type": "OpenUri"
                     }
                  ]
               },
               {
                  "title": "Bug 11422",
                  "text": "Iteration: .....",
                  "activityTitle": null,
                  "activitySubtitle": null,
                  "activityText": null,
                  "activityImage": null,
                  "facts": [
                     {
                        "name": "State",
                        "value": "To Do"
                     },
                     {
                        "name": "Found In",
                        "value": "None"
                     },
                     {
                        "name": "Assigned To",
                        "value": "None"
                     }
                  ],
                  "images": null,
                  "potentialAction": [
                     {
                        "name": "View Bug 11422",
                        "targets": [
                           {
                              "os": "default",
                              "uri": "REMOVED"
                           }
                        ],
                        "@type": "OpenUri"
                     }
                  ]
               }
            ]
         },
         "name": null,
         "thumbnailUrl": null
      }
   ],
   "entities": [],
   "channelData": null,
   "action": null,
   "replyToId": null,
   "value": null,
   "name": null,
   "relatesTo": null,
   "code": null
}

Thanks @nwhitmont and @benmetheny , I came to use HeroCard instead of O365ConnectionCard, so I am closing this issue.

How to prepare rich card using JSON template in c#


struct(lib): restructure the library modules

This commit restructures the library to be more conforming to the
mathematical theory of finite elements. This is an experimental choice
that might not pan out. But hey, this is an experimental library for now
so we'll see.
should solve #9 once discussions have panned out.

@achilleasev @mkochat please review


Bundler

Replaces the default tsc build instructions with the vite bundler, which significantly decreases build duration.
This PR also removes unused imports and restructures imports, which allows for easier testing in the future with a tool like jest.

I think this PR should be fine to merge, once the conflicts are resolved.

Sorry it looks like some more conflicts popped up after you resolved the old ones. I think you should have permission to merge yourself, feel free to do so once you resolve conflicts again.


Fix Activity TCN classifier node handling of unknown objects

PTAL @hdefazio and @cameron-a-johnson .


Fix missing error check

Description
Fix missing error check
Fixes #237
Type of change

Bug fix (non-breaking change which fixes an issue)

Codecov Report

Merging #329 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #329   +/-   ##
=======================================
  Coverage   79.33%   79.33%
=======================================
  Files          15       15
  Lines        1631     1631
=======================================
  Hits         1294     1294
  Misses        238      238
  Partials       99       99

Continue to review full report at Codecov.

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


support gnome-shell 3.34

fix #113
fix #112

Ah, that's all? It works on 3.34 now?

Yep. It works

Ok, I got a hold of gnome 3.34.
You broke the timer... You changed the the signal from 'value-changed' to 'notify::value' without updating the signal handler signature.
The new handler takes no params now, so pass the slider manually:
this.sigm.connect(this.slider, 'notify::value', () => this.slider_changed(this.slider.value));

Also here to make sure the fullscreen slider works:
this.slider.connect('notify::value', () => {
        this.delegate.slider_changed(this.slider.value);

    slider_changed (value) {
        if (this.tic_mainloop_id) {
            Mainloop.source_remove(this.tic_mainloop_id);
            this.tic_mainloop_id = null;
        }

I'm not sure why you reference issue #112. That one is about gnome-shell 3.28.

You broke the timer..

Sorry) I didn't see any errors in log and don`t check up timer,   because not not use it
Fixed it

Thx. Btw, Is this compatible with 3.32 btw? I'll probably make a branch for it otherwise.

Great extension. Thanks!
Tried codes on master branch. It doesn't work on my Ubuntu 19.10 with gnome shell 3.34 though.

Thx. It's merged now.
@diguabo Try again, I hadn't merged this pull request yet.

Thx. It's merged now.
@diguabo Try again, I hadn't merged this pull request yet.

works fine now. :)
Thanks!

I did, but it'll take a while to get reviewed.


user_script - attempt to concatenate local 'final_capacity' (a nil value)

I'm getting an error when using redis (Elasticache)
ReplyError: ERR Error running script (call to f_e275b1feeacbf5bcf4eb2e4a524a32d702c22ce4): @user_script:105: user_script:105: attempt to concatenate local 'final_capacity' (a nil value)
Any direction would be great.
Setup:
  redisClient = new Redis.createClient({
    host: "[removed]",
    port: 6379,
    password: "[removed]",
    db: 0
  });

  redisConnection = new Bottleneck.RedisConnection({
    client: redisClient
  });

  limiterGroup = new Bottleneck.Group({
    minTime: 0,
    connection: redisConnection,
    timeout: 300000
  });

minTime is set in update when creating from the group
const createLimiter = ({ id, minTime = 0 }) => {
  const limiter = limiterGroup.key(id);
  if (minTime !== 0) {
    limiter.updateSettings({ minTime });
  }
  return limiter;
};

Here's the scheduling call:
    const proxySpecificRequest = Proxy.buildRequestOptions(options, bestProxy);

    const scheduledRequest = bottlenecks[host][bestProxy]
      .schedule(()=>request(proxySpecificRequest))
      .then(result=>result)
      .catch((error) => {
        if (error instanceof Bottleneck.BottleneckError) {
          console.log(`MEH`);
        }
        console.error(error);
        process.exit(1);
      });
    return scheduledRequest;

Very nice catch. This error only occurred when a limiter doesn't have maxConcurrent or reservoir after calling updateSettings(). I've fixed it and released v2.13.2. Thank you for reporting it and providing code to reproduce it.
By the way, limiter.updateSettings() returns a promise, you might want to wait for it to resolve and/or catch potential errors.


Added note on how to choose the C++ debugger, update VS2017

Would be nice to add a screenshot, like the following:

but I've no idea what are the formatting requirements, so I'll leave it up to the docs team. /cc @conceptdev

The debugger selection is the easy part.  Finding a "C++ Dynamic Shared Library (Android) project" is the trick here. That's the screen shot you need. (I'm still looking).

Actually, we have an open issue to update this topic with a better C++ example than SanAngeles – I've included a note there to also add the necessary debugger selection screenshots.

@pwink53 it might be that you're missing the C++ Mobile workload entirely if you're not finding that project template:

With that, I see it as:


[service][dvc] generate snapshot after endBatchWrite complete

Create snapshots after end batch write complete

After a batch write, create a partition snapshot. The snapshot will be under the directory in the "./snapshot" folder for each batch-push version. The subfiles under "./snapshot" will be used for blob transfer.
The blob transfer manager are initial for Service, not only DVC.

How was this PR tested?

Run integration test at TestBatch. Snapshots are generated.

[WIP] plain table integration test will be added in next commit.
Does this PR introduce any user-facing changes?

[x] No. You can skip the rest of this section.
[ ] Yes. Make sure to explain your proposed changes and call out the behavior change.

Nitpick: I imagine you intend to prefix the commit message with [server] rather than [service]?


Share results with ibicus team and schedule next meeting

They will be attending the workshop on 1 March
Minimum communication for workshops at least

closing this as they have now been invited to UA monthly and weekly


docs: add dbgpt_hub usage documents

add dbgpt_hub usage documents.
some test cases for datasouces

We may be able to test this PR after #954 is merged :)

It works.
https://github.com/eosphoros-ai/DB-GPT/actions/runs/7270109706/job/19808708189?pr=955


Copy Entry before starting goroutine on Fire

Shared references to *logrus.Entry might cause concurrent writes to
Entry.Data.

I appreciate you submitting this, and I completely understand the issue at hand. I would question though if this is the right way to fix this, or if it shouldn't just be a requirement of the using code to not modify an entry until after a call to the logger has been made? It would seem to me a bad idea to delegate the copying at this level, as it should be controlled by higher-level code that is working with the actual log entries. I'm not rejecting this PR, but I really am undecided if this is the best approach.

I'll look at how other hook implementations deal with this, and make a decision soon.

So -- reviewing other hooks, and thinking about this, I believe the right approach is to move the logic that builds the actual stackdriver log message up, and to copy the fields into that type. The goroutine in Fire would be passed the built stackdriver message instead of a *logrus.Entry. Since this isn't work that I can do today, and because I've also noticed that quite a bit of cleanup needs to be done, I've merged this for now. I'll write a "correct" implementation at a later date, but as a stop-gap measure this is fine.

@kenshaw thanks for reviewing, merging and for the feedback. After reading your message, I'm starting to suspect that there's something wrong on my code (or some other hook is messing it up). I'm investigating it x(
What we're doing a lot is something like that:
logger := logrus.New().WithFields(...)

logger is actually a *logrus.Entry in this case. Then we do stuff such as:
logger.WithError(...).Error(...)
logger.WithField("k", "v").Debug(...)

But that should work fine even with sdhook as it was before, because WithFields copies the Entry and returns a new pointer. I think some other hook might be causing issues.

@kenshaw so yeah, there's a bug in my code in the order that hooks get registered. A hook that modifies Entry.Data was being registered after sdhook, so sometimes I was lucky to get the field on StackDriver, other times I was half-lucky to not get the fields but np panic either, and then there's some panics lol
I still think that for since sdhook creates a goroutine, it should operate on its own copy of the data (to ensure that what gets sent to stackdriver is exactly what was provided to Fire).

You are right that it should make a copy at the goroutine. However, as I mentioned above, I believe the "correct" thing would be to build the lowlevel Stackdriver API message and then kick off the goroutine. I'll revise this when I have time, but likely will not get to this in the next week.

@kenshaw no worries, thank you very much for the quick feedback!


Magic number extension functions

We should allow things like:
500.dp()
5.days

Because they are not magic numbers, they have units.
More about this in #3283
This PR adds a new flag to MagicNumber to allow this. Open questions:

Should we enable this flag by default?
Is ignoreExtensionFunctions a good name?

I changed the PR a bit: I enabled ignoreExtensionFunctions by default (last commit)


Not deleting cookie in dev

Expected Behavior
...
Service should delete the cookie.
Actual Behavior
...
Service doesn't delete the cookie with cookieService.delete("key"); and cookieService.deleteAll();,
I've tried adding the path in the second parameter as well.
Steps to Reproduce the Problem
...
Specifications

Version: ..."ngx-cookie-service": "^1.0.10", "@angular/core": "^5.2.0",
Browser: ... *
...

Hello akash!
Quite some people have problems similar to yours. Therefore, I assume that it's likely an implementation issue. Maybe I'm wrong, but there are a whole lot of things you can try. First of all, you should check out common cookie problems connected to localhost. Then, you can have a look at our FAQ and/or open a Stack Overflow question. If none of this helps, maybe it's really a problem with our package. Feel free to open another issue, if you manage to narrow down your problem (and feel like it's an issue with our cookie service).
Good luck with your bug hunt.
Cheers


Update README.md of Release Notes

.NET Core February 2019 Updates.

@leecow FYI: Looks like it was missed in Feb updates.


SPSB: SH: Labour Component

Worker Component (Picture, name, trade, rate, contact details, experience, availability)
Dummy Object containing multiple workers
Back button

created component but need data


Missing class attributes in non-C#-languages

Hello Microsoft
There seams to  be an issue generating the class signature:
In C# there are all class attributes correctly shown
[System.AttributeUsage(System.AttributeTargets.Assembly, Inherited=false)]
[System.Runtime.InteropServices.ComVisible(true)]
[System.AttributeUsage(System.AttributeTargets.Assembly, AllowMultiple=false)]
public sealed class AssemblyConfigurationAttribute : Attribute

in all other languages they are missing and only a summary of all applied attributes listed:
VB.NET:
Public NotInheritable Class AssemblyConfigurationAttribute
Attributes
AttributeUsageAttribute, ComVisibleAttribute, AttributeUsageAttribute
in VB.NET (and the other languages) I have e.g. no clue that the AttributeUsage is AllowMultiple=false. I only see there are 2 AttributeUsageAttributes applied.
Please generate the signatures similair to C#, in particular (VB.NET example):
<System.AttributeUsage(System.AttributeTargets.Assembly, Inherited := False)>
<System.Runtime.InteropServices.ComVisible(True)>
<System.AttributeUsage(System.AttributeTargets.Assembly, AllowMultiple := False)>
Public NotInheritable Class AssemblyConfigurationAttribute
	Inherits Attribute

Thank you.

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

ID: e3925ee5-a030-35ef-7cfd-0ccc90f30bb4
Version Independent ID: a8927033-0017-3af9-eacc-61fe7fc15731
Content: AssemblyConfigurationAttribute Class (System.Reflection)
Content Source: xml/System.Reflection/AssemblyConfigurationAttribute.xml
Product: dotnet-api
GitHub Login: @rpetrusha
Microsoft Alias: ronpet

@HugoRoss thank you for bringing this to our attention!
@mairaw seems to be a problem with the doc generations. If you scroll to the top and change the language of the article to VB.NET (or anything besides C#) the attribute list is gone.


Fixed encoding for date shown in qrc header, now is proper UTF-8

Fixes first part of #9.

Thanks

You're welcome, thanks for your work on this project :+1:


Cannot create folder with Cyrillic names in the Project view

Describe the bug
Attempt to create folder with Cyrillic letters in the name. The error displayed that name for folder is is invalid.
Same when attempt to import file with Cyrillic characters in name.

Currently working as designed.   Is there a strong argument for making a change?

Actually not. But i have initial confusion when I see the message. Maybe some text change that will indicate what rules for names user should follow. Not some generic error, but something more descriptive, like “Invalid folder name. Folders should consists from Latin letters and digits only” or something like that. Same for filename error message. If somebody put Cyrillic С inside the filename it can be fun :)


Enable API reference docs to show accessor methods

Previously, the API docs section of cupy-xarray has been disabled on because import cupy doesn't work on Readthedocs CI without CUDA. Luckily, there is now a cupy-core package on conda-forge (see https://github.com/conda-forge/cupy-feedstock/pull/241) that makes CUDA optional, so we can use that to build the API docs!
Preview at https://cupy-xarray--44.org.readthedocs.build/api.html

(Yeah, not sure why some of those API methods are centre-aligned :sweat_smile:)
I've also updated the 'Contributing documentation' section in the contributing guide which had some typos. Full steps to reproduce the docs build are:
conda env create --file ci/doc.yml
conda activate cupy-xarray-doc

cd docs
make html

References:

https://github.com/conda-forge/cupy-feedstock/issues/229
https://sphinx-autosummary-accessors.readthedocs.io/en/stable/usage.html

Fixes #5

(Yeah, not sure why some of those API methods are centre-aligned 😅)

I think that's because those don't have docstrings (DataArray.cupy.get() doesn't, either, but it shares the table with methods that do have one).

Edit2: I'd also advise against using numpydoc and napoleon together, they don't always work well together

Ok, removed numpydoc at commit 5087d89ba012c8afafade10c5e1601db721ce06f!

Edit3: to install the package, I'd follow the recommendation documented by RTD (add -e .. to the pip section in the environment file) – this is also what we're doing in xarray

Ah yes, I was trying with one dot ., but forgot that two dots .. are needed to move up a directory! Done at ccc192513bb745465b2da95ea483050e1ba1dc91 (and contributing instruction docs also updated to remove pip install --editable=. part).

Edit: looks like all of them are centered, just that some of them have longer strings

Hmm you're correct, they are all center-aligned. Let me try to play around with the docstrings and/or the sphinx template.

Ok, couldn't figure out how to remove the center-alignment :sweat_smile:, I had a look at other xarray-contrib repos using the Furo theme, and it seems like xwrf has the same issue, but cf-xarray doesn't.
So... I just added in the some docstrings to make it look less empty. Maybe @dcherian or someone else can look at cf-xarray's css file and figure out how to remove the centre-alignment issue.

Nice work @weiji14 I've added you as maintainer so you should be able to click merge here :)
re: center-aligning. I do not recall doing anything specific. Apparently flox has this issue too, i suspect it is a regression in furo

re: center-aligning. I do not recall doing anything specific. Apparently flox has this issue too, i suspect it is a regression in furo

Ah ok, maybe best to report this upstream then at https://github.com/pradyunsg/furo? I'm not sure whether the API docs in flox or cf-xarray looked like this before, so can't tell if it's a regression bug. It looks as though Furo is centering tables by default, so maybe we need a directive to left align it, but I couldn't find out exactly how.

Nice work @weiji14 I've added you as maintainer so you should be able to click merge here :)

Thanks! You must have read my mind. Secretly, I've been hoping to get maintainer access after this PR because I have some free time next week, so maybe (just maybe) I'll put in some time to update #10 :smiling_imp:
Will leave this open a bit longer in case anyone has other suggestions, otherwise I'll go ahead and merge this sometime tomorrow.


HelloHacktoberfest - React

Hi there..
Can you provide a description of the issue?
I am interested in working on it..

You have to print Hello Hacktoberfest using Reactjs. You can use your won creativity. Do follow the folder naming convention mentioned in Contributing file. And do check the other repo ToDoApp as well. Dont forget to give stars to the repo. Thanks

I want to work on this issue, Can you assign me?

@abhishek-kumar-91 I think someone is working on this issue. So I will create separate issue of this and assign it to you.

You can assign me another issue that lebel with the hacktoberfest

@ajjayymahato Thank you..

@abhishek-kumar-91 Yes i have made another issue, please check and comment on that then only i will be able to assign you


Fix error when called with prompt containing newlines

Closes #19
I'm not sure if format_item will also need a patch, but my rudimentary tests show that it does seem to cope with newlines at least somewhat in its current state.

@Conni2461 I'd love if you could review this.

Ping.

sorry for the late response. thanks for the fix :D


EM-3196: Updated functional test cases to run with serenity integrati…

…on runner
Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

this is covered in #259


Derived arguments (computed props) within a schema

Hey everyone!
Firstly – Zod is awesome. Picked it up recently and I've been having a blast working with it.
In recent weeks I've encountered a situation which I thought might benefit from a discussion here.
We're currently in the process of refactoring an old codebase that used mobx-state-tree to manage it's state. MST has a really similar approach to Zod's runtime type system, with a nice API for adding computed properties to a schema:
const UserStore = types
  .model({
    users: types.array(User)
  })
  .views(self => ({
    get numberOfAdults() {
      return self.users.filter(user => user.age > 18).length
    }
  }))

Now, I came across a good suggestion to wrap Zod's schema.parse({}) call in a factory function and add the computed functions in before returning:
const UserSchema = z.object({ name: z.string(), age: z.number() })

const UserCollectionSchema = z.object({
  users: z.array(UserSchema),
})

const createUserModel = (input: Partial<z.infer<typeof UserCollectionSchema>>) => {
  const model = UserCollectionSchema.parse(input)
  return {
    ...model,
    get numberOfAdults() {
      return model.users.filter((user) => user.age > 18).length
    },
  }
}

createUserModel({ users: [{ name: 'Jon', age: 29 }] }).numberOfAdults // => 1

This is a really clean suggestion, and would definitely be the route I'd look to take. However... consider the following change to the user schema:
const UserSchema = z.object({ name: z.string(), dateOfBirth: z.date() })

Ideally I'd be able to expose age as a computed property, deriving its value from the date of birth field. This is difficult to achieve without nesting factories here - the consumer of UserCollectionSchema shouldn't care whether age is a derived property or not. The power here is in nested object schema's each adding their own computed properties that can be carried around alongside the validation logic.
I'm pretty new to using Zod - this might be entirely outside the scope of the project, or something Zod supports now/in the future. There seems to be a few outstanding discussions that relate to this subject but all seem either incomplete or stale, so I thought it was worth asking!
(Possibly related: https://github.com/colinhacks/zod/issues/38)

Actually, seems this is pretty simple to do with transform:
const UserSchema = z
  .object({ name: z.string(), dateOfBirth: z.number() })
  .transform(values => ({
    get age() {
      dayjs(values.dateOfBirth).diff(dayjs(), 'year')
    }
  })

@johlampert as an MST fanboy I am wondering how you deal with the other things MST offers, are you adding any reactivity to your zod objects? Plain mobx? How are you making sure the "views" are reactive?

Has this issue been resolved?


Integrate frequency visualization with Datastore

Wire up frequency visualization service to obtain IP addresses data from the real Datastore. Using the vis-network library (MIT license) to visualize graph nodes (unique IP addresses) and graph edges (number of connections).
The datastore should contain either mock data or real data.

Switched from simple groups view of network to a wider neighborhood view with longer edges and no changes in proximity based on number of frequencies (simple groups view had an issue with commonly connected nodes being too close to each other). Added in better physics and stabilization so graph won't move even with a larger number of nodes or frequencies.

Hard-coded three groups based on first three bits of IP address. Should have three main groups ― Class A/B, Class C, Class D/E ― as well as a way to dynamically group more crowded addresses within those groups (e.g. if all packets are in Class C).

Note: at the moment, IP addresses are completely displayed as strings. To be careful, we could try obfuscating them (maybe only showing several digits?).


Update AmbientLightDocument for Foundry VTT v10.276

To Change
AmbientLightDocument
Kind of Change
Update
Additional Info
No response

I'd like to try this one.


Fix issue with 404 error when logging out from the client applications

Fixes an issue where the user could no longer log out from the application (404 error on the /logout route).

Merged. Deleting branch.


Slanted map

The basemap is slanted as though you're flying over the city not looking down on it.

Hello ! I would like to work on this issue, could you suggest me where to start?

@Amritanshu02 thanks for you offer! but I think we'll be able to handle this ourselves

@ericahagen are you simply loading https://mapkibera.github.io/watsan/nairobi/?