BF: inform that no to  can be identical if casing is ignored

Closes #857
An alternative could be to establish a new section, like "Case sensitivity" in the same document, which would allow to generalize the rule to cover the entire file path, and then just refer to it from <label>.  But was not sure if it would not just get lost among already a good number of sections there, and where to place it.  Sounds like a foundational aspect to me and should be close on top but "what is not as important" there? ;)

[ ] Whenever this PR is merged in some form or shape, an issue should be filed in bids-validator to have validation for this implemented.

edit 1: is there a term to describe such desired behavior?  it is neither "case sensitive" nor "case insensitive" .  "case collision intolerant"?

An alternative could be to establish a new section, like "Case sensitivity" in the same document, which would allow to generalize the rule to cover the entire file path, and then just refer to it from .

That sounds better.

But was not sure if it would not just get lost among already a good number of sections there, and where to place it. Sounds like a foundational aspect to me and should be close on top but "what is not as important" there? ;)

Few people read the spec linearly, most people will read this potential new section after hitting an error in the validator (once we add support there), so I think a "great placing" of the section is less important than having it as a section (because it allows us, as you say, to more easily generalize the rule)

edit 1: is there a term to describe such desired behavior? it is neither "case sensitive" nor "case insensitive" . "case collision intolerant"?

I like case collision intolerant

I think we're asking for trouble by making this a MUST NOT-level change. I would suggest softening to SHOULD NOT and having the validator warn.
Users can promote some options to promote warnings to errors (for example, fMRIPrep considers missing T1w images an error and OpenNeuro considers missing author lists an error), and some flags appear as check boxes on the web interface. I would support doing that for this to raise awareness of the potential problem, without going so far as to automatically invalidate legacy datasets.

re @effigies

I think we're asking for trouble by making this a MUST NOT-level change. I would suggest softening to SHOULD NOT and having the validator warn.

warnings often get ignored.

I checked existing public openneuro datasets -- seems to be no hits.  Those which are yet to be released, better have it fixed first (and likelihood of encountering such cases is small)
(git)smaug:/mnt/datasets/datalad/crawl/openneuro[master]
$> for ds in ds*; do files=$(/usr/bin/find $ds/*); nf=$(echo $files | wc -l); fl=$(echo $files | tr 'A-Z' 'a-z' | sort | uniq -c); nfl=$(echo $fl | wc -l); echo -n "$ds $nf $nfl "; [ "$nf" == "$nfl" ] && echo "ok" || echo "PROBLEM";  done

resulted in none with PROBLEM
A sample run on HBN one mentioned
(git)smaug:/mnt/datasets/datalad/crawl/openneuro[master]
$> for ds in ../../crawl-misc/HBN_BIDS ; do files=$(/usr/bin/find $ds/*); nf=$(echo $files | wc -l); fl=$(echo $files | tr 'A-Z' 'a-z' | sort | uniq -c); nfl=$(echo $fl | wc -l); echo -n "$ds $nf $nfl "; [ "$nf" == "$nfl" ] && echo "ok" || { echo "PROBLEM"; echo $fl | grep -v '^ *1 '; }; done
../../crawl-misc/HBN_BIDS 81321 81308 PROBLEM
      2 ../../crawl-misc/hbn_bids/sub-ndarvn280jtn
      2 ../../crawl-misc/hbn_bids/sub-ndarvn280jtn/ses-hbnsitecbic
      2 ../../crawl-misc/hbn_bids/sub-ndarvn280jtn/ses-hbnsitecbic/anat
      2 ../../crawl-misc/hbn_bids/sub-ndarvn280jtn/ses-hbnsitecbic/anat/sub-ndarvn280jtn_ses-hbnsitecbic_acq-vnavnorm_t1w.json
      2 ../../crawl-misc/hbn_bids/sub-ndarvn280jtn/ses-hbnsitecbic/anat/sub-ndarvn280jtn_ses-hbnsitecbic_acq-vnavnorm_t1w.nii.gz
      2 ../../crawl-misc/hbn_bids/sub-ndarvn280jtn/ses-hbnsitecbic/fmap
      2 ../../crawl-misc/hbn_bids/sub-ndarvn280jtn/ses-hbnsitecbic/fmap/sub-ndarvn280jtn_ses-hbnsitecbic_acq-fmri_dir-ap_epi.json
      2 ../../crawl-misc/hbn_bids/sub-ndarvn280jtn/ses-hbnsitecbic/fmap/sub-ndarvn280jtn_ses-hbnsitecbic_acq-fmri_dir-ap_epi.nii.gz
      2 ../../crawl-misc/hbn_bids/sub-ndarvn280jtn/ses-hbnsitecbic/fmap/sub-ndarvn280jtn_ses-hbnsitecbic_acq-fmri_dir-pa_epi.json
      2 ../../crawl-misc/hbn_bids/sub-ndarvn280jtn/ses-hbnsitecbic/fmap/sub-ndarvn280jtn_ses-hbnsitecbic_acq-fmri_dir-pa_epi.nii.gz
      2 ../../crawl-misc/hbn_bids/sub-ndarvn280jtn/ses-hbnsitecbic/func
      2 ../../crawl-misc/hbn_bids/sub-ndarvn280jtn/ses-hbnsitecbic/func/sub-ndarvn280jtn_ses-hbnsitecbic_task-rest_run-1_bold.json
      2 ../../crawl-misc/hbn_bids/sub-ndarvn280jtn/ses-hbnsitecbic/func/sub-ndarvn280jtn_ses-hbnsitecbic_task-rest_run-1_bold.nii.gz

Situation is IMHO of the same caliber of enforcement as "<label> - an alphanumeric value...", and it is not tool specific (as given examples on needing or not anatomical or some optional metadata) but rather might be effecting users of major OS/file systems before they even get to the tool to analyze it.  Due to such collisions, and tools just issuing a warning if/whenever such collisions detected, users might proceed to analyzes without noticing that some files might have been overwritten with a copy from an alternative casing.  That could effect reproducibility etc -- e.g. if someone originally ran analysis on Linux and then someone tries to reproduce using analysis script, they might not even mention that on their OS/system apparently there was some warning issued some time and results "differ".  So I would vote for making it strong (MUST NOT) instead of just a SHOULD NOT.

Thanks everyone for the feedback!  So I am to

craft a separate session
will term it as "case collision intolerant"

As I said, OpenNeuro could promote the warning to an error and prevent this from arising in our data. The question is whether the standard should break backwards compatibility in this way.

As I said, OpenNeuro could promote the warning to an error and prevent this from arising in our data. The question is whether the standard should break backwards compatibility in this way.

without this "fix" to the standard, such a BIDS dataset might not be compatible with major OSes.  So, as to me, it is not "breaking backward compatibility" (as if a problematic dataset could be used "correctly" before) but rather a "bugfix" (as @sappelhoff noted in https://github.com/bids-standard/bids-specification/issues/857#issuecomment-903507639 noted) to the standard to avoid the issue of a BIDS-compliant dataset incompatibility with the OSes/filesystems.

without this "fix" to the standard, such a BIDS dataset might not be compatible with major OSes.

That was the argument that convinced me to consider this change a bugfix ... that and the fact that we - apparently - wouldn't break a lot of datasets if any. I would be interested in further opinions though.

PR updated, RFC is posted: https://groups.google.com/g/bids-discussion/c/ixm2aFgAJy0

The RFC (so far) has yielded two comments that I interpret to be in favor of this (breaking) change. I think an input from @bids-standard/steering would be nice to have here.

This change sounds very reasonable to me.

Thinking about this now, this is consistent with the previous decision that FA (fractional anisotropy) and fa (flip angle) cannot both exist as suffixes. Would it make sense to make a more general rule like:
File name components, including labels and suffixes, are case-sensitive,
but collisions MUST be avoided when case is ignored.
For example, a dataset cannot contain both `sub-S1` and `sub-s1`.
Additionally, because the suffix `eeg` is defined, then the suffix `EEG` may not be added to the standard.

It's mixing rules for dataset curators and BEP leads a little bit.

Sounds great to me -- feel welcome @effigies to make it into a recommendation or just a follow up commit if placement should be different (section)

It also sounds good to me. Understanding it as a bug fix and indeed preventing future errors. It's nice there isn't any known public dataset affected. And that the same applies for both labels and suffixes.

@yarikoptic Pushed a commit directly to your branch. Please have a look.

Thanks!!

Thank you @effigies , looks good for me, but I guess I shouldn't approve my own PR ;)

Well, between the two of us, we can count as one.

filed https://github.com/bids-standard/bids-validator/issues/1330 , and got surprised that current master is a whooping v1.6.0-203-g811e17e2 - so lots of changes/development since the last release, without any bugfix or minor release.

It reminds me of an earlier discussion on units, where we identified that Greek characters used in units (ohm) and prefixes (micro) are ambiguous. See https://bids-specification.readthedocs.io/en/stable/99-appendices/05-units.html. An important raison d'être for the specification is to disambiguate and to make choices where individual researchers themselves might go for opposite choices. In this case "a" and "A" are ambiguous under some conditions.
Hence I also approve of this "breaking change" as a bug fix to the specification.

Given the general agreement and the postings on the mailing list to make a wider audience, I feel like we can merge this PR in 3 days, thus observing our 5 days rule. It'll then be part of the next release unless anything changes in the meantime.

Thanks for identifying this issue and pushing for a solution @yarikoptic and all reviewers.


Try leaflet.js instead of Google Maps

Should be faster.

+1 when we get close to 25K map accesses
https://developers.google.com/maps/documentation/javascript/usage
On Mon, May 18, 2015 at 8:40 PM, Daniel Hershcovich <
<EMAIL_ADDRESS>wrote:

Should be faster.
—
Reply to this email directly or view it on GitHub
https://github.com/hasadna/anyway/issues/256.

@robi-y I wouldn't be worry about the 25k limit (see the note in the link
you shared)
בתאריך 18 במאי 2015 22:05, "robi-y"<EMAIL_ADDRESS>כתב:

+1 when we get close to 25K map accesses
https://developers.google.com/maps/documentation/javascript/usage
On Mon, May 18, 2015 at 8:40 PM, Daniel Hershcovich <
<EMAIL_ADDRESS>wrote:

Should be faster.
—
Reply to this email directly or view it on GitHub
https://github.com/hasadna/anyway/issues/256.

—
Reply to this email directly or view it on GitHub
https://github.com/hasadna/anyway/issues/256#issuecomment-103177981.

For this we need to apply for a google grant (maybe @galraij should decide)

I think we do have some kind of understanding with google, let me know what to ask from them and I will.

On May 19, 2015, at 16:29, robi-y<EMAIL_ADDRESS>wrote:
For this we need to apply for a google grant (maybe @galraij https://github.com/galraij should decide)
—
Reply to this email directly or view it on GitHub https://github.com/hasadna/anyway/issues/256#issuecomment-103490639.

Basically if we're having close to 25K hits a day we need to ask for more quota.
Either by our connections there or by:
https://www.google.com/earth/outreach/grants/software/index.html

I don't know where can we see how many Google maps hits we have a day, but I find it hard to believe that we have 25K of them.
The performance issue is not an issue anymore, since we calculate clustering on the server now and there aren't many markers (or cluster markers) drawn on the map. So I don't think the map engine is a big of a bottleneck..

We are far from any limit, but even when we get to a limit we are close enough to google to sort things out.


How to style m-btn component

@neongrau
const docElement = document.querySelector('openapi-explorer');
      const style = document.createElement('style');
      style.innerHTML = `
      .m-btn {
        border-radius: 15px !important;
        box-shadow: none;
      }`;
      docElement.shadowRoot.appendChild(style);

    openapi-explorer::part(navbar-operations-header) { /*works*/
      background: linear-gradient(90deg, #0065AD, #02AFC3);
      border-top: none;
      border-bottom: 1px solid rgba(255,255,255, .2);
      font-size: 11px;
    }
    openapi-explorer::part(navbar-components-header) { /* needed but not implemented? */
      background: linear-gradient(90deg, #0065AD, #02AFC3);
      border-top: none;
      border-bottom: 1px solid rgba(255,255,255, .2);
      font-size: 11px;
    }

@neongrau can you provide a visual of what the problem is here and how you would like it to look like? This would be the best way to figure out how to either suggest a solution or provide new functionality. Thanks!

currently button look like this:

but i want to restyle them to look like this:

Closed?

Okay, now everything is fixed. You would reference the button style changes the same way you might do the other updates. In this case:
openapi-explorer::part(btn--resp) {
      border-radius: 15px !important;
      box-shadow: none;
    }

Is probably what you want.

Okay, now everything is fixed. You would reference the button style changes the same way you might do the other updates. In this case:
openapi-explorer::part(btn--resp) {
      border-radius: 15px !important;
      box-shadow: none;
    }

Is probably what you want.

yes, that is perfect!
Thank you very much for this great help!


There is no "./configure"

The manual says:

Unix-like Operating Systems

In the folder usrsctp type
$ ./configure
$ make
But there is no "configure" script in the source (but "configure.am). The doc should tell how to get it.

Run ./bootstrap before ./configure and make

Yes, I figured it out. I just meant that the doc is currently incorrect :)

I'm creating a pull request right now! :smile:

Solved by pull request #35
@tuexen Close?

Yes. Thanks.


Using defer for mutex unlock in eventstream.go

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Eike Wichern seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Azure search as search option

Add the azure search as a search option to the template setup

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: mattporritt sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

I've not reviewed the PR in detail, only looked at Hosungs comments.
Looking forward to having linting etc. in place to automatically catch the formatting errors. Might even be a good idea to have a pre-commit hook to fix these auromatically (just an observation nothing to do with this PR really).

It's strange that the pending CLA check page is about PR #80 (created but then closed very soon, probably replaced with this one), when this PR is #81. Up above, it also says "All CLA requirements are met" so I'm not sure what to believe...?

This is issued from a different GitHub account, so we can believe this one :-)
Fixes #22

I was talking about the inconsistent CLA check status, not the multiple PRs... Maybe the CLA check status below was changed after my change request. Will have to wait and see for more commits to be added.

@hosungsmsft - regarding Tika service inclusion, Tika service has never been introduced in the template since elastic search cluster was added.
@mattporritt will have some further discussion with Microsoft directly on Tika service inclusion.

Thanks @superzoelu . We'll speak with @mattporritt about the Tika instance install/config matter at our regular sync-up meeting today. I also filed another issue for the tracking (#84). This is now approved and will be merged soon. Thanks for your hard work!


An upgrade to Riak 2.0 from Riak 1.4 (and continuing to use app.config) can lead to sibling generation [JIRA: RIAK-1681]

In Riak 1.4 allow_mult defaults to false and therefore is false if allow_mult is not set in app.config.
During an upgrade to Riak 2.0, the app.config could continue to be used (therefore stopping the riak.conf being used). In this scenario the default bucket-type changes from allow_mult: false to allow_mult: true potentially resulting in unexpected sibling generation.
To reproduce:

Install Riak 2.0

Start Riak and check default bucket props
sudo riak-admin bucket-type status default | grep allow_mult

Stop Riak

Copy a default Riak 1.4 app.config and vm.args in to /etc/riak/

Start Riak and check default bucket props
sudo riak-admin bucket-type status default | grep allow_mult

In the first instance (with riak.conf) I see:
allow_mult: false

In the second instance (with app.config) I see:
allow_mult: true

This means an upgrade to Riak 2.0 where the app.config continues to be used would result in a change of allow_mult setting from false to true for existing bucket properties.

Using cuttlefish (riak.conf), the allow_mult = true default is set for the default bucket type at https://github.com/basho/riak_kv/blob/develop/priv/riak_kv.schema#L512
Without riak.conf no further overrides of the bucket defaults for all buckets (https://github.com/basho/riak_core/blob/develop/src/riak_core_bucket_type.erl#L135) seem to happen. The defaults for the default bucket are assembled through app_helper:getenv in https://github.com/basho/riak_core/blob/develop/src/riak_core_bucket_props.erl#L108.
A default app.config from version 1.4 won't have the riak_core.default_bucket_props settings, and the code will therefore fall back to the hardcoded defaults. We should test if adding a section for riak_core.default_bucket_props to app.config can be used as a workaround and document it.

Testing that now @kesslerm, thanks!

Can confirm that adding
{default_bucket_props, [{allow_mult, false}]},

to app.config is a workaround and does not impact typed buckets defaults.

Full output of riak-admin bucket-type status default when using riak.conf and app.config as above:

with riak.conf
allow_mult: false
basic_quorum: false
big_vclock: 50
chash_keyfun: {riak_core_util,chash_std_keyfun}
dvv_enabled: false
dw: quorum
last_write_wins: false
linkfun: {modfun,riak_kv_wm_link_walker,mapreduce_linkfun}
n_val: 3
notfound_ok: true
old_vclock: 86400
postcommit: []
pr: 0
precommit: []
pw: 0
r: quorum
rw: quorum
small_vclock: 50
w: quorum
young_vclock: 20

with app.config
allow_mult: true
basic_quorum: false
big_vclock: 50
chash_keyfun: {riak_core_util,chash_std_keyfun}
dvv_enabled: true
dw: quorum
last_write_wins: false
linkfun: {modfun,riak_kv_wm_link_walker,mapreduce_linkfun}
n_val: 3
notfound_ok: true
old_vclock: 86400
postcommit: []
pr: 0
precommit: []
pw: 0
r: quorum
rw: quorum
small_vclock: 50
w: quorum
young_vclock: 20

Differences:

allow_mult
dvv_enabled

This is "expected" behaviour. Please see https://github.com/basho/cuttlefish/wiki/Cuttlefish-for-Application-Users specifically Cuttlefish will see your app.config sitting where it's supposed to, and use that instead.
Looping in @seemaj for opinions. I think the right thing is add the workaround to the procedure for upgrading. The best thing would be a script that turned the legacy app.config into a valid riak.conf.

I have found an alternative to Sean's approach that works; needs more review to make sure it's as otherwise harmless as I think it is.
bugfix/jrd/727
[posted via JIRA by John Daily]

I have found an alternative to Sean's approach that works; needs more review to make sure it's as otherwise harmless as I think it is.
https://github.com/basho/riak_core/tree/bugfix/jrd/727
[posted via JIRA by John Daily]

Filed https://github.com/basho/riak_core/pull/765
[posted via JIRA by John Daily]

[~jdaily] Does that mean we should abandon [https://github.com/basho/riak_kv/pull/1109]?
[posted via JIRA by Brett Hazen]


support position, size, repeat for backgroundImage

Crop images using canvas.
Create a repeat image with createPattern in canvas.

Oh wow, it's a big one. I'll need some time to go through this code.

Any chance this might get merged soon? We could really use it 😄

@brianokeefe feel free to use that branch, because I don't know if it will be merged in this form. I really like all the calculations done by @KimDal-hyeong , but I don't like that it's downloading image with a custom param (?cache). Seems like a hack. Right now, we leave downloading images to the asketch2sketch part which is cleaner, and I'd like to keep it this way.

@kdzwinel gotcha, do you have any thoughts on what a better strategy to tackle this might be?
(For what it's worth - it looks like makeImageFill in the html2asketch part will already try to download the image to make a data url anyway, is that correct?)

@kdzwinel what would be the ideal approach here? This is a feature I'd love to see working 😄

Hey all, sorry for late response. I'm currently torn between pushing current master (lets call it v1) forward and working on v2 (which will depend heavily on react-sketchapp - see #37 ). Reusing react-sketchapp will mean that html-sketchapp will be able to focus on html->react part and leave, the tricky, react->sketch part to its bigger brother. I really want to try this. On the other hand, I don't want to completely kill v1 until v2 proves to be the right way forward for the project, so there are still things merged to v1 (eg. #63). This branch however is tricky, mainly because it's a hack (although a clever one!). First of all it downloads images in JS which I'd like to avoid (3rd party images will be blocked by CORS), I'd prefer sketch plugin to do the downloading. Second of all it sews images together on a canvas - I'd prefer to use a native (Sketch) solution instead (Sketch does seem to support patterns - https://medium.com/sketch-app-sources/creating-patterns-in-sketch-12cc612ef09a ). If we could solve these two problems I'll be happy to merge it into v1.

PSA: I just made nodeToSketchLayers sync, so downloading images within that method is no longer possible (#71 - it will be released to npm as v2.0.0 soon).
@brianokeefe @theresama
IMO the temporary solution, until we have a proper support, is to extract @KimDal-hyeong code and run it on the page you are trying to extract before running html-sketchapp (it will replace all external images with data:). Both @markdalgleish and I keep such hacks in a separate js files (e.g. https://github.com/seek-oss/seek-style-guide/blob/master/docs/src/components/SketchExports/fixSketchRendering/fixSketchRendering.js ), so that they are easy to remove when the proper support lands in html-sketchapp. Hopefully this way @brianokeefe won't have to maintain a separate html-sketchapp fork ;)

I updated https://github.com/brainly/html-sketchapp/issues/17 with TLDR of what I wrote in the previous comment.


Add token_count client method

token_count
As discussed in #291 , it can be useful in many cases to support calculating the token-count of messages before sending them to OpenAI.
This PR adds an OpenAI::Client.token_count instance method which does this. To minimize astonishment, it accepts the same parameters input as the other methods. Its output is always a nonnegative integer.
If the caller has already require'd the tiktoken_ruby module, this new method automatically uses it to calculate exactly the number of tokens that OpenAI will parse. (Because parameters includes the model name, we know we're using the same algorithm OpenAI will use.)
Or, if Tiktoken is not available, it uses the two "helpful rules of thumb" in OpenAI's docs and averages them as an estimate.
Because testing the Tiktoken code paths works best if the module is actually included and not mocked, this PR adds that gem to the Gemfile. Note that this does not change the dependency list. Also, because the test is written against two specific, existing models, that module's counts should not change in the future and thus the test results should be pretty future-proof.
I'm happy to make any changes desired. Just let me know.
ruby 2.6
Tiktoken requires ruby >= 2.7.  This gem requires ruby >= 2.6. I wanted to keep this gem's test suite passing on all versions of ruby.
What I did was the slightly unorthodox method of editing Gemfile to only make mention of tiktoken when running on ruby >= 2.7, and add conditionals in the test file to skip those three tests on ruby 2.6.
It works — I checked it locally on ruby 2.6, 2.7, and 3.1.
But... it's a little ugly. Personally, if you asked me, since 2.6 isn't getting security updates, I wouldn't want to encourage its use. I would revert the ugly changes (f8d548103a6f11b8231192894f2951fa3e6de5ef) and set the required version to 2.7. But I didn't want to make that change without discussing/consulting about it first. What's in this PR works fine and changes things as minimally as possible.
All Submissions:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?

Rename the method to rough_token_count

I'm happy to do this, but I'd find it less useful. Does it change your mind to know that OpenAI's recommended estimation algorithms are usually high by 10-20%?
To me, that's a lot of wiggle room for error, if people are trying to have their code make decisions based on that estimate.
For example, in the largest example given in the docs, the Declaration of Independence, it's off from Tiktoken's calculations by 13-17%:
jamie@Jamies-MacBook-Air ruby-openai % bundle exec irb
irb(main):001:0> require 'openai'
=> true
irb(main):002:0> OpenAI::Client.new.token_count(parameters: { model: "tktk", messages: [ { content: File.read("dofi")}]})
=> 1887
irb(main):003:0> require 'tiktoken_ruby'
=> true
irb(main):004:0> Tiktoken.encoding_for_model("gpt-4").encode(File.read("dofi")).size
=> 1616
irb(main):005:0> Tiktoken.encoding_for_model("davinci").encode(File.read("dofi")).size
=> 1674

Thanks for your feedback. I've submitted #312 which I believe addresses it.


Consider exchanging refresh tokens for access tokens on demand

The access tokens we receive when a user authenticates through GitHub are currently stored in the database.
While these are very limited in scope, we should consider expiring access tokens.
Expiring access tokens are valid for 8 hours, and requires us to renew the token using a refresh token. The refresh token will be included in the final step of the OAuth2 flow when a user authenticates through GitHub.
We should consider storing the refresh token in the database instead. The refresh token on its own is useless, and has a 6 month expiry time. This way we can generate short-lived access tokens just as we want to perform an action on behalf of the user.
To renew an access token using a refresh token:
# Make a POST Request to:
https://github.com/login/oauth/access_token
# With parameters:
refresh_token="<token>"
grant_type="refresh_token"
client_id=<client ID>
client_secret=<client secret>

Which will return a new access token for a given user.

This was added in #736.


Code coverage integration?

Any chance of adding code coverage tool (e.g. Istanbul or jscoverage) integration to the generated modules?

We could put logics in either Gruntfile or .travis.yml. coveralls works very well with travis.

This'll be fix as part of https://github.com/yeoman/generator-node/issues/66
I'll close this issue as it's being worked on ATM and almost merged in the generator.


Too many plotters per temp drive

I am occasionally seeing the limit for how many plotters per temp drive being ignored.
My suspicion is that the phases like 2:? and 4:? are to blame.
My config only allows 1 plotter per temp drive. In the screenshot below, notice how drive "temp7" show as OK even though there is a job present. This happened while in phase 2:?. Once it moved on to phase 2:1, it was no longer showing as ready.

This actually just happened again twice in a few minutes. I had plotters in phase 2:? and 4:? and it created two new plotters despite being at the limit.

Let me know if this is fixed (or just close the issue if it is). Thanks!

I haven't had this issue since pulling down these changes. I'm pretty sure it's fixed. Will reopen if needed.


OAK-9879: CacheLIRS statistics may return incorrect load count

Synchronize access to loadSuccessCount
Enable test

See alternative patch https://github.com/apache/jackrabbit-oak/pull/673

Closing this PR in favour of #673


Using TOA for DuckLink Positioning System instead of RSSI

The DuckLink Positioning System (DPS) is used to locate other Ducks in GPS-denied environments. For more details read the wiki on DPS.
Currently the DPS uses RSSI values to locate where the lost Duck is. Another possible method is to use Time of Arrival (ToA). ToA calculates the distance by using the time it takes a signal sent by a Duck to reach another Duck.
We would like to explore ToA to see if it would be a better process than using RSSI.

this is a feature that we are not going to pursue for the near future. Will re-open when we do.


updated logrus so Prometheus can build on Solaris/Illumos

The logrus vendored with Prometheus is ancient, and does not compile on Solaris:
tsurumah ~/go>env GOPATH=`pwd` GO15VENDOREXPERIMENT=1 go get -f -t -u -v github.com/prometheus/prometheus/cmd/...
github.com/prometheus/prometheus (download)
github.com/prometheus/prometheus/vendor/github.com/Sirupsen/logrus
# github.com/prometheus/prometheus/vendor/github.com/Sirupsen/logrus
src/github.com/prometheus/prometheus/vendor/github.com/Sirupsen/logrus/text_formatter.go:28: undefined: IsTerminal

Updating to the head for logrus fixes the problem.


Improve the readme file

Readme.md is very terse. It should contain more information about how the application works and its usage.
It should have:

Information about the directory structure and what content goes where.
Information about how to execute the application.
Warnings and disclaimers about the fitness of the application.
Build requirements (go version 1.8 or better)

I don't think warnings and disclaimers are appropriate at this point


Add some docs on how we use GOV.UK Notify

We're starting to use GOV.UK Notify in lots of places (not just Email Alert API), so this updates the docs to make this clearer and start to introduce separation between GOV.UK Notify and Email Alert API in peoples minds.

I think this might help to structure #2487.

Thanks @issyl0, those should be resolved now!


Remove dangling square bracket

This square bracket is a typo in the sentence, so I've remove it.

Thank you!


Add animation options for Line charts

The only functional change here is the addition of the animation options to the Line config.
The rest of the changes are the result of running elm-format over the code (which I do subconsciously), so if you'd like a trimmed down version with just the functional changes, let me know.

Yep, the emacs mode for elm makes it super easy to elm-format everything, so I do it reflexively now. It's great to have a tool like that!


Add necessary actions

Such as:

[ ] Build necessary NuGet packages
[x] Build docker image

Initial release was built. Nuget packages are not required for this component


[Issue]:   Why I can not use drift search?

Do you need to file an issue?

[x] I have searched the existing issues and this bug is not already filed.
[ ] My model is hosted on OpenAI or Azure. If not, please look at the "model providers" issue and don't file a new one here.
[ ] I believe this is a legitimate bug, not just a question. If this is a question, please use the Discussions area.

Describe the issue
When I use --method global drift "xxxx", I got error says there is no drift search while I saw it updated in the repo..
Steps to reproduce
No response
GraphRAG Config Used
# Paste your config here

Logs and screenshots
No response
Additional Information

GraphRAG Version:
Operating System:
Python Version:
Related Issues:

HI @MinzhiHuang
Could you please add the full command you're running?

I used python3 -m graphrag.query --root ./The_Block --method drift

Also, I just want to ask another question that is when I use the global search, many of the times I get errors of
"creating llm client with {'api_key': 'REDACTED,len=95', 'type': "openai_chat", 'model': 'gpt-4o-mini', 'max_tokens': 4000, 'temperature': 0.0, 'top_p': 1.0, 'n': 1, 'request_timeout': 180.0, 'api_base': None, 'api_version': None, 'organization': None, 'proxy': None, 'cognitive_services_endpoint': None, 'deployment_name': None, 'model_supports_json': True, 'tokens_per_minute': 150000, 'requests_per_minute': 10000, 'max_retries': 10, 'max_retry_wait': 10.0, 'sleep_on_rate_limit_recommendation': True, 'concurrent_requests': 20}
not expected dict type. type=<class 'str'>:
Traceback (most recent call last):
File "/opt/anaconda3/lib/python3.12/site-packages/graphrag/llm/openai/utils.py", line 130, in try_parse_json_object
result = json.loads(input)
^^^^^^^^^^^^^^^^^
File "/opt/anaconda3/lib/python3.12/json/init.py", line 346, in loads
return _default_decoder.decode(s)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/anaconda3/lib/python3.12/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/anaconda3/lib/python3.12/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
not expected dict type. type=<class 'str'>:
Traceback (most recent call last):
File "/opt/anaconda3/lib/python3.12/site-packages/graphrag/llm/openai/utils.py", line 130, in try_parse_json_object
result = json.loads(input)
^^^^^^^^^^^^^^^^^
File "/opt/anaconda3/lib/python3.12/json/init.py", line 346, in loads
return _default_decoder.decode(s)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/anaconda3/lib/python3.12/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/anaconda3/lib/python3.12/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
Warning: All map responses have score 0 (i.e., no relevant information found from the dataset), returning a canned 'I do not know' answer. You can try enabling allow_general_knowledge to encourage the LLM to incorporate relevant general knowledge, at the risk of increasing hallucinations.
"
Only with the global search but not local search, may I please know why? Is that an issue with my query?

I'm encountering the same issue with error JSONDecodeError: Expecting value: line 1 column 1 (char 0).

I'm encountering the same issue with error JSONDecodeError: Expecting value: line 1 column 1 (char 0).

I think the reason for this error is that your model is not strong enough to generate valid json format.

how about   raise ValueError(
ValueError: Length of values (65) does not match length of index (66)

I used python3 -m graphrag.query --root ./The_Block --method drift

The version of GraphRAG that includes drift search uses graphrag as a standalone command instead of a module: graphrag query --root ./The_Block --method drift


Lint on push

Adds lint to on push action per #56

This addressed https://github.com/dapr/dapr/issues/1951


validate inputs to optimization algorithm

The optimization algorithm should validate its inputs, and throw exceptions if any are not acceptable, rather than returning NaNs or a BoundsError, or otherwise going off the rails. There should be no inputs to the optimizer that cause the optimizer to return something invalid, even with fuzz testing. Any exception thrown should indicate what's wrong with the input, before running the optimizer, not that a NaN was encountered with running it.
Maybe good to work on this issue along with #255. @rgiordan If you'd rather focus on statistical modeling, I'll find time to work on both issues. @gostevehoward  -- If working with the optimizer continues to be challenging, please let us know and we'll prioritize this issue.

The vast majority of cases have been resolved. The only ones left are documented in other issues: #414 and #415.


Warning React 18 ReactDOM.render

Hi,
I'm using release 18 of react (below short list of the dependencies using in the project):
    "leva": "^0.9.29",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "react-scripts": "5.0.1",

I receive warning in the console after adding leva useControls in the component (below print from console):
Warning: ReactDOM.render is no longer supported in React 18.
Use createRoot instead. Until you switch to the new API, your app will behave as if it's running React 17.
Learn more: https://reactjs.org/link/switch-to-createroot

Duplicate of #358


[rom, keymgr] Advance state from INIT to ROOT_CREATOR results in error.

Use PR lowrisc/opentitan#7109 to reproduce this issue.
Attempting to advance from INIT to CREATOR_ROOT results in:
WORKING_STATE = Disabled
OP_STATUS = DONE_ERROR
ERR_CODE = 0xe

Reproduction steps:
cd ${REPO_TOP}
# build verilator
./meson_init.sh -f
ninja -C build-out/

FLASH_BIN_TEST=build-bin/sw/device/silicon_creator/testing/sw_silicon_creator_lib_driver_keymgr_functest_sim_verilator.elf
build-bin/hw/top_earlgrey/Vchip_earlgrey_verilator \
  --meminit=rom,build-bin/sw/device/silicon_creator/mask_rom/mask_rom_sim_verilator.scr.40.vmem \
  --meminit=otp,build-bin/sw/device/otp_img/otp_img_sim_verilator.vmem \
  --meminit=flash,${FLASH_BIN_TEST}

Hi Tim,
I added additional code to the functional test referenced above to program the CreatorSecret and OwnerSecret in their respective info flash pages. I have to double check the operations to make sure I am doing this correctly.
The devices by default are running in RMA state.
I haven't checked yet to see if other secrets are initialized.

I tried to lock the SECRET2 partition and put the device in DEV or PROD mode, but this results in a flash erase error.
Locking SECRET2 and running the test in RMA mode still fails to advance into CREATOR_ROOT.

thanks Miguel.
Let me bring this thing into DV and have a look.
It's very likely you've run into some kind of design issue since this area
of flash is not well tested.
On Wed, Jun 23, 2021 at 11:31 PM moidx @.***> wrote:

I tried to lock the SECRET2 partition and put the device in DEV or PROD
mode, but this results in a flash erase error.
Locking SECRET2 and running the test in RMA mode still fails to advance
into CREATOR_ROOT.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/issues/6653#issuecomment-867377852,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSUGKLNBFZOAEUDBSD3TULGLDANCNFSM45IGNCYA
.

okay i think i understand what's going on.
A few things.

the flash -> keymgr seed transmission only happens at power up when the seed is determined to be transmittable (SECRET2 is locked)
the creator flash seeds can only be programmed if SECRET2 is not locked, ie, you provision the flash seed and the root keys together in one shot.

So I think the two test cases you went through

dev_state = RMA, SECRET2 not locked
In this state we are able to program the flash.  However, after programming, keymgr is still unaware of it because the "transmit" window has passed.

dev_state = DEV, SECRET2 is locked
Since SECRET2 is locked, even though you normally would have permission to the info page, it is now locked out, resulting in an erase error.

So we can do a few things here

I can try adding a manual reset and that should trigger seed transmission again
Add a mechanism to allow software to request transmission of flash seeds thus relaxing the boot up requirement.  I don't see a huge reason why we have to allow transmission at start-up only.  Let me know what you think.  This last change would require some tweaknig.

It looks like this issue was created just before we added signature verification to Mask ROM (#6550). Updated reproduction steps to use build-bin/sw/device/boot_rom/boot_rom_sim_verilator.scr.40.vmem since functional tests use the test boot rom but I'm not sure if anything else needs to be updated. @tjaychen @moidx PTAL.

thanks @alphan ! this definitely explains why i couldn't reproduce this test exactly.
@moidx does it make sense for this test, we create a signed version of it? I think you wanted to test the ROM programming of some of the inputs as part of the test?

i think this issue can be resolved now as we managed to get the test working.


Data format issue

Memory datas which had a secondary formatting cannot be merged together correctly

The line break (new line) at the end of file is lost after the data is secondary reformatted.

Fixed in version 1.3.5


Bring native_assets ios tests out of staging

Move test added in https://github.com/flutter/flutter/pull/130494 out of staging.

https://ci.chromium.org/ui/p/flutter/builders/luci.flutter.staging/Mac_ios native_assets_ios
https://ci.chromium.org/ui/p/flutter/builders/luci.flutter.staging/Mac_ios native_assets_ios_simulator

Monitor the CI results of the new shard on the Flutter build dashboard. After 50 consecutive passing builds without any flakes, the flake bot will create a PR to remove the bringup: true parameter from .ci.yaml in the Framework tree. This will allow the test to block the tree, preventing breakages. With this change, the new shard will start running in presubmit automatically, unless specify presubmit: false.

https://github.com/flutter/flutter/wiki/Adding-a-new-Test-Shard#steps-to-add-a-new-framework-test-shard
Umbrella issue:

https://github.com/flutter/flutter/issues/129757

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

@vashworth The test status show up as an empty green square with no summary. Do we need to tweak the tests to make it a fully green square?

@vashworth The test status show up as an empty green square with no summary. Do we need to tweak the tests to make it a fully green square?

The hollow green square means it's a bringup/staging test, it'll become a filled green square when it's out of bringup


UI-Unable to view details of services deployed failed in the page

In the page MyServices, the option details is disabled when the service deployed failed.

let me do it

Fixed by the PR https://github.com/eclipse-xpanse/xpanse/pull/1738


Outdated Interfaces vs. Type Aliases

TypeScript Version:  3.3.0-dev.201xxxxx
Search Terms:
Interfaces, Type Aliases
Code
Expected behavior:
The docs for Interfaces vs. Type aliases are outdated. They state that types don't create names for errors whereas interfaces do create names. This isn't true in more recent versions of typescript.
In the first playground link, I test this expecting to see no type name for the error in the line where I assign to the type "Point". Additionally, I expect that I shouldn't be able to extend or implement type aliases as the docs say that I can't.
Actual behavior:
You can see that the errors in each line clearly state the type name of the regardless of whether or not it is a type or interface. You can also see that when I try to extend/implement a type alias, everything transpiles like how you would expect, with no errors
Playground Link:
http://www.typescriptlang.org/play/#src=type Point %3D {
    x%3A number%3B
    y%3A number%3B
}

interface PointInterface {
    x%3A number%3B
    y%3A number%3B
}

const typeInstance%3A Point %3D {x%3A 1%2C z%3A 1}%3B
const interfaceInstance%3A PointInterface %3D {x%3A 1%2C z%3A1}%3B
http://www.typescriptlang.org/play/#src=type Point %3D {
    x%3A number%3B
    y%3A number%3B
}

interface ThreeDimensionPoint extends Point {
    z%3A number%3B
}

class ThreeDimensionPointClass implements Point {
    x%3A number%3B
    y%3A number%3B
    z%3A number%3B
}
Related Issues:
https://github.com/Microsoft/TypeScript/issues/28980

Great one, partially duplicated in https://github.com/Microsoft/TypeScript/issues/28980


Enhancement: add ability to mask some columns from HashedModel commitment

Is your feature request related to a problem? Please describe.
In some use cases, it may be useful to commit to only part of a record, e.g. for maintaining some metadata without creating additional models/tables/attachments.
Describe the solution you'd like
The HashedModel should have a class attribute columns_excluded_from_hash: tuple[str]. Any column names in this tuple should be excluded from calls to generate_id.
Describe alternatives you've considered
First implemented in a subclass, but the pending bug fix will involve changing the generate_id method, so it should be done in HashedModel instead to avoid future problems when updating dependencies.
Additional context
Example implementation (excluding logic for pending bug fix):
    @classmethod
    def generate_id(cls, data: dict) -> str:
        """Generate an ID that does not commit to the columns that
            should be excluded from the cryptographic commitment.
        """
        return super().generate_id({
            k:v for k,v in data.items()
            if k not in cls.columns_excluded_from_hash
        })

Done


hotfix: Adjusting node typos for good

Node 17 is considered a development branch (same for the @types/ package). When I upgrade the project to Node 18, I'll update the types then. This is also a dev dependency so there's no need to worry about it getting to the end user.

Ok man thanks


Camera Qaulity.............

If anyone knows what needs to be done to improve the quality of that camera, please let me know.

Hi, can you provide more details?

already mention has done how to improve the camera quality


chore(package updates): [INFRA-1356] Update CDKTF packages

Goal
Update all CDKTF packages so that the repository is up-to-date.
Todos

[x] Find a way to update all the packages - turns out I needed to uninstall all the provider packages first, update CDKTF to 0.17, then reinstall the provider packages
[x] Get all checks to pass

Reference
https://getpocket.atlassian.net/browse/INFRA-1348

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add ADA compliance for visitor code

By adding accessibility to the visitorCode View, fonts can be scaled, and voiceOver can be applied to elements.
MOB-1775

Looks good to me. Is ADA snapshot coverage planned for the subsequent PR?

Yes accessibility will be covered by snapshot tests

!squash


GPU out of memory

We train the model ( train_siamese_net.py ) on the HistoGraph dataset with default parameters, however the it is crashed with out of memory. Our GPU is 1080ti with 12G memory.
What is the parameter you used? and how long it takes for training ?

We train it with a GPU TITAN Xp. Have you tried to reduce the batch size? It takes quite a lot for training, around 2 days.


object forPrimaryKey publisher

Goals
Subscribe to changes to a single objects attribute
Actual Results
Only the initial value is published, not subsequent updates
Code Sample
realm.object(ofType: Foo.self, forPrimaryKey: foo.id)!
  .publisher(for: \.name)
  .print()
  .assign(to: \.fooName, on: self)
  .store(in: &self.subscribers)

try! realm.write { foo.name = "Test" } // Not printed or stored in fooName

Version of Realm and Tooling
Realm framework version: 5.0.0
Xcode version: 11.4.1
iOS/OSX version: 10.15.4
Dependency manager + version: Pod 1.8.4

If foo is a managed object, then realm.object(ofType: Foo.self, forPrimaryKey: foo.id) isn't doing anything useful; it's just looking up the object you already have and returning another reference to it. If foo isn't a managed object, then try! realm.write { foo.name = "Test" } isn't actually modifying anything in the Realm.
Assuming that's just an issue with the reduction to a small code sample, there's still another issue: publisher(for:) uses KVO to observe the property on the object. One of KVO's footguns is that it does not retain the object being observed, and this extends to publisher(for:). As a result, the object returned by realm.object(ofType:forPrimaryKey:) is deallocated at the end of the statement (in Release builds; in Debug builds it'll be autoreleased and be deallocated an unspecified time later), which means that by the time the write occurs the object being observed no longer exists and the subscription has already been torn down.
To fix this you'll need to hold onto a reference to the object being observed.

@tgoyne Makes sense, thanks a lot for the explanation. Holding onto the object reference fixed it for me!


Optimize SWF file size

Following up on the slight SWF file size increase from splitting the ActionScript into separate "modules" in PR #393, we should investigate trying to optimize the SWF size back down a bit if possible.
The size increased from 2.496 KB to 3.304 KB, which is an increase of ~32%. See PR #393 for additional info, comparisons, references, etc.

Related/overlapping: #146 and #148.


Automatically set order property

If order is not set explicitly, set it automatically according to the child's position among its siblings.
Compatibility pass: for method parameters, if index is not set, copy order to index
In traversals, to select the n'th parameter, use the index field as opposed to the order field
For all frontends except pysrc2cpg, do not manually set order on parameters
Quite a bit of work on removing setting of the order field from c2cpg and javasrc2cpg

Do not merge yet. Still need to look into how this affects codescience.

Closing to bring in step by step.


can not  auto update

VSCode Version: Code 1.11.2 (6eaebe3b9c70406d67c97779468c324a7a95db0e, 2017-04-13T07:56:42.517Z)
OS Version: Darwin x64 16.0.0

can not auto update!!!

Please provide us more information such as logs, behavior etc. Thanks :)

I also have this problem when running VSCode under a non-admin account on macOS. After clicking on Update Now, VSCode goes through the motions of updating itself, quits and reloads itself. Next time you run VSCode, it says that there is an update available and you can go through the process again ... and again.
At now time does VSCode open a dialog box to request Admin permission to update itself. (Which I guess is why the update silently fails.).

@PeterWAWood https://github.com/Microsoft/vscode/issues/7426#issuecomment-277737150
Closing since there's no actual details here.


CCL couldn't get local_idx/count from environment variables on XPU

System Info
- `Accelerate` version: 0.27.0.dev0
- Platform: Linux-5.15.0-91-generic-x86_64-with-glibc2.35
- Python version: 3.10.13
- Numpy version: 1.26.3
- PyTorch version (GPU?): 2.1.0a0+cxx11.abi (False)
- PyTorch XPU available: True
- PyTorch NPU available: False
- System RAM: 1007.61 GB
- `Accelerate` default config:
        Not found

Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[X] My own task or dataset (give details below)

Reproduction
My code is based on this script. And the command to launch my job is accelerate launch training.py.
2024:01:15-03:36:29:(1980058) |CCL_WARN| did not find MPI-launcher specific variables, switch to ATL/OFI, to force enable ATL/MPI set CCL_ATL_TRANSPORT=mpi
2024:01:15-03:36:29:(1980058) |CCL_WARN| could not get local_idx/count from environment variables, trying to get them from ATL
2024:01:15-03:36:29:(1980058) |CCL_ERROR| global.cpp:150 getenv_local_coord: condition global_data::env().ze_ipc_exchange == ccl::ze::ipc_exchange_mode::sockets failed
to get local_idx/count from ATL, set CCL_ZE_IPC_EXCHANGE=sockets explicitly
Traceback (most recent call last):
  File "/soft/fanli/HuggingFace/testcase/fine-tune/run_fine-tune.py", line 261, in <module>
    fire.Fire(train)
  File "/home/sdp/miniconda3/envs/study/lib/python3.10/site-packages/fire/core.py", line 141, in Fire
    component_trace = _Fire(component, args, parsed_flag_args, context, name)
  File "/home/sdp/miniconda3/envs/study/lib/python3.10/site-packages/fire/core.py", line 475, in _Fire
    component, remaining_args = _CallAndUpdateTrace(
  File "/home/sdp/miniconda3/envs/study/lib/python3.10/site-packages/fire/core.py", line 691, in _CallAndUpdateTrace
    component = fn(*varargs, **kwargs)
  File "/soft/fanli/HuggingFace/testcase/fine-tune/run_fine-tune.py", line 254, in train
    trainer.train()
  File "/soft/fanli/hardware-study/transformers/src/transformers/trainer.py", line 1539, in train
    return inner_training_loop(
  File "/soft/fanli/hardware-study/transformers/src/transformers/trainer.py", line 1687, in _inner_training_loop
    model, self.optimizer = self.accelerator.prepare(self.model, self.optimizer)
  File "/soft/fanli/hardware-study/accelerate/src/accelerate/accelerator.py", line 1227, in prepare
    result = tuple(
  File "/soft/fanli/hardware-study/accelerate/src/accelerate/accelerator.py", line 1228, in <genexpr>
    self._prepare_one(obj, first_pass=True, device_placement=d) for obj, d in zip(args, device_placement)
  File "/soft/fanli/hardware-study/accelerate/src/accelerate/accelerator.py", line 1104, in _prepare_one
    return self.prepare_model(obj, device_placement=device_placement)
  File "/soft/fanli/hardware-study/accelerate/src/accelerate/accelerator.py", line 1355, in prepare_model
    model = torch.nn.parallel.DistributedDataParallel(
  File "/home/sdp/miniconda3/envs/study/lib/python3.10/site-packages/torch/nn/parallel/distributed.py", line 795, in __init__
    _verify_param_shape_across_processes(self.process_group, parameters)
  File "/home/sdp/miniconda3/envs/study/lib/python3.10/site-packages/torch/distributed/utils.py", line 265, in _verify_param_shape_across_processes
    return dist._verify_params_across_processes(process_group, tensors, logger)
RuntimeError: oneCCL: global.cpp:150 getenv_local_coord: EXCEPTION: to get local_idx/count from ATL, set CCL_ZE_IPC_EXCHANGE=sockets explicitly
2024:01:15-03:36:31:(1980057) |CCL_WARN| did not find MPI-launcher specific variables, switch to ATL/OFI, to force enable ATL/MPI set CCL_ATL_TRANSPORT=mpi
2024:01:15-03:36:31:(1980057) |CCL_WARN| could not get local_idx/count from environment variables, trying to get them from ATL
2024:01:15-03:36:31:(1980057) |CCL_ERROR| global.cpp:150 getenv_local_coord: condition global_data::env().ze_ipc_exchange == ccl::ze::ipc_exchange_mode::sockets failed
to get local_idx/count from ATL, set CCL_ZE_IPC_EXCHANGE=sockets explicitly
Traceback (most recent call last):
  File "/soft/fanli/HuggingFace/testcase/fine-tune/run_fine-tune.py", line 261, in <module>
    fire.Fire(train)
  File "/home/sdp/miniconda3/envs/study/lib/python3.10/site-packages/fire/core.py", line 141, in Fire
    component_trace = _Fire(component, args, parsed_flag_args, context, name)
  File "/home/sdp/miniconda3/envs/study/lib/python3.10/site-packages/fire/core.py", line 475, in _Fire
    component, remaining_args = _CallAndUpdateTrace(
  File "/home/sdp/miniconda3/envs/study/lib/python3.10/site-packages/fire/core.py", line 691, in _CallAndUpdateTrace
    component = fn(*varargs, **kwargs)
  File "/soft/fanli/HuggingFace/testcase/fine-tune/run_fine-tune.py", line 254, in train
    trainer.train()
  File "/soft/fanli/hardware-study/transformers/src/transformers/trainer.py", line 1539, in train
    return inner_training_loop(
  File "/soft/fanli/hardware-study/transformers/src/transformers/trainer.py", line 1687, in _inner_training_loop
    model, self.optimizer = self.accelerator.prepare(self.model, self.optimizer)
  File "/soft/fanli/hardware-study/accelerate/src/accelerate/accelerator.py", line 1227, in prepare
    result = tuple(
  File "/soft/fanli/hardware-study/accelerate/src/accelerate/accelerator.py", line 1228, in <genexpr>
    self._prepare_one(obj, first_pass=True, device_placement=d) for obj, d in zip(args, device_placement)
  File "/soft/fanli/hardware-study/accelerate/src/accelerate/accelerator.py", line 1104, in _prepare_one
    return self.prepare_model(obj, device_placement=device_placement)
  File "/soft/fanli/hardware-study/accelerate/src/accelerate/accelerator.py", line 1355, in prepare_model
    model = torch.nn.parallel.DistributedDataParallel(
  File "/home/sdp/miniconda3/envs/study/lib/python3.10/site-packages/torch/nn/parallel/distributed.py", line 795, in __init__
    _verify_param_shape_across_processes(self.process_group, parameters)
  File "/home/sdp/miniconda3/envs/study/lib/python3.10/site-packages/torch/distributed/utils.py", line 265, in _verify_param_shape_across_processes
    return dist._verify_params_across_processes(process_group, tensors, logger)
RuntimeError: oneCCL: global.cpp:150 getenv_local_coord: EXCEPTION: to get local_idx/count from ATL, set CCL_ZE_IPC_EXCHANGE=sockets explicitly
[2024-01-15 03:36:35,030] torch.distributed.elastic.multiprocessing.api: [ERROR] failed (exitcode: 1) local_rank: 0 (pid: 1980057) of binary: /home/sdp/miniconda3/envs/study/bin/python
Traceback (most recent call last):
  File "/home/sdp/miniconda3/envs/study/bin/accelerate", line 8, in <module>
    sys.exit(main())
  File "/soft/fanli/hardware-study/accelerate/src/accelerate/commands/accelerate_cli.py", line 47, in main
    args.func(args)
  File "/soft/fanli/hardware-study/accelerate/src/accelerate/commands/launch.py", line 1014, in launch_command
    multi_gpu_launcher(args)
  File "/soft/fanli/hardware-study/accelerate/src/accelerate/commands/launch.py", line 672, in multi_gpu_launcher
    distrib_run.run(args)
  File "/home/sdp/miniconda3/envs/study/lib/python3.10/site-packages/torch/distributed/run.py", line 797, in run
    elastic_launch(
  File "/home/sdp/miniconda3/envs/study/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 134, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/home/sdp/miniconda3/envs/study/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 264, in launch_agent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
============================================================
fine-tune/run_fine-tune.py FAILED
------------------------------------------------------------
Failures:
[1]:
  time      : 2024-01-15_03:36:35
  host      : a4bf01943df8.jf.intel.com
  rank      : 1 (local_rank: 1)
  exitcode  : 1 (pid: 1980058)
  error_file: <N/A>
  traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html
------------------------------------------------------------
Root Cause (first observed failure):
[0]:
  time      : 2024-01-15_03:36:35
  host      : a4bf01943df8.jf.intel.com
  rank      : 0 (local_rank: 0)
  exitcode  : 1 (pid: 1980057)
  error_file: <N/A>
  traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html
============================================================

Root-Cause
The error log above say that oneCCL could not get local rank from environment variables and here is the oneCCL source code. The reason of the error is that I am not using mpirun -f hosts -n 2 -ppn 2 python xx.py, but accelerate launch xx.py to launch my distributed job. And by default oneCCL recognizes MPI-Launcher.
In order to make it work, we need to explicitly set the environment CCL_PROCESS_LAUNCHER as specified here. Among the 3 options, we should go for "none" and explicitly set the CCL_LOCAL_SIZE and CCL_LOCAL_RANK. Then both mpirun and accelerate launch will work for distributed training on XPU.
Expected behavior
I should not get this error when running distributed fine-tuning on XPU and somewhere in accelerate should set this environment variables for me.

Here is the PR for this issue: https://github.com/huggingface/accelerate/pull/2339. @muellerzr pls have a review. Thanks!

Resolved via #2339.


White background color Card in darkmode

Problem:
@ saas-ui/react Card component will render white background in darkmode.
This happend after upgrading saas-ui to the newest version. Everything was working fine at "@saas-ui/react": "1.7.3".
Current dependencies:
"@chakra-ui/icons": "^2.0.14",
"@chakra-ui/react": "2.4.4",
"@emotion/react": "^11",
"@emotion/styled": "^11",
"@headlessui/react": "^1.7.5",
"@heroicons/react": "v2",
"@saas-ui/forms": "^1.4.1",
"@saas-ui/react": "^1.7.3",
"framer-motion": "^6",
"next": "12",
"react": "18.2.0",
"react-dom": "18.2.0",
"typescript": "4.9.4"
Using theme from '@saas-ui/react'

Current: Card > Background color = 'background: var(--chakra-colors-white);'
Previous (desired): Card > Background color = 'background: var(--chakra-colors-whiteAlpha-100);'

This is a common issue when upgrading saasui/chakraui and is caused by multiple versions of @chakra-ui/system being loaded into the project.
In case you are using yarn 3 running yarn dedupe will 90% of the time fix this.
Also make sure to upgrade Chakra UI to 2.4.9 when upgrading to 1.8.x

Thanks a lot! yarn dedupe fixed the problem right away.


Make the height of the editor in Review Box smaller (4 lines as GitHub)

As the title (and see the comment in PR)
This PR tries to improve the UI. And partially helps

https://github.com/go-gitea/gitea/issues/18183

Before

After

can we shrink the size of the dropzone too?

can we shrink the size of the dropzone too?

I have tried but found it a little more difficult. Since we are working for 1.16-rc, time is limited, maybe we can refactor the Dropzone later (and with others together).

Should probably remove the dropzone completely and make the edit box act as a drop target instead. But I agree it's something for another PR.

wouldn't this simply target the dropzone to make it smaller?
.review-box .dz-message {
   margin-top: 10px;
   margin-bottom: 10px;
}

OK that's giving a slightly odd appearance due to the min-height rules but we could stick a slightly higher margin-top on the .dz-message - or even do
.review-box .ui.dropzone.dz-clickable {
   min-height: 0!important;
}

But if we drop something it, it will be much larger 😂
I think we could use some other design instead of introducing too many !important.

The fact that it grows when it actually contains something is fine by me!
We don't need it to take up all that space when it's empty and is likely to be empty for the majority of the time.

(unfortunately the !important is necesitated because of another !important elsewhere. I agree !important is AWFUL but as you correctly say - this is a bodge to fix things for 1.16.)

The !important is not necessary. I can handle it.
How do you think about the two new UI?

now that looks a bit tight around the drop files to me!
(Sorry this is going round and round slightly.)

now that looks a bit tight around the drop files to me!
(Sorry this is going round and round slightly.)

That's fine. I also feel the height is a little small. Let's make it larger.

And if we get rid of the margin-bottom from the editor
 or put the dropzone in the same
 that should make them more connected...

How about move the drop box on top of lines and words counting and move lines and words counting on left bottom corner.

It's impossible now. lines and words counting is inside the EasyMDE, it is a part of it.

trigger bot


Some agents with online updates fail when used with step_offset of train_agent

The PCL implementation causes a minor error when it is used with step_offset, because of
if self.t - self.t_start == self.t_max:

in pcl.py, while self.t is overwritten by train_agent.  To be precise, assert self.t_max is None or self.t - self.t_start <= self.t_max will fail at the beginning of PCL.update_on_policy (https://github.com/toslunar/chainerrl/commit/f8d07b385d11cd63aea03558cfc4eb1db632d370).
The implementations of A3C and ACER seem to have the same issue if trained by train_agent instead of train_agent_async.

Good catch. The problem comes from the fact that resuming agent training via step_offset is not well tested.


Outdated pip reference in "Strictness and spec enforcement" docs

On https://docs.astral.sh/uv/pip/compatibility/#strictness-and-spec-enforcement it says:

uv tends to be stricter than pip, and will often reject packages that pip would install. For example, uv omits packages with invalid version specifiers in its metadata, which pip similarly plans to exclude in a future release.

As of pip 24.1, pip now rejects those versions too - so it's no longer a "future release".
I was going to open a PR to remove that last sentence, however, it seems that it would be useful if this section of the docs still had an example - so I thought you might want to add another in its place (and I don't know of any)?

I found something to replace this with.


i386: Update asmhelpers.S

Should be In accordance with /arch/i386/debugbreak.S. If not, project would fail in x86 building(And other related issues still exists in x86 building for sure).

@obastemur Can you take a look? I'm not too familiar with this syntax.

@dwfault IIRC this file wasn't failing to build already. Could you please explain your changes?

It's for Linux x86 build. Just something  from an unsuccessful compile attempt.
With this modification, there would be one less error in Linux x86 build. Thanks for attention.

@dwfault Thanks for the answer. Looking at the definitions, I'm not sure what's wrong with the current definitions there. Could you please explain?

I'm fraid not. Maybe the current format is not recognized by Linux x86 building system but works well with x64. I'm not sure.
And I noticed that ChakraCore is not going to support Linux x86 in a short/medium run? So maybe this  pr is with nothing significant...anyway, you could have a try and maybe understand this pr.

I noticed that ChakraCore is not going to support Linux x86 in a short/medium run?

That's also what I know :)
The problem is that this PR replaces common preprocessor defs with their expanded versions and keeping one or two things out (IMHO it shouldn't). We could fix (if necessary) definitions instead but at the moment it wouldn't make much difference.
Thanks for the effort and sending this PR! and also quick replies! If you are interested, we have bunch of issues open and waiting for contributions! --> https://github.com/Microsoft/ChakraCore/issues?q=is%3Aissue+is%3Aopen+label%3A"help+wanted"
Closing this one for now. Feel free to open it back if you feel like these changes are needed.

Thanks!


Error: interface not found in proxy object: org.bluez.GattService1

So I'm currently trying to get some characteristic values from a device, but unfortunately I can't fix this error. Using bluetoothctl I can easily extract the characteristic values, but with the package things fail.
const { bluetooth, destroy } = createBluetooth()
const adapter = await bluetooth.defaultAdapter()

const device = await adapter.waitDevice(uuid);

if(! await device.isConnected()) {

  await device.connect();
}

console.log(await device.isConnected());
await device.gatt();

throw new Error(`interface not found in proxy object: ${name}`);
            ^

Error: interface not found in proxy object: org.bluez.GattService1

Can you provide your operating system name and version?

I'm using Ubuntu 22.04. as OS.

Thanks for the feedback. I added this ubuntu version on the CI pipeline, but I don't see any issue https://github.com/chrvadala/node-ble/pull/39.
Have you tested it on a fresh Ubuntu 2204 installation?

I'll investigate further in the upcoming days and give some additional information..

I have run into this problem on Ubuntu 22.04 too. Was any resolution found for this issue ?

any update ?👀
This problem still exists 🚶♂
Error:
/home/erfan/Desktop/bluetooth/node_modules/dbus-next/lib/client/proxy-object.js:81
      throw new Error(`interface not found in proxy object: ${name}`);
            ^

Error: interface not found in proxy object: org.bluez.GattService1
    at ProxyObject.getInterface (/home/erfan/Desktop/bluetooth/node_modules/dbus-next/lib/client/proxy-object.js:81:13)
    at BusHelper._prepare (/home/erfan/Desktop/bluetooth/node_modules/node-ble/src/BusHelper.js:32:42)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async BusHelper.prop (/home/erfan/Desktop/bluetooth/node_modules/node-ble/src/BusHelper.js:62:5)
    at async GattServer.init (/home/erfan/Desktop/bluetooth/node_modules/node-ble/src/GattServer.js:31:20)
    at async Device.gatt (/home/erfan/Desktop/bluetooth/node_modules/node-ble/src/Device.js:156:5)
    at async /home/erfan/Desktop/bluetooth/main.js:31:24

Node.js v20.9.0

Do you have a way to reproduce it? A test case would be great

Do you have a way to reproduce it? A test case would be great

test it on ubuntu 24.04


Make sgpt much better!!!

Two things would make this tool much better

Accept the prompt from stdin. I did this by using this   prompt: str = typer.Argument(... if sys.stdin.isatty() else sys.stdin.read(), ...
Have an option for 'no preprompt' so we can use this to ask GPT any kind of question. Currently it will say I'm sorry, but as a Command Line App ShellGPT, I am not capable ...

Here are some uses for the stdin optin above
(echo 'summarize this file for me'; cat main.py) | sgpt
or
(echo 'explain these files to me'; ls /var/log) | sgpt

Another goodie would be an option for --pure-code which would print the code only but 'without' the backquotes so you can do this
sgpt --pure-code 'python code for printing first 10 prime numbers'  | python

Two things would make this tool much better
1. Accept the prompt from stdin. I did this by using this   prompt: str = typer.Argument(... if sys.stdin.isatty() else sys.stdin.read(), ...

2. Have an option for 'no preprompt' so we can use this to ask GPT any kind of question. Currently it will say I'm sorry, but as a Command Line App ShellGPT, I am not capable ...

In 1, I should have shown the whole line
prompt: str = typer.Argument(... if sys.stdin.isatty() else sys.stdin.read(),  show_default=False, help="The prompt to generate completions for."),

Having said that I do love this tool :-)

#80 #86 #93
Good luck getting stdin added.

oh and #35


Cannot find module 'vue'

Describe the issue / bug.
previous version (webpack 1) its works fine, but in current version (webpack2) i got this error " Cannot find module 'vue' "
How can I reproduce this problem?
install new version from vue-cli on window10 , npm i and finally  run with "npm run dev" command.
If visual, provide a screenshot.

Tell me about your development environment.

Node version: 6.9.1
NPM version: 3.10.10
vue-cli version: 2.10
Operating System: windows10

From #102

Node version: 7.4
NPM version: 4.1.2
vue-cli version: (if necessary) 2.8
Operating System: Windows 10 x64

@RezaHaidari
Can you confirm node_modules were installed inside the app directory?

Yes, they installed under /app/node_modules/
-vue
-vue-electron
-vue-router
-vuex

@MatthewOverall
Are you also on Windows?

Yes

What can I do to help? I just pulled this down for the first time and can't see immediately where the issue is coming from. If you can't replicate the issue in your environment I would be glad to set up a remote session.

@MatthewOverall
Currently trying to investigate within a virtual box. But I think it might be an issue trying to add app/node_modules to globalPath in app/index.ejs.

Yes, you are correct, the path seperator is acting as an escape char.
require('module').globalPaths.push('D:\Source\cube-utils-ui\app\node_modules')
vs
require('module').globalPaths.push('D:\\Source\\cube-utils-ui\\app\\node_modules')

Just caught myself, lol. This is pretty unfortunate, going to apply a fix shortly.

In the meantime @RezaHaidari, until he releases the fix.
replace
require('module').globalPaths.push('<%= htmlWebpackPlugin.options.appModules %>')
with
require('module').globalPaths.push('<%= htmlWebpackPlugin.options.appModules.replace(/\\/g,'\\') %>')
inside the index.ejs file.

Your fix dosen't work for me @MatthewOverall.
The new fixed path is incorrect, my path doesn't have any "/" by default.
(With htmlWebpackPlugin.options.appModules)
Path with the new fix:

@charlesdelorme
copy new update, work for me.
require('module').globalPaths.push('<%= htmlWebpackPlugin.options.appModules.replace(/\/g,'\\') %>')
thanks @MatthewOverall

@charlesdelorme You must have coppied it just before my edit.
require('module').globalPaths.push('<%= htmlWebpackPlugin.options.appModules.replace(/\\/g,'\\\\') %>')

Thanks for the help @MatthewOverall ! My virtual box is very sluggish to get things done quickly.

@SimulatedGREG
Glad to help. Thanks for creating this boiler plate project. Really well done.


aws: registry_auth_aws fixes

Changes

Serious bugfix
Make hubploy update docker config when role_arn is used.
Micro bugfix
Make hubploy set variables early so we avoid risking variable unset errors in our finally clause.
Loud failure 1
Make hubploy fail loudly if service_key is invalid
Loud failure 2
Let hubploy fail loudly if both service_key and role_arn are passed

Review recommendation
Review commit by commit, they are quite cohesive logically to represent the changes listed.

 It seems like different commands are influenced differently by having them set.

Thanks, @consideRatio!

@yuvipanda thanks for your time to review and merge! :heart: I rebased #106 on this which should make it a bit easier to review now.


It is now known as "Azure Data Lake Storage"

The current name is "Azure Data Lake Storage".  "Azure Data Lake Store" was the previous name.

@saveenr Could you review the proposed changes? Thanks.

Bug opened for PRMerger issues: https://ceapex.visualstudio.com/SRE/_workitems/edit/112917

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

@ktoliver Please review this PR and merge.  Thanks!

#sign-off

@JasonWHowell: I'm sorry - only the author of this article, @saveenr, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Fix broken link with redirect - .openpublishing.redirection.cognitive-services.json

Hi @jasonwhowell - This pull request was opened in the public repo. Content managers should work in the private repo, per the Microsoft Docs contributor guide. Would you make this content update in the private repo instead? Thank you! We'll close this PR.


feature request: unicode in source

Introduction
Some languages now support Unicode (mostly UTF8) for writing source code. It would be great if one could also use Unicode in Stan source.
Broadly, there are two possible levels of support:

in variable and function names (eg ϕ), and
in operators (eg ≤), which provide synonyms for existing ones (eg <=)

Example
This is how the 8 schools example would look like in unicode:
data {
  int<lower=0> J;             // number of schools
  real y[J];                  // estimated treatment effect (school j)
  real<lower=0> σ[J];         // std err of effect estimate (school j)
}
parameters {
  real μ;
  real θ[J];
  real<lower=0> τ;
}
model {
  θ ~ normal(μ, τ);
  y ~ normal(θ, σ);
}

Possible benefits

more compact source code
better mapping to equations in papers

Possible downsides

editor/entry support
font support
possibly corrupted files

The first two are mitigated by the fact that ASCII is a subset of UTF8, so using the feature is optional.
UTF8 support in various languages which have interfaces for Stan

language
identifiers
operators

R
yes
no

Python
only from version 3
no

Julia
yes
yes

Matlab
yes, but needs to be enabled
no

Stata
yes, from version 14
no

Editor support
Emacs
See this list for various UTF8 implementations using autocomplete, company-mode, and quail.
See also

discussion on stan-dev
detailed description for Julia

Should this be under Stan rather than CmdStan?

Sorry. Moved it.


Few changes made in exun talks

VinyakP told me to change the description of one of the speakers

Cool, merging.


No more fixed link for Cuda Archive download link

Added a Dictionary mapping between CUDA Version and the appropriate CUDA archive link.

We no longer accept PRs to 1.14 or earlier branches as we no longer do releases for these versions.


checksum: add FxHash and GxHash based checksum

This is just to test out the performance compared to the xxhash we've been using until now.  Early measurements with 4M blobs have shown that it could be worth experimenting with fxhash (https://lib.rs/crates/rustc-hash) which is used in the rust compiler. Another one worth trying out is ahash (https://lib.rs/crates/ahash) used by hashbrown. Ahash is too unstable.

Due to stability concerns i've tested some of the hash impls with a bunch of different compiler versions on different CPUs and indeed ahash is quite unstable, but fxhash remained remarkably stable.  They all produce the same hash for a given input under stable and nightly.

Numbers from one of the EPYC 9000 servers:
GxHash:
	Minimum: 45441 ns
	50%: 46400 ns
	95%: 47980 ns
	Maximum: 53160 ns
ahash:
	Minimum: 123610 ns
	50%: 126410 ns
	95%: 128561 ns
	Maximum: 135941 ns
XxHash:
	Minimum: 217851 ns
	50%: 221981 ns
	95%: 226151 ns
	Maximum: 246701 ns
Highway:
	Minimum: 320102 ns
	50%: 324492 ns
	95%: 327932 ns
	Maximum: 344701 ns
FxHash:
	Minimum: 708773 ns
	50%: 710374 ns
	95%: 711574 ns
	Maximum: 727214 ns
ZwoHash:
	Minimum: 708794 ns
	50%: 714243 ns
	95%: 717874 ns
	Maximum: 728874 ns
Murmur3:
	Minimum: 3144406 ns
	50%: 3149066 ns
	95%: 3153416 ns
	Maximum: 3623948 ns

The PR should be mostly finished now, I'll perform some tests and then merge it down. From the hashing implementations now in the stack the order in regards to performance seems to be: GxHash > XxHash ~ FxHash. The latter two really are system-dependent, I've had systems in the testbed in which XxHash outperformed FxHash by 2x and some in which FxHash is somewhat faster than XxHash. Although overall, GxHash seems to be No. 1 in each of these machines.

The picture is similar for Highway.

After some benchmarking I can validate the performance difference also in Haura, the differences are most notable when cache pressure is highest, for example on point queries. The figure below shows the performance scaling with XxHash in blue and GxHash in orange.

Since there is no data stored beyond ephemeral development stuff in all existing Haura deployments, I took the liberty to modify the default checksum. The version for gxhash is pinned to v3.1.1.


I made changes to the readme file to demonstrate git pull request and…

I have finished demonstrating how to make a pull request and commit changes with commit messages

@Enecode this is a good start. I will go ahead and merge this PR. some few hacks.

always make your commit messages and PR titles as short and descriptive as possible. (less than 50 characters is good)
To ensure that ll commits are signed, always use the following command in your terminal git commit -S -s -m"<commit message>"


TODO: implicit timestamp filtering using one of the log files

Sometimes one log file contains the relevant information on a test or event, and others are background logging that can be quite large and include log content for a long time (such as a syslog or db log).
Command line switch to designate one of the input files as the implicit start/end time range for merging.

Would also be good to include a few records from the other log files before and after, since extra context is sometimes the crucial piece of information.

0.9.0 added --autoclip command-line option, though output is clipped just to the timestamps in the first file, with no added lines from the other files.


status totals (quick?)

I usually get the status totals from the query builder, but JB would like an interim update for a grant.
Could you  supply me with
protein coding status

published
biological role interred
conserved unknown
S. pombe specific protein uncharacterised
Schizosaccharomyces specific proetin, uncharacterized
(I'm not sure how these are stored in Chado, but they come from the artemis 'colour' qualifier.

In fact there might be a   link where I can access them for the current build directly?, so you might only need to point me here?

[ ] update totals  in spreadsheet for JB (vw)

https://curation.pombase.org/pombe/view/object/cv/21?model=chado

Thanks, I sent the updated spreadsheet to JB


refactor(symbolwinbar): Minor performance improvement

I think (left + right) >> 1 is better here
#a > 0 is likely optimized by luajit but optimizing it doesn't make the code uglier so might as well...

LGTM

yeah maybe good .Oh  there has some change in symbolbar
1 . currently it will ignore user winbar config .so provide a function then can set into winbar config.

better events logic .


[REQUEST] Font settings

Please, can add Font settings for the code editor and the user interface also, because on small display (laptop) all is too microscopic.

I fully agree with @milen-prg , the font used are too small and should be appreciated the possibility to change font.

Hi and thank you @milen-prg and @BOB63 ♥
I'm sorry, but unfortunately I'm not working on it at the moment :(
I'm co-founding an AI start-up dedicated to e-commerce customer service... (www.achille.ai).
However, you can always open the package/zip and go to the CSS file to try and change the fonts and sizes.
It's Web format behind the UX ;)


Error subimmting share: Too many shares pending

Hi guys!
I am a HiveOS user and I have a problem with the miner.
I have tried with several pools, and two different wallets and in all cases I do not get shares, the error appears: "Connection terminated: Error submitting shre: Too many pending shares" attached screenshot.
Apparently, it connects correctly to the pool and the hasrate is good 14.44Kh with two 3080Ti. But there are no valid or rejected shares either.
Can anybody help me?
Thank you so much!

Unfortunately is this out of our control - best to contact either the miner developer or a pool operator.


[typescript] Including typings in published package

Fixed #7696.

[x] PR has tests / docs demo, and is linted.
[ ] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Duplicate of #7686?

I'm closing for #7696, thanks for the contribution!

@oliviertassinari #7686 isn't a duplicate, it addresses a different set of changes and does not include the fixes in this one.
Instead, I will leave a comment on #7686 to include the changes I've made here, and hope it doesn't get merged without -- or all those tests will be testing something that isn't usable, haha!

Yes it does. As far as I have seen the other PR, the typescript source will be included in the release.


fix(atomic): improved labels for rating facet values

https://coveord.atlassian.net/browse/KIT-1082
Examples:

Rating facet

Inclusion filter on 5 out of 5 stars; 6112 results
Inclusion filter on 4 out of 5 stars; 19182 results
Inclusion filter on 3 out of 5 stars; 3122 results
Inclusion filter on 2 out of 5 stars; 619 results
Inclusion filter on one out of 5 stars; 572 results

Rating range facet

Inclusion filter on 5 out of 5 stars; 6112 results
Inclusion filter on 4 to 5 stars; 24869 results
Inclusion filter on 3 to 5 stars; 27714 results
Inclusion filter on 2 to 5 stars; 28265 results
Inclusion filter on 1 to 5 stars; 28776 results

It's not always stars, user can change it. Could we say something more generic, such as "rating, 5 out of 5" ?


How can I get clean URLs?

I have some html files that I want to serve up, but I don't want to put the file extensions in the names of the files, because I want clean URLs.
Can I have html files with names like index, about, and still serve them up like html files to port 8080?
The -e options doesn't seem to work when doing http-server -e html site/. I get no character encoding declared errors in firefox and 404's on the console.
If I do http-server site/ -e html then firefox promps me to download the index and about files.

@wamoyo do you have any interest in exploring / coding this?

I ended up doing a bit of a work around, but I did fork this repo and make some adjustments. I'm happy to explore, absolutely : )

@wamoyo are you looking for something more than what fixing #160 would provide?

So, the fact the html is the default helped me out, and then I ended up creating both page.html and page without the .html extension files for each of my pages. Then pushing the ones without the extension up to S3 with a content-type set to 'text/html'. It works just fine for my purposes.
There's another challenge with this, which is that I can't tell pug (my html template language) to output files with no extension.
If I wanted clean URLs and nothing else, I'd need to fix the issue at the template, local static server, and S3 level. I opted to just fix the third, and rely on http-server's default of type html. This works, and has the added benefit that if someone were to type the .html extension, they'd still get the page they asked for.

Good to know. I'll focus my efforts on #160 then, and revisit more complex options later.
For my part, I'd like something similar to the File Handler in wptserve (a Python-based server for running the Web Platform Tests system at the W3C).
I'd like index to map to index.html (if it exists...and possibly through a series of other media types if found...perhaps optionally). I'd also very much like their .headers file thing for adding arbitrary headers to responses per file or directory. Super handy for all kinds of things. But decidedly a different issue. 😄
I'm going to close this in favor of focusing on #160 and/or filing additional more fixable bugs/features. :wink:
Thanks for the feedback @wamoyo!


Added two handed interactions to NVRInteractableItem

Added two-handed interactions to NVRInteractableItem.  Just select the checkbox in the inspector to enable for any items you want to allow "two handed" grabs.  Enabled for large yellow boxes in Example scene.   Added ForceEndHover() and cached transforms to help out.
Also, some refactoring (space changes/removal of excess 'using' includes) done automatically by a plugin.

Ugh, that is some horrible diffing, I really didn't alter it THAT much.  You could skip taking the scene file and manually make those changes, i just checked off the 'two handed' box on all the big yellow boxes.

Thanks a bunch for this pull request @SmartCarrion. And thanks for your support in the community! Sorry it's taken me so long to address. I've gone ahead and used this pull request as an example to implement two handed interactions in a slightly different way. We now have Interactable.AttachedHands and AllowTwoHanded. I added support for interaction points too. Basically your first hand gets the interaction point. I need to expand out interaction points later to separate include right/left and touch/vive points, but that's a later feature.


Add static file configuration & update how to contribute

Corresponding PR on the main repo: https://github.com/danny-avila/LibreChat/pull/3455
Summary
This updates the ENV config to address the new variables I added for the static cache. I put this right after ports in the Server Config section.
Additionally, I wasn't able to find this repo so I added that to the "Contributing to the Docs" page.
Apparently, my auto-formatter fixed some extra trailing spaces as well. Sorry about that.
Copilot Summary
This pull request includes several updates to the documentation to enhance clarity and provide additional configuration options. The most important changes include the addition of a new section on static file cache control, updates to the cache control behavior description, and a new "Getting Started" section for contributing to the documentation.
Documentation Enhancements:

pages/docs/configuration/dotenv.mdx: Added a new section on Static File Cache Control, including options for STATIC_CACHE_MAX_AGE and STATIC_CACHE_S_MAX_AGE with explanations on how to configure them.

Contributing Guide:

pages/docs/documentation/index.mdx: Added a new "Getting Started" section with instructions on how to fork the repository, create a branch, and clone it locally for contributing to the documentation.

re-opening this PR here with my changes to the Traefik docs based on the comment here -> https://github.com/danny-avila/LibreChat/pull/3455#issuecomment-2254991375
https://github.com/LibreChat-AI/librechat.ai/pull/98