RegulatoryType

Hi,
Kindly update the regulatoryType  with these new properties; Manufacturer, Documents, ProductSafety and .ResponsiblePersons.
Thank you very much.

Have you solved this problem? How did you do it? Can you help me answer it?

No I have not. I am still waiting for responses. I hope  I will get response  before  13th December so that I have enough time to implement it in my application.

I learned from other sources that eBay's SDK project team is no longer maintaining the project. I don't know if this news is accurate. I hope an official person can reply. There is a knowledge base that says update SDK, I followed the operation failed, hope this link to help you.
https://developer.ebay.com/support/kb-article?KBid=1034

Thank you very much for your response. It has helped me to resolve it
https://stackoverflow.com/questions/1302525/how-to-use-a-wsdl
The link above shows how to reference wsdl in a  .net project
http://developer.ebay.com/webservices/1371/eBaySvc.wsdl
use the above uri and you will be able to access all the types

my email is<EMAIL_ADDRESS>

Hello together, was someone able to successfully update to the current latest wsdl (1375)?

Hi,
It is almost the end of October. If they don't respond, consider
refactoring your code and applying the steps in the link below. I am
working on this as a backup
https://stackoverflow.com/questions/48023631/querying-ebay-api-with-wcf
Kind regards
Olayinka
On Mon, 30 Sept 2024 at 11:38, Nesh @.***> wrote:

Hello together, was someone able to successfully update to the current
latest wsdl (1375)?
—
Reply to this email directly, view it on GitHub
https://github.com/eBay/trading-api-dotnet-sdk/issues/5#issuecomment-2382766066,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKAQMD5H3QJ72CN5X4POTD3ZZES3RAVCNFSM6AAAAABLMYPGFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBSG43DMMBWGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

have a look at the second answer: Step 1 to Step 4
On Tue, 22 Oct 2024 at 16:29, Olayinka Popoola @.***>
wrote:

Hi,
It is almost the end of October. If they don't respond, consider
refactoring your code and applying the steps in the link below. I am
working on this as a backup
https://stackoverflow.com/questions/48023631/querying-ebay-api-with-wcf
Kind regards
Olayinka
On Mon, 30 Sept 2024 at 11:38, Nesh @.***> wrote:

Hello together, was someone able to successfully update to the current
latest wsdl (1375)?
—
Reply to this email directly, view it on GitHub
https://github.com/eBay/trading-api-dotnet-sdk/issues/5#issuecomment-2382766066,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKAQMD5H3QJ72CN5X4POTD3ZZES3RAVCNFSM6AAAAABLMYPGFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBSG43DMMBWGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

I updated WebService.cs according to the method of the document, some warnings occurred after overwriting, most of them are because the interface properties are outdated, so I deleted some properties and methods until the warning is eliminated, finally generated a dll, I tested AddFixedPriceItem this method, can work properly, there are Regulatory properties, other functional interfaces have not been tested, do not know whether it can be used normally, if there is a need for this dll, you can leave the mailbox, I will send it over

@hanba
Hello, i really would like to have your DLL.
You asked to leave you a mail, but I didn't manage to find how I can leave you a private message here on GitHub.
Hope this post will help.

I'm working on this. Keeping you posted.

I created a PR https://github.com/eBay/trading-api-dotnet-sdk/pull/8 after I updated the library to v1379 of the API. The source branch is this https://github.com/marconline/trading-api-dotnet-sdk/tree/v4.7.2

If you want to do by yourself, follow these steps:

fork their repo
clone your repo locally
open solution CodeGen.sln inside Tools\CodeGen and compile them
after compilation, open a cmd with admin privileges
enter inside Tools\CodeGen\bin folder
run CodeGen.exe. Don't mind about command line parmeters, since they are ignored due to a bug in the code (opened a PR #9 )
a WebService.cs file will be generated inside the folder Users\lrishi\Documents\TradingAPISDK-.NET\Source\eBay.Service.SDK\Core\Soap
copy that WebService.cs file and overwrite the same one inside Source\eBay.Service.SDK\Core\Soap
after that, removed files related to deprecated calls and remove references to deprecated fields

Hi, It is almost the end of October. If they don't respond, consider refactoring your code and applying the steps in the link below. I am working on this as a backup https://stackoverflow.com/questions/48023631/querying-ebay-api-with-wcf Kind regards Olayinka
…
On Mon, 30 Sept 2024 at 11:38, Nesh @.> wrote: Hello together, was someone able to successfully update to the current latest wsdl (1375)? — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKAQMD5H3QJ72CN5X4POTD3ZZES3RAVCNFSM6AAAAABLMYPGFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBSG43DMMBWGY . You are receiving this because you authored the thread.Message ID: @.>

Thank you for this link, and to the author for this tip.
For years, I’ve been dealing with the stress of waiting for the SDK to be updated. It gets particularly stressful when there are changes in the eBay API that need to be quickly implemented in my software.
The same applies to the December 13th deadline for the introduction of GPSR.
I followed the steps and now have my own 'SDK' – it’s not that complicated if you only need it for your own purposes. I use only 11 methods and was able to integrate it into my production software in less than 10 hours.
During my implementation, there was even another eBay API update, which I was able to apply within seconds.
Of course, I am grateful to the developers of the SDK, which I have been using for over 10 years.
Thanks to the tip here, I am no longer dependent on it and would recommend everyone to do the same.

Hello @Neshik  . Did you follow my steps?
If yes, I'm happy that I've been useful and that you were able to do that!
If you like, join my WhatsApp group for e-commerce developers: https://chat.whatsapp.com/Gb9Yy7VxVugAUwj4MLptoa

eBay Service SDK v1.0.1 is now available.

Thanks, I'll check it out.
On Wed, 13 Nov 2024, 17:01 Lokesh Rishi, @.***> wrote:

eBay Service SDK v1.0.1
https://www.nuget.org/packages/eBay.Service.SDK/1.0.1 is now available.
—
Reply to this email directly, view it on GitHub
https://github.com/eBay/trading-api-dotnet-sdk/issues/5#issuecomment-2474215560,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKAQMD6MCA555UDXYXHHBWT2AOAVPAVCNFSM6AAAAABLMYPGFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZUGIYTKNJWGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


LogisticGAM not converging

I am trying to run LogisticGAM with n_splines =10. The data sets has 13 variables, however I have been constantly getting convergence issue with LogisticGam. Following is what the message looks like
N/A% (0 of 11) |                         | Elapsed Time: 0:00:00 ETA:  --:--:--/usr/local/lib/python3.6/dist-packages/pygam/links.py:149: RuntimeWarning: divide by zero encountered in true_divide
  return dist.levels/(mu*(dist.levels - mu))
/usr/local/lib/python3.6/dist-packages/pygam/pygam.py:592: RuntimeWarning: invalid value encountered in multiply
  self.distribution.V(mu=mu) *
/usr/local/lib/python3.6/dist-packages/pygam/pygam.py:614: RuntimeWarning: invalid value encountered in greater_equal
  mask = (np.abs(weights) >= np.sqrt(EPS)) * np.isfinite(weights)
  9% (1 of 11) |##                       | Elapsed Time: 0:00:00 ETA:   0:00:02/usr/local/lib/python3.6/dist-packages/pygam/links.py:149: RuntimeWarning: divide by zero encountered in true_divide
  return dist.levels/(mu*(dist.levels - mu))
/usr/local/lib/python3.6/dist-packages/pygam/pygam.py:592: RuntimeWarning: invalid value encountered in multiply
  self.distribution.V(mu=mu) *
/usr/local/lib/python3.6/dist-packages/pygam/pygam.py:614: RuntimeWarning: invalid value encountered in greater_equal
  mask = (np.abs(weights) >= np.sqrt(EPS)) * np.isfinite(weights)
100% (11 of 11) |########################| Elapsed Time: 0:00:01 Time:  0:00:01

Link to the data set that I am trying to run is as follows:
https://drive.google.com/file/d/11XfIHSB9boFZmYHaotJdsT6Gmsth9eTr/view?usp=sharing
https://drive.google.com/file/d/1HTK8AjLN0ahFnLNPwjGc2x0UzOpvS1B7/view?usp=sharing
Link to my google colab notebook is
https://colab.research.google.com/drive/1JM9YPMd3XQQBzcx6Raq4eoIpppUtEQG9

There is a parameter called max_iter which is set to 100 by default. If you increase it, then the convergence should be achieved. Also, your n_spline values are too high in some cases, and therefore, the reliability of the model will be low; so consider changing that.


Separate file for finding plugins .so

In GitLab by @ksiero on Sep 23, 2020, 09:39
Finding shared objects of plugins should be moved from global_context to separate file.

mentioned in commit 25548c8ec4344913c41c41f6f640ca0da8d951e2

mentioned in commit f05d4abc5ff0e3831ab66bbcbda3d568437e3535

mentioned in commit 5f30d0455e79cd2884432cac2ceee73090b41739

mentioned in commit 9db61fc4d7c577e3e8e943500cac742d92fa1b51

mentioned in commit dd5d3365464a659e873f2a39f52ae88dda5512bf

mentioned in commit 9546b171a12c97794c972d67f6c7d5d629f5edae

mentioned in commit b6f70a83ca23630d86b05a597367235077493f97

mentioned in commit f6b62111092ce4e24657257a996da5485d32e822

mentioned in commit 27d7cd416e6e780478549aca8ec68891fc1930bc

mentioned in commit 82e40214d7d440f048c3ffec29733da107040fd0

mentioned in commit ec067905af27f3940f324ce1c17240f5238d89e4

mentioned in commit 0b209a0b528d9529fe18629c0b868f597f93f883

mentioned in commit 2ee583aa442588708698f06967bf0f079af99d20


Make nginx IP configurable

Make it possible for nginx to not listen on all interfaces.
@chhhavi @mdelillo

Hey @mdelillo, could you say more about the need for this? Is this security related?

Hi @zvance, we are using this to have nginx listen on localhost. The use case is to have multiple services running co-located on a single VM (for example, on PCF Dev), but only having them accessible through the public routes for security.

Thanks @mdelillo. We've scheduled this for a later date.

@mdelillo thanks for the PR, apologies for the absurdly long time it took for this to be merged.


Piercetrey/ch 110674/proto cleanup

removed unused protos
consolidated duplicated protos to shared proto project
removed grpc dependency/generation from contract-proto and encryption projects since there are no grpc services in their protos
Updated proto-java dependency to 3.12.0 (since this version was getting pulled in somehow after I restructured things and both versions were ending up on the classpath causing issues)

Codecov Report

Merging #28 (dcb7e6e) into main (3f57b0a) will not change coverage.
The diff coverage is 62.50%.

@@            Coverage Diff            @@
##               main      #28   +/-   ##
=========================================
  Coverage     46.62%   46.62%
  Complexity       55       55
=========================================
  Files            14       14
  Lines           845      845
  Branches         92       92
=========================================
  Hits            394      394
  Misses          404      404
  Partials         47       47

Impacted Files
Coverage Δ

...venance/scope/sdk/extensions/EnvelopeExtensions.kt
0.00% <0.00%> (ø)

...n/kotlin/io/provenance/scope/sdk/SessionBuilder.kt
67.22% <63.63%> (ø)

.../src/main/kotlin/io/provenance/scope/sdk/Client.kt
27.41% <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 3f57b0a...dcb7e6e. Read the comment docs.


gulp stuck

After git clone and npm install, if I run gulp, it gets stuck at Finished 'compile:example' after 11 s. I've waited for about half an hour.
gulp validate passed successfully.
gulp backend:watch exits after Finished 'compile:example' after 10 s without creating the server.
Tried again in a new directory and now it's been stuck at [18:32:33] Finished 'bower' after 11 s for 3+ minutes.

gulp is not supposed to terminate. It starts the watch mode.
gulp backend:watch requires go app engine tooling to be installed and in the path.
Both work for me with a fresh clone.

I know, I've used the project before. Go is installed.
This time gulp never displayed the "listening" message. This is on a corp Goobuntu.

Is it possible that something blocks the ports? Does gulp serve work? Seems weird that all tasks creating a server fail.

gulp build works and gulp serve does serve at http://localhost:8000. I've verified that goapp is in $PATH.
Looking carefully at the log for gulp build alone, I see this:

[20:00:47] Finished 'copy:static' after 1.2 s
[20:00:54] [TypeError: Buffer.alloc is not a function]

Which node version are you using? Is it possiblity related to this?
http://stackoverflow.com/questions/36499840/typeerror-buffer-alloc-is-not-a-function
On Sat, Nov 5, 2016 at 3:20 AM Dan Dascalescu<EMAIL_ADDRESS>wrote:

gulp build works and gulp serve does serve at http://localhost:8000. I've
verified that goapp is in $PATH.
Looking carefully at the log for gulp build alone, I see this:
[20:00:47] Finished 'copy:static' after 1.2 s
[20:00:54] [TypeError: Buffer.alloc is not a function]
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ampproject/amp-by-example/issues/465#issuecomment-258587809,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXOOFFEmdXmXEUwvmnJKQ0GiMy_awpoks5q6_XngaJpZM4KpGgi
.

@dandv Did you resolve the issue? I seem to have the same problem, running gulp seems to get stuck. I haven't used gulp before so I figured after a few minutes that it was done. I was waiting for a message like "done, you can now go to localhost:8000" like I'm used to. Going to localhost:8000 gave me a bunch of errors, missing images and missing custom styling, but I assume that is related.

Which Node version are you using?
On Mon, 28 Nov 2016 at 07:32, Peter van der Meer<EMAIL_ADDRESS>wrote:

@dandv https://github.com/dandv Did you resolve the issue? I seem to
have the same problem, running gulp seems to get stuck. I haven't used
gulp before so I figured after a few minutes that it was done. I was
waiting for a message like "done, you can now go to localhost:8000" like
I'm used to. Going to localhost:8000 gave me a bunch of errors, missing
images and missing custom styling, but I assume that is related.
[image: image]
https://cloud.githubusercontent.com/assets/561293/20659635/0305cd60-b545-11e6-8dd0-b803790fbe25.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ampproject/amp-by-example/issues/465#issuecomment-263201648,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXOONykPL-BVhs2_RXotzqb7tITuEiaks5rCoOYgaJpZM4KpGgi
.

Running Windows 10, Node is at v6.9.1 and NPM is at v4.0.2 .

Still experiencing the issue.
I'm running v5.5.0. It is possible that node was upgraded on my box within the past month, and if it helps, I can check internally if that was the case.

Might the issue be caused by a dependency, rather than the node version?
 Can you verify whether the 'watch' or 'serve' task causes the problem?

It's gulp watch:
➜  amp-by-example git:(master) ✗ node_modules/.bin/gulp watch
[01:16:44] Using gulpfile ~/prg/amp-by-example/gulpfile.js
[01:16:44] Starting 'watch'...
[01:16:45] Finished 'watch' after 315 ms

(a minute later, nothing at http://localhost:8000 or 8080)

BTW, gulp is at v3.9.1. I disprefer gulp, so I've been using the locally installed copy in node_modules/.bin/gulp. Maybe you were using an older version?

gulp watch won't start the webserver. Instead do something like:
`touch src/test.html'
to see whether it's stuck.

Couldn't reproduce it on a linux box either:

node 7.0.0
gulp 3.9.1

Also works for me on Linux with node 6.9.1, node 7.2.0 and gulp 3.9.1. (Fresh checkout, npm install gulp ; npm install ; node_modules/.bin/gulp.)

I do have a missing dependency error for Python on npm install, but after the errors it says it's just optional. Maybe that helps..

OK, I've figured it out. Kind of embarrassing actually.
While gulp does appear to get suck, e.g. after "Finished 'compile:example' after 12 s", what actually happens is that gulp parallelizes the default tasks (it has to, since gulp watch doesn't complete) and gulp serve, even though listed last, doesn't execute last. gulp build takes longer and finishes executing last. Its console output appears last. For some reason, this hasn't happened before I filed this bug. (More puzzling is that I didn't just go to http://localhost:8000 to see whether the server was actually listening.)
Anyway, if you look in the log, you can see that folder "dist" serving at http://localhost:8000 was somewhere in there. What I expected was for that line to be last in the console output.
PS: @ithinkihaveacat, I think you don't need the npm install gulp step because it's a devDependency.

@dandv Yeah that's what I did 5 days ago too. I noticed the same thing, but I'm getting a bunch of errors. But seeing as you've closed this issue I don't think your project looks the same as my screenshot, does it?

@peterplus1: I also see the missing favicon errors, but, one thing at a time - #508.


Move y-partykit deps to peerDependencies

Marks yjs and react as peerDependencies.
The react hook (and dependency) would ideally be in a separate package, but I've made it optional here.

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

This seems reasonable. I can't remember why I'd put it directly in deps, probably a mistake. I'll test this next week and land it. Thank you!

I don't think this should be a breaking change, but let's ship it and see what happens.


[1.3] Add Bwc Test for OS 1.1 (#417)

Signed-off-by: Shenoy Pratik<EMAIL_ADDRESS>Description
backport  #417
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

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

Codecov Report

Merging #423 (5e82fb5) into 1.3 (64bb6b9) will increase coverage by 4.42%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                1.3     #423      +/-   ##
============================================
+ Coverage     72.95%   77.38%   +4.42%
============================================
  Files            94       30      -64
  Lines          3946     1888    -2058
  Branches        611      377     -234
============================================
- Hits           2879     1461    -1418
+ Misses          892      424     -468
+ Partials        175        3     -172

Flag
Coverage Δ

dashboards-reports
77.38% <ø> (ø)

reports-scheduler
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...tsscheduler/model/GetAllReportInstancesResponse.kt

...heduler/action/UpdateReportInstanceStatusAction.kt

...eduler/model/UpdateReportInstanceStatusResponse.kt

...in/org/opensearch/reportsscheduler/util/Helpers.kt

...rtsscheduler/action/GetAllReportInstancesAction.kt

...g/opensearch/reportsscheduler/metrics/Metrics.java

...ortsscheduler/model/GetReportDefinitionResponse.kt

...tsscheduler/model/UpdateReportDefinitionRequest.kt

...tsscheduler/model/DeleteReportDefinitionRequest.kt

...search/reportsscheduler/model/ReportInstanceDoc.kt

... and 54 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[APIM 3.2.0] Avoid extra configurations outside of the deployment.toml for Throttling

Describe your problem(s)
It was identified that currently throttling configurations in an active-active deployment of WSO2 API Manager have configurations outside of the primary configuration file <AM_HOME>/repository/conf/deployment.toml.
This tarnishes the usability since, users' familiarity with the primary configuration file and will be cumbersome when it comes to introducing these configuration changes in an installation platform.
Describe your solution
This is an improvement request to provide support for these additional configurations within the primary configuration file and avoid the need to perform extra configuring steps outside of this configuration file.
Suggested Labels:
Type/Improvement
Suggested Assignees:
@tharindu1st @pubudu538

This can be achieved by configuring following configuration
[apim.throttling]
event_duplicate_url = ["tcp:traffic-manager-2:5672"]
@Mariangela @shaniR  please replace the above mentioned step by defining this config


Re-apply Ruby 3.3 PR and simplify chat javascript test

Trello card
Simplify webchat JS test
Context
Changes proposed in this pull request
Guidance to review

Closing as superseded by https://github.com/DFE-Digital/get-into-teaching-app/pull/4397


Bug: Error "Request failed with status code 400" after second change of temperature after restart

Describe The Bug
After restarting homebridge the first temperature setting works fine, but the next wil fail with error 400.
To Reproduce
restart homebridge, then set temperature in homekit, then set again temperature in homekit. Then temperature wil not change and error 400 appears in the logfile.
Expected behavior
when set the temperature the temperature should be set.
 Error Message: "Request failed with status code 400"
[12/16/2021, 4:08:53 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home Error: {"message":"Request failed with status code 400","name":"Error","stack":"Error: Request failed with status code 400\n    at createError (/homebridge/node_modules/homebridge-honeywell-home/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/homebridge/node_modules/homebridge-honeywell-home/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/homebridge/node_modules/homebridge-honeywell-home/node_modules/axios/lib/adapters/http.js:293:11)\n    at IncomingMessage.emit (node:events:402:35)\n    at endReadableNT (node:internal/streams/readable:1343:12)\n    at processTicksAndRejections (node:internal/process/task_queues:83:21)","config":{"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false},"transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1,"headers":{"Accept":"application/json, text/plain, */*","Content-Type":"application/json","Authorization":"Bearer D6cQ2CEqYfeB9c4OhFxSnAugvumt","User-Agent":"axios/0.24.0","Content-Length":51},"responseType":"json","params":{"locationId":1541748,"apikey":"GP9pZ6QASplBLva4NNMpfTb44yKotqHs"},"method":"post","url":"https://api.honeywell.com/v2/devices/thermostats/LCC-B82CA0340349","data":"{\"mode\":\"Heat\",\"heatSetpoint\":22,\"coolSetpoint\":10}"},"status":400}
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home device: {"displayedOutdoorHumidity":100,"vacationHold":{"enabled":false},"currentSchedulePeriod":{"day":"Thursday","period":"P1"},"scheduleCapabilities":{"availableScheduleTypes":["None","Geofenced","TimedEmea"],"schedulableFan":false},"scheduleType":{"scheduleType":"Timed","scheduleSubType":"EMEA"},"changeSource":{"by":"partner","name":"Homebridge rpi"},"scheduleStatus":"Resume","allowedTimeIncrements":10,"settings":{"hardwareSettings":{"brightness":3,"maxBrightness":5},"temperatureMode":{"air":true},"specialMode":{},"devicePairingEnabled":true},"deviceOsVersion":"T6H600WF1003","deviceClass":"Thermostat","deviceType":"Thermostat","deviceID":"LCC-B82CA0340349","deviceInternalID":3748634,"userDefinedDeviceName":"Honeywell Home","name":"Honeywell Home","isAlive":true,"isUpgrading":false,"isProvisioned":true,"macID":"B82CA0340349","deviceSettings":{},"service":{"mode":"Up"},"deviceRegistrationDate":"2021-12-07T07:43:27.9533333","dataSyncStatus":"Completed","units":"Celsius","indoorTemperature":20,"outdoorTemperature":8,"allowedModes":["Heat","Off"],"deadband":0,"hasDualSetpointStatus":false,"minHeatSetpoint":5,"maxHeatSetpoint":35,"minCoolSetpoint":-18,"maxCoolSetpoint":-18,"changeableValues":{"mode":"Heat","heatSetpoint":21,"coolSetpoint":10,"thermostatSetpointStatus":"HoldUntil","holdUntil":"16:30:00","nextPeriodTime":"16:30:00","endHeatSetpoint":20,"endCoolSetpoint":10,"heatCoolMode":"Heat"},"operationStatus":{"mode":"EquipmentOff","fanRequest":false,"circulationFanRequest":false},"deviceModel":"T5-T6"}
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home Fetched update for Honeywell Home
       from Honeywell API: {"mode":"Heat","heatSetpoint":21,"coolSetpoint":10,"thermostatSetpointStatus":"HoldUntil","holdUntil":"16:30:00","nextPeriodTime":"16:30:00","endHeatSetpoint":20,"endCoolSetpoint":10,"heatCoolMode":"Heat"}
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus TemperatureDisplayUnits: 0
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus CurrentTemperature: 20
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus HeatingThresholdTemperature: 21
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus CoolingThresholdTemperature: 10
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus TargetHeatingCoolingState: 1
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus Currently Mode (OFF): EquipmentOff(0)
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus TargetTemperature (HEAT): 21)
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic TemperatureDisplayUnits: 0
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic CurrentTemperature: 20
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home CurrentRelativeHumidity: undefined
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic TargetTemperature: 21
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic HeatingThresholdTemperature: 21
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic CoolingThresholdTemperature: 10
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic TargetHeatingCoolingState: 1
[12/16/2021, 4:09:00 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic CurrentHeatingCoolingState: 1
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home device: {"displayedOutdoorHumidity":100,"vacationHold":{"enabled":false},"currentSchedulePeriod":{"day":"Thursday","period":"P1"},"scheduleCapabilities":{"availableScheduleTypes":["None","Geofenced","TimedEmea"],"schedulableFan":false},"scheduleType":{"scheduleType":"Timed","scheduleSubType":"EMEA"},"changeSource":{"by":"partner","name":"Homebridge rpi"},"scheduleStatus":"Resume","allowedTimeIncrements":10,"settings":{"hardwareSettings":{"brightness":3,"maxBrightness":5},"temperatureMode":{"air":true},"specialMode":{},"devicePairingEnabled":true},"deviceOsVersion":"T6H600WF1003","deviceClass":"Thermostat","deviceType":"Thermostat","deviceID":"LCC-B82CA0340349","deviceInternalID":3748634,"userDefinedDeviceName":"Honeywell Home","name":"Honeywell Home","isAlive":true,"isUpgrading":false,"isProvisioned":true,"macID":"B82CA0340349","deviceSettings":{},"service":{"mode":"Up"},"deviceRegistrationDate":"2021-12-07T07:43:27.9533333","dataSyncStatus":"Completed","units":"Celsius","indoorTemperature":20,"outdoorTemperature":8,"allowedModes":["Heat","Off"],"deadband":0,"hasDualSetpointStatus":false,"minHeatSetpoint":5,"maxHeatSetpoint":35,"minCoolSetpoint":-18,"maxCoolSetpoint":-18,"changeableValues":{"mode":"Heat","heatSetpoint":21,"coolSetpoint":10,"thermostatSetpointStatus":"HoldUntil","holdUntil":"16:30:00","nextPeriodTime":"16:30:00","endHeatSetpoint":20,"endCoolSetpoint":10,"heatCoolMode":"Heat"},"operationStatus":{"mode":"EquipmentOff","fanRequest":false,"circulationFanRequest":false},"deviceModel":"T5-T6"}
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home Fetched update for Honeywell Home
       from Honeywell API: {"mode":"Heat","heatSetpoint":21,"coolSetpoint":10,"thermostatSetpointStatus":"HoldUntil","holdUntil":"16:30:00","nextPeriodTime":"16:30:00","endHeatSetpoint":20,"endCoolSetpoint":10,"heatCoolMode":"Heat"}
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus TemperatureDisplayUnits: 0
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus CurrentTemperature: 20
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus HeatingThresholdTemperature: 21
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus CoolingThresholdTemperature: 10
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus TargetHeatingCoolingState: 1
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus Currently Mode (OFF): EquipmentOff(0)
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home parseStatus TargetTemperature (HEAT): 21)
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic TemperatureDisplayUnits: 0
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic CurrentTemperature: 20
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home CurrentRelativeHumidity: undefined
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic TargetTemperature: 21
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic HeatingThresholdTemperature: 21
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic CoolingThresholdTemperature: 10
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic TargetHeatingCoolingState: 1
[12/16/2021, 4:09:09 PM] [HoneywellHome] [DEBUG] Thermostat: Honeywell Home updateCharacteristic CurrentHeatingCoolingState: 1

### Config for homebridge-honeywell-home

```shell
"name": "HoneywellHome",
            "credentials": {
                "consumerKey": "xxxxxxxxxxx",
                "consumerSecret": "xxxxxxxxxxx",
                "accessToken": "xxxxxxxxxx",
                "refreshToken": "xxxxxxxxxx"
            },
            "options": {
                "devices": [
                    {
                        "deviceID": "LCC-B82CA0340349",
                        "deviceClass": "Thermostat",
                        "thermostat": {
                            "thermostatSetpointStatus": "TemporaryHold"
                        }
                    }
                ]
            },
            "platform": "HoneywellHome"

Screenshots
No response
Device & Model
Honeywell Lyric T6
Node.js Version
16.13.1
NPM Version
8.1.2
Homebridge Version
1.3.8
Homebridge Honeywell Home Plugin Version
11.1.2
Homebridge Config UI X Plugin Version
<IP_ADDRESS>
Operating System
Raspbian

Can you try setting your thermostatSetpointStatus to permanentHold and see if it still gives you these errors?

When set to permanenthold error 400 is also there, but not after the second but after the third time to set de temperature.

@martennienhuis, can you try the latest beta:

Click here to find out how to install Beta

Thanks for your quick response…..
When i set it to permanenthold everything seems to be fine.
But when I set it to temporaryhold and i do several changes of the temperature, after the third setting the logging shows permanent hold.   This is reported in the log as wel in the honeywell home app.

Yes, and to be sure, i changed the setting to permanenthold, then restart hombridge, then change the setting back to temporaryhold and restart homebridge again an the logfile still shows permanenthold.

@martennienhuis I tested this myself with it being on NoHold and had no issues, so not sure what else there is I can do.

I removed the plugin and installed again. Still permanent hold when temporary hold is selected, also when the setting is nohold.

I checked version 11.0.4, and this version works without problems. So the API seems to be oke.

This has fixed the issue for me also, thank you so much for your efforts.

@riskitforabiscuit1252 What fixed the issue?

I checked version 11.0.4, and this version works without problems. So the API seems to be oke.

I will have to look at the difference from then to now...

@riskitforabiscuit1252 What fixed the issue?

Sorry I was getting confused, I assumed @martennienhuis was talking about the newest update (11.2.0) when he said it was working without problems. My bad.
I was originally having the same issue as @martennienhuis when setting temporary hold with the temperature set only working the first time. I just updated to 11.2.0 and it seems to have completely resolved any issues I had with this for me. (Using a T5/T6)

@martennienhuis, I looked over 11.0.4 and I am not see anything on why this shouldn't work in v11.2.0.
I would remove what you have in your config and reset backup with the UI.

I think i found something. I checked the config file and compared this with the settings screen and i found there was a space before the devicename. After removing this space in the config setting screen i restarted homebridge and now the temporaryhold is working. I think something went wrong with the copy-past from the device tab to the setting tab.
Maybe it is a good improvement to be able to select the device in the settings tab?

I did some additional testing and i think this solved the problem. Version 11.2.0 seems te be fine. Thanks a lot for your help.

@martennienhuis, good to know. If someone smart then me is able to figure out how to handle that in the Custom UI, I would be willing to take a Pull Request for that, but I don't have enough coding knowledge to do that.
I have added the nextPeriodTime as a config setting, that shows up in the config UI now so you can set how many hours you want to have this temporary hold set. This will always be 4 hours by default when sending temporary hold or will look at your config hour amounts.
if you would like to test this?

I tested the beta and it seems to work as you described. I see in the logfile the timestamp when the temporaryhold will end. I wil do some additional testing today and wait when this period is passed.
but…. I do not fully onderstand the usecase for this feature.

The nextperiodtime Is not working. I waited till the period is over and the thermostat is not changing back. Also the honeywell home app is not showing this schedulepoint.
I do not understand the usecase of this new setting.
In my situation My thermostat has a daily schedule for managing the temperature in my house. If i want to make it a little warmer i do this via homekit, but i want to be sure the next scheduled period my thermostat is taking back. So, my thermostat schedule is leading and i can make manual exceptions via homekit with temporaryhold setting. This works excelent in the previous version (11.2.0) of the plugin.
Can you please keep the temporaryhold feature as it was? Maybe you can introduce a new userdefinedhold instead?
i went back to version 11.2.0.

@martennienhuis Test again without inputting anything into nextperiod time. I am pretty sure I made it so that it wouldn't send next period time if nothing was in there.

I tested again without inputting anything into nextperiod time.
After changing the temperature setting in homekit, my thermostat is showing this on the display and in my honewell home app the temperature change is vissible, but the app is indicating that this setting is till my next scheduled time, in my case 9:30pm. So this is what i need, but I understand the default nextperiodtime is 4 hours, and in the logfile is the nextperiodtime 5:16pm logged.
Maybe i misunderstand the feature. What is the expected behaviour of the nextperiodtime? See also my usecase “In my situation…..” above.

Well depending on peoples schedules. It should hold the temp for the next 4 hours, then revert to schedule. If schedule is in 3 hours it will go to the schedule. This will work good for users that have more wide open schedules, that only change the temp once a day.

Oke, I tested again without inputting anything into nextperiod time.
This is working as i expected, and as temporaryhold always worked.
next to this i did 2 tests:
test 1;
Test started at 1pm
Add an aditional schedule time in my honeywel; 3pm. (Is first next)
then i added nextperiodtime is 4
result 1;
My honeywell home app shows “keep until 3 pm”
Logfile shows nextperiodtime = 5pm
test 2;
I removed the schedule at 3pm and my next schedule is 9:30pm
Start te test at 1:30 pm
Result 2;
My honeywell home app shows “keep until 9:30 pm”
Logfile shows nextperiodtime = 5:30 pm

1 addition…. When i removed the nextperiod time i restarted homebridge.
The configfile has no nextperiodtime parameter,
but the logfile shows: nextperiodtime: 4 hours from now.

@martennienhuis  4 is default.
Maybe I will have to remove this, as it seems that the Honeywell api don't care about the time.

Oke. Again, thanks for your help. I’m happy with version 11.2.0.


power_meter device profiles detect too many entities

Devices listed in the library as power_meter will show up with every of their sensor:* entity in the auto detection:

Originally posted by @RubenKelevra in https://github.com/bramstroker/homeassistant-powercalc/issues/2834#issuecomment-2564313385

As discussed.
This is due to the device having 4 "sensor." entities.
Powercalc discovers per entity, and for power meters this is all entities of sensor domain.
Working on a per device discovery now, which is ideal for self usage of IoT devices.
Have working draft ready now.
https://github.com/bramstroker/homeassistant-powercalc/pull/2868
Needs some final polishing.
But we can add "discovery_type": "device" to the model.json.
This will also cause the powercalc profile to only be discovered once per device, as it's not bounded to specific entities.


Make JWT one-time use?

I'm using JWT-simple to help make a confirmation email. That is to say, when a user registers for an account, they are sent an email, where they need to click a button to confirm their email address. On click, a URL with the JWT is sent to my server.
My question is: is there a way to make the JWT one-time use? As in, have it expire after the JWT has been sent to the server once?

Hi, I've also implemented a jwt-based email validation. Here is how I did it:

when the user signs up, they are created in my db with a field state: pending (or anything like that),
then, an email is sent to the user containing an url with a JWT (generated using a key different from the one that generates authentication tokens); this token has a short (minutes or hours) expiration date, and contains the user id and the user email,
when the user clicks on the link, the server checks the email token (the user needs to be authenticated, and the auth token is checked as usual), and the field state in the db is set to verified (or something similar) if the decoding works,
if the state of the user is already verified or the token is invalid, then the controller returns an error.

Regarding the one-time use, JWT are stateless so that's not possible unless you somehow implement a server-side check (like in my example). You can use the jti claim (that is give your token a unique identifier, which might help you do so), but I don't think that it is required in your case.
Regarding expiration, same answer, if you need per-token invalidation, you need to d it server-side. In any case, you should add an exp (date-based expiration) claim to all of your tokens.

Thank you for all that. This is roughly how I was going to set my email verification up, and your explanation cleared up some minor points for me.

Hi,
has your question been fully answered so far ? If so, may I close this issue ?
Thank you.

I'm closing the issue, feel free to re-open it if you need anything else.


eval_expr errors

I'm having two problems with eval_expr. These might be related, but I'm not sure to what degree.
constant rat : Type
constant rof : linear_ordered_field rat
notation `ℚ` := rat

attribute [instance] rof
open tactic

run_command do
 e ← to_expr `([5] : list ℕ),
 eval_expr ℕ e,
 return ()

noncomputable meta def mk_list : tactic (list ℚ) := do
 e ← to_expr `([3, 3] : (list ℚ)),
 eval_expr (list ℚ) e

run_command
 mk_list >> return ()

Issue 1: in the first run_command, Lean reports an error at the backtick following to_expr. I'd expect this to appear at eval_expr instead.
Issue 2: in mk_list, Lean again reports an error at the backtick.
type mismatch at definition '_eval_expr.18.794', has type
  list ℚ
but is expected to have type
  Prop

This is triggered by the following run_command, there's no error with that commented out.
The error location is unstable: when I add a new declaration below, it somtimes moves to run_command.
The error message doesn't make sense, where did Prop come from?
This is only triggered when the type is declared as a constant. There's no issue when rat is replaced with nat.

Note, the list ℚ in the second example is just an artifact, the following produces the same error:
constant rat : Type
constant rof : linear_ordered_field rat
notation `ℚ` := rat
attribute [instance] rof
open tactic

noncomputable meta def mk_list : tactic ℚ := do
 e ← to_expr `(3 : ℚ),
 eval_expr ℚ e

run_command  mk_list >> return ()

I will fix the error message position issue, and the bad error message. That being said, you cannot use eval_expr with rat. How would be able to execute code that uses axioms rat and rof?

Thanks! I don't expect to be able to use eval_expr with rat like this. This example was pared down from a more complicated one, which also (in retrospect) shouldn't work, but the mistake wasn't as obvious and the error messages made it difficult to find what was wrong.

fixed by commits above.


Publish Dockerfile

Describe the feature
It would be helpful if you published the Dockerfile used to build the currently published image, because then potential fixes for issues (like this one) could be tested in a container

Never mind. Found it here:
https://github.com/aler9/rtsp-simple-server/blob/fa5da674655ad051f52b50bd2b01b0e70ff53d5e/Makefile#L219


termios ver 0.2 dependency will need to be updated later

this commit pins termios dependency to 0.2 version, this version has a bug described in this comment.
I think recent versions of termios have some build issues, and it's better to pin Terminal::Lineeditor to 0.2 for now, but just leaving this issue here as a reminder to update termios dependency when the build issue is resolved.

Thank you for opening this!  Yeah, I'm waiting for things to settle down a bit before changing the version pin.  For now hopefully people will be no worse off than they were a week ago.  :-)


📎 Implement noImplicitCoercion - eslint/no-implicit-coercion

Description
Implement no-implicit-coercion.
Want to contribute? Lets you know you are interested! We will assign you to the issue to prevent several people to work on the same issue. Don't worry, we can unassign you later if you are no longer interested in the issue! Read our contributing guide and analyzer contributing guide.

i want to work on this


Some question

Some Question
Hello author, I am very interested in your paper. I have read through the entire paper and am preparing to test gpt-3.5-turbo using your open-source code (by calling the API). However, I encountered some issues during implementation and would like to ask for your advice:

When reading the dataset, I did not seem to find a method to divide the data in code generation into easy/medium/hard categories.
For the time being, I can only perform tests on code generation and Test-output-prediction.
The results I found when testing LLM for code generation are as follows:
{"pass@1": 0.0, "pass@5": 0.0, "detail": {"pass@1": {"7": 0.0, "1": 0.0, "3": 0.0, "4": 0.0, "9": 0.0, "2": 0.0, "8": 0.0, "0": 0.0, "6": 0.0, "5": 0.0}, "pass@5": {"7": 0.0, "1": 0.0, "3": 0.0, "4": 0.0, "9": 0.0, "2": 0.0, "8": 0.0, "0": 0.0, "6": 0.0, "5": 0.0}}}

The changes I made to main.py are as follows:
def main():
    args = get_args()

    if args.scenario == Scenario.codegeneration:
        benchmark = load_code_generation_dataset()
        format_prompt = format_prompt_generation
    elif args.scenario == Scenario.testoutputprediction:
        benchmark = load_test_prediction_dataset()
        format_prompt = format_prompt_test_output
    else:
        raise ValueError(f"Scenario {args.scenario} not implemented")

    runner = GPT3APIRunner()

    results = runner.run_main(benchmark, format_prompt)

    copy_benchmark = benchmark[:10]
    samples = [problem.get_evaluation_sample() for problem in copy_benchmark]
    metrics,result = codegen_metrics(samples,results)

How should I solve this problem? Thank you very much!

Thanks for your interest in our benchmark. I have added easier support for computing more granular now.
On running python -m lcb_runner.runner.main --model {model_name} --scenario codegeneration --evaluate we now generate an _eval_all.json
https://github.com/LiveCodeBench/LiveCodeBench/blob/ad9c886ead9cd259da33bbcfca08171d4ed001ef/lcb_runner/runner/main.py#L78-L90
Once this file is constructed, you can get more detailed metrics using
python -m lcb_runner.evaluation.compute_scores --eval_all_file {saved_eval_all_file}  # --start_date 2023-09-01

Finally, I have added support for the --continue_existing flag to use the existing model generations already to avoid the recomputation cost. Hope this helps!
Please reach out if you have any further questions!


JPEG marker FFD1

Hi, I am using your library for dcoding JPEG files. I ran into a file, which has a FFD1 marker, and it crashes the whole JPEG decoding process. Could you implement the support for this marker? It occurs in the file attached below (and all JPG viewers can open it).

.

There are some implementation details at https://stackoverflow.com/questions/8748671/jpeg-restart-markers. Could you provide a PDF file with such an image so we know that it can exist in a PDF file and how other viewers handle it?

I ran into a file, which has a FFD1 marker, and it crashes the whole JPEG decoding process. Could you implement the support for this marker?

The assumption seem to be that Restart markers are not supported in src/core/jpg.js, but if that actually were the case then we'd not be able to decode most (or any?) JPEG images; please see the existing code (part of the MCU decoding): https://github.com/mozilla/pdf.js/blob/12aba0f91a5cd3e36fa81cb799540f8073990831/src/core/jpg.js#L448-L453
The problem is much more likely that this particular JPEG image is corrupt in one way or another, and as mentioned above debugging would be easier with a PDF file containing the JPEG image.
(Also, please remember to fill out the https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md when opening an issue.)

Here's a PDF file with the JPEG image: test.pdf -- it displays blank in pdf.js and works in PDFium.

Fixed by the PR above.

Could you also update these? https://github.com/mozilla/pdfjs-dist/tree/master/image_decoders

pdfjs-dist will be updated automatically when the next release is made.


Binary classification: weights are shown only for one class

I just tried the baseline tutorial, keeping only 2 categories of classes, instead of 4.
When I render my explain_weights result, I only get weights for one class, as you see below.

My code looks like this:
from sklearn.datasets import fetch_20newsgroups

categories = ['alt.atheism', 'soc.religion.christian']
              # 'comp.graphics', 'sci.med']
twenty_train = fetch_20newsgroups(
    subset='train',
    categories=categories,
    shuffle=True,
    random_state=42
)
twenty_test = fetch_20newsgroups(
    subset='test',
    categories=categories,
    shuffle=True,
    random_state=42
)

from sklearn.feature_extraction.text import CountVectorizer
from sklearn.linear_model import LogisticRegression
from sklearn.pipeline import make_pipeline

vec = CountVectorizer()
clf = LogisticRegression()
pipe = make_pipeline(vec, clf)
pipe.fit(twenty_train.data, twenty_train.target)

import eli5

weights_explanation = eli5.explain_weights(clf, top=30,
                                                  target_names=twenty_test.target_names)

# Save to disk
with open('linear_weights.html', 'w') as file:
    file.write(eli5.format_as_html(weights_explanation))

I am using scikit-learn==0.21.3 and eli5==0.10.1 version.
I have the same problem when running this with another dataset too. Any ideas?
Edit: Does it maybe just mean that the green weights are contributing more to class y=1 and the red weights don't contribute so much to y=1, thus, they contribute to y=0?

Closing: I guess this might be the normal usage, according to https://stackoverflow.com/questions/51659523/eli5-show-weights-with-two-labels.


Proposal: Add event support to urql client

About
There are a lot of moving parts going on in Urql exchanges, these include:

Operation specific events (i.e. “operation deduped”)
Exchange state events (i.e. “cache state has been changed”)

Currently we provide a means for communicating some operation specific events but not all. There are no means to communicate exchange specific events which are not coupled to an operation.
This proposal is the addition of an event target. It's a pub/sub mechanism for exchanges to publish the aforementioned events and for devtools, a user, or any other third party to consume.
Usage
Listening to events in the console:
const client = createClient({ ... });
client.eventTarget.addEventListener(console.log);

Passing the client to a third party library (such as devtools);
myDevTool(client);

Types
Types only apply if a known key is used. This prevents conflicts with core while also allowing for ambiguous types.
If third parties want to add a type, can use declaration merging
import { DebugEventTypes } from 'urql'

declare module "urql" {
  export interface DebugEventTypes {
    newType: { dataProp: string };
  }
}

Todo

[x] Disable in prod
[ ] Add docs on debugging events
[ ] Add babel plugin to remove debug events in prod bundles (cc @JoviDeCroock)

Cheers for the thoughts @wgolledge

I'm guessing this could, down the line, remove the need for the devtools exchange?

Yes totally, instead we could just pass the client to a devtools function.

One more point on the event dispatching - I wonder whether it could make sense to have an optional dispatch system applied to every exchange that could be invoked (if the exchange desires) with a message and optional data (and the type if it can't be inferred)? It could save having to pass the client through exchanges 🤷♂

Initially I thought it would be a good idea to only pass the dispatch function but then realised that we already pass the client (which contains the EventTarget) so it felt pretty redundant.
I think most exchanges will end up with a function like this:
const myExchange = ({ client, forward }) => {
  const publishMessage = (m) => client.eventTarget.dispatchEvent({ ...m, source: "myExchange" });
  // ...
}

Awesome - yep looks good as far as I can see! Will wait for @kitten and/or @JoviDeCroock to weigh in

Update -
A few example of an event we might see:
{
  type: "fetch",
  message: "A network request has been made",
  operation,
}
{
  type: "refetch",
  message: "Attempting to refetch a failed network request",
  operation,
  data: {
    retries: 1,
  }
}

Required attributes are now:

type (UID for event)
message (human readable description)
operation (associated operation)
data (optional additional data)

This also means we need to change our devtools implementation so that we no longer listen via an exchange but instead for events. That way we streamline every message to look similar to the above.

@andyrichardson this seems like the way to go :+1: in what cases do we need to provide additional data? It'd be great if we kept this more on the untyped side, so that adding new debugging events would be easy.
What I basically mean is, if we make this a log call (naming-wise as well as in how it looks to contributors), then adding new calls could be useful in Jest / development as well as being very flexible when people go and add custom logging/debugging events in new exchanges.
So for instance, if someone goes and makes a retryOrAuth exchange, they may add
log('auth', 'Refreshing the current access token since it's expired);

So for them this would look just like console.log. It's also basically the same as what we currently do, we'd just allow for type to be raw strings as well.

Thanks for the response @kitten!

What I basically mean is, if we make this a log call (naming-wise as well as in how it looks to contributors), then adding new calls could be useful in Jest / development as well as being very flexible when people go and add custom logging/debugging events in new exchanges.

One of the things I want to really make clear with this is that it's an event bus for the purpose of debugging - not for logging events. While making it work like console.log does make things easier to get started, I think it sets a precedent that doesn't really reflect what's going on.
I wouldn't advise people use this for testing as it exposes implementation details. In a browser however, events could very easily be logged to the console.
const client = createClient({ ... });
client.eventTarget.addEventListener(console.log);

Every exchange action is associated with an operation, hiding that information when dispatching the event leaves room for ambiguity (not something you want when debugging).
The implementation of the event target is basically a 1-for-1 copy of EventTarget. If you want to trim things down a little, we could pass dispatchEvent as an argument to exchanges but I don't see too much benefit for that.

It'd be great if we kept this more on the untyped side, so that adding new debugging events would be easy.

Have you tried dispatching a custom event? There's nothing stopping you from doing that - the types are there for type safety and to prevent conflicts between third-party exchanges 👍

So regardless of this being associated with testing or debugging (those were just other use-cases that came to mind), I believe the client.eventTarget.dispatchEvent naming doesn't immediately indicate that this isn't a core part of the package / client's architecture.
So while the terms "info" or "logging" (the latter indeed being inaccurate) may not be what we want here, I think it may make sense to replace the term "event" here, e.g. client.debugEvents.dispatch or client.info.dispatch, etc.
Overall I believe it should be clear to someone using this or reading our exchanges that this isn't something they need to learn, or something that we have to mention explicitly in the "Concepts" docs to avoid confusion.
To us this is just an addition, but I think using the term "events" in this case without other hints in the code to its purpose could make it be confused with streams, since we use the term "events" frequently to explain what streams/observables are. (ref: https://formidable.com/open-source/urql/docs/concepts/stream-patterns/)

Sure thing @kitten I wasn't aware that your issue was with the use of the term eventTarget and I've renamed it to something less generic - debugTarget

I've found a limitation of the current state notably being the lack of source.
We can either get this merged and add source support once I've had time to flesh it out or can hold this off for now.


Checking for updates

I absolutely love that your updating this app every day or multiple times a day - however I just use it as a glorified game launcher and havent had an issue in years.
Can we please get the option to disable update checks? Also...whats checking for updates? I blocked winlaunch.exe in firewall for both inbound and outbound but its still seeing a new update somehow

v.<IP_ADDRESS> fixed this issue.

v.<IP_ADDRESS> fixed this issue.

Allowing me to "lower" the frequency of updates is not the same as being able to disable them


onScrollOffsetChange lag

Does onScrollOffsetChange lag for everyone else or is that just me? I'm using it to adjust the size of a header and it's very delayed on some device, continuing to change the offset number seconds after the scroll stops. Is there a way to cut down the interval or any other tips on improving performance?
Platform & Dependencies
Please list any  applicable dependencies in addition to those below (react-navigation etc).

react-native-draggable-flatlist version: 3.1.2
Platform: ios and android
React Native or Expo version: react native 0.68.2
Reanimated version: 2.8.0
React Native Gesture Handler version: 2.4.2

I am also experiencing this issue. Did you figure out a solution to cutting down the interval?

Any workaround on this issue?


Error when require a PNG image

This only happens on build step, it doesn't happen on dev mode. I guests it's node/webpack environment
Stack trace:
Template execution failed: SyntaxError: /home/khoa/web/tooth/frontend/components/search/trans.png: Unexpected character '�' (1:0)
  SyntaxError: /home/khoa/web/tooth/frontend/components/search/trans.png: Unexpected character   '�' (1:0)
  > 1 | �PNG
      | ^
    2 | ?
    3 | [22m
    4 | IHDR  m[41  1mQ�^a[22m  2mtEXtSoftwareAdobe ImageReadyq�e  m<  qiTXtXML:com.adobe.xmp  <?xpacket begin=" " id="W5M0MpCehiHzreSzNTczkc9d"?> <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk  3m="Adobe XMP Core 5.5-c014 79.151481, 2013/03/13-12:09:15        ">  m <rdf:RDF xmlns:rdf="http:  //www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:[33mDescription rdf:about="" xmlns:xmpMM=[39m"http://ns.adobe.com/xap/1.0/mm/" xmlns:stRef="http:/  /ns.adobe.com/xap/1.0/sType/ResourceRef#" xmlns:xmp="http://ns  .adobe.com/xap/1.0/" xmpMM:OriginalDocumentID="xmp.d  id:d3a7c906-7b1b-1749-be6c-7b7c0df0881c" xmpMM:DocumentID=  m"xmp.did:FC0A9B24DE7111E4A312C636C492E7C2" xmpMM:InstanceID="xmp.iid:FC0A9B23DE7111E4A312C636C492E7C2" xmp:CreatorTool  ="Adobe Photoshop CC (Windows)"> <xmpMM  9m:DerivedFrom stRef:instanceID="xmp.iid:f76eb8  cd-94ec-114f-a62f-7f548c5ac408" stRef:documentID="xmp.did:d3a7  c906-7b1b-1749-be6c-7b7c0df0881c"/> </rdf[39m:Description> </rdf:  9mRDF> </x:xmpmeta> <?xpacket end="r"?>t`��ID  ATxڼ��

  - index.js:4452 Parser.pp$5.raise
    [frontend]/[babylon]/lib/index.js:4452:13

  - index.js:1147 Parser.getTokenFromCode
    [frontend]/[babylon]/lib/index.js:1147:10

  - index.js:776 Parser.readToken
    [frontend]/[babylon]/lib/index.js:776:19

  - index.js:7148 Parser.readToken
    [frontend]/[babylon]/lib/index.js:7148:20

  - index.js:766 Parser.nextToken
    [frontend]/[babylon]/lib/index.js:766:19

  - index.js:1672 Parser.parse
    [frontend]/[babylon]/lib/index.js:1672:10

  - index.js:7180 parse
    [frontend]/[babylon]/lib/index.js:7180:37

  - index.js:517 File.parse
    [frontend]/[babel-core]/lib/transformation/file/index.js:517:15

  - index.js:602 File.parseCode
    [frontend]/[babel-core]/lib/transformation/file/index.js:602:20

  - pipeline.js:49
    [frontend]/[babel-core]/lib/transformation/pipeline.js:49:12

  - index.js:564 File.wrap
    [frontend]/[babel-core]/lib/transformation/file/index.js:564:16

  - pipeline.js:47 Pipeline.transform
    [frontend]/[babel-core]/lib/transformation/pipeline.js:47:17

  - node.js:152 Object.transformFileSync
    [frontend]/[babel-core]/lib/api/node.js:152:10

  - node.js:118 compile
    [frontend]/[babel-register]/lib/node.js:118:20

  - node.js:144 loader
    [frontend]/[babel-register]/lib/node.js:144:14

  - node.js:154 Object.require.extensions.(anonymous function) [as .js]
    [frontend]/[babel-register]/lib/node.js:154:7

  - module.js:20 require
    internal/module.js:20:19

  - index.js:4 Object.<anonymous>
    /home/khoa/web/tooth/frontend/components/search/index.js:4:1

preact build --no-prerender will fix this in the interim.  We need to shim in a binary data loader for the prerenderer, should be pretty simple to do.

IMHO the best idea would be to use webpack to create a bundle exporting (library target?) root component which would be processed by preact's string renderer.
This way all glorious webpack loaders are preserved (e.g. url loaders, image size optimization etc).

@rkostrzewski this is how we are doing it in Phenomic . To be fair, this is a very complicated thing to do and there are many important bugs than this. So I suggest that in the mean time, just tell user to avoid webpack specific loader (just like Next.js did)

I've been thinking we might have to do the webpack-on-the-server route.  It's not the worst thing, the current loader injection stuff I had to add to get basic apps working under Node directly is pretty gross.
I've seen people use UMD for both their web bundle and their Node import for SSR - think that'd work?  Not sure if it would bloat the bundle size at all.

@rkostrzewski this can be closed right ?

I don't think this is fixed.

This is fixed by switching to prerender using Webpack.


Turn-taking bot

The turn-taking bot realizes a controlled dialogue flow between two users.
Necessary data is read from the example file questions_images.json.
For the bot to work properly you will have to set the plugin triggers (both in the waiting_room.json and in the meetup_task.json) as follows:
"submit-message": "intercept-message"
"print-history": "intercept-history"

Nice work!
Was this designed to be a sample bot or as bot for a specific project? We want to keep the bots in the repository as small as possible and probably completely remove all sample bot and move them to external repositories as mentioned in #45 and only link them in the README.md and the documentation.

I guess, @davidschlangen likes to see interceptions in action? Here you go! 🙂

Good stuff!
This is meant to be a sample bot. It’s a fine line, but I think this kind of abstract skeleton bot should indeed be bundled with the main code.
Which reminds me, I’m not exactly clear what the role of the mentioned plugin trigger jsons is, but whatever it is, the file should not be called meetup_task.json. The term „meet-up“ should not occur anywhere, in fact, as this is a concrete instantiation in a particular game (which has nothing to do with this one).

-Makes sense! (Putting both into a directory.) questions_images.json is only used there, as far as I know.


RDS IAM Token Generation

I am having trouble figuring out how to generate the token based on the example given in the aws_sig_auth crate
Based on the function name, I was expecting a token to be the output when I run it and I can then plug in that token as the password and connect to the DB
However the output of the generate_rds_iam_token is returning the following:
"[DB URL]:5432/?Action=connect&DBUser=rw_iam&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=[KEY]%2F20230608%2Fus-east-1%2Frds-db%2Faws4_request&X-Amz-Date=20230608T030929Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=992e883d26959e655886c1ee3cd1ecb7f48676802663d054eb283f158fbb0466"

There is no Security Token that is being returned and as a result, I can't input it as the password

Actually I think I got it. Think It's due to the Key that is being used which preventing the Security Token from being generated


Cleanups

(best read commit-by-commit)

when merged, also update:

https://opensource.axo.dev/cargo-dist/book/quickstart/javascript.html
https://github.com/axodotdev/axolotlsay-hybrid/


OpenAPITool Helidon Documentation

[ ] Server MP
[ ] Server SE
[ ] Client MP
[ ] Client SE

See:
#4021
#4020
#4018
#4023

Re-opening this issue because we have not moved the docs to 4.x yet.
I will do that forward port at some point.

With 4.1 both the MP and SE docs for generating clients and servers reflect the recently-enhanced 4.x generation features. Closing.


[BUG REPORT] Test Cases Needed for New Merge/Diff Logic and API

Describe the bug
A clear and concise description of what the bug is.
Test cases are needed for the changes introduced in #32.
Severity

Select an option:

[ ] Data Corruption / Loss of Any Kind
[ ] Unexpected Behavior, Exceptions or Error Thrown
[ ] Performance Bottleneck

N/A
To Reproduce
Steps to reproduce the behavior, minimal example code preffered:
Run the tests
Expected behavior
A clear and concise description of what you expected to happen.
More thorough testing.
Screenshots
If applicable, add screenshots to help explain your problem.
N/A
Desktop (please complete the following information):

OS: any
Python: any
Hangar: 0.0.0 -> 0.1 rc

Additional context
Add any other context about the problem here.
See #32 for changes introduced

Hi @hhsecond, can I assign this to you? I know you were starting to dig into the diff and merger internals the other day, and since this is stable (even considering the changes introduced in #70), its a good project which we won't duplicate effor on.

@rlizzo Sure, I'll take it up.

Fixed in #76


Docs layout issues when announcementBar visible

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[ ] I have tried the npm run clear or yarn clear command.
[ ] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[ ] I have read the console error message carefully (if applicable).

Description

When the announcementBar is visible, the docs sidebar has a weird layout issue
Page: https://docusaurus.io/tests/docs
Good URLs to reproduce (long sidebar collapsed - long content):

https://docusaurus.io/docs/sidebar/items
https://docusaurus.io/tests/docs/toc/toc-_-5/

Note: it's not because of the hideable sidebar feature, the issue is also there when there's no sidebar collapse button
Also related to https://github.com/facebook/docusaurus/issues/7815: the announcement bar height should probably be dynamic/flexible and layout should rather adapt gracefully to any size.
Reproducible demo
No response
Steps to reproduce
https://docusaurus.io/tests/docs
Expected behavior
No weird layout with elements overlapping
The visible scrollbar takes the appropriate height.
Actual behavior
Elements overlap and the scrollbar does not go up to the bottom (the scrollbar should touch the collapse button)
Your environment

Public source code:
Public site URL:
Docusaurus version used:
Environment name and version (e.g. Chrome 89, Node.js 16.4):
Operating system and version (e.g. Ubuntu 20.04.2 LTS):

Self-service

[ ] I'd be willing to fix this bug myself.

I'd like to work on this.

Hi everyone!
I have investigated this issue and believe I have created a fix in this PR.  It appears that a CSS property of fixed is causing the overlapping issue seen in the above screenshot.  I have removed the CSS property and was hoping to get some reviews.  Thanks a bunch!

@slorber I would like to work on this issue if it is available.

i will try this issue with #8374

Hello @slorber, I have found the solution to this problem, How do I make sure the fix doesn't create other issues, can you please help, it's my first time contributing.

@arbitrarymahi you can create a pull-request and we'll review it.
Note: all attempts to fix this have failed so far, it's not an easy issue to take for a first contribution so make sure you tested all the edge cases.

@slorber Please check my PR for this issue: https://github.com/facebook/docusaurus/pull/8829

Hi community
Thanks for all contributors that gave it a try to solve this annoying layout problem.
We received multiple PRs but no implementation provided was satisfying enough.
All the proposed PRs had bugs in the review URLs I suggested:

docusaurus.io/docs/sidebar/items
docusaurus.io/tests/docs/toc/toc-_-5

This problem is likely more complex to solve than it seems, and I'll probably have to handle it myself instead of asking for community help.
For now, I suggest that the community step back on this issue and stop submitting PRs. I'm going to do the cleanup and close the existing PR attempts.
If you still think you can solve it properly and submit a PR, please review carefully the 2 URLs above so that there is no issue at all (we are not looking for a partial fix here) on different viewport sizes with/without the announcement bar. I'll review these pages very carefully on your PR so doing this work upfront ensures that your PR is valid.

Initially I was only looking at CSS functionality which was the incorrect approach.

@r-lawrence will review your PR on time but please make sure your solution works BEFORE react hydration. If it's using hooks it's likely working only after hydration.
For me, the solution is rather CSS math + inlined JS, and I'll review carefully that it works as I expect it to. Please test your PR with slow 3G mode activated and ensure there are no unexpected layout shifts during the React hydration, and that it works fine if we attempt to scroll before the hydration.

Argos CI is new, I'll review the UI diff reported, but wonder why your PR should involve minor changes at all.

before I mark them as ok.

Are you able to do that? This is unexpected.

will review your PR on time but please make sure your solution works BEFORE react hydration. If it's using hooks it's likely working only after hydration.

I didn't have to much time to take a look at this right now, but I think you are correct.  When running the functionality on 3G slow throttled mode in the chrome dev tools, there is a small layout shift.  You can see it in this short video.  The bottom sidebar ad and button are initially located incorrectly because the hydration has not occurred and the application has not detected the announcement bar.  Then it adjusts its positioning, after the hooks events fire.
https://github.com/facebook/docusaurus/assets/62929526/f586258c-ac18-4749-b46a-6a967096c191

I think I may be a bit confused...  How does the announcement bar show up before hydration?  It appears it managed by the useContext hook listed above.   Is there a way we can somehow mimic this functionality for the sidebar too?  IE - allowing for the application to detect if the announcement bar is present before hydration, then using the hook to correctly adjust height based on scroll movement?

do you have any suggestions on how this can be done with strict CSS math + inline JS?  I'de be happy to give them a shot.

Also, originally the functionality that used the useAnnouncementBar function from packages/docusaurus-theme-common/src/contexts/announcementBar.tsx was housed in packages/docusaurus-theme-classic/src/theme/DocSidebar/Desktop/Content/index.tsx.  To me, it appeared this functionality was added in an effort to fix the sidebar issue when the announcement bar was present.  This functionality is what causes the margin to be off in the sidebar when the announcement bar is present.  In turn, this also affects the scrollbar not extending to the bottom of the sidebar.  (see screenshots below)

Even if this solution isn't viable, should we still remove the functionality added to packages/docusaurus-theme-classic/src/theme/DocSidebar/Desktop/Content/index.tsx to add margin when the announcement bar is detected?  This is causing the bug thats related to the scrollbar not extending to the bottom sidebar ad

Argos CI is new, I'll review the UI diff reported, but wonder why your PR should involve minor changes at all.

Looking at this quickly, some css was changed to allow for the sidebar ad and button to always be positioned at the bottom of the page.  The resulting UI changes could be from some of this CSS.  There was two places I changed css for height - packages/docusaurus-theme-classic/src/theme/DocRoot/Layout/Sidebar/styles.module.css and packages/docusaurus-theme-classic/src/theme/DocSidebar/Desktop/styles.module.css.  One of these changes could be causing the layout shift in Argos?
Thanks for your response and when I have additional time later, I'll be happy to continue looking at this for a bit!

@r-lawrence I'm not super familiar with this code and can't help you much. It is there for a long time, was not coded by me.
I am not 100% sure of the solution to use and how many changes are required. If I help you figure things out, I would be faster to actually solve the problem myself.
What I'm sure of is the outcome we want: 0 layout shifts.
And for that, I believe reading localStorage in inlined JS + using CSS math could work. not sure but it's what I would try first).
If you are able to solve it on your own that's nice, otherwise, I can't really help and it's preferable that you close your PR.

@slorber Hey no problem.  I'll work on this a bit later when I have some more time.  If I can't come up with a solution in a reasonable time, I'll go ahead and close the PR.  Thanks!

Hi @slorber - is this issue still open ? I would like to give a try!


Mismatch between ts-rs's idea of camelCase and serde's

I have a type like this:
#[derive(Debug, Serialize, TS)]
#[serde(rename_all = "camelCase")]
#[ts(export)]
pub struct ItemImageList {
    pub id: u32,
    pub crc32c_hash: u32,
}

The generated camelCase field name from serde for the field crc32c_hash is crc32cHash. ts-rs, on the other hand, decides to generate the following TS file:
// This file was generated by [ts-rs](https://github.com/Aleph-Alpha/ts-rs). Do not edit this file manually.

export interface ItemImageList { id: number, crc32CHash: number, }

This obviously leads to problems when trying to use the ItemImageList interface in TS to read JSON serialized by serde.
The solution for me for the time being, has been to slap #[ts(rename = "crc32cHash")] on the field. But the question is, should there actually be a discrepancy here?

Thanks for opening the issue!
No, this is definetely not intentional. We use the inflector crate for converting between the inflection. Unfortunately, it seems like it isn't 100% compatible with serde. I suppose we need to figure it if we can directly use serde's logic for this conversion, or if has to be re-implemented.

Apparently this isn't the only crate being "hit" by this mismatch. https://github.com/whatisinternet/Inflector/issues/85


Updated Javadocs comments for new methods

Provided more detail in javadocs comments for new methods

Codecov Report

Merging #109 (24f04f6) into add-delete-group-modification (928cdd1) will not change coverage.
The diff coverage is n/a.

@@                       Coverage Diff                        @@
##             add-delete-group-modification     #109   +/-   ##
================================================================
  Coverage                            62.44%   62.44%
  Complexity                             408      408
================================================================
  Files                                   80       80
  Lines                                 1467     1467
  Branches                               157      157
================================================================
  Hits                                   916      916
  Misses                                 511      511
  Partials                                40       40

Impacted Files
Coverage Δ

src/main/java/seedu/address/model/AddressBook.java
75.00% <ø> (ø)

...n/java/seedu/address/storage/JsonAdaptedGroup.java
23.80% <ø> (ø)

.../java/seedu/address/storage/JsonAdaptedPerson.java
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 928cdd1...24f04f6. Read the comment docs.


Update location and description

I have moved to South Sweden, so I need to update this as well.

Docs Build status updates of commit 57e01f2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

rd/tibi-covaci.yml
:white_check_mark:Succeeded

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

@tibor19
Your changes are merged and published to RD website. Please check it from RD website: https://rd.microsoft.com


Change "Manage" to "Create" dynamically on landing page

During user testing, users were confused about your use of the word "Manage..." for the "Manage DNS Records" and "Manage Certificate" buttons, when they didn't have either.
We should set the text dynamically based on whether the user has any DNS Records or Certificate yet:

If a user has no DNS Records: "Create DNS Record", otherwise "Manage DNS Records"
If a user has no Certificate: "Create Certificate", otherwise "Manage Certificate"

I think I can handle this.


Using Warning and Error Severity

Thanks for this excellent tool. I’d like to trigger warning and error states at different values on the same linter, something like:
SelectorDepth:
  max_depth: 2
  severity: warning

SelectorDepth:
  max_depth: 3 # Only permitted if overriding vendor CSS
  severity: error

My desired output would be [W] for rules matching SelectorDepth: 3 and [E] for rules matching SelectorDepth:4.
The readme mentions scss-lint can return both warnings and errors, but I can’t seem to get this working on a single property. Is this supported? If so can someone share an example config please? If this is not supported, please let me know so I can add “Feature Request” to the issue title 😉
Thanks!

Hey @oli, thanks for suggesting ways we can improve the tool.
The format you suggest would not work because of the YAML specification itself. YAML will treat duplicate keys as overwriting previously-defined keys, for example:
# test.yaml
linters:
  SelectorDepth:
    max_depth: 2
    severity: warning

  SelectorDepth:
    max_depth: 3 # Only permitted if overriding vendor CSS
    severity: error

Running the following command:
ruby -e "require 'yaml'; puts YAML.load_file('test.yaml').to_yaml"

You'll get:
---
linters:
  SelectorDepth:
    max_depth: 3 # Only permitted if overriding vendor CSS
    severity: error

Thus this is fundamentally not supported at the YAML level.
Thus support for this would need to be added on a per-linter basis. I'm open to pull requests but I think you might be nearing the area of "overcomplicating" your rules. Warnings have their place but I would see the example you provide as being more annoying than useful. I personally want to see output when there is an actual problem.
Hope that helps!


Make the starter completely responsive

The current version does not work very well on mobile. That should be improved. :)

I'll see if I can have time next weekend! What methodology for css did you guys pick? I guess anyway css grid with flex fallback for the layout?
Any constrictions about the design? Not that I'm a good designer but I can check dribble and dunk something... Good job so far!

That's great Matt. 🎉

I'll see if I can have time next weekend! What methodology for css did you guys pick? I guess anyway css grid with flex fallback for the layout?

No methodology so far... I'm personally up for anything as long as it's consistent and not too much overhead. Right now it's hand written.

Any constrictions about the design? Not that I'm a good designer but I can check dribble and dunk something... Good job so far!

You've got free hand and we can give each other feedback about it? :)
Personally I think the looks of the current implementation are "relatively pretty". :D

Fixed in #25


Updating menu options causes a NullReferenceException

Whenever a mod tries to update the value of a menu option, like a slider, a NullReferenceException is thrown.
As a more concrete example, a mod uses the "OnLoadLocal" interface to load some data from the save file. In this function, the mod tries to update the value of the slider representing the same option as the one loaded from the save file, otherwise, the slider will show the default value for that option instead of the one actually used by the mod:

The slider is created much earlier than when local data is loaded, in the "GetMenu" interface:

Upon closer inspection, the exception is thrown by line 305 of the "MenuUtils.UpdateOption" function, when "label.key" is evaluated, but "label" is null:

This parameters seems to be null because of a bug in the lambda defined in function "ModMenu.AddModOptions", line 141:

This function calls "UpdateOption" first, and then calls the appropriate Update function of the option, depending on it's type. However, for the second argument, it passes all sorts of data depending on the option type, except for the label. Since this function calls the Update function with a null label, which in turn calls "UpdateOption" again, but this time, without a label set, causing the NullReferenceException.

Why would you change the value of the slider in the OnLoadLocal since it will be initialized with localData.annotationLimitIndex when creating the slider in GetMenu?

The "GetMenu" is not called if you go to the menu in-game and try to change the options of the mod. In this case, the slider is initialized before local data is loaded, with the default value from "localData.annotationLimitIndex". If a save file is loaded, localData.annotationLimitIndex is updated with information from the save file, but if you go into the menu to check the settings, you will still see the default value. This can cause confusion and does not allow the actual value to be checked by the player.

Fixed in v1.0.4


Can't run project

For both variants (from wav and mic recording) that I try - same error:
Traceback (most recent call last):   File "parse_file.py", line 39, in <module>     process_file(**vars(args))   File "parse_file.py", line 31, in process_file     with WavProcessor() as proc:   File "/mnt/Data/project/devicehive-audio-analysis/audio/processor.py", line 45, in __init__     self._init_youtube()   File "/mnt/Data/project/devicehive-audio-analysis/audio/processor.py", line 74, in _init_youtube     youtube8m.model.load_model(sess, params.YOUTUBE_CHECKPOINT_FILE)   File "/mnt/Data/project/devicehive-audio-analysis/audio/utils/youtube8m/model.py", line 43, in load_model     set_up_init_ops(tf.get_collection_ref(tf.GraphKeys.LOCAL_VARIABLES))   File "/mnt/Data/project/devicehive-audio-analysis/audio/utils/youtube8m/model.py", line 26, in set_up_init_ops     if "train_input" in variable.name: AttributeError: 'str' object has no attribute 'name'
Model was downloaded from your link.

What is your Python version?
python --version
You could also try to use python3 (do not forget to install dependencies with pip3).

I meet the same problem, python2, python3 both not work

I have solved the problem imported by pycharm, maybe some dependencies not install

Same here, but I have all dependencies installed as per the requirements.txt

Ok, so to anyone having this problem, make sure to specify your mic using input_device_index=x on your self.in_stream() and self.out_stream() functions in device.py.
To find the ID of your input device, run (note, run sudo pip install sounddevice first):
import sounddevice
print(sounddevice.query_devices())

where you can look through all sound devices attached to your computer.

This removed the initial problem I had, and it actually runs perfectly on my laptop running Linux Mint, but when I try to port the code to a Raspberry Pi 3 (which has all packages correctly installed with reference to the requirements.txt),  I'm always given the -9981 Buffer Overffow error.
Is it impossible to run such an application on the limited hardware of the Raspberry PI? By the way thank you very much for publishing a really cool use of Tensorflow for audio analysis.


fix: update dependencies to solve the problem of garbled CJK characters

Ref: https://github.com/fiatjaf/nostr-tools/pull/20
Update dependencies to solve the problem of garbled CJK characters:

hey there, thank you this has been merged. closing.


Error on missing file when searching for cluster id

Sometimes when DDC searches for the cluster Id in the db files under <DREMIO_HOME>/data/db if a compaction occurs the file could be removed before parsing, for example
INFO:  2024/02/21 11:32:02 local.go:349: found clusterIdentity key in file /opt/dremio/data/db/catalog/631143.sst
INFO:  2024/02/21 11:32:02 local.go:310: found cluster ID 'xxx-xxx-xxx-xxx-xxx' in file /opt/dremio/data/db/catalog/631143.sst in 513 seconds
ERROR: 2024/02/21 11:32:02 local.go:265: during unable to collect cluster stats like cluster ID: error walking the path /opt/dremio/data/db: prevent panic by handling failure accessing a path "/opt/dremio/data/db/catalog/635623.sst": lstat /opt/dremio/data/db/catalog/635623.sst: no such file or directory

was fixed in #213


Switch default digest type for BookKeeper to CRC32c

CRC32c is faster than CRC32. In release 2.0, we included BK-4.7 which already supports CRC32c, so we can safely change the default for 2.1 to CRC32c.
This is a followup action from #1369

Yes


VS Code: release v1.6.1

VS Code: release v1.6.1 - patch release.
Test plan
n/a

Would it make sense to do the 1.8 release earlier with this PR? Otherwise, we would need to cherry-pick and release from the branch, which does not have any value in itself. cc @kalanchan @philipp-spiess

@valerybugakov I just know from my side but I do want to get https://github.com/sourcegraph/cody/issues/3216 into the release which is not done yet 😬 . I’m fine with doing a release from main personally though.

I cherry-picked only the commit I'm interested in for the A/B test on top of the last release to ensure we're good for a Wednesday release.


Use a custom directory <> module mapping for Python modules?

I have a project where Python files from multiple repositories are combined into a single Docker image and then restructured into a single Python package. Is there a way to make Visual Studio Code aware of this nonstandard structure to get code completion, analysis etc.? In other words, given an import like
import A.B.module as module
the IDE should look for module in path X/Y using some set A.B -> X/Y mapping.
Alternatively, it could internally treat import A.B.module as module like import module as module (ignoring the A.B.), which could be used in combination with python.autoComplete.extraPaths to pick up on the missing imports.
https://github.com/microsoft/pylance-release/issues/1948 is a similar issue, but doesn't look like it has gone anywhere.

Pylance is built on top of Microsoft's open-source type checker called pyright. Pyright supports a way to configure multiple "execution environments" within your project. For full details refer to this documentation. Within each execution environment, you can specify a different root directory, Python version, Python platform, and additional import resolution paths (extraPaths). I think this may address your needs.

Looks like that tool lets you define multiple import resolution paths, which is very helpful, but it doesn't quite help with the import resolution issue I'm facing.
For reference (this is essentially the same issue as https://github.com/microsoft/pylance-release/issues/1948), I'm working with several GitHub repos structured like so
repo1
  src
    file1.py
    file2.py
    ...
repo2
  src
    file3.py
    ...

which are merged into a single Docker container / Python package at runtime:
package
  repo1
    file1.py
    file2.py
    ...
  repo2
    file3.py
    ...

All first-party imports are absolute - import package.repo1.file1. This works at runtime, but isn't recognized by the IDE, since it doesn't match the compile-time code structure.
By adding several root directories using Pylance's extraPaths, multiple execution environments etc., I can get relative imports like import file1 working, but still not absolute ones like import package.repo1.file1.
It's also possible to clone multiple repos into a single directory and mimic the structure of the package like so:
[VSCode root directory]
  package
    repo1
      src
        file1.py
        file2.py
        ...
    repo2
      src
        file3.py
        ...

But this only enables imports like import package.repo1.src.file1- almost, but not quite import package.repo1.file1. My question is whether it's possible to get this kind of import working via IDE config without reworking the code layout.

You're correct — execution environments won't work for you unless you change the layout of your repo.
Your needs are similar to those of a library author who is working on code that is intended to be installed in site-packages and executed from that context. The standard way to handle that is through the use of an "editable install". You would need to create a setup.py that describes how your final package is laid out. Then members of your development team would simply do a one-time pip install -e <local package name>. This would create a <package> directory in your site-packages folder. Within that <package> directory will be ".pth" files that are symbolic links that point back to your project source. This effectively creates the final on-disk structure and allows static analysis tools like pylance, mypy, pylint, etc. to resolve imports as they will be resolved at the time the code is executed.


Make spawn detect .cmd files on windows

npm installs bin files with .cmd extension on Windows. When I install https://github.com/fhelwanger/ocaml-on-windows, I get opam.cmd, ocamlmerlin.cmd, etc.
The problem is that child_process.spawn doesn't find .cmd files by default. This PR adds {shell: true} to spawn options to make it work on Windows by default. This way, users won't need to configure paths manually.

I tried this change on linux and it seems to still be working. I don't have a windows to try, but I would be ok to merge the change if you say it works for you.
@freebroccolo is it ok if I accept some merge requests like this one?

This is a fine change. Let's just merge it.

@Khady @chenglou yes, it is fine with me to merge stuff like this if I haven't gotten to it yet and it looks reasonable


Project by tag - does not work or am i the problem

May bethis is no issue ...
I create a project based on "tag", not "folder".
No note is listet but i have a lot notes with the selected tag like "project" or "priority".
Did i something or something not to prevent it to work?

For a tag named in daily, you can build the project with the target tag field filled in the form #daily. Maybe double check the # sharp character and retry will solve this. If the problem persists, feel free follow up and you can post the project config and an example note for better reference.

It works fine, found the discussion about tag tags and # ...
As often, the main problem is in front of the PC ;-)


Fix capitalization in bibliography

For the JOSS paper, there are some tricks to protecting capitalization in references.  JOSS uses a bibliographic style that uses Initial case, rather than Title Case for references.  But, U.S. (as an example), should be kept capitalized.  The answer (and some subtle issues, are described in https://tex.stackexchange.com/questions/10772/bibtex-loses-capitals-when-creating-bbl-file#:~:text=Lower-casing works indiscriminately--,you enclose them in braces.
No action needed from the team here.  I'll get you a PR in a bit to fix this.

OK, if I've done things correctly, you should have a PR that has the changes to close this issue.  I don't work in GitHub that much (my employer uses an internal GitLab instance for our work), so I may not have done things exactly right.  But, you can see what I did to fix the issue and double check me to see that I've caught everything.

This was implemented in PR #481 . Cheers @usethedata!!!