Installation

Is there any video tutorial or more detailed document on how to install? I read the documentation but I couldn't install by myself. Sorry.
Although I really need this tool!!
Any input is welcome.
Many thanks, Sheyla

hi sheyla,
can you describe in more detail what you mean by install? and with "tool", do you mean the SDK itself or one of the examples?
best,
simon

Hi, Mistafunk. Thank you for your reply.
What I need to do is similar to this movie:
https://www.youtube.com/watch?v=YqNEsJkVuaY
So I link in the link that they suggest to download and install the plugin.
So in my understanding, I may install the SKD to have this plugin working...
Is that right?
Thank you,
Sheyla


New rule proposal: Do not use hardcoded strings

We need to localize an application where some strings are using resource files and some aren't.
On one hand we need to detect all the strings that are hardcoded, and on the other we need a rule to enforce that rule from now onwards.
I am aware of CA rules "CA1302: Do not hardcode locale specific strings"  and "CA1303: Do not pass literals as localized parameters".
In the case of CA1302 https://msdn.microsoft.com/en-us/library/ms182186.aspx  it only applies to strings that refer to special system folders  but we need to extend it to other strings also.
In the case of CA1303 https://msdn.microsoft.com/en-us/library/ms182187.aspx, it only applies to method parameters and we need also the cases of methods or properties that return hardcoded strings (ie return "xyz");

It's an interesting rule for sure. My hesitations lie in the following:

A good localization tool needs to also detect string literals that appear in XAML files. This project is only capable of analyzing C# files, so it would not be sufficient on its own.
How would one would indicate a particular string is not supposed to be localized? The #pragma warning disable approach is "ugly", while other approaches like Eclipse's use of $NON-NLS$ comments proves difficult to work with over time.

Sam,
Thanks for your prompt reply.

As other StyleCop rules we were thinking of this one only for c# code files. For the XAML case I am using the parsing of http://wpflocalizeaddin.codeplex.com/ in order to detect hardcoded strings in XAML files. If there is a way StyleCop can be integrated into XAML files that would be great and I could add the existing parsing for those files also. If not I would  have a task that applies that parsing in the build phase and make it fail if it doesn't pass.

I did an initial parsing with ReSharper cmd line tools that already has a similar feature.
And there are lot of strings in our code I don't want to be detected such as those contained in RaisePropertyChanged(..), new Uri(...), DllImport(...), FindVisualChildByType(...), between many others. Instead of excluding in the code each of this methods which would be very tedious and error prone I was thinking in being able to configure the rule externally, maybe in the same definition file, such as:

RaisePropertyChanged,new Uri,DllImport,FindVisualChildByType

Is that possible ? A way to configure rules externally in StyleCop ? If not, other alternatives?
On the other hand with the previous StyleCop we were able to suppress rules in methods with the same notation as CA: [SuppressMessage("StyleCop.CSharp.DocumentationRules", "SA1649:FileHeaderFileNameDocumentationMustMatchTypeName", Justification = "Reviewed.")] Isn't that possible anymore ?
Thanks again,
Claudio


How can i center align of tags?

Which version of the WSTagsField are you using?
3.1.0
On which platform does the issue happen?
iOS 11
Are you using Carthage?
No
Are you using Cocoapods?
No
I only downloaded this and run sample project.
Which version of Xcode are you using?
9.3
What did you do?
How can i align center of tags?
What did you expect to happen?
I hope to align center of tags and placeholder.

@vasylboy90 There's now option for that at the momento Sorry. I'll have that in consideration for a future feature. Thanks.


Use eslint 9

With the introduction of turborepo and big updates, I suggest updating eslint to version 9 as well.
If it's okay, I'd like to work on it.

@wonkyDD Let's open pull request, if you want :)

I'm already upgraded to eslint 9.2.0 - can't remember what I needed to do or if anything specific broke when I did it, but let me know your error and I will compare against mine

@wonkyDD Are you want some help or the lack of time?

@PatrykKuniczak I totally forgot because several urgent matters came up. I won't be able to focus on it for a while, so if someone else can handle it, I'm fine with that. 😭

@wonkyDD We're need to wait for related/other libs, because they don't support version 9

I have checked that libs, and
    "@typescript-eslint/eslint-plugin": "8.0.0-alpha.47",
    "@typescript-eslint/parser": "8.0.0-alpha.47",

Fix it already, but it's in alpha.
Rest packages working for support of 9 version, we need to check it periodically, but closer to the end of this year.

You can check out typescript-eslint.
See: https://typescript-eslint.io/packages/typescript-eslint/#migrating-from-legacy-config-setups

@plbstl Are you eager to take it?

@PatrykKuniczak yeah I am

@plbstl Feel free to open PR, i'm currently working on other things :)


Use the new granular cache actions

Description:
Actions/cache now supports choosing when to save and restore.
See https://github.com/actions/cache/discussions/1020 for a description.
So, setup-node can run the save automatically after packages install.
For that, the install command has to be called by setup-node as well.
It can be passed as an option, it can have a default (npm ci), and with corepack support #546 the defaults can be sensible, per package manager type.
So then, most devs will just use this action with flags cache and install and that's all they need to do.
Justification:

more efficient runs
less boilerplate to use

Are you willing to submit a PR?

Maybe, but not now

Hello @wmertens
Thank you for your feature request. We will investigate it and come back you you :)

Hello @wmertens. I think it should not be implemented in scope of actions/setup-node because according to the ADR the cache should the majority of use cases. If you need more flexible solution it is better to use actions/cache.
For now I'm going to close the issue.

Hmm, wouldn't this functionality be 95% of use cases? Most of the time, you want your package manager of choice to run the install, and you want this to happen as fast as possible, and so you want caching?

The setup-node action saves global cache directory for npm, yarn and pnpm that is why I think it does rely on the place where the cache will be saved. Moreover, the main purpose of the action is to setup Nodejs for images and adding extra logic to execute npm ci or npm i will be an overload for the action.


v1.0.6 updated setup.py and added noarch generic to meta.yml

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin I'm sorry if this isn't the correct account to tag, but I'm having some trouble converting this to a noarch package. I'm trying to set this up so it doesn't call console scripts. However, the builds keep failing.


New PostFinance Space Connecting Problem

Hi there
As we have 2 webshops, we wanted to use this PlugIn as well for the 2nd webshop.
For this, we needed to open up a new "Space" in the Postfinance backend - all done, the new Space ID is integrated in the PlugIn, the payment methods are synchronized and I can make test orders with all methods - so all should be good, except that the TWINT payment is not transferred from the JTL shop to the JTL Wawi  - although the order status is "payed" in the JTL Shop, it does not say payed in the JTL Wawi - so it doesn't synchronize. Mastercard, Postfinancecard and Paypal work though.
Have you got an idea what the problem might be?
Br's
Ralph

@3d-printerstore did you setup the Paymentmethodename in the second shop 1:1 as it is in Wawi? Wawi doesnt check any IDs, Wawi only checks if the name of the paymentmethod is the same as it is in Wawi. If it matches = payment done, else unpaid until you check and set to paid.

Yes, the payment method names are the same in both shops - strangely all other payment methods work

Hi please contact<EMAIL_ADDRESS>directly for your issue.
Thanks!

@3d-printerstore is your problem solved? Then please close the issue here. Thank you

@3d-printerstore yes thats usual. So please close the issue. I can't do. Only admins and they don't have time....they have to fix the problems ;-)

It’s closed, but could you or someone look at my other issue please?
“PHP Version 8.2 or higher #42”
Freundliche Grüsse / Salutations / Best regards
Ralph Borbeck
3D-PRINTERSTORE.CH
except ag
Weststrasse 15
CH - 8570 Weinfelden
+41 71 620 32 38
<EMAIL_ADDRESS>https://3d-printerstore.chhttps://3d-printerstore.ch/
Von: Alcpaone @.>
Gesendet: Montag, 13. Mai 2024 09:44
An: pfpayments/jtl-5 @.>
Cc: 3D Printerstore @.>; Mention @.>
Betreff: Re: [pfpayments/jtl-5] New PostFinance Space Connecting Problem (Issue #41)
@3d-printerstorehttps://github.com/3d-printerstore yes thats usual. So please close the issue. I can't do. Only admins and they don't have time....they have to fix the problems ;-)
—
Reply to this email directly, view it on GitHubhttps://github.com/pfpayments/jtl-5/issues/41#issuecomment-2106871619, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB5CFSQSC4ZJRJALPR75MC3ZCBVL3AVCNFSM6AAAAABGACJGWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWHA3TCNRRHE.
You are receiving this because you were mentioned.Message ID: @.***>


How to install v0.2

Hi, I used this command to install hnswlib
pip install --user git+https://github.com/nmslib/hnswlib#subdirectory=python_bindings

it is v0.2
but now it is v0.3, So how can I install v0.2?
Thank you!

Hi @UpCoder ,
I've added a tag for v0.2, so you should be able to use the following command:
pip3 install --user<EMAIL_ADDRESS>
I wonder, are experiencing problems with the current version in master (it should be backward compatible with v0.2)?

Thank you for your reply. But I found it can not solve my problem.
When I load the index file which I trained on v0.2 instead of v0.3, it will occur this error:
Warning: Calling load_index for an already inited index. Old index is being deallocated.Warning: loading of old indexes will be deprecated before 2019.
Please resave the index in the new format.
File "/opt/tiger/ensemble_work/projects/RetrievalVideoWeb/back_end/retrieval/retrieval_douyin.py", line 38, in build_hnsw
    p.load_index(index_save_path, max_elements=paras['construct']['num_elements'])
MemoryError: std::bad_alloc

But I change the version to 0.2, It still doesn't work for me.
Do you have any suggestion about that?
The memory is enough:
top - 10:21:20 up 14:59,  0 users,  load average: 6.29, 6.85, 6.57
Tasks:  10 total,   1 running,   9 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.2 us,  0.0 sy,  0.0 ni, 99.8 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem:  15360.00+total, 4391.152 used, 10968.84+free,    0.000 buffers

and the size of the index file is 20MB.

@UpCoder That is strange. It seems like the file is corrupted (which would lead to this warning). Can you share it?
You can also try an earlier commit (pip3 install --user git+https://github.com/nmslib/hnswlib.git@10273f5705c1e14f82c3c7466f688742db2051ff#subdirectory=python_bindings).

Thank you!
It suddenly works for me...
The index file is Google

Great! I'll check it for problems...

@UpCoder
I've checked the file. The master version of hnswlib opens it without a problem...

@yurymalkov Thank you! Yes, the master branch works now. But I don't know what cause the error...

@UpCoder removed this confusing message, should be a "file not found" / "corrupt index" messages instead. (develop branch)


fix(org unit selector): restrict org unit tree

This PR restricts Organisation Units to those assigned to the selected dataset, see https://dhis2.atlassian.net/browse/TECH-1298.
Joe might slightly update the final design, but I think this would be within the overall approach of the ticket

This comment can be removed with these changes.


actions popover: Change "Topic Edit" to "View Source / Topic Edit".

We also change the focus from the topic editing box to the cancel button
when the topic is non-empty.

Automated message from Dropbox CLA bot
@rishig, it looks like you've already signed the Dropbox CLA. Thanks!

Split into two commits and merged, thanks @rishig!


#18583 fix routines statement call generation

correct functions call added

Check the following:

[x] Result of the "Execute stored procedure" for a procedure
[x] Result of the "Execute stored procedure" for a procedure with the complex name (must be quoted)
[x] Result of the "Execute stored procedure" for a function
[x] Result of the "Execute stored procedure" for a function with the complex name (must be quoted)

Result for the uncompiled function/procedure will not have parameters in the brackets - it is expected, first compile routine correctly.

Verified


Develop evaluation on full sequences

When testing the initial box is selected from the last landmark or initial frame ground truth


@updateAt doesn't work as expected

Bug description
Columns with @updatedAt are not automatically updated when the record is updated, but the value is set on insert.
How to reproduce

Run migrations and generate a prisma client
Create a new record. You can see that fields created_at and update_at have the same value - it's ok.
Update the record one more time.  The fields created_at and update_at have the same value after any update. The value of  update_at wasn't changed.

Expected behavior
Columns with @updatedAt has a new value of current time after each update.
Prisma information
generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native", "linux-musl"]
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model Test {
  id            String   @id @default(dbgenerated("public.uuid_generate_v4()")) @db.Uuid
  name          String
  createdAt     DateTime @default(now()) @map("created_at") @db.Timestamptz(3)
  updatedAt     DateTime @updatedAt @map("updated_at") @db.Timestamptz(3)
}

await prisma.test.usert({
  where: { name: 'test' },
  update: { name: 'test1' },
  create: { name: 'test' },
});

Environment & setup

OS: macOS, Ubuntu
Database: PostgreSQL
Node.js version: v19.8.1

Prisma Version
prisma                  : 4.14.0
@prisma/client          : 4.14.0
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine d9a4c5988f480fa576d43970d5a23641aa77bc9c (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli d9a4c5988f480fa576d43970d5a23641aa77bc9c (at node_modules/@prisma/engines/migration-engine-darwin-arm64)
Format Wasm             : @prisma/prisma-fmt-wasm 4.14.0-67.d9a4c5988f480fa576d43970d5a23641aa77bc9c
Default Engines Hash    : d9a4c5988f480fa576d43970d5a23641aa77bc9c
Studio                  : 0.484.0

Could you try out if this also happens when the field with @updatedAt is not mapped via @map to a different name? Maybe that is where this bug stems from. Thanks!

I have the exact same issue. UpdatedAt is stuck at the same time as createdAt's @default(now()).

I have the exact same issue. UpdatedAt is stuck at the same time as createdAt's @default(now()).

You should remove any assignments to updatedAt in your code, except for @default(now()). Don't touch it at all. It'll be managed by ORM

I have the exact same issue. UpdatedAt is stuck at the same time as createdAt's @default(now()).

I have the exact same issue. UpdatedAt is stuck at the same time as createdAt's @default(now()).

Here's the right syntax: updatedAt DateTime @updatedAt @default(now()) This is what eventually worked out for me.

it worked for me thank you


email column not populated

How's it going? Thanks for building this.
I'm following your set up but when I submit my form, I see a new row and the timestamp column gets filled by the value from my payload for email is not. Any idea why that might be?

https://github.com/jamiewilson/form-to-google-sheets/issues/42


Add support for registering and unregistering fonts

Adds support to register and unregister fonts in CTFontManager.  This allows apps to use custom fonts by either registering them programmatically or by including them in the app's info.plist
Fixes #1022
Fixes #1250

This change is

:clock1:

@Status Stub

how come we're leaving this out?

Refers to: Frameworks/CoreText/CTFontManager.mm:128 in f49940a. [](commit_id = f49940a0f302d667fae27df18c680b174b3fb430, deletion_comment = False)

@Status Stub

It wasn't one of the functions in issue #1022.  I only added the other unregistering ones because they were needed for testing.

In reply to: 263722645 [](ancestors = 263722645)

Refers to: Frameworks/CoreText/CTFontManager.mm:128 in f49940a. [](commit_id = f49940a0f302d667fae27df18c680b174b3fb430, deletion_comment = False)

possibly excessive but might be good to add tests that validate that the registered fonts are accessible from CG-side as well

@Status Stub

I realize we didn't explicitly call it out in #1022, but it'd be good to take care of this now, just to finish up the feature set.

In reply to: 263724102 [](ancestors = 263724102,263722645)

Refers to: Frameworks/CoreText/CTFontManager.mm:128 in f49940a. [](commit_id = f49940a0f302d667fae27df18c680b174b3fb430, deletion_comment = False)

@Status Stub

fix annotation!

In reply to: 263735377 [](ancestors = 263735377,263724102,263722645)

Refers to: Frameworks/CoreText/CTFontManager.mm:128 in f49940a. [](commit_id = f49940a0f302d667fae27df18c680b174b3fb430, deletion_comment = False)


blank($value) helper

Laravel Version: 9.351
PHP Version: 8.2
Database Driver & Version: PG14

Description:
I wanted to ask if there is a reason why the blank helper doesn't include an isset check?
    function blank($value)
    {
        if (is_null($value)) {
            return true;
        }
    ....

should be
    function blank($value)
    {
        if (!isset($value) || is_null($value)) {
            return true;
        }
    ....

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

isset — Determine if a variable is declared and is different than null

https://www.php.net/manual/en/function.isset.php
As $value is always declared inside the function scope it is a parameter, checking only for null is sufficient.


Metrics: Move TimeSeriesCumulative and TimeSeriesGauge to top level. Hide TimeSeries.

To make APIs more consistent with the proto definition.

Codecov Report

Merging #1306 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1306   +/-   ##
=========================================
  Coverage     82.59%   82.59%
  Complexity     1302     1302
=========================================
  Files           198      198
  Lines          6382     6382
  Branches        585      585
=========================================
  Hits           5271     5271
  Misses          951      951
  Partials        160      160

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 ee73299...10c3764. Read the comment docs.


Product and person css updates

Issue
Resolves #569
What was done

[x] Updated the person name to text wrap when name is too long
[x] Fixed it so that long tag names have the same padding on the right as they do the left
[x] Moved person note icon to directly after person's name
[x] Fixed a bug where if you typed a new person name into the assignment form, the input width would get larger once the name got too long. Now the width doesn't change.

How to test

Test that the above is visually true.

FOR DEVS
Feature URL: See feature branch
FOR APPROVAL
Approval URL: See Approval branch

@smle225 Weird. I didn't change the icon size.


Add INTAKE_PATH default catalog loading

Closes #167.
This PR updates the default catalog loader to check for any directories specified by the INTAKE_PATH environment variable. This behaves like a regular path where each directory should be colon separated. If each directory exists it will be included in the loading of default catalog files.

This sounds like a very reasonable thing to want to do.
I have a couple of worries here:

colons make poor separators on windows, where a colon may be part of a path. Perhaps the syntax needs to be a JSON list?
I would add this as a config file attribute, which may be the simplest way for a user/sysadmin to pass the information in.
should we allow remote directories or specific remote catalogue files here? I think that, as things stand, remotes would be loaded (except that the paths always contain colons).

For ease of use, I think we have to use the path conventions on each platform: colons for Mac/Linux and semicolons on Windows.  I think remote directories might be too confusing for an environment variable named *_PATH.

By the way, the failure in travis is related to the package upload after testing is done, apparently the secure token isn't being resolved. I am tempted to remove the upload altogether and handle releases manually. Conda-forge should certainly be the long-term aim, but that has higher overheads per release, which I expect to still be frequent.

I've added windows semicolon support and added the option to the config as catalog_path but have overridden from the environment still.

Well, it seems I was wrong about removing the sleep, since now one of the tests fails. I'll look into why that is later, but you can just reinstate the sleep for now.
Also, feel free to remove the package upload step - either completely, or with an extra condition on the availability of the token.

Done and done!

@martindurant I'm not sure I understand what all these test error are. Do you have any thoughts?

No, I can''t think of anything obvious. Perhaps remove that print, and see if it's just "one of those things"?

I had forgotten about the print. Hopefully it is something as daft as that!

OK, it's good.
I can merge this now, if you are done.

Yes please!

Done. Thanks for this.


Shorten long lines of code in part 2

I think this is ready to merge.  It makes all the code in Part 2 fit within the margins of the PDF.

If there are no objections, I will go ahead and merge this tomorrow.

Sorry, got busy with other things, but I'll take a quick look today...

Looks good!  A few comments/suggestions:
Burgers_approximate:

Should we provide links to exact_solvers/burgers.py as we do in the Burgers notebook?  Here we include much more code directly so maybe not needed.  Also, should we somehow link to clawpack/riemann/.burgers_1D_py?   (Same question applies to other notebooks in Part II.)

Regarding your query, I don't think I've ever tried the HLL solver for Burgers', but probably someone has.  Remove this query?

Shallow_water_approximate:

I like your simplified derivation of the Roe average states, here and in Euler, but should we also give a reference to the more general (?) parameter vector approach from Roe's original paper?

For the Roe solver with the entropy fix, also show PyClaw solutions to illustrate that this solution gives good results in the context of a numerical method? (Even though the Riemann solution itself still looks very different from the true solution with discontinuities rather than rarefactions.)  I guess this is covered in the last notebook of Part II (for Euler, anyway), so maybe just refer forward to that notebook rather than showing an example?

For  Transonic rarefaction example a, the true solution shows an interesting bump in hu in the rarefaction wave between q_l and q_m.  It might be clearer to the reader why it looks this way if the next cell In[20] used yaxis = 'hu' rather than u? But all the other phase plane plots use u so maybe this would be confusing.

Euler_approximate:

Equation (12) for $\hat H$  is too long in the pdf.

Euler_compare:

The figures are too wide on my browser, and wider than in other notebooks.

In the discussion of each example, perhaps suggest that the reader adjust the value of N in each solver and re-execute the cell.  Perhaps define N = 50 at the top of the cell and use this N in each solver so it's easy to change?  Or make this a widget?

I just noticed another problem: in Euler_compare the pdf version only shows the solution at t=0, rather than two times.

I implemented your suggestions in the Burgers chapter: linked to exact_solvers/burgers.py and clawpack/riemann/burgers_1D_py.py and removed my query.  I also shortened the PyClaw script by removing some unneeded options.

In the shallow water approximate notebook, I added a link to Roe's paper and chapter 15 of FVMHP that discuss the parameter vector approach.  I included a second h-hu state plane plot for the example with the bump, and a comment about this.
I agree that it would be nice to include some pyclaw simulations in the shallow water notebook.  I will do this in a separate PR.

In the Euler approx notebook, I added links to the exact solver and the Clawpack solver, and broke up the equation that was still too long.
The euler_compare notebook still needs some work, which I will do in a subsequent PR.


Init job fails because digits_sklearn_opencv.rpz is too big for direct download

The init job downloads an HTML file warning about the file size instead of the file.
init/init.py

Fixed with e3de83bc: moved files to my S3.


Add interfaces from the current draft of PSR-15

It will be useful to start playing with it.
I've added the interfaces as-is from the current version of the draft.

👍

Thanks!


Chap4 (CNN_working_details.ipynb) -- Squeeze on model output

On the cell to train the model
def train_batch(x, y, model, opt, loss_fn):
    model.train()
    prediction = model(x)
    batch_loss = loss_fn(prediction, y)
    batch_loss.backward()
    optimizer.step()
    optimizer.zero_grad()
    return batch_loss.item()

Prediction have the outcome of [1, 1] while we give the y_train
y_train = torch.tensor([0, 1])

We got a miss matching size and the code doesn't run
Error Trigger
Using a target size (torch.Size([1])) that is different to the input size (torch.Size([1, 1])) is deprecated. Please ensure they have the same size.

To fix it, either
y_train = torch.tensor([0, 1]).to(device).float().unsqueeze(1)

def train_batch(x, y, model, opt, loss_fn):
    model.train()
    prediction = model(x)
    batch_loss = loss_fn(prediction.squeeze(0), y)
    batch_loss.backward()
    optimizer.step()
    optimizer.zero_grad()
    return batch_loss.item()

COOL!!


Cask sudo prompt uses GPGTools logo

Hi, I received the following prompt when attempting to install Microsoft Teams through Applite:

The lock logo is from the https://gpgtools.org/ project, and I was /super/ confused by this because I first thought it prompted for my GPG keychain passphrase, which was of course unexpected.
If anything this should pop up an Apple system authorization dialog, and if a custom one is not avoidable it should not use icons from unrelated projects, copyright issues aside.

Hi, you were prompted for your admin password because Microsoft Teams has a .pkg installer which requires it. We need to pass the password into the running brew shell instance through the 'SUDO_ASKPASS' parameter, and given that Applite is a GUI focused app we needed a graphical solution. The default apple password prompt unfortunately cannot be used through the command line, so we ended up using the 'pinentry-mac' package, which is part of GPGTools. It is the most secure way we found to pass the password into the shell. See #5 for more info.

Thanks for letting me know. I'll close the issue for now.


Improve the design of button on create memory form

Improve the alignment of submit button and clear button on create memory form

Thanks for the PR
@luckykumarirai you can't make a PR unless the issue is Assigned to you
Also, we want the button to be placed one below the other
So I am closing the pull request

Thanks for the PR
@luckykumarirai you can't make a PR unless the issue is Assigned to you
Also, we want the button to be placed one below the other
So I am closing the pull request


https://github.com/SAP/connect-openui5/issues/49

fix Issue https://github.com/SAP/connect-openui5/issues/49.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.J. Moldawski seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@eugen-eugen thanks for bringing this up and sorry for the delay to respond.
I really appreciate your PR 👍 I just did some minor tweaks on top of it.


Long songs may raise MemoryError

In case of long sequences setting a song variable may result in
MemoryError: memory allocation failed, allocating 160208 bytes

Perhaps it would be better if the data is read in chunks from an external file.

Great repo. Yes, this would be a really nice feature. I am trying to play longer songs as well.


Replace sortby query parameter with ordering for search endpoint

Context
In #331, we replaced the client-only query parameter p and size with offset and limit, respectively, to align with the BE API implementation of the search endpoint.
In this issue, we want to replace the client-only sortby parameter with ordering to match the BE API.
Solution or next step

Remove the usage of sortby parameter from the useSearchManager hook
Update the data fetching logic to ensure the search functionality works as expected with the new implementation

After discussion, we're also removing the client-only empty query as part of this PR.


Add workaround for hanging UI when scrolling main charts list

https://user-images.githubusercontent.com/16542463/174160524-870a34d7-7106-4fe2-97dd-07a86aaa25a2.mp4
Seems to work, not an ideal solution but it makes the app performant again.
Also handles splitview menu for iPhone in landscape mode.

Great job!


create mechanism for creating an order

Let's have an order flow of:

POST /api/order/
Host: localhost:8080
Auth: basic username:password
Content-type: application/json
Accept: application/json

{
    "orderId" : 12345, // if 0 create new order
    "orderDate : {current date},
    "customerId" : "54321",
}

Returns

{
  "orderId": neworderid_
}

And for adding items we can have:

POST /api/order/
Host: localhost:8080
Auth: basic username:password
Content-type: application/json
Accept: application/json

{
    "orderId" : 12345,
    products: [
      {
        "productId" : "2",
        "quantity": _N_
}

Ok, I've implemented most of this, but I haven't implemented quantities for products in an order – I'll have to look at how to implement a List of ElementCollections.


Missing ASG IAM output variables on Gitlab example

Missing ASG IAM output variables on Gitlab example
Steps to reproduce
ᐅ cd ./examples/gitlab-simple-ha
ᐅ make generate-ssh-key
ᐅ make render-tfvars
ᐅ make network
ᐅ make plan
ᐅ make apply
terraform-0.12.2 plan -out=tf.out

Error: Reference to undeclared output value

  on main.tf line 65, in resource "aws_iam_role_policy_attachment" "s3-full-access-attachment":
  65:   role       = module.gitlab-asg.asg_iam_role_name

An output value with the name "asg_iam_role_name" has not been declared in
module.gitlab-asg.

Error: Reference to undeclared resource

  on ../../modules/persistent-ebs/outputs.tf line 12, in output "iam_profile_policy_document":
  12:   value       = aws_iam_role_policy.attach_ebs.policy

A managed resource "aws_iam_role_policy" "attach_ebs" has not been declared in
gitlab-asg.service-data.

Makefile:63: recipe for target 'plan' failed
make: *** [plan] Error 1

Version
Terraform v0.12.2
Terraform AWS Foundation master v0.9.3

Thanks for the ticket, we'll take a look.

I looked into this problem, with terraform 0.12.7 I got errors:

Error: Reference to undeclared resource
on ../../modules/persistent-ebs/outputs.tf line 12, in output "iam_profile_policy_document":
12:   value       = data.aws_iam_role_policy.attach_ebs_policy_doc.policy
A data resource "aws_iam_role_policy" "attach_ebs_policy_doc" has not been
declared in gitlab-asg.service-data.
Error: Reference to undeclared output value
on main.tf line 43, in resource "aws_iam_role_policy_attachment" "s3-full-access-attachment":
43:   role       = module.gitlab-asg.asg_iam_role_name
An output value with the name "asg_iam_role_name" has not been declared in
module.gitlab-asg.
Error: Reference to undeclared output value
on main.tf line 52, in resource "aws_iam_role_policy" "associate_eip":
52:   role = module.gitlab-asg.asg_iam_role_name
An output value with the name "asg_iam_role_name" has not been declared in
module.gitlab-asg.

After looking around I fount out that this two commits are at fault:

https://github.com/fpco/terraform-aws-foundation/commit/76305263bd7bf0a77d2f0fa7931db37ae5b3ff63 many variables were renamed and moved, and an output was left with the value aws_iam_role_policy.attach_ebs.policy that does not exists
https://github.com/fpco/terraform-aws-foundation/commit/d63c3aaa242ab133b296bb49c6f42ac73a9e7d0b#diff-de7b621296cb5354086132f4fc41881e some outputs where deleted without giving a replacement

I made a fix commit https://github.com/fpco/terraform-aws-foundation/commit/f0f66e012c79b0270a89808187f87784254073d1 renames the faulty value of the output in 1 and adds a new output for 2 with the value module.instance_profile.iam_role_name that I think was the intended output here, @ketzacoatl can you please check if using this value for this output is ok?
and @devgnx could you please check that commit to see if it solve your issues, with those fixes it runs good to me

@devgnx The branch to test is 241-Missing-ASG-IAM-output-variables.

Hi @JoseD92 and @ketzacoatl, thank you for the quick response, I'll test the branch 241-Missing-ASG-IAM-output-variables as soon as possible.

Variables are now bound, but there still some issues, maybe worth a new Github Issue but for now I will post here:
S3 bucket policy is timing out while waiting for s3-full-access become success.
Maybe is related to:
https://github.com/terraform-providers/terraform-provider-aws/issues/9414
https://github.com/terraform-providers/terraform-provider-aws/issues/9435
Steps to reproduce
ᐅ cd ./examples/gitlab-simple-ha
ᐅ make generate-ssh-key
ᐅ make render-tfvars
ᐅ make network
ᐅ make plan
ᐅ make apply "tf.out"
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Creating...
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [10s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [20s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [30s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [40s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [50s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [1m0s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [1m10s elapsed]
module.docker-registry-s3-storage.aws_s3_bucket_policy.s3-full-access: Still creating... [1m20s elapsed]

Error: Error putting S3 policy: timeout while waiting for state to become 'success' (timeout: 1m0s)

  on ../../modules/s3-remote-state/main.tf line 94, in resource "aws_s3_bucket_policy" "s3-full-access":
  94: resource "aws_s3_bucket_policy" "s3-full-access" {

Makefile:65: recipe for target 'apply' failed
make: *** [apply] Error 1


Fixed mdd android c++ miengine glass tests

Verify this fix works in both VS2015 U3 (micro update 3.5) and VS2017 RC:

Fixed the build error in android C++ debuggee projects, we might need to revisit this if we release new version of android application later.
Fixed test script to retrieve the correct %errorlevel% code when failed to build projects. Currently the test script marked all of glass tests as successfully even the projects failed to build due to missing the redirect "stderr" code.
Fixed the load exceptions issues in glass2 ": Unable to load one or more of the requested types"
Fixed the "COM API failures" issues due to fail to load one binary in glass2 runtime.

Hi @richardzeng1985, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

I was not able to create a new pull request, so try to close this one first.


Automatic resuming of flows after azkaban-executor restart

This is a new feature suggestion. Feedback much appreciated!
Rationale
We need to support resuming flows and jobs after azkaban-executor is restarted. Currently Azkaban just marks interrupted flows and jobs as FAILED on startup. This is done silently without sending flow failure notifications or anything like that.
Reasons for "restarting" azkaban-executor include at least:

Azkaban-executor java process crashed (OOM, for example)
Azkaban version update requires a restart to apply changes (especially in a single executor or solo-azkaban setup)
Hardware failure or some other problem requires replacing the azkaban-executor with an entirely new instance

Design
Actions on startup for interrupted flows:

Start execution for the flow again with the same execution id and project version
Jobs that support resume are started again with JobState.isResume=true
Jobs that don't support resume are started over

So jobs that don't support resume get "1 extra retry" by default
This can be disabled by setting resume.retryJobIfResumeNotImplemented=false

Jobs are resumed without incrementing the retry attempt count – they should have the attempt number that was running when flow was interrupted
Add new flow level email notification option resume.emails (similar to the existing failure.emails)

New Job API:
a) new interface StatefulJob extends Job

Adds method: void setState(JobState)

This is called before Job#run. Job implementation would typically save the provided state in a field so that it can use it when run() is called
StatefulJob could also be an abstract class that implements setState method and stores the provided JobState in a protected field

OR
b) new optional constructor arg JobState (called via reflection if the class has this constructor)

args: String jobid, final Props sysProps, final Props jobProps, final Logger log, JobState state
A bit "magical", because the job doesn't explicitly declare that it "supports resuming". Also easier to make a mistake when implementing job types.

New interface JobState
New interface JobState with methods:

void setState(Props)

This persists the given state Props into DB (key: flow/execution/job/attempt)

Props getState()
boolean isResume()

Jobs could basically get the same result by checking JobState.getState() != null in the beginning of the run, but I think that having a specific method is useful.
Naturally isResume will keep returning false for a regular (not resumed) execution even if the job saves something to the JobState.

This way the job can store some execution state that is fetched back for it before resuming.
Notes about our use cases
Usually we just need to store an external job id after it has been launched, and when resuming we continue polling for the external status by id.
Resuming can also be useful for "locally running jobs" if they know how to continue from whatever state they have saved so far.
In practice we for example launch AWS EMR clusters/jobs externally with a custom job type for that purpose. We have some other custom job types as well that launch a job externally and then poll for that to complete.
In most of the cases we would need to store an external job id after it has been launched. When resuming we either continue polling for the external status by id, or launch a new external job if there's no existing job id to track.
Implementation details
Pipelined flows
Order must be preserved for flows that are running in pipeline mode. They must be resumed in their original submission order.
Otherwise some flow could've ran half of its jobs while a later execution for the flow is waiting for it to complete. If restart happens now and the flows are submitted in the opposite order, that would mean that the other flow starts executing and the job that was in the middle of its work becomes blocked.
Job and flow logs
Jobs & flows must continue appending to the logs from the interrupted execution.

For example, flow log should have all the history before the flow was interrupted + info about how execution and jobs were resumed + anything else that normally comes after that.

JobState

azkaban.jobExecutor.JobState interface belongs to azkaban-common module (next to azkaban.jobExecutor.Job)
JobState instance is provided to job types by calling Job#setState(JobState) (if the job supports resuming)
The JobState implementation saves the Props in DB when JobState#setState(Props) is called

Documentation
At least document all new property names.

Any updates on when this feature will be available?

Hopefully soon, but as you can see this post is only 4 days old. First we would need review of this plan by repo owners and an "ok" before we can start implementing it in practice. I would say it will still take weeks before this could be seen as a working feature in the master branch.

Thanks for the detailed write-up.
I will have to think more about it.
At Linkedin, we currently only start a new executor process and let the existing flows finish before shutting down the old executor processes. We don't have any resumable job type currently.
Yes, it wold be nice to support resuming in a case of an H/W failure. However, h/w failure is rare so far. OOM in the executor process is also rare. I am interested in supporting a way to restart the executor process without affecting the running job processes. This will simplify our deployment process and gives us the flexibility to recover from a software bug in the executor more quickly.
Do h/w failure and OOM happen often in your environment? Or is the ease of software update the main motivation for you?

The main motivation is being able to ensure that important scheduled flows are completed even if the executor crashes in the middle of an execution. A part of ensuring that is the ability to continue externally running jobs in a clean way after any kind of restart.

It would be a real problem if we couldn't continue polling externally launched jobs after a restart and launch a new overlapping job instead. Currently we have a custom way to synchronize the external jobs via a DB, but this still means that when we resume polling the job gets a new execution id and the previous execution has been marked as FAILED.

Main OOM scenarios are:

Metaspace (Java 8) runs out after reloading custom job types multiple times

Because each reload creates new classloaders that aren't always entirely cleaned up, most often because of some background threads left running and preventing classes to be garbage collected from the old classloaders

OS level "OOM" that makes OS sacrifice java process and kills it

This can happen if additional processes created by command jobs consume too much memory (as a special case when a process creates sub-processes). That's partially caused because we have disabled available memory check before running command jobs, because of reasons.

Too many / heavy flows running at the same time, basic OOM

I can't be sure, but I think this is because azkaban-executor creates instances of ExcutableNode/ExecutableFlow for each node in the graph.
Example of heavy graph: you have chained, say, some big flow, into a bigger flow that runs the same big sub-flow in a of sequence 30 times.

Running out of heap size because of running enough ~memory-hungry jobs that run within the executor JVM

Hasn't really happened to us, but I can imagine it rather easily

Of course if we hit any of these issues we try to fix the cause of the problem. But you can't always predict problems so Azkaban should be able to recover from crashes automatically.

@juhoautio i think it's a valid feature request. Thanks! I'm curious about how you would plan to implement setState and getState, and how do we define a state exactly?

I'm curious about how you would plan to implement setState and getState

First of all note that Job#setState(JobState) and JobState#setState(Props) are entirely different methods. Actually should rename the latter to JobState#setProps(Props). But I'll stick with the original method name for now..
Then to some kind of impl. plan.
Look at JobTypeManager#buildJobExecutor. When building the executor:

Check if the job is resumable (how exactly, depends on what kind of Job API is chosen for resumable job types)
Instantiate the job type as usual (call constructor with reflection)
Call Job#setState on the created instance
Continue as normal, eventually Job#run is called

Creating the JobState:

This would probably happen elsewhere and get passed as an argument to JobTypeManager#buildJobExecutor
Load the state Props from DB by <execution id + attempt number> (if exists).
If state is found for this execution/attempt, then it's a resume case and JobState is created with those Props and isResume=true. Otherwise it's created with empty Props and isResume=false.
Set the state on the job by calling Job#setState

Also JobState needs to have a way to persist the Props into DB when the Job calls JobState #setState. So some kind of DB gateway instance must be passed to JobState constructor.

and how do we define a state exactly?

I'm not sure what this question means?

@juhoautio Hi, this is exactly what we are looking forward to do. We process data in our jobs scheduled in azkaban. If azkaban goes down and comes up after a certain period of time, there is a data hole created for the jobs which did not run. Below example might clear this up:
Case Scenario: A job is scheduled hourly in azkaban. Let's say the job takes 45 minutes for successful completion. Let the scheduled time for the job be:
12pm -> 1pm -> 2pm -> 3pm -> 4pm and so on..
Let's say azkaban went down at 12:30pm and came up at 2:30pm.
Current Scenario: Azkaban will not restart the failed job (12pm job) or any missing instances in between. It will continue with its execution by running the next scheduled instance i.e. 3pm.
Expected Scenario: Azkaban should run in replay mode and re-run the 12pm job and other missing jobs. Here we have 2 cases:

Job was scheduled keeping concurrency on: Azkaban will launch all the missing instances together. Thus, at 2:30pm, three instances correponding to 12pm, 1pm and 2pm will be launched concurrently. Azkaban will continue with normal execution post this.
Job was scheduled keeping pipeline feature on: Azkaban will launch the 12pm instance at 2:30pm. It will put other instances in a pipeline. Once the execution of 12pm instance(which was re-run at 2:30pm) is over at 3:15(45min is the processing time for one job), azkaban will launch the 1pm instance at 3:15pm. This way, azkaban will try to catch up the lag period. Once azkaban catches up, normal hourly execution would continue.

Also, if possible, could you let us know a time-period by which this feature might be available? Or if there has been any progress at your end? We can probably discuss the design, if you have one ready.
Because we are also planning on making the changes in source code for the same. Just want to avoid duplicate effort.
Any help would be appreciated. :)

Thanks @priyanshjain28. We didn't consider "replay" mode for schedules, but that's a good addition, definitely. I think it could be handled separately, though. We haven't written any code for this yet. I was aiming at getting a common agreement on the specification with the repo owners before starting to implement anything. The goal being, getting code review to catch problems, and having this feature merged into the public repo to avoid diff with our own fork. We could have time to implement this, but I'm not sure how quickly we will be able to have a spec greenlighted by @HappyRay and @chengren311.

I'm going to start working on this. As there hasn't been a chance to prepare & agree on the spec with repo owners, I believe it won't be easy to get it merged in.. But even if so, please give any last feedback you might have. I think I'm going to drop a PR just for reference once this feature is ready.

@juhoautio sorry about the delay.
I plan to refactor the core DAG processing code to make it easier to maintain e.g. easier to unit test and understand. I hope to find time to do so in the next month or so.
This will likely touch many classes. I hope the end result will be better code that is easier to add new features.
If you can wait until the big refactoring is done, it may make your job and merge easier.
For your use case:

Azkaban version update requires a restart to apply changes (especially in a single executor or solo-azkaban setup)
Do you run in a multiple executor mode? If so, you should be able to start a new executor process to replace the existing instance as an active executor. Let the existing one finish processing existing flows. It has worked for us. Would it work for you?

I expect resuming functionality to have no impact on the DAG execution part of the application. Or it should be small at least.
We don't run multi-executor yet, but hoping to switch to that at some point. Making that switch requires some additional tooling and conf changes.
Yes, using multi-executor mode would help us with a deployment a bit and that alone is a reason enough to take it into use. But it won't help us with:

executor crash scenarios (because azkaban doesn't start the interrupted flows again)
long-running "streaming jobs" (can be running for days) that are running on an external cluster, that we'd rather not interrupt, but just continue tracking them

@juhoautio thanks for initiating this. Ability for flows to withstand (rolling) restarts would be great to have, and we'd love to help realize this. Any progress more progress on this besides https://github.com/azkaban/azkaban/pull/1438?

@swamisun yes, we have this implemented according to our needs and it's been in production use for a while. For us it was enough for now to implement the bullet points that you can find in the issue description in the beginning of the Design section (the ones before New Job API etc.)
In our case resumable jobs are typically such that are actually tracking some external task. The external task ids we store into a database in our custom job types so that they can fetch them from there when a job is resumed. It would be nicer if azkaban itself would support JobState as described above.
Any way, if this (what we have) suits your needs, I guess I could prepare a pull request to share the code. But currently it seems to me like it won't get to be included in the main Azkaban repository at least any time soon.

@djaiswal83 DAG rewrite also mentioned here https://github.com/azkaban/azkaban/issues/1127#issuecomment-325883966 – what do you think about this?

As I mentioned in other thread, there is no plan to work on it in near future.

@djaiswal83 thanks. We have automatic resuming implemented in our private fork. Are you open to including it? If yes, I could prepare a pull request. But it’s of course some work, so I wouldn’t be making PR if you don’t see it as a useful contribution.

Let me get back on that in a day or two.

@juhoautio This is very useful feature. Thank you so much for working on it. I have couple of doubts. Below I have mentioned the same.

Which executor will resume the flow? Can resume be picked up by any executor? Or does it go to the same executor?
It will be good to resume from Dispatch logic place (azkaban.executor.ExecutionController). Please ignore my comment if it is already happening at that place.
My assumption is : this feature will be useful to treat flow as a stateless entity and resume it from where it is left. It will allow us to resume flows no matter where executors are running, bare metal or containers.
I am not clear about resume for streaming or long running jobs. How is it working currently on your production environment?

Which executor will resume the flow? Can resume be picked up by any executor? Or does it go to the same executor?

With the current implementation, it may be any of the active executors.

It will be good to resume from Dispatch logic place (azkaban.executor.ExecutionController).

Ok, why? In our impl it's done by RunningExecutionsUpdater because it monitors running flows and

it can detect that the executor is not active any more
it can deduce from a "Flow does not exist" response that the execution is not running on the assigned executor any more

When an execution needs to be resumed, RunningExecutionsUpdater calls ExecutorManager, which then does  this.queuedFlows.enqueue.

My assumption is : this feature will be useful to treat flow as a stateless entity and resume it from where it is left. It will allow us to resume flows no matter where executors are running, bare metal or containers.

In comparison, what would be a stateless flow entity?

I am not clear about resume for streaming or long running jobs. How is it working currently on your production environment?

For these the Azkaban jobs are tracking some external jobs that remain running continuously, potentially forever. Our streaming job type is such that when the Azkaban job is killed, it terminates the external cluster, and once it has terminated, then the Azkaban job also reaches the KILLED status.
When an execution is moved to another executor, our job type is able to resume tracking the external job because the external job's ID is persisted in a DB and it's read from there when the resumed execution starts. We haven't yet implemented the JobState interface that I specified in the description above, so it's a bit of a hack currently. Having JobState as a feature of Azkaban's job type plugin interface would allow for a clean implementation.

Hi @juhoautio we have similar use case to the resume you mentioned. However, in our case it may not be a forever running streaming job, but jobs that may have been spawned to Yarn.
From 3 years ago, our use cases have evolved and we in fact have started witnessing OOMs. In addition, upgrade/rollback of Executors will indeed be simplified by bringing down the Executor Server and restarting after the upgrade.
Our (Linkedin's) use case for restart ability will require the flows to get restarted with the same execution id and fast forward to the point in DAG where the FlowRunner was pre-crash. We would also need to connect to all the jobs that were spawned to external entities such as Yarn or Kubernetes. We don't at least for now see the Jobs as "Resumable", but we do need to re-establish a connection with those or restart if required.
Sounds like your implementation hits a number of these points. Therefore, I am really keen to see the PR.

@arvindpruthi I would like to make a PR. But it would be nice if @djaiswal83 or other repo owner could confirm that there is bandwidth for reviewing & merging it – or are you, @arvindpruthi also eligible for that? :)

Our (Linkedin's) use case for restart ability will require the flows to get restarted with the same execution id and fast forward to the point in DAG where the FlowRunner was pre-crash.

Cool, that is how our fork behaves.

We would also need to connect to all the jobs that were spawned to external entities such as Yarn or Kubernetes. We don't at least for now see the Jobs as "Resumable", but we do need to re-establish a connection with those or restart if required.

To resume & continue tracking external jobs we currently save the external job's id in a custom DB table. Ideally Azkaban's Job interface could natively support saving some kind of job / attempt state that could be read in the job type code on resume. However, I would submit the first version of resuming feature without that building block to keep the scope manageable. Job state could be added after that. Do you have anything against that?

Hi @juhoautio I am one of the repo owners and the tech lead for Azkaban at Linkedin. This is an important PR and busy as we might be, either @djaiswal83 or someone within my team will find time to review the PR. I agree to keep resumability out of the PR for now.

@arvindpruthi thanks. I'd like to make that PR, but would it be possible to get PR https://github.com/azkaban/azkaban/pull/2515 merged first?

@juhoautio we are going through an internal process to manage commits due to which everything is held off. Please be patient as very soon we will bring both internal and external repos to sync and start merging PRs.


Cell types from olfactory bulb

Hi,
Please could someone add the following cell types from the olfactory bulb?

mitral cell
tufted cell (two sub-types "middle" and "external" plus ideally a generic version, since the sub-types aren't always disinguished)
granule cell
periglomerular cell

and the same from the accessory olfactory bulb:

mitral cell
tufted cell (no IRI that I can find)
granule cell
glomerular layer cell

as well as olfactory receptor neuron (which projects to the olfactory bulb)

There is no mention of tufted cells in the accessory olfactory bulb in https://doi.org/10.3389/fncir.2020.561822. I don't see a statement that says that they do not exist exist there, however there is a discussion that they do project to the AON.

(for the time being, we have no data from nor models of the AOB, only the main olfactory bulb, so we could punt on the AOB entries for now)

@lzehl we really have to push the issue with brain region + cell type! This will be crucial in this case and I'm sure it won't be the last time...

TODO:

add all cell types above (except accessory olfactory bulb tufted); please use 'neuron' instead of 'cell'; also keep combinatoric names in a human readable order (e.g., olfactory bulb external tufted neuron; very other name goes into synonym)


SUNEDITOR.create.fail [React]

Hello everyone,
is there maybe a issue with React ? Because in Fiddle it sems to work fine.
`import React, { Component } from 'react'

import 'suneditor/dist/css/suneditor.min.css'
import suneditor from 'suneditor';

suneditor.create('sample', {
 // insert options
});
export default class Editor extends Component {
  render() {
    return (
      <div>
    <textarea id="sample" className="sample">Hi</textarea>
      </div>
    )
  }
}

Hi, @Sio5
Suneditor takes an ID or DOM element as its argument value.
It seems that the creation failed because the "textarea" has not yet been rendered.
Call suneditor.create function after the "textarea" is rendered.

Hey , JinHong88
Thanks for Reply.
Yea figured it yesterday out aswell.
componentDidMount did the job, all fine.


[Video player]: does not restore focus to video player after playing – React Safari Mobile

Description
I played the video in content block segmented, it opened in the native player, I navigated to close the video and the focus was brought to the top of the Content block, now I have to navigate down the whole page again 👎
Expect Focus to be restored to the video player on close
Recording
https://user-images.githubusercontent.com/45692622/158698510-37ceb512-31d0-4113-aab9-07686b8863c3.mov
Component(s) impacted
tested on Content block segmented
Could impact any component / template that utilizes video player
Confirmed this is the case

Content block simple
Content group simple
Lead space block with video
etc

Browser
Safari
Carbon for IBM.com version
v1.32.0 rc0
Severity
Severity 2 = Aspects of design is broken, and impedes users in a significant way, but there is a way to complete their tasks. Affects major functionality, has a workaround.
Application/website
c4IBM.com
Package
@carbon/ibmdotcom-react
CodeSandbox example
https://carbon-design-system.github.io/carbon-for-ibm-dotcom/next/react/?path=/story/components-content-block-segmented--default
Steps to reproduce the issue (if applicable)
No response
Release date (if applicable)
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate issues

Looking at this, it might not be something we can adjust since the focus is captured within the Kaltura player itself. We wouldn't be able to manipulate the focus from the player


Spelling

Thanks @codykonior - there appears to be a problem with the build server. Once that's resolved, I'll get this merged in 😃. Iain


Add ability to set additional HPA annotations

Proposal
Add ability to set additional HPA annotations:
I'm trying to provide both solutions: keda autoscaling and kube-downscaler (https://codeberg.org/hjacobs/kube-downscaler)
For kube-downscaler  it's necessary to annotate HPA with corresponding "downtime" annotations.
So it would be nice to have an ability to provide HPA annotations in horizontalPodAutoscalerConfig
thanks
Use-Case
make Pod autoscaling more flexible
Anything else?
No response

Adding additional labels to HPA is something that we can support, though.

I agree with @tomkerkhove , we can just add support to adding additional annotations, how end users use them is their scope.
Maybe we could add a section in the SO or just pass SO labels to HPA. WDYT?

I think that's fair


XMP tag has been deprecated since HTML3.2

I found this library to be very useful, and one of my colleagues used it to help us build API documentation that didn't require us to replace all of the > and < with > and &lt. In fact, I see it as a competitor to static-site generator tools like Jekyll, Octopress, and DocPad. In fact, that's exactly what we did with our API documentation. we used Strapdown.js to create a static page.
However, it recently came to my attention that <xmp has been deprecated since HTML3.2.
Should you consider using a non-deprecated tag in this library, such as <pre> or <code> as suggested by the Mozilla HTML documentation on XMP?

Note: Do not use this element.

It has been deprecated since HTML3.2 and was not implemented in a consistent way. It was completely removed from the language in HTML5.

Use the <pre> element or, if semantically adequate, the <code> element instead. Note that you will need to escape the '<' character as '<' to make sure it is not interpreted as markup.

A monospaced font can also be obtained on any element, by applying an adequate CSS style using monospace as the generic-font value for the font-family property.

http://stackoverflow.com/a/10830811

Except it doesn't make it unique. It simply leaves the library open to undefined behavior as described in the Stack Overflow link.  If everyone decided to go out and make up their own tags, then the Internet would be a mess.  There is nothing I see special or unique about Strapdown.js that isn't special or unique about some other library or tool that does use semantically correct markup.
If there is a good reason for this, it would be interesting to hear. I'm not against the idea of making up tags in practice, as long as it's not just because of ignorance of how HTML works.

For reference "undeprecating" the <xmp> tag for the benefit of strapdown and others was rejected by w3 (in 2013) as wont fix.
See https://www.w3.org/Bugs/Public/show_bug.cgi?id=12235#c15
Would a sensible way forward be to support a custom tag based on <pre> as an alternate syntax?

Wouldn't it just work to use a div? I'm no html expert but it seems like
that is what most libs do, no?
Le 5 janv. 2016 7:35 PM, "tortoise74"<EMAIL_ADDRESS>a écrit :

For reference "undeprecating" the  tag for the benefit of strapdown
and others was rejected by w3 (in 2013) as wont fix.
See https://www.w3.org/Bugs/Public/show_bug.cgi?id=12235#c15
Would a sensible way forward be to support a custom tag based on  as
an alternate syntax?
—
Reply to this email directly or view it on GitHub
https://github.com/arturadib/strapdown/issues/40#issuecomment-169178700.

It works with textarea right now

I know I'm late to the party but I would suggest using <script type="text/markdown"> as the container tag. This won't encode HTML entities and you won't have to set display:none; styling on it as well.

That's a good point. Although it's not uncommon to see markup in text/x-template tags for various template systems like Handlebars, Vue, etc. it's not the most semantic implementation I agree. The only other thing I could think of would be something like <template class="markdown">.

<template>  is meant for HTML code that is not readily rendered by a client, but instead leaves it in the DOM for scripts to manipulate.
Since any content is allowed, it's an obvious candidate as an alternative to the deprecated <xmp> tag.


Merge changes from 'staging' to 'main' (PR #213)

Change Summary
Summarise your changes in points

This PR includes changes from staging PR: https://github.com/ujala-singh/github-repository-dispatch-receiver/pull/213"

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code refactoring (restructuring existing code without changing any functionality)
[ ] This change requires a documentation update

Documentation/Release Plan

Problem Statement doc
Feature documentation
Release plan

Testing Checklist
Changes tested on

[ ] development
[ ] production
[ ] MABL Tests Link (if any)
[ ] Successful Workflow Links (if any)

Hey @ujala-singh, your main branch PR has been automatically created. In order to merge the PR, Please test your changes on staging (pre-prod) and update the change summary and checks accordingly.


Bump orchestrator version to 3.2.6

Current orchestrator version is 3.2.3 released on 04 Aug 2020.
Nowadays Orchestrator is not in active developing.
Latest minor version with fixes is v3.2.6 released on 27 Jul 2021.

[v] I've made sure the CHANGELOG.md will remain up-to-date after this PR is merged.

@cndoit18 review plz 🙏

@milero @calind ready for merge


Error installing apax

PS D:\GitHub_Project\apax> pip install apax
Collecting apax
Using cached apax-0.9.1-py3-none-any.whl.metadata (5.6 kB)
Collecting ase<4.0.0,>=3.22.1 (from apax)
Using cached ase-3.23.0-py3-none-any.whl.metadata (3.8 kB)
Collecting clu<0.0.8,>=0.0.7 (from apax)
Using cached clu-0.0.7-py3-none-any.whl.metadata (2.0 kB)
Collecting e3x<2.0.0,>=1.0.2 (from apax)
Using cached e3x-1.0.2-py3-none-any.whl.metadata (3.6 kB)
Collecting einops<0.7.0,>=0.6.0 (from apax)
Using cached einops-0.6.1-py3-none-any.whl.metadata (12 kB)
Collecting flax==0.8.4 (from apax)
Using cached flax-0.8.4-py3-none-any.whl.metadata (10 kB)
Requirement already satisfied: jax<0.5.0,>=0.4.25 in c:\users\administrator\appdata\local\programs\python\python313\lib\site-packages (from apax) (0.4.37)
Collecting lazy-loader<0.5,>=0.4 (from apax)
Using cached lazy_loader-0.4-py3-none-any.whl.metadata (7.6 kB)
Collecting numpy<2.0,>=1.23 (from apax)
Using cached numpy-1.26.4.tar.gz (15.8 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing metadata (pyproject.toml) ... error
error: subprocess-exited-with-error
× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [21 lines of output]
+ C:\Users\Administrator\AppData\Local\Programs\Python\Python313\python.exe C:\Users\Administrator\AppData\Local\Temp\pip-install-xsdvulod\numpy_4cff7dcee46b4f8d9a75f02dd9f6153e\vendored-meson\meson\meson.py setup C:\Users\Administrator\AppData\Local\Temp\pip-install-xsdvulod\numpy_4cff7dcee46b4f8d9a75f02dd9f6153e C:\Users\Administrator\AppData\Local\Temp\pip-install-xsdvulod\numpy_4cff7dcee46b4f8d9a75f02dd9f6153e.mesonpy-4wcdwwhw -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md --native-file=C:\Users\Administrator\AppData\Local\Temp\pip-install-xsdvulod\numpy_4cff7dcee46b4f8d9a75f02dd9f6153e.mesonpy-4wcdwwhw\meson-python-native-file.ini
The Meson build system
Version: 1.2.99
Source dir: C:\Users\Administrator\AppData\Local\Temp\pip-install-xsdvulod\numpy_4cff7dcee46b4f8d9a75f02dd9f6153e
Build dir: C:\Users\Administrator\AppData\Local\Temp\pip-install-xsdvulod\numpy_4cff7dcee46b4f8d9a75f02dd9f6153e.mesonpy-4wcdwwhw
Build type: native build
Project name: NumPy
Project version: 1.26.4
WARNING: Failed to activate VS environment: Could not parse vswhere.exe output
  ..\meson.build:1:0: ERROR: Unknown compiler(s): [['icl'], ['cl'], ['cc'], ['gcc'], ['clang'], ['clang-cl'], ['pgcc']]      The following exception(s) were encountered:
  Running `icl ""` gave "[WinError 2] 系统找不到指定的文件。"
  Running `cl /?` gave "[WinError 2] 系统找不到指定的文件。"
  Running `cc --version` gave "[WinError 2] 系统找不到指定的文件。"
  Running `gcc --version` gave "[WinError 2] 系统找不到指定的文件。"
  Running `clang --version` gave "[WinError 2] 系统找不到指定的文件。"
  Running `clang-cl /?` gave "[WinError 2] 系统找不到指定的文件。"
  Running `pgcc --version` gave "[WinError 2] 系统找不到指定的文件。"

  A full log can be found at C:\Users\Administrator\AppData\Local\Temp\pip-install-xsdvulod\numpy_4cff7dcee46b4f8d9a75f02dd9f6153e\.mesonpy-4wcdwwhw\meson-logs\meson-log.txt
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.

Hi, thank you for reaching out.
It seems that the problem arises due to python not finding a C compiler. I would recommend making sure that you have something like gcc installed and available in your path.
That said, we have no experience with installing Apax on Windows as Jax does not offer GPU support for that plattform.

The compiler error has been resolved, but a new error has emerged.

C:\Users\Administrator>pip install git+https://github.com/apax-hub/apax.git
Collecting git+https://github.com/apax-hub/apax.git
Cloning https://github.com/apax-hub/apax.git to c:\users\administrator\appdata\local\temp\pip-req-build-4csqz6ih
Running command git clone --filter=blob:none --quiet https://github.com/apax-hub/apax.git 'C:\Users\Administrator\AppData\Local\Temp\pip-req-build-4csqz6ih'
Resolved https://github.com/apax-hub/apax.git to commit c760b198aa5b9f932261afe344b8af683ae80d92
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Collecting ase<4.0.0,>=3.22.1 (from apax==0.9.1)
Using cached ase-3.23.0-py3-none-any.whl.metadata (3.8 kB)
Collecting clu<0.0.8,>=0.0.7 (from apax==0.9.1)
Using cached clu-0.0.7-py3-none-any.whl.metadata (2.0 kB)
Collecting e3x<2.0.0,>=1.0.2 (from apax==0.9.1)
Using cached e3x-1.0.2-py3-none-any.whl.metadata (3.6 kB)
Collecting einops<0.7.0,>=0.6.0 (from apax==0.9.1)
Using cached einops-0.6.1-py3-none-any.whl.metadata (12 kB)
Collecting flax==0.8.4 (from apax==0.9.1)
Using cached flax-0.8.4-py3-none-any.whl.metadata (10 kB)
Requirement already satisfied: jax<0.5.0,>=0.4.25 in c:\users\administrator\appdata\local\programs\python\python313\lib\site-packages (from apax==0.9.1) (0.4.37)
Collecting lazy-loader<0.5,>=0.4 (from apax==0.9.1)
Using cached lazy_loader-0.4-py3-none-any.whl.metadata (7.6 kB)
Collecting numpy<2.0,>=1.23 (from apax==0.9.1)
Using cached numpy-1.26.4.tar.gz (15.8 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing metadata (pyproject.toml) ... done
Collecting optax<0.2.0,>=0.1.3 (from apax==0.9.1)
Using cached optax-0.1.9-py3-none-any.whl.metadata (6.7 kB)
Collecting orbax-checkpoint==0.5.16 (from apax==0.9.1)
Using cached orbax_checkpoint-0.5.16-py3-none-any.whl.metadata (1.8 kB)
Collecting pydantic<3.0.0,>=2.3.0 (from apax==0.9.1)
Using cached pydantic-2.10.3-py3-none-any.whl.metadata (172 kB)
INFO: pip is looking at multiple versions of apax to determine which version is compatible with other requirements. This could take a while.
ERROR: Ignored the following versions that require a different python version: 1.21.2 Requires-Python >=3.7,<3.11; 1.21.3 Requires-Python >=3.7,<3.11; 1.21.4 Requires-Python >=3.7,<3.11; 1.21.5 Requires-Python >=3.7,<3.11; 1.21.6 Requires-Python >=3.7,<3.11; 1.26.0 Requires-Python <3.13,>=3.9; 1.26.1 Requires-Python <3.13,>=3.9
ERROR: Could not find a version that satisfies the requirement tensorflow<3.0.0,>=2.12.0 (from apax) (from versions: none)
ERROR: No matching distribution found for tensorflow<3.0.0,>=2.12.0


exit with exit code 1 on aerender failure for CLI

I have a use case to know whether a job has failed or not based on the exit code of nexrender. It's pretty standard for a CLI to return an error code of non-zero for a failure.

Totally agree! Thanks!


Cloud Run does not load .env variables

I spend the last couple of days trying to find what I have done wrong but I am still not able to figure out because I am able to run the app locally using flask run and also using Docker using docker-compose up --build.
My issue is my Cloud Run deployment is successful but Service Unavailable when I am clicking on the URL. I checked the logs and seems my environment variables are not correctly loaded:
line 7, in <module> from web_messaging.blueprints.user import user File
"/web_messaging/web_messaging/blueprints/user/__init__.py", line 1, in <module> from
web_messaging.blueprints.user.views import user File
"/web_messaging/web_messaging/blueprints/user/views.py", line 3, in <module> from
web_messaging.extensions import mongo, login_manager, c, bc File
"/web_messaging/web_messaging/extensions.py", line 18, in <module> twilio_client = Client(TWILIO_SID,
TWILIO_TOKEN) File "/usr/local/lib/python3.9/site-packages/twilio/rest/__init__.py", line 54, in __init__
raise TwilioException("Credentials are required to create a TwilioClient")
twilio.base.exceptions.TwilioException: Credentials are required to create a TwilioClient

I have a config/.env file and a config/settings.py. I am loading the env variables from .env using  load_dotenv() on my config/settings.py. I decided to add some print and try/expect statements in my config/settings.py to see the value of variables.
settings.py
import os
from dotenv import load_dotenv
BASEDIR = os.path.abspath(os.path.dirname(__file__))

try:
    load_dotenv(os.path.join(BASEDIR, '.env'))
    print("OK")
    print(BASEDIR)
except Exception as e:
    print(str(e))

# Mongo Database
MONGO_URI = os.getenv('MONGO_URI')
TWILIO_SID = os.getenv('TWILIO_SID')
TWILIO_TOKEN = os.getenv('TWILIO_TOKEN')
print(MONGO_URI)
print(TWILIO_SID)

When I am running with flask run, docker-compose or on cloud-run:

The BASEDIR is /web_messaging/config
There is no exception during the load_dotenv() call

However, there is one major difference, the value of MONGO_URI, TWILIO_SID and all of my environment are correct on flask run and docker-compose but not on the Cloud Run logs. On Cloud Run, those variables are equal to None.
When I don't use a .env and directly put the value of my variables inside /web_messaging/config, there is no issues. I also tried to moved .env outside of the config file and in few other locations but I still got the same issue.
.
├── requirements.txt
├── Dockerfile
├── Docker-compose.yml
├── config
│   ├── .env
│   ├── settings.py
│   ├── gunicorn.py
│   └── __init__.py
├── web_messaging
│   ├── app.py      # where I am calling create_app() - factory pattern
│   ├── blueprints
│   ├── static
│   └── ...
└── ...

Dockerfile
FROM python:3.9-slim

ENV INSTALL_PATH /web_messaging
RUN mkdir -p $INSTALL_PATH

WORKDIR $INSTALL_PATH

COPY requirements.txt requirements.txt
RUN pip install -r requirements.txt

COPY . .

CMD gunicorn -b <IP_ADDRESS>:8080 --access-logfile - "web_messaging.app:create_app()"

docker-compose.yml
version: '2'

services:
  website:
    build: .
    command: >
      gunicorn -b <IP_ADDRESS>:8080
        --access-logfile -
        --reload
        "web_messaging.app:create_app()"
    environment:
      PYTHONUNBUFFERED: 'true'
    volumes:
      - '.:/web_messaging'
    ports:
      - '8080:8080'

config/.env
COMPOSE_PROJECT_NAME=web_messaging
FLASK_SECRET='xxx'
MONGO_URI="mongodb+srv://xxx"
MONGO_DB='xxx'
TWILIO_SID='xxx'
TWILIO_TOKEN='xxx'

config/settings.py
import os
from dotenv import load_dotenv
BASEDIR = os.path.abspath(os.path.dirname(__file__))

load_dotenv(os.path.join(BASEDIR, '.env'))

DEBUG = True
PYTHONDONTWRITEBYTECODE=1
#SERVER_NAME = '<IP_ADDRESS>:5000'

# Mongo Database
MONGO_DBNAME = os.getenv('MONGO_DB')
MONGO_URI = os.getenv('MONGO_URI')

# Twilio API
FLASK_SECRET = os.getenv('FLASK_SECRET')
TWILIO_SID = os.getenv('TWILIO_SID')
TWILIO_TOKEN = os.getenv('TWILIO_TOKEN')

config/gunicorn.py
bind = '<IP_ADDRESS>:8080'
accesslog = '-'
access_log_format = '%(h)s %(l)s %(u)s %(t)s "%(r)s" %(s)s %(b)s "%(f)s" "%(a)s" in %(D)sµs'

Hi @Pierre-Alexandre35, thank you for the detailed bug report. Unfortunately, this issue tracker has limited visibility and scope - basically, it's just for reporting issues with the samples contained here and is only watched by the folks who work on these samples.
In the future, you're likely to get a faster response on StackOverflow's "google-cloud-run" tag.
In looking at your issue, it looks like your .env file may not be inside the the application code running on Cloud Run. A likely reason for this is the following combination of behaviors:

The .env file is configured in your .gitignore
The application does not have a .gcloudignore

When these two problems happen at the same time, gcloud commands to build your application into a container do not upload any of the files covered in your .gitignore. Many dotenv implementations silently fallback to default values if the .env file is missing.
If this is your problem, creating an empty .gcloudignore file will fix it. Here's a sample gcloudignore file from the helloworld-shell sample in this repo:
https://github.com/GoogleCloudPlatform/cloud-run-samples/blob/836133e0cbf9ac6cb0c1c71ef2b5a68462771ab1/helloworld-shell/.gcloudignore#L1-L12
If this does not help, please comment back here with a link to your StackOverflow question!


Adding effects to cards of "Open Source Programs we are a part of"

Right now, cards here are looking really great but I think they would look better if we will make them to take less space.
I can enhance the hover effects like when the person will hover onto the card it will increase it's size and will show the information and read more button while as normally the cards will only show Event logo and Event name.
If the mentors and project managers are ok with doing so I would like to work on this issue.
Let me know @anushbhatia

Right now, cards here are looking really great but I think they would look better if we will make them to take less space.
I can enhance the hover effects like when the person will hover onto the card it will increase it's size and will show the information and read more button while as normally the cards will only show Event logo and Event name.
If the mentors and project managers are ok with doing so I would like to work on this issue.
Let me know @anushbhatia

Sure @ankitaugale23 . Please go ahead and give a PR. We will review it accordingly 😊

Right now, cards here are looking really great but I think they would look better if we will make them to take less space.
I can enhance the hover effects like when the person will hover onto the card it will increase it's size and will show the information and read more button while as normally the cards will only show Event logo and Event name.
If the mentors and project managers are ok with doing so I would like to work on this issue.
Let me know @anushbhatia

Assigned for 3 days. If required we can extend the deadline for the initial PR

I would like to work on this issue. Pease assign me this

Sure Thanks for assigning it to me. I will complete my task and make a PR by 16th march. Is it okay? @smaranjitghose

Heyy..I can fix this issue. As a beginner I am figuring out. Please let me know if I can contribute to it or it is closed?

Sure @sharvariiii

Sure @sharvariiii

Assigned for 3 days, after which the issue shall be closed

Can you please guide me what changes are required from my side because "the person will hover onto the card it will increase it's size and will show the information and read more button " this feature is already there. Also #758 has assigned to someone else so that person is working on that issue which is similar to this one. Will be waiting for your response.

This was supposed to be a UI enhancement issue where you were expected to suggest improvements. Otherwise, the maintainers themselves would have stated the requirements