can not use

Start building sites …
ERROR 2021/04/24 17:58:51 Configuration Error 配置文件错误

You haven't configured the uBlogger version param correctly yet. See #basic-configuration
你还没有正确配置 uBlogger 的版本参数. 参考 #basic-configuration

Total in 121 ms
Error: Error building site: TOCSS: failed to transform "css/style.scss" (text/x-scss). Check your Hugo installation; you need the extended version to build SCSS/SASS.
(base) xiaopeng@xiaopeng-HP-Z800-Workstation:~/Hugo/hugo-blog$ hugo -d docs
Start building sites …
ERROR 2021/04/24 18:00:36 Configuration Error 配置文件错误

You haven't configured the uBlogger version param correctly yet. See #basic-configuration
你还没有正确配置 uBlogger 的版本参数. 参考 #basic-configuration

ERROR 2021/04/24 18:00:36 render of "taxonomy" failed: execute of template failed: template: taxonomy/terms.html:52:16: executing "taxonomy/terms.html" at <partial "footer.html" .>: error calling partial: "/home/xiaopeng/Hugo/hugo-blog/themes/uBlogger/layouts/partials/footer.html:36:30": execute of template failed: template: partials/footer.html:36:30: executing "partials/footer.html" at <index .Site.Data.authors $authorName>: error calling index: index of untyped nil
ERROR 2021/04/24 18:00:36 render of "taxonomy" failed: execute of template failed: template: taxonomy/terms.html:52:16: executing "taxonomy/terms.html" at <partial "footer.html" .>: error calling partial: "/home/xiaopeng/Hugo/hugo-blog/themes/uBlogger/layouts/partials/footer.html:36:30": execute of template failed: template: partials/footer.html:36:30: executing "partials/footer.html" at <index .Site.Data.authors $authorName>: error calling index: index of untyped nil
ERROR 2021/04/24 18:00:36 failed to render pages: render of "home" failed: execute of template failed: template: index.html:52:16: executing "index.html" at <partial "footer.html" .>: error calling partial: "/home/xiaopeng/Hugo/hugo-blog/themes/uBlogger/layouts/partials/footer.html:36:30": execute of template failed: template: partials/footer.html:36:30: executing "partials/footer.html" at <index .Site.Data.authors $authorName>: error calling index: index of untyped nil
Total in 101 ms
Error: Error building site: TOCSS: failed to transform "css/style.scss" (text/x-scss). Check your Hugo installation; you need the extended version to build SCSS/SASS.

Did you install an extended version of Hugo? This theme needs it. If not, you can find it at https://github.com/gohugoio/hugo/releases

Did you tried to put .json file with data about author into /data/authors/.json? Where  is author which will be displayed on the site.

@kszpieg a couple of versions ago I made it so that it was not required))

@SpongeBab  did the solution help you from @tomaja-linuxo?

@kszpieg a couple of versions ago I made it so that it was not required))

I had a similar problem yesterday and the solution from @tomaja-linuxo didn't help me too much :) Just add .json to the path.
at <index .Site.Data.authors $authorName>: error calling index: index of untyped nil
It seems that @SpongeBab just has not required a path :)

@tomaja-linuxo @kszpieg Thank you!
@uPagge Yeah,The hugo-extended version is required.
And I went to the LoveIt website , browse the official documents.
It help me to solve the problem.
I think there should have a brief guide for installation in README .Because I haven’t use the LoveIt theme.

Glad the issue has been fixed.
Hopefully this month the documentation will be completely updated))


Failing tests: tests/snapshots out of date

It looks like the latest few releases have broken tests caused by a change in loggin output. Not sure when it happened, but it's causing tests to fail. Here's the output from running cargo test locally on my machine:
     Running target/debug/deps/echo-7079832437b58e65

running 4 tests
test with_poll ... FAILED
test with_announce ... FAILED
test without_announce ... FAILED
test with_error ... FAILED

failures:

---- with_poll stdout ----
thread 'with_poll' panicked at 'Unexpected failure.
code=<interrupted>
stderr=```"WARN - Polling for changes every 500ms ms\n"```
code=<interrupted>
stdout=```""```
stderr=```"WARN - Polling for changes every 500ms ms\n"```
', /Users/david/.cargo/registry/src/github.com-1ecc6299db9ec823/assert_cmd-1.0.3/src/assert.rs:149:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

---- with_announce stdout ----
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Snapshot Differences ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Snapshot file: tests/snapshots/echo__with_announce.stderr.snap
Snapshot: with_announce.stderr
Source: tests/echo.rs:132
-old snapshot
+new results
───────────────────────────────────────────────────────────────────────────────────
std_to_string(&mut main.stderr)
────────────┬──────────────────────────────────────────────────────────────────────
    1       │-WARN - Polling for changes every 500 ms
    2       │-
          1 │+WARN - Polling for changes every 500ms ms
          2 │+
────────────┴──────────────────────────────────────────────────────────────────────
stored new snapshot /Users/david/Developer/src/cargo-watch/tests/snapshots/echo__with_announce.stderr.snap.new
To update snapshots run `cargo insta review`
thread 'with_announce' panicked at 'snapshot assertion for 'with_announce.stderr' failed in line 132', /Users/david/.cargo/registry/src/github.com-1ecc6299db9ec823/insta-0.16.1/src/runtime.rs:995:9

---- without_announce stdout ----
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Snapshot Differences ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Snapshot file: tests/snapshots/echo__without_announce.stdout.snap
Snapshot: without_announce.stdout
Source: tests/echo.rs:167
-old snapshot
+new results
───────────────────────────────────────────────────────────────────────────────────
std_to_string(&mut main.stdout)
────────────┬──────────────────────────────────────────────────────────────────────
    1       │-without announce
    2       │-
────────────┴──────────────────────────────────────────────────────────────────────
stored new snapshot /Users/david/Developer/src/cargo-watch/tests/snapshots/echo__without_announce.stdout.snap.new
To update snapshots run `cargo insta review`
thread 'without_announce' panicked at 'snapshot assertion for 'without_announce.stdout' failed in line 167', /Users/david/.cargo/registry/src/github.com-1ecc6299db9ec823/insta-0.16.1/src/runtime.rs:995:9

---- with_error stdout ----
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Snapshot Differences ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Snapshot file: tests/snapshots/echo__with_error.stderr.snap
Snapshot: with_error.stderr
Source: tests/echo.rs:202
-old snapshot
+new results
───────────────────────────────────────────────────────────────────────────────────
std_to_string(&mut main.stderr)
────────────┬──────────────────────────────────────────────────────────────────────
    1       │-WARN - Polling for changes every 500 ms
    2       │-
          1 │+WARN - Polling for changes every 500ms ms
          2 │+
────────────┴──────────────────────────────────────────────────────────────────────
stored new snapshot /Users/david/Developer/src/cargo-watch/tests/snapshots/echo__with_error.stderr.snap.new
To update snapshots run `cargo insta review`
thread 'with_error' panicked at 'snapshot assertion for 'with_error.stderr' failed in line 202', /Users/david/.cargo/registry/src/github.com-1ecc6299db9ec823/insta-0.16.1/src/runtime.rs:995:9

failures:
    with_announce
    with_error
    with_poll
    without_announce

test result: FAILED. 0 passed; 4 failed; 0 ignored; 0 measured; 0 filtered out; finished in 30.19s

I think this might be related to Jenkins not having been run during the last few releases.

The tests don't really run on macOS to start with. I’ve restored running them in CI anyway.

Oh, they don't? Weird, they seem to at least run. I think either the Debug or Display impl of the duration type being used in the failing test above has changed and that's the reason the tests are failing.
I'm bringing it up because right now Nixpkgs packages this tool but the package is currently broken in repo for macOS. It's a great tool, maybe I can try my hand at a fix if you can point me in the direction of this Debug|Display impl that's causing failing tests?
Or if there's a root cause I'm not seeing that's further work, I suppose I can send a PR to Nixpkgs to skip tests on Darwin.

I've fixed the display discrepancy tests (well, I've changed the tests to pass, and I'll fix the actual issue upstream in the next point update), but the tests still won't work on macOS for platform differences reasons at a different level (iirc, notify, due to fsevents, but might be something else), so it's not really testing what it's purporting to. They don't work on Windows for... yet another reason, which I'm really confused about and haven't tracked down.
You can absolutely use this issue as justification for not running tests in the nixos package, if needed.
Also, the tests are stateful and need a directory to be cleared (or to run somewhere that's cleared every time, like CI) to complete, which is awful, but as mentioned in the latest commit here, the real behaviour tests are in watchexec, and it wasn't really a priority to have them here, given it's quite a bare "shell" over it. Always happy to have more / better tests contributed, of course.

Weird! Would the issue in tweet you linked happen to be cause by Windows using a different encoding (UTF-16, perhaps?) than on the usual unix-y system?

Most likely, but how to make it either work...?

I'm seeing the same thing when trying to patch this for nixpkgs to include libiconv as a Darwin dependency: https://github.com/passcod/cargo-watch/issues/170

I'm seeing the same thing when trying to patch this for nixpkgs to include libiconv as a Darwin dependency: https://github.com/NixOS/nixpkgs/issues/120688

Most likely, but how to make it either work...?

That's a good question. I don't know how this comparison is being made, but some kind of normalization would probably be necessary? I don't know much about the idiosyncrasies of the Windows platform, but maybe doing an in-memory comparison where you specifically encode the file contents to UTF-8 would fix the issue?

It's all done by the insta tool, so maybe that's got an option. It might also be newlines: https://github.com/mitsuhiko/insta/pull/172

Well, updating insta to the latest 1.7.1 does still run the tests properly, but there's still an issue with an extra ms being tacked on to the output that's failing the tests same as above.

https://github.com/watchexec/watchexec/issues/191

I've updated the tests to insta 1.7.1 among other things for 7.7.1, may help here.

@davidarmstronglewis Can you handle the nixpkgs side to get it to latest?

PR's been updated, confirming that I can disable the disabling of tests :)
Nice work!


chore: Upgrade to React 18

https://github.com/dxos/protocols/issues/1321

Current dependencies on/for this PR:

main

PR #40   👈

PR #41

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: 🔄 Waiting for checks to pass
This pull request is currently waiting for CI and mergeability checks to pass before being merged.
This comment was auto-generated by Graphite.

Job Reference: Je0Vzki5i1gX182k5g3W


Add more OS to CI matrix

This adds most of the popular/highly used Linux distributions to the test matrix. I would have liked to add OpenSUSE too, but their mirrors are having trouble and I couldn't install packages in that. Maybe a TODO for future.

The ubuntu devel and fediora rawhide failures are expected as this PR does not have the openssl 3.0 fix, but I really do not understand the fedora:latest issue. Sounds to me as the krb5-config script is broken there somehow ...

@omajid can you rebase and comment out fedora:latest for now?
once devel/rawhide pass I will merge and then look into fixing latest myself

And rawhide failed to install a package ... hilarious
but fixed itself after a re-run

Thanks a ton for this PR, it's awesome to be able to test more broadly


⚠ Secret Website 3 has degraded performance

In 3d36cd8, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 21523 ms

Resolved: Secret Website 3 performance has improved in 06259ca.


[zh-cn] localize blog: 2023-05-04-statefulset-autodelete.md

This blog has not zh version yet.
I will localize it. Open the issue to avoid possible dup.
blog/_posts/2023-05-04-statefulset-autodelete.md
/assign
/language zh

This issue has been fix in https://github.com/kubernetes/website/pull/41109

/close


[docs] Updated compatibility table in README

Coverage remained the same at 99.794% when pulling 1c2998edef8de3ff47d852cf90be7a5b22dc37d3 on readme-compatibility-table into 1bb3cad035701b7f402533176b9b1ef1ee5838bd on master.


[Bug] Elevation Ruler completely locks up all movement after attempting to move a token

Attempting to move any token with Elevation Ruler active causes this error

Afterwards, moving the mouse cursor to any point on screen causes this error

And finally, if I manage to unselect the token by going to the measurement tools then back to the token tools, this error comes up every time I move the cursor over any token

Can confirm this is also happening to me on v12.329

Same here.

This may be fixed now as of PF2e v6.1.11 . Tried out the module and it seems to be working again. You can see that they changed how the drag measurement was implemented to better accommodate modules like this one. For people who still have the issue, try updating the game system and the PF2e elevation ruler integration, if you have it installed.

The underlying issue should be addressed in v0.9.10.


[Coverity CID :197621]Incorrect expression in /tests/kernel/static_idt/src/main.c

Static code scan issues seen in File: /tests/kernel/static_idt/src/main.c
Category: Incorrect expression
Function: test_static_idt
Component: Tests
CID: 197621
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

*** CID 197621:  Incorrect expression  (ASSERT_SIDE_EFFECT)
/tests/kernel/static_idt/src/main.c: 157 in test_static_idt()
151     volatile int error;     /* used to create a divide by zero error */
152
153
154     TC_PRINT("Testing to see interrupt handler executes properly\n");
155     _trigger_isr_handler();
156

CID 197621:  Incorrect expression  (ASSERT_SIDE_EFFECT)
Argument "int_handler_executed" of z_zassert() has a side effect because the variable is volatile.  The containing function might work differently in a non-debug build.

157     zassert_not_equal(int_handler_executed, 0,
158       "Interrupt handler did not execute");
159     zassert_equal(int_handler_executed, 1,
160           "Interrupt handler executed more than once! (%d)\n",
161           int_handler_executed);
162


Cell 5 of notebook 03 has issue

A further look into broker.log file reveals that port 1883 has been used by the package mosquitto. I don't recall when I installed that package, but to make things work, I need to disable this package so 1883 becomes available again.
# systemctl disable mosquitto
# systemctl stop mosquitto


feat(fs): add node fs support

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


OKTA-449311 Add support for authenticator password settings.

Builds are failing due to AWS outage of our MFA test helper tool.


Loading data without create tables

I am trying to connect to an existing db and I want to load some data from a table.
var db = new SQLiteConnection("Mydatabase.db");
var query = db.Query("SELECT * FROM TESTSNAME");
query object contains 5 TestsModel elements (it is fine), but all the object parameters are always null
[Table("TESTSNAME")]
public class TestsNameModel
{
[PrimaryKey]
[MaxLength(2)]
public string Code { get; set; }
[MaxLength(25)]
public string Name { get; set; }
}
Table
CREATE TABLE [TESTSNAME] (
[NAME] varchar(25) NOT NULL,
[CODE] varchar(2) NOT NULL PRIMARY KEY
);
Can you help me with this? I don't want create the table at the beginning, but I want be able to work with an exisisting db.
Thanks
Armando

CreateTable is poorly named, think of it more as RegisterTable - it will only create the table if it doesn't exist. It will also migrate (add columns) to an existing table.
Just call CreateTable<TestsNameModel>() and you're all set to query.

Hi Frank,
thanks you your answer, but it does not solve the issue, my I did not explained it correctly.
I already have a db file with the schema already in place, so I don't need to create table or other schema objects, I need simply to get data from it. When I use the Query statment I got the list of object, but the object does not contains any value. Please check the image to see what I mean

OK, I'll have to look at the code path to figure out what's going on.

Thanks. it is working now. I just updated the libraries from Nuget anf it is fine.
Thanks a lot.

Glad to hear. Yeah that was confusing!


Polyfilling modules

The presentation in this repository articulates integrity as an important goal of built-in modules. When we discussed this topic in committee, additional, opposing goals were raised in the area of hackability, for the ability to do polyfills, bug fixes, and virtualization.
This post focuses on polyfilling new features to look like built-in ones, but the techniques may work as well for the other cases mentioned above.
Feature requests to support polyfilling
When new APIs come into JavaScript and its host environments, these can often be filled in by polyfills, JavaScript code which achieves the same goal. Some cases that polyfills cover for in terms of the evolution of specifications:

An class/library is entirely missing
An individual function/method is missing within a class/library
A function or constructor changes behavior, for example by adding an overload

Some ways polyfills are invoked today:
a. A separate script tag in a page, as recommended by polyfill.io
b. Importing a module which mutates the global object and/or objects within that, e.g., babel-polyfill
c. Importing a module which exports an object that has the same behavior as a built-in, also known as a ponyfill
Option c. above doesn't require any special support/integration from the platform--it's just a module that matches the built-in interface--so the rest of this document focuses on cases a. and b.
How polyfilling could fit into package-name-maps
Native modules are proposed to enable polyfilling on the web with a different mechanism. The Layered APIs proposal suggests a syntax like "std:foo|https://bar.com/baz.js" for a module specifier with a fallback. The package name maps proposal proposes a refinement of this syntax, where the fallback is listed in the map.
Both of these mechanisms only permit the case 1. above, not 2. or 3. If the standard library is supported at all, then the fallback will not be used, so it's not possible to add additional methods or cases within methods.
If the package-name-map can remap the uses of the standard library, then polyfills could be supported for cases 2. and 3. For example, if the syntax "@std/<lib>" is used, for various values of <lib>, and this is remappable via package-name-map, with simply a default value of being the built-in library, then a polyfill could wrap the built-in version of a standard library using package-name-map's feature enabling different paths to have different mappings.
Polyfilling across embedding environments
Option b. above for using polyfills, in conjunction with modern tooling, can work across Node.js and the Web Platform to use polyfills against current JS and Web APIs in practice. Should we have a cross-environment way to invoke polyfills for built-in modules?

<script
  type="polyfill"
  module="temporal"
  src="https://example.com/temporal.js"
></script>

if module="temporal" is already supported by the browser, it decides to not load it, making it transparent to the developer. There could be another attribute to let the developer force the browser to load the module in cases where the module is supported but it's missing a method or something.
used as
import { Instant } from temporal;

notice the lack of quotes on the import. Since this is supposed to be the standard library, urls don't make sense here. the lack of urls will set the apart from a random module.
There's also the option of developing some api to allow developers to register standard modules.
// main.js or index.html head script
polyfills.load('temporal', {
  url:'https://example.com/temporal.js',
  force: true, // or falsy
});

or doing it from the perspective of the polyfill
// temporal-polyfill.js
var temporal = { Instant: class Instant {} }
// inspired by customElements.register
polyfills.register('temporal', temporal, { force: true })

but this doesn't have the benefit of not loading the script like the other suggestions do.
But above all, I suggest staying away from magic strings like std:temporal|https://example.com/temporal.js they just make everything confusing.

Note, there are also polyfills which do not introduce new features but just fix bugs, for example: https://github.com/fanmingfei/array-reverse-ios12

There could be another attribute to let the developer force the browser to load the module in cases where the module is supported but it's missing a method or something.

How?

a force boolean attribute that loads and uses the given implementation even if the browser already supports the module

Some bugs require full replacement to patch; the best practice today imo will remain so in the future: the polyfill code should be the source of truth for determining if it needs to make any changes.
Maybe there could be a way to load some kind of predicate module that can dynamically determine if it needs to load?

It seems preferable to perform at most one HTTP request, if possible. Including the requested version and the browser's current version of the module in that request should be adequate, especially since the polyfill server can always just serve a complete reimplementation if it likes (or one that dynamically detects what needs patching, but includes all the necessary code).
In the not-so-distant future, when virtually all browsers support virtually everything that a certain standard module is supposed to support, but a few new features have been recently added to the spec, I sincerely hope the polyfill mechanism is capable of providing just those new features. Otherwise our polyfills are just going to keep getting bigger as the standard library grows, rather than eventually shrinking and disappearing.

That would be the best scenario. But it's more difficult to patch a module than to patch the global. I guess it's just a different kind of problem. This might be possible with the third suggestion of an API that lets talk user supply a module implementation programmatically. This might allow the one http request to provide the patch based on the user agent. Slowly but surely this server request would eventually be a noop

Related discussion: https://github.com/drufball/layered-apis/issues/34

@domenic 's import-maps proposal has been evolving well into a solution for all of the issues we discussed in this thread. It seems like a technically good solution to me.
From here, I'm wondering: Are we comfortable with the system for polyfilling being determined per-embedder, or should we have a system that works across embedders? Can import-maps be the this system to apply across embedders, or would we need some changes, or a different system? Are there different needs in different embedders that motivate separate systems for controlling module polyfills?
I'm content with import-maps being developed as a WICG/WHATWG specification, and in my opinion, it'd be nice if this polyfilling solution can be applied across the JS ecosystem as a whole, not just in the web.
Related discussion on import-maps and Node: https://github.com/nodejs/open-standards/issues/13

If the standard library is part of the language, then i think the polyfilling method needs to be as well.

If Node and the Web have different needs here, I think it should be fine to develop the polyfilling solution in hosts, rather than within the language. Maybe we could include a requirement in the specification that the host must include some such mechanism. I don't understand exactly what is different about their needs, though.

I disagree. Shimming an initial primordial state is not a host specific concept, and for many existing shims, is already done in a non-host-specific manner. We should uphold this.
When language-wide issues are left to hosts, we have failed. We failed to codify the host-independent behavior that all platforms must implement and all clients may count on. If the consequence of leaving it to hosts to define is that they gratuitously differ from each other in pointless ways, then we have failed even worse.

we should either propose a practical mechanism

@erights Be my guest!

@littledan This in conjunction with inline modules: reference giving an idea of how this would work.
Requiring a hand-shake with the host environment is certain to introduce a very sticky situation  with library authors importing standard modules/polyfills.
Just as i can use WeakMap today as if it where native within a polyfilled runtime. I too should be able to import standard libraries without any convoluted hand-shake with the host environment because as a library i'm implicitly not in control of that hand-shake(the role is mostly delegated to the consumer) and is a good model going forward with esm standard modules.
For example in the linked reference i mentioned a fictional module "Window" that could be polyfilled, which can be extended to demonstrate how current day feature detection is done and how it can be preserved going forward in the face of this proposal.
module Window extends Window {
    // could be any keyword, super, this, implements etc...
    if (!implements(Window)) {
        // implement polyfill when the extending module does not exist.
    }
}

// or go full in on syntax
module Window implements Window {
// only if Window is not already implemented
// this might have the benefit that the vm could better optimize not loading/running this if Window is indeed implemented.
}

Arguable this is at odds with a "magic string" syntax direction. Given that direction makes this virtually impossible, a facet that i would hope this to be a data-point against that going direction(magic strings).

Fallbacks like
std:virtual-scroller|https://some-cdn.example/virtual-scroller.mjs

looks beautiful decision, but will not work in a serious part of use cases. In this case, we have problems, for example, with shared between polyfills helpers. Polyfills should be able to be bundled to one file.
We need at least an additional way to polyfill from usual JS code. By calling usual methods - syntax solution will cause a problem for old engines.
It should work synchronously. Why synchronously? Now, we load polyfills before all code. No one will do
waitForLoadingPolyfills.then(() => {
  runAllTheRestCode();
})

We need a registry.
Something like:
STDLibraryRegistry.get(name);
STDLibraryRegistry.setModule(name, value);
STDLibraryRegistry.setModuleProperty(name, key, value);

Also, this way could help with polyfilling built-in modules because import from stand modules namespace could be simply transpiled to calling methods of this registry:
import { len, map } from "std:builtins";
// =>
const { len, map } = STDLibraryRegistry.get("std:builtins");

@littledan any feedback?

Thanks for this detailed review.

Polyfills should be able to be bundled to one file.

import-maps is based on different things being in different resources, if I understand correctly. Is your suggestion based on performance, deployability or something else? I believe WebPackage should help with some of those issues.

syntax solution will cause a problem for old engines.

I'm wondering if @rich-harris's https://github.com/rich-harris/shimport and @guybedford's shim in https://github.com/guybedford/es-module-shims alleviates these concerns. Old engines don't have built-in modules anyway...

It should work synchronously.

I can imagine usages of your suggestion for synchronous dynamic access, but I don't understand why it's a requirement.
In browser-native implementations, the import-maps solution (including as a way to replace get-originals) should be as synchronous as an import statement. For transpiler output, if built-in modules are being entirely polyfilled on that platform, then there should be no particular barrier to implementing this API as something transpiler-internal; if they are not being entirely polyfilled, then they can be supplied with import-maps and used via import statements. Would this work?

@littledan

Is your suggestion based on performance, deployability or something else?

Take a look an architecture of standard library actual polyfills. core-js contains thousands of files, hundreds shared between modules helpers. @ljharb es-shims project also contains many shared between polyfills helpers like es-abstract. Even with WebPackage loading all of those files separately and asynchronously will cause critical slowdown.

I'm wondering...

We can't test the availability of new syntax by Function like in the first repo example at least because it will cause CSP issues. Without testing and available non-syntax solutions, we will be forced to completely replace of modules system and built-in modules even if they are available in the engine.

Old engines don't have built-in modules anyway...

We talk about polyfilling. Polyfilling and transpaling should provide it even for old engines.

I can imagine usages of your suggestion for synchronous dynamic access, but I don't understand why it's a requirement.

@ljharb already wrote one part of the answer in another issue, the second you can find above.

@ljharb wdyt about https://github.com/tc39/proposal-javascript-standard-library/issues/2#issuecomment-448530196 ?

@zloirock i agree completely with the problems you describe; I’m not sure about your suggested solution but that’s worth exploring.

@WebReflection I've been thinking some similarish thoughts to bits of what you said, but unsure how you would go about it really... Did you have ideas on how you would bake that in? I'd be very curious to hear thoughts on that.

@bkardell the only easy solution I could think of, since based on new things that won't break anything we know already, is allowing a do expression to define the static import.
import foo from do {
  let gotcha = false;
  try {
    failIfGotcha();
  } catch(o_O) {
    gotcha = true;
  }
  gotha ? '@ungap/foo' :  'std:foo'
};

@WebReflection I'm not sure I understand... you're suggesting you'd do that everywhere, or you'd do that to build some map of exports that your app uses but is otherwise left as an exercise for each thing, or at a higher level through some tooling?

@zloirock

Without testing and available non-syntax solutions, we will be forced to completely replace of modules system and built-in modules even if they are available in the engine.

One thing I think you can count on is, built-in modules would only be shipped if it's together with import-maps--you won't have to make a built-in module polyfill/wrapper work without import-maps. So, you'd have two versions: the 100% polyfill shipped as a module and bundled as it is today, or the new thing where you use import-maps and modules wrapping other modules. Would this be too complicated an architecture?

That can’t be counted on unless import maps are part of the language; there are more engines than browsers and node.

@littledan sure, it can simplify some cases, but it's not a solution for the indicated problem.

Hi everyone, I'll share a common use case where the polyfilling fallback option will be a problem.
I'm the author of @ngx-pwa/local-storage, the most popular Angular library for local storage. The main goal of the lib is the same as kv-storage: having an efficient storage via indexedDB, but with a simple API like localStorage.
There are dozen of librairies like this one, including the famous localforage.
If the lib wants to use the new kv-storage, it is not the role of the lib to include a polyfill, as it would lead to several issues:

duplicate polyfills if other libs do the same,
paths could change when the lib  is used in the final application.

You could argue that with kv-storage API, this kind of libs won't be useful anymore, but that's not true, as they also do many other things, like:

fallback to localStorage in some cases (private mode of Firefox/IE/Edge for example),
fallback to memory storage for server-side rendering,
workaround for some browsers issues (like IE/Edge not supporting indexedDB v2),
wrappring in other tools (like RxJS for mine),
etc.

So currently, to choose the best storage, runtime checks are done, like:
if (window.indexedDB) {}

I don't see anyway to do a runtime check with the current proposal.

@cyrilletuzi I've proposed a solution to the exact issue you're facing here
it's been ignored and it got 2 thumbs down
the issue goes beyond your case, as already written.
the only way to do what you need is to ignore import maps and load dependencies asynchronously through a dynamic import(...) dance that will allow fallbacks.
I know this is not the answer you were looking for, but I'm also happy you brought here your use case, and I'm pretty sure many others will follow up.
import maps right now is useless for polyfills ... apparently they don't see it, but it's already the case.

Following @WebReflection answer, I need to add that dynamic import() is not possible in all cases, as it's asynchronous, which is not possible in my case.

My thoughts on the design of a JavaScript standard library hasn't changed; it shouldn't ship in any form that doesn't allow you to polyfill a standard module without effectively changing consumer code – https://github.com/tc39/proposal-javascript-standard-library/issues/2#issuecomment-448517949
That is a consumer shouldn't have to do any weird host dependent handshake, for example:
import foo from "std:something|somethingelse"
// or
import foo from do { /* ... */}

Because as @WebReflection mentions sometimes you intentionally don't want to use the standard module if it's defective, and additionally in contrast to the goals of any standard library pollutes consumer sites with extraneous data that would almost certainly need to change when something out of the blue happens.
This is most certainly a far cry from the current status quo of a clean separation between consumers and providers where:
var map = new WeakMap

Works regardless of how the provider implements the constructor by either being builtin/polyfilled/extended/replaced.
That is any standard library if one where to exist should preserve the is global-ish but is polyfill-able/extend-able/replace-able artefact of current global JavaScript constructors.

So, looking to the stage 2 presentation slides, polyfilling issue is completely ignored, "import-maps should handle those".
TC39, please, listen to the opinions of polyfills authors! Don't break the polyfilling in JavaScript!

@mattijs re the slide content, please see https://github.com/tc39/proposal-javascript-standard-library/issues/2#issuecomment-467946979

@ljharb I read that explanation a while back, thanks for pointing it out again.
@zloirock I'll think some more on the use case you are laying out.


I have no idea to deal with this problem, ubuntu 18.04 miniconda

#0 21.73                        from /opt/conda/lib/python3.11/site-packages/torch/include/ATen/core/dispatch/Dispatcher.h:4,
#0 21.73                        from /opt/conda/lib/python3.11/site-packages/torch/include/torch/csrc/api/include/torch/types.h:12,
#0 21.73                        from /tmp/pip-install-cf1psikn/mmcv-full_3fdf057e44b7448787b24698b8e60bdf/mmcv/ops/csrc/common/pytorch_cpp_helper.hpp:3,
#0 21.73                        from ./mmcv/ops/csrc/pytorch/active_rotated_filter.cpp:5:
#0 21.73       /opt/conda/lib/python3.11/site-packages/torch/include/ATen/core/boxing/impl/make_boxed_from_unboxed_functor.h: In constructor ‘c10::impl::assert_is_valid_input_type<T, AllowDeprecatedTypes, Enable>::assert_is_valid_input_type()’:
#0 21.73       /opt/conda/lib/python3.11/site-packages/torch/include/ATen/core/boxing/impl/make_boxed_from_unboxed_functor.h:109:10: warning: ‘if constexpr’ only available with ‘-std=c++17’ or ‘-std=gnu++17’
#0 21.73         109 |       if constexpr (guts::typelist::contains<supported_primitive_arg_types, T>::value) {
#0 21.73             |          ^~~~~~~~~
#0 21.73       In file included from /opt/conda/lib/python3.11/site-packages/torch/include/ATen/core/boxing/KernelFunction_impl.h:2,
#0 21.73                        from /opt/conda/lib/python3.11/site-packages/torch/include/ATen/core/boxing/KernelFunction.h:251,
#0 21.73                        from /opt/conda/lib/python3.11/site-packages/torch/include/ATen/core/dispatch/Dispatcher.h:4,
#0 21.73                        from /opt/conda/lib/python3.11/site-packages/torch/include/torch/csrc/api/include/torch/types.h:12,
#0 21.73                        from /tmp/pip-install-cf1psikn/mmcv-full_3fdf057e44b7448787b24698b8e60bdf/mmcv/ops/csrc/common/pytorch_cpp_helper.hpp:3,
#0 21.73                        from ./mmcv/ops/csrc/pytorch/active_rotated_filter.cpp:5:
#0 21.73       /opt/conda/lib/python3.11/site-packages/torch/include/ATen/core/boxing/impl/make_boxed_from_unboxed_functor.h: In constructor ‘c10::impl::assert_is_valid_output_type<T, AllowDeprecatedTypes, Enable>::assert_is_valid_output_type()’:
#0 21.73       /opt/conda/lib/python3.11/site-packages/torch/include/ATen/core/boxing/impl/make_boxed_from_unboxed_functor.h:215:10: warning: ‘if constexpr’ only available with ‘-std=c++17’ or ‘-std=gnu++17’
#0 21.73         215 |       if constexpr(guts::typelist::contains<supported_primitive_arg_types, T>::value) {
#0 21.73             |          ^~~~~~~~~
#0 21.73       /opt/conda/lib/python3.11/site-packages/torch/include/ATen/core/boxing/impl/make_boxed_from_unboxed_functor.h: In static member function ‘static void c10::impl::make_boxed_from_unboxed_functor<KernelFunctor, AllowDeprecatedTypes>::call(c10::OperatorKernel*, const c10::OperatorHandle&, c10::DispatchKeySet, c10::Stack*)’:
#0 21.73       /opt/conda/lib/python3.11/site-packages/torch/include/ATen/core/boxing/impl/make_boxed_from_unboxed_functor.h:575:10: warning: ‘if constexpr’ only available with ‘-std=c++17’ or ‘-std=gnu++17’
#0 21.73         575 |       if constexpr (has_outputs) {
#0 21.73             |          ^~~~~~~~~
#0 21.73       In file included from /opt/conda/lib/python3.11/site-packages/torch/include/torch/csrc/api/include/torch/types.h:12,
#0 21.73                        from /tmp/pip-install-cf1psikn/mmcv-full_3fdf057e44b7448787b24698b8e60bdf/mmcv/ops/csrc/common/pytorch_cpp_helper.hpp:3,
#0 21.73                        from ./mmcv/ops/csrc/pytorch/active_rotated_filter.cpp:5:
#0 21.73       /opt/conda/lib/python3.11/site-packages/torch/include/ATen/core/dispatch/Dispatcher.h: In static member function ‘static Return c10::Dispatcher::callWithDispatchKeySlowPath(const c10::TypedOperatorHandle<Return(Args ...)>&, at::StepCallbacks&, c10::DispatchKeySet, const c10::KernelFunction&, Args ...)’:
#0 21.73       /opt/conda/lib/python3.11/site-packages/torch/include/ATen/core/dispatch/Dispatcher.h:597:6: warning: ‘if constexpr’ only available with ‘-std=c++17’ or ‘-std=gnu++17’
#0 21.73         597 |   if constexpr (num_boxed_args != 0) {
#0 21.73             |      ^~~~~~~~~
#0 21.73       error: command '/usr/bin/gcc' failed with exit code 1
#0 21.73       [end of output]
#0 21.73
#0 21.73   note: This error originates from a subprocess, and is likely not a problem with pip.
#0 21.73   ERROR: Failed building wheel for mmcv-full
#0 21.73   Running setup.py clean for mmcv-full
#0 23.75 Failed to build mmcv-full
#0 23.75 ERROR: Could not build wheels for mmcv-full, which is required to install pyproject.toml-based projects
Dockerfile:23
21 |     RUN pip install openmim
22 |     RUN pip install torch
23 | >>> RUN mim install mmcv-full==1.7.0
24 |     RUN pip install mmdet==2.27.0
25 |     RUN pip install torchserve
ERROR: failed to solve: process "/bin/sh -c mim install mmcv-full==1.7.0" did not complete successfully: exit code: 1

I think there's some incompatibility in the version of torch released last month. I got around this by making the following change:
diff --git a/torchserve/Dockerfile b/torchserve/Dockerfile
index ec7aa64..5ee973d 100644
--- a/torchserve/Dockerfile
+++ b/torchserve/Dockerfile
@@ -19,7 +19,7 @@ RUN apt-get update && \

 # install python dependencies
 RUN pip install openmim
-RUN pip install torch
+RUN pip install torch==2.0.1
 RUN mim install mmcv-full==1.7.0
 RUN pip install mmdet==2.27.0
 RUN pip install torchserve

thanks!
yesterday, I changed mmcv-full==v1.7.0 to mmcv-full==v1.3.17;   it's ok now!


PAPP-23145: policy actions add and asset configuration

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[ ] Testing of all the changes has been performed (for bug fixes / features)
[ ] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[ ] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[ ] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[ ] Verify all checks are passing.
[ ] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[ ] Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type
Please check the type of change your PR introduces:

[ ] New App
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

@pdesai-crest

Fix static test job
Fix integration test job
update unreleased.md
Update readme.html based on the changes

Remove 'None' parameter from all the methods, param.get() will by default return None in case of any failure.
mac_filter = param.get("mac_address", None)

Please use _validate_integers common methods if possible, u can take reference from bit9 app. if not then move the if condition at first place, then inside that use the try-except block

Please update the wheel files as per the latest version and directory standards

Please use _validate_integers common methods if possible, u can take reference from bit9 app. if not then move the if condition at first place, then inside that use the try-except block

@pdesai-crest please fix this logic as well.

Static tests are failing due to license issue. https://splunk.slack.com/archives/C01F1PWD3S6/p1639553681069500


Add dollar sign to cost field

Related SO question: https://stackoverflow.com/questions/2913236/html-text-input-field-with-currency-symbol
This will make it more intuitive for users that this is a cost field (and that they need not enter a dollar sign).

Relevant jsFiddle: https://jsfiddle.net/q6Lmqh8h/634/

Completed in these two commits:
5f5b6d1031a07656a6a3bbc2070aba47a91c2d7d (edit page)
a0ca8f9916c4fc570ecb0b42dce0598b71d36062 (new request page)


Add ability to move Widgets

Suggested new feature or improvement
Add ability to move Widgets so you can place them in way that fits the way you work
Scenario
Add ability to move Widgets so you can place them in way that fits the way you work
Additional details
No response

Duplicate of #673


Multi-Device Support

Overview
Users will likely access the web wallet from multiple devices. This transition should be both seamless and secure.
Stories
As a user, I want to use the NEAR wallet on multiple devices, so I can easily access NEAR applications on desktop and mobile.
As a user, I want to set limits on my transaction amounts, requiring two factor authentication above the limits, so I can use the web wallet to safely store $100-$1000 worth of assets.
Flows
Desktop to Mobile Flow

User selects “Add a new mobile device” on desktop
Signs a transaction creating a new full access key
Scans QR code with mobile device (URL w/ full access private_key)
Redirected to “New Device Confirmation” screen on mobile device
Selects “Complete Device Setup”

Send batch transaction adding new full access key and removing full access key contained in the URL

Redirected to “Profile”

Mobile to Desktop Flow

User selects “Already have an account? Add this device” on desktop
Redirected to “Add Device” page on desktop
Selects “Add this device”, QR code generated
Scans QR code on mobile device Scans QR code with mobile device (URL w/ public_key)
Confirms “Add device”, signs a transaction creating a full access key using the public_key from the QR code
Redirected to “New Device Confirmation” screen on mobile device
Selects “Complete Device Setup”

I want to also add that right now it's unclear which devices which keys are from. e.g. in the list of Full Access Keys - which one is the key in the wallet UI vs keys from somewhere else.


Ctrl-click (Go To Definition) not working

Type: Bug
Hello, Go To Definition via F12 is working fine, but via Ctrl+Click is not working. Holding Ctrl and hovering over any reference no longer underlines the reference.
Trying to get a solution to this to help improve my workflow, thanks!
VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) Ultra 9 185H (22 x 3072)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
31.45GB (17.17GB free)

Process Argv
--crash-reporter-id bd3864fb-31a5-4255-8c8b-cd06bf8360e1

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

cmake-tools
ms-
1.19.52

cpptools
ms-
1.22.11

cpptools-extension-pack
ms-
1.3.0

cmake
twx
0.0.17

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
newcmakeconfigv2:31071590
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530

what language?
code snippet and screenshot please

Hello, embedded C / C. I Just got a new laptop and installed all the same extensions (only really had the one extension pack being the cmake tools) and it has never worked on my new machine. Would really like this to work as I use VS side by side with STM32CubeIDE which is correctly using Ctrl+Click in the intended way.
Right now Ctrl+Click adds multiple cursors instead of going to definition.

Do you have editor.multiCursorModifier configured?

Yes, somehow that was changed which is odd cause this is a fresh VS Code install. Reverted back to alt (I don't ever really use Alt anyway nor multicursor) and now everything is working as intended. Thank you for the help.


AppArmor for containers

Test and create AppArmor profiles for beacon, validator, eth1. Look into same for grafana, prometheus, node_exporter, at lower priority.
It'd need to be done individually for each client and be quite a bit of work, trial-and-error to a degree.
It'd also enhance security dramatically.

I am deciding not to do this. AppArmor in docker is a bit niche and a lot of work to implement. Monitoring the k8s project instead, which should gain good security options in 2021 / H1 2022. There may be a fork of this project to be used with k8s / microk8s / k3s.


An exercise in a MSc course on AI

User Story

Short story:
As a teacher, I want to use UPF to let my students play around with different planners.

Full story:
I teach an introductory course on AI in a MSc program on computer engineering.  In one of the hands-on exercises, students have to build an integrated planning and execution system to control a simulated robot.  They are given an off-the-shelf HTN planner and a low-fidelity robot simulator.  They need to write the top-level execution loop, which interacts with the planner and with the robot simulator accordingly to the following diagram.

The robot has to transport boxes across different rooms to reach a given configuration; additional difficulties include closed doors that need to be opened, and the presence of a gremlin who occasionally displaces the boxes.
I want the students to use the UPF instead of the given planner, so they can experiment with using different planners, possibly addressing more complex tasks.
Acceptance Criteria

[ ] Using the UPF should not make the exercise more complex for the students

Additional Material

Example of top level code that the students are expected to implement. The call to "pyhop" should be replaced by a suitable call to UPF.

def top_level(robot, task, verbose=1):
    """ Top level execution loop: make a robot perform a task, replan on failures """
    state = State()
    while sense_plan_act(robot, state, task, verbose=verbose) is False:
        continue

def sense_plan_act(robot, state, task, onestep=False, verbose=1):
    """ Sense-Plan-Act loop: read the world state, generate a plan, execute it  """
    get_state(state, robot)
    plan = pyhop.pyhop(state, task, verbose)
    if plan:
        result = do_action(plan, robot)
        if result:
            print("Execution completed!")
        else:
            print("Execution failed!")
        return result
    else:
        print("No plan found!")
    return None

Attention Points

No other relevant info for now

Question: currently do the students need to write the pyhop task themselves is it given?

Students write the pyhop domain themselves, in one exercise.  Then, in a follow-up exercise  they put their planner/domain in the executor loop.
To be complete, there is also a third part where they include an ontological reasoner in the loop to do tasks like "go to the kitchen" where none of the rooms is labeled "kitchen" in the map, but we know that a kitchen must contain a stove and that there is a stove is in room-3.

@asaffio This user story should be now fully supported (I think). Feel free to reopen the issue if you think something is still missing.


[Upgrade][DO NOT update branch] Alpha TestNet v0.0.11

Summary
An upgrade for Alpha TestNet from v0.0.10 to v0.0.11.
Issue
Beta TestNet has been launched using v0.0.11 (release candidate), and we need to upgrade alpha so both networks use the same version.
Type of change
Chain upgrade.
Testing

[] An upgrade is tested by upgrading a network provisioned by the old version (v0.0.10) to the new version (v0.0.11)

Sanity Checklist

[ ] I have tested my changes using the available tooling
[ ] I have commented my code
[ ] I have performed a self-review of my own code; both comments & source code
[ ] I create and reference any new tickets, if applicable
[ ] I have left TODOs throughout the codebase, if applicable

Upgrade has been tested and validated locally:
5:39PM INF applying upgrade "v0.0.11" at height: 20 module=x/upgrade
5:39PM INF Starting v0.0.11 upgrade handler module=server
5:39PM INF Starting parameter updates for v0.0.11 module=server
5:39PM INF Current session params module=server params={"num_suppliers_per_session":0}
5:39PM INF Successfully updated session params module=server new_params={"num_suppliers_per_session":15}
5:39PM INF Current tokenomics params module=server params={"dao_reward_address":"","mint_allocation_proposer":{"application":0,"dao":0,"proposer":0,"source_owner":0,"supplier":0}}
5:39PM INF Successfully updated tokenomics params module=server new_params={"dao_reward_address":"pokt1r6ja6rz6rpae58njfrsgs5n5sp3r36r2q9j04h","mint_allocation_proposer":{"application":0,"dao":0.1,"proposer":0.05,"source_owner":0.15,"supplier":0.7}}
5:39PM INF Starting authorization updates for v0.0.11 module=server
5:39PM INF Granting authorization module=server
5:39PM INF Successfully granted authorization module=server
5:39PM INF Running module migrations module=server

This is interesting.
The diff between versions shows we need to add a new authorization, but we already have it on Alpha TestNet:
poktrolld q authz grants-by-granter pokt10d07y265gmmuvt4z0w9aw880jnsr700j8yv32t --node=https://shannon-testnet-grove-seed-rpc.alpha.poktroll.com

- authorization:
    type: cosmos-sdk/GenericAuthorization
    value:
      msg: /poktroll.session.MsgUpdateParam
  expiration: "2500-01-01T00:00:00Z"
  grantee: pokt1r6ja6rz6rpae58njfrsgs5n5sp3r36r2q9j04h
  granter: pokt10d07y265gmmuvt4z0w9aw880jnsr700j8yv32t

Tested again after authorization code removed:

5:58PM INF ABCI Handshake App Info hash=48BAFBE9874B2A7625D9834A983AB231C98523767859E5208A277F8518CF66C0 height=19 module=consensus protocol-version=0 software-version=0.0.11-rc-bc2a3c44
5:58PM INF ABCI Replay Blocks appHeight=19 module=consensus stateHeight=19 storeHeight=20
5:58PM INF Replay last block using real app module=consensus
5:58PM INF applying upgrade "v0.0.11" at height: 20 module=x/upgrade
5:58PM INF Starting v0.0.11 upgrade handler module=server
5:58PM INF Starting parameter updates for v0.0.11 module=server
5:58PM INF Current session params module=server params={"num_suppliers_per_session":0}
5:58PM INF Successfully updated session params module=server new_params={"num_suppliers_per_session":15}
5:58PM INF Current tokenomics params module=server params={"dao_reward_address":"","mint_allocation_proposer":{"application":0,"dao":0,"proposer":0,"source_owner":0,"supplier":0}}
5:58PM INF Successfully updated tokenomics params module=server new_params={"dao_reward_address":"pokt1r6ja6rz6rpae58njfrsgs5n5sp3r36r2q9j04h","mint_allocation_proposer":{"application":0,"dao":0.1,"proposer":0.05,"source_owner":0.15,"supplier":0.7}}
5:58PM INF Running module migrations module=server
5:58PM INF adding a new module: 06-solomachine module=server
5:58PM INF adding a new module: 07-tendermint module=server

I think we're good to go. I'll wait for a review, before I cut a new version.

I'm going to remove the merge from main into this branch and do a force push.
This branch is not ready for code from main yet, as I'm still figuring out what happened on Alpha TestNet.

@okdas Following up on an offline discussion.

This branch is not ready for code from main yet, as I'm still figuring out what happened on Alpha TestNet.

If you can't resolve it by mid-day today, let's do the following:

Post your latest update + investigation + details
Please move over to load-testing
@bryanchriswhite will pick it up next week
If @bryanchriswhite doesn't figure it out by mid week next week, I'll just in and help
@okdas Please be ready (aside from working on (2)) to potentially help out with some questions

Here's my investigation so far: https://www.notion.so/buildwithgrove/Alpha-TestNet-v0-0-11-Postmortem-152a36edfff680d58411c8fa384f877c?pvs=4
TLDR: KVStore had a different representation of empty params for the tokenomics module (alpha testnet vs local node), which explains the difference in behavior.
I've also included some action items for us (me mostly) to do to avoid this and issues that were uncovered during this upgrade / postmortem investigation.
@bryanchriswhite I would love you to look into this as well, and I'm happy to pair/help.

OK, and now that I sent the previous message, it struck me what exactly happened here.
Alpha TestNet was provisioned using v0.0.9, which had a different protobuf for the tokenomics module params: https://github.com/pokt-network/poktroll/blob/v0.0.9/proto/poktroll/tokenomics/params.proto#L16
And it had a value, too: https://github.com/pokt-network/pocket-network-genesis/blob/master/shannon/testnet-alpha/genesis.json#L1018
That protobuf was then removed in v0.0.10, but the bytes were still preserved in the KVStore: 082A - see them decoded here.
As I did not see any changes in the protobuf when comparing v0.0.10 to v0.0.11, I deemed it safe to read the parameters from KVstore, while it was not.
If we did not remove the parameter or used a different field ID for the new fields, this wouldn't happen.

TL;DR, we SHOULD use reserved for deleted fields AND we SHOULD be versioning our protobuf types (e.g. proto/tokenomics/v1beta1).

OK, and now that I sent the previous message, it struck me what exactly happened here.

:exploding_head: Nice sleuthing! :rocket:

If we did not remove the parameter or used a different field ID for the new fields, this wouldn't happen.

Point taken that going forward, we need to be much more careful about backwards compatibility. In this particular case, I don' think there's any way we could've avoided removing this field as it was necessary to resolve a dependency cycle. In cases like this, it seems like the correct thing to do, going forward, would be to remove the field but also add its field number (and possibly field name) as reserved.
FWIW, this case would also be a bit unusual, IMHO, to resolve with versioned types as we would end up having multiple branches in the effected module's InitGenesis function to handle the two different versions of genesis. I think this makes much less sense then the typical case, which would be where a message or query handler has conditional branches for each version. "Genesis backwards-compatibility" seems like a bit of an oxymoron. :joy:
This (re-)raises the point of versoined protobuf source, which we currently are not setup for, neither from a go package nor a proto source package persective. I think we will need to do something like the following in order to pre-allocate sufficient degrees of freedom to ensure we can safely increment the protobuf types into the future, without causing caos from both the go module/pkg and buf.build perspectives:
Current proto directory structure:
./proto
└── poktroll
    ├── application
    │   └── *.proto
    │   └── *.proto
    ├── gateway
    │   └── *.proto
    ├── proof
    │   └── *.proto
    ├── service
    │   └── *.proto
    ├── session
    │   └── *.proto
    ├── shared
    │   └── *.proto
    ├── supplier
    │   └── *.proto
    └── tokenomics
    │   └── *.proto

Conventional (versioned):
./proto
└── poktroll
    ├── application
    │   └── v1beta1
    │       └── *.proto
    ├── gateway
    │   └── v1beta1
    │       └── *.proto
    ├── proof
    │   └── v1beta1
    │       └── *.proto
    ├── service
    │   └── v1beta1
    │       └── *.proto
    ├── session
    │   └── v1beta1
    │       └── *.proto
    ├── shared
    │   └── v1beta1
    │       └── *.proto
    ├── supplier
    │   └── v1beta1
    │       └── *.proto
    └── tokenomics
        └── v1beta1
            └── *.proto

Firstly, great investigation @okdas!
@bryanchriswhite I want to avoid the module/v1beta1/*.proto refactor just now.
Let's continue with:

Only incrementing IDs
Using reserved fields for deprecated fields

Things we'll look out for:

How do other cosmos chains do this?
When (if) we hit major proto refactors, we'll revisit package versioning


92 constand nd timeseries

current tests should pass but we can add some specific tests for this (after refactoring)
closes #92

Hello @CagtayFabry! Thanks for opening this PR.

In the file tests/asdf_tests/test_asdf_core.py:

Line 49:9: F841 local variable 'rot' is assigned to but never used

In the file weldx/asdf/tags/weldx/core/transformations/rotation.py:

Line 72:39: F541 f-string is missing placeholders

Do see the Hitchhiker's guide to code style


I upload a few car images in my repo.

I upload a few car images in my repo.

Thank you for your contributions @NandhiniPython


Enhancement: more logging in E2E tests

Summary
Original explanation:

Pass the nightly tests by updating imported type.EvalDelta from go-algorand-sdk and updating conduit dependency.

This no longer applies, as tests are passing because the conduit dependency has been updated.
Additional changes:

update pinned AWS E2E key to latest available
add env printout and other breadcrumbs in e2e Dockerfiles
refactor python scripts to make them a little easier to work with/debug

Issue
#1521
Related PR's

go-algorand-sdk PR: https://github.com/algorand/go-algorand-sdk/pull/531
conduit PR: https://github.com/algorand/conduit/pull/73
go-algorand PR: https://github.com/algorand/go-algorand/pull/5381 for cross-repo type checking

Looks mostly good once we resolve some of the outstanding todos.

I believe I've resolved these TODO's except for the long-standing issue that we discussed above.


use websocket  garbage collection(Unhandled exception:)or vm errors

When I at the beginning of the application is started and a websocket connection and send the data for the first time the flutter  run can appear the following error console, it is strange that the next to repackage this problem will not appear again
Unhandled exception:
Exception: Error connecting to observatory: WebSocketChannelException: WebSocketChannelException: HttpException: Connection closed before full header was received, uri = http://<IP_ADDRESS>:8100/ws
#0      throwToolExit (package:flutter_tools/src/base/common.dart:29)
#1      VM.invokeRpcRaw (package:flutter_tools/src/vmservice.dart:653)

#2      VM._fetchDirect (package:flutter_tools/src/vmservice.dart:496)

#3      ServiceObject.reload (package:flutter_tools/src/vmservice.dart:344)

#4      VMService.getVM (package:flutter_tools/src/vmservice.dart:172)
#5      ResidentRunner.connectToServiceProtocol (package:flutter_tools/src/resident_runner.dart:218)

#6      HotRunner.attach (package:flutter_tools/src/run_hot.dart:97)

#7      HotRunner.run (package:flutter_tools/src/run_hot.dart:222)

#8      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:281)

#9      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:151)

#10     RunCommand.verifyThenRunCommand (package:flutter_tools/src/commands/run.dart:196)

#11     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:121)
#12     CommandRunner.runCommand (package:args/command_runner.dart:194)

#13     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:262)

#14     CommandRunner.run. (package:args/command_runner.dart:109)
#15     Future.Future.sync (dart:async/future.dart:208)
#16     CommandRunner.run (package:args/command_runner.dart:109)
#17     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:157)
#18     run. (package:flutter_tools/executable.dart:140)

#19     AppContext._run (package:flutter_tools/src/base/context.dart:76)

#20     AppContext.runInZone. (package:flutter_tools/src/base/context.dart:66)
#21     _rootRun (dart:async/zone.dart:1120)
#22     _CustomZone.run (dart:async/zone.dart:1001)
#23     runZoned (dart:async/zone.dart:1465)
#24     AppContext.runInZone (package:flutter_tools/src/base/context.dart:65)
#25     run (package:flutter_tools/executable.dart:113)

#26     main (package:flutter_tools/executable.dart:66)

#27     main (file:///Users/pengyun/flutter/packages/flutter_tools/bin/flutter_tools.dart:8)
#28     _startIsolate. (dart:isolate-patch/isolate_patch.dart:263)
#29     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:151)

Some sort of hot-reload error?  @a-siva @tvolkert

@jsonpeng can you provide us some instructions on how to reproduce this error.

haven't received any instructions on how to reproduce the error, assuming not an issue anymore and closing the issue. Please feel free to reopen the issue if that is not the case and instructions for reproducing the bug is available.


How many kinds of Ethereum smart contract problems can be detected by OCTOPUS？

Hello, I am a postgraduate from Hohai University. Because I'm investigating related fields, I would like to know how many kinds of Etehereum smart contract problems OCTOPUS can detect. I haven't found relevant description documents or papers. If they exist, please tell me that I will read the relevant documents. I'm sorry to disturb your life and look forward to your reply.

Hi,
If you want to detect vulnerabilities with octopus you need to create your detection rules matching the SSA representation. I'm not working on this subject at the time so you should take a look to other project like slither.


nuget.exe failed

CMake Error at flutter/ephemeral/.plugin_symlinks/video_player_win/windows/CMakeLists.txt:35 (message):
Integrity check for
D:/workspace/app/build/windows/x64/nuget.exe failed

I tried to clean build this package and it works well today.
Could you run flutter clean first, and build again?
If it is still failed, please let me know which version of video_player_win you are using.

video_player_win version is 2.3.4  and flutter doctor is

I had tried, still fails

Please  open browser and download https://dist.nuget.org/win-x86-commandline/v5.10.0/nuget.exe.
Open console, cd to download path, and run certutil -hashfile nuget.exe sha256
If the result of sha256 string not equal to 852b71cc8c8c2d40d09ea49d321ff56fd2397b9d6ea9f96e532530307bbbafd3
then there maybe something wrong with your ISP.
E:\Downloads> certutil -hashfile nuget.exe sha256
SHA256 的 nuget.exe 雜湊:
852b71cc8c8c2d40d09ea49d321ff56fd2397b9d6ea9f96e532530307bbbafd3
CertUtil: -hashfile 命令成功完成。

Thank you, I guess is proxy,  I try to use global vpn and it work


using seek_to with specify timestamp in external stream  cann't work

-- redpanda
-- rpk topic create test -p 3

-- proton1
drop stream if exists test_external1;
create external stream if not exists test_external1(id int, value string) settings type = 'kafka', brokers = 'redpanda-1:9092', topic = 'test', data_format='JSONEachRow';

-- redpanda
-- rpk topic produce test
{"id":1,"value":"sometext"}
Produced to partition 0 at offset 2 with timestamp<PHONE_NUMBER>271.
{"id":2,"value":"aaaaa"}
Produced to partition 2 at offset 1 with timestamp<PHONE_NUMBER>170.
{"id":3,"value":"bbbbb"}
Produced to partition 1 at offset 1 with timestamp<PHONE_NUMBER>566.
{"id":4,"value":"ccccc"}
Produced to partition 2 at offset 2 with timestamp<PHONE_NUMBER>830.
-- proton
select * from test_external1 settings seek_to='2023-11-11 14:15:24.219';

Kafka and alike don't have good support for seeking for a specific timestamp. I don't think we should support this in external streams. Please let me know if you think differently @chenziliang @jovezhong

Kafka can seek via timestamp. The timestamp can be server side append time by default or application assigned time if I recalled it correctly. But in general m, they could be different than _tp_time (event time)

I think you mean  rd_kafka_offsets_for_times()? My understanding is that it uses messages' timestamps, which could be event time or ingest time. So do we want seek_to works in that way? If so, I have a follow up question, should we generate the _tp_time field for each kafka message using the message's timestamp too? I think that's reasonable if we allow using seek_to with timestamps.

https://cwiki.apache.org/confluence/display/KAFKA/KIP-32+-+Add+timestamps+to+Kafka+message and https://github.com/timeplus-io/proton/blob/develop/src/KafkaLog/KafkaWALCommon.cpp#L234-L277

That was what i read quite a long time back.

If we like to support seek_to for external stream, this is the best thing we can do since we don't control the timestamp, end users do. We just need document what it means.
I would suggest deferring this feature a bit since no customer requirements so far.

seek_to='earliest' looks good but specifying a timestamp does not work, @lizhou1111 , please add your verification result here.

Duplicates #345


 We keep getting issues almost every day of bug reports when a person just copy-paste the error from your app that says to report to isomorphic-git. Often they don't provide any context.
This is a continuation of https://github.com/forcedotcom/cli/issues/2194 people keep reporting errors about your extension to our project.

I don't use salesforce CLI. But here is the copy-pasted info from other issue:
{
  "cliVersion"<EMAIL_ADDRESS>  "architecture": "linux-x64",
  "nodeVersion": "node-v18.17.0",
  "osVersion": "Linux 5.15.0-1042-azure",
  "shell": "bash",
  "rootPath": "/usr/local/lib/node_modules/@salesforce/cli",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 2.3.6 (core)",
    "@oclif/plugin-commands 2.2.21 (core)",
    "@oclif/plugin-help 5.2.[16](https://github.com/jdschleicher/sf-sfdx-cli-version-troubleshooting/actions/runs/5893258460/job/15987028213#step:3:17) (core)",
    "@oclif/plugin-not-found 2.3.36 (core)",
    "@oclif/plugin-plugins 3.2.0 (core)",
    "@oclif/plugin-search 0.0.22 (core)",
    "@oclif/plugin-update 3.1.30 (core)",
    "@oclif/plugin-version 1.3.8 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.46 (core)",
    "@oclif/plugin-which 2.2.29 (core)",
    "@salesforce/cli 2.4.10 (core)",
    "apex 2.3.10 (core)",
    "auth 2.8.12 (core)",
    "data 2.5.5 (core)",
    "deploy-retrieve 1.[17](https://github.com/jdschleicher/sf-sfdx-cli-version-troubleshooting/actions/runs/5893258460/job/15987028213#step:3:18).2 (core)",
    "info 2.6.38 (core)",
    "limits 2.3.29 (core)",
    "login 1.2.25 (core)",
    "org 2.9.30 (core)",
    "schema 2.3.[22](https://github.com/jdschleicher/sf-sfdx-cli-version-troubleshooting/actions/runs/5893258460/job/15987028213#step:3:23) (core)",
    "settings 1.4.[24](https://github.com/jdschleicher/sf-sfdx-cli-version-troubleshooting/actions/runs/5893258460/job/15987028213#step:3:25) (core)",
    "sobject 0.2.2 (core)",
    "source 2.10.30 (core)",
    "telemetry 2.2.5 (core)",
    "templates 55.5.9 (core)",
    "trust 2.5.4 (core)",
    "user 2.3.[28](https://github.com/jdschleicher/sf-sfdx-cli-version-troubleshooting/actions/runs/5893258460/job/15987028213#step:3:29) (core)"
  ]

oof, sorry for all the trouble @jcubic.
I logged a WI for us to work on this.
There may still be people that don't upgrade after we fix this so I turned on notifications on isomorphic-git repo for new issues try to catch them and redirect to us.

Thanks, I hope this is exact same issue that was already solved.

@cristiand391 I don't think its due to outdated installations. I am running most recent sf version and also get the error.
$ sf project deploy start --ignore-conflicts
Error (1): An internal error caused this command to fail. Please file a bug report at https://github.com/isomorphic-git/isomorphic-git/issues with this error message: Invalid checksum in GitIndex buffer: expected  but saw da39a3ee5e6b4b0d3255bfef95601890afd80709

$ sf version --verbose --json
{
  "cliVersion"<EMAIL_ADDRESS>  "architecture": "linux-x64",
  "nodeVersion": "node-v18.17.0",
  "osVersion": "Linux 6.2.0-26-generic",
  "shell": "bash",
  "rootPath": "/home/fmann/.nvm/versions/node/v18.17.0/lib/node_modules/@salesforce/cli",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 2.3.6 (core)",
    "@oclif/plugin-commands 2.2.21 (core)",
    "@oclif/plugin-help 5.2.16 (core)",
    "@oclif/plugin-not-found 2.3.36 (core)",
    "@oclif/plugin-plugins 3.2.0 (core)",
    "@oclif/plugin-search 0.0.22 (core)",
    "@oclif/plugin-update 3.1.30 (core)",
    "@oclif/plugin-version 1.3.8 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.46 (core)",
    "@oclif/plugin-which 2.2.29 (core)",
    "@salesforce/cli 2.4.10 (core)",
    "apex 2.3.10 (core)",
    "auth 2.8.12 (core)",
    "data 2.5.5 (core)",
    "deploy-retrieve 1.17.2 (core)",
    "dev 1.1.3 (user)",
    "info 2.6.38 (core)",
    "limits 2.3.29 (core)",
    "login 1.2.25 (core)",
    "org 2.9.30 (core)",
    "schema 2.3.22 (core)",
    "settings 1.4.24 (core)",
    "sobject 0.2.2 (core)",
    "source 2.10.30 (core)",
    "telemetry 2.2.5 (core)",
    "templates 55.5.9 (core)",
    "trust 2.5.4 (core)",
    "user 2.3.28 (core)",
    "sfdx-git-delta 5.24.0 (user)"
  ]
}

My Salesforce VS Addons also recently updated and no longer trigger deprecated warnings of using ´sfdx force source *´, not sure if this may be related.

@cristiand391 Is there a work arround for this issue? currently using latest version of cli, and this is preventing me from doing any work. All deployments to my sandbox fail with this exact error.
{
  "cliVersion"<EMAIL_ADDRESS>  "architecture": "win32-x64",
  "nodeVersion": "node-v18.16.0",
  "osVersion": "Windows_NT 10.0.19045",
  "shell": "cmd.exe",
  "rootPath": "C:\\Users\\StephaniePoorman\\AppData\\Roaming\\npm\\node_modules\\@salesforce\\cli",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 2.3.6 (core)",
    "@oclif/plugin-commands 2.2.21 (core)",
    "@oclif/plugin-help 5.2.16 (core)",
    "@oclif/plugin-not-found 2.3.36 (core)",
    "@oclif/plugin-plugins 3.2.0 (core)",
    "@oclif/plugin-search 0.0.22 (core)",
    "@oclif/plugin-update 3.1.30 (core)",
    "@oclif/plugin-version 1.3.8 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.46 (core)",
    "@oclif/plugin-which 2.2.29 (core)",
    "@salesforce/cli 2.4.10 (core)",
    "apex 2.3.10 (core)",
    "auth 2.8.12 (core)",
    "data 2.5.5 (core)",
    "deploy-retrieve 1.17.2 (core)",
    "info 2.6.38 (core)",
    "limits 2.3.29 (core)",
    "login 1.2.25 (core)",
    "org 2.9.30 (core)",
    "schema 2.3.22 (core)",
    "settings 1.4.24 (core)",
    "sobject 0.2.2 (core)",
    "source 2.10.30 (core)",
    "telemetry 2.2.5 (core)",
    "templates 55.5.9 (core)",
    "trust 2.5.4 (core)",
    "user 2.3.28 (core)"
  ]
}

@poormansaj the classic force source * commands still work. So if you don't depend on sourcetracking, you can fallback to them (docu).

@poormansaj as a workaround you can run:
rm .git/index                                                                                ─╯
git reset

do you have staged files in your repo when you see this issue?

@jayree Thanks, that's helpful to know should this happen again.  I was not checking to see what was staged and not at the time, but I did test today.  The issue seems to be resolved, however, regardless of whether I have unstaged changes, staged changes, or unsynced commits.

Any news on this issue? The issue still persists in @salesforce/cli/2.7.11 linux-x64 node-v18.17.0. I reset my sfdx folder and made a fresh clone of the remote. After couple of project deploy/retrieve the issue came back again. So I need to fallback to force source deploy/retrieve.

We believe that this issue has been resolved. Please make sure you are using the latest version of sf (currently 2.11.8) and the latest version of the Salesforce VSCode extension. If you are still having issues, please open a new issue.


Installation error

Hi,I have successfully installed, but use the command: label studio
The following error occurred:

Please use virtual environments like venv or conda.
https://docs.python.org/3/library/venv.html


This message event did not happen in a guild on MessageReceivedEvent

General Troubleshooting

[x] I have checked for similar issues.
[x] I have updated to the latest JDA version.
[x] I have checked the branches or the maintainers' PRs for upcoming bug fixes.

Bug Report
 getting error when I call `event#getGuild()` on MessageReceivedEvent
Expected Behavior
 it should get where the message comes from because the event have `event#getTextChannel()` also so it should be guild info also
Code Example or Reproduction Steps
 N/A
Code for JDABuilder or DefaultShardManagerBuilder Used
 N/A
Exception or Error
 IllegalStateException : This message event did not happen in a guild

Please include the entire exception, including the stacktrace. Just the first line is not enough for a bug report. What is the version shown by JDAInfo.VERSION?

Please include the entire exception, including the stacktrace. Just the first line is not enough for a bug report. What is the version shown by JDAInfo.VERSION?

oh yeah sorry, I forget to put this, I use the last version 5.0.0 alpha, also this is the entire exception its including in this picture https://prnt.sc/22ddnuw

This has already been fixed in 5.0.0-alpha.2
Duplicate of #1926

This has already been fixed in 5.0.0-alpha.2
Duplicate of #1926

it's still... i use 5.0.0-alpha.2 version

This has already been fixed in 5.0.0-alpha.2
Duplicate of #1926

bro answer.........


Update MD file on new branch 2017-21-14_13-11-22

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


PSR-7 Compatibility?

Looks like this library comes with it's own implementation of HTTP messages, almost identical to those defined in PSR-7 standard, but not compatible on interface level. I can see that:

UriInterface can be used directly
RequestInterface and ResponseInterface are almost compatible
streams are different, as they need to support async operations

I think it is worth to build building some kind of bridge between this implementations, for the sake of compatibility. It won't be very elegant if you think about good OOP practices, but it's going to be very pragmatic - say someone develops PSR-7 library for detecting mobile devices using headers, it could be used directly from within icicle/http app.
This "bridge" can be implemented in many different ways. As an example, Request class could have following methods:
public function getBody()
{
    throw new RuntimeException("Synchronous stream is not supported");
}

public function getAsyncBody() // ...or whatever name would be better
{
    return $this->stream;
}

You get incompatible getBody(), but everything else (headers, uri) can be used as always.
What do you think? I could create a PR with example bridge implementation.

I really like the idea of having a PSR-7 adaptor available, but I'm not sure it should be included in this package. If the user only writes asynchronous code, then there would be no reason to have the adaptor available or have a dependency on psr/http-message. It is incredibly easy to block a script if one starts using code that was written to be synchronous, so I want to make it more obvious to the user what the consequences of using such code could have. However, having it in as a separate package that is linked from this package's documentation sounds like a fantastic idea.
I could set up a separate repo for the adaptor and push a basic project skeleton. You could do a PR against that, does that sound reasonable?
Here's some of what I had in mind to get you started:
use Icicle\Http\Message\MessageInterface

class SynchronousMessage implements Psr\Http\Message\MessageInterface
{
    private $message;

    private $body;

    public function __construct(MessageInterface $message)
    {
        $this->message = $message;
        $this->body = new SynchronousStream($message->getBody());
    }

    // Other PSR-7 MessageInterface methods...

    public function getBody()
    {
        return $this->body;
    }

    public function getAsyncMessage() // Or some other name
    {
        return $this->message;
    }
}

use Icicle\Loop;
use Icicle\Stream\ReadableStreamInterface

class SynchronousStream implements Psr\Http\Message\StreamInterface
{
    private $stream;

    public function __construct(ReadableStreamInterface $stream)
    {
        $this->stream = $stream;
    }

    public function read($length)
    {
        $promise = $this->stream->read($length);

        // Blocks until promise is resolved.
        while ($promise->isPending()) {
            Loop\tick(true);
        }

        $result = $promise->getResult();

        if ($promise->isRejected()) {
            throw $result;
        }

        return $result;
    }

    // Similar methods for write and seek.

    // Other PSR-7 StreamInterface methods...

    public function getAsyncStream() // Or some other name
    {
        return $this->stream;
    }
}

Interesting approach. Sure, prepare a skeleton and I will send a PR.
Still thinking, is dependency to psr7 that bad? You could at least reuse URI interface, as it is exactly the same as in PSR7 implementations.

I avoided a dependency on psr/http-message because I didn't want to confuse users, thinking that the library was completely PSR-7 compatible, but I also wanted the interface to be familiar so I went with a similar interface. Note that there are some differences in thrown exceptions, since I think throwing InvalidArgumentException for everything is rather silly, especially when the library has to actually build HTTP messages, not just import arrays from the SAPI.
Additionally, I intend to release v1 and v2 of Icicle (and all components for Icicle) simultaneously with v1 for PHP 5.5+ and v2 for PHP 7. The PHP 7 version will have type hints on methods and massive performance improvements. Assuming I did this to all the HTTP message interfaces, UriInterface would not be compatible with the PSR-7 interface.
I created a new repo and committed a project skeleton and a little bit of code based on what's above at https://github.com/icicleio/Psr7Adaptor. Write any adaptor classes you think would be useful. Message, Request, Response, and Uri will all need to be wrapped. Also, something to convert PSR-7 messages back to Icicle messages would make sense, but an async stream would have to be provided with the message.
Feel free to send me an email, DM me on twitter, or we could talk on gitter.im.

I still think that sharing code with PSR-7 implementation is not bad - they are focused on processing HTTP messages which are almost the same here, they solve common problems like security (see (here)[https://github.com/zendframework/zend-diactoros/blob/master/src/HeaderSecurity.php] and (here)[http://framework.zend.com/security/advisory/ZF2015-04]). I feel that if someone is able to use your library, he will also read the manual and understand that it is different :)
Anyway, it's your call :-)
Before I go into coding, could you rename this package to something like psr7-bridge? "Bridge" is common term for package connecting two others, while adapter (btw, usually spelled with "e", at least in most what I've seen in PHP: ZF, Symfony...)  is usually reserved for something that can be plugged in and replaced (see Auth adapters in ZF2: https://github.com/zendframework/zend-authentication/tree/master/src/Adapter)

I've contributed to the zend-diatoros project before and probably will contribute again. :)
Most of what the linked class does is taken care of by this line: https://github.com/icicleio/Http/blob/master/src/Message/Message.php#L326 However, I will definitely take another look to make sure I've covered that vulnerability.
I very much agree with the name change, bridge is a much better term, and doesn't have the spelling ambiguity problem. Already done: https://github.com/icicleio/Psr7Bridge. I might change React Adaptor to React Bridge as well.

Understood :)
BTW, you can use regex from my latest patch to zend-diactoros - it works faster than their current implementation:
// validate
if (preg_match('/[^\x09\x0a\x0d\x20-\x7E\x80-\xFE]/', $value)) {
    return false;
}

Closing this issue, to be followed up in new repo.

Hm.  Thanks to @mtymek for pointing me here.  I have to disagree with twowski, though.  Having an interface that looks and acts almost like PSR-7, but isn't, is more confusing that just being totally different.
I don't follow why the streams area an issue.  As for PHP 7 and scalar typing, I am all for adding that in time but that is best done PHP-globally.  I specifically pushed for PSR-7 to have single, predictable return types specifically to make a PHP 7 version of it in the future easier.  If anything, I'd petition FIG to start releasing PHP 7-ified versions of its interfaces for those who want the extra pedantry (including me).
I think the current approach actually makes it more confusing, not less.

I went with a PSR-7-like interface because I thought it would be familiar to users and immutability seemed like a good idea.
Streams are an issue because in asynchronous code you cannot call StreamInterface::read() and block while waiting for a string. Streams could be made non-blocking (immediately returning an empty string if no data is available), but that's not enough: the stream object needs some method to poll for available data. I could extend the PSR-7 stream interface with a method for polling, but then you'd be required to use only streams of that interface in async code, defeating the whole point (interoperability).
I'm open to suggestions on how to make the interfaces different to avoid confusion, however, the interfaces of PSR-7 in general make a lot of sense. This package might benefit from mutable messages, simply because message objects are built in parts, requiring many clones before producing the final object to be sent to the client or server.
Adding types in PHP 7 is a minor nicety of having interfaces specific to this package and was not a major contributing factor in the decision. I too would like to see PHP 7 versions of the FIG interfaces with all the necessary types added to prototypes.


createMutable getters do not work if they're on the prototype

Describe the bug
I tried to do the following:
import { render } from "solid-js/web";
import { createEffect } from "solid-js";
import { createMutable } from "solid-js/store";

function Test() {
  const m = createMutable({
    a: 1,
    get b() { return this.a * 4; }
  });

  console.log(">>>", m.a, m.b);
  m.a++;

  createEffect(() => {
    console.log(">>>", m.a, m.b);
  });

  return (
    <button type="button" onClick={() => m.a++}>
      {m.a} - {m.b}
    </button>
  );
}

render(Test, document.getElementById("app")!);

This worked as espected, the "b" getter updated without problems every time "a" had changed
import { render } from "solid-js/web";
import { createEffect } from "solid-js";
import { createMutable } from "solid-js/store";

class A {
  a = 1
  get b() { return this.a * 4; }
}

function Test() {
  const m = createMutable(new A());

  console.log(">>>", m.a, m.b);
  m.a++;

  createEffect(() => {
    console.log(">>>", m.a, m.b);
  });

  return (
    <button type="button" onClick={() => m.a++}>
      {m.a} - {m.b}
    </button>
  );
}

render(Test, document.getElementById("app")!);

But then I tried putting the "b" getter on a class and not only the reactivity stopped, but the getter stopped working completely giving only its first value and ignoring the changes to "a"
(This bug is perfectly reproducible on the playground but NOT only there)
Your Example Website or App
The solid playground is ok
Steps to Reproduce the Bug or Issue
Just run the code and click the button, you will notice something is off
Expected behavior
The output of the first example
Screenshots or Videos
No response
Platform

OS: Windows
Browser: Opera
Version: 98 I think

Additional context
No response

Interesting.. technically we don't wrap classes and only wrap own properties to prevent infinite proxy recursion loops into built-ins. This is interesting though. It definitely isn't what I was thinking when adding this feature but it is probably worth looking at whether this is feasible to support without causing too many issues with edge cases.

In wrap funtion, for class component, Object.getOwnPropertyDescriptors doesn't return the getter and setter. I create a MR to fix it.


MAINT: Add validation for schedule_function params

Return a TypeError if we passes a date_rule for a time_rule and
vice-versa

Coverage increased (+0.07%) to 81.539% when pulling cf456cdb64e74c3baa499cd613bbbc519da0588c on schedule_func_type_error into 402fb2aa999c7a89230930b7ba204b4842d4e303 on master.

I think a much more simple change that could be made here would be to have the default time_rule for schedule_function be Always(). In the old implementation, market_open(1) was "is the current time at least 1 minute after the market has opened" which was just always true. Making this change will preserve the old behavior.

I thought schedule_function was designed so that the function runs at most once a day. By have a time_rule of Always(), this is no longer the case

It will still be the case because we construct the actual rule that gets registered as OncePerDay(date_rule & time_rule)

so are you saying we should be supporting a schedule function where the user is trying to use two time rules as in "when the time is exactly 3 hours after the market opens and exactly 1 minute after the market opens"?

No, we cannot support that because we have changed rules to be exactly equal and not greater than or equal, which is more correct with the new scheduling stuff in zipline. The only reason that is the rule that is generated is that the default for time rule is market_open(minutes=1). If we make that Always then the rule would be: " hours after the market open and always" which reduces to "3 hours after the market open"

are you talking about a case where is the user is trying to do schedule_function(func, time_rules.market_open(hours=3))? I would argue that this is not even valid, since you're putting a time_rule where a date_rule should be

My point is that there is no actual difference between a time and date rule, the names are picked to reflect a common use case. Notice that many rules have meaning in both contexts.

unassigning myself here, @lianga888 and @llllllllll can figure out what needs to be done.

closing in favor on https://github.com/quantopian/zipline/pull/1221


Razorpay payment gateway integration request

Razorpay integration would be helpful for indian customers to payout easily. Kindly add if possible.

Hi @sunmughan, thank you for your feature request, we always try to integrate functions that can be useful for many users. Unfortunately Razorpay is mainly known in India, therefore the target audience for this integration is too small.
However it is still possible to integrate this payment option.

a package for Razorpay is already provided by a community member https://github.com/ramlashkar/BagistoRazorpay s.
You can check this post on our Forum if you want to integrate it yourself.


Segmentation fault trying to build the builtin package on Ubuntu 16.10

I just tried to install ponyc on a DigitalOcean server running Ubuntu 16.10 x64 for testing. I installed LLVM 3.9 and all the packages (pony version 0.14.0-3301.681301f) via apt. ponyc starts up but immediately terminates with a segfault, even when just building the HelloWorld example.
root@ubuntu-512mb-lon1-01:~/example# ponyc
Building builtin -> /usr/lib/pony/0.14.0-3301.681301f/packages/builtin
Segmentation fault (core dumped)

@gfmio can you run that under lldb/gdb and provide a backtrace?
ideally build ponyc using "make install config=debug"
then run ponyc under either lldb or gdb so you can get a complete backtrace. that would help quite a bit. if you are unsure how to get a backtrace, see:
https://www.ponylang.org/reference/pony-lldb-cheatsheet/

this seems to be the same error, i experienced in #1939 : https://gist.github.com/mfelsche/1e7cc1974054843295675f912b6d5591

Yup, I basically installed the same packages as @mfelsche did. Running lldb gives me:
Current executable set to 'ponyc' (x86_64).
(lldb) run
Process 10377 launched: '/usr/bin/ponyc' (x86_64)
Building builtin -> /usr/lib/pony/0.14.0-3301.681301f/packages/builtin
Process 10377 stopped
* thread #1: tid = 10377, 0x0000000700000002, name = 'ponyc', stop reason = signal SIGSEGV: invalid address (fault address: 0x700000002)
    frame #0: 0x0000000700000002
error: memory read failed for 0x700000000

I'll uninstall pony and build it from source now.

Yes when building from source, you need to compile with --pic
./build/release/ponyc --pic examples/helloworld

can you build that and see what you get in a backtrace?

Ah, sorry. It doesn't crash anymore now. So probably the issue just seems to be with the pony package in apt?

@gfmio that's interesting and good to know. can you run the version from the pony package in apt under the debugger and send a backtrace?
Thanks for your help and sorry you are experiencing problems.

Weird, somehow the reply I posted yesterday didn't actually get posted. No worries, I really like Pony, so I'm happy to help (in whatever limited capacity).
Sure, no worries. I really like Pony, so I'm happy to help (and I want to work for my own purposes anyway).
On both Ubuntu 16.10 and Ubuntu 17.04, the package in apt is ponyc (0.14.0-3301.681301f) and on both systems I get the following output from lldb:
root@ubuntu-512mb-lon1-01:~/helloworld# lldb -- ponyc
(lldb) target create "ponyc"
Current executable set to 'ponyc' (x86_64).
(lldb) run
Process 10400 launched: '/usr/bin/ponyc' (x86_64)
Building builtin -> /usr/lib/pony/0.14.0-3301.681301f/packages/builtin
Process 10400 stopped
* thread #1, name = 'ponyc', stop reason = signal SIGSEGV: invalid address (fault address: 0x700000002)
    frame #0: 0x0000000700000002
error: memory read failed for 0x700000000

Also, on a slightly different issue: For issues with the webserver package, shall I file an issue in this repo or is there a different repo for that?

In theory this should be fixed when #1976 is done

@gfmio can you verify this issue was fixed for you?

Assuming this was fixed and closing.

Hi, sorry, I forgot to check. Yes, the issue is resolved. Thanks!


Specify default GitHub URL variable

Updated Terraform Modules as well to separate SPs and directories to prevent conflict in single workspace:

https://github.com/databricks/terraform-databricks-mlops-aws-project
https://github.com/databricks/terraform-databricks-mlops-azure-project-with-sp-creation
https://github.com/databricks/terraform-databricks-mlops-azure-project-with-sp-linking

Tested via https://github.com/databricks/single-workspace

Could you add the jira issue number?

Could you add the jira issue number?

I thought we only did this in universe since this is a public repo and we don't expose JIRA numbers in public repos (e.g. mlflow)?

@arpitjasa-db  WOW I need to come back and modify all my PR title.
I thought it's nice to have the ticket link to PR automatically.

@arpitjasa-db WOW I need to come back and modify all my PR title. I thought it's nice to have the ticket link to PR automatically.

Yeah haha I totally understand


need to update tomal file

tomal file consists of deprecated dependencies

wrong added here raising pull request

closed for reversising issue on pull request