apply.sh issue

I use ArchLinux to run the apply.sh
other script work fine
it showed  this
I follow the video and stuck in this segment

Try not running the script as root but being a regular user and using sudo. If your distro doesn't have sudo try installing it (you can remove it after)

I used your method, but the problem persists. I've determined that it's a mount problem

so, did you fix it? how?
I am using ArchLinux too and facing same problem no setting Applying SELinux security contexts to directories

Try not running the script as root but being a regular user and using sudo. If your distro doesn't have sudo try installing it (you can remove it after)

I used your method, but the problem persists. I've determined that it's a mount problem

so, did you fix it? how? I am using ArchLinux too and facing same problem on Applying SELinux security contexts to directories

Try not running the script as root but being a regular user and using sudo. If your distro doesn't have sudo try installing it (you can remove it after)

I used your method, but the problem persists. I've determined that it's a mount problem

so, did you fix it? how? I am using ArchLinux too and facing same problem on Applying SELinux security contexts to directories

I didin't fix it. I took turns using ArchLinux and Ubuntu. Four script were successfully run in this way


fix(loading): ensure loading overlay stays above components

Fixes https://github.com/carbon-design-system/carbon-components/issues/403

👍 ✅


Enable for use with GitHub enterprise

Pull request to resolve issue "Custom github url not supported #144"
I removed hard-coded github.com endpoints. With the proposed changes oauth2_proxy works with enterprise github if user sets validateURL (as well as loginURL and redeemURL) to github enterprise endpoint.

These changes look nice and minimal. I'm not the one who decides if this is merged, but I think there are two small steps you need to take before this is merged:

you changed the tab before the comment // https://developer.github.com/v3/orgs/#list-your-organizations to spaces, change it back to tab
squash all these commits down into one commit (with an "interactive rebase")

Closing this to sort out the interactive rebase.

@ruta-goomba  did you ever do the rebase?


code release

Hello,
I am very interested in your impressive research. Could you please let me know when you plan to make your code available? Thank you!

Thank you for your interest!
I think it'll probably take a week or two.

Looking forward to the code release. Thank you!

@ByeongHyunPak 3weeks past， could you please share your code to the community? we are all waiting for your code
haha

We sincerely apologize for the delay in releasing the code. We're in the process of updating our packages to the latest versions (e.g., xformers for memory efficiency, and the latest versions of mmcv and mmseg). Unfortunately, we’re still encountering a few issues that we’re working hard to resolve. 😥 We'll release the code as soon as possible with minimal required actions on your part. Please bear with us a little longer.

@ByeongHyunPak Hi another 2 weeks past, could you please provide your code for us as a reference?

Sorry to keep you waiting. We've finished the process for code release. We're currently transferring the code from our internal server to the outside. You should be able to access the code tonight or tomorrow.


no internet after sleep wake

I had no issue before the 10.15.5 and 0.5.9,
but I can't get any internet connection after the sleep-wake.
I'm using the same motherboard b450-i Strix and the onboard LAN.
Does anybody have any info on this issue?

Just out of interest, what CPU are you using? Sleep doesn't work for me at all so not sure I can really help with fixing this 😓

https://wccftech.com/fix-internet-not-working-after-waking-mac/
Hi guys,
For me the link above solved the problem. Now it works great :)


Builder uses TileDB-SOMA 1.0

If blocked by TileDB-SOMA 1.0, then API should use latest version by end of sprint.

Closed as dup of #87


Initial release

WIP

It seems to be structured / organized . However, it appears somewhat over-engineered for its current functionality. I would try to simplifying the current codebase, specially for error handling and logging that's way to verbose and needless to maintain.
While the code itself is highly modularized with all of these interfaces, the added value of that is minimal, there're no tests nor different implementations to start introducing the interfaces. We usually work from concrete types to the abstractions, not the other way around.
The scattered/extensive configurations can be also a cause of a trouble, at least make sure they're consolidated in the same place. Please streamline that
more notes on the error messages formatting

Lowercase Messages: use lowercase for error messages, except for proper nouns
No Punctuation:  omit trailing punctuation (periods, exclamation marks) in error messages. don't use failed, error, ..etc in the error it will very annoying when nested failed :... failed:... failed :....


[feature] [fix] Add covid information hero and little fixes at the icon component

Hey there 👋🏻,
I saw at the figma desing by @kevmodrome that there should be some covid related information about the events // event planning, so I created a hero component thats even reusable for other kind of actual message we want bring to the page visitors. If you are thinking that something could be made better or improved, please let me know.
Warning Hero

WarningHero.svelte component:

flexible Icon & content props
closable by the user

Icon

add two more icons:

virus (I customized the RemixDesignIcon a little bit)
closing cross

now the props width and height to control the icon size are working

preview

Hope I was able to resolve the issues. Thank you @geoffrich for giving me feedback 🙂

Hope I was able to resolve the issues. Thank you @geoffrich for giving me feedback 🙂


Use the STAC UML to populate missing fields

Relevant links:
https://github.com/radiantearth/stac-spec/blob/master/STAC-UML.pdf
https://github.com/radiantearth/stac-api-spec/tree/master/stac-spec
https://github.com/radiantearth/stac-api-spec/blob/master/stac-spec/overview.md
https://github.com/radiantearth/stac-api-spec/tree/master/item-search
https://github.com/radiantearth/stac-api-spec/tree/master/item-search#query-parameter-table

@bo-lu Some of the missing fields can be extracted from the collection level, and some missing fields are currently hardcoded for CCMEO data cube. Solutions for the missing fields are documented in this spreadsheet for review. Codes will be committed to the repo for review.

Codes are committed to the main brunch: https://github.com/Canadian-Geospatial-Platform/stac_to_geocore/commit/200c8994b01497493c4ef92f74904d43eac22230

main brunch: sounds tasty ;)


iframe is allowed by default, but should it be?

Apologies if this is outside of the goals of the default tags allowed, but I was surprised to see iframe in the list. Doesn't that carry an unacceptable amount of risk with it? Thanks!

I'm not going to remove it in the current major release because it would break someone's production code, but I think we should remove it for the next — as it currently stands the configuration does not make much sense because iframe is allowed, but src is not allowed for iframe. Someone is relying on iframe being allowed, though, and just enabling src to move on to the next step, and we don't get to break their code in the 1.x series.
I am going to tag this 2.x.

Thanks @boutell. Great point about src not being allowed by default...that certainly helps.

iframe dont alow fullscreen even by define it


Add Implementors and References as properties of the models?

As done in matminer should we add implementors and references as properties of the models?

Good idea.


scaffolder-backend: replace all usage and prevent new usage of path.resolve

Modifying the lint rules and switching out all existing usages of path.resolve in the scaffolder backend, as it is particularly likely to lead to insecure code.
The reasoning for leaving path.join intact is that it's typically not what you'd reach for when computing output paths, and we do still need some way to join together paths :grin:

Nice work!

Maybe we should update the eslint config in the scaffolder-modules too. Like cookiecutter and rails have occurences I think?


fix crash on running into archived channels which are not joinable

Hey @troy-f
Can you find evidence supporting the fact that you Cannot join archived channels at all?
I think that sometimes you're actually able to join despite them being archived.
Therefore I would suggest adding try...except on the join channel method for each channel so we join whatever we can, and when we can't it won't raise.
What do you think?
By the way are you on Discord? let's chat.
https://discord.gg/wMFstnWp

only a workspace owner can change settings to allow themselves to join an archived channel (meaning, temporarily un-archive it), you would need to have a whole lot more permissions for the bot to do that. for the moment this is the best solution until the error handling and configurability of data source plugins is made better.


Error Installing on Win 7 with Python 3

From<EMAIL_ADDRESS>on 2013-02-03T21:51:12Z
Installing Spyder 2.1.13 having Python 3.3 on Win 7 Pro with the latest SP
I have Python 2.7 previously deleted, but Spyder finds it in Registry.
What steps will reproduce the problem?

Start installing Spyder 2.1.13
The installation progresses until
On Postinstall script finishes with error ImportError: No module named 'builtin'

Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1246

From ccordoba12 on 2013-02-04T15:31:37Z
2.1.13 is not working with Python 3.3. You need to download the latest repo, here: http://v21.spyderlib.googlecode.com/archive/bfc9c25d6359babdbf0bc47f3170d1eff70a9adf.zip and then run (after uncompress it):
python setup.py install
Please note that our port to Python 3 is still experimental but should be working by now. Let us know if that version works for you so we can close this issue.
Summary: Error Installing on Win 7 with Python 3  <span class="oldvalue"> (was: Error Installing on Win 7 Pro - ImportError: No module named 'builtin') </span>
Labels: MS-v2.1

From<EMAIL_ADDRESS>on 2013-02-18T13:33:53Z
i have the same error and your link is broken.

From pierre.raybaut on 2013-02-19T07:21:07Z
Please try v2.1.14 from here: https://code.google.com/p/spyderlib/source/checkout?repo=v21

From<EMAIL_ADDRESS>on 2013-04-14T06:30:57Z
I have Python 3.3.1 using Win7 Pro:

Start installing Spyder <IP_ADDRESS>
The installation progresses until
On Postinstall script finishes with error ImportError: No module named 'builtin'

From<EMAIL_ADDRESS>on 2013-04-04T09:22:00Z
python setup.py install gives:
Traceback (most recent call last):
File "setup.py", line 16, in <module>
from sphinx import setup_command
ImportError: No module named 'sphinx'

From<EMAIL_ADDRESS>on 2013-04-17T22:22:01Z
I having same issues as #5
I have Python 3.3.1 using Win8 Pro:

Start installing Spyder <IP_ADDRESS>
The installation progresses until
On Postinstall script finishes with error ImportError: No module named 'builtin'

From<EMAIL_ADDRESS>on 2013-04-18T06:35:18Z
Somme troubles that #4 , #5 , #6 and i try yours new lib

From<EMAIL_ADDRESS>on 2013-04-23T09:34:38Z
Same trouble as number 4.

From ccordoba12 on 2013-04-23T10:02:59Z
Please, please don't insist on trying to install Spyder <IP_ADDRESS> or 2.2rc in Python 3. They won't work(!) neither with Python 3.3 nor 3.2.
I know we announced support for Python 3 since January but we haven't made an official release with the new code yet. Sorry for the big confusion but we didn't think we could take so much time to release 2.2, and official Py3 support was planned after that.
If you really want to try our Py3 support right now, please use mercurial to download the new code from the link Pierre mentioned in comment #3.
Now, about the sphinx error some of you are seeing: if you have both python 2 and 3, you have to install sphinx for both versions. You probably installed it for version 2 but not for 3 and that's why the error appears.

From<EMAIL_ADDRESS>on 2013-04-23T10:01:56Z
Can we disable the dependency on Sphinx for 2.2?  I never noticed it as part of 2.1.  It is a MESS.  It brings pygments, docutils, and jinja2--and the installation is still not done.  Given the horrible condition of pypi, any dependency on downloaded packages is fraught with problems.  Minimize dependencies; don't increase dependencies.  Maybe this is a clever feature, but make it entirely optional.  Happy to launch a website for help and docs.

From<EMAIL_ADDRESS>on 2013-04-23T10:05:00Z
No.  I am installing rc0 of 2.2 on Python 2.7.3.  I have no Python 3.x whatsoever.

From<EMAIL_ADDRESS>on 2013-04-23T10:06:26Z
pip install sphinx is stalled trying to get pyments 1.6 from poco.org.  WTF?

From ccordoba12 on 2013-04-23T10:08:56Z
@-lewis: the Sphinx dependency is entirely optional but we recommend it to get the best experience from our Object Inspector.
I think sphinx is required at buid time to install our documentation but unfortunately I don't know how to avoid it.

From pierre.raybaut on 2013-04-30T08:10:01Z
Status: Duplicate
Mergedinto: 944

From ccordoba12 on 2013-04-23T10:10:34Z
@-lewis: The Issue title clearly states that this is for Python 3, so please don't hijack it.


Dropdown items inside navbar is not working properly

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
I createad a navbar by the help of bootstrap and inside it i added a dropdown menu but when i am trying to access the dropdown item it is not opening.

                  UTKRISHT KRISHI                  <button class="navbar-toggler" type="button" data-bs-toggle="collapse" data-bs-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">                    </button>

                                                 Home

                                   Products

Fruit

Vegetable

Cereals

                     Featured

               About Us

               Contact Us

Attached the screenshot of my issue and also the code

Reduced test cases
Currently i did not have idea how to fix it
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
v5.1.0

Now my issue is resolved as i have some changes in my code and it start working.🔥


AttributeError: 'str' object has no attribute 'copy'

Hi Team,
I am facing issue while running post request using RequestLibrary
AttributeError: 'str' object has no attribute 'copy'
python version:3.10.11
robot framework version: 5.0.1
requests==2.23.0
Kindly suggest on this issue

Does the situation change with different Robot Framework versions? If not, then the problem is most likely in your data or in RequestLibrary. My guess is that you are passing a string to a place where a dictionary is expected. If you suspect that this issue is related to Robot Framework core, please provide more information about the problem. If you believe the issue in RequestLibrary, please submit an issue to its tracker. If you are just looking for help, please use our Slack or other support forums listed at robotframework.org. This issue tracker is only for bug reports and enhancement requests related to Robot Framework core.


gateway 3 not found

hello why on my list there isn't gateway 3?

installation it is ok:

It also does not work for me.
Using hassio on raspberry 4.
Installed addon via HACS
It worked fine when I was testing it on my PC - Home assistant on windows via docker

Browser cache


mod conflict

The mod Create completely bricks the mod and doesn't load the game. It would be nice to use these mods in tandem with each other.

Can you send the latest.log?

Please reopen with a log.


Redeploy demo/sandbox more quickly by only waiting for AMD64 Docker image to complete

Description
Small change to docker.yml to immediately redeploy demo/sandbox when the AMD64 image is built.  This allows us to redeploy without waiting on the ARM64 image (which can sometimes take an hour).

Ported to dspace-7_x in #2655


Add Navbar Component

Not sure if it's related to this PR or not, but do look into this. Carbon frame has a scroll as well as the outer container.

Not sure if it's related to this PR or not, but do look into this. Carbon frame has a scroll as well as the outer container.

That's a known issue @humzahasan, will be fixing it in a single PR.


"Error: Model not initialized: "Model" needs to be added to a Sequelize instance before "call" can be called."

Hello Typescript-Sequelize'rs,
This may be a noob question but I will try to explain as best I can. As you can see, I run into an error when trying to save data to my PostgreSQL database. I tried to reduce everything back to basics to trace the error, here's my situation.

I set up the sequelize connection to my DB:

const sequelize =  new Sequelize({
        database: dbconfig.database,
        dialect: dbconfig.dialect,
        username: dbconfig.username,
        password: dbconfig.password,
        host: dbconfig.host,
        port: dbconfig.port
});

I confirm that the connection is established using:

sequelize.databaseVersion().then((databaseVersion) => {
    console.log(databaseVersion);
} );

This gives me the correct version of my PostgreSQL DB (10.3 - Ubuntu)  as expected.

I created a Person.model.ts and added it to Sequelize using
sequelize.addModels([__dirname + '../models/person.model.ts']);
The person.model.ts is a copy of the model in your Wiki page.

I then try to create a new instance of the Person using,
const person = new Person({name: 'bob', age: 99});

When I try to run the code, I get the following error,

/home/mick/Documents/code/travelbudget/node_modules/sequelize-typescript/lib/models/BaseModel.js:64
                throw new ModelNotInitializedError_1.ModelNotInitializedError(model, { accessedPropertyKey: propertyKey });
                ^

Error: Model not initialized: "Model" needs to be added to a Sequelize instance before "call" can be called.
    at new ModelNotInitializedError (/home/mick/Documents/code/travelbudget/node_modules/sequelize-typescript/lib/models/errors/ModelNotInitializedError.js:18:16)
    at checkInitialization (/home/mick/Documents/code/travelbudget/node_modules/sequelize-typescript/lib/models/BaseModel.js:64:23)
    at Function._target.(anonymous function) [as call] (/home/mick/Documents/code/travelbudget/node_modules/sequelize-typescript/lib/models/BaseModel.js:34:21)
    at new Person (/home/mick/Documents/code/travelbudget/dist/out-tsc/models/person.model.js:26:28)
<snip>

I wasn't sure if the table needed to exist on my DB, so I created the Person table on the DB.

I then decided to try a different approach, and instead of using the person.model.ts, I created the table directly through Sequelize and added the data that way. This way worked as expected.
const myperson = sequelize.define('person', {
    name: {
      type: Sequelize.STRING
    },
    age: {
      type: Sequelize.REAL
    }
  });

myperson
    .sync({ force: true })
    .then(() => {
        console.log('Connection synced')
        return mycurrency.create({
            name: 'joe',
            age: '5'
        })
    })
    .catch(err => {
        console.log('err');
    });

My question is, what am I doing wrong that I cannot use the person.model.ts file to create and add new data?
Any help or directions would be greatly appreciated. Thanks!!

Hey @micklynch, you either need to pass the class reference, the path to the directory(not the actual file) or a glob.
So for example sequelize.addModels([Person]) should do the job :)

Thanks for the fast response @RobinBuschmann.
I tried the following:
import { Person } from '../models/person.model';
...
sequelize.addModels([Person]);
const person = new Person({name: 'bob', age: 99});

And I still get the error.
Here's my `Person.model.ts' file
import {Table, Column, Model, CreatedAt, UpdatedAt} from 'sequelize-typescript';

@Table
export class Person extends Model<Person> {

    constructor(name?: any, age?: any) {
        super(name, age);
        console.log(name);
      }

    @Column
  name: string;

  @Column
  age: number;

}

The constructor you're defined is wrong... see https://github.com/RobinBuschmann/sequelize-typescript/blob/master/lib/models/Model.d.ts#L39
But this is not the actual issue. Do you add the model and try to create the instance of Person in the same file?
For me it working perfectly well: I've created an example repo reflecting  what you've done: https://github.com/RobinBuschmann/st-366

An issue that I've seen very often is, that the model ist references correctly in one file and in another one the case sensitivity of the used path differs from the one where the model was added:
// index.ts
import {Person} from './person.model';
...
sequelize.addModels([Person]);

// usage.ts
import {Person} from './Person.model'; // <-- Please note capitalized Person here
new Person(...);

Node loads the file content again, so that:
// usage.ts
import {Person as CapitalizedPerson} from './Person.model'; // capital P
import {Person} from './person.model';

Person === CapitalizedPerson // false

Thanks a million Robin.
I think it was the constructor that was causing the issue. After I fixed that, I got another error that was related to my tsconfig.json. The repo you created for me was very helpful is sorting out that problem.
Cheers and keep up the great work!!

You're welcome :)
Then I'll close this issue now

Thx RobinBuschmann you save my day.
Changing the case in the import statement fix my issue.

@UrielCh Hi UrielCh,
Can I see your code as an example, I don't have wrong case in import statement but I still met this issue.

@UrielCh Hi UrielCh, Can I see your code as an example, I don't have wrong case in import statement but I still met this issue.

In the case of the project I was working on, I initialized it here.
It was what was missing

import statement but I still met this issue.

... I do not remember which project had the issue ... sorry.

I had the same issue, I fixed it by initializing all the models by sequelize.add([Models]) in the index of service folder by self executing function.


chore: Adds tests to cover #101

@cibernox I believe this will cover your change

Makes sense. Can you publish a new release?


Documentation improvement

Is there an existing issue for this?

[x] I have searched the existing issues

Current Behavior
I ran into some issues to run Yace locally using docker command in the document and they took me some time to solve.

Couldn't read /tmp/config.yml: open /tmp/config.yml: permission denied
EnvAccessKeyNotFound: failed to find credentials in the environment

Solutions:

add the option --user "$(id -u):$(id -g)" in the docker run command
use the options in the docker run command instead of the bind mount of the credentials file
-e AWS_ACCESS_KEY_ID='' -e AWS_SECRET_ACCESS_KEY='' -e AWS_DEFAULT_REGION=''

Expected Behavior
Add these error cases and solutions in the docker run section in the document or may update the docker command if these are common cases.
Steps To Reproduce
No response
Anything else?
Accidentally labeled this as a Bug. It seems not able to be removed. Please help remove the bug label.

Closing this as it seems to refer to a really old version of yace. If you can still reproduce the issue with the latest realease please feel free to reopen.


The image is not visible on the website if we add it inside TypedTableBlock.

Issue Summary
We are facing the issue when we have added the image inside the TypedTableBlock. The image is not visible in the preview, and it is also not visible on the frontend.
Below is the HTML tag stored in the Wagtail database. There are no image tags, and no image URL is present inside the wagtail.
embed alt="Test" embedtype="image" format="center" id="11***"
Steps to Reproduce

Start a new project with wagtail start myproject
Create a StreamField with TypedTableBlock as one of the option.
In TypedTableBlock use RichTextBlock as one of the option.
Go to wagtail, and add the image inside the TypedTableBlock section.
Check in the preview you will not able to see the image inside the table. Same for the frontend side also.

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: (yes)

Technical details

Python version: 3.10.10.
Django version: 3.2.19
Wagtail version: 4.2.4
Browser version: Chrome 116

Hi @krishav43 - thanks for the report. However, I'm unable to replicate this as described. Starting from a fresh Wagtail 4.2.4 instance, I added "wagtail.contrib.typed_table_block", to INSTALLED_APPS, edited home/models.py to:
from django.db import models

from wagtail.models import Page
from wagtail.fields import StreamField
from wagtail.admin.panels import FieldPanel
from wagtail import blocks
from wagtail.contrib.typed_table_block.blocks import TypedTableBlock

class HomePage(Page):
    body = StreamField([
        ('table', TypedTableBlock([
            ('text', blocks.RichTextBlock()),
        ])),
    ], blank=True, null=True, use_json_field=True)

    content_panels = Page.content_panels + [
        FieldPanel('body'),
    ]

and home/templates/home/home_page.html to:
{% extends "base.html" %}
{% load static wagtailcore_tags %}

{% block body_class %}template-homepage{% endblock %}

{% block extra_css %}{% endblock extra_css %}

{% block content %}

{% include_block page.body %}

{% endblock content %}

I then created a table containing an image:

and this displayed correctly in preview and on the live page:

If you can provide more detailed steps that replicate the issue, I'll be happy to reopen and investigate further. Note that the <embed> tag in the database content is expected - see https://docs.wagtail.org/en/stable/extending/rich_text_internals.html#data-format.


git clone with --recurse-submodules

When git added some submodules, docker build will failed due to submodules' code is missing.

When git added some submodules, docker build will failed due to submodules' code is missing.

I don't know why this CI test all failed

Fixed the tests in https://github.com/basecamp/kamal/commit/9ccfe20b107cec85aca8f37834cf7c66add972c3

It's strange that you added more than one submodules but only one is required. Whatever, you can try pre-build hook to remove unnecessary submodules


Utilize state from Ironic to determine if BMC credentials are valid

So far a BareMetalHost will reflect an error if BMC credentials are not set.  Once those credentials are set in Ironic, we can use the state of the ironic node to determine if the BMC credentials are valid.  We know the credentials are valid when the bare metal node moves to the "manageable" state.
https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/node_states.html

#48 implemented this


chore: update plugin to Warp 2

BREAKING CHANGE: now replaces warp-css with Warp 2 contents

Should we perhaps take in uno or presetWarp as input to the plugin instead of bringing our own?

Should we perhaps take in uno or presetWarp as input to the plugin instead of bringing our own?

If this was a generic plugin, I would agree that it could be passed in. However, as I see this plugin as more of a "batteries included" type of thing to prevent people having to know too much about the things going on then I'm not so sure.
it would mean people using the plugin would have to provide a generator function  or as you say pass in uno and the preset.

Moving to https://github.com/warp-ds/esbuild-plugin


Made some small changes to the codebase.

JS within the index.html file is now separated from the index.html file. It now resides in /scripts/highlightText.js . I notice this has code that handles more than just highlighting, but I don't feel familiar enough with the codebase to fix that. This should be looked in to quickly, for organisational purposes. (You already have script files split per purpose, I see)
Dropped the trailing . for embedded scripts, as the site will (seemingly) be hosted from https://catogre.github.io, and the index.html will reside in /, this will be fine.
Fixed up gitignore, smaller, and more targetted towards Jekyll, albeit it could be removed from the repo entirely.
Moved the css file to /media/ as it seems to fit better there.

Thanks for the changes. Merging right now


change Seek API to be less enum-y

The current seek API pretty closely mirrors the relevant OS APIs by having a single method with the seek-style specified as a runtime flag. However this just makes usage of the API more awkward. This API is logically 3 distinct methods that are being squashed into one by overloading on an enum variant.
I consider this to be a popular "trap" in Rust API design; you see several similar methods and reason that they can in fact be unified be taking an enum, reducing the combinatorics and surface-area of the API. However this is simply shuffling the complexity from methods to variants. It requires the caller to pull the enum in scope, and since the prevailing style is to not pull in variants, leads to stuttery incantations like reader.seek(SeekFrom::Start(offset)). In addition it requires a newcomer to lookup what on earth SeekFrom even is.
Therefore this amendment proposes the following changes:

reader.seek(SeekFrom::Start(offset)) -> reader.seek_from_start(offset)
reader.seek(SeekFrom::Current(offset)) -> reader.seek_from_current(offset)
reader.seek(SeekFrom::End(offset)) -> reader.seek_from_end(offset)

Since the relevant OS APIs are a single method, this increases the implementation burden on library authors. However I believe that the Rust philosophy generally favours library consumers over authors (see e.g. where the burden of unsafe primarily lays). This particular API is one where implementation should be a rare one-off thing, while consumption is most certainly not.

Yeah I agree in general with these kinds of changes (enum to method).

:+1: I agree with the reasoning here.
As a side note, this style of overloading is also not very common as a convention (in contrast to trait-based overloading).

Linux and the BSDs support more than the three ways listed above to seek in a file:

SEEK_DATA and SEEK_HOLE are nonstandard extensions also present in Solaris, FreeBSD, and DragonFly BSD; they are proposed for inclusion in the next POSIX revision (Issue 8).

Using separate functions is even less extensible than enums.

@mahkoh I don't see much difference in the extensibility between
enum SeekFrom {
   Start(u64),
   Current(i64),
   End(i64),
   #[cfg(any(target_os="linux",target_os="bsd",...))]
   Data(u64),
   #[cfg(any(target_os="linux",target_os="bsd",...))]
   Hole(u64),
}

and
fn seek_from_start(&mut self, offset: u64) -> Result<i64>;

fn seek_from_current(&mut self, offset: i64) -> Result<i64>;

fn seek_from_end(&mut self, offset: i64) -> Result<i64>;

#[cfg(any(target_os="linux",target_os="bsd",...))]
fn seek_for_data(&mut self, offset: u64) -> Result<i64>;

#[cfg(any(target_os="linux",target_os="bsd",...))]
fn seek_for_hole(&mut self, offset: u64) -> Result<i64>;

If you want five methods just for seeking that's probably fine. POSIX manages to combine 4 billion different ways to seek in a file in one method.

The safe and extensible way to define this API is to use a custom but extensible type:
mod file {
    pub struct Seek(pub i32);

    pub const SEEK_SET: Seek = Seek(0);
    pub const SEEK_CUR: Seek = Seek(1);
    pub const SEEK_END: Seek = Seek(2);

    impl File {
        fn seek(&mut self, pos: i64, whence: Seek) -> Result<i64> {
        }
    }
}

@mahkoh
The separate pos and whence methodology (which is used in old_io) runs into this issue that one needs to cast (via as) the pos parameter quite a bit if only seeking from the start or end, as those variants typically have u64 typed values (not i64). When I converted some of my code that uses seek from old_io to new io, I was able to remove a bunch of as i64, which I'd really like to not add back in.
Even if we went back to this, I'm not sure it's a good idea to expose a public constructor for the whence parameter. How would a user know what magic numbers they were allowed to supply? And if we make it private, it becomes very similar to how old_io works right now.
I suppose the question should be: why should we want to combine 4 billion methods into a single one?

I suppose it might be helpful to note that this RFC is for the Seek API, not the File api, and additional functions based on OS support for seeking file descriptors doesn't make sense (as Seek is used for things not backed by file descriptors).
It might make sense to add some special seek variants to File, but I'm not sure that's in scope here.

How would a user know what magic numbers they were allowed to supply?

By looking them up in the OS manual. No harm will come from invalid numbers.

why should we want to combine 4 billion (or rather, 5) methods into a single one?

You mean like seek_from_start_0, seek_from_start_1, seek_from_start_2, and so on? That would be<PHONE_NUMBER>854775807 functions, not 4.

why should we want to combine 4 billion (or rather, 5) methods into a single one?

It's not combining anything. The OS provides one function and you're trying to split it up because the number of valid inputs in one of the arguments is small.
Quite similar to OpenOptions. Just change it to open_read, open_read_write, open_read_write_append, open_read_append, open_write, open_write_append, and open_append.

Platform-specific APIs can be added via extension traits (which I thought was our strategy). Otherwise the current, previous, and proposed APIs are all inappropriate for handling OS-specific extensions. If we indeed want to transparently support those, then the only tractable design would be basically what the C-API is: magic numbers.

POSIX manages to combine 4 billion different ways to seek in a file in one method.
why should we want to combine 4 billion (or rather, 5) methods into a single one?
You mean like seek_from_start_0, seek_from_start_1, seek_from_start_2, and so on? That would be<PHONE_NUMBER>854775807 functions, not 4 billion.

My point was that there aren't actually 4 billion (or<PHONE_NUMBER>854775807, if you'd prefer your newer numbering): we've got 5. And each of them has a special meaning not communicated by seek_5334
In any case, if we do want to expose underlying OS mechanisms to seek in interesting ways, I'm not sure that should go on trait Seek. Seek ends up being used for things that aren't OS provided, and burdening all the users & implementers (who aren't using file descriptors) with an API designed to work with FILE * or int fd may not be the best choice.

Platform-specific APIs can be added via extension traits (which I thought was our strategy). Otherwise the current, previous, and proposed APIs are all inappropriate for handling OS-specific extensions.

The design I posted above supports extensions without extension traits. A seek operation that is not wrapped by the standard library can be introduced by the user simply by defining:
const SEEK_DATA: Seek = Seek(linux_consts::SEEK_DATA);

With extension traits they will have to write yet another lseek binding even though it's already there in the stdlib.

magic numbers

There is nothing magic about numbers with well known names such as SEEK_DATA. The only thing that is accomplished by using a fixed set of enum variants or functions is that you lock the user into your idea of which platform specific functions should be provided.

To be clear I wasn't belittling the notion of using plain numbers; just using the best term I know for it. I'm not a huge fan of their usage but it can make sense for an OS-level abstraction.

In computer programming, the term magic number
[...]
Unique values with unexplained meaning or multiple occurrences which could (preferably) be replaced with named constants

@mahkoh I think "magic numbers" is a fair characterization of using special numbers when you really mean semantically different things. Replacing random C constants with enums and typed values is a huge part of what gives rust the safe, high-level flavor that it has, whereas the C APIs we bind to are (while usually very flexible) not ergonomic to use directly.
I'm not convinced your scheme of using constants is any better than just using an enum. All I'm really seeing as an advantage is that it breaks the currently tight abstraction over the underlying APIs, which allows you to introduce new seek modes.
This abstraction leak is both a good and a bad thing. @mahkoh if I'm right, you're viewing it as a positive since it allows you to easily introduce your API for non-standard extensions you might use, but from the POV of the rust project right now, it's actually better for the abstraction to be tight and only extensible via std::os::platform extension APIs. A tight abstraction allows for clear behavior and stability, whereas an open abstraction like you're discussing is much harder to cleanly stabilize.

With extension traits they will have to write yet another lseek binding even though
it's already there in the stdlib.

This is a completely valid concern, but I also view it as a rather short-term issue which we shouldn't let dictate long-term API strategy. Eventually we will be able to expose more and more platform specific APIs and bindings, these things are just hidden right now for the purposes of stability for 1.0.

I think "magic numbers" is a fair characterization of using special numbers when you really mean semantically different things.

That doesn't make any sense. The expression "magic number" has a well known definition that I already posted above.

Replacing random C constants with enums and typed values is a huge part of what gives rust the safe

You should know that "safe" has a very specific meaning in Rust. Doing a wrong seek operation is not unsafe. It's very interesting how you incorrectly apply a word with negative connotation (magic number) to my idea of how this API should look like and then incorrectly apply a word with a positive connotation (safe) to your idea how the API should look like.

high-level flavor that it has

Should it be more high level than Python at the cost of flexibility?

Replacing random C constants with enums and typed values

The value that is passed to seek in my API is typed.

whereas the C APIs we bind to are (while usually very flexible) not ergonomic to use directly

I do not understand why
lseek(fd, offset, SEEK_SET);

is less ergonomic than
file.seek(Seek::Set(offset));

which allows you to introduce new seek modes.

Correct, me. I don't have to wait for the library maintainers to maybe introduce new variants that can do what I want.

you're viewing it as a positive since it allows you to easily introduce your API for non-standard extensions

Everything becomes non-standard when the standard you're working with is the intersection of what all supported operating systems provide. Right now you cannot even set the mode on a directory you create with Rust. Everything will have mode 0o777. Because Windows doesn't have modes so that's non-standard. Another example: File cannot even open files larger than 4G on 32 bit unix because that would require a non-standard API.

A tight abstraction allows for clear behavior and stability, whereas an open abstraction like you're discussing is much harder to cleanly stabilize.

With words such as "cleanly" you can justify just about anything. If we're just talking about "stabilize": glibc has had a stable API and ABI for much longer than Rust exists. In contrast to that: Rust has to break the API if it ever introduces a new seek mode into the enum.
There is nothing "unstable" about the API I posted above.

Eventually we will be able to expose more and more platform specific APIs and bindings

Platform specific extension traits do not create good APIs. Assuming the current seek implementation with an enum, the seek function will always be limited to the existing three cross platform seek modes because you cannot change a function with an extension trait. So the function for platforms that support SEEK_DATA will be called what? seek_linux, seek_freebsd, seek_dragonfly? Not all unixes support SEEK_DATA, so it makes no sense to provide it via the unix module.
My API above has this covered as the only thing you have to do to extend it to a platform specific functionality is to define a new constant. And then you can continue using the API you've used for years but with new functionality.
The current "stabilization process" confuses "stable" with "locked down".

Expanding on the terrible API extension traits provide: If you use extension traits, then you have to use one function for every platform specific detail. This does not work:
if cfg!(target_os = "dragonfly") {
    file.seek_dragonfly(...);
} else if cfg!(target_os = "linux") {
    file.seek_linux(...);
}

etc. This is already a problem with OpenOptionExt today. You have to write code like this:
#[cfg(target_os = "dragonfly")]
fn my_oneliner(...) {
    file.seek_dragonfly(...);
}

#[cfg(target_os = "linux")]
fn my_oneliner(...) {
    file.seek_linux(...);
}

my__oneliner(...);

@mahkoh the methods don't have to have different names.

What about, say,
fn seek<T: SeekWhence>(&mut self, seek: T)
// or
fn seek<T: SeekWhence>(&mut self, pos: i64, whence: T)

used like, file.seek(io::SeekStart(10)), or file.seek(10, linux::SeekData), although this is possibly still quite "enum"-y.

I don't see how OpenOptionExt has this problem

You can't open a file with the same modes on linux and windows but with mode set on linux. You cannot do
if cfg!(unix) {
    options.mode(...);
}

The name of the function is not the only problem. If you reference a name that doesn't exist on the target platform, e.g. SEEK_DATA on windows, then you have to move that piece of code into its own function, away from the rest of the logic.

What about, say,

Probably depends on how SeekWhence looks like.

@huonw That's interesting... My feeling is that a strong API should:

evaluate to lseek (or whatever) for raw-file-type Seek back-ends;
allow evaluating to distinct functions for other Seek back-ends.

I don't think the second point above can be supported in current Rust, but the API you described might eventually allow a future Rust to support what I'm talking about.
To spitball, something like this would eventually be neat to support:
// MyType lazily reads from, say, an open socket, and allows seeking through all data that's
// currently been read.
// does not support SEEK_END, since that would require reading all data to find EOF,
// which violates expectation that seeking is a fast operation.
// this use-case also suggests a SEEK_FORWARD and SEEK_REVERSE SeekWhence,
// which act like SEEK_CUR but only allow advancing in a desired direction.
// note that SEEK_FORWARD and SEEK_REVERSE don't actually have analogues
// in the POSIX seek routine.
impl Seek for MyType {
  fn seek(&mut self, offset: i64, whence: SeekSet) -> i64 {
    self.my_seek_set(offset);
  }
  fn seek(&mut self, offset: i64, whence: SeekCur) -> i64 {
    if offset < 0 {
      self.rewind(-offset)
    } else {
      self.advance(offset)
    }
  }
  // do not implement `seek` for SeekEnd: op not supported for MyType.
}
let x = MyType::new();
x.seek(10, SeekSet);
// x.seek(0, SeekEnd); <- fails to compile, because `seek` is not implemented with SeekEnd parameterization.
fn blah<T: Seek>(x: &mut T) {
  // using SeekEnd variant would have to propagate to function signature somehow?
  x.seek(0, SeekEnd);
}
// blah(&mut x); <- fails to compile, somehow? blah uses SeekEnd,
// which MyType doesn't provide an implementation for, so the attempt
// to call `blah` should fail to compile, or at least to link.

This won't work in this form, but I feel like there's the germ of something here... The Rust generics compilation model (in which a different function may be generated for each unique parameterization of a type) almost seems to allow explicitly controlling the function generation for a specific parameterization. If you can do that, you might also want to avoid generating functions for unsupported parameterizations.
I'm not sure this is a good idea, but it's interesting to me all the same. And I like that using a SeekWhence trait would be compatible with a crazy idea like this, if this crazy idea was ever thought useful to add to the language.

@aidancully We can implement something similar using multidispatch:
pub trait Seek<T=SeekFrom> {
    fn seek(&mut self, offset: T);
}

All seekable streams would implement Seek<SeekFrom>, but files would implement Seek<platform_name_here::FancySeekExtensions> as well.

:+1: to changing the Seek trait to use three methods. It makes it much nicer to use. Since this is a general trait, which covers Cursors and other non-file things, I don't think supporting platform-dependent seek functionality should be a consideration here. Types that need other methods of seeking (os-specific file objects, among others) will provide it independently of this trait.

Enum params is OK for me. It's common in api design, and seek is not the
only one.
On Mar 20, 2015 7:43 AM, "rkjnsn"<EMAIL_ADDRESS>wrote:

[image: :+1:] to changing the Seek trait to use three methods. It makes
it much nicer to use. Since this is a general trait, which covers Cursors
and other non-file things, I don't think supporting platform-dependent seek
functionality should be a consideration here. Types that need other methods
of seeking (os-specific file objects, among others) will provide it
independently of this trait.
—
Reply to this email directly or view it on GitHub
https://github.com/rust-lang/rfcs/pull/969#issuecomment-83810799.

And It's verbose to have three seek methods.
On Mar 20, 2015 8:27 AM, "Liigo Zhuang"<EMAIL_ADDRESS>wrote:

Enum params is OK for me. It's common in api design, and seek is not the
only one.

@liigo

Enum params is OK for me. It's common in api design, and seek is not the only one.

The question whether is this particular case, where there are only three variants, it makes sense to have the complication of an enum instead of just having three methods. I find having three methods to be much simpler, cleaner, and easy to use.

And It's verbose to have three seek methods.

I think it's much more verbose to have to type reader.seek(SeekFrom::Start(offset)) repeatedly in user code that to just be able to do reader.seek_from_start(offset)

Also, from a purely bikeshedding perspective, what about seek_absolute and seek_relative instead of seek_from_start and seek_from_current?

As for @kennytm 's code above,
enum SeekFrom {
   Start(u64),
   Current(i64),
   End(i64),
   #[cfg(any(target_os="linux",target_os="bsd",...))]
   Data(u64),
   #[cfg(any(target_os="linux",target_os="bsd",...))]
   Hole(u64),
}

now
match Start(0) {
    Start(_) | Current(_) | End(_) =>{}
    _ =>() // error here for Windows
}

so current API do has extensibility problem.
+1 for this RFC.

@rkjnsn "relative to what?" isn't answered by seek_relative(), hence the _from_foo naming.

Unfortunately I dropped the ball on this one; we need to stabilize this API for beta, and at this point there's not time to make this change. (I personally much prefer the proposed API, but there wasn't a clear consensus anyway, and it's used rarely enough that it probably doesn't matter much).
I'm going to close this RFC. Thanks again, @Gankro!

:(
Oh well


[HTTPCookie] Make cookies(withResponseHeaderFields:for:) signature match Darwin

I'd be grateful if this API signature fix could make it into Swift 3.1.  Thanks.

@swift-ci please test and merge


Possibility to install without creating shortcuts

Hello,
it would be great if the Rocket.Chat client would support some options to simplify deployment:
(Other parts of this task #139, #140)

possibility to install without creating shortcuts (desktop and start menu in Windows).

I have to say it again: great project, guys!

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/30679992-deployment-options?utm_campaign=plugin&utm_content=tracker%2F19476668&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F19476668&utm_medium=issues&utm_source=github).

[x] possibility to install without creating shortcuts (desktop and start menu in Windows). (via #116)
[ ] possibility to deploy a config file for the first connection (e.g. server address, username, toggled server list status, ...)
[ ] command line option to start the client in hidden mode (tray icon) or remember this setting when closing the app

@flauschi can you split this issue in small issues? And rename this to the first one? So we can close this and set more details and priorities for each item.
Best.

@rodrigok Done. New issues are #139 and #140. This one could be closed. I have already tested it. :)

Thanks


Feature Request:  Basic Logging

Maybe I've just not run across them yet, but I think it would be handy to have a basic audit log for Honolulu.

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

ID: 786aeae9-05e3-50e3-4d33-46c5a8174576
Version Independent ID: b5f7ee33-6b8e-005a-f8de-fb57aa2841e2
Content: Microsoft Project Honolulu Frequently Asked Questions
Content Source: WindowsServerDocs/manage/honolulu/honolulu-faq.md
Service: unspecified
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

HI, Matthew (again :) ) - best bet is to go to http://aka.ms/HonoluluFeedback to request basic logging capability. The team is currently working on improvements to Honolulu. Thanks!


Setting logging appender target as lowercase "stdout" or "stderr" failure

Dropwizard version 2.1x

Issue description:
In the Dropwizard Console Logging Doc as well as javadoc of the ConsoleAppenderFactory Class, both indicate that the target property can be a lowercase word stderr or stdout. However, this setting failure is exposed when we are using customized JSON Deserialization in the application as following:
     bootstrap.getObjectMapper()
     .enable(DeserializationFeature.READ_UNKNOWN_ENUM_VALUES_USING_DEFAULT_VALUE);

and addressed out the logging appender's target setting in test-example.yml and example.yml:
appenders:
    - type: console
      # add target for test
      target: stdout

Exception is thrown as following:
[ERROR] com.example.helloworld.IntegrationTest  Time elapsed: 0.456 s  <<< ERROR!
io.dropwizard.configuration.ConfigurationParsingException:
test-example.yml has an error:
  * Incorrect type of value at: logging.appenders.[0].target; is of type: String, expected: ConsoleStream

Caused by: com.fasterxml.jackson.databind.exc.InvalidFormatException:
Cannot deserialize value of type `io.dropwizard.logging.ConsoleAppenderFactory$ConsoleStream` from String "stdout": not
one of the values accepted for Enum class: [STDERR, STDOUT]  at [Source: UNKNOWN; line: -1, column: -1] (through reference
chain: com.example.helloworld.HelloWorldConfiguration["logging"]-
>io.dropwizard.logging.DefaultLoggingFactory["appenders"]->java.util.ArrayList[0]-
>io.dropwizard.logging.ConsoleAppenderFactory["target"])

Issue can be reproduced by git clone this dropwizard-example forked branch.
runmvn clean install after git clone, the above exception will be thrown.
Also,  this PR shows the modifications from the original dropwizard-example repo to expose this issue.

The exception won't be thrown when ommitting out the target property in test-example.yml  or using the default JSON Deserialization settings. In this case, I assume the default setting "STDOUT" is being used.
This exception won't be thrown when passing an uppercase word STDOUT or STDERR as the value to the target. So it indicates that the enum ConsoleStream Class won't accept lowercase words for the target property, which contradicts the Dropwizard Console Logging Doc as well as the javadoc for the ConsoleAppenderFactory Class.

Hi @yingliu928, thanks for reporting this. The issue should be caused here. In the default configuration, the FuzzyEnumModule from Dropwizard ensures the property is deserialized correctly when using the lowercase values. Therefore the docs are fine for common use cases. However, when using one of the three Jackson features listed in the linked class, the custom deserializer won't be used.
Updating the docs won't help us much because this is a problem for all enum values, what you already experienced at commenting out the 'health' configuration.
As the FuzzyEnumModule does more than just ignore cases, we could use the MapperFeature#ACCEPT_CASE_INSENSITIVE_ENUMS as a fallback strategy.
@dropwizard/committers I'd put a vote for enabling the MapperFeature#ACCEPT_CASE_INSENSITIVE_ENUMS by default. As the FuzzyEnumModule is also registered by default, this shouldn't be a behavior change, the custom deserializer still gets invoked and the value is parsed correctly. Any concerns against that?

@zUniQueX Thanks for the feedback!


Descriptive message not visible in Onyphe API error

Is it possible to display the descriptive message returned by the API during error 400 ?
Sample message from the API documentation :
{
  "error": 3,
  "text": "Invalid API key format",
  "myip": "<redacted>",
  "status": "nok"
}

Thank you for suggesting this enhancement !
It is possible and will be a great improvement to allow the user to understand underlying server errors if any.
It is now available as part of release 0.2.0 (see both 1a65bc4e62a338b021f07b7393713abb078a67aa and 26616ac95e0ea933dd5f344b2072e1e2d131598d).


[bug] change clearlydefined certifier to use Metadata.ScannedOn time for hasSourceAt

Describe the bug
Currently hasSourceAt uses metadata timestamp which is set when the attestation is created. This needs to be changed to Meta-Updated  timestamp which is when Clearly Defined last scanned for this information.
The current timestamp causes the hasSourceAt to node to be re-created because of the KnownSince field changing. More accurately, this should only be re-created when clearly defined has re-scanned on its own service.
Expected behavior
Not recreate hasSourceAt nodes when a the scanned timestamp from clearly defined has not changed during the ceritifer run.
GUAC version
v0.8.8

Based on looking at the code, this is set to the right value: https://github.com/guacsec/guac/blob/main/pkg/ingestor/parser/clearlydefined/clearlydefined.go#L173
The issue is rather the documentRef is different as the attestation contains the "time the scan was done by the CD certifier" which causes the document ref to be different.
For example:
{
  "data": {
    "HasSourceAt": [
      {
        "id": "has_source_ats:01924ebd-f4a6-7d46-8823-bb02319401bb",
        "justification": "Retrieved from ClearlyDefined",
        "knownSince": "2024-07-18T04:55:24.584Z",
        "package": {
          "id": "package_types:deb",
          "type": "deb",
          "namespaces": [
            {
              "id": "package_namespaces:debguac-split-@@debian",
              "namespace": "debian",
              "names": [
                {
                  "id": "package_names:63121b40-c9b1-5c90-8c5a-ff3899a6c190",
                  "name": "dash",
                  "versions": [
                    {
                      "id": "package_versions:5d7f13bf-a953-5b6d-aa59-336fd4f9f64d",
                      "version": "0.5.11+git20200708+dd9ef66-5",
                      "qualifiers": [
                        {
                          "key": "arch",
                          "value": "arm64"
                        },
                        {
                          "key": "distro",
                          "value": "debian-11"
                        }
                      ],
                      "subpath": ""
                    }
                  ]
                }
              ]
            }
          ]
        },
        "source": {
          "id": "source_types:debsrc",
          "type": "debsrc",
          "namespaces": [
            {
              "id": "source_namespaces:debsrcguac-split-@@",
              "namespace": "",
              "names": [
                {
                  "id": "source_names:b5ade3d0-0fa6-58d4-b2af-370f87fff294",
                  "name": "dash",
                  "tag": "0.5.11+git20200708+dd9ef66-5",
                  "commit": null
                }
              ]
            }
          ]
        },
        "origin": "clearlydefined",
        "collector": "clearlydefined",
        "documentRef": "sha256_81c875d1658cabc40096e6742ea84f6fde66608bbe9b2049bcad6ba6e5d9434f"
      },
      {
        "id": "has_source_ats:01924eed-5d4c-752c-bc37-f48f58d9fe9d",
        "justification": "Retrieved from ClearlyDefined",
        "knownSince": "2024-07-18T04:55:24.584Z",
        "package": {
          "id": "package_types:deb",
          "type": "deb",
          "namespaces": [
            {
              "id": "package_namespaces:debguac-split-@@debian",
              "namespace": "debian",
              "names": [
                {
                  "id": "package_names:63121b40-c9b1-5c90-8c5a-ff3899a6c190",
                  "name": "dash",
                  "versions": [
                    {
                      "id": "package_versions:5d7f13bf-a953-5b6d-aa59-336fd4f9f64d",
                      "version": "0.5.11+git20200708+dd9ef66-5",
                      "qualifiers": [
                        {
                          "key": "arch",
                          "value": "arm64"
                        },
                        {
                          "key": "distro",
                          "value": "debian-11"
                        }
                      ],
                      "subpath": ""
                    }
                  ]
                }
              ]
            }
          ]
        },
        "source": {
          "id": "source_types:debsrc",
          "type": "debsrc",
          "namespaces": [
            {
              "id": "source_namespaces:debsrcguac-split-@@",
              "namespace": "",
              "names": [
                {
                  "id": "source_names:b5ade3d0-0fa6-58d4-b2af-370f87fff294",
                  "name": "dash",
                  "tag": "0.5.11+git20200708+dd9ef66-5",
                  "commit": null
                }
              ]
            }
          ]
        },
        "origin": "clearlydefined",
        "collector": "clearlydefined",
        "documentRef": "sha256_cced45104c833750ed00aad002a56b397d6c11c0e41c436338313acd554990d1"
      }
    ]
  }
}

where the document refs don't match.
``

closing this right now as this is a non-issue.


armv7 compatibility for docker image

Added os libraries and installed Rust to be able to install pillow python library required to make ibeam docker image compatible with armv7 architecture

My baa, it wasn't pillow, it was cryptography. Here is the link to the docs with the requirement. Unsure why this hasn't caused issues without armv7 addition to docker build.

So, do I understand correctly: manylinux installs Rust for us automatically, but is not available for armv7, hence you need to install it manually?
That is correct

What are you trying to say here? Can you check how much each layer weighs in the new image and report it back here? Whether the addition is worth it would depend on how much build time and image weight it adds.

This is one I built for armv7, it adds 300MB from Rust installation. In terms of build time below is the comparison between both.

Thanks for the breakdown @matthewmoorcroft.
That's roughly a 50% increase in build time and image size. I think until there's a substantial userbase requesting it, I'd vote for this being an exceedingly large addition.
However, as to not throw your work away, how about we create a separate Dockerfile, eg. 'Dockerfile_armv7', in which we preserve these changes. It wouldn't become part of the main image, however it would make it available for other users who'd like to build for armv7. Would that make sense?

Hey @Voyz that makes perfect sense, will make changes to the code to create alternate versions.

Hey @Voyz sorry for the delay, created the two alternate versions for Docker, let me know if there are any other issues

Hey @matthewmoorcroft no problem at all! Many thanks for picking this up once again and finishing this PR. Looks, great, ready to merge 👍
Thanks for this contribution!


Pre-trained model for this project (Adapter)

Hi, could you please provide the pre-trained models for this SAM-Adapter project?

Hello! Please view this link: https://cowtransfer.com/s/da0559afdfc045 click link to check [ best_results.tar ] or access cowtransfer.com and input extract code: y85nd7 to check;

Received the file. Thank you


Universal does not work with yarn commands

I have recently migrated to your starter pack for universal support. Looks really good but unfortunately I have issues when running the app in production mode. The app works fine when I run either 'yarn start' and yarn run start:hmr
I am guessing we need to run yarn run build to compile all assets to make it production ready. This works on the CLI but I just see the Webpack Analyzer Bundle (not sure if that is an error)
I then run yarn run universal the CLI does not throw errors but there are console errors with broken reference files to the css and js.
Also, when I try to load a new link via routes I get no content found
I have seen the folder for server and it looks okay to me with the css and js files being populated
I'm not sure what I am missing but it appears to be some setting. I need universal mode to work as our app is going to be dependent on strong SEO. I have followed the same steps with a fresh copy of the stater pack code as-is but the same issues are happening as mentioned above.
Any help appreciated.

As stated in other issues, I will not be touching Universal branches until it's updated to work properly with angular 4.0. Universal lags behind the main angular branches so it breaks more and more with every angular update as it's not tested against core.

@qdouble can you add a shrinkwrap for the time being please to freeze the dependencies working with eachother?

will be updated to Angular 4?

I have been working on this here, but am pretty stumped as to the best way to fix this error:
/Users/matt/Projects/Personal/angular-universal/angular-webpack2-starter/node_modules/@ngrx/store/src/dispatcher.js:6
import { BehaviorSubject } from 'rxjs/BehaviorSubject';
^^^^^^
SyntaxError: Unexpected token import
    at Object.exports.runInThisContext (vm.js:78:16)
    at Module._compile (module.js:543:28)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.83 (/Users/matt/Projects/Personal/angular-universal/angular-webpack2-starter/dist/server/index.js:1:127267)
    at e (/Users/matt/Projects/Personal/angular-universal/angular-webpack2-starter/dist/server/index.js:1:177)

I know why it is happening, ngrx has some .js files that have es6 syntax in them and the build system isn't transpiling that to es5.  This stackoverflow post recommends either using babel, using webpack, or yelling at the ngrx developers.  The webpack suggestion is probably where the solution is, but I'm still not quite familiar enough with how this starter is using for AOT/Universal.

I have gotten a little further, but due to this issue I don't think I can go any further since it seems Material 2 just plain does not work yet with Angular Universal, and won't officially until 'around 4.1.x'.
Unofficially there are a few workarounds that do work as mentioned here.

@fdambrosio yes, I will update the universal (or whatever they rename it to) branches when it is somewhat stable... doesn't seem to make sense to mess with it right now


Change layout to SingleChildScrollView or ListView.

https://stackoverflow.com/questions/49480051/flutter-dart-exceptions-caused-by-rendering-a-renderflex-overflowed

if you're available to commit, you can look at this issue. @davidkhala


class name for valid and invalid input

reactstrap set the class for a valid input to is-valid and is-invalid for an invalid input.
availity set the class to av-valid respectively av-invalid.
Do I miss something?

Just extra classes for you to target. Their is also av-touched and av-dirty. You can use these classes to style fields different via css based on their current validation state.

Ok. But why don't you set the reactstrap class?

I switched most of the class names to be is-{thing} such as is-dirty and is-touched but I could not do is-valid and is-invalid as those trigger styles in default bootstrap which may not be wanted. This is mostly the is-valid as it is more rare to see the "success" validation styles in the wild. av-valid and av-invalid are still used in case custom styles want to target those and is-invalid is used when when invalid (along with av-invalid).
Yes, it's slightly opinionated, only is-invalid and not is-valid, but it is more common, and this is availity reactstrap validation and that is the styles for Availity.
Closing since it isn't an issue, but more of a question (which is hopefully answered). Feel free to keep the conversion going if you need to.


Problem building in Ubuntu 14.04

Generating build/mk-moar-pc.pl ......................... OK

Configuration FAIL. You can try to salvage the generated Makefile.
Command failed (status 256): /home/jmerelo/perl5/perlbrew/perls/perl-5.24.0/bin/perl Configure.pl --optimize --prefix=/home/jmerelo/.rakudobrew/moar-nom/install --make-install
Command failed (status 7424): /home/jmerelo/perl5/perlbrew/perls/perl-5.24.0/bin/perl Configure.pl --prefix=/home/jmerelo/.rakudobrew/moar-nom/install --backends=moar --make-install --git-protocol=https --git-reference=/home/jmerelo/.rakudobrew/bin/../git_reference --gen-moar
Failed running /home/jmerelo/perl5/perlbrew/perls/perl-5.24.0/bin/perl Configure.pl --backends=moar --gen-moar --git-reference="/home/jmerelo/.rakudobrew/bin/../git_reference" --make-install  at /home/jmerelo/.rakudobrew/bin/rakudobrew line 57.
	main::run("/home/jmerelo/perl5/perlbrew/perls/perl-5.24.0/bin/perl Confi"...) called at /home/jmerelo/.rakudobrew/bin/rakudobrew line 382
	main::build_impl("moar", undef, "") called at /home/jmerelo/.rakudobrew/bin/rakudobrew line 115

I upgraded rakudobrew to the last version, and checked with perl 5.20 and 5.24 No idea what's the problem.

Still the same problem with today's version. Any idea?


accountBalance requires securityCredential and certPath

docs inform on a single requirement of providing consumerKey and consumerSecret.
Though for the accountBalance request securityCredential is also a requirement. Where to find this for our Mpesa account?

is that also the case for the myKey.cert?

Yes at https://developer.safaricom.co.ke/docs#introduction
You have Sandbox Certificate and Production Certificate provided as links on the left pane

when I login and check api details for the app, i find consumerKey and consumerSecret. But where to find the "securityCredential"?


Cell custom style - limit the number of rows globally

Hi,
I'm trying to limit the number of rows of each cell data in the body to 1 row.
I know how to do it for a specific column but I want to do it in the theme for all the table in my project.
I add to my theme file the rule:
 MUIDataTableBodyCell: {
    simpleCell: {
      display: "-webkit-box",
      overflow: "hidden",
      maxWidth: "26vw",
      "-webkit-box-orient": "vertical",
      "-webkit-line-clamp": 1,
    }
  },

but it looks like I can't change the display prop to "-webkit-box" without ruin the table style.
Any suggestion?

ref : https://material-ui.com/customization/theming/

Style is dependent on material-ui (cell, table, pagination, footer... etc).
Please refer to the address below.
ref

https://material-ui.com/customization/theming/
https://material-ui.com/customization/globals/
#1343

I tried that but the MUIDataTableBodyCell style class belongs to mui-datatables

Found a solution:
For example: In case all cells in the table wrapped with p tag:
 MUIDataTableBodyCell: {
    simpleCell: {
      "& $p": {
        display: "-webkit-box",
        overflow: "hidden",
        maxWidth: "20vw",
        "-webkit-box-orient": "vertical",
        "-webkit-line-clamp": 1,
      },
    },
  },


🐛 [firebase_dynamic_links] onLink always returns null for iOS after upgrading to 0.7.0+1

Bug report
Dynamic links were working correctly in my app when I was using firebase_dynamic_links 0.6.2. Per the recent flutter fire migration document, I upgraded dynamic links, firebase_core and other flutter fire plugins to the appropriate versions. After upgrading dynamic links to 0.6.2, dynamic links now only work for android. I've tried on the iOS simulator and a real device.
When a dynamic link is opened, the will come into the foreground, but FirebaseDynamicLinks.instance.onLink always produces a PendingDynamicLinkData of null.
Steps to reproduce
firebase_core: ^0.7.0
firebase_dynamic_links: 0.7.0+1

void initDynamicLinks(BuildContext context) async {
  //This is called if the app is already open
  FirebaseDynamicLinks.instance.onLink(
      onSuccess: (PendingDynamicLinkData dynamicLink) async {
    final Uri deepLink = dynamicLink?.link;

    _handleReceivedDynamicLink(context, deepLink);
  }, onError: (OnLinkErrorException e) async {
    print('onLinkError');
    print(e.message);
  });

  //This is called when the app is closed
  final PendingDynamicLinkData data =
      await FirebaseDynamicLinks.instance.getInitialLink();
  final Uri deepLink = data?.link;
  if (deepLink != null) {
    _handleReceivedDynamicLink(context, deepLink);
  }
}

The deepLink variable is always returning null after a dynamic link is opened.
Expected behavior
In the android version, and in the past iOS version of the plugin, the same code produces a non-null value for the bolded value. I've tried also switching to the beta version of Flutter to see if that produced any different results, and it hasn't changed this issue.
From doing a bit of searching, I thought it might be related to the issue found here: https://github.com/FirebaseExtended/flutterfire/issues/4711
The difference is, that's working for iOS and not android. I also tried to suggested workaround and it didn't work for my issue.

Flutter doctor
[✓] Flutter (Channel beta, 1.26.0-17.3.pre, on Mac OS X 10.15.6 19G2021 darwin-x64, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Android Studio (version 4.1)
[✓] Connected device (2 available)

• No issues found!

Flutter dependencies
dependencies:
- animator 2.0.2 [flutter states_rebuilder]
- auto_size_text 2.1.0 [flutter]
- cached_network_image 2.5.0 [flutter flutter_cache_manager octo_image]
- cloud_firestore 0.16.0 [flutter meta quiver firebase_core firebase_core_platform_interface cloud_firestore_platform_interface cloud_firestore_web]
- cloud_functions 0.9.0 [meta flutter firebase_core firebase_core_platform_interface cloud_functions_platform_interface cloud_functions_web]
- cupertino_icons 1.0.0
- device_info 0.4.2+7 [flutter device_info_platform_interface]
- firebase_auth 0.20.0+1 [meta firebase_core firebase_core_platform_interface firebase_auth_platform_interface firebase_auth_web flutter]
- firebase_core 0.7.0 [firebase_core_platform_interface flutter quiver meta firebase_core_web]
- firebase_core_platform_interface 3.0.1 [flutter meta plugin_platform_interface quiver]
- firebase_crashlytics 0.4.0+1 [flutter stack_trace firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface]
- firebase_dynamic_links 0.7.0+1 [flutter firebase_core]
- firebase_messaging 8.0.0-dev.14 [meta flutter firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web]
- firebase_storage 7.0.0 [flutter firebase_core firebase_core_platform_interface firebase_storage_web firebase_storage_platform_interface quiver]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_launcher_icons 0.8.1 [image args yaml path]
- flutter_native_admob 2.1.0+3 [flutter]
- google_fonts 1.1.2 [flutter http path_provider crypto]
- http 0.12.2 [http_parser path pedantic]
- image 2.1.19 [archive xml meta]
- image_cropper 1.3.1 [flutter]
- image_picker 0.6.7+22 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- intl_phone_number_input 0.6.0 [flutter meta libphonenumber libphonenumber_plugin equatable]
- modal_progress_hud 0.1.3 [flutter]
- package_info 0.4.3 [flutter]
- permission_handler 5.0.1+1 [flutter meta permission_handler_platform_interface]
- photo_view 0.10.3 [flutter]
- provider 4.3.3 [collection flutter nested]
- share 0.6.5+4 [meta mime flutter]
- shared_preferences 0.5.10 [meta flutter shared_preferences_platform_interface shared_preferences_linux shared_preferences_macos shared_preferences_web]
- smooth_page_indicator 0.2.0 [flutter]
- timezone 0.6.1 [path]
- url_launcher 5.7.10 [flutter url_launcher_platform_interface url_launcher_web url_launcher_linux url_launcher_macos url_launcher_windows]

dev dependencies:
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]

transitive dependencies:
- archive 2.0.13 [crypto args path]
- args 1.6.0
- async 2.5.0-nullsafety.3 [collection]
- boolean_selector 2.1.0-nullsafety.3 [source_span string_scanner]
- characters 1.1.0-nullsafety.5
- charcode 1.2.0-nullsafety.3
- clock 1.1.0-nullsafety.3
- cloud_firestore_platform_interface 3.0.1 [flutter meta collection firebase_core plugin_platform_interface]
- cloud_firestore_web 0.3.0+1 [flutter flutter_web_plugins http_parser meta firebase_core firebase_core_web cloud_firestore_platform_interface js]
- cloud_functions_platform_interface 4.0.1 [flutter meta firebase_core plugin_platform_interface]
- cloud_functions_web 3.1.3 [firebase_core firebase_core_web cloud_functions_platform_interface flutter flutter_web_plugins http_parser meta js]
- collection 1.15.0-nullsafety.5
- convert 2.1.1 [charcode typed_data]
- crypto 2.1.5 [collection convert typed_data]
- device_info_platform_interface 1.0.1 [flutter meta plugin_platform_interface]
- equatable 1.2.5 [collection meta]
- fake_async 1.2.0-nullsafety.3 [clock collection]
- ffi 0.1.3
- file 5.2.1 [intl meta path]
- firebase_auth_platform_interface 3.0.1 [flutter meta firebase_core plugin_platform_interface]
- firebase_auth_web 0.3.2+6 [flutter flutter_web_plugins meta http_parser intl firebase_core firebase_core_web firebase_auth_platform_interface js]
- firebase_core_web 0.2.1+3 [firebase_core_platform_interface flutter flutter_web_plugins meta js]
- firebase_crashlytics_platform_interface 1.1.6 [flutter meta collection firebase_core plugin_platform_interface]
- firebase_messaging_platform_interface 1.0.0-dev.10 [flutter meta firebase_core plugin_platform_interface]
- firebase_messaging_web 0.1.0-dev.5 [flutter flutter_web_plugins meta firebase_core firebase_core_web firebase_messaging_platform_interface js service_worker]
- firebase_storage_platform_interface 1.0.4 [flutter meta collection firebase_core plugin_platform_interface]
- firebase_storage_web 0.1.1+3 [async crypto firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
- flutter_blurhash 0.5.0 [flutter meta]
- flutter_cache_manager 2.1.1 [flutter path_provider uuid http path sqflite pedantic clock file rxdart image]
- flutter_plugin_android_lifecycle 1.0.8 [flutter]
- flutter_web_plugins 0.0.0 [flutter js characters collection meta typed_data vector_math]
- http_parser 3.1.4 [charcode collection source_span string_scanner typed_data]
- image_picker_platform_interface 1.1.0 [flutter meta http plugin_platform_interface]
- intl 0.16.1 [path]
- js 0.6.3-nullsafety.3
- libphonenumber 1.0.2 [flutter meta]
- libphonenumber_platform_interface 0.2.0 [flutter plugin_platform_interface]
- libphonenumber_plugin 0.1.0 [flutter flutter_web_plugins libphonenumber_platform_interface libphonenumber_web]
- libphonenumber_web 0.1.1 [flutter flutter_web_plugins js libphonenumber_platform_interface]
- matcher 0.12.10-nullsafety.3 [stack_trace]
- meta 1.3.0-nullsafety.6
- mime 0.9.7
- nested 0.0.4 [flutter]
- octo_image 0.3.0 [flutter flutter_blurhash]
- path 1.8.0-nullsafety.3
- path_provider 1.6.27 [flutter path_provider_platform_interface path_provider_macos path_provider_linux path_provider_windows]
- path_provider_linux 0.0.1+2 [path xdg_directories path_provider_platform_interface flutter]
- path_provider_macos 0.0.4+3 [flutter]
- path_provider_platform_interface 1.0.4 [flutter meta platform plugin_platform_interface]
- path_provider_windows 0.0.4+3 [path_provider_platform_interface meta path flutter ffi win32]
- pedantic 1.9.0
- permission_handler_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- petitparser 3.1.0 [meta]
- platform 2.2.1
- plugin_platform_interface 1.0.3 [meta]
- process 3.0.13 [file intl meta path platform]
- quiver 2.1.5 [matcher meta]
- rxdart 0.24.1
- service_worker 0.2.4 [js]
- shared_preferences_linux 0.0.2+1 [file flutter meta path path_provider_linux shared_preferences_platform_interface]
- shared_preferences_macos 0.0.1+10 [shared_preferences_platform_interface flutter]
- shared_preferences_platform_interface 1.0.4 [meta flutter]
- shared_preferences_web 0.1.2+7 [shared_preferences_platform_interface flutter flutter_web_plugins meta]
- sky_engine 0.0.99
- source_span 1.8.0-nullsafety.4 [charcode collection path term_glyph]
- sqflite 1.3.2+2 [flutter sqflite_common path]
- sqflite_common 1.0.3+1 [synchronized path meta]
- stack_trace 1.10.0-nullsafety.6 [path]
- states_rebuilder 3.2.0 [flutter collection]
- stream_channel 2.1.0-nullsafety.3 [async]
- string_scanner 1.1.0-nullsafety.3 [charcode source_span]
- synchronized 2.2.0+2
- term_glyph 1.2.0-nullsafety.3
- test_api 0.2.19-nullsafety.6 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.3.0-nullsafety.5 [collection]
- url_launcher_linux 0.0.1+1 [flutter]
- url_launcher_macos 0.0.1+7 [flutter]
- url_launcher_platform_interface 1.0.9 [flutter meta plugin_platform_interface]
- url_launcher_web 0.1.5+3 [url_launcher_platform_interface flutter flutter_web_plugins meta]
- url_launcher_windows 0.0.1+3 [flutter]
- uuid 2.2.0 [crypto convert]
- vector_math 2.1.0-nullsafety.5
- win32 1.7.4+1 [ffi]
- xdg_directories 0.1.0 [path process flutter]
- xml 4.5.1 [collection convert meta petitparser]
- yaml 2.2.1 [charcode collection string_scanner source_span]

Hi @sjrphx
Does the initial link also not work for you? Is the link still generating correctly or are you using the same link?
Thank you

Hi @sjrphx
Does the initial link also not work for you? Is the link still generating correctly or are you using the same link?
Thank you

Thank you for replying.
The initial link is also null and behaves the same when the app is closed and a dynamic link is opened. Link generation is still working correctly, and I'm using a new link.

I'm not seeing this using the official example and firebase_dynamic_links: ^0.7.0+1.
The version change should not have caused something like this. Just to be sure are you certain the link is set up correctly for iOS?
How are you opening the link in android and iOS?

To ensure there was no issue with with how I'm using the two on each platform, I had the debugger running and was debugging upstream of that possibility:
FirebaseDynamicLinks.instance.onLink(
onSuccess: (PendingDynamicLinkData dynamicLink) async {
final Uri deepLink = dynamicLink?.link;
The .onLink onSuccess gets called but is producing a null Uri variable (deepLink) for iOS.

It's hard to know what is going wrong exactly without the exact link and project. Still, since it seems like the upgrade caused it, this could have been caused by a change in the package native code.

I've ended up downgrading this package and the related dependencies in order to have my app function until there's more clarity on the subject. Please let me know if there's anything I can do to help further debug the issue.

I ended up finding out what the issue was, and it was on my side. Specifically, I changed my dynamic link domain link, but didn't change it everywhere (FirebaseDynamicLinksCustomDomains in Info.plist had the wrong link). Sorry for the false alarm!


0.60.0-b6

This brings the Beast subtree up to date and includes these important changes:
WebSocket

Fix race in pings during reads
Fix race in close frames during reads
Fix race when write suspends
Allow concurrent websocket async ping and writes

Codecov Report

Merging #2034 into develop will decrease coverage by -0.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #2034      +/-   ##
===========================================
- Coverage    67.25%   67.25%   -0.01%
===========================================
  Files          683      683
  Lines        49231    49231
===========================================
- Hits         33112    33109       -3
- Misses       16119    16122       +3

Impacted Files
Coverage Δ

src/ripple/protocol/impl/BuildInfo.cpp
82.6% <ø> (ø)
:white_check_mark:

src/ripple/core/impl/JobQueue.cpp
86.17% <0%> (-0.47%)
:x:

src/ripple/app/ledger/impl/LedgerMaster.cpp
44.41% <0%> (-0.23%)
:x:

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 460dd8f...0b605b3. Read the comment docs.


Combine rewritePackages and rewritePackagedFiles

Motivation

rewritePackagedFiles runs in parallel, rewritePackages does not. There's no functional reason why they can't both run in parallel, as part of the same pass. Saves about 4s in the packager pass.
Test plan

Ran existing tests, also tested on Stripe codebase.
Before:

After:

See included automated tests.
cc @jvilk-stripe @nroman-stripe

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_Kh6QLjgLMfiG2J
→ https://go/builds/bui_Kh6QjO6MqT1FtV


Issue2088 - Add functionality for School/Department for an organisation.

Add functionality for School/Department for an organisation.
Changes:
- added a Department model whose instances belong to an org and require name.
- added a DepartmentController and views for create, edit/update and a index view which is a tab
of 'Organisational Details'.
- added the optional attribute department_id to User model.
- added Rspec tests.

Updated app/controllers/registrations_controller.rb, app/models/org.rb and
app/models/user.rb to get rid of outstanding Rubocop warnings

Fix for issue #2088.
Based on changes requested in closed temporary PR
https://github.com/DMPRoadmap/roadmap/pull/2133

@briri will work on it tomorrow.


Hello, I need help. I am unable to run the code can you please help me in doing that

I have downloaded python, webdriver, vs code. But , i dont know how to setup them . please help me int that.

Clone the repo to a directory and run “py main.py”

a new version was released. easier to run.


Knowledge base & Add new question not working

i've got the following parts not working , knowledge base

Create a new question

the end-user functionality seems to work as expected only the expert functionality especially these two parts that aren't working... appreciate any insight on how i can troubleshoot this error..thank you!

I have the same type of issue.

Thank you for reporting this. Seems like there would be some deployment issue. Please validate tenant Id in App Service configuration in Azure portal. It should be tenant Id of tenant where manifest is installed.
Please review other configuration values and manifest values as well.
Let us know if issue still persists.


Added packaging to Jenkinsfile

Need to test this in Jenkins

@akilaMD
It's ready, right? I'm going to merge it.

@akilaMD
It's ready, right? I'm going to merge it.

Yes it is. Feel free to merge it.


Windows version?

Is there a windows version of these scripts? If so, where?

Hi,
We currently don't have windows version of these samples.
Thanks,
Surya.


osbuild: use osbuild_cli directly as main entry

Instead of having a another indirection via main_cli, directly use osbuild_cli in as main function in __main__.py. Compared to main_cli osbuild_cli also does indeed return a value that can be given to sys.exit in __main__.

@gicmo Can you rebase on master and rerun the CI? I'd be ready to merge this.

(I triggered a rerun manually now. Lets see whether it works without a rebase.)


Run functional tests on CI

...you mean unit tests

Add this as the very first step to resolve dependency problems.
      - name: "Set default PHP version"
        run: "sudo update-alternatives --set php /usr/bin/php7.4"

We don't have unit tests for this specific project 😅

You're pushing so hard GitHub gets red hot!
May I help?

Very bad news 😿 Upstream error?

@szepeviktor yes. May you try with this fix https://github.com/codelicia/xulieta/pull/70?


Add RBQFetchedResultsControllerTests.m

I've added test code for RBQFetchedResultsController.
This also contains the test of related to this (https://github.com/Roobiq/RBQFetchedResultsController/pull/21) in this test case

:+1:


[webapi] Add WebAudio test with rebase M49

BUG=https://crosswalk-project.org/jira/browse/XWALK-6545

Pls don't merge before M49, as they need to debug.


npm driver - infinite recursion causes memory leak / crash

I was analyzing some sites and found this one, where wappalyzer would get stuck – the chromium process would be taking all the CPU and memory.
After some debugging, I found the root cause to be in the getJs function, where it is dereferencing the window object, and because the site has added more custom functions/objects to Object's prototype, the function got stuck, recursively adding a huge number of properties on all objects...
An easy fix would be to add hasOwnProperty check to line 79:
if(!obj.hasOwnProperty(key)) return;

I checked a few other sites with this change and it worked well, but it's possible it might break detection for some other technologies.
Another option might be using for example JSON.prune package, or adding a timeout for evaluating the script.
Or, if possible, evaluate processJs (or the part of the function that accesses window) directly on the page where it has access to window.
Platform

NPM

Fixed in 088590b0661029138ac90950df988001d2f53e81 and v6.0.10, thank you!

You're right about moving the evaluation onto the page, not sure why I didn't do it like that in the first place. Fixed again in v6.0.12.


Allow DeleteBehavior to be reset to the default

Breaking out of #12661
For example, by allowing null to be set in the fluent API.
Note that the value in core metadata is not nullable, so this means either making it nullable as well (which would be a more significant break) or causing null in the fluent API to re-run the convention logic used if no value has been set.

Note that setting it to null will just reset the value to the model default, it won't rerun the conventions that might have modified it. To achieve that we would either need default value conventions  or metadata layering (part of https://github.com/aspnet/EntityFrameworkCore/issues/214) where higher configuration source would not remove the lower source value, but just hide it.


console action "actionS" runs twice

What steps will reproduce the problem?
run actionS(){} as console action
What is the expected result?
runs twice
What do you get instead?
not using this action name in app
Additional info
\yii\base\Controller::createAction
_protected/vendor/yiisoft/yii2/base/Controller.php:223
$actionMap = $this->actions();

Q
A

Yii version
<IP_ADDRESS>.

PHP version      7.0.33

Operating system

actions() is reserved method name, you can't have actionS() as action method name. The only way to have action s is to define it inside of actions() as a standalone action class.

actions() is reserved method name, you can't have actionS() as action method name. The only way to have action s is to define it inside of actions() as a standalone action class.

Sure, but I did not find mention of this in the documentation

@rob006 I don't really understand the relationship between the actions and actionS method names since they can be used separately as a method.
This seems more like a mistake, but if not, it's really missing from the documentation.

I don't think there is a good way to mention it.

@rob006 any suggestion?

As  a note in "inline actions": https://www.yiiframework.com/doc/guide/2.0/en/structure-controllers#inline-actions ?

@oleyur would you please provide exact code on how you are defining your action?


Support session token

This allows users to use ec2 instance roles.   A more detailed implementation would query the metadata services directly to fill in the information directly.  Regardless, this is the bare minimum implementation.  Requires an updated aws-request-signer, which was released four months ago.

i didn't update the poetry.lock file, so the tests fail.  not sure if you'd want my poetry.lock anyway, as it looks quite different after running an update.

@toppk nice changes, will be better then you add some sentences to the README about it.

i didn't update the poetry.lock file, so the tests fail. not sure if you'd want my poetry.lock anyway, as it looks quite different after running an update.

Just run poetry update aws-request-signer this should change the minimum packages. BTW, for me it’s not a problem to update the lockfile completely.

okay, I thought it would be confusing to add token to the Usage section, so I documented it down below.
I updated the lock file, and it seems like category is going away from poetry.lock as documented here:
https://github.com/python-poetry/poetry/issues/5702

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.053%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
301

Relevant Lines:
338

💛  - Coveralls

released in version 0.8.7


Allow multiple packs images

Hello Maintainers,
this PR adds the option to use multiple st2 packs-images.
This is a breaking change, as value st2.packs.image is replaced by st2.packs.images. Datatype changes from dict/hash to list of dicts/hashes.
This is useful, when a lot of different packs are being used, as a single container can result in multiple GB very quickly, mostly due to virtualenvs.
When using multiple st2 pack-images, the User can reduce possible downtimes due to reduced image size of new/changed containers. Also the build process can be a lot faster, if the User is providing custom packs.
Currently there is a fail message implemented in templates/deployments.yaml to prevent Users from accidential removal of their custom st2packs-image. It triggers, when st2.packs.image is defined and not empty. This should notify all Users about this change.
In #118 & #160 a centralization of packs-specific definitions for this chart was shown. As these PRs are still being discussed for other reasons, I've decided to include these centralizations in this PR.
This should make these PRs a little smaller and more compatible to each other, once they will or will not be finalized.

Rebased to current master, should now be mergeable again :)

Rebased to current master, should now be mergeable again :)

Hey @armab
Finally rebased and tested it again - should be mergable again :)


ASP.NET Core du routage éblouissant

French documentation says "éblouissant" instead of Blazor. It sucks…

https://docs.microsoft.com/it-it/aspnet/core/blazor/routing?view=aspnetcore-3.0

For example, the Italian documentation do not have this problem…

https://docs.microsoft.com/fr-fr/aspnet/core/blazor/routing?view=aspnetcore-3.0

@JasonCard can you please take a look at this feedback for the ASP.NET Core localized docs? Is there a way to ensure that Blazor never gets translated in those docs since it's the product name?
/cc @guardrex @Rick-Anderson @scottaddie

There must be a list of words not to translate, for the repo, org wide ?

@vintzl  Ce sont des commentaires très précieux. Merci d'avoir pris le temps de créer un problème.

@mairaw Yes, we can follow up on this issue, so the product name "Blazor" won't get translated.
@DavidPrio could you please help to follow up on this loc issue reported in en-us repo?
cc @Rick-Anderson

Hello, @vintzl
Thank you for your feedback.
We are actively reviewing your comments and will get back to you soon.
Kind regards,
Microsoft DOCS International Team

@mairaw @JasonCard @Rick-Anderson
We are working in this issue.
For a long term solution we suggest the term to be blocked in the source page to avoid its translation in the future.
@DavidPrio @Gonzalo-Salines

@CeciAc  by blocked to you mean `code fenced`?

Either that or the new no-loc feature.

@mairaw that's correct
https://review.docs.microsoft.com/en-us/help/contribute/markdown-reference?branch=master#non-localized-strings

We should create a feature request to support a .no-loc file, like .gitignore that doesn't loc any of the words in the file.  Blazor is used thousands of times. We can't expect customers to know about this. Adding Blazor once to a .no-loc file file is an more elegant solution.
Alternative, add meta-data
---
no-loc: Blazor, foo, bar
title: the title
description: Get an
author: rick-anderson
---

The ignore file approach seems best.

Looks like that's supported
author: cillroy
no-loc: [Global, Strings, to be, Ignored]

@CeciAc  once you approve https://github.com/aspnet/AspNetCore.Docs/pull/15171 we'll add that to all the Blazor docs via https://github.com/aspnet/AspNetCore.Docs/issues/15172

Hi @Rick-Anderson @mairaw As long as all instances refer to "Product" named Blazor, this is not localizable. Linguistically speaking, there is no need to include the term in the localization HOs. If no technical issues, I believe you can go ahead with the change. However, I would like MS Loc PM @JasonCard to approve this. Thanks!
@SunnyDeng cc

Not sure if I follow @DavidPrio. If it's not localizable, why is getting localized then?

I think @DavidPrio meant to say that product name should not be localizable, and recommends the use of no-loc metadata as long as long as all instances of "Blazor" is product name.
@CeciAc The no-loc metadata syntax in aspnet/AspNetCore.Docs#15171 looks correct, so please go ahead to approve. If it does not work for some reason, then we should follow up with a bug.
cc @Rick-Anderson @mairaw @SunnyDeng @bodhigautam

Hi everyone.
You still have some bad outputs…
try this in Bing or Google:

blazor site:docs.microsoft.com  éblouissant

here a sample:

https://docs.microsoft.com/fr-fr/aspnet/core/blazor/hosting-models?view=aspnetcore-3.1

@vintzl I've moved that to https://github.com/aspnet/AspNetCore.Docs/issues/16273. We don't work closed issues. It's best to open a new issue using the This page feedback button+form at the bottom of any topic (English repo tho; otherwise, it goes to the localization team).


RecordedData in to Wavesurfer.js

I'm having trouble understanding how I can get the recordedData from videojs-record into Wavesurfer-js
I'm storing the recordedData blob in IndexedDB and that's all fine, but when I retreive it and try to load it into Wavesurfer-js using loadBlob I just get an error in the console:
TypeError: t is undefined[Learn More] wavesurfer.min.js:6:47681
HTTP load failed with status 404. Load of media resource https://rss-developer:444/[object%20AudioBuffer] failed.

Of course at this point it doesn't load anything and this is with the latest videojs-record and wavesurfer-js. I'm using Firefox but it does the same in Chrome as well. I haven't tried any other browsers as I'm sure it's not a browser related issue.
Is it possible to move the recordedData immediately to an instance of Wavesurfer-js, and if so, how is it done?

but when I retreive it and try to load it into Wavesurfer-js using loadBlob

@Ziggy2001 can you show the code you're using to achieve this? also use the non-minified version of wavesurfer.js so we get a better error message.

Sure this is the code I use to retreive the data from the IndexedDB:
//Get the blob data
var tx = db.transaction('audio', 'readonly');
var audio = tx.objectStore('audio');
var request = audio.get( uid );

request.onsuccess = function(e) {
   wave.loadBlob( request.result['data'] );
};

This is the code I use to save it in the IndexedDB:
  var transaction = db.transaction(['audio'], 'readwrite');
  var audio = transaction.objectStore('audio');
  var item = {
    uid: uid,
    data: vtplayer.recordedData,
    created: new Date().getTime()
  };

 var request = audio.put(item);

Hope that's of some use. I'll try using the non-minified version as well to see if I get a clearer message.

have you tried without indexeddb?

I did try loading the recordedData directly in using loadBlob but that didn't seem to want to work either. It gave the same TypeError: t is undefined error.
I've just tried using the non-minified version but oddly it's giving me two new errors:
SyntaxError: import declarations may only appear at top level of a module wavesurfer.js:1
TypeError: WaveSurfer.create is not a function

Okay I've managed to figure out a way around this issue by simply creating a createObjectURL blob from the stored data in the IndexedDB which is brilliant. However, the reason I'm trying to do all this is because in Chrome dataURLs have seek problems when you try to set the seek. For example you will try to seek to the middle of the file and it'll go to just before the end. I think it's to do with the server not providing the Accept-Ranges: bytes header on blob urls. If anyone has any ideas on how to resolve this then please let me know.

good to hear. You should use the ts-ebml plugin to inject metadata and make the file seekable.

Thanks for this. I have tried it but the further issue I have is I need the audio to be wav, not webm.