ValueError on specifying low level graph source

Got unexpected ValueError on attempt to specify low level graph source,
  File "/work/app/graph/data.py", line 30, in <module>
    token_access_time_src = sa.FieldsQuery(DB_ENGINE_KEY, token_access_time)
  File "/usr/local/lib/python3.6/dist-packages/hiku/sources/sqlalchemy.py", line 24, in __init__
    self.primary_key, = from_clause.primary_key
ValueError: not enough values to unpack (expected 1, got 0)

Models defined as,
import sqlalchemy as sa

from sqlalchemy.dialects.postgresql import UUID

token = sa.Table(
    'tokens',
    metadata,

    sa.Column('id', UUID(), primary_key=True),
    ...
)

token_access_time = sa.Table(
    'token_access_times',
    metadata,

    sa.Column(
        'token',
        None,
        sa.ForeignKey('tokens.token', ondelete='CASCADE'),
        nullable=False,
        unique=True),
    ...
)

Graph source definition,
from hiku.sources import aiopg as sa

token_access_time_src = sa.FieldsQuery(DB_ENGINE_KEY, token_access_time)
token_src = sa.FieldsQuery(DB_ENGINE_KEY, token)

Low level graph nodes declared as,
from hiku.graph import Node
from hiku.sources import aiopg as sa

...

    Node('token', [
        sa.Field('token', token_src),
        ...
    ]),

    Node('token_access_time', [
        sa.Field('token', token_access_time_src),
        ...
    ]),

Python version: 3.6.1
Hiku version: 0.3.6.post1
SQLAlchemy version: 1.1.9
aiopg version: 0.13.0

Sorry for late response. Seems like token_access_times table doesn't have a primary key. Is this true? As I see, token_access_times.token column looks like primary key, but was not declared this way. It is still possible to use this table without changes (if it was defined this way intentionally) by explicitly specifying primary_key optional argument in FieldsQuery.__init__ method:
token_access_time_src = sa.FieldsQuery(DB_ENGINE_KEY, token_access_time,
                                       primary_key=token_access_time.c.token)

@vmagamedov
Can confirm. All works as expected after specifying primary_key=.... My bad for not looking deeply in docs/code. Thanks for pointing out.
Closing as invalid.


sell leather to player

What if we rename, and retexture horse amour to scrap. Then the players can get scrap which they need to break down and, with the current recipes, this will give them leather.

Not sure what you mean by scrap. But I prefer to sell hourses to players and let them do hourse farms

Though i feel like people won't like killing hourses

No; not killing horses. But companies send/sell 'scrap' (retextured horse amour items) and the player can then grind them into useful items. The recipe is already in the game, so a texture swap would allow an extra process as you'd need a factory to break up the 'scrap' given to the player (horse amour items, not horses themselves).
So companies given horse amour to players -> players take it and use it in a create's crushing wheels -> chance to get leather, white/yellow/orange ingots, and string (string is needed for conductor caps after all; so then you can make train timetables)

Yea I know you meant hours armor, was talking about actual horses because it's more mechanically interesting to farm

I like the scrap idea, but we can add it as new item, no need to reporpus horse armor

In general we can have companies send you a few types of scrap for recycling, that will be cool


JRE_HOME

I ran into an issue which lead to the need of setting JRE_HOME, would it be desirable to set JRE_HOME within this cookbook, perhaps as a recipe?

I think this is fine to be left to a wrapper cookbook - I dont find it a common use case software needs JRE_HOME.

@erichelgeson thanks for the feedback.
Anything that needs libs not to be modified or increased security properties. Here's our use case, we're using bouncycastle for pgp (de/en)cryption, including it as a maven dependency modifies the signature of the jar and renders it useless. Leading us to need JRE_HOME set, and the original jar to be located in JRE_HOME/lib.


Release <IP_ADDRESS> has incorrect nuspec configuration

ISSUE TITLE:
Release <IP_ADDRESS> has incorrect nuspec configuration
ISSUE DESCRIPTION:
I cant see where your deployment scripts are but I believe there is an issue when generating a nu-spec file for release. In release <IP_ADDRESS> the nu-spec was:
  <metadata>
    <id>StorageDsc</id>
    <version><IP_ADDRESS></version>

However in release <IP_ADDRESS> it is
  <metadata>
    <id>StorageDsc</id>
    <version>4.2.0</version>

Notice the missing ".0"
The result of this is that the module is installed to C:\Program Files\WindowsPowerShell\Modules\StorageDSC\4.2.0 but the psd1 file has "<IP_ADDRESS>" specified and thus makes it an invalid module. Running Get-Module -ListAvailable fails to return <IP_ADDRESS>.
This should be a pretty simple fix. I'm happy to have a look if you can point me in the right direction? I don't see any scripts that deal with packaging this module
Details of the scenario you tried and the problem that is occurring
Tried installing this module from our Artifactory instance using Install-Module. The command completes successfully but the resultant module is not valid and cannot be imported.
Trying to import the module via its psd1 yields the underlying reason
PS D:\Code> Import-Module 'C:\Program Files\WindowsPowerShell\Modules\StorageDsc\4.2.0\Stora
geDsc.psd1'
Import-Module : The ModuleVersion key in module manifest 'C:\Program
Files\WindowsPowerShell\Modules\StorageDsc\4.2.0\StorageDsc.psd1' specifies module version '<IP_ADDRESS>'
which does not match its version folder name at 'C:\Program
Files\WindowsPowerShell\Modules\StorageDsc\4.2.0'. Change the value of the ModuleVersion key to match
the version folder name.
At line:1 char:1
+ Import-Module 'C:\Program Files\WindowsPowerShell\Modules\StorageDsc\ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (C:\Program File...StorageDsc.psd1:String) [Import-Module
   ], InvalidOperationException
    + FullyQualifiedErrorId : Modules_InvalidModuleManifestVersion,Microsoft.PowerShell.Commands.ImportM
   oduleCommand

Verbose logs showing the problem
Suggested solution to the issue
Update the nu-spec to have the full 4 part version number
The operating system the target node is running
OsName               : Microsoft Windows 10 Enterprise
OsOperatingSystemSKU : EnterpriseEdition
OsArchitecture       : 64-bit
WindowsVersion       : 1803
WindowsBuildLabEx    : 17134.1.amd64fre.rs4_release.180410-1804
OsLanguage           : en-GB
OsMuiLanguages       : {en-GB}

Version and build of PowerShell the target node is running
Name                           Value
----                           -----
PSVersion                      5.1.17134.112
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17134.112
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Version of the DSC module that was used ('dev' if using current dev branch)
N/A

Hi @mrhockeymonkey - Leaving off the trailing 0 in the nuspec is actually something Nuget does rather than something we do during the publish process. However, this shouldn't cause a problem when using Install-Module StorageDsc from the PSGallery.
I gave it a try myself and it all looks OK:

How did you install the module?

Indeed you are correct it looks like I don't have the issue when I try from PSGallery on my home laptop. At work we use Artifactory to cache PSGallery modules for internal use (we have no direct internet access). Artifactory is the equivalent of a standard NuGet repository.
I'll test this by spinnig up a separate NuGet server, not Artifactory, and see what happens. There is a chance it's Artifactory at fault.

Hi @mrhockeymonkey - I use Sonatype Nexus at work which is similar to JFrog Artifactory and we use it to proxy the modules. However, we're using it as a "proxy" rather than a mirror. You could use PSGallery on a machine connected to the internet to pull down the modules using Install-Module and then bring the files into your internal network manually and then use the Publish-Module command to publish them back up to Artifactory.

Hi @PlagueHO feel free to close this (apologies for not replying sooner). As mentioned its a weird quirk with artifactory, turns out this only happens when I install directly from artifactory's cache and not when I use it as a proxy. The only reason I was doing that at all was because i had no way to specify the version I wanted explicitly in Ansible but that is getting solved in https://github.com/ansible/ansible/pull/46516 so no need for this issue anymore.
thanks for your feedback.

I just ran into this same issue with ComputerManagementDsc and xWebAdministration, installing packages manually cached from PSGallery in a local file share as a repository. The nuspec has the truncated version number, so the modules install to the wrong folder name.

Leaving off the trailing 0 in the nuspec is actually something Nuget does rather than something we do during the publish process.

Some other Microsoft modules and third-party modules don't seem to have this issue. Are there still no plans to fix it?

Looks like there is a separate issue for this at the PSGallery level. More info is at https://github.com/PowerShell/PowerShellGallery/issues/55

Hi @psychonic - this has been a long time problem with PowerShellGet - but more correctly an annoying behavior of Nuget itself. It will affect all DSC Resource modules published to the PSGallery unfortunately.


doc: Add api curl examples

Summary

Add some more curl http examples
Checklist

[x] Scope: The referenced issue is addressed, there are no unrelated changes.
[x] Run Locally: Verified that the docs build using make server
[ ] New Features Marked: Documentation for new features is marked using the new-in-version shortcode, according to the guidelines in README.md.
[x] Style Guidelines: Documentation obeys style guidelines in README.md.
[ ] Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
[x] Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.

I really don't think the index page of our API reference should document how you can create end devices with cURL, which we don't want users to do in the first place

I'm split here. It's a robust example, and even if we don't recommend that people do it, it provides a lot of insight about how to interact with the HTTP API. @johanstokking  ?

Yes, I do think it makes sense to document device provisioning the HTTP way, i.e. with cURL examples.

I'm not against documenting it. I just think it shouldn't be on the index page of our API reference


Icons are not aligned.

Icon not aligned.

-Verified this issue on staging app version 1.4.0(182)


[SITE, SPONSOR] SITE should notify SPONSOR when a new shipment is received and scanned

After implementing #333, SITE should send a message to SPONSOR that will contain the shipmentId and the new status.(the shipment status)
Sponsor should insert a notification into his system and mount the sReadKeySSI

Started working on it

Created PR for this


How to check status online/offline for opponent

Hi, @meosieudang
Get user's last activity status - https://developers.connectycube.com/js/messaging?id=get-last-activity
You will get 0 seconds if user is online.


Function Score Query Usage - Object Initializer syntax does not compile

The object initializer syntax in the docs does not compile. There is no generic Field<Project> property. Either the generic property is missing, the documentation is incorrect, or it's just not apparent where Field<obj> is coming from.

If you click the "edit" button on any of the docs, it will link to the underlying asciidoc file from which it was generated:

This in turn will link back to the source code that generated the asciidoc:

Field<T>() is using a static import; the full name is Nest.Infer.Field<T>():
https://github.com/elastic/elasticsearch-net/blob/b0a8d867cd75b6e617f40d759986ed623c4b21eb/src/Tests/Tests/QueryDsl/Compound/FunctionScore/FunctionScoreQueryUsageTests.cs#L8
This is called out in the Field Inference documentation, but I think it would be noisy to call it out everywhere it's used.


Whitespaces are not being rendered

Hey tomolt, thanks for the great library. I'm encountering a problem that whitespaces are not being rendered for some reason. Did I miss something? I used your stress.c file as template.
Here's a snippet of my code. letterImagePtr is just a struct that groups several image related information.
SFT sft = {0};
SFT_Glyph gid;
SFT_GMetrics *metricsPtr = &(letterImagePtr->metrics);
SFT_Image *imagePtr = &(letterImagePtr->image);

sft.font = font;
sft.xScale = size;
sft.yScale = size;
sft.flags = SFT_DOWNWARD_Y;

if (sft_lookup(&sft, c, &gid) < 0)
{
    /* Lookup failed. */
}
else if (sft_gmetrics(&sft, gid, metricsPtr) < 0)
{
    /* Metrics evaluation failed. */
}
else
{
    imagePtr->width  = metricsPtr->minWidth;
    imagePtr->height = metricsPtr->minHeight;
    imagePtr->pixels = malloc((size_t)imagePtr->width * (size_t)imagePtr->height);
    printf("\n-------> Char: '%c', width: %d\n", (const char)c, imagePtr->width);
    if (imagePtr->pixels)
    {
        sft_render(&sft, gid, *imagePtr);
    }
    else
    {
        /* Pixel reservation failed. */
    }
}

Here's the Output:

Thanks and BR
monstermichl

Hi,
The width of a glyph refers to how to big of a canvas/image is needed to draw the glyph into.
As there is nothing to be drawn for white space characters, it makes sense that the width ends up being zero.
What's more important is the glyphs "advanceWidth" attribute, which tells you how far you should move
your 'pen' to the right before drawing the next glyph.
I tried documenting what each of these attributes does in the man page.
Also, I admit that the stress program is really not a great reference, since it doesn't show you how to actually put
text on the screen (it is meant for performance profiling).
If you're vaguely familiar with X11 you might find the sftdemo program useful.
Alternatively, someone else wrote another sample program,
which writes out PGM images (instead of relying on a specific graphics API).
I have not looked closely at that one so far, but it is probably a good reference.
I hope this helps!

Great, thank you. I must have missed that :)


target: mbedos5: release jerry_value_t

JerryScript-DCO-1.0-Signed-off-by: Marko Fabo<EMAIL_ADDRESS>

Please, give a more descriptive commit message:

the patch clearly does not deal with releasing values only (it seems that there was also a bug in arg checks), and
the commit message does not tell why the releasing of f is necessary (e.g., what issue rose from it not being released).

If you do not start the eventloop in mbed, just call the jerry_cleanup function at the end of the application, you got this error message:
ICE: Assertion 'ECMA_STRING_IS_REF_EQUALS_TO_ONE (string_p)' failed at ../../jerry-core/ecma/base/ecma-literal-storage.c(ecma_free_string_l. Error: ERR_FAILED_INTERNAL_ASSERTION
@akosthekiss I am sorry about the empty message, but I thought it is a simple bug, and my PR is correct and clear solution for that. Probably i was wrong, and there is an other way to fix this error.
I'm working on the solution, and i will update the PR soon.

@akosthekiss @LaszloLango
updated

@akosthekiss
If you delete the jerry_release_value from dropCallback, you get the same error.
My new update possibly make the code more clear, please check.


Add support for vite builds

The Docker image build fails with this error:
Could not read package.json: Error: ENOENT: no such file or directory, open '/var/www/html/package.json'

After adding NODE_ENV=production, mine fails because it's not able to find vite, though I don't get an error about package.json.  Do you have a package.json in your Laravel project?
This works for me:

git clone https://github.com/exaco/laravel-octane-dockerfile.git
cd laravel-octane-dockerfile.git
git checkout 74f1b02
(Remove the two NODE_ENV=production statements from the frontend build)
cd ../
laravel new test-app
cd test-app
cp -r ../laravel-octane-dockerfile/Dockerfile ../laravel-octane-dockerfile/deployment ./
docker build -t test-exaco . --no-cache

tbh, I don't set NODE_ENV=production when building.  Since the intermediate build is not included in the final image and we get the prod build in public, is it necessary to include those statements?

Thank you for your assistance! I have attempted several times to run the code on my machine and via GitHub actions, but I kept encountering the same error. I want to clarify that I have already made sure that the package.json file exists. It's possible that you are not experiencing this error because in the particular commit you referenced, you are checking for the existence of package.json before running the npm commands.
Nevertheless, I will give it another try and see if I can resolve the issue.
As a best practice for Dockerizing Node apps, I had previously set NODE_ENV=production, but I now realize that it may not be necessary in this case since the bundlers are usually smart enough to handle the build process efficiently.

np!  Glad to try and help.  This package is awesome.  Yes, I was not checking for package.json in my PR, which should be done.  Assuming everyone has one isn't safe, even if it comes standard today with a laravel new.
I can adjust my PR and resubmit with the check for package.json and also NODE_ENV removed if you'd like?

I appreciate it. Feel free to adjust your PR and resubmit it with the necessary changes.


Remove unneeded <regex> includes

We (ClickHouse) disallow usage of the <regex> header in our code (https://github.com/ClickHouse/ClickHouse/pull/58681) because the standard library's regexp implementation is generally perceived as slow. Whenever we upgrade the Azure submodule in ClickHouse, we manually remove all includes of <regex>, and (if needed) rewrite std regular expressions to re2 regular expressions. In the case of Azure, <regexp> is included but the functionality is not used, so we can get away with simply removing the includes.
We are not proposing that Azure should require a similar rule as ClickHouse, please consider this PR as a mere header cleanup.

Thank you for making this contribution. As part of some recent work we no longer use regex and the headers can be safely removed.

That is almost true. I had to revert a  removal in one specific place because tests actually still use them. https://github.com/Azure/azure-sdk-for-cpp/pull/5851/commits/01e4d789a32aff02587f5371e3d1d4bcbba57c66
(however, this doesn't matter for us as we don't compile the tests)

Thank you for making this contribution. As part of some recent work we no longer use regex and the headers can be safely removed.

That is almost true. I had to revert a removal in one specific place because tests actually still use them. 01e4d78
(however, this doesn't matter for us as we don't compile the tests)

That's correct, I should have been a bit more specific. Where you removed the header it's no longer used. We do still use regex for a part of the test proxy infrastructure. :)


Error in ClipperPaths with undefined object for points

https://ptb.discord.com/channels/915186263609454632/1137543980293292083/1167171927824146534

Should be fixed in upcoming v0.6.0


Support Multiple Kubernetes Syncs

Overview
The OpenFeature Operator (OFO) supports Custom Resources (CR) for FlagD flag definitions. In some situations, it may be beneficial to split the flag definitions between multiple CRs. This can be used to overcome limitations in the max default size of a CR in Kubernetes or to ease configuration management.
Proposal
Allow a user to define multiple openfeature.dev/featureflagconfiguration annotations that are applied to FlagD as arguments. These arguments are applied in the order they were defined, which determines the merge strategy in case of a collision.
Requirements

[ ] Update the OFO to support multiple openfeature.dev/featureflagconfiguration` annotations
[ ] open-feature/flagd#217

Resolve: https://github.com/open-feature/open-feature-operator/issues/17


[Feature Request]: Add forget password

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
To allow user to reset his password if he/she forgets his password
Record

[X] I agree to follow this project's Code of Conduct
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

@mehul-m-prajapati how  is ur progress??

@Sibam-Paul : suggest me which approach should I follow..

Sending otp
Sending reset link in email
Adding security questions in user profile

1

Services like SendGrid, Mailgun, or Amazon SES allow you to send emails without needing to expose your email credentials.
SendGrid:

Sign up for a SendGrid account.
Generate an API key in the SendGrid dashboard.
Use the API key in your application instead of your email/password.
Example with SendGrid:

const sgMail = require('@sendgrid/mail');
sgMail.setApiKey(process.env.SENDGRID_API_KEY);

const sendEmail = async (to, subject, text) => {
    const msg = {
        to,
        from<EMAIL_ADDRESS>        subject,
        text,
    };
    await sgMail.send(msg);
};

@mehul-m-prajapati It's goin to take charge no.
And integrate the API key need to talk to @kartikayasija about the API key

@Sibam-Paul : Closing issue because of long wait times.

@mehul-m-prajapati Open it he was busy so couldn't reply


Allow posting Pictures with DRF

In the short documentation it mentions this:

We do ship with a read-only PictureField that can be used to include all available picture sizes in a DRF serializer.

So there is currently no way to create a Picture through a DRF serializer?
Or how would you go about doing that?

I think I got it.
I created a new serializer which uses the pictures.models.PictureField instead of pictures.contrib.rest_framework.PictureField


Only .gba games in file browser

Windows browser will only display .gba games in folder to avoid confusion.

I'll merge this to 1.0 and gh-pages tonight.


Improve password manager experience

c.f. https://web.dev/change-password-url/

Add "well-known" URL for changing passwords
Add autocomplete attributes to help password managers understand what
fields are for

Review app deployed to https://teaching-vacancies-review-pr-3077.london.cloudapps.digital


IIS error with Microsoft.Skype.Bots.Media

Hello!
I want  to deploy RealTimeMediaCalling bot application for IIS
By default, I created projects (Bot Application, MVC, WebApi, etc.)
All works good.
After adding Microsoft.Skype.Bots.Media to the project, I see an error.
https://www.screencast.com/t/GYhpa10jJ7a
"Could not load file or assembly 'Microsoft.Rtc.Internal.Media' or one of its dependencies. An attempt was made to load a program with an incorrect format."
I tried:

Compiled the project for the platforms AnyCPU, x64, x86
Changed "Enable 32-bit Application to True" in ApplicationPool(IIS).
Installed the latest version VCRedist x86 and x64
Nothing helps...

If I delete this library, then again the project works well.
Where my mistake? Can you please help.
PS:I have VS2015(14.0.25421.03 Update 3)

we support only 64 bit mode.

I compiled for x64, but the problem remained...
The problem is repeated after adding Microsoft.Skype.Bots.Media
https://www.screencast.com/t/PRWcTGqj

Hi, can anyone please advice how solve this issue? I can confirm ASP.Net application compilation fails even for x64... (tested on VS2017, latest update included).

I am facing the same issue. I can compile the code but getting error while running the application.
Configuration : X64, VS2017, Latest Update.   No luck.

short answer:
Modify the web.config file under <system.web> tag add:
<hostingEnvironment shadowCopyBinAssemblies="false"/>

Rebuild
for more info see my answer on SO:
https://stackoverflow.com/a/49425225/3263555

Same issue here... x64, VS2017

Same issue here as well. x64, x86, Any CPU... all give the same error when I run the program. VS2019


Predictive text in Android interferes with this widget

When predictive text is activated in Android, it seems formatCardNumber, formatCardExpiry and formatCardCVC are not called, or not working properly.
It happens both with card.js and card.jquery.js
Customers would be unable to proceed with the purchase: expiry date cannot be entered properly. The slash, which should be added automatically, does not appear. And it cannot be added by hand, apparently. Odd.
Other than that: fantastic tool :)
Hope someone has a hint on how to fix this, or a workaround, as I'm rather unfamiliar with Android specifics.

I'm going to close this in favor of #199. If you think they are two separate issues, please reopen!


AKS distro is for Kubernetes only

What this PR does / why we need it: Set default distro value to AKS (for VHD delivery) only if Kubernetes
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
If applicable:

[ ] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

AKS distro is for Kubernetes only

/lgtm

/lgtm


Support for Receivers

This PR adds support for receivers to the your library. This may need a bit more testing before its ready to be added. Is there anything you want me to add to this PR before accepting it?

Thanks for your work on this. I fixed some code formatting and tweaked a few things.
You can try the dev branch with composer require tuurbo/spreedly:dev-receivers

My initial tests against a test account seem to be working well for all the main api calls. I plan to do a bit more testing yet.

We did more testing on it and as far as I am aware, everything is working fine. Let me know when you merge this into master and release it.

I did find a slight error with the update method, was due to an incorrect conversion from XML to JSON format.

I pushed the fix to dev-receivers. Same fix was also applied to the create method. Also, added more tests.

Should the deliver method be left as is? Don't completely understand receivers, but I'm assuming the body param could be anything, so a string value would probably work best?


Initialize a SimDem Project through simdem init

To make it easier to get started with a new project, given the user is in an empty directory, they can run
simdem init

This initializes a basic SimDem project structure, including environment variable files. Optionally, this can work similar to npm init, where there is an interactive process that customizes the project structure.

This is a good idea.


Get status in webhook payload

Hello,
Thank you @adamcooke for your work on Postal!
It would be nice to get the status/reason of the message bounces directly in the payload JSON or, at least, a copy of the plain text message (so we can parse it).
Without this, we have to go through the platform to understand what happened (overquota, unknown user, ...)
Thank you again,
Julien

Are you talking about the MessageBounced event?

Yes, absolutely.

In the case of a bounce message, we don't actually know the reason. This is contained within the bounce message but we don't parse this to try to find it. You would need to implement your own logic to read the message and determine it's purpose.
You can use the message API to obtain the full content of the message from the Postal API whenever you receive it. https://atech.github.io/postal-api/controllers/messages/message.html


git submodule

@hectorsector Would it be possible to cover the git submodule? 🙏

@QikeLi I'll pass it along for Eric to cover near the end, but it's not usually in the scope of our class, so it'll be superficial. What are you trying to do? I may be able to link you to some resources.

Thank you, Hector! I would like to be able to manage some sub-projects under a big project.  🙇

This cheatsheet may be helpful!


Generated by :no_entry_sign: Danger


Sync from CMSMELA

The changes to makefile were not accidental

I also don't agree we should use NNPDF's location. If the files are the same, providing a copy from us is more manageable than keeping track of NNPDF location changes. We have been there before and received complaints if you recall.


Add integration test for PRs

Too easy to break the build when merging fixes, e.g. #10 -> #11

Currently, you have tiny inputs for the flake, and it's good that someone adds your flake as an input. What do you think about adding some other dependencies but only for CI?
Seems like they are unnecessary for the flake, so we shouldn't include any additional dependencies to the main flake. Should we create another flake only for CI? Or just use CI without nix magic (formatting, testing and so on)?

@selfuryon I don't have strong feelings here, the bundle itself is comparatively large (50MB+) that I don't feel bad adding a few kb of dependencies.
A separate flake in a subdirectory just for testing could work too though, if it's convenient. :)
Overall, any amount of integration testing is better than nothing, so any approach is appreciated!

Got that, I will try to do that this week :)


Try to catch dnsmasq configuration errors

Using the validate parameter should ensure we don't push anything
weird in dnsmasq.
Using the block/rescue logic should ensure we can get some debugging
data.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

recheck

/hold
I want a run against older CRC - iirc adoption has something?

/hold cancel
Got a pass on older CRC: https://github.com/infrawatch/service-telemetry-operator/pull/610
https://review.rdoproject.org/zuul/buildset/d688db7419f9428da196e0879dd12f3c

It help me debugging the CRC cloud feature. Thanks!


vidloop does not build

.../baresip-apps/modules/vidloop/vidloop.c: In function ‘packet_handler’:
.../baresip-apps/modules/vidloop/vidloop.c:282:57: warning: passing argument 3 of ‘vl->vc_dec->dech’ from incompatible pointer type [-Wincompatible-pointer-types]
  282 |                 err = vl->vc_dec->dech(vl->dec, &frame, &keyframe,
      |                                                         ^~~~~~~~~
      |                                                         |
      |                                                         _Bool *

Have to open this issue. The fix is not so simple for me. @sreimers, please could you have a look?

Sure will provide a PR.


[APISS-10] RFC for API Guidelines v4.0

This is too confusing as it is. Will create a separate PR to move files.


External semaphore compatibility fixes

Track when a semaphore payload is imported and restored, turn off
semaphore validation when using an external payload.
VK_KHR_external_semaphore_fd entry points and test cases to come in a follow-on patch

Hmmn, this one is going to be fun. Give me some time to wrap my head around all the details here.

@mikes-lunarg do you want to split out the two refactoring commits into their own pull request and land those, while we're still figuring out what to do with the actual external fence stuff?

Rebased and added suggestion from @chrisforbes about retiring work early when an external semaphore is signaled


fix(frontend): update routes

:tada: This PR is included in version 3.2.0-alpha.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.2.0-online.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Remove fallback to bash default completion

This doesn't work correctly when there's 'globstar' option set
in bash. Running the completion with '**' and then cancelling it stills
triggers bash globstar search, which might be very expensive.

I don't think this can be a solution. We still want to use bash default completion with those commands. e.g. ssh -i ~/.ssh/<tab>. fzf completion should be an exception, that only happens when completion trigger is given, not the default.

This will work, but I would still like to keep the default ** though.
I've noticed that the problem is caused by adding the -o bashdefault to the completion. On my system, the default completion for ssh is: complete -o default ssh (Note: there's no -o bashdefault).
So, this still works with globstart because bash doesn't try to evaluate ** as a globstar. FZF is adding -o bashdefault to the picture which causes the different (unwanted) behavior.
I've just tried it with: complete -F _fzf_complete_ssh -o default and ssh -i ~/.ssh/<tab> still works and ssh ** works as expected for me as well.

On my system, the default completion for ssh is: complete -o default ssh (Note: there's no -o bashdefault).

I see, I'd like to know if it's universally true. Do you think it's safe to make this change?

I see, I'd like to know if it's universally true. Do you think it's safe to make this change?

I must admit that I don't really understand the different between 'default' and 'bashdefault'. The bash man page is not very clear about that. I'll try to investigate more the difference between them and also try it with different distributions. So far, I've tried Archlinux and Fedora and both work better without the 'bashdefault'.

I've looked deeper into the fzf and bash completions to have a better understanding how it works. I think that my previous solution of removing -o bashdefault is not enough.
I believe that both -o default and -o bashdefault should be removed because they are changing the behaviour of installed bash completions.
Here's a demonstration:
# Create a file called '-zabc'
cd $(mktemp)
touch -- -zabc

First test scenario: No bash completion installed, no fzf completions:

ssh -z<tab> -> -zabc
# There's no "smart" completion so bash defaults to filename completion
# This is fine, at least some completion is better than nothing

Second scenario: Installed bash completions without fzf completions:

ssh -z<tab> ->   # no completion
# This is actually correct as there's no -z flag for ssh!

ssh -i -z<tab> -> -zabc
# This is correct as -i parameters expects a file

Third scenario: Installed bash completions + fzf completion:

ssh -z<tab> -> -zabc
# fzf firstly tries original bash completion. That correctly returns an empty
# response. However, fzf then incorrectly tries filename completion as well

My proposed solution:

Remove -o default -o bashdefault from the completions. That will fix the case when bash completions are installed. I've looked at Archlinux, Fedora and Ubuntu and the default completion for ssh (and other commands) is: complete -F _ssh ssh. There's no -o default nor -o bashdefault

I assume that bash completions once installed are the same on every distribution.

Modify _fzf_handle_dynamic_completion and add

else
  COMPREPLY=( $(compgen -o default -o bashdefault -- "$cur") )
  return 0
fi

at the end of that function. This will handle the cases when the bash completions are not installed. In that case we want to fall-back to the default filename completion.

Proof of concept work at: https://github.com/junegunn/fzf/pull/1149
Hopefully, I'll find some time during the weekend to work on it.


Add xo-style commands to intkey CLI

This PR updates the intkey CLI to look like the xo CLI. The new commands are:

intkey set <name> <value>
intkey inc <name> <value>
intkey dec <name> <value>
intkey show <name>
intkey list

All the old intkey commands have been removed except for workload, which will be removed when testing is changed over to smallbank. The old intkey commands have been left alone. They can be removed later, but that will have to be done in conjunction with documentation updates.

@peterschwarz:The plan, I believe, is to work on better (and consistent) CLI usage text as a separate task. I am currently gathering recommendations and will create a CLI usage style guide as part of https://jira.hyperledger.org/browse/STL-744.

@chenette @peterschwarz I added some not-very-thoughtful usage text descriptions to the new commands. We can discuss better alternatives now or come back to it later.


Fix R example and run examples in CI

This closes #121 by removing the extra argument (left over from pre- #98) and also adds a line to run each example program as part of our CI to make sure they stay up-to-date.

The PR looks OK, but there's still a failing test on the Julia side.

I can’t figure out the Julia test failure. My current guess is it’s an issue with Julia 1.9.0 which was released yesterday

I've got to move on to other things for now, but here's a quick update on my progress so far.  Julia 1.8 and 1.9 output different error messages when tested against the same faulty Stan programs.

Load the Stan program test_models/throw_data/throw_data.stan:

Julia 1.8: ERROR: construct(, 204) failed with exception: Exception: find this text: datafails
Julia 1.9: ERROR: construct(, 204) failed with unknown exception

Run BridgeStan.log_density(model, rand(1)) with Stan program test_models/throw_lp/throw_lp.stan:

Julia 1.8: ERROR: log_density() failed with exception: Exception: find this text: lpfails
Julia 1.9: ERROR: log_density() failed with unknown exception
What seems odd to me is the differences between these error messages comes from the C++ file bridgestan.cpp.  The C++ try-catch is catching different exceptions based on the Julia version.  I don't immediately understand this.
The quickest/hackiest fix would be to change line 9 in the file julia/test/model_tests.jl from if VERSION >= v"1.8" to if VERSION == v"1.8".  Is this a reasonable temporary fix, while we create a new issue focused on Julia 1.9 and move away from this Rlang PR?

I've also spent some time running it down and just filed an issue with Julia: https://github.com/JuliaLang/julia/issues/49772.
I believe this is a legitimate bug in Julia that has nothing to do with BridgeStan specifics. I'm happy to either bin Julia 1.8 in our test suite until it is resolved or merge with the one test failing.


LayerItem: fix: update label when GeoResourceFuture resolves

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.005%) to 99.675%

Totals

Change from base Build<PHONE_NUMBER>5:
-0.005%

Covered Lines:
13499

Relevant Lines:
13500

💛  - Coveralls


repositioned the loader at center of page for routes

Proposed Changes

Fixes #8762
Repositioned the loader for all routes at exact center of the display screen (you can see it in the screenshots)
@ohcnetwork/care-fe-code-reviewers

Merge Checklist

[ ] Add specs that demonstrate bug / test a new feature.
[ ] Update product documentation.
[ ] Ensure that UI text is kept in I18n files.
[ ] Prep screenshot or demo video for changelog entry, and attach it to issue.
[ ] Request for Peer Reviews
[ ] Completion of QA

Summary by CodeRabbit

New Features

Updated the Loading component to cover the entire viewport, ensuring better visibility during loading processes.
Enhanced accessibility features in the Loading component for improved user experience.

Bug Fixes

Improved positioning of the Loading component for a more consistent user experience.

Closing as duplicate of #8976


Remove all request snapshot code

What problem does this PR solve?
Issue Number: close #10526
Problem Summary:
Request snapshot is used to request a snapshot explicitly from follower to fix problems like corruption. But the API has never been used or tested. Technically, it's an unreleased feature. So we can remove these code to make code clean.
What is changed and how it works?
Just remove the code about request snapshot
What's Changed:
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
PR to update pingcap/tidb-ansible:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note
Please add a release note.
If you don't think this PR needs a release note then fill it with None.

/cc @BusyJay

/run_all_tests

/rebuild

/rebuild

/rebuild

/merge


SINGLE_TABLE Inheritance breaks with optional ManyToOne relationship in subclass

When using single table inheritance with an optional ManyToOne relationship the referenced entity is loaded with no data whatsoever.  You have to reload the entity from the database in order to get it to load any of the appropriate data.  Here is a repository link with a working example:
https://bitbucket.org/GDIBass/relationalsingletableinheritancedoctrinebug/overview

@GDIBass thank you for submitting this issue with that working example but it would be far more helpful if you could send us a PR with a failing test case. This isolates everything and makes it easier to solve the problem.
You can find examples on https://github.com/doctrine/doctrine2/tree/388afb46d0cb3ed0c51332e8df0de9e942c2690b/tests/Doctrine/Tests/ORM/Functional/Ticket.

@lcobucci Will do.  Should I name mine DDC6622?

I can't get it to replicate with the tests.  Perhaps it's something with Symfony?  I'll get something on Stack Exchange

@GDIBass closing here - please re-open once reproduced only with the ORM.

Check also https://github.com/doctrine/doctrine2/pull/1194 meanwhile


What purpose does puppeteer serve over chrome-remote-interface?

I've been working with the author of https://github.com/cyrus-and/chrome-remote-interface for several years now, and I'm wondering what purpose puppeteer serves that couldn't have been contributed to chrome-remote-interface?
chrome-remote-interface is already used by several projects and other browsers vendors such as Mozilla in https://www.npmjs.com/package/devtools-client-adapters.
The projects and even the abstractions looks much similar, with the obvious exception of Pupperteer (currently) not supporting other browsers out of the box.
I'm glad to see the Chrome DevTools team pushing for CDP usage outside of DevTools. Just curious on the rationale to fork instead of working with the community.

Puppeteer is the next logical abstraction layer on top of the protocol after cri. It encapsulates some of the web domain specifics:

interprets network events to implement navigation strategies
explains how device emulation works
explains how to capture full page screenshots
how runtime can be used to evaluate complex / async expressions
and many more to come...

Basically, it serves as a reference to the protocol implementation, where context and order of the events are as important as the protocol method signatures themselves.
It turns out that with this mission is accomplished, we are getting a sound product that can be used for the PhantomJS scenarios running against the modern Chromium platform. So we decided to go all the way there and commit to the use-case-driven lightweight API for web testing and automation with Puppeteer.
This is by no means a replacement for the devtools protocol as an interfacing API for tool vendors to use, quite the opposite, this is a real-time reference for the key protocol methods usage.

I'll add in that we want to see CDP succeed too. At the same time, it's kind of horrifying that it takes ~75 LOC to take a fullpage screenshot with the protocol.  I felt uncomfortable asking all developers to engage with the browser at that layer.
Instead of those 75 lines, that should be more like
const browser = await puppeteer.launch();
let page = await browser.newPage();
await page.goto('https://www.google.com/');
await page.screenshot({path: 'output.png', fullPage: true});
browser.close();

This is more reasonable for all developers who want to write an automation script.
However, yes... there are usecases that puppeteer doesn't satisfy. For example, it's unclear if Lighthouse will ever move to sit on top of puppeteer, as we have very unique usecases. For those situations and for other tool developers, writing against the protocol layer makes total sense.
As an aside, we're going through the exercise of making sure all the protocol methods and features that Puppeteer is using are non-experimental in the protocol. That sort of backpressure on protocol stability feels good, ya?

Great job, this is my choice to replace phantomjs!

Thanks for sharing the perspective and reasoning @pavelfeldman @paulirish. My initial understanding of puppeteer was "yet another" pure CDP client, but I now understand that the goals for the clients and abstractions a different.
And yeah @paulirish, protocol stability feels ;)

The release of Puppeteer is a really exciting development. I've been waiting for some time for something like this to happen. We've seen what happened to PhantomJS (almost 2k open issues and main maintainer stepping down without a successor), NightmareJS (lot of unreplied issues for months, probably the project is not a strategic part of Segment) and so on. In theory it is great for an individual or an established startup to drive a web browser automation project. But in reality, the scope of web browser automation simply gets out of hand very quickly. There are just too much edge cases to support for a fast-changing domain. Being driven by a large commercial entity actually has a chance of making it work out.
I'm speaking from the context of test automation and general browser automation. Puppeteer functions more like the high-level browser automation projects above. Whereas Chrome Remote Interface project really is a low-level way to access all that DevTools Protocol can offer. By being low-level it gives developers the tools to do whatever should be possible with the protocol. Puppeteer on the other hand, by being specifically designed to addressed browser automation, makes it so much easier to do common tasks and pain points encountered for browser testing / automation.
The issue for this domain is the DevTools Protocol (Chrome Debugging Protocol was the old name I think) is designed originally for debugging the browser. It looks like there's intention to support more automation use cases. However there is still a lot of hacking needed to do something simple and what is often required, for the example of capturing a full page screenshot. Chrome Team themselves have to write a lot of code to do that. That's really ok, because of the original purpose of DevTools. Puppeteer, however, bridges that gap by abstracting the many low-level steps into simple browser automation methods.
So it's really 2 different projects for different purposes, and should be allowed to developed separately. So that both projects can iterate at its own maximum speed to reach its own potential faster. I'm a CasperJS user for couple of years, and my initial impression of Puppeteer looks like it could be the foundation to transit CasperJS to support visible / headless Chrome.


LEDs not working

At least for me LEDs are not working since this release: https://github.com/ah-/anne-key/releases/tag/2018-03-10-127-master-f4fe08f

Thanks! It should work if you manually toggle the LED chip off/on via the FN2 layer (https://github.com/ah-/anne-key/blob/master/src/layout.rs#L52). Hold the ANNE key down, then press escape, wait a second, then press 1. Afterwards the normal fn-rtyu keys should work.
This is due to us not yet having proper power management for the LED chip, I'll see if I can put something in to make it somewhat work again short-term..

For whatever reason I still can't get them to work, even after following your instructions. Wish I had something to debug the keyboard with.

Hmm, I'm just seeing the similar issues. Sometimes it works after a reset, sometimes it doesn't. Will investigate.

Can you try the lateest build once it's done? This makes it work somewhat reliably for me now. The manual toggle from earlier didn't work I think because I had local changes.

Can confirm this issue is fixed now.


For 9.6.0 release: description of new Metrics functionality and its microflow activities

@RTI team: can you review this?
@Documentation team: can you review this after approval of the RTI team? Other question: we refer to some images in the microflow activity descriptions, like we do in the workflow activity descriptions. Should we add these images or do you want to make them?

Images reviewed.


Rename the ':api' subgenerator to ':endpoint', ':model' or ':resource'

I'm not a native speaker either, but I think most people would understand API as the complete collection of all related endpoints in a given system or project, while :endpoint would make more sense to describe each individual URL to manipulate a single named resource.

It seems reasonable. I like api because it refers directly to the folder name. I would not change the name though, because it will end up in a huge breaking change. Instead we can create an alias.

Closing this because it isn't a priority and creating alias with Yeoman isn't trivial. If someone really wants this, I'll accept a PR adding the alias. 👍


update streams page

updates the stream page plotting
Dont merge yet

@DanielJMaher @oceanzus im also going to fix the toc

@oceanzus this one is done ill do the toc in another one


Update state of the world when receiving blocks

Block needs to be validated.
Transactions in the new block need to update account balances
and be deleted from the mempool.

This ticket is about "state = consensus manager" subsystem.
When this subsystem gets new block from sync subsystem which is networking, it should validate incoming data (if its not malicious, etc).
When data is correct, it has another role besides validation layer - it should force the correct consensus on our node.
It should send data to blockchain service, to state service and to mempool

Block needs to be validated.

I understand this ticket depends on validation of block header i.e. #44

Block needs to be validated.

As an optimization, a set of observed invalid/bad blocks can be kept in order not to waste network and computation resources re-downloading the block. Keeping a set of the hashes of the block headers of the invalid/bad blocks would be sufficient. The set could be limited in size e.g. only the 100 most recently seen on the network.
The typical case I have in mind is a block whose header is valid but whose body is not. This can happen if e.g. any of the following happens:

Any of the transactions in block is structurally invalid e.g. invalid signature;
Any of the transactions in the block shall not have been included (or not included in that position) because of unfulfilled requirements/assumptions (e.g. account balance not sufficient, nonce not big enough, oracle creation with id already used);
Hash of the root of the state trees after application of transactions is not correct (consider that, provided transactions are executed in order from genesis, the hash of the root is deterministic and verifiable).

@lucafavatella great idea about the bad blocks! Yes, please include them (hashes).
And Yes it depends on #44 and on validating the block itself. @lucafavatella do you think we should move validation to your service and keep this one only as a dispatcher of requests? (we need central place to control business flow of incoming new block anyway).
Probably the validation code should live in a block service but be executed based on call from here.
It will be like a dependency path - when one check is green, we can proceed to the next one with new block handling

@lucafavatella do you think we should move validation to your service and keep this one only as a dispatcher of requests? (we need central place to control business flow of incoming new block anyway).
Probably the validation code should live in a block service but be executed based on call from here.
It will be like a dependency path - when one check is green, we can proceed to the next one with new block handling

@sennui Block validation takes time and I would not make it run in a server holding state (like the one in #69) as that would become a bottleneck. I believe validation can be run by any process, interacting with the other services as needed.

@lucafavatella true, but I meant logic not the context. The operation will be run in a context of dispatcher (#71) or dispartcher-spawned process. The code should live in #69 and be written by you or Zbig because you know the most about it @zp-sd


Add a default fallback handler

Context / issue
Safes deployed by the Safe Core SDK can't receive NFT's automatically because the default falback handler is set to the zero address.

Add a default fallback handler (https://github.com/gnosis/safe-core-sdk/blob/main/packages/safe-core-sdk/src/safeFactory/index.ts#L125)
Add a method to replace the fallback handler (https://github.com/gnosis/safe-contracts/blob/main/contracts/base/FallbackManager.sol#L26)

Hi @germartinez , I think you have opened this issue after looking at my StackExchange post, right?
Few more things to draw into your attention:

Safes deployed by Safe Core SDK also can't receive ERC1155 NFTs automatically. Pls also consider this.
There are so many Safes on Ethereum Mainnet deployed via our platform using Safe Core SDK. Can you pls share an easy to understanding steps to enable this default fallback handler things for already deployed Safes on Mainnet.
Kindly consider resolving this issue asap.


Figure out how to reconcile existing resources with newly imported ones from templates

This should resolve how we handle variable importing that was mentioned in #13297


Show help when no command line arguments are given

Currently, it crashes when no arguments are given. AppSettings::ArgRequiredElseHelp can prevent it.

Thanks :)


Config server yml or properties endpoints can produce unexpected results when merging collections and maps

Please review the attached YAML file for sample properties. Note the default profile has an array of PromoCode objects defined. When a SpringBoot application is configured to talk to the Config Server with the appropriate profile, you get the correct response. However, when you request the properties or yaml view, you get a mixed array of the 2 profiles.
http://localhost:8888/promoCodes/default - produces correct json
http://localhost:8888/promoCodes/dev - produces correct json

Alternate views produce correct results for default profile
http://localhost:8888/promoCodes-default.properties

promos.promoCards[0].client: Google Nexus 6P     <----
promos.promoCards[0].description: Free stuff for Google users     <----
promos.promoCards[0].endDate: 2016-04-26T20:01:30.781Z     <----
promos.promoCards[0].image: http://google.com/images/coolpic.jpg     <----
promos.promoCards[0].name: P1     <----
promos.promoCards[0].platform: Android     <----
promos.promoCards[0].startDate: 2016-04-26T20:01:30.781Z     <----
promos.promoCards[0].thumbnail: http://google.com/images/coolpic.jpg     <----
promos.promoCards[1].client: Google Nexus 5X
promos.promoCards[1].description: Free stuff for Google users
promos.promoCards[1].endDate: 2016-04-26T20:01:30.781Z
promos.promoCards[1].image: http://google.com/images/coolpic.jpg
promos.promoCards[1].name: P2
promos.promoCards[1].platform: Android
promos.promoCards[1].startDate: 2016-04-26T20:01:30.781Z
promos.promoCards[1].thumbnail: http://google.com/images/coolpic.jpg
promos.promoCards[2].client: iPhone 6S
promos.promoCards[2].description: Expensive stuff from Steve
promos.promoCards[2].endDate: 2016-04-26T20:01:30.781Z
promos.promoCards[2].image: http://apple.com/images/coolpic.jpg
promos.promoCards[2].name: P3
promos.promoCards[2].platform: iOS 9
promos.promoCards[2].startDate: 2016-04-26T20:01:30.781Z
promos.promoCards[2].thumbnail: http://apple.com/images/coolpic.jpg
promos.promoCards[3].client: Nokia Lumia 8610
promos.promoCards[3].description: Bad stuff for windoze users
promos.promoCards[3].endDate: 2016-04-26T20:01:30.781Z
promos.promoCards[3].image: http://microsoft.com.com/images/coolpic.jpg
promos.promoCards[3].name: P4
promos.promoCards[3].platform: Windoze
promos.promoCards[3].startDate: 2016-04-26T20:01:30.781Z
promos.promoCards[3].thumbnail: http://microsoft.com.com/images/coolpic.jpg

Alternate views produce incorrect results for dev profile
http://localhost:8888/promoCodes-dev.properties

promos.promoCards[0].client: Nokia Lumia 8888     <----
promos.promoCards[0].description: Bad stuff for windoze users     <----
promos.promoCards[0].endDate: 2016-04-26T20:01:30.781Z     <----
promos.promoCards[0].image: http://microsoft.com.com/images/coolpic.jpg     <----
promos.promoCards[0].name: P4     <----
promos.promoCards[0].platform: Windoze     <----
promos.promoCards[0].startDate: 2016-04-26T20:01:30.781Z     <----
promos.promoCards[0].thumbnail: http://microsoft.com.com/images/coolpic.jpg     <----
promos.promoCards[1].client: Google Nexus 5X
promos.promoCards[1].description: Free stuff for Google users
promos.promoCards[1].endDate: 2016-04-26T20:01:30.781Z
promos.promoCards[1].image: http://google.com/images/coolpic.jpg
promos.promoCards[1].name: P2
promos.promoCards[1].platform: Android
promos.promoCards[1].startDate: 2016-04-26T20:01:30.781Z
promos.promoCards[1].thumbnail: http://google.com/images/coolpic.jpg
promos.promoCards[2].client: iPhone 6S
promos.promoCards[2].description: Expensive stuff from Steve
promos.promoCards[2].endDate: 2016-04-26T20:01:30.781Z
promos.promoCards[2].image: http://apple.com/images/coolpic.jpg
promos.promoCards[2].name: P3
promos.promoCards[2].platform: iOS 9
promos.promoCards[2].startDate: 2016-04-26T20:01:30.781Z
promos.promoCards[2].thumbnail: http://apple.com/images/coolpic.jpg
promos.promoCards[3].client: Nokia Lumia 8610
promos.promoCards[3].description: Bad stuff for windoze users
promos.promoCards[3].endDate: 2016-04-26T20:01:30.781Z
promos.promoCards[3].image: http://microsoft.com.com/images/coolpic.jpg
promos.promoCards[3].name: P4
promos.promoCards[3].platform: Windoze
promos.promoCards[3].startDate: 2016-04-26T20:01:30.781Z
promos.promoCards[3].thumbnail: http://microsoft.com.com/images/coolpic.jpg

Note the difference in promos.promoCards[0] between the 2 results indicated by <----.
The desired output should be for the dev profile:
http://localhost:8888/promoCodes-dev.properties

promos.promoCards[0].client: Nokia Lumia 8888
promos.promoCards[0].description: Bad stuff for windoze users
promos.promoCards[0].endDate: 2016-04-26T20:01:30.781Z
promos.promoCards[0].image: http://microsoft.com.com/images/coolpic.jpg
promos.promoCards[0].name: P4
promos.promoCards[0].platform: Windoze
promos.promoCards[0].startDate: 2016-04-26T20:01:30.781Z
promos.promoCards[0].thumbnail: http://microsoft.com.com/images/coolpic.jpg

The issue occurs in org.springframework.cloud.config.server.environment.EnvironmentController, specifically convertToProperties(Environment environment):
private Map<String, Object> convertToProperties(Environment profiles) {
    Map<String, Object> map = new TreeMap<>();
    List<PropertySource> sources = new ArrayList<>(
            profiles.getPropertySources());
    Collections.reverse(sources);
    for (PropertySource source : sources) {
        @SuppressWarnings("unchecked")
        Map<String, String> value = (Map<String, String>) source.getSource();
        map.putAll(value);                               <-- (No checking for existing array from earlier profile with same name)
    }
    postProcessProperties(map);
    return map;
}

The issue is the for loop over the PropertySources. The Map<String, String> value has a key that contains all the individual promos.promoCards[X] entries individually and puts them all on each iteration into a final map, replacing any duplicates.  However, in the case of a YAML list, it should also be checking if any other 'promos.promoCards[' exists as keys and remove them before adding all of the current iteration to the resulting map.
promoCodes.yml.txt

When you say

(No checking for existing array from earlier profile with same name)

Do you mean an existing array with the same name from an earlier property source?

@spencergibb yes, for instance, in the default profile you have an array established as such: promos.promoCards[0].client. If this is the case, then any other promos.promoCards[X]: should be removed before doing the putAll on the map.
You should be able to take the attached yml, put it in any Config Server git repo and see the result by hitting the different endpoints.

I think this is asking too much of the properties endpoints (i.e. it's not supported and isn't really supposed to be). If you have a proposal about how to improve it, we can treat it as an enhancement (pull requests welcome).

@dsyer I think this a bug, rather than an enhancement. It is a data consistency issue. When you request the normal JSON endpoint, you get the desired results. However, when you request properties or YAML, with the supplied config file, you get a mix of the data provided by the default profile and the dev profile. The array of properties returned with the dev profile replaced the first element in the default array with the only item in the dev array, yet all the other default items in the array remain in the final output.
I have the code pulled down and need to get it into STS or Intellij to play with it. Hopefully, I can get a PR out there for it.

+1 I've just got a same bug

This issue was closed as "fixed" more than 4 years ago. If you are experiencing a problem with the latest version, it would be better to open a new issue as it's unlikely to be related.

Yep, thank you


"It is diffcult or impossible to do obsure(very unique) things in Keras".  Is it?

"It is diffcult or impossible to do obsure(very unique) things in Keras", this is what an expert in out department has suggested me. He advised me to switch to TF.  We are working on a Deep learning Project, which might lead us to propose our own CNN architecture and very different way of back-propagation, where loss function will be calculated at different layers simultaneously. We will be using CNNs inspired architecture for reconstruction and denoising of images. I am well familiar with CNN for classification in Keras, therefore I would obviously try to stay with Keras. Also learning curve of TF is little higher compare to KERAS. SO my question is what do u think of that guys statement  "It is diffcult or impossible to do obsure(very unique) things in Keras"? Has anybody experienced it?

Looking at the variety of projects out there featuring Keras, I would tend to disagree with this. Also, don't forget Keras supports defining custom layers.

Disclaimer: I'm just a beginner trying to learn more, so I might be way off on this one.
Well, if you use Keras on top of TF then what's the problem? You can use everything in TF and use Keras at the same time, no?
I'm no expert, far from it as a matter of fact, but it seems to me that it ought to be easier to modify an existing framework than to write everything you need "from scratch" in TF? Having different gradients from different loss functions that flow into a NN at different layers seems like something that Keras can handle.

Well, if you use Keras on top of TF then what's the problem? You can use everything in TF and use Keras at the same time, no?
The problem is I am novice to TF. And as said learning curve of TF is higher, so nothing but time.
Yes well said keras and TF can be easily mixed. Well known to me.


Errors upon upgrading to 0.43.0

Note the tests still pass

It’s hard to see what is causing the error as it’s being masked by the unhandled rejection, but this might be related to https://github.com/libp2p/js-libp2p-tcp/issues/130

Errors are no longer around in newer versions


Language selection

This is probably going to be a fairly large change, besides requiring third-party effort for the translations. May be worth setting up one of those open-source localization services?

#https://github.com/johnnesky/beepbox/issues/33

Didn't mean for the mention to show up on the beepbox github, welp

Are we going to have it automatically translate the webpage or is it going to be manually done? I've seen instances where beepmods have been automatically translated from english to other languages (with there being a mod that actually does this already) but I want to make sure exactly what we're supposed to be doing here.


More colors functionality?

Colors also supports formatting (underline, bold, etc). Any chance of getting support for these? I'd love to be able to set a certain log type so it's bolded as well as colored.

Would look at a PR for this.

Well, actually this is already supported.


Divided pagination sample into 3 different samples

Divided pagination sample into 3 different samples:
1. SearchWithPageSizeSample
2. SearchWithOffsetSample
3. SearchWithNextPageTokenSample

And tests are green! The error is an unrelated flake.

@amanda-tarafa I've applied suggested changes. Hope everything looks good now :)
CC: @t-karasova

Failure is unrelated and being tracked in #1563


Explain the Iroha versioning

Python 3 guide and [JavaScript guide] mention certain versions of Iroha, currently v2-pre-rc.1 for Python 3 and 2.0.0-pre-rc.9 for JavaScript.
This will need to be clarified for the new user: we should add links to download a version with a certain tag, explain how to get a certain version from SDK, apply the same approach for the SDKs and tell what SDK code works with a certain Iroha version.
TL;DR: more is needed to tell a version; we need to explain what steps a user needs to perform.

This is essentially what we discussed re versions and doc testing, right?


create-react-app on create container

Related to issue https://github.com/github/codespaces-react/issues/3.
With these changes the create-react-app script is executed when the container is started.

👋 Thanks for the PR! I'm a little confused as this looks like it deletes a good chunk of the template?

Yes, it deletes the current project because the project is always created by the create-react-app script, always bringing the most stable version of the react app. The idea here is not to need to update the template from time to time.

commit

I believe that would interact poorly with our codespace prebuilds on this project. Currently while it's a frustrating burden to update the template periodically it provides the best possible user experience because they don't have to wait for any dependencies to be installed or anything to be generated by create-react-app. This would be net-better for us, the maintainers, but worse for our users.

It is a good observation point. I took into account the user's requirement to always start with the most up-to-date source code version, in the same way that the machine is configured before use.

For sure that is also important.


Make test_demo.py to a single CI job

What was wrong?
Fix #354
How was it fixed?
Extract test_demo to py36-eth2-demo.
Cute Animal Picture

@hwwhww what do you think about the following:
/tests/eth2/core/beacon/*
/tests/eth2/integration/beacon/*
so that we can s/beacon/shard/ when the time comes
and that the "demo" stuff goes into integration for now

@hwwhww i started making the changes and i'm happy to do so -- just want to confirm as it will involve some import patching, etc. i would prefer to only do once

Sorry for the delay of this PR! I was thinking about that we can mock BLS verification in this test, as:
https://github.com/ethereum/trinity/blob/ee5951a788fd697bf7c16a4269f472b4bcc8495e/tests/eth2/beacon/state-fixtures/test_minimal_state.py#L29-L52
@ralexstokes the directory looks good to me! Feel free to close this PR and make another one if you've started to work on this. 👍


[BUG] EventHubEvent implementation does not reflect the Event Hub message structure

Investigative information

Python version: 3.7

Repro steps

Create an Azure Function with Event Hub trigger
Observe the structure of the EventHubEvent parameter in the main function:
def main(event: azure.functions.EventHubEvent):
or the interface it is implementing: azure.functions._abc.EventHubEvent

Expected behavior
The structure of the EventHubEvent interface (and implementation) should reflect the actual data structure of the event hub message.
Practically the EventHubEvent should match the Python SDK for Event Hub EventData implementation.
Actual behavior
The azure.functions.EventHubEvent does not match the structure of azure.eventhub.EventData. Some attributes are entirely missing, such as:

properties
system_properties

Known workarounds
None.
Contents of the requirements.txt file:
N/A
Related information

azure.functions.EventHubEvent
azure.functions._abc.EventHubEvent
azure.eventhub.EventData

Discussed with @Hazhzeng. We are looking to see if we can add the raw json payload.

I took a quick look at this as well. There might be an additional issue when the cardinality of the trigger is set to one. Even the basic enqueued_time, offset, etc were missing for me.
Problem might be here: https://github.com/Azure/azure-functions-python-library/blob/e008cbf1c3fcb602407fce45a8a5f906bcbe900b/azure/functions/eventhub.py#L128-L139
Looks like the trigger metadata has different properties than what the code is expecting so the mapping doesn't work.

Yes we have already added the enqueued_time but it is not deployed. https://github.com/Azure/azure-functions-python-worker/issues/639. Since this will be an ongoing issue with the SDK changing we are planning to add a raw body property so that customers can get the raw payload

@anirudhgarg Can you share more information on what's changing in the metadata that breaks this? Exposing the raw data just passes on the problem, and any app that is dependent on the raw data will still break.

Lets make sure that this works for cardinality 1 and cardinality many

@Hazhzeng What is the ETA for this fix to be generally available?

@daawnee I will check up on this today, We should have already deployed this but I will confirm today.

In v1.3 I don't see any change in the interface, so probably it has not been released, yet.

Yes the deployment is going on right now - we are hoping it should finish by the end of next week if not earlier.

Deployment is done, we have added the properties now. Closing this out.


opt into or remove deprecated interfaces

The deprecated interfaces include the following.
document.remove() returns a response with both a uris property and a uri property.  The singular property is a legacy from when document.remove() could only remove a single document.  We should remove that property in MarkLogic 9.
In MarkLogic 8, the developer has to opt in to get a transaction object and receives a transaction id string by default.  MarkLogic 9 should reverse the default and opt in.
In MarkLogic 8, the developer has to opt in for a zero-based slice on the search response and supplies a 1-based slice by default.  MarkLogic 9 should reverse the default and opt in.

MarkLogicClient.remove() should also be addressed per the documentation:

For backward compatibility, if a string is passed, the uri is returned as a string, but in the next major release, the uri will be return as an array with one string.

Mike, if you find other things to remove/change besides the items called out here, please add them so that I can ensure they all make it into the release notes.

Per email discussion with @ehennum and @jmakeig, we will deprecate the transactionId string and legacy slice option in ML9 and remove those features entirely in ML10. I will add to the JSDoc regarding this in my check-in and @kcoleman-marklogic can review.

@ayuwono, these updates to address deprecated features will break tests:

Remove() methods for documents now only return arrays of one or more URIs. So any tests that expect a string return value need to be fixed.
The transactions.open() method now returns a full-fledged Transaction object by default instead of an object with a transactionId string. So any tests not expecting the Transaction object will need to be fixed.
The slice() method now works in "array" mode by default. This differs from "legacy" mode in how the params work. Tests that are working with sliced results will need to have their params updated.

Changed all of the affected tests

@kcoleman-marklogic, can you review the changes to the jsdoc comments for this fix? You can see what changed here:
https://github.com/marklogic/node-client-api/pull/360/files
Namely, there are comment changes for:
DatabaseClient.remove()
queryBuilder.slice()
transactions.open()

Bit late for me to mention this, I know, but shouldn't the slice change apply to values queries, too? It seems rather odd to only make it zero-based for search results.

Sorry to get to this so late. Incompats always come in really late for me. The jsDoc looks OK modulo the following:

the question above about slicing values query results (btw, to prop up my assertion, marklogic.setSliceMode claims it applies to both)
if the slice change applies to both, then the values query slice jsDoc needs updating
in queryBuilder.slice, this text in the description used to be a link and isn't now: module:marklogic.setSliceMode
transactions.open does not make it clear what the default is, IMO

The only one of these that's important is the values slice issue.

One other thought that drifted across my empty mind:
I have covered these changes in the ML release notes, but should they be mentioned somewhere on GitHub? IDK what the GitHub convention is for reporting backward incompatibilities.

@ayuwono, let's chat today about possibly getting the slice update for values queries in for 2.0.0. See Kim's comment https://github.com/marklogic/node-client-api/issues/231#issuecomment-296403244.

FWIW, here are the related release notes:
http://pubs.marklogic.com:8011/9.0/guide/relnotes/chap4#id_34190

@kcoleman-marklogic, in http://pubs.marklogic.com:8011/9.0/guide/relnotes/chap4#id_78125:
In the first code example, "PageLenth" --> "PageLength"

@kcoleman-marklogic, in https://github.com/marklogic/node-client-api/issues/231#issuecomment-296404227 you say:

transactions.open does not make it clear what the default is, IMO

The Returns documentation for that method currently says:
"either a Transaction object (the default) or string transactionId..."
Are you referring to some other default value?

No, sorry, I didn't read as far as the "returns" description, so I missed that. I retract my statement.
My pea brain got stuck on the function description at the top (which leads with the non-return result type) and the option description, neither of which indicate what the default is.

I'll check the link tomorrow morning, after the next doc build. I want to make sure it works on DMC, too (it should). I'll fix that typo in the release notes before tomorrow's build, too.

@kcoleman-marklogic, thanks, I will merge that PR then now so it gets into the doc build.

@kcoleman-marklogic, regarding https://github.com/marklogic/node-client-api/issues/231#issuecomment-296455238 about documenting backwards incompatibilities, I'd like to avoid duplicating documentation so how about we link to that incompatibilities doc page from the GitHub release page? I put static text in the release draft from which we can link when we have a final URL:
https://github.com/marklogic/node-client-api/releases
@jmakeig, any thoughts on this?

@kcoleman-marklogic, regarding the slice() method for ValuesBuilder in https://github.com/marklogic/node-client-api/issues/231#issuecomment-296404227, I think you're right. But I talked to @ayuwono and we agreed that it is too late to get that into 9.0-1. Definitely put that in 9.0-2, I will file an issue.

About slice: OK, thanks. I'll change the docs not to include value query.
About the incompats: Linking to docs.marklogic.com is OK with me, but it is really up to Justin.
If you decide to go with it, the URLs will be exactly as now, but replace the host:port prefix docs.marklogic.com. So http://docs.marklogic.com/9.0/guide/relnotes/chap3#whatever.

@kcoleman-marklogic, thanks for the link info. I updated the release page with the appropriate docs.marklogic.com link:
https://github.com/marklogic/node-client-api/releases

The links aren't working worth a darn on pubs, but that's on our end and nothing to do with you. Could be a problem with how we're building the JSDoc or maybe the doc app is doing something nefarious. Either way, not your problem. I'll investigate today.

OK, I think we're good. It looks like the doc build didn't pick up your last checkin for some reason. It's kinda weird since we clone a new copy of the repo every night. Gremlins.
Anyway, I expect happy faces everywhere tomorrow.

The build from this morning looks fine. Your links are working.

Thanks, @kcoleman-marklogic. Closing.


DyanmoDB: Allow accessing the table's key schema

Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository's issues are intended for feature requests and bug reports.

I'm submitting a ...

[x] :rocket: feature request

What is the expected behavior (or behavior of feature suggested)?

It would be nice if it was possible to read a DynamoDB table's key schema (hash attribute name and type, as well as range attribute name and type if there is one).

What is the motivation / use case for changing the behavior or adding this feature?

When building abstractions on top of DynamoDB (think: API Gateway proxies, Lambda functions that perform scheduled maintenance, ...), it can be useful to know the key schema in order to be able to generate correct integration requests.

I agree, and more! Lately I realized we need to expose all (resolved) configuration props as read only properties of the concrete construct, to support reflection use cases and aspects. Wanna pick this up?

I agree with the general ideal, however the current DynamoDB Table construct does not lend itself very well to this... because it is a somewhat mutable construct (you can add local & global indices after the construct is initialized, and those are effectively configuration props).

It’s a good point but still for the use case of aspects and validation this is still useful because at that point I expect all configuration to be final. Having said that, we should call that out in the docs of relevant properties that those can change


Draft & Verify

Does this repository implement Draft & Verify?

@Ryu1845 hey! thanks for sharing that paper!
that looks quite close to the early exit strategy (but i think they predict which layers to skip) - but using the same model for drafting is definitely what i was going for.
i think my prophet transformer idea should be the best though (although i'm biased and still haven't ran any head to head 😆 )

@Ryu1845 really think we are going to see a resurgence in adaptive computation research over the next year, like actually made practical

I think so too, thanks again for your work.
it looks like the official code for the paper will be uploaded here, but I'll keep an eye on this repo too :wink:

@Ryu1845 sounds good!
yea i think the main idea from the prophet is to take advantage of the cached last layer embedding from the large model, which should be superior to any early exit stuff. if you find me another paper that did that, would definitely read and implement

@Ryu1845 ohh yes, they totally did. so the only difference is i use a small transformer as the medusa / prophet heads
ok let me cite them as well

@Ryu1845 oh haha, they don't have a paper, just a github repo

I'm guessing they'll release a paper once they've got a working prototype :smile:
It looks like it's still a WIP https://github.com/FasterDecoding/Medusa/issues/3

@Ryu1845 ohh, so it isn't functional yet? maybe i'll send their group a message. solving batched spec decoding is a bit tricky

~~I'm guessing they'll release a paper once they've got a working prototype 😄 ~~ ~It looks like it's still a WIP FasterDecoding/Medusa#3~ I actually don't know if it's running yet :/

so it works or doesn't work?

it looks like it works, I'm sorry for the misunderstanding on my side

nice! that's amazing, i believe in that approach

i'll have to read their code next week and see how they approach batching

@lucidrains
Amazing work!
Do you plan to release your results with early exit?
Thanks


New release for eo-strings_0.4.0

New release for eo-strings_0.4.0

PR-Codex overview
This PR focuses on updating the version of the org.eolang.txt package and its dependencies. It also adds new functionality and fixes some issues.
Detailed summary

Updated the version of the org.eolang.txt package and its dependencies to 0.4.0
Added new objects and tests for string manipulation
Added support for regular expressions in the org.eolang.txt package
Improved the trimming and splitting functionality of strings
Added new methods to check if a string contains alphabetic or ASCII characters
Added new method to repeat a string multiple times

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@yegor256 Please, have a look


Phrase "translations" rendered multiple times

There are two things worth investigating.
Translations invoked prematurely
Looks like some phrases that should only be used in outcome nodes are being "translated" in the questions that lead to that outcome eg if you add a Rails.logger.warn("[Translating]<EMAIL_ADDRESS>somewhere here and visit http://smartanswers.dev.gov.uk/maternity-paternity-calculator/y/maternity/2015-08-11/yes, you will see that this phrase is rendered there.
I believe this should not be required
Translations invoked multiple times
If you visit any outcome you will see that a lot of phrases are being "translated" multiple times. I'm curious if this can be avoided.

I don't believe this is a problem now that we've switched away from using the I18nRenderer.
The original problem was in I18nRenderer#translate! and its call to I18n.translate!. The call to I18nRenderer#state_for_interpolation in that method resulted in the return value of every method on the state object being sent to I18nRenderer#value_for_interpolation. If the value sent to #value_for_interpolation was a PhraseList then we'd call I18n.translate! again, which would result in another call to I18nRenderer#state_for_interpolation. I think this explains both problems listed in this issue, i.e. why we were seeing multiple translations of the same key, and why we were seeing phrases translated even when they weren't required by a given outcome.
Closing.


Stay responsive without using activateignoreotherapps

Hello again :)
I put a webview inside the popover, and the webview responds to mouse movements on first show of the popover but after clicking outside the popover which will hide it, and then showing it again, this time the webview is not responsive unless I click inside the pop over. Of course activateigonoreotherapps solves the problem, but it creates like a glitch because it greys out other opened apps. and it is not a nice user experience. e.g. dropbox app on mac activates and responds to mouse movement inside its popover without greying out other opened apps.
I hope you understood what I mean.
Best

Hi there! Thanks for reporting the issue. I will trying working with a web view and see what I can do.


Update request: armcord 3.2.5 → 3.2.6

Package name: Armcord
Latest released version: 3.2.6

Current version on the unstable channel: 3.2.5
Current version on the stable/release channel: 3.2.5

[x] Checked the nixpkgs pull requests

Notify maintainers
@wrmilling

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

Looks like you submitted it moments before I was about to click send on my PR and came to copy the issue number :smile:


Does iodine work on Mac OS X 10.15.6?

I see the following error on Mac OS X 10.15.6. Does iodine support Mac OS X? Thanks.
$ sudo ./iodined -f <IP_ADDRESS> test.com
Enter password:
iodined: open_tun: Failed to open tunneling device: No such file or directory

What version are you running?
You either need the old tuntaposx (http://tuntaposx.sourceforge.net/) or use utun (by setting -d utunX)

What version are you running?
You either need the old tuntaposx (http://tuntaposx.sourceforge.net/) or use utun (by setting -d utunX)

When I tested iodine, I used the one cloned from this repo.

When I tested iodine, I used the one cloned from this repo.

With recent macos versions utun devices should be used. Try with argument -d utun0 (or higher number if needed)

With recent macos versions utun devices should be used. Try with argument -d utun0 (or higher number if needed)

I just pushed a commit that should automatically use utun without having to specify -d option.

I just pushed a commit that should automatically use utun without having to specify -d option.

With recent macos versions utun devices should be used. Try with argument -d utun0 (or higher number if needed)

I did try this. However MacOS errors out saying iodine: open_tun: /dev/utun0: No such file or directory:

It sounds like you are using an old version (not recent from git). Try again with the latest code, it should work without having to specify -d.
What does ./bin/iodine -v print? If you just run iodine it is possible it is using another version found in the PATH.

It sounds like you are using an old version (not recent from git). Try again with the latest code, it should work without having to specify -d.
What does ./bin/iodine -v print? If you just run iodine it is possible it is using another version found in the PATH.

I'm running 0.7.0. Is it the right one? I downloaded the tarball from the Iodine website

No, go to https://github.com/yarrick/iodine and click the green Code button and select 'Download ZIP'
0.7.0 is a few years old now.

Thanks!


Update codeql-analysis.yml

replaced dev7x to dev7 for CodeQL scanning

@brentschmaltz we will want to bring this one over to dev7 as well.


Set the namespace in the sample configurations for the ray & jupyter applications to ai-on-gke

/gcbrun

Thanks. I've now also included the files in the applications/rag directory.

/gcbrun


spam hdf5 output

loads of errors printed out from hdf5 along the lines of
HDF5-DIAG: Error detected in HDF5 (1.12.2) thread 31:
  #000: H5A.c line 528 in H5Aopen_by_name(): can't open attribute
    major: Attribute
    minor: Can't open object
  #001: H5VLcallback.c line 1091 in H5VL_attr_open(): attribute open failed
    major: Virtual Object Layer
    minor: Can't open object
  #002: H5VLcallback.c line 1058 in H5VL__attr_open(): attribute open failed
    major: Virtual Object Layer
    minor: Can't open object
  #003: H5VLnative_attr.c line 130 in H5VL__native_attr_open(): can't open attribute
    major: Attribute
    minor: Can't open object
  #004: H5Aint.c line 545 in H5A__open_by_name(): unable to load attribute info from object header
    major: Attribute
    minor: Unable to initialize object
  #005: H5Oattribute.c line 476 in H5O__attr_open_by_name(): can't open attribute
    major: Attribute
    minor: Can't open object
  #006: H5Adense.c line 394 in H5A__dense_open(): can't locate attribute in name index
    major: Attribute
    minor: Object not found

occurs on three different platforms (foe-linux, arc4, and my Mac)
possibly a conflict that occurs as a result of iris or climateforcing in the dependencies (everything is conda installed from conda-forge, except climateforcing which comes from chrisroadmap.).

ah, it's climateforcing causing the issues

There does not appear to be an obvious conda-based solution to this other than to delete and re-install conda. This did work.
It would appear that where possible, all packages should be obtained from the conda-forge channel. I tried this previously but the installation/my conda distro was probably so old and conflicting that it wouldn't work.
https://stackoverflow.com/questions/74226436/hdf5-error-when-opening-nc-files-in-python-with-xarray


Dev i2c #379

Closes #379
I2C/SPI refactored to use context manger to handle closing the device

@sjpark608 as discussed, please add integration tests to blast i2c and spi devices over the limit of file descriptors to see if any issue happens.


[Bug Report] While listening to blur events and Keyup enter events for input, when I trigger keyup enter events, the blur events also be triggered

Element UI version
1.4.2
OS/Browsers version
macOS High Sierra 10.13 / chrome 66
Vue version
2.5.13
Reproduction Link
https://jsfiddle.net/Lnqpqogb/1/
Steps to reproduce

click the new tag button.
input something.
press return.
open the chrome devtools, you can see output 2 times the number 1.

What is Expected?

when I press return, only execute the kekup enter function.
when the focus is lost, only execute the loses focus function.

What is actually happening?

when I press return, both execute the keyup enter function and the loses focus function.
when the focus is lost, only execute the loses focus function.

This is how native input works, so there's not much we can do: https://jsfiddle.net/leopoldthecuber/Lnqpqogb/2/


Add support for modifying phases in adjust

Currently, I have something like this in my plan:
prepare:
  how: shell
  script:
   - systemctl disable --now dnf-makecache.service || true
   - systemctl disable --now dnf-makecache.timer || true

adjust:
  - when: distro == centos-stream-9
    prepare+:
       script+:
        - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm

  - when: distro == centos-stream-8
    prepare+:
       script+:
         - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm

This works. But to my knowledge it works only because my prepare block does not contain multiple "phases" (?).
Now, I would like to add another adjust similar to:
when: distro == fedora-26:
  prepare+:
    how: shell
    order: 99
    script:
      - yum -y downgrade tpm2-tss

so that my prepare ends up with two "phases", having different order. But to my knowledge this is not possible. It would be nice to have some way of doing that, e.g. by introducing new syntax or improving existing implementation.

We support multiple configs. While you will still not be able to 'adjust' selected 'config' you utilize the 'order' (default one is 50, configs are ordered by their order and then by their position).
prepare:
  - how: shell
    script:
    - systemctl disable --now dnf-makecache.service || true
    - systemctl disable --now dnf-makecache.timer || true

adjust:
  - when: distro == centos-stream-9
    prepare+:
    - how: shell
      script:
        - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm

  - when: distro == centos-stream-8
    prepare+:
    - how: shell
      script:
         - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm

  - when: distro == fedora-26
    prepare+:
    - how: shell
      order: 99
      script:
      - yum -y downgrade tpm2-tss

@lukaszachy  So instead of extending list of items within one script attribute I would be adding new scripts. Correct?

Yes. Prepare configuration will have list of item and you will be adding new item.

One way to approach it could be ability to assign some sort of "alias" or "id" to a particular phase and then refer to that phase in an adjust rule through when:
prepare:
  - how: shell
    alias: my-shell-prepare1
    script:
     - cmd1
     - cmd2

adjust:
  - when alias == my-shell-prepare1
    script+:
      - cmd3


Just some of my own needed changes

Sorry if this is alot, I plan to keep updating my end with the og.
Cheers and ty for making this plugin.

Ah uhm well no problem, but I am actually not updating this package anymore. Sorry about the misunderstanding, I’ve become a lot better at maintaining and organizing my packages over the past years but this one should technically be archived.
you may of course still use it however you see fit. You might also be interested in my docfx-unitypackage action, which generates documentation automatically when you push to main (or any branch of your choosing).


Mark tests that potentially fail

For the new Debian package, I found two tests that fail under some circumstances:

test_apply_manuever_correct_plane wants to retrieve some remotel data for Ceres,
test_plot_maneuver requires the numba "parallel" extension nor-existent on 32-bit (#1315)

This PR marks them properly.

Thank you @olebole ! Is this worth backporting to a 0.16.1 release if we ever make it?

I will apply this as a patch to the 0.16 sources when building the Debian package, so I don't need it myself.


expose constants because they are legit useful

we all had a talk about this and decided it wasn't a great idea #closed


README.md expand import examples

Proposal to expanded the README to what I was looking for to get started. Feel free to change.
I was also not sure what this sentence means:

Because the Iterator.prototype methods depend on a receiver (the this value), the main export in each subdirectory takes the string to operate on as the first argument.

Does it relate to explicit imports instead of shimming or is it an implementation detail?

It means that instead of forcing you to do, eg, require('es-iterator-helpers'/Iterator.prototype.drop').call(iterator, count), you'd do require('es-iterator-helpers'/Iterator.prototype.drop')(iterator, count). "The string" there is a mistake; it should be "the iterator".

Right, I mean I figured it out eventually what the require path was relative to, how to convert CJS to ESM and which module executed the shims automagically. But all three together were a bit many hurdles for my taste, hence this PR.
I pushed two commits (to make CI pass and to fix the typo you mentioned), so now it's ready to merge I think.

Removing evalmd is like deleting tests - the benefit of having an ESM example is much much smaller than the benefit of guaranteeing readme examples are correct.
That said, i think evalmd has an html comment way to ignore specific code blocks, so that might work here.

Done...


[MBL-783] Update PagginationErrorViewholderViewmodel to rx2

📲 What
Update PagginationErrorViewholderViewmodel to rx2
🤔 Why
We are so close
📋 QA
Make sure the app works as normal where pagination is concerned
Story 📖
MBL-783

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (master@97e6b10). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##             master    #1927   +/-   ##
=========================================
  Coverage          ?   74.23%
  Complexity        ?     1967
=========================================
  Files             ?      336
  Lines             ?    19597
  Branches          ?     2711
=========================================
  Hits              ?    14547
  Misses            ?     3466
  Partials          ?     1584

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix 'latlng' param

LatLng param wasn't converted to string before request. This causes 'Bad request' error

Thanks @bbldzr

Hi @tonydspaniard ,
This commit is not included in latest version(1.0.2).


Github issues and comment

Add functions to pull github issue and issue comments
Move iter_get to generic utils.py file so it can be used outside index.py

On my sample enterprise github, i was able to export 48,000 comments and issues in less than 3 minutes on my laptop.
Note - I looked into using gevent to do issues and comments in parallel but didn't see much improvement (if any) on the small sample set.  Need to investigate with a larger sample set.

looks good. manually merged, but didn't quite follow instructions properly, so this didn't close. I reverted the change on line 34 -  your settings file should just have the github api host, not the entire path.


Dont see zone support in supported region.

I have a APIM in au east. I tried to extend this to multiple zones. However for both an existing APIM instance and a newly created one, when I go to location, I cannot find capability to add zones like we see on this page.

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

ID: fb9d23f7-6741-bffa-af05-6efab2c633ed
Version Independent ID: 43000c12-513e-5ae3-5ee8-12c6f676d628
Content: Availability zone support for Azure API Management
Content Source: articles/api-management/zone-redundancy.md
Service: api-management
GitHub Login: @dlepow
Microsoft Alias: apimpm

@rajanbhayana Thank you for your feedback! We will review and update as appropriate.

@rajanbhayana Looks like the option is not yet available from the Azure portal as I can see the same observation for other regions. I have reached out to my team and I will update you once I heard back from them.

@rajanbhayana I have got an update from the team that the portal changes are not yet deployed. I am assigning this issue to the content author to update the document as appropriate.
@dlepow Can you help with this?

@rajanbhayana - Apologies for slow response to your issue. I believe the availability zones capabilities and regions described on this page are now up to date. Accordingly, I'll close this issue. Thanks for reaching out.
#please-close