(SERVER-1130) Add a per-environment timestamp into the env-classes cache

This commit adds a "last-updated" timestamp per environment to the
environment classes cache.  The timestamp is used by incoming
environment_classes cache requests to determine if the cache info has
changed between the time the request starts parsing for info and when
the cache is about to be updated, e.g., if a call from a separate
request to mark-environment-expired were to occur during parsing for
class info in a request.  If the timestamp has been updated during that
window, the cache is not updated with the latest parsed data, since that
data may already be stale.
This commit also adds an integration test,
class-info-updated-after-cache-flush-during-prior-request, which
performs an environment cache flush while a class info request is in
progress and validates that the following class info request gets the
latest data.

Ping @cprice404 for review whenever you get a chance.

+1 other than the one assertion that i think isn't quite right.

@cprice404 I think I hit all of your feedback so far.  Let me know if you see anything else that you'd like to see changed.

@rlinehan it might be worth having you review this post-facto in case I missed anything and/or just to get yourself a bit more familiarity with this part of the code.  I went ahead and merged it because I wanted to try to start pushing builds up today.

Retroactive :+1:. I left a few comments about the environment-class-info-tags unit test, because I found that pretty confusing to read through, and I agree that creating a with-puppetserver-and-mocked-jruby-service macro at some point might be really nice, but those are both small/nitpicky things and otherwise this looks good.


Failed to generate a source tarball for project

Hi, thank you for making cargo-dist happens. This was really needed. Filing a small bug:
This is likely an edge case that got missed, but it happens in a fresh git project with no commits.
Command ran: cargo dist build
Error log:
fatal: not a valid object name: HEAD
  × We failed to generate a source tarball for your project
  help: This is probably not your fault, please file an issue!

Adding a commit to the git project, makes it go away.

Good catch, thank you! I hadn't considered this usecase. We check whether you're running in a directory that isn't a git repo, but we don't check whether you're in a repo that has no commits. I'll fix this.

This is fixed; we'll have the fix in an upcoming release. Thanks again for your report!


Added the game of ATLAS

PR Description 📜
Added the game: ATLAS
Fixes #1907

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[x] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Oh okay sir

Thank you  @AnkitaBarbora , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀

Oh okay sir, I thought I could add it in this project because the game logic and gameplay was different. But no problem, I would love to continue contributing for this project 😄


Initial conformance tests for TCPRoute

What would you like to be added:
Initial conformance tests for TCPRoute need to be added.
Why this is needed:
In order to mature TCPRoute to beta and eventually GA, we'll need conformance tests and implementations reporting their usage of them.

/cc

@shaneutt when you have a moment, do you mind assigning me this issue?


Add .gitignore for typical build artifacts

I'd personally rather encourage out of tree building, even for simple projects.... Thoughts?

I mean, I guess I'm just so use to it that i have a completely ingrained pattern for out-of-tree building.
Maybe I should just use git clean more instead.
Anyways, I don't really see any harm. Sorry for arguing. ;]


[SPARK-16632][sql] Respect Hive schema when merging parquet schema.

When Hive (or at least certain versions of Hive) creates parquet files
containing tinyint or smallint columns, it stores them as int32, but
doesn't annotate the parquet field as containing the corresponding
int8 / int16 data. When Spark reads those files using the vectorized
reader, it follows the parquet schema for these fields, but when
actually reading the data it tries to use the type fetched from
the metastore, and then fails because data has been loaded into the
wrong fields in OnHeapColumnVector.
So instead of blindly trusting the parquet schema, check whether the
Catalyst-provided schema disagrees with it, and adjust the types so
that the necessary metadata is present when loading the data into
the ColumnVector instance.
Tested with unit tests and with tests that create byte / short columns
in Hive and try to read them from Spark.

Test build #62561 has started for PR 14272 at commit d853ba0.

@yhuai @liancheng
Not sure if this is the best place for the fix, but the problem is gone with the change. It duplicates some minor logic from ParquetSchemaConverter, but it seems weird to call that class from here since this code has no access to config data.

Test build #62561 has finished for PR 14272 at commit d853ba0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test PASSed.

This LGTM. Although it's a little bit hacky since technically the fields in requested schema passed to the Parquet record reader may have different original types (INT_8 and INT_16) from the actual ones defined in the physical file, fortunately Parquet record reader doesn't check for original types.

I'm merging this to master.
@yhuai Do we want this in branch-2.0?

Would like to add that AFAIK byte and short are the only problematic types that we don't handle before this PR. Other Hive-Parquet schema conversion quirks like string (translated into binary without UTF8 annotation) and timestamp (translated into deprecated int96) are already worked around in Spark.

Discussed with @yhuai, I'm also merging this to branch-2.0.
@vanzin Thanks for fixing this!

yea. I think the fix is pretty safe. After discussion with @liancheng, seems the more general fix is to just to use the requested catalyst schema to initialize the vectorized reader.

Opened #14278 for the simpler yet more general fix.


Cu 8696pcy8n create friends page patryk kosiski

Add new root for friends
Add first version of friends page
Refs: CU-8696pcy8n

Task linked: CU-8696pcy8n Create friends page

This is how it looks like:


SNPE dill bug (new?)

Hi,
I repeat #653 but with the default SNPE (with maf) to test the inference saving with dill but I get  an error

dill.version
'0.3.4'

    raise PicklingError(
_pickle.PicklingError: Can't pickle <built-in method tanh of type object at 0x2b729fb78980>: it's not found as torch._VariableFunctionsClass.tanh

Here is the snippet

import torch
import dill

from sbi.inference import SNPE, prepare_for_sbi, simulate_for_sbi
from sbi import utils as utils
from sbi.utils.get_nn_models import posterior_nn

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

def main():

    num_dim = 1

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

    simulator, prior = prepare_for_sbi(linear_gaussian, prior)

    inference = SNPE(
        prior=prior, device="cpu"
    )

    theta, x = simulate_for_sbi(simulator, proposal=prior, num_simulations=500)

    inference = inference.append_simulations(theta, x)

    density_estimator = inference.train()

    posterior = inference.build_posterior(density_estimator)

    obs = linear_gaussian(prior.sample())
    posterior = posterior.set_default_x(obs)

    with open(f"saved_posterior.dill", "wb") as f:
        dill.dump(posterior, f)

if __name__ == "__main__":
    main()

An idea? does I should use pickle? if so a snippet would be nice.
Thanks

Hi, thanks for creating the issue. As described here the posterior should be saved with pickle.

Thanks, notice that the FAQ 6 has probably a wrong link at the end, as it describe a dill saving scenario and I would have expected a link to the one you point (ie FAQ 5). (hope to be clear)

Thanks for the pointer regarding FAQ 6. Please simply ignore the last paragraph of the question (it is outdated and will be fixed asap): you can save inference objects and posteriors with pickle, no need to use dill.
For multi-round: I would save the posterior and inference object after every round. And yes, I would also save the seeds. For sbi, you have to seed only torch and numpy (only if you use slice_np as MCMC sampler).


Edit image metainfo

There should be an edit button on each row of the images:

That allows to edit metadata information.
      "metadata": {
        "name": "Silica_small.tif",
        "relativePath": "Fribourg/Silica_small.tif"
      },

There should be 2 metadata information currently:

name
pixelSize

pixelSize should be defined as a number + units. Like '1 mm' and corresponds to the size of 1 pixel.
We will see later to convert this using js-quantities.

The type of 'pixelSize' should be: https://github.com/cheminfo/cheminfo-types/blob/main/src/core/Value.d.ts
The allowed units could be for now: nm, µm, mm, m, km
You can use 'input group' to input the value
https://blueprintjs.com/docs/#core/components/input-group

pixelSize should be defined as a number + units. Like '1 mm' and corresponds to the size of 1 pixel.

Should the pixel value and unit be saved in the same metadata ?
I think it would be easier for the display and data editing if they are saved separately
      "metadata": {
        "name": "Silica_small.tif",
        "relativePath": "Fribourg/Silica_small.tif"
        "pixelSize": "0.272727272727"
        "pixelUnit": "nm"
      },

I would prefer it is saved in the same metadata but you are right that we didn't develop a way to display it so you can for now use 2 fields.

Please add a 's' at units. pixelUnits


This tutorial didn't work for me with Visual Studio Code

I am using:
dotnet: 3.1.413
vs code: 1.61
I tried to run this, and I get it to say it is listening on the ports, but when I open my browser, I get: No webpage was found for the web address: https://localhost:5001/

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

ID: 583ae3e7-5915-f22b-e54c-6c100cf2a7da
Version Independent ID: 95f2549e-29f9-e31a-b4d0-432b971643ff
Content: Tutorial: Create a web API with ASP.NET Core
Content Source: aspnetcore/tutorials/first-web-api.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Got confused between .net core and .net framework.


Improve validation of the configuration file at deserialization time

Description
Leverage serde to improve validation of the configuration file at deserialization time.
The idea is to validate as many static properties of the configuration file at deserialisation time by replacing String and Option<String> with more specific types such as std::time::Duration, Strategy or Direction.

For contributor use:

[ ] Wrote tests
[ ] Updated CHANGELOG.md
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Updated relevant documentation (docs/) and code comments
[ ] Re-reviewed Files changed in the Github PR explorer

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@01dde40). Click here to learn what that means.
The diff coverage is 24.2%.

@@           Coverage Diff            @@
##             master     #20   +/-   ##
========================================
  Coverage          ?   20.6%
========================================
  Files             ?      19
  Lines             ?     398
  Branches          ?      41
========================================
  Hits              ?      82
  Misses            ?     289
  Partials          ?      27

Impacted Files
Coverage Δ

relayer/cli/src/commands/start.rs
0% <0%> (ø)

relayer/cli/src/commands.rs
46.6% <100%> (ø)

relayer/relay/src/config.rs
29% <23%> (ø)

relayer/cli/src/application.rs
34.9% <25%> (ø)

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 01dde40...bda6902. Read the comment docs.

Looks good. At some point we should identify parameters that are chain type specific and probably rethink the .toml configuration "language".

Agreed! Perhaps even look at something like the Dhall configuration language: https://dhall-lang.org


Timezone issues in ui

Local time is being used in the frontend while backend is using US-central time
Sync them together

issues resolved


Bot Stops Working Properly after ServerBusyOrOfflineException

Expected Behavior
catching pokemon going to forts
Actual Behavior
Server Busy

then after the bot restarts it's just walking around doing nothing

Steps to Reproduce
after the bot loses connection like in the first picture
it stops working properly after restarting the programm
im running a loop
@echo off title inet :loop python pokecli.py timeout /t 60 >null GOTO loop
Other Information
OS: Win7
Git Commit: 190640f06fc623f804c554ce1ac9264c9fa8b22d

Got the same problem

Got the same problem
Win 10


Detection confidence when drawing tracked_objects' boxes?

Hi @aguscas ,
I am drawing bounding boxes from tracked_objects but I don't see an option to display detection confidence.

Why is that so?
What's the easiest way to get detection confidence? For my use case, I need the ability to track but also to display detection confidence in the output.

Let me know in case of any questions. Thanks!

Doesn't the argument draw_scores of the draw_boxes function allow you to draw the confidences?

No, I just gave it a try. draw_scores doesn't seem to work with tracking_objects but works with Detection objects. For my use case, I would need it to work with tracking_objects since I also want tracking object id to keep track of the same object. Let me know if you need anything additional. Thanks!

Alright, makes sense since the score is an attribute of the Detection instead of the TrackedObject.
I can make a PR to add an score attribute to the TrackedObject to draw it (setting it to None in the TrackedObject. tracker_step method, and setting it equal to detection.score in the TrackedObject.hit method), but we would have to see with @facundo-lezama  or @javiber  if that would be a desirable feature to have in general before.
Anyway, I am not sure I understood the exact reason you want to be able to draw the id. What did you mean by 'I also want tracking object id to keep track of the same object'?

Yeah, PR would be great!
I am using norfair to track faces. When I present my users with the output, I want to show them:

detected faces with their confidence
if the same person is present in multiple frames, "id" from tracked_object to denote that it's the same person you have seen in other frames so essentially group faces by person.

Does that make sense?

I made this PR which add the scores attribute to the TrackedObject instances. It still is not merged (since we need to first discuss if that is a feature we would like to have), but you can try installing that version of norfair if you want to use it


close the loop on basic orders, use better seed

Codecov Report
Patch and project coverage have no change.

Comparison is base (49ea98e) 100.00% compared to head (9620fbb) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##               1.5     #1070     +/-   ##
===========================================
  Coverage   100.00%   100.00%
===========================================
  Files           46        21     -25
  Lines         2652      1230   -1422
  Branches       396       220    -176
===========================================
- Hits          2652      1230   -1422

Flag
Coverage Δ

foundry
?

production
?

reference
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 35 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


sc-im: aligning a selection of cells cause crash

Description of changes
By disabling fortify in gcc this fixes #335130 sc-im: aligning a selection of cell's cause crash
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

[x] Fits CONTRIBUTING.md.

Not true. The commit message should start with sc-im.

Please edit the commit summary to sc-im: fix crash and put more details in the body.

Please edit the commit summary to sc-im: fix crash and put more details in the body.

I just did. Sorry for my beginner mistakes.

Looks OK to me but I cannot reproduce the bug on Darwin. Needs someone with Linux to test it.

Result of nixpkgs-review pr 335133 run on x86_64-darwin 1

1 package built:

sc-im

I was able to verify the commit on x86_64-linux.
On recent nixpkgs (9g23szywla53rajzivcisxkiv415hwy0-sc-im-0.8.4), sc-im dumps core when trying to align the cells. With this PR (x6psi9sw54xyq2aa34k0p3ss1pxb8c4i-sc-im-0.8.4), aligning works as expected.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 335133

x86_64-linux

:white_check_mark: 1 package built:

sc-im

@mipmip please rebase to handle merge conflicts.

Thanks, I'm happy as this is my first PR 🎉


How can I manually convert the mp4 to a "real" mp4 if I have forgotten the automatic thing?

Title

Try this:
https://superuser.com/questions/624565/ffmpeg-convert-flv-to-mp4-without-losing-quality

In the new version, the conversion is automatic


Target element not being re-evaluated while the DOM is still being built

I'm submitting a bug report

Framework Version:
1 - Aurelia CLI 3.0.1

Operating System:
OSX 14.4.1

Node Version:
18.17.1

NPM Version:
9.6.7

Browser:
all | Chrome XX

Language:
ESNext

Current behavior:
Using the portal attribute, like portal="target.bind: isMobile ? '.bncHeader' : '.bncOptionsWrapper'" puts the element with this attribute at the end of the body if the intended target element isn't rendered yet. Otherwise it works fine.
I can work around this problem by binding the to-be-portalled element later, when the target element is available in the DOM but this is not ideal.
Expected/desired behavior:
The target portal element should be re-evaluated while the DOM is still being rendered.
What is the motivation / use case for changing the behavior?
For a hybrid application for desktop / mobile some elements need to be portalled to somewhere else on mobile.

Thanks @Esger , it doesnt seem like a straight forward task with "while the dom still rendering". We can try to wait for the task queue probably, do you want to have a PR for this?

@bigopon Waiting for the task queue might be a better idea indeed. Our application makes several calls to the back end before everything is rendered.
Maybe the Mutation Observer API can be useful. https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver as well? (observe the whole document to check if the target appears)
A PR for me isn't very useful I'm afraid :) although I am curious about the solution.


Cannot make a custom response serialization

Cannot get 3.0 to work with custom response serialization, because of error "Cannot call a value of non-function type 'NSHTTPURLResponse?'"

Your static serializer uses an optional value while the response serializer does not. That is your issue. In the future, please post sample code and not screenshots. It's much easier for us to debug and for others to code scan.
Good luck!

Thanks man! Appreciate your work!


Escaping and quoting issues

Quotation marks are mandatory in XML. Since there is no easy way of telling HTML apart from HTML-looking XML (<title> is both an HTML and SVG tag, for example), we should quote everything.
This also addresses #31.

Some entities must be preserved to prevent JS injection attacks:

// Read properly escaped text.
auto doc = createDocument(`<script>alert("Hello!");</script>`);
// Write malicious code.
assert(doc.root.innerHTML == `<script>alert("Hello!");</script>`);

Minification is indeed a nice goal as long as it doesn't lead to invalid outcome.
Hmm, it might be a good idea to keep a whitelist of HTML block tags. Then an emitter could work in one of three modes:

Generic (conservative) mode,
HTML mode,
XML mode.

In HTML mode it omits quotation marks; in XML mode it "self-closes" empty tags (which is not legal in HTML). When stepping into a non-whitelisted tag, it switches to XML.
However, since this library can be used not only for complete documents but also for fragments, an emitter should start in generic mode by default (to not accidentally break anything). There should be an optional parameter in compactHTML which specifies the initial mode. That way a user can manually enable quotes omission if they know for sure their document is an HTML document.
Any remarks on that?

Personally, I think that attribute values should either always be quoted, or that there should be some sort of setting to specify whether the output should be "compact" (non-quoted) or fully quoted.
I've rarely if ever seen HTML with non-quoted attribute values before encountering it with htmld, and while yeah, it does save a few bytes here and there, it just feels sloppy to me to leave values unquoted even if it is technically allowed by the spec.

The idea of the compactHTML methods was to produce the smallest possible valid representation of the nodes, not for humans to look at or having feelings about, but for crawlers and browsers to ingest.Note that being XML compatible is not at all a goal of this library, but I do agree it doesn't hurt to aim for it. I think having the non-compact methods allow for a setting is a great idea, but compactHTML should try to live up to it's name.

How about having a compactXML method?

How about having a compactXML method?

I'm afraid there would be too much duplicated code, so I'd stick with an enum parameter to compactHTML.
The idea is to be able to get the smallest possible representation that is:

valid HTML (the most common use-case),
valid XML,
both valid HTML and XML when it's not known ahead of time what the document is (by coincidence, it's more aesthetically appealing for some people than the 1st).


webhook patcher: replace istio queue with k8s queue

Please provide a description of this PR:
To prevent out of order patch ops cause config outdated

LGTM. Couple of nits

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
c481b6af359d2a4881c305ce17984aee1939d5f7
link
unknown
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Fix uncheck follow company checkbox conflicting with some boolean options

My proposed solution is to change,
boolean['follow'] = false
To
boolean['stay up to date'] = false
On
fillFields.ts

Better solution:
Don't use the fillBooleans method for this.
Select the follow [companyname] to stay up to date with their page checkbox by id=follow-company-checkbox


fix: remove jsx ext from declaration file ext

Description of changes:
Removes .jsx extension from generated declaration files
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Can we get a unit test on this, please?


TCP2: Add support for arbitrary data payloads

At present, TCP2 can’t correctly handle payloads greater than 128 bytes.
So, add support for arbitrary data payloads.
As a result, eliminate net_pkt_linearize().

@tbursztyka
Thanks for the input, fixed.
Regarding 506ec7a, if there’s a reason to translate NET_BUF_ASSERT() into nothing, I can drop it.
What’s the logic, anyway?

@ozhuraki indeed assert is not a log level. Instead, put it out of the ifdef, and make it use __ASSERT as you did. If one does not want such assert to be made, it will be possible to disable it via unselecting CONFIG_ASSERT
Or create a NET_ASSERT in Kconfig... either way. Let's see what @jhedberg thinks about it

@tbursztyka
OK and done.

Let's see what @jhedberg thinks about it

The mapping to __ASSERT seems fine to me

What's the status of this PR? @ozhuraki are you going to address the latest comment from @jukkar? Fixes to commits that are not yet upstream should be done in those commits themselves (using e.g. git rebase -i) rather than by adding new "fixup" commits to the PR.
@tbursztyka are you ok with this PR after the latest changes?

@jhedberg

What's the status of this PR?

Feedback had been addressed. The PR itself might have been missed while the master have been blocked during the release.

Fixes to commits that are not yet upstream should be done in those commits themselves (using e.g. git rebase -i) rather than by adding new "fixup" commits to the PR.

Fixes had been done to the commits themselves. That comment might be slightly out of date, unless I am missing something.

@ozhuraki ok, thanks! @tbursztyka are you still planning to review this?

@tbursztyka

Please apply the comment I made (you still have parameters to re-indent in first or second patch)

Sorry, a few have slipped indeed, corrected.

and reply to our questions about hard coded numbers etc...

The rest had been fixed.

ah, instead of fixing in place the hard coded number you added another patch to do it everywher. ok.

Ok, lets get this merged as there are more TCP patches coming after this one.


Index.rs: Add db writeability check

Add a writeability check to the is_database_old function in case the database is managed externally (such as being in the /nix/store directory).
Closes #33
Signed-off-by: David Houston<EMAIL_ADDRESS>

Thanks


break command confuses an absolute file path with a regexp

For example:
(dlv) b /home/user/file.go:15
Command failed: Malformed breakpoint location "/home/user/file.go:15" at 0: no line offset can be specified for regular expression locations

My mistake, I'll fix it.


Can't login using firebase_app_distribution_login

Issue Description
When i try to use the firebase_app_distribuition_login function the link that is generated returns a 400 response code in the browser. I have tested it on my Macbook on our Mac Mini Build Server and a colleague at my company is having the issue.

Configuration
bundle exec fastlane run firebase_app_distribution_login --verbose
Complete verbose output
[✔] 🚀
DEBUG [2022-04-12 11:13:37.70]: Checking if there are any plugins that should be loaded...
DEBUG [2022-04-12 11:13:37.70]: Loading 'fastlane-plugin-appicon' plugin
INFO [2022-04-12 11:13:37.70]: gem 'fastlane-plugin-appicon' is already installed
DEBUG [2022-04-12 11:13:37.71]: Loading 'fastlane-plugin-firebase_app_distribution' plugin
INFO [2022-04-12 11:13:37.71]: gem 'fastlane-plugin-firebase_app_distribution' is already installed
+-------------------------------------------+---------+------------------------------------------------+
|                                             Used plugins                                             |
+-------------------------------------------+---------+------------------------------------------------+
| Plugin                                    | Version | Action                                         |
+-------------------------------------------+---------+------------------------------------------------+
| fastlane-plugin-appicon                   | 0.16.0  | android_appicon, appicon                       |
| fastlane-plugin-firebase_app_distribution | 0.3.3   | firebase_app_distribution_login,               |
|                                           |         | firebase_app_distribution_add_testers,         |
|                                           |         | firebase_app_distribution_get_udids,           |
|                                           |         | firebase_app_distribution,                     |
|                                           |         | firebase_app_distribution_get_latest_release,  |
|                                           |         | firebase_app_distribution_remove_testers       |
+-------------------------------------------+---------+------------------------------------------------+

objc[27891]: Class AppleTypeCRetimerRestoreInfoHelper is implemented in both /usr/lib/libauthinstall.dylib (0x1e52d5eb0) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1040904f8). One of the two will be used. Which one is undefined.
objc[27891]: Class AppleTypeCRetimerFirmwareAggregateRequestCreator is implemented in both /usr/lib/libauthinstall.dylib (0x1e52d5f00) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x104090548). One of the two will be used. Which one is undefined.
objc[27891]: Class AppleTypeCRetimerFirmwareRequestCreator is implemented in both /usr/lib/libauthinstall.dylib (0x1e52d5f50) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x104090598). One of the two will be used. Which one is undefined.
objc[27891]: Class ATCRTRestoreInfoFTABFile is implemented in both /usr/lib/libauthinstall.dylib (0x1e52d5fa0) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1040905e8). One of the two will be used. Which one is undefined.
objc[27891]: Class AppleTypeCRetimerFirmwareCopier is implemented in both /usr/lib/libauthinstall.dylib (0x1e52d5ff0) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x104090638). One of the two will be used. Which one is undefined.
objc[27891]: Class ATCRTRestoreInfoFTABSubfile is implemented in both /usr/lib/libauthinstall.dylib (0x1e52d6040) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x104090688). One of the two will be used. Which one is undefined.
Successfully loaded Appfile at path '/Users/ralfkralicek/Coding/Work/appname-ios/fastlane/Appfile'
- app_identifier: 'bundleIdentifer'
- apple_id: 'email'
- team_id: 'teamid'
- itc_team_id: 'itc
-------
INFO [2022-04-12 11:13:37.81]: ---------------------------------------------
INFO [2022-04-12 11:13:37.81]: --- Step: firebase_app_distribution_login ---
INFO [2022-04-12 11:13:37.81]: ---------------------------------------------
INFO [2022-04-12 11:13:37.82]: Open the following address in your browser and sign in with your Google account:
INFO [2022-04-12 11:13:37.82]: https://accounts.google.com/o/oauth2/auth?access_type=offline&approval_prompt=force&client_id=563584335869-fgrhgmd47bqnekij5i8b5pr03ho849e6.apps.googleusercontent.com&include_granted_scopes=true&redirect_uri=urn:ietf:wg:oauth:2.0:oob&response_type=code&scope=https://www.googleapis.com/auth/cloud-platform
INFO [2022-04-12 11:13:37.82]:
 [2022-04-12 11:13:37.82]: Enter the resulting code here:

Environment

Library
Version

fastlane
2.2.6

fastlane-plugin-firebase_app_distribution
0.3.3

@RalfK92 we've released a pre-release version 0.3.4.pre.1 of our fastlane plugin with a fix for the login issue. Feel free to use this version in the meantime. We plan to ship a new 0.3.4 version with the fix by the end of the week.

@tagboola @lfkellogg thanks for the fast replies. I will try to your proposed solutions tomorrow.

@tagboola  i tried the 0.3.4.pre.1 release.
`bundle exec fastlane run firebase_app_distribution_login
[✔] 🚀
+-------------------------------+-------------+-------------------------------+
|                                Used plugins                                 |
+-------------------------------+-------------+-------------------------------+
| Plugin                        | Version     | Action                        |
+-------------------------------+-------------+-------------------------------+
| fastlane-plugin-appicon       | 0.16.0      | android_appicon, appicon      |
| fastlane-plugin-firebase_app  | 0.3.4.pre.1 | firebase_app_distribution_lo  |
| _distribution                 |             | gin,                          |
|                               |             | firebase_app_distribution_ad  |
|                               |             | d_testers,                    |
|                               |             | firebase_app_distribution_ge  |
|                               |             | t_udids,                      |
|                               |             | firebase_app_distribution,    |
|                               |             | firebase_app_distribution_ge  |
|                               |             | t_latest_release,             |
|                               |             | firebase_app_distribution_re  |
|                               |             | move_testers                  |
+-------------------------------+-------------+-------------------------------+
08:28:04: --- Step: firebase_app_distribution_login ---
08:28:04: ---------------------------------------------
08:28:04: Open the following address in your browser and sign in with your Google account:
08:28:04: https://accounts.google.com/o/oauth2/auth?access_type=offline&approval_prompt=force&client_id=563584335869-fgrhgmd47bqnekij5i8b5pr03ho849e6.apps.googleusercontent.com&include_granted_scopes=true&redirect_uri=http://localhost:8081&response_type=code&scope=https://www.googleapis.com/auth/cloud-platform&state=cac6fdb47daa665e0114bfc9076f70a3`
After copying the link into my browser i was able to select the google account but was then faced another error.

Hmm weird you received that error with Firefox. We tested the flow on Firefox and it seems to be working fine 🤔
Did the login flow work for you on Firefox before it was broken? The new flow does require connecting to localhost now. I wonder if there is a setting or extension that is preventing this. When you have a chance, can you try logging in with Firefox in troubleshoot mode?

What you guessed is actually true.  I'm using a plugin to automatically remove tracking elements from URLs.
https://addons.mozilla.org/en-US/firefox/addon/clearurls/
Seems there is a percentage encoding stuff going on which leads to the error.
Pasting this into my browser the plugin enabled,
https://accounts.google.com/o/oauth2/auth ?access_type=offline &approval_prompt=force &client_id=563584335869-fgrhgmd47bqnekij5i8b5pr03ho849e6.apps.googleusercontent.com &include_granted_scopes=true &redirect_uri=http://localhost:8081 &response_type=code &scope=https://www.googleapis.com/auth/cloud-platform &state=b0838f27746e151994b08f82334450ac
produces this url:
https://accounts.google.com/o/oauth2/auth ?access_type=offline &approval_prompt=force &client_id=563584335869-fgrhgmd47bqnekij5i8b5pr03ho849e6.apps.googleusercontent.com &include_granted_scopes=true &redirect_uri=http%3A%2F%2Flocalhost%3A8081 &response_type=code &scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcloud-platform &state=b0838f27746e151994b08f82334450ac
So no problem on your side. Thanks for your help.


[cli] Use kubeconfig with kubectl

When running rancher kubectl the command should use the kubeconfig for the current cluster to execute the command and not rely on the local kubeconfig file.

Available with v1.0.0-alpha11

Tested with v1.0.0-alpha11.
rancher kubectl command can be used to execute kubectl commands for the current cluster.


HHH-12630 Keep the original starting exception and use it as a cause

https://hibernate.atlassian.net/browse/HHH-12630

@yrodiere it's either that or I log the exception directly with the logger. What's your take on this?

Yes, not a big fan either but I suppose there's a good reason for that.

Merged, thanks!


Wrong project name (CFME) in UI info messages

appears in several screens, probably needs a global solution

@chessbyte not sure whose domain is this (productization? branding?) some mentions of CFME are shown in UI, some hardcoded in backend/written to log.

@bmclaughlin can you please try to track these down and productize the strings?

@abonas is this issue is no longer relevant can you please close.

I don't know if this is still relevant or not, I've not been working with miq for almost a year now.


style(): change all tutorials to an even nominal style

change all tutorials to an even nominal style

:+1: Seems to be a good idea!

@gilgda Change the Webserver.md to nominal style. Besides, really good work! :+1:


Error when importing 'vertexai.preview' and 'vertexai.language_models'

File Name
generative-ai/language/prompts/intro_prompt_design.ipynb
What happened?
During Qwiklabs - Google Cloud Skills Booster excercises, 'Generative AI with Vertex AI: Prompt Design' when running the vanilla version of the intro_prompt_design.ipynb
on the Vertex AI Workbench, based on the longs - the error similar to issue  #363 .
Relevant log output
from vertexai.language_models import TextGenerationModel
from vertexai.language_models import ChatModel
2024-03-05 18:50:42.218294: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
Cell In[6], line 1
----> 1 from vertexai.language_models import TextGenerationModel
      2 from vertexai.language_models import ChatModel

File ~/.local/lib/python3.10/site-packages/vertexai/__init__.py:22
     19 __version__ = aiplatform_version.__version__
     21 from google.cloud.aiplatform import init
---> 22 from vertexai import preview
     24 __all__ = [
     25     "init",
     26     "preview",
     27 ]

File ~/.local/lib/python3.10/site-packages/vertexai/preview/__init__.py:20
      1 # -*- coding: utf-8 -*-
      2
      3 # Copyright 2023 Google LLC
   (...)
     15 # limitations under the License.
     16 #
     18 from google.cloud.aiplatform.metadata import metadata
---> 20 from vertexai.preview import developer
     21 from vertexai.preview import hyperparameter_tuning
     22 from vertexai.preview import initializer

File ~/.local/lib/python3.10/site-packages/vertexai/preview/developer/__init__.py:18
      1 # -*- coding: utf-8 -*-
      2
      3 # Copyright 2023 Google LLC
   (...)
     15 # limitations under the License.
     16 #
---> 18 from vertexai.preview._workflow.serialization_engine import (
     19     any_serializer,
     20 )
     21 from vertexai.preview._workflow.serialization_engine import (
     22     serializers_base,
     23 )
     24 from vertexai.preview._workflow.shared import configs

File ~/.local/lib/python3.10/site-packages/vertexai/preview/_workflow/serialization_engine/any_serializer.py:30
     28 from google.cloud.aiplatform import base
     29 from google.cloud.aiplatform.utils import gcs_utils
---> 30 from vertexai.preview._workflow.serialization_engine import (
     31     serializers,
     32     serializers_base,
     33 )
     34 from vertexai.preview._workflow.shared import (
     35     supported_frameworks,
     36 )
     38 from packaging import requirements

File ~/.local/lib/python3.10/site-packages/vertexai/preview/_workflow/serialization_engine/serializers.py:52
     49 SERIALIZATION_METADATA_FRAMEWORK_KEY = "framework"
     51 try:
---> 52     from tensorflow import keras
     53     import tensorflow as tf
     55     KerasModel = keras.models.Model

File /opt/conda/lib/python3.10/site-packages/tensorflow/__init__.py:37
     34 import sys as _sys
     35 import typing as _typing
---> 37 from tensorflow.python.tools import module_util as _module_util
     38 from tensorflow.python.util.lazy_loader import LazyLoader as _LazyLoader
     40 # Make sure code inside the TensorFlow codebase can use tf2.enabled() at import.

File /opt/conda/lib/python3.10/site-packages/tensorflow/python/__init__.py:37
     29 # We aim to keep this file minimal and ideally remove completely.
     30 # If you are adding a new file with @tf_export decorators,
     31 # import it in modules_with_exports.py instead.
     32
     33 # go/tf-wildcard-import
     34 # pylint: disable=wildcard-import,g-bad-import-order,g-import-not-at-top
     36 from tensorflow.python import pywrap_tensorflow as _pywrap_tensorflow
---> 37 from tensorflow.python.eager import context
     39 # pylint: enable=wildcard-import
     40
     41 # Bring in subpackages.
     42 from tensorflow.python import data

File /opt/conda/lib/python3.10/site-packages/tensorflow/python/eager/context.py:28
     25 from absl import logging
     26 import numpy as np
---> 28 from tensorflow.core.framework import function_pb2
     29 from tensorflow.core.protobuf import config_pb2
     30 from tensorflow.core.protobuf import coordination_config_pb2

File /opt/conda/lib/python3.10/site-packages/tensorflow/core/framework/function_pb2.py:16
     11 # @@protoc_insertion_point(imports)
     13 _sym_db = _symbol_database.Default()
---> 16 from tensorflow.core.framework import attr_value_pb2 as tensorflow_dot_core_dot_framework_dot_attr__value__pb2
     17 from tensorflow.core.framework import node_def_pb2 as tensorflow_dot_core_dot_framework_dot_node__def__pb2
     18 from tensorflow.core.framework import op_def_pb2 as tensorflow_dot_core_dot_framework_dot_op__def__pb2

File /opt/conda/lib/python3.10/site-packages/tensorflow/core/framework/attr_value_pb2.py:16
     11 # @@protoc_insertion_point(imports)
     13 _sym_db = _symbol_database.Default()
---> 16 from tensorflow.core.framework import tensor_pb2 as tensorflow_dot_core_dot_framework_dot_tensor__pb2
     17 from tensorflow.core.framework import tensor_shape_pb2 as tensorflow_dot_core_dot_framework_dot_tensor__shape__pb2
     18 from tensorflow.core.framework import types_pb2 as tensorflow_dot_core_dot_framework_dot_types__pb2

File /opt/conda/lib/python3.10/site-packages/tensorflow/core/framework/tensor_pb2.py:16
     11 # @@protoc_insertion_point(imports)
     13 _sym_db = _symbol_database.Default()
---> 16 from tensorflow.core.framework import resource_handle_pb2 as tensorflow_dot_core_dot_framework_dot_resource__handle__pb2
     17 from tensorflow.core.framework import tensor_shape_pb2 as tensorflow_dot_core_dot_framework_dot_tensor__shape__pb2
     18 from tensorflow.core.framework import types_pb2 as tensorflow_dot_core_dot_framework_dot_types__pb2

File /opt/conda/lib/python3.10/site-packages/tensorflow/core/framework/resource_handle_pb2.py:16
     11 # @@protoc_insertion_point(imports)
     13 _sym_db = _symbol_database.Default()
---> 16 from tensorflow.core.framework import tensor_shape_pb2 as tensorflow_dot_core_dot_framework_dot_tensor__shape__pb2
     17 from tensorflow.core.framework import types_pb2 as tensorflow_dot_core_dot_framework_dot_types__pb2
     20 DESCRIPTOR = _descriptor.FileDescriptor(
     21   name='tensorflow/core/framework/resource_handle.proto',
     22   package='tensorflow',
   (...)
     26   ,
     27   dependencies=[tensorflow_dot_core_dot_framework_dot_tensor__shape__pb2.DESCRIPTOR,tensorflow_dot_core_dot_framework_dot_types__pb2.DESCRIPTOR,])

File /opt/conda/lib/python3.10/site-packages/tensorflow/core/framework/tensor_shape_pb2.py:36
     13 _sym_db = _symbol_database.Default()
     18 DESCRIPTOR = _descriptor.FileDescriptor(
     19   name='tensorflow/core/framework/tensor_shape.proto',
     20   package='tensorflow',
   (...)
     23   serialized_pb=_b('\n,tensorflow/core/framework/tensor_shape.proto\x12\ntensorflow\"z\n\x10TensorShapeProto\x12-\n\x03\x64im\x18\x02 \x03(\x0b\x32 .tensorflow.TensorShapeProto.Dim\x12\x14\n\x0cunknown_rank\x18\x03 \x01(\x08\x1a!\n\x03\x44im\x12\x0c\n\x04size\x18\x01 \x01(\x03\x12\x0c\n\x04name\x18\x02 \x01(\tB\x87\x01\n\x18org.tensorflow.frameworkB\x11TensorShapeProtosP\x01ZSgithub.com/tensorflow/tensorflow/tensorflow/go/core/framework/tensor_shape_go_proto\xf8\x01\x01\x62\x06proto3')
     24 )
     29 _TENSORSHAPEPROTO_DIM = _descriptor.Descriptor(
     30   name='Dim',
     31   full_name='tensorflow.TensorShapeProto.Dim',
     32   filename=None,
     33   file=DESCRIPTOR,
     34   containing_type=None,
     35   fields=[
---> 36     _descriptor.FieldDescriptor(
     37       name='size', full_name='tensorflow.TensorShapeProto.Dim.size', index=0,
     38       number=1, type=3, cpp_type=2, label=1,
     39       has_default_value=False, default_value=0,
     40       message_type=None, enum_type=None, containing_type=None,
     41       is_extension=False, extension_scope=None,
     42       serialized_options=None, file=DESCRIPTOR),
     43     _descriptor.FieldDescriptor(
     44       name='name', full_name='tensorflow.TensorShapeProto.Dim.name', index=1,
     45       number=2, type=9, cpp_type=9, label=1,
     46       has_default_value=False, default_value=_b("").decode('utf-8'),
     47       message_type=None, enum_type=None, containing_type=None,
     48       is_extension=False, extension_scope=None,
     49       serialized_options=None, file=DESCRIPTOR),
     50   ],
     51   extensions=[
     52   ],
     53   nested_types=[],
     54   enum_types=[
     55   ],
     56   serialized_options=None,
     57   is_extendable=False,
     58   syntax='proto3',
     59   extension_ranges=[],
     60   oneofs=[
     61   ],
     62   serialized_start=149,
     63   serialized_end=182,
     64 )
     66 _TENSORSHAPEPROTO = _descriptor.Descriptor(
     67   name='TensorShapeProto',
     68   full_name='tensorflow.TensorShapeProto',
   (...)
    100   serialized_end=182,
    101 )
    103 _TENSORSHAPEPROTO_DIM.containing_type = _TENSORSHAPEPROTO

File ~/.local/lib/python3.10/site-packages/google/protobuf/descriptor.py:553, in FieldDescriptor.__new__(cls, name, full_name, index, number, type, cpp_type, label, default_value, message_type, enum_type, containing_type, is_extension, extension_scope, options, serialized_options, has_default_value, containing_oneof, json_name, file, create_key)
    547 def __new__(cls, name, full_name, index, number, type, cpp_type, label,
    548             default_value, message_type, enum_type, containing_type,
    549             is_extension, extension_scope, options=None,
    550             serialized_options=None,
    551             has_default_value=True, containing_oneof=None, json_name=None,
    552             file=None, create_key=None):  # pylint: disable=redefined-builtin
--> 553   _message.Message._CheckCalledFromGeneratedFile()
    554   if is_extension:
    555     return _message.default_pool.FindExtensionByName(full_name)

TypeError: Descriptors cannot be created directly.
If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
If you cannot immediately regenerate your protos, some other possible workarounds are:
 1. Downgrade the protobuf package to 3.20.x or lower.
 2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).

More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The message on the top of the User-Managed Notebooks (request to migrate to new Workbench instance - below) confirms that issue is the same as #363  - and as a result of Qwicklabs (for me GSP1151) is still using the old VMs.

The new Workbench Instances bring the features of Managed and User-Managed Notebooks into a single offering. (Migrate)

Seems that forcing the version as second cell in each of the QwickLabs managed notebooks resolves the issue.
!pip install protobuf==3.19.3

@OWLYone Thanks for reporting this issue, I made #432 to implement your workaround.
@polong-lin I made b/328420624 to report this to the Qwiklabs team.


tweak specimen collection device def

Using "device" rather than "container" in def.

Reviewed on April 24th OBI call.


Error in the code

Hi,
Lines 841-846 in multiple_features.py reads:
        self.xyz_mean = torch.mean(self.patch_xyz_lib)
        self.xyz_std = torch.std(self.patch_rgb_lib)
        self.rgb_mean = torch.mean(self.patch_xyz_lib)
        self.rgb_std = torch.std(self.patch_rgb_lib)
        self.fusion_mean = torch.mean(self.patch_xyz_lib)
        self.fusion_std = torch.std(self.patch_rgb_lib)

Is this correct? It looks like an error.
Thanks

yes, I have same question。

This code mainly does scaling on the values of the data, because there is some instability in the image edge values of the XYZ data, so we use a uniform scaling factor and mean value. Maintaining the way the code is written works better.


feat(intersection): use planned velocity from upstream modules (#5156)

Description
右折時にwalkwayでの停止がある場合はそれを見越してintersectionで停止する機能
Related links
https://tier4.atlassian.net/browse/RT0-29263 のチケットに対応
prediction時間を伸ばせば

https://tier4.atlassian.net/browse/RT0-29263
https://tier4.atlassian.net/browse/RT0-29263

でORがなくなることが期待される
launcher PR: https://github.com/tier4/autoware_launch.x2/pull/459
Tests performed

Notes for reviewers

Interface changes

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@mkuri
intersectionでcrosswalkやwalkwayを考慮して衝突計算する機能をマージしました
ロジックはシンプルで、

intersectionで入力経路の停止点を見て自車の動きを予想することで、crosswalkやwalkwayを考慮した衝突計算を可能に
launcherの順番的にcrosswalkやwalkwayはintersectionの前に呼ばれる


Singleton DefaultContractResolver for JsonSerializerSettingsProvider.CreateSerializerSettings

Today each call to JsonSerializerSettingsProvider.CreateSerializerSettings() will return a new settings instance with a new DefaultContractResolver instance.
https://github.com/aspnet/Mvc/blob/master/src/Microsoft.AspNetCore.Mvc.Formatters.Json/JsonSerializerSettingsProvider.cs
It would be better for performance and memory usage if there was a static singleton DefaultContractResolver and the new settings returned from CreateSerializerSettings returned that singleton. Slow reflection logic is cached by the resolver and sharing it means it will be cached once
e.g.
public static class JsonSerializerSettingsProvider
{
    private const int DefaultMaxDepth = 32;

    // return shared resolver by default for perf so slow reflection logic is cached once
    // developers can set their own resolver after the settings are returned if desired
    private static readonly DefaultContractResolver SharedResolver = new DefaultContractResolver
    {
        NamingStrategy = new CamelCaseNamingStrategy(),
    };

    /// <summary>
    /// Creates default <see cref="JsonSerializerSettings"/>.
    /// </summary>
    /// <returns>Default <see cref="JsonSerializerSettings"/>.</returns>
    public static JsonSerializerSettings CreateSerializerSettings()
    {
        return new JsonSerializerSettings
        {
            ContractResolver = SharedResolver,

            MissingMemberHandling = MissingMemberHandling.Ignore,

            // Limit the object graph we'll consume to a fixed depth. This prevents stackoverflow exceptions
            // from deserialization errors that might occur from deeply nested objects.
            MaxDepth = DefaultMaxDepth,

            // Do not change this setting
            // Setting this to None prevents Json.NET from loading malicious, unsafe, or security-sensitive types
            TypeNameHandling = TypeNameHandling.None,
        };
    }
}

Why does this need to be baked in? Why not just cache a static in your application?

Because I noticed that it was being recommended to devs to use that call when creating serializer settings for use with ASP.NET Core
https://github.com/aspnet/Mvc/issues/4562#issuecomment-226190759

@JamesNK is the CamelCaseNamingStrategy immutable?

No, and neither is DefaultContractResolver but the type exposed by JsonSerializerSettings is IContractResolver which just has a single method on it.
To get into trouble with modifying them a dev would need to actively cast the IContractResolver to DefaultContractResolver and then start fiddling with properties.
If they wanted to change the resolver on the settings it is much easier for them to just assign a new one, i.e.
var settings = JsonSerializerSettingsProvider.CreateSerializerSettings();
settings.ContractResolver = new DefaultContractResovler
{
    NamingStrategy = new SnakeCaseNamingStrategy()
};

No, and neither is DefaultContractResolver but the type exposed by JsonSerializerSettings is IContractResolver which just has a single method on it.

Right, I'm not a fan of this... We could just recommend they do the right thing and store a static that they own. It also won't suddenly start affecting every where that calls this (if they did modify the value).

People want to call JsonSerializerSettingsProvider.CreateSerializerSettings() multiple times because they want to have different settings for JsonInputFormatter and JsonOutputFormatter.
The perf hit of using a new contract resolver isn't insignificant - https://aspnetwebstack.codeplex.com/workitem/2092

We merged https://github.com/aspnet/Mvc/pull/6363. Thanks!


Faucet kehabisan DOGE

Ini saya lampirkan error lognya

--------------------- 2018-02-12 17:25:30.009731259 +0700 WIB m=+11758.989597640

Autoclaim Faucet

Get Dogecoin
CoinHub
My Doggy

The faucet is out of this particular currency. Want to try another one?(A few currencies depend on the exchange, the faucet will usually be re-filled once shogunnʼs ‘buy’ orders are filled.) (If you are really impatient, perhaps someone will /tip shogunn some DOGE?)(I would put a little “faucet balance” widget on the main page, but that would currently result in a TON of API requests…)

Do not bookmark this page! Use http://autoclaim.win instead. (If the claim URL changes and you visit this page directly, you might be mistaken for a bot and banned.)

Cariin list web yang serupa. Nanti diupdate.

oke om

Lebih efisien kalo nyarinya pake dork:
intext:"This faucet requires your address to be linked to a FaucetHUB account"

oke gan,
btw yang getdogecoin.website kalau di versi 102 jalan normal, tapi error di 103

Coba kirim SS perbedaannya.
Pada tanggal 15 Feb 2018 11.45 AM, "felangga"<EMAIL_ADDRESS>menulis:

oke gan,
btw yang getdogecoin.website kalau di versi 102 jalan normal, tapi error
di 103
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dwisiswant0/Faucet-DOGE-Bot/issues/4#issuecomment-365824254,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYo_5OCqzOt4I2wLO_T3TTivn3O4mg9dks5tU7ZOgaJpZM4SB9Qu
.

Errornya gini yang 103

--------------------- 2018-02-15 11:49:35.9960673 +0700 +07 m=+18.679051301

400 Bad request

Your browser sent an invalid request.


Adding linker flags to reduce compiled size by 68-75%, based on platform.

This cuts to built size of the Daytona docker image from ~18.3mb to ~4.9mb, a savings of 73%. Accomplished via use of ldflags (-s -w) passed during the build, and compressing the built artifact with upx.


Logout

How to get logout after logging in ?

I looked up Tumblr's official documentation. It seems there is no provision to logout a user from APIs. The best you can do is delete the tokens you received.
I'll see what I can do for this in the next build.

No documentation of any logout API or invalidating auth tokens on Tumblr or Jumblr. Lost cause. Closing issue.


Give more informative messages for GQL errors

This gives more insight into the most common issues when using the GQL query feature.

https://ocd.appscale.com:8080/job/Daily Build/4961/


Fix your folder structure

[x] Make sure no unnecessary files are commited
[x] put your main project in the root folder instead of in a subfolder
[x] Make a decent README.md with detailed instructions on how to use the code

Should be done or almost done

Should .idea folder be in there? I think not?


fix(pss): make sending PSS messages more efficient

a minor improvement on pss trojan mining

code cleanup
using errgroup
change to bigendian
fix for the parity bit

This change is

@zelig can you explain why and how this is improving things? (and to which degree?)

before:
growlie@growlie-strikes-back ~/go/src/github.com/ethersphere/bee/pkg/pss ±master⚡ » go test -v -bench=. -run Bench -benchmem -benchtime 5s
goos: linux
goarch: amd64
pkg: github.com/ethersphere/bee/pkg/pss
cpu: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
BenchmarkWrap
BenchmarkWrap/length:1,depth:1
BenchmarkWrap/length:1,depth:1-4         	     187	  33675828 ns/op	18788199 B/op	  104356 allocs/op
BenchmarkWrap/length:4,depth:1
BenchmarkWrap/length:4,depth:1-4         	     622	   9896097 ns/op	 5419940 B/op	   30071 allocs/op
BenchmarkWrap/length:16,depth:1
BenchmarkWrap/length:16,depth:1-4        	    1520	   3850104 ns/op	 2013067 B/op	   11114 allocs/op
BenchmarkWrap/length:16,depth:2
BenchmarkWrap/length:16,depth:2-4        	      30	 757000467 ns/op	425943036 B/op	 2366465 allocs/op
BenchmarkWrap/length:64,depth:2
BenchmarkWrap/length:64,depth:2-4        	      38	 145133468 ns/op	81234541 B/op	  451305 allocs/op
BenchmarkWrap/length:256,depth:2
BenchmarkWrap/length:256,depth:2-4       	     166	  37935671 ns/op	21093620 B/op	  117162 allocs/op
BenchmarkWrap/length:256,depth:3
BenchmarkWrap/length:256,depth:3-4       	       1<PHONE_NUMBER> ns/op<PHONE_NUMBER> B/op	18111114 allocs/op
BenchmarkWrap/length:4096,depth:3
BenchmarkWrap/length:4096,depth:3-4      	      15	 591351344 ns/op	242435498 B/op	 1347379 allocs/op
BenchmarkWrap/length:16384,depth:3
BenchmarkWrap/length:16384,depth:3-4     	      40	 223228374 ns/op	74415670 B/op	  413806 allocs/op
PASS
ok  	github.com/ethersphere/bee/pkg/pss	106.122s

after:
growlie@growlie-strikes-back ~/go/src/github.com/ethersphere/bee/pkg/pss ±(dfccf46b...)⚡ » go test -v -bench=. -run Bench -benchmem -benchtime 5s
goos: linux
goarch: amd64
pkg: github.com/ethersphere/bee/pkg/pss
cpu: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
BenchmarkWrap
BenchmarkWrap/length:1,depth:1
BenchmarkWrap/length:1,depth:1-4         	     232	  27393762 ns/op	19365715 B/op	  107572 allocs/op
BenchmarkWrap/length:4,depth:1
BenchmarkWrap/length:4,depth:1-4         	     844	   7616651 ns/op	 5263813 B/op	   29211 allocs/op
BenchmarkWrap/length:16,depth:1
BenchmarkWrap/length:16,depth:1-4        	    1869	   3619230 ns/op	 1997974 B/op	   11042 allocs/op
BenchmarkWrap/length:16,depth:2
BenchmarkWrap/length:16,depth:2-4        	      13	 435784661 ns/op	261811824 B/op	 1454861 allocs/op
BenchmarkWrap/length:64,depth:2
BenchmarkWrap/length:64,depth:2-4        	      61	 113410167 ns/op	75256698 B/op	  418116 allocs/op
BenchmarkWrap/length:256,depth:2
BenchmarkWrap/length:256,depth:2-4       	     206	  30770748 ns/op	18623767 B/op	  103452 allocs/op
BenchmarkWrap/length:256,depth:3
BenchmarkWrap/length:256,depth:3-4       	       1<PHONE_NUMBER> ns/op<PHONE_NUMBER> B/op	22129769 allocs/op
BenchmarkWrap/length:4096,depth:3
BenchmarkWrap/length:4096,depth:3-4      	       9	 956932108 ns/op	326600746 B/op	 1815988 allocs/op
BenchmarkWrap/length:16384,depth:3
BenchmarkWrap/length:16384,depth:3-4     	      26	 264735541 ns/op	85486048 B/op	  475630 allocs/op
PASS
ok  	github.com/ethersphere/bee/pkg/pss	80.735s

pkg/pss/trojan.go, line 248 at r1 (raw file):
Previously, zelig (Viktor Trón) wrote…
this was only to trigger the context cancel to terminate the other routines, but i guess i should just use a cancel on the context right?

Context cancellation will return error on eg.Wait from the next routine. If we dont care about the errors from the other routines once the first one is done, we should return nil on <-ctx.Done(). Although I dont think errorgroup usage give any advantages here apart from context semantics

pkg/pss/trojan.go, line 248 at r1 (raw file):
Previously, zelig (Viktor Trón) wrote…
Context cancellation will return error on eg.Wait from the next routine. If we dont care about the errors from the other routines once the first one is done, we should return nil on <-ctx.Done(). Although I dont think errorgroup usage give any advantages here apart from context semantics

Agree, we can also specifically check if the returned error is the context.Canceled error and ignore it in the it is.

@zelig pss integration tests are failing

seems to be OK for now. restarted the build several times. let's monitor the situation


Add missing PS and cli commands to register Microsoft.HybridCompute p…

…rovider

@nachoalonsoportillo : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@anosov1960 Sasha, could you please take a look at the file changes tab in this public PR? If you approve the changes, you can sign off. If you have feedback, note it in the comments of the PR.
@nachoalonsoportillo Thanks for this suggested change, and apologies for the delay.


Debugger mode problem in interaction with browsers in latest version 1.95

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:  1.95
OS Version: Windows 10 Enterprise

Steps to Reproduce:
1.I am going to try to explain in words the error that I received starting with the latest version 1.95, it caused some type of conflict in debugger mode with any open browser, as soon as I put a breakpoint in the vscode in any file, the The browser would freeze, the website would not load without having any type of error on the screen when starting the debugger mode, if I removed the breakpoint initially I started the debugger mode it seemed that the operation was normal but when It stopped at the breakpoint and moved on to the next one. I tried to interact with some element on the screen, the browser froze again, going back down to version 1.94.2 now works.
I tried to delete browser cache, visual cache, delete visual delete browser, and I couldn't solve it, I don't know if it is a problem that only affects me in the browser or it could be a general problem for other users

I'm having the same problem with revision 1.95.1

Thank you very much for the review, I don't know what could be happening, later I will update the version again to see if it persists

Same bug here. MacOS 15, VsCode 1.95.1
After starting debug session, chrome opens but page hangs loading forever.

Probably https://github.com/microsoft/vscode/issues/232651 which will be fixed in upcoming 1.95.2 later this week.

I confirm, same problem here with 1.95.1 under both Linux and Windows.
This is used to work for debugging a NextJs 14 app router project, now Chrome randomly hangs loading forever:
launch.json

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Next.js: debug full stack",
      "type": "node-terminal",
      "request": "launch",
      "command": "pnpm run dev",
      "skipFiles": [
        "${workspaceFolder}/<node_internals>/**",
        "${workspaceFolder}/node_modules/**"
      ],
      "serverReadyAction": {
        "action": "debugWithChrome",
        "killOnServerStop": true,
        "pattern": "- Local:.+(https?://.+)",
        "uriFormat": "%s",
        "webRoot": "${workspaceFolder}"
      }
    }
  ]
}

Temporary workaround: the issue goes away rolling back to 1.94.2.

https://github.com/microsoft/vscode/issues/232651#issuecomment-2450365808

Thank you guys


Added scancodes for launch keys

@freerdp-bot test

@freerdp-bot test

Should we consider that fort stable ?

@hardening best open a new request for backport issue and reference all the ones you´d like


add logic to query real go get vcs url

you might want to run some thorough tests, I tested against a few Gopkg.lock files containing various google libs and it seems to work

Looks good to me. I'll let @qknight do the merging if he's fine with the PR, as he's the project owner.

amazing! thank you guys!


extension issue

Type: Bug
hi sir ,
i hope everyone will be fine my problem is that the extension of python is not installing in my vs studio please solve my problem.
thanks
VS Code version: Code 1.71.2 (74b1f979648cc44d385a2286793c226e611f59e7, 2022-09-14T21:03:37.738Z)
OS version: Windows_NT x64 6.3.9600
Modes:
Sandboxed: No

@MURTAZAJAN1122 Can you please share more details about this issue (any error messages)

Hi @MURTAZAJAN1122  Since we haven't heard back from you in a while, we assume the issue is resolved. Feel free to create a new ticket if you have any other issues.

Error in Installation of python extension
On Thu, Oct 6, 2022, 6:19 PM Muhammad Murtaza @.***>
wrote:

No, it has not.
On Thu, Oct 6, 2022, 6:13 PM madhurivadaligithub @.***>
wrote:

Hi @MURTAZAJAN1122 https://github.com/MURTAZAJAN1122 Since we haven't
heard back from you in a while, we assume the issue is resolved. Feel free
to create a new ticket if you have any other issues.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vsmarketplace/issues/485#issuecomment-1270023693,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3JAVYPC5KOUHIWNGFGBEOLWB3GBJANCNFSM6AAAAAAQV7EWPM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Can you share more details about the error you are getting?
A screenshot of the error or recording of your issue would help us better understand the issue.

I an already shared.
On Thu, Oct 6, 2022, 6:22 PM Sai Kanth @.***> wrote:

Can you share more details about the error you are getting?
A screenshot of the error or recording of your issue would help us better
understand the issue.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vsmarketplace/issues/485#issuecomment-1270037639,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3JAVYL3VFCBOACPCQKCKI3WB3G75ANCNFSM6AAAAAAQV7EWPM
.
You are receiving this because you were mentioned.Message ID:
@.***>

No response.
On Thu, Oct 6, 2022, 6:47 PM Muhammad Murtaza @.***>
wrote:

Is there any solution of this issue?
On Thu, Oct 6, 2022, 6:33 PM Muhammad Murtaza @.***>
wrote:

I an already shared.
On Thu, Oct 6, 2022, 6:22 PM Sai Kanth @.***> wrote:

Can you share more details about the error you are getting?
A screenshot of the error or recording of your issue would help us
better understand the issue.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vsmarketplace/issues/485#issuecomment-1270037639,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3JAVYL3VFCBOACPCQKCKI3WB3G75ANCNFSM6AAAAAAQV7EWPM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Closing until issue has reproducable steps.


Make Ollama available on Chocolatey

The Windows installers works great, but requires that I manually download/update it from the ollama website. Would it be possible, probably when the Windows version has matured some more, to add ollama to Chocolatey? That will probabably aid in making this an (even) easier to install package on Windows.

No, I'd rather have this on winget

I understand winget is the supported Windows installation method, but at the moment it seems chocolatey has a larger package repository (10k vs 6k on winget) and for example Ansible supports choco and not winget due to some issue between Windows Server 2022 and winget.
Also, is this an either/or feature? I don't know anything about maintaining packages on winget/chocolatey, but perhaps the package can be published on both winget and chocolatey?


feat: add new list(banner,editorchoice) and adjust field

according to the document adjust fields and lists

new list: Specialfeature Editor choice, Job Banner, event Banner, resource Banner, home page Banner
new field: storyType(post), section(SpecialfeatureList), topSpecialfeature(SpecialfeatureList)
rm field: subtitle(post), isTop(event), banner(event)

test slack notification


Implement SetLastError DllImport flag functionality

Call PInvokeMarshal.SaveLastWin32Error after the P/Invoke call to ensure
the last error is saved in thread local variable which can be later
accessed through PInvokeMarshal.GetLastWin32Error.
Additionally, I have rename ParameterAttributes to
ParameterMetadataAttributes to avoid the confusion with
System.Reflection.ParameterAttributes.
This change also makes sure PInvoke works on Unix and also get rids of
build warning on windows.
@jkotas @yizhang82 @MichalStrehovsky

Can you also update MarshalHelpers.IsStubRequred to check for the SetLastError flag?
(To make sure we don't treat methods with simple signatures that have SetLastError as not requiring a marshalling stub.)

LGTM modulo last few comments. Thanks!


🪲 Predicate pushdowns into JOINs don't appear to be working

TPCH query 08
select
    nation,
    o_year,
    sum(amount) as sum_profit
from
    (
        select
            n_name as nation,
            year(o_orderdate) as o_year,
            l_extendedprice * (1 - l_discount) - ps_supplycost * l_quantity as amount
        from
            data.tpch.part,
            data.tpch.supplier,
            data.tpch.lineitem,
            data.tpch.partsupp,
            data.tpch.orders,
            data.tpch.nation
        where
            s_suppkey = l_suppkey
            and ps_suppkey = l_suppkey
            and ps_partkey = l_partkey
            and p_partkey = l_partkey
            and o_orderkey = l_orderkey
            and s_nationkey = n_nationkey
            and p_name like '%plum%'
    ) as profit
group by
    nation,
    o_year
order by
    nation,
    o_year desc;

pre-optimization
└─ EXIT
   └─ ORDER BY (nation, o_year DESC)
      └─ PROJECT (nation, o_year, SUM(amount))
         └─ AGGREGATE (SUM(amount)) GROUP BY (nation, o_year)
            └─ SUBQUERY AS profit
               └─ PROJECT (nation, YEAR(o_orderdate), l_extendedprice * (1 - l_discount) - ps_supplycost * l_quantity)
                  └─ FILTER (s_suppkey = l_suppkey AND ps_suppkey = l_suppkey AND ps_partkey = l_partkey AND p_partkey = l_partkey AND o_orderkey = l_orderkey AND s_nationkey = n_nationkey AND p_name LIKE '%plum%')
                     └─ CROSS JOIN
                        ├─ SCAN (data.tpch.part)
                        ├─ SCAN (data.tpch.supplier)
                        ├─ SCAN (data.tpch.lineitem)
                        ├─ SCAN (data.tpch.partsupp)
                        ├─ SCAN (data.tpch.orders)
                        └─ SCAN (data.tpch.nation)

post optimization
└─ EXIT
   └─ ORDER BY (nation, o_year)
      └─ PROJECT (SUM(amount), nation, o_year)
         └─ AGGREGATE (SUM(amount)) GROUP BY (nation, o_year)
            └─ SUBQUERY AS profit
               └─ PROJECT (YEAR(o_orderdate), l_extendedprice * (1 - l_discount) - ps_supplycost * l_quantity, nation)
                  └─ FILTER (p_name LIKE '%plum%')
                     └─ FILTER (s_nationkey = n_nationkey)
                        └─ FILTER (o_orderkey = l_orderkey)
                           └─ FILTER (p_partkey = l_partkey)
                              └─ FILTER (ps_partkey = l_partkey)
                                 └─ FILTER (ps_suppkey = l_suppkey)
                                    └─ FILTER (s_suppkey = l_suppkey)
                                       └─ CROSS JOIN
                                          ├─ SCAN (data.tpch.part) [p_partkey, p_name]
                                          ├─ SCAN (data.tpch.supplier) [s_suppkey, s_nationkey]
                                          ├─ SCAN (data.tpch.lineitem) [l_orderkey, l_partkey, l_suppkey, l_quantity, l_extendedprice, l_discount]
                                          ├─ SCAN (data.tpch.partsupp) [ps_partkey, ps_suppkey, ps_supplycost]
                                          ├─ SCAN (data.tpch.orders) [o_orderkey, o_orderdate]
                                          └─ SCAN (data.tpch.nation) [n_nationkey, n_name]

the optimizer has pushed the projections to the SCANs, but has not pushed the predicates into the JOIN, maybe because it's a 6-way cross join.
Note this query ultimately fails after running for a few minutes because of the YEAR function call not handling null entries.

a simpler example:
SELECT * FROM $planets, $satellites WHERE mass = gm

creates this plan:
   └─ FILTER (mass = gm)
      └─ CROSS JOIN
         ├─ READ ($planets) [id, name, mass, diameter, density, gravity, escapeVelocity, rotationPeriod, lengthOfDay, distanceFromSun, perihelion, aphelion, orbitalPeriod, orbitalVelocity, orbitalInclination, orbitalEccentricity, obliquityToOrbit, meanTemperature, surfacePressure, numberOfMoons]
         └─ FILTER (id < 4)
            └─ READ ($satellites) [id, planetId, name, gm, radius, density, magnitude, albedo]


audio redirection by mp3 doesn't sound with mstsc Windows 10 RS3

mstsc on Windows 7 sounds.
Shell version: 6.3.9600
Control version: 6.3.9600
RDP 8.1

Windows 10 Insider Preview 1709 1705.1000 doesn't sound.
Shell version: 10.0.17025
Control version: 10.0.17025
RDP 10.5

Windows 10 1709 16299.19 doesn't sound.
Shell version: 10.0.16299
Control version: 10.0.16299
RDP 10.4

Maybe because of wave format config.
After Fall Creators Update, wave format became stricter.

After I changed g_bbuf_size 11520 -> 4096, it sounds but not smooth. Maybe g_bbuf_size is the problem but 4096 is not still a valid value.

You can user NeutrinoRDP or maybe FreeRDP to connect to MS server and only report MP3 audio and see what size it uses.  I don't think MP3 is like AAC where the compress block matters.

OK, I'll try it.

I've created a wiki page of audio formats. Windows don't seem to use MP3 when it works as an RDP server.
https://github.com/neutrinolabs/xrdp/wiki/Audio-formats-supported-by-Windows-as-a-RDP-Server

This is true , but mstsc still supports it since it relying on media
foundation api.
בתאריך יום ג׳, 5 בדצמ׳ 2017 ב-8:10 מאת metalefty<EMAIL_ADDRESS>
I've created a wiki page of audio formats. Windows don't seem to use MP3
when it works as an RDP server.
https://github.com/neutrinolabs/xrdp/wiki/Audio-formats-supported-by-Windows-as-a-RDP-Server
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/965#issuecomment-349206071,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADTH1L6y5t8fQGx0ngTZKhLwnPrMw2WBks5s9N5bgaJpZM4QyF8s
.

--
Idan Freiberg
PGP FP: 8108 7EC9 806E 4980 75F2  72B3 8AD3 2D04 337B 1F18

Yes, the result is Windows as the server. As the client, mstsc actually supports MP3 but I can't know the correct wave format values for MP3 by peeping in RDP communications to Windows.

Now it sounds on Windows 10 2004 build 19041.685.


searchHistory function bug

Hello @legastero
Thanks for amazing library that made our working easy.
When i call
const messages = await client.searchHistory({
				with: jid
			});

inside anywhere not work except after sendMessage method that works nice, how i can get messages list without click to send message

@legastero I figured out why it disconnects when i use it, i will close it, but anyway it happens sometime.


Please update the provider for .NET Core 3

The current provider has issues when using under .Net Core 3
System.TypeLoadException: Could not load type 'Microsoft.EntityFrameworkCore.Infrastructure.IDbContextOptionsExtensionWithDebugInfo' from assembly 'Microsoft.EntityFrameworkCore, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
   at IMSBackend.Models.CassandraDbContext.OnConfiguring(DbContextOptionsBuilder optionsBuilder)
   at Microsoft.EntityFrameworkCore.DbContext.get_InternalServiceProvider()
   at Microsoft.EntityFrameworkCore.DbContext.Microsoft.EntityFrameworkCore.Infrastructure.IInfrastructure<System.IServiceProvider>.get_Instance()
   at Microsoft.EntityFrameworkCore.Infrastructure.Internal.InfrastructureExtensions.GetService[TService](IInfrastructure`1 accessor)
   at Microsoft.EntityFrameworkCore.Infrastructure.AccessorExtensions.GetService[TService](IInfrastructure`1 accessor)
   at Microsoft.EntityFrameworkCore.Design.Internal.DbContextOperations.CreateContext(Func`1 factory)
   at Microsoft.EntityFrameworkCore.Design.Internal.DbContextOperations.CreateContext(String contextType)
   at Microsoft.EntityFrameworkCore.Design.Internal.MigrationsOperations.AddMigration(String name, String outputDir, String contextType)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.AddMigrationImpl(String name, String outputDir, String contextType)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.AddMigration.<>c__DisplayClass0_0.<.ctor>b__0()
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.<>c__DisplayClass3_0`1.<Execute>b__0()
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.Execute(Action action)
Could not load type 'Microsoft.EntityFrameworkCore.Infrastructure.IDbContextOptionsExtensionWithDebugInfo' from assembly 'Microsoft.EntityFrameworkCore, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'.

According to this, the provider has to be updated to support .NET Core 3

We are going to take a look ASAP.

The project has been migrated to DOTNET CORE 3.1 in the branch "release/2.0.0".

The project has been migrated to DOTNET CORE 3.1 in the release 2.0.0


Bug: enableZoom not working correctly with chartRegion

Hello,
When creating a line chart with regions and setting the enable-zoom property to true - on zoom functionality lines with regions don't zoom in, only the dots move. the lines without region works fine. Tested only on Chrome and FF.
Example:

To bad the graphics you provided are not visible. Any chance of providing an online example or something? Also need to check if this is a angular lib bug or a c3js bug.


React Router v4

Still a WIP (see the relevant discussion in #99).
So far, I've removed the old index.js and index.jsx files and added a /src directory containing the new components, store, and (somewhat opinionated) stylesheet. I haven't updated the /demo, package.json, or /test directories much yet as I'd like to discuss a bit more. I'll have to dig into the build process some more as well. I do think there may be some opportunities to simplify a few things as we go but I'd like to make sure that's ok before jumping into anything.
Once I've had a bit more time to jump into this I'll update with some thoughts. Until then, if anyone wants to dig into the /src files and try them out that'd be awesome. Definitely open to any feedback you all might have.

Thank you! I will be digging into it tomorrow! :)

@svenanders hey, do you have any updates on this PR? :)

It would be so nice to have this merged..
Plz bump!

@lucascarvalho @almirfilho what do you think of the proposed API for this? Did either of you try it out?
@svenanders definitely let me know your thoughts once you've had a chance to review. I think I'll have some time next week to help push this forward (e.g. add tests, update the demo, rewrite the readme, etc.).

Anything I could do to help move this along?

@MrLeebo have you had a chance to look at or play around with this? Just curious on your thoughts since I did talk this through with you in #99.
@gotdibbs and others -- I have some other updates/features once this starts moving along. And we would have to think about tests and documentation. I've been using this setup for a while now though with v4 and, while I've run into a few small quirks, it has worked really well overall.
@svenanders I'd love to move this along here but if you're unsure of the direction I'm happy to push it to a separate package as well.

@skipjack Honestly I haven't pursued this very much since that discussion. At work we opted to just keep using RRv3 for the foreseeable future since there doesn't seem to be a way to upgrade without refactoring nearly one hundred components in our app. I would be interested in seeing the Friends demo ported to this as a comparison, though.

I still think it's a good idea to do as we discussed earlier, that is, move the current master to a deprecated branch and use this PR as the base for a new master. I'm sorry I've been unable to work on this since before summer (feel really bad about this).

@skipjack The data object that is required as a props, what should be passed along here?

@svenanders it's basically a location descriptor with the addition of a title that can be any valid PropTypes.node. You can see it's used in the main component's render method.
I actually have some time this week to help push this forward and as I said I have a few updates/fixes to push. To @MrLeebo's point, I will add a "friends" example as well as a README.

@svenanders @MrLeebo added the README, working on the /demo now.

Ok started writing the demo -- though right now it only works on the webpack-dev-server. I still have some work to do on it which I'm hoping to finish up in the next couple days. @svenanders I feel a little bad tearing up the build processes but there were some things I couldn't figure out so I'm just trying to simplify the setup wherever I can.
This is slowly and surely becoming a rewrite of the whole repo, so I hope you don't mind. I'd be happy to discuss and re-integrate any processes I intentionally or unintentionally remove.

That's cool. I thought the Makefile-system I employed was meaningful back in the day, but I don't mind it being refactored into something more up to date. There's also a lot of unnecessary complexity in the current demo folder that I don't mind removing either. So yeah, go ahead, and know I'm very happy and thankful that you're spending time on this!

Ok pretty much finished the demo but there's still some more cleanup to do. Here's a quick screenshot:

I thought the Makefile-system I employed was meaningful back in the day, but I don't mind it being refactored into something more up to date. There's also a lot of unnecessary complexity in the current demo folder that I don't mind removing either. So yeah, go ahead, and know I'm very happy and thankful that you're spending time on this!

Ok great, and yeah no problem at all! I'll let you know when I feel like the whole thing is in a good place -- and once it's there I could use some help with testing (like the actual automated testing not just reviewing/discussing the API).

Ok @svenanders et al I think this is ready for a review...
Demo

npm start: Starts a webpack-dev-server for easy local development.
npm run build: Creates a deployable demo in /demo/dist.

Core

npm run build: Populates /dist with deployable files.
npm run release: Utilizes standard-version to automate changelog generation and versioning.

Before running the above commands, you'll have to run an npm install in both the root directory and /demo. I think this could be avoided with some tweaks to the root configs if people feel 2 package.json files are overkill. Aside from that, I did strip a lot out so we could start with a simpler base and then discuss adding things back in if necessary. I would highly recommend we stick with standard-version for releasing as it makes life a lot easier (cleaner commit history, automated changelog, automated semver-compliant versioning).
Anyway, excited to hear feedback and hopefully push this forward. I am starting to run out of bandwidth to work on this so hopefully some others may be able to step in and help with certain things after we discuss what's needed.

Wow! At first glance, this looks fantastic. The code looks clean and nice, and the important core functionality is all there. I'll be checking it out in depth when I have capacity later today, so I can understand everything that's going on and suggest some test cases.

I'll be checking it out in depth when I have capacity later today, so I can understand everything that's going on and suggest some test cases. You've done more work on this than could ever be expected, and I'm ready to step up to maintain your excellent work.

Thanks! And yeah definitely let me know if I can clarify anything...

Any updates for this pull request ?

+1 Waiting for V4 merge here!

Hi all! SORRY for taking forever. I've scoured and tested and I love this PR, and the only thing I've been waiting for is trying to add some content to this myself. HOWEVER, out of respect for @skipjack and all of you waiting, I can't delay this any longer, so here's what I'm doing: I'm moving the old code to a legacy branch, merging this wholesale and publishing this PR as the new main npm module (as 2.x), while keeping the old one available at 1.x

Awesome @svenanders, I'm interested to hear your thoughts on writing/adding tests! I guess the store could be tested in isolation but I don't have too much experience testing react components so I'm interested in what you think would be best.

Writing React component tests are pretty straightforward (at least nowadays), although I actually prefer to just the code logic and trust React to render it correctly. However, I think I'll go ahead and write up some tests using enzyme and chai-enzyme and publish is at as a PR for you to look at and comment on.

Writing React component tests are pretty straightforward (at least nowadays), although I actually prefer to just the code logic and trust React to render it correctly. However, I think I'll go ahead and write up some tests using enzyme and chai-enzyme and publish is at as a PR for you to look at and comment on.

Sounds great.
Also, looking through the issues, I think a bunch will be resolved by this PR (e.g. #108) though I'm not sure if you'd like to keep them open to support react-router v3. The nice think about this solution though is that if we remove the NavLink dependency, and instead let it be passed via props, the new components would actually work for v3 as well.

Wow, that's worth exploring. I have a site that's using this component and is sort of stuck on React Router 3, so I'll definitely check out this solution to see if I can't use this new version rather than the old one by passing this down as a prop!


Combined fixes

Pull Request Description
What issue does this change request address?
Closes #1785
What are the significant changes in functionality due to this change request?
Updates ray.
Fixes test to find windows conda defs.
Also removes Prescient warning when not needed.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[x] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Job Test CentOS 8 on 622d30d : invalidated by @joshua-cogliati-inl
Failed: Diff tests/framework/user_guide/ForwardSamplingStrategies/Grid

Job Test qsubs falcon on 622d30d : invalidated by @joshua-cogliati-inl
Very slow Set Python Environment

Job Test qsubs sawtooth on b199a0b : invalidated by @joshua-cogliati-inl
FAILED: Diff tests/cluster_tests/AdaptiveSobol/test_parallel_adaptive_sobol

Job Test qsubs falcon on b199a0b : invalidated by @joshua-cogliati-inl
FAILED: Timeout tests/cluster_tests/RavenRunsRaven/Code Timeout tests/cluster_tests/InternalParallel/test_interal_parallel_ext_model

Job Test CentOS 8 on df49ab9 : invalidated by @joshua-cogliati-inl
FAILED: Diff tests/framework/user_guide/ForwardSamplingStrategies/Grid

Job Test qsubs sawtooth on df49ab9 : invalidated by @joshua-cogliati-inl
FAILED: Diff tests/cluster_tests/RavenRunsRaven/Code Diff tests/cluster_tests/AdaptiveSobol/test_parallel_adaptive_sobol

Job Test qsubs sawtooth on df49ab9 : invalidated by @joshua-cogliati-inl
FAILED: Diff tests/cluster_tests/RavenRunsRaven/Code

Job Test qsubs sawtooth on df49ab9 : invalidated by @joshua-cogliati-inl
FAILED: Diff tests/cluster_tests/RavenRunsRaven/Code Diff tests/cluster_tests/AdaptiveSobol/test_parallel_adaptive_sobol

Job Test qsubs sawtooth on df49ab9 : invalidated by @joshua-cogliati-inl
conda env remove --name raven_libraries -y has taken over 3 hours.

Job Test qsubs sawtooth on df49ab9 : invalidated by @wangcj05
FAILED: Diff tests/cluster_tests/RavenRunsRaven/Code

@mandd @wangcj05 Changes made, and the tests have passed.

checklist is good, PR is good to be merged.