Relation Annotation: Add Single/Multi Relation Mode to Viewer

Currently, the viewer lists all relations within a single document. During annotation, this introduces the need for extra clicking to navigate through individual relations. We should have an annotation mode that only shows one relation per document, generating multiple views of the same doc.

I'm going to close this for now, as I think the current viewer mode should be better here now, but feel free to reopen!


change specName for hydradx to hydration

since hydradx is renamed now to hydration.
const assetTransferApiHydration = new AssetTransferApi(hydration.api, 'hydradx', 4);
example

ahh looks like its coming from the hydration parachain runtime only
	const { specName } = await api.rpc.state.getRuntimeVersion();


refactor: Tag.types file translation

Refactor Request
-- fill in the line below:
** discord username: dram3vlh**
Is your refactor request pertaining to a problem? Please elaborate.
The tag component that displays the load capacity has not been translated from English to Turkish.

The code has been updated, but I think the release has not been issued yet, so I am closing the issue. @emr3rden


Use toned-down device SVGs, with Logitech G403 example

During a discussion I had with Jakub Steiner he suggested we use toned-down device SVGs instead. Both @whot and I like this approach, so let's discuss this with the rest! This is a first device he did for us, which is the G403 that I own so I can use it while working on Piper.
The mockups aren't entirely up-to-date (will fix that tonight or tomorrow, most likely) but this is where we're going (that's still proof of concept code that I'll extend in the next few days). As you can see, we will need to retrieve some coordinates from the SVG to place the labels. This is why I also updated the guidelines. I also made the canvas size smaller (simply took what Jakub gave me, it looks good) which noticeably increases performance when opening and resizing Piper.

CC @raghukamath @whot @bentiss. Please CC more people that should be involved.

Also, Jakub offered to do three more devices for us. Are there any devices that are particularly important to get done?

@Hjdskes the image looks very nice, I like it a lot!

I have updated #159 to include the image.

Just a small comment on the SVG itself (which I like very much).
I am a little bit concerned the " G" is too close to the real Logitech logo. IIRC we put as a requirement to not have any copyrighted material, and even if the shape of the mouse has a lot of chances of being copyrighted, having the actual logo is a little bit more worrying.
Please change this into something else (circle maybe), and we can merge the PR.

Good point, I'll pass that on to Jakub.

Jakub also mentioned (after reading the requirements for the SVGs) that using photos to start isn't something to encourage. He said that it's best to let designers to this work, and he'll try to help out as much as he can.
We also discussed prelighting/highlighting the button in the SVG when the respective button is hovered/pressed in Piper (no capture mode yet to do this directly from the device). I'll see if I can make this work, from the SVG side it just requires that the buttons have unique identifiers next to the leaders so we can inject CSS into the SVG programmatically.

fwiw, I've asked @jimmac in email for the G502, G700 and the roccat kone xtd, all three have have special features that require some design input, once we have those we can probably get the others based on those as template.

This is nice, I like it.
In the mockup you linked, the text appears white, I believe it is a bit low on contrast and can be more readable is it is a bit darker in color.

@raghukamath fwiw, that's not the final text, we're trying to do away with the button labels altogether. So that white text won't stay there.

Look what we've got: https://github.com/gnome-design-team/gnome-mockups/tree/master/libratbag/assets
I'll update the SVG instructions to account for left and right leaders, and I'll start importing those SVGs as well.

Look what we've got: https://github.com/gnome-design-team/gnome-mockups/tree/master/libratbag/assets

Nice!
But there are few errors on those SVGs (not easy to find out when you don't own the mice):

G403: nothing to report
G502:

there is a missing "sniper button" below the 2 left thumb buttons (see https://github.com/libratbag/libratbag/blob/master/data/logitech-g502.svg button 5)
the button between the wheel and the one in the middle (button 8) doesn't report anything, it's a mechanical switch
the wheel has both vertical and horizontal scrolling capabilities, horizontal "buttons" can be configured (but not the vertical ones)

G700:

there are 2 missing "thumb buttons" below the 2 left thumb buttons (see https://github.com/libratbag/libratbag/blob/master/data/logitech-g700.svg button 3 4 5 and 6)
the button between the wheel and the one in the middle (button 10) doesn't report anything, it's a mechanical switch
the wheel has both vertical and horizontal scrolling capabilities, horizontal "buttons" can be configured (but not the vertical ones)
there is no LED on the mouse

Both the G502 and G700 have their button leaders on each side, so I guess this requirement should go away, or we should add a "preferably" in front of the paragraph.

Both the G502 and G700 have their button leaders on each side, so I guess this requirement should go away, or we should add a "preferably" in front of the paragraph.

Yes, this is precisely what I meant when I said I'll update the SVG instructions :)

Devices left to tone down:

[ ] etekcity
[ ] logitech-g300
[ ] logitech-g303
[ ] logitech-g500s
[ ] logitech-g502 (awaiting update to fix issues raised in https://github.com/libratbag/libratbag/pull/182#issuecomment-308467084)
[ ] logitech-g700 (awaiting update to fix issues raised in https://github.com/libratbag/libratbag/pull/182#issuecomment-308467084)
[ ] logitech-g9
[ ] logitech-g900
[ ] logitech-mx_master
[ ] roccat-kone-xtd

Hopefully I've addressed the issues raised about the model g700 and g502. I've also added the scrollwheel vertical directions as assignable events as per Jente's request.

Very cool, thanks!

I've also added the scrollwheel vertical directions as assignable events as per Jente's request.

These seem to be missing from the G403 still (not sure if those are still planned, apologies if they are)

Sorry Sparkleshare was stuck pushing the local changes. Even the 403 should have the scrollwheel fixed now.

@bentiss Are you aware of any devices that do not have a static button assigned to switching resolutions? With "static" I mean that it's not exposed to the outside and hence libratbag cannot remap it, as on e.g. the G403 and G500.
This is relevant for fa8194ae6dacb5d0011e2b6527cbf9908be059f1. For Piper's resolutions page, I need to highlight which button(s) is(are) assigned to switch resolutions. For the G403 and G500 this is, as mentioned, not exposed through libratbag and hence we have to set this statically in the SVG. Of course, this will fail to work for devices where this is remappable, if there are any?

(Replying here to keep everything in this thread)

Not sure about the G500, but the resolution switch button (under the wheel) on the G403 is definitively addressable and can be remapped.

Hm... not sure where I got the idea that this is static then.. @whot thought his G500 was static as well. In that case, we'll probably have to deal with both static and not static buttons. This will in both cases require the fourth layer but without the label in the SVG. I'll have to figure out how to draw a label for static buttons, but that should be do-able. That solves this issue, then.

What could be interesting is to mention that any other drawings need to be drawn in one or more separate layers, that may (or not) be drawn by the UI.

Sure, I can add this. It shouldn't be in the way for Piper I think.

@bentiss Are you aware of any devices that do not have a static button assigned to switching resolutions? With "static" I mean that it's not exposed to the outside and hence libratbag cannot remap it, as on e.g. the G403 and G500.

After reading this, I believe you might be mixing up the mice models and buttons:

the G700, G900 and the G502 in this PR have all a mechanical switch below the wheel that enable/disable the ratchet mode on the wheel. When ratchet is disabled, the wheel is in the "free wheel" mode, where it just doesn't have any click (and a lot of inertia).
all buttons on the Logitech devices I have are addressable and can be remapped in libratbag.

So IMO, the ratchet mode buttons that are just mechanical should just be grayed out in the SVG and nothing should mention it.
Also, there is one thing we need to do on the SVG (no need to ask jimmac for that), is that all the Logitech devices can't remap the vertical wheel events. So there are a couple of leaders/buttons on the drawings that need to be removed (and we need to rearrange the other leaders).

Every electrical button can be remapped on the G500/G500s. The mechanical switch for ratchet mode is the one under the wheel. Also, as bentiss said, vertical wheel does not count as buttons, but horizontal wheel does.

I just updated all three toned down SVGs we currently have according to the new guidelines. The only device that isn't entirely done is the G700; my Inkscape skills aren't good enough to separate a button0 and a button1 from the rest of the device such that these can be given their identifiers.

I made an attempt at a G500/G500s SVG copying the G700 style. I have a few remarks regarding the instructions:

There is no size for the image but margins and spacing are given in pixels. Different images will be scaled differently resulting in different margins, spacing, border size, ...
The two main buttons on the G500 and G700 do not have separate pieces, so there is no corresponding object. Mouse wheel tilt is not drawn either. Is the "buttonX" id mandatory for every button? What should be done for this kind of buttons.

Regarding the G500, I have drawn the LEDs but not the leaders. These LEDs cannot be configured with effects, but they can be switched on and off depending on the resolution (and profile). Should they be ignored, or should there be 4 LED leaders?

@cvuchener I think for the G500s we should just ignore the LEDs, they're such a minor thing that the effort of exposing the configuration is probably not worth it.
as for

The two main buttons on the G500 and G700 do not have separate pieces, so there is no corresponding object.

Do you refer to it being the same piece of plastic? For the highlight, just make something up then I'd say.

I made an attempt at a G500/G500s SVG copying the G700 style. I have a few remarks regarding the instructions:

Looks good!

There is no size for the image but margins and spacing are given in pixels. Different images will be scaled differently resulting in different margins, spacing, border size, ...

Right, good point. Up until now we haven't cared about size too much, since it's unlikely that a user will have two devices to notice the window resizing when (s)he switches device in Piper. Let's add a minimum of 400*400 and a maximum of 500*500.

The two main buttons on the G500 and G700 do not have separate pieces, so there is no corresponding object. Mouse wheel tilt is not drawn either. Is the "buttonX" id mandatory for every button? What should be done for this kind of buttons.

Mouse wheel tilt should be drawn in the latest G502 and G700; it's the little arrows pointing left and right. Copy those and place the marker squares somewhere close to it, and give the arrows the button ids.
The button id is mandatory insofar that without it, the button cannot be highlighted (like this). I agree with @whot in that you can just create an object that overlaps with part of the button (e.g. the top) so it's clear what element is being configured. This also has to be done for the G700 SVG still.

This should be merged after #212. With the new theme support in libratbag, I suppose we can go ahead and merge the three devices that currently have an SVG. If so, I'll move the list from https://github.com/libratbag/libratbag/pull/182#issuecomment-308504676 to an issue instead.
Do note that the G700 still has no buttons in the SVG for button0 and button1 (my Inkscape isn't good enough to fix that)

@Hjdskes, can you quickly rebase the PR on top of master? It seems to conflict.
Once rebased, feel free to merge the PR.


Not working for https://www.youtube.com/channel//videos URL

I just noticed that when you are in videos section for specific channel, if the channel has a Channel ID instead of User ID, i.e. the URL is youtube.com/channel/..../videos instead of youtube.com/user/..../videos, the script does't work.
A simple fix is to replace line 163 from this:
} else if (window.location.href.match(/./user/.+/videos/)) {
to this:
} else if (window.location.href.match(/./(user|channel)/.+/videos/)) {

Good catch. Fixed in v2.8


security issue with dependencies

vulnerability found in cli
Description: Insecure use of /tmp folder
Introduced through<EMAIL_ADDRESS>From<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>

I see the issue fixed in version<EMAIL_ADDRESS>Closing this issue now.


RCTContacts.xcodeproj cannot be added in XCode!

Your manual installation section is wrong.
RCTContacts.xcodeproj can't be added that way, it is not selectable.

Did you already run react-native link react-native-contacts ?
If so, the library might be added already, and that's why you cannot select it.

@adbarmand should the react-native link step be removed altogether? it seems like it doesn't work

updated the instructions to more closely match the RN docs, @wzup lmk if it works

updated docs and verified that you can link the lib, removed the image.


Remove hiera_hash in favour of lookup()

Any hiera functions prevent you from moving to the new puppet lookup() function.
When moving to the hierarchy in modules,  you have to turn off 'classic hiera'.
Classic hiera uses:  hiera(),  hiera_array(),  hiera_hash().
The new version uses lookup().
This would change
hiera_hash('elasticsearch::plugins', $::elasticsearch::plugins)
to:
lookup( { 'name'  => 'elasticsearch::plugins',
               'merge' => 'hash',
        })

Happy to submit a PR on this - unless anyone knows that this is in the works and I didn't see it when searching issues.

Hey @brettswift, I don't think this is underway in any issues or PRs, so feel free to take a crack at it if you'd like. I haven't played around with lookup() vs. hiera*() before, but as long as it's supported across the versions the module supports and tests pass, I'm  👍. Thanks for the help!

It seems like this was introduced into puppet 4.3.
According to the metadata.json file here,  the module still supports 3.2 on PE. (which I think was puppet 3.6 or something).
Is there a version / timeline to leave puppet 3 behind?

No timeline right now. In the meantime one option could be handling lookup()/hiera() calls based upon the puppet version fact - it's definitely uglier than just deprecating 3.x but it'd be immediately doable.

Good idea,   I thought the compiler would see the function and fail if it wasn't available, even if it wasn't going to execute it in that run.. however a quick test proves me wrong!
I am currently doing inventory of all the things we'd have to refactor to get to the next version of hiera.. so you may not see this PR immediately.   I'll see what I can do.   Thanks!

There is a nicer workaround here:
https://tickets.puppetlabs.com/browse/HI-518
If that doesn't work I'll send in a PR to use the new lookup function if it's available.
I'll leave the state of this ticket up to you if you want to close it or keep it for tracking etc..

If the workaround ends up working for you and you're happy with the solution, feel free to close this issue. If you need to PR something, go ahead and we can close this out once that's done. 👍

Will do. Thanks
On Tue, Jun 21, 2016 at 13:56 Tyler Langlois<EMAIL_ADDRESS>wrote:

If the workaround ends up working for you and you're happy with the
solution, feel free to close this issue. If you need to PR something, go
ahead and we can close this out once that's done. 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elastic/puppet-elasticsearch/issues/642#issuecomment-227553172,
or mute the thread
https://github.com/notifications/unsubscribe/AAsMFcHrJYPtckC-23cUhNj7FuotQHaSks5qOEH9gaJpZM4IyCiI
.

FYI, I'll be removing all calls to hiera_* functions in the module when the 6.x branch of the module gets release and we deprecate Puppet 3.x. Moving forward, folks should be able to use lookup_options instead and get the same effect without needing any calls to lookup().


⚠ ClamAV has degraded performance

In 34558d2, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 191 ms

Resolved: ClamAV performance has improved in fcea955.


Implemented countIf function for Lists

Motivation
Resolves #723
Expanded the stdlib  by adding a function on lists which counts how often a given predicate evaluates true.  After some time thinking about it, I went with the name countIf.
Changes
Added the code for the countIf[A](list: List[A]){predicate: (A => Bool) }: Int  Function in libraries/common/list.effekt with fitting Documentation.
Implemented a test and check file file in the examples/stdlib/list directory
Testing
I locally ran the sbt:effekt>test successfully and tested some examples.
It can be tested the same way
Notes
This is my first contribution to the effekt-lang, so I am happy to hear feedback and change things if there's need for it:)

regards Jakub

Regarding the name of the function, I'll ask at the Effekt Working Group meeting what the consensus is. :)

Hey Jiri, thank you for your extensive Feedback and help, retrospective I could have been a bit more attentive to the stylistic choices, but I guess thats how lessons are learned:)
If I find the time next to Lectures, I would like to tackle some more good first issue labelled Issues if thats allright:)
I'm looking forward to the naming consensus!

Hey :)
I don't want to steal much of your time anymore, but I'm kind of lost now, I walked through the code with a checklist in mind and cannot really see what I missed here!

Thanks a lot, I haven't had such a perspective on styling and formatting code before! :) Really learned something from this issue

This should really do it now! Thanks a lot again, really opened my eyes to some cleaner (looking) code, definitely going to refactor some of my own projects by time!
Thanks for the help:)

This should really do it now! Thanks a lot again, really opened my eyes to some cleaner (looking) code, definitely going to refactor some of my own projects by time!

You're welcome.
I'm not sure I'd call it a refactoring (though technically it is): the code is still identical, just the formatting (its presentation) changed -- to me (and the compiler) it's the exact same code down to the identifier names, just in a different coat of paint.

The Effekt Working Group has decided that the function should be called count based on the proximity to Scala and Unison.

whoops the rename didn't work, guess the branch stays with the old name:)

Hey @jiribenes , I renamed the files and all appearances of countIf to count :)
I think wit this, we are finished here, thanks again for your extensive help, really made me think a lot more about code-style!
Looking forward to some other Issues/PRs :)

✨ Merged! ✨
Thanks yet again for your contribution, @JakubSchwenkbeck!


Add some default vscode settings

Description
Adds default vscode configuration for the repo, hopefully making it easier for incoming developers to just get started with working on osmosis with vscode.

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

Codecov Report

Merging #1197 (71606ae) into main (eed3294) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1197      +/-   ##
==========================================
- Coverage   21.03%   21.03%   -0.01%
==========================================
  Files         196      196
  Lines       25349    25351       +2
==========================================
  Hits         5332     5332
- Misses      19054    19059       +5
+ Partials      963      960       -3

Impacted Files
Coverage Δ

x/gamm/keeper/pool_service.go
56.61% <0.00%> (-0.61%)
:arrow_down:

Continue to review full report at Codecov.

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


⚠ Bofrost.lu has degraded performance

In 8fe09b3, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1896 ms

Resolved: Bofrost.lu performance has improved in be33cc3 after 13 minutes.


Correct output for missing periods + MissingWMO with coarse frequencies.

Pull Request Checklist:

[x] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #570 and fixes #572.

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Documentation has been added / updated (for bug fixes / features)
[x] HISTORY.rst has been updated (with summary of main changes)
[ ] bumpversion (minor / major / patch) has been called on this branch
[ ] Tags have been pushed (git push --tags)

What kind of change does this PR introduce?
1 - Add a resampling code to MissingWMO.execute to allow frequencies larger than 'MS'. Also small refactoring of MissingFromContext.execute to use the subclass's  execute method, and not an init-call syntax.
2 - Fix MissingPct and AtLeastNValid to correctly mark as missing cases where a whole period is absent from the input.

Does this PR introduce a breaking change?
No.

Pull Request Test Coverage Report for Build 2364

7 of 8 (87.5%)  changed or added relevant lines in 1 file are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 92.354%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

xclim/core/missing.py
7
8
87.5%

Files with Coverage Reduction
New Missed Lines
%

xclim/subset.py
3
62.5%

Totals

Change from base Build 2363:
-0.1%

Covered Lines:
3213

Relevant Lines:
3479

💛  - Coveralls


Python 3.6 and pipenv 2018.10.13 fails to install isort 4.3.9

python-3.6.3
pipenv-2018.10.13
pip-18.1
setuptools-40.4.3

$ pipenv sync
Installing dependencies from Pipfile.lock (64ec66)…
An error occurred while installing isort==4.3.9 --hash=sha256:f19b23b22fb5a919a081bc31aabcc0991614c244d9215267e11abf2ca7b684ce! Will try again.
  🐍   ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 49/49 — 00:00:12
Installing initially failed dependencies…
Collecting isort==4.3.9 ▉▉▉▉▉▉▉▉▉▉▉▉▉ 0/1 — 00:00:00
  Using cached https://files.pythonhosted.org/packages/72/41/5188c1dafe27263005a017d4a2dd0def7c97fddc443564a260da414ee94d/isort-4.3.9-py2.py3-none-any.whl

THESE PACKAGES DO NOT MATCH THE HASHES FROM Pipfile.lock!. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
    isort==4.3.9 from https://files.pythonhosted.org/packages/72/41/5188c1dafe27263005a017d4a2dd0def7c97fddc443564a260da414ee94d/isort-4.3.9-py2.py3-none-any.whl#sha256=ee5fddfd792e6e1d664ee28f3fbe00dfc26d8d3c6f059ee78f4da4c19718007c (from -r /tmp/pipenv-_dzf4mi8-requirements/pipenv-xvpvpxqh-requirement.txt (line 1)):
        Expected sha256 f19b23b22fb5a919a081bc31aabcc0991614c244d9215267e11abf2ca7b684ce
             Got        ee5fddfd792e6e1d664ee28f3fbe00dfc26d8d3c6f059ee78f4da4c19718007c

Relock your file again. Then it will work again
They added the wheel file some days later https://github.com/timothycrosley/isort/issues/855

Closing as duplicate.


[gdal] Update to 3.1.3

This PR is partially inherited from #9100, will make the following changes:

Add option INSTALL_COMMAND to vcpkg_build_nmake and vcpkg_install_nmake
Add option MAKEFILE to vcpkg_build_make
Update gdal to 3.1.3
Switch execute_process to vcpkg_install_nmake on Windows.
Switch execute_process to vcpkg_configure_make/vcpkg_install_make on *inx.

Note: Because part of the dependencies in *inx has a missing relationship on the master, this PR does not deal with this and will be dealt with in other PRs.
Fixes #11905 #8664.

Needs to merge #10408 first(requires libgeotiff 1.6.0).

cc @Neumann-A for review this PR.

/azp run

Hello, trying to update to 3.1.3 I've merged this PR in my fork (https://github.com/Matioupi/vcpkg/tree/gdal_313) but gdal build now fails ( x64-windows ). It looks like it's trying to build the "all" target wich does not exists in the makefile.vc. What did I missed ?

I added this commit :
https://github.com/Matioupi/vcpkg/commit/03bdeb306de3c39137c57e41bc259ba770863a79
to my fork that changes the build version suffix. 204 was for gdal 2.4.1 and without adding VERSION to nmake options the 3.1.3 would default to 301

Ping @BillyONeal for review this PR.

@strega-nil @BillyONeal Anything else?

/azp run

@strega-nil Can we merge this PR now?


fix: paginate DescribeNetworkInterfaces with deep filters

Issue #, if available:
Fixes #188
Description of changes:
Paginate DescribeNetworkInterfaces API call by specifying a deep filter like vpc-id and subnet-id as unpaginated API call causes the operation to fail when there is a large number of network interfaces.
https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-network-interfaces.html
Unpaginated calls were used in the periodic leaked ENI cleanup routine and during trunk initialization to fetch all branch ENIs on the node. These are now paginated to use vpc-id and subnet-id respectively, and also added jitter to avoid EC2 API throttling and increased call volume to address earlier issue with pagination.
Testing:
Security group for pods test succeeded:
Ran 19 of 23 Specs in 975.331 seconds
SUCCESS! -- 19 Passed | 0 Failed | 0 Pending | 4 Skipped
PASS

Ginkgo ran 1 suite in 16m18.325964387s
Test Suite Passed

Manual tests:

Node scale up/down
Pods using security groups scale up/down
Created 500+ ENIs in same VPC to confirm call volume has not increased drastically

ec2_describe_network_interfaces_pages_api_call_count 4
ec2_describe_network_interfaces_pages_api_err_count 0

Soak tests in progress, will update results

Release notes:
Paginate DescribeNetworkInterfaces API call

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Some overall comments
    Created 500+ ENIs in same VPC to confirm call volume has not increased drastically

ec2_describe_network_interfaces_pages_api_call_count 4
ec2_describe_network_interfaces_pages_api_err_count 0

1. Do we have _before_ and _after_ call count.

2. We could measure is the pod create latency of the SGPP operation _before_ and _after_ the change in cluster with 1000 ENI and ensure that they there is no change.

3. Does the paginated version return any empty pages at all, even with a filter? Can we assert against it?

4. What are the drawbacks on including a required vpc-id as a parameter in the new version of VPC RC?

5. So the trunk Init routine, `WaitForNetworkInterfaceStatusChange` will continue to use DescribeNetworkInterfaces (unpaginated), but only the ENI cleanup will use the paginated. Is that correct? Do we see any problems with trunk init using the unpaginated, with large number of ENI cases?

Yes, we do a benchmark test for every release, the first graph is from v1.4.3 vs second graph from the test. This is running the integration test cases in a loop for 5 times.

SGPP pod creation latency is comparable to previous releases when scaled up to 1000 pods, approx 4 mins.

The paginated version could return empty pages, this is not deterministic. But using deep filter seems to have alleviated the problem of increased call volume. Graph for soak test with 100 nodes and scaling pods using security pods from 0 to 1000 every 15 mins, running overnight

There should be no drawbacks, we will update the controller manifest accordingly with the release to populate the VPC-ID. This is required for the cleanup routine to pass the vpc-id in DescribeNetworkInterfaces

All other calls to DescribeNetworkInterfaces pass in the network interface ID, like in WaitForNetworkInterfaceStatusChange, and is not an issue with respect to throttling.

All other calls to DescribeNetworkInterfaces pass in the network interface ID, like in WaitForNetworkInterfaceStatusChange, and is not an issue with respect to throttling.

Got it. Thank you!.


Spam Video ID Submission

Duplicate Links

[X] Yes, I checked that the ID is not currently in the list
[X] I read the wiki explaining each different categories and examples before submitting

(Required) Spam Comment Direct Link
https://www.youtube.com/watch?v=JRuvxFrKsfQ
(Optional) Screenshot of comments using the link

(Required) List of the spam video IDs / Links
T23PD8Ejhgo
T_cjacm3KUc
AnFFiv56q1A
dQw4w9WgXcQ

Added


[#140925095] bootstrap blank page

all /components deleted
transaction containers deleted
removed redux wire-up in App
renamed title in index page
removed css
left existing base redux code (actions, reducers, store, default data definitions)

Let's merge this and we'll see if there's anything else to clean up


build(main): release 1.1.3

:robot: I have created a release beep boop
1.1.3 (2024-10-16)
Build System

deps-dev: bump @babel/core from 7.25.7 to 7.25.8 (f4ed1a2)
deps-dev: bump @babel/eslint-parser from 7.25.7 to 7.25.8 (8080140)
deps-dev: bump globals from 15.10.0 to 15.11.0 (3d0797c)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.1.3
:sunflower:


Add Transpile section to top header

Unblocks https://github.com/Qiskit/documentation/issues/18.

Going to close this because it's easy from an infrastructure perspective and is blocked on the section being ready. There's not anything for us to do in the meantime. And all the work happens in closed source anyways.


Road to 1.0.0

Main goals:

[x] Rewrite into TypeScript
[ ] Make the code more server agnostic

[ ] Replace eventEmitter with idk, something non Nodejs exclusive
[ ] Make node:crypto module call optional, and fail on constructor if secure is true and module doesn't exists

[ ] Find out why Prettier is crying a lot lately 🙄
[x] Find a way to keep previous versions of the documentation active, so they don't become unusable
[ ] (optional) Find out how to restore compatibility with GAS (Going server agnostic should help a lot)
[ ] Release to NPM

can you please also fix the issue with fetch, its crashing alot of time maybe use axios instead of fetch to make api calls

The new version will allow users to pick their own request implementation or ponyfill, as long as it follows the same arguments as the standard fetch (which unfortunately axios doesn't follow, but node-fetch does). I think the code will be ready for friday, will do my best.
If you can't wait until the stable release, consider using the 1.0.0-beta.2 release on npm. It works afaik, and you can use the fetch method you want.

yeah the problem i am having its crash randomly, sometime it works but sometime it does not work. also it should throw exception instead of crashing the whole server.

Sorry, I don't get it. Why is the server crashing? The code I wrote doesn't intentionally crash, it throws errors. Does using try/catch in your code prevents the crash?
If you want, lets move to a new issue and leave this one reserved for the roadmap.


No notifications on macOS after build

I am getting notifications in my Electron app when it is in dev mode, but after it is built there are no notifications present.
I have my build setup with:
  node: {
    __filename: true,
    __dirname: true
  },

to account for webpacker and I also have my development and distribution profiles setup in Xcode which are detected during an Electron build. So I can (mostly) eliminate most of the common Electron and electron-builder issues that could cause node-notifier to be a problem.
Any thoughts here? I have no errors in the Console logging app.
What could be causing this?

Any thoughts?

the same here

the same problem on windows

Same problem here on macOS. When in dev mode it works fine, but when prod it doesnt' work.
It is working in dev mode even though I have:
  node: {
    __dirname: false,
    __filename: false
  },

same here

My package.json
{
  …
  "main": "main.js",
  "scripts": {
    "postinstall": "electron-builder install-app-deps",
    "start": "electron main.js",
    "pack": "build --dir",
    "dist": "build"
  },
  "build": {
    "appId": "my.app.id",
    "dmg": {
      "contents": [
        {
          "x": 110,
          "y": 270
        },
        {
          "x": 370,
          "y": 270,
          "type": "link",
          "path": "/Applications"
        }
      ]
    },
    "mac": {
      "category": "productivity",
      "extendInfo": {
        "CFBundleURLName": "myapp",
        "CFBundleURLSchemes": [
          "myapp"
        ]
      }
    },
  },
  "dependencies": {
    "electron-is-dev": "^1.1.0",
    "electron-updater": "^4.0.6",
    "electron-window-state": "^5.0.3",
    "node-notifier": "^5.4.0",
    "url-parse": "^1.4.6"
  },
  "devDependencies": {
    "asar": "^1.0.0",
    "electron": "^4.1.4",
    "electron-builder": "^20.39.0",
    "electron-packager": "^13.1.1",
    "electron-reloader": "^0.2.0"
  }
}

@mikaelbr
I tried with this instruction : https://github.com/mikaelbr/node-notifier#within-electron-packaging.
That generates very heavy .dmg and .zip files, and node-notifier still don't work.

After working one full day on node-notifier problems with Electron, i chose to use node-mac-notifier which works great under production.
node-notifier library seems powerful and has many stars, but many people seems to face build problems, even for windows.
As an example Slack use node-mac-notifier and electron-windows-notifications which are stable versions, even for very old versions of Electron. You don't have as many options but that's works.

You may need this: node-notifier-in-electron-vue

@ReAlign that's interesting, thanks for sharing. Even if wearen't using Vue though?

@Noitidart no, it‘s is just a simple handling of the situation ,
I am just simple processing, ensure that can be used.

I fixed it with "asar": false in my build config

@Noitidart  add asarUnpack option to electron-builder
"build": {
    "asarUnpack": [
      "./node_modules/node-notifier/vendor/**"
    ],
    ...
}

@leekangtaqi Thanks! You made my day!!


how to use the backup api to backup the memory db?

I have written the code but it said

no method named backup found for type rusqlite::Connection in the current scope

my code is
extern crate rusqlite;

use rusqlite::Connection;

use std::path::Path;
use rusqlite::DatabaseName;

fn main() -> (){

  let conn = Connection::open_in_memory().unwrap();

  let result = conn.execute("CREATE TABLE goods (
            id             INTEGER        PRIMARY KEY ON CONFLICT FAIL AUTOINCREMENT
        );", &[]);
  conn.execute("insert into goods values(1)").unwrap();
  conn.backup(DatabaseName::Main, Path::new("goods.db"), None).unwrap();
  println!("done");
}

did I do something wrong with it?  Thanks for your help!

Missing backup feature I guess ?


Share single realm store between datastores #4568

Closes #4568

it reduses usage of Wallet.functional.realm(forAccount: wallet) to single place, as well as creeating RealmStore(realm for each realm, for each data store. with this pr, we use single storage


Support podcast properties a la Media RSS

Apple podcasts still point to Media RSS specs from 2003 and use very old constructs:
https://help.apple.com/itc/podcasts_connect/#/itcb54353390
Is there a way we can make ninjs support podcast behaviour, perhaps even talk to podcast providers to see what they would like to add, so people could mark up podcasts using ninjs instead of Media RSS?

Maybe step 1 is to map ninjs to media RSS and see what maps directly and what needs adding.

I had a look at this and to my understanding RSS is a XML standard with this podcast extensions defined by Apple. So is this a question for NAR/NewsML-G2 primarily?

Closed since we have the same type of discussion in #69.


Support angular projects

Hi,
I fixed some of the missing type declarations. This library can now be imported into Angular and other similar frameworks.
I had to change Geometry to BufferGeometry  in src/parsers/CityObjectParser.js because according to [THREE] (https://discourse.threejs.org/t/three-geometry-will-be-removed-from-core-with-r125/22401) Geometry is no longer renderable.
Thanks.

Hey @imtiazShakil,
I see your point. Nevertheless, I think you have misidentified the problem.
First of all, the library doesn't make an explicit request itself. This is done on the browser because of the creation of a WebWorker to allow the geometry to be parsed on another thread.
Second, your problem here isn't that the request is blocked. What is happened, rather, is that you receive a 404 stating that /helpers/ParserWorker.js does not exist. The blocking message is showing up after that, because I assume that your backend returns some dummy 404 HTML page as a response. Since the browser was expecting a JavaScript file but your backend returns an HTML page, that's why you get the blocking message.
Why is /helpers/ParserWorker.js missing? I assume it's because you haven't made your bundlers (webpack or whatever else you might be using) to include this file in the build and, therefore, it doesn't end up in your deployment. I've had a similar issue and since I am not a bundler expert either, what I ended up doing was to use parsel.js which seems to be "clever" enough to work out of the box with web workers and bundle them correctly.
Therefore, here is what can be done:

you can try to make your bundler work with the web worker. I could try to take a look at this one, particularly if that's something that we need to resolve in the library as well.
you can switch to parcel.js which, according to my experience, works fine with this and should not create any issues for you.
you can try to make a non-WebWorker version of CityJSONWorkerParser (e.g. a CityJSONParser class) that would, basically, use the ChunkParser (like the current parser class) and create all objects etc, just not through ParserWorker.
you can keep the obsolete classes, although I am not sure how reliable they are, anymore, and they are considered old and unmaintained code.

I have to admit, the last option might seem the most compelling and easy solution, but it is my least favorite and recommended one. On the other hand, I wouldn't want to make you spend too much time on it if you don't think it's worth it, so if you insist on it I can approve this PR. Keep in mind, though, that I will, eventually, remove these classes in a future update.

Hi @liberostelios , Thanks for the explanation.

Why is /helpers/ParserWorker.js missing? I assume it's because you haven't made your bundlers (webpack or whatever else you might be using) to include this file in the build and, therefore, it doesn't end up in your deployment. I've had a similar issue and since I am not a bundler expert either, what I ended up doing was to use parsel.js which seems to be "clever" enough to work out of the box with web workers and bundle them correctly.

I investigated on this issue. What I found is both webpack and parcel.js can handle webworker files (creating a separate package for them), but inorder to achieve that the library has to be bundled. I imported un-bundled cityjson-threejs-loader   in my angular project, that's why I was facing this issue.
But after I bundled cityjson-threejs-loader using yarn parcel build src/index.js, I stumbled into other issues

in the dist folder the type declaration files are missing (eg. .d.ts files)
after manually copying the type declaration files, I was able to import and transpile cityjson-threejs-loader library in my angular project. But then I failed due to some issues where webpack doesn't understand parcel.require. I forgot the actual error message but it was something like this ERROR Error: Uncaught (in promise): ReferenceError: assignment to undeclared variable parcelRequire

So based on the above experience I think external projects may not able to use CityJSONWorkerParser out of the box.
Finally I followed your following advice.

you can try to make a non-WebWorker version of CityJSONWorkerParser (e.g. a CityJSONParser class) that would, basically, use the ChunkParser (like the current parser class) and create all objects etc, just not through ParserWorker.

Now everything is working when I'm using CityJSONParser.  So please review this new class. Let me know if you find any bugs.
Thanks.

Hello @liberostelios , Hope you are doing fine.
Did you get any time to check on the latest commits?
I would like to hear your feedback, thanks!

Hi @imtiazShakil,
I haven't been able to test the new class in practice. It seems to be fine, but I think there is a lot of duplication that we could have avoided there. Since I understand that this was already a lot of effort for you and I understand that the code is already at a state that serves the purpose of your project, I'll merge it as it is right now and make sure to refactor it in the future.
Thank you for your contribution 🙌


Mobile Trading Page: Mobile Keyboard shouldn't cover order ticket inputs

Works great when using Decore Wallet and moves the order ticket up but in Coinbase Wallet this behaviour isn't working.
Note: We need to test this in other mobile wallets

@JohnDanz can we address this?

I'm actually seeing the keyboard move the view like we would expect. you can still scroll once the keyboard is up but that's always the behavior as far as i can tell. I don't see it covering any of the inputs however unless i force it to.

it's prob phone dependent. mine the order form is covered up but I can just scroll to see more of the phone. I think we are good on this, users won't get confused.

See when i clicked it, and it pushes the whole screen -- and when i explicitly started the input at the very bottom of my phone view it moved it to the right spot.

@Chwy5 I don't think this is an issue and user expects the behaviors described above. Ether the content gets pushed up or the user can scroll the content. Plus I don't see how we could address the keyboard moving or not moving the content.
recommend closing

closing


[MINOR] Revert removing explicit typing (changed in some examples and StatFunctions)

What changes were proposed in this pull request?
This PR reverts some changes in https://github.com/apache/spark/pull/12413. (please see the discussion in that PR).
from
    words.foreachRDD { (rdd, time) =>
    ...

to
    words.foreachRDD { (rdd: RDD[String], time: Time) =>
    ...

Also, this was discussed in dev-mailing list, here
How was this patch tested?
This was tested with sbt scalastyle.

cc @rxin

Thanks! LGTM.

Actually, shouldn't we maybe a bit wait for arriving at conclusion? I am leaning toward that this change is correct but feel like some think not although it is a tiny monir change.

Test build #56046 has started for PR 12452 at commit 52f1324.

Test build #56046 has finished for PR 12452 at commit 52f1324.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56046/
Test FAILed.

retest this please

Test build #56055 has started for PR 12452 at commit 52f1324.

Test build #56055 has finished for PR 12452 at commit 52f1324.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56055/
Test FAILed.

retest this please

Test build #56060 has started for PR 12452 at commit 52f1324.

Test build #56060 has finished for PR 12452 at commit 52f1324.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56060/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

test this please

(The tests org.apache.spark.sql.hive.HiveSparkSubmitSuite.SPARK-8020: set sql conf in spark conf	 and
org.apache.spark.sql.hive.HiveSparkSubmitSuite.SPARK-9757 Persist Parquet relation with decimal column pass in my local)

Test build #56076 has started for PR 12452 at commit 52f1324.

Test build #56076 has finished for PR 12452 at commit 52f1324.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56076/
Test FAILed.

Test build #2814 has started for PR 12452 at commit 52f1324.

Test build #2814 has finished for PR 12452 at commit 52f1324.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds no public classes.

OK i'm just going to merge this. It's actually not that big of a deal, but I wanted to make a point about avoiding changing code for the sake of changing code. Thanks a lot for bearing with me @HyukjinKwon .


Test failures on master with DataArray.to_cdms2

See https://travis-ci.org/pydata/xarray/jobs/410459646
Example failure:
=================================== FAILURES ===================================
_________________ TestDataArray.test_to_and_from_cdms2_classic _________________
self = <xarray.tests.test_dataarray.TestDataArray testMethod=test_to_and_from_cdms2_classic>
    def test_to_and_from_cdms2_classic(self):
        """Classic with 1D axes"""
        pytest.importorskip('cdms2')

        original = DataArray(
            np.arange(6).reshape(2, 3),
            [('distance', [-2, 2], {'units': 'meters'}),
             ('time', pd.date_range('2000-01-01', periods=3))],
            name='foo', attrs={'baz': 123})
        expected_coords = [IndexVariable('distance', [-2, 2]),
                           IndexVariable('time', [0, 1, 2])]
        actual = original.to_cdms2()
>       assert_array_equal(actual, original)
E       ValueError:
E       error during assertion:
E
E       Traceback (most recent call last):
E         File "/home/travis/miniconda/envs/test_env/lib/python2.7/site-packages/numpy/testing/_private/utils.py", line 752, in assert_array_compare
E           x, y = x[~flagged], y[~flagged]
E         File "/home/travis/miniconda/envs/test_env/lib/python2.7/site-packages/cdms2/avariable.py", line 1177, in __getitem__
E           speclist = self._process_specs([key], {})
E         File "/home/travis/miniconda/envs/test_env/lib/python2.7/site-packages/cdms2/avariable.py", line 938, in _process_specs
E           if Ellipsis in specs:
E       ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()
E
E
E       Arrays are not equal
E        x: TransientVariable([[0, 1, 2],
E                          [3, 4, 5]])
E        y: array([[0, 1, 2],
E              [3, 4, 5]])

I think @stefraynaud worked on the cdms2 converters last. Any thoughts on what's going on here?

I suppose we probably just need to convert these TransientVariable objects explicitly into numpy arrays before using assert_array_equal?

A call to .getValue() before the comparison of the content should do the trick for both axes (coordinates) and variables.
Howerver for variables and 2D axes, the comparison will fail if the fill_value is different since .getValue() is basically a call to .filled(). In this case, a call to .asma() is more appropriate if the assertion function handles masked values.


Constant hallucinations,

I have spent over 8 million tokens over 15 hours trying to create a basic app. 90% of the time has been spent trying to fix your coding errors and doing rollbacks because the preview screen would be blank and only fixed by rolling back as Bolt.new cannot see there is a blank screen and tries to make repairs to the issues and says they're fixed but it's still a blank screen. The program will try to add a feature and then remove most of the work done to date at least 50% of the time. It's one step forward and 2 steps back. I would love to see an actual usable app made by Bolt that wasn't just a basic widget. I could learn to code quicker than I could get a usable app at my current rate.

I rollback to a saved point and the blank screen issue follows it 30% of the time. I then have to request multiple times to fix, sometimes it can fail up to 5 times before I try another rollback point, and then that point will have a different page layout that was never seen before. At the rate I'm going, I will use all my 10M tokens well and truly before I finish if all one basic app.
I have already started from scratch after I could not move past the blank preview screen which lost me hours of work for nothing.

I rolled back to a previous saved point, and now all my fields have changed to something new.  I'm not inputting the coding it's all Bolt. I am using magical more defined prompts 90% of the time. Please fix these coding issues and top up my tokens.


align licenses

What I did the other day in The-AI-Alliance/community was have the three licenses named thusly:

LICENSE.Apache-2.0
LICENSE.CC-BY-4.0
LICENSE.CDLA-2.0

However, that scheme doesn't indicate which one applies where, like your scheme. Also, there is no single LICENSE file there now. I don't know if that's bad or okay?
Anyway, I'll approve the PR.


Support for Life A2 NC

It would be great, if you could add support for the Soundcore Life A2 NC.

Have you tried it anyway, because it might work even though I haven't listed it.

Yes, I have tried it, I selected the headphones from the menu inside the Sonitus settings. If I try to change to noise cancel, the blue button appears and then disappears without any changes. Inside the Soundcore app it’s working normally.

Okay, could you message me on Discord, I communication is a bit easier over there. I will need some specific logs.

No problem, I will write you tomorrow on discord :)

I have the same model, and I had try but not work, this can be great make support this model.

Hi @AleksIralda , I've send you the test version over Discord. I haven't released that version yet because it doesn't automatically detect the device, I might add a setting to choose the headphones model in the preference bundle to bypass this.


Feedback - Can not resolve SciModel

Scope
What does your feedback relate to?

[] Project aims/objectives
[] Repository structure
[x] Model plugin
[] Rimpl code
[] Documentation
[] Tests
[] Other

Details
I have tried to use IF cli with the example yaml. But I kept receiving error messages as the snapshot until I deleted the SciModel config in the graph.children.child.config.sci.

It's so weird since my colleague can resolve the same yaml file with the IF cli and we both use Mac OS and the node v18.17.1 (npm v9.6.7). The @grnsft/if, @grnsft/if-models, and @grnsft/if-unofficial-models are the same version 9.6.7.

npm i -g @grnsft/if-models

I have re-installed the dependencies and here are the log:
➜  gsf git:(main) ✗ nvm use 18.17.1
Now using node v18.17.1 (npm v9.6.7)
➜  gsf git:(main) ✗ npm i -g @grnsft/if

changed 85 packages in 2s

5 packages are looking for funding
  run `npm fund` for details
➜  gsf git:(main) ✗ npm i -g @grnsft/if-models

changed 105 packages in 13s

9 packages are looking for funding
  run `npm fund` for details
➜  gsf git:(main) ✗ impact-engine --impl test.yml

[!important] Incubation Project

This project is an incubation project being run inside the Green Software Foundation; as such, we *DON’T recommend using it in any critical use case.
Incubation projects are experimental, offer no support guarantee, have minimal governance and process, and may be retired at any moment. This project may one day graduate, in which case this disclaimer will be removed.

[!important]

You are using models that are not part of the Impact Framework standard library. You should do your own research to ensure the models are up to date and accurate. They may not be actively maintained.

InputValidationError: Invalid input
    at validate (/Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/@grnsft/if-models/build/util/validations.js:37:15)
    at SciModel.validateInput (/Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/@grnsft/if-models/build/lib/sci/index.js:99:43)
    at /Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/@grnsft/if-models/build/lib/sci/index.js:26:36
    at Array.map (<anonymous>)
    at SciModel.execute (/Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/@grnsft/if-models/build/lib/sci/index.js:25:36)
    at Observatory.doInvestigationsWith (/Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/@grnsft/if/build/lib/observatory.js:20:44)
    at Supercomputer.calculateOutputsForChild (/Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/@grnsft/if/build/lib/supercomputer.js:103:31)
    at async Supercomputer.compute (/Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/@grnsft/if/build/lib/supercomputer.js:139:13)
    at async impactEngine (/Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/@grnsft/if/build/index.js:38:22)
(node:42128) [DEP0128] DeprecationWarning: Invalid 'main' field in '/Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/<EMAIL_ADDRESS>of 'dist/index.js'. Please either fix that or report it to the module author
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:42128) [DEP0128] DeprecationWarning: Invalid 'main' field in '/Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/<EMAIL_ADDRESS>of 'dist/index.js'. Please either fix that or report it to the module author
(node:42128) [DEP0128] DeprecationWarning: Invalid 'main' field in '/Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/<EMAIL_ADDRESS>of 'dist/index.js'. Please either fix that or report it to the module author
(node:42128) [DEP0128] DeprecationWarning: Invalid 'main' field in '/Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/<EMAIL_ADDRESS>of 'dist/index.js'. Please either fix that or report it to the module author
(node:42128) [DEP0128] DeprecationWarning: Invalid 'main' field in '/Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/<EMAIL_ADDRESS>of 'dist/index.js'. Please either fix that or report it to the module author
(node:42128) [DEP0128] DeprecationWarning: Invalid 'main' field in '/Users/yuysnsun/.nvm/versions/node/v18.17.1/lib/node_modules/<EMAIL_ADDRESS>of 'dist/index.js'. Please either fix that or report it to the module author

The yaml file I used is examples/impls/test/aggregation-test.yml

If I annotate the sci model, it runs seems well:
impact-engine --impl test.yml  --ompl result.yaml

[!important] Incubation Project

This project is an incubation project being run inside the Green Software Foundation; as such, we *DON’T recommend using it in any critical use case.
Incubation projects are experimental, offer no support guarantee, have minimal governance and process, and may be retired at any moment. This project may one day graduate, in which case this disclaimer will be removed.

[!important]

You are using models that are not part of the Impact Framework standard library. You should do your own research to ensure the models are up to date and accurate. They may not be actively maintained.

here is the impl file test.yaml(I also annotate the aggregation , since the InvalidAggregationParams: Aggregation metric carbon is not found in inputs[0]. error):
name: nesting-demo
description:
#aggregation:
#  aggregation-metrics: ['carbon', 'energy']
#  metrics: ['carbon', 'energy']
#  type: 'horizontal'
tags:
  kind: web
  complexity: moderate
  category: on-premisen
initialize:
  models:
    - name: teads-curve
      model: TeadsCurveModel
      path: "@grnsft/if-unofficial-models"
    - name: sci-e
      model: SciEModel
      path: "@grnsft/if-models"
    - name: sci-m
      path: "@grnsft/if-models"
      model: SciMModel
    - name: sci-o
      model: SciOModel
      path: "@grnsft/if-models"
    - name: sci
      model: SciModel
      path: "@grnsft/if-models"
graph:
  children:
    child: # an advanced grouping node
      pipeline:
        - teads-curve
        - sci-e
        - sci-m
        - sci-o
#        - sci
      config:
        teads-curve:
          thermal-design-power: 65
        sci-m:
          total-embodied-emissions: 251000 # gCO2eq
          time-reserved: 3600 # 1 hour in s
          expected-lifespan: 126144000 # 4 years in seconds
          resources-reserved: 1
          total-resources: 1
        sci-o:
          grid-carbon-intensity: 457 # gCO2/kwh
#        sci:
#          functional-unit-duration: 1
#          functional-duration-time: ''
#          functional-unit: requests # factor to convert per time to per f.unit
      children:
        child-1:
          inputs:
            - timestamp: 2023-07-06T00:00
              duration: 10
              cpu-util: 10
              e-net: 0.000811 #kwh
              requests: 380
            - timestamp: 2023-07-06T00:10
              duration: 10
              cpu-util: 10
              e-net: 0.000811 #kwh
              requests: 380
            - timestamp: 2023-07-06T00:20
              duration: 10
              cpu-util: 10
              e-net: 0.000811 #kwh
              requests: 380
            - timestamp: 2023-07-06T00:30
              duration: 10
              cpu-util: 10
              e-net: 0.000811 #kwh
              requests: 380
        child-2:
          inputs:
            - timestamp: 2023-07-06T00:00
              duration: 10
              cpu-util: 20
              e-net: 0.000811 #kwh
              requests: 380
            - timestamp: 2023-07-06T00:10
              duration: 10
              cpu-util: 30
              e-net: 0.000811 #kwh
              requests: 380
            - timestamp: 2023-07-06T00:20
              duration: 10
              cpu-util: 40
              e-net: 0.000811 #kwh
              requests: 380
            - timestamp: 2023-07-06T00:30
              duration: 10
              cpu-util: 50
              e-net: 0.000811 #kwh
              requests: 380
        child-3:
          inputs:
            - timestamp: 2023-07-06T00:00
              duration: 10
              cpu-util: 10
              e-net: 0.000811 #kwh
              requests: 380
        child-4:
          inputs:
            - timestamp: 2023-07-06T00:00
              duration: 10
              cpu-util: 10
              e-net: 0.000811 #kwh
              requests: 380

here is the ompl file result.yaml:
name: nesting-demo
description: null
tags:
  kind: web
  complexity: moderate
  category: on-premisen
initialize:
  models:
    - name: teads-curve
      path: '@grnsft/if-unofficial-models'
      model: TeadsCurveModel
    - name: sci-e
      path: '@grnsft/if-models'
      model: SciEModel
    - name: sci-m
      path: '@grnsft/if-models'
      model: SciMModel
    - name: sci-o
      path: '@grnsft/if-models'
      model: SciOModel
    - name: sci
      path: '@grnsft/if-models'
      model: SciModel
graph:
  children:
    child:
      pipeline:
        - teads-curve
        - sci-e
        - sci-m
        - sci-o
      config:
        teads-curve:
          thermal-design-power: 65
        sci-m:
          total-embodied-emissions: 251000
          time-reserved: 3600
          expected-lifespan: 126144000
          resources-reserved: 1
          total-resources: 1
        sci-o:
          grid-carbon-intensity: 457
      children:
        child-1:
          inputs:
            - timestamp: 2023-07-06T00:00
              duration: 10
              cpu-util: 10
              e-net: 0.000811
              requests: 380
            - timestamp: 2023-07-06T00:10
              duration: 10
              cpu-util: 10
              e-net: 0.000811
              requests: 380
            - timestamp: 2023-07-06T00:20
              duration: 10
              cpu-util: 10
              e-net: 0.000811
              requests: 380
            - timestamp: 2023-07-06T00:30
              duration: 10
              cpu-util: 10
              e-net: 0.000811
              requests: 380
          outputs:
            - grid-carbon-intensity: 457
              energy: 0.000057777777777777776
              operational-carbon: 0.026404444444444442
            - grid-carbon-intensity: 457
              energy: 0.000057777777777777776
              operational-carbon: 0.026404444444444442
            - grid-carbon-intensity: 457
              energy: 0.000057777777777777776
              operational-carbon: 0.026404444444444442
            - grid-carbon-intensity: 457
              energy: 0.000057777777777777776
              operational-carbon: 0.026404444444444442
        child-2:
          inputs:
            - timestamp: 2023-07-06T00:00
              duration: 10
              cpu-util: 20
              e-net: 0.000811
              requests: 380
            - timestamp: 2023-07-06T00:10
              duration: 10
              cpu-util: 30
              e-net: 0.000811
              requests: 380
            - timestamp: 2023-07-06T00:20
              duration: 10
              cpu-util: 40
              e-net: 0.000811
              requests: 380
            - timestamp: 2023-07-06T00:30
              duration: 10
              cpu-util: 50
              e-net: 0.000811
              requests: 380
          outputs:
            - grid-carbon-intensity: 457
              energy: 0.00008625546239837399
              operational-carbon: 0.039418746316056914
            - grid-carbon-intensity: 457
              energy: 0.0001072720189701897
              operational-carbon: 0.04902331266937669
            - grid-carbon-intensity: 457
              energy: 0.00012295117716802168
              operational-carbon: 0.056188687965785904
            - grid-carbon-intensity: 457
              energy: 0.00013541666666666666
              operational-carbon: 0.061885416666666665
        child-3:
          inputs:
            - timestamp: 2023-07-06T00:00
              duration: 10
              cpu-util: 10
              e-net: 0.000811
              requests: 380
          outputs:
            - grid-carbon-intensity: 457
              energy: 0.000057777777777777776
              operational-carbon: 0.026404444444444442
        child-4:
          inputs:
            - timestamp: 2023-07-06T00:00
              duration: 10
              cpu-util: 10
              e-net: 0.000811
              requests: 380
          outputs:
            - grid-carbon-intensity: 457
              energy: 0.000057777777777777776
              operational-carbon: 0.026404444444444442

oooh ok - i see the problem.
The example impl you are using is out of date - there is a PR open to fix this and I'm reviewing it now - I'll tag you in this comment thread when it's done so you can grab the up to date one.

closing as complete


npm test fails because of missing css

IMPORTANT: This repository's issues are reserved for feature requests and bug reports. Do not submit support requests here.
Steps to reproduce and a minimal demo of the problem
npm test
What steps should we try in your demo to see the problem?
Current behavior
End up with an error like:
WARN [web-server]: 404: /base/dist/dev/home/components/home.component.js
Expected/desired behavior
Other information
If you change the Component styleURLs from:
styleUrls: ['./home.component.css']
to:
styleUrls: ['./home.component.scss']
The tests pass.

Cheers @perrywoodin , had a quick look and need to dig into the config to process scss files with karma tests. Renaming to scss creates other problems and is probably not the correct solution, will try and look into this over the next few days.

@perrywoodin @asgarddesigns - For reference, this has nothing to do with Karma.
If you look at build.js.test.ts it inlines the templates on a test run.
With the current project implementation, all of the component styles are set to look for css which doesn't exist until the process.scss task is executed.
That said, until gulp-inline-ng2-template ludohenin/gulp-inline-ng2-template#28 supports variable resolution there isn't a whole lot you can do about it as the test build is "technically" going to fail anyway.

@d3viant0ne Yep, I'm in the same position and trying to find a way around it. My plan was to preprocess the sass files into css but not had much luck.
Failing that, removing inlining may be the temporary fix, does gulp-inline-ng2-template confer a big speed benefit? I am guessing it's probably very nice to have with the larger projects...

The test build should work exactly like the dev build - it should not do inlining of templates or CSS. Inlining is for prod builds only where we need to package up the components. Based on this, I have removed inlining from the test build. This allows the process to push forward, but it is now failing at run time. The components are not able to load the templates. I can't figure this one out, because the templates do exist where the component is looking for them!!! See the error message below:
  About component
    ✖ should work
      Chrome 49.0.2623 (Mac OS X 10.11.4)
      PhantomJS 2.1.1 (Mac OS X 0.0.0)
    Failed: Failed to load /Users/nbhati/projects/angular2-seed-sass/dist/dev/about/components/about.component.html
    invoke@/Users/nbhati/projects/angular2-seed-sass/node_modules/zone.js/dist/zone.js:308:34
    run@/Users/nbhati/projects/angular2-seed-sass/node_modules/zone.js/dist/zone.js:201:50
    /Users/nbhati/projects/angular2-seed-sass/node_modules/zone.js/dist/zone.js:553:61
    invokeTask@/Users/nbhati/projects/angular2-seed-sass/node_modules/zone.js/dist/zone.js:341:43
    runTask@/Users/nbhati/projects/angular2-seed-sass/node_modules/zone.js/dist/zone.js:238:58
    drainMicroTaskQueue@/Users/nbhati/projects/angular2-seed-sass/node_modules/zone.js/dist/zone.js:459:43

The message above says failed to load about.component.html. I don't understand why - the file does exist at that location. Any ideas?

@nareshbhatia - I tried to get this to work properly for almost a week and eventually gave up.
If you step deep into zone, it's looking for it where it where it isn't ( path issue ). So while it's technically a bug, it's going to get stuffed in a back log somewhere because I'm sure SASS / SCSS support for inline templates isn't in the 1.0 scope.
My solution to this was a postcss implementation that as a side-effect decreased by build/re-build times quite a bit. So call it 90% of the Sass functionality I wanted with none of the b.s. trying to get this to work properly.

Hmmm, interesting! Can you please clarify why it is a SASS / SCSS support issue? The way the test process is set up, there is no SASS involved at runtime - the compiled JS file looks like this:
AboutComponent = __decorate([
    core_1.Component({
        selector: 'sd-about',
        moduleId: module.id,
        templateUrl: './about.component.html',
        styleUrls: ['./about.component.css']
    }),

At runtime about.component.html and about.component.css are available in the same folder. So I can't understand why they can't be loaded. This is the exact same setup during the dev build and there are no issues there.

It took me a while to trace it, but I think in the end the solution is just a two-line change in karma config. I attached a pull request.

Awesome work, @amaltsev! Merged.
Thanks.

Wow, talk about looking in the wrong place. Seed : 1, Josh : 0. @amaltsev Nice job running that down.


已经设置了id仍然报错401

https://github.com/CarGuo/GSYGithubAppFlutter/issues/111
https://github.com/CarGuo/GSYGithubAppFlutter/issues/105


Does Xamarin.Forms for TV support TV Remote Controller?

Hi,
I want to start an Tizen TV application with c# and I would like to know if i create the Xaml UI with Xamarin.Forms, do i get TV remote controller support? I can navigate menus and give input using remote controller?
I know that same thing for Xbox using XF, it is not possible to use joystick or remote controller with xamarin.forms uwp. Only native UWP works.
is it the same for Tizen and XF?
thanks for the help

Hi @EmilAlipiev! What exactly does support for the remote controller mean?
If you mean using the remote control to move or select focus between UI elements, it is already supported.
Or if it means controlling a separate input device such as a game pad, please refer to the API below.
https://developer.samsung.com/smarttv/develop/api-references/tizenfx-tv-api-references/tizen.tv.accessory/gamepadbuttons-struct.html

Hi @EmilAlipiev! What exactly does support for the remote controller mean?
If you mean using the remote control to move or select focus between UI elements, it is already supported.
Or if it means controlling a separate input device such as a game pad, please refer to the API below.
https://developer.samsung.com/smarttv/develop/api-references/tizenfx-tv-api-references/tizen.tv.accessory/gamepadbuttons-struct.html


test assertion assumes a clean postgres db

i am running make test on master and it is failing because the expected tables returned by statements.PG_OBJECTS does not exactly match the tables that the running postgres has. statements.PG_OBJECTS returns tables from all databases, not just the one that the client.TestAll() creates. however, the test at line 203 asserts equality- which fails as the following output demonstrates
▶ make test
godep go test -cover ./...
?   	github.com/sosedoff/pgweb	[no test files]
ok  	github.com/sosedoff/pgweb/pkg/api	0.026s	coverage: 8.3% of statements
ok  	github.com/sosedoff/pgweb/pkg/bookmarks	0.015s	coverage: 100.0% of statements
Teardown error: exit status 1
--- FAIL: TestAll (1.34s)
        Error Trace:    client_test.go:203
			client_test.go:340
	Error:		Not equal: []string{"alternate_stock", "authors", "book_backup", "book_queue", "books", "customers", "daily_inventory", "distinguished_authors", "editions", "employees", "favorite_authors", "favorite_books", "money_example", "my_list", "numeric_values", "publishers", "schedules", "shipments", "states", "stock", "stock_backup", "subjects", "text_sorting"} (expected)
			        != []string{"alternate_stock", "authors", "book_backup", "book_queue", "books", "customers", "daily_inventory", "distinguished_authors", "editions", "employees", "favorite_authors", "favorite_books", "money_example", "my_list", "numeric_values", "persons", "publishers", "schedules", "shipments", "states", "stock", "stock_backup", "subjects", "text_sorting"} (actual)

			Diff:
			--- Expected
			+++ Actual
			@@ -1,2 +1,2 @@
			-([]string) (len=23 cap=23) {
			+([]string) (len=24 cap=32) {
			  (string) (len=15) "alternate_stock",
			@@ -16,2 +16,3 @@
			  (string) (len=14) "numeric_values",
			+ (string) (len=7) "persons",
			  (string) (len=10) "publishers",

FAIL
coverage: 46.5% of statements
FAIL	github.com/sosedoff/pgweb/pkg/client	1.362s
ok  	github.com/sosedoff/pgweb/pkg/command	0.014s	coverage: 80.0% of statements
ok  	github.com/sosedoff/pgweb/pkg/connection	0.178s	coverage: 90.0% of statements
?   	github.com/sosedoff/pgweb/pkg/data	[no test files]
?   	github.com/sosedoff/pgweb/pkg/history	[no test files]
?   	github.com/sosedoff/pgweb/pkg/shared	[no test files]
?   	github.com/sosedoff/pgweb/pkg/statements	[no test files]
?   	github.com/sosedoff/pgweb/pkg/util	[no test files]
godep: go exit status 1
make: *** [test] Error 1

lets change the assert.Equal in line 208 to something that checks asserts that objects["public"].Tables contains all the expected tables. something like :

	for table := range tables {
		assert.True(t, stringSliceContains(objects["public"].Tables, table))
	}
	// stringSliceContains(a,b) returns whether slice a contains string b

How did you get extra tables in the test database?

i didn't. look slike statements.PG_OBJECTS returns tables from all the databases

PG_OBJECTS statement only returns objects from the current database. Also, if you look at client tests, it drops and then recreates the database on every run so you should not have any extra tables in your database. Would need more info on your setup since i cant reproduce your issue.

You should not have any tables while running make test since it will drop and recreate the database on every run, see https://github.com/sosedoff/pgweb/blob/master/pkg/client/client_test.go#L332
Closing for now since its an edge case and has something to do with your local setup. I tried to reproduce with no luck.

sorry for replying late @sosedoff. i found out that for some reason whenever i create a new pg database, it was automatically creating a table named "person". i think there is some default schema being applied to every new table and that was polluting the test db. since this is an issue very specific to my machine setup, im going to close the pull request as well. thanks for getting back though!

@akarki15 check the template1 database.
https://www.postgresql.org/docs/current/static/sql-createdatabase.html

holy shit that was it. thanks a lot @cbandy!


[feature request] Add zoom-fullscreen info to query

At the moment, the output of yabai -m query --spaces has the field:
"native-fullscreen": 1
to let you know whether a space contains a natively fullscreened app in it or not.
However there is no equivalent field to let you know whether or not there is a zoomed window, e.g.
"zoom-fullscreen": 1
My use case for this is to be able to display in my ubersicht bar which spaces have a zoomed window on them. Currently I just have to press my keybinding to toggle zoom-fullscreen to check if a window on that space was zoomed or not.
If you are open to adding this feature, a corresponding event for when a zoom-fullscreen is toggled would be amazing (otherwise the ubersicht widget would have to resort to polling)

This is already available as a window query.
yabai -m query --windows --window | jq '."zoom-fullscreen"'

You can also query this for a whole space by checking if any window on a given space is fullscreen:
yabai -m query --windows --space | jq -e 'map(select(."zoom-fullscreen" == 1)) | length > 0'
false

@dominiklohmann oh thats awesome thank you! I guess I didn't play around with all of the query flags enough.
I just double checked and I'm pretty sure there is no event for it though, is that correct? Unless it's included in the bar_refresh event?

There is no signal for it. The signals only reflect system events.
As this can be triggered through yabai only, you can just run code when you toggle a windows zoom-fullscreen property.

ah of course! Thanks for the help, I'll try and get this working when I have a sec and post the result here for others who may be trying to do the same/similar thing :)

Ok it took me a while since I've never written my own jq before, but I got it working. I ended up writing a script that inserts the zoom-fullscreen variable into the output of yabai -m query --spaces so that it can be easily integrated into ubersicht.
Script can be found here for anyone who wants it :)

@dominiklohmann The above script that I have is really slow because it has to N + 1 queries, where N is the number of spaces. And since it's a bash script, needs to run the commands in series.
Is there a way to get this information in less yabai queries? Atm the ubersicht bar takes 2-3 seconds to update...

You don't need to restrict your query to a single space.
yabai -m query --windows | jq 'group_by(.space) | map({"\(.[0].space)": (map(select(."zoom-fullscreen" == 1)) | length > 0)}) | add'

Example output:
{
  "1": false,
  "2": false,
  "3": false,
  "4": false
}

@dominiklohmann thank for the tip about the single windows query 👍
I ended up implementing it as a node script instead so that I can run the two commands in parallel. It is basically the same speed as just running yabai -m query --spaces now.
// This script adds the field "zoom-fullscreen" to the output of each object in $(yabai -m query --spaces)
// If a window within a space is currently zoomed in, the value will be 1, otherwise 0
import * as util from "util"
import * as cp from "child_process"

const promiseExec = util.promisify(cp.exec)

const spacesCommand = promiseExec("/usr/local/bin/yabai -m query --spaces")
const windowsCommand = promiseExec("/usr/local/bin/yabai -m query --windows")

Promise.all([spacesCommand, windowsCommand])
    .then(([spacesOutput, windowsOutput]) => {
        const spaces = JSON.parse(spacesOutput.stdout)
        const windows = JSON.parse(windowsOutput.stdout)
        // Add "zoom-fullscreen" to each space object
        const defaultZoomFullscreen = spaces.map(space => ({...space, "zoom-fullscreen": 0}))
        windows.forEach(window => {
            if (window["zoom-fullscreen"] == 1) {
                defaultZoomFullscreen[window.space -1]["zoom-fullscreen"] = 1
            }
        })
        process.stdout.write(JSON.stringify(defaultZoomFullscreen))
    })

I ended up implementing it as a node script instead so that I can run the two commands in parallel.

Note that you can also do this in shell scripts, the syntax just isn't very ergonomic.
Great to see you found a solution to your problem, and thanks for sharing it. 👍


deploy：Problem executing script

Search before asking

[X] I had searched in the issues and found no similar issues.

Question
There was a problem executing the script：
Error from server (ServiceUnavailable): error when retrieving current configuration of:
Resource: "storage.k8s.io/v1, Resource=storageclasses", GroupVersionKind: "storage.k8s.io/v1, Kind=StorageClass"
Name: "local-hostpath", Namespace: ""
from server for: "manifests/host-path-sc.yaml": apiserver is shutting down
Error: exit status 1
hardware configuration
cpu:j1900  Memory：6G

If you're deploying directly with k8s and not through sealos, you'll need to handle pv,pvc,sc on your own


Add information to README.md about using NVM

Hey Guys!
I tried out the spatie/markdown package yesterday and I got stuck on why it would not render properly. It transpires the issue was that I use NVM, and the package was looking for node in a particular place, where it was not. It took me far longer to realize that this was what was happening, and required the help of someone in the Laracasts forum too!
My first though was to update the package to accept another variable, so the user could specify the location of their node executable. But then I decided it probably made more sense just to symlink the file instead, as the likelihood is, in production, node would be installed instead of NVM, so it's less of an issue.
I figured it would be good to add this to the readme, to help anyone else that gets stuck. If this PR is accepted, I will also make a similar on one the spatie/markdown package too!
Thanks Guys :)

Thanks!


.env variable for NEXT_PUBLIC_DEFAULT_CHANNEL=default-channel doesn't work

Summary
Changing the .env value for NEXT_PUBLIC_DEFAULT_CHANNEL does not do anything. A quick search shows that value is never read.
Steps to reproduce

Change the .env NEXT_PUBLIC_DEFAULT_CHANNEL to anything.
Start the server.

A link to a reproduction repository
No response
What OS are you using?
No response
Your next.config.js file
No response
Builds logs (or link to your logs)
No response
Function logs
No response

Yes, this variable does nothing. It is hardcoded in lib/region.ts


Link to Awesome MD List & Projects

Hi @BubuAnabelas,
I've jsut started a markdown resources project. I've added links to other similar projects, including yours:
https://github.com/tajmone/markdown-guide#awesome-markdown
Could you also add a generic links section, offering links to similar projects and Awesome Markdown lists? It makes it easier for users to find similar projects, and creates a nice web of resources.

I appreciate being in your list, but as I'm trying to make a truly awesome markdown list it doesn't feel right to add similar stuff, as it wouldn't really contribute to the users looking for awesome markdown tools and editors.
Thank you again for adding this repo to the list! :+1:

True, my repo doesn't qualify as an Awesome list.
Thanks all the same!


Integrate Analytics

With the analytics lib introduced in #118, we can now actually integrate it to track things.

[x] Integrate with login
[x] Integrate with command framework (e.g. validation, help, context, etc.)
[x] Integrate with vip app
[x] Integrate with vip app list
[x] Integrate with vip sync
[ ] Add disclaimer on login
[ ] Add opt-out
[x] Make sure analytics failures are non-critical
[ ] Review all events to make sure they are necessary and useful
[ ] Switch uuid to GH ID after login.

Overall looks good. There are some instances where I'm not sure if trackEvent will resolve before the CLI exits. The idea of "fire and forget" is nice, but I'm not sure how it works in practice since we're not working with a long-running process.

The idea of "fire and forget" is nice, but I'm not sure how it works in practice since we're not working with a long-running process.

Those are all supposed to be blocking async actions (which is now fixed).
I'm not totally happy about the implementation (both the blocking aspect and the extra complexity it adds). It would be nice to move towards a single request instead (maybe firing on beforeExit + uncaughtException) and a cleaner implementation (maybe using events?).

Going to move the the disclaimer, opt-out, and Tracks user alias to new PRs.


Fix HexToBytesIter::size_hint

HexToBytesIter iterates once for each pair of hex digits.

I wrote these two tests to convince myself the patch was correct, want to add them?

    #[test]
    fn hex_to_digits_size_hint() {
        let hex = "deadbeef";
        let iter = HexDigitsIter::new_unchecked(hex.as_bytes());
        // HexDigitsIter yields two digits at a time `[u8; 2]`.
        assert_eq!(iter.size_hint(), (4, Some(4)));

    }

    #[test]
    fn hex_to_bytes_size_hint() {
        let hex = "deadbeef";
        let iter = HexToBytesIter::new_unchecked(hex);
        assert_eq!(iter.size_hint(), (4, Some(4)));
    }

And I confirmed that the second one fails on master.

Yes will add them thank you ! Let me know if you want me to pull the 'len' tests I added into their own standalone tests.

Rebase: add tests from Tobin.

Its good like this, thanks for finding this. We tried pretty hard with these iterators so its nice to have bugs removed.


Fix serial handler race condition Fixes #9

PyGPSClient Pull Request Template
Description
Amend serial_handler() to avoid race condition on null data stream.
Fixes # (issue)
#9
Testing
Please test all changes, however trivial, against the supplied unittest suite tests/test_*.py e.g. by executing the tests/testsuite.py
module or using your IDE's native Python unittest integration facilities.
Please describe any test cases you have amended or added to this suite to maintain >= 99% code coverage.

[x] Tested on all platforms Windows, Linux, MacOS, RPiOS

Checklist:

[x] My code follows the style guidelines of this project (see CONTRIBUTING.MD).
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[ ] (if appropriate) I have added test cases to the tests/test_*.py unittest suite to maintain >= 99% code coverage.
[x] I have tested my code against the full tests/test_*.py unittest suite.
[x] My changes generate no new warnings.
[x] Any dependent changes have been merged and published in downstream modules.
[x] I understand and acknowledge that the code will be published under a BSD 3-Clause license.

@semudev2 out of interest, were you running on an M1 Mac? I hear the Python 10 tkinter performance is particularly poor on these?
Shame, as on the Dell XPS Ubuntu platform I normally use it flies (at least 3 times faster than an Intel Macbook Pro) - admittedly a compiled version of Python 3.10.2 with stable optimizations enabled. I did try compiling Python 3.10 with tkinter on MacOS but life is too short.


Bump build to scala 2.11.12 and see what happens

Bumps our build to for 2.11 to Scala 2.11.12.
closes #1965

Looks like things passed here; anything else you wanted before a merge @farmdawgnation ?

yep

Or rather, nope - this looks good :P


Add captions to code blocks

https://github.com/open-function-computers-llc/better-wordpress-docs/commit/a089d70217f6c2860c36ca1de031439229b64389


How to turn off caching for the razzle-babel-loader?

razzle-babel-loader cache
I'm noticing that the razzle-babel-loader is dumping lots of files in the cache directory. I'd like to either be able to turn this off in a simple way, OR if these caches are needed, at least reduce the number of files that are generated somehow since there are tons of them
I'm using  ^4.0.0-canary.17 of razzle
Thanks

set
webpackOptions.babelRule.use[0].cache = false

set
webpackOptions.babelRule.use[0].cache = false

How about for razzle 3.x?

in conclusion, with `@canary`, and adding this to `modifyWebpackConfig`, I got dev bundle to load in IE11 ```
// 3rd party modules that need to go through babel for IE11 support in Dev
const babelLoaderIndex = webpackConfig.module.rules.findIndex(makeLoaderFinder('babel-loader'));
webpackConfig.module.rules[babelLoaderIndex].use[0].cache = false;

From where do I import this makeLoaderFinder function?


Add .TIF extension synonym

Add ".tif" as an extension synonym for ".tiff" files

Great idea. Thanks for adding!


How to mount all screens on App load

Hello, I have a simple Application with 3 simple RN WebView screens.
To avoid the page loading of each WebView as the user progresses through the stack, I would like to mount each Screen at app load time, similar to how React Native Navigation by Wix does.
I would use Wix's stack navigator implementation, but I prefer the API of this library, it's truly perfect. I understand why this library might not have this functionality implemented by default for performance reasons, but I was wondering if this was at all possible to achieve.
Any help immensely appreciated, and thank you for the great work on this lib!
createStackNavigator({
  PageOne: WebView1, // mounts on app load
  PageTwo: WebView2, // PROBLEM: mounts only when navigated to
  PageThree: WebView3 // PROBLEM: mounts only when navigated to
})

I already replied to you here https://github.com/react-navigation/react-navigation/issues/6010#issuecomment-503751540
We may eventually add a method to preload a screen before navigating to it, but it's not the same as always pre-rendering all screens.
https://github.com/react-navigation/rfcs/issues/73

@satya164 thanks, that's effectively what I would like to achieve!


Add PSP support

This requires the AUR package libretro-ppsspp-gameros. That is a patched version of the libretro-ppsspp package found in the Arch repository. The difference is that the assets are included and the libretro core has been patched to load them. I'll create a PR for that on the GamerOS repo as well.

This PR would resolve #47

I did forget to add to the readme. I can do that later. It is bedtime now 😅

I've changed the internal resolution now. This should be ready to merge.


Compare also against swiper-isearch in README

here https://github.com/raxod502/ctrlf#why-not-swiper you didn't mention swiper-isearch, which was introduced a year ago

Reasonable.

Also, having used swiper for quite a while, and having only just switched to ctrlf today (BTW I love it already!), I find the argument in that section unnecessarily weak.  It says:

The selling point of Swiper is that it shows you an overview of the matches. Ask yourself: when was the last time you actually got anything useful out of that overview?

Actually, I find that overview incredibly useful, multiple times pretty much every day.  However consult-line is a perfect substitute (and also proof that at least one other person finds that functionality useful).  So I suggest rephrasing that argument.

Maybe also worth noting that the weakness of that argument delayed my switch to ctrlf by several months.  Now I'm feeling regret for the delay ;-)

Also, having used swiper for quite a while

The question here is not about swiper but about swiper-isearch, which does everything (I suppose) ctrlf can do and even more.

Now I'm feeling regret for the delay ;-)

what for?

Maybe also worth noting that the weakness of that argument delayed my switch to ctrlf by several months. Now I'm feeling regret for the delay ;-)

taking into account that there is (and existed before ctrlf was "invented") swiper-isearch, that section should be empty since

Furthermore, Swiper constrains itself almost exclusively to line-based search by design, which makes it unsuitable to the task of quick movement within a line or movement to a commonly occurring search string.

argument is not valid either

I find the argument in that section unnecessarily weak

Fair enough. I will note that other people have said they agree with it, so I think whether or not the overview is helpful depends on the individual person. It makes sense to make this subjectivity explicit in the README.

Now I'm feeling regret for the delay ;-)

What information could have been available that would have communicated the changes of CTRLF that matter to you personally? Or was it just that the note about the overview not being helpful seemed very wrong to you, and hence you didn't look further?

@raxod502 commented on December 21, 2020 11:01 PM:

I find the argument in that section unnecessarily weak

Fair enough. I will note that other people have said they agree with it, so I think whether or not the overview is helpful depends on the individual person. It makes sense to make this subjectivity explicit in the README.

Agreed :clap:

Now I'm feeling regret for the delay ;-)

What information could have been available that would have communicated the changes of CTRLF that matter to you personally?

Well the first thing I really liked was the ability to navigate multiple matches within a single line, but that was before I realised that swiper-isearch existed.  The other thing I like is seeing the count of matches right next to the match.  Other than that and the overview, I'm not sure there are huge differences with swiper-isearch.

Or was it just that the note about the overview not being helpful seemed very wrong to you, and hence you didn't look further?

Yeah pretty much, but that was also before I learned that I could get an overview from occur (which is kind of crazy and embarrassing given that I've used emacs since 1994).  If #69 was addressed then I would not miss the absence of an overview being displayed in the minibuffer by default.

I like is seeing the count of matches right next to the match

like this?

It makes sense to make this subjectivity explicit in the README.

In such case the phrasing isn't perfect. Something like "I don't use it" would sound more stainless

@a13 commented on December 23, 2020 8:50 AM:

I like is seeing the count of matches right next to the match

like this?

No, that's not right next to the match.

right next to the match

I'm assuming you mean this functionality of CTRLF, which displays the match count and index within the buffer, rather than only the minibuffer:

Exactly.


Allow all buttons to be able to be remapped

@Fortinbra which buttons currently cannot be re-mapped?


port PR from https://github.com/arrow-kt/arrow-meta/pull/1036

mimics https://github.com/arrow-kt/arrow-meta/pull/1036

Let me merge #6 first, not that this push introduces a false state in our artifactory


Alt+click (eyedropper) in tilemap should jump to tile page

Using the eyedropper on the tilemap should open the page containing the corresponding tile in either "My Tiles" or "Gallery"

Implemented.


Update the slack invite link since the existing link expired.

Fix #39.

This change is

/assign @sarahmaddox


ambari-logsearch: Add jdeb support

This patch add debian package creation support for ambari-logsearch
package.
Signed-off-by: Naresh Bhat<EMAIL_ADDRESS>What changes were proposed in this pull request?
Add jdeb support for ambari-logsearch
How was this patch tested?
The build (release-2.5.2) and test is done on AArch64 machine with Debian-9
Please review Ambari Contributing Guide before opening a pull request.

@nareshgbhat , thanks for the contribution but this has already done in logsearch.
you can try out: (its in assembly module)
mvn clean package -Dbuild-deb


chore: add semantic-release

This looks good to me. Will this run automatically when changes are merged into master? I'm wondering how you specify if a change is major, minor, or patch.


Dev Test: Charges and Fields [+PhET-iO]

In late 2016, Charges and Fields PhET-iO went through an RC for a PhET-iO version, see https://github.com/phetsims/tasks/issues/736
5 issues were raised, 3 of which have been fixed and verified.  The remaining 2 issues are:

[x] https://github.com/phetsims/phet-io/issues/915
[x] https://github.com/phetsims/phet-io/issues/914

which are fixed and pending testing.
I noticed that the QA team has several other issues on their radar at the moment, so I was hesitant to create a new dev version now (as noted in https://github.com/phetsims/phet-io/issues/863#issuecomment-322341631 ).  The aforementioned issues may be tested in phettest.colorado.edu but before we go to full dev or RC testing, but when the priority/time is right for this issue, let @samreid or @zepumph know and they will create you a dev version on the spot.
Reassigned to @ariel-phet for prioritization, scheduling, delegation and labeling.

One other point, I think we are trying to get into a pattern where we test the non-phet-io and the phet-io versions and publish them simultaneously.

To put it in terms of https://github.com/phetsims/QA/issues/19, this seems to be the type of phet-io dev test that will be moving on to an RC.

From https://github.com/phetsims/QA/issues/19#issuecomment-320722872
It is assumed, in this case, that all wrappers will be tested. At least one browser per device listed here will be tested.

Mention the appropriate designers: @arouinfar (sim) and @samreid + @zepumph (phet-io)
Note the purpose of this sim (general release, for a study, etc...).: PhET-iO release
Sim version wrapper index link (will be published when QA team is ready)
A complete checklist of any issues to be verified: provided in top comment
Any relevant deadlines.  @kathy-phet said it would be good to have 20 PhET-iO sims by Jan 1, 2018, and yesterday @kathy-phet said:

Finishing up charges and field phet-io was also in you possible list. This would be good to make available, so if it fits to wrap that up then that would be good.

Medium priority until some of the current high priority items finish off (CCK, projectile motion, pendulum lab)

I published a dev version here:
http://www.colorado.edu/physics/phet/dev/html/charges-and-fields/1.1.0-phetiodev.1/wrappers/index/

I published a new dev version as described in https://github.com/phetsims/charges-and-fields/issues/130#issuecomment-324766969

@samreid @zepumph This got pretty decent coverage.  I hesitate to say this dev version is done testing though. It would probably be a better idea to get a new dev version before continuing than to keep going with this dev version. @samreid would you like to do another IOU until CCK is finished?

Sounds good, let me know when you are ready for the next dev version.

Next dev versions should include LOL features in joist.

Closing this issue. iO has changed quite a bit, and this issue is stale.


rustup

Prevent MIR optimizations from removing this read.

@bors r+

:pushpin: Commit c003fd0157e0b19f0fba8d3491423d6bf678d873 has been approved by RalfJung

:hourglass: Testing commit c003fd0157e0b19f0fba8d3491423d6bf678d873 with merge e29f1379413dd5ddbcbb3199bbe9faf2745824f5...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing e29f1379413dd5ddbcbb3199bbe9faf2745824f5 to master...