mix plugin does not show phoenix commands

After the last update the mix plugin does not show the phoenix tasks.
My zsh version: zsh 5.2 (x86_64-apple-darwin15.0.0), installed via brew
My installation (done via: antigen):
antigen use oh-my-zsh

antigen bundles <<EOBUNDLES
  git
  brew
  django
  osx
  python
  mix

  # Custom:
  sobolevn/git-secret
EOBUNDLES

antigen theme obraun

antigen apply

These tasks can be found in mix --help output. Double checked that. My mix [TAB] output:
[11:49:21] sobolev :: MacBook-Pro-Nikita  ➜  Documents/elixir/elixir_lang_moscow » mix
--help             -- Describe available tasks
--version          -- Prints the Elixir version information
app.start          -- Start all registered apps
archive            -- List all archives
archive.build      -- Archive this project into a .ez file
archive.install    -- Install an archive locally
archive.uninstall  -- Uninstall archives
clean              -- Delete generated application files
cmd                -- Executes the given command
compile            -- Compile source files
compile.protocols  -- Consolidates all protocols in all paths
deps               -- List dependencies and their status
deps.clean         -- Remove the given dependencies' files
deps.compile       -- Compile dependencies
deps.get           -- Get all out of date dependencies
deps.unlock        -- Unlock the given dependencies
deps.update        -- Update the given dependencies
do                 -- Executes the tasks separated by comma
escript.build      -- Builds an escript for the project
help               -- Print help information for tasks
hex                -- Print hex help information
hex.config         -- Read or update hex config
hex.docs           -- Publish docs for package
hex.info           -- Print hex information
hex.key            -- Hex API key tasks
hex.outdated       -- Shows outdated hex deps for the current project
hex.owner          -- Hex package ownership tasks
hex.publish        -- Publish a new package version
hex.search         -- Search for package names
hex.user           -- Hex user tasks
loadconfig         -- Loads and persists the given configuration
local              -- List local tasks
local.hex          -- Install hex locally
local.rebar        -- Install rebar locally
new                -- Create a new Elixir project
run                -- Run the given file or expression
test               -- Run a project's tests

And mix --help:
[11:50:24] sobolev :: MacBook-Pro-Nikita  ➜  Documents/elixir/elixir_lang_moscow » mix --help
mix                     # Runs the default task (current: "mix run")
mix app.start           # Starts all registered apps
mix archive             # Lists all archives
mix archive.build       # Archives this project into a .ez file
mix archive.install     # Installs an archive locally
mix archive.uninstall   # Uninstalls archives
mix clean               # Deletes generated application files
mix cmd                 # Executes the given command
mix compile             # Compiles source files
mix deps                # Lists dependencies and their status
mix deps.clean          # Deletes the given dependencies' files
mix deps.compile        # Compiles dependencies
mix deps.get            # Gets all out of date dependencies
mix deps.unlock         # Unlocks the given dependencies
mix deps.update         # Updates the given dependencies
mix do                  # Executes the tasks separated by comma
mix ecto.create         # Create the storage for the repo
mix ecto.drop           # Drop the storage for the repo
mix ecto.gen.migration  # Generate a new migration for the repo
mix ecto.gen.repo       # Generate a new repository
mix ecto.migrate        # Run migrations up on a repo
mix ecto.rollback       # Rollback migrations from a repo
mix escript.build       # Builds an escript for the project
mix gettext.extract     # Extracts translations from source code
mix gettext.merge       # Merge template files into translation files
mix help                # Prints help information for tasks
mix hex                 # Prints Hex help information
mix hex.build           # Builds a new package version locally
mix hex.config          # Reads or updates Hex config
mix hex.docs            # Publishes docs for package
mix hex.info            # Prints Hex information
mix hex.key             # Hex API key tasks
mix hex.outdated        # Shows outdated Hex deps for the current project
mix hex.owner           # Hex package ownership tasks
mix hex.public_keys     # Manages Hex public keys
mix hex.publish         # Publishes a new package version
mix hex.registry        # Hex registry tasks
mix hex.search          # Searches for package names
mix hex.user            # Hex user tasks
mix loadconfig          # Loads and persists the given configuration
mix local               # Lists local tasks
mix local.hex           # Installs Hex locally
mix local.phoenix       # Updates Phoenix locally
mix local.public_keys   # Manages public keys
mix local.rebar         # Installs rebar locally
mix new                 # Creates a new Elixir project
mix phoenix.digest      # Digests and compress static files
mix phoenix.gen.channel # Generates a Phoenix channel
mix phoenix.gen.html    # Generates controller, model and views for an HTML based resource
mix phoenix.gen.json    # Generates a controller and model for a JSON based resource
mix phoenix.gen.model   # Generates an Ecto model
mix phoenix.gen.secret  # Generates a secret
mix phoenix.new         # Creates a new Phoenix v1.1.4 application
mix phoenix.routes      # Prints all routes
mix phoenix.server      # Starts applications and their servers
mix profile.fprof       # Profiles the given file or expression with fprof
mix run                 # Runs the given file or expression
mix test                # Runs a project's tests
iex -S mix              # Starts IEx and run the default task

It's because mix help is a little slow, so mix just keeps simple. Maybe what you want is the plugin mix-fast.

The thing is: it was working before the last update.

@sobolevn it can't have ever worked before because the last update didn't modify any of the subcommands returned. See the history: https://github.com/robbyrussell/oh-my-zsh/commits/master/plugins/mix
If you want that to work, use the mix-fast plugin instead. However, if mix phoenix commands are available by default we can put them in the subcommands array as well.


SLF4J Warnings showing up when starting the UC Server in CLI

Describe the bug
Getting the following SLF4J warnings when starting the UC Server:

No SLF4J providers were found.
Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier.

To Reproduce
Steps to reproduce the behavior:

build/sbt package
bin/start-uc-server

Expected behavior
We should get rid of these warnings.
System [please complete the following information]:

OS: macOS Sonoma 14.5

Additional context
As mentioned here we can get rid of the warnings if we replace log4j-slf4j-impl with log4j-slf4j2-impl in build.sbt here and here.
Please let me know if this makes sense. Thanks!

Apache Spark and Delta Lake use slf4j for logging and am wondering why UC chose another lib? Perhaps UC could (should?) use the same logging lib?

The following should work in commonSettings:
  libraryDependencies ++= Seq(
    "org.slf4j" % "slf4j-api" % "2.0.13",
    "org.slf4j" % "slf4j-log4j12" % "2.0.13" % Test,
    "org.apache.logging.log4j" % "log4j-slf4j2-impl" % "2.23.1",
    "org.apache.logging.log4j" % "log4j-api" % "2.23.1",
  ),

Let me know @vksx if you wanna work on it. I can support you if needed.

@jaceklaskowski Sure, I'll take this up. I will add the recommended changes to commonSettings.


Fixing the issue for realtime table creation with env variables in stream configs

Description
Fixing the issue of failure to create a realtime table with env variable inside it.
Current Pinot doesn't apply env variables during the table creation phase.
For the real-time table creation, Kafka consumer won't be initialized correctly when Kafka connection secrets are configured as env variables. E.g.
"ssl.truststore.password": "${KAFKA_TRUSTSTORE_PASSWORD}",
"ssl.keystore.password": "${KAFKA_KEYSTORE_PASSWORD}",

Codecov Report

Merging #6373 (6db99dd) into master (1beaab5) will decrease coverage by 21.17%.
The diff coverage is 38.69%.

@@             Coverage Diff             @@
##           master    #6373       +/-   ##
===========================================
- Coverage   66.44%   45.27%   -21.18%
===========================================
  Files        1075     1294      +219
  Lines       54773    62540     +7767
  Branches     8168     9090      +922
===========================================
- Hits        36396    28313     -8083
- Misses      15700    31889    +16189
+ Partials     2677     2338      -339

Flag
Coverage Δ

integration
45.27% <38.69%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ot/broker/broker/AllowAllAccessControlFactory.java
100.00% <ø> (ø)

.../helix/BrokerUserDefinedMessageHandlerFactory.java
52.83% <0.00%> (-13.84%)
:arrow_down:

...org/apache/pinot/broker/queryquota/HitCounter.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...che/pinot/broker/queryquota/MaxHitRateTracker.java
0.00% <0.00%> (ø)

...ache/pinot/broker/queryquota/QueryQuotaEntity.java
0.00% <0.00%> (-50.00%)
:arrow_down:

...ker/routing/instanceselector/InstanceSelector.java
100.00% <ø> (ø)

...ceselector/StrictReplicaGroupInstanceSelector.java
0.00% <0.00%> (ø)

...roker/routing/segmentpruner/TimeSegmentPruner.java
0.00% <0.00%> (ø)

...roker/routing/segmentpruner/interval/Interval.java
0.00% <0.00%> (ø)

...r/routing/segmentpruner/interval/IntervalTree.java
0.00% <0.00%> (ø)

... and 1292 more

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 2a7d506...6db99dd. Read the comment docs.


some docs

More info about prepare, build and run DF

I wrote that the build&launch is the same for Windows. Unfortunately, I am unable to test the instructions on Windows, so I cannot correct them for that operating system. I suspect that the name of the executable file is not the only one difference.

@BASM building process on Windows is more or less the same, just the name of the library is dfint_hook.dll instead of libdfint_hook.so. See build workflow: https://github.com/dfint/df-steam-hook-rs/blob/main/.github/workflows/build.yml

That is right, the same cli command, output as dll.


analysis.types.paddingThreshold is not respected

Version and Platform (required):

Binary Ninja Version: 3.5.4387-dev Personal (71942341)
OS: Windows
OS Version: 10.0.25375.1
CPU Architecture: x64

Bug Description:
Compilers sometimes like to generate weird code when initializing nested structures:

There's a separate argument to be made that BN should handle this better, but the more annoying issue for me here is the rendering of the types involved:

The fact that the whole S1DataCacheBucket structure is rendered this way makes it much harder to add fields at specific offsets by hand, which is particularly important in this case because of the weird offset pointers in the initialization code confusing BN's analysis.
Steps To Reproduce:

Grab this BNDB.
Navigate to 0x7ff69baff3a0.

Expected Behavior:
There should be no __padding fields rendered in the Types view.

Our code is correct for this case

The problem is that you have somehow (maybe unknowingly) changed the value of analysis.types.paddingThreshold for the binary.

That was exactly it. Changing it on the Resource level fixed the issue.
It's strange though. I don't think I've ever used the Resource tab in the settings UI... not sure how that crept in there.


vkd3d: 1.10 -> 1.12

Description of changes

Closes https://github.com/NixOS/nixpkgs/pull/293902
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3605

Small note: vkd3d-proton 2.12 is likely to release soon, given that the changelog was already committed.

I will stack it when it arrives, then.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3609

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4091

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4095


Upstream MetadataImage and related classes

Mostly a wholesale copy of the files from confluentinc/kip-500, with a few fixes for the test classes

@hachikuji : yes, the copies are unintentional.  we should should avoid those...
Also we should be able to access topics / partitions by id, but it requires an extra hop, as you saw.

Manually merged to trunk to fixup authorship


Feature request: Key input without pressing enter

The key controls are single characters. It would be nice if actions immediately triggered after pressing the keys, without hitting enter key.

@hkdobrev @ipwnponies Verdict??

@mkchoi212 I'm liking the responsiveness with this change. It's a more fluid experience, matches closely with interactivity ofgit --patch flows and vim.
Just a note on my workflow and how I've been using fac, it's primarily for viewing diff and navigation, I haven't been using the 'resolve using yours/theirs' extensively.

Closing this issue. This feature will most likely be part of https://github.com/mkchoi212/fac/issues/29

I'd love to see this added since #29 seems to be working fine.

With https://github.com/mkchoi212/fac/commit/8e39330e01eab8d14528a39d5a2d18d33bd5a783, you can now define cont_eval key in .fac.yml to toggle the behavior of not having to press enter for evaluation.
Please refer to https://github.com/mkchoi212/fac/blob/master/binding/README.md for more detail


Final Capstone project - Team members

This is the repository for our final capstone at Microverse 😄, we are four team members working on this project :
Say welcome to ⏬ :

@Laylo309 (a.k.a the sleepy Oracle) - Member A
@nelsinofrancisco (A.k.a the Big Oracle)  - Member B
@JbirdL86 (a.k.a The Bird) - Member C
@Hamzaoutdoors (a.k.a El Patron) - Member D

the link for our project: Link here

Hi @Hamzaoutdoors, @JbirdL86, @Laylo309, @nelsinofrancisco,
In my opinion, your project is complete! There is nothing else to say other than... it's time to start it :shipit:
Good luck! 🎉
Feel free to leave any questions or comments in the Issue thread if something is not 100% clear.


Add more filter options in index pages

Blocks:
From/To number.
From/To dates.
Transactions:
From/To block number.
From/To dates.
Contracts:
From/To dates.
Classes:
From/To declared at.


[POC] Test integrating "downlevel the minimum supported TS version"

This is a POC so it is not intended to be merged.
Created to test https://github.com/process-analytics/bpmn-visualization-js/pull/2326

✔ Tests completed. So closing.


Clean -fw from sample names in MultiQC

The new gzipping / rRNA code with --removeRiboRNA in the pipeline now appends -fw and -rv to the FastQ file names:
https://github.com/nf-core/rnaseq/blob/3b6df9bd104927298fcdf69e97cca7ff1f80527c/main.nf#L987-L988
These are not currently trimmed off by MultiQC and result in the sample rows being split:

This PR adds -fw to the MultiQC config, so that the sample names are cleaned and will merge into a single row again.
PR checklist

[x] PR is to dev rather than master
[x] This comment contains a description of changes (with reason)
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If necessary, also make a PR on the nf-core/rnaseq branch on the nf-core/test-datasets repo
[ ] Ensure the test suite passes (nextflow run . -profile test,docker).
[ ] Make sure your code lints (nf-core lint .).
[ ] Documentation in docs is updated
[x] CHANGELOG.md is updated
[ ] README.md is updated

@ewels as discussed on gitter this was for nfcore-rnaseq v 1.4.2 (multiqc v1.7). I have made some changes for implementation on our cluster but mainly to resource settings so should affect the multiqc part (https://github.com/kviljoen/RNAseq)

Hi @kviljoen,
You should not need to fork and edit the pipeline code to change configuration settings. The pipelines (and Nextflow) are designed so that you can overwrite just about everything in your own files. Then the codebase is kept "clean" and the pipeline is more reproducible, plus you can easily update without overwriting your changes.
See https://nf-co.re/usage/configuration for some documentation (recently revamped) and https://nf-co.re/usage/configuration as the place to go to add your config profile (which will then be instantly available to all nf-core pipelines).
Phil

I'm not sure why the GitHub actions lint test is failing here.. @ggabernet - any ideas?

Hi @ewels I'm still getting sample rows being split by '-fw' in the multiqc report even after inclusion of '-fw' in the multiqc_config.yaml for stripping.

Hi @kviljoen - sorry to hear that. This is definitely with the dev version of the pipeline? I don't think that this change is in a stable release yet..

Yes @Phil Ewels<EMAIL_ADDRESS>I tried to use the dev version
but got an unrelated error:
'Unknown variable 'ch_fasta_for_rsem_reference' where it looks like there
was no channel created for ch_fasta_for_rsem_reference? I've therefore just
added '-fw' to my own multiqc_config.yaml, not sure if I need any
additional edits?
Thanks for the quick reply!
Katie.
On Wed, Jun 17, 2020 at 9:55 AM Phil Ewels<EMAIL_ADDRESS>wrote:

Hi @kviljoen https://github.com/kviljoen - sorry to hear that. This is
definitely with the dev version of the pipeline? I don't think that this
change is in a stable release yet..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nf-core/rnaseq/pull/375#issuecomment-645216109, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACGSZMEBKLB7JT7LQECR3DTRXBZGRANCNFSM4KPTNZ5Q
.

--
Katie
Bioinformatician
Division of Computational Biology
Institute of Infectious Diseases & Molecular Medicine
University of Cape Town
South Africa
+27 21 406 6176<EMAIL_ADDRESS>

Ok, we should make a new issue about the ch_fasta_for_rsem_reference problem 😅
The change you mentioned should be all that is required. You can see that block of the MultiQC config in the pipeline here:
https://github.com/nf-core/rnaseq/blob/8845b219c5583c3a5173f51f5037b32f8945e093/assets/multiqc_config.yaml#L1-L7
It seems to work fine in my testing though 🤔

Thanks @ewels probably something on my side then. I'm currently using
process.container = 'nfcore/rnaseq:1.4.2' not sure if that would change
anything. Not sure if the ch_fasta_for_rsem_reference problem is on my
side, perhaps you could check if working for you?
Regards,
Katie.
On Wed, Jun 17, 2020 at 10:48 AM Phil Ewels<EMAIL_ADDRESS>wrote:

Ok, we should make a new issue about the ch_fasta_for_rsem_reference
problem 😅
The change you mentioned should be all that is required. You can see that
block of the MultiQC config in the pipeline here:
https://github.com/nf-core/rnaseq/blob/8845b219c5583c3a5173f51f5037b32f8945e093/assets/multiqc_config.yaml#L1-L7
It seems to work fine in my testing though 🤔
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nf-core/rnaseq/pull/375#issuecomment-645243273, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACGSZME2JE3QODPIRFL7SSTRXB7PLANCNFSM4KPTNZ5Q
.

--
Katie
Bioinformatician
Division of Computational Biology
Institute of Infectious Diseases & Molecular Medicine
University of Cape Town
South Africa
+27 21 406 6176<EMAIL_ADDRESS>

If you're using the development code, you should be using the development container - the dev tag instead of 1.4.2. This tag should be hardcoded in the pipeline though, usually there's not a need to specify this yourself?
The automated tests are passing fine so it must be something specific to the way that you're running the pipeline. Let's discuss on the other issue thread though.

Hi Phil, yes, dev container specified for dev branch (I was referring to my master branch where I'm on 1.4.2 and had only changed -fw in multiqc_config.yaml). Attached log file from dev run. Please note that this is a result of merging with my own version of the pipeline because we've had to make some small tweaks particularly with memory labels in the main.nf to get it to run optimally on our cluster [https://github.com/kviljoen/RNAseq/tree/dev], so may be specific to my version of pipeline. Log file attached
testrun.log

Hi @kviljoen,
I can't see any MultiQC config edits when comparing your fork?
Will move discussion of the log over to the other issue to try to keep these two separate 😅
Phil

Hi Phil,
The test I ran was on my master branch not dev, sorry (since dev wasn't working because of the other ch_fasta_for_rsem_reference issue). It's here
Regards,
Katie

Ok, the change looks fine. And you're not supplying a custom MultiQC config or anything? Is it possible to attach a MultiQC report where this is a problem?

Hi Phil, no custom MultiQC config no.

Hi @ewels I'm now running the nf-core/dev pipeline but am still having this issue, unfortunately.


outdated/updated packages

@ehawkvu , shall we have a outdated tracker for packages that are not outdated; similar to KISS upstream?
unmaintained/outdated packages get dropped as well.

I'm not opposed, but I'd like to have this be more automated. I've been looking for an excuse to use https://github.com/ehawkvu/kiss-personal/blob/master/bin/kiss-automail

wouldnt that (more or less) make you the sole reciever of said emails @ehawkvu? :p
in regards to this repo anyway.
I can absolutly  see the benefit in community repo though.

@hovercats kiss-automail can account for this, and if I were to use it, I would add two more files to the root of the directory, a blacklist for packages (ones that should not have emails sent out for whatever reason) and one for emails themselves. Naturally I'd blacklist myself from receiving emails.
As for the community repo, I think it'd be a pretty good solution, but I haven't really asked around.

sounds good.
yeah, you should make an issue about it over at the upstream repo, or atleast mention it in the irc, if it hasnt already/


Build pages for BCO registry

Once the registry DB tables are added to the userdb and API endpoints are created, build pages for UI.

Fixed with:

https://github.com/biocompute-objects/portal/pull/228
https://github.com/biocompute-objects/bco_api/pull/146
https://github.com/biocompute-objects/userdb/pull/30


SOCKS5 proxy support

This PR adds SOCKS5 proxy support with and without authentication. It superseeds #4102.

@akallabeth I've treated your comments and removed the timer vs SunOS things from this PR


Copy button in readme copies output

When you copy with the copy button the Hello World example in the README, it also copies the output.

This seems to be resolved.. please comment if there is anything else I have overlooked.


How to show/displace the testing result files?

I was able to generate 6 output files for each point cloud input file when executing test.py.
But how can I show or display the 6 output files (2 .off files and 4 .obj files)?
thanks

Hi, you can drag all the files to MeshLab together. The .off file is the input point cloud, the *_edge.obj is the skeletal line,s and the *_face.obj is the skeletal faces.


Error with select query when using PostgreSQL 12

Please first make sure you have looked at:

Documentation: https://github.com/mkleehammer/pyodbc/wiki
Other issues

Environment
To diagnose, we usually need to know the following, including version numbers.  On Windows, be
sure to specify 32-bit Python or 64-bit:

Python: 3.6
pyodbc: 4.0.30
Host OS: Ubuntu 18.04
DB: PostgreSQL
driver: PostgreSQL Unicode
Docker Image for PostgreSQL: postgres:12.2-alpine
All code runs on docker containers.
(Note: The error doesn't occur for PostgreSQL 11.7, I believe it only affects PostgreSQL 12+, please see the StackOverflow question below.)

Issue
Often it is easiest to describe your issue as "expected behavior" and "observed behavior".

Observed behavior:

When I execute a select query, this error occurs but I still receive the result of the query.
ERROR:  column c.relhasoids does not exist at character 245
STATEMENT:  select n.nspname, c.relname, a.attname, a.atttypid, t.typname, a.attnum, a.attlen, a.atttypmod, a.attnotnull, c.relhasrules, c.relkind, c.oid, pg_get_expr(d.adbin, d.adrelid), case t.typtype when 'd' then t.typbasetype else 0 end, t.typtypmod, c.relhasoids, attidentity from (((pg_catalog.pg_class c inner join pg_catalog.pg_namespace n on n.oid = c.relnamespace and c.oid = 16395) inner join pg_catalog.pg_attribute a on (not a.attisdropped) and a.attnum > 0 and a.attrelid = c.oid) inner join pg_catalog.pg_type t on t.oid = a.atttypid) left outer join pg_attrdef d on a.atthasdef and d.adrelid = a.attrelid and d.adnum = a.attnum order by n.nspname, c.relname, attnum
ERROR:  current transaction is aborted, commands ignored until end of transaction block

Related: https://stackoverflow.com/questions/58461178/how-to-fix-error-column-c-relhasoids-does-not-exist-in-postgres

Expected behavior: This error doesn't happen.

It sounds like you might need to upgrade your ODBC driver. The following works for me:
import pyodbc

cnxn = pyodbc.connect("DSN=PostgreSQL35W")
print(f'driver: {cnxn.getinfo(pyodbc.SQL_DRIVER_NAME)}, version: {cnxn.getinfo(pyodbc.SQL_DRIVER_VER)}')
# driver: PSQLODBC35W.DLL, version: 12.00.0000

print(crsr.execute("SELECT 1 AS foo").fetchall())
# [(1, )]

Thank you very much for your quick reply. Unfortunately, this solution doesn't work for me.
Can you tell me this driver is for Windows or Linux, please?
I tried updating the driver for Linux but it seems that my driver is up-to-date.
odbc-postgresql is already the newest version (1:10.01.0000-1)
unixodbc is already the newest version (2.3.7).

Here are the drivers that is available for me:
>>> import pyodbc
>>> print(pyodbc.drivers())
['MySQL ODBC 8.0 Driver', 'MySQL ODBC 8.0', 'PostgreSQL ANSI', 'PostgreSQL Unicode', 'ODBC Driver 17 for SQL Server']

Only PostgreSQL Unicode works (with the error above)
When I tried your query (print(crsr.execute("SELECT 1 AS foo").fetchall()) ), it also works well. But for any more complex query, like SELECT id from table, this error appears.

Please post result of
print(f'driver: {cnxn.getinfo(pyodbc.SQL_DRIVER_NAME)}, version: {cnxn.getinfo(pyodbc.SQL_DRIVER_VER)}')

after you connect with PostgreSQL Unicode.

Here it is: driver: psqlodbcw.so, version: 10.01.0000

Okay so your ODBC driver is up-to-date as far as the Ubuntu 18.04 repositories are concerned, but Ubuntu repos often distribute rather old versions of stuff like this. You're using a v10 driver and apparently it doesn't work with a v12 server. You'll need to get a newer version of the ODBC driver directly from PostgreSQL.

Thank you very much for your help. I think version 11.7 will work too.


no matches for kind "Jaeger" in version "io.jaegertracing/v1alpha1"

I've installed the operator on OpenShift through creating the yaml files provided from the steps, but the operator back off with CrashLoopBackOff as follows.
# oc get pod
NAME                              READY     STATUS             RESTARTS   AGE
jaeger-operator-97dd6d757-xphlp   0/1       CrashLoopBackOff   8          21m

And the operator's pod logs are here.
# oc logs jaeger-operator-97dd6d757-xphlp
time="2019-03-11T12:38:29Z" level=info msg=Versions arch=amd64 jaeger-operator=1.10.0 operator-sdk=v0.4.1 os=linux version=go1.11.1
time="2019-03-11T12:38:29Z" level=info msg="Auto-detected the platform" platform=openshift
time="2019-03-11T12:38:29Z" level=info msg="Automatically adjusted the 'es-provision' flag" es-provision=false
time="2019-03-11T12:38:29Z" level=fatal msg="no matches for kind \"Jaeger\" in version \"io.jaegertracing/v1alpha1\""

What is it wrong in my installation steps for the operator ? It looks like v1alpha1 API version is not including the Jaeger resources, the documentation is based on v1 API version, so it's not matched API version with it.  If you have any workaround to fix it ?
My env is OpenShift v3.11.82. Thanks

Apologies but looks like the readme is describing the installation instructions for the current master branch, which has changed apiGroup from io.jaegertracing/v1alpha1 to jaegertracing.io/v1, but the operator.yaml is referring to the 1.10 version of the operator.
If you are intending to deploy a CR using the new jaegertracing.io/v1 apiGroup, then probably the easiest fix is to change the operator image to use the master tag.

Thank you @objectiser ! It work for me ! I'll close this issue.


Bootstrap's JavaScript requires jQuery (error)

I'm submitting a bug report

Aurelia Skeleton Version
skeleton-typescript

Framework Version:
1.0.0

Please tell us about your environment:

Operating System:
Windows [8.1]

Node Version:
4.4.7

NPM Version:
3.10.6

JSPM OR Webpack AND Version
JSPM 0.16.41

Browser:
Electron 1.0 | Chrome 51.0.2704.103

Language:
all | TypeScript X.X | ESNext

Current behavior:
followed steps to setup
ran electron index.js command
loading screen displays nothing happens. open dev tools
Error: (SystemJS) Bootstrap's JavaScript requires jQuery(…)
note: I commented out the bluebird.min.js
Expected/desired behavior:

What is the expected behavior?
load application
What is the motivation / use case for changing the behavior?

probably can temp fix it by adding it to the index.html

Yep. That's what I did to get it working.

@doktordirk  can You please paste this fix here? Have same problem...

Can you guys try npm update and see if this is still happening?

@niieani npm update didn't work for me
@s-krawczyk just add a script tag like so to the index.html file before the </head> tag
 <script<EMAIL_ADDRESS>

that npm update helps with jspm, was unlikely in the first place :)

@nmyvision that's strange I've tried that and not wokred for me
Have You problem with typings of jquery and angular-protractor? I get type mismatch errors. After some changes in typings of jquery it builds but still exception of undefinied "jquery". Any?

@s-krawczyk sounds like you have a different issue than mine. My issue was jquery client library wasn't loading (or maybe not loading before bootstrap). Sounds like your having issues with typescript references, what IDE and version of typescript do you have installed.

Adding
<script<EMAIL_ADDRESS>above all other scripts just before  fixed the problem for me.
The index.html now ends like this:
`

<!-- We include bluebird to bypass Edge's very slow Native Promise implementation. The Edge team -->
<!-- has fixed the issues with their implementation with these fixes being distributed with the  -->
<!-- Windows 10 Anniversary Update on 2 August 2016. Once that update has pushed out, you may    -->
<!-- consider removing bluebird from your project and simply using native promises if you do     -->
<!-- not need to support Internet Explorer.                                                      -->
<script<EMAIL_ADDRESS><script<EMAIL_ADDRESS><script src="jspm_packages/system.js"></script>
<script src="config.js"></script>
<script>
  System.import('aurelia-bootstrapper');
</script>

`

This issue might be related to the PR: https://github.com/aurelia/skeleton-navigation/pull/675 .

@nmyvision they are kinda-sorta related. jQuery and Bootstrap just don't play well in a modular setup, unfortunately.

I'm getting the same error in skeleton-typescript-aspnetcore but adding jquery to the Index.cshtml file doesn't fix the problem. Can you think of any reasons why?

https://github.com/jspm/registry/blob/master/package-overrides/github/twbs/bootstrap%403.3.7.json
That override should fix the issue, I'll try removing bootstrap and installing again and make sure the override is used

stale since 2016


7.3 updates

We need to update the simple html dom from 1.5 to at least 1.7 or php7.3 fails hard.
I'll leave this open for any other 7.3 issues we find, so far that is all I have found.

🙏


sense::handler creates deprecated "Filters" entry in resulting yaml

when attempting to create the sample handler:
sensu::handler { 'slack':     type    => 'pipe',     command => "/opt/sensu/embedded/bin/handler-slack.rb",     config  => {       'webhook_url' => 'https://hooks.slack.com/services/###/###/###',       'template'    => '',     }   }
the resulting created yaml will contain an empty "filter" entry.  Despite being empty, this causes the same error to repeat in the sensu logs while evaluating the handler:
{"timestamp":"2017-03-16T09:41:35.902187-0700","level":"info","message":"handler output","handler":{"command":"/opt/sensu/embedded/bin/handler-slack.rb","type":"pipe","filters":[],"severities":["ok","warning","critical","unknown"],"name":"slack"},"output":["warning: event filtering in sensu-plugin is deprecated, see http://bit.ly/sensu-plugin\nwarning: occurrence filtering in sensu-plugin is deprecated, see http://bit.ly/sensu-plugin\nonly handling every 30 occurrences:"]}
Manually editing the yaml and pulling out the empty filters entry suppress the message, but it seems like something that should likely be cleaned out.

Hi @Justin-DynamicD, the filter deprecation warnings you describe are a product of changes in the sensu-plugin library, and are not related to the presence or absence of filters in the handler definition.
Please see https://sensuapp.org/blog/2016/07/07/sensu-plugin-filter-deprecation.html for an in-depth description of this situation.

Manually editing the yaml and pulling out the empty filters entry suppress the message

I think it is more likely that your next test event had a sufficient number of occurrences to qualify for being handled.

perhaps my explanation is poor, but the link provided describes the exact problem as well as my suggestion:  eventually remove the filtering from sensu::handler, so it sounds like it's being worked on.
To clarify, however: Even if the resulting value is left empty, merely declaring "filters" in the handler yaml file will generate the warning in the sensu-server log.


Travis Build Failing due to libc6

This started when I made changes yesterday. I reverted back and the issue persisted, and also the change I made had nothing to do with this.
Tensorflow backend fails to load due to missing libc6. I checked out some conversations, and it seems that it might have to do something with versions. Resolving now.

Traceback (most recent call last):
  File "./test_script.py", line 1, in <module>
    from autonomio.commands import data, train, test
  File "/home/travis/build/autonomio/core-module/autonomio/__init__.py", line 3, in <module>
    from train_new import kuubio
  File "/home/travis/build/autonomio/core-module/autonomio/train_new.py", line 7, in <module>
    from transform_data import transform_data
  File "/home/travis/build/autonomio/core-module/autonomio/transform_data.py", line 6, in <module>
    from y_transform import y_transform
  File "/home/travis/build/autonomio/core-module/autonomio/y_transform.py", line 2, in <module>
    from keras.utils import np_utils
  File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/keras/__init__.py", line 3, in <module>
    from . import activations
  File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/keras/activations.py", line 4, in <module>
    from . import backend as K
  File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/keras/backend/__init__.py", line 73, in <module>
    from .tensorflow_backend import *
  File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/keras/backend/tensorflow_backend.py", line 1, in <module>
    import tensorflow as tf
  File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/tensorflow/__init__.py", line 24, in <module>
    from tensorflow.python import *
  File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/tensorflow/python/__init__.py", line 51, in <module>
    from tensorflow.python import pywrap_tensorflow
  File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/tensorflow/python/pywrap_tensorflow.py", line 52, in <module>
    raise ImportError(msg)
ImportError: Traceback (most recent call last):
  File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/tensorflow/python/pywrap_tensorflow.py", line 41, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 28, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 24, in swig_import_helper
    _mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
ImportError: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17' not found (required by /home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so)

Can you take a look at this Anish? I think it's some pretty basic linux package stuff. Maybe some versions change since we did our last build, and that messed it up.

Is it okay if I have a look tomorrow evening, or day-after-tomorrow morning?

Totally yea. Thanks!~

On May 9, 2017, at 19:51, Anish Mangal<EMAIL_ADDRESS>wrote:
Is it okay if I have a look tomorrow evening, or day-after-tomorrow morning?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/autonomio/core-module/issues/30#issuecomment-300229072, or mute the thread https://github.com/notifications/unsubscribe-auth/AHk0FLMwougewJLReczjVUMzQeSa2kZRks5r4JmIgaJpZM4NU7y8.

This might be an issue with tensorflow. I've opened a ticket on their tracker.
https://github.com/tensorflow/tensorflow/issues/9838

BTW, this usually means your system is too old. TensorFlow internal testing is using Ubuntu 16.04, are you on 14.04? It's possible to make it work with older systems by upgrading just glibc,
http://stackoverflow.com/questions/33655731/error-while-importing-tensorflow-in-python2-7-in-ubuntu-12-04-glibc-2-17-not-f

Dear @yaroslavvb it looks like we are on 16.04 as this line within .travis.yml would suggest.
https://github.com/autonomio/core-module/blob/master/.travis.yml#L2

Hmm. Looks like from the log we are on ubuntu 12.04. Strange! I will check the travis configuration.

Do ldd --version. My Ubuntu 14.04 system has 2.19, and looks like TF only needs 2.17
(memory) yaroslav@52:~/git0/pixel-cnn-private$ ldd --version
ldd (Ubuntu EGLIBC 2.19-0ubuntu6.9) 2.19

It looks as if travis doesn't support 16.04 as of now :(
https://docs.travis-ci.com/user/ci-environment/
@mikkokotila What do you suggest?

14.04 should be OK. There are quite a few people using 14.04 still

Hey, and thanks very much for @yaroslavvb this. I'm sorry I was away for a couple of days. I think 14.04 is totally fine for our core and it will work out of the box, but for the container version we would have to think this through more carefully, as we intentionally avoided the 14.04 base image on docker after giving it a try. I guess if we want to keep using Travis CI in this context, we have no other option that going through the hoops of setting up the container again but now on 14.04.
Unless you disagree @m-anish I'll create an issue for that...and assign to you ()

this is resolved (sometime time ago I believe).


OMIM "included" entries and not the preferred names on MONDO terms

NV to do:  updated 02/10/22
I need to write out concrete action items for Nico to work on this.

I have run into a couple of cases where an OMIM entry is only once in MONDO, but the disease name it is associated with is the OMIM "included" disorder, not the preferred name from OMIM. We handle these "included" terms as distinct entries in MedGen and thus cannot link a MONDO ID to the term which is OMIM's preferred term. Some examples:
I.	MONDO:0007691 “chronic inflammatory demyelinating polyneuropathy”
a.	Maps to OMIM https://www.omim.org/entry/139393 but this represents Guillain-Barre syndrome, Familial AND “other entity” POLYNEUROPATHY, INFLAMMATORY DEMYELINATING, CHRONIC, INCLUDED; CIDP, INCLUDED
b.	UMLS splits the MIM term among multiple CUIs; we split the OMIM entry into distinct concepts for GBS, familial and then imported the MONDO term separately.  However put the MIM# on the entry with the preferred name (In this case would be Guillain-Barre syndr, familial.)
II.	MONDO:0007608 Desmoid tumor
a.	MIM https://omim.org/entry/135290 is for both desmoid disease, hereditary. AND “other” Desmoid Tumor (caused by somatic mutation)
b.	MONDO includes the Fibromatosis, familial infiltrative (FIF) alt name, but not desmoid disease, hereditary. So we can’t have a MONDO ID for our entry that represents the PT from OMIM (DESMOID DISEASE, HEREDITARY) UMLS CUI: C1851124
c. is this one of the instances where maybe the disorders are similar enough? I'm not a clinician so I can't say.
Nicole, I see your ticket #2745, so it looks like there is a mechanism to manage OMIM entries relating to multiple disease names, I hope that means MONDO can link the MIM#s to the terms of the preferred name and (as needed) the "included" terms.

Hello @kanems
I'm Sabrina, a new curator who recently joined the Mondo team.
We will address your issue as soon as possible. Thank you for your patience.
If this is a high priority, please let me know and we can prioritize it. Thank you!

I asked Ada about this and this was her response:
In most cases, an included title is not the same concept as the parent entry, so the UMLS has handled this correctly.  If you are linking to OMIM so that people can read about it, then use the parent MIM number, but ontologically it cannot be represented as the same.  This is the opposite from alternate titles which are synonyms.  Sometimes included concepts are off-shoots or not clearly distinct.  We may not have looked at them for some time, as well.

Hi Nicole, Ada's response is how I understood the distinction between "included" vs "alternate" terms on the same OMIM number, which is reassuring. However, my question to Mondo may not have been clear initially, let's see if I can clarify.
Is Mondo's policy to map OMIM numbers based on the main "preferred" name on the record or on the "included" name?
MedGen maps on the "preferred name" from OMIM and so if Mondo does the opposite, we cannot replicate the Mondo:OMIM relationship in MedGen, but we'd like to agree with Mondo as much as possible (we're just agreeable folks like that ;-) )
One example is OMIM 139393, which, as I read it, has the primary preferred name of "GUILLAIN-BARRE SYNDROME, FAMILIAL" (see screen shot). However, this OMIM number maps to MONDO:0007691 "chronic inflammatory demyelinating polyneuropathy" which has a related synonym "Guillain-Barre syndrome, familial."  So I think Mondo has appropriately handled that these two disease terms are related but not exactly the same, but I was confused by the selection to use the "included" disease rather than the OMIM primary name on the number.

Depends on @jiaola's work on the OMIM ingest.
@kanems - I'll respond to your comment above soon, thanks!

to do:
Would be nice to have a new xref tag, something like:
MONDO:includedInOMIM or
MONDO:splitFromOMIM

@kanems
we renamed MONDO:0007691 to 'Guillain-Barre syndrome, familial', it should be available in the next release (early September)
We want to use the OMIM preferred labels for Mondo terms, we'll work on cleaning this up. Based on Ada's response too, we'll work on retroactively splitting out the terms that are 'included' in OMIM entries, as these should be separate classes, as noted above.
Thanks for bringing this to our attention! It will take some time as our developer Dazhi is working on improving the OMIM ingest workflow.

On QC call (211105):
Need to break down into a step by step to-do list.
During OMIM ingest, we should tag synonyms to indicate the "included" terms, so curators can go back later and decide whether these "included terms" should be synonyms or a new term.
This requires a lot of work in the ingest pipeline. Will be done in 2022.

NCBI and UMLS have used the strategy of treating each 'included' term as a distinct concept and merging later if review indicates that some of the included terms within a MIM record are synonyms to each other. It is unlikely that an included term is a synonym to the concept represented by the MIM number title and alternate terms, so it may be appropriate to treat as distinct until proven otherwise , rather than treating as the same and then having to split.
caveat:  I am using synonym here as 'different terms for the exact same concept'

I agree with @maglott's suggestion. I think it would be best if we added 'included' entries as new terms in Mondo and they would have the xref to the OMIM ID with a new tag MONDO:includedInOMIM.
I'm not sure how difficult it would be to do this retroactively?


[PA-1403] TC Automation - Delete backup from deleted or unavailable cluster of a non-admin user from admin

What this PR does / why we need it:
This PR adds a test case named "DeleteUserBackupsAndRestoresOfDeletedAndInActiveClusterFromAdmin" to automate the use case of deleting backup from deleted or unavailable cluster of a non-admin user from admin. This test case will increase the test coverage of Px-Backup TC Automation and ensure that the orphaned object feature functions as intended.
Which issue(s) this PR fixes (optional)
Closes #PA-1403
Special notes for your reviewer:
This test case is applicable to Px-Backup versions 2.6.0 and above. I will update the results once the test runs are complete.
TestRail: https://portworx.testrail.net/index.php?/cases/view/87569

The commit checks will fail because I neither set the upstream to px-backup/2.5.2-dev nor rebased with the topic/krishna-px/PA-1528-v7 branch, in order to keep the review process easy. This test case may not belong to the file it is in.

Thank you for the reviews. These changes are now included in PR #1663.


CloudPath.iterdir should use yield from

https://github.com/drivendataorg/cloudpathlib/blob/3af76b9b9d8e44a0094248673e5a9b3934f6863f/cloudpathlib/cloudpath.py#L327-L329
It would be more efficient to write:
def iterdir(self) -> Iterable["CloudPath"]:
   yield from self.client._list_dir(self, recursive=False)

🤷  IMO not worth tracking in an issue. If someone made this change as part of a substantive PR that would be fine


[Bug] Quickstarts Not Showing in Hubspot connector

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
As described. Downstream connections seem empty but only for one instance of the hubspot connectors in our account

Relevant error log or model output
No response
Expected behavior
I'd expect the quickstarts to show as in all the other hubspot connectors in our account

dbt Project configurations
quickstart
Package versions
quickstart
What database are you using dbt with?
snowflake
dbt Version
quickstart
Additional Context
No response
Are you willing to open a PR to help address this issue?

[ ] Yes.
[ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
[X] No.

Hey there @rishi-tripathy 👋 so in this repository we support the code that Quickstart uses, whereas I believe your question is more about Quickstart itself specifically.
I'd recommend opening a ticket in the Fivetran support portal and the Quickstart team can help you better from there


nixos/prometheus: add AF_NETLINK permission to node-exporter netdev

I found https://github.com/prometheus/node_exporter/pull/2105 does not work. It turns out to be node exporter can't find any devices without AF_NETLINK permission. I added
[Service]
RestrictAddressFamilies=AF_NETLINK

to /run/systemd/system/prometheus-node-exporter.service.d/override.conf.
Then I can see network addresses appear in the prometheus metrics.

Motivation for this change
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Closed in favour of #198638.


Emit SymbolInformation for relevant synthetic symbols

According to the SemanticDB spec, producers should emit SymbolInformation entries for symbols like caseclass-generated code, synthetic implicit parameters for context/view bounds, etc (see the full list in the spec). Metacp already does that because it simply retranslates whatever pickles say, but metac is syntax-based, so it isn't up to speed yet.

Also need to update the spec to cover parameter translation for case classes.

I hit on this disrepancy between metac and metacp in #1399 metacp produces more symbols than metac.


opt-level = 0 + debug=false does not produce no-debuginfo bins

cmake-rs tries to translate cargo settings to cmake settings, but there are two cases where the debuginfio settings are ignored. The first is opt-level=0 + debug=false. This picks the CMake Debug profile, which always has debuginfo on.
The second is opt-level=s + debug=true. This picks MinSizeRel, which always has debuginfo off.
Solving this in the general case looks hard. I have begun trying to do it by running the cmake configure step once with the -LA flags, to list the configured values of CMAKE_C_FLAGS_DEBUG (etc); modify those flags, then run the actual configuration.
I think it's a viable solution, but I haven't quite gotten there: https://github.com/brson/cmake-rs/tree/dev-nodebug
This is a problem in TiKV where we are turning off debuginfo to improve compile times, but RocksDB makes up a huge chunk of that debuginfo. cc https://github.com/tikv/tikv/issues/4711
We could probably solve this one-off in librocksdb_sys, but it would seem better to solve it for everybody.

I'm not personally intimately familiar enough with cmake to know how to fix this myself, but your patch seems reasonable to me! I sort of wish we could just tell it what flags we want in the axes that we have, but having a workaround in the meantime should be fine. Want to send a PR for those changes?

Yeah, I'll send a patch when I get it working.
It may be reasonable to just translate rust's options directly to CMAKE_C_FLAGS_DEBUG, but I also don't know enough about CMake to know whether that is ok.

I don't have an answer, but I just wanted to put this thought out there.
Currently, cmake-rs does this:

if opt-level ≡ 0 then CMAKE_BUILD_TYPE=Debug,
if opt-level ∈ {1, 2, 3} then:

if debug ≡ false then CMAKE_BUILD_TYPE=Release
if debug ≡ true then CMAKE_BUILD_TYPE=RelWithDebInfo

if opt-level ∈ {s, z} then CMAKE_BUILD_TYPE=MinSizeRel

Here's one alternative that gives debug a higher precedence:

if debug ≡ true then:

if opt-level ∈ {0, s, z} then CMAKE_BUILD_TYPE=Debug
if opt-level ∈ {1, 2, 3} then CMAKE_BUILD_TYPE=RelWithDebInfo

if debug ≡ false then:

if opt-level ∈ {0, 1, 2, 3} then CMAKE_BUILD_TYPE=Release
if opt-level ∈ {s, z} then CMAKE_BUILD_TYPE=MinSizeRel

Perhaps you could move the {s, z} around a bit, but I guess one shouldn't expect to get a minimized build with debug info compiled in, so as long as debug ≡ false, you won't get CMAKE_BUILD_TYPE=MinSizeRel.

I think that the algorithm I suggested in https://github.com/alexcrichton/cmake-rs/issues/79#issuecomment-494676960 is a reasonable and simple change that would handle the corner cases mentioned by @brson, but I'm not sure if it's the best way to go in the long term.
If it's given that the goal of a -sys crate is to build a non-Rust library under the control of a Rust library, I think it makes sense to have Rust, via cmake-rs, decide certain aspects of building. The CMAKE_<LANG>_FLAGS and CMAKE_<LANG>_FLAGS_<CONFIG> seem to be good candidates for those aspects. Unfortunately, CMake does not appear to make it easy/desirable to do this, and the general advice I've read is to not override these but use CMAKE_<LANG>_FLAGS_INIT and CMAKE_<LANG>_FLAGS_<CONFIG>_INIT instead. Plus, you might run into conflicts with particularly picky CMakeLists.txt.
With that in mind, perhaps it would be useful to have cmake::Config functions that allow one to choose how to override certain variables, giving different mechanisms as arguments. The options could include:

Don't override. That is, let CMake or the CMakeLists.txt decide.
Override by letting cmake-rs choose a value that best fits the cargo settings.

Having more options seems reasonable to me! I'm not really sure which is the best way but having a few to try seems reasonable.

Thanks for the suggestions @spl

From the linked tikv thread, it may end up that we use debuginfo=1 for release mode. CMake itself doesn't seem to make any distinction between debuginfo levels, just on or off. And furthermore, by my recollection, cargo itself doesn't provide the debuginfo level to the build script, just on or off.
So for the tikv use case we may not be able to get what we want out of cargo and cmake-rs. (the equivalent of opt-level=3 + debuginfo=1 for cmake projects).
Unfortunately rocksdb is a big chunk of our binary and our debuginfo. If the above scenario happens we may just have to hack up or build script for our fork of rocksdb.


ZeroAndOneInflatedBetaOutput: module 'mxnet.symbol' has no attribute 'logical_or'

I originally thought this was a typo, but I tried to make the change to np.logical_or locally, and that did not fix the problem. Please let me know if more information would be helpful
In gluonts 0.6.3, I am submitting the following:
estimator_4 = deepar.DeepAREstimator(
    freq="W", prediction_length=4, trainer=trainer_1, distr_output=ZeroAndOneInflatedBetaOutput(),
    context_length=26, num_cells=104, dropout_rate=0.1)
predictor_4 = estimator_4.train(training_data=data_train_beta)

This produces the error referenced in the title with the following stack trace:
  0%|          | 0/50 [00:00<?, ?it/s]
learning rate from ``lr_scheduler`` has been overwritten by ``learning_rate`` in optimizer.
  0%|          | 0/50 [00:01<?, ?it/s]
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-24-94b4fecb46f1> in <module>
      2     freq="W", prediction_length=4, trainer=trainer_1, distr_output=ZeroAndOneInflatedBetaOutput(),
      3     context_length=26, num_cells=104, dropout_rate=0.1)
----> 4 predictor_4 = estimator_4.train(training_data=data_train_beta)

~/.conda/envs/cuda_test/lib/python3.6/site-packages/gluonts/model/estimator.py in train(self, training_data, validation_data, num_workers, num_prefetch, shuffle_buffer_length, **kwargs)
    274             num_prefetch,
    275             shuffle_buffer_length,
--> 276             **kwargs,
    277         ).predictor

~/.conda/envs/cuda_test/lib/python3.6/site-packages/gluonts/model/estimator.py in train_model(self, training_data, validation_data, num_workers, num_prefetch, shuffle_buffer_length, **kwargs)
    247             input_names=get_hybrid_forward_input_names(trained_net),
    248             train_iter=training_data_loader,
--> 249             validation_iter=validation_data_loader,
    250         )
    251

~/.conda/envs/cuda_test/lib/python3.6/site-packages/gluonts/mx/trainer/_base.py in __call__(self, net, input_names, train_iter, validation_iter)
    343                     )
    344
--> 345                     epoch_loss = loop(epoch_no, train_iter)
    346                     if is_validation_available:
    347                         epoch_loss = loop(

~/.conda/envs/cuda_test/lib/python3.6/site-packages/gluonts/mx/trainer/_base.py in loop(epoch_no, batch_iter, is_training)
    260                             if first_forward:
    261                                 first_forward = False
--> 262                                 _ = net(*inputs)
    263                                 if self.post_initialize_cb:
    264                                     self.post_initialize_cb(net)

~/.conda/envs/cuda_test/lib/python3.6/site-packages/mxnet/gluon/block.py in __call__(self, *args)
    680             hook(self, args)
    681
--> 682         out = self.forward(*args)
    683
    684         for hook in self._forward_hooks.values():

~/.conda/envs/cuda_test/lib/python3.6/site-packages/mxnet/gluon/block.py in forward(self, x, *args)
   1242                                      'Find all contexts = {}'.format(ctx_set))
   1243                 with ctx:
-> 1244                     return self._call_cached_op(x, *args)
   1245             with ctx:
   1246                 try:

~/.conda/envs/cuda_test/lib/python3.6/site-packages/mxnet/gluon/block.py in _call_cached_op(self, *args)
    993     def _call_cached_op(self, *args):
    994         if self._cached_op is None:
--> 995             self._build_cache(*args)
    996         assert self._cached_op, "Gluon failed to build the cache. " \
    997                                 "This should never happen. " \

~/.conda/envs/cuda_test/lib/python3.6/site-packages/mxnet/gluon/block.py in _build_cache(self, *args)
    922
    923     def _build_cache(self, *args):
--> 924         data, out = self._get_graph(*args)
    925         data_names = {data.name: i for i, data in enumerate(data)}
    926         params = self.collect_params()

~/.conda/envs/cuda_test/lib/python3.6/site-packages/mxnet/gluon/block.py in _get_graph(self, *args)
    914             params = {i: j.var() for i, j in self._reg_params.items()}
    915             with self.name_scope():
--> 916                 out = self.hybrid_forward(symbol, *grouped_inputs, **params)  # pylint: disable=no-value-for-parameter
    917             out, self._out_format = _flatten(out, "output")
    918

~/.conda/envs/cuda_test/lib/python3.6/site-packages/gluonts/model/deepar/_network.py in hybrid_forward(self, F, feat_static_cat, feat_static_real, past_time_feat, past_target, past_observed_values, future_time_feat, future_target, future_observed_values)
    456
    457         # (batch_size, seq_len)
--> 458         loss = distr.loss(target)
    459
    460         # (batch_size, seq_len, *target_shape)

~/.conda/envs/cuda_test/lib/python3.6/site-packages/gluonts/mx/distribution/distribution.py in loss(self, x)
    136             for each event in `x`.
    137         """
--> 138         return -self.log_prob(x)
    139
    140     def prob(self, x: Tensor) -> Tensor:

~/.conda/envs/cuda_test/lib/python3.6/site-packages/gluonts/mx/distribution/transformed_distribution.py in log_prob(self, y)
    147             y = x
    148
--> 149         return self.base_distribution.log_prob(x) + lp
    150
    151     def cdf(self, y: Tensor) -> Tensor:

~/.conda/envs/cuda_test/lib/python3.6/site-packages/gluonts/mx/distribution/inflated_beta.py in log_prob(self, x)
     80
     81         # mask zeros for the Beta distribution input to prevent NaN gradients
---> 82         inputs = F.where(F.logical_or(x == 0, x == 1), x.zeros_like() + 0.5, x)
     83
     84         # compute log density, case by case

AttributeError: module 'mxnet.symbol' has no attribute 'logical_or'

Looks like mx.nd has it while mx.sym doesn't have it. Maybe a fix is to use broadcast_logical_or, which appears to be in both

@deejlucas do you want to take a shot at this and open a PR?

@lostella Sure, I'll take a shot at it.

@lostella I've made this simple change and verified that my code runs. A couple questions about testing for you or anyone else who knows.

There are a set of tests that fail even when running pytest in master (including all tests in test/distribution/test_flows.py). Is this expected? Is it okay not to concern myself with tests that don't cover this change?
Now that the code is running, I get NA losses for all batches in the first epoch when I try to train a model on the data that originally motivated me to try this out. This happens for all sets of hyperparameters in a random search of a reasonable hyperparameter space. This is also the case when I try to use a set of state unemployment figures as the targets (something that seemed potentially appropriate based on literature). This may be outside of the scope of the issue, but I'm hesitant to put in a PR without training a model that actually works. Do you know of a dataset that is known to be suitable for this distribution?

@deejlucas

Yes that's fine, there are some tests which occasionally fail due to randomness, some of these could use some improvement but you don't have to worry about it.

You could try with the "traffic" dataset, which should have data in [0, 1].

@lostella
It seems like something is wrong with the log_prob function in the underlying beta distribution, and I'm afraid my ability to troubleshoot symbolic programming is coming up short.
The code below produces nan loss in the first epoch. I tried removing elements of the log_prob functions in Beta and determined that removing F.log(1 - x) prevents NaNs. This is confusing to me, as there's no reason I can think of that F.log(1-x) should be problematic when F.log(x) is not.
Should we consider this outside the scope of this issue? I've addressed the error that originally caused me to open this issue. I can do a PR of the trivial fix for that and open a new one for the issue described above, but it would be a PR to fix broken code, unless I'm really mixed up here.
If this is out of scope for this issue, I'd be happy to work on the new issue too, if someone a little more knowledgeable can point me in the right direction.
import numpy as np
import pandas as pd

from gluonts.dataset import common
from gluonts.model import deepar
from gluonts.mx.trainer import Trainer
from gluonts.mx.distribution.beta import BetaOutput

start = pd.to_datetime('1999-01-04')

train = []
for d in range(10000):
    train.append({"target": np.random.beta(0.1, 0.25, 1000), "start": start})

dataset = common.ListDataset(train, freq="W-MON", one_dim_target=True)

#%%
import mxnet as mx

trainer_1 = Trainer(ctx=mx.context.gpu(),
                      epochs=100,
                      batch_size=32,
                      learning_rate=1e-8,
                      minimum_learning_rate=5e-10,
                      weight_decay=1e-8
                    )

estimator_3 = deepar.DeepAREstimator(
    freq="W", prediction_length=24, trainer=trainer_1, distr_output=BetaOutput(),
    context_length=48, num_cells=96, dropout_rate=0.1
    )

predictor_3 = estimator_3.train(training_data=dataset)

@deejlucas does the problem arise on CPU too?

@lostella I get the same result (much more slowly :))

@deejlucas you can set hybridize=False and debugging will be much easier. I'm looking at it and indeed something looks off with Beta

@deejlucas found the issue, nothing wrong with Beta :-) you need to turn off the target scaling in the estimator:
DeepAREstimator(..., scaling=False)

Ah, that makes perfect sense! I'll get in the PR for this issue then. Thanks for taking a look at this with me

One note: I had to clip the target value because otherwise observations very close to 0 or 1 would still raise nans in your example. So I did it like this:
train = []
for d in range(100):
    target = np.random.beta(0.1, 0.25, 1000)
    target = np.clip(target, 1e-7, 1. - 1e-7)
    train.append({"target": target, "start": start})

This might be something that the distribution could handle internally when computing log_prob. On the other hand, one probably wants anything >=1 or <=0 to yield nans (e.g. to spot the scaling issue above), so blindly clipping within log_prob may not be ideal.


Still get refs/heads prefix in outputs

Description
I'm trying to get branch name from a direct branch push.
What I Did
Used ${{ steps.branch_name.outputs.ref_branch }} but still receive refs/heads/<branch> prefix in outputs.

This should be resolved


Spread must be the final element of an element list

I got this error with cardinal which I suppose uses esprima-fb under the hood:
Error: Unable to perform highlight.
The code contained syntax errors: Line 101: Spread must be the final element of an element list

The line is:
101| const partials = mergeTemplateItems(filterMatchingTemplates(...args, Types.PARTIAL));

The code compiles as expected with babel though. Am I using the spread operator wrong?

I'm not sure off the top of my head but esprima-fb isn't maintained any more, sorry. We've switched to Babel internally and suggest other people do too since it's much more actively maintained.


mentions.md file is missing

Hello,
I was reading the style guide in Puntuaction section and found out that @mentions article link is broken, the file mention.md is missing in repository.

Hi Rafa,
Thanks for your email. We are indeed having some issues with that link, so we are currently trying to solve this issue.
Thank you!
Maite
From: Rafa Moyano @.>
Sent: Saturday, March 13, 2021 1:51 AM
To: MicrosoftDocs/microsoft-style-guide @.>
Cc: Subscribed @.***>
Subject: [MicrosoftDocs/microsoft-style-guide] mentions.md file is missing (#212)
Hello,
I was reading the style guide in Puntuaction sectionhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fstyle-guide%2Fpunctuation%2F&data=04|01|v-maites%40microsoft.com|7012d38bf8ed428043bf08d8e5ba16b8|72f988bf86f141af91ab2d7cd011db47|1|0|637511934836042547|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=ubocec94Cr6xHdm8ShJgJCSPq%2FqQG8JpVwXfHmBZU%2FI%3D&reserved=0 and found out that @mentionshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fstyle-guide%2Fpunctuation%2F%40mention.md&data=04|01|v-maites%40microsoft.com|7012d38bf8ed428043bf08d8e5ba16b8|72f988bf86f141af91ab2d7cd011db47|1|0|637511934836052503|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=yPU%2FEE15n9Z%2BTKQDq9j3pIuoca2wVGNL0hzWxxJB2pI%3D&reserved=0 article link is broken, the file mention.md is missing in repository.

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-style-guide%2Fissues%2F212&data=04|01|v-maites%40microsoft.com|7012d38bf8ed428043bf08d8e5ba16b8|72f988bf86f141af91ab2d7cd011db47|1|0|637511934836052503|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Djy%2BX01WAKu4y3oBwgNcaN2pEzJ%2BFxEwgS1De9ebX4I%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FASXUAR2XE3E3D3MNKQH6S4TTDKZHXANCNFSM4ZDG5YLA&data=04|01|v-maites%40microsoft.com|7012d38bf8ed428043bf08d8e5ba16b8|72f988bf86f141af91ab2d7cd011db47|1|0|637511934836052503|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=DXQDS8ITe3AK%2FGNPxVh%2FjBW1xZow2qc7NM1kuvqd70k%3D&reserved=0.


Feature/switch to fhir valuesets

I also integrated lombok. When using lombok it is helpful to install a lombok plugin in the IDE (e.g. IntelliJ). Please, tell me your opinion about using lombok. I could remove it and readd the boilerplate code of getters and setters.
I need not adopt the Samply Parent POM to use Spring Boot. Instead I added the Spring Boot dependency management and the Spring Boot Maven Plugin.

remove maven wrapper
DONE
answer questions regarding URL machting and whitespace
CHANGED CODE
document usage of lombok in README
ADDED
add version to lombok in POM
The version is managed by Spring Boot.


add backtrack into readme

also fix ignoresmoke and backtrack chams to work with health based option enabled

Thanks.


deployment improvements

this goes along with the porter pull request in the terraform project.
This uses the gcp workload federation with github actions.
Removes pub/sub and calls directly to cloud run
Deploys cloud run and the scheduler in the action
TODO

Authorize the cloud run request

The request was not authenticated. Either allow unauthenticated invocations or set the proper Authorization header. Read more at https://cloud.google.com/run/docs/securing/authenticating

Mount secrets to the cloud run instance

Access secrets via the mount

Looks good to me so far.


Implement rendering of different items

Currently we are rendering apples for any item that gets set in our inventory - we should render the correct textures

Partially fixed by: https://github.com/Lea-fish/Leafish/pull/119


Consistent exceptions targeting user

We need a set of exceptions that will be used to notify the user of critical errors during parsing/run of adapters.
So far, there is some ValueError here and there.

See also issue #32


Fixed css

hi @MarkoAndrew93 you should only add the font 'Roboto' to pass this homework. Please do it

@MarkoAndrew93 please fix linter error


YAML considers most keys as "String", preventing automatic triggering of code completion

When typing in code, code completion is triggered automatically when typing. This is because non-comment/non-string tokens have a standard type of "Other" and the Quick Suggestions setting is "On" for "Other".
However, in YAML, typing bare keys at the top level are categorised as "String" so you don't get any completion unless you manually invoke it:

But some kinds of invalid syntax are set as "Other", which means code completion can automatically trigger in the case of invalid code:

It seems odd to have code completion automatically trigger for invalid code, but not for typing keys where it's more likely to provide some useful suggestions. I'm pretty sure it never used to work like this, I've had a few reports recently that this "stopped working".

dup: https://github.com/microsoft/vscode/issues/231224#issuecomment-2424546588

Related: https://github.com/microsoft/vscode/issues/231224

Not sure who owns YAML these days. @aeschli ?

basic auto word string suggestions are disabled by default because of how useless they are in YAML

I'm not sure what you mean is useless here. Do you mean editor.wordBasedSuggestions? Because that seems like a different issue. I support disabling editor.wordBasedSuggestions for YAML (actually, I recommend disabling it for everything, because it's useless everywhere IMO).
However, code completion shouldn't generally be disabled globally for YAML assuming that there are no extensions providing good values.
It's not clear to me whether categorising them as "string" is incorrect here, or whether "string" should be enabled for Quick Suggestions for YAML, but I feel like it should be one of those (I don't know which because I'm not sure "string" is very well defined here).

but VSCode broke "editor.quickSuggestions" in 1.94.0

Can you expand on what "broke" means here? Did YAML used to have different default settings? I don't want to change the users default settings for YAML (because I provide completion only for a small number of YAML files), but I do want completion to automatically trigger in the same way that is does for non-YAML (and I believe it used to for YAML).

Do you mean editor.wordBasedSuggestions?

Yes, I didn't know it was a separate setting

code completion shouldn't generally be disabled globally for YAML

editor.wordBasedSuggestions are the only completions available when there are no other YAML extensions
completions have always been (effectively) disabled for YAML

Can you expand on what "broke" means here?

Dup: https://github.com/microsoft/vscode/issues/231224

editor.wordBasedSuggestions are the only completions available when there are no other YAML extensions
completions have always been (effectively) disabled for YAML

Yep, but I don't think the settings/grammar should be such that if the user installs another YAML extension they need to also change settings for the completion to work. I don't see any reason for this. If YAML suggestions are bad by default, the fix is to disable wordBasedSuggestions for it by default IMO.

Can you expand on what "broke" means here?

Dup: https://github.com/microsoft/vscode/issues/231224

I read that issue but I don't understand how it's related. I'm not trying to use configurationDefaults - I'm asking for YAML completions to work reasonable with a YAML extension installed without either the extension or user having to override settings. We don't have to change settings to get completion for any other languages, and it's not clear to me why this would be intended for YAML.

I don't see any completions from the Dart extension.
fresh install VSCode 1.95.0

We don't have to change settings to get completion for any other languages

JSON, Docker and Markdown change the default "editor.quickSuggestions" settings
and so does these other extensions

I don't see any completions from the Dart extension.

Is the extension active and do you have a Dart SDK set up?

JSON, Docker and Markdown change the default "editor.quickSuggestions" settings

I don't think this makes it a good idea for some reasons I gave in https://github.com/Dart-Code/Dart-Code/issues/5320#issuecomment-2451913329. Having multiple extensions overriding settings can also lead to conflicts between them.
I don't understand why YAML completion shouldn't work sensibly out of the box like any other language.

I don't understand why YAML completion shouldn't work sensibly out of the box like any other language.

technically it is working exactly the same
strings disable auto completion like every other language
even the json extension supplies the same default settings
https://github.com/microsoft/vscode/blob/4fb64349bcd479e1a0be1a146fedc98264364f0b/extensions/json-language-features/package.json#L130

Having multiple extensions overriding settings can also lead to conflicts between them.

I don't think that's a problem
have you notice conflicts between default settings before?

Is the extension active and do you have a Dart SDK set up?

yes
can you confirm completions work with all other extensions disabled?

strings disable auto completion like every other language

Yes, but every other language doesn't consider almost everything a string. They consider things strings where code completion is almost certainly unwanted. The YAML grammar is categorising almost everything as strings.
IMO, the categorisation is wrong (see my original screenshots - why are some things string and some things other?) and if that was fixed (so everything was "other") that would also fix this problem.

have you notice conflicts between default settings before?

No, because I don't use any other YAML extensions. But what happens if two extensions try to set different values? They can't both apply, so one of them is not going to get the values it wants. But as pointed out above, my extension is not providing completion for all YAML files - it makes no sense for me to make settings changes for all YAML files (if those settings are "good", then they should be the defaults in VS Code).

can you confirm completions work with all other extensions disabled?

Yep (I actually hardly have any extensions anyway). Would you mind filing an issue at https://github.com/Dart-Code/Dart-Code so we can get some more info and try to track down why it's not working for you (save derailing this issue)? Thanks!

The new grammar hasn't been shipped with VSCode since Oct 11th now https://github.com/microsoft/vscode/pull/231096
both the old and new grammar mark everything as string in the same way
except the new grammar has new invalid tokens, which aren't always marked as string
which I may change in the future

If this is working as intended, then I feel VS Code should set the defaults for YAML appropriately

would you like VSCode to enable suggestions in strings by default?
the same as JSON?
https://github.com/microsoft/vscode/blob/13d2a615cb98a1dc3371dcea2f03d8e65b2d83e6/extensions/json-language-features/package.json#L130-L136


Flutter don´t start

Steps to Reproduce
I try to use Flutter, but always closes after I enter any command. The only return that I get it´s that:
after this message, the console closes

flutter_console.bat to

Flutter version --> 1.22.5
Windows --> 8.1
path --> C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\Python38\Scripts;C:\Program Files\Python38;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\nodejs;C:\Users\AGT\AppData\Local\Android\Sdk\tools;C:\Users\AGT\AppData\Local\Android\Sdk\tools\bin;C:\Users\AGT\AppData\Local\Android\Sdk\platform-tools;C:\ant\apache-ant-1.9.15;C:\Users\AGT\AppData\Local\Android\Sdk\tools;C:\Users\AGT\AppData\Local\Android\Sdk\platform-tools;C:\Program Files\Java\jdk1.8.0_271;C:\Gradle\bin;C:\src\flutter\bin;C:\Program Files\Git\cmd;C:\Windows\System32;C:\Program Files\Git\cmd\git.exe
Logs

Hi @AGTolosa
Can you please run from your terminal (making sure that flutter is added to your path)
flutter doctor -v

and provide the full logs.
Thank you

Please set path in environment variable : https://flutter.dev/docs/get-started/install/windows
And after that restart your terminal and check flutter command.

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.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.

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.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Fix all Linter warnings

Dev Docs PR
Description
Working on fixing all the linter warnings so we can start enforcing link checks.
Deadline
Casual.
Change type

[X] Doc bug fix. Fixes #DDI-93.

PR checklist:

[ ] My documentation follows the style guidelines of this project.
[ ] I previewed my documentation on a local server using mkdocs serve.
[ ] Running mkdocs serve didn't generate any failures.
[ ] I have performed a self-review of my own documentation.

@amplitude-dev-docs
@caseyamp

Thinking of a better way to handle this.


Girlscript Summer of Code Introduction/Tracking

👋 Hi @TAHIR0110,
I am Prince,web developer(Core Team) Girlscript Summer of Code. I'll be collaborating with you on preparing your repo for GSSoC'24 Program
Why are these changes required?
After Analysing last year's contributions and feedback it would be great for students to have a couple of standard readme files on the repo to understand what the project is all about and some issues detailing what they can contribute. This will help you to see increased engagement in your repository as well.
As mentioned students get a chance to learn step by step, how to build this project as well as invite mentors to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for Girlscript summer of code 2024 on 10th May.
This issue will serve as a tracking issue to track all issues related to GSSoC'24. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.
If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.
I look forward to working with you :octocat:

[ ] #4
[ ] #5
[ ] #6
[ ] #7
[ ] #8

Hello, I hope this message finds you well. I am well experienced in python with 5 stars in hackerrank and consistently learning ML. I want to gain hands on experience by contributing to this project through GSSOC'24. Please give me opportunity to contribute to this project. I hold a google data analytics course certificate of 6 months too. I have already completed a project named AI avatar generation in which I have already worked with sound using the librosa library and lipsync GANs. I have a deep knowledge of python,its libraries and frameworks. Please let me contribute to this isuue.

Greetings
This is Khush agrawal
i would like to work on this issue as a part of this year's GSSoC So please assign this issue to me


GSSoC: Announcement Banner for home page (Fixes #84)

I have added an introduction to the site on the home page via HomeIntro Component and made some CSS changes in Home Page to adjust it.
Fixes #84

Resolve the conflicts!

@Swarnendu0123 pls check


Yingjianw/list db with follower reader timestamp

As we see more dbs added to our metadata service, the load on crdb increases when there are many listDB calls, and we see only subset of certain nodes in our cluster experiencing high cpu usage.
Thus, in order to better spread the traffic, for list dbs operation, we are going to use the read_follower_timestamp.
Unfortunately, we need to rollback previous 2 commits as we don't want them to be included into the same rollout

To make things cleaner, could you first separate out the revert changes from the core logic changes?


Do not use parameters for private classes

Private classes with parameters make it possible for end-users to pass
custom values to these private classes via Hiera and break things.
If we do not have such parameters, we make breakage less likely.

You might need to adjust the rspec test to according to your changes.

Hum, I don't think these parameters where tested, and the CI is passing.  Do you have a point of attention in mind?

Nevermind - I have done it for you :D I think I didn't not express my needs correctly.


[authpolicy-v2] Well-known attributes in the generated AuthConfigs

Closes:

#265

Do you have an example verification steps that could be done manually?

Same ones from #256 will do. You should look for the diff in the generated AuthConfigs.


guild members

I'm trying to get guild.Members but I get this:
2023/09/17 22:36:53 error get discord users: HTTP 403 Forbidden, {"message": "Missing Access", "code": 50001}
exit status 1

code:
	members, err := disBot.GuildMembers(GUILD_ID, "", 1000)
	if err != nil {
		log.Fatalf("error get discord users: %v", err)
	}

(I should mention that the bot is in the server and has admin permissions)

Are you sure GUILD_ID isn't empty and has the id of the server you've mentioned?

@FedorLap2006 yes, this stuff is all correct!


Explain Camera2dBundle.projection needs to be set carefully

Encountered it while implementing https://github.com/bevyengine/bevy/pull/11109.

@matiqo15 I added comment in OrthographicProjection initially, but then decided it is more appropriate on Camera2dBundle, because OrthographicProjection can be used not only with 2D camera.

Makes sense, but I still think we should at least mention it in OrthographicProjection so that we can point users in the right direction. Would like to get someone else's opinion on this.

@rodolphito I suspect that might be

fragile to minor changes the project
may result in visual artefacts due to float rounding

But I don't really know.

I believe this needs to have main merged in; it's try to run CI checks that aren't available it seems.


How to implement Lucky 🍀 numbers algorithm  on C++?

According to https://github.com/AllAlgorithms/python/pull/32#issuecomment-426884796

Hi @zxey I liked, but it seems that the algorithm isn't properly implemented.

According to this the following gif:

From 1-100 the lucky numbers should be:
1, 3, 7, 9, 13, 15, 21, 25, 31, 33, 37, 43, 49, 51, 63, 67, 69, 73, 75, 79, 87, 93, 99

This is the link to your implementation repl.it/@abranhe/lucky-numbers-in-python online, I just set the range from 1 - 100.
In a part of the output you will see:
number 17 is not lucky
number 18 is not lucky
number 19 is lucky
number 20 is not lucky
number 21 is not lucky
number 22 is not lucky
number 23 is not lucky
number 24 is not lucky
number 25 is not lucky
number 26 is not lucky
number 27 is lucky
number 28 is not lucky

Where they don't match with the output it should be:
Eg:

19 isn't lucky
25 is lucky
27 isn't lucky
and so on ...

So this need to be fixed to be merged, I am creating an issue right now, hopefuly we will implement correctly.

After finding this issue on Python I went back again to C++ to double check if the algorithm was ok, but cpp/lucky numbers doesn’t seem right at all.
We need to find the a correct implementation for Lucky Numbers!

This issue will be closed since it was fixed on #83


Color Contrast discrepancy

I'm getting a color contrast failure on a test when running this package that I don't receive in the browser. The test environment is "seeing" different hex codes than what are set in code. To debug I tried changing the failing foreground color to css 'hotpink': #ff69b4.
Here are the values I get in the error message across all three test browsers:

Actual Hex Code
Chromium
Firefox
Webkit

#ff69b4
#fedd9c
#ff9aaa
#ff71b2

None of them match the actual hex code. I have no idea what's happening here. Any thoughts?

Weird! Thanks for the issue report.
Couple questions:

Is there any transparency or opacity on any elements in the component?
Are there any animations or transitions (especially on opacity)?
Are you using storybook's a11y addon?

Is there any transparency or opacity on any elements in the component?
No. These are solid hex codes in CSS.

Are there any animations or transitions (especially on opacity)?
No, I've disabled all animations.

Are you using storybook's a11y addon?
I'm not exactly sure how to do this. I put it first in the list of addons in .storybook/main.js. Is that all it takes?

I put it first in the list of addons in .storybook/main.js. Is that all it takes?

Yes, I believe that's all it takes.
Also, can you:

Post a screen shot of the component rendered in storybook (if you're able. I'm assuming it's not secret or anything)
Let me know which version of axe-core you're using

In the screenshot I reverted the text from `hotpink` back to `#002B3F`.
Version
<EMAIL_ADDRESS>Full error message
1. color-contrast (Elements must have sufficient color contrast)

          For more info, visit https://dequeuniversity.com/rules/axe/4.3/color-contrast?application=axeAPI.

          Check these nodes:

          - html:
Use the Controls tab in addons panel to modify the story

            summary: Fix any of the following:
                       Element has insufficient color contrast of 1.4 (foreground color: #d2c48a, background color: #fee59a, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

          - html: Controls
            summary: Fix any of the following:
                       Element has insufficient color contrast of 1.4 (foreground color: #d2c48a, background color: #fee59a, font size: 12.0pt (16px), font weight: bold). Expected contrast ratio of 4.5:1

Thanks for the info. It's weird that the foreground color is showing up as #d2c48a.
Couple more things to try

If you run the tests again, does the #d2c48a change or stay the same? If it changes, that usually means there's some sort of transition.
If you run non-headlessly with the --headless=false CLI flag, does anything change?
What version of axe-storybook-testing are you on? v4 upgraded the version of Playwright that's used (Not sure if that would effect this or not)
Can you share what styles are applying to the element? (Only if the code is open source)

If you run the tests again, does the #d2c48a change or stay the same? If it changes, that usually means there's some sort of transition.

I switched to a different branch and then back. Oddly the foreground changed to #eed994. I've now re-run the tests three times and consistently get #eed994.

If you run non-headlessly with the --headless=false CLI flag, does anything change?

--headless=false still results in: #eed994
But headless false reveals a transition I wasn't aware of. The element is fading in.

What version of axe-storybook-testing are you on? v4 upgraded the version of Playwright that's used (Not sure if that would effect this or not)

<EMAIL_ADDRESS>

Can you share what styles are applying to the element? (Only if the code is open source)

I'll dig into this if I can't fix the transition issue that seems to be causing the problem

@ahuth thanks so much for helping me troubleshoot. Disabling the transition solved the failing test.
BTW, I'm loving this storybook/a11y/CI solution. Wish I'd found it sooner.

No problem!
These tests run with prefers-reduced-motion forced to on. So one thing you can do is turn off any transitions when the prefers-reduced-motion media query matches.
Glad you're getting use out of this project!


API not working properly in angular 2.

I am getting javascript from a bin( jsbin ). After that i pass it to JSHINT(soure) to check for errors. But unfortunately an error occurs when i try to do this. The javascript code is as follows,
window.addEventListener('load',function(){     var ele = document.getElementById("haha");     ele.innerHtml = " empty"; });
And, i am writing this in my angular2 component:
this.jsBinService.getBinJs().subscribe( data => {      	jshint.JSHINT(data);     	console.log(jshint.JSHINT.data());     });

Hmm, I can't reproduce the error (I've included my attempt to reproduce below).
Can you provide some more information:

The error you are experiencing. Is this a linting error being reported by
JSHint, or is it JavaScript error being thrown by the run time?
The version of JSHint you are using

Thanks!
var jshint = require('../jshint');
var src = 'window.addEventListener(\'load\',function(){ var ele = document.getElementById("haha"); ele.innerHtml = " empty"; });'

jshint.JSHINT(src);
console.log(JSON.stringify(jshint.JSHINT.data(), null, '  '));

{
  "functions": [
    {
      "name": "(empty)",
      "param": null,
      "line": 1,
      "character": 41,
      "last": 1,
      "lastcharacter": 114,
      "metrics": {
        "complexity": 1,
        "parameters": 0,
        "statements": 2
      }
    }
  ],
  "options": {
    "indent": 4,
    "maxerr": 50
  },
  "implieds": [
    {
      "name": "window",
      "line": [
        1
      ]
    },
    {
      "name": "document",
      "line": [
        1
      ]
    }
  ],
  "member": {
    "addEventListener": 1,
    "getElementById": 1,
    "innerHtml": 1
  }
}

It's been a few weeks, so I'm assuming you've worked this out. Let me know if that's not the case, and we can re-open this issue.

Issue is resolve d thanks:)😃
On 25-Mar-2017 10:00 PM, "jugglinmike"<EMAIL_ADDRESS>wrote:

It's been a few weeks, so I'm assuming you've worked this out. Let me know
if that's not the case, and we can re-open this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jshint/jshint/issues/3096#issuecomment-289222681, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMr9GSRSnRPykmCNZd1NFcEwsl_o4E7Xks5rpUE4gaJpZM4Lyq_N
.


Moderation Omni - New Categories (Illicit*) support.

What:

[x] Bug Fix
[ ] New Feature

Description:
The Omni Moderation models were released, thus deprecating the older models (now referred to as Legacy). This introduced the illicit and illicit/violent moderation category, but ONLY for Omni. This presented an issue as this library iterated all known types and assumed all models will have it.
Now we only set a Category if we have it and thus support partial support of Omni Moderation.
Ref: https://platform.openai.com/docs/guides/moderation
This does NOT add support for the new category_applied_input_types field.

Thanks @iBotPeaches for the PR 🥳


Is Station shutting down? Which app should we use instead?

There are multiple threads about Station no longer working with Google sign-in which makes it effectively useless for anyone who either uses Google apps or signs on with Google. That affects almost everyone.
There hasn't been any reply on the message boards about these issues so can we assume Station is shutting down?
If so, what apps should we migrate to?

Ferdium is cool but searching for every app is not available.

Just in case someone else stumbles on this

https://github.com/albertlauncher/albert
https://github.com/Wox-launcher/Wox
https://github.com/cerebroapp/cerebro

Thats what i found thats somewhat active.

I'm confused, so its a live again? A comment would be amazing ^^ Its closed as not planned but at the same time there is 2.1.0. But the readme is still "not active, just PR"


Release Google.Cloud.Gaming.V1 version 1.0.0

Changes in this release:
First GA release.

Commit 0ca05f5: chore: Regenerate all APIs using protoc 3.13 and Grpc.Tools 2.31

Created release for Google.Cloud.Gaming.V1-1.0.0


WebGUI: Runtime Error ASSERTION_FAILED in zcl_abapgit_serialize

Hi all,
When trying to connect to an online repository via WebGUI, I get an ASSERTION_FAILED runtime error in zcl_abapgit_serialize (line 482, after the Z_ABAPGIT_SERIALIZE_PARALLEL function call in method run_parallel). sy-subrc has value 2 and lv_msg says "RFC task 2 already open".
Details:

Happens only with the non-standalone abapGit via WebGUI. For the standalone version (no matter if SAPGUI or WebGUI) or in SAPGUI (no matter if standalone or not) the issue is not present.
SAP_BASIS 757
abapGit version 1.113.0

Any ideas?
Best,
Jonathan

Can you try to disable parallel processing?

OK, with parallel processing disabled it's working.  For me this is OK right now. Just let me know if somebody wants to track the issue down and needs more information.
Thanks,
Jonathan
PS: Changing the setting itself for me works only in SAPGUI. When I "Save Settings" (see screenshot above), I get a new WebGUI screen within the existing WebGUI screen, but nothing is saved. But this is another topic...

Yeah, let's keep the issue open. Btw. I don't have this issue in WebGUI when parallel processing is enabled.
WebGUI has several quircks...

The standalone version does not run anything in parallel (since the function group is not part of it).
WebGUI has known limitations (no popups, etc) so not something you should use on a regular basis. The issue with nested frames is known (https://github.com/abapGit/abapGit/issues/4433) and reproducible. Unfortunately, no workaround is available currently.
Back to your issue, the explanation for the error is in SAP Note 1060205.   We will have to check the code to see if we handle the task names correctly.

you are right, of course. i mixed up with plain web version (via sicf).

I had a closer look. The error can indeed occur if there are resource issues. If there are not sufficient dialog processes available, then the following do-loop might try to call Z_ABAPGIT_SERIALIZE_PARALLEL several times using the same task name. This will lead to the "RFC task  already open" error as described in Note 1060205.
Please check if #5269 prevents this error


Issue with parameters of type file in the client generator

The client generator has an issue with parameters of type file. For example, for the following swagger spec:
  /services/{serviceId}/files:
    post:
      operationId: CreateServiceFiles
      consumes:
        - multipart/form-data
      parameters:
        - name: files
          in: formData
          required: true
          type: file

In the CreateServiceFilesParams struct, the field Files is of type os.File, but is later compared to nil. It should either be of type *os.File, or the nil comparison should not be there.
We need this for one of our projects at SAP. It seems to be a rather small and straightforward change, I would like to contribute a PR for it.

I have a branch for this but I couldn't reproduce your issue. Can you check if it's ok now?

The issue is no longer reproducible with the newest generator, built from source. Thanks a lot for fixing it!