[WIP] Integrate Construction API 2.0

Related Issue: #112
Blocking PR: https://github.com/coinbase/rosetta-sdk-go/pull/118

Pull Request Test Coverage Report for Build 4193

9 of 15 (60.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+15.2%) to 90.173%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

configuration/configuration.go
9
15
60.0%

Files with Coverage Reduction
New Missed Lines
%

configuration/configuration.go
1
90.17%

Totals

Change from base Build 4167:
15.2%

Covered Lines:
156

Relevant Lines:
173

💛  - Coveralls


Iterator preserves last delta link

Overview
Related to #190
The PageIterator now stores and exposes the odata.nextLink and odata.deltaLink values from the most recent page.
Also fixed a related bug that allowed you to call Iterate indefinitely and always get the last item.

@rkodev

@eric-milin please update the change log

Done

@eric-millin please rebase this pr of the main branch so checks can re run


extract the duel.dll file

hello, sorry for bothering you,this is not the issues. So did you know how to open the duel.dll file and read data in it? thanks for your reading.

i use dotpeek and see this name, can you tell me how to extract this?, Sorry for my bad english

It's a library coded in C which contains the duel engine for master duel. C gets compiled to machine code and can't be "extracted". You can use tools like IDA to decompile functions into pseudocode but there aren't any debug symbols for duel.dll so the usefulness would be limited.


VECTOR-68 Vector dimensions are not being validated correctly

LGTM
note that you can remove the old vector(Float) signature from CQLTester since you added the generic version

Thanks for the review. I have removed the CQLTester.vector(Float) signature.
Are those CI results good? There is a bunch of failures, but they don't seem related to the changes. For example, the failure of VectorTypeTest#emptyIndexTest seems to be locally reproducible on the vsearch branch this PR is based on.


WIP: Update to new scalismo version

An initial preview of changes needed to update to new scalismo dependency and the complete migrating to scala 3. Yet not all warnings are fixed.

What happened to the integration tests? I see that no CI is running?

You were right, the build.sbt was indeed missing. I corrected that now.
I do not yet know what happened to the CI. Maybe never setup correctly or it was not maintained and is now outdated.


Add annotation to indicate parent workload by Kueue

What type of PR is this?
/kind feature

What this PR does / why we need it:
It is needed for the Kueue integration with other frameworks. The first integration we will need it for is with the MPI operator framework. The annotation will be added by a webhook to the child job created by a framework (the Launcher job in case of the MPIJob). A job with this annotation will not create a Kueue workload, but reuse the workload created by its parent job (the MPIJob in the case of the integration with MPIJob).
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
WIP, because not tested yet.

/assign @alculquicondor @tenzen-y

Squashed the commits


Try Fix encoding

The pound sign in this code sample renders incorrectly

https://docs.microsoft.com/en-us/dotnet/api/system.single.tostring?view=netframework-4.8
I believe this is because the file was ISO-8859-1 encoded rather than UTF-8. This message popped up when trying to edit it - according to GitHub the file encoding will be automatically changed when the commit is made.
I also had to make an unrelated change for GitHub to allow me to submit the PR.

Hmm. The displayed result still looks incorrect.  @rpetrusha Do you have any ideas?

I can take a look

The same issue, incidentally, is true of the VB example.

I'm sure that I'm missing some obvious point, @BillWagner, but in the absence of merging it and building the article where it's used, how do we know that it isn't rendering properly?

@rpetrusha @ChrisMaddock When I look at the update, the £ symbol was not appearing in the first diff line. Could have been my mistake this morning. What are you seeing?
And, yes, I agree that the VB sample should also be fixed.

There are several issues I found. I'll submit a PR separately that you can compare with this.

I am seeing the £ symbol in the first diff line.

I submitted #1085 to fix encoding problems in C# and VB source files. I found 108 files impacted.

Thanks for pointing out this issue, @ChrisMaddock. Since #1085 offers a more comprehensive fix, I'll close this PR.


Config4 Enum Representation

Add Config 4 to RegisterMask and RegisterPosition (+all needed small size enum types, like on/off etc.)

Finished


Make all ITs use per-test server:

Overview
That prevents interference between tests in case of failures; and
enables them to run concurrently.
± 3472b64841753bedbe91f4bef530fb717ef0599c

See: https://jira.bf.local/browse/ECR-XYZ
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

Coverage remained the same at 85.478% when pulling 8d2cde5a7bc55cbc35bde9f71b78b22a77e5d12d on dmitry-timofeev:fix-par-tests-in-lc into 3877080a964eb889a5a785f9f7e8a0c34bf20520 on exonum:master.

This goes next to prevent any possible failures with concurrent execution.


Not compatible with models made up of multiple meshes

Hi,
I've started using this for a project, and it seems to work great so far. However, this doesn't really seem to work with ragdolls made up of more than one mesh.
I have a model with a mesh for the body, and some of the meshes on the head are actually separated (Such as a hat, etc). However, the skinned mesh renderer splittable only supports one mesh. I have attempted to add more than one of the script pointing to different objects (I am aware of it being bad practice), but only the body mesh is sliced, and other meshes are just duplicated in the cloned armature. I also can't seem to get the armature splitting working when the SplittableSkinned component is anywhere but the root character.
Is there a way you have in mind where a ragdoll with multiple meshes can be split apart? The tutorial doesn't seem to have that either.
Thanks

Hi @POWERUPT,
The MeshSplitter/Splittable workflow indeed doesn't support child meshes of skinned meshes. This is really an oversight on my part since it would have been nice to have. What you want to achieve should be possible using the MeshSplitter only workflow, but it will require some more work since you're have to create the split game objects yourself after getting the result of the split. If you want an example on how you could do this, you can look at the CreateSplitObjectsSkinned method in MeshSplitterSkinned.cs.
As for this missing feature, I'll be adding the limitations in the docs but unfortunately won't be fixing it as I've moved on to other projects.
Greetings,


WIP V0.2.0 - New Theme System

New in this PR...

[x]  All new theme system and API for theming based on StyleSheet API
[x]   New Carousel component that now snaps and no scroll bar on web and autoplay
[x]   Moved to storybook for docs as RSG is no longer maintained
[x]   Moved to expo for native example app
[x]   Co-located docs, tests, and components
[x]   Updated RN, and React
[x]   Refreshed default theme colors
[x]   Merged TabButton into SegmentedControlButton
[ ]   Added visual regression tests
[ ]   Generate sketch files using stock or custom themes
[ ]   fix SVG icon rendering

Documentation for the theme system can be found here: https://github.com/mattapperson/nachos-ui/blob/new-theme/src/Theme/ThemeProvider.md

I'll continue tomorrow. Good night 🌚

Am I understand it correctly that storybook is going to be used instead of https://avocode.com/nachos-ui/docs/#!.?

Am I understand it correctly that storybook is going to be used instead of https://avocode.com/nachos-ui/docs/#!.?

Correct, it seems the best alternative for a still-maintained docs provider?


Fix: Calculate the efficiency correctly in API

Example:
Valid shares: 24638
Invalid shares: 57947
Old code: -135.19%
New code: 29.83%

Could you switch the PR against the development branch? Thanks!

Done.
While doing so I found out that this could actually end up deciding by zero, applied a second commit for that.

Thanks!


Allow findc and findt commands to search via tag

As per title

Document UG with relevant examples when done

Will settle this with changing predicate

Done in adrianongjj's PR. Closed


blackboard bold symbols in MathML mode with Firefox

I have noticed that if I have MathML produced by itex blackboard bold symbols are correctly displayed by MathJax 2.0 in MathML mode with Firefox (see http://www.math.ist.utl.pt/seminars/). The same applies for LateX displayed in HTML-CSS mode (see http://blog.math.ist.utl.pt/). But they fail to display correctly for LaTeX displayed in MathML mode (see http://blog.math.ist.utl.pt/). It seems MathJaX has a limitation on this but there is no real reason for that.
I do have the latest STIX fonts installed and am using Debian wheezy. Firefox is the latest from www.mozilla.com.

OK, thanks for the report.  Firefox doesn't currently implement the mathvariant="double-struck" attribute, so MathJax sets up some CSS rules to ask Firefox to use MathJax's web fonts for this.  Unfortunately, the URL wasn't being set properly.  I have fixed the URL in the v2.0-latest branch of MathJax.

itex translates \mathbb{R} to the entity ℝ which in turn is translated by MathJax to the binary unicode character. This route is fine.
If entering (\mathbb{R}) MathJax provides R which is displayed correctly if using HTML-CSS but not if using MathML.

As I said, the issue with NativeMML is resolved in the v2.0-latest branch of MathJax, so if you use that, it should work in all output modes.


Windows 7 Pro: Terminal text disappears on VSC window resize, pane snap & Explorer pane resize.

VSCode Version: Code 1.14.2 (cb82febafda0c8c199b9201ad274e25d9a76874e, 2017-07-19T23:34:19.566Z)
OS Version: Windows_NT x64 6.1.7601
Extensions:

Extension
Author (truncated)
Version

jshint
dba
0.10.15

vscode-eslint
dba
1.2.11

vscode-html-css
ecm
0.1.7

auto-close-tag
for
0.4.3

beautify
Hoo
1.1.1

debugger-for-chrome
msj
3.1.6

vetur
oct
0.9.3

vscode-icons
rob
7.11.0

(4 theme extensions excluded)

Steps to Reproduce:
Console before error.

Have console output text.
2a. Move VSC to left or right side of screen so that the "pane snap" preview appears.
2b. Resize VSC window to a smaller size.
2c. Adjust Explorer size to make terminal smaller.
Parts of the terminal text will disappear and cannot be recovered.

Reproduces without extensions: Yes/No

@danaoira
cc @Tyriar
This is by design and a function of the way xterm interacts with the shell.
Duplicate of #30430
See discussion there as well.


propose-update needs better changelog handling

At the moment it seems that packit propose-update just blindly copies the %changelog from upstream's .spec file to downstream dist-git. E. g. for my test fork of cockpit-podman with a fake 1.1 release, I get this generated dist-git diff:
--- a/cockpit-podman.spec
+++ b/cockpit-podman.spec
@@ -1,12 +1,11 @@
-# This spec file has been automatically updated
-Version:        1
-Release:        2%{?dist}
 Name:           cockpit-podman
+Version:        1.1
+Release:        1%{?dist}
 Summary:        Cockpit component for Podman containers
 License:        LGPLv2+
 URL:            https://github.com/cockpit-project/cockpit-podman

-Source0:        https://github.com/cockpit-project/cockpit-podman/releases/download/%{version}/cockpit-podman-%{version}.tar.gz
+Source0:        https://github.com/martinpitt/cockpit-podman/releases/download/%{version}/cockpit-podman-%{version}.tar.gz
 BuildArch:      noarch
 BuildRequires:  libappstream-glib

@@ -32,6 +31,3 @@ appstream-util validate-relax --nonet %{buildroot}/%{_datadir}/metainfo/*
 %{_datadir}/metainfo/*

 %changelog
-* Wed Apr 17 2019 Cockpit Project<EMAIL_ADDRESS>- 1-2
-- Update to upstream 1 release
-

packit must expect, and not change, existing %changelog entries in downstream dist-git, and just create a new entry on release. This could use rpmdev-bumpspec(1), which by and large does the right thing, and even has a --file option to read the entry from.
Commonly, upstream tags have a description that appears on the GitHub release page, and usually summarizes the news from that release. This would make an excellent default changelog entry unless the user specifies something different through a packit option. It's e. g. what cockpituous' release-srpm does, feel free to steal code/ideas.
Maintaining the complete changelog upstream does not work, as one and the same upstream release commonly goes to different releases of Fedora and RHEL, where they necessarily have to deviate. So upstream .spec files should usually just keep an empty %changelog.

OK, I got your point. From the packit perspective, there are two points:

Generating a new changelog from the release.

Should not be hard to implement, we already have a code to get release information.
If we have the same specfile in upstream and downstream, it would be enough. (We have also packit sync-from-downstream for this purpose.)

Do not sync the whole specfile.

For now, we are only copying the files specified in config from upstream to downstream.
There is (currently) no difference between specfile and other files how they are copied.
It is only needed if the upstream and downstream specfile differ:

=> if this is not a usual situation, we can add some action/hook to handle this situation.
=> if this is a usual situation, we need to handle it in a different way, but not sure how easy it can be.

Are you aware of any Fedora or RHEL packages which have identical spec files? From my experience that is  almost impossible, e. g. bugzilla refs between the two are different more often than not, and release cycles also vary a lot (i. e. not every time you update Fedora you can update RHEL, and RHEL point release updates don't go into Fedora). So I'd say that differering %changelog are the norm.

This is tough. I agree with Martin that changelogs differ between Fedora versions and RHEL, so they are really specific to a dist-git branch.
I propose to solve this by allowing people to control the handling of the spec file:

packit would perform rpmdev-bumpspec by default:

people will be able to configure this: supply the file for the changelog entry comment
supply the comment via CLI
disable bumpspec altogether

packit will not copy the changelog from upstream by default (can be changed in the config file)
the whole %changelog handling can be replaced with a custom action

Does this make sense?

@TomasTomecek : Yes, this makes perfect sense. II would even simplify it -- either you use the default behaviour (rpmdev-bumpspec with text from tag), or you supply a custom command that does the entire .spec mangling by itself. More fine-grained configurability and behaviours are just a pain to implement, test, maintain, and understand, IMHO.
Also, while it's not trivial, I don't think it's that tough - it's mostly about grabbing the text from the tag and tossing it to rpmdev-bumpspec. I'm sure that there are some details to be worked out, like the name/email and so on, but what cockpit's release-srpm does seems to work fine by and large (see the link in the description).


remove valueOf property from results of config.get()

Get rid of the annoying { valueOf: undefined } property resulting from prototype flattening.
cc @Raynos

lgtm.

@Raynos can you publish this to unpm too?


Different behaviors for cosmos db linux emulator on unbuntu 18 vs 20 image

Description
Copied from https://github.com/Azure/azure-cosmos-dotnet-v3/issues/3010
Describe the bug
Using Azure DevOps and a ubuntu-latest hosted agent, when starting the container, the container returns right away the following:
This is an evaluation version.  There are [165] days left in the evaluation period.
Shutting Down
Shut Down

Additional context
Can't use older images (tags) to see if the code has changes since, as it fails the evaluation time check
Is there something I can add as environment variable to get more logs out to diagnose the problem?
Virtual environments affected

[ ] Ubuntu 18.04
[X] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Agent name: 'Hosted Agent'
Agent machine name: 'fv-az31-196'
Current agent version: '2.198.2'
Operating System
Virtual Environment
Virtual Environment Provisioner
Current image version: '20220131.1'
Agent running as: 'vsts'
Is it regression?
No response
Expected behavior
The container should create the partitions and return "Started" at some point
Actual behavior
The container exits and the logs shows
This is an evaluation version.  There are [165] days left in the evaluation period.
Shutting Down
Shut Down

Repro steps
Create an Azure DevOps pipeline with the following:
pool:
  name: Azure Pipelines
  vmImage: 'ubuntu-latest'
jobs:
- job: TestJob
  displayName: 'My Job'
  steps:
  - task: PowerShell@2
    name: showNetAdapters
    displayName: 'Show NetAdapters'
    inputs:
      pwsh: true
      targetType: inline
      script: |
        ifconfig
        $ipAddress = (hostname -I | awk '{print $1}')
        Write-Output "IpAddress = $ipAddress"
  - task: PowerShell@2
    name: startCosmosDb
    displayName: 'Start Azure Cosmos DB emulator'
    inputs:
      pwsh: true
      targetType: inline
      script: |
        $ipAddress = (hostname -I | awk '{print $1}')
        $containerId = (docker create -p 8081:8081 -p 10251:10251 -p 10252:10252 -p 10253:10253 -p 10254:10254 -m 3g --cpus=2.0 -e AZURE_COSMOS_EMULATOR_PARTITION_COUNT=10 -e AZURE_COSMOS_EMULATOR_ENABLE_DATA_PERSISTENCE=false -e AZURE_COSMOS_EMULATOR_IP_ADDRESS_OVERRIDE=$ipAddress mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator)
        Write-Host "##vso[task.setvariable variable=cosmosDbContainerId]$containerId"
        docker start $containerId
        Start-Sleep -Seconds 5
        $isStarted = $false
        while ($isStarted -eq $false) {
            $logs = (docker logs $containerId)
            if ($logs.Contains('Started')) {
                Write-Output "Container $containerId started."
                $isStarted = $true
                break;
            }
            Write-Output "Waiting for container $containerId to start"
            Write-Output ($logs | Out-String)
            Start-Sleep -Seconds 5
        }
  - script: |
      echo 'ContainerId = $(cosmosDbContainerId)'
      docker logs $(cosmosDbContainerId)
    displayName: Diagnostics
  - script: |
      ipAddress=$(hostname -I | awk '{print $1}')
      curl -k https://$ipAddress:8081/_explorer/emulator.pem > $(Agent.TempDirectory)/emulatorcert.crt
      sudo cp $(Agent.TempDirectory)/emulatorcert.crt /usr/local/share/ca-certificates/
      sudo update-ca-certificates
      echo "##vso[task.setvariable variable=cosmosDbEndpoint]https://$ipAddress:8081"
    displayName: 'Prepare emulator'
  - script: |
      if [ ! -z "$(cosmosDbContainerId)" ];
      then
        docker rm -f $(cosmosDbContainerId)
        sudo rm -f /usr/local/share/ca-certificates/emulatorcert.crt
      fi
    displayName: 'Clean Azure Cosmos DB emulator'
    condition: always()

Hi @DOMZE .
Thanks you for tour report. We will take a look at this.

Hello @DOMZE your repro yml fails on all environments (not only on Ubuntu 20) since it incorrectly creates docker container for CosmosDB. Please use this one guideline to correctly create container. These steps work for me.
I'm going to close this issue since it's not related to image generation.

How does it incorrectly creates the docker container?
docker create and docker start is just docker run split in 2 commands (docker run = docker create + docker start)...
also on the official docs, they run the container in interactive mode (using -it), which clearly can't be done in an automated environment.
It also says after the running the container in interactive mode: After the emulator is running, using a different terminal, different terminal because the original terminal is blocked by TTY...
So to go back to my last point on Azure Devops (not github actions...), doing the command as you showed (docker run, results in the following error from docker):
the input device is not a TTY
which makes sense considering there's no TTY...
So just want to know, how can one work (in my azure devops agent using ubuntu 18 and not in ubuntu 20)? the SAME exact pipeline YAML?

@nikolai-frolov
The script below works (and is using the DevOps recommended Docker approach) yet if you specify ubuntu-latest as the image, it doesn't. You'll see that by the 'Stopping container' messages in the powershell task.

trigger: none

pool:
  name: Azure Pipelines
  vmImage: 'ubuntu-18.04'

resources:
  containers:
  - container: azure-cosmosdb-emulator
    image: mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator
    ports:
    - "8081:8081"
    - "10251:10251"
    - "10252:10252"
    - "10253:10253"
    - "10254:10254"
    options: --name azure-cosmosdb-emulator -m 3g --cpus=2.0 -e AZURE_COSMOS_EMULATOR_PARTITION_COUNT=20 -e AZURE_COSMOS_EMULATOR_ENABLE_DATA_PERSISTENCE=false -e AZURE_COSMOS_EMULATOR_IP_ADDRESS_OVERRIDE=<IP_ADDRESS>

jobs:
- job: Job
  displayName: 'Job'

  services:
    azure-cosmosdb-emulator: azure-cosmosdb-emulator

  steps:

  - task: PowerShell@2
    name: startCosmosDb
    displayName: 'Wait for Cosmos'
    inputs:
      pwsh: true
      targetType: inline
      script: |
        $isStarted = $false
        while ($isStarted -eq $false) {
            $logs = (docker logs azure-cosmosdb-emulator)
            if ($logs.Contains('Started')) {
                Write-Output "Container $containerId started."
                $isStarted = $true
                break;
            }
            Write-Output "Waiting for container azure-cosmosdb-emulator to start"
            Write-Output ($logs | Out-String)
            Start-Sleep -Seconds 5
        }

At the first of all, they use -d flag which allow to run container in background. Also it works fine without -it flags as well.
- name: Check execution
        shell: pwsh
        run: |
          $ipaddr = ifconfig | grep "inet " | grep -Fv <IP_ADDRESS> | awk '{print $2}' | head -n 1
          docker pull mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator
          docker run -d -p 8081:8081 -p 10251:10251 -p 10252:10252 -p 10253:10253 -p 10254:10254  -m 3g --cpus=2.0 --name=test-linux-emulator -e AZURE_COSMOS_EMULATOR_PARTITION_COUNT=10 -e AZURE_COSMOS_EMULATOR_ENABLE_DATA_PERSISTENCE=true -e AZURE_COSMOS_EMULATOR_IP_ADDRESS_OVERRIDE=$ipaddr mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator
          docker ps --all

Please double check parameters which are passed during container creation and provide the build link if it still doesn't work for you.

Hi @nikolai-frolov could you give the yaml code I posted a try? It's pretty clear from there that the container is stopping immediately (and the pipeline won't complete)

@soenneker it works fine on 20.04 ADO after adding of endpoint to your infinite cycle:

trigger: none

pool:
  name: Azure Pipelines
  vmImage: 'ubuntu-20.04'

resources:
  containers:
  - container: azure-cosmosdb-emulator
    image: mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator
    ports:
    - "8081:8081"
    - "10251:10251"
    - "10252:10252"
    - "10253:10253"
    - "10254:10254"
    options: --name azure-cosmosdb-emulator -m 3g --cpus=2.0 -e AZURE_COSMOS_EMULATOR_PARTITION_COUNT=20 -e AZURE_COSMOS_EMULATOR_ENABLE_DATA_PERSISTENCE=false -e AZURE_COSMOS_EMULATOR_IP_ADDRESS_OVERRIDE=<IP_ADDRESS>

jobs:
- job: Job
  displayName: 'Job'

  services:
    azure-cosmosdb-emulator: azure-cosmosdb-emulator

  steps:

  - task: PowerShell@2
    name: startCosmosDb
    displayName: 'Wait for Cosmos'
    inputs:
      pwsh: true
      targetType: inline
      script: |
        $isStarted = $false
        $retriesCount = 10
        while ($isStarted -eq $false -or $retriesCount -ne 0) {
            $logs = (docker logs azure-cosmosdb-emulator)
            if ($logs.Contains('Started')) {
                Write-Output "Container $containerId started."
                $isStarted = $true
                break;
            }
            Write-Output "Waiting for container azure-cosmosdb-emulator to start"
            Write-Output ($logs | Out-String)
            Start-Sleep -Seconds 5
            $retriesCount--
        }
        docker ps --all

Well, seems issue is reproducible not at all 100% cases. I will investigate this deeply.

@milismsft does mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator image create logs somewhere? I can't find a reason why this container stops just after the start on ubuntu 20.04 (docker client is identical with 18.04 and it seems like compatibility issue for now)...

@nikolai-frolov did you try to execute that workload locally on a Ubuntu 20.04 Linux VM or local machine? The only issue that I'm aware of is when using the Azure DevOps pipeline configured with Ubuntu 20.04 (seems that 18.04 works just fine), and will recommend opening a support ticket with the respective Azure team.
There are no extra logs that can be retrieved at this time. The error seems to be coming from the initial setup which initializes the Windows sandbox we run the emulator under. There must be some policies or similar that are in the way of it, unfortunately without a local repro it will be a very hard thing to investigate.

One more thing, the script above that checks for the emulator if it's started, that is incorrect actually. Just because the container is started/running, it does not translate into the emulator being ready to service requests. Please see our public documentation of how to verify that emulator is truly ready (i.e. check through the emulator's "explorer" link if the PEM public certificate key is available).

I tried to reproduce the issue locally on VM with ubuntu-20.04 image, but without luck: every time it successfully starts a container. I used the following:
$containerId = (docker create -p 8081:8081 -p 10251:10251 -p 10252:10252 -p 10253:10253 -p 10254:10254 -m 3g --cpus=2.0 -e AZURE_COSMOS_EMULATOR_PARTITION_COUNT=10 -e AZURE_COSMOS_EMULATOR_ENABLE_DATA_PERSISTENCE=false -e AZURE_COSMOS_EMULATOR_IP_ADDRESS_OVERRIDE=<IP_ADDRESS> mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator)
docker start $containerId
docker ps --all

When I tried to execute the same in the ADO pipeline it also passes (at least 5 pipelines pass in a row):
trigger: none

pool:
  name: Azure Pipelines
  vmImage: 'ubuntu-20.04'

jobs:
- job: Job
  displayName: 'Job'
  steps:
  - task: PowerShell@2
    name: startCosmosDb
    displayName: 'Wait for Cosmos'
    inputs:
      pwsh: true
      targetType: inline
      script: |
        $containerId = (docker create -p 8081:8081 -p 10251:10251 -p 10252:10252 -p 10253:10253 -p 10254:10254 -m 3g --cpus=2.0 -e AZURE_COSMOS_EMULATOR_PARTITION_COUNT=10 -e AZURE_COSMOS_EMULATOR_ENABLE_DATA_PERSISTENCE=false -e AZURE_COSMOS_EMULATOR_IP_ADDRESS_OVERRIDE=<IP_ADDRESS> mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator)
        docker start $containerId
        docker logs --timestamps --details $containerId
        docker ps --all

On the other hand, issue still occurs during using an azure container:
trigger: none

pool:
  name: Azure Pipelines
  vmImage: 'ubuntu-20.04'

resources:
  containers:
  - container: azure-cosmosdb-emulator
    image: mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator
    ports:
    - "8081:8081"
    - "10251:10251"
    - "10252:10252"
    - "10253:10253"
    - "10254:10254"
    options: --name azure-cosmosdb-emulator -m 3g --cpus=2.0 -e AZURE_COSMOS_EMULATOR_PARTITION_COUNT=20 -e AZURE_COSMOS_EMULATOR_ENABLE_DATA_PERSISTENCE=false -e AZURE_COSMOS_EMULATOR_IP_ADDRESS_OVERRIDE=<IP_ADDRESS>

jobs:
- job: Job
  displayName: 'Job'

  services:
    azure-cosmosdb-emulator: azure-cosmosdb-emulator

  steps:

  - task: PowerShell@2
    name: startCosmosDb
    displayName: 'Wait for Cosmos'
    inputs:
      pwsh: true
      targetType: inline
      script: |
        $isStarted = $false
        $retriesCount = 10
        while ($isStarted -eq $false -and $retriesCount -ne 0) {
            $logs = (docker logs azure-cosmosdb-emulator)
            if ($logs.Contains('Started')) {
                Write-Output "Container $containerId started."
                $isStarted = $true
                break;
            }
            Write-Output "Waiting for container azure-cosmosdb-emulator to start"
            Write-Output ($logs | Out-String)
            Start-Sleep -Seconds 5
            $retriesCount--
        }
        docker ps --all

Probably it should be investigated by owning team. I'm going to update https://github.com/microsoft/azure-pipelines-tasks/issues/15865 with my findings.

Issue definitely don't related to Azure DevOps since the same issue occurs in the GitHub Actions which uses it's own GitHub Runner for execution.
@milismsft I've added additional output for ports in use and "docker inspect" (please see this one run to find output of successful 18.04 and failed 20.04 images). Comparing of them it looks like issue occurs during Sandbox creation and it terminates a container. Could you please assist with further investigation?
name: "Cosmos DB check"

on:
  workflow_dispatch:

defaults:
  run:
    shell: pwsh

jobs:
  testing:
    name: Testing
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os: [ ubuntu-18.04, ubuntu-20.04 ]
    steps:
      - name: Start Azure Cosmos DB emulator
        run: |
          Write-Output "Ports in use before container creation:"
          netstat -tulpn | grep LISTEN

          Write-Output "Container creation..."
          $containerId = (docker create -p 8081:8081 -p 10251:10251 -p 10252:10252 -p 10253:10253 -p 10254:10254 -m 3g --memory-swap -1 --cpus=2.0 mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator)

          Write-Output "Container starting..."
          docker start $containerId
          Start-Sleep -Seconds 10
          $retriesCount = 5
          while ($retriesCount -ne 0) {
            $logs = (docker logs $containerId)
            Write-Output ($logs | Out-String)
            if ($logs[-1] -eq 'Started') {
              Write-Output "Container $containerId started."
              break
            }
            Write-Output "Waiting for container $containerId to start..."
            Start-Sleep -Seconds 5
            $retriesCount--
          }

          docker ps --all

          docker inspect $containerId

          Write-Output "Ports in use after container creation:"
          netstat -tulpn | grep LISTEN

I've additionally compared the output of "lscpu" command (see here) and looks like VMX is unsupported on some machines, so probably it's a reason why Windows sandbox can't be created (@milismsft to confirm). It would be good to throw an error which caused the failure to speed up investigation for future failures.
@soenneker, @DOMZE Unfortunately, the underlying hardware is subject to change even without our awareness so that we can't guarantee anything related to the available CPU instructions. If you need any specific CPU instruction it's better to rely on a self-hosted runner for that.

@milismsft @DOMZE could you please reopen related issue (https://github.com/Azure/azure-cosmos-dotnet-v3/issues/3010) for tracking? We are going to close this issue since it looks unrelated to image generation and should be investigated on the owners side. Feel free to contact us for assistance.

@DOMZE I opened https://github.com/Azure/azure-cosmos-db-emulator-docker/issues/45 for tracking purposes.

@milismsft we discussed with you that it's not related to machines. Also issue occurs on both Azure Agents and GitHub Runners which use different services. Your ticket to Azure team without logs and links will not take affect...


add create random points and revise points to line

add create random points, revise points to line a little bit, as it is preload parameters need to be adjusted.  ID column , form string -> int or string, -> delete preloading for group col and serial col

@UrbanGISer can you please rebase the branch to the latest version of main. Thanks

@UrbanGISer please check if we can use this method instead

Replace the original code with the function of geopandas.GeoSeries.sample_points (with default method of "uniform")


remove hover bg color

the hover bg color can conflict with the text color. While adding the cursor pointer by default is a good idea, if the user of the component wants hover style then they should pass that in as part of the styles.

I'm not sure if I agree with this. Imho Button hover colors should stay the same across all applications. @fivenp any thoughts on this?

Hover should look good with the child color, child text should remain readable. If we want a fixed hover color, we also need fixed child color. How can we enforce that? In my opinion we shouldn't.

here @mosch : https://allthings.atlassian.net/secure/RapidBoard.jspa?rapidView=4&projectKey=APP&view=detail&selectedIssue=APP-650
CancelBookingButton
this is the pr: https://github.com/allthings/app/pull/1111

Closed in favor of https://github.com/allthings/elements/pull/34


Empty siteconfig property under Webapp directory

A user reported:
From Thom Schumacher
When viewing web applications in my subscription I the property for SiteConfig is empty. I would think that that would be the same value as:
Get-AzureRmWebAppSlot -name webapp -ResourceGroupName myres -slot ‘production’
In the provider my drivename is AZ.
cd az:\mysub\webapps
(gci *webapp).siteconfig
(gci *webapp).sitename — this is valid and has data
CLoudShell Version
PS Azure:\> dir env:acc_version
ACC_VERSION                    master_20171006.3
Modules
4.4.0      AzureRM
3.4.0      AzureRM.Profile

@Thom,  the WebApp directory under Azure drive is calling Get-AzureRmWebApp. I also can repro it with the following commands. Thanks for reporting it. I opened a github issue to track it.
#SiteConfig is empty
Get-AzureRmWebApp | % {$_.SiteConfig}

# worked properly
Get-AzureRmWebApp -name JianyunBot| % {$_.SiteConfig}

According to @ahmedelnably and @markcowl, populating SiteConfig is a separate call, which can be seriously expensive and perf hit. For that consideration, Siteconfig is empty object for now. However Azure cmdlet team is willing to consider to allow user opt in to perf hit case such as -Config. See  https://github.com/Azure/azure-powershell/issues/4841

Thank you for your response and for putting the issue I put on the blog site about this... Look forward to what comes next.
thom


tweaked summary of the GPL

see https://twitter.com/mikl/status/494123034836746241

Hm, I certainly appreciate the goals of #51 and the thinking that lead to this pull request, though I really don't like this wording.  "Legally enforcing" is kind of meta, all licenses should be legally enforceable, and enforcing something legally is not necessarily the part people want out of copyleft, that's a vector towards achieving this result. The phrasing "I want to require that others share improvements" is better I believe.

Thanks for the suggestion. Since this discussion hasn't been active for a while, and there was a lot of discussion around this in #51, I'm going to close this for now. We're happy to continue the conversation though.


Pod on one node can not ping VM on other node

On OpenShift.
Launching a pod on on node, then trying to ping running a VM on another node fails.

pod tp pod on another node works
pod to vm on same node works

@karmab is the bug description correct?

correct

note that the vm do have their ips received, as any pod running on the same host are able to reach them

for instance,
given those nodes
NAME                                  STATUS    ROLES     AGE       VERSION
ospha1.cloud.lab.xxx   Ready     master    6d        v1.9.1+a0ce1bc657
ospha2.cloud.lab.xxx   Ready     <none>    6d        v1.9.1+a0ce1bc657
ospha3.cloud.lab.xxx   Ready     <none>    6d        v1.9.1+a0ce1bc657

+------+---------+-------------+------------------------------------------+-------+------------------------------------------+--------+
| Name |  Status |     Ips     |                  Source                  |  Plan |                 Profile                  | Report |
+------+---------+-------------+------------------------------------------+-------+------------------------------------------+--------+
| vm1  | Running | <IP_ADDRESS> | kubevirt/fedora-cloud-registry-disk-demo | kvirt | kubevirt/fedora-cloud-registry-disk-demo |  N/A   |
+------+---------+-------------+------------------------------------------+-------+------------------------------------------+--------+

this vm has this details
name: vm1
creationdate: 2018-03-19T14:51:50Z
host: ospha2.cloud.lab.xxx
status: Running
template: kubevirt/fedora-cloud-registry-disk-demo
plan: kvirt
profile: kubevirt/fedora-cloud-registry-disk-demo
cpus: 1
memory: 1024M
ip: <IP_ADDRESS>
diskname: disk0 disksize: 0GB diskformat: N/A type: registrydisk path: vm1-vol0
diskname: cloudinitdisk disksize: 0GB diskformat: N/A type: cloudinit path: cloudinitvolume

@karmab could you do route in a vm pod and in an ordinary pod so that we can see if the routes are not correct anymore after the interface is created for the vm?


Bootstrap theme: missing scrollbar on IE8

On IE8, when the select dropdown is taller than the max-width, there is no scrollbar. This is due to a missing overflow-y style. In IE8, without the style, it acts as if overflow-y: hidden. Adding the following CSS fixes this problem.
.ui-select-bootstrap > .ui-select-choices {
    overflow-y: auto;
}

I also tested that latest Chrome and Firefox are not affected (they still show the scrollbar only when content is too tall).

@gillius Can you check if this is still a valid issue on the latest version of the ui-select. If so can you provide a plunker and a PR for it?
Thanks

Fortunately, we left IE8 behind in the dust a long time ago, so I don't even have access to a machine with IE8 anymore, only Edge and IE11. So, the issue may still exist but I don't care about it being resolved nor can provide feedback on it anymore, so close it if you wish.

Thanks indeed ie 8 is very old but just double checking.


npm publish

Hi,
Why are you not publishing on npm?
Greetings

I must say even more, if he will not do that. I will make it and give him
the rights.
Because last change with static port 8083 broke my connection and to avoid
it at least npm release would be nice.
Very cool project, but static port should be removed.
Greetings,
Bluefox
7 Июл 2016 г. 15:42 пользователь "Daniel Becker"<EMAIL_ADDRESS>написал:

Hi,
Why are you not publishing on npm?
Greetings
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jishi/node-sonos-discovery/issues/87, or mute the
thread
https://github.com/notifications/unsubscribe/AEXqgL5Z9r483S06qBo54NBpjD9es0T0ks5qTQJJgaJpZM4JHFwf
.

Ok I mean port 8080.
7 Июл 2016 г. 18:27 пользователь "Bluefox Fox"<EMAIL_ADDRESS>написал:

I must say even more, if he will not do that. I will make it and give him
the rights.
Because last change with static port 8083 broke my connection and to avoid
it at least npm release would be nice.
Very cool project, but static port should be removed.
Greetings,
Bluefox
7 Июл 2016 г. 15:42 пользователь "Daniel Becker"<EMAIL_ADDRESS>написал:

Hi,
Why are you not publishing on npm?
Greetings
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jishi/node-sonos-discovery/issues/87, or mute the
thread
https://github.com/notifications/unsubscribe/AEXqgL5Z9r483S06qBo54NBpjD9es0T0ks5qTQJJgaJpZM4JHFwf
.

What static port? The current version trys to find an unused Port on the System for the Event-Callbacks, and on Sonos-Systems, its always :1400

The static port relates to the web-controller, not discovery.
The reason for not publishing on npm has been that I can not guarantee support nor updates to it, and I personally find it highly annoying when people publish crap on public repositories that gets abandoned within months :) I didn't want to be equally bad.
I however have considered publishing the new version, but only the discovery library (I don't think npm is the place for actual applications), if I can iron out all quirks and also be more strict in my versioning and keeping backward compatibility.


Fix Barbarian Fishing Requirements and Rates

Description:

Previously, leaping sturgeons had a 48 agility requirement. This has been fixed to 45.
Previously, the minion always obtained a leaping trout even though there is supposed to be a chance for a failed roll. This roll for a failed catch has been added. Exp rates are now normalized thanks to this addition.

Changes:

Add a chance to NOT catch a fish during barbarian fishing.

Changed the message received when starting a barbarian fishing run to reflect that a player now attempts a certain amount of fish.

Changed the message received when minion finishes a barb fishing run to reflect that a player failed a fish an amount of failed/attempts.

[X] I have tested all my changes thoroughly.

Test


Fix broken link

warning: Absolute link should be made relative
   ┌─ architecture.md:12:24
   │
12 │ which is important for [relative pointers](/relative-pointers.html).
   │                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Absolute link should be made relative
   │
   = When viewing a document directly from the file system and click on an
     absolute link (e.g. `/index.md`), the browser will try to navigate to
     `/index.md` on the current file system (i.e. the `index.md` file inside
     `/` or `C:\`) instead of the `index.md` file at book's base directory as
     intended.

     This warning helps avoid the situation where everything will seem to work
     fine when viewed using a web server (e.g. GitHub Pages or `mdbook serve`),
     but users viewing the book from the file system may encounter broken links.

     To ignore this warning, you can edit `book.toml` and set the warning policy to
     "ignore".

         [output.linkcheck]
         warning-policy = "ignore"

     For more details, see https://github.com/Michael-F-Bryan/mdbook-linkcheck/issues/33
   = Suggestion: change the link to "relative-pointers.html"

mdbook-linkcheck shows that, I clicked on that link and it was broken while I was reading the book.

Thank you!


Document Creating Virtual Chassis

Issue type
[ ] Feature request
[ ] Bug report
[x] Documentation

Environment

Python version:  3.5.2
NetBox version:  2.3

Update Documentation on How to Create a virtual chassis
Forking and working on making the update to match what was posted in Slack channel.

Going to hold off on this as I'm hoping to overhaul the docs pretty soon.


Include test

I meant to only try fixing downloads include, but turns out that your fork is quite a bit behind. I suppose it is not a problem.


Test installing OVS on Fedora 23

Need to test installing OVS on Fedora 23 (only Fedora 25). The results of this testing will be used to augment Recipe 1.5.

As of late February 2017, both Fedora 23 and 24 included Open vSwitch 2.5.0 in their default repositories, and the process for installing OVS was the same on Fedora 23/24/25 (simply use dnf install openvswitch). I need to update the Fedora recipe accordingly.
This also affects #2.

Addressed via 58b2c6c.


Set Up PyMGRIT and PyTorch - Daniel

[x] Set up PyMGRIT and test by running quickstart example
[x] Set up PyTorch and test with their verification

1. Set up PyMGRIT and test by running quickstart example

2. Set up PyTorch and test with their verification
Displaying PyTorch version and creating some Tensors:

Using PyTorch with NVIDIA T400 GPU:


Fix sliced model loading for HF models

I merged Pavel's tests into this branch and ran them. They pass. Hence completing the PR now.


Why timeout happens to account when reporting?

http://imgur.com/a/z5YCJ
Only one reporting was completed today and all of the other reporting was failed because of the timeout error.

That happens to me as well but not that often.

I happen to me almost everytime...

Are you able to connect with any other SteamKit-based automation software like ArchiSteamFarm? The "Fail" error is new, I'll investigate.

Yes, I connected to Idle Master and HourBooster with those accounts before.

I have this problem too, i cant commend anyone. I tried it with my 2 accounts.


puzzlecode domain is dead

The domain puzzlecode.org in /developing-programs/pair-programming is no longer the right place.

[ ] set up an alternate hosting of https://github.com/mikegagnon/puzzlecode

Replaced PuzzleCode with Exercism, until we find a way to make PuzzleCode accessible again.
That's the whole idea of school-in-a-box. Integrate as much as we can, so we don't run into these problems in the future.

PuzzleCode has been integrated into WDX-180. Live link.
Updated README.
Next task, integrated the wiki


Kick

I can't kick another player if his name is empty. Is there any problem ? I use Heroku.
Thank you in advance.

This is a good question. If a player is unnamed, then they should be given a simple ID by the server for Admin's to recognize them by.

I finally found ! just use -kick !


dart fix will remove an unused optional parameter which is required by super class

a.dart
class EngineMapping {
  const EngineMapping({
    required this.flutterEngineRevision,
    required this.shorebirdStorageBucket,
  });

  final String flutterEngineRevision;

  final String shorebirdStorageBucket;
}

b.dart
import 'a.dart'

const config = ProxyConfig(
  engineMappings: {
    ...flutter_3_7_10,
    ...flutter_3_7_8,
  },
);

class _EngineMapping3_7 extends EngineMapping {
  const _EngineMapping3_7({
    required super.flutterEngineRevision,
    super.shorebirdStorageBucket = 'download.shorebird.dev',
  });
}

const flutter_3_7_10 = {
  'adb70a20d4718b5ce60cdd99ad81d8de54afcb35': _EngineMapping3_7(
    shorebirdStorageBucket: 'download-dev.shorebird.dev',
    flutterEngineRevision: 'ec975089acb540fc60752606a3d3ba809dd1528b',
  ),
};

If you comment out the line     shorebirdStorageBucket: 'download-dev.shorebird.dev', and run dart fix (which my editor does automatically on save), dart fix will decide that shorebirdStorageBucket is an optional parameter with a default value which is never set, and thus remove it.  But it can't!  Because it's actually a required super parameter. :(
The above is slightly reduced from:
https://github.com/shorebirdtech/shorebird/blob/34cfb4b6bc8a52efc3ea78d1d358611e76faa261/packages/artifact_proxy/lib/config.dart#L47
I was commenting out line 47 and then getting confusing errors:
Before you save the analyzer says:
[{
	"resource": "/Users/eseidel/Documents/GitHub/_shorebird/shorebird/packages/artifact_proxy/lib/config.dart",
	"owner": "_generated_diagnostic_collection_name_#2",
	"code": {
		"value": "unused_element",
		"target": {
			"$mid": 1,
			"path": "/diagnostics/unused_element",
			"scheme": "https",
			"authority": "dart.dev"
		}
	},
	"severity": 2,
	"message": "A value for optional parameter 'shorebirdStorageBucket' isn't ever given.\nTry removing the unused parameter.",
	"source": "dart",
	"startLineNumber": 16,
	"startColumn": 11,
	"endLineNumber": 16,
	"endColumn": 33
}]

After you save (and dart fix runs) you get:
[{
	"resource": "/Users/eseidel/Documents/GitHub/_shorebird/shorebird/packages/artifact_proxy/lib/config.dart",
	"owner": "_generated_diagnostic_collection_name_#2",
	"code": {
		"value": "missing_required_argument",
		"target": {
			"$mid": 1,
			"path": "/diagnostics/missing_required_argument",
			"scheme": "https",
			"authority": "dart.dev"
		}
	},
	"severity": 8,
	"message": "The named parameter 'shorebirdStorageBucket' is required, but there's no corresponding argument.\nTry adding the required argument.",
	"source": "dart",
	"startLineNumber": 16,
	"startColumn": 8,
	"endLineNumber": 39,
	"endColumn": 10
}]

eseidel@Erics-MacBook-Pro shorebird % flutter --version
Flutter 3.7.10 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 4b12645012 (8 days ago) • 2023-04-03 17:46:48 -0700
Engine • revision ec975089ac
Tools • Dart 2.19.6 • DevTools 2.20.1

Here is a simpler reduction:
class PublicSuperclass {
  const PublicSuperclass({
    required this.a,
    required this.b,
  });

  // a is not required to show the bug, just here to make the example more
  // realistic.
  final String a;
  // b is required by the superclass, but optional in the subclass.
  final String b;
}

class _PrivateSubclass extends PublicSuperclass {
  const _PrivateSubclass({
    required super.a,
    // Even though this is an optional argument setting the default has a
    // side effect, just removing the line (as `dart fix` suggests) will cause
    // an error.
    super.b = 'b',
  });
}

const foo = _PrivateSubclass(
  // Comment out the following line and run `dart fix` to see the error.
  b: 'c',
  // This line has no effect, just here for realism.
  a: 'a',
);

https://dart-review.googlesource.com/c/sdk/+/364000


Shouldn't wagtail.contrib.settings.models.BaseSetting be called BaseSettings?

This is a fairly minor gripe, but I'm confused about why this class has a singular name, rather than a plural name, even though it represents the base model for a collection of settings. I know that it's convention to name database models in the singular (e.g. Page vs Pages), but a Page is a singular thing, while a BaseSetting represents all the settings for a singular Site.

This is the sort of naming problem that you can't really solve perfectly, and need to make a tradeoff between code clarity and logical correctness - for example, if we called the individual model 'settings' then you'd have the question of what to call an array of 'settings' objects. (I don't know if that particular situation is likely to ever come up, but I wouldn't want to count on us never running into similar problems.) Either way, changing the name at this point would involve going through a deprecation process, and I think the pain of that would outweigh any marginal benefits of making the change.


Make JSONHandler customization docs clearer

As pointed out by @Stargateur in https://github.com/falconry/falcon/issues/1906#issuecomment-817374057, our JSONHandler customization docs could be made clearer by separately illustrating different (albeit closely related) concepts:

Use a custom JSON library (such as the exemplified rapidjson). Customize parameters.
Use the stdlib's json module, just provide custom serialization or deserialization parameters. Also link to the "Prettifying JSON Responses" recipe, which illustrates customization of dumps parameters.
Add a sentence or two about replacing the default JSON handlers, not just toss in a code snippet as it is at the time of writing this. Also link to Replacing the Default Handlers from that explanation.

Hi, I can start working on this

Awesome, go ahead @dflss ! I'll remove the needs contributor label.


pushing new branch to remote

Hi team, I have introduced a new case study, I have validated locally and everything seems to be working fine (locally). However, when I am trying to push the new branch to the remote I reveive an authentication error fatal: Authentication failed for 'https://github.com/developmentseed/aep.git/'. I assume this is a security issue that can be resolved via an access token or by simply being added as collaborator? Or is this something I should configure on my machine. Thanks!

Hi @akorkovelos.
Great to hear that everything is working locally. Just added you as a contributor to this repo with write access. You should be able to push a new branch.
Feel free to reopen this issue if the problem persists.


Update ExecutorConfig when it is changed so that Executor and Cassand…

…ra binaries can be updated.
This fixes https://dcosjira.atlassian.net/browse/CASSANDRA-29

LGTM! Will merge once the tests pass.


Improved error handling for the recipe resolver in recipe2plan

Hmmm... what's exactly the benefit? The name of the component which failed is in the Error? Is there more?

Hmmm... what's exactly the benefit? The name of the component which failed is in the Error? Is there more?

Besides adding an error class, I add an additional case to throw an error here. This way, it will inform you which handle is problematic instead of the obtuse TypeError: Cannot read property 'hash' of null.


ATT Speedtest Server no longer working

I noticed my speedtest results started to be very erratic around 10/25/24.  I run a test every hour, and I had not specified a specific server ID to use for my tests, but it seemed to always default to ATT, Server ID 47749, my ISP is ATT.    Every test before 10/25/24, was hitting that ATT server ID.    After that, it was just hitting any of the random servers in my area.   Did something happen to the ATT Server ID 47749?   I tried to force it in my container with the - SPEEDTEST_SERVERS= 47749 setting, but every test using it fails.  When I go to https://c.speedtest.net/speedtest-servers-static.php I do not see the ATT server as an option.    Running a direct test from my ATT Modem, I get basically line speeds as expected.   Is there a way I can figure out what server is needed for ATT or what happened to it?
I'm using Docker, with the latest release of speedtest-tracker.

HI @andrewjmoser,
It seems that server id 47749 no longer exists as it returns an error when testen on it, and like you said it does not show up on the speedtest.net website anymore. The only one how can tell you what happend to the server is AT&T themself 😅 .
speedtest -s 47749
[error] Configuration - No servers defined (NoServersException)

If you want to specify a server in your config make sure there is no space between the = and the server id 😉 .


Add PowerShell to default scripts.

Adds PowerShell to the default extensions and scopes lists.

Hi @lsegal the PR is ready, including PowerShell scripts.
I added a condition in returning extension, as we don't want to return the file extension command if a selection is made (we don't want to pass the whole file).
Have a look, let me know what you think. Thanks :)

Looks good!

Thanks mate. :)
Are you able to do a build so the package is available in the package repo?
cheers :)


Don't fail if one sample fails

As is, if there's one problematic sample (as defined in by_col), the whole thing returns an error.
Add a try_catch() statement in process_optim(), along with an output message and an entry in the class object.
Perhaps add a condition that the whole thing fails if the first 10% all fail.

Do this after #42.


Add info about /debug endpoint

Proposed changes
Google has very strict API requirements that can sometimes be hard to adhere to. This change highlights the /debug endpoint which can be really helpful in better understand what may be wrong with a payload by Google's standards.
Merge timing
ASAP is fine

Thanks for the improvements @forstisabella ! 🙌 I'll keep that in mind for future updates!


Support for postgres database with password and docker secrets

Hi, I'm currently planning a setup of kong and konga in a docker swarm environment and I got pretty far for now.
The related part of my compose file:
  # kong:
  kong-migrations:
    image: "kong:1.0.0"
    command: kong migrations bootstrap
    depends_on:
      - postgres
    environment:
      KONG_DATABASE: postgres
      KONG_PG_DATABASE: kong
      KONG_PG_HOST: postgres
      KONG_PG_USER: kong
    configs:
      - source: kong_entrypoint_overwrite
        target: /kong_entrypoint_overwrite.sh
        mode: 0770
    secrets:
      - postgres_user_passwd
    entrypoint:
      /kong_entrypoint_overwrite.sh
    deploy:
      restart_policy:
        condition: on-failure

  kong:
    image: "kong:1.0.0"
    depends_on:
      - postgres
      - kong-migrations
    environment:
      KONG_ADMIN_ACCESS_LOG: /dev/stdout
      KONG_ADMIN_ERROR_LOG: /dev/stderr
      KONG_ADMIN_LISTEN: '<IP_ADDRESS>:8001'
      KONG_CASSANDRA_CONTACT_POINTS: postgres
      KONG_DATABASE: postgres
      KONG_PG_DATABASE: kong
      KONG_PG_HOST: postgres
      KONG_PG_USER: kong
      KONG_PROXY_ACCESS_LOG: /dev/stdout
      KONG_PROXY_ERROR_LOG: /dev/stderr
    ports:
      - "9005:8000/tcp"
      - "9006:8001/tcp"
      - "9007:8443/tcp"
      - "9008:8444/tcp"
    configs:
      - source: kong_entrypoint_overwrite
        target: /kong_entrypoint_overwrite.sh
        mode: 0770
    secrets:
      - postgres_user_passwd
    entrypoint:
      /kong_entrypoint_overwrite.sh
    command:
      - kong
      - docker-start

  konga-prepare:
    image: pantsel/konga:next
    depends_on:
      - postgres
    # This is ugly and I really would like to get rid of having the password in plain text in the command
    command: "-c prepare -a postgres -u postgresql://konga:<secret_password>@postgres:5432/konga"
    deploy:
      restart_policy:
        condition: on-failure
    secrets:
      - postgres_user_passwd

  konga:
    image: pantsel/konga:next
    depends_on:
      - kong
    ports:
      - 9009:1337
    environment:
      - DB_ADAPTER=postgres
      - DB_HOST=postgres
      - DB_DATABASE=konga
      - DB_USER=konga
      - NODE_ENV=production
    configs:
    - source: konga_entrypoint_overwrite
      target: /konga_entrypoint_overwrite.sh
      mode: 0770
    secrets:
      - postgres_user_passwd
      - konga_jwt_token
    entrypoint:
      /konga_entrypoint_overwrite.sh

Currently I had to overwrite the entry point scripts of kong and konga to use docker secrets.
The scripts are pretty simple and follows the schema:
export KONG_PG_PASSWORD=$(cat /run/secrets/postgres_user_passwd)
source /docker-entrypoint.sh "$@"

But I would really like to have support for something like:
environment:
      POSTGRES_PASSWORD_FILE: /run/secrets/postgres_passwd

As supported in the postgres docker image. This would remove a lot of clutter from my compose file and I hope will benefit others that are trying to make their docker world a little bit safer.
I'm pretty new to docker, but if you like I could try to create a PR for this feature.

@pantsel

@nylocx , PRs are always welcome!

Well, some useful PRs have arrived and remaining unmerged for long time, e.g. https://github.com/pantsel/konga/pull/586#issuecomment-654431890


JAVA example build but only update the example.class or turn off generating javadocs

I have built the java example and it works. Now I want to implement my own stuff in the Example.java. I don't want to build the whole thing again via "cmake --build . --target install" after every little change I make in the Example.java. What is another option? What can I do to just update my changes from the Example.java for the build files and run it then?
Also, every time i build the example, a lot of doc files (.html) are generated. Can I turn it off?

No. You can compile Example.java in any way you want. For example, like this:
javac -d bin org/drinkless/tdlib/example/Example.java

Thanks!


document manual safekeeper replacement procedure

this needs to be updated in view of the SK IDs that we've introduced recently
once updated, someone needs to try out the procedure before we close this
@stepashka  can try on staging :)


In the FARMING TAB the "Your Node full conetion disappears"

After 1 hour or more it disappears. No connection appears here. I don't know what else to do help me please. I already formatted the pc and reinstalled windowns from scratch. DMZ, port fowarding .. And I only use 1 pc
1 week already and I can't solve this problem. The way they are, I'm not mining right? I will not be able to receive anything the way it is right ??

HERE THE debug.log:
2021-05-17T10:19:40.701 full_node chia.full_node.full_node: ERROR Respond peers exception: 'NoneType' object has no attribute 'host'. Traceback: Traceback (most recent call last):
File "chia\server\node_discovery.py", line 509, in respond_peers
File "chia\server\node_discovery.py", line 474, in add_peers_neighbour
AttributeError: 'NoneType' object has no attribute 'host'
and:
2021-05-17T10:19:40.764 full_node full_node_server : ERROR Exception: <class 'concurrent.futures._base.CancelledError'>, closing connection None. Traceback (most recent call last):
File "chia\server\server.py", line 531, in api_call
File "asyncio\tasks.py", line 435, in wait_for
concurrent.futures._base.CancelledError
2021-05-17T13:04:53.250 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id 9a46f929e8dea94d94bf674695b8f305c692833bd2ba7e7c35a8f4d15055b120, status 3 error: Err.UNKNOWN_UNSPENT
2021-05-17T13:12:57.176 full_node chia.full_node.full_node: ERROR Consensus error 124, not disconnecting
2021-05-17T13:16:17.103 full_node chia.full_node.full_node: WARNING Wasn't able to add transaction with id 6bb7e579b964997ce502afe309c18f745cc0a6023f0c3cad4b79f343022992f5, status 3 error: Err.DOUBLE_SPEND

Did you find any solution @hugofaria8 ? I have same problem.

No solutions... you?


Update Russian translation

Description

Updates old translations
Translates new files

Hello! Thank you for opening your first PR to Starlight! ✨
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any issues you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Vercel 🤩

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.

Thank you for the huge work! I also appreciate you correcting my grammatical errors and typo! I've left a few comment questions, but overall, I would approve this PR. ✨


Does FlashInfer support variable-length inputs?

Does FlashInfer currently have a result for variable-length inputs, similar to the varlen_fwd interface in Flash Attention, which supports different sequence lengths for each batch?

Hi, of course, variable length are described as RaggedTensor data structures:
https://docs.flashinfer.ai/tutorials/kv_layout.html#ragged-tensor
and the corresponding API:
https://docs.flashinfer.ai/api/python/prefill.html#flashinfer.prefill.BatchPrefillWithRaggedKVCacheWrapper


Vectors

Hi Andy,
I'm using 6502bench to disassemble a rom for an educational 6502/816 sbc.  Maybe I'm not seeing it but how does one label vectors like for example RESET, IRQBRK or NMI?
Thanks!
Andy

I'm not sure what you mean.  Are you adding labels to the CPU vectors at $FFFA-FFFF?  If so, does your ROM image include that area?
If it's part of the image, you just add a label to that location (double-click in label column).  Format it as a 16-bit numeric address.  This will place an auto-label at the vector target address, but doesn't automatically hint the target as code (there's a "TO DO" list item for that).  You can however double-click on the .dd2 to jump to the target address and add a hint manually (Ctrl+H Ctrl+C).
If that memory range is not part of the image, you can add a project symbol for that address (currently Edit > Project Properties > Project Symbols, then "New Symbol").  If this is something that's common to multiple projects then it would make sense to create a .sym65 file for common use.
If none of the above is what you're after, tell me more about what you're trying to do.

Hi Andy,
The ROM image would burn into a 32k rom that resides in $8000-$ffff.  I was using it last night.  It didn't appear that I could change the data statements from .dd1 to .dd2.  I have a *.dis65 file created if you'd like to see.  It's a rom image that would be burned into a 28c256 for example.
  From: Andy McFadden<EMAIL_ADDRESS>
To: fadden/6502bench<EMAIL_ADDRESS>Cc: handyandy802<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Sent: Wednesday, November 7, 2018 6:36 PM
Subject: Re: [fadden/6502bench] Vectors (#41)
I'm not sure what you mean. Are you adding labels to the CPU vectors at $FFFA-FFFF? If so, does your ROM image include that area?If it's part of the image, you just add a label to that location (double-click in label column). Format it as a 16-bit numeric address. This will place an auto-label at the vector target address, but doesn't automatically hint the target as code (there's a "TO DO" list item for that). You can however double-click on the .dd2 to jump to the target address and add a hint manually (Ctrl+H Ctrl+C).If that memory range is not part of the image, you can add a project symbol for that address (currently Edit > Project Properties > Project Symbols, then "New Symbol"). If this is something that's common to multiple projects then it would make sense to create a .sym65 file for common use.If none of the above is what you're after, tell me more about what you're trying to do.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Try this: select address $FFFA, then shift-click address $FFFF.  Right click, select Edit Operand.  At the top of the Edit Data Format dialog it should say, "Select data format (6 bytes selected)".  Click "16-bit words, little-endian", then over to the right click "Address", then OK.  You should see FFFA/FFFC/FFFE formatted as .dd2 (probably with auto-generated labels).
The data operand edit feature always operates on what's currently selected.  There's an open issue (#29) for adding a "format as word" feature, tied to Ctrl+W, that would convert the next couple of bytes to a word even if only one byte is currently selected.  (It would just be a 16-bit data item though, not a numeric reference to an address, so wouldn't simplify this operation.)
I'm wondering if I should add hover-over tooltips to disabled items on that dialog that say "this isn't available because you don't have enough items selected".


Cant pan inside scroll view

When I put color picker into a scroll view and try to pan the scroll is triggered.

Fixed by https://github.com/itome/flutter_circle_color_picker/pull/20


es-300-fbo-shadow issue

Hi,
when I run it I get a black screen and in the console

OpenGL: undefined behavior(medium) 131222: Program undefined behavior warning: Sampler object 0 has depth compare enabled. It is being used with depth texture 3, by a program that samples it with a regular sampler. This is undefined beahvior.

Found the issue


Implement Handler for Box and Arc

There are definitely some situations where you may want to package your handlers in a Box or Arc, instead of creating your own wrapper type. We should, therefore, spare the users the effort implement Handler for those types.
Bonus quest: Investigate if some variant of impl<T> Handler for T where T: Deref, T::Target: Handler is a viable alternative or if it would conflict too much.

@Ogeon can you take a look at the pull request. Is this in line with what you were planning? If this looks Ok I'll commit for Box<T> as well. I'm working on a generic way to do this like you suggested. But current implementation is conflicting.
I've a questions. Can you suggest a good example where Arc<T> handler feels like an obvious choice? In my example the usage seems forced.

Your implementation for Arc<T> looks good. I also realized that a more generic implementation would conflict with the implementation for Fn, so it won't work, but that's ok. It was just a thought I had.
Your example is close enough, with the difference that it would have to depend on the path to be more "obvious":
fn my_handler(context: Context, response: Response) {
    if let Some(var) = context.variables.get("var") {
        //do stuff with var
    } else {
        //do something else
    }
}

//...

let handler = Arc::new(my_handler);
insert_routes! {
    router => {
        Get: handler.clone(),
        ":var" => Get: handler
    }
}

This example is essentially the hello_world example, but with Arc instead of just a copy of the function pointer. A more "real" usecase would be if the handler had some non-copy data that had to be available at both / and /:var. This would require either the data or the handler itself to be wrapped in an Arc. It's hard to make examples that doesn't feel forced.

I'm not 100% sure if an example for this is really necessary for this. It's quire basic, but on the other hand, why not?

Thanks for feedback @Ogeon. Still getting hang of Rust and quite liking it so far.
As you said, the example that I've added doesn't add anything to what we already have. It was more of a proof of concept for me to see if everything is working fine. We don't have an example that uses all the http verbs. So I was thinking I can add an example that holds a resource. Get, Post and Delete methods get, update and remove resource respectively. I'm new to Rust and as far as I can understand I need a mutable reference of handler to do it. But I don't know how to do it in current setup. Can you help me with that.

I see :smile: It's nice of you to consider adding new examples. Some of the current examples can be extended to show more aspects of the library and it may even be a good idea to replace some of them. The todo example covers multiple http verbs in general, and it's also an example of how mutable state can be implemented (together with handler_storage), so that may already be covered. This is, however, a bit of a side topic and this is not really the right place. We can continue the discussion in a separate issue or pull request if you would like to go through and improve the examples.

Cool thanks. I removed example and updated PR. This should take care or Arced handlers.
Now I need help with Boxed handlers. Implementing it the same way as Arc results in compiler error:
src/handler.rs:14:1: 18:2 error: conflicting implementations for trait `handler::Handler` [E0119]
src/handler.rs:14 impl<F: Fn(Context, Response) + Send + Sync + 'static> Handler for F {
src/handler.rs:15     fn handle_request(&self, context: Context, response: Response) {
src/handler.rs:16         self(context, response);
src/handler.rs:17     }
src/handler.rs:18 }
src/handler.rs:14:1: 18:2 help: run `rustc --explain E0119` to see a detailed explanation
src/handler.rs:27:1: 31:2 note: note conflicting implementation here
src/handler.rs:27 impl<T: Handler> Handler for Box<T> {
src/handler.rs:28     fn handle_request(&self, context: Context, response: Response) {
src/handler.rs:29         (**self).handle_request(context, response);
src/handler.rs:30     }
src/handler.rs:31 }
error: aborting due to previous error
Could not compile `rustful`.

Appreciate your help on this.

That's really strange... Oh, wait, Box<FnOnce> implements FnOnce and so does anything that implements Fn, meaning that T: Fn may be a Box... It should at least be possible to implement Handler for Box<Handler>, I think, since Handler doesn't require Fn. That's the main usecase for boxed handlers, anyway.


Documentation Cleanup

The bulk of the documentation is okay.   This thread will enumerate

gaps
simplifications to be made
clarifications
reorganization

Initial todo:

[x] version releases.  git tags engaging publish to pypi
[ ] environment setup / dependencies.  including Windows, Mac, Linux caveats
[ ] connections to organelle-segmenter-plugin
[ ] ??

[ ] Add instructions to information section within each organelle-segmenter-plugin workflow
[ ] Ensure all functions are properly annotated for published documentation site.


sigdump support for Windows

Is your feature request related to a problem? Please describe.
https://github.com/fluent/fluentd/pull/3131#issuecomment-1007690885
There is no way to trigger Sigdump.dump on Windows.
Describe the solution you'd like
Add a new win32 event for it like #3131.
Describe alternatives you've considered
none.
Additional context
No response

@fujimotos and I have released fluent-plugin-sigdump.
https://github.com/fluent-plugins-nursery/fluent-plugin-sigdump
This is one way to get sigdump in Windows.
In addition, I will try to improve fluent-ctl.


Investigate methods for running the emulator for tests

Issue
As of now, our test suite requires that the user sets up and runs the emulator in a separate terminal. Ideally, we would have some command or some other method to automatically do that for the user so that they do not have to configure and run the emulator for themselves.
Possible methods (list in progress):

AntRun Plugin

Next Steps

[ ] Investigate methods
[ ] Implement a strategy to lower user effort for running tests

Consider looking into github workflows. Example: https://github.com/googleapis/java-spanner/pull/310/

https://github.com/GoogleCloudPlatform/cloud-spanner-samples/tree/it branch has a fully working solution (with gradle).

Added github action for continuous integration with emulator on https://github.com/GoogleCloudPlatform/cloud-spanner-samples/pull/61


Use critical_section for Peripherals::take.

cortex_m https://github.com/rust-embedded/cortex-m/pull/447
msp430 https://github.com/rust-embedded/msp430/issues/13
riscv https://github.com/rust-embedded/riscv/pull/110
xtensa_lx https://github.com/esp-rs/xtensa-lx/issues/20, https://github.com/esp-rs/esp-hal/pull/151
mips_mcu https://github.com/kiffie/pic32-rs/issues/5

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @therealprof (or someone else) soon.
Please see the contribution instructions for more information.

I'm a bit concerned about what this means for platforms that don't have critical-section support yet. I know msp430 is working on it but having some codegen size issues, and I don't know anything about mips_mcu. It might be worth waiting a little longer for those architectures to get support before releasing svd2rust that uses it?
Having it as an optional dependency/feature seems useful though and does mean those platforms don't need immediate critical-section support, even end-users could add simple interrupt-based implementations to use take() if needed.

It might be worth waiting a little longer

I don't think it's worth waiting. Other architectures will have to implement these only once they upgrade svd2rust anyways. I have opened issues for the affected architectures to give them a heads up though.

Oh, thanks, I didn't see the edit to the first comment. SGTM to me then.


surface: handle hyperlinks more reliably

We refresh the link hover state in two (generic) cases

When the modifiers change
When the cursor changes position

Each of these have additional state qualifiers. Modify the qualifiers
such that we refresh links under the following scenarios:

Modifiers change

Control is pressed (this is handled in the renderer)
Mouse reporting is off
OR
Mouse reporting is on AND shift is pressed AND we are NOT reporting
shift to the terminal

Cursor changes position

Control is pressed (this is handled in the renderer)
We previously were over a link
The position changed (or we had no previous position)
Mouse reporting is off
OR
Mouse reporting is on AND shift is pressed AND we are NOT reporting
shift to the terminal

This fixes a few issues with the previous implementation:

If mouse reporting was on and you were over a link, pressing ctrl
would enable link hover state. If you moved your mouse, you would
exit that state. The logic in the keyCallback and the
cursorPosCallback was not the same. Now, they both check for the same
set of conditions
If mouse reporting was off, you could hold control and move the mouse
to discover links. If mouse reporting was on, holding control + shift
would not allow you to discover links. You had to be hovering one
when you pressed the modifiers. Previously, we only refreshed links
if we weren't reporting the mouse event. Now, we refresh links even
even if we report a mouse event (ie a mouse motion event with the
shift modifier pressed will hover links and also report events)

Old Behavior
Notice that the state of the hyperlink is erratic in comlink. When I am over it and press ctrl the link is underlined and the url hint in the lower left shown for one frame, but then the state is dropped.
https://github.com/user-attachments/assets/52d6a8c8-8459-4d67-85eb-5d91f9833771
New Behavior
State is retained when holding ctrl+shift. And the link only underlines if I press both ctrl+shift. If I move the mouse around while holding these keys, I can discover new links.
https://github.com/user-attachments/assets/78fa8e97-eb0c-4618-bd96-fe40d6bc67ce

cc @tristan957

Thanks for finding the proper fix. Next release is gonna be great!

It's hard to make sense of this logic since it's so poorly tested (something I'm working on). A brief glance this looks okay, and I think it should only affect links if there are bugs in this logic anyways, and links are already a bit buggy. So overall I'm just going to merge this and try to refactor in tests later. Thank you!

I completely agree. I tried to document when we do this the best I could, but there are lot of moving pieces, as well as opinions. This currently works how I intuitively would think it should, but even then I had some reservations on which behavior is preferred. Ping me once you are ready with your refactor and I can put in some concrete tests to get the behavior exact (and make it easier to discuss the ideal behavior).


Train for multiple data fragments

Hi, I am confused about how to train when there are multi time-series clips/slices for the only one object(such as one company stock).
And I don't know whether they are continuous in time (probably not continuous).
It seems need to consider the dataset clips as the batch inputs?
Here is an example, the dataset have 10 sequences with different lengths. But they do both are from one object recording(not different object)

Best Regards,
Zahir Wang

Do you mean sliding each sequence into segments of the shape (num_i, seq_length, 1) and then combining them into (num, seq_length, 1)? I do think it’s feasible.

Like this, I have the seq(1-n) and i only know these seqs are from one original seq.

Thank you for your detailed and vivid illustration. Identifying where each sequence breaks is indeed a tricky issue, and it’s clearly beyond the scope of this repo. If the discontinuities can be tolerated or ignored, I think it’s OK to proceed directly with the approach mentioned above.


No module named 'contextvars'

Netflix add-on version
1.18.7
Operative systems used
Linux (Ubuntu / Mint / ...)
Kodi version used
Kodi 19 (Matrix)
Description of the bug
Netflix plugin doesn't start. Error message says that module "contextvars" is missing.
Log says the same:
...
                                                     File "/home/murple/.kodi/addons/plugin.video.netflix/packages/sniffio/_impl.py", line 1, in <module>
                                                       from contextvars import ContextVar
                                                   ModuleNotFoundError: No module named 'contextvars'

pip3 says that contextvars is installed:
murple@nuc:~$ pip3 list|grep context
contextvars             2.4

I can also import the module on commandline
murple@nuc:~$ python3
Python 3.8.10 (default, Mar 15 2022, 12:22:08)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import contextvars
>>>

Steps to reproduce the behavior
Start
Debug log - mandatory
https://paste.kodi.tv/muzudiqode.kodi
Possible fix
No response
Additional context
No response
Screenshots
No response

this is not a bug
but misconfiguration in your python packages
there are many issues on this topic please search in the old closed issues or asking in forum


Catch errors from missing api-keys in .env file

Acceptance Criteria
As directly defined by Eloi:

[ ] Errors from missing api-keys in .env file are caught and comprehensible instructions for the user on how to add them is printed to the console.

Discovered that Preet already did this at the beginning of this sprint.


On Mac, binding anything to ctrl-/ produces a "whump" sound

I noticed it first in atomic-emacs triggering core:undo, but after some small experiments, it looks like the problem is in Atom.

Thanks for the report. I'm pretty sure this is another instance of this issue: https://github.com/atom/electron/issues/2617 which is tracked in Atom here https://github.com/atom/atom/issues/1669 (for the ctrl-cmd-down combo). Can you add a comment to those issues so that we keep things in one place?
I just tried ctrl-/ in Chrome, and it produces a sound as well.


reading relationships from Postgresql database

Hello,
I wanted to create .er file based on schema in Postgresql database.
It works well for tables, but ignores relationships.
Example script
psql t1 -c "CREATE SCHEMA t1;
            CREATE TABLE  t1.parent(id INTEGER PRIMARY KEY);
            CREATE TABLE  t1.child (id INTEGER PRIMARY KEY,
                                   parent_id INTEGER REFERENCES t1.parent(id) NOT NULL)"
eralchemy -i 'postgresql+psycopg2:///t1' -s t1 -o t1.er
cat t1.er

yields output
[t1.parent]
    *id {label:"INTEGER"}
[t1.child]
    *id {label:"INTEGER"}
    parent_id {label:"INTEGER"}

ignoring FOREIGN KEY constraint. Is it intended?
I'm using PostgreSQL 9.6.10 on Ubuntu 18.04 and ERAlchemy version 1.2.10.

Same problem for me. It ignores relations between tables when my input is an existing postgres instance.

Same problem here!

I have this issue as well.

As the changes from my fork are now merged here, and I could not reproduce this issue, I'll close it now.


Taskqueue service stats

Track taskqueue service statistics.
Separately track protobuffer and rest api statistics.

@jeanleonov Would you mind rebasing? The diffs here include the common service stats pieces.

https://ocd.appscale.com:8080/job/Daily Build/4632/

https://ocd.appscale.com:8080/job/Daily Build/4655/

@cdonati thanks for the patient review.

https://ocd.appscale.com:8080/job/Daily Build/4669/


update website docs file

There are some mistakes which I am going to fix and merge from my repository.

I am updating here. after checking all, I will submit a merge request.


V3 multipart encoding property type  for content-type isn't supported

Given this spec:
openapi: "3.0.0"
info:
  title: Test
  version: "1.0"
paths:
  /convert:
    post:
      operationId: doWork
      description: Work work work.
      requestBody:
        required: true
        content:
          multipart/form-data:
            schema:
              properties:
                options:
                  description: The configuration data.
                  type: object
                  properties:
                    foo:
                      type: string
                      description: A foo.
                  required:
                    - foo
                message:
                  description: Big text file
                  type: string
                  format: binary
              required:
                - options
                - message
            encoding:
              message:
                contentType: text/plain
      responses:
        201:
          description: Request worked.

and given the documentation: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md#special-considerations-for-multipart-content
I would not expect any errors or lack of the contentType for message when reading the YAML. I do get a diagnostic error: "encoding is not a valid property at #/paths//convert/post/requestBody/content"

Diving into the code a bit, Microsoft.OpenApi.Readers\V3\OpenApiMediaTypeDeserializer.cs / _mediaTypeFixedFields has a comment like a todo for encodings, but its left unimplemented.

Well it looks like the rest of the plumbing is there; this is what is missing in the _mediaTypeFixedFields
{
    "encoding", (o, n) =>
    {
        o.Encoding = n.CreateMap(LoadEncoding);
    }
},

Based on the PR and the conversation above, I believe this is resolved. Please reopen if that's not the case.


[redis-ha] /readonly-config/init.sh fails as service names not in getent hosts

The init.sh script fails as it tries to look up the announce service but those DNS are not in the hosts table inside the pod..
Could not connect to Redis at test-redis-redis-ha:26379: Temporary failure in name resolution
Initializing config..
/readonly-config/init.sh: 85: /readonly-config/init.sh: Could not resolve the announce ip for this pod: not found

<IP_ADDRESS>       localhost
<IP_ADDRESS>       localhost ip6-localhost ip6-loopback
<IP_ADDRESS>      test-redis-redis-ha-server-0.test-redis-redis-ha.test-redis.svc.cluster.local test-redis-redis-ha-server-0

I'm having the same issue. I was curious if you were able to resolve this?

I took my fork of the helm template, commented out https://github.com/helm/charts/blob/master/stable/redis-ha/templates/_configs.tpl#L116-L124
and have another script to handle the master/secondary selection.
A version of https://github.com/smileisak/docker-images/blob/master/redis/alpine/redis-launcher.sh


Websocket client disconnects when related upstream is down

Description:
We run kubernetes websocket server pods.
Between clients and the services we want envoy proxy to take care of connections lifecycle.
More precisely, the idea is to "preserve" a websocket connection in such way that the connection is taken over by another healthy upstream (once original upstream is gone).
We are not in control of the clients.
So far, we tried different configuration options in order to reroute/fail over/keep alive/prevent disconnecting websocket connection, but we keep failing.
Once pod is Terminating/Terminated the downstream connection got broken too - the client gets disconnected.
Let me share what we tried to do:

First, we do gracefully close websocket connections on SIGTERM signal
With Lua script, we cannot intercept any request/response since the connection is upgraded from the start and the communication is binary from that point on
Health checks, circuit breaker and weighted clusters don't help mitigate this issue

We strongly believe this preservation of websocket connection is possible to manage with envoy.
Could you please give us a hand how best we can approach this problem.
Here is the currentenvoy.yaml example:
admin:
  access_log_path: /dev/stdout
  address:
    socket_address:
      address: <IP_ADDRESS>
      port_value: 14000
static_resources:
  listeners:
  - address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 7070
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: filter_wsprogram
          codec_type: auto
          upgrade_configs:
          - upgrade_type: websocket
          route_config:
            name: local_route
            virtual_hosts:
            - name: app
              domains:
              - "*"
              routes:
              - match:
                  prefix: "/"
                route:
                  idle_timeout: 0s
                  priority: HIGH
                  weighted_clusters:
                    clusters:
                      - name: wsprogram_cluster
                        weight: 90
                      - name: wsprogram_backup_cluster
                        weight: 10
                    total_weight: 100
          http_filters:
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
  clusters:
  - name: wsprogram_cluster
    type: STRICT_DNS
    lb_policy: ROUND_ROBIN
    dns_lookup_family: V4_ONLY
    #connect_timeout: 1s
    dns_refresh_rate: 0.01s
    load_assignment:
      cluster_name: wsprogram_cluster
      endpoints:
        - lb_endpoints:
            - endpoint:
                address:
                  socket_address:
                    address: wsprogram-headless-zero
                    port_value: 80
    circuit_breakers:
      thresholds:
        - priority: DEFAULT
          max_connections: 1000
          max_pending_requests: 1000
          max_requests: 10000
          max_retries: 3
          track_remaining: true

    health_checks:
      - timeout: 1s
        interval: 1s
        unhealthy_threshold: 1
        healthy_threshold: 2
        tcp_health_check:
          send:
            text: "00"
          receive:
            text: "00"
  - name: wsprogram_backup_cluster
    type: STRICT_DNS
    lb_policy: ROUND_ROBIN
    dns_lookup_family: V4_ONLY
    #connect_timeout: 1s
    dns_refresh_rate: 0.01s
    load_assignment:
      cluster_name: wsprogram_backup_cluster
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: wsprogram-headless-one
                port_value: 80
    circuit_breakers:
      thresholds:
        - priority: DEFAULT
          max_connections: 1000
          max_pending_requests: 1000
          max_requests: 10000
          max_retries: 3
          track_remaining: true

    health_checks:
    - timeout: 1s
      interval: 1s
      unhealthy_threshold: 1
      healthy_threshold: 2
      tcp_health_check:
        send:
          text: "00"
        receive:
          text: "00"

@kyessenov any ideas about this ?

Following as we have similar requirements and constraints.


Isthumus: Spec updates for L2 withdrawals-root in block header

Peeling off the work associated with updating specs mentioned in: https://github.com/ethereum-optimism/optimism/issues/12044
General notes: keep the specs categorized in the isthumus  directory, and file names consistent across upgrades:
e.g. Execution layer changes go exec-engine.md.

[x] Specs note that the block-body withdrawals list is encoded as an empty RLP list.
[x] Specs note that any block-after-transaction simulation should include an empty withdrawals-root;
the block is sealed at the end of a block.
[x] Specs note that the withdrawals-root in the genesis block,
if Isthumus is active, is always the empty withdrawals root, regardless of L2 state.
[x] Specs note that the withdrawals-root starting at shanghai, pre-Isthumus,
is set to an empty withdrawals list, this equals the same root as an empty storage root.
The withdrawals are there in L2 state, just not elevated into the withdrawals-root.
Pre-Isthumus output-root construction should be careful not to use the header withdrawals-root.
[x] Specs note that at the time of state-processing, with an in-progress header,
the withdrawals-root should not be available to the EVM / application layer.
[x] Specs Engine-API modification: ExecutableData gets a withdrawalsRoot attribute.
[x] Specs note that for an accurate storage-root to be known,
the block state has to be committed first, before the withdrawals storage root can be set accurately.
This attribute should thus be set right after setting the state-root attribute of the header.
[x] Specs EL P2P note: block-bodies and block-headerts responses are handled the same in isolation:
we compute the body-withdrawal-hashes from the received withdrawals list in the block body.
Then, when we compare the body-withdrawal-hashes to the header withdrawal-hashes,
and if optimism Isthumus is active for the given header, we check if the body-withdrawal-hash matches the empty list root,
while allowing the header-withdrawal-hash to be any non-null value.
By verifying at this later stage, we have the header timestamp, and can apply the fork logic conditionally.
[ ] Specs update to describe CL ExecutionPayload SSZ encoding with new withdrawals-root included.

[ ] We remove the withdrawals list from the encoding, diverging from the L1 beacon-chain ExecutionPayload encoding.

[x] Spec that we continue to use engine_newPayloadV3 engine-API,
but now with the additional ExecutionPayload attribute, that is omitted pre-Isthumus.
[ ] Specs update to describe new CL P2P gossip topic, with updated ExecutionPayload SSZ encoding,
and a gossip-validation rule that checks if the withdrawals root is non-nil, and withdrawals list is empty.
This spec change goes into the main rollup-node-p2p.md, to be consistent with the other gossip topics.
[ ] Update fault-proof-program spec that describes the output-claim verification,
and link to the Isthumus specs change of the block header.

Updated references Holocene -> Isthumus


Support for Ubiquiti access point device tracker (No Unifi controller required)

Description:
This adds support for a Unifi device tracker this is different from the current tracker https://home-assistant.io/components/device_tracker.unifi/ because it doesn't require the user to be running the Ubiquiti Unifi controller. This device tracker connects directly to a Unifi access point and pulls the connected clients via SSH. I have only tested with a UAP-AC-LR.
Not sure if the tests are sufficient enough...
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
device_tracker:
  - platform: unifi_direct
    host: <IP_ADDRESS>
    username: UBNT
    password: BLAH_BLAH
    track_new_devices: false

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[X] New dependencies have been added to the REQUIREMENTS variable (example).
[X] New dependencies are only imported inside functions that use them (example).
[X] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

I think you need to rebate your branch on latest dev. Also make sure you test all methods and cases. See red parts here:
https://coveralls.io/builds/14018332/source?filename=homeassistant%2Fcomponents%2Fdevice_tracker%2Funifi_direct.py

@MartinHjelmare fingers crossed, this might actually be done know?

@w1ll1am23 did you see my comment? I think you just need to move around the order of arguments to match the patch annotations. Then reapply the logout patch, and this should be done.

@MartinHjelmare sorry, I did see it but forgot that I did. I just made those changes and it ran locally, we will see what happens.

Fix the lint error and this is good to go! :tada:


refac: Comment on IIntegrationEventDispatcher.cs

Changed the comment on the interface method name "DispatchIntegrationEventsAsync".
Description

References

#887

Merge with main requires new review (I think).


Elligator for indistinguishable public key

Hi.
Thanks for this great project.
As noise and snow are famous for providing excellent security guarantees while requiring few efforts to adopt, I am trying to use snow in my (yet another) proxy tool (prototype) which aims at circumventing Internet censorship. I start with  Noise_NNpsk0_25519_ChaChaPoly_BLAKE2s as it looks pretty straightforward.
But then I realize that, in initial handshake messages, public keys (e of -> psk, e, e of <- e, ee in my case) are sent as plaintext, which leaves opportunities for an eavesdropper to distinguish a handshake from a uniform random byte string. As noted in the spec §10.5, elligator could be used to generate/encode public keys that are indistinguishable from random bytes.
Is there any plan to support it in the future?

Hey @Gowee,
Yes, support for Elligator could be added (or possibly just adding "codec" functions to the keys being transmitted over the wire so folks could take control of it themselves, as it's not an official part of the Noise framework).
How far along on your project are you, and do you have any ideas on how you'd like to see it implemented?

Hi, @mcginty.
It is here: https://github.com/Gowee/noisy-shuttle. A just-working prototype for now.
Considering that handshake messages are written out as opaque bytes instead of structs, I think a "codec" function (Fn(&[u8; 32]) -> [u8; 32] ?) would be straightforward. (Or is there an alternative way to get handshake messages as structured? Say, something like, struct Psk_E { pubkey: [u8; 32], aead_tag: [u8; 16] } ?)


bcrestoration.qgs updates -  symbolize veg_comp_lyr_r1_poly

aws layer is not schema prefixed so not currently in template.  Can close when that is done

can also add
WHSE_WATER_MANAGEMENT.GW_AQUIFERS_CLASSIFICATION_SVW - https://catalogue.data.gov.bc.ca/dataset/ground-water-aquifers/resource/dd0338c7-7b43-41da-918d-46c1d6df03ad


support THttpClientTransport

support THttpClientTransport

Can you provide more information? I do not see any new protocol added in this pull request.

Can you provide more information? I do not see any new protocol added in this pull request.

yeah.i had added ThriftHttpClient,ThriftHTTPClientPool,THttpEntity and THttpClientTransportAdapter in 9dab2f1

Can you add some test cases about it? I do not understand how it works.


Upgrade to Microsoft.UI.Xaml 2.6.2 (or equivalent)

This commit moves us from MUX 2.5 to MUX 2.6. I have temporarily
disabled the new control styles in TerminalApp\App.xaml by setting
ControlsResourcesVersion to Version1. There is no significant expected
visual impact.
Closes #10508

@msftbot merge this in 10 minutes


All infrastructure as code

Also ecr, s3

s3 is in terraform, ecr will stay as cli. the ecr stuff happens too early for the rest and i think it's fine when this will be handled with java sdk. its * as code anyway already.