swift-2.0/iOS 9 - Can't set headers in session.configuration.HTTPAdditionalHeaders

I'm using the swift-2.0 branch on iOS 9 with Xcode 7 beta 2. When trying to set the shared session's headers, it seems that all values gets dismissed:
Code
var headers = ["User-Agent": "MyUserAgent"]
if let authToken = authToken {
    headers["Authorization"] = "Bearer \(authToken)"
}
Manager.sharedInstance.session.configuration.HTTPAdditionalHeaders = headers
// Breakpoint here

lldb output
(lldb) po headers
▿ 2 elements
  ▿ [0] : 2 elements
    - .0 : "User-Agent"
    - .1 : "MyUserAgent"
  ▿ [1] : 2 elements
    - .0 : "Authorization"
    - .1 : "Bearer XcTp1mg1p8PwQe3KTejkHVGml2ujOsjrQneqkgDKm0iLqv6bGDAfWCJHqSb29D91"

(lldb) po Manager.sharedInstance.session.configuration.HTTPAdditionalHeaders
▿ Optional([Accept-Language: en;q=1.0, Accept-Encoding: gzip;q=1.0,compress;q=0.5, User-Agent: App/com.site.App (<IP_ADDRESS>; OS Version 9.0 (Build 13A4280e))])
  ▿ Some : 3 elements
    ▿ [0] : 2 elements
      - .0 : Accept-Language
      - .1 : "en;q=1.0"
    ▿ [1] : 2 elements
      - .0 : Accept-Encoding
      - .1 : "gzip;q=1.0,compress;q=0.5"
    ▿ [2] : 2 elements
      - .0 : User-Agent
      - .1 : "App/com.site.App (<IP_ADDRESS>; OS Version 9.0 (Build 13A4280e))"

I expected to see the Authorization token as well as User-Agent=MyUserAgent when inspecting the http headers. What's happening here?

Looks like I didn't read the documentation enough:

Modifying Session Configuration

var defaultHeaders = Alamofire.Manager.sharedInstance.session.configuration.HTTPAdditionalHeaders ?? [:]
defaultHeaders["DNT"] = "1 (Do Not Track Enabled)"

let configuration = NSURLSessionConfiguration.defaultSessionConfiguration()
configuration.HTTPAdditionalHeaders = defaultHeaders

let manager = Alamofire.Manager(configuration: configuration)

And from https://developer.apple.com/library/ios/documentation/Foundation/Reference/NSURLSession_class/#//apple_ref/occ/instp/NSURLSession/configuration :+1:

Discussion
Changing mutable values within the configuration object has no effect on the current session, but you can create a new session with the modified configuration object.

So I guess I have to create a new manager with a custom configuration. I'll try that and close the issue if it works as expected.

And it works! Sorry for the noise.

hi, I'm running into the same issue - but not sure I understand the answer.  Does that mean I need to set the manager's headers on every request?  Is the sample code listed the solution?

@mypark You can't change the default http headers of the shared manager, you have to create a new manager with the code above and use it for all your requests. It has the same interface than Manager.

@ldiqual  Thank you so much it resolved the issue

@ldiqual I have the same problem but still doesn't work, this was working on previous version
private func setHeaderToken(token:String){
    var defaultHeaders =    Alamofire.Manager.sharedInstance.session.configuration.HTTPAdditionalHeaders ?? [:]
    defaultHeaders["Authorization"] = "Bearer " + token
    let configuration = NSURLSessionConfiguration.defaultSessionConfiguration()
    configuration.HTTPAdditionalHeaders = defaultHeaders
    let manager = Alamofire.Manager(configuration: configuration)
}

@cesar-oyarzun-m I got the same problem... I try several way and sample, but the "Authorization" header are not added to the request. I "snif' the local request with Charles and I do not see it in the raw header. Do you find a solution? I am on the 3.1.2
thanks

@pdsavard, you need to pass Authorization headers as part of the Request. Not through the NSURLSessionConfiguration. See the README for more info.

@cnoon what are your thoughts on updating the README to more accurately reflect this?

This is not recommended for Authorization or Content-Type headers. Instead, use URLRequestConvertible and ParameterEncoding, respectively.

As @cesar-oyarzun-m said, this used to work despite the recommendation to do otherwise but now it seems as if it's more than that.

IMO the statement is accurate @paulyoung. If you think there's room for improvement, then by all means, please submit and PR and we'll certainly take a look! 👍🏼


Doesn't work on load

When element is in viewport on loading ( initial view ), sometimes it doesn't work. Can't find any 'rule' when this is happening, anyone had similar problem ?

yes, it seems to especially occur on mobile.


feat(fetch/nvd): use NVD API feed

What did you implement:
Fixes #88
Type of change

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

How Has This Been Tested?
$ go-cpe-dictionary fetch nvd
INFO[11-18|14:19:42] Fetching...                              URL=https://github.com/vulsio/vuls-data-raw-nvd-api-cpe/archive/refs/heads/main.tar.gz
INFO[11-18|14:20:33] Fetching...                              URL=https://github.com/vulsio/vuls-data-raw-nvd-api-cpematch/archive/refs/heads/main.tar.gz
INFO[11-18|14:23:03] Inserting new CPEs
1379927 / 1379927 [-------------------------------------------] 100.00% 7341 p/s

Checklist:
You don't have to satisfy all of the following.

[ ] Write tests
[ ] Write documentation
[x] Check that there aren't other open pull requests for the same issue/feature
[x] Format your source code by make fmt
[x] Pass the test by make test
[x] Provide verification config / commands
[x] Enable "Allow edits from maintainers" for this PR
[x] Update the messages below

Is this ready for review?: YES
Reference

(@MaineK00n , just so that you know, I don't use go-cpe-dictionary, so I won't be able to do a functional test. go-cve-dictionary is the only part of vuls.io that I use.)


how to manually download the chromium engine

hi, i just got this problem:
ranslating...[W:pyppeteer.chromium_downloader] Starting Chromium download. Download may take a few minutes.
Traceback (most recent call last):
  File "/home/t/n/.local/bin/deepl", line 8, in <module>
    sys.exit(main())
  File "/home/t/n/.local/lib/python3.8/site-packages/deepl/main.py", line 13, in main
    result = t.translate(script)
  File "/home/t/n/.local/lib/python3.8/site-packages/deepl/deepl.py", line 140, in translate
    return asyncio.get_event_loop().run_until_complete(
  File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "/home/t/n/.local/lib/python3.8/site-packages/deepl/deepl.py", line 145, in _translate
    browser: Browser = await launch(
  File "/home/t/n/.local/lib/python3.8/site-packages/pyppeteer/launcher.py", line 307, in launch
    return await Launcher(options, **kwargs).launch()
  File "/home/t/n/.local/lib/python3.8/site-packages/pyppeteer/launcher.py", line 120, in __init__
    download_chromium()
  File "/home/t/n/.local/lib/python3.8/site-packages/pyppeteer/chromium_downloader.py", line 139, in download_chromium
    extract_zip(download_zip(get_url()), DOWNLOADS_FOLDER / REVISION)
  File "/home/t/n/.local/lib/python3.8/site-packages/pyppeteer/chromium_downloader.py", line 83, in download_zip
    raise OSError(f'Chromium downloadable not found at {url}: ' f'Received {r.data.decode()}.\n')
OSError: Chromium downloadable not found at https://storage.googleapis.com/chromium-browser-snapshots/Linux_x64/588429/chrome-linux.zip: Received <?xml version='1.0' encoding='UTF-8'?><Error>AccessDenied<Message>Access denied.</Message>We're sorry, but this service is not available in your location</Error>.

^C

could you give me some hints how to manually download the engine (like where to put the zip file and so)?
thanks in advance
keep up the good work :)

Are you using Proxy?

no, its just not a rural connection but a server net...
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 04:d4:c4:d2:68:9d brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/32 scope global eno1
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/29 brd <IP_ADDRESS> scope global eno1
       valid_lft forever preferred_lft forever
    inet6 2a01:4f8:231:482b::2/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::6d4:c4ff:fed2:689d/64 scope link
       valid_lft forever preferred_lft forever
$ curl ifconfig.io
<IP_ADDRESS>
$

Chromium downloadable not found at https://storage.googleapis.com/chromium-browser-snapshots/Linux_x64/588429/chrome-linux.zip:
Received

AccessDenied
Access denied.
We're sorry, but this service is not available in your location
.
```

Anyway, this issue depends on not deepl-cli but https://github.com/pyppeteer/pyppeteer.
Please report this to pyppeteer.

thanks, ill do so but first i try
$ tar cfvJ pyppeteer.tar.xz .local/share/pyppeteer

and then scp and untar it over there ;)

btw, work around doing
tar cfvJ pyppeteer.tar.xz .local/share/pyppeteer

copying to the other system and then doing
tar xfvJ /tmp/pyppeteer.tar.xz

worked fine ;)


Crash with --in and missing "module" declaration

From fstarlang/fstar-mode.el#12:
$ bin/fstar.exe --in
#push
type t = T
#end

Unexpected error; please file a bug report, ideally with a minimized version of the source program that triggered the error.
Failure("Unset current module")

I think this is part of https://github.com/FStarLang/FStar/issues/344, too (I didn't realize when looking at the original report)

This does not apply anymore in neither OCaml nor F# versions :
fstar.exe --in
#push
type t = T
#end
Error: No initial module directive found


Fade VCM toolbar

Provide a description of the new feature / enhancement
Add setting to have the VCM ~notification~ toolbar fade after x seconds.

Good idea

@4x4Strings @crutkas
what notification?

How I took this was the dialog with the mute toggle buttons for webcam / mic

@4x4Strings @crutkas
what notification?

This one:

My main gripe is that as it is there isn't a really good location for it as, since it's clickable, any corner you choose for it something gets blocked.
I think if you had the option for the notification to fade after x seconds, it would be a huge improvement to usability.

@crutkas I wannt merge this with #8705, agree?

yeah, /dup #8705


write a code of conduct which looks exquisite and gives a proper explaination to contributor

read the announcement section
2)read the about of the project
search on google

and make a CODE_OF_CONDUCT.md file for medi-connect repo

Hi @Luson045 I want to work on this issue. Please assign this issue to me.

done 👍

Hi @Luson045 I have done. Kindly review the PR.


security: :lock: security issues

Description
Fix dependabot and  npm audit security issues
Reference

Critical

[x] https://github.com/wrappid/wrappid-app/security/dependabot/8
[ ] https://github.com/wrappid/wrappid-app/security/dependabot/10

Moderate

[x] https://github.com/wrappid/wrappid-app/security/dependabot/2
[x] https://github.com/wrappid/wrappid-app/security/dependabot/4
[x] https://github.com/wrappid/wrappid-app/security/dependabot/5
[x] https://github.com/wrappid/wrappid-app/security/dependabot/6
[ ] https://github.com/wrappid/wrappid-app/security/dependabot/7
[x] https://github.com/wrappid/wrappid-app/security/dependabot/9
[ ] https://github.com/wrappid/wrappid-app/security/dependabot/11
[ ] https://github.com/wrappid/wrappid-app/security/dependabot/12
[x] https://github.com/wrappid/wrappid-app/security/dependabot/13

Fixed possible issues. Remaining will be fixed, when a feasible fix is available. Hence, closing.


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 10:54:29 on 2023.04.22
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 0, errors out: 0
Original problem ID: 19865
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=19865

Problem has been resolved in 3m 0s at 10:57:29 on 2023.04.22
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 19865


Update deployment.md

updated deployment.md to re-enable the download of fake-crypto-material.zip

@chris-zimm Thank you for submitting this PR. Unfortunately you commit is not signed off as it is described by our contributing guideline and enforced by our quality checks (see checks).
Could you please fix this issue in order to allow the PR being merged


use a .gen.go extension

What problem are you facing?
Having all files generated prefixed by zz_generated does not make it easier to understand what they are about when opened in a tree explorer.
How could Terrajet help solve your problem?

terrajet could generate files like .gen.go this convention is already followed by protobuf generator in go to make the distinction between generated files and hand written files.

Hi @remyleone ! We're mostly following the convention of kubebuilder from upstream which uses that prefix for its generated files so that all generated files look similar 🙂

One thing that was not clear is whether or not those files should be kept as it or should they be renamed/edited. What happen if I need to update the jet-generated files? Maybe it would be helpful to add in the header of those generated files if they should be deleted/edited/renamed. In particular it could be really helpful to have a small description/documentation at the top of the files that explain what they mean. I'm not sure to understand what are the differences between deepcopy, managed, managedlist, terraform, and types.

Oh does that notice not appear in your generated files?

// Code generated by terrajet. DO NOT EDIT.

It does appear but I don't understand what this generated code does or the purpose it got. A bit of documentation about why those files are needed and how they work together and interact with the rest of the provider could be useful.


This Week in Information Security - Week of June 1st

Bio:
Charles Neill is a Security Engineer at Rackspace, who tests Rackspace products as well as OpenStack projects like Barbican. He is also a developer on DefectDojo, an open source defect tracking system using the Django framework.
Social Media:
Twitter: @ccneill
Github: cneill
Website: inventropy.us/blog/
Editing Preference:
Feel free to edit as needed.
Posting Preference:
Desired date to publish: June 2nd, 2015
I tried adding some YouTube videos to the mix this week, so that there's more than just text to entice potential readers. Let me know if I've inadvertently gotten the syntax wrong, etc. (I made sure to include my "more" tag this week :blush:  ) Also, I realize the blurbs are pretty long this week for some of the articles I listed, so if you'd like me to trim them down at all, just let me know.
Thanks!

Thanks so much, Cat! I just committed all the suggested edits.

I'll let le @smashwilson look over this.

Pulling into a PR on the deconst-hosted repo presently :wrench:

Dang, it looks like I messed up by naming the post the same as the week before, so clicking the "read more" on the old post takes you to the new one (also, the Disqus comment on the new article is from the old one). What would be the best way to prevent name collisions going forward?

Oh, we'll probably need to do another dual PR to update the title.
I... might be able to write a Jekyll plugin to detect collisions in the future, but I'm swamped for a while, so I'm not sure where that sits on the priority queue...


chore(eslint): amend ecma version

amended ecma version to match with new rules
Signed-off-by: Malcolm Hire<EMAIL_ADDRESS>

Merged into https://github.com/dwp/eslint-config-base/releases/tag/v4.1.0


[Event Change Request] table 38 "Purchase Header" - OnBeforeRecreatePurchLinesHandler

Hello, can you please move the OnBeforeRecreatePurchLinesHandler event before the PurchLineExists() check?
We need this because we have an check for already registred purchase lines and give an error. An exit at this point ist not enough for us.
procedure RecreatePurchLines(ChangedFieldName: Text[100])
    var
        TempPurchLine: Record "Purchase Line" temporary;
        ItemChargeAssgntPurch: Record "Item Charge Assignment (Purch)";
        TempItemChargeAssgntPurch: Record "Item Charge Assignment (Purch)" temporary;
        TempInteger: Record "Integer" temporary;
        TempPurchCommentLine: Record "Purch. Comment Line" temporary;
        TransferExtendedText: Codeunit "Transfer Extended Text";
        ConfirmManagement: Codeunit "Confirm Management";
        ExtendedTextAdded: Boolean;
        ConfirmText: Text;
        IsHandled: Boolean;
    begin
        IsHandled := false;
        OnBeforeRecreatePurchLinesHandler(Rec, xRec, ChangedFieldName, IsHandled);
        if IsHandled then
            exit;
        if not PurchLinesExist() then
            exit;

        IsHandled := false;
        OnRecreatePurchLinesOnBeforeConfirm(Rec, xRec, ChangedFieldName, HideValidationDialog, Confirmed, IsHandled);
        if not IsHandled then
            if GetHideValidationDialog() then
                Confirmed := true
            else begin

You could use the OnBeforeRecreatePurchLinesHandler event instead

I woud like to use the OnBeforeRecreatePurchLinesHandler  event. but befor run the PurchLinesExist() precedure.

Sorry, I mis-read your post.  I understand now and yes moving it to the beginning of the procedure would be needed for your requirement.

This is possibly a breaking change. Some apps could depend on the previous exit from PurchLinesExists().
This request should be new event (e.g. OnRecreatePurchLinesOnBeforePurchLinesExists)


Pass PSP enablement value from rancher chart to webhook chart

Issue: https://github.com/rancher/rancher/issues/40328
Problem

Solution

Testing

Engineering Testing
Manual Testing

Automated Testing

QA Testing Considerations

Regressions Considerations

@KevinJoiner, @crobby, I am a little concerned about this handler code that runs on repo change.
https://github.com/rancher/rancher/blob/9bb8d5674d4f2fe85cca799b07a6d18eee257b9e/pkg/controllers/dashboard/systemcharts/controller.go#L51
https://github.com/rancher/rancher/blob/9bb8d5674d4f2fe85cca799b07a6d18eee257b9e/pkg/controllers/dashboard/systemcharts/controller.go#L74
Not sure I understand what this does, but looks like it will replace one of the inner values map. Thus, PSP inner map would be removed. Should this merge maps instead?

@maxsokolovsky That code is okay because of the code that follows
The desired behavior is to have the system-default-registry set to the setting if the provided chart does not define the global key.
So your comment is mostly correct, except the chart definition overrides the hardcoded value, which is why the PSP setting persists.


Optimize resampling operations

The resampling operations we copied from gridtools are all in a massive monolithic numba-ized function, which has several disadvantages, which I'll try to outline:

Huge functions with deep nesting are unreadable
The entire function needs to be compiled in one go which slows down the initial compile step (takes about ~5 seconds)
The JIT compiler has to validate types and since np.sqrt is apparently only defined for float types all the data must be of float type even for downsampling methods which do not use np.sqrt.

While splitting the huge function into individual functions should only be seen as an initial step towards refactoring this code, it already has two major advantages:

No super long compile step to begin with.
No requirement to cast the input arrays to floats unless using downsampling with standard deviation and variance methods

When running resampling on the landsat data (using mean downsampling) the timings before and after this PR are:
PRE:

Compilation: 6.88 s
Downsampling: 2.58 s

POST:

Compilation: 1.56 s
Downsampling: 1.26 s

Okay, I didn't stop there and enabled numba parallelization. On my machine the results are now:

PRE: 2.58 s
POST (not parallel): 1.26 s
POST(parallel): 0.515 s

Thanks!


Fix integration tests

update s3 config to match latest Trino version
wait for functional processor node instead of /v1/info API

That's really great, Thank you!


Issue with ERR_BUFFER_OUT_OF_BOUNDS

I'm facing an issue related to Kafka,my current service using kafkaJS v1.15.0, written in Nodejs.
Here's the log error the server return.
{"level":"ERROR","timestamp":"2022-05-26T04:26:22.024Z","logger":"kafkajs","message":"[Consumer] Crash: KafkaJSNumberOfRetriesExceeded: Attempt to access memory outside buffer bounds","groupId":"my-group","retryCount":0,"stack":"KafkaJSNonRetriableError\n  Caused by: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds\n    at boundsError (internal/buffer.js:70:11)\n    at Buffer.readInt32BE (internal/buffer.js:468:5)\n    at Decoder.readInt32 (/var/services/bo-consumer-v2/node_modules/kafkajs/src/protocol/decoder.js:50:31)\n    at module.exports (/var/services/bo-consumer-v2/node_modules/kafkajs/src/protocol/recordBatch/v0/decoder.js:43:40)\n    at decodeMessages (/var/services/bo-consumer-v2/node_modules/kafkajs/src/protocol/requests/fetch/v4/decodeMessages.js:27:35)\n    at runMicrotasks (<anonymous>)\n    at processTicksAndRejections (internal/process/task_queues.js:94:5)\n    at decodePartition (/var/services/bo-consumer-v2/node_modules/kafkajs/src/protocol/requests/fetch/v11/response.js:39:13)\n    at Decoder.readArrayAsync (/var/services/bo-consumer-v2/node_modules/kafkajs/src/protocol/decoder.js:179:18)\n    at decodeResponse (/var/services/bo-consumer-v2/node_modules/kafkajs/src/protocol/requests/fetch/v11/response.js:44:15)"}
I debugged into the library and realized if length == 0 then it throws an error

Has anyone faced or know how to solve this problem?

I have had the same problem 🥲

Can you reproduce this in 2.0.1? If yes, please share the raw buffer. The easiest way to get it is probably to put a breakpoint here: https://github.com/tulios/kafkajs/blob/master/src/protocol/requests/fetch/v11/response.js#L48 and then copy the value of rawBuffer. Alternatively, you can run the program with the environment variables KAFKAJS_LOG_LEVEL=debug KAFKAJS_DEBUG_PROTOCOL_BUFFERS=1 KAFKAJS_DEBUG_EXTENDED_PROTOCOL_BUFFERS=1 to log the full Fetch response buffer.
Note that this will include the message data, so only share it if it doesn't contain any sensitive data.

Can you reproduce this in 2.0.1? If yes, please share the raw buffer. The easiest way to get it is probably to put a breakpoint here: https://github.com/tulios/kafkajs/blob/master/src/protocol/requests/fetch/v11/response.js#L48 and then copy the value of rawBuffer. Alternatively, you can run the program with the environment variables KAFKAJS_LOG_LEVEL=debug KAFKAJS_DEBUG_PROTOCOL_BUFFERS=1 KAFKAJS_DEBUG_EXTENDED_PROTOCOL_BUFFERS=1 to log the full Fetch response buffer.
Note that this will include the message data, so only share it if it doesn't contain any sensitive data.

Yes , i've changed version to 2.0.1 and debug into the path you sent.
and got the rawBuffer
I couldn't upload the file so I posted it directly on google drive, I hid some sensitive information, please review it
https://drive.google.com/file/d/1RhK5-q-vVpzLBHYP8pDso68JZ9xpq9MD/view?usp=sharing

I have had the same problem, Waiting for the experts

interesting problem, waiting for the experts

Encountered this issue with 2.2.0, when reverting to 1.16.0, it works just fine.

Have the same issue with 1.16.0

Have a similar issue (i.e., ERR_BUFFER_OUT_OF_BOUNDS with v2.2.3) but the stack trace is not exactly the same as below:
    throw new ERR_BUFFER_OUT_OF_BOUNDS();
    ^

RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds
    at new NodeError (node:internal/errors:393:5)
    at boundsError (node:internal/buffer:84:11)
    at Buffer.readInt32BE (node:internal/buffer:482:5)
    at Decoder.readInt32 (<my-project-dir>/src/node_modules/kafkajs/src/protocol/decoder.js:52:31)
    at Connection.processData (<my-project-dir>/src/node_modules/kafkajs/src/network/connection.js:526:38)
    at Socket.onData (<my-project-dir>/src/node_modules/kafkajs/src/network/connection.js:184:14)
    at Socket.emit (node:events:513:28)
    at addChunk (node:internal/streams/readable:324:12)
    at readableAddChunk (node:internal/streams/readable:297:9)
    at Readable.push (node:internal/streams/readable:234:10) {
  code: 'ERR_BUFFER_OUT_OF_BOUNDS'
}

Did anyone find any solution for this?

Anyone has a solution. ? It happens in my consumer.
I cant really reproduce it happens very rarely , usually during some kind of network issue.
Actaully the second best could be if I can find a graceful way to catch this exception somehow.
A workaround I am also looking for is is there any event I can hook on to in the consumer itself. to catch this exception myself.
I checked the  consumer event.CRASH event but I see it doesnt catch it.
but maybe there is some other way to catch this within the consumer context . I couldnt find a way .
I can easily reproduce the exception using a flag and directly modifying this.offset to exceed buffer length. just so that I can check the stack and see if there is a way to catch the exception gracefully (some hook in the consumer) , but no luck. consumer doesnt seem to have any event I can hook on to but maybe Im wrong.
below is the code I use to throw the exception.
readInt32() {
if(throwMe){
this.offset = this.buffer.length + 4;
}
const value = this.buffer.readInt32BE(this.offset)
this.offset += INT32_SIZE
return value
}

Hi
Looking at the code , I can see that the ONLY way we can get this exception is if somehow the data is corrupted or invalid.
and if expectedResponseSize  < 4 somehow due to invalid data in the buffers. (connection.js)
const expectedResponseSize = decoder.readInt32()
if  expectedResponseSize < 4 will continue the flow but then we will reach the line 429
const correlationId = response.readInt32()
and since the buffer size < 4 it will crash.
Soo .... I think there should be some data integrity validation to make sure we don't get an invalid expectedResponseSize value.
In this case , not sure how to handle but for sure we must close the connection or something since the stream has lost its integrity.

Hi,
I have created a simple kafka consumer using kafkajs. Getting the same ERR_BUFFER_OUT_OF_BOUNDS. I want to create a simple consumer which fetches data from kafka.
Kafka Consumer code:-
consumer.ts
`import 'dotenv/config';
import { Kafka, type KafkaMessage, logLevel } from 'kafkajs';
import { nanoid } from 'nanoid';
const brokers = process.env.KAFKA_BROKERS
? process.env.KAFKA_BROKERS.split(',')
: ['localhost:9092'];
const topic = process.env.KAFKA_TOPIC ? process.env.KAFKA_TOPIC : 'breeze-logs';
let isConnected = false;
if (brokers.length === 0) {
console.log('Kafka brokers not found');
}
if (topic === '') {
console.log('Kafka topic not found');
}
const kafka = new Kafka({
brokers: brokers,
logLevel: logLevel.DEBUG,
clientId: nanoid()
});
const consumer = kafka.consumer({ groupId: 'my-group', maxBytesPerPartition: 1024 * 1024 });
consumer.on('consumer.connect', () => {
isConnected = true;
console.log('kafka consumer connected');
});
consumer.on('consumer.disconnect', () => {
isConnected = false;
console.log('Kafka consumer disconnected');
});
consumer.on('consumer.crash', () => {
console.log('Kafka consumer Crashed');
});
export async function handleMessage(message: KafkaMessage){
console.log(Kafka consumer received message: ${message.value});
};
if (!isConnected) {
try {
await consumer.connect();
} catch (e) {
console.log('Kafka consumer error connecting the consumer: ', String(e));
}
}
export async function runKafkaConsumer() {
try {
await consumer.subscribe({ topic });
await consumer.run({
eachMessage: async ({ message }) => {
handleMessage(message);
}
});
} catch (e) {
console.error('Kafka consumer error running consumer:', String(e));
}
}
`
running kafka consumer in hooks
try{   runKafkaConsumer(); }catch(e){   console.log("running kafka consumer", String(e)); }
can someone please help with the same

in  v1.16.0 it works correctly


[Eve] Make abstract base class decorator

Description
Try contributing to eve by attempting to address a TODO.

Yes, I don't like it that much either. I quickly took a stab at what seemed like a long-standing TODO in the code. I'll take the other approach.


Is there a way to get school vacation ?

Days off are great, but holidays may also be understood as school vacation. did someone already spend some time on this topic ?

Hi,
thank you.
Nope. Unfortunately I think it's not feasible, because school days (and vacations) are set on year basis with no specific logic.


Use show instead of writemime.

Closes #17. No test changes.

[Current coverage][cc-pull] is 93.29%

Merging [#18][cc-pull] into [master][cc-base-branch] will decrease coverage by 1.17%

@@             master        #18   diff @@
==========================================
  Files            15         16     +1
  Lines           325        343    +18
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            307        320    +13
- Misses           18         23     +5
  Partials          0          0

Powered by Codecov. Last updated by [7cdc04c...0ba8556][cc-compare]
[cc-base-branch]: https://codecov.io/gh/TotalVerb/Currencies.jl/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/TotalVerb/Currencies.jl/compare/7cdc04c4bae73bddb314455e32b9bf5b36a9743d...0ba855609cba706eb46d8defd179b5ea591e24d9
[cc-pull]: https://codecov.io/gh/TotalVerb/Currencies.jl/pull/18?src=pr

Coverage decreased (-2.7%) to 91.714% when pulling d654486da34ebe3bedfea82fa4ca22da4ef3b702 on writemime into 7cdc04c4bae73bddb314455e32b9bf5b36a9743d on master.

Coverage decreased (-0.05%) to 94.412% when pulling 5436e6e316c23662520da5623a26b4863e3e08ff on writemime into 7cdc04c4bae73bddb314455e32b9bf5b36a9743d on master.


ERROR  TypeError: Cannot read property 'getEnforcing' of undefined, js engine: hermes
ERROR  TypeError: undefined is not an object (evaluating '_TurboModuleRegistry.default.getEnforcing')
I tried only on the Android with the:
newArchEnabled=false
hermesEnabled=true
"@dongminyu/react-native-step-counter": "^0.1.16",
"react-native": "0.71.7", also on another project with "react-native": "0.71.8",
So the project is running and is not throwing any error until I import this library into a file.
And from the errors that I saw, I think that all are related to this: export default TurboModuleRegistry.getEnforcing('RNStepCounter') as Spec;
I tried to clean everything possible and since the project is running I don't think that is a link problem.
From what I read on react-native Turbo Native Modules is working only with the new architectures. And I see that you mentioned on README that library compatible with both new and legacy architectures
Can you please help me?

hello.
@aluxmanu How are you?
I'm happy to announce that I've fixed an error in the library that I found thanks to you, so I committed it on last Saturday, self-tested it, and released a minor version update today.
As this is my first React Native module, there were a few small and big issues that I found and fixed quickly, and the error you reported was an issue with the critical logic of interfacing the android/src/newarch/StepCounterSpec.kt file and the android/src/oldarch/NativeStepCounterSpec.kt file as an interface, and we fixed the error by organizing the scattered namespaces of RNStepCounter, StepCounter, etc.
that were causing some issues.
In my experience developing open source libraries, it's very rewarding to receive and incorporate feedback like this.
Thanks for reporting the first issue!!! Feel free to reopen this issue if you see any other issues that follow this, or open a new issue if you encounter any other errors!
p.s. the whole ChangeLogs are here!! Release Notes
https://www.npmjs.com/package/@dongminyu/react-native-step-counter/v/0.2.0?activeTab=versions

Hi again @AndrewDongminYoo.
I manage to pass the rnx-align-deps error just by removing it the library from the package.
And I tested again this issue and now i get this error:
 ERROR  Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'StepCounter' could not be found. Verify that a module by this name is registered in the native binary., js engine: hermes

But this time i get this error when I try to use any methods. Last time I was getting this error directly when i was importing the package.
Also, another thing noticed at the import I get this:
Cannot find module '@dongminyu/react-native-step-counter' or its corresponding type declarations
But from what I see you do type-checking so maybe you can have a look at this too.
Thank you for your help with those problems!

@AndrewDongminYoo any updates?


Feature request: resolve latest version of Bazel from something other than GitHub's APIs

In #18 it was mentioned that Bazelisk can fail because GitHub will rate limit IPs, which can be a problem on shared networks.
{
    "message": "API rate limit exceeded for <IP_ADDRESS>. (But here's the good news: Authenticated
    requests get a higher rate limit. Check out the documentation for more details.)",
    "documentation_url": "https://developer.github.com/v3/#rate-limiting"
}

We hit this in our office because we generate our WORKSPACE in our non-Bazel build (as we migrate) and sometimes users do a clean build which deletes this file. Bazelisk will only use .bazelrc if it's beside a WORKSPACE file.
Our fix is to generate our Bazel build before invoking Bazel, which is totally reasonable/the right thing for us. It would still probably be good for Bazelisk to use non-GitHub infrastructure for resolving the latest version, as mentioned in #18 (it would have hidden our bug, which would suck for us, but it seems like the right thing for Bazelisk).

@fweikert Can we reuse your logic that gets the latest RC from GCS also for this case?
@j3parker Sorry for the trouble! We'll fix this. :) It looks like you found a solution for your use case for now, but in case you need another workaround - if you have an API token, you could set the BAZELISK_GITHUB_TOKEN environment variable, and Bazelisk should use it to query the API.

Ah it's no trouble for us. The loud failure was helpful :) If this issue were already implemented we would have potentially silently downloaded a more up to date version of Bazel than we needed. So I think we were doing things wrong.
The token thing is nice, thanks! I think we won't need it but I'll keep it in mind.

Would it be sufficient to write a cronjob/cloud function that mirrors the JSON file on GCS once a day or so, and point bazelisk to the GCS URL by default?

Another motivation for this is that GitHub hasn't been the most stable. Perhaps GCS with a GitHub fallback could be awesome?

@Yannic : it should be possible to retrieve the latest version from the GCS bucket layout, which means we don't need an additional json file.
GitHub has been a single point of failure in the past. Even if we fix the version resolution we should have a look at "bazelisk --migrate" which currently requires GitHub, too.

From our experience, even with the recent GitHub downtime, mirror.bazel.build is consistently worse than GitHub, we get many download failures from it per day, where as with GitHub we only ever get them during known downtime

One possibility is to prefer one, but use the other as a fallback. More complicated, but more robust.

@keith : What exact error do you get? If there's a problem with the mirror we should fix it.

WARNING: Download from https://mirror.bazel.build/openjdk/azul-zulu11.2.3-jdk11.0.1/zulu11.2.3-jdk11.0.1-linux_x64.tar.gz failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException Checksum was faf80bb9a40c6fb6c14cba12b5727bbe6c817bc0e7bc4f6991428250754a803b but wanted 232b1c3511f0d26e92582b7c3cc363be7ac633e371854ca2f2e9f2b50eb72a75
ERROR: An error occurred during the fetch of repository 'remotejdk11_linux':
   java.io.IOException: Error downloading [https://mirror.bazel.build/openjdk/azul-zulu11.2.3-jdk11.0.1/zulu11.2.3-jdk11.0.1-linux_x64.tar.gz] to /root/.cache/bazel/_bazel_root/69693e54603dc2f7d82afd5028699a20/external/remotejdk11_linux/zulu11.2.3-jdk11.0.1-linux_x64.tar.gz: Checksum was faf80bb9a40c6fb6c14cba12b5727bbe6c817bc0e7bc4f6991428250754a803b but wanted 232b1c3511f0d26e92582b7c3cc363be7ac633e371854ca2f2e9f2b50eb72a75
ERROR: /root/.cache/bazel/_bazel_root/69693e54603dc2f7d82afd5028699a20/external/bazel_tools/tools/jdk/BUILD:494:1: @bazel_tools//tools/jdk:remote_jdk11 depends on @remotejdk11_linux//:jdk in repository @remotejdk11_linux which failed to fetch. no such package '@remotejdk11_linux//': java.io.IOException: Error downloading [https://mirror.bazel.build/openjdk/azul-zulu11.2.3-jdk11.0.1/zulu11.2.3-jdk11.0.1-linux_x64.tar.gz] to /root/.cache/bazel/_bazel_root/69693e54603dc2f7d82afd5028699a20/external/remotejdk11_linux/zulu11.2.3-jdk11.0.1-linux_x64.tar.gz: Checksum was faf80bb9a40c6fb6c14cba12b5727bbe6c817bc0e7bc4f6991428250754a803b but wanted 232b1c3511f0d26e92582b7c3cc363be7ac633e371854ca2f2e9f2b50eb72a75

We see many errors along these lines


Accept '-F' and '-framework' flags

For OS X -F and -framework flags need to be accepted and translated into into -L framework=...  and -l framework=..., respectively.
The -F option needs to be added to rustc before, see rust-lang/rust/#20259.

Do you have an example of a pkg-config file which prints out -F or -framework? Just something to test out on.

Sure, I encountered this with the Qt5 packages I installed with homebrew.
$ pkg-config --libs Qt5Core
-F/usr/local/Cellar/qt5/5.4.0/lib -framework QtCore


Whether the Extension attribute of the ACL is optional or mandatory

Problem
Whether the Extension attribute of the ACL is optional or mandatory
Extension is mandatory in [TC-ACL-1.1] of Draft_SVE2_TestPlanVerificationSteps
However display in Access Control cluster.xml is optional

This is optional in the spec.  Filed https://github.com/CHIP-Specifications/chip-test-plans/issues/2103 on the verification steps.

closing the issue as the PICS updated in the test plan


Phonegap plugin push for phonegap build app

Hello, i'm trying to integrate Push Notification functionality to my app build with phonegap build.
I've added the plugin
<preference name="android-build-tool" value="gradle"/>
<plugin name="phonegap-plugin-push" source="npm"  spec="1.7" >
     <param name="SENDER_ID" value="XXXXXXX" />
</plugin>

in my config.xml
And the code:

var push;
try {
push = PushNotification.init({ "android": {"senderID": "XXXXXX"}});
}
catch (error) {
alert(error.message)
}
in the "ondeviceready" event of my index.js

When i generate the apk on PhoneGap Build, everything is fine, but when i install it on my device, the catch section of my code give me an alert with "PushNotification is not defined".
I've tried everything, but with no success.
Can u please help me?
Thank you very much.

Why 1.7 exactly?

@MooUser yeah, that spec looks invalid. PGB probably can't find a version 1.7 and thereby does not include it in your app. Use a valid semver in your spec like 1.7.0 for instance.

Version 1.7 was just a try... before that i put also version 1.8.4 which was the suggested value to use.

Hi everybody: after multple attempts, finally i had my registrationID. Thanks to @macdonst  and the first section of his workshop available at http://macdonst.github.io/push-workshop/
Maybe this page will help some people having the same trouble.
I think i will close this question and maybe i will open another one about sending custom notification, instead of using the FCM Notification panel.
Thank you so much for your interesting.


Using two DrawAtlas with original image and manipulated from it makes performance issue.

The problem
Using two drawAtlas with atlas and manipulated from it at the same time gets performance issue.
Drawing either the original image or manipulated not at the same time has no performance loss.
But drawing both simultaneously impacts performance significantly.

It doesn't make changes whether using drawAtlas or drawRawAtlas.

How to reproduce

Load an image and draw it by drawAtlas(). You cannot see the issue yet.
Flip the loaded image horizontally or manipulate it and then draw it by drawAtlas().
You can see the jank. Switching the order from (1 => 2) to (2 => 1) also has a jank.

Reproducible repo

https://github.com/Hwan-seok/flutter_draw_atlas_performance_issue
You can see the issue more dramatically after adjusting the slider to around 4000~6000(it depends on testing devices' performance).

Video of the performance issue
https://user-images.githubusercontent.com/38072762/217324247-954659dc-fa26-4990-af8f-d833a706119a.mp4

Target Platform: Reproduced on both Android and iOS. I cannot confirm others.
Target OS version/browser: Tested on Android 11, 12, and 13. Also iOS 14, 15, and 16.
Devices: Simulator, emulator, Galaxy Z flip 3, Galaxy S 10, 20, Galaxy A30, iPhone 12 mini, and iPhone 14 pro.
Logs

Logs

No issues found! (ran in 1.1s)

[✓] Flutter (Channel master, 3.8.0-6.0.pre.18, on macOS 12.6 21G115 darwin-arm64, locale ko-KR)
    • Flutter version 3.8.0-6.0.pre.18 on channel master at
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision e8eac0d047 (2 hours ago), 2023-02-07 18:21:18 +0200
    • Engine revision b67690f696
    • Dart version 3.0.0 (build 3.0.0-204.0.dev)
    • DevTools version 2.21.1

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at
    • Platform android-33, build-tools 32.1.0-rc1
    • Java binary at:
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

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

[✓] Android Studio (version 2021.3)
    • Android Studio at
    • 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.13+0-b1751.21-8125866)

[✓] Android Studio (version 2021.3)
    • Android Studio at
    • 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.13+0-b1751.21-8125866)

[✓] IntelliJ IDEA Ultimate Edition (version 2022.2.4)
    • IntelliJ at
    • 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

[✓] IntelliJ IDEA Ultimate Edition (version 2022.2.4)
    • IntelliJ
    • 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

[✓] IntelliJ IDEA Ultimate Edition (version 2022.2.3)
    • IntelliJ at
    • 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

[✓] VS Code (version 1.75.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.58.0

[✓] Connected device (4 available)
    • SM F711N (mobile)           • R3CRC0329PF   • android-arm64  • Android 13 (API 33)
    • sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64  • Android 13 (API 33) (emulator)
    • macOS (desktop)             • macos         • darwin-arm64   • macOS 12.6 21G115 darwin-arm64
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 109.0.5414.119

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

• No issues found!

@Hwan-seok, thanks for your report. This issue is reproducible on the latest stable and master channels with provided sample code.
I'm testing this on Realme 6, Android 11.
Attaching the timeline trace JSON file here: dart_devtools_2023-02-08_15_55_40.698.json.zip

Demo recorded video
https://user-images.githubusercontent.com/104349824/217483028-6ea02198-e86a-4e36-bf08-a9e6cb38667c.mp4

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.7.1, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.7.1 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7048ed95a5 (11 hours ago), 2023-02-01 09:07:31 -0800
    • Engine revision 800594f1f4
    • Dart version 2.19.1
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio Dolphin 2021.3.1.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

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

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio Dolphin 2021.3.1.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.13+0-b1751.21-8125866)

[!] Android Studio (version 2022.1)
    • 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
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • 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

[✓] VS Code (version 1.74.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.58.0

[✓] Connected device (4 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D                         • android-arm64  • Android 11 (API 30)
    • iPhone (mobile)  • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.7.2 19H218
    • macOS (desktop)  • macos                                    • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)     • chrome                                   • web-javascript • Google Chrome 109.0.5414.119

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

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.8.0-7.0.pre.23, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.8.0-7.0.pre.23 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6e7f580370 (6 minutes ago), 2023-02-08 12:37:24 +0800
    • Engine revision f310ffd146
    • Dart version 3.0.0 (build 3.0.0-204.0.dev)
    • DevTools version 2.21.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

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

[✓] Android Studio (version 2022.1)
    • 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.15+0-b2043.56-8887301)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • 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

[✓] VS Code (version 1.75.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.58.0

[✓] Connected device (4 available)
    • SM T225 (mobile)       • R9JT3004VRJ                          • android-arm64  • Android 13 (API 33)
    • iPhone 14 Pro (mobile) • AB2EBB55-6852-40A7-9A12-057128370920 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-1 (simulator)
    • macOS (desktop)        • macos                                • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 110.0.5481.77

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

! Doctor found issues in 1 category.

I was able to reproduce this on a Pixel 3.
Performance drops significantly when drawing one atlas if the atlas size is set to the maximum on the slider.  Performance also drops when drawing both atlases if the atlas size slider is set to a value around 4000.
This occurs because the atlases are exceeding the size of Skia's resource cache.
When this happens, most of the time is spent in a call to glTexSubImage2D for a large texture.  Each frame's call to the Skia drawAtlas operation is going through a GrMakeCachedBitmapProxyView code path that creates this texture and places it in a cache.
However, a later call to GrResourceCache::purgeAsNeeded may remove some of the textures if the cache's size exceeds its limit.
In the two atlas scenario, each of the textures alone can fit within the cache, but the combined size of both textures does not fit.  After each frame, GrResourceCache::purgeAsNeeded then deletes one of the textures.  So on the next frame, that atlas has a cache miss and its texture needs to be rebuilt.  This pattern repeats on every frame.

Also, while profiling this app I noticed that ComplexityCalculatorHelper::drawAtlas was taking a nontrivial amount of time.
On every frame ComplexityCalculatorHelper::drawAtlas is trying to calculate the cost of each rectangle in the atlas.  For an atlas with thousands of rectangles this can be expensive.
@flar

The cost of each rectangle in the set being ask to draw? I've done this on Flame with Tiled: we produce flipped atlases (if the artist used Tiled and flips individual cells) and we try to use one atlas call.

We could get rid of flipping if there was a way to invert the rectangle, reducing the atlas size.

ComplexityCalculatorHelper::drawAtlas exists to estimate the benefit of raster caching. Since it only needs to be a reasonable estimate, I suspect we could think of something much cheaper to compute, for example count * CostOf(rect[0]).
In that same file (https://github.com/flutter/engine/blob/main/display_list/display_list_complexity_helper.h), I see that there might potentially be a similar issue with long paths in https://github.com/flutter/engine/blob/main/display_list/display_list_complexity_helper.h#L244. cc @dnfield

If we benefit from having a more accurate complexity analysis of paths, we could just do this once when building the path and pass it along to DL.

I suspect, however, that we'd probably be "good enough" by just counting the number of verbs and points in the path though. More expensive verbs have more points. It doesn't quite scale linearly but we could probably more quickly estimate the costs this way.


Proposal: allow to omit return statements and function block

Coming from scala background, I frequently find that I miss few very useful features, which could be added to TypeScript language too. One of them is automated return of a last statement in the functional block. It makes use of functional programming style much more clean.
Consider the example (typescript with react, aka TSX):
        if (this.state) {
            return (

                    { this.state.documents.map(d => { return
{d.name}
; }) }

            );
        } else {
            return (

                    Loading...

            );
        }

If it "was" scala-like it could be written like the following:
        if (this.state) {

                { this.state.documents.map(d =>
{d.name}
); }

        } else {

                Loading...

        }

Or this example:
        snapshot(() => {
            const readmePath = require('./blog/idx-meta.jsn');
            return fetch(readmePath)
                .then(response => {
                return response.text();
            }).then(text => {
                return JSON.parse(text) as (Metadata & Name)[];
            });
        })

would look like the following:
        snapshot(() => {
            const readmePath = require('./blog/idx-meta.jsn');
            fetch(readmePath)
                .then(response => response.text())
                .then(text => JSON.parse(text) as (Metadata & Name)[]);
        })

Notice no returns and additional {} brackets for one-liner functional blocks. What do you think about this proposal?

TypeScript doesn't change the semantics of existing JavaScript code


Suggest change event flow

Hi.
I suggest change event flow.
The PanRecognizer have "pan(start|move|end|cancel)" and "pan(left|right|up|down)" event. The PinchRecognizer have "pinch(start|move|end|cancel)" and "pinch(in|out)" event.
The "emit" method of Recognizer is fire "pan(start|move|end|cancel)", "pinch(start|move|end|cancel)".The "emit" method of Manager is fire "pan(left|right|up|down)", "pinch(in|out)" .
The "emit" method of PanRecognizer call step is
1. Manager#emit call
2. Recognizer#emit call
So. The event flow of PanRecognizer is "pan(left|right|up|down) -> panstart -> (left|right|up|down) ....-> panend".
The "emit" method of PinchRecognizer call step is
1. Recognizer#emit call
2. Manager#emit call
So. The event flow of PinchRecognizer is "pinchstart -> pinch(in|out) .... -> pinchend -> pinch(in|out)".
Event flow is different from each other. [sample]
I suggest that same event flow.
"pinchstart -> pinch(in|out) .... -> pinchend"
"panstart -> pan(left|right|up|down) ....-> panend"

@runspired This change makes sense to me its what mouse events do. What do you think?

Seems to make sense but I'm on my phone

Looked closer, this is good, and fixes several open  issues

Would fix #824

@arschmitz @runspired
Thank you.


Add metrics to track which clients we're disconnecting from.

Unfortunately we can't dynamically create labels for metrics but we can add some basic logic that can check the peer info and guess at the type of the client.

@macfarla - are we collecting metrics or logs in our latest peering changes around this?


Feature/shared encoder for input

Proposal for fixing #70
It's unittested which seemed to be the best way to check things out. Only the tagging/training is not unittested.
I did not give the option to force reusing (and not caring about new characters...), maybe this is a feature you think could be useful ? (training on two different dataset one smaller than the other ?)

Closed as per #70 discussion: not worth the complication.


HorizontalRule not being exported at the root of components

Detailed description
Cannot pull in HorizontalRule when importing from root of the package
Steps to reproduce the issue

In a React application, install @carbon/ibmdotcom-react
Import the HorizontalRule:

import { HorizontalRule } from '@carbon/ibmdotcom-react';

See import error

This has been addressed in v0.5.1.


Option to always pull image when creating a container

Is your feature request related to a problem? Please describe.
I have a case where my tests should always retrieve the latest image. AFAIK, this library now pulls an image only if it's missing (sort of like docker run --pull "missing" ..., which is the default) but I would like to always pull the image (so it gets the most up to date version of it) before starting the container (like docker run --pull "always" ... does).
Describe the solution you'd like
An option that enables this behavior would be perfect, for example a .WithImagePull(PullType) builder method where PullType could be Missing (default behavior) or Always. Although I am not sure how this could be implemented.
Describe alternatives you've considered
The image pull can be done explicitly before building/starting the container by using Docker.DotNet directly and this would be okay, but testcontainers-dotnet already has support for credential helpers (AFAIK Docker.DotNet does not support that) which I'm trying to take advantage of (since I'm authenticating to a private registry)
How much would this be feasible? Thanks!

An equivalent to the Java withImagePullPolicy would be great.

That's exactly what I've imagined, although I don't have experience with the Java version. I will try to take a look at how it's implemented there and see how I could implement similar feature for testcontainers-dotnet

@BenasB Let us know if you have any questions regarding the Java implementation 🙂


commit Nise51 & Nise52

Models look good. Changes to package-lock.json approved to be in line with package.json.


builder for python2.7-decorator-4.4.1 is failing

Describe the bug
After updatinging my nix-channel from yesterdays 20.03pre to the current 20.03pre nixos-rebuild is failing by not being able to build pythong2.7-decorator.
building '/nix/store/g4lj2f02pqj87vfmy2sypc7k7g8k14sv-python2.7-decorator-4.4.1.drv'...
created 487 symlinks in user environment
building '/nix/store/wq021y7lrk9p1znkqg0slpm0m9mch4av-weechat-bin-env-2.7.drv'...
Sourcing python-catch-conflicts-hook.sh
Sourcing python-remove-bin-bytecode-hook.sh
Sourcing setuptools-build-hook
Using setuptoolsBuildPhase
Using setuptoolsShellHook
Sourcing pip-install-hook
Using pipInstallPhase
Sourcing python-imports-check-hook.sh
Using pythonImportsCheckPhase
Sourcing setuptools-check-hook
Using setuptoolsCheckPhase
unpacking sources
unpacking source archive /nix/store/idhfvc7jkc7gh9b3bqi3q1va87s4ckyg-decorator-4.4.1.tar.gz
source root is decorator-4.4.1
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file decorator-4.4.1/src/decorator.egg-info/top_level.txt
patching sources
configuring
no configure script, doing nothing
building
Executing setuptoolsBuildPhase
building '/nix/store/icmlb4ihii81rav18b1l7vw5avanv6h8-etc-nixos.conf.drv'...
created 9 symlinks in user environment
running bdist_wheel
running build
running build_py
creating build
creating build/lib
copying src/decorator.py -> build/lib
installing to build/bdist.linux-x86_64/wheel
running install
running install_lib
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/wheel
copying build/lib/decorator.py -> build/bdist.linux-x86_64/wheel
running install_egg_info
running egg_info
writing src/decorator.egg-info/PKG-INFO
writing top-level names to src/decorator.egg-info/top_level.txt
writing dependency_links to src/decorator.egg-info/dependency_links.txt
reading manifest file 'src/decorator.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'documentation.pdf'
writing manifest file 'src/decorator.egg-info/SOURCES.txt'
Copying src/decorator.egg-info to build/bdist.linux-x86_64/wheel/decorator-4.4.1-py2.7.egg-info
running install_scripts
adding license file "LICENSE.txt" (matched pattern "LICEN[CS]E*")
creating build/bdist.linux-x86_64/wheel/decorator-4.4.1.dist-info/WHEEL
creating 'dist/decorator-4.4.1-py2.py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it
adding 'decorator.py'
adding 'decorator-4.4.1.dist-info/LICENSE.txt'
adding 'decorator-4.4.1.dist-info/METADATA'
adding 'decorator-4.4.1.dist-info/WHEEL'
adding 'decorator-4.4.1.dist-info/pbr.json'
adding 'decorator-4.4.1.dist-info/top_level.txt'
adding 'decorator-4.4.1.dist-info/RECORD'
removing build/bdist.linux-x86_64/wheel
Finished executing setuptoolsBuildPhase
installing
Executing pipInstallPhase
/build/decorator-4.4.1/dist /build/decorator-4.4.1
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Processing ./decorator-4.4.1-py2.py3-none-any.whl
Installing collected packages: decorator
Successfully installed decorator-4.4.1
/build/decorator-4.4.1
Finished executing pipInstallPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/4d2bxibs9bl4609a298mvbp376hhs6dc-python2.7-decorator-4.4.1
strip is /nix/store/7wy2mifb0igrp9hzf9dzwddadbs7ai7d-binutils-2.31.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/4d2bxibs9bl4609a298mvbp376hhs6dc-python2.7-decorator-4.4.1/lib
patching script interpreter paths in /nix/store/4d2bxibs9bl4609a298mvbp376hhs6dc-python2.7-decorator-4.4.1
checking for references to /build/ in /nix/store/4d2bxibs9bl4609a298mvbp376hhs6dc-python2.7-decorator-4.4.1...
running install tests
no Makefile or custom buildPhase, doing nothing
pythonCatchConflictsPhase
pythonRemoveBinBytecodePhase
pythonImportsCheckPhase
Executing pythonImportsCheckPhase
setuptoolsCheckPhase
Executing setuptoolsCheckPhase
running test
WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox.
running egg_info
writing src/decorator.egg-info/PKG-INFO
writing top-level names to src/decorator.egg-info/top_level.txt
writing dependency_links to src/decorator.egg-info/dependency_links.txt
reading manifest file 'src/decorator.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'documentation.pdf'
writing manifest file 'src/decorator.egg-info/SOURCES.txt'
running build_ext
test_add1 (tests.test.ExtraTestCase) ... ok
test_decorator_factory (tests.test.ExtraTestCase) ... ok
test_no_first_arg (tests.test.ExtraTestCase) ... ok
test_qualname (tests.test.ExtraTestCase) ... ok
test_signature (tests.test.ExtraTestCase) ... ok
test_unique_filenames (tests.test.ExtraTestCase) ... ok
test_gen123 (tests.test.GeneratorCallerTestCase) ... ok
copying path '/nix/store/kxxwb4p4a6gmlm1jbl8isy0gi7z136ih-libgdata-0.17.11' from 'https://cache.nixos.org'...
copying path '/nix/store/7z7vcm1allx3m3cdg0c5k5qh0ig9vhdc-evolution-data-server-3.34.3' from 'https://cache.nixos.org'...
test (tests.test.NoDocumentation) ... **********************************************************************
File "/build/decorator-4.4.1/src/tests/documentation.py", line 50, in tests.documentation.operation1
Failed example:
    operation1()
Expected:
    operation1 is slow
Got nothing
**********************************************************************
1 items had failures:
   1 of   1 in tests.documentation.operation1
***Test Failed*** 1 failures.
FAIL
test_singledispatch1 (tests.test.NoDocumentation) ... ok
test_singledispatch2 (tests.test.NoDocumentation) ... ok
test_c_classes (tests.test.TestSingleDispatch) ... ok
test_mro (tests.test.TestSingleDispatch) ... ok
test_mro_conflicts (tests.test.TestSingleDispatch) ... ok
test_register_abc (tests.test.TestSingleDispatch) ... ok
test_register_decorator (tests.test.TestSingleDispatch) ... ok
test_register_error (tests.test.TestSingleDispatch) ... ok
test_simple_overloads (tests.test.TestSingleDispatch) ... ok
test_wrapping_attributes (tests.test.TestSingleDispatch) ... ok

======================================================================
FAIL: test (tests.test.NoDocumentation)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/build/decorator-4.4.1/src/tests/test.py", line 81, in test
    self.assertEqual(err, 0)
AssertionError: 1 != 0

----------------------------------------------------------------------
Ran 18 tests in 5.651s

FAILED (failures=1)
Test failed: <unittest.runner.TextTestResult run=18 errors=0 failures=1>
error: Test failed: <unittest.runner.TextTestResult run=18 errors=0 failures=1>
builder for '/nix/store/g4lj2f02pqj87vfmy2sypc7k7g8k14sv-python2.7-decorator-4.4.1.drv' failed with exit code 1

Expected behavior
nixos-rebuild switch should be working without an error.
Metadata

system: "x86_64-linux"
host os: Linux 5.4.23, NixOS, 20.03beta377.ebc9620c3f6 (Markhor)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.2
channels(root): "nixos-20.03beta-436.43ab8e86ca6, unstable-20.09pre215333.42f0be81ae0"
channels(matthias): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
attribute:
- python27Packages.decorator
module:

@costrouc

I have no idea what could have changed. I did a nix-channel --update but nix-info -m still returns the same values and now it worked without this error!?


cmd/go: add flag to show only test names, not other -test.v output

I want to be able to show individual tests being run without printing out t.Log messages unless a test fails.  There's currently no way to do that AFAICT.
I use t.Log a lot to write debugging info to make it easier to figure out why tests fail, including dumping server log messages into t.Log.  Printing this out for passing tests makes the output far too noisy.  However, I really value being able to see the list of all individual tests that are run and their execution times.  This can make it easier to look back at old test runs and see if a test has gotten slower over time, etc.
Adding a new flag that'll work like -v for the purposes of showing what tests are run would be super awesome IMO.

Can you pipe the output through grep to filter out the lines you're not interested in?

On 19 Sep 2017, at 06:37, Nate Finch<EMAIL_ADDRESS>wrote:
I want to be able to show individual tests being run without printing out t.Log messages unless a test fails. There's currently no way to do that AFAICT.
I use t.Log a lot to write debugging info to make it easier to figure out why tests fail, including dumping server log messages into t.Log. Printing this out for passing tests makes the output far too noisy. However, I really value being able to see the list of all individual tests that are run and their execution times. This can make it easier to look back at old test runs and see if a test has gotten slower over time, etc.
Adding a new flag that'll work like -v for the purposes of showing what tests are run would be super awesome IMO.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm not completely opposed but it does sound a lot like featuritis to me. Grep is your friend. Let other tools do some of the lifting.

I'd be happy to grep if there's some way to distinguish between log
messages written during a failing test and those written during a passing
test.  I just don't think there's any way to do that.  I'd be happy to be
proven wrong.
On Tue, Sep 19, 2017, 2:31 AM Rob Pike<EMAIL_ADDRESS>wrote:

I'm not completely opposed but it does sound a lot like featuritis to me.
Grep is your friend. Let other tools do some of the lifting.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/21926#issuecomment-330442810, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADCcyLxbGFLQDW2vNffDZKExPAqaQFicks5sj1_WgaJpZM4Pbfhq
.

How about this"
zapf(~/src/tt) % go test -v
=== RUN   TestSucceeding
--- PASS: TestSucceeding (0.00s)
=== RUN   TestFailing
--- FAIL: TestFailing (0.00s)
	test_test.go:10: whoops, about to fail
	test_test.go:11: ker-bham!
FAIL
exit status 1
FAIL	tt	0.006s
zapf(~/src/tt) % go test -v 2>&1 | grep "^=== RUN"
=== RUN   TestSucceeding
=== RUN   TestFailing

Or this
% go test -list Test
TestSucceeding
TestFailing
ok  	tt	0.005s

The former requires me to run my tests twice and still forces me to wade through masses of logs to find log output for the failing tests.  The second mostly works (if I then run go test without -v), it at least gives me the list of tests that'll run, but doesn't give me execution times of individual tests.
I just wish the two features were separated - the "always show logging" and "show individual tests being run".

Once we do machine-readable test output you can split this as many different ways as you want. Let's plan for that instead of adding more control knobs here.


Any change to download from other site other than YouTube?

Hi,
I've just come across this repo - Excellent BTW!
yt-dlp can download from other types of sites, however, when trying with your app is says 'not a valid link'...
Any chance this can be used for other types of site?

At the moment the program is focused on downloading from YT, simply because that's all I need it to do. I haven't even tried to use it for any other site, so I don't know how that compares to the YT usage. I will have to do some research and evaluate how I could evolve the interface to support other sites. I'm also not opposed to adding other features, like a queuing system for example. I don't know when any of that is going to happen, though. Keep an eye on the repo, I guess.

Cool.
yt-dlp seems to be able to recognise video streams from other sites without too much trouble.
E.g.
yt-dlp.exe --list-formats https://vimeo.com/660749181
I forked your repo and attempted to build in the hope that I could simply remove / alter the URL validation. I was unable to get it to build though. I only have the most basic knowledge of C++ I'm afraid. I'll give it another try though at a later date.
Queuing is an excellent idea!
There is a python app available but it seems to be more trouble than its worth to get the application 'portable', and there are paid applications available, but I'm near sure most of them are shipped with virus's / too much adware, so your program is great!

Just removing the link validation doesn't work (I just tried), because the output from yt-dlp is different, and needs to be parsed differently. At first glance, the differences seem to be fairly minimal though, so I might add Vimeo support in the next version!

Ahh...
Of course.
How about.... The option to not render the format list and just use yt-dlp
default? Then it may work on several types of site?
Kind regards,
Jamie
On Sun, 2 Jan 2022, 13:09 ErrorFlynn, @.***> wrote:

Just removing the link validation doesn't work (I just tried), because the
output from yt-dlp is different, and needs to be parsed differently. At
first glance, the differences seem to be fairly minimal though, so I might
add Vimeo support in the next version!
—
Reply to this email directly, view it on GitHub
https://github.com/ErrorFlynn/ytdlp-interface/issues/1#issuecomment-1003713731,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACCL6X6TCIXICVY4VUM43V3UUBFBFANCNFSM5LCVJOYA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

That's a good idea, I'll see what I can do.

is this implemented?

Yes.


[lighthouse] fix formatting for "more info" heading

What's changed, or what was fixed?

fixes formatting for the "more info" heading in each lighthouse audit

Target Live Date: 2017-12-12 (today)

[ ] This has been reviewed and approved by @petele
[x] I have run gulp test locally and all tests pass.
[x] I have added the appropriate type-something label.

R: @petele

Whoops!
There were 20 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/lighthouse/audits/_template.md#L24 - '


Fix fuchsia colour name

Accidentally missed from #208.
Before

After

You can preview this change here:
Built with commit 0c428df2c63b9e932536f44d18de5cb955f8fe4e
https://deploy-preview-221--govuk-design-system-preview.netlify.com


clarify playground url

It wasn't clear to me that playground is at path /playground. Propose to clarify that
Description
Clarify that "playground" is reachable only on path /playground. The existing docs made me thing it would available at http://<host>:3000 since only the port number was mentioned
References
Review Checklist

[x] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[x] I have added tests to validate that the change in functionality is working as expected

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


fix NumberFormatExceptions coming from Vanilla Hammers

This fixes some NumberFormatExceptions on Vanilla Hammers' side. There's still a couple more on DynaGear's side but I'm about to fix those too. These changes should be mirrored in Vanilla Excavators.

thank you thank you


overflow is not working with borderRadius in android.

Is this a bug report?
yes
Have you read the Contributing Guidelines?
yes
Environment
Environment:
OS: macOS Sierra 10.12.6
Node: 7.10.1
Yarn: 0.27.5
npm: 4.2.0',
Watchman: 4.7.0
Xcode: 9.0 (9A235)
Packages: (wanted => installed)
react-native: 0.47.1
react: 16.0.0-alpha.12
Steps to Reproduce
import React, { Component } from 'react';
import { AppRegistry, View } from 'react-native';

export default class BoldAndBeautiful extends Component {
  render() {
    return (
      <View
           style={{width:200, height:200, selfAlign:'center', borderRadius:100, overflow:'hidden'}}
      >
          <View
               style={{width:200, height:200, backgroundColor:'red'}}
          />
      </View>
    );
  }
}
AppRegistry.registerComponent('AwesomeProject', () => BoldAndBeautiful);

Expected Behavior
the red View should be circular  in android.
Actual Behavior
the red View be square in android. overflow is not working.
Reproducible Demo
Use code above

Hi @neilzhengzx
I am also facing same issue

This is a known issue, android doesn't support overflow and won't for the time being. As a workaround you have to apply the border radius to the subview also.


beam search, temperature, video segments

Can someone please help me understand what effect does parameters like beam search, temperature and video segments have on the VQA responses ? Could not find this in the repo or InternVideo/Vchat paper.

For beam search and temperature, they are the hyperparameters for LLM. Here are some descriptions from Bing：

In LLM, beam search is a decoding strategy that generates a set of beam sequences to choose from. Diverse beam search is an extension of the beam search strategy that allows for generating a more diverse set of beam sequences to choose from¹. Temperature is a hyperparameter used in the softmax function that controls the randomness of the output. A higher temperature will generate more random output¹².

¹: Hugging Face
²: GitHub
For the video segment, we use it to control the input frames. Large video segment means inputting more frames.


[Enhancement]: Auto play button in Rock Paper Scissors game

Do you want to have the enhancement of existing game ? 😀 Describe yourself..
An auto play button on click will play automatic moves until the stop play button is pressed.
Describe the solution you'd like
I can create this auto play button which on click plays automatic moves and on clicking again stops the automatic play.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @meetarora10 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @meetarora10 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


[Bug]: Longhorn RWX volumes are not attached

Description
Hi,
I'm using multiple clusters using this solution. Today, suddenly all the Longhorn RWX mounts stopped working in all of my clusters.
Previously I used Longhorn 1.5.1, now I rolled back to 1.4.3 but the same.
This is all I found in the logs:
Oct 11 07:42:23 dev-worker-1 k3s[1294]: Mounting command: /usr/local/sbin/nsmounter
Oct 11 07:42:23 dev-worker-1 k3s[1294]: Mounting arguments: mount -t nfs -o vers=4.1,noresvport,intr,hard <IP_ADDRESS>:/pvc-13538170-4278-4467-b2b0-1f1ba6f54a4c /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/185c34f566c2eca6e8c7c6a2ede2094c076d7d25ddae286dc633eeef80551af0/globalmount
Oct 11 07:42:23 dev-worker-1-autoscaled-small-19baf778f50efd8c k3s[1294]: Output: mount.nfs: Protocol not supported for <IP_ADDRESS>:/pvc-13538170-4278-4467-b2b0-1f1ba6f54a4c on /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/185c34f566c2eca6e8c7c6a2ede2094c076d7d25ddae286dc633eeef80551af0/globalmount

I'm using a self installed longhorn, so it's disabled in the kube.tf, but this is the values.yaml I'm using. This also worked yesterday, so I'd say it's not related to the issue.
ingress:
  enabled: true
  annotations:
    kubernetes.io/tls-acme: "true"
    cert-manager.io/cluster-issuer: "letsencrypt-prod"
  ingressClassName: "nginx"
  host: "longhorn.blabla"
  tls: true
  tlsSecret: longhorn.blabla-tls

longhornManager:
  tolerations:
    - key: kubernetes.io/arch
      operator: Equal
      value: arm64
      effect: NoSchedule
longhornDriver:
  tolerations:
    - key: kubernetes.io/arch
      operator: Equal
      value: arm64
      effect: NoSchedule
longhornUI:
  tolerations:
    - key: kubernetes.io/arch
      operator: Equal
      value: arm64
      effect: NoSchedule
longhornConversionWebhook:
  tolerations:
    - key: kubernetes.io/arch
      operator: Equal
      value: arm64
      effect: NoSchedule
longhornAdmissionWebhook:
  tolerations:
    - key: kubernetes.io/arch
      operator: Equal
      value: arm64
      effect: NoSchedule
longhornRecoveryBackend:
  tolerations:
    - key: kubernetes.io/arch
      operator: Equal
      value: arm64
      effect: NoSchedule
persistence:
  defaultClassReplicaCount: 3
  defaultClass: false
  defaultReplicaAutoBalance: least-effort
defaultSettings:
  taintToleration: "kubernetes.io/arch=arm64:NoSchedule"
  storageOverProvisioningPercentage: 1000
  kubernetesClusterAutoscalerEnabled: "true"
  defaultReplicaCount: 3

Do you have any ideas or advices on how to further debug it?
Kube.tf file
module "k8s" {
  providers = {
    hcloud = hcloud
  }
  hcloud_token = var.hcloud_token
  version = "v2.7.0"

  source = "kube-hetzner/kube-hetzner/hcloud"

  cluster_name = "dev-worker-1"

  ssh_public_key  = file("./keys/id_ed25519.pub")
  ssh_private_key = file("./keys/id_ed25519")

  control_plane_nodepools = [
    {
      name        = "control-plane-fsn1",
      server_type = "cax21",
      location    = "fsn1",
      labels      = [],
      taints      = [],
      count       = 3
    },
  ]

  agent_nodepools = [
    {
      name        = "agent-cpx31",
      server_type = "cpx31",
      location    = "fsn1",
      labels      = [],
      taints      = [],
      count       = 0
    },
    {
      name        = "egress",
      server_type = "cax11",
      location    = "fsn1",
      labels      = [
        "node.kubernetes.io/role=egress"
      ],
      taints = [
        "node.kubernetes.io/role=egress:NoSchedule"
      ],
      floating_ip = true
      count       = 1
    },
    {
      name        = "agent-arm-medium"
      server_type = "cax31"
      location    = "fsn1"
      count = 1
      labels      = [
        "kubernetes.io/arch=arm64"
      ],
      taints = [
        "kubernetes.io/arch=arm64:NoSchedule"
      ],
    },
  ]

  autoscaler_nodepools = [
    {
      name        = "autoscaled-small"
      server_type = "cpx31"
      location    = "fsn1"
      min_nodes   = 0
      max_nodes   = 0
    },
    {
      name        = "autoscaled-medium"
      server_type = "cpx41"
      location    = "nbg1"
      min_nodes   = 2
      max_nodes   = 3
    },
  ]

  network_region = "eu-central"

  load_balancer_type     = "lb11"
  load_balancer_location = "fsn1"

  # Use dedicated load balancer for control plane
  use_control_plane_lb = true

  restrict_outbound_traffic = false

  # Use cilium as CNI as it supports egress nodes
  cni_plugin        = "cilium"
  cluster_ipv4_cidr = local.cluster_ipv4_cidr
  cilium_values     = <<EOT
ipam:
  operator:
    clusterPoolIPv4PodCIDRList:
      - ${local.cluster_ipv4_cidr}
kubeProxyReplacement: strict
l7Proxy: "false"
bpf:
  masquerade: "true"
egressGateway:
  enabled: "true"
extraConfig:
  mtu: "1450"
EOT

  # Install it manually
  enable_longhorn       = false
  # Install prometheus + prometheus-adapter instead
  enable_metrics_server = false
  # Install it manually
  ingress_controller    = "none"

  cluster_autoscaler_extra_args = [
    "--enforce-node-group-min-size=true"
  ]

  create_kubeconfig    = false
  create_kustomization = false

  initial_k3s_channel = "v1.27"
  automatically_upgrade_k3s = false
  automatically_upgrade_os = false

  k3s_exec_server_args = "--kube-apiserver-arg enable-admission-plugins=PodTolerationRestriction,PodNodeSelector"
}

Screenshots
No response
Platform
Linux

@janosmiko You might want to SSH into a node and see the logs. Please refer to the Debug section in the readme.
@aleksasiriski Maybe you would know something about that specific issue?

Hi @mysticaltech ,
I found those logs in the node's journalctl (where the pod that needs the RWX volume). And actually when all the rest is working well (eg: a POD with RWO volume works as expected).

@janosmiko Please have a look if the nfs packages are installed. If not, make sure you are using the latest version of the nodes.
See the packer file how nfs is installed and do the same manually, if that solves it, we would have identified the problem.

Maybe this one is related?
https://github.com/longhorn/longhorn/issues/6857

Same here. Disaster :-/

@janosmiko The upgrade flags are not retroactive, they take effect on the first deployment only. But see the upgrade section in the readme, you can disable it manually.
About the nfs-client, just freeze the version with zypper (via transactional-update shell).

The upgrade flags are not retroactive, they take effect on the first deployment only. But see the upgrade section in the readme, you can disable it manually.

Can these be applied on the autoscaled nodes too?
Eg: I created the cluster with automated upgrades = true, but I want to disable automated upgrades. If I change this in terraform and apply it on the cluster, that will make sure the autoscaled nodes will not be created using automated upgrades and I only have to disable it manually on the already existing nodes?
Freezing the nfs-client can be a good solution for the already existing nodes, but autoscaled (newly created) nodes will be created using the new package version. :/

I reported it here:
https://bugzilla.opensuse.org/show_bug.cgi?id=1216201

@janosmiko Yes you can ssh into autoscaled nodes too. And what you could do is freeze the version at the packer level and publish the new snapshot (just apply packer again, see readme).

@janosmiko @Robert-turbo If you folks can give me the working version of the nfs-client I will freeze it at the packer level. Theses kind of things do not need to get updated often.

@mysticaltech
Working version:
S  | Name                            | Type    | Version                        | Arch   | Repository
---+---------------------------------+---------+--------------------------------+--------+------------------------
i+ | nfs-client                      | package | 2.6.3-39.4                     | x86_64 | (System Packages)

Problematic version:
S  | Name                            | Type    | Version                        | Arch   | Repository
---+---------------------------------+---------+--------------------------------+--------+------------------------
i+ | nfs-client                      | package | 2.6.3-39.5                     | x86_64 | openSUSE-Tumbleweed-Oss

Folks see solution here https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/discussions/1018, and also PR merging right away to avoid this problem in the future.

Should be fixed in v2.8.0 but the image update is needed, please follow the steps laid out in https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/discussions/794.

(The solution was to install and freeze an older version of nfs-client), see the solution linked above for manual fixes).

Hi @mysticaltech ,
Could you reopen this issue and wait for some feedback from real users please? Just asking because it's a critical issue for those who use this in production...
And it still doesn't work. I tested it even by manually pinning the nfs-client version only on all my nodes and the RWX longhorn volumes are still not mounted.
Also, Neil Brown mentioned in the related bugreport that this package update (nfs-client 2.6.3-39.4 -> 2.6.3-39.5) doesn't contain any changes, so the issue must be in another package.
https://bugzilla.suse.com/show_bug.cgi?id=1216201#c2
Also, installing x86-64 package on the arm snapshots will not work.
https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/pull/1026#pullrequestreview-1678861630

@mysticaltech
It looks like downgrading the kernel-default package to 6.5.4-1.1 and a reboot solves the issue.
You don't have to downgrade and pin the nfs-client package.
See the progress in the related bugreport: https://github.com/longhorn/longhorn/issues/6857

Thanks for the details @janosmiko, you are right. Will revert the change to pin the version and wait for more feedback on this issue.

The changes to the base images pinning nfs-client werer reverted in v2.8.1.

@janosmiko As this is a longhorn bug, there is nothing else we can do here, closing for now. Thanks again for all the research and the info.

It's not a Longhorn bug, but actually a bug in the Linux kernel.
For anyone who faces the same issue and wants a real (and tested) solution...
SSH to all your worker nodes and run these commands:
transactional-update shell
zypper install -y --oldpackage https://download.opensuse.org/history/20231008/tumbleweed/repo/oss/x86_64/kernel-default-6.5.4-1.1.x86_64.rpm
zypper addlock kernel-default
exit

touch /var/run/reboot-required

If you'd like to make sure the autoscaled nodes also have this pinned kernel, delete the previous snapshots from hcloud, then modify the packer config with these:
  install_packages = <<-EOT
    set -ex
    echo "First reboot successful, installing needed packages..."
    transactional-update --continue pkg install -y ${local.needed_packages}
    transactional-update --continue shell <<- EOF
    setenforce 0
    rpm --import https://rpm.rancher.io/public.key
    zypper install -y https://github.com/k3s-io/k3s-selinux/releases/download/v1.4.stable.1/k3s-selinux-1.4-1.sle.noarch.rpm
    zypper addlock k3s-selinux
    zypper install -y "https://download.opensuse.org/history/20231008/tumbleweed/repo/oss/x86_64/kernel-default-6.5.4-1.1.x86_64.rpm"
    zypper addlock kernel-default
    restorecon -Rv /etc/selinux/targeted/policy
    restorecon -Rv /var/lib
    setenforce 1
    EOF
    sleep 1 && udevadm settle && reboot
  EOT

and rerun packer init hcloud-microos-snapshots.pkr.hcl && packer build hcloud-microos-snapshots.pkr.hcl
Wait for the images to be built and finally run terraform apply to update the cluster autoscaler config.

Note: @mysticaltech I saw it somewhere else too but it's kinda said it's more important to you to close bug reports asap instead of helping your users who are in trouble and trying to use your project.

@janosmiko Absolutely not, I help the best I can, I even spent a few hours Sunday night implementing a fix you suggested that turned out not to be it. Now the bug is from Longhorn, there is nothing to do on that side but warning about it, hence pinning the issue.

you suggested that turned out not to be it

I haven't suggested that fix, you talked with another guy in the linked discussion about that. But I assume none of you tested if it really works and solves the issue.

there is nothing to do on that side but warning about it

I mentioned a temporary solution in the comment above: https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/issues/1016#issuecomment-1767668561


python3Packages.whirlpool-sixth-sense: unstable-2021-08-22 -> 0.16

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 170023 run on x86_64-linux 1

3 packages failed to build:

home-assistant-component-tests.whirlpool
python310Packages.whirlpool-sixth-sense
python39Packages.whirlpool-sixth-sense


fasterwhisper and whisperx are faster than this repo

Hello, have u tested fasterwhisper and whisperx? https://github.com/guillaumekln/faster-whisper
this lib is way more faster than transformers.

I am sure he has.
Please provide benchmarks comparing faster-whisper and insanely-fast-whisper that support your claim.

also make sure to try with flash attention enabled 😊

Thanks @thomasmol & @patrick91!
@lucasjinreal - We've put up some benchmarks on the README. I didn't get the time to benchmark WhisperX but given it uses faster-whisper backend, I'm assuming we're faster here.
I'm closing this issue for now, feel free to re-open if you have any questions!

So we tuning on hf's transformers like enable flashattn etc, and got faster speed than faster-whisper? Why so many people bother using ctranslate2 to do whisper if transformers got a faster speed?

Because we added it 2 weeks back :)
On Tue 21. Nov 2023 at 03:19, MagicSource @.***> wrote:

So we tuning on hf's transformers like enable flashattn etc, and got
faster speed than faster-whisper? Why so many people bother using
ctranslate2 to do whisper if transformers got a faster speed?
—
Reply to this email directly, view it on GitHub
https://github.com/Vaibhavs10/insanely-fast-whisper/issues/60#issuecomment-1820107948,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEOREKYSUCNN3DJ3IEIBDK3YFQFTVAVCNFSM6AAAAAA7SIGTXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRQGEYDOOJUHA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

If so, we need ask people stop using ctranslate2, it's really messy and very hard to install without pain.

@lucasjinreal we don't need to do anything. You are free to use this repo and stop using ctranslate. Maybe ctranslate has some other benefits or more improvements down the line that would improve its performance. Other people are free to use whatever library or tech they want, you don't have to "ask people to stop" using a certain library.

Yes, but not all people have insights on how it really worked, like me, I just look the stars of repo, if your repo actually faster than faster-whisper,
it would be good thing to higly suggested and highlights the weakness which other libs has when compare.

Feel free to write a blog post or article and publish it comparing different whisper implementations. As mentioned, there are now benchmarks in the readme: https://github.com/Vaibhavs10/insanely-fast-whisper#insanely-fast-whisper comparing faster-whisper with this repo.


HIVE-27286: Upgrade jettison version to 1.5.4 to address CVE-2023-1436

What changes were proposed in this pull request?
Upgrade jettison version to 1.5.4
Why are the changes needed?
To fix CVE-2023-1436
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing tests

@shreeyasand jettison version 1.3.4 is a transitive dependency in tez-api as well, please exclude
Dependency tree:
|  +- org.apache.tez:tez-api:jar:0.10.2:compile
|  |  +- commons-lang:commons-lang:jar:2.6:compile
|  |  +- org.codehaus.jettison:jettison:jar:1.3.4:compile

Nice catch @akshat0395! Otherwise, LGTM

LGTM, +1

@TuroczyX could you please help merge this PR?

@TuroczyX could you please help merge this PR?

@veghlaci05 Could you please review and merge this?

@deniskuzZ @veghlaci05 Could you please merge?

@deniskuzZ @veghlaci05 could you please merge?


ALC  Beijing成员介绍系列之：娟神的成长之路

@tristaZero 有一篇类自传的文章，正在撰写中。
值得广为传播。

I think this issue can close now, the introduce article already public to site.
https://alc-beijing.github.io/alc-site/post/heros_journey_trista/

Hi @lijiangsheng1 , Your contribution made ALC Beijing become prosperous, very appreciated!


Can't build storefront npm.

Noob here...
I am running all latest versions and have been going through all documentation without any luck to resolve my issue. I have seen similar issues but no clear instruction on how to fix.
The furthest I was able to get was here in the VS doc(How to prevent an error "Can’t build storefront npm"):
https://docs.vuestorefront.io/guide/basics/recipes.html#how-to-get-dynamic-prices-to-work-catalog-rules
–which I then followed but still get the same issue as when I try the "easy setup" (https://docs.vuestorefront.io/guide/general/introduction.html#installing-vue-storefront)
I've scoured the forum and anywhere else I can to find a solution... no luck. :(
Problem I am having is that node(correct me if I'm wrong) is failing to build Vue Storefront. I've checked the log file but really am not savvy enough to know what to make of it other than it's failing at the installer script and "There is likely additional logging output above.":
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>installer: node ./core/scripts/installer
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>installer script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Any help would be greatly appreciated. Looking forward to getting this up and running. Thanks!

Please check your node version; it’s hard to say anything more without the logs provided

@DJ-DESIGN Did you get any solution? I am getting same issue.

Ok, thanks. I'm on version: 10.15.1

I had a typo(space) in one of my project directory folder names. Breaking my build. The error log explained it. I'm still learning... Thanks for responding!


chore: update npm-run-all to npm-run-all2

This PR aims to replace npm-run-all which is no longer maintained (https://github.com/mysticatea/npm-run-all - last release November 2018).
The replacement npm-run-all2 can be used as a replacement that is still actively maintained (https://github.com/bcomnes/npm-run-all2 - last release October 2023)

npm-run-all2 why?
A maintenance fork of npm-run-all. npm-run-all2 is a fork of npm-run-all with dependabot updates, release automation enabled and some troublesome babel stuff removed to further reduce maintenance burden. Hopefully this labor can upstream some day when mysticatea returns, but until then, welcome aboard!

Please note that I created this PR semi-automatically across all applicable projects in https://github.com/camunda and https://github.com/camunda-community-hub
Feel free to ping me if you find any issue with it or simply ignore it.

Thanks for your contribution. We don't usually accept automated PR opens as it significantly increases our workload (cf. https://github.com/camunda/camunda-modeler-process-io-specification-plugin/pull/36#issuecomment-1908399233). I'm hence closing this one.


Price Slider Causing Flickering

https://user-images.githubusercontent.com/58960798/177310055-c260a427-ed99-4a99-a4d0-1069770a5dc9.mov

I think it comes from Trend Facet I tried something to change the order of facets and without trends it works:
https://share.getcloudapp.com/QwunL0Je

I think it comes from Trend Facet I tried something to change the order of facets and without trends it works: https://share.getcloudapp.com/QwunL0Je

thank you @VirAlex 🙏