Bug with evaluator (pytrec)

Running twice an evaluator with metrics evaluated at different cut-offs changes the result (I tested with nDCG and AP), as in this code (observe that the second call returns :
import ir_measures
from ir_measures import * # imports all supported measures, e.g., AP, nDCG, RR, P

qrels = {
    'Q0': {"D0": 0, "D1": 1},
    "Q1": {"D0": 0, "D3": 2},
    "Q2": {"D0": 1, "D3": 2},
}
run = {
    'Q0': {"D0": 1.2, "D1": 1.0},
    "Q1": {"D0": 2.4, "D3": 3.6},
    "Q2": {"D4": 2.4, "D10": 3.6}
}

evaluator = ir_measures.evaluator([nDCG @ 10, nDCG @ 20], qrels)

ndcg20_a = evaluator.calc_aggregate(run)[nDCG@20]
ndcg20_b = evaluator.calc_aggregate(run)[nDCG@20]

# Gives AssertionError: nDCG@20 values are different: 0.5436432511904858 vs 0.0
assert ndcg20_a == ndcg20_b, f"nDCG@20 values are different: {ndcg20_a} vs {ndcg20_b}"

The second run returns a value of 0 (but this does not happen if using only nDCG@20 or another metric)

Hi @bpiwowar -- this is a bug that stems from a problem with pytrec_eval. We've fixed the issue on our fork of pytrec_eval, which can be installed via pytrec-eval-terrier==0.5.4
It looks like the main branch or ir-measures requires the newer version, but it hasn't made its way to pypi yet.
More info on the issue here: https://github.com/terrierteam/ir_measures/issues/42#issuecomment-1237454081

OK this indeed fixes the issue, thanks

Would it be possible to release a new version of ir-measures with the updated requirements?

Hey @bpiwowar - I pushed v0.3.3 to pypi, which should address this problem.

Great thanks !


PHP 8: method_exists() fixes and composer.json version constraint update

Ref: sebastianbergmann/phpunit#4325
PHP 8 builds are currently failing because method_exists() calls throw exceptions if the argument is not string|object. This PR fixes these calls by making sure the arguments are string|object before calling method_exists. This is because PHP 8 throws \TypeError and \ValueError exceptions from internal functions.
In preparation for PHP 8, this PR also updates composer.json PHP version constraint to allow PHP 8.
All tests now pass on PHP 8 dev builds.

Considering the tests don't need updating, and classes cant be numeric anyways i don't think this is a BC break, so this should be good to merge.
I'm gonna keep the nightly build on allow failure for now, as it could break build if there is a 'bad' version on travis.

Awesome, thanks a lot @BackEndTea .


[KOGITO-5316] BDD tests: Wrong Jobs service image is used for Infinis…

…pan test
Signed-off-by: Karel Suta<EMAIL_ADDRESS>https://issues.redhat.com/browse/KOGITO-5316
Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[x] You have read the contributors' guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains a link to the JIRA issue
[x] Pull Request contains a description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[x] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

Tested locally as this is not covered in BDD smoke tests.


Add SNI support to the HttpClient class

resolve #716

Cool. You solved the architectural issue blocking me validating domains (https://github.com/an-tao/trantor/pull/120). I'll try and see if this also solved the handshake issue.


Fix space in script path and Fix new file explorer instance error

Currently if the directory path to Register.cmd or Uninstall.cmd contains spaces, a UAC prompt will come up, after accepting the prompt it closes and does nothing.
This patch fixes two bugs:

Space in full path to scripts.
If Register.cmd is ran and instead of closing the file explorer window if you open a new instance of file explorer, it causes a crash, as shown in the next picture.

You mentioned that you fixed "If Register.cmd is ran and instead of closing the file explorer window if you open a new instance of file explorer, it causes a crash, as shown in the next picture."
But there doesn't seem to be a relevant source code change in the commit?
Also there is an encoding error in the "Uninstall.cmd" file.

You mentioned that you fixed

"If Register.cmd is ran and instead of closing the file explorer window if you open a new instance of file explorer, it causes a crash, as shown in the next picture."

But there doesn't seem to be a relevant source code change in the commit?
Also there is an encoding error in the "Uninstall.cmd" file.

The taskkill at the end of Register.cmd is responsible for not allowing the user to create a new instance.

Well, the coding is still wrong, but I will fix it, thank you.


[QUESTION] How to dynamically add commands with typer?

First check

[x] I used the GitHub search to find a similar issue and didn't find it.
[x] I searched the Typer documentation, with the integrated search.
[x] I already searched in Google "How to X in Typer" and didn't find any information.
[x] I already searched in Google "How to X in Click" and didn't find any information.

Description
I am writing a CLI tool that would expose various commands available that are dynamically created and I need a method for adding commands when the app starts as they depend on the tool config, for example when run inside a different repository it may expose a different set of commands.
Additional context
While using click in the past I was able to create some extra commands but I discovered that I was not able to change their description because the __doc__ is static and python does not allow me to update it after the object are created.

Would something like that do:
Given dynamic.json
{
  "first-command": true,
  "second-command": true,
  "second-command-name": "my-name",
  "second-command-help": "This is dynamic description."
}

and dynamic_cli.py
import typer
import json

with open('dynamic.json', 'r') as j:
    config = json.load(j)

app = typer.Typer()

def say_hello():
    typer.echo("HELLO")

def say_goodbye():
    typer.echo("BYE")

if config["first-command"]:
    app.command()(say_hello)

if config["second-command"]:
    say_hello.__doc__ = config["second-command-help"]
    say_hello.__doc__ += " 5546"

    app.command(
        name=config["second-command-name"],
    )(say_goodbye)

if __name__ == "__main__":
    app()

You can configure what is exposed by the CLI. You could also use app.command(hidden=True), however it just hides the command from help - you could still call it.
Or your use case is more complex and you are looking for some more sophisticated solution?

@captainCapitalism Thank you! The example seem to be sufficient for my use-case. I am going ot test it this evening. I was about to avoid click completely for this new tool due to the complications related to docs and dynamic commands.
I will close it, eventually reopening if it does not work.

Thanks for the help here @sathoune ! 👏  🙇
Thanks for reporting back and closing the issue @ssbarnea  👍

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.

hello! how can we also dynamically add arguments to the command? i'm trying to generate a typer CLI programmatically


Tableau Dashboard Lineage Drawn to Table in Different Schema

Affected module
Ingestion - Tableau
Describe the Bug
We have a Snowflake database service with ingestion configured to consume all schemas from our production database. In this database, we have a public schema that holds a number of dimension and fact tables. This same production database also holds snapshots of the public schema (named public_yyyy_mm_dd based on the date the snapshot was taken). The snapshot schemas basically hold copies of the tables from the public schema, which share names.
When we ran our Tableau ingestion, it seems to have drawn lineage from many dashboards to one of these snapshot schemas, rather than the actual public schema where the dashboards are sourcing their data from. I confirmed that the Tableau metadata API is returning the correct schema, and not the snapshots.
We were able to temporarily fix this on our end by filtering the snapshot schemas from ingestion and removing the previously ingested metadata from our instance of Open Metadata. However, I assume that there could be a case in the future where table names are legitimately shared across schemas (in this case we couldn't just filter our the 'duplicates') and we'd need lineage to be drawn correctly between dashboards.
To Reproduce

Set up a Snowflake database service
Configure ingestion against a Snowflake database with multiple schemas containing identical tables (same column schema, and same name)
In tableau, create a data source that references one of these tables that are identical across these schemas
Create a dashboard that uses the data source created in step 3
Run Open Metadata Tableau ingestion

Expected behavior
Dashboard lineage is drawn to the correct source table in Snowflake
Version:

OS: debian
Python version: 3.9
OpenMetadata version: 0.13.2
OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[tableau]==0.13.2]

Additional context
Add any other context about the problem here.

let's handle this after adding the dataModel changes

This should be fixed by this PR.
@joal-zb could you confirm once the 1.0 version is released? Otherwise, feel free to reopen it. Thank you.


Remove block on hover and focus of Icon Buttons

Fixes issue #123
I checked and didn't see anywhere else where this was needed, so I think this solved the problem.

@mattnickles please review :)


Add aggregation description to BLS document

[ ] Add aggregate_pubkeys function description
[ ] Add aggregate_signatures function description
[ ] Rename bls_verify.md -> bls_signature.md

TBD:

Add more description: BLS signature scheme for Ethereum 2.0: Aggregate and Multi-Signatures based on BLS (Boneh–Lynn–Shacham) over BLS12-381.

Addressed with https://github.com/ethereum/eth2.0-specs/pull/316

closing in favor of #316


Help

@pauldb09

Try to down grade to mongodb v5.3

@pauldb09, please help me.

@pauldb09

@pauldb09 was this solved? Seems like they were left on read a little bit. Lol.

@SpaceLeft Just read the error and do it


Training start date on calendar year

I noticed today that the training start date is at the beginning of the calendar year, not the water year. Seems like it should be the water year
https://github.com/USGS-R/drb-do-ml/blob/43b4277f0fe3ae4d3f61dc8bb48ed5a78b36f456/_targets.R#L91

I'm guessing it doesn't make too much of a difference, but I think it would be good to correct this.

Good point, I have a vague recollection that this date 1980-01-01 is when gridMET data are available. I would have to check if that's true, but could explain why we chose the calendar date start.


raftstore-v2: use snapshot to initialize split

What is changed and how it works?
Issue Number: Ref #12842
What's Changed:
Create a new storage introduces unnecessary complexity and corner cases.
As split is an initialization just like snapshot, this PR reuses snapshot to make
the process a lot simpler and more robust.

Check List
Tests

Unit test
Integration test

Release note
None

PTAL

/merge

/merge


issue with building project

[azureuser@mgt Viya4]$ docker build github.com/sassoftware/viya4-orders-cli -t viya4-orders-cli
unable to prepare context: unable to 'git clone' to temporary context directory: Error trying to use git: exit status 128 (Cloning into '/tmp/docker-build-git267569601'...
git: 'remote-https' is not a git command. See 'git --help'.
)

Hi, what version of Git are you using? Is git-remote-https.exe present in your Git installation?

[azureuser@mgt ~]$ git --version
git version 2.30.0
also from this instruction where I get the 923456_lts_depassets.tgz?
What should I include the configuration file..the API and Scret?
Can you provide a sample yml configuration file?
Using a configuration file, /c/Users/auser/vocli/.viya4-orders-cli.yaml, to convey your API credentials, get deployment assets for SAS Viya order 923456 at the latest version of the Long Term Support (lts) cadence. Send the contents to file /c/Users/auser/vocli/sasfiles/923456_lts_depassets.tgz:
Regards,
Esmat Shabon
Sr. Solution Advisor
Fraud and Security Intelligence
Phone: (<PHONE_NUMBER>
Esmat.shabon<EMAIL_ADDRESS>From: Sarah Page<EMAIL_ADDRESS>Sent: Monday, February 08, 2021 11:24 AM
To: sassoftware/viya4-orders-cli<EMAIL_ADDRESS>Cc: Esmat Shabon<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [sassoftware/viya4-orders-cli] issue with building project (#8)
EXTERNAL
Hi, what version of Git are you using? Is git-remote-https.exe present in your Git installation?

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsassoftware%2Fviya4-orders-cli%2Fissues%2F8%23issuecomment-775265688&data=04|01|esmat.shabon%40sas.com|ce7efaf60e744f7c43cb08d8cc4de693|b1c14d5c362545b3a4309552373a0c2f|0|0|637483982247440016|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=c7TgodG76QxRh9BYHEGERvilEF3mSndQgt2itocn1Go%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAM42JVOWTKOOYYYBK4ST2BDS6AFY3ANCNFSM4XJH3PNQ&data=04|01|esmat.shabon%40sas.com|ce7efaf60e744f7c43cb08d8cc4de693|b1c14d5c362545b3a4309552373a0c2f|0|0|637483982247450014|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=W32pwmRCYCdERReQL89Cdg7tMRfm5OPkR%2Fq4wIK977M%3D&reserved=0.

Is git-remote-https.exe present in your Git installation?
From the README.md on the project homepage in GitHub:

user had bad git installation - closing


Either the assertion indicates an error in the framework itself, or we should provide substantially more information

Reporting this
════════ Exception caught by widgets library ═══════════════════════════════════════════════════════
The following assertion was thrown building Navigator-[GlobalObjectKey<NavigatorState> _WidgetsAppState#414a7](dirty, state: NavigatorState#de1f2(tickers: tracking 3 tickers)):
'package:flutter/src/widgets/navigator.dart': Failed assertion: line 3803 pos 12: '!_debugLocked': is not true.

Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=BUG.md

The relevant error-causing widget was:
  MaterialApp file:///home/myapp/flutter/lib/main.dart:20:12
When the exception was thrown, this was the stack:
#2      NavigatorState.build (package:flutter/src/widgets/navigator.dart:3803:12)
#3      StatefulElement.build (package:flutter/src/widgets/framework.dart:4619:28)
#4      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4502:15)
#5      StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:4675:11)
#6      Element.rebuild (package:flutter/src/widgets/framework.dart:4218:5)
...
════════════════════════════════════════════════════════════════════════════════════════════════════
Reloaded 0 of 705 libraries in 413ms.

Hi @eldarj,
Can you please provide your flutter doctor -v, your flutter run --verbose and a minimal complete reproducible code sample that shows this issue.
Thank you

Without additional information we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Vite-ssg build error in SSR step

Describe the bug
I'm using vue3-carousel in my project and getting following error while building with build script.
[vite-ssg] Build for server...
vite v5.2.11 building SSR bundle for production...
Ambiguous external namespace resolution: "virtual:vue-router/auto" re-exports "useRouter" from one of the external modules "vue-router" and "unplugin-vue-router/data-loaders/basic", guessing "vue-router".
"useRouter" is imported from external module "unplugin-vue-router/data-loaders/basic" but never used in "virtual:vue-router/auto".
✓ 66 modules transformed.
✓ 0 webfont css downloaded. (0 ms, cache hit: NaN%)
.vite-ssg-temp/7un0o79hrz/manifest.webmanifest                         0.39 kB
.vite-ssg-temp/7un0o79hrz/assets/style-EG92fjKA.css                   35.60 kB
.vite-ssg-temp/7un0o79hrz/assets/route-block-mFfs_uHM.js               0.05 kB
.vite-ssg-temp/7un0o79hrz/assets/en-DrlAedJ-.js                        1.14 kB
.vite-ssg-temp/7un0o79hrz/assets/tr-BgRAO5hH.js                        1.16 kB
.vite-ssg-temp/7un0o79hrz/assets/_...all_-Emgd7hKA.js                  1.19 kB
.vite-ssg-temp/7un0o79hrz/assets/virtual_pwa-register-MFElTJ3Z.js      1.45 kB
.vite-ssg-temp/7un0o79hrz/assets/workbox-window.prod.es5-BZWEBaKl.js   8.18 kB
.vite-ssg-temp/7un0o79hrz/assets/index-BkKP3A0x.js                    43.61 kB
.vite-ssg-temp/7un0o79hrz/main.mjs                                    78.91 kB
✓ built in 452ms
file:///Users/ademtonay/Projects/kt-dent/.vite-ssg-temp/7un0o79hrz/assets/index-BkKP3A0x.js:4
import { Carousel, Navigation, Pagination, Slide } from "vue3-carousel";
         ^^^^^^^^
SyntaxError: The requested module 'vue3-carousel' does not provide an export named 'Carousel'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:134:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:217:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)

[vite-ssg] An internal error occurred.
[vite-ssg] Please report an issue, if none already exists: https://github.com/antfu/vite-ssg/issues
file:///Users/ademtonay/Projects/kt-dent/.vite-ssg-temp/7un0o79hrz/assets/index-BkKP3A0x.js:4
import { Carousel, Navigation, Pagination, Slide } from "vue3-carousel";
         ^^^^^^^^
SyntaxError: The requested module 'vue3-carousel' does not provide an export named 'Carousel'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:134:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:217:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)

Node.js v20.13.1
 ELIFECYCLE  Command failed with exit code 1.

Reproduction
none
System Info
System:
    OS: macOS 14.4.1
    CPU: (10) arm64 Apple M2 Pro
    Memory: 619.52 MB / 16.00 GB
    Shell: 3.6.1 - /opt/homebrew/bin/fish
  Binaries:
    Node: 20.13.1 - /opt/homebrew/opt/node@20/bin/node
    npm: 10.2.5 - /usr/local/bin/npm
    pnpm: 9.1.1 - ~/Projects/kt-dent/node_modules/.bin/pnpm
  Browsers:
    Chrome: 124.0.6367.209
    Safari: 17.4.1

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Contributions

[ ] I am willing to submit a PR to fix this issue
[ ] I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)

same error here.

I solved the issue by downgrade vite packages from:
   "vite": "^5.2.11",
    "vite-bundle-visualizer": "^1.2.1",
    "vite-plugin-inspect": "^0.8.4",
    "vite-plugin-pwa": "^0.20.0",
    "vite-plugin-vue-devtools": "^7.1.3",
    "vite-plugin-vue-layouts": "^0.11.0",
    "vite-plugin-webfont-dl": "^3.9.4",
    "vite-ssg": "^0.23.7",
    "vite-ssg-sitemap": "^0.6.1",
    "vitest": "^1.6.0",

to:
    "vite": "5.0.3",
    "vite-bundle-visualizer": "0.11.0",
    "vite-plugin-inspect": "0.7.42",
    "vite-plugin-pwa": "0.17.2",
    "vite-plugin-vue-devtools": "1.0.0-rc.5",
    "vite-plugin-vue-layouts": "0.8.0",
    "vite-plugin-webfont-dl": "3.9.1",
    "vite-ssg": "0.23.5",
    "vite-ssg-sitemap": "0.6.1",
    "vitest": "1.0.0-beta.6"

Note: It's just a workaround

Thank you so much it worked! @ademtonay

I am running into the same issue except downgrading packages is not fixing it for me.

I also encountered the same problem, my vite version is 5.3.1。

I solved the problem for me by downgrading "vue3-carousel" (from 0.3.3) by adding the following dependency:
"vue3-carousel": "0.3.1"

Hey @muckch ,  I'm gonna try this too thanks.


Kisa connect not working with Android 14, see here for more details https://discord.com/channels/956182090964152390/956187012333969479/1319443022902988810

KisaPilot Connect can no longer run correctly when in the background on Android 14, even with "Unrestricted" background battery usage. When something else is in the foreground (for example: Waze), Developer options -> Running services -> ... -> Show cached processes -> KisaPilot Connect will show as "Cached background process".
Test info:
Device: Pixel 5a
OS: Android 14
Root: Yes
Disabled: Battery Saver, Battery Manager
Enabled on KisaPilot Connect: Allow background usage, Unrestricted background usage
Suggestion: Creating a foreground service for the KisaPilot Connect app.


Nice crappy bugged lib

Even the simplest example fails miserably.....

After line 88, try adding:
stream.Position = 0;


Installation failed while using vagrant

Background:
Installation on Windows 10, laptop, HP, core i7, 16 GB memory
Virtual box version 6.0.6
Vagrant version 2.2.4
Date: 05/13/2019
Problem:
while installing via 'vagrant up' , the installation fails while installing nat vm because of cni version mismatch. The log display is mentioned here.
deployment_logs.zip
`    k86-nat64: Fetched 110 kB in 1s (87.8 kB/s)
k86-nat64: Reading package lists...

k86-nat64: + echo 'Installing Kubernetes Components...'
k86-nat64: Installing Kubernetes Components...
k86-nat64: + sudo -E apt-get install -qy --allow-downgrades kubelet=1.10.5-00 kubectl=1.10.5-00 kubeadm=1.10.5-00
k86-nat64: Reading package lists...
k86-nat64: Building dependency tree...
k86-nat64: Reading state information...
k86-nat64: Some packages could not be installed. This may mean that you have
k86-nat64: requested an impossible situation or if you are using the unstable
k86-nat64: distribution that some required packages have not yet been created
k86-nat64: or been moved out of Incoming.
k86-nat64: The following information may help to resolve the situation:
k86-nat64: The following packages have unmet dependencies:
k86-nat64:  kubelet : Depends: kubernetes-cni (= 0.6.0) but 0.7.5-00 is to be installed
k86-nat64: E
k86-nat64: :
k86-nat64: Unable to correct problems, you have held broken packages.

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
`

It was a problem with the Kubernetes version, as this was written a while back and it still uses 1.10.5 K8s version and today 1.14 is out. I specified the K8s version in 'Vagrantfile' to
env['KUBERNETES_VERSION'] = env['KUBERNETES_VERSION'] || "1.14.0"
but after i did cleanup and restarted the ./vagrant-start ... it picked up the 1.10.5 version again, may be from the clone which was downloaded already?
However, I fixed it by changing it in provision_every_node.sh variable directly to
k8s_version="1.14.0"


Platform-specific Gems not found in vendor/cache

We have a dependency on google-protobuf, which has platform-specific gems for linux, macOS, and ruby. We also bundle package our gems so we can deploy w/o needing to hit RubyGems while building our images. We've attempted to configure bundler to cache all specified platform-specific gems so they're also updated via a bundle update.
The initial bundle install works as expected - installs the gem and updates ./vendor/cache. But subsequent bundle install, bundle package, and other commands fail with Could not find <GEM> in any of the sources. Interestingly, subsequent bundle update works as expected.
Minimal set of steps to reproduce
mkdir bundle_platform_error && cd bundle_platform_error

bundle init
bundle package

At this point we have an empty ./vendor/cache and pretty much bare Gemfile.lock. Next we configure Bundler to cache all platform gems:
bundle config --local specific_platform true && \
  bundle config --local cache_all_platforms true

bundle lock --add-platform x86_64-linux
bundle lock --add-platform x86_64-darwin-18

cat Gemfile.lock
#=> GEM
#=>   specs:
#=>
#=> PLATFORMS
#=>   ruby
#=>   x86_64-darwin-18
#=>   x86_64-linux
#=>
#=> DEPENDENCIES
#=>
#=> BUNDLED WITH
#=>    2.0.1

Then, to make sure things work as expected, we add a non-platform specific gem:
echo 'gem "dumb_delegator"' >> Gemfile

bundle
#=> Fetching gem metadata from https://rubygems.org/.
#=> Resolving dependencies...
#=> Using bundler 2.0.1
#=> Using dumb_delegator 0.8.0
#=> Updating files in vendor/cache
#=>   * dumb_delegator-0.8.0.gem
#=> Bundle complete! 1 Gemfile dependency, 2 gems now installed.
#=> Use `bundle info [gemname]` to see where a bundled gem is installed.

bundle
#=> Using bundler 2.0.1
#=> Using dumb_delegator 0.8.0
#=> Updating files in vendor/cache
#=> Bundle complete! 1 Gemfile dependency, 2 gems now installed.
#=> Use `bundle info [gemname]` to see where a bundled gem is installed.

All works well. The initial bundle install installed and cached the gem. A subsequent bundle install used the existing install gems and updated the cache. Now we add a platform-specific gem:
echo 'gem "google-protobuf"' >> Gemfile

bundle
#=> Fetching gem metadata from https://rubygems.org/.
#=> Resolving dependencies...
#=> Using bundler 2.0.1
#=> Using dumb_delegator 0.8.0
#=> Using google-protobuf 3.7.1 (universal-darwin)
#=> Updating files in vendor/cache
#=> Fetching google-protobuf 3.7.1
#=>   * google-protobuf-3.7.1.gem
#=>   * google-protobuf-3.7.1-universal-darwin.gem
#=> Fetching google-protobuf 3.7.1 (x86_64-linux)
#=>   * google-protobuf-3.7.1-x86_64-linux.gem
#=> Bundle complete! 2 Gemfile dependencies, 3 gems now installed.
#=> Use `bundle info [gemname]` to see where a bundled gem is installed.

cat Gemfile.lock
#=> GEM
#=>   remote: https://rubygems.org/
#=>   specs:
#=>     dumb_delegator (0.8.0)
#=>     google-protobuf (3.7.1)
#=>     google-protobuf (3.7.1-universal-darwin)
#=>     google-protobuf (3.7.1-x86_64-linux)
#=>
#=> PLATFORMS
#=>   ruby
#=>   x86_64-darwin-18
#=>   x86_64-linux
#=>
#=> DEPENDENCIES
#=>   dumb_delegator
#=>   google-protobuf
#=>
#=> BUNDLED WITH
#=>    2.0.1

That worked. All three versions of the gem were cached, and our specific platform (macOS) was installed and used. Now we'll bundle install again and we expect a noop.
bundle
#=> Using bundler 2.0.1
#=> Using dumb_delegator 0.8.0
#=> Using google-protobuf 3.7.1 (universal-darwin)
#=> Updating files in vendor/cache
#=> Could not find google-protobuf-3.7.1 in any of the sources

It errors (with a return code of 7), warning "Could not find  in any of the source. However, we can verify the gems are in the ./vendor/cache:
tree vendor/cache
#=> vendor/cache
#=> ├── dumb_delegator-0.8.0.gem
#=> ├── google-protobuf-3.7.1-universal-darwin.gem
#=> ├── google-protobuf-3.7.1-x86_64-linux.gem
#=> └── google-protobuf-3.7.1.gem
#=>
#=> 0 directories, 4 files

Interestingly a bundle update at this point does work, and exits happily:
bundle update
#=> Fetching gem metadata from https://rubygems.org/.
#=> Resolving dependencies...
#=> Using bundler 2.0.1
#=> Using dumb_delegator 0.8.0
#=> Using google-protobuf 3.7.1 (universal-darwin)
#=> Updating files in vendor/cache
#=> Bundle updated!

But subsequent command, like bundle install and bundle package (at least), fail:
bundle
#=> Using bundler 2.0.1
#=> Using dumb_delegator 0.8.0
#=> Using google-protobuf 3.7.1 (universal-darwin)
#=> Updating files in vendor/cache
#=> Could not find google-protobuf-3.7.1 in any of the sources

bundle package
#=> Using bundler 2.0.1
#=> Using dumb_delegator 0.8.0
#=> Using google-protobuf 3.7.1 (universal-darwin)
#=> Updating files in vendor/cache
#=> Could not find google-protobuf-3.7.1 in any of the sources

Next steps?
I'm not sure where to take it from here. I doubt this is expected behavior, but would like to confirm.
Environment
Bundler       2.0.1
  Platforms   ruby, x86_64-darwin-18
Ruby          2.6.2p47 (2019-03-13 revision 67232) [x86_64-darwin18]
  Full Path   /Users/sharman/.rbenv/versions/2.6.2/bin/ruby
  Config Dir  /Users/sharman/.rbenv/versions/2.6.2/etc
RubyGems      3.0.3
  Gem Home    /Users/sharman/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0
  Gem Path    /Users/sharman/.gem/ruby/2.6.0:/Users/sharman/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0
  User Path   /Users/sharman/.gem/ruby/2.6.0
  Bin Dir     /Users/sharman/.rbenv/versions/2.6.2/bin
Tools
  Git         2.21.0
  RVM         not installed
  rbenv       rbenv 1.1.1
  chruby      not installed

Bundler Build Metadata
Built At          2019-01-04
Git SHA           d7ad2192f
Released Version  true

Bundler settings
console
  Set for the current user (/Users/sharman/.bundle/config): "pry"
gem.mit
  Set for the current user (/Users/sharman/.bundle/config): true
gem.test
  Set for the current user (/Users/sharman/.bundle/config): "rspec"
gem.coc
  Set for the current user (/Users/sharman/.bundle/config): false
specific_platform
  Set for your local app (/Users/sharman/code/bundle_platform_error/.bundle/config): true
cache_all_platforms
  Set for your local app (/Users/sharman/code/bundle_platform_error/.bundle/config): true

Possibly Related Issues?
I've seen several other Issues reported, all seemingly around the area of package-specific gems. Perhaps related? Perhaps not. They are:

https://github.com/bundler/bundler/issues/5989
https://github.com/bundler/bundler/issues/6606
https://github.com/bundler/bundler/issues/6610

It seems this is caused by the version specific to the development platform being installed on the local machine, and the generic version as well as all other platform specific versions not being installed.
bundle package then cannot resolve the Gem since it only tries the installed Gems. I'm not sure on what to do here. A quick fix would be to resolve all Gems remotely when running bundle package.
If someone points me in the right direction, I'm willing to create a patch.

I posted a workaround here, in case it helps.


terminus wp media import --post_id does not pass the post_id correctly to wp-cli

Hi!
Ok, I'm not entirely sure this is a terminus problem. I'll report it here but if it's deemed to be wp-cli issue, close it.
When I execute the command:
$ terminus wp media import https://farm8.staticflickr.com/7552/15827270506_ce62e709c9_o_d.jpg --post_id=1 --featured_image --site=cli-6
Running wp media import https://farm8.staticflickr.com/7552/15827270506_ce62e709c9_o_d.jpg --post_id=1 --featured_image=1  on cli-6-dev
Warning: --post_id parameter needs a value
Success: Imported file https://farm8.staticflickr.com/7552/15827270506_ce62e709c9_o_d.jpg as attachment ID 14.

Notice the warning. Yes, it imports the image but it does not pick up the post_id.
This however, works:
$ terminus wp media import https://farm8.staticflickr.com/7552/15827270506_ce62e709c9_o_d.jpg --post_id=\"1\" --featured_image --site=cli-6

Notices the escaped quotes around the 1.
I tested it with wp-cli directly on my personal server and a test site and wp-cli works without the quotes.
 $ /usr/local/bin/wp-cli.phar media import https://farm8.staticflickr.com/7552/15827270506_ce62e709c9_o_d.jpg --post_id=1 --featured_image

I'm not even sure where to start looking for this one. It does however look like we are passing something in that wp-cli doesn't like. Possibly cast it as (int) before building the command? Trim it because there is something we can't see appended to it?  Dunno.
Cheers!
=C=

Smells like an issue with how we are wrapping/escaping things. It might be a bit of a dive to debug, but we should try to get to it before more users do.
Could be the same issue with Drush too.

@calevans did you try putting quotes around the image url?

Good idea. didn't work, but no, I did not try that. Just did now, same output as before.
/Users/cal$ terminus wp media import "https://farm8.staticflickr.com/7355/16204225167_1e1bb198e5_b.jpg" --post_id=1 --featured_image --site=cli-test
Running wp media import https://farm8.staticflickr.com/7355/16204225167_1e1bb198e5_b.jpg --post_id=1 --featured_image=1  on cli-test-dev
Warning: --post_id parameter needs a value
Success: Imported file https://farm8.staticflickr.com/7355/16204225167_1e1bb198e5_b.jpg as attachment ID 6.

Cheers!
=C=

@calevans I think this has been fixed with #288


Broken link for performance guide

The link to the performance guide in Resources>Overview is broken. It’s now at https://haskell.foundation/hs-opt-handbook.github.io/

Thanks so much! Now fixed! Note that you can propose edits directly with the edit button on the top right of each page.

HI Reuben. I just forked the repo so can now do pull requests. Before making a PR, just wanted to ask a couple of questions.  First, since the Books section is only a section, would you want to add a link to Travis Cardwell's comprehensive list? Second, would it be ok to add an additional book or two (I really like Rebecca Skinner's Effective Haskell)? And if so, is your preference for the Amazon link or for the publisher web site (Pragmatic has the full table of contents, pdf excerpts, and code)?

Thanks for asking! I'm trying to avoid being comprehensive, and instead giving opinionated choices (see "less > more" here: https://github.com/reubenharry/haskell-docs/blob/main/Contributing.md). I also try to only mention free resources (in the interest of miminizing effort/commitment required for a newcomer) so this is why I didn't include non-free books. But that said, I'd be in favour of adding Effective Haskell (the publisher web site link) if you think it's a worthwhile book for beginners/intermediates. You could add it under a "Paid Resources" section, or similar.
(Also note that for quick changes, you don't even need to fork, you can just make PRs online (with the edit button as mentioned above). But of course for anything substantial, forking is the way.)


ARTEMIS-718 - AMQP type message bodies are being lost

https://issues.apache.org/jira/browse/ARTEMIS-718

dont merge this yet

@andytaylor it looks good. Why not merge yet. tests are failing?

its fine to merge now

@andytaylor looks like this failed again.  Could you take a look

@mtaylor doesn't seem related to his changes

I'm running the testsuite manually. if all ok I will merge this.


Add --rm flag to kubectl debug to remove debug pod on exit

What would you like to be added:
I would like to add the --rm flag to kubectl debug, similar to the flag in kubectl run and docker run, which allows automatic deletion of the debug pod upon exit. Since ephemeral containers cannot be removed, this flag would only apply when debugging a node or a pod with --copy-to.
I have already opened a PR for this feature, as its implementation is small:
https://github.com/kubernetes/kubernetes/pull/129046
Why is this needed:
kubectl debug -it node is very useful replacement for ssh, but I often forget to remove completed debug pods. These completed pods are generally not useful, and even the official documentation includes a step for "Cleaning up".
$ kubectl get pods
NAME                           READY   STATUS      RESTARTS   AGE
node-debugger-minikube-4gq42   0/1     Completed   0          74s
node-debugger-minikube-8xrvr   0/1     Completed   0          31s
node-debugger-minikube-hscjt   0/1     Completed   0          20s
..

Although at first sight it looks reasonable, each new flag puts kubectl debug under a risk of unusability that kubectl run already experiences due to plenty of flags. As already stated in the description, this new flag won't work on ephemeral containers anyway. In my opinion, hurting the usability for a new flag far outweighs the benefits we get and we should be reluctant to add this flag.

Hi, I understand that we should be cautious about adding flags. What do you think about adding a specific label to debug pods instead of introducing a flag? This would at least make cleaning up debug pods easier.


Support scoped modules

Node-red doesn't appear to have the ability to pick up scoped modules installed to $HOME/.node-red which are installed with a parent directory named after the module scope (i.e. node_modules/@myscope/my-node instead of just node_modules/my-node). Are there any workarounds for nodes that are published to private registries under a package scope? Would it be possible to modify the lookup code to peek inside any directories beginning with @ and include nodes found in there?

+1
http://stackoverflow.com/questions/37058267/private-npm-modules-installed-via-package-json-without-a-parent-directory/37058998#37058998

A workaround we used for scoped modules was to have node-red embedded into an express app, then pass the "nodesDir" setting pointing to the installed node_modules/@scope folder, when doing RED.init(server,settings). All the nodes are then installed through the package.json of the express app.
http://nodered.org/docs/embedding

tried out 0.14.0 branch and get TypeError with installed scoped package - package works fine without scope in name of package.json - did I need some more to configure in the package.json?
TypeError: Cannot read property 'nodes' of undefined
at Object.getAllNodeConfigs [as getNodeConfigs] (/node-red/red/runtime/nodes/registry/registry.js:382:54)
at module.exports.getAll (/node-red/red/api/nodes.js:39:31)
at Layer.handle [as handle_request] (/node-red/node_modules/express/lib/router/layer.js:95:5)
at next (/node-red/node_modules/express/lib/router/route.js:131:13)
at /node-red/red/api/auth/index.js:63:13
at Layer.handle [as handle_request] (/node-red/node_modules/express/lib/router/layer.js:95:5)
at next (/node-red/node_modules/express/lib/router/route.js:131:13)
at Route.dispatch (/node-red/node_modules/express/lib/router/route.js:112:3)
at Layer.handle [as handle_request] (/node-red/node_modules/express/lib/router/layer.js:95:5)
at /node-red/node_modules/express/lib/router/index.js:277:22
at Function.process_params (/node-red/node_modules/express/lib/router/index.js:330:12)
at next (/node-red/node_modules/express/lib/router/index.js:271:10)
at urlencodedParser (/node-red/node_modules/body-parser/lib/types/urlencoded.js:88:40)
at Layer.handle [as handle_request] (/node-red/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/node-red/node_modules/express/lib/router/index.js:312:13)
at /node-red/node_modules/express/lib/router/index.js:280:7

Ah... you found a deficiency in my testing. Will take another look.

With this commit 9e26aeea1dc80a6c670f6f99ba9def9700bf7205 the 0.14.0 branch should now properly handle scoped modules

very well - Thank you!


FEATURE REQ: Patch added.

Hello dear Ghost. I dont know How hard it is or if it is possible but It would be nice if on the mouse over tooltip info, there would be a line for Added in Patch: X.y.z
Thanks :)

Shall i remove this req?

Yeah I don't think this is something feasible for me to implement right now - might revisit in the future


The difference between KeyList and ThresholdKey is ambiguous and poorly documented

At some point, the decision was made to combine KeyList and ThresholdKey objects, such that if a threshold value is set, then a ThresholdKey protobuf is produced, otherwise producing a KeyList protobuf
This invites misuse: a KeyList is intended to have specialized behavior related to files. It isn't just a ThresholdKey where N of N keys are required to sign.

If a developer wants the special KeyList behavior, but sets a threshold value without understanding the implications, they might not know that suddenly they no longer have a KeyList at all
If a developer doesn't know anything about the specialized file related behavior of a KeyList, and assumes setting no threshold == requiring N of N signatures (logical, IMO), they could get be blindsided by specialized KeyList behavior

Possible solution: deprecate all functions in KeyList that have to do with a threshold, and create a new ThresholdKey object which does what a ThresholdKey is supposed to do

Skyler has pointed out that this would be a breaking change, since converting a protobuf to a KeyList / ThresholdKey would yield a different object type, if ThresholdKey becomes a separate object.


chore: make struct comments match struct names

Description

make struct comments match struct names
Motivation and context

How has this been tested?

Screenshots (if appropriate):
Checklist:

[ ] I followed the contributing guidelines and code of conduct.
[ ] I have added a relevant changelog to CHANGELOG.md
[ ] I have added tests to cover my changes.
[ ] I have updated the documentation accordingly.
[ ] I have updated API documentation client/docs/swagger-ui/swagger.yaml

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

Thank you for your interest and corrections. However, simple typo correction PRs are not accepted.


Incorrect header left padding in What's New and All controls pages

Describe the bug
The header left padding is too small in What's New and All controls pages.
Screenshots

Version Info

Gallery version (found on Settings page):
<IP_ADDRESS>
Windows 10 version:

[ ] Insider Build (xxxxx)
[ ] May 2020 Update (19041)
[x] November 2019 Update (18363)
[ ] May 2019 Update (18362)
[ ] October 2018 Update (17763)
[ ] April 2018 Update (17134)
[ ] Fall Creators Update (16299)
[ ] Creators Update (15063)
[ ] Anniversary Update (14393)

Device form factor:

[x] Desktop
[ ] Mobile
[ ] Xbox
[ ] Surface Hub
[ ] IoT

Additional context

Thanks for filing this issue. I believe that this was fixed with the new update :)


Resolves a couple of open issues

Let me know if you have any concerns. Assuming this hasn't diverged too far from master/trunk, should be ready to go for merge.

Renamed the WIN files as MK files
Handles known local SVN concerns
Working around NMAKE/MAKE collisions for now
Made a couple of attempts at resolving AssemblyInfo: methinks this is likely just the way it is, but am still interested to see the info from Explorer File Info
Last but not least, culminating in NuGet packaging/delivery: there was some confusion in the naming of the package, but I also took the opportunity to separate out some logical targets, as well as for the FlatZinc sub-project

@lperron My mistake. I will submit a correction ASAP. Thanks!

--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/google/or-tools/pull/333#pullrequestreview-25477530

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

@lperron Okay, what is the purpose of the CSHARPEXE variable? It seems to be there only to serve the csharpexe target?
 Are you saying that .exe should happen for *nix as well?

Renaming these was intentional. These are critical for proper comparison:
makefiles/Makefile.third_party.unix
makefiles/Makefile.third_party.win

Otherwise, diff tools thinks they are images, not text.

@lperron Additionally, so FlatZinc is not ready for publishing, either? It's an interesting approach.

Closing this one. Will re-submit.

@lperron There is also value in separating the nuget targets, for OrTools, and for FlatZinc: 1) staging, 2) packing, and 3) distribution. This is because, for folks like me, we like to sometimes stage our package to local repositories for test purposes. And with the make target chaining, it is trivial to reconstruct a target in your CI.


Can Unbox perform object to json as well?

Does Unbox supports object serialization to json?

just found Wrap


[v8 and v9] issue: uninstalling packages with Doctrine classes doesn’t refresh the others

If I uninstall a package with Doctrine classes, other Doctrine entities from other installed packages with Doctrine classes don’t get refreshed or get removed from somewhere wherever they sit. After uninstalling any such package with Doctrine and visiting any page other entities are used I get:
require(/srv/www/htdocs/c9/application/config/doctrine/proxies/__CG__OtherPackageDoctrineClassName.php): failed to open stream: No such file or directory
Refreshing the entities in System & Settings > Environment > Database Entities > Refresh Entities fixes the problem. Shouldn't that happen automatically during the package uninstall?
Having the "On - Proxy classes will be generated on the fly. Good for development." option set in System & Settings > Environment > Database Entities > Settings > Doctrine Development Mode also fixes the issue. Although that's great for development, normal users may not have that option enabled and will always get the error.
Refreshing entities on package uninstall doesn't help:
$em = DatabaseORM::entityManager();
$manager = $this->app->make(DatabaseStructureManager::class, ['em' => $em]);
$manager->refreshEntities();

Proxy classes are refreshed during uninstall:
https://github.com/concrete5/concrete5/blob/develop/concrete/src/Package/Package.php#L633
So I'm not sure what's going on here

That problem is actually not only with installed packages but any packages in the packages folder regardless if they are installed or not. So:

Install a package with Doctrine classes
Install another package with Doctrine classes
Uninstall any package with Doctrine classes
Go to any page using any installed package with Doctrine classes - get the error
Try to install any package with Doctrine classes - get the error
Either refresh entities or set the entities development mode - do whatever and get no errors

Proxy classes are refreshed during uninstall:
https://github.com/concrete5/concrete5/blob/develop/concrete/src/Package/Package.php#L633
So I'm not sure what's going on here

@aembler , isn't that the source of the problem - that line destroys the entities thus they have to be manually refreshed/rebuilt. Commenting out that line fixes the problem! Without 'destroyProxyClasses' uninstalling the packages and doing whatever with the others don't result in the error.

If you add
        $dbm = new DatabaseStructureManager($em);
        $dbm->destroyProxyClasses();

immediately before the uninstall
and then add
        $dbm->generateProxyClasses();

after the uninstall does it fix your problem?

@aembler , do you mean to add those in package controllers?

I mean add it to the core to test and see if it fixes the problems that you're describing. I haven't seen these problems so it's difficult for me to test.

The Package has its own destroyProxyClasses. And that's what it does on line 633 - it destroys all classes. The DatabaseStructureManager's destroyProxyClasses($prefix = null) needs the prefix and only destroys a single class.
But there's no generateProxyClasses in the Package. It's only in the DatabaseStructureManager and generateProxyClassesFor(array $metadatas) needs the metadatas. Where do I get it?

I don't think destroyProxyClasses only destroys a single class.
I'm just trying to copy useful code that we've used elsewhere to try and solve this problem. It's very possible that the package specific proxy class destruction code is unnecessary for the very reasons you've outlined – it'd be better to just destroy and regenerate all proxy classes every time a package is uninstalled. That's what I'm hoping you'll be able to test.

Do you want me to add the above first 2 lines in the Package uninstall() as first lines and the other one as the last?

I don't think destroyProxyClasses only destroys a single class.

Sorry, I'll rephrase it. Yes, that destroys multiple classes but with a single prefix. What should that prefix be? What if I have different prefixes, does it mean I have to do that multiple times for all used prefixes?

In destroyProxyClasses($prefix = null) the $prefix argument is optional. Have you tried to omit it?

I added
$metadata = $em->getMetadataFactory()->getAllMetadata();
$dbm = new DatabaseStructureManager($em);
$dbm->generateProxyClasses($metadata);

after line 638 in Package and that seems to have fixed the problem.

Should I generateProxyClasses or refreshEntities or both or neither in my packages during their install/upgrade/uninstall?


Allow not preventing default event behaviors on wasm

Objective
On wasm, bevy applications currently prevent any of the normal browser hotkeys from working normally (Ctrl+R, F12, F5, Ctrl+F5, tab, etc.).
Some of those events you may want to override, perhaps you can hold the tab key for showing in-game stats?
However, if you want to make a well-behaved game, you probably don't want to needlessly prevent that behavior unless you have a good reason.
Secondary motivation: Also, consider the workaround presented here to get audio working: https://developer.chrome.com/blog/web-audio-autoplay/#moving-forward ; It won't work (for keydown events) if we stop event propagation.
Solution

Winit has a field that allows it to not stop event propagation, expose it on the window settings to allow the user to choose the desired behavior. Default to true for backwards compatibility.

Changelog

Added Window::prevent_default_event_handling . This allows bevy apps to not override default browser behavior on hotkeys like F5, F12, Ctrl+R etc.

bors r+


fix: Remove BOM for Avacodo errors

Used this to remove the BOMs
find . -type f -iname "*.json" -exec node -e "var f = process.argv[1]; var contents = fs.readFileSync(f, 'utf8'); if (contents.charCodeAt(0) === 0xFEFF) { fs.writeFileSync(f, contents.slice(1), 'utf8'); } " \{\} \;

I did find that replacing the . with specific folders was needed given the amount of files

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

Automation for azure-sdk-for-java

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python
This PR contains more than 3 context, SDK generation is not enabled. Contexts found:

EnterpriseKnowledgeGraph/resource-manager
sql/resource-manager
azsadmin/resource-manager/backup/Microsoft.Backup.Admin
cognitiveservices/data-plane/CustomVision/Training
cognitiveservices/data-plane/CustomVision/Prediction

Automation for azure-sdk-for-js
This PR contains more than 3 context, SDK generation is not enabled. Contexts found:

cognitiveservices/data-plane/CustomVision/Prediction
azsadmin/resource-manager/backup/Microsoft.Backup.Admin
EnterpriseKnowledgeGraph/resource-manager
cognitiveservices/data-plane/CustomVision/Training
sql/resource-manager

@sergey-shandar does Avocado complain about BOM?

@jhendrixMSFT you get messages like this
code: JSON_PARSE
message: The file is not valid JSON file.
error:
  kind: syntax
  code: invalid symbol
  position:
    line: 1
    column: 1
  token: "\uFEFF"
  message: "invalid symbol, token: \uFEFF, line: 1, column: 1"
  url: >-
    /Users/nschonni/Documents/github/azure-rest-api-specs/specification/EnterpriseKnowledgeGraph/resource-manager/Microsoft.EnterpriseKnowledgeGraph/preview/2018-12-03/EnterpriseKnowledgeGraphSwagger.json


Fix msrvs

Objective
The rust-versions are out of date.
Fixes #17008
Solution
Update the values
Cherry-picked from #17006 in case it is controversial
Testing
Validated locally and in #17006

I can remove the one for input_focus if you want @alice-i-cecile


Vehicle_Calibration

Hello there,
I am using the vehicle calibration procedure to obtain my personal "control_conf.pb.txt" (please refer to this link). What is obscure to me is the methodology behind its creation. As far as I understood, I am supposed to give commands "acceleration, speed limit, deceleration" after running
python modules/tools/calibration/data_collector.py. I have two questions mainly:

What is the way to select reasonable values for the above variables?
It is mentioned in your guide that I am supposed to run each command multiple times. What does it mean? Why?

Thanks for the attention.

I have same questions, do you know the answers now?
Apollo 3.5.0

The calibration table is speed   gas/brake ratio  acceleration   so you need to speed up and down in different acceleration. then you can get the relationship of three value. ——Reply reference comes from the Apollo developer community issue master contest https://apollo.auto/developer/questiondata_cn.html?target=632


Fix form field dragging bug

This has been partially fixed. Form field dragging bug goes away after first field drag action.

this has been fixed permanently


Remove unused imports and exports

Well, I finished my rewrite of Koa (I know how it works now!) and I saw that there were some code that are not used. I could be wrong (too much hours rewriting this) but I don't think so... :P

thanks!


[TODO] Fix the error in InsertOlympusWrapper after updating to CIRCT(ccd8f90a8c79741f270ac542e93979b9d1d0b15e)

LLVM ERROR: can't create type 'mlir::LLVM::LLVMPointerType' because storage uniquer isn't initialized: the dialect was likely not loaded, or the type wasn't added with addTypes<...>() in the Dialect::initialize() method.

Most likely, it's because of Line 432 in InsertOlympusWrapper.cpp. The creation of LLVM::PinterType looks weird, I don't remember why I did this. Need more investigation

It turns out that in Pass definition of InsertOlympusWrapper, the LLVM dialect is not in the dependentDialects list. Adding LLVM into it fixed the error.

Besides, there are errors about the creation of ops, which are:

LLVM::AllocaOp in InsertOlympusWrapper and DfgToLLVM: add element type to the arguments
LLVM:LoadOp in DfgToLLVM(Line 283): the load type was always I64, which led to errors in created cf.br if the required type is not.
For InsertOlympusWrapper we need to allow that dfg.loop can be not the first op inside a ProcessOp.
These are all fixed in the following commits.


Model Loading through file path

@ZhangGe6  thansk for sharing the awesome work !! i have few queries

is there any way we can load the model from a file path instead of gui's open file dialog box ?
I tried to modify the source code with other libraries imports the web ui is crashing with giving any error , can you let us knw how to add it so that we can expand the existing code base with other features "const fs = require('fs'); "
Thanks in advances

@abhigoku10 Loading model from file path is not supported now. Can you share what the motivation/benefit is to do so?

@ZhangGe6  thansk for the response , we are trying to add a model operations in python part of the existing code base where graph needs to be transfered from python to java module but we end having error at transfering and loading . Is there any option to do this functionality ?

@abhigoku10 Transfering data from Python to Java is not supported yet. I am not familiar with this field, so I am afraid I can't provide useful advice.


Add Battle for Evermore to Game list

Update ReadMe.md to include Battle for Evermore game from Mud.xyz.

Looks like I missed this previously, but it also seems like mud.xyz and this game are no more. If there is an updated link, please share it!


Event tracking rev 2

https://user-images.githubusercontent.com/35935196/169381648-481196d0-1077-4909-9d00-c89f1130a8f6.mp4

@alis-khadka this is targeting the wrong branch. Currently its targeting RC -- it should target master (and you should remove the commits from your previous feature which we tabled)


⚠ Ion has degraded performance

In ac84bad, Ion (https://ion.tjhsst.edu) experienced degraded performance:

HTTP code: 200
Response time: 2871 ms

Resolved: Ion performance has improved in a96e68a.


[DC-1811] circleci image update

* update circleci docker image tag.  previous image was deprecated
* attempting to get google sdk to install without using repos
* forced to install google-cloud-sdk without apt, as it isn't in the new image yet
* source the gcloud tools before use
* changing " to ' for setting path variable

closing this PR.  some of this will be handled by DC-1820.


Add Rain Finance Token

{
"chainId": 101,
"address": "23GYXSNdxZi47QLY3c7iG6Q5g6heqWRReuNnAqdDiRfB",
"symbol": "RFT",
"name": "Rain Finance",
"decimals": 9,
"logoURI": "https://raw.githubusercontent.com/solana-labs/token-list/main/assets/mainnet/rain logo.jpg",
"tags": [
"utility-token",
"community-token"
],
"extensions": {
"instagram": "https://instagram.com/rainfinance.rft",
"telegram": "https://t.me/rainfinance",
"twitter": "https://twitter.com/rain_finance",
"website": "https://rainfinance.io/"
}
},

I can help refer this https://github.com/zakimzf/profile/pull/1
PS: If you dont need my help..then please ignore this!