vagrant and DNS

Hi,
I am having trouble again with the DNS module with the latest version of the Ansible version:
vagrant up k8s-master
vagrant ssh k8s-master
vagrant@k8smaster:~$ kubectl get pods -o wide -A
NAMESPACE        NAME                                READY   STATUS             RESTARTS   AGE   IP           NODE        NOMINATED NODE   READINESS GATES
kube-system      coredns-fb8b8dccf-9sm5l             0/1     CrashLoopBackOff   12         35m          k8smaster
kube-system      coredns-fb8b8dccf-fjrfv             0/1     CrashLoopBackOff   12         35m          k8smaster
kube-system      etcd-k8smaster                      1/1     Running            0          34m   <IP_ADDRESS>   k8smaster
kube-system      kube-apiserver-k8smaster            1/1     Running            0          35m   <IP_ADDRESS>   k8smaster
kube-system      kube-controller-manager-k8smaster   1/1     Running            0          34m   <IP_ADDRESS>   k8smaster
kube-system      kube-proxy-88fnd                    1/1     Running            0          35m   <IP_ADDRESS>   k8smaster
kube-system      kube-scheduler-k8smaster            1/1     Running            0          35m   <IP_ADDRESS>   k8smaster
ovn-kubernetes   ovnkube-db-58cc89dfb9-zdl5g         2/2     Running            2          34m   <IP_ADDRESS>   k8smaster
ovn-kubernetes   ovnkube-master-d54d59d55-5jzkq      2/2     Running            4          34m   <IP_ADDRESS>   k8smaster
ovn-kubernetes   ovnkube-node-vm7g7                  0/3     Pending            0          34m
Any idea what is wrong? API server seems reachable. Let me know if you want more specific information...

Apparently -init-gateways and -gateway-local options are now enabled by default in vagrant/provisioning/setup-master.sh script, so this is not the problem anymore.

It appears that ovnkube-node fails to run with 2 gigs of memory:
vagrant@k8smaster:~$ kubectl -n ovn-kubernetes describe pod/ovnkube-node-vm7g7
[...]
Events:
Type     Reason            Age                      From               Message

Warning  FailedScheduling  3m21s (x150 over 3h44m)  default-scheduler  0/1 nodes are available: 1 Insufficient memory.
Doubling memory for the master VM fixes this problem but one of the core-dns services remains in crash loop:
kube-system      coredns-fb8b8dccf-cbf8n             1/1     Running            5          25m   <IP_ADDRESS>   k8smaster
kube-system      coredns-fb8b8dccf-lmttf             0/1     CrashLoopBackOff   9          25m   <IP_ADDRESS>   k8smaster

Btw, the slaves did not join the master automatically, it seemed like they need to be manually joined?

You mean kubelet? If so, the latest vagrant should let you join automatically.
In general, daemonsets with community image is right now broken. Looks like we went out of sync. I have asked a dev to update it to the latest and then I will try again.

Joining was not handled automatically. It was only working when I did it manually.
About the DNS issue, some logs from the coredns:
2019-04-10T10:28:58.133Z [ERROR] plugin/errors: 2
2712880051517785174.537626345269378054. HINFO: read udp
<IP_ADDRESS>:42005-><IP_ADDRESS>:53: i/o timeout
E0410 10:29:17.117971       1 reflector.go:134]
github.com/coredns/coredns/plugin/kubernetes/controller.go:322: Failed
to list *v1.Namespace: Get
https://<IP_ADDRESS>:443/api/v1/namespaces?limit=500&resourceVersion=0:
dial tcp <IP_ADDRESS>:443: i/o timeout
From the command line, I get -403 from the wget:
$ kubectl --namespace kube-system exec -ti etcd-k8smaster /bin/sh
wget "https://<IP_ADDRESS>:443/api/v1/namespaces?limit=500&resourceVersion=0"
Connecting to <IP_ADDRESS>:443 (<IP_ADDRESS>:443)
wget: note: TLS certificate validation not implemented
wget: server returned error: HTTP/1.1 403 Forbidden


Ensure new blocks are marked complete only when strict finality is reached

This PR introduces a small collection of state flags which are carried around with blocks being executed and accumulated.
The state is held in a type named HotBlock - i.e. a new block which is currently being worked upon.  The state is primarily used in the reactor's dispatch_event via the HotBlockAnnouncement.  This announcement is made by the ContractRuntime after executing a FinalizedBlock and by the BlockAccumulator after storing a block which has just reached sufficient finality.
The introduction of this state has allowed for the removal of some state from the BlockAccumulator and also should ensure that actions such as executing a block, storing a block or marking it complete are all done only once per block.
It also has allowed the node to avoid needlessly gossiping new immediate switch blocks (all nodes going through an upgrade create the immediate switch block, not just the validators).
Closes #3520.

bors merge


Fix for Linux Builds

Modified build process for Linux so that it now runs successfully
Bumped restify inside of packages/app/main, packages/emulator/cli, and packages/emulator/core

As a side effect to this, had to add option handleUncaughtExceptions: true to restify.createServer() calls because it is no longer a default setting in restify 5.x.x

Pull Request Test Coverage Report for Build 709

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 49.301%

Totals

Change from base Build 670:
0.0%

Covered Lines:
3227

Relevant Lines:
5836

💛  - Coveralls


SPOI-11412 Added walkthrough document for S3 to Redshift application template

@deepak-narkhede Please review and merge.

Looks good to me.


Bittensor 6.6.0: btcli st show returns "object is not iterable" error

Describe the bug
Although btcli st -h lists "show" as an applicable command, typing 'btcli st show' returns "TypeError: 'subtensor' object is not iterable".
To Reproduce

Verify current version is 6.6.0
Type 'btcli st show --wallet.name (name)' or just "btcli st show" and follow the prompts.

Expected behavior
The command should "...List all stake accounts for wallet" as per the help command.
Screenshots

Environment
MacOS, Bittensor 6.6.0
Additional context
First reported in the Discord, in the French language channel, by user "Patubzh29"

same here. delegating a stake works, but all staking-commands ultimatively fail with this error messages.
(arch x86_64 with python venv. bittensor=6.6.0, python=3.11.6)

Fixed as of 6.6.1


horizontal lines low contrast in dark mode

Horizontal lines have low contrast in dark mode and are nearly invisible. I tried with different primaryHues, but no luck. (some elements like buttons have poor contrast when using colors like dark blue as primaryHue, but work good with other colors. However, the hr color has poor contrast in both)
Maybe switch color system to HSLA (instead of RGBA), so the user (read developer) can set a primary hue (H) and then the elements are colored with various lightness, saturation and alpha.

pr welcome

Is nextra using tailwind colors under the hood?

I took a look at the source code, and saw that horizontal lines are gray (not changing with primaryHue), so I just changed gray-900 to gray-800 (maybe gray-700 is better?) to make it more visibile.


Building BTC TX with an address having excessive UTXOs takes forever

Issue
A transaction with specific from address can take forever to build, for example:
await sendBtc({
  from: 'tb1quqtqsh5jrlr9p5wnpu3rs883lqh4avpwc766x3',
  tos: [
    {
      address: 'tb1quqtqsh5jrlr9p5wnpu3rs883lqh4avpwc766x3',
      value: 1000,
    },
  ],
  source,
});

What happens:

The construction process contains a loop to estimate the fee of the transaction
In each loop, the BtcAssetsApi.getBtcUtxos() API is called to get the latest UTXO[] list
Each request can take 8-15 seconds, and in each loop, more UTXOs are collected to the inputs
If the inputs length increased, the estimated fee is also increased, causing another round of the loop
The condition to break the loop takes a very long time to be satisfied (due to the INSUFFICIENT_UTXO error)
The loop (tested by @Dawn-githup) can take 40+ minutes to fail, which is clearly abnormal

Investigation & resolvers

[ ] Should the BtcAssetsApi to be queried once per build to avoid long waiting time of requests?

The UTXO[] list can be updated during the construction, should we worry about it?

[ ] There's only a 1000 satoshi output in the outputs, not a huge cost at all, so why won't the loop stop?

Is it because some bugs remain in the pay fee process?

Should the BtcAssetsApi to be queried once per build to avoid long waiting time of requests?

Yes, we should query once per build and check the inputs UTXO after the transaction is built.
The BtcAssetsApi can provide a new API /bitcoin/v1/tx/:txid/outspend/:vout to return the spending status of each UTXO. It would be faster and more efficient.

Debug report
Ran some tests today:

For the example mentioned above, the total loop should be 6 times.
In each loop, the BtcAssetsApi.getBtcUtxos() API is used for querying UTXO[].
In each loop, the BtcAssetsApi.getRgbppAssetsByBtcUtxo() is used for checking each input's corresponding RGBPP assets, and if the UTXO is bound with any, it's excluded from the collection process.

Step 2 takes about 8-15 seconds, and although a single request in step 3 doesn't take much time, for each UTXO, there is a request to check if it's qualified to be used as an input. The more inputs, the more requests, therefore costing more time.
Resolvers for the performance issue

BtcAssetsApi.getBtcUtxos(): Despite the improvements that will be applied to the btc-assets-api, the SDK can cache and reuse the result of the API within the scope of a single Txbuilder.payFee() call, instead of querying the UTXO[] list multiple times in the loop.
BtcAssetsApi.getRgbppAssetsByBtcUtxo(): We may also cache the result of this API to prevent querying the same UTXO multiple times in the loop, but for each UTXO, we MUST query at least once, so the overall time savings on this API could be small.

The value-cost trap
Even if all the above issues are resolved, the exmaple transaction is still not construct-able. Here's a log that shows how:
loop(1): time(16.99s) preFee(0) currentFee(13019) inputs(3)
loop(2): time(17.00s) preFee(13019) currentFee(54661) inputs(16)
loop(3): time(17.03s) preFee(54661) currentFee(185932) inputs(57)
loop(4): time(17.10s) preFee(185932) currentFee(605266) inputs(188)
loop(5): time(17.38s) preFee(605266) currentFee(1950218) inputs(608)
loop(6): time(18.87s) preFee(1950218) currentFee(6256922) inputs(1953)

You can see that in each round of the loop, the fee significantly increased. And in each loop, the transaction included more and more inputs. In the end, the transaction failed with the fee requirement of 6256922 satoshi, and it had included 1953 inputs in the transaction.
It was just a small transaction, with only a single goal: to transfer 1000 satoshi to himself. How could the transaction require 1953 inputs to be included, and it was still insufficient for paying the network fee? Simply put, it's because:

Each UTXO contained too few satoshi (mostly 1000 satoshi each), yet the fee rate was too high.
The more inputs were included in the transaction, the higher the network fee became.

This is like a trap; no matter how many UTXOs (with 1000 satoshi value) you put into the transaction, you can never satisfy the network fee requirement. Therefore, even though the transaction included 1953 inputs, it still lacked enough satoshi for paying the fee.

I think a possible solution to The "the value-cost trap" problem is to start with the estimated number of sats needed, rather than continually getting new UTXOs until demand is met.

It was just a small transaction, with only a single goal: to transfer 1000 satoshi to himself. How could the transaction require 1953 inputs to be included, and it was still insufficient for paying the network fee?

If this is a normal BTC transfer, maybe the BTC SDK could try to find a UTXO with larger value as input.
Coin Selection Algorithm: Some Bitcoin wallets and libraries use a coin selection algorithm to choose the UTXOs to spend in a transaction. These algorithms are designed to minimize the number of inputs required while still covering the amount being sent and the fee.


Any plan to port on Android?

It's the best one on iOS platform.  Hope port to Android in one day.

Unfortunately I'm not an Android Developer. So no plans till now.


Make sure the VSOCK system service loads the correct module

Signed-off-by: Zhuchen Wang<EMAIL_ADDRESS>
What this PR does / why we need it:
The VSOCK TLS improvement loads a different VSOCK module and causes the VSOCK feature broken
After merging PR #8889, VM creation with autoattachVSOCK failed. Libvirt complains about failed to open vhost-vsock device.
The host is GCE instance with Ubuntu 20.04 and the guest OS is also Ubuntu 20.04.
After debugging, it turns out that the code doesn't load the correct module in my setup.
lsmod | grep vsock
vmw_vsock_virtio_transport_common    32768  0
vmw_vsock_vmci_transport    32768  1
vsock                  36864  3 vmw_vsock_virtio_transport_common,vmw_vsock_vmci_transport
vmw_vmci               69632  1 vmw_vsock_vmci_transport

The correct modules should be
lsmod | grep vsock
vhost_vsock            24576  0
vmw_vsock_virtio_transport_common    32768  1 vhost_vsock
vhost                  49152  1 vhost_vsock
vsock                  36864  2 vmw_vsock_virtio_transport_common,vhost_vsock

Without PR #8889, the /dev/vhost-vsock device is accessed during the device plugin startup  and the vhost_vsock module should be loaded automatically when the first time the /dev/vhost-vsock device is accessed. Now, the VSOCK system service is started before the device plugin. Therefore, with the incorrect module loaded, the vhost_vsock module cannot be loaded due to modprobe: ERROR: could not insert 'vhost_vsock': Device or resource busy.
This PR simply opens the /dev/vhost-vsock before the system service listening on a VSOCK port to make sure the correct vhost_vsock module is loaded.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

Open `/dev/vhost-vsock` explicitly to ensure that the right vsock module is loaded

@rmohr

/ok-to-test

It is not guaranteed that the correct module is loaded, seems to be coincidence to me that it works this way? Can't the module be loaded after the device node is created?

It's this code that doesn't guaranteed the correct module. Since virt-handler starts the device plugin which handle over the devices, I think it's fine to have virt-handler to load the module. However, in this case, the system service is started before the device plugin, which causes the problem. I think if we move the system service after the device plugin startup, the problem can also be solved.

So the reason for the wrong module being loaded is that udev rules are not setup properly?

So the reason for the wrong module being loaded is that udev rules are not setup properly?

Almost. There are two triggers to load vsock modules:

A syscall socket(AF_VSOCK, ...)
Accessing the vsock device file

The complication is now this:
AF_VSOCK on socket calls is used for vmware vsock and for virtio vsock. The loaded modules decide which one will be used. The OS now has to decide which one to load when AF_VSOCK syscalls are happening. vmware has precendence here (not sure if on all kernels but at least on many). Probably for backward compatibility. And only one of the virtio drivers can be loaded at the same time.
If we however access the virtio vsock device file first, udev has a clear signal what we actually want, the virtio vsock driver.

Ok, that sounds reasonable. And could the device plugin manage the loaded modules (in the future)?

And it would be great if this explanation was included in the commit message to give some context.

I put the explanation in the commit message and the PR.

Thank you! LGTM for now.

I think we could in a follow-up improve the system service startup by, like the device-plugin, having a file-watcher.

Can we track this follow up somewhere? Is there an issue for it?
/lgtm
/retest

Can we track this follow up somewhere? Is there an issue for it?

Done: https://github.com/kubevirt/kubevirt/issues/9114

/approve

/test pull-kubevirt-e2e-k8s-1.26-sig-compute

/retest


Transfer repository ownership to SciTools

📰 Custom Issue

It's early days for geovista, which has just been born :partying_face:
The current plan is to bootstrap geovista here with an minimal stable core under ownership of https://github.com/bjlittle, before then transferring ownership of the repository to the https://github.com/SciTools organisation.
At the moment SciTools is slowly undergoing re-licensing from LGPL to BSD 3-Clause, and a refresh of its CLA. After this work is completed, and when geovista is "ready" it will be migrated to SciTools to live alongside its more mature and well-behaved sister cartopy.
More importantly, once geovista is under SciTools ownership, it can then be maintained by its awesome team of core developers :smile:

Looking forward to this! Do you think we could have a checklist in the main issue body of what would make GeoVista "ready"? Should make it easier for us to hold ourselves to account.

Bump

@trexfeathers I'm not going to create an exhaustive list here. I think that would be a bit counter-productive. Also, at the moment the line in the sand is quite fluid, and I'm totally okay with that.
However, I am using the  label in the this GH project to capture my current thinking on what I want to deliver.
Also, I don't see the point in transferring ownership too soon, otherwise I can't be as nimble and reactive as I am at the moment.
I think the decision of "when" will eventually become clear, and I'm in no particular rush to force that decision along atm.

@trexfeathers However, do keep nudging me. That should keep things healthy 😉
It's important that the migration happens 👍

This is probably a "perfect is the enemy of the good" situation. We have to make sure we recognise when GeoVista has passed the "good" threshold, and resist waiting for "perfect".

This issue is still important.

This issue is still important.


fix(output): adjustments for output text for different types of data

Resolves: #333

Closing and will revisit at a later time due to complexity.


benchtop: plumb fetch concurrency from cli

#192  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @pepyakin and the rest of your teammates on  Graphite


Clarify GitHub auto-token vs GitHub PAT

@jcbhmr can you clarify in the readme when a github token is needed to be specified? Whenever i see "github token" in a readme, i think of a PAT instead of the github action provided github token.

Originally posted by @Andrew-Chen-Wang in https://github.com/Andrew-Chen-Wang/github-wiki-action/issues/38#issuecomment-1552185948

I can try to use "${{ github.token }}" or "GitHub context token" or "GitHub auto-token" in these cases 👆 but I don't know how much good it would do since most of the text there is instructions on how to replace the ${{ github.token }} with your own Personal Access Token for cross-repo pushing permissions. I could elaborate on that and name the section something better like:

Cross-repo wikis
You can use this action to deploy your octocat/mega-docs repository to the octocat/mega-project repository's wiki tab! You just need to:

Create a custom GitHub Personal Access Token with the permissions to push to the octocat/mega-project repository. That's the target repo where your wiki pages will be pushed to the .wiki.git.
In the octocat/mega-docs repo (the source code for the wiki), you need to set the repository: option to repository: octocat/mega-project to tell the action to push there.
You need to set the token: option to the Personal Access Token that you created with the ability to push to the wiki Git repo. You can use repository secrets for this! Something like token: ${{ secrets.MY_TOKEN }} is good!

Here's an example:
{{and then a demo here}}

And then I could also put in a section about permissions like:

Permissions
In order to successfully push to the .wiki.git Git repository that backs the wiki tab, we need the contents: write permission. You can set this like so:
{{and then a demo here}}

Does that seem like what you had in mind?

I usually refer to github.token as "Auto-included GitHub Action token"
I meant a distinction between when to use this action token and when to use a PAT.


fixing links

links in docs were mixed case, but filenames were all lower. For example (Instructions)[Instructions.md] should be (Instructions)[instructions.md] since the filename is instructions.md.
Probably not a problem if on a Windows file system, but assuming GitHub is not.

Thanks for doing this, Larry, but this is already fixed in the gh-pages branch, which is where all the docs actually live. I really need to just delete the master branch. The docs are actually live at: http://microsoft.github.io/RTVS-docs/

Sounds good, closing this PR since it's fixed.


jQuery conflict with li a[href*=#]

Hey there, mainly stumbling over it through a jQuery version update in the latest WordPress 4.5, I realised your plugin is affected by a weak declaration including the hash character which should be escaped:
li a[href*=#] should be changed to li a[href*='#']
accordingly in order to work with the latest jQuery 1.x version. I added it manually in my local copy, but it would surely be nice to have it officially available through your repository :wink: .

Hi, I just merged pull request #45 which fixes the issue with hash character issue. It's also in master repo.

Currently line 63 still has the same problem. It must be escaped like this  menuItemsHref = $self.find('li a[href*="#"]'),.


Use darken for ctp-current in latte.

This is my poor elisp attempt at a fix for #75

I dont even wanna touch elisp, You my man are great.


affected/package: xml/encoding

What version of Go are you using (go version)?
1.19.5
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
windows/amd64
What did you do?
After running the snippet "https://go.dev/play/p/r7BVXxvAygX" on the input data
y
I get the output data generated by using the Encoder.EncodeToken
y
that is non-well-formed XML with a duplicated attribute name xmlns.
What did you expect to see?
y
What did you see instead?
y
Please fix.

Duplicate of #42807


[OpenApi] Pydantic Support

Adds pydantic support (closes #210 )

Codecov Report

Merging #240 (ecf56b3) into main (072b448) will increase coverage by 0.13%.
The diff coverage is 97.82%.

@@            Coverage Diff             @@
##             main     #240      +/-   ##
==========================================
+ Coverage   87.38%   87.52%   +0.13%
==========================================
  Files          38       39       +1
  Lines        3147     3190      +43
==========================================
+ Hits         2750     2792      +42
- Misses        397      398       +1

Impacted Files
Coverage Δ

goblet/tests/test_openapispec.py
94.24% <93.33%> (-0.12%)
:arrow_down:

goblet/resources/plugins/pydantic.py
100.00% <100.00%> (ø)

goblet/resources/routes.py
86.00% <100.00%> (+0.36%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Multiple dex files define Lcom/google/android/gms/internal/zzqf

:app:dexDebug
Unknown source file : UNEXPECTED TOP-LEVEL EXCEPTION:
Unknown source file : com.android.dex.DexException: Multiple dex files define Lcom/google/android/gms/internal/zzqf;
Unknown source file :   at com.android.dx.merge.DexMerger.readSortableTypes(DexMerger.java:596)
Unknown source file :   at com.android.dx.merge.DexMerger.getSortedTypes(DexMerger.java:554)
Unknown source file :   at com.android.dx.merge.DexMerger.mergeClassDefs(DexMerger.java:535)
Unknown source file :   at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:171)
Unknown source file :   at com.android.dx.merge.DexMerger.merge(DexMerger.java:189)
Unknown source file :   at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:502)
Unknown source file :   at com.android.dx.command.dexer.Main.runMonoDex(Main.java:334)
Unknown source file :   at com.android.dx.command.dexer.Main.run(Main.java:277)
Unknown source file :   at com.android.dx.command.dexer.Main.main(Main.java:245)
Unknown source file :   at com.android.dx.command.Main.main(Main.java:106)

:app:dexDebug FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:dexDebug'.
> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command '/Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home/bin/java'' finished with non-zero exit value 2

Fixed,
node_modules/react-native-fcm/android/build.gradel
change
compile 'com.google.firebase:firebase-core:9+'
compile 'com.google.firebase:firebase-messaging:9+'
to
compile 'com.google.firebase:firebase-core:9.2.1'
compile 'com.google.firebase:firebase-messaging:9.2.1'

This solved my issue. I was compiling a project with react-native-maps which was depending on:
  compile "com.google.android.gms:play-services-base:9.4.0"
  compile 'com.google.android.gms:play-services-maps:9.4.0'

Thank you!!

don't these dependencies belong in the gradle files (another step to installing I know, but what other option do we have?)  How else can you match all of these to 9.* for other libraries you have. In my case react-native-maps.

it's really werid issue,
i had com.google.android.gms:play-services-auth:9.4.0
And after I update play-services-auth to 10.0.1, problem solved.


Auto-completion not working

I'm using Windows 10 64bit with atom 1.0.19.
When starting atom, there's an warning in the console:

And after opened a solution and try to type in one of the .cs file, the auto-complete not functioning and errors appears in console:

@zmLGBBM is this still happening for you?  I think I may have fixed this one already.

I have just noticed this has started to happen for me.
Running v0.25.10

I think this perhaps the root cause: https://github.com/OmniSharp/omnisharp-roslyn/issues/296

Fixed via #563


email notifications about news comments should hyperlink to actual comment thread

I recieved this email:
Just a quick heads-up: testify
replied to you on Camper News.
You can keep this conversation going.
Just head back to the discussion here: http://freecodecamp.com/news/
learning-d3--essential-skills-for-the-javascript-programmer--mr-hassles-long-underp

the Free Code Camp Volunteer Team

the link takes me to the main news page.  Searching for "d3" took me to my original submission, but there was no additional comment from "testify".
Perhaps as a separate issue, commenting should bump the news item up in some way.

@adventurebear can you verify that the link you received in the email had a space between  http://freecodecamp.com/news/ and learning-d3--essential-skills-for-the-javascript-programmer--mr-hassles-long-underp? That is why the link wasn't working. Links shouldn't have spaces in them obviously, so if that was the case, we need to trim leading whitespace from titles.

I copied and pasted exactly as the Emil was so that's probably the cause. I
deleted it already though.
On Saturday, May 23, 2015, Quincy Larson<EMAIL_ADDRESS>wrote:

@adventurebear https://github.com/adventurebear can you verify that the
link you received in the email had a space between
http://freecodecamp.com/news/ and
learning-d3--essential-skills-for-the-javascript-programmer--mr-hassles-long-underp?
That is why the link wasn't working. Links shouldn't have spaces in them
obviously, so if that was the case, we need to trim leading whitespace from
titles.
--
Reply to this email directly or view it on GitHub
https://github.com/FreeCodeCamp/freecodecamp/issues/474#issuecomment-104953969
.

--
Schedule a Swim lesson, Podcast or Coaching consult here:
http://www.booknow.so/SteelCity

to clarify, it was a line break, but that may be due to a space followed by a long unbroken "word" falling to the next line.    Maybe a short link stays on one line and the hypertext works?

@adventurebear this is now fixed! Thanks for reporting it!


A new fix for #47

Dear maintainers,
I was struggling with some misbehavior in my application, without realizing this may very well be related with issues #47 #52 and #54
Similar to the use cases reported originally by @smeybi, my application also may remove ammo bodies during its lifecycle, as they represent assets that are spawned/despawned on the scene.
After some long debugging I have realized there existed a problem with the way ammo bodies were deleted. If we look at
https://github.com/c-frame/aframe-physics-system/blob/98cf0b39465c76006cc86d4a21e227cfcdc12f06/src/drivers/ammo-driver.js#L67-L76
At line 74 we see that when an ammo body is deleted, its supposed entry in the collisionKeys array is removed. However, this entry will be there only if the body ever participated in a collision in the role of body0
https://github.com/c-frame/aframe-physics-system/blob/98cf0b39465c76006cc86d4a21e227cfcdc12f06/src/drivers/ammo-driver.js#L106-L109
If this never happened at the time the body is removed, the resulting index -1 will de-facto make so that splice will delete an arbitrary entry in collisionKeys. If this pattern repeats often enough, it will de-facto disable event generation for any body on the scene, as only in the collisionKeys loop we do cleanup the collisions array, which is checked before we trigger the event
https://github.com/c-frame/aframe-physics-system/blob/98cf0b39465c76006cc86d4a21e227cfcdc12f06/src/drivers/ammo-driver.js#L110-L114
https://github.com/c-frame/aframe-physics-system/blob/98cf0b39465c76006cc86d4a21e227cfcdc12f06/src/drivers/ammo-driver.js#L126-L140
In my proposal I revert the previous fix, which came at the cost of a memory leak, and refactor the code so that we do not instantiate the data structures relevant for collisions on the fly, but at body creation. This ensures that a collisionKeys entry is there for every body and also makes the code more orderly IMO.
Please have a look if this also solves the issue reported originally.
All the best

Fantastic work.  Thank you so much.


Allow ConfigurationOptions to be passed to the ConnectionMultiplexer

Summary of the changes:

Adds ConfigurationOptions to RedisCacheOptions
Passes either ConfigurationOptions or Configuration to ConnectionMultiplexer.
Adds a check in the constructor that one of these is not null

This allows you to set options in the ConnectionMultiplexer that you cannot when using the connection string, such as RemoteCertificateValidationCallback

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

Have added the requested changes :)


parse_git_dirty error

Hi everyone,
Since yesterday I have this error message "  parse_git_dirty:4: command not found: git   " after removing git for a new installation.
Now it is totally impossible to update, upgrade my system. I am using Ubuntu 18.04.3 LTS.
Someone can at least explainme what does it means ?
Thank you for your support.

Git is part of the prerequisites. You need to reinstall it.
If you can't use your shell for now, rename your .zshrc file temporarily, re-install git, and then rename .zshrc back to its original name.

You can hack it to not get that error by redefining the function with an empty body, like so:
parse_git_dirty() {}

But yeah, git is a prerequisite and thus we don't check for its existence in pretty much anywhere. If you have OMZ autoupdate enabled (it is by default) you'll also get errors once in a while.


Prepare release 2.16.0

The first two commits are pre-requisite for the rest of the process. They (1) tidy up the github actions and prepare for switching to go 1.23 and (2) make the relprep script use X.YY instead of X.YY.ZZ versions for envtest, which seems more reliable (and possibly required now).
$ ./hack/relprep.sh 2.16.0
$ go get<EMAIL_ADDRESS>$ go mod tidy

Manually downgraded sigs.k8s.io/structured-merge-diff/v4 due to mis-matched struct in v4.4.2.
Checklist

[X] Commits are signed with Developer Certificate of Origin (DCO)
[X] Tested on OpenShift
[X] Tested on vanilla K8s

Fixes #246

Looks great! Lots of cloudeventsource stuff this time. It's a shame about golangci-lint, but glad you got to the bottom of it :smile:
/lgtm


Simplify use by direct download and execute

The installation instructions call for using git, and the update instructions say to repeat install, but with git that is really not repeat, it would be a git pull, which is not quite the same.
Suggest as alternative instructions to execute script directly using e.g.
wget -O - https://raw.githubusercontent.com/jordanhillis/pvekclean/master/pvekclean.sh | bash -s arg1 arg2

The installation instructions call for using git, and the update instructions say to repeat install, but with git that is really not repeat, it would be a git pull, which is not quite the same.
Suggest as alternative instructions to execute script directly using e.g.
wget -O - https://raw.githubusercontent.com/jordanhillis/pvekclean/master/pvekclean.sh | bash -s arg1 arg2

The update instruction listed on the readme are old and I will have to change that. The new way to update is to simply run pvekclean and it will automatically look for updates. If it finds a new update it gives you the option to update right from the command line with a simply "y". Let me know if you have any further questions!

I assume (I did not look at code) that only works when Can we install PVE Kernel Cleaner to your /usr/local/sbin for easier access [y/N] n installing, else git pull would bring in the updated version, and changing the version in the git folder would create an inconsistency?

I assume (I did not look at code) that only works when Can we install PVE Kernel Cleaner to your /usr/local/sbin for easier access [y/N] n installing, else git pull would bring in the updated version, and changing the version in the git folder would create an inconsistency?

The update can be applied even if it isn't installed to the /usr/local/sbin. It will update the file you executed so if that's pvekclean.sh inside a folder somewhere it will update that or if you ran /usr/local/sbin/pvekclean it will update that. It does this using curl and checks to ensure the correct #!/bin/bash is the first line before applying the update to the file to avoid scenarios where it failed to retrieve the requested file. I did this instead of git in instances where maybe the user doesn't have git installed for some reason. Curl seems to be more common place on systems.
Does this answer your question? I feel like maybe I am misunderstanding it 😅 so feel free to ask more questions if need be.

If you update files in a git managed folder, the contents of the folder is now out of sync with the upstream. If you change the install instructions to just use wget/curls to get the script, then set +x, then the script can update itself without impacting the git state. So splitting hairs here, but pulling using git should update by pulling from git, not external modification.

# Function to check for updates
check_for_update() {
	if [ "$check_for_updates" == "true" ] && [ "$force_purge" == "false" ]; then
		local remote_version=$(curl -s -m 10 https://raw.githubusercontent.com/jordanhillis/pvekclean/master/version.txt || echo "")
		# Unable to fetch remote version, so just skip the update check
		if [ -z "$remote_version" ]; then
			printf "${bold}[*]${reset} Failed to check for updates. Skipping update check.\n"
			return
		fi
		if [ "$remote_version" != "$version" ]; then
			printf "*** A new version $remote_version is available! ***\n"
			printf "${bold}[*]${reset} Do you want to update? [y/N] "
			read -n 1 -r
			printf "\n"
			if [[ $REPLY =~ ^[Yy]$ ]]; then
				local updated_script=$(curl -s -m 10 https://raw.githubusercontent.com/jordanhillis/pvekclean/master/pvekclean.sh)
				# Check if the updated script contains the shebang line
				if [[ "$updated_script" == "#!/bin/bash"* ]]; then
					echo "$updated_script" > "$0"  # Overwrite the current script
					printf "${bold}[*]${reset} Successfully updated to version $remote_version\n"
					exec "$0" "$@"
				else
					printf "${bold}[*]${reset} The updated script does not contain the expected shebang line.\n"
					printf "${bold}[*]${reset} Update aborted!\n"
				fi
			fi
		fi
	fi
}

This is the update function within the script that checks for updates on the version.txt. If it finds an update it asks the user if they want to install this update. If they select "y" it will grab the latest version of pvekclean.sh from the repo and overwrite whatever file they are using (could be any path or name) with the source code from this.

If you overwrite the file as part of an update, then using git to install is not appropriate.


Documentation / Readme Example Clarification

Driver version
NA
Redshift version
NA
Client Operating System
NA
Python version
NA
Table schema
NA
Problem description

Expected behaviour: Reference/Description to undefined variables.
Actual behaviour: Examples have reference to undefined variables
Error message/stack trace: "... is not defined"
Any other details that can be helpful:

The Readme has reference to functions that are not defined. The example I'm trying to work with:
with db_table.cursor() as cursor:
    cursor.write_dataframe(df, "book")
    cursor.execute("select * from book; ")
    result = cursor.fetchall()

I cannot find reference to db_table object. How was this created?
Python Driver trace logs

NameError: name 'db_table' is not defined
Reproduction code

See current readme

Hi @nfmcclure ,
In this case, db_table is the Connection object created using the method redshift_connector.connect(). Please see the readme section basic example to see how a connection can be established.
We will correct the naming of this variable in our docs to clarify that it is the connection object as the current naming is needlessly confusing. Thank you for taking the time to open and issue and help us improve our docs :).

We've updated our README to address this issue in v2.0.904. Please feel free to open a new issue if you have further comments or questions.


GDScript 2.0: Parent _init() function not called if child class doesn't define it

Godot version
v4.0.dev.calinou.de83ee57e
System information
Windows 10 x64
Issue description
Recent GDScript changes no longer automatically call parent functions on methods like _init(), _ready(), _process(delta), etc if a child class has a definition for them that does not manually call super.whatever(). I'm fully in support of this.
But if you have a parent class which has _init() defined and then you have a child class which does not have _init() defined, _init() will not be called. This is different than how all other such functions behave.
Steps to reproduce
Create some class which has an _init() defined. Then create a script which extends it and has no definition for _init.
Instantiate the child class and notice that _init() does not get called, even though there's nothing overriding it.
Minimal reproduction project
Init.zip
I have two classes, Parent and Child, which both have _init() and _ready() defined. As is if you run the project you'll get the Child class' output for both functions; it overrides them after all.
Comment out the Child's definition of _ready() and run it and you'll get the Parent's version of it. This also makes sense -- that is now the only definition of _ready() in the hierarchy.
But comment out the Child's definition of _init() and the Parent's definition will not get called. Despite being the only definition available. This is surprising and inconsistent with every other similar function's implementation.

Should be resolved by this PR https://github.com/godotengine/godot/pull/51456

The PR referenced has been merged so would recommend this issue can now be closed

Closed by https://github.com/godotengine/godot/pull/51456

I guess someone forgot to click the close button. Closing now as fixed.


Documentation test

All documentation examples are tested

coverage: 100.0%. remained the same
when pulling ba8449e591d31fd5d9b6b66ef65460d996177c95 on documentation-test
into 1f270e9c022b53b7a43db3647f96bca3404a95f6 on main.


PublishDiagnosticsClientCapabilities and tagSupport

I'm trying to update my server with a replacement that I am writing for Microsoft.VisualStudio.LanguageServer.Protocol. The replacement brings forward the types from the 3.6-ish/2+ year old version that VS 2019 uses to the 3.16 spec. I need to move forward to something that I can use with VSCode, GNU Emacs and other clients that support semantic highlighting. It works great, but I'm now looking at every detail to make sure ever interface/class/struct/enum is correct even for things that I don't use.
One problem is the "tagSupport" field of the PublishDiagnosticsClientCapabilities interface.
export interface PublishDiagnosticsClientCapabilities {
    ...
    /**
     * Client supports the tag property to provide meta data about a diagnostic.
     * Clients supporting tags have to handle unknown tags gracefully.
     *
     * @since 3.15.0
     */
     tagSupport?: {
         /**
          * The tags supported by the client.
          */
         valueSet: DiagnosticTag[];
     };
}

The JSON I received from VS2019 for initialization included the following:
  "publishDiagnostics": {
    "tagSupport": true
  }

This causes an error because "true" cannot be mapped to a struct containing valueSet/DiagnosticTags array. Am I reading the spec this right? If so, I think I need to flag a bug in VS2019.
(Also, this may not be the correct place to raise this, but this might be a problem with the spec, in that it's missing "| boolean" for "tagSupport".)

A boolean is not valid for tagSupport, so that's a bug in VS2019 (or whatever extension might be providing that).

Thanks. I'll raise the issue with the VS2019 team.


Python - azure.functions.WsgiMiddleware does not support multiple Set-Cookie response headers

Bug
When a HttpResponse has multiple headers with the same name, only one header is returned.
Django uses multiple response cookies  (e.g. 'csrf' and 'messages').
Multiple Set-Cookie headers can be returned. Set-Cookie is the name (the key) of the Http Response Header.
Context
A Django app running in an Azure Function
package
Name: azure-functions
Version: 1.8.0
Summary: Azure Functions for Python
Home-page: UNKNOWN
Author: Microsoft Corporation
Author-email<EMAIL_ADDRESS>
Version
Azure function runtime version = ~4
Reproduction

Create a http response with two Set-Cookie headers
This header has been captured from the app running without the Azure wsgi middleware.

HTTP/1.1 200 OK
Date: Sun, 16 Jan 2022 09:00:59 GMT
Server: WSGIServer/0.2 CPython/3.9.9
Content-Type: text/html; charset=utf-8
X-Frame-Options: DENY
Vary: Cookie
Content-Length: 5206
X-Content-Type-Options: nosniff
Referrer-Policy: same-origin
Set-Cookie:  messages=""; expires=Thu, 01 Jan 1970 00:00:00 GMT; HttpOnly; Max-Age=0; Path=/; SameSite=Lax
Set-Cookie:  csrftoken=L6coOZOclDhAg2X7geBKbhvJSHPxz9AbgOkoVqNAIsgVe8oxTEPTSPbc2VPSyjwq; expires=Sun, 15 Jan 2023 09:00:59 GMT; Max-Age=31449600; Path=/; SameSite=Lax

Run without azure.functions.WsgiMiddleware
Two  Set-Cookies headers are returned (as depicted above)

Run with azure.functions.WsgiMiddleware.handle

import azure.functions as func
def main(req: func.HttpRequest, context: func.Context) -> func.HttpResponse:
    http_response = func.WsgiMiddleware(application).handle(req, context)
    return http_response

Only one header with the name "Set-Cookie" is returned.
Local and remote
This behaviour has been reproduced both locally (while debugging) as on an Azure Function container (icarus-int)
Root cause
Python package 'azure-functions'
azure\functions_http.py
class HttpResponseHeaders(BaseHeaders, collections.abc.MutableMapping):

    def __setitem__(self, key: str, value: str):
        self.__http_headers__[key.lower()] = value

    def __delitem__(self, key: str):
        del self.__http_headers__[key.lower()]

The headers are stored as a dictionary. All keys in a dictionary are unique.
References
https://www.rfc-editor.org/rfc/rfc6265#page-6
Section 3
"Origin servers SHOULD NOT fold multiple Set-Cookie header fields into
a single header field.  The usual mechanism for folding HTTP headers
fields (i.e., as defined in [RFC2616]) might change the semantics of
the Set-Cookie header field because the %x2C (",") character is used
by Set-Cookie in a way that conflicts with such folding."
https://www.rfc-editor.org/rfc/rfc6265#section-4.1
"Servers SHOULD NOT include more than one Set-Cookie header field in
the same response with the same cookie-name.  (See Section 5.2 for
how user agents handle this case.)"
This means that multiple Set-Cookie headers with different cookie-names are allowed.

Having the same issue. Is there any timeline available on if/when this will be available? Or would it be better to rewrite my functions to e.g. Node where setting multiple cookies seems to be available?

Leaving this here for anyone like myself who is searching for how to do this, finds this as the only relevant google search result, and can't figure out how to do it. Here's example code that is working.
response = func.HttpResponse(json.dumps({'code': 'success', 'message': "User logged in"}), status_code=200)
# Headers have to be added by this method as the default is a dict, which doesn't work because dict keys are unique
response.headers.add("Set-Cookie", f"token={token}")
response.headers.add("Set-Cookie", f"id={uuid}")

Leaving this here for anyone like myself who is searching for how to do this, finds this as the only relevant google search result, and can't figure out how to do it. Here's example code that is working.
response = func.HttpResponse(json.dumps({'code': 'success', 'message': "User logged in"}), status_code=200)
# Headers have to be added by this method as the default is a dict, which doesn't work because dict keys are unique
response.headers.add("Set-Cookie", f"token={token}")
response.headers.add("Set-Cookie", f"id={uuid}")

It's people like you that make this world a better place -- tried everything to get this to work, thank you!

Leaving this here for anyone like myself who is searching for how to do this, finds this as the only relevant google search result, and can't figure out how to do it. Here's example code that is working.
response = func.HttpResponse(json.dumps({'code': 'success', 'message': "User logged in"}), status_code=200)
# Headers have to be added by this method as the default is a dict, which doesn't work because dict keys are unique
response.headers.add("Set-Cookie", f"token={token}")
response.headers.add("Set-Cookie", f"id={uuid}")

Thanks for the code, but this ended up not working.  You'll see toh Set-Cookies in the header response, but if you'll notice in the cookie's tab, only one cooke is set, and since it's a dictionary, the second Set-Cookie overwrites the values of the first Set-Cookie.

Odd, that works perfectly fine for me. Behind the scenes it's not a dictionary actually, it's a list of tuples as seen in line 1138 of the Headers object file: `self._list.append((_key, _value))`

Here's what I'm seeing:

The client is a stock create react app running locally on https://<IP_ADDRESS>:3000
I'm using stock azure functions v4 with no middle where or extra imports -- maybe I need to add something?

This is an issue with chrome, not your code. https://stackoverflow.com/questions/63204093/how-to-get-set-multiple-set-cookie-headers-using-fetch-api
Officially, there is no requirement to support multiple Set-Cookie headers in a response, so chrome's auto-parsing of your headers is deleting the second one (but the standard arguably says it could keep either one). If you try this with Postman, or a different request client, you'll find you're getting both cookies set. Remember that how the headers are handled is entirely on the client, and you have full control over that in your client code.


Write script to convert .nat EUMETSAT files to intermediate file format

Detailed Description
Following on from #13
Features of this script

[ ] Takes command-line arguments for directory of .nat files; and target directory for intermediate files
[ ] Optionally reprojects (to be tracked in a separate issue)
[ ] Optionally only saves a geographical subset of the data (perhaps with some handy human-readable shortcuts like "UK")
[ ] The default behaviour should be that, when the script starts, it check through all the .nat files (recursively), and checks through all the already-converted files, and only converts data which is present in the .nat files but absent in the intermediate files.  Provide an option to 'clobber' existing files.
[ ] Use all the CPU cores.

Related:

The ipython notebook I wrote in 2019 to convert and reproject .nat files to NetCDF
Comparison I made of image file formats downloaded from EUMETSAT

Yeah, I agree, keeping as much of the satellite specific stuff in Satip makes sense. I like generally keeping the packages as separate as possible.


Feat/chain to receive

Previously, When mocking multiple functions on the same module, the
syntax was:
allow(Mockable) |> to_receive(do_something: fn -> :error end)
Mockable |> to_receive(do_something_else: fn -> :success end)

allow(Mockable) now returns a struct in the format
%Pavlov.Mocks{module: Mockable} this is now the expected argument to
to_receive allowing the following:
allow(Mockable)
  |> to_receive(do_something: fn -> :error end)
  |> to_receive(do_something_else: fn -> :success end)

The first commit breaks the old way of doing this. The second commit fixes it again. If you want to support the old way let me know and I can squash the commits.

Thanks for this! I don't see much reason to continue supporting the old way, since to_receive is the only composition that interacts with allow as of now.

@inf0rmer I've removed that commit.

Thanks!


ndx-pose 0.2.0 release

@talmo I would like to make a 0.2.0 release with the latest changes and add ndx-pose to the NDX Catalog this month.
You noted a couple TODO and nice to have items in https://github.com/rly/ndx-pose/pull/24.
Do you want to make any other changes or do any testing before the 0.2.0 release? I think the nice to have items can wait for a future release.

I will also review #5 and #13 before release.

Hey @rly,
Nope, nothing on the ndx-pose end, but we'll be working to update sleap-io to support the training data very soon! (As well as a conda-forge release)


Include base64 library in project

Would be easier for user (me;) if the base64 library was included.

Once I get this running as a gradle dependency it should be able to have that depenency during your gradle sync, which should make it transparent.

I have simplified this so you simply include base64coder in your dependencies along with the library.

The base64coder dependency shouldn't be necessary. Android ships with base64 utility methods as of API level 8: http://developer.android.com/reference/android/util/Base64.html


Download toolchains from behind a proxy

I'm currently behind a proxy, and can't download any toolchains. How do you set up proxy settings with multirust?

@Aaronepower do you have http_proxy and https_proxy set up?

I'm on Windows forgot to say. But I do also have those set up as env variables.
On Thu, Nov 12, 2015 at 12:34 PM, Michael Pankov<EMAIL_ADDRESS>wrote:

@Aaronepower do you have http_proxy and https_proxy set up?
Reply to this email directly or view it on GitHub:
https://github.com/Diggsey/multirust-rs/issues/35#issuecomment-156092513

Hi,
Any news on this issue, I can't use multirust because of a enterprise proxy. Is there any workaround ?
Thanks !

Same issue here. I am on Ubuntu 15.10, 64-bit.
I have http_proxy, https_proxy and ftp_proxy set up.
multirust - the script, picks them up and the command multirust update works.
multirust-rs - the Rust application, doesn't work with the proxy.
info: updating existing install for 'beta'
downloading file from: 'https://static.rust-lang.org/dist/channel-rust-beta.sha256'
error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-beta.sha256' to '/home/uidr1070/.multirust/tmp/tfr6k8vxppx6ngcd_file' (Network: connection refused)
info: updating existing install for 'nightly'
downloading file from: 'https://static.rust-lang.org/dist/channel-rust-nightly.sha256'
error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-nightly.sha256' to '/home/uidr1070/.multirust/tmp/x07lpef1zc6s24vr_file' (Network: connection refused)
info: updating existing install for 'stable'
downloading file from: 'https://static.rust-lang.org/dist/channel-rust-stable.sha256'
error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-stable.sha256' to '/home/uidr1070/.multirust/tmp/pr1qo3_cbbj0tk5g_file' (Network: connection refused)

   beta update FAILED
nightly update FAILED
 stable update FAILED

Tried today rustup and the issue is still present.
I had issues installing it(multirust-rs was installing over multirust but it doesn't any more - another issue):
Continue? (Y/n) Y

error: toolchain 'nightly' is not installed
rustup: command failed: /tmp/tmp.pHwfFAkit0/rustup-setup

To solve the issue I had to run multirust uninstall command(I tried removing the toolchains, then the metadata, finally after removing multirust it worked).
After this, I tried to install rustup:
Continue? (Y/n)
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-stable.toml.sha256' to '/home/uidr1070/.multirust/tmp/zo5drrtemgah7y1s_file' (Network: connection refused)
rustup: command failed: /tmp/tmp.sr3f0QCId8/rustup-setup

Waiting on this too, but according to #344 this bug should be fixed shortly.

This should now be done! With the switch to curl in https://github.com/rust-lang-nursery/rustup.rs/pull/434 rustup should naturally pick up the relevant env vars now.

I'll test when I go back to work and report the results.

Just updated to latest rustup, proxies confirmed working!

I can confirm that the behavior seems to be the same as with cargo.

Works through a proxy
Doesn't work through WPAD

All tools have problems running in cmd because of WPAD, so I guess this is the expected behavior :)


image filter test: use kubernetes/pause as a "since"

Use kubernetes/pause, which is not expected to be updated regularly, as a reference image for the "since" filter, instead of alpine, which is updated regularly, and which therefore can be newer than busybox.  (I was tempted to use references with digests to make a permanent fix, but that would also implicitly hard code an architecture.)

@rh-atomic-bot r+


Capacity - add storage usage to agents rpc and openapi

feat(plugin): format byte size into appropriate unit

Used the human read crate to format it.
Also convert block size in blocks to a size.
The doc mention that the size is in 512 blocks, is this really always true? Even
if the device is 4k?

Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

refactor(plugin): add new row trait to simplify single row resources

Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

feat(capacity/thin/plugin): add usage to rest plugin

Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

feat(capacity/thin/openapi): add volume and replica usage the openapi

Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

feat(capacity/thin/rpc): add volume and replica usage to the agents rpc

Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

bors merge

bors merge

bors cancel

bors merge


[HDFS-462] Add readiness check to journal nodes

The deployment plan now waits for the journal nodes to succeed their readiness check before proceeding to deploying the name nodes.

retest this please

@gabrielhartmann Addressed comments

@gabrielhartmann rebased on master


Help and warning messages update

Update warning text in decode mode about stdout.
Update help messages in encode and decode mode about stdin/stdout option for file argument.

Make sure use of OUT/OUTFILE is consistent.

[ ] calc

[ ] check spacing before parentheses

[ ] check

[ ] check spacing before parentheses

[ ] decode

[ ] check spacing before parentheses
[ ] check usage of OUT/OUTFILE
[ ] add info on stdout as OUT

[ ] encode

[ ] check spacing before parentheses
[ ] check usage of OUT/OUTFILE
[ ] add info on stdin as INFILE

[ ] repair

[ ] check spacing before parentheses

[ ] rescue

[ ] check spacing before parentheses

[ ] show

[ ] check spacing before parentheses

[ ] sort

[ ] check spacing before parentheses


add a proposal template

@mwengren and @MathewBiddle  this is the first step for our Contributor Guidance. I'll add the rest in another PR to keep the review context short.

@ocefpaf This looks like a good start!
I'm a bit confused about how you're thinking this will be used by potential applicants, however.  For GSoC applications, the students' applications should be private - so I'm not sure a PR or public issue is the best approach - it can open the door for plagiarisms of someone's idea.
Should we just post this as a plain old markdown file/template in the repo root (CONTRIBUTOR_GUIDANCE.md for example) to give them an idea for what information we're expecting for a student application via GSoC portal (in addition to whatever Google directs them to include)?
Here's the text from the Org page in the GSoC dashboard for reference for what I'm referring to that Google is asking for:

Contributor Guidance
Provide your potential contributors with a page containing tips on how to write a successful proposal for your organization. Let them know what you want included, how you want it structured, and how to best get in touch. Examples.

Currently we have a link to the repo root to answer that (which doesn't include the right info of course), so improving on that would be great.
Let me know what you think, it would be great to get this addressed ASAP - so even just renaming this file perhaps if you agree and merging this PR I'd be in favor of (and then we should update our GSoC Org profile to point here for the Contributor Guidance link), but I do want to understand

For GSoC applications, the students' applications should be private - so I'm not sure a PR or public issue is the best approach - it can open the door for plagiarisms of someone's idea.

Indeed and we had that before :-/

Let me know what you think, it would be great to get this addressed ASAP - so even just renaming this file to not make it an issue template if you agree and merging this PR would be a step in the right direction.

Let me do that and we can figure out a long term solution later when we have more time.

@ocefpaf I took your templates/proposal.md file here and adapted slightly and renamed to just go in the project root instead.  Any objections if I just push that directly now to main and you could adapt this PR accordingly if needed?

Please do!

Let's close it to avoid confusion. We can work o refining this for 2025. What do you think @mwengren ?

Ok.  I'll close it.  We should consider updating the https://github.com/ioos/gsoc/blob/main/contributor-guidance.md separately though, I think that could use a little more attention.  I'll try to take a look when I can but if anyone has time and suggestions for additions, please have at it.


Console spam

As of projectborders-5.0.0-0.1.1.jar, console is spammed with generation progress, about every 2 ticks.
Please only shows progress every 5 or 10 seconds instead.

I have little control over the Generators log. I can either enable it or disable it but I can't change any aspects of it. I do plan on adding a config option to enable/disable logging


should be able to use the output of ros config export for ros install

i just did it, and i get a kernel panic on boot

What's the status on this ? i'm running v1.0.4 and ros c export still generates a non-valid file starting with EXTRA_CMDLINE: /init instead of #cloud-config.

its down for the v1.2 milestone - it might be something for a new contributor to learn a little about the RancherOS codebase :)

I see what you're doing there 😆, I'll see what I can do. Any chance you'd be available on slack to help me setting up a dev environment if needed ?

yes to a chance - I'm in Brisbane, Australia, so a mildly painful TZ - but you can also ping @joshwget :D


Virtual Node Not Created

After installing Liqo, no virtual node is created on the Kubernetes cluster
I'm looking for a solution to deploy geo-distributed read-only replicas for my application in the different data centers of my cloud provider (DigitalOcean) across the globe, closer to my client's servers, so I decided to give Liqo a try. However, the results I'm getting are quite different from what I see in the presentation video (https://www.youtube.com/watch?v=tHCKGwnmuAA), from the naming of the pods, to the virtual node not being created.
Steps to Reproduce
I've tried following the documentation (https://doc.liqo.io/user/gettingstarted/install/). However, small modifications were required, since at the first run, the default installation could not get the POD_CIDR and SERVICE_CIDR, so I've done this instead:

Get the Cluster Subnet and Service Subnet from the DigitalOcean Kubernetes cluster:
doctl kubernetes cluster get kubernetes-cluster-1-name

Export variables to make them available at Liqo installation time:
export POD_CIDR=<IP_ADDRESS>/16
export SERVICE_CIDR=<IP_ADDRESS>/16

Run the installation command again:
curl -sL https://get.liqo.io | bash

Wait until all pods are marked as "Running":
kubectl get po -n liqo

Check the cluster nodes to see if the virtual node is created, like in the video tutorial:
kubectl get no

Expected behavior
I would have expected to see a new node (the virtual node created by Liqo), but only my 2 initial Kubernetes nodes are present, without any new one.
Screenshots

Questions:

What am I doing wrong? Is this virtual node still created with the latest version?
How can I access the graphic dashboard? Maybe there are things I don't yet understand that will make more sense after checking the dashboard.
Is Liqo the right solution for such a geo-distribution? Will I be able to specify which pods should be offloaded and where, in case of multiple clusters? (for example, I would need the application and a database replica to be always located in the same cluster, to prevent latency)

Thanks!

Bogdan,

unfortunately, the current peering process is really prone by errors. This is the reason we're creating an helm chart to simplify the installation, which should be ready (and documented) in a few days. As a short answer to your question, yes, you should see one more node in your cluster.
The graphic dashboard was available in version 0.1 but, due to the many changes we did in 0.2, it is of little use nowadays.
Yes, this is possible, but everything has to be done manually, unfortunately.

Final remark: Liqo is not yet for production; many problems can be solved, but require somebody in our team to help you on that matter. For this reason, I would suggest to join our Slack workspace and start "begging" our engineers in the help channel.

Thanks Fulvio!
I've joined the Slack workspace and I'll keep an eye for the release of the helm chart.


Regenerate ServiceManagement client

This PR was generated using Autosynth. :rainbow:
Here's the log from Synthtool:
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/synth.py.
synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir16 scripts/generate_client.sh ServiceManagement
synthtool > Wrote metadata to clients/service_management/synth.metadata.

Closing so this will regenerate with the otp_app fix.


tags: 429 and 429-gateway

Replicates the 429 and 429-gateway tag from Yuu
references: 429 and 429-gateway

Great points, tbh most of the tag was copied directly from Yuu. If everything you said is correct I don't think these warrant a tag, I'll close the PR :+1:


The game could not be started (80020148)

Title says the error
In my PSP 09g it is giving that error when starting up Infinity 2

Firmware version?

6.61
But i already fixed it, but when i boot up, it doesn't open the CFW, i still have to open PROUPDATE to get it
I will try to downdrade back then update, let's see if that works

@PedroxTheBest99, is the issue is still actual?


Give MNIST examples more visual output

This change is

Your screenshot looks really cool!
The travis-ci came back with some errors (looks like minor issues), could you fix those please?
Thanks so much for this contribution :)

Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

demos/mnist/index.html, line 14 at r2 (raw file):

MNIST demo


abnormal cerebellum interpositus nucleus morphology - def typo

abnormal cerebellum interpositus nucleus morphology MP:0009984
DEF: any structural anomaly of the nucleus composed of the globose and emoliform nuclei of the cerebellum; in some mammalian species the globose nucleus is not distinguishable
emoliform should be changed to "emboliform".

Typo has been fixed.


Update 'simplify' to handle arithmetic operators on ranges

Codecov Report
Attention: 37 lines in your changes are missing coverage. Please review.

Comparison is base (8486108) 81.07% compared to head (fdc553e) 80.72%.

Files
Patch %
Lines

src/Escalier.Data/Library.fs
32.25%
21 Missing :warning:

src/Escalier.TypeChecker/Prune.fs
66.66%
16 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #100      +/-   ##
==========================================
- Coverage   81.07%   80.72%   -0.36%
==========================================
  Files          17       17
  Lines        5262     5327      +65
  Branches      646      654       +8
==========================================
+ Hits         4266     4300      +34
- Misses        996     1027      +31

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Scripting Maskrcnn with wrapper code

I can script Maskrcnn parts (as is) using this:
import torch
import torchvision

model = torchvision.models.detection.maskrcnn_resnet50_fpn(pretrained=True).eval()
backbone_script = torch.jit.script(model.backbone)
torch.jit.save(backbone_script, './Maskrcnn_backbone.pt')

and load it in cpp using this:
#include<torch/torch.h>
#include<iostream>
#include<torch/script.h>

int main()
{
	auto backend = std::make_unique<torch::jit::script::Module>torch::jit::load("./Maskrcnn_backbone.pt"));
	return 0;
}

And,
When I add a wrapper around the parts like this:
import torch
import torchvision

class BackboneWrapper(torch.nn.Module):
    def __init__(self, model):
        super(BackboneWrapper, self).__init__()
        self.transform = model.transform
        self.backbone = model.backbone

    def forward(self, images, targets=None):
        # type: (List[Tensor], Optional[List[Dict[str, Tensor]]]) -> Dict[str, Dict[str, Tensor]]
        images, _ = self.transform(images, targets)
        features = self.backbone(images.tensors)
        return {'features': features}

model = torchvision.models.detection.maskrcnn_resnet50_fpn(pretrained=True).eval()
backbone_script = torch.jit.script(BackboneWrapper(model))
torch.jit.save(backbone_script, './Maskrcnn_backbone_wrapped.pt')

It does save the model without errors in python, but when I try to load it in cpp:
#include<torch/torch.h>
#include<iostream>
#include<torch/script.h>

int main()
{
	auto backend = std::make_unique<torch::jit::script::Module>torch::jit::load("./Maskrcnn_backbone_wrapped.pt"));
	return 0;
}

I get this error:
Unknown builtin op: torchvision::_new_empty_tensor_op.
Could not find any similar ops to torchvision::_new_empty_tensor_op. This op may not exist or may not be currently supported in TorchScript.
: torchvision-0.4.2-py3.6-linux-x86_64.egg/torchvision/ops/new_empty_tensor.py", line 16
        output (Tensor)
    """
    return torch.ops.torchvision._new_empty_tensor_op(x, shape)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <--- HERE
Serialized   File "code/__torch__/torchvision/ops/new_empty_tensor.py", line 4

It looks like Torchscript is somehow messing up the save when I use a wrapper (the directory structure also looks different for the serialized files) and therefore cannot find the operators while loading it on cpp.
I think it is important to make parts work with custom wrappers because different software would have different interfaces and everyone would eventually want to make these parts work with their code internally.
Thank you.

@cted18 can you also post the gcc / compilation arguments you used to compile and run the model on C++?

Sure.
Pytorch, torchvision and libtorch install:
conda install pytorch torchvision cudatoolkit=10.1 -c pytorch-nightly
https://download.pytorch.org/libtorch/nightly/cu101/libtorch-shared-with-deps-latest.zip

Following this https://pytorch.org/tutorials/advanced/cpp_export.html
sample.cpp:
#include<torch/torch.h>
#include<iostream>
#include<torch/script.h>

int main()
{
	auto backend = torch::jit::load("./Maskrcnn_backbone_wrapped.pt");
	return 0;
}

CMakeLists.txt:
cmake_minimum_required(VERSION 3.0 FATAL_ERROR)

project(sample)

add_executable(sample sample.cpp)

find_package(Torch REQUIRED)

target_link_libraries(sample "${TORCH_LIBRARIES}")
set_property(TARGET sample PROPERTY CXX_STANDARD 11)

Build commands:
cmake -D CMAKE_PREFIX_PATH=/path/to/libtorch .
make -j8

Hi,
So looks like you didn't follow the instructions in https://github.com/pytorch/vision/pull/1407#issuecomment-563048240
You need to add
 static auto registry =
     torch::RegisterOperators()
         .op("torchvision::nms", &nms)
         .op("torchvision::roi_align(Tensor input, Tensor rois, float spatial_scale, int pooled_height, int pooled_width, int sampling_ratio) -> Tensor",
             &roi_align)
         .op("torchvision::roi_pool", &roi_pool)
         .op("torchvision::_new_empty_tensor_op", &new_empty_tensor)
         .op("torchvision::ps_roi_align", &ps_roi_align)
         .op("torchvision::ps_roi_pool", &ps_roi_pool)
         .op("torchvision::deform_conv2d", &deform_conv2d)
         .op("torchvision::_cuda_version", &_cuda_version);

in your sample.cpp file, and link it properly in your CMakeLists.

Oh yes.
I failed to incorporate some other changes.
Thanks for looking into this.

@cted18 can you share the final CMakeLists.txt content that worked for you?


Feat: Add animation rough notation.js in start us button

Describe the feature
Add animation rough notation.js in start us button
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

solved #375


Load data from URL query

This one implements part of the URL query scheme we decided on yesterday.
Builds on #40
Here's an example URL
http://<IP_ADDRESS>:3000/?stan=https://gist.githubusercontent.com/magland/da3d4143276827609ec9317bb3db8b04/raw/cf48846a36de0559f96a9e4bcb5a5dcbe46383be/main.stan&data=https://gist.githubusercontent.com/magland/da3d4143276827609ec9317bb3db8b04/raw/cf48846a36de0559f96a9e4bcb5a5dcbe46383be/data.json&num_chains=6&num_warmup=1000&num_samples=1000&init_radius=2&seed=6&title=test_title
It specifies stan, data, num_chains, num_warmups, num_samples, init_radius, seed, and title
All the allowed query parameters are: stan, data, sampling_opts, num_chains, num_warmup, num_samples, init_radius, seed, title
You can't specify both sampling_opts and the inline opts at the same time.
After the initial load, if any of the content of the project changes, the query string on the URL disappears (as we had decided). But if you undo the changes within the same session, the query reappears. I find that convenient.
If the project has been edited (and the query string disappears) the changes are saved to browser storage.
I have not yet implemented loading entire project from single gist URI. I think that should be a separate PR along with saving to gist.

Replaced by #84


Check dependent destroys on object graph

When we purge a circle in STG or PROD, we need to guarantee all dependent data in the graph is purged.

Circle

Helpers

Comments

Workgroups

Documents
Tasks

Comments

Supplies

Comments

Projects

Tasks
Supplies

Documents

@dottorer thanks for the dependency listing above.
Re. deleting circle helpers:

the helper's circle roles should be destroyed for sure, this is safe as well.
a helper could be in multiple circles. It could be safely destroyed if he only in one circle. Checking this is a little extra work, and needs to be written & tested with care, since an error here can cause big (!) trouble. Alternatively we could always leave the users in the DB. In that case the user could still log in, but would get a 404/not found error because the circle is gone. The users could also always be deleted "by hand" in the admin area.

@dottorer I added dependent destroys for everything I could find. This also means everything down the relation graph will be deleted, i.e. if you delete a working group all tasks, supplies, projects in it should be deleted.
I also extended the admin area to have a very basic list of all relevant resources. You could now have some fun in the staging admin area :-)
As of now, no users are deleted, only all their circle-specific roles.

@phillipoertel we need to ensure that we do not delete users in a circle if they are also in another circle. It seems that only users with their primary circle being destroyed should be destroyed.

@dottorer would you really delete a user if his primary circle is deleted, but he is still in another one?

I guess the best scenario for multi circle users is to delete the circle but not the user. We then would need to make any of his other circles the primary. If only one circle exists, we can delete the user since as an orphan it make little sense.
Technically this could be too much work. I believe that orphaned users would at login be asked to join another existing circle. I could also hand purge orphans from time to time.
For now let's leave orphan users for me to hand purge....

Using now for DEMO purge...works.


Adding Ontology Identifiers to units of measurement

@Peyman-N can I merge or should this be merged after your other PR is merged #461 ?


drivers: uart_stm32: Add support for tx/rx swap

Add a new boolean devicetree property tx-rx-swap to the
st,stm32-usart binding, used to control TX/RX swap during
device initialization.
Signed-off-by: Alexander Mihajlovic<EMAIL_ADDRESS>

@abxy Thanks for adding this feature! I noticed that the tx-rx-swap is applied in uart_stm32_configure() but not also in uart_stm32_init(). Is there any reason for this? In my application the tx-rx pins that need to be swapped are the pins of the chosen UART for the zephyr kernel, so this results in lost logs prior to the reinitialization of the peripheral. I would like to add this to the initialization function.

@abxy Thanks for adding this feature! I noticed that the tx-rx-swap is applied in uart_stm32_configure() but not also in uart_stm32_init(). Is there any reason for this?
No reason. This was a mistake on my part. I think it should be moved to the initialization function since there is no way to change swap setting via the API.

It may be supported in the future, so I'll leave it in the configuration as well.


Attempt to fix flaky TestGetRoundTripper* tests

Which problem is this PR solving?

Resolves #4732

Description of the changes

Introduces an atomic boolean outside of the HTTP test handler and only set to true if the expected request is received.
This should prevent cases where unrelated processes are hitting the same test URL.

How was this change tested?

Ran make test to pass.
Ran go test -tags=memory_storage_integration -count 10 ./... and confirmed metricsstore tests are passing.
Note that a number of unrelated tests were failing with the -count 10 flag set, not as a result of the changes from this PR, namely:

--- FAIL: TestFactory (0.00s)
    --- FAIL: TestFactory/#00 (0.00s)
panic: Reuse of exported var name: test_1694287567920905000_counter_x
 [recovered]
	panic: Reuse of exported var name: test_1694287567920905000_counter_x

and
--- FAIL: TestPublishOpts (0.00s)
    builder_test.go:308:
        	Error Trace:	/Users/albertteoh/go/src/github.com/albertteoh/jaeger/cmd/agent/app/builder_test.go:308
        	Error:      	Received unexpected error:
        	            	cannot create processors: cannot create Thrift Processor: cannot create UDP Server: cannot create UDPServerTransport: listen udp :5775: bind: address already in use
        	Test:       	TestPublishOpts

Checklist

[x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
[x] I have signed all commits
[x] I have added unit tests for the new functionality
[x] I have run lint and test steps successfully

for jaeger: make lint test
for jaeger-ui: yarn lint and yarn test

Using boolean in the assert is not the best output when the assert fails. Using the actual string produces much more intuitive output in case of test failure.

Good suggestion, addressed in: 31bdc02


Cannot create new incidents

Describe the bug
Creating a new incident results in the error Incident not updated. Reason: list index out of range. I have created a fresh deployment (using dispatch-docker), using commit 846535a. Loaded sample data, registered a user, and used the documentation to bump them to admin role (docker exec, dispatch user update, etc).
web_1        | 2021-06-16T17:03:15.937978275Z INFO:     <IP_ADDRESS>:47812 - "POST /api/v1/default/incidents HTTP/1.0" 400 Bad Request

To Reproduce
Steps to reproduce the behavior:

Go to 'Incidents tab
Click on New
Fill out various incident details
Click save
See error

Expected behavior
Creation of an incident
Desktop (please complete the following information):

macOS, Chrome v91

Looking at debug logs, directly prior to the 400 there are calls out to PagerDuty. I have properly set the service ID, and all calls return 200. Logs seem to indicate incident was created. Unknown reporter seems to refer to auto-created individual (myself).
web_1        | 2021-06-16T17:14:04.849786288Z INFO:Dispatch Core App: Incident created:/usr/local/lib/python3.8/site-packages/dispatch/event/service.py:log:154
web_1        | 2021-06-16T17:14:05.115120773Z INFO:Dispatch Core App: Unknown added to incident with Reporter role:/usr/local/lib/python3.8/site-packages/dispatch/event/service.py:log:154

web_1        | 2021-06-16T17:14:05.361939820Z DEBUG:https://api.pagerduty.com:443 "GET /oncalls?limit=100&schedule_ids%5B%5D=*AAA*&escalation_policy_ids%5B%5D=*BBB*&offset=0 HTTP/1.1" 200 80:/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py:_make_request:452
web_1        | 2021-06-16T17:14:05.362382677Z DEBUG:Request completed: #method=GET|#url=https://api.pagerduty.com/oncalls?limit=100&schedule_ids%5B%5D=*AAA*&escalation_policy_ids%5B%5D=*BBB*&offset=0|#status=200|#x_request_id=*XXX*|#date=Wed, 16 Jun 2021 17:14:05 GMT|#wall_time_s=0.052378:/usr/local/lib/python3.8/site-packages/pdpyras.py:postprocess:1273
web_1        | 2021-06-16T17:14:05.363999143Z INFO:     <IP_ADDRESS>:40194 - "POST /api/v1/default/incidents HTTP/1.0" 400 Bad Request

The schedule/escalation policy IDs are correct. Is there any constraint requiring the commander/reporter of an incident to be a member of the PagerDuty policy, or similar? I do notice, when viewing the incident page that an incident is created, but commander/reporter fields are blank (and I cannot tell if any other automation has triggered, i.e. zoom/gdocs).

What authentication method are you using? We typically get reporter from the currently logged-in user.

Oh, I see you're using the default docker image and example data, let me take a look at the example data settings to see if something needs to be changed.

I forgot to mention, I was originally using the PKCE auth flow and encountered this same error there. I actually wiped the environment and loaded the test data to see if it would still reproduce with just the basic auth flow.
In the new env (with basic auth) I thought perhaps because my "Individual" had the name "Unknown" it wasn't populating some schema, but after updating the Name to "Eric" I now see a different error upon incident creation: Incident not updated. Reason: [object Object]
web_1        | 2021-06-16T18:45:01.176735486Z INFO:     <IP_ADDRESS>:41630 - "POST /api/v1/default/incidents HTTP/1.0" 422 Unprocessable Entity

This happens if I have the commander/reporter set both to myself, or both to the default dispatch user.

Can you show me the actual server response for the error? In chrome it would be under the network tab, then click on the request and then click on the response or preview tab. Typically when we get a 422 we should get some kind of error message associated telling us why our request was bad.

It would seem something strange is going on with Individuals. I've edited the name to "Eric" but it reverts to "Unknown" after some period of time/action. With "Unknown" I receive HTTP 400 {"detail":"list index out of range"} and the incident is created, but in some weird state. Now I actually cannot reproduce the [object Object] error, as whenever I rename my Individual to "Eric" and create an incident, the name is reverted to "Unknown" (and I receive the list index error).

Okay, I think I understand what's going on with the renaming. Can you make sure that the dispatch-contact plugin is enabled for this project?
When creating incidents do you have any issues creating an incident from the Report Incident form (button on the bottom left) or only from the table Incidents > New?

The Report Incident button & table -> new both result in the same "list index out of range" error. I can confirm the dispatch-contact plugin is enabled.
Are there plugins I should disable here to reduce complexity of debugging this? Full plugin listing:

I would disable all plugins except dispatch-contact, dispatch-ticket  and dispatch-auth-provider-basic
Also, I found something we should change. We're swallowing the actual exception here:
https://github.com/Netflix/dispatch/blob/master/src/dispatch/incident/views.py#L110
But we should also log it so we're not in the dark like we are now.
Would you be able to patch that file add logging to the line I mentioned? Something like this:
import logging
log = logging.getLogger(__name__)

---snip---

    try:
        incident = create(
            db_session=db_session, reporter_email=current_user.email, **incident_in.dict()
        )
    except Exception as e:
        log.exception(e)  # add some real logging
        raise HTTPException(status_code=400, detail=str(e))

---snip---

I will create a PR with that logging separately.

Alright, after disabling all plugins except those 3, I can now create an incident successfully (200 response). If I re-enable the pagerduty plugin, create a pagerduty service, and associate that service with an incident type as the "commander service", the "list index out of range error occurs again. I'll patch that logging in and update shortly.

Okay, the issue seems to be resolved. The problem is that the pagerduty service/escalation policy associated with Dispatch did not have a schedule (just statically assigned users), which caused an issue with the PD plugin on incident creation. Creating an on-call schedule and assigning that to the PD escalation policy, instead of an individual user, resolved the issue.
Full exception:
web_1        | 2021-06-16T21:10:50.502157213Z ERROR:list index out of range:/usr/local/lib/python3.8/site-packages/dispatch/incident/views.py:create_incident:113
web_1        | 2021-06-16T21:10:50.502180012Z Traceback (most recent call last):
web_1        | 2021-06-16T21:10:50.502187287Z   File "/usr/local/lib/python3.8/site-packages/dispatch/incident/views.py", line 109, in create_incident
web_1        | 2021-06-16T21:10:50.502193120Z     incident = create(
web_1        | 2021-06-16T21:10:50.502198444Z   File "/usr/local/lib/python3.8/site-packages/dispatch/incident/service.py", line 238, in create
web_1        | 2021-06-16T21:10:50.502203962Z     assign_incident_role(
web_1        | 2021-06-16T21:10:50.502209326Z   File "/usr/local/lib/python3.8/site-packages/dispatch/incident/service.py", line 44, in assign_incident_role
web_1        | 2021-06-16T21:10:50.502215330Z     assignee_email = oncall_plugin.instance.get(service_id=service.external_id)
web_1        | 2021-06-16T21:10:50.502243970Z   File "/usr/local/lib/python3.8/site-packages/dispatch/decorators.py", line 58, in wrapper
web_1        | 2021-06-16T21:10:50.502250512Z     result = func(*args, **kwargs)
web_1        | 2021-06-16T21:10:50.502255161Z   File "/usr/local/lib/python3.8/site-packages/dispatch/decorators.py", line 74, in wrapper
web_1        | 2021-06-16T21:10:50.502259846Z     return func(*args, **kwargs)
web_1        | 2021-06-16T21:10:50.502264341Z   File "/usr/local/lib/python3.8/site-packages/dispatch/plugins/dispatch_pagerduty/plugin.py", line 33, in get
web_1        | 2021-06-16T21:10:50.502269212Z     return get_oncall(client=client, service_id=service_id)
web_1        | 2021-06-16T21:10:50.502273776Z   File "/usr/local/lib/python3.8/site-packages/dispatch/plugins/dispatch_pagerduty/service.py", line 28, in get_oncall
web_1        | 2021-06-16T21:10:50.502278461Z     return get_oncall_email(client, service)
web_1        | 2021-06-16T21:10:50.502283300Z   File "/usr/local/lib/python3.8/site-packages/dispatch/plugins/dispatch_pagerduty/service.py", line 19, in get_oncall_email
web_1        | 2021-06-16T21:10:50.502288158Z     user_id = list(oncalls)[0]["user"]["id"]
web_1        | 2021-06-16T21:10:50.502293118Z IndexError: list index out of range
web_1        | 2021-06-16T21:10:50.503504808Z INFO:     <IP_ADDRESS>:35506 - "POST /api/v1/default/incidents HTTP/1.0" 400 Bad Request

Cool. Glad you got it figured out. We should probably provide a better error message for that. I'll cut a PR.


tests(proxy) Increase delay to workaround Travis failures

Workaround the intermittent Travis failures we keep getting,
by increasing the delay in error_default_type_spec.lua tests
to 1 second.
These tests are failing because they update the configuration,
run kong reload, wait for an arbitrary amount of time, then
run the test. This arbitrary amount of time (currently 0.5s)
is not always enough, so while increasing it is not a real
solution to the problem, at least it can make our Travis tests
pass on these, so that the fail/pass status in the Travis/Github
integration becomes useful again.
See #2803.

Turns out the Travis run for this PR failed because we have more intermittent failures unrelated to this fix. I restarted the build manually on Travis two more times and out of the three runs I had two failures and one success (with failures erroring on different tests — unfortunately I didn't write down the offenders and Travis doesn't seem to save the logs for restarted jobs).

One of the new intermittent failures was this:
spec/02-integration/00-helpers/00-helpers_spec.lua @ 7: helpers: assertions and modifiers setup

Wondering if each of these intermittent failures should be made into new issues.


import quill-emoji

I want to use it in conjunction with quill-emoji, but it still does not work. Who has encountered the same problem as me and how to solve it?

I use vue-quill-editor, emoji is introduced, there are no errors, but the emoticon icon is not displayed, and there is no click event

You should install quill-emoji.
#370 check this.


FOSCommentBundle : ServiceNotFoundException:

Hi I try to install FOSComment.
After do all step in setup manual, I have this debug message.
ServiceNotFoundException: The service "fos_comment.listener.comment_spam" has a dependency on a non-existent service "%fos_comment.spam_detection.comment%".
Thank for your help

Can you give your configuration of this bundle?


Assume service team IAM role for integration tests

Create onboarding document for service teams to join the Prow cluster
Add service-role lookup into Prow job wrapper

Completed in https://github.com/aws-controllers-k8s/test-infra/pull/30


Updating preview gallery order of items.

Fixes #3934
Quick fix to where the latest submission image get added to in the mini gallery after a user crops a new image.
@DoSomething/front-end

:ship:


Too many language labels

Hi,
Is there a way to specify the preferred language in LodLive?
Consider this : http://lod.kb.nl/LodLive/?http://viaf.org/viaf/64013650
Some resources contain too many language labels to fit into the cicle.
Thanks,
Roland

it's pretty strange, labels should be ellipsed
look at http://en.lodlive.it/?http://dbpedia.org/resource/Rome
as you pointed out something is wrong with http://en.lodlive.it/?http://viaf.org/viaf/64013650 I'll check it

done!


Update pools_list.json

Issue with the logoURI of bLuna in the pool bLuna-Solid
Description and Motivation

Related Issues

Checklist:

[x] I have read Migaloo's contribution guidelines.
[x] My pull request has a sound title and description (not something vague like Update index.md)
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation.
[x] The code is formatted properly yarn lint.
[x] The project builds and is able to deploy on Netlify yarn build.

bLUNA become bLuna (it was an error of logoURI)


Set project root, to enable filtered clickable stack traces in rollbar.

Looks good
On Wednesday, April 22, 2015, Michael Hale<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/heroku/telex/pull/38
Commit Summary

Set project root, to enable filtered clickable stack traces in
rollbar.

File Changes

M config/initializers/rollbar.rb
https://github.com/heroku/telex/pull/38/files#diff-0 (2)

Patch Links:

https://github.com/heroku/telex/pull/38.patch
https://github.com/heroku/telex/pull/38.diff

—
Reply to this email directly or view it on GitHub
https://github.com/heroku/telex/pull/38.

+1!
On Wed, Apr 22, 2015 at 11:36 AM, Will Leinweber<EMAIL_ADDRESS>wrote:

Looks good
On Wednesday, April 22, 2015, Michael Hale<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/heroku/telex/pull/38
Commit Summary

Set project root, to enable filtered clickable stack traces in
rollbar.

File Changes

M config/initializers/rollbar.rb
https://github.com/heroku/telex/pull/38/files#diff-0 (2)

Patch Links:

https://github.com/heroku/telex/pull/38.patch
https://github.com/heroku/telex/pull/38.diff

—
Reply to this email directly or view it on GitHub
https://github.com/heroku/telex/pull/38.

—
Reply to this email directly or view it on GitHub
https://github.com/heroku/telex/pull/38#issuecomment-95295174.


请问如何让侧边栏的文章目录全部展示

现在都是每次滑到哪儿文章目录展开到哪。这样查看文章结构就很不方便，请问怎么设置才能让文章目录默认全部都展开？

请问设置toc:
enable: true
(# 标题)虽然可以显示目录，但是无法点击跳转到指定位置，怎么解决

add the code to themes/next/source/css/_custom/custom.styl
.post-toc .nav .nav-child { display: block; }
the menu will expand all levels by default.

NexT is rebased into organization repo.
If you want new feature, fix, or support, create new in NexT v6.x repo (desirable in English).
There is instructions on English or Chinese how to update from v5.1.x to v 6.x
You also may read this for details.


Worker-side monitoring without UDP

Is your feature request related to a problem? Please describe.
The present worker-side monitoring uses UDP, which is lossy. Losses have been observed in practice in DESC runs.
Other worker communication, such as HTEX task submission/result-returning, is not lossy.
Worker-side monitoring should not be lossy.
Describe the solution you'd like
In the desc branch I've prototyped switchable worker->submit side monitoring channels; UDP remains an option. In addition to that, I have implemented:

an HTEX-specific channel which sends monitoring information over the same ZMQ channels as task results.

a shared filesystem based channel, which works with non-HTEX executors such as the workqueue executor. I expect that this scales extremely poorly (because of shared-fs access from all nodes) but is not lossy.

Additional context
This work is part of LSST DESC CI

Here is a third option:
Write the monitoring data sequentially to a file, in the current directory of the task.
Specify the file as an output file in WQ, and additionally give the WORK_QUEUE_WATCH flag.
The WQ worker will periodically send back new output over the manager->worker connection.
From the manager side, it just looks like the file is growing sequentially as the task runs, rather than waiting until the task is complete.
Then, a shared filesystem is not required, at least when using WQ.
Would that help?

@dthain that looks good.


Changed feedback from dialog to less obtrusive message

Love the plugin, but felt that the dialog was an extra click and more obtrusive than the message down in the bottom center of the canvas.  Let me know what you think.

Good one!


Incorrect react multiline comments formatting

Input:

{/*
Some very very very very long line to break line width limit
*/}

Result:

  {/*
Some very very very very long line to break line width limit
*/
  }

Repro link:
https://jlongster.github.io/prettier/#{"content"%3A"
{%2F*
Some very very very very long line to break line width limit. <%2Fdiv>*%2F}<%2Fdiv>"%2C"options"%3A{"printWidth"%3A80%2C"tabWidth"%3A2%2C"singleQuote"%3Afalse%2C"trailingComma"%3Afalse%2C"bracketSpacing"%3Atrue%2C"jsxBracketSameLine"%3Afalse%2C"doc"%3Afalse}}


Flux.1.dev.fp8 CKPT trainning the avr_loss keep 'nan'

i was trying to trainning a lora which use flux.1.dev.fp8 CKPT,and the log keep telling me that avr_loss is nan,i do not know where i setting wrong or someting?
the system & version:
[START] Security scan
[DONE] Security scan
ComfyUI-Manager: installing dependencies done.
** ComfyUI startup time: 2024-09-28 16:52:30.478163
** Platform: Windows
** Python version: 3.11.8 (tags/v3.11.8:db85d51, Feb  6 2024, 22:03:32) [MSC v.1937 64 bit (AMD64)]
** Python executable: D:\comfyUI\ComfyUI_windows_portable_nvidia.7z\python_embeded\python.exe
** ComfyUI Path: D:\comfyUI\ComfyUI_windows_portable_nvidia.7z\ComfyUI
** Log path: D:\comfyUI\ComfyUI_windows_portable_nvidia.7z\comfyui.log
Prestartup times for custom nodes:
0.0 seconds: D:\comfyUI\ComfyUI_windows_portable_nvidia.7z\ComfyUI\custom_nodes\rgthree-comfy
0.0 seconds: D:\comfyUI\ComfyUI_windows_portable_nvidia.7z\ComfyUI\custom_nodes\ComfyUI-Easy-Use
4.2 seconds: D:\comfyUI\ComfyUI_windows_portable_nvidia.7z\ComfyUI\custom_nodes\ComfyUI-Manager
Total VRAM 6144 MB, total RAM 32461 MB
pytorch version: 2.3.1+cu121
Set vram state to: NORMAL_VRAM
Device: cuda:0 NVIDIA GeForce RTX 3060 Laptop GPU : cudaMallocAsync
Using pytorch cross attention

Not seen that happen myself, I'd recommend updating to torch 2.4.1 though, it's what kohya recommends to be used and it has solved lots of memory and speed issues for many who have updated.

我自己没见过这种情况，但我建议更新到 torch 2.4.1，这是 kohya 建议使用的，它已经为许多更新过的人解决了许多内存和速度问题。

ok ,i will try to update,thank you so much

Not seen that happen myself, I'd recommend updating to torch 2.4.1 though, it's what kohya recommends to be used and it has solved lots of memory and speed issues for many who have updated.

hi, i am upgrade the pytorch to 2.4.1,but the loss still keep "nan"……

What is your optimizer used? Or maybe u attach your workflow here.

大概率是学习率问题

你是怎么做到这么慢的，如果是batch size太大按理说这个速度早就oom了


continued gray tiles and timeslider console errors

We thought we got these fixed over in #262, but @jeffreyameyer reports they are back:

this looks to me like another bad loading condition of some kind, but I am not sure what kind.
Jeff, had you just navigated here from another page?

Not sure where I came from... will try to repro.
In addition, this is the type of thing I'm hoping we can catch as soon as users see them using the "Browser" app in New Relic... not sure it's the exact right hammer for this nail, but I'm curious if it would help: https://docs.newrelic.com/docs/browser/

Just spun around various zooms and timeslider reconfigs and slipping around & this popped up:

So... not sure if this is the same issue as before, but there's more. Other tiles are closer to the middle of the map & are more of a performance (slow to update / render) issue, but it's impacting user experience to see a gray checkerboard.

And, again... not sure what led to this prior to search, but this is a result of search + clicking on one of the results

Hmmm... this is not really a location-specific behavior, so I'm not sure a link to a specific x/y/z will provide what you need.
Seeing it right now in France.
https://www.openhistoricalmap.org/#map=15/46.7656/5.1554&layers=O&date=1900&daterange=1800,2021

OK, moving up the priority list the install of NewRelic browser monitoring. Going to file a separate ticket for that

I wonder if this could be a similar root cause to #286, where have race conditions on timeslider startup

I'm hopeful that the fixes we put in place for #286 will eliminate this issue, but I'm going to leave open for a while to see. We also have browser monitoring now running on production in New Relic, so we can look back at that for JS errors periodically and see what's happening to other users as well

Still seeing them as of today... (this is what I was referring to in today's standup)


Replace twoway crate with memchr

The twoway crate has been deprecated, as can be seen from the first line of the docs

Looks good to me. @SergioBenitez any reviews?

@paolobarbolini, thanks for the PR.

Would be great to get a release with this, @rousan.

Ping @rousan. It's a bit annoying when changes are merged but no release is made for months :smiley:

Hi, sorry for the delay. I just released a version from master branch.
v2.0.2

Thanks @rousan