Created A New Dedicated Contact Page

Created A New Dedicated Contact Page

Closes Issue #718

Can u pls add required screenshots to review @swarnade

This Are the Sample Image Have a Look

Hey, remove the 1st screenshot section. Becos the layout of that doen't look  good. Let only the contact section & footer & navbar be. And also change the title of the page, like it is showing OS-COde| chapters na...

@akshathar-navada  Done All Changes According To Your Requirement.

Hey we need something like this, with proper layout , only navbar, contact section and the footer


Support 'Delete' eviction policy for Azure Spot Standalone VMs

Is your feature request related to a problem? Please describe.
Currently Azure Spot standalone VMs only support eviction policy of 'Deallocate'. We have made changes in the CRP service for standalone Spot VMs to support 'Delete' eviction policy as well. Changes need to be made in JAVA SDK should to support this.
Describe the solution you'd like
Currently JAVA SDK blocks choosing 'Delete' eviction policy for Standalone Spot VMs. Changes need to be made to support this. Here is the link to the swagger PR for this change: https://github.com/Azure/azure-rest-api-specs/pull/9743
Describe alternatives you've considered
NA
Additional context
Swagger PR: https://github.com/Azure/azure-rest-api-specs/pull/9743
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[ ] Description Added
[ ] Expected solution specified

@rakeshakkera Thanks for the update. I have added new commit with the mentioned changes.

Close this as supported.


[do-not-merge] Add guide actions and explanation of state to top of page

This shows the user what state the guide is in, and allows them to easily
review/publish it.

This is not going to be used anymore: https://trello.com/c/QAu4Eggt/96-fix-create-a-new-guide-edition-workflow


Make satelitelink loop supervised by watchdogs

Is your feature request related to a problem? Please describe.
Make satelitelink loop supervised by watchdogs
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Fixed


Extension does not apply color scheme on new page load, requiring a reload to appear

Starting about a month ago, Midnight Lizard will not reliably inject the color scheme when opening a new page. Reloading the page is necessary for the scheme to be applied. I'm not sure how to go about troubleshooting this. Can anyone offer some guidance?
Windows 10, using Brave v1.48.122 (Chromium 109.0.5414.87)

I recently started using this extension.  Has it been going on this long?  I'm noticing now that it doesn't even seem to properly disable itself when the global on/off switch is off--it still breaks GitHub's appearance and I have to reload the page to fix it.  Time to uninstall, I guess.

@pavel-agarkov You seem to be talking about custom "new tab" pages.  That is not what this issue is about.  This is about the extension just not working sometimes, but then it does work after reloading the page.

oh, yeah, I had problems with global disable functionality as well but did not have time to debug it.
But I did not have any examples when Midnight Lizard would not apply a scheme.
If it is happening for a particular website please try to remove it's settings (Global settings->Delete current website settings)
If it is randomly happening for different websites please send me console logs from that page - maybe I can spot errors there...

I stopped using the extension months ago after it became intermittent and I got no replies to this issue

@pavel-agarkov For me, it often happens on GitHub's notifications page:

I load the notifications page.  Everything seems fine.
I click a notification.  Everything seems fine.
I click the back button.  I see the list of notifications, but the background color of the BODY element is wrong (white, when my GitHub settings enable its own dark mode), and none of the elements on the page do anything when clicked.
I refresh the page, and everything works fine.

I suspect it may be related to the usage of the HTML5 history API; maybe Midnight Lizard isn't correctly recognizing when a tab has changed location and isn't applying its changes correctly, or something like that.
Anyway, like dziban303, I had to uninstall the extension, because even when I had it globally disabled, the problem on the GitHub notifications page persisted.  It was doing more harm than good, for my usage.  I'm afraid I can't provide more information than that.


Scrollbar does not align well on iPhones in Horizontal orientation

Steps to Reproduce

Modify the flutter gallery app, inside material/backdrop_demo.dart, remove the horizontal padding from the ListView(so the problem can be visible).
Run the app on an iPhone.
Rotate iPhone to horizontal orientation, scroll the list and observe the scroll bar. The scroll bar does not align to the right of the ListView, and block the content.

I have tested it on iPads and Android phones, they all worked perfectly.
This problem is causing my app's scroll bar blocking some of the scrollable contents which is not expected.

Target Platform: iOS
Target OS version/browser: iOS 12.4.1
Devices: iPhone Xs
Logs
[✓] Flutter (Channel beta, v1.12.13+hotfix.6, on Mac OS X 10.15.1 19B88, locale zh-Hans-CN)
    • Flutter version 1.12.13+hotfix.6 at /Users/chuangkegongchang/flutter/flutter
    • Framework revision 18cd7a3601 (7 days ago), 2019-12-11 06:35:39 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/chuangkegongchang/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3, Build version 11C29
    • CocoaPods version 1.8.3

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 39.0.3
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] Connected device (2 available)
    • Pixel 3a    • 942AY0J30K                               • android-arm64 • Android 10 (API 29)
    • ITHOAD01008 • 502b79899779568a0a171fc8a8c19c7e63d845a8 • ios           • iOS 13.1.3

• No issues found!

CC @LongCatIsLooong

Hi @TomassMaximum
if the issue persist with the latest stable version of flutter
could you please provide your updated flutter doctor -v ,
your flutter run --verbose
and if possible a reproducible minimal code sample.
Thank you

Hi @TomassMaximum
Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore
reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any
more information for us; we will reopen it right away!
Thanks for your contribution.

Accidentally closed, my bad

This is a duplicate of https://github.com/flutter/flutter/issues/25802. Closing.


Create an issue template

Inspired from https://github.com/iiitv/algos/issues/254 , I think we can create an issue template which will guide users when creating an issue. It can contain checklists to make sure a proper issue is created.

Assign me


anchore.io analysis online stops, will this project remain working?

Hi,
the website anchore.io says:
" In the coming weeks we plan to end-of-life the Anchore.io online analysis service.".
does this mean the open-source engine will stop working somehow? Or is this service indepedent of the online service?

Hi @hanscees and thank you for your enquiry!
We have made the decision to end-of-life our online Anchore.io service in order to refocus product development efforts on our Anchore Enterprise product.
But please be assured that this specific change will have no effect whatsoever on any of our open-source offerings and service dependencies, which will remain fully supported and continuously developed!

I'm going to close this issue with the assumption that the enquiry has been satisfactorily answered.
However, if you have any additional questions related to this topic, please don't hesitate to reopen the thread (or create a new one). Thanks!


Can I add the restriction function to the Run pipeline button

What is version of KubeSphere DevOps has the issue?
ks3.2.1
How did you install the Kubernetes? Or what is the Kubernetes distribution?
kubekey
Describe this feature
At present, there is no click limit on "Run" in the building pipeline UI interface, which will cause developers to click and run continuously at the same time. We hope to increase the limit. For example: Disallow second clicks while the build is running
Additional information
No response

Will this check button be helpful？


How to close datepicker when click outside?

How to close datepicker when click outside?
I want a standart behaviour.
Thank you.

This is already the standard behavior of the datepicker

Unfortunatelly, in my case the datepicker closes only if I press Esc. Can you tell me in which cases it's possible?

It's hard to say without seeing your code -- it's possible that another plugin is removing/disabling the click handler on the document, which this component relies on to close the picker.

@ilya4544 Did you ever figure this out?


Problems about validation AP in DDP mode with frozen BatchNorm

Hi,
I am fining tuning from YOLOX models. And I freeze all the BatchNorm2D layers as follows:
self.model.module.backbone.eval()
self.model.module.head.cls_convs.eval()
self.model.module.head.reg_convs.eval()
self.model.module.head.cls_preds.eval()
self.model.module.head.reg_preds.eval()
self.model.module.head.obj_preds.eval()
self.model.module.head.stems.eval()
And I find validation AP is very low when I use multiple cards in DDP mode, and it's ok when I use a single card without DDP. I think the only major change I made to the original YOLOX code is to freeze BatchNorm layers. Please could you provide some suggestions on possible causes? Thank you very much.

No worry. Just find I did not gather the validation outputs correctly.


Nullable embeddable's getting hydrated to undefined

Describe the bug
A nullable object embeddable like this:
@Embeddable()
export class Permissions {
    @Property()
    foo!: string;

    @Property()
    bar!: number;
}

// Used in
export class User2 {
    // Other properties...
    @Embedded(() => Permissions, { object: true, nullable: true })
    permissions: Permissions | null = null;
}

Will be returned from a repository find call with permissions being undefined.
Given the type constraint and the default to null this was unexpected behaviour that caused a bug for us.
To Reproduce
See above
Expected behavior
Expected it to be null.
Additional context
Add any other context about the problem here.
Versions

Dependency
Version

node
16.13.1

typescript
^4.5.5

mikro-orm
^5.0.5

postgres
^5.0.5

That's weird, for regular entity properties it should work this way, so indeed a bug. Note that it won't work for nested embeddables, only for properties that actually represent a database column (with nested embeddables you would have to have the null stored in the JSON, then it would be hydrated as null). Also note that the property initializer is not used for hydration of existing entities.

If object is false it creates the columns permissions_foo and permissions_bar which are both nullable. If one of them is null (or both like when permissions is set to null) i expected it to be hydrated to null but i found undefined. If permissions is explicitly set to null it fails on flush inside nativeInsertMany (AbstractSqlDriver).
        const props = [...set].map(name => meta.properties[name] ?? { name, fieldNames: [name] });
        const fields = core_1.Utils.flatten(props.map(prop => prop.fieldNames));

name is permissions (!= permissions_foo and permissions_bar) which leads to an undefined inside fields.
Is it forbidden to declare an embeddable nullable without also setting object to true?
@Embeddable()
export class Permissions {
    @Property()
    foo!: string;

    @Property()
    bar!: number;
}

// Used in
export class User2 {
    // Other properties...
    @Embedded(() => Permissions, { object: false, nullable: true })
    permissions: Permissions | null = null;
}

If object is false it creates the columns permissions_foo and permissions_bar which are both nullable

If your embedded property is nullable, all its properties are nullable at the schema level, nothing we can do about that in inline mode. And with nullable db column you always get it hydrated to null, that is how SQL drivers work.

It was not about the nullable columns but situations where it is undefined instead of null or setting it to null breaks flush. Hopefully the following test cases are helping. I ran it on the current master.
import { Embeddable, Embedded, Entity, MikroORM, PrimaryKey, Property } from '@mikro-orm/core';
import type { PostgreSqlDriver } from '@mikro-orm/postgresql';

@Embeddable()
export class A {

  @Property()
  alpha!: number;

  @Property()
  beta!: number;

}

@Entity()
export class B {

  @PrimaryKey()
  id!: number;

  @Embedded({ entity: () => A, object: false, nullable: true })
  a!: A  | null;

  @Property()
  v!: boolean;

}

@Entity()
export class C {

  @PrimaryKey()
  id!: number;

  @Embedded({ entity: () => A, object: false, nullable: true })
  a: A  | null = null;

  @Property()
  v!: boolean;
}

describe('GH issue XXXX', () => {

  let orm: MikroORM<PostgreSqlDriver>;

  beforeAll(async () => {
    orm = await MikroORM.init({
      entities: [A, B, C],
      dbName: `mikro_orm_test_gh_xxxx`,
      type: 'postgresql',
    });
    await orm.getSchemaGenerator().ensureDatabase();
    await orm.getSchemaGenerator().dropSchema();
    await orm.getSchemaGenerator().createSchema();
  });

  afterAll(() => orm.close(true));

  test('B', async () => {
    let e = orm.em.create(B, { v: false });

    // eslint-disable-next-line no-console
    console.log(e.a); // undefined => expected null

    await orm.em.persistAndFlush(e);

    // eslint-disable-next-line no-console
    console.log(e.a); // undefined => expected null

    orm.em.clear();

    e = (await orm.em.find(B, { v: false }))[0];

    // eslint-disable-next-line no-console
    console.log(e.a); // undefined => expected null

    e.a = null;
    e.v = true;

    await orm.em.flush(); // runs smoothly

    orm.em.persist(orm.em.create(B, { v: false }));
    orm.em.persist(orm.em.create(B, { v: false }));

    await orm.em.flush(); // working, because a is not set

    orm.em.persist(orm.em.create(B, { v: false, a: null }));
    orm.em.persist(orm.em.create(B, { v: false, a: null }));

    await orm.em.flush(); // TypeError: Cannot read properties of undefined (reading 'replace')
  });

  test('C', async () => {
    let e = orm.em.create(C, { v: false });

    // eslint-disable-next-line no-console
    console.log(e.a); // null

    await orm.em.persistAndFlush(e);

    // eslint-disable-next-line no-console
    console.log(e.a); // null

    orm.em.clear();

    e = (await orm.em.find(C, { }))[0];

    // eslint-disable-next-line no-console
    console.log(e.a); // undefined => expected null

    e.a = null;
    e.v = true;

    await orm.em.flush(); // runs smoothly

    orm.em.persist(orm.em.create(C, { v: false }));
    orm.em.persist(orm.em.create(C, { v: false }));

    await orm.em.flush(); // TypeError: Cannot read properties of undefined (reading 'replace')
  });

});

@B4nan Just for clarification, it is now clear to you what i meant and you approve my expectations?

Well, the first two "assertions" in the first test are wrong, B.a is supposed to be undefined, as the entity was just created/flushed, that is correct/expected behaviour. We dont fill null anywhere, it needs to come from you (constructor/property initializer) or from the database.
The fact that the flushing throws is a bug for sure. The third assertion that tests entity returned from database looks suspicious, but it might be an implementation edge case


django-pgtrigger package isn't recognized correctly

Describe the bug
django-pgtrigger package package is marked as obsolete by deptry even even though it's actually imported. The problem might be that import name doesn't match the package name (as per their documentation).
To Reproduce
Steps to reproduce the behavior:

Install django-pgtrigger
In some *.py file add import pgtrigger
Run deptry with default configuration. It will r

Expected behavior
deptry should recognize that package pgtrigger is a name of a package exposed by django-pgtrigger installation
System [please complete the following information]:

OS: e.g. macos 12.4
Language Version: 3.9.6
Poetry version: none

Additional context
None

Thanks for raising the issue.
The problem here is that installing django-pgtrigger adds (at least) two directories to the site-packages directory in the virtual environment. django-pgtrigeer has associated metadata, but pgtrigger does not:
site-packages git:(main) ✗ ls | grep pgtrigger
django_pgtrigger-4.5.2.dist-info
pgtrigger

➜  site-packages git:(main) ✗ tree django_pgtrigger-4.5.2.dist-info
django_pgtrigger-4.5.2.dist-info
├── INSTALLER
├── LICENSE
├── METADATA
├── RECORD
├── REQUESTED
└── WHEEL

0 directories, 6 files

➜  site-packages git:(main) ✗ tree pgtrigger
pgtrigger
├── __init__.py
├── __pycache__
│   ├── __init__.cpython-39.pyc
│   ├── apps.cpython-39.pyc
│   ├── compiler.cpython-39.pyc
│   ├── contrib.cpython-39.pyc
│   ├── core.cpython-39.pyc
│   ├── features.cpython-39.pyc
│   ├── installation.cpython-39.pyc
│   ├── migrations.cpython-39.pyc
│   ├── models.cpython-39.pyc
│   ├── registry.cpython-39.pyc
│   ├── runtime.cpython-39.pyc
│   ├── utils.cpython-39.pyc
│   └── version.cpython-39.pyc
├── apps.py
├── compiler.py
├── contrib.py
├── core.py
├── features.py
├── installation.py
├── management
│   ├── __init__.py
│   ├── __pycache__
│   │   └── __init__.cpython-39.pyc
│   └── commands
│       ├── __init__.py
│       ├── __pycache__
│       │   ├── __init__.cpython-39.pyc
│       │   └── pgtrigger.cpython-39.pyc
│       └── pgtrigger.py
├── migrations.py
├── models.py
├── registry.py
├── runtime.py
├── utils.py
└── version.py

5 directories, 32 files

Therefore, deptry will fail to find the associated metadata for pgtrigger, and fall back to guessing that the corresponding package name is pgtrigger, which in this case is wrong. (A similar thing happens with the google packages, but there falling back to google is successful, see https://github.com/fpgmaas/deptry/issues/5)
I will need to investigate exactly why it is that it was decided that pgtrigger does not have associated metadata. But I am afraid that in this case, since AFAIK there is no information on the system  linking django-pgtrigger to pgtrigger, there is no way for deptry to make the link between the module and the package, and using ignore_obsolete in pyproject.toml is the best solution I can offer for now.
If someone has any idea if it's possible to link django-pgtrigger to pgtrigger, I'm interested to know so we can add another method to link packages and modules if no metadata is found.

Some things I want to investigate here, when I have the time:

Why does django-pgrtrigger use the folder structure it currently has in site-packages?
It seems that Poetry (django-pgtrigger used Poetry to publish) never adds a top-level.txt to the directory. Why? Should we raise an issue for this in Poetry?
Would having a top-level.txt have sufficed for deptry to recognize this package?

It's simply caused by the following specification in pyproject.toml:

[tool.poetry]
name = "django-pgtrigger"
packages = [
  { include = "pgtrigger" }
]

It seems top-level.txt is only added by setuptools, Poetry does not add this.
Yes.

I discovered that the metadata file RECORD also contains information that we could use. it's description is: RECORD: records the list of installed files..   I will try to build a solution using this.

This should now be solved in release 0.5.2


If saving BinaryTempBody fails, check the cache folder structure exists - if it doesn't, recreate and try again

Please search to check for an existing issue (including closed issues, for which the fix may not have yet been released) before opening a new issue: https://github.com/k9mail/k-9/issues?q=is%3Aissue
Expected behavior
New emails should appear in the Inbox until deleted or pushed off the bottom
Actual behavior
Phone appears to be polling normally, then, recent emails are no longer visible and new emails are not being received.  A Synchronizing Disabled message may appear for in instant.  Under the Inbox, the message: "ErrnoException: open failed" remains constant.  To resolve the issue, I use TaskManager to stop K9 and then upon restart, K9 Mail runs normally.  Emails that came and went, now re-appear is if they are new.
Steps to reproduce

I do a cold start in the morning.  First occurrence of ErrnoException may happen around noon.
I have the same issue on another identical phone which uses a different Email provider
K9 Mail has been used successfully on this phone for over 3 years with no issues.

Environment
K-9 Mail version: 5.206
Android version: 4.1.2
Account type (IMAP, POP3, WebDAV/Exchange): IMAP
k9mail.txt

How much storage do you have left on the device. It's failing to create a temporary file.

Hello Philip
The phone is reporting 613 MB available.  The one clue that I can’t emphasize enough is that it works for about a 1/2 day perfectly.  Yesterday, I used Task Manager to stop K9Mail and it suddenly started working again.  It’s working perfectly right now.
I really appreciate your help with this.  K9mail has been a wonderful tool since January 2014!

In another unrelated but unexpected occurrence, I completely uninstalled K9Mail in order to do a fresh install of version 5.206 as part of troubleshooting the above problem.  When I used the previous version’s settings, K9 Mail would not start.  There was a blip on the screen and then it was gone.  Unfortunately, I didn’t capture a log.  I simply reconfigured the account manually.

Wayne Davis
From: Philip
Sent: Thursday, April 06, 2017 3:45 AM
To: k9mail/k-9
Cc: daviwph ; Author
Subject: Re: [k9mail/k-9] Issue fetching New Emails typically after several hours of success - ErrnoException: open failed (#2486)
How much storage do you have left on the device. It's failing to create a temporary file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I have some information that might help:
My phone has a “Task Manager” which came factory installed and not present on the market.
I’ve used it to kill processes that linger in the background from Google Maps and Chrome.
It also has an automatic “Clear Ram” function that can be set to “Optimize Ram” every hour.
To the best of my recollection, I’ve used the “Clear Ram” automatic function for the past 3 years.
Observations:
Running “Clear Ram” manually will restart the K9Mail PushService
Running “Clear Ram” manually will clear the ErrnoException: open failed condition
Setting “Clear Ram” to not run automatically may prevent ErrnoException: open failed from happening
Out of curiosity, is the temporary file in RAM or in the phone’s DATA section?
If it’s in RAM and “Clear Ram” removes the reference, it may be causing this unrecoverable error.  Just a wild guess.

It's a file. It's almost certainly stored in a /tmp folder or similar.
That said, if you're running applications that interfere with Android's memory management you're going to see unpredictable problems which we can't reasonably support.
We do our best to fix memory leaks and so on. You shouldn't need to be doing stuff that kills our code abruptly - Android will automatically clean up stuff if it needs to and we test that we behave reasonably.

If this can be reproduced without that thing running feel free to re-open this.

Thank you Philip,
Yes, it’s OK now and I must reply with a red face.
I found the temp file location in the data folder under /com.fsck.k9/cache

As many times over the years we have seen the message “No such file or directory”, I think it’s safe to say that sometimes there is no such file –because- there is no such directory.  In this case, I believe the sub-directory cache was deleted.  When K9 is starts, it will create a sub-folder /cache/ if there isn’t one and will go on with life.  If /cache/ is deleted in while K9Mail is running, it will try to create a file on a folder that doesn’t exist and we know that will never work.
So yes, I suffered from a self-inflicted wound.  At the risk of sounding like a patch, wouldn’t be wonderful if K9Mail could reinitialize the cache folder as it does when it first starts when open failed occurs.  Then, it could deliver a notification that would say:  “You tried to break me but I’m much smarter than you are”
Thanks for your help!

I ran into the same problem today on a Samsung Galaxy S4 - no new mail showing up in the Inbox with the error as reported above.  I am not using any sort of Task Manager.  However, I did clear the system cache yesterday when I noticed disk space was only about 400MB.  Rebooting the phone got K-9 working again.
I second the suggestion that K-9 should handle this situation more gracefully.

I've re-opened it, but in my view it's really low priority - if you're messing around with the file system on Android and not using the inbuilt 'Clear Cache' method then you ought to know what you're deleting. It's like doing rm -r on an application's folder and expecting the application to be fine.

Hi Philip, I was using the Android 'Clear Cache' command.

Ah okay, we should definitely handle that :(

Hello -
I confirm that bug still exists - installed some weeks ago K9-email, with two accounts on a LG G4 Android 6 -
Everything was ok until I accepted the "Smart Cleaning" yesterday suggested by Android (including deletion app cache).. then when syncing accounts I had "ErrnoException" stated below each folder - impossible to retrieve any email.
Only suppression of K9, re-installation (via F-Droid) worked.


Make password generator to generate secure passwords

It is not planned to 'convert' this app into a password manager. Therefore, this feature completely looses its relevance.


Russian locale and important fixes

Bug with "Edit user:" string fixed, now it should translates correctly.
Temporary fix for issue #230. Now translators can make various translations for "Unread" action and tab. In every non-English translation, except Russian, "Unread" action is now hard-coded as "Unread". Yes, it's dirty, but I don't know how to fix it without large refactoring. Be free to suggest other solutions, can include them into this PR.
Russian locale added.

Last commit also fixed nasty bug with truncating unicode characters which made tofus.
Before:

After:

Please, can you send the last commit in a separate pull-request against the current master since it's different than the translation work?
Regarding the translation, I prefer to wait that issues #230 and #229 are addressed. I will work on it in the next couple of days.
Thanks

@fguillot I sent #233, now will wait your refactoring. Can you notify me, please, when it will be done?


Add a metacat / data_dispatcher option equivalient for --dataset-definition

It would be --metacat-query xxx and would basically be equivalent to:  -e SAM_PROJECT=$(ddisp project create xxx)
which would start the project with data_dispatcher at launch time and pass its ID in SAM_PROJECT, letting the compatability
code in ifdhc 2_7 and later use data dispatcher calls to get the next file, etc.
Users would need data_dispatcher and metacat setup  to use this.

Discussion points:

Request: Add Classad Attribute or ENV that indicates in the job which data handler we're using (SAM or Metacat). We should coordinate this with POMS, fife_wrap, fife_launch, FIFE devs.
We should try to isolate the metacat-specific (and while we're at it, the SAM-specific code).  So our get_parser.py would, for example from metacat import BLAH) would have this arg (--metacat-query xxx`), call BLAH.  The same could be done for SAM-specific options.


sourcelookup not evaluating a source

For feature GB126 in sheet MM_kore1280 in grambank original sheet, there is a source listed as "Sohn (2015:324) Grammaticalization". I'm guessing this is because there is more than one work by Sohn from this year, and that it should be "Sohn_Grammaticalization (2015:324)". However, pygrambank sourcelookup doesn't seem to evaluate this source. When I run it on this sheet, I get:
Resolved sources:
155	g_Sohn_Korean	Sohn, Ho-min. 1994. Korean. (Descriptive Grammars Series.) London: Routledge. xvii+584pp.
120	g_Sohn_Korean_1999	Sohn, Ho-Min. 1999. The Korean language. Cambrige: Cambridge University Press. 462pp.
20	g_LeeRamsey_Korean	Iksop Lee and Ramsey, Robert S. 2000. The Korean Language. (SUNY Series in Korean Studies.) New York: State University of New York Press. xiii+374pp.

OK

Shouldn't it also check "Sohn (2015:324) Grammaticalization" and throw some kind of warning?

AFAICT Glottolog doesn't have anything by Sohn from 2015 in hh.bib. The problem here is that sourcelookup is happy as long as at least one reference can be matched per datapoint. So the unmatched Sohn (2015:324) Grammaticalization is simply read as some sort of comment.

Yes, I would want it to say that it tried matching Sohn 2015 to hh.bib or gb.bib and that it couldn't.
Right, okay. What can we do to change that? I know that sourcelookup already ignores things like "personal correspondence" etc, but in thise case we'd like it to try and resolve it (and fail).

Tha'd be great!
And maybe also some kind of warning for strings that include a space and something after the YEAR:PAGES. Like in this case the " grammaticalization".

fix pushed to master

Thank you

it used to be that the pygrambank cldf command ran sourcelookup on every sheet right, so that the output from there could be used for our "check warnings"-todo list. This is still the same with cldfbench right?

Okay, thanks. I'll try and re-install and run it so that I can update the to do list for automatic warnings.

cldfbench is complaining that the proto-languages, like ocea1241, doesn't have a macroaea. Is this something that mucks something up? Would you like me to submit a PR to glottolog/glottolog adding macroareas for family-level languoids?

Just  ignore this warning.
Hedvig Skirgård @.***> schrieb am Mi., 12. Jan. 2022,
17:53:

cldfbench is complaining that the proto-languages, like ocea1241, doesn't
have a macroaea. Is this something that mucks something up? Would you like
me to submit a PR to glottolog/glottolog adding macroareas for family-level
languoids?
—
Reply to this email directly, view it on GitHub
https://github.com/grambank/pygrambank/issues/51#issuecomment-1011251552,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGUOKETGZOQVCI2UDFGEQTUVWWW3ANCNFSM5LTMSQRQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Ok.

I can read in all the sheets line by line and then do a match to this output, but it'd be easier if it could report the sheet right away please.


Request for Assistance in Converting Project to functional based totally.

I have been working on my project using a different architecture, but after considering the benefits of functional programming, I have decided to switch to a functional-based approach. This transition will not only align with industry standards but also enhance the maintainability and scalability of my project.
I understand that functional programming promotes immutability, pure functions, and declarative code, which can lead to more predictable and easier-to-test applications. By embracing these principles, I believe my project will become more robust and efficient.
However, I am relatively new to functional programming and would greatly appreciate your guidance and expertise in refactoring my codebase. I am confident that with your assistance, I will be able to successfully migrate my project to a functional-based architecture.
I have already done some initial research and identified areas in my project that can benefit from functional transformations. By adopting higher-order functions, leveraging immutable data structures, and embracing functional composition, I hope to optimize the performance and readability of my code.
Once again, I want to express my gratitude for your willingness to support me in this endeavor. Your expertise and guidance will undoubtedly contribute to the success of my project. Thank you for your assistance and I look forward to working together on this functional conversion.

Hello @ansulagrawal ,
I can help. I suggest to split the codebase on tasks for better organization.

Hello @ansulagrawal ,
I can help. I suggest to split the codebase on tasks for better organization.

Hello @DamyanBG thank you for showing intrest.  For now you can fork the repo and start working on it.
Once we think you are good to go we will add you to colabrators.
Thanks once again.

@ansulagrawal I will start it these days. Can you tell me is that repo converted as package? I was not able to find it in npm...

https://www.npmjs.com/package/react-big-schedule
@DamyanBG here is the link for the npm package

Thank you!

Hello @ansulagrawal ,
I made the first PR. I refactored the class component HeaderView to functional component - #73
I have few suggestions:

please, create me task for every component which I will refactor for better tracking of the progress
I think there are few things which can be fixed in the logic of that component
I think it is good idea to add Prettier config file

This is from me for now. Maybe I will have more ideas these days.

Hello @DamyanBG ,
Yes I was also thinking for the same. You can procced with what all you want.
Nice suggestion by the way thanks.

So do you want me to split the work on smaller tasks and to add labels good-first-issue and help-needed? Usually there are a lot people who are looking for projects to contribute. If we split the work on smaller issues, then I think it will be better.

Sure lets do thaf

OK, I will do that these days

Hello @ansulagrawal and @JitendraSoni1234 ,
What is that non organization here? I refactored HeaderView component from class to functional. I can see that @JitendraSoni1234 committed some hotfix directly to the master branch :D and returned the previous class component. Isn't better to provide information about that hotfix and to see the problems behind it, to fix it and continue on the functional component. With organization like this be sure that this repo will have no feature.

@DamyanBG the code reverted back was done due to the header view was not working as expected as the date used to show invalid date.
Sorry for not informing you, but due to urgent requirement we did that.

Okay, give me the code example which broke the functional component and I will take a look.

I will create a code sandbox link and provide you

@DamyanBG check below image

Here is the link: https://codesandbox.io/s/suspicious-cdn-fzj624?file=/src/App.js:220-238

Okay, thank you for the provided information. I had a little mistake when refactored the code. I made a PR with working code. You can check.

Hello Team, we have decided to stop converting to functional based totally as its just of time waste and no one is free to do so. If any one want to do he/she can do it and raise the pr. But internal team won't be spending time on this anymore.

Regards React Big Schedule Team.


Show directions and traffic.

Hi can i show traffic and directions in this module?

Traffic is supported (check readme), directions are not supported (not even by wrapped sdks)


Add comments to files associated with the Welcome Dashboard

Added comments to the following files:

dashboardView.js
CurrentTask.jsx
CurrentTaskNotes.jsx
CurrentTaskTimer.jsx
TimerConfig.jsx
TaskList.jsx

I'm going to close this PR because it needs a rebase and is going to the wrong branch


Increment version for keyvault/azcertificates releases

Increment package version after release of keyvault/azcertificates

/check-enforcer evaluate


Issues in mobile Safari when used as Bootstrap input group

Previous discussion in this issue: https://github.com/Bluefieldscom/intl-tel-input/issues/148
And this pull request: https://github.com/Bluefieldscom/intl-tel-input/pull/161
Issue can be reproduced in this Codepen by uncommenting the JS line relating to the arrow div.
Issue: cannot open dropdown or even focus the input in mobile safari when the input is part of a Bootstrap input group. Problem seems to be with the arrow div - removing it after initialising the plugin fixes the problem. Needs further investigation, but I'm assuming it's a problem with the CSS triangle.

I did like the arrow. RIP arrow. Good work.

Update: it is the CSS triangle. Add this line of CSS to remove the triangle and fix the problem:
.intl-tel-input .iti-flag .arrow {border: none;}

I will continue to investigate and maybe file a bug with Bootstrap/Mobile Safari in due course.

I managed to whittle the test case down to this: http://codepen.io/jackocnr/pen/LEQNXx
And posted an issue with the Bootstrap guys here: https://github.com/twbs/bootstrap/issues/15842
I'll see what they say. The next job would be to extract the relevant CSS lines from the Bootstrap stylesheet and just post it on Stack Overflow and/or the Mobile Safari bug tracker, if one exists.

The Bootstrap guys confirmed the problem, but said it is a Webkit issue. So I managed to extract the 2 lines from Bootstrap required to reproduce the issue.
Codepen here: http://codepen.io/jackocnr/pen/LEdrxP
And posted an issue on the WebKit Bugzilla here: https://bugs.webkit.org/show_bug.cgi?id=141822 and also on bugreport.apple.com.
We'll see what they say. I also added a note to the readme about the workaround.

Very cool to see this issue continue to escalate! Good job!

Seeing as how this is definitely not an issue with this plugin (the Webkit issue has now been confirmed), and I've added a note/workaround to the readme, I'm going to close this issue now. Thanks for reporting it.


vite ssr - spaces in url leads to different req.pathname

Describe the bug
Making a request in SSR mode to http://localhost:5173/indextest/dangiel1 leads to the req.originalUrl looking like
/indextest/dangiel1
but making a request to http://localhost:5173/index%20test/dangiel1 (note the %20 space) leads to:
/@id/__x00__/index%20test/dangiel1
Reproduction
N/A
System Info
System:
    OS: macOS 12.4
    CPU: (10) arm64 Apple M1 Max
    Memory: 954.67 MB / 64.00 GB
    Shell: 5.1.16 - /usr/local/bin/bash
  Binaries:
    Node: 17.9.0 - ~/.nvm/versions/node/v17.9.0/bin/node
    Yarn: 1.22.15 - ~/.nvm/versions/node/v17.9.0/bin/yarn
    npm: 8.5.5 - ~/.nvm/versions/node/v17.9.0/bin/npm
  Browsers:
    Chrome: 103.0.5060.134
    Safari: 15.5

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

It's worth noting that my route handling is set up to handle a special root page:
  app.use(
    /^\/(.+)/,
    serverRenderRoute({ vite })
  );

  // Serve the index page at the root of the dev server.
  app.use(
    "/",
    indexPage()
  );

It doesn't reproduce with a simple setup. Please provide a reproduction.
https://stackblitz.com/edit/github-rfwq5p?file=src%2Fentry-server.js,server.js

Here's a reproduction - https://github.com/mkilpatrick/vite-ssr-react-base/tree/url-space. Start up the server and go to http://localhost:5173/about vs http://localhost:5173/about me.
It's related to inline modules and SSR.
[vite] Internal server error: Cannot read properties of undefined (reading '0')
      at Context.load (file:///Users/mkilpatrick/Desktop/vite-ssr-react-base/node_modules/vite/dist/node/chunks/dep-71eb12cb.js:41067:65)
      at Object.load (file:///Users/mkilpatrick/Desktop/vite-ssr-react-base/node_modules/vite/dist/node/chunks/dep-71eb12cb.js:35260:50)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at async loadAndTransform (file:///Users/mkilpatrick/Desktop/vite-ssr-react-base/node_modules/vite/dist/node/chunks/dep-71eb12cb.js:39751:24) (x3)
/@id/__x00__/about%20me?html-proxy&index=0.js
No routes matched location "/@id/__x00__/about%20me?html-proxy&index=0.js"

It's happening in the vite:html-inline-proxy load code.

It seems there is an inconsistency of filePath.
https://github.com/vitejs/vite/blob/937cecc7d89194d8672ab62beb92827f45764c15/packages/vite/src/node/plugins/html.ts#L62-L66
It reproduces with https://github.com/vitejs/vite/issues/9054#issuecomment-1183259223, too.


carthage update fails

 $ carthage update
*** Fetching ReactiveFoundation
*** Fetching ReactiveUIKit
*** Fetching ReactiveKit
*** Checking out ReactiveKit at "v1.0.8"
*** Checking out ReactiveFoundation at "v1.0.4"
*** Checking out ReactiveUIKit at "v1.0.6"
*** xcodebuild output can be found in /var/folders/tr/3lftss053tqdh731cgt0w1p00000gn/T/carthage-xcodebuild.6LzfqB.log
Failed to discover shared schemes in project Quick.xcodeproj—either the project does not have any shared schemes, or xcodebuild never returned

The log file is empty.
$ xcodebuild -version
Xcode 7.1
Build version 7B91b

After removing Carthage/ dir, got same error.

Using --platform iOS
$ carthage update --platform ios
*** Cloning ReactiveFoundation
*** Cloning ReactiveUIKit
*** Cloning ReactiveKit
*** Checking out ReactiveFoundation at "v1.0.4"
*** Checking out ReactiveUIKit at "v1.0.6"
*** Checking out ReactiveKit at "v1.0.8"
*** xcodebuild output can be found in /var/folders/tr/3lftss053tqdh731cgt0w1p00000gn/T/carthage-xcodebuild.bOvVcK.log
Failed to discover shared schemes in project ReactiveKit.xcworkspace—either the project does not have any shared schemes, or xcodebuild never returned

@toshi0383, do you have latest version of Carthage?

Yes, should be the latest.
$ carthage version
0.10.0

Oh I love Carthage. Looks like Cartfiles for dependencies were causing problems. I've removed them so I hope it will work now. Please try.

Let's use CocoaPods primarily?
On Sun, 29 Nov 2015 at 18:06, Srđan Rašić<EMAIL_ADDRESS>wrote:

Oh I love Carthage. Looks like Cartfiles for dependencies were causing
problems. I've removed them so I hope it will work now. Please try.
—
Reply to this email directly or view it on GitHub
https://github.com/ReactiveKit/ReactiveKit/issues/13#issuecomment-160421474
.

@ivanmoskalev A lot of people use Carthage over cocoa pods so I don't think it's worth only using cocoa pods.

@Danappelxx I think there is no trouble making the framework Carthage-supported even if we use another dependency manager as main :)

I think the reason Carthage is being used in reactive kit is due to it being more stable and less involved. I personally think we should stick with it (at least, primarily).

** BUILD SUCCEEDED **

Thanks !

@ivanmoskalev, I guess by "main" you mean dependency manager for "sub-frameworks" like ReactiveFoundation dependency on ReactiveKit? I've switched all that to git submodules :) Carthage honours git submodules and CocoaPods manages dependencies well so I think we should be good to go.


fix(api/list-org-repos): ensure active flag is boolean

closes https://github.com/go-vela/community/issues/853
when GORM is given the proper type, it will use the appropriate query depending on which driver is in use.
tested in local setup with both postgres and sqlite. no functional differences.
as a side note, it's not intuitive to start up the local (or any) stack with sqlite. compilation requires CGO and when using alpine requires you to make sure you are on alpine 3.18 instead of the latest (see issue #1164 on github.com/mattn/go-sqlite3). latest gcc and musl in the newest alpine (3.19.x) apparently do not work with that library. alternatively, and probably preferably, it looks like you can pass CGO_CFLAGS="-D_LARGEFILE64_SOURCE" in addition to CGO_ENABLED=1.

@ecrupper yes, maybe in form of documentation 😬


Tuple fields

This small PR introduces tuple field extraction. Initially I was thinking to use a syntax like t.0 to extract a field, but using t.f0 seems equally good and requires no changes to the grammar, and will not introduce ambiguities.

Perhaps this is intended by design, but this proposal syntactically disallows the ability to have a run-time variable expression, or even a named compile-time constant (e.g. #define symbol, or const int x = 2;) as the index of the tuple element reference.
Using syntax like my_tuple[0] or similar, even if most or all implementations would likely limit the expression to a compile-time known value that is int (also bit<W> or int<W>), would enable code like:
#define MY_FAVORITE_INDEX 2
const int second_favorite_index = 5;

     a = my_tuple[MY_FAVORITE_INDEX];
     b = my_tuple[second_favorite_index];

Yes, this is by design, with a dynamic index we cannot statically tell the field type.

So compile-time known value is needed, understood.  But an expression still might be useful for developers?  We allow compile-time known value expressions in bit slices today, and in place of the W in bit<W> types.

This syntax won't work for expressions.

Fixes #864

I approve but let's discuss at the July LDWG.

+1 for array indexing syntax, even if the indices are restricted to compile-time constant expressions.

Actually, upon reflection, I think array indexing is much better than f0, f1, etc.

Would it make sense to introduce optional field names that can be defined by the programmer, while using f0, f1, etc. as a backup?

@vgurevich can you elaborate on your proposal?

@mbudiu-vmw -- something like:
result = Hash.get({src_ip = hdr.ipv4.src_addr, dst_ip=hdr.ipv4.dst_addr, potocol=hdr.ipv4.proto});

This is an anonymous struct, not a tuple. We have an issue filed for supporting anonymous structs, and you are listed as an owner.

The spec should say whether tuple fields can be left values.

The spec should say whether tuple fields can be left values.

@jnfoster : made the requested typo fix. If you approve we can merge this.


Add explanation about the difference between Outbounds and Transparent-proxying

Description
https://kuma.io/docs/2.7.x/production/dp-config/dpp/

When should I use Outbounds / Transparent-proxying?
Is there any limits to use Outbounds/ Transparent-proxying in Kubernetes / Universal environment?
What is the default choice if we do not set them?

We discussed having a glossary in triage: xref #868


Horovod support

Based upon the new backend in #188, this adds support for the Horovod library for data parallelism.
The main advantages in contrast to DeepSpeed are an easier installation and more stability.
However, DeepSpeed offers far more features.

:pray:


Request: chocolatey package

Is your feature request related to a problem? Please describe.
I want to be able to quickly update the app the way I update all my other apps.
Describe the solution you'd like
I'd like to be able to run choco install brancato and get the app, and get notified when new releases are available.
Additional context
I've been looking for an excuse to create a chocolatey package for a while now. :)

Choco package uses msiexec with the silent features, something like:
msiexec /i C:\Path\To\brancato_0.7.1_x64_en-US.msi /qn /norestart
Need to figure out the property for getting it to start up after. And then need to create the nuspec, etc. etc.

You're more than welcome to tackle this! It was definitely in the back of my brain haha.
I think I'd personally rather work on the native Tauri update server mechanism for updates, but this is a great Windows focused solution that meets people at an existing ecosystem


CountDocuments: count command did not return a numeric "n" value

Description
When expected CountDocuments result is 0, cursor returns empty array without the 'n' value, which throws an exception instead of returning 0.
        $cursor = $server->executeReadCommand($this->databaseName, new Command($this->createCommandDocument()), $this->createOptions());
        // this is an empty array which will cause an unexpected exception
        $result = current($cursor->toArray());

        if ( ! isset($result->n) || ! (is_integer($result->n) || is_float($result->n))) {
            throw new UnexpectedValueException('count command did not return a numeric "n" value');
        }

        return (integer) $result->n;

Environment
MongoDB server version: 3.6.4-rc0-2-g0fe08c834e
PHP Version 7.2.2
MongoDB extension version | 1.5.1
libbson bundled version | 1.11.0
libmongoc bundled version | 1.11.0
mongo-php-library version: 1.4.1

Thanks for the report. I've opened PHPLIB-376 to track this.
If you need an immediate solution and are not using transactions, the deprecated Collection::count() method should be usable.

PHPLIB-376 is not closed, and will be part of an upcoming 1.4.2 release.

Not sure it's still relevant, got the same error today with:

Mongod 4.0.0 (git version 3b07af3d4f471ae89e8186d33bbb1d5259597d51)
PHP 7.2.8
PHP Extension 1.5.0
libbson bundled version | 1.11.0
libmongoc bundled version | 1.11.0
PHP Library 1.4.1

MongoDB PHP Library 1.4.2 which has this fix, is now released: https://groups.google.com/forum/#!topic/mongodb-announce/Z_XOpIQTJyo


💡[FEATURE]: Impact of Macroeconomic Indicators on Stock Market Volatility

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
This analysis will explore how various macroeconomic indicators, such as GDP growth, inflation rates, and unemployment rates, influence stock market volatility. I will use historical data on macroeconomic indicators and stock market indices to perform the analysis.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@Akshat111111
Kindly assign me this issue

@Akshat111111
Kindly assign me this issue

@Akshat111111
Is this already done?

the pr which is merged can be seen in the PR section


Create a settings view

Just what the title says.
The following items should be included:

Dark/night mode (See #8)
Advanced config

API endpoint

This list can change anytime before this issue is solved.

Background fetch frequency (e.g. 10 mins; 45 mins; 3 h; 1 d)


A request for Multitrack MusicVAE checkpoint

Thanks for your work and I am interested in the works about Multitrack MusicVAE. But I can not find the pretrained model about it.

It looks like the original model checkpoints are in the magenta-js directories. You can check out the links in https://goo.gl/magenta/js-checkpoints. For any of the multitrack directories, you should be able to download the files model.ckpt-100000.data-00000-of-00001 and model.ckpt-100000.index which you can use to run the Python models.


docs(IconExampleLoadingGroup): typo use to user

Current coverage is 100% (diff: 100%)

Merging #815 into master will not change coverage

@@           master   #815   diff @@
====================================
  Files         136    136
  Lines        2197   2197
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
  Hits         2197   2197
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 52743fc...5a7e2db

Great, thanks!


feat: Add support for human-readable duration formats

Fixes #649. This was discussed in an arch meeting roughly two weeks ago (when this PR was opened).
It is part of the effort to unify duration formats used in our CRDs. Operators would need to use the exported Duration type to support human-readable duration formats. This PR adds support for human-readable durations, like 2d2h20m42s or15d2m2s. The Duration type requirements are tracked in #649
These changes are breaking, because:

in some cases the type changes from number to string
in cases where string is already used, the parsing might be slightly different

# Author
- [X] Changes are OpenShift compatible
- [ ] CRD changes approved

# Reviewer
- [ ] Code contains useful comments
- [ ] (Integration-)Test cases added
- [ ] Documentation added or updated
- [ ] Changelog updated
- [ ] Cargo.toml only contains references to git tags (not specific commits or branches)

In its current form, the Duration is not usable in const environments, thus we are unable to define constant values like here: https://github.com/stackabletech/trino-operator/blob/main/rust/crd/src/lib.rs#L124
There currently is an open issue upstream in humantime, but there seems little to no progress. We could, however, implement our own (simplified) parsing.

This also doesn't enforce unit order (unlike https://gist.github.com/nightkr/c75db0c27ac0815e4f8c41cbfed3aa61#file-crd_duration-rs-L89-L101)

This also doesn't enforce unit order (unlike https://gist.github.com/nightkr/c75db0c27ac0815e4f8c41cbfed3aa61#file-crd_duration-rs-L89-L101)

Yes, that was one thing I wanted to continue working on. Had it on my personal TODO list :)

Commit fe1911e breaks duration::test::parse_invalid::case_3. This change needs to be reverted.

Actual change LGTM, giving it a try with trino-op graceful shutdown

error[E0277]: cannot multiply `{integer}` by `stackable_operator::duration::Duration`
  --> rust/operator-binary/src/operations/graceful_shutdown.rs:46:13
   |
46 |         + 2 * GRACEFUL_SHUTDOWN_GRACE_PERIOD
   |             ^ no implementation for `{integer} * stackable_operator::duration::Duration`
   |
   = help: the trait `Mul<stackable_operator::duration::Duration>` is not implemented for `{integer}`

Looking at the generated deploy/helm/trino-operator/crds/crds.yaml, we have the following change I would have not expected.
                     gracefulShutdownTimeout:
                       default: 1h
                       description: Time period the trino workers have to gracefully shut down, e.g. `1h`, `30m` or `2d`. Consult the trino-operator documentation for details.
-                      type: string
+                      properties:
+                        nanos:
+                          format: uint32
+                          minimum: 0.0
+                          type: integer
+                        secs:
+                          format: uint64
+                          minimum: 0.0
+                          type: integer
+                      required:
+                        - nanos
+                        - secs
+                      type: object

@Techassi as discussed, pushed the fixes, please have a look

Yes, looks good! Waiting for final feedback from @nightkr

Commit fe1911e breaks duration::test::parse_invalid::case_3. This change needs to be reverted.

Fair, I should have fixed those test cases.

Commit fe1911e breaks duration::test::parse_invalid::case_3. This change needs to be reverted.

Fair, I should have fixed those test cases.

98149d7c57a381668b6c05e07bf4f27b198992b8

Awesome, thanks for working on this!


May be bug or Some other problem

I was communicating to one Open protocol controller with 3 tool. So first we try to use MID0100 but for that we are getting parsing error while receiving the response from the controller. So vendor of controller suggest that we can use 3 different port for 3 tool of the controller so we changed accordingly. We are testing everthing with the sample app in the repo. So we connected successfully but we are getting the response from all the 3 tool  multple times. Even controller is sending one time but we are receiving multiple times. This is the first problem we faced but after some time we are having another big problem , controller is sending the data of all the 3 tool but we are receiving only for either 1 or 2 tool. When we restart the app then we again receive the data from all the 3 tool for 2-3 times but again then we received the data only for 1 or 2 tool. Here I am attaching code and log file as well.
Log_20201001.log
Code.txt

I think this is off-topic issue because source of this issue is not related to this project.
Anyway, your problem is you are trying to process asynchronous data synchronously. Sample is sufficient for 1 controller but no for 3.

Hi, Thank you for your time and feedback. I will use this code, But I was short on time for this project so I figured out there is MID0100 and MID0101 for multispindle so I am using this MID in my project. But I am having one problem with that sometimes I am getting a message in the log that keep alive not received and then I never got the data again. So what I am doing on keepalive timer I am reconnecting to the controller(calling btnConnect) event. I don't know why this happening. Even though I will change in that code too according to this code then will see how it will work..BY THE WAY, THANK YOU AGAIN

You are welcome, let me know result :)
There is bug in MID 0100 and I forgot to report it. Constant LAST_REVISION has value 4 but this revision isn't defined and flag "sendOnlyNewData" wasn't implemented at all. Anyway, "Send only new data" is for revision 3+ and I can test MID 0100 on 2 PF4000 controllers and one PF6000 and each controller can use only MID 0100 with revision 1 so I think this flag is useless (for now).
Here is modified code:
using OpenProtocolInterpreter.Converters;
using System.Collections.Generic;

namespace OpenProtocolInterpreter.MultiSpindle
{
    /// <summary>
    /// Multi-spindle result subscribe
    /// <para>
    ///     A subscription for the multi-spindle status. For Power Focus, the subscription must
    ///     be addressed to a sync Master.
    /// </para>
    /// <para>
    ///     This telegram is also used for a PowerMACS 4000 system
    ///     running a press instead of a spindle. A press system only supports revision 4 and higher
    ///     of the telegram and will answer with <see cref="Communication.Mid0004"/>, MID revision unsupported if a subscription
    ///     is made with a lower revision.
    /// </para>
    /// <para>Message sent by: Integrator</para>
    /// <para>
    ///     Answer: <see cref="Communication.Mid0005"/> Command accepted or
    ///     <see cref="Communication.Mid0004"/> Command error, Controller is not a sync master/station controller,
    ///     Multi-spindle result subscription already exists or MID revision unsupported
    /// </para>
    /// </summary>
    public class Mid0100 : Mid, IMultiSpindle, IIntegrator
    {
        private readonly IValueConverter<long> _longConverter;
        private readonly IValueConverter<bool> _boolConverter;
        private const int LAST_REVISION = 4;
        public const int MID = 100;

        public long DataNumberSystem
        {
            get => GetField(2, (int)DataFields.DATA_NUMBER_SYSTEM).GetValue(_longConverter.Convert);
            set => GetField(2, (int)DataFields.DATA_NUMBER_SYSTEM).SetValue(_longConverter.Convert, value);
        }

        public bool SendOnlyNewData
        {
            get => GetField(3, (int)DataFields.SEND_ONLY_NEW_DATA).GetValue(_boolConverter.Convert);
            set => GetField(3, (int)DataFields.SEND_ONLY_NEW_DATA).SetValue(_boolConverter.Convert, value);
        }

        public Mid0100() : this(LAST_REVISION)
        {

        }

        public Mid0100(int revision = LAST_REVISION) : base(MID, revision)
        {
            _longConverter = new Int64Converter();
            _boolConverter = new BoolConverter();
        }

        public Mid0100(int revision, bool sendOnlyNewData) : this(revision)
        {
            SendOnlyNewData = sendOnlyNewData;
        }

        public Mid0100(int revision, int dataNumberSysten, bool sendOnlyNewData) : this(revision)
        {
            DataNumberSystem = dataNumberSysten;
            SendOnlyNewData = sendOnlyNewData;
        }

        protected override Dictionary<int, List<DataField>> RegisterDatafields()
        {
            return new Dictionary<int, List<DataField>>()
            {
                { 1, new List<DataField>() },
                {
                    2, new List<DataField>()
                            {
                                new DataField((int)DataFields.DATA_NUMBER_SYSTEM, 20, 10, '0', DataField.PaddingOrientations.LEFT_PADDED, false),
                            }
                },
                {
                    3, new List<DataField>()
                            {
                                new DataField((int)DataFields.SEND_ONLY_NEW_DATA, 30, 1, '0', DataField.PaddingOrientations.LEFT_PADDED, false),
                            }
                },
                {
                    4, new List<DataField>()
                }
            };
        }

        public enum DataFields
        {
            DATA_NUMBER_SYSTEM,
            SEND_ONLY_NEW_DATA
        }
    }
}

Sorry for the late reply and thanks for posting this code. I was busy with this controller thing where I am getting data more than one time even the controller is sending only one time but I am getting some times 3-4 times. I am using Revision 1 for 0100 but now I will test your code too. I have found one more problem with Mid0101 when parsing data then during conversion there is a problem with the substring variable

Yes, I found this bug too but I forgot it in my last comment :)
I fixed it this way (I deleted extra "* 18"):
public override IEnumerable<SpindleOrPressStatus> Convert(string value)
        {
            for (int i = 0; i < value.Length; i += 18)
            {
                // var spindleValue = value.Substring(i * 18, 18);
                var spindleValue = value.Substring(i, 18);
                yield return new SpindleOrPressStatus()
                {
                    SpindleOrPressNumber = _intConverter.Convert(spindleValue.Substring(0, 2)),
                    ChannelId = _intConverter.Convert(spindleValue.Substring(2, 2)),
                    OverallStatus = _boolConverter.Convert(spindleValue.Substring(4, 1)),
                    TorqueOrForceStatus = (TighteningValueStatus)_intConverter.Convert(spindleValue.Substring(5,1)),
                    TorqueOrForce = _decimalConverter.Convert(spindleValue.Substring(6, 6)),
                    AngleOrStrokeStatus = _boolConverter.Convert(spindleValue.Substring(12, 1)),
                    AngleOrStroke = _intConverter.Convert(spindleValue.Substring(13,5))
                };
            }
        }

Hi,
Thanks for your feedback. Now I am having one strange problem some data is missing. When I checked the log then When I received the tightening data then if before sending confirmation MID, keep alive mid sent then the connection is lost and then I am reconnecting to the controller but till then I have lost the data. This happens mostly in the case of first data NG then connection lost then I only had NG data because reconnection to the controller will take some time and till then the operator has passed the operation to the next process.

I think you didn't sent some ACK or didn't sent it in right order. I checked if keepalive (MID 9999) can drop connection and I sent keepalive before ack on purpose and connection was unaffected. I had similar issues when I forgot to send ack. You can find this in Open Protocol specification:
4.3.3 Subscribed data message acknowledge
Depending on the subscription message” No Acknowledge Flag” settings in the message header the integrator is acknowledging or not acknowledging. If the flag is NOT set the integrator shall acknowledge the data event messages by sending the corresponding acknowledge MID, otherwise not. If no acknowledge is received before the response timeout, the controller will re-send the message up to three times. After three attempts the controller will consider the connection as lost.
You can try to subscribe with NoAck option (byte 12 in message header) to test this possibility. "No ack" option is considered as unreliable so you should restore this option after testing.

I am sending the ACK but I feel so while checking log I noticed I am getting message keep alive not received if just before ACK I am sending keep alive MID and after that code enter to reconnect method which will take some time and till then I have lost some OK data. I am send ACK in the following way
  private void OnTighteningReceived3(MIDIncome e)
  {
            Log.Information("Tightening Data Received For Port 9003");
            // lblManualMidResult.Text = "Tightening Data Received";
            driverPort3.SendMessage(e.Mid.BuildAckPackage());
}

I have 3 controller for multispindle and one controller with single tool. In both the cases I am having problem..Can you help me what wrong I am doing and where ?  Can controller handle multiple operation like when controller is waiting for some ACK and we are sending MID9999 for keep alive ?

I tried to send keepalive before ACK on purpose and this is result:
15.10 05:02:59.371 ... DEBUG: READ << 00420015            0042015-05-26:08:56:56
15.10 05:02:59.380 ... >> KeepAliveAtlas >> (00209999            )
15.10 05:02:59.383 ... << Parameter set selected - 4 (2015-05-26 08:56:56)
15.10 05:02:59.385 ... DEBUG: WRITE >> PsetNo_Acknowledge >><PHONE_NUMBER>1         )
15.10 05:02:59.408 ... >> PsetNo_Acknowledge >><PHONE_NUMBER>1         )
15.10 05:02:59.410 ... Parameter set ID: 4
15.10 05:02:59.428 ... DEBUG: READ << 00209999

So, I received response from controller 48ms later and no connection lost error or something like this.
It's hard to tell where is problem when I have only fragments of your code. I don't see try-catch block so I can guess if you're trying to log different events in same time you can get "file is in use" exception.
Try to run logger in different thread (if you don't do it already) or try to swap lines like this:
private void OnTighteningReceived3(MIDIncome e)
{
            driverPort3.SendMessage(e.Mid.BuildAckPackage());
              // lblManualMidResult.Text = "Tightening Data Received";
            Log.Information("Tightening Data Received For Port 9003");
}

Thanks for your reply.. Yes, i am using the try-catch block and not getting error message. But I will try to change as you have suggested. Thanks again for your help.

I tried to modify sample to work with multi-spindle tightening and I found problem is probable in SimpleTcpClient not your code. This TCP client is synchronous, it's good for sample but not for production. I lost connection to controller when I receive tightening result and in same time keepalive MID was sent and client waiting for response.
Check this code:
public void WriteLine(string data)
        {
            if (string.IsNullOrEmpty(data)) { return; }

            while (this.waitingForResponse)
                Thread.Sleep(10);
            if (data.LastOrDefault() != Delimiter)
            {
                Write(data);
            }
            else
            {
                Write(data);
            }
        }

You can see You can't send ACK MID when other MID was sent with request for response and client is waiting for requested response.

Thanks for your time again..this is exactly happening with me..Now what should I do and where and what should I change to run this code in production?

I tried to change TCP class to SimpleTcp [1] (NuGet name is SuperSimpleTcp) and got no connection lost during one and half hour. I want share this multi-spindle sample with this project but I don't when it will be ready.
[1] https://github.com/jchristn/SimpleTcp

Hi
I think i had a similar issue . To improve the process don't send keep alive if you already send another command. Use keep alive only you have nothing to communicate. This will not fix your error but will decrease the chance of getting error.

@xGusu  Thanks for your reply. I tried to do so by creating one flag which will check if the controller is not waiting for ACK then only keepalive will send the data. But as you said it does not fix the error and due to critical data I can not say to the client that you have to manage like this only.
@yanick76  Thanks for sharing the class reference link I will try to use this class and hoping the issue will be resolved.
Thanks again for your time and help @yanick76 @xGusu

Modified sample is included in different issue
https://github.com/Rickedb/OpenProtocolInterpreter/issues/34

I left this sample running for 24 hours and i got no connection lost (and no crash or memory/resources leak) so you can use this sample I think it's stable enough.
I hope this helps you.

Thank you so much for your help & time. I will use this sample in my production application. Thank you again

Closing issue due to inactivity and it seems that was solved.
If problem persists, just reopen it.


Rewrite to work with React's Concurrent Suspense mode

Concurrent Suspense completely changes the approach to how state management would work while lightmap is being computed. Need to start rebuilding for that.

i think the only difference is that it's not a race. all components unsuspend at the same time
given:
<Suspense ...>
  <Async1 />
  <Async2 />
  <Sync />

previously: sync just fires stupidly, then async 1 and 2 depending on who's first
now: async1, async2, sync all fire at the same time as they should, when every thing inside has lifted the suspense.
this can later be controlled by the user via suspenselist (race, one after the other, all in sync).
how's the project going btw, would love to try it out again :)

Yeah, the blocking/concurrent mode is in some ways easier to think about that way. The only tricky part is that I'd like to keep the following logic:

core scene suspends (e.g. loading gltf/etc)
core scene is finished, unsuspends
lightmapper wakes up, grabs a reference to core scene object and suspends again
lightmapper is finished, unsuspends

The issue is that from a container component's perspective, the above will result in a short "blip" between step 2 and 3 (when things are unsuspended by core scene but not yet suspended by lightmapper). Sort of like a FOUC.
And the lightmapper can of course e.g. hide the not-yet-lit scene during the blip, sure, but I just don't like that this will result in the fallback spinner animation being reset for the overall suspense wrapper.
On the other hand, if I understand correctly, suspense wrapper can have a debounce on loading state? So maybe at least it won't unmount/remount loader instance during that "blip".

you can probably resolve that by using useEffect and useLayoutEffect, the latter comes before the actual render on screen.

So here is a test sandbox: https://codesandbox.io/s/divine-firefly-rh2mx?file=/src/App.js.
I used useLayoutEffect to make sure that the "blip" is instantaneous, so at least there is no flash of unstyled content.
BUT. The loader gets re-instantiated - you'll notice how "loader instance" number changes during processing, at the moment that the content finishes loading. This might just look weird/cause spinner animation reset/etc. Not sure how to debounce that.

(also, I am still wrapping my head around why the zero-dependency effects seem to run multiple times instead of just once, will need to read newer docs)

suspense unmounts the effects. i think only useEffect is left standing. i dont quite understand what the goal is for the sandbox.

suspense unmounts the effects. i think only useEffect is left standing. i dont quite understand what the goal is for the sandbox.

The sandbox demonstrates how lightmapper can wait for suspended content and then also suspends while doing lightmapping.
But the problem is that inbetween the two suspended phases the fallback loader gets re-created which would reset any e.g. spinner animation. I would like to find a way to avoid that re-creation/reset, it creates unsightly jank.

Fixed in #16.


Change Vat recipe for EndStone to use less Resonant Ender

Rotarycraft uses just 50mb per endstone.
Vat should also use 50mb, with 4 cobblestone.
While we are at it, add recipe for Resonant Ender by melting a Ender Lily seed.
Also change the Vat's Resonant Ender to Ender Pearl recipe to use just 200mb of ResEnder. Not sure if it should be every pearl but more than just the white one.

Vat uses 125mb per endstone.
If it was the same as Rotarycraft, I wouldn't bother with Rotarycraft, the vat is earlier in the tech tree.


Fix icon alignment

Closes #6

I could make this Tailwind if you wasnt.

I could make this Tailwind if you want.

But is that worth it? Tailwind is for people who don't want to put in effort.

It's not "people who don't want to put in effort" it's to make the code neater, allow fast development, and allows you to make a colour scheme.

It's not "people who don't want to put in effort" it's to make the code neater, allow fast development, and allows you to make a colour scheme.

Oh, so what about https://github.com/JaydenDev/searchocean/issues/2#issuecomment-1002358303?

@webdev03 I'd prefer this be done in tailwind yes, go ahead.

@webdev03 go to #2 and you can start. Closing PR.

@webdev03 go to #2 and you can start. Closing PR.

Fine. Reject another one of my PRs for no reason and I delete every fork I have of things you've made.


Integration Test - Release - 2019/10/31 22:22:54

Auto create for integration test. IssueCommandFlow

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


update praise page on staging site

thoughts? so more recent?

update praise page on staging site

jim will show us how


Superset container always restarting

Hi, I tried to run demo.sh here with mysql parameters and it crashed when the command docker-compose exec ... was given and show this error message:
Error response from daemon: Container 3e9f7c301b53417db5b703633f8d540ffdf6341e283e419f62021fe521fc3cf0 is restarting, wait until the container is running
I checked the  containers working status and the superset container is always restarting, never gone up fully.
CONTAINER ID        IMAGE                 COMMAND                  CREATED             STATUS                          PORTS               NAMES
3e9f7c301b53        amancevice/superset   "superset runserver"     16 minutes ago      Restarting (1) 42 seconds ago                       mysql_superset_1
93634e93af06        mysql                 "docker-entrypoint.s…"   17 minutes ago      Up 17 minutes                   3306/tcp            mysql_mysql_1
48fde5649b50        redis                 "docker-entrypoint.s…"   17 minutes ago      Up 17 minutes                   6379/tcp            mysql_redis_1

I would like to know how to solve this.
Update
I figure out that it can be happened because this part of docker-compose file:
  superset:
    image: amancevice/superset
    restart: always
    depends_on:
      - mysql
      - redis
    environment:
      MAPBOX_API_KEY: ${MAPBOX_API_KEY}
    ports:
      - "8088:8088"
    volumes:
      - ./superset_config.py:/etc/superset/superset_config.py

But I still don't know why, shoud I remove the parameter restart: always?
Thanks!

I think this might be a MySQL issue. MySQL recently released v8.
Try changing the mysql image to image: mysql:5

Changed, but know the mysql container also restarting always
  mysql:
    image: mysql:5
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: superset
      MYSQL_DATABASE: superset
      MYSQL_USER: superset
      MYSQL_PASSWORD: superset
    volumes:
      - mysql:/var/lib/mysql

CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                         PORTS               NAMES
0e4ce3c2929b        mysql:5             "docker-entrypoint.s…"   3 minutes ago       Restarting (2) 8 seconds ago                       mysql_mysql_1
f00e26ddb189        redis               "docker-entrypoint.s…"   3 minutes ago       Up 3 minutes                   6379/tcp            mysql_redis_1

Would you mind clearing out all the old containers and trying again? With a completely clean environment (no running or stopped containers) and setting mysql to mysql:5 I am seeing this working.

Very strange. Sorry for your troubles!


Configure active directory connection and authentication against AD groups

Summary
This converts the original OIDC Generic connection to use the OIDC Active Directory implementation instead. This change allows for AAD Groups to be mapped to Drupal roles and allows us to authorize that a non-admin user has access to the site based on an AAD group that matches the site's URI.
A custom module named ecms_authentication is installed and adds an pre-authorize hook that calls a custom service class to check if the user authenticating against active directory is an administrator or is a member of a group that matches the site's URI.
Metadata

Question
Answer

Did you use a meaningful pull request title?
yes

Did you apply meaningful labels to the pull request?
yes

Did you perform a self review first?
yes

Documentation reflects changes?
yes

CHANGELOG reflects changes?
yes

Unit/Functional tests reflect changes?
yes

Did you perform browser testing?
yes

Risk level
Medium

Relevant links
RIG-23

@ben-hamelin, I have this rebased and it is ready for review now.


WIP: Don't need to reversemap files

Goes along with the changes in https://github.com/alanz/ghc-mod/pull/17
This paves the way to removing mappedFiles altogether.
This also fixes a bug: With current master, open a file, and, without saving, write something like
foo id = id

You will get a diagnostic for name shadowing, but the file mentioned in the diagnostic will be the temporary mapped file instead of the actual file. This behaviour will not happen after the changes in this PR are applied.
This eliminates the need for reverseMap altogether, and probably fixes a bunch of other bugs in the process, involving returning the mapped file to vscode instead of the actual file.
Needs testing.  It also needs to tested against code with TH and CPP.
To test, you will need to
$ cd submodules/ghc-mod
$ git remote add wz1000 https://github.com/wz1000/ghc-mod
$ git fetch wz1000
$ git checkout wz1000/proper-mapped-files

and then build normally.

This does not work with CPP

This does not work with CPP

Is that an observed behaviour? Because as I understand it the line numbers should still line up. Or is it a case of not actually running the preprocessor?

@alanz this is the error that gets triggered: https://gitlab.haskell.org/ghc/ghc/blob/master/compiler/main/GhcMake.hs#L2454

Quick sanity check on macOS is working. Looks like the code action functional tests are failing though

@wz1000  yes, the missing preprocessing. CPP is such a PITA


[WIP] Match resonant website

See conversation in #403

Current coverage is 58.19% (diff: 100%)

Merging #408 into master will not change coverage

@@             master       #408   diff @@
==========================================
  Files            26         26
  Lines           708        708
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            412        412
  Misses          296        296
  Partials          0          0

Powered by Codecov. Last update 15e91c3...b900275

I don't think Roboto Slab is right for the app, though it may just be because I am used to how it was before. The slab font is too heavy/bulky in, e.g., the matching panel. I think Roboto or even Roboto Condensed might work better (but of course I'd have to see it).
I may grab Steve Jordan tomorrow and get his opinion as well.

Do you mean the matching panel header, or the clickable pills inside? I thought the latter was one of the few places it wasn't too heavy. If you meant the header, that's actually Montserrat.
Both fonts have lighter weights available—If we want to match the Resonant website, we should use the same fonts as much as possible (changing the weight is usually a far less drastic change than dropping the slabs / going condensed).

Right, I meant inside the pills. I like the Montserrat caps in the window titles.
I actually don't think we need to make it an explicit goal to match the fonts in the Resonant website. If we do, that's ok, but the fonts need to serve their purpose within the app first and foremost.

Another option that I'll throw out there is that we can change the fonts on the Resonant website :) The main Girder client and various RTD are two others areas that would benefit from style normalization.

I'll take the bold position that our attempts to figure out typefaces for
Resonant Lab should not become a larger discussion about fonts on our other
websites at the current time :-P
On Fri, Sep 23, 2016 at 10:15 AM Jeff Baumes<EMAIL_ADDRESS>wrote:

Another option that I'll throw out there is that we can change the fonts
on the Resonant website :) The main Girder client and various RTD are two
others areas that would benefit from style normalization.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Kitware/candela/pull/408#issuecomment-249204518, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACxNJOj-wnomSk3Qm5lUAhcerkX1Tp4lks5qs971gaJpZM4KEX3F
.

In that light, it might be worth waiting for Kitware to implement some kind of branding style guide (I think @superlib mentioned something about revamping the main page—maybe all sites should conform to whatever styles are put in place there?)

Sorry for further devolving the conversation :) I agree with @ronichoudhury: make the app look good - if there are matches with the current Resonant website that's great but not required. I just wanted to add that the Resonant website did not have an in-depth style discussion so should not be considered gold-standard.
I like the energy around making RL look awesome, but for now let's pick a "good enough" and  we can always continue iterating later.

I'm planning to sit down with Steve later today, so we'll try to figure out
a combo that works generally. When overarching style guides come in some
day, we can reconsider RL as well.
On Fri, Sep 23, 2016 at 10:27 AM Jeff Baumes<EMAIL_ADDRESS>wrote:

Sorry for further devolving the conversation :) I agree with
@ronichoudhury https://github.com/ronichoudhury: make the app look good

if there are matches with the current Resonant website that's great but
not required. I just wanted to add that the Resonant website did not have
an in-depth style discussion so should not be considered gold-standard.

I like the energy around making RL look awesome, but for now let's pick a
"good enough" and we can always continue iterating later.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Kitware/candela/pull/408#issuecomment-249207473, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACxNJOhj1Sq-3h96w3W4n564E99qLk_fks5qs-GogaJpZM4KEX3F
.

Closing in favor of #403


Remove DatabaseUser from all resource specs

It is currently implemented in lib-common, but not in mariadb-operator. mariadb-operator always creates database user with name == .DatabaseName.
Whith this change we pass the same value (the database name) to lib-common's NewDatabase function.
See: https://raw.githubusercontent.com/openstack-k8s-operators/mariadb-operator/master/templates/database.sh

/test ironic-operator-build-deploy-kuttl

/test ironic-operator-build-deploy-kuttl
Error: [error resolving name : quay.rdoproject.org/openstack-k8s-operators/openstack-operator-bundle:62a48ae6deda854d37bcd1359b0a5c4695f56ad7: not found, image "quay.rdoproject.org/openstack-k8s-operators/openstack-operator-bundle:62a48ae6deda854d37bcd1359b0a5c4695f56ad7": not found]


[api test] Expose laxcomma

New pull request: https://github.com/jshint/jshint/pull/282#issuecomment-2685188
Only the changes we discussed here.

Thanks! Could you add tests for this option, please? I can do it myself but I am not sure when I will have time to get it done.

What exactly are you looking for in tests? As I understand it the test files in JSHint must themselves pass and I had to add the laxcomma option to the test options since the comma-first style is used. Is that sufficient?

@antonkovalyov Ping. I'm happy to write tests, I'm just not sure what you want tested. There are already tests using this option since the test code uses the comma-first style.
Just let me know and I'll them in there :)

Oops, I thought I have already replied to this thread. Sorry.
 Put them into tests/options.js please.

So, I wrote a basic test for this feature.
However, I'm wondering if allowing laxcomma should require allowing laxbreak? That's how we do it right now.

@mmalecki Yes. laxbreak should be able to be true even if laxcomma is false.

I think it would also be useful to allow laxcomma while simultaneously disallowing laxbreaks as laxbreaks cover a wider range of options, whereas node modules often only violate the laxcommas part of it.

@mmalecki I don't see fixtures/laxcomma included in your commit -- can you please commit that file?

@goatslacker Derp. Amended and included.

So this LGTM.
My only issue is with both laxbreak and laxcomma required in order to pass comma-first. I feel like only one should be required not both.
@antonkovalyov @WolfgangKluge thoughts?

laxbreak is false by default I believe. You need two settings because laxcomma does not cover this kind of syntax:
  return someBool
    ? true
    : false;

That works if we change if (!option.laxbreak || !option.laxcomma) { to if (!option.laxcomma) {
That line is in the comma function which handles only commas. The only reason I can think of is because of backwards compatibility.

@goatslacker I think you're right. I wrote out the matrix of values
+--------------------------------+
| laxbreak | laxcomma | result   |
+--------------------------------+
| true     | true     | no error |
| false    | true     | error    |
| true     | false    | error    |
| false    | false    | error    |
+--------------------------------+

The settings I would use would be { laxbreak: true, laxcomma: false } which yield the desired behavior (an error). For others who wish to allow laxcomma but not laxbreak (i.e. { laxbreak: false, laxcomma: true }) it still yields an error which seems wrong to me.
This would be a breaking change though (not backwards compatible) so I'm curious what @antonkovalyov or @WolfgangKluge have to say

I'm actually not worried about backwards compatibility in this case since I believe the options need to be split up regardless.
I've got the changes done and ready to merge in branch gh-340 https://github.com/jshint/jshint/compare/master...gh-340 but I want to hear others' take on it before I merge.

Thoughts on what? Sorry, I got lost in the discussion here.

By adding laxcomma we'll break any previous checks that were using laxbreak to allow comma-first style.

Making sure that this doesn't introduce any other bugs by removing the laxbreak check on https://github.com/jshint/jshint/blob/gh-340/jshint.js#L2030

Maybe we can output an explanation message in case of laxbreak = true and laxcomma = false when the first comma error occurs (I think we will break some more functions in the future where this can be helpful, too - so a generic method for this requirement (output a specific message once, if certain options are set) would be great)

... Looks good. You can output the above mentioned message here.

@goatslacker Looks like we have the go-ahead here. Can we merge this in?

We definitely need to mention the change on the website but breaking in this way is sometimes necessary. I agree with @WolfgangKluge—an explanation message would be nice.

Looks good to me. We have regression test and I will test on Disqus code base before tagging a new stable release with this change.

You can merge it in. Sorry @indexzero that it took so long. :-)

@antonkovalyov No worries. Credit goes to @goatslacker for making it happen :)

No, credit goes to @indexzero for the PR!
I'll add the message and merge it in.


Small Changes, Bug Fix, Class.Inc revert

Reverting the changes done to the class.inc files and moving it to a single set of writes in basics.inc.
Made the behavior for mana and end uniform for AutoMedBreak.
Fixed an issue with new characters when AssistType isn't declared yet.

I forgot an &&. Resubmitting.


Towards a better handling of failed export

Currently, if a database export fails, the db record will end up with status "Export failed", and in the current UI implementation, this will render some other operations on that database unreachable, like Extend and Portal-ext info (which should still be available, because the db is still there).

I guess perhaps the db should still end up with Completed status, so that everything is still accessible on the UI. The user will know about the failed export (and its cause) from the email (and push) notification. Anyway I don't think that users will tipically look for this info on the UI. They will start an export, and I don't think they will wait and watch the UI in the meantime. (I, as a user, would be totally OK with this)
But as you think, @djavorszky , we could implement some more sophisticated stuff for this if you want. And I also guess it depends on the new structural changes as well.

Cross-posting from #191:
Thinking about it, I think the "Completed" status is simply redundant, and we may be approaching statuses the wrong way. The general idea is that a database may be "usable" nor "not usable".
"Usable" would simply mean that clients can connect to it, which is the case when the database has been successfully created or imported, but also when an export is in progress.
"Not usable" would be everything else - import/create in progress, or any failed status.
And then we could sub-status these, e.g. specify why a database is unusable or a usable database being exported at the moment. What do you say? I'm not sure. Just thinking aloud. Also, even if we go with this, I don't like the usable/unusable statuses, they sound silly, so we may want to look for better ones.

I agree that in these new circumstances, the current status system seems kind of obsolete and could be re-thinked and re-written somewhat. (Above I tried to give the possible less "intrusive" approach as always, as I am not a big fan of (frequent) core structural changes, as they may affect the stability perceived by users.)
Your proposal seems OK to me (even the Usable/Not Usable status names...I can't think of anything better now)

I understand your concern - for me, reliability is of utmost importance.
As we're going to go to a new UI anyway, we might as well make some changes on the front end. The backend, as long as it keeps working the way it was before, should only have minimal affect on user perception.. Ideally, at least.
What I've been thinking is to remove the current portal-ext button and instead take the user to a full page where all information is present - database export (if available), portal-exts, info on when the database was imported / created, when it expires, and an event log: e.g. when it was last exported, or in which status did the import fail, things like that.
Sure, it's a big change, but I think we may be able to make it more user-friendly and leave space to add more information in the future.

Sounds good to me.

Ticket merged to new location


$stateChange* events are deprecated in upcoming angular-ui-router 1.0.0

While digging into routing, I realized the upcoming update of angular-ui-router is deprecating $stateChange events: https://github.com/angular-ui/ui-router/issues/2219
Instead, the following is recommended:
$transitions.onStart({}, function() {});
$transitions.onSuccess({}, function() {});

However a solution is proposed here but I was wondering if there should be any adjustment to redux-ui-router as a consequence?

By doing a quick search on the source code, current version is indeed quite reliant on $stateChange* events. Not sure how straightforward the upgrade would be.

You can find more support for ui-router 1.0.x on this branch https://github.com/neilff/redux-ui-router/tree/prev-state-fix. Not sure if it's working correctly though, last time I tested it wasn't.

Fixed by #78

Will there be a release soon for 0.7.0?

Just ran into this myself. I was confused that master was showing things have already been upgraded to work with the new $transitions callbacks. Wasn't until I went digging around my node_modules, I realized NPM had an old version. Any news when there will be a release?

@jhummel There is now a 0.6.1 release and a 0.7.1-rc.1 with support for ui-router 1.0.0. Please have a jam and see if it solves you issues...

Thank you so much for this lib, example is minimal and clear, I am learning Redux and it helped a lot. In a typical angularjs application, your state is usually stored in services, controllers (scopes), router states.. it can get messy real fast..
Even if you isolate all side effects to a single place (rootscope or a dedicated state service) it's decoupled from ui-router, big problem solved with redux-ui-router.
I'm rewriting a angularjs app with typescript. I can confirm that 0.7.1-rc.1 works nicely with 1.0.0-rc.1.


before delete Udf check exist

What is the purpose of the pull request
1 Modify judgment order(调整顺序，先判断是否存在)
2 before delete check entity exist

Codecov Report

Merging #1618 into dev will decrease coverage by <.01%.
The diff coverage is 0%.

@@           Coverage Diff            @@
##             dev   #1618      +/-   ##
========================================
- Coverage   8.11%    8.1%   -0.01%
========================================
  Files        282     282
  Lines      13785   13789       +4
  Branches    2201    2202       +1
========================================
  Hits        1118    1118
- Misses     12583   12587       +4
  Partials      84      84

Impacted Files
Coverage Δ

...e/dolphinscheduler/api/service/UdfFuncService.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Create a skeletal version of individual Project Portfolio Page (PPP)

Just the headings are enough. You can write to be added soon as placeholders for content.
PDF conversion not required.
Follow the details in website

Added my skeletal PPP, made the PR as well.

Done as well, team lead please review. Thanks!