bad data returned by SELECT query on time series

Directions
System info: Influxdb 1.3.2, CentOS 6.6
Installation: Backend for Grafana 4.4, fed by collectd 5.5.3
In Grafana, I have a query something like this:
SELECT non_negative_derivative(sum("value"), 1m) FROM "A" WHERE "host" =~ /^$host$/ AND "instance" = 'X' AND "type" = 'Y' AND "type_instance" =~ /^$Z$/ AND time > now() - 6h GROUP BY time(2m), "type_instance"
And the data comes back like this, with really large spikes in it:
1502100120000, 1823
1502100240000, 1707
1502100360000, 1687
1502100480000, 1745
1502100720000, 15916461.5
1502100840000, 1603
Running the query with a narrower interval, I see this:
SELECT non_negative_derivative(sum("value"), 1m) FROM "A" WHERE "host" =~ /^$host$/ AND "instance" = 'X' AND "type" = 'Y' AND "type_instance" =~ /^$Z$/ AND time > now() - 4h AND time < now() - 3h GROUP BY time(1m), "type_instance"
1502100120000, 921
1502100180000, 933
1502100240000, 829
1502100300000, 823
1502100360000, 862
1502100420000, 827
1502100480000, 899
1502100540000, 865
1502100660000, 840
1502100720000, 887
1502100780000, 773
1502100840000, 798

You have a gap in your data:
1502100480000 = Mon Aug  7 06:08:00 EDT 2017
1502100540000 = Mon Aug  7 06:09:00 EDT 2017
1502100660000 = Mon Aug  7 06:11:00 EDT 2017
1502100720000 = Mon Aug  7 06:12:00 EDT 2017

You're using the derivative transformation, which calculates based on elapsed time. Meaning inconsistent time will screw it up.

I think this question would be better for the community website. If it turns out to be a bug, I can reopen it here if you comment on the issue. I think phemmer is right that this is due to a gap in the data, but the fact that your second query doesn't have that gap feels weird.
The community website is at https://community.influxdata.com.


Removing Library

Can’t seem to figure out how to remove a library.

you will need to go into the Administration section and remove from there

Nothing works in the administration section. All links throw the something went wrong error.

@MrGreen01010 ah, sorry, that's because of #1402 , which I should get a release out to fix in the next day or two.

I just hit release on v0.52.0, so you should be able to get the fix for this in a couple of hours.


Overlapping allowed even though allowOverlap is false

☑ I have searched [existing issues]
☑ I am using the [latest multi slider version]
When I set allowOverlap to false, it works as expected, but when I reload the screen, it allows me to overlap both cursors again. It also happens when I don't set allowOverlap
This is on iOS, haven't tested on Android
onValuesChange(values){
        this.setState({limitesDensidad: values})
    }

                  <MultiSlider
                        ref={e => this.slider = e}
                        selectedStyle={{
                            backgroundColor: globals.colors.tealBlueDark,
                        }}
                        unselectedStyle={{
                            backgroundColor: 'lightgrey',
                        }}
                        values={[this.props.limitesDensidad[0],this.props.limitesDensidad[1]]}
                        onValuesChange={(values) => {
                                 this.props.onValuesChange(values)
                        }}
                        containerStyle={{
                            height: 80,
                        }}
                        trackStyle={{
                            height: 3,
                        }}
                        touchDimensions={{
                            height: 40,
                            width: 40,
                            borderRadius: 20,
                            slipDisplacement: 40,
                        }}

                        customMarker={SliderDot}
                        sliderLength={this.state.sliderLength}
                        min={25}
                        max={29}
                        allowOverlap={false}
                        snapped={true}
                    />

Showing both cursors:

Now overlapped, even though allowOverlap is false (also happens when I don't set allowOverlap):

(Edited out some experimental code on a failed attempt to find a workaround)

This happens because of this calculation, if `this.props.sliderLength` or `this.optionsArray.length` are quite large and close to each other, then this value is quite small.

This value then used for calculation based on `this.props.allowOverlap`. As you can see, if it is small and there are quite a lot of values, markers will still overlap.
My suggestion would be to have prop stepLength, which will override it's calculation

Thanks @CyxouD
Have you tried with snapped={true} and it still occurs?
Can you create a repo for me in order to reproduce this and I will take a look at it

+1

@sergiotbh
Hi mate,
please use isMarkersSeparated =false
isMarkersSeparated={false}
allowOverlap={false}
snapped={true}
Hope fully it will fix your issue.

@syedtehrimabbas Your fix doesn't work:

@ptomasroos, we added this functionality in a fork of this repository (see https://github.com/kiwicom/react-native-multi-slider/commits/master).
In the package depending on it (@kiwicom/universal-components), we're targeting the GitHub URL to the repo... and this seems to trigger a weird bug in some GitLab CI pipelines with yarn install... So I would much rather use @ptomasroos/react-native-multi-slider instead of our fork.
Since it seems this issue is still open, would you consider integrating these changes here and publish a new version of the package to NPM?
We also used it in a web environment (see https://kiwicom-universal-components.netlify.com/?selectedKind=Slider&selectedStory=Default&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybook%2Factions%2Factions-panel to see it in action!), so we added some build step to make sure the JavaScript is transpiled.
e.g.

Let me know if that's something you'd like and if I could be of any help!
Thanks a lot!

Of course! Would be great to have a PR for this.

Seems like stepLength calculation is wrong, which cause the bug.
For reference the calculation:
    this.optionsArray =
      this.props.optionsArray ||
      createArray(this.props.min, this.props.max, this.props.step);
    this.stepLength = this.props.sliderLength / this.optionsArray.length;

If your slider goes from, let's say, 0 to 10:

this.optionsArray = [0, 1, ... 10]; => its length is 11
however, this.props.sliderLength should only be divided by 10 (representing the 10 sections 0-1, 1-2, ..., 9-10)

The fix is then simply to replace L56 by
    this.stepLength = this.props.sliderLength / (this.optionsArray.length - 1);
I opened a PR: #209


add support for v4 compressed

Hello Timothy,
Thank you for this useful addition.
This is a file type I did not encounter (then I had only 2 sources so far 😄).
Are you the author of the decompressor code or is it something that could be available somewhere with another license?
Best regards,

chatgippity did most of the heavy lifting tbh, it’s possibly a port of libmspack

I refactored the code a little bit and made a new package with it.
Can you please test it?
As I do not have any compressed version 4 full details files available, I can't test it myself!
I'm peculiarly curious about the naming scheme of these files, and wondering how the "compressed file" file type leading to the "compressed version 4 OAB file" can be obtained, as I don't set it anywhere in my code?

Yeah, looks good. Sorry that you had to rework my sloppy addition


Is there any practical advantage of putting Windows 10 in the user agent ?

Quite a lot of Windows 7 users must be using your browser. Let them have their representation on the OS market share charts, eh!

All major browsers changed to reporting only Windows 10 in their user agents regardless of the actual Windows version. Reporting any other version of Windows would represent a form of fingerprinting which can be used against Supermium as an "old" or "bad" browser. There have already been various issues with Cloudflare et al. blocking Supermium and this could make them even worse.
There is also the UA replacement, User Agent Client Hints (UACH). The official specification does not even properly recognize Windows NT 6.x or below (NT 6.x is equivalent to 0.x, and NT 5.x doesn't exist), and after dealing with government sites in certain countries that blocked Supermium because the brand string in the UACH was not "Google Chrome" or "Microsoft Edge", I decided that it would be risky to identify as NT 6.x or below with UACH.

but if you are still wish to alter UACHs despites, win32ss told above - welcome https://github.com/win32ss/supermium/issues/831#issuecomment-2315746158 and https://github.com/win32ss/supermium/issues/867#issuecomment-2332999022

I guess a toggle under chrome settings should suffice to most people, if it's not much of an overhead.

@xixhub
hmmm this one can be the real reason of issues with CF that gone for now. Based on some articles about the passive OS sniffing it's not something that Supermium can even access, this thing is based on the OS' TCP/IP implementation and its configuration. You can try to alter the config to mimic something else but it will affect a whole system. Sure, with extra drivers, there is an ability to do it exclusive for specific software.
I would be glad to play with them and the config on VM just for testing, but i need a playground(any site that block Supermium). browserleaks good for "debugging" necessary values, but real example need for testing


fix: added justify around to CButtonToolbar

Added justify around from bootstrap as a type for the CButtonToolbar component
#203

This PR is still valid


LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210729153322213 to main

LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210729153322213 to main with localized lcls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 42.472%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
26783

Relevant Lines:
57117

💛  - Coveralls


error

I installed the atom, and not allow me to download the packages, the error is:  Searching for "package name" failed.Show output ... it is not recognized as an internal or external command, operable program or batch file. The system can not find the path specified. And not as changing the route Many thanks in advance. regards

Please reopen a new issue and follow the issue template to provide us with the needed information to debug this issue.  Thanks!


update option comments

looks like a minor oversight from copying some option code from another command. pulled the descriptions from the Bugsnag/Client@deploy docblocks.

Thank you. 👍


Xcode 9 beta 6 There was an problem decoding this CoreML document

validator error: Description of multiarray feature '__feature_vector__' has an invalid or unspecified dataType. It must be specified as DOUBLE, FLOAT32 or INT32

Remove the existing NamesDT.mlmodel file from the project navigator.
Cd into the Convert folder and run python names.py. This will generate a new NamesDT.mlmodel
Drag and drop the new NamesDT.mlmodel into the Resources folder in the project navigator. Make sure Names is checked under the target membership.
Run

Thanks @benaneesh ! I've updated CoreML model with a new one convered using coremltools 0.6.3.


data: edgarrmondragon

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Did you mean to close your PR @edgarrmondragon ?

Did you mean to close your PR @edgarrmondragon ?

Yes! sorry for the noise 😄

no problem


LogicError: create_buffer failed: INVALID_BUFFER_SIZE

I am following the tutorial on computing the capacity of a cube with a re-entrant corner found here:
https://nbviewer.org/github/bempp/bempp-cl/blob/master/notebooks/laplace/reentrant_cube_capacity.ipynb
When I input:
sol, _, iteration_count = bempp.api.linalg.gmres(op, rhs, use_strong_form=True, return_iteration_count=True)
I get the error on the title. I tried SciPy 1.6.0 and 1.7.0. Any guidance on this?

It could be that you are running out of memory when running that example. Could you try running with (eg) h=0.5 and see if the error still happens?


Test against PHP 8.1

Codecov Report

Merging #5 (277c206) into master (0e06b2a) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              master        #5   +/-   ##
===========================================
  Coverage     100.00%   100.00%
  Complexity        53        53
===========================================
  Files              4         4
  Lines            177       177
===========================================
  Hits             177       177

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 0e06b2a...277c206. Read the comment docs.


Window constraints

Hi, thanks for this library. Are there any plans to add local and global windowing constraints? I'm interested in asymmetric local windows that retain the original time series size, and global windows that don't stray too far from the main diagonal.

Hello, thank you for your interest in the library!  Actually, I added support for a Sakoe-Chiba band in version 0.1.6 back in April.  I just updated the documentation, and you can see an example here:
http://www.ctralie.com/Research/linmdtw/notebooks/BasicUsage.html
As for asymmetric windows, I have no immediate plans, but I would welcome pull requests!
Hope that helps.
Best,
Chris

Hi @radkoff, just curious what your thoughts are on this, and if we should leave this issue open

Thanks for the info. It turns out the asymmetry is a dealbreaker for me. I'm still working out whether DTW is the right approach for what I'm working on, and if so, I may circle back with a pull request!


Support file sharing between evaluations and tools

Currently the only way to pass data between an eval and a tool is via JSON through the protocol. This becomes a bit unwieldy for evals that need to send a lot of input data or that require the tool to send back a lot of output data. Perhaps we should also allow a session to include a shared directory that the eval and tool can both and read and write.
This raises a couple questions:

How can the protocol (currently encapsulated in run.py) expose this in a way that remains agnostic of the way the eval and tool are implemented? Currently the eval and tool just need to be commands that can be run to produce processes with stdin and stdout, but this change would require them to have more complex interactions with the outside world. It might be fine though; we already have eval.sh and tool.sh pass the --interactive flag to docker run, so maybe we can just do a similar thing for a filesystem mount.
Should filesystem events be reflected in the protocol at all? Or should it simply be conventional? For instance, perhaps the eval can make sure to write an input file before it sends an "evaluate" command, and require that the tool write its output file before it sends its response.
How should output files be saved for later analysis and validation? Currently the entire session can be saved as one JSON file, but with this change, the filesystem could potentially undergo destructive writes in the course of a session. Should we just save all the files in the final state of the shared directory? Or should we impose some limitations that ensure that, e.g., files can only be written once and not overwritten?

I have an idea for how to do this. If the protocol is modified such that the input and output data is represented as file names in the messages, then the tool.sh automation (or something it invokes) can automatically detect when a Docker image is invoked, and transparently copy files and and forth and rewrite the file names in the messages. This means the automation needs to be somewhat protocol-aware rather than just a dumb proxy, but the important thing is that specific tool implementations don't have to care - it will all be completely transparent.
I think persistent storage of output (and input) files should be done on the "host", understood as the system that runs run.py, outside the Docker images. Actual validation can be done in Docker images, by sending files there, using the same idea of transparently copying files and rewriting file names.

@athas this roughly lines up with what I was thinking, and I like the idea of handling it in tool.sh. How difficult would it be to throw together a prototype? If it's not too hard, I think I'd have an easier time deciding whether this makes sense upon looking at an initial implementation of the idea.

I'm not much of a Docker expert, but I'll give it a shot.

As of #130, we've now ported all the evals from ADBench without needing this feature, so I'm going to close this; if we turn out to need it later, we can reopen it then.

The reason this has not become necessary is because the PyTorch implementation (used for validation) is so slow that all the ADBench-derived evals use only the smallest datasets by default. It may still be the case that shuffling a 1GiB Jacobian over JSON is fine, but we should probably check at some point. Although I suspect the bottleneck will actually be the terminal printing in run.py.

Yep, so maybe e.g. #137 will help. As an aside, I've also considered changing the format printed by run.py from just JSON to JSON Lines, which would then make it easier to build something like run-pretty.py on top of the intermediary rather than just replacing the entire intermediary.


UI minor changes to improve legibility

[UI minor changes to improve legibility UPDATED]
Minor style changes in App, data-table, menu, item and start css files to improve tables legibility and color contrast without modifying the original palette colors.
Screenshots🗒

.deploy to development

As requested, please review this new proposal of UI color style changes.

Thank you for this PR! We should have raised concerns here rather than in Discord to keep things in one place, but thank you for making tweaks based on feedback. Will try to keep future discussion here so it's easier to follow. I hope to take a look in earnest later today (but someone else might get to it first). Will do a test deploy for now though.

.deploy to development

Thank you, i read all the conversation this morning so i tried to take all the considerations into this. But if you do not agree with this new PR, no problem ;)

Sorry for taking so long to get to this! Theme changes are always kind of fraught because people tend to have strong feelings on how things should look. Thank you for taking the time to make the initial PR and for this revision. The smoky background is a cool touch, imo. Unfortunately, I've been elected by the core maintainers to convey the message that this is a bit too much of a change. It really changes the overall feel of the site and makes things much darker feeling. That doesn't necessarily make it "wrong", but there's some concern that the original site's character gets somewhat lost. Maybe for starters, just start with smaller tweaks like making the background ~ 2% darker and changing the link color to something slightly lighter (e.g., in the neighborhood of #cab286) but maintaining the current link color for hovers.
Again, we really appreciate your efforts on this, and we don't want to discourage you from contributing more in the future. Big theme changes can just be rather controversial and it seems we're a bit stuck in our ways in that regard.
P.S. If you want to spin your translation additions off into a separate PR, we can get those merged ASAP.

I understand @Razzmatazzz, thank you for taking this into consideration anyway. I really thought that it wouldn't be approved, but i had a lot of fun trying to get a more attractive look and feel for the site. The translations will be finished on this weekend so i´ll create the PR when done.

Ok, thanks again for all the effort. It is very much appreciated.


Animation/stylings issues in date range picker

Demonstrable on website here
On 'default' style for date range picker:

Range shading overlaps beyond the curvature of the beginning (earlier) date, resulting in a visual inconsistency.

On 'default' and 'new_york' styles:

Deselecting an end-date incorrectly renders the range shading fading away. While fading away, each day appears as a 'bubble' shading, as if it were selected, rather than maintaining the solid bar expected for the date-range shading.

Image captured mid-deselect animation

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


[Qdrant] Figure out 3-large dimension

See: https://github.com/dust-tt/dust/pull/5270
text-embedding-3-large
3072 native but vectors are designed such that they can be truncated to lower dimensionality.
Staying at 1536 would have no memory impact and seems like a nice trade-off:
https://openai.com/index/new-embedding-models-and-api-updates/

We decided to stick with 1536 as first intent


Sanitize values in message_dict before serializing to json

If one attempts to log a message, that is a bytestring containing invalid utf-8, json.dumps in makePickle raises UnicodeDecodeError. This pull request attempts to fix this by sanitizing offending values in message_dict using repr. While attempting to log raw byte sequences is not particularly a good idea, a logging library by any means should not just error out, it should make the best effort to log the message, whatever it contains (that is the behaviour of loggers / handlers in the standard library).
Tests, demonstrating erroneous behaviour are also included.

Closing it since it's not active.


Failure to load dependencies with long file names on Windows

Problem

When trying to build a crate on Windows that has dependencies with long file names, cargo fails to pull dependencies with a "path too long" error. This issue does not seem to appear on Linux (tested with WSL).
The output I got from cargo build
error: failed to load source for a dependency on `curve25519-fiat`

Caused by:
  Unable to update https://github.com/calibra/rust-curve25519-fiat.git#d7e30233

Caused by:
  failed to update submodule `fiat-crypto`

Caused by:
  failed to update submodule `coqprime`

Caused by:
  invalid path '\\?\C:\Users\User\.cargo\git\checkouts\rust-curve25519-fiat-d934e46b8646fad1\d7e3023\curve25519-fiat\src\external\fiat-crypto\coqprime\src\Coqprime\examples\prime216656403549020227250327256032933021325435259861468456540459488823774358486649614451547405419273433458932168893949521787.v' (path too long); class=Filesystem (30)

Steps

git clone https://github.com/libra/libra.git
cargo build

Possible Solution(s)

I assume this issue is related to this bug that exists in libgit2 since 2015: https://github.com/libgit2/libgit2/issues/3053. If so, pushing for a fix in libgit2 may resolve this issue.
Make cargo use the system's git command, or add an option to use another binary instead of libgit2.

Notes
Output of cargo version:
cargo 1.37.0-nightly (4c1fa54d1 2019-06-24)

As of today, libra is locked on rust nightly-2019-07-08.

I can confirm that adding git-fetch-with-cli doesn't help


Add job that targets the latest mono-devel

@enricosada I have no idea whether I got the build commands right here or anything, but you can modify this PR branch.

@dotnet-bot test ci please

@dotnet-bot test Ubuntu x64 Release Build please.

Thank A LOT @mmitche !
I'll modify the build script to take advantage of this specific build agent! thank a lot!


Question: Ban Risk?

I just came across an article that pointed out this new (?) article on Niantic's FAQ that references permanent bans due to "accessing Pokémon GO clients or backends in an unauthorized manner including through the use of third-party software."
I know that technically we fall into this category, but in practice, I don't think what we're doing is that bad. We're basically just reading the list of monsters and occassionally performing a simple rename or transfer operation. I don't even know how Niantic might be able to detect this, although I'm sure if there's a will there's a way.
@Eric-Carlton, what are your thoughts on this? Do you think there is a high risk of Niantic getting wise to our benign little app and punishing us? Should we take this into consideration when prioritizing, e.g., bulk transfer operations?

I would like to think that we're in the clear. We're performing mostly reads - and really just 1 per session to retrieve inventory, we're not currently allowing users to do anything that earns experience, and we're not causing a huge network load.
I think that the more writes we perform, the more of a risk we take. Transfers and renames are likely low risk. Especially in their current form - one at a time, just like the app. That's part of the reason I designed it to work like that. That's also the reason you can toggle those buttons. If you don't want to raise your ban risk, just turn them off.
I think evolves are a bad idea altogether. By implementing that, we start allowing 2 things that we aren't currently allowing:

We're allow users to earn experience. That's toeing the line on botting, in my opinion.
We're allowing you to earn experience faster than you can through the legitimate client. Even if you close down your app and restart to avoid the animation, pressing an evolve button takes way less time. Especially if we batch them, you could theoretically do several in a second. That's gonna get you banned.

Right now, I think we're in a good place. I'm a little cautious and I'll probably wait it out over the weekend and keep an eye on r/pokemongodev to see if it looks like any other IV reader users have been banned. It seems like Niantic is heavily targeting botters and mappers, which do give an unfair advantage and cause way more network load than we do.
After saying all of that, I'm not affiliated with Niantic and I can't say where they're trying to draw the ban line. As always, use at your own risk.

I think other, similar, apps have been receiving c&ds as far as a few weeks ago. In terms of priority, botting/hacking is probably higher, but all use the same APIs. I think you're right that adding support for evolving would draw too much attention, I only suggested that as an ease-of-life thing, especially when my own device can restart the app in 7 seconds to skip the ~22 (or ~30 for a new) second animations. That being said, they will probably do what they've done and target the APIs and send c&ds. Honestly though, they should have known better when implementing the variable stats and made that information available like other games have.
The cleanest approach to this whole thing was justinleewells/pogo-optimizer, as there was virtually no way to know if it was running until SSL pinning required a hacked binary. I myself was working on an android VPN client which would do the same thing on your phone directly instead of being limited to a WiFi proxy. That way as soon as you caught the Pokemon you'd get a little banner/toast notification of its exact stats so you'd know to trash it or not. Bummer.
What's your opinion of automatically renaming the pokemon to display their IVs? I do this manually, but I have been thinking of automating it. My naming scheme has been "FFF (%%%%)", hex representation of the IVs followed by percentage for easy comparison. I also find out their move sets and prepend an "O"ffense or "D"efense or "✔" (for "OD") to show if they have the right moves for attacking or defending (or both).

@collinsmith I'm don't think this is the platform for automating renames. I've had other issues opened to automate renames, but with a different format. I think the current way is the most democratic. Without pre-filling on rename, we're starting everyone on the same level - a blank slate. I renaming with a specific default format is probably best done on your own fork. That way, it only impacts you and not the userbase as a whole.

I haven't seen any bans based solely on IV checkers, like this one, alone over the weekend. Therefore, I'm comfortable starting up development again tomorrow evening. My current priorities are

Adding multi-user support for localStorage
Adding UI / localStorage support for table columns

After that, I'll work on STAB DPS calculation, DPS sort, and other issues in the 1.0.0 milestone.
I also think this is a good forum to discuss what this application is for and what this application is not for. I've done a lot of thinking over the weekend, and here are my thoughts:

This application should not do anything that gives the player experience.  I will be closing all issues related to evolves because of this.
This application should be as safe to use as possible. I think a big part of this will be implementing #61. @DanForbes let me know if you need help with this. This is a high priority for me.

That's really about it. I want to be able to show Pokemon stats, specifically hidden values, and give the ability to show Pokemon rank based on different criteria ( sorts ).  I think anything else may be out of the scope of this application. We're already doing most of that. There are some optimizations left to be made, but I think we're doing very well so far.
I'll leave this issue open for another ~20 hours or so, which would be about 8:30p.m. EST.  for comments. If any of you disagree with anything I've said, let me know and we can talk about it.

I feel like I should also mention that I test / develop with my main Google account. Should the ban hammer come down on stuff like this, I'll be targeted along with other users. In fact, I may be a more visible target since I'm using my account to test while I'm developing. I'll post a notice should I get banned, or if any users report bans solely because of use of this application (:

Vis-a-vis what this application is and is not for, I agree that anything related to gaining XP should be verboten. I'm actually inclined to go one step farther and say that I think this should be a read-only application. All I really want to do is compare my monsters to one another with a higher degree of precision than is exposed by the game's "official" features. With that in mind, I would propose that we remove the rename and transfer features, and remove #48 from consideration (at least in its current form). I know that other people might feel differently than me and I don't think it's terrible to keep the existing write-oriented features of the app (especially since they can be hidden), but that's just my two cents.

I don't mind the rename / transfer / favorite operations being exposed here. The only caveat is that I feel like our current way of turning them off should remain. It gives the ability to have a read only app, with the flexibility to perform some non XP earning operations related to Pokemon management.

Conversation on this seems to be dwindling. Closing for now. If anyone has any more questions, feel free to open another issue.


undefined reference to `engine_load_afalg_int'

/usr/bin/ld: ./libcrypto.so: undefined reference to engine_load_afalg_int' /usr/bin/ld: ./libcrypto.so: undefined reference to engine_load_padlock_int'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:6460: apps/openssl] Error 1
make[1]: Leaving directory '/opt/openssl-1.1.1d'
make: *** [Makefile:174: all] Error 2

May I ask, why is Hui like this? How can I fix it.

How did you configure the build? What is the os/architecture/compiler where you're building it?

I am on the ubunut20.04 system in the gcc version 9.4.0 environment, using the source code to install, after downloading the tar package, unzip it, then ./config, make&&make install @t8m

using the source code to install

Which tarball did you use? What release?

The 1.1.1d is quite old. Could you try the latest version from the 1.1.1 branch?

Thank you very much, I have completed the installation as you suggested


Ci/remove-yarn-yml

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix test flakiness

Tests should not rely on order of tasks being executed across subprojects.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

@bot-gradle test and merge


The difference between the global and local methods is not clear.

Is there a treatise that shows the difference between global and local search methods in edgeSplitter.train_test_split of stellargraph?
edgeSplitter = EdgeSplitter(G) graph_test, samples_test, labels_test = edgeSplitter.train_test_split(p=0.1, method="global", seed=24)

The source code is the best reference for this. The relevant file is https://github.com/stellargraph/stellargraph/blob/e46af15c2dbcaa9ae6328dd1ec62c6f9ef7f5467/stellargraph/data/edge_splitter.py, and searching for local or global reveals:
https://github.com/stellargraph/stellargraph/blob/e46af15c2dbcaa9ae6328dd1ec62c6f9ef7f5467/stellargraph/data/edge_splitter.py#L125-L141
The two methods called there have doc strings:
Global:
https://github.com/stellargraph/stellargraph/blob/e46af15c2dbcaa9ae6328dd1ec62c6f9ef7f5467/stellargraph/data/edge_splitter.py#L914-L923
Local:
https://github.com/stellargraph/stellargraph/blob/e46af15c2dbcaa9ae6328dd1ec62c6f9ef7f5467/stellargraph/data/edge_splitter.py#L804-L819
Example: consider a really simple line graph with 8 nodes a -- b -- c -- d -- e -- f -- g -- h. Suppose the sampler chooses a as the starting node for a negative edge:

global: any other node (c, d, ... h) can be chosen for the second node to make the edge, meaning it can generate a negative edge like a -- f
local: only nodes close to the start a can be chosen. With the default probabilities, it's up to 3 hops away, so the edge like a -- f will never be generated, because f is too far away.

Does that make things a bit clearer?

Yes, it's clear.
There is a possibility that uniform sampling can be devised a little more.
It was very helpful for me to explain it carefully.
I would even like to emulate the speed of this response.
If you find you on twitter, I'll follow you.
I want to close it with this.


iPad mini 2 does not Jailbreak

I press go, the storage is full notification shows up, then it says already jailbroken. No reboot. No respring. No cydia.

logs? yalu beta version?

does the app say already jailbroken if you open it again?

you are actually jailbroken.
ssh into your device and run uicache to make Cydia show up, or refer to #209

Luca you release untether jailbreak ios 10.2?


Documentation/Support for multi-select option sets

When executing a fetchXml that contains a multi select option set field, the value of the field is an array of optionset values. (JSON array of int values.)
A copy data action from Dynamics 365 to blob storage (as a json file), sets this value to null in the exported json file. Therefor it seems to me that multi select option set is also not a supported AttributeType.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 304d4c46-c0ac-05c9-15eb-d8b677ec5e90
Version Independent ID: 36a79d36-2b72-2722-68e5-e167f9a2cd41
Content: Copy data from and to Dynamics CRM or Dynamics 365 (Common Data Service) by using Azure Data Factory
Content Source: articles/data-factory/connector-dynamics-crm-office-365.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@vadakoen Thanks for the feedback. We are investigating into the issue and will update you shortly.

@vadakoen I am assigning the issue to the content owner to have a look.
@linda33wj Can you please take a look at it?

@vadakoen Thanks for the feedback. You are right that AttributeType.MultiSelectPicklist type is not supported now. I've added to the Data Type section in this article to clarify. We will track this ask and further traige for the future.
#please-close


Display of Raw source in a text window has issues when data is XML on one line

The raw window displays nothing when the RAW XML is on one line

In v7 this should be addressed by #1678

This is down to the v6 data viewer not being able to deal at the character level so it can't really cope with single line data.
This will be addressed in v7.  Too big a change for v6.


semicolon removed

example code does not work with it there (syntax error)

@usufruct yes thats totally right :)
Thanks for your contribution

Thank you for the migration code!


$update deprecated

Btw, first time issue-filer, long time user--thanks: glad to be here. Sorry if I'm tripping over any protocols or if I'm missing something.
Anyway, looks like when the $firebase service was removed in 6e38dad8f976ab42496b9818cae1ffd1a257db71 the $update method was removed along with it (not migrated to $firebaseObject).  I understand $firebaseObject is not a drop-in replacement for $firebase, it was still frustrating when I could find any mention of that feature's deprecration (unless I'm totally missing something).
Can $update() be added $firebaseObject, analogulously to $firebaseArray.$add()? Seems like a pretty simple use case, but that method would be hugely useful for creating a new object, and receiving it's firebase reference in a promise so I can continue to edit it, or call $bindto, instead of having to use the native js library.

Hey there, thanks for using AngularFire and filing this issue!
$update() was indeed removed when $firebase was removed. The migration guide has some examples of how to convert from using $firebase to using the core Firebase library, which is the recommended solution here. There is no example for $update() explicitly, but the concept is the same.
If you want to update an instance of $firebaseObject, you don't even need to call $firebase.$update() or use the core Firebase library's update() method. All you need to do is something like this:
var obj = $firebaseObject(ref);
obj.$loaded().then(function() {
  obj.foo = "bar";
  obj.baz = true;
  return obj.$save();
}).then(function() {
  console.log("Object saved!");
}).catch(function(error) {
  console.log("Error:", error);
});

Since the synced object is really just a regular JavaScript object, treat it as such and update it directly. Then, when you want those changes synced to Firebase, just call $save().

Thanks for the quick response Jacob, but the reason I'm trying to use something like $update() (or $set() for my use case, even ) is to avoid calling $loaded. My use case is creating a user with a unique id I specify (fbUrl.com/user/:userid). With the method proscribed above the entire object at /user is then synced/downloaded, if I'm understanding that correctly--a hugely unnecessary use of bandwidth for saving a user.

In which case you should avoid AngularFire entirely--a great bindings library for handling complexities of syncing objects and arrays into Angular, but entirely unnecessary for a simple write op. As the migration guide already linked suggests, just work directly on the Firebase reference:
ref.update( newUserData );

However, as you've stated that you are creating a new user with a unique ID, update() is entirely the wrong approach. Instead, to create a new user, you should be utilizing ref.set()
Cheers,
Kato

Also, just to add on to what Kato mentioned, if your concern is not downloading the data, you don't want to use $firebaseObject at all. Even if you don't call $loaded(), instantiating a synced object with $firebaseObject will download the data. The $loaded() method is just convenience method which will fire once the data is downloaded. If you don't use it, the same things still happen in the background.
So that is why it is better in your case to follow Kato's advice and not use $firebaseObject at all but just use the regular Firebase client. Hope that helps!

Gotcha--understand much better now why it would actually be a bad idea to
implement $update  (or $set). I am in fact implementing plain JS client
to just do the write op--makes more sense for my use case now. Thanks for
the reply!
On Sun, Mar 22, 2015 at 8:27 PM, Jacob Wenger<EMAIL_ADDRESS>wrote:

Also, just to add on to what Kato mentioned, if your concern is not
downloading the data, you don't want to use $firebaseObject at all. Even
if you don't call $loaded(), instantiating a synced object with
$firebaseObject will download the data. The $loaded() method is just
convenience method which will fire once the data is downloaded. If you
don't use it, the same things still happen in the background.
So that is why it is better in your case to follow Kato's advice and not
use $firebaseObject at all but just use the regular Firebase client. Hope
that helps!
—
Reply to this email directly or view it on GitHub
https://github.com/firebase/angularfire/issues/593#issuecomment-84744600
.


Add pacing column to layout for current month only.

Github Issue (if applicable): #651
Trello Link (if applicable):
Forum Link (if applicable):
Explanation of Bugfix/Feature/Enhancement:
The pacing column is only relevant to the current month. The old code was adding the pacing column to the layout but hiding it. That had a ripple effect on other toolkit features.
Recommended Release Notes:
Pacing column will be displayed for current month only. This means that column widths will vary when moving backward and forward between the current month and other months.

Thanks!


[WIP] Migrate DynamicGroup model and functionality from extras to core

Closes: #2826
What's Changed

Move the DynamicGroup model and associated classes (filters, forms, views, API, etc.) from the extras app to the core app.
Create migrations (based on example from https://davit.tech/django-move-model) to move the existing database tables and content-types between apps instead of deleting the existing tables and creating new empty tables.

Migrating the content-type isn't covered in the linked blog post but it's necessary to ensure that GFKs such as in ObjectChange don't get broken.
I have manually tested migration back-and-forth between this branch and next with a DynamicGroup with a change history; I haven't tested the migrations against an empty table but CI should prove that out one way or the other.

To get URL patterns to work correctly, I had to split nautobot.core.urls into nautobot.core.urls (app-level URLs, such as now dynamic-groups) and nautobot.core.urls_root (the base urlconf for all of Nautobot), and similarly split nautobot.core.api.urls into nautobot.core.api.urls and nautobot.core.api.urls_root.
To avoid circular imports between extras and core after the move, I had to:

convert nautobot.core.api.views and nautobot.core.views into submodules
move the setup of the dynamic-group signal handlers into the AppConfig's ready() method instead of connecting them at import time

One lingering issue I haven't been able to solve for is adding any nav menu items in nautobot.core.navigation. Some issue with application loading and initialization order - the URL resolution for the nav menu items causes nautobot.core.admin to be imported and evaluated early, apparently too early? and so app startup fails.

TODO

[x] Explanation of Change(s)
n/a Added change log fragment(s) (for more information see the documentation)
n/a Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[x] Example Plugin Updates (when adding/changing features)
[x] Outline Remaining Work, Constraints from Design

OK, that's a bizarre error from unit test initialization. Any ideas? Will investigate on Monday.

Seems to be an issue with the test-only model defined in nautobot/core/tests/test_models.py not getting a table created in the database. Not sure why my changes are influencing anything here; but based on some googling it perhaps shouldn't be working in the first place as written? Could use some extra eyes here.

One extra concern not directly addressed by this PR is how this change would be handled by apps (plugins) that have foreign-keys to any of the Extras models, such as to in this case a DynamicGroup. Probably the data migration needs to inspect the migrated model for any and all reverse-relations that it contains, and handle all of those identified foreign-keys at once.

😢
At the moment we're going to shelve moving extras for the time being (maybe 3.0) due to the significant impact to migration for 2.0. Let's let the Plugin API be more widely adopted and clean up some other things first before we move extras.


Uncaught ReferenceError: $el is not defined

Hey @chrismccord
Can't seem to use $el in afterInsert hook. It's throwing this error
afterInsert: ->
    $el.fadeIn 'slow'
 Uncaught ReferenceError: $el is not defined

Thanks

you need to access @$el, with the @.

thanks @ajb (adam). Trying out coffee-script for the first time.


C3 add missing pages e2es

This PR:

adds C3 e2e pages tests for docusaurus and gatsby
fixes broken cleanup for quarantined C3 e2e pages tests
fixes broken astro e2e test

Note
Also the Angular e2e test is missing, I was planning to add it to this PR but the Angular creation via pnpm
is currently broken (#4023) so if it's ok I'll just add the docusaurus and gatsby tests here and add the Angular one
after the pnpm issue's been fixed

warning
The issue with astro was that we were using the blog template, that (unrelated to e2es, actually for users) doesn't work so I switched it to the basics template, we do however need to investigate why the blog template doesn't work (I assume it used to)


Update simpleclient to 0.10.0

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.prometheus", artifactId = "simpleclient" } ]

labels: library-update, semver-minor

Superseded by #420.


Nwrl Nx Support

First off, thank you so much for picking up this project. I tested the latest branch today and it fixes many of the issues I had with the previous versions of this project. Your work is definitely awesome.
Secondly I would like to make a feature request, it seems like you have a road map planned and you are making commits very often which is awesome however I would like to request that support be added for Nwrl Nx a mono repo solution.
The current extension does load up in a Nwrl Project but runs into problems because it is running directly from the jest binary. I purpose detecting is an angular project (with angular.json in the root) and if it is default to running jest with ng test instead of the jest binary. This will run jest through @angular-builders/jest and use the settings in angular.json.
Adding this support would be super awesome and make this extension super usable in my daily workflow. Nx defaults to using jest so having support for this would be a match made in heaven imho.

Hey @wSedlacek. Thanks for the compliment. It did seem the original project was dead (I did try to raise a PR there).
Interestingly I'm working on a Nx.dev project at work currently although it is React not angular.  It is part of the reason I created #9.  Although your use case does appear to supplement it.
if you're interested in raising a PR that'd be great. I'm keen to involve others in this too.

I would love to help out if I find the time! I will definitely make pull request towards this if I find the opportunity.

WOW! You certainly have made quite a bit of progress.
I was attempting to review the latest commit on the monorepo branch and it looks really good!
One bug I did encounter when testing it was this.
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined

Coming from here:
https://github.com/kavod-io/vscode-jest-test-adapter/blob/adfca75bdc4562be0260747300a58895ee03f33e/src/repo/NxdevAngular.ts#L54
The problem is that setupFile is an optional param so on the libraries I have that do not use it this error gets thrown.
I also was noticing that it was not passing the options like passWithNoTests into the extension.
The full schema for the Jest Builder is here for reference:
https://github.com/nrwl/nx/blob/master/packages/jest/src/builders/jest/schema.json

I started to play around with Web Storm and I was able to get my NX Nwrl repo to work with their Jest testing run directly through the CLI by:

Adding the following config settings to every Angular app and library's jest.config.js

  globals: {
    'ts-jest': {
      stringifyContentPathRegex: '\\.html$',
      tsConfig: '<rootDir>/tsconfig.spec.json',
      astTransformers: [
        'jest-preset-angular/build/InlineFilesTransformer',
        'jest-preset-angular/build/StripStylesTransformer',
      ],
    },
  },
  setupFilesAfterEnv: ['<rootDir>/src/test-setup.ts'],

Adding the following line to the root jest.config.js

  projects: ['<rootDir>/apps/*/jest.config.js', '<rootDir>/libs/**/jest.config.js'],

WOW! You certainly have made quite a bit of progress.

Cheers.  I was on holiday and working on this kind of thing is what I like to do in the evenings.

The problem is that setupFile is an optional param so on the libraries I have that do not use it this error gets thrown.

Nice detective work!  I came to the same conclusion the other day when I tested the extension with our Nx React repo, which doesn't have any setup files.  I'm in two minds as to whether to even bother tracking it.  I guess I'll check what the Nx test code is doing and decide.

I also was noticing that it was not passing the options like passWithNoTests into the extension.

Hmmm, I did see that at one point as well, I'll have to have a look at that.

I started to play around with Web Storm and I was able to get my NX Nwrl repo to work with their Jest testing run directly through the CLI by:
...

Perfect, that's exactly what you need to do and I appreciate the testing on your behalf.  TBH I was going to reply and see if you would do that favour.
Obviously, I wouldn't expect anyone to modify their configuration files like that in the long term (I don't know if it will break the Nx dev functionality).  At the moment, for running the tests I'm using the jest-editor-support package, which runs jest on the command line and parses the output.  I think in the long term, this isn't the best option.  In the case of Nx.dev, it would mean either modifying the config files on disk and then reverting them (yuck), or creating temp config files somewhere with the required modifications (less yuck).  But I'm considering whether I take a different approach and actually add Jest to my extension and use the jest.runCLI command, which is what the Nx Angular test script does.  This would reduce version conflicts in Jest (i.e. if jest config options change over time) and I don't think there should be any changes in Jest itself that should change whether user's unit tests pass or not.  It would mean that I can pass a Jest config object instead of the path to a config file, which would allow me to modify the config as required by packages like Nx Angular.
But my plan is to tidy up a couple of issues, like you've discovered and try getting the test debugging working correctly and then I'll probably publish to the extension store.  It'll be a prerelease, since I don't have unit tests in place - but it'll mean that I can start getting some user feedback and issues from a wider audience.

Is there any update on how to get this working with nx angular? Thanks for the awesome work!

@SSmale My message from 28 days ago details the config changes I used to get this working.
Basically rather then treating each projects jest.config.js as a super set for the workspace's root you instead treat them as individuals that are imported to the root as projects. This configuration also works for running NX projects with Wallaby
Here is my WIP project where I have this implemented and working
https://gitlab.com/wsedlacek/ccg-x/-/tree/cards-api
It may be nice to edit the schematics to generate projects in this way to avoid having to set it up like this on every project/library generation.

Thanks for the quick reply @wsedlacek, I’ll give that a go but I was referencing the other work being done on not having to edit configs.

I discovered that the jest-editor-support library can accept a command other than a path to the Jest executable.  I've just pushed support for Create React App which was in the same boat as this.  So I may be able to implement this support without major changes.  Hopefully, you'll see it soon.

Just an FYI - I've found that Nx will need a PR to allow for the retrieval of settings using the nx test command.  Using plain Jest it would be something like:
npx jest --showConfig

But Nx doesn't pass through the showConfig flag.  They also may not accept the PR - but it seems harmless to me.

Good news, the changes were accepted into Nx.  Just need to wait for the next release.  Not sure what the release cancer is, but if you see it before I do, feel free to comment.

I added this support behind a dev toggle (UseNxCli) so you can test this feature the old way as well as the new way.  But you'll still have to wait for the next Nx Dev release >9.2.4.

Awesome work @rossknudsen! Can't wait to try it out!


FIFF tag fixes.

I am now attempting to fix the overlaps that we have with the FIFF tags. I just want some comments before I dive any deeper. Is this the right way to change the tags without breaking backwards functionality? This is the fix for FIFF.FIFFB_EPOCHS. Ping @agramfort  @Eric89GXL

 FIFF.FIFFB_EPOCHS  = FIFFB_PHANTOM_SUBSYSTEM = 122

Change FIFF.FIFFB_EPOCHS  = 373 (e.g.)
If you find block 122 inside FIFFB_MEAS_INFO, it is likely to be FIFFB_PHANTOM_SUBSYSTEM. Otherwise it is probably FIFF.FIFFB_EPOCHS.

@jaeilepp are you going to take care of making the mne-constants repo from the Elekta MNE constant files? That might be a better first step, because then we can verify that all the names and numbers are good before moving forward.
I was planning on doing it, but if you have time, it makes sense to do it as part of this changeset.

Yeah, I can look into it. What exactly should the repo contain?

From the emails with Jukka, it looks like the first step is to put the _MNE.txt files up on GitHub. We can start by putting only the MNE files up there, and if Elekta eventually wants to make use of the repo, we can get them access. I propose adding them to a new mne-fiff-constants repo. We can always change the name later if @agramfort doesn't like it :)
Then make the following changes in this PR and the defs, as Jukka suggests:

 FIFF.FIFFB_EPOCHS  = FIFFB_PHANTOM_SUBSYSTEM = 122

Change FIFF.FIFFB_EPOCHS  = 373 (e.g.)
If you find block 122 inside FIFFB_MEAS_INFO, it is likely to be FIFFB_PHANTOM_SUBSYSTEM. Otherwise it is probably FIFF.FIFFB_EPOCHS.

 FIFF.FIFFB_ICA = FIFFB_STATUS_SUBSYSTEM  = 123

Change FIFF.FIFFB_ICA  = 374 (e.g.)
If you find block 123 inside FIFFB_MEAS_INFO, it is likely to be FIFFB_STATUS_SUBSYSTEM. Otherwise it is probably FIFF.FIFFB_ICA.

 FIFF.FIFF_CUSTOM_REF = FIFF_HPI_COI_FREQ = 236

Change FIFF. FIFF_CUSTOM_REF  = 3561 (e.g.)
If you find tag 236 is inside FIFFB_HPI_MEAS, it is likely to be FIFF_HPI_COI_FREQ.

 FIFF.FIFFV_SEEG_CH = FIFF_QUAT_2   = 702

We could change FIFF.FIFFV_SEEG_CH = 802 and embed in our definitions.
You can separate CH 702 according to the context, channel name and unit.

 FIFF.FIFF_MNE_BASELINE_MIN  = FIFF_DATA_BUFFER2 = 304

Change FIFF.FIFF_MNE_BASELINE_MIN  = 3565 (e.g.)
Again, separate tag 304 by context.

 FIFF.FIFF_MNE_BASELINE_MAX  = FIFF_TIME_STAMP = 305

Change FIFF.FIFF_MNE_BASELINE_MAX  = 3566 (e.g.)
Again, separate tag 305 by context.
Make sense?

So you mean making a revision to the MNE.txt files? It says that DO NOT PUBLISH WITHOUT PERMISSION. Do we have permission?

Yes, on 20 Oct 2015 we received email permission from Elekta by @jnenonen (Jukka) to put the MNE range constants up on GitHub. It's our responsibility to maintain the bookkeeping and documentation, so we might as well start by removing that line since we're making it (more) public now :)

Ok. Just wanted to make sure...

It appears I don't have a permission to create a repo under mne-tools...

you have admin rights now

@jaeilepp do you think it's reasonable to get this one in for 0.11 (in the next couple of weeks)? We should really try to have this if possible so that we can correct our types right ASAP.

Yeah, this shouldn't take too long. I was just waiting for feedback from someone. I guess the definitions are okay as they are...

What did you need feedback on? The numbers chosen? I think Jukka suggested some that seemed fine.

BTW are these old constants used in MNE-c? I'm not too familiar with the c-code.

The old/incorrect ones you mean? No. Those we created for mne-python objects that MNE-C doesn't support. The MNE-MATLAB tools will probably need to be updated at some point.

If the tests pass this is ready for my part.

LGTM! @agramfort you want to take a look or good enough already from your end?

did you actually check if you can read old epo and ica files?
maybe someone else can also test?

I didn't, but I can once @jaeilepp lets me know it works for him :)

did you actually check if you can read old epo and ica files?

Works for me.

I am trying to read an old -epo.fif file and I get:
RuntimeError: bad channel(s) [u'MEG 2443', u'EEG 053', u'MEG 2443', u'EEG 053'] marked do not exist in info

this is unrelated but it should be fixed
file is at:
http://perso.telecom-paristech.fr/~gramfort/sample-epo.fif

The error @agramfort gets is related to the bug with reading meas_info. It was fixed for ICA objects earlier by @Eric89GXL . I suppose this happens to evoked objects as well...

Here it is https://github.com/mne-tools/mne-python/pull/2559

yes. It should be fixed too.

Now it should work.

I wonder if it happens to old raw objects too...

Yeah it probably could

So it should be safe to add clean_bads to raw class too? It doesn't mess up anything?

It should be safe AFAIK

I would add it to Raw too.
let me know when travis is happy afterwards.

merged by rebase.
thanks @jaeilepp


Paste and match style

"Paste and match style" is a standard feature in most Mac apps. When I copy text to be pasted into an email (usually from a website) I expect to be able to paste it into an email without carrying the formatting along with it. I don't need bold 24-pt. red text pasted into the body of an email that's composed with 12-pt. black text, so I use Paste and Match Style (command-shift-V in Chrome) to dump the text into the message cleanly.
Manageyum lacks this feature, so I'm forever pasting first into just about any other program to strip the formatting, copying that cleaned up text to the clipboard, then pasting into Manageyum. Anything you can do about this?

As a workaround you can use CMD+\ in Gmail to remove all formatting. Slightly less painful:

paste formatted text into regular Gmail compose window
select the text you just pasted
hit CMD+\ to remove all formatting and reset to regular Gmail email style

That's basically what I'm doing now, though it's funny that your suggestion includes pasting into the regular Gmail compose window. I'm using Manageyum specifically to avoid having a few Gmail tabs open all the time in Chrome. ;)

Indeed. I'm using Manageyum to keep track of 6-7 different Gmail accounts so I don't have to have them all open in Chrome. Very useful for that. Even more useful when Profiles become available.

It's handy for the tabs I normally have to keep open for the several SaaS's I use daily. Looking forward to seeing how Manageyum evolves.


About adding image upload function

What does this PR do?
I added an image upload function.
Ther is no function to submit images and FormData in the buttons.
New file
-/components/imageInput.tsx
-/components/sendImageForm.tsx
Changed file
-/components/uploadFormHook.tsx

[x] Documentation or TypeScript types (it's okay to leave the rest blank in this case)
[x] Code changes

How did you verify your code works?
By localhost server and github workflows.

What does this PR do?
I added an image upload function. Ther is no function to submit images and FormData in the bottons.

Do you mean buttons instead of bottons?
Or bottom?

Could you resolve the conflicts to merge?

Could you resolve the conflicts to merge?

Yes, I did it.


Navigate to another dashboard from image click

Resolves #19

Grafana's image that images are clickable only in the middle: https://github.com/grafana/grafana/issues/41445


[Automation] Generate Fluent Lite from Swagger devtestlabs#package-2018-09

[Automation] Generate Fluent Lite from Swagger devtestlabs#package-2018-09

/azp run java - devtestlabs - mgmt - tests

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure.resourcemanager:azure-resourcemanager-devtestlabs


TimeSlider

The TimeSlider is a utility Control that emits TimeExtent values typically for use with a view control to enhance the viewing of geographic features that have attributes based upon Date/Time information.

[x] UWP
[x] WPF
[x] Xamarin.Android
[x] Xamarin.iOS
[x] Xamarin.Forms

Complete and verified


Add OnReady attribute source generator

Alternative implementation for proposal: Proposal#2425
Reason for this alternative implementation
In this implementation, only the nuget packages are updated. The bindings generator was not edited to make this work.
Usage
It contains 2 implementations.
One for methods:
[OnReady("Player/Sprite")]
partial Sprite2D PlayerSprite();

And one for Properties(Only compatible with dotnet 9):
[OnReady("Player/Sprite")]
partial Sprite2D PlayerSprite { get; }

Generated code
They both use a source generator to generate a partial class containing the following implementation.
For methods:
Sprite2D? _playerSprite; //Backing field
Sprite2D PlayerSpriteReady => _playerSprite ??= PlayerSprite(); // Property
Sprite2D PlayerSprite() // Method implementation
{
    return GetNode<Sprite2D>("Player/Sprite");
}

For properties:
  Sprite2D? _playerSprite; //Backing field
  partial Sprite2D PlayerSprite => _sprite ??= GetNode<Sprite2D>("Player/Sprite"); // Property implementation

When you use a nullable type, it generates the following property instead:
  partial Sprite2D PlayerSprite? => _sprite ??= GetNodeOrNull<Sprite2D>("Player/Sprite");

This uses GetNodeOrNull so it doesnt throw an exception and you can handle nulls yourself.
Compatibility
The property version uses partial properties which is only supported with dotnet9.
The generator wont generate this when the property is not partial, so it wont generate incompatible code when having a godot project with dotnet version lower than dotnet9.
Analyzers
There are 3 new analyzer coming with this source generator:

GD0501: On ready member type must derive from Godot.Node
GD0502: On ready member must be partial and must not be implemented
GD0503: On ready member cannot be static

I'll have to add these to the documentation as well.
Alternative PR
There is a similar PR for this proposal: PR#92886
There was a comment regarding the name of the attribute being too similar to a concept in gdscript(@onready) without it being exactly the same. I personally don't understand this point as it is supposed to be the same functionality as you get in GDscript(Getting a node from the tree without explicitly calling getnode in the _ready method).
I also believe this implementation is more elegant and concise. You can use the onready members in the _onready without any problems. There are no extra methods to be called by the engine. In essence this generator rather generates pure boilerplate code instead of modifying how flow of the ready methods get called.
As this doesnt add any methods, stacktraces remain the same and easy to debug. The property is the same as if the user had a field filled with getnode in the ready method.
I remember when i started in godot and immediatly got confused as to why there was no OnReady annotation like in GDscript. Having it the same name in C# makes this for newcomers alot more intuitive to use and follow GDscript tutorials online.
Ofcourse this name can easily be changed if deemed too confusing.
Extra
I've added 2 tests.
Documentation still needs to be made.

Bugsquad edit, closes: https://github.com/godotengine/godot-proposals/issues/2425

Thanks for contributing to the .NET module. The .NET team has discussed this PR and have found that it doesn't address the concerns raised in the original PR (https://github.com/godotengine/godot/pull/92886).
Mainly, the implementation proposed doesn't match the behavior of GDScript's @onready annotation, and we believe implementing such a feature idiomatically in C# is not possible. We also think the current implementation can be easily provided as a third-party NuGet package.
We have decided to close this and the original PR, please read the closing statement in the original PR for more details: https://github.com/godotengine/godot/pull/92886#issuecomment-2480378278
Again, we apologize for the inconvenience. Thanks for the contribution nonetheless.


Extends another config with plugins do not add attributes

Describe the bug
Extends a plugin does not work.
To Reproduce
The entry point config file:
extends:
  - recommended
  - ./serverUrls.yml
apis:
  auth@v1:
    root: ./doc/openapi/auth/openapi.yml

The child config file serverUrls.yml in plugins/plugin.js:
apis:
  auth@v1:
    decorators:
      plugin/replace-servers-url:
        serverUrl: https://
plugins:
  - "./plugins/plugin.js"

The plugin.js in plugins:
const ReplaceServersURL = require('./decorators/replace-servers-url');
const id = 'plugin';

/** @type {import('@redocly/cli').DecoratorsConfig} */
const decorators = {
  oas3: {
    'replace-servers-url': ReplaceServersURL,
  },
};

module.exports = {
  id,
  decorators,
};

Expected behavior
The main config should have the same decorators as defined in serverUrls.yml.
Redocly Version(s)
1.0.0-beta.125
Node.js Version(s)
v16.15.1

Hi @lbrun25,
Redocly CLI doesn't extend anything from the nested apis section.
However, you can solve your case either by explicitly specifying the decorator in the auth@v1 section in the entry file or by moving decorators from apis to the root level in serverUrls.yml:
plugins:
  - "./plugins/plugin.js"
decorators:
      plugin/replace-servers-url:
        serverUrl: https://

I'm closing this as I'm not sure there's anything to fix. The extends section relates to the rulesets, so APIs, decorators and other definitions aren't picked up in that section - and this is as expected. @tatomyr's explanation of how to achieve the desired outcome I think covers everything (thanks!). Please do re-open if you need anything more on this.


Update README.md

enhancers

please have a look at the CONTRIBUTING.MD before proposing a new company. You cannot modify the README file directly.

replaced with another pr


MTIColorLookupFilter error result

I test the MTIColorLookupFilter with the default lookup image lookup.png on Iphone 6 iOS 9.3.1 but the result image was strange as below image. When I tried to test on Iphone 6 iOS 12.0 the result was correct as I expected. Please help me to fix it!

The “MTKTextureLoader” load images upside down on iOS9. You can use the custom texture loader in MetalPetal to fix this. See
https://github.com/MetalPetal/MetalPetal/blob/master/Frameworks/MetalPetal/MTITextureLoaderForiOS9.h


[EDA] Prevent deletion of a Term Record when there is a Related Child Term Record

Critical Changes
Changes
We've updated the functionality to prevent the deletion of Term records that have related Term records. This change is for internal-use only and is disabled at this time. You won't see any difference in functionality.
Note: We strongly recommend that EDA Admins don't manage Hierarchy Custom Settings directly and, instead, use the EDA Settings UI.
Issues Closed
Closes #1124
New Metadata
Deleted Metadata
Testing Notes
Scenario 1: “Prevent Term Deletion” checkbox is enabled and Term record have related Term Grade, Course Connection, or Course Offering Schedule or Term records.

Check “Prevent Term Deletion” checkbox in Hierarchy Settings.
Create 2 Term records
Associate 1 Term record to another.
Delete the parent Term record.
You should receive a pop up error that you cannot delete this Term. See https://salesforce.quip.com/fXSbAE7hHWV8#LPKACAsjDGR for the error message.

Scenario 2: “Prevent Term Deletion” checkbox is disabled and Term record have related Term Grade, Course Connection, or Course Offering Schedule or Term records.

UnCheck “Prevent Term Deletion” checkbox in Hierarchy Settings.
Create 2 Term records
Associate 1 Term record to another.
Delete the parent Term record.
The Parent Term should be deleted

Scenario 3: “Prevent Term Deletion” checkbox is disabled and Term record have related Term Grade, Course Connection, or Course Offering Schedule or Term records.

Uncheck “Prevent Term Deletion” checkbox in Hierarchy Settings.
Create 2 Term record
Associate 1 Term record to another.
Delete the Term record
You should be able to delete the Parent Term record

Scenario 4: “Prevent Term Deletion” checkbox is disabled and Term record does not have related Term Grade, Course Connection, or Course Offering Schedule or Term records.
UnCheck “Prevent Term Deletion” checkbox in Hierarchy Settings.

Create a Term record
Delete the Term record
You should be able to delete the Parent Term record

Looks like there's at least one place in the unit test where we are doing an ORDER BY Name -- Name is a potentially encryptable field. If a customer is using shield and chosen to encrypt the Name (yes that's an edge case, but) then it will fail for them.

@lifewithryan Sorry I should've know! I slightly modified a couple of methods to go around it. Can you please give it another shot? Thx.

Passes QA - Waiting to merge until we release 1.94
Ticket will be "In Waiting"

Did a quick smoke test and everything looked go: Merging and Closing


Suggestion: add an 'event' argument to onAny handlers

There's a problem with using this.event to get the event. If you're in the habit of binding a this onto handlers, you'll be unable to do this for onAny handlers. For example:
emitter.onAny(function() {
    // this.event is almost definitely undefined, and definitely isn't the triggering event
}.bind(this))

I suggest that instead, the onAny API be changed to this:
emitter.onAny(function(event, argument1/*, ...*/) {
   console.log("Got a "+event+" event!")
}.bind(this))

emitter.emit("whatever", 4)

Open to a PR that makes the first arg the event.
On Friday, February 20, 2015, fresheneesz<EMAIL_ADDRESS>wrote:

There's a problem with using this.event to get the event. If you're in
the habit of binding a this onto handlers, you'll be unable to do this for
onAny handlers. For example:
emitter.onAny(function() {
// this.event is almost definitely undefined, and definitely isn't the triggering event
}.bind(this))
—
Reply to this email directly or view it on GitHub
https://github.com/asyncly/EventEmitter2/issues/139.

--
Sent from Gmail Mobile

@hij1nx Great, that's much clearer! The only question I have is what happens when those methods are called on a range that already has some selection associated with it? Does it completely change the selection, or does it just "grow" the selection?

I don't see any obvious reason why this.event can't be set before invoking _all handlers.  What am I missing?

Well antipattern or not, I've seen lots of code use this pattern, and have used it myself (tho I usually create a that variable i assign to this i can then use in the callback). The issue is that this is the only thing that causes EventEmitter2 to not be a fully compatible drop-in replacement for node's EventEmitter, which is a good feature to have for a library that already so closely follows the same API. And emitter.event should never contain the event - this would break things in cases where you emit another event from the emitter inside the event handler, and then lower in the event handler access emitter.event.

@cxreg, I'm not seeing the re-binding in the PR code. What file/line is it in?

@RangerMauve I think he meant the rebinding in my example in the original post up at the top. The bind(this).

+1

It seems this is implemented. I see this.event correctly set in my EventEmitter2.onAny handler. Issue to be closed ?

@Yvem this.event is being set, but the PR adds the event as the first argument of the callback rather than a property of this. The reason being is that functions that got bound to a different this context cannot access the event name in the current implementation.

+1

Fixed in #141

:+1:


feat: Recursive Directory Listing

Tests are passing:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Chore/remove redundant routes and amend school retrieval

retrieve schools by id and not urn

 Default school retrieval should be by id and not by urn


Facilitate reducing precision of data before saving

We can reduce the size of our datasets by changing how numbers are represented, such as reducing from double to single precision.

Talk to Valerio, he references SunSpec  and MODBUS.
Also talk to Yuliya about the 3/7 presentation


fix(uiSelect): add class to dropdown instead of simple opacity change…

…  to remove flicker
Previous behaviour and new one with punks are in issue #1583.

What tests do you need specifically? It does not change interaction and just replaces opacity with class change?

I can do one test that it will fix by replication issue https://github.com/angular-ui/ui-select/issues/1583 itself but I believe to do it for such a small specific issue is a bit overkill.

I agree on the fact that it looks like a bit of overkill. But as this libary has many issue it is our best check for problems in the future. Could you make it and commit it?

To this same branch, no problem. I need to add comit with test(uiSelect): PR #1936 or copy same messege but starting with test?

i think test(uiSelect): PR #1936 will do. It can be in the same PR (just to be clear 😄 )

Any updates on this issue?
Thanks

Oops, forgot completely, will take some time tomorrow evening to clean it up.

We are seeing the same issue as in #1583 however when applying the changes in this PR, it did not help. Looking forward to a proper fix.

Good solution, but doesn't seem to work when $select.$animate is null.


Typescript version in samples

Since Typescript is Firebase's suggested language for Functions it would be super helpful to have a Typescript version along side the vanilla JS samples to get the community jumpstarted in that direction.

Where is this documented? I'm curious. Thanks.

Write Production Quality Cloud Functions (Firebase Dev Summit 2017)

Yesterday we integrated support for TypeScript in firebase-tools. Download the latest copy of firebase-tools with:
npm install -g firebase-tools

and you can initialize new projects with our recommended TSConfig and TSLint options. firebase-tools will also ensure that your code is compiled and free of linter errors (warnings are OK) before deploying. You can see more about TypeScript with Cloud Functions in our docs


First draft: Tell Grace's story about a journey to a new library.

Please note that I'm neither a technical writer nor am I a native speaker. This is just a quick summary of the experiences I had while doing some stuff with kube-rs. It would be awesome to get some help to get this into a state where it actually could help you pals to improve the experience when using async code.
Thanks for this project btw :)

Reading the article once more, I'm not sure if Grace is the right stereotype for this issue. I just see myself as a Grace. :thinking:

@Gottox hope you don't mind -- I'm trying to move some PRs along, so i went ahead and added some FAQs. I'm going to merge but feel free to open a PR with edits if you have ideas for what to change or more to add!

Feel free! I was rather unsure about the quality of my text. Hope I can help nontheless :+1:


Build should support es6 target in tsconfig

[x ] bug report -> please search issues before submitting
[x ] feature request

As suggested by the article "You might not need to transpile your JavaScript" if one is targeting modern browsers than es6 should work as a target.
Versions.
Angular 4.3.6
Angular cli 1.3.2
Change target in tsconfig.json to "es6"
ng build --bh /ui/ --prod --aot

_Date: 2017-09-02T18:56:38.448Z
Hash: 8032803bfa9cd5eeccc0
Time: 31830ms
chunk {0} polyfills.427414a5bc7cff210ba6.bundle.js (polyfills) 98.1 kB {4} [initial] [rendered]
chunk {1} main.65fe0ebc36062fa8f7ee.bundle.js (main) 945 kB {3} [initial] [rendered]
chunk {2} styles.d41d8cd98f00b204e980.bundle.css (styles) 0 bytes {4} [initial] [rendered]
chunk {3} vendor.cce22225937a659c544a.bundle.js (vendor) 959 kB [initial] [rendered]
chunk {4} inline.1835379b8caad20d2658.bundle.js (inline) 1.45 kB [entry] [rendered]

ERROR in main.65fe0ebc36062fa8f7ee.bundle.js from UglifyJs
Unexpected token: punc ()) [main.65fe0ebc36062fa8f7ee.bundle.js:94,12]_

Desired functionality.
ES 6 target should build (and work in a modern browser)

Support for ES6 is being tracked in https://github.com/angular/angular-cli/issues/2907. Please subscribe to that issue for further updates.

Closing as answered by @devoto13, thanks 👍


Add overflow-wrap: break-word to body tag

https://developer.mozilla.org/en-US/docs/Web/CSS/overflow-wrap

This looks like a duplicate of #306
What problem are you solving?

Looks like almost the same, but I think we should apply overflow-wrap: break-word to the body since there could be a too long word on any part of a page, not only in a post title(https://github.com/jekyll/minima/pull/306).
Example:
Too long word in the body of one of my article caused extra horizontal scroll before I fixed it. So I decided to try to fix that directly for minima, not only for my website.

Could you please review this patch?


Type mismatch Socket broadcast,broadcastEvent

sockets.contains(_ws) => sockets.contains(this)

Thanks for that contribution!
LGTM


SyntaxError: Invalid RegExp: Invalid escape, js engine: hermes

Bug Description
a regexp from this lib triggers this error on Hermes(React native).
// node_modules/zod-to-json-schema/dist/cjs/parsers/string.js
exports.zodPatterns = {
  // remove other codes
  emoji: RegExp("^(\\p{Extended_Pictographic}|\\p{Emoji_Component})+$", "u"),
};

"expo": "~51.0.21",
"react-native": "0.74.3"

Steps To Reproduce
a repo to reproduce it.
https://github.com/Albert-Gao/rn-invalid-regexp
The Expected Behavior
It should work. (Works on JSC)
More
It seems to be a Herms issue according to this: https://github.com/facebook/hermes/issues/1027
So I first created an issue on the Hermes side: https://github.com/facebook/hermes/issues/1460
But if it is really hard to solve on the engine side, I wonder is there a way we can tweak this regexp to make it compatible with Hermes?

seems it will be solved in the future version of Hermes, so close this one :)

@Albert-Gao This is now avoided with lazy-loading. Released in 3.23.2.

@StefanTerdell thanks, i tested, works like a charm with Hermes now :)


Compile libgit2 deterministically by sorting read_dir

It seems the order that C files are passed to build.file(&path); has impact on the binary. Right now build.rs is using a simple read_dir, so the final binary varies depending on the order the files are returned by the filesystem of the build machine. This patch collects into a Vec first and then sorts it to ensure the order of build.file(&path); calls is always deterministic.
Fixes #618

Thanks!


onclone is not working

Bug reports:
I want to change the display property of myDiv from none to block inside the cloned document. The reason to do this is that I want to hide my div in the actual dom. When I am trying to use onclone option of html2canvas, to change the property it is not reflecting. Can someone please check if I am missing something here? Please find below the link to the reproducer.
Codesandbox
Specifications:

html2canvas version tested with: 1.0.0-rc.7
Browser & version: Chrome 87
Operating system: Windows 10

建议，将你的内容，放在整个页面的下面  z-index: -1 上面再盖一层， 推测是   html2canvas 不能识别 display: none 的元素

建议，将你的内容，放在整个页面的下面 z-index: -1 上面再盖一层， 推测是 html2canvas 不能识别 display: none 的元素

@utkarsh22garg

Happens to me as well. onclone is indeed being called yet nothing is happening. Ended up downgrading to version 1.0.0-alpha.12.

I have the same problem, any news about this?

The onclone is working, but as you are rendering an element with display:none, it has no width/height. Changing it to use visibility and it works justs fine: https://codesandbox.io/s/xenodochial-northcutt-002g6?file=/src/App.js


Missing .env and error in geo-stream-kafka_producer docker

Thanks for putting together this example. I encountered an issue when building the app . The env_file is not available in the geostream folder which caused the docker compose to fail. So I removed it.
env_file:
- ./geostream/.env
When checking  geo-stream-kafka_producer docker I saw the following error . Hope you can help .
File "./app/main.py", line 5, in <module>
    from app.core.config import KAFKA_INSTANCE
  File "./app/core/config.py", line 12, in <module>
    KAFKA_URI: str = config("KAFKA_URI")
  File "/usr/local/lib/python3.7/site-packages/starlette/config.py", line 62, in __call__
    return self.get(key, cast, default)
  File "/usr/local/lib/python3.7/site-packages/starlette/config.py", line 75, in get
    raise KeyError(f"Config '{key}' is missing, and has no default.")
KeyError: "Config 'KAFKA_URI' is missing, and has no default."

hi @mtvu, sorry for the late reply. I guess I should've added the information in the readme. The consumer, as well as the producer have a config.py that is looking for an .env file and in there for the KAFKA_URL and KAFKA_PORT. You can either provide an .env file or you set the parameter yourself.


Ability to tail metrics

Sometimes it would be awesome to run expensive query only to fetch a small portion of data (:
We can extend StoreAPI for this, by adding some limits (series, chunks etc)

Still valid and help wanted 🤗


Remove pkg package

fixes #30

Codecov Report

Merging #38 (ac275cc) into master (c149870) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #38   +/-   ##
=======================================
  Coverage   87.42%   87.42%
=======================================
  Files          11       11
  Lines         867      867
=======================================
  Hits          758      758
  Misses         72       72
  Partials       37       37

Impacted Files
Coverage Δ

config/config.go
95.74% <ø> (ø)

parser/parser.go
100.00% <ø> (ø)

task/daemon.go
0.00% <ø> (ø)

task/message.go
100.00% <ø> (ø)

task/repo/authfs.go
80.00% <ø> (ø)

task/repo/data.go
73.91% <ø> (ø)

task/repo/repofs.go
80.20% <ø> (ø)

task/server.go
81.27% <ø> (ø)

task/task.go
96.34% <ø> (ø)

task/transport/server.go
100.00% <ø> (ø)

... and 1 more

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 c149870...ac275cc. Read the comment docs.


Add ability to ship dry ice to UPS

Adds the DryIce node to the purchase request when the packages have a dry_ice option.
Usage looks like:
Package.new(80, [2, 6, 12], :units => :imperial, :dry_ice => {weight: 1.4})

and gets you a nice comment on the label

and I'm hoping to use the same dry_ice hash option for FedEx soon.

I'm hoping to use the same dry_ice hash option for FedEx soon.

Would be great to keep them consistent!

Thanks!


Use busybox:1.28 instead of busybox:1.26

Use multi-arch busybox:1.28 image instead of busybox:1.26
Signed-off-by: Nitesh Konkar<EMAIL_ADDRESS>

@nitkon Please sign the CLA.
The change LGTM.

@Random-Liu : I have now signed the CLA.


Fix accounts profile

Getting accounts tab ready for prime time.

@eoghanTadhg Can you double-check the styles of the subscriptions tab?  The subscriptions and listservs had description text, but it was hard-coded lorem ipsum.  I changed that to dynamic helper {{description}}, but did not define any since I figured they were all self-explanatory.  However, the main text is no longer perfectly aligned vertically.

@micchickenburger , Unfortunately originally designed for just handling a title, the description was added after the fact, thus margins were adjusted to align both lines center with the toggle switches.
Short of rebuilding that section using display:table display:table-cell and vertical-align properties, it could not be accomplished with great ease.
We can open a new ticket to improve that feature?
In the meantime, we modify the margins to accomodate w/ description or w/o.
Thoughts?

@eoghanTadhg Sure, let's just modify the margins for now.

@micchickenburger, I've adjusted the margin accordingly.


Feature/illuminate database

We are no longer working on Slim 2 as Slim 3 is nearly ready for release and so we are only accepting security fixes to Slim 2.
However, be aware that the Slim develops all use different database abstraction libraries, so we are unlikely to ever dictate a specific one in the skeleton application.

That makes sense, thanks.


Updated the Dark mode button

Related Issue
Fixes: #823
Description
Added the dark mode button and fixed its position for responsiveness on small screens.
Type of PR

[x] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
Large Screen:
https://github.com/Suchitra-Sahoo/AgriLearnNetwork/assets/115869626/128e2720-009b-457d-9648-26f35ec55107
Small Screen:
https://github.com/Suchitra-Sahoo/AgriLearnNetwork/assets/115869626/10401c31-afb8-488b-abdd-18dfeba88b83
Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

@Suchitra-Sahoo Please review this PR and also tell me if I have to make any changes if it's correct please assign it to me and add level and label

Position is fine now. But the mode is not changing when i'm clicking on the option.

But when I am doing its working properly


Compiling println!(indoc!(...)) hangs forever

The following never finishes compiling:
#[macro_use]
extern crate indoc;

fn main() {
    println!(indoc!("
        Help I don't compile
    "));
}

Thanks! This was previously reported in #12. As far as I know there is no way for this to work on the stable compiler. You can switch to the "unstable" feature of indoc, or use runtime-fmt with stable indoc, or give up on indoc.

Alright, thanks for the heads up. indoc is great btw :)


Updating solution for challenge 2 & 3

Adding some more content related to the latest Azure changes and updating the screenshots accordingly

@microsoft-github-policy-service agree [company="{Microsoft}"]

@microsoft-github-policy-service agree


CI KIWI test is now using kube 1.21, not 1.22

There is a revert of the kube version of he kiwi ci test.
It was using 1.21, but later changed to use 1.22, so knative operator can pass.
But now it is back to use kube 1.21.
@mvalarh

Yes, we had to revert. We are currently designing how we are going to handle such situation. Temporary i can enable it for you if needed.

Right. It will be great, if you can make knative-operator an exception to run on kube 1.22.

HI @J0zi @mvalarh,
The latest Kind version uses 1.23. Could we not update it?

@camilamacedo86 @mvalarh Same is happening to us with Kiwi tests #1310 (Tackle beta.1 requires v1.22 minKubeVersion) and we are set to release on Jun 16th our stable, will probably run into it again, are exceptions possible per project?

We are working on dynamic k8s version. We will use latest k8s and if operatorhub.io/ui-metadata-max-k8s-version: "1.21" is specified we will use ks8 1.21. This feature should be ready this week.

This is in production thanks to @J0zi


Update README.md

Changes: Added the link of Github Flow in README for collaboration by noobs.

@till-tomorrow To follow best practices of contribution, first create an issue with the description about the bug, feature or chore and then send the PR for the same.


Op557 option for disabling gravatar

Adds an option to disable Gravatar, specially useful for offline installations (as the timeout if unable to connect to gravatar is 5 minutes).
It is disabled by default on tests (the relevant tests, stub this to the correct value for testing). This (+ #7246) fixes offline tests.
From CartoDB/cartodb-onpremise#557

And the final piece of the puzzle for offline testing. Can you CR @juanignaciosl?

Added a suggestion about gravatar_enabled?, 👍  after that. Please make sure that configuration parameter is deployed before deploying this ;-)

Shouldn't need to deploy any configuration changes, if the parameter is not found it defaults to true, as was doing before.
Anyway, the config change will go first :+1:

Oh, I didn't realize. Since its name is gravatar_enabled I thought that default was false, but it makes sense keep current behaviour 👍

New flag deployed, merging this...


Adjust test/material/popup_menu_test.dart for Dart 2 semantics.

Dart 2 implements reified generics which means showMenu<int> creates
_PopupMenu<int> not _PopupMenu<dynamic>.

@Hixie friendly ping.

@Hixie applied your suggestion. PTAL

Ping


ReactEditText extends AppCompatEditText

Summary
Google recommends to extend AppCompat widgets, and Android Studio suggests the change. This PR changes ReactEditText to extend AppCompatEditText.
Changelog
[Android] [Changed] - ReactEditText extends AppCompatEditText
Test Plan
CI is green

@dulmandakh This PR failed to land because there are internal components that inherit from ReactTextInputManager that now require to import the androidx.appcompat.widget.AppCompatEditText dependency.
I will modified that when I have some time, and I will try to re-land

@mdvacca you can use exported_deps

@hramos @mdvacca please review and merge


Gh 4304 improve docker image security

GitHub issue resolved: #4304
Briefly describe the changes proposed in this PR:

PR Author Checklist (see the contributor guidelines for more details):

[ ] my pull request is self-contained
[ ] I've added tests for the changes I made
[ ] I've applied code formatting (you can use mvn process-resources to format from the command line)
[ ] I've squashed my commits where necessary
[ ] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

CQs:

[ ] https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/5394

Before:

After:

Hmz, looks like you've accidentally committed fixes for (white space) formatting issues in a series of unrelated files

Hmz, looks like you've accidentally committed fixes for (white space) formatting issues in a series of unrelated files

I got a bit ahead of myself by upgrading a bunch of build time dependencies while I was at it, but then I realise I would be spending the entire weekend filing CQs for them...so I reverted those changes. The only "unrelated" thing I'm keeping is some performance improvements to the maven build.

I got a bit ahead of myself by upgrading a bunch of build time dependencies while I was at it, but then I realise I would be spending the entire weekend filing CQs for them...so I reverted those changes.

Have you tested the Eclipse dash-license tool ? Filing CQs is now a (mostly) automated process

I got a bit ahead of myself by upgrading a bunch of build time dependencies while I was at it, but then I realise I would be spending the entire weekend filing CQs for them...so I reverted those changes.

Have you tested the Eclipse dash-license tool ? Filing CQs is now a (mostly) automated process... a much nicer experience than manually adding CQs and attaching jars via the old website ...

I didn't pick up any of the maven plugins :(

Fwiw I think we don't really have to file CQs for maven plugins anymore. We did so in the past, but it later turned out that we have a lot of discretion there. Especially as we don't actually distribute these, they're just part of our build env.


sql dsl

cool project.
I saw in some issue or other that you would be happy about an SQL DSL.
Genji has one if your interested. https://github.com/genjidb/genji
its quite nice... Let me know if you have any questions.
Just saw in https://github.com/kelindar/column/issues/5 that your thinking about persistence too. genji might be useful for that too.  But i imagine you want something closer to a sime file system rather than a LSM ?

Cool, I'll have a look. For SQL DSL this package will never implement this, I want to keep the focus of this only on the underlying decomposition storage model implementation and nothing else. Other projects can take both and implement a SQL or anything else for querying.
For the snapshotting we only need a redo log with periodic compaction, nothing too fancy.


WRP-6257: Cell: Add grow prop to expand the size to its container

Checklist

[x] I have read and understand the contribution guide
[x] A CHANGELOG entry is included
[x] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
A growable cell will expand to its maximum size according to the remaining space of the container. This is used when you want to grow the size of this cell so that it fills the container.
Resolution
add grow prop to Cell component.
A growable Cell has a declaration of flex: 1 1 100% in CSS by default. However, the flex-basis property is overridden by the var(--cell-size) value passed from JS. And by combining max-width: none and flex-grow: 1 declaration, its size can be increased by the size of its parent container.
Also, by the declaration of flex: 1 1 100%, the flex-shrink property has a value of 1, which means that its size can be reduced as much as necessary, but because of min-width: var(--cell-size) and min-height: var(--cell-size) declaration, it does not decrease below the specified cell size.
When combined with shrink, shrink prop takes precedence over grow prop and grow prop is simply ignored. When used in conjunction with size, the size will be the minimum size, growing as necessary, to fit the container.
Additional Considerations
Screenshot tests are added to Sandstone (enactjs/sandstone#1417)
Unit Test Cases

grow CSS class is applied when no props (shrink, size) are  given
grow CSS class and flex-basis CSS style are applied when grow and size props are given
grow CSS class is not applied when used with shrink prop

Sampler

The thrid Cell is modified to change the grow and size props.The part where grow is automatically activated is still checkable when shrink prop is disabled in the second Cell.
Clarify the names of each Cell and control to make them easier to distinguish.

Links
WRP-6257
enactjs/sandstone#1417
Comments
Enact-DCO-1.0-Signed-off-by: Hoeun Ryu<EMAIL_ADDRESS>

A new patch set has been pushed to address reviewer's comments.

A new patch set has been pushed and PR description has been changed to address reviewer's comments.

PR has been updated to address comments.

merge with the latest develop branch
fix the typo, thrid -> third
use NO-BREAK SPACE instead of normal space for each Cell's content in the sampler.