fix(parsing-rules): fix assignment timing when number is found in type

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Current Examples/Sniffator is an empty app

I'm learning how to use ble-plx now, however the examples/Sniffator is an empty app for RN v0.51. Could your team update this example?

Hello,
The Sniffator example app is currently under an update procedure #189 . You can check out the progress on example_app_update branch or an older commit from before #190

@dariuszseweryn I've also complete a working sample myself with most of the functions. So thanks, I'm looking forward to the new sample though.


31- Next Permutation Leetcode

#51
Cpp code for Next Permutation on Leetcode

@GuptaTanisha Great Work 👍🏻 Merged!


Rewriting SSH Public Keys Fails After Migration

Description
I have migrated my Gitea database, copied all configuration files exactly as they were previously, and renamed all configuration code and system directories to the correct new names wherever they needed to be changed. When I start the Gitea service on the new system, the logs are able to find the new binary, configuration file, and /var/lib/gitea/ directory; however, they state Unable to MkDirAll(/var/lib/<old_name>/.ssh): mkdir /var/lib/<old_name>: permission denied.
There are no references to the old name in the configuration file, and the database and database user have been renamed correctly. It seems Gitea is attempting to create a new directory under the old directory name, despite everything being changed.
Gitea Version
1.21.7
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
https://gist.github.com/inferenceus/2960870b3fbaeba808787832a02eec6c
Screenshots
No response
Git Version
2.43.0
Operating System
Gentoo Linux
How are you running Gitea?
Compiled from source via Gentoo Linux package manager, using GURU repository.
Database
PostgreSQL

Can you double-check your app.ini?
https://github.com/go-gitea/gitea/blob/2df38af752c13ca02a899d6a53848c68259d3336/models/asymkey/ssh_key_authorized_keys.go#L134-L138
setting.SSH.RootPath should be sourced from the config.
If it's not explicitly set, it is derived from the current user
https://github.com/go-gitea/gitea/blob/db545b208b4bd3d1961c519da66ee2b4421afa5c/modules/util/path.go#L248-L266
https://github.com/go-gitea/gitea/blob/2df38af752c13ca02a899d6a53848c68259d3336/modules/setting/ssh.go#L114

setting.SSH.RootPath should be sourced from the config.
If it's not explicitly set, it is derived from the current environment

Awesome. I didn't know that. It works flawlessly. Thanks for the help.


copy_message: Remove weird white background displayed on hover.

The white background is coming from bootstrap, we override it
here.

@amanagr The common styling across all the copy buttons in the frontend is done by a base class copy_button_base in zulip.css. It might be better to add the on-hover changes there.

This lgtm but I agree with @sumanthvrao it'd be better to do this in the base class if we can.

Thanks, @sumanthvrao, for the review. Updated!

Closing as this was linkely fixed in another PR or when we switched the icon.


CSS class names for buttons

Are there plans to send the CSS class names for the buttons along with the name and listener?
It would come in handy for styling especially with Bootstrap.

hi @emilian the name of the button will transfer to the button's classname, I think the name is what you want.
 this.state.buttons.map(function (button, i) {
            return React.createElement('button', {
              id: button.name.toLowerCase(),
              key: i,
              className: button.name.toLowerCase(),
              onClick: this.handleClick
            }, button.name)
          }, this)

Here is the demo

   <span data-reactid=".<IP_ADDRESS>:$0">Simple example with one button and listener
   <div class="buttons" data-reactid=".<IP_ADDRESS>">
       <button id="close" class="close" data-reactid=".<IP_ADDRESS>.$0">close</button>

Thanks for the reply.
Actually I want to keep the class name and the button name separate. It would be good to have another property for the CSS classes along with name and listener. Something like this:
buttons: [{
    name: 'close',
    listener: function() {

    },
   cssClasses: 'btn btn-default'
}],

@emilian I get it. I will add additional property className.And change it like
 this.state.buttons.map(function (button, i) {
            return React.createElement('button', {
              id: button.name.toLowerCase(),
              key: i,
              className: button.className ? button.className :  button.name.toLowerCase(),
              onClick: this.handleClick
            }, button.name)
          }, this)

Is it fine for you ?

Yes, that would be perfect. Thanks xeodou.

@emilian I am already push the new code. You can upgrade the package through npm.

I upgraded yesterday and it is working just fine. Thanks for the quick turnaround!

It;s fine.


This project code is lost. Time, Token and Money is lost. Can you get this fixed?

Describe the bug
I have created this project but the code is not available after reloading the project. If you are not able to restore the project. Need the tokens to be refunded.
Link to the Bolt URL that caused the error
https://bolt.new/~/bolt-vite-react-tnspc3
Steps to reproduce
Load the project.
Expected behavior
Loading the project should load all the code that was generated.

Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>
performance.memory = {
  "totalJSHeapSize": 117020089,
  "usedJSHeapSize": 113010765,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = jpmirrar
Chat ID = 36d1e0c231b1

Additional context
No response

Hi @jpmirrar,
Appreciate the feedback here! We are aware of this issue with chat persistence. Temporary workarounds and updates can be found here: #39. You can go to stackblitz.com, login with your Bolt credentials, click Collections on the left-hand side, and then open Bolt Collection. Appreciate your patience as improvements continue to be made. Refund requests are handled by reaching out to<EMAIL_ADDRESS>

@endocytosis The issue for me is not about the chat but the code itself is lost, it is not available in StackBlitz. I only have the boilerplate code generated but the code that was created using bolt.new is completely lost.
This happened when I selected the React as a choice to create the project in bolt.new. Whereas when I created any project without selecting the templates available in the bottom of the page then it is working as expected.
This issue is not the same as #39.


When generating depth images, use torch_compile with ZoeDepth for compatibility

(e.g. for systems needing https://github.com/nerfstudio-project/nerfstudio/pull/1982)

(not sure what's up with the Pyright complaints, given the small changes)

Runtime errors encountered; may need to redo.

Previously the compatibility utility torch.compile worked for functions, but not for modules as torch.compile was originally employed here.  (See https://pytorch.org/tutorials/intermediate/torch_compile_tutorial.html for usage.)

Pyright failure is not a functional issue, see https://github.com/pytorch/pytorch/issues/81462 for more details.

Related to #2305 @ethanweber if you want to sanity check.
(See https://github.com/nerfstudio-project/nerfstudio/pull/2305#issuecomment-1666067515)

(Made Pyright happy.)

(readthedocs check is stuck, 404 details, not sure how to re-run)


In libraries, add sampling over nuisance parameters / uncertainties in the parameters that are NOT being varied over.

For example, in the Double Schechter GSMF, there are well characterized uncertainties in the fit parameters.  The existing option is to use distributions for these parameters, over their quoted uncertainties - adding a dimension to the parameter space.  Should also implement a method where these are randomly sampled over, but not explicitly a dimension of the parameter space.

See also: https://github.com/nanograv/holodeck/issues/48

I think it's best to introduce these a new parameters that are being varied over, you can just ignore them.  It's a benefit of the latin hypercube that this shouldn't decrease performance or sampling otherwise.


use condition properly  fix #1917

What is the purpose of the change
use condition properly  fix #1917
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #3086 into master will increase coverage by 0.02%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master    #3086      +/-   ##
============================================
+ Coverage     63.43%   63.45%   +0.02%
  Complexity       75       75
============================================
  Files           653      653
  Lines         28261    28261
  Branches       4820     4820
============================================
+ Hits          17926    17932       +6
+ Misses         8057     8039      -18
- Partials       2278     2290      +12

Impacted Files
Coverage Δ
Complexity Δ

...org/apache/dubbo/registry/redis/RedisRegistry.java
39.26% <0%> (+6.49%)
0 <0> (ø)
:arrow_down:

...ache/dubbo/remoting/transport/AbstractChannel.java
75% <0%> (-12.5%)
0% <0%> (ø)

.../remoting/transport/netty4/NettyClientHandler.java
75% <0%> (-11.12%)
0% <0%> (ø)

.../dubbo/remoting/transport/netty4/NettyChannel.java
61.17% <0%> (-4.71%)
0% <0%> (ø)

...he/dubbo/remoting/transport/netty/NettyServer.java
67.85% <0%> (-3.58%)
0% <0%> (ø)

.../apache/dubbo/remoting/transport/AbstractPeer.java
58.69% <0%> (-2.18%)
0% <0%> (ø)

...dubbo/metadata/support/AbstractMetadataReport.java
69.35% <0%> (-1.62%)
0% <0%> (ø)

...dubbo/remoting/exchange/support/DefaultFuture.java
71.81% <0%> (-1.35%)
0% <0%> (ø)

...pache/dubbo/registry/support/AbstractRegistry.java
80.82% <0%> (-1.13%)
0% <0%> (ø)

...pache/dubbo/remoting/transport/AbstractServer.java
47.91% <0%> (-1.05%)
0% <0%> (ø)

... and 2 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 5ea4fa5...79af072. Read the comment docs.


Application error: a client-side exception has occurred (see the browser console for more information).

The page went white blank and displayed this when I clicked the "Fetch next sequence" button. The account I was fetching for had just been created, or was in the process of being created.

Application error: a client-side exception has occurred (see the browser console for more information).

@leighmcculloch, Could you please provide more details on the steps you took to see the application error? I can't reproduce it.
I get an "Account not found" error when fetching the sequence number for an account that is not funded.

When the fetch method throws an error, it's handled properly (manually throwing "Something went wrong" from the method).

Unfortunately that's all the info I have. I can't reproduce it. It was a one time it occurred. It must be very sensitive to timing.

Will revisit when we have sentry

Cannot replicate. We will reopen this issue if needed.


Edit multi-reddit does nothing

Go to a multi-reddit, click three lines at bottom right to bring up menu, click manage multi-reddit, click Edit multi-reddit, no effect

Going to expand on this, we can show the subreddits in the top banner area that single subreddits use for quick links

Done for the next update!


Mac framework_tests_impeller is super flaky on widgets.shader_mask.bounds.matches_top_left

It has been flaky 10 times in recent commits:
Example builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac framework_tests_impeller/126/overview
10:41 +14681 ~142: /Volumes/Work/s/w/ir/x/w/flutter/packages/flutter/test/widgets/shader_mask_test.dart: Bounds rect includes offset visual inspection
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following SkiaException was thrown while running async test code:
Skia Gold received an unapproved image in post-submit
testing. Golden file images in flutter/flutter are triaged
in pre-submit during code review for the given PR.

Visit https://flutter-gold.skia.org// to view and approve
the image(s), or revert the associated change. For more
information, visit the wiki:
https://github.com/flutter/flutter/wiki/Writing-a-golden-file-test-for-package:flutter

Debug information for Gold --------------------------------
stdout: Given image with hash d051cff927d4ce28ab72215e43a2fb2b for test
widgets.shader_mask.bounds.matches_top_left
Expectation for test: 084ddbbcf1a5fc0c30e4c871a29ee072 (positive)
Expectation for test: 09c634d298e4513100f38d957eaaf179 (positive)
Expectation for test: 16fe16898a0e94260e913f2ecf55beaf (positive)
Expectation for test: 52f8861d4f9e3b8ef600c63626d74bec (positive)
Expectation for test: 56afb5fedead66f585d0db73be201a1c (positive)
Expectation for test: 85543c08c4e66a2fc737c14b6c68763b (positive)
Untriaged or negative image:
https://flutter-gold.skia.org/detail?grouping=name%3Dwidgets.shader_mask.bounds.matches_top_left%26source_type%3Dflutter&digest=d051cff927d4ce28ab72215e43a2fb2b

stderr: Test: widgets.shader_mask.bounds.matches_top_left FAIL

result-state.json: No result file found.

When the exception was thrown, this was the stack:
#0      SkiaGoldClient.imgtestAdd (package:flutter_goldens/skia_client.dart:252:7)
<asynchronous suspension>
#1      MatchesGoldenFile.matchAsync.<anonymous closure> (package:flutter_test/src/_matchers_io.dart:118:32)
<asynchronous suspension>
<asynchronous suspension>
#3      _expect.<anonymous closure> (package:matcher/src/expect/expect.dart:123:26)
<asynchronous suspension>
<asynchronous suspension>
#5      expectLater.<anonymous closure> (package:flutter_test/src/widget_tester.dart:512:24)
<asynchronous suspension>
#6      main.<anonymous closure> (file:///Volumes/Work/s/w/ir/x/w/flutter/packages/flutter/test/widgets/shader_mask_test.dart:107:5)
<asynchronous suspension>
#7      testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:183:15)
<asynchronous suspension>
#8      TestWidgetsFlutterBinding._runTestBody (package:flutter_test/src/binding.dart:1018:5)
<asynchronous suspension>
<asynchronous suspension>
(elided 3 frames from dart:async and package:stack_trace)

The exception was caught asynchronously.
════════════════════════════════════════════════════════════════════════════════════════════════════

10:41 +14681 ~142 -1: /Volumes/Work/s/w/ir/x/w/flutter/packages/flutter/test/widgets/shader_mask_test.dart: Bounds rect includes offset visual inspection [E]
  Test failed. See exception logs above.
  The test description was: Bounds rect includes offset visual inspection

Disabled in https://github.com/flutter/flutter/pull/144573, keeping this open for tracking.


Clean up leaking threads

Closes #1458
Should be merged into 4.2 and likely 4.1.

+1

dffsdkfjksdfsdfkkjsdkfsd

Created https://issues.apache.org/jira/browse/LOG4J2-1259

+1 on this. The original dangling threads issue should be left open with a link to the log4j2 issue though

Yup. I'll keep it open to see what log4j has to say. Thanks all.


request example for GET /{db}/_shards/{docid} is replaced with its response

refrence
current request
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Length: 94
Content-Type: application/json
Date: Fri, 18 Jan 2019 20:08:07 GMT
Server: CouchDB/2.3.0-9d4cb03c2 (Erlang OTP/19)

expected request:
GET /db/_shards/{docid} HTTP/1.1
Accept: */*
Host: localhost:5984

Closing as fixed by @jiahuili430


works beautiful - thanks a lot

Just installed Version 1.0.0 and tried it out.
Work as expected and beautifully.
My workflow to use this node is at the moment like this:

get the JSON from the previous node in n8n
goto JSONata Playground
paste the JSON into the left side
write and test my JSONata "statement"
once working, copy the JSONata statement
paste it into the n8n-jsonata node as the query

Absolutely easiest way to refactor/filter/rearrange some JSON data!
Thanks a lot for this node!

@cellerich somehow i overlooked the comment.
Thanks for the kind words, even though I no longer use n8n myself, I'm glad that the node helps other people.


[web-app-manifest.json] Add partial support for FireFox

Add partial support for FireFox, implemented in Android only (from v58):
https://www.mozilla.org/en-US/firefox/android/58.0/releasenotes/
Also added a few keywords to make it easier to find in search.

Firefox for Android is already covered by and_ff so I think adding it to just "Firefox" is redundant. Feel free to add the keywords in another PR however.


optimize rosa scheduled workflow to run reduced combinations

Fixes #900
Trim the ROSA Scheduled workflow to only two combinations

ROSA Scheduled Create Active/Active cluster with Volatile Sessions and External Infinispan
ROSA Scheduled Create Active/Active cluster with Persistent Sessions and External Infinispan

Working run: https://github.com/kami619/keycloak-benchmark/actions/runs/10123478369

Open question to discuss in the meeting today. Should we remove the old A/P code to reduce the things we need to maintains as it's still available in the 0.13 branch if required?

@ryanemerson @pruivo Thank you for the reviews, I addressed your comments and will merge this so we have a run tomorrow


ci: try resolve load locally custom gh-action

Description
For custom github action to load, let's try to use actions/checkout first before loading it.
Reference: https://github.community/t/path-to-action-in-the-same-repository-as-workflow/16952/2
If it still doesn't worked, I think I will put duplicated step for build 2 image in workflow.yml

:tada: This PR is included in version 1.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Test helper to await Durable Object's alarms

We would like to test the side effects in our alarms, but the best way to do it now seems to be sleeping in tests for MAX_ALARM_TIMEOUT (which can slow tests down significantly), or mocking an internal function used in alarm via jest.
Would it be a good idea to expose a similar API to res.waitUntil() (e.g., await res.waitForAlarms()), which optionally accepts an argument to change the alarm interval, so they can be tested instantly?

Hey! I wanted to work on this for myself too.
I've been thinking more along the lines of:
global.flushDurableObjectAlarms(ids?: DurableObjectId[])

Where no ids specified means to call all existing alarms.
I'll try to find time this week to add this.


[Shortcircuit] Add documentation about new parameters

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?
Docs update
What is the new behavior (if this is a feature change)?
New parameters were added to the API. This PR is to document them.

@annetill, @So-Fras, if one of you would have time to review this addition to the documentation it would be great.
It's about the new parameters that were added (some time ago) for the short circuit analyses.
Many thanks


Support array result for common action and sequence action

Description

POEM document pr: https://github.com/apache/openwhisk/pull/5244
This feature is:  provide support array result feature for common action and sequence action. e.g.

Support array result for common action

# cat ~/hello-array.js
function main(params) {
    console.log("-------------log test---------")
    return [{"key1":"value1"},{"key2":"value2"}];
}

# wsk -i action create hello-array-nodejs --kind nodejs:10 ~/hello-array.js
# wsk -i action invoke hello-array-nodejs -r -v
REQUEST:
[POST]	http://xxx.xxx.xxx.xxx:10001/api/v1/namespaces/_/actions/hello-array-nodejs?blocking=true&result=true
...
...
Response body size is 37 bytes
Response body received:
[{"key1":"value1"},{"key2":"value2"}]

Support array result for sequence action

# cat ~/split.js
function main(msg) {
    var separator = msg.separator || /\r?\n/;
    var lines = payload.split(separator);
    return lines;
}

# cat ~/sort.js
function main(msg) {
    var lines = msg || [];
    lines.sort();
    return lines;
}

# wsk -i action create /whisk.system/utils/split --kind nodejs:10 ~/split.js
# wsk -i action create /whisk.system/utils/sort --kind nodejs:10 ~/sort.js
# wsk -i action create mySequence --sequence /whisk.system/utils/split,/whisk.system/utils/sort
# wsk -i action invoke --result mySequence --param payload "bbb\ncccc\naaaa"  -r -v
REQUEST:
[POST]	http://xxx.xxx.xxx.xxx:10001/api/v1/namespaces/_/actions/mySequence?blocking=true&result=true
...
Response body size is 22 bytes
Response body received:
["aaaa","bbbb","cccc"]

Activation check in elasticsearch

# curl -u xxx:xxx -H "Content-Type: application/json" '[http://xxx.xxx.xxx.xxx:9200/lambda-exp_whisk.system/_search?pretty=true' -d  '{
  "query" : { "match" : { "activationId" : "9cc4dad8d81342fc84dad8d81302fc54" }},
  "from":0,
  "size":1
}'
{
  "took" : 3,
  ...
  "hits" : {
    "total" : 1,
    "max_score" : 5.1628795,
    "hits" : [
      {
        "_index" : "lambda-exp_whisk.system",
          ...
          "logs" : [
            "2022-07-21T06:53:16.543515915Z stdout: -------------log test---------"
          ],
          "name" : "hello-array-nodejs",
          ...
          "response" : {
            "result" : "[{\"key1\":\"value1\"},{\"key2\":\"value2\"}]",
            "size" : 37,
            "statusCode" : 0
          },
          ...
        }
      }
    ]
  }
}

# curl -u xxx:xxx -H "Content-Type: application/json" '[http://<IP_ADDRESS>:9200/lambda-exp_whisk.system/_search?pretty=true' -d  '{
  "query" : { "match" : { "activationId" : "9c774fe852de44cdb74fe852de94cd54" }},
  "from":0,
  "size":1
}'
...
          "response" : {
            "result" : "[\"aaaa\",\"bbb\",\"cccc\"]",
            "size" : 21,
            "statusCode" : 0
          }
...

The response.result must use text to store, because different activation's same filed may use different type, e.g.
one activation's result's name filed value is string , e.g. {"name": "jack"}
another activation's result's name filed value is int, e.g. {"name": 12}
Elasticsearch doesn't support this, it store like this, it would report error.

Other works

As above example, we already know, nodejs runtime supports this feature by default.
But other runtimes(e.g. go, java, php, etc) don't support,

After this pr merged, there still has other works for runtime images, need to support subsequent prs for other images.
And in CLI side, still has small mount works to parse the JSON array string to user.

Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[x] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Scheduler
[x] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[x] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[x] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[ ] I signed an Apache CLA.
[ ] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

Codecov Report

Merging #5290 (460fdff) into master (a03507c) will decrease coverage by 75.34%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #5290       +/-   ##
==========================================
- Coverage   79.90%   4.56%   -75.35%
==========================================
  Files         238     238
  Lines       14161   14184       +23
  Branches      603     586       -17
==========================================
- Hits        11316     648    -10668
- Misses       2845   13536    +10691

Impacted Files
Coverage Δ

.../org/apache/openwhisk/core/connector/Message.scala
15.38% <0.00%> (-60.91%)
:arrow_down:

...whisk/core/containerpool/AkkaContainerClient.scala
0.00% <0.00%> (-78.73%)
:arrow_down:

...pache/openwhisk/core/containerpool/Container.scala
2.15% <ø> (-88.18%)
:arrow_down:

...e/elasticsearch/ElasticSearchActivationStore.scala
0.00% <0.00%> (-77.91%)
:arrow_down:

...pache/openwhisk/core/entity/ActivationResult.scala
0.00% <0.00%> (-90.67%)
:arrow_down:

...cala/org/apache/openwhisk/http/ErrorResponse.scala
44.55% <0.00%> (-44.56%)
:arrow_down:

...org/apache/openwhisk/core/controller/Actions.scala
0.00% <0.00%> (-90.79%)
:arrow_down:

...core/controller/actions/PostActionActivation.scala
0.00% <ø> (-100.00%)
:arrow_down:

...isk/core/controller/actions/PrimitiveActions.scala
0.00% <0.00%> (-86.42%)
:arrow_down:

...hisk/core/controller/actions/SequenceActions.scala
0.00% <0.00%> (-80.00%)
:arrow_down:

... and 213 more

It generally looks good to me. So it is not a breaking change and there would be no issue with the existing features, right? Do we have to merge this before merging all runtime changes?

Yes, has no issue.
Should merge this first, because other runtime prs depend on this pr.

Have any comment, due to there exist several runtime pr depend on this pr, so i just asked.


ZBase.Foundation.Mvvm.Unity.ViewBinding.MonoBinder  Reduce GC

FindNearestContext does not require 'new List()'

Fixed in https://github.com/Zitga-Tech/ZBase.Foundation.Mvvm/commit/a4ce7ffaf6a6d749cd92c09fbec8a0e409970a67


Updated documentation

What Does This PR Do?
Updated the Readme files with selected changes made by the interns.
Where Should The Reviewer Start?
How Should This Be Manually Tested?
Background Context
Screenshots
Checklist (if applicable):
[ ] item 1
[ ] item 2
[ ] item 3
[ ] item 4
[ ] item 5

@Debadri-Redapple Please review this PR and then I can merge this.

@drxeno02 Please review this PR and then I can merge this.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 334

Questions ?
Please refer to the Backport tool documentation


Create Clinical Trial .yaml schema

The Wikidata folks participating in the Virtual Biohackathon for Covid-19 will be working out the schema for clinical Trials in Wikidata next week. Would make sense to work on this then.


Scheduler caught exception

hello,
I have a Dashing dashboard using the spreadsheet gem, everything works correctly but after about 30 minutes Scheduler throws a fit in the console window.
Any ideas?
thanks.
scheduler caught exception:scheduler caught exception:
scheduler caught exception:scheduler caught exception:
================================================================================scheduler caught exception:
scheduler caught exception:
Too many open files - /tmp/oo_20150330-8033-9yqvkx/.
scheduler caught exception:
scheduler caught exception:
/var/lib/gems/1.9.1/gems/spreadsheet-1.0.1/lib/spreadsheet.rb:71:in `initialize'
Too many open files - /home/administrator/manchvegas/xls/newcases.xls

Hello,
it says "Too many open files - /home/administrator/manchvegas/xls/newcases.xls".
Your code seems to open files and not close them. Fix this by closing the files.
Closing the issue since it is not a rufus-scheduler issue.
Kind regards.


Chiral note

Implements chirality as annotation. This PR also refactors the dialect a bit. Now types need to be provided explicitly, to be able to assign None as default. Attributes with None value are filtered out. It is a design choice but I kind of like the pysmiles convention in this regard.

@pckroon yes they are;

I don't care enough to not want them to be.


Adds modal version with bootstrap without jquery

This PR supports using the bootstrap package in version 4.6 and 5 without using Jquery.
Some changes were made in the Modal component and in the modal.js file and also in the tests to be able to call 3 variables that bootstrap controls.
By default I put a configuration file for the user to select the css framework of their choice, but tailwind will be loaded without configuration.

Hi @luanfreitasdev,
Thanks for the PR but for now I'm only supporting Tailwind CSS (https://github.com/livewire-ui/modal/issues/23).
In the future, I might add a non-CSS framework version depending on demand.

Any advance? i really need this

@kevin4dhd feel free to fork this repository and create a Bootstrap / jQuery version.

@luanfreitasdev do you've got a working fork?

@Restingo
Hi, there's this branch, see if it works please
https://github.com/luanfreitasdev/modal/tree/feature/bs-modal
Thank you

@luanfreitasdev I'm getting the following error:
Uncaught TypeError: Cannot read property 'querySelector' of undefined
    at modal.js:1
    at ge (cdn.min.js:5)
    at cdn.min.js:5

@Restingo
did you put modal.js from that same repo?
You will have to manually put and clear the cache

@luanfreitasdev yes I'm using the same files and also cleared local and browser caches.

@luanfreitasdev I've added x-ref="{{ $id }}" to bootstrap.blade.php like the following, now the error is gone:
<div
    id="{{ $id }}"
    x-ref="{{ $id }}"
    class="modal fade" tabindex="-1" role="dialog"
    aria-hidden="true"
>

Can you please check? But there is also stuff like x-show.immediate="activeComponent == '{{ $id }}'" missing?

@luanfreitasdev also when I'm closing the modal with ESC or X the gray background still stays and needs another ESC to hide.

@luanfreitasdev any news?

@luanfreitasdev Thanks for this.
We've been using for production with some minor tweaks. It would be great if this pull request was accepted and supported with the official package.

Thanks @RishabSwift, @Restingo  ,
I redid the installation in a new project and it worked perfectly without needing to change anything.

@luanfreitasdev, some minor bugs I have noticed

When you have a child modal with a different width set through bsModalWidth(), then it does not work as expected. For example, if the parent width is lg and the child width is sm, then the child's class becomes modal-lg modal-sm (notice the parent modal's class gets carried over to the child modal).
When you open a child modal and dismiss it, the modal is dismissed but backdrop drop of the child modal remains. You have to press esc to remove the backdrop. For example, if you open a parent modal, and open a child modal, then dismiss the child modal, then open the child modal again, you have to press esc twice to dismiss it. I think this is what @Restingo is referring to.

Hello, @RishabSwift
what changes did you need to make to make this part work, can you share with us?
Thank you!

@luanfreitasdev ,
How can I install your fork ?
Many thanks in advance for your feedback.

@luanfreitasdev ,
How can I install your fork ?
Many thanks in advance for your feedback.

Were you able to install this? I need it too

For anyone interested in installing this version via composer, follow the steps below
Add the package to your composer under require section
"livewire-ui/modal": "dev-feature/bs-modal",
Then add this new value as the composer's new root value
,
  "repositories": [
    {
      "type": "vcs",
      "url": "git@github.com:luanfreitasdev/modal.git"
    }
  ]

Then run composer update
You will ask for a token from GitHub if you add this for the first time, visit the link which gave in the terminal and get the token.

composer update
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- illuminate/support[v8.0.0, ..., v8.11.2] require php ^7.3 -> your php version (8.1.6) does not satisfy that requirement.
- Root composer.json requires laravel/ui ^4.0 -> satisfiable by laravel/ui[v4.0.0, v4.0.1, v4.0.2, 4.x-dev].
- Conclusion: don't install laravel/framework v9.20.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.21.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.21.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.21.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.21.3 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.21.4 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.21.5 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.21.6 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.22.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.22.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.23.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.24.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.25.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.25.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.26.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.26.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.27.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.28.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.29.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.30.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.30.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.31.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.32.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.33.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v9.34.0 (conflict analysis result)
- livewire-ui/modal dev-feature/bs-modal requires livewire-ui/livewire-ui ^0.1.0 -> satisfiable by livewire-ui/livewire-ui[0.1.0].
- Root composer.json requires livewire-ui/modal dev-feature/bs-modal -> satisfiable by livewire-ui/modal[dev-feature/bs-modal].
- Conclusion: don't install laravel/framework v9.19.0 (conflict analysis result)
- livewire-ui/livewire-ui 0.1.0 requires illuminate/support ^8.0 -> satisfiable by illuminate/support[v8.0.0, ..., 8.x-dev].
- Only one of these can be installed: illuminate/support[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev], laravel/framework[v9.19.0, ..., 9.x-dev]. laravel/framework replaces illumi
nate/support and thus cannot coexist with it.
- Root composer.json requires laravel/framework ^9.19 -> satisfiable by laravel/framework[v9.19.0, ..., 9.x-dev].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The Pro version includes a modal and slide-over that work with Bootstrap but does require Alpine.


Revert "Pin Python 3.7 version in CI for macos-latest"

This reverts commit 2935166fac26e5961b54e02b477a26ddc90baa96.
Contributor Checklist:

[ ] I have added or updated my entry in the creators.json file
[ ] I have added a changelog entry for my contribution
[ ] I have added/updated documentation for all user-facing changes
[ ] I have added/updated test cases

Reviewer Checklist:

[ ] /azp run libertem.libertem-live-data passed

/azp run libertem.libertem-live-data


Open pull requests

I would just like to ask about the 2 open pull requests that other people have made; they are both features I would find useful (esp the timestamp parser). Since the code has already been written and is waiting for review, is there any timeline on when (if at all) those features could be merged into the main project so we can use them?

I'll look into them... The date thingy is incomplete and the timestamp thingy is not well implemented in some areas. That's the general problem with PR's. Most of the time you're faster if you just do it yourself.


conda mambabuild failing with "KeyError: Dist" again

I think the problem discussed in #88, #103 and #104 may have reappeared.

boa                       0.6.0            py37h03978a9_0
conda                     4.10.3                   pypi_0
conda-build               3.21.4           py37haa95532_0
mamba                     0.15.0                   pypi_0
python                    3.7.10               h6244533_0

Traceback (most recent call last):
File "C:\Miniconda\Scripts\conda-mambabuild-script.py", line 10, in
sys.exit(main())
File "C:\Miniconda\lib\site-packages\boa\cli\mambabuild.py", line 142, in main
call_conda_build(action, config)
File "C:\Miniconda\lib\site-packages\boa\cli\mambabuild.py", line 127, in call_conda_build
**kwargs,
File "C:\Miniconda\lib\site-packages\conda_build\api.py", line 195, in build
variants=variants
File "C:\Miniconda\lib\site-packages\conda_build\build.py", line 3079, in build_tree
test(pkg, config=metadata.config.copy(), stats=stats)
File "C:\Miniconda\lib\site-packages\conda_build\build.py", line 2871, in test
is_conda=metadata.name() == 'conda')
File "C:\Miniconda\lib\site-packages\conda_build\environ.py", line 907, in create_env
display_actions(actions, index)
File "C:\Miniconda\lib\site-packages\conda\exports.py", line 236, in display_actions
actions['LINK'] = [index[d] for d in actions['LINK']]
File "C:\Miniconda\lib\site-packages\conda\exports.py", line 236, in
actions['LINK'] = [index[d] for d in actions['LINK']]
KeyError: Dist(channel='file://c:/workspace/XXX_master/conda-bld', dist_name='xxx-2.55.0+master.0.7ad9d1-py_0', name='xxx', fmt='.tar.bz2', version='2.55.0+master.0.7ad9d1', build_string='py_0', build_number=0, base_url=None, platform=None)

Things I would note are:

It seems like this may be Windows-specific, or at least it seemed to still work on the parallel Linux build that happens in our Jenkins setup.
It's a noarch build.
As you can see in the output, we tell conda-build to output under a local subdirectory, via the CONDA_BLD_PATH env var.

Let me know if there's anything else I can provide.
(Side note: I think the pypi versions reported there are an artifact of the environment having been created with micromamba?)

Sorry for the bug! Indeed we just merged a new implementation of the Channel class that is probably responsible for this regression. For now you could pin to mamba 0.14 and boa 0.5 until this is fixed

@afranchuk maybe you've got some insight here

More specifically, the semantics of channel specifications has changed, so there may be remaining mismatch within consuming implementations. It's not immediately clear to me (mostly due to unfamiliarity with boa) how that is interacting with the conda api calls, but I'll read through the source.

The only thing I see probably incorrect is https://github.com/mamba-org/boa/blob/defd5fa66cd6e7c7661c480a48ce63c13c842011/boa/core/solver.py#L55-L60.
Two things that stand out: you seem to want the url without credentials, but c["url"] has credentials (c["channel"].url(with_credentials=False) would do the trick I think), and the final split_anaconda_token(remove_auth(x)[0] is exactly what was the problem in the mamba index command: remove_auth does not correctly parse windows uris. See https://github.com/mamba-org/mamba/blob/master/mamba/utils.py#L309-L315.
Also note that since that should be a url without credentials, maybe the remove_auth/split_anaconda_token isn't necessary? Technically the split_anaconda_token may be, but remove_auth certainly shouldn't be needed.

I probably am experience the same problem in https://github.com/robotology/robotology-superbuild/issues/822 when a dependency exist just in the local channel. Interestingly, for me the issue only occures on Windows.

I'll fix it later today. Sorry folks!

I'll fix it later today. Sorry folks!

No hurries, I'll try to pin mamba and boa.

@afranchuk any chance you know how to fix this?
on Windows, the local channel coming from mamba seems to have file://c/mychannel/... format, or file://c:/mychannel -- that's why there is the key error.
Gotta investigate it a bit more tomorrow, but should be fixable :)

Well yeah, it's the same workaround as I linked above with explanation, though I linked it based on master so now the link is not the right lines.
It's this: https://github.com/mamba-org/mamba/blob/8812acb77857546e3e081abcd9a8a4540f12cc96/mamba/utils.py#L330-L336

But also as I said, you could probably do without calling remove_auth entirely.

ok, this looks to be the difference -- will fix it now

I think this is fixed now? Do we need both mamba 0.15.1 and boa 0.6.1 or just one of those?

both will have to be at the latest version, although there is still an issue in the tests on master which I am fixing now.

Unfortunately that still fails, though the exception has changed a bit:
KeyError: Dist(channel='file://c/workspace/XXX_master/conda-bld', dist_name='xxx-2.55.0+master.46c40d-py_0', name='xxx', fmt='.tar.bz2', version='2.55.0+master.46c40d', build_string='py_0', build_number=0, base_url=None, platform=None)

(Note that the colon in c: has disappeared now)

yes, one more update to go :) sorry.
the proper URL form on Windows is file:///c:/... (note the triple slashes).
Will cut another mamba release right now, then it should be fixed.

it should be fixed now with mamba 0.15.2 and boa 0.6.2

Indeed, everything works fine for the robotology channel generations, and we removed all the pinnings in https://github.com/robotology/robotology-superbuild/pull/834 .

Is this tickling the same thing?
KeyError: Dist(channel='defaults', dist_name='tzdata-2023c-h04d1e81_0', name='tzdata', fmt='.conda', version='2023c', build_string='h04d1e81_0', build_number=0, base_url=None, platform=None)

I'm getting this under Windows 10 WSL2 Ubuntu.
(pybert)
dbanas@Dell-XPS-15:~
$ conda info

     active environment : pybert
    active env location : /home/dbanas/miniconda3/envs/pybert
            shell level : 2
       user config file : /home/dbanas/.condarc
 populated config files : /home/dbanas/.condarc
          conda version : 23.3.0
    conda-build version : 3.23.3
         python version : 3.10.9.final.0
       virtual packages : __archspec=1=x86_64
                          __cuda=12.0=0
                          __glibc=2.35=0
                          __linux=<IP_ADDRESS>=0
                          __unix=0=0
       base environment : /home/dbanas/miniconda3  (writable)
      conda av data dir : /home/dbanas/miniconda3/etc/conda
  conda av metadata url : None
           channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /home/dbanas/miniconda3/pkgs
                          /home/dbanas/.conda/pkgs
       envs directories : /home/dbanas/miniconda3/envs
                          /home/dbanas/.conda/envs
               platform : linux-64
             user-agent : conda/23.3.0 requests/2.28.1 CPython/3.10.9 Linux/<IP_ADDRESS>-microsoft-standard-WSL2 ubuntu/22.04.1 glibc/2.35 solver/libmamba conda-libmamba-solver/22.8.1 libmambapy/1.3.1
                UID:GID : 1000:1000
             netrc file : None
           offline mode : False


build: Re-add setup.py

The Python build tools are fine without a setup.py but Dependabot
chokes: https://github.com/dependabot/dependabot-core/issues/4483
Add a setup.py to keep Dependabot happy.
Fixes #1828
Signed-off-by: Jussi Kukkonen<EMAIL_ADDRESS>Please fill in the fields below to submit a pull request.  The more information
that is provided, the better.
Fixes #
Description of the changes being introduced by the pull request:
Please verify and check that the pull request fulfills the following
requirements:

[ ] The code follows the Code Style Guidelines
[ ] Tests have been added for the bug fix or new feature
[ ] Docs have been added for the bug fix or new feature

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.89%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1112

Relevant Lines:
1132

💛  - Coveralls


TAJO-1584: Remove QueryMaster client sharing in TajoMaster and TajoWorke...

...r

I’ve add option to reuse configuration.
QUERY_MASTER_RPC_CLIENT_REUSE("tajo.querymaster.rpc.client.reuse", false)

In this patch, the connection reuse is changed to be optional. In my opinion, it would be better if we completely remove the reuse feature. Actually, I'm not sure if anyone want 'reuse feature'.
Others look good to me.

I agree with you. I will remove the 'reuse feature'

@hyunsik
Could you review again?

+1 ship it!!


process exampleSetFlag to flag deserialization of null example vs missing

related PRs and tickets:

https://github.com/swagger-api/swagger-core/pull/3637
https://github.com/swagger-api/swagger-inflector/issues/371

@gracekarina, this change introduced a bug.
Now, when serializing the OpenAPI object, the exampleSetFlag attribute is being written in my YAML file.
 parameters:
    ParamP-App-id:
      name: app-id
      in: path
      required: true
      style: simple
      explode: false
      schema:
        type: integer
        format: int32
        exampleSetFlag: false  <-----


Test Issue By Bytepay: brainy sky

This issue is for bytepay test

/bytepay task 0.001DOT

Bytepay: Finish This Task, sulnong will pay you 0.001 DOT.
Comment in Following instruction to apply for this task
/bytepay apply
Visit http://localhost:10086 for more detail

/bytepay apply

Bytepay: Task has been assigned to @Emptycity-tear.

/bytepay bind 5FjiXjMHLNFNn4M6LAhENnKq3qa5wA4uGCd5BFSwEPQJe5vL

@Emptycity-tear:
Bind Success.

Please recharge token on http://localhost:10086 first.


Fixed #29728 -- Stopped re-saving session if CSRF cookie remains unchanged.

https://code.djangoproject.com/ticket/29728

Hello @nijel, thanks for the patch!
Could you add a test to CsrfViewMiddlewareUseSessionsTests as well?
You should be able to assert against request.session.modified.

I've tried, but looks too complex for me right now. The problem being that all tests currently use TestingHttpRequest, which does not have real session storage, but just a dict attached as a session...

Okay, I've replaced the session for tests, hopefully that's correct way to do that.


Diablo II cursor move when menuing

In Diablo II, especially in windowed mode, when you open a menu (inventory or character panel) the mouse will jump to a new location. It doesnt stay where it should be. Would be a big QOL for d2 ddraw users.

All the cursor issues should be fixed already if you compile cnc-ddraw from the latest commit, just make sure you have set "hook=4" in ddraw.ini.
If you don't how to compile it, here's the latest build (I pre-configured it for diablo 2 to support high-refresh rate monitors as well):
cnc-ddraw-d2.zip

This one has a different signature to the one in the releases so ill give it a shot. ty


I want to see val loss on tensorboard but face with error TypeError: loss() missing 1 required positional argument: 'img_metas'

In config file , workflow = [('train', 1)] , I change it to workflow = [('train', 1),('val',1)],hope to see val loss on tensorboard , but after one train epoch , val epoch begin , get error:TypeError: loss() missing 1 required positional argument: 'img_metas'.
Detail:
2021-12-21 12:11:29,428 - mmdet - INFO - Evaluating bbox...
Loading and preparing results...
2021-12-21 12:11:29,430 - mmdet - ERROR - The testing results of the whole dataset is empty.
2021-12-21 12:11:29,448 - mmdet - INFO - Exp name: small_val_loss.py
2021-12-21 12:11:29,449 - mmdet - INFO - Epoch(val) [1][1534]
/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/utils/registry.py:252: UserWarning: The old API of register_module(module, force=False) is deprecated and will be removed, please use the new API register_module(name=None, force=False, module=None) instead.
'The old API of register_module(module, force=False) '
/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/utils/registry.py:252: UserWarning: The old API of register_module(module, force=False) is deprecated and will be removed, please use the new API register_module(name=None, force=False, module=None) instead.
'The old API of register_module(module, force=False) '
/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/utils/registry.py:252: UserWarning: The old API of register_module(module, force=False) is deprecated and will be removed, please use the new API register_module(name=None, force=False, module=None) instead.
'The old API of register_module(module, force=False) '
/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/utils/registry.py:252: UserWarning: The old API of register_module(module, force=False) is deprecated and will be removed, please use the new API register_module(name=None, force=False, module=None) instead.
'The old API of register_module(module, force=False) '
Traceback (most recent call last):
File "./tools/train.py", line 189, in
main()
File "./tools/train.py", line 185, in main
meta=meta)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmdetection/mmdet/apis/train.py", line 177, in train_detector
runner.run(data_loaders, cfg.workflow)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/runner/epoch_based_runner.py", line 127, in run
epoch_runner(data_loaders[i], **kwargs)
File "/opt/conda/envs/mmdetection/lib/python3.7/site-packages/torch/autograd/grad_mode.py", line 26, in decorate_context
return func(*args, **kwargs)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/runner/epoch_based_runner.py", line 67, in val
self.run_iter(data_batch, train_mode=False)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/runner/epoch_based_runner.py", line 32, in run_iter
outputs = self.model.val_step(data_batch, self.optimizer, **kwargs)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/parallel/distributed.py", line 94, in val_step
output = self.module.val_step(*inputs[0], **kwargs[0])
File "/data/E/personal/liang/Traffic_Sign_Detection/mmdetection/mmdet/models/detectors/base.py", line 253, in val_step
losses = self(**data)
File "/opt/conda/envs/mmdetection/lib/python3.7/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
result = self.forward(*input, **kwargs)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/runner/fp16_utils.py", line 98, in new_func
return old_func(*args, **kwargs)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmdetection/mmdet/models/detectors/base.py", line 172, in forward
return self.forward_train(img, img_metas, **kwargs)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmdetection/mmdet/models/detectors/single_stage.py", line 84, in forward_train
gt_labels, gt_bboxes_ignore)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmdetection/mmdet/models/dense_heads/base_dense_head.py", line 326, in forward_train
losses = self.loss(*loss_inputs, gt_bboxes_ignore=gt_bboxes_ignore)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/runner/fp16_utils.py", line 186, in new_func
return old_func(*args, **kwargs)
TypeError: loss() missing 1 required positional argument: 'img_metas'
Traceback (most recent call last):
File "./tools/train.py", line 189, in
main()
File "./tools/train.py", line 185, in main
meta=meta)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmdetection/mmdet/apis/train.py", line 177, in train_detector
runner.run(data_loaders, cfg.workflow)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/runner/epoch_based_runner.py", line 127, in run
epoch_runner(data_loaders[i], **kwargs)
File "/opt/conda/envs/mmdetection/lib/python3.7/site-packages/torch/autograd/grad_mode.py", line 26, in decorate_context
return func(*args, **kwargs)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/runner/epoch_based_runner.py", line 67, in val
self.run_iter(data_batch, train_mode=False)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/runner/epoch_based_runner.py", line 32, in run_iter
outputs = self.model.val_step(data_batch, self.optimizer, **kwargs)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/parallel/distributed.py", line 94, in val_step
output = self.module.val_step(*inputs[0], **kwargs[0])
File "/data/E/personal/liang/Traffic_Sign_Detection/mmdetection/mmdet/models/detectors/base.py", line 253, in val_step
losses = self(**data)
File "/opt/conda/envs/mmdetection/lib/python3.7/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
result = self.forward(*input, **kwargs)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/runner/fp16_utils.py", line 98, in new_func
return old_func(*args, **kwargs)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmdetection/mmdet/models/detectors/base.py", line 172, in forward
return self.forward_train(img, img_metas, **kwargs)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmdetection/mmdet/models/detectors/single_stage.py", line 84, in forward_train
gt_labels, gt_bboxes_ignore)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmdetection/mmdet/models/dense_heads/base_dense_head.py", line 326, in forward_train
losses = self.loss(*loss_inputs, gt_bboxes_ignore=gt_bboxes_ignore)
File "/data/E/personal/liang/Traffic_Sign_Detection/mmcv/mmcv/runner/fp16_utils.py", line 186, in new_func
return old_func(*args, **kwargs)
TypeError: loss() missing 1 required positional argument: 'img_metas'
Traceback (most recent call last):
File "/opt/conda/envs/mmdetection/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/opt/conda/envs/mmdetection/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/opt/conda/envs/mmdetection/lib/python3.7/site-packages/torch/distributed/launch.py", line 260, in
main()
File "/opt/conda/envs/mmdetection/lib/python3.7/site-packages/torch/distributed/launch.py", line 256, in main
cmd=cmd)
subprocess.CalledProcessError: Command '['/opt/conda/envs/mmdetection/bin/python', '-u', './tools/train.py', '--local_rank=1', 'work_dirs/from_resnet/vfnet_xiangguan/vfnet_1x/small_val_loss.py', '--launcher', 'pytorch']' returned non-zero exit status 1.

@liang532 Please use the issue template.

@liang532 did you solve the issue? I face this problem with VFNet but not other single stage models. Happens to all versions after mmdet==2.17.0

I find that the forward_single fucntion returns three value cls_score, bbox_pred, bbox_pred_refine during training and returns only two values cls_score, bbox_pred_refine when it is not in training.
Could this be the cause of this problem?
https://github.com/open-mmlab/mmdetection/blob/a64303186aa79811a050942f1bdab430a6a7f7af/mmdet/models/dense_heads/vfnet_head.py#L307

@BIGWangYuDong other than the fix proposed https://github.com/open-mmlab/mmdetection/pull/7173, is there any other way we can solve this bug?

So is this still open? was found some solution to this? Is there a way to produce validation loss during training on vfnet?


Issue installing with bundler

Error Report
Questions

What did you do?
I ran the command /Users/pasqualelsaxton/.gem/ruby/2.6.0/bin/bundle update

What did you expect to happen?
I expected Bundler to run the installer and create a lock file

What happened instead?
Instead, what happened was the installer started then errored out

It seems to be breaking when it installs unf_ext v<IP_ADDRESS>
I have reinstalled x-code and accepted the license and still the issue is persisting. I am not installing fastlane via brew or gems or any other way because of requirements for this specific app.
I need to be able to install from the gemfile on local machines and circle ci in the exact same way and there seems to be something breaking in the installs.
I am using the following:
   Mac OS: 10.15.7
   XCode: 12.3 (12C33)

Any help would be great, thank you.
Backtrace
Errno::EACCES: Permission denied @ rb_sysopen - /Users/pasqualelsaxton/Documents/repos/va-mobile-app/VAMobile/ios/vendor/bundle/ruby/2.6.0/gems/json-2.5.1/CHANGES.md
  /Library/Ruby/Site/2.6.0/rubygems/package.rb:431:in `initialize'
  /Library/Ruby/Site/2.6.0/rubygems/package.rb:431:in `open'
  /Library/Ruby/Site/2.6.0/rubygems/package.rb:431:in `block (2 levels) in extract_tar_gz'
  /Library/Ruby/Site/2.6.0/rubygems/package/tar_reader.rb:65:in `each'
  /Library/Ruby/Site/2.6.0/rubygems/package.rb:412:in `block in extract_tar_gz'
  /Library/Ruby/Site/2.6.0/rubygems/package.rb:541:in `block in open_tar_gz'
  /Library/Ruby/Site/2.6.0/rubygems/package.rb:538:in `wrap'
  /Library/Ruby/Site/2.6.0/rubygems/package.rb:538:in `open_tar_gz'
  /Library/Ruby/Site/2.6.0/rubygems/package.rb:411:in `extract_tar_gz'
  /Library/Ruby/Site/2.6.0/rubygems/package.rb:391:in `block (2 levels) in extract_files'
  /Library/Ruby/Site/2.6.0/rubygems/package/tar_reader.rb:65:in `each'
  /Library/Ruby/Site/2.6.0/rubygems/package.rb:388:in `block in extract_files'
  /Library/Ruby/Site/2.6.0/rubygems/package/file_source.rb:29:in `open'
  /Library/Ruby/Site/2.6.0/rubygems/package/file_source.rb:29:in `with_read_io'
  /Library/Ruby/Site/2.6.0/rubygems/package.rb:385:in `extract_files'
  /Library/Ruby/Site/2.6.0/rubygems/installer.rb:830:in `extract_files'
  /Library/Ruby/Site/2.6.0/rubygems/installer.rb:310:in `install'
  /Users/pasqualelsaxton/.gem/ruby/2.6.0/gems/bundler-2.2.3/lib/bundler/source/rubygems.rb:158:in `install'
  /Users/pasqualelsaxton/.gem/ruby/2.6.0/gems/bundler-2.2.3/lib/bundler/installer/gem_installer.rb:67:in `install'
  /Users/pasqualelsaxton/.gem/ruby/2.6.0/gems/bundler-2.2.3/lib/bundler/installer/gem_installer.rb:18:in `install_from_spec'
  /Users/pasqualelsaxton/.gem/ruby/2.6.0/gems/bundler-2.2.3/lib/bundler/installer/parallel_installer.rb:163:in `do_install'
  /Users/pasqualelsaxton/.gem/ruby/2.6.0/gems/bundler-2.2.3/lib/bundler/installer/parallel_installer.rb:154:in `block in worker_pool'
  /Users/pasqualelsaxton/.gem/ruby/2.6.0/gems/bundler-2.2.3/lib/bundler/worker.rb:62:in `apply_func'
  /Users/pasqualelsaxton/.gem/ruby/2.6.0/gems/bundler-2.2.3/lib/bundler/worker.rb:57:in `block in process_queue'
  /Users/pasqualelsaxton/.gem/ruby/2.6.0/gems/bundler-2.2.3/lib/bundler/worker.rb:54:in `loop'
  /Users/pasqualelsaxton/.gem/ruby/2.6.0/gems/bundler-2.2.3/lib/bundler/worker.rb:54:in `process_queue'
  /Users/pasqualelsaxton/.gem/ruby/2.6.0/gems/bundler-2.2.3/lib/bundler/worker.rb:88:in `block (2 levels) in create_threads'

Environment
Bundler       2.2.3
  Platforms   ruby, universal-darwin-19
Ruby          2.6.3p62 (2019-04-16 revision 67580) [universal.x86_64-darwin19]
  Full Path   /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
  Config Dir  /Library/Ruby/Site
RubyGems      3.2.3
  Gem Home    /Users/pasqualelsaxton/Documents/repos/va-mobile-app/VAMobile/ios/vendor/bundle/ruby/2.6.0
  Gem Path    /Users/pasqualelsaxton/Documents/repos/va-mobile-app/VAMobile/ios/vendor/bundle/ruby/2.6.0
  User Home   /Users/pasqualelsaxton
  User Path   /Users/pasqualelsaxton/.gem/ruby/2.6.0
  Bin Dir     /Users/pasqualelsaxton/Documents/repos/va-mobile-app/VAMobile/ios/vendor/bundle/ruby/2.6.0/bin
OpenSSL
  Compiled    LibreSSL 2.8.3
  Loaded      LibreSSL 2.8.3
  Cert File   /private/etc/ssl/cert.pem
  Cert Dir    /private/etc/ssl/certs
Tools
  Git         2.24.3 (Apple Git-128)
  RVM         not installed
  rbenv       not installed
  chruby      not installed

Bundler Build Metadata
Built At          2020-12-22
Git SHA           29dc3c8398
Released Version  true

Bundler settings
path
  Set for your local app (/Users/pasqualelsaxton/Documents/repos/va-mobile-app/VAMobile/ios/.bundle/config): "vendor/bundle"
  Set for the current user (/Users/pasqualelsaxton/.bundle/config): "vendor/bundle"

Gemfile
Gemfile
source "https://rubygems.org"

gem "fastlane"

Gemfile.lock

There is no fastlane env because the install fails

Errno::EACCES: Permission denied @ rb_sysopen - /Users/pasqualelsaxton/Documents/repos/va-mobile-app/VAMobile/ios/vendor/bundle/ruby/2.6.0/gems/json-2.5.1/CHANGES.md

It looks like the issue is on your end.  Can you please make sure if the install directory's permission is correct?


Factor out the display of an issue into a helper, so that I can display ...

...one outside of the issues "home" page in DGU.

Coverage decreased (-0.37%) to 91.86% when pulling c7fe618bd62202e834811a7ffd7c70d2ae7aa00e on datagovuk:factor-out-issue-html into b6e15eba4cd92925fe7b14b417a39a4186868e7e on okfn:master.

Coverage decreased (-0.37%) to 91.86% when pulling c7fe618bd62202e834811a7ffd7c70d2ae7aa00e on datagovuk:factor-out-issue-html into b6e15eba4cd92925fe7b14b417a39a4186868e7e on okfn:master.

The reason I want this is so that I can display issues on the dataset page. This is how we do comments and issues is really a replacement for that. So we'd do this instead of using the issues home page. It makes them more visible and I don't think we'll get more than a few for each dataset, so I don't need the filtering, sorting and searching facilities that the issues home page would give.

Anyway, let me know if it is a problem to merge this, as I'll just move this to ckanext-dgu.

Coverage decreased (-0.54%) to 91.69% when pulling ef69daed1da970e53dadd6bcd85486f0655cec16 on datagovuk:factor-out-issue-html into b6e15eba4cd92925fe7b14b417a39a4186868e7e on okfn:master.

Coverage decreased (-0.54%) to 91.69% when pulling fd8c55b1ad449d27c7511531d168f7efd4888ea0 on datagovuk:factor-out-issue-html into b6e15eba4cd92925fe7b14b417a39a4186868e7e on okfn:master.


Generate MQTT certificate problem

How can we make this certificate , Becasue when I want to make a application server I have this error :
Read mqtt ca_cert: No such file or directory (os error 2)

Please see the docs: https://www.chirpstack.io/docs/guides/mosquitto-tls-configuration.html


Pictus thumbnail DLL doesn't close PSD handles

OS: Windows 10
To reproduce:

open a folder with some PSD files
wait until thumbnails are shown
attempt to edit or delete one of the files

Actual result: the file can't be deleted or modified until dllhost.exe dies
Expected result: the file can be deleted or modified immediately after Pictus is done generating its thumbnail

The thumbnail handler doesn't open the files manually, but instead gets pre-opened streams from Windows. Does it only happen with PSD files for you?

Yes, this seems to only affect PSD files. I copied a bunch of images in different formats to a directory, opened it with Windows Explorer and then looked at the list of dllhost's file handles. The only handle it had in this directory was to the PSD file.

I don't manage to reproduce that with my test files, so it might be something in those files that causes it. Are you able to send me a few of those files?

Could have something to do with the number of layers. I will send you an example file when I get home.

The issue appears to be trickier than I thought. While Pictus thumbnail DLL always keeps open handles to all PSD files, it doesn't always affect user's ability to delete and modify those files.
I tried to reproduce this issue today with a bunch of PSDs, some of which were real photos, and some test images. The thumbnail process kept handles to all PSDs. I could however still edit and delete the PSD files, even those with which I previously had problems.
In my test directory I also had a bunch of JPG files and I noticed that the thumbnail process opened those files as well, but then immediately closed them.
Here's one of my test files (in a zip archive because github does not allow to upload PSDs): pictus-test-blank.psd.zip


"Egress https" part docs for 1.0 is still an old version

Describe the bug
I'm trying to allow an external service can be accessed by a meshed service, following egress-https part. When I tried to create an EgressRule object, I got this error:
error: unable to recognize "dev-external-svc.yaml": no matches for kind "EgressRule" in version "networking.istio.io/v1alpha3"

Then I fixed it by modifying it as a ServiceEntry object.
Seems like the EgressRule definition is totally removed from CustomResourceDefinition list?
$ kubectl get crd | grep egress
$

Expected behavior
Update egress-https part docs, to tell us that we should use new objects to replace the old ones.
Steps to reproduce the bug
Just follow the "egress-https" part docs for istio 1.0.
Version
$ istioctl version
Version: 1.0.6
GitRevision: 98598f88f6ee9c1e6b3f03b652d8e0e3cd114fa2
User: root@464fc845-2bf8-11e9-b805-0a580a2c0506
Hub: docker.io/istio
GolangVersion: go1.10.4
BuildStatus: Clean

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.2", GitCommit:"cff46ab41ff0bb44d8584413b598ad8360ec1def", GitTreeState:"clean", BuildDate:"2019-01-10T23:35:51Z", GoVersion:"go1.11.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.2", GitCommit:"cff46ab41ff0bb44d8584413b598ad8360ec1def", GitTreeState:"clean", BuildDate:"2019-01-10T23:28:14Z", GoVersion:"go1.11.4", Compiler:"gc", Platform:"linux/amd64"}

Docs are fixed in 1.1. Closing it now.

Docs updated


Update to 1.51.0 broke switching projects from WSL2 to Docker container workflow via Remote WSL and Container extensions.

VSCode Version: 1.51.0
OS Version: Windows 10 Pro (version 2004)
Docker Desktop: <IP_ADDRESS> (49427), WSL2 backend
WSL2 (Debian in my case)

Steps to Reproduce:

Remote-WSL: New Windows (launch WSL2 instance)
Open any project/source folder within WSL2 filesystem
Remote-Containers: Add Development Container Configuration Files...
Nothing happens.  WSL2 becomes unresponsive.

(Previous to the update, above steps triggers the ability to pick and customize a development container profile from pre-configured container profiles.  Also noticed is that this "freezes" the WSL2 Linux instance, and any attempt to open a WSL2 terminal also just hangs.  Have to bounce WSL2 with wsl --shutdown to reset.)
Also, likely related

Remote-WSL: New Windows (launch WSL2 instance)
Open a VSCode project with existing container profile ( .devcontainer and Dockerfile)
VSCode does not detect project as a container project, or prompts whether to re-open in container.

(Previous to update, VSCode detects the Docker profile and asks whether to re-open the project in container.)

Does this issue occur when all extensions are disabled?: Yes/No
Not applicable, based on nature of bug.

Not the same issue.

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

When reopen code from WSL2, previous open tabs are not restored (#107111)

Docker Desktop updated to the latest version this morning (from reported <IP_ADDRESS> -> <IP_ADDRESS> (49550)).
I re-tested the above-described workflow, and the issues appears to be resolved.  Since VSCode did not update since filing ticket, I assume bug is either on Docker Desktop's side, or it's an order of operation/interaction bug between Docker Desktop and VSCode.
In any case, closing ticket as this is likely not a VSCode issue.


[ibex, nmi] Ibex nmi is not fired without enabling plic irq

The test chip_sw_rv_core_ibex_nmi_irq (#14609 ) is enabling the plic irq for both wdog and alert_handler in order to have the nmi handler being called.
It's also acknowledging the irq in the plic in order to stop it from being called.
Acording to @tjaychen this behaviour doesn't look right and needs investigaiton as the nmi path and the plic path are technically supposed to be different.

I'll take a look at this.

thanks @msfschaffner


High incoming supply voltage

The home energy meter reports the incoming supply voltage in excess 250V consistently overnight, peaking at 256V in the middle of the day.  What behavior of SmartEVSE shall expect charging the EV while voltage peak up to 256V.
If the EV shutdowns charging and voltage restore to operational range 220-240v does the SmartEVSE will try to recover charging automatically.

The SmartEVSE has no voltage measurement built in. Therefore it's impossible for it to react on overvoltage.
Please note that the absolute maximum voltage is 263Vac, above that the controller might become defective. There is a MOV for protecting against overvoltage spikes, this will start conducting around 275Vac, and might eventually blow the internal fuse.
The SmartEVSE will keep trying to start charging, if it detects a connected EV.


[CI] use seed specific to commit for Mysticeti simtest

Description
When a simtest is flaky, unrelated PRs can encounter failures which cannot be easily reproduced locally or in simtest nightly. It doesn't seem productive to block the PR submission in this case.
Test Plan
CI

If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

This should be deterministic. You could use the current commit hash to derive a seed.

I'm also a bit ambivalent about this. We have found and fixed many many bugs over that past year because they were blocking PRs. I agree its odd to put the burden on the author of an unrelated PR, but we are only so-so about keeping up with the nightly failure reports, which are supposed to find these bugs

I think blocking unrelated PRs are not very fair to people working on projects unrelated to core, because of prioritization issues in core. As a middle ground, how about I just make the change to the Mysticeti workflow?

It seems @mystenmark likes the comment above. Adding @arun-koshy for Mysticeti CI change.


Add parts in variants

Move all parts logic to variant
Fix all failing test
Display variant's parts in product show view
Allow to add parts to variants in backend
And refactor some messy stuff

An assembly product could include product's parts plus variant's parts, or only product's parts.

Will this get merged?

@proletarian probably not, the project hasn't been maintained and I think it needs a working 2-4-stable before we put in new features

Thanks @huoxito. Do you know if there is an alternative project for this purpose? If not, I'll probably need to use this for now and contribute a branch back later.

nope, can't think of any other right now sorry

@stevenbarragan great work. Was this for 2.2 initially?

Thank you @tesserakt, yes it was for 2.2. I hope, somehow it gets merged.

@stevenbarragan awesome. Are you using it in production?

To be honest, I'm not sure if they are still using it, I got another job, but we used it on production in that time.

Cool, I'm going to give it a whirl since we need it in production asap.
FWIW I think this should be in Core, awesome stuff @stevenbarragan

Sweet, I hope it works for you as well.

Is there still any interest for this feature? It's way out of date.

Closing as stale

I am super interested in rebasing it on top of 3-0-stable. Made a first try but got stuck somewhere in the middle, on huge conflicts in specs (some whole-file indenting were being made there?).
Anyway, i could invest some time in getting it into shape, but would like to have some feedback from you guys - anyone with good understanding of the changes between 2.4 and 3.0, compared to changes in this PR? Is it even doable given 3-0-stable state?
Please ping me! Cheers


Enable multiple sessions per user

Currently, if you log into Multinet from different browsers, only one browser will retain an active login.
Instead, Multinet should behave more like Google accounts. To solve this, we need some way to map multiple session tokens to the same user. This will require a bit of database engineering--perhaps an indirection collection that maps tokens to user _id values.

To add, I think having a concept of Session objects is a good idea (here, Session just means our document structure for representing this data). This would mean that the cookie that the client now has directly maps to a Session document, which then maps to a user. This both allows for multiple sessions to be assigned to one user, as well as makes the logic for querying easier (i.e., find a Session document with a field exactly matching the user cookie, vs querying a list). It would also allow us to store extra information about each session, if we wanted to (I'm not sure what, but maybe site settings or something).
However, the down side to this, is that it adds another database query, which would slow down the retrieval of user info from a cookie. We'd have to see how much of an issue this is, and we may be able to do some optimization to limit the number of database calls. It's also important to consider that in the future, much of the information from the api may rely on the information about the user's login, as they may have access to privileged data. So increasing the time to fetch user information could propagate that to the rest of the api calls.

However, the down side to this, is that it adds another database query, which would slow down the retrieval of user info from a cookie. We'd have to see how much of an issue this is, and we may be able to do some optimization to limit the number of database calls. It's also important to consider that in the future, much of the information from the api may rely on the information about the user's login, as they may have access to privileged data. So increasing the time to fetch user information could propagate that to the rest of the api calls.

This is maybe a place where encrypting the user data and storing that in the cookie could be helpful. I would want to (1) make sure that is the simplest way to solve the problem and (2) rely on a third-party library to handle the encryption.

It could also simply be another place that Foxx microservices would be of use (the first one being the workspace indirection lookups).


chore(*): Bump version to 0.5.0

Hi there :)
I'm opening a version bump PR to push the latest changes into a hex release. Do you think you would have some time to do the releasing in the upcoming days @sntran or a way of allowing me to do it ? You can reach me on twitter with DMs under the same handle @achedeuzot if needed ;)
Thanks a lot !

Coverage remained the same at 93.548% when pulling 89f2e54e8c2039850c5f1df59bd51e4ed5f140ab on feature/version-bump into e7a212c1333f7f8a8989434c14fe01529629b70c on master.

Hi @sntran :) Any way we could go forward with this ? I'd like to further improve this module :)

Hi @sntran , could you get back to me before the end of the month ? It's blocking some features I'd like to add to this module as well as some bug fixes that I need.
I'd really like to be autonomous on this module (release, tests, ...) and get out of your way if you don't have the time to do it. Please get back to me so we can find a way that's OK for both.

Hi @achedeuzot !
Sorry for the lack of activity on my end!
If I transfer the repo to you, will you be able to do everything? Or do I need to also transfer Hex's ownership too?

I would also see @sobolevn 's opinion on the transfer, but not sure if he has time to look at any time soon.

Hi @sntran , you'll need to transfer the repo, and I think the hex.pm ownership too so I can push releases.
In any case, the repo will just be redirected to the new one and won't disappear. I'll keep it public with the same Licence as yours was so if @sobolevn wants to discuss this later on, we can discuss through a github issue or you can contact me through whatever other means is good with you :)

GitHub does not let me transfer, since you already have a repo with the same name. I

Oh sorry, I've deleted it now :)

I have the same handle (@achedeuzot) on hex.pm (if that information helps ^^)

Alright, I have transferred the repo to you, and also added you as the owner of the hex's package.

Perfect, thank you so much for your help @sntran  :)

Hi @achedeuzot, is there any reason that you removed me from the the hex's package?

Hi @sntran, I was testing how this hex.owner stuff works. I've added you back :)


not sending changes through to lsp-tsserver?

Hi all,
Thanks a lot for the great package!
This is very likely not an LSP issue, I filed an issue on lsp-tsserver already but am not 100% sure.
Mirroring the content here:
I'm having a weird problem on my new computer. I'm not really sure if it's on LSP's side or lsp-tsserver. When I open a file the language server seems to get the file fine, but if I make any change to the file the language server seems to not get my changes, even if I save the file.
first open, placing caret on the constructor parameter, correctly highlights the reference

adding a few spaces in front of the reference, it seems the language server is still working on the first opened version

Any idea what could be the cause/fix? Thanks a lot.
I'm on Sublime 3206, LSP 0.8.2, lsp-tsserver 0.0.4, Windows 10 17763
Edit: Just tested on my old computer, where everything still works. I have the same Windows version, same Sublime, LSP and lsp-tsserver version. My Sublime User folder is even synced with onedrive so Sublime on the two computers have exactly the same configs.

Fixed by upgrade node from 11.13 to 11.14

Thanks for updating with your fix - would have been nice to see logs from the server to figure out what is breaking on the server. But I guess things can break on "current" Node.

Yeah didn't go that far. I added logging to the python package, and immediately realized that LSP is merely sending file path and caret location to the language server, the problem had to be on node / lsp-tsserver side. My first suspicion was the installation of node - I used to use chocolatey on my old computer, now I'm using scoop on the new one. I tried installing node with chocolatey, which of course installed the latest (11.14) which happen to fix the problem. I almost commented on the issue and closed it, but decided to see if it was the version instead. And... here we are, yes it was just a bad version, scoop is all good. If that didn't work, I'd start adding logs in lsp-tsserver.

Hmm, looks like node version wasn't the real cause. I had the same problem on my Surface Pro with node v11.14
Fixed it with uninstalling and re-installing node in an admin console, still using scoop.

Somehow this issue came back. I've uninstalled and re-installed nodejs several times, with or without admin privilege, the problem doesn't seem to go away. If you were to make a best guess, what would you say that the cause is?

Also, what kind of logs would be helpful? Please let me know. Thanks!

typescript-language-server works, but it is not showing highlights (the blue, green underlines). Closing since this is not an LSP issue. A word about why typescript-language-server doesn't show highlights would be appreciated, the project pages says it supports textDocument/documentHighlight


Upgrade to esbuild 0.19

This PR upgrades to the latest version of esbuild.
There are now two copies of esbuild installed in development, aas pkgroll is still using esbuild 0.18. I'd be happy to file a PR against that repository as well.

Thanks but we had to revert due to a change in how esbuild compiles require():
https://github.com/esbuild-kit/core-utils/issues/47
Closing this for now.

Thanks for linking to that other issue. I did search in this repository and check the Git blame before opening this PR, but the fact that it was in a different repository explains why I didn't see it!

Well, I had the same problem with sharp as Mariuz, and I just tried his repo, using the latest tsx with a resolution for<EMAIL_ADDRESS>and suddenly at least that issue with sharp has gone away. Strange, since the bug in esbuild is still there. Did tsx accidentally implement a workaround somewhere along the way?


Remove Carthage folder

There is no need to store Carthage folder in repository.
Carthage is smart enought to symlink dependencies

The way the project is currently setup it required (see the failure in the test and analyze steps on PINOperationQueue.h)

The way the project is currently setup it required (see the failure in the test and analyze steps on PINOperationQueue.h)

I believe that CI should make carthage checkout before build and that should fix it

@garrettmoon can you please launch workflows on CI?


Allow setting Java Toolchain determineReleaseState via builder DSL/property to use EA releases

I wanted to use JDK 19 with Gradle 7.6 master nightly releases
However, it doesn't find the JDK binary. This is because the release type is hardcoded as ga, where 19 requires ea.
It would be great to give users more control if needed over how to construct Toolchain binary URLs so that preview JDK's could be used 🙂
https://github.com/gradle/gradle/blob/7af2e5edf3d99eb9bda3b611cf22af70b1a0dde5/subprojects/platform-jvm/src/main/java/org/gradle/jvm/toolchain/install/internal/AdoptOpenJdkRemoteBinary.java#L159-L162
https://github.com/gradle/gradle/blob/7af2e5edf3d99eb9bda3b611cf22af70b1a0dde5/subprojects/platform-jvm/src/main/java/org/gradle/jvm/toolchain/install/internal/AdoptOpenJdkRemoteBinary.java#L93-L106

Duplicate of #18168


Insomnia preview showing empty json

Expected Behavior

Actual Behavior
In preview it showing an empty json.
Reproduction Steps
No response
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
2023.1.0
What operating system are you using?
Ubuntu
Operating System Version
22.04
Installation method
Official documentation
Last Known Working Insomnia version
No response

@ProttoyAD This is incomplete information. Where is your source code for returning the response, how does it get formed? This does not look to be an issue with Insomnia client.


Caldav support

Does this feature exist in Emacs orgmode?
Yes
If answer to first question is "Yes", please provide the link to the orgmode manual or any documentation related to the feature
https://github.com/dengste/org-caldav
Additional context
This is probably a massive ask. I dont know much about caldav other than that I managed to get it to work with calcurse and my owncloud. It would be wonderful to have the org agenda be in sync with caldav protocol as per the above emacs plugin

Since this is a plugin for emacs orgmode, and not a part of the emacs orgmode core, same thing applies here. This can go only as a separate plugin. It would never be part of the core.
I'm fully open to add a plugins infrastructure that will allow anyone to create plugins like this.
If you have any suggestions what would be helpful to be exposed from orgmode.nvim, feel free to post it on the issue above.

This plugin seems relevant https://github.com/BartSte/nvim-khalorg

@ranjithshegde I know this is quite old, but here's an idea for a fix/hack: If you have a public-facing server (ex: you host your own website) to which you can sync your org files (syncthing, dropbox, rsync with some cronjobs even...). You could have a minimal install of emacs on that website and schedule it (write a cron job) to generate an ical file from your org files. Afterwards, all you gotta do save that file so that it's accessible through your web server. Note: This will make that calendar publicly available which may or may not be exactly what you want ;)


enhance href check to check for anchor links

see: https://github.com/kubernetes-incubator/service-catalog/pull/275/files#r98456823

Moving to 0.0.3 because this isn't done yet.

@duglin please update this issue with the status. I am moving this out of a milestone until we decide exactly what we are doing here.

done - latest verify-href checker does this.


Removed .travis.yml and added github actions

No feature or bug fixes only moving away from TravisCI to Github actions. Halfway there requires code review.

I will do some tests tomorrow to make sure its working.

I will do some tests tomorrow to make sure its working.

@dunglas Ready for CR, I made some tests with npm publish and worked as expected. A new secret key value needs to be added to  NPM_TOKEN secret needs to be added GitHub secrets.

Thank you very much @ersin-demirtas!


feat: sync on a schedule

Checklist

[x] Ensure PR title matches the conventional commits format.

CodiumAI Agent Commands
As required run the following CodiumAI Agent commands:

Request PR review using @CodiumAI-Agent /review (and if required, request an incremental update with @CodiumAI-Agent /review -i)
Request PR improvement suggestions with @CodiumAI-Agent /improve --extended
Request PR update using @CodiumAI-Agent /describe

@CodiumAI-Agent /review

PR Analysis

🎯 Main theme: This PR focuses on refactoring the code to improve the structure and readability, and adding new features to the application. The main changes include moving the primary operations of the __main__ into the new start method of the App class, adding logging to the connect method, and adding a check to ensure the LOG_LEVEL environment variable contains a valid log level value.
📝 PR summary: The PR introduces several changes to the ado_asana_sync application. It refactors the code to improve the structure and readability, and adds new features to the application. The primary operations of the __main__ are moved into the new start method of the App class, logging is added to the connect method, and a check is added to ensure the LOG_LEVEL environment variable contains a valid log level value. The PR also includes minor changes such as removing unused imports and adding a new dependency in the pyproject.toml file.
📌 Type of PR: Refactoring
🧪 Relevant tests added: No
🔒 Security concerns: No security concerns found

PR Feedback

💡 General suggestions: The PR introduces several improvements to the codebase, making it more structured and readable. The addition of logging to the connect method is a good practice as it helps in debugging and understanding the flow of the application. The check for the LOG_LEVEL environment variable is also a good addition as it ensures that the application is configured with a valid log level. However, it would be beneficial to include tests for the new changes to ensure they work as expected and do not introduce any regressions.

 🤖 Code feedback:

relevant file: ado_asana_sync/sync/sync.py
suggestion: The start_sync function currently runs an infinite loop with a sleep time between each iteration. This could potentially cause issues if an error occurs during the sync process, as the application would continue to run indefinitely. It would be beneficial to add error handling within the loop to catch any exceptions and either attempt to recover or exit the application gracefully. [important]
relevant line: def start_sync(a: App) -> None:

relevant file: ado_asana_sync/sync/app.py
suggestion: The connect method currently does not handle any exceptions that may occur during the connection process. It would be beneficial to add error handling within this method to catch any exceptions and provide a more descriptive error message. This would help in debugging any issues related to the connection process. [important]
relevant line: def connect(self) -> None:

relevant file: ado_asana_sync/sync/sync.py
suggestion: The read_projects function currently reads the projects from a JSON file. While this works for a small number of projects, it may not scale well for a large number of projects. It would be beneficial to consider using a more scalable solution, such as a database, for storing and retrieving the projects. [medium]
relevant line: def read_projects() -> list:

relevant file: ado_asana_sync/sync/sync.py
suggestion: The create_tag_if_not_existing function currently creates a new tag if it does not exist. However, it does not handle any exceptions that may occur during the creation process. It would be beneficial to add error handling within this function to catch any exceptions and provide a more descriptive error message. This would help in debugging any issues related to the tag creation process. [medium]
relevant line: def create_tag_if_not_existing(a: App, workspace: str, tag: str) -> TagResponse:

How to use

Tag me in a comment '@CodiumAI-Agent' and add one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback.
/ask <QUESTION>: Pose a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, use the /config command.

How to use PR-Agent

Tag me in a comment '@CodiumAI-Agent' and add one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback.
/ask <QUESTION>: Pose a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, use the /config command.


[AutoPR] logic/resource-manager

Created to accumulate context: logic/resource-manager

Can one of the admins verify this patch?

Can one of the admins verify this patch?


c10d::allgather_ and   c10d::allreduce_ is not currently implemented for the XPU device

🚀 The feature, motivation and pitch
[rank0]:   File "/home/lxxx/miniconda3/envs/torch/lib/python3.11/site-packages/torch/nn/parallel/distributed.py", line 825, in __init__
[rank0]:     _verify_param_shape_across_processes(self.process_group, parameters)
[rank0]:   File "/home/lxxx/miniconda3/envs/torch/lib/python3.11/site-packages/torch/distributed/utils.py", line 288, in _verify_param_shape_across_processes
[rank0]:     return dist._verify_params_across_processes(process_group, tensors, logger)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]: NotImplementedError: The operator 'c10d::allgather_' is not currently implemented for the XPU device. Please open a feature on https://github.com/intel/torch-xpu-ops/issues. You can set the environment variable `PYTORCH_ENABLE_XPU_FALLBACK=1` to use the CPU implementation as a fallback for XPU unimplemented operators. WARNING: this will bring unexpected performance compared with running natively on XP

Description:
When attempting to use Distributed Data Parallel (DDP) training on an Intel Arc A770 GPU, I encountered a NotImplementedError indicating that the c10d::allgather_ operator is not currently implemented for the XPU device. This operator is crucial for multi-GPU training scenarios.
Steps to reproduce:

Set up a PyTorch environment with XPU support
Attempt to initialize a DistributedDataParallel model
Run the training script

Feature request:
Please implement the c10d::allgather_ operator for the XPU device to enable proper functionality of Distributed Data Parallel training on Intel GPUs.
Also c10d::allreduce_
Thank you for your attention to this matter.
Alternatives
No response
Additional context
No response

I would like to echo this request. I see that at least these 3 operators are not implemented: c10d::allgather_, c10d::_allgather_base_, c10d::allgather_into_tensor_coalesced_. Note that CUDA have them and they seem to work fine running with gloo torch distributed backend. Also note that torch distributed backend might be used even on a single GPU system with world_size=1 with further scaling to multi-GPU when needed.
I have reproducers for the ops I've identified as missing here:

https://github.com/pytorch/pytorch/issues/142096


MUMUP-1508 : Fix sidebar collapse on click of an element

Weirdness with a ng-init variable with attempting to access it in a child controller instance. Moved the variable to a variable on the header controller, accessing it that way works fine. #scopeIsWeird

:+1:


Seems electron couldn't get correctly installed on now.sh server

I have an app works smoothly on my local machine, while on server it just return 502 error:

Using process.on('uncaughtException', () => {}) I got this:
Error: spawn /home/nowuser/src/node_modules/electron/dist/electron ENOENT

Seems electron couldn't get correctly installed on now.sh? In my case, I'm using nightmare which depends on electron.

I guess the general purpose npm deployment is lacking some native dependencies; the easiest way around it would be to use a custom dockerfile

@jamo Thanks for the hint!
I'm trying with the dockerfile way, it feels harder to debug though >. <
While, is there any plan on fixing these native dependencies? It's delightful working with nodejs on now.sh 😭

I think electron is rare dependency for a web server so I don't think we see native support for it in our npm images...
Once the Dockerfile is running locally, and it exposes only one port, it's really likely to work as a now deployment w/o any issues

If it's because "the general purpose npm deployment is lacking some native dependencies", then it would be a problem for all native module IMHO, not just electron. There's many package for web server would requires native dependencies.
Is the supported native dependencies picked up by hands?

I've found the problem, electron was installed correctly while lacking some runtime dependencies:
https://github.com/electron/electron/issues/6945
Indeed it's not a good idea to run electron on server :(

Same issue here and this is my repo which is using Nightmare, I have to give up it now.


Improve download UX

Need to disable the button during download operation, also provide some sort of spinner/notification that the download is pending.

And down the line it would be great to explore a progress bar, though I have to figure out how to do that on the Rust side.

This has been done- button greys itself out and disables itself during download


Localhost ERR_CONNECTION_REFUSED

🐛 Bug Report
Running puppeteer on localhost does not work, returns ERR_CONNECTION_REFUSED when trying to connect using page.goto("http://localhost:3000"). I've tried adding timeouts, configuring jest-pupeteer.config.js, rearranging files, etc., but nothing seems to be working. As an aside, calling npm start before npm test on another terminal window runs the tests successfully, but I would rather not have that so as to reduce confusion when people run tests locally and on Github actions.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Link to repl or repo (highly encouraged)
I don't have a repo as this is with a company's codebase but I have my test files and configuration here:
import puppeteer from "puppeteer"
import 'expect-puppeteer'

let browser: puppeteer.Browser
let page

describe("about page", () => {

  beforeAll(async () => {
    browser= await puppeteer.launch({
      headless: false
    })
    jest.setTimeout(60000)

    page = await browser.newPage()
    await page.goto("http://localhost:3000")
  })
  test("renders about page correctly", async() => {

  })
})

afterAll(() => {
  browser.close()
})

My jest-puppeteer.config.js:
module.exports = {
  launch: {
    headless: process.env.HEADLESS !== 'false',
    timeout: 30000
  },
  server: {
    command: 'PORT=3000 react-scripts start',
    port: 3000,
  },
}

jest.config.js:
module.exports = {
  clearMocks: true,
  coverageDirectory: "coverage",
  moduleFileExtensions: ["ts", "tsx", "js", "jsx", "json", "node"],
  "preset": "jest-puppeteer",
  roots: ["<rootDir>"],
  "testEnvironment": "jest-environment-jsdom-sixteen",
  testRegex: ["(/__tests__/.*|(\\.|/)(test|spec))\\.tsx?$"],
  transform: {
        "^.+\\.tsx?$": "ts-jest",
    },
}

Script to run tests:
       "test": "react-scripts test --env=jest-environment-jsdom-sixteen",

## Run `npx envinfo --system --binaries --npmPackages expect-puppeteer,jest-dev-server,jest-environment-puppeteer,jest-puppeteer,spawnd --markdown --clipboard`

Paste the results here:

```bash

it looks like your testEnvironment is jest-environment-jsdom-sixteen not jest-environment-puppeteer.
If you remove the testEnvironment property from your config and remove --env=jest-environment-jsdom-sixteen from the test command, does it work?