Usage Example throws all kind of errors

this are the errors its throwing and its very confusion for newbies
warning: unused import: `std::fs::File`
 --> src\main.rs:4:5
  |
4 | use std::fs::File;
  |     ^^^^^^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

error[E0277]: the `?` operator can only be used in a function that returns `Result` or `Option` (or another type that implements `std::ops::Try`)
  --> src\main.rs:7:16
   |
6  | / fn main() {
7  | |     let file = std::fs::File::open("fixtures/self/foo.pdb")?;
   | |                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ cannot use the `?` operator in a function that returns `()`
8  | |     let mut pdb = pdb::PDB::open(file)?;
9  | |
...  |
21 | |     }
22 | | }
   | |_- this function should return `Result` or `Option` to accept `?`
   |
   = help: the trait `std::ops::Try` is not implemented for `()`
   = note: required by `std::ops::Try::from_error`

error[E0277]: the `?` operator can only be used in a function that returns `Result` or `Option` (or another type that implements `std::ops::Try`)
  --> src\main.rs:8:19
   |
6  | / fn main() {
7  | |     let file = std::fs::File::open("fixtures/self/foo.pdb")?;
8  | |     let mut pdb = pdb::PDB::open(file)?;
   | |                   ^^^^^^^^^^^^^^^^^^^^^ cannot use the `?` operator in a function that returns `()`
9  | |
...  |
21 | |     }
22 | | }
   | |_- this function should return `Result` or `Option` to accept `?`
   |
   = help: the trait `std::ops::Try` is not implemented for `()`
   = note: required by `std::ops::Try::from_error`

error[E0277]: the `?` operator can only be used in a function that returns `Result` or `Option` (or another type that implements `std::ops::Try`)
  --> src\main.rs:10:24
   |
6  | / fn main() {
7  | |     let file = std::fs::File::open("fixtures/self/foo.pdb")?;
8  | |     let mut pdb = pdb::PDB::open(file)?;
9  | |
10 | |     let symbol_table = pdb.global_symbols()?;
   | |                        ^^^^^^^^^^^^^^^^^^^^^ cannot use the `?` operator in a function that returns `()`
...  |
21 | |     }
22 | | }
   | |_- this function should return `Result` or `Option` to accept `?`
   |
   = help: the trait `std::ops::Try` is not implemented for `()`
   = note: required by `std::ops::Try::from_error`

error[E0277]: the `?` operator can only be used in a function that returns `Result` or `Option` (or another type that implements `std::ops::Try`)
  --> src\main.rs:13:30
   |
6  | / fn main() {
7  | |     let file = std::fs::File::open("fixtures/self/foo.pdb")?;
8  | |     let mut pdb = pdb::PDB::open(file)?;
9  | |
...  |
13 | |     while let Some(symbol) = symbols.next()? {
   | |                              ^^^^^^^^^^^^^^^ cannot use the `?` operator in a function that returns `()`
...  |
21 | |     }
22 | | }
   | |_- this function should return `Result` or `Option` to accept `?`
   |
   = help: the trait `std::ops::Try` is not implemented for `()`
   = note: required by `std::ops::Try::from_error`

error[E0599]: no variant named `PublicSymbol` found for enum `pdb::SymbolData<'_>`
  --> src\main.rs:15:33
   |
15 |             Ok(pdb::SymbolData::PublicSymbol{function: true, segment, offset, ..}) => {
   |                                 ^^^^^^^^^^^^ variant not found in `pdb::SymbolData<'_>`

error[E0599]: no method named `name` found for struct `pdb::Symbol<'_>` in the current scope
  --> src\main.rs:17:71
   |
17 |                 println!("{:x}:{:08x} is {}", segment, offset, symbol.name()?);
   |                                                                       ^^^^ method not found in `pdb::Symbol<'_>`

error[E0277]: the `?` operator can only be used in a function that returns `Result` or `Option` (or another type that implements `std::ops::Try`)
  --> src\main.rs:17:64
   |
6  | / fn main() {
7  | |     let file = std::fs::File::open("fixtures/self/foo.pdb")?;
8  | |     let mut pdb = pdb::PDB::open(file)?;
9  | |
...  |
17 | |                 println!("{:x}:{:08x} is {}", segment, offset, symbol.name()?);
   | |                                                                ^^^^^^^^^^^^^^ cannot use the `?` operator in a function that returns `()`
...  |
21 | |     }
22 | | }
   | |_- this function should return `Result` or `Option` to accept `?`
   |
   = help: the trait `std::ops::Try` is not implemented for `()`
   = note: required by `std::ops::Try::from_error`

error: aborting due to 7 previous errors

Some errors have detailed explanations: E0277, E0599.
For more information about an error, try `rustc --explain E0277`.
error: could not compile `rustpro`.

To learn more, run the command again with --verbose.

Thanks for reporting this, @serak! The example is now synchronized with the one from the top-level library docs.


Not being to upload Custom Variables as a part of CM offline conversion data

Hi There,
We are running Megalista implementation for a client for quite a long time. It's been working wonderfully so far.
However, in one of the scenarios, where we use the CM offline conversion upload functionality, it uploads all the data except Custom Variables. Below are the steps that we have performed and confirmed at our end.

All these custom variables are available and enabled on the floodlight level.
We also used regular API calls to push these same variables into the CM platform and that worked fine. So the problem is not with the data or setup on the CM part.

We value your time and effort. However, it would be of huge help if it would be possible to look at this from Megalista's end.
Any help or guidance would be highly appreciated, as we are not sure how to proceed beyond this point.
Additionally, if any input is needed from our end, we would be happy to contribute.
Thanks & Regards,
Sandhya

Hi Sandhya.
First of all, sorry for the delay in getting back to you.
Can you confirm when this instance of Megalista was deployed on your client environment?
It would be really helpful to know the Megalista "version" they're running so that we can pinpoint the issue.
For your reference, we've merged the commit that implemented custom variables in Megalista on Aug 16, 2021, so if you've deployed Megalista for this client earlier, high chances that they're just using an old version.
If not, let us know and we can try to debug it together.
Cheers,
Caio

Hi Sandhya.
First of all, sorry for the delay in getting back to you.
Can you confirm when this instance of Megalista was deployed on your client environment?
It would be really helpful to know the Megalista "version" they're running so that we can pinpoint the issue.
For your reference, we've merged the commit that implemented custom variables in Megalista on Aug 16, 2021, so if you've deployed Megalista for this client earlier, high chances that they're just using an old version.
If not, let us know and we can try to debug it together.
Cheers, Caio

Hi Caio,
Thank you so much for your response. I really appreciate it and no worries about the delay part.
Regarding the "Megalista version", I did a redeploy with the latest version around a month and a half back, as the previous version deployed was "Megalist".
Also, I went through pull request #41, it seems the code running in the client's env is updated with the same.
Kindly let me know how to move forward with this. Also, happy to provide more details if needed.
Thanks,
Sandhya

Thanks for confirming Sandhya!
This is kind of surprising because we do have tests verifying that the customVariables are built into the final CM API body for the CM connector (see here for your reference).
Can you provide an anonymized/mock sample of the data you're trying to upload so that I can try to reproduce the issue on my side? Maybe there's some specific structure that you're trying to use that we have not predict in our tests.

Thanks for confirming Sandhya!
This is kind of surprising because we do have tests verifying that the customVariables are built into the final CM API body for the CM connector (see here for your reference).
Can you provide an anonymized/mock sample of the data you're trying to upload so that I can try to reproduce the issue on my side? Maybe there's some specific structure that you're trying to use that we have not predict in our tests.

Thanks again for your quick response Caio! Really appreciate it.
Please find here a screenshot of the sample data for your reference.

In the above screenshot, Variables U1, U3, and U7 stand for ConfCode, OAB_ID, and Device ID, respectively. I hope this helps.
Kindly let me know f I can help with anything else.

Hi @caiotomazelli,
I hope the sample data that I shared earlier has been of help. But was just curious to know if there are any updates related to the same. Additionally, happy to help with any further data/information or support.
Thanks,
Sandhya

Hi @Sandhya-1988 sorry for the delay getting back to you.
Looks like it's going to be an easy fix: your custom variable columns are using snake_case as opposed to camelCase, which is what we expect, as you can see below:

Also, check out our Example BQ Data for Testing to see how data should be structured in BQ for customVariables (it must be a single Array column).
I'll close the issue for now but feel free to reopen if you need anything else.
Cheers,
Caio


UI Error in Safari

General information
version of ShellHub): 0.4.0 (ShellHub is running on localhost in a docker-compose container
Safari: 13.1.2 (146<IP_ADDRESS>.5)
Chrome: Version 84.0.4147.135
Mac OSX: 10.14.6 (macOS Mojave)
Problem description
Some icons are not shown correctly in the UI and the navigations fails. The problem occurs only in Safari.
Problem story

After logging into ShellHub some UI icons are not shown.

Attached are two screenshots to illustrate the icon problem

Also the navigation in the left menu bar is not working in the Safari browser. The following menu entries produce some errors. The UI didn't respond to the click event and didn't transition to the new view. For the error log please refer to the attachments section.

Devices
Sessions
Firewall Rules

Attachements - Screenshots
Screenshot in the Chrome browser

Screenshot in the Safari browser

Attachments - Error Logs UI
Error Log Devices
[Error] SyntaxError: Unexpected token '<'
(anonyme Funktion) (devices.41bbfcbc.js:1)
[Error] ChunkLoadError: Loading chunk devices failed.
(missing: http://localhost/js/devices.41bbfcbc.js)
o (chunk-vendors.c38e9b1e.js:39:20557)
(anonyme Funktion) (chunk-vendors.c38e9b1e.js:39:21028)
(anonyme Funktion) (chunk-vendors.c38e9b1e.js:39:16875)
promiseReactionJob
[Error] SyntaxError: Unexpected token '<'
(anonyme Funktion) (chunk-a6ebbc5e.9004940f.js:1)
[Error] SyntaxError: Unexpected token '<'
(anonyme Funktion) (chunk-ebd2cd9e.d7631a6b.js:1)
[Error] SyntaxError: Unexpected token '<'
(anonyme Funktion) (chunk-25e298bc.960fc29b.js:1)
Error Log Sessions
[Error] SyntaxError: Unexpected token '<'
(anonyme Funktion) (chunk-a6ebbc5e.9004940f.js:1)
[Error] ChunkLoadError: Loading chunk chunk-a6ebbc5e failed.
(missing: http://localhost/js/chunk-a6ebbc5e.9004940f.js)
o (chunk-vendors.c38e9b1e.js:39:20557)
(anonyme Funktion) (chunk-vendors.c38e9b1e.js:39:21028)
(anonyme Funktion) (chunk-vendors.c38e9b1e.js:39:16875)
promiseReactionJob
[Error] SyntaxError: Unexpected token '<'
(anonyme Funktion) (chunk-5d149bb1.b50e4281.js:1)
Error Log Firewall Rules
[Error] SyntaxError: Unexpected token '<'
(anonyme Funktion) (chunk-a6ebbc5e.9004940f.js:1)
[Error] ChunkLoadError: Loading chunk chunk-a6ebbc5e failed.
(missing: http://localhost/js/chunk-a6ebbc5e.9004940f.js)
o (chunk-vendors.c38e9b1e.js:39:20557)
(anonyme Funktion) (chunk-vendors.c38e9b1e.js:39:21028)
(anonyme Funktion) (chunk-vendors.c38e9b1e.js:39:16875)
promiseReactionJob
[Error] SyntaxError: Unexpected token '<'
(anonyme Funktion) (chunk-2ce4287c.45868ea5.js:1)

@leonardojoao do you have any idea on how it is possible to test it using Safari browser without a Mac?
I think that Mac users should not be ignored

So, I tested the project using the scope configuration specification.
Fisrt, I runned the ShellHub version 0.4.0. Then, I created the tunnel to shared my localhost environment.
Finally, I used the URL generated for use in an online application, you have the possibility to select the operating system, browser and version list.
But, I can't reproduce the error.

@MPP-SG, we are unable to reproduce this issue. As we did not receive feedback since September, we are assuming it has been fixed.
Please reopen otherwise.

@MPP-SG, we are unable to reproduce this issue. As we did not receive feedback since September, we are assuming it has been fixed.
Please reopen otherwise.


Render the correct time for proposal cards

The time is being calculated wrong in the proposal cards. I believe there is a function for calculating time in the VotezUp app

Where can we find the VotezUp app?


Bump v2.1.1

Before you submit this PR: make sure to put all operations-related information in a wiki-note, a PR should be about code and is publicly accessible
What does the code in this PR do / what does it improve?
Can you briefly describe how it works?
Can you give a minimal working example (or illustrate with a figure)?
Please include the following if applicable:

[ ] Update the docstring(s)
[ ] Update the documentation
[ ] Tests to check the (new) code is working as desired.
[ ] Does it solve one of the open issues on github?

Notes on testing

Until the automated tests pass, please mark the PR as a draft.
On the XENONnT fork we test with database access, on private forks there is no database access for security considerations.

All italic comments can be removed from this template.

coverage: 93.533% (+0.02%) from 93.511% when pulling b8a5350d43ef897e7c25d427502a25ff5a9e904e on bump_211 into 8a499f570f08475768df81e0de09cce47ee1995c on master.


Offline indication

https://github.com/hubspot/offline
https://github.com/vaadin/expense-manager-demo

#51 Implementation using app-storage/app-network-status-behavior


Add Fedora IoT bootc bootable containers [Top Level]

Phase 1 - Container image

[ ] #16
[ ] #17
[ ] #18
[ ] #19

Phase 2 - Disk images

[ ] Create disk images with osbuild to produce disk images (Anaconda, installer etc)

@cgwalters we'll use this to track the proper way of producing and delivering the iot image - as I think I've understood it, we would leverage the fedora infra to either 1) derive directly from the fedora base bootc images or 2) perhaps just derive in a Dockerfile (?) - anything you want to add?

This is a big complex topic but it certainly seems to me like success here is that IoT's default stance is being a set of reference examples (possibly with pre-built containers) that derives from a common base image by default as a Containerfile indeed.
Now, it is very clear to me that a lot of demanding use cases will want to build their own base images.  And we need to make that work well too, which is a thread that crosses all of this.

This is a big complex topic but it certainly seems to me like success here is that IoT's default stance is being a set of reference examples (possibly with pre-built containers) that derives from a common base image by default as a Containerfile indeed.

I believe as long as we have pre-built containers whether we build them as base images or derive and podman build makes sense (I personally have no strong opinion, maybe I like the Containerfile+podman build better as it's simpler too w/o going rpm-ostree).

Now, it is very clear to me that a lot of demanding use cases will want to build their own base images. And we need to make that work well too, which is a thread that crosses all of thi

This is probably gonna be part of some investigation we can do as part of this issue too and understand shortcomings of either approaches to make an informed call on what we need (or fix the toolings to make us do what we need)

cc @travier too
It seems we can follow what other Fedora based spins are doing too - that is, leverage the work done in pungi to re-use the rpm-ostree manifest and just build a base container out of that, leaving us the possiblity to further play with the manifest if needed and until something "cross-fedora" is identified perhaps (?)

Yes, this is the path I would follow/recommend. Containerfile based builds are good for derivatives, but base images are better composed directly by rpm-ostree compose image.


Stack overflow when getting quickinfo on alias with same name as module

module bar { }

import bar = bar;

When you hover over the bar alias you get the following stack overflow.
at getSymbolLinks (:10887:13)
at getTypeOfAlias (:12806:13)
at getTypeOfSymbol (:12836:17)
at getTypeOfAlias (:12808:17)
at getTypeOfSymbol (:12836:17)
at getTypeOfAlias (:12808:17)
at getTypeOfSymbol (:12836:17)
at getTypeOfAlias (:12808:17)
The issue seems to be that resolveAlias called by getTypeOfAlias is supposed to re-enter and return unknown symbol, but it's not.. therefor getTypeOfAlias is stack-overflowing.

For the record the same happens with findAllRefs and getOccurrences, but not goToDefinition.

Fixed by #3160


mkdirp module cannot be found

The problem affects the latest release.  It seems caused by the recently added loader-fs-cache dependency, which does not include mkdirp in the dependency list  (but it uses it).
I have reported it viankakrisna/loader-fs-cache#1, but I created this issue for people experiencing the same problem.

I've just run into this problem also.  Given that this 1.7.0 release is obviously broken, would it be possible to roll back the loader-fs-cache and release 1.7.1 and then iron out the issues in this bug report?
Right now this is completely breaking eslint-loader.
/cc @MoOx @viankakrisna

Sorry for the breakage! it's now released as 1.0.1

@davazp @jeremywiebe In this kind of scenario, the best thing to do is to use ~1.6.0 so you don't get the "bug". Reverting an improvement because of a small thing that you can workaround by having mkdir around or using an old version look crazy to me. Opening a PR to add the missing dep will take the same time as commenting here btw.
@viankakrisna no problem, this kind of things happen :) Thanks for fixing this quickly!

@viankakrisna that was fast!  Thank you.


Re-organize code according to kubectl/oc conventions

What is the purpose of this change? What does it change?
This work aims to fix #785. I'm creating this PR while the work is still ongoing so that interested parties can comment and decisions can be taken while code is still being written.
Was the change discussed in an issue?
#785
How to test changes?
If everything goes well, nothing will change externally for odo users so tests should work as expected.

Working on this is quite painful because it's quite difficult to rebase without duplicating work or knowing that the rebased work will need to be repeated each time a rebase needs to happen. I would like to perform 2 changes to master to make things simpler moving forward. I will open PRs once I'm done.

To make things easier I propose to proceed by steps by first merging #893 into master which should make it easier to track master in this PR.

Blocked by #914

:white_check_mark: odo build 57 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/bdb22c71ff by @metacosm)

Hi @metacosm how is this going?

@kadel moving slowly because I need other changes to be done first, spending a lot of time waiting for reviews / merges, rebasing or trying to figure out how to replicate a test failure… 😔

@metacosm If there is a PR that is blocking you and you are waiting for it to be merged, just ping me, I'll make sure that it is a priority.

:white_check_mark: odo build 278 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/445c2d2c6b by @metacosm)

:white_check_mark: odo build 311 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/f8fdd3b124 by @metacosm)

@kadel I'm actually at a stage where I cannot really move forward without making rather big changes to the code so I'm not too sure how to proceed since merging the changes from master will be quite difficult once these changes are made.

@kadel I'm actually at a stage where I cannot really move forward without making rather big changes to the code so I'm not too sure how to proceed since merging the changes from master will be quite difficult once these changes are made.

is this still an issue, or it was addressed by #1002?

:white_check_mark: odo build 542 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/0d8ea6e201 by @metacosm)

:white_check_mark: odo build 555 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/ab73b063d3 by @metacosm)

is this still an issue, or it was addressed by #1002?

No, this is address. I should be able to move forward much faster now.

:white_check_mark: odo build 557 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/b1c7f4771e by @metacosm)

:white_check_mark: odo build 563 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/11efad4c70 by @metacosm)

:white_check_mark: odo build 565 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/276de3d58a by @metacosm)

:white_check_mark: odo build 569 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/6e4c24d7a2 by @metacosm)

I don't have much knowledge of the internals of kubectl and oc, but this looks great nonetheless :P

@kadel odo -h should be fixed, though it should be noted that we now need to specify which flags we want to appear in the help explicitly via: https://github.com/redhat-developer/odo/pull/871/files#diff-ae6461ee1175c7152132051efcd0bbecR133
There is a weird indentation error which I think is caused by the interaction of complete and k8s templating… :(

:white_check_mark: odo build 587 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/180b3acac2 by @metacosm)

there is still something weird with help message --project and --skip-connection-check are shown on the same lin
  -p, --port=[]: Ports to be used when the component is created (ex. 8080,8100/tcp,9100/udp
      --project='': Project, defaults to active project      --skip-connection-check=false: Skip cluster check
  -v, --v=0: log level for V logs. Level varies from 0 to 9 (default 0).

@kadel odo -h should be fixed, though it should be noted that we now need to specify which flags we want to appear in the help explicitly via: https://github.com/redhat-developer/odo/pull/871/files#diff-ae6461ee1175c7152132051efcd0bbecR133
There is a weird indentation error which I think is caused by the interaction of complete and k8s templating… :(

for all flags, or only for root level flags?

@metacosm I've noticed that only service command has been updated to follow Complete/Validate/Run pattern.
Am I right when I assume that this PR is meant to be something like a template on how to do it?
And after this is merged, the rest of the commands can be splitted between multiple people and worked in parallel?

Exactly.

There is a weird indentation error which I think is caused by the interaction of complete and k8s templating… :(

for all flags, or only for root level flags?

I am not too sure yet.

there is still something weird with help message. --skip-connection-check is always shown on the same line as the previous flag
odo create -h
....
  -p, --port=[]: Ports to be used when the component is created (ex. 8080,8100/tcp,9100/udp
      --project='': Project, defaults to active project      --skip-connection-check=false: Skip cluster check
  -v, --v=0: log level for V logs. Level varies from 0 to 9 (default 0).
...

odo -h
....
  -y, --y=false: Don't prompt user for typing 'yes' when installing completion      --skip-connection-check=false: Skip
cluster check
....

@kadel That's the weird indentation I was talking about. This seems to be an issue with kubectl templates: https://github.com/redhat-developer/odo/blob/c88f02e247710c51c11ac4662ea69086e1bbcaf9/vendor/k8s.io/kubernetes/pkg/kubectl/cmd/templates/templates.go#L51
The second if section should be on a different line to properly put the flags on a different line. Or, at least, that's how it looks to me. Maybe I'm missing something?

If I add a new line there, then the display of options is fixed, however that means modifying a file in vendor. Note that I checked and, unless I'm mistaken, it seems that this issue is also present in kubectl master: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/util/templates/templates.go#L51-L54

I've also noticed that there are commands missing from the output :-(
Help from this PR:
▶ odo -h
Odo (OpenShift Do) is a CLI tool for running OpenShift applications in a fast and automated matter. Odo reduces the
complexity of deployment by adding iterative development without the worry of deploying your source code. Find more
information at https://github.com/redhat-developer/odo

Examples:
  # Creating and deploying a Node.js project
  git clone https://github.com/openshift/nodejs-ex && cd nodejs-ex
  odo create nodejs
  odo push
  # Accessing your Node.js component
  odo url create

Other Commands:
  app         Perform application operations
  project     Perform project operations

Component Commands:
  component   Components of application
  create      Create a new component
  delete      Delete an existing component
  describe    Describe the given component
  link        Link component to a service or component
  list        List all components in the current application
  log         Retrieve the log for the given component.
  push        Push source code to a component
  update      Update the source code path of a component
  watch       Watch for changes, update component on change

Utility Commands:
  login       Login to cluster
  logout      Log out of the current OpenShift session
  version     Print the client version information

Other Commands:
  help        Help about any command

Options:
      --complete=false: Install completion for odo command
      --uncomplete=false: Uninstall completion for odo command
  -y, --y=false: Don't prompt user for typing 'yes' when installing completion      --skip-connection-check=false: Skip
cluster check
  -v, --v=0: log level for V logs. Level varies from 0 to 9 (default 0).

Use "odo <command> --help" for more information about a given command.

Help from current master:
▶ ./odo.master -h
Usage:
  odo [command]

Examples:
  # Creating and deploying a Node.js project
  git clone https://github.com/openshift/nodejs-ex && cd nodejs-ex
  odo create nodejs
  odo push

  # Accessing your Node.js component
  odo url create

Component Commands:
  component   Components of application.
  create      Create a new component
  delete      Delete an existing component
  describe    Describe the given component
  link        Link component to a service or component
  list        List all components in the current application
  log         Retrieve the log for the given component.
  push        Push source code to a component
  update      Update the source code path of a component
  watch       Watch for changes, update component on change

Other Commands:
  app         Perform application operations
  catalog     Catalog related operations
  project     Perform project operations
  service     Perform service catalog operations
  storage     Perform storage operations
  url         Expose component to the outside world

Utility Commands:
  login       Login to cluster
  logout      Log out of the current OpenShift session
  utils       Utilities for terminal commands and modifying Odo configurations
  version     Print the client version information

Flags:
      --alsologtostderr                  log to standard error as well as files
      --complete                         Install completion for odo command
      --log_backtrace_at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
      --log_dir string                   If non-empty, write log files in this directory
      --logtostderr                      log to standard error instead of files (default false)
      --skip-connection-check            Skip cluster check
      --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
      --uncomplete                       Uninstall completion for odo command
  -v, --v Level                          log level for V logs. Level varies from 0 to 9 (default 0).
      --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
  -y, --y                                Don't prompt user for typing 'yes' when installing completion

Use "odo [command] --help" for more information about a command.

You can see that almost all commands (like service, storage, catalogorurl) from Other Commands:are missing.utils` from utility commands is also missing.
Also some logging related flags are not there in the output

If I add a new line there, then the display of options is fixed, however that means modifying a file in vendor. Note that I checked and, unless I'm mistaken, it seems that this issue is also present in kubectl master: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/util/templates/templates.go#L51-L54

Not user if using kubernetas templates was a good idea :-(

That's what oc is doing so thought this fit into this change. I can revert this, though… What do you think, @kadel ?

:white_check_mark: odo build 612 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/cfb6d5f0f0 by @metacosm)

Now I'm having issues with --complete flags. It doesn't work for me :-( It just shows the help message :-(

:white_check_mark: odo build 616 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/c8c82f417a by @metacosm)


PHP Fatal error:  Default value for parameters with a class type hint can only be NULL in \QrCode.php on line 61

I simply install via composer and tried the advanced code as is in the Readme
Updated to PHP 7.2 after a couple of previous errors.
composer require endroid/qr-code

Looks like you are running your script in php < 7. Versions prior to php 7 expect a "string" class because the scalar type "string" does not yet exist.

I have confirmed I am running and I am still getting that same error
<EMAIL_ADDRESS>

Hmm too bad. I have no idea why php 7 incorrectly interprets the scalar type hint as a class type hint. Maybe you can post your issue in a php discussion group as it is a language related issue and people there probably have more expertise on this.

Actually, please ignore this for now with my apologies, I think my server might be giving me some issues and I don’t want to waste your time. I will come back to this once I work this out and the problem persists. Or I will update you and close the ticket. I appreciate your time.

@robp2175 Have you figured this out yet? I'm also running on php 7.1 and i'm getting this error, too.


.Net security vulnerability (putty ports #503, 505)

see microsoft's security update #4.03 (July 2021).

.Net version has been updated, vulnerability has been fixed.


Do not atomic decrement in drop when refcount == 1

There's PR #88 which implements it.
With patch applied, benchmark becomes measurably (about 5%) faster.
Same optimization is implemented in libc++:
void
__shared_weak_count::__release_weak() _NOEXCEPT
{
    // NOTE: The acquire load here is an optimization of the very
    // common case where a shared pointer is being destructed while
    // having no other contended references.
    //
    // BENEFIT: We avoid expensive atomic stores like XADD and STREX
    // in a common case.  Those instructions are slow and do nasty
    // things to caches.
    //
    // IS THIS SAFE?  Yes.  During weak destruction, if we see that we
    // are the last reference, we know that no-one else is accessing
    // us. If someone were accessing us, then they would be doing so
    // while the last shared / weak_ptr was being destructed, and
    // that's undefined anyway.
    //
    // If we see anything other than a 0, then we have possible
    // contention, and need to use an atomicrmw primitive.
    // The same arguments don't apply for increment, where it is legal
    // (though inadvisable) to share shared_ptr references between
    // threads, and have them all get copied at once.  The argument
    // also doesn't apply for __release_shared, because an outstanding
    // weak_ptr::lock() could read / modify the shared count.
    if (__libcpp_atomic_load(&__shared_weak_owners_, _AO_Acquire) == 0)
    {
        // no need to do this store, because we are about
        // to destroy everything.
        //__libcpp_atomic_store(&__shared_weak_owners_, -1, _AO_Release);
        __on_zero_shared_weak();
    }
    else if (__libcpp_atomic_refcount_decrement(__shared_weak_owners_) == -1)
        __on_zero_shared_weak();
}

Closing due to inactivity.


Add getRange and getCut to OwnedLocation

Fixes #141

This is waiting on #143, which fixes #142. Once that goes in one of the unit tests included in this pull request will get no longer be an expected failure.


Remove uses of boost::promote_args and boost/math/tools/promotion.hpp

Summary
There was only one remaining use of boost::promote_args, and a number of using/includes were left over of other template metaprogramming cleanups. Fixes #1426.
Tests
Existing tests should be enough.
Side Effects
None.
Checklist

[X] Math issue #1426

[X] Copyright holder: Marco Colombo
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[X] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[X] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

Fantastic work again @mcol
I think there are also a few of these in the test/unit folder - example? We can handle those separately also if you want.

You're right, how did I miss them? :) Let's remove them here.

+1 to changing the name.  Is the basic idea to find the minimal type that's mutually assignable by all arguments?

On Dec 1, 2019, at 11:18 PM, Steve Bronder<EMAIL_ADDRESS>wrote:
@SteveBronder requested changes on this pull request.
Thanks! I think for these we just need to change promote_args_t to return_type_t and it's good to go.
Thinking about it more tho, do wonder whether we should change return_type_t to be named promote_type_t since that seems to get across promote to the highest type more accurately. I'll leave it to your discretion
In stan/math/prim/mat/prob/lkj_cov_lpdf.hpp:

@@ -58,12 +56,11 @@ return_type_t<T_y, T_loc, T_scale, T_shape> lkj_cov_lpdf(
}

template <typename T_y, typename T_loc, typename T_scale, typename T_shape>
-inline typename boost::math::tools::promote_args<T_y, T_loc, T_scale,

                                            T_shape>::type

-lkj_cov_lpdf(const Eigen::Matrix<T_y, Eigen::Dynamic, Eigen::Dynamic>& y,

        const Eigen::Matrix<T_loc, Eigen::Dynamic, 1>& mu,

        const Eigen::Matrix<T_scale, Eigen::Dynamic, 1>& sigma,

        const T_shape& eta) {

+inline promote_args_t<T_y, T_loc, T_scale, T_shape> lkj_cov_lpdf(
I think we can replace all of these promote_args_t to be return_type_t. May even be good to take it a step further and make promote_arg_t into an internal namespace within the return_type.hpp. Then I think it would be easier to see that promote_args_t is only used internally for return_type_t
In test/unit/math/rev/mat/functor/util_algebra_solver.hpp:

@@ -33,14 +34,12 @@ Eigen::Matrix<T2, Eigen::Dynamic, 1> general_algebra_solver(

struct simple_eq_functor {
template <typename T0, typename T1>

inline Eigen::Matrix<typename boost::math::tools::promote_args<T0, T1>::type,

                  Eigen::Dynamic, 1>

inline Eigen::Matrix<stan::promote_args_t<T0, T1>, Eigen::Dynamic, 1>

Same return_type_t here as well
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

+1 to changing the name.  Is the basic idea to find the minimal type that's mutually assignable by all arguments?

Yeah I think the intent is the common_type that respects the var>doubles > int hierarchy etc.

@mcol I think your right it would probably be reasonable to do this in a seperate PR

You should be able to merge @SteveBronder. You have permission on maintainers (you're the only one with a status!).

Yes I can merge, though I personally find pressing the merge button satisfying on my PRs so I like to let the PR submitter do so :)

I find it much more satisfying when the PR, branch, and issue just disappear off the radar.  But I can see mileage may vary.  Sorry if I deprived anyone of the fun of merging.


feat(DTFS2-NONE): update logo to tudor crown

Introduction :pencil2:
We need to update the crown to be a tudor crown
Resolution :heavy_check_mark:
Kept the existing pattern for the header pages, and updated the svg following html guides here:
https://github.com/alphagov/govuk-frontend/releases/tag/v4.8.0
Miscellaneous :heavy_plus_sign:
The current setup is most likely due to the requirement to have many more additional class tags on the header element, so I've kept the file the same for now.

closed as ticket now exists


Add starcraft and Carla environments to CI / dockerfiles

Work on this is blocked by #198 at the moment, but these environments are not yet part of our regular CI golden + trace test flows.

Starcraft environment, container building, and testing has now been added in #169.  Carla cannot be added until we have GPU workers in CI.


Badges were missing from the tutorials page

Badges were missing from the tutorials page.

Should we use the same table structure here as in README (for the consistency)?


isNull() throwing deprecation warnings

I am trying to use validator.isNull() with a var that I have tried to instantiate as null, undefined or as new String(null), but none of these cases seem to work with isNull, I am always receiving the same error:
validator deprecated you tried to validate a object but this library (validator.js) validates strings only. Please update your code as this will be an error soon.

How can this be coerced correctly, or should this function be modified or removed in light of the String only validation?
Looking at the source for isNull would suggest a better name name and description would be isEmpty seeing as this is a simple length check.

The library validates strings only. Automatic coercion of input to a string was deprecated and then removed in the latest release. Passing anything that isn't a string will now result in an error.
isNull() should have probably been renamed to isEmpty() (or similar) in that release. Previously null and undefined input would have been coerced to an empty string; now all the validator does is check if the input string has a length of zero. I'll update the README so that this is clear.
I only just bumped v4 to v5 so I'm not prepared to make a breaking change to rename it.


Hi, this is really amazing!

I just built the vst3 which worked fine (linux)
the only step i found missing was the submodules which i got with
git submodule update --init --recursive
if you want to add it to the readme.
As probably expected some jsfx load and work, some don't.
Are you interested in testing feedback already or is it too early in the process?
Anyway very exciting!

Yes please, send all the feedback, this would be much appreciated.

Cool so here is a very quick unorganized look (ignoring gfx):

Any jsfx that look for files in other directories don't load
two examples:
https://github.com/geraintluff/jsfx/blob/master/Level Meter.jsfx#L10

[ysfx] error: Level Meter.jsfx: cannot find import: delay-utils.jsfx-inc
[ysfx] error: ???: no source is loaded, cannot compile

https://github.com/JoepVanlier/JSFX/tree/master/Squashman
[ysfx] error: Squashman.jsfx: cannot find import: squashman_upsamplers.jsfx-inc
[ysfx] error: ???: no source is loaded, cannot compile

jsfx that don't have a desc: field don't load (but that's a descision you made i think?)

If sliders are dropdown menus I see this a lot:
[ysfx] warning: slider5: the enumeration has an invalid range
with the then following dropdowns being ignored
example:

https://github.com/JoepVanlier/JSFX/blob/master/Basics/MS-20.jsfx

From the ones that come with reaper:
The analysis jsfx don't have outputs mapped which reaper can see and uses the option
"pass through unmapped output channels" by default
with the vst you have to uncheck the outputs manually to get sound through.

So far for now, like I said just a quick look.
If you know all this already please let me know (before I spam your issue tracker with known stuff :) )

Any jsfx that look for files in other directories don't load

I can't repro this one at all, what is your setup?

jsfx that don't have a desc: field don't load (but that's a descision you made i think?)

That field is specified as required, I was supposing that all jsfx must have it.
Do you mind to link one of these files?

with the then following dropdowns being ignored

The warning here is inconsequent, the reality is that following sliders have a syntax problem in them.
As you see, it has 2 opening < characters.
slider6:1<0,1,1<{Off,On}>Inertia
Regardless, thanks for noting, i'll make the parser more permissive.

You cannot repro means it works for you?
I don't have a special setup, all jsfx go in .config/Reaper/Effects (imported via reapack but that doesn't change the hierarchy)
I think the specs are pretty lose at various points, you can do all sorts of things "wrong" and it still works
(inside reaper, which is what I compared it to) which is of course good and bad, but also means that's how a lot of jsfx look like :)
example that doesn't use desc:  https://github.com/leafac/reaper/blob/main/Effects/leafac_Bit crusher.jsfx
(but you can also just delete that line from any jsfx and load it in reaper)

I think the specs are pretty lose at various points

Yes that's what I figured, and I already identified some of the cases, and fixed a few from jsusfx.
It happens that the spec is sometimes plain wrong, checking against Reaper is a better reference.
Anyway I've fixed MS20 at least, and added a unit test for that; we can improve the test suite with cases like that as we go, it's also the reason why i've made it.

You cannot repro means it works for you?

Yes it doesn't give that problem you refer to. You're loading via plugin right ?

yes with the plugin. i just tried again with the squashman example and it is the same message. cannot find import: squashman_upsamplers.jsfx-inc which is in the Dependencies folder.

The spec again mentions desc as required field, even as marker of jsfx file type to use for detection.
Unfortunately, Reaper is thinking otherwise.
It gets also in the way of how discovery is done in Carla, so that will be to revise as well.

cannot find import: squashman_upsamplers.jsfx-inc which is in the Dependencies folder.

Right I understand what's the deal here; whatever import files it doesn't find, it scans for them recursively in the Effects folder.

I think the hard requirement in reaper is the @sample block and a somewhat correct math.
It's perfectly fine to add a few more requirements for the plugin, that won't be a deal breaker :)

@sample definitely is not required. midi plugins don't use this

see not  even that

Great! I went through the Effects folder here, now all of them load and display all sliders,
the remaining errors I get are all gfx related, really cool.
Audio is not always there but I make that a separate issue.

the remaining errors I get are all gfx related, really cool.

Ok gfx is implemented as stubs, these errors should go away

Adding, because I just stumbled over it:
jsfx's import method (in reaper) is case insensitive.
example:  https://github.com/JoepVanlier/JSFX/blob/master/Yutani/Saike_FMFilter2.jsfx#L116
doesn't load in ysfx because of a case mismatch.
(sorry @JoepVanlier for using you as the example again :))

Hahaha, no worries! Thanks for pointing these things out @mynameismuhl . I'll do fixups on my end for this stuff as well. A lot of it comes from kind of sloppy coding practices when doing jsfx to be honest. That and no linter being available. Personally, I wouldn't mind a stricter implementation :D
Thanks @jpcima for setting all of this up. I frequently get requests from people who want to run some plugins in other DAWs on Linux and your implementation could be a great solution for them :)

jsfx's import method (in reaper) is case insensitive.

ah, yes, rather unfortunate, but true. I'll make this its own issue.
You're welcome @JoepVanlier , and your work has been helpful so far.

doesn't load in ysfx because of a case mismatch.

This one should be fine from now.

Since everything in here is either solved or in a separate issue I am closing this.


Improved Harvester Maintenance Mode broken

Problem:
The Improving Harvester Maintenance Mode feature has been broken by another PR by changing the logic which is responsible for shutting down VMs.
The for loop which iterates over the VMs to be shut down was probably mistakenly pulled in an if condition, which is unfortunately wrong and makes the previous logic inoperable.
Solution:
Adapt the original code to the new conditions.
Related Issue:
https://github.com/harvester/harvester/issues/6727
Test plan:
See https://github.com/harvester/harvester/pull/5328

@mergifyio backport v1.3


[UI][AKS] Use dynamic AKS cluster location for imported clusters

Followup for https://github.com/rancher/rancher/issues/33534
Currently UI hardcodes "eastus" as the AKS cluster location:
https://github.com/rancher/ui/blob/ea36d73a762f8c4e93d21f1019c6de8138df5d3c/app/models/cluster.js#L168
and uses it when creating an imported cluster object:

Once this fix is merged, the /meta/aksClusters call will return something like this:
$ curl -s -u $TOKEN "https://localhost:8443/meta/aksClusters?cloudCredentialId=cattle-global-data:cc-abcde" | jq .
[
  {
    "resourceGroup": "colleen-group",
    "clusterName": "colleen-1",
    "rbacEnabled": true,
    "location": "westus"
  },
  {
    "resourceGroup": "mj-demo",
    "clusterName": "mj-demo",
    "rbacEnabled": true,
    "location": "germanywestcentral"
  }
]

UI should use the location returned from /meta/aksClusters to populate resourceLocation in the cluster create request for imported clusters.
It's also unnecessary (but not harmful) to pass "region" and "tenantId" in to /meta/aksClusters:

Tested on rancher/rancher:master-head e83ac8c with rancher/aks-operator:v1.0.1-rc15
The location is now correctly fetched for the imported AKS server living in norwayeast azure location on attempt to update the cluster from rancher.

Close.


Typo in the website tutorial

typo in the tutorial " (we've aonly got one Show in this tutorial ☺):"
Can be found in the following link:
https://www.edgedb.com/tutorial/nested-structures/polymorphism/expressions

Checked to see someone updated the typo to be fixed.


runtime: Don't hardcode PATH_MAX

Windows' _fullpath and _getcwd will handle allocation if we pass NULL as the buffer, but please note that this will not remove path length limitations.
Unfortunately, posix_fs.jakt is not so straightforward.
realpath: POSIX.1-2008 lets us pass NULL for the second argument, resolved_path; libc will allocate for us.
getcwd: Linux lets us pass NULL, but POSIX defines this as undefined behavior. Can and should we special-case any os/libc whose getcwd will do the allocation for us?

We could add the means to select different modules based on libc, but iirc getcwd() will return with an error if the path doesn't fit in the buffer, so we should be able to keep allocating larger buffers until it returns non-NULL?

Paths over 4096 can now be returned by jakt's current_directory and real_path: We use the POSIX.1-2008 realpath behavior, and getcwd has a loop to grow the buffer size until the buffer is sufficient.
This does not mean Jakt is long path aware on POSIX, as that would require breaking paths up into relative paths that fit within PATH_MAX (which could be as low as _POSIX_PATH_MAX, 256) and using openat chaining (to implement filesystem apis that may fail on long paths such as as mkdir)


feat: add valgrind support to all images

What?
Add valgrind support to both images.
Why?
To allow memory profiling in CI for the compilers team.

It was decided to use the most recent valgrind and set it up differently, closing this one for now.


Implement [^'0'-'9'] syntax

Do you find the lack of this syntax to be a problem in practice?

Not really. I was just toying with lexgen.


baseimage

Problem description

Problem location

I saw a problem on the following URL:

I couldn't find the information I wanted. I expected to find it near the following URL:

Other:

Project version(s) affected

Suggestions for a fix

@nienie There's isn't any information on the ticket for us to take action on. I'm closing the issue here for that reason. Feel free to add more information on the ticket to continue the conversation.


dSYM upload fails after update to v1.3.4

After updating from version 1.3.2 to 1.3.4 of this plugin with no changes to my Fastfile, the upload_symbols_to_bugsnag step of my build process started failing.
Expected behavior
dSYM upload to Bugsnag succeeds
Observed behavior
Received the following error messages:
[12:21:44]: undefined method `each' for "/Users/distiller/project/ParkWhiz.app.dSYM.zip":String
[12:21:44]: You passed invalid parameters to 'upload_symbols_to_bugsnag'.
[12:21:44]: Check out the error below and available options by running `fastlane action upload_symbols_to_bugsnag`
...
[12:21:44]: Invalid default value for dsym_path, doesn't match verify_block

Steps to reproduce
Here is the relevant snippet of my Fastlane action:
gym(scheme: params[:scheme], export_method: "app-store", archive_path: archive_path(params))
upload_symbols_to_bugsnag

Version
Worked with version 1.3.2.  Failed with no changes to my Fastfile after update to version 1.3.4.
Additional information
I don't have time to investigate fully, but looking at your code, it appears that the issue is that the value of Actions.lane_context[SharedValues::DSYM_OUTPUT_PATH] is not an array; that causes the verify_block to fail when upload_symbols_to_bugsnag starts.
See:
https://github.com/bugsnag/bugsnag-dsym-upload/blob/v1.3.2/tools/fastlane-plugin/lib/fastlane/plugin/bugsnag/actions/upload_symbols_to_bugsnag.rb#L113

I ended up fixing my build script by replacing
upload_symbols_to_bugsnag

with
upload_symbols_to_bugsnag(dsym_path: [Actions.lane_context[SharedValues::DSYM_OUTPUT_PATH]])

but, as you know, this should not be necessary if default params are formed correctly.

@jbelkins Had the same issue and your solution worked. Thanks!

Yes, definitely there's an issue with the default value on the last update of the plugin

Jut got this after upgrading to v1.4.0 of the plugin.


Address brokenness/usability issues in the  #file context variable

A large GitHub Enterprise customer have expressed:

#file references are awkward because they can’t be pasted or derived from open tabs. They require interaction with a modal or a select list.  If I have a collection of say 5 files that are relevant for establishing context, this is painful to achieve. So I can’t paste #file refs into chat and make them turn “blue”.  A #tabs would have been more useful.
Basically, it should be possible to get parity with completions.

Another community member has expressed:

the announced context variable #file doesn't work. As I wrote, I tried #file context variable (even though not in the screenshot I shared). As expected, it said it referenced the whole file (lines 1-), but still right after it copilot chat said it can't access the file.

The second issue- the file will not be used when it is too large or doesn't fit into the context window. We can do more to compress it, and also it should be obvious whether the file was actually used: https://github.com/microsoft/vscode-copilot-release/issues/926
Will use this issue for the first point

Closing as we've made several improvements here over the last few releases:

You can do multi select of tabs and then drag and drop them into chat to add them as context
You can also do multi select in the file explorer view and search view to add files as context
In the file picker you can right arrow to add a file as context without closing the picker
In Copilot Edits you can click the Add Files button then select Open Editors to add all open editors to your working set

Also, for the second point, we now have larger context windows since a few months ago, so truncation should be less frequent, and there is a warning when part of the file is omitted.


bug: 'torch.dtype' object has no attribute 'lower'

Describe the bug
I am trying to host Mistral with a LoRA adapter on a GPU, when I tried to start the openllm server using
openllm mistral --serialization safetensors --backend vllm --quantize int4 --adapter-id /path/to/adapter:local_adapter
The server starts, after that, I am getting this error

Traceback (most recent call last):
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/starlette/routing.py", line 705, in lifespan
async with self.lifespan_context(app) as maybe_state:
File "/opt/conda/envs/pytorch/lib/python3.10/contextlib.py", line 199, in __aenter__
return await anext(self.gen)
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/bentoml/_internal/server/base_app.py", line 75, in lifespan
on_startup()
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/bentoml/_internal/runner/runner.py", line 317, in init_local
raise e
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/bentoml/_internal/runner/runner.py", line 307, in init_local
self._set_handle(LocalRunnerRef)
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/bentoml/_internal/runner/runner.py", line 150, in _set_handle
runner_handle = handle_class(self, *args, **kwargs)
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/bentoml/_internal/runner/runner_handle/local.py", line 27, in __init__
self._runnable = runner.runnable_class(**runner.runnable_init_params)  # type: ignore
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/openllm/_runners.py", line 148, in __init__
raise openllm.exceptions.OpenLLMException(f'Failed to initialise vLLMEngine due to the following error:\n{err}') from err
openllm_core.exceptions.OpenLLMException: Failed to initialise vLLMEngine due to the following error:
'torch.dtype' object has no attribute 'lower'

I tried without the quantization method as well, but i got the same error
To reproduce
openllm mistral --serialization safetensors --backend vllm --quantize int4 --adapter-id /path/to/adapter:local_adapter
Logs
No response
Environment
bentoml: 1.1.11
python: 3.10.11
platform: Linux-5.15.0-1036-aws-x86_64-with-glibc2.31
uid_gid: 1000:1000
conda: 22.11.1
in_conda_env: True
I am using openllm 0.4.41
System information (Optional)
GPU: A10g(g5.xlarge)

close for openllm 0.6


Devise Mailer

All user structure are defined. Configure devise mailer to recover password.

Hi, do you mind if I pick this up?

Go on @andela-mogala ! :+1:

Thanks @eduqg. Just for clarity, what should be the expected behaviour when this task is completed.
If you can put in the format below

When user does x, the system does y
...

Hey @andela-mogala. I should have clarified before.
In the page for login, must have a link with 'Forgot password?'. When the user click on it, one email must be sent with a link to recover the password. After that, the user must be redirected to one page to update a new password.
Must be created one config.action_mailer in initializers/development.rb. This link might help.


Crossbow?

Do you plan to import crossbow from Balkon's?

We thought about it and maybe we will add it in 0.7 already.

BUT: We won't import it. We will completely rewrite it, like every other weapon / feature in this mod

We already have the textures for normal and siege crossbows. They will come, we just might do some refactoring first...

After 1 month and 5 days, I have decided to work on it now. If you have any suggestions, just write them here ^^

Well, now it implemented correctly and works fine (see Fixes at ecddd2631fe8e55f630f784d80dce1f1bab6420e)


Add error logging capability during testing

Rather than stop the test at the first failure the test should log the error and continue. This will require a  logging to a central location (single file, database, etc.) from any number of tests run, at any level. It should capture which test failed, when it failed (date/time stamp), and what the error was.

Sounds like we should probably:

Switch the output to use the python logger: https://docs.python.org/2/library/logging.html
Change the custom python test scripts to not return an exit code (or we could also switch these to use pyunit - but would be more work)

Judson's work on the pilot project for logging and unittest are included in #308.

Status update as the unittest building progresses we've got this one working, where TestRunner.py calls a named logger (setting a unique log file) from UnitTestUtilities.py and puts it into .\solutions-geoprocessing-toolbox\utils\test\log.


[bal-nav] Add active state for deeper links in the navigation

[ ] Design an active link-state in Figma

🕹 Prototype:
https://www.figma.com/proto/TpLyniy71JAMZhps0qHhVU/Baloise-–-UI-Kit-(Team-Library)?page-id=187%3A2287&node-id=2711%3A18525&viewport=1871%2C541%2C0.11&scaling=min-zoom&starting-point-node-id=2711%3A18525&show-proto-sidebar=1
https://www.figma.com/file/TpLyniy71JAMZhps0qHhVU/Baloise-–-UI-Kit-(Team-Library)?node-id=42309%3A351617&viewport=16528%2C685%2C1.47
Propsal

https://jira.ibmix.de/browse/BARE-1035
https://jira.ibmix.de/browse/BARE-1036
Tickets are created on IBM's side.

Swapped this ticket to a design task


Update pnpm version to v9.13.2

This pull request includes updates to the package.json file to improve compatibility and maintain up-to-date dependencies.
Dependency updates:

Updated the pnpm version from 8 to 9 in the engines section.
Updated the packageManager version from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>

@damien-schneider can you also adapt the CI workflow?

@damien-schneider can you also adapt the CI workflow?

You're right, it is done. Upgraded pnpm action-setup to v4 and pnpm to v9.x.x

@psteinroe Would you prefer to specify the exact version v9.13.2 throughout, or should we remove this version specification from the global package.json to allow flexibility?

Please let me know when you’re ready to merge. Keeping the branch updated and resolving pnpm-lock conflicts for each package update is a bit tedious. 😅


kitti submission

Hi, it is a very nice work!
I would like to ask questions about kitti submission. When I get 'kitti_submission' folder, how can I create the right ZIP file.
The tips on the Kitti website are as follows:

For the optical flow task, do we only need to include the 'flow' folder in the submitted folder?So just rename your procedurally generated 'kitti_submission' folder to 'flow' and compress it into a ZIP file?

Yes, I think so.


Chevron icon is too large after Skin 16.1.0 update

latest skin version removed some CSS override which made the chevron look smaller. As a result the icon size has changed.

deployed


Cannot grow volume group！

when i  use weedfs， i often meet  “Cannot grow volume group”， i find  volume -max  （dufalut “7”） ，I need big storage ，so I modify the upper limit，But there are still problems ，what should  i do ？

increase the upper limit or post more details here.

I recently found such a mistake:
runtime: out of memory: cannot allocate 1310720-byte block<PHONE_NUMBER> in use)
fatal error: out of memory,
how can I solve it?

Add memory?
On Sun, Sep 17, 2017 at 8:42 PM Dr13am<EMAIL_ADDRESS>wrote:

I recently found such a mistake:
runtime: out of memory: cannot allocate 1310720-byte block<PHONE_NUMBER> in
use)
fatal error: out of memory,
how can I solve it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/chrislusf/seaweedfs/issues/562#issuecomment-330124358,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABeL78-w6zEHUY5nA_xA4MCytiP1VKMEks5sjeatgaJpZM4PaBB8
.

the pull request may have resolved this issue.


Integrated a Ping event

Added a Ping device Event, mostly in order to track the number of pings as a health statistic.

Codecov Report

Merging #124 into master will increase coverage by 0.1%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #124     +/-   ##
=========================================
+ Coverage   84.16%   84.27%   +0.1%
=========================================
  Files          81       81
  Lines        4597     4603      +6
=========================================
+ Hits         3869     3879     +10
+ Misses        629      626      -3
+ Partials       99       98      -1

Impacted Files
Coverage Δ

device/listener.go
86.79% <100%> (+1.37%)
:arrow_up:

device/manager.go
85.86% <100%> (+0.05%)
:arrow_up:

service/subscription.go
100% <0%> (+5.06%)
:arrow_up:

Continue to review full report at Codecov.

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


Blocking mob spawns does not work

i have set animals and monsters to false :
animals:
==: MVSpawnSubSettings
spawn: 'false'
spawnrate: '-1'
exceptions: []
monsters:
==: MVSpawnSubSettings
spawn: 'false'
spawnrate: '-1'
exceptions: []
yet animals still spawn.

This should no longer be the case.


Set the application-id in the Linux shell

Description
Set the application-id in the Linux shell.
Related Issues
Fixes https://github.com/flutter/flutter/issues/59234.
Tests
No tests added.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

Can I get Termux commands to hack FB that works

I've updated the test, but please check the following:

I'm pulling the application ID out of my_application.cc. This feels a bit hacky, so not sure if we want to move this into a more common location, e.g. CMakeLists.txt?
By requiring the test to run with Linux support, does this make it harder to run elsewhere? Should it be split out from the Android/iOS code?
I couldn't work out how to run the tests locally, so I'm relying on the CI system to have run them correctly.

Started Google testing for this PR

I'm pulling the application ID out of my_application.cc. This feels a bit hacky, so not sure if we want to move this into a more common location, e.g. CMakeLists.txt?

That would make the parsing less subject to accidental breakage. Probably worth doing in case this code gets used in production, rather than just tests.

By requiring the test to run with Linux support, does this make it harder to run elsewhere? Should it be split out from the Android/iOS code?

No, that's just the mock context; it'll run everywhere.

I couldn't work out how to run the tests locally, so I'm relying on the CI system to have run them correctly.

cd packages/flutter_tools
pub get
pub run test <relative path to test file>

Or if you use VS Code with the Flutter extension, you'll get an affordance to run individual tests from the UI.

Google testing passed!

I wasted far too much time trying to debug that regexp 🤯...
@stuartmorgan, can you have a quick look and see if the CMake changes look good to you. The only other thing I was thinking is the application ID is coded into both the CMakeLists.txt and my_application.cc - we could use a define/generated header to pass that variable through. I'm not sure what your preferred method of doing is that with CMake or if it really matters.

The only other thing I was thinking is the application ID is coded into both the CMakeLists.txt and my_application.cc - we could use a define/generated header to pass that variable through. I'm not sure what your preferred method of doing is that with CMake or if it really matters.

A define should work fine, and would be much simpler than a generated header, so that SGTM. I do think we shouldn't have it in two places, as that's a foot-gun.


Support unified commerce

Support unified commerce with the Terminal API

Hey,
Thank you very much for proposing this enhancement. Our team will review the proposal thoroughly and consider its potential implementation in the future.
Best regards.


Reduce heap allocations in proc.ListPIDs()

A small improvement to proc.ListPIDs().
Benchmarks from my local dev system:
Before
goos: linux
goarch: amd64
pkg: go.opentelemetry.io/ebpf-profiler/proc
cpu: 12th Gen Intel(R) Core(TM) i7-12800H
BenchmarkListPIDs-20                5373            203274 ns/op           57888 B/op       1025 allocs/op
PASS
ok      go.opentelemetry.io/ebpf-profiler/proc  1.139s

After
goos: linux
goarch: amd64
pkg: go.opentelemetry.io/ebpf-profiler/proc
cpu: 12th Gen Intel(R) Core(TM) i7-12800H
BenchmarkListPIDs-20                7153            171458 ns/op           24855 B/op        614 allocs/op
PASS
ok      go.opentelemetry.io/ebpf-profiler/proc  1.642s

I am thinking if we could just completely drop populatePIDs? It is called only at startup, and the intention is to pre-populate all processes to ebpf. However, I think this is unnecessary, as the new-process-seen mechanism will report the ones that are actually busy. Just removing this would speed up startup and reduce memory usage everywhere as the sleeping processes are not processed.
@christos68k @florianl What do you think?

I am thinking if we could just completely drop populatePIDs? It is called only at startup, and the intention is to pre-populate all processes to ebpf. However, I think this is unnecessary, as the new-process-seen mechanism will report the ones that are actually busy. Just removing this would speed up startup and reduce memory usage everywhere as the sleeping processes are not processed.

Fully agree on this :+1:

I think this is unnecessary, as the new-process-seen mechanism will report the ones that are actually busy. Just removing this would speed up startup and reduce memory usage everywhere as the sleeping processes are not processed.

Tbh, I wasn't aware of the lazy PID processing.
Removed the initial scanning for running processes.


rpc: Serialize in getblock without cs_main

Backported from bitcoin

https://github.com/bitcoin/bitcoin/pull/15932
https://github.com/bitcoin/bitcoin/pull/12151

NACK will be ported when merging 0.19


Make Nyan Cat Fly During Browser Capture

First off, you are truly doing God's work with this plug-in. Thanks for all the work that went into it.
I do have a feature request though. I'm currently running Karma tests against browsers captured via Sauce Labs. For each test I run, it takes about 15-75 seconds for the browser instance to be created and then captured. This delay would be much more tolerable if I could watch Nyan Cat fly through the night's sky as the capturing proceeds.
Currently, he doesn't start flying until the test actually begins executing. Since my tests normally take only a second or two to run, I end up barely seeing the animation at all. I only have 1 test out of 12 that actually runs long enough to see it.
Would it be possible to change the default or add a setting that one can opt into so that the animation kicks off much earlier/immediately in the test run?

Now that I think about it, what I want probably isn't possible. I'll go ahead and close this. Thanks again!


az tag update returns an invalid status 'Accepted'

This is autogenerated. Please review and update as needed.
Describe the bug
The tag update command is failing, even though the update is actually succeeding (as indicated by the accepted status).
Command Name
az tag update
Errors:
Operation returned an invalid status 'Accepted'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az tag update --resource-id {} --tags {} --operation {}

Expected Behavior
Environment Summary
macOS-12.4-arm64-arm-64bit, Darwin 21.5.0
Python 3.10.5
Installer: HOMEBREW

azure-cli 2.38.0

Additional Context

@zhoxing-ms  for awareness

Operation returned an invalid status 'Accepted'

This should be an error caused by the data structure returned by the ARM service.

According to my previous experience, this is probably caused by the fact that the return value of the service does not contain the error attribute.
@ScottColdwellTR Could you please provide the debug log to help service team investigate it?

Since this should be an ARM service issue, and the az tag update command is also owned by service team, so I would like to route this issue to ARM team. @Grayer123 Could you please help have look at this issue?

We are seeing the exact same problem with the exact same command, both for 2.34.1 and for 2.38.0. It sounds like this is being worked. If there are any work-arounds in the meantime, it would be really appreciated.

Since this issue may be an ARM service issue, so CLI doesn't have a good work-around. Maybe you can try to use az rest to request the REST API directly.
@ScottColdwellTR @vhhughes By the way, could you please send me the debug log (add --debug parameter) by email to facilitate our troubleshooting? My email address is<EMAIL_ADDRESS>thanks~

@zhoxing-ms I sent you the debug log via email. Thanks for looking into this so quickly!

I have found the root cause is due to the status code in the Python SDK is not handled correctly, the HttpResponseError error will be raised if the status code is not 200. But in fact, 201 and 202 should not throw errors
Python SDK code: code link
@Grayer123 Please update the Swagger, then let them contact Python SDK team @msyyc to release a new Python SDK version. After that, you can bump the new SDK version to fix this issue.

Not to detract from the original issue, but when I tried one of the workarounds:

Use the az resource update --set tags.key=value

It errored with
cli.azure.cli.core.azclierror: Error occurred in deserializing the response body.
az_command_data_logger: Error occurred in deserializing the response body.

I added the --debug flag, and saw that the response was XML, but it appears the code is applying a json decoder to it.

I added the --debug flag, and saw that the response was XML, but it appears the code is applying a json decoder to it.

@Grayer123 This is still a service issue. Could you help investigate this problem or know who is the right person to investigate it?

Hi, I am having the same issue when trying to update tags using both bash and powershell.
az tag update --resource-id _myresourceid_ --operation merge --tags test=1234

the tag will be added but I am getting the error which cause an issue in azure pipeline

@rthorn17 - Do you understand why tags might be returning an error for the "Accepted" status?


Frontend: add dropdown for custom webhook method and type

Description
add ui to select method (POST, PUT, PATCH) and type (HTTPS, HTTP) for custom webhook

Issues Resolved
[List any issues this PR will resolve]
Check List

[x] New functionality includes testing.

[x] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #348 (1749c73) into main (416b099) will increase coverage by 0.76%.
The diff coverage is 92.85%.

@@            Coverage Diff             @@
##             main     #348      +/-   ##
==========================================
+ Coverage   83.02%   83.78%   +0.76%
==========================================
  Files          66       66
  Lines        1867     1869       +2
  Branches      487      490       +3
==========================================
+ Hits         1550     1566      +16
+ Misses        310      296      -14
  Partials        7        7

Flag
Coverage Δ

dashboards-notifications
83.78% <92.85%> (+0.76%)
:arrow_up:

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

Impacted Files
Coverage Δ

...CreateChannel/components/CustomWebhookSettings.tsx
82.60% <ø> (ø)

dashboards-notifications/public/utils/constants.ts
100.00% <ø> (ø)

...tions/public/pages/CreateChannel/CreateChannel.tsx
88.23% <87.50%> (+3.49%)
:arrow_up:

...nnels/components/details/ChannelDetailsActions.tsx
89.28% <100.00%> (+17.85%)
:arrow_up:

...nels/components/details/ChannelSettingsDetails.tsx
84.78% <100.00%> (+0.69%)
:arrow_up:

...cations/public/pages/CreateChannel/utils/helper.ts
100.00% <100.00%> (ø)

...ions/public/pages/Emails/utils/validationHelper.ts
93.47% <0.00%> (+1.58%)
:arrow_up:

Continue to review full report at Codecov.

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


RefSeq missing MT transcripts

RefSeq GRCh37/GRCh38 joint historical do not have any contigs of "NC_012920.1"
There are 37 entries for contig NC_012920.1 in the latest GFF file:
zgrep NC_012920.1 GCF_000001405.40_GRCh38.p14_genomic.RS_2023_10.gff.gz | egrep "\sgene\s"
516000;Name=ND1;gbkey=Gene;gene=ND1;gene_biotype=protein_coding;gene_synonym=MTND1
NC_012920.1	RefSeq	gene	4263	4331	.	+	.	ID=gene-TRNI;Dbxref=GeneID:4565,HGNC:HGNC:7488,MIM:590045;Name=TRNI;gbkey=Gene;gene=TRNI;gene_biotype=tRNA;gene_synonym=MTTI
NC_012920.1	RefSeq	gene	4329	4400	.	-	.	ID=gene-TRNQ;Dbxref=GeneID:4572,HGNC:HGNC:7495,MIM:590030;Name=TRNQ;gbkey=Gene;gene=TRNQ;gene_biotype=tRNA;gene_synonym=MTTQ
NC_012920.1	RefSeq	gene	4470	5511	.	+	.	ID=gene-ND2;Dbxref=GeneID:4536,HGNC:HGNC:7456,MIM:516001;Name=ND2;gbkey=Gene;gene=ND2;gene_biotype=protein_coding;gene_synonym=MTND2

We must have been not reading these in correctly

From what I can tell, RefSeq do not provide MT transcripts
There are not NM_ records against NC_012920.1 and All of the proteins in MT have the "YP_" prefix - which means there is no associated NM_ transcript

@holtgrewe - I am not an expert on mitochondria - but apparently sometimes these genes are transcribed as large polycistronic units... and as it's different that's why there's no standard transcripts given
So, the "correct" thing to do would be to insert the genes, but w/o transcripts, but that's not very useful as we store start/end etc in transcripts
So perhaps we could insert transcripts with IDs like "fake-transcript-YP_XXX" that have start/end and coding start/end taken from the gene start/end - is that what you mean?

@davmlaw yes that's what I mean to make refseq symmetric to Ensembl

@holtgrewe - see https://github.com/SACGF/cdot/releases/tag/data_v0.2.26
import gzip
import json
filename = "/data/annotation/cdot/refseq/GRCh38/cdot-0.2.26.GCF_000001405.40_GRCh38.p14_genomic.RS_2023_10.gff.json.gz"
data = json.load(gzip.open(filename))
for t, td in data["transcripts"].items():
    contig = td["genome_builds"]["GRCh38"]["contig"]
    if contig == "NC_012920.1":
        print(t)

Output
fake-rna-ATP6
fake-rna-ATP8
fake-rna-COX1
fake-rna-COX2
fake-rna-COX3
fake-rna-CYTB
fake-rna-ND1
fake-rna-ND2
fake-rna-ND3
fake-rna-ND4
fake-rna-ND4L
fake-rna-ND5
fake-rna-ND6

In [10]: data["transcripts"]["fake-rna-COX3"]
Out[10]:
{'biotype': ['mRNA'],
 'gene_name': 'COX3',
 'gene_version': '4514',
 'genome_builds': {'GRCh38': {'cds_end': 9990,
   'cds_start': 9206,
   'contig': 'NC_012920.1',
   'exons': [[9206, 9990, 0, 1, 784, None]],
   'note': "TAA stop codon is completed by the addition of 3' A residues to the mRNA",
   'strand': '+',
   'url': 'https://ftp.ncbi.nlm.nih.gov/genomes/all/annotation_releases/9606/GCF_000001405.40-RS_2023_10/GCF_000001405.40_GRCh38.p14_genomic.gff.gz'}},
 'hgnc': '7422',
 'id': 'fake-rna-COX3',
 'protein': 'YP_003024032.1',
 'start_codon': 0,
 'stop_codon': 784}

Cc @tedil


Enable corepack in CI

In lieu of https://github.com/actions/setup-node/issues/531, enable this by hand.
I'm pretty sure this works.

The fact that we need a separate package manager to manage package managers is crazy; let's see how long until that space also gets fragmented and then we need a package manager manager manager...

The fact that we need a separate package manager to manage package managers is crazy; let's see how long until that space also gets fragmented and then we need a package manager manager manager...

volta, pacman, .... 😄

This insulates us from the version of npm provided by the version of node that's installed, instead using the version of npm declared in package.json. Really, this only matters for anything that intends to actually modify package.json or package-lock.json, so could be scoped down to just affect the update scripts, version bumpers, the release, etc, if desired, but if it were available on the setup-node action, I'd be enabling it everywhere.
Arguably, this should also be applied to the AzDo task we use to release TS to npm (non-nightly), as that's exactly what has broken us in the past; it using npm 6 which has different behavior that we use everywhere else.

I opted to remove all but the ones where it matters.


zdisk for /var

Thank you for this project! I see this as an excellent use to help reduce writes to SSDs and uSDs for longevity. The main use I have for this is for a zdisk mounted at /var as that is where many packages write persistent data to by default.
However, it seems that zdisk can't use a zdisk for /var because "zdisk stop saves the contents of /mnt/zdisk into a squashfs filesystem stored in /var/lib"
Shouldn't this dependency be removed so zdisk can be used for /var ? What about using /dev/shm ? And/or if too large to rebuild in ram, testing for a disk-based mount before re-building the squashfs?

Hi @reukiodo, the destination for the squashfs file can be changed, all variables are in the script head.
It can be changed so that the value of the variable can be overwritten with an external value. Eventually I make a change.
Managing all /var is not easy, there are many different directories, some of which are usually mounted on tmpfs.
This script was created to help reduce disk space usage for NodeJS projects, where the node_modules is heavy and many files are duplicated between projects.
If you want to reduce SSD usage I can suggest looking at log2ram and dir2ram. I use the first mainly with Raspberry, to reduce writes and speed up disk access, while the second is used by OpenMediaVault for a lot of directories.
log2ram keeps files in one zram device (for logs usually the compression ratio ranges from 2.5 to 3.0), while the second uses a simple tmpfs device.
See also zram-swap-config, which handles a swap on zram, may also be useful.


Azure Pipelines hosted agents have been updated to contain .Net Core 3.x (3.1) SDK/Runtime along with 2.1.

Hello, I am trying to make automatic deployments our portal is in .net core 2.2 but when I install it I get the following error

I have tried applying the global.json to apply that version but it has not worked either, the yml is this:
trigger:

dev

pool:
vmImage: 'windows-latest'
variables:
solution: '**/*.sln'
buildPlatform: 'Any CPU'
buildConfiguration: 'Release'
netversion: '2.2.402'
steps:

task: UseDotNet@2
displayName: 'Use .Net Core sdk 2.2.402'
inputs:
version: $(netversion)
includePreviewVersions: true

task: UseDotNet@2
inputs:
packageType: 'sdk'
useGlobalJson: true

task: DotNetCoreCLI@2
inputs:
command: restore
projects: '**/*.csproj'

task: NuGetToolInstaller@1

task: NuGetCommand@2
inputs:
restoreSolution: '$(solution)'

task: VSBuild@1
inputs:
solution: '$(solution)'
msbuildArgs: '/p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:PackageLocation="$(build.artifactStagingDirectory)"'
platform: '$(buildPlatform)'
configuration: '$(buildConfiguration)'

task: PublishSymbols@2
displayName: 'Publish symbols path'
inputs:
SearchPattern: '**\bin***.pdb'
PublishSymbols: false
continueOnError: true

task: PublishBuildArtifacts@1
displayName: 'Publish Artifact'
inputs:
PathtoPublish: '$(build.artifactstagingdirectory)'
ArtifactName: 'artefacto'
condition: succeededOrFailed()

Hi @algarciatech I'm closing it due to inactivity at the moment - please let us know if it still actual for you.


Great icons! Would love to see HTML and CSS added

that's the request @Crawron :)
These really are my favorite icons for VSCode ever though

Thanks! I've just added icons for HTML and CSS, they'll release on the next version.


Is there any requirement for the input video?

I run the api_example/demo.py using cgdetr on a video of  length 104s and it report the bug as
Traceback (most recent call last):
  File "/home/桌面/video_highlight/lighthouse/api_example/demo.py", line 29, in <module>
    model.encode_video('/home/liaowenjie/桌面/video_highlight/video/video1_part_1.mp4')
  File "/home/anaconda3/envs/lighthouse/lib/python3.9/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/anaconda3/envs/lighthouse/lib/python3.9/site-packages/lighthouse/models.py", line 86, in encode_video
    video_feats = self.feature_extractor.encode_video(video_path)
  File "/home/anaconda3/envs/lighthouse/lib/python3.9/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/anaconda3/envs/lighthouse/lib/python3.9/site-packages/lighthouse/feature_extractor.py", line 192, in encode_video
    slowfast_frames = self.sf_loader.read_video_from_file(video_path)
  File "/home/anaconda3/envs/lighthouse/lib/python3.9/site-packages/lighthouse/video_loader.py", line 223, in read_video_from_file
    video = self.preprocess(video, info)
  File "/home/anaconda3/envs/lighthouse/lib/python3.9/site-packages/lighthouse/slowfast_preprocess.py", line 183, in __call__
    tensor = self._pad_clips(tensor, self.padding_mode)
  File "/home/anaconda3/envs/lighthouse/lib/python3.9/site-packages/lighthouse/slowfast_preprocess.py", line 174, in _pad_clips
    z = th.cat(n * [tensor[-1:, :, :, :, :]])

And I test on the other video of length 150s, it succeed but it gives a negative pred_relevant_window [-0.1586, 5.4191, 0.9571].
I notice the original code have the limitation that the video length should be under 150s. So is this the problem of the video or the problem of the cgdetr?

Thank you for your test.

I run the api_example/demo.py using cgdetr on a video of length 104s and it report the bug as

This is a bug. I will fix this.

And I test on the other video of length 150s, it succeed but it gives a negative pred_relevant_window [-0.1586, 5.4191, 0.9571].

You need to clip max(0, start) / min(video_length, end). This is post-processing, but is not implemented now.

I notice the original code have the limitation that the video length should be under 150s. So is this the problem of the video or the problem of the cgdetr?

The max video length is 150s due to the QVHighlights limitation.

@whycantfindaname I reproduced the error. But please wait for 1 week due to the conference deadline. Thanks.

@whycantfindaname I reproduced the error. But please wait for 1 week due to the conference deadline. Thanks.

It's ok. Thanks for your contribution!

@whycantfindaname Hi, I fixed the issue. Could you try it again? If you have any problems, please re-open the issue.


Create 0000-01-02-vibrio81.md

layout: slide
title: "Welcome to our second slide."
Your text
Use the left arrow to go back.

WTF

please change number 5

l


ValueError: Dimensions must be equal

Got problem when training my own data. How to solve this problem?
2019-06-11 13:34:26.884751: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1103] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 10416 MB memory) -> physical GPU (device: 0, name: GeForce GTX 1080 Ti, pci bus id: 0000:01:00.0, compute capability: 6.1)
Using TensorFlow backend.
/home/universe/miniconda3/lib/python3.6/site-packages/keras/engine/saving.py:1140: UserWarning: Skipping loading of weights for layer conv2d_59 due to mismatch in shape ((1, 1, 1024, 28) vs (255, 1024, 1, 1)).
  weight_values[i].shape))
/home/universe/miniconda3/lib/python3.6/site-packages/keras/engine/saving.py:1140: UserWarning: Skipping loading of weights for layer conv2d_59 due to mismatch in shape ((28,) vs (255,)).
  weight_values[i].shape))
/home/universe/miniconda3/lib/python3.6/site-packages/keras/engine/saving.py:1140: UserWarning: Skipping loading of weights for layer conv2d_67 due to mismatch in shape ((1, 1, 512, 28) vs (255, 512, 1, 1)).
  weight_values[i].shape))
/home/universe/miniconda3/lib/python3.6/site-packages/keras/engine/saving.py:1140: UserWarning: Skipping loading of weights for layer conv2d_67 due to mismatch in shape ((28,) vs (255,)).
  weight_values[i].shape))
/home/universe/miniconda3/lib/python3.6/site-packages/keras/engine/saving.py:1140: UserWarning: Skipping loading of weights for layer conv2d_75 due to mismatch in shape ((1, 1, 256, 28) vs (255, 256, 1, 1)).
  weight_values[i].shape))
/home/universe/miniconda3/lib/python3.6/site-packages/keras/engine/saving.py:1140: UserWarning: Skipping loading of weights for layer conv2d_75 due to mismatch in shape ((28,) vs (255,)).
  weight_values[i].shape))
Create YOLOv3 model with 12 anchors and 2 classes.
Load weights model_data/yolo_weights.h5.
Freeze the first 249 layers of total 252 layers.
Traceback (most recent call last):
  File "/home/universe/miniconda3/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1626, in _create_c_op
    c_op = c_api.TF_FinishOperation(op_desc)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Dimensions must be equal, but are 4 and 3 for 'yolo_loss/truediv_2' (op: 'RealDiv') with input shapes: [?,26,26,4,2], [3,2].

seems to be caused by the anchor file. Use author default anchor file will solve this problem


Implement reading of adaptive scripts

Currently a bit blocked because I know too little about adaptive scripts and the docs are cough not very telling.


Formatted source code using Apache Commons standards.

Using the Eclipse formatter provided in the previous PR.

Although this a good step to standardisation I wondered if there is a way to achieve the same in a maven plugin so that those not using eclipse can be compliant?
A quick check found this formatter-maven-plugin which is built on top of the eclipse formatter. Could you have a look and see if it works when added to the pom for the code in this PR. I.e. you should be able to run mvn formatter:format and it should not change any of your files that you formatted in eclipse.
If it works then the formatter:validate goal could be added to the goals run by the CI server (in a future PR) to make sure new code has not forgotten to run the formatting.

@aherbert Let me try that and I will report back.

@aherbert it worked like a charm.  In fact it picked up directories I missed because I assumed Eclipse recursed directories when it formatted but it did not.  but the Plugin does and picks up the whole source tree.

I think that the eclipse formatter will recurse the directory if you start at a resource folder (e.g. src/main/java). But if you start at a package in the directory tree below the top level (e.g. org.apache.commons.beautils2) then it only processes those java files in the current package.
Have you looked at how the formatter treated comments. I see that you have configured it to allow formatting in javadoc comments. In my experience this is not good for compact lists:
  /**
   * Test method.
   *
   *

   *
This
   *
list
   *

   */

Becomes:
  /**
   * Test method.
   *
   *

This
list

   */

The javadoc will still render the same but anyone reading the source file will struggle.
So I would recommend you have a scan through the code for
 elements and check them.
You can solve this by adding spaces:
  /**
   * Test method.
   *
   *

   *
   *
This
   *
   *
list
   *
   *

   */

becomes:
  /**
   * Test method.
   *
   *

   *
   *
This
   *
   *
list
   *
   *

   */

Basically just stripping leading whitespace.
Also check what it has done in
 blocks. You can protect them to some extent using
{@code but then the code cannot contain } which is hard to avoid if documenting loops and other block statements.

I tested
 /**
     * Test method.
     *
     *

     *
This
     *
list
     *

     */

became this...
    /**
     * Test method.
     *

     *
This
     *
list
     *

     */

Closing this PR.  Will create a new one


fix(country/ioc) add missing ioc for South Sudan

add missing ioc for South Sudan
https://en.wikipedia.org/wiki/South_Sudan_at_the_Olympics

Thanks for the input. I didn't use your pull request as the actual change should have been made in countries.csv which the JSON is generated from. But much appreciated all the same!
Code now on NPM as v0.0.28


Reactor Redstone Port Fuel Level too small.

The Reactor Redstone Port when set to Output:Fuel Amount, only allows 7 digits to be input.  My current reactor holds 38080000mB, which is 8 digits.... any chance we can get the port's digits increased to 8 or more?
I would like to set a port to generate redstone signal if my reactor ever drops below ~38060000mB to signal my fuel storage to deliver more fuel to the input port.  Ive got a reprocessor working full time, i just want to be able to add yellorium only when necessary and burn the blutonium as its made.
Please let me know.  Thanks.

An easy workaround I found that will do the same thing is to have two fuel imupts.
Bluetonium ingots in one
And yellorium blocks in the other
It will pull the ingots befor the blocks.

Interesting.  I just fed 2 ports to see which one ate the fuel first.  Hooked the blutonium feed to that one and rednet controlled yellorium feeder to the other.  In the end it works for what I wanted to do, but i still think the redstone port value being too small to address reactor capacity is a problem that should be addressed when time allows.
Thanks for the idea though, its a good one.
Date: Tue, 4 Aug 2015 23:44:50 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS>Subject: Re: [BigReactors] Reactor Redstone Port Fuel Level too small. (#521)
An easy workaround I found that will do the same thing is to have two fuel imupts.
Bluetonium ingots in one
And yellorium blocks in the other
It will pull the ingots befor the blocks.
—
Reply to this email directly or view it on GitHub.


magento-cloud activity -p  -e  command does not work

Issue in ./help/troubleshooting/miscellaneous/checking-deployment-log-if-the-cloud-ui-shows-log-snipped-error.md
Hi,
I think there is an error in this very first command in Solution section:
magento-cloud activity -p <project id> -e <environment>

When I am trying to run it, I got an error:
$ magento-cloud activity -p 7yvbzwvtkgerq -e production

  [CommandNotFoundException]
  Command "activity" is not defined.
  Did you mean one of these?
      activity:cancel
      activity:get
      activity:list
      activity:log
      integration:activity:get
      integration:activity:list
      integration:activity:log

Looks like the correct syntax should be activity:list, not activity :
magento-cloud activity:list -p 7yvbzwvtkgerq -e production

as this gives me the expected results.
Let me know if you need any additional information regarding this issue.
Regards,
Rafal Janicki

Hi @bl4de Thank you for this suggested change. I have created a Jira for this work which will be assigned on intake. Please note that this PR may need to be copied internally before it can be worked.


Constraint on part of a variable

Thanks for the great package!
I wonder if it's possible to express the following constraint with cvxpy?

I've tried something like this
# n = 20
# x = Variable(n)
constraints = [0 <= x, x <= 1]
for t in range(1, n + 1):
	xSum = 0
	for i in range(1, t + 1):
		xSum += x[i - 1]
	c = 0 <= a * exp(xSum) + xSum - t
	constraints.append(c)

but got the not following DCP rules error:

cvxpy.error.DCPError: Problem does not follow DCP rules.

It's not a convex constraint. You can try DCCP: https://github.com/cvxgrp/dccp


Communication Mechanism Work Item 6 Release lock api

Description
Release Lock API
Issues Resolved
https://github.com/opensearch-project/opensearch-sdk-java/issues/370
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #312 (b40fccb) into main (23c70b9) will increase coverage by 0.17%.
The diff coverage is 16.57%.

:exclamation: Current head b40fccb differs from pull request most recent head 65ed8e3. Consider uploading reports for the commit 65ed8e3 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main     #312      +/-   ##
============================================
+ Coverage     31.17%   31.35%   +0.17%
- Complexity       66       98      +32
============================================
  Files            12       22      +10
  Lines           773     1110     +337
  Branches         80       98      +18
============================================
+ Hits            241      348     +107
- Misses          513      736     +223
- Partials         19       26       +7

Impacted Files
Coverage Δ

...rg/opensearch/jobscheduler/JobSchedulerPlugin.java
31.66% <0.00%> (-1.10%)
:arrow_down:

...arch/jobscheduler/model/ExtensionJobParameter.java
0.00% <0.00%> (ø)

...obscheduler/rest/request/GetJobDetailsRequest.java
45.16% <ø> (ø)

...r/transport/request/ExtensionJobActionRequest.java
0.00% <0.00%> (ø)

...heduler/transport/request/JobParameterRequest.java
0.00% <0.00%> (ø)

...bscheduler/transport/request/JobRunnerRequest.java
0.00% <0.00%> (ø)

...transport/response/ExtensionJobActionResponse.java
0.00% <0.00%> (ø)

...duler/transport/response/JobParameterResponse.java
0.00% <0.00%> (ø)

...cheduler/transport/response/JobRunnerResponse.java
0.00% <0.00%> (ø)

...ensearch/jobscheduler/utils/JobDetailsService.java
2.52% <0.00%> (-1.16%)
:arrow_down:

... and 7 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Just a premise, This PR has below changes

Reorganizing request files in request package and response files in response package
Release Lock API
Removing _get from RestGetJobDetailsAction api route as the api is already a GET api so it is not needed to be in path

@joshpalis @dbwiddis @saratvemulapalli


Fix list pagination on search

I want to merge this change because... it:

fixes crash on search when cursor is improperly set to non-search results
fixes improper pagination on list pages

PR intended to be tested with API branch:
Screenshots

Pull Request Checklist

[ ] This code contains UI changes
[ ] All visible strings are translated with proper context including data-formatting
[ ] Attributes [data-test-id] are added for new elements
[ ] Changes are mentioned in the changelog
[ ] The changes are tested in different browsers and in light/dark mode

Test environment config

API_URI=https://qa.staging.saleor.cloud/graphql/

Task linked: SALEOR-3727 Search crashes when cursor doesn't exist


FB: Scrape various text fields

I took this to mean "message" (above the photo) and "description" (below photo/link)