invoke sourceMappingURLPrefix every time

because some time we need change url prefix by file path

Coverage remained the same at 100.0% when pulling a1f5c8eca80cd436587e438a19d528e6776e6585 on bolasblack:sourceMappingURLPrefix-invoke-every-time into fb17a22d5e44922909baa157b1bc25a1b65492df on floridoo:master.

Coverage remained the same at 100.0% when pulling a1f5c8eca80cd436587e438a19d528e6776e6585 on bolasblack:sourceMappingURLPrefix-invoke-every-time into fb17a22d5e44922909baa157b1bc25a1b65492df on floridoo:master.

Coverage remained the same at 100.0% when pulling a1f5c8eca80cd436587e438a19d528e6776e6585 on bolasblack:sourceMappingURLPrefix-invoke-every-time into fb17a22d5e44922909baa157b1bc25a1b65492df on floridoo:master.


Proposal: a protocol to obtain Bearer access tokens for HTTP Authorization for the AJAX/API/bot use case

the example-workflow.md document leaves unspecified how an application or automatic client (like an in-browser AJAX client where no cookie exists or can be used, or a server-side application with its own WebID (like a bot)) obtains an access credential when presented with a 401 Unauthorized response from a resource server.
node-solid-server, oidc-op, and oidc-rp together address this case in a currently undocumented (experimental?) way, described in #24. summary: "a proof-of-possession token is manufactured by the client and presented directly as a bearer token".
i'd like to propose an alternative method that is more in line with the spirit of OAuth, and which also uses proof-of-possession.  i've (re)written a full protocol proposal at WebID HTTP Authorization Protocol.  highlights of this protocol and capabilities it enables include:

the client must sign a challenge chosen by the resource server to prove immediate possession of the private challenge key;
the server, rather than the client, chooses the validity period of the access token;
provides an extensible framework for obtaining access tokens using different authentication mechanisms (for example, the spec includes a method to authenticate and obtain a bearer token using WebID-TLS, but that's beyond the scope of this Issue);
an optional HTTP 302 redirect-based token delivery mode that can be used to establish an application identifier, especially in case the proposal at #23 is rejected or not widely implemented (or for WebID-TLS);
the server (or its authorization delegate) can choose the format/representation/length of the token, for example to fit in with existing authorization infrastructure or to work optimally in the server's implementation;
the server can revoke its own access tokens trivially;
the server can require (and manage/revoke) different access tokens for different protection spaces it may serve, consistent with HTTP authorization semantics -- these tokens could be generated and validated by different authorization subsystems running in the server and have independent lifetimes.

summary of the protocol (please see zenomt/webid-auth-protocol for a full description):

try to access restricted resource;
get 401 Unauthorized, and a WWW-Authenticate response header that includes a challenge nonce and a token-exchange endpoint URI;
create and sign a proof-of-possession token that includes the challenge nonce and the URI you were trying to access (and your OIDC identity token);
exchange the proof-token for a Bearer access token (with its own expiration time);
use this token in Authorization headers for requests to the same protection space, until it expires.

Thanks a lot for writing this up! It caused confusion and pain to me as well when starting to write a test suite. I think we need to fix this.

@sylvainlb This might be interesting to you

@zenomt When you say "the server, rather than the client, chooses the validity period of the access token;" Is the server the RS or the OP?

@jaxoncreed the resource server chooses the validity period of the access tokens it issues. the validity period of its access tokens could be shorter or longer than the validity period of the presented proof-tokens. the reasoning is: the access policy of the resource server is up to the resource server, not to the client or the client's OIDC Provider.

to be more precise, the access token is issued by the webid_pop_endpoint, which is the resource server's authorization server.  the resource server could be its own authorization server, or (in some deployments, like enterprise systems) the authorization server could be a centralized service to which multiple resource servers are coupled.
this separation is more obvious with the webid_tls_endpoint, where for it to be useful in the real world it needs to have a different origin than the resource server (so the server can ask for a client certificate).  the webid_tls_endpoint server could be a virtual host on the same actual server, or it could be a completely different server.

i struck out the "302 redirect" mode above as a "highlight" of the protocol (though it's still present). that mode isn't useful to establish an application identifier with the webid_pop_endpoint. i've modified the spec, including the Syntax, Operation, and Security Considerations sections to explain why.  also in the Security Considerations section is an explanation as to why you can't believe the Origin header for any Bearer-type authorization scheme, not just this one.

i've made a reference implementation in https://github.com/zenomt/webid-auth-nginx .

unfortunately the minutes from this morning's Solid Community call were lost, and i don't remember who asked about it, but i have added a sequence diagram for the WebID-OIDC access token case to the https://github.com/zenomt/webid-auth-protocol .

Great! It was @bblfish who asked "(Henry) Is there a sequence diagram as part of the spec?"

@zenomt - It can be helpful to ping the group for anyone who has personal IRC logs (as I would have, were I logged in to IRC at the time) ... or, if RRSAgent was present, to ping W3 admins for help locating the bot's log.  W3 admins can usually also help with processing anyone's IRC logs into minutes via the scripts.

Ah, I am always on, even if I'm not on present :-) But it seems it is in the minutes? Anything else that was lost?

i updated my full proposal based on https://github.com/solid/webid-oidc-spec/issues/12#issuecomment-502723430 which is a cleaner method of determining the appid from the id_token audience than i had originally proposed. i'm still proposing that the redirect_uri be the appid and that it is present in the id_token aud list.


feature remove reinterpret_cast , use assert_cast

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


WebApp - Add banner for token list page

Version test: https://47fe9cd2.subwallet-webapp.pages.dev/home/tokens/detail/DOT-Polkadot
Validation passed.

[ ] Do not show footer in token detail screen in case responsive

Actual: Open page on mobile device then click on Search button on header then observe the screen displayed


use canary spin to run tests

There is a database file committed to this PR.
Also, you can update the URL in the configuration action to canary.
That will continue to work and make things easier if we ever want to have cross platform actions.

Thanks for pointing that out, will make the change.


Feature request: Nested lists

I have been looking at several rich text editors for the past days, and I wanted to submit a feature request that I thought could be of use for your component; nested lists.
How to use:
When editing inside a list, press tab to add a list within the list. The list button in the toolbar will now change this child list, not the parent. If you're using an ordered list (1, 2, 3), the child list elements should by default be ordered (a, b, c). If you're using an unordered lists, the child elements should by default be unordered.
The html could look something like this:

First regular li

Second regular li

First child li

And should render like this:

First regular li
Second regular li

First child li

Let me know what you think!

Hi @kristofferlund
It's good idea.
It seems to be not hard to implement.

The 2.26.0 version has been updated.
If there is an issue, please register as a new issue.
Thank you.

@JiHong88 Would it be possible to parameterize this functionality?
Thank you.


how to train with laion-5b dataset?

If using large amounts of image data, how can the current reading efficiency be accelerated?

Just prepare the data in the normal way, set the type of each sample in JSON


[RFE] Handle VolumeAttachments explicitly to speed up failover

Based on the discussion at https://groups.google.com/g/medik8s/c/_esi9rj9mTU/m/_aGvInpSAgAJ
When a node suddenly dies, the pods using RWO volumes on it cannot be rescheduled, because of the multi-attach error. The VolumeAttachment object effectively locks the pod to the node and until it is removed, the volume cannot be rescheduled. This generally makes sense when the RWO volumes are local, but much less so for network-attached RWO volumes.
In any case, the flow currently is for the SBA mechanism to run it's course, removing the node from the cluster, which in turn eventually removes volumeattachments (or not, depending on settings and random gods of k8s API interconnections). This bring the potential downtime of a pod from a possible few seconds, to at least 5 minutes and more (the rescheduling pod retries at an exponentially growing retry timeouts as the reconciliation loop is set).
This RFE is about deleting the VolumeAttachments belonging to the removed node explicitly to avoid the huge delays and shorten the downtime of a workload.

Thanks for bringing this up @dyasny
We will explore volumeattachements and pods direct deletion in the near future as an alternative for node deletion

closing this as it was implemented in https://github.com/medik8s/poison-pill/pull/110


Review of the DeputyGuardianModule Proxy Change

Review of the DeputyGuardianModule Proxy Change
Introduce a proposal that will prevent to regenerate the PSPs and make some unnecessary changes to the guardian contract each time we update the DeputyGuardianModule code.
Date, Time and Duration
Wednesday, 9 October 2024 at 11 EDT, 20-30 minutes.
Design Doc
Additional Context
If the changes are accepted, we should also leverage this opportunity to make some other requested changes for Incident response improvements
Requested Attendees
@maurelian @tynes @ajsutton @smartcontracts

@Ethnical - Just posted on OP Stack calendar.  Please confirm that this looks good to you and I will close the ticket!✨

Thanks @op-aaron this is good :) We should also maybe add them on discord calendar to make sure contributors can join also.

Great!  Thanks for the quick check @Ethnical .  I need to check in with @tynes and some of the Discord folks to understand the policy around the Discord calendar.  Historically we have not put design reviews, stand-ups, or most of the events from the OP Stack calendar  on the Discord event calendar.  I'm not opposed but I want to understand why before duplicating the event manually as this can introduced "multiple source of truth" issues (i.e. if the time or recipients get changes, meeting link is bad, etc ...).
That said, if you feel it is important then I can request it be added.  Just let me know.  I believe the thinking is that the OP Stack calendar is a more open resources it is public and doesn't require an invite unlike the Discord server.   So this allows you to invite external (not joined to Discord) folks to the event vs. having it live in Discord.

@Ethnical - The policy is to only use the Discord events for the protocol office hours and direct folks to the public calendar for all other events like design reviews.  That said, I've asked the admin to add a link to the public cal in the events section to clarify that is where the majority of events live.  So, next time, someone will be able to click through to see the public cal with all events.
I'm going to close this issue for now since the event was posted but - as I said - if you feel it is critical to have this reflected in the Discord Events I can facilitate that for you 🙏

@op-aaron I forgot to answer back..
Yes make completely sense this is not mandatory to make this one for discord it was just a friendly reminder about it.
But that make completely sense to it.

@bobajeanjacques-op - Can you please upload the recording of this meeting to our youtube channel when you have a chance?
I've re-opened the ticket and assigned to you so please feel free to close once done.  Of course, please let me know if you have any questions or need any more info.  Thank you!
Meeting link: https://drive.google.com/file/d/1r8jcM19M9LC6KFbkg-P62IG1SytJq8eR/view?usp=drive_web
Title: Design Review of the DeputyGuardianModule Proxy Change
Description:
This design review meeting introduces a proposal to prevent the regeneration of the PSPs and unnecessary changes to the guardian contract each time we update the DeputyGuardianModule code.  If the changes are accepted, we should also leverage this opportunity to make some other requested changes for Incident response improvements
Please review the Design Doc for more information.

@op-aaron requested access!

Doh!  Sorry about that, I just shared with you @bobajeanjacques-op and will make sure I do this in advance next time.  Please let me know if you have any issues accessing the recording!

@amandaoptimist - JJ suggested that you might be able to help us with this request.  Can you please post the design meeting to OP youtube channel when you have a chance (not urgent).  I've included the info to use to post it above but please let me know if you have any questions.  Thank you!


cannot config integration

I'm a 2021 lynk&go 01 owner from China, I don't know whether Chinese version is different from yours or not, but I cannot config Lynk & Co Integration, it says Unknown error occurred. I'm mot sure is there any problem about my email adress, because in China, we log in lynk&go app using phone numbers, so we don't use email address to log in. If you have solutions, please let me know, thank you very much!

No they are different unfortunately


I made a fork, and cloned it to my PC and created my own Branch. I made…

… one comment in server.R. I use github desktop, but followed the general flow here: https://blog.scottlowe.org/2015/01/27/using-fork-branch-git-workflow/
Let's see how this goes...
So in the Pull Request window, it's not clear to me if you get to decide whether to keep my edit or whether it is merged automatically (eek!). I have the big green Create Pull Request button and "Able to merge. These branches can be automatially merged." which makes me think that Github is going to automatically accept my edit, instead of letting you decide. That seems a little sketchy, but I might be missing something... I'm going to try it and we can roll it back if necessary.

Looks like it gives you the decision-making authority! That's a relief!


Precompiling VectorizationBase errors in Ubuntu, julia 1.7.2

Hi! I get a precompilation error when importing VectorizationBase. Originally I got this error when trying to install DifferentialEquations.jl, but I reproduce the error just adding VectorizationBase. I can reproduce it with julia 1.7.2 or 1.6.5 in Ubuntu, Below the stacktrace (for julia 1.7.2, for 1.6.5 I get the same):
julia> using VectorizationBase
[ Info: Precompiling VectorizationBase [3d5dd08c-fd9d-11e8-17fa-ed2836048c2f]
ERROR: LoadError: UndefVarError: num_cache_levels not defined
Stacktrace:
 [1] include
   @ ./Base.jl:418 [inlined]
 [2] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId, UInt64}}, source::Nothing)
   @ Base ./loading.jl:1318
 [3] top-level scope
   @ none:1
 [4] eval
   @ ./boot.jl:373 [inlined]
 [5] eval(x::Expr)
   @ Base.MainInclude ./client.jl:453
 [6] top-level scope
   @ none:1
in expression starting at /home/ismael/.julia/packages/VectorizationBase/yDGcX/src/VectorizationBase.jl:1
ERROR: Failed to precompile VectorizationBase [3d5dd08c-fd9d-11e8-17fa-ed2836048c2f] to /home/ismael/.julia/compiled/v1.7/VectorizationBase/jl_voXyGg.
Stacktrace:
 [1] error(s::String)
   @ Base ./error.jl:33
 [2] compilecache(pkg::Base.PkgId, path::String, internal_stderr::IO, internal_stdout::IO, ignore_loaded_modules::Bool)
   @ Base ./loading.jl:1466
 [3] compilecache(pkg::Base.PkgId, path::String)
   @ Base ./loading.jl:1410
 [4] _require(pkg::Base.PkgId)
   @ Base ./loading.jl:1120
 [5] require(uuidkey::Base.PkgId)
   @ Base ./loading.jl:1013
 [6] require(into::Module, mod::Symbol)
   @ Base ./loading.jl:997

Any ideas? Thanks in advance!

This should be fixed soon https://github.com/JuliaRegistries/General/pull/55825

Thank you both for the very very fast reply! @lcontento's answer worked for me, in the meantime until it is fixed in general. Should I close this?

I can close it once I release a new version of VB that excludes the problematic CPUSummary versions.

Please let me know if you run into any more problems!


How using begin/end frame?

https://gitlab.com/0xtrzy/engine-tui/-/tree/master
How put text to screen using begin frame?
I must initialize some other function? Anybody can help me?
 rencache_begin_frame();
 rencache_draw_rect(male, czerwone);
 rencache_draw_text(foncik, "żółw", 14, 2, kolorek);
 rencache_end_frame();

(original comented https://gitlab.com/0xtrzy/engine-tui/-/blob/master/main.c )
I think a benchmark needs to be created to see which engine is the fastest

Meybe using glfw https://www.glfw.org/ ?


Aeon Labs support

Just wondering if this is an error, as the Aeon Labs door sensor is not currently showing up in Homebridge. Is there support for this device type? Also Aeon Labs multisensor only shows humidity, luminence, temperature, but not motion.
Thanks

I have a Fibaro multi sensor and I also only get luminance and temperature. I tried adding Homebridge.IsPrimary Homebridge.Service.Type:MotionSensor and Homebridge.Characteristic.Type:MotionDetected tags to the general purpose alarm device which makes it show up in Homebridge but without any readable value to indicate motion. Also temperature and luminance is now gone.

Hey @jsg4 , can you follow these instructions and attach your accessories and devices output?


alpine: 2.24 → 2.25

Motivation for this change
CVE-2021-38370
https://nvd.nist.gov/vuln/detail/CVE-2021-38370
Closes #138647
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.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.

/marvin opt-in
/status needs_reviewer


postcss-loader issues

Two users reported me the following error:
[09:50:26] Finished 'appsettings' after 3ms
WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration has an unknown property 'postcss'. These properties are valid:
   object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
   For typos: please correct them.
   For loader options: webpack 2 no longer allows custom properties in configuration.
     Loaders should be updated to allow passing options via loader options in module.rules.
     Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader:
     plugins: {
       new webpack.LoaderOptionsPlugin({
         // test: /\.xxx$/, // may apply this only for some modules
         options: {
           postcss: ...
         }
       })
     }
    at webpack

It seems that the latest webpack 2 beta is not compatible with the stable postcss-loader. aspnet-starter-kit have already fixed that issue. Could you please merge that commit?

Yes, same error.


[Bug] Using ${foo.bar} returns ${foo} if foo is not a container

cfg = OmegaConf.create(dict(foo=0, bug="${foo.bar}"))
print(cfg.bug)

The above code prints "0" while I would expect it to crash.
What puzzles me is that this behavior is actually tested right now:
def test_indirect_interpolation2() -> None:
    d = {
        "a": {"aa": 10},
        "b": "${a.aa}",
        "c": "${b.aa}",
    }

    cfg = OmegaConf.create(d)
    assert cfg.c == 10

This test doesn't make sense to me: accessing cfg.c should crash since b is equal to 10 so b.aa should be invalid. Am I missing something?

This looks like a bug in the test and in the code.
This makes more sense:
def test_indirect_interpolation2() -> None:
    d = {
        "a": {"aa": 10},
        "b": "${a.aa}",
        "c": "${b}",
    }

feel free to send a PR.


Update the freeze, clone and stamp BBEs

Purpose
Update the freeze, clone and stamp BBEs.

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-0.990.0@dc185b1). Click here to learn what that means.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##             release-0.990.0   #12831   +/-   ##
==================================================
  Coverage                   ?      60%
  Complexity                 ?      659
==================================================
  Files                      ?     2068
  Lines                      ?   101695
  Branches                   ?    12953
==================================================
  Hits                       ?    61024
  Misses                     ?    35486
  Partials                   ?     5185

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 dc185b1...a764976. Read the comment docs.


added Range and Scale settings

Only tested on Classic and maybe a switch to the default in-range check should be added cause, not everyone wants a 30yards range check

I pulled in only part of this patch, namely the part allowing to change the frame scale.
I'm not in love with the way the range indication was implemented, mainly because it was confusing and potentially breaking. Setting the range indication based on a single spell is an interesting way about going about it, I'm not sure if it's the best approach though. In the past we could query our distance from a player directly, and that was ideal, but they removed that unfortunately.
My main concerns are #1, this is a confusing option for players, #2 this will cause potential breakage (I always worry about this when we override built in functionality.)

I'm not in love with the way the range indication was implemented, mainly because it was confusing and potentially breaking. Setting the range indication based on a single spell is an interesting way about going about it, I'm not sure if it's the best approach though. In the past we could query our distance from a player directly, and that was ideal, but they removed that unfortunately.

I know, was hoping for a better solution but that's the best I found. (for CLASSIC)

My main concerns are #1, this is a confusing option for players, #2 this will cause potential breakage (I always worry about this when we override built-in functionality.)

mhh, what do you mean with "potential breaking", I run this "code" couple of weeks and saw no errors except the error with combat leaves.
But that's, why I said a custom option to "opt-in", is needed cause most players are not needing a custom range. Healers normally have 40 yards and descursing needs 30 yards in classic - that's why the custom range was added. (i think its a small use case, but mages are fucked if they casting at max range 36yards and want start decursing which is 30 yards)
But if you want to add the alpha, you need to do it anyways.  You can do it with IsSpellInRange or UnitInRange.
function EnhancedRaidFrames:UpdateRangeAlpha(frame)
	if string.match(frame.unit, "party") or string.match(frame.unit, "raid") then
		if IsSpellInRange(EnhancedRaidFrames.db.profile.range.spell, frame.displayedUnit) then
			frame:SetAlpha(EnhancedRaidFrames.db.profile.range.alpha.maximum)
			frame.background:SetAlpha(EnhancedRaidFrames.db.profile.range.background.maximum)
		else
			frame:SetAlpha(EnhancedRaidFrames.db.profile.range.alpha.minimum)
			frame.background:SetAlpha(EnhancedRaidFrames.db.profile.range.background.minimum)
		end
	end
end

the usage of IsSpellInRange is incorrect, which may break your testing environment.
returns - 1 if the target is in range of the spell, 0 if the target is not in range of the spell, nil if the provided arguments were invalid or inapplicable.

Ok I cherrypicked in your change to the OutOfRange fade as well. Just tested it and that's working pretty great

I'll keep looking at this. I want to find a more elegant solution. It seems so heavy handed to set everything to be 30 yards or 40 yards. I really wish there was a per-spell way to do it. bleh.

What if we did per-indicator range checking? We could shade the indicator red tinted if the spell isn't in range or something to provide the visual indicator. That gets around the all or nothing issue I had above

Ok I cherrypicked in your change to the OutOfRange fade as well. Just tested it and that's working pretty great

great 👍

I'll keep looking at this. I want to find a more elegant solution. It seems so heavy handed to set everything to be 30 yards or 40 yards. I really wish there was a per-spell way to do it. bleh.

What do you mean with "per-spell way"? That the range is calculating dynamically based on the latest casted spell or a spell the player selects?

What if we did per-indicator range checking? We could shade the indicator red tinted if the spell isn't in range or something to provide the visual indicator. That gets around the all or nothing issue I had above

I think this is confusing when the "player" frame indicates the player is in range and a other indicates he isn't. It is like the small dot on the "default" action bar, when a spell is in range or not - what I think no one likes.
Overall I prefer a custom range function, with a UI toggle to enable the feature and a dropdown of default ranges (with ranges like 10, 20, 30, 40) or an input field to be flexible for spell names.
function rangeCheck(unit)
    local db = EnhancedRaidFrames.db.profile
    if(db.customRange) then
        return IsSpellInRange(db.rangeSpell, unit) == 0
    else
        local inRange, checkedRange = UnitInRange(unit);
        return checkedRange and not inRange
    end
end

https://github.com/brittyazel/RaidFrameIndicators/blob/490bc7d928821f2c0439b817ec0adc302a59040e/EnhancedRaidFrames.lua#L206-L211
is it possible to add frame.background:SetAlpha(EnhancedRaidFrames.db.profile.rangeAlpha) as well to get the frame fully transparent?


Inability to Re-Access Tool Editing Interface

Problem description
After creating a tool within the Managed Guardian Service (MGS) platform, users are unable to navigate back to the tool's editing interface once they have navigated away. This issue occurs specifically when attempting to upload a schema or make further adjustments to the tool. This limitation is significantly hindering workflow efficiency, as users cannot make necessary changes or updates to their tools after the initial setup.
Expected behavior
Users should be able to navigate back to the tool's editing interface from any point within the platform. This would allow for continuous editing, schema uploads, and adjustments to the tool.
Video
Please refer to the attached video that demonstrates the issue as it occurs during tool creation and subsequent attempts to navigate back to the editing interface.
https://github.com/user-attachments/assets/5c964d8c-e438-44a1-811f-d1d1df1fd400

@xj85770  Thank you so much for raising this bug. We are looking at this ticket and will keep you posted once we have solution and fix for it.

@prernaadev01 Thanks!


Cannot set log level for proposalBuilder in config

Description
Setting this in config seems to have no effect:
  "logging": {
      "proposalBuilder": "error"
  }

It seems to be because the proposalBuilder logger is not configured here:
https://github.com/spacemeshos/go-spacemesh/blob/51b425e629b53a1985fc720e7ab28424c7ac823c/config/logging.go#L17-L50
This issue appears in commit hash: 51b425e
Related: #5167, #5179

looks fixed here https://github.com/spacemeshos/go-spacemesh/pull/5420


Make RedbValue and RedbKey public

Currently the type-safe benefits of this library are diminished because a user cannot implement the necessary traits to make a table with their defined types. Instead they currently have to make a table definition of along the lines of TableDefinition<[u8], [u8]> which kinda sucks.
i suggest adding pub use types::{RedbValue, RedbKey}, and whatever else is needed to lib.rs

Ya, I'm planning to add support for custom types! I haven't quite decided on how it should work, so would love your input actually. What's your use case, and how are you thinking of serializing your data?
I could make those traits public and require serialization to/from &[u8]. Alternately, I think I could have users serialize to/from tuples, which avoids them having to implement the serialization logic and may allow for more storage optimizations because the serialization format would be exposed to redb. The new trait would look something like the following (but I think with per trait per desired tuple arity, since it can't be generic over the number of tuple fields):
trait CustomType {
  type SerializedForm: (T0, T1) where T0: RedbValue, T1: RedbValue;

  fn to_serialized(&self) -> Self::SerializedForm;

  fn from_serialized(serialized: Self::SerializedForm) -> Self;
}

struct MyUserStruct {
  name: String,
  age: u8,
}

impl CustomType for MyUserStruct {
  type SerializedForm = (&str, u8);

  fn to_serialized(&self) -> (&str, u8) {
     (&self.name, self.age)
  }

  fn from_serialized(serialized: (&str, u8)) -> Self {
    Self {
      name: serialized.0.to_string(),
      age: serialized.1
    }
  }
}

The other thing I'm waiting for is Generic Associated Types to become stable. Right now the RedbValue trait has to have weird HRTB stuff, like the WithLifetime trait, to work around it.

What's your use case, and how are you thinking of serializing your data?
My plan is to use a couple different serialization crates depending on data type, like speedy and serde.

I could make those traits public and require serialization to/from &[u8].
I think this is likely best because it feels like the best UX to just be able to define how to (de)serialize and then have everything work. I relatively strongly dislike the tuple form unless it comes with concrete performance benefits.

Can you give this branch a try? I added the VariableWidthValue trait, which provides a simpler interface than directly exposing RedbValue & RedbKey

Thanks for adding that @cberner . I too have a need for user-defined value types.  The branch you mentioned looks good, but it's pretty far behind latest now.  If you can merge in latest to that branch, I'd be happy to take a look for my project and see how it works out.
Thanks for pulling together this awesome db; performance has been stellar thus far in my tests!

Sure. Try this one: https://github.com/cberner/redb/pull/new/custom_types I think it's more up to date.
Also, can you tell me more about your use-case for user defined types? I'm trying to decide whether they're really necessary, or whether it's reasonable to leave it to users to convert between &[u8] or a tuple type

Thanks for the quick response @cberner !  I'll give the linked changes a try later this evening.
It will probably sound bizarre, but I'm utilizing redb as the backend for the compiling and runtime of a custom scripting language.  This language defines the gameplay logic and interactions for a multiplayer game.
The general idea is to gather data-driven declarations of variables, transactions, etc and validate/compile them into a cache-friendly and performant form. This is retained in the 'runtime' database as a set of rules or game logic. After compilation, it is read-only and available on both clients and servers. Storing the runtime in this form allows for simple distribution of workload across multiple threads/cores, and minimizes unnecessary coupling of concrete types.
Separate from the 'runtime' db is a 'world' database.  It retains information about the layout of the game world and its entities.  A small subset of 'world' data is replicated to relevant clients based on the user's interactions with the world (ie. the creature they're fighting, resource node they're harvesting, crafting bench, etc).
Each client also has a corresponding table in a 'user' database, and the entirety of it is replicated to the corresponding client. Reads are done locally to evaluate potential interactions, update UI, etc.. But any actual transactions which affect gameplay are performed on the server. The transaction rules are identical on the client and server's runtime db, but in the event of a desync, the server is already replicating the changes back to re-sync game state.
In terms of actual implementation, I have little need for keys that aren't u128 or str.  But I have a long list of user-defined value types that I'd like to store with redb.  Here's an example:
pub struct DbsTransaction {
pub description: String,
pub conditions: Vec, //each entry contains 5-6 vars depending on an internal enum
pub inputs: Vec, //each entry contains 3 vars
pub outputs: Vec //each entry contains 3 vars
}
Manual conversion is obviously possible, but very error prone.  Tuples could also quickly get out of hand.  Utilizing something like bincode::serialize could alleviate some of the pain; but if the end-user needs to do that for every custom type, it becomes a lot of unnecessary boilerplate.

I was using https://github.com/pmagaz/reddb for prototyping early on, and I really appreciate the approach they took of supporting serde-compatible formats for auto-serialization.  Obviously, the internals of that crate rely on serde for far more than that; but the interface is nice nonetheless.
If you're concerned about bringing in too many dependencies, perhaps support for something like this can be enabled with a feature flag or addon crate?

Thanks for the response.  Yeah, I wrote a simple proc macro for adding to_bytes() and from_bytes(...) to all relevant structs in the meantime. Type safety is the only major loss at this point.
That said, I do think there is value in exposing the RedbValue and RedbKey types.  Doing so locally opened up some options for generics that otherwise would not have been possible.


[APIPUB-1] Serilog implementation

@CSR2017 @jasonh-edfi @lchavarriaga
Please help review and merge the changes,
Thanks

Please include the necessary nuget packages and any .cs files required to enable logging directly to AWS Cloudwatch.  This was previously possible with the AWS.Logger.Log4net nuget package and a simple change to log4net.config.  Logging to AWS Cloudwatch is required for EA's use cases.
https://blog.ivankahl.com/logging-dotnet-to-aws-cloudwatch-using-serilog/

Moved it to a different PR #15


Leverage auth engine accessor auto resolution in integration tests

The enhancement brought by #143 allows to simplify the integration tests to avoid capturing the kubernetes auth accessor and pass it via environment variables to tests, which then currently replaces some placeholders with the passed value.
Using this new capability, there is no need to query the vault engine externally and pass the retrieved value for consumption in tests, making them more simple, straightforward and maintainable.

@raffaelespazzoli you wished for seeing this small change, there it is ;-)


Check architectures for submission to app store

We need to investigate the architectures that are built and make sure they match the requirements for applications submitted to the app store.
https://developer.ibm.com/answers/questions/249027/ios-submition-issue-invalid-architectures/

@glennrfisher Hey, did you guys figure out how to fix this issue? We're trying to submit to the app store and getting the same errors.

Hi @sinchan. Unfortunately, we have not yet gotten the chance to check out this issue. :(

@glennrfisher Do you know if anyone has succeeded in submitting to the app store using recent versions of the SDK?

According to this Carthage issue this problem may have been caused by our "Copy Frameworks" build phase within the SDK project. I removed this build phase in the remove-copy-frameworks branch.
@sinchan: Would you mind building the SDK from the remove-copy-frameworks branch and try submitting to the app store again? We think this may fix the problem.

@glennrfisher Just using the 'remove-copy-frameworks' branch didn't do it, but using it in addition to the following article and stackoverflow question did:
http://ikennd.ac/blog/2015/02/stripping-unwanted-architectures-from-dynamic-libraries-in-xcode/
http://stackoverflow.com/questions/35240330/errors-building-xcode-project-after-adding-in-run-script-fatal-error-lipo-inpu

Thanks for following up, @sinchan! Glad it's working.
You might also be interested in this section of the Carthage readme.


[Question] 🐛 Image Annotation 的 position、start、end 如何理解 !!! 看不懂

+1

Sorry, due to problems in the program's architecture design, we are unable to effectively fix the issues. But it fixed in G2 5.0, you can have a try.


Add pipeline threshold to confusion matrix returns

fix #3079
There are 2 potential issues that I want to raise, although they are not severe enough to block this PR from being merged.
First is the aesthetic of the index when it is very granular, as can be seen here:

Note that the threshold is 0.99999..., but looking at the dataframe, it just shows as 1.0, which could be confusing for OS users. By grabbing the index itself,, we can see the actual value. We could stringify the index to have them appear, but this might be annoying for our internal use:

The other is when our optimized pipeline threshold doesn't match the best threshold chosen through this method. This can be seen in the problem above, but also can be seen here:

Above, the pipeline is optimized using accuracy binary, and we see the pipeline threshold 0.360321 actually has a worse performance value compared to 0.5 with accuracy, which is the ideal value find_confusion_matrix_per_thresholds finds. The differences here are likely how we're finding the optimal threshold, with our optimize_thresholds using gradient descent, and our current method using a simple linear scan. Is this disparity an issue for our users? Discussing with @freddyaboulton, it could be confusing when our optimal thresholds don't match up. However, what would be the best approach to fix this, if necessary?
Again, these two issues shouldn't block the merge of this PR, but are both things I wanted to bring up for discussion.

@angela97lin yep, that was the first concern! Just an aesthetic issue. Filed an issue to address the second here


Mat/Pat - Bugs - Production test

Bugs

Full Time/ Part time is not populating in employee info

Showing a validation error for number of days, number of days should be an optional field

"Optional" button now appearing!


LinkageChecker: Add libanl.so.1 to the whitelist [Linux]

Codecov Report

Merging #824 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #824      +/-   ##
==========================================
- Coverage   70.69%   70.67%   -0.02%
==========================================
  Files         384      384
  Lines       20520    20520
==========================================
- Hits        14506    14503       -3
- Misses       6014     6017       +3

Impacted Files
Coverage Δ

utils/analytics.rb
82.05% <0%> (-7.7%)
:arrow_down:

linkage_checker.rb
65.27% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Wrong format for Request Id

Issue originally reported by @dcartman in https://github.com/vknabel/vscode-swift-development-environment/issues/12#issuecomment-394492671
I'm running on macOS, swift 4.1, compiled source kite with swift 4.1, updated to most recent version of MSDE (2.4.3).
Pointing at the debug build of sourcekite I am getting these errors:
/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/out/src/server/sourcekites.js:88
throw new Error("wrong format for reqid");
^

Error: wrong format for reqid
at SourcekiteResponseHandler.handleResponse (/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/out/src/server/sourcekites.js:88:23)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at readableAddChunk (_stream_readable.js:178:18)
at Socket.Readable.push (_stream_readable.js:136:10)
at Pipe.onread (net.js:560:20)
[Info - 1:39:54 PM] Connection to server got closed. Server will restart.
[Error - 1:39:54 PM] Request textDocument/hover failed.
Error: Connection got disposed.
at Object.dispose (/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/node_modules/vscode-jsonrpc/lib/main.js:825:25)
at Object.dispose (/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/node_modules/vscode-languageclient/lib/client.js:57:35)
at LanguageClient.handleConnectionClosed (/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/node_modules/vscode-languageclient/lib/client.js:1983:42)
at LanguageClient.handleConnectionClosed (/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/node_modules/vscode-languageclient/lib/main.js:126:15)
at closeHandler (/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/node_modules/vscode-languageclient/lib/client.js:1970:18)
at CallbackList.invoke (/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/node_modules/vscode-jsonrpc/lib/events.js:71:39)
at Emitter.fire (/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/node_modules/vscode-jsonrpc/lib/events.js:135:36)
at closeHandler (/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/node_modules/vscode-jsonrpc/lib/main.js:221:26)
at CallbackList.invoke (/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/node_modules/vscode-jsonrpc/lib/events.js:71:39)
at Emitter.fire (/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/node_modules/vscode-jsonrpc/lib/events.js:135:36)
at IPCMessageReader.AbstractMessageReader.fireClose (/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/node_modules/vscode-jsonrpc/lib/messageReader.js:135:27)
at ChildProcess. (/Users/daniel/.vscode/extensions/vknabel.vscode-swift-development-environment-2.4.3/node_modules/vscode-jsonrpc/lib/messageReader.js:253:61)
at emitTwo (events.js:111:20)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket. (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)

Before updating the latest version of MSDE, autocompletion was not presenting any results or errors.
If I run sourcekite from the command line, I'm getting this output:
~/Repos/sourcekite/.build/x86_64-apple-macosx10.10/debug/sourcekite
|||[main.swift:34] sourcekite - sourcekitd_initialize
1
|||[main.swift:42] sourcekite - state: endRequest
|||[main.swift:43] sourcekite - input: 1
|||[main.swift:44] sourcekite - input length: 1

Just to be sure: you didn't install any beta, right?
Does it solve your problem when you compile sourcekite with -c release?

Thanks.
Compiling with '-c release' fixes the error, and I'm now seeing autocompletion and source comments for built-in classes, and classes in my project.
Is source kite supposed to be reading through the swift package dependencies?


Adding CVEs for keda-2.11-adapter

Adding Advisory GHSA-2c7c-3mj9-8fqh for keda-2.11-adapter

added in https://github.com/wolfi-dev/advisories/pull/802


[CT-3417] [Feature] more usable compiled code output from uniqueness tests

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
whenever I have a failing uniqueness test, I end up spending too long rewriting the compiled output from dbt test, e.g.
select
    id as unique_field,
    count(*) as n_records

from some_model
where id is not null
group by id
having count(*) > 1

into
with
    src as (select * from some_model),
    dupes as (
        select
            id as unique_field,
            count(*) as n_records

        from src
        where id is not null
        group by id
        having count(*) > 1
    )
select *
from src
where id in (select unique_field from dupes)

in order to find out e.g. which of the upstream models caused the duplicates. I'd propose the compiled code from dbt test uniqueness tests follows the following format instead:
with
    src as (select * from some_model),
    dupes as (
        select
            id as unique_field,
            count(*) as n_records

        from src
        where id is not null
        group by id
        having count(*) > 1
    )
select * from dupes
--select * from src where id in (select unique_field from dupes)

this would make it easier rewrite the output: comment out select * from dupes and uncomment the line below.
Describe alternatives you've considered
my current alternative is to have the abovementioned query saved, but then I need to rewrite both the unique column, and the table name every time.
Who will this benefit?
debugging models with failing uniqueness tests.
Are you interested in contributing this feature?
I'd love to but I'd need some help as I mostly know sql and jinja
Anything else?
wondering if this would also be useful for not_null tests and potentially other tests, but it's a lot easier rewriting
select some_column
from some_table
where some_column is null

into
select *
from some_table
where some_column is null

so this wouldn't benefit as much from the approach I'm suggesting.

Hi @dbeatty10 , thanks for the writeup! I think I have a workaround to avoid the downsides:
with
    dupes as (
        select
            id as unique_field,
            count(*) as n_records

        from {{ref('some_model')}}
        where id is not null
        group by id
        having count(*) > 1
    )
select unique_field, n_records from dupes
--select * from {{ref('some_model')}} where id in (select unique_field from dupes)

But also very OK if you don't wanna re-open the PR; I can just implement this through the workaround you mention 🙏


Precision and recall

Save execution view should calculate precision and recall as well as total pass rate

You can decide where to calculate these numbers: you can select it on the Frontend or create proper optimised endpoints on the backend. You can read more about it here: https://en.wikipedia.org/wiki/Precision_and_recall

Speaking about what do we mean by FALSE POSITIVE and FALSE NEGATIVE.
We talk about the tool level. Not test level.
Our save-cli when it tests static analyser - reports how many warnings were EXPECTED, how many of them were FOUND, how many warnings are MISSING and how many warnings were superfluous (that we DID NOT EXPECT).
In this case PRECISION for benchmark = FOUND / (FOUND + FOUND BUT NOT EXPECTED)
RECALL for benchmark = FOUND / (FOUND + NOT FOUND). BTW - FOUND + NOT FOUND = ALL EXPECTED warnings.

As we have discussed - we need to focus on PRECISION and RECALL. We should also calculate FP/NUMBER_OF_TESTS and FN/NUMBER_OF_TESTS. All these data will be needed later to properly calculate developer's rating.


[TE] Anomaly ID Presentation Component

Adding the anomaly title and id header block (this may be changing soon) along with styles and integration test for display of title, ID, percent change, etc.

@apucher Good question!
TLDR: Yes
Yarn maintains consistency across machines in two key ways:

Yarn uses a deterministic algorithm that builds up the entire dependency tree before placing files where they need to be.
Important info from the install process is stored in the yarn.lock lockfile so that it can be shared between every system installing the dependencies.

source: https://yarnpkg.com/blog/2016/11/24/lockfiles-for-all/


ENH: first draft at qt plan builder

Type on the right, nested messages show up on the left
Still hacky.
To test, in IPython
%matplotlib qt
import matplotlib.pyplot as plt
plt.plot(range(5))

to make sure qApp and everything is setup, then run
plan_writer()

type a plan and set the iterable equal to target, ex
import bluesky.plans as bp
from bluesky.examples import det

target = bp.count([det])

The code is evaluated against the current globals, but the result is shoved into a local dict.

Current coverage is 81.31% (diff: 0.00%)

Merging #626 into master will decrease coverage by 1.30%

@@             master       #626   diff @@
==========================================
  Files            20         21     +1
  Lines          4371       4441    +70
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           3611       3611
- Misses          760        830    +70
  Partials          0          0

Powered by Codecov. Last update cf05cb4...5a16f93

Superseded by work in bluesky-widgets and related repos.


Added pd.DataFrame transformation for Imputer and HampelFilter

What does this implement/fix? Explain your changes.
Added pd.DataFrame transformation for Imputer and HampelFilter.

Martin Walter<EMAIL_ADDRESS>Mercedes-Benz AG on behalf of Daimler TSS GmbH.
https://github.com/Daimler/daimler-foss/blob/master/LEGAL_IMPRINT.md

should be tested like before? I have removed the tag univariate-only so I think the following existing test function is applied to them now?
https://github.com/alan-turing-institute/sktime/blob/7343dc36566935b42167878c45d570099af96dab/sktime/transformations/tests/test_all_transformers.py#L90-L100

Martin Walter<EMAIL_ADDRESS>Mercedes-Benz AG on behalf of Daimler TSS GmbH.
https://github.com/Daimler/daimler-foss/blob/master/LEGAL_IMPRINT.md


Add: Skip_while operator

Added skip_while operator (including tests, doxygen docu + samples)

Wow! Looks great to me, thank you!


[SONARMSBRU-198] Amended targets so warnings are not treated as errors

... for FxCop and Roslyn analysis
Updated tests
There is also a related StyleCop property $(StyleCopTreatErrorsAsWarnings). However, we don't run StyleCop as part of the build (it's run by the StyleCop plugin in the sonar-runner) so there's no point in us setting that property in the targets file.

LGTM

Manually tested


Bump version

Coverage remained the same at 74.934% when pulling a05baf92a2511947accd9477b191f180f22174a1 on develop into c43e010c3b480346a2f80ec343b058c0b2514254 on master.


Implementing different policies for the same class

I have an REST API application with administration interface built using ActiveAdmin. It uses Pundit adapter to restrict access for different types of AdminUsers (I have admin, crm manager, and cms manager roles).
Thus, I use Pundit to authorize AdminUsers to access our domain model objects.
Now, I have to implement authorization of ApiClients for the same objects via REST API interface.
Thereby, I need different policies for the same class for two different authorization contexts (AdminUser and ApiClient)
My current decision is to use custom PolicyFinder and ignore Pundit.policy method.
class AdminPunditAdapter < ActiveAdmin::AuthorizationAdapter
  def authorized?(action, subject = nil)
    policy_finder = AdminPolicyFinder.new(subject)
    policy = policy_finder.policy!.new(user, subject)

    policy.respond_to?(action) && policy.public_send(action)
  end
end

class AdminPolicyFinder < Pundit::PolicyFinder
  def find
    policy = super
    "Admin#{policy}" if policy
  end
end

This solution doesn't look perfect, I'd rather expect either from PolicyFinder to be able to return different policies depending on authorization context or from Pundit.policy method to be configurable with policy finder class.

There are a ton of discussions about this particular issue. Please search around a bit and read them before commenting further on this issue.


Added form to be used from browser

This note is referenced in a section that describes using curl to interact with the application.  While perhaps implied, I thought it made sense to explicitly mention the browser.

Can one of the admins verify this patch?

[test]

LGTM, thanks @rdruss. Merging.

merged: c3be1f996d9771f59db45dd008a6b6cf4ed8a86e


add first line of stacktrace to console.log error in dev environment

enhancement a bit more error to debug
Description
I usually see errors on reflexes during development in the console.log first, so it would be nice to have a hint there,
where the error is coming from.
Therefore I added the first line of the stacktrace to the error info in the console.log for convenience.
Why should this be added
Pure convenience, only done in dev environment
Example output

Checklist

[x] My code follows the style guidelines of this project
[x] Checks (StandardRB & Prettier-Standard) are passing
[x] This is not a documentation update

Sure, why not! 😉


Colors! As RGB Hexdecimal

Colors is a helper I always end up doing myself.
Maybe #rgb_color and #rgba_color.
It would return "#RRGGBB" and "#RRGGBBAA" respectively.
Or an one shot thing: "%06x" % rand(0x1000000) or rubocop ok format('%06x', rand(0x1000000))
Thank you, I use faker everywhere!

This can be closed @stympy

TY!


add EcoAssistant blog

Why are these changes needed?
Add a blog introducing EcoAssistant
Related issue number
N/A
Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

@microsoft-github-policy-service agree

Codecov Report

Merging #647 (67f87d5) into main (9a216b1) will decrease coverage by 3.21%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #647      +/-   ##
==========================================
- Coverage   28.73%   25.53%   -3.21%
==========================================
  Files          27       26       -1
  Lines        3379     3372       -7
  Branches      760      760
==========================================
- Hits          971      861     -110
- Misses       2337     2443     +106
+ Partials       71       68       -3

Flag
Coverage Δ

unittests
25.53% <ø> (-3.15%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 4 files with indirect coverage changes

Both code formatting check and doc checks fail.

you can use pre-commit to help with the formatting.

you can use pre-commit to help with the formatting.

yes. all checks are passed now


Add story: "Niklaus wants to use GhostCell-like cell borrowing"

Okay, I'll change to Barbara. I will also expand it out where requested -- and try and adjust to fit the "story" style!

I've tried to address the comments. I'm happy to edit further as necessary.

I think this story would be better if were rephrased to more extensively motivate statically checked cells and have slightly less detail on a proposal that could go into the standard library. Then some of that detail can be moved to a "shiny future" story.

I'm not sure I'm the right person to fully motivate this, and probably nor is Barbara -- although I could try. If you want a "RefCell tale of woe" then perhaps we need a more naive character. I assume that Barbara knows very well the problems of RefCell borrows and avoids those problems through diligent manual checking. I avoid RefCell::borrow_mut as much as I can, so I don't have a tale of woe either. Just recently, coding with it I realized that I had to wake up and pay attention and double-check my code, and actually I found one place where I needed to drop the borrow in order to avoid the possibility of a panic. But this is prevention. Someone without that awareness could easily get a lot deeper in before having unexpected panics and then having to debug and so on. But I don't have a story like that because I'm already aware of the danger.
Anyway I will expand the story part and explain more stuff and see if I can motivate it better. Regarding splitting it up -- really this is for you guys to decide. Niko asked me to expand on the qcell stuff, so I did. I don't know how best to fit into your structure. I was running with "Barbara has a curious mind and tries to solve the problem herself". Whether there is a bright future, I'm not sure. It may be technically impossible given the constraints, but Barbara (and I) can't be sure. Maybe it IS possible, and if someone can see that bright future path then that would be fantastic!

I think this story would be better if were rephrased to more extensively motivate statically checked cells and have slightly less detail on a proposal that could go into the standard library. Then some of that detail can be moved to a "shiny future" story.

Hmm, @rylev, I think i agree. What i could imagine would be a story that highlights a case where the user has to debug panics, which ghostcell would avoid. and perhaps clarifies why cells are needed in the first place (this might reference other stories).

Thinking some more about the motivation, I don't know whether this is a practical problem for lots of people or not. Is there anything special about how async/await code is structured that means you can be lax with RefCell borrows and it all works out fine anyway? In my runtime glue code, there was definitely a case where I could have had a panic. But if the problem is limited to coders of runtimes it is not such a big deal.

I think that there will be more cells in async code than other code specifically because of the fact that &mut contexts don't place nicely, as described in [alan lost the world](https://github.com/rust-lang/wg-async-foundations/blob/master/src/vision/status_quo/alan_lost_the_world.md0. I have no idea if ghostcell can help here, though!

I can accept that the motivation is not strong enough right now, unless it happens to connect with another story.

@uazu My personal policy is to try and merge all stories -- this is brainstorming, after all, not making any full decisions! So, I would like to merge this PR. However, before doing so, it'd be good if we make as strong a case as we can. Editing the story to focus a bit on the practical difficulties, if we can think of some, would be excellent. As I said, I think that we are likely to have cells showing up to share context between tasks.

I've added two examples. If anyone can think of other example scenarios, I can add them.

As this hasn't been merged yet, I thought it best to correct a small error in example 1. I have now constructed the full example and it does panic. I didn't just paste in the original code as it is a lot more complicated and would take more explaining. The example now illustrates the problem situation better.

Great! Merging.


if i upload my .env file to vercel or railway it does not work, it does not detect my site password and it does not detect the api key that i assigned in the .env either

How is Anse deployed?
Vercel
Describe the bug
if i upload my .env file to vercel or railway it does not work, it does not detect my site password and it does not detect the api key that i assigned in the .env either
Console Logs
No response
Participation

[X] I am willing to submit a pull request for this issue.

Currently anse does not use any variable environments, and will be added later.

Do you have some roadmap?


Enable task artisan to be run twice in one flow

Because of using invoke to call laravel:artisan[:command_name],
we should make task laravel:artisan can be run twice and more in one flow.

LGTM


Bot.runAsUser

Before:  When a bot runs, any resources created or edited would appear as edited by the Bot, not the user that triggered the Bot.
Now:  You can set an optional flag on the Bot called runAsUser, which means the Bot will act as the user that triggered the execution.
The common case for this is the QuestionnaireResponse -> resources workflow.  If a user fills out a form, and that creates a new patient or a new order, ideally it should show up as the user doing it, not the bot.

Coverage increased (+0.004%) to 95.144% when pulling c6d796746cd5e2edd20c7f379931ffeab8a18738 on cody-bot-run-as-user into 39d1d9d196620e23cea8d057c02832f689c4f52a on main.


Fixes "podSelctorCallback" typo.

Nothing more. :-)

Nothing more. :-)

Actually, also two phpdoc fixes for Resource(s)List return type.

Thanks. 🚀


Super resolution quaility on arbitrary imagenet image

I test ddnm on arbitrary imagenet image but did not get as good results as the demo.
The command I use is :
CUDA_VISIBLE_DEVICES=3 python main.py --resize_y --config confs/inet256.yml --path_y ./ILSVRC2012_val_00046632.JPEG --class 22 --deg "sr_averagepooling" --scale 4 -i imagenet_46632_cc_256x96
Apy:

final:

Is there any parameter I need to adjust?

Hi, this is because of the out-of-domain problem. For example, the first patch start from the left-up corner, where no eagles appear. Actually, none of a patch can cover full eagle content. In this case, using Hierarchical Restoration may alleviate this problem. You may refer to the paper for Hierarchical Restoration Unlimited-Size Diffusion Restoration.


ImportError: No module named 'pip.req'

Steps to reproduce
pip install py-mini-racer
Expected behavior
install !
Actual behavior
setup.py", line 12, in
from pip.req import parse_requirements
ImportError: No module named 'pip.req'
System configuration
Python version:
python 3.5
pip 10.0.1
solution
Seems to be an incompatibility with new version of pip (>=10)
https://stackoverflow.com/a/49867265/1619521
so have to change
from pip.req import parse_requirements
to
try: # for pip >= 10
    from pip._internal.req import parse_requirements
except ImportError: # for pip <= 9.0.3
    from pip.req import parse_requirements

Thanks, this was fixed in https://github.com/sqreen/PyMiniRacer/pull/49. Will be released soon.

Hi, I have same problem will it be fixed soon? Is there any work around?

Workaround : install previous version of pip.
Think this would work.
pip install pip==9.0.3
Le mar. 8 mai 2018 à 16:47, bootcher007<EMAIL_ADDRESS>a écrit :

Hi, I have same problem will it be fixed soon? Is there any work around?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sqreen/PyMiniRacer/issues/50#issuecomment-387428014,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHcpybZlhAPWTQ9npMBNcgofKs5aM2VTks5twa_mgaJpZM4Tso_0
.

It should be fixed now with the last version of PyMiniRacer

Hello,
In my centos 8, there is  19.3.1 version of pip. An I had this pip.req problem. To solve this, I installed pip 9 version and my problem fixed.
But  there is so many version range from 9 upto 19.. Do you think that there is another way in newer version of pip to solve this pip.req problem?

Hey, this should have been fixed in this PR https://github.com/sqreen/PyMiniRacer/pull/49
Can you send us more info regarding your problem by sending us the output of the commad pip debug?
Thanks

thank you I solved
Sélim Menouar<EMAIL_ADDRESS>18 Eki 2019 Cum, 23:20 tarihinde
şunu yazdı:

Hey, this should have been fixed in this PR #49
https://github.com/sqreen/PyMiniRacer/pull/49
Can you send us more info regarding your problem by sending us the output
of the commad pip debug?
Thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sqreen/PyMiniRacer/issues/50?email_source=notifications&email_token=AIZCGR6CIAB5NGNQOEIUWBDQPILCBA5CNFSM4E5SR72KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBV2AIY#issuecomment-543924259,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIZCGR23V564TKZNPYUT3L3QPILCBANCNFSM4E5SR72A
.

Hey, this should have been fixed in this PR #49
Can you send us more info regarding your problem by sending us the output of the commad pip debug?
Thanks

I guess this topic is closed? But i am struggling with exactly above.  Only option to downgrade? I've installed py-mini-racer. Made no difference.
Using pip 20.1.1 from /usr/lib/python3/dist-packages/pip (python 3.8) ... trying to install prometheus
Find debug below:
pip version: pip 20.1.1 from /usr/lib/python3/dist-packages/pip (python 3.8)
sys.version: 3.8.5 (default, Aug  2 2020, 15:09:07)
[GCC 10.2.0]
sys.executable: /usr/bin/python3
sys.getdefaultencoding: utf-8
sys.getfilesystemencoding: utf-8
locale.getpreferredencoding: UTF-8
sys.platform: linux
sys.implementation:
name: cpython
'cert' config value: Not specified
REQUESTS_CA_BUNDLE: None
CURL_CA_BUNDLE: None
pip._vendor.certifi.where(): /etc/ssl/certs/ca-certificates.crt
pip._vendor.DEBUNDLED: True
pip._vendor.WHEEL_DIR: /usr/share/python-wheels
debundled wheel versions:
CacheControl==0.12.6
appdirs==1.4.4
certifi==2<IP_ADDRESS>
chardet==3.0.4
colorama==0.4.3
contextlib2==0.6.0
distlib==0.3.0
distro==1.5.0
html5lib==1.0.1
idna==2.9
ipaddr==2.2.0
lockfile==0.12.2
msgpack==0.6.2
packaging==20.3
pep517==0.8.2
pip==20.1.1
pkg_resources==0.0.0
progress==1.5
pyparsing==2.4.7
requests==2.23.0
resolvelib==0.3.0
retrying==1.3.3
setuptools==44.0.0
six==1.15.0
toml==0.10.1
urllib3==1.25.9
webencodings==0.5.1
wheel==0.34.2
Appreciate, if you can comment.


Bug on 3.0.0

Since 3.0.0 WebImage is not able to update its URL
on v2.2.7

on v3.0.0

Full code
struct ContentView: View {
    @State var isOn = false

    var url: URL? {
        if isOn {
            .init(string: "https://upload.wikimedia.org/wikipedia/commons/thumb/c/c1/Google_%22G%22_logo.svg/1024px-Google_%22G%22_logo.svg.png")
        } else {
            nil
        }
    }

    var body: some View {
        VStack {
            WebImage(url: url)
                .resizable()
                .scaledToFit()
                .frame(width: 50, height: 50)
            Button("Toggle") {
                isOn.toggle()
            }
        }
    }
}

I found a workaround by setting .id(url) but I don't think this is optimized

I have the same issue on AnimatedImage but only when switching between nil and non nil URL

nil url only ? What's your SDWebImage version, please provide the full Pod version (upload your Podfile.lock)
A reproduce demo is better.

I found a workaround by setting .id(url) but I don't think this is optimized

@arnauddorgans  Actually, I compare the 2.x and master branch and found this.
I guess this cause issue ? Why does we still need this identifier ? Is nil url special ?

Fixed in v3.0.1

It works perfectly now, thanks! ❤


Bucket creation is not checking the mod bits on directory (r) if nfs4acls are present

Environment info

NooBaa Version: noobaa-core-5.17.0-20241005.el9.x86_64
Platform: Standalone noobaa

Actual behavior

Set NC_DISABLE_ACCESS_CHECK : false
Create an account account7000 with --newbucketspath /mnt/gpfs0/account7000/
Create a new directory /mnt/gpfs0/account7000/bucket7000-03 with root:root and 770 permission set.
If I don't set the nfs4acl on the path “/mnt/gpfs0/account7000/bucket7000-03” , bucket creation is failing as expected.
However if I set nfs4acl using “nfs4_setfacl -a A::user7000@:rwaDxtTnNcCoy /mnt/gpfs0/account7000/bucket7000-03", bucket creation is succeeding.

Expected behavior
My understanding is we still need to check for account7000(uid 7000, gid 7000) must have READ (r) access set via mod bits on the bucket directory. Currently no mod bit check (r) is performed if nfs4acls are present in the directory
Steps to reproduce
Mentioned in actual behaviour.
More information - Screenshots / Logs / Other output

@anandhu-karattu with latest code changes PR , modbit based access restriction is disable for noobaa by defaultand its controlled using flag config.NC_DISABLE_POSIX_MODE_ACCESS_CHECK. If not overriden with config.json change NC_DISABLE_POSIX_MODE_ACCESS_CHECK always will have value true.
cc : @romayalon

@naveenpaul1 , I am using build "noobaa-core-5.17.0-20241016.el9.x86_64".
In this build I don't see the parameter "NC_DISABLE_POSIX_MODE_ACCESS_CHECK" in config.json.
@romayalon , do we need to back port this flag in to 5.17 ? As suggested by Naveen, I added the parameter manually in the config.json "NC_DISABLE_POSIX_MODE_ACCESS_CHECK=false" and looks like nfs4acls are not getting considered after that.

@anandhu-karattu I could already see the new configuration in 5.17 branch, Its already backported to 5.17
new config NC_DISABLE_POSIX_MODE_ACCESS_CHECK in 5.17 branch : https://github.com/noobaa/noobaa-core/blob/5.17/config.js#L895

@naveenpaul1 , I have 16/Oct build . But I can not see this parameter in config.json
[root@522oct21-21 ~]# rpm -qa | grep noobaa
noobaa-core-5.17.0-20241016.el9.x86_64
[root@522oct21-21 ~]#
[root@522oct21-21 ~]#
[root@522oct21-21 ~]# jq . /mnt/cesSharedRoot/ces/s3-config/config.json
{
  "CONFIG_ROOT": "",
  "ENDPOINT_FORKS": 2,
  "NSFS_BUF_POOL_MEM_LIMIT": 0,
  "NSFS_BUF_SIZE": 0,
  "ENDPOINT_PORT": 6001,
  "ENDPOINT_SSL_PORT": 6443,
  "ENDPOINT_SSL_STS_PORT": 0,
  "EP_METRICS_SERVER_PORT": 0,
  "ALLOW_HTTP": false,
  "NSFS_CALCULATE_MD5": true,
  "UV_THREADPOOL_SIZE": 16,
  "GPFS_DL_PATH": "/usr/lpp/mmfs/lib/libgpfs.so",
  "NSFS_OPEN_READ_MODE": "",
  "NSFS_CHECK_BUCKET_BOUNDARIES": false,
  "NSFS_TRIGGER_FSYNC": false,
  "NSFS_WHITELIST": [],
  "TIME_TO_SYNC_BUCKET": 0,
  "TIME_TO_SYNC_ACCOUNT": 0,
  "BACKUP_PATH": "",
  "RESTORE_PATH": "",
  "NOOBAA_LOG_LEVEL": "default",
  "NSFS_NC_STORAGE_BACKEND": "GPFS",
  "NSFS_NC_CONFIG_DIR_BACKEND": "GPFS",
  "NSFS_DIR_CACHE_MAX_DIR_SIZE": 536870912,
  "NSFS_DIR_CACHE_MAX_TOTAL_SIZE":<PHONE_NUMBER>,
  "NSFS_GLACIER_ENABLED": false,
  "NSFS_GLACIER_LOGS_ENABLED": false,
  "NC_MASTER_KEYS_GET_EXECUTABLE": "/usr/lpp/mmfs/bin/cess3_key_get",
  "NC_MASTER_KEYS_PUT_EXECUTABLE": "/usr/lpp/mmfs/bin/cess3_key_put",
  "NC_MASTER_KEYS_STORE_TYPE": "executable",
  "LOG_TO_SYSLOG_ENABLED": true,
  "LOG_TO_STDERR_ENABLED": false,
  "NC_DISABLE_ACCESS_CHECK": false
}

@anandhu-karattu It's not listing here because NC_DISABLE_POSIX_MODE_ACCESS_CHECK is not added in config.json. I am not sure who is responsible for updating the config.json, most probably the Scale team
@rkomandu

@anandhu-karattu @naveenpaul1 @guymguym we shouldn't expose it to the user, we kept this flag as an option to use it in the future.
Today our read check is via opening the file/directory and not via mode bits.
@anandhu-karattu If you still want to test it although we should not expose it to the user (currently) you can edit the config.json file directly.

@romayalon I agree. This is not a bug. Summarising my understanding after the tests

if an ACL (I tested nfs4acl) on the directory, it will be considered for bucket/account creation always.
If the user does not want to honour the ACL, currently we have no option. However adding the flag "NC_DISABLE_POSIX_MODE_ACCESS_CHECK=false" will stop considering the ACLs. We are not disclosing this to the users as of now. I discussed this with @madhuthorat and we are good with that approach.
If no ACLs present and "NC_DISABLE_ACCESS_CHECK": false , noobaa will look for the READ (r) access in the directory for the account owner.

@anandhu-karattu almost,
3 -> We always check read permissions of the directory by opening it (not bia mod bits), regardless of the existence of an ACL.
So are we good to close it?

Yes please close it @romayalon

closing issue


Make it possible for users to customize CupertinoNavBar's previousTitle text style.

Use case
Make it possible for users customized CupertinoNavBar's previousTitle text style.
Proposal
Make it possible for users customized CupertinoNavBar's previousTitle text style.

@lucasjinreal
You shared a proposal to make changes to CupertinoNavBar, but can you also elaborate on the use case you are trying to achieve with this proposed change ?

Thank u for the response.
We want something like this:

I know it can be achieved by custom leading, but I want keep the transition animations, if customize the leading, animation would gone.
It's than possiable at least make the leading back icon and text style can be changable?
At least the previousPageTitle text style, it should be changable, since the middle text can be set standalone, if they are not aligned, will looks weired.

We should check to see if this can be worked around currently by wrapping the leading widget and title on the previous page with a Hero widget to maintain that animation.

Some attempts have been made. Firstly, conducting the operation externally could be cumbersome. Secondly, the hero animations could be displayed but were not highly uniform with the default animations in the Cupertino transition (such as transition, scale, and alpha, etc.).


Retrieving point write status was broken in 3.0?

Previous behavior for the point_write method here was to retrieve the write status of the point if only the point argument was supplied (causing all other arguments to be None).
Since the 3.0 release, more specifically a78f5889997217e8e5afe16ca252e063b9025207, if the who kwarg is not provided, self._username is used instead.
This seems to break the previous behavior of calling point_write(point), as who is no longer None.
Can you provide guidance for how to retrieve point write status in 3.0? Is this behavior intended?

What if you explicitly pass who=None ?

Forgot to ask, using this in skyspark ? nhaystack or widesky ?

What if you explicitly pass who=None ?

Nevermind... it'll be overridden...

Please, try the develop branch where I modified the behaviour so who will be reset to None in the case where level is None.

Sorry for not replying earlier. Just saw the change here

Does it make sense to change the error message to remove the requirement for who to be None as the value for who will not be considered if level is None.
In the first part of the if statement, you set who to be None, but that does seem to be used - is that line needed?

With these suggestions, the on_point_write method would become:
def _on_point_write(self, point, level, val, who, duration, callback, **kwargs):
        args = {"id": self._obj_to_ref(point)}
        if level is None:  # Ignore value for who as it may be username
            if (val is not None) or (duration is not None):
                raise ValueError(
                    "If level is None, val and duration must be None too."
                )
        else:
            args.update({"level": level, "val": val})
            if who is not None:
                args["who"] = who
            if duration is not None:
                args["duration"] = duration
        return self._get_grid("pointWrite", callback, args=args, **kwargs)

It may also be worth updating the docstring of the point_write method to reflect the change: If level is None, the val and duration parameters should be None too, the write status of the point is retrieved.

You are right. who is not used. We can remove that line.
Merci !
Regarding the docstring, I'm heading toward this, hoping it will be clearer.
    """
    point is either the ID of the writeable point entity, or an instance of
    the writeable point entity to retrieve the write status of or write a
    value to.

    To retrieve the write status of the point, value, duration and level are required to be None.
    To write to a point, value and level are required and duration is optional.
    """

Function will become
def _on_point_write(self, point, level, val, who, duration, callback, **kwargs):
    args = {"id": self._obj_to_ref(point)}
    if level is None:
        if (val is not None) or (duration is not None):
            raise ValueError(
                "You tried writing a value without specifying a level (or specified a duration without providing a level neither a value. Please provide required level. If trying to retrieve write status of the point, provide None as value, duration and level"
            )
    else:
        args.update({"level": level, "val": val})
        if who is not None:
            args["who"] = who
        if duration is not None:
            args["duration"] = duration
    return self._get_grid("pointWrite", callback, args=args, **kwargs)


Should be noted in the documentation about sourcing when using brew

When you use homebrew there is a specific source path you need to use in .zshrc in order for it to work. This is non-obvious and can be easily missed in the homebrew printout after the install. This should be noted to make the install documentation better

Thanks for the report.  That actually sounds like either a PEBKAC (user didn't read post-install message) or a downstream bug (homebrew should make that message harder to overlook).  Having said that, we do cover other downstreams in our docs so we can say something about homebrew as well.
I don't use homebrew myself, however, so I'll leave this issue for a homebrew user to fix.  Would you like to suggest a patch?

When using Brew, the command for sourcing the script should be
echo "source $(brew --prefix zsh-syntax-highlighting)/share/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh" >> ${ZDOTDIR:-$HOME}/.zshrc
Enable syntax highlighting in the current interactive shell:
source $(brew --prefix zsh-syntax-highlighting)/share/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh

Thanks! Needs a ${(q)}. Will leave it to a Homebrew user to review further. Excuse brevity.


Changes to juniper_ixia.textproto and juniper.config files

juniper_ixia.textproto - Removed reference to cptx image which isnt needed
juniper.config - Corrected the number of sub-ports

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
580

Relevant Lines:
1173

💛  - Coveralls

Hello,
Can you please review this request and merge it.

/gcbrun


Support Macros on Windows

Investigating issues with enabling Macros on Windows:

[ ] CI build support for extracting the toolchain
[ ] build issues (references to early build)
[x] memory corruption
[x] array truncations
[x] fix ASTGen
[x] fix swift-frontend
[x] fix swift-driver
[x] fix tests for Windows
[x] Update packaging to include the new content

Change Set:

https://github.com/apple/llvm-project/pull/7377
https://github.com/apple/llvm-project/pull/7378
https://github.com/apple/swift-syntax/pull/2130
https://github.com/apple/swift/pull/68258
https://github.com/apple/swift/pull/68256
https://github.com/apple/swift/pull/68257
https://github.com/apple/swift/pull/68268
https://github.com/apple/swift/pull/68271
https://github.com/apple/swift/pull/68278
https://github.com/apple/swift/pull/68280
https://github.com/apple/swift/pull/68291
https://github.com/apple/swift/pull/68292
https://github.com/apple/swift/pull/68302
https://github.com/apple/swift/pull/68307
https://github.com/apple/swift/pull/68308
https://github.com/apple/swift/pull/68309
https://github.com/apple/swift/pull/68313
https://github.com/apple/swift/pull/68314
https://github.com/apple/swift/pull/68315
https://github.com/apple/swift/pull/68318
https://github.com/apple/swift/pull/68319
https://github.com/apple/swift/pull/68321
https://github.com/apple/swift/pull/68322
https://github.com/apple/swift/pull/68323
https://github.com/apple/swift-driver/pull/1433
https://github.com/apple/swift-installer-scripts/pull/245

State of the world:

[ ] 2 test failures:

[ ] requires changes to swift-driver & swift-driver for the default plugin directory
[ ] CustomStringConvertible conformance is not being seen resulting in the error message being rendered improperly

[ ] Need to fix the build system to wire together the toolchain.
[ ] Update the CI build script to invoke the build appropriately
[ ] Update the packaging rules

5.9.1 is out with the support.


KmlPlacemark method call over mInlineStyle when it is null

Check for method call over mInlineStyle when it is null

I signed it!
2017-08-30 17:30 GMT+02:00 googlebot<EMAIL_ADDRESS>
Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If your company signed a CLA, they designated a Point of Contact who
decides which employees are authorized to participate. You may need to
contact the Point of Contact for your company and ask to be added to the
group of authorized contributors. If you don't know who your Point of
Contact is, direct the project maintainer to go/cla#troubleshoot.
In order to pass this check, please resolve this problem and have
the pull request author add another comment and the bot will run again.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/googlemaps/android-maps-utils/pull/418#issuecomment-326027969,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeBgZEcYl-fUwa4JSgxgvKRvCVLh6v4Mks5sdYAZgaJpZM4PHkbH
.

Thanks again


[SPARK-45340][SQL] Remove the SQL config spark.sql.hive.verifyPartitionPath

What changes were proposed in this pull request?
In the PR, I propose to remove already deprecated SQL config spark.sql.hive.verifyPartitionPath, and the code under the config. The config has been deprecated since Spark 3.0.
Why are the changes needed?
To improve code maintainability by remove unused code.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
By running the modified test suite:
$ build/sbt "test:testOnly *SQLConfSuite"
$ build/sbt "test:testOnly *QueryPartitionSuite"

Was this patch authored or co-authored using generative AI tooling?
No.

Merging to master. Thank you, @cloud-fan and @HyukjinKwon for review.


add stacktrace for error

this is an example of the output when an error happens:
mgradm install podman --logLevel=debug --config /root/mgradm.yaml uyuni-master-podman-srv.mgr.suse.de
11:54AM INF mgradm/cmd/cmd.go:53 > Welcome to mgradm
11:54AM INF mgradm/cmd/cmd.go:54 > Executing command: podman
11:54AM INF shared/utils/config.go:32 > Using config file /root/mgradm.yaml
11:54AM DBG shared/utils/exec.go:52 > Running: timedatectl show --value -p Timezone
11:54AM DBG shared/utils/exec.go:58 > Command output: Europe/Berlin

11:54AM INF mgradm/cmd/install/podman/utils.go:59 > setting up server with the FQDN 'uyuni-master-podman-srv.mgr.suse.de'
11:54AM DBG shared/utils/utils.go:65 > Computed image name is registry.opensuse.org/systemsmanagement/uyuni/master/containers/uyuni/server:latest
11:54AM INF shared/podman/images.go:19 > Ensure image registry.opensuse.org/systemsmanagement/uyuni/master/containers/uyuni/server:latest is available
11:54AM DBG shared/utils/exec.go:52 > Running: podman images --quiet registry.opensuse.org/systemsmanagement/uyuni/master/containers/uyuni/server:latest
11:54AM DBG shared/utils/exec.go:58 > Command output: ff1389b2481b

11:54AM INF shared/podman/network.go:22 > Setting up uyuni network
Error: cannot wait for system start: cannot generate systemd service: cannot setup network: exit status 1

it would be helpful to add a stacktrace when error happens, to point out exactly the command that fails

Agree I ran into the same issue yesterday on arm64. the error is not very descriptive.


Updated Graph API version

Thought this lib needed a version-bump. Maybe we should make the graph api version into a variable?

Please fix the tests as well. Is the functionality confirmed to be working still as well?

@eXeDK Yeah the Graph version bump didn't change the functionality of the requests

@magnusburton if you are still using this package. Are you interested in helping getting this package up to speed and maintaining it?
Unfortunately I don't have the required time to do all of the job myself.

Updated the Graph API to 2.12 instead :-)


fix: properly handle default parameter assignment

#226  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Fixes #225


As a user on a Division profile page, I want to see how the Division I am viewing compares and ranks with other Divisions.

As a user I want to see the same for Upazilas and Districts


Filter Input defaultValue not working when input has property alwaysOn

When I use filter with defaultValue & alwaysOn
const UserFilter = props => (
  <Filter {...props}>
    <TextInput label="name" source="name" defaultValue="test" alwaysOn />
  </Filter>
);

then default value is not rendered.
Without alwaysOn it works like a charm!

I don't know what you expect, and I don't think this should be a feature.
If you want an "always on" default filter, use the list filter prop.
Can you explain me your use case?

Use-case:

Show list of users
Buy default show only "Active" users(using filter)
"Admin-on-rest customer" can be able to see all users(disable filter)

Maybe it not admin-on-rest functionality/feature, but I caught this unexpected behavior

I actually have the same issue: I need a date input filter always on and with a default value, but the default value doesn't apply to the input when set to alwaysOn.

Example:
export const MyFilter = (props) => (
    <Filter
      {...props}
      >
      <DateInput label="Before" source="start_stamp.leq" alwaysOn defaultValue={moment().endOf('day').format()} />
      <DateInput label="After" source="start_stamp.geq" defaultValue={moment().startOf('day').format()}/>
    </Filter>
);

Basically there's a componentShouldUpdate missing somewhere when alwaysOn is set..

Can't reproduce anymore on master


more options for speedTextFormat?

Is it possible to allow something else then INTEGER or FLOAT(like double or decimal)?

Added in V 1.3.0.


pausemenu none option in acts like a music file when carried over to 0.7.2

Describe your bug here.
Mind you, if you are modding, please try testing your bug in a clean version of the engine instead, this ensures the bug is actually caused by the engine itself.
crashes bc none acts like a music file when carried over to 0.7.2

Command Prompt/Terminal logs (if existing)
Uncaught Error: Error loading sound from file: ./assets/shared/music/none.ogg
Please report this error to the GitHub page: https://github.com/ShadowMario/FNF-PsychEngine

Are you modding a build from source or with Lua?
Not modding
Which branch of the engine are you using?
Latest (main)
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
none

i tryed changing then changing bac and this did not work

Should be fixed now, redownload 0.7.2h


build.sh broken with bash 4.4

With bash 4.4:
$ ./build.sh
$ echo $?
69

This is a problem because to use Realm at all, you at least need build.sh download-core or build.sh cocoapods-setup.
The issue seems to be in the way we expand -debug commands:
# Use Debug config if command ends with -debug, otherwise default to Release
case "$COMMAND" in
    *-debug)
        COMMAND="${COMMAND%-debug}"
        CONFIGURATION="Debug"
        ;;
    *) CONFIGURATION=${CONFIGURATION:-Release}
esac
export CONFIGURATION

based on my limited debugging putting print statements at various parts of the script 😅

build.sh is executed via /bin/sh if you run it as ./build.sh, so it should always be using the system version of Bash. That's been Bash 3.2 for some time now.
A different version of Bash can only be used if you're invoking it as sh build.sh or bash build.sh and happen to have a different version of sh or bash in your PATH ahead of the system version. It's not clear to me that there's any reason to support this scenario.

re-installing bash worked.

Got this issue again after installing Xcode 8.2 beta 2, and the solution was to accept the new license: sudo xcodebuild -license accept.


Update README.md

additionalOptions causes a gradle exception documentation is incorrect. The correct variable is additionalParameters.

see issue #9


Is there support for e.g. 5.12.x to get the most recent patches automatically?

I would like to use "version: 5.12.x" (or 5.12 or 5.12.*) for example to receive patches with fixes and security updates in the chosen (LTS) version line automatically.

There is not support for that, I don't think there is a good way to get the latest version automatically.

I believe this can be easily done in aqtinstall v2. Please see install-qt command § Command Line Options — aqtinstall 2.0.0 documentation.

Indeed aqtinstall v2/install-qt-action v3 supports this

What is the correct way to use this?
Which naming scheme is supported? @jurplel

Passing 5.12 should do it. I am updating the docs now.

Passing 5.12 should do it. I am updating the docs now.

Thanks you for adding the info to https://github.com/jurplel/install-qt-action#version

Passing 5.12 should do it. I am updating the docs now.

I run into some issues when using 6.3.
The action runs, but shows Error: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined at the very end.
When using 6.3.* that error does not appear. 🤔

¯_(ツ)_/¯
I will put in the docs to use 5.12.*

Both find and install 6.3.1 though, weird...
Resolved spec '6.3' to 6.3.1
Resolved spec '6.3.*' to 6.3.1
Below the "resolved spec" lines, the logs also say in both cases Specified Qt version is unknown: 6.3.1..
Same path error with 5.15, while it works with 5.15.* (both use 5.15.2 according to the logs, no "unknown Qt version" message)
Resolved spec '5.15' to 5.15.2
Resolved spec '5.15.*' to 5.15.2

Passing 5.12 should do it. I am updating the docs now.

I run into some issues when using 6.3. The action runs, but throws Error: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined at the very end.
When using 6.3.* that error does not appear. 🤔

Interesting. What happens if you use ”6.3”?
I am guessing that install-qt-action is interpreting 6.3 as a floating point number instead of a string; in that case maybe quotes would help. I think aqtinstall interprets this as a SimpleSpec whether you use quotes or not, which is why it can resolve the spec.

For the record, 6.3.x does also not work but returns this useful message:
aqtinstall(aqt) v2.1.0 on Python 3.7.9 [CPython MSC v.1900 64 bit (AMD64)]
Invalid version or SimpleSpec: '6.3.x'
See documentation at: https://python-semanticversion.readthedocs.io/en/latest/reference.html#semantic_version.SimpleSpec
Examples:
* "*": matches everything
* "5": matches every version with major=5
* "5.6": matches every version beginning with 5.6
* "5.*.3": matches versions with major=5 and patch=3

Maybe I should clarify that I do not input those values to the action directly.
I use a matrix setup to simplify the job creation across various Windows builds and use variables for the version. We do also use single quotes for the version already and I used them for all the above mentioned tests.
This is the working setup (matrix configuration):
      matrix:
        include:
          - target: Win-32bit
            arch: 32
            qt_version: '5.15.*'
            qt_arch: msvc2019

          - target: Win7+-64bit
            arch: 64
            qt_version: '5.15.*'
            qt_arch: msvc2019_64

          - target: Win10+-64bit
            arch: 64
            qt_version: '6.3.*'
            qt_arch: msvc2019_64
            qt_modules: "qt5compat qtmultimedia qtwebsockets"

With the install-qt-action step being:
      - name: Install Qt ${{matrix.qt_version}} for ${{matrix.target}}
        uses: jurplel/install-qt-action@v3
        with:
          cache: true
          version: ${{matrix.qt_version}}
          arch: win${{matrix.arch}}_${{matrix.qt_arch}}
          setup-python: false
          modules: ${{matrix.qt_modules}}

Interesting. What happens if you use ”6.3”?

Using "6.3" and "5.15" (instead '6.3' or '5.15') still results in:
Error: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
I also tried it without any quotes around the version number (6.3 and 5.15). Same error.
If I use 6.3.* and 5.15.* without any quotes, it does work though.
Either way, the log reveals that the action always receives the input version correctly:
Run jurplel/install-qt-action@v3
  with:
    version: 6.3

Run jurplel/install-qt-action@v3
  with:
    version: 6.3.*

Run jurplel/install-qt-action@v3
  with:
    version: 6.3.x

If I didn't miss something, that should wrap up to:

Using x in versions as placeholder does not work (also see SimpleSpec docs)
Globes do work in versions (tested for PATCH only)
Defining only MAYOR.MINOR does not work (even though aqtinstall reports that it should!)
Quotes doesn't matter for version (single, double or none)