Remove deprecated -f flag on docker tag

The -f flag on docker tag has been deprecated in docker 1.10 and is expected to be removed in docker 1.12.
This fix removed the -f flag on docker tag and also updated deprecated.md.
- Description for the changelog
The deprecated -f flag on docker tag has been removed.
NOTE: A separate pull request for engine-api will be opened to cover the related changes.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

thanks! can you check the bash/zsh completion scripts as well? not sure if they still contain this flag

also /cc @dnephin in case your PR needs to be updated

Thanks @thaJeztah. I checked contrib/completion/bash/docker and contrib/completion/zsh/_docker, didn't find the reference of -f/-force for docker tag.

@thaJeztah -f was removed from the completions in #19642, so we are clean here.

That's for checking! (Was typing on my phone, so wasn't able to check myself)
LGTM

@yongtang https://github.com/docker/engine-api/issues/239 was merged, so you can update the vendored engine-API files

Thanks @thaJeztah the pull request has been updated to include the engine-api changes. Let me know if there are any issues.

thanks! LGTM

LGTM 🐼

Moving this to docs-review. Looks like at least https://github.com/docker/docker/blob/master/docs/reference/api/docker_remote_api_v1.24.md#tag-an-image-into-a-repository needs some updates

Thanks @vdemeester. The related docs docker_remote_api_v1.24.md and docker_remote_api.md has been updated to include the changes in this pull request.

One small suggestion, but LGTM otherwise

Thanks @thaJeztah the pull request has been updated.

LGTM :angel:

It seems that there's no backwards-compatible way to force-tag images now that works with Docker versions prior to 1.10 (released only 5 months ago). I've opened #24494 for discussion; please consider waiting to drop this flag, as this will make it very difficult to migrate large Docker deployments to 1.12.


Add Applications section to user guide

Rename Features section to Applications.

Add first-pass adaptations of Linux Networking documents.

I did a rough cleanup pass on the content of Sandeep's LNW Documentation branch.

Created a docs/apps hierarchy.
Renamed files to fit into the existing paradigm.
Made sure each document had a title heading.
Removed individual tables of contents.
Addressed markdownlint warnings.
Added documents to index.


updates for F* PR 2488

F* PR 2488 changes the reflection AST for ascription nodes. This PR fixes its uses. In addition, there are a couple of proof tweaks in a file.

Thanks for the review, I will merge it once the F* PR is in.


When do you plan to release the training code

i've been waiting for 3 month too, i hope to get a date

Still no updates apparently. The "coming soon" was removed from the website a few months ago

When will code will be released? I have some family photos, They have some white scratches on them. If you guys know any other program to fix that problem then that would be great for me.

When will code will be released? I have some family photos, They have some white scratches on them. If you guys know any other program to fix that problem then that would be great for me.

you could post it on reddit.com/r/estoration

When will code will be released? I have some family photos, They have some white scratches on them. If you guys know any other program to fix that problem then that would be great for me.

you could post it on reddit.com/r/estoration

Sorry for the late reply, I saw your message pretty earlier but forgot to reply but anyways I will surely check it. Thanks for the help

Are you guys going to open source the actual project?

Are you guys going to open source the actual project?

I don't think so as it is been like a lot of months since this issue opened, maintainers didn't even comment once. So I think they just left it

The code is now released! We've also included Colab demos to enable users to easily try out our method. Don't hesitate to play with it if you've got some old photos you're eager to try out!

@roxanneluo Thanks Alot


Fix azure oracle deployment.

Description
Azure CLI has been updated to support Microsoft's Graph Query API (https://github.com/Azure/azure-cli/issues/12946), and the old "az ad sp show" query no longer works.
Tested
Deployed to baklava (centralus).
Backwards compatibility
The new query is not backwards compatible, but the old API is no longer available.

Thanks! 🚢


bump rsp to 1.4.1103-1

Hi @colearendt could you review this? I don't have permission to add reviewers or merge. Thanks!

Hi @colearendt could you review this? I don't have permission to add reviewers or merge. Thanks!

@melissa-barca thanks!! Has RStudio Server Pro changed where the .deb files are located?
Do you have access to this build on docker hub?  Done
Building dependency tree... 0% Building dependency tree... 0% Building dependency tree... 50% Building dependency tree... 50% Building dependency tree
Reading state information... 0% Reading state information... 0% Reading state information... Done
Failed to open the software package
The package might be corrupted or you are not allowed to open the file. Check the permissions of the file.
The command '/bin/sh -c apt-get update --fix-missing && curl -O ${RSP_DOWNLOAD_URL}/rstudio-server-pro-${RSP_VERSION}-amd64.deb && gdebi --non-interactive rstudio-server-pro-${RSP_VERSION}-amd64.deb && rm rstudio-server-pro-${RSP_VERSION}-amd64.deb && apt-get clean && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 1
build hook failed! (1)

And this is the base URL we are using, I believe: https://github.com/rstudio/rstudio-docker-products/blob/c5767e2f86dcfa9cd9b699082a33895d10b91378/server-pro/.env#L2

@melissa-barca thanks!! Has RStudio Server Pro changed where the .deb files are located?
Do you have access to this build on docker hub?  Done
Building dependency tree... 0% Building dependency tree... 0% Building dependency tree... 50% Building dependency tree... 50% Building dependency tree
Reading state information... 0% Reading state information... 0% Reading state information... Done
Failed to open the software package
The package might be corrupted or you are not allowed to open the file. Check the permissions of the file.
The command '/bin/sh -c apt-get update --fix-missing && curl -O ${RSP_DOWNLOAD_URL}/rstudio-server-pro-${RSP_VERSION}-amd64.deb && gdebi --non-interactive rstudio-server-pro-${RSP_VERSION}-amd64.deb && rm rstudio-server-pro-${RSP_VERSION}-amd64.deb && apt-get clean && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 1
build hook failed! (1)

And this is the base URL we are using, I believe: https://github.com/rstudio/rstudio-docker-products/blob/c5767e2f86dcfa9cd9b699082a33895d10b91378/server-pro/.env#L2

Thanks @colearendt I fixed the URL and the tests are now passing.

Thanks @colearendt I fixed the URL and the tests are now passing.


Remove version: Microsoft.Edge version 113.0.1774.50

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

For moderators or/and anyone else

[!Caution]
As a result of several personal problems I've had over the last few months + my final exams coming up very soon, I'm currently unable to look at my GitHub notifications every day and maintain my executions correctly.
If you detect a certain problem on a certain pul request:

Either you can close the pull request directly without mentioning me.
Or you can send me a message on X (Twitter): @Exorcism0666

Thank you for your understanding, and I'm sorry if some pull requests can't be approved due to the situation I'm in.

This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

URL: https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/998981f1-7f79-4799-ace0-857d7ac07db2/MicrosoftEdgeEnterpriseX86.msi
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 912)


Enable test components to handle props.children

Used in SAEI, should've make the change in the generator.

this one is already there in one of the pending PRs

https://github.com/Jam3/generator-jam3/pull/326/files#diff-93e76e8321c01bb9a194f4b6022469ebR18

Good to know, thank you! @namniak
btw what's the plan of merging all your PRs? can't wait

Duplicate of #326.


Zarf destroy doesn't clean up zarf secrets in deployed services

Steps to reproduce

Deploy a package with Zarf into the cluster.
Run 'zarf destroy'

Expected result
All zarf secrets are being cleaned up (including zarf secrets within deployed by zarf services).
Actual Result
Zarf secrets within deployed by zarf services are still exists.
Visual Proof (screenshots, videos, text, etc)

Thanks @olhakonst17 this is a good find.  Did you happen to use the optional flag --remove-components?  I believe that would have removed these as well.


Add aliasing error message

This code:
type alias Vector2 =
  { x : Float
  , y : Float
  }

v : Vector2
v =
  { x = 0 }

triggers this error message:
Type mismatch between the following types on line 9, column 5 to 10:

       Temp32703.Vector2

       { x : Float }

   It is related to the following expression:

       { x = 0 }

The whole "temp" part is super weird and not beginner friendly

I understand this as "type error messages should localize types so they are easier to read" which I agree with.
I'll open an issue for this on the compiler to track progress. Thanks for the report!

Sorry about the terrible name. I couldn't come up with a clear enough name. I hope the body was clear enough.
I think you may want to consider the possibility of expanding on the alias type.
Like adding:
mismatch between Vector and { x = 0 } ... yadda yadda ...

where

type alias Vector =
  { x : Float
  , y : Float
  }

as a sort of reminder. I think it may helpful to just remind what the type alias aliases to save time on going hunting for docs and stuff.
Ideally, someday, an IDE would offer a "go to definition" feature if you right-click or something, but in the meantime, this could help get that instant feedback and see actually what the mismatch is about.


DownloadPipelineArtifact task: Could not find any pipeline artifacts in the build.

I'd like to migrate from YAML builds to multi-stage YAML pipelines.
So I took a working template from our CI build and added stages/tasks for an integration deployment.
At first I had to realize that I need to download a published artifact "manually" (which makes sense, but wasn't obvious to me).
I am using sub-templates, the following example is "copied together".
The problem is that PublishBuildArtifacts@1 from the build logs File upload succeed., but DownloadPipelineArtifact@1 then errors out with Could not find any pipeline artifacts in the build..
1##[debug]Evaluating condition for step: 'DownloadPipelineArtifact'
2##[debug]Evaluating: SucceededNode()
3##[debug]Evaluating SucceededNode:
4##[debu
g]=> True
5##[debug]Result: True
6Starting: DownloadPipelineArtifact
7==============================================================================
8Task         : Download Pipeline Artifact
9Description  : Download Pipeline Artifact
10Version      : 1.1.3
11Author       : Microsoft Corporation
12Help         : Download named artifact from a pipeline to a local path.
13==============================================================================
14Download from the specified build: #3968
15Download artifact to: d:\a\1\a
16##[error]Could not find any pipeline artifacts in the build.
17##[debug]Processed: ##vso[task.logissue type=error;]Could not find any pipeline artifacts in the build.
18##[debug]Processed: ##vso[task.complete result=Failed;]
19##[debug]   at Agent.Plugins.PipelineArtifact.PipelineArtifactServer.DownloadAsync(AgentTaskPluginExecutionContext context, PipelineArtifactDownloadParameters downloadParameters, DownloadOptions downloadOptions, CancellationToken cancellationToken)
20   at Agent.Plugins.PipelineArtifact.DownloadPipelineArtifactTaskV1.ProcessCommandInternalAsync(AgentTaskPluginExecutionContext context, CancellationToken token)
21   at Agent.PluginHost.Program.Main(String[] args)
22Finishing: DownloadPipelineArtifact

The example:
trigger:
  batch: true
  branches:
    include:
    - develop

stages:
- stage: Build
  jobs:
  - job: Build
    pool:
      vmImage: windows-2019
      demands:
      - msbuild
      - visualstudio
      - vstest
    steps:
    # Build steps...
    - task: PublishBuildArtifacts@1
    displayName: 'Publish Artifact: FooBar'
    inputs:
        ArtifactName: 'FooBar'
- stage: INT
  jobs:
  - deployment: INT_Deployment
    pool:
      vmImage: windows-2019
    environment: 'INT'
    strategy:
      runOnce:
        deploy:
          steps:
          - task: DownloadPipelineArtifact@1
            inputs:
            artifactName: 'FooBar'
            targetPath: $(System.DefaultWorkingDirectory)
          # Deployment steps...

You could use it this way instead: https://github.com/microsoft/azure-pipelines-yaml/blob/master/templates/deploy-to-existing-kubernetes-cluster.yml#L46
Your yaml for publishing artifacts could look something like this:
    - task: PublishPipelineArtifact@0
      inputs:
        artifactName: 'FooBar'
        targetPath: 'artifacts'

And also, if you add a dependsOn step to your deployment it would download the artifacts by default. You wouldn't need an extra DownloadPipelineArtifact step

You have to differentiate between Build Artifacts and Pipeline Artifacts. The correct task you need for multi-stage YAML pipelines is PublishPipelineArtifact and DownloadPipelienArtifact.

Thanks for pointing that out @efzwo. Also understood pipeline artifacts as a successor over build artifacts regarding perf. and everything. Additionally publish and download have to be of the same kind, using PublishBuildArtifact and DownloadPipelineArtifact or vice versa will not work.
Unfortunately it is still not working for me.
- task: PublishPipelineArtifact@0
  displayName: 'Publish Artifact: FooBar'
  inputs:
    artifactName: 'FooBar'
    targetPath: '$(Build.ArtifactStagingDirectory)'

First I needed to find out that I have to set the targetPath to the staging directory which is set by default for the PublishBuildArtifact task. Now the artifacts package looks good.
Unfortunately I am not able to deploy my MSDeploy package (which is part of the artifacts package) because the ZIP file could not be found:
##[error]Error: No package found with specified pattern: d:\a\1\s**\FooBar.Web.zip`
But prior to this the download of the artifact was successful:
##[section]Starting: Download Artifact
==============================================================================
Task         : Download Pipeline Artifact
Description  : Download Pipeline Artifact
Version      : 1.1.3
Author       : Microsoft Corporation
Help         : Download named artifact from a pipeline to a local path.
==============================================================================
Download from the specified build: #1234
Download artifact to: d:\a\1/
Downloading 1 pipeline artifacts...
Information, DedupManifestArtifactClient will correlate http requests with X-TFS-Session {some-guid}
Information, Start downloading artifact - FooBar
Information, Minimatch patterns: [**]
Information, Filtered 1540 files from the Minimatch filters supplied.
Information, Could not initialize dataport.
Information, Downloaded 0.0 MB out of 540.0 MB (0%).
Information, Downloaded 231.4 MB out of 540.0 MB (43%).
Information, Downloaded 471.4 MB out of 540.0 MB (87%).
Information, Downloaded 540.0 MB out of 540.0 MB (100%).
Information,
Download statistics:
Total Content: 540.0 MB
Physical Content Downloaded: 327.6 MB
Compression Saved: 212.4 MB
Local Caching Saved: 0.0 MB
Chunks Downloaded: 7,539
Nodes Downloaded: 0

Information, Download completed.
Downloading artifact finished.
##[section]Finishing: Download Artifact

I tried both ways as @ds-ms stated. Implicitly via dependsOn and explicitly via DownloadPipelineArtifact. Weird enough to say that when I tried the explicit way I had two download tasks: "Download Artifact" and "DownloadPipelineArtifact" (and yes, dependsOn was commented out...).
Can you tell me if this is correct for deploying the wep app?
      - task: AzureRmWebAppDeployment@3
        displayName: 'Deploy FooBar'
        inputs:
          azureSubscription: 'Foo/Bar/Project ({some-guid})'
          WebAppName: 'int-foobar-web'
          DeployToSlotFlag: true
          ResourceGroupName: 'INT-foobar'
          SlotName: 'some-valid-slot'
          Package: '$(System.DefaultWorkingDirectory)/**/FooBar.zip'

"Default" "Download Artifact" task download path:
Download artifact to: d:\a\1/
My explicit use of DownloadPipelineArtifact@1 with downloadPath: '$(System.DefaultWorkingDirectory)':
Download artifact to: d:\a\1\a
Use a part of the artifact via AzureRmWebAppDeployment@3 and Package: '$(System.DefaultWorkingDirectory)/**/FooBar.zip':
##[error]Error: No package found with specified pattern: d:\a\1\s**\FooBar.zip
Obviously none of the download paths matches with the path where the MSDeploy package is being searched for. It seems like $(System.DefaultWorkingDirectory) changed in the meantime. What is going on?!

I am using $(System.ArtifactsDirectory) in the second stage now instead it works. Dunno why it shouldn't with the other variable but nevermind. Thanks guys!


GH-910: Fix return type headers for async returns

Fixes https://github.com/spring-projects/spring-amqp/issues/910
cherry-pick to 2.1

... and cherry-picked to 2.1.x


Allow configuration of unordered list character

Thanks for the work on this plugin!
One thing I'd love to see is the ability to configure the character used to prefix unordered list items. Unless I'm missing something, this plugin always uses -. In other projects that I work in, the * is preferred. Also, my personal preference is the asterisk.

Implemented in https://github.com/dprint/dprint-plugin-markdown/pull/101 (0.17.0 -- releasing in a few mins)


feat: configuration change handling

related: #56

user/valaxy.config.ts > user/site.config.ts
user/vite.config.ts > user/valaxy.config.ts
remove vite.valaxy
handling details and hot load config

other:

user/vite.config.ts
theme/vite.config.ts
theme/valaxy.config.ts
doc update(part)

For Single-file obsessive user:
// valaxy.config.ts
export default defineConfig({
  // site info config
  site: {},
  // all vite config
  vite: {},
  // markdown plugin
  markdown: {}
  // other internal plugin
  // ...
})

For beginner:
// site.config.ts for site info
export default defineSite({})

For users who like categorization:

vite.config.ts for vite
valaxy.config.ts for internal plugin
site.config.ts for site info config

I think we should switch between different identities at will for the convenience of all users

This will happen if mixed together, users and themes cannot be switched at will, and theme valaxy needs to be handled separately

We should try our best to meet the low switching cost, which can make our users and theme development more convenient, make our themes more, and everyone can become a theme developer. As long as it wants to be, we should be as contented as possible.


Datepicker handlers

Hi,
In short, I have 2 questions.

How can I close the datepicker on selection?
Why does this datepicker implementation not suffer from this bug  whereas Materialize's one (and mine) does?

Longer explanation:
I understand Materialize uses pickadate.js under the covers. Having checked its API I see there are a range of event callbacks available:

How can I apply these to the datepicker in Angular 2? I got as far as grabbing the datepicker through
        var $input =$(this.el.nativeElement); // We grab a reference to the datepicker here
        var picker = $input.pickadate('picker');

but there's not a great deal I can do from there. I actually want to close the datepicker on selection and found that an attribute 'closeOnSelect' exists: http://amsul.ca/pickadate.js/date/
Unfortunately, placing this in [materializeParams] doesn't seem to work.
One more thing, I noticed the Datepicker sample here http://angular2-materialize.surge.sh/#/datepicker
does not suffer from this bug  whereas Materializes (plus mine) does... can you think of any reasons why? I thought the implementation between both would be near identical...
As always, thank you!
Pieris

Got this sorted.
For the date handling part, I used:

        var $input = $(this.el.nativeElement); // We grab a reference to the datepicker here
        var picker = $input.pickadate('picker');
        picker.on('close', function() {
          //...
        })

Are we able to use events callback already? Do anyone knows how to do it in Angular 2?

See here: https://github.com/InfomediaLtd/angular2-materialize/issues/283
<input materialize="pickadate" [materializeActions]="actions" type="text" />

this.actions.emit({action:"pickadate",params:["close"]});


[FLINK-13587][table-planner-blink] Fix some operator names are not set in blink planner

What is the purpose of the change
Currently, there are some transformation names are not set in blink planner. For example, LookupJoin transformation uses "LookupJoin" directly which loses a lot of informatoion.
Brief change log

Introduces a RelWriter RelDisplayNameWriterImpl to reuse code of "explainTerms" to generate operator names
Fix some operator names are not set in blink planner

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

As discussed with @godfreyhe offline, we will rename getDisplayName to getRelDiscription() and keep it in FlinkRelNode.
Will update this later.

Hi @godfreyhe , I have updated the PR.

@godfreyhe  comments addressed.

Travis passed.
Merging...


[SPARK-38222][SQL] Expose Node Description attribute in SQL Rest API

What changes were proposed in this pull request?
Currently, SQL public Rest API does not expose node description and it is useful to have more details at query level such as:
- Join Operators(BHJ, SMJ, SHJ) => when correlating join operator with join type and which leg is built for BHJ.
- HashAggregate => aggregated keys and agg functions
- Providing alignment with SparkUI DAG visualization (per node/operator) under sql page (nodeDesc is shown
   when user comes on the operator on UI)
- List can be extended for other operators.

Current Sample Json Result:
{
    "nodeId" : 14,
    "nodeName" : "BroadcastHashJoin",
    "wholeStageCodegenId" : 3,
    "metrics" : [ {
          "name" : "number of output rows",
          "value" : {
        "amount" : "2"
          }
    }
},
...
{
    "nodeId" : 8,
    "nodeName" : "HashAggregate",
    "wholeStageCodegenId" : 4,
    "metrics" : [ {
      "name" : "spill size",
      "value" : {
        "amount" : "0.0"
      }
    }
}

New Sample Json Result:
{
    "nodeId" : 14,
    "nodeName" : "BroadcastHashJoin",
    "nodeDesc" : "BroadcastHashJoin [id#4], [id#24], Inner, BuildLeft, false",
    "wholeStageCodegenId" : 3,
    "metrics" : [ {
          "name" : "number of output rows",
          "value" : {
        "amount" : "2"
          }
    }
},
...
{
    "nodeId" : 8,
    "nodeName" : "HashAggregate",
    "nodeDesc" : "HashAggregate(keys=[name#5, age#6, salary#18], functions=[avg(cast(age#6 as bigint)), avg(salary#18)])",
    "wholeStageCodegenId" : 4,
    "metrics" : [ {
      "name" : "spill size",
      "value" : {
        "amount" : "0.0"
      }
    }
}

Why are the changes needed?
It is useful to have more details  at query level such as:

join type,
which leg is built for BHJ,
aggregated keys,
agg functions
Providing alignment with SparkUI DAG visualization (per node/operator) under sql page etc.

Does this PR introduce any user-facing change?
No
How was this patch tested?
Add more coverage to existing UTs

cc @gengliangwang @srowen

I don't have enough context to really have an opinion. While it seems reasonable, I wonder in general whether it makes sense to return the description all the time (? this would return the description in many responses?) where it's just overhead in a lot of cases.

Thanks @srowen for quick feedback. Please find some samples per operation as follows. I also attach whole sql response to jira in order to give clear idea:
https://issues.apache.org/jira/secure/attachment/13040136/Spark_SQL_REST_Result_with-nodeDesc

I think on following options:

We can exclude WholeStageCodegen and if (nodeName == nodeDesc) for all use-cases.
Option 1: We can expose SQLConf in order to include white-listed operators. With this option, the user can define the operator white-list. For example:

spark.sql.rest.api.include.operators.from.desc=SortMergeJoin,HashAggregate,Project

Option 2: We can also expose another SQLConf if end user wants to see nodeDesc of all operators. For example:

spark.sql.rest.api.enable.all.operators.desc=false(default)

Sample Results:
"nodeName" : "SerializeFromObject",
"nodeDesc" : "SerializeFromObject [knownnotnull(assertnotnull(input[0, org.apache.spark.status.api.v1.sql.Salary, true])).personId AS personId#17, knownnotnull(assertnotnull(input[0, org.apache.spark.status.api.v1.sql.Salary, true])).salary AS salary#18]",

"nodeName" : "Project",
"nodeDesc" : "Project [personId#17 AS id#24, salary#18]",

"nodeName" : "Exchange",
"nodeDesc" : "Exchange hashpartitioning(name#5, age#6, salary#18, 5), ENSURE_REQUIREMENTS, [id=#87]",

"nodeName" : "Sort",
"nodeDesc" : "Sort [id#24 ASC NULLS FIRST], false, 0",

"nodeName" : "Scan",
"nodeDesc" : "Scan[obj#3]",

"nodeName" : "SortMergeJoin",
"nodeDesc" : "SortMergeJoin [id#4], [id#24], Inner",

"nodeName" : "HashAggregate",
"nodeDesc" : "HashAggregate(keys=[name#5, age#6, knownfloatingpointnormalized(normalizenanandzero(salary#18)) AS salary#18], functions=[partial_avg(age#6), partial_avg(salary#18)])",

"nodeName" : "Filter",
"nodeDesc" : "Filter<EMAIL_ADDRESS>
// Following ones need exclusion
"nodeName" : "WholeStageCodegen (3)",
"nodeDesc" : "WholeStageCodegen (3)",

"nodeName" : "Project",
"nodeDesc" : "Project",

No to new configs, IMHO. Is this info not available from some other API that tells you about nodes, rather than return it as a side effect in other calls? maybe I misunderstand


Reissue info is shown on releases page

I think of this as a first step. My first idea was to have an icon/text in the top right corner, but I couldn't find a way I liked so I went for the card-body version with text. So maybe a solution that also includes the cards on the homepage could later replace this.
Further future ideas: filtering releases by reissue flag and being able to exclude these releases from mails.

 Handle reissues and rereleases

Quite nice for an interim solution, final solution should be https://trello.com/c/ae9s5L3D

Yeah I thought of something like that too!


[CARBONDATA-1541] There are some errors when bad_records_action is IGNORE

Fix error:
1.When table only have one column and the column data is INT, it should be success
2.when sort_columns is null,it should be success

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/389/

Build Failed with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/267/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/390/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/268/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1020/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/392/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/270/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1021/

Please review it @QiangCai

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1023/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/280/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/403/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1034/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/406/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/283/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1037/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/286/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/409/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1040/

Please review it @jackylk

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/420/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/296/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1050/

@jackylk I have changed it and CI pass.

LGTM

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1183/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/552/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1417/


[docs] python3 bytes -> string in example in README

The current README.md indicates the following "first TensorFlow program":
>>> import tensorflow as tf
>>> hello = tf.constant('Hello, TensorFlow!')
>>> sess = tf.Session()
>>> sess.run(hello)
Hello, TensorFlow!
>>> a = tf.constant(10)
>>> b = tf.constant(32)
>>> sess.run(a+b)
42
>>>

This works fine under python2, but handling of strings has changed slightly in python3. Suggested improvement to the example program for compatibility with both python2 and python3 (we need to convert bytes to string):
>>> import tensorflow as tf
>>> hello = tf.constant('Hello, TensorFlow!')
>>> sess = tf.Session()
>>> sess.run(hello).decode("utf-8")
Hello, TensorFlow!
>>> a = tf.constant(10)
>>> b = tf.constant(32)
>>> sess.run(a+b)
42

Tested from the wheel build of 0.11.0 (final), converted to RPM, on Fedora 24/25.
Thanks!

@dgoerger would you like to send a PR? Thanks.

@dgoerger What is the error message you see with the current version?

Hmm. Further testing suggests this may be more serious than I'd thought. Type inconsistency, not just documentation.
$ python3
>>> type('Hello, TensorFlow!')
<class 'str'>
>>> type(tf.constant('Hello, TensorFlow!'))
<class 'tensorflow.python.framework.ops.Tensor'>
>>> type(tf.Session().run(tf.constant('Hello, TensorFlow!')))
<class 'bytes'>

According to the docs, input type Tensor outputs via numpy ndarray, which appears not to output type string. Reformatting Session.run(Tensor) when output type is bytes, to new output type string, might give the intended behaviour here. Compare non-ASCII:
$ python3
>>> import tensorflow, sys
>>> type('¿Cómo se ve?')
<class 'str'>
>>> type(tensorflow.constant('¿Cómo se ve?'))
<class 'tensorflow.python.framework.ops.Tensor'>
>>> type(tensorflow.Session().run(tensorflow.constant('¿Cómo se ve?')))
<class 'bytes'>
>>> type(tensorflow.Session().run(tensorflow.constant('¿Cómo se ve?')).decode(sys.getdefaultencoding()))
<class 'str'>
>>> tensorflow.Session().run(tensorflow.constant('¿Cómo se ve?'))
b'\xc2\xbfC\xc3\xb3mo se ve?'
>>> tensorflow.Session().run(tensorflow.constant('¿Cómo se ve?')).decode(sys.getdefaultencoding())
'¿Cómo se ve?'

... and of course the same doesn't work on python2:
$ python2
>>> import tensorflow, sys
>>> type('¿Cómo se ve?')
<type 'str'>
>>> type(tensorflow.constant('¿Cómo se ve?'))
<class 'tensorflow.python.framework.ops.Tensor'>
>>> type(tensorflow.Session().run(tensorflow.constant('¿Cómo se ve?')))
<type 'str'>
>>> type(tensorflow.Session().run(tensorflow.constant('¿Cómo se ve?')).decode(sys.getdefaultencoding()))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 0: ordinal not in range(128)
>>> # yikes, python2 default encoding is ascii
>>> type(tensorflow.Session().run(tensorflow.constant('¿Cómo se ve?')).decode('utf-8'))
<type 'unicode'>
>>> tensorflow.Session().run(tensorflow.constant('¿Cómo se ve?'))
'\xc2\xbfC\xc3\xb3mo se ve?'
>>> tensorflow.Session().run(tensorflow.constant('¿Cómo se ve?')).decode('utf-8')
u'\xbfC\xf3mo se ve?'

So I guess fixing this discrepancy will require evaluating what type object should be output by tensorflow.Session().run(Tensor(string)). On the other hand, is it possible non-ASCII doesn't work at all under the current Session.run() python2 implementation? The python2 output seems non-ideal, but maybe I'm missing a common trick.

TensorFlow converts str to bytes in most places, including sess.run, and this is unlikely to change.  The user is free to convert back, but unfortunately it's too large a change to add a unicode dtype to the core.  Closing as won't fix for now.

For the record, it's useful to use
from tensorflow.python.util import compat

compat.as_bytes(...)
compat.as_text(...)

to do the conversions between bytes and string when needed.


low t-values affecting cluster based statistics

I'm using the function permutation_cluster_1samp_test from the cluster_level module in mne.stats.  The output of stat_fun shows extraordinarily low t-values, which are all from nodes in the medial wall. I have provided a boolean array to the exclude argument of the function to list the nodes to exclude. The only clusters I am ending up with in my final results are those adjacent to the medial wall with negative t-values. Is there a way to deal with this issue without defaulting to the use of a one-tailed test?
I'm using the mne version '0.17.2' and here is the code for the function call:
tfce = False
chance=0.1
nproc=1
n_permutations=10000
n_subjects = 16
threshold = dict(start=0, step=0.1) if tfce else \
    -stats.distributions.t.ppf(0.05, n_subjects - 1)
# run it

stat = permutation_cluster_1samp_test(
    data.samples - chance,
    threshold=threshold,
    tail=0,
    stat_fun=ttest_1samp_no_p,
    n_jobs=nproc,
    n_permutations=n_permutations,
    out_type='indices',
    connectivity=c,
    exclude=vals_inv[0],
    seed=423
)

The boolean array given as an input to exclude was obtained from a medial wall mask, and the sparse connectivity matrix c was calculated from a gifti file.

@vassiki by "low" do you mean close to zero, or negative? For close to zero you can start your threshold above zero somewhere, it might help.
Otherwise it might be useful to figure out why the medial vertices are so strongly activated for your data


Add Support for MatchPyramid model

This is a support for MatchPyramid model discribed in Text Matching as Image Recognition.

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

thanks @ssdf93 . do you have some model result on the text matching task in the tutorial.md?

Hi, @ssdf93
In your Interaction layer, you provide a parameter hidden_dim for uses. But actualy, if there hidden_dim is not consistent with its previous block, it will raise Exception. So please remove the hidden_dim parameter and get it automatically from previous block.

Thank you very much @ericwtlin , I have modified the interaction layer and the test score of wikiQA is now 0.7634


Contradiction that needs to be resolved

In file object.h there is an issue where the move constructor states that it will not throw an exception yet if the argument is not of type Object it throws.

You're right, it has been changed.


fix(parent-visibility): decouple tab from parent visibility

Related Ticket(s)
Closes #11749
Description
This decouples C4DTab from ParentVisibilityMixin, which avoids the sideeffect of registering the c4d-tab component, when you're otherwise just making use of ParentVisibilityMixin.
Changelog
Changed

Avoids referencing C4DTab from ParentVisibilityMixin by duplicating the event name.

The code changes here look good to me, but this is failing ci-check. Can you look into that, @m4olivei ?

Huh, interesting, appraently there is a rule that requires static get returns to only be a string or string literal:
https://github.com/carbon-design-system/carbon-for-ibm-dotcom/blob/main/packages/web-components/tools/babel-plugin-create-react-custom-element-type.js#L186-L190

Okay, now that we have a representative deploy preview, I've found an issue. <dds-cta-block-item-row> uses ParentVisibilityMixin, and it's not rendering properly within tabs (see https://ibmdotcom-webcomponents.s3.us-east.cloud-object-storage.appdomain.cloud/deploy-previews/11759/index.html?path=/story/components-cta-block--within-tabs).

Thanks @jkaeser . Looks like main has the same problem. I'll look into it.

It turns out that the Tabs Extended component changed structure such that the tab component is no longer a parent to the contents of each tab panel. As such, the ParentVisibilityMixinImpl doesn't work in v2 and a new paradigm is needed for doing the same.
In addition, the story for CTA block > Within tabs was not correctly updated in v2 for the new tabs strucutre alluded to above.
All that is to say, we're now out of scope for the original ask and we kind of need to take this back to the drawing board for v2, which we'll do in a follow up issue.
Closing for now.


Logo of this Bamboo compiler

This is about time this Bamboo compiler gets a logo.

We could always put up a bounty for you @pirapira 😉
https://github.com/ethereum/vyper/issues/794

I'd love to take a crack!


TypeError when using reversible rule operator

The reversible rule operator | does not seem to work.  The following model results in a TypeError being raised:
Model()
Monomer('A', ['bind'])
Monomer('B', ['bind'])
Parameter('k', 1)
Rule('bind', A(bind=None) + B(bind=None) | A(bind=1) % B(bind=1), k, k)

The specific error is:
TypeError: unsupported operand type(s) for |: 'ReactionPattern' and 'ComplexPattern'

Please could you confirm the version of Python and PySB you're using? I was unable to reproduce your error on either Python 2.7.14 or Python 3.5.2 using the current PySB master (commit c55f3a5).
You can check the PySB version with print(pysb.__version__).

Python 3.6.1 and pysb v1.5.0

PySB v1.5.0 is the latest release version, but the | reversible rule operator was only recently added to PySB on Github. It will be present in the next release.
If you want to use | in the meantime, you'll need to use a pre-release version of PySB from Github (e.g. pip install git+git://github.com/pysb/pysb.git). I'll speak to other admins about getting a release out ASAP so that our users can begin switching to the new syntax.

Ah, ok.  It was in the docs, so I figured it was in the latest release
Thanks!

PySB v1.6.0 has now been released, which includes the | reversible rule operator. We've also updated pysb.readthedocs.org to reflect the most recent release by default, rather than development version, to avoid such confusion in the future.


Bring back Python 3.6 debugging support by breaking debugging out into its own extension

By making debugging a separate extension we can do an initial release using debugpy 1.5 which will work all the way back to Python 2.7, and then immediately do another release using debugpy 1.6. That way people who need debugging support for older Python versions can pin the debugging extension version but leave the Python extension alone to get newer feature support (if it works with the old version of Python that they are running).

Is this only for debugging support? Or can Intellisense also be included? I work for a company that uses Red Hat 7 which does support 3.6 as part of the distribution.

This is only explicitly for debugging as IntelliSense shouldn't be affected by any of this as Pylance is written in TypeScript. If you're using Jedi then that is up to the Jedi project itself in terms of what versions they support.

I am feeling that this  answers  my question on why my debugger does not start: https://stackoverflow.com/questions/74812777/vs-code-python-debugger-would-not-start-with-python-extension-2022-xx-xx-althoug?noredirect=1#comment132043707_74812777
What is the minimal python version that still works with the python extension debugger.

What is the minimal python version that still works with the python extension debugger?

Python 3.7.

v2022.6.3  working fine

Is there any ETA? I'm regularly hit by the update / new install then later wonder why something doesn't work on a remote...
Additional this would make the Python extension itself smaller which is nice for people that don't actually need to debug.

@GitMensch no promises, but we are hoping for a preview release in May.
And Python 2.7 is in the same situation as 3.6, so we would have to see if the last debugpy release would work with the extension and then make that the initial release, do an immediate new release for one that uses the newest version that supports back to Python 3.6, and then do yet another immediate release that uses the newest version of debugpy regardless of Python version support. But once again, no promises on whether we will be able to get support for Python 2.7 out.

@brettcannon Hello!
I write an example to support debugging python3.6. Instead of using the pythonFiles/lib/python/debugpy package directly, I use pythonFiles/dispatch_debugpy package to import different versions of debugpy depending on python versions.
Would you like to consider this way?
Here's example code, not fully tested yet, but works on my local machine. Support debugging python 3.6

That looks nice, but I'm not sure if the python36 path is "general setup" that will be found in all environments.
Yes, handling this in ts code would likely be preferable, it would at least provide an option to explicit specify python36 (or 27).

It seems like there are at least 3 kinds of python paths:

debugAdapterPython: active interpreter or workspace folder interpreter
debugLauncherPython: active interpreter or workspace folder interpreter
debugee python: python config in launch.json

And the adapter, launcher, debugee all use the same debugpy path which is {EXTENSION_ROOT_DIR}/pythonFiles/lib/python by default.
When workspace folder interpreter is different to python config in launch.json, the debugee may use a different version of python from adapter and launcher.
In order to keep debugpy version matching python version, debugpy path and python path should be set in ts code.

We have the new debugpy extension out in preview, but it currently only supports Python 3.7 or newer. Once we know the separation was done successfully (which we would appreciate help with if you have Python 3.7 or newer), we plan on releasing "older" versions of the extension with older versions of debugpy which will cover Python 3.6.
So it's all coming along and being actively worked on, but it's not done yet.

这是来自QQ邮箱的自动回复邮件。 您好，你的邮件我已经收到。

Nice, so there's hope to get an even "older" version that supports Python 2.7 if Python 3.6 works, right?

Nice, so there's hope to get an even "older" version that supports Python 2.7 if Python 3.6 works, right?

Yep, that's the hope! If https://pypi.org/project/debugpy/1.5.1/ works as we hope it will, then it covers Python 2.7 through (at least) Python 3.9, so fixing this for 3.6 implicitly brings Python 2.7 support along with it if there isn't something odd about supporting such an old version of Python.

Any updates here? Does debugpy 1.5.1 allows debugging in python3.6?

这是来自QQ邮箱的自动回复邮件。 您好，你的邮件我已经收到。

Any updates here? Does debugpy 1.5.1 allows debugging in python3.6?

We're actively working on getting our new debugging extension to work with debugpy 1.5.1 which supports Python 2.7 and newer. We will announce here once the extension has a version that you can use and test with. If you want to help speed that work up, please use the extension with any Python code you have that supports Python 3.7 and newer to help make sure the debugger code is as stable as possible before we effectively fork it for a one-time release with debugpy 1.5.1.

We have released the version of the debugging extension that works with debugpy 1.5.1! To use it, install the latest version starting with 2023.1.* on VSCode Insiders. Please help us use the extension with any Python code you have that supports Python 3.6 or lower to help ensure that the debugger code is as stable as possible. Thanks

If anyone has time to verify the 2023.1.* versions of https://marketplace.visualstudio.com/items?itemName=ms-python.debugpy work for them when debugging Python 2.7 or Python 3.6 we would really appreciate it! We won't be fixing bugs in older versions of the Python Debugger extension, so once we move on from debugpy 1.5.1 that will be it for supporting those older versions of Python.
If we don't hear from anyone we will assume the extension works fine and move on to do a release with debugpy 1.7 (Python 3.7 and newer) and then shortly thereafter do a release for debugpy 1.8 (Python 3.8 and newer).

Hi @brettcannon. I could do a simple python 2 debugging session with the latest vscode, python extension and the latest 2023.1.* of the debugpy extension (stepping through code, inspecting variables).
Does it mean installing the debugpy extension 2023.1.* with the latest python extension is the recommended way to debug python 2 and 3.6? Is it preferred over installing an older version of the python extension itself?

Does it mean installing the debugpy extension 2023.1.* with the latest python extension is the recommended way to debug python 2 and 3.6?

Yep!

Is it preferred over installing an older version of the python extension itself?

Also yes!
The idea is that you install the version of the Python Debugger extension that's appropriate/necessary for your version of Python (and FYI we will be shifting all of our debugging over to the separate extension once we feel confident in its stability), but that you can then install whatever version of the Python extension you want, including the latest version (assuming there isn't something in it that you want which no longer works with your version of Python).

Thanks for your work! When I am trying to debug inside my docker container (with dev container extension), I am still prompted that python version lower than 3.7 is not supported. Am I missing some steps? I tried to hit the debug button, or use "Debugpy: Debug Python File" in command palette, the behaviors are the same

The versions installed inside my dev container:
Python Extension: v2023.16.0
Debugpy Extension: v2023.3.12621007
Debugpy version: 1.5.1

Am I missing some steps?

@XuShenLZ  Are you using the Python Debugger extension or the Python extension itself? And are you using the appropriate version of the Python Debugger extension?

Am I missing some steps?

@XuShenLZ Are you using the Python Debugger extension or the Python extension itself? And are you using the appropriate version of the Python Debugger extension?

@brettcannon I have both Python Debugger extension or the Python extension installed. And the versions of them are listed above

Python version: 3.6.9
VS Code Python Extension: v2023.16.0
VS Code Debugpy Extension: v2023.3.12621007 (v2023.1.12492010 does not work either)
Debugpy package version: 1.5.1

It seems that when I hit the "debug" button or "Debugpy: Debug Python File" in the command palette, it still tries to use the Python extension to do that. How should I set it to use Debugpy Extension?

Thanks for your reply @XuShenLZ, the version 2023.3.* does not support python versions lower than 3.7. Could you try again with the version v2023.1.12492010?(Make sure that this version is installed in the container)
If the bug persist could you create an issue in the Python Extension repo with more information about your system? Thanks

Thanks @paulacamargo25 . I tested again with version v2023.1.12492010. The good news is that it can work for Python 3.6.9, but the bad news is that I have to use the "RUN and DEBUG" panel on the right to start debugging, rather than the convenient debug button at the right top corner of my python file.
I have brought this up in an issue in the Python Extension repo.

Is attaching to a remote debugpy 1.5.1 supported?

It should when both sides are running the same version of debugpy, but @paulacamargo25 should be able to give a more definitive answer.

From debugpy perspective, it depends on direction of connection, too.
If you're using "connect" in your launch.json and --listen on the debuggee side, all debugpy code is running on the latter, and the remote connection is between the client (VSCode) on one end and debugpy on the other, which is pure DAP and should be supported with any debugpy version.
OTOH if you are using "listen" in launch.json and --connect in the debuggee, you have the debug adapter running on VSCode side and the debug server (pydevd) running remotely. What passes on the wire then is still mostly DAP but there are some bits that are non-standard. This should still mostly work in practice, but I'm not entirely sure that we never broke back-compat for this not-quite-DAP.
Since the scenario described above is the first one, it's more likely that breakpoints not being hit are due to some issues with path mapping, or possibly because the folder is misinterpreted as library code (if so, "justMyCode":false should fix it).

Oh no. This kit need to support python2 also

So here's the summary as I see it:

Current Debugpy extension v2023.3.13341006 doesn't support Python <= v 3.7
Somehow, v2<IP_ADDRESS> does.
However, v2<IP_ADDRESS> isn't available on the extension's website.

I certainly can't get the debugger to work with a conda environment with Python 3.6 installed:

Is there anything that can be done for us folk who still need to maintain code bases with Python <= 3.7?  Happy to play with experimental setups as well.
Thanks!

Thanks! Got it working.
For anyone else dropping by here after a web-search, here are the complete set of steps to debug Python code <=3.7 on Visual Studio Code:

Get Visual Studio Code Insiders (Not "regular" Visual Studio Code)

Install Python extension. Right click on the settings icon in the extensions marketplace, and click "Install another version"

Choose v2023.22.1 (Other versions may work, but roughly, versions  from January 2023 seem to be the last versions that support <= Python 3.7)

Search for debugpy again in the Extensions sidebar. Once again, select "Install another version". Choose v2023.1.12492010

If you have Visual Studio Code Insiders installed on other laptops like I do (a work/home laptop e.g.), make sure you uncheck "Sync this extension". But don't worry; as the sync is Insiders-to-Insiders, it won't affect your "regular" VS Code setup.

Reload if necessary.

When you do debug your code, do so via the Run-and-Debug panel, and not the button on the right. Do make sure you select the right conda environment as well (but you know how to do that already, dont you)

The other alternative is to junk this and use PyCharm (which apparently works seamlessly for all Python versions), but where's the fun in doing that. :)

Get Visual Studio Code Insiders (Not "regular" Visual Studio Code)

This shouldn't be necessary after the next release of VS Code which should be out roughly 2024-02-01.

The other alternative is to junk this and use PyCharm (which apparently works seamlessly for all Python versions), but where's the fun in doing that. :)

Admittedly we could as well (we use the same base debugger and we actually used to fund it's development), but it's a download size trade-off: little over 100 MB or over 500 MB? And this also affects downloading updates to the extension. And w/ the vast majority of our users not needing to download an older version of debugpy, we decided on the smaller, faster, less wasteful approach.

Thanks! Got it working.
For anyone else dropping by here after a web-search, here are the complete set of steps to debug Python code <=3.7 on Visual Studio Code:

Get Visual Studio Code Insiders (Not "regular" Visual Studio Code)
Install the Python extension. Right click on the settings icon in the extensions marketplace, and click "Install another version"

3. Choose v2023.22.1 (Other versions may work, but roughly, versions  from January 2023 seem to be the last versions that support <= Python 3.7)
4. Search for debugpy again in the Extensions sidebar. Once again, select "Install another version". Choose v2023.1.12492010

5. If you have Visual Studio Code Insiders installed on other laptops like I do (a work/home laptop e.g.), make sure you uncheck "Sync this extension". But don't worry; as the sync is Insiders-to-Insiders, it won't affect your "regular" VS Code setup.
6. Reload if necessary.
7. When you do debug your code, do so via the Run-and-Debug panel, and not the button on the right. Do make sure you select the right conda environment as well (but you know how to do that already, dont you)

The other alternative is to junk this and use PyCharm (which apparently works seamlessly for all Python versions), but where's the fun in doing that. :)

vS code 1.87 not allowed to use old version of debugger.

vS code 1.87 not allowed to use old version of debugger.

Can you be more specific? Extensions can set a minimum VS Code version, but not a maximum.

这是来自QQ邮箱的自动回复邮件。 您好，你的邮件我已经收到。

I tried to install another old version of debugger as advised( Search for debugpy again in the Extensions sidebar. Once again, select "Install another version". Choose v2023.1.12492010), but could not find the version any more

I tried to install another old version of debugger as advised( Search for debugpy again in the Extensions sidebar. Once again, select "Install another version". Choose v2023.1.12492010), but could not find the version any more

There was a bug in the marketplace. Please try again.

Same here vscode : 1.84.2 won't show the 2023.X debugpy versions

4. v2023.1.12492

still only v2024 available, got any info on this behaviour ?

You can follow the steps here in order to install a pre-release version of the extension.

still only v2024 available, got any info on this behaviour ?

A detail that I'm not sure is obvious is you need to opt into the pre-release version of the extension as the older versions of the extension w/ older debugpy releases were released as pre-release. As soon as you switch you will see all of the versions:

(Notice how I filtered the versions to only "2023.1" and you can sort of make out behind the drop-down it says "Switch to Release Version", showing I'm using a pre-release version.)

I have opened https://github.com/microsoft/vscode-python-debugger/issues/212 to help make this more clear.

I'll close this issue since the Python Debugger is already in production, feel free to submit a feature-request pr bug report in the Python Debugger Extension Repository.

Hello! ?9?9Thanks for your


[Draft] Social event Page under "Events"

This PR add a single page under /social-event and the corresponding link in the menu. The /social-event page has general information about the Tuesday social event, a button to buy tickets and a thank you to our sponsor.

-change CEST to Dublin time.

ticket page referenced but doesn't have any social event info.
add kiwi's brief


Complex types binding

In section for Complex types I think this sentence

For each property of the complex type, model binding looks through the sources for the name pattern prefix.property_name. If nothing is found, it looks for just property_name without the prefix.

is not 100% correct.
If a query like ?Instructor.Id=10&Name=foo is bound to method void OnGet(Instructor instructor) than resulting object of type Instructor will have field Id set to 100 but field Name willl be null.
Not sure if this for all targets but at parameters is is like that in ASP.NET 6.0 (cf. https://github.com/dotnet/aspnetcore/blob/ae1a6cbe225b99c0bf38b7e31bf60cb653b73a52/src/Mvc/Mvc.Core/src/ModelBinding/ParameterBinder.cs#L157)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e24f48f8-6c4d-ecda-6ce6-a7826d396e99
Version Independent ID: 9c4af557-8d06-4c6c-ad2a-0dd234547563
Content: Model Binding in ASP.NET Core
Content Source: aspnetcore/mvc/models/model-binding.md
Product: aspnet-core
Technology: aspnetcore-mvc
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

From my investigation is was always like that (at least in ASP.NET Core) and I would treat this as documentation issue only.
When I was hit by this issue I first checked docs and they stated that ID would bind in this scenario. 4 hours later after a lot of debugging, code reading and testing I managed to find implementation. And it actually makes sense for me. It was only docs that put me into wrong way.

Yes, I can see in the code you linked that the decision to use the prefix is determined up-front, so it makes sense. Perhaps we should update the docs to explain that this decision is up-front, and not evaluated for each property.


feat(navbar): navbar redesign

Navbar redesign

Overview

Changelog

Review requests

Risk assessment

Code comments:

This is a really massive PR. It would have been better as a series of smaller PRs

This adds a lot of CSS to the monorepo

The monorepo does not use the .module.css convention used in the website

We've been moving away from CSS modules to styled-components in the monorepo

Variables attached to :root appear to shadow other variable that the component library attaches to :root, which has led to bugs in the past

Any :root variables (if CSS cannot be avoided) should be named/scoped so as to not conflict with already established variable names from the components library

I don't see any unit tests added, which I would want for the components that include state

Behavior notes from reviewing http://sandbox.labware.opentrons.com/navbar-redesign/. This is just what I noticed, and shouldn't be considered an exhaustive list

The nav should match the content width, but it does not

The dropdown carets don't appear to be present

The mobile nav CTA buttons look like their spacing is wrong

Also, I'm getting weird scroll bar behaviors for elements underneath the mobile nav

I addresed comments, but I don't know why sandbox version is different than the local version. I guess thats why you see this visual issues.

Still looks like there are navbar width + spacing issues at a variety of screen sizes:


apiv2(ticdc): implement the get processor

What problem does this PR solve?

Issue Number: ref #8019
What is changed and how it works?
Implement the get processor for API v2
Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
No
Do you need to update user documentation, design documentation or monitoring documentation?
No
Release note
`None`

/run-all-tests

/merge

/run-verify-tests
/run-kafka-integration-tests

/run-verify-tests


Bump submariner-operator version

...to get latest RBAC changes.
Related to https://github.com/submariner-io/submariner/pull/2897

cc @sridhargaddam @Jaanki


Write Documentation for App

Primarily to describe the proposals but also to discuss other features.
Got started here: https://hackmd.io/Onj4udZlRgKq9jasY6LI-w
Here is what we did for FDD: https://hackmd.io/PTma-ucCQHm88pkN_Zfpqw
Should include As Is and Potential Enhancements headings to explain current functionality and inspire ways to increase automation or add features. Would like to sell a vision of what is possible for future engagements.
May consider just replacing the README: https://github.com/0xBootleggers/bufficorn

https://github.com/SporkDAOOfficial/bufficorn-dao/blob/main/README.md


Create a create-soroban-dapp boilerplate based on create-react-app (with next)

### My tasks
- [ ] https://github.com/paltalabs/soroban-react/issues/55
- [ ] https://github.com/paltalabs/soroban-react/issues/58
- [ ] https://github.com/paltalabs/soroban-react/issues/56
- [ ] https://github.com/paltalabs/soroban-react/issues/57
- [ ] https://github.com/paltalabs/soroban-react/issues/59


[WIP]Deploy referendumauth-contract on mainchain

fix #1986

:x: Build AElf <IP_ADDRESS>71 failed (commit https://github.com/AElfProject/AElf/commit/512b7ccf00 by @xiangxingxing)

:white_check_mark: Build AElf <IP_ADDRESS>08 completed (commit https://github.com/AElfProject/AElf/commit/3b9a7f203f by @rosona)


Make advanced page load current settings into the page

Currently, the advanced page always starts with the same checkboxes checked, etc.  It should be loaded with the current settings.

Resolved by 536c97484b295640a9472aed7c04bf2374b7ce06.

Reopening because this is currently incomplete; the advanced query checkbox is checked and the toggle early/late/randomize are not loaded (although they haven't been added to the querydata yet anyway, so I don't blame you).  I'll update this ticket once the dependency issue has been fixed.

@mdiller You're good to finish this up now.

Resolved by 19854a71178e3a9b156ebfa72bb1ab071da4334e

Thanks!


Fix text position on Y-axis, we should take fontSize in mind to layout the Text/TSpan shapes

SVG coord tes case https://www.w3.org/TR/SVG/images/coords/OrigCoordSys.svg

Close as it's been picked into 6.0.0 branch.


Add Array Unterface for createIndex(_:unique:ifNotExists:)

How about adding array interface for createIndex(_:unique:ifNotExists:), in addition to variadic interface?
Inside variadic function the type of the parameter is Array. But it does not accept Array Type.
Isn't it inconvenient a little bit in using it inside some functions like below?
import SQLite

var table: Table
func Hoge(numberColumns: Int...) {
...
table.createIndex(numberColumns) // Error because of variadic.
...
}

Sincerely,

It is inconvenient and it’s my fault. I tried to remove controversy between documentation and code.
Please see https://github.com/stephencelis/SQLite.swift/blob/master/Documentation/Index.md#indexes and https://github.com/stephencelis/SQLite.swift/pull/666 for more details.


Getting 404 error testing basic Authentication call on http://docs.timdorr.apiary.io

Not sure if this is appropriate place to post this issue - apologies if not..
I am using:
http://docs.timdorr.apiary.io/#reference/vehicle-commands/open-trunkfrunk/get-an-access-token?console=1
Passing in the grant_type, client_id, client_secret and my valid Tesla email and password (in plain text -- is that the issue?) --- and when I run that on 'Production' and choose 'Call Resource' - I always get a 404 error....
I can't figure out what I'm doing wrong, but suspect that this call should work.  NOOb :|

Don't use the tools on the site. You need to make these requests in your language/library of choice.


Supply a docker image for the Unipept server

After discussion with the HPC@UGent team, Bart came up with the idea of supplying the Unipept server as a virtual machine for local installation. I think this would be a great idea. To go even further, power users that run one or more instances of the Unipept server could also donate free CPU cycles to the community. This would require a scheduler that dispatches user request (which are already split in several blocks anyway) across the available Unipept servers. This could also be used as a load balancer if users run multiple private instances of the Unipept server. Probably there are already frameworks that can handle this kind of dispatching.
Perhaps the dispatcher than also would need to take into account the version numbers of the available Unipept instances, and clients could selectively target certain instances. In addition, some scenario could be tought over to automatically update Unipept servers if new versions of the database become available.
Original issue by @pdawyndt on Sun May 11 2014 at 21:36.

Docker might be an option
Original comment by @bmesuere on Fri May 23 2014 at 10:31.

Passenger provides base docker images for rails deployment. (as seen https://github.com/phusion/passenger-docker)
Original comment by ghost on Fri May 23 2014 at 10:32.

see also:

S. V. Angiuoli, M. Matalka, A. Gussman, K. Galens, M. Vangala, D. R. Riley, C. Arze, J. R. White, O. White, and W. F. Fricke. Clovr: a virtual machine for automated and portable sequence analysis from the desktop using cloud computing. BMC Bioinformatics, 12:356, 2011.
A. Wilke, J. Wilkening, E.M. Glass, N. Desai, and F. Meyer. An experience report: porting the mg-rast rapid metagenomics analysis pipeline to the cloud. Concurrency and Computation: Practice and Experience, 23(17):22502257, 2011.
J. Wilkening, A. Wilke, Narayan Desai, and Folker Meyer. Using clouds for metagenomics: A case study. In
IEEE Cluster 2009 , 2009.

Original comment by @pdawyndt on Sun Jun 01 2014 at 12:30.


Remove all the bugs that code contain

Make the code more stable and easy to understand.

I want to work on this issue please assign me this issue.

I want to work on this issue under JWOC

I want to work on this issue under JWOC

I want to work on this issue under JWOC

You can start the work.

I think this work is left pending for many days , i am not sure but as far as i remember i refactored the code in my PR #17 , if there's anything left pls inform @Nikhil636  and lets close this simple issue.  I am ready to contribute under JWOC but before that can you pls check if there's anything that needs to be refactored left ?

I don't think there's anything left to refactor, I'm closing this issue you can claim any other issue

I think this work is left pending for many days , i am not sure but as far as i remember i refactored the code in my PR #17 , if there's anything left pls inform @Nikhil636 and lets close this simple issue. I am ready to contribute under JWOC but before that can you pls check if there's anything that needs to be refactored left ?


Organization_id error

Log in again to obtain new cookies.

I've run into the same issue myself. No matter what I try, nothing seems to work... even logging back in. I'm starting to wonder if there's a fix for this, or if Claude has banned it.

must be a network environment in the us or the uk

must be a network environment in the us or the uk

I can access it through my browser, but the crawler returns {"error": {"type": "permission_error", "message": "We are unable to serve your request"}}. I have set up the proxy.

I try setting up a proxy, and it works.

Hi, I am in the US and I also cannot use this api. I have the same error here.
Moreover, I cannot find the cookie:

scroll down to find the cookie😅

@deflorator1980 what's that debugging view called, please?


Extract Durations Tacotron2 with reduction_factor > 1

Facing AssertionError: different between sum_durations and len_mel when using reduction_factor > 1.
https://github.com/TensorSpeech/TensorflowTTS/blob/master/examples/tacotron2/extract_duration.py#L179
Although it works fine with reduction_factor = 1.
Are there any changes to be made for the same?
Thanks.

@vikrantsharma7 hi you cann't do that, duration is extracted from alignment which produces from Tacotron-2 with reduction_factor=1.

@dathudeptrai thanks for the quick reply.


jsonpath v0.5.6 doesn't deal with empty strings well.

In JSON documents having an empty string ( "" ) is considered valid, for example:
"source_amount": {
    "currency": "USD",
    "value": "100",
    "issuer": ""
}

However, the jsonpath gem drops the following stack trace when it sees empty strings:
19:19:14 jobs.1 | Agent#517: Error when fetching url: no implicit conversion of nil into String
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/jsonpath-0.5.6/lib/jsonpath.rb:15:in `initialize'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/jsonpath-0.5.6/lib/jsonpath.rb:15:in `new'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/jsonpath-0.5.6/lib/jsonpath.rb:15:in `initialize'
19:19:14 jobs.1 | /home/drwho/huginn/lib/utils.rb:59:in `new'
19:19:14 jobs.1 | /home/drwho/huginn/lib/utils.rb:59:in `values_at'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:303:in `block in extract_json'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:297:in `call'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:297:in `block in extract_each'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:296:in `each'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:296:in `each_with_object'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:296:in `extract_each'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:302:in `extract_json'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:195:in `block in check_url'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/liquid-2.6.2/lib/liquid/context.rb:112:in `stack'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:173:in `check_url'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:164:in `block in check_urls'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:163:in `each'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:163:in `check_urls'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agents/website_agent.rb:157:in `check'
19:19:14 jobs.1 | /home/drwho/huginn/app/models/agent.rb:437:in `async_check'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/performable_method.rb:30:in `perform'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/backend/base.rb:94:in `block in invoke_job'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/backend/base.rb:91:in `invoke_job'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:204:in `block (2 levels) in run'
19:19:14 jobs.1 | /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/timeout.rb:91:in `block in timeout'
19:19:14 jobs.1 | /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/timeout.rb:101:in `call'
19:19:14 jobs.1 | /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/timeout.rb:101:in `timeout'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:204:in `block in run'
19:19:14 jobs.1 | /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:203:in `run'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:280:in `block in reserve_and_run_one_job'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:280:in `reserve_and_run_one_job'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:187:in `block in work_off'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:186:in `times'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:186:in `work_off'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:150:in `block (4 levels) in start'
19:19:14 jobs.1 | /home/drwho/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:149:in `block (3 levels) in start'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:148:in `block (2 levels) in start'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:147:in `loop'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:147:in `block in start'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/plugins/clear_locks.rb:7:in `call'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/plugins/clear_locks.rb:7:in `block (2 levels) in <class:ClearLocks>'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `call'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `call'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `block in add'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
19:19:14 jobs.1 | /home/drwho/.rvm/gems/ruby-2.1.5/gems/delayed_job-4.0.6/lib/delayed/worker.rb:146:in `start'
19:19:14 jobs.1 | bin/threaded.rb:47:in `block (2 levels) in <top (required)>'
19:19:14 jobs.1 | bin/threaded.rb:17:in `safely'
19:19:14 jobs.1 | bin/threaded.rb:44:in `block in <top (required)>'

All things considered this seems pretty harmless but it can also make it difficult to isolate bugs in other agents running at the same time.  What if there was a way (and there may not be - ECANTFIX is fine) to turn of stack traces like this?

Really?  What's the json path you're using?

For the following JSONpath, if there has been no transaction the strings are empty:
"extract": {
    "transaction_timestamp": {
      "value": "$.payments.[*].timestamp"
    },
    "source_account": {
      "value": "$.payments.[*].source_account"
    },
    "destination_account": {
      "value": "$.payments.[*].destination_account"
    },
    "source_value": {
      "value": "$.payments.[*].source_amount.value"
    },
    "source_currency": {
      "value": "$.payments.[*].source_amount.currency"
    },
    "destination_value": {
      "value": "$.payments.[*].destination_amount.value"
    },
    "destination_currency": {
      "value": "$.payments.[*].destination_amount.currency"
    },
    "direction": {
      "value": "$.payments.[*].direction"
    },
    "transaction_hash": {
      "value": "$.payments.[*].hash"
    }
  }

Which extraction is blowing it up?

All of them.  If there are no recent transactions, the value of every key in "extract" will be empty (i.e., "").

@virtadpt, what URL is that JSONPath fetching?  I'd like to try it locally.  Maybe you could give me the Scenario JSON?

The scenario JSON is a couple of megabytes in size, so getting it to you will be problematic.  However, here is a URL that triggers this bug on a semi-reliable basis: https://api.ripple.com/v1/accounts/rrrrrrrrrrrrrrrrrrrrBZbvji/payments

Haha, so after playing with this for like 45 minutes, I realized you need to use path instead of value. :hamster:
#831 should prevent this in the future.

When I have time I'll update my install and give it a spin.

@virtadpt You can just switch your usage from value to path now and it should work.  My addition is just a validation.

I've made the change, and it was like night and day. Thanks!

Great!


Negative ccp_alpha issues

Likley due to rounding, some things added in recent commits to 3_LearnAndBuildBT

Issue is with training being different than full training/cost pruning


fix: reflect attributes used for styling

Alaska Airlines Pull Request
Fixes #10
Summary:

reflect target attribute so that :host([target]) styles apply when property set
set default values for boolean properties
remove commented out code

Type of change:
Please delete options that are not relevant.

[x] Revision of an existing capability

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

:tada: This PR is included in version 1.2.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Timetally function tabs not visible

I have deployed the time tally application successfully in teams as per your deployment steps but not getting function tabs like add task , add project , submit approval etc. also not able to access manager dashboard.

You should be set as a manager of someone in the Azure AD to see these functions.

@tamasv83 How long will it take for the Buttons ( task, project, submit approval ) to show on the app after >> You should be set as a manager of someone in the Azure AD to see these functions?

@Anny-Alex after setting yourself as a manager of someone in the Azure AD, were you able to see the buttons which you weren't seeing previously?


Make the first residence in Residence History represent the Current Residence

The first residence in Residence History should be explicitly called out to be the client's "Current Residence."

The End Date for the Current Residence should always read, "Present"

#170 suggests that End Date should be interchangeable with Lease End Date, instead of saying "Present."  What say you to this?

Rolling with this solution for now.


Workspace exclude doesn't work if nested under a member path

Problem
It doesn't appear as though the workspace.exclude key works for paths that are nested under a path included in workspace.members
Steps

Create a nested package structure:

/tmp % cargo new outer
     Created binary (application) `outer` package
/tmp % cd outer
/tmp/outer % cargo new middle
     Created binary (application) `middle` package
/tmp/outer % cd middle
/tmp/outer/middle % cargo new inner
     Created binary (application) `inner` package

Add a workspace.members key to the outermost level, and observe that the workspace build succeeds:

/tmp/outer/middle % cd /tmp/outer
/tmp/outer % echo "[workspace]\n  members = [\".\", \"middle\"]" >> Cargo.toml
/tmp/outer % cargo build --all
   Compiling middle v0.1.0 (/tmp/outer/middle)
   Compiling outer v0.1.0 (/tmp/outer)
    Finished dev [unoptimized + debuginfo] target(s) in 0.34s

Now go to the inner package and observe that the build fails:

/tmp/outer % cd /tmp/outer/middle/inner
/tmp/outer/middle/inner % cargo build
error: current package believes it's in a workspace when it's not:
current:   /tmp/outer/middle/inner/Cargo.toml
workspace: /tmp/outer/Cargo.toml

this may be fixable by adding `middle/inner` to the `workspace.members` array of the manifest located at: /tmp/outer/Cargo.toml

Fair enough; let's explicitly exclude this package instead, and try again:

/tmp/outer/middle/inner % cd /tmp/outer
/tmp/outer % echo "exclude = [\"middle/inner\"]" >> Cargo.toml
/tmp/outer % cd /tmp/outer/middle/inner
/tmp/outer/middle/inner % cargo build
error: current package believes it's in a workspace when it's not:
current:   /tmp/outer/middle/inner/Cargo.toml
workspace: /tmp/outer/Cargo.toml

this may be fixable by adding `middle/inner` to the `workspace.members` array of the manifest located at: /tmp/outer/Cargo.toml

It still wants to be in the workspace! We're stuck.
Possible Solution(s)
If there's overlap between paths in members and exclude, I would expect the more-specific path to win. In this case, the excluded path "middle/inner" is more specific than the member paths "." or "middle", so the exclusion should win. This is probably not so simple if the paths contain globs, though.
Notes
Output of cargo version:
% cargo version
cargo 1.31.0 (339d9f9c8 2018-11-16)

Thanks for your looking into this :crab:

As a workaround, in "inner" you can include an empty [workspace] table, and it will work.
I definitely see some wonkiness with checking paths "starts_with".

Yeah, that's the workaround I'm using for now; I can imagine situations where it will be painful to change the inner package, though.

I just encountered this when creating a dummy crate inside my examples/ directory and originally thought it had something to do with #6009.
The crate is only ever meant to be compiled as WASM so I don't want to include it in the normal workspace. Fortunately I have control over the source code so I can use the workaround proposed by @ehuss for now.

In my case the top-most Cargo.toml has:
[workspace]
members = [".", "crates/*", "commands/*"]
default-members = [".", "crates/*", "commands/*"]

and I want to exclude crates/README.md and commands/README.md with
exclude = ["crates/README.md", "commands/README.md"]

but I get failures that
$ cargo build
error: failed to read `/Users/felipesere/Development/rust/orogene/crates/README.md/Cargo.toml`

Caused by:
  Not a directory (os error 20)

I was expecting anything listed in exclude (whether its heardcoded or a glob) to be removed from the members

Any chances this bug can be resolved, or are there any workarounds? Currently running into this problem since I want to create a binary for testing, and put it under the directory for the library it tests.

[This is yet resolved]
I am going to close this. Further discussion could happen in #11405. If you think this is wrong please leave a comment. We could reopen it.

Any chances this bug can be resolved, or are there any workarounds? Currently running into this problem since I want to create a binary for testing, and put it under the directory for the library it tests.

I guess you can use this workaround.

I'd like to confirm that this is still an issue with the following:
exclude = ["runtime/crates/scripting"]
members = ["runtime/crates/*"]

scripting does not contain a Cargo.toml (it holds other crates), so this causes an error. I've side-stepped this for now by expanding out the crates/* glob manually, but it would be nice to have more predictable behaviour here.

Still facing this issue. It's particularly annoying when you have crates you'd like to exclude in a member's tests folder.

#14155 contains an same test for cargo's testsuite.


Display Error

Hi, at first let me say thanks for this great module.
i got an display error since updating to latest magic mirror version.

Picture is attached. Any idea how to fix this?

Not quite sure what the issue is, but I am looking into it. This is a duplicate of #7 so I am going to close this issue out.


Made spacing consistent

I linted the markdown to make the style of the document consistent.

Hi @rogersachan, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;


Instruction unclear on how to start

I tried to authorize, but the code ends with an error (TypeError: __init__() got an unexpected keyword argument 'allowed_methods')

Hi, can you send the code snippet that you currently have

I just used the same code provided in the documentation and replaced the id, secret, url, username and passwords

I created a new release that addressed this issue. Please use pip install --upgrade ticktick-py and see if you get the same error. Thank you for making the issue!

Same errors still. After the upgrade.

I do have the same issue, using the provided start instructions. Ticktick version 2.0.1

Ahh okay I will continue working on a fix. I haven't been able to reproduce the problem so I will work on that. In the meantime, doing something like this may work:
from ticktick.oauth2 import OAuth2        # OAuth2 Manager
from ticktick.api import TickTickClient     # Main Interface
import requests

requests_session = requests.session()

auth_client = OAuth2(client_id=client_id,
                                   client_secret=client_secret,
                                   redirect_uri=uri,
                                   session=requests_session)

client = TickTickClient(username, password, auth_client)

I think it worked. Now I have to see how to work with the api :)
Thanks.


URLs which redirect to latest version of a package

i.e. http://package.elm-lang.org/packages/<author>/<package>/latest redirects to http://package.elm-lang.org/packages/<author>/<package>/2.2.1
Would be useful for linking to a package from a blog post or Github page, when you want readers to see the latest, not direct them to a specific version.

Whoops, this appears to already be supported. Could swear I tried it and it didn't work…


Add sound for incorrect quiz answers

Incorrect answer sound: https://brainy-literacy-assets.s3.amazonaws.com/audio/incorrect_answer_sound.mp3
As of right now, there is no audio for a correct answer in the aws bucket.

Please add your planning poker estimate with ZenHub @Fattimo


Resizing & statuslines

Describe the bug
HI, There are still 2 bugs in dashboard.

When I open neovim and dashboard appears then I ran the command :h browse (or any other command like :h showmode )
then the doc appears for that particular command but when I close the doc by :q then the doc disappears but the statusline and tabline still show up in dashboard also.
When I open up neovim in terminal and dashboard appears then I resized the terminal but that resized have 2 problems.

The Quit option which actions = :q stops working after resizing.
Other options in dashboard for files doesn't work well. After resizing the terminal while keeping neovim open the New File and settings option of dashboard works but they don't dispaly the statusline and tabline in new file opened from dashboard option after resize. ( new file in dashboard actions = DashboardNewFile and settings in dashboard actions = :e ~/.config/nvim/lua/setttings/init.lua )

To Reproduce
Steps to reproduce the behavior:

Open up neovim in terminal and run :h browse or any other help command. Then close the doc by :q and you will see the statusline and tabline in dashboard appeared.
Open up neovim in terminal and the resize the terminal by increasing size of terminal. then you will see the Quit option stops working and New File option to not display statusline and tabline in new file.

Min config
{ desc = 'Quit',
  action = ':q' },
{ desc = 'New File',
  action = 'DashboardNewFile' }

Expected behavior
Dashboard should not be affected by resizing the terminal and statusline and tabline should not be appeared in dashboard after closing the doc for an option in dashboard.
Screenshots
This is a screenshot when I resized the terminal, Quit option stoped working and settings option and New file option opened without displaying statusline and tabline.
Note: I can quit the dashboard even after resizing the terminal by typing :q command but the Quit option which do the same :q stops working and other files option gets affected too)

This is a screenshot of statusline and tabline appeared in dsahboard after closing doc for a vim/neovim command.

like i said this is expect behavior . if you don't like this PR welcome.

@glepnir and what about the resize issues? Can you please fix those. Just open neovim in terminal and then inrease the size of your terminal and you will see.

I use window tiling program. Unable to test your window behavior. Resize neovim via tmux works fine. So I can't work for your environment

@glepnir  the isssue is in tmux also. I just used to tmux to test the resize issue and the issue is there.
Which OS are you using? I'm user of Artix Linux with mate-terminal and desktop.

Dunno whats the problem, maybe my terminal problem.

can't reproduce.

@glepnir  I will try another desktop environment in the new Artix realese when it comes out. I think the problem is in my mate terminal.

@glepnir sorry to bother you once again but the issue is not in terminal as I checked it on another laptop with lxde desktop having lxde terminal. Please try this resize error without tmux in the os default terminal. I need to close neovim whenver resized.

why lots of people not these question ? I think you should check the usage. some times not make sense I think. it just a simple start screen plugin. just use once on neovim start. Don't make it complex.


provide more info when package is not installable

Codecov Report

Merging #25 into master will decrease coverage by 2.5%.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           master     #25     +/-   ##
========================================
- Coverage    96.8%   94.3%   -2.5%
========================================
  Files           6       6
  Lines         679     679
========================================
- Hits          657     640     -17
- Misses         22      39     +17

Impacted Files
Coverage Δ

conda_concourse_ci/compute_build_graph.py
88.2% <100%> (-9.1%)
:arrow_down:

Continue to review full report at Codecov.

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

Codecov Report

Merging #25 into master will decrease coverage by 2.5%.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           master     #25     +/-   ##
========================================
- Coverage    96.8%   94.3%   -2.5%
========================================
  Files           6       6
  Lines         679     679
========================================
- Hits          657     640     -17
- Misses         22      39     +17

Impacted Files
Coverage Δ

conda_concourse_ci/compute_build_graph.py
88.2% <100%> (-9.1%)
:arrow_down:

Continue to review full report at Codecov.

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

Codecov Report

Merging #25 into master will decrease coverage by 2.5%.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           master     #25     +/-   ##
========================================
- Coverage    96.8%   94.3%   -2.5%
========================================
  Files           6       6
  Lines         679     679
========================================
- Hits          657     640     -17
- Misses         22      39     +17

Impacted Files
Coverage Δ

conda_concourse_ci/compute_build_graph.py
88.2% <100%> (-9.1%)
:arrow_down:

Continue to review full report at Codecov.

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


Extend fix-its for C-style for loops to include loop var "+= 1"

Since the commit to deprecate “++” went through soon after the one to
deprecate C-style for loops, it’d be nice to auto-fix the for loops
even after previously changing ++ to += 1. So let’s do that.

Nice, thanks!


Code Editor issues

Challenge http://freecodecamp.com/challenges/waypoint-comment-your-javascript-code has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
I entered my comments into the code editor, however, the left panel is responding by pretty much telling me my code has an error. I don't see anything wrong with my line of code, and this is also the first time that the left panel has said why my code is incorrect, which I've noticed that it never had mentioned reasons for any of my code errors in my code editor in the previous lessons.

I had the same issue.
I went back to "Map" and click around a bit, and then back into this 'waypoint' and it just showed it as successful without doing anything.

Closing as duplicate of #2137


fix(tours): consider tours might not have a waypoint when asking for …

…last driver

Coverage remained the same at 42.382% when pulling 93d6fd6cfa129c5c91b8a6353eb065e2f6d3147d on fix/tours into 61ad5427ed5c0691636f39dab6e1507460ed3f92 on master.

Coverage remained the same at 42.382% when pulling 93d6fd6cfa129c5c91b8a6353eb065e2f6d3147d on fix/tours into 61ad5427ed5c0691636f39dab6e1507460ed3f92 on master.


Notification click listener doesn't unsubscribe

https://github.com/oasisprotocol/oasis-wallet-ext/blob/dabb8b41c105b86bf7e526916541e9db9dc98d0c/src/background/service/APIService.js#L688-L696
If user creates 3 transactions (without closing the popup), and clicks on 3rd notification, then it will open 3 duplicate tabs

listener should probably filter if (id === id) and then removeListener
I would prefix id with e.g. 'txConfirmed-' + id, so adding different notifications won't cause a conflict

It is slightly better now that it has filtering by ID
https://github.com/oasisprotocol/oasis-wallet-ext/blob/33f4c7e35079299e5aa8771ee544f98bc9fdb898/src/background/service/APIService.js#L767-L780


Logger instance hook for logging to different locations.

This is definitely one of the better and more flexible logging frameworks for client side swift. Awesome work.
It would be great, however, to add an abstraction which will allow you to assign multiple output locations. E.G., Instead of just logging to standard output, it would be nice to be able to take the same record and just send it to another logging service via https.
Happy to open a PR for this when I get the time.

I second this feature request


Not working with multiple fonts styles

Thanks a lot for hosting these font files.
Unfortunately what you are suggesting  ("glyphs": "https://cdn.jsdelivr.net/gh/kylebarron/openmaptiles-fonts/fonts/{fontstack}/{range}.pbf") doesn't work with multi font styles like Positron as described here.
The style is requesting https://cdn.jsdelivr.net/gh/kylebarron/openmaptiles-fonts/fonts/Metropolis%20Regular,Noto%20Sans%20Regular/0-255.pbf and fails with a 401 error.
Do you have any suggestions?
Thanks.

Well, that's expected. If you need to serve Metropolis%20Regular,Noto%20Sans%20Regular from static files, you'd need to have a folder named that, including the comma. Usually a list of font selections (i.e. in CSS) mean "choose the first one that exists". So if you know Metropolis Regular exists, then you can remove Noto Sans from the list.
So just fork positron and change
        "text-font": ["Metropolis Medium Italic", "Noto Sans Italic"],

to
        "text-font": ["Metropolis Medium Italic"],

Closing as I don't think this is related to this font repository.

Thanks for the explanation.