Add ToInt32(ReadOnlySpan)

public static int ToInt32(ReadOnlySpan value)

Can you provide a link to the method documentation?

https://learn.microsoft.com/en-us/dotnet/api/system.bitconverter.toint32?view=net-7.0

You cannot polyfill static methods on existing types.


Add new custom domains for DOMANI spaces

Add new custom domain for dextfprotocol.eth
Add custom domain for new space domanidao.eth

Following the documentation, I did:

added the CNAME records for governance.dao.domani.finance and governance.domani.finance (value snapshotpage.b-cdn.net)
called https://ina9pk8175.execute-api.us-west-2.amazonaws.com/dev?domain=governance.dao.domani.finance and https://ina9pk8175.execute-api.us-west-2.amazonaws.com/dev?domain=governance.domani.finance to activate the domains

Anyway I get an "Internal server error" for both calls.

I also noticed that now the custom domains https://governance.domani.finance and https://governance.dao.domani.finance bring to the snapshot directory with the list of all spaces


Term request: phosphorus  in soil package

same format as elements in misc and sediment packages
New term details
For us to assess a new term request we require the following details:
Term name -
Structured comment name - [a less than 20char no spaces version of the name]
Definition - [a clear and concise description of the term including ]
Expected value - [e.g. text or EFO and/or OBI etc...]
Value syntax - [e.g. {float} {unit}|{termLabel} {[termID]}|{text}|{timestamp} etc...]
Example - [provide and example value]
Preferred unit - [if appropriate]
Package(s) - [list any packages that should include the new term]

Additional context
Add any other context about the new term here.

We need to assess this in respect to the existing term "tot_phosp"
Term name- total phosphorus
Structured comment name - tot_phosp
Definition - Total phosphorus concentration in the sample, calculated by: total phosphorus = total dissolved phosphorus + particulate phosphorus
Expected value - measurement value
Value syntax - {float} {unit}
Example - 0.03 milligram per liter
Preferred unit - milligram per liter
Package(s) -hydrocarbon resources-cores, hydrocarbon resources-fluids/swabs, wastewater/sludge, water

should we add this new term?
Term name - Phosphorus
Structured comment name - phosphorus_conc
Definition - concentration of phosphorus in the sample
Expected value -
Value syntax -
Example - [provide and example value]
Preferred unit - [if appropriate]
Package(s) - [list any packages that should include the new term]
hydrocarbon resources-cores, hydrocarbon resources-fluids/swabs, microbial mat/biofilm, sediment, water, soil

We need to assess this in respect to the existing term "tot_phosp"
Term name- total phosphorus
Structured comment name - tot_phosp
Definition - Total phosphorus concentration in the sample, calculated by: total phosphorus = total dissolved phosphorus + particulate phosphorus
Expected value - measurement value
Value syntax - {float} {unit}
Example - 0.03 milligram per liter
Preferred unit - milligram per liter
Package(s) -hydrocarbon resources-cores, hydrocarbon resources-fluids/swabs, wastewater/sludge, water

should we add this new term?
Term name - Phosphorus
Structured comment name - phosphorus_conc
Definition - concentration of phosphorus in the sample
Expected value -
Value syntax -
Example - [provide and example value]
Preferred unit - [if appropriate]
Package(s) - [list any packages that should include the new term]
hydrocarbon resources-cores, hydrocarbon resources-fluids/swabs, microbial mat/biofilm, sediment, water, soil


Fix tests with modulesync 7.2.0

Pull Request (PR) description
Resolving spec and acceptance issues
This Pull Request (PR) fixes the following issues
Fixes #394

Could anyone please help me look at the failing acceptance tests here?
both CentOS 7 and Ubuntu 20.04 acceptance tests run fine locally.
For me both OracleLinux 7 and 8 fail locally with
Error: /Stage[main]/Postgresql::Server::Reload/Postgresql::Server::Instance::Reload[main]/Exec[postgresql_reload_main]: Failed to call refresh: invalid byte sequence in US-ASCII

I have been hacking the acceptance test in this PR to figure out why mysql won't start om ubuntu 20.04 ...
I finally think I found the issue by printing the journal.
https://github.com/voxpupuli/puppet-jira/actions/runs/7812854040/job/21311068344#step:6:1347
Does anyone know how to fix apparmor issues here?


Need memo field in ibc/applications/transfer/v1/MsgTransfer

Problem
Here, the MsgTransfer type does not have the memo field.
According the ICS spec, I think it should include the memo field, which is used for ibc-hook module of Cosmos-SDK.
This memo field is needed for advanced functionality, like cross-chain-swap.
Suggestion
I think the maintainers should include the latest proto files, and rebuild the TS types for juno network.
Then, it can include the new field - memo into the TS MsgTransfer type.

Agree thanks - I made an issue on CosmJS main repo, but forgot about just doing it here. Will look into and take this on thanks!

Update you can use the following snippet to use the transfer value and sign + broadcast if you still need it
https://github.com/Reecepbcups/ibc-anywhere-webapp/blob/main/src/routes/%2Bpage.svelte#L437-L469


added 10k bytes notice

Sounds good to me :) @eddiezane - in reference to the github issue you commented on about a week ago in regards to someone having issues with unique args.


Just wanted to thank you

This is working awesome. The most easy way to solve this issue.

Thanks!


Feature : Keep me logged In feature added

Issue that this pull request solves
Closes: #1127
Proposed changes
Keep me logged in feature added.
Types of changes
Put an x in the boxes that apply

[x] New feature (non-breaking change which adds functionality)

Screenshots

Other information
Any other information that is important to this pull request

Hey @Kajol-Kumari
Please review the pr

Hello @Kajol-Kumari
Please could you review it before Gssoc ends...? it's ends around 7pm

@Kajol-Kumari
Thank you... 😄


Proposal: context file describing the container info

When application is running within a container, there's no easy way to understand whether the application is Dockerized or not. Moreover, when querying the host name (for example, in Java: InetAddress.getLocalHost().getHostName()) the host name is represented by an integer, which is meaningless.
It will be very useful, especially for monitoring & diagnostics purposes, to be able to easily fetch (local file injected to the container fs on startup?) the container info, such as real host name, image name, container name and container ID.

There are several proposals for this type of thing. See https://github.com/docker/docker/issues?utf8=✓&q=is%3Aissue+is%3Aopen+introspection

Thanks closing as this is a dup.


ENGINEERING BLOG PART

Removed Contentful
Added Ghost and its content deliver package
Built the home for blogs, still some lorems in the bottom tho need to fix that
Single Page Hero Done, main content left to built...

NEED TO FIX GIT IGNORE AND TAG BUILDER FUNCTION


https://github.com/UE4SS-RE/RE-UE4SS/issues/17

#17
User should be able to open the console enabler without crashing. Current outcome is that game.exe crashes upon initialization of this module

Accidental open


consistent /DATASET qualifier names

Reported by ansley b manke on 4 Feb 2016 19:47 UTC
The /DATASET qualifier is on many commands.  But on some it's /DATASET, on others it's /DATA, and on a large number, just /D.
Let's make them all /DATASET
CONTOUR/D
LIST/D
PLOT/D
LOAD/D
DEFINE ATTRIBUT/D
VECTOR/D
STAT/D
SHADE/D
WIRE/D
POLYGON/D
CANCEL ATTRIBUT/OUTPUT/DATA
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2362

Comment by ansley.b.manke on 5 Feb 2016 01:21 UTC
It turns out that /D= is handled in get_context_mods rather than being handled in each command subroutine as a qualifier, so the short /D= was used to make parsing easier there.  It is simple enough to change the parsing a bit in get_context_mods to match /DATASET to 4 characters.
This is done, with new benchmark test, and otherwise changes the benchmark output only in the output of SHOW COMMANDS.
Sending        bench/bn_all.jnl
Adding         bench/bn_dataset_qualifier.jnl
Sending        fer/dat/xcommand_data.F
Sending        fer/gnl/get_context_mods.F


extern-ify some vars in ross-extern.h

In some cases, linker errors have ensued from duplicate symbols.

Thanks, I'm surprised we haven't been burned sooner...

Coverage increased (+21.65%) to 48.77% when pulling 8f47dd76691b5b98a384cd32350df914302997fd on JohnPJenkins:extern-vars into 2c33a7ade442e83618af9002591a04c58c8a9902 on carothersc:master.


ℋ  🏆 WORLD CUP SPORTS 🏆   Ỵ

Addon Manifest URL
https://worlcup.surge.sh/manifest.json
Addon Description
World Sports streams
Language of Content
No response
Choose Labels

[ ] anime
[ ] asian drama
[ ] bollywood
[ ] cartoons
[ ] debrid support
[ ] http streams
[X] live tv
[ ] metadata
[ ] misc
[ ] movies
[ ] music
[ ] nsfw
[ ] podcasts
[ ] radios
[ ] subtitles
[ ] torrents
[ ] tv shows
[ ] video games

What are the VIP Links?

they are just FHD links

they are just FHD links

But I can't access them, like I can't access Sport TV 1 VIP


Fix some conflicts with ASP.NET dependencies

Summary
The original PR #4716 missed a few pieces.

Need to include the WebMatrix DLLs in the new AspNetWebPages package, they were also updated.
Need to include DotNetNuke.Web.Mvc in the AspNetMvc package, since it relies on a particular version of MVC (another option would be adjusting the version range on the binding redirect, but that would only fix subsequent upgrades).
Move the HTTP module for MVC into the AspNetMvc package, since the pieces it relies on aren't included until after install.

Thank you soooo much for looking into this!
I will test a clean install and upgrade after it builds.
Just one little thing, where the removals of newlines in the comments in release.config and development.config intentional ?

No, the whitespace changes were done automatically by my editor, I've reverted those changes.

I'll be on my computer again in a bit - I can also do a test as soon as the build finishes.

I successfully installed the package and successfully upgraded from 9.9.1

Awesome @bdukes - I just downloaded and will test as well.


ruby: fix failing tests with Ruby 3.0

The tests were previously failing due to keyword argument changes in Ruby 3.0.

[ ] Did you create an Apache Jira ticket?  (not required for trivial changes)
[ ] If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"?
[x] Did you squash your changes to a single commit?  (not required, but preferred)
[ ] Did you do your best to avoid breaking changes?  If one was needed, did you label the Jira ticket with "Breaking-Change"?
[ ] If your change does not involve any code, include [skip ci] anywhere in the commit message to free up build resources.

Thanks!
There are some more errors, possible to fix these as well?
Primarily this one:

TypeError: can't convert SpecServerSocket to IO (SpecServerSocket#to_io gives NilClass)

but there's also some more warnings.

Thanks!
There are some more errors, possible to fix these as well?
Primarily this one:

TypeError: can't convert SpecServerSocket to IO (SpecServerSocket#to_io gives NilClass)

but there's also some more warnings.

I think that warning is from Ruby 2.5. I'm not seeing this test failure in Ruby 2.7.5 or 3.0.5.


why not clearInterval the Timers？

me defined one the flipclock:
var timer = $('#id').FlipClock(second, {
clockFace: 'MinuteCounter',
countdown: true,
})
why not clearInterval(timer)  ???
big god help me!!  thanks!!

Just closing old issues. New version of the library uses requestAnimationFrame, not intervals. clock.stop() will stop the timer.


bumping STS to match mssql dependency

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.001%) to 41.711%

Files with Coverage Reduction
New Missed Lines
%

src/sql/workbench/services/connection/browser/connectionDialogWidget.ts
1
73.44%

Totals

Change from base Build<PHONE_NUMBER>1:
-0.001%

Covered Lines:
30719

Relevant Lines:
68916

💛  - Coveralls


[CLI DX] Improve the output for tsc --init

Suggestion
As of 4.4, a run of tsc looks like:
$ /Users/ortatherox/dev/typescript/resolve-ts/node_modules/.bin/tsc --init
message TS6071: Successfully created a tsconfig.json file.

I propose instead we change this message to provide more context about a few key values which have been set:
Example
$ /Users/ortatherox/dev/typescript/resolve-ts/node_modules/.bin/tsc --init

Created a new tsconfig.json with:                                                 [    ]
                                                                                [  TS]
  strict: true
  target: es5
  module: commonjs
  esModuleInterop: true

You can learn more at https://aka.ms/tsconfig.json

The qualifiers for whether something should be included in the list is that showInSimplifiedHelpView: true and the value is not the default. In the case about target is es5 but the default is es3 for example.
The cute little right aligned logo is used in tsc --help so you can re-use that code.
It's worth noting that a user can pass in defaults via tsc --init --target es2017, but I think that occurs before the code where you would write this, so it's just context which might be useful for testing.
Exceptions
None that I can think of.

Hey @orta, i would like to try implementing it.

Sure, give it a shot - until there's a solid WIP PR it's open for anyone to give a shot.

Hi @orta! I’ve made some progress on this, but I’d appreciate some guidance as to whether I’m on the right track and how to deal with a couple problems I’m running into:
Getting serialized option value
I believe we’d want the new logic for outputting the set values to live in executeCommandLine.ts. One thing I struggled with is getting executeCommandLine.ts to know the serialized representation of some of the enums, for example going from ScriptTarget.ES5 to "es5". It seems like that logic is currently done in commandLineParser.ts in functions like serializeCompilerOptions - however, that function is currently unexported.
My current approach is to export that function so that I can use it in executeCommandLine.ts, but I’m unsure how chill it is to add an export like this. Is this a reasonable approach? Other options I considered were making an exported new version of generateTSConfig that also returns the compilerOptionsMap it uses or simply duplicating code into executeCommandLine.ts.
Determining if default
The other thing I’m struggling with is how to determine whether a config value is different from the default. I saw there's a defaultValueDescription property for options in commandLineParser.ts, but it's a description and not the value itself. For example, it uses "ES3" as the defaultValueDescription for target. However, running tsc --init --target ES3 would use "es3" as the value. This is a simple case where just doing a case-insensitive comparison would work, but it seems like there are more complex cases where defaultValueDescription doesn’t directly correspond to a value. For example declaration uses defaultValueDescription: Diagnostics.false_unless_composite_is_set.
Do you have suggestions for figuring out if a value isn’t a default? Should I be hardcoding something for the specific options listed in this issue?
I appreciate any help you can offer! And also, @AlexMunoz, if you've attempted this too and have any advice, let me know! Thanks!

Ace!
Re: Getting serialized option value
Exporting that function and marking it internal is 👍🏻 ( that might even mean I can opt in to sneakily re-use it in the playground too) - it's the same pattern use for convertToTSConfig
Determining if default
Interesting, I wonder if we can generate a 'blank' tsconfig object and compare the one generated by that with  the one we're about to make and see what the differences are there instead. Will look in the cod enow.

From a quick test it seemed like parseConfigFileTextToJson("blank.tsconfig.json", "{}") just returned a config of {}.
From what I can tell, it seems like an approach like generating a blank tsconfig wouldn't work because the default settings aren't applied at the tsconfig level, but at a later point. For example, the default setting for target is es3, and, correct me if I'm wrong,
it seems like that gets applied as the default here.
I think based on that it would be hard to know what the default for any given setting is without having to hardcode something like "for target, call getEmitScriptTarget with {} and see what we get back" (or alternately just hardcode that the default for target is es3).
I think this gets particularly complex for settings like module where the default seems to depend on other settings.
For settings that depend on others like that perhaps we could do something like getEmitModuleKind({...compilerOptions, module: undefined}) to find what the default would normally be for the other settings that are being used 🤔
I'd appreciate any thoughts you have - I'm not sure if I'm overcomplicating something here or if this is actually complicated!

Hi @orta, following up to see if you have any further suggestions! I'm still interested in taking this on, but was feeling blocked on how to figure if a setting is different from the default.

Ah sorry - this issue isn't assigned to me, so it falls through some of my email filters. Some great questions,  after digging through the code I think maybe it's worth thinking about it from scratch again. From a design perspective:
tsc --init

Should show the diff from the blank tsconfig.
tsc --init --target es2015

Should show es2015 for target, instead of the current es5.
tsc --init --preserveConstEnums false

We probably want to also include preserveConstEnums in that output. For confirmation that it was registered.
This means we have two sets of inputs we want to show, and instead of trying to take two tsconfigs and resolve the difference, we can instead use the known sets of changes and work to present them. So we have this code in the compiler:
export const defaultInitCompilerOptions: CompilerOptions = {
        module: ModuleKind.CommonJS,
        target: ScriptTarget.ES5,
        strict: true,
        esModuleInterop: true,
        forceConsistentCasingInFileNames: true,
        skipLibCheck: true
    };

Which is the tsc --init defaults and generateTSConfig(options: CompilerOptions  this options param which should only contain params passed into the CLI (e.g. preserveConstEnums and target above) - so in theory we should be able to use the list of all defaultInitCompilerOptions and options key: values to show the diff. That should reduce the complexity a bunch.
If you struggle to find a way to go from ScriptTarget.ES2015 (1) to "es2015" leave that to me, and I'll figure that out and make something general, it can just print the number
Maybe then we drop the requirement that showInSimplifiedHelpView be set to be true, because then it could act inconsistent with your CLI input.

Hi @orta, @wizered67  I have tried to fix this, not sure if this is the right way. If you have any advice, let me know.


Add changelog

^

@tulios I added a changelog, but for every pull request we should bump version and edit changelog. what do you think? what about old PRs merged without bumping version?


CAS 5.0 - SAML RelayState not returned

I have included the following in my report:

[X] CAS server version: 5.0.0
[X] Container/environment type/version (Tomcat, Jetty, Java, Linux/Windows, etc): apache-tomcat-8.5.5 on Solaris 11
[X] Steps to duplicate the problem: 1. enable SAML IdP, 2. register Dropbox SP, 3. Try to get Linking Code from Dropbox via any native App, 4. Dropbox will use RelayState in SP initiated SSO to remember target page on POST Calback, 5. see RelayState is droped on constructing service URL and on postback
[X] Configuration/Overlay pushed to https://github.com/cas-projects/cas-issues/: not yet
[X] Mailing-List: https://groups.google.com/a/apereo.org/forum/#!topic/cas-user/p9OPOkJu2D4

Yup. Definitely an issue. Thank you.
Followup: is the Dropbox integration broken with this issue or do you just not end up on the requested page but can login nonetheless?

Dropbox works, but you land on the main page, which breaks all native
clients trying to get a linking code from Dropbox.
Am 25. November 2016 5:18:20 nachm. schrieb Misagh Moayyed
<EMAIL_ADDRESS>
Yup. Definitely an issue. Thank you.
Followup: is the Dropbox integration broken with this issue or do you just
not end up on the requested page but can login nonetheless?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apereo/cas/issues/2148#issuecomment-262990072

It would be helpful if you also could attach full debug logs so this can be traced. If not I think we can easily duplicate this with any SP that deals with relay-state.

I have already quick fixed it in our 5.0.0 overlay. Im already out of
office, but can have a look on it again on monday.
Am 25. November 2016 5:20:27 nachm. schrieb Misagh Moayyed
<EMAIL_ADDRESS>
It would be helpful if you also could attach full debug logs so this can be
traced. If not I think we can easily duplicate this with any SP that deals
with relay-state.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apereo/cas/issues/2148#issuecomment-262990399

Sure. Look forward to it.

@rkorn86 any particular updates on this?

sorry, did not had the time yet. i will send you additional infos later
this week based on current 5.1 snapshot.
Am 29.11.2016 um 16:14 schrieb Misagh Moayyed:

@rkorn86 https://github.com/rkorn86 any particular updates on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apereo/cas/issues/2148#issuecomment-263597166, or
mute the thread
https://github.com/notifications/unsubscribe-auth/ADqEG2lAA_eUQHnBnH_p93FhVBuQBx8cks5rDEFmgaJpZM4K8VnQ.

Here are some logs of a non-working 5.1.0-SNAPSHOT, PR will follow.
2016-12-02 10:24:18,643 DEBUG [org.opensaml.messaging.decoder.servlet.BaseHttpServletRequestXMLMessageDecoder] - <Beginning to decode message from HttpServletRequest> 2016-12-02 10:24:18,647 DEBUG [org.opensaml.saml.saml2.binding.decoding.impl.HTTPRedirectDeflateDecoder] - <Decoded RelayState: eyJwcm92aWRlcl91cmwiOiAiaHR0cHM6Ly9pZHAtZGV2Lmdmei1wb3RzZGFtLmRlL2Nhcy9pZHAvcHJvZmlsZS9TQU1MMi9SZWRpcmVjdC9TU08iLCAiYXJncyI6IHsiZXhwZWN0ZWRfZW1haWwiOiAicmtvcm5AZ2Z6LXBvdHNkYW0uZGUifSwgImtleSI6ICJmcm9tX2NsaWVudCJ9> 2016-12-02 10:24:18,750 DEBUG [org.apereo.cas.support.saml.web.idp.profile.SSOPostProfileHandlerController] - <Decoded SAML object [{urn:oasis:names:tc:SAML:2.0:protocol}AuthnRequest] from http request> 2016-12-02 10:24:18,750 DEBUG [org.apereo.cas.support.saml.web.idp.profile.SSOPostProfileHandlerController] - <Decoded SAML object [{urn:oasis:names:tc:SAML:2.0:protocol}AuthnRequest] from http request> 2016-12-02 10:24:18,754 DEBUG [org.apereo.cas.support.saml.web.idp.profile.SSOPostProfileHandlerController] - <Checking service access in CAS service registry for [Dropbox]> 2016-12-02 10:24:19,887 DEBUG [org.apereo.cas.support.saml.web.idp.profile.SSOPostProfileHandlerController] - <Built service callback url [https://idp-dev.example.com/cas/idp/profile/SAML2/POST/SSO/Callback.+?entityId=Dropbox&SAMLRequest=PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48c2FtbHA6QXV0aG5SZXF1ZXN0IHhtbG5zOnNhbWxwPSJ1cm46b2FzaXM6bmFtZXM6dGM6U0FNTDoyLjA6cHJvdG9jb2wiIEFzc2VydGlvbkNvbnN1bWVyU2VydmljZVVSTD0iaHR0cHM6Ly93d3cuZHJvcGJveC5jb20vc2FtbF9sb2dpbiIgSUQ9ImlkLTJiODQ3ZDI4MjM2ODRjMDU4YjdmYWJlZjZmZjk3ZjEzIiBJc3N1ZUluc3RhbnQ9IjIwMTYtMTItMDJUMDk6MjQ6MThaIiBQcm90b2NvbEJpbmRpbmc9InVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDpiaW5kaW5nczpIVFRQLVBPU1QiIFZlcnNpb249IjIuMCI%2BPHNhbWw6SXNzdWVyIHhtbG5zOnNhbWw9InVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDphc3NlcnRpb24iPkRyb3Bib3g8L3NhbWw6SXNzdWVyPjxzYW1scDpOYW1lSURQb2xpY3kgQWxsb3dDcmVhdGU9InRydWUiIEZvcm1hdD0idXJuOm9hc2lzOm5hbWVzOnRjOlNBTUw6MS4xOm5hbWVpZC1mb3JtYXQ6ZW1haWxBZGRyZXNzIi8%2BPC9zYW1scDpBdXRoblJlcXVlc3Q%2B]> 2016-12-02 10:24:19,887 DEBUG [org.apereo.cas.support.saml.web.idp.profile.SSOPostProfileHandlerController] - <Created service url [https://idp-dev.example.com/cas/idp/profile/SAML2/POST/SSO/Callback.+?entityId=Dropbox&SAMLRequest=PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48c2FtbHA6QXV0aG5SZXF1ZXN0IHhtbG5zOnNhbWxwPSJ1cm46b2FzaXM6bmFtZXM6dGM6U0FNTDoyLjA6cHJvdG9jb2wiIEFzc2VydGlvbkNvbnN1bWVyU2VydmljZVVSTD0iaHR0cHM6Ly93d3cuZHJvcGJveC5jb20vc2FtbF9sb2dpbiIgSUQ9ImlkLTJiODQ3ZDI4MjM2ODRjMDU4YjdmYWJlZjZmZjk3ZjEzIiBJc3N1ZUluc3RhbnQ9IjIwMTYtMTItMDJUMDk6MjQ6MThaIiBQcm90b2NvbEJpbmRpbmc9InVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDpiaW5kaW5nczpIVFRQLVBPU1QiIFZlcnNpb249IjIuMCI%2BPHNhbWw6SXNzdWVyIHhtbG5zOnNhbWw9InVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDphc3NlcnRpb24iPkRyb3Bib3g8L3NhbWw6SXNzdWVyPjxzYW1scDpOYW1lSURQb2xpY3kgQWxsb3dDcmVhdGU9InRydWUiIEZvcm1hdD0idXJuOm9hc2lzOm5hbWVzOnRjOlNBTUw6MS4xOm5hbWVpZC1mb3JtYXQ6ZW1haWxBZGRyZXNzIi8%2BPC9zYW1scDpBdXRoblJlcXVlc3Q%2B]> 2016-12-02 10:24:19,888 DEBUG [org.apereo.cas.support.saml.web.idp.profile.SSOPostProfileHandlerController] - <Redirecting SAML authN request to "[https://idp-dev.example.com/cas/login?service=https%3A%2F%2Fidp-dev.example.com%2Fcas%2Fidp%2Fprofile%2FSAML2%2FPOST%2FSSO%2FCallback.%2B%3FentityId%3DDropbox%26SAMLRequest%3DPD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48c2FtbHA6QXV0aG5SZXF1ZXN0IHhtbG5zOnNhbWxwPSJ1cm46b2FzaXM6bmFtZXM6dGM6U0FNTDoyLjA6cHJvdG9jb2wiIEFzc2VydGlvbkNvbnN1bWVyU2VydmljZVVSTD0iaHR0cHM6Ly93d3cuZHJvcGJveC5jb20vc2FtbF9sb2dpbiIgSUQ9ImlkLTJiODQ3ZDI4MjM2ODRjMDU4YjdmYWJlZjZmZjk3ZjEzIiBJc3N1ZUluc3RhbnQ9IjIwMTYtMTItMDJUMDk6MjQ6MThaIiBQcm90b2NvbEJpbmRpbmc9InVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDpiaW5kaW5nczpIVFRQLVBPU1QiIFZlcnNpb249IjIuMCI%252BPHNhbWw6SXNzdWVyIHhtbG5zOnNhbWw9InVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDphc3NlcnRpb24iPkRyb3Bib3g8L3NhbWw6SXNzdWVyPjxzYW1scDpOYW1lSURQb2xpY3kgQWxsb3dDcmVhdGU9InRydWUiIEZvcm1hdD0idXJuOm9hc2lzOm5hbWVzOnRjOlNBTUw6MS4xOm5hbWVpZC1mb3JtYXQ6ZW1haWxBZGRyZXNzIi8%252BPC9zYW1scDpBdXRoblJlcXVlc3Q%252B]"> 2016-12-02 10:24:20,853 DEBUG [org.apereo.cas.support.saml.services.SamlIdPEntityIdAuthenticationRequestServiceSelectionStrategy] - <Located entity id Dropbox from service authentication request at https://idp-dev.example.com/cas/idp/profile/SAML2/POST/SSO/Callback.+?entityId=Dropbox&SAMLRequest=PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48c2FtbHA6QXV0aG5SZXF1ZXN0IHhtbG5zOnNhbWxwPSJ1cm46b2FzaXM6bmFtZXM6dGM6U0FNTDoyLjA6cHJvdG9jb2wiIEFzc2VydGlvbkNvbnN1bWVyU2VydmljZVVSTD0iaHR0cHM6Ly93d3cuZHJvcGJveC5jb20vc2FtbF9sb2dpbiIgSUQ9ImlkLTJiODQ3ZDI4MjM2ODRjMDU4YjdmYWJlZjZmZjk3ZjEzIiBJc3N1ZUluc3RhbnQ9IjIwMTYtMTItMDJUMDk6MjQ6MThaIiBQcm90b2NvbEJpbmRpbmc9InVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDpiaW5kaW5nczpIVFRQLVBPU1QiIFZlcnNpb249IjIuMCI%2BPHNhbWw6SXNzdWVyIHhtbG5zOnNhbWw9InVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDphc3NlcnRpb24iPkRyb3Bib3g8L3NhbWw6SXNzdWVyPjxzYW1scDpOYW1lSURQb2xpY3kgQWxsb3dDcmVhdGU9InRydWUiIEZvcm1hdD0idXJuOm9hc2lzOm5hbWVzOnRjOlNBTUw6MS4xOm5hbWVpZC1mb3JtYXQ6ZW1haWxBZGRyZXNzIi8%2BPC9zYW1scDpBdXRoblJlcXVlc3Q%2B>

I have run into this issue with our production CAS 5 server. Can you provide me with the overlay changes you made so that we can get past this until we can test and configure a 5.1 server in the future? @rkorn86

Guys, can this change be moved into 5.0.x branch ? Without this, we cant use IDP in 5.0.3 :( Thanks

Thanks Moayyed. I see that there is another pull request: https://github.com/apereo/cas/pull/2156


astah-community: init at 7.2.0

Motivation for this change
This adds Astah Community 7.2.0: an UML modeler.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@Mic92 Thanks for the review!
The requested changes were amended to the commit.

Thanks!


TypeError if a possible result isn't in the format [Image Dimensions] [Type]

Good morning/afternoon/evening,
I'd like to report what is likely a bug due to IQDB (or rather, probably Gelbooru) rarely returning an [Unrated] without any image dimensions specified, which in turn makes line 186 in api.js fail with a TypeError, as dimensionTexts[1] ends up being undefined.
function parseResultsPage($, $pageEl) {
  // ...
  const $dimensionEl = $($rows[$matchEl.length + 2]).find('td');
  const dimensionTexts = $dimensionEl.text().trim().split(' ');
  const dimension = dimensionTexts[0].replace(/[^\d]/g, '-').split('-');
  const width = parseInt(dimension[0]);
  const height = parseInt(dimension[1]);
  const type = dimensionTexts[1].substring(1, dimensionTexts[1].length - 1).toLowerCase(); // error occurs here
  const $similarityEl = $($rows[$matchEl.length + 3]).find('td');
  const similarityTexts = $similarityEl.text().trim().split(' ');
  // ...

Edit: I just cross-checked with the code in the repository, it corresponds to line 214 in api.ts.
// dimensionTexts[1] is undefined, therefore .substring() causes a TypeError
const type = dimensionTexts[1].substring(1, dimensionTexts[1].length - 1).toLowerCase()

As seen here, the dimensionTexts aren't in the format WidthXHeight [Type], but just [Type]:

while the code assumes that the result should look like this:

Amazing library otherwise! Cheers.

Thank you very much for your feedback. This bug has been confirmed!

This bug was fixed in v0.2.1


Add failing test for __env_promise compile failure

This compiles in Clang, but not GCC 11.

I think this would be fixed if ex::__env_promise<ex::__empty_env> did not satisfy receiver, which is true in R7 world. I'm not sure if there's another constraint/short circuit missing somewhere else though.

I think this would be fixed if ex::__env_promise<ex::__empty_env> did not satisfy receiver, which is true in R7 world.

Yup. I think the solution is to start moving in the direction of R7, with an explicit opt-in to the receiver concept. Then __env_promise can unequivocally state that is is not a receiver.

#753 fixes a bunch of problems this PR exposed. Thanks! I've cherry-picked your commit into that branch and will close this PR.


Facet filter Component needs a reset + needs to show filters applied

Would it make sense to make the selection view a component that you could put on these pages? This would display all filters currently applied, and would allow removing them.

That's a great idea.

Ah, I forgot about this one. Will put it on the list. I hope to get to most of these things for republic of letters this afternoon...


feat(prql-python)!: use Sql(None) for default Target and allow CompileOptions without target argument

Part of #1855
Update to fall back to the target specified in the query header if no target is specified.

This is the same content as #1856, so merge for now.
Please let me know if there are any problems.


Error when running PWD locally

Hi, I've got the following error when running the tests. I also got the same one when running PWD locally via Docker Compose. Seems this is linked to go 1.8.1 (instead of 1.7.1 that is the recommended one).
$ go version
go version go1.8.1 darwin/amd64

$ go test ./...
# github.com/franela/play-with-docker/services
services/docker.go:81: undefined: types.ServiceInspectOptions
services/docker.go:81: too many arguments in call to i.dockerClient.ServiceInspectWithRaw
	have ("golang.org/x/net/context".Context, string, <T>)
	want ("github.com/docker/docker/vendor/golang.org/x/net/context".Context, string)

Try to update your docker repo.


browser entry field in the package.json file is incorrect.

Describe the bug
All the packages have the browser entry field set to build/umd/index.production.min.js but the rollup config is outputting build/umd/index.production.js
The above issue causes a problem when trying to import any package with parcel bundler.
To Reproduce
Expected behavior
Parcel should be able to resolve to correct file specified in the browser entry field.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: mac
Browser: chrome
Version: [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser: [e.g. stock browser, safari]
Version: [e.g. 22]

Additional context
Add any other context about the problem here.

I think this also causes issues with vitest:
Error: Failed to resolve entry for package "react-location". The package may have incorrect main/module/exports specified in its package.json: Failed to resolve entry for package "react-location". The package may have incorrect main/module/exports specified in its package.json.


Move llvm:Error types

Older compilers don't have the copy-elision rule of newer C++ compilers, resulting in an error message when returning a non-copyable type. Move llvm::Error instead of copying it.
/home/ewilde/work/swift-project/swift/lib/Frontend/CachingUtils.cpp:93:16: error: call to deleted constructor of 'llvm::Error'
        return Err;
               ^~~
/home/ewilde/work/swift-project/llvm-project/llvm/include/llvm/Support/Error.h:184:3: note: 'Error' has been explicitly marked deleted here
  Error(const Error &Other) = delete;
  ^
/home/ewilde/work/swift-project/llvm-project/llvm/include/llvm/Support/Error.h:491:18: note: passing argument to parameter 'Err' here
  Expected(Error Err)
                 ^
/home/ewilde/work/swift-project/swift/lib/Frontend/CachingUtils.cpp:123:16: error: call to deleted constructor of 'llvm::Error'
        return Err;
               ^~~
/home/ewilde/work/swift-project/llvm-project/llvm/include/llvm/Support/Error.h:184:3: note: 'Error' has been explicitly marked deleted here
  Error(const Error &Other) = delete;
  ^
/home/ewilde/work/swift-project/llvm-project/llvm/include/llvm/Support/Error.h:491:18: note: passing argument to parameter 'Err' here
  Expected(Error Err)
                 ^

@swift-ci please smoke test

LGTM.


Is it possible to install the tweaks on Sony a3000?

I have an a3000 witch i use mostly for YouTube videos and it’s a pain to only records 29 min and 51 secs.
I tried to install the tweak several times with no luck.
Is it possible on the a3000 or is there some fw limitation?

The A3000 can probably be added. As a first step, we have to dump its firmware. If you're interested to help, here's what you can do:

If you're on windows, download the newest development build of pmca-console here.
Download 0x22030000.zip and place it in the same folder (no need to unpack).
Power on your camera and connect it over USB to your computer.
Open a command prompt and run the following command: pmca-console guess_firmware -f 0x22030000.zip
With a bit of luck, the script should find the model id of your camera.

Let me know if you need any help.

The A3000 can probably be added. As a first step, we have to dump its firmware. If you're interested to help, here's what you can do:

If you're on windows, download the newest development build of pmca-console here.
Download 0x22030000.zip and place it in the same folder (no need to unpack).
Power on your camera and connect it over USB to your computer.
Open a command prompt and run the following command: pmca-console guess_firmware -f 0x22030000.zip
With a bit of luck, the script should find the model id of your camera.

Let me know if you need any help.

I’m actually a Mac user, but i do have a Windows laptop laying around. I’ve tried the pmca-console of the link you provided, but it consistently crashes every single time as soon as it opens. My laptop runs on the newest windows 10 version.

@leoleo-s You have to run the program in the windows command line. Place the .exe file and the .zip file in the same directory, open the command line, run cd C:\path\to\the\directory and then run pmca-console-v0.17-51-g52f5c6f-win.exe guess_firmware -f 0x22030000.zip

Hi Probably few years too late, but i own this camera and i could help if you are still intrested. :)


[Bug Report] DatePicker issues with certain display values

Element UI version
2.10.1
OS/Browsers version
Win10 / Chrome v75.0.3770.100
Vue version
2.6.10
Reproduction Link
https://jsfiddle.net/Terrijoo/6boy5puf
Steps to reproduce
Enter the field and type "20190709" and press TAB
What is Expected?
The value being converted to "2019-07-09"
What is actually happening?
The value gets deleted.
Additional Information:
A lot of our customers use it as a "short" way of entering a date on a numpad (german format, and there's no "." on the numpad - so like "09072019" is easier to enter than "09.07.2019")
This seems to have broken on around 2.9.x, since it was still working in 2.8.2.
Working example of 2.8.2:
https://jsfiddle.net/Terrijoo/6boy5puf/2/
This can also be reproduced on the document sites:
https://element.eleme.io/2.8/#/en-US/component/date-picker -- works
https://element.eleme.io/2.9/#/en-US/component/date-picker -- doesn't work
Or am I overseeing a config that enables it again?

#16713 一样的问题


lineage: check if CI job is complete before fetching data

If the data is fetched before the dot file is ready, the UI goes blank and doesn't seem to recover on its own

Related to error handling in general (#136).


Check in the background if the deployment server is reachable

Closes #1444

From the users point of view, I'd suggest that we align the default hint with the error hint: When is which one needed? Do we need to display the default hint at all.
Indeed, with the validation on start the default hint might never be useful. On the other hand, otherwise the user might not know what URL field is about. Anyway, I just pushed a change which disables the hint at all. Let's see how it feels now.

TODO:

Re-run the connection check when the window with the dialog is focused.
Fix missing credentials error.

Postponing this until we finish the experiments with the new extensions API. Probably lots of the code will be changed, including the contributions prepared within this PR.

Implemented and merged the feature via https://github.com/camunda/camunda-modeler/pull/1491


Requester pays modal with no billing project [SATURN-862]

Draft PR, depends on SATURN-117

Closing this PR as the changes are going in with https://github.com/DataBiosphere/terra-ui/pull/1701


Minor documentation edits

Some small clarifications / spelling / grammar fixes
Add a link from the README to the rendered documentation

Thanks a lot!


archivist: scan and per-query options

Added a scan method to archivist, and updated the documentation accordingly.
Per-query option for mget. Query options will be merged with the options passed to the mget call.

Updated PR to include the possibility to add per-query options.


SPM support

Thank you @arturgrigor.

@arturgrigor I've this error:

I'm doing something wrong?

PKHUD SPM Test.zip
@PGLongo I'm not sure, but you can check and run this small demo with Xcode 12 and everything should work just fine.

Please can you try to install PKHUD with SPM?

@PGLongo
I did that by running the following commands:
mkdir pkhud-spm-test
cd pkhud-spm-test
swift package init
vi Package.swift; here I added a ".package(url: "https://github.com/pkluz/PKHUD.git", .upToNextMinor(from: "5.4.0"))," to the dependencies section, and listed "PKHUD" in the "pkhud-spm-test" target's dependencies
swift package update
swift package generate-xcodeproj

And everything worked just fine.

@PGLongo I got that same problem earlier on a build machine because they are still using Xcode 11 and this library requires Xcode 12 due to the images that come with it and bundling resources into the library is only available in Xcode 12.


Service Request by [Jessica ] on editing in for Green County in the IPA tracker

[x] Qualtrics Service Request Form was received from User
[x] e-mail acknowledging that User's Qualtrics Service Request Form was sent
[x] Problem NOT RESOLVED
[ ] Problem PARTIALLY RESOLVED
[ ] Problem FULLY RESOLVED and Issue is Closed
[ ] Qualtrics Post-Service Request Survey was sent to User

Use comments feature (below) to document:

A clear and concise description of the solution.

A clear and concise description of any alternative solutions or features you've considered.

Any additional context, such as screenshots about the problem.

From: Jessica Neufeld<EMAIL_ADDRESS>Date: Tuesday, January 11, 2022 at 12:18 PM
To: Donrie Purcell<EMAIL_ADDRESS>David Lounsbury<EMAIL_ADDRESS>Subject: IPA Tracker issue - Editing Measures
CAUTION: This email comes from an external source; the attachments and/or links may compromise our secure environment. Do not open or click on suspicious emails. Please click on the “Phish Alert” button on the top right of the Outlook dashboard to report any suspicious emails.
Hi Donrie and David,
I submitted an issue I'm having via the tracker Support site. This was related to editing the measures for data collection in Greene's IPAs. Do you know when this might be addressed? There is no immediate urgency, but I would like to anticipate the timeline.
Thanks,
Jessica
--
Jessica Neufeld, MPH
Program Manager
HEALing Communities Study
Social Intervention Group
Columbia University School of Social Work
1255 Amsterdam Avenue
New York, NY 10027
<EMAIL_ADDRESS>Website:  https://sig.columbia.edu/

Hi Jeff
Please see the error code below:

Hi Jeff:
DP and I see are each replicating this issue. Seems to be just for Greene County.
Can you address ASAP??
Best,
DL

From: Jeff Bazinet<EMAIL_ADDRESS>Sent: Wednesday, January 12, 2022 3:31 PM
To: Donrie Purcell<EMAIL_ADDRESS>Cc: David Lounsbury<EMAIL_ADDRESS>Subject: Re: Issues within Green county

CAUTION: This   email comes from an external source; the attachments and/or links may   compromise our secure environment. Do not open or click on suspicious emails.   Please click on the “Phish Alert” button on the top right of the Outlook   dashboard to report any suspicious emails.
Yeah. This is the same issue that's been reported quite a few
times. The fact of the matter is that at one point, they created a measure. We
have since disallowed that capability and the measure they created is not in
the list options for that type of measure.
The best way to fix this is to add the measures for that strategy
to the list options. They should match exactly.
This error should never
appear in wave 2 because you're never allowing them to enter their own
measures.

From: Donrie Purcell<EMAIL_ADDRESS>Sent: Wednesday, January 12, 2022 3:17:25 PM
To: Jeff Bazinet<EMAIL_ADDRESS>Cc: David Lounsbury<EMAIL_ADDRESS>Subject: Issues within Green county

This
Message is being sent from outside of FDRHPO or NCI.  Please do not click
on links or download attachments without properly verifying them.

Hi
Jeff

Jessica
has reported that her team at Green County has not been able to effectively
edit Measures in Specification.

I
have placed an error code in the email for you to review.

Regards
Donrie Purcell, PhD, MPH

Every generation has the
obligation to free men's minds for a look at new worlds,....to look out from a
higher plateau than the last generation.
Ellison S. Onizuka

<![if !supportLineBreakNewLine]>
<![endif]>

Yeah. This is the same issue that's been reported quite a few times. The fact of the matter is that at one point, they created a measure. We have since disallowed that capability and the measure they created is not in the list options for that type of measure.
The best way to fix this is to add the measures for that strategy to the list options. They should match exactly.
This error should never appear in wave 2 because you're never allowing them to enter their own measures.

Thanks for this information. So, we should be able to add the measure they added to the list options, then the issue will go away, Correct?

@donriepurcell
If we Download the Data for Green, I expect that we will see the 'offending' Measure Name, and then we can add it to List Options. I would copy and paste it from the Download (as text), as a new Measures list option.
Can you give this a shot?
DL

The offending measure is "2.14 # of naloxone units distributed in community".
While this measure exists in the database, it is there for OEND, not MOUD, which is how their strategy has been defined..

Thank you @jbazinet1111
@donriepurcell  Can you follow up with Greene County about this next week?
@donriepurcell  We should not have these issues with Wave 2 if we have a clean, compete codebook of measures, and if we can effectively train users.
DL

Hi Jeff
Thanks for pointing out the issue previously. It took me a while to figure out that Green county had a strategy that should be in OEND, which was misplaced as an MOUD strategy.
David and I moved to edit the strategy, and I am closing this service request.
Regards
Donrie

From: Jessica Neufeld<EMAIL_ADDRESS>Sent: Thursday, January 27, 2022 5:27 PM
To: Donrie Purcell<EMAIL_ADDRESS>Cc: David Lounsbury<EMAIL_ADDRESS>Subject: Re: Green County

CAUTION: This   email comes from an external source; the attachments and/or links may   compromise our secure environment. Do not open or click on suspicious emails.   Please click on the “Phish Alert” button on the top right of the Outlook   dashboard to report any suspicious emails.
Hi
Donrie,
Thanks
for getting back to me.

So,
because the ORCCA bucket was mislabeled, it prevented editing from
happening to the measures?
I
feel like I haven't come across that issue before. Do you think it's specific
to Greene or has the potential to be an issue with all the counties?

Best,
Jessica

On
Wed, Jan 26, 2022 at 3:52 PM Donrie Purcell<EMAIL_ADDRESS>wrote:
Hi
Jessica,

I
want to apologize for taking some time to get back to you as it relates to
editing the IPA strategy within Green County.
It
appears from our discovery that the strategy in question was mislabeled as a
MOUD in the ORCCA EPB & EPB.
I
have attached a series of photos to indicate what was there previous to our
final change.

Regards
Donrie Purcell, PhD, MPH


Has there been any conversation about building Heimdall-rs using WebAssembly?

Component
Heimdall (Core)
Question
I have a vuejs project and trying to integrate heimdall-rs to do decompilation work. I was wondering if it's possible to build heimdall-rs into a JS module using WASM?
Open to any suggestion

Hey! Thank's for opening an issue :)
I honestly don't know enough about WASM to attempt this, but there have been a few people asking for it so I may attempt to figure it out some day. In the meantime, you can host heimdall on your backend using something like: #202

Hi @Jon-Becker, thanks for the reply! I strongly believe that building heimdal-rs into a JS bundle using WASM could offer significant benefits. Consider the wide range of use cases where Heimdal-rs can enhance client web applications, especially given that most are developed using popular JS frameworks like React, Vue, Angular, etc.
I've done lots of research on the decompilation issue, and my team and I were shocked to learn that there's no decent JS solutions for it. If we can successfully build Heimdal-rs using WASM and publish it as an NPM package, I believe it could garner significant attention and traction.

probably too much of a lift, not sure if worth it tbh.


Create a common Navbar and a footer

[x] Create two html pages for navbar and footer in /assets/content directory.

[x] Create a js script to load above components dynamically.

[x] Link the script to every page.

i'll do it

done pr #117

Thanks @Piumal1999 👍


Matrix-free slower than classsical matrix-assembled method

Hi guys,
I'm interested in the matrix-free (partial assembly) feature of MFEM. With partial assembly enabled, I tried a Jacobian smoother preconditioner, an LOR preconditioner, as well as precondition by the assembled high-order matrix.
However, each CG iteration step costs more time than the classical method with 2nd order basis. I thought it's normal that matrix-free solver requires more iterations, but it's supposed to be faster in each matrix-vector multiplication.
For example, I test Poisson' equation on a 3d fichera mesh with 4th order basis function. Classical FEM solver with GSSmoother requires 80 iterations and 36 seconds. Matrix-free CG solver requires 80 iterations and 47 seconds preconditioned by assembled matrix, 138 iterations and 45 seconds preconditioned by LOR, and 195 iterations and 59 seconds preconditioned by OperatorJacobiSmoother.
It seems the matrix-vector evaluation of matrix-free methods are not (very) faster than sparse matrix-vector multiplication.
Is the basis order too low to observe the improvement of matrix-free method? Or it is hard to observe without AVX vectorization?

Was this on one of MFEM's examples? How big was the problem you tested in terms of DOFs? I assume you are running on CPU?

I was running ex1 and add different preconditioners for it. The DoFs are about 24 million. I'm running on CPU inside a vmware virtual machine, but I would hope to run it on our solver with AVX-512 arichitecture eventually.
I noticed in ex26, multigrid preconditioner needs far less runtime than Jacobi smoother and LOR preconditioner. Do Nedelec and RT elements support multigrid methods in MFEM?

It looks like you are not using hypre preconditioners. For good performance you definitely want to use HYPRE's BoomerAMG (or AMS for H(curl) or ADS for H(div)) even if you run just on 1 processor.
For partial assembly (AssemblyLevel::PARTIAL) the best preconditioners should be (1) p-multigrid (illustrated in ex26p) using BoomerAMG as the coarse solver and (2) LOR + BoomerAMG solver (illustrated in miniapps/solvers/plor-solvers.cpp)
For H(div) and H(curl) problems, you can use LOR + ADS and LOR + AMS, respectively (illustrated in miniapps/solvers/plor-solvers.cpp). If the degree is not very high, for H(div) you can also try the hybridization solver (using BoomerAMG as the solver for the hybridized system) illustrated in ex4p.

If you want the best performance with partial assembly on CPU and you are solving H1 diffusion, you can try the template code, illustrated in miniapps/performance/ex1p.cpp -- you will need to instantiate the specific order you want in the source file -- it is a template parameter. This code is vectorized too, as long as you enable a compiler option like -march=native and use the config option MFEM_USE_SIMD=YES.

Thank you Dobrev. Eventually I hope to solve problems in H(curl) space with partial assembly methods. I'll look miniapps/solvers/plor-solvers.cpp first.

I compared the serial LOR preconditioner from performance/ex1.cpp and miniapps/solvers/lor_solvers.cpp for H1 space. With same refinement levels and basis function order, the LORSolver<GSSmoother> in lor_solvers.cpp is significantly faster than the GSSmoother preconditioner on lor bilinearform in performance/ex1.cpp.
option 1:
       BilinearForm *a_pc = NULL;
       SparseMatrix A_pc;

       Mesh mesh_lor;
       FiniteElementCollection *fec_lor = NULL;
       FiniteElementSpace *fespace_lor = NULL;
       int basis_lor = BasisType::GetType('G');
       mesh_lor = Mesh::MakeRefined(mesh, order, basis_lor);
       fec_lor = new H1_FECollection(1, dim);
       fespace_lor = new FiniteElementSpace(&mesh_lor, fec_lor);

       a_pc = new BilinearForm(fespace_lor);
       a_pc->AddDomainIntegrator(new DiffusionIntegrator(one));
       a_pc->UsePrecomputedSparsity();
       a_pc->Assemble();
       a_pc->FormSystemMatrix(ess_tdof_list, A_pc);

       GSSmoother M(A_pc);
       PCG(*A, M, B, X, 1, 400, 1e-12, 0.0);

and option2
       LORSolver<GSSmoother> solv_lor(a, ess_tdof_list);
       PCG(*A, solv_lor, B, X, 1, 400, 1e-12, 0.0);

The later needs 46 iterations, while the former needs 69. What's special about LORSolver that it's different to a GSSmoother with lor bilinearform as operator?

The later needs 46 iterations, while the former needs 69. What's special about LORSolver that it's more efficient than a GSSmoother with lor bilinearform as operator?

I haven't looked closely at the code that you posted, but my guess would be that this is because LORSolver uses collocated quadrature to assemble the low-order-refined system. It is counterintuitive (but true) that using a reduced quadrature for the low-order system gives you a better preconditioner for the high-order system with full quadrature (see e.g. this paper).

Hi @v-dobrev,
In fully assembled mode, I changed the order of cg.SetOperator() and cg.SetPreconditioner() and found that setting operator after preconditioner gives better convergence, though slower than original.
For example, when fichera.mesh is refined 3 times (Hcurl space, 304272 dofs, 4 processors) the number of iteration and the time to solve linear system is
669 and 33.1s with no precondition,
628 and 32.0s with Jacobi precondition,
24 and 23.6s with SetPreconditioner() first, and
49 and 11.7s with SetOperator().
I think preconditioner must be set later for partial assembly, but I wonder why setting preconditioner first gives less iterations.

The problem is solved in #4531 .


Use RNGCryptoServiceProvider instead of System.Random

https://devdiv.visualstudio.com/DevDiv/_workitems?id=244741&_a=edit
This was the only use of System.Random in the code base.
I don't know how to verify that this works as intended in the Search Client but I verified the code that I changed generates random numbers within the correct range.
This is not entirely fair, but I think the difference in fairness is probably very minimal.
What I mean is that when you generate only discrete bytes of randomness rather than discrete chunks of the size you want, you get uneven randomness. For example, if you were looking for a range of 0-2 but were generating 0-3 and used modulus when the generated number was too big, 0 would turn up 50% of the time and 1 and 2 would only show up 25% of the time each. However, I think because we are generating 8 bit chunks instead of 2 bits, the effect is much more minimal.
Also I didn't want to loop generating numbers that were out of range because this method is much slower than System.Random.
Let me know if you think there's a better solution to this or we can find a way to get rid of the randomness altogether.

Hi @scottbommarito, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

The randomness is part of our load balancing here. Not sure if we have to kill of System.Random here?

@maartenba Unfortunately the SDL task says "use only approved random number generators", not "use only approved random number generators when doing security-critical work"...so I think it's either do this or ask for an exception...

Ship it 😀

(forgot to tag more people)
@skofman1 @shishirx34 @ryuyu

:clock1:

The SDL only applies for crypto-operations :)
"This requirement applies to all Microsoft products and services that use random numbers for security purposes"
If it's not for security, then Random() is just fine.

@blowdart lol thanks

Don't let this stop you going through the SDL though :) This deserves a :cookie:


404 at: /docker-for-mac/index/

URL: /docker-for-mac/index/
followed the "Where to go next" link at the bottom of the Docker for Mac CE download page (https://store.docker.com/editions/community/docker-ce-desktop-mac?tab=description)

@tr2000 thanks so much, this is fixed now


CARDS-1394: The questionnaire wizard suggests invalid default values for the na/noneOfTheAbove options in long/double/decimal questions with list or list+input display

Known limitation: switching the data type from text to long (or other number type) after the answer options generated and displayed will not update the values of the special options to be numeric, because answer options are not re-rendered, preventing any data that has already been entered from being discarded. IMO this is ok for now and could be fixed later if it becomes a real usability issue.

Up for discussion: what numerical values are best for the special options? In this PR -1 is used for NA and 0 is used for None of the above. Feedback is welcome.

Double is misbehaving in view mode

I disabled predefined answer options for double questions in the questionnaire wizard in commit da7f521, since the number representation can cause a multitude of UI bugs including mis-identification of predefined options associated with a value.


Clarification for exchange and trade-in after 1/1/24

The blue box on this page gives the impression that for RI purchased after 1/1/24, both exchange to other RI and trade-in to a savings plan won't be possible. Elsewhere I have seen and heard that trade-in is expected to be possible after 1/1/24. Can you confirm which it is?

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

ID: b0221e55-a5ed-fb19-9347-b810b982e6ba
Version Independent ID: c26f55d1-b206-fcd6-218a-a08ef40e49d1
Content: Self-service trade-in for Azure savings plans - Microsoft Cost Management
Content Source: articles/cost-management-billing/savings-plan/reservation-trade-in.md
Service: cost-management-billing
Sub-service: savings-plan
GitHub Login: @bandersmsft
Microsoft Alias: **banders

@dohughes-msft Thank you for your patience in this matter!
RIs purchased after 1/1/24 cannot be exchanged.  RIs purchased prior to 1/1/24 can be exchanged only once after 1/1/24.
Background:
RI exchanges are essentially two transactions – cancel and purchase.  On 1/1/24, our RI purchase policy will no longer permit exchanges.  That is why RIs purchased on or after this date are not exchangeable.  RIs purchased prior to 1/1/24 were purchased under the old terms, so they can be exchanged an unlimited number of times, prior to the start of the new terms (1/1/24).  When the customer does a post-12/31/23 exchange, they would be effectively purchasing a new RI under the “no exchange” terms.
Please note that we will continue to allow RI exchanges for products that are end-of-life.
Hope this  answers your question!

@SadiqhAhmed-MSFT thank you but the question is not about RI exchange.
The question is how long will trade-in be permitted from RI to Savings Plan? Does it in any way revolve around 1/1/24 or is it completely separate?

@bandersmsft Thank you for confirming that, and the update. Just as a final note it still says "For a limited time you may trade-in your Azure compute reservations for a savings plan." just above your newly-added line which is a little contrary.


IvorySQL:When the sequence value in the inserted table is greater than the maximum value of the field type, the insert cannot be inserted

#342


Need for "sort" in product

I checked the issue with "sort" in "product" function, and it does not seem to play any role.
I ran test functions without "sort" operation, and the results were correct although the asserted values need to be changed to reflect the changed orders of variables.

Ahh I found an issue with the Transport example. I will look into it tomorrow.

I conclude that there is NO PROBLEM to remove the "sort" operation. Assertion errors simply occur from the different orderings of variables and rows in CPMs.


sequence section - omit 'CDS' for ncRNA genes

I just realized that we actually shouldn't call the sequence "CDS sequence" for non-coding RNA genes. I guess just label it "Sequence" instead.

This is done now.
See also: #461.


[style]: upgrading the boxes containing the data for projects

What's the style idea?
We need to improve the boxes and their style along with the background, the boxes are too close and leave the side spaces which looks a bit off, and it could also use some css upgradation to make it look more efficient.
Add screenshots
Add screenshots

the info box should look like this

and arranged like the boxes above with three in one row
Code of Conduct

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

like these short project info boxes are too plain, and can be updated. For example if you want someone to go to the site and open these projects, they will for sure be attracted by the catchy look of the info about it. Right now to be honest, it is a bit basic and just provides the info, I could edit the css, make it look more catchy to attract the attention of the viewers.

yes sure, by the way i am a part of gssoc'23

hey @sanchitaa14  we are working on redesigning the card so now we can close this issue


Book: Section 3B: Portability

From @jamesmunns on July 10, 2018 9:34
How can use of Rust improve portability between Projects, Targets, or even Operating Systems?
Copied from original issue: rust-embedded/wg#119

From @TotalKrill on July 30, 2018 9:26
I would really like to see some more graphical representation on how the different crates are thought to interact with the software, also some recommended guidelines for naming the crates so they are more easily found on crates.io. Example:
device crates should end with *-device, and board crates should end with *-board, driver crates should end with *-driver.
A graphical representation that basically says:

Device crate = MCU registers, peripherals, settings, timers etc
Board crate = Where SPI, UART etc are hooked up, what oscillators are running. ( are drivers a part of the board crate?)

Similar to this picture:

I addressed this topic briefly in my RustConf talk. I will at least dump all of my written notes in this section today.
https://ferrous-systems.github.io/rustconf-james-2018/#/58
I also attempted to cover why this is desirable, e.g. when you have N chips and M drivers, N*M is a much larger number than N+M implementations

Any attempt of trying to visualize this for me is a victory, it would help a lot for me to understand the scope of the embedded-hal traits. What i feel now is that embedded-hal traits are the arrows connecting everything.
Should board crates have the drivers? since the components are probably on the board. Just trying to show what should be replaced and what does not need to be replaced when porting hardware would be nice.
It would also feel easier for a new rust dev like me to understand the scope and roles of different crates and how to navigate the future huge embedded rust ecosystem.


Could you please share your processed dataset D_arena?

Could you please share your processed dataset D_arena?

Hi there! A similar dataset is available on HuggingFace at https://huggingface.co/datasets/lmsys/lmsys-arena-human-preference-55k.


Debug hang

Temporary PR to help with #39

@scjody ok if we close this?
We could maybe write down some info in the CONTRIBUTING.md file with a link to this PR

Yes, it's easy enough for me to re-create if needed.


WIP: schema validation and versioning

So far just adds some basic machinery for validating records against json schemas and validating that the schemas themselves are "self-describing" in the snowplow sense
Also adds a publishSchema cli command that will read a self-describing schema from a file, construct a WKI out of the schema's self object, and publish it to the mediachain.schemas namespace.
TODO:

[x] update publish command to accept a schema which will validate input objects
[x] link to schemas in published records
[ ] add schema object to deps for published statments
[ ] optionally validate fetched records against their schemas
[x] replace ad-hoc selection and filtering in publish command with jq "translator"

Just did some time and disk measurements, publishing 100K flickr records using compound statements of 100 records each, using eight workers.
master:
25.27 real        94.11 user         8.09 sys
25.27 real        93.72 user         7.96 sys
25.28 real        93.24 user         7.89 sys

# disk usage (in blocks of 512 bytes)
$ du ~/.mediachain/mcnode/{stmt,data}
58856	/Users/yusef/.mediachain/mcnode/stmt
61720	/Users/yusef/.mediachain/mcnode/data

schema branch:
25.31 real       113.47 user         9.35 sys
25.27 real       112.81 user         9.19 sys
25.26 real       113.82 user         9.67 sy

$ du ~/.mediachain/mcnode/{stmt,data}
67856	/Users/yusef/.mediachain/mcnode/stmt
71536	/Users/yusef/.mediachain/mcnode/data

So adding the schema reference to deps adds ~ 46 bytes per statement, and making the records "self describing" adds about 50 bytes per object.  Overall it's an increase of ~ 91 MB per 1MM records.
Time-wise, the cost of using jq for processing is fairly negligible; only about 6.6ms difference per 100k run, or 0.12 ms per record.  This is considerably better than earlier tests with non-compound statements, in which there was ~ 1 second difference for a 100K run between jq and non-jq branches.
Importantly, the tests above were done with --skipSchemaValidation, which makes the time measurements kind of misleading; I'm going to do a comparison with validation enabled in the hot path and see what we're working with there.  But the disk usage should be the same either way.

It looks like enabling schema validation in the publish command doesn't add as much time overhead as I expected:
schema branch, validation enabled:
26.33 real       142.87 user        10.13 sys
26.26 real       143.80 user        10.12 sys
26.30 real       144.45 user        10.22 sys

The per-record cost is about 5ms, although that would still add up over the course of a big ingestion.


[com.google.fonts/check/version_bump] font version should be checked against font in GF repo not GF API

Observed behaviour
Fontbakery didn't FAIL in https://github.com/google/fonts/pull/5539 although the PR merged was containing a font with the same version in google/fonts repository.
Expected behaviour
Currently this check is comparing font version against the font served by the API, when it should compare against the font in google/fonts repo, even of not published. The families go through several servers before being published on GF, and the font version is used to make sure if the font got pushed to these servers. If the font version is the same, then we need to open the font to see if the fix has been pushed, which is very time consuming and there could be mistakes.

It seems that this checked has been fixed since I opened this issue because I received this fail in https://github.com/google/fonts/pull/6280
🔥 FAIL: Version number has increased since previous release on Google Fonts? (com.google.fonts/check/version_bump)
🔥 FAIL Version number 1.001007080078125 is equal to version on Google Fonts.
🔥 FAIL Version number 1.001007080078125 is equal to version on Google Fonts GitHub repo.
Although it might be incomplete cause it fails even though the font file were not touched (only metadata.pb). So changing the title to make it more specific to that issue.

Although, the FAIL didn't get trigger in this PR: https://github.com/google/fonts/pull/6230
Which makes me think that it doesn't check the proper table. We want a different version number in the name table — compare to previous file in the main branch of the github repo.


Fixed REBELinBLUE/deployer#396

@REBELinBLUE The ace editor comment parser to highlight (TODO|HACK|XXX|FIXME) seems to be causing issue on code climate. Is it true for your master as well ? Any idea how i can skip this ?


Fix evaluation xval

Might lead to rare issues with say ContingencyTableEvaluation which used stored members to evaluate.
http://buildbot.shogun-toolbox.org/builders/CentOS7 - libshogun/builds/465/steps/test/logs/stdio

Thanks!

BTW.
Can you please check that all calls inside the omp are thread safe?
Otherwise we might run into more problems later


chore(reactivity): fix typo in types

I am glad you spotted this, I was just about to do the PR myself. Saved me the trouble.

I am glad you spotted this, I was just about to do the PR myself. Saved me the trouble.

Yeah my code was wrong and the TS error showed me the typo. I was a bit surprised but here we go. 😄

Nice. I had only just started doing Vue3 for about 20 minutes.. but I am super nosey of "why/how/what" things are doing and just started digging into the .d.ts files as a good place to start. Spotted that.
Hope I can help more in the future once I got a bit of time under my belt.


docs: change title

Semantic pull request status cannot be found in the head sha for some reason, maybe it doesn't trigger for all push? Check how we can support that.


how to dump insert blank line?

const yml = yaml.dump(object, options);
fs.writeFileSync(saberpath, yml);

The results are shown below
stages:
  - install
  - test
  - sonar
  - build
install:
  stage: install
  image: node:14.19.0
  script:
    - yarn
  artifacts:
    name: install
lint:
  stage: test
  image: node:14.19.0

Here's what I'd like to see, how do I insert blank lines between blocks
stages:
  - install
  - test
  - sonar
  - build

install:
  stage: install
  image: node:14.19.0
  script:
    - yarn
  artifacts:
    name: install

lint:
  stage: test
  image: node:14.19.0

There are no options for such formatting. You could probably dupm each key separate, and then join results with blank spaces

The source code, no blank lines between blocks
const yml = yaml.dump(object, options);
fs.writeFileSync(saberpath, yml);

The new code, insert blank lines between blocks
const res = Object.entries(object).reduce((arr, [key, val]) => [...arr, yaml.dump({ [key]: val }, options)], []);
fs.writeFileSync(saberpath, res.join('\n'));

One drawback of this: the sortKeys option won't work because each element is treated separately. So you'll have to do your own pre-sort of the data.


Showing error on npm install with v0.4.7 version

AlaSQL is based on unpaid voluntary work. Thank you for taking the time to make it better.
Programming question?

Please use http://stackoverflow.com/questions/ask?tags=alasql

Something not working as expected?

Describe the problem
Showing error on npm install with v0.4.7

Provide code that replicates the problem
npm WARN enoent ENOENT: no such file or directory, open '/tmp/test/package.json'
npm WARN test No description
npm WARN test No repository field.
npm WARN test No README data
npm WARN test No license field.
npm ERR! Linux 4.13.0-45-generic
npm ERR! argv "/home/jogendra/.nvm/versions/node/v7.10.0/bin/node" "/home/jogendra/.nvm/versions/node/v7.10.0/bin/npm" "install"<EMAIL_ADDRESS>npm ERR! node v7.10.0
npm ERR! npm  v4.2.0
npm ERR! path /tmp/test/node_modules/alasql/bin/alasql-cli.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod '/tmp/test/node_modules/alasql/bin/alasql-cli.js'
npm ERR! enoent ENOENT: no such file or directory, chmod '/tmp/test/node_modules/alasql/bin/alasql-cli.js'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR!     /home/jogendra/.npm/_logs/2018-07-14T18_53_09_122Z-debug.log

We suggest to spawn a jsfiddle from http://jsfiddle.net/mtt9r7rx/

Hmm. Strange.
what if you do the same for version 0.4.6 ?

Its working fine for me on version 0.4.6.

Can you please provide the exact command you are running?

npm install alasql@^0.4.0(Please ensure you have clean npm cache and verify version after install)

Thanks You @mathiasrw


Add initial spack.yaml and config

In this PR:

Add initial spack.yaml
Add initial config directory with versions of spack, spack-packages and spack-config

Closes #2

Gadi is unhappy at the moment, so the deployment has failed. Will rerun when it is better. As an aside...maybe it is worth upserting or deleting old comments...the PRs become a bit large with all these comments...
See failed run: https://github.com/ACCESS-NRI/ACCESS-ESM1.5/actions/runs/9345587853/job/25718740970?pr=5

Hi @CodeGat , I think we should require an exact version of netcdf* and hdf5 packages that correspond with the non-Spack build.

Fair enough @harshula - what would those versions be, or where can I find them?

what would those versions be, or where can I find them?

Hi @penguian , Can you please list here, the versions of netcdf* and hdf5 packages that correspond with the non-Spack build?

Versions used by the non-Spack build at https://github.com/penguian/access-esm-build-gadi/blob/master/Makefile :

netcdf/4.7.1 -- from /apps/Modules/modulefiles and /apps/netcdf/4.7.1/lib/pkgconfig/netcdf.pc, with settings at /apps/netcdf/4.7.1/lib/libnetcdf.settings
netcdf-fortran 4.5.1 -- from /apps/netcdf/4.7.1/lib/Intel/pkgconfig/netcdf-fortran.pc
hdf5/1.10.5 -- from /apps/Modules/modulefiles and /apps/netcdf/4.7.1/lib/libnetcdf.la

Note that MOM5 for ACCESS-OM2 uses netcdf/4.7.4: https://github.com/mom-ocean/MOM5/pull/333
I don't think that it would hurt to use 4.7.4 for ACCESS-ESM1.5 as well, but we need to check.

Thanks Paul. I'll add those versions, and try with 4.7.4. By netcdf, do you mean the spack package netcdf-c?

Thanks Paul. I'll add those versions, and try with 4.7.4. By netcdf, do you mean the spack package netcdf-c?

Yes, sort of. The [Makefile](https://github.com/penguian/access-esm-build-gadi/blob/master/Makefile ) uses the NCI netcdf/4.7.1 module which includes both the equivalent of the netcdf-c and netcdf-fortran Spack packages. See the directory  /apps/netcdf/4.7.1 for details.

@harshula in reference to:

The Makefile uses the NCI netcdf/4.7.1 module which includes both the equivalent of the netcdf-c and netcdf-fortran Spack packages. See the directory /apps/netcdf/4.7.1 for details.

Would we be better off using the system netcdf rather than the spack-packages one?

Would we be better off using the system netcdf rather than the spack-packages one?

No. We decided to avoid using the system netcdf.

Also:
$ spack install netcdf-fortran<EMAIL_ADDRESS>arch=linux-rocky8-x86_64
==> Error: concretization failed for the following reasons:

   1. Cannot satisfy<EMAIL_ADDRESS>   2. Cannot satisfy<EMAIL_ADDRESS>

Noted, we are using @4.6.1

Linking https://github.com/ACCESS-NRI/spack-packages/pull/121 for possible changes to the spack.yaml.

Hi @CodeGat , See below for the relationship between netcdf-c and netcdf-fortran versions:
$ cat /apps/netcdf/4.7.1/lib/Intel/pkgconfig/netcdf-fortran.pc
prefix=/apps/netcdf/4.7.1
exec_prefix=${prefix}
libdir=/apps/netcdf/4.7.1/lib/Intel
includedir=/apps/netcdf/4.7.1/include/Intel
ccompiler=gcc
fcompiler=ifort

Name: netcdf-fortran
Description: NetCDF Client Library for Fortran
URL: http://www.unidata.ucar.edu/netcdf
Version: 4.5.1
Requires.private: netcdf > 4.1.1
Libs: -L${libdir} -lnetcdff
Libs.private: -L${libdir} -lnetcdff -lnetcdf
Cflags: -I${includedir}

$ cat /apps/netcdf/4.7.4/lib/Intel/pkgconfig/netcdf-fortran.pc
prefix=/apps/netcdf/4.7.4
exec_prefix=${prefix}
libdir=/apps/netcdf/4.7.4/lib/Intel
includedir=/apps/netcdf/4.7.4/include/Intel
ccompiler=gcc
fcompiler=ifort

Name: netcdf-fortran
Description: NetCDF Client Library for Fortran
URL: http://www.unidata.ucar.edu/netcdf
Version: 4.5.2
Requires.private: netcdf > 4.1.1
Libs: -L${libdir} -lnetcdff
Libs.private: -L${libdir} -lnetcdff -lnetcdf
Cflags: -I${includedir}

@harshula, how is it that @penguian ran the model using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>in this PR: https://github.com/ACCESS-NRI/spack-packages/pull/121 ?

The approval has come quicker than expected!
Lets not merge this until we move to 0.22 and https://github.com/ACCESS-NRI/ACCESS-ESM1.5/pull/7 and https://github.com/ACCESS-NRI/build-cd/issues/102 are merged.

Although the above installed, we still have issues with module use. Testing out ways to fix it now: https://github.com/ACCESS-NRI/ACCESS-ESM1.5/issues/8#issuecomment-2207906452

Finally! Modulefiles work as expected - they were using old modulefiles for some reason, but we deleted the old modulefiles recreated the current ones.


NO-ISSUE:  Add auto-attach to rhsm registration commands

Ensures that manage-vm.sh  brings  rhsm to a healthy state.
On certain cases  after manage-vm.sh  and  RHEL registration run  successful ,  the system status is Invalid:
microshift@microshift-dev ~]$ sudo subscription-manager status
+-------------------------------------------+
   System Status Details
+-------------------------------------------+
Overall Status: Invalid

Red Hat Enterprise Linux for x86_64:
- Not supported by a valid subscription.

System Purpose Status: Not Specified

@eslutsky , can we also fix this script?
https://github.com/openshift/microshift/blob/main/scripts/devenv-builder/configure-vm.sh#L84

/lgtm


Remove unused directories

To get started with some cleanup i have started to remove folders that are not used anymore.

+1

I'm in favour of cleanup, but we should not shut the door on multi-distro support.  In fact I think that is by far the best way to build a real community.  So :-1: until the wider team discusses this.
One option would be to add a multi-distro-support tag before merging this so that the code is easily retrievable later if we add support back in.  However there is still the risk that some Ubuntu/CentOS fan who is curious about Crowbar visits this github project, looks at the code, sees that only SUSE distros are supported, and then leaves before they discover that there is already a lot of prior work done on supporting these distros.  So I'm not convinced by that approach.

I have remove ALL distro folders, even the SUSE ones. IMHO our goal have to be to build everything with tools like OBS. And all the distro folders are still available in the old master tag. So i think this :-1: is not really valid.

Sorry but old-master is not a good tag name - when people look back in a year or two they will have NO clue what it refers to.  Please pick a more descriptive name that at least refers to a particular release, e.g. pre-tex but better than that.

Uhm, there are already branches for stoney and tex?

And btw, old-master is used for ALL other barclamps.

Uhm, there are already branches for stoney and tex?

Yes - I heard that you created them independently even though @vuntz had recommended to postpone creation until this sprint.  But they are already out of date, and also the corresponding _service files have not been changed accordingly, so they are currently unused.
This task is in the current Grapes sprint, so please don't do anything else on it.

And btw, old-master is used for ALL other barclamps.

Nope, it's missing from barclamp-pacemaker at very least.  And sorry, but even if it was used for all barclamps, that wouldn't magically convert it from being a bad name into a good name :-)  When people look back in a year or two they will have NO clue what old-master means.  That's like the pre-RCS approach to version control where people kept copies of files by appending suffices like .old, .old.2, and .REALLY.OLD.

Ok forgot it. I will defintily stop improving this stuff now.

@tboerger Either you misunderstood me, or you give up far too easily.  I made some constructive criticism on the branching issue, and I also think that more discussion regarding multi-OS support is needed before we start changing anything radically (this PR is far more invasive than the branch creation which @vuntz suggested postponing); however I am strongly in favour of clean-up in general.  Fixing the branch naming should be done by Grapes this sprint, and after that I expect it would make sense to consider merging this PR and others which remove other unmaintained code.

I wanted to do some improvement, you have been the first person that wanted to have changes. This improvment have not been accepted so i will simply stop that. I don't want to discuss over and over again the same stuff. Do what you want with the cleanup in Grapes, i will just stop it as i have more then enough other things to do. That was just something i did to get something different than HAWK to see.

This improvment have not been accepted so i will simply stop that.

Why?  Do you give up every time one of your PRs receives some constructive criticism?  If we all did that, the team would make no progress at all.

I don't want to discuss over and over again the same stuff.

We are not discussing the same stuff over and over.  We only discussed it once, and then you closed the PR.  I'm not sure why.  I guess maybe you were offended by me saying old-master was a bad name for a branch?  If so then feel free to ask me to be politer and I will apologise and try to use gentler words in future, but I hope we can avoid letting emotions get in the way of valid technical discussions.

I alreadt know this endless discussions. And i won't do it again for this. Feel free to improve in Grapes. I will not start any more improvement before i get any card in that direction.
And for the naming of the branch... They are already there for multiple months and nobody cared about the naming. The same for cleaning up branches btw. Oh, wait, i have been the one that cleaned the stuff of others in that part...
And of course this old-master branch doesn't exist for pacemaker, this barclamp has been developed far later, just as a sidenode and shame on me that i don't remember that while i stated all barclamps got this branch.
And there will be no Ubuntu/CentOS or whatever fan get interested in that if there are nowhere some working images or packages available. But that's a totally different thing nobody really cares about.

I alreadt know this endless discussions.

They're not endless but it requires patience to reach a consensus.  Giving up simply because you disagree with someone does not help reach consensus.

They are already there for multiple months and nobody cared about the naming.

That's not true, I always care about naming.  I don't remember you notifying the community before you created old-master - if you did I'm pretty sure I would have noticed and replied saying it was not a good choice.  But if I missed it I apologise.

And of course this old-master branch doesn't exist for pacemaker, this barclamp has been developed far later, just as a sidenode and shame on me that i don't remember that while i stated all barclamps got this branch.

This demonstrates why old-master is a not an ideal branch/tag name - it provides zero context for what "old" refers to, so it's not clear whether old-master is supposed to line up to the same point in time across all repos, or whether it's supposed to be independent per repo.  And as I already said, this will result in confusion when people look back at this in the future.  Maybe names like pre-stoney, pre-tex etc. are not hugely descriptive either, but at least they give some rough context to the timeframes involved.  Of course we could get more accurate by including a timestamp, but it's still not clear what that means.  In particular, we have had per-release branching in the barclamps for a LONG time, but not in the main Crowbar repo.  So trying to draw parallels between each regarding old-master doesn't make any sense.

And there will be no Ubuntu/CentOS or whatever fan get interested in that if there are nowhere some working images or packages available.

True, which is why we need to discuss our cross-distro strategy.

But that's a totally different thing nobody really cares about.

I don't think we've had enough discussions or had enough conclusions yet for that to be true.

True, which is why we need to discuss our cross-distro strategy.

We already discussed about that. and the only conclusion to keep it maintainable is to use OBS for the different distros.

I don't think we've had enough discussions or had enough conclusions yet for that to be true.

Of course... Everybody sais "yeah, we need a community", "yeah, let's do it open for other interested people" and what happened? I have created everything on OBS, and nobody cares about it. Just look at OBS. I have been the only one who has done something on it...

We already discussed about that.

Then I think I missed that discussion :-(

and the only conclusion to keep it maintainable is to use OBS for the different distros.

Yes, that seems like a good approach to me.

Everybody sais "yeah, we need a community"

Not everybody.

"yeah, let's do it open for other interested people" and what happened? I have created everything on OBS

What you have done so far is super cool, however it's not enough yet.  I suspect we'll need Ubuntu or Fedora packages.

and nobody cares about it. Just look at OBS. I have been the only one who has done something on it...

Of course noone will notice until there is a good website, good quickstart documentation, an announcement, and some other noise on social media.  Surely you did not expect they would?  That is why I have been pushing for these things to be fixed for the last 2 years or so.  But it's great that FINALLY PM/PO are prioritizing this work in the sprints.  If we do it right, I really think people could start paying more attention.

What you have done so far is super cool, however it's not enough yet. I suspect we'll need Ubuntu or Fedora packages.

Of course we need, that, but do you want to write them? There had been one guy on IRC that had interest in that, but of course he lost interest because nothing happened.

Of course noone will notice until there is a good website, good quickstart documentation, an announcement, and some other noise on social media. Surely you did not expect they would? That is why I have been pushing for these things to be fixed for the last 2 years or so. But it's great that FINALLY PM/PO are prioritizing this work in the sprints. If we do it right, I really think people could start paying more attention.

Even within SUSE nobody cared about it... That really requires no further attraction/website/documentation or whatever. Sorry that i really took a vacation and have not been there to guide through every step... The last release worked quite well on OBS, until somebody just started to copy it into IBS just because of being too lazy or whatever.

I suspect we'll need Ubuntu or Fedora packages.

Of course we need, that, but do you want to write them?

Even within SUSE nobody cared about it...

That's incorrect.  People are working on improving the website right now.  If noone within SUSE cared then that would not be happening.

That really requires no further attraction/website/documentation or whatever.

Sorry, I have no idea what your point is here.  But a good website and docs ARE absolutely necessary.  Surely you are not disputing that?

Sorry that i really took a vacation and have not been there to guide through every step...

No need to apologise - none of this should be dependent on individuals.  Like I already said, this requires careful discussion, prioritization, and planning within Scrum.  You seem to be suggesting that we need individuals to personally "care" in order for any of this to succeed, but that's not true.  It's a professional team effort based on shared goals.  We're not a bunch of hobbyists only working on this in our spare time (although of course hobbyists are always very welcome in the project too).


Filter out Discovery hits #145

This cuts our test_sequences in half, and brings back user-agents other than e2e.test.

I think this is a good and mergeable pull request for an initial filtering, but this is a topic we should return to.  From what I can see here, we created a list of Op ID's through a separate filtering script, and the parameters of that filter was based on a noticed pattern in the test sequences.  I think it woudl be valuable to articulate the logic  behind that pattern, or more precisely define what makes something part of discovery.  We could then use that logic to dynamically create that list, instead of it being hardcoded.  This would have the benefit of not having to update our code when changes are made to discovery tests, and also increasing the trust and accuracy in our data.

/lgtm


Angular 404

Description:
Create Angular component, that will render 404 - Resource not found.
Current behaviour:
Right now we don't have 404 component in Angular, we fallback it to old Django views, whenever route is not found in RouterModule. The problem occurs for offers - they have a route defined in Angular, but when Django returns 404 from API we have empty.
Expected behaviour:
When API returns 404 we should catch that and render some 404 errror page.

@Rafalkufel


Support for React Native 0.73 - Android

I'm trying to use this library with the latest React Native version 0.73.4
But I'm having problems on Android.
I'm running the app from an emulator.
How to reproduce
npx react-native@latest init Readium073
yarn add react-native-readium
yarn android
or use my repo
https://github.com/casperolesen/Readium073
Java version error
`Execution failed for task ':react-native-readium:compileDebugKotlin'.

'compileDebugJavaWithJavac' task (current target is 17) and 'compileDebugKotlin' task (current target is 1.8) jvm target compatibility should be set to the same Java version. Consider using JVM toolchain: https://kotl.in/gradle/jvm/toolchain`

I've tried to remove this from the build.gradle
kotlinOptions {
    jvmTarget = "1.8"
  }

This fixes the issues with the Java version.
Build failed with an exception
I'm now getting multiple errors when trying to build like
/react-native-readium/android/src/main/java/com/reactnativereadium/ReadiumView.kt:62:7 'when' expression must be exhaustive, add necessary 'is Failure', 'OpenDrmManagementRequested', 'OpenOutlineRequested', 'StartNewSearch' branches or 'else' branch instead
/react-native-readium/android/src/main/java/com/reactnativereadium/epub/UserSettings.kt:226:73 Unresolved reference: webView
/react-native-readium/android/src/main/java/com/reactnativereadium/reader/EpubReaderFragment.kt:112:55 Unresolved reference: epub_navigator_tag
I can get the build to complete by fixing or removing the lines with errors.
Metro error
Unable to load script. Make sure you're either running Metro (run 'npx react-native start') or that your bundle 'index.android.bundle' is packaged correctly for release
This is were I'm stuck now.
When I remove react-native-readium the app is running fine again.
I'm not an experienced kotlin developer, but I would like to help fixing this! 🦸♂
I just don't know if it's a small bug or something that needs a bigger rewrite of this library.
If someone else can confirm that it's not working with the latest release of React Native - how should we fix it?

@casperolesen , I'll look into this when I'm able. However, if you want to start looking into it, my recommendation would be to start by cloning this repo and upgrading the example project to<EMAIL_ADDRESS>See if your issues persist once you do that. If they do, send me a PR for the upgrade, and I'll pull it down and see if I can reproduce your issue.
Then we can go from there.

Thanks! I'll take a look 👁

So what is the suggested solution to solve this problem? I did not understand anything exactly

@themehdihn I (or someone else) needs to look into this as there's some upgrades to the library required. I haven't yet had the time, but feel free to dig around yourself!

I (or someone else) needs to look into this as there's some upgrades to the library required. I haven't yet had the time, but feel free to dig around yourself!

Please do this as soon as possible, because no other library is working properly for react-native until now.

Please do this as soon as possible

@themehdihn you realize that this is an open source project right?...
Have you paid me or any of the other contributors for their work on this? Why should anyone drop all the other important things their doing just so you can have what you want?
If you're willing to pay for my time, I'd be happy to drop what I'm doing to investigate this for you.

I could reproduce @jspizziri as you said, i will pass what was necessary change to reproduce the same error.
"react-native": "0.73.6",
"react-native-screens": "^3.30.1",

buildscript {
    ext {
        ...
        compileSdkVersion = 34
        targetSdkVersion = 34
        ndkVersion = '25.1.8937393'
        ...
    }
    ...
    dependencies {
        ...
        classpath('com.android.tools.build:gradle')
        ....
    }
    ...
}

includeBuild('../node_modules/@react-native/gradle-plugin')

distributionUrl=https\://services.gradle.org/distributions/gradle-8.3-all.zip

@candidogustavo please submit a PR so I can look at a formal diff.

@candidogustavo please submit a PR so I can look at a formal diff.

I am trying to fix it by myself the last two weekends, but i am stuck in an error i have no idea what is the cause, i don´t receive any other error anymore "Unable to load script.Make sure you are either running a Metro server or that your bundle 'index.android.bundle' is packaged correctly for release". Do you have any tip to discover what is happening?

@candidogustavo can you share a full stack trace of your error? I have this on my list of things to look into, but I just haven't had the time to get to it yet.

Hey, I'm running into this issue upgrading my app too. I see some statuses have changed in the last week, just wondering if any work is happening on this or if any work is planned? 👍

@Riandan I haven't begun work on it, but its definitely something that will happen eventually. I just need to find the time to do it. Would love to see the community setup in and help make it a reality!

This issue is closed by https://github.com/5-stones/react-native-readium/pull/60


ResponseFactory doesn't implement the correct interface

I tried to add your ResponseFactory to my PSR-15 Dispatcher, but it cracked up saying that it must implement Psr\Http\Message\ResponseFactoryInterface. Currently it implements Interop\Http\Factory\ResponseFactoryInterface, which it doesn't like.

Psr\Http\Message\ResponseFactoryInterface doesn't exist in any package. Where are you seeing this?

Right. Interop\Http\Factory\ResponseFactoryInterface has the same methods as a Psr one, but it isn't defined (yet). In the http-factory repo, the interface should be defined with the Psr namespace until an official Psr package is available. I'll close this issue and reopen it on the other repo.


Unused getIO() and ioForTask() methods, removeable or future use?

Impact of the new feature
When browsing MicroServices/Tools/Common.py I saw that the function ioForTask(request,url) is only called by getIO() in the same file, and doing a search for the latter function name, it is not called anywhere in WMCore repository, nor when I searched GitHub
for any public repositories importing from WMCore.MicroService.Tools.Common did I find anyone importing this function nor anyone importing * .
Is your feature request related to a problem? Please describe.
Can these functions be deleted, or or are they still usable in private repositories or potential future debugging?
Describe the solution you'd like
Delete if unnecessary?
Describe alternatives you've considered
Additional context

Hi @oljemark , thank you for creating this ticket. I had a look at those 2 functions and they are indeed not used.
They have been inherited from the Unified system, so we kept them around for a while, in case we would decide to use them.
This has not happen for a few years now, so I would just go ahead and delete them. Would you be willing to make a PR removing them?

Like this? Didn't find out how the unit test in test/python/WMCore_t/MicroService_t/Tools_t is manually run.

For the unit tests, you would have to pull an image from CERN registry, which is behind SSO. I can either test it myself, or we let automated Jenkins to test it, but first you will have to join a team in this repository (you should have received an invitation). However, that is not a problem, as I this code was never used and I didn't see any unit tests for it as well.
Thank you very much for the PR, really appreciated!