Allow configuring priorityClassName for broker deployment

Describe the feature
Add the ability to configure the priorityClassName for the broker pods. We would like to be able to set the priorityClassName to something other than the default.

[!TIP]
Vote this issue reacting with :+1: or :-1:

@KevinFrommeltAtFanatics you can customize the priorityClassName and other podSpec fields by using a strategic merge patch, for further details see custom mods via a strategic merge patch, i.e.
apiVersion: broker.amq.io/v1beta1
kind: ActiveMQArtemis
metadata:
  name: artemis-broker
spec:
  resourceTemplates:
    - selector:
        kind: StatefulSet
      patch:
        kind: StatefulSet
        spec:
          template:
            spec:
              priorityClassName: high-priority


Transformer fixes 2

This combines:

Speedups to _convert()
Making the maxpool sampling optional and off by default
Restore the old qfit transformer code and C extension
Update map scaling to rely on simple density summation, not FFT
Ligand tests with real data

This is incomplete but we are going to merge with dev to keep all CCTBX in one branch.


Add redirectUri optional parameter to UserAgentApplication and …

…usa a default value for the authority parameter. These changes address this issue with SPAs that don't use hash-based routing.

@austindyoung,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@austindyoung, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

@austindyoung fixed in dev


Refactor if statement

https://github.com/morewings/react-forge-ui/blob/c2f3753efb0f2a0d0e66b2a0beb7a497ae17db87/src/lib/Dialog/Dialog.tsx#L56
if ((event.target as HTMLDialogElement).nodeName === 'DIALOG' && closeOnClickOutside)

:tada: This issue has been resolved in version 0.8.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Improve UX for Discoverability of Disaster Post Clickability

I've had a few people using the app not realize each disaster post on the main posts view was clickable to open a detail view for the disaster.
We can make the disaster post detail view more discoverable by showing a view button or something, maybe have it change color on hover and keep it subtle on non hover if we want to think about mobile and how there is no hover state on mobile devices.

We'll need a stronger signifier on the posts to communicate that affordance.

Pictorial content would be nice, like a mini version of the map. A post heading that appears link-like would also be nice. Maybe a subtle contrast colored button looking thing with an arrow icon or view details text.


Fluid conduit will not connect to Tinker's Construct tank

Minecraft 1.10.0
Forge <IP_ADDRESS>6
EnderCore 1.10-<IP_ADDRESS>
EnderIO <IP_ADDRESS>.0.50_alpha
Tinkers Construct 1.9.4-2.3.3
It stopped working after the fluid changes in Forge for 1.9.4, so it also does not connect in the 1.9.4 build.

see #3375


Error installing remix-auth-github

I am getting error when installing remix-auth-github.
$ npm i remix-auth-github
npm ERR! ERESOLVE could not resolve
npm ERR!
.
.
.
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! remix-auth-github@"*" from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/@remix-run/server-runtime
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/remix-auth-github
npm ERR!     remix-auth-github@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

The peer dependencies need to be updated. Maybe this can coincide with the change to vite.

Also having this issue. Is anyone using this package?

This should be fixed in v1.7.0.


Unexisting pipeline exits silently.

Hello,
When I run dotnet fsi .\build.fsx -p Foobar where the pipeline name does not exist in my build.fsx file, nothing happens.
Though this is fine, I suggest we show a message with pipeline not found, did you mean ....

Yes, we can add that.

@nojaf it is released in 0.3.8

Many thanks!


Arc_test method

Added docstrings and turned arc_test function into a Mantissas Class's method.

Thank you!
I just adapted the color to the general theme.
Hope you keep contributing with nice things.


Global Pause Feature

If this already exists, I'm sorry, but I could not find it in the documentation.
I would like to request for a function that would allow you to instantly pause all existing animations, such as anime.pauseAll(), which can either work as a toggle or just as a pause functionality, as well as anime.resumeAll(), which will conversely instantly resume all existing animations.

I think you can pause all using
https://animejs.com/documentation/#running
anime.running.forEach(a => a.pause());

@web2033 ahh, okay. Thank you!

@web2033 oh, but what about resuming? It seems like they're moved away from anime.running when you pause them?


NTR - fix export of supplier streams

Coverage increased (+0.03%) to 42.217% when pulling 64e4c688e8add6748e054281de844c821a60ae7b on NTR-fix-supplier-streams-on-update into c34ecea38abb68377b3cb85655e9bd9cb450a3c6 on master.


Stacktraces are empty in AWS Lambda

Using the following code in an AWS Lambda running the Go 1.x image (Amazon Linux) the generated output is empty:
stacktrace := sentry.NewStacktrace()
Running the same command on a Mac dev machine returns the expected stack.

Fixed in https://github.com/getsentry/sentry-go/commit/18c90128b8582641e330b23394ed9a68f1586026
Tested manually on AWS and works fine now!

Can you please confirm?

There are no breaking changes for now, but if you want to feel "safer", I'll release beta.2 tomorrow morning :)

Works for me!

@mattcollum https://github.com/getsentry/sentry-go/releases/tag/v0.0.1-beta.2

Trying to test this and not seeing any events at all in Sentry anymore from lambdas. Did something change with flush?   And what's the best approach to using that to ensure all messages make it out before the function ends?

Upped the time on Flush to 1 second and am seeing events again.  Can see stacktraces but they are missing the code snippets that I see when sending from local tests.  Any way to include those?  Getting closer!

@mattcollum it's not possible to extract source files from binaries, as symbol resolutions in go allow to read lines and function names only.
However, we can kinda work around it: https://github.com/getsentry/sentry-go/commit/5d6d24943a90e128155f888e4d82897103f5379b
In order to get the context right, you need to bundle your source code with the binary, eg.
GOOS=linux go build main.go && zip handler.zip ./main ./main.go ./other.go ./sources.go

However, it'll only work if all the files are within the root directory, as we resolve it based on the filename and making it more flexible would require a lot of changes right now (we'll definitely make them if there'll be a huge need for that.

Right that makes total sense. Thanks for the tip, I'll play around with this and see if its worth it for us.

@kamilogorek So was thinking of trying this out and wanted to ensure I read this right.  For this to work we need to flatten out the source code into a single directory and then zip it alongside the go binary?  We have files with the same name in different packages so thinking this might be an issue unfortunately

@mattcollum I agree that it's not ideal, and that's why I'll update how it works this week so you won't have to flatten it anymore. I'll keep you posted.

Awesome as always, thx @kamilogorek

@mattcollum aaand it's released. Update to 0.1.2 and deploy your lambdas with source code included, that's all. Directory structure doesn't matter anymore, so you can even push the whole thing up there.
$ GOOS=linux go build main.go && zip -r handler.zip *

nice!
so the goal here is instead of a straight Go binary that we deploy to lambda, we upload a zip containing the binary and the source code?  we're using serverless so need to weave this into our build/deploy process properly

Correct. There's, unfortunately, no easy way to make it work other than providing source code directly in Go.

Working example:

nice.  trying it now and will lyk

Does it matter how closely it matches your model?  I've got the following in zip
-srcdir1
-srcdir2
-srcdirn
-functions/functionDir/main.go
-bin/app
Zip deploys fine and the Lambda runs but just seeing regular stacktraces with no source.  Could it be the fact I've got the binary in a bin dir as opposed to at the root of the zip?  Is there another setting I need when initializing Sentry maybe that I missed from earlier chats?

@mattcollum it's kinda more complex structure, as what I do right now is that I'm looking for the main frame, assume (blindly) that it's living in the root directory of the project and then try to extract path prefix from it.
I have a better idea now though, so will try to implement it soon.

Got it.  Not pressing so schedule as you see fit but let me know when I should try again

@mattcollum it's done on master. Can you give it a try without a new release? It should read the file content now without any additional config, even with the structure like yours.
There's now also a way to opt-out of this feature if someone doesn't want to have it (eg. for a possible performance boost, as it has to perform I/O operation).
sentry.Init(sentry.ClientOptions{
	Integrations: func(integrations []sentry.Integration) []sentry.Integration {
		var filteredIntegrations []sentry.Integration
		for _, integration := range integrations {
			if integration.Name() == "ContextifyFrames" {
				continue
			}
			filteredIntegrations = append(filteredIntegrations, integration)
		}
		return filteredIntegrations
	},
})

Let there be stacktraces!  Nice work :)

Woohoo! Will release 0.1.3 now then :) Thanks for a quick turnaround!

Likewise :)


Fix issue 3751

fix issue #3751
Modify allocateChars() function that allocates bytes as its length.

为什么这个变更在master没有？


Array access

Hi, I've just found a bug in your ArrayAccess implementation.
The valid() method was returning false for keys that are actually valid (like 0, for example), thus breaking the functionality of foreach() loops.
I also fixed some method's docs :)
Regards,
Javier.

Thanks, @nkm !
Could you write some tests for this case?

@red-led sure, just give me a couple days :)

Ok. But I'll merge this now, just in case it wll be merged to upstream


Attention model

Hi Guys,
I was trying to implement a simple idea related the attention model.
What I'm trying  to do is as follows:
1-given a clip of video which contains 16 frame which can be described by one vector using C3D model as a context.
2- every frame  can be described by VGG model.
my question is:
how can I do  to calculate the contribution of every frame to to get the context. literally  the value of z in the attached image  here  using keras?.  The target will be the class of the clip.
here in Image of what I'm trying to implement
https://heuritech.files.wordpress.com/2016/01/detail_attentionmodel1.png?w=768
Best,
Adel

Perhaps the AttentionSeq2Seq model from seq2seq can help you. If you need to implement this at a lower level, try recurrentshop, which is what seq2seq is built on.


Add a non-ActiveRecord money accessor

Proposing a new module to support the equivalent of MoneyColumn::ActiveRecordHooks for non ActiveRecord::Base objects.
class NormalObject
  include MoneyAccessor

  money_accessor :price

  def initialize(price)
    @price = price
  end
end

object = NormalObject.new(12.34)
object.price # => #<Money value:12.34>

The code is somewhat similar to MoneyColumn::ActiveRecordHooks, but I believe there was not enough in common to abstract what would be shared. I think it would simply complexify things without any real gain.

@davidcornu @sgnr Could I have your opinions and review on this please.

I think that makes sense. :shipit:

Minor stuff. LGTM

@davidcornu All fixed and :green_apple: !

:shipit:


Empty noDataText leaves white box on page

What version of React-Table are you using?
6.6.0
What bug are you experiencing, or what feature are you proposing?
When clearing the noDataText prop, the space for the text remains on the page and looks off. If there is no text, I'd like that box to go away.
Use https://codesandbox.io/s/X6npLXPRW (by clicking the "Fork" button) to reproduce the issue.
https://codesandbox.io/s/p2w0rwnpjx

You could dynamically control your defaultPageSize when there is no data and set it to 0 or 1. To be honest, even that looks a little bit strange when react-table is designed to be a fixed height table.
No-one has asked for this specific change so it is unlikely to make it into the development pipeline.

There is an option to resolve this in the current release.... Override the NoDataComponent - make it return a null.
Closing now.


Dokodemo-door with V2Ray DNS Changes DNS TTL

What version of V2Ray are you using?
V2Ray 4.44.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.17.5 linux/amd64)
A unified platform for anti-censorship.
What's your scenario of using V2Ray?
Just use V2Ray as DNS shunts.
What problems have you encountered?
Inbound dokodemo-door changes TTL of DNS record to 600 seconds, whatever the original TTL is, though I already disabled the cache of V2Ray internal DNS.
What's your expectation?
Dokodemo-door keeps the record unchanged.
Please attach your configuration here
Server configuration:
The issue does not relate to servers, so omitted.
Client configuration:
{
  "dns": {
    "hosts": {
      "geosite:category-ads-all": "<IP_ADDRESS>"
    },
    "servers": [
      {
        "address": "<IP_ADDRESS>",
        "port": {{ port for overseas dns query, listened by local coredns }}
      },
      {
        "address": "<IP_ADDRESS>",
        "port": {{ port for home dns query, listened by local coredns }},
        "domains": ["geosite:geolocation-cn"]
      }
    ],
    "queryStrategy": "UseIPv4",
    "disableFallback": true,
    "disableCache": true
  },
  "inbounds": [
    {
      "listen": "<IP_ADDRESS>",
      "port": 53,
      "protocol": "dokodemo-door",
      "settings": {
        "address": "<IP_ADDRESS>",
        "port": {{ port for overseas dns query, listened by local coredns }},
        "network": "tcp,udp",
        "timeout": 0
      }
    }
  ],
  "outbounds": [
    {
      "protocol": "dns"
    }
  ]
}

Server log:
The issue does not relate to servers, so omitted.
Client log:
I just set loglevel to debug and redirect its output here.
2022/01/08 15:08:36 [Info] app/dns: DNS: created UDP client initialized for <IP_ADDRESS>:{{ port for overseas dns query, listened by local coredns }}
2022/01/08 15:08:36 [Info] app/dns: DNS: created UDP client initialized for <IP_ADDRESS>:{{ port for home dns query, listened by local coredns }}
2022/01/08 15:08:36 [Debug] app/proxyman/inbound: creating stream worker on <IP_ADDRESS>:53
2022/01/08 15:08:36 [Info] transport/internet/tcp: listening TCP on <IP_ADDRESS>:53
2022/01/08 15:08:36 [Info] transport/internet/udp: listening UDP on <IP_ADDRESS>:53
2022/01/08 15:08:36 [Warning] V2Ray 4.44.0 started
2022/01/08 15:08:44 [Debug] [116576051] proxy/dokodemo: processing connection from: <IP_ADDRESS>:52887
2022/01/08 15:08:44 [Info] [116576051] proxy/dokodemo: received request for <IP_ADDRESS>:52887
2022/01/08 15:08:44 [Info] [116576051] app/dispatcher: default route for udp:<IP_ADDRESS>:{{ port for overseas dns query, listened by local coredns }}
2022/01/08 15:08:44 [Info] [116576051] proxy/dns: handling DNS traffic to udp:<IP_ADDRESS>:{{ port for overseas dns query, listened by local coredns }}
2022/01/08 15:08:44 <IP_ADDRESS>:52887 accepted udp:<IP_ADDRESS>:{{ port for overseas dns query, listened by local coredns }}
2022/01/08 15:08:44 [Debug] app/dns: domain google.com will use the first DNS: [UDP:<IP_ADDRESS>:{{ port for overseas dns query, listened by local coredns }}]
2022/01/08 15:08:44 [Debug] app/dns: DNS cache is disabled. Querying IP for google.com at UDP:<IP_ADDRESS>:{{ port for overseas dns query, listened by local coredns }}
2022/01/08 15:08:44 [Debug] app/dns: UDP:<IP_ADDRESS>:{{ port for overseas dns query, listened by local coredns }} querying DNS for: google.com.
2022/01/08 15:08:44 [Debug] transport/internet/udp: dispatch request to: udp:<IP_ADDRESS>:{{ port for overseas dns query, listened by local coredns }}
2022/01/08 15:08:44 [Info] transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:{{ port for overseas dns query, listened by local coredns }}
2022/01/08 15:08:44 [Info] app/dispatcher: default route for udp:<IP_ADDRESS>:{{ port for overseas dns query, listened by local coredns }}
2022/01/08 15:08:44 [Info] proxy/dns: handling DNS traffic to udp:<IP_ADDRESS>:{{ port for overseas dns query, listened by local coredns }}
2022/01/08 15:08:44 [Info] app/dns: UDP:<IP_ADDRESS>:{{ port for overseas dns query, listened by local coredns }} got answer: google.com. TypeA -> [<IP_ADDRESS>] xxx.xxxxxxms
2022/01/08 15:08:44 [Debug] app/dns: UDP:<IP_ADDRESS>:{{ port for overseas dns query, listened by local coredns }} updating IP records for domain:google.com.
2022/01/08 15:08:52 [Info] app/proxyman/outbound: failed to process outbound traffic > proxy/dns: connection ends > context canceled
2022/01/08 15:08:52 [Info] transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe

Other configurations (such as Nginx) and logs here
coredns config (Corefile):
.:{{ port for overseas dns query, listened by local coredns }} {
  bind <IP_ADDRESS>
  forward . tls://xxx.xxx.xxx.xxx:xxxx {
    max_fails 0
    tls_servername aaa.aaa
  }
}
.:{{ port for home dns query, listened by local coredns }} {
  bind <IP_ADDRESS>
  forward . tls://yyy.yyy.yyy.yyy:yyyy {
    max_fails 0
    tls_servername bbb.bbb
  }
}

dig google.com output (first time):
; <<>> DiG 9.16.23 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26744
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.			IN	A

;; ANSWER SECTION:
google.com.		600	IN	A	<IP_ADDRESS>

;; Query time: xxx msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: {{ date and time }}
;; MSG SIZE  rcvd: 44

Note: the Query time is larger than 100 ms.
dig google.com output (second and other times):
; <<>> DiG 9.16.23 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 676
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.			IN	A

;; ANSWER SECTION:
google.com.		600	IN	A	<IP_ADDRESS>

;; Query time: 3 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: {{ date and time }}
;; MSG SIZE  rcvd: 44

Note that the query time (3 ms) is so short that the query must be finished in local machine. I used wireshark and found that the DNS query was finished just in port 53. It did not even enter coredns port! So the problem should be with dokodemo-door.

BTW, when I run dig google.com -p{{ port for overseas dns query, listened by local coredns }} (which directly queries DNS via coredns, bypassing V2Ray), the issue does not happen.

You need to remove the dns outbound and add a freedom outbound.

What you observed is V2Ray's internal DNS server limiting TTL to be no higher than 600. #1179 was made to fix this bug, but was rejected by @xiaokangwang. You can apply this patch yourself, or use downstream forks like Shadowsocks-NET/v2ray-go.

Thank you! Since this is really a bug and not fixed (or intentionally not to fix), should I close the issue or just let it alone?

I think we can keep it open for more discussions.

Wait, the issue persists in the Shadowsocks-NET/v2ray-go repo. I use the latest release from Actions (this one).

I just tried to find the reason. Since I know little about golang, I just globally searched 600 and found its two occurence. And I forked v2ray-go and changed these 600 to 432 and 543 seperately. Then I use Actions to build and found that the TTL is now 432. So the reason should be here.

Unfortunately it's not be easy to fix this bug. The lookup method currently only returns a slice of IPs. We have to change the interfaces to return the DNS RRs instead of only IPs. New fields would have to be introduced to the IPRecord struct.

Is there any development on this problem?

Overriding any DNS reply TTL to 600 still an issue in V2Ray 5.13.0

I have identified an issue related to the handling of DNS TTL (Time to Live) values in V2ray. I would like to request a feature enhancement that addresses this issue and provides more flexibility in the TTL manipulation process. Currently, when V2ray encounters DNS responses with TTL values shorter than 600 seconds, it artificially expands the TTL to a fixed value of 600 seconds. This behavior becomes problematic in situations where shorter TTLs are explicitly set by authoritative DNS servers, such as the case of the domain "dns.msftncsi.com" used for Microsoft OS testing, where a TTL of 30 seconds is intended.
I kindly request that you address the forced override of DNS TTL values to 600 seconds in V2ray. Instead, I propose implementing a more flexible approach that allows for the preservation of the original TTL as specified by the authoritative DNS server.
TTL Preservation: Modify the DNS resolver module in V2ray to retain the original TTL value received from the authoritative DNS server, regardless of its duration. This modification will ensure that V2ray accurately respects the TTL settings dictated by the DNS infrastructure.
Or
Fine-grained Configuration: Introduce a configuration parameter that provides users with the ability to define their desired behavior for handling short TTL values. This parameter should allow users to choose between preserving the original TTL, overriding it with a custom value, or using the default behavior of V2ray (expanding to 600 seconds).
By implementing these changes, V2ray will become more adaptable to various DNS environments and requirements. Users will be able to maintain the integrity of the TTL values and ensure accurate DNS resolution without forced overrides.

#1179


Name Conflict for medplum storage bucket name

Description

Our AWS tooling defaults to naming the storage bucket medplum-{environment}-storage
For example, if a customer calls their environment staging, the bucket will be called medplum-staging-storage
Because S3 bucket names are globally unique across regions and accounts, this can cause conflicts between self-hosted users.
This conflict causes the aws tooling to fail and rollback

Proposal

Use the domain name for the bucket name (e.g. storage.{environment}.foomedical.com) to keep these buckets globally unique across organizations

This is configurable.  I'm ok to change the default value as suggested.

Fixed in https://github.com/medplum/medplum/pull/3112


Strange behaviour (hangs server) on certain BLE device

A few days now I'm looking into a problem connecting a device which I think maybe has a limited BLE stack. Connecting and getting info with BLE Scanner on a Android phone works though.
In version 1.0.1 it failed constantly. When connecting (yes connecting) to the device, the device BLE hung itself, because after trying to connect with NimBLE and disconnecting the ESP32 from power the phone still sees the device, but cannot connect to it/get information from it.
The changes made until today in NimBLE have a different result:

Quite often the connection didn't succeed [Using the refactored BLE examples]:
16:09:31.848 -> GAP procedure initiated: connect; peer_addr_type=0 peer_addr=c4:64:e3:92:13:7c scan_itvl=16 scan_window=16 itvl_min=24 itvl_max=40 latency=0 supervision_timeout=256 min_ce_len=0 max_ce_len=0 own_addr_type=0
16:09:31.848 -> ble_hs_hci_cmd_send: ogf=0x08 ocf=0x000d len=25
16:09:31.848 -> 0x0d 0x20 0x19 0x10 0x00 0x10 0x00 0x00 0x00 0x7c 0x13 0x92 0xe3 0x64 0xc4 0x00 0x18 0x00 0x28 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00
16:09:31.848 -> Command Status: status=0 cmd_pkts=5 ocf=0xd ogf=0x8
16:09:31.950 -> LE connection complete. handle=0 role=0 paddrtype=0 addr=c4.64.e<IP_ADDRESS>c local_rpa=<IP_ADDRESS>.0.0 peer_rpa=<IP_ADDRESS>.0.0 itvl=40 latency=0 spvn_tmo=256 mca=0
16:09:31.950 -> D NimBLEClient: "Got Client event "
16:09:31.950 -> D NimBLEClient: "Connection established"
16:09:31.950 -> GATT procedure initiated: exchange mtu
16:09:31.950 -> host tx hci data; handle=0 length=7
16:09:31.950 -> ble_hs_hci_acl_tx(): 0x00 0x00 0x07 0x00 0x03 0x00 0x04 0x00 0x02 0x00 0x01
16:09:31.950 -> txed att command: mtu req; conn=0 mtu=256
16:09:31.950 -> ble_hs_hci_cmd_send: ogf=0x08 ocf=0x0016 len=2
16:09:31.950 -> 0x16 0x20 0x02 0x00 0x00
16:09:31.950 -> Command Status: status=0 cmd_pkts=5 ocf=0x16 ogf=0x8
16:09:32.224 -> Number of Completed Packets: num_handles=1
16:09:32.224 -> handle:0 pkts:1
16:09:32.224 -> Disconnection Complete: status=0 handle=0 reason=62
16:09:32.224 -> D NimBLEClient: "Got Client event "
16:09:32.224 -> I NimBLEClient: "disconnect; reason=574, "
16:09:32.224 -> onDisconnect

Sometimes, the connection succeed. However, getting a service or doing a discovery with discover attributes then gets an error:
16:10:00.922 -> GATT procedure initiated: exchange mtu
16:10:00.922 -> host tx hci data; handle=0 length=7
16:10:00.922 -> ble_hs_hci_acl_tx(): 0x00 0x00 0x07 0x00 0x03 0x00 0x04 0x00 0x02 0x00 0x01
16:10:00.922 -> txed att command: mtu req; conn=0 mtu=256
16:10:00.922 -> ble_hs_hci_cmd_send: ogf=0x08 ocf=0x0016 len=2
16:10:00.922 -> 0x16 0x20 0x02 0x00 0x00
16:10:00.922 -> Command Status: status=0 cmd_pkts=5 ocf=0x16 ogf=0x8
16:10:00.989 -> Number of Completed Packets: num_handles=1
16:10:00.989 -> handle:0 pkts:1
16:10:01.092 -> LE Remote Used Features. handle=0 feat=fd 00 00 00 00 00 00 00
16:10:01.092 -> ble_hs_hci_evt_acl_process(): conn_handle=0 pb=2 len=7 data=0x03 0x00 0x04 0x00 0x03 0xf7 0x00
16:10:01.092 -> rxed att command: mtu rsp; conn=0 mtu=247
16:10:01.092 -> D NimBLEClient: "Got Client event "
16:10:01.092 -> I NimBLEClient: "mtu update event; conn_handle=0 mtu=247"
16:10:01.092 -> D NimBLEClient: ">> deleteServices"
16:10:01.092 -> D NimBLEClient: "<< deleteServices"
16:10:01.092 -> onConnect
16:10:01.092 -> D NimBLEClient: "<< connect()"
16:10:01.092 ->  - Connected to server
16:10:01.092 -> D NimBLEClient: ">> getService: uuid: 0x180a"
16:10:01.127 -> D NimBLEClient: ">> retrieveServices"
16:10:01.127 -> GATT procedure initiated: discover service by uuid; uuid=0x180a
16:10:01.127 -> txed att command: find type value req; conn=0 start_handle=0x0001 end_handle=0xffff attr_type=10240
16:10:01.127 -> host tx hci data; handle=0 length=13
16:10:01.127 -> ble_hs_hci_acl_tx(): 0x00 0x00 0x0d 0x00 0x09 0x00 0x04 0x00 0x06 0x01 0x00 0xff 0xff 0x00 0x28 0x0a 0x18
16:10:01.160 -> Number of Completed Packets: num_handles=1
16:10:01.160 -> handle:0 pkts:1
16:10:01.329 -> ble_hs_hci_evt_acl_process(): conn_handle=0 pb=2 len=9 data=0x05 0x00 0x04 0x00 0x01 0x06 0x01 0x00 0x11
16:10:01.329 -> rxed att command: error rsp; conn=0 req_op=6 handle=0x0001 error_code=17
16:10:01.329 -> D NimBLEClient: "Service Discovered >> status: 273 handle: -1"
16:10:01.329 -> E NimBLEClient: "characteristicDiscCB() rc=273 "
16:10:01.329 -> D NimBLEClient: "<< << Service Discovered"
16:10:01.329 -> E NimBLEClient: "Could not retrieve services"
16:10:01.329 -> D NimBLEClient: "<< getService: not found"
But I know for sure that this service exists and on other devices it's working without a problem. Same happens with the BLE_Client example code (this time with the discover attribute function - and again, the codes works without a problem with other devices):
16:31:46.172 -> D NimBLEClient: ">> retrieveServices"
16:31:46.172 -> GATT procedure initiated: discover all services
16:31:46.172 -> txed att command: read group type req; conn=0 start_handle=0x0001 end_handle=0xffff
16:31:46.172 -> LE Connection Update Complete. handle=0 itvl=120 latency=0 timeout=60
16:31:46.172 -> host tx hci data; handle=0 length=11
16:31:46.172 -> ble_hs_hci_acl_tx(): 0x00 0x00 0x0b 0x00 0x07 0x00 0x04 0x00 0x10 0x01 0x00 0xff 0xff 0x00 0x28
16:31:46.172 -> D NimBLEClient: "Got Client event "
16:31:46.172 -> I NimBLEClient: "Connection parameters updated."
16:31:46.276 -> Number of Completed Packets: num_handles=1
16:31:46.276 -> handle:0 pkts:1
16:31:46.483 -> ble_hs_hci_evt_acl_process(): conn_handle=0 pb=2 len=9 data=0x05 0x00 0x04 0x00 0x01 0x10 0x01 0x00 0x11
16:31:46.483 -> rxed att command: error rsp; conn=0 req_op=16 handle=0x0001 error_code=17
16:31:46.483 -> D NimBLEClient: "Service Discovered >> status: 273 handle: -1"
16:31:46.483 -> E NimBLEClient: "characteristicDiscCB() rc=273 "
16:31:46.483 -> D NimBLEClient: "<< << Service Discovered"
16:31:46.483 -> E NimBLEClient: "Could not retrieve services"
16:31:46.483 -> E NimBLEClient: "Error: Failed to get services"
The funny thing is though that in both cases, with the latest changes in code I can still connect from my phone to the device after the errors occur (although with the first one it's logical because the connection wasn't finalized).
Normally I would suspect the device implementation of BLE, but since the BLE Scanner on my phone doesn't seem to have a problem with it, and the behaviour changed (BLE on the serverdevice not hanging anymore) with the latest changes, I'm thinking it may be caused by something in NimBLE...

Hi @Calypso971 Thank you for the detail and logs (especially with the NimBLE stack logging).
What I see here is that in the first log, before the recent code changes, the error was BLE_ERR_CONN_ESTABLISHMENT, which was probably a symptom that was fixed in that change.
After the code changes you now get BLE_ATT_ERR_INSUFFICIENT_RES. Which is the server telling you it can't process the request for some reason. The question is what is that reason?
I suspect it could be this:
txed att command: read group type req; conn=0 start_handle=0x0001 end_handle=0xffff
The server may not be able to process this request as it's asking for the whole database of attributes.
To test this you could try changing the 0xffff on this line to a smaller value, maybe 0x0fff, and check the result.
It's not a solution to the problem, as that will prevent retrieving the full attribute set, but it would provide a clue as to the next step.

@h2zero: Thanks for your suggestion.
First of all: the first debuglines are still with the latest version, only on one of those disconnect sessions. But I can work around those with a retry I guess, so there should be a workaround for that. First thought that maybe connectivity could be an issue, but the devices are next to eachother, the phone I use for testing is much further away, and the RSSI reported is good.
Tried your suggestion of using 0x0fff, doesn't have a result (also tried to change it on line 1385) but that didn't give a result; tried it with discovery, service 0x1800, 0x180a and (this one) with a custom service that is present on the device (and can be accessed by BLE Scanner on the phone):
08:17:58.183 -> D NimBLEClient: ">> getService: uuid: f000ffc0-0451-4000-b000-000000000000"
08:17:58.217 -> D NimBLEClient: ">> retrieveServices"
08:17:58.217 -> GATT procedure initiated: discover service by uuid; uuid=f000ffc0-0451-4000-b000-000000000000
08:17:58.217 -> txed att command: find type value req; conn=0 start_handle=0x0001 end_handle=0x0fff attr_type=10240
08:17:58.217 -> host tx hci data; handle=0 length=27
08:17:58.217 -> ble_hs_hci_acl_tx(): 0x00 0x00 0x1b 0x00 0x17 0x00 0x04 0x00 0x06 0x01 0x00 0xff 0x0f 0x00 0x28 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xb0 0x00 0x40 0x51 0x04 0xc0 0xff 0x00 0xf0
08:17:58.251 -> Number of Completed Packets: num_handles=1
08:17:58.251 -> handle:0 pkts:1
08:17:58.320 -> ble_hs_hci_evt_acl_process(): conn_handle=0 pb=2 len=9 data=0x05 0x00 0x04 0x00 0x01 0x06 0x01 0x00 0x11
08:17:58.320 -> rxed att command: error rsp; conn=0 req_op=6 handle=0x0001 error_code=17
08:17:58.320 -> D NimBLEClient: "Service Discovered >> status: 273 handle: -1"
08:17:58.320 -> E NimBLEClient: "characteristicDiscCB() rc=273 "
08:17:58.320 -> D NimBLEClient: "<< << Service Discovered"
08:17:58.320 -> E NimBLEClient: "Could not retrieve services"
08:17:58.320 -> D NimBLEClient: "<< getService: not found"
08:17:58.320 -> We are now connected to the BLE Server.
When I'm correct, the error returned (17) is 0x11 Unsupported Feature or Parameter Value? Basically, since it's also doing a discovery when just accessing a single service, the problem could be in the discovery call, as you are suggesting by changing the 0xffff value. But why is a BLE Scanner application on the phone then working, when that one is totally dependent of the discovery...

@Calypso971 I'm not sure what could be causing this issue, all I can see in the log is the response to the discovery command is error code 0x11. That code is an ATT response code, which NimBLE reports as 0x0111 (273) Aka: BLE_ATT_ERR_INSUFFICIENT_RES.
The peripheral is saying it's low on resources and cannot process the request, but what resources?
There are a couple of possiblities:

Too busy, we may need to delay or change connection parameters
Not enough memory to handle the request, not much we can do other than wait and hope it clears

A couple questions, what is this device you're connecting to?
Could your phone possibly be connected still while you're connecting with the esp32 (might explain the error code)?

The peripheral is saying it's low on resources and cannot process the request, but what resources?
There are a couple of possiblities:
* Too busy, we may need to delay or change connection parameters

Did quite some testing with those, but it didn't succeed :-(. Because it annoys me that I can't get this to work, I did a BT Snoop on my phone and examined it with Wireshark. Connection parameters of my phone are strange to say the least:
min/max are 6 (7.5 ms) and Supervision delay is 500. While in your example code you mention that the min/max shouldn't be lower as 24... Ofcourse trying these parameters still don't have the wanted result.

* Not enough memory to handle the request, not much we can do other than wait and hope it clears

The funny thing of this is, is that a query by phone doesn't have the problem. And the discovery call is almost the same:
Phone: 02 00 0b 00 07 00 04 00 10 01 00 ff ff 00 28
ESP32: 00 00 0b 00 07 00 04 00 10 01 00 ff ff 00 28
The first byte is the handle, so that is the only change and not strange. On the Phone results are returned, so I think the BLE call (TX) is the same, the memory usage on the same device should be too.

A couple questions, what is this device you're connecting to?

Texas Instruments based uPC board with a Laird SaBLE-x-R2 bluetooth module

Could your phone possibly be connected still while you're connecting with the esp32 (might explain the error code)?

Not with the phone, and also the module is programmed in such a way to only accept one connection. So if you're connected (and I am with the ESP32) it doesn't accept connection from another device.
I've also tried to do something "dirty" and request a non-existent UUID. Because this should also trigger a discovery, I'd expect to get the dreaded error also. But it didn't:
15:37:54.483 -> ble_hs_hci_acl_tx(): 0x00 0x00 0x0d 0x00 0x09 0x00 0x04 0x00 0x06 0x01 0x00 0xff 0xff 0x00 0x28 0x0a 0x3f
15:37:54.515 -> Number of Completed Packets: num_handles=1
15:37:54.515 -> handle:0 pkts:1
15:37:54.585 -> ble_hs_hci_evt_acl_process(): conn_handle=0 pb=2 len=9 data=0x05 0x00 0x04 0x00 0x01 0x06 0x01 0x00 0x0a
15:37:54.585 -> rxed att command: error rsp; conn=0 req_op=6 handle=0x0001 error_code=10

However as seen in one of the previous scans, requesting an existing UUID directly also returns the error 17. This also points into a memory issue. My first reaction also was: it's the problem of the device I'm connecting to. However, that doesn't explain why connecting with a phone and BLE Scanner just works. Also other BLE scanning applications just work.
If helpful (to view the comm flow that works) I can mail the Snoopfile from the phone - maybe there's something in the communication before the actual request of the discovery that gives a hunch of what's going on compared to the connection information from the ESP:
15:45:42.266 -> GAP procedure initiated: connect; peer_addr_type=0 peer_addr=c4:64:e3:92:13:7c scan_itvl=16 scan_window=16 itvl_min=24 itvl_max=40 latency=0 supervision_timeout=256 min_ce_len=0 max_ce_len=0 own_addr_type=0
[15:45:42.300] -> ble_hs_hci_cmd_send: ogf=0x08 ocf=0x000d len=25
15:45:42.300 -> 0x0d 0x20 0x19 0x10 0x00 0x10 0x00 0x00 0x00 0x7c 0x13 0x92 0xe3 0x64 0xc4 0x00 0x18 0x00 0x28 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00
15:45:42.300 -> Command Status: status=0 cmd_pkts=5 ocf=0xd ogf=0x8
15:45:42.676 -> LE connection complete. handle=0 role=0 paddrtype=0 addr=c4.64.e<IP_ADDRESS>c local_rpa=<IP_ADDRESS>.0.0 peer_rpa=<IP_ADDRESS>.0.0 itvl=40 latency=0 spvn_tmo=256 mca=0
15:45:42.676 -> D NimBLEClient: "Got Client event "
15:45:42.676 -> D NimBLEClient: "Connection established"
15:45:42.676 -> GATT procedure initiated: exchange mtu
15:45:42.676 -> host tx hci data; handle=0 length=7
15:45:42.676 -> ble_hs_hci_acl_tx(): 0x00 0x00 0x07 0x00 0x03 0x00 0x04 0x00 0x02 0x00 0x01
15:45:42.676 -> txed att command: mtu req; conn=0 mtu=256
15:45:42.676 -> ble_hs_hci_cmd_send: ogf=0x08 ocf=0x0016 len=2
15:45:42.676 -> 0x16 0x20 0x02 0x00 0x00
15:45:42.676 -> Command Status: status=0 cmd_pkts=5 ocf=0x16 ogf=0x8
15:45:42.710 -> Number of Completed Packets: num_handles=1
15:45:42.710 -> handle:0 pkts:1
15:45:42.779 -> LE Remote Used Features. handle=0 feat=fd 00 00 00 00 00 00 00
15:45:42.779 -> ble_hs_hci_evt_acl_process(): conn_handle=0 pb=2 len=7 data=0x03 0x00 0x04 0x00 0x03 0xf7 0x00
15:45:42.779 -> rxed att command: mtu rsp; conn=0 mtu=247
15:45:42.779 -> D NimBLEClient: "Got Client event "
15:45:42.779 -> I NimBLEClient: "mtu update event; conn_handle=0 mtu=247"
15:45:42.779 -> D NimBLEClient: ">> deleteServices"
15:45:42.779 -> D NimBLEClient: "<< deleteServices"
15:45:42.779 -> D NimBLEClientCallbacks: "onConnect: default"
15:45:42.779 -> D NimBLEClient: "<< connect()"

Thank you for the details @Calypso971. Since this works with the phone and we can rule out, for now, a resource constraint on the peripheral, maybe the problem is a resource issue on the esp32.
There are a couple settings we can try in order to verify that possibility.
In nimconfig.h the following values can be adjusted to increase buffers:
/** @brief ACL Buffer count */
#define CONFIG_BT_NIMBLE_ACL_BUF_COUNT 12

/** @brief ACL Buffer size */
#define CONFIG_BT_NIMBLE_ACL_BUF_SIZE 255

/** @brief HCI Event Buffer size */
#define CONFIG_BT_NIMBLE_HCI_EVT_BUF_SIZE 70

/** @brief Number of high priority HCI event buffers */
#define CONFIG_BT_NIMBLE_HCI_EVT_HI_BUF_COUNT 30

/** @brief Number of low priority HCI event buffers */
#define CONFIG_BT_NIMBLE_HCI_EVT_LO_BUF_COUNT 8

/**
 * @brief Sets the number of MSYS buffers available.
 * @details MSYS is a system level mbuf registry. For prepare write & prepare \n
 * responses MBUFs are allocated out of msys_1 pool. This may need to be increased if\n
 * you are sending large blocks of data with a low MTU. E.g: 512 bytes with 23 MTU will fail.
 */
#define CONFIG_BT_NIMBLE_MSYS1_BLOCK_COUNT 12

My first thought is to try increasing the HCI_EVT settings, try doubling them and see what happens.
This is all speculation without seeing logs from the peripheral however so trial and error is all I can suggest.

Well without details no answer I think. This is a strange thing happening, and that only motivates me more to find out what's going on.
Doubled the values a few times, and beside the ACL Buffer Size it didn't have any effect. However, the ACL Buffer Size doubled means a crash/reboot of the ESP, so I left that one on 255.
Also have been playing a bit with the MTU and MSYS settings, also without result. Going to continue tomorrow.

This is a strange thing happening, and that only motivates me more to find out what's going on.

I like this attitude 😄 . I'm very curious myself, tried to reproduce this issue but have been unable.
Another thing you can try is removing the call to exchange MTU here, you would also need to then change this to rc = 0; break;.
Also I have had issues in the past with this line. You could try commenting that out.

Succes. Bypassing the MTU exchange did it. Even though it's very early, I'm taking a glass on it and will try to look into a possible solution later this weekend. Thanks for the help upto now!

Glad to hear there is progress on this. Of course I now wonder why that causes the issue....

Yeah, want to know it myself too ofcourse. When looking at what's happening in MTU exchange:
08:35:48.066 -> GATT procedure initiated: exchange mtu
08:35:48.066 -> host tx hci data; handle=0 length=7
08:35:48.066 -> ble_hs_hci_acl_tx(): 0x00 0x00 0x07 0x00 0x03 0x00 0x04 0x00 0x02 0x80 0x00
08:35:48.066 -> txed att command: mtu req; conn=0 mtu=128
This is a request to change MTU to 128, right?
08:35:48.066 -> ble_hs_hci_cmd_send: ogf=0x08 ocf=0x0016 len=2
08:35:48.099 -> 0x16 0x20 0x02 0x00 0x00
08:35:48.099 -> Command Status: status=0 cmd_pkts=5 ocf=0x16 ogf=0x8
08:35:48.099 -> Number of Completed Packets: num_handles=1
08:35:48.099 -> handle:0 pkts:1
08:35:48.099 -> ble_hs_hci_evt_acl_process(): conn_handle=0 pb=2 len=7 data=0x03 0x00 0x04 0x00 0x03 0xf7 0x00
08:35:48.099 -> rxed att command: mtu rsp; conn=0 mtu=247
This is the response to put the MTU to 247 (strange value IMHO)
08:35:48.099 -> D NimBLEClient: "Got Client event BLE_GAP_EVENT_MTU"
08:35:48.099 -> I NimBLEClient: "mtu update event; conn_handle=0 mtu=128"
And now it's updated to 128?
In my opinion this doesn't match up - I request 128, I set it to 128, and in between I get an answer saying that it is 247.
Maybe there's a logical explanation for this though.
Another time I got about the same sequence, but then it seems to have negotiated to 247 (again 247):
13:12:21.289 -> txed att command: mtu req; conn=0 mtu=256
13:12:21.289 -> ble_hs_hci_cmd_send: ogf=0x08 ocf=0x0016 len=2
13:12:21.359 -> rxed att command: mtu rsp; conn=0 mtu=247
13:12:21.359 -> I NimBLEClient: "mtu update event; conn_handle=0 mtu=247"
Now the stranger part: from another device (that works) I get exactly the same result. So I'm pretty stuck here.

I request 128, I set it to 128, and in between I get an answer saying that it is 247.
Maybe there's a logical explanation for this though.

Yes the explanation is that we send our MTU (128) and the peripheral sends it's MTU (247) and as per spec the lowest of the 2 values is used for the connection MTU. All seems to be working as intended there.

Closing this as stale. Please re-open if the issue is not yet resolved.


fix(collectionActor): fix random failures

Refer to this link for build results (access rights to CI server needed):
http://ci.really.io//job/really-pr-validator/76/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://ci.really.io//job/really-pr-validator/77/
Test PASSed.

test this please

Refer to this link for build results (access rights to CI server needed):
http://ci.really.io//job/really-pr-validator/78/
Test PASSed.


Build fails when PKG_CONFIG_PATH env variable is not empty

build.rs:86 should add the bundled lib path to the beginning, not the end of PKG_CONFIG_PATH, or system-wide libgit2 will be used if present, which can lead to build failures (like in Heather/gentoo-rust#124)

Good point! Thanks for the report!


SSR error 1.0.0-next.154/155

Hello, great to see this option as an adaptor!
I am getting this error though from within @sveltejs/kit/dist/ssr.js:
file:///Users/gilbert/Code/eze-app/node_modules/.pnpm/@sveltejs+kit@1.0.0-next.154_svelte@3.42.1/node_modules/@sveltejs/kit/dist/ssr.js:1607
	if (incoming.path !== '/' && options.trailing_slash !== 'ignore') {
	                                     ^

TypeError: Cannot read property 'trailing_slash' of null

My svelte.config.js had been set to ssr: false, and I have also tried ssr: true - I'm taking a poke around the official adaptors but can't see anything obvious for this. Any help much appreciated!

Hmm, how are you calling the adapter?

This looks great, but I just got stuck at the same place after building and trying to run it
/build/chunks/app-e494f937.js:1211
  if (incoming.path !== "/" && options2.trailing_slash !== "ignore") {
                                        ^

TypeError: Cannot read properties of null (reading 'trailing_slash')

Ah, I figured it out, options is null because init hasn't been called, just got it working and going to submit a pr


PhealNg got updated

PhealNg got updated and uses now Guzzle in order to communicate, could there be any problems with that ?

Its about time PhealNG moved from its own curl wrapper to something more decent.
I haven't noticed any BC breaks as it is pretty much internal change so i don't think anything would change from user perspective.

Don't see a problem with that, but this reminds me that I want to change the binding from my own symfony pheal binding to another one: https://github.com/tarioch/pheal-bundle/issues/1

Yeah I did the changes on PhealNG about the curl stuff ^^ but I wasn't sure anymore and just want to mentioned it


Youtube history download sees 0 videos

I copied/pasted the following from an issue I wrote in youtube_dl.  I tried youtube_dlc master today (9/13) and the same issue exists.

Checklist

[ x] I'm reporting a broken site support
[ x] I've verified that I'm running youtube-dl version 2020.07.28
[ x] I've checked that all provided URLs are alive and playable in a browser
[ x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[ x] I've searched the bugtracker for similar issues including closed ones

Verbose log

[debug] System config: []
[debug] User config: ['-o', '%(uploader)s_%(upload_date)s_%(title)s_%(height)s_%(id)s.%(ext)s', '--continue', '--no-overwrites', '--ignore-errors', '--external-downloader', 'aria2c', '--external-downloader-args', '-x 16 -s 16 -k 1M --console-log-level=error --file-allocation=none --keep-unfinished-download-result=false --summary-interval=0']
[debug] Custom config: []
[debug] Command-line args: ['--cookies', '/home/user/.config/youtube-dl/cookies-user.txt', '--max-filesize', '10g', '--download-archive', './.downloaded.txt', '--verbose', 'https://www.youtube.com/feed/history']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2020.07.28
[debug] Python version 3.7.8 (CPython) - FreeBSD-12.1-RELEASE-p8-amd64-64bit-ELF
[debug] exe versions: ffmpeg 4.3.1, ffprobe 4.3.1, rtmpdump 2.4
[debug] Proxy map: {}
[youtube:history] Youtube History: Downloading webpage
[download] Downloading playlist: Youtube History
[youtube:history] playlist Youtube History: Downloading 0 videos
[download] Finished downloading playlist: Youtube History
Description

Trying to download from YouTube's history results in it showing zero videos and not downloading anything.  Using the same cookies and download.txt file but downloading from a playlist instead works fine, so I know those files are valid.  I also tried downloading the history from three different accounts and the same behavior of zero videos happens.  The last time this worked properly was July 22nd, so it seems to have been broken for a while.
Here is the exact command I'm using:
/usr/local/bin/youtube-dl --cookies /home/user/.config/youtube-dl/cookies-user.txt --max-filesize 10g --download-archive ./.downloaded.txt --verbose https://www.youtube.com/feed/history

Haven't tested this. But I simply assume youtube changed something on their end. I can try to debug it and see what is happening when it's trying to download the feed info.

Well turns out the subscription feed isn't working as well. All the other feeds don't even have URL support.

@xarantolus
https://github.com/blackjack4494/youtube-dlc/pull/173

PS D:\gitkraken\youtube-dl> python3 -m youtube_dlc "https://www.youtube.com/feed/history" -v -F --cookies .\cookies.txt
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://www.youtube.com/feed/history', '-v', '-F', '--cookies', '.\cookies.txt']
[debug] Loading archive file None
[debug] Encodings: locale cp65001, fs utf-8, out utf-8, pref cp65001
[debug] youtube-dlc version 2020.09.29
[debug] Git HEAD: 60ecb525b
[debug] Python version 3.6.5 (CPython) - Windows-10-10.0.19041-SP0
[debug] exe versions: ffmpeg 4.2.1, ffprobe 4.2.1
[debug] Proxy map: {}
[youtube:history] Youtube History: Downloading webpage
[download] Downloading playlist: Youtube History
[youtube:history] playlist Youtube History: Downloading 200 videos
[download] Downloading video 1 of 200
[youtube] hZSOhVdzqZk: Downloading webpage
[info] Available formats for hZSOhVdzqZk:
format code  extension  resolution note
249          webm       audio only tiny   53k , opus @ 50k (48000Hz), 18.30MiB
250          webm       audio only tiny   74k , opus @ 70k (48000Hz), 23.10MiB
140          m4a        audio only tiny  133k , m4a_dash container, mp4a.40.2@128k (44100Hz), 50.10MiB
251          webm       audio only tiny  133k , opus @160k (48000Hz), 41.90MiB
278          webm       256x144    144p   73k , webm container, vp9, 30fps, video only, 13.20MiB
160          mp4        256x144    144p  119k , avc1.4d400c, 30fps, video only, 9.82MiB
242          webm       426x240    240p  147k , vp9, 30fps, video only, 17.12MiB
133          mp4        426x240    240p  222k , avc1.4d4015, 30fps, video only, 18.69MiB
243          webm       640x360    360p  304k , vp9, 30fps, video only, 33.23MiB
134          mp4        640x360    360p  325k , avc1.4d401e, 30fps, video only, 32.04MiB
244          webm       854x480    480p  566k , vp9, 30fps, video only, 53.00MiB
135          mp4        854x480    480p  653k , avc1.4d401f, 30fps, video only, 50.44MiB
247          webm       1280x720   720p  987k , vp9, 30fps, video only, 98.92MiB
136          mp4        1280x720   720p 1206k , avc1.64001f, 30fps, video only, 94.31MiB
248          webm       1920x1080  1080p 1616k , vp9, 30fps, video only, 200.76MiB
137          mp4        1920x1080  1080p 2446k , avc1.640028, 30fps, video only, 184.57MiB
18           mp4        640x360    360p  223k , avc1.42001E, 30fps, mp4a.40.2@ 96k (44100Hz), 86.31MiB
22           mp4        1280x720   720p  372k , avc1.64001F, 30fps, mp4a.40.2@192k (44100Hz) (best)
[download] Downloading video 2 of 200
[youtube] yyxy-KW_seI: Downloading webpage

will include the fix in the next release. It will be out in a few minutes.

It's only grabbing the first page of videos. (~200)
Im using "--playlist-items 1-1500" but it doesn't work.

Yup that's due to youtube chaning apis.
Instead of ajax they use https://www.youtube.com/youtubei/v1/browse?key= but the ajax sometimes still works or is used by youtube. As for the new api they changed the location/name of the token within the last 2-3 weeks.
There is
"INNERTUBE_API_KEY":"AIza..." in the html doc
which is needed to make any requests to /youtubei/v1/
Couldn't find any sources for endpoints yet but have documented a few already maybe I will make them public when I have a nicer rewrite.
Maybe @xarantolus is interested in this as well as he wrote the feed/url extraction fix.
Entrypoint for next continuation request is embedded in html doc as well
{"continuationItemRenderer":{"trigger":"CONTINUATION_TRIGGER_ON_ITEM_SHOWN","continuationEndpoint":{"clickTrackingParams":"CB0...=","commandMetadata":{"webCommandMetadata":{"url":"/service_ajax","sendPost":true,"apiUrl":"/youtubei/v1/browse"}},"continuationCommand":{"token":"4qmFsgJ....","request":"CONTINUATION_REQUEST_TYPE_BROWSE"}}}}]

We just need the token and can send a new request with some additional mandatory parameters such as
authorization: SAPISIDHASH 16..._6b5c3...
We actually need the sapisid which can then be fed into some algorithm to give us back a valid hash SAPISIDHASH
This algorithm is quite easy
sha1(new Date().getTime() + " " + SAPISID + " " + origin) [source]
The implementation for a fix shouldn't take long

@qw3rty2017

[youtube:history] Youtube History: Downloading page #42q
[youtube:history] Youtube History: Downloading page #43q
[youtube:history] Youtube History: Downloading page #44q
[youtube:history] Youtube History: Downloading page #45q
[youtube:history] Youtube History: Downloading page #46q
[youtube:history] Youtube History: Downloading page #47q
[youtube:history] Youtube History: Downloading page #48q
[youtube:history] Youtube History: Downloading page #49q
[youtube:history] Youtube History: Downloading page #50q
ERROR: Unable to download JSON metadata: HTTP Error 500: Internal Server Error (caused by <HTTPError 500: 'Internal Server Error'>); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version;
see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dlc with the --verbose flag and include its complete output.

I added the qs otherwise I would ping several issues.
I actually don't know nor believe that page 50 is the maximum. Sometimes it stops earlier like around 40-ish.
The '500 HTTP ERROR' needs to be analzed. There is prolly some rate limiting going on.
However I have honestly no clue how to know when to stop polling this way. As there shouldn't be any more continuation token if I am done.
But at least it is working now. Have to polish it a bit but then it's ready to be shipped with next release.


Add option to request only recent listens.

My listens history goes back to 2005, so it's rather large, and therefore slow to update. Using the --pages option to limit it to recent listens isn't helpful, because I might listen to a variable number of songs between updates.
This PR implements a --days option that stops the exporter after seeing a listen older than the specified number of days. This means the last page of the export will contain listens older than the specified number of days, but this I think is no problem.

Yeah, makes sense, glad to merge
Could you change the condition to be a separate one? I'd rather not have it be that difficult to read with all the parens
Like
if days is not None and (datetime.utcfromtimestamp(max_ts) < datetime.utcnow() - timedelta(days=days)):
     break
if pages is not None....:
     break

thanks!


gnomeExtensions.pop-shell can't pick "Active Hint Color"

Describe the bug
In pop-shell's tray menu the option "Active Hint Color" doesn't do anything when clicked.
Steps To Reproduce
Steps to reproduce the behavior:

Install & enable pop-shell in GNOME (xserver).
Open pop-shell's tray menu and try clicking "Active Hint Color."

Expected behavior
A color picker dialog should open to enable the user to select their desired color.
Additional context
I see that this was an issue in the past (#156033) that got fixed by #158724
In the previous issue both the "Active Hint Color" and the "Floating Window Exceptions" dialog didn't work, but in my case only the "Active Hint Color" is not working.
Notify maintainers
@genofire

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[grnqrtr@nixos:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.5.4, NixOS, 23.11 (Tapir), 23.11pre527133.5ba549eafcf3`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.17.0`
 - channels(root): `"nixos, nixos-hardware"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

i got that error:
Mar 26 00:18:32 localhost main.js[10452]: JS LOG<EMAIL_ADDRESS>Mar 26 00:18:32 localhost main.js[10452]: JS LOG<EMAIL_ADDRESS>Mar 26 00:18:32 localhost main.js[10452]: JS ERROR: Error: getSettings() can only be called when extension is available
                                          getSettings@file:///run/current-system/sw/share/gnome-shell/extensions/pop-shell@system76.com/color_dialog/main.js:27:15
                                          launch_color_dialog@file:///run/current-system/sw/share/gnome-shell/extensions/pop-shell@system76.com/color_dialog/main.js:40:40
                                          @file:///run/current-system/sw/share/gnome-shell/extensions/pop-shell@system76.com/color_dialog/main.js:65:1
Mar 26 00:18:32 localhost main.js[10452]: Module<EMAIL_ADDRESS>threw an exception

As a workaround, this can be configured with:
dconf.settings."org/gnome/shell/extensions/pop-shell" = {
  hint-color-rgba = "rgba(126, 186, 228, 1)";
};

it looks like @wrenix has fixed it.
@grnqrtr do you like to close this issue?

I'm still experiencing this, although my error is different:
main.js[5382]: JS ERROR: Error: Requiring Gtk, version 3.0: Typelib file for namespace 'Gtk', version '3.0' not found
require@resource:///org/gnome/gjs/modules/esm/gi.js:16:28
@gi://Gtk:3:25
main.js[5382]: Module<EMAIL_ADDRESS>threw an exception

The "floating window exceptions" dialog doesn't work for me, either.


Remove babel-preset-jsdoc-to-assert from unit test

Fix https://github.com/almin/almin/issues/82
This leaves .babelrc for https://github.com/almin/almin/issues/83

LGTM


Progress ring visibility

@akshithrajesh290 What's your problem with the ProgressRing visibilty?

maybe github problem but here is what he wrote
Need to show Progress ring for at least 5 seconds in My Application
I tried using Threads But I am getting exception Is there any way to show the progress ring for few seconds
—

@bigworld12 It's more a SO question.

oh ok xd


Fix try/catch not working

Promises need to be async functions or else if they get rejected they can't be caught.

Its 1am right now if you want any more details you'll have to wait until i wake up


config: fix dfp config validation

Commit Message: fix DFP not doing san/sni checks with new style upstream config
Risk Level: high. people with broken configs will now have them rejected
Testing: updated tests
Docs Changes: n/a
Release Notes: inline

@mattklein123 I think this fixes the issue we had with Envoy Mobile.  Normally I'd runtime guard the new validation but it may happen before runtime, and arguably allow_insecure_cluster_option has been around so offers a similar level of "theoretically already plumbed ways to make the error go way".  WDYT?

/wait


bugfix: add default domain for the raw image

Describe what this PR does / why we need it
bugfix: fix pull docker images failed when the image name without domain.
Does this pull request fix one issue?
Fixes #728

Describe how you did it
Describe how to verify it
Special notes for reviews

/test image


update fio wrapper to support greater than 1 numjobs

This update is to allow users to specify greater than 1 numjobs. removed greater than 1 check, and added a loop for processing log file for N number of numjobs.
@aakarshg
@dustinblack
@jtaleric
@bengland2

Sample of data in Grafana dashboard.
http://marquez.perf.lab.eng.rdu2.redhat.com:3000/d/-8bpuoNWk/fio-summary-with-rook-ceph?orgId=1&from=1571348598365&to=1571348867521&var-user=acalhoun&var-UUID=debug-fio-numjob&var-cluster_name=acalhoun&var-Operation=All&var-io_size=All&var-log_interval=1s&var-net_device=All&var-block_device=All&var-instances=All

Sample Grafana data with numjob set to 4. Test was 3 samples or write operations at 4KiB io size with a duration of 15 minutes each, and 32 servers.
http://marquez.perf.lab.eng.rdu2.redhat.com:3000/d/-8bpuoNWk/fio-summary-with-rook-ceph?orgId=1&from=1571353092644&to=1571356330861&var-user=acalhoun&var-UUID=debug-fio-numjob&var-clustername=acalhoun&var-Operation=All&var-io_size=All&var-interval=30s&var-net_device=All&var-block_device=All&var-instances=All

Looks like a bad rebase as if you like at file changes it shows a ton more changes that're already in master, can you please fix it @acalhounRH ? and just make sure that the only change noticeable is the one that you made?


feat(error): change Display for Error to only print top error

hyper's Error used to print the error source automatically, preferring to provide a better default for users who do not know about Report. But, to fit better with the wider ecosystem, this changes the format to only print the hyper Error itself, and not its source.
Closes #2844
BREAKING CHANGE: The format no longer prints the error chain. Be sure to
check if you are logging errors directly.
The Error::message() method is removed, it is no longer needed.
The Error::into_cause() method is removed.

Finally, amazing! Error printing where hyper is now part of the error stack will make so much more sense and blend in so much better from now on. Good decision :+1:


Show context in un-focused buffers

Hi, would be great to have an option for the context to persist whenever another buffer is focused.

Sure. I don't have much time to code these days but I'd accept a PR for it.

Would also like this feature.
Quickly checked if it would involve changing a line or two, but current code is wired around having always one (reusable) buffer and one window, implementing this will involve keeping track of a buf/win per win.

Same, is kind of annoying seeing the context disappearing when another buffer/window is focused, e.g. telescope, toggleterm, etc.


Allow JS to access clipboard

This PR enables JavaScript clipboard access for Linux, MacOS & Edge Chromium on Windows.
For Linux & macOS it enables both document.execCommand("paste) & navigator.clipboard, however for Edge Chromium only the latter.
I have not been able to find any info about enabling clipboard access for EdgeHTML so I assume it only works with a custom implementation. Since the Webview Runtime is dropping Q3 and will make the EdgeHTML integration obsolete it doesn't seem worth the effort though.

@abeMedia - can you review? I am really not sure why clang-format keeps on failing.

Sure thing. Will do later today.

If you run clang-format -style=file -i webview.h it should fix things automatically. It looks like there's an issue with where you put the * (e.g. ICoreWebView2* sender instead of ICoreWebView2 *sender) and then your editor might be putting extra whitespace on line 933

Have fixed the formatting. Think we're ready to merge

Thankyou!

No, thank you! ;)

cool😉

I just noticed that on Gtk (Fedora Linux) middle-button click does a paste from the clipboard (i.e. CLIPBOARD), but it should do a paste from the current selection (i.e. PRIMARY).

I just noticed that on Gtk (Fedora Linux) middle-button click does a paste from the clipboard (i.e. CLIPBOARD), but it should do a paste from the current selection (i.e. PRIMARY).

This is most likely the default in GTK since all this PR does is enable GTK's native clipboard support.

"This is most likely the default in GTK since all this PR does is enable GTK's native clipboard support."
Looks like you're right - using epiphany has the same problem.


Support yolo v4

Hi can you support yolo v4 in Yolo.Net

Hi,
Another user wrote that it works:
https://github.com/AlturosDestinations/Alturos.Yolo/issues/161


Include side scrolling in admin listing pages at its core

Is your proposal related to a problem?
Yes, it is. I find frustrating to extend models (specially models related to users, people, business, and so on) that usually need extra fields (e.g., occupation, education, address details, field work, etc.) only to realize admin listings pages do not automatically activate side scrolling. More than 10 fields (depending on the characters size of them) do not fit withouth braking the page or hiding fields in the right side of the viewport).
Describe the solution you'd like
I don't have a solution to this problem. I suspect it could be solved with hooks, but to my vague understanding of frontend development, given that side scrolling a wide table is a pretty basic feature that just about anyone might need in the near future, I believe this should be solved at the core.css of Wagtail. It should not be left to customization, as to avoid adoption frustrations.
Describe alternatives you've considered
I looked at Wagtail docs to see if there was a way to hook admin to a custom css, but I am not that experienced with neither Wagtail of CSS. I am trying to extend Wagtail to a full blown service marketplace. So it needs quiete a lot of work.
Additional context
I have posted this issue at Stackoverflow as a question as well here with some pictures to ilustrate the problem.
Recently I tested extending the People model found at Wagtail Bakery demo, instead of extending with my own models. Unfortunately the problem persists with Bakery models as well.

Hello @biofsphere, as part of Outreachy winter cohort I would love to put in my efforts to this issue, Can I contribute?

I suppose you can. I wish I could. But I did not reach that skill level yet.

can you please indicate where is exactly you facing this issue on which page ?

The issue is not page specific. It happens whenever a model with enough columns is brough into Wagtail. The admin page overlap the far right columns with the filters area.

The issue is not page specific. It happens whenever a model with enough columns is brough into Wagtail. The admin page overlap the far right columns with the filters area.

Hello @biofsphere .. could you clarify should I make these changes ?

@AnishaSingh0118 The screenshot you've posted doesn't seem to relate to this issue.
(To be clear - @biofsphere is just the reporter for this issue, not a member of the Wagtail core team, and is not in a position to advise on what you should work on.)

@AnishaSingh0118 The screenshot you've posted doesn't seem to relate to this issue.
(To be clear - @biofsphere is just the reporter for this issue, not a member of the Wagtail core team, and is not in a position to advise on what you should work on.)

Oh, ok may be i posted the wrong image. I will update on this.

@biofsphere still this problem is there?
if yes, I like to work on it.

@yashp4858 the best way to confirm the issue is to replicate it yourself with the given details.
A similar issue was recently reported in #11675, so yes, this is still valid.


Not getting density value for tiff files

I am not able to see the density value from tiff file but it works fine with jpg and png files.
const image = sharp(fileResult.data);
const metadata = await image.metadata();
{
format: 'gif',
size: 24521,
width: 307,
height: 290,
space: 'srgb',
channels: 3,
depth: 'uchar',
isProgressive: false,
paletteBitDepth: 8,
pages: 1,
loop: 1,
delay: [ 100 ],
background: { r: 0, g: 0, b: 0 },
hasProfile: false,
hasAlpha: false
}

format: 'gif',

This looks like the metadata from a GIF image rather than a TIFF image.

sorry its my bad. please ignore this one, i have checked for tif file and its coming. Thank you

Its working as expected


Import HRQ into HNC (disabled by default)

This implementation of Hierarchical Resource Quotas (HRQs) is based on
the implementation from the GKE Hierarchy Controller.  It's not a
straight import since the GKE version was deployed as a separate
workload, but I've made minimal adaptations to get it to fit into HNC.
Tested: This has only been very lightly tested in HNC so far. I've
imported all the integ tests and E2E tests, and they all pass, but I
certainly wouldn't recommend that anyone use it just yet. The default
manifest includes the HRQ CRD and permissions but nothing else (notably,
the HRQ webhooks), and one feature - the periodic resync of HRQ usages -
is not yet implemented (I'll do that in a followup PR).

/assign @rjbez17
/cc @erikgb

/lgtm

/lgtm

Third time's the charm


motidy extensions in content/zh/docs/reference/glossary/extensions

zh-trans: motidy extensions in content/zh/docs/reference/glossary/extensions
Update: motidy extensions in content/zh/docs/reference/glossary/extensions
Co-Authored-By: lpf7551321

/assign @tengqm

/lgtm
/approve
Thanks for the fix.


getUserInfo returning 404 to listen() in a chat with >4 people

Hello, I get a 404 error on the console whenever there's a message sent to a group chat.
It still happens when there's nothing on the login callback function.
Same problem on the last stable version, and git version.
Here's the result of adding console.log(data) on utils:505:
http://pastebin.com/raw/3n9b4Bbp

Hey @ErmanSayin, I just tried on my side and sending a message works. Could you login, do something like fs.writeFileSync("someAppState.json", JSON.stringify(api.getAppState()), 'utf8'); and send me the file at<EMAIL_ADDRESS>I should be able to login using that cookie on that account and test it out. If you feel like revoking access you can simply login and then call api.logout and it'll invalidate that cookie.
It's due to /chat/user_info being an invalid url for some reason. Can you try sending a message to a chat with multiple people?

@bsansouci Oh sorry, I meant when someone else in a group chat sends a message. It works fine on single-user conversation.

Ah well that doesn't change much haha. In either case the problem seems to be in getUserInfo (whether it's called from listen or from sendMessage).

I kinda got around the issue by hardcoding the group ID in the code so listen doesn't use getUserInfo when there's a message

The cookies stopped working for me. I think they get invalidated as soon as you re-login with the same account. If you want me to explore a little more on my side you can send me the actual credentials so I can login and try things. I find this issue very weird because I don't understand how an endpoint like /chat/user_info can return 404 for you and not for me.

After doing some looking into this issue, it looks like the culprit is the hack to retrieve the list of participants from the html of the page here.
I would recommend making a change to make a call to the thread_info.php (the same endpoint as called by getThreadHistory).  This seems to return the full list of participants under payload.threads[0].participants when called as follows with the threadID and the current userID.
threads[thread_fbids][0]:<ThreadID>
messages[thread_fbids][<ThreadID>][offset]:0
messages[thread_fbids][<ThreadID>][timestamp]:
messages[thread_fbids][<ThreadID>][limit]:10

@ErmanSayin @asdfasdfvful can someone sync to master and verify that this commit fixes the issue?

@Schmavery all I need to do is npm install facebook-chat-api again correct? I did that and I'm still getting the same error

I deleted the node_module files and reinstalled it just to make sure. Here is the log in case something changed
http://pastebin.com/Pi3bd5yB

@Schmavery listen works for me, although sendMessage is broken, no errors

@asdfasdfvful remove facebook-chat-api from node_modules, then do git clone https://github.com/Schmavery/facebook-chat-api.git, then do npm update inside the new facebook-chat-api folder

Thanks a lot to all of you! It's fixed

Thanks for the confirmation guys.  I'll push to npm tonight.


Add Traditional Chinese Translation

Add Traditional Chinese Translation

Sorry. Translation is not actual. Latest version support Integration GUI Options

Sorry. Translation is not actual. Latest version support Integration GUI Options


Add Anox

Anox are an upcoming team looking to make their mark during Epicenter, if they qualify.

Thanks! Great to see you still looking out for new teams <3

np! And dont worry, I will always look for new teams.
On Wed, Oct 5, 2016 at 12:12 AM, Oskar Risberg<EMAIL_ADDRESS>wrote:

Thanks! Great to see you still looking out for new teams <3
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kokarn/csgo-data/issues/171#issuecomment-251599472,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARfY4nLWkiqaVOMisW19h20CZBu1_5GHks5qw03SgaJpZM4KOZ3s
.


Add SortingStrategy in Queue api

What type of PR is this?

/kind feature
/kind api-change
What this PR does / why we need it:
Add SortingStrategy in Queue api
Which issue(s) this PR fixes:

First part #8
Special notes for your reviewer:

I need to make sure I'm understanding this correctly. By capacity level policy do you mean within or across queues?
If it's within a queue, I think we can set the policy in the capacity and when we want to create a new queue, the queue will inherit it from the capacity.
If it's across queues, that's addressing fairness rather than starvation. It can't solve the problem here in #46

Think of Capacity as a "global" queue of all the queues pointing to the capacity; so the order should be enforced on all workloads sent to the same capacity even if they were submitted to different queues.

I also think a queueing strategy at the capacity level is needed. But there are still some things to discuss here. Could you give more comments for it? @ahg-g @alculquicondor
Personal opinion:
I think the strategy at the capacity level is to sort between multiple Queues, e.g. which Queue's workloads we schedule first. The strategy at the queue level is to sort within the queue, such as which workload needs to be scheduled first.
If the strategy at the capacity level act directly on all workloads belongs to the capacity, This way the queue does not serve the purpose of dividing the tenants. A tenant submits a lot of workloads before others so that no other tenant's workloads can be scheduled. This is no different from the one-to-one correspondence between capacity and queue.

Given the above, the namespaced Queue API wasn't meant to offer isolation between tenants since tenants could be given the permission to create/delete queues, and it is not something always limited to the Batch Admin.

Thanks for your detailed introduction. @ahg-g  If this is our design purpose, I got it. The queue is not the isolated unit, the capacity is the isolated unit. Queue may be a classification for jobs under the same tenant. Right?
If so, I wonder if we still need to set up an Internel.queue(heap) for each queue. Shouldn't we rather need to only set an Internel.queue(heap) for each capacity?

If so, I wonder if we still need to set up an Internel.queue(heap) for each queue. Shouldn't we rather need to only set an Internel.queue(heap) for each capacity?

Yes; perhaps Capacity is confusing as a name, may be we should call it ClusterQueue (synonym with ClusterResourceQuota, the cluster-scoped RQ from openshift).

If so, I wonder if we still need to set up an Internel.queue(heap) for each queue. Shouldn't we rather need to only set an Internel.queue(heap) for each capacity?

Yes; perhaps Capacity is confusing as a name, may be we should call it ClusterQueue (synonym with ClusterResourceQuota, the cluster-scoped RQ from openshift).

@alculquicondor is this going to be a significant change? if so, can you suggest a simpler path? perhaps the two step ordering aldo suggested earlier could be one step in that direction.

Yes; perhaps Capacity is confusing as a name, may be we should call it ClusterQueue (synonym with ClusterResourceQuota, the cluster-scoped RQ from openshift).

Maybe ElasticQuota or ClusterElasticQuota ? elastic indicates resource sharing? Also there is a difference in nomenclature with ResourceQuota or ClusterResourceQuota?

Quota in the name doesn't clarify that this is a cluster-scoped queue; while it is not unusual to associate "Queue" with usage limits. Also, we want to introduce budgets, not just quotas (assuming quota is defined as a limit at a specific point in time)

Also there is a difference in nomenclature with ResourceQuota or ClusterResourceQuota?

ResourceQuotas are namespaced objects, ClusterResourceQuotas are not (in other words, they are cluster-scoped)

is this going to be a significant change?

Do you mean having a single heap (not saying queue to avoid confusion) per Capacity? I think it is a reasonable simplification. We will still need a heap per Queue once we implement limits at that level, but at the moment they are not providing much.
It will be significant code moving around, but not much re-implementation. Better now than later.

Thanks, then I suggest we do the following:

Move the API to Capacity
Introduce a single heap per capacity to implement the API

They probably need to happen in the opposite order. I would like to do 2, if you don't mind @denkensk

@alculquicondor  Don't mind, and could you provide some basic implementation at your first pr?
That way I can do other work on efficient re-enqueue in parallel. Thanks. 😄

They probably need to happen in the opposite order

I think the order may not be so strict, we can merge this pr first (because it's ready) and don't use it.
and then introduce a single heap per after that.

/retest

/lgtm


Failed to parse SourceMap Error

From some point, I keep getting this error from the console.
Breakpoints seem to point at wrong points in chrome developer tools because of this.
Any ideas?

I've also been getting this the last day or two

I have the same error in the Chrome Console. I'm using Version 51.0.2704.84 (64-bit) of chrome and my Webpack config file is updated from this commit : https://github.com/davezuko/react-redux-starter-kit/commit/fedfd79f0795cb0aa561424d28ce3334be3e878b

Do you think it's Chrome-specific issue or webpack is somehow involved too?

I fixed this by switching to the Chrome Dev release channel. I think this is a Chrome issue (at least, mine was). Maybe there's some specific bug that this project triggered, but it appears to be fixed upstream in Chrome.

I had similar problems in a different project, and was able to solve it with a small change to style-loader.  See here:
https://github.com/webpack/style-loader/pull/132

Appears fixed in Chrome 52.0.2743.82


Support quoting parameter names

Changes
/kind feature
This change plumbs through support for quoting user-provided names during variable resolution as proposed here.
In addition to $(params.foo) you can now use $(params."foo"), which is useful for disambiguation when the name contains . characters (e.g. $(params."dev.tekton.foo")).
I have updated unit tests, and added a minor update to docs, but if there are more tests or docs that should be updated, please send me pointers.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[ ] Commit messages follow commit message best practices
[ ] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Support quoting user-provided names during variable substitution, e.g. $(params."foo") or $(results."bar".path)

cc @vdemeester @afrittoli @ImJasonH

Something strange is going on, both of those passed.  I think in the past this correlated with Prow being overloaded?

/retest

This feature addition feels a tad under-specified to me.  Is this intended as a proposal or do you want us to proceed on merging this as-is?
Here's what I'm gathering from reading the code: This change affects params, workspaces, results and resource variables.  From an initial scan it doesn't look like we've added this support to context variables, for example.  Only certain portions of variables are quotable (e.g. "resources.%s.%q.%s" is supported but not "resources.%q.%s.%s"; "workspaces.%q.%s" is supported but not "workspaces.%q.%q").  The doc atm doesn't capture these ambiguities or explain the reasoning.  Some apply tests have been updated to remove the inputs. prefix, which might mean we're dropping a bit of coverage of backwards-compatible behaviour - unclear to me atm.
I'd like to throw another design in to the ring: support bracket notation instead, e.g. params["my.param.with.periods"] which could in turn be taken a step further to array param subscripts ala params.myparam[1] or params["my.array.param.with.periods"]["1"] or something similar.  This isn't so much to dissuade you from running with your design, but I reckon there's enough conceptual room here to at least describe some alternatives in a PR, say why we discount them, and get some conversation going around it.
TL;DR I'm wary of lgtm'ing this without a bit of discussion first.  It might even be TEP-worthy?  Curious what other folks think @tektoncd/core-maintainers

/hold

"resources.%s.%q.%s" is supported but not "resources.%q.%s.%s"

The intention was to support quote all user-sourced names, there are a few of these (some I'm adding) where the %s is used for built-in strings.  In the example above, my inference was that the first %s was generally used for "inputs" or "outputs", which is perhaps incorrect.
I am happy to discuss this further, but nobody was discussing anything in the linked issue.  I'm glad this triggered some 😉

On TEPs, perhaps it is worth framing this as an incidental aspect of the broader idea I think we should pursue, which I have roughly sketched here: https://github.com/tektoncd/pipeline/issues/3590#issuecomment-738051808
Ultimately, without that, I have effectively no energy to pursue this further.


Problem with import seems to be corrupted on release 23 when coming from 22

Problem with import seems to be corrupted on release 23 when coming from 22
I exported from my phone as a json from v22 into another android system which had v23 the latest. Keys show imported successfully and all showed up but none of the one time pass codes work for 2fa..
I will be sticking with v22 until this is resolved.
This problem is reproducible and from memory this may have happened with other versions in the past by virtue of the same method.

This turned out to be another problem. Bluestacks has a glitch that when the apk is installed externally this json import becomes corrupt no matter what (no error code just incorrect otp). However, the fix to this is simply to install from Fdroid inside the emulated os.


Check LDaCA profile conformance for OMAA crate

LDaCA - which we're ultimately targeting - follows the ldac-profile for structuring collections.
Options:

feed back to Symplectic that the OMAA crate should also adhere to LDaCA
ignore LDaCA for now and get the extensions working
do a preprocessing between Symplectic and Oni to make the crate LDaCA compliant

Deliverable for this issue is documentation of the problem and a decision for the above

Duplicate


Mario can go through some block by wind

Wind doesn't use speed or physics, it just doesn't move him if there are tiles in the way

ed14ae89792efe5c27dae5dfe29a908e17b0cdd6

Hey, not done yet, it still has some blocks can go through.

Ice block

Oh OK, but you still should fix the ice block and muncher (sorry because I say after you fixed)


importing single files doesn't work

you can't do #import "Sort";
seems like we need to check single files in the module directory as well as folders.

this works now!


Cricket Score WhatsApp Bot🏏

Prerequisites

[X] I am a GSSoC-22 Participant
[X] I checked to make sure that this issue has not already been filed

Description
I want to add Cricket Live Score WhatsApp Bot which will be made using Python . It will update Cricket live Score through your whatsapp
Tech Stack
Python

@heet-kumar please assign


Wrong version in VS2015?

I just installed Code Contracts version 1.9.10714.2 having VS2015 installed as well, but inside VS2015 it displays as version 1.8.10107.10 instead. It displays the correct version inside VS2013 though.
Is this by design or is this a bug? Or are there two versions (for VS2013 and VS2015) only packaged inside the same installer?

Known issue, look fx at https://github.com/Microsoft/CodeContracts/issues/411


Use modified tailscale cli arguments for proxy

Proposed Changes
SSIA
Related Issues
partially fixes #287

Closing in favor of a better solution.


If a contact custom field with Name that matches NPSP field (after namespace) exists, error in Contact Merge and Manage Household

Thread: https://powerofus.force.com/0D58000002eAJYw
Steps to reproduce.
Create custom Contact field - label Deceased, Name - Deceased (Deceased__c)
Clone a contact, and then merge in Contact Merge tab
Error: Failed to query contact information. Error: System.QueryException: duplicate field selected: npsp__Deceased__c

**lurch: add

Tracking W-010021

This also appears to be an issue with the Manage Household page. Any custom field with the same name as a NPSP field after the namespace prefix.

We encounter this issue with some regularity with NGOC. I wrote about it here: https://powerofus.force.com/0D58000002HCTYA
Our approach has been to treat it as a platform shortcoming and have customers give different API names to their custom fields.
The only approach that I know of for an ISV to take is to "faux-namespace" fields, and all the references to them, eg, inside one's NPSP dev org, call a field npsp_Deceased__c, so that when packaged, the field's API name is npsp__npsp_Deceased__c. Kind of ugly. And not foolproof - if someone created a field called npsp_Deceased__c in their org you'd still have a conflict.
I'll be interested to see if you have a better alternative!

@tet3 thanks for the feedback! What's interesting here is that it's a new issue introduced in the push of 3.71 on Tuesday night/Wednesday morning. These orgs had these competing custom fields before and didn't have this problem. Something new is setting it off.

we recently updated our API version, so that may have exposed the issue.
Dave
David Habib | Lead Member of Technical Staff | salesforce.org
On Thu, Apr 21, 2016 at 2:45 PM, Judi Sohn<EMAIL_ADDRESS>wrote:

@tet3 https://github.com/tet3 thanks for the feedback! What's
interesting here is that it's a new issue introduced in the push of 3.71 on
Tuesday night/Wednesday morning. These orgs had these competing custom
fields before and didn't have this problem. Something new is setting it off.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/SalesforceFoundation/Cumulus/issues/2056#issuecomment-213125424

Hi Team,
Just tried to merge a contact and ran into the issue you're describing.  Never had before (going to what  Judi just said).   Our custom field is Deceased__c.
Any workaround you suggest in the meantime as you're looking into this further?
Thanks!
Jodi

@JodiNA - rename your custom field's Name (not Label) to something else, such as Deceased_Custom (which would give it the API name of Deceased_Custom__c)

Thanks, I'll try that.
On Fri, Apr 22, 2016 at 3:26 PM, Judi Sohn<EMAIL_ADDRESS>wrote:

@JodiNA https://github.com/JodiNA - rename your custom field's Name
(not Label) to something else, such as Deceased_Custom (which would give it
the API name of Deceased_Custom__c)
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/SalesforceFoundation/Cumulus/issues/2056#issuecomment-213561087

--
Jodi Nemser-Abrahams
Information & Data Manager
Keshet
284 Amory Street
Jamaica Plain, MA 02130
617.524.9227x111
Web: www.keshetonline.org
Facebook: www.facebook.com/KeshetGLBTJews
Twitter: @KeshetGLBTJews https://twitter.com/KeshetGLBTJews
Blog: www.myjewishlearning.com/category/keshet/
Subscribe for LGBT Jewish news, resources and inspiration in your inbox
http://bit.ly/1E6oJYK.
*Registration http://www.keshetonline.org/teenshabbaton/ for our first
ever West Coast Shabbaton for LGBTQ and ally teens is open! *Find more
information here http://www.keshetonline.org/teenshabbaton/.
Stand up for transgender rights. Sign Keshet's petition
https://www.keshetonline.org/work/petition-in-support-of-full-transgender-rights-in-massachusetts/support-transgender-rights-in-ma/
calling
Massachusetts legislators to support “An Act Relative to Transgender
Anti-Discrimination."
A teen. A mom.
See how we are transforming the Jewish community together
https://youtu.be/3b8NL5jwt4o.

Included in beta release version 3.72 (Beta 2) and higher

Included in production release version 3.72

Re-opening as this issue is back (due to the API change?). See https://powerofus.force.com/0D58000002wIoed

**lurch: add

Tracking W-011266

Here's some code to help identify all clashing field names in your org

private static Set<String> getInstalledPackageNamespaces() {
    Set<String> namespaces = new Set<String>();
    for (AggregateResult ar : [SELECT NamespacePrefix FROM ApexClass WHERE NamespacePrefix != null GROUP BY NamespacePrefix]) {
        String namespace = (String) ar.get('NamespacePrefix');
        namespaces.add(namespace.toLowerCase() + '__');
    }
    return namespaces;
}

Set<String> installedNamespaces = getInstalledPackageNamespaces();
Map<String,SObjectType> describe = Schema.getGlobalDescribe();
public static Map<String, List<String>> findConflictingFields(String objectApiName) {
    Map<String, List<String>> conflictingFields = new Map<String, List<String>>();

    Map<String, Schema.SObjectField> fieldMap = describe.get(objectApiName).getDescribe().fields.getMap();

    Map<String, List<String>> potentialConflicts = new Map<String, List<String>>();

    for (String fieldName : fieldMap.keySet()) {
        String namespacedFieldName = '';
        String unnamespacedFieldName = fieldName;

        for (String namespace : installedNamespaces) {
            if (fieldName.startsWith(namespace)) {
                namespacedFieldName = fieldName;
                unnamespacedFieldName = fieldName.substringAfter(namespace);
                break;
            }
        }

        if (!potentialConflicts.containsKey(unnamespacedFieldName)) {
            potentialConflicts.put(unnamespacedFieldName, new List<String>());
        }
        potentialConflicts.get(unnamespacedFieldName).add(fieldName);
    }

    for (String unnamespacedFieldName : potentialConflicts.keySet()) {
        List<String> fields = potentialConflicts.get(unnamespacedFieldName);
        if (fields.size() > 1) {
            conflictingFields.put(unnamespacedFieldName, fields);
        }
    }

    return conflictingFields;
}

public static void printConflicts(String objectApiName) {
    Map<String, List<String>> conflicts = findConflictingFields(objectApiName);

    if (conflicts.isEmpty()) {
//        System.debug('No conflicting fields found for ' + objectApiName);
    } else {
        System.debug('Conflicting fields found for ' + objectApiName + ':');
        for (String fieldName : conflicts.keySet()) {
            System.debug('  Field name: ' + fieldName);
            System.debug('    Conflicting fields: ' + String.join(conflicts.get(fieldName), ', '));
        }
    }
}

for (String sObjectName : describe.keySet()) {
//    System.debug('Checking conflicts for object: ' + sObjectName);
    printConflicts(sObjectName);
}


Consider separation of lifecycle concerns with the collection controller

One of the philosophical points of view with the operator pattern is that the operator has a separate lifecycle from the software it manages. This lets you upgrade the operator without disturbing and of the existing software instances, and lets the operator orchestrate roll forward/roll back of a software instance.
The Kabanero instance controller adheres to this point of view, but the collection controller seemingly violates this point of view. We might consider factoring the collection controller off into another deployment at some point in the future.

My two cents on this.... I have been lumping the Kabanero controller and the Collection controller into one logical instance.  The Kabanero controller has logic that knows how to read an index.yaml and create Collection objects.  The Collection controller has logic that pulls the Kubernetes resources for a collection and creates the object instances (Pipelines, Tasks, etc).  They both sort of work in tandem - I can't imagine a situation where you would want to have one version of the Kabanero controller, but a different version of the Collection controller.
When I think about the two as a logical instance though, I can see the appeal of having a separate operator that manages versions of those two things together.  For example, having a new Kubernetes group operator.kabanero.io that contained an object called Instance which described which version of the kabanero/colleciton controller to get, and the URL for an index.  Someone would be able to use the operator to deploy a Kabanero instance which understood a v2 index.yaml in one namespace, and then another Kabanero instance which understood a v3 index.yaml in another namespace, but only have the actual operator installed one time.  The operator would pull one version of the controllers for one namespace, but another version of the controllers for the other.  The Kabanero operator might react to a new Instance by creating a Kabanero object in the namespace, and creating two Deployment objects, one containing a Kabanero controller at the requested level, and one containing the Collection controller at the same level.  Or perhaps one Deployment that contains both controllers.
On the other hand, the operator.kabanero.io group would really just contain the install logic for Kabanero.  All of the so-called "day 2" operations would be managed by the controllers.  I was thinking about new CRD types, for example a CRD that represented a refresh request (go look at the index and refresh/reconcile the contents, as the CLI would do).  However doing so would require the Kabanero instance to go look, which is handled by the Kabanero controller, so it would really be the Kabanero controller owning that CRD, not the operator.  Maybe that's enough - the operator controls versioning of the controllers, and the controllers handle everything else.

The changes being proposed in #288 will likely require this.  It would be good if we could have a new main() for the collective controller, and a new Docker container, but continue to source it from the kabanero-operator project (this project) in GitHub.
We should build a 0.3.0 collection-controller which retains its current behavior.  When we release the 0.4.0 operator, we can include this container in the 0.3.0 version, so that when deploying 0.3.0 kabanero using the 0.4.0 operator, the user will get the 0.3.0 collection controller behavior.  Then, for 0.4.0 and beyond, we'll build a new collection controller container at each release.


runtime error: invalid memory address or nil pointer dereference

I've started the container and pointed it to the output dirctory, but it crashes:
2024-11-17T21:33:55.203838889Z time="2024-11-17T21:33:55Z" level=info msg="Start watching: /output"
2024-11-17T21:35:12.703855921Z time="2024-11-17T21:35:12Z" level=info msg="New file to upload:/output/pl_scan_2024-11-17 21.35.04.pdf"
2024-11-17T21:35:12.711801367Z panic: runtime error: invalid memory address or nil pointer dereference
2024-11-17T21:35:12.711863858Z [signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x62fc2f]
2024-11-17T21:35:12.711886032Z
2024-11-17T21:35:12.711905848Z goroutine 7 [running]:
2024-11-17T21:35:12.711929241Z main.uploadFile({0xc000120150, 0x27}, {0xc00001c036, 0x28}, {0xc00001c008, 0x28})
2024-11-17T21:35:12.711974592Z 	/go/src/github.com/Celedhrim/scantopl/scantopl.go:62 +0x26f
2024-11-17T21:35:12.712275125Z main.main.func1()
2024-11-17T21:35:12.712310093Z 	/go/src/github.com/Celedhrim/scantopl/scantopl.go:119 +0x27d
2024-11-17T21:35:12.712331177Z created by main.main
2024-11-17T21:35:12.712349777Z 	/go/src/github.com/Celedhrim/scantopl/scantopl.go:107 +0x38

Any idea, what i can do to fix that?


Adding Azure extension package to /logs trigger

Summary of the pull request
References and relevant issues
Detailed description of the pull request / Additional comments
Validation steps performed
PR checklist

[ ] Closes #xxx
[ ] Tests added/passed
[ ] Documentation updated

/logs

eeeyyy it works! :)

When we use the trigger and don't need all three logs, let's try to remember to go back and edit the comment to only include what is needed to make life easier for folks reporting issues. Most bugs in this repo shouldn't need any extension logs (if they do, the bug maybe should be transferred to the correct repo).


Replaced init.sql from docker/db folder with hardlink pointing to file in resource folder

and added statements from old init.sql script.

not relevant anymore, I used the file some time back


Fix connect string for ssl

Current connect string to libovsdb always passes tcp.
Hence, ssl will not work if client wants to use ssl.
This commit fixes the same.

LGTM


Lambda manager bugfix

Motivation and context

Constantly increasing RAM consumption in cvat_worker_low docker container while using automatic annotation with detector model in nuclio.
How has this been tested?

It was tested manually
Checklist

[x] I submit my changes into the develop branch
[ ] I have added a description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

@PMazarovich , thanks for your contribution!