White Output screen when attempting to solve puzzle.

Hi, I am trying to solve any of the exercises, but running either "Run Sample Tests" or "Attempt" just leaves the Output section of the page all white without responding. I've tried jumping through a few of them, but they all do the same. Am I missing something to run them? I have solved one puzzle before, that I could complete.

Chris.

It's basically #928.
The fix is only pushed to preview.codewars.com and not deployed to the main site yet, so it might take a few more days before the fix is applied.

Thanks for responding.


Improve edge handling

As pointed out by a (@aqnYRuzZStrJDpo)[https://twitter.com/aqnYRuzZStrJDpo/status/1754537410996904207?s=20] and (@sdw)[https://twitter.com/sdw] on Twitter, the current blurring algorithm does not handle edges well and could be improved.

Fixed as of 081f44330565c867b6486cace37b9bdd32941e78


Remove #[ignore] from test suite after upgrading near-workspaces-rs to support Rust 1.70+

See https://github.com/near/cargo-near/pull/103/commits/9ce42fd2e191ea8f4021b0b5aaea5bbe4cc89177

taking this issue


token auth validation

The database operation tests were failing due to missing or inconsistent fixtures, specifically for user roles (e.g., authenticated users, admin, and manager). Additionally, critical data like nickname in user_base_data and comprehensive update fields in user_update_data were incomplete, causing validation errors.

Fix: https://github.com/Hk574/Homework-10/tree/jwt_token_auth_validation
Added fixtures like user_token, admin_token, and manager_token for role-based authentication testing. Updated user_base_data with a valid nickname (JohnnyD) and improved user_update_data with fields like email and first_name. Enhanced login_request_data to include both username and email for better authentication coverage. These changes ensure consistent testing and robust validation of user schemas and authentication flows.


Make Basis Universal import quiet unless engine is in verbose mode

This makes Basis Universal stdout match other compression modes.
Previously, this was printed on every Basis Universal import:
Total basis file slices: 1
Slice: 0, alpha: 1, orig width/height: 96x16384, width/height: 96x16384, first_block: 0, image_index: 0, mip_level: 0, iframe: 0

Thanks!


re-generate actions

Checklist

[ ] Update changelog in CHANGELOG.md.

Context
I apparently forgot to re-generate all commands after the recent refactorings. This is just all generated code. One idea to prevent this in the future would be to have a check for it in CI.

Alright, there was a bit more broken which got fixed now. The plan execution should work again.


Update handling of minibuffer message overlays

The cursor would jump forth and back when displaying the message. Overriding make-overlay isn't necessary any more because the content is only defined by the input now but instead we need to make sure the cursor stays at the front of the overlay by overriding put-text-property when calling minibuffer-message. I won't merge this before also adjusting selectrum--fix-set-minibuffer-message which I will do after upgrading to Emacs 27 where I can test it.

Turns out for selectrum--fix-set-minibuffer-message there is no more advice necessary :)

Well, that's certainly good news!


ci: init

Codecov Report

Merging #1 (bb2f844) into main (5cae1cb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #1   +/-   ##
=======================================
  Coverage   89.85%   89.85%
=======================================
  Files           1        1
  Lines         138      138
=======================================
  Hits          124      124
  Misses          7        7
  Partials        7        7

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 5cae1cb...bb2f844. Read the comment docs.


New Star icon size / placement

Hi. in the latest batch of new icons the Star seems to be sat a bit higher / or be slightly smaller than the other icons, makes alignment in app quiet difficult.

Hey!
Icons are are funny business because you have to work with all sorts of different shapes with different proportions. Some are top heavy and others, like the star, are more bottom heavy making it optically imbalanced so you have to compensate by using a bit of space.
It's subtle but you can see in the context of an app if placed next to text, the current icon feels more optically balanced:


How do I convert the tensorflow to tensorflowlite

Hello,
Thank you for providing the conversion notebook for tensorflow. I am new to ML and was wondering how would i go about converting the tensorflow .pb file to tensorflow lite file .tflite?
Regards,
Manny
I tried the following:
import tensorflow
converter = tensorflow.lite.TFLiteConverter.from_saved_model("./checkpoint/tensorflow_generator/")
test = converter.convert()

Getting this error:
None is only supported in the 1st dimension. Tensor 'serving_default_input_1' has invalid shape '[None, None, 80]'.

This is out of support of this repository.
Please solve by yourself.


[BUG] Keyboard opening after picking an image on iOS

Description
We have the same issue as in #1442 and #1745  in our project. We do not have any input, we are just uploading an identity document.
When document is uploading, we render a <Loader /> component, on top of it, we have erratically the keyboard showing up:
https://user-images.githubusercontent.com/77674046/122070510-52384380-cdf6-11eb-8805-1746df97291d.mp4
Edit : I can't play on linux debian chrome latest the video directly on github, but downloading for playing works.
How to repeat issue and example

Download on the iOS store the app pass culture, register as someone born in is eighteen years old, got to the identity verification check, upload document from library.

Solution
We have none so far, and we may have to change the uploading library if we can't find a solution.
Additional Information

Image Picker version: 4.0.3
React Native version: 0.63.3
Platform: iOS
Development Operating System: Mac OS Big Sur 11.2.3
Dev tools: Xcode 12.4 (12D4e)

cannot be reproduce after reinstalling the app


Updates deprecated

Codecov Report

Merging #176 into master will increase coverage by 0.14%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #176      +/-   ##
============================================
+ Coverage     72.82%   72.97%   +0.14%
  Complexity        9        9
============================================
  Files            87       87
  Lines          2690     2690
  Branches        226      226
============================================
+ Hits           1959     1963       +4
+ Misses          595      592       -3
+ Partials        136      135       -1

Impacted Files
Coverage Δ
Complexity Δ

...e/src/main/java/com/uber/tchannel/api/TFuture.java
70% <ø> (ø)
0 <0> (ø)
:arrow_down:

...java/com/uber/tchannel/handlers/RequestRouter.java
70.17% <ø> (+3.5%)
0 <0> (ø)
:arrow_down:

...c/main/java/com/uber/tchannel/tracing/Tracing.java
72% <100%> (ø)
0 <0> (ø)
:arrow_down:

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 028e29d...d006316. Read the comment docs.


Draft PR: Same as PR# 1044 - need deployment for functional review

Summary
The deployment on PR 1044 is broken. This PR is to get a deployment for functional review. The changes here are identical to 1044.

There is now a working deployment on 1044. Closing this.


Protocol ssh default and optional in config

Set "-ssh" as default option for Putty, to fix Issure #28.
Like Pull Request #23, but the user can disable it by setting
config.putty.ssh_options = ""
In config you can put more as one option to your box, for example a tunnel to the webserver:
config.putty.ssh_options = "-ssh", "-L", "8080:localhost:80"
I feel, it would be nice, that vagrant putty works for mostly all (new) users.
Using vagrant putty -- -ssh is of curse an alternate without this patch. But a typically new user in vagrant (like me) needs first to find what is the problem here with Putty. An advanced user, who changed the ssh_client, can also change ssh_options (example kitty). So, the default -ssh should be not a problem.

Fixes #28


Add a flag to PuppeteerCrawler to set the page load timeout

Now you need to use this awkard way:
const { gotoExtended } = Apify.utils.puppeteer;
{
...
gotoFunction: ({ page, request }) => gotoExtended(page, request, { timeout: 120000 }),
pageFunction: ...
}

https://github.com/apifytech/apify-js/pull/432


FileUpload - Delete tmp file on revert and save

https://github.com/laravel-filament/filament/pull/995#issuecomment-1001482132

Thanks!


Fix working with different schemas

✓ Checklist:

[ ] This PR has been added to CHANGELOG.md (at the top of the list);
[ ] Tests for the changes have been added (for bug fixes / features);
[ ] Docs have been added / updated (for bug fixes / features).

Close #93

Codecov Report

Merging #102 (109cad7) into main (6e686dc) will decrease coverage by 0.25%.
The diff coverage is 28.57%.

@@            Coverage Diff             @@
##             main     #102      +/-   ##
==========================================
- Coverage   78.63%   78.37%   -0.26%
==========================================
  Files          50       50
  Lines        3023     3020       -3
==========================================
- Hits         2377     2367      -10
- Misses        646      653       +7

Impacted Files
Coverage Δ

datanymizer_dumper/src/lib.rs
2.85% <ø> (ø)

datanymizer_dumper/src/postgres/dumper.rs
22.22% <0.00%> (ø)

...atanymizer_dumper/src/postgres/schema_inspector.rs
0.00% <0.00%> (ø)

datanymizer_engine/src/settings/mod.rs
64.44% <0.00%> (-6.29%)
:arrow_down:

datanymizer_dumper/src/postgres/table.rs
85.92% <71.42%> (-0.50%)
:arrow_down:

datanymizer_dumper/src/postgres/row.rs
91.48% <100.00%> (ø)

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 6e686dc...109cad7. Read the comment docs.


Add --no-wait argument

This prevents us from looping and waiting for launchctl to finish stopping the service if we just want to attempt once and immediately exit.

@SMillerDev Good catch, added.


[Bug]: Welcome tour is failing with an error - "Action Get Customers has Failed" - if env is set as Staging in some other app

Is there an existing issue for this?

[X] I have searched the existing issues

Description
If the environment is set to Staging in an application, and now we try to invoke Welcome Tour, It fails with an error Action Get Customers has Failed
Steps To Reproduce

In a workspace, open an application and switch the environment dropdown such that it reads Staging
Now from the home page, invoke welcome tour
Note that it fails with an error "Action Get Customers has failed"

Public Sample App
No response
Environment
Release
Issue video log
No response
Version
Cloud

The selection of the environment should be contained within the application itself. Ideally whichever environment the user selects in one of their application should not affect other applications in their workspace.
@sribalajig @riteshkew Another reason to contain environment selection information within the application

This is going to be handled by the fixes under this change https://github.com/appsmithorg/appsmith-ee/issues/2164


flx: getCounter function

When the twikoo_visitors property is not set, the COUNTER_GET request is not executed.

nice fix


owl:Datatype mistakenly used when rdfs:Datatype is intended

Bug description
OWL does not have a concept owl:Datatype, but it appears in one of the SHACL reviewing shapes of OWL syntax.  (OWL does have a concept owl:DatatypeProperty, which may have contributed to masking this oversight.)
https://github.com/ucoProject/UCO/blob/1.3.0/ontology/owl/owl.ttl#L147-L162
This was not caught by the "upstream" design-vocabulary tests (IRI typo checkers for RDF, RDFS, and OWL) in Issue 488 because the concept reference occurred in a SPARQL query, which is not reviewed by the concept typo-checking function.
This is a straightforward fix, and will be handled with the bug-fix workflow, not requiring a committee vote.  The fix will still receive testing through the CASE example repositories.
Steps to reproduce
This should be flagged as an error:
@prefix ex: <http://example.org/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

ex:ClassDatatype-1
    a
        owl:Class ,
        rdfs:Datatype
        ;
    .

owl.ttl currently (UCO 1.3.0) considers that conformant.

It is possible to spell the affected shapes and similar shapes using other SHACL constructs aside from SPARQL, which would enable Issue 488's testing to catch this kind of error.  But, I intend to handle that with a proposal requiring at least one committee vote.  If there's a nontrivial testing impact from this bugfix proposal, this issue might morph to become that syntax change proposal too.


Null check syntax: null or is

In the alpha releases, null checks were performed by:
body: { null: true } or body: { null: false }
In the first beta release, I  added an is operator to allow:
body: { is: NULL } or body: { is: NOT_NULL }
I only want to support one or the other in v1.0.0.  My preference is the is operator, as I think it's easier to read inside complex queries.  Anyone else have a preference?

what is NULL and NOT_NULL? are they constants?
The only issue I see with the second one is that NULL and NOT_NULL aren't JS

NULL and NOT_NULL are GraphQLEnumTypes.  When making a query without variables, you use the enum value within the query as shown above.  When making a query with variables, you use the string representation of the enum as shown below:

looks good! as long as docs are clear :)
great library btw!

I'd prefer isNull: true|false, I don't think it's necessary to complicate the schema with an additional enum. This also allows you to pass isNull: null which means "I don't care if it's null or not" which is useful if you use variables in your GraphQL queries; with the is: approach the equivalent is: null would seem like is: NULL but that's not the meaning.
query Things ($searchTerm: String!, $nullName: Boolean) {
  allThings(filter:{term: {equal: $searchTerm}, name: {isNull: $nullName}}) {
    nodes { ... }
  }
}

👍 Keep up the good work!

Agreed.  The is: null would be a source of confusion, and I definitely prefer body: { isNull: true } over body: { null: true }.  I'll cut a release that includes isNull and plan to deprecate the other two at v1.0.0.  (Wish I could actually mark them deprecated, but GraphQL doesn't support deprecating input fields AFAIK.)


Error using Spotify media player

Home Assistant release (hass --version):
0.43.0
Python release (python3 --version):
Python 3.5.2
Component/platform:
Spotify media player
Description of problem:
The following error occurs after I authorize the application
File "/usr/local/lib/python3.5/dist-packages/homeassistant/components/media_player/spotify.py", line 156, in update
self.refresh_spotify_instance()
File "/usr/local/lib/python3.5/dist-packages/homeassistant/components/media_player/spotify.py", line 143, in refresh_spotify_instance
self._oauth.is_token_expired(self._token_info))
AttributeError: 'SpotifyOAuth' object has no attribute 'is_token_expired'

Additional info:
@happyleavesaoc suggested that I make sure I've installed the correct version of spotipy but I'm not sure how to validate this.

I got it to work using this command
pip3 install --upgrade git+https://github.com/happyleavesaoc/spotipy@connect-api
Is there a cleaner way of doing this? Should this be included in the docs?

When using the official spotipy release on pypi (spotipy 2.4.4) you need to apply two patches/commits for this to work.
The first one is from the upstream repository:
https://github.com/plamere/spotipy/commit/d092683be34123a56b77b4496a2540b240054d6b
which solves the AttributeError: 'SpotifyOAuth' object has no attribute 'is_token_expired' error.
And the seconds one is from happyleavesaoc fork:
https://github.com/happyleavesaoc/spotipy/commit/544614f4b1d508201d363e84e871f86c90aa26b2
for the Spotify Connect API support, which is already reported upstream as pull request https://github.com/plamere/spotipy/pull/182 currently still awaiting to be accepted.

Would there have been a way to change the dependencies of the component so that this happens automatically? At first, all I did was add the component to my configuration, and homeassistant took care of installing all of the dependencies itself.

Imho the easiest/best way will be when upstream accepts the pull request and releases a proper new spotipy version including that feature (which will additionally allow distributions to properly package the new version).

As discussed in https://github.com/home-assistant/home-assistant/issues/7286 would it be possible to get this feature integerated and a new spotipy version released? This would ease adoption for distributions. Personally I can say I've tested spotipy (in combination with home assistant and different hardware, namely an Amazon FireTV and a Google Nexus 4 with the official Android Spotify app) with this pull request and it works really well so I'd love to see this feature getting merged.

The Home Assistant dependency management system should have installed the proper version of spotipy compatible with this component (which right now is my fork). I'm uncertain why that would not have been the case. There should technically be no difference between installing my fork or a proper pypi package.


"editor.suggestSelection": "recentlyUsed" not working as expected

Issue Type
Bug
Description
"editor.suggestSelection": "recentlyUsed"
I love this feature but I think its broken in this release. It is not remembing my recently used suggestion and only highlighting the top suggestion.
VS Code Info
VS Code version: Code 1.20.1 (f88bbf9137d24d36d968ea6b2911786bfe103002, 2018-02-13T15:23:28.607Z)
OS version: Darwin x64 17.4.0
Extensions (19)

Extension
Author (truncated)
Version

EditorConfig
Edi
0.12.0

beautify
Hoo
1.3.0

html-css-class-completion
Zig
1.16.2

path-intellisense
chr
1.4.2

vscode-eslint
dba
1.4.5

githistory
don
0.4.0

vscode-babel-coloring
dza
0.0.4

gitlens
eam
8.0.0

vscode-npm-script
eg2
0.3.3

code-runner
for
0.8.7

easy-icons
jam
0.3.1

node-debug2
ms-
1.19.0

debugger-for-chrome
msj
4.1.0

vetur
oct
0.11.7

trailing-spaces
sha
0.2.11

code-spell-checker
str
1.6.3

vscode-react-native
vsm
0.5.7

vscode-todo-highlight
way
0.5.11

local-history
xyz
1.6.2

(1 theme extensions excluded)

Reproduces only with extensions

@archcorsair did you try the different setting values as described here? https://github.com/Microsoft/vscode/issues/41060#issuecomment-364284879?

@egamma I tried byRecency but it did not change anything. I'd also like to note that I didn't have any user settings configured for this feature up until I tried to troubleshoot why it stopped working.
First I tried manually setting "editor.suggestSelection": "recentlyUsed" according to the dropdown provided:

I then tried updating it to "editor.suggestSelection": "byRecency" but it still does not suggest the most recently used item, only the top selection.

I didn't think to try recentlyUsedByPrefix and it now works as expected. Thank you for your help @egamma :)


Csp training

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes

caishaoping seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.
Have you signed the CLA already but the status is still pending? Recheck it.

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes

caishaoping seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.
Have you signed the CLA already but the status is still pending? Recheck it.

created by accident

created by accident


Fix bug in ASIO shutdown

Prior to this commit, when shutting down the ASIO subsystem, we ignored the result of our waiting to join on the ASIO thread's termination.
By ignoring the result, in cases where the join failed, we would continue doing ASIO shutdown related activities while the ASIO system was still running.
This was "not good".

@dipinhora is the interaction with the systematic testing asio shutdown ok with this change?

Hi @SeanTAllen,
The changelog - fixed label was added to this pull request; all PRs with a changelog label need to have release notes included as part of the PR. If you haven't added release notes already, please do.
Release notes are added by creating a uniquely named file in the .release-notes directory. We suggest you call the file 4548.md to match the number of this pull request.
The basic format of the release notes (using markdown) should be:
## Title

End user description of changes, why it's important,
problems it solves etc.

If a breaking change, make sure to include 1 or more
examples what code would look like prior to this change
and how to update it to work after this change.

Thanks.

@dipinhora is the interaction with the systematic testing asio shutdown ok with this change?

systematic testing shouldn't be impacted (i think) as it already works with how the asio shutdown process happens...

successfully ponyint_thread_join'd later on or not but this seems good to me..

Unless I am completely misreading the docs that I refreshed myself on, that shouldn't be possible.


Snow can be bypassed with window.parent.alert(...)

Reproduce by running:
window.parent.alert(1);

In https://lavamoat.github.io/snow/demo/

Can't seem to reproduce this successfully. Here are the steps I've taken:

visit https://lavamoat.github.io/snow/demo/
open console
paste payload above
press enter
Result: Snow successfully captures the alert attempt and logs it to console instead.
Would you mind helping me understand what I'm missing? A video or any other creative idea will be highly appreciated.

Yep, same environment issue I described in https://github.com/LavaMoat/snow/issues/68


Device Request - mmWave Radar Sensor ceiling/wall mount 24G 240V - _TZE204_dtzziy1e / MTG275-ZB-RL, TS0601

Update: URLs are updated, now they work when they are selected :)
Device Name: mmWave Radar Sensor ceiling/wall mount 24G 240V
Device Model: MTG275-ZB-RL, TS0601
Device Description: wall/ceiling mount (on top, not in a wall/ceiling) mmWave presence sensor
Link to device image.
Device Interview:
"ids": {
"modelId": "TS0601",
"manufacturerName": "_TZE204_dtzziy1e"
},
"endpoints": {
"ieeeAddress": "18:7a:3e:ff:fe:f1:c8:b9",
"networkAddress": 17709,
"modelId": "TS0601",
"manufacturerName": "_TZE204_dtzziy1e",
"endpointDescriptors": [
{
"status": "SUCCESS",
"nwkAddrOfInterest": 17709,
"_reserved": 20,
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 81,
"applicationDeviceVersion": 0,
"_reserved1": 1,
"inputClusters": [
0,
4,
5,
61184
],
"outputClusters": [
25,
10
]
}
],
"deviceType": "router",
"receiveWhenIdle": true,
"capabilities": {
"alternatePANCoordinator": false,
"deviceType": true,
"powerSourceMains": true,
"receiveWhenIdle": true,
"security": false,
"allocateAddress": true
},
"extendedEndpointDescriptors": {
"1": {
"clusters": {
"basic": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 0,
"name": "zclVersion",
"value": 3,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 1,
"name": "appVersion",
"value": 70,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 2,
"name": "stackVersion",
"value": 0,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 3,
"name": "hwVersion",
"value": 1,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 4,
"name": "manufacturerName",
"value": "_TZE204_dtzziy1e",
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 5,
"name": "modelId",
"value": "TS0601",
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 6,
"name": "dateCode",
"value": "",
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 7,
"name": "powerSource",
"value": "mains",
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"writable",
"reportable"
],
"id": 65502,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 65533,
"name": "clusterRevision",
"value": 2,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 65534,
"name": "attributeReportingStatus",
"value": "PENDING",
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 65504,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 65505,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 65506,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 65507,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"groups": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 0,
"name": "nameSupport",
"value": {
"type": "Buffer",
"data": [
0
]
},
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 65533,
"name": "clusterRevision",
"value": 2,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"scenes": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 0,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 1,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 2,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 3,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 4,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 65533,
"name": "clusterRevision",
"value": 2,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
}
},
"bindings": {
"ota": {},
"time": {
"attributes": [],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
}
}
}
}
}
Additional Comments:
Manufacterer: Wenzhou Wenzhi Automation Technologie Co.
Device Series: MTGX75
Firmware Version: 7.2.2-0
Device review, including hardware description and HA integration: link
Bought on Aliexpress .
Device support request for ZHA  and Herdsman Converter

JSON information Tuya iot platform
Standard Instruction Set:

Code
Type
Values

sensitivity
Integer
{   "unit": "",   "min": 1,   "max": 9,   "scale": 0,   "step": 1 }

near_detection
Integer
{   "unit": "m",   "min": 0,   "max": 1000,   "scale": 2,   "step": 10 }

far_detection
Integer
{   "unit": "m",   "min": 150,   "max": 1000,   "scale": 2,   "step": 10 }

Standard Status Set:

Code
Type
Values

presence_state
Enum
{   "range": [     "none",     "presence"   ] }

sensitivity
Integer
{   "unit": "",   "min": 1,   "max": 9,   "scale": 0,   "step": 1 }

near_detection
Integer
{   "unit": "m",   "min": 0,   "max": 1000,   "scale": 2,   "step": 10 }

far_detection
Integer
{   "unit": "m",   "min": 150,   "max": 1000,   "scale": 2,   "step": 10 }

checking_result
Enum
{   "range": [     "checking",     "check_success",     "check_failure",     "others",     "comm_fault",     "radar_fault"   ] }

target_dis_closest
Integer
{   "unit": "m",   "min": 0,   "max": 1000,   "scale": 2,   "step": 1 }

I think it should be a new device, as it's combined radar detection and light switch.
It seems to be using these datapoints:
0xEF02: ("dp_2", t.uint32_t, True),
0xEF03: ("dp_3", t.uint32_t, True),
0xEF04: ("dp_4", t.uint32_t, True),
0xEF06: ("dp_6", t.enum8, True),
0xEF65: ("dp_101", t.uint32_t, True),
0xEF66: ("dp_102", t.uint32_t, True),
0xEF67: ("dp_103", t.CharacterString, True),
0xEF69: ("dp_105", t.enum8, True),
0xEF6A: ("dp_106", t.enum8, True),
0xEF6B: ("dp_107", t.enum8, True),
0xEF6C: ("dp_108", t.uint32_t, True),
reference

Indeed, I am not using the switch but if I have to believe the article description than the switch could be controlled separately.
The device also has a light sensor (lux).

hi @tommetje,
Its a complete new device, the endpoints do not match after all.

You may give it a try.
radar_sensor_3.zip
Proceed as described: https://github.com/JohanBendz/com.tuya.zigbee/issues/565#issuecomment-1837384040

This was fun! :D
I could add my device, no errors or anything. However sadly no luminosity or occupancy readings.

@tjarb I would like to have support for my device and I would not mind to do some tinkering myself. Would you have any ideas of what I could try to make my device work?

you have to find te corresponding endpoint numbers. you can change them yourself and see if things respond.
Adding my tuya device was also my first homey project 😉

Any news to the support for this device  MTG75-ZB-RL (ZHA/skyconnect)?


ValidationError but appears correct

Getting this validation error when running combined with tap-hubspot (potloc variant). It seems like this is an array?
I'm a bit out of my depth here on correct json schemas and being able to tell if this is a tap or target issue. Might be my own misunderstanding.
jsonschema.exceptions.ValidationError: '[{"category": "HUBSPOT_DEFINED", "typeId": 2, "label": "Primary Company"}, {"category": "HUBSPOT_DEFINED", "typeId": 280, "label": null}]' is not of type 'array'
Failed validating 'type' in schema['properties']['associationTypes']:
    {'items': {'properties': {'category': {'type': ['null', 'string']},
                              'label': {'type': ['null', 'string']},
                              'typeId': {'type': ['null', 'integer']}},
               'type': 'object'},
     'type': 'array'}

I think this
'[{"category": "HUBSPOT_DEFINED", "typeId": 2, "label": "Primary Company"}, {"category": "HUBSPOT_DEFINED", "typeId": 280, "label": null}]'

is actually a JSON array string so that's probably why validation is failing.
The tap's probably emitting the record with associationTypes as a string, rather than an array.

You're right. Looks like it's defaulting to string.
Will check with the tap then.

Turns out this is likely an SDK issue https://github.com/meltano/sdk/issues/1204


Create GUI map/scenario editor

According to this write-up, Elite Command had a GUI editor for editing existing maps and making entirely new ones. A similar editor could build off of #40 (once that's done) and make Zetawar more accessible.

I'm not sure if this editor should be part of this repo or should be created as another repo within the Zetawar organization in Github. Thoughts?

I'd lean toward putting it in the same repo at first and then spinning it out later if it makes sense.


MM-32784, MM-35604: CRT, Adds follow/unfollow dot menu item in RHS and center

Summary
This commit enables the user to follow or unfollow a thread, or message,
from the post's dot menu in the RHS thread viewer and center channel.
Ticket Link
https://mattermost.atlassian.net/browse/MM-32784
https://mattermost.atlassian.net/browse/MM-35604
Screenshots

Release Note
NONE

/update-branch


Notebook cell border has <1px offset

VSCode Version: 1.50-Insiders
OS Version: macOS

As shown in above image, when border color is set to #f0f and cell background is set to #0ff, you can tell that there is probably 1px or less misalignment.

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

No, there is no offset at all, it's simply my astigmatism.


Chore/downgrade cardano-db-sync 7.1.0

Description
A race condition exists if starting  cardano-db-sync within 3 seconds of cardano-node, when there's no existing state. We also must move to an Allegra fork compatible version prior to the next epoch, so cannot stay on v6.
https://github.com/input-output-hk/cardano-db-sync/issues/433
Proposed Solution
Introduce a small startup offset to push it out of the race window.

I'm already syncing and waiting for it reaches +4M block so I can update e2e snapshot db and run the test suite


chore(extension): set live urls for cardano services

Set cardano services url to live

Allure Report
allure-report-publisher generated test report!

processReports: ✅ test report for 7d5fa21a

passed
failed
skipped
flaky
total
result

Total
23
0
0
0
23
✅


added optional parameters for position and line cues (vtt)

Related to #11
In the end, I was able to solve the issue and I decided to make a PR for it. The naming of these two new optional parameters is based on my current understanding of the spec, but maybe a better name could be necessary (I've not 100% understood what those values where meant for).
Since these additional parameters are optional, I thought that an Option enum would be the best way to store those values.
As I said, I'm new to rust, so this code would need to be reviewed. I used it in my project and now all the vtt files (both with and without optional parameters) are correctly parsed.
At the very least, this could be used as a starting point 🙂

Hey, Cheers for the PR! At the time I implemented this, I noticed that various players are interpreting the standard in their own way...with most players the inline cues don't even get rendered properly for WebVTT.
Even the normal cues get interpreted differently per player and they interpret the colors differently and this was a frustration point for me. When I tested initially, one player might have had blue color on blue cue and another pink on blue cue and similar other small issues.


Additional refactor before 3.0

I have spent a bit of time refactoring your code (originally mostly for my understanding of what was going on in there).
You can find the branch I am currently working on here: https://github.com/sgenoud/PptxGenJS/blob/refactor/text-fragment/src/elements/text.ts
It should be easier to test with this structure (for instance by having snapshots of the generated XML for the different elements).
I can also imagine being easier to extend / improve.
Would you be interested in this kind of refactoring for the project? If I continued to work on it would be open to merge a PR?

Possibly... after having spent the last half of this year converting the code to TypeScript, i'm just ready to ship it at this point.

I know the feeling. Sometimes you just want to be done with a big project.
The point with adding my refactor to yours is that it might add some additional API changes - so it would be better to bunch them together.
I have been working on it further in this branch: https://github.com/sgenoud/PptxGenJS/tree/refactor-master. I have decided to keep my own fork for now (and add some features there).
If you decide to go and add some more stuff to version 3, I will be happy to to prepare a nice clean PR!

Thanks!


WebTorrent: torrent.swarm is deprecated.

WebTorrent version: 1.1.2 (webtorrent 0.91.0)
Node.js version: v5.11.0
Browser name/version (if using WebTorrent in the browser):

webtorrent-cli on npm 3.8.6 on Ubuntu 16.04 LTS
$ webtorrent --vlc magnet_uri

WebTorrent: `torrent.swarm` is deprecated. Use `torrent` directly instead.

UNEXPECTED ERROR: If this is a bug in WebTorrent, report it!
OPEN AN ISSUE: https://github.com/feross/webtorrent/issues

DEBUG INFO: webtorrent-cli 1.1.2, webtorrent 0.91.0, node v5.11.0, linux x64, exit 1
/usr/local/lib/node_modules/webtorrent-cli/bin/cmd.js:488
    var unchoked = torrent.swarm.wires.filter(function (wire) {
                                ^

TypeError: Cannot read property 'wires' of undefined
    at Timeout.draw [as _repeat] (/usr/local/lib/node_modules/webtorrent-cli/bin/cmd.js:488:33)
    at Timeout.wrapper [as _onTimeout] (timers.js:408:11)
    at Timer.unrefdHandle (timers.js:445:14)

Update:
I have deleted "swarm"s from cmd.js it works but when torrent finished this error appeared.
torrent downloaded successfully from 2/3 peers in 482s!

webtorrent is exiting...

UNEXPECTED ERROR: If this is a bug in WebTorrent, report it!
OPEN AN ISSUE: https://github.com/feross/webtorrent/issues

DEBUG INFO: webtorrent-cli 1.1.2, webtorrent 0.91.0, node v5.11.0, linux x64, exit 1
/usr/local/lib/node_modules/webtorrent-cli/node_modules/webtorrent/lib/torrent.js:1471
    if (self.discovery.tracker) self.discovery.tracker.complete()
                      ^

TypeError: Cannot read property 'tracker' of null
    at Torrent._checkDone (/usr/local/lib/node_modules/webtorrent-cli/node_modules/webtorrent/lib/torrent.js:1471:23)
    at /usr/local/lib/node_modules/webtorrent-cli/node_modules/webtorrent/lib/torrent.js:1423:14
    at /usr/local/lib/node_modules/webtorrent-cli/node_modules/simple-sha1/index.js:6:5
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

Yes, thanks for the report. I forgot to merge the PR I sent to webtorrent-cli: https://github.com/feross/webtorrent-cli/pull/6

Released as webtorrent-cli 1.1.3


[FEAT] Sort member roles

Library Version
5.0.2
Describe the Bug
The roles of a user are always mixed and not in the actually order
Steps to Reproduce
add yourself some roles on a server and run the code provided below
Expected Results
That the roles would be in the right order
Minimal Reproducible Code
@slash_command(name='roles')
async def roles_cmd(ctx: InteractionContext):
    for role in ctx.member.roles:
        print(role.name)

Traceback
No response
Checklist

[X] I have searched the open issues for duplicates.
[X] I have shown the entire traceback, if possible.
[X] I have removed my token from display, if visible.
[X] I have attempted to debug this myself, and I believe this issue is with the library

Additional Information
No response

I'll add this for a future release. But yes, astrea is completely right


Release new version of VS Code

This introduces the ability to manually enter a license key instead of requiring the user to sign in using GitHub or GitLab.

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

v0.105.0
GitHub release

Your semantic-release bot :package::rocket:


Cemu Vulkan 1.16.0 WIP crashes on Vega (not on Polaris) with Zelda BOTW (but works with Radeon GPU Profiler service enabled)

Hi,
don't know if you are aware but for a month all Cemu Vulkan preview builds (1.16WIP and only for patreons currently) cause crashes upon "new game" on Zelda breath of the wild on Vega GPUs on latest 19.8.1 driver as well as latest AMDVLK driver shared here..
what is more strange is that we don't have that artifact on Polaris hardware.. (some youtube videos show Vega VII (Vega 20) isn't affected also)..
I attach log with WIP7 altough latest WIP9 version fails too:
log - copia (3).txt
error seems:
[09:30:23] Failed to create graphics pipeline. Error -4
what's even more strange is that if you install latest Radeon GPU Profiler 1.6 and start Radeon Developer Panel and press "connect" so it starts the service (and an RGP OSD appears on all Vulkan apps) the Cemu Vulkan works correctly on Vega..
EDIT: the RGP OSD on Cemu shows "Radeon Developer mode" "Profiling Ready" and with that it works..
Hope AMD Vulkan guys gave a look at it as it affects it's latest Windows driver (2.0.99), AMDVLK open source driver (2.0.104) and also the Vulkan driver shipped with AMDGPU Pro 19.30 (shows as version 2.0.100)
EDIT:
2 things to note: all other drivers work Nvidia ones and Intel Anvil and also Mesa RADV works..
for running Cemu on Linux you need Wine built with patch for VK child window render support
(https://source.winehq.org/patches/data/167679)
also my thought is maybe because is compiles a lot (hundreds) of shaders/pipelines in few seconds which could be causing GPU TDR's?

@oscarbg , we don't have the environment to reproduce this issue, can you help to debug a little bit to find out why it's failed to create the pipeline?

Please re-open the issue if the issue is still there


Messages with arguments can not be used

I have an entry in messages.properties with arguments like:
user.login.success={0}, you have logged in.
how will i use it in java script.

I agree this should be built in, but here's what I did to get around it...
After the generated code is loaded, anywhere in javascript...
(function (win) { 	win.$oldL = $L; 	win.$L = function (options) { 		var retVal = $oldL(options.code); 		if (options.params) { 			for (var i = 0; i < options.params.length; i++) { 				var re = new RegExp("\\{" + i + "\\}","g"); 				retVal = retVal.replace(re, options.params[i]); 			} 		} 		return retVal; 	} }(this));
Then you just use it like...
$L({code: 'your.message.code', params: ['optional', 'params']});


Disabling the option "Display total number of tabs above the popup icon" is not persistent!

Hello,
I'm using FF60 and because I don't need the option of displaying tab count, I disabled the option but the problem is that the setting is not persistent! i.e. when closing FF and re-opening it again, I find the tab count returned again!

Same for me, FF61 for linux mint. I've had it like that for quite some time, perhaps since FF60, I don't really know.

Yesterday my screen blanked out when recovering from hibernation so I shut Ff down with keyboard shortcut instead of the close button on the window border. Then I shutdown my laptop with the power button instead of the menu before starting it again. When I started Ff the disabled option persisted! However after trying again to shut down Ff with keyboard shortcut or using Ff menu it didn't persist.
I'm open for more experimentation with shutdown procedures (but preferably not provoking blank outs...) if you think it can help you solve this.

I'm using Waterfox 56.2.14 (64-bit) (latest version) and any of the changes is persistent!
It started happening some days ago and is very annoying!
I've tried everything, reinstalling the add-on, reseting to defaults and setting all again, etc.
Every time I close the browser any settings I've changed is lost and back to defaults.

Hy.Here is what i just experienced.The tabs are not presented corectly.Here take a look i compered it with a session addon that i  use don't judge by the pages names.Thank you.


Create form to update an existing facility

Problem
At the moment we don't have a form where we can update an existing facility.
Success
We want a form where we able to update an facility. At the moment we don't have a figma for this form but we can use the same style for the existing form.
Since we are updating a  facility it means that most fields will not be required. Here is the graphQl input:
input UpdateFacilityInput {
  nameEn: String
  nameJa: String
  contact: ContactInput
  mapLatitude: Float
  mapLongitude: Float
  healthcareProfessionalIds: [Relationship!]
}

Requirements

[ ] Create input fields for updating a facility
[ ] Add field validation
[ ] Make a update request with the update data (should this be different PR?)

Implementation notes
[Suggest how this might be implemented.]

This is going to be split into two tickets. One for the UI/UX and one for the functionality


chef-client doesn't properly reset the ruby environment

Description
It appears that in Chef version 12.0.0, a fix was implemented for https://github.com/chef/chef/issues/2548. The fix was to use some ruby code to clear out the GEM_HOME and GEM_PATH environment variables:
ENV["GEM_HOME"] = ENV["GEM_PATH"] = nil unless ENV["APPBUNDLER_ALLOW_RVM"] == "true"
However, if the Gem/Gem::Specification class is initialized before the environment variables are reset then the fact that they are nil doesn't matter.
However, adding Gem.clear_paths after the ENV reset will cause the Gem/Gem::Specification classes to re-read the environment on the next command and will result in a working chef-client run. Seems like this is the logic next step for the original fix introduced.
A script that simply unsets GEM_HOME and GEM_PATH resolves this issue as does rvm system since there is no system ruby and therefore that rvm command simply unsets the variables.
Chef Version
12.16.42
Platform Version
CentOS 6.8
Replication Case

Bootstrap node with 12.16.42
Install rvm::system (using https://github.com/martinisoft/chef-rvm version 0.9.4)
Logout
Log back in
sudo to root (sudo su -)
run /opt/chef/bin/chef-client

Client Output
       /opt/chef/embedded/lib/ruby/site_ruby/2.3.0/rubygems/dependency.rb:308:in `to_specs': Could not find 'addressable' (= 2.4.0) among 17 total gem(s) (Gem::MissingSpecError)
       Checked in 'GEM_PATH=/usr/local/rvm/gems/ruby-2.3.1:/usr/local/rvm/gems/ruby-2.3.1@global', execute `gem env` for more information
       	from /opt/chef/embedded/lib/ruby/site_ruby/2.3.0/rubygems/dependency.rb:320:in `to_spec'
       	from /opt/chef/embedded/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:65:in `gem'
       	from /opt/chef/bin/chef-client:4:in `<main>'

Stacktrace
See output above.

already fixed in https://github.com/chef/appbundler/pull/24 appbundler seems to need a gem release


Always restart sssd after changing sssd.conf

This was not happening under RHEL. We don't necessarily need to
restart it immediately either.

why not a reload instead of a restart?

I've not looked at this in a while. Maybe it would work, I think I only used restart because that's what was there before.


fix_save says it cant find python

so i basically have no clue what im doing or how to work/use python or any of this but i was fallowing the readme for the fixed save and when i opened  file i get the fallowing

yeti have python 3.13 installed so im at a loss i even tried clicking on the python file its self and it just open and closes. so i have no clue if im doing something wrong, i did try looking for videos on youtube to see if anyone had a guide up on how to use this to see if that would make it easier on for me to fallow along but couldnt find any. really need the help so i can get my offline world working right for me showing up on my dedicated sever

How to Install Python Properly (Without Breaking Things!)
1. Download Python

Go to the official site: https://www.python.org/downloads/.
Download the version for your operating system.

2. Run the Installer

Open the downloaded installer (probably named something like python-<version>.exe).

3. The Important Part

Before clicking Install Now, CHECK the box at the bottom that says:
"Add Python to PATH" 🟩
(This is what makes Python accessible from the command line!)

4. Install Python

Click Install Now and let it do its magic.

5. Verify the Installation

Open a terminal (Command Prompt, PowerShell, or Bash).
Type:python --version

If you haven't solved it, follow the top two answers on this : https://stackoverflow.com/questions/65348890/python-was-not-found-run-without-arguments-to-install-from-the-microsoft-store
it worked for me


cargo-deny: 0.9.1 -> 0.10.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/EmbarkStudios/cargo-deny/releases.
meta.description for cargo-deny is: "Cargo plugin to generate list of all licenses for a crate"
meta.homepage for cargo-deny is: "https://github.com/EmbarkStudios/cargo-deny"
meta.changelog for cargo-deny is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/nix/store/y7aj2prvi241df7j95qcl55683k7nhnh-cargo-deny-0.10.0/bin/cargo-deny passed the binary check.
1 of 1 passed binary check by having a zero exit code.
1 of 1 passed binary check by having the new version present in output.
found 0.10.0 with grep in /nix/store/y7aj2prvi241df7j95qcl55683k7nhnh-cargo-deny-0.10.0
found 0.10.0 in filename of file in /nix/store/y7aj2prvi241df7j95qcl55683k7nhnh-cargo-deny-0.10.0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
cargo-deny

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/y7aj2prvi241df7j95qcl55683k7nhnh-cargo-deny-0.10.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cargo-deny https://github.com/r-ryantm/nixpkgs/archive/c40049dcda10ab0d5d6b71276aff1451f4b8acaf.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/y7aj2prvi241df7j95qcl55683k7nhnh-cargo-deny-0.10.0
ls -la /nix/store/y7aj2prvi241df7j95qcl55683k7nhnh-cargo-deny-0.10.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

cargo-deny

Maintainer pings
cc @matthiasbeyer for testing.

Result of nixpkgs-review pr 143857 run on x86_64-linux 1

1 package built:

cargo-deny


'this' as default parameter value in a function refers to the wrong object

Here's a short example:
A: class {
	value := 0
	other: Int
	init: func
	foo: func (v := this value) {
		this other = v
	}
}

B: class {
	whatever := 1
	init: func
	bar: func (w := this whatever) -> Int {
		a := A new()
		a foo()
		a other
	}
}

b := B new()
something := b bar(2)

The value of v in foo should be this value but this does not point to itself but rather to the calling object b and fails with: error: ‘example__B’ has no member named 'value'
The same happens if the last line is replaced with something := b bar(), then the default value of w in bar fails because this is undeclared (we're not calling from any object).
(I assume this is not by design.)

(I assume this is not by design.)

haha, definitely not by design

Huh, fun one.


write/elf: mark .data.rel.ro as SHF_WRITE

See https://github.com/bjorn3/rustc_codegen_cranelift/issues/921 for more context.

Coverage increased (+0.7%) to 53.96% when pulling c4350b735d08e7556ee1822e19252894ef49ccad on bjorn3:elf_rel_ro_write into ff506cc4eb27a3e1f0f6bd3e9ebb25359ab3eee8 on gimli-rs:master.

Is there anything you still want to change before the next release?

Replacing goblin has been a major change, so I wanted to do more validation of that, but I don't currently have much time.  Did you test cg_clif with both ELF and Mach-O?

I have somewhat tested it with ELF. (not the full cg_clif test suite though) I haven't tested with Mach-O. I think I will create a draft PR for cg_clif tomorrow, so I can test it on CI.

Both ELF and Mach-O work fine for cg_clif on CI: https://github.com/bjorn3/rustc_codegen_cranelift/runs/509535100

Great, thanks for testing. I'll try to do some sanity checks for a couple of other users of this crate, and do a release this week.

0.18.0 is released.


numbers in header name

The current validation for header names (line ~100) is:
allowHeaders: Joi.array().min(1).items(Joi.string().regex(/^[a-zA-Z-]+$/))

We have a case where our header contains numbers. Amazon requires a special header when using signed (authenticated) requests: X-Amz-Content-Sha256. http://docs.aws.amazon.com/general/latest/gr/signature-version-4.html. The current validation regex fails on the #'s in the header name.
I think a more appropriate regex would be /^(\w|-)+$/.

Fixed in release v0.1.2!

Thanks!


[Help] Importing css errors, alias not working.

Found an issue or bug? Tell me all about!
Sorry, this may not be a bug and is probably more likely an issue on my end, please forgive me if so.
I am trying to make use of SCSS, the vue-loader seems to already be included in the config, and I have installed the needed modules. However I am unable to import the SCSS sheet containing my variables and mixins.
Describe the issue / bug.
Reddit post: https://www.reddit.com/r/vuejs/comments/66x5rm/having_trouble_importing_scss_undefined/
Error: http://imgur.com/a/ZUcLm
No matter what I have tried I can not get the correct path to the file or there is some other issue with the configuration. The var.scss file needs to be loaded into the app.vue file.
The alias doesn't appear to work as well which makes me think maybe the path isn't the issue.
I have tried many different path variations but no luck.

./var
./var.scss
var
var.scss
~/var.scss
~/var
~var

#
How can I reproduce this problem?
Attempt to import css
#
If visual, provide a screenshot.
http://imgur.com/a/ZUcLm
#
Tell me about your development environment.

Node version: 6.9.3
NPM version: 3.10.10
vue-cli version: (if necessary)
Operating System: Windows 10 build 1703

If you are looking to suggest an enhancement or feature, then feel free to remove everything above.

Hi,
try this: (it should work :))
 @import './../var.scss'
if you want to put your scss files in src/assets/scss
the import should be like this:
@import './../assets/scss/var.scss'
other notice:
the path is from App.vue if you work with another component inside components folder then you must add another level to the path (i mean /../)
@import'.**/../**../assets/scss/var.scss'
look at the picture my folder named css

@Ampix0
You're initial try with @import "renderer/var.scss"; was just missing the ~. Change it to @import "~renderer/var.scss";.
One extra thing to note, if you are wanting to use a variables file you would have to import this file in every component that needs it. But luckily, you can actually import a variables files directly into the loader so all components have access to it without having to manually import it every time.
This can be done by updated the vue-loader configuration in webpack.renderer.config.js at line 54.
scss: 'vue-style-loader!css-loader!sass-loader?data=@import "~renderer/vars.scss";'

@SimulatedGREG unfortunately that is not working as well, that's currently how i have it written. I'm going to try @NadhirBoukhenifra suggestions now as well and report back.
error:

         ERROR in ./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-09a923c1!./~/sass-loader/lib/loader.js!./~/vue-loader/lib/selector.js?type=styles&index=0!./app/src/renderer/App.vue
         Module build failed:
         undefined
         ^
               File to import not found or unreadable: ~renderer/var.scss.
         Parent style sheet: stdin
               in C:\Users\Ampix0\Documents\GitHub\electron-vue\tickr-for-robinhood\app\src\renderer\App.vue (line 15, column 1)
          @ ./~/vue-style-loader!./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-09a923c1!./~/sass-loader/lib/loader.js!./~/vue-loader/lib/selector.js?type=styles&index=0!./app/src/renderer/App.vue 4:14-269 13:2
-17:4 14:20-275
          @ ./app/src/renderer/App.vue
          @ ./app/src/renderer/main.js
          @ multi (webpack)-dev-server/client?http://localhost:9080 webpack/hot/dev-server ./app/src/renderer/main.js

@NadhirBoukhenifra your direct relative path did work. So somehow my issue is resolving the alias. Thank you for getting me this far.

@NadhirBoukhenifra
Do you have a project repo I could look at?

@SimulatedGREG almost untouched.
https://github.com/Ampix0/ticker-for-robinhood

@Ampix0

Your vars.scss isn't in your app/src/renderer folder like your original screenshot implied. Moving that file to the renderer folder and using the method of injecting into the loader itself should do the trick.

@SimulatedGREG Well that's embarrassing... Not sure if the file was somehow moved or if the indenting in my IDE tricked me. Eitherway I apologize for wasting everyone's time!

No problem, I know that struggle as well. Glad we got this sorted out.

Hello everyone,
I has an issue for importing my styles. I followed the instructions from the "Using Pre-Processors" page in the doc.
Here is my folder architecture:

And here is what I wrote in consequence in my webpack.renderer.config.js:
{
    test: /\.vue$/,
        use: {
            loader: 'vue-loader',
            options: {
                loaders: {
                    sass: 'vue-style-loader!css-loader!sass-loader?indentedSyntax=1&data=@import "./src/renderer/scss/style"',
                    scss: 'vue-style-loader!css-loader!sass-loader?data=@import "./src/renderer/scss/style";'
            }
        }
    }
},

Unfortunatley this failed to compile and I got the following error message:

I managed to fix this by changing the source in my webpack.renderer.config.js like so:
loaders: {
    sass: 'vue-style-loader!css-loader!sass-loader?indentedSyntax=1&data=@import "renderer/scss/style"',
    scss: 'vue-style-loader!css-loader!sass-loader?data=@import "renderer/scss/style";'
}


Bump haskell.nix

Might fix our shell issue.

Pre-submit checklist:

Branch

[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages
[ ] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] Reviewer requested

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

Configuring ghc-prim-0.6.1...
ghc-cabal: Cannot find the program 'alex'. User-specified path
'/nix/store/08cf7qvrhfk9cfr31n9wxcfxjh25k9zv-alex-exe-alex-3.2.4/bin/alex'
does not refer to an executable and the program is not on the system path.

Hmm. Seems to be on macs. @hamishmack have you seen this before?

Now it's failing in a different way. Good stuff. Seems like maybe it's non-deterministic, perhaps I should just let it get on with it...

The different way:

libraries/mtl/Control/Monad/RWS/Strict.hs:20:8: error:
Could not find module ‘Prelude’
There are files missing in the ‘base-<IP_ADDRESS>’ package,
try running 'ghc-pkg check'.
Use -v to see a list of the files searched for.
|
20 | module Control.Monad.RWS.Strict (
|        ^^^^^^^^^^^^^^^^^^^^^^^^
libraries/mtl/Control/Monad/RWS/Strict.hs:51:1: error:
Could not find module ‘Control.Monad’
There are files missing in the ‘base-<IP_ADDRESS>’ package,
try running 'ghc-pkg check'.
Use -v to see a list of the files searched for.
|
51 | import Control.Monad
| ^^^^^^^^^^^^^^^^^^^^
libraries/mtl/Control/Monad/RWS/Strict.hs:52:1: error:
Could not find module ‘Control.Monad.Fix’
There are files missing in the ‘base-<IP_ADDRESS>’ package,
try running 'ghc-pkg check'.
Use -v to see a list of the files searched for.
|
52 | import Control.Monad.Fix
| ^^^^^^^^^^^^^^^^^^^^^^^^
libraries/mtl/Control/Monad/RWS/Strict.hs:53:1: error:
Could not find module ‘Data.Monoid’
There are files missing in the ‘base-<IP_ADDRESS>’ package,
try running 'ghc-pkg check'.
Use -v to see a list of the files searched for.
|
53 | import Data.Monoid
| ^^^^^^^^^^^^^^^^^^

And it made it. Go figure.

Okay, now the dependency is gone. Turns out we didn't need the haskell.nix bump but it doesn't hurt I guess.


Please reword the following message

Please reword this message:
"Error | VSSDK002 | The   PackageRegistrationAttribute.AllowsBackgroundLoading should be set to true if   and only if the package derives from AsyncPackage.
-- | -- | -- "
In fact, from that message, it wasn't clear to me that my package, which derives from AsyncPackage had the AllowsBackgroundLoading set to false.

Will wait for more feedback before investing in splitting this message up into two based on the code.


fix: Material update

About this PR

Closes #

Technical highlight/advice

How to test my changes

Checklist

[ ] I didn't over-scope my PR
[ ] My PR title matches the commit convention
[ ] I did not include breaking changes
[ ] I made my own code-review before requesting one

I included unit tests that cover my changes

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

I added/updated the documentation about my changes

[ ] 📜 README.md
[ ] 📕 docs/*.md
[ ] 📓 docs.lenra.io
[ ] 🙅 no documentation needed

I still need to find out why the LenraTable component size has changed since Material was updated. It is 6 pixels too big in height.

The Switch widget also changed in Material 3.
It seems hard to adapt it so we might need to create a custom widget.
https://blog.logrocket.com/advanced-guide-flutter-switches-toggles/#creating-a-custom-animated-switch-button

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 71.52%. Comparing base (26cc6d8) to head (3758e55).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             beta     #123      +/-   ##
==========================================
- Coverage   71.71%   71.52%   -0.19%
==========================================
  Files          38       38
  Lines         912      906       -6
==========================================
- Hits          654      648       -6
  Misses        258      258

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:tada: This PR is included in version 1.0.0-beta.53 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


React Calendar events are not working in IE

Hi team,
React Calendar events are not working in IE. It is working fine in chrome.Am I missing anything?
Please let me know if anybody has idea.
Thanks

install polyfills for foreach, it should work fine

install polyfills for foreach

Hi I installed polyfills using below command still getting the issue. kindly suggest if I am missing anything.
Thanks

install missing polyfills for IE as well.

install polyfills for foreach

Hi I installed polyfills using below command still getting the issue. kindly suggest if I am missing anything.
Thanks

install missing polyfills for IE as well.

install polyfills for foreach

Hi I installed polyfills using below command still getting the issue. kindly suggest if I am missing anything.
Thanks

It is working..
thanks,


Prevent volume usage alerts

What this PR does / why we need it:
KubePersistentVolumeUsageCritical is filed when pv free disk space goes below 5%. The PR sets elasticsearch curator disk space threshold also to 5% (1.5Gi for shoot cp, and 5Gi for garden ns) to prevent the alert.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
@wyb1 , @mvladev
Release note:

NONE

/hold
Let me check.

/hold cancel
Updated KubePersistentVolumeFullInFourDays to ignore elastic pvc, curator should clean up when free disk space is < 5%.

/lgtm


python-pytest-xdist: disable tests on darwin

Motivation for this change
Not sure why the failure only happens on darwin (python3). http://hydra.nixos.org/build/52755528
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Pushed https://github.com/NixOS/nixpkgs/commit/e5a4da2ab8687c52d140653cc0fb17e2344f48a6
Hopefully we now get a channel update again.

Hmm, I didn't check the build before pushing, but I'm getting failing tests on NixOS as well.
I've disabled tests on 2.x and pushed a version bump https://github.com/NixOS/nixpkgs/commit/37cb24a318f1c54f2a84cbca84c9bfb1d500289c

Strange, pretty sure I tested it on both platforms.


[WIP] Add a scikit-learn interface

Will close https://github.com/ray-project/xgboost_ray/issues/96 after it's finished.
Also includes https://github.com/ray-project/xgboost_ray/pull/110, so that should be merged first.
Issue: As this interface inherits from xgboost's sklearn interface, it may be hard if not impossible to make this interface compatible with all xgboost versions supported by xgboost-ray. We may have to consider setting an additional xgboost version requirement just for this interface in order to avoid issues.
tests/test_sklearn.py is copied almost verbatim from https://github.com/dmlc/xgboost/blob/a5c852660b1056204aa2e0cbfcd5b4ecfbf31adf/tests/python/test_with_sklearn.py in order to ensure 1:1 coverage, with minimal modifications. Some tests were disabled due to not being applicable for a distributed setting.

I think it's only missing readme changes & and example at this point


[DATA] Data for Bojanala district and Dr Kenneth Kaunda district in North West is swapped around

Which Dataset
https://github.com/dsfsi/covid19za/blob/master/data/district_data/provincial_nw_cumulative.csv
Error Description
The number of cases for Bojanala district and Dr Kenneth Kaunda in North West is swapped around.
https://twitter.com/NorthWestDOH/status/1284388516902862850/photo/1
Suggested fixes

Swap headings
Swap data

Fixed @h-khoza
Please check and close if satisfied


Changed styling of description lists, images, links, and headlines

Added more styling for description lists, links and images.
Also changed the fonts and styling of headlines.
Also fixed the site on mobile.

Clean :+1:


Update scala3-library, ... to 3.0.1

Updates

org.scala-lang:scala3-library
org.scala-lang:scala3-library_sjs1

from 3.0.0 to 3.0.1.
GitHub Release Notes - Version Diff - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (3.0.0).
You might want to review and update them manually.
CHANGES.md
CONTRIBUTING.md
monix-catnap/shared/src/main/scala/monix/catnap/FutureLift.scala
monix-catnap/shared/src/main/scala/monix/catnap/Semaphore.scala
monix-eval/shared/src/main/scala/monix/eval/Coeval.scala
monix-eval/shared/src/main/scala/monix/eval/CoevalLift.scala
monix-eval/shared/src/main/scala/monix/eval/CoevalLike.scala
monix-eval/shared/src/main/scala/monix/eval/Task.scala
monix-eval/shared/src/main/scala/monix/eval/TaskLift.scala
monix-eval/shared/src/main/scala/monix/eval/TaskLike.scala
monix-eval/shared/src/main/scala/monix/eval/internal/CoevalDeprecated.scala
monix-eval/shared/src/main/scala/monix/eval/internal/TaskDeprecated.scala
monix-eval/shared/src/main/scala/monix/eval/package.scala
monix-execution/jvm/src/main/scala/monix/execution/internal/Platform.scala
monix-execution/jvm/src/main/scala/monix/execution/schedulers/ExecutorScheduler.scala
monix-execution/shared/src/main/scala/monix/execution/Scheduler.scala
monix-execution/shared/src/main/scala/monix/execution/UncaughtExceptionReporter.scala
monix-execution/shared/src/main/scala/monix/execution/cancelables/package.scala
monix-execution/shared/src/main/scala/monix/execution/misc/LocalDeprecated.scala
monix-execution/shared/src/main/scala/monix/execution/misc/package.scala
monix-execution/shared/src/main/scala/monix/execution/rstreams/package.scala
monix-execution/shared/src/main/scala_3.0-/monix/execution/misc/Local.scala
monix-execution/shared/src/main/scala_3.0/monix/execution/misc/Local.scala
monix-reactive/shared/src/main/scala/monix/reactive/ObservableLike.scala
monix-reactive/shared/src/main/scala/monix/reactive/internal/deprecated/ObservableDeprecatedBuilders.scala
monix-reactive/shared/src/main/scala/monix/reactive/internal/deprecated/ObservableDeprecatedMethods.scala
monix-tail/shared/src/main/scala/monix/tail/internal/IterantDeprecated.scala
project/MimaFilters.scala

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang" } ]

labels: library-update, semver-patch, old-version-remains

Superseded by #1489.


proposal: built-in wrapper interface

I was wondering if Unwrap Is As %w can be abstracted for other type's too, not only for errors and introduce a more general build-in wrapper interface instead?
package wrapper

type Wrapper interface {
	Unwrap() Wrapper
}

func Unwrap(w Wrapper) Wrapper {
	if w != nil {
		return w.Unwrap()
	}
	return nil
}

package wrapper_test

import (
	"testing"
	"wrapper"
)

type wrapperT struct{ s string }

func (w wrapperT) Unwrap() wrapper.Wrapper { return nil }

type wrappedT struct {
	s string
	w wrapper.Wrapper
}

func (w wrappedT) Unwrap() wrapper.Wrapper { return w.w }

func TestUnwrap(t *testing.T) {
	w1 := wrapperT{"wrapper"}
	w2 := wrappedT{"wrapper wrap", w1}

	testCases := []struct {
		w    wrapper.Wrapper
		want wrapper.Wrapper
	}{
		{nil, nil},
		{wrappedT{"wrapped", nil}, nil},
		{w1, nil},
		{w2, w1},
		{wrappedT{"wrap 3", w2}, w2},
	}
	for _, tc := range testCases {
		if got := wrapper.Unwrap(tc.w); got != tc.want {
			t.Errorf("Unwrap(%v) = %v, want %v", tc.w, got, tc.want)
		}
	}
}

https://github.com/golang/go/issues/29934
I am doing this in a separate proposal because the more I think about it, the more I think this decision needs to be made before the new error packages goes life because don't think this can be made backward compatible once the new error package goes life with it's locked in type error in wrap.go
In short this would be the way forward in my opinion in Go2
type error interface {
	Error() string
	Unwrap() wrapper
}

type wrapper interface {
	Unwrap() wrapper
}

Monad is definitely not the right name for this. A “monad” has two characteristic operators: Haskell calls them return and >>=, although you may also seem them called unit and bind. To form a monad, those operators have to have particular algebraic relationship (often called the “monad laws”).
The Unwrap function does not correspond to either of those operators.

Note that the proposed Monad interface will not match any types in existence today.
See https://golang.org/doc/faq#covariant_types.

Thanks, will change the name to Wrapper.
But it could mach Error types in 1.13 right? I strongly believe a Wrapper interface would be in the same line as Reader and Writer?

No, it will never match any existing type. The type Wrapper (or Monad or what-have-you) is distinct from, say, the type error, so a method with the signature Unwrap() error will never match the method Unwrap() Wrapper in the interface definition.

Ok but doesn't make Unwrap() Wrapper make more sense then Unwrap() error
I agree that for example the severHTTP method from the http Handler interface doesn't return a concrete type but didn't the http Handler interface proof that making a general interface like that has a huge advantage making http handlers more universal? Maybe I am comparing apples with oranges here but hope most can see the pattern here what I am trying to explain.

So the errors package would look like this instead
package errors

import "wrapper"

func New(text string) error {
	return &errorString{text, nil}
}

type errorString struct {
	s string
	w wrapper.Wrapper
}

func (e *errorString) Error() string {
	return e.s
}

func (e *errorString) Unwrap() wrapper.Wrapper {
	return e.w
}

I guess modifying the buildin error interface going to much to ask for :(
--- FAIL: TestDependencies (0.23s)
    deps_test.go:547: unexpected dependency: errors imports [wrapper]
    deps_test.go:547: unexpected dependency: wrapper imports [internal/reflectlite]

I also made this suggestion but no one noticed AFAICT. I think it would be useful for the http optional interfaces but it requires thinking through.

I'm implementing it in https://golang.org/cl/184818 to have a exact estimate what would break but I am stuck :(
When I do ./all.bash I get
errorString does not implement error (wrong type for Unwrap method)
                have Unwrap() wrapper
                want Unwrap() <T>

I guess I am missing some wrapper register step or something, need help :(

I haven't looked at your CL, but you cannot add methods to the error interface (or any interface in the standard library really), as that would break preexisting code that wrote their own implementation of that interface.

Yep understand, but would like to have a better estimate how much would break, and how much benefit we can gain by testing it and be able to show examples. As far as I can tell it's not that many lines of code to make the compiler and the complete standard library work? But then again I could be totally wrong here.

Why would it matter how much would break? The Go 1 Compatibility docs says that no amount of breakage is acceptable with few acceptable exceptions (none of which seem to apply in this case).
Note: I'm not talking about breaking the standard library, I'm talking about breaking public non-standard-library code. For instance, here is a hypothetical pre-existing Go program which cannot break: https://play.golang.org/p/Ia3Ic7uySAe. There will be other such programs.

Yes but now modules can mitigate that specifying the go version. So if we can proof only a limited amount of cases will break then it still worth for Go2. If however it turns out it brings havoc to the complete Go community and even the standard library then, yes it's not worth it. But I still believe the complete standard library can work with minor changes. Which is a good start for a Go2 proposal

I don't believe that module go versions help in this situation.
A module with "go 1.13" needs to be able to import and use a library from a module with "go 1.14" and vice-versa; if the two modules don't agree on the "error" interface, I don't see how that could be managed sensibly. For instance, if the "go 1.14" module calls a function from the "go 1.13" module which returns an error, then it will be able to call "Unwrap" on that error, even though the implementation of that error type (inside the "go 1.13" module) didn't necessarily need to implement said "Unwrap" method.
(I should note that this is the simplest possible example; there are more complicated examples where the type gets from the "go 1.13" module to the "go 1.14" module not directly as a value of type error, but as an interface{}, and then the "go 1.14" module type-casts it to the error interface)

Agree then a conversion tool is going to be required or modifying the code which I assume for now be trivial fixes until I can test it better by compiling common repos with this change.

Sorry, your last comment was a little ambiguous, so I just wanted to make sure I said it clearly for the record:
If I upgrade my compiler and recompile my code, the Go 1 compatibility document essentially says that my code must compile with the new compiler (assuming it compiled with the old compiler). Relatedly, if I upgrade my compiler, all the code I depend on must also compile, even if I cannot make any modifications to that code.
If a language change requires a conversion tool when upgrading compilers, or requires modifying the code at all when upgrading compilers (no matter how trivial the modifications), then it is not meeting the standard set in the Go 1 compatibility document.
(Unfortunately, I might not get a chance to respond to further comments as I might have limited network connectivity for a while)

Here is the gist I wrote before arguing that Is/As could be made to use interface{} and work generally: https://gist.github.com/carlmjohnson/d06cd8d10e0aef65f565a55cc57cd986
The signature needed is just interface { Unwrap() interface{} } with optional Is and As extensions to override the normal wrapping behavior.

You will get better debug messages with a specified wrapper interface I think but anyway if we manage to make this work then it going to be trivial to make your version work and compare because it requires a lot less changes to the compiler I assume.

I think this decision needs to be made before the new error packages goes life because don't think this can be made backward compatible once the new error package goes life with it's locked in type error in wrap.go

It's pretty clearly too late to make a language change for Go 1.13.
Also, in this example:
type error interface {
	Error() string
	Unwrap() wrapper
}

The error type is not mandated to have an Unwrap method, even in Go 1.13, nor will it ever be required to have one. And the current optional Unwrap method returns another error, not a wrapper. That is, it's important that it doesn't unwrap to some other non-error thing.
Given that error can't and won't adopt this, it doesn't seem like it needs to be a language built-in at all. And maybe if we do generics you will be able to write Wrapper(T) that has Unwrap() T.

Agree when we have generics you win :P but until then carlmjohnson or I win because wrapping anything you want was the main purpose so you can use it for wrapping logs etc also :)
I admit your new error handling is awesome but pushing it before we have generics feels to me like we are going to regret it in the future especially after I actually could try this proposal https://golang.org/cl/184818 thx to @mdempsky

Generics don’t really have anything to do with wrapping. Any type system powerful enough to express the concept of wrapping is also so powerful that it makes no meaningful guarantees about what it contains, so you don’t gain anything.
I think in general people overestimate the advantages of static typing for expressing complex types. If it’s complex, your static type is as likely to be buggy as anything else. Just use dynamic types and move on.

that can also be true, once I can play with generics then it could be I have to agree with you on that too


Get opentelemetry trace id from request headers instead of creating a new trace

What does this PR do?
Fixes #2376
I made a simple middleware to extract OpenTelemetry context (e.g. trace id, span id) from request headers. When valid transparent info is provided, then, it'll gonna use that context to create the span (if not, it'll generate its own as it does currently).
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[x] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[x] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@OlivierDehaene OR @Narsil

@Narsil @OlivierDehaene @ErikKaum hi! if you have the bandwidth, could you by any chance review this PR? thanks!
related PR: https://github.com/huggingface/text-embeddings-inference/pull/425

Sorry I was confused.
We already have a context extractor that we set here. It should already parse the W3C format and therefore the traceparent header so I'm not sure what exactly is the problem here.
Let me get back to you.

Sorry I was confused. We already have a context extractor that we set here. It should already parse the W3C format and therefore the traceparent header so I'm not sure what exactly is the problem here. Let me get back to you.

Hi. Thanks for the response.
from these two comments, https://github.com/huggingface/text-generation-inference/issues/2376#issuecomment-2290216997, https://github.com/huggingface/text-generation-inference/issues/2376#issuecomment-2293051826, I guess it seems the axum opentelemetry integration doesn't just do it automatically unlike most other frameworks. So, I just made a simple middleware to parse the traceparent header and manually inject it. please let me know if you find a better way to implement this!


Building use Nix flake fails with error: cannot coerce a set to a string

Describe the bug?
The docs mention you can use Nix (flakes) to build the project, but cloning the repo and running nix build fails with(without full stacktrace):
error: cannot coerce a set to a string

       at /nix/store/hm561lqf9zg7q0bx3j3rax74bnq0hjnf-source/flake.nix:35:38:

           34|         packages.erg = pkgs.rustPlatform.buildRustPackage {
           35|           inherit (cargoToml.package) name version;
             |                                      ^
           36|           src = builtins.path {
(use '--show-trace' to show detailed location information)

Reproducible code
git clone https://github.com/erg-lang/erg.git && cd erg

If you have direnv and nix-direnv installed (I do):
direnv allow

And running the build:
nix build

Expected result
A successful compilation.
Actual result
~/d/erg/erg main 1.2s | 1 ❱ nix build --show-trace
error: cannot coerce a set to a string

       at /nix/store/hm561lqf9zg7q0bx3j3rax74bnq0hjnf-source/flake.nix:35:38:

           34|         packages.erg = pkgs.rustPlatform.buildRustPackage {
           35|           inherit (cargoToml.package) name version;
             |                                      ^
           36|           src = builtins.path {

       … while evaluating the attribute 'version' of the derivation 'erg'

       at /nix/store/gx2yx1nc9i1q0r7vszcafyv52gmdwnqw-source/pkgs/stdenv/generic/make-derivation.nix:270:7:

          269|     // (lib.optionalAttrs (attrs ? name || (attrs ? pname && attrs ? version)) {
          270|       name =
             |       ^
          271|         let

Additional context
No response
Erg version
main branch
Python version
None
OS
macOS 13 (Ventura)

I see there was an update for the Nix flake, but currently with a fresh clone, getting the following error/warning:
~/d/erg/erg main ❱ nix build
error: builder for '/nix/store/sr6frjpwk8bvn7a4gci22yk0qsid6l2j-erg.drv' failed with exit code 101;
       last 10 log lines:
       > Executing cargoBuildHook
       > ++ env CC_aarch64-apple-darwin=/nix/store/b9bh3z78rqff14bf0fd78xb07b5cnwdw-clang-wrapper-11.1.0/bin/cc CXX_aarch64-apple-darwin=/nix/store/b9bh3z78rqff14bf0fd78xb07b5cnwdw-clang-wrapper-11.1.0/bin/c++ CC_aarch64-apple-darwin=/nix/store/b9bh3z78rqff14bf0fd78xb07b5cnwdw-clang-wrapper-11.1.0/bin/cc CXX_aarch64-apple-darwin=/nix/store/b9bh3z78rqff14bf0fd78xb07b5cnwdw-clang-wrapper-11.1.0/bin/c++ cargo build -j 10 --target aarch64-apple-darwin --frozen --release
       > error: failed to parse manifest at `/private/tmp/nix-build-erg.drv-0/nqa6wd2nk4hfxi7z1rmk9ird5h0m41np-source/Cargo.toml`
       >
       > Caused by:
       >   feature `workspace-inheritance` is required
       >
       >   The package requires the Cargo feature called `workspace-inheritance`, but that feature is not stabilized in this version of Cargo (1.62.0).
       >   Consider adding `cargo-features = ["workspace-inheritance"]` to the top of Cargo.toml (above the [package] table) to tell Cargo you are opting in to use this unstable feature.
       >   See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#workspace-inheritance for more information about the status of this feature.
       For full logs, run 'nix log /nix/store/sr6frjpwk8bvn7a4gci22yk0qsid6l2j-erg.drv'.

Yes, it looks like Nix are using an old version of cargo/rustc. I'm looking into how to update the dependencies now (I wasn't the one who added the Nix installing script).

I tried doing fixing it as well, but I'm clueless in Rust land :P.
Usually nix flake update does things for me


No animation when element hitting top edge of viewport

This is:
Bug/Feature request/Question depending on how you look at it
Specifications

AOS version: demo page
OS: Android 8.1 / 7.1.2 / probably all
Browser: Chrome / Firefox latest

Expected Behavior
Animate element when scrolling down and element leaves viewport on top edge and other way around also of course when scrolling up and element comes into viewport on top edge.
Or maybe that's better to understand (read from beginning to end and end to beginning too): element invisible above viewport, animation on top edge, element visible inside viewport, animation on bottom edge (that currently solely is), element invisible below viewport
Actual Behavior
Animation only on bottom edge
Steps to Reproduce the Problem
Scrolling inside demo
Possible Solution
If this is by intention add option to animate also on top edge.

Did you try the option mirror:true in init?

Hi @su-ex! I believe what you're looking for is the mirror option, as @MarioPerini pointed. Check out documentation for more informations. If it's not - feel free to reopen this issue and tell us more about what are your expectations in regards to the mirror setting.

Sorry, I've run out of time and forgot about this until I saw the notification bell on GitHub.
Yes, mirror option sounds good. I don't know how I could ooversee this although I actually read through all options.
But another question arrives out of that: With mirror top and bottom animation would be the same if I see it right, but if I want some sort of continuous scrolling page where elements fly in from top on the top side and from the bottom on the bottom side how could it be possible to achieve that?

You can change the data-aos parameter with JS if you watch for the class aos-init and aos-animate.

@MarioPerini
You mean detecting scrolling direction and then setting sort of animation dependant on that? At least that's the idea I got about that. But how would those events help me to achieve that? Also if I listen to those events, won't it already be too late to change the type of animation? Or when are those events triggered (before starting animation (what I would need) it after or while) or could the animation be deferred somehow till some stuff is done?
It's just that I'm unsure about all the corner cases meaning what is if it's detecting the scrolling direction exactly in the moment the AOS animation gets triggered, will it be too late to change it and the old one gets played? Hmm, I'll just experiment a bit with this at the end of the week (when I hopefully get some time for experiments 😋 ) and see what I can achieve. I'll try it with mirror: true, detect scrolling direction and set animation dependant on that (either by awaiting this in event or through changing the data-aos). Maybe it works well enough with ignoring some corner cases or this actually just works. Thanks for all your tips!


Bootstrap dropdown-menu doesn't get close when clicking an element

I'm firing the bootstrap v3.3.5 dropdown menu by using the javascript function dropdown('toggle') as stated in the docs.
Usually dropdowns would hide whenever you click outside them or you select one of their options.
This doesn't happen when firing it through javascript.
In this reproduction you'll see two menus:

One which works as expected as its fired using the "components" trigger
And another one, using the right click of the mouse, which doesn't work as expected. (it doesn't get closed on click outside or even on element click)

I was able to "manually" get rid of the dropdown menu when clicking outside it by using the following:
$('body').removeClass('open');

But I'm not quite sure why dropdown menus don't work in the same way as when you fire them by the normal procedure.
And having to manually hide them doesn't seem like the best solution...
I opened the same issue in stackoverflow but I didn't get a good solution.

A. You're calling $('#menu').dropdown('toggle') twice in your event handler method
B. You're missing a
 around the

C. You're missing an element with data-toggle="dropdown" (Not explicitly documented, but followed by all the examples and related to the warning in http://getbootstrap.com/javascript/#callout-dropdowns-data-required )
D. The examples imply that dropdown methods are supposed to be invoked on the data-toggle="dropdown" element, not the class="dropdown-menu" element, but apparently there are exceptions to that.
Revised example: http://jsfiddle.net/cvrebert/wnjmb1La/
Action items:

[ ] (Re: C): Further clarify in http://getbootstrap.com/javascript/#callout-dropdowns-data-required that a trigger element is always required, even for programmatic triggering
[ ] (Re: D): Determine which elements of the dropdown the dropdown methods are supposed to work on, and document this more explicitly

B. You're missing a  around the

It doesn't seem to be required, its just to make sure its using a relative position as far as I understood.
Here's the example without it.

C. You're missing an element with data-toggle="dropdown" (Not explicitly documented, but followed by all the examples and related to the warning in http://getbootstrap.com/javascript/#callout-dropdowns-data-required )

That is what it seems to be the trick! Adding an invisible element with the data-toggle attribute.
Thanks for it!

Bootstrap 3 is no longer being officially developed or supported.
All work has moved onto our next major release, v4. As such, this issue or pull request is being closed as a "won't fix." For additional help and support, we recommend utilizing our community resources. Thanks for your understanding, and see you on the other side of v4!
<3,
@mdo and team


add temperature and response_format for assistant api

please add temperature and response_format for assistant api

would be great to have that :D!


Clearcanvas(CC) Image Server Usage as Data Source

Hello,
How do i need to configure clearcanvas image server in config/default.js file ? My CC server listens to port 1000 for wado requests.

Ohif v2x support dicomweb only, doesn't support DIMSE standard that CC has unless you use ohif v1.x
You can use https://github.com/knopkem/dicomweb-proxy as broker proxy to connect to.
ohif <=> proxy <=> CC


Update cheerio

There are currently issues in later cheerio versions, see the following open issues:

https://github.com/cheeriojs/cheerio/issues/2643
https://github.com/cheeriojs/cheerio/issues/2648


new protobuf based monitoring api function added

Pull request type
Please check the type of change your PR introduces:

[X] Feature

What is the current behavior?
Current Getmonitoring function serializes the internal protobuf monitoring message object into a std::string. This leads to bad performance for scenarios with a huge amount of entities (pub/sub > 10k).
Issue Number: N/A
What is the new behavior?
New API function introduced to get a full monitoring snapshot as google protobuf message object.
namespace eCAL
{
  namespace Monitoring
  {
    namespace Entity
    {
      static const unsigned int Publisher  = 0x001;
      static const unsigned int Subscriber = 0x002;
      static const unsigned int Server     = 0x004;
      static const unsigned int Client     = 0x008;
      static const unsigned int Process    = 0x010;
      static const unsigned int Host       = 0x020;

      static const unsigned int All = Publisher
        | Subscriber
        | Server
        | Client
        | Process
        | Host;

      static const unsigned int None = 0x000;
    }
  }
}

/**
 * @brief Get monitoring as protobuf message.
 *
 * @param [out] mon_       Protobuf message to store the monitoring information.
 * @param       entities_  Entities definition.
 *
 * @return Zero if succeeded.
**/
ECAL_API int GetMonitoring(eCAL::pb::Monitoring& mon_, unsigned int entities_ = Entity::All);

API extension rejected from the team.


Scala.js 2.11 supported.

Since scala-js is dropped Scala 2.11 in scala-js 1.0
And method to change the scala-js version to 0.6 when the cross-build version is Scala 2.11 with JSPlatform?

Hello,
This looks like a question on using Scala.js, rather than a bug report. The GitHub Issues in this repo are for bug reports and feature requests only. Please ask questions on StackOverflow or on Discord (channel #scala-js), where more than just the core developers can see and answer.
Thank you for your understanding.

Regardless, if you need Scala 2.11, stay on Scala.js 1.12.0. This is the last version that supported Scala 2.11. We expect that if you can afford not to upgrade past Scala 2.11, you can also afford not to upgrade past Scala.js 1.12.0.

Regardless, if you need Scala 2.11, stay on Scala.js 1.12.0. This is the last version that supported Scala 2.11. We expect that if you can afford not to upgrade past Scala 2.11, you can also afford not to upgrade past Scala.js 1.12.0.

Thanks, that I know what I need to do with this problem.


Background Work with WorkManager

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-compose-workmanager?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-7-pathway-1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-workmanager#8
Specify the language of the codelab if it is not English:
In which task and step of the codelab can this issue be found?
3
Describe the problem
blur isn't applied

Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version:
API version of the emulator:
Additional information
Include screenshots if they would be useful in clarifying the problem.

nevermind, it is applied though the value of 1 is so low that it's hard to distinguish the blurred picture from the original


Use trait collection to resolve border colors

Summary
https://github.com/facebook/react-native/commit/c974cbff04a8d90ac0f856dbada3fc5a75c75b49 changed the border colors to be of UIColor instead of CGColor. This allowed working with dark mode to switch the border colors automatically. However, in certain situation the system can't resolve the current trait collection (see https://stackoverflow.com/a/57177411/2525941). This commit resolves the colors with the current trait collection to ensure the right colors are selected. This matches with the behavior of how the background color is resolved (also in displayLayer:).
Changelog
[iOS] [Fixed] - Resolve border platform color based on current trait collection
Test Plan
Same test plan as https://github.com/facebook/react-native/pull/29728

Hi @cortinico thanks for the review. I rebased it and amended the lines you mentioned. It looks like there were some whitespaces that the linter didn't agree with.

@cortinico Thank you for taking care of my outstanding PRs. I really do appreciate it.

@cortinico Thank you for taking care of my outstanding PRs. I really do appreciate it.

Sorry those fell through the cracks 👍 Glad we got to merge them though!


MM-31185 Added localization to date picker used when searching for posts around a given date

Summary
Enabled localization of react-day-picker in  /components/suggestion/search_date_suggestion with momentjs packages.
Ticket Link
https://github.com/mattermost/mattermost-server/issues/16520

Hello @shuang2411,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


error when running make

So I've set up my environment, I'm using Atom to do the exercises but I'm stuck on the first one. (C++)
I've installed cmake and boost, using Homebrew on Mac. I created a 'build' folder inside the hello-world folder and I ran cmake .. inside it, which generated the required files.
Now I'm new to TDD, but from what I can see all I have to do to run the tests is run make in the terminal? When I do so, it spits out a huge error message, which I'm attaching here.
I'm not sure if I'm just being stupid or something really is wrong, so please help me. It seems to be something about missing libraries.
error.txt

This looked like it was some error building boost. We've removed our dependency on Boost, see #233. See the new docs for new directions.