Update release version.

Codecov Report

Merging #1750 into master will decrease coverage by 0.13%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1750      +/-   ##
============================================
- Coverage     82.19%   82.05%   -0.14%
+ Complexity     1966     1946      -20
============================================
  Files           291      288       -3
  Lines          9142     9010     -132
  Branches        877      862      -15
============================================
- Hits           7514     7393     -121
+ Misses         1333     1329       -4
+ Partials        295      288       -7

Impacted Files
Coverage Δ
Complexity Δ

...us/contrib/resource/util/K8sContainerResource.java

.../contrib/resource/util/AwsEc2InstanceResource.java

.../contrib/resource/util/GcpGceInstanceResource.java

...ensus/contrib/resource/util/GcpMetadataConfig.java

...ncensus/contrib/dropwizard5/DropWizardMetrics.java

...sus/contrib/resource/util/AwsIdentityDocUtils.java

...pencensus/contrib/dropwizard5/DropWizardUtils.java

...pencensus/contrib/resource/util/ResourceUtils.java

...monitoredresource/util/AwsEc2InstanceResource.java
91.66% <0%> (ø)
2% <0%> (?)

...ib/monitoredresource/util/AwsIdentityDocUtils.java
58.33% <0%> (ø)
8% <0%> (?)

... and 6 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 0f9898c...975674f. Read the comment docs.

Please resolve the conflict (mostly the monitored-resource-util) has been marked as deprecated so just ignore that readme update.


New update Instagram on Story Link Stickers

Hey guys 👋
If you don't know Instagram did an update on link in stories, they are now stickers.
So instead of having a bottom link now they have the 'story_link_stickers'.
Basically now it looks like :

For my code it's important to get the links of the story.
Before we we using this query:
L.context.graphql_query("bf41e22b1c4ba4c9f31b844ebb7d9056",{"reel_ids": _50influ_ids, "precomposed_overlay": False})
In the response : data.reels_media[].items[].story_cta_url we got the link to a promoted website.
But now they use the stickers. Which can be found in data.reels_media[].items[].tappable_objects[].
The issue with this is that there are no links but only the @mention of the page.
"tappable_objects": [
  {
      "__typename": "GraphTappableMention",
      "x": 0.290607316864677,
      "y": 0.07670205432594801,
      "width": 0.345439537370406,
      "height": 0.033316492385728,
      "rotation": -0.018403547785067,
      "custom_title": null,
      "attribution": null,
      "username": "pinupsecretparis",
      "full_name": "Pin Up Secret",
      "is_private": false
  }
]

After some research, I've found a way to get the links in the stickers using this query:
https://i.instagram.com/api/v1/feed/reels_media/?reel_ids=643876791
In reels_media[].items[].story_link_stickersHere I have the story link
"story_link_stickers": [
  {
      "x": 0.7727234451307351,
      "y": 0.93278627378107,
      "z": 0,
      "width": 0.313277271838977,
      "height": 0.031720795736375006,
      "rotation": -0.034307130117797,
      "is_pinned": 0,
      "is_hidden": 0,
      "is_sticker": 1,
      "is_fb_sticker": 0,
      "story_link": {
          "link_type": "web",
          "url": "https://l.instagram.com/?u=https%3A%2F%2Fwww.pinup-secret.fr%2F&e=ATOzY4ZjNiL14yFe_EgYOqsUuXbBbckLQfohXgu5NgwnbP9vPzvajpej7zOTZulFJHMIWTygt6nJje3fIatXkCs&s=1",
          "link_title": "Visit Link"
      }
  }
]

Now that I know we can get the links from the stickers using a different endpoint, I would like to keep using this method L.context.graphql_query("bf41e22b1c4ba4c9f31b844ebb7d9056",{"reel_ids": _50influ_ids, "precomposed_overlay": False})
And show the new sticker links 🚀
How can I show the story_link_stickers.story_link data ? Maybe it's a variable I need to pass to the query, like show_stickers ?
But I don't know where to get the list of possible variables...
Anyone could help me ?
Thank ❤

In which way are performing the https://i.instagram.com/api/v1/feed/reels_media/?reel_ids=643876791 query?
I have tried:
L.context.get_iphone_json('api/v1/feed/reels_media/', params={'reel_ids': '{reel_id}'})

And:
L.context.get_iphone_json('api/v1/media/{media_id}/info/', params={})

In both instances, the story_link_stickers property is omitted, even though when I inspect the same queries in the Instagram Web app in the browser, this property is available.
Ideally, this data should be available when using the .get_stories() method, but for now if you could share your workaround that would be most helpful.

For now I've used an HTTP call https://i.instagram.com/api/v1/feed/reels_media/?reel_ids=643876791
In which the story_link_stickers is here.
Waiting for a solution with instaloader

Hey @berthelol How can you find reel_id? Is this endpoint just working for stories? Its look like only work with reels media.

Hey @akasaa101
reel_id is the instagram id of the user (pk)
You can get it using theses:
https://instagram.com/zoebassetto/?__a=1
or the sdk of instaloader ;)
This endpoint is working for stories, I haven't really check anything else tbh :)


This line code confused me.

https://github.com/url-kaist/patchwork-plusplus/blob/0d430884cbea4c3cfa009cf99a46c4f04ae964e2/patchworkpp/src/patchworkpp.cpp#L97
In my opinion, i should begin with 'init_idx'?

Hi, @Shaoqing26. Thanks for sharing your opinion.
Actually, your opinion makes sense since we find the init_idx value to remove the noises.
The code, which finds the init_idx value, prevents the noise from being selected as the 'lowest point representative(LPR)' by the threshold of  params_.adaptive_seed_selection_margin * params_.sensor_height. Because the average height of LPR is used to calculate the height threshold of initial seed points(lpr_height + params_.th_seeds), LPR should exclude the noise points which have unrealistically low heights.
However, when we select the initial seed points, it is necessary to include every point with a lower height than the lpr_height + params_.th_seeds by beginning the for loop with 0. This is because the ground points can still exist under the params_.adaptive_seed_selection_margin * params_.sensor_height due to the slope of the ground. As you pointed out, the noise points can be included in the initial seed points at this moment.
By the way, to handle the problem of noises, Patchwork++ presents a new module called Reflected Noise Removal(RNR). Moreover, as there is another step for the ground points extraction using PCA, I guess this part will not affect the final ground estimation result severely whether the for loop begins with 0 or init_idx.
I will check the potential problem of this part. Thank you :)


Add GitHub to supporting companies

Missing the logo file?

I probably messed up this change with the tweaks I did in the other PR (in case that gets merged first), as I formatted the lines. It might still merge ok though - the only real difference is formatting.

https://github.com/MobileNativeFoundation/mobilenativefoundation.org/pull/11


[bugfix] Remove shift for options without arguments.

By using shift in a while loop with options that have no arguments (ie: -d  -a) it is possible for Lambo to skip an option. Example:
lambo project-name -a -d -e atom

This would run only --auth and --editor options and skip the --develop option.

Geez, nice catch. Thanks!


Is it possible to get an alphanumeric keyboard for  on Z10?

Currently if I specify <input type="text" id="fieldName"  />, I will get the virtual alpha keyboard on the Z10.
This is a slight UI annoyance if you are asking your client to enter a confirmation number or postal code which require alphanumeric.  BB has the alphanumeric keyboard (password entry), but I'm at a loss as to how to trigger it from bbUI.js.  My dev contact at BB was also at a loss.
I also posted on SO, no response:
http://stackoverflow.com/questions/16202647/how-to-get-alphanumeric-keyboard-on-input-in-html5-bbui-js-for-blackberry-10

I just updated my Blackberry z10 to the latest bb OS 10.3.1 - works great - except one major problem! I can't use alphanumeric password feature and I cannot disable the STUPID buggy bs Simple Password! Good Job moronic Devs at BB! You call this improvement! Anyone know if there is any fix to this annoying retarded issue that makes zero sense as to why I cannot even disable Simple Password and not able to use Alphanumeric on the new BB OS 10.3.1? Any help would be greatly appreciated. Sorry for the bother but only if Devs were more responsible before putting out buggy-ass time wasting updates that cause more problems then the "improvements" they offer. If all else fails I will simple go back to the old BB OS. Unreal. Ty all for taking the time. Cheers!

@jny01 Nice bump bro!


[FR] Update blank to LLM Content instead of string?

When we create a new board we have input.text -> output.text, and both ports are strings. It seems the first move we tend to make is to convert from string to Object => LLM Content. What if we update the blank.ts to use the following for its configuration:
{
    schema: {
      properties: {
        content: {
          type: "object",
          title: "Content",
          examples: [],
          behavior: ["llm-content"],
          default:
            type === "input" ? '{"role":"user","parts":[{"text":""}]}' : "null",
        },
      },
      type: "object",
      required: [],
    },
  }

Or we could make a second blank-llm.ts template?

I really like this idea. Let's do this.


Rewriting Paths with TCP Mode (proxyfing swarm vizualizer service)

Hello,
I'm trying to proxyfi the swarm vizualiser service
My DF label conf
This is the label I uses I want to rewrite path because the visualizer service listen on '/', and it works on tcp
      labels:
        - com.df.notify=true
        - com.df.distribute=true
#        - com.df.servicePath=/visu/
        - com.df.reqMode=tcp
        - com.df.reqPathSearch=/visu/
        - com.df.reqPathReplace=/
        - com.df.port=8080
        - com.df.srcPort=8080

Perhaps it's not possible to rewrite url in TCP mode..
For now I've got an Error
proxy_proxy.1.9c5szn2bin7u@node1    | backend visu_visu-be8080
proxy_proxy.1.9c5szn2bin7u@node1    |     mode tcp
proxy_proxy.1.9c5szn2bin7u@node1    |     http-request set-path %!
proxy_proxy.1.9c5szn2bin7u@node1    | (BADINDEX)    server visu_visu visu_visu:8080

The output of the configuration gives me
...
backend visu_visu-be8080
    mode tcp
    http-request set-path %[path,regsub(/visu/,/)]
    server visu_visu visu_visu:8080

I reproduce it on play-with-docker
docker swarm init --advertise-addr $(hostname -i)

Create proxy
git clone https://gist.github.com/3b54d37fd85e39cbafa546f6f99c616b.git
docker stack deploy proxy --compose-file 3b54d37fd85e39cbafa546f6f99c616b/proxy-flow.yml

Create Service
git clone https://gist.github.com/d2d3fb5587629e49c9acb28b994c1638.git
docker stack deploy visu --compose-file d2d3fb5587629e49c9acb28b994c1638/vizualizer.yml

It deploy the service so that we can access-it on the port 81 http://ip10_0_2_3-81.play-with-docker.com/ >(Change IP according to your setup)
I want also to access it throug the proxy :
http://ip10_0_2_3-80.play-with-docker.com/visu/

(Change IP according to your setup)

Check the configuration
curl http://localhost:8080/v1/docker-flow-proxy/config

There are two problems with the labels you set. The first one is that reqPath should not end with /.  It should be:
        - com.df.servicePath=/visu
        - com.df.reqPathSearch=/visu
        - com.df.reqPathReplace=/

However, that's not a real problem. The issue is that Mano used absolute instead relative paths in his client requests. So, even though the UI now opens through /visu, it continues making requests thinking as if it's root. If you inspect it in Chrome console, you'll requests like /apis/nodes. The are only two solutions I can think of.

Change the code of the visualizer so that it uses relative path (e.g. apis/nodesinstead /apis/nodes). Make a pull request.
Use / as servicePath and add serviceDomain as, for example, visu.acme.com.

@allamand Please let me know if the ticket can be closed or you have a follow-up question.

Closing the ticket due to inactivity. Feel free to reopen.


Batch remove action snapshots

What
This commit changes the way action snapshots are removed such that they are deleted in bulk. Additionally it moves the archive process to after the release process ends, preventing archiving from running multiple times between a release.
It also removes the BIRTH action, which was included to ensure that an action always had a parent. We don't need this. The only time an action will not have a parent is during START.
Why
Mostly just a performance optimization that was uncovered with #438

Fixes #440

Codecov Report

Merging #440 into no-append will decrease coverage by 0.6%.
The diff coverage is 100%.

@@              Coverage Diff              @@
##           no-append     #440      +/-   ##
=============================================
- Coverage      77.23%   76.63%   -0.61%
=============================================
  Files             44       44
  Lines           1362     1374      +12
  Branches         251      256       +5
=============================================
+ Hits            1052     1053       +1
- Misses           257      263       +6
- Partials          53       58       +5

Impacted Files
Coverage Δ

packages/microcosm/src/lifecycle.js
100% <ø> (ø)
:arrow_up:

packages/microcosm/src/action.js
100% <100%> (ø)
:arrow_up:

packages/microcosm/src/history.js
100% <100%> (ø)
:arrow_up:

packages/microcosm/src/utils.js
100% <100%> (ø)
:arrow_up:

packages/microcosm/src/microcosm.js
100% <100%> (ø)
:arrow_up:

packages/microcosm/src/addons/action-button.js
0% <0%> (-100%)
:arrow_down:

packages/microcosm/src/addons/action-queue.js
0% <0%> (-100%)
:arrow_down:

packages/microcosm/src/addons/action-form.js
97.61% <0%> (+97.61%)
:arrow_up:

Continue to review full report at Codecov.

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

@efatsi I'm going to close this one out. I have some changes to history that invalidate this in some upcoming work. Will post soon :)


Added Vedant to the List

What changes does this PR do?

Adds my name into the README.md file

Screenshots (If any)

Actually a minor blunder happen while raising this PR hence the above mess, but I have raised another PR with proper formatting.


Incompatible Version.

The recent update does not allow for v1.1.1 [Incompatible version] with the BepinEx v5.4.2202

it should. you probably instead got the error that the server is still running version 1.1.0 and needs to be updated


./mixed-content-scan --no-check-certificate does not work

Hi,
I have installed the latest ./mixed-content-scan and when I try to scan the website as:
./mixed-content-scan --no-check-certificate https://mysite.com
It throws Scan options and returns to prompt without checking anything

I think you just need to put the option before the argument, thus:
mixed-content-scan https://mysite.com --no-check-certificate


docs(progress-bar): update docs and deprecate for removal

Signed-off-by: Matt Hippely<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[x] If applicable, have a visual design approval

@colinreedmiller - I'll add a link in the comments when the preview is built.
PR Type
What kind of change does this PR introduce?
Deprecates parts of the ClrProgressBar api.
Adds a new style for user defined style (color)
Updates the documentation recommendations and examples for both colors and variations.

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Documentation content changes
[ ] clarity.design website / infrastructure changes
[x] Other... Please describe:
This also adds a scss variable and class for a user defined progress color $clr-progress-user-color.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@colinreedmiller - here is the links to the preview: https://deploy-preview-3831--vmware-clarity.netlify.com/documentation/progress

@clane and @colinreedmiller - please take a look at the updated docs page for progress bar. It includes the changes requested by Colin and a re-organized layout that uses the newer layout to structure the content.
https://deploy-preview-3831--vmware-clarity.netlify.com/documentation/progress
Please take a look at the following sections

Accessibility
Color
Variations

Looks good but I think there is a typo at "An option percentage label ". I should say "optional".

This doesn't appear to be a backport, it should only go into master since we'll be deprecating it as of 3

Regarding the statement "An optional percentage label can be included after the progress bar as needed" we should also mention that this additional percentage label has to be programmatically associated with the progress bar it is representing. This can be done by passing multiple id property references to aria-labelledby. Additionally, our example that demonstrates having two labels for a progress bar should actually have two visual/programmatic labels as it currently does not.  I recommend to follow the example below.

Container 1 loading Progress

<progress aria-labelledby="containerloadingProgressLabel1 containerloadingProgressLabel2"  max="100" value="65" data-displayval="65%"></progress>
65%

Just realized that the screen reader user may hear "65%" before they actually read progress bar and its labels due to the live region. Since the screen reader user may hear "65%" out of context, can we make this  message more complete?
Container 1 Loading Progress is65%


Issue with date/time/log format for custom logs

Hi!
I do have a custom log file with the following:
<IP_ADDRESS> - - [Wed, 15 Sep 2021 09:59:09 GMT] "GET /some/url/home.html HTTP/1.1" 200 70749 "-" "Amazon CloudFront"
Having difficulties to set appropriate parameters in date/time/log format.
Changed combined  date format to following:
%a, %d %b %Y
But still unable to parse.
Any hints on this one?

This should work:
goaccess access.log --log-format='%h %^[%d %t %^] "%r" %s %b "%R" "%u"' --date-format='%a, %d %b %Y' --time-format=%T


[Awesome-React-Components ] -> [React UI Libraries]

[Awesome-React-Components
] -> [React UI Libraries]
Resource Name - Awesome-React-Components
Absolutely Awesome React Components & Libraries
Link: https://github.com/brillout/awesome-react-components
Checklist:

[x] I have performed a self-review of submitted resource and its follows the guidelines of the project.

To general resource to add to this list.


Fixed bug in comparison at AbstractTableGateway->executeInsert

When executeInsert is called, sometimes $insertState['table'] is string or Zend\Db\Sql\TableIdentifier, that also happens with $this->table.
I got to a case that $insertState['table'] is string and $this->table is Zend\Db\Sql\TableIdentifier and that isn't mapped so a Exception is always thrown.
Example:

$tableGateway = new \Zend\Db\TableGateway\TableGateway('table1', $dbAdapter);
$sql                  = new \Zend\Db\Sql\Sql($dbAdapter);
// Prepare a insert with select
$select = $sql->select('any_table');
$select->columns(array('column1', 'column2'));
$select->where('status' => 'active');
$insert = $sql->insert('table1');
$insert->columns(array('column1', 'column2'));
$insert->values($select); //could be $insert->select($select) too
$tableGateway->insertWith($insert); // this will call AbstractTableGateway->executeInsert

@edsonhoraciojunior  Could you add unit-test ?

I'd like to schedule this for 2.4, but I need a test case, @edsonhoraciojunior

This issue has been moved from the zendframework repository as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html
New issue can be found at: https://github.com/zendframework/zend-db/issues/138


Deconz uses the default ssl port 443 for websockets but doesn't provide an ssl certificate

Why not expose websockets on the normal webserver port instead of causing conflicts?

It's docker. You can change the port yourself

You can change the port to whatever you like and this is not an issue specifically with the Docker image. Closing.


Select Out of Bounds Warning in SystemVerilog Plugin

This might be unrelated to Surelog/UHDM, but the plugin emits warning on the following snippet of SV.
module top(a, s ,z);
  input [4:0] a;
  input [1:0] s;
  output [7:0] z;

  shift inst(.a(a),.s(s),.z(z));
endmodule

module shift(a,s,z);
  parameter    width_a = 4;
  parameter    signd_a = 1;
  parameter    width_s = 2;
  parameter    width_z = 8;

  input [width_a-1:0] a;
  input [width_s-1:0] s;
  output [width_z -1:0] z;

  generate if ( signd_a )
  begin: SGNED
    assign z = fshl_s(a,s,a[width_a-1]);
  end
  else
  begin: UNSGNED
    assign z = fshl_s(a,s,1'b0);
  end
  endgenerate

  function [width_z-1:0] fshl_u_1;
     input [width_a  :0] arg1;
     input [width_s-1:0] arg2;
     input sbit;
     parameter olen = width_z;
     parameter ilen = width_a+1;
     parameter len = (ilen >= olen) ? ilen : olen;
     reg [len-1:0] result;
     reg [len-1:0] result_t;
     begin
       result_t = {(len){sbit}};
       result_t[ilen-1:0] = arg1;
       result = result_t <<< arg2;
       fshl_u_1 =  result[olen-1:0];
     end
  endfunction // fshl_u

  function [width_z-1:0] fshl_u;
     input [width_a-1:0] arg1;
     input [width_s-1:0] arg2;
     input sbit;
     fshl_u = fshl_u_1({sbit,arg1} ,arg2, sbit);
  endfunction // fshl_u

  function [width_z-1:0] fshr_u;
     input [width_a-1:0] arg1;
     input [width_s-1:0] arg2;
     input sbit;
     parameter olen = width_z;
     parameter ilen = signd_a ? width_a : width_a+1;
     parameter len = (ilen >= olen) ? ilen : olen;
     reg signed [len-1:0] result;
     reg signed [len-1:0] result_t;
     begin
       result_t = $signed( {(len){sbit}} );
       result_t[width_a-1:0] = arg1; // Line 64
       result = result_t >>> arg2;
       fshr_u =  result[olen-1:0]; // Line 66
     end
  endfunction

  function [width_z-1:0] fshl_s;
     input [width_a-1:0] arg1;
     input [width_s-1:0] arg2;
     input sbit;
     reg [width_a:0] sbit_arg1;
     begin
       if ( arg2[width_s-1] == 1'b0 )
       begin
         sbit_arg1[width_a:0] = {(width_a+1){1'b0}};
         fshl_s = fshl_u(arg1, arg2, sbit);
       end
       else
       begin
         sbit_arg1[width_a] = sbit;
         sbit_arg1[width_a-1:0] = arg1;
         fshl_s = fshr_u(sbit_arg1[width_a:1], ~arg2, sbit);
       end
     end
  endfunction
endmodule

Error
read_uhdm file.uhdm
file.sv:64: Warning: Range [3:0] select out of bounds on signal `\fshr_u$func$file.sv:85$5.result_t': Setting 3 MSB bits to undef.
file.sv:64: Warning: Range [3:0] select out of bounds on signal `\fshr_u$func$file.sv:85$5.result_t': Setting 3 MSB bits to undef.
file.sv:64: Warning: Range [3:0] select out of bounds on signal `\fshr_u$func$file.sv:85$5.result_t': Setting 3 MSB bits to undef.
file.sv:66: Warning: Range [7:0] select out of bounds on signal `\fshr_u$func$file.sv:85$5.result': Setting 7 MSB bits to undef.
Generating RTLIL representation for module `\top'.

@alaindargelas I did some debugging and it looks like len is being returned as a VPIRef Object when it appears like it should be a parameter. Is that correct?

@QuantamHD, that is OK, as the ref_obj actual is the actual value of the parameter. The plugin knows how to do that.
It took me some time to compile the plugin and debugging, but I got it. I'll fix it tomorrow.
The issue is a Surelog issue, the "reg signed" keyword  combination is the problem, it prevents the parsing of the actual dimension of the reg.
If you temporarily remove "signed" everything works.

Minimum testcase:
module shift();
function int fshr_u;
   reg signed [4-1:0] result;
endfunction
endmodule

Missing range:
|uhdmtopModules:
\_module: work@shift (work@shift), id:13 tests/ScratchPad.sv:1:1: , endln:5:10
  |vpiName:work@shift
  |vpiDefName:work@shift
  |vpiTop:1
  |vpiTaskFunc:
  \_function: (work@shift.fshr_u), id:14, line:2:1, endln:4:12, parent:work@shift, parID:13
    |vpiName:fshr_u
<EMAIL_ADDRESS>    |vpiVariables:
    \_logic_var: (work@shift.fshr_u.result), id:15, line:3:4, endln:3:22<EMAIL_ADDRESS>parID:14
      |vpiName:result
<EMAIL_ADDRESS>      |vpiAutomatic:1
    |vpiVisibility:1
    |vpiReturn:
    \_int_var: , id:1, line:2:10, endln:2:13
    |vpiInstance:
    \_module: work@shift (work@shift), id:13 tests/ScratchPad.sv:1:1: , endln:5:10
  |vpiTopModule:1

@QuantamHD @rkapuscik With #2929, you can now see the range of the var.
But I tried the Yosys plugin and the same warning message appears, so something has to happen in the plugin code.
While digging, I found more sub issues that I'll update later on, they are about the sign-ness and typespec of the functions return values in general.

@rkapuscik @tgorochowik can you coordinate what needs to be done in the plugin ?

If the parameters are changed, the problem arises again; I think the problem is parameter propagation. Let's modify @QuantamHD example above and replace top()
module top (a,s,z);
  // Different size parameters than are the default of the shift module.
  parameter width_a = 240;
  parameter width_s = 9;
  parameter width_z = 240;

  input [width_a-1:0] a;
  input [width_s-1:0] s;
  output [width_z-1:0] z;

  shift #(
      .width_a(width_a),
      .width_s(width_s),
      .width_z(width_z)
  ) inst (
      .a(a),
      .s(s),
      .z(z)
  );
endmodule

// rest as above

The expectation is that all the functions that derive not only the return value (which now seems to be fine), but also some of its other input/output widths from parameters
input [width_a-1:0] arg1;
input [width_s-1:0] arg2;

... still have the width coming from the module shift() defaults in the parameters, not the values passed when instantiating shift()
Passing  this through Surelog -> UHDM -> Yosys and have Yosys emit Verilog we can see from the initialization values widths something interesting: it hints that Yosys is assuming the width of arg1 and arg2 to be what used to be the default width 4 and 2 while they should be now 240 and 9 (note that the result width looks like to be correctly calculated):
  assign \fshr_u$func$select_out_of_bounds.sv:101$5.$result  = 240'hxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx;
  assign \fshr_u$func$select_out_of_bounds.sv:101$5.arg1  = 4'hx;
  assign \fshr_u$func$select_out_of_bounds.sv:101$5.arg2  = 2'hx;
  assign \fshr_u$func$select_out_of_bounds.sv:101$5.sbit  = 1'hx;
  assign \fshr_u$func$select_out_of_bounds.sv:101$5.result  = 240'hxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx;
  assign \fshr_u$func$select_out_of_bounds.sv:101$5.result_t  = 240'hxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx;

Are the changed parameters properly propagated and emitted to UHDM ?

Fixed by #2936 , typespec where reduced to constants prematurely, so the parameters values (correctly propagated) could not be substituted (as the expressions where reduced). Also fixed the UHDM elab to point the function calls to the cloned functions in scope of the module instance instead of the function declaration.
Yosys seems happy after this fix:
[  FATAL] : 0
[ SYNTAX] : 0
[  ERROR] : 0
[WARNING] : 2
[   NOTE] : 7
Warning: Removing unused module: \shift from the design.
Generating RTLIL representation for module \top'. Generating RTLIL representation for module $paramod\shift\width_a=32'd240\signd_a=32'd1\width_s=32'd9\width_z=32'd240'.
yosys>

Thank you, looks like that fixed it!


Add info to contributing

Coverage remained the same at 100.0% when pulling 47e374c645d9f4a392907da736041f00b03f996e on contributing-info into 93874987a669297eb5965e0e4476133aeb801ac1 on master.


Rename GCS to GCP

Describe your changes:
Fixes #9886

I worked on renaming gcs to gcp

Type of change:

[ ] Bug fix
[ ] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

Remaining things:
Migrations


Reloading window signs out of all accounts

Type: Bug
Whenever the VSCode window reloads all accounts are signed out and you have to sign back in.
Steps to reproduce:

open a window of vscode
sign in to one or more accounts
reload the window (developer: reload)
all accounts are signed out

expected result: accounts stay signed in
actual result: all accounts sign out, making it impossible to open a codespace
VS Code version: Code 1.70.1 (Universal) (6d9b74a70ca9c7733b29f0456fd8195364076dda, 2022-08-10T06:09:06.916Z)
OS version: Darwin x64 17.7.0

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.70.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Can you provide the contents of the Microsoft/GitHub Authentication output pane:

And also anything that shows up in Dev Tools:

ctrl + shift + P
"Dev Tools"

The GitHub authentication output:

The Microsoft authentication output:

There is nothing related to this in dev tools.
Also, this error started when I updated to 1.70.1

Restarting the computer appears to have fixed the issue. Thank you for your help!

Restarting the computer appears to have fixed the issue. Thank you for your help!

Restarting the computer appears to have fixed the issue. Thank you for your help!

Interesting. I'll close this then but I do wonder what changed. Did you maybe change your password on your OS?

It had been a while since it had been restarted, so maybe vscode being closed out and reopened allowed it to renew permissions? I wonder if something was preventing it from reading the keychain on the Mac, and the restart removed that.

Yeah that's my suspicion as well... in any case, it's good to know that this particular error can be fixed with a restart.


WVD Resources and Relationships Article

Hello - I thought that the following article might be good to incorporate into this documentation: https://github.com/PeterSmallbone/WVD/wiki/WVD-(Windows-Virtual-Desktop)-Resources-and-Relationships
Thanks!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f26be54d-0f67-5098-7839-98f5bb064188
Version Independent ID: 187fa3ce-ade9-1b07-2af3-c874ec3d0aac
Content: Windows Virtual Desktop for the enterprise - Azure Example Scenarios
Content Source: docs/example-scenario/wvd/windows-virtual-desktop.md
Service: architecture-center
Sub-service: example-scenario
GitHub Login: @doodlemania2
Microsoft Alias: pnp

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#298839

We have this captured as an article to improve. Thank you for your feedback!


Unable to download a song from SoundCloud

$ youtube-dl -x --verbose "https://soundcloud.com/philotue/irish-coffee"
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-x', '--verbose', 'https://soundcloud.com/philotue/irish-coffee']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2019.12.25
[debug] Python version 3.8.1 (CPython) - Linux-5.3.1-arch1-1-ARCH-x86_64-with-glibc2.2.5
[debug] exe versions: ffmpeg 4.2.1, ffprobe 4.2.1
[debug] Proxy map: {}
[soundcloud] philotue/irish-coffee: Downloading info JSON
WARNING: Unable to download JSON metadata: HTTP Error 401: Unauthorized
[soundcloud] philotue/irish-coffee: Downloading info JSON
ERROR: Unable to download JSON metadata: HTTP Error 401: Unauthorized (caused by <HTTPError 401: 'Unauthorized'>); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/usr/lib/python3.8/site-packages/youtube_dl/extractor/common.py", line 627, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/lib/python3.8/site-packages/youtube_dl/YoutubeDL.py", line 2237, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/lib/python3.8/urllib/request.py", line 531, in open
    response = meth(req, response)
  File "/usr/lib/python3.8/urllib/request.py", line 640, in http_response
    response = self.parent.error(
  File "/usr/lib/python3.8/urllib/request.py", line 569, in error
    return self._call_chain(*args)
  File "/usr/lib/python3.8/urllib/request.py", line 502, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.8/urllib/request.py", line 649, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)

Duplicate https://github.com/ytdl-org/youtube-dl/issues/23529


target[Symbol.iterator] is not a function

atom.tooltips.add errors when given a jQuery object
https://github.com/atom/atom/blob/843f91c8d2b5d436da2de5a64fbed42f1757a61b/src/tooltip-manager.js#L115-L119
the target in the for loop is what is throwing the error
Applicable Issues
https://github.com/morassman/process-palette/issues/55
https://github.com/platformio/platformio-atom-ide-terminal/issues/403

/cc: @maxbrunsfeld @nathansobo

Looks like this problem was introduced by converting TooltipManager to JS.

looks like it was added in jQuery 2.2.0 and space-pen uses 2.1.4 so any package using atom-space-pen-views will have this issue.
https://blog.jquery.com/2016/01/08/jquery-2-2-and-1-12-released/

Any way you can release another beta version with this fix soon? I keep finding more packages that don't work because of this issue.

@rsese I put this on the reactor queue. We should really hotfix this.


Is trunk check open source

Hi, started using trunk yesterday and I dig it, but I'm wondering if the tool itself is open source?
Running on M1 Mac and it's taking a bit of CPU because it's not compiled for darwin-arm64, was hoping to open an issue on the main repository but not seeing that repo.

Found there's an arm64 package on brew.sh, installed, but when I set "trunk.trunkPath": "/opt/homebrew/bin/trunk" in VSCode I get an error.

Hi Kevin!
Thanks for letting us know this is important to you. While trunk is not open-source, we do have arm64 support on the roadmap, and hearing feedback like this helps us prioritize. FWIW, my personal experience with rosetta and particularly trunk + rosetta has been very positive without any notice of slowness.


@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/opentelemetry-api-feedstock#4.


Merge two large switch blocks in AOT snapshotting

No functional changes. Merges two platform switch statements and
eliminates an iOS-specific local.

Related #2089


I'd like to join this project's community

Your public repo
https://github.com/tflaj/gov4git-identity-public.git
Your public branch
main

 Follow up
On Thursday, 29-Feb-24 17:17:51 UTC by Gov4Git dev
@tflaj was added to the community.


Adding support for binding reponse

Finishing missing support for Route Service
The request was handled but not the response.
http://docs.cloudfoundry.org/services/api.html#binding

@tinygrasshopper Can you check ? thanks

Merged. Thanks!


The name is wrong

Hi!

Remember, Apple!

Approved


Update README.md

Added note about dependency on Cordova Android 7.0.0.

Much appreciated, thanks!


tmt-report-result: may need to escape special symbols like colon

It seems like tmt-report-result script adds testcase name  to log file name. https://github.com/teemtee/tmt/blob/8245c4797d69b6a1574ae9e4445d6eb571080389/tmt/steps/execute/scripts/tmt-report-result#L26
One of my tests has colons in it's testcase names which appear is not expected by some parser.
01:32:49         Command returned '0' (success).
01:32:49         Extract results of '/livepatch/selftests'.
01:32:49         fail:
            mapping values are not allowed in this context
              in "<unicode string>", line 1, column 26
01:32:49
01:32:49         summary: 0 tests executed

tmt-report-results.yaml
  - name: /1..7 selftests: livepatch: test-callbacks.sh Pass
    result: pass
    log:
      - 1..7_selftests:_livepatch:_test-callbacks.sh_Pass_test-callbacks_result.log
    end-time: "2024-09-14T01:32:26.859726+00:00"
    data-path: /data/guest/default-0/livepatch/selftests-1/data
  - name: /2..7 selftests: livepatch: test-ftrace.sh Pass
    result: pass
    log:
      - 2..7_selftests:_livepatch:_test-ftrace.sh_Pass_test-ftrace_result.log
    end-time: "2024-09-14T01:32:28.841241+00:00"
    data-path: /data/guest/default-0/livepatch/selftests-1/data
  - name: /3..7 selftests: livepatch: test-livepatch.sh Pass
    result: pass
    log:
      - 3..7_selftests:_livepatch:_test-livepatch.sh_Pass_test-livepatch_result.log
    end-time: "2024-09-14T01:32:36.808714+00:00"
    data-path: /data/guest/default-0/livepatch/selftests-1/data
  - name: /4..7 selftests: livepatch: test-shadow-vars.sh Pass
    result: pass
    log:
      - 4..7_selftests:_livepatch:_test-shadow-vars.sh_Pass_test-shadow-vars_result.log
    end-time: "2024-09-14T01:32:36.868439+00:00"
    data-path: /data/guest/default-0/livepatch/selftests-1/data
  - name: /5..7 selftests: livepatch: test-state.sh Pass
    result: pass
    log:
      - 5..7_selftests:_livepatch:_test-state.sh_Pass_test-state_result.log
    end-time: "2024-09-14T01:32:43.781280+00:00"
    data-path: /data/guest/default-0/livepatch/selftests-1/data
  - name: /6..7 selftests: livepatch: test-syscall.sh Pass
    result: pass
    log:
      - 6..7_selftests:_livepatch:_test-syscall.sh_Pass_test-syscall_result.log
    end-time: "2024-09-14T01:32:43.982790+00:00"
    data-path: /data/guest/default-0/livepatch/selftests-1/data
  - name: /7..7 selftests: livepatch: test-sysfs.sh Pass
    result: pass
    log:
      - 7..7_selftests:_livepatch:_test-sysfs.sh_Pass_test-sysfs_result.log
    end-time: "2024-09-14T01:32:47.802114+00:00"
    data-path: /data/guest/default-0/livepatch/selftests-1/data

Or use quotes to wrap these free-form fields' values:
  - name: "/1..7 selftests: livepatch: test-callbacks.sh Pass"
    result: pass
    log:
      - "1..7_selftests:_livepatch:_test-callbacks.sh_Pass_test-callbacks_result.log"

I believe this could be easily fixed by applying #3231 and it could potentially land in the v1.37 release.
CC: @psss

I believe this could be easily fixed by applying #3231 and it could potentially land in the v1.37 release.

Yeah, sounds like an easy fix for the regression we introduced recently. Let's get it in!


Automated cherry pick of #4513: fix: 腾讯云不支持描述字段参数

Cherry pick of #4513 on release/2.14.
#4513: fix: 腾讯云不支持描述字段参数

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.14@98d7994). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             release/2.14   #4515   +/-   ##
==============================================
  Coverage                ?   6.84%
==============================================
  Files                   ?     522
  Lines                   ?   88756
  Branches                ?       0
==============================================
  Hits                    ?    6076
  Misses                  ?   82173
  Partials                ?     507

Flag
Coverage Δ

#aFlag
6.84% <ø> (?)

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 98d7994...b2a52ad. Read the comment docs.

/lgtm

/approve


Bag.read_text much slower than DataFrame.read_csv

Playing with DataFrame and Bag I found out that the same ~500 MB file was loading into memory way longer with Bag.read_text compared to DataFrame.read_csv:
import dask.dataframe as dd

if __name__ == '__main__':
    _ = dd.read_csv("./data.csv").compute()

execution time: 0min 4s
import dask.bag as db

if __name__ == '__main__':
    _ = db.read_text("./data.csv").compute()

execution time: 2min 37s
using much more memory as well (hundreds of MB vs ~8 GB).
I found out that program spends most of time on serialization of decode() result from dask\bag\text.py. Replacing cloudpickle with pickle results with execution time of 29s, with memory usage about 3 GB.
Is it known issue?
My environment is Python 3.5.1 :: Anaconda 4.1.0 (64-bit) on Windows 10. I use dask from master branch. data.csv is clicks_tests.csv from https://www.kaggle.com/c/outbrain-click-prediction/data

I suspect that this is all just interprocess communication.
How about the following:
db.read_text('.data.csv').count().compute()

You are right, 5s. Can you explain why does this help?

The cost isn't in read_text, it's in pulling the data back from the worker python process to the main process when calling .compute().  This incurs a pickle and IPC roundtrip, both of which are slower than reading from disk.  It's much better to leave the data on the worker and do processing there, such as by using Bag.map methods or other dask functionality.

Ideally, you want .compute() to return a small result.

Thank you. I guess this issue should be closed.

You might find the following document of use: http://dask.pydata.org/en/latest/scheduler-choice.html


ThreeFold Connect Authenticator Browser Icon is Not ThreeFold

Is your feature request related to a problem? Please describe
ThreeFold Connect Authenticator Browser Icon is Not ThreeFold, but Vue

Describe the solution you'd like

We should perhaps have the threefold logo instead of the Vue logo

The Vue icon still appears instead of TF icon.


Modifying CSS or SCSS files in the Lit templates do not trigger a full reload

Describe the bug

The Lit template needs a full page reload since it currently does not support HMR. Modifying CSS files triggers an HMR instead of a full page reload. This means the user will have to trigger a reload manually to see the changes.
Possibly related to #2633 but the opposite way around?

Reproduction

git clone git@github.com:e111077/vite-lit-element-ts-sass.git
cd vite-lit-element-ts-sass
npm install
npm run dev
open browser to localhost:3000
open dev tools
add some new text to src/my-element.ts and save
observe full page reload in dev tools console
Change the border color of src/my-element.scss and save
observe HMR in dev tools console
observe no change to color
reload page
observe change in color

System Info
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
  System:
    OS: Linux 5.4 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
    Memory: 23.58 GB / 25.01 GB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 15.14.0 - ~/.nvm/versions/node/v15.14.0/bin/node
    npm: 7.7.6 - ~/.nvm/versions/node/v15.14.0/bin/npm
  npmPackages:
    vite: ^2.2.3 => 2.2.3

Used package manager: npm
Logs

  vite:config bundled config file loaded in 30ms +0ms
  vite:config using resolved config: {
  vite:config   build: {
  vite:config     target: [ 'es2019', 'edge18', 'firefox60', 'chrome61', 'safari11' ],
  vite:config     polyfillDynamicImport: false,
  vite:config     outDir: 'dist',
  vite:config     assetsDir: 'assets',
  vite:config     assetsInlineLimit: 4096,
  vite:config     cssCodeSplit: false,
  vite:config     sourcemap: false,
  vite:config     rollupOptions: { external: /^lit-element/ },
  vite:config     commonjsOptions: { include: [Array], extensions: [Array] },
  vite:config     minify: 'terser',
  vite:config     terserOptions: {},
  vite:config     cleanCssOptions: {},
  vite:config     write: true,
  vite:config     emptyOutDir: null,
  vite:config     manifest: false,
  vite:config     lib: { entry: 'src/my-element.ts', formats: [Array] },
  vite:config     ssr: false,
  vite:config     ssrManifest: false,
  vite:config     brotliSize: true,
  vite:config     chunkSizeWarningLimit: 500,
  vite:config     watch: null
  vite:config   },
  vite:config   plugins: [
  vite:config     'alias',
  vite:config     'vite:resolve',
  vite:config     'vite:html',
  vite:config     'vite:css',
  vite:config     'vite:esbuild',
  vite:config     'vite:json',
  vite:config     'vite:wasm',
  vite:config     'vite:worker',
  vite:config     'vite:asset',
  vite:config     'vite:define',
  vite:config     'vite:css-post',
  vite:config     'vite:build-html',
  vite:config     'commonjs',
  vite:config     'vite:data-uri',
  vite:config     'rollup-plugin-dynamic-import-variables',
  vite:config     'postcss-lit',
  vite:config     'vite:import-analysis',
  vite:config     'vite:esbuild-transpile',
  vite:config     'vite:terser',
  vite:config     'vite:reporter'
  vite:config   ],
  vite:config   configFile: '/home/elliott/Workspace/lit/vite-lit-element-ts-sass/vite.config.ts',
  vite:config   configFileDependencies: [ 'vite.config.ts' ],
  vite:config   inlineConfig: {
  vite:config     root: undefined,
  vite:config     base: undefined,
  vite:config     mode: undefined,
  vite:config     configFile: undefined,
  vite:config     logLevel: undefined,
  vite:config     clearScreen: undefined,
  vite:config     build: {}
  vite:config   },
  vite:config   root: '/home/elliott/Workspace/lit/vite-lit-element-ts-sass',
  vite:config   base: '/',
  vite:config   resolve: { dedupe: undefined, alias: [ [Object] ] },
  vite:config   publicDir: '/home/elliott/Workspace/lit/vite-lit-element-ts-sass/public',
  vite:config   cacheDir: '/home/elliott/Workspace/lit/vite-lit-element-ts-sass/node_modules/.vite',
  vite:config   command: 'build',
  vite:config   mode: 'production',
  vite:config   isProduction: true,
  vite:config   server: {},
  vite:config   env: { BASE_URL: '/', MODE: 'production', DEV: false, PROD: true },
  vite:config   assetsInclude: [Function: assetsInclude],
  vite:config   logger: {
  vite:config     hasWarned: false,
  vite:config     info: [Function: info],
  vite:config     warn: [Function: warn],
  vite:config     error: [Function: error],
  vite:config     clearScreen: [Function: clearScreen]
  vite:config   },
  vite:config   createResolver: [Function: createResolver]
  vite:config } +3ms
vite v2.2.3 building for production...
✓ 16 modules transformed.
dist/style.css                        0.07kb / brotli: 0.06kb
dist/vite-lit-element-ts-sass.es.js   15.06kb / brotli: 5.16kb

Before submitting the issue, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the docs.
[x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[x] Provide a description in this issue that describes the bug.
[x] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

I plugged in a community HMR module to HMR Lit elements, but the SASS issue still persisted similar to the open svelte bug linked in the description

同样的问题，希望能解决

Note: this seems to have been fixed in CSS files but not SCSS files

This is because import foo from 'foo.css' has two effects.
The first one is injecting foo.css to html. This one's hmr is handled by Vite.
The second one is exporting the content of foo.css. This one's hmr is not handled by Vite currently.
For example, this repro has style applied which is imported with import text from './style.css'.
What is difficult here is Vite needs to differentiate import 'foo.css' and import foo from 'foo.css'. Vite injects ?used to import foo from 'foo.css' during build for tree shaking. So it may be possible to implement by that approach.
For a workaround you could use it like below too.
import 'foo.css' // inject css
import foo from 'foo.css?inline' // obtain content

BTW I feel this multiple effect a bit confusing.

Vite 4 has deprecated default imports from .css and refers to ?inline instead. So I think this is resolved.


some problem abtout speed

why the speed of synthesis is very slow?how to slove it?
Need some help! Thanks!

Can I see how slow it is?


[python/mdns] Add "discover" command for operational discovery

Problem
DiscoveryImplPlatform class contains code for DNS-SD discovery (currently, only Linux provides a backend based on Avahi), but no common interface for the functionality exists.
Summary of Changes

Expose the mDNS resolver functionality implemented for Avahi/Linux using a new Resolver interface.
Add DiscoverDevice method to the device controller.  The method initiates operational discovery of a node over mDNS-SD.
The results are then used to update the address of the node and the error code is additionally communicated to an optional delegate.
Add discover <fabricid> <nodeid> command to the Python controller.

Usage:

Build CHIP with chip_mdns_advertiser="platform" argument.
Start Python CHIP controller.
Pair a CHIP device using connect -ble ... command.
Discover the device using discover <fabricid> <nodeid>.

Note that Thread devices currently don't support the DNS-SD service registration, but one can still test the new command by registering a service manually, e.g. given that the default node ID 12344321 is used run the following commands to register the corresponding service:
    avahi-publish-address host1.local. fd11:22::1 &
    avahi-publish-service -H host1.local. BC5C01-7B _chip._tcp 12345

After that, discover<PHONE_NUMBER>1 should return fd11:22::1:12345.

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


statusBar.foreground is read-only (breaks plugins)

VSCode Version: 1.22.0-insider
OS Version:mac high sierra 10.13.3 (17D102)

Steps to Reproduce:

Attempt to use vim plugin version 0.11.1 (or any other plugin that needs to modify statusBar.foreground)
any interaction that makes the plugin attempt to edit this property (hitting hjkl in this case) causes the following error in the console:

Error: TypeError: Cannot delete read only property 'statusBar.foreground' of object
    at Object.deleteProperty (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:524:821)
    at StatusBarImpl.SetColor (/Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/statusBar.js:30:20)
    at ModeHandler._renderStatusBar (/Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/mode/modeHandler.js:1065:39)
    at ModeHandler.<anonymous> (/Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/mode/modeHandler.js:1048:18)
    at Generator.next (<anonymous>)
    at /Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/mode/modeHandler.js:7:71
    at Promise (<anonymous>)
    at __awaiter (/Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/mode/modeHandler.js:3:12)
    at ModeHandler.updateView (/Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/mode/modeHandler.js:884:16)
    at ModeHandler.<anonymous> (/Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/mode/modeHandler.js:202:28)
    at Generator.next (<anonymous>)
    at /Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/mode/modeHandler.js:7:71
    at Promise (<anonymous>)
    at __awaiter (/Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/mode/modeHandler.js:3:12)
    at ModeHandler.handleSelectionChange (/Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/mode/modeHandler.js:97:16)
    at Object.taskQueue_1.taskQueue.enqueueTask [as promise] (/Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/mode/modeHandler.js:68:58)
    at TaskQueue.<anonymous> (/Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/taskQueue.js:32:32)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/taskQueue.js:4:58)
    at <anonymous> (at TaskQueue.<anonymous> (/Users/joshua/.vscode-insiders/extensions/vscodevim.vim-0.11.1/out/src/taskQueue.js:36:29))
t.log @ console.ts:136
t._logExtensionHostMessage @ extensionHost.ts:398
(anonymous) @ extensionHost.ts:211
emitTwo @ events.js:106
emit @ events.js:194
process.nextTick @ internal/child_process.js:766
_combinedTickCallback @ internal/process/next_tick.js:73
_tickCallback @ internal/process/next_tick.js:104

Does this issue occur when all extensions are disabled?: Yes/No
No

Reading your description it seems that the issue originates from an extension and not VS Code itself. Thereby I will close this issue and kindly ask you to report this issue against the extension repository.
Most extensions are on GitHub as well so it should be easy to file it against the extension. If you open an extension on the market place, click on the Support link to find out more.

Thanks again for your feedback!

@sandy081 see https://github.com/VSCodeVim/Vim/issues/2432#issuecomment-371737601

Also, if settings.json is dirty, then I get constant log spam whenever I move the cursor using the vim extension:
[renderer3] [error] Unable to write into user settings because the file is dirty. Please save the user settings file first and then try again.: Error: Unable to write into user settings because the file is dirty. Please save the user settings file first and then try again
Is that supposed to happen when the settings file is dirty and an extension tries to update the configuration?

@roblourens Good catch.

I think the problem is with .get('colorCustomizations'); and Object.assign doesn't work.

Problem is not with assign. It's because JSON.stringify() on the result object (which is proxy) is not returning proper value. Proxy should have a trap for toJSON property access.  Having this trap fixes this.

Is that supposed to happen when the settings file is dirty and an extension tries to update the configuration?

Yes, this is expected.


Mods do not get removed from game config when GAME_MODS_IDS_LIST is empty

Describe the bug
I am not sure if it this a bug or a feature request, but mod IDs do not get removed from the server config when I leave GAME_MODS_IDS_LIST empty
To Reproduce
Steps to reproduce the behavior:

Add mod IDs to GAME_MODS_IDS_LIST and start the server with mods
Remove IDs from GAME_MODS_IDS_LIST and update the stack
Game still starts with mods, because the mod IDs are still present in the server config

Expected behavior
I expect the server to start with no mods when GAME_MODS_IDS_LIST is empty

I think the ENV vars should be the main source of truth. If people want to primarily modify the server config itself, there is the feature to change ARMA_CONFIG to a different config file.

I will leave the decision to the folks if they actually want it.

So what do the folks say? :)

https://github.com/acemod/docker-reforger/blob/32a30c9c35733f23016e187d7a6909a89c8957ea/launch.py#L121-L123


Update docs for https://github.com/facebook/react-native/pull/17747

Update docs for https://github.com/facebook/react-native/pull/17747

Wait how does this commit makes sense without updating build.gradle of react-native simultaneously?
This is changing

Android SDK version 23 27 (compileSdkVersion in build.gradle)

and

SDK build tools version ~23.0.1~~ 26.0.2 (buildToolsVersion in build.gradle)

But if you look at the relevant part of build.gradle the numbers there are still are
android {
    compileSdkVersion 23
    buildToolsVersion "23.0.1"

So I think merging this PR as it is will only create confusion, because the docs will suggest Android tools that have a mismatch with what RN actually uses.

@hey99xx I had updated and force-push to the branch in the PR in RN, and am waiting for more feedback https://github.com/facebook/react-native/pull/17747#issuecomment-363969697
Haven't updated this PR to reflect the changes in versions there yet.

But, the instructions about build tool versions could probably be removed completely, as the new gradle version will pick one itself depending on compatibility.

It seems like this is outdated now and we'll need a new PR with the latest versions for everything. Sorry that it took so long to get back to this.


QA time locked accounts

Test block production with timed accounts (Currently timed-locked accounts can be created only in genesis ledger)
Having locked tokens changes the coinbase amount and this in turn affects the blockchain snark. We should test if new snarked ledgers are created with transactions (user and coinbase transactions) on these timed-locked account. This would mean running a qa net long enough to emit proofs from the scan state. just_emitted_a_proof in the logs tell whether a block has a new snarked ledger.

The existing unit tests in Transaction_snark compare the checked and unchecked timing validations.
Validation takes a (timed) account, a transaction amount, and a global slot, and returns a new timing (perhaps Untimed) or an error. If there's no error, validation succeeds, and the transaction can proceed.
"Fully-vested" means the calculated min balance is zero. The situations considered in the existing tests are.

Valid cases:

before the cliff time, still timed
past the cliff, the min balance is still greater than zero, so still timed
fully-vested, so now untimed
fully-vested, can spend whole balance

Error cases:

past the cliff, transaction amount would reduce balance below min balance, an error
past the cliff, transaction amount exceeds actual balance, an error

Possible new unit tests: compare the calculated min balances in checked, unchecked worlds before/after cliff, after full vesting.
Possible integration tests: send payment with timed account, with amounts that would, would not take balance below minimum. Should see applied status for success, source insufficient balance.
(All timing validation errors map to insufficient balance, apparently, though some should be something like "insufficient available balance due to timing".)

Worked out a way to deal with expected errors


Require stg prerelease

Related Issue or Background Info

#1634
#1633

Draft PR against another feature branch to get both moving.
Changes Proposed

require the current release to be present in stg in order to run the prod deployment

Additional Information
There is an argument that this should be something we can override manually. Doing that is at best complicated: this is simple. For the sake of argument, here's what I came up with (bearing in mind that allowing manual releases is not on the table):

run this stg-check job.
if it fails, run a new job step that is tied to a special deployment environment that has an approval list, such that it'll block and require a sign-off from another person before it can complete
somehow require for the deployment to go forward that one of those two jobs have completed. (This is the step I'm not 100% sure is possible.)

Considering that the staging release takes under 10 minutes, not allowing it seemed simpler.
Screenshots / Demos
Checklist for Author and Reviewer
Testing

let me explain about testing the production release workflow...

If we have agreement on the README changes, I'll try to update the accompanying image, since it has numbers on it that no longer match.


improve colors in the compiler output

The colored output is a definite improvement.
We could make it even better if:

The code with the error were rendered in its own color (or even used the same syntax highlighting as the IDE).
Text quoted with single quotes in error messages were rendered in the same way (using the code color, or the syntax highlighter), just like we do in the IDE.
The color (currently dark blue) used to render paths was easier to read in terminals with a dark background.

A further request I have is that we add a line break after the error location info, and before the error message, giving us something like this:
../language/src/ceylon/language/meta/declaration/ClassDeclaration.ceylon:158
warning: declaration is never used: 'Annotation'
    shared formal ConstructorDeclaration[] annotatedConstructorDeclarations<Annotation>()
                                                                            ^

I hate how currently the actual error message always wraps.

Doing proper syntax highlighting on the error line might be tricky because we don’t know for sure which state the lexer is in at the beginning of the line.
     print(");

Could be part of
print(
    "foo bar
     print(");

or
     print(");
            foo bar");

We won’t have that problem for single-quoted fragments though.

@lucaswerkmeister True, we do have tokens which span multiple lines. But how common is it to have an error that occurs partway-through a multiline token. I don't this it's common at all.

I doubt we could really do proper coloring like the IDE,  in general we only have a very small set of fixed colors to work with (in my experience only the 4 current colors work reliably in all terminals)

Besides the fact that I think it world quickly become garish to have error, location and code all colored. It would negate the advantage that finally the errors and warnings are very visibly recognizable and turn everything into the same porridge we had before, but now colored

I doubt we could really do proper coloring like the IDE,  in general we only have a very small set of fixed colors to work with (in my experience only the 4 current colors work reliably in all terminals)

Oh I see, I did not know that.

It might make sense to make the source code indicator (^) blue, since it’s location info just like the file name. (But so is the line number, which we currently don’t color…)

I'm not sure any of it "makes sense", I think it's more a case of esthetics and usability. The blue color is indeed somewhat difficult to read in some cases so I thought to limit it to just the filename. Sure the number could be blue as well but the caret, a single character on an empty line, might make it to hard to see.
Anyway, unless people can come up with good ideas and/or reasons I'm closing this. IMO we should use colors very sparingly.


RuntimeError

Hello,
I am receiving errors when I test (using inference.py) with some custom images of different size and the error is as follows -
RuntimeError: invalid argument 0: Sizes of tensors must match except in dimension 1. Got 15 and 90 in dimension 2 at c:\a\w\1\s\tmp_conda_3.7_104535\conda\conda-bld\pytorch_1550400486030\work\aten\src\thc\generic/THCTensorMath.cu:83
This particular moment I had an image with dimensions 216*120 but I have had similar error for different sized images as well which were comparatively bigger.
Will you kindly tell what is causing this error and how can I get rid of it?

Hi,
the model supports 640x360 input resolution as input. Since you use a different resolution, I presume that the error is at the concatenation of an interpolation layer output with the features of the corresponding skip connection. This happens because the interpolation layers utilize the default h and w  (360 and 640, see models/shallow_partial.py), while the skip connections feed the decoder with feature maps of your h' and w', where h' < h and w' < w (i.e. 15 < 90 in your case).

Hi @spthermo. Thank for the reply.
I get this part. But sometimes an image of 1280*720 has also been read but an image with dimensions 694*512 gives errors.
Also I have found another discrepancy, when my input image is in .jpg format, I am able to see the denoised depth image (output from inference.py) but can't see the denoised depth image when it is in .png format (it is totally black image everytime). Interestingly the pointclouds in both the cases are available and somewhat similar. Did you guys had the same observation while testing?

@spthermo yes,i also found input the png image will output the all black images,how to solve this?

@kearcer try to download another image viewer, like ImageJ

After loading a file with the load_depth function, the result should be an image tensor containing the depth values in meters (the scale parameter is responsible for that scaling, with the default value being 0.001 and assuming that the image contains the depth in millimeters).
Typical formats for depth images would be:

.exr with raw float values (in arbitrary scaling, in the case of meters for example, it should be load_depth(filename, scale=1.0))
.png with unsigned short (i.e. 16bit) values (usually in millimeters)
.pgm with unsigned short (i.e. 16bit) values (usually in millimeters)

It should be noted that .jpeg files are unsuitable to store depth values.
If you need more help with your files, please upload a sample that we can check.


Update flux to 0.11.0

Can you target this change against the flux-staging branch? Also were there no changes needed? The influxdb storage has to implement the flux.Table interface, I am surprised nothig needed to change.

It appears that it reuses the code in platform so there's no unique code that implements flux.Table in this project. I'll modify this PR to be rebased  off of flux-staging and change the target branch.

Awesome, glad to here its reusing code :)


Latest build conventions

coverage: 99.623%. remained the same
when pulling d5b9c44dad826cf0925cd4ecc76543e04c512ee2 on latest_build
into 0599b3b92b882ae9883bf10613987ed3d54d0fd2 on main.


Document migration consolidation procedure

Even if there is no formal command or other provision to support consolidation of migration files, it would still be useful to document a working procedure to achieve this. Migration consolidation is the normal process of reducing the number of migration files down to zero, or near-zero periodically, to eliminate old, obsolete migrations and speed up database seeding and migrations.

Along these lines, if the migrations themselves cannot be easily consolidated (or even if they can), maybe a small step would be to have built-in support (i.e. configuration option) for automatically organizing migrations into subdirectories by year or year and month. After a few years, in a long-running or on-going project, as we have, its easy to amass hundreds of migrations, particularly if you subscribe to the idea of limiting the number of database changes performed in each individual migration or, at least, keeping each migration as single-purpose as possible (i.e. there tends to be more migrations when taking this approach). So, in that case, or just after a longer period of time with the "beefy migration" approach, it doesn't seem helpful for most of those migrations to remain in "direct view" in the migrations directory, particularly those created more than 12 months ago.

The subdirectory approach sounds more like a workaround then, if you have that many, I also agree that just merging them in the end would be probably the best long-term kind of resolution on this.
But it can still be done in parallel of course.
I also have to scroll already multiple pages on some repos to get to the lastest one :)

@broberts-mrmc Migration organization should be considered a separate topic from consolidation. Please create a separate issue to discuss that.

I could agree if you weren't iDead. As a general rule, I don't make agreements with the dead. Seriously, as one issue or separate issues, it makes me little difference. Though, I think the topics are related so, if separate issues, a reference between the separate issues would seem appropriate.

I would like to link here to laravels docs on this https://laravel.com/docs/8.x/migrations#squashing-migrations
As this might clarify some terminology options.
Also, I think there might be already some existing issues or PRs around a similar topic
So far I only found https://github.com/cakephp/phinx/issues/102

I believe Doctrine also has a command called rollup, although it seems scarcely documented, so I'm not sure if it is exactly the same thing. There are, however, some recent blog posts on the topic.


my customHeaders works, but I can not get excepted data!

Expected behavior
I use phantomjs to get ajax data of a website written with laravel framework.
there is my code to set the customHeaders, token[1] is laravel's csrf _token.
.then(content =>    {
   var patt1=new RegExp(/(?:content=")[a-z|A-Z|0-9]+(?=">)/);
   var token = patt1.exec(content);
   token = token.toString().split('"');
   sitepage.customHeaders = {
        'X-CSRF-TOKEN' : token[1],
        'Accept' : 'application/json',
        'X-Requested-With' : 'XMLHttpRequest'
    };
  return sitepage.open(server, 'POST', data);
  })
.then(status => {
     console.log(status);
     console.log(sitepage);// I can see the customHeaders here!
     return sitepage.property('content');
})

But when I run this code, laravel seems consider that I am do a csrf request!
And I print the cookies, It also looks normal!
Actual behavior
I have a test code and can works correctly run with phantomjs not the nodejs.
function post(server, data, callback) {
    page.open(server, 'post', data, callback);
}
// This function just for get the msg!
page.onConsoleMessage = function(msg) {
    var url = 'https://gamedataquery.sdo.com/ajax/getpaypoint';
    var data = 'date=2016-05-13+~+2016-05-20&area=(177)%E7%BB%8F%E5%85%B8%E5%9B%9E%E5%BD%92%E4%BA%8C%E5%8C%BA+-+all';
    page.customHeaders = {
        'X-CSRF-TOKEN' : msg,
        'Accept' : 'application/json',
        'X-Requested-With' : 'XMLHttpRequest'
    };
    post(url, data, function(status){
        console.log(status);
        console.log('----------------------------------------------\n');
        console.log(page.plainText);
    });
};

Steps to reproduce the behavior

I don't know...

Environment

OS:Windows7
Node version (node -v):6.2.0
package version: 2.1.7

I have never used laravel framework. But you should use property to set customHeaders.

@amir20 Could you tell me how to use property to set a value? Please show me a sample example.
I have fixed this problem use phantom-prebuilt package.But I am still interested in this project.

I haven't tested it but something like page.property('customHeaders', { ... }) should work. This is also in the README file. Please read it.


Removed link in resource images

Fixes

Fixes #197  by @Xaid-vfx
Description

Resource images and whitespace no longer act as links. Also, improved the formatting of the code.
Technical details

Removed the anchor tag around the resource image div to prevent unintended navigation.
Screenshots

The cursor does not change to pointer, indicating there is no link in the area

Checklist

[ ] My pull request has a descriptive title (not a vague title like Update index.md).
[ ] My pull request targets the default branch of the repository (main or master).
[ ] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@Xaid-vfx Did the needful, please review this PR. Thankyou

Thanks so much for your work here, but I'm closing this, as it was already resolved in #203


[SPARK-4561] [PySpark] [SQL] turn Row into dict recursively

Add an option recursive to Row.asDict(), when True (default is False), it will convert the nested Row into dict.

cc @JoshRosen

Merged build triggered.

Merged build started.

Test build #40079 has started for   PR 8006 at commit 922cc5a.

Test build #40079 has finished for   PR 8006 at commit 922cc5a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

cc @JoshRosen for review

Merging this into master and 1.5 branch


Fixes bug with in_iframe(visible: true)

Fixes bug where in_iframe(visible: true) blows up because true gets converted to a string, but must stay in TrueClass

I just saw the features area, I'll work on adding feature tests for this fix.  However, Travis CI failed for what looks like chrome version issues.

I just saw the features area, I'll work on adding feature tests for this fix.  However, Travis CI failed for what looks like chrome version issues.

Closing this PR for one that contains new tests

Closing this PR for one that contains new tests


3.9.0 The time of the year is spring

General information
Project issue is for:
(Server/Modules/Launcher)
Expected result:
If the file contains "weather.json" set the "seasonType" parameter for "name": "SPRING" to 1, then spring is displayed more correctly, with thawing as online.
Actual result:
With the value "seasonType": 3 for "name": "SPRING" in the file "weather.json" the game displays late spring.
(Add a description of the issue here)
How to reproduce

Log files
Server: (found in /user/logs/server-yyyy-mm-dd-xx.log)
BepinEx: (found in /BepinEx/LogOutput.log)
Client: (found in /Logs/log_<date>_<version>/<date>_<version> traces.log)
Profile
You can optionally include your game profile if you think it would help us reproduce the error easily (found in /user/profiles/xxxxxxxxxxxx.json)
The profile id can be found in the top left of the launcher.
Screenshots
(Optional, only add them if you think it adds value)
Notes - PLEASE READ!
DO NOT INCLUDE THIS SECTION IN THE REPORT

Do not include any of the text written in parentheses and italics in your report (example text - do not include me in the report!)
If you uploaded and attach the log files to the issue report, instead of using the codepaste, please remove the "Log Files" section as well.
If you use the codepaste site please make sure the paste has a sufficiently long lifespan set, 24hrs is often not enough.
You must be able to replicate the issue with a fresh profile, while running no mods.
If you are using a profile from an older version of SPT-AKI, then please make a fresh profile and replicate the issue like above prior.
You must upload all the required log files, even if you think they are useless.
Failure to comply with ANY of the requirements may result in your issue being closed without further investigation.

Attachments

2024-04-24[09-57]_223.6, -0.6, -76.6_0.0, -0.6, 0.0, 0.8_6.81 (0).png (3193 KiB)
2024-04-24[10-00]_317.6, -3.5, 267.3_0.0, 1.0, -0.1, 0.3_7.06 (0).png (3328 KiB)

Originally written by Torm_Ozz

I'm not sure what the actual issue is here. You have not filled out the issue template correctly. Also, please note that v3.9.0 is under early active development and is no where near stable.

Originally written by Refringe


fixes skyplot labels [CPP-831]

reverts breaking changes from https://github.com/swift-nav/swift-toolbox/pull/802
fixes ReferenceError for visibility field

Frontend and Release Workflow Started here

frontend bench failing on CI fixes - can ignore

Frontend and Release Workflow Started here

To be honest, it's not clear what the regression was, i guess it was type errors of the m.trackingSkyPlkotStatus.labels & in the iterator of Keys.SATS?

yee that was case

might be worth thinking about how to add a few tests there, just because it should be relatively straightforward

yea unit tests would be nice... not sure how to go about it tho might be kinda funky tho. i.e. testing for UI changes / interactivity,
can use like https://doc.qt.io/qtforpython/overviews/qttestlib-tutorial1-example.html
maybe worth dropping a ticket in the backlog since i dont think we have any tests setup for python

Ok cool, if the infra isn't there on the UI side, scratch the unit testing bit. I do think it might be worth thinking about ways to add better testing to the UI side, but that is a bigger issue than this one PR.


Fix CF releases link that actually points to Diego releases

This is exceptionally confusing when you're trying to figure out what Diego version you should be using with your CF release.

Thanks, @Jonty!


luci-base: Update Japanese translation

・Update Japanese translation
Signed-off-by: musashino205<EMAIL_ADDRESS>

Please sign-off with your real name in future.

OK. I will change the name from the next commit.


cksum: failing GNU tests

The latest version of GNU's tests add tests/misc/cksum, tests/misc/cksum-a, tests/misc/cksum-c, and tests/misc/sm3sum, all of which currently fail. This will track the respective problems from each.

I suspect that this is because uu_cksum currently only takes file arguments, and does not implement any of the necessary options. The GNU Coreutils 9.0 docs for cksum list the following options:

[ ] -a/--algorithm
[ ] --debug
[ ] --untagged
All options supported by b2sum:

[ ] -l/--length
All options supported by md5sum:

[ ] -b/--binary
[ ] -c/--check
[ ] --ignore-missing
[ ] --quiet
[ ] --status
[ ] --tag
[ ] -t/--text
[ ] -w/--warn
[ ] --strict
[ ] -z/--zero

Investigating the codebase a bit further, I see that both md5sum and b2sum are implemented via hashsum. This suggests we should make cksum also be implemented by hashsum. I've checked off above all the options currently implemented by hashsum.

Looks like test/misc/b2sum is also failing, both because hashsum doesn't support -l/--length, and cksum doesn't support -a blake2b.
I'm going to try implementing this.

I made a bunch of progress on this and then ran out of time to finish the PRs. Picking this back up now; I'll rebase my current local work and get some initial PRs up.

Ugh, this is annoying: b3sum was added in https://github.com/uutils/coreutils/pull/3108, and its corresponding upstream binary defines -l/--length in bytes, whereas GNU Coreutils b2sum defines -l/--length in bits.
There are three options here:

Define -l/--length as bytes to match upstream b3sum. Given that compatibility with GNU Coreutils is being prioritised (per this issue), I think that would not be considered acceptable as b2sum would then never pass GNU tests.
Define -l/--length as bits to match GNU Coreutils. I really dislike this option, for two reasons:

--length being bits means it needs to be a multiple of 8, so 7/8 of values that upstream b3sum accepts will be rejected here. That's not so bad, it makes the difference discoverable.
In the cases where an upstream length is a multiple of 8, b3sum here would output 1/8 of the length, e.g. instead of a 16-byte hash the user gets a 16-bit hash (2 bytes). This is a TERRIBLE silent security issue.

Define -l/--length as bits when used with b2sum or cksum, and bytes when used with b3sum. This is awful for UX; in particular, it is undefined how hashsum should treat it. The least-bad option might be to just special-case the byte interpretation to b3sum, and not allow it to be used with -a blake3 on hashsum (otherwise hashsum would almost certainly end up conflicting with cksum if the latter adds BLAKE3 support).

We have a somewhat-similar issue in that hashsum itself defines a separate --bits flag for its SHA3 and SHAKE support, which is effectively duplicative of GNU Coreutils -l/--length. I'm not going to try solve that here.

cc @oconnor663 who wrote b3sum

While I really want GNU's compatibility, we workaround with upstream testsuite from time to time. See
https://github.com/uutils/coreutils/blob/main/util/build-gnu.sh#L121=
and below

Note that the suprising behaviour you mentioned in option 2 not only happens between b3sum implementations but also between different hashing algorithms. I.e. if I use the external b3sum first and then (GNU) b2sum, then the length does not match either. Hence, I think we bring back the consistency and should build what a hypothetical GNU b3sum would look like, not what another b3sum already does, to ensure compatibility/consistency with GNU and with the other utils in uutils.
I like the first option too, but it would indeed break GNU compatibility, so like Sylvestre mentioned, we'd have to work around the tests. Not to mention that it could be surprising for GNU users (although we'd err on the secure side).

Yeah, the inconsistency blows. Here are some scattered thoughts about why it ended up the way it is:

Unfortunately, different BLAKE2 interfaces have been inconsistent for a long time. CLIs and written naming conventions tend to use bits, but Python's hashlib.blake2b API takes the digest_size parameter in bytes. Similarly, C APIs usually take a size_t somewhere that counts bytes.

Measuring BLAKE2 output in bits makes sense from a security perspective. The security properties of BLAKE2b-512 and BLAKE2b-256 mirror those of SHA-512 and SHA-256. However, this relationship relies somewhat on BLAKE2b not allowing output sizes larger than its internal state size. For example, b2sum -l 1024 will just error out. The same doesn't apply to BLAKE3, though, which has a built-in XOF that'll give you as many output bytes as you like. "BLAKE3-512" (if we were to call it that) does not provide more security than the default 256-bit BLAKE3. I find this is a common source of confusion, so I discourage naming BLAKE3 instances in terms of bits, even though it can make sense on the small end.

Similarly, and again like SHA-512 and SHA-256, BLAKE2b-512 and BLAKE2b-256 are independent ("domain separated") hash functions. Changing the output length gives you a completely different hash. This is a natural design for those functions, since they can mix the output length in initialization one way or another. But for an XOF like BLAKE3, it's pretty common for the output length to be "who knows, we're gonna use this as a stream cipher", so domain-separating outputs of different lengths isn't always possible. Rather than having two modes for this, as BLAKE2X did, in BLAKE3 shorter outputs are always prefixes of longer ones. This is another reason why I discourage bit-counting names like "BLAKE3-512".

Which is all to say, that when there's a choice between counting bits and counting bytes, BLAKE3 pretty strongly prefers to count bytes. It keeps CLIs and library APIs consistent with each other, and it avoids some common points of confusion. But sometimes there isn't a choice, like our situation here, and then we suffer some inconsistency.

Interesting! That does make it clearer as to why b3sum is different. Maybe a solution could be to make a split API. So b2sum (and the other ones GNU supports) would accept a --bits option and -l would work but be deprecated/hidden. b3sum would accept a --bytes option and using the wrong argument would result in an error.

If you all decide to do something like --bytes, it might be reasonable to add a similar option upstream on b3sum, so that there's at least something we could tell people to do that'll work (or give a clear error message) everywhere?

Current coreutils b3sum generates hash *filename, but the original implementation by @oconnor663 uses a second space instead of an asterisk and refuses to check hashes if such character is missing as follows
$ b3sum -c B3SUMS
b3sum: Invalid space
b3sum: WARNING: 3 computed checksums did NOT match

We need to either discuss it or bring this part of coreutils into line.

It would appear this was fixed via #6499.


Some API documentation is blank (PubSub, Datastore, others)

Some of the API documentation pages are blank:

http://google-cloud-python.readthedocs.io/en/latest/pubsub/publisher/api/client.html
http://google-cloud-python.readthedocs.io/en/latest/pubsub/subscriber/api/client.html
http://google-cloud-python.readthedocs.io/en/latest/datastore/client.html
http://google-cloud-python.readthedocs.io/en/latest/monitoring/client.html

This makes it time consuming to develop with this SDK as one must drop into a pdb and inspect the objects you have in your hand.

Thanks for letting us know @robhaswell, that certainly is not the intention, it seems something is going wrong with our Read the Docs build.
Check out our gh-pages version of the docs:
https://googlecloudplatform.github.io/google-cloud-python/latest/pubsub/publisher/api/client.html
/cc @lukesneeringer

Those pages are all rendering correctly now.  Please feel free to reopen if you discover any others.


expose BearerTokenChallengeAuthenticationPolicy

fixes #18539

Is extracting shared parts of both policies something that is planned?

Is extracting shared parts of both policies something that is planned?

No plans, but I would expect us to slowly deprecate the non-challenge version as challenge handling becomes more common (which it will).

No plans, but I would expect us to slowly deprecate the non-challenge version as challenge handling becomes more common (which it will).

Can we replace the existing policy with the new one?

No plans, but I would expect us to slowly deprecate the non-challenge version as challenge handling becomes more common (which it will).

Can we replace the existing policy with the new one?

We could, as long as we have no concerns with swapping them out.

We could, as long as we have no concerns with swapping them out.

If the goal is to swap everyone to the new type anyway we should just go for it.

If the goal is to swap everyone to the new type anyway we should just go for it.

@pakrym Personally, I'd prefer to test the water with the libraries which need to handle challenges first, before we dive in and change everything.

Could we file an issue to deprecate BearerTokenAuthenticationPolicy in favor of this, and port other client libraries after we have some more usage?

Did the codeflow change much for policies that don't override the AuthorizeRequestOnChallengeAsync?

Did the codeflow change much for policies that don't override the AuthorizeRequestOnChallengeAsync?

Could we file an issue to deprecate BearerTokenAuthenticationPolicy in favor of this, and port other client libraries after we have some more usage?

We definitely can. Mostly trying to figure out whether the changes we've done are that scary.

#20704

#20704

Did the codeflow change much for policies that don't override the AuthorizeRequestOnChallengeAsync?

#20704

Did the codeflow change much for policies that don't override the AuthorizeRequestOnChallengeAsync?

No, it should be the same.

No, it should be the same.

So what are we afraid would break?

No, it should be the same.

So what are we afraid would break?

@schaabs - Any concerns? It's baked for a while in Key Vault with no issues.

Also, we would never be able to mark the original policy as [Obsolete] as that is a source-breaking change.


[Bug]: Code Freeze date for Core and Dashboard should be atleast 2 business days before code freeze for Plugins

Describe the bug
As per https://github.com/opensearch-project/opensearch-build/issues/3743, for 2.10.0, the code freeze date(code complete, release branch and version increments) for Core and Dashboard is set to 9/4 and for respective plugins to be part of 2.10.0 as well, it is same as seen: https://github.com/opensearch-project/job-scheduler/issues/424. The first RC cut is called out 9/5 as per https://opensearch.org/releases.html which means that all plugins alongwith core and dashboard need to be code, test complete, release branch and version increments by 9/4.
My concern is that, plugins are downstream of Core and Dashboard. So if there are any last minute changes to either Core/Dashboard on 9/4, downstream plugins which may get impacted would have 0 to less time to address the changes/fixes due to upstream changes.
My request here is to have Code freeze/release readiness date for both Core and Dashboard to be atleast 2 days before code freeze/release readiness for plugins.
To reproduce
N/A
Expected behavior
No response
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
No response
Additional context
No response
Relevant log output
No response

cc @CEHENKLE , @bbarani , @dblock , @navneet1v

This was hotly debated multiple times. Would this apply to all dependencies (e.g. many plugins depend on job scheduler)? Would an alternative of adding "feature complete", after which "breaking changes" aren't allowed, give us more flexibility and time?

This was hotly debated multiple times. Would this apply to all dependencies (e.g. many plugins depend on job scheduler)? Would an alternative of adding "feature complete", after which "breaking changes" aren't allowed, give us more flexibility and time?

Yes this does apply to JS plugin as well. My concern is if we know there is a dependency chain, we want to ensure whateve is the upstream, should be ready before downstream.

@bbarani Is https://github.com/opensearch-project/.github/issues the right place for this discussion?


Missing tests for undo/redo functionality

Write missing tests for the new classes added for undo/redo.

All tests that use assertCommandSuccess also test for undo now, as well as some other tests that I wrote, so i'm closing this for now.


Netskope: Fixed Pkg

Netskope: Fixed Pkg

Azure Sentinel to Microsoft Sentinel
Required items, please complete
Change(s):

Azure Sentinel to Microsoft Sentinel
Reason for Change(s):

Azure Sentinel to Microsoft Sentinel
Version Updated:

N/A

Testing Completed:

N/A

Checked that the validations are passing and have addressed any issues that are present:

N/A

@v-dvedak
Netskope Fixed Pkg v. 2.0.1. Changes "Azure Sentinel" to "Microsoft Sentinel".

Sorry. Looks like Netskope was already approved. Closing this PR.


Source release contains sereral files during the build phase.

Please answer these questions before submitting your issue.

Why do you submit this issue?
[x] Bug

Bug
From IPMC release check:

I see.

However that does not actually have a tag with the name '5.0.0-alpha'

Also, when I compare the contents of
apache-skywalking-apm-incubating-5.0.0-alpha-src.tgz with the tag,
there are several files in the source release that don't appear to
have a counterpart in the Git repo.

For example, apm-sniffer/apm-agent/dependency-reduced-pom.xml

skywalking-ui/*

That does not seem right

Fixed


Gaia player not working

Hello,
I've just set my TMDBHelper players through the link but Gaia add-on doesn't start the scraping. Maybe it should be updated? I don't know, thanks anyway in advance for your time and your help

This is the message from the dev who was very kind to answer to my request of Gaia integration.
"Thanks for reporting this. I've made the necessary changes. Please use Gaia v6.1.8 or later. It still has to be fixed from TMDBHelper's side.
I've noticed you already filed a ticket on TMDBHelper's github. Could you please post this link there as well:
https://github.com/gaiakodi/gaiasource/blob/938de3bf536b48ba399fd19990addfafed20dd0a/plugin.video.gaia/addon.py#L2399
There is a long comment I added in v6.1.8 to addon.py under the "scrape" endpoint. It describes all aspects of creating as scraping command, including various examples. They essentially just have to copy those examples and replace their parameters.
In the old TMDBHelper command they passed a bunch of unnecessary parameters, which are only internal to Gaia. You just have to pass 1 or more IDs, or the title+year. Gaia does the rest."


boringssl git fetch fail, and possible fix

change .gitmodules content to ->
[submodule "third_party/zlib"]
path = third_party/zlib
url = https://github.com/madler/zlib
[submodule "third_party/protobuf"]
path = third_party/protobuf
url = https://github.com/google/protobuf.git
branch = v3.0.0-beta-2
[submodule "third_party/gflags"]
path = third_party/gflags
url = https://github.com/gflags/gflags.git
[submodule "third_party/googletest"]
path = third_party/googletest
url = https://github.com/google/googletest.git
[submodule "third_party/boringssl"]
path = third_party/boringssl
url = https://github.com/google/boringssl.git
[submodule "third_party/nanopb"]
path = third_party/nanopb
url = https://github.com/nanopb/nanopb.git

someone else had done the same thing.


optimized: 优化安全组规则，支持逗号分隔的规则

这个 PR 实现什么功能/修复什么问题:

优化安全组规则update操作
支持不连续端口

是否需要 backport 到之前的 release 分支:

release/2.11

/area region
/cc @swordqiu @yousong

Codecov Report

Merging #3257 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #3257      +/-   ##
=========================================
+ Coverage    7.11%   7.11%   +<.01%
=========================================
  Files         480     480
  Lines       77788   77731      -57
=========================================
- Hits         5536    5534       -2
+ Misses      71789   71733      -56
- Partials      463     464       +1

Flag
Coverage Δ

#aFlag
7.11% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/compute/models/secgrouprules.go
5.05% <0%> (+1.14%)
:arrow_up:

pkg/util/seclib2/seclib.go
91.48% <0%> (-4.26%)
:arrow_down:

pkg/baremetal/tasks/stop.go
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

/approve
/lgtm


Add ms.custom tag for E2E scenarios

Docs Build status updates of commit 4b75c3a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/index.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

#sign-off

@rsameser - Please review.


#1069 Add isStrictlyBlank and isNotStrictlyBlank

Check List:

Fixes #1069
Unit tests : Yes
Javadoc with a code example (API only) : Yes

Adds isStrictlyBlank and isNotStrictlyBlank methods (which work the same as isBlank and isNotBlank, but with null counting as blank).

Closing this, as the requirements have changed slightly.


Does Kandinsky-3 support image mixing?

As title says. I know Kandinsky 2.1 does image mixing but curious if this is supported here as well. Thanks!

@aspctu please check-out https://github.com/ai-forever/kandinsky3-diffusers where we implemented IP-Adapter to mix images


Night mode and or other themes

Any plans on implementing night modes or other themes like in iBooks? Thanks.

I have no plan for that. It's a sample code to learn how to use PDFKit on iOS. I prefer to keep it as simple as possible.


 I'm looking to make a plugin that replicates the 2008 music update in RS3. I figured that would be doable as a plugin because sounds have no reason to be handled server side.
I've gotten the project all set up in IntelliJ and have played around with the features, but I haven't been able to find much regarding the music system. The only potentially useful thing I've found is the widget that holds the current playing music track.
I can see that VarPlayer has fields for unlocked music tracks, but I haven't the slightest clue how to read that.
Can anyone offer input? Ideally I would be able to read the song the game wants to play by name/ID, be able to play a song by name/ID, and read when the currently playing song ends. Other behavior I could construct around that.
If APIs to work with the music system don't exist, this can be considered a feature request for this plugin, and potential others that may want to interact with the music system.

We don't have much of the music API reversed. The varplayers for music tracks we no longer use since Jagex added the music indicator feature to the main client, but you can see example usage from the old music indicator plugin: 732db3940f60fd9a7b275d3700afe9baf9bc1f1d. They wouldn't tell you what is playing currently though I think. I'd have to look into how to access that, though you could maybe just read the track name off of the interface.

Thanks for pointing me to that code, it would be very helpful when implementing the plugin as I would need to know which music the player has unlocked when deciding which track to play. It also looks like that it has the capability to map from id to name and back, which is good.
I've figured out how to read the currently playing music track name from the GUI widget, so at this point I would be able to get all the way through choosing a song to play.
So theoretically all I'd need is the ability to start a song playing. Though if I'm reading off the GUI, starting a new song would probably mess with that, which may or may not be handleable.

Jagex's music system appears to be an insurmountable obstacle in this case and I have given up trying to find my way through it.

Re-opening as this is a valid request, we just haven't gotten around to doing the API development work for this.