Version bump torchvision<0.21

Issue #, if available:
Description of changes:
We need to bump the max version of torchvision to support torch 2.4.x. Only torchvision > 0.18 supports torch 2.4.x
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks for the PR! I also have some other dependency updates in the python3.12 PR here. https://github.com/autogluon/autogluon/pull/4536/commits/74831688185416831f6491cbd2758339d8dc6c18

@suzhoum Thanks! I'd recommend using my version range for torchvision, since it includes 0.20.x


Addresses SAM issue 1354

API changes from patch branch

Thanks for tackling this one and for updating the API files for my PR #1352.

It looks like the "Max" parameter of the DiurnalPeriod widget for ur_ec_sched_weekend changed from 12 to 24, but not for ur_ec_sched_weekday. Should these both be 36 for both the weekday and weekend matrix to help address #28? In my testing the widget works with 36 periods, so I'm not sure it matters what the Max parameter value is.
Similarly should invoke.cpp Line 3543 loop 36 times instead of 24?

Yes, definitely! I was going to do a separate pull request for issue 28. The max parameter should set how many colors are added and should limit the max period number.


Generate Comment doesn't work

Before submitting your bug report

[x] I'm not able to find an open issue that reports the same bug
[x] I've seen the troubleshooting guide on the AutoDev Docs

Relevant environment info
- OS: window 11
- AutoDev VSCode: v0.5.2
- IDE:

Description
After Selected code, then click right contextmenu autodev->Generate Comment. It doesn't work. In the output panel, it shows "[error] Commands error 0"
To reproduce

Selected code;
Click right contextmenu autodev->Generate Comment;
See error: In the output panel, it shows "[error] Commands error 0"

Log output
No response

用的哪家的模型？

使用的是什么语言？

我这边遇到同样的问题， 是用的模型是 Tongyi

可能得看看日志；


diffculty R5 implementation

New difficulty algorithm implementation

It is not ready yet,  I need to fix build error on Mac

Error is fixed,  PR is ready for review.


Class 'LynX39\LaraPdfMerger\PDFManage' not found

I have this error:
Class 'LynX39\LaraPdfMerger\PDFManage' not found
what can be the problem, I do it all the instructions to install

The pacakage have a little bug, in local it works but in webfaction server fails, the problem is with the name of class is: class PDFManage and should be class PdfManage

Hi @carlituxman, thanks for issue.
Resolved!

Why the composer update don't update this??


Client Get not working

Hi,
In section Subscriptions Client, 'Get' button is not working.
Happy to help if you share what is supposed to happen!
Thanks!

Ah, apologies!  I am still working on that section and missed the link on the main page - it should not be accessible yet.


Crop Area: Kenya 2019

[x] High-quality cropland map generated
[ ] Area estimation pipeline run
[ ] Expert check

@adebowaledaniel here's the 2019 Map- [On EarthEngine] https://code.earthengine.google.com/e2eb13955fe8296e72b9681349550afb


[VL] TPCDS-Q23b failed on large scale

Backend
VL (Velox)
Bug description
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007feb2f043bcb, pid=1573553, tid=0x00007feb1e9ff700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_161-b12) (build 1.8.0_161-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.161-b12 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libvelox.so+0x4b84bcb]  facebook::velox::exec::GroupingSet::extractGroups(folly::Range<char**>, std::shared_ptr<facebook::velox::RowVector> const&)+0xdb
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /mnt/DP_disk5/tpcds/yarn/usercache/sparkuser/appcache/application_1702277591581_0578/container_1702277591581_0578_01_000016/hs_err_pid1573553.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

Spark version
None
Spark configurations
No response
System information
No response
Relevant logs
No response

may related with #4628


Coercing from a timestamp does not work (should it?)

Not sure if a bug or a feature. I have a timestamp in an int that does not get converted to anything.
time = '1529884800'
Dry::Types.module()::JSON::Time.valid?(time) #=> false
Dry::Types.module()::JSON::Time[time] #=>  '1529884800'

The only way it can work, is by doing something like that:
MyTime = Types::Params::Time.constructor { |val| ::Time.at(val.to_i) }

@mensfeld Looks like is the expected behavior, in the coercion https://github.com/dry-rb/dry-types/blob/master/lib/dry/types/coercions.rb#L38 we use Time.parse and if an ArgumentError is raised we return the input, in this case, is what is happening:
Time.parse('1529884800')
ArgumentError: argument out of range

So it is a feature.


fix(space): converting column name entity -> country

Hey @edomt - I think the etl was failing because grapher needs the entity column to be called country, so just changing that here for the exoplanet dataset.

Oops saw you have one open already!

Yes! Thank you though ☺


Automate multiple forms in one Weaver run

I think this is ready for review a little earlier than expected (replaces #631). This PR allows you to automate multiple (related) forms in one Weaver session. Each template is added to the output's bundle and a separate attachment block is added for each file, but the user experience is a single interview. There is no special feature that lets you separate out the documents once the interview is generated.
A lot of code was touched to reach this result.

Some field handling code that had to deal with both PDF-style tuples and DOCX-style string fields was removed. Instead, the fields are put into a single list of DAFields. The source document type is marked for use when necessary.
Much code in the YAML was abstracted and placed into the interview_generator.py file
Some functions in the interview_generator.py file were moved into the DAFieldList class
Some confusing abstractions were simplified--e.g., instead of 3 separate lists to track signatures, custom fields, and "built-ins" there is one list with an attribute of each DAField and some helper methods
Some names were cleaned up. More consistently, I use document instead of f or the_file or other possibly confusing terms. Instead of calling the list of fields fields I renamed to all_fields (which was also used before) to make search easier. (fields has several meanings in the YAML)
Some cleanup of validation to handle multiple source files, and some code moved to the module file
Validation screens had to be modified to handle multiple files. I also now use the human-readable field type and removed some redundant code. There's still room to improve validation screens though--we now have 3: one for DOCX, PDF, and mixed file upload types.
Upload validation now uses the .fix_up() method to validate PDFs. This is faster than pdf_concatenate and has the side effect of letting us fix invalid xref tables and some other PDF issues automatically.

I believe this is a good list of what to test:

[ ] Get a valid YAML output when you automate one PDF
[ ] Get a valid YAML output when you automate one DOCX
[ ] Get a valid YAML output when you automate multiple PDFs
[ ] Get a valid YAML output when you automate multiple DOCX files
[ ] Get a valid YAML output when you automate mixed PDF and DOCX templates
[ ] Invalid DOCX and PDF files generate a human-readable error
[ ] At least one interview you generate from the list above (preferably mixed PDF and DOCX) can be imported and run in the playground after generation
[ ] "Custom" people work correctly for PDF and DOCX templates
[ ] The PDF normalizing functions work as expected
[ ] @purplesky2016's new survey options still work
[ ] I'm feeling lucky still works. You can modify this URL to point to your playground to test I'm feeling lucky: https://apps-dev.suffolklitlab.org/interview?i=docassemble.playground10WeaverMultipleTemplates%3Aassembly_line.yml&new_session=1&form_to_use=https://courtformsonline.org/forms/9174d60bba63599e1506732cb93e52b9.pdf&title=ADM-121+%7C++Attorney+Fees+Billing+Form&jur=AK&nsmi=[]

Some test files that might be useful:
Valid files
01 - Funky Filename ---.docx
civil_docketing_statement_polished_repaired.pdf
Fax_cover_sheet.pdf
made_up_variables.docx
sample_word_template.docx
single_field.docx
test_amount_value.docx
Test_custom_names.docx
test_docket_numbers.docx
test_pdf_fields.pdf
Invalid files
Fax_cover_sheet_corrupt.pdf
invalid_xref_table.pdf (this file should actually work now)
not_a_pdf.pdf
single_field_corrupted.docx
valid_docx_with_mako.docx
valid_word_invalid_jinja.docx
Fixes
Fix https://github.com/SuffolkLITLab/docassemble-ALWeaver/issues/484
Fix https://github.com/SuffolkLITLab/docassemble-ALWeaver/issues/629
Fix #637
progress on https://github.com/SuffolkLITLab/docassemble-ALWeaver/issues/628
possible progress on https://github.com/SuffolkLITLab/docassemble-ALWeaver/issues/559
progress on #558

I'm hopeful that we can review it over the next ~ week? This is a big enough refactor that it puts other Weaver work on hold in my mind (I wouldn't want to deal with merge conflicts created by starting a new feature), but it's so big that I can't imagine it taking less than ~ a week. Please let me know if that's not possible--obviously it will take whatever time it takes!


Error - ValueError: It appears you are trying to construct a functional model, but not all of the inputs in the first positional argument of your layer call are symbolic tensors. (Input objects, or the output of another layer) Functional models cannot correctly track custom layers unless all values in the first call argument are symbolic.

As i am running the training code with coco dataset. Getting the error - ValueError: It appears you are trying to construct a functional model, but not all of the inputs in the first positional argument of your layer call are symbolic tensors. (Input objects, or the output of another layer) Functional models cannot correctly track custom layers unless all values in the first call argument are symbolic.
Getting error in efficientdef function in model.py
def efficientdet(phi, num_classes=20, num_anchors=9, weighted_bifpn=False, freeze_bn=False,
                 score_threshold=0.01, detect_quadrangle=False, anchor_parameters=None, separable_conv=True):
    assert phi in range(7)
    input_size = image_sizes[phi]
    input_shape = (input_size, input_size, 3)
    image_input = layers.Input(input_shape)
    w_bifpn = w_bifpns[phi]
    d_bifpn = d_bifpns[phi]
    w_head = w_bifpn
    d_head = d_heads[phi]
    backbone_cls = backbones[phi]
    features = backbone_cls(input_tensor=image_input, freeze_bn=freeze_bn)
    if weighted_bifpn:
        fpn_features = features
        for i in range(d_bifpn):
            fpn_features = build_wBiFPN(fpn_features, w_bifpn, i, freeze_bn=freeze_bn)
    else:
        fpn_features = features
        for i in range(d_bifpn):
            fpn_features = build_BiFPN(fpn_features, w_bifpn, i, freeze_bn=freeze_bn)
    box_net = BoxNet(w_head, d_head, num_anchors=num_anchors, separable_conv=separable_conv, freeze_bn=freeze_bn,
                     detect_quadrangle=detect_quadrangle, name='box_net')
    class_net = ClassNet(w_head, d_head, num_classes=num_classes, num_anchors=num_anchors,
                         separable_conv=separable_conv, freeze_bn=freeze_bn, name='class_net')
    classification = [class_net([feature, i]) for i, feature in enumerate(fpn_features)]
    classification = layers.Concatenate(axis=1, name='classification')(classification)
    regression = [box_net([feature, i]) for i, feature in enumerate(fpn_features)]
    regression = layers.Concatenate(axis=1, name='regression')(regression)
    model = models.Model(inputs=[image_input], outputs=[classification, regression], name='efficientdet')
    # apply predicted regression to anchors
    anchors = anchors_for_shape((input_size, input_size), anchor_params=anchor_parameters)
    anchors_input = np.expand_dims(anchors, axis=0)
    boxes = RegressBoxes(name='boxes')([anchors_input, regression[..., :4]])
    boxes = ClipBoxes(name='clipped_boxes')([image_input, boxes])

    # filter detections (apply NMS / score threshold / select top-k)
    if detect_quadrangle:
        detections = FilterDetections(
            name='filtered_detections',
            score_threshold=score_threshold,
            detect_quadrangle=True
        )([boxes, classification, regression[..., 4:8], regression[..., 8]])
    else:
        detections = FilterDetections(
            name='filtered_detections',
            score_threshold=score_threshold
        )([boxes, classification])

    prediction_model = models.Model(inputs=[image_input], outputs=detections, name='efficientdet_p')
    return model, prediction_model

getting above error at line ->  classification = [class_net([feature, i]) for i, feature in enumerate(fpn_features)]
tensorflow and keras versions used are same as the one's in requirement.txt

Which TensorFlow version you are using?
This error is likely to appear on tf2. You can either downgrade your tf or make some changes to the code base to make it work on tf2.

Thank you, I was using tf 2.3.1 version only. I upgraded the tf to 2.4 and made some changes in box net and class net call function it works now. Sry. Haven't updated the issue here.

Thank you, I was using tf 2.3.1 version only. I upgraded the tf to 2.4 and made some changes in box net and class net call function it works now. Sry. Haven't updated the issue here.

Can you elaborate on what changes were made in the call() function to get this to work?

@VeereshVS What changes did you make to the box net and class net call functions?

I also encountered the same problem.


Akka http recency

Description
This PR updates akka-http to the latest minor version to gather security related and other fixes.
My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[x] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[x] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

@mhenke1 There is another PR which update Akka related dependencies #4316

@chetanmeh Thx for pointing at that PR which I missed. I will close this one.


How to go in the CallKit when clicking above in-call

Hello Guyz, Any Solution for this when trying to click the above that color green it's doing nothing.
i want is that when clicking the green button above then goes to here and am bit bind don't know where to start.

@diegogarciar  how can i achieve this?

I think we have no control on what callkit does. If its not working probably its an iOS issue. I've seen this issue too with WhatsApp recently.

@diegogarciar yeah i think also thanks for the reply an sorry for my late reply am gonna close this issue


Customize server state script tag

What problem does this feature solve?
In vue-server-renderer, the renderState() method generates a <script> tag in which the context state is injected for client consumption and hydration. Both the contextKey and windowKey are configurable via options, but there is no way to customize the <script> tag for targeting purposes.
I would like to be able to remove this <script> tag from the DOM after client hydration, but it would be very hacky to find and select this node without the ability to define an id attribute or similar on it. I am proposing a new option that will append an id attribute to this <script> tag, called scriptKey. This new scriptKey should be in the same options object that contextKey and windowKey are currently.
What does the proposed API look like?
context.renderState({
  scriptKey: 'VueState'
});

// -> <script id="VueState">window.__INITIAL_STATE__={...}</script>

so that later in the client code this is possible:
const vueTag = document.getElementById('VueState');
vueTag.parentElement.removeChild(vueTag);

This is a good idea, but instead of exposing the option just for the id, why not just expose an option to make the script self-removing? I even think it should be removed by default and only turned on during development.

Even better! Shall I work on a PR for that then?

@markbrouch yes please!

Well, now that I think about it, this <script> tag isn't read until entry-client implementation usually, so I don't think an automatic removal is possible. One thing we could do is provide the boolean option removeOnReplace to context.renderState() and have it append an id attribute to the <script> tag which could then be read by Vuex store.replaceState() here: https://github.com/vuejs/vuex/blob/dev/src/store.js#L158 and removed.

The script registers the global variable window.__INITIAL_STATE__, removing itself doesn't make that variable go away.

Oh I see what you're getting at - we can have the script tag delete itself immediately since it will have already dumped __INITIAL_STATE__ into the global context.


No longer possible to pass PyPI password as envar defined in config options

Hi, already for a year, on various Airflow 2.x versions, we were using the below method to pass the password to the requirements.txt file:

https://docs.aws.amazon.com/mwaa/latest/userguide/best-practices-dependencies.html#best-practices-dependencies-custom-auth-url
--constraint /usr/local/airflow/dags/constraints.txt

--extra-index-url<EMAIL_ADDRESS>
It worked correctly until we upgraded to 2.9 - since then we get the following error:
WARNING: 401 Error, Credentials not correct for https://<gitlab-domain>.com/api/v4/projects/6423/packages/pypi/simple/<package-name>/

There were no changes in configuration options, the option name and password value are still the same. When we hardcode the password directly into requirements.txt - it works correctly, so the password itself is not a problem. It seems the given config is simply not accessible anymore as envar and the related placeholder is evaluated as empty.

Hmm.. this is strange. We are not doing any preprocessing on the requirements.txt file that modifies its content, and literally just pass it to safe-pip-install (our version of pip install). Are you able to produce it using the Docker Compose setup (in the README instructions)?

Ohh.. I see, you are passing in the username and password via environment variables, sorry didn't notice that. Then yeah, I see why that wouldn't work, as we are not passing the environment variables down to the safe-pip-install call. This should be an easy fix.

In fact, the issue you are seeing started to happen after we merged PR #122, as we removed passing down the environment variables to the pip in that PR, because I mistakenly thought it is not useful and might cause issues. We can just revert that line and we should be good.

@rafidka thanks for quick analysis and answer!

We can just revert that line and we should be good.

That would be really great as that's currently the only option not to store a password directly in requirements.txt afaik


Steps have changed.

An image needs to be changed and I have the image however I can't upload it to the images folder.  Deleted the connect clicks which are between a couple steps as they seem to be removed from the process.  Attached the new image that should replace

@sdneufer Your PR currently only deletes the text...you instead should leave the text in place as it was and just replace the image.  If you upload an image of the same name as the original file was named, it will be replaced.

If you navigate to your patch-3 branch, then navigate to the iamges folder, you can use the upload file button to upload your new image file named the same as the existing file.  So, if you have new image files of IFTTT_connect1.png and IFTTTT_connect2.png....then you need to upload them there.

Looks like you've deleted the image paths for two images though.  If you just want to replace them, edit the page to add the file paths back and just upload the images. 👍

I was deleting the two images and text that did not appear when I made the new applet.
I uploaded the image that changed (the text was already changed... appears so anyway) so I did not change that text.

@sdneufer Was this the very first IFTTT applet you were creating? Those two steps you edited out only happen for the very first time you create an applet...so if you'd ever created one before with that account, those would've already been connected services so the link wouldn't have appeared.  Just double checking.

(or at least only used to happen for the very first applet...i haven't set up a new IFTTT account in a couple months to verify...hence my question. 😄 )

I thought about that.  ok... checked it, created a new account...  back to the drawing board. ie... I will comment that the connect buttons only show up when creating the first applet in a new account.
Do I close this one and start over?
Should I choose a different branch?

Totally up to you....You can use your branch of patch-3 still. Any edits you make on that branch will be incorporated into this PR still. So you could edit back in those lines and add a note that those will only appear on the first applet.

Oops, sorry I was late in seeing this 😜


Add CI GitHub Actions workflow

This continuous integration workflow cross-compiles Nickel to WASM,
then builds the rest of the website, and deploys the whole thing to
Netlify using the Netlify CLI. Netlify automatic builds should
therefore be disabled. We use GitHub Actions for the build instead of
Netlify because that way we can use Nix.
The Nickel repo is tracked as a submodule. Changes to the Nickel repo
are not automatically reflected on the website. Instead, the website
tracks releases (once these exist). Deploying changes to Nickel on the
website requires updating the submodule reference by hand.

When switching to nix we should use flake.nix to define multiple (only one initially) nickel inputs that we would track using nix flake update rather than git submodule.

I feel very neutral about git submodule vs nix flake. If you think the latter is better then go ahead. I've never used flakes so wouldn't know where to start. The UX for submodules can be frustrating. Maybe flakes fares better.

we should have a nightly cron github action that updates the nickel inputs/nickel submodule, otherwise we will have to bump nickel branch(es) that we are tracking for the website.

That's a feature, not a bug. Last week, I inadvertently and silently broke the website example when I made a change to Nickel (back when both were still part of the same repo). Admittedly, that's a limitation of the test suite. But until we have better testing, best to manually update these refs I think, following manual vetting. It doesn't need to be all that frequent, because documentation changes don't happen that often. And once we do have a release, then we won't want to update anything on the website except the master version documentation so long as a new stable release hasn't appeared. Examples on the website shouldn't change unless we intentionally change them.

@garbas I forgot to mention: cron job thing is worth a ticket (this is a PR and it's already merged).


Replace UNSAFE_componentWillReceiveProps with getDerivedStateFromProps

Based on https://github.com/ankeetmaini/react-infinite-scroll-component/pull/178

even after making these changes, chrome still gives me the same error about UNSAFE_componentWillReceiveProps.  very odd.

Anybody home?

Sorry for the really long delay. I was too busy. I have updated the PR so that the loader will hide after the component updates. I'm not sure why I have deleted these lines in the first place. Good catch @ankeetmaini :)

Who can merge it?

I'll do a release later today! Thanks :)


[Issue #205] fix: Goal price fix

Description:
Fixes the goal feature, which was broken. Probably related to the obsolete Currency Formatter lib being used. In their own github page:

This is still being used in other places. I did not care to refactor it all because this would require more work than the necessary to fix the goal issue, but would be a good thing to do post V1.
Test plan:
Compile the paybutton.js file locally by running npm run build first on the react/ folder and then on the paybutton/ folder.
Then, create a HTML file e.g:
<!DOCTYPE html>

  <title>lkasdfjaskl</title>


Define ChainRule for runcircuit (w/o noise)

This would make working with noise and AD easy.
The runcircuit w/o noise should be easy to write. You essentially ahve an implementation inside of /src/autodiff.jl
function rrule(::typeof(rayleigh_quotient), O::MPO, U::Vector{ITensor}, ψ::MPS; kwargs...)
  ϕl = runcircuit(ψ, U; kwargs...)
  ϕl = noprime(*(O, ϕl'; kwargs...))

  Udag = reverse([dag(swapprime(u, 0=>1)) for u in U])
  ξ⃗ = MPS[ϕl]
  for udag in Udag
    ξ⃗  = vcat(ξ⃗, apply(udag, ξ⃗[end]; move_sites_back = true, kwargs...))
  end
  ξ⃗l = reverse(ξ⃗)
  y = real(inner(ξ⃗l[1], ψ))
  ...
  return y, rayleigh_quotient_pullback
end

i'm unsure how that should be written with noise. I'm not so familiar with ITensor's notation..

Hi @PhilipVinc,
That's a good point, we could write an rrule directly for runcircuit. Perhaps in that way we could avoid the need for writing an explicit rrule for rayleigh_quotient and make it easier for people to use more general cost functions. We would just need to make sure we can write the rule so that it is just as efficient as the one we would write for rayleigh_quotient directly.
In terms of the noisy circuit evolution, @GTorlai and I have discussed it we have a plan for the noisy circuit rayleigh_quotient rrule, which should translate over to runcircuit. It should mostly just look like the noiseless circuit rule, but you have to be a bit careful about order of operations so the contractions are efficient, since the noisy circuit has nonlocal contractions of the Krauss dimensions. In general, we've written runcircuit to be essentially generic to whether or not there is noise.
Cheers,
Matt

Hi @mtfishman , thanks for the answer.

We would just need to make sure we can write the rule so that it is just as efficient as the one we would write for rayleigh_quotient directly.

You also can have both... and remind users to use reyleigh_quotient for best performance.
(Though, right now reyleigh_quotient does not work with noise, which is why i was using directly runcircuit).

In terms of the noisy circuit evolution, @GTorlai and I have discussed it we have a plan for the noisy circuit rayleigh_quotient rrule, which should translate over to runcircui

I'd be happy to know when you've got a sketch of this working. With @sbarison we are trying to benchmark a few things and this would speed up our calculations enourmously

I believe I've worked out that the rrule for runcircuit directly can be done efficiently (with and without noise), so that would be a good way to go. Agreed we could have definitions for both runcircuit and rayleigh_quotient, but ideally we would avoid code duplication.
Sounds good, glad to hear there is interest in this. We will keep you posted.

but ideally we would avoid code duplication.

If they are the same you can just call a sub-function.
In general, I'd like julia code to be wholly differentiable at the top level.
If a function is exported and accessible by users, it should be differentiable in some form.
Otherwise, how I am to know that one is differentiable and the other ain't? You can document that one might be less efficient, but ideally it should be.

Right, but the goal of an AD library is have a sweet spot, where you define a minimal set of rules and the AD package like Zygote automatically composes them so that a wider range of functionality is differentiable. We would not explicitly make differentiation rules for every single user facing function, that would be impractical and essentially negate a big reason for using AD in the first place.
I'm just proposing the idea that hopefully by making runcircuit differentiable, functions like rayleigh_quotient will be differentiable automatically, since rayleigh_quotient is just a simple wrapper around runcircuit and inner so AD libraries like Zygote should be able to compute it's derivative automatically.
Essentially there is almost not much point in even providing rayleigh_quotient since it is so easy to write in terms of runcircuit and inner, we mostly used it as a convenient function for writing an AD rule to use in cost functions for VQE-like applications.

With regard to:

In general, I'd like julia code to be wholly differentiable at the top level. If a function is exported and accessible by users, it should be differentiable in some form. Otherwise, how I am to know that one is differentiable and the other ain't? You can document that one might be less efficient, but ideally it should be.

I think everyone agrees with that notion, and we consider it a bug if something is not differentiable in PastaQ.jl and ITensors.jl, but unfortunately our manpower and time is very limited and you will find many of these sorts of bugs right now, as we work through things one by one. You'll know if it is not differentiable if it throws an error, and you can raise an issue about it or better yet make a pull request with an rrule.

Sorry! I think i misuderstood what you meant in your previous message!
Of course I agree 100% with what you are saying

Sorry! I think i misuderstood what you meant in your previous message! Of course I agree 100% with what you are saying

No worries, communicating over the internet is imperfect. Glad we're on the same page. In the end, of course we might have to make a specialized rayleigh_quotient rule for efficiency, but hopefully not. Giacomo says he is close to getting an rrule working with the noisy circuit version of rayleigh_quotient and we will discuss how it might work to just make a rule for runcircuit instead.
Also, for context, we are only in the very early stages of adding differentiation support for PastaQ.jl and ITensors.jl. Because of the unique needs of the ITensor indexing interface and tensor network computations in general, many rules have to be written by hand to make things work, so it is a bit of an undertaking. For example, for performance it is very important to account for order of operations of tensor network contractions and caching across tensor network contractions, which are nontrivial tasks in general. Additionally, we can't just blindly rely on rules for linear algebra to help us out, since often our calls to matrix multiplication or matrix decompositions are buried beneath many layers of non-differentiable abstractions. So I hope it didn't come off as snarky when I said that we want people to raise issues and help out, any help with this would be greatly appreciated.


"Fix" OpAnd

This is just a hack, I think there is an uint -> uint8 overflow somewhere that I can't find, that or there is something weird happening with enums.
The bug:
	if b.OpType == ops.OpAnd {

is false even when b.OpType IS equal to ops.OpAnd (somehow?), so it falls back on 	lsrc := c.compileExpNoDestHint(b.Left) and the code below it.

found the root cause, closing


Fix for RestSharp Dependency Issue #101

Upgraded RestSharp Dependency and tested locally.

AppVeyor build and test fail.

@brprigge thank you for your contribution, at this point we don't directly merge PRs. We will have to research on the breaking changes RestSharp has created due to these versions, will put this in our roadmap.

@brprigge thank you for your contribution, at this point we don't directly merge PRs. We will have to research on the breaking changes RestSharp has created due to these versions, will put this in our roadmap.

What is the timeline on the roadmap?  This is preventing us from using your service currently.

Sorry you facing these challenges. Just curious are you using .net core or .net framework?
I see this has already been added to our roadmap will be out with our next release cycle, which will be somewhere in first two weeks of June.

We have a pre-release published on Nuget.
https://www.nuget.org/packages/DocuSign.eSign.dll/4.5.0-rc


Function which will be the most important thing, in MC:PE modding history

A function which will return a string in the clients current selected language.
Like a function ModPE.getStringInClientsLanguage(key); like i want to make See which mob mod it is, if the Mob is pointed for example the pointed entity is a cow, no the user don't understand english at it's best and don't know what mob that is, then we could use the function to return the cow's name for example in the spanish language.
This is important for multilanguage support for mods.

i18n.LANGUAGE_ENGLISH;
i18n.LANGUAGE_SPANISH;
...

i18n.getLanguage(); // Gets language
i18n.getLocalizedValue(key); // Gets a key, but localized for the current language
i18n.setLocalizedValue(lang, key, value); // Sets a key for a language

"Function which will be the most important thing, in MC:PE modding history" not really at all

I18n.setLocalizedValue already exists - it's called ModPE.langEdit; the rest I'll add.

ModPE.getLanguage() and ModPE.getI18n("name") added to latest beta. Thanks!


Add support for external references

Some specifications contain external reference like ref: ../common
Add a support using validator.swagger.io tools.

The service https://validator.swagger.io/ allows resolving a specification with external references.
It just needs parameters resolveFully=true and validateExternalRefs=true
The class SpecificationLoader.cls has been updated to use these parameters if a URL is used to generate the code.
Resolving external references won't be possible if we specify a file instead of a URL.
I also fixed code generation problems with special characters with property names.
Some properties contain _-@
A fix version has been pushed on OEX OpenAPI-suite 1.0.1.
I tested with 3 code generation modes the DID Manager, It looks good, no compile error with the generated code:
Set link = "https://nuts-node.readthedocs.io/en/stable/_static/didman/v1.yaml"
Set sc = ##class(dc.openapi.server.ServerAppGenerator).Generate("dc.Theo.srv",link)
Set features("simpleHttpClientOnly") = 1
Set sc = ##class(dc.openapi.client.Spec).generateApp("dc.Theo.cli", link, .features)
Set sc = ##class(dc.openapi.client.Spec).generateApp("dc.Theo.prd",link)

gen-output.txt


bug in "exp/exp_basic.py"

There's a bug in line 41 "self.model_dict[Mamba] = Mamba", it should be self.model_dict['Mamba'] = Mamba"

Thank, I have merged the pull request.


Debugging Issue

I am getting a debugging issue on this one. Everything else works fine up until I go to debug then I get sh: 1: [: Linux: unexpected operator. Also there is multiple copy past errors where "Node.js" was left in place of C.

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

ID: d57262ff-a4b9-8117-6811-4906376063d0
Version Independent ID: 96cd19ac-d78f-32f8-7339-1fdf76919f81
Content: Debug C modules for Azure IoT Edge
Content Source: articles/iot-edge/how-to-develop-c-module.md
Service: iot-edge
GitHub Login: @shizn
Microsoft Alias: xshi

@QiMata Thanks for the feedback. We are actively investigating and will get back to you soon.

I am experiencing a similar issue. The debug process does work but, depending on how the deployment.template.json file is updated, results may vary. This tutorial needs further clarification on making edits to this file, specifically step two: Build and deploy your module for debugging
Error: No such container: CModule
Command failed: "docker" "exec" "-i" "CModule" "sh" "-c" "sh -c 'uname && if [ $(uname) == "Linux" ] ; then ps axww -o pid=,comm=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,args= ; elif [ $(uname) == "Darwin" ] ; then ps axww -o pid=,comm=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,args= -c; fi'"
Error: No such container: CModule

@formulahendry @adashen

@Mike-Ubezzi-MSFT this is a known issue and caused by cpptools extension. The bug is tracked at https://github.com/Microsoft/vscode-cpptools/issues/2444 The status seems fixed but not released.
And we has also tracked in our tool repo at https://github.com/Microsoft/vscode-azure-iot-edge/issues/283 We will keep this thread updated when the fix from cpp tool is released.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Missing information on Table Max Property Size

The azure-table-storage-scale-targets section is missing information about property size limits which according to the extended error information I just received is 64Kb.
It would have been really nice to have known about this limit at design stage!

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

ID: 1c9ef03f-cf87-a333-623b-afbd39fd75a2
Version Independent ID: 7ab8460b-b303-c829-4c45-462be21b38b2
Content: Azure Storage scalability and performance targets - storage accounts
Content Source: articles/storage/common/storage-scalability-targets.md
Service: storage
Sub-service: common
GitHub Login: @roygara
Microsoft Alias: rogarana

@acrov Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@acrov  thanks for reaching out, we appreciate it. I didn't find anything that actually denotes the max size limit in our documentation. So I will reach out to the product team and try to get confirmation on the actual size limit. I'll let you know what I hear back and update the doc accordingly.

@acrov - We document the property size limitations here. I agree that they should also be in the doc listed above, and I'll make that update.
The total size of all properties combined must be less than or equal to 1 MB. There's no 64 KB limit on an individual property. Can you provide the error message you're getting?
Here's the excerpt from the doc:
Property Limitations
An entity can have up to 255 properties, including 3 system properties described in the following section. Therefore, the user may include up to 252 custom properties, in addition to the 3 system properties. The combined size of all data in an entity's properties cannot exceed 1 MB.

That’s the overall row limit of 1MB.  There IS a limit on the individual property.  You actually document the column limit, albeit implicitly, within the Property Types section - https://docs.microsoft.com/en-gb/rest/api/storageservices/understanding-the-table-service-data-model#property-types by saying Edm.Binary and Edm.String have max size of up to 64k.
The error I get is a 400 Bad Request StorageException with ExtendedErrorInformation of PropertyValueTooLarge – documented here https://docs.microsoft.com/en-us/rest/api/storageservices/table-service-error-codes
I certainly agree that the documentation should include more details on this limit.
From: Tamra Myers<EMAIL_ADDRESS>Sent: 29 May 2019 23:48
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Adrian Crossley<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Missing information on Table Max Property Size (#31488)
@acrovhttps://github.com/acrov - We document the property size limitations herehttps://docs.microsoft.com/rest/api/storageservices/understanding-the-table-service-data-model#property-limitations. I agree that they should also be in the doc listed above, and I'll make that update.
The total size of all properties combined must be less than or equal to 1 MB. There's no 64 KB limit on an individual property. Can you provide the error message you're getting?
Here's the excerpt from the doc:
Property Limitations
An entity can have up to 255 properties, including 3 system properties described in the following section. Therefore, the user may include up to 252 custom properties, in addition to the 3 system properties. The combined size of all data in an entity's properties cannot exceed 1 MB.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/31488?email_source=notifications&email_token=ALWM6EXNFGPEWAFE3CX2KCLPX4B33A5CNFSM4HNWH6I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWQ3FUQ#issuecomment-497136338, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALWM6EVSVNO7NKMQ4S5RI53PX4B33ANCNFSM4HNWH6IQ.

@acrov - Thanks again for your feedback. I have updated the scalability targets for the Table service to document the max total property size and to refer users to the reference for individual property sizes. These changes should be live shortly.
#please-close


Extension issue

Issue Type: Bug
Extension Name: vscodeintellicode
Extension Version: 1.2.12
OS Version: Windows_NT x64 10.0.19042
VSCode version: 1.54.3

:warning: We have written the needed data into your clipboard. Please paste! :warning:

@samdruster thanks for the report - we need a little more detail of what you are seeing before we can make any progress with this issue. Please can you add the info below so we can investigate further? Thanks!:

What language are you trying to use IntelliCode with? (Python/JavaScript/TypeScript/Java/SQL)?
What happens when you try to type a method/property in that language for a common class - do you see IntelliCode "stars" in the autocomplete list?
Can you open up the Output pane (View menu.... Output), then select VS IntelliCode from the dropdown on the top right bar of that pane, and copy the contents of the pane here? It will often contain useful information to help with debugging.  It will look something like this (here for Python):

Hi @samdruster are you still experience issues here?
Feel free to open a new issue if you are, would love to hear from you.


Add SSO login using OpenIDconnect system (auth.durhack.com)

Describe the feature you'd like
Allow only users with the judges category to log in to the judging platform using the auth.durhack.com OpenIDConnect/keyclock system.
Pre-existing Issue or Justification
No response
Additional context
No response

go keyclock support: https://github.com/Nerzal/gocloak
plain oidc support: https://github.com/coreos/go-oidc?tab=readme-ov-file


The function getPrimaryKey in the BaseActiveRecord class  dose not work well

when i use the function getPrimaryKey to get the primary key of data table, if the code not defined attributes ，it returns null  string ,I think it  dose not work well.
codes of the function  getPrimaryKey :
public function getPrimaryKey($asArray = false)
{
        $keys = $this->primaryKey();
        if (!$asArray && count($keys) === 1) {
            return isset($this->_attributes[$keys[0]]) ? $this->_attributes[$keys[0]] : null;
        } else {
            $values = [];
            foreach ($keys as $name) {
                $values[$name] = isset($this->_attributes[$name]) ? $this->_attributes[$name] : null;
            }
            return $values;
        }
   }

What is the expected result?
if the code not defined attributes ，return the primary key of data table is better.
What do you get instead?
Additional info

Q
A

Yii version
2.0.9

PHP version
5.6.18

Operating system
centos 6.5

Please show the contents of your attributes() method. Did you override it to return empty array?
Are you sure that foreign key constraints do exist in the table you are referring to?

@arogachev
The data table dose not use foreign keys  and not define or override attributes()

@yeoman-chen Sorry, I did mean primary keys.


kong error log  'nil while logging' in report_http_status

Summary
When an upstream server return a non-2xx response, kong will log some error like:
2018/02/23 17:14:58 [error] 73739#0: *6034 [lua] balancer.lua:253: report_http_status(): [healthchecks] failed reporting status: nil while logging request, client: <IP_ADDRESS>, server: kong, request: "GET /status-123 HTTP/1.1", upstream: "http://<IP_ADDRESS>:8001/status-123", host: "kong.localhost.com"

The client can get response correctly but this error log is very confusing as we are monitoring kong's error log.
  And a new error log in error.log:

2018/02/23 17:14:58 [error] 73739#0: *6034 [lua] balancer.lua:253: report_http_status(): [healthchecks] failed reporting status: nil while logging request, client: <IP_ADDRESS>, server: kong, request: "GET /status-123 HTTP/1.1", upstream: "http://<IP_ADDRESS>:8001/status-123", host: "kong.localhost.com"

Additional Details & Logs

Kong version: 0.12.1
Operating System: mac or ubuntu

@ZeeShen thank you for reporting! This is already fixed in master, and will feature in the upcoming 0.12.2.


GraphIQl on AWS Lambda

Hi,
I've set up a graphql endpoint with API gateway and AWS lambda.
I'm using the GraphiQL electron app to query my endpoint and it's working like a dream!
Although ... the docs don't show up?
My lambda is just accepting the request, extracting the query, stripping out \n and \ and then sending this off to graphql.  ( its not express so no body-parser ... bummer )
graphql(Schema, query)
This is working fine for queries and mutations but something is wrong when trying to open up the docs tab, just get a spinner ...
I'm not 100% sure whats happening when I open the docs tab and I can't see any requests...
I can introspect the schema with
{__schema {
  queryType {
    name,
    fields { name, description} }}
}

I get a correct response and the docs on the schema are displayed as expected...
So, what does the docs tab do? do I need to supply it manually with the schema?
Many thanks for any help,
Stephen.

Hi @maitriyogin - GraphiQL tries to send an introspection query using your fetcher function to your endpoint when it's first brought up, and the docs explorer wouldn't show up unless your schema is ready, either from this initial introspection step or by manually providing it. It sounds like your introspection step in the beginning when the component is mounted is not successful - would you mind checking that?

Mine is not working and I appear to successfully work with the introspection step?  I also do not have any kind of auto complete.  Not sure what is wrong but all the queries work fine.


pywhatkit.sendwhatmsg_to_group discards all non-Latin letters

Description
Everything is working fine when sending with pywhatkit.sendwhatmsg to one person, but when sending to group all
non-latin characters disappears (like ä,ö etc...)
Version Information

OS: ALMA LINUX 9
Browser: Firefox
Python: 3.9.18
PyWhatKit: 5.3

https://github.com/Ankit404butfound/PyWhatKit/issues/346
kindly confirm if the solution here fixes your requirement.

Hi
Thanks for your help
I'm still unable to send messages to group
Now I get error:
Traceback (most recent call last):
File "/root/send-messages_final.py", line 25, in
pywhatkit.sendwhatmsg_to_group('XXXXXXXXXXXX',(my_string1+'\n'+my_string2+'\n'+my_string3), 10, 52)
File "/usr/local/lib/python3.9/site-packages/pywhatkit/whats.py", line 111, in sendwhatmsg_to_group
core.send_message(message=message, receiver=group_id, wait_time=wait_time)
File "/usr/local/lib/python3.9/site-packages/pywhatkit/core/core.py", line 71, in send_message
keyboard.write(char)
File "/usr/local/lib/python3.9/site-packages/keyboard/init.py", line 854, in write
scan_code, modifiers = next(iter(entries))
StopIteration
And for some reason same code working when sending to one phone number
Kind Regards
Jari
Lähettäjä: Agbayewa Adetunji @.>
Lähetetty: tiistai 26. marraskuuta 2024 2.47
Vastaanottaja: Ankit404butfound/PyWhatKit @.>
Kopio: Jari Ihanainen @.>; Author @.>
Aihe: Re: [Ankit404butfound/PyWhatKit] pywhatkit.sendwhatmsg_to_group discards all non-Latin letters (Issue #348)
#346https://github.com/Ankit404butfound/PyWhatKit/issues/346
kindly confirm if the solution here fixes your requirement.

Reply to this email directly, view it on GitHubhttps://github.com/Ankit404butfound/PyWhatKit/issues/348#issuecomment-2499326410, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5BL37A7YQEZINKUXCRPH4L2CPAGZAVCNFSM6AAAAABSN2WQSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJZGMZDMNBRGA.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

I still suffer with this
When I'm using
pywhatkit.sendwhatmsg('+358 XXX XXX XXX',(my_string1+'\n'+my_string2+'\n'+my_string3), 7, 25)
Everything is just fine

BUT
Using
pywhatkit.sendwhatmsg_to_group('XXXXXXXXXXXXXX',(my_string1+'\n'+my_string2+'\n'+my_string3), 7, 40)
I lost all non-latin charactrs like ä,ö etc...

Please help, I really do not uderstand where is the different between sendwhatmsg and sendwhatmsg_to_group


docs: adds grammar fixes to metadata-management.md

Signed-off-by: Jennifer Power<EMAIL_ADDRESS>Description
Updates information in metadata-management design documentation.
Type of change

[X] This change requires a documentation update

How Has This Been Tested?
N/A, Docs only
Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

/lgtm


Getting blazor error UI while using electron

Description: Today I have decided to use electron.NET with blazor server, I have followed this tutorial and it worked fine.
Now when I started my app again to after some things I have added to my project and I got this issue in the console warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3]       Failed to determine the https port for redirect. I have decided to debug it IIS Express and I got no issues at all.
To try to fix I have tried to:

Remove things from the original project.

Create a new project, follow the tutorial and without changing anything and adding any code to the project use electronize start.

Electron.NET Version: Latest

.NET Core: Latest

Node.js and npm Version: Latest

Blazor Type: Server

Steps to Reproduce:

Create new blazor server project.
Install and setup Electron.NET like in the tutorial.
Run electronize start

Okay a little update today it seems to work like it should but I didn't change or touch anything, you guys should look into it.
Maybe its a problem with blazor/.NET core itself?

Yes this is a Blazor issue not an Electron issue. You should probably close it.

Yes this is a Blazor issue not an Electron issue. You should probably close it.

How is that a Blazor issue if when using Blazor normally I didn't get this problem?

Because I believe that the HttpRedirectMiddleware is running inside your server project, in which case it is not specific to Electron.NET. It is indicating that your launchSettings.json file has incorrect settings.

Because I believe that the HttpRedirectMiddleware is running inside your server project, in which case it is not specific to Electron.NET. It is indicating that your launchSettings.json file has incorrect settings.

Hmm but now without changing anything it works fine for me no errors no something running smooth even as Electron window.


[Podspec] Fix import issues with CocoaPods 1.0 on OS X

Workaround for CocoaPods/CocoaPods#5313.
@TimOliver: This has potential to break MAS-compatiblity. Could you validate whether apps using frameworks like that pass AppStore's automated file validations?
/c @jpsim

@mrackwitz doesn't this break CocoaPods before 1.0? See CI output using 0.39.0:
Setup completed

 -> Realm
 -> Realm (0.102.1)
    - ERROR | [OSX] xcodebuild: Returned an unsuccessful exit code. You can use `--verbose` for more information.
    - NOTE  | xcodebuild:  error: File exists and is not a symbolic link: /var/folders/bj/n03qf0s968d07kcp9bc4v_vw0000gl/T/CocoaPods/Lint/build/Release/Realm.framework/Headers

Analyzed 1 podspec.

[!] The spec did not pass validation, due to 1 error.

@jpsim: Good point. I didn't thought about that at all. But I don't see a way around that until CocoaPods is fixed. If we decide that backwards-compatibility to 0.39 is still a requirement at this point, we would likely need to document a post install Podfile-hook as a workaround in the meantime.


.gemspec.rz files not being generated in 0.5.1

It seems like the .gemspec.rz files stopped being generated in 0.5.1 which makes commands like "gem update " fail miserably with 404 error.

This appears to be a bug in ruby gems incremental index updates.
I'm going to disable incremental updates by default until I can get it sorted out.
Fixed in b65c27dd5979e0614158b4dbc6454e14a15018d5 and deployed as 0.5.2.

Wow, that's fast. Thanks a bunch!


Missing translations

Some content is still not localizable. This list compiles the missing content I noticed untranslatable. Everything is open to discussion :smile:

[ ] Package classifiers (open discussion here #6882)
[x] "Locale updated" banner when switching language
[ ] Status message "All Systems Operational" in the footer (see https://github.com/pypa/warehouse/issues/7455#issuecomment-731915822)
[ ] Size units (kB, GB etc.)
[x] "Released: " in the package details page header
[ ] "Our sponsors" page
[ ] "Terms of use" and "Maintenance page" mirro as discussed in #6565
[ ] Sponsor categories in footer

I fixed the "locale updated" flash message in https://github.com/pypa/warehouse/pull/7452.
The status message is loaded on the frontend from StatusPage so will probably not be localizable.
Some of these are due to https://github.com/pypa/warehouse/issues/6825 as well.

Status message "All Systems Operational" in the footer is translatable.

Status message "All Systems Operational" in the footer is translatable.

It's not, these strings come from an API call to an external service that happens with client-side JavaScript:
https://github.com/pypa/warehouse/blob/0ad848d266619c7961bcc0cc1cdad45fc9495d12/warehouse/templates/base.html#L310-L312
https://github.com/pypa/warehouse/blob/0ad848d266619c7961bcc0cc1cdad45fc9495d12/warehouse/static/js/warehouse/utils/statuspage.js#L14-L26

@NathanBnm That page is mostly marked for translation, although there are a few strings that aren't: https://github.com/pypa/warehouse/blob/27b11434358a8ff98db29a8c701a5b7c1289f207/warehouse/templates/pages/sponsors.html
Unfortunately we can't currently translate the sponsor descriptions.

Additionally plaintext emails and email subjects are not being translated because .txt files are not being searched for translations:
https://github.com/pypa/warehouse/blob/525002445b2f97024e229651259eb9409c9b582d/babel.cfg#L1-L2


Adding ID to list item

What?
Extending the list component to allow a user to pass an ID to a list item, should no custom ID be provide one will be generated.
Why?
Whilst converting an element to use the list component (on Whitehall) this resulted in a testing error due to a missing ID. Current iteration of this gem component does not provide an option to generate an ID or provide a custom one.
This extension aims to resolve this and provide these options for future list component use.
Visual Changes
None however screenshots for Context attached

Anything else?
Raising a draft for feedback if should do this.

There shouldn't be multiple ids that are the same on the page - each list item needs a unique id attribute, or no id attribute.

Agreed. In this context this PR needs to be adjusted for a unique ID attribute.
However as this requirement is currently only required in Whitehall (I've not seen other apps need this feature) currently investigating why a unique ID is being used and if it can be removed to avoid this need for this update.

@maxgds this PR's been sitting around for a while - is this feature still a requirement or can this PR be closed?

I think we found a workaround for this - certainly this work isn't on our radar at the moment. I'll close this but bear in in mind if the issue resurfaces.


envoyfilter match routeConfiguration portName gateway cann't match any routeConfiguration

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
Bug description
envoyfilter match routeConfiguration portName gateway cann't match any routeConfiguration
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
Steps to reproduce the bug
apply following yaml config:
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: match
spec:
  workloadSelector:
    labels:
      istio: ingressgateway
  configPatches:
  - applyTo: VIRTUAL_HOST
    match:
      context: GATEWAY
      routeConfiguration:
        portName: http
        gateway: istio/bookinfo-gateway
        vhost:
          name: "*:80"
    patch:
      operation: REMOVE
  - applyTo: VIRTUAL_HOST
    match:
      context: GATEWAY
      routeConfiguration:
        portName: http
        gateway: istio/bookinfo-gateway
        name: "http.80"
    patch:
      operation: ADD
      value:
            name: "*:80"
            domains:
            - "*"
            routes:
            - match:
                prefix: "/"
              direct_response:
                status: 200
                body:
                  inline_string: "example body\n"

[root@master01 match]# kubectl get gw -n istio
NAME                  AGE
bookinfo-gateway      13d
istio-egressgateway   4d1h
mysql                 16d

[root@master01 match]# kubectl get gw bookinfo-gateway -n istio -o yaml
apiVersion: networking.istio.io/v1beta1
kind: Gateway
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"networking.istio.io/v1beta1","kind":"Gateway","metadata":{"annotations":{},"name":"bookinfo-gateway","namespace":"istio"},"spec":{"selector":{"istio":"ingressgateway"},"servers":[{"hosts":["*"],"port":{"name":"http","number":80,"protocol":"HTTP"}}]}}
  creationTimestamp: "2021-04-21T04:50:50Z"
  generation: 5
  managedFields:
  - apiVersion: networking.istio.io/v1beta1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .: {}
          f:kubectl.kubernetes.io/last-applied-configuration: {}
      f:spec:
        .: {}
        f:selector:
          .: {}
          f:istio: {}
        f:servers: {}
    manager: kubectl-client-side-apply
    operation: Update
    time: "2021-04-21T04:50:50Z"
  name: bookinfo-gateway
  namespace: istio
  resourceVersion: "1491063"
  uid: 08570ff9-3b85-4600-9296-c89612faf26a
spec:
  selector:
    istio: ingressgateway
  servers:
  - hosts:
    - '*'
    port:
      name: http
      number: 80
      protocol: HTTP

Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
[root@master01 match]# istioctl version --remote
client version: 1.9.2
control plane version: 1.9.2
data plane version: 1.9.2 (14 proxies)
[root@master01 match]# kubectl version --short
Client Version: v1.20.5
Server Version: v1.20.5
How was Istio installed?
Environment where the bug was observed (cloud vendor, OS, etc)
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

Since you have operation "REMOVE" on virtualhost Istio removes that virtual host. If you want to update virtualhost use MERGE operation.

what I delete is vhost,not routeConfiguration.
also:
Replace contents of a named filter with new contents. REPLACE operation is only valid for HTTP_FILTER and NETWORK_FILTER. If the named filter is not found, this operation has no effect.

apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: match
spec:
  workloadSelector:
    labels:
      istio: ingressgateway
  configPatches:
  - applyTo: VIRTUAL_HOST
    match:
      context: GATEWAY
      routeConfiguration:
        portName: http
        gateway: istio/bookinfo-gateway
        name: "http.80"
    patch:
      operation: MERGE
      value:
            name: "*:80"
            domains:
            - "*"
            routes:
            - match:
                prefix: "/"
              direct_response:
                status: 200
                body:
                  inline_string: "example body\n"

I used merge no affect

I think this is a bug。
@ramaraochavali

port name match only works for https. I believe this is documented

apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: match
spec:
  workloadSelector:
    labels:
      istio: ingressgateway
  configPatches:
  - applyTo: VIRTUAL_HOST
    match:
      context: GATEWAY
      routeConfiguration:
        portName: httpS
    #    gateway: istio/bookinfo-gateway
    patch:
      operation: MERGE
      value:
            name: "*:443"
            domains:
            - "*"
            routes:
            - match:
                prefix: "/"
              direct_response:
                status: 200
                body:
                  inline_string: "example body\n"

no effect

Seems to work for me. Are you sure the port name is portName: httpS? capital S?
And is the envoyfilter in istio-system ns?

https works fine now，bug gateway must in istio-system namespace
gateway: istio/bookinfo-gateway  is not working


Adapt Point structure to a continous time axis

This PR is related to #13 as "Slide Filter" needs a continuous time axis and currently, we only support discrete time (x-axis). There are two ways to address this problem. 1) Change the Point structure and the implementation of "Swing Filter" to properly utilize the new continuous time axis. 2) Create a new Point structure called ContinousPoint and make "Slide Filter" utilize only this ContinousPoint. I decided the first one is better although it creates changes all around in the Swing Filter's compress and decompress functions. After testing, everything is working well and the new Point is working as expected.

Following https://github.com/cmcuza/TerseTS/pull/38#discussion_r1633848505, I close this PR. A new PR with the corresponding changes and reverting the code in Swing is needed.


namespace_based_enricher.go:64] Failed to get namespace: exist: %!s(bool=false) error:

i use kubernetes v1.1.3。the config file to run heapster is below:
apiVersion: v1
kind: ReplicationController
metadata:
name: monitoring-heapster-v6
#namespace: kube-system
namespace: default
labels:
k8s-app: heapster
version: v6
spec:
replicas: 1
selector:
k8s-app: heapster
version: v6
template:
metadata:
labels:
k8s-app: heapster
version: v6
spec:
  nodeName: <IP_ADDRESS>
  containers:
    #- image: gcr.io/google_containers/heapster:v0.16.1
    #- image: kubernetes/heapster:v0.19.0
    #- image: gcr.io/google_containers/heapster:v1.0.0
    - image: kubernetes/heapster:canary
      name: heapster
      resources:
        limits:
          cpu: 100m
          memory: 300Mi
      command:
        - /heapster
        - --source=kubernetes:http://<IP_ADDRESS>:8080?inClusterConfig=false&auth=
        - --sink=kafka:?brokers=<IP_ADDRESS>:9092&timeseriestopic=testseries&eventstopic=testtopic

kubectl get namespace shows:
NAME      LABELS    STATUS    AGE
default       Active    55d
see the logs by heapster pod:
I0322 10:51:33.555695       1 heapster.go:61] Heapster version 1.0.0
I0322 10:51:33.555743       1 configs.go:60] Using Kubernetes client with master "http://<IP_ADDRESS>:8080" and version "v1"
I0322 10:51:33.555754       1 configs.go:61] Using kubelet port 10255
I0322 10:51:33.559001       1 heapster.go:87] Starting with Apache Kafka Sink
I0322 10:51:33.559095       1 heapster.go:87] Starting with Metric Sink
I0322 10:51:33.587133       1 heapster.go:166] Starting heapster on port 8082
I0322 10:52:05.000267       1 manager.go:79] Scraping metrics start: 2016-03-22 10:51:30 +0000 UTC, end: 2016-03-22 10:52:00 +0000 UTC
I0322 10:52:05.446183       1 manager.go:152] ScrapeMetrics: time: 445.758866ms size: 55
W0322 10:52:05.446554       1 namespace_based_enricher.go:64] Failed to get namespace: exist: %!s(bool=false) error:
W0322 10:52:05.446577       1 namespace_based_enricher.go:64] Failed to get namespace: exist: %!s(bool=false) error:
why show these errors?
hope some one can help...

Are these warnings repeatable?

Heapster gets a list all namespaces from the API server and adds some namespace information to the pods and containers. If the pod's namespace is not on the namespace's list then the warning is printed (although it is badly formatted - i will fix it right now).
I don't have a clear answer why this was possible given that it had 30 sec to get the namespaces.

thank you very much for you reply!
According to you explanation, I think I find the reason. There are two pods running in kube-system namespace, but kubectl get namespaces command only shows the default namespace. I will test is later, thanks for your help!

Log fixed with #1086


[DIR-928] Lock node version to 18.18.1

Description
Lock node version to 18.18.1

Thanks @sir-hassan. I also updated the node version in the .nvmrc file and linked this to a linear ticket. I wanted to write down a little bit more context for "future me" if i at some point try to update node in the future.


feat: add defineUtility, update utilities and clean plugins

In this PR:

New defineUtility utility
All utilities are reworked to use it
All plugins except hasVitePluginPlugin have been removed as they do not bring anything compared to utilities
Docs have been revamped
Plugins have been de-emphasized from docs as they will be reworked in 0.9
Playground and tests have been updated

Unfortunately, the PR got way too big so here is how you can review it without losing your sanity:

On the files tab only review changes made outside of docs
Review docs carefully by visiting the preview
I need confirmation on the hasVitePluginPlugin implementation. Does the updateConfig patching still work now that we pass params directly?

TODO:

[x] Add defineUtility
[x] Update utilities
[x] Clean plugins
[x] Update playground
[x] Update tests
[x] Update docs

[x] New utility
[x] Utilities
[x] Breaking changes (oh boy)
[x] Recommend template
[x] Check all docs

[x] Changeset
[x] Check hasVitePlugin
[x] Test!!
[x] PR description
[x] How to review

I am currently testing hasVitePluginPlugin in the playground, and it looks like it is not working, but I am still investigating

The overriding issue can be fixed by spreading the params after the plugins instead of before:
  return providedHooks[hookName]?.({
-   ...params,
    ...Object.fromEntries(
	    plugins.map((plugin) => [
		    plugin.name,
		    plugin.implementation(params, { name }),
	    ]),
    ),
+   ...params,
  } as any);


txpool_content reports superfluous account data

txpool_content reports superfluous data
Description
We've noticed with the recent txpool refactor that the txpool_content is now reporting accounts that don't have any pending or queued transactions.
Your environment

OS and version Ubuntu 20
version of the Polygon SDK 1ff87c043c3323665bee55a3124852a27f9b3fbf
branch that causes this issue develop

Steps to reproduce

Tell us how to reproduce this issue  Use https://github.com/mrwillis/eth-txn-spam to spam transactions on a network
Where the issue is, if you know
Which commands triggered the issue, if any

Expected behaviour
txpool_content should not report accounts that have no pending or queued transactions
Actual behaviour
txpool_content reports accounts that have pending or queued transactions, causing response bloat.
Logs
{
    "jsonrpc": "2.0",
    "id": null,
    "result": {
        "pending": {
            "0x004fA466f846Cf3F9759AaE5BA8c9D0F606019D4": {},
            "0x00FF4420E8E7BDCA326611aF9A67728711c726Df": {
                "1055": {
                    "nonce": "0x41f",
                    "gasPrice": "0x3b9aca00",
                    "gas": "0x186a0",
                    "to": "0xA89CFBC28c287Fa4af054a1D72Bec077f62De925",
                    "value": "0x38d7ea4c68000",
                    "input": "0x",
                    "hash": "0xf57869184e7b446ac9a2de164a155495dea89bb035dd3e5cfc2ec5721db2bdbb",
                    "from": "0x00FF4420E8E7BDCA326611aF9A67728711c726Df",
                    "blockHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
                    "blockNumber": null,
                    "transactionIndex": null
                }
            },
            "0x01fFD7736BDA6227a0662dC7FE051327ee41d14B": {
                "1042": {
                    "nonce": "0x412",
                    "gasPrice": "0x3b9aca00",
                    "gas": "0x186a0",
                    "to": "0x4aa7696Ae4dffE4CFCf5E490DD0FFc948b1599A8",
                    "value": "0x38d7ea4c68000",
                    "input": "0x",
                    "hash": "0x3139d05c35ca989d600b5cc6272c181563b8bb0aacf8131845be3b94f74251f0",
                    "from": "0x01fFD7736BDA6227a0662dC7FE051327ee41d14B",
                    "blockHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
                    "blockNumber": null,
                    "transactionIndex": null
                }
            },
            "0x03DD7f83dc6c10Ba10B8C2b689ac1f324CFC87A9": {
                "682": {
                    "nonce": "0x2aa",
                    "gasPrice": "0x3b9aca00",
                    "gas": "0x186a0",
                    "to": "0x8006b05F48EebE5346048A1F297994D15aDdD37f",
                    "value": "0x38d7ea4c68000",
                    "input": "0x",
                    "hash": "0x112defa2a9e06aa90ac5a77c9289fb946028b03f4e1a530cec4824ad01919a32",
                    "from": "0x03DD7f83dc6c10Ba10B8C2b689ac1f324CFC87A9",
                    "blockHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
                    "blockNumber": null,
                    "transactionIndex": null
                }
            },
            "0x05C4771831448090cd01DD557a474e011E9911e8": {
                "751": {
                    "nonce": "0x2ef",
                    "gasPrice": "0x3b9aca00",
                    "gas": "0x186a0",
                    "to": "0x45e837815EAd7af8244222dc540Fd9E4D1a05634",
                    "value": "0x38d7ea4c68000",
                    "input": "0x",
                    "hash": "0xc055970bcf92dab7a299e2e3e2f0285c0dad7e32f613f3c5abdba5460b8b16a5",
                    "from": "0x05C4771831448090cd01DD557a474e011E9911e8",
                    "blockHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
                    "blockNumber": null,
                    "transactionIndex": null
                }
            },
            "0x0645E05471943ED32D8C64F6C7671f037aBfb92D": {},
            "0x06D911398a7547c84942Af4B6f75F9F8F8bCeb87": {
                "623": {
                    "nonce": "0x26f",
                    "gasPrice": "0x3b9aca00",
                    "gas": "0x186a0",
                    "to": "0x4c7158E6b8730fe1EdaEB0D7fF606bf2D679fdC3",
                    "value": "0x38d7ea4c68000",
                    "input": "0x",
                    "hash": "0x86a2350362d25cc01dfa6cf44878001839e49c9d6615a8bba3d341e55fbc390e",
                    "from": "0x06D911398a7547c84942Af4B6f75F9F8F8bCeb87",
                    "blockHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
                    "blockNumber": null,
                    "transactionIndex": null
                }
            },
            "0x0ADD669c0C630508a1051C3ff4a23277deB746f1": {
                "1088": {
                    "nonce": "0x440",
                    "gasPrice": "0x3b9aca00",
                    "gas": "0x186a0",
                    "to": "0xF042aCCAe0b77C7B6049fC9f2fa38ce1F136C0E6",
                    "value": "0x38d7ea4c68000",
                    "input": "0x",
                    "hash": "0x99b85bff4e5c47d17eacf01b663e1466751709bad497eec47b17ff5e264aa293",
                    "from": "0x0ADD669c0C630508a1051C3ff4a23277deB746f1",
                    "blockHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
                    "blockNumber": null,
                    "transactionIndex": null
                }
            },
            "0x0BFF440Ba70808F2762a8BF0407aaefD88166385": {},
            "0x0C52fc2061b5380eA6299b84aA45c270ef1772E1": {
                "768": {
                    "nonce": "0x300",
                    "gasPrice": "0x3b9aca00",
                    "gas": "0x186a0",
                    "to": "0x390ad0a70407cAb6082738A2025662c78C632D4e",
                    "value": "0x38d7ea4c68000",
                    "input": "0x",
                    "hash": "0x5399fc54672638e0fa1915db03f25b1ca3f37abb50a021c9aa703df759f5016a",
                    "from": "0x0C52fc2061b5380eA6299b84aA45c270ef1772E1",
                    "blockHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
                    "blockNumber": null,
                    "transactionIndex": null
                }
            },
            "0x0Ca1c856C869a309f0F9731E0d405655D31f040A": {
                "686": {
                    "nonce": "0x2ae",
                    "gasPrice": "0x3b9aca00",
                    "gas": "0x186a0",
                    "to": "0xABaeCdef0A8E01a6A35dF437F2C3ee944Eba27f0",
                    "value": "0x38d7ea4c68000",
                    "input": "0x",
                    "hash": "0xf264d4ff8c3f43fc5abb3c4c1c7cef97b89b3b9aa08c4626e2c126f066affeb2",
                    "from": "0x0Ca1c856C869a309f0F9731E0d405655D31f040A",
                    "blockHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
                    "blockNumber": null,
                    "transactionIndex": null
                }
            },
            "0x0a1C62296F54a987E1bb513FC6308D07Cd50AA9B": {
                "891": {
                    "nonce": "0x37b",
                    "gasPrice": "0x3b9aca00",
                    "gas": "0x186a0",
                    "to": "0x5bd4aa3c8a76a7296Ffb26D295d3133B10AEa440",
                    "value": "0x38d7ea4c68000",
                    "input": "0x",
                    "hash": "0x47245868d03a05b5de479ac778ff957688e4d4b483f66ecc79d7780451793406",
                    "from": "0x0a1C62296F54a987E1bb513FC6308D07Cd50AA9B",
                    "blockHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
                    "blockNumber": null,
                    "transactionIndex": null
                }
            },
            "0x0b2e14d0b4a62e317Df089B44E6d8C1126df4851": {},
            "0x0bF8310C86F38Ba604e9B5b0Bd8072A967117c9c": {},
            "0x119D31f0299478D13C6E2943019ff2F6Ef1d8159": {},

Proposed solution
If you have an idea of how to fix this issue, please write it down here, so we can begin discussing it

Thank you for picking up on this issue - work is in progress.


[Refactor] Remove the namespace vectorized

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[x] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #13805
Problem Summary(Required) ：

The namespace vectorized is not used. So I remove the namespace related codes.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

run starrocks_admit_test

run starrocks_admit_test

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test


Edit symbol when not a recognized contributor greyed out with sometimes-wrong hover message

Description
Reproduce the bug:

Visit a project
Fork it
Go back to the original project
Open a file
Hover over the pencil symbol to edit

Expected behavior:

Editing should work but switches to the fork (or prompts to switch to the fork at least)

Experienced behavior:

Action is greyed out
Hover text says "You must fork this repository to make or propose changes to this file." even though you already did fork the repository

Screenshots

Gitea Version
1.17
Can you reproduce the bug on the Gitea demo site?
Yes
Operating System
Ubuntu GNU/Linux
Browser Version
Firefox 103.0

Did you refresh the page after you forked the repo?

Did you refresh the page after you forked the repo?

Yes, at both Codeberg and at https://try.gitea.io, and with multiple attempts. The behavior is consistent. Anyway, when you first fork, you land at your fork, and you have to go back to the original before you can even be in the situation to see this bug. So, refreshing shouldn't matter, but the issue shows up even after forcing a reload.


Add support for QoS on poses topic

This reduces the latency of motion capture information

Requires https://github.com/IMRCLab/motion_capture_tracking/pull/3


Updated dependencies (Relay 0.8.0)

I've updated some packages, in particular Relay and React/ReactDOM peers.
Relay update breaks the library, I've tested this on my project but (a) I'm not really an expert with Relay and (b) surely my project isn't a torough test for the library.
Anyway, in the new version of Relay (0.8.0), RelayContext is replaced by RelayEnviroment but apparently they are not exactly equivalent.
Indeed this error is raised
Invariant Violation: RelayNetworkLayer: Use `injectNetworkLayer` to configure a network layer.

From this line.

I read the issues regarding Relay 0.8.0, and it seems this PR is not relevant


[blueprint] fixed router naming

Per guides and trial/error, this shouldn't be used here ;-)

Coverage remained the same at 47.656% when pulling 0c1d1b245ed573c1d5880d9a849cb04aebca8eaf on acorncom:patch-3 into e20ac7dba02181f44ea1edc67d35bafbc35ec362 on denali-js:master.


User created dont have grant privilege

mysqldConfig = aMysqldConfig(v5_7_19)
.withCharset(Charset.LATIN1)
.withPort(port)
.withUser(username, password)
.withTimeZone("Europe/London")
.withTimeout(2, TimeUnit.MINUTES)
.withServerVariable("max_connect_errors", 666)
.build();
    embeddedMysql = anEmbeddedMysql(mysqldConfig)
            .addSchema(SchemaConfig.aSchemaConfig(schemaName).build())
            .start();

    logger.info("MySQL is started with config : {}", embeddedMysql.getConfig().toString());

database starts up successfully and scripts can be run.  But the create user don't have GRANT privileges
everything runs except GRANT commands
org.flywaydb.core.internal.dbsupport.FlywaySqlScriptException:
Migration a.sql failed
SQL State  : 42000
Error Code : 1142
Message    : GRANT command denied to user 'dev'@'localhost' for table 'y'

@josepharuja - maybe you could share at least part of sql that is failing.


Switch to react-hot-loader@3

Continuing the discussion in #29:
The current hmre implementation is rather instable and buggy, but something new and shiny ✨ is on the horizon: react-hot-loader seems to be the way to go forward.
Let's see how things are going regarding v3.0.0 and switch as soon as a stable version hits npm.

Beta is just stable enough, I guess...
¯_(ツ)_/¯


EpiOAuth.php fails on PHP 5.5

On PHP v5.5, you get the error message:
Deprecated: curl_setopt(): The usage of the @filename API for file uploading is deprecated. Please use the CURLFile class instead in .../EpiOAuth.php on line 270.
There needs to be a check for PHP v5.5 along the lines of:
if (function_exists('curl_file_create')) {
.... Curlfile() class code
} else {
.... Existing code
}

However, what is the correct code to use?

This is no longer valid in PHP 7 - "curl_setopt(): Disabling safe uploads is no longer supported"
So the whole routine will need to be re-written for PHP v7 - I understand that we need to use something along the lines of new \CURLFile($localFile)

Upon upgrading from PHP 5.4 straight to 5.6, we started getting this error when using the "@" upload syntax:
{"code":189,"message":"Error creating status."}
The fix above didn't help; we must be using the library a bit differently.  I was able to fix the problem by simply adding the following line right before the return statement in EpiOAuth.php's curlInit($url) function:
curl_setopt($ch, CURLOPT_SAFE_UPLOAD, false);
Hope this helps someone else!


Regarding replacing the table mesh with a custom-made model

I wanna look into maybe modeling a different table theme to coincide with a bar I'm maintaining, but I wanted to ask here if it's possible currently without breaking the prefab or its scripts.
I'm asking because:

Another prefab I'm using in the world, MiniGreen's Coffee Set to be exact, loses some functionality when trying to directly edit the contents of the prefab and even warns the user about it, even if you have no intention of directly tampering with the U# scripts or components - hence why I'm hesitant.

It would also be helpful to have a prefab that comes with the textures pre-crunched so I don't have to find out after the fact how much of the build size they take up.

I'm assuming I just replace the mesh in the renderer component and reposition the colliders for each hole but I wanted to know if there was more to it than that.

Hey, it's totally possible: you'll want to keep the table size and pool locations the same, but there are already about four pool table remeshes. You can refer to Juice's CottonFox variant for how extreme you can go.

Hey, it's totally possible: you'll want to keep the table size and hole locations the same, but there are already about four pool table remeshes. You can refer to Juice's CottonFox variant for how extreme you can go.

Dope, will do.


net/frr - BGP weight option and bug fix for disable-connected-check option

Add (advanced) bgp weight attribute and move disable-connected-check to the correct place (both should be set in the generic peer options).
It looked like "community lists" missed a toggle action, added that as well.

To test both disable-connected-check and weight use the following on OPNsense 22.1.8 or 22.4
opnsense-patch -c plugins 8b1facb 6a4631b


[ember-intl] (...) missing from en-us

Recently I've updated ember-intl to its latest version and now, when running the project with ember s, I'm getting a lot of [ember-intl] (...) missing from en-us. My translation file is called en-US and I've checked that the correct name (with US in upper case) is set in the intl.locale in the  beforeModel application route, baseLocale  and locales in config/ember-intl file. Am I missing something?
I've also noticed that all the keys that it says that are missed are from subdirectories. The ones from the root file doesn't appear in the list of "missing". And to make it more strange, although it says that they are missed, all of them are working correctly in the application.

@HenryVonfire any chance you can throw together a sample app that reproduces this?

@jasonmit Sure, here you have. While doing this I've discovered that it wasn't actually ember-intl the one generating the problem but ember-intl-cp-valdiations, should I open an issue in that repository?

Yes please

Ok. I'll close this issue then.

Should be fixed in ember-intl-cp-validations v2.3.1
Thanks


Full-Screen Games don't seem to work with it

While playing full-screen games it looks like it only takes colors of what's behind the game, like the desktop and other things, not the game itself.

Fixed, it was because the toggle "Disable Full Screen Optimizations" was turned on.


Update main from dev #2

Update main from dev to get benefit of dependency updates, documentation updates and new enhancements.

/easycla

Still not fixed.  Closing, will reopen another to test whether the EasyCLA check will pass now that Kris has updated her GitHub and LFX accounts with the same email.


Pypi package does not include templates and theme folders

Hi,
It seems that the package distributed through pypi does not include templates folder which produces an error in mkdocs:
(.venv) mkdocs serve
INFO    -  Building documentation...

[WinError 3] The system cannot find the path specified: 'c:\\users\\my.user\\devel\\rics\\pi_lib\\.venv\\lib\\site-packages\\mkapi\\templates'

I installed it via pip install mkapi (version 0.4.0)
Placing the templates folder in the module path works like a charm.
Also, not sure if needed but the theme folder isn't distributed either.

Thank you for your information. setup.py was wrong. I fixed it. Please update Version 0.4.2 or later.

Awesome,
works great now.
Thanks


A technical doubt

Hello @ethliup!
Thank you for nice work and many congratulations..
In this framework, what ensures that each image should be sharp and it's a deblurred version of input? It might happen set of rendered images(which are blurry), when we average them can still ensure output will be as blurry as input..
Can you please clarify on this.
Thank you
Gopi

Thank you for your question.
The answer is geometric constraints.
To clarify:
The geometric constraints of this 3D scene should be satisfied to ensure the consistency of rendering from different camera poses (e.g. some rays from front, some rays from left side, some rays from right side). If all the rendered images (rays) are blurry, the training loss will be very high. You can find more details about this in the BADNeRF and NeRF papers.
In our BeNeRF, the sharpness of the scene is further ensured by the event stream. With RGB loss only, it would be challenging to construct a 3D scene from a very short trajectory (the geometric constraint is not strong enough for optimization, so what you described may happen). However, the additional information provided by the event stream makes it possible to build the sharp 3D scene (i.e. the event loss mentioned in our paper).
If you have any further questions, please don’t hesitate to reach out.

Thank you so much for your detailed explanation...
I am trying with similar framework with Gaussian Splatting, but my output(each image) is not clear(deblurred), each image is having artifacts but the blur image(rendered blur image) when I sum up render ones is giving input blur image, even with PSNR 60dB or so.. this I tried with 5 virtual cameras. When I tried to increase no. of virtual cameras, virtual cameras are drifting in zigzag fashion. For pose optimization, I am not using B-splines, is that the issue for drifting of camera locations? Also, for some reason, event loss is contributing not much, if I keep factor 2 for event loss, framework is not converging at all. Also, if I use only event loss, output is fully blank even with BeNeRF..
Help and suggestions in this regard are highly appreciated.
Thank you
Gopi

Thank you so much for your detailed explanation...
I am trying a similar framework with Gaussian Splatting, but my output(each image) is not clear(deblurred), each image is having artifacts but the blur image(rendered blur image) when I sum up render ones is giving input blur image, even with PSNR 60dB or so.. this I tried with 5 virtual cameras. When I tried to increase no. of virtual cameras, virtual cameras are drifting in zigzag fashion. For pose optimization, I am not using B-splines, is that the issue for drifting of camera locations? Also, for some reason, event loss is contributing not much, if I keep factor 2 for event loss, framework is not converging at all. Also, if I use only event loss, output is fully blank even with BeNeRF..
Help and suggestions in this regard are highly appreciated.
Thank you Gopi

You may check out BAD-Gaussians if you train with multiple images without event loss.
https://github.com/WU-CVGL/BAD-Gaussians
For our BeNeRF, I think it should undoubtedly work if you only change from NeRF to Gaussians.

Can we shortly meet online when you are available? It will be very helpful.. I am working on this problem, but struct with this for quite a time.  I guess, you will be very busy, but if you can spare sometime, it will be really great..

@GopiRajuMatta
Thank you for reaching out! I'd be happy to set up an online meeting to discuss this further.
Could you please let me know which software you prefer to use for the meeting (e.g., Zoom, Google Meet, etc.) and suggest a few dates and times that work for you?
The author of BAD-Gaussian will also be joining us, so we’ll try to accommodate everyone’s schedules.
Looking forward to helping you with this!

Thank you so much for your positive reply!
Google meet should be fine..
Dates and times:  13/11/24(Wednesday), 9am to 6pm(IST)
14/11/24(Thursday), 9am to 3pm(IST)
15/11/24(Friday), 9am to 2pm(IST)
Thank you once again..

Thank you so much for your positive reply!
Google meet should be fine.. Dates and times: 13/11/24(Wednesday), 9am to 6pm(IST) 14/11/24(Thursday), 9am to 3pm(IST) 15/11/24(Friday), 9am to 2pm(IST)
Thank you once again..

Cool. Can you tell me you work email address? I'll send you the meeting ID and time later.


Fixing not defined error and adjusting headers to http standards

Nginx always deleted the user_id header while passing it.
Seems that user_id is not a valid header,
https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/?highlight=disappearing http headers#missing-disappearing-http-headers

According to the link you attached, headers with underscorce are valid too.

Thanks for bringing this PR, and I think I didn't take account for this kind of issue on queries in get endpoints.
In my opinion, what if we just put the ID in a query string, and just put auth in headers. I believe this would ensure compatibility in most systems

I agree with that.

Yeah that's my bad, they are valid, but both nginx and Apache will drop the headers. Anyway, I agree with the querrys version, I already wondered why you would do it over headers.

That settles it, I'll update the library to fix those issue probably this night to tomorrow afternoon.
You will receive an update on my Server once the update is live