Improve resilience on cilium operator while Gateway API CRDs are not available

Add a controller that runs in a loop until the CRDs are installed before initializing gateway API controllers.
If the CRDs are not installed at helm installation time, fatal w/ a helpful message that points out to our documentation on how to install them.

Follow up of https://github.com/cilium/cilium/pull/28982

I think that in the ideal state, we would have a watcher running all the time that would start the Gateway controllers or restart the operator if the Gateway CRD install state changes (whether that be installing or uninstalling the Gateway API objects).

We made experimental CRDs optional in #34212


Provide env var to overwrite user agent

Hi,
This PR adds the CORSANYWHERE_USERAGENT env var to overwrite user agent.

Coverage remained the same at 100.0% when pulling 2abaa78335aaa5dbfa8a793122f32e2532f7e743 on dsavenko:master into 4814647a9d21f14858da282387a4295c17f2851d on Rob--W:master.

Why?
Note that the standard allows clients to already change the User-Agent header via XHR/fetch. Firefox has already been updated to match the spec; Chrome is lagging behind: https://bugs.chromium.org/p/chromium/issues/detail?id=571722

Well, Chrome is the main reason. The bug is there since 2015 and has the lowest priority. I don't think they're going to fix it soon.

Why?

I mean, why do you want to override the user agent from CORS Anywhere? This seems like quite specific functionality that is not generally useful to most users.

I've got a website, which redirects to mobile version based on User-Agent. Since I'm accessing it via fetch from the client side, I always get the mobile version instead of the desktop on, which is not what I want.
Afaik, it's a frequent trick to redirect to mobile version based on User-Agent. So, may be I'm not alone in this trouble.
P.S. If you want more details, I'm not trying to do anything shady. I'm developing an online RSS reader, and that website also redirects its RSS link to the mobile version, but their mobile version doesn't have that RSS resource (i.e. I get HTTP 404 after the redirect). Clearly, this is a misconfiguration on their side. I contacted them, but they refused to fix it, because 'users should use special applications to access RSS, not the browser' (their answer).


It's 2024

Update copyright year
Changes

Update 'MIT-LICENSE.txt' year.

Context

Thanks, @adsingh14! Looks like that's the only spot that needs updating. Happy New Year! 🎊

Thanks, @adsingh14! Looks like that's the only spot that needs updating. Happy New Year! 🎊


Should typespec::vpiParent ever be non-null??

typespec (and subclasses) can generally be shared across various variable declarations. Considering that fact, should typespec::vpiParent ever be non-nullptr??
At the moment, there are number of cases where typespec parent is being set to something legal. Just wondering if I am missing something obvious. If not, I can fix these as I find them.

typespec::vpiParent should always contain something. If you find nullptr, we should put the correct parent.

Hmm this is contradicting my statement. For non-elaborated model, typespec::vpiParent would be either be package or module depending on where its declared. But for elaborated model, however, the same typespc could be used by two different modules or in different context within the same module. Wouldn't the vpiParent pointer be ambiguous for elaborated models?
I see that logic_typespec are unique in the hierarchy (possibly because of the range that they hold which could be different for each use case) but other subclasses of typespec aren't unique. They are shared across uses.
This issue leans back into the other issue #2669. If we want to have a legal pointer for tracking parent of typespec, there needs to be a ref_obj in the hierarchy.

The definition typespec has a parent pointing to its definition location {The package, the design (if outside any scope), the module}, for complex types like structs it point where it is defined. Basic typespecs {logic, bit, byte...} are inlined, they get uniquely defined where used. All typespecs gets a parent.
In the elaborated model, typespecs get uniquified (cloned) and point to their respective instance parent, that is because of parameters or defparams that can influence their content.
Issue https://github.com/chipsalliance/Surelog/issues/2669 has been solved with location values, as stated, a ref_obj is out of the question because of the class inheritance of the object model. A new ref_typespec would have to be introduced and would break backward compatibility with too much code (And not adding much to the location solution).

May be I am just missing something obvious here. Please help me out.
Here's the UHDM for AllBindings test. I have enabled the vpi_ids command line argument to help uniquely identify the nodes. This examples has one enum definition, one module definition, and two unique use case of the enum in the module.

In the elaborated model, typespecs get uniquified (cloned)

As per your statement, I expected to find 3 instances of type_scr1_mem_resp_e enum_typespec

Definition in enum.v, line 1
Use in top.v, line 1
Use in top.v, line 3

But there is only one instance and that happens to be the definition (id: 4). Also, the parent pointer is null for the definition.
Also, typespecs seems to be crossing AllModules & TopModules boundary. It was my understanding that everything gets cloned during the elaboration process. Is that not the case anymore?
design: (work@top), id:18
|vpiElaborated:1
|vpiName:work@top
|uhdmallModules:
\_module: work@top (work@top), id:19 dut.sv:1:1: , endln:5:10, parent:work@top, parID:18
  |vpiFullName:work@top
  |vpiDefName:work@top
  |vpiNet:
  \_logic_net: (work@top.dmem2exu_resp_i), id:21, line:1:57, endln:1:72, parent:work@top, parID:19
    |vpiName:dmem2exu_resp_i
<EMAIL_ADDRESS>  |vpiNet:
  \_logic_net: (work@top.dmem2exu_resp_ii), id:23, line:3:37, endln:3:53, parent:work@top, parID:19
    |vpiName:dmem2exu_resp_ii
<EMAIL_ADDRESS>  |vpiPort:
  \_port: (dmem2exu_resp_i), id:20, line:1:57, endln:1:72, parent:work@top, parID:19
    |vpiName:dmem2exu_resp_i
    |vpiDirection:1
    |vpiLowConn:
    \_ref_obj: , id:22
      |vpiActual:
      \_logic_net: (work@top.dmem2exu_resp_i), id:21, line:1:57, endln:1:72, parent:work@top, parID:19
|vpiTypedef:
\_enum_typespec: (type_scr1_mem_resp_e), id:4, line:1:1, endln:5:24
  |vpiName:type_scr1_mem_resp_e
  |vpiInstance:
  \_design: (work@top), id:18
  |vpiBaseTypespec:
  \_logic_typespec: , id:3, line:1:14, endln:1:19
    |vpiRange:
    \_range: , id:0, line:1:20, endln:1:23
      |vpiLeftRange:
      \_constant: , id:1, line:1:20, endln:1:21, parID:0
        |vpiDecompile:1
        |vpiSize:64
        |UINT:1
        |vpiConstType:9
      |vpiRightRange:
      \_constant: , id:2, line:1:22, endln:1:23, parID:0
        |vpiDecompile:0
        |vpiSize:64
        |UINT:0
        |vpiConstType:9
  |vpiEnumConst:
  \_enum_const: (SCR1_MEM_RESP_NOTRDY), id:6, line:2:5, endln:2:36
    |vpiName:SCR1_MEM_RESP_NOTRDY
    |UINT:0
    |vpiDecompile:2'b00
    |vpiSize:2
  |vpiEnumConst:
  \_enum_const: (SCR1_MEM_RESP_RDY_OK), id:9, line:3:5, endln:3:36
    |vpiName:SCR1_MEM_RESP_RDY_OK
    |UINT:1
    |vpiDecompile:2'b01
    |vpiSize:2
  |vpiEnumConst:
  \_enum_const: (SCR1_MEM_RESP_RDY_ER), id:12, line:4:5, endln:4:36
    |vpiName:SCR1_MEM_RESP_RDY_ER
    |UINT:2
    |vpiDecompile:2'b10
    |vpiSize:2
|uhdmtopModules:
\_module: work@top (work@top), id:24 dut.sv:1:1: , endln:5:10
  |vpiName:work@top
  |vpiVariables:
  \_enum_var: (work@top.dmem2exu_resp_i), id:15, line:1:57, endln:1:72, parent:work@top, parID:24
    |vpiTypespec:
    \_enum_typespec: (type_scr1_mem_resp_e), id:4, line:1:1, endln:5:24
    |vpiName:dmem2exu_resp_i
<EMAIL_ADDRESS>    |vpiAutomatic:1
    |vpiVisibility:1
  |vpiVariables:
  \_enum_var: (work@top.dmem2exu_resp_ii), id:16, line:3:37, endln:3:53, parent:work@top, parID:24
    |vpiTypespec:
    \_enum_typespec: (type_scr1_mem_resp_e), id:4, line:1:1, endln:5:24
    |vpiName:dmem2exu_resp_ii
<EMAIL_ADDRESS>    |vpiAutomatic:1
    |vpiVisibility:1
  |vpiDefName:work@top
  |vpiPort:
  \_port: (dmem2exu_resp_i), id:25, line:1:57, endln:1:72, parent:work@top, parID:24
    |vpiName:dmem2exu_resp_i
    |vpiDirection:1
    |vpiLowConn:
    \_ref_obj: (work@top.dmem2exu_resp_i), id:26, parent:dmem2exu_resp_i, parID:25
      |vpiName:dmem2exu_resp_i
<EMAIL_ADDRESS>      |vpiActual:
      \_enum_var: (work@top.dmem2exu_resp_i), id:15, line:1:57, endln:1:72, parent:work@top, parID:24
    |vpiTypedef:
    \_enum_typespec: (type_scr1_mem_resp_e), id:4, line:1:1, endln:5:24
    |vpiInstance:
    \_module: work@top (work@top), id:24 dut.sv:1:1: , endln:5:10

Fixed by #2700
I made the following change, typespecs now always have a parent:
If the typespec is declared at the $root level, the parent is the design object
If the typespec is declared in a package it is the vpiTopPackage
If the typespec is declared in a module or interface or class or program it is the vpiAllModule, vpiAllInterface, vpiAllClass, vpiAllProgram object
If a typespec is declared in the generate statement, it is the generate statement instance (Fully elaborated)


DS-2880: additional javadocs docs and renames for clarity

Currently still a work in progress.

Thanks @rradillen and @jonas-atmire!  Let us know when this is ready for review and merge. It's looking good so far (at a glance).  For now, I'll flag this for 6.0 and mark as "work in progress"

@rradillen and @jonas-atmire: This PR now looks to include some code changes?  We'd need to get the description of it updated, if it's now more than just Javadocs.
To be clear, code refactoring is OK, but it'd need to be described in this PR.

I changed some names of classes to more acurately reflect their purpose. I.e. make them more self documenting.

@rradillen : any updates on this work? We're striving to get 6.0 out the door before OR16, and time is getting short.
Also, as noted in the related DS-2880 ticket comments, as of yet, we cannot seem to get PubMed integration working in the pre-6.0 codebase.

Restructured the packages to have a better overview of functionality and minimise orphan classes.
Updated the documentation accordingly
I've retested this PR rebased on the latest master to verify it still works.
To correctly retrieve the actual records (+fixing errors while retrieving a handlebars file), the latest config update pull request (https://github.com/DSpace/DSpace/pull/1370) is required though. Since this is a small quick win change, I don't think it would be any problem to merge it.
The latest (non-javadoc) documentation can be found here.
https://wiki.duraspace.org/display/DSDOC6x/2016+Framework+for+live+import+from+external+sources

We've finished the changes we wanted to make.
Summary:

Added javadoc to all packages, methods and classes in org.dspace.importer.external
Restructured the package tree to be a little more sensible.
Renamed classes to be more descriptive of their function.
Updated the README.md and ported those changes to https://wiki.duraspace.org/display/DSDOC6x/2016+Framework+for+live+import+from+external+sources

Note that #1370 should be merged first and this one should be rebased on the then master. (In reverse rebasing that will be a nightmare).

Closing this PR in favor of #1462 (which is a merger of all the commits in this PR along with some of them from #1370).


Proper compute step in a separate thread

Currently, the compute step is done synchronously with the render step, but it should be changed so that it does not depend on things like Window events (e.g. keyboard input, resizing etc).

Investigating this in the feat-improve-async-execution branch.
As of 78a3574, the implementation in the branch is still not working. See attached image: the interval between compute steps can take up to about 600ms, but it should take at most 1/60s=16.7ms

Not possible because wgpu still doesn't support fine grained synchronization control and barriers (reference: https://github.com/gfx-rs/wgpu/issues/1066 and https://github.com/gfx-rs/wgpu/issues/1260), which makes commanding the GPU through multiple CPU threads infeasible.


Deprecation

Jira link(s)
https://issues.jboss.org/browse/RHMAP-21138
What
Add deprecation notice
Why
Analytics feature is deprecated
How
Update the README to make it clear.
Verification Steps
Checklist:

[ ] Code has been tested locally by PR requester
[ ] Changes have been successfully verified by another team member

@davidffrench thank you for your review.


OADP-708/OADP-1526: Validation for BSL/VSL credentials secrets

OADP-708: validate secret names in BSL and VSL, remove required default VSL secret if no VSL.
OADP-1526: Validate existence of VSL credentials.
This includes a rebase of #784, and adds an extra commit on top. I'm not sure if it's better to rebase and merge #784 separately and use this just for the OADP-1526 work, but the changes in this combined pull request are working as far as I can tell.

/test all


API documentation

https://apiblueprint.org/
https://raml.org/developers/document-your-api
https://github.com/tmcw/docbox
https://github.com/Rebilly/ReDoc

Draft - https://mlowicki.github.io/rhythm/api.
TODO:

Examples for API returning list of jobs
API in some places return nil like for not set labels - idea is to replace it with empty map
Describe the format of payload for adding / updating job


"search_engine=v2 is not available for your tenant because it is deprecated" error

Description
I've configured WP-Auth0. But then after trying to login, it says:
There was a problem with your log in:
{\"statusCode\":400,\"error\":\"Bad Request\",
\"message\":\"The User Search Engine v2
(search_engine=v2) is not available for your tenant
because it is deprecated. Please use the
User Search Engine v3 instead (search_engine=v3).
For guidance on how to upgrade from v2 to v3, see
https://auth0.com/docs/users/search/v3#migrate-from-search-engine-v2-to-v3\",
\"errorCode\":\"operation_not_supported\"}
[error code: access_denied]

Prerequisites

[x] Did you check the documentation? Yes, it only says API for migration for standard web app, but says nothing about this wordpress plugin
[x] Did you check the Auth0 Community? Yes. Found this link, it says something about user API, but not sure if this is relevant
[x] Did you check the WP.org Support Forum? Yes
[x] Are there any related or duplicate Issues or PRs in this repo? No duplicate

Environment
Please provide the following:

WP-Auth0 version: 3.7.0
WordPress version: 4.9.8
PHP version: PHP 5.6.33-3+ubuntu16.04.1+deb.sury.org+1 (cli)
Browser version, if applicable: Firefox 62.0.3 (64-bit)

Reproduction

Create new tenant with Auth0
Implement Wordpress by creating new Application, as in Auth0 official guide
Trying logging in with Auth0

Expectation: can login as usual
Actual: It shows search_engine=v2 is not available for your tenant because it is deprecated

Thanks for the feedback, we will look into this.

@mufid  - Thank you for the report here and apologies for the trouble. The fix here is:

Go to your Auth0 dashboard > Rules
Edit the Account-Linking-Do-Not-Rename Rule:

On or around line 26, change v2 to v3

I'll put out a patch release to address other new installs.

Releasing the patch on WP.org now.


Storing info

Could you check and approve it so the new stuff can be added then to a new storingInfo branch?

Fixing the merge conflicts resulted in a merge from dev to this branch, which was something I thought was not really a good idea, but also resulted in what this pull request was needed for, so I'm closing it since the problem was fixed 😬


Encapsulate dimension, vector data type validation/processing inside Library

Description
As part of #1779 , we need to have the ability to take a user config for a float based space type (i.e. l2) and configure the quantization framework to go from float to bit and build a faiss binary index. In the current implementation, the data type validation is outside of the KNNLibrary/engine abstractions. This will make it difficult do the complex configuration around the quantization framework index building and search. The main theme of this PR is to move towards handling Library specific configuration to the library.
This PR does the following:

Adds KNNMethodConfigContext that is passed to KNNLibrary for validation as well as processing. The KNNMethodConfigContext object has information outside of what is passed by the user for configuring the method. This will allow the KNNLibrary specific components to do more complex validation/processing logic such as configuring a binary index, or figuring out how to validate/process incoming vectors. This wasnt added as a part of KNNMethodContext because it would bloat the class further. This is somewhat of an extension to the VectorSpaceInfo abstraction
For per-dimension processing/validation, faiss fp16, we moved the different validators/processors to the Library so we dont have to extract encoder information from the mapping.
Dimension check's and version created were added to KNNMethodConfigContext

Check List

[X] Commits are signed per the DCO using --signoff.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@navneet1v ah I forgot about that - good catch. Let me fix

@jmazanec15 seems like a build failure.. can you check once whats happening

@navneet1v I dont see anything interesting in the logs and am not able to reproduce it locally. Im guessing its unrelated/flaky. Captured the logs: https://gist.github.com/jmazanec15/ec985b4aeeae3325d5159974cfb375ab. Ill retry


[ISSUE #2494] Fix skip oauth2 plugin failed

Fix #2494 .

Codecov Report

Merging #2495 (42868d0) into master (c8ddbdb) will decrease coverage by 0.39%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #2495      +/-   ##
============================================
- Coverage     59.96%   59.57%   -0.40%
+ Complexity     4157     4121      -36
============================================
  Files           651      651
  Lines         18283    18284       +1
  Branches       1654     1654
============================================
- Hits          10964    10892      -72
- Misses         6488     6558      +70
- Partials        831      834       +3

Impacted Files
Coverage Δ

.../org/apache/shenyu/plugin/oauth2/OAuth2Plugin.java
33.33% <0.00%> (-1.97%)
:arrow_down:

...rg/apache/shenyu/admin/utils/ThreadLocalUtils.java
0.00% <0.00%> (-66.67%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
61.38% <0.00%> (-19.81%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
51.57% <0.00%> (-12.64%)
:arrow_down:

...a/org/apache/shenyu/common/utils/VersionUtils.java
67.85% <0.00%> (-10.72%)
:arrow_down:

...apache/shenyu/admin/utils/ShenyuDictH2Trigger.java
63.63% <0.00%> (-9.10%)
:arrow_down:

...ache/shenyu/admin/utils/PluginHandleH2Trigger.java
63.63% <0.00%> (-9.10%)
:arrow_down:

.../apache/shenyu/admin/model/dto/BatchCommonDTO.java
50.00% <0.00%> (-7.15%)
:arrow_down:

...apache/shenyu/admin/model/dto/AuthPathWarpDTO.java
57.14% <0.00%> (-7.15%)
:arrow_down:

...org/apache/shenyu/admin/model/dto/AuthPathDTO.java
58.82% <0.00%> (-5.89%)
:arrow_down:

... and 26 more

Continue to review full report at Codecov.

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


Update docs for upgrade command

Added new command flags and also replaced the description with what was provided in winget output for the upgrade command

[x] I have signed the Contributor License Agreement.
[x] This pull request is related to an issue. (talked about outdated docs briefly here #3263)

Microsoft Reviewers: Open in CodeFlow

@ryfu-msft can you double check to make sure these arguments work as documented here?

/azp run


neovim lsp jump to definition throws error on readonly files when using suda_smart_edit

This has been a long-standing issue of mine, which I finally got around to troubleshooting
I've been using suda_smart_edit = 1 because it is extremely useful when editing system files
However, I noticed when doing scala development, whenever I would use vim.lsp.buf.definition to a dependency file, I would get an error (this happens on neovim 0.8.1, but also happens on every neovim version I can remember):
"~/myproject/.metals/readonly/dependencies/play_2.13-2.8.18-sources.jar/play/api/mvc/Action.scala" 511L, 18648B
Error executing vim.schedule lua callback: /usr/share/nvim/runtime/lua/vim/uri.lua:86: Invalid buffer id: 26
stack traceback:
        [C]: in function 'nvim_buf_get_name'
        /usr/share/nvim/runtime/lua/vim/uri.lua:86: in function 'uri_from_bufnr'
        /usr/share/nvim/runtime/lua/vim/lsp/util.lua:254: in function 'get_lines'
        /usr/share/nvim/runtime/lua/vim/lsp/util.lua:320: in function 'get_line'
        /usr/share/nvim/runtime/lua/vim/lsp/util.lua:335: in function 'get_line_byte_from_position'
        /usr/share/nvim/runtime/lua/vim/lsp/util.lua:1096: in function 'jump_to_location'
        /usr/share/nvim/runtime/lua/vim/lsp/handlers.lua:359: in function 'handler'
        /usr/share/nvim/runtime/lua/vim/lsp.lua:1383: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>
Press ENTER or type command to continue

Running buffers returns:
:buffers
  1  h   "api/app/myproject/controllers/MyController.scala" line 353
 27 %a   "suda:///home/perrin4869/myproject/.metals/readonly/dependencies/play_2.13-2.8.18-sources.jar/play/api/mvc/Action.scala" line 1
Press ENTER or type command to continue

Since I noticed the buffer was renamed to suda:///, I tried disabling the plugin, and the problem was solved.
You can probably reproduce this by doing vim.lsp.buf.definition which would result in opening a readonly file on any lsp server, this is not specific to scala (but probably common in scala due to metals creating readonly dependency files).
I really don't have much of a clue how this could be solved, but I thought I'd report it

Thanks for the report. Well, I'm not sure but it seems Neovim accidentally enables LSP features on a virtual file (suda://...) even Neovim cannot handle it. So it's a kinda Neovim's runtime issue I guess.

Yeah feel free to close this if you don't consider this a suda issue.
But to be fair, lsp should be enabled in that virtual file, even if it's not writable you can jump to definition, etc

But to be fair, lsp should be enabled in that virtual file, even if it's not writable you can jump to definition, etc

Yes but only when Neovim's LSP itself supports a virtual file handling I think.


Cannot read property 'toRgb' of undefined when hsv() is called on rgba gradient

I am trying to get the HSV short interpolation for this two colors:

rgba(86, 86, 86, 1)
rgba(45, 163, 185, 1)

I run:
const gradient = tinygradient(['rgba(86, 86, 86, 1)','rgba(45, 163, 185, 1)']);
console.log(gradient.hsv(9, 'short'))
// Cannot read property 'toRgb' of undefined

This can be replicated on https://mistic100.github.io/tinygradient/, if you open the console and run the above. It seems work fine if I run
console.log(gradient.rgb(9))

But I need the hsv interpolation on this case.
Stack:

Fixed in 1.1.2, please note that HSV interpolation is not possible anyway when there is a grayscale color. The error was in the wallback from HSV to RGB.


Add DDEV_PHP_VERSION to image build time, docs for building extension

The Problem/Issue/Bug:
It was always awkward to build a PHP extension in a Dockerfile because you had to do the very fragile setting of PHP version inside the Dockefile
How this PR Solves The Problem:

Provide DDEV_PHP_VERSION at Dockerfile build time
Provide docs example on how to build an extension

Manual Testing Instructions:
Try out the doc.
Automated Testing Overview:
Added test of this in TestCustomBuildDockerfiles

For you @drupal-daffie :)

Thanks so much for the improvements @mattstein !


ErrorException Laravel Framework Illuminate Foundation

{"error":{"type":"ErrorException","message":"Undefined index: timezone","file":"/home/admin/web/solder.servername.net/public_html/vendor/laravel/framework/src/Illuminate/Foundation/start.php","line":167}}> php artisan optimize
{"error":{"type":"ErrorException","message":"Undefined index: timezone","file":"/home/admin/web/solder.servername.net/public_html/vendor/laravel/framework/src/Illuminate/Foundation/start.php","line":167}}[root@servername public_html]# php -v

Error appears after installing not sure what to make of it never had this issue last time i install solder on the same server. Running CentOS 7 php 5.5

http://i.imgur.com/3fjnEyj.png

Turned out i didnt have php55w-fpm installed installed with no errors after fixing that.

gloglmic - I'm having the same problem on a Mac machine where I'm running PHP-5.6.11 - I'm not sure what php5w-fpm is and how to install it - can you elaborate on your fix and how I can get this fixed as well?  Thanks!

@ChipCustomizer open a new issue, since you are on a different platform from giogimc. when you open the new issue, please specify whether you are using homebrew or macports, and i'll see if i can't help.


Problem with compiling

After my recent update to the repository, the compiling was broken without any error messages on github.
The CSS did not apply to the page and the posts were not compiled.
Even I revert the commit, it doesn't help.
My repository is here: https://github.com/eugene-yang/blog
Local Jekyll is working fine. I have no idea why this happened. Thank you.

It looks like right now the compiler can only compile the gitpage for account instead of general gitpage repository.
Is there any configuration I need to make for the compiler to generate the right path to documents?


linux_arm build error: constant<PHONE_NUMBER>51353865 overflows big.Word

On linux_arm, a dependency fails to build.
Question: do you have the same problem when trying to build the "gdrive-linux-arm" download file?
$ go get github.com/prasmussen/gdrive
# github.com/soniakeys/graph
../go/src/github.com/soniakeys/graph/bits.go:71: constant<PHONE_NUMBER>51353865 overflows big.Word

+1

You might have better luck compiling now, a change was done to the graph library 3 days ago regarding 32-bit support: soniakeys/graph@a9791af
Just make sure you get the latest version of the graph library.

Unfortunately not. See my comment on https://github.com/soniakeys/graph/issues/41.

The graph library is changed hopefully to support arm but I have no way to test it.  Confirmation that it works for arm would be much appreciated.

Gdrive builds and runs fine now on "linux_arm".

Excellent, thanks @soniakeys


feat: sell and fund flow [LIVE-784]

❓ Context

Impacted projects: [e.g. live-mobile]

Linked resource(s): https://ledgerhq.atlassian.net/browse/LIVE-784
Old pr: https://github.com/LedgerHQ/ledger-live-mobile/pull/2232

It's the same as https://github.com/LedgerHQ/ledger-live-desktop/pull/4361 but for mobile.

Add the exchange SELL and FUND flow in the context of the live-app-sdk.

✅ Checklist

[ ] Test coverage: Did you write any tests to cover the changes introduced by this pull request?
[x] Atomic delivery: Is this pull request standalone? In order words, does it depend on nothing else?
[ ] Breaking changes: Does this pull request contain breaking changes of any kind? If so, please explain why.

📸 Demo

https://user-images.githubusercontent.com/8398372/156401634-8cc60458-d8c1-4b18-98e7-6d73dcdb95c2.mov
🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

Parts of the app affected / Test plan

Start the platform-app-test-exchange locally (yarn dev)
Start Ledger Live Mobile with envs below
Settings -> Developer -> Load Platform Manifest
Paste manifest below
Test the SELL and FUND flows (only works with BTC as of today)

PS: You will need a test version of the exchange app to test the fund flow, cf. the platform-app-test-exchange README for details.

.env
DISABLE_TRANSACTION_BROADCAST=1
MOCK_EXCHANGE_TEST_CONFIG=1

manifest.json
{
 "id": "test-app",
 "name": "Test app",
 "url": "http://localhost:3000",
 "homepageUrl": "https://developers.ledger.com/",
 "icon": "",
 "platform": "all",
 "apiVersion": "0.0.1",
 "manifestVersion": "1",
 "branch": "debug",
 "categories": ["tools"],
 "currencies": "*",
 "content": {
   "shortDescription": {
     "en": "Test Live App. Use at your own risk."
   },
   "description": {
     "en": "Test Live App. Use at your own risk."
   }
 },
 "permissions": [
   {
     "method": "*"
   }
 ],
 "domains": [
   "https://*",
   "http://*"
 ]
}

Successful Fund on Android (physical) with Nano X
https://user-images.githubusercontent.com/87659842/173056896-05e0261f-0618-4bf7-9056-ad4a00542874.mov

Unsuccessful fund on iOS when it freezes on the 'complete' phase'
https://user-images.githubusercontent.com/87659842/173058514-08adcc98-314f-418b-aaf5-b316d262a6c1.mov
Successful iOS fund on Nano X:
https://user-images.githubusercontent.com/87659842/173058699-4548d0c2-43fa-480f-8698-ef85b92baae7.mov


Fix Rosetta handling of coinbase fees (plus miscellaneous related fixes)

Fix broken query_height query in Rosetta block.ml

Fix Rosetta handling of coinbase fees
Rosetta was incorrectly using a constant for all coinbase fees. Some
fees are "supercharged" so they're actually variable. The specific fee
was already available so this switches to using that and removes the
code that was pulling the base coinbase fee constant from GraphQL.

Tested using Rosetta ./start.sh and Coinbase's rosetta-cli.
Checklist:

[x] Document code purpose, how to use it
[x] Tests were added for the new behavior
[ ] All tests pass (CI will check this if you didn't)
[x] Serialized types are in stable-versioned modules
[x] Does this close issues? List them:

!ci-build-me

!ci-build-me

!ci-build-me


Programs are not executed in Firefox

I tried the Wipple playground in Firefox 113 on Ubuntu 22.04. The programs in code boxes don't run and I get the following error message in the console window, apparently for each code block.
SyntaxError: export declarations may only appear at top level of a module
at worker-1e0324df.js:18:21590
In Chrome and Chromium however they run properly.

I just tested in Firefox 114 and everything appears to be working, so please update your browser and let me know if it works for you! The issue was that Firefox didn't support ES Modules in Web Workers, but they added support in version 114: https://www.mozilla.org/en-US/firefox/114.0/releasenotes/#note-789543


Improve comment consistency

Comments are not overly consistent in style throughout the project.

Thanks for this feedback Mark, I'll take a look as I run through it.

 Hopefully it is adopted.

(Referring to pull request I made #3 which does address this issue)


Making VectorProductDomain more generic

Would it be possible for VectorProductDomain to have a type parameter for the array type, to allow allow for using a CuArray, StructArray, etc.? If so, adding support for Adapt.jl might make sense in the same context.

It should be relatively easy to add a new product domain for a specific type, since most of the logic is implemented for the abstract supertype ProductDomain.
In contrast, parameterizing the container type itself is not a simple thing to do, I'm afraid. What do you want to do exactly? Right now, it should be possible to use any AbstractVector to check for membership of a VectorProductDomain without conversion, unless the element types don't match. (Do let me know if this doesn't work, it should.) But this assumes you're happy with storing the domains themselves as a Vector. If that is not the case, something new would be needed.

I meant using something like
struct VectorProductDomain{T,D,V<:AbstractVector{D}} <: ProductDomain{V}
    domains::D
end

Adapt.adapt_structure(to, d::VectorProductDomain) = VectorProductDomain(adapt(to, d.domain))

So that one could do things like adapt(CuArray, my_domain), as part of lifting a larger computation (with nested data structures, containing ProductDomains somewhere) onto a GPU.

Note that there are four types involved here:

the element type of the product domain (a vector, let's say V)
its element type T (as in V <: AbstractVector{T})
the type of the composing domains (D)
and the container type of the list of domains (DD).

The connection is that eltype(DD) == D and eltype(D)==T. In turn, eltype(V)==T. In other words, V is some vector of elements of type T, and DD is some vectors of elements of type Domain{T}. The simplification in VectorProductDomain is that V==Vector{T} and DD==Vector{D}.
So, the most general vector product domain would be:
struct GeneralVectorProductDomain{DD,T,V<:AbstractVector{T}} <: ProductDomain{V}
    domains::DD
end

It would be assumed that domains is an indexable list of domains of type D. A constructor would have to verify or ensure that eltype(eltype(domains))==eltype(V)==T.
In your intended usage with adapt, which of the types would end up changing? This is not clear to me. Is it enough for V to change to a CuArray, or would DD have to be a CuArray of Domain{T}? If that is even possible, I don't know :-)

Well, in many use cases, e.g. whendomains if a vector of a bitstype, e.g. intervals, representing domains as a CuArray should be no problem, right?

Ah, sorry - I think I misunderstood something, I mixed up Vector{D} and Vector{T}.

Now I see - the difficulty here stems from the fact that domains don't have to be a subtype of  Domain.
Checking the element types in the ctor, like you proposed, should be fine though, right?

In your intended usage with adapt, which of the types would end up changing? This is not clear to me. Is it enough for V to change to a CuArray, or would DD have to be a CuArray of Domain{T}

Hm ... not sure, I think I haven't fully understood the role of V yet. But DD would definitely be a CuArray. Let's take a this use case - a very high dimensional space, but the domains are simple intervals. So I'd like to do something like this
d = ProductDomain([0..i for i in 1:10^5]
d_cu = adapt(CuArray, d)

with the result that d_cu.domains is a CuArray. So that something like
in.(lots_of_points_cu, Ref(d_cu))

could be made very fast.

Okay, the example helps, but I think we're not in the same place yet :-)
If pd is a product domain, then in(x, pd) makes sense when x is a vector. Here, the output is a single boolean: true if all the elements of x belong to the corresponding domains in pd. The in function maps a vector to a single boolean.
The statement in.(x, Ref(pd)) makes sense when x is a vector of vectors. In that case, the output is a vector of booleans: the broadcast notation yields something like [in(el, pd) for el in x], so each el has to be a vector.
Somehow I don't think that is what you have in mind. Is it? If you want to check a very large vector for membership of a very high-dimensional product domain and expect a single boolean output, then we have to look into how to do the mapreduce operation efficiently on GPU's. If you want to obtain a large vector of booleans, with each element telling whether x[i] belongs to pd.domains[i], then you don't actually need a product domain. You could do in.(x_cu, domain_cu) where domain_cu is a CuArray of intervals (or other domains).

For reference, here is the mapreduce operation of a product domain. I don't know whether this would be efficient when x and domains are CuArray's, or even if I could represent a vector of domains on a GPU - I'm not familiar enough with it I'm afraid.

The statement in.(x, Ref(pd)) makes sense when x is a vector of vectors. In that case, the output is a vector of booleans

Yes, that's what I had in mind, as a use case example. For example assume you've generated a lot of samples via MCMC in a high-dimensional space, and want to know which are in a certain sub-volume. Or just which fraction of them, in which case you'd then take the mean of the resulting boolean vector.

For reference, here is the mapreduce operation of a product domain

In my described use case, many mapreduce's would run in parallel - not sure how efficient it would be, but I think a fitting implementation could be found. It might not even be about the pure speed - you may have to do volume membership tests as part of a larger computation, and want to avoid moving data back to the CPU for that.

Ok cool, sorry - it looked like a suspiciously advanced use case to me (I guess it is!) especially with the product domain itself already having dimension 10^5 in your example.
It may take more work to be efficient, but I agree that the first goal should be to be able to express the problem. So I'll look into that general product domain first.

Well, it wouldn't necessarily be 10^5 dimensions, but in Bayesian inference (e.g. via HMC), dimensionality can get high. And we often need a way to express parameter bounds.

It may take more work to be efficient, but I agree that the first goal should be to be able to express the problem. So I'll look into that general product domain first.

Thanks! I agree, making things really efficient may not be so easy, but being able to store bounds in a flexible would already be great. It would also make it possible to use things like StructArray, which would (e.g. for intervals) result in an column-oriented memory layout.

Meanwhile I implemented a more general product domain on master. I'm hesitant to include packages that are not otherwise related to domains as dependencies, but it should now be easy to link to Adapt.jl elsewhere.
It is called GenericVectorProductDomain, but one can also use the existing ProductDomain function (with an AbstractVector of domains as argument) or the ProductDomain{V} constructor where V is an AbstractVector. The concrete subtype that is returned depends on the types of the arguments and on V.
julia> using DomainSets

julia> pd = GenericVectorProductDomain([0..i for i in 1:500])
0..1 x 0..2 x 0..3 x 0..4 x 0..5 x ... x 0..496 x 0..497 x 0..498 x 0..499 x 0..500

julia> pd_ofs = ProductDomain(OffsetArray([0..i for i in 1:10], 1:10))
0..1 x 0..2 x 0..3 x 0..4 x 0..5 x 0..6 x 0..7 x 0..8 x 0..9 x 0..10

julia> typeof(ans)
GenericVectorProductDomain{Array{Int64,1},OffsetArray{Interval{:closed,:closed,Int64},1,Array{Interval{:closed,:closed,Int64},1}}}

julia> pd = GenericVectorProductDomain{Vector{Float64}}([0..i for i in 1:500])
0.0..1.0 x 0.0..2.0 x 0.0..3.0 x 0.0..4.0 x 0.0..5.0 x ... x 0.0..496.0 x 0.0..497.0 x 0.0..498.0 x 0.0..499.0 x 0.0..500.0

In the line above, since V is a Vector{Float64}, the element type of the domains is converted to Float64. This is to ensure that, as mentioned above, eltype(eltype(domains))==eltype(V).
Would this work?

Oh, yes, very nice:
using DomainSets, IntervalSets, StructArrays
d = ProductDomain(StructArray([0..i for i in 1:10]))
d.domains isa StructArray

Thank you!

I'm happy to hear that it works! I forgot to test the in.(x, Ref(pd)) example, but I just did and it seems to work too. Once the basic functionality seems right, I'll tag the minor release update.
For reference, as I mentioned the membership of product domains revolves around a mapreduce function call, though there are a few wrappers around it. All memory allocations do occur in that function call, I checked. In case you want to change this for a combination of types (for particular DD and V say), it is best to specialize indomain.
The GenericVectorProductDomain is still a vector domain (there could be an even more general product domain I suppose), because vector domains are a special case: the in method accepts any AbstractVector and passes it on to indomain function without conversion. That is because conversions of arrays are typically not very efficient.

What's the difference between ProductDomain and GenericVectorProductDomain now`?
Btw - seems to run on a GPU, too, now (just not super fast, but that was to be expected). Will look more deeply into this at some point.

Regarding Ref(pd) in bcasts - how about defining
@inline Base.Broadcast.broadcastable(d::Domain) = Ref(d)

I guess domains should in general behave like scalars under broadcasting, right?

ProductDomain is the abstract supertype of product domains. I've made different concrete subtypes, because they require different type parameters and I did not want to make a single super-parameteric type.
One advantage of the abstract supertype is that it enables the ProductDomain{T}(...) syntax, i.e., you can specify what the element type of the product domain should be. You can't usually append a type parameter to a function, only to types. Also, the constructor returns a concrete type that matches the product domain the user has in mind (based on the arguments), without the user having to worry about what the concrete type is called. This means the implementation of the concrete type could also change in between releases, as long as their behaviour remains the same. It also means I can make special cases that are more efficient (for example require fewer type parameters) for the compiler.
So, you'll always have ProductDomain(whatever) isa ProductDomain, but in reality it will be some concrete subtype.

Regarding Ref(pd) in bcasts - how about defining
@inline Base.Broadcast.broadcastable(d::Domain) = Ref(d)

I guess domains should in general behave like scalars under broadcasting, right?

I'm afraid we already used broadcast to make maps, e.g.: 2 * d .+ 4 maps the domain by 2x+4. It is based on seeing the domain as a container of points. It is just a continuous container, rather than a discrete one.
But perhaps something can be done when broadcast styles are mixed, reverting to Ref(d) in that case.

Ah, silly me, sorry. I see, ProductDomain returns either a VectorProductDomain or a GenericVectorProductDomain, depending on the array type. Just curious, is there a reason to have both?

It is based on seeing the domain as a container of points.

Oh, sure - Those semantics do make sense of course!

Ah, silly me, sorry. I see, ProductDomain returns either a VectorProductDomain or a GenericVectorProductDomain, depending on the array type. Just curious, is there a reason to have both?

Of course any VectorProductDomain can be represented as a GenericVectorProductDomain, but that doesn't mean that it has to. The implementation is shared because it is implemented at a higher level. In some other case where I've used this pattern, it tremendously simplifies the output of statements, in particular when they contain the type... That is actually my main motivation :-)
A hidden cost of generalizing types is also in compiler time, though I've never actually tried to measure whether having fewer type parameters helps.

You can't usually append a type parameter to a function, only to types

Well, you can, as long as the functions are constructors. But yes, one has to be careful with the order of type parameters, it can't be changed, though types at the end can be left out. But for a type Foo{A, B, C} one can define a custom ctor Foo{A}(...), of course.

 I was just wondering if VectorProductDomain and GenericVectorProductDomain should be separate types, but I won't try to meddle with the design of your package (which I like a lot).  I was just wondering if VectorProductDomain and GenericVectorProductDomain should be separate types, but I won't try to meddle with the design of your package (which I like a lot). :-)

So VectorProductDomain{T} has a single type parameter, that's all. This pattern is fairly recent, it wasn't like that before. But for general types with many parameters the constructors for all the different use cases quickly become difficult to manage. In this case, the final straw came when I realized that certain use cases needed an extra parameter, but the others did not.
For completeness, and because there is no documentation, it is about the product of a 1D with a 2D domain. You typically want this to behave as a 3D domain. But then in may be called with an SVector{3}, and the job of the product domain is to call its elements with a 1d and 2d vector respectively. This information is kept in the DIM parameter in the VcatDomain. This gave me some headaches for a while.
In contrast, a VectorDomain assumes that all dimensions are the same, because storing the information necessary for the inverse of vcat would require storing another vector. Worse is that all types of the domains have to be the same in all dimensions too, otherwise it becomes less efficient.

Hmm, it is VectorProductDomain{T,D} with two type parameters.

But for general types with many parameters the constructors for all the different use cases quickly become difficult to manage.

I know what you mean ... had merry fun with that in ArraysOfArrays. :-)

it is about the product of a 1D with a 2D domain. You typically want this to behave as a 3D domain

Oh, right ... you did some heavy lifting, here!

I'm reconsidering and I currently made the VectorProductDomain more generic after all (not committed yet). It makes the code shorter. So, GenericVectorProductDomain will disappear again soon.

Nice! I have a very clunky domain/bounds system in the internals of BAT.jl, and I've love to replace it with something clean like DomainSets ...

I think the code we were talking about has been merged, so I'm closing this issue - feel free to reopen or open a new one if things can be improved.

Sure, thanks again!


update zh-hans

Proposed changes
Update zh-hans

Types of changes

Bugfix (non-breaking change which fixes an issue)

Linked Issues

Further comments

@vincent99   Hi vincent. These are the parameters of the custom cluster yaml, some commonly used by users and some configured according to best practices. Many users don't know how to configure these parameters, and our UI currently doesn't support customizing these parameters, so I put these common parameters in translation so I know how to configure them when editing cluster yaml.


image resize option added

for decreasing file sizes and creating  more readable log files when the image is too big.

Hello. Thanks for the PR.
Could you check why tests are failing?

I think there is no relation with this PR, I got same error before this commit.
It seems like an import error because of pyplot which uses numpy. I saw several issues about this error, it can be related with numpy version. According the issue below, numpy 1.15 works well but 1.16 and the CI uses 1.16.
https://github.com/numpy/numpy/issues/14012#issue-468102255


NameError: name 'char_field' is not defined

Traceback (most recent call last):
File "main.py", line 62, in
train_iter, test_iter = load_data(text_field, label_field, device=-1, repeat=False)
File "main.py", line 47, in load_data
train_data, test_data = dataset.splits(text_field, label_field)
File "/data/Neural_Speed_Reading_via_Skim-RNN_PyTorch/dataset.py", line 101, in splits
examples = cls(text_field, char_field, label_field, path=path, **kwargs).examples
NameError: name 'char_field' is not defined

The bug is fixed. Thanks.


Add getSessionAndUserBySessionId method to adapter-mongoose

As discussed on Discord.
I've added a getSessionAndUserBySessionId method to the mongoose adapter, which uses a lookup (join) instead of two separate db calls.

Thanks!


Is it possible to use the S4TF toolchain with GitHub actions?

Hi, I wondered if it's possible to use the toolchain for GitHub action tests. If no, is there another option for CI tests? Thanks.

Thanks. I'd like to run tests for an open source S4TF project I'm working on.
The docker file seems interesting. I'll see if I can use that.

@dan-zheng I checked if I could get that to work, but it crashes with:
CMake Error: The source directory "/swift-apis" does not appear to contain CMakeLists.txt.
277
Specify --help for usage, or press the help button on the CMake GUI.
278
The command '/bin/sh -c cmake -G Ninja -D CMAKE_BUILD_TYPE=Release -D CMAKE_Swift_COMPILER=/swift-tensorflow-toolchain/usr/bin/swiftc -D USE_BUNDLED_CTENSORFLOW=YES -D TensorFlow_INCLUDE_DIR=/swift-tensorflow-toolchain/usr/lib/swift/linux/x86_64/modulemaps/CTensorFlow -D TensorFlow_LIBRARY=/swift-tensorflow-toolchain/usr/lib/swift/linux/libtensorflow.so -B /BinaryCache/tensorflow-swift-apis -S /swift-apis' returned a non-zero code: 1

See https://github.com/rickwierenga/s4tfpackage/runs/432779938 for the full log. It's weird because that repo seems to contain a CMakeLists file: https://github.com/tensorflow/swift-apis/blob/master/CMakeLists.txt. I'm have very little experience with Docker so excuse me if this is a dumb question.

This is the GitHub Action repo: https://github.com/rickwierenga/S4TF-Tests. I deleted some pieces from the end of the Dockerfile, but that shouldn't be an issue because it crashes before that.
And this is the sample package I'm trying to use it with https://github.com/rickwierenga/s4tfpackage/.

@rickwierenga i get the same error when trying to run sudo docker build https://raw.githubusercontent.com/tensorflow/swift-apis/master/Dockerfile but if you do a git clone https://github.com/tensorflow/swift-apis.git and then cd swift-apis and sudo docker build . that seems to work.

Strange... The swift-apis repo should not be a dependency for the Dockerfile to work because that's the whole point of having Docker in the first place. Would you happen to know if the Dockerfile could be updated?

@dan-zheng I checked if I could get that to work, but it crashes with:
CMake Error: The source directory "/swift-apis" does not appear to contain CMakeLists.txt.
277
Specify --help for usage, or press the help button on the CMake GUI.
278
The command '/bin/sh -c cmake -G Ninja -D CMAKE_BUILD_TYPE=Release -D CMAKE_Swift_COMPILER=/swift-tensorflow-toolchain/usr/bin/swiftc -D USE_BUNDLED_CTENSORFLOW=YES -D TensorFlow_INCLUDE_DIR=/swift-tensorflow-toolchain/usr/lib/swift/linux/x86_64/modulemaps/CTensorFlow -D TensorFlow_LIBRARY=/swift-tensorflow-toolchain/usr/lib/swift/linux/libtensorflow.so -B /BinaryCache/tensorflow-swift-apis -S /swift-apis' returned a non-zero code: 1

Sorry, tensorflow/swift-apis's CI (Dockerfile) breaks occasionally! It should pass most of the time - when it's broken, our top priority is to fix it.
The CMake error should be fixed now. It occurred at the time because CMake support was just being added and unstable.

My request: could you please clarify what you mean by "how to use the S4TF toolchain with GitHub actions?" The question currently isn't particularly actionable - a specific request would be helpful!

Thanks. I will check it out as soon as I get the chance (probably Sunday) and I'll let you know how it goes.

could you please clarify what you mean by "how to use the S4TF toolchain with GitHub actions?" The question currently isn't particularly actionable - a specific request would be helpful!

William Zhang (@WilliamHYZhang) and I are building an open source project where we would like to run tests online before merging PRs. For most swift packages this is possible through the Swift Action (https://github.com/actions/starter-workflows/blob/master/ci/swift.yml), but it understandably fails for packages requiring third party toolchains. The Dockerfile seems like a great solution for this, if it works :)

@rickwierenga if you get a nice setup, let's figure out how to document it so others can learn from and benefit from your configuration too!

Here is a simple example of what you want to do @rickwierenga: https://github.com/xanderdunn/swift-action
It's much simpler and faster than using the swift-apis Dockerfile, which is getting and building many things. Just grabbing the pre-built binary is sufficient for a GitHub action.


Stop requesting changelogs in PRs

We added this requirement before the changelog was automated. Now that the changelog generated by a script, it's not helpful for PRs to update the changelog anymore, so we shouldn't expect it anymore.
What was the end-user problem that led to this PR?
We had to ask a PR to remove a changelog entry, even though the PR was following the docs.
What was your diagnosis of the problem?
It looks like we failed to update the docs when we automated generating the changelog.
What is your fix for the problem, implemented in this PR?
Removing the changelog requirement from the docs hopefully means that future PRs will not include changelog entries, and we can generate future changelogs automatically.
Why did you choose this fix out of the possible options?
I chose this fix because it seemed like the smallest change that would accomplish the goal.
/cc @mattbrictson

Nice! Thanks for updating that. 👍

@bundlerbot r+


Doc of Configure Contract Pallet is out of date

Is there an existing issue?

[X] I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

[X] This is not a support question.

Content request
In https://docs.substrate.io/tutorials/work-with-pallets/contracts-pallet/
No such crates named
'pallet-contracts-rpc-runtime-api', 'pallet-contracts-rpc'
Are you willing to help with this request?
Yes!

What is the solution to go to the end of the tutorial?

Potentially more context for this issue:

STEP "Implement the Contracts configuration trait"

Going to fresh install and try and reproduce, didn't have issues a couple weeks ago.

link to pallet_contracts_rpc_runtime_api and pallet_contracts_rpc are broken :
https://paritytech.github.io/substrate/master/pallet_contracts_rpc_runtime_api/index.html
https://paritytech.github.io/substrate/master/pallet_contracts_rpc/index.html

Any updates regarding this? I have been trying to complete the tutorial but facing similar issues

These crates have been removed (see: https://substrate.stackexchange.com/questions/6375/error-no-matching-package-named-pallet-contracts-rpc-found). Updating the documentation to reflect this.

Initially, errors seemed to be caused by a problem in the manifest files.
https://github.com/substrate-developer-hub/substrate-node-template/pull/407
However, after fixing those problems, we discovered major compatibility issues between the pallets required to add the pallets required for smart contracts and the current version of the node template.
To resolve these compatibility issues would require extensive changes to the configuration of the standard node template, including using older versions of all crates and modifying multiple files (far beyond what the tutorial was intended to demonstrate).
If you want to experiment with smart contract development for your blockchain, you should use the preconfigured substrate-contracts-node instead of the standard node template.
To dive directly into smart contract development, see the tutorials in Develop smart contracts.
If you have trouble with those tutorials, please open a new issue.


Replace custom FutureLift with monix-catnap implementation

Also cleaned up effect type bounds, now we don't ask for Concurrent: ContextShift everywhere

An extra dependency seems a bit too much, I agree


try to support tooz in EL8/py3

Problem: Tooz < 2.2.0 doesn't support consul heartbeat. @nmaludy Got it committed to tooz: https://github.com/openstack/tooz/commit/6e750b6921c42f3c2ffed2e135be4d9c65e96f36#diff-ac4db250c2e1f5b2d95e610996274b96.
I have tested this and updated fixed-requirements.txt as follows:
tooz==1.66.1; python_version <= '2.7'
tooz==2.3.0; python_version >= '3.6'

The question is - will this build correctly? It seems to me (@blag ) that the make requirements script doesn't put both lines in the generated requirements files.
Proof that it works:

Looks like CI is not happy with that requirements definition


Add Concept Exercise: the-farm

Towards #103
Scaffold https://github.com/exercism/cairo/blob/main/exercises/concept/calculator-conundrum
TODO:

[ ] use C#'s implemented concept exercise for inspiration, e.g. https://github.com/exercism/csharp/tree/main/exercises/concept/calculator-conundrum

[ ] implement instructions.md
[ ] implement introduction.md
[ ] implement hints.md
[ ] implement ./meta/design.md

[ ] implement the example solution in .meta/exemplar.cairo
[ ] implement the exercise stub at src/lib.cairo
[ ] implement tests for the exercise at tests/red_vs_blue_darwin_style.cairo
[ ] replace <your_gh_username> placeholder with your actual GH username in .meta/config.json
[ ] add missing blurb to .meta/config.json

Changed the exercise to calculator-conundrum as it's a much more straightforward exercise.


Add ability for server pre-shutdown hook

Problem statement
It would be awesome to be able to allow consumers of this library to add a pre-shutdown hook to the server that gets generated by go-swagger.  This would allow consumers to handle any tasks that are required before stopping accepting new connections (before shutting down the http(s) server).
In our particular case, we want to signal to the readiness probe (kube) that we are shutting down (return 500) so no traffic gets routed to this pod.  There is a small window of time when we still need to accept new connections (it is not deregistered from kube yet). When the SIGINT/SIGTERM signals are sent, we need to wait a period of time before shutting down the actual http server.
Area to add this feature
This should be a small change that we should be able to add this to the templates pretty easily.   I can create a PR for this.
Environment
swagger version: 2.x
go version: 1.12.7
OS:   Mac/Darwin

This issue can be closed.  I will leave it open for maintainers because I am not sure of the workflow here.

we tend to close with the PR. Thanks for your contribution!


_observableThrow will stop working in RxJS 8.0 see warning below.

(alias) _observableThrow(error: any): Observable (+2 overloads)
import _observableThrow
Returns an observable that will error with the specified error immediately upon subscription.
@param error — The error instance to emit
@deprecated
Support for passing an error value will be removed in v8. Instead, pass a factory function to throwError(() => new Error('test')). This is because it will create the error at the moment it should be created and capture a more appropriate stack trace. If for some reason you need to create the error ahead of time, you can still do that: const err = new Error('test'); throwError(() => err);.

This is for everyone who is still looking for a solution to this problem without having to adapt the current NSwag code.
Since I really like NSwag and really wanted to generate the client for Angular, I searched for a solution for a long time and found one.
You can simply take the template AngularClient.liquid, modify it and tell the generator the template folder with the modified template.
This way you can make even more adjustments to the generated client.
I simply expanded the two places in the template:

return {{ Framework.RxJs.ObservableThrowMethod }}(e)
return {{ Framework.RxJs.ObservableThrowMethod }}(response_)

like this:

return {{ Framework.RxJs.ObservableThrowMethod }}(() => e)
return {{ Framework.RxJs.ObservableThrowMethod }}(() => response_)

Have fun :-)


error using export_for_isaac.py: File name too long

Hi again,
Actually something strange happened.
When running the code like this: ./export_for_isaac.py with any kind of argument, like -h for instance, this error pops out.
The error disappears once you run the code like thins: python3 export_for_isaac.py...
I tried to delete the issue but could not, so I will simply close it with this comment.
Sorry


Fix Array.slice() forgetting Array with type.

Fixes https://github.com/godotengine/godot/issues/67015.
Before this PR, the function returned a new Array completely forgetting about the original Typed Array's type.

Might be worth checking if there are other modified Array-returning methods that would need the same treatment.

If there's any, for other methods outside of Array it may be a bit more slower and "annoying" because they can't just assign _p->typed directly.

Might be worth checking if there are other modified Array-returning methods that would need the same treatment.

The same should be done in Array::filter (in this PR, it's the same change).

Besides that Array::operator +(Array, Array) should also return a typed array if operands are typed arrays with the same type.
I think adding:
if (array_a.is_typed() && array_b.is_typed() && array_a.get_typed_builtin() == array_b.get_typed_builtin() && array_a.get_typed_class_name() == array_b.get_typed_class_name() && array_a.get_typed_script() == array_b.get_typed_script()) {
	sum.set_typed(array_a.get_typed_builtin(), array_a.get_typed_class_name(), array_a.get_typed_script());
}

at the beginning of (or rather before sum is resized):
https://github.com/godotengine/godot/blob/880a0177d12463b612268afe95bd3d8dd565bf52/core/variant/variant_op.h#L824-L834
should do the thing. Can be made as a separate PR, can be included in here.

Then there's a question whether Array constructors taking in PackedTArray:
https://github.com/godotengine/godot/blob/880a0177d12463b612268afe95bd3d8dd565bf52/core/variant/variant_construct.cpp#L204-L212
should also produce typed arrays? Of course in such case e.g. each of PackedByteArray, PackedInt32Array, PackedInt64Array would need to result in TypedArray<int64_t> (Array[int] in GDScript).
Not sure about this one though. Nevertheless this one is for sure for a potential separate PR.

I'm starting to smell a code smell. There could be an Array::copy_typed_from or something...

Applied this PR's fix to both filter() and map(), as well.

Applied this PR's fix to both filter() and map(), as well.

Array::map shouldn't be changed, array values can be mapped to any type.

Besides that Array::operator +(Array, Array) should also return a typed array if operands are typed arrays with the same type.
Can be made as a separate PR, can be included in here.

Yeah, another upcoming PR. It's a wholy different fix for a similar issue.

Then there's a question whether Array constructors taking in PackedTArray [...] should also produce typed arrays? Of course in such case e.g. each of PackedByteArray, PackedInt32Array, PackedInt64Array would need to result in TypedArray<int64_t> (Array[int] in GDScript).

I may be very wrong about this, but it doesn't seem like Typed Arrays bring much if any performance improvement, so to most users it wouldn't even matter. If anything, users may in fact want to convert Packed*Arrays to normal Arrays solely because they'd no longer be limited by what type they accept.

If anything, users may in fact want to convert Packed*Arrays to normal Arrays solely because they'd no longer be limited by what type they accept.

Yeah, good point. So ideally there would be a way to convert PackedTArray to generic Array or to Array[T] (which is the same generic array, just restricted to the given type) depending on what the user want. But I think it can be as is for now. Let's not complicate things unnecessarily. If/when it will be reported as an issue then it could be tackled I guess.

https://github.com/godotengine/godot/pull/54940 Is this not the + op fix?

#54940 Is this not the + op fix?

No, it doesn't change anything about OperatorEvaluatorAddArray (as it doesn't use Array::append_array being changed in #54940) which handles Array + Array.

Thanks!

While doing #67001 I noticed that Array has actually multiple methods that handle typing: get_typed_builtin(), get_typed_class_name(), get_typed_script(). The latter two are for Object-type classes and attached scripts respectively. So what was done in this PR is probably not enough.

_p->typed is the struct that contains all three. The three methods access that struct directly. Hence my feeling (comment) that... something along the lines of a method, say, returning true if all three are equal to another array's type may be beneficial.


Startup failure with pthread_create failed: Operation not permitted

Title: Startup failure with pthread_create failed: Operation not permitted
Description:
More of a help request - I'm attempting to upgrade an Envoy instance from 1.25.0 to 1.29.2 and finding that it now fails to start with an assert. Relevant long lines from latest main:
[2024-04-01 21:42:40.506][1][critical][backtrace] [./source/server/backtrace.h:112] Envoy version: 014a68f303074fb743b780548ac58d2e1340ec53/1.30.0-dev/Clean/RELEASE/BoringSSL
[2024-04-01 21:42:40.506][1][critical][backtrace] [./source/server/backtrace.h:127] Caught Segmentation fault, suspect faulting address 0x0
E0401 21:42:40.488786132       1 thd.cc:157]                           pthread_create failed: Operation not permitted
[2024-04-01 21:42:40.505][1][critical][assert] [source/common/common/posix/thread_impl.cc:147] assert failure: false. Details: Unable to create a thread with return code: 1
Our FatalActions triggered a fatal signal.

Note the ordering above is not necessarily correct due to logging infrastructure reasons.
Locally, with docker I do not get this issue, and also I don't get it in my CI infrastructure - only in an instance deployed to AWS ECS. Where might I start looking to diagnose this issue as I've come up empty trying to find similar situations encountering the same issue.
From what I can tell the return code 1 indicates an EPERM error, but I haven't change anything regarding permissions or the envoy user etc.
Also tried the latest main version to see if that helped but same result (slightly better error message as shown above)

@zakhenry I wasn't sure the reason, just some random thoughts, have you tried to run the privileged container? Maybe just check the container has enough permission first.

cc @phlax if he saw something similar in the CI job.

i didnt see this before - you definitely shouldnt require a privileged container (or any special caps)
it seems related to running with realtime scheduling
there is a similar discussion here https://stackoverflow.com/questions/9313428/getting-eperm-when-calling-pthread-create-for-sched-fifo-thread-as-root-on-lin
i would try running the binary directly (ie no container) on the problem platform and see what gives with that

Thanks for the ideas both, to update we managed to find a correlation for this issue which was that our version of docker in ECS was incompatible with envoy 1.29.0. For now we're pinning at 1.28.0 until we can upgrade our ECS AMIs


Editorial: Add note to ref to UTS35 about weekinfo

Address https://github.com/tc39/proposal-intl-locale-info/issues/30 by deferring to UTS35
and invalidate https://github.com/tc39/proposal-intl-locale-info/issues/85

Making sure I understand the broader matter correctly: the current wording will respect -u-ca, but because "rg" is not in [[RelevantExtensionKeys]], -u-rg will not be taken into account when determining the returned Record's value?
I wonder if this note on the whole might be clearer if the specific extensions that affect the Record's value were listed in the note,  and if it were explicitly stated that  https://www.unicode.org/reports/tr35/tr35-dates.html#first-day-overrides determines  which of the components of _locale_ have priority.

[[RelevantExtensionKeys]] for Intl.Locale doesn't have the same semantics as [[RelevantExtensionKeys]] for Intl service constructors. I guess it's now finally time to rename [[RelevantExtensionKeys]] for Intl.Locale → https://github.com/tc39/ecma402/pull/914.

My intention of this note is to delegate the whole algorithm to UTS35 instead of specify a half baked algorithm that we need to keep updating the algorithm if UTS35 change later.

UTS 35 has validity requirements which are not implemented in ICU4C.
Relevant specifications for rg and sd, including their validity requirements:

https://unicode.org/reports/tr35/tr35.html#RegionOverride
https://unicode.org/reports/tr35/tr35.html#UnicodeSubdivisionIdentifier
https://unicode.org/reports/tr35/tr35.html#Unicode_Subdivision_Codes
https://unicode.org/reports/tr35/tr35.html#Validity_Data

UTS 35 contains examples for validity checks in the "Unit preference overrides" section:

https://unicode.org/reports/tr35/tr35-info.html#Unit_Preferences_Overrides

Is it a normative requirement to implement the validity checks when referencing UTS 35's "First Day Overrides"?

Results for some locales and the returned week info objects from the V8 implementation:

Locale
Week Info
Correctness
Comment

en
{firstDay: 7, weekend: [6, 7], minimalDays: 1}
Correct
Missing region, add US per likely-subtags.

en-US
{firstDay: 7, weekend: [6, 7], minimalDays: 1}
Correct
Expected week info for US.

en-DE
{firstDay: 1, weekend: [6, 7], minimalDays: 4}
Correct
Expected week info for DE.

en-DE-u-rg-uszzzz
{firstDay: 7, weekend: [6, 7], minimalDays: 1}
Correct
Region override to use US.

en-DE-u-rg-aazzzz
{firstDay: 1, weekend: [6, 7], minimalDays: 1}
Incorrect
Region AA doesn't exist, so region override is invalid and should be ignored per UTS 35.

en-DE-u-rg-001zzz
{firstDay: 1, weekend: [6, 7], minimalDays: 1}
Incorrect
001 is a macro region, so region override is invalid and should be ignored per UTS 35.

UTS 35 has validity requirements which are not implemented in ICU4C.
Relevant specifications for rg and sd, including their validity requirements:

https://unicode.org/reports/tr35/tr35.html#RegionOverride
https://unicode.org/reports/tr35/tr35.html#UnicodeSubdivisionIdentifier
https://unicode.org/reports/tr35/tr35.html#Unicode_Subdivision_Codes
https://unicode.org/reports/tr35/tr35.html#Validity_Data

UTS 35 contains examples for validity checks in the "Unit preference overrides" section:

https://unicode.org/reports/tr35/tr35-info.html#Unit_Preferences_Overrides

Is it a normative requirement to implement the validity checks when referencing UTS 35's "First Day Overrides"?
Results for some locales and the returned week info objects from the V8 implementation:
Locale	Week Info	Correctness	Comment
en	{firstDay: 7, weekend: [6, 7], minimalDays: 1}	Correct	Missing region, add US per likely-subtags.
en-US	{firstDay: 7, weekend: [6, 7], minimalDays: 1}	Correct	Expected week info for US.
en-DE	{firstDay: 1, weekend: [6, 7], minimalDays: 4}	Correct	Expected week info for DE.
en-DE-u-rg-uszzzz	{firstDay: 7, weekend: [6, 7], minimalDays: 1}	Correct	Region override to use US.
en-DE-u-rg-aazzzz	{firstDay: 1, weekend: [6, 7], minimalDays: 1} Incorrect	Region AA doesn't exist, so region override is invalid and should be ignored per UTS 35.
en-DE-u-rg-001zzz	{firstDay: 1, weekend: [6, 7], minimalDays: 1} Incorrect	001 is a macro region, so region override is invalid and should be ignored per UTS 35.

v8 is on ICU 74-2 and not updated to ICU 75-1 yet. Some of the UTS35 is implemented in 75-1. I need to check are the two issues you mentioned due to 74-2 vs 75-1 or the trunk is not correct yet.

UTS 35 has validity requirements which are not implemented in ICU4C.

could you file an ICU ticket about what is missing? I am not quite sure I understand what is missing there now. Comparing the current v8 behavior is not a good idea since I added some of that latest UTS35 support into 75-1 but v8 is still on 74-2 so far.

Hmm, I just saw this in https://tc39.es/ecma402/#sec-language-tags (emphasis mine):

All structurally valid language tags are appropriate for use with the APIs defined by this specification, but implementations are not required to use Unicode Common Locale Data Repository (CLDR) data for validating them;

This looks like another problem when directly referencing to UTS 35 for week info processing, because UTS 35 does require validation. Maybe you can sidestep this issue by adding a note that validation as performed in UTS 35 is not required for ECMA-402?


'Customizing the JWT Generation' section is referred to the 200 doc space.

Description:
Customizing the JWT Generation in [1] is still referred to the contents in 200 doc space. Better to add relevant content under 2xx space
[1] https://docs.wso2.com/display/AM2xx/Extending+the+API+Manager

Fixed in the following pages.
[1] https://docs.wso2.com/display/AM2xx/Extending+the+API+Manager
[2] https://docs.wso2.com/display/AM210/Extending+the+API+Manager
[3] https://docs.wso2.com/display/AM220/Extending+the+API+Manager


Login attempt throws an error

To enable the AI features of Notty one needs to click the Menu button and then clock the login Google button. But that fails:

It's not clear to me if I have to make an edit to .env.example or to copy it to .env as documentation has yet to manifest, being early days for Notty.

Hi! Yes, you need to copy the .env.example into a .env file and get all the necessary tokens to make it work.


Donation: Gas price is too high for regular tx

Is that something that can be configured on an interface level? Why is it this expensive?

@patpedrosa creating a new stream should cost roughly 0.003 (650k gas * 5gwei gasPrice)

one-time send should be a regular "send' transaction on Celo

The donation seemed to expensive and it seems like the base cost is too high; @decentralauren will provide more info

https://github.com/GoodDollar/GoodWeb3-Mono/blob/master/packages/sdk-v2/src/sdk/base/hooks/useGasFees.ts
Maybe this can be used/is usefull from sdk-v2 package?
it enforces the baseGwei fee defined by celo protocol

@benefacto in the code where we do TXs it must be hardcoded with 5gwei cast costs.
either in each TX, or if a global setting is possible in whatever web3 framework is used.
see also lewis comment on how we created a hook that enforces that for the useDapp framework

@krisbitney
This one is still existing. suggested gwei from dapp is 10 gwei where 5 is sufficient

@krisbitney This one is still existing. suggested gwei from dapp is 10 gwei where 5 is sufficient

Got it. I had thought you guys wrote the @gooddollar/goodcollective-sdk package. I changed it there, but you may need to publish a new version on npm before the change is available in the app.

@krisbitney once https://github.com/GoodDollar/GoodCollective/pull/111/files is merged i'll trigger the publish

@krisbitney once https://github.com/GoodDollar/GoodCollective/pull/111/files is merged i'll trigger the publish

Awesome. Thanks.

goodcollective-sdk got released now, didn't really matter from what branch

https://github.com/GoodDollar/GoodCollective/pull/111/files

Amazing, thanks. And thank you for updating the branch.

verified


About Label Smoothing Regularization

I‘m wondering how Label Smoothing Regularization works，could you please release the code about that part？3Q

To know more details about the Label Smoothing Regularization, please refer the paper "Rethinking the Inception Architecture for Computer Vision".


Broken rendering of MC dialogs, introduced in 0.3.2

Versions of everything:

macos 10.14.5
tmux stable 2.9a (current latest from brew)
mc stable 4.8.22 (current latest from brew)

Configs:

alacritty config, mostly key bindings are modified: https://github.com/TheIndifferent/dotfiles/blob/master/macos/alacritty_and_tmux/.config/alacritty/alacritty.yml
tmux config, custom thingy to show current dir: https://github.com/TheIndifferent/dotfiles/blob/master/macos/alacritty_and_tmux/.tmux.conf
mc custom skin: https://github.com/TheIndifferent/dotfiles/tree/master/macos/alacritty_and_tmux/.config/mc

Steps to reproduce:

Upgrade Alacritty from 0.3.1 to 0.3.2.
Open Alacritty to full screen on 1920x1080 resolution.
Open mc and try to delete a file.
Renders correctly when resized to quarter or half screen.
When copying files, seems like there is a similar rendering issue but hard to catch because it goes with jumping mc progress bar.

Duplicate of https://github.com/jwilm/alacritty/issues/2217.

@chrisduerr the original issue is reported for version 0.2.7, but for me every version from 0.2.4 to 0.3.1 works perfectly fine (currently downgraded to 0.3.1 to workaround the issue) 🤔  can it be the same issue?

Oh, I linked the wrong issue, sorry. Changed it to https://github.com/jwilm/alacritty/issues/2353.

Yup, that one looks correct 😃  thanx! It's weird that right now I cannot reproduce it on 0.3.2 either, and the original issue is reported for 0.3.1, so it is probably correct.

The issue has to do with a cache filling, so it's tough to reliably reproduce it. However the latest master should fully fix it.


Moved padding-bottom to container so lists can't be horizontally scrolled

If the sidebar is narrower than the list of open files, the user could click and drag right on the padding-bottom beneath the working set to scroll the file names over. The user could not click and drag back though.
This fix puts the padding on the container instead, so the overflow has no effect.

@stowball I can't seem to reproduce the problem that this is fixing. Are you still seeing it? Can you add a screenshot or video?
Got any other details? Does it also require a vertical scrollbar? Which OS/version? Latest version of Brackets?

I'm having trouble recording a screencast of it, but I've just noticed that my fix breaks the .scroller-shadow bottom position as that's absolutely positioned

Managed to screencast the issue where you can drag the padding and scroll the file list out of view

seems useful to scroll ;) Reminds me of this.

Do you follow me on Twitter?! https://twitter.com/stowball/status/652247896432074752?s=09

Coincidence!


Update Porfolio with picture, facts, and paragraph

This is just a preliminary request to ensure that I am doing all of this right!

This is just a preliminary request to ensure that I am doing all of this right!

Final change was made! I think I am done, at least for now!

Final version of my portfolio! https://aashby-sps-summer20.uc.r.appspot.com/ - that's the link to it!

Great!  Hey! I'm also a Rewriting the Code Fellow.

Great! Hey! I'm also a Rewriting the Code Fellow.

 That is so cool!


Combine ERA5 and ERA5T data

Closes #190.
Change proposed in this Pull Request

Description
Requesting cutout data spanning recent (ERA5T) and data older than ~3 months (ERA5) results in an additional dimension in cutout.data, called expver, which atlite currently cannot handle gracefully.
This change collapses the two dimensions into a single dimension.
Motivation and Context
See details in #190.
How Has This Been Tested?
The first commit of this pull request introduces a failing test that demonstrates the bug. The second commit fixes the bug and makes the failing test pass.
IMPORTANT: the test introduced in the first commit should not be merged into master. The test data is time-dependent. Data which is ERA5T today will become ERA5 in the future. I only added the test for illustration. See the discussion in this pull request for alternative test proposals.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] I tested my contribution locally and it seems to work fine.
[x] I locally ran pytest inside the repository and no unexpected problems came up.
[x] I have adjusted the docstrings in the code appropriately.
[ ] I have documented the effects of my code changes in the documentation doc/.
[x] I have added newly introduced dependencies to environment.yaml file.
[ ] I have added a note to release notes doc/release_notes.rst.
[x] I have used pre-commit run --all to lint/format/check my contribution

IMPORTANT: the test introduced in the first commit should not be merged into master. The test data is time-dependent. Data which is ERA5T today will become ERA5 in the future. I only added the test for illustration. See the discussion in this pull request for alternative test proposals.

@FabianHofmann This fix is addressing a "moving target" bug. The test case in the first commit spans September and October 2022, where the CDSAPI currently returns ERA5 data for September, and ERA5T data for October, but this will shift in December (source).
In order to make this a stable test - we could keep the downloaded response data from CDSAPI in a file, and have the retrieve_data function load the request from file if the file is available. This would require another code change though. I made a dirty version of this solution in https://github.com/PyPSA/atlite/compare/master...zoltanmaric:atlite:reuse-downloaded-era5-files
I think this loading from file would be a useful feature anyway to prevent having to redownload large requests from the CDSAPI when debugging the building of cutouts.

Thanks @zoltanmaric, always a pleasure to see contributions from you (sorry I am not so responsive at the atlite repo lately).  This looks very sensible.

@zoltanmaric sorry again that I am so slow here. Looks awesome!


Evaluate model given dumped data

Add in the dumped data (or model generated outputs of the same format as the dumped data) in a folder called model_output in src/
Then run evaluate_model.py
@danyaljj

Thanks! I am assuming gpt/field-dist.png is added by mistake?

Thanks! I am assuming gpt/field-dist.png is added by mistake?

Added it in as an example of how to send a GPT request by local image! Used as a reference for the future


Refactor to add QCMetric class and list of URLs for reference images/figures

Added quality_control.Stage per discussion, and modified examples to better reflect our concept. Also added name to QCEvaluation and made descriptions optional, to separate stage/name/desc from each other.


Added MessageCollector

Basically a broader and more useful Prompt.
Changes have been made since PR #20.

Updated to include the actual utlity file, and example file that i forgot.


Release annotations for Application Insights - PowerShell script fails parsing

Hello!
I'm trying to implement the "Release annotations for Application Insights" (task version is 2.*), but unfortunately the Inline Script is failing some parsing during execution. I've set the Script Type to PowerShell as indicated in the documentation, copied the contents of CreateReleaseAnnotation.ps1. The logs point to the following:
2021-06-10T12:22:45.6499536Z At D:\a\_temp\azureclitaskscript1623327739627_inlinescript.ps1:1 char:7
2021-06-10T12:22:45.6522425Z + param(
2021-06-10T12:22:45.6542045Z +       ~
2021-06-10T12:22:45.6546159Z Missing ')' in function parameter list.
2021-06-10T12:22:45.6547602Z At D:\a\_temp\azureclitaskscript1623327739627_inlinescript.ps1:9 char:1
2021-06-10T12:22:45.6548543Z + )
2021-06-10T12:22:45.6549240Z + ~
2021-06-10T12:22:45.6549922Z Unexpected token ')' in expression or statement.
2021-06-10T12:22:45.6550728Z At D:\a\_temp\azureclitaskscript1623327739627_inlinescript.ps1:13 char:2
2021-06-10T12:22:45.6632911Z + â€¯â€¯â€¯ Id = [GUID]::NewGuid();
2021-06-10T12:22:45.6633919Z +  ~
2021-06-10T12:22:45.6634392Z Missing '=' operator after key in hash literal.
2021-06-10T12:22:45.6635148Z At D:\a\_temp\azureclitaskscript1623327739627_inlinescript.ps1:27 char:3
2021-06-10T12:22:45.6635870Z + az rest --method put --uri "$($aiResourceId)/Annotations?api-version= ...
2021-06-10T12:22:45.6636339Z +   ~
2021-06-10T12:22:45.6637593Z Missing '=' operator after key in hash literal.
2021-06-10T12:22:45.6638288Z At D:\a\_temp\azureclitaskscript1623327739627_inlinescript.ps1:27 char:3
2021-06-10T12:22:45.6638859Z + az rest --method put --uri "$($aiResourceId)/Annotations?api-version= ...
2021-06-10T12:22:45.6639244Z +   ~
2021-06-10T12:22:45.6639574Z The hash literal was incomplete.
2021-06-10T12:22:45.6640072Z     + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
2021-06-10T12:22:45.6640648Z     + FullyQualifiedErrorId : MissingEndParenthesisInFunctionParameterList
2021-06-10T12:22:45.6641053Z
2021-06-10T12:22:45.6955238Z ##[error]Script failed with exit code: 1

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

ID: ee1eec15-6783-f8a2-81c0-ffa9d1b40dc2
Version Independent ID: ab875981-7b0d-95be-dc5b-91f87acbe477
Content: Release annotations for Application Insights - Azure Monitor
Content Source: articles/azure-monitor/app/annotations.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @lgayhardt
Microsoft Alias: lagayhar

I have removed some extra lines and white spaces from the script and it now works!
It looks like that now:
param([parameter(Mandatory = $true)][string]$aiResourceId, [parameter(Mandatory = $true)][string]$releaseName, [parameter(Mandatory = $false)]$releaseProperties = @())

$annotation = @{Id = [GUID]::NewGuid(); AnnotationName = $releaseName; EventTime = (Get-Date).ToUniversalTime().GetDateTimeFormats("s")[0]; Category = "Deployment"; Properties = ConvertTo-Json $releaseProperties -Compress}

$body = (ConvertTo-Json $annotation -Compress) -replace '(\\+)"', '$1$1"' -replace "`"", "`"`""

az rest --method put --uri "$($aiResourceId)/Annotations?api-version=2015-05-01" --body "$($body) "

@wagnerbsouza I'm running into the same problem here, thanks for sharing your updated script. Where did you get the value for the $aiResourceId parameter?

Hey, you’re welcome!
The aiResourceId comes from the Application Insights in Azure Portal.
Once you’re in its “Overview”, click on “JSON view” on top right of it (right above the “Instrumentation Key”).
The first key in the JSON is “id”. That’s the value you want for your aiResourceId.
From: Dan @.>
Sent: Thursday, 10 June 2021 17.32
To: MicrosoftDocs/azure-docs @.>
Cc: Wagner Souza @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Release annotations for Application Insights - PowerShell script fails parsing (#76735)
@wagnerbsouzahttps://github.com/wagnerbsouza I'm running into the same problem here, thanks for sharing your updated script. Where did you get the value for the $aiResourceId parameter?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/76735#issuecomment-858723388, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALZPBFUAO4XRHIAB45XTV73TSDLH5ANCNFSM46OOHGWQ.

Hi @wagnerbsouza thank you for bring this to our attention.  One of our community members submitted a public PR to fix the spacing issue. The changes should go live today or tomorrow.
Thank you!
#please-close


Raise a warning if sequence count is non-consecutive

To let the user know if the packet sequence count in the primary header skips a number which would imply that a packet was lost. The sequence count is per APID therefore they would have to be checked individually.

Sounds reasonable. We might make this an option set to True by default, eg warning_on_missing_packet=True. We may also consider making our subclasses of warning, eg CCSDSPyWarning -> ParsingWarning -> MissingPacketWarning or something like that

Depends on #15

@ddasilva this can be closed.


[Snyk] Fix for 1 vulnerabilities

Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json
yarn.lock

Adding or updating a Snyk policy (.snyk) file; this file is required in order to apply Snyk vulnerability patches.
Find out more.

Vulnerabilities that will be fixed
With a Snyk patch:

Severity
Priority Score (*)
Issue
Exploit Maturity

636/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 6.3
Prototype Pollution  SNYK-JS-LODASH-567746
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Old


Clarify bulk user download limit

This section:
Each bulk activity to create a list of users can run for up to one hour. This enables creation and download of a list of at least 500,000 users.
Should instead read:
Each bulk activity to create a list of users can run for up to one hour. This enables creation and download of a list of up to 500,000 users.

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

ID: 7800fcb4-d251-f271-bc12-9377cd0407fa
Version Independent ID: 319b62fc-cea7-1add-559b-bb2a35b3a0ad
Content: Download a list of users in the Azure Active Directory portal
Content Source: articles/active-directory/enterprise-users/users-bulk-download.md
Service: active-directory
Sub-service: enterprise-users
GitHub Login: @curtand
Microsoft Alias: curtand

@berberich
Thanks for your feedback! We will investigate and update as appropriate.

Thanks for the discussion around this, @berberich. @curtand, this has been confirmed with the PG.
I made a pull request to update the doc and will sign off once the build has completed. https://github.com/MicrosoftDocs/azure-docs-pr/pull/156068


Having trouble compiling

Getting the following errors when attempting to compile...
Arduino: 1.8.13 (Linux), Board: "TTGO T-Watch, Enabled, Default (2 x 6.5 MB app, 3.6 MB SPIFFS), 2000000, None"

sketch/SPIFF_fns.cpp: In function 'void build_acc_pts_file()':
SPIFF_fns.cpp:189:25: error: 'sizeof_Access_Points' was not declared in this scope
     for(int i = 0 ; i < sizeof_Access_Points ; i++) {
                         ^
sketch/SPIFF_fns.cpp: In function 'int read_acc_pts_file_and_compare_with_SSIDs(WiFiAp*)':
SPIFF_fns.cpp:230:27: error: 'number_of_networks' was not declared in this scope
       for (int i = 0; i < number_of_networks; ++i) {
                           ^
Multiple libraries were found for "WiFi.h"
 Used: /home/XXXX/.arduino15/packages/esp32/hardware/esp32/1.0.4/libraries/WiFi
 Not used: /opt/arduino-1.8.13/libraries/WiFi
Multiple libraries were found for "SD.h"
 Used: /home/XXXX/.arduino15/packages/esp32/hardware/esp32/1.0.4/libraries/SD
 Not used: /opt/arduino-1.8.13/libraries/SD
exit status 1
'sizeof_Access_Points' was not declared in this scope

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

fixed.  I have to keep two versions of the file, one for me,
one for the rest of the world.  I didn't keep the second
one updated.

Thanks!  I had the same issue when starting to play with this.


Installing instructlab installs CUDA dependencies

Describe the bug
The doc mentions that to install with CPU support pip install instructab but it also installs the CUDA dependencies
To Reproduce
Steps to reproduce the behavior:

Create an empty virtual env and activate it
pip install instructlab

Expected behavior
No CUDA dependencies installed
Screenshots

Device Info (please complete the following information):

Hardware Specs: Win11PRo
OS Version: Win11Pro
Python Version: 3.11
InstructLab Version: ??

Additional context

What dependencies are you referring to exactly?

nvidia- dependencies (lots of) and torchaudio (2.5.1+cu121)


[v0.3] Set no sigopt as default

remove --no_sigopt option and add --enable_sigopt option
sigopt is disabled by default

Completed and ready for merge. @xuechendi


Update README.md

I added some clarifications regarding installation instructions related to changes in #53

Looks great, thank you!


TypeError: cannot unpack non-iterable numpy.float32 object

Keep getting this error when pointing my camera on anything (I guess this is when line detection algorithm is triggered)
Exception in Tkinter callback
Traceback (most recent call last):
  File "tkinter\__init__.py", line 1948, in __call__
  File "tkinter\__init__.py", line 861, in callit
  File "app\app.py", line 477, in show_frame
  File "app\app.py", line 459, in capture
  File "camscan\scanner.py", line 488, in main
  File "camscan\scanner.py", line 58, in draw_hough_lines
TypeError: cannot unpack non-iterable numpy.float32 object

Thanks for pointing out! This is fixed in the following commit:
https://github.com/suhren/camscan/commit/ec55beb645966a28b20eab443e60e3c74b55e9d6


Remove extended profile section, revise discovery

This PR removes the Extended Profile section, which has become redundant after the addition of the new Reading & Writing sections.
It also includes a revision of the Discovery section to remove redundant information and make it  a bit more succinct.
Closes #102 , #57

HTML Preview | HTML Diff


pcsx2: darwin app, add maintainer

Description of changes

Split the package in linux.nix and darwin.nix
darwin.nix fetches the pre-compiled binaries from GitHub

Tried to compile this but fails on aarch64-darwin, requires a x86_64-darwin machine
The pre-compiled app runs fine under Rosetta, the version is in sync with the Linux one

The three files have been formatted with nixfmt-rfc-style.
Added myself as maintainer for Darwin

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[X] Fits CONTRIBUTING.md.

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4127

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4132

Result of nixpkgs-review pr 320122 run on aarch64-darwin 1

1 package built:

pcsx2

The app requires Rosetta to run, how could this dependency be declared in nixpkgs in general to differentiate between packages that run natively on Apple Silicon and packages needing Rosetta?

@afh That's a good point - my gut tells me this should only be declared as a x86_64-darwin, and then aarch64-darwin can download this anyway by using Nix config / extra platforms.
@NixOS/darwin-maintainers thoughts on this?

FYI, upstream is working on natively supporting ARM.
https://github.com/PCSX2/pcsx2/pull/11364

That's a good point - my gut tells me this should only be declared as a x86_64-darwin derivation, and then aarch64-darwin can download this anyway by using Nix config / extra platforms.

I agree. There’s nothing about this app that is aarch64-darwin (currently); it just so happens that all aarch64-darwin machines support software that lets them run x86_64-darwin software.

@SuperSamus @afh @emilazy Thanks for the feedback, I'm going to change the derivation and make it natively compile for x86_64-darwin, so it's ready for when aarch64-darwin support will be officially released.

@emilazy hit a roadblock, got most of the project to compile, but it fails when trying to compile Metal shaders, as that would require the host's xcrun and Xcode.
What's the best way forward here?

Using tools on the host would be tricky, i.e. it will depend on Xcode - lot of impurity.
I could patch the app so the shaders are not compiled, just copied over, but then I would have to change the renderer pipeline, so those are compiled at runtime instead. Not impossible but this would be highly time consuming. Also we don't know for how long this will work and might require constant maintenance over time.
Not a big fan of this idea: fetch the binary dist from Github regardless, and copy over the pre-compiled *.metallib files to the final app bundle
We could just stick to the binary distribution as a temporary solution, and think how to bring Metal shader compiling into the packaging pipeline, so other derivations can benefit from it too, and revisit this at a later stage.

Pinging also @NixOS/darwin-maintainers, any input will be greatly appreciated.

@emilazy @afh reverted this PR to its previous status.
As stated in https://github.com/NixOS/nixpkgs/pull/320122#issuecomment-2185396923, some thinking is required to bring Metal shaders into the pipeline.
I don't thinks there's an immediate / obvious solution to this, so I suggest to go with option (4) from the previous comment, rather than having no Darwin support at all.
I'll bring this topic up on Matrix when I got some time 👍🏻


Consume a Basic OData Service

Hi,
I wonder the tutorial starting with an project that already exits. Cound you please tell me the Prerequisites?
When I click on Prerequisites > this has also a Prerequisites > an so on and so on with prerequisites.
Could you please state the preceeding tutorial? What kind of projekt do I have to set up?
Many thanks
Regards
Mario

Thank you for your feedback. We haven't heard from you in the past 30 days, so we are closing the issue.
If you still have questions, feel free to reopen the issue.


Cannot run parallel jobs in the UI

Bug description 🐞
When a run is already pending/running, starting a new job via the UI will result in a 403 error in the console.

Steps to reproduce

Run a job
While the job is running, running another one via the UI via the 'Start a new job' modal

Expected behavior
Ideally, queue the next run. Otherwise, provide an error in the UI that a job is already running
Example repository
No response
Anything else?
I am evaluating terrakube via the minikube helm deployment.

This can be change. It will only happen when you are using the UI, if you trigger the job using the CLI driven workflow or using a push to the repository it will create a queue of jobs internally

I will fix this one for 2.20.1

I created the release that fixes this issue.
https://github.com/AzBuilder/terrakube/releases/tag/2.20.1

I can confirm it works


Some marker events are missing

The Marker component does not emit the following events:

contextmenu
mouseout

Added in v0.6.0.

Added in v0.6.0.


Add filter to UI so user can select specific data

Tracked by #15

Learned about react and put in a skeleton for the checkboxes.
{t:75}

Added checkboxes with tooltips to complete the task.
{t:90}