Data fail to install

When I try to install data on MacOSx with the following command:
bcbio_vm.py --datadir=~/install/bcbio-vm/data install --data --tools --genomes GRCh37 --aligners bwa
I get the following error message and no data file are installed.
Thanks for your support!
INFO: Extracting RNA-seq references: GRCh37-rnaseq-2014-07-14.tar.xz
tar: GRCh37/rnaseq-2014-07-14/ref-transcripts.gtf.db: Wrote only 5120 of 10240 bytes
tar: GRCh37/rnaseq-2014-07-14/ref-transcripts.genePred: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/ref-transcripts.refFlat: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/ref-transcripts.dexseq.gff: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/ref-transcripts-mask.gtf: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/rRNA.gtf: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/rRNA.gtf.db: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/rRNA.interval_list: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/tophat/GRCh37_transcriptome.gff: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/tophat/GRCh37_transcriptome.fa: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/tophat/GRCh37_transcriptome.fa.tlst: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/tophat/GRCh37_transcriptome.ver: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/tophat/GRCh37_transcriptome.3.bt2: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/tophat/GRCh37_transcriptome.4.bt2: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/tophat/GRCh37_transcriptome.1.bt2: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/tophat/GRCh37_transcriptome.2.bt2: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/tophat/GRCh37_transcriptome.rev.1.bt2: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/tophat/GRCh37_transcriptome.rev.2.bt2: Cannot write: No space left on device
tar: GRCh37/rnaseq-2014-07-14/tophat/large_exons.gtf: Cannot write: No space left on device
tar: Exiting with failure status due to previous errors
Fatal error: local() encountered an error (return code 2) while executing 'xz -dc GRCh37-rnaseq-2014-07-14.tar.xz | tar -xpf -'
Aborting.
Upgrading bcbio-nextgen data files
Setting up virtual machine
[localhost] local: cat /etc/*release | grep DISTRIB_CODENAME | cut -f 2 -d =
[localhost] local: cat /proc/version
[localhost] local: cat /etc/issue
[localhost] local: cat /etc/*release | grep DISTRIB_CODENAME | cut -f 2 -d =
[localhost] local: echo $HOME
[localhost] local: uname -m
[localhost] local: mkdir -p /usr/local/share/bcbio-nextgen/genomes/Hsapiens/GRCh37
[localhost] local: pwd
[localhost] local: echo $HOME
[localhost] local: mkdir -p '/root/tmp/cloudbiolinux/2d48e41c-2b04-38f0-96e7-e3ca48f3e875'
[localhost] local: wget --continue --no-check-certificate -O GRCh37-rnaseq-2014-07-14.tar.xz 'https://s3.amazonaws.com/biodata/annotation/GRCh37-rnaseq-2014-07-14.tar.xz'
[localhost] local: mv GRCh37-rnaseq-2014-07-14.tar.xz /usr/local/share/bcbio-nextgen/genomes/Hsapiens
[localhost] local: rm -rf /root/tmp/cloudbiolinux/2d48e41c-2b04-38f0-96e7-e3ca48f3e875
[localhost] local: xz -dc GRCh37-rnaseq-2014-07-14.tar.xz | tar -xpf -
local() encountered an error (return code 2) while executing 'xz -dc GRCh37-rnaseq-2014-07-14.tar.xz | tar -xpf -'
' returned non-zero exit status 1
Stopping docker container
bcbio-nextgen-vm updated with latest bcbio-nextgen code and third party tools and biological data

Thanks for trying out bcbio. It looks like the disk you're installing on ran out of space:
Cannot write: No space left on device
tar: Exiting with failure status due to previous errors

If you clear up some additional space and restart it should kick off where it left off. Hope this helps.


added code to fix issue with wrong dashboards showing up upon update

PR to add code to fix issue with wrong dashboard displaying when committing an edit on a post. Also cleaned up various code.

update


bPermissions, single world TP doesn't seem to be working.

Multiverse version 2.4
bPermissions 2.12
Developing a new small server, and wanting our default group to be able to jump between two worlds

- multiverse.teleport.self.creative
- multiverse.teleport.self.world

I'm only able to allow this group to teleport using the /mv tp command by giving them

- multiverse.teleport.*

Full permissions file
default: default
groups:
  default:
    permissions:
    - bpermissions.spawn
    - commandbook.rules
    - commandbook.spawn
    - commandbook.time.check
    - multiverse.core.info
    - multiverse.core.list.worlds
    - multiverse.core.spawn.self
    - multiverse.core.tp.*
    - multiverse.core.tp.self
    - multiverse.teleport.*
    - multiverse.teleport.self.creative
    - multiverse.teleport.self.world
    groups: []
    meta:
      prefix: §4[Guest]§r
  student:
    permissions:
    - antibuild.bypass
    - commandbook.home.set
    - commandbook.home.teleport
    - commandbook.msg
    - commandbook.mute
    - commandbook.say
    - commandbook.say.me
    - commandbook.warp.list
    - commandbook.warp.teleport
    - worldedit.selection.*
    - worldguard.region.addmember.own.*
    - worldguard.region.addowner.own.*
    - worldguard.region.claim
    - worldguard.region.info.own.*
    - worldguard.region.removemember.own.*
    - worldguard.region.removeowner.own.*
    groups:
    - default
    meta:
      prefix: §4[CMS]§r
  staff:
    permissions:
    - commandbook.home.teleport
    - multiverse.teleport.self.world_nether
    - multiverse.teleport.self.world_the_end
    - worldguard.region.*
    groups:
    - default
    - student
    meta:
      prefix: §4§l[Staff]§r
  guest:
    permissions: []
    groups: []

Closing due to issue age (sorry). We slacked off on our issues. If you're still having this issue, please read up on submitting a bug and post the details with a more recent server/multiverse version. Sorry again!


Playlist items always showing 7 items

Describe the bug
Everytime I tried to pull tracks from playlist its always give me up to 7 instead of the limit (100). I did check all playlist and give me 7 too. Any idea what I missed? I check the limit and it is 100.
Your code
result = sp.playlist_items(playlistID, additional_types=['track'])
                available_tracks = len(result)

Expected behavior
Give me more than 7

This is definitely strange! Can you confirm that you are checking different playlists i.e. that playlistID is not always set to the same playlist, or perhaps check this with print([item['track']['name'] for item in result]). Some replicable code would be appreciated as well - currently, I'm fetching up to the specified limit.

I did check it and I try all of the available playlist and give me same results which 7 tracks only per playlist.

I'm not entirely sure, though I'll keep investigating for you - in the meantime, note that results are buffered based on the limit, try the following:

Explicitly set limit=100 e.g. spotify.playlist_items(playlistID, additional_types=['track'], limit=100)
Use the below code to fetch ALL the tracks.

As an example:
data_stream = spotify.playlist_items(playlistID, additional_types=['track'], limit=100)
all_tracks = []

while data_stream:
    all_tracks.extend(data_stream['items'])
    data_stream = spotify.next(data_stream)

available_tracks = len(result)

This code is necessary for long playlists above the set limit as multiple requests are necessary.
Let us know if doing either 1) or 2) yields any difference!

result does not directly contain the items, try len(result['items']) instead

@stephanebruckert yes that solved the issue. Sorry my bad and thanks @Quizz1Cal too!


(kubelogin) Not available as kubectl plugin

Chocolatey Version
2.2.2
Chocolatey License
None
Package Version
1.28.0
Current Behaviour
After installing the package the plugin is not available to kubectl as expect, running kubectl plugin list yields no results.
The kubectl plugin mechanism expects the kubelogin binary to be on your path under the name kubectl-oidc_login.
Expected Behaviour
kubectl plugin list should list kubelogin
Steps To Reproduce

Run choco install kubectl
Run choco install kubelogin
Run kubectl plugin list

Environment
- Operating System: Microsoft Windows NT 10.0.22621.0
- PowerShell Version: 5.1.22621.1778
- Shell: Windows PowerShell

Chocolatey Log
NA

Anything else?
The original package author @jetersen is of the opinion that the the file should not be renamed, and is/was using kubelogin.exe on path to use in the kubeconfig for Windows, see https://github.com/chocolatey-community/chocolatey-packages/issues/2074
It is my expectation that by installing kubelogin, which is a kubectl plugin, it should 'just work' as a plugin without additional steps, perhaps things evolved over time that it doesnt fully work as expected, and given it maybe used as per the original package author, I think adding an alternative shim with the expect kubectl plugin name format would work?

Resolved in
https://github.com/chocolatey-community/chocolatey-packages/pull/2283

@jetersen thanks for the reminder!  I will go ahead and close out this issue!


Receipt: override operator image

As a pull request owner and reviewers, I checked that:

[X] Appropriate documentation exists and/or is up-to-date:

[X] Content of the docs/source is reflecting the changes

/lgtm

I'll let people with the right knowledge take over this PR - imho that's the best :). I'm obviously missing some pieces, having either @Sandeepyadav93 or @viroel take over the content would be for the better.

/hold
so that it won't merge before corrections - and it should allow anyone to unhold it once ready.

Not relevant anymore


How to start a phone-based ctc training

Hi all,
I'm trying to train a phonetic alignment model in the aishell-1 dataset. The Conformer-CTC pre-train model is good enough at the char level, but at the phone level, there is only a Conformer-MMI model that can be used, which has a different TrainingGraphCompiler from the CTC model.
What I noticed is the tokens.txt under data/lang_phone folder which does not include sos/eos and <blk> tokens but includes <eps>, <SIL>, <SPN> and disambig tokens. So does it possible to start a phone-based ctc training by simply changing  tokens.txt,  L.pt files and continuing to use CharCtcTrainingGraphCompiler?
Thanks a lot.

https://github.com/k2-fsa/icefall/tree/master/egs/librispeech/ASR/tdnn_lstm_ctc
This recipe is also using a phone-based modeling unit. It is the very first recipe we have and its performance is no as good as our recent ones.

https://github.com/k2-fsa/icefall/tree/master/egs/librispeech/ASR/tdnn_lstm_ctc
This recipe is also using a phone-based modeling unit. It is the very first recipe we have and its performance is no as good as our recent ones.

Thanks for your recommendation. I have successfully trained a phone-based conformer-ctc with CER 9.5% at epoch 30 by creating a PhoneCtcTrainingGraphCompiler combined compile function of CharCtcTrainingGraphCompiler and lexicon of MmiTrainingGraphCompiler.
As for the phonetic alignment results, the timestamp of the phone-based model is severely backward-biased compared to the char-based model. The start frame of the consonant is nearly the middle of the char.


The portmidi library is not thread safe.

This means the current design of &aplay can lead to a few different failure modes.
This discussion with jnthn++ has details for the likely reason as well as a design suggestion how to avoid this issue.

This branch (which will be merged into master soonish) solves the "really bad" failure modes, which include e.g. "Host error"s or segfaults. Closing this issue, because the remaining async issues in Audio::MIDI::Note are covered with issue #1.


UnhandledPromiseRejectionWarning: TypeError: No path specified

I'm trying to run the Cyton example code and I'm getting a "No path specified" exception
Here's the code that I'm using:
const { Cyton } = require('openbci-observable');

async function init () {
    const cyton = new Cyton();
    await cyton.connect();
    await cyton.start();

    cyton.stream.subscribe(sample =>
        console.log('sample', sample)
    );
}

init();

Inside new Cyton(), the init function calls autoFindOpenBCIBoard(), which tries to find a valid serial port.  If successful, it ends with this code:
          if (this.options.verbose) console.log('auto found board');
          resolve(this.portName);

However, this doesn't block the call to await cyton.connect(); which tries to connect to portName which is undefined.

I tried to delay the call to connect by doing this:
const { Cyton } = require('openbci-observable');
async function init () {
    const cyton = new Cyton({ verbose: true });
    setTimeout(async function () {
        await cyton.connect();
        await cyton.start();
        cyton.stream.subscribe(sample =>
            console.log('sample', sample)
        );

    }, 1000);
}
init();

However, I noticed that the call to connect() is actually blowing away the portName.
Cyton.prototype.connect = function (portName) {
...
      this.portName = portName;
      if (this.options.verbose) console.log('using real board ' + portName);
      this.serial = new SerialPort(portName, {
...

So, calling connect() with no arguments will not work.
I changed the line in my code to await cyton.connect(cyton.portName);, now will use the auto discovered serial port.

This however doesn't solve the problem of connect(portName) being called before the constructor has resolved the port in the constructor's call to the init() function.  Since a constructor doesn't return a promise, I don't know if we can await it.  However, if I just resign to auto-discover the port a second time, I can await on that.
This is my code that can successfully connect to my Cyton board and stream data:
const { Cyton } = require('openbci-observable');
async function init () {
    const cyton = new Cyton({ verbose: true });
    await cyton.autoFindOpenBCIBoard();
    await cyton.connect(cyton.portName);
    await cyton.start();
    cyton.stream.subscribe(sample =>
        console.log('sample', sample)
    );
}
init();

If it helps.  I'm using Mac OS X 10.13.3, with node version 9.8.0.


Fix download of artifacts

Download of artifacts failed due to mismatched versions of the download/upload-artifact workflows

Hoffentlich...


vsCode problem

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/run
Operating System: macos
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

?????

I think you've found a bug in dotnet run: it doesn't work when your path contains a directory that ends with a period (in your case, taigermos.). I can reproduce it on Ubuntu:
~$ mkdir 'app.'
~$ cd app./
~$ dotnet new console
The template "Console Application" was created successfully.

Processing post-creation actions...
Running 'dotnet restore' on /home/svick/app./app..csproj...
  Restore completed in 183.13 ms for /home/svick/app./app..csproj.

Restore succeeded.

~/app.$ dotnet run
Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly '/home/svick/app./bin/Debug/netcoreapp3.0/app..dll'. The system cannot find the file specified.

File name: '/home/svick/app./bin/Debug/netcoreapp3.0/app..dll'

Can you try running the tutorial in another directory, that's not under your home directory?

至于错误，它似乎已在.Net 5中修复。

thanks


Add Livespotting into powered-by-mesos.md

Thanks for inclusion

Committed as:
commit 71b47658e411456df4a34491ea82bd4115f70479
Author: Jan Stabenow<EMAIL_ADDRESS>Date:   Wed May 25 12:23:30 2016 +0200

    Add Livespotting into powered-by-mesos.md.

    This closes #106

@tillt thanks :-)


White screen after re-launch with "Open app in fullscreen" enabled

I confirm (by marking "x" in the [ ] below: [x]):

[x] This is not a troubleshooting question. Troubleshooting questions go here: https://docs.mattermost.com/install/troubleshooting.html.
[x] This doesn't reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
[x] I have read contributing guidelines.

Summary
App shows white screen after re-launch if Open app in fullscreen option is selected.
Environment

Operating System: macOS 12.4
Mattermost Desktop App version: 5.10
Mattermost Server version: 7.0.0

Steps to reproduce

Select Open app in fullscreen in App Options
Close App
Reopen App

Expected behavior
App shows UI
Observed behavior
App shows white screen

Looks like the BrowserView isn't being drawn correctly when the app opens in full-screen.
@leitmori A workaround for now would be to switch tabs or servers back and forth, but I'll make a fix.
Created a ticket: https://mattermost.atlassian.net/browse/MM-45203

@leitmori It looks like this is fixed in the nightly builds. Can you confirm for me?
You can find the nightlies here: https://community.mattermost.com/core/channels/desktop-builds

Great! I'll mark this as Closed then.


Showcase stronger examples

Hi! Thanks for drafting this proposal. I certainly feel the pain behind every example provided in the README. However, I must admit all of them can be solved and in a more elegant way than creating a write-once const. Allow me to demonstrate.
Example 1
let value;

if (someCondition) {
  value = 1;
} else if (someOtherCondition) {
  value = 2;
} else {
  value = 3;
}

This isn't really an assignment of value but computing of value. There's a logic to that computing (conditionals), and so it belongs to a function:
function computeValue() {
  if (someCondition) return 1
  if (someOtherCondition) return 2
  return 3
}

const value = computeValue()

This is a great pattern that makes the computation explicit, testable in isolation (and you do need to test computeValue!), and keeps the original assignment to value simple while still using const.
Example 2
let value1, value2;

if (someCondition) {
  value1 = 1;
  value2 = 5;
} else if (someOtherCondition) {
  value1 = 2;
  value2 = 10;
} else {
  value1 = 3;
  value2 = 15;
}

This should be solved by moving out the computation for value1 and value2 as well. However, since the emphasis of this example is in multiple values, and those values are assigned based on shared conditions, this strongly suggests that a choice of a better data structure should be considered.
function computeValue() {
  if (someCondition) {
    return { a: 1, b: 5 }
  }

  if (someOtherCondition) {
    return { a: 2, b: 10 }
  }

  return { a: 3, b: 15 }
}

const value = computeValue()
// value.a / value.b

Collocation on the data structure level is generally beneficial but you can disregard this suggestion if the relevance of value1 and value2 is purely coincidental. If it is, then the same suggestion from Example 1 applies without fault to this one.
Example 3
async function doSomething() {
  let result;

  try {
      result = await someOperationThatMightFail();
  } catch (error) {
      return;
  }

  doSomethingWith(result);
}

This is a common pitfall when handling async/await. And yet I don't think it has to be solved on the const level.
Take a look at my approach to this problem in until:
const [error, value] = await until(() => someOperationThatMightFail())

I'd argue this example is out of scope of your proposal as it involves not only the value assignment but also error handling, which you can neither disregard nor accommodate within the current proposal.

If anything, this hints at a different proposal to help wrap async/await operations in something like until. A Promise.until(), perhaps?

Concerns
In general, I see the proposal to the change of the const behavior to be detrimental to the expectations and the benefits which the const was designed to provide.
Please note that per original intention, const is only ever meant to be used for module-wide constants. It never stood for an immutable version of var, but it often gets misused that way. Overall, let is preferred for variable assignments, and it already behaves as you are proposing.

TLDR const for top level module-scope constants only, and SCREAMING_CASE only.
— Source

I know this is somewhat controversial but if the folks behind the spec say we are misusing const then, perhaps, we are misusing const. Suggesting additional, branching behaviors to it will not make things easier.

Thanks for the feedback. Indeed, I intentionally did not show refactors using functions because it's pretty clear that most developers are not doing that, otherwise I wouldn't be able to find examples of the patterns I mention. (Finding these patterns in the ESLint source code is what led me to write up this proposal.) I added a new FAQ to cover this because you're the second person to ask about it.

Please note that per original intention, const is only ever meant to be used for module-wide constants. It never stood for an immutable version of var, but it often gets misused that way. Overall, let is preferred for variable assignments, and it already behaves as you are proposing.

Through ESLint, I've been watching how people are actually using const and let for nine years now. Very shortly after ES2015 was released, people started using const not just for module-wide constants, but for any immutable bindings. That's why prefer-const is such a popular ESLint rule. At this point, I think it's fair to say that const is a general-purpose immutable binding.
Your point about getting better examples is a good one. I think it's important for the explainer to show simple examples that illustrate the usage patterns and then link off to more complex, real-world examples (as I did with the try-catch use case). I'm continuing to look for those real-world examples, but there's only so many hours in the day. :smile:

I also profoundly disagree that const was only "intended" for module-level constants - it was intended for any binding that can't be reassigned, which is how it's used.

@ljharb, I believe I'm quoting one of the folks who worked on the spec. I agree with you, in practice it's used completely differently. Keeping the specs in-line with reality is a commendable effort, and if this proposal makes it so, it would be good.

That's just one person, 2+ years after the feature was shipped in the spec. That does not reflect the intent of the committee, only the opinion of one person.

@nzakas just to offer another voice here, I saw your examples and thought they were great and immediately understandable and following much of code in the wild 👍
More examples are always good, but the existing ones are very good motivators in my opinion.

Thanks @karlhorky 🙏


Update README

Attach some screenshots from website

Should we add #7 and #6 in the readme itself?


disable days via setDisabled

Now days can be disabled and therefore can not be selected. disabled attribute is added/removed to/from each day link tag, and selectDay is not called if disabled is present.

thanks for the contribution


different BIC with same parameters

I run example with same parameters 3 times and I am getting different BICs. Initially, I wanted to try different number of clusters and based on minimum BIC, identify number of clusters and that was when I found out that every run with same parameters and dataset yielded different BICs. Could you please explain why BIC vary while parameters and data are the same.

Hmm, that definitely shouldn’t be happening. Are you sure you’ve pulled the newest version of the code? This might have to do with issue #30 , where we used a different random seed every time we ran TICC. Can you try re-pulling and running again? Thanks!

I used the new version and it is resolved. Thanks!

Great, glad that fixed it!


Create student.txt for Rudolf Diesel Gymnasium Augsburg

@philipp1808 I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host student.rdg-online.de not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


Corrected and Improved Items display in Log

Transform typical json strings into user friendly text
Check for item words by descending length (because 'Super Potion' contains 'Potion', the icon was showing twice)
Parse quantities and display count next to icon
Specific icons for specific actions

Hey! Thanks for your time, unfortunatly we've been reworking the whole app for some times now in the vuejs-rework-gulp branch.

@Outpox y u no make minor updates :(

'Cause we remade the build process and changed the tools used. It will allow us to work much faster once it's done.

@Outpox Wish you all the best to get it done soon and polished! I am so thankful! :heart_eyes:

OK, I understand. If you are interested by the change, tell me whenever you are ready with the reworking activity, and I can port it wherever you want it to be.

Yep, that's why I didn't close the PR in the first time :P

yo @Outpox how's it going?


toascii - Opaque Capture Addresses Output as Decimals

Addresses in the toascii output should be strings with hex formatted numbers withing them.
Functions like vkGetBufferOpaqueCaptureAddress are having their return values output as decimal integers rather than strings with hex formatted numbers embedded, as is visible in our VulkanAsciiConsumer::Process_vkGetBufferOpaqueCaptureAddress().
Our other functions of interest are:
Process_vkGetBufferOpaqueCaptureAddressKHR
Process_vkGetDeviceMemoryOpaqueCaptureAddressKHR

Or is this actually a P1 because the values could be very large and unrepresentable in JSON legally?

Or is this actually a P1 because the values could be very large and unrepresentable in JSON legally?

The JSON can hold it, and a Python number in a parser for that language should*, but some JSON parsers (e.g. ones that leverage json being legal Javascript) use doubles for numbers and so could theoretically have a problem.
GPU's would have to be returning virtual addresses rather than physical ones and be allocating way up high in the upper pebibyte range to run out of integer bits in a double though, and even Windows server on CPUs stays in the 128 TiB range.
I think this gets promoted to P1 the day our format gets a schema, because traces with these pointers will fail schema validation at that point.
* Python default to bignum integers that go way over the 64 bits we might need:
Python 3.10.4 (main, Jun 29 2022, 12:14:53) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> a = 256
>>> a *= 256; print(a)
65536
>>> a *= 256; print(a)
16777216
>>> a *= 256; print(a)
4294967296
>>> a *= 256; print(a)
1099511627776
>>> a *= 256; print(a)
281474976710656
>>> a *= 256; print(a)
72057594037927936
>>> a *= 256; print(a)
18446744073709551616
>>> a *= 256; print(a)
4722366482869645213696
>>> a *= 256; print(a)
1208925819614629174706176
>>> a *= 256; print(a)
309485009821345068724781056
>>> a *= 256; print(a)
79228162514264337593543950336
>>> a *= 256; print(a)
20282409603651670423947251286016
>>> a *= 256; print(a)
5192296858534827628530496329220096
>>> a *= 256; print(a)
1329227995784915872903807060280344576
>>> a *= 256; print(a)
340282366920938463463374607431768211456
>>> a *= 256; print(a)
87112285931760246646623899502532662132736
>>> a *= 256; print(a)
22300745198530623141535718272648361505980416
>>> a *= 256; print(a)
5708990770823839524233143877797980545530986496

Note for the fix:
diff --git a/framework/generated/vulkan_generators/vulkan_ascii_consumer_body_generator.py b/framework/generated/vulkan_generators/vulkan_ascii_consumer_body_generator.py
index 1385538..d16a66a 100644
--- a/framework/generated/vulkan_generators/vulkan_ascii_consumer_body_generator.py
+++ b/framework/generated/vulkan_generators/vulkan_ascii_consumer_body_generator.py
@@ -170,6 +170,8 @@ class VulkanAsciiConsumerBodyGenerator(BaseGenerator):

         # Handle function return value
         if not 'void' in return_type:
+            if 'VkResult' != return_type:
+                print(name, " -> ", return_type)
             body = '            FieldToString(strStrm, true, "return", toStringFlags, tabCount, tabSize, \'"\' + ToString(returnValue, toStringFlags, tabCount, tabSize) + \'"\');\n'

         # Handle function arguments

Pumps out:
Generating generated_vulkan_ascii_consumer.cpp

vkGetBufferOpaqueCaptureAddressKHR  ->  uint64_t
vkGetBufferOpaqueCaptureAddress  ->  uint64_t
vkGetDeviceMemoryOpaqueCaptureAddressKHR  ->  uint64_t
vkGetDeviceMemoryOpaqueCaptureAddress  ->  uint64_t

vkGetAccelerationStructureDeviceAddressKHR  ->  VkDeviceAddress
vkGetBufferDeviceAddressEXT  ->  VkDeviceAddress
vkGetBufferDeviceAddressKHR  ->  VkDeviceAddress
vkGetBufferDeviceAddress  ->  VkDeviceAddress

vkGetDeferredOperationMaxConcurrencyKHR  ->  uint32_t
vkGetImageViewHandleNVX  ->  uint32_t

vkGetRayTracingShaderGroupStackSizeKHR  ->  VkDeviceSize

vkGetPhysicalDeviceDirectFBPresentationSupportEXT  ->  VkBool32
vkGetPhysicalDeviceScreenPresentationSupportQNX  ->  VkBool32
vkGetPhysicalDeviceWaylandPresentationSupportKHR  ->  VkBool32
vkGetPhysicalDeviceWin32PresentationSupportKHR  ->  VkBool32
vkGetPhysicalDeviceXcbPresentationSupportKHR  ->  VkBool32
vkGetPhysicalDeviceXlibPresentationSupportKHR  ->  VkBool32


Refactor and move KoalasBoxPlot to be consistent in plot implementations.

This PR make current plot implement consistent, and remove KoalasBoxPlotSummary for now. Seems like the generalization can be done differently later. Currently seems a bit overkill to me.
Mainly this PR moves codes just to be consistent.

Merged.


[parametric] Add Java library OTel support

Description
This PR adds OpenTelemetry support to Java library client for parametric tests.
It requires some dd-trace-java instrumentation fixes (https://github.com/DataDog/dd-trace-java/pull/5037).
Workflow

⚠⚠ Create your PR as draft (we're receiving lot of PR, it saves us lot of time) ⚠⚠
Follows the style guidelines of this project (See how to easily lint the code)
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

NOTE:  By default in PR only default scenario tests will be launched. Please refer to the documentation to run all scenarios in your PR if needed.

Once your PR is reviewed, you can merge it ! :heart:

The 1.12.0 version of Java tracer was just released.
So it is ready for review @cbeauchesne

relaunching the CI !

It's still failing on java/parametric, is it expected ?

Looks like nobody is maintaining the docker image with the tracer...
I will need to fix it myself or revert to the curl/wget solution to download the Java tracer.
But in the same time, the OTel tests changed again... I will deal with it later I guess 🤷

@cbeauchesne I updated it with the old way to get tracer and latest parametric tests state.


Photodiode sensitivity not enough for led detection + red led stays on

Hi, I'm having a couple of issues :

I have the recommended photodiode but doesn't seem to be sensitive enough to pick up the meter led
I can use a torch to trigger the photodiode but often the red light will tend to stay on permanently

On (1) I've adjusted to pot so the D0-LED on the photodiode board is just off.  From there I can get the red led to light and see a detection registering in the logs when I get a torch and shine it right up to the photodiode.
It's entirely possible this is some hardware fault with the photodiode sensor, or that this version just isn't sensitive enough or something, but I thought I'd ask since it's not hugely clear to me.  Given the ESPHome sensor type is essentially "pulse" I suspect all the logic around outputting a pulse to D0 is done on the photodiode board, so this is probably not some code or config issue?  Maybe I should reorder the same board or perhaps there's an alternative with better sensitivity?
On (2) I can use a torch to trigger the photodiode and I see log entries appearing for the detection.  Moving the torch away the red led stays on though, my understanding is it should turn itself off?
Worth noting that even though the led stays on, moving the torch back over the photodiode does register a secondary detection, so if this is an issue it doesn't seem to be with light detection as such, more around turning on/off the led.

With the debug led something will change, because there are more people who have the same problem that the led stays on.

I am experiencing the same issue, I have spent hours tuning the photodiode sensor and just can't get it to detect the LED on my meter. As above, I was able to simulate the meter with a torch and it worked, so the setup from a wiring and YAML point of view is working correctly.
I am think I will order another photodiode sensor as it seems to be the sensor not being sensitive enough. I wonder if anyone else has had this issue?
For clarity, I am using a Landis+Gyr e360 smart meter, it has a red pulse LED and 1/Wh = 1000/kWh.
Any ideas on what else to try whilst I wait forever for my new sensor?

Landis Gyr + E470 here.  But even though you could say it isn't the brightest LED in the world I do feel this probably isn't a smart meter issue as such.
For example given the red led issue staying on issue above, I tried using the Glow's own LED (which is much brighter) to trigger the diode and I couldn't even get that to work, only a bright torch shone right into the center of the diode right up next to it seemed to work (even after trying to calibrate via the pot), to me that seems like it's just the diode unit itself isn't really suitable.

I agree it seems to be the sensor/diode itself that's the issue. I am going to order a couple more to test, at least they're cheap.
Your idea of trying a different diode is an interesting one, I am not sure if the IC would be tuned to this one in particular, but worth a try if new ones don't work.

Please check whether the photodiode is the right way around, as shown in the picture.  My two modules that I ordered were the wrong way round.  The cathode must be connected to "+" not to "-".  After turning the photodiode over, it worked with low sensitivity on the poti.  But I also have the continuous glow of the red LED, since Esphome 2021.8.x, before with 1.20.4 it was okay.
Hope that helps...

Oh... My... God.... It is soldered on backwards. Thanks for the suggestion! I will flip and resolder and see how it goes.

Please check whether the photodiode is the right way around, as shown in the picture. My two modules that I ordered were the wrong way round. The cathode must be connected to "+" not to "-". After turning the photodiode over, it worked with low sensitivity on the poti. But I also have the continuous glow of the red LED, since Esphome 2021.8.x, before with 1.20.4 it was okay.
Hope that helps...

This image is showing it the wrong way round or the right way round?  Mine is soldered the opposite way, is that correct cathode should be negative right?

https://www.analog.com/en/technical-articles/optimizing-precision-photodiode-sensor-circuit-design.html
I found this a few das ago and i tried to flip the Photodiode, then it works well.
The Image is showing the right way round. It is Not a LED!

Please check whether the photodiode is the right way around, as shown in the picture. My two modules that I ordered were the wrong way round. The cathode must be connected to "+" not to "-". After turning the photodiode over, it worked with low sensitivity on the poti. But I also have the continuous glow of the red LED, since Esphome 2021.8.x, before with 1.20.4 it was okay.
Hope that helps...

I think the picture in the link is the wrong way. Mine is soldered the other way. I googled this topic and everywhere  I found that the LED flat side is the negative (cathode). I have checked my module and the flat side is soldered to the negative "-" side on the board . Does this mean that the printing on the module is wrong? I checked my module with multimeter and the GND and the "-" leg on the diode has continuity, So I am confused now.

IT is NOT a LED, see Post before...

IT is NOT a LED, see Post before...

Gotta say, awesome work spotting that.  Thanks that's saved so much messing about.

IT is NOT a LED, see Post before...

Thank you. I haven't seen your previous reply, as I was writing my comment and  the page didn't refreshed before I have submitted my comment. I ordered mine from Banggood so it is probably the same batch as @nygellyndley has. I will turn around my photodiode immediately.

I bought mine on ebay.de, shipped from China.  The pick and place robot probably also believed it was an LED 😂
Nice that I could help, I read and write most of the things with Google translator because my school English is very rusty 🙄

Please check whether the photodiode is the right way around, as shown in the picture. My two modules that I ordered were the wrong way round. The cathode must be connected to "+" not to "-". After turning the photodiode over, it worked with low sensitivity on the poti. But I also have the continuous glow of the red LED, since Esphome 2021.8.x, before with 1.20.4 it was okay.
Hope that helps...

Thanks for this, was messing with mine for hours. 2 diodes sent the wrong way round. Desoldered and it was working as it should. Thanks

I have rotated the photodiode and now it works correctly. Thank you @cegenolf  for the hint.

I've got some of photodiode modules on order. Just for clarity, should the flat of the photodiode be on the + or - marking of the PCB?
https://m.media-amazon.com/images/I/51VEP0osl1L._AC_SL1100_.jpg

If you have the photodiode is mounted as in the picture on the link, than it is correct. Check the metal parts inside the photodiode. The bigger part should be "+".

Just wanted to come back in and say that my PD was indeed mounted backwards. Was actually a bit annoying to get de-soldered but I managed to switch it around and bang, working like a charm.

Life saver. Mine was shipped backwards also and now is working great with it the correct way around.

I think we should put some more in the docs on this, as this seems to be a more common problem 🤔

@klaasnicolaas Hi, as many of us encountered the issue of the wrongly soldered photodiode, would you be so kind to mention this in the readme, so everyone is aware of this, and they don't start spaming the issue section with this topic.

That was exactly what I suggested 🤣 Does anyone have pictures of a photodiode connected right and wrong way?

@klaasnicolaas Here are some pictures which are with the correct orientation:
https://www.sunrom.com/p/light-sensor-module-photodiode
https://m.media-amazon.com/images/I/51VEP0osl1L._AC_SL1100_.jpg
... and here is my module with the wrongly soldered photodiode.

And indeed I also had this issue... very handy to update the readme to show this!  (thanks @KixMan28 that was very clear!)

And indeed I also had this issue... very handy to update the readme to show this! (thanks @KixMan28 that was very clear!)

Created a pull request : Created a pull request for this : https://github.com/klaasnicolaas/home-assistant-glow/pulls
@KixMan28 I used your image I hope you don't mind!

@nygellyndley no problem.

just a quick heads up before I go and unsolder the diode:
when changing the potentiometer, I can make the diode recognize the LED in the meter, at least it's showing something on the own status LED, and the red LED in the case is flashing briefly
but my diode looks exaktly like the one in https://github.com/klaasnicolaas/home-assistant-glow/issues/34#issuecomment-913155023
so I'm wondering what is going on here...

just a quick heads up before I go and unsolder the diode:
when changing the potentiometer, I can make the diode recognize the LED in the meter, at least it's showing something on the own status LED, and the red LED in the case is flashing briefly
but my diode looks exaktly like the one in #34 (comment)
so I'm wondering what is going on here...

I had the same, when changing the sensitivity dial, it did pick up the led. But it didn't report the correct values. Often my values were around 72000 watt although it was actually around 100watt... after flipping the diode it reported it correctly.

It's strange. I have desoldered it and resoldered in correct way.
I can drop the sensitivity now to make it recognizing the IR-LED, but the values sent to Home Assistant are still not correct: makes about 2 kW/h per minute :-o

I played around with the potentiometer, and made it close to the maximum before it doesn'T stop recognizing anymore.
Now I get a more realstic measurement, however, it seems that this is not updating even if I'm starting water heater, coffeemaschine and the iron.
It's always around 358-362 Watts

@pschneider87 please edit your post instead of double posting to keep the overview. Also I would say double check that your diode is getting all the flashes, especially if it is flashing raptly. With all that stuff on I would imagine it will be a disco light on your electricity meter. also make sure it isn't exposed to other light so make sure you block any light from exposing the diode.
Besides this also make sure you have adjusted your pulse_rate

@bruvv sorry for double posting, will remember this.
Regarding the issue:
the Meter  LED pulses 61 times per Minute, Pulserate in the script is set to 10000. HA Glow exposing 358 to 362 Watt which is correct for this pulse rate.
Checking the internal power consumption of the meter returns ~ 250 Watt, which should be ~ 42 Pulses per Minute
So maybe the meter is just not as correct as it should be
Maybe someone else with an Itron 3 HZ meter can confirm if this is an generall issue with this meter, or a specific for mine...

Just received my modules, which also have the photodiode wrongly orientated.

So I am not the only one with this problem then... I have some basic soldering skills. Is it easy to fix on my own?

So I am not the only one with this problem then... I have some basic soldering skills. Is it easy to fix on my own?

It's very very easy.

So I am not the only one with this problem then... I have some basic soldering skills. Is it easy to fix on my own?

Took me about 5 minutes with just a soldering iron and some solder. Potential you could lift a track though if you are not proficient with soldering.

I also got one from Banggood that was the wrong way round, after fixing that it now detects the pulses from a torch, but its not detecting the pulses from my meter, I have even adjusted the sensitivity to just after it stops flashing like crazy on its own.
I even tried covering the diode so no ambient light gets in.

I also got one from Banggood that was the wrong way round, after fixing that it now detects the pulses from a torch, but its not detecting the pulses from my meter, I have even adjusted the sensitivity to just after it stops flashing like crazy on its own.
I even tried covering the diode so no ambient light gets in.

Did you properly sold the ESP Pins? I had some pins not being connected well, with the same experience

I also got one from Banggood that was the wrong way round, after fixing that it now detects the pulses from a torch, but its not detecting the pulses from my meter, I have even adjusted the sensitivity to just after it stops flashing like crazy on its own.
I even tried covering the diode so no ambient light gets in.

Did you properly sold the ESP Pins? I had some pins not being connected well, with the same experience

I'm not seeing the D0 light on the board light up when the meter flashes, but it does when the torch flashes.
I will resolder them just in case (also I have daisy chained the dupont cables from the esp32 to the photodiode board (will remove one link to test)

Oh wow, mine also seems to be from a batch with the diode the wrong way. Thanks so much!

It took a while but I've updated the documentation with better illustration and a separate section at the bottom as FAQ.

There's still the red led staying on but I think that's already logged elsewhere, happy to close this

Code has already been changed for the red light, so that should be solved. For now I'm closing the issue.

where should I get the firmware for ESP32, the link at the bottom of the page is blocking me and not letting me download anything
this ()

is there a tutorial on how and what to upload to ESP 32, I'm new, stupid and I don't know what's going on, I can't find it

This issue has already been closed, which means that you will not respond with new issues that are not related to the first post.
Please open a new issue with an explanation of your problem.

can't you just help me get these files for ESP and home assistant to build a sensor like this?

You can use the website to (via improv) put the firmware on your ESP or you can download the yaml file, like the instructions under get started. For further text and explanation, please create a new issue, since your request for help has nothing to do with this issue.


Cannot synchronize changes from Vue component to Vuex

Hey, guys Im newbie in Vuex and I'm trying to understand how it works? I have got some problems with synchronize,
I have got leftsidebar menu and when i change my route, I assume that I can change my Vue.http.get() request, by passing some params from vue-router.
But when im changing my route, my component page doesn't reload, What I need to do??
this is my code:
test.txt

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server, gitter or StackOverflow.


HTTP post request wrong Json output

Hi,
When calling for my API from CLI, the Post request returns a Json string with all the escape character inside. it feels like the string has been json marshalled twice.
Example:  {\n  "properties": {\n   "disabled": true\n  }\n }
Expected output:
{
"properties": {
"disabled": true
}
}
in comparison I also have the default command which returns the correct value.
The code I used for those 2 API are identical. same methods So I don't understand the disparity in the returns.
This only happens when I call it through CLI, If I set up a local service, I can directly use CURL commands to call those APIS and I will get the expected returns.
Rrunning in cloudshell:
az resource invoke-action --action enableConsole --ids "/subscriptions/$Subscription/providers/Microsoft.SerialConsole/consoleServices/default"
"{\n  "properties": {\n   "disabled": false\n  }\n }"
az resource show --ids "/subscriptions/$Subscription/providers/Microsoft.SerialConsole/consoleServices/default" | jq .properties
{
"disabled": false
}
Both the Above API uses same method to create the json string and add the string to Header.

@chfa Thanks for reaching out. I will have a look at this issue later.

Some update. I ran the Cli commands with --debug on , and this is what I see

So in the header it seems to be the correct format and once displayed, it got Json marshalled again it seems.

@chfa I think the different format is because you have different response content format. When you run az resource show --ids "/subscriptions/$Subscription/providers/Microsoft.SerialConsole/consoleServices/default" | jq .properties --debug, you can see the response content is in string format without line breaks. However, in the debug information you show, response content includes line breaks, which will be displayed as \n in CLI. It can be fixed when your response content in the following format:
msrest.http_logger : Response content:
msrest.http_logger : {"properties": { "disabled": false} }

In addition, if it is hard for you to change the returned content, we can add transformer function like this.

can you please add a transformer function?
thanks
Sent from Outlookhttp://aka.ms/weboutlook

From: Zunli Hu<EMAIL_ADDRESS>Sent: Tuesday, September 17, 2019 6:58 AM
To: Azure/azure-cli<EMAIL_ADDRESS>Cc: Chen Fan<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-cli] HTTP post request wrong Json output (#10479)
@chfahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fchfa&data=02|01|Chfa%40microsoft.com|d84ac07dcdb34d0a356608d73b7725dc|72f988bf86f141af91ab2d7cd011db47|1|0|637043255234377558&sdata=6kwMkZg6O4TetMwWwXhXJUzM%2BJg%2FNtEydoK7vDfn3%2BQ%3D&reserved=0 I think the different format is because you have different response content format. When you run az resource show --ids "/subscriptions/$Subscription/providers/Microsoft.SerialConsole/consoleServices/default" | jq .properties --debug, you can see the response content is in string format without line breaks. However, in the debug information you show, response content includes line breaks, which will be displayed as \n in CLI. It can be fixed when your response content in the following format:
msrest.http_logger : Response content:
msrest.http_logger : {"properties": { "disabled": false} }
In addition, if it is hard for you to change the returned content, we can add transformer function like thishttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fblob%2Fdev%2Fsrc%2Fazure-cli%2Fazure%2Fcli%2Fcommand_modules%2Fnetwork%2F_format.py%23L107&data=02|01|Chfa%40microsoft.com|d84ac07dcdb34d0a356608d73b7725dc|72f988bf86f141af91ab2d7cd011db47|1|0|637043255234387554&sdata=U2631LKFHoDOarbII7mpsKKfMu9XFgaD6xCNBFhuUpg%3D&reserved=0.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fissues%2F10479%3Femail_source%3Dnotifications%26email_token%3DANEOOR2YEX4JQWNY43EWLGDQKDPBDA5CNFSM4IU7VM6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD64TYTI%23issuecomment-532233293&data=02|01|Chfa%40microsoft.com|d84ac07dcdb34d0a356608d73b7725dc|72f988bf86f141af91ab2d7cd011db47|1|0|637043255234397549&sdata=aNdMl%2FAZwvHE3cwHi0cQ9A98vjRC3Ji673E%2BtLyN9RE%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANEOORY2ZIU5J24PGCGLKQLQKDPBDANCNFSM4IU7VM6A&data=02|01|Chfa%40microsoft.com|d84ac07dcdb34d0a356608d73b7725dc|72f988bf86f141af91ab2d7cd011db47|1|0|637043255234397549&sdata=rb3BwnTgf7bDmuoO1E7cDMfoR3ja480vSznGqHJXWY4%3D&reserved=0.


Canceling the SpawnEntityEvent for a block's drops stops tool degradation

Player breaks iron with a pickaxe -> spawn of iron Item entity canceled via the SpawnEntityEvent -> the player's pickaxe doesn't degrade.

The tool shouldn't degrade if the block isn't dropped - it's as if it did not happen. If anything, a getter/setter to control it, defaulting to true.

The block is still broken, so something did happen.

I think this shows a bigger issue of event chaining. When do we decide design wise when cancelling an event cancels the "stack" of future effects and when it doesn't?
Can you instead change what entity spawned instead of cancelling the event? If not this would appear to be the correct way to cancel the drop without stopping future processing, and the API should allow you to do so.

You can work around this by removing the spawned entities from inside the event.

Then I don't see this as a bug.

How is it not a bug that an item being spawned, when cancelled does not degrade a tool? The only link here is the block.
Player breaks block -> { spawnItem, degradeTool }
Not
Player breaks block -> spawnItem -> degradeTool
The latter makes no sense, and treating that as some kind of a chain is ONLY going to lead to confusion. There is absolutely no advantage to treating item degradation as a downstream competent of a block's drop being spawned.

Because block drops are directly related to how the block is broken, whether it be explosion, tools, plugins, or modded tile entities.
Fortune, silktouch, and if introduced, explosion yield.
I can see your point of view, but disagree.
Whatever gets decided, it would be nice to see some semi-solid rules on how cancelling should work and effect downstream stuff, so rather then having opposing points of view, we could refer to a model to determine what the correct result should be.

Following your argument though, what happens if I cancel this event and the thing that broke the block was a block of TNT? Do we cancel the explosion?

Under those rules it would / should halt further processing of the explosion, if it's not already happened (previous tick / stage of processing) so yes.
In my eyes cancelling is the emergency stop rewind and should effectively undo the transaction of whatever action is happening.
The problem would then be defining what an "action" is. and unfortunately might even be implementation specific details leaking.
I might be completely off base, but either there should be a concept of event chains / actions or all side effects should throw an event regardless of previous events.
Should cancelling the explosion cancel the block destroys?

Re-test with stable-5 and report back if it still occurs. We'll re-open in the event that it does.


Add Hilbert matrix to jax.scipy.linalg

This PR adds an implementation of Hilbert matrices of order n that mirrors the API of scipy.linalg.hilbert(n) (https://docs.scipy.org/doc/scipy/reference/generated/scipy.linalg.hilbert.html#scipy.linalg.hilbert).
See #10144 for context.
Pinging @jakevdp, because he offered to review :)

(We'll also need to rebase on an updated main branch now to resolve conflicts)

I'm going to close this since it's gone stale – feel free to re-open if you'd like to work on this again!

Hi @jakevdp hope you're doing well. Can I open a PR for this issue?


Fixing indentation issue with the Windows checkmark

Fixing indentation issue on line 15 with the Windows checkmark on the top where it says which OS these applies to.

@KostaS10 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

The formatting fix looks good; thanks @KostaS10.


Support SSH key gets lost during leapfrog

Support SSH key gets lost during leapfrog and we need to move it back to physical hosts to sustain container failure

This has been addressed with https://github.com/rsoprivatecloud/openstack-ops/pull/48


[Future Suggestion] NodeJS port

Instead of going with my previous suggestion (https://github.com/kc9eye/GalnetArchive/issues/2: a Debian port), it would probably be better to use NodeJS, as that's basically cross platform compatible.

Sure

Sure


our connection isn't private

URL
https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-tutorial/run
Operating system
windows
More information about your system
No response
Description
running dotnet mvc for  the  first time, I got this  error: our connection isn't private
dotnet --info
.NET SDK:
Version:           8.0.203
Commit:            5e1ceea679
Workload version:  8.0.200-manifests.8cf8de6d
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.22621
OS Platform: Windows
RID:         win-x64
Base Path:   C:\Program Files\dotnet\sdk\8.0.203\
.NET workloads installed:
There are no installed workloads to display.
Host:
Version:      8.0.3
Architecture: x64
Commit:       9f4b1f5d66
.NET SDKs installed:
8.0.202 [C:\Program Files\dotnet\sdk]
8.0.203 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Other architectures found:
x86   [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]
Environment variables:
Not set
global.json file:
Not found
Learn more:
https://aka.ms/dotnet/info
Download .NET:
https://aka.ms/dotnet/download

At the bottom of the page, there are some instructions on how to solve that

have you tried that?


[WIP] generate docs for fairing APIs

What this PR does / why we need it:
Generate the Docs for Fairing APIs.
I prefer to use the sphinx to generate the docs for Fairing APIs. I would like have a demo for the Fairing community to show my thoughts by the PR.
I created the script doc-gen.sh, maintainer just need to execute the script to generate new docs after add new functions/features or updated the docstrings for some functions/classes, and then create PR to merge that.
Note:  Creating the PR is to show my proposal for generating docs for Fairing APIs, and will discuss with Fairing community, if have better solution, the ticket will be closed. Thanks
Which issue(s) this PR fixes :
Fixes #326
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

This change is

@karthikv2k As shown in the meeting just now, what do you think for this? If you also agree that's good choose using sphinx, so check in the doc-gen.sh and immature docs?  If so, someone updated the docStrings for the APIs laster, just ran the script to generate docs diff and can check the result directly, and fixing the warning or error if any during generating.

I geneated two types doc: html and markdown, since we cannot review the html page directly unless set up html server or using the tools such as https://htmlpreview.github.io/, so I genereated markdown type so user can read that directly, seems for user experience, seems html is better than markdown. So just generated two types. Thanks.

@sarahmaddox We are going to generate the Fairing documents, I'm wonder is that possiable to put the html docs in our kubeflow.org? can we create a link(Fairing) on top right corner of the kubeflow.org to link to faring html page? Thanks.

@sarahmaddox We are going to generate the Fairing documents, I'm wonder is that possiable to put the html docs in our kubeflow.org? can we create a link(Fairing) on top right corner of the kubeflow.org to link to faring html page? Thanks.

Hallo @jinchihe Thanks for generating these docs! You should create a new Reference section in the Fairing section of the docs:
https://www.kubeflow.org/docs/fairing/
To do that, follow the pattern of the "Reference" section in the Pipelines section of the docs:
https://www.kubeflow.org/docs/pipelines/
When ready, please send your PR to @joeliedtke for review. He can help you with getting the doc metadata and structure correct.

Hallo Abhishek, I'm on a plane, so this response will be delayed. The ref
docs should be on kubeflow.org. I added a comment earlier in this thread
with some info.
On Fri, 1 Nov 2019, 05:41 Abhishek Gupta<EMAIL_ADDRESS>wrote:

/test kubeflow-fairing-presubmit
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubeflow/fairing/pull/338?email_source=notifications&email_token=ABO2TC6BLLZ6MPZE3K3KISLQRMDEDA5CNFSM4IJJOSD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECYOJPI#issuecomment-548463805,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABO2TC6LLX2N65CHXC7IRY3QRMDEDANCNFSM4IJJOSDQ
.

Agree, I generated two types docs: html and markdown. The html docs are great for end users. please see below attachment for my quick demo pictures. We may need put those html docs to html server. for markdown, that's ok both for github repo and kubeflow.org.
@sarahmaddox I'm not sure if we can put the html docs to kubeflow.org (working as html server side).
/cc @jlewi

/lgtm
/approve


force_to_top no longer moves imports to top of file.

I think I am trying to use force_to_top correctly.
With the latest version on PyPI an import that is part way down the file (but not inside a function) gets moved to the appropriate section at the top of the file. However, using the current master branch the import is left where it is, although it does get the appropriate comment added above it as per my .isort.cfg file.
Is this a bug or a deliberate change in version 5?

force_to_top, just means top within the a section not the file. isort has moved to a streaming parsing approach in 5.0.0 which allows it to safely sort around and within block of code (https://timothycrosley.github.io/isort/docs/major_releases/introducing_isort_5/) However, this does unfortunately mean it can't move imports to the top. If enough people up vote this issue I will add a feature to enable this with an acknowledgement that performance will be reduced.

I'd love to have this back. During development I could simply put the import statements wherever I was working currently and let isort push them to the top. If in a rare case a file needed multiple sections of imports, I simply added it to the ignore list and handled it manually.

@pmeier This is indeed a pattern I got in the habbit of following myself as well. Aiming to get this into the next minor release

This has now been deployed to PyPI in the 5.1.0 release,
See: https://timothycrosley.github.io/isort/docs/configuration/options/#float-to-top
Thanks again!
~Timothy

Wonderful, thanks Timothy. I'll give this a try.
By the way, you spelt "guaranteed" wrong in that section of the docs (you put "gauranteed").

Thanks for letting me know :) I've updated the documentation


Tutorial on finding WCS solutions (and possibly simple coadd/differencing?)

The functionality of this function: https://docs.astropy.org/en/stable/api/astropy.wcs.utils.fit_wcs_from_points.html is really begging for a tutorial. It could conceivable be added to the photometry guide, but sometimes you just want to do this for astrometry too, so I think it could be a good stand-alone tutorial.  I would imagine the following (I've split this into 3 parts which could be a 3-part tutorial or just three sections of one tutorial):
Part 1:

Start from an image that is slightly distorted with no wcs but where you can say "we know about where this is pointed" and can identify by eye a few bright stars.
Use those with fit_wcs_from_points to get a "rough" WCS solution (i.e. just basic TAN projection)
Part 2:
Use the rough solution to cross-match to a catalog with known-good astronometry (e.g. Gaia, SDSS, or POSS)
Re-fit the wcs with fit_wcs_from_points but using a fancier projection that includes some sort of distortion correction.
Part 3:
Find a second image that's similar to the first but offset just a bit (e.g., a dither, or from a different night for time-series photometry)
Repeat parts 1-2 (or maybe just 2 if the "rough" solution is good enough) to get a WCS including distortion corrections
Use reproject (https://reproject.readthedocs.io/en/stable/) to project the second image to the wcs of the first image
Either coadd the two images (yielding a better image) or subtract them (to see variable stars pop out)

I'm working on a tutorial that does this right now!


Key for Note Air 4C

I need a key for Note Air 4C

I need a key for Note Air 4C
sorry i found it, just didnt see it at first.


make error messages more user friendly

make error messages more user friendly for cases when public/private input files are needed but not provided

CI run here https://github.com/NilFoundation/zkLLVM/pull/503


Update SPI to 0.92

Including SPI change at 0.90 https://prestodb.io/docs/current/release/release-0.90.html

Add getColumnTypes API to RecordSink https://github.com/facebook/presto/commit/4770f04be1b4ea9f4d9
Add PageSink to SPI https://github.com/facebook/presto/commit/cdbead924403895eb4b8584
https://github.com/facebook/presto/commit/3563790bf651b17aedb1d => ae5b3ad2924aa3

Now not using PageSink nor RecordSink SPI. => #7


[VCM] TeamViewer complains no camera driver is installed

Microsoft PowerToys version
0.51.1
Running as admin

[X] Yes

Area(s) with issue?
Video Conference Mute
Steps to reproduce
Select "PowerToys VideoConference Mute" as video source in TeamViewer
✔ Expected Behavior
TeamViewer capturing the video stream from the PowerToys virtual camera
❌ Actual Behavior
TeamViewer saying "Please install the camera driver"

Other Software
TeamViewer 15.24.5

How is the experience for other apps? (Teamviewer, Teams, Skype, Google Meet...)

Thanks for the feedback but VCM is moving to maintenance only in the 0.67 timeframe. Our team will only directly address critical bugs, security and accessibility issues.
We'll accept community PRs for enhancements.


update README [show option]

Hi @ethomson.
I'm Dario, a developer at BuildNN.
Firstly, I want to thank you for the great work you did, I use your action basically everyday and It works really great.
Developing my pytest-summary extension I discovered about the option show that is not mentioned on the README.
Since I consider it helpful, I added it.
PS. any advice on my extension is more than welcome

Any update?

I guess you don't believe in collaborations.
I opened this PR almost 9 months ago, and today I found out you did it in January by yourself.
A message would be appreciated.

Hi @dariocurr - apologies that I didn't see this. Indeed, I do believe in collaboration. The README change was included in PR #13.
Thanks for the fix - sorry again that I didn't see the notification for your pull request.


Add types for cv.exceptionFromPtr

OpenCV.js can throw pointers to internal exceptions.  Luckily the library supports retrieving the exception behind a pointer using the exceptionFromPtr function.
This PR adds types for this function.

updated in 1.3.4


How do I return null in the resolver?

Returning null in the resolver for a nullable DateTime gives 1970-01-01T00:00:00.000Z
typeDefs = `
  type User {
    dob: DateTime
  }
`

resolvers = {
  User: {
    dob: () => null
  }
}

I would expect returning null to have the query response also be null instead of 1970-01-01T00:00:00.000Z

Hmm, this sounds like it is a bug. Would you mind creating a PR that reproduces this error in one of the test cases? This would help me solve this issue.


Switch required pydantic versioning to accomodate v2

Pydantic has a ground up re-write that's starting to make it into newer distros, F40, OpenSuse Tumbleweed, etc which includes pydantic v1 support, but breaks the default importing we are doing.
This adjusts the base pydantic in pyproject.toml to be a minimum of 1.2 (to meet Ubuntu 20.04 baseline requirements) and adds a try/except block to try loading the correct pydantic version where we are expecting.
Quick check on F40, in a venv, this plus the change in tt-tools-common to do roughly the same thing should sort out #27

Verified it works on Ubuntu 20.04 system


NaQ++ Stage-1 pretrained checkpoint

Thank you for releasing the code of this excellent work! For EGO4D NLQ 2023 Challenge, I notice that only the finetuned NaQ++ model have been released. Will you release the checkpoint of the NaQ++ stage-1 pretrained model?

Hi @xyzforever. No, we don't plan to release the stage-1 model since the NaQ++ release was largely to serve as baselines for the Ego4D challenge. You should be able to train the stage-1 model following our instructions here.


Add readme with examples

Right now, it's not clear what it is or how to use it.
Need a description in the readme and full-fledged examples of use with popular libraries in a separate repository (to maintain zero dependencies here).

It turned out to be a big separate project
To be accessed by going to https://github.com/thevan4/telegram-calendar-examples

It doesn't look like much, but it's a good place to start.


[DUOS-1964][risk=no] Add DataAccessGovernance section to Data Submission Form

Addresses
https://broadworkbench.atlassian.net/browse/DUOS-1964
Replaced the old one (closed that PR) because it had so many conflicts that it was easier to make a new branch from develop.

Have you read Terra's Contributing Guide lately? If not, do that first.

Label PR with a Jira ticket number and include a link to the ticket
Label PR with a security risk modifier [no, low, medium, high]
PR describes scope of changes
Get a minimum of one thumbs worth of review, preferably two if enough team members are available
Get PO sign-off for all non-trivial UI or workflow changes
Verify all tests go green
Test this change deployed correctly and works on dev environment after deployment

I am not sure why npm audit is failing (bootstrap requirement didn't change?) but this should be ready for re-review
Changes:

Search for diseases in ontology
More idiomatic / cleaner form field usage
Date validation + field for date

Looking good - I can now select items under "Secondary Data Use Terms".
With the new changes however, section 1.1 Data Custodian is grayed out and I can't enter anything into the form field. I'm also unable to enter anything for section 1.10 Data Access Committee and the drop down doesn't have any DACs listed. If I remember correctly this was working before.

Looking good - I can now select items under "Secondary Data Use Terms". With the new changes however, section 1.1 Data Custodian is grayed out and I can't enter anything into the form field. I'm also unable to enter anything for section 1.10 Data Access Committee and the drop down doesn't have any DACs listed. If I remember correctly this was working before.

Hmm, curious. The data access committee dropdown works fine locally. Is it possible there is an error on you hitting the DAC endpoint on consent?
Also, I believe the data submitter (I assume you mean submitter? the custodian field also works for me locally) field is supposed to be greyed out - it's prefilled with the current user's information.


can't uninstall edge on 23h2

checked the microsoft edge since I switched to arc browser, it says error

Heya,
This is an issue that I am aware off. There's actually an open issue for it here: https://github.com/Raphire/Win11Debloat/issues/38
To summarize: Removing edge only works on systems where the region is set to a country within the EEA. And even then it might not work as there appears to be a bug in Windows that prevents some users from removing edge even with the correct region set.
I'll close this issue as a duplicate, if you have any additional info please provide it in the issue linked above.


Shower thought: Remove dependency on generated ProtobufJS files

The ProtobufJS files just call to jspb.Message etc, that stuff could.be done in the protoc-gen-gopherjs files themselves. Would probably require some experimentation first.

Gonna take a stab at implementing this in https://github.com/johanbrandhorst/protobuf/tree/remove-dependency-on-generated-files

Managed to get this to pass all my tests -  still a bit of cleaning up to do in generate.go, but this is starting to look like a reality now!

I'm sufficiently pleased with the current state of this to merge it into master. See #13


Create dataset loader for IndonesianNMT

Dataloader name: indonesiannmt/indonesiannmt.py
DataCatalogue: http://seacrowd.github.io/seacrowd-catalogue/card.html?indonesiannmt

Dataset
indonesiannmt

Description
Repository containing datasets for data automatically generated from gpt-3.5-turbo and text-davinci-003 used in the work "Replicable Benchmarking of Neural Machine Translation (NMT) on Low-Resource Local Languages in Indonesia"

Subsets
-

Languages
ind, jav, min, sun, ban

Tasks
Machine Translation

License
Unknown (unknown)

Homepage
https://github.com/luckysusanto/IndonesianNMT

HF URL
-

Paper URL
https://arxiv.org/abs/2311.00998

#self-assign


Always shows download error

Checklist

[x] I'm asking a question
[x] I've looked through the README and FAQ for similar questions
[x] I've searched the bugtracker for similar questions including closed ones

Question

WRITE QUESTION HERE
How to solve this problem ??
--> DownloadError: ERROR: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the verbose flag and include its complete output.

Don't skip the template, there's absolutely nothing in the post that tells anything cuz the "No video formats found" is as general error as it gets with ytdl's modularity. This is why the template exists.


Check subcmd exit codes in rebuild-iptables script

Description
Ensures rebuild-iptables does actually succeed by checking subcommand exit codes.
Issues Resolved
https://github.com/chef-cookbooks/iptables/issues/64

I see that you're planning to replace this script. I am wondering if I should close this PR however it might make sense to merge it b/c 1) it may be a while before the rewrite happens, 2) the rewrite is likely going to require a major version bump and it may be a while before its widely adopted. Feel free to close this PR if appropriate.


add reddit wallpapers scraper

Description
Created scraper for wallpapers
Fixes #595
Type of change
Choosing one or more options from the following as per the nature of your Pull request.

NOTE: These boxes can be checked using [X]

[ ] Bug fix (non-breaking change which fixes an issue)

[x] New feature (non-breaking change which adds functionality)

[ ] Documentation Update

Checklist:
Please tick all the boxes that are fulfilled by your Pull Request.

[x] I have named my files and folder, according to this project's guidelines.
[x] My code follows the style guidelines of this project.
[x] My Pull Request has a descriptive title. (not a vague title like Update index.md)
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have created a helpful and easy to understand README.md, according to the given README_TEMPLATE.
[x] I have included a requirements.txt file (if external libraries are required.)
[x] My changes do not produce any warnings.
[x] I have added a working sample/screenshot of the script.

Thank you @tusharnankani !
I'll be sharing more projects here 👍


Hard refactor

Protected properties in all models, getters and setters, new initialization for all Models

@StereoFlo thank you. I have reviewed it a bit and this looks awesome.
I will merge and after reviewing it a bit more will release this version .


waitForNavigation Error: Execution context was destroyed, most likely because of a navigation.

I have the following test:
 it("Should not have to open Knhb when logging in again whilst still being logged in in SSO", async () => {
        await page.goto("http://localhost:3000");
        await expect(await page.evaluate(() => {
            localStorage.clear();
            return localStorage.getItem("id_token");
        })).toBe(null);
        await Promise.all([
            page.waitForNavigation(),
            page.goto("http://localhost:3000/matches")
        ]);
        await expect(await page.title()).toBe("Digitaal Wedstrijd Formulier");
    });

It opens a page which redirects a few times, after all the redirects are done it should continue. Instead of waiting it throws the following error:
Error: Execution context was destroyed, most likely because of a navigation.

@jordyvandomselaar what's your puppeteer version? Also, how do I reproduce this locally?

You would reproduce it using
await Promise.all([
            page.waitForNavigation(),
            page.goto("http://localhost:3000/matches")
        ]);

The goto should contain any url that would redirect you somewhere.

@jordyvandomselaar what kind of redirects are these? We have tests for this exact scenario with regular HTTP redirects and things are working just fine.

Having the same problem. Just started to use this lib and totally stuck..

@stoplion please file a separate issue with details so that we can repro this. I'll close this since it's not actionable.

@aslushnikov I also have this issue. Should I create new topic?

@best-coupon-codes please do, but make sure to include a good reproduction script so that we can reproduce it locally. Otherwise it would not be actionable.


[Chat] Fix backspace to return to previous chat

If you haven’t already, check out our contributing guidelines for onboarding!

The behaviour of the back button in a web/mobile browser needs to be refined. At the moment it
Expected Result/Deliverable:
You should shift back to the previous chat.
Actual Result:
In desktop web: it goes to https://expensify.cash/r/undefined and content stays the same
In android web: it goes out of the app, back to the previous page you had loaded
Action Performed:
Head to expensify.cash
Open a chat with another user
Switch to another chat
Press the browser's back button
Workaround:
Click on the previous chat directly.
Platform:
Where is this issue occurring?

[x] Web
[x] Mobile Web
[ ] iOS
[ ] Android
[ ] Desktop App

Expensify/Expensify Issue URL: https://github.com/Expensify/Expensify/issues/157550

Upwork posting: https://www.upwork.com/jobs/~014dab1ed80ed6c3a2

Hello @kadiealexander,
I would love to work on this issue, and putting together a proposal.

Hi @kadiealexander
I would like to participate in this issue.
Problem

Here we have navigation for reports as r/:reportID
So, when we navigate between reports on the web, It only changes the parameter of the URL. It does not change the screen.
https://github.com/Expensify/Expensify.cash/blob/9b282f10de193d9a4115bc30f51e0dfdb4133050/src/libs/Navigation/linkingConfig.js#L5-L14
In react-navigation it does not push changes between the same screen parameter to navigation history.
Eg: /r/123456 to /r/01010101

Solution

To solve this I will add report navigation to the browser history
Inside sidebarLinks.js onSelectRow I will do the following,

onSelectRow={(option) => {
    if (getPlatform() === 'web') {
        window.history.pushState({}, '', option.reportID);
    }
    Navigation.navigate(ROUTES.getReportRoute(option.reportID));
    this.props.onLinkClick();
}}

Then on the web back navigation will work
Also we can move this check to Navigation.js. Then it will be available everywhere.

Thanks.

It's important to use links as the primary way of navigation instead of navigation actions such as navigation.navigate. It'll ensure that links are properly usable on web. reference
My proposal

Create a custom link which let us navigate to a screen using a path instead of a screen name based on the linking options.
The implementation will be similar to  this

Let me know what you think, thanks in anticipation.

@kadiealexander This issue needs to be updated since the r/undefined issue no longer exists. The issue affecting navigation history is still occurring however. It doesn't matter what web platform we are on the kinds of weird browser button behavior we see are the same.

It's important to use links as the primary way of navigation instead of navigation actions such as navigation.navigate

Thanks @mikeattara, why is this important exactly?

In react-navigation it does not push changes between the same screen parameter to navigation history when we use navigation.navigate()

@SameeraMadushan It does seem to work sometimes. So could there be a bug somewhere? The solution provided will work for reports so I'm not sure this workaround is what we are looking for. Ideally, we can get to the bottom of why the history is working inconsistently.

@marcaaron It's not a bug, It's the default behavior of navigation.navigate

navigation.navigate('RouteName') pushes a new route to the stack navigator if it's not already in the stack, otherwise, it jumps to that screen.

check this on: https://reactnavigation.org/docs/navigating/#summary

To show reports we have only one screen. so navigation.navigate won't push a new route to the stack and history won't get created.
If we can use navigation.push('RouteName')  instead .navigate this issue won't be there. Because,

We can call navigation.push('RouteName') as many times as we like and it will continue pushing routes.

But in the implementation getActionFromState doesn't provide push method. Do you have any comments on that?

@marcaaron, @SameeraMadushan findings are correct.
  if (action !== undefined) {
        root.dispatch(action);
    } else {
        root.reset(state);
    }

Here the action would always be navigate and when the route is the same navigate replace the existing state instead of Pushing a new one into History. We can confirm this by logging the state on History on Console.
So a solution here could be to Update the LinkTo implementation and adopt the useLinkProps implementation which will give us an action option. Now when the route is report route we can pass StackActions.push(ROUTES.REPORT_WITH_ID, {'reportID': id}) to action which should solve this.
Check here how Navigate behaves for Stack Navigators https://reactnavigation.org/docs/navigation-prop/#navigate

I think the solution may be slightly more complex than just using a PUSH action (though that does seem like it's an important piece of the puzzle).
Presently, if we push a new report screen onto the stack this will have weird consequences with the way things are set up now (drawer upon drawer navigator will appear). e.g.

But maybe it would work with things set up a different way e.g. without using the drawer navigator.

Looked into this some more. It is possible to get around the issue we noticed last time (many drawer navigators stacking) by moving the ReportScreen into a Stack.Navigator. Then, if we push new Report routes the browser history should work more reliably.
However, I also noticed that these Report screens never actually unmount and just stack on top of each other forever. This is the default behavior of react-navigation but doesn't make as much sense when we consider the overall design and performance of this app (it's fairly expensive to render the chat screens so pushing an infinite number seems like a dangerous idea).
But, maybe there's some way to get the screen to unmount if not focused as a workaround here.
Also wondering how a change like this might affect @kidroca's PR over here

I also noticed that these Report screens never actually unmount and just stack on top of each other forever.

@marcaaron  Pushing new routes in the mobile is fine right? Because when a user opens a report screen and If the user wants to open another report, the user has to go back(when going back will pop the screen) and start the stack from the drawer.
Pushing a new screen won't be a problem on the web, because the dom will just replace the report view with a new report and only the history will be recorded in the browser.

Hmm if the problem is only on mobile this means routing already works correct
What I expect from the back button when I'm inside a chat is to return me to the LHN though

I start from the LHN (drawer open)
I pick a conversation
I want to go back - intercept the back button and just open the drawer

Do you also want to be able to return to prior opened chats - the information should be in the navigation state? It will add some complexity but can probably be extracted
Could you be interested in the simpler approach for the moment though

pressing back from a chat expands the LHN
pressing back again collapses it and I'm back in the chat?

I don't think any changes will impact my PR a much. My changes are confined in the ReportScreen and it's children, wherever this component is moved it should still work the same.

If the user wants to open another report, the user has to go back(when going back will pop the screen) and start the stack from the drawer.

As long as there's drawer involved you are still on the Report Screen
You get the sense that you go back - because you start with the drawer expanded
But the Report Screen is always mounted the drawer just draws over it
So going back is just opening the drawer over the current screen. Then selecting a chat from the drawer just swaps the screen content.
With react nav 5 you can add screen definitions to the drawer nav dynamically so that for each chat you'd have a separate screen, selecting a chat would go to that screen and the previous screen should be discarded (though it might be saved by rn nav for back navigation performance) though I don't think it would help the current situation that much

@kidroca Oh! 👀  That's true.

because the dom will just replace the report view with a new report and only the history will be recorded in the browser

@SameeraMadushan I think when we push() a screen above another screen both remain mounted. The behavior you are describing does sound like what we'd expect when we use navigate() (but I am just guessing based on some quick logging done when the component mounts).
@kidroca That's a great point. And I agree that's 100% what our expectation would be if we were viewing things on mobile. But also makes less sense if we're on desktop where we'd expect to have a normal browser history built up as we navigate around.
Either way, I think we could in theory switch from a push behavior to a replace behavior depending on if we were on desktop/web or mobile/mWeb. That does sound a little complex, but unsure if react-navigation is offering a better way to handle web at the moment.

Spent some more time looking into this today and came up with a kind of dirty incomplete solution here
https://github.com/Expensify/Expensify.cash/pull/2295/files
Some kind of solution in react-navigation would be ideal, but not sure if allowing the option to switch to browser history.pushState() type behavior for the NAVIGATE action on web with a permanent drawerType is a direction they would consider.


Please include the namespaces in the examples

Things like VssConnection exist in more than one namespace, so copy/pasting the example to see it working immediately cant resolve the correct single namespace.

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

ID: aa8505e8-cef0-fee8-866a-e000058ac233
Version Independent ID: d6858ee2-4282-b4e1-fb3b-e8b531b950b7
Content: .NET Client Library Samples for Azure DevOps Services
Content Source: docs/integrate/get-started/client-libraries/samples.md
Product: devops
Technology: devops-ecosystem
GitHub Login: @chcomley
Microsoft Alias: chcomley

Hello @StingyJack! Thanks for your feedback, we'll address this as soon as possible and keep in touch. Have a great weekend!

Hi @StingyJack, We only have one VssConnection class in our code base and it is under the namespace: Microsoft.VisualStudio.Services.WebApi.  You must have a 3rd party binary loaded, which also has one.
Thanks! Let us know if you need more clarity.

@chcomley  - I didn't actually look for the types in the docs =O  (sorry).   i did have a screenshot of the two namespaces that were suggested. Isnt that the built-in type resolution context menu? Resharpers looks different I think. Either way, this is probably another bug for devcomm or youtrack.

Thanks @StingyJack, I've created a ticket with the Developer Community. Here's a link: https://developercommunity.visualstudio.com/idea/692744/include-namespaces-in-examples-for-net-client-libr.html
Thank you!


Add @Generated annotation to sync and async client itself

Fix #1265

@srnagar
I'm working on supporting partial update (https://github.com/Azure/autorest.java/issues/1050), we will first support adding new methods or modify existing generated methods in sync and async clients.
Hence, I will first check if the class is auto generated and has @Generated annotation, if it has, then the class is in scope of partial update. Then, handle partial update for this class.
I tried to add @Generated annotation to the class to make it easier to identify if the class is auto generated in this pr, example as below. But encounter the error that: @Generated annotation type is not applicable to class. It is only applicable to ElementType.METHOD, ElementType.CONSTRUCTOR, ElementType.FIELD.
May I know do we have plan to make @Generated annotation applicable to class? If not, I can close this pr and I can iterate the methods to see if any method has @Generated annotation to identify class in scope of partial update.
@Generated
@ServiceClient(builder = LlcClientBuilder.class, isAsync = true)
public final class LlcAsyncClient {
    @Generated private final ParamsImpl serviceClient;
...
}

@Retention(RetentionPolicy.SOURCE)
@Target({ElementType.METHOD, ElementType.CONSTRUCTOR, ElementType.FIELD})
public @interface Generated {
}

@haolingdong-msft currently, the @Generated annotation is not supported for classes. We want it to be granular at the method level as the new client APIs are generally convenience overloads and adding the @Generated annotation to the class can accidentally overwrite these manually added convenience methods when code is regenerated.

@haolingdong-msft currently, the @Generated annotation is not supported for classes. We want it to be granular at the method level as the new client APIs are generally convenience overloads and adding the @Generated annotation to the class can accidentally overwrite these manually added convenience methods when code is regenerated.

It makes sense. I will close this pr and iterate the methods under the class to identify classes in scope of partial update. Thanks @srnagar


[BUG] Python 3.9 in image "andreper/jupyterlab:3.0.0-spark-2.4.4"

Hey! Thank you very much for the project, it helps us a lot.
However, it looks like during the last update (about 15 hours ago) there was the problems in updating the images. Now in the image with spark 2.4.4 Python 3.9 is installed, instead of 3.7.
For this reason, errors occur when the container starts.
Is it possible to fix this problem and roll back the python version in the image back to 3.7?
Thanks in advance

Seems the problem still persists, any update?


Template could not be saved since domain id is None.

Rasa version:
rasa --version
Rasa 1.0.0
(from docker)
Rasa X version (if used & relevant):
Installed rasa/rasa-x:stable from docker.
Python version:
python3 --version
Python 3.6.8
Operating system (windows, osx, ...):
linux 64 bit
Linux 154c7240445c 4.4.0-1083-aws #93-Ubuntu SMP Wed May 8 16:08:41 UTC 2019 x86_64 GNU/Linux
Issue:

Open web UI
Go to "responses"
enter something

ERROR: in the logs ->
rasa-x_1           | Template could not be saved since domain id is None.

And nothing is saved.
Content of configuration file (config.yml) (if relevant):
language: en
pipeline: supervised_embeddings
policies:
  - name: MemoizationPolicy
  - name: KerasPolicy
  - name: MappingPolicy

Hmm, did you provide a domain file?

@akelad There is no domain.md file:
$ sudo find /etc/rasa/ -name domain.xml -o -name domain.md
[nothing returned]

I can't see where in the instructions it tells me where to place this file (I do have a domain.md in my local instance).
I have tried placing it in various locations in the rasa_rasa-production_1 container, but the result is the same.  I'm just guessing as to where it should be.

It appears (not surprisingly) that the bad url in #3726 was causing this issue also.

it's domain.yml not domain.md -- is this on a server version of rasa x then I guess? Yeah so i'm afraid there's no way to upload a domain file to that yet, but we're adding functionality for that soon

Closing this one, as the root cause was addressed in #3726

@akelad regarding domain.yml, can you point me to where this is supposed to go in the server system?

No where right now 😬 there's a release coming very soon where it'll be loaded though :)


Role on galaxy missing files.

This is basically the same issue as reported in #3, although that one is closed therefore a new one.
@vdvm something really is ascrew when downloading this role through galaxy. I've been pulling my hair out because I couldn't find the reason the root user wouldn't get a password, even when explicitly setting them through --extra-vars.
To be certain that the vars where actually passed correctly into the role I wanted to add some debug statements into the role files, but it turns out that the mysql_secure_installation.yml is actually missing when downloading from galaxy (see attached screenshot). I've triggered a new download to assure I had the latest version.
Looking at the timestamps of the files, it is clear what is happening. The main.yml file reports that is created on Dec 22, 2014, and mysql_secure_installation.yml was added on Jan 30, 2015. Could you update the galaxy release to the latest version?

Created a new release and synced with galaxy. Does this fix the issue?

When I run the update then the new files do show up. However my configuration is currently broken so can't test the deployment. I'll test that tomorrow.

@vdvm that seems to work, I however did find an other small bug that prevented the secure installation to finish. See #5.

@erikfrerejean thanks for your help!


Can't open after updating to the latest version

Describe the bug
After opening the console, the error is reported as follows
Uncaught (in promise) Error: Unknown variable dynamic import: ./locales/zh-CN.json
    at index-DEXvmT-O.js:301:7991
    at new Promise (<anonymous>)
    at __variableDynamicImportRuntimeHelper (index-DEXvmT-O.js:301:7894)
    at Object.read (index-DEXvmT-O.js:302:76644)
    at tt.value (index-DEXvmT-O.js:302:43845)
    at tt.value (index-DEXvmT-O.js:302:44941)
    at index-DEXvmT-O.js:302:44623
    at Array.forEach (<anonymous>)
    at tt.value (index-DEXvmT-O.js:302:44599)
    at tt.value (index-DEXvmT-O.js:302:44681)

Steps to reproduce

Open memos
F12 Then look at the error message

The version of Memos you're using
latest version
Screenshots or additional context
No response

@boojack

same with en-US

+1

2024/03/04 02:55:48 INFO OK method=/memos.api.v2.WorkspaceSettingService/GetWorkspaceSetting
2024/03/04 02:55:49 INFO OK method=/memos.api.v2.AuthService/GetAuthStatus
2024/03/04 02:55:49 INFO OK method=/memos.api.v2.UserService/GetUserSetting
2024/03/04 02:56:04 INFO OK method=/memos.api.v2.WorkspaceSettingService/GetWorkspaceSetting
2024/03/04 02:56:04 INFO client error method=/memos.api.v2.AuthService/GetAuthStatus error="rpc error: code = Unauthenticated desc = user not found"

I have been using the new version. I can’t log in on the mobile side, but the web side is normal.

Maybe https://github.com/usememos/memos/commit/342f341b3d5e4d9cec958a77a9de7283fc23894d helps

Maybe 342f341 helps

I updated the docker image to this version, and the error message is gone on the web side, but it's blank and nothing is there!

I have been using the new version. I can’t log in on the mobile side, but the web side is normal.

Web-based normal?

Maybe 342f341 helps

You can test it with your demo, I see that the demo is still reporting errors now：Error: Unknown variable dynamic import: ./locales/zh-CN.json

2024/03/04 02:55:48 INFO OK method=/memos.api.v2.WorkspaceSettingService/GetWorkspaceSetting 2024/03/04 02:55:49 INFO OK method=/memos.api.v2.AuthService/GetAuthStatus 2024/03/04 02:55:49 INFO OK method=/memos.api.v2.UserService/GetUserSetting 2024/03/04 02:56:04 INFO OK method=/memos.api.v2.WorkspaceSettingService/GetWorkspaceSetting 2024/03/04 02:56:04 INFO client error method=/memos.api.v2.AuthService/GetAuthStatus error="rpc error: code = Unauthenticated desc = user not found"

I'm also having it, but it seems a different bug. I have it on the server-side, not on the client-side

2024/03/04 02:55:48 INFO OK method=/memos.api.v2.WorkspaceSettingService/GetWorkspaceSetting 2024/03/04 02:55:49 INFO OK method=/memos.api.v2.AuthService/GetAuthStatus 2024/03/04 02:55:49 INFO OK method=/memos.api.v2.UserService/GetUserSetting 2024/03/04 02:56:04 INFO OK method=/memos.api.v2.WorkspaceSettingService/GetWorkspaceSetting 2024/03/04 02:56:04 INFO client error method=/memos.api.v2.AuthService/GetAuthStatus error="rpc error: code = Unauthenticated desc = user not found"

I'm also having it, but it seems a different bug. I have it on the server-side, not on the client-side

Is your web client working?
@grigio

@s544838371 no. I rollback to memos:stable and it started to work again

2024/03/04 10:30:55 INFO OK method=/memos.api.v2.WorkspaceSettingService/GetWorkspaceSetting
2024/03/04 10:30:55 INFO OK method=/memos.api.v2.AuthService/GetAuthStatus
2024/03/04 10:30:55 INFO OK method=/memos.api.v2.UserService/GetUserSetting

也许342f341有帮助

我将docker镜像更新到这个版本，web端的错误信息消失了，但是一片空白，什么也没有！ @boojack

me

I'm having the same problem, cheers for fixing it!

也许342f341有帮助

我将docker镜像更新到这个版本，web端的错误信息消失了，但是一片空白，什么也没有！ @boojack

me too

me to +1

@s544838371 Please check the latest version again, it might be fixed with ec20610. And it's better to open it in an incognito window.

Thanks, latest version works for me.

2024/03/04 02:55:48 INFO OK method=/memos.api.v2.WorkspaceSettingService/GetWorkspaceSetting 2024/03/04 02:55:49 INFO OK method=/memos.api.v2.AuthService/GetAuthStatus 2024/03/04 02:55:49 INFO OK method=/memos.api.v2.UserService/GetUserSetting 2024/03/04 02:56:04 INFO OK method=/memos.api.v2.WorkspaceSettingService/GetWorkspaceSetting 2024/03/04 02:56:04 INFO client error method=/memos.api.v2.AuthService/GetAuthStatus error="rpc error: code = Unauthenticated desc = user not found"

I'm also having it, but it seems a different bug. I have it on the server-side, not on the client-side

@grigio I think it might be some normal logs from API requests. You don't have to worry about that.

2024/03/04 02:55:48 INFO OK method=/memos.api.v2.WorkspaceSettingService/GetWorkspaceSetting 2024/03/04 02:55:49 INFO OK method=/memos.api.v2.AuthService/GetAuthStatus 2024/03/04 02:55:49 INFO OK method=/memos.api.v2.UserService/GetUserSetting 2024/03/04 02:56:04 INFO OK method=/memos.api.v2.WorkspaceSettingService/GetWorkspaceSetting 2024/03/04 02:56:04 INFO client error method=/memos.api.v2.AuthService/GetAuthStatus error="rpc error: code = Unauthenticated desc = user not found"

@wu0lei @grigio  user not found，I think the prompt is due to not being logged in to your account.

Now that the latest version of docker has solved the problem, the issue will be closed, thanks to everyone!


Missing license file

The project is missing a license file.

Yes I looked it up based on the link.  It is not referenced anywhere else, such as someone coming across a folder of the source.
In my case I'm using it in the context of Yocto/OpenEmbedded.  The expectation of this build framework is that it has an explicit license file in the actual repo.
It's a formality.

It's in the repo, however it's under the folder flutter_secure_storage. I will copy it to the main directory as well.