NullReference Exception under Android API 25

Hi,
the current version does not work with Android. I always get a NullReferenceException.
Target API is 25.
Test project can be found here: RangeSliderTest

I think the NullReferenceException is due to ThumbImage being null RangeSliderControl.cs line 328
_thumbHalfWidth = 0.5f * ThumbImage.Width;

ThumbImage was set by the line
ThumbImage = BitmapFactory.DecodeResource(Resources, thumbNormal);

@timdinhdotcom Any ideas why android isn't loading the image?

@j-sauer is finding weird issues. seek_thumb_normal.png and seek_thumb_pressed.png don't load. seek_thumb_disabled does seem to load but looks like a faint rectangle rather than a circle.

Here is my work around
Add this method
private Bitmap BitmapFromResourceId(int id)
{
    using (var stream = Resources.OpenRawResource(id))
    {
        return BitmapFactory.DecodeStream(stream);
    }
}

change this block
            if (ThumbImage == null)
            {
                ThumbImage = BitmapFactory.DecodeResource(Resources, thumbNormal);
            }
            if (ThumbPressedImage == null)
            {
                ThumbPressedImage = BitmapFactory.DecodeResource(Resources, thumbPressed);
            }
            if (ThumbDisabledImage == null)
            {
                ThumbDisabledImage = BitmapFactory.DecodeResource(Resources, thumbDisabled);
            }

to
            if (ThumbImage == null)
            {
                ThumbImage = BitmapFromResourceId(thumbNormal);
            }
            if (ThumbPressedImage == null)
            {
                ThumbPressedImage = BitmapFromResourceId(thumbPressed);
            }
            if (ThumbDisabledImage == null)
            {
                ThumbDisabledImage = BitmapFromResourceId(thumbDisabled);
            }

@timdinhdotcom OK great. @j-sauer and I are working on doing this with circle drawables, bypassing resources. If our approach is going well we can take that one (which is resolution independent), otherwise we can use yours. We can do the PR.

Thanks @timdinhdotcom. But your changes don't fix @j-sauer issue.

Thanks @charlesroddie How did you fix it? I've been trying to fix it for a while but didn't fix it.

We are trying to bypass using resources by putting drawing circles in code instead of using bitmaps. (Could use xml too but code to be completely safe.) All of the relevant resources (seek_thumb_disabled, _normal, and _pressed) are just two or three circles. Pretty sure that will work.

Fixed in 0.7.30
Thanks a lot @charlesroddie


Unexpected "divide by zero" warning with numba.vectorize and np.log

The behavior of np.log function under numba.vectorize is strange to me. It throws unexpected warning but gives the correct result.
Here is the testing code.
import numpy as np
import numba

def slog(a):
    if a > 0:
        return np.log(a)
    return 0

print(np.__version__)
print(numba.__version__)
assert numba.vectorize(slog)(0) == 0
with np.errstate(divide="raise"):
    slog(0)
    numba.jit(slog)(0)
    numba.vectorize(slog)(0)

The output is
numpy version 1.19.4
numba version 0.52.0
h.py:11: RuntimeWarning: divide by zero encountered in slog
  assert numba.vectorize(slog)(0) == 0
Traceback (most recent call last):
  File "h.py", line 15, in <module>
    numba.vectorize(slog)(0)
FloatingPointError: divide by zero encountered in slog

Thanks for the report. I think that this is the same as this: https://github.com/numba/numba/issues/4793#issuecomment-622323686
Looking at the LLVM IR from env var NUMBA_DEBUG=1, it has:
  %.94 = load i64, i64* %.93, align 8 ; Load variable 'a' into %.94
  %.13.i2 = icmp sgt i64 %.94, 0 ; signed integer "greater than" comparison, between 'a' and 0, store result to %.13.i2
  %.51.i4 = sitofp i64 %.94 to double ; cast 'a' to a 'double' type and store in %.51.i4
  %.52.i5 = tail call double @llvm.log.f64(double %.51.i4) #2 ; Call `log` on variable %.51.i4 and store into %.52.i5
  %34 = bitcast double %.52.i5 to i64 ; Cast the result of the log to an int64 and store in %34.
  %35 = select i1 %.13.i2, i64 %34, i64 0 ; If %.13.i2 is true store the result of the log call, if false store 0.

which is doing the same as in #4793 (I've added descriptions after the ; on each line). Basically, LLVM elects to call the log function speculatively.

Yes, you are right. So is there any way to close this warning? I know I could use numpy.seterr, but am not sure it would give the best performance.

@szsdk I believe the workaround from https://github.com/numba/numba/issues/4793#issuecomment-623296850 is the only currently known one. If you are concerened about performance I would suggest benchmarking it to determine the impact this has.

Closing this issue as it seems to be resolved. If this is not the case please re-open with a comment about any item that appears to be unresolved. Many thanks.


Shrine.logger.level value is not herited

A configuration problem similar to the now fixed https://github.com/janko-m/shrine/issues/57 .
Documentation says:

Logging is by default disabled in tests, but you can enable it by setting Shrine.logger.level = Logger::INFO.

Based on this, I tried to change log level:
Shrine.plugin :logging

class SomeUploader < Shrine; end

Shrine.logger.level = Logger::WARN
#=> 2
SomeUploader.logger.level
#=> 1

What happen here if I understand correctly, is that when the :logger option is not specified, each uploader class end up with a different @logger instance variable (cf. here and here ).
I expected Shrine.logger.level to be shared accross all uploaders. But as is, it needs to be set for each class.
I'm willing to make a pull request, but I'm not sure of the best solution:

change @logger object to be uniq accross all uploaders ?
keep one logger by class, but add an option to choose logger level at plugin initialisation ?

Thanks for your time, this gem is awesome.

@AntoineBecquet
Thank you for reporting this and we're glad you're liking the gem. I really appreciate you taking the time to present the case in such a clear and concise manner and dig into the issue.
I've confirmed this behavior even when you configure Shrine.logger.level before subclassing, but I'll have to defer the final design decision to @janko-m as he might have reasons for implementing it in this way. We'd also need to consider the impact, if any, this might have on existing apps. My opinion would be to have your second solution but it doesn't have to be only at plugin initialization, it just needs to be configured before subclassing. The subclass logger should inherit all options from Shrine class on subclass creation but can then be overridden individually in any of the subclasses.
@janko-m
I've confirmed this behavior even when you set the main Shrine.logger.level before creating a subclass. The subclass does not inherit Shrine configuration. Please advise as to what behavior you'd like it to be and whether we'd need to consider any impact to existing applications.

The Shrine subclasses should definitely inherit the logger from the superclass. In other words, this should work:
Shrine.plugin :logging
Shrine.logger.level = Logger::INFO

class ImageUploader < Shrine
end
ImageUploader.logger.level #=> Logger::INFO

I wouldn't like the logger object to be shared amongst subclasses, as then we don't have inheritance. In other words, I think the behaviour should stay the following:
Shrine.plugin :logging

class ImageUploader < Shrine
end

Shrine.logger.level = Logger::INFO
ImageUploader.logger.level #=> Logger::DEBUG (the default)


Removed extra 'is' in line 9

I removed the extra 'is' in line 9 which I believe is a typographical error.

Thanks @Boye95!

@Boye95 Would you mind signing the CLA agreement so I can merge? Thanks.

@Boye95 Would you mind signing the CLA agreement so I can merge? Thanks.

I have done that. It might take some minutes for it to reflect here.


Fix command

@bors r+ Thank you!!

:pushpin: Commit ffb3e15 has been approved by brson

:hourglass: Testing commit ffb3e15 with merge 01c954e...

:broken_heart: Test failed - status-appveyor

@bors retry

:hourglass: Testing commit ffb3e15 with merge 2ee9cf1...

:sunny: Test successful - status-appveyor, status-travis
Approved by: brson
Pushing 2ee9cf1d392cc9bd4f523642c78bf4044852613a to master...


add link to css doc

please link the an external css document.

All done and commited!

just the facts ma'am
| topping | courier |
|--------|--------|
| topping| Cell |
| Cell | ma|
| Cell | Cell |
| Da | Cell |


release new version?

Hi, it seems that the latest changes from #109 are not yet released, could you release it in hex please?
thanks

Released mogrify version 0.9.2


chore: fix merge queue

Are these code changes actually needed for the queue fix?

@djc in theory no...but I think because merge queue wasn't running something snuck in that I just merged. So this should enable CI for the merge queue and also fix the issues on master.


FullStackHero .NET 8 Starter Kit Beta Available!

Discussed in https://github.com/fullstackhero/dotnet-starter-kit/discussions/966

Originally posted by iammukeshm July 23, 2024
The repository consists of 3 Projects.

Aspire Dashboard: Helps ease local development experience by visualizing metrics, logs, open telemetry data, and stats. Grafana / Prometheus integration also comes out of the box. Set the Aspire project as the default and run the application. Both WebAPI and Blazor would boot up. You will need Docker running on your machine since containers of Prometheus and Grafana would spin up too.

.NET 8 Web API: Follows Modular Architecture, with clean code separation. It is integrated with EF Core 8, PostgreSQL, Redis, FluentValidation, Serilog, Hangfire, MediatR, and Minimal APIs. It is truly an awesome development experience. Multi-tenancy is the USP of this project.

Blazor WASM Standalone: MudBlazor flavored Client Application that talks to the JWT-secured Web API.

My focus was not only on building an application, but also engineering a solution that exhibits even wider SDLC practices, right from Docker, Docker Compose, Terraform, CICD with GitHub Actions, and Performance & Metrics with Aspire.
FullStackHero is now available for testing purposes. I would consider the current version as Beta. Most of the Razor Pages are added. A few of the User Management Pages are yet to be added.
Quick Start Guide is available in the README.md file of this repository.
Let me know your feedback. Thanks!

what is this issue for? @1hossin6494


chore(main): release 0.9.2

:robot: I have created a release beep boop
0.9.2 (2024-12-16)
Bug Fixes

bump marked from 15.0.3 to 15.0.4 (#637) (1af7ff1)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.9.2
:sunflower:


Disable autocomplete for input box

It's really annoying when you're trying to search through history and you scroll through autocomplete options instead.
It's as simple (at least in chrome) as setting the autocomplete attribute of #inputbox to off. This attribute is supported in HTML5, so it's mostly supported by modern browsers. I don't know if Safari is still an exception though, I'm not a web dev.
Also, this is an awesome project.

Which browser does this occur on for you? On both Firefox and Chrome everything works as expected for me unless I'm misunderstanding the issue. If there's some setting I need to enable let me know and I can give it another shot.
Alternatively if you make your suggested change yourself and this fixes things, feel free to make a pull request and I can merge it in if it doesn't change any other behaviour.
Thanks!

Hey, kinda late but whatever. It's happening to me on Chrome, I'll send a PR in just a minute.

Merged your pull request #7  -- thanks!


[CG, BUG] We need to update Header styling for all modals that are showing in the app

The Headers are not centralized on all modals!
Examples:

verified on prod


Memory map queries do not enforce correct alignment

Both rustc and UEFI expect pointers to be correctly aligned for the target type. However, we do not enforce this when querying a memory map, as we take an unrestricted &mut [u8], cast it to *mut MemoryDescriptor, and pass it down to UEFI. This is undefined behavior waiting to happen.
Since type alignments are small and bytes are cheap in the archs targeted by UEFI, the right thing to do in this case is probably to skip the first few bytes of the input slice in order to reach a part which is properly aligned, and do the write there.
I solved a very similar problem as part of #69. As I expect such "take a buffer as input and write into it" patterns to be common in UEFI's low-level environment, it might be worthwhile to take the alignment correction code that I wrote there and generalize it.
Here is a tentative API mockup:
/// Best API most of the time
fn realign_for<T: Sized>(storage: &mut [u8]) -> &mut [u8];

/// Lower-level API that is sometimes needed because mem::align_of does not support DSTs
fn realign(storage: &mut [u8], alignment: usize) -> &mut [u8];

Better DST support could be provided with a custom derive, that computes the alignment automatically instead of having people compute it by hand, and errors out on dyn Trait. But I would only do this at a later point in uefi-rs' evolution, if we encounter the use case sufficiently often to justify the significant code complexity of that infrastructure.

I would rather have a development-time mechanism which warns the developer that they somehow passed an unaligned buffer, yes.
The realignment functions could be useful as utilities for the users of the crate, but it feels like doing it silently is not beneficial.

I would rather have a development-time mechanism which warns the developer that they somehow passed an unaligned buffer, yes.
The realignment functions could be useful as utilities for the users of the crate, but it feels like doing it silently is not beneficial.

Just to be clear, this calls for more attention than a development-time warning. Passing an unaligned buffer to UEFI or using an unaligned reference to Rust is undefined behavior and like any UB it is more dangerous in release mode than in debug mode. So even in release mode, we must either fix it ourselves, panic when we encounter it, or mark functions that may take unaligned buffers as unsafe.

Shall we settle on documenting that the input slice must be well-aligned and panicking at runtime if it isn't?

It does seem reasonable to me. It should be the responsibility of the caller to handle memory allocation and alignment.


--scripts-version not working with forked react-scripts

According to @gaearon's tweet  https://twitter.com/dan_abramov/status/774888111927091200
I forked react-scripts to another package named feeble-scripts and tried running create-react-app myapp --scripts-version feeble-scripts, because CRA reads react-scripts's package.json in https://github.com/facebookincubator/create-react-app/blob/master/global-cli/index.js#L149-L155, so the command fails end with Error: Cannot find module '/path/to/myapp/node_modules/react-scripts/package.json'.

Apparently we broke this when we added the Node version check. Would you like to send a PR fixing this?


goctl api format don't support import other api declare type

Describe the bug
goctl api format don't support import other api declare type
To Reproduce
Steps to reproduce the behavior, if applicable:

The code is

a.api
type A {}

b.api
import "a.api"
type B {
Data []A
}

The error is
can not found declaration 'A' in context

goctl 1.3.2

format b.api will report errors.
generate go code from b.api, a.api should also be formatted.


New metrics structure completed.

New metrics structure allows user to create and define params for metrics as desired. Current metric classes in metrics/ can be extended or completely new custom metric can be defined inheriting jury.metrics.Metric.

@devrimcavusoglu why is this test failing? https://github.com/obss/jury/pull/35/checks#step:10:19

@devrimcavusoglu why is this test failing? https://github.com/obss/jury/pull/35/checks#step:10:19

Interesting. All checks seems passing for me, is it any spesific check or for all checks at same step ?

@devrimcavusoglu all checks fail at tests/jury/test_jury.py::test_evaluate_concurrent FAILED                 [ 60%]


Marketplace package is not up to date

As you have merged my changes, I unpublished my version from the marketplace. For any future additions I make to this, I'll make a pull request for you.
I see that the package on the marketplace is not up to date (It doesn't have mine or @owt5008137 changes). Could you publish a new version? Thanks!

Thanks a lot for your changes to the package. I published the new version to the marketplace.


version 4.1.4 remove passing params in router.push. What is the alternative?

What problem does this feature solve?
on the changelog page here -> https://github.com/vuejs/router/blob/main/packages/router/CHANGELOG.md
it explains that passing params while doing a route push is an anti pattern and it was removed.
Is there an alternative?
That link explains that i only have 2.

put the data in query
or as an actual param

I cannot use option #1 as it will change the url to have params. This is something that isnt desirable for my app.
And as for option #2, it looks like i can only add it as actual params in boolean mode as shown here -> https://router.vuejs.org/guide/essentials/passing-props.html#boolean-mode
I assume that this prop values for boolean mode is setup in the router.js file?  If this is the case, then I cannot use this because when it there file, i have no context of what is actually being passed.  By this i mean, the way i currently use it, when i do a router.push, i'll be inside some template file that knows what data to add to the params for the next view.  But in the router.js file, i have no context for what to pass.
What does the proposed API look like?
can the propose API look like how its always been?
router.push({ name: 'somewhere', params: { oops: 'gets removed' }})

那现在不需要显示在路径当中的参数应该怎么传递？

by setting props: true in your router.js file

No, it's useless
------------------ 原始邮件 ------------------
发件人: @.>;
发送时间: 2022年8月26日(星期五) 中午11:38
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [vuejs/router] version 4.1.4 remove passing params in router.push. What is the alternative? (Issue #1531)
by setting props: true in your router.js file
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Also have this problem. Using pinia or history api state just feel less intuitive than passing params directly.

@vincent-lu
you
can
pass
params
directly
by going to your router and setting props to true.
import { createRouter, createWebHistory } from 'vue-router'

const router = createRouter({
  history: createWebHistory(import.meta.env.BASE_URL),
  routes: [
    {
      path: '/',
      name: 'index',
      component: () => import('../views/index.vue'),
      props: true               <----------------  LOOK AT THIS
    },
    ```

    Now pass stuff in your params like you did before, and it will end up in the props of the component


prefix

https://github.com/g-makarov/vite-plugin-svg-spritemap/blob/main/src/utils.ts#L44
I suggest you reconsider this way.
if the prefix is not needed, it would be good to get rid of -.
I suggest - make it part of a prefix that can be removed

@nepster-web hi, that's a good point


Wrong filenames

Seems that no filenames are generated. Only one file named files.md and every time it is overwritten by the newest one.

Is fixed with 2edaa97.


[ja] Fix broken links in persistent-volumes

This PR fixes a broken link in the Japanese persistent-volumes document.

/lgtm
Thank you for creating this PR!
The Update looks good for me!
But the CI for Netlify(a build system for generating webpage) said an error, this looks the error on Netlify side.
Could you empty-commit by doing following to retrigger the build?
git commit --amend --no-edit
git push -f

Thank you for your review!
I built again and the error on the Netlify side is fixed!

Thank you for quick response!

/assign @nasa9084
Could you review this?


Add cr overrides e2e tests

Fix #45
Signed-off-by: ruromero<EMAIL_ADDRESS>

@ruromero I created #59. No need to make changes in this PR as a result of it. Please rebase when you get a chance and we can merge this as-is and address any other things in subsequent PRs.

@font if you want to merge #59 before this one I'll rebase or I can do the refactoring in the next PR


Version constraint failed

Because hooks_riverpod 0.14.0+4 depends on flutter_hooks ^0.17.0 and no versions of hooks_riverpod match >0.14.0+4 <0.15.0, hooks_riverpod ^0.14.0+4 requires flutter_hooks ^0.17.0.
So, because fstore depends on both flutter_hooks ^0.18.0 and hooks_riverpod ^0.14.0+4, version solving failed.
pub get failed (1; So, because fstore depends on both flutter_hooks ^0.18.0 and hooks_riverpod ^0.14.0+4, version solving failed.)

flutter_hooks upgraded to 0.18
  flutter_hooks: ^0.18.0
  hooks_riverpod: ^0.14.0+4

Fixed in 1.0.0-dev.4


Announcement: Introducing the RealSense D435f stereo depth camera

Hi everyone,
A new RealSense D435f camera has been added to the RealSense 400 Series range of stereo depth camera products and is now available for purchase from the official online RealSense Store.
https://store.intelrealsense.com/buy-intel-realsense-depth-camera-d435f.html
The D435f adds an IR pass filter to the pair of depth sensors.  Full details of this new camera model are available in the data sheet document for the 400 Series.
https://dev.intelrealsense.com/docs/intel-realsense-d400-series-product-family-datasheet
The data sheet provides the following information about the new filter:

D435f = D435 with 750nm near-infrared filter (CLAREX® NIR-75N) applied to cover glass, with holes over projector and RGB sensor openings.  Filter transmits near-infrared light and absorbs visible light.  Filter’s thickness = 0.5 mm.

Pages 64 and 65 of the data sheet provides a feature comparison between the D435f and the rest of the 400 Series range, a comparison of D435 and D435f, and a chart of the filter's optical properties.
Further information about the D435f is available at the Intel Newsroom press release at the link below.
https://www.intel.com/content/www/us/en/newsroom/news/intel-realsense-d435f-adds-infrared-pass-filters.html

Hi, I wonder if the SDK of D435f is available now or we can still take D435f as a D435 and use the current SDK.

Hi @Jing-lun New models have support integrated into the SDK before release for testing purposes.  I should have a D435f in several days from the time of writing this if you would prefer to wait for me to perform testing and share the results.

Hi @Jing-lun New RealSense camera models typically have support already integrated into the SDK before the date of their release on sale. I should have a D435f in several days from the time of writing this if you would prefer to wait for me to perform testing and share the results.

Sounds great, many thanks!

@MartyG-RealSense
will d435f work with AGX Jetson devkit without gsml?
Thanks

D435f is a D435 USB camera with an added light filter on the sensors and is detected by the RealSense SDK as a D435.

@MartyG-RealSense we need d457
could you point out if intel provides a de-serializer that can be used with d457 with intel desktop or nuc, please?

@MartyG-RealSense
the intel store de serializer connects to Jetson AGX Xavier by which port? The image only shows the top of the de-serializer
Thanks

@AndreV84  I do not have further images of the Intel de-serializer board and details of how it is connected to the Xavier, unfortunately.

@MartyG-RealSense zendesk yet only suggested not to use d457 but use d455 instead.
reference driver I am still requiesting responseless from them


Add Subset Sum or Equal Partion sum Problem in Python/dynamic Programming folder

OK

ok I will send another request


add: amdgpu-dkms-deb

Added this to fix aomp-deb UBUNTUINSTALL.

Check the CI. It seems to be showing some issues.

Seems like a CI issue, can you verify this works on your machine?

I've figured out that aomp-deb does not need amdgpu-dkms-deb, instead the issue was aomp: https://github.com/ROCm-Developer-Tools/aomp/issues/323. So I'm going to remove firmware deb and fix aomp-deb later.


feat: Support for Signin Error; Parameterizing Username label

🚨 Proposed changes

Please review the guidelines for contributing to this repository.

This feature allows the user to receive feedback on sign-in failures. This allows the user to display their own custom error messages when signing in fails.
⚙ Types of changes
What types of changes does your code introduce? Put an x in the boxes that apply

[X] New feature (non-breaking change which adds functionality)
[X] Bugfix (non-breaking change which fixes an issue)
[X] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] Documentation Update (if none of the other choices apply)
[X] Refactor

Hi @SaachiNayyer, thank you for the PR :smile: is It ready for review?

Hi @SaachiNayyer, thank you for the PR 😄 is It ready for review?

Hi antoniomuso
😄 its ready for review.


Implement procref instruction

As discussed in https://github.com/0xPolygonMiden/miden-vm/issues/728#issuecomment-1732344823, it would be good to provide an instruction which would put hash of a given procedure onto the stack. This instruction could be procref.NAME where name is the label of the procedure. For example:
use.std::math::u64

begin
    procref.u64::add
end

To support this, we'd need to add a new variant to the Instruction enum which could look something like ProcRef(ProcedureId). When this instruction is processed by the assembler, we'd need to convert it into four PUSH operations to push the actual procedure MAST root onto the stack.

Closed by #1113.


Fix issues on MacOS and enable running them on CI

The backend loader now looks for .dylib on MacOS.
MacOS gets its own link line with OpenMP and Boost libs detected via CMake and fixes rpath argument.
The unsigned long issue with sycl::vec as on Windows has been taken care of.
Enables building and running tests on MacOS.
This fixes #437 and fixes #534.

@hipsycl-ci-bot test this please!


Incomplete test: API attributes

Context: production readiness proposal and plan
The feature “API attributes” is identified as incomplete test coverage. As a measure to reach Istio production quality in 0.3, this issue is opened to track the progress of providing sufficient test coverage for the feature in question.
This issue is initially assigned to the working group leads.
Recommendations:

Come up with a test plan for how the feature should be tested. Identify and document (in this issue, or a separate document this issue will link to) test cases and whether each will be covered by an integration test (with some level of mocking and/or starting up selected components in test environment), or end to end test (aka system test, which brings up the whole Istio to exercise the feature; currently live in the istio/istio repo).
If you expect the test plan is complex and controversial, consider having it formally reviewed.
State an ETA in the issue, and assign this to a developer who will execute the test plan.
Execute the test plan as the highest priority for 0.3.
For any bug or defect identified by the new test cases, file a new issue and link it from this one.
Close this issue only when the test plan is completely executed, and all additional issues identified in step 3 are fixed.

If you see a risk of not fixing this issue by end of 0.3, please contact<EMAIL_ADDRESS>as soon as possible. We will also periodically ping the issue for update.

100% coverage in pkg/attribute so I think we're covered.

I think this is about API management attributes production, right?
On Wed, Mar 21, 2018 at 9:39 AM Martin Taillefer<EMAIL_ADDRESS>wrote:

100% coverage in pkg/attribute so I think we're covered.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/1091#issuecomment-375009938, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJGIxijmIeQoy7bkqCyb4DRNEB4xkdVTks5tgoIqgaJpZM4P0yIp
.

There was no such thing as API management in october, so I wouldn't think so.


Cant hit headshots with backtrack enabled

Anyone else notice that you almost cant hit a headshot while backtrack is enabled?
If anyone got a fix for this, please share :)

that dosent happen to me did u did any changes to backtrack?

Im using default source, no changes.

maybe the other player uses legit aa

yep having same issues

maybe the other player uses legit aa

i dont think bots playing on my local server are using legit aa >_>

LMFAO
try to make the aimbot aim at the BT not he player
or any tick between them

LMFAO
try to make the aimbot aim at the BT not he player
or any tick between them

LMFAO are you retarded? How about you stop changing the subject of the issue. And for the record, I am not using aimbot, I AM ONLY TALKING ABOUT BACKTRACK.

bump


Hourly Schedules Not Working

I'd like to reference https://github.com/airbnb/airflow/issues/353
Since I cannot re-open that ticket, I'd like to follow up here. I tried to move my DAG to hourly, a critical requirement for our business and an important milestone for the GA of a new product. Unfortunately, when I changed the schedule interval to 3600, I noticed that the ds parameters were not resolving beyond the day.

{{ execution_date }} is a python datetime.datetime object, you can format it however you want. {{ execution_date.isoformat() }} or more intricate formating using the strftime method

Oh and since 1.6.0 you can set schedule_interval='@hourly'

nice!

The upgrade to 1.6.0 and hourly is not actually working. Airflow is not honoring my DAG specified.


iOS  App Crash with Stub_CallToRuntime

Steps to Reproduce

1、I could not reproduce the crash.
Expected results:
won't crash
Actual results:
Crashed: io.flutter.1.ui
0  libsystem_kernel.dylib         0x6bbc __pthread_kill + 8
1  libsystem_pthread.dylib        0xd854 pthread_kill + 208
2  libsystem_c.dylib              0x1f6ac abort + 124
3  Flutter                        0x566a78 (缺少 UUID b5f419596300357c85f161f5e6e0920d)
4  Flutter                        0x651c20 (缺少 UUID b5f419596300357c85f161f5e6e0920d)
5  Flutter                        0x664aa8 (缺少 UUID b5f419596300357c85f161f5e6e0920d)
6  Flutter                        0x6576e4 (缺少 UUID b5f419596300357c85f161f5e6e0920d)
7  Flutter                        0x5d37dc (缺少 UUID b5f419596300357c85f161f5e6e0920d)
8  Flutter                        0x6382e0 (缺少 UUID b5f419596300357c85f161f5e6e0920d)
9  App                            0x7cb8 Stub_CallToRuntime + 92
10 App                            0x7e74 Stub_AllocateObjectSlow + 48
11 App                            0x58118 Offset.operator_add_1438 + 152
12 App                            0xb4c1fc RenderShiftedBox.paint_39377 + 140
13 App                            0x72e18 RenderObject._paintWithContext_1965 + 100
14 App                            0x773a0 PaintingContext.paintChild_2021 + 132
15 App                            0xb4bd10 RenderProxyBoxoperator_andRenderBoxoperator_andRenderObjectWithChildMixinoperator_andRenderProxyBoxMixin.paint_39372 + 64
16 App                            0x72e18 RenderObject._paintWithContext_1965 + 100
17 App                            0x773a0 PaintingContext.paintChild_2021 + 132
18 App                            0xb4bd10 RenderProxyBoxoperator_andRenderBoxoperator_andRenderObjectWithChildMixinoperator_andRenderProxyBoxMixin.paint_39372 + 64
19 App                            0x72e18 RenderObject._paintWithContext_1965 + 100
20 App                            0x773a0 PaintingContext.paintChild_2021 + 132
21 App                            0xb4bd10 RenderProxyBoxoperator_andRenderBoxoperator_andRenderObjectWithChildMixinoperator_andRenderProxyBoxMixin.paint_39372 + 64
22 App                            0x72e18 RenderObject._paintWithContext_1965 + 100
23 App                            0x773a0 PaintingContext.paintChild_2021 + 132
24 App                            0xb4bd10 RenderProxyBoxoperator_andRenderBoxoperator_andRenderObjectWithChildMixinoperator_andRenderProxyBoxMixin.paint_39372 + 64
25 App                            0x72e18 RenderObject._paintWithContext_1965 + 100
26 App                            0x72d88 PaintingContext._repaintCompositedChild_1964 + 280
27 App                            0x72c54 PaintingContext.repaintCompositedChild_1963 + 36
28 App                            0x72ba0 PaintingContext._compositeChild_1962 + 44
29 App                            0x77380 PaintingContext.paintChild_2021 + 100
30 App                            0xb4bd10 RenderProxyBoxoperator_andRenderBoxoperator_andRenderObjectWithChildMixinoperator_andRenderProxyBoxMixin.paint_39372 + 64
31 App                            0x72e18 RenderObject._paintWithContext_1965 + 100
32 App                            0xb5385c RenderSliverMultiBoxAdaptor.paint_39425 + 1600
33 App                            0x72e18 RenderObject._paintWithContext_1965 + 100
34 App                            0x773a0 PaintingContext.paintChild_2021 + 132
35 App                            0xb531f4 RenderSliverEdgeInsetsPadding.paint_39424 + 184
36 App                            0x72e18 RenderObject._paintWithContext_1965 + 100
37 App                            0x5b8d18 RenderViewportBase._paintContents_17281 + 1276
38 App                            0x5b8f2c RenderViewportBase._paintContents_17284 + 52
39 App                            0x72a08 PaintingContext.pushLayer_1956 + 304
40 App                            0x77f7c PaintingContext.pushClipRect_2032 + 488
41 App                            0xb51474 RenderViewportBase.paint_39412 + 280
42 App                            0x72e18 RenderObject._paintWithContext_1965 + 100
43 App                            0x72d88 PaintingContext._repaintCompositedChild_1964 + 280
44 App                            0x9d9c80 PipelineOwner.flushPaint_32487 + 504
45 App                            0x9d8920 WidgetsFlutterBindingoperator_andBindingBaseoperator_andGestureBindingoperator_andSchedulerBindingoperator_andServicesBindingoperator_andPaintingBindingoperator_andSemanticsBindingoperator_andRendererBinding.drawFrame_32475 + 100
46 App                            0x9da65c WidgetsFlutterBindingoperator_andBindingBaseoperator_andGestureBindingoperator_andSchedulerBindingoperator_andServicesBindingoperator_andPaintingBindingoperator_andSemanticsBindingoperator_andRendererBindingoperator_andWidgetsBinding.drawFrame_32497 + 180
47 App                            0x9da57c WidgetsFlutterBindingoperator_andBindingBaseoperator_andGestureBindingoperator_andSchedulerBindingoperator_andServicesBindingoperator_andPaintingBindingoperator_andSemanticsBindingoperator_andRendererBinding._handlePersistentFrameCallback_32496 + 32
48 App                            0x9daba4 WidgetsFlutterBindingoperator_andBindingBaseoperator_andGestureBindingoperator_andSchedulerBindingoperator_andServicesBindingoperator_andPaintingBindingoperator_andSemanticsBindingoperator_andRendererBinding._handlePersistentFrameCallback_32503 + 44
49 App                            0x9b65c WidgetsFlutterBindingoperator_andBindingBaseoperator_andGestureBindingoperator_andSchedulerBinding._invokeFrameCallback_2576 + 60
50 App                            0x9b5a4 WidgetsFlutterBindingoperator_andBindingBaseoperator_andGestureBindingoperator_andSchedulerBinding.handleDrawFrame_2575 + 668
51 App                            0x9b2e8 WidgetsFlutterBindingoperator_andBindingBaseoperator_andGestureBindingoperator_andSchedulerBinding._handleDrawFrame_2574 + 280
52 App                            0x9b1b8 WidgetsFlutterBindingoperator_andBindingBaseoperator_andGestureBindingoperator_andSchedulerBinding._handleDrawFrame_2573 + 40
53 App                            0xa0dd20 rootRun_33379 + 208
54 App                            0xa0dc38 rootRun_33378 + 124
55 App                            0xef3934 CustomZone.run_53409 + 160
56 App                            0xef5400 CustomZone.runGuarded_53444 + 52
57 App                            0x7ff08 invoke_2119 + 156
58 App                            0x86010 PlatformDispatcher._drawFrame_2219 + 40
59 App                            0xa11060 drawFrame_33455 + 40
60 App                            0xa11098 drawFrame_33456 + 24
61 App                            0x78f0 Stub_InvokeDartCode + 220
62 Flutter                        0x59eb60 (缺少 UUID b5f419596300357c85f161f5e6e0920d)
63 Flutter                        0x59f6f0 (缺少 UUID b5f419596300357c85f161f5e6e0920d)
64 Flutter                        0x69ae00 (缺少 UUID b5f419596300357c85f161f5e6e0920d)
65 Flutter                        0x4e767c (缺少 UUID b5f419596300357c85f161f5e6e0920d)
66 Flutter                        0x557544 (缺少 UUID b5f419596300357c85f161f5e6e0920d)
67 Flutter                        0x3d99a8 (缺少 UUID b5f419596300357c85f161f5e6e0920d)
68 Flutter                        0x3feba4 (缺少 UUID b5f419596300357c85f161f5e6e0920d)
69 Flutter                        0x30584c (缺少 UUID b5f419596300357c85f161f5e6e0920d)
70 Flutter                        0x308b48 (缺少 UUID b5f419596300357c85f161f5e6e0920d)
71 CoreFoundation                 0xa7258 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 28
72 CoreFoundation                 0x30af8 __CFRunLoopDoTimer + 1008
73 CoreFoundation                 0x2b6b0 __CFRunLoopDoTimers + 316
74 CoreFoundation                 0xb3a4 __CFRunLoopRun + 1964
75 CoreFoundation                 0x1e240 CFRunLoopRunSpecific + 572
76 Flutter                        0x308a18 (缺少 UUID b5f419596300357c85f161f5e6e0920d)
77 Flutter                        0x3083fc (缺少 UUID b5f419596300357c85f161f5e6e0920d)
78 libsystem_pthread.dylib        0x3348 _pthread_start + 116
79 libsystem_pthread.dylib        0x1948 thread_start + 8

Code sample

Logs

Flutter 3.0.5 • channel stable • https://github.com/flutter/flutter.git
Framework • revision f1875d570e (8 days ago) • 2022-07-13 11:24:16 -0700
Engine • revision e85ea0e79c
Tools • Dart 2.17.6 • DevTools 2.12.2

Hi @shingohu, could you provide the output of flutter doctor -v and the affected device information?

Hi @shingohu, could you provide the output of flutter doctor -v and the affected device information?
@huycozy
flutter doctor -v

[✓] Flutter (Channel stable, 3.0.5, on macOS 12.4 21F79 darwin-arm (Rosetta), locale zh-Hans-CN)
    • Flutter version 3.0.5 at /Users/hellotalk/Applications/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f1875d570e (9 days ago), 2022-07-13 11:24:16 -0700
    • Engine revision e85ea0e79c
    • Dart version 2.17.6
    • DevTools version 2.12.2
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /Users/hellotalk/Library/Android/sdk
    • Platform android-32, build-tools 32.1.0-rc1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/XCode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

Scanning for devices is taking a long time...[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.4 21F79 darwin-arm (Rosetta)
    • Chrome (web)    • chrome • web-javascript • Google Chrome 103.0.5060.134
    ! Error: Jersey 11 is not connected. Xcode will continue when Jersey 11 is connected. (code -13)

[✓] HTTP Host Availability
    • All required HTTP hosts are available

crash on iOS15 100%  and foreground 100%

@flutter-symbolizer-bot https://github.com/flutter/flutter/issues/108101#issue-1313108106 force flutter#v3.0.5 ios release arm64

@shingohu I see there's an open issue that has a part of similar stack trace  #68853 but not exactly the same.
Keeping it open for further insights from the team.

@shingohu you shared the crashed thread stack, can you also share the exception type/subtype/message/termination reason etc at the top? Or the whole crash log?

This is failing on spawning a thread. It is likely going to happen due to resource exhaustion. Without a reproducible test case, there is likely nothing we can do to verify if the VM or engine is doing something incorrectly. cc @rmacnak-google for thoughts.

Right, the usual reason we would fail to start a new thread is the process already has too many threads. But without a reproduction there's not much else we can say.

Closing as unactionable.


WL-5128 Change so that the chosen copyright text displays.

Doesn't seem ideal, if the user has add copyright information but not selected 'Use copyright information below' under copyright status (both on Edit Details from the Resources drop-down on a file) then the copyright information is still displayed.  Cannot see a way of avoiding this without hard coding something that will not be nice.

I dont follow your comment sorry.


feat: add a login alarm for ops1 and ops2

Summary | Résumé

Creates two sns topics one warn and one critical
Alerts when users try to login, alerts on the warning topic when 2
failures occur, alert on critical when a success occurs

Just needs the module source, but looks like the other code we use

That's embarassing


D435i - shifted image for infra cameras with resolution 1280x800

Required Info

Camera Model
D400 (D435i camera)

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 18.04

Kernel Version (Linux Only)
4.15.0-47-generic

Platform
PC

SDK Version
v2.25.0

Language
C

Segment
Robot

Issue Description
I'm facing an issue with resoution 1280x800. The image does not correspond to the distance and position of the camera towards the target in this case. I attached the images.
This image is captured with resolution 1280x800

This image is captured with resolution 1280x720

Thank you for your help.
Jan

I updated the firmware to recommended versions and it helped. Now it is fine. Thanks!


remove duplicate code

Current coverage is 40.31% (diff: 0.00%)

Merging #2089 into master will increase coverage by 0.04%

@@             master      #2089   diff @@
==========================================
  Files          1583       1577     -6
  Lines         54627      54498   -129
  Methods       10774      10759    -15
  Messages          0          0
  Branches       7468       7436    -32
==========================================
- Hits          21999      21970    -29
+ Misses        32628      32528   -100
  Partials          0          0

Powered by Codecov. Last update f6a2981...72595a4


How to use webpackbar to monitor the total compilation progress when exporting multiple configurations?

Problem: How to use webpackbar to monitor the total compilation progress when exporting multiple configurations?
module.exports = [
  {
    output: {
      filename: './dist-amd.js',
      libraryTarget: 'amd',
    },
    name: 'amd',
    entry: './app.js',
    mode: 'production',
  },
  {
    output: {
      filename: './dist-commonjs.js',
      libraryTarget: 'commonjs',
    },
    name: 'commonjs',
    entry: './app.js',
    mode: 'production',
  },
];

Thank you!

Can you share how do you solve this?


[Mod Info] Dynamic Resolution (Fixed for 1.9!) [Steam ID  812713438] by Gradius Twin

Mod:
Dynamic Resolution (Fixed for 1.9!) [Steam ID  812713438] by Gradius Twin
Other Information

Alternatives: which mods are alternatives for this one.

Compat report currently states:
 - An alternative you could use:
    * [Steam ID<PHONE_NUMBER>] Render It!
      Workshop page: https://steamcommunity.com/sharedfiles/filedetails/?id=1794015399

I'm not sure that's a valid replacement as Render It doesn't allow user to set bigger render size, it only allows them to tweak how the current scene is rendered.
Dynamic Resolution mod doesn't tweak how the scene is rendered, it just changes the size of the rendering - so by default the city is rendered at screen size. DR mod allows user to render it from 25% up to something like 500% of their screen size, then scale the result back to their screen size.
Users on potato computers can get performance boost by using lower resolution than their screen size, at the expense of worse graphics quality (more blurry). For screenshots or for users with big GPUs, graphics quality can be significantly improved by rendering at higher resolutions, at the expese of more GPU load.
It might be worth noting that CSL has a special Shift+F12 hotkey which takes a high-definition screenshot; it temporarily sets render size to 200%, takes screenshot, and saves lossless copy to folder as described here:

If user only wants Dynamic Resolution mod for high-res screenshots, the Shift+F12 combo might be more suitable for their needs (as it won't be frying their GPU during normal gameplay if they forget to revert to 100% render size).

I'll add a note about Shift-F12 and remove Render It as alternative. This will be updated in catalog 3.48.

I'll add a note about Shift-F12 and remove Render It as alternative. This will be updated in catalog 3.48.


2024.1 deprication for SUPPORT_*

Describe the bug
2024.1 will throw a deprication warning for the CLIMATE.SUPPORT_* components.
from homeassistant.components.climate.const import (
    CURRENT_HVAC_HEAT,
    CURRENT_HVAC_IDLE,
    SUPPORT_PRESET_MODE,
    SUPPORT_TARGET_TEMPERATURE,
)

The SUPPORT_* should be replaced with ClimateEntityFeature
https://developers.home-assistant.io/blog/2022/04/02/support-constants-deprecation
To Reproduce
Expected behavior
Screenshots
Version
** Debug SCAN **
** IMPORTANT **
Additional context

Fixed in https://github.com/bosch-thermostat/home-assistant-bosch-custom-component/releases/tag/v0.24.1


Adding "Browser" to the "Contents" section

Description
The table of contents section was missing the "Browser" section, and wanted to make it easier to navigate straight to it from the README.md file!
Checklist

[x] Only one project/change is in this pull request
[ ] Addition in chronological order (bottom of category)
[ ] Appropriate language icon(s) added if applicable
[ ] Has a commit from less than 2 years ago
[x] Has a clear README in English

@JonLim Thank for your PR! 👍


Consumer not consuming message after error

Hi @mhowlett  - we are seeing occasionally after some errors our consume stop consuming messages but the application is still running seems like it is in a zombie state. How to determine which errors can be ignored and which cannot be ignored. Below are few errors
Broker: coordinator load in progress
Disconnected(after<PHONE_NUMBER>ms in up state)
also if we have 3 broker it is best to specify all the 3 broker in consumer config or even 1 works as i was seeing internally it connects to all 3?
please guide us.
thanks

Hi @mhowlett - any thoughts/suggestions.. we are already checking the isfatal flag but still app sometimes hit the zombie state in case of non fatal errors
Thanks


Missynthesis with break statements

The break statement support doesn't take the effects of the step expression into account. We missynthesize a priority encoder if written this way:
    always_comb begin: for_loop_priority_encoder
        integer i = 0;
        encoded = 1'b0;
        for (i = 0; i < INPUT_WIDTH; i++) begin
            if (bits[i]) begin
                break;
            end
        end
        encoded = i;
    end

The step expression is not evaluated inside the conditional branch for:
SwitchHelper b(current_case, vstate, {RTLIL::S0});
			b.sw->statement = &stmt;

			b.branch({substitute_rvalue(disable)}, [&]() {
				current_case->statement = &stmt.body;
				eval.push_frame(nullptr, disable);
				stmt.body.visit(*this);
				eval.pop_frame();
			});
			b.finish(netlist);

			for (auto step : stmt.steps)
				eval(*step);

			ncycles++;

I assume that the effect of the step should also be tracked inside the branch.

Yes, but at the same time we need for it to be constant folded for the cv check, which may require some restructuring of the case tree to work out. (Specifically subsequent iterations need to be below earlier iterations on the case tree.) I can look into it later.

Okay, thanks!

Should be addressed in e08d249


Can't run weave getting started notebook locally

Describe the bug
Hi,
I'm trying to run the Quick Start tutorial. It worked fine in Google Colab notebook.
But when I try to run on my PC I get the following error:
---------------------------------------------------------------------------
HTTPError                                 Traceback (most recent call last)
Cell In[15], line 24
     17     return response.choices[0].message.content
     20 sentence = """I watched as a Tyrannosaurus rex (T. rex) chased after a Triceratops (Trike), \
     21 both carnivore and herbivore locked in an ancient dance. Meanwhile, a gentle giant \
     22 Brachiosaurus (Brachi) calmly munched on treetops, blissfully unaware of the chaos below."""
---> 24 result = extract_dinos(sentence)
     25 print(result)

Cell In[15], line 2, in extract_dinos(sentence)
      1 def extract_dinos(sentence: str) -> dict:
----> 2     response = client.chat.completions.create(
      3         model="gpt-4o",
      4         messages=[
      5             {
      6                 "role": "system",
      7                 "content": """In JSON format extract a list of `dinosaurs`, with their `name`,
      8 their `common_name`, and whether its `diet` is a herbivore or carnivore"""
      9             },
     10             {
     11                 "role": "user",
     12                 "content": sentence
     13             }
     14             ],
     15             response_format={ "type": "json_object" }
     16         )
     17     return response.choices[0].message.content

File ~\AppData\Roaming\Python\Python312\site-packages\weave\trace\op.py:336, in op.<locals>.op_deco.<locals>.create_wrapper.<locals>.wrapper(*args, **kwargs)
    334 if client_context.weave_client.get_weave_client() is None:
    335     return func(*args, **kwargs)
--> 336 call = _create_call(wrapper, *args, **kwargs)  # type: ignore
    337 res, _ = _execute_call(wrapper, call, *args, **kwargs)  # type: ignore
    338 return res

File ~\AppData\Roaming\Python\Python312\site-packages\weave\trace\op.py:159, in _create_call(func, *args, **kwargs)
    156 client._save_nested_objects(inputs_with_defaults)
    157 attributes = call_attributes.get()
--> 159 return client.create_call(
    160     func,
    161     inputs_with_defaults,
    162     parent_call,
    163     attributes=attributes,
    164 )

File ~\AppData\Roaming\Python\Python312\site-packages\weave\trace_sentry.py:211, in Sentry.watch.<locals>.watch_dec.<locals>.wrapper(*args, **kwargs)
    208 @functools.wraps(func)
    209 def wrapper(*args: Any, **kwargs: Any) -> Any:
    210     try:
--> 211         return func(*args, **kwargs)
    212     except Exception as e:
    213         self.exception(e)

File ~\AppData\Roaming\Python\Python312\site-packages\weave\weave_client.py:507, in WeaveClient.create_call(self, op, inputs, parent, attributes, display_name, use_stack)
    505 if isinstance(op, Op):
    506     unbound_op = maybe_unbind_method(op)
--> 507     op_def_ref = self._save_op(unbound_op)
    508     op_str = op_def_ref.uri()
    509 else:

File ~\AppData\Roaming\Python\Python312\site-packages\weave\weave_client.py:846, in WeaveClient._save_op(self, op, name)
    844 if name is None:
    845     name = op.name
--> 846 op_def_ref = self._save_object_basic(op, name)
    848 # setattr(op, "ref", op_def_ref) fails here
    849 # op.ref = op_def_ref fails here
    850 # Seems to be the only way to set the ref on the op
    851 op.__dict__["ref"] = op_def_ref

File ~\AppData\Roaming\Python\Python312\site-packages\weave\weave_client.py:744, in WeaveClient._save_object_basic(self, val, name, branch)
    742 if isinstance(val, ObjectRef):
    743     return val
--> 744 json_val = to_json(val, self._project_id(), self.server)
    746 response = self.server.obj_create(
    747     ObjCreateReq(
    748         obj=ObjSchemaForInsert(
   (...)
    753     )
    754 )
    755 ref: Ref

File ~\AppData\Roaming\Python\Python312\site-packages\weave\trace\serialize.py:39, in to_json(obj, project_id, server)
     37 file_digests = {}
     38 for name, val in encoded["files"].items():
---> 39     file_response = server.file_create(
     40         FileCreateReq(project_id=project_id, name=name, content=val)
     41     )
     42     file_digests[name] = file_response.digest
     43 result = {
     44     "_type": encoded["_type"],
     45     "weave_type": encoded["weave_type"],
     46     "files": file_digests,
     47 }

File ~\AppData\Roaming\Python\Python312\site-packages\tenacity\__init__.py:336, in BaseRetrying.wraps.<locals>.wrapped_f(*args, **kw)
    334 copy = self.copy()
    335 wrapped_f.statistics = copy.statistics  # type: ignore[attr-defined]
--> 336 return copy(f, *args, **kw)

File ~\AppData\Roaming\Python\Python312\site-packages\tenacity\__init__.py:475, in Retrying.__call__(self, fn, *args, **kwargs)
    473 retry_state = RetryCallState(retry_object=self, fn=fn, args=args, kwargs=kwargs)
    474 while True:
--> 475     do = self.iter(retry_state=retry_state)
    476     if isinstance(do, DoAttempt):
    477         try:

File ~\AppData\Roaming\Python\Python312\site-packages\tenacity\__init__.py:376, in BaseRetrying.iter(self, retry_state)
    374 result = None
    375 for action in self.iter_state.actions:
--> 376     result = action(retry_state)
    377 return result

File ~\AppData\Roaming\Python\Python312\site-packages\tenacity\__init__.py:398, in BaseRetrying._post_retry_check_actions.<locals>.<lambda>(rs)
    396 def _post_retry_check_actions(self, retry_state: "RetryCallState") -> None:
    397     if not (self.iter_state.is_explicit_retry or self.iter_state.retry_run_result):
--> 398         self._add_action_func(lambda rs: rs.outcome.result())
    399         return
    401     if self.after is not None:

File C:\ProgramData\anaconda3\envs\finetuning\Lib\concurrent\futures\_base.py:449, in Future.result(self, timeout)
    447     raise CancelledError()
    448 elif self._state == FINISHED:
--> 449     return self.__get_result()
    451 self._condition.wait(timeout)
    453 if self._state in [CANCELLED, CANCELLED_AND_NOTIFIED]:

File C:\ProgramData\anaconda3\envs\finetuning\Lib\concurrent\futures\_base.py:401, in Future.__get_result(self)
    399 if self._exception:
    400     try:
--> 401         raise self._exception
    402     finally:
    403         # Break a reference cycle with the exception in self._exception
    404         self = None

File ~\AppData\Roaming\Python\Python312\site-packages\tenacity\__init__.py:478, in Retrying.__call__(self, fn, *args, **kwargs)
    476 if isinstance(do, DoAttempt):
    477     try:
--> 478         result = fn(*args, **kwargs)
    479     except BaseException:  # noqa: B902
    480         retry_state.set_exception(sys.exc_info())  # type: ignore[arg-type]

File ~\AppData\Roaming\Python\Python312\site-packages\weave\trace_server\remote_http_trace_server.py:397, in RemoteHTTPTraceServer.file_create(self, req)
    380 @tenacity.retry(
    381     stop=tenacity.stop_after_delay(REMOTE_REQUEST_RETRY_DURATION),
    382     wait=tenacity.wait_exponential_jitter(
   (...)
    389 )
    390 def file_create(self, req: tsi.FileCreateReq) -> tsi.FileCreateRes:
    391     r = requests.post(
    392         self.trace_server_url + "/files/create",
    393         auth=self._auth,
    394         data={"project_id": req.project_id},
    395         files={"file": (req.name, req.content)},
    396     )
--> 397     r.raise_for_status()
    398     return tsi.FileCreateRes.model_validate(r.json())

File C:\ProgramData\anaconda3\envs\finetuning\Lib\site-packages\requests\models.py:1024, in Response.raise_for_status(self)
   1019     http_error_msg = (
   1020         f"{self.status_code} Server Error: {reason} for url: {self.url}"
   1021     )
   1023 if http_error_msg:
-> 1024     raise HTTPError(http_error_msg, response=self)

HTTPError: 401 Client Error: Unauthorized for url: https://trace.wandb.ai/files/create

Here's the piece of code that caused the issue:

import weave
from openai import OpenAI

client = OpenAI(api_key="...")

# Weave will track the inputs, outputs and code of this function
@weave.op()
def extract_dinos(sentence: str) -> dict:
    response = client.chat.completions.create(
        model="gpt-4o",
        messages=[
            {
                "role": "system",
                "content": """In JSON format extract a list of `dinosaurs`, with their `name`,
their `common_name`, and whether its `diet` is a herbivore or carnivore"""
            },
            {
                "role": "user",
                "content": sentence
            }
            ],
            response_format={ "type": "json_object" }
        )
    return response.choices[0].message.content

# Initialise the weave project
weave.init('jurassic-park')

sentence = """I watched as a Tyrannosaurus rex (T. rex) chased after a Triceratops (Trike), \
both carnivore and herbivore locked in an ancient dance.  My current theory is that there was an error when two of our backend services were communicating. Could you tell me if this is consistently reproducible for you or intermittent?

It is consistent

Any update on this issue?
Thanks

We've identified two causes of the Unauthorized error so far, but we don't think either of them applies to your case.

There was a brief backend service communication problem during some write authorization checks.
We identified a problem with service accounts accessing Weave.

One thing you could try is running "wandb login --relogin" and letting us know what that shows and whether the problem persists.
Another thing we could try is having you upgrade to our latest release, weave 0.50.12. That supports an environment variable designed to help us debug this sort of situation. You could add this to your script:
import os
os.environ["WEAVE_DEBUG_HTTP"] = "1"

And the resulting output should give us a better idea of if there is a problem with the headers your client is sending.

Actually, I just discovered a Windows-only bug that I think might be the cause of your problem. apikeys on Windows are typically kept in ~/_netrc instead of ~/.netrc. Most of our code checks both places but some authentication code in Weave wasn't. I've got a proposed fix up at https://github.com/wandb/weave/pull/2039

@jamie-rasmussen Thanks for the update and follow up.
1- Upgrading to weave=0.50.12 didn't work.
I set the debug var as you said:
import os
os.environ["WEAVE_DEBUG_HTTP"] = "1"

Here's the output:
Running the following init code:
import weave
# Initialise the weave project
weave.init('jurassic-park')

The output is:
Please login to Weights & Biases (https://wandb.ai/) to continue:
---------------------
Time: 10:25:42.945668
Thread ID: 11480
Method: GET
URL: https://trace.wandb.ai/server_info
Headers:
  User-Agent:
python-requests/2.32.3
  Accept-Encoding:
gzip, deflate
  Accept:
*/*
  Connection:
keep-alive
Body:
  None
----- Response below -----
Elapsed Time: 0.47 seconds
Status Code: 200
Reason: OK
Headers:
  content-type:
application/json
  x-cloud-trace-context:
21b8b242b36cc2b92a0ad5f9470cd0ce;o=1
  date:
Tue, 30 Jul 2024 07:25:43 GMT
  server:
Google Frontend
  Content-Length:
46
  via:
1.1 google
  Alt-Svc:
h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Body:
  1 {
  2     "min_required_weave_python_version": "0.46.0"
  3 }
Logged in as Weights & Biases user: ahmadelsallab.
View Weave data at https://wandb.ai/ahmadelsallab/jurassic-park/weave
<weave.weave_client.WeaveClient at 0x1f5451dc8f0>

Running:
import weave

# Weave will track the inputs, outputs and code of this function
@weave.op()
def extract_dinos(sentence: str) -> dict:
    response = client.chat.completions.create(
        model="gpt-4o",
        messages=[
            {
                "role": "system",
                "content": """In JSON format extract a list of `dinosaurs`, with their `name`,
their `common_name`, and whether its `diet` is a herbivore or carnivore"""
            },
            {
                "role": "user",
                "content": sentence
            }
            ],
            response_format={ "type": "json_object" }
        )
    return response.choices[0].message.content

# Initialise the weave project
#weave.init('jurassic-park')

sentence = """I watched as a Tyrannosaurus rex (T. rex) chased after a Triceratops (Trike), \
both carnivore and herbivore locked in an ancient dance. Meanwhile, a gentle giant \
Brachiosaurus (Brachi) calmly munched on treetops, blissfully unaware of the chaos below."""

result = extract_dinos(sentence)
print(result)

I get an error + new debug output as follows:
---------------------
Time: 10:25:44.194407
Thread ID: 11480
Method: POST
URL: https://trace.wandb.ai/files/create
Headers:
  User-Agent:
python-requests/2.32.3
  Accept-Encoding:
gzip, deflate
  Accept:
*/*
  Connection:
keep-alive
  Content-Length:
874
  Content-Type:
multipart/form-data; boundary=958220b639a5cdb3b19af48b8e25d4dd
Body:
--958220b639a5cdb3b19af48b8e25d4dd
Content-Disposition: form-data; name="project_id"

ahmadelsallab/jurassic-park
--958220b639a5cdb3b19af48b8e25d4dd
Content-Disposition: form-data; name="file"; filename="obj.py"

import weave

@weave.op()
def extract_dinos(sentence: str) -> dict:
    response = client.chat.completions.create(
        model="gpt-4o",
        messages=[
            {
                "role": "system",
                "content": """In JSON format extract a list of `dinosaurs`, with their `name`,
their `common_name`, and whether its `diet` is a herbivore or carnivore"""
            },
            {
                "role": "user",
                "content": sentence
            }
            ],
            response_format={ "type": "json_object" }
        )
    return response.choices[0].message.content

--958220b639a5cdb3b19af48b8e25d4dd--

----- Response below -----
Elapsed Time: 0.24 seconds
Status Code: 401
Reason: Unauthorized
Headers:
  www-authenticate:
Basic
  content-type:
application/json
  x-cloud-trace-context:
d952b356bdf57d3fab51ac4091dde3b9;o=1
  date:
Tue, 30 Jul 2024 07:25:44 GMT
  server:
Google Frontend
  Content-Length:
30
  via:
1.1 google
  Alt-Svc:
h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Body:
  1 {
  2     "detail": "Not authenticated"
  3 }
---------------------------------------------------------------------------
HTTPError                                 Traceback (most recent call last)
Cell In[15], line 31
     24 # Initialise the weave project
     25 #weave.init('jurassic-park')
     27 sentence = """I watched as a Tyrannosaurus rex (T. rex) chased after a Triceratops (Trike), \
     28 both carnivore and herbivore locked in an ancient dance. Meanwhile, a gentle giant \
     29 Brachiosaurus (Brachi) calmly munched on treetops, blissfully unaware of the chaos below."""
---> 31 result = extract_dinos(sentence)
     32 print(result)

File ~\AppData\Roaming\Python\Python312\site-packages\weave\trace\op.py:336, in op.<locals>.op_deco.<locals>.create_wrapper.<locals>.wrapper(*args, **kwargs)
    334 if client_context.weave_client.get_weave_client() is None:
    335     return func(*args, **kwargs)
--> 336 call = _create_call(wrapper, *args, **kwargs)  # type: ignore
    337 res, _ = _execute_call(wrapper, call, *args, **kwargs)  # type: ignore
    338 return res

File ~\AppData\Roaming\Python\Python312\site-packages\weave\trace\op.py:159, in _create_call(func, *args, **kwargs)
    156 client._save_nested_objects(inputs_with_defaults)
    157 attributes = call_attributes.get()
--> 159 return client.create_call(
    160     func,
    161     inputs_with_defaults,
    162     parent_call,
    163     attributes=attributes,
    164 )

File ~\AppData\Roaming\Python\Python312\site-packages\weave\trace_sentry.py:211, in Sentry.watch.<locals>.watch_dec.<locals>.wrapper(*args, **kwargs)
    208 @functools.wraps(func)
    209 def wrapper(*args: Any, **kwargs: Any) -> Any:
    210     try:
--> 211         return func(*args, **kwargs)
    212     except Exception as e:
    213         self.exception(e)

File ~\AppData\Roaming\Python\Python312\site-packages\weave\weave_client.py:507, in WeaveClient.create_call(self, op, inputs, parent, attributes, display_name, use_stack)
    505 if isinstance(op, Op):
    506     unbound_op = maybe_unbind_method(op)
--> 507     op_def_ref = self._save_op(unbound_op)
    508     op_str = op_def_ref.uri()
    509 else:

File ~\AppData\Roaming\Python\Python312\site-packages\weave\weave_client.py:846, in WeaveClient._save_op(self, op, name)
    844 if name is None:
    845     name = op.name
--> 846 op_def_ref = self._save_object_basic(op, name)
    848 # setattr(op, "ref", op_def_ref) fails here
    849 # op.ref = op_def_ref fails here
    850 # Seems to be the only way to set the ref on the op
    851 op.__dict__["ref"] = op_def_ref

File ~\AppData\Roaming\Python\Python312\site-packages\weave\weave_client.py:744, in WeaveClient._save_object_basic(self, val, name, branch)
    742 if isinstance(val, ObjectRef):
    743     return val
--> 744 json_val = to_json(val, self._project_id(), self.server)
    746 response = self.server.obj_create(
    747     ObjCreateReq(
    748         obj=ObjSchemaForInsert(
   (...)
    753     )
    754 )
    755 ref: Ref

File ~\AppData\Roaming\Python\Python312\site-packages\weave\trace\serialize.py:39, in to_json(obj, project_id, server)
     37 file_digests = {}
     38 for name, val in encoded["files"].items():
---> 39     file_response = server.file_create(
     40         FileCreateReq(project_id=project_id, name=name, content=val)
     41     )
     42     file_digests[name] = file_response.digest
     43 result = {
     44     "_type": encoded["_type"],
     45     "weave_type": encoded["weave_type"],
     46     "files": file_digests,
     47 }

File ~\AppData\Roaming\Python\Python312\site-packages\tenacity\__init__.py:336, in BaseRetrying.wraps.<locals>.wrapped_f(*args, **kw)
    334 copy = self.copy()
    335 wrapped_f.statistics = copy.statistics  # type: ignore[attr-defined]
--> 336 return copy(f, *args, **kw)

File ~\AppData\Roaming\Python\Python312\site-packages\tenacity\__init__.py:475, in Retrying.__call__(self, fn, *args, **kwargs)
    473 retry_state = RetryCallState(retry_object=self, fn=fn, args=args, kwargs=kwargs)
    474 while True:
--> 475     do = self.iter(retry_state=retry_state)
    476     if isinstance(do, DoAttempt):
    477         try:

File ~\AppData\Roaming\Python\Python312\site-packages\tenacity\__init__.py:376, in BaseRetrying.iter(self, retry_state)
    374 result = None
    375 for action in self.iter_state.actions:
--> 376     result = action(retry_state)
    377 return result

File ~\AppData\Roaming\Python\Python312\site-packages\tenacity\__init__.py:398, in BaseRetrying._post_retry_check_actions.<locals>.<lambda>(rs)
    396 def _post_retry_check_actions(self, retry_state: "RetryCallState") -> None:
    397     if not (self.iter_state.is_explicit_retry or self.iter_state.retry_run_result):
--> 398         self._add_action_func(lambda rs: rs.outcome.result())
    399         return
    401     if self.after is not None:

File C:\ProgramData\anaconda3\envs\finetuning\Lib\concurrent\futures\_base.py:449, in Future.result(self, timeout)
    447     raise CancelledError()
    448 elif self._state == FINISHED:
--> 449     return self.__get_result()
    451 self._condition.wait(timeout)
    453 if self._state in [CANCELLED, CANCELLED_AND_NOTIFIED]:

File C:\ProgramData\anaconda3\envs\finetuning\Lib\concurrent\futures\_base.py:401, in Future.__get_result(self)
    399 if self._exception:
    400     try:
--> 401         raise self._exception
    402     finally:
    403         # Break a reference cycle with the exception in self._exception
    404         self = None

File ~\AppData\Roaming\Python\Python312\site-packages\tenacity\__init__.py:478, in Retrying.__call__(self, fn, *args, **kwargs)
    476 if isinstance(do, DoAttempt):
    477     try:
--> 478         result = fn(*args, **kwargs)
    479     except BaseException:  # noqa: B902
    480         retry_state.set_exception(sys.exc_info())  # type: ignore[arg-type]

File ~\AppData\Roaming\Python\Python312\site-packages\weave\trace_server\remote_http_trace_server.py:402, in RemoteHTTPTraceServer.file_create(self, req)
    385 @tenacity.retry(
    386     stop=tenacity.stop_after_delay(REMOTE_REQUEST_RETRY_DURATION),
    387     wait=tenacity.wait_exponential_jitter(
   (...)
    394 )
    395 def file_create(self, req: tsi.FileCreateReq) -> tsi.FileCreateRes:
    396     r = requests.post(
    397         self.trace_server_url + "/files/create",
    398         auth=self._auth,
    399         data={"project_id": req.project_id},
    400         files={"file": (req.name, req.content)},
    401     )
--> 402     r.raise_for_status()
    403     return tsi.FileCreateRes.model_validate(r.json())

File C:\ProgramData\anaconda3\envs\finetuning\Lib\site-packages\requests\models.py:1024, in Response.raise_for_status(self)
   1019     http_error_msg = (
   1020         f"{self.status_code} Server Error: {reason} for url: {self.url}"
   1021     )
   1023 if http_error_msg:
-> 1024     raise HTTPError(http_error_msg, response=self)

HTTPError: 401 Client Error: Unauthorized for url: https://trace.wandb.ai/files/create

2- Renaming ~/_netrc into ~/.netrc worked. Thanks!

Thank you again for the detailed information. The fix (https://github.com/wandb/weave/pull/2039) has been merged and will be part of the next Weave library release. We've been posting new releases approximately weekly. If you upgrade after that you should be able to remove the duplicate ~/.netrc file workaround. I'll close this ticket now.
If you have additional feedback or error reports for Weave, posting them to its repo (https://github.com/wandb/weave) will help get them to our team quicker. We appreciate you trying Weave and helping us make it better!


NPE in SocialContextTemplate.getSocialContext(..) if no context object in response

a request for /{user}?fields=context may return a response as simple as this one (using an existing user ID that didn't authorize the app):
{
  "id": "{user}"
}

This response causes a NullPointerException at
JsonNode contextNode = responseNode.get("context").get(context);

I've just revisited this and it's still the same problem, the returned JSON has slightly changed though:
{
  "context": {
    "id": "{contextId}"
  },
  "id": "{userId}"
}

this pushes the NPE down by just one line though:
JsonNode contextNode = responseNode.get("context").get(context);
ArrayNode dataNode = (ArrayNode) contextNode.get("data");


Format on Save not working

Format on save is not working for me in Atom 1.25.0, but it worked previously.
Calling the command does work

Try to remove quote marks around the path to clang-format executable in the plugin config.

Sorry for the long time to reply. Did the above comment by @tikonen fix it? I'm going to assume it did and close this issue, if you are still experiencing the error let me know and I'll look into it.


Avoid pointer events on the bullet View containers.

pointerEvents="box-none" is applied to the containers for the arrows elements.
This commit adds it to the bullet containers too so that users can have more area to swipe.

Looks good, thanks!


Pin cmake-js to ~5.2.0 to fix building on Windows

Some change between cmake-js 5.2.0 and 5.3.0 broke our AppVeyor tests (logs), as well as locally on my machine. See https://github.com/cmake-js/cmake-js/issues/186.

9.0.1


Complete testing of #1979

There are a lot of unit tests already, but there are some more that need to be written.  Check with @wanderingbort to get the list of what should be done for unit and integration tests. #1979

@wanderingbort @heifner I am thinking that this is complete or will not be implemented.  If I don't hear from you I will presume that is the case.

The unit test coverage is sufficient.


libfec \o/

I see the docs (and the bench output) mention libfec, but I can't for the life of me find libfec — well, more precisely, I found a couple things that might be libfec.
I forked one from Google code, and the more likely one seems to be from ka9q.net … but it won't compile on my modern computer.  Some of the preprocessor directives comment out too much code, which is fixable, but other linking issues come up too.
Is that the right one?  I can probably fix it or is it the Google code one?  Asking for a quick doc fix here, sortof along the lines of changing “libfec” to “libfec by so-and-so.”

Paul, good point. Yes, I'm referring to Phil Karn's (KA9Q's) old, old libfec library. Unfortunately the assembly is old and doesn't support modern architectures. The easy fix is to force it to use portable C. It's of course a lot slower than the MMX/SSE assembly version he provides, but it gets the job done in a pinch. I'm trying to spin my own decoders (Viterbi, RS, BCH, and LDPC) but it's not high on my priority list.
Updating the documentation is!

Hi, thanks.  I have no idea what you just said regarding decoders, but perhaps it'll make amusing wiki queries later.  I don't particularly even need fec, it just can't handle building the package incompletely and then having 'make bench' complain to me.
I'll also look for the portable C stuff.  Is it maybe a configure flag?  Thanks again.

I don't think there's a configure option for it. I can send you a patch that might help.

How did you force it to use Portable C?  Just modifying the Makefile.in to use something like pcc instead of gcc?

Oh, I see the patch.  Missed that.

that patch does not apply cleanly — but fec compiled …

Well it compiles, but fails to provide cpu_mode() and various other failures when you make test or try to build with it from liquid-dsp.  I can just chalk this up as: doesn't work.  I definitely don't actually need it.

Ok. I'll try to generate a good patch and share it.

On Jul 8, 2015, at 10:40, Paul Miller<EMAIL_ADDRESS>wrote:
Well it compiles, but fails to provide cpu_mode() and various other failures when you make test or try to build with it from liquid-dsp. I can just chalk this up as: doesn't work. I definitely don't actually need it.
—
Reply to this email directly or view it on GitHub.

@jettero I have a clone which works on x86-64 darwin. It might work for you. https://github.com/brian-armstrong/libfec
Note that it is not clever enough to decide system it is building on, so you may need to invoke ./configure with --build e.g. ./configure --build=x86_64-apple-darwin15.0.0. There's probably a good way to avoid that but my configure-foo isn't very strong.

Brian's fix to libfec is better than any patch I could have created.


[Feature] Case insensitive search

There needs to be an intermediate option between case-sensitive search, and using regular expressions for describing search text.  Regular expression usage for case-insensitive is very verbose, since the regexp parser doesn't currently allow for special flags.
Possible Solution

Add new commands find-like and exclude-like to apply case-insensitive filters.

Alternatives

Adding options to find-text and exclude-text such as --case-insensitive.  This would require option parsing for commands.

Added in c2357c0a3c8e2fb6a94825c7199f96bae6695849.


fix(puppeteer): upgrade puppeteer to 13.3+

Fix #864: Upgrade puppeteer to 13.3+

Codecov Report

Merging #867 (e070f81) into develop (2c14c54) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #867   +/-   ##
========================================
  Coverage    65.41%   65.41%
========================================
  Files           47       47
  Lines         1573     1573
  Branches       342      342
========================================
  Hits          1029     1029
  Misses         544      544

Continue to review full report at Codecov.

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


task144 add apache license to label.go

Ⅰ. Describe what this PR does
add apache license to label.go
Ⅱ. Does this pull request fix one issue?

fixes #XXXX
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

/assign @yangyuliufeng


Fix article in IoT Edge installation docs

Updates "a" => "an" because it is in front of a vowel

@myagley : Thanks for your contribution! The author, @kgremban, has been notified to review your proposed change.

Thanks @myagley
#sign-off


@sync-ignore proxy setting double slash gets lost

🐛 Describe the bug
My settings.json looks like this:
// @sync-ignore
"http.proxy": "http://user:pw@myproxy:port",
// @sync-ignore
"http.proxyStrictSSL": false,
When download my laptop settings to my office computer, the settings.json gets rewritten but the http proxy becomes http:user:pw@myproxy:port (missing the "//") so that all extension downloads fail afterwards.
🌴 Visual Studio Code Version : 1.331

@shanalikhan I will take this


Use semantic versioning for the stable release v1

Semantic versioning uses the major.minor.patch-suffix scheme. Are there any particular reasons not use it?
Note: You were using it until the first stable version: v1. It should be like v1.0.0
See: https://semver.org

GitHub Actions release tags are not semantic version numbers. See https://docs.github.com/en/actions/creating-actions/about-custom-actions#using-tags-for-release-management.

GitHub Actions release tags are not semantic version numbers. See https://docs.github.com/en/actions/creating-actions/about-custom-actions#using-tags-for-release-management.

The second item on the list: Create a release using semantic versioning...

Moving major version tags to point current release can be extra work. I can understand if you don't want extra work to keep up.


[Keychain] Service name collision

[REQUIRED] Step 1: Describe your environment

Xcode version: 12
Firebase SDK version: 6.18 and 6.33
Firebase Component: Firebase Core/ Messaging
Component version: 6.18 and 6.33
Installation method: CocoaPods

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
Somewhere in code (i guess it the analytics module) happens a setting a _pfo value to a keychain without a custom service name.
So when developers using a react-native-keychain and call method getGenericPassword it returns _pfo value instead of the previously saved password.
Code: https://github.com/oblador/react-native-keychain/blob/master/RNKeychainManager/RNKeychainManager.m#L329
Issue: https://github.com/oblador/react-native-keychain/issues/363

Somewhere in code (i guess it the analytics module) happens a setting a _pfo value to a keychain without a custom service name.

Does removing Analytics from the project prevent the bug from occurring?

@morganchen12 Yes

Any action on this? This is still an issue.


Bukkit 1.20.5 support

Fixed MinecraftComponentSerializer
Implemented 1.20.5 book facet using item components
Fixed tab list isSupported check

Don't need setters if 1.17 constructor exists

Fixes #162

Tested this, works perfectly! Great job.

Did you test Audience#sendActionBar here, I'm having issue with it. https://github.com/KyoriPowered/adventure-platform/issues/167


Memleak queue fixes

Fix a memory leak in gfx on error
Now clearing message queue on free just as Hash and ArrayList
dynamic channel message queue now frees objects still in the queue
Clear the client channel queue and free data

@akallabeth just a matter of taste but I prefer
status = op()
if (status)
  .....

over
status = op()

if (status)
  .....

IMHO it looks better when the operation and the test are grouped in the same block.

@mfleisz Already fixed.

@freerdp-bot test


process is not defined

Vue.js version
1.0.19
Steps to reproduce
use webpack
run your web-app in browser
What is Expected?
work as well, as it works in electron
What is actually happening?
In browser environment I get this error Uncaught ReferenceError: process is not defined
It fails in file vue.common.js on line 913

Just in case somebody is facing same issue there's a workaround for it. Just add to your plugins this one
new webpack.DefinePlugin({ 'process.env.NODE_ENV': '"development"' })
in your webpack.config.js

Hi there! I doesn't seem very clear to me what the issue you're mentioning is. This seems to be more of an issue with your Webpack configuration as opposed to a Vue issue.

@FadyMak
It looked really strange for me that vue.js doesn't work with webpack right out of the box. Even if it is a normal behaviour (which I think is not) you should've mention this webpack-specific thing with DefinePlugin somewhere in readme or in the doc.
I think it would be way better to make a little check for environment since vue.common.js can be used in browser as well.

vue.common.js is the common-js bundle. I don't think that you intentionally used this version.
Just use vue.min.js or the development version and you will see, that no such thing as a webpack.DefinePlugin is needed.

@Nirazul It's quite disappointing that it is possible to use a wrong version of lib without realizing it. I just did require('vue') and it seemed to me pretty obvious that everything will work like butter :(

Webpack should automatically shim the process unless you explicitly tell it not to, same for Browserify. Are you using Webpack 2 beta? That might cause different behavior.

@yyx990803 nope, I'm running webpack 1.12.9. Thanks for your reply, it pointed me to the real cause of the problem. Webpack indeed shims process variable for us automagically. I just had target: 'electron' in my webpack.config.js. When I changed it to target: 'web' everything worked as expected!
It turned out to be not a vue issue at all

fyi the suggestion by @kucherenkovova makes the symptom go away (I'm not sure it also solves or works around the problem, perhaps it does) by ensuring that process.env is indeed defined, it has nothing to do with the value of NODE_ENV. So the following also "works"
plugins: [
new webpack.DefinePlugin({
'process.env': {}
}),
],

.min.js version is not suitable for ES6 imports
.esm.js version is not suitable for ES6 imports


The "Funny" i18n languages could be doing more harm than good

The en-Scouse, en-au and en-tx languages could be construed as exploiting stereotypes for comic effect, and thus could offend and alienate some users, and generally make the product look bad and less welcoming.
I'm not arguing that cucumber shouldn't support multiple languages, nor am I arguing that the languages should not be customisable.
I'm arguing that the presence of those languages could well have a negative affect – more negative than positive.

Thanks for raising this Rachel, it's not something that had ever occurred to me before.
I'd love to hear some opinions about this issue.

could be construed as exploiting stereotypes for comic effect

Strewth mate, don't spit the dummy!  I don't know about them Scousers, but us true blue Aussies think it's a bit of a dag.
(Seriously ... I'm Australian, and I have no problem whatsoever with this.  The very fact that there's an en-au language in the software in the first place suggests an awareness of Australia's existence.  That's one up on many projects :smile: ).

Yeah, nah, I don't have a problem with this and I don't see how this might alienate or discourage other users. en-au does not feature any real stereotypical phrases and uses informal language that an Australian English speaker might use in everyday conversation. Even if it did somehow manage to fit in some reference to "shrimps on the barbie", "crikey" or such I'd like to think that if anyone really cared enough about it, they would simply put in a pull request.
A lot of Ruby projects are created out of developers having a bit of fun, and whilst some have made some arguably bad decisions, I don't believe this is one of those. Like Duncan has said, the fact someone made reference to Australia essentially shows awareness and inclusivity more than anything else.

Some history:
The Australian translation comes from my Australian friend @delitescere (cucumber/cucumber@df07d38f6d448c75a34593157e1e9fafa375a929). Sorry Josh - I forgot to credit you.
The Scouse one is from Alexandra Schladebeck (then Alexandra Imrie) (cucumber/gherkin@55810dc7f5df9fc94895d750332939804d1780c7). I don't recall if she's a native speaker of the Scouse dialect, but since she gave me the translation I assume she's at least familiar with it.
The Texan one is from me, and I'm definitely not a speaker of Texan English.
The Australian and Scouse translations are so far-fetched that I'm surprise you'd label them as linguistic stereotypes. That said, if it truly offends you we'll remove them.
The Texan translation is different - I have no problem understanding how that can be seen as a linguistic stereotype. I'm sorry if I hurt anyone's feelings.
We don't plan on making any more releases of Gherkin 2 - our efforts are now on Gherkin 3. Are there any objections if we remove those the three translations in question from Gherkin 3 when that comes out?

@rvedotrc if I understand your point correctly, it doesn't really matter whether individual people from Australia, Liverpool or Texas are offended by these languages, but that someone seeing them could get the impression that this is a community who think it's funny to mock stereotypes. Is that right?

For example, if there were an en-gay or en-ebonics I would be uncomfortable with that, despite being neither gay or black. I think @rvedotrc is pointing out that these examples are at the shallow end of that curve.

Just recently, I was using the en-lol - LOLCAT as a great example of how to make i18n functionality testable - you can test out i81n functionality even if you only speak English.  The extra language is also a great example of how easy it is to add another one.
I can understand the point that people might be offended or uncomfortable if they thought the tool (or tool maintainers) was not being respectful of someone else.  LOLCAT seems on the right side of the line though right?
I personally think LOLCAT is funny, and I'm a native Texan!

I think @mattwynne and @richarda have it perfectly.
By including au/scouse/tx, a reader (and not necessarily an au/scouse/tx reader) could come away with the impression that someone is being mocked, and by extension that the project condones that. As @richarda points out, en-lol is unlikely to convey that impression.
By including au/scouse/tx, the project therefore risks being seen as a place where people might be treated less than respectfully, and the product risks being seen less professional than it would otherwise be.
Even if the project decides to carry that risk by not removing these translations, the effect is wider than just this project. The tech industry benefits from being seen as a respectful place, and small things like this contribute to how the industry is seen.

@rvedotrc - consider also the image that the industry portrays by worrying about trivial matters like this.
I've worked for a University and remember the atmosphere of self censorship where folks were afraid to say anything that might offend anyone on behalf of someone else.
I agree that tech has respect and safety issues, but this sort of thing won't address them, and will likely make the culture worse.

Firstly, stereotypes aren't "exploited" for comic effect, they are simply "used". Stereotypes are exploited for other purposes but we needn't get into that.
Secondly, as an Australian, I am puzzled as to why that anyone thinks my expressions aren't good enough to be used in a translation, humourous or otherwise.
Thirdly, this industry dies have problems with exclusivity and as a person in the privileged position, I shall consent to the removal of stereotypical translations, including my own.

Here are my comments as the contributor of the en-Scouse translation.
Most importantly, if there is actual offense taken - remove them. It's not that important. I had forgotten I'd contributed this.
On being reminded of this I had the same thoughts as I did back then - it's cute and quirky and I don't see a problem with it. Most specifically because:

In my opinion, dialects are something that should be treasured, not stifled. Language is variable and "alive" and its differences should be celebrated.
Any stigma attached to a dialect or accent is not inherent to the dialect - but is purely socially motivated. At least for the Scouse, one could argue that we're doing our bit to make it less stigmatized  ;) (I can't put into words enough how much that last sentence is meant both reasonably seriously and also tongue-in-cheek).
I can only really speak for Scouse since I am a native speaker of it and did my Masters dissertation on aspects of the dialect: the translation is probably not 100% accurate but is fair, based on the common variables used there (pluralisation of "you" done as "youse", variablility of [t] sounds with [r] or nothing for example).
Again, at least for Scouse, there is a fair amount of literature on its variables as well as books like "learn yerself Scouse" (I think books like this exist for most dialects). See point one about celebration of differences.

So, that's my 2cts. I also agree with @delitescere's comments above.

We have established that the Scouse and Australian translations were written by native speakers who are proud of their dialect. Their motivation was to celebrate their dialect.
If anyone is mocking or offending in this matter it must be those who don't take these dialects or translations seriously. It's beyond the scope of this project to make people more tolerant, except for celebrating linguistic diversity.
The Scouse and Australian translations will remain. I have removed Texan (cucumber/gherkin@0e9322ae9e71c54590b062e4bedc812fd4c3b58c), but I'd welcome a new translation by a native speaker of that dialect.
Aslak


Can't rearrange Corp specs and total damage correctly (maybe fixed already)

From a Discord discussion:
Gamer1120: I asked Faux why he preferred OSBuddy over RuneLite for Corp, and this was his answer: https://clips.twitch.tv/ResoluteCrowdedPelicanYouDontSay (basically likes the spec counter better and can set the dark core to click-through)
FluffyRabbit: he was having trouble positioning it when he first tried it
Gamer1120: Does anyone have the VOD or clip of that?
FluffyRabbit: @Gamer1120 found it https://www.twitch.tv/videos/292173006?t=03h46m06s
Now, I watched Faux struggle a bit with rearranging Corp specs, and this clip seems to sum it up perfectly: https://clips.twitch.tv/WealthyOilyNikudonFutureMan .
Note that this was around 2 weeks ago and might have been fixed already. I have no way of testing this, other than that Faux still uses OSBuddy for Corp.
Relates to #4559

Faux did not understand how snap corners work.

:upside_down_face:


refactor: remove amplify-prompts from transformers

Description of changes

Remove amplify-prompts peer dep from transformers.
Add log buffer to transformers that can then be retrieved later.

amplify-category-api reads log buffer and then logs the messages using amplify-prompts.

I have not removed amplify-prompts from @aws-amplify/graphql-transformer-migrator yet. I will do that in another PR if necessary.
CDK / CloudFormation Parameters Changed

N/A
Issue #, if available

N/A
Description of how you validated changes

Unit testing.

Needs further testing.
Checklist

[x] PR description included
[ ] yarn test passes
[ ] Tests are changed or added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I have not removed amplify-prompts from @aws-amplify/graphql-transformer-migrator yet. I will do that in another PR if necessary.

I don't think that'll be necessary, since the graphql-transformer-migrator should be principally concerned w/ the Amplify state management, not the transformer internals itself.

I added flushLogs because I wasn't sure if there would be a case where the same transformer instance would be used multiple times (potentially keeping previous warnings).


TyperChecker2 fix which ended up as UnionType Table Indexer Support

This was supposed to fix an issue mentioned in the Discord Server. https://discord.com/channels/385151591524597761/906369439262461992/1284683079587336212
It starts with TypeChecker2, however the cause of it is because of two things and I believe that the fix in TypeChecker2 isn't ideal, or maybe is even skipping the cache?
The first one is TypeChecker2. And the second one is because UnionType doesn't "reduce" as props. e.g. some sort of simplify. We'd need an RFC that defines what Syntax UnionType should have when making tables, that is not [indexer] as you can only have one.
I am not sure what seen is for, but I think it's to reduce things getting recomputed or something, not sure.

type unionType = "A" | "B" | "C"
type Test = {
  [unionType]: number;
}

Make it loop through all the unions when index into Test through Assign Prop? (But I want to change it to use the Subtyping functionality instead since it has a cache)
Or to add them into the props of the TableType upon NameConstraint dispatch or something.
type Test = {
  A: number, B: number, C: number
}

This is what I was thinking about. And currently it loops. 🤷
But it's only if you use a UnionType as an indexer.
This also means that keyof works!

The thing is Luau only wants one table indexer. What's funny is that we can sorta have multiple purely with Union Types!
Performance can be questioned though.
index<> doesn't have any issue and can index without any problems. But TypeChecker2 didn't know about the functions and I didn't want to include any Headers because I am unsure if anyone would of want more Header Files being included at certain places.

I do feel like that there's been maybe two or more functions doing the same thing instead of SOLID Principle.

welp this one has issues with the unit tests compared to when I built it in Studio

ye it built but it failed the Unit Test compared to when in Visual Studio
but it doesn't error on the other ones compared for me in Visual Studio

it's because I didn't test with fflags=true

This PR though: https://github.com/luau-lang/luau/pull/1418

Thanks for the contribution!
The correct way to fix this is to use the isSubtype function to do a proper subtype test rather than to manually take the type apart.
                TypeId givenType = module->internalTypes.addType(SingletonType{StringSingleton{prop}});
                if (isSubtype(givenType, indexType, NotNull{module->getModuleScope().get()}, builtinTypes, *ice))
                    return {NormalizationResult::True, {tt->indexer->indexResultType}};

I've already written a fix.  It should be available with the next OSS sync.


Straka/input check

This PR adds input sanitization for GT elements in aggregate and finalize, as the underlying arkworks trait Field does not enforce being the in correct prime order subgroup.

@mstraka100 can we add a quick negative test to this (i.e. a test to show that finalize and aggregate reject bad input)?


Auto rollback

Please read https://github.com/etcd-io/etcd/blob/master/CONTRIBUTING.md#contribution-flow.

/retest


Vulnerability roundup 85: php-7.3.16: 1 advisory [5.3]

search, files

[ ] CVE-2019-11048 CVSSv3=5.3 (nixos-20.03)

Scanned versions: nixos-20.03: a84b797b28e. May contain false positives.
Cc @etu
Cc @globin

See also: #88380

Fixed in 7.4.6, 7.3.18, and 7.2.31

merged - closing


Pre-processing pipeline contains incorrect code

Code in the pre-processing pipeline is incorrect; it's machine specific and contains extraneous cells that aren't related to pre-processing. Code doesn't run on cloud/kaggle.

Lists indented incorrectly; table output is formatted wrong

Commit new notebook with fixed indents and corrected output table


make mixin available as dll

Unfortunately, it's not possible at the moment due to the Nitra limitations.


MM-44722: Checklist improvements

Summary
This PR slightly changes the behaviour of the buttons in the checklist item: the ones for modifying the assignee, the slash command and the due date. In particular:

The buttons that have no value now have a transparent background and a border. This applies to the Run Details page and the RHS.
The rest of the behaviour in the RHS is unchanged.
In the Run Details page, the viewers can only see buttons that do have a value, as before, but now the owner button always shows the full name. There's a bug right now through which viewers can change the assignee, but that's not a regression and will be tackled in a different PR. I created a ticket:
In the Run Details page, the participants see all buttons all the time, regardless of whether they have a value or not.

Check the screenshots below to see the new style.
Screenshots
Viewer mode

Participant mode

Checklist in the RHS is still the same

Ticket Link
https://mattermost.atlassian.net/browse/MM-44722
Checklist

[ ] Telemetry updated
[ ] Gated by experimental feature flag
[ ] Unit tests updated

I'll take a look at those failing tests as soon as possible!


SSHj update URL 404 error

Description
When trying to install/update SSHj (as described here to fix an issue with SSH) it doesn't work. This URL returns a 404 error:
https://dbeaver.io/update/sshj/latest
But this URL works fine:
https://dbeaver.io/update/sshj/
DBeaver Version
Any
Operating System
No response
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

@enekochan Hi, SSHJ now comes preinstalled with all versions of DBeaver.

You can switch it here

Thanks to pointing out to the issue connected with website.
Please, let me know whether you managed to solve your issue with ssh.

Thank you both!
@E1izabeth The ssh issue was related to #19033 and I've updated to early access version to fix it.
Should I close the issue then?

Thank you for response.
Yes please close the issue then.


add support for azure vnetResourceGroup

Corrects https://github.com/kubernetes-incubator/kubespray/issues/2120 & https://github.com/kubernetes-incubator/kubespray/issues/2247

CLA should be signed @k8s-ci-robot

ci check this

ci check this