text:
Video limit didn't seem to work on A7

I have an A7 (ILCE-7) and successfully installed OpemMemories - Tweak today. I was on firmware 2.0.0 and tried setting the video length limit to maximum, but after 30 minutes of video my camera stopped recording (e.g. the tweak had no effect). Then I updated to firmware 3.1.0 (the latest) and tried it again, still no effect.
Thanks for developing this, hopefully this debug info is useful. Happy to try any fixes you suggest.

Can you try setting it to 5 seconds?

I changed it to 5 seconds and it worked (stopped recording video automatically after 5 seconds). Then I set it back to maximum (13h 1m), and tested again and it stopped recording after 30 minutes (no change).

Does it stop exactly at 29:50 / 29:51? Otherwise it could be due to overheating or other factors.

Yes exactly at 29:50

Uhm, I can't see the clip length in your screenshot :)
What does the app display for "current limit" if you just open it up?

Those are the raw .MTS files it recorded to the SD card, 10:40 + 10:40 + 8:29 = 29:49 (off by 1 due to rounding). The current limit in the app says 13h 01m 00s. At the end of the recording I hear the 'chime' sound it plays when ending recordings + the camera isn't very warm.

Sry, my bad. It's a bit weird because it seems to work on the A7M2. I will look into this when I have time.
If anybody else has tested this on the A7, please comment here.

It doen't work on my sony a7 too :(

Do you have the same symptoms? Does setting it to 5s work, but not 30min?

Im setting it to no limit,
Well, anyway, thank you very much , for what you did for us
Hope you can bring features on the a7mkii for sony a7 user : 14bit raw and supports phase auto focus with mount adapter 3rd party. ^^
here is my catlog
TWEAKLOG.TXT

It worked with my Alpha 7 rii Camera. Firmware 3.10, japanese import! Great! I had to use windows.IE Browser.Now I have all languages.And the Video function.
Didnt work with Safari and Mac.
Thanks a lot!

4 Hrs non-stopping recording achieved. No temperature warning at all. Got one 113GB and one 35.2GB files Seems Sony still splits files every 3hrs recording.

This issue is about the A7.

Could it be that the hack does not work with AVCHD recording and only works on cameras that are recording on XAVC?

Also experiencing this issue A7 (Mk 1).  5s setting works, but recording stops at 29:50 when I choose maximum (13h).

Everybody: Which settings are you recording in (codec / framerate / etc)?

A7r won't record past the 30 min limit even though the tweak says 13h 01m 00s. The 5s test does work. It is set to record in AVCHD,  24p, 1080. Region set to New York/Bogota.  My A7sii and Rx100iii will record past the 30 minute limit.

U.S. AVCHD 1080p 60p

60p 28M(PS) AVCHD

I'll add also 28M (PS) Chicago/Mexico City

Doesn't work on my A7 mk1 either. 24p 1080 region set to New York/Bogota

Have same situation.
5s test break works, but without sound
0:29:50 and 13:01:00 options successfully stores their selection in app even after reboot, but both breaks at 0:29:50 with standard sound
firmware 3.1.0
region is Europe/Moscow
bug occures at 25p/17M and 50p
Thanks for great work!

Same here.
A7 (V3.10) after 29:50 min stops (region is Europe/Paris bug occures at 25p/17M and 50p)
RX100iii no problem >30 min with XAVC-S and AVCHD codec (tried both).
Anyway; thanks for the big efforts so far. Much appreciated by many people fro sure!!

confirm. doesn't work on A7r ILCE-7Ra Please HELP  (PS tested on A7ii - no issues. )
details:
camera
ILCE-7R
Ver. 3.10
app
tweak app version 0.9
java API 2.3
Disable video rec lim : check on (current limi: 13h 01m 00s)
result
camera makes beep sound and stops on 29:50 all the time
camera doesn't post any warnings etc
TWEAKLOG.TXT

confirm:
cameras:
ILCE-7
Ver. 3.10
ILCE-7
Ver. 2.00
app:
tweak app version 0.7.1
same situation:
5s test break works, without sound
0:29:50 and 13:01:00 options successfully stores their selection in app even after reboot, but both breaks at 0:29:50 with standard sound

Confirming the issue here as well.
ILCE-7
Ver 3.10
Same as others have reported, the setting appears to take effect, but camera still stops recording video just short of 30 minutes.

I tested on A5000, A6000, and A7mk1 A7Rmk1.
In all these cameras the same problem - stops at 29:50.
A6000 tested on the new software with XAVCS. Although it stops at 29:50.

Installed on Sony A7 with 2.0 firmware.
Enabled the longer recording length in app settings, said about 13 hours available
Unfortunately all video recordings stop at exactly 29:50.36
This is using AVCHD 1920x1080 and plenty of SD space
Updated to 3.20 Firmware, but still no joy.
Model: ILCE-7
Backup region: CX77801
Tweak app version: 0.9

Same thing for me, the video stops at 29:50 even after setting up the Unlock.
Would love the hack to work of this first version of the Sony A7.
Camera : ILCE-7
Firmware : Ver 3.20
Region :  Europe/Paris
Video Settings : AVCHD / 1080p / 60p 28M (PS)
Merci for your work ;)

Just installed and ran a test recording, stops at 29 minutes, 50 seconds.
Camera: ILCE-7
Firmware : Ver 3.2
Region : United States
Video Settings: AVCHD / 1080 24p
[INFO][InfoAdapter] Model: ILCE-7
[INFO][InfoAdapter] Backup region: CX77800_UC2
[INFO][InfoAdapter] Tweak app version: 0.9
[INFO][InfoAdapter] Java API version: 2.3
Included TWEAKLOG
Parts that look interesting:
[INFO][BaseProperty.exists] backup property 0x3c04b6 does not exist
and
[INFO][BaseProperty.setValue] backup property 0x10d008f is protected
[INFO][guessProtected] cannot write backup property 0x10d008f (probably protection)
TWEAKLOG.TXT

So are we still waiting for a fix on this A7 not working? I'm having the same problem. Excited to see this fixed so my A7 can be used for longer videos.

On Alpha 7S2 same issue but with 35 min, so strangely it get through the 29'50'' but for only 5'10'' more then stop.....
Hope you will able to fix it and thanks again for the achieved work.

Same problem here :-(
ILCE-7r, firmware 3.2
Installed tweaks successful, setting limit to 13h but recording still stops at 29'50"

@ma1co is using pmca-gui v0.15 on Firmware 4.0 is working finally? I have now a 7M2 and would like to test to unlock the recording time limit also, maybe it will work on this one. Thanks!

@milkagb pmca-gui should work since June 8 (the day FW 4.0 was released). If you have any problems, please let us know.

Any update?
It is still not work...
A7 mark1's last firmware is 3.20.

Did anyone figure out why this happens? Or is this one mystery that can't be solved?

I have this same problem. Do you have any solutions?

none at the moment...

;(

Hello and thanks for your work
Same problem here.
I do not hsve the option for 5" then I can try.
Camera: ILCE-7
Firmware: 3.2
Installed OpenMemories Tweak
Changed limit in app to Disable Video limit 13h 01m 00s
Recording video at 1080 50p AVHCD stops at 29' 50"
Recording video at 1080 25p AVHCD stops at 29' 50"
Hope we can solve it

I have the same problem. Any news. Thanks

Any news or Any solutions?

Same issue here on my A7

Same issue here:
Camera: ILCE-7
Firmware: 3.20
OpenMemories Tweak: 0.11
Recording video at 1080 24p AVHCD stops at 29' 50"

Same on my ILCE-7 :(

Same issue here.
Camera: ILCE-7
Firmware: 3.20
OpenMemories Tweak: 0.11
Tweak app says recording limit is set to 13h 01m 00s
Video actually stopped at 29:50
Wish I'd read these issues earlier. I tried to record an event (luckily it wasn't the only camera angle) and didn't know it stopped :(
Has there been any progress on this issue or hope of it being fixed?

How are you ?

In the meantime, has a solution been found for the ILCE 7 camera? We have the same problem: the recording stops just before 30 minutes and the tweak app has no effect.

Same issue here ☹

Same here with A6000.
Pls. can you asist?

I’m having a similar issue.  Camera info:
ILCE-7RM2 (a7 rii)
Tweak version 0.11
Android 4.1.2 (SDK 16)
Java API 2.14
I’m a little confused by some of the comments here (about setting an arbitrary recording limit). In the tweak app, under video, the only options are checkboxes for Disable video recording limit (13h 01m 00s) and Disable 4K video recording limit (RX100M4 only)(not available)
I just tried my first long recording since installing the app, and it stopped at 35min (longer than the old limit, but not by much). This was MP4, 1920x1080 30p.

authors: C-hiba Capestrano Chiarascuro Corstiaan Cosmo Jeziorko KCS74 Kedaranatha Lummerland1000 QuantMcDonald ShatteredPixelz Sion-Jones a7tulp acehobojoe arturjaracz chandy227 chungdha fantforever friendlygiraffe gimdongwoo jonlewisorg kurusutomari lawonga ma1co maxogden milkagb na7681 pete176 r3dm4n red-scott reugelo roryphd seifer7 thanhtran207 tomekdersuaaron


text:
JS Error FormData is not defined

Error: ReferenceError: FormData is not defined
at TurnstileVerify.validate (... dist/index.cjs:43:18)

Hi @OlegKunitsyn,
thanks for bringing this up.
Which Node.js version are you using?

source: gharchive/issue

authors: OlegKunitsyn maaaathis

repo: maaaathis/turnstile-verify

license: MIT

license_type: permissive

license_source: github-api


text:
which version of a module is installed?

if i update a module in lc, do instances of that module in unbuilt stacks auto-update, or do they have to be manually updated?
how do you tell what version of a module is installed in a stack?

if we discover that we do have multiple versions, the PI should also display the version

i just modified the code to navrad to add a little version property:
constant kVersion is "2.6.0"
property widgetVersion get returnVersion
handler returnVersion ()
	return kVersion
end handler

a brand new one has the property. the existing one (it can tell me its version) in the navrad editor stack has the old one (it can't tell me its version).
this kind-of affirms what i suspected because of the appearance of the navbar in the editor stack.

Oh, look, a contributor to the repo made a note about this very issue in 2018

in 2018, i say "nope, i was wrong"
so twice i have tested this and at some point during the test, come to the conclusion that the codebase did not update when the widget updated. the question is what recipe is leading to that situation?

repo: macMikey/LCB-missing-manual


text:
Unable to serialize checkbox values after change

I have a input form field that is checkbox. initially it is not checked. After checking the field becomes checked. However, when I try to serelizeObject, I do not see the value

However, if the field is loaded as checked during initial form load, then serialObject picks it up.
What am I missing?
Krish

I have following code in coffeescript to print out the issue
form_object = @$('form').serializeObject()
console.log(@$('form'))
console.log(form_object)
the form shows checked=checked value
however, the from_object does not set enable=true
Here is the video I captured from chrome console. It's such a pain to copy console.log to paste.
https://www.dropbox.com/s/62zhgpxvjikxs3v/UnableToProcess_Checkbox.swf?dl=0

I have following code in coffeescript to print out the issue
form_object = @$('form').serializeObject()
console.log(@$('form'))
console.log(form_object)
the form shows checked=checked value
however, the from_object does not set enable=true
Here is the video I captured from chrome console. It's such a pain to copy console.log to paste.
https://www.dropbox.com/s/62zhgpxvjikxs3v/UnableToProcess_Checkbox.swf?dl=0

I have following code in coffeescript to print out the issue
form_object = @$('form').serializeObject()
console.log(@$('form'))
console.log(form_object)
the form shows checked=checked value
however, the from_object does not set enable=true
Here is the video I captured from chrome console. It's such a pain to copy console.log to paste.
https://www.dropbox.com/s/62zhgpxvjikxs3v/UnableToProcess_Checkbox.swf?dl=0

I have following code in coffeescript to print out the issue
form_object = @$('form').serializeObject()
console.log(@$('form'))
console.log(form_object)
the form shows checked=checked value
however, the from_object does not set enable=true
Here is the video I captured from chrome console. It's such a pain to copy console.log to paste.
https://www.dropbox.com/s/62zhgpxvjikxs3v/UnableToProcess_Checkbox.swf?dl=0

:+1: it appears that this other package provides a default value for unchecked Checkboxes:
https://github.com/marioizquierdo/jquery.serializeJSON

Duplicate of #33

authors: macek rvarma1848 toobulkeh

repo: macek/jquery-serialize-object

license_source: bigquery


text:
adding initial code for StratifiedShuffleSplit

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
implementation for StratifiedShuffleSplit

There is a test failure due to the doc processor cannot handle certain type. Could you please take a look at it? Let me know if it's too hard.

sure will do

Also, could you make sure these things?

Export StratifiedShuffleSplit in index.ts (check model_selection/index.ts) so the users can actually use it
add an integration test
Please add unit tests to ensure 100% coverage and all the behaviours for this code
You need to add doc strings (check other APIs) so the doc processor can actually pick it up and generate documentation.

Also, could you make sure these things?
1. Export `StratifiedShuffleSplit` in `index.ts` (check model_selection/index.ts) so the users can actually use it

2. add an integration test

3. Please add unit tests to ensure 100% coverage and all the behaviours for this code

4. You need to add doc strings (check other APIs) so the doc processor can actually pick it up and generate documentation.

fixed

@JasonShin  please review this

source: gharchive/pull-request

authors: JasonShin VariableVasasMT

repo: machinelearnjs/machinelearnjs


text:
Angular 6 SEO in legacy J2EE Apps - Suggestions are appreciated

I'm submitting a...

[ ] Bug report
[ ] Feature request
[x ] Documentation issue or request

In package

[x ] @ng-toolkit/init
[ ] @ng-toolkit/serverless
[ ] @ng-toolkit/universal
[ ] @ng-toolkit/pwa
[ ] @ng-toolkit/firebug

Current behavior

Hi, Thank you very much for this toolkit, it works amazing and providing SEO benefits for Angular apps for newly built apps or the Angular only apps. We have situation where we had homegrown Application build with J2EE and we are migrating to Angular on UI side but based on how its designed we cant convert the entire app as Angular so we are using hybrid approach which is main JSPs are bundled with Angular Apps. Its working great from the feature perspective. We are generating the /dist folder from angular app and copying the the resources of legacy ui/js code base, however we lost the SEO as we don't use NODE/ Express in the PROD run time.  Can you recommend some options to achieve SEO here without writing entire UI layer in Angular at a time. Thanks a lot !!
Expected behavior

Minimal reproduction of the problem with instructions

Example repository

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z

- Node version: XX
- Platform:

Others:

Hello @swamytalam,
Even though the Angular documentation states at Universal Web Server section:

Any web server technology can serve a Universal app as long as it can call Universal's renderModuleFactory() function. The principles and decision points discussed here apply to any web server technology.

The reality is that we depend on Angular Universal and its core features to support SEO. So far, looks like it is only supported on NodeJS/Express and ASP.NET as you can check at the official repo.
But don't panic! The Angular Universal team is working on bringing this feature for different  languages as seen in this issue

authors: KingDarBoja swamytalam

repo: maciejtreder/ng-toolkit


text:
lambda.js

I'm submitting a...

[x] Bug report
[ ] Feature request
[ ] Documentation issue or request

In package

[ ] @ng-toolkit/init
[x] @ng-toolkit/serverless
[ ] @ng-toolkit/universal
[ ] @ng-toolkit/pwa
[ ] @ng-toolkit/firebug

Current behavior

Minimal reproduction of the problem with instructions
ng add @ng-toolkit/serverless --provider aws
ERROR: Path "/lambda.js" does not exist.
Environment

Angular CLI: 7.1.2
Angular: 6.1.10

- Node version: v8.11.3
- Platform: Mac
- OS: darwin x64

Others:
Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.8
@angular-devkit/build-angular     0.6.8
@angular-devkit/build-optimizer   0.6.8
@angular-devkit/core              0.6.8
@angular-devkit/schematics        7.1.2
@angular/cdk                      7.1.1
@angular/cli                      7.1.2
@angular/fire                     5.1.1
@angular/material                 7.1.1
@ngtools/webpack                  6.0.8
@schematics/angular               7.1.2
@schematics/update                0.11.2
rxjs                              6.3.3
typescript                        2.7.2
webpack                           4.8.3

Facing the same issue when trying to migrate from an already created universal project

Closed for housekeeping reasons.
A new version will arrive soon which should fix these issues.

authors: KingDarBoja macorifice mc-lovin


text:
Simulation-based calibration with Variational Inference

Hello,
I am encountering an error when trying to apply simulation-based calibration with a Variational Inference posterior: VIPosterior (I tried MCMCPosterior and it runs fine).
The error occurs when I call the function run_sbc:
AttributeError: The variational posterior was not fit on the specified `default_x` tensor([[...]]). Please train using `posterior.train()`.

To help diagnose the issue, I have prepared a minimal code example that reproduces the error:
import torch
from sbi import analysis as analysis
from sbi import utils as utils
from sbi.analysis import run_sbc
from sbi.inference import (SNLE, VIPosterior,
                           likelihood_estimator_based_potential,
                           prepare_for_sbi, simulate_for_sbi)

num_dim = 3
prior = utils.BoxUniform(low=-2 * torch.ones(num_dim), high=2 * torch.ones(num_dim))

len_x_o = 10
x_o = torch.zeros(len_x_o, num_dim,)+ 0.01*torch.randn(len_x_o, num_dim,)

def linear_gaussian(theta):
    return theta + 1.0 + torch.randn_like(theta) * 0.1

simulator, prior = prepare_for_sbi(linear_gaussian, prior)
inference = SNLE(prior=prior, density_estimator="nsf")
theta, x = simulate_for_sbi(simulator, prior, num_simulations=200)

likelihood_estimator = inference.append_simulations(theta, x).train(show_train_summary=True)
potential_fn, parameter_transform = likelihood_estimator_based_potential(likelihood_estimator, prior, x_o)
posterior = VIPosterior(potential_fn=potential_fn, prior=prior, theta_transform=parameter_transform)
posterior.train()
posterior = posterior.set_default_x(x_o)

thetas = prior.sample((1_000,))
xs = simulator(thetas)

ranks, dap_samples = run_sbc(
    thetas, xs, posterior, num_posterior_samples=1_000
)

I suspect that the reason for this error is due to the posterior not being trained after the introduction of each new vector in the simulated dataset xs.

Hello @hdahmou, thanks for creating this issue. Indeed, this seems to be a bug: the run_sbc method should call posterior.train() for each new "xi in xs".
I will make a PR with a fix soon!

authors: hdahmou janfb

repo: mackelab/sbi


text:
support metadata plugins in configuration

We plan to add metadata plugin feature in agent. This pull request adds support for read the configuration of metadata plugins from the config file.

LGTM

authors: Songmu itchyny

repo: mackerelio/mackerel-agent


text:
Homebrew bottle fails to build on Mojave

When trying to update the homebrew version of Macvim to snapshot 159, the bottle fails to build on Mojave, see Homebrew/homebrew-core#45455. There seems to be a Ruby mismatch.
The problem becomes apparent when running brew test macvim. The output shows that macvim --version has no Ruby support (-ruby) although Mac OS X Mojave ships with Ruby 2.3: see https://jenkins.brew.sh/job/Homebrew Core Pull Requests/50000/version=mojave/testReport/brew-test-bot/mojave/test_macvim/
Most likely, there is a problem with the way Homebrew tries to build the bottle. So probably a Homebrew problem and no Macvim problem. However, I hope that some Macvim developers care about this problem as many users use Macvim through Homebrew. Hopefully, we could shed some light on the build failure.
It seems that there are two possible solutions to this problem.
Either we could ignore the problem and remove Ruby support from the Mojave bottle. I don't know how many users actually rely on Ruby support... On the other hand, I think that Apple plans to stop shipping Ruby with OS X so we might need to do this in the future anyway.
The other option would be to solve the Homebrew problem, which seems to be the superior solution at this point. However, I have no clue how to do this since the problem does not seem to occur on a local computer.
I am not a very experienced user but I love the work you guys have done with Macvim. Therefore, I would very much like to help to solve this problem. I might be interpreting this problem completely wrong, so don't hesitate to tell me and point me in the right direction. Basically, any help would very much be appreciated.

@mvcouwen Thank you for an issue,
Reading the log and formula, configure script of ViM (MacVim is only GUI) haven't found library or it was incompatible for some reason. Formula explicitly checks that ruby was included into the build.
You could try to build it manually by yourself and provide full build logs to discover what really happened.

Returning to #952, it looks only for Ruby 2.6 shipped with Catalina. Alternatively, you could build with ruby/dyn (or download an official GitHub build), install Ruby 2.6 and try to use it.

@eirnym Thanks for the help! Are you suggesting to make the Macvim formula dependent on ruby? And then use homebrew ruby to build Macvim?
On the other hand, I have read somewhere that deleting SDKROOT (as done in the formula for Sierra and Yosemite) might solve the mismatch. Is this worth trying?

Could you try the build from GitHub if it works for you?
please, try to build MacVim manually explicitly providing ruby paths for configure script, such as --with-ruby-command as per documentation for configure script.

BTW, I don't know why the formula for MacVim is different with formula for vim

Solved by PR Homebrew/homebrew-core#45624.

authors: eirnym mvcouwen

repo: macvim-dev/macvim

license: Vim


text:
K33 version

Now plots create as K33 data.

I thought this was supposed to be a massive amount of work ,instead of changing just 1 code line?

@madMAx43v3r surely it cannot be this easy?

@madMAx43v3r surely it cannot be this easy?

I feel like this is some kind of joke because they removed all the instructions

just testing it now........
I think it is bull.....
there is no difference it plotting time......
plus i don't see the code "auto adapting" to a larger array, basically it's just a bigger array
then not utilized.

well if it is a "joke" its gonna be on him... by the time i have finished with him

@madMAx43v3r surely it cannot be this easy?

I feel like this is some kind of joke because they removed all the instructions

well if it is a "joke" its gonna be on him... by the time i have finished with him

just testing it now........
I think it is bull.....
there is no difference it plotting time......
plus i don't see the code "auto adapting" to a larger array, basically it's just a bigger array
then not utilized.
nope file is exactly the same size & same processing time.
108,821,664,318 bytes (108.82 GB on disk)

the plot checker reports it as size 32

Yep exactly as expected

lol that's not how it works, the seed is always 32 bytes, k is something totally different

authors: Hardcore-fs SNGDude VertiHydro madMAx43v3r


text:
Add filters

It would be nice to have filtering options, on reactweb and react-native like most downloaded or new

Hello Yesid, thank you for taking the time to submit this suggestion. It's definitely something that we want to add in the near future :+1: Thanks!

Hello @yeso126, we are working on a new catalog that adds both sorting and filtering capabilities. We are beta testing now and it's available here: https://js.coach
Thank you again for your feedback :+1:

repo: madebyform/react-parts


text:
Error 404 on Recipe#fork

http://raspberry-cook.fr/recipes/fork?id=86

corrected in 1.5.2


text:
Non Fungible tokens transfers not showing correctly on Ithacanet, and when manually adding they show in Fungible token section

I've been debugging an issue with my new token for 2 days now and I believe I've found a bug in Temple when on Ithacanet
To reproduce this I created a minimal contract that demonstrates the issue. If you deploy the contract on Mainnet and Ithacanet and follow the instructions you will be able to see the problem.
I have already deployed this contract on both networks:
✅  - Mainnet (Works as Expected) - KT1GXMnnNv3pYJE7u3E48vhqZsWHpVDZMBSy - BCD Link
❌  - Ithacanet (Fails) - KT1NMwUAPcbk6cv5DC9HpkTkYGR3sMqDS3dC - BCD Link
The entrypoint you must call is mint and you must pass in a single valid ipfs CID in plain string format without the ipfs:// prefix
The CID must be a valid TZIP-21 compatible JSON metadata file.
The example that I used is at ipfs CID QmR5jRRrfRPen6Tzvs242wSRR8829W1WzWDmsrZSLTo13H - to reproduce the issue you can call the endpoint with this value (full contents included at bottom of report) - example metadata ipfs.io link
Expected Result
"+1 TOKEN" in the 'Activity' tab and the token showing in the 'Collectibles' tab

Actual Result
Nothing is shown on 'Activity' tab, and nothing shows in the 'Collectibles' tab

Manually Adding Asset
If you manually add the collectible contract and token id the token displays on the 'Tokens' tab instead of the 'Collectibles' tab

Notes
This is the exact same code and metadata, just deployed on 2 different networks.
This is the Bare Bones FA2 Contract in SmartPy that was deployed to both networks.
Metadata used in this example
{
  "artifactUri": "ipfs://QmdUh6xSMcjGtUwmk2d7GktAsmXYyA2WQTjiktFbD6dAWm",
  "attributes": [
    {
      "name": "Artifact",
      "value": "Token"
    },
    {
      "name": "Status",
      "value": "Generic"
    }
  ],
  "creators": [
    "tz1ZWje5jpfbWrG5iuxz7qUx7eBLLAS5Tv3z"
  ],
  "decimals":0,
  "description":"Generic FA2 Example Token",
  "displayUri": "ipfs://QmfKF2fkZRGnEhH3E8C6dadjb1vHGffErHQfpv5AonhvCy",
  "formats": [
    {
      "dimensions": {
        "value": "2500x2500",
        "unit": "px"
      },
      "mimeType": "image/png",
      "uri": "ipfs://QmdUh6xSMcjGtUwmk2d7GktAsmXYyA2WQTjiktFbD6dAWm"
    },
    {
      "dimensions": {
        "value": "1000x1000",
        "unit": "px"
      },
      "mimeType": "image/png",
      "uri": "ipfs://QmfKF2fkZRGnEhH3E8C6dadjb1vHGffErHQfpv5AonhvCy"
    },
    {
      "dimensions": {
        "value": "350x350",
        "unit": "px"
      },
      "mimeType": "image/png",
      "uri": "ipfs://QmTKS7C1J1pCtAeUtG5DbEgCr1NLQ7dZwnhMi4QwrjxcJY"
    }
  ],
  "identifier":"TOKEN",
  "isBooleanAmount": true,
  "minter": "tz1ZWje5jpfbWrG5iuxz7qUx7eBLLAS5Tv3z",
  "name":"Generic FA2 Token",
  "publishers": [
    "tz1ZWje5jpfbWrG5iuxz7qUx7eBLLAS5Tv3z"
  ],
  "rights": "(c) 2022 0x10. All rights reserved.",
  "royalties": {
    "decimals": 6,
    "shares": {
      "tz1ZWje5jpfbWrG5iuxz7qUx7eBLLAS5Tv3z": "100000"
    }
  },
  "shouldPreferSymbol": true,
  "symbol":"TOKEN",
  "thumbnailUri":"ipfs://QmTKS7C1J1pCtAeUtG5DbEgCr1NLQ7dZwnhMi4QwrjxcJY",
  "type": "Generic Token",
  "isTransferable": true,
  "burnable": true,
  "tags": ["0x10", "example", "fa2", "token"],
  "language": "en"
}

I see that this issue has been marked as resolved but I'm still experiencing this bug
is it still awaiting release?

@letier3110 do you have any updates on my question above?
is this still not working in production?

This same issue is now happening when switching to Jakarta


text:
[FEATURE] Specify HTML title on command line

This is a pretty simple request and I'm happy to submit a PR for it but wanted to talk to you about how best to go about it.
I would like to be able to specify the title used in HTML output from the command line. I'm currently going through a lot of projects trying to find dependencies and sometimes end up with multiple DependenSee HTML browser windows open and it would be helpful to be able to tell them apart more easily.
An option could be added such as -HT or -HtmlTitle where it defaults to "DependenSee" (current behavior) if not specified. The option could be ignored for mismatched output types, a warning displayed but output still generated, or an error + abort triggered.
My approach would be to add new constants in ResultWriter.cs for HtmlTitleToken and HtmlTitleDefault and then make the necessary updates in PowerArgsProgram.cs, Program.cs, ResultWriter.Write, and ResultWriter.WriteAsHtmlToFile to support passing the value through and applying it. The value would be appropriately escaped before being injected into the HTML output.
I also considered using something like AngleSharp to make the update since it's HTML but that seems like overkill as long as the value is being escaped properly.
I don't intend to modify XML, JSON, or GraphViz output as I am less familiar with their use cases and wouldn't want to make changes that could break anyone else's workflow.
I look forward to hearing your thoughts on this.

Yep this sounds good.
Escaping can be done with WebUtility.HtmlEncode.
Can ignore the option if the -OutputType is not HTML . This is consistent with  -OutputPath which is ignored when the -OutputType is a Console output.
May be we should look into treating each output type as a sub command, but that would break backwards compatibility, so I can think about doing that later separately.
If you're happy to do a PR, I look forward to it. Otherwise I can implement it, though it may take a few weeks for me to find the time.
If you're doing a PR, please branch from dev and also update the version number here to increment the minor version.

Sounds good. I'll start on it and should have a PR for you either today or tomorrow.

Your changes are now available on Nuget.
Thanks you for your contribution and thank you again for using DependenSee ♥

repo: madushans/DependenSee


text:
[IMPAC-639] Threshold currency

Replaces #413

Replaced by https://github.com/maestrano/impac-angular/pull/514 (which rebases these changes on-top of 1.7)

authors: cesar-tonnoir xaun

repo: maestrano/impac-angular


text:
Issue report

Im trying to dump a game from microsoft store
Game name: (please, specify the game name)
Engine version: (specify engine version, if known)
Platform: (specify platform, if known)
Error message: Some data left
Stack trace:    at uTinyRipper.Lz4.Lz4DecodeStream.ReadBuffer(Stream stream, Int64 count)
at uTinyRipper.BundleFileScheme.ReadFileStreamMetadata(Stream stream, Int64 basePosition)
at uTinyRipper.BundleFileScheme.ReadScheme(Stream stream)
at uTinyRipper.GameCollection.ReadScheme(SmartStream stream, String filePath, String fileName)
at uTinyRipper.GameCollection.LoadScheme(String filePath, String fileName)
at uTinyRipper.GameStructure.ProcessPlatformStructure(GameStructureProcessor processor, PlatformGameStructure structure)
at uTinyRipper.GameStructure.Load(List1 pathes, LayoutInfo layinfo)    at uTinyRipper.GameStructure.Load(IEnumerable1 pathes, LayoutInfo layinfo)
at uTinyRipperGUI.MainWindow.LoadFiles(Object data)

No promises, but you can try my AssetRipper fork.

repo: mafaca/UtinyRipper


text:
muichiro and kanae problem

Game name: (please, specify the game name)
Engine version: (specify engine version, if known)
Platform: (specify platform, if known)
Error message: Some data left
Stack trace:    at uTinyRipper.Lz4.Lz4DecodeStream.ReadBuffer(Stream stream, Int64 count)
at uTinyRipper.BundleFileScheme.ReadFileStreamMetadata(Stream stream, Int64 basePosition)
at uTinyRipper.BundleFileScheme.ReadScheme(Stream stream)
at uTinyRipper.GameCollection.ReadScheme(SmartStream stream, String filePath, String fileName)
at uTinyRipper.GameCollection.LoadScheme(String filePath, String fileName)
at uTinyRipper.GameStructure.ProcessPlatformStructure(GameStructureProcessor processor, PlatformGameStructure structure)
at uTinyRipper.GameStructure.Load(List1 pathes, LayoutInfo layinfo)    at uTinyRipper.GameStructure.Load(IEnumerable1 pathes, LayoutInfo layinfo)
at uTinyRipperGUI.MainWindow.LoadFiles(Object data)
Game name: (please, specify the game name)
Engine version: (specify engine version, if known)
Platform: (specify platform, if known)
Error message: Some data left
Stack trace:    at uTinyRipper.Lz4.Lz4DecodeStream.ReadBuffer(Stream stream, Int64 count)
at uTinyRipper.BundleFileScheme.ReadFileStreamMetadata(Stream stream, Int64 basePosition)
at uTinyRipper.BundleFileScheme.ReadScheme(Stream stream)
at uTinyRipper.GameCollection.ReadScheme(SmartStream stream, String filePath, String fileName)
at uTinyRipper.GameCollection.LoadScheme(String filePath, String fileName)
at uTinyRipper.GameStructure.ProcessPlatformStructure(GameStructureProcessor processor, PlatformGameStructure structure)
at uTinyRipper.GameStructure.Load(List1 pathes, LayoutInfo layinfo)    at uTinyRipper.GameStructure.Load(IEnumerable1 pathes, LayoutInfo layinfo)
at uTinyRipperGUI.MainWindow.LoadFiles(Object data)

uTinyRipper has been abandoned, but you can try my AssetRipper fork. In the event that AssetRipper encounters issues while ripping your files, feel free to post an issue on that repository.
AssetRipper is actively being developed with the intent to recover games as best as possible. Weekly releases are normally on Sunday or Monday. I encourage you to help out if you're able and willing. Code contributions can be submitted via pull requests.
If you like the work I've done and want to see it continue, please consider sponsoring me. It really does help with development. These are some of the notable things I've implemented since taking over development:

2020+ support
APK, XAPK, and IPA reading with SharpZipLib
Dummy shaders (so everything isn't pink when you open the project)
IL2Cpp support via an integration of Cpp2IL
Better game platform support
Full script decompilation with the ILSpy decompiler
Cross-platform support
Multiple configuration options
Numerous performance improvements
Support for all asset types

Sponsorship Links:

GitHub Sponsors
Patreon
Paypal


text:
Enable queries

Let the user query for an aggregate answer such as:
3d8 gt 10  # What is the chance of 3d8 > 10
2d8 le 10  # What is the chance of 2d8 <= 10

Actually, the user should specify an aggregation mode.
So if 1d4 produces 4 25%, 1d4 gt should produce 75%, 50%, 25%, 0% (the chances of being > 1, > 2, > 3, and > 4).
The same should work for lt, le, eq (the default mode), and ge.
Lastly, the last number is another query component. So the user can query as specified in my first comment by selecting one result.

Partially done.
We are still missing the option of not providing a third value (2d8 < instead of 2d8 < 6).

repo: mafagafogigante/dicestats


text:
flaky reconnect

sometimes reconnect doesn't work if a peer is offline for more than the RETRIES array allow.

I think this may be related to a problem I have identified.
(While in sync mode): When a peer gets dropped for some reason it is not possible to reconnect because it gets caught as "duplicated". Unless we stop the process and start a new one or the peer changes its id (uses a different port, for example).
I think I have found the cause of this issue. I will submit a pull request.

authors: fejnartal mafintosh

repo: mafintosh/discovery-swarm

license: mit


text:
Handle edge cases in 'authorized'

always recognize the original db author as authorized
recognize others as authorized when the only head is by the author in question

forgot to standard!

repo: mafintosh/hyperdb


text:
Add dry-run packages check on release branch

Is your feature request related to a problem? Please describe.
Check that packages are correct and can be built correctly before creating a release
Describe the solution you'd like
Add a workflow for dry-run checking packages on release branch

Completed in #16

repo: magicblock-labs/bolt


text:
Bump Version of @magic-sdk/connect to 6.2.0, Again

📦 Pull Request
Bump Version of @magic-sdk/connect to 6.2.0
✅ Fixed Issues

[List any fixed issues here like: Fixes #XXXX]

🚨 Test instructions
[Describe any additional context required to test the PR/feature/bug fix.]
⚠ Don't forget to add a semver label!

patch: Bug Fix?
minor: New Feature?
major: Breaking Change?
skip-release: It's unnecessary to publish this change.

:rocket: PR was released in @magic-ext/connect@6.2.0, @magic-ext/react-native-bare-oauth@8.1.0, @magic-ext/react-native-expo-oauth@8.1.0, @magic-sdk/react-native-bare@14.1.0, @magic-sdk/react-native-expo@14.1.0 :rocket:

authors: Ariflo magiclabsFE

repo: magiclabs/magic-js


text:
Update logo asset

📦 Pull Request
[Provide a general summary of the pull request here.]
✅ Fixed Issues

[List any fixed issues here like: Fixes #XXXX]

🚨 Test instructions
[Describe any additional context required to test the PR/feature/bug fix.]
⚠ Don't forget to add a semver label!
Please only add one label:

patch: Bug Fix?
minor: New Feature?
major: Breaking Change?
skip-release: It's unnecessary to publish this change.

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install @magic-ext/oauth@11.1.3-canary.504.4801941131.0
npm install @magic-sdk/pnp@11.1.3-canary.504.4801941131.0
npm install magic-sdk@17.1.3-canary.504.4801941131.0
# or
yarn add @magic-ext/oauth@11.1.3-canary.504.4801941131.0
yarn add @magic-sdk/pnp@11.1.3-canary.504.4801941131.0
yarn add magic-sdk@17.1.3-canary.504.4801941131.0

:rocket: PR was released in @magic-ext/oauth@11.1.3, @magic-sdk/pnp@11.1.3, magic-sdk@17.1.3 :rocket:

authors: Dizigen magiclabsFE


text:
Running Installer - Vite Compatibility Issue

I'm trying to install maglev by running:
bundle exec rails g maglev:install
However, that throws the following error:
/Users/XXXX/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/vite_ruby-3.3.4/lib/vite_ruby/compatibility_check.rb:24:in raise_unless_satisfied': vite-plugin-ruby@^3.1.2 might not be compatible with vite_ruby-3.3.4 (ArgumentError)

hey @rfrisch43 👋 Which version of Maglev are you using? The 1.2.1 version should point to a recent version of vite-plugin-ruby.

@did I was following the instructions here: https://docs.maglev.dev/quickstart
So it was pinned to 1.1.3
Updating to 1.2.1 did solved the install issue but now I'm having other issues.
Nothing is rendered when visiting http://localhost:3000/ and http://localhost:3000/maglev/editor/en/index is erroring:
2023-07-30 20:06:23 -0400 Read: #<TypeError: no implicit conversion of Symbol into String>
I'm going to try a fresh install but do you offer install guidance and if so where is the best place reach out?
Thanks!

@rfrisch43 alright, the documentation wasn't up to date. I've fixed it. Thanks a lot!
Regarding your other issue, it's related to Puma and the Vite Rack middleware. The solution is quite simple, juste upgrade Puma to the 6.x version.

Perfect, that fixed it, Thanks!

I'm trying to install maglev by running:
bundle exec rails g maglev:install
However, that throws the following error:
/Users/XXXX/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/vite_ruby-3.3.4/lib/vite_ruby/compatibility_check.rb:24:in raise_unless_satisfied': vite-plugin-ruby@^3.1.2 might not be compatible with vite_ruby-3.3.4 (ArgumentError)

I'm seeing this same error on 1.7.2

/Users/XXXX/.asdf/installs/ruby/3.1.2/lib/ruby/gems/3.1.0/gems/vite_ruby-3.8.2/lib/vite_ruby/compatibility_check.rb:24:in `raise_unless_satisfied': vite-plugin-ruby@^5.0.0 might not be compatible with vite_ruby-3.8.2 (ArgumentError)

authors: brentdodell did rfrisch43

repo: maglevhq/maglev-core


text:
VGA log are displaying VAMP GATEWAY AGENT: katana string

needs to be the correct version, not hardcoded

closing this as it's fixed

repo: magneticio/vamp-gateway-agent


text:
Can't create reports under https

Hi,
I'm using grafana in front of haproxy under https. I have an error "error generating report" when i try to generate a report.
The url used is : https://<Server>/api/plugins/mahendrapaipuri-dashboardreporter-app/resources/report?dashUid=jLdsyDbWz&from=now-1M%2FM&to=now-1M%2FM&var-datasource=000000001&var-zone=xxx

grafana log file :

logger=http.server t=2024-03-28T09:14:48.55601014+01:00 level=info msg="HTTP Server Listen" address=0.0.0.0:3000 protocol=https subUrl= socket= logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-03-28T09:17:18.303597619+01:00 level=info msg="chrome executable provided by grafana-image-renderer will be used" pluginID=mahendrapaipuri-dashboardreporter-app chrome=/var/lib/grafana/plugins/grafana-image-renderer/chrome/linux-124.0.6351.0/chrome-linux64/chrome endpoint=callResource logger=plugin.mahendrapaipuri-dashboardreporter-app t=2024-03-28T09:17:18.344329972+01:00 level=error msg="error generating report" endpoint=callResource err="error fetching dashboard iLdsyDbWz: error executing request for https://localhost:3000/api/dashboards/uid/jLdsyDbWz?var-datasource=000000001&var-zone=xxx: Get \"https://localhost:3000/api/dashboards/uid/jLdsyDbWz?var-datasource=000000001&var-zone=xxx\": tls: failed to verify certificate: x509: certificate relies on legacy Common Name field, use SANs instead" pluginID=mahendrapaipuri-dashboardreporter-app logger=context userId=1 orgId=1 uname=admin t=2024-03-28T09:17:18.345307952+01:00 level=error msg="Request Completed" method=GET path=/api/plugins/mahendrapaipuri-dashboardreporter-app/resources/report status=500 remote_addr=X.X.X.X time_ms=54 duration=54.222984ms size=24 referer= handler=/api/plugins/:pluginId/resources/* status_source=downstream
Is there a way to disable certificate verify like in grafana-reporter with option ssl-check=false ?
grafana open source:  10.4.1
grafana-image-renderer : 3.10.1
OS : Ubuntu 22.04.4

As I understand, you are running Grafana instance with TLS enabled.
At the moment, no, there is no way to skip TLS verify but this should be easy to implement and it is a valid use case. We can add another configurable option which can be set either by provisioning or using Grafana UI to allow skipping TLS verify.
I should be able to add this feature and make a new release next week. Cheers for reporting this bug.

Thank you.
Waiting for next release to test it.
Regards

Hello @Alan1810 , could you please try this patch? You can download the plugin artifacts from CI artifacts. You will need to set skipTlsCheck to true in the plugin provisioning config file.

Hello @mahendrapaipuri,
I don't an environment to compile and no direct access to internet. Is there a way to have a release ?
Best regards

@Alan1810 Alright, here is the nighly release. Would you be able to test with this? Cheers

Hi @mahendrapaipuri,
The nightly release works fine. Thank you for your works.
Is there a way to modify the output ? For example, the number of page is present at the bottom of each page and in the dashboard title.
Best regards

Cheers @Alan1810 for testing it out.
Could you please open a new issue about the output customization? I will close this one as the PR has been merged.


text:
onSuggestionTap not giving back the value  null value always

I am using this package to show the dynamic list of object but it's just setting the value in the controller i didnot get back the suggestion tapped value onSuggestionCall give null value always
To Reproduce
Expected behavior
A clear and concise description of what you expected to happen.
Actual behavior
What you actually saw instead of the expected behavior.
Screenshots
If applicable, add screenshots to help explain your problem.
Code sample

Show code sample
class LocationSearchAbleTextField extends StatelessWidget {
  final TextEditingController controller;
  final Function(dynamic val) onSuggestionItemTap;
  final List<dynamic> suggestionList;
  final String hintText;
  VoidCallback? onTralingTap;
  String? initialValue;
  String? searchLabel;
  String? errorText;
  bool? showTraling;
  bool? isForm = false;
  double? itemHeight;
  String? Function(String?)? validator;
  Function(String?)? onSave;

  LocationSearchAbleTextField(
      {super.key,
      required this.controller,
      required this.onSuggestionItemTap,
      required this.suggestionList,
      this.onSave,
      this.isForm = false,
      this.initialValue,
      this.showTraling = true,
      this.validator,
      this.itemHeight,
      this.errorText,
      this.searchLabel,
      this.onTralingTap,
      required this.hintText});

  @override
  Widget build(BuildContext context) {
    ListingVm listingVm = Provider.of<ListingVm>(context, listen: false);
    final focus = FocusNode();
    return Center(
      child: SearchField(
        controller: controller,
        initialValue:
            initialValue != null && suggestionList.contains(initialValue)
                ? SearchFieldListItem<String>(initialValue!)
                : null,
        onSubmit: onSave,
        validator: validator,
        onSearchTextChanged: (query) {
          isForm!
              ? listingVm.getFormLocationList(query: query)
              : listingVm.getFilterLocationList(query: query);
          final filter = suggestionList
              .where((element) => searchLabel != null
                  ? element.fullName.toLowerCase().contains(query.toLowerCase())
                  : element.name!.toLowerCase().contains(query.toLowerCase()))
              .toList();
          return filter
              .map((e) => SearchFieldListItem<String>(
                  searchLabel != null ? e.fullName : e.name!,
                  child: Padding(
                    padding: const EdgeInsets.symmetric(
                        vertical: 4.0, horizontal: 5.0),
                    child: Text(searchLabel != null ? e.fullName : e.name!,
                        style: AppStyle.lightDarkTextStyle.copyWith(
                            fontSize: 1.8.h, fontWeight: FontWeight.normal)),
                  )))
              .toList();
        },
        key: const Key('searchfield'),
        hint: hintText,
        itemHeight: itemHeight ?? 6.h,
        autoCorrect: false,
        searchInputDecoration: InputDecoration(
          filled: true,
          errorText: errorText,
          contentPadding:
              const EdgeInsets.symmetric(vertical: 0, horizontal: 10),
          fillColor: AppColors.kScaffoldBackgroundColor,
          border: OutlineInputBorder(
            borderRadius: BorderRadius.circular(15.0),
            borderSide: BorderSide.none,
          ),
          suffix: showTraling!
              ? InkWell(
                  onTap: onTralingTap ??
                      () async {
                        controller.clear();
                      },
                  child: Icon(
                    Icons.clear,
                    color: Colors.black,
                    size: 2.4.h,
                  ))
              : null,
          hintStyle: TextStyle(
            color: AppColors.kBlackLightColor,
            fontSize: 2.h,
          ),
          hintText: hintText,
        ),
        suggestionsDecoration: suggestionDecoration,
        scrollbarAlwaysVisible: false,
        maxSuggestionsInViewPort: 5,

        ///line color between suggestion..
        // marginColor: ,
        suggestions: suggestionList
            .map((e) => SearchFieldListItem<String>(
                searchLabel != null ? e.fullName : e.name!,
                child: Padding(
                  padding: const EdgeInsets.symmetric(
                      vertical: 4.0, horizontal: 4.0),
                  child: Text(searchLabel != null ? e.fullName : e.name!,
                      style: AppStyle.lightDarkTextStyle.copyWith(
                          fontSize: 1.8.h, fontWeight: FontWeight.normal)),
                )))
            .toList(),
        focusNode: focus,
        suggestionState: Suggestion.expand,
        onSuggestionTap: (SearchFieldListItem<String> x) {
          focus.unfocus();
          onSuggestionItemTap(controller.text);
        },
      ),
    );
  }

  final suggestionDecoration = SuggestionDecoration(
    shape: BoxShape.rectangle,
    boxShadow: const [
      BoxShadow(
        color: AppColors.kScaffoldBackgroundColor,
        blurRadius: 2.0,
        spreadRadius: 0.0,
        offset: Offset(0.0, 0.0),
      )
    ],
    padding: const EdgeInsets.all(4),
    color: AppColors.kWhiteColor,
    // borderRadius: BorderRadius.all(Radius.circular(20)
    // )
  );

// final inputDec
}

Additional context
Add any other context about the problem here.

i need full object value  i tried to change the type from string to dynamic but nothing changed alwasy got null values

onSuggestionTap: (SearchFieldListItem selectedItem) {
print('i am here on suggestion tap...');
   print('selected item i got is ${selectedItem.item}');

    },

i got null value

Hi @WaseemAbbasi22, Thanks for filing the issue.
I see the issue in your code, you are not passing item parameters to SearchFieldListItem
return filter
              .map((e) => SearchFieldListItem<String>(
                  item: e,  // Pass the object you want to receive for the list item
                  searchLabel != null ? e.fullName : e.name!,
                  child: Padding(
                    padding: const EdgeInsets.symmetric(
                        vertical: 4.0, horizontal: 5.0),
                    child: Text(searchLabel != null ? e.fullName : e.name!,
                        style: AppStyle.lightDarkTextStyle.copyWith(
                            fontSize: 1.8.h, fontWeight: FontWeight.normal)),
                  )))
              .toList();

See this complete example for more details
https://github.com/maheshmnj/searchfield/blob/master/example/lib/country_search.dart
Additionally I have updated the doc comments a little bit to clarify this.

Let me know if you have any further questions.

Thanks alot i got the solution i just have one more query if i want to style the suggestions just like normal dropdown how can i acheive that

Thanks alot i got the point

repo: maheshmnj/searchfield


text:
More neat training

Hi, Mahmoud! I need to train the network for a specific task - there is one scene, but filmed from two angles. The problem is that there are cases where from one angle the colors in the scene are more saturated than from the other. Does it make sense to practice with reHistoGAN (Universal) or would it be more practical to look at white balance or exposure correction? Thanks in advance for the answer!

If the colors of two frames supposed to be similar, I guess you may use traditional color transfer methods — no need for deep learning. Also exposure adjustment is a potential solution.

If the colors of two frames supposed to be similar, I guess you may use traditional color transfer methods — no need for deep learning. Also exposure adjustment is a potential solution.

I've looked at a lot of engineering methods that would do color transfer locally throughout the frame, but unfortunately I haven't found anything that works

authors: Alexasandrovich mahmoudnafifi

repo: mahmoudnafifi/HistoGAN


text:
Error: "AppTrackingTransparency" plugin is not implemented on ios

Bug Report
Plugin version:
[ ] 1.x
[x] 2.0.3
Capacitor version:
[ ] 2.x
[] 3.x
[x] 4.0.1
Current behavior:
After I added this plugin and run app I have this exception in log
[error] - ERROR Error: Uncaught (in promise): Error: "AppTrackingTransparency" plugin is not implemented on ios te@capacitor://localhost/main.b7d4641eaa6e5c9d.js:1:10040 @capacitor://localhost/main.b7d4641eaa6e5c9d.js:1:11592 @capacitor://localhost/main.b7d4641eaa6e5c9d.js:1:11892 onInvoke@capacitor://localhost/main.b7d4641eaa6e5c9d.js:1:318462 @capacitor://localhost/polyfills.3ebd5e0cff18d293.js:1:2768 @capacitor://localhost/polyfills.3ebd5e0cff18d293.js:1:18559 onInvokeTask@capacitor://localhost/main.b7d4641eaa6e5c9d.js:1:318282 @capacitor://localhost/polyfills.3ebd5e0cff18d293.js:1:3437 A@capacitor://localhost/polyfills.3ebd5e0cff18d293.js:1:10761 @capacitor://localhost/polyfills.3ebd5e0cff18d293.js:1:9532
Expected behavior:
Plugin will work.
Steps to reproduce:
Add the plugin to app.
Related code:

Ionic info:
Ionic:
Ionic CLI                     : 6.20.1 (/usr/local/lib/node_modules/@ionic/cli)
Ionic Framework               : @ionic/angular 6.2.2
@angular-devkit/build-angular : 14.1.2
@angular-devkit/schematics    : 14.1.2
@angular/cli                  : 14.1.2
@ionic/angular-toolkit        : 6.1.0
Capacitor:
Capacitor CLI      : 4.0.1
@capacitor/android : 4.1.0
@capacitor/core    : 4.1.0
@capacitor/ios     : 4.1.0
Utility:
cordova-res                          : 0.15.4
native-run (update available: 1.7.0) : 1.6.0
System:
NodeJS : v16.16.0 (/usr/local/bin/node)
npm    : 8.17.0
OS     : macOS Monterey

Hi @nowitz please provide an example repository where the error is reproducible, as I am not able to.

Closing this for now as not reproducible.

authors: mahnuh nowitz


text:
TCP simultaneous connect while looping to bootstrap to a list of endpoints

Due to looping to connect to cached contacts, two client trying to connect to same local port (not listening & unoccupied) connect to each other. (TCP simultaneous connect)
Steps to reproduce:
1. Start first crust peer and close it once it starts listening.
prakash@machine:~/rust/maidsafe/crust (MAID-1136_new_bootstrap_event)$ cargo run --example crust_peer
   Compiling crust v0.1.5 (file:///home/prakash/rust/maidsafe/crust)
     Running `target/debug/examples/crust_peer`
Error reading Bootstrap file: Error { repr: Os { code: 2, message: "No such file or directory" } }. Creating "./crust_peer.bootstrap.cache".
Listening for new connections on Tcp(V4(127.0.0.1:45574)), Tcp(V4(192.168.0.10:45574)), Tcp(V6([::1]:45574)), Didn't bootstrap to an existing network - this may be the first node of a new network.
^C

Bootstrap cache will have listening endpoints added (currently unused)
prakash@machine:~/rust/maidsafe/crust (MAID-1136_new_bootstrap_event)$ cat crust_peer.bootstrap.cache
[
  {
    "endpoint": "127.0.0.1:45574"
  },
  {
    "endpoint": "192.168.0.10:45574"
  },
  {
    "endpoint": "[::1]:45574"
  }
]prakash@machine:~/rust/maidsafe/crust (MAID-1136_new_bootstrap_event)$

2. Start first crust peer again and it can be noticed that it bootstrapped with its previous listening port.

prakash@machine:~/rust/maidsafe/crust (MAID-1136_new_bootstrap_event)$ cargo run --example crust_peer
     Running `target/debug/examples/crust_peer`
Listening for new connections on Tcp(V4(127.0.0.1:37180)), Tcp(V4(192.168.0.10:37180)), Tcp(V6([::1]:37180)),
New BootstrapConnection to peer at Tcp(V4(192.168.0.10:45574))
1 connected node: Tcp(V4(192.168.0.10:45574))
Enter command (stop | connect <endpoint> | send <endpoint> <message>)>Bootstrapped to Tcp(V4(192.168.0.10:45574))
Got at least one bootstrap connection. Breaking bootstrap loop.

Enter command (stop | connect <endpoint> | send <endpoint> <message>)>

lsof output
 prakash@machine:~$ lsof  -i :45574
COMMAND     PID    USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
crust_pee 16100 prakash   11u  IPv4 1603649      0t0  TCP 192.168.0.10:45574->192.168.0.10:45574 (ESTABLISHED)
crust_pee 16100 prakash   13u  IPv4 1603649      0t0  TCP 192.168.0.10:45574->192.168.0.10:45574 (ESTABLISHED)

I coded a solution after reading about the tradeoffs from the several solutions. This solution is portable and works now.
@chandraprakash did most of the research when I started to work on the task, so it was easy & fast to pick up where he left.

authors: chandraprakash vinipsmaker

repo: maidsafe/crust


text:
crust_peer fails to stop

Not the first time it happens ( https://github.com/maidsafe/crust/issues/277 https://github.com/maidsafe/crust/issues/141 ).

It's working again. Not sure which commit fixed it, but must have been work from @inetic.

It's failing again.
How to reproduce

Open a single crust_peer instance.

Do not connect to any other node. You may see:
    Running `target/debug/examples/crust_peer`
    Listening on ports Tcp(V4(0.0.0.0:5483))
    Enter command (stop | connect <endpoint> | send <endpoint> <message>)>

You might also see:
  Didn't bootstrap to an existing network - this may be the first node of a new network.

Enter stop.
crust_peer doesn't stop.

A hint to solve this issue. The hanged/hanging crust_peer instance will gracefully stop if you, now, start another crust_peer instance that will automatically connect (through beacon) to the previous instance. This second instance won't have any trouble execute the stop command.

Fixed here https://github.com/maidsafe/crust/commit/20965f1f6eeaf178572964dba854f97058730677

authors: inetic vinipsmaker


text:
Fix crust tmp

This change is

r? @canndrew
(maidsafe_highfive has picked a reviewer for you, use r? to override)

r? @Viv-Rajkumar

r? @afck

Reviewed 5 of 5 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

authors: afck maidsafe-highfive ustulation


text:
New cursor

With canvas you should be able to create & use a custom cursor. At the moment I think that the "pointer" cursor is pretty ugly and is taking too much place while making pixel art. The cursor should be a pencil or something thin like this.

That's a good point, could you search for some free available icon sets I can add to here?

Sure, something like this : https://www.iconfinder.com/icons/1167983/draw_drawing_edit_pen_pencil_write_writing_icon#size=128

Added with https://github.com/maierfelix/poxi/commit/7e5be8475d2d2fb2f3ecf36aed485bdc205a49f3

repo: maierfelix/poxi


text:
ask for help

thanks for inventing this good software
I have a question. When fitting Wannier, do we only require that the localization of magnetic atoms is good?
waiting for your answer

No. Usually we need not only the orbitals of the magnetic atoms, but also these hybridize with them. For example, in FeO, the Fe d orbitals and the O p orbitals are needed.
Best regards,
HeXu

authors: YJNDL mailhexu


text:
MF-1640 - Create tests for mqtt pubsub

Signed-off-by: aryan aryangodara03@gmail.com
What does this do?
Adds tests for the mqtt implementation of pkg/messaging
Which issue(s) does this PR fix/relate to?
Resolves #1640
List any changes that modify/break current functionality
Nil
Have you included tests for your changes?
Yes
Did you document any new/modified functionality?
Nil
Notes
N/A

Codecov Report

Merging #1643 (29241cd) into master (d9c4704) will decrease coverage by 0.78%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1643      +/-   ##
==========================================
- Coverage   68.96%   68.18%   -0.79%
==========================================
  Files         138      140       +2
  Lines       11350    11481     +131
==========================================
  Hits         7828     7828
- Misses       2828     2959     +131
  Partials      694      694

Impacted Files
Coverage Δ

pkg/messaging/mqtt/publisher.go
0.00% <0.00%> (ø)

pkg/messaging/mqtt/pubsub.go
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Please fix CI.

@0x6f736f646f if this is OK now, please approve

authors: AryanGodara codecov-commenter dborovcanin drasko

repo: mainflux/mainflux


text:
[Snyk] Upgrade typeorm from 0.2.24 to 0.3.20

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade typeorm from 0.2.24 to 0.3.20.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 526 versions ahead of your current version.
The recommended version was released 3 months ago, on 2024-01-26.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Prototype Pollution SNYK-JS-TYPEORM-590152
801/1000  Why? Mature exploit, Has a fix available, CVSS 8.3
Mature

Prototype Pollution SNYK-JS-XML2JS-5414874
801/1000  Why? Mature exploit, Has a fix available, CVSS 8.3
Proof of Concept

Prototype Pollution SNYK-JS-HIGHLIGHTJS-1045326
801/1000  Why? Mature exploit, Has a fix available, CVSS 8.3
No Known Exploit

Regular Expression Denial of Service (ReDoS) SNYK-JS-HIGHLIGHTJS-1048676
801/1000  Why? Mature exploit, Has a fix available, CVSS 8.3
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: typeorm

0.3.20 - 2024-01-26Bug Fixes

added missing parentheses in where conditions (#10650) (4624930), closes #10534
don't escape indexPredicate (#10618) (dd49a25)
fallback runMigrations transaction to DataSourceOptions (#10601) (0cab0dd)
hangup when load relations with relationLoadStrategy: query (#10630) (54d8d9e), closes #10481
include asExpression columns in returning clause (#10632) (f232ba7), closes #8450 #8450
multiple insert in SAP Hana (#10597) (1b34c9a)
resolve issue CREATE/DROP Index concurrently (#10634) (8aa8690), closes #10626
type inferencing of EntityManager#create (#10569) (99d8249)

Features

add json type support for Oracle (#10611) (7e85460)
add postgres multirange column types (#10627) (d0b7670), closes #10556
add table comment for postgres (#10613) (4493db4)

Reverts

Revert "fix: prevent using absolute table path in migrations unless required (#10123)" (#10624) (8f371f2), closes #10123 #10624
revert "feat: nullable embedded entities (#10289)" (#10614) (15de46f), closes #10289 #10614

0.3.20-dev.fa86f6f - 2024-01-03

0.3.20-dev.f232ba7 - 2024-01-26

0.3.20-dev.dd8c0fd - 2024-01-26

0.3.20-dev.d0b7670 - 2024-01-26

0.3.20-dev.c22e30f - 2024-01-04

0.3.20-dev.8f371f2 - 2024-01-26

0.3.20-dev.8ebe769 - 2024-01-26

0.3.20-dev.73e3b49 - 2024-01-03

0.3.20-dev.62f574b - 2024-01-26

0.3.20-dev.54d8d9e - 2024-01-26

0.3.20-dev.1b34c9a - 2024-01-26

0.3.20-dev.15de46f - 2024-01-08

0.3.20-dev.0cab0dd - 2024-01-26

0.3.20-dev.4624930 - 2024-01-26

0.3.19 - 2024-01-03Bug Fixes

fixed Cannot read properties of undefined (reading 'sync') caused after glob package upgrade

0.3.19-dev.633c4e3 - 2024-01-03

0.3.18 - 2024-01-03 Read more

0.3.18-dev.ff6e875 - 2023-07-22

0.3.18-dev.fdb9866 - 2023-12-29

0.3.18-dev.fbd45db - 2023-08-19

0.3.18-dev.f6bb671 - 2023-12-29

0.3.18-dev.f6b87e3 - 2023-12-29

0.3.18-dev.ebd61d1 - 2023-09-30

0.3.18-dev.e72a9da - 2023-08-19

0.3.18-dev.e67d704 - 2024-01-02

0.3.18-dev.dff2d53 - 2023-07-22

0.3.18-dev.dd59524 - 2024-01-02

0.3.18-dev.d184d85 - 2023-10-05

0.3.18-dev.c8ee5b1 - 2023-08-19

0.3.18-dev.c6f608d - 2023-08-19

0.3.18-dev.befe4f9 - 2023-09-02

0.3.18-dev.b8af97a - 2023-09-30

0.3.18-dev.b6b46fb - 2023-12-29

0.3.18-dev.b5ec088 - 2024-01-03

0.3.18-dev.b240d87 - 2023-12-29

0.3.18-dev.ad5bf11 - 2023-12-29

0.3.18-dev.aa8d24c - 2023-12-29

0.3.18-dev.a939654 - 2023-12-29

0.3.18-dev.a909d5b - 2023-07-12

0.3.18-dev.a4900ae - 2023-12-29

0.3.18-dev.a00b1df - 2024-01-02

0.3.18-dev.9471bfc - 2023-09-22

0.3.18-dev.8d0e7f9 - 2023-09-30

0.3.18-dev.7e9cead - 2023-12-29

0.3.18-dev.7adbc9b - 2023-08-19

0.3.18-dev.7a58bbf - 2023-12-29

0.3.18-dev.6d5b5d9 - 2023-12-29

0.3.18-dev.65858f3 - 2023-12-29

0.3.18-dev.48f5f85 - 2023-12-29

0.3.18-dev.3cf938e - 2023-12-29

0.3.18-dev.3cda7ec - 2024-01-02

0.3.18-dev.2dc9624 - 2023-12-29

0.3.18-dev.173910e - 2024-01-02

0.3.18-dev.15bc887 - 2024-01-03

0.3.18-dev.122c897 - 2023-12-29

0.3.18-dev.0f11739 - 2024-01-02

0.3.18-dev.022d2b5 - 2023-08-19

0.3.17 - 2023-06-20Bug Fixes

#10040 TypeORM synchronize database even if it is up to date (#10041) (b1a3a39)
add missing await (#10084) (f5d4397)

0.3.17-dev.f5d4397 - 2023-06-19

0.3.17-dev.d4607a8 - 2023-05-10

0.3.17-dev.b1a3a39 - 2023-06-20

0.3.17-dev.abb9079 - 2023-05-09

0.3.17-dev.7108cc6 - 2023-06-20

0.3.16 - 2023-05-090.3.16 (2023-05-09)
Bug Fixes

add trustServerCertificate option to SqlServerConnectionOptions (#9985) (0305805), closes #8093
add directConnection options to MongoDB connection (#9955) (e0165e7)
add onDelete option validation for oracle (#9786) (938f94b), closes #9189
added instanceName to options (#9968) (7c5627f)
added transaction retry logic in cockroachdb (#10032) (607d6f9)
allow json as alias for longtext mariadb (#10018) (2a2bb4b)
convert the join table ID to the referenceColumn ID type (#9887) (9460296)
correct encode mongodb auth credentials (#10024) (96b7ee4), closes #9885
create correct children during cascade saving entities with STI (#9034) (06c1e98), closes #7758 #7758 #9033 #9033 #7758 #7758
express option bug in init command (#10022) (5be20e2)
for running cli-ts-node-esm use exit code from child process (#10030) (a188b1d), closes #10029
mongodb typings breaks the browser version (#9962) (99bef49), closes #9959
RelationIdLoader has access to queryPlanner when wrapped in transaction (#9990) (21a9d67), closes #9988
resolve duplicate subscriber updated columns (#9958) (3d67901), closes #9948
select + addOrderBy broke in 0.3.14 (#9961) (0e56f0f), closes #9960
support More/LessThanOrEqual in relations  (#9978) (8795c86)

Features

mariadb uuid inet4 inet6 column data type support (#9845) (d8a2e37)

Reverts

"refactor: remove date-fns package (#9634)" (54f4f89)

0.3.16-dev.f5b93c1 - 2023-04-18

0.3.16-dev.e0165e7 - 2023-04-17

0.3.16-dev.d8a2e37 - 2023-04-25

0.3.16-dev.b064049 - 2023-04-18

0.3.16-dev.a188b1d - 2023-05-09

0.3.16-dev.96b7ee4 - 2023-05-09

0.3.16-dev.8795c86 - 2023-05-09

0.3.16-dev.68aa573 - 2023-04-15

0.3.16-dev.54f4f89 - 2023-05-09

0.3.16-dev.3d67901 - 2023-04-18

0.3.16-dev.2a2bb4b - 2023-05-09

0.3.16-dev.21a9d67 - 2023-05-09

0.3.16-dev.06c1e98 - 2023-05-09

0.3.16-dev.9460296 - 2023-05-09

0.3.15 - 2023-04-15Bug Fixes

make cache optional fields optional (#9942) (159c60a)
prevent unique index identical to primary key (all sql dialects) (#9940) (51eecc2)
SelectQueryBuilder builds incorrectly escaped alias in Oracle when used on entity with composite key (#9668) (83c6c0e)

Features

support for the latest mongodb v5 (#9925) (f6a3ce7), closes #7907 #7907

0.3.15-dev.f6a3ce7 - 2023-04-15

0.3.15-dev.f1c5662 - 2023-04-15

0.3.15-dev.3a72e35 - 2023-04-13

0.3.15-dev.115059d - 2023-04-10

0.3.14 - 2023-04-09Bug Fixes

drop xml & yml connection option support. Addresses security issues in underlying dependency (#9930) (7dac12c)

Features

QueryBuilder performance optimizations (#9914) (12e9db0)

0.3.14-dev.daf1b47 - 2023-04-06

0.3.14-dev.0194f17 - 2023-04-06

0.3.13 - 2023-04-06 Read more

0.3.13-dev.f7f6817 - 2023-04-06

0.3.13-dev.f7b210b - 2023-04-05

0.3.13-dev.f1330ad - 2023-04-06

0.3.13-dev.de1228d - 2023-04-06

0.3.13-dev.af4f15c - 2023-04-06

0.3.13-dev.a868979 - 2023-04-06

0.3.13-dev.a11809e - 2023-04-06

0.3.13-dev.98f2205 - 2023-04-05

0.3.13-dev.97280fc - 2023-04-06

0.3.13-dev.58fc088 - 2023-02-09

0.3.13-dev.4fa14e3 - 2023-04-05

0.3.13-dev.4ac8c00 - 2023-04-06

0.3.13-dev.1fcd9f3 - 2023-04-05

0.3.13-dev.099fcd9 - 2023-02-08

0.3.13-dev.07221a3 - 2023-04-05

0.3.13-dev.0619aca - 2023-04-06

0.3.12 - 2023-02-07 Read more

0.3.12-dev.ef64bfc - 2023-01-28

0.3.12-dev.defb409 - 2023-01-03

0.3.12-dev.ca315f0 - 2023-02-05

0.3.12-dev.c77c43e - 2023-02-06

0.3.12-dev.c669f50 - 2023-01-28

0.3.12-dev.b97633b - 2022-12-28

0.3.12-dev.b8704f8 - 2023-02-06

0.3.12-dev.ae91c05 - 2022-12-27

0.3.12-dev.adce698 - 2023-02-07

0.3.12-dev.a95bed7 - 2022-12-18

0.3.12-dev.9bd3a64 - 2023-02-07

0.3.12-dev.8668c29 - 2022-12-29

0.3.12-dev.7df2ccf - 2023-02-06

0.3.12-dev.7726f5a - 2023-02-06

0.3.12-dev.74f7f79 - 2023-01-11

0.3.12-dev.6fb2121 - 2023-02-05

0.3.12-dev.6c928a4 - 2022-12-19

0.3.12-dev.67973b4 - 2022-12-29

0.3.12-dev.63ab05f - 2023-02-05

0.3.12-dev.54ca9dd - 2023-02-07

0.3.12-dev.4df969e - 2023-01-28

0.3.12-dev.3e1caf0 - 2023-01-03

0.3.12-dev.1a9b9fb - 2023-02-06

0.3.12-dev.18b659d - 2022-12-29

0.3.12-dev.15a4eb9 - 2022-12-29

0.3.12-dev.12fdd73 - 2023-02-07

0.3.12-dev.0eb7441 - 2023-02-07

0.3.12-dev.0d72317 - 2022-12-03

0.3.12-dev.8731858 - 2023-02-07

0.3.12-dev.8251812 - 2022-12-16

0.3.11 - 2022-12-03 Read more

0.3.11-dev.fc3b4f8 - 2022-12-03

0.3.11-dev.f07fb2c - 2022-12-03

0.3.11-dev.efb4168 - 2022-11-04

0.3.11-dev.d71e9c4 - 2022-12-03

0.3.11-dev.cdabaa3 - 2022-09-20

0.3.11-dev.b5ff79f - 2022-11-04

0.3.11-dev.97fae63 - 2022-12-03

0.3.11-dev.8a837f9 - 2022-09-20

0.3.11-dev.85fa9c6 - 2022-11-05

0.3.11-dev.81fc9a9 - 2022-12-03

0.3.11-dev.7fbc3ad - 2022-12-03

0.3.11-dev.71efa8e - 2022-12-03

0.3.11-dev.6eb674b - 2022-11-05

0.3.11-dev.6ba48bd - 2022-12-03

0.3.11-dev.66acec8 - 2022-11-04

0.3.11-dev.658604d - 2022-12-03

0.3.11-dev.5253c8f - 2022-11-04

0.3.11-dev.4ec04fa - 2022-11-21

0.3.11-dev.4a36d0e - 2022-11-05

0.3.11-dev.38e0eff - 2022-11-04

0.3.11-dev.2e1c9fd - 2022-11-04

0.3.11-dev.2473ff0 - 2022-12-03

0.3.11-dev.1cb738a - 2022-12-03

0.3.11-dev.19536ed - 2022-11-05

0.3.11-dev.7386318 - 2022-12-03

0.3.10 - 2022-09-19

0.3.10-dev.f24b262 - 2022-09-19

0.3.10-dev.e3aac27 - 2022-08-29

0.3.10-dev.de15df1 - 2022-09-19

0.3.10-dev.cc63961 - 2022-08-30

0.3.10-dev.a1960e1 - 2022-09-15

0.3.10-dev.773a4fe - 2022-09-14

0.3.10-dev.749809a - 2022-09-19

0.3.10-dev.52e5f7c - 2022-09-14

0.3.9 - 2022-08-28

0.3.8 - 2022-08-26

0.3.8-dev.fd7ae97 - 2022-08-24

0.3.8-dev.eb8f0c6 - 2022-08-24

0.3.8-dev.e49d0c8 - 2022-08-24

0.3.8-dev.de8aaac - 2022-08-24

0.3.8-dev.dadb658 - 2022-08-24

0.3.8-dev.d285fd0 - 2022-07-06

0.3.8-dev.c4f4650 - 2022-08-25

0.3.8-dev.bd96e27 - 2022-08-24

0.3.8-dev.bb33cd0 - 2022-07-11

0.3.8-dev.b8d04dc - 2022-08-25

0.3.8-dev.9f7fc14 - 2022-08-24

0.3.8-dev.8dcd61e - 2022-08-24

0.3.8-dev.72728f1 - 2022-08-25

0.3.8-dev.7198a7a - 2022-08-24

0.3.8-dev.68e8f22 - 2022-08-25

0.3.8-dev.64674e6 - 2022-08-24

0.3.8-dev.5ebc626 - 2022-08-24

0.3.8-dev.5e5abbd - 2022-08-25

0.3.8-dev.46d0021 - 2022-08-24

0.3.8-dev.3a533a4 - 2022-08-24

0.3.8-dev.340ab67 - 2022-08-25

0.3.8-dev.2e67138 - 2022-06-30

0.3.8-dev.15f90e0 - 2022-08-22

0.3.8-dev.109c1fa - 2022-06-29

0.3.8-dev.0b54222 - 2022-07-05

0.3.8-dev.03317a3 - 2022-08-28

0.3.7 - 2022-06-29

0.3.7-dev.ec23922 - 2022-06-22

0.3.7-dev.ec05f1d - 2022-06-29

0.3.7-dev.bcdddc3 - 2022-06-29

0.3.7-dev.a748f3c - 2022-06-29

0.3.7-dev.97e1dc1 - 2022-06-28

0.3.7-dev.60a7960 - 2022-06-28

0.3.7-dev.1b5aa62 - 2022-06-28

0.3.6 - 2022-04-12

0.3.6-dev.ef025bd - 2022-05-31

0.3.6-dev.ea176b2 - 2022-05-20

0.3.6-dev.e296126 - 2022-06-22

0.3.6-dev.e24cced - 2022-06-22

0.3.6-dev.d0ed02d - 2022-05-20

0.3.6-dev.cf3efec - 2022-05-23

0.3.6-dev.cc5a5c1 - 2022-04-11

0.3.6-dev.c814b07 - 2022-04-05

0.3.6-dev.bbdc20f - 2022-05-31

0.3.6-dev.b84cb9b - 2022-04-13

0.3.6-dev.9f8429f - 2022-04-27

0.3.6-dev.9d331b1 - 2022-04-11

0.3.6-dev.9adab34 - 2022-04-13

0.3.6-dev.862a402 - 2022-05-31

0.3.6-dev.7dfb69f - 2022-04-15

0.3.6-dev.78df84c - 2022-04-29

0.3.6-dev.62518ae - 2022-04-12

0.3.6-dev.506133e - 2022-06-10

0.3.6-dev.49cbe23 - 2022-04-18

0.3.6-dev.4687be8 - 2022-04-12

0.3.6-dev.2d8afbe - 2022-04-16

0.3.6-dev.22570f5 - 2022-05-20

0.3.6-dev.1b4cb00 - 2022-05-23

0.3.6-dev.189592c - 2022-05-20

0.3.6-dev.1197d1d - 2022-04-11

0.3.6-dev.07f4537 - 2022-06-22

0.3.6-dev.0659ec3 - 2022-05-30

0.3.6-dev.0418ebc - 2022-04-13

0.3.5 - 2022-04-05

0.3.5-dev.ec6c119 - 2022-03-28

0.3.5-dev.ec27803 - 2022-04-02

0.3.5-dev.eacecce - 2022-03-26

0.3.5-dev.e58c796 - 2022-03-31

0.3.5-dev.c5dfc11 - 2022-03-29

0.3.5-dev.baa2f44 - 2022-04-02

0.3.5-dev.b1a0107 - 2022-03-30

0.3.5-dev.9d1e246 - 2022-04-02

0.3.5-dev.9ac8e9e - 2022-03-26

0.3.5-dev.7832a1a - 2022-04-05

0.3.5-dev.69c33a2 - 2022-04-04

0.3.5-dev.3730fd0 - 2022-04-04

0.3.5-dev.2205a1a - 2022-04-02

0.3.5-dev.1693a17 - 2022-04-04

0.3.5-dev.002274c - 2022-03-26

0.3.5-dev.6774605 - 2022-04-02

0.3.4 - 2022-03-26

0.3.4-dev.d2cfd22 - 2022-03-26

0.3.4-dev.ceee439 - 2022-03-26

0.3.4-dev.c75bcae - 2022-03-23

0.3.4-dev.68a5c23 - 2022-03-23

0.3.4-dev.54c7db4 - 2022-03-25

0.3.4-dev.4b37030 - 2022-03-26

0.3.4-dev.17d391c - 2022-03-26

0.3.4-dev.494008 - 2022-03-26

0.3.3 - 2022-03-23

0.3.3-dev.f010205 - 2022-03-22

0.3.3-dev.a641c5d - 2022-03-23

0.3.3-dev.7cc1848 - 2022-03-23

0.3.3-dev.52a641c - 2022-03-23

0.3.3-dev.2b83776 - 2022-03-23

0.3.2 - 2022-03-22

0.3.2-dev.edf27d9 - 2022-03-22

0.3.2-dev.ce5973c - 2022-03-21

0.3.2-dev.c8fb1bb - 2022-03-21

0.3.2-dev.b53a481 - 2022-03-21

0.3.2-dev.97699e8 - 2022-03-22

0.3.2-dev.35106df - 2022-03-22

0.3.2-dev.28309eb - 2022-03-21

0.3.2-dev.05fc744 - 2022-03-22

0.3.1 - 2022-03-21

0.3.1-dev.d61f857 - 2022-03-18

0.3.1-dev.9f1b8e3 - 2022-03-21

0.3.1-dev.941b584 - 2022-03-17

0.3.0 - 2022-03-17

0.3.0-rc.41 - 2022-03-12

0.3.0-rc.40 - 2022-03-12

0.3.0-rc.39 - 2022-03-12

0.3.0-rc.38 - 2022-03-12

0.3.0-rc.37 - 2022-03-12

0.3.0-rc.36 - 2022-02-26

0.3.0-rc.35 - 2022-02-22

0.3.0-rc.34 - 2022-02-22

0.3.0-rc.33 - 2022-02-22

0.3.0-rc.32 - 2022-02-17

0.3.0-rc.31 - 2022-02-17

0.3.0-rc.30 - 2022-02-17

0.3.0-rc.29 - 2022-02-17

0.3.0-rc.28 - 2022-02-12

0.3.0-rc.27 - 2022-02-11

0.3.0-rc.26 - 2022-02-11

0.3.0-rc.25 - 2022-02-11

0.3.0-rc.24 - 2022-02-11

0.3.0-rc.23 - 2022-02-11

0.3.0-rc.22 - 2022-02-09

0.3.0-rc.21 - 2020-10-01

0.3.0-rc.20 - 2020-09-29

0.3.0-rc.19 - 2020-03-02

0.3.0-rc.18 - 2020-03-02

0.3.0-rc.17 - 2020-02-11

0.3.0-rc.16 - 2020-02-07

0.3.0-rc.15 - 2020-02-07

0.3.0-rc.14 - 2020-02-07

0.3.0-rc.13 - 2020-01-28

0.3.0-rc.12 - 2020-01-28

0.3.0-rc.11 - 2020-01-27

0.3.0-rc.10 - 2020-01-27

0.3.0-rc.9 - 2020-01-27

0.3.0-rc.8 - 2020-01-27

0.3.0-rc.7 - 2020-01-26

0.3.0-rc.5 - 2020-01-26

0.3.0-rc.4 - 2020-01-26

0.3.0-rc.3 - 2020-01-26

0.3.0-rc.2 - 2019-12-16

0.3.0-rc.1 - 2019-12-16

0.3.0-alpha.24 - 2019-09-12

0.3.0-alpha.23 - 2019-03-15

0.3.0-alpha.22 - 2018-10-19

0.3.0-alpha.21 - 2018-10-08

0.3.0-alpha.20 - 2018-10-05

0.3.0-alpha.19 - 2018-10-01

0.3.0-alpha.18 - 2018-09-25

0.3.0-alpha.17 - 2018-09-25

0.3.0-alpha.16 - 2018-09-12

0.3.0-alpha.15 - 2018-09-10

0.3.0-alpha.14 - 2018-09-06

0.3.0-alpha.13 - 2018-09-06

0.3.0-alpha.12 - 2018-08-31

0.3.0-alpha.11 - 2018-08-31

0.3.0-alpha.10 - 2018-08-14

0.3.0-alpha.9 - 2018-08-14

0.3.0-alpha.8 - 2018-08-14

0.3.0-alpha.7 - 2018-08-02

0.3.0-alpha.6 - 2018-06-30

0.3.0-alpha.5 - 2018-05-24

0.3.0-alpha.4 - 2018-05-24

0.3.0-alpha.3 - 2018-05-24

0.3.0-alpha.2 - 2018-05-24

0.3.0-alpha.1 - 2018-05-24

0.2.46-dev.486f8c5 - 2022-03-04

0.2.46-dev.5608956 - 2022-03-15

0.2.45 - 2022-03-04

0.2.45-dev.f3cfdd2 - 2022-03-02

0.2.45-dev.ea16ac2 - 2022-02-26

0.2.45-dev.96ac8f7 - 2022-03-02

0.2.45-dev.33b2bd7 - 2022-02-26

0.2.45-dev.32549fe - 2022-03-01

0.2.45-dev.3131c5c - 2022-02-23

0.2.45-dev.10f46d9 - 2022-02-26

0.2.45-dev.0fc093d - 2022-03-04

0.2.45-dev.6523526 - 2022-02-26

0.2.44 - 2022-02-23

0.2.44-dev.948d328 - 2022-02-23

0.2.44-dev.8742e33 - 2022-02-17

0.2.44-dev.7facbab - 2022-02-21

0.2.44-dev.6713a42 - 2022-02-17

0.2.44-dev.5a71803 - 2022-02-22

0.2.44-dev.2d3374b - 2022-02-22

0.2.44-dev.2c2fb29 - 2022-02-23

0.2.44-dev.1f54c70 - 2022-02-19

0.2.44-dev.136015b - 2022-02-18

0.2.44-dev.3291524 - 2022-02-23

0.2.43 - 2022-02-17

0.2.43-dev.a5493fb - 2022-02-16

0.2.43-dev.a24d48a - 2022-02-17

0.2.43-dev.96aed8a - 2022-02-17

0.2.43-dev.7dbe956 - 2022-02-17

0.2.43-dev.6b0b15b - 2022-02-17

0.2.43-dev.6ab9b3a - 2022-02-17

0.2.43-dev.60a5b84 - 2022-02-17

0.2.43-dev.4590c9b - 2022-02-17

0.2.42 - 2022-02-16

0.2.42-dev.f8154eb - 2022-01-31

0.2.42-dev.f7c1f7d - 2022-02-15

0.2.42-dev.f3e2b0e - 2021-11-23

0.2.42-dev.f224f24 - 2022-02-12

0.2.42-dev.ece0da0 - 2022-01-31

0.2.42-dev.e52b26c - 2021-12-11

0.2.42-dev.e0adeee - 2022-02-15

0.2.42-dev.d6043b7 - 2022-02-14

0.2.42-dev.d10484e - 2022-01-31

0.2.42-dev.d0f32b3 - 2022-02-16

0.2.42-dev.cefddd9 - 2021-12-11

0.2.42-dev.ce69228 - 2022-01-15

0.2.42-dev.cbb61eb - 2022-01-31

0.2.42-dev.bd22dc3 - 2021-12-10

0.2.42-dev.baa5880 - 2022-02-15

0.2.42-dev.b93416d - 2022-02-16

0.2.42-dev.a855b90 - 2022-01-15

0.2.42-dev.a11c50d - 2022-02-15

0.2.42-dev.a0f09de - 2021-11-23

0.2.42-dev.9e844d9 - 2022-02-16

0.2.42-dev.93bf96e - 2022-02-16

0.2.42-dev.93383bd - 2022-02-15

0.2.42-dev.92c3e79 - 2022-02-12

0.2.42-dev.90a8deb - 2021-12-11

0.2.42-dev.8f2ae71 - 2022-02-16

0.2.42-dev.8898a71 - 2022-02-15

0.2.42-dev.6523fcc - 2022-01-15

0.2.42-dev.6316e26 - 2022-02-12

0.2.42-dev.600bd4e - 2022-02-15

0.2.42-dev.54cf660 - 2021-12-06

0.2.42-dev.4a7f242 - 2022-01-31

0.2.42-dev.2bf93d4 - 2021-12-10

0.2.42-dev.26815c6 - 2022-01-31

0.2.42-dev.26581d0 - 2022-01-15

0.2.42-dev.1cfd7b9 - 2022-01-31

0.2.42-dev.1446e02 - 2022-02-01

0.2.42-dev.0626ed1 - 2021-12-10

0.2.42-dev.02400da - 2022-02-14

0.2.42-dev.3286519 - 2021-11-18

0.2.42-dev.3284808 - 2022-02-12

0.2.42-dev.2834729 - 2021-12-11

0.2.41 - 2021-11-18

0.2.41-dev.d494fcc - 2021-11-18

0.2.41-dev.c895680 - 2021-11-13

0.2.41-dev.c59ef29 - 2021-11-17

0.2.41-dev.b2c8168 - 2021-11-14

0.2.41-dev.98d5f39 - 2021-11-13

0.2.41-dev.91080be - 2021-11-14

0.2.41-dev.8a5e671 - 2021-11-18

0.2.41-dev.7b8a1e3 - 2021-11-18

0.2.41-dev.4e7d32f - 2021-11-17

0.2.41-dev.32bf6c0 - 2021-11-17

0.2.41-dev.2d0abe7 - 2021-11-16

0.2.41-dev.29cb891 - 2021-11-14

0.2.41-dev.1f558b1 - 2021-11-11

0.2.41-dev.15ad5ac - 2021-11-17

0.2.40 - 2021-11-11

0.2.40-dev.e80f97d - 2021-11-11

0.2.40-dev.d039319 - 2021-11-10

0.2.40-dev.ae858ad - 2021-11-09

0.2.40-dev.a92120a - 2021-11-10

0.2.40-dev.969af95 - 2021-11-09

0.2.40-dev.41ee95c - 2021-11-09

0.2.40-dev.3f98197 - 2021-11-09

0.2.40-dev.1588c58 - 2021-11-09

0.2.40-dev.0cc8fbb - 2021-11-10

0.2.40-dev.0334d10 - 2021-11-11

0.2.39 - 2021-11-09

0.2.39-dev.f79ae58 - 2021-11-09

0.2.39-dev.ef33cf4 - 2021-10-28

0.2.39-dev.e4d4636 - 2021-11-08

0.2.39-dev.dd94c9d - 2021-10-04

0.2.39-dev.d8c5812 - 2021-10-03

0.2.39-dev.d7d19e9 - 2021-10-02

0.2.39-dev.cf281ef - 2021-10-22

0.2.39-dev.bc55836 - 2021-10-28

0.2.39-dev.b6c828c - 2021-10-18

0.2.39-dev.b678807 - 2021-10-02

0.2.39-dev.6929ae3 - 2021-11-06

0.2.39-dev.503d1dc - 2021-10-20

0.2.39-dev.4ad3a61 - 2021-10-21

0.2.39-dev.4aaafdf - 2021-11-09

0.2.39-dev.4638dea - 2021-11-04

0.2.39-dev.2c861af - 2021-10-26

0.2.39-dev.28c183e - 2021-11-04

0.2.39-dev.25271d7 - 2021-11-02

0.2.39-dev.2133ffe - 2021-10-22

0.2.39-dev.179ae75 - 2021-10-26

0.2.39-dev.1197f88 - 2021-10-29

0.2.39-dev.0bc194c - 2021-10-03

0.2.39-dev.0adad88 - 2021-10-27

0.2.39-dev.9692930 - 2021-11-08

0.2.39-dev.8615733 - 2021-10-06

0.2.39-dev.6558295 - 2021-11-05

0.2.39-dev.1649882 - 2021-11-05

0.2.38 - 2021-10-02

0.2.38-dev.e9366b3 - 2021-08-18

0.2.38-dev.d8f6037 - 2021-10-02

0.2.38-dev.d4111ce - 2021-10-02

0.2.38-dev.b858f84 - 2021-08-17

0.2.38-dev.a868078 - 2021-08-28

0.2.38-dev.749511d - 2021-08-25

0.2.38-dev.324f1d8 - 2021-10-02

0.2.38-dev.22676a0 - 2021-08-24

0.2.38-dev.02f0bce - 2021-08-13

0.2.37 - 2021-08-13

0.2.37-dev.fe78bee - 2021-08-08

0.2.37-dev.fbd1ef7 - 2021-08-11

0.2.37-dev.fbbac93 - 2021-08-03

0.2.37-dev.f7eb46d - 2021-07-31

0.2.37-dev.f0e40f6 - 2021-08-06

0.2.37-dev.cd71f62 - 2021-07-31

0.2.37-dev.ca26297 - 2021-08-04

0.2.37-dev.ba366f2 - 2021-08-08

0.2.37-dev.ab39066 - 2021-08-06

0.2.37-dev.a5e4ce7 - 2021-08-05

0.2.37-dev.a3a3284 - 2021-08-10

0.2.37-dev.91d5b2f - 2021-07-31

0.2.37-dev.80cdf8f - 2021-08-11

0.2.37-dev.768b4fe - 2021-08-05

0.2.37-dev.69fabaf - 2021-07-31

0.2.37-dev.65cbcc7 - 2021-08-10

0.2.37-dev.5a3767f - 2021-08-08

0.2.37-dev.5714e8d - 2021-08-11

0.2.37-dev.37c40a6 - 2021-08-11

0.2.37-dev.37bd012 - 2021-08-04

0.2.37-dev.36398db - 2021-08-12

0.2.37-dev.2344db6 - 2021-08-04

0.2.37-dev.01a038c - 2021-08-13

0.2.37-dev.4201938 - 2021-08-05

0.2.36 - 2021-07-31

0.2.36-dev.d365acc - 2021-07-30

0.2.36-dev.b797781 - 2021-07-30

0.2.36-dev.76e7ed94 - 2021-07-30

0.2.36-dev.62d7976 - 2021-07-31

0.2.36-dev.0d90bcd - 2021-07-30

0.2.35 - 2021-07-29

0.2.35-rc.0 - 2021-07-28

0.2.34 - 2021-06-03

0.2.33 - 2021-06-01

0.2.32 - 2021-03-30

0.2.31 - 2021-02-08

0.2.30 - 2021-01-12

0.2.29 - 2020-11-02

0.2.28 - 2020-09-30

0.2.27 - 2020-09-29

0.2.26 - 2020-09-10

0.2.25 - 2020-05-19

0.2.24 - 2020-02-28

    from typeorm GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

🎉 Congrats! This commit does not introduce any vulnerablities.
☑ security/snyk check is completed. (View Details)

✅ No vulnerabilities were found.

🎉 Congrats! This commit does not introduce any vulnerablities.
☑ security/snyk check is completed. (View Details)

✅ No vulnerabilities were found.

🎉 Congrats! This commit does not introduce any vulnerablities.
☑ security/snyk check is completed. (View Details)

✅ No vulnerabilities were found.

☑ license/snyk check is completed. (View Details)

✅ No vulnerabilities were found.

🎉 Congrats! This commit does not introduce any vulnerablities.
☑ security/snyk check is completed. (View Details)

✅ No vulnerabilities were found.

🎉 Congrats! This commit does not introduce any vulnerablities.
☑ security/snyk check is completed. (View Details)

✅ No vulnerabilities were found.

🎉 Congrats! This commit does not introduce any vulnerablities.
☑ security/snyk check is completed. (View Details)

✅ No vulnerabilities were found.

☑ license/snyk check is completed. (View Details)

✅ No vulnerabilities were found.

🎉 Congrats! This commit does not introduce any vulnerablities.
☑ security/snyk check is completed. (View Details)

✅ No vulnerabilities were found.

☑ license/snyk check is completed. (View Details)

✅ No vulnerabilities were found.

🎉 Congrats! This commit does not introduce any vulnerablities.
☑ security/snyk check is completed. (View Details)

✅ No vulnerabilities were found.

repo: maismas/nodejs-goof


text:
feature: allow any value to be saved against a mark

When using a mark as a favourite or bookmark the user might want to use a custom value not in a defined list, this allows any value to be saved

Dear @digitalSloth , your pr looks good!
Could you please add some documentation?

authors: digitalSloth riccardodallavia

repo: maize-tech/laravel-markable


text:
Support for BWT FI 45 pool heater

Hi,
are you guys planning to support the BWT FI 45 pool heater?
I tried to integrate it which resulted in the follwoing error:
2021-05-25 17:19:58 ERROR (MainThread) [homeassistant.components.climate] Error while setting up tuya_local platform for climate
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 231, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/tuya_local/climate.py", line 52, in async_setup_entry
await async_setup_platform(hass, {}, async_add_entities, discovery_info)
File "/config/custom_components/tuya_local/climate.py", line 27, in async_setup_platform
raise ValueError(f"Unable to detect type for device {device.name}")
ValueError: Unable to detect type for device My pool heater
From the error message I assume the decvice is simply not supported...
I also assume the integration almost works because I could see some actual device data in the log:
2021-05-25 17:38:13 WARNING (MainThread) [homeassistant.loader] You are using a custom integration tuya_local which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-05-25 17:38:18 DEBUG (MainThread) [custom_components.tuya_local] Setting up entry for device: 4771835498f4abecc15f
2021-05-25 17:38:18 DEBUG (MainThread) [custom_components.tuya_local.device] Creating device: 4771835498f4abecc15f
2021-05-25 17:38:18 INFO (MainThread) [custom_components.tuya_local.device] Setting protocol version for My pool heater to 3.3.
2021-05-25 17:38:20 DEBUG (SyncWorker_2) [custom_components.tuya_local.device] Refreshing device state for My pool heater.
2021-05-25 17:38:20 DEBUG (SyncWorker_2) [custom_components.tuya_local.device] refreshed device state: {"devId": "4771835498f4abecc15f", "dps": {"1": true, "2": 25, "3": 24, "4": "heat", "9": 0, "updated_at": 1621957100.7268553}}
2021-05-25 17:38:20 DEBUG (SyncWorker_2) [custom_components.tuya_local.device] new cache state (including pending properties): {"1": true, "2": 25, "3": 24, "4": "heat", "9": 0, "updated_at": 1621957100.7268553}
2021-05-25 17:38:20 DEBUG (MainThread) [custom_components.tuya_local.device] Inferring device type from cached state: {'1': True, '2': 25, '3': 24, '4': 'heat', '9': 0, 'updated_at': 1621957100.7268553}
2021-05-25 17:38:21 WARNING (MainThread) [custom_components.tuya_local.device] Detection for My pool heater failed
2021-05-25 17:38:21 ERROR (MainThread) [homeassistant.components.climate] Error while setting up tuya_local platform for climate
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 231, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/tuya_local/climate.py", line 52, in async_setup_entry
await async_setup_platform(hass, {}, async_add_entities, discovery_info)
File "/config/custom_components/tuya_local/climate.py", line 27, in async_setup_platform
raise ValueError(f"Unable to detect type for device {device.name}")
ValueError: Unable to detect type for device My pool heater
From the log I can guess that taget and current temperature as well as heating mode and other information is already taken from the device...
All in all looks pretty promising to me :-)
Hope to hear from you guys

Hi,
The other information I would need is:

Which of the "2": 25 and "3": 24 is the target temperature, and which the measured temperature.
What is the temperature range that can be set.
"4": "heat" looks like a preset (I guess that is what you mean by heating mode).   What are the other presets? Or is it just an indicator.
Do you have any idea what "9": 0 is for?  It could be an error code (0 being no error), or a timer.

Currently I am in the middle of a refactoring to make adding new devices easier.  I will add this and other pending devices once I have the required climate functions working. This one looks fairly basic, so should

Hi, thank you very much for considering this device for your integration!

25 degrees celsius is the target temperature and 24 degrees is the temperature measured by the device.
The target temperature range can vary between 8 and 40 degrees.
The device supports heating and cooling. It heats or cools in different modes (see screenshot) like 'Automatic', 'Smart Cooling', 'Boost Cooling', 'Eco Cooling and similar ones for heating. If you like i can try all those modes and provide you the logs for each mode.
I have no clue so far what "9": 0 is for. You can setup timers and I also saw error messages in the app when e.g. the pool pump was idle. I'll try some different settings in the app and collect the results in the logs if you think that helps....

Yes, cycling through the presets will help.  No need to spend much time on dps "9", timers can be set up in HA independently of the device, and if it is an error code, I can just add an attribute that reports it as an int for any automations to pick up on.

This appears to be the same as the Remora pool heater requested in #15, except for a variation in the minimum temperature, and maybe some additional presets.  They could either be combined into one device with lowest common denominator functionality, or they will be impossible to distinguish automatically and will need to be manually configured.

OK, here are the modes :

Eco heating mode : {"1": true, "2": 25, "3": 23, "4": "quietheat", "9": 0, "updated_at": 1622002888.8546965}
Boost heating mode : {"1": true, "2": 25, "3": 23, "4": "quickheat", "9": 0, "updated_at": 1622023001.359755}
Smart heating mode : {"1": true, "2": 25, "3": 24, "4": "heat", "9": 0, "updated_at": 1622028474.5414855}
Automatic : {'1': True, '2': 25, '3': 24, '4': 'auto', '9': 0, 'updated_at': 1622028926.2002869}
Smart cooling mode :  {"1": true, "2": 25, "3": 24, "4": "cool", "9": 0, "updated_at": 1622029041.9679456}
Boost cooling mode : {"1": true, "2": 25, "3": 24, "4": "quickcool", "9": 0, "updated_at": 1622029119.8440619}
Eco cooling mode : {"1": true, "2": 25, "3": 24, "4": "quietcool", "9": 0, "updated_at": 1622029167.5428402}
Eco cooling mode but device switched to standby {"1": false, "2": 25, "3": 24, "4": "quietcool", "9": 0, "updated_at": 1622029204.0674973}
Hope that helps ! Let me know if you need more or want me to test something else...
Thanks!

OK, unfortunately apart from heat and cool, they are not the same as the Remora heatpump.  I will have to think some more about how these two devices can be distinguished.  I just added the Remora support in 0.5.0, so you could try that now.  If you are using HACS, click on the menu at top right of the Tuya Local box, and select "Update Information" to check for updates without waiting the 10 hours that HACS has between checks.

I forgot the device states with the water pump switched off :
{"1": true, "2": 25, "3": 24, "4": "heat", "9": 1, "updated_at": 1622030104.1905162}

I tried it...

You made my day !!!
Thank you so much!!!

I have added full support in 0.8.3 for this device.  You will need to delete and re-add the device to change the device type from Remora to BWT.  Make sure you have a note of the local key and device id before you delete it.  The local key is in the Options, the device id may appear in the logs, or you can browse through config/.storage/core.config_entries to look for the current config.

Just installed it and it worked right away.
Jason Rumney @.***> schrieb am Sa., 3. Juli 2021, 05:04:

I have added full support in 0.8.3 for this device. You will need to
delete and re-add the device to change the device type from Remora to BWT.
Make sure you have a note of the local key and device id before you delete
it. The local key is in the Options, the device id may appear in the logs,
or you can browse through config/.storage/core.config_entries to look for
the current config.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/make-all/tuya-local/issues/17#issuecomment-873334424,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APM3LKEVQPXDBLEOSFKLO2LTVZ44TANCNFSM45PVHR2Q
.

repo: make-all/tuya-local


text:
Request support for WIFI Remote Switch TOB9-63T No metering

Log message
Test protocol error 901: Network Error: Unable to Connect

https://www.aliexpress.com/item/1005005566304770.html
Product ID
i6ibspwrdkfh7gdy
Product Name
WiFi智能开关
DPS information
{
  "result": {
    "model": "{\"modelId\":\"e1er9w\",\"services\":[{\"actions\":[],\"code\":\"\",\"description\":\"\",\"events\":[],\"name\":\"默认服务\",\"properties\":[{\"abilityId\":1,\"accessMode\":\"rw\",\"code\":\"switch_1\",\"description\":\"\",\"extensions\":{\"iconName\":\"icon-dp_power2\",\"attribute\":\"645\"},\"name\":\"开关\",\"typeSpec\":{\"type\":\"bool\"}},{\"abilityId\":9,\"accessMode\":\"rw\",\"code\":\"countdown_1\",\"description\":\"\",\"extensions\":{\"iconName\":\"icon-dp_time2\",\"attribute\":\"740\"},\"name\":\"开关倒计时\",\"typeSpec\":{\"type\":\"value\",\"max\":86400,\"min\":0,\"scale\":0,\"step\":1,\"unit\":\"s\"}},{\"abilityId\":21,\"accessMode\":\"ro\",\"code\":\"test_bit\",\"description\":\"\",\"extensions\":{\"attribute\":\"736\"},\"name\":\"产测结果位\",\"typeSpec\":{\"type\":\"value\",\"max\":5,\"min\":0,\"scale\":0,\"step\":1}},{\"abilityId\":38,\"accessMode\":\"rw\",\"code\":\"relay_status\",\"description\":\"\",\"extensions\":{\"iconName\":\"icon-zhuangtai\",\"attribute\":\"736\"},\"name\":\"上电状态设置\",\"typeSpec\":{\"type\":\"enum\",\"range\":[\"off\",\"on\",\"memory\"]}},{\"abilityId\":40,\"accessMode\":\"rw\",\"code\":\"light_mode\",\"description\":\"\",\"extensions\":{\"iconName\":\"tcl_function_light\",\"attribute\":\"224\"},\"name\":\"指示灯状态设置\",\"typeSpec\":{\"type\":\"enum\",\"range\":[\"relay\",\"pos\",\"none\",\"on\"]}},{\"abilityId\":41,\"accessMode\":\"rw\",\"code\":\"child_lock\",\"description\":\"\",\"extensions\":{\"iconName\":\"icon-dp_power2\",\"attribute\":\"132\"},\"name\":\"检修锁定\",\"typeSpec\":{\"type\":\"bool\"}},{\"abilityId\":42,\"accessMode\":\"rw\",\"code\":\"cycle_time\",\"description\":\"最大10个定时功能: 每10个字节代表；\\n/#1通道号（bit0--开关，bit7-bit1---通道号）；\\n/#2星期；\\n/#3#4起始时间(min)；\\n/#5#6结束时间(min)；\\n/#7#8开启时间(min)；\\n/#9#10关闭时间(min)；\",\"extensions\":{\"iconName\":\"icon-dp_time3\",\"attribute\":\"128\"},\"name\":\"循环定时\",\"typeSpec\":{\"type\":\"string\",\"maxlen\":255}},{\"abilityId\":66,\"accessMode\":\"rw\",\"code\":\"online_state\",\"description\":\"\",\"extensions\":{\"iconName\":\"icon-dp_updown\"},\"name\":\"查询状态\",\"typeSpec\":{\"type\":\"enum\",\"range\":[\"online\",\"offline\"]}}]}]}"
  },
  "success": true,
  "t": 1731780708886,
  "tid": "3f49d79fa44611efbd65e6107338fc03"
}

Information about how the device functions
Simple wifi remote switch without metering function

See #522 for connection issues

authors: make-all vladmokryi


text:
MIPs with problems to parse

Some problems where found on this MIPS:

MIP Path: MIP97/MIP97.md

MIP Path: MIP98/MIP98.md

fixed by https://github.com/makerdao/mips/pull/824

authors: RoxanaSocaDspot patrick-j-govalpha

repo: makerdao/mips


text:
-version command

There should be -version and -v command added that respond with current package version
This one should be implemented inside index.js file

Please review and merge this #8

repo: makoteq/metaxa


text:
Error ofcompilation in  angular 9

getting an error of compilation:
ERROR in Failed to compile entry-point mat-select-autocomplete (module as esm5) due to compilation errors:
node_modules/mat-select-autocomplete/fesm5/mat-select-autocomplete.js:282:30 - error NG1010: Value at position 3 in the NgModule.imports of SelectAutocompleteModule is not a reference: [object Object]

I am getting the same exception. Is any one working on this ?
It looks like the 2 files are referring to older version of Material components:
Existing:
import { MatButtonModule, MatCheckboxModule } from '@angular/material';
Expected:
import { MatButtonModule} from '@angular/material/button'; import { MatCheckboxModule} from '@angular/material/checkbox';

No, it's just that angular 10 has ivy enabled by default, which supports tree-shaking, so you need to include each component on it's own.

No, it's just that angular 10 has ivy enabled by default, which supports tree-shaking, so you need to include each component on it's own.

authors: achilehero aish16 pingouin-creation

repo: malothnaresh/mat-select-autocomplete


text:
cannot read property of RNFSFileTypeRegular of undefined

I get the following errors:
on iOS simulator: cannot read property of RNFSFileTypeRegular of undefined
on iOS device: undefined is not an object (evaluating 'RNFSManager.RNFSFileTypeRegular')
I completed the setup, then react-native link for all three dependencies.
Then I tried manually linking react-native-fs, still didn't work...
Any solutions to this?
Thanks

Nevermind... had missed some step in the manual linking of react-native-fs
Its working now...

Nevermind... had missed some step in the manual linking of react-native-fs
Its working now...

Hey LaVielle, you could use it?? tell me at farras.abiyyu.doko@gmail.com

Nevermind... had missed some step in the manual linking of react-native-fs
Its working now...

Hi LaVielle, Could you use it? tell me at farras.abiyyu.doko@gmail.com

authors: LaVielle farrasdoko

repo: malsapp/react-native-photo-upload


text:
Auth form

Choose ui lib and make Auth form

I will use MUI as ui

repo: mamedbekovruslan/real-estate-crm


text:
Footer added

Description
New footer design added.
Fixes #73

@Jagannath8 hey can you remove the Facebook icon and attach my twitter url in the twitter icon? You can find it in my GitHub profile.

Ya sure!

@Jagannath8 merged. Thank you for your contribution 🥇

repo: manankohlii/spacex-launch-data


text:
Fixed logging message type check in logit method

Previously, "warn" logging messages would not be logged due to the logit method checking for "warning" but "warn" being passed in.

Nice catch! :) thanks for the contribution.

authors: JonCooperWorks mandatoryprogrammer

repo: mandatoryprogrammer/xsshunter


text:
consider using deptry to review dependencies

https://github.com/fpgmaas/deptry

Hello, can I take this up. I have read a bit about deptry and its rule violations. This repo has multiple DEP001, DEP002 and DEP003 errors.

Few of DEP001 are due to module imports which need not be added to dev dependencies, hence we can add for deptry ignore in toml file (like ghidra, binaryninja), others (ids, java) I am investigating if its module or missing dependency.
DEP002 is due to formatting and checking modules (flake8, isort, ruff) that needs to added to ignore file, as deptry only checks  imports py, ipynb files.
I am still reading about DEP003 and how to resolve/ignore it.

Sounds good, go for it 😄

authors: mr-tz psahithireddy williballenthin

repo: mandiant/capa


text:
rename args.sample to args.input

since the input file is not longer guaranteed to be an executable file to analyze (cape, freeze, result document), then we should rename the CLI argument from sample to input (?). we should do this in v7 since its a breaking change that goes along with the cape work.

thoughts @mr-tz @mike-hunhoff ?

I agree a name change is due. I also like file as input makes me think of Python's input and that I could pipe/type/etc. data to capa.

I also like file as input makes me think of Python's input and that I could pipe/type/etc. data to capa.

Good point, how about input_file?

sounds good

authors: mike-hunhoff williballenthin


text:
allow for density to be strings not numbers

I've seen a few times this same scenario, and manifoldjs should be smart enough to support:
https://www.npmjs.com/static/images/touch-icons/manifest.json
It expects the density to be a number, not a string representing a number.  it should just work

The spec corrects for this also. See algorithm for how to process the density member (i.e., use Number.parseFloat()):
https://w3c.github.io/manifest/#density-member

authors: boyofgreen marcoscaceres

repo: manifoldjs/ManifoldJS


text:
Add internal Style page

Adds a /styles page with all of our widgets (well, just buttons and inputs for now)
https://prod-g62bqjmme-mantic.vercel.app/styles
I had this at one of my previous companies and it made debugging widgets easier and was also just good documentation. It's kinda like Storybook, but easier to maintain

Sweet! I remember we had a gallery page for all our front-end components at Google (within a suborg of ads).

Nice presentation! Seems like the green button is missing a darker bg on hover

authors: jahooma sipec

repo: manifoldmarkets/manifold


text:
🛑 Mesa Freeworld is down

In aaa356b, Mesa Freeworld (https://nonfree.eu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mesa Freeworld is back up in 1005ada after 17 minutes.

repo: manjaro-contrib/upptime