Generating inputs to Oscar model

Hi Oscar Team,
Thanks for the interesting paper and open-sourcing your model.
On your download page, you mention that images are fed into Oscar through the outputs of a "Faster R-CNN with ResNet-101, using object and attribute annotations from Visual Genome". Have you made this model available too? It would be great if you could give a link to this pre-trained model, as it is necessary to run Oscar on my own images (I'm interested in image captioning and VQA).
I have tried to look for it myself, and the closest thing I could find was the R101-FPN from the Detectron2 model zoo (PyTorch model). However, this was trained on the COCO dataset of object tags, and I understand that the Visual Genome has significantly more labels. So surely this one would fail to produce the image features that Oscar expects?
I'd be grateful if you could let me know if my thinking is correct and if there is a link to the appropriate PyTorch model for generating inputs that Oscar can use.
Thanks in advance!

I used this codebase and pre-trained models, https://github.com/peteanderson80/bottom-up-attention, it is pre-trained on VG with 1600 tags.

@xjli Thanks for this! I did however have quite a lot of issues getting this model to run with Caffe. Just as an example, the model will not load when using the standard Caffe Docker image.
Do you know of an openly available Docker image where I can run the bottom-up attention model?

I personally use this one: https://github.com/airsplay/py-bottom-up-attention

I personally use this one: https://github.com/airsplay/py-bottom-up-attention

@vincentlux I am planning to use the repo that you have mentioned above - https://github.com/airsplay/py-bottom-up-attention, to generate features another dataset I have been working on. I was wondering if you could get similar performance to what is stated in Oscar paper using the features generated by airsplay's bottom-up-attention repo?

@vincentlux I am planning to use the repo that you have mentioned above - https://github.com/airsplay/py-bottom-up-attention, to generate features another dataset I have been working on. I was wondering if you could get similar performance to what is stated in Oscar paper using the features generated by airsplay's bottom-up-attention repo?

I tested on the retrieval task and the performance is ~2 points lower, did you test? Not sure if it is because the location feature processing is different or the visual feature is different. Would be great if @xjli can provide more information on the feature extraction stage.

I tested on the retrieval task and the performance is ~2 points lower, did you test? Not sure if it is because the location feature processing is different or the visual feature is different. Would be great if @xjli can provide more information on the feature extraction stage.

I tested on the retrieval task and the performance is ~2 points lower, did you test? Not sure if it is because the location feature processing is different or the visual feature is different. Would be great if @xjli can provide more information on the feature extraction stage.

I personally use this one: https://github.com/airsplay/py-bottom-up-attention

Can I know how did you get the label.tsv from the code??

@vincentlux I am planning to use the repo that you have mentioned above - https://github.com/airsplay/py-bottom-up-attention, to generate features another dataset I have been working on. I was wondering if you could get similar performance to what is stated in Oscar paper using the features generated by airsplay's bottom-up-attention repo?

Did you trained with your own dataset? I am trying to do the same. I managed to get captions for my own images using the features of Bottom-Up-Attention, but OSCAR fails to train with the features of a newly entire dataset. So: inference works, but training does not.
The class ExceptionWrapper is re-raising the original error, but fails to do so, so the original error is hidden to me. The message is: __init__() missing 2 required positional arguments: 'doc' and 'pos' debug, which seems to be caused by a malformed JSON.

@brightsit I also try to use https://github.com/airsplay/py-bottom-up-attention.
to generate the feature.tsv, I use the detectron2_mscoco_proposal_maxnms.py, but make little modification.
to generate the label.tsv, I use the demo_feature_extraction.ipynb from the same folder(instance variabel is the label we want),also need some modification.
the value generated is the value we want, but the format is different, need additional step to match the format with coco_dataset.
i try to do inference using my own dataset, but no luck i'm getting __init__() missing 2 required positional arguments: 'doc' and 'pos' debug :"(
maybe if i'm success i will post the code in here

Yeah I would also appreciate some example code for how to run inference / predict captions

For me, __init__() missing 2 required positional arguments: 'doc' and 'pos' debug was caused by an issue loading the feature tsv file.  airsplay/py-bottom-up-attention formats the tsv file with single quotes, but json requires double quotes. This hacky fix in the CaptionTensorizer class fixed things:
def get_image_features(self, img_idx):
    # Updated to format json appropriately
    dict_str = self.feat_tsv.seek(img_idx)[1]
    dict_str = dict_str.replace('"', '"""')
    dict_str = dict_str.replace("'", '"')
    feat_info = json.loads(dict_str)
    num_boxes = feat_info['num_boxes']
    features = np.frombuffer(base64.b64decode(feat_info['features']), np.float32
            ).reshape((num_boxes, -1))
    return torch.Tensor(features)

After this, there is one more step to making inference work on a new dataset. Bottom-Up Attention generates features of size 2048, but Oscar expects 2054. The difference comes from concatenating information about the bounding boxes' positions (Ref: last paragraph on pg. 4 of the original research paper).
Luckily, that is explained with working code here: https://github.com/microsoft/Oscar/issues/33#issuecomment-702864446.

@anbrjohn Thank you very much! That helps a lot

For me, __init__() missing 2 required positional arguments: 'doc' and 'pos' debug was caused by an issue loading the feature tsv file. airsplay/py-bottom-up-attention formats the tsv file with single quotes, but json requires double quotes. This hacky fix in the CaptionTensorizer class fixed things:
def get_image_features(self, img_idx):
    # Updated to format json appropriately
    dict_str = self.feat_tsv.seek(img_idx)[1]
    dict_str = dict_str.replace('"', '"""')
    dict_str = dict_str.replace("'", '"')
    feat_info = json.loads(dict_str)
    num_boxes = feat_info['num_boxes']
    features = np.frombuffer(base64.b64decode(feat_info['features']), np.float32
            ).reshape((num_boxes, -1))
    return torch.Tensor(features)

After this, there is one more step to making inference work on a new dataset. Bottom-Up Attention generates features of size 2048, but Oscar expects 2054. The difference comes from concatenating information about the bounding boxes' positions (Ref: last paragraph on pg. 4 of the original research paper).
Luckily, that is explained with working code here: #33 (comment).

If you don't want to touch the run_captioning.py code, you could convert the single-quotes into double-quotes by running a script like below after generating the tsv files
LABEL_FILE = "./custom.label.tsv"
FEATURE_FILE = "./custom.feature.tsv"

def quote_conversion(path):
    with open(path, 'r') as f:
        text = f.read()

    converted_text = text.replace("'", '"')

    with open(path, 'w') as f:
        f.write(converted_text)

quote_conversion(LABEL_FILE)
quote_conversion(FEATURE_FILE)

我个人使用这个：https://github.com/airsplay/py-bottom-up-attention

Hello, I have been researching how to generate the OSCAR and VINVL input data for captioning inference recently, but I am a bit confused. Can you provide me with some assistance?


Write tests for language change checks

I don't have time to support the application, so the edits are unfortunately not relevant.


Your Docker Setup for Boulder

Good day, just wish to get your insight in how you setup your boulder running on docker. I had boulder running with docker, even after exposing the ports 5001 and 5002 on docker, i still see connection refused when boulder tries to run it's validation.
See below
dns-srv: Query -- [mydomain.com.] A
dns-srv: Query -- [mydomain.com.] AAAA
dns-srv: Query -- [mydomain.com.] CAA

I094851 boulder-va HTTP request to http://mydomain.com:5002/.well-known/acme-challenge/qfst_k1H8Fbaqs2BO37IZHtY3xQGzw_YqwP3TASt7Xo failed. err=[&url.Error{Op:"Get", URL:"http://mydomain.com:5002/.well-known/acme-challenge/qfst_k1H8Fbaqs2BO37IZHtY3xQGzw_YqwP3TASt7Xo", Err:(*net.OpError)(0xc4201c9b30)}] errStr=[Get http://mydomain.com:5002/.well-known/acme-challenge/qfst_k1H8Fbaqs2BO37IZHtY3xQGzw_YqwP3TASt7Xo: dial tcp <IP_ADDRESS>:5002: connect: connection refused]
I094851 boulder-va HTTP request to http://mydomain.com:5002/.well-known/acme-challenge/qfst_k1H8Fbaqs2BO37IZHtY3xQGzw_YqwP3TASt7Xo failed. err=[&url.Error{Op:"Get", URL:"http://mydomain.com:5002/.well-known/acme-challenge/qfst_k1H8Fbaqs2BO37IZHtY3xQGzw_YqwP3TASt7Xo", Err:(*net.OpError)(0xc4201c9b30)}] errStr=[Get http://mydomain.com:5002/.well-known/acme-challenge/qfst_k1H8Fbaqs2BO37IZHtY3xQGzw_YqwP3TASt7Xo: dial tcp <IP_ADDRESS>:5002: connect: connection refused]
I094851 boulder-va [AUDIT] Validation result JSON={"ID":"hyovGELAKgj21WbWHyaDSb8Dmn9avHcidg5gaPcVBhc","Requester":2,"Hostname":"mydomain.com","ValidationRecords":[{"url":"http://mydomain.com:5002/.well-known/acme-challenge/qfst_k1H8Fbaqs2BO37IZHtY3xQGzw_YqwP3TASt7Xo","hostname":"mydomain.com","port":"5002","addressesResolved":["<IP_ADDRESS>"],"addressUsed":"<IP_ADDRESS>"}],"Challenge":{"id":17,"type":"http-01","status":"invalid","error":{"type":"connection","detail":"Fetching http://mydomain.com:5002/.well-known/acme-challenge/qfst_k1H8Fbaqs2BO37IZHtY3xQGzw_YqwP3TASt7Xo: Connection refused","status":400},"token":"qfst_k1H8Fbaqs2BO37IZHtY3xQGzw_YqwP3TASt7Xo","keyAuthorization":"qfst_k1H8Fbaqs2BO37IZHtY3xQGzw_YqwP3TASt7Xo.-rNg0ollukXW1vPZLS3AE9YNaf91w9NaxLPgChhekcY","validationRecord":[{"url":"http://mydomain.com:5002/.well-known/acme-challenge/qfst_k1H8Fbaqs2BO37IZHtY3xQGzw_YqwP3TASt7Xo","hostname":"mydomain.com","port":"5002","addressesResolved":["<IP_ADDRESS>"],"addressUsed":"<IP_ADDRESS>"}]},"RequestTime":"2018-03-12T09:48:51.756965943Z","ResponseTime":"0001-01-01T00:00:00Z","Error":"connection :: Fetching http://mydomain.com:5002/.well-known/acme-challenge/qfst_k1H8Fbaqs2BO37IZHtY3xQGzw_YqwP3TASt7Xo: Connection refused"}
I094851 boulder-va Validations: {ID:hyovGELAKgj21WbWHyaDSb8Dmn9avHcidg5gaPcVBhc Identifier:{Type: Value:} RegistrationID:2 Status: Expires:<nil> Challenges:[] Combinations:[] Wildcard:false}
I094852 boulder-wfe JSON={"Endpoint":"/acme/challenge/hyovGELAKgj21WbWHyaDSb8Dmn9avHcidg5gaPcVBhc/17","Method":"GET","UserAgent":"Go-http-client/1.1 (darwin; amd64) xenolf-acme","Code":202,"Extra":{"AuthorizationStatus":"invalid","ChallengeType":"http-01","Identifier":{"type":"dns","value":"mydomain.com"}}}
I094852 boulder-wfe JSON={"Endpoint":"/acme/authz/hyovGELAKgj21WbWHyaDSb8Dmn9avHcidg5gaPcVBhc","Method":"POST","Errors":["400 :: malformed :: Error deactivating authorization :: only valid and pending authorizations can be deactivated","\u0026errors.BoulderError{Type:2, Detail:\"only valid and pending authorizations can be deactivated\"}"],"Requester":2,"Contacts":["mailto:yours@yours.com"],"UserAgent":"Go-http-client/1.1 (darwin; amd64) xenolf-acme","Code":400,"Payload":"{\"resource\":\"authz\",\"Status\":\"deactivated\"}","Extra":{"AuthorizationStatus":"invalid","Identifier":{"type":"dns","value":"mydomain.com"}}}

I wonder if i need to do more setup on the host or the container apart from exposing the ports to both the container and host?
Would appreciate your directions and thoughts.
This is how i run my setup: https://github.com/wirekit/tlsfs/blob/master/makefile#L5

Since this issue came up when I tried to find what I was doing wrong, this might be helpful for anyone using xenolf/lego with docker-compose, but I'm not sure if it's the same problem as yours:
My plan was to define a general lego service in docker-compose.yml and then use "docker-compose run" to execute the required commands. The letsencrypt validation always failed though, because the connection (from letsencrypt to the HTTP server started by lego) was refused, just like in this issue report.
It took me a while to figure out that the port mappings declared in docker-compose.yml are not used for commands started through "docker-compose run" because these are considered to be one-off commands. The ports are only mapped for services defined in the .yml file that are started through "docker-compose up" (and similar commands). So I defined a lego-renew service that has a "command: --email bleh --domain blah renew --days 60" line and now "docker-compose up lego-renew" works fine.

@w-flo Would be great to a sample if possible.

Thanks very much
Best Regards,
Alex A. Ewetumo.
Software Engineer
https://github.com/influx6<EMAIL_ADDRESS>Skype: trinoxf, Tel:
+2349053058679)
On Fri, Jun 22, 2018 at 12:37 PM, w-flo<EMAIL_ADDRESS>wrote:

Sure, this is my yml file:
version: '3.4'
services:
lego-obtain:
image: xenolf/lego:latest
command: --accept-tos<EMAIL_ADDRESS>--domains="my.example.domain" --path="/certs" run
volumes:
- cert_store:/certs
ports:
- "80:80"
restart: 'no'
lego-renew:
image: xenolf/lego:latest
command<EMAIL_ADDRESS>--domains="my.example.domain" --path="/certs" renew --days 60
volumes:
- cert_store:/certs
ports:
- "80:80"
restart: 'no'
volumes:
cert_store:
name: cert_store
I actually have the lego-obtain service commented out because you only
need this for the initial certificate request and I don't want to risk to
start it by accident.
It stores the certificate in a named volume "cert_store", which is also
used in other containers that need the certificate. (It's a
one-machine-setup that offers multiple services, only 2 or 3 users.)
I have a systemd service that is started (using a systemd timer unit)
daily at a random time and this is the service definition:
Type=oneshot
WorkingDirectory=/path/to/directory/where/lego/yml/file/is/stored/
ExecStart=/usr/bin/docker-compose up lego-renew
I'm not 100% sure the systemd service&timer actually work, but my manual
attempts two weeks ago looked promising. The thing that is still missing:
trigger a bunch of "docker-compose restart" commands for the 4 different
docker services that use the certificate. It's not really important though
since I reboot that box ~weekly, and the new cert should get picked up
after reboot.
Also, regularly doing "docker-compose pull" in the lego yml file directory
is probably a good idea to get lego updates.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/xenolf/lego/issues/499#issuecomment-399413409, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAICLYZ5Bq2bsr3UQAOnm9bgO3QR9_SEks5t_Nb6gaJpZM4So14h
.


Use readonly array for input options

When using op: readonly Options[] = [/* ... */] as an input for ng-select, the type checker complains.
readonly T[] states that it is an array of T where no elements can be added or removed from the array.
Without this change, the library user cannot use a readonly array as input value.

Thanks for your contribution @nikeee . I am not sure if I correctly understand your issue. I tried to reproduce this be using the following readonly array as input for the ng-select component:
import { Component } from '@angular/core';
import {IOption} from 'ng-select';

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.css']
})
export class AppComponent {
    testOptions: readonly IOption[] = [
        {label: 'Belgium', value: 'BE'},
        {label: 'Luxembourg', value: 'LU'},
        {label: 'Netherlands', value: 'NL'}
    ]
}

<ng-select [options]="testOptions"></ng-select>

and that works fine for me. Did I misunderstand something?

The error occurs when doing a production build with fullTemplateTypeCheck enabled.

I created a new project with angular cli:
ng new simpleNgSelect

This project by default has fullTemplateTypeCheck set to true in tsconfig.json. I installed ng-select with:
npm install --save ng-select

and added the code from my previous comment to the app component. Running a production build with:
ng build --aot

and with
ng build --prod

works fine for me, without any errors.

You are right.
I had this error when compiling:
Argument of type 'readonly IOption[]' is not assignable to parameter of type 'IOption[]'.
  The type 'readonly IOption[]' is 'readonly' and cannot be assigned to the mutable type 'IOption[]'

This lead me to beleave that there is a problem with the type of this library. However, there was some filter that was missing the readonly modifier.
Is there a reason not to merge this PR anyway? I mean, now the public API states that the passed array will not be mutated.

Is there a reason not to merge this PR anyway? I mean, now the public API states that the passed array will not be mutated.

You have a point there, and I am still considering merging it. But if I want to add it to the next minor release, I need to check if it is not a breaking change. It could be a breaking change if compilation fails for those users who currently provide a list of options that is not readonly.
To be honest, I have not worked with angular for some time already, so I have to read up on the subject to get up to date with the latest developments.


chore: remove JsonThrowOnErrorRector and FinalizePublicClassConstantRector from skip() config

as no longer part of sets

Description
Explain what you have changed, and why.
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

Ready to merge 👍

Thank you @michalsn for the review, let's merge 👍


remove english strings in .mo files

I don't think we need to copy this file across with the english strings - it should fall back on english for strings that aren't found for any given language.
Originally posted by @jacalata in https://github.com/tableau/tabcmd/pull/105#discussion_r880096423

I am not sure but this change might be causing the En Local language translation error in the latest build which i mentioned ?


x/tools/gopls: set types.Config.GoVersion based on go.mod

In Go 1.18, the GoVersion was added to go/types.Config (proposal: #46648). This field configures the Go language version, as would be passed to the compiler via -lang, and read by the Go tool from the go directive in the go.mod.
This means that gopls can now match compiler type-checking errors exactly, by setting Config.GoVersion based on the applicable go.mod file. We should do this for 1.18, as it will be common for users to write generic code with gopls, only to be surprised when they get errors from the go command due to their go.mod file.
This is also a critical component of using gopls built with a recent version of Go to target building at an older Go version.

CC @hyangah @heschi
Hana was (quite wisely) concerned about users bumping up against version skew pain with 1.18. This is one part fixing that.


Feature/lc 167

I added the solution for LC-167 https://leetcode.com/problems/two-sum-ii-input-array-is-sorted/

Deciding to close because I'm not sure if this is maintained


fixed date string format

fixes #1569

hello @lrosenth , I originally stole this code from you (I guess) and you might be interested.
Now, is it the best way to do it in the salsah1.5 case?
Right now we take the ARK and we append the current date:
    "knora-api:arkUrl" : {
      "@type" : "xsd:anyURI",
      "@value" : "http://<IP_ADDRESS>:3336/ark:/72163/1/0001/55UrkgTKR2SEQgnsLWI9mgR/c8zmKe=eRjWMOGIOw=5GyAh"
    },

An alternative would be to get the versioned  ARK straight from the API and get the last changed version, not an ever renewed ARK without concern of the resource being the same for years:
    "knora-api:versionArkUrl" : {
      "@type" : "xsd:anyURI",
      "@value" : "http://<IP_ADDRESS>:3336/ark:/72163/1/0001/55UrkgTKR2SEQgnsLWI9mgR/c8zmKe=eRjWMOGIOw=5GyAh.20191129T100000673298Z"
    }

wouldn't it be better?

right now, the ARK dereferences to knora-app which displays the resource at the requested version. The version is a time-stamp which is not forwarded in the exploration of the data graph (by clicking on a linked resource).
So if we ask for a resource with the last change date or the now timestamp, we get the same resource. And we also get the same result when clicking on a link of that resource.
Conclusion: let's grab the last resource.

Thanks @lrosenth :)


[QAE1057] PDF generators for Audit Certificates

Done with generation of PDF Audit Certificates for:

Innovation Award
International Trade Award
Sustainable Development Award

looks good :+1:


Use Python 3.13 as the base image

We may as well use Python 3.13 as the base image - as we're using Docker, we may as well just use the latest version.
https://github.com/piccolo-orm/piccolo-admin-docker/blob/376f0ac0fd230036acd5e931703a275c1e774a71/Dockerfile#L1
Eventually we might want to publish multiple image versions, but for now, lets just use the latest Python version.

@dantownsend I can add that if you want.

@sinisaos Cool, thanks!


Simplify the process of preparing metadata components

This is done by passing by the metadata source directory, without compressing the given directory. Checksum varies each time a new archive is generated thus failed the duplicate check.
Fixes OLCS-267

Will merge today.


make Watching.close callback optional

https://github.com/webpack/webpack/issues/769#issuecomment-73615872

Thanks


jql: 7.0.3 -> 7.0.4

Diff: https://github.com/yamafaktory/jql/compare/jql-v7.0.3...jql-v7.0.4
Changelog: https://github.com/yamafaktory/jql/releases/tag/jql-v7.0.4
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 258594 run on x86_64-linux 1

1 package built:

jql


vue3 example/tooling broken for me

Hi, I'm very new to single-spa-vue, but I think I've maybe spotted an issue with the vue3 example and the create-single-spa tooling.
On https://single-spa.js.org/docs/ecosystem-vue/, it says this:
[....]
const vueLifecycles = singleSpaVue({
  createApp,
  appOptions: {
    render() {
      return h(App, {
        // single-spa props are available on the "this" object. Forward them to your component as needed.
        // https://single-spa.js.org/docs/building-applications#lifecyle-props
        name: this.name,
        mountParcel: this.mountParcel,
        singleSpa: this.singleSpa,
      });
    },
  },
  handleInstance: (app) => {
    app.use(router);
  }
});
[...]

However, if I do that, I get the following failure when it tries to mount the component:
app-errors.js:12 Uncaught TypeError: application '@tvsquared/tvs-spapoc-nav' died in status SKIP_BECAUSE_BROKEN: Cannot convert object to primitive value
    at patchAttr (runtime-dom.esm-bundler.js?830f:168)
    at patchProp (runtime-dom.esm-bundler.js?830f:354)
    at mountElement (runtime-core.esm-bundler.js?5c40:3826)
    at processElement (runtime-core.esm-bundler.js?5c40:3789)
    at patch (runtime-core.esm-bundler.js?5c40:3709)
    at componentEffect (runtime-core.esm-bundler.js?5c40:4211)
    at reactiveEffect (reactivity.esm-bundler.js?a1e9:42)
    at effect (reactivity.esm-bundler.js?a1e9:17)
    at setupRenderEffect (runtime-core.esm-bundler.js?5c40:4176)
    at mountComponent (runtime-core.esm-bundler.js?5c40:4134)

Digging in shows that patchAttr is trying to set the values name, mountParcel, and singleSpa on the DOM element, which it can't do 'cos singleSpa is an object so cannot be converted to a primitive value.
I'm not sure what the correct way to fix this is; if I omit
        name: this.name,
        mountParcel: this.mountParcel,
        singleSpa: this.singleSpa,

completely, things work, but I don't know what effect that will have.
Oh, I'm using vue 3.0.5, single-spa-vue 2.2.0 - basically I set it all up yesterday and ran into this problem.
Vue 2 works absolutely fine. I notice it does not pass those three props in the docs.

Update! Aahhhhh, so if I define
  props: {
    name: String,
    mountParcel: Function,
    singleSpa: Object
  }

In my App.vue, it stops trying to render them into the DOM. Right ok, that makes sense.
Why are those in the example for vue3 and not vue2? I'd suggest removing them from the vue3 one as well maybe.

Thanks for the description here - I think the best solution would be to modify App.vue to add those props. However, that can be tricky, as App.vue is an existing file when vue-cli-plugin-single-spa runs and it's hard to parse and modify existing files.
I don't think that deleting the props is a good solution, as it's a very common question we receive "how do I use single-spa props." Perhaps we could comment out the props in the main file, explaining that you can uncomment the props if you modify the App.vue file accordingly. The reason that the props exist in the Vue 3 main file but not the Vue 2 file is that we added the props because it was so common of a question, and forgot to do it in both places.
I'm transferring this to vue-cli-plugin-single-spa. Here's the relevant file: https://github.com/single-spa/vue-cli-plugin-single-spa/blob/89d9868f1b3ff9db1870452e23586cd78f89e503/template/src/main-vue-3.js#L14. Do you have interest in submitting a pull request commenting out the props in vue 3, and adding the commented props to vue 2?


Reading: Update spec for recursive fetching

Fix for not updating spec in https://github.com/studentinsights/studentinsights/pull/2626.

selfie


E-W and N-S orography gradient field

Part of Epic #97
As a Improver developer I need fields that enable me to spread probabilities in a orographically appropriate manner (e.g. not spreading the high risk of fog in a valley up the surrounding hill sides). To do this I need fields of orography gradient calculated in the x and y directions only (not diagonal).
Acceptance criteria:

Create CLI to enable creation of diagnostic gradient fields using adjacent cell gradient plugin (in utilities.spatial).
Produce an example field using orography as input and check output.

@bayliffe I think that there might be the need for a follow-on issue in order to make sure that the structure of the directory containing the CLI test data is optimal. I think as we write more tests the top-level $IMPROVER_ACC_TEST_DIR directory might get quite full, so may be there would be a better way to structure this directory.


Conflict ClientMessage.h with mysql-dev

I found a conflict thing.
static const uint8_t PROTOCOL_VERSION in hazelcast/client/protocol/ClientMessage.h:111
It conflict with defined Macro In mysql/mysql_version.h in mysql-dev (5.7.25)

Many thanks @skyend for raising this issue with your PR! 👏 :)


Update Chart metadata

Update Chart metadata in order to host Kamaji on Rancher application catalog.

@bsctl this could be a nice issue for Hacktoberfet: may I ask you to share the required metadata in order to accept contributions also from new contributors?

Here the required metadata:
annotations:
  catalog.cattle.io/certified: partner
  catalog.cattle.io/release-name: kamaji
  catalog.cattle.io/display-name: Kamaji - Managed Kubernetes Service


Wfc598

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/429/
Test PASSed.


Request: Origin, PSN, and Wii Icons

Hoping to see Origin: Powered by EA, PSN (Playstation Network), and Nintendo Wii/Wii U Icons

These are all included now, I think.


Bump operative reinforcement cost

See https://github.com/tgstation/tgstation/blob/838742297ee2cd692362c42b8bccde8a5e307376/code/modules/uplink/uplink_items/nukeops.dm for tg values
Few issues:

I wanted to make borgs cheaper but we don't have as many tools to deal with borgs as in 13 so I left that higher for now until they're more fleshed out and we can balance them better (though they can be super squishy in some situations which is eh).
Operatives seem to be getting used frequently as they're easy to arm up and bump nukie numbers where they might've been 3-5 to 5-8.

:cl:
tweak: Bumped nukie operative cost from 14 to 35TC.

Woah that's a massive bump. You practically cant get them unless you warops.

changelog said 14 but the price is 16

Woah that's a massive bump. You practically cant get them unless you warops.
Doesn't TG also have TC earning mechanics?

no idea but considering mechs go up to 100TC seems fine to me.

This is awful.
35 TC for a suicide bomber

Better PR https://github.com/space-wizards/space-station-14/pull/29557


few pizza images are missing in menu section

few pizza images are missing in menu section

#42 added pizza images in menu


TypeError for td.OneOf

I am using td.OneOf to set up terminal condition for recursion, which means I will implement two different blocks based on whether I get empty list or not.
td.OneOf(lambda pair: pair[0] == [],  (add_metrics(is_train, is_empty=False), add_metrics(is_train, is_empty=True)))
But I get "TypeError: bad output type PyObjectType for <td.Composition.input 'metrics'>, expected TupleType". It seems that a PyObjectType is fed into add_metrics, but I am pretty sure that the output before td.OneOf is TupleType.
Thanks!

Hi, I think I solved the problem.
The basic usage of td.OneOf is:
td.OneOf(key_fn, case_blocks),
where key_fn is either a python function or a block.
In a python function case, the Fold transforms it into a td.InputTransform block with PyObjectType inputs and outputs.
Remember that all the input types of key_fn, case_blocks, and td.AllOf must keep the same, because the output before td.OneOf is also fed into key_fn as input. When initiate td.AllOf, Fold propagates the input type from key_fn block to td.AllOf and then case_blocks. See line 1629 of blocks.py
So, here is the contradiction for case_blocks between your input type TupleType and the expected PyObjectType.
See the following example.
a=['1',['3', '4']]
b=['2',['3', '4']]
block1 = (td.Scalar('int32'), td.Scalar('int32'))
block2 = td.Function(tf.add)
block3 = td.Function(tf.multiply)
oneof = (td.Identity(), block1) >> td.OneOf(key_fn=lambda x: x=='1', case_blocks=(td.GetItem(1) >> block2, td.GetItem(1) >> block3))
We will get "TypeError: bad input type PyObjectType for <td.Function tf_fn='add'>, expected TupleType or TensorType". It can be solved by this:
oneof = (td.Identity(), block1) >> td.OneOf(key_fn=(td.GetItem(0) >> td.InputTransform(lambda x: x=='1')),         case_blocks=(td.GetItem(1) >> block2, td.GetItem(1) >> block3))
oneof.eval(a)  => array(12, dtype=int32)
oneof.eval(b)  => array(7, dtype=int32)


Speed up attach process by using cached API

It's more of a bug fix.
We shouldn't use kubeclient to make direct API to the server since there is no cache.
This speeds up the volume attaches process by about 50%.
https://github.com/longhorn/longhorn/issues/160

@yasker I wonder that was engine-manager debug logging enabled on purpose in here or just something which you forgot? It looks be still hardcoded to enabled on now three years later.


Make sure sage installs correctly

@dimpase @isuruf
Trying to install sage python=2.7 with mamba seems to crash. I am investigating locally. Maybe you can help?
What does the crash say?

it boils down to
ImportError: /home/dimpase/miniconda2/envs/sage/lib/python2.7/site-packages/sage/matrix/../../../../liblinboxsage.so.0: undefined symbol: _ZNK6Givaro7IntegercvSsEv

something to do with givaro package, I guess.

It's not a conda issue. It's a packaging issue. Sage hasn't been updated to the new compilers and needs a rebuilt. So, conda create -n sage sage python=2.7 -c conda-forge/label/cf201901 should work. (conda-forge/label/cf201901 is a channel with the old packages.)

OK, I tried mamba create -n sage sage python=2.7 -c conda-forge/label/cf201901 - this gives a working version of Sage 8.3. Great, thanks!

cool! thanks @isuruf for helping out.


The number of train

While I read the data， 772 in train_tasks_in_train.json

Thanks for trying our source code. For the file "train_tasks_in_train.json" of NELL and Wiki, the lengths indeed are 342 and 772. However, we ignore small training tasks which have no more than 10 triples (implemented in line 34 of "data_loader.py"), so the final statistics are 321 and 589.


Please document env vars

I see 2 env vars in the source code, but they don't seem to work and it will still ask for the token and write it to ~/.transifexrc.
Would be great to fully run it with env vars only and document it in the README.
Thanks!

@m3nu Of course we can add it to the documentation, but regarding your question could you please share a little bit more about how you set your environment variables, to unblock you?
Things I tried so far, just to see if everything behaves normally:

Prefixing the variable TX_TOKEN=randomstring tx status ✅
Adding the variable in profile file export TX_TOKEN="randomstring" ✅

It works now. Not sure what was wrong before.

Thanks for the update @m3nu! 💪
We will include the environment variables in the documentation and I will close this!

Documentation updated!


Adding a link to the updated Hebrew translations.

Hi guys,
I've added a more recent translation of AOR & published a NPM package for it (the previous repo didn't have one).

ping @mstmustisnt, is your translation still supported?

@motro I'd prefer that you collaborate with @mstmustisnt on the mstmustisnt/aor-language-hebrew repository instead of starting a new one.

@fzaninotto I'd prefer that too, however there was never a NPM package published under this name (meaning no one has used it before since trying to install it would fail) and the repo hasn't been updated for the last 7 months.
In fact, I just published the NPM package yesterday for the first time: https://www.npmjs.com/package/aor-language-hebrew

Sorry, guys. I'm not able to provide support to keep Hebrew translations updated.


brew breaks sudo password cache

brew doctor output
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
  python-packaging

Verification

[X] My "brew doctor output" above says Your system is ready to brew. and am still able to reproduce my issue.
[X] I ran brew update twice and am still able to reproduce my issue.
[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

brew config output
HOMEBREW_VERSION: 4.3.12
ORIGIN: https://github.com/Homebrew/brew
HEAD: 874d2da45344d3b27aa740e555b0210d8c474220
Last commit: 8 hours ago
Core tap JSON: 30 Jul 13:41 UTC
Core cask tap JSON: 30 Jul 13:41 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 12
Homebrew Ruby: 3.3.4 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4/bin/ruby
CPU: dodeca-core 64-bit arm_blizzard_avalanche
Clang: 15.0.0 build 1500
Git: 2.39.3 => /Applications/Xcode.app/Contents/Developer/usr/bin/git
Curl: 8.4.0 => /usr/bin/curl
macOS: 14.3.1-arm64
CLT: <IP_ADDRESS>.1.1708646388
Xcode: 15.4
Rosetta 2: false

What were you trying to do (and why)?
I want to type a sudo password only once during a timeout period.
What happened (include all command output)?
After any brew command, any sudo command aftwards requires the password, even when I entered it just before.
What did you expect to happen?
That the sudo password cache does not expire when using brew commands
The following might ask for the sudo password first
sudo -v
brew --help
sudo -v

But since a brew update today it also always asks it after the brew command even though it should be still in the sudo cache
Step-by-step reproduction instructions (by running brew commands)
Just run

sudo -v
brew --help
sudo -v

and see if it asks for the sudo password after the brew command

This is likely a WONTFIX, sorry. We clear the sudo password cache intentionally as a precaution against privilege escalation attacks. See https://brew.sh/2024/07/30/homebrew-security-audit/.

If

Seems to be hardcoded:
https://github.com/Homebrew/brew/blob/eac5720d44457fcfcb24b325bde3a70fce41ac15/bin/brew#L70-L74
Would you allow a flag which skips resetting the sudo password cache?
Else, I don't see a way to use brew with automation (e.g. Ansible) when it's combined with other package managers (like apt).
One could use Ansible Vault to store the sudo password, and it could be a little more secure if root privileges are only used for the parts where it is needed.
On the other hand, a flag to skip the reset would be very handy.

Would you allow a flag which skips resetting the sudo password cache?

No, seems inappropriate to disable a security feature flagged in our audit this way.

I don't see a way to use brew with automation (e.g. Ansible) when it's combined with other package managers (like apt).

Use SUDO_ASKPASS or sudoers entry. There are many ways of accomplishing this without a flag.


[FR] Improve the BulkWriter API to prevent UnhandledRejections

The BulkWriter class was made public in version 4.1.0. however, it has some use disadvantages compared to using a BatchWriter.
The problem lies in the fact that close never fails, and the fact that writing (update, delete, set) returns a promise.
This makes it difficult and awkward to correctly handle errors, which is absolutely necessary on cloud functions, as UnhandledRejections will make the whole function to fail with a very cryptic error.
It'd be great if we could write something like:
const writer = db.bulkWriter();
writer.update(ref1, {...});
writer.update(ref2, {...});
try {
  await writer.commit();
} catch (error) {
  // decide whether to continue, fail, log or do something else based on the error.
  // error could be an object having a `failures` and `succeses` fields, where each failure or success has the all the arguments of the write operation.
  // Or something similar to the result of promiseAllSettled. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/allSettled
}

Note that using WriteBatch resembles the proposed API.
Compare that to what one needs to do today.
let sharedState = ...;
const writer = db.bulkWriter();
 // depending on whether we want to skip failures or actually fail what the catch function will be
writer.update(ref1, {...}).catch(...);
writer.update(ref2, {...}).catch(...);
await writer.close();
// Check shared state

@sk- Thanks for the feedback! When designing the BulkWriter API, we considered but ultimately decided against such a design due to the additional state management that would be required to map the index-based results array back to the original requests. In addition, BulkWriter does not have the 500-write limit that WriteBatch has and automatically batches and sends writes. This would make defining the return behavior for flush() more complex when flush() is called several times in succession with writes in between (returning all writes vs. just the writes in between flush() calls).
However, you bring up a good point that having floating promises can result in hard to debug UnhandledPromiseRejection errors. From here, we are looking at two options:

Expose an error handler that BulkWriter will run when an operation fails.
On close(), return a list of document writes that succeeded, and a list of document writes that failed.

In both cases, we would be adding a catch() handler that would prevent the UnhandledPromiseRejection errors from being thrown.
Would either of these options help your use case? Are you hoping to blindly retry writes that failed, or run some other logic?

Thanks @thebrianchen for the reply.
In our case we just want to log those requests that failed, as those will certainly indicate some error or data corruption in our side. Think of failed updates or deletes. We also want to stop execution of subsequent code.
In our use case I don't think we are going to be calling flush repeatedly, as we are mostly replacing WriteBatch with BulkWriter.
Of the two options I think the second one works better with async/await and would be similar to what I proposed. Defining a default error handler may avoid repetition (if the writes are not done in a loop) but still requires to handle a shared state, that you need to check after closing the writer.
Compare:
let sharedState = ...;
const writer = db.bulkWriter();
 // depending on whether we want to skip failures or actually fail what the catch function will be
for(const id of usersToUpdate) {
  writer.update(db.collection('users').doc(id), {...}).catch((error) => {...});
}
await writer.close();
// Check shared state

vs
let sharedState = ...;
const writer = db.bulkWriter({errorHandler: (error) => {...}});
 // depending on whether we want to skip failures or actually fail what the catch function will be
for(const id of usersToUpdate) {
  writer.update(db.collection('users').doc(id), {...});
}
await writer.close();
// Check shared state

Just a quick update that this feature is still being considered and worked on, but I've had several other issues come up in the meantime. I'll be getting to working on this soon!


Output format issue

Hello!
I have an issue with adjusting a required output format. In the documentation I've noticed that gcpdiag have a support for multiple output formats (json, csv, terminal). But whenever I'm trying to issue the gcpdiag lint --output json --project PROJECT. I'm receiving the following error gcpdiag lint: error: unrecognized arguments: --output json. Could you please explain what can be the issue here?
Regards

+1
details:
gcpdiag 0.55
usage: gcpdiag lint [-h] [--auth-adc] [--auth-key FILE] [--auth-oauth] --project P
[--billing-project P] [--show-skipped] [--hide-ok] [--include INCLUDE]
[--exclude EXCLUDE] [--include-extended] [-v] [--within-days D] [--config FILE]
[--logging-ratelimit-requests R] [--logging-ratelimit-period-seconds S]
[--logging-page-size P] [--logging-fetch-max-entries E]
[--logging-fetch-max-time-seconds S]
the output was: gcpdiag lint: error: unrecognized arguments: --output csv
Run diagnostics in GCP projects.
optional arguments:
-h, --help            show this help message and exit
--auth-adc            Authenticate using Application Default Credentials
--auth-key FILE       Authenticate using a service account private key file
--auth-oauth          Authenticate using OAuth user authentication (default)
--project P           Project ID of project to inspect
--billing-project P   Project used for billing/quota of API calls done by gcpdiag (default is the
inspected project, requires 'serviceusage.services.use' permission)
--show-skipped        Show skipped rules
--hide-ok             Hide rules with result OK
--include INCLUDE     Include rule pattern (e.g.: gke, gke/*/2021*). Multiple pattern can be
specified (comma separated, or with multiple arguments)
--exclude EXCLUDE     Exclude rule pattern (e.g.: BP, */*/2022*)
--include-extended    Include extended rules. Additional rules might generate false positives
(default: False)
-v, --verbose         Increase log verbosity
--within-days D       How far back to search logs and metrics (default: 3 days)
--config FILE         Read configuration from FILE
--logging-ratelimit-requests R
Configure rate limit for logging queries (default: 60)
--logging-ratelimit-period-seconds S
Configure rate limit period for logging queries (default: 60 seconds)
--logging-page-size P
Configure page size for logging queries (default: 500)
--logging-fetch-max-entries E
Configure max entries to fetch by logging queries (default: 10000)
--logging-fetch-max-time-seconds S
Configure timeout for logging queries (default: 120 seconds)

Thank you for reporting this issue. Let me investigate this problem.


25 add include parameter

Added Parameter -Include. Works very similar to -Exclude, the patterns are evaluated against the items .FullName property, however this parameter targets only files (FileInfo instances). Closes #25.

Codecov Report

Merging #26 (a87b92a) into main (7238b44) will increase coverage by 0.44%.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main      #26      +/-   ##
==========================================
+ Coverage   91.86%   92.30%   +0.44%
==========================================
  Files          11       11
  Lines         332      351      +19
==========================================
+ Hits          305      324      +19
  Misses         27       27

Flag
Coverage Δ

PS_5.1
?

PS_7_Windows
92.30% <100.00%> (+0.44%)
:arrow_up:

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

Files
Coverage Δ

src/PSTree/Commands/GetPSTreeCommand.cs
91.40% <100.00%> (+1.49%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


"CI" workflow does not run on PRs

For example https://github.com/ansys/grantami-serverapi-openapi/pull/100.
Expected behavior:

Push changes to pom file
'Generate client library' workflow runs, generates the client code and commits changes
'CI' workflow is triggered, as files in 'ansys-grantami-serverapi-openapi' have been modified. (<- does not happen)

May be related, but it seems that pushing another change to the pom file on an existing PR does not trigger a re-run of the 'Generate client library' workflow.

I’m sure I’ve seen this working elsewhere, i.e. bomanalytics-openapi? You push a change to the pom or json definition, which triggers the regeneration of the code, and then the CI runs to bills and test the package.
I don’t have my laptop though, so it’s difficult to check to be sure.


Fix propagation of use_flash for offloaded inference

This change fixes an issue where _forward_offload() was being passed the parameter use_flash but didn't accept the parameter use_flash. This also passes use_flash along to _prep_blocks() since it's a required parameter.
Context
When running run_pretrained_openfold.py with the config for offload_inference enabled, this error occurred:
Traceback (most recent call last):
  File "/.../shared/openfold/run_pretrained_openfold.py", line 591, in <module>
    main(args)
  File "/.../shared/openfold/run_pretrained_openfold.py", line 439, in main
    out = run_model(model, processed_feature_dict, tag, args)
  File "/.../shared/openfold/run_pretrained_openfold.py", line 119, in run_model
    out = model(batch)
  File "/.../shared/openfold/lib/conda/envs/openfold_venv/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
    return forward_call(*input, **kwargs)
  File "/.../shared/openfold/openfold/model/model.py", line 510, in forward
    _recycle=(num_iters > 1)
  File "/.../shared/openfold/openfold/model/model.py", line 384, in iteration
    _mask_trans=self.config._mask_trans,
TypeError: _forward_offload() got an unexpected keyword argument 'use_flash'

Thanks for the PR! This was actually half-deliberate; FlashAttention doesn't work that well for the long sequence sizes for which the offloading mode is useful. I propose completely removing the use_flash parameter being passed to _forward_offload in model.py and manually passing use_flash=False to _prep_blocks in the same function instead.


Create make clean target

We need a make clean target that wipes out logs, binaries, etc.

Fixed on e96ceca8dbde151a864d21e4c6812bb058bf78ea


build breaks with 5.0.0-beta.2

Issue description

reactstrap version #5.0.0-beta.2
import method es
react version #16.2.0
bootstrap version #4.0.0

What is happening?
when building with gulp + browserify this happens:
/Users/matteo/dev/my-project/node_modules/react-popper/lib/react-popper.js:1
export { default as Manager } from './Manager';
^
ParseError: 'import' and 'export' may appear only with 'sourceType: module'

If I install 5.0.0-beta everything is fine
If I install 5.0.0-beta.2 the build breaks
If I manually install react-popper 0.8.2 and delete 0.8.1 everything is fine again

the strange thing is that react-popper was updated from 0.8.1 to 0.8.2 to "fix: build" (see https://github.com/souporserious/react-popper/commit/0d97929b038b1bba69f920772505f8d6af158f3f), while reactstrap's commit b515e6b says "chore(build): downgrade react-popper to fix build"

The fix build was supposed to downgrade the version in the yarn lock, I didn't notice it was bumped in the package.json... Yay two package systems! ....

I was going off of https://github.com/reactstrap/reactstrap/issues/859#issuecomment-368629275
@supergibbs what version of react-popper should we be depending on (to get a release out)?

0.8.1 worked for me. Hopefully there is a 0.8.3 coming soon. Fix is ready:
https://github.com/souporserious/react-popper/pull/93

Right. I looked, the package.json and yarn.lock both are pinned 0.8.1, but the issue above is stating that 0.8.1 is not working, but when upgrading to 0.8.2 it does. ¯_(ツ)_/¯

Hi, I've redone everything from scratch to be extra-sure. I can confirm react-popper 0.8.2 works for me:
$ # modified package.json to install 5.0.0-beta.2
$ rm -rf node_modules
$ npm install
$ gulp build
[...]
export { default as Manager } from './Manager';
^
ParseError: 'import' and 'export' may appear only with 'sourceType: module'
$ rm -rf build
$ npm install<EMAIL_ADDRESS>$ rm -rf node_modules/reactstrap/node_modules/react-popper
$ gulp build
[...]
[17:56:31] Finished 'build' after 59 s

I wonder if there is a babel update making that work? You aren't using yarn so the lock file is getting ignored

This works for me with npm v5.6.0 and yarn v1.5.1:
rm -rf node_modules
yarn
yarn build

running yarn add react-popper@latest installs v0.8.2 and then yarn build fails

I'm using node 6.12.2 and npm 3.10.10, mainly because of an issue with l10ns which doesn't install on more recent node versions (at least it didn't, should check if they fixed the issue)
I'll try to find some spare time to make a small app with the minimum amount of dependencies to see if I can replicate the error, so maybe we can see if it's due to babel or something else.

Well hopefully react-popper will update soon and fix it for everyone but think this can be closed for now since yarn works (beta.2 is out 🎉) and that is the official build tool for this project.

v0.8.2 doesn't have this issue<EMAIL_ADDRESS>v0.8.1 does<EMAIL_ADDRESS>Since it's complaining about export { default as Manager } from './Manager';, only the versions with that code would be an issue... right?

Oh sorry, I was confused by @cvlmtg's original issue. Using beta.2 broke the app build, not building reactstrap. I am now getting that error on my app trying to use beta.2.
Sounds like 0.8.2 breaks the rollup build in reactstrap but is needed after the build. Ugh. Maybe revert back to 0.7.4 until 0.8.3 is out (assuming that fixes it)?

Or build with 0.8.1 then change the dependency to 0.8.2?

Other errors when using Reactstrap 5.0.0-beta.2 externally:
TypeError: Cannot use 'in' operator to search for 'default' in undefined
// Dist location
var ReactDOM__default = 'default' in ReactDOM ? ReactDOM['default'] : ReactDOM;

Do we need a postbuild test to ensure the generated files are valid or something?

I get the same issue in a project that uses Browserify + Babel for .jsx files. Hacking my node_modules/ to upgrade to react-popper 0.8.2 fixes the issue for me.

Similar issue with a Gatsby SSR starter using reactstrap - updating to 0.8.2 solved it.

@TheSharpieOne Wouldn't be a bad idea to do a quick post-build test.
Would need 2:
1 - Using explicit dependencies
  <script src="//cdnjs.cloudflare.com/ajax/libs/prop-types/15.6.0/prop-types.min.js"></script>
    <script src="//cdnjs.cloudflare.com/ajax/libs/react/16.0.0/umd/react.production.min.js"></script>
    <script src="//cdnjs.cloudflare.com/ajax/libs/react-dom/16.0.0/umd/react-dom.production.min.js"></script>
    <script src="//cdnjs.cloudflare.com/ajax/libs/react-transition-group/2.2.1/react-transition-group.min.js"></script>
    <script src="//cdnjs.cloudflare.com/ajax/libs/react-popper/{{replaceWithReactPopperPackageVersion}}/react-popper.min.js"></script>
    <script type="text/javascript" src="{{ReactstrapDistBuildDefaultMin}}"></script>

    <script> // Run through a few basic reactstrap tests here </script>

2 - Using full version
   <script src="//cdnjs.cloudflare.com/ajax/libs/prop-types/15.6.0/prop-types.min.js"></script>
    <script src="//cdnjs.cloudflare.com/ajax/libs/react/16.0.0/umd/react.production.min.js"></script>
    <script src="//cdnjs.cloudflare.com/ajax/libs/react-dom/16.0.0/umd/react-dom.production.min.js"></script>
    <script type="text/javascript" src="{{ReactstrapDistBuildFullVersionMin}}"></script>

    <script> // Run through a few basic reactstrap tests here </script>

So, what's the plan? Are we just waiting for react-popper to release a new version? Do we want to downgrade to a version of react-popper which works both in the build and usage? Do we want to build with 0.8.1, but have the package.json reference 0.8.2?

For me 0.8.2 has no issues.
So the current workaround for reactstrap is to install react-popper and run rm -rf node_modules/reactstrap/node_modules/react-popper. It think updating reactstrap to 0.8.2 shoud be fine.

Right, 0.8.2 doesn't appear to have any run-time issues, but it breaks the rollup build used to generate reactstrap's release artifacts due to the way<EMAIL_ADDRESS>defines the exports (note in that link the exports are defined via function execution, not something that rollup's tree walking can automatically pick up).


kafka spout patching

Patching heron for it work with kafka-spout.

Great!!!

👍

@nlu90 - This patch will suffice for running Storm kafka spout. Or we need this for heron-kafka spout as well?

@kramasamy we need this for heron-kafka spout as well

@nlu90 - instead of introducing another set of configuration for the spout, I was wondering, can we think about making it more simpler. Looking at the config - kafka spout - seems to adding a lot of config and hard coded as well. We want to move away from hard coding the config into the topology. We can introduce the notion of config per component - in a cleaner fashion.

@kramasamy If we want to introduce the notion of config per component, what are the changes needed?

ship it 👍


Crash if gyroscope disabled in app settings

Summary:
I hoped to get a more steady image if I disable the gyro in the settings. But if I disable the gyroscope and leave the settings, the app immediately crashes. After the loading screen, it crashes again, only way to resume operation is deleting all app data.
Steps to reproduce:
Tick the "Disable gyro" checkbox, leave the menu.
Expected behavior:
Works as it did before.
Observed behavior:
Crashes, will no longer load
Device and Android version:

Xiaomi Mi 9T Pro (also sold as Redmi K20 Pro)
MIUI 12.5.2 Global (default ROM)
Android 11
Google Play Services 21.30.16

Screenshots:
Not much to see regarding the crash, leave the settings, app closes. So maybe I'll attach some stack trace instead.
skymap-crash.txt
That's from starting after I broke it, I guess the one right after breaking would look similar.

Thanks a lot for the report! Disable gyro is really a hack for folks whose
phones don't have a gyroscope and switches them back over to the old
compass & accelerometer way of doing things.  Obviously it shouldn't crash
though! So I'll look into that. If you just want to stop the map moving
then tap the manual mode/auto mode button that shows on the main screen
(looks like a finger icon).
On Thu, Sep 2, 2021 at 11:39 AM Blauelf @.***> wrote:

Summary:
I hoped to get a more steady image if I disable the gyro in the settings.
But if I disable the gyroscope and leave the settings, the app immediately
crashes. After the loading screen, it crashes again, only way to resume
operation is deleting all app data.
Steps to reproduce:
Tick the "Disable gyro" checkbox, leave the menu.
Expected behavior:
Works as it did before.
Observed behavior:
Crashes, will no longer load
Device and Android version:

Xiaomi Mi 9T Pro (also sold as Redmi K20 Pro)
MIUI 12.5.2 Global (default ROM)
Android 11
Google Play Services 21.30.16

Screenshots:
Not much to see regarding the crash, leave the settings, app closes. So
maybe I'll attach some stack trace instead.
skymap-crash.txt
https://github.com/sky-map-team/stardroid/files/7099325/skymap-crash.txt
That's from starting after I broke it, I guess the one right after
breaking would look similar.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sky-map-team/stardroid/issues/406, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD5LWC7BMQDCC4L6UP4JH6DT76LB7ANCNFSM5DJM45XQ
.

BTW - although I can't reproduce this on my phone, the log you provided is
really useful and I'm pretty sure I can fix the issue based on that.
On Fri, Sep 3, 2021 at 7:54 AM John Taylor @.***> wrote:

Thanks a lot for the report! Disable gyro is really a hack for folks whose
phones don't have a gyroscope and switches them back over to the old
compass & accelerometer way of doing things.  Obviously it shouldn't crash
though! So I'll look into that. If you just want to stop the map moving
then tap the manual mode/auto mode button that shows on the main screen
(looks like a finger icon).
On Thu, Sep 2, 2021 at 11:39 AM Blauelf @.***> wrote:

Summary:
I hoped to get a more steady image if I disable the gyro in the settings.
But if I disable the gyroscope and leave the settings, the app immediately
crashes. After the loading screen, it crashes again, only way to resume
operation is deleting all app data.
Steps to reproduce:
Tick the "Disable gyro" checkbox, leave the menu.
Expected behavior:
Works as it did before.
Observed behavior:
Crashes, will no longer load
Device and Android version:

Xiaomi Mi 9T Pro (also sold as Redmi K20 Pro)
MIUI 12.5.2 Global (default ROM)
Android 11
Google Play Services 21.30.16

Screenshots:
Not much to see regarding the crash, leave the settings, app closes. So
maybe I'll attach some stack trace instead.
skymap-crash.txt
https://github.com/sky-map-team/stardroid/files/7099325/skymap-crash.txt
That's from starting after I broke it, I guess the one right after
breaking would look similar.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sky-map-team/stardroid/issues/406, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD5LWC7BMQDCC4L6UP4JH6DT76LB7ANCNFSM5DJM45XQ
.

Very odd. The smoothing code expects  a sensor event with a value array of size 3. It's not getting one I guess. I think this fix will stop the crash, but it'll basically just turn the smoother into a noop. If the sensor event is the wrong size I'm not sure the app will actually work...but at least it ought not to crash.

Hmm.  I can now reproduce this on my own phone when I create a new build, but not with the app as currently released in the Play Store.  My guess is it's related to upgrading the SDK. I wonder if they deprecated or broke something.

On a side note, I've actually experienced the same crash on my Galaxy A50 a few months ago, when I was working on my Telescope.Touch fork. For my app, I solved it by completely removing ExponentiallyWeightedSmoother. In my tests, it had no noticeable effect on the sky map - other than sometimes crashing it.
Increasing the refresh rate of the map to 60 FPS had a much better effect, making it extremely smooth and responsive. I achieved it by using SensorManager.SENSOR_DELAY_FASTEST in the SensorOrientationController, and setting updatesPerSecond to 60 in the Flinger class. All the mid-range smartphones I tested had no trouble dealing with a 60Hz refresh rate. Maybe give it a try and see if it works for you.
Regards,
Marco Cipriani

Thanks Marco. Much of Sky Map's code was designed for prehistoric phones -
e.g. the smoother code was the original code built from before most phones
did some kind of sensor fusion.  The refresh rate was also set for "how
high can we set this before the phone locks up"!  Obviously times have
changed.
I'm still a bit puzzled why this happens though - on my own phone it will
crash in the way the OP described if I do a new build against Android-30 so
I wonder if some old API has been disabled.  Ideally I'd keep this code
here as there are still some new phones that lack gyroscopes and don't seem
to properly implement the direction sensor...but perhaps it's time to
retire it.
On Mon, Sep 6, 2021 at 6:34 PM Marco Cipriani @.***>
wrote:

On a side note, I've actually experienced the same crash on my Galaxy A50
a few months ago, when I was working on my Telescope.Touch fork. For my
app, I solved it by completely removing ExponentiallyWeightedSmoother. In
my tests, it had no noticeable effect on the sky map - other than sometimes
crashing it.
Increasing the refresh rate of the map to 60 FPS had a much better effect,
making it extremely smooth and responsive. I achieved it by using
SensorManager.SENSOR_DELAY_FASTEST in the SensorOrientationController,
and setting updatesPerSecond to 60 in the Flinger class. All the
mid-range smartphones I tested had no trouble dealing with a 60Hz refresh
rate. Maybe give it a try and see if it works for you.
Regards,
Marco Cipriani
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/sky-map-team/stardroid/issues/406#issuecomment-913875161,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD5LWCZ3DK3RQJIP2AFEYS3UAU6WHANCNFSM5DJM45XQ
.

Much of Sky Map's code was designed for prehistoric phones

Yeah, I spent a lot of time updating Telescope.Touch to use the latest APIs and Android/Java features, especially on the UI side. I also updated some code that handles sensors because of some deprecated API calls. However, it had nothing to do with this issue, and I did it mainly to future-proof my app. I have no idea why the GPlay version works and the debug one doesn't.

Ideally I'd keep this code here as there are still some new phones that lack gyroscope

I didn't delete the accelerometer code (or anything non-gyroscope related). I only removed the smoother. Feeding the raw values to the map without any smoothing/processing had a slightly positive effect on performance. Removing the accelerometer support would mean removing even modern low-end smartphones from the list of supported devices (e.g. the Galaxy A20 series).

Here's the diff: https://github.com/sky-map-team/stardroid/compare/1.9.7-RC1...master
The only non-trivial changes are things like dependency versions and build versions.

I think it has something to do with the new targetSdkVersion and compileSdkVersion. I've noticed several times behavior changes when targeting a new Android release. What happens if you revert back to version 30?
Note that targeting Android 12 (API 31) requires adding the exported flag to the launcher activity, otherwise the app may not compile or run: Manifest merger failed: Apps targeting Android 12

Oh silly me. Should have checked this first as it's pretty obvious in hindsight.
It was caused by this well-intentioned PR to upgrade to the latest sensor API:
https://github.com/sky-map-team/stardroid/commit/a884f53db6e60791be6c8822f813b3cad2342227
I haven't looked in detail into why it causes the crash, I'm just going to roll it back for now.  I should have tested it properly before accepting it.

And the diff I think I should have been looking at was the 'two dot' one: https://github.com/sky-map-team/stardroid/compare/lastworkingversion..master


get current context inside registered function

Hi , is it possible to get the current build context inside a registered function?

Sort of.  You can use the save_context type to save the build context into a variable name and then reference it via the template syntax or within your function from the registry.

Thanks


Error in convert_checkpoint.py when converting 13B weights

Whenever I try to convert the 13B weights (unmodified) sourced from the dalai llama download, the first checkpoint successfully completes; however, the second checkpoint fails to convert.
I am using this command:
python scripts/convert_checkpoint.py
--output_dir checkpoints/lit-llama
--ckpt_dir dalai/llama/models
--tokenizer_path /dalai/llama/models/tokenizer.model
--model_size 13B
And receive the following error:
python scripts/convert_checkpoint.py     --output_dir checkpoints/lit-llama     --ckpt_dir dalai/llama/models     --tokenizer_path dalai/llama/models/tokenizer.model     --model_size 13B
50%|███████████████████████████████████████████                                           | 1/2 [00:32<00:32, 32.09s/it]
Killed

most likely it means you don't have enough RAM

I have 32 gb, how much do you need?

On Apr 7, 2023, at 3:30 AM, Chris @.***> wrote:

most likely it means you don't have enough RAM
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

Work is underway here https://github.com/Lightning-AI/lit-llama/pull/108 to make it cheaper (30GB should suffice)

@psych0v0yager I don't think you have enough RAM to hold the 13B model at 32bit precision (you need 48GB).
As a check, try instantiating the 13B model
from lit_llama.model import LLaMA

model = LLaMA.from_name("13B")

BTW are you loading the original checkpoints? We could provide an option to load incrementally in bfloat16 to reduce the requirements.

This should help: https://github.com/Lightning-AI/lit-llama/pull/111
@psych0v0yager can you try this out on your system?

Thank you for the prompt replies.
I attempted the instantiation and additional conversion argument and received the following results.
Python 3.10.10 (main, Mar 21 2023, 18:45:11) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

from lit_llama.model import LLaMA
model = LLaMA.from_name("13B")

Killed
python scripts/convert_checkpoint.py     --output_dir checkpoints/lit-llama     --ckpt_dir /dalai/llama/models     --tokenizer_path /dalai/llama/models/tokenizer.model     --model_size 13B --dtype bfloat16
50%|█████████████████████████████████████████████████████████████████▌                                                                 | 1/2 [00:46<00:46, 46.04s/it]
Killed
Could it potentially be a VRAM issue? I only have 12 gb in my Nvidia 3060. Furthermore the model weights come from the dalai llama repo (https://github.com/cocktailpeanut/dalai) and I believe they are the full precision weights.
Thanks again for the support

Killed means that the program was killed by your OS. From my experience it appears in 99% when you try using more RAM and SWAP than you have. My advice: run htop (or top) and check the memory consumption when the script is running to confirm the root cause of the problem. If you dont have enough VRAM, you see OOM exception.

Closing this one, feel free to reopen


[Vita, Switch] Vita and Switch Ports

It's #1 but with a clean commit history!
This pull request is the result of grabbing all the changes from both @Stary2001's fork, and @SonicMastr's fork, cutting out the fat, and sticking it on top of a fresh copy of Godot's 3.5 branch!
It's tested locally and working. Hopefully, this will be the last time I have to submit or edit this.

Editor is borked for some reason. Will investigate tomorrow.


Add safe query_interface for classes

We currently have a safe way to invoke QI for interfaces but not for classes. We should implement one.

Unlike WinRT classes, COM classes don't have an ABI representation.

That's not what this issue was meant to capture, but the real reason also doesn't make much sense either. Closing


e2e/prune: run two top containers

In hope to make the prune tests more robust, run two top containers and
stop one explicitly to reduce the risk of a race condition.
Fixes: #4452
Signed-off-by: Valentin Rothberg<EMAIL_ADDRESS>

LGTM and happy green tests, including prune.  @mheon @baude WDYT?

/lgtm


Merge trunk

Resolving merge conflict for upstream version bump to 3.8-SNAPSHOT:
gradle.properties
streams/quickstart/java/pom.xml
streams/quickstart/java/src/main/resources/archetype-resources/pom.xml
streams/quickstart/pom.xml
tests/kafkatest/__init__.py

Plus one more conflict in bin/kafka-server-stop.sh:
<<<< HEAD
    PIDS=$(ps ax | grep ' kafka\.Kafka ' | grep java | grep -v grep | awk '{print $1}'| xargs)
====
    PIDS=$(ps ax | grep ' kafka\.Kafka ' | grep java | grep -v grep | awk '{print $1}')
    PIDS_SUPPORT=$(ps ax | grep -i 'io\.confluent\.support\.metrics\.SupportedKafka' | grep java | grep -v grep | awk '{print $1}')
>>>>

Thanks, @mjsax .  The kafka-server-stop.sh conflict resolution LGTM.
It seems you resolved the other conflicts related to the version bump in favor of this repo, not changing anything.  Do we want to include the version bump in this PR (similar to https://github.com/confluentinc/kafka/pull/979), or is the intention to do it separately?

Thanks @rondagostino -- that's right. My understanding is that a version bump on master would happen independently. \cc @ijuma to confirm

Seems we don't have a 3.7 branch yet -- guess the version bump on master should only happen when we get 3.7 branch? i am not familiar with the process who/when 3.7 will/should be created. I assume, it will be part of CP 7.7 release (we are still working on 7.6 release right now).


What is the relationship between verifiable presentations and combined format for presentation?

My  expectation was that the SD-JWT's combined format for presentation would be used inside a verifiable presentation. Something similar to the example below
{
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "https://www.w3.org/2018/credentials/examples/v1"
  ],
  "id": "urn:uuid:3978344f-8596-4c3a-a978-8fcaba3903c5",
  "type": ["VerifiablePresentation"],
  "verifiableCredential": [{
    "type": "SD-JWT Presentation",
    "combinedFormat": "XXX.XXX.XXX~YYY~ZZZ"
  }]
}

I'm curious whether this was considered. If so, it would be nice to add a section on that to the spec on the relationship.

This spec defines its own format for verifiable presentations without a focus on being compatible to the W3C format. It may be possible to envelope the presentation format as shown in your example, but that would not be defined by this specification.

Duplicate of #113


cmd/bridge: Remove --headers.trusted-hash flag for bridge node

This PR removes the headers.trusted-hash flag from bridge node options.

However, this will close a manual pruning hack for bridge node runners. It is arguable we if we should allow it or not for Bridges and Fulls cc @renaynay @adlerjohn


Keyboard interrupt ^C does not halt processing

I was running one of the examples on my laptop, and got super boooooored, but ctrl-C just raises some kind of caught exception and leaves a pile of Python processes running.
Are you by any chance catching all exceptions, including KeyboardInterrupt? Because that's not really the way I would like ctrl-C to work, as it turns out. 😃

BTW, I had to eventually kill -9 the root Python process.

No this is a consequence of the multiprocessing library that is being used. Likely you hit ctrl-C while multiple processes were working. My understanding of the behavior you are seeing is that the master process stays open until every other process finishes its task so that it can close them and not leave zombie workers.
If you see this behavior using -max_workers 1, then I might be wrong, but I can assure you that I am not catching all exceptions anywhere. (With the exception of a one time gathering command line args which only happens once, and is not expected to stick around as mentioned in #54 and #46 )

Maybe you could catch KeyboardInterrupt then, and use it to gracefully shut down the workers?

That seems reasonable. I will look into that.

This issue was related to multiprocessing, which has been removed from pyshgp. Closing this issue.


support for angular 2.0.0-rc.0 and later

With the release of angular 2.0.0-rc.0 all of the angular packages have been renamed. This causes problems with ng2-idle.

alpha.5 that I just released a few hours ago addresses this.


Fix manage_home on AIX

Fixes: #6092
cc @chef/maintainers

still need to find a way to nuke codecov...


cannot load libspotify_embedded_shared.so

Running main.py results in missing spotify_embedded_shared.so library. Exact output:
python main.py
Traceback (most recent call last):
File "main.py", line 8, in
from connect_ffi import ffi, lib
File "/home/pi/spotify/spotify-connect-web/connect_ffi.py", line 19, in
libraries=[str('spotify_embedded_shared')])
File "/usr/local/lib/python2.7/dist-packages/cffi/api.py", line 405, in verify
lib = self.verifier.load_library()
File "/usr/local/lib/python2.7/dist-packages/cffi/verifier.py", line 101, in load_library
return self._load_library()
File "/usr/local/lib/python2.7/dist-packages/cffi/verifier.py", line 211, in _load_library
return self._vengine.load_library()
File "/usr/local/lib/python2.7/dist-packages/cffi/vengine_cpy.py", line 155, in load_library
raise ffiplatform.VerificationError(error)
cffi.ffiplatform.VerificationError: importing '/home/pi/spotify/spotify-connect-web/_cffi__x8b237976x2c265354.so': libspotify_embedded_shared.so: cannot open shared object file: No such file or directory
I can confirm that library is in the same directory as main.py and  I also tried symlinking to /usr/lib and /usr/local/lib which didn't change anything.
I am running on Raspberry Pi2, and strange enough given docker image works as it's supposed. On the docker image libspotify_embedded_shared.so is placed in /usr/lib directory which I already tried without any luck.
Any suggestions how to get it working without docker?

I've got the same problem with RPI B+ and RPI2
With the chroot version,
And has anyone managed to use a software mixer with it ?

@insanebits make sure you're using the armhf version of the library if you're using it outside of an chroot
@balbuze rpi b+ requires the chroot/docker version, and to use it without chroot/docker on rpi 2, you need to use the armhf version, and software mixer stuff is being discussed in #11

Hello,
thank a lot for the answers.
On my RPI2 I, to use it without chroot or docker, I have put  libspotify_embedded_shared.so (armhf version) in same folder than python script.
Now I've got a other message
.//libspotify_embedded_shared.so: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
Traceback (most recent call last):
File "main.py", line 8, in
from connect_ffi import ffi, lib
File "/root/connect/connect_ffi.py", line 19, in
libraries=[str('spotify_embedded_shared')])
File "/usr/lib/python2.7/dist-packages/cffi/api.py", line 340, in verify
lib = self.verifier.load_library()
File "/usr/lib/python2.7/dist-packages/cffi/verifier.py", line 74, in load_library
self._compile_module()
File "/usr/lib/python2.7/dist-packages/cffi/verifier.py", line 139, in _compile_module
outputfilename = ffiplatform.compile(tmpdir, self.get_extension())
File "/usr/lib/python2.7/dist-packages/cffi/ffiplatform.py", line 25, in compile
outputfilename = _build(tmpdir, ext)
File "/usr/lib/python2.7/dist-packages/cffi/ffiplatform.py", line 51, in _build
raise VerificationError('%s: %s' % (e.class.name, e))
cffi.ffiplatform.VerificationError: LinkError: command 'arm-linux-gnueabihf-gcc' failed with exit status 1
Any idea ?

Look in #11, answer is in my post.

I'm gonna close this for now, feel free to re-open if you're still having problems

This was important stuff! Why isn't this on the readme?  Please add the fact that the armhf version of the lib is needed, it would be much clearer!
Thanks,
Rafa.


zk: implement ZkList command

Surfaces the zk.list LSP command in the same way as zk.new and zk.index.

Thanks for the review


text_on_image Creator - Web design #70

https://images01.nicepagecdn.com/page/49/35/html-template-4935607.jpg Design a text_on_image like the above image
Create a file "text_on_image_NUM_by_(YourName).html" in the modules/text_on_image folder.
Use simple HTML and CSS and JAVASCRIPT to create the text_on_image animation. You can use the interface development https://kwickerhub.com/ (This project) or you can write the lines of code yourself.
Step by Step Guide.
Fork this project(Use the 'fork' button in the top right corner) and Clone your Fork.
git clone https://github.com/YOUR_USERNAME/frontend
Open your code Editor and Create a file "text_on_image_NUM_YOUR_NAME_.html" in the "modules/text_on_image" folder of this project you just cloned. No need to create head, title and body tags, Just Add a div tag with some embedded style(i.e use the style tag) and the script tag where necessary.
If you want to add an image resource, please add it in the folder ••
"modules/text_on_image/images_and_icons"
We recommend you use an svg for your image/icon.
Push your Code: You need to push your recent changes back to the cloud. Use the command below in the main directory of this Repository
git push origin dev
or use a GUI tool to avoid mistakes or complexity. LOL.
Then make you Pull Request...
Below is a example of the code structure we need:
<div>
    <!---YOUR CODE---->
</div>

<style>
    /* YOUR STYLE */
</style>

<script>
    // YOUR SCRIPT if any
</script>

The goal of this issue is to create modules that other people/dev/designers can use or easily import into their projects. Avoid the desire to style all elements in the page by using codes like:
<style>

*{

}
/* OR */

div, a, h1, pre{

}

</style>

use classes or id to style the elements to avoid a collision of styles.
Remember to make your module usable across different screens(Make your design responsive).
For more examples:
modules->buttons
modules->cards
for examples of contributions or Pull request accepted in to the project.
And please do not wait for this issue to be assigned to you as we have limited hands but have a lot to do/cover. Please send in your PR.
Good-luck and thank you.

Hey @NtemKenyor I am working on this issue.

I am interested in it. I have started working on it.

i have finished the task and this is my PR: https://github.com/KwickerHub/WebCraftifyAI/pull/893


update charts parameters and docs

Codecov Report

Merging #220 (e3cc9f8) into main (6b32da4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #220   +/-   ##
=======================================
  Coverage   97.25%   97.25%
=======================================
  Files          47       47
  Lines        2408     2408
=======================================
  Hits         2342     2342
  Misses         39       39
  Partials       27       27

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 6b32da4...e3cc9f8. Read the comment docs.


Update sbt-wartremover, wartremover to 3.0.12

About this PR
📦 Updates

org.wartremover:sbt-wartremover
org.wartremover:wartremover

from 3.0.11 to 3.0.12
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.wartremover" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.wartremover" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #210.


Input the volume increment

Before opening the issue, have you...?

[X] Searched for existing issues

Is your feature request related to a problem? Please describe
On my LG monitor the default OSD scale for volume is 6 which is too high.
Selecting fine control checkbox makes it 1, which is too low.
Describe the solution you'd like
It would be nice to have it as a number/multiplier field/slider to have fine adjustment and make it just right!
Describe alternatives you've considered
There isn't really any alternative that I'm aware of, please let me know if there is a config file I can use to achieve this
Anything else?
No response

Hi, you can change the DDC volume control range under advanced settings for the display. Try to change the default 0-100 to something else so the range is clipped.


docker-compose: fix grafana-agent path

Description
The path has changed upstream to /bin/grafana-agent
Fixes
Fixes running the demo application and other uses of the docker-compose environment
Checklist

[x] Tests added
[x] Changelog updated
[x] Documentation updated

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


excludes command parameter from token

Changes proposed in this PR

excludes command parameter from token

Why are we making these changes?
Avoid command in token tests unless needed.

Will merge when green


refactor: cookieParser.ts to be safer and simpler

Description
I found a more simple and less null ptr exceptions way to write cookieParser.ts's cookieParser method in 2 lines. It turns out that there was no null handling when checking for whether the data was actually returned from a different system.
Related Issue

Motivation and Context
This is better code for Prestashop and more flexible for Moqui.
How Has This Been Tested?
Running yarn dev, and going through the process of submitting an order, getting information and looking at the logs.
Looks like there aren't any tests already after running yarn test.
Screenshots (if appropriate):
Types of changes

[x ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x ] All new and existing tests passed.

@acetousk thanks for your contribution, your NPE check is okay, however there is a prestashop-specific consideration that I explain it in the code.

@acetousk thanks for your contribution, your NPE check is okay, however there is a prestashop-specific consideration about cookies that should be taken into account.
first let me explain how prestashop works with cookies. Actually prestashop generates many cookies in different situations. First when we call any of the APIs it generates a cookie for that session - to keep track of that guest user. Once the guest user tries to register prestashop generates another cookie, to keep track of the logged in user (now customer). Add to cart and other endpoints should be called with that second cookie. So, we should always use the last generated cookie for the future API calls.
That's why I looped over the cookie array and got the last element (we know that all prestashop cookies have PrestaShop word).


Invalid class “ShortReadQ” object: sread() and id() length mismatch

Hi,
I encountered the following error message when trying to run UMIc:

Could you suggest a way to troubleshoot? Thanks!

Thanks for your prompt reply, Nikos!
There are 439 reads in the file and it's zipped.

Hmm, I’m having trouble understanding the exact error causing the issue. It’s also quite odd that, despite having 439 reads, you’re getting 830/831. Do you believe it would be possible to provide us with an example file you're trying to run, or perhaps a subset of it?
I should also mention that UMIc started as a side project by a former colleague of mine. In its current form, UMIc operates as a collection of R scripts and has a few bugs that we need to address. We are, however, planning to develop it into a stand-alone R package to make it more robust and user-friendly.

What would be the best way to send you the file? It's about 400 KB in size. Thanks!

The file seems small, so feel free to email it to us at<EMAIL_ADDRESS>If it's too large for email, you can send a WeTransfer link instead.
Thank you in advance!

Thank you! Just sent you an email with the fastq file attached. Here's a dropbox link just in case: https://www.dropbox.com/scl/fi/mtf114rz39z2fkpc3gap5/output_1.fastq.gz?rlkey=v3d4x957ebhw6njknz42tpw4n&st=8zj18by9&dl=0

Hi again,
We have received the .fastq.gz file and I have already managed to run UMIc on your sequences.
As I previously mentioned, at the moment, UMIc runs as a collection of R scripts. That means that the user has to manually edit some of its input parameters (you will be able to find/edit these in UMIsProject.R script).
Following this, below are the input parameters I used for your sequences:
########## Inputs ##########

#type of data - paired or single
pairedData <- FALSE

#UMI located in Read1 --> "R1"
#UMI located in Read1 and Read2 --> "R1 & R2"
UMIlocation <- "R1"

#length of the UMI
UMIlength <- 12 #5

#length of th sequence
sequenceLength <- 22

#min read counts per UMI, for initial data cleaning
countsCutoff <- 5

#max UMI distance for UMI merging
UMIdistance <- 1

#max sequence distance for UMI correction
sequenceDistance <- 3

#inputs folder / working directory
inputsFolder <- "path/to/your/fastq/"

#outputs folder
outputsFolder <- "output/folder/"

The tool produced the output files in the specified output folder.
Nikos

Thanks for your reply. We have 8 bp UMIs and the bases after the UMIs are constant.
Here are my parameters:
#type of data - paired or single
pairedData <- FALSE

#UMI located in Read1 --> "R1"
#UMI located in Read1 and Read2 --> "R1 & R2"
UMIlocation <- "R1"

#length of the UMI
UMIlength <- 8 #5

#length of th sequence
sequenceLength <- 22

#min read counts per UMI, for initial data cleaning
countsCutoff <- 1

#max UMI distance for UMI merging
UMIdistance <- 2

#max sequence distance for UMI correction
sequenceDistance <- 2

Hi @HaiqiChenLab,
Apologies for the delayed response!
We identified a bug while working with your .fastq file, but we have resolved the issue. I have tested and processed your sample successfully. Could you please confirm if everything is running smoothly on your end as well?
Nikos

Closing this issue for now; we can reopen it if necessary.


New launch instructions for V3

I tried to launch opensource V3 version but newer TensorFlow isn't compatible with V3's code. So I have created requirements.txt which lists best compatible versions for the project (all libraries are just before last commit - November, 2018).
Also I have changed port so server could be run from venv without root rights (to bind to 80 port)

It would be great to have this merged, I also struggled a bit with instantiating proper versions.


In the extension "Hiero", unable to generate specific font if the font name ends with "Bold" or number, etc.

According to the code and the document of java.awt.Font.decode(String str) :
https://github.com/libgdx/libgdx/blob/1ba527c9968a2fa8ec022a64ac2dcce6574ee8dd/extensions/gdx-tools/src/com/badlogic/gdx/tools/hiero/Hiero.java#L298
If a font name ends with "plain", "bold", "italic", "bolditalic", or number, it will not be able to parse correctly. For example, "Bauhaus 93" is recognized as a font named "Bauhaus" and pointsize is 93.
To solve the problem, the str in Font.decode(String str) should end with -PLAIN-12. ("plain" is the default style and "12" is the default pointsize)
The modification code is below:
Line 298: unicodeFont = new UnicodeFont(Font.decode(String.format("%s-PLAIN-12", fontList.getSelectedValue())), fontSize, boldCheckBox.isSelected(),

I sent a PR 10 days ago that fixes this. It is an extremely easy PR to review for anyone who has read this issue. Guess what? No one has reviewed or even commented on it! Hooray! In short, use AngelCode BMFont in most cases, or in some specific cases FontWriter (mainly for distance field fonts or TextraTypist; it uses different code to load in plain libGDX, which may move into its own library soon). It just seems like Hiero is unmaintainable if simple fixes get ignored, so you might as well use software that works.


Not working on MacOS

[X] I am using the [latest SDK version]
[X] This API is compatible with my vCenter version
[X] I have searched [existing issues]

Environment

sdk package version:
nsx-vmc-aws-integration-python-sdk     <IP_ADDRESS>.1.15419398
nsx-vmc-policy-python-sdk              <IP_ADDRESS>.1.15419398
pyobjc-framework-DictionaryServices    2.5.1
pyobjc-framework-EventKit              2.5.1
pyobjc-framework-FSEvents              2.5.1
pyobjc-framework-LaunchServices        2.5.1
pyobjc-framework-ScreenSaver           2.5.1
pyobjc-framework-ServiceManagement     2.5.1
pyobjc-framework-SyncServices          2.5.1
pyvmomi                                7.0
vapi-client-bindings                   3.3.0
vapi-common-client                     2.15.0
vapi-runtime                           2.15.0
vmc-client-bindings                    1.24.0
vmc-draas-client-bindings              1.5.0
vSphere-Automation-SDK                 1.25.0

python version: Python 2.7.16

vSphere version: 7.0

Operating System/Shell (used to run SDK-based apps):
MacOS 10.15.4/zsh

Steps or code snippet to reproduce
ansible-inventory --list -i .vmware.yaml
Actual behavior
[WARNING]:  * Failed to parse /Users/az/.ansible/.vmware.yaml with vmware_vm_inventory plugin: Please install "PyVmomi" Python module as this is required for VMware Guest dynamic inventory plugin.
[WARNING]: Unable to parse /Users/az/.ansible/.vmware.yaml as an inventory source
[WARNING]: No inventory was parsed, only implicit localhost is available
Expected behavior

Hi @UAnton
Can you describe what is the problem with Automation SDK here?
Or perhaps consider raising an issue on https://github.com/ansible-collections/vmware if it is Ansible issue.

FYI: https://github.com/ansible-collections/vmware/blob/master/requirements.txt

Thanks

@UAnton
https://github.com/ansible-collections/vmware/issues/154
This might be relevant to you.


Known Issues

As I am the sole maintainer of this, there are some issues that pop up that either can't be fixed or can't be easily fixed. Here is a list of all of these:

Potion count can be inaccurate (and even negative) if Entropic Brew and/or Alchemize is involved. There is no way to fix this, as the data is not present in the run files. I've pinged modargo (creator of the RunHistoryPlus mod) to add the relevant fields. If and when these new fields arrive, only the new runs will be correct. Older runs will continue to be wrong.
Literally anything pertaining to web design. I am not a web designer; my knowledge of HTML is limited at best, and my CSS/JavaScript knowledge is nonexistent. All pages are auto-generated using Jinja2 templates (see the Templates folder); any changes should be made there. UI and appearance is very low on my to-do list; feel free to contribute.

I will add more items to this post as I find new issues that I cannot resolve, or that would be too long and thus not prioritized.

Testing webhook

Something I noticed while watching a recent run was that potions are going above the expected value, but it doesn't look like Entropic Brew or Alchemize was there. At first i thought it had something to do with going to a shop (as you can see, it says Baalor had 4 potions on floor 54) but that wouldn't be consistent with it showing 3 for floors 45 through 49.
https://baalorlord.tv/runs/1658440304

For the above: not currently considering discarded potions in the potion delta.
Also, timers are broken. I haven't had time to look into them.

Discarded potions are now properly calculated in potion delta. Timers should be fixed, too, though I can't test that locally yet as it requires a live channel.

Work on potion gains and other meta-gains during and outside combat has started at https://github.com/modargo/RunHistoryPlus/pull/3 - thanks Nekaida for working on this! When this arrives (whenever that is), then I'll be able to fix the potion count issue and a few more things!

All of these issues have either been fixed, or have their own dedicated issues. Closing this.


Incubation: negative values issues

The following fields shouldn't be able to go negative:
pH
duration
repeats

ready for review and merge on pull request #47


Mention SpecAugment in doc

📚 Documentation
TimeStretch, TimeMasking and FrequencyMasking are implementation of SpecAugment, but it is not immediately clear from the documentation.
We can add

Reference to the paper
Add example images

Note: when adding images to documentation, we need to make sure that

documentation is still comprehensive without the image
the colormap is friendly to the people with color vision deficiencies. (viridis should do)

@mthrok I would like to work on this.

Thanks @krishnakalyan3. Let me know if you need help.


User request: study stats

It would be nice if you could see the statistics for a study, for example the total number of moves, time since created, etc...

It could work in general, too. Like counting the number of moves in a PGN in Analysis board.
lichess.analysis.study.data contains (amongst other things):

likes
createdAt
secondsSinceUpdate

Unfortunately, this doesn't apply to the study list because there are no useful APIs for getting this information. If a study is private, it will say it's private even if you are a contributor. One option is to execute a call at https://lichess.org/study/{studyId} and parse the included JSON, but it seems wasteful to do that for each study on a page.

Issue added to lichess for a more suitable API: https://github.com/lichess-org/lila/issues/14563

Still waiting for any comment on the study API request.


Can't customize max-width

I'm not entirely sure if this is a bug, although I doubt I'm doing something wrong since it's so simple.
module.exports = {
  theme: {
    maxWidth: {
     'max-w-7xl': '80rem',
    }
  }
}

This is the same example given on this page
I know my tailwind.config.js works because I successfully already added breakpoints.
Is this my mistake or is this a bug?

You shouldn't prefix width's name:
maxWidth: {
  '7xl': '80rem',
}

Ah oops, sorry about that.
Thank you for the help.


Unable to create layer for LottieAnimationView (HUAWEI)

Description
Crashing app with 'Unable to create layer for LottieAnimationView' Error
Steps to Reproduce

On HUAWEI device honor 6x
Android version is 7

Expected behavior:
Actual behavior:
Versions
My current lottie-react-native version is "3.3.2"
I think it's only happen on some specific devices.
Similar issue is opened in lottie-android github here. But I couldn't figure out to solve.
https://github.com/airbnb/lottie-android/issues/1387
Error log is like this
Fatal Exception: java.lang.IllegalStateException: Unable to create layer for LottieAnimationView, see logcat for more info
       at android.os.MessageQueue.nativePollOnce(MessageQueue.java)
       at android.os.MessageQueue.next(MessageQueue.java:356)
       at android.os.Looper.loop(Looper.java:138)
       at android.app.ActivityThread.main(ActivityThread.java:6517)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:942)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:832)

Anyone has fixed this problem?

Same issue for me

Same issue for me

Same issue, we've got 57 crashes affecting 38 users in the past 7 days,
55% samsung, 16% Sony.
75% Android 5, 25% Android 9


Update Configure-Additional-Authentication-Methods-for-AD-FS.md

Hi,
I have added miniOrange as an additional authentication method for AD FS. Kindly review and merge the changes.
Thanks,
Urvesh Patel

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

@billmath Hi, Bill.
Could you please provide an update on when the PR would be merged?
Thanks,
Urvesh Patel


Added missing azure-tenant-id secret to databricks

Found azure-tenant-id was expected in pipeline code, but missing from databricks secrets. This adds it in.

/test

:robot: pr-bot :robot:
:runner: Running tests: https://github.com/UCLH-Foundry/FlowEHR/actions/runs/6260489355 (with refid a1e90952)
(in response to this comment from @damoodamoo)

/test

:robot: pr-bot :robot:
:runner: Running tests: https://github.com/UCLH-Foundry/FlowEHR/actions/runs/6273489000 (with refid a1e90952)
(in response to this comment from @jjgriff93)

Confused. Why do we need this? Why can’t we just add the secret through the config, same way as cognitive services key is added in?

:robot: pr-bot :robot:
:runner: Running tests: https://github.com/UCLH-Foundry/FlowEHR/actions/runs/6417061708 (with refid a1e90952)
(in response to this comment from @jjgriff93)


R.2.1. - Add grouping to the leaderboard

Requirement 2.1 - Leader board grouping
The leader board currently shows the ranking of all participants in the system. We want to add a feature where the leader board can be filtered to show particular groups of participants

End of semester