New Install

Hi there.
Thank you for your work on this project..
Im new to HA and saw your integration and thought it would work really well for me :)
I had a couple of issues installing HACS, but all good now, however when i came to add your repo, HACS said that it was already in the marketplace...  so i downloaded this version.
I dont seem to get any configuration items (ie unable to login to Sensit) and i only get the readme.md if i enable experimental features in HACS....
is this me going wrong somewhere?
Thanks again for your time and energies!

Ah that's my fault for not updating the readme after the repo was accepted by HACS. You should just be able to search HACS now to install without adding the custom repo. If that doesn't work can you add this to your config and let me know what debug messages you see from the Sensit integration?
logger:
  default: warning
  logs:
    custom_components.kingspan_watchman_sensit: debug

Hi
thanks for getting back to me...
The repo is added to my HACS implementation (so thats all good) ...
but i dont get asked to enter my username/password..

This is all i see 🤷♂

I think the best idea is to remove the integration, add the debug logging, restart HA and re-add. You should see some logs then. I see:
2023-01-13 14:28:23.543 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] API init as username=XXXXXXXXXX
2023-01-13 14:28:23.543 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Fetching tank data with username= XXXXXXXXXX
2023-01-13 14:28:25.141 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Tank data: level=628, capacity=1300, serial_number= XXXXXXXXXX,last_read=2023-01-13 00:31:44.543000+00:00, usage_rate
=17.5, forecast_empty=35
2023-01-13 14:28:25.141 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Finished fetching kingspan_watchman_sensit data in 1.598 seconds (success: True)
2023-01-13 14:28:25.156 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Adding sensor entities
2023-01-13 14:28:25.156 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Init entity Oil Level
2023-01-13 14:28:25.156 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Init entity Tank Percentage Full
2023-01-13 14:28:25.156 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Init entity Tank Capacity
2023-01-13 14:28:25.156 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Init entity Last Reading Date
2023-01-13 14:28:25.156 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Init entity Current Usage
2023-01-13 14:28:25.156 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Init entity Forecast Empty
2023-01-13 14:28:25.160 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Read oil level: 628 litres
2023-01-13 14:28:25.161 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Read oil level: 48.3 percent
2023-01-13 14:28:25.161 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Read tank capcity: 1300 litres
2023-01-13 14:28:25.161 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Tank last read 2023-01-13 00:31:44.543000+00:00
2023-01-13 14:28:25.161 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Current oil usage 17 days
2023-01-13 14:28:25.162 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Tank forecast empty 35 days
2023-01-13 22:28:25.496 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Fetching tank data with<EMAIL_ADDRESS>2023-01-13 22:28:26.445 DEBUG (MainThread) [custom_components.kingspan_watchman_sensit] Tank data: level=628, capacity=1300, serial_number=20001412,last_read=2023-01-13 00:31:44.543000+00:00, usage_rate

So i added the following lines to my configuration.yaml
logger:
default: warning
logs:
custom_components.kingspan_watchman_sensit: debug
this is all i see in the logs...
2023-01-20 09:35:16.351 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration kingspan_watchman_sensit 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
2023-01-20 09:35:16.351 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs 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

The indentation of the config is important and I can't tell if that's right (see above) but I've added a quick install button on the README (the blue button). I suggest deleting the integration again and then adding from that button. I just tried this and was asked for my username and password again

Hi there,
thanks for getting back to me - still no dice...
im running Home Assistant 2023.1.6, but when i click on the install button you put in the readme i get this error...
Error
This integration does not support configuration via the UI. If you followed this link from the Home Assistant website, make sure you run the latest version of Home Assistant.
I repasted the debugging code into configuration.yaml

so i installed again through the HACS marketplace, reboot and then opened the integration page, clicked on Watchman and get this...

if i enable experimental settings i get this...

but im still havent been asked to log in 🤷♂
Thanks for all your help... sorry if its all my fault!

OK - figured it out...
(sort of...)
Firstly - thanks for your patience and help!
When i ticked "Enable experimental features" in HACS - i saw the full version of the repo readme

at this point in HACS i was able to click on the install button and was asked for my username and password!
thanks again!

Great thanks for confirming. I'll go and see what "Enable experimental features" does!

no worries.
Thanks for your help & if you need any "dummies" troubleshooting...  happy
to help :)
On Sun, 22 Jan 2023 at 15:14, Jon Connell @.***> wrote:

Great thanks for confirming. I'll go and see what "Enable experimental
features" does!
—
Reply to this email directly, view it on GitHub
https://github.com/masaccio/ha-kingspan-watchman-sensit/issues/2#issuecomment-1399516018,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARJRW5ROVNLMSGSPYFEPEBDWTVFFFANCNFSM6AAAAAAUBIBROM
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Simplify code testing templates

Use t.TempDir() to simplify our test code

Addresses some points that @dfreilich raised in the https://github.com/buildpacks/scafall/pull/3 review.


Fit size to a certain format

I'm trying to convert an HTML document and make it fit in an A4 format (it's a certificate). The issue is that it's larger than A4, and it takes several pages. How can I make it fit to A4? Is there any way to do it? I could convert it to a larger size and then look for a PDF library to make it fit in A4, but I thought there might be a simpler solution. Thanks!

Thanks!!!! @santiagobasulto.
It worked. :)


Error creating a function

I have been trying to write this function (at the end of Wordle). Here I have succeeded:

However, several times, while creating it, there has been an error thrown - visible in the console e.g.:

The fact that the error arises in ParamList suggests to me that it might be something to do with the function having no params - although this is allowed, and has not cause a problem elsewhere. It also doesn't seem to happen when writing a function that, say, returns an Int, so maybe it is in some way specific to Iter?

I've taken a look at this. It's because the rootNode of the ParamList is still undefined when the compile is happening.
The compile assumes that this will never be true. ie even if a field is empty there will be a ParseNode with no content.
Need to decide if that is a correct assumption (and so fix the ParmList rootNode) or not and add checks within the compile code.

Currently, the rootNode is not set up until there is any text to parse. I think this is the right approach.
The ParamList does have the optional flag set to true
I think the compiler should test for whether the root node exists. If it does not exist, then if the field is marked optional, the compiler should move on, but if the field is not optional and the root node is undefined it should throw an error (this should not occur) - because the field should still be showing as parse incomplete.


Add option to disable JSON reporting completely

We could have it on by default but instead of creating many report files:
~/.reframe/reports/run-report-0.json
~/.reframe/reports/run-report-1.json
etc...

we could set the default to overwrite:
~/.reframe/reports/run-report.json

and then add the option to specify new report files (as before) ?

@jgphpc Not a bad idea either.

I think that setting the default as you propose here is the best solution, in which case I don't think we need to have an extra configuration parameter to disable reporting completely, do we?

If you have hundreds of jobs all writing to the same file (~/.reframe/reports/run-report.json), it will not work, no ?

Good point, but that's a different issue. Even if you had a single file per session as now, the problem would remain the same; you might end up with two reframe instances trying to create the same file. We would need to arbitrate that using a file lock.


#9461 fixed assignability of component types to sequence types

I'm still trying to verify but I notice that some of the changes are to .xtend files in the UI plugin.  IIRC this was the spot where we had to commit the generated Java file(s) because of the jar-in-jar build issue.  When you build the plug-in do you notice any dirty Java files that should be committed?

AFAIR, only the classes that are referred to by other plug-ins had to be converted to Java, which is not the case for those I changed. So I expect no build issues. Please notify me if you encounter problems.
Dr. Jan Köhnlein
<EMAIL_ADDRESS>TypeFox GmbH
Am Germaniahafen 1
24143 Kiel
Phone: +49<PHONE_NUMBER>7
Skype: jankoehnlein
Twitter: jankoehnlein
Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385
Geschäftsführer: Sven Efftinge, Moritz Eysholdt, Dr. Jan Köhnlein

On 26. Apr 2017, at 16:39, Keith Brown<EMAIL_ADDRESS>wrote:
I'm still trying to verify but I notice that some of the changes are to .xtend files in the UI plugin. IIRC this was the spot where we had to commit the generated Java file(s) because of the jar-in-jar build issue. When you build the plug-in do you notice any dirty Java files that should be committed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm having a build issue locally.
Description	Resource	Path	Location	Type
The import org.xtuml.bp.xtext.masl.parser.antlr.lexer.jflex.MASLFlexer cannot be resolved	JFlexBasedInternalMASLLexer.java	/org.xtuml.bp.xtext.masl.ide/src-gen/org/xtuml/bp/xtext/masl/ide/contentassist/antlr/lexer/jflex	line 14	Java Problem
It looks to me like MASLFlexer.java is a generated file that is not being created for some reason.

There is a .gitignore for it, pushed in 84781ccb9586b39dcfca339c9d32eb6e67f7e5fa
Don't see why this would make any sense.
Dr. Jan Köhnlein
<EMAIL_ADDRESS>TypeFox GmbH
Am Germaniahafen 1
24143 Kiel
Phone: +49<PHONE_NUMBER>7
Skype: jankoehnlein
Twitter: jankoehnlein
Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385
Geschäftsführer: Sven Efftinge, Moritz Eysholdt, Dr. Jan Köhnlein

On 26. Apr 2017, at 17:11, Keith Brown<EMAIL_ADDRESS>wrote:
I'm having a build issue locally.
Description	Resource	Path	Location	Type
The import org.xtuml.bp.xtext.masl.parser.antlr.lexer.jflex.MASLFlexer cannot be resolved	JFlexBasedInternalMASLLexer.java	/org.xtuml.bp.xtext.masl.ide/src-gen/org/xtuml/bp/xtext/masl/ide/contentassist/antlr/lexer/jflex	line 14	Java Problem
It looks to me like MASLFlexer.java is a generated file that is not being created for some reason.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Should it be in the .gitignore or not?  Levi showed me how to use the "Run As > MWE2 workflow" on git/bridgepoint/src/org.xtuml.bp.xtext.masl.parent/org.xtuml.bp.xtext.masl/src/org/xtuml/bp/xtext/masl/GenerateMASL.mwe2 and now MASLFlexer.java appeared.

As the workflow is currently not run in the build and other files depend on MASLFlexer.java the build will fail.
So the .gitignore is wrong IMHO. But maybe you should ask Travis why he added it.
I'd remove the .gitignore and push the MASLFlexer.java.
Dr. Jan Köhnlein
<EMAIL_ADDRESS>TypeFox GmbH
Am Germaniahafen 1
24143 Kiel
Phone: +49<PHONE_NUMBER>7
Skype: jankoehnlein
Twitter: jankoehnlein
Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385
Geschäftsführer: Sven Efftinge, Moritz Eysholdt, Dr. Jan Köhnlein

On 26. Apr 2017, at 17:18, Keith Brown<EMAIL_ADDRESS>wrote:
Should it be in the .gitignore or not? Levi showed me how to use the "Run As > MWE2 workflow" on git/bridgepoint/src/org.xtuml.bp.xtext.masl.parent/org.xtuml.bp.xtext.masl/src/org/xtuml/bp/xtext/masl/GenerateMASL.mwe2 and now MASLFlexer.java appeared.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


SurfParams mistake

per RR:

 NRv7.2 should use AICEV=0.149 and AICEN=19.851 (matching MERRA-2).

AICEV and AICEN are not currently being used, but still should be fixed

fixed by https://github.com/GEOS-ESM/GEOSgcm_GridComp/pull/57


Fix get scalar array bug for VTK pane

There was a bug that would prevent scalars from being shown sometimes. This fixes it.
Here's code to see the difference (running off of vtki master branch - note there are several examples here that show this happening):
import vtki
import numpy as np

vtki.set_plot_theme('doc')
sphere = vtki.Sphere(radius=3.14)

# make cool swirly pattern
vectors = np.vstack((np.sin(sphere.points[:, 0]),
np.cos(sphere.points[:, 1]),
np.cos(sphere.points[:, 2]))).T

# add and scale
sphere.vectors = vectors*0.3

# plot the arrows and the sphere
p = vtki.Plotter()
p.add_mesh(sphere.arrows, scalars='GlyphScale', color=None, lighting=False, stitle='Vector Magnitude')
p.add_mesh(sphere, color='grey', ambient=0.6, opacity=0.5, show_edges=False)
p.show()

Codecov Report

Merging #372 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master     #372   +/-   ##
=======================================
  Coverage   86.63%   86.63%
=======================================
  Files          92       92
  Lines        7884     7884
=======================================
  Hits         6830     6830
  Misses       1054     1054

Impacted Files
Coverage Δ

panel/pane/vtk.py
30.32% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks @banesullivan


Support Signatories in KYCVerificationResult

Summary
Support Signatories in KYCVerificationResult because Signatories is required during onboarding and we should be able to check it from like /getAccountHolder call.

Hello @yuweihsu01, files in src/platforms* API's are deprecated and shall be removed soon. Please migrate to the new Adyen For Platforms.


Add TypeScript type definitions to wouter-types repo, publish to definitely-typed

Hello,
After 4 years of using React, I finally see a reasonable react-router.
There's just one thing I'd appreciate.
Could you please provide typescript type definitions? Either include it in this package, or add them to definitely-typed repo.
Thank you!

Alright, a few people have already been asking about the TS types. I've never worked with TS before, but I think I get the idea: we could add an index.d.ts file to the package with type declarations. This is definitely something I'll need a help with. I'm going to add a "Help Needed" tag to this issue, so if someone wants to contribute this might be a good place to start.

Be careful with typings if your project is not written in typescript and you do not plan to use it in a TS project any time. The problem is that if your typings are not up to date with your project code, you will have bugs in here that you cant/wont fix on your own. This hinders development greatly.
I would keep typings out of any project that is not TS based. Creating a separate project for types (or have it managed in definitely typed) is a good way to get started.

Perhaps adding the typings to the larger typings library where contributors can maintain it?

Ok, so I checked the TypeScript docs, and seems like adding types to definitely-typed is the most appropriate option. One thing I don't quite understand yet is how do I make sure the types correspond to the latest version of the library? Let's say I publish a new version to NPM, how do I make sure types in the repo are up to date?
Hope anyone could help me with that. Thanks!

Well, you would need to update the typings before you publish, or have somebody update them.

You match version number on typings package with this lib version number
and it should work out fine
On Wed, 24 Apr 2019, 12:29 Christian Engel<EMAIL_ADDRESS>wrote:

Well, you would need to update the typings before you publish, or have
somebody update them.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/molefrog/wouter/issues/5#issuecomment-486166904, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABYC6CBDXAGL7SUH4QLAIITPSAY7PANCNFSM4HGPGMKQ
.

And how does this solve the problem that would not be available for the recent version?

In that case it wouldn't. But it would signal TS users that they shouldn't
upgrade yet.
Could a possibility be having a .d.ts file in the root of this repo. And
keep it updated between releases?
On Wed, 24 Apr 2019, 13:30 Christian Engel<EMAIL_ADDRESS>wrote:

And how does this solve the problem that would not be available for the
recent version?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/molefrog/wouter/issues/5#issuecomment-486184307, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABYC6CEHXGIHPQXIYNJNIYTPSBAD5ANCNFSM4HGPGMKQ
.

This brings us back to my comment from above. If the author is not using TS for this project, it doesnt make sense to maintain typings here, since he would get the bugs assigned in this project and cannot take care of them. ¯_(ツ)_/¯

Hey guys! I see quite a lot of people are interested in TS support. I think I could migrate it to TS and open a PR for that. @molefrog How do you feel about going to TS?

I would leave the migration to the author - if he even wants to. What does it help if its typed afterwards but he cannot maintain it anyore? :)
Seriously - the only sane way is putting types on definitely typed. And somebody who cares about TS needs to maintain it. Forever. If thats not possible, drop the idea completely.

Hey, @yurist38 I appreciate the enthusiasm, but I must say I kinda agree with @Paratron and don't think rewriting the entire library in TS is a wise decision.
When I was designing the library I wanted it to be as minimal as possible (no deps, no transpilation). That's said I intentionally left out some features from React Router, just to make it cover 95% of use cases. Rewriting it in TS would add some complexity that I really think we would benefit from.
Again, sorry for rejecting this, but what you can help with however is creating contributing to https://github.com/molefrog/wouter-types by adding index.d.ts and later publishing it to definitely-typed. This is what I would need help with, since I'm not that familiar with TS world yet.

I don't really see a point why you are so scared by migrating to TS but no problem, it's completely up to you though.

This might not be the best explanation, but I just thought I should share this just to explain why exactly I'm leaning towards having everything in js.  This whole library was sort of an experiment around an idea that we can easily publish modern frontend libraries as-is, no babel, no transpilation, just plain ES6 (that's right) modules. An ES6 (ex ES2015) is currently fully supported by the majority of browsers, so ideally it should be up to a library consumer to decide whether or not this should be transpiled. That being said, if someone wants to support IE11 in their project, they should be aware that the transpilation stage needs to be enabled for node_modules as well. I should probably let people know in advance before they start using the library about this approach in the README.
So I know it's not entirely related, but having ts source will force us to introduce the transpilation (ts -> js) before publishing, and this just kinda breaks the concept 😊
Again, sorry for being stubborn, hope you get the idea!

Thank you for explaining that, I got the idea. But it still sounds a bit weird to me, to be honest. I simply don't see any benefit of such an experiment. Maybe I don't understand something, but from my perspective, the project won't lose anything if you add the transpilation stage to it. Opposite, most likely the bundle size will be even smaller and the codebase will be more reliable and bullet-proof with TS. Both transpilation and build will be done automatically in CI pipelines anyway.
About the README you're right, it's better to mention that it needs to be compiled to ES5 because most of the projects are ignoring node_modules folder on transpilation.

Hey, @mcongy, I added type definitions to DefinitelyTyped. npm install --save @types/wouter

@StrayFromThePath Thanks a lot for the help, appreciate that. I have added a section in README covering the TypeScript support:
https://github.com/molefrog/wouter/blob/master/README.md#can-i-use-wouter-in-my-typescript-project


Adding benchmarks to compare Patch model to Standard model

Work in progress

API change check
API changes are not detected in this pull request.

Closing in favor of https://github.com/annelo-msft/azure-sdk-for-net/pull/8


Implement dynamic checking of guesses (if correct or wrong) via websocket

was only done in server not in client


refactor/deprecate - hardware module

the hardware module was ported from the mycroft mark 2 in order to implement the mk2 enclosure, but it has some problems

unlike everything else in this package, this does not provide a plugin class to be used in a downstream entry point, it's just fully optional helper classes, conceptually I'm not sure they belong here or elsewhere
colors is a minimal implementation with hardcoded color values, it should use the color utils from lingua-franca, or at least we should not have 2 classes with same name in official ovos packages, makes code ambiguous and hard to import at same time
switches is not a abstract switch at all, it represents only the mk2 switch combination, this should be fully deprecated IMHO
fan is similar to switches, i could see an argument to keep it but dont feel the cpu_temperature doesnt really belong here, this should be fully deprecated IMHO
they all refer to "capabilties" which was a mark2 rewrite branch concept, it doesnt apply to ovos and that is dead code
they all ignore base event handlers from the PHAL base class, if we introduce methods for specific actions then those should be used in default event listeners from base class

i believe the LED class is useful since it is common across many plugins, so that one should be modernized and everything else dropped.

I'm not sure this should drag Lingua Franca and language parsing into a hardware interface; minimally I think the interface should include methods to accept and translate hex/hsl/rgb values to whatever the particular LED object wants.
I think the hard-coded values should be kept for primary/secondary colors and black/white only (red, orange, yellow, green, blue, violet, black, white). A plugin/skill could use LF externally to determine a hex/hsl/rgb value to pass to the LED object.
Switches and fan I am less worried about, but I do believe some abstraction is helpful so each plugin doesn't need to implement pull_up/pull_down setup and can just set config and get a binary "on"/"off" value to work with.
The fan I likewise think is helpful since there is common logic for how to manage fan speed based on CPU temp, but it may not be used in practice since ideally that would be controlled by the system.

Releated LED animation issue https://github.com/OpenVoiceOS/ovos-plugin-manager/issues/94

Right now, the animations are coded to use the Color class from OPM
https://github.com/OpenVoiceOS/ovos-plugin-manager/blob/09482f93729b1452279b6ea15bb9a188b0edad5d/ovos_plugin_manager/hardware/led/animations.py#L32
If this was loosened to use a tuple instead, plugins could use Lingua Franca for colors and still use these animations.

Perhaps a separate ovos-PHAL-plugin-leds is in order?  Then it can accommodate for several different types?


Hidden settings icon and misplaced brightness slider

Description
The brightness slider is misplaced and also you can access the settings app with an invisible settings icon.
Steps to reproduce
Screed recording placed inside Zip file
Screenrecord and Logs.zip
ROM info
Aosp Extended 5.3 (8.1 Oreo)
Moto G 2015 Osprey
Xposed 90.3 Beta
Module version (build version)
Android P-ify snapshot 0.1.0 alpha #26
Xposed log / logcat
Both are placed inside the previous Zip file

Screenshot?

Inside the zip file there is a screen recording to better demonstrate the issue

Anyway, here are some screenshots :grin:

I can confirm the hidden settings icon

Brightness slider at bottom is because of your ROM.

Oh I see, then I guess the only issue would be the settings icon :)


Icons are not getting displayed for Copy, Done etc on iPhone iOS 10

I have integrated the FLEX library in my app but i am sometimes not getting the icons for Copy, Done etc in the explorer.

@DotzuX this is not the repo for FLEX, and I don't know FLEX well enough to help with this.


Nuget name improvements

Description of Change
One additional commit which adds the nuget Analyzer tests and name updates.
This is on top of my other pr since it needs the dependency object changes.
Have test cases been added to cover the new functionality?
Yes

Can one of the admins verify this patch?


CONTAINS relationship automatically added when using parse_file(file_name) function.

I am contacting you to confirm the specifications of spdx-tools.
After converting test1.spdx.txt to JSON format using the functions parse_file(file_name) and write_file(document, file_name), “SPDXRef-testpackage CONTAINS SPDXRef-testfile” is added.

See test1.json.

After converting test2.spdx.txt to JSON format using the functions parse_file(file_name) and write_file(document, file_name), “SPDXRef-testpackage CONTAINS SPDXRef-testfile” is not added.

See test2.json.

The only difference between test1.spdx and test2.spdx is the order of the package information and file information.
I am using spdx-tools v0.8.2.
Is the addition of “SPDXRef-testpackage CONTAINS SPDXRef-testfile” a specification?
Is it a specification that “SPDXRef-testpackage CONTAINS SPDXRef-testfile” is added or not depending on the order of package and file information?
Best regards,

From https://spdx.dev/wp-content/uploads/sites/31/2023/09/SPDX-specification-2-2.pdf the relevant statements are:
When implementing tag:value format, the positioning of File elements is syntactically significant:
• Files are assumed to be associated with the Package Information that immediately precedes it, if a package exists.
• If a package contains files, the File Information section must follow its Package Information section.
• If a File is not part of any package, it must precede any Package Information section reference in the SPDX document.
So it seems that it is behaving correctly.
On 11/1/24, 7:12 AM, "Yasutake Kurita" @.***> wrote:
I am contacting you to confirm the specifications of spdx-tools.
After converting test1.spdx.txthttps://github.com/user-attachments/files/17600400/test1.spdx.txt to JSON format using the functions parse_file(file_name) and write_file(document, file_name), “SPDXRef-testpackage CONTAINS SPDXRef-testfile” is added.
·         See test1.jsonhttps://github.com/user-attachments/files/17600383/test1.json.
After converting test2.spdx.txthttps://github.com/user-attachments/files/17600401/test2.spdx.txt to JSON format using the functions parse_file(file_name) and write_file(document, file_name), “SPDXRef-testpackage CONTAINS SPDXRef-testfile” is not added.
·         See test2.jsonhttps://github.com/user-attachments/files/17600384/test2.json.
The only difference between test1.spdx and test2.spdx is the order of the package information and file information.
I am using spdx-tools v0.8.2.
Is the addition of “SPDXRef-testpackage CONTAINS SPDXRef-testfile” a specification?
Is it a specification that “SPDXRef-testpackage CONTAINS SPDXRef-testfile” is added or not depending on the order of package and file information?
Best regards,
—
Reply to this email directly, view it on GitHubhttps://github.com/spdx/tools-python/issues/834, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHQIMJ3SL5QHC2OU6YUPJRDZ6OD2JAVCNFSM6AAAAABRAKX276VHI2DSMVQWIX3LMV43ASLTON2WKOZSGYZDSMJSGA2TONQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

@billie-alsup
Thank you for providing an answer to my question. I really appreciate it.
I confirm that the pdf contains the following information. And I also understood that the tool specification is based on the following content.
Thank you for your help.

By the way, the pdf is the SPDX 2.2 specification, is the same written somewhere about the SPDX 2.3?
From https://spdx.dev/wp-content/uploads/sites/31/2023/09/SPDX-specification-2-2.pdf the relevant statements are:
When implementing tag:value format, the positioning of File elements is syntactically significant:
• Files are assumed to be associated with the Package Information that immediately precedes it, if a package exists.
• If a package contains files, the File Information section must follow its Package Information section.
• If a File is not part of any package, it must precede any Package Information section reference in the SPDX document.
So it seems that it is behaving correctly.


SIP bypassing for main application also on IDE

We Bypass SIP on two occasions: executing the user's application, and when the application executes other executables.
The first one is currently only done in the CLI, so if a user tries to run a SIP application (Maybe a bash script, if there is IDE support for that?) in the IDE with mirrord, the layer would not be loaded into the application, and the application would run alone.
The second kind is handled also on IDEs, so if the user's application is not SIP, but executes SIP binaries, we do handle that (by hooking execve), assuming the executable's path is ignored by the file hooks (otherwise we would try to read the file for SIP handling, then we would hook the file open, try to open it in the cloud, not find it, return "File not found", the SIP detour would fail, and the executable would be executed without the layer loading into it).
If you would like to have support for executing SIP binaries with mirrord in an IDE, please let us know and we will prioritise it :)

Whenever there are developments in this issue, the part about SIP in the FAQ should be updated accordingly.

In vscode we modify the debug configuration on launch in order to inject the layer. Unfortunately there is no universal "executable" configuration field that specifies what will be the command that is run. The value of the program field is just an argument to the executable, when running programs written in interpreted languages (config.program might be main.py, but the executable that has to run is the python interpreter).
I think we could sidestep SIP by replacing the interpreter, and debugging would still work, but I am not sure of it.
If we want to replace the interpreter the same way we set the environment, by modifying the debug configuration, we would have to have custom code for each interpreted language, and we would only support sidestepping SIP for those debug types. This is because the interpreter config field is different for each debug type.
For example, with the built-in debugger type node, config.runtimeExecutable sets the interpreter, but for python its config.python.
This approach might lead to a situation where users decide to use some new interpreted language on Mac with a dedicated vscode debugger extension, and we would have to quickly add a couple of lines to our extension's code in order to support that debug type. The change itself would not be difficult, we would just have to find out the name of the field that is used to specify the interpreter with that debugger, and add
if (config.type === "thisnewdebugger") {
    let patched_interpreter_path = sip_patch(config.interpreter); // simplified code
    config.interpreter = patched_interpreter_path;
}

So supporting new debuggers would probably mostly not be a problem, but users might have to wait a bit for support, and some users might just give up on mirrord without ever asking us to add support for their weird debugger.
Is this ok, or do you think there is a good way for us to switch the executable that is being run in a way that is debugger-type-agnostic?
My guess is that if there is another way to do it it's so complicated it's not worth it, but I wanted to write all of this down so that you can let me know if I'm wrong about this.
There is another way I can think of, but it has many flaws. One of them is that it assumes the interpreter executable is always going to be specified as just the name (python, node) and not as a path, so if that assumption is wrong this method will not do.

We iterate all configuration fields in the assumption of one of them has to be the interpreter executable if this debug type is of an interpreted language (if it's not interpreted we're fine anyways). We try to SIP-patch each of those fields. Any successfully created patched binaries will be created in mirrord's temp dir.
We put mirrord's temp dir at the front of the PATH environment variable.
Now when the interpreter is executed, the patched version is the first in PATH so it's the one that is going to be executed.

I think it's okay to have implementation per launch type for time being.

Done for vscode (for node and python - other config types need to be added to a mapping) in #1069.
Still not supported on JetBrains.

Did we experience this on JetBrains?

Did we experience this on JetBrains? if not I suggest to close this and open when we have a solid situation :)

Ok, closing.
If you are a mirrord user and would like to have support in the mirrord JetBrains plugin for running interpreted scripts where the interpreter is SIP protected (e.g. because it has a #!env ... shebang), please comment here and we'll prioritise adding support for that.


[AutoPR] operationalinsights/resource-manager

Created to accumulate context: operationalinsights/resource-manager

(message created by the CI based on PR content)


[UMBRELLA] Kubectl independence: releasing

Part of #114.
Improve Kubectl independence by releasing independently.
Kubectl is currently released as part of core kubernetes, on a 3-month schedule.
The goal of this issue is to track the feasibility of releasing independently, and the challenges and improvements that needs to be done.

A couple of thoughts on releasing:

Ideally, this repository is go get-able, so you can get kubectl by just running go get k8s.io/kubectl/cmd/kubectl,
If we want to maintain multiple versions, we can use gopkg.in and branches,
We could provide tarballs with pre-compiled versions for people who don't want to install the go suite.
We could create ubuntu/homebrew/distro-specific packages

/remove-lifecycle rotten


Show gzip information for the resulting index.html file

It would be nice to also show gzip for the resulting index.html file.
For this to work first https://github.com/vitejs/vite/pull/12485 needs to get merged.
Than we also need to allow reportCompressedSize to be true which is disabled at the moment.
I'll provide a PR for this!

Can you better explain the use case for this?
Turning it on won't break the plugin, but it does add a bit more delay in the build process, and I'm struggling to understand the situations where this information would be useful.
This plugin is designed for compiling a web app into a single (and uncompressed) HTML file, so you can open and run it from a file system directly.
Using this plugin to build a site that is served via a web server would normally be a bad idea, since it subverts all of the performance benefits that come from modern web servers and bundlers: parallel connections, partial caching, on-demand asset loading, not having to base64-encode binary assets, not having to block compilation and rendering until the whole page loads, etc.
I can imagine using it for some limited-capability embedded system web servers, like ESP8266WebServer, but those don't tend to support on-the-fly compression anyway.

I'm happy to explain!
My use-case is the second one you have mentioned. I'm deploying to a very limited embedded device. Like expected one-the-fly compression is not supported, but it looks like the embedded webserver can diliver pre-copressed assets. Because the flash memory is very limited I need to keep an eye on the the bundle size.
As I see it the option reportCompressedSize does absolutely no harm to vite-plugin-singlefile. Users that don't want or need the gzip target size being reported can just disable the setting. Users like me that are interested in this information should be able to use it!
@richardtallent If you think it is necessary I can add a note to the README and advice users to disable reportCompressedSize which is on by default!?

Thanks, makes sense now, fixed in 0.13.5!


bug:

Hello, I got a quick question:
I'm getting TypeError: Image or Canvas expected when using the following code.
const resultbg = await fetch("https://cdn.discordapp.com/attachments/725418862346240070/747769058283225158/Capture.PNG ");
    const bg = await resultbg.buffer();
    let img = new Canvas(400,180)
    .printImage(bg, 0, 0, 400, 180)
    .setColor("#ffffff")
    .setTextSize(27)
    .addText(name, 10, 10) // name = mentioned user or author's username
    .setTextSize(18) // rest of profile...```

Is the picture not in an acceptable format? What did I forgot to do?

I'm really sorry about using the wrong template.


docs(onboarding): don't recommend editor

By submitting this PR, I am indicating to the Numberscope maintainers that I have read and understood the contributing guidelines and that this PR follows those guidelines to the best of my knowledge. I have also read the pull request checklist and followed the instructions therein.

Don't recommend/approve a specific editor for use with Numberscope. Keep note that VS Code works well with Vue.

Looks good to me. Merging.


Allow client to request subset of ensemble model outputs

Problem:
A common use case of ensemble model is preprocess -> inference -> postprocess. In most case, user will request last step output (postprocessed inference), as it might for example reduce networking between Triton & Application. But often, the application might also require the raw inference result (intermediate output). The current configuration & client interface (at least the Python one), seem to support requesting a subset or all the output (Python client takes a list of InferRequestedOutput). But for some reason, requesting a subset of all output results in InferenceServerException: [StatusCode.INVALID_ARGUMENT] in ensemble, [request id: ] unexpected deadlock, at least one output is not set while no more ensemble steps can be made.
Solution:
As of today, the only solution I found is to create 2 ensemble model (or actually N - 1 ensemble where N is the total number of steps):

preprocess -> inference
preprocess -> inference -> postprocess
Then, my client is either requesting output from first or second ensemble model. Not ideal as it introduce unnecessary complexity.

CC: @GuanLuo


arch/risc-v/src/common/riscv_initialstate.c: Fix stack pointer in coloration

Summary
The logical CPU index should be retrieved with up_cpu_index(); the riscv_mhartid() returns the actual hart id of the SoC.
For mpfs target for example, NuttX can run on a single HART, for example on mhartid 2, but there is still just one logical CPU for the NuttX.
Impact
risc-v target with more than 1 hart, NuttX running on some other than hartid 0
Testing
Tested on mpfs platform, running NuttX on hart 2

Hi @jlaitine could you test this on rv-virt:smp, just to be safe? Thanks!

Hi @jlaitine could you test this on rv-virt:smp, just to be safe? Thanks!

built the target, tested with
qemu-system-riscv32 -semihosting -M virt,aclint=on -cpu rv32 -smp 4 -bios none -kernel nuttx -nographic
Runs fine!


Sample time delay insufficient for normal tolerance

The time delay between i2c write and read operations is insufficient to cover the natural part to part variation of ADS1x15 devices. The consequence of this is that some parts return the previous reading whenever queried. This issue only becomes apparent if the gain value changes between two conversions as the value returned will be correct for the previous gain setting.
Currently a delay of (1.0/data_rate + 0.0001) is used.  The datasheet for the ADC states that the sample rate varies up to +/-10%. So, to avoid this potential issue the delay should be changed to (1.0/(0.9*data_rate))

This new library's implementation does properly handle the part to part
conversion time variation as it actually queries the device to see when the
conversion is complete.
It does have a little bit of room for improvement though as the _read
function waits in increments of 10ms if the _conversion_complete query
immediately after the _write_register call returns false. I haven't tested
it but I would guess that for all but the very fastest data rates on the
ADS1015 this first check will always come back indicating incomplete,
forcing a wait time before that next check that is excessive for all but
the lowest data rate setting of the slower ADS1115. This penalty will
severely limit the user's ability to make multiple rapid single conversion,
likely 50-100 samples/second, even when they believe they are using a much
faster data rate.
I would recommend some modifications that changed depending on how closely
you'd like to complete relative to the ADC's conversion completion.
1A. Add a sleep of 1.0/data_rate, the nominal conversion time, before the
while loop checks for conversion completion
2A. Add a sleep of 1.0/(data_rate*1.1)), the minimum conversion time,
before the while loop
Followed by a change to the sleep time within the loop:
1B. A sleep of 1.0/(data_rate0.10) should loop at most once for case 1A or
twice for 2A above and adds minimal i2c traffic but fully covers the -10%
sampling rate condition
2B. A sleep of 1.0/(data_rate0.01) should loop at most 10 times for A1 and
20 times for 2A. This will let you more closely catch the ADCs completion
For 2B you could even monitor the average number of additional iterations
the specific device requires and add that much extra time to the sleep
before the while loop.  This will reduce the i2c traffic.
On Sun, Nov 18, 2018 at 11:22 AM ladyada<EMAIL_ADDRESS>wrote:

hiya - we'll be deprecating this library soon and replacing it fully with
the circuitpython version which will be supported (we're waiting on one
more breaking interface change before archiving this library for good)
can you check out
https://github.com/adafruit/Adafruit_CircuitPython_ADS1x15 and see if
that does the right thing?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/adafruit/Adafruit_Python_ADS1x15/issues/12#issuecomment-439713859,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArCxbBEbWSU_BvHvdsPGcARiZdC-0zBFks5uwaVegaJpZM4Ynvtg
.

ooh do you mind either submitting a PR or adding an issue to that repo? that way we will see it next time we do a sweep thru the librayr! it would be appreciated

Sure :)
On Wed, Nov 21, 2018, 9:50 AM ladyada<EMAIL_ADDRESS>wrote:

ooh do you mind either submitting a PR or adding an issue to that repo?
that way we will see it next time we do a sweep thru the librayr! it would
be appreciated
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/adafruit/Adafruit_Python_ADS1x15/issues/12#issuecomment-440735666,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArCxbNmEh2SAXwvm9HoO883b5aDNxSBZks5uxYRYgaJpZM4Ynvtg
.

Hi! We are deprecating this library. This issue is either fixed or may need updating for the new library:
https://github.com/adafruit/Adafruit_CircuitPython_ADS1x15
Please see issue summary here:
https://github.com/adafruit/Adafruit_Python_ADS1x15/issues/13


CEP for Conda Deprecation Schedule

As we seek to remove outdated code and bring conda and conda-build back into the modern Python era (#24) it's more important to define a clear deprecation policy such that downstream applications are properly notified of pending deprecations.
This proposed deprecation policy hinges on ideas from #26 so much of this could be reworked pending modifications made there.

@conda-incubator/steering
This pull request falls under the Enhancement Proposal Approval policy of the conda governance policy, please vote and/or comment on this PR.
It needs 60% of the Steering Council to vote yes to pass.
To vote, please leave a regular pull request review (see Files changed tab above > green Review changes button) with one of the following options:

Approve for yes
Request Changes for no.

Also, if you would like to suggest changes to the current proposal, please leave a comment below, use the regular review comments or push to this branch.
This vote will end on 2022-10-07.

@beckermr Hm, no, we haven't decided on how we decide on what gets deprecated. This CEP is a response to the realization that as we tackle tech debt, we keep finding functionality that is outdated/unused or has long since been replaced. This is intended to be more of a warning system for downstream projects and to inform them of the correct alternative.
Yes, we should view the pending deprecation as a comment period. It wouldn't hurt to outline a process for disputing a deprecation, I'll put something together.

No, we are not zero padding months in CEP8

@beckermr just added details on:

how the pending deprecation state is also a comment period
how to dispute a deprecation (raise an issue with details)
how disputes are resolved if there is an impasse (steering council vote, same as a CEP)

Let me know if you have additional concerns

Thank you. That looks great! If we create a technical group sometime in the future we should appeal decisions to them.

We could probably get away with using DeprecationWarning only (since Python's PendingDeprecationWarning is a bit deprecated itself) and use comments / deprecation tooling to note exactly how deprecated something was.

@jezdez it's gone passed a suggestion 😁
https://github.com/python/cpython/blob/b863b9cd4b8681cf5fff5f121837a1039045783f/Lib/warnings.py#L498-L514


Create FOUR separate Tune Twins Games

The Congo data collection will need to have four versions of the game that can be accessed independeltly. They will be to run each version of the game as a single game, without randomization

Original
Pitch
Spectral
Rhythmic

Each will have its own playlist, supplied by DJB or JL

NB this is probably going to be possible without any programming involved (through the admin interface).

Ok, great, though might actually close/resolve this issue since at our workshop last week, we decided we might take a different route to this (filing that now)

Yes! You are right, Berit! Thanks!


Fix logo aspect ratio and adapt navigation

I noticed that the GURPS logo was compressed when it was added in the last update so I made some tweaks to fix that. Nothing personal but JQuery makes me itch, so I swapped that out in gurps.js for perfectly good JS.
Here's what the update looks like:

As mentioned in my DM... I included the fix (in spirit), so I won't be merging this PR.

As mentioned in my DM... I included the fix (in spirit), so I won't be merging this PR.

This looks good! Even through this was a very small change, could you create a branch and submit a PR next time?

This looks good! Even through this was a very small change, could you create a branch and submit a PR next time?


folders: sub folder items extract into tracked item folder.

https://pastebin.com/raw/7W4ALmKy

Can you be more specific with your issue? A vague title and Pastebin link isn't that helpful. Looking at the Pastebin I'm guessing this is a feature request, correct?

@Njinx - This users is watching a folder named TV. A folder named STP is copied into TV that contains sub folders with rar files. The things being extracted from those rar files ends up in the STP folder and not the sub folder where the rar files are at.
The request is for the extracted items to go back into the sub folder, not the tracked item folder (STP in this case). The conversation leading to this issue is in my Discord.

@davidnewhall I see. While whether you want to implement this is obviously up to you, it looks like this feature is probably out of the scope of this project and @ZeroPoke might want to look into Sonarr or another media management program.

It's not out of scope. It's a bug.


fix startupOptions mode bug

the class MySqlSourceConfigFactory is not support the new startupOptions

Other startup modes are note supported now.

@TeriMoni Thanks for your contribution. But we need to improve the PR  to really support these options, currently the underlying code does not support these options, thus your change is not enough.

These start up modes have been added in #1661. Close this PR.


OutlawN

New Port for { OutlawN }
Game Information

Title: { OutlawN }
URL: { https://programancer.itch.io/outlawn-retrogradejam2 }

Submission Requirements
CFW Tests
Ensure your game has been tested on all major CFWs:

[x] AmberELEC
[x] ArkOS
[x] ROCKNIX
[x] muOS

Resolution Tests
Test all major resolutions:

[x] 480x320
[x] 640x480
[x] 720x720 (RGB30)
[x] Higher resolutions (e.g., 1280x720)

File Structure

Your port should have the following structure:

portname/

port.json
README.md
screenshot.jpg
cover.jpg
gameinfo.xml
Port Name.sh
portname/

Additional Resources
For an in-depth guide on creating a pull request, refer to: PortMaster Game Packaging Guide

Why is the pull request for a new port?
In the PR you write down what the PR is all about.


Remove aw kv1

Motivation and Resolution
@haroune-mohammedi @fracek  @ivpavici
Many projects using Starknet.js have errors during the import of the library.
See Abi-wan Telegram for examples.
One example with the get-starknet project, if using Starknet.js v6.1.1 :

After this PR, no more messages.
Usage related changes
The guides have not been modified, as nothing is related to v1.
Development related changes
Remove all code related to abi-wan-kanabi v1.
V2 code unchanged.
Checklist:

[x] Performed a self-review of the code
[x] Rebased to the last commit of the target branch (or merged it into my branch)
[x] Updated the tests
[x] All tests are passing

Seems to be problem to pass tests.
On my side it works :


What is your roadmap for the missing parts of the end to end process?

Initial Question:
The roadmap in the email (below)doesn’t state when the obligations or indeed the calculations will be available in live, instead it mentions they’ll be available in simulation from end February. What is the schedule for this as we would need to be very confident this will manifest before the quarterly deadlines – but also from a usability perspective this also means our Users can’t request liability estimates when they want, which would seem one of the only benefits of MTD during Public Beta.
SDS Response:
A further API release is planned for the end of February and the current plan is to include:
• Expanding the Get business and property information elements to include Business name and address as well as accounting period and accounting type.
• Introduction of test stubs for the following:
• Simulating the ability to get the customers update obligations for self-employment and property businesses
• Ability to simulate sending an update on interest income information
• Agent Access – simulating the check whether an agent is authorised to act on behalf of the taxpayer and sending an update on their behalf.
• Subscription to MTD – simulating the check to find out if a customer has subscribed to MTD
• Get calculation – providing a mock calculation response that aligns with the output that will be received from the strategic calculator once all the APIs are in place.
PT Response:
I did read this, as I had to in order to form the question.  My question was what does this mean?  When does it go live?  Is it 2 weeks between being available in simulation to being available in production or is it 2 years?  As far as IRIS are concerned, we need to know everything about your roadmap – this is our development effort and our development teams working on our live products.  We cannot suspend all activity on our product suite to anticipate things coming from HMRC, especially if the design is not specified in advance and there’s potential for us to have to redesign as well as integrate.

Hi P-Tracy,
As this is a non-technical question, I have forwarded this to SDST for you. They will be in touch with you via e-mail.
Thanks,
Jacob

Hi Pauline,
Sorry for the misunderstanding, detail was added to your question not as a response but as context to help with answer from our delivery team. Formal answer will be provided early next week.
Thanks,
Dennis


Source Request: Zoro / Zoroxtv

Source name
Zoro
Source link
https://zoroxtv.to/
Source language
English
Other details
There is an extension in the repository with a file name of zoro, but its extension name is HiAnime. This is another website, but uses the same zoro theme, I think.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

It was the relan zoro previously. Item recently change ip address to aniwatch.to then again to hianime.to
The zoro you're saying is just a copy of the original


typo in "about" on the github page

Quick and dirty backup tool benchmark with reproductible results

-> reproducible

Yes, I did write it as in french... Thanks.


Background Image instead of Background Color

Could anyone point me in the right direction to set a Background Image instead of a Background Color?
Specifically for the Stage.

That is not a feature in the current editor.

I'd be satisfied with a hacky few lines of JS to enter in the console. I found:
this.app.editor.webgl.stage.children[0]
and
this.app.editor.canvas2d.stage.children[0]
depending on the renderer toggle
seems to be the ref to the background sprite
but modifying the _texture._baseTexture.imageUrl doesn't seem to do the trick.
Heck, if there were a few lines to set the background alpha to 0 for the stage and the canvas I could hacky add an image behind it in the dom
end goal is our creative team to test+modify+tweak particle animations on top of a screenshot of where it will be used in final media without having to run build pipelines.
I can't decide whether to solve from this.app or from this.PIXI , plz forgive, thanks a-plenty

Going into the private variables of Sprite/Texture definite won't get you anywhere in this case. I think you'd want something like ...children[0].texture = this.PIXI.Texture.from(<background url of hosted file somewhere>)


Add LICENSE file, update README to point to it.

We were having trouble with a missing license in one of our PRs here:
https://github.com/sigstore/policy-controller/pull/236
So, this PR adds a LICENSE file just like here:
https://github.com/alibabacloud-go/tea/blob/master/LICENSE
And I updated the README.md to point to it just like here:
https://github.com/alibabacloud-go/tea/blob/master/README.md
For consistency.
Signed-off-by: Ville Aikas<EMAIL_ADDRESS>

similar PR: https://github.com/alibabacloud-go/cr-20160607/pull/1

Sorry, this is automatically generated and cannot be modified in this way. We will fix it as soon as possible.


就是GFW的问题，没有正确科学上网去 go get

go version go1.4.2 darwin/amd64，使用proxychains-ng挂的shadowsocks，go get同样不成功.

@CodeFalling Go is not a dynamic build binary, so its never load a network shared library, proxychains is base on injecting a shared library, so its not working with Go, and almost all go binaries.
But it use the http_proxy and https_proxy from env.
I hope its related, since I use google translator to read the topics.

@fzerorubigd Thanks for pointed out that.Set all_proxy works great.


Enhancement: Result display issues

Result display is currently scrollable and has long outputs which make it hard to read and forces the user to scroll through the result display in order to read the help message

Clients returned are crammed together and colon and semicolon are hard to distinguish

Response message when editing a client still scrollable

Same for delete

Response message when editing a client still scrollable

Same for delete

I think horizontal scrolling is fine for cases like u showed in delete where the information is just too long. If we wrap it and try to fit super long clients and their details within the box it might look messy imo. Another thing we can do is only display certain attributes to prevent overflow. What do u think @dillontkh also my main reason for this enhancement was to prevent vertical scrolling and limit it to 4 lines

 Response message when editing a client still scrollable  Same for delete

thanks, should be resolved now @dillontkh


VirtualizeListView contents disappear when changing monitors of different DPI

Symptoms:

Content disappears or gets cut off when changing between Windows of different DPI

Reproduction:

Create a VirtualizeListView, populate with contents
Drag application between monitors, one set to 100% scaling, the other set to 150% scaling.
Observe content disappear.

Reproduction Repo: Pending
https://github.com/user-attachments/assets/d6523a89-c86b-434f-98cf-8a5b76d03023

Just tried to reproduce, but everything works as expected. Used Sample project from this repo

I forgot to add that my monitors are also different resolutions.

@daltzctr please try v 1.2.0


[BUG] Bootloader cannot reflash after the flash of a gate

** Which version the bug has been detected **
Luos engine 2.4.2
Describe the bug
Each time we flash a gate with the bootloader, so finally we have 2 gates and 2 pipes, and we want to reflash the node, the node is not responding, so we cannot reflash. However the network continues working, if we launch a detection we still have the 2 gates and 2 pipes
Network configuration

and we flash with a gate binary.
How to reproduce the bug
Flash 1 time with a gate binary, and then try to reflash with any binary.
Additional context
Add any other context about the problem here.
Don't hesitate to add screenshots or to link an entry from the forum.

This was a Pyluos bug and it is resolved here: https://github.com/Luos-io/Pyluos/pull/144

Correctet in Pyluos release 2.2.2


Fix Bulk split error substatus

Packages impacted by this PR
@azure/cosmos
Issues associated with this PR
Describe the problem that is addressed by this PR

On a partition error gone error in bulk calls, substatus in the error needs to be checked instead of subStatusCode.
Update ChangeLog with just the split proof support in bulk API. Currently our SDK as a whole does not support merge.

What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


Methods to assign charge during or after atomtyping

The workflow we've been using with OPLS doesn't work for most forcefields. In Amber, for example, non-bonded VdW and bonded interactions are specified through atomtyping but partial charges are assigned after atomtyping using antechamber, which uses AM1-BCC. In other words, a given atomtype may have different partial charges if it's used in different molecules. (One such example is n-chloroalkanes, in which the chlorines have different charges than hydrogens but only one atomtype is used for the carbon, which can result in non-zero total charges on the molecule).
The major limitation that comes to mind is that AM1-BCC is only to be used on small molecules. A large system would need to be broken down into residues, molecules, or characteristic moieties, passed to antechamber or an equivalent, and then replicated back to the whole system.

So,
antechamber is installable in conda:
conda install -c omnia ambermini

And isn't too hard to run. Here, I run it on a propylene carbonate molecule and store the charges in an output mol2 file.
$ time antechamber -i prcarb.pdb -fi pdb -o prcarb.mol2 -fo mol2 -c bcc -nc 0
Total number of electrons: 54; net charge: 0

Running: //anaconda/bin/../bin/sqm -O -i sqm.in -o sqm.out

real	0m0.297s
user	0m0.264s
sys	0m0.025s

And we can obviously grab these charges in parmed:
>>> import parmed as pmd
>>> pc = pmd.load_file('prcarb.mol2', structure=True)
>>> [atom.charge for atom in pc.atoms]

So it's easy enough to generate these partial charges and store them. But given AM1's inability to scale past small systems, this would need to be run on single prototype molecules, which, as far as I know, isn't really how atomtyping works right now.
One idea I have (say I have an existing gaff.xml file with correct information and partial charges of 0 in <NonBondedForce>):

Atomtype the system as normal so the rest of the topology has bonded and LJ terms
Pass a list of residue names to a function that slices out a single residue of each type
Run an antechamber wrapper on this slice
Grab the generated partial charges and map them back onto each copy of this residue

This works in my head and should work for a box of small molecules (or a more complex system in which only its small molecules are passed to this function). This certainly wouldn't work on big slabs and might not work for polymers unless each monomer is accounted for as a single residue.
Any thoughts? Worth pursuing this approach?

The basic procedure that one needs to apply here is conceptually simple but hard to implement in a general way. It's most established for proteins and nucleic acids (and is where the charges in those force fields typically come from) so you may want to see what's been done there. Basically, you "slice" (to use your term) a piece of the system out, cap it in a way so that the caps don't affect its electronic structure much, compute charges, remove the caps, distribute residual charge from the caps back across the slice so that it still has the proper formal charge, then link it back into the larger chain.
It's conceptually simple. The main problems, as I understand it, relate to finding a general way to pick where to slice so that you end up with electronically relatively decoupled regions so that your charges aren't (a) artificial and (b) totally dependent on where you picked to slice.
If you have an OpenEye license, I think OpenEye is working on a general approach for this it might be possible to try out.
I'm also happy to discuss briefly by phone if you guys want.

Thanks for your comment, looks like I wasn't too far off the mark. Could you share some references that demonstrate this? I looked around a bit but I'm not familiar with the biophysical literature and I only found its use in small molecules.
I'm not working with any polymers/biopolymers at the moment, so I was thinking about doing a simpler implementation that was limited to small molecules. Obviously we would want to support arbitrarily large molecules in the futures but this might be useful as a first step (and it would be more useful for my research in the immediate future, so I can start using GAFF and forcefields that rely on setting partial charges).
Thoughts guys? Want to wait until @ctk3b is back to chat or is this worth implementing now?

Check out Automated Topology Builder (and some of their associated papers linked on the website). They go into detail with regards to the different methods for chopping up the system and different ways of getting charges.
https://atb.uq.edu.au
A workflow that calls another tool for getting the charges would of course be useful, but given the way mbuild/foyer are currently designed/implemented, dumping these parameters and their associated charges to a custom, reusable force field file would probably be the way to go.  We can create a catalog of molecule specific GAFF forcefield files.
This might actually be a good way to go, as I’ve read papers that just say “we got charges from ATB” but they don’t list the charges or list which scheme from ATB they used, so the work is not reproducible.  Having these force field files would remove any ambiguity as to which parameters/charges were actually used.
On Jul 3, 2017, at 9:05 AM, Matt Thompson <notifications<EMAIL_ADDRESS>wrote:
Thanks for your comment, looks like I wasn't too far off the mark. Could you share some references that demonstrate this? I looked around a bit but I'm not familiar with the biophysical literature and I only found its use in small molecules.
I'm not working with any polymers/biopolymers at the moment, so I was thinking about doing a simpler implementation that was limited to small molecules. Obviously we would want to support arbitrarily large molecules in the futures but this might be useful as a first step (and it would be more useful for my research in the immediate future, so I can start using GAFF and forcefields that rely on setting partial charges).
Thoughts guys? Want to wait until @ctk3bhttps://github.com/ctk3b is back to chat or is this worth implementing now?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/mosdef-hub/foyer/issues/122#issuecomment-312684058, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABW4q8m4uiTKmu4XD573qw6ZvcbGFtzbks5sKRFagaJpZM4NfX7E.

Thanks for the note on ATB - I hadn't realized they discussed these issues on there so I'll have to look.
Let me know if I can be helpful at all.
Regarding having files versus having charging procedures -- I have always felt knowing the origin of the files is even more important than having the files themselves. The worst case scenario is, as you describe it, papers which just say "We got charges from ATB" without saying which/how, but it's still less than ideal to say, "We got charges from ATB and here are our files," as one still doesn't know where they came from.  Who knows what it really is? I'd much rather have, "Here are my files, and here's the algorithm I used to generate them."
If you do implement something along these lines, can you try and do it in a way which is not Foyer-specific? We'll ultimately need something for blocking too, and it would be nice to be able to reuse rather than rewrite.

The JCTC paper about ATB has a lot of good details:
http://pubs.acs.org/doi/abs/10.1021/ct200196m
As does their most recent paper on improving it (I don’t have access to the full journal, but NIH has a mirror):
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3590896/
I agree with you, having the files and information about how they were generated is probably a better way to ensure reproducibility than just the files alone.  However, we also need to make sure we are including what structure was given to the code to calculate the charges. That is, did we provide the whole molecule or just a smaller fragment and what was the fragment?
We just had issues trying to reproduce someone’s charges they got from ATB; at first I thought it might be because we were using v2 not v1.2 (v2 has improved methods), but upon digging deeper, discovered they only fed ATB the heagroup (with very short tails capped off), making the (reasonable) assumption that the tail beads have the same charges (which is certainly useful when the goal is to vary tail length)…but of course, it would have been nicer just to have those details to begin with (which is certainly where coming up with some best practice checklists would be great).
We can automatically have all this information if we encode this all into a well defined python script/workflow  where the structure is defined in say, mbuild, with that structure passed to a code to calculate the charges, and everything gathered back and dumped to a composed file, we would have all the information we need to reproduce the work (assuming this script is included with the publication or in a linked git repo).
The secondary issue with this (and something we talked about with you a few months ago) is that this would introduce a whole bunch of new atom-types for any case where the charge is different.  However, if we are generating this in an automated way AND using SMARTS to define the usage, this is less of a significant issue than if we did this all by hand or tried to include these parameters in some general force field library, rather than just a custom file for a specific molecule (recent changes to mbuild/foyer allow you to atom-type on individual components, not just the whole library, although I’m sure these have been pushed to the main repo yet).
On Jul 4, 2017, at 9:28 AM, David L. Mobley<EMAIL_ADDRESS>wrote:
Thanks for the note on ATB - I hadn't realized they discussed these issues on there so I'll have to look.
Let me know if I can be helpful at all.
Regarding having files versus having charging procedures -- I have always felt knowing the origin of the files is even more important than having the files themselves. The worst case scenario is, as you describe it, papers which just say "We got charges from ATB" without saying which/how, but it's still less than ideal to say, "We got charges from ATB and here are our files," as one still doesn't know where they came from.  Who knows what it really is? I'd much rather have, "Here are my files, and here's the algorithm I used to generate them."
If you do implement something along these lines, can you try and do it in a way which is not Foyer-specific? We'll ultimately need something for blocking too, and it would be nice to be able to reuse rather than rewrite.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/mosdef-hub/foyer/issues/122#issuecomment-312915454, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABW4q881mBSNW8126mP5daRsmykc1qyBks5sKmhEgaJpZM4NfX7E.

Alright, to sum up some of these discussions, I'll be taking a stab at building another package outside of foyer that calls a QM method to assign charge. I'll need to figure out a handful of details along the way (blocking being the biggest hurdle) and I'll tag people in issues elsewhere if I need help.
I agree that documenting the underly algorithms, not necessarily just spitting out files, is the best approach for reproducibility and openness.

If you do implement something along these lines, can you try and do it in a way which is not Foyer-specific?

My vision is for it to take and return parmed structures, which fits right into the foyer workflow but should also be generally useful to people who have other workflows.

Excellent. That sounds great. LMK if it would be helpful to have a call with us to discuss strategies for this. Otherwise, please just tag me as you get going as I'll be an interested spectator and potentially interested in using as well.


Allow toasts to work with FtResponse

name: Pull Request
about: Fix for issues 486
title: '[PR] Allow toasts to work with FtResponse'
labels: 'bug', 'hacktoberfest'
assignees: ''

Related Issue
[BUG] FtResponse breaks toasts
Proposed Changes
Add FtResponse to list of supported response types
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist
Go over all the following points, and put an x in all the boxes that apply:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] I am aware that this is an nbdev project, and I have edited, cleaned, and synced the source notebooks instead of editing .py or .md files directly.

Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

Great!


fix falsy values evaluation

What is this PR for?
On the function execAndGetLine is an if statement which can detonate errors due to no all function branches return a result. Furthermore, the errors could be detonated by a falsy value which could be the expected result for the user.
if (evalOutput) {
  return { type: "output", value: prettyFormat(evalOutput) }
}

In example, if the user writes 1 - 1 which should return 0 will end up breaking the component due to receiving undefined during rendering lines on the terminal.
Maybe the if statement was required for other reasons. If that's the case I'm happy to help, otherwise I think this pull request has everything need to make it work.
Thanks for creating this component!!
What have been done in this PR?

Fix the falsy values evaluation in the REPL component.
Add one more line on the component story  for checking a falsy value will be correctly evaluated.

cheers!


please remove the panopticlick EFF tracker protection domains unless they're actual trackers

I don't see the point of simply blocking these domains by hardcoding them in a list.
trackersimulator.org
eviltracker.net
do-not-tracker.org
If their purpose is to test certain fingerprinting techniques, why prevent them from doing that?  You're effectively breaking the test of techniques that thousands of actual tracking companies use by blocking these 3 innocuous domains.
I can't find the right words to explain that.
I liken this to cell phone companies overclocking your phone when running benchmark apps.  It helps your brand but we're actually trying to test something specific.

@jawz101 all three of these come to us via adaway.org.
Please take up this issue with them, they have an issues page.
Closing.

ok.  We'll see how that goes.  Their list hasn't had updates in 2 years https://github.com/AdAway/adaway.github.io/commits/master/hosts.txt


Fix every PR linking to PR 123

Follow up of #21686
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: "addresses #123"), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment "fixes #<ISSUE NUMBER>" instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @damccorm

Can one of the admins verify this patch?

Can one of the admins verify this patch?

LGTM thanks!


unable to connect containers using storage explorer

Preflight Checklist

[x] I have installed the latest version of Storage Explorer.
[x] I have checked existing resources, including the troubleshooting guide and the release notes.
[x] I have searched for similar issues.

Problem
i am trying to connect storage using SAS getting error
Desired Solution
i would like to get an fix ASAP
Alternatives and Workarounds
No response
Additional Context
No response

@40107511 Sounds like you're encountering a problem and not requesting a new feature. Please provide the information requested in our bug template and we will help you diagnose your problem. Be sure to include:

Your OS/platform and architecture.
The version of Storage Explorer you are using.
Detailed steps that you followed to encounter the issue.
The type of storage service you are trying to connect to.
The SAS you are using (do NOT include the sig part of the SAS).
The text or a screenshot of the error you are receiving.


7/31 Publish

@Taojunshen,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-autogen/account.pycliyml
:white_check_mark:Succeeded
View

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


send Download & Impression data to BigQuery

For Dovetail audio: the player follows redirects (and hits podtrac-ish counts), but when it gets to DT it hits the "debug" endpoint, which doesn't track impressions or downloads (and shouldn't, since it's also used by backsaw, etc). The player then manually logs impressions to Adzerk as the listener plays the ads - but not to us/ BigQuery.
To be the most accurate, the Player should fire a “Download” to bigquery when you actually press play, and fire impressions to bigquery the same time it logs to adzerk.

Is this medium priority? Not sure. @kookster?

This will likely require either a new kinesis-logging endpoint within DT itself, or some sort of pixel tracker that can do the same thing.  As we think about a generic pingbacks standard for dovetail, might be a good idea to use that same standard to receive pingbacks within dovetail.

Original description:

For Dovetail audio: the player follows redirects (and hits podtrac-ish counts), but when it gets to DT it hits the "debug" endpoint, which doesn't track impressions or downloads (and shouldn't, since it's also used by backsaw, etc). The player then manually logs impressions to Adzerk as the listener plays the ads - but not to us/ BigQuery.
To be the most accurate, the Player should fire a “Download” to bigquery when you actually press play, and fire impressions to bigquery the same time it logs to adzerk.

PRX version fixed!  Forever!


Update records.json

🌐 Website

Link:
Screenshot:
📋 Checklist

[ ] I have starred the repository.
[ ] I have read and accepted the Terms of Service.
[ ] There is reasonable content on my site.
[ ] I have configured a custom domain for my site.

Hello! It seems that you have successfully applied for a subdomain before. If you need to update the link of the CNAME record, please modify "sportlivelk": "383zyusx94sis.ahost.marscode.site" in records.json.
If you want to apply for a second subdomain, according to our FAQ:
Q: May I apply for more than one subdomain?
A: Yes, you can. However, starting from your second subdomain, you can only apply subdomains for your projects which have no less than 5 stars. If you are using [Github Pages](https://pages.github.com/), we strongly recommend you to bind the subdomain to your your-username.github.io domain, so that you can use path-based routing for whatever you like.

, please attach your project link.
Thank you for your understanding and support.


Random Adaptation

What do you think, I'll keep this draft since it is pre-refactoring, and make a real one after.

Also I couldn't figure out how to make it spin like every 10 seconds let's say


Migrate to use typescript-eslint from tslint

Fix https://github.com/karen-irc/option-t/issues/350

This change is

bors r+


setMinDate greyed out time gets black again after click

I noticed something that might be confusing for people who use the datetimepicker.
When i use setMinDate and use the time-picker, the hours before the defined minDate are greyed out like expected, however as soon as i click some time there, the hours greyed out before, get black again, but they are still not selectable.

ok. i have found a pull request for this already.
https://github.com/T00rk/bootstrap-material-datetimepicker/pull/109
i checked the code (unfortunately he converted spaces to tabs or something like that, so the changes are not much helpful)
but i found that only
this.initHours(); was added to the end of _onSelectHour function and
this.initMinutes(); was added to the end of _onSelectMinute function.
i tested it, and it helped. :) So +1 for mergin it.

To solve this bug, I changed the for loop in onSelectHour :

for (var i = 0; i < th.length; i++)
{
if (!this.toggleTime(i, true))
{
$(th[i]).attr('fill', '#bdbdbd');
}
else
{
$(th[i]).attr('fill', '#000');
}
}

And in onSelectMinute :

for (var i = 0; i < tm.length; i++)
{
                    if (!this.toggleTime(i * 5, false))
                    {
                        $(tm[i]).attr('fill', '#bdbdbd');
                    }
                    else
                    {
                        $(tm[i]).attr('fill', '#000');
                    }
                }


Typeguard of undefined check not working on array property

Search Terms:
typeguard collection array undefined
Code
let c: { tiles: { x?:number }[]} = { tiles:[]};
for (let i = 0; i < c.tiles.length; i++) {
    if (c.tiles[i].x)
        Math.max(1, c.tiles[i].x); //compiler error 'Type undefined is not assignable to type number.'
}

Turn on strictNullChecks.
Expected behavior:
if (c.tiles[i].x) should act as a typeguard, and when it is referred to on the next line, it should be treated as type number.
Actual behavior:
It is treated as number|undefined.
Playground Link:
link
Turn on strictNullChecks.

Workaround:
``typescript
let c: { tiles: { x?:number }[]} = { tiles:[]};
for (let i = 0; i < c.tiles.length; i++) {
let x = c.tiles[i].x
if (x)
Math.max(1, x);
}

Duplicate of #10530


Memory scan is failing over all methods and OS's

hey dude, I've tried all options across both windows and linux, I haven't been able to get past the Scanning for corrupted object part in the memory corruption stage. I suppose it could be my PS4  since that's the only constant, but if you have any ideas I'd appreciate it!
using the latest release
tried on

python 3.10 on linux mint
python 3.12 on windows

[+] STAGE 1: Memory corruption
[+] Pinning to CPU 0...done
[*] Sending malicious LCP configure request...
[*] Waiting for LCP configure reject...
[*] Sending LCP configure request...
[*] Waiting for LCP configure ACK...
[*] Waiting for LCP configure request...
[*] Sending LCP configure ACK...
[*] Sending IPCP configure request...
[*] Waiting for IPCP configure ACK...
[*] Waiting for IPCP configure request...
[*] Sending IPCP configure NAK...
[*] Waiting for IPCP configure request...
[*] Sending IPCP configure ACK...
[-] Scanning for corrupted object...failed. Please retry.

nvm, I got it working with Windows after doing a full restart on the PS4 and spamming it like 10 times in a row. I used the PPPwn Goldhen and PPPwn_GO options.


added made the text of the logo white #2465

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #2465
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test case A
[ ] Test case B

Checklist:

[x] The title of the PR states what changed and the related issues number (used for the release note).
[ ] Does this PR require documentation updates?
[ ] I've updated documentation as required by this PR.
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have tested it for all user roles
[ ] I have added all the required unit/api test cases

Changes are covered under https://github.com/devtron-labs/devtron/pull/2475 so closing this PR.


Optional e.preventDefault() in handleContainerClick function

Hello!
Just included your plugin in a project of mine recenty and I'm finding it really nice!  Setup is dead simple and the different easing animations are really good :)
However, I'm looking for a way to override the e.preventDefault() call in .handleContainerClick().
Basically, I've put data-scroll="{id}" attributes to a bunch of <input>s in a large form such that clicking each input scolls to the next question.  The scrolling itself is working really well, but now clicking on an input doesn't actually select it.  When I removed, e.preventDefault(), everything was fine.
Is there an easy way to remove this behaviour that I haven't seen (or, failing that, would it be possible to add this in)?
Thanks so much!
Paul

Hi @pcraig3
Thank you for using this library!
I will try to add the following as an option. What do you think?
new SweetScroll({
  preventDefault: true, // Cancels the trigger click event.
  stopPropagation: true // Prevents further propagation of the trigger click event in the bubbling phase.
});

Yes, that would be perfect!
:+1: :+1:

Thank you! Add option in the v0.6.0.

v0.6.0 released :+1:
Will it work as expected?

tsuyoshiwada/sweet-scroll: ECMAScript2015 Friendly, dependency-free smooth scroll library.
sweet-scroll

Yes, this is excellent!  Thanks so much :smiley:


Merge different prefix options

I really enjoy the simplicity of this extension and it works perfectly out of the box. The only thing I find frustrating is that I cannot recreate the metric naming scheme I had in mind with the options available (e.g. a top level prefix for all stastd metrics).
Currently the the following options are available for prefixing the metric names:

add_client_prefix
path_prefix
add_path_prefix

In my opinion, these could be simplified by just using a single option path_prefix, like this pull request suggests. In the current state, we would lose the ability to include the client name, tough.
I had the idea to add support for token substitution, like it is possible in check configurations, but I don't know if that is possible. If it was, we could mimic the current behavior using a default for path_prefix like this: :::name:::.statsd. Suggestions are welcome.
Thank you for the awesome work and your feedback!

I identified some other issues. I'll reopen this pull request with a different branch as source.


fix: yarn notifier

Problem
yarn notifier was unable to run for me locally.
issue 1 - tsconfig baseUrl/paths
I was getting an error that it cannot find module stores/useWalletStore

I fixed this by adding `tsconfig-paths` into the tsconfig
 "ts-node": {
+   "require": ["tsconfig-paths/register"],
    "compilerOptions": {
      "module": "commonjs"
    }
 }

I also removed tsconfig.commonjs.json and merged it into the ts-node field in tsconfig.json
issue 2 - unexpected token '<'
After fixing the paths I got new errors because there is JSX in the one of the imports used by the notifier

I added react-jsx so that the JSX would be compiled rather than preserved. I didn't love this solution because I don't think there should be JSX loaded in a headless script that's called from node.
"compilerOptions": {
+  "jsx": "react-jsx",
  "module": "commonjs"
}

issue 3 - @solana/wallet-adapter-phantom is not cjs
The next error was because @solana/wallet-adapter-phantom is only exported as esmodules

I went down various rabbitholes trying to fix this (type: module in package.json, babel presets, swc, esbuild)
Solution 🎉
By far the simplest approach was to move ConnectionContext and getConnectionContext into their own file, this way the notifier script doesn't import any JSX or the esm @solana/wallet-adapter-phantom code.
⚠ I don't know if utils/connection.ts is the best place for this file, or if it would be better to leave it in the store file and move the JSX and wallet-adapter code out of the store file instead?
But this works for now and fixes the immediate problem.
Finally
I also upgraded all eslint* dependencies because I got a warning from yarn test-all but I can revert that commit if it's problematic.

⚠ I don't know if utils/connection.ts is the best place for this file, or if it would be better to leave it in the store file and move the JSX and wallet-adapter code out of the store file instead?

It's better here, I think store is inherently related to UI and connection is more basic concept
Just let's unify our utility functions under tools and deprecate utils
Thank you for all that cleanup work, the project needs it !!!


Almost!  Crashing on Instagram with latest build.

DL latest build
Set up Podfile
Add my ID, and secret key. That's it. Pretty simple.
Run Demo

OAuth verification on mobile is not easy, that we know.
Kaboom!   I'm confused a bit by this one. There is nothing optional here. Error does not show up at compile time. Only at run time. So close! Thanks.

Ok, started from scratch, worked.

Instagram["consumerKey"] instead of Instagram[4612379641789] would've worked.

Got it thanks. Yes, missed the constants.swift file. Guess what threw me was the error message. thanks :-)


Add "offset" parameter to GroupBy query.

It works by doing the query as normal and then throwing away the first
"offset" number of rows on the broker.

Note: I don't think this patch has the issue from https://github.com/apache/druid/pull/10233#issuecomment-668173929, because unlike Scan queries, GroupBy query results are stable from run to run. (There is always an ordering, even if it's implicit.)

Note: I don't think this patch has the issue from #10233 (comment), because unlike Scan queries, GroupBy query results are stable from run to run. (There is always an ordering, even if it's implicit.)

Nevermind! I realized that this isn't true at the outer layer of the query. It's true when merging is happening, but not when we're going to apply the offset, because the LimitSpec might have reordered things in an unstable way if not all dimensions were provided as orderBys. I'll modify DefaultLimitSpec to use a stable sort and add some tests.

Note: I don't think this patch has the issue from #10233 (comment), because unlike Scan queries, GroupBy query results are stable from run to run. (There is always an ordering, even if it's implicit.)

Nevermind! I realized that this isn't true at the outer layer of the query. It's true when merging is happening, but not when we're going to apply the offset, because the LimitSpec might have reordered things in an unstable way if not all dimensions were provided as orderBys. I'll modify DefaultLimitSpec to use a stable sort and add some tests.

OK, I just pushed a commit that stabilizes the sort, at the cost of an extra counter per element. I think this is okay, because we don't expect the limited resultset on a query like this to be very close to the amount of memory we have available. (Of course, it's possible for a user to type in a very high number, but in this case we'd do better to move the sorting off-heap.)