Support rpm deployment

See original issue on GitLab
In GitLab by [Gitlab user @jjardon] on Dec 12, 2017, 20:12

In GitLab by [Gitlab user @Conan_Kudo] on Jan 3, 2018, 12:21
What exactly does this mean, from a BuildStream point of view?

In GitLab by [Gitlab user @tristanvb] on Jan 3, 2018, 13:13
[Gitlab user @Conan_Kudo] It basically means creating an rpm deployment kind of plugin, similar to the one we have in the bst-external repo for debian packages.
These will basically take the output artifact from a given module build, and consume public data from the given element to fill in any blanks needed to generate the package metadata.
This could arguably be filed against the bst-external repo directly, but then we'd just have all these bug trackers to keep track of flying around :)

In GitLab by [Gitlab user @Conan_Kudo] on Jan 3, 2018, 13:21
[Gitlab user @tristanvb] So this is different from supporting RPMs as input or building RPMs, then?

In GitLab by [Gitlab user @tristanvb] on Jan 3, 2018, 13:26
[Gitlab user @Conan_Kudo] It's different from supporting RPMs as input, but it is pretty much exactly "building RPMs"
For a package deployment plugin like this, naturally one needs to have the element which builds RPMs, depend on a runtime which provides rpmbuild, usually you want this runtime to match exactly the rpm based distro that you want to deploy to (this is not much different than using an autotools plugin, and assuming that the user is depending on a runtime that has tooling such as autoconf, automake and make).

In GitLab by [Gitlab user @Conan_Kudo] on Jan 3, 2018, 13:31
Well, at least for constructing environments and getting dependencies, you can use DNF on Fedora, Mageia (6+), and openSUSE (Tumbleweed and Leap 15.0), which means you also have a Python API to work with.
As for building RPMs, that should be relatively painless (assuming you want to translate YAML to a spec). If you want to "construct" the RPMs directly, that'd require wiring into librpm itself (probably through its Python bindings).
As for making repositories, there's createrepo_c unless you want to build the metadata yourself (which you could!).

In GitLab by [Gitlab user @tristanvb] on Jan 3, 2018, 13:45
Just noting here, it is not desirable to use host rpm, so there will be no dependency that a user have rpm installed on their host - every mutation in the BuildStream pipeline needs to happen inside the controlled sandboxed environment.
Yes, we generate a spec file from the YAML, specifically a rather lax and uncontrolled part of the YAML that we call "public data", and we feed that to whichever rpm mechanics exist in the controlled runtime (the python plugin is mostly responsible for interpreting that YAML, generating a spec file and invoking rpmbuild in the isolated build sandbox).
There is an earlier, more rigid version of this approach already in https://gitlab.com/baserock/ybd, which mostly does the right thing but certainly needs some tuning (for the purpose it is used now, it is currently used in some production systems and working well, but I expect it to break on corner cases).

In GitLab by [Gitlab user @Conan_Kudo] on Jan 3, 2018, 13:53
So does that mean you need to do your own dependency resolving and whatnot? Or are you going to grab a generic preinstall image to bootstrap from?
The way you do debs is through debootstrap, which implies that needs to exist on the system somehow.

In GitLab by [Gitlab user @tristanvb] on Jan 3, 2018, 14:32
Generally yes it implies that something like debootstrap should be employed to generate a consistent image for the runtime. This is not always the case with rpm based distros, take for instance those crazy tizen derived things that keep rearing their head... those usually come with tarball SDKs from their ISVs.
It's also perfectly possible to build everything from a tiny runtime, including the bootstrap of the compiler, build RPM itself and configure it how you want your distro to be, and then deploy everything you need for your entire custom distro after everything has been built, using your own custom built runtime as a base.
As long as host tools were not used, there are many ways to fry the cat...

In GitLab by [Gitlab user @Conan_Kudo] on Jan 3, 2018, 15:18
So as long as you can bootstrap up to DNF (or even just microdnf if I could figure out what I'm doing wrong in this PR), you should be able to pull this off for any arbitrary architecture.

In GitLab by [Gitlab user @tristanvb] on Mar 31, 2018, 10:38
changed title from {-[Feature Request] -}Support rpm deployment to Support rpm deployment

In GitLab by [Gitlab user @tristanvb] on Nov 4, 2020, 11:04
This is the wrong venue, an rpm generating plugin would be most welcome along side the deb plugins we have in the bst-plugins-experimental repo.


Update the software lifecycle table

The software lifecycle table needed an update considering both 0.15 and 0.16 have been released now

Concept ACK

'Release' and 'Maintenance End' dates look good. Where did you get the 0.13 EOL date?

Maybe ask in this weeks meeting if everyone is ok with that EOL?

@jnewbery I just tried to follow a similar pattern as the existing dates. Good idea to discuss in the meeting yep

Relevant discussion: https://botbot.me/freenode/bitcoin-core-dev/2018-03-22/?msg=98127132&page=5

utACK effded2ede4d6345b70212b845e5f59d6a8a3888

Added EOL date for 0.14 as per discussion, should be ready to go now then

utACK d7b21c152891de5d1b459b004700c3551296a544

utACK d7b21c1


Windows Design Improving

Good work, but I have a suggestion.
Why don't you make window bar and taskbar icon be like this?

also the system tray icon, I think it will be good in white and when you have a notification, it turns into blue.

thanks :)

I would like to see this happening. ♥

With the current framework we can't make that title bar, but I like your idea for the tray icon.
Please try the new beta I made.
More information here: https://github.com/Aluxian/Facebook-Messenger-Desktop/issues/458

Hey! Any updates on that try icon? It looks really bad on Windows 10:
http://i.imgur.com/MjozcUz.png
I can set you up with all the sizes of that official icon that you need, for some reason Windows 10 is still using the 16px icon for the taskbar icons. It's retarded, but I guess it could be fixed by simply adding the 16px icon.
The icon looks good at 125% DPI though!
http://i.imgur.com/1HwQ5Kk.png

Well I'm waiting on the main dev to see when he is going to move to MDF 2 (based on electron).
It annoys me to work on code that is going to be thrown away in a month or two...
 Good luck on your exams!


Fix sequelize/types/lib/hooks path

#1198  Problem solved.
'types/lib' folder was removed in sequelize verstion >= 6,
test/specs/instance.spec.ts file edit - Model.reload() method is return Model,
Deprecated: Operator Aliases

@mystylelee This won't work because up to version 6.15.1 it's still using the old paths.

@lukashroch do we have a target date for when this will be released?

@stanleynguyen I've opened a PR to push out a release. So hopefully soon.


Not able to apply hide Expression for multicheckbox type field ,

Hello ngx-formly team ,
Its request from you to please give me solution for this requirement :
Q: I want to apply hideExpression for multicheckbox type fields option , But its not working . I am able to achieve the result using hideExpression if the field is radio , select , but not able to do with multicheckbox .
Here is detailed Explanation:
Question : I want to show the field with labled "show me ", , when user selects option one(1) from multicheckbox , but hideExpression is not working
My code : Its NOT working with multicheckbox but working with radio
export class AppComponent {
form = new FormGroup({});
model = {};
fields: FormlyFieldConfig[] = [
{
key: 'multicheckbox',
type: 'multicheckbox',
props: {
label: 'Multicheckbox',
required: true,
options: [
{ label: 'Option 1', value: '1' },
{ label: 'Option 2', value: '2' },
],
},
},
{
key: 'showme',
type: 'input',
props: {
label: 'show me',
placeholder: 'Input placeholder',
required: true,
},
hideExpression: "!(model.multicheckbox['1'] ===  true)"
},
];
}
working code with radio:
fields: FormlyFieldConfig[] = [
{
key: 'radio',
type: 'radio',
props: {
label: 'Radio',
required: true,
options: [
{ label: 'Option 1', value: '1' },
{ label: 'Option 2', value: '2' },
],
},
},
{
key: 'showme',
type: 'input',
props: {
label: 'show me',
placeholder: 'Input placeholder',
required: true,
},
hideExpression: "!(model.radio ===  '1')"
},
];

@aitboudad pls provide solution

@kenisteward @beeman pls core team help me

sorry by mistake I closed that

@Rishabh-Yadav-12 if u got solution to your issue plz help me as i am also facing similar issue, my id: singhnitin354 @ gmail . com


update postinstall to use sh shell for wider compatibility

Some Linux systems and Docker Images (Ubuntu, Debian, and Alpine for example) don't come with Zsh Shell out of the box, the only shell in common between macOS, Linux(and it's all variant) is Sh Shell so I update the script to use Sh instead of Zsh for wider compatibility.

I really dislike sh, it’s very lacking. Is there no way to somehow disable the package on non-macOS targets in npm?

Bash should also be fine.
This script is relatively small. I wonder in general.

We using sh just for a small check for the OS type, we are not using sh to write logic,
and to make sure you support all kinds of OSs you're going to run your package on you should use the common language between them all, and I think sh would be our choice here,
Or we can use Bash as you said, but use the syntax with POSIX compatibility.

@LeoNatan I have updated it to use bash instead, but I made the check to be compatible with older shells too for POSIX standard

Using #!/usr/bin/env bash will result in env searching your $PATH for any version of bash it can find. This means whether bash is at /bin/bash, /usr/local/bin/bash, or anywhere else, you’ll be able to correctly call bash and use them there bashisms to your heart’s content!

@LeoNatan Hey Leo is there any updates about this PR,
I just wanted to know your decision about this PR, as right now my CI still down because I can't do yarn install
I have changed it back to Bash as you requested, I also searched for a way to disable the package on non-macOS targets in npm but unfortunately, I haven't found any so please keep me updated with your decision, or let me know what you want me to do so I can get that PR to merge 😄

Hey, it’s Saturday! 😉
What Linux distro comes without Bash? And is such a distro even worth supporting? 😈

Thanks
I’ll release soon.

1.0.148 out
Please try

@LeoNatan Thanks a lot Leo, it works but I had to move my docker image from alpine to debian based as alpine come with sh only and it raises an error as it can't fine bash
Command: ./postinstall.sh
Arguments:
Directory: /var/lib/jenkins/workspace/n-App-Login-page-Mobile-DMS-2998/node_modules/detox-recorder
Output:
env: can't execute 'bash': No such file or directory

as using #!/usr/bin/env bash make sure the script running using bash without fallbacks, once I moved into debian based it works as it should.
usually, I use alpine as they are small in size and save a lot of time downloading the image and storage
but that's good for now I can keep my CI up and running. Thanks

Ufff, this is ridiculous. 🤦♂ Fine, submit a PR with sh and I'll put that. The script is so small, it doesn't matter.

How big is bash that they don't add it? Is this some Linux snobbery?

I'll just edit the file myself. Thanks

1.0.149 with sh

@LeoNatan Thanks a lot, now it's working like a charm with alpine too, my CI back to the game right now with no errors at all.
Thanks.

BTW, how is Detox Recorder working for you? 😂

@LeoNatan Actually it works really well so far, Thanks so much for this, sometimes I need to edit the test a bit as it has some redundant steps especially when I am typing for example when I want to write username:
    await element(by.text('u')).atIndex(0).replaceText('u');
    await element(by.text('us')).atIndex(0).replaceText('us');
    await element(by.text('use')).atIndex(0).replaceText('use');
    await element(by.text('user')).atIndex(0).replaceText('user');
    await element(by.text('usern')).atIndex(0).replaceText('usern');
    await element(by.text('userna')).atIndex(0).replaceText('userna');
    await element(by.text('usernam')).atIndex(0).replaceText('usernam');
    await element(by.text('username')).atIndex(0).replaceText('username');

also, I have noticed a strange thing when I put the command in package.json to use yarn to fire the command it doesn't work
but if I write the command in the terminal directly it works as expected.

Not sure what is going on. Could be that yarn breaks some environment. The Detox CLI simply forwards arguments to the binary when calling detox recorder:
https://github.com/wix/Detox/blob/7c8b0864879c35d4e3b8c6d4b7e347e2cb1b960b/detox-cli/cli.js#L48
If you want to debug, you can run a logger by calling
log stream --level debug --style compact --predicate "subsystem=='DetoxRecorder'"

and then the yarn command, and post here the output. Thanks

The reason I use replaceText instead of, say typeText is because in the UI you can select any insertion point with the cursor, while with Detox we don't have that control. Perhaps I can coalesce multiple replaceText calls in to a single one, the last one.


fix: Do not run as root, use read-only filesystem

Note: The docker image artifacts had to be moved from image/ to docker/
because the "image" name is somehow special to "docker build", ADD
commands were not working from there.
Fixes #39

/lgtm
/approve


Pools payment on mainnet doesn't charge pools and takes a lot of time

Fails to extend pool
pool: https://explorer.grid.tf/api/v1/reservations/pools/3943
payment: https://explorer.grid.tf/api/v1/reservations/pools/payment/3943
Payment is paid and released but didn't charge cu, su units

Update: It charged the units after around 2 hours :)

is this the same issue or not? https://github.com/threefoldtech/tf_operations/issues/199

@sabrinasadik  It's the cause for the 3Bot deployment timeout, Pools extension is failing

Can someone please explain what the problem here is and why it's still not resolved?

Explorer has been updated to query multiple txes per call, and stellar horizon server is behaving properly again, pools now behave as expected.

https://explorer.devnet.grid.tf/api/v1/reservations/pools/13549

https://explorer.devnet.grid.tf/api/v1/reservations/pools/13551

It seems to be related to horizon, since we are now running our own instance, but more importantly since we are moving to v3, I'll close this again.


Correct the namespace of MockNamespaceTest

The namespace of MockNamespaceTest class did not comply with psr-4 autoloading standard. Leaving the class with incorrect namespace would cause it to not be autoloaded  in Composer v2.0.

@malkusch can you please merge this PR.

@michalbundyra Looks a bit more active in this repo.
Could you merge this?

@yoeriboven I am the only maintainer right now. I knew about this issue and will solve it soon. Thanks!

@yoeriboven I am the only maintainer right now. I knew about this issue and will solve it soon. Thanks!

Thank you :)

@hhovakimyan
sorry, but it does not solve the problem, try:
{
    "name": "test/package",
    "require": {
        "php-mock/php-mock": "dev-master"
    },
    "repositories": [{"type":"git","url":"https://github.com/hhovakimyan/php-mock.git"}]
}

and run:
composer install -o

you will still see the same deprecation notice:
Deprecation Notice: Class phpmock\tests\MockNamespaceTest located in ./vendor/php-mock/php-mock/tests/MockNamespaceTest.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:201

Namespace in tests is very confusing at the moment. We should clear it out a bit in general. DO you want to help? Thanks.

@hhovakimyan I've updated the namespace, and it works now as expected. Thanks!

Great! Although I don't understand the solution. You got any idea why this works or were you just trying things out and this seemed to work?

@yoeriboven it works because composer do not care about other namespaces than defined (at least for now). And these are just test classes autoloaded by PHPUnit, so all tests are the same.
I do not like this solution, but this is the quickest/easiest for now. We will see what is gonna happen with "next" composer version, so we might need more changes there.

@yoeriboven @hhovakimyan I've reported issue to composer: https://github.com/composer/composer/issues/8801 we will see if there will be any response about it. Probably we would need to fix more tests here, but let see what they are gonna say. Thanks for reporting again. So far you can use 2.2.2 without deprecation notice.


Signed CA is missing CN value breaking ability to trust for SSL on iOS devices

The PEM file generated by Warden during the install process for signing certificates used by Traefik is lacking a CN value thus breaking the ability to install the certificate as a profile and then trust the certificate on iOS devices. Opening the PEM on iOS currently results in an installed profile, but the certificate is not showing up in the list of certificates to be trusted for SSL after installing as a profile.
The following forum thread appears to describe this exact scenario, and indicates the lacking CN value as the culprit: https://forums.developer.apple.com/thread/89568
Information in forum thread should be validated, and the install routine corrected appropriately. As regenerating a CA would require re-signing already present certificates, the regeneration will be left a manual process (cleanup files, run warden install, etc) and I will plan to call this out in release notes once fixed.
Another example of this iOS peculiarity cropping up can be found here: https://github.com/FiloSottile/mkcert/issues/47
The following KB page documents how one is expected to trust a CA for SSL on iOS devices: https://support.apple.com/en-us/HT204477

For those needing to re-create CA root and re-issue certificates, the following process should be followed:

Remove existing trusted certificate
a) macOS/Darwin
sudo security remove-trusted-cert -d ~/.warden/ssl/rootca/certs/ca.cert.pem

b) Fedora/CentOS
rm /etc/pki/ca-trust/source/anchors/warden-proxy-local-ca.cert.pem

c) Ubuntu/Debian
rm /usr/local/share/ca-certificates/warden-proxy-local-ca.crt

Cleanup all issued certs and CA root files
rm -rf ~/.warden/ssl

Re-create and trust new CA
warden install

Re-issue SSL certificates as needed via warden sign-certificates ...

Following changes in associated PR, the Warden issued CA now shows up for trusting on iOS devices:


Draft: runnable default codeblocks

This PR aims at providing default runnable codeblocks to the user (i.e addressing #148)
Checklist:

[ ] I've added Google style docstrings to my code.
[ ] I've used pydantic for typing when/where necessary.
[ ] I have linted my code
[ ] I have added tests to cover my changes.

Other note @JulesBelveze it looks like dslim/bert-base-NER has been trained on that sample.conll (at least as far as i can tell from testing it with nlptest). Can you look into ROI for using a small sample from ontonotes instead? https://huggingface.co/datasets/conll2012_ontonotesv5
It might not be worth the time invested, let me know if you think we should stick to that sample.conll


twister: Always change skip to error on integration platforms

Before only with --integration such skips were changed to errors. This hinders issues when twister is call with --all flag in CI and new skips on integration platforms are not caught. Then those skips cause errors in other PRs when --integration was used.

This change prevents issues like this:
https://github.com/zephyrproject-rtos/zephyr/issues/62380

you need to fix the testsuite.


SPFx : ACE : Unable to get cached state

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
No response
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[X] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

SPFx version 1.14 / 1.14.0-beta.5

Describe the bug / error
As per the documentation, "we should be able to get the cached state of an ACE in onInit method so that we can determine if further logic needs to be executed."
This would be useful when we perform an async operation to get the initial state which might not change frequently (e.g. values from a termset).
After following the instructions in the documentation, I can see the state being cached

However, the value of cachedLoadParameters in the onInit method is always undefined.

Can you please confirm if that should not be the case?
Steps to reproduce

Please clone the repo here

Note - Although it is using packages related to 1.14.0-beta.5 the issue can be seen in 1.14.0

Run gulp serve
Add the ACE on to a page
For second page load onwards, I am expecting this line to show the cached value however that is not the case.

Expected behavior
For second page load onwards, I am expecting this line to show the cached value however that is not the case.

Hi @anoopt , sorry for the late reply. Looking at your code, it looks like cacheLoadParameters are empty. Which is odd considering your local storage contains the ACE cached state. Is this still reproducing?

Hi @dennisjsyi in the latest SPFx version 1.15.2 I see that ICachedLoadParameters and ICacheSettings are excluded from @microsoft/sp-adaptive-card-extension-base package.

The release notes say that the caching functionality should be available in 1.16.

Is there any other way of testing this?

@anoopt - as this is still a beta API you should use beta versions of SPFx. Currently it's 1.15.0-beta.6 which is a bit behind 1.15.2 in terms of available features.
We're working on the 1.16.0 beta to be released in a few weeks.

Thank you @AJIXuMuK . I'll wait for 1.16.0 beta and test this functionality.

Hi @AJIXuMuK and @dennisjsyi . I can see that state is being cached in an ACE created with 1.16.0
However, on alternative page load the cache (cachedState) is getting cleared. Please find below the implementation. Can you please let me know if that is as per the documentation?
First page load

Following page load

The above repeats.
import { BaseAdaptiveCardExtension, ICachedLoadParameters, ICacheSettings } from '@microsoft/sp-adaptive-card-extension-base';
import { isEmpty } from '@microsoft/sp-lodash-subset';
...
...
public onInit(cachedLoadParameters?: ICachedLoadParameters): Promise<void> {

    console.log("cache - onInit - %o", cachedLoadParameters);

    //Expecting this to be false for every page load after the first one
    if (isEmpty(cachedLoadParameters.state?.title)) {

      console.log("cache - state empty");

      this.state = {
        title: 'Setting from onInit'
      };
    }

    this.cardNavigator.register(CARD_VIEW_REGISTRY_ID, () => new CardView());
    this.quickViewNavigator.register(QUICK_VIEW_REGISTRY_ID, () => new QuickView());

    return Promise.resolve();
  }
protected getCacheSettings(): Partial<ICacheSettings> {
    return {
      isEnabled: true, // can be set to false to disable caching
      expiryTimeInSeconds: 86400, // controls how long until the cached card and state are stale
      cachedCardView: () => new CardView() // function that returns the custom Card view that will be used to generate the cached card
    };
  }

  protected getCachedState(state: IHw116AdaptiveCardExtensionState): Partial<IHw116AdaptiveCardExtensionState> {
    console.log("cache - getCachedState - %o", state);

    return { title: state.title };
  }
...
...


Using i18n of releases/builds

How can the i18n of releases/builds be used? Neither the readme nor the Wiki nor the --help command line argument seem to give a hint how to switch to another language.

This isn't supported officially yet...
But You can set it on the command line via JVM parameters:
java -Duser.country=DE -Duser.language=de -jar epubcheck.jar ...

Perhaps a --language (or --lang or whatever) command line parameter would be adequate. If not specified, the tool should use the current locale as it does now (which can be specified via -Duser.language=xx).

Good idea! :)

This will probably be implemented with PR #650 in near future.


Update Five-seveN Sprite

Please see CONTRIBUTING.md first.
This is an update issue. This means that somebody has already created a sprite for this item. After a while, an update issue is automatically generated for improvement purposes. You can either enhance the original sprite, or create one from scratch!
Reference sprite:

Happy Hacking! :smiley:

I'll try my best. ;)

Great! Thank you. :smiley:


Set a name for parts / the default scale in the output file

I think that OpenCascade allows you to set the scale of the file (eg. meters or milimeters), when exporting to STEP / STL, is there a way to set that from replicad?
Also wondering if there's a way to go through all the parts and give them colors / names ?

I think that OpenCascade allows you to set the scale of the file (eg. meters or milimeters), when exporting to STEP / STL, is there a way to set that from replicad?

No, I have not exposed them now (but I don't see any reason on the top of my head not to).

Also wondering if there's a way to go through all the parts and give them colors / names ?

You can give the parts within the workbench some names and colors, but this is not done at the opencascade layer (and will not be shown in the STEP file). Not sure how I would expose that though.

BTW what's the proper way to access the Opencascade.js underlying implementation from Replicad, and the meshes? I'm not sure exactly how the wrapper is built and how I can call Opencascade.js functions if needed?

The getOC function returns the opencascade object that you can use directly.

Very cool!! Thanks a lot!


Nib

Hi,
I installed your lib with cocoa pods but the nibs are missing.
Thank you to push them in the future

Hi!
It's finally fixed! Thanks to @alimashuri


Swaps with missing "from" and/or "to" branches

Swaps endpoint sometimes returns swaps with missing "to" branches and even missing "from" branches. E.g. on this page (https://ocean.defichain.com/v0/mainnet/poolpairs/61/swaps/verbose?next=001d4b1200000033), txid d7a8807bc3e0aebf5db4b7cd392698a3e3213a2b33738091bf085b24b2d760fb

Duplicate of https://github.com/JellyfishSDK/jellyfish/issues/1487 where some snapshotted nodes don't have all the account history.
Issue expected to be fixed by v3.0 of node release.

/area packages
/apps whale-api
/kind bug

Closing as this should be fixed with https://github.com/DeFiCh/ain/releases/tag/v2.9.3


Automated Package Upgrade

:tada: This PR is included in version 2.0.10 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Eligibility Questionnaire] Elderly and Special Needs eligibility filtering data and product questions

Outstanding product questions and verification we need to do:

Data verification: Verify that "elderly" and "special needs" are eligibility requirements for each of the properties in the corresponding HUD compliant group. I did a cursory search of a couple of properties and the information is available online. We may need to call the properties if the information is not available online.

Data verification: Verify which other non-HUD properties have "elderly" and "special needs" as a requirement. This can involve an online search or phone calls to the property.

Data verification: Determine the age threshold for each "elderly" property (62 or 55).

Data verification: Are there any properties that require you to be both elderly and have a disability to apply?

Product question: Do we want to have a special category for partially elderly properties?

Product question: Do we want to have more specific categories for "special needs" properties? Some are specific to people with a mobile impairment or mental illness.

See #317 for more information

Responding to Product Questions:
Product question: Do we want to have a special category for partially elderly properties?
Response: Yes please, confirming, let's add a separate category of 'partially elderly' (or similar to match existing naming convention) to indicate to the resident that it's not an entirely senior-living facility.
Product question: Do we want to have more specific categories for "special needs" properties? Some are specific to people with a mobile impairment or mental illness
Response: How often is this specification called out in data collection? Given this level of information may not be available for all propertied, my recommendation is to keep a generic 'special needs' category, but to include specifics in the unit summary description, where specifics exist. @elenm please let me know if you disagree or have another suggested workaround. Thanks!
@elenm do you need assistance unblocking the data questions with HRD? Happy to assist.

I sent the list of properties over to Safiya that need verifying and I believe the intention was to verify the age threshold and whether these are requirements for the communities or preferences.

Thanks Kar! I'm assuming we also want to add filtering for the partially elderly properties? Should we add it as another community type in the filtering modal?

Yes, let's try the following options:

Community Type > All
Community Type > 'Varied housing (including senior 62+ options)'
Community Type > 'Senior housing (62+ only)'
Community Type > 'Special Needs and disability'

@tomgebauer @elenm open to feedback on language use on 2 and 3


cmake: Check if Fortran compiler is usable before enabling it.

When configuring with cmake -DBUILD_WITHOUT_LAPACK=ON, the Fortran compiler is forced to be gfortran. That causes the configuration (for the tests) to fail if no Fortran compiler is installed.
I don't understand why the compiler is forced to gfortran in that case. Afaict, that shouldn't be necessary.
The proposed change lets the build system check if a Fortran compiler is available before using it.

Yeah, this is some oddity left over from GotoBLAS (which then got faithfully translated to cmake syntax - only I suspect in the gmake case setting NOFORTRAN=1 is a stronger deterrent for the tests). Probably some higher-order cleanup should be done (could be the dummy compiler entry is just created to avoid syntax errors from half-empty statements in the original f_check script).

Just to clarify: Is the higher-order cleanup you are hinting at a prerequisite for this PR? The proposed change works for me. But I might be missing something.

No, just a note to myself...


HHH-15495 - add test case

Thanks. Superseded by https://github.com/hibernate/hibernate-orm/pull/5284


Fix 04_controlling_mix runtime

I saw that only https://github.com/rive-app/rive-flutter/commit/66305cb511f4787c3b6cecb09c15b18bd9c5149d exposed the mix, which is required for the 04_controlling_mix example.
I think that until that version is published, we want to use a Git dependency, so that others are able to run the example easily :)

Thanks for catching that; the latest version is published and there's a PR up to fix the pubspec.


[Snyk] Upgrade @playwright/test from 1.42.1 to 1.43.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @playwright/test from 1.42.1 to 1.43.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 48 versions ahead of your current version.
The recommended version was released 22 days ago, on 2024-04-04.

Release notes

Package name: @playwright/test

1.43.0 - 2024-04-04New APIs

Method browserContext.clearCookies() now supports filters to remove only some cookies.
// Clear all cookies.
await context.clearCookies();
// New: clear cookies with a particular name.
await context.clearCookies({ name: 'session-id' });
// New: clear cookies for a particular domain.
await context.clearCookies({ domain: 'my-origin.com' });

New mode retain-on-first-failure for testOptions.trace. In this mode, trace is recorded for the first run of each test, but not for retires. When test run fails, the trace file is retained, otherwise it is removed.
import { defineConfig } from '@ playwright/test';
export default defineConfig({
use: {
trace: 'retain-on-first-failure',
},
});

New property testInfo.tags exposes test tags during test execution.
test('example', async ({ page }) => {
  console.log(test.info().tags);
});

New method locator.contentFrame() converts a Locator object to a FrameLocator. This can be useful when you have a Locator object obtained somewhere, and later on would like to interact with the content inside the frame.
const locator = page.locator('iframe[name="embedded"]');
// ...
const frameLocator = locator.contentFrame();
await frameLocator.getByRole('button').click();

New method frameLocator.owner() converts a FrameLocator object to a Locator. This can be useful when you have a FrameLocator object obtained somewhere, and later on would like to interact with the iframe element.
const frameLocator = page.frameLocator('iframe[name="embedded"]');
// ...
const locator = frameLocator.owner();
await expect(locator).toBeVisible();

UI Mode Updates

See tags in the test list.
Filter by tags by typing @ fast or clicking on the tag itself.
New shortcuts:

F5 to run tests.
Shift F5 to stop running tests.
Ctrl ` to toggle test output.

Browser Versions

Chromium 124.0.6367.29
Mozilla Firefox 124.0
WebKit 17.4

This version was also tested against the following stable channels:

Google Chrome 123
Microsoft Edge 123

1.43.0-beta-1712871607000 - 2024-04-11

1.43.0-beta-1712860105000 - 2024-04-11

1.43.0-beta-1712646596000 - 2024-04-09

1.43.0-beta-1712258732000 - 2024-04-04

1.43.0-beta-1712217576000 - 2024-04-04

1.43.0-beta-1712173949000 - 2024-04-03

1.43.0-beta-1712010778000 - 2024-04-01

1.43.0-beta-1711849714000 - 2024-03-31

1.43.0-beta-1711742093000 - 2024-03-29

1.43.0-beta-1711653598000 - 2024-03-28

1.43.0-beta-1711554436000 - 2024-03-27

1.43.0-beta-1711493485000 - 2024-03-26

1.43.0-beta-1711484700000 - 2024-03-26

1.43.0-beta-1709675102000 - 2024-03-05

1.43.0-alpha-2024-03-26 - 2024-03-26

1.43.0-alpha-2024-03-25 - 2024-03-25

1.43.0-alpha-2024-03-24 - 2024-03-24

1.43.0-alpha-2024-03-23 - 2024-03-23

1.43.0-alpha-2024-03-22 - 2024-03-22

1.43.0-alpha-2024-03-21 - 2024-03-21

1.43.0-alpha-2024-03-20 - 2024-03-20

1.43.0-alpha-2024-03-19 - 2024-03-19

1.43.0-alpha-2024-03-18 - 2024-03-18

1.43.0-alpha-2024-03-17 - 2024-03-17

1.43.0-alpha-2024-03-16 - 2024-03-16

1.43.0-alpha-2024-03-15 - 2024-03-15

1.43.0-alpha-2024-03-14 - 2024-03-14

1.43.0-alpha-2024-03-13 - 2024-03-13

1.43.0-alpha-2024-03-12 - 2024-03-12

1.43.0-alpha-2024-03-11 - 2024-03-11

1.43.0-alpha-2024-03-10 - 2024-03-10

1.43.0-alpha-2024-03-09 - 2024-03-09

1.43.0-alpha-2024-03-08 - 2024-03-08

1.43.0-alpha-2024-03-07 - 2024-03-07

1.43.0-alpha-2024-03-06 - 2024-03-06

1.43.0-alpha-2024-03-05 - 2024-03-05

1.43.0-alpha-2024-03-04 - 2024-03-04

1.43.0-alpha-2024-03-03 - 2024-03-03

1.43.0-alpha-2024-03-02 - 2024-03-02

1.43.0-alpha-2024-03-01 - 2024-03-01

1.43.0-alpha-2024-02-29 - 2024-02-29

1.43.0-alpha-2024-02-28 - 2024-02-28

1.43.0-alpha-1711470013000 - 2024-03-26

1.43.0-alpha-1711027602000 - 2024-03-21

1.43.0-alpha-1710520846000 - 2024-03-15

1.43.0-alpha-1709847741000 - 2024-03-07

1.43.0-alpha-1709823751000 - 2024-03-07

1.42.1 - 2024-03-02Highlights
#29732 - [Regression]: HEAD requests to webServer.url since v1.42.0
#29746 - [Regression]: Playwright CT CLI scripts fail due to broken initializePlugin import
#29739 - [Bug]: Component tests fails when imported a module with a dot in a name
#29731 - [Regression]: 1.42.0 breaks some import statements
#29760 - [Bug]: Possible regression with chained locators in v1.42
Browser Versions

Chromium 123.0.6312.4
Mozilla Firefox 123.0
WebKit 17.4

This version was also tested against the following stable channels:

Google Chrome 122
Microsoft Edge 123

    from @playwright/test GitHub release notes

Commit messages

Package name: @playwright/test

7c7f8ac cherry-pick(#30227): chore(deps): bump vite from 5.0.12 to 5.0.13 (#30254)
62d4dc9 cherry-pick(#30235): feat(chromium): roll to r1112
79d4776 cherry-pick(#30226): chore: migrate to the testserver.initialize
6b94231 cherry-pick(#30202): do not run setup tasks on test run via server
0889736 cherry-pick(#30185): chore: opt into stdio forwarding
a01db3f chore: mark version 1.43.0 (#30183)
1cd1239 cherry-pick(#30170): chore: hide internal commands
122ab67 cherry-pick(#30138): fix: UI Mode tags without theme applied
75776db cherry-pick(#30135): chore: do not exit UI mode upon page reload
757f308 docs: release notes 1.43 for js (#30128)
021c5c1 chore: revert support of duplicate form data fields in multipart post data (#30127)
e4403dd fix(chromium): race between requestPaused and requestWillBeSent in workers (#30125)
dd1eca2 fix(trace viewer): show correct number of pages without screencast (#30124)
0bf635e chore: ensure max failures exit yields erroneous status code (#30120)
c27ec77 docs(test-projects-js.md): fix typo in "Test filtering" section (#30114)
2de8a6b chore: move filter params into the clearCookies (#30111)
1824ba1 feat(chromium-tip-of-tree): roll to r1205 (#30119)
397244c test: add a test for disabled cache with context-wide request interception (#30072)
599185d feat(ui-mode): show native tags in test tree (#30092)
051afb9 fix(test runner): update fixture teardown error message (#30109)
8e27d67 feat(webkit): roll to r1992 (#30110)
65d8279 fix(ct): ct ID clash on similar imports (#30108)
7039ad0 chore: follow up to the api review for test server (#30097)
a849ea9 feat(fetch): multiple fields with the same name in post data (#30104)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Superseded by #245


New player stats method (Get stats by match)

https://docs.faceit.com/docs/data-api/data/#tag/Players/operation/getPlayerStats <- this endpoint

v0.0.2 released with this PR


Updates the DragDrop Example

The DragDrop example was throwing an error as soon as you triggered the mouseUp.
I've fixed the example, and added comments to it.

Codecov Report

Merging #52 into master will not impact coverage.

@@           Coverage Diff           @@
##           master      #52   +/-   ##
=======================================
  Coverage   93.12%   93.12%
=======================================
  Files          44       44
  Lines         887      887
=======================================
  Hits          826      826
  Misses         61       61

Continue to review full report at Codecov.

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


Readme issue

Please fix the issue in the readme
import retina from 'retinajs'; should be import retina from 'retinajs';
https://monosnap.com/file/5kyKL4YuAufNvWIHK5rhzfllesPwLM
also put somwhere npm install retinajs otherwise you may think that you need to npm install retina which is wrong. I spent 15 minutes to guess where is the mistake.

Plus one on this. I spend about 3 hours (!) to find this mistake...


How to add the icon on the angular gantt header?

I have a scenario to add an icon on the Angular Gantt headers. I tried multiple blogs. But could not find the solution.
Actually I followed the steps by the below link.
https://github.com/angular-gantt/angular-gantt/issues/356
Code snippet:
mainApp.controller('CustomHeaderController', function ( $scope, Service) {
var promise = Service.SpecialDays();
promise.then(function (resp) {
$scope.SpecialDayList = resp.data;
});
$scope.dispImageOnHeader = function (date) {  //same date is returning
$scope.data1 = $scope.SpecialDayList;
var chk = 0;
if ($scope.data1 != undefined) {
$.each($scope.data1, function (idx, item) {
var t = date.substring(0, 10);
if (t == item) {
chk = 1;
}
});
        if (chk == 1)
            return "custom-task11";
        else
            return "";
    }

}

}
Any help would be appreciated?
Thanks..

I fixed myself. The problem was that I was getting the value from date._i instead of date._d property from the javascript.
{{::column.label}}\n
mainApp.controller('CustomHeaderController', function ( $scope, Service) {
var promise = Service.SpecialDays();
promise.then(function (resp) {
$scope.SpecialDayList = resp.data;
});
$scope.dispImageOnHeader = function (date) { //same date is returning
$scope.data1 = $scope.SpecialDayList;
var chk = 0;
if ($scope.data1 != undefined) {
$.each($scope.data1, function (idx, item) {
var t = date.substring(0, 10);
if (t == item) {
chk = 1;
}
});
if (chk == 1)
return "custom-task11";
else
return "";
}
}
}


SyntaxError in iOS 8: Const declarations are not supported in strict mode

Version
4.5.8
Environment info
  System:
    OS: Windows 10 10.0.18362
    CPU: (4) x64 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
  Binaries:
    Node: 12.19.0 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.11.3 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 86.0.4240.183
    Edge: Spartan (44.18362.449.0)
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.0-rc.2
    @vue/babel-plugin-jsx:  1.0.0-rc.3
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  4.5.8
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1
    @vue/babel-sugar-composition-api-render-instance:  1.2.4
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  4.5.8
    @vue/cli-plugin-babel: ~4.5.0 => 4.5.8
    @vue/cli-plugin-eslint: ~4.5.0 => 4.5.8
    @vue/cli-plugin-router:  4.5.8
    @vue/cli-plugin-vuex:  4.5.8
    @vue/cli-service: ~4.5.0 => 4.5.8
    @vue/cli-shared-utils:  4.5.8
    @vue/compiler-core:  3.0.2
    @vue/compiler-dom:  3.0.2
    @vue/compiler-sfc: ^3.0.0 => 3.0.2
    @vue/compiler-ssr:  3.0.2
    @vue/component-compiler-utils:  3.2.0
    @vue/preload-webpack-plugin:  1.1.2
    @vue/reactivity:  3.0.2
    @vue/runtime-core:  3.0.2
    @vue/runtime-dom:  3.0.2
    @vue/shared:  3.0.2
    @vue/web-component-wrapper:  1.2.0
    eslint-plugin-vue: ^7.0.0-0 => 7.1.0
    vue: ^3.0.0 => 3.0.2
    vue-eslint-parser:  7.1.1
    vue-hot-reload-api:  2.3.4
    vue-loader:  15.9.5 (16.0.0-rc.0)
    vue-style-loader:  4.1.2
    vue-template-es2015-compiler:  1.9.1
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce
I have a fresh installation of Vue using vue create app
In package.json  in browserslist I have ios >= 8. Command npx browserslist lists all ios safari browsers from 8 to 14.
After running npm run build, babel doesn't seem to transpile const in strict mode to var.
In iOS 8 I get SyntaxError: Unexpected keyword 'const'. Const declarations are not supported in strict mode.
What is expected?
Babel will take into account browserslist setting from package.json and transpile code to be used in listed browsers, so const will be changed to var, and there will be no error in iOS 8
What is actually happening?
In .js files in dist folder, const variables are not changed to var, error is showing up in iOS 8

I believe Vue 3 doesn't support iOS 8 yet. As the Proxy object is not available until iOS 10 https://caniuse.com/?search=Proxy


BIGTOP-2603: NN/RM charm should include a spark user/group

When NN/RM are not colocated with spark, they do not know about the spark user/group.  When in yarn-client mode, the spark charm will create hdfs dirs with spark ACLs.  This leads to warnings like this on the namenode:
WARN org.apache.hadoop.security.UserGroupInformation: No groups available for user spark
Always create the spark user/group on NN and RM.  This also works if spark/NN/RM are all colocated.
Note that hadoop should be a secondary group (not primary) for extra users created by these charms, so this PR ensures that as well.

LGTM +1 . Do you think we should be doing the same with other components that may use hdfs, like hbase?

Yeah, we probably should.  oozie and hue come to mind.  We chatted about this a little while ago.  It would really be nice if the charm that relied on hadoop-plugin would send user info over the plugin relation.
The plugin would then proxy that to the NN or RM as needed.  Unfortunately, this isn't really a priority at the moment, so I think we'll treat spark as special for now and work up a more generic solution later.


Color time difference white for tied timeruns

Is this handled on game side already? Iirc there a string handling code there as well.

Seems like it is, but it's using z as color.
https://github.com/etjump/etjump/blob/3efd0421d1c1463bd76500af92521d5ba6907f3a/src/game/etj_timerun.cpp#L311


Remove Crossplane from upstream community operators

Opening this PR as a maintainer of upstream Crossplane. We do not maintain this entry anymore. Upbound maintains a distribution of Crossplane, which is being added in https://github.com/operator-framework/community-operators/pull/3859
Upstream variant of https://github.com/operator-framework/community-operators/pull/3858
Thanks submitting your Operator. Please check below list before you create your Pull Request.
Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@kasey, @displague since you are previous contributor, can you have a look at changes if ok with you?

/merge possible

Crossplane has certainly evolved a bit since it was introduced here. I know that I don't have the bandwidth to continue the maintenance of this integration.
Assuming all of the guidelines for removing a package have been met, this looks good to me.  Existing users should be encouraged to adopt another form of installation or reintroduce this package with the Crossplane 1.2+ 🚀


[release-1.8] trigger push when networks change

Manual cherrypick required.
#30070 failed to apply on top of branch "release-1.8":
Applying: trigger push when networks change
Applying: add reason
Applying: lint
Applying: e2e unit test
Using index info to reconstruct a base tree...
M	pilot/pkg/model/push_context.go
M	pilot/pkg/serviceregistry/kube/controller/fake.go
M	pilot/pkg/xds/fake.go
Falling back to patching base and 3-way merge...
Auto-merging pilot/pkg/xds/fake.go
CONFLICT (content): Merge conflict in pilot/pkg/xds/fake.go
Auto-merging pilot/pkg/serviceregistry/kube/controller/fake.go
Auto-merging pilot/pkg/model/push_context.go
CONFLICT (content): Merge conflict in pilot/pkg/model/push_context.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0004 e2e unit test
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

@stevenctl can this be closed?

I need to wrap up a manual cherry pick. If we're not releasing another 1.8 then yes it can.

I think we are not doing another 1.8


About ape

Thanks for your code first!
After reading your code, I want to kown why don't use ape(absolute position embedding) in this code, because i saw the option is False by default.
I also want to confirm that if I use the 128-size pic to train the model with ape, could I can change the image size when I evaluation the model. I thought the length of position embedding is related to the num of patches, and the num of patches is related to the image size.
Hope you can solve my problem!

I didn't test ape because relative position embedding has shown better performance in other tasks.
Yes, you can. See more discussions in https://github.com/JingyunLiang/SwinIR/issues/9.

Thanks for your answer!


Try Rodas5P as default solver

It runs Dommel at similar speed to QNDF, and doesn't diverge over long timespans when iterating between drainage and infiltration on the bucket test model.
HWS model is 44s with Rodas5P vs 10s QNDF. Though QNDF is known to be wrong (#1851). With QNDF I get one large leak of -632063 and several 1e-8. With Rodas5P just one of 2.5e-6. So this addresses that as well.
On top of #1868.

Rodas5P doesn't seem to like ManningResistance very well. The Julia tests go from 15 min to 30 min, and fail and are slow at Manning tests:
  test/run_models_test.jl                          |  137     5    142  18m28.1s
    trivial model                                  |   32           32     12.6s
    bucket model                                   |    8            8      0.5s
    leaky bucket model                             |   14     2     16     21.1s
    basic model                                    |   12           12      0.4s
    basic arrow model                              |    3            3      1.6s
    basic transient model                          |    5     1      6      0.3s
    Allocation example model                       |    3            3     20.3s
    sparse and AD/FDM jac solver options           |    9            9     55.4s
    TabulatedRatingCurve model                     |    5            5     23.7s
    Profile                                        |   12           12      0.1s
    Outlet constraints                             |    3            3     21.3s
    UserDemand                                     |    5            5     14.2s
    ManningResistance                              |    3     2      5  15m25.0s
    mean_flow                                      |   23           23     11.8s

Closing in favor of #1874.


altTypes produces registerEnum errors

OpenUI5 version: 1.120.2
Using UI5 Controls as altTypes produces an error, as if the Control would be an enum
This example:
sap.ui.core.Control.extend("XYZ", {
    metadata: {
        aggregations: {
            button: {
                type: "sap.m.Button",
                altTypes: ["sap.m.MenuButton"]
            }
        }
    }
});

is functionally identical to:
sap.ui.core.Control.extend("XYZ", {
    metadata: {
        aggregations: {
            button: {
                type: ["sap.m.Button", "sap.m.MenuButton"]
            }
        }
    }
});

however, the first one produces the following error and the second doesn't
The type 'sap.m.MenuButton' was accessed via globals. Defining enums via globals is deprecated. Please require the module 'sap/ui/base/DataType' and call the static 'DataType.registerEnum' API. -

Both usages are not supported. Aggregations don't support multiple (managed object) types. Either a single type or an interface can be used.
The altTypes are meant to specify a primitive alternative, e.g. like string for the tooltip aggregation. The given type name must be resolvable via the DataType.getType API. In UI5 1.x, this API was able to resolve a name as a global name to create an enum type from it. In UI5 2.x this is no longer supported as we abandon global names. That's the background of the - often misleading - error message.
We've meanwhile improved this error message in 1.121. It now reads:

[DEPRECATED] The type '${sTypeName}' was accessed via globals. Defining types via globals is deprecated. In case the referenced type is an enum: require the module 'sap/ui/base/DataType' and call the static 'DataType.registerEnum' API. In case the referenced type is non-primitive, please note that only primitive types (and those derived from them) are supported for ManagedObject properties. If the given type is an interface or a subclass of ManagedObject, you can define a "0..1" aggregation instead of a property

This still does not reflect the usage in altTypes, but they're basically used to make single aggregations alternatively behave like properties.


Adjust migrations for djangoCMS 3.3.0 and 3.3.1 compatibility

Code looks good 👍
but I don't really understand why you're explicitly defining "cmsplugin_ptr" field. Can you put short note here?

Thanks @jqb.
Updated PR description.

ok to merge


ES module does not export types, ie VNode

Prompted by https://github.com/cyclejs/cyclejs/issues/925 I wanted to switch to ES module only, but AFAICT it is not possible to import the types, ie VNode from the es module.

@jvanbruegge , #225?

not really because it is just plain missing

@jvanbruegge , similar to #319?

@jvanbruegge is this what you're looking for?
<EMAIL_ADDRESS>import { VNode } from 'snabbdom/es/vnode.js'

Please confirm whether this works for you.

It is now
import { VNode } from 'snabbdom/vnode'

If there are any more issues, please let me know.


Add loopdevice implementation

This PR adds the LoopDevice implementation and applies few little changes in utilities to make ResolveLink method easier to use.

Codecov Report
Attention: 94 lines in your changes are missing coverage. Please review.

Comparison is base (0bc93e0) 73.53% compared to head (582cefa) 73.68%.

Files
Patch %
Lines

pkg/snapshotter/loopdevice.go
73.11%
64 Missing and 25 partials :warning:

pkg/utils/common.go
75.00%
4 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1891      +/-   ##
==========================================
+ Coverage   73.53%   73.68%   +0.14%
==========================================
  Files          70       71       +1
  Lines        7391     7747     +356
==========================================
+ Hits         5435     5708     +273
- Misses       1558     1618      +60
- Partials      398      421      +23

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


When calling auth/login this exception will occured instagrapi.exceptions.LoginRequired: login_required .

When calling auth/login this exception will occured instagrapi.exceptions.LoginRequired: login_required .
However I will received login success email in my mailbox.
INFO<EMAIL_ADDRESS>[429] POST https://i.instagram.com/api/v1/accounts/contact_point_prefill/ (<IP_ADDRESS>.135, Xiaomi capricorn)
WARNING:  Status 429: Too many requests
INFO<EMAIL_ADDRESS>[200] POST https://i.instagram.com/api/v1/accounts/login/ (<IP_ADDRESS>.135, Xiaomi capricorn)
INFO<EMAIL_ADDRESS>[403] POST https://i.instagram.com/api/v1/feed/timeline/ (<IP_ADDRESS>.135, Xiaomi capricorn)
INFO:     <IP_ADDRESS>:58156 - "GET /auth/login HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/uvicorn/protocols/http/httptools_impl.py", line 385, in run_asgi
    result = await app(self.scope, self.receive, self.send)
  File "/usr/local/lib/python3.8/site-packages/uvicorn/middleware/proxy_headers.py", line 45, in __call__
    return await self.app(scope, receive, send)
  File "/usr/local/lib/python3.8/site-packages/fastapi/applications.py", line 199, in __call__
    await super().__call__(scope, receive, send)
  File "/usr/local/lib/python3.8/site-packages/starlette/applications.py", line 112, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/usr/local/lib/python3.8/site-packages/starlette/middleware/errors.py", line 181, in __call__
    raise exc from None
  File "/usr/local/lib/python3.8/site-packages/starlette/middleware/errors.py", line 159, in __call__
    await self.app(scope, receive, _send)
  File "/usr/local/lib/python3.8/site-packages/starlette/exceptions.py", line 82, in __call__
    raise exc from None
  File "/usr/local/lib/python3.8/site-packages/starlette/exceptions.py", line 71, in __call__
    await self.app(scope, receive, sender)
  File "/usr/local/lib/python3.8/site-packages/starlette/routing.py", line 580, in __call__
    await route.handle(scope, receive, send)
  File "/usr/local/lib/python3.8/site-packages/starlette/routing.py", line 241, in handle
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.8/site-packages/starlette/routing.py", line 52, in app
    response = await func(request)
  File "/usr/local/lib/python3.8/site-packages/fastapi/routing.py", line 201, in app
    raw_response = await run_endpoint_function(
  File "/usr/local/lib/python3.8/site-packages/fastapi/routing.py", line 148, in run_endpoint_function
    return await dependant.call(**values)
  File "./routers/auth.py", line 21, in auth_login
    result = cl.login(
  File "/usr/local/lib/python3.8/site-packages/instagrapi/mixins/auth.py", line 378, in login
    self.login_flow()
  File "/usr/local/lib/python3.8/site-packages/instagrapi/mixins/auth.py", line 159, in login_flow
    check_flow.append(self.get_timeline_feed([chance and "is_pull_to_refresh"]))
  File "/usr/local/lib/python3.8/site-packages/instagrapi/mixins/auth.py", line 215, in get_timeline_feed
    return self.private_request(
  File "/usr/local/lib/python3.8/site-packages/instagrapi/mixins/private.py", line 321, in private_request
    raise e
  File "/usr/local/lib/python3.8/site-packages/instagrapi/mixins/private.py", line 308, in private_request
    self._send_private_request(endpoint, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/instagrapi/mixins/private.py", line 209, in _send_private_request
    raise LoginRequired(response=e.response, **last_json)
instagrapi.exceptions.LoginRequired: login_required

Originally posted by @kunal52 in https://github.com/adw0rd/instagrapi/discussions/254

released instagrapi 1.9.11

The issue still persists

@Mustafa0142 What exactly is the issue? If LoginRequired occurs, then you need to log in or re-login. Everything works fine for me on thousands of my accounts

@Mustafa0142 What exactly is the issue? If LoginRequired occurs, then you need to log in or re-login. Everything works fine for me on thousands of my accounts

I am using your example on your Instagrapi website where you can upload a video to story. It used to work fine but now it just keeps telling me loginrequired. I tried different accounts as well. Same issue.

@Mustafa0142 What exactly is the issue? If LoginRequired occurs, then you need to log in or re-login. Everything works fine for me on thousands of my accounts

I figured it out, it just had something to do with the network I was connected to. It blocks the HTTP requests for some reason. I connected to a different network and it worked.

@adw0rd If I run the app through ethernet, I get this error
instagrapi.exceptions.ClientError: Please wait a few minutes before you try again.
But if I connect to wifi, it goes away. Can you help?


Kubernetes harness problems with config.toml version 1

here's the story:

We updated some CI jobs in kubernetes to use 1.5.0 rc0 of containerd here
This caused a bunch of jobs to fail in the weekend, see the red failures in 4/9 and 4/10 here
The problem was tracked to the following error message in containerd log

time="2021-04-09T12:20:01.758944502Z" level=warning msg="failed to load plugin io.containerd.grpc.v1.cri" error="invalid plugin config: no corresponding runtime configured in `runtimes` for `default_runtime_name`"

we did some debugging, printing the config.toml here
for the record the config.toml was

# Kubernetes doesn't use containerd restart manager.
disabled_plugins = ["restart"]
oom_score = -999

[debug]
  level = "info"

[plugins.cri]
  stream_server_address = "<IP_ADDRESS>"
  max_container_log_line_size = 262144
[plugins.cri.cni]
  bin_dir = "/home/kubernetes/bin"
  conf_dir = "/etc/cni/net.d"
  conf_template = "/home/kubernetes/cni.template"
[plugins.cri.registry.mirrors."docker.io"]
  endpoint = ["https://mirror.gcr.io","https://registry-1.docker.io"]
# Setup a runtime with the magic name ("test-handler") used for Kubernetes
# runtime class tests ...
[plugins.cri.containerd.runtimes.test-handler]
  runtime_type = "io.containerd.runtime.v1.linux"

So we could have fiddled around trying to fix the version 1 config.toml which used to work in 1.4.x, but fails in 1.5.0 rc0 or we could just upgrade to v2 of config.toml and we ended up doing that here:
https://github.com/kubernetes/kubernetes/pull/100992

we landed 3 PRs based on this:

https://github.com/containerd/containerd/pull/5335
https://github.com/containerd/containerd/pull/5342
https://github.com/containerd/containerd/pull/5341


Add padding-bottom to button #install-hypr

Before:

After:

remind me in 7 days please

weird it doesn't happen for me..i'll add a bottom padding anyways, thanks!

weird it doesn't happen for me..i'll add a bottom padding anyways, thanks!

Maybe this thing appears only in Chromium based browsers, didnt check it..

Maybe this thing appears only in Chromium based browsers, didnt check it..

checked on brave still not able to reproduce this issue :(
may I know which OS are you viewing the site with, and at what resolution?

Maybe this thing appears only in Chromium based browsers, didnt check it..

checked on brave still not able to reproduce this issue :( may I know which OS are you viewing the site with, and at what resolution? And the browser

Currently on Win10(res: FullHD) and issue still persists in Chrome and Edge..

 On windows its on every browser possible, can't believe I never visited this site on windows, tysm @sherichev

Now i'd have to check if each element is displaying properly on each os properly or not :(

remind me in 7 days please

Can i remind you about my PR?

@vaxerski


Training Lab: Data Transformation with dbt and Snowflake

Migrated from GitLab: https://gitlab.com/meltano/academy/-/issues/4
Originally created by @aaronsteers on 2021-06-13 17:51:15

View 5 previous comments from the original issue on GitLab


Mouse 4 and 5 buttons (forward and back for editor navigation history) are broken after update

Issue Type: Bug
Hi there, after updating my vscode, my forward and back buttons on my mouse no longer traverse navigation history. This works in all other applications (chrome, slack etc.) so not a problem with the mouse. I see this update includes some updates to editor navigation history, wondering if that could be the cause.
Tried modifying workbench.editor.navigationScope but to no avail. Also launched without extensions as you can see below and still broken.
Happy to provide whatever info is needed
VS Code version: Code 1.65.2 (Universal) (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T14:33:49.188Z)
OS version: Darwin arm64 21.4.0
Restricted Mode: No

System Info

Item
Value

CPUs
Apple M1 Pro (10 x 24)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 4

Memory (System)
16.00GB (3.29GB free)

Process Argv
. --disable-extensions

Screen Reader
no

VM
0%

Extensions disabled

🤷  works fine for me on macOS.
Does it reproduce on https://insiders.vscode.dev/ ?

Yes it does repro on https://insiders.vscode.dev/

The key binding ^- works as expected, but the mouse buttons do not. In other chrome tabs the mouse buttons work as expected

@callum-stripe can you:

open https://insiders.vscode.dev/
open dev tools sources tab
add a breakpoint to historyService.ts line 130 (here)
click buttons 3 and 4 and see if the breakpoint is hit?

All the code is minified, I think I need a source map.
Do your mouse 4 and 5 buttons work inside https://insiders.vscode.dev/? I've noticed when I navigate in the current tab to https://insiders.vscode.dev/ the mouse 4 and 5 buttons are captured by the browser and not propagated to the current page, resulting in a forwards or backwards navigation (back to this github issue for example). However when I open https://insiders.vscode.dev/ in a new tab there's no history to nav to, but I'm not sure if the browser then propagates the input to the page. A quick Google search does not reveal a setting to propagate mouse 4 and 5 input to the page

Source maps are provided and will load shortly after.
I think as long as focus is inside an editor, the mouse buttons can be captured by us.

Am I doing this right? Doesn't look like historyService.ts is showing up as a file

Looks like it failed to load some source maps, they look mostly for extensions though:

Ok thanks, this sounds like an upstream problem then and not with VSCode. We rely on the buttons getting through.

Got it, so likely a chromium issue?

If you can reproduce this in Chrome, then I suggest to report this at https://bugs.chromium.org/p/chromium/issues/list


Merge config.*.yaml and `config.yaml environment variables and hooks

[Sorry for the vague title, I struggled to think of what to call it]
Is your feature request related to a problem? Please describe.

I am new to DDEV and am currently in the process of setting up some config files to share with my team.
We use TYPO3 set up with .env files but, as it is just the development environment (and for quick setup), I have committed the following to my config.yaml
web_environment:
- TYPO3_CONTEXT=Development/Local
- TYPO3_DB_HOST=db
- TYPO3_DB_USER=db
- TYPO3_DB_PASSWORD=db
- TYPO3_DB_NAME=db

The issue arose when I wanted to change the TYPO3_CONTEXT for my local install, without changing the committed file (for risk of accidental committing). Suggest on Discord was the creation of a config.env.yaml to override settings.
This worked, however I had to re-declare all of my variables.
Describe the solution you'd like
It would be great if you could just declare the variable you wish to overwrite
E.g.
web_environment:
- TYPO3_CONTEXT=Production

Rather than needing to reset the DB credentials again.

We usually use .env files, too. And yes, we duplicate a lot of stuff (100 lines or more for all the cache/mail/... configurations) in them. I rather enjoy that it is so explicit.
If you want to do any kind merging of config, I suggest you do it in AdditionalConfiguration.php.
And for very simple sites where you only need 2 envs (local and live) the ddev-mechanism is sufficient: DB stuff is added by ddev to a ddev-managed AdditionalConfiguration.php.

Thanks for this issue. You're not the first one to hit it. I think there will be a variety of ways to do environment variables in the near future, so that may solve it as well.

We could definitely be using this on a company-wide project I'm working on that we're converting over from Lando. Would it be good if the environment variables were defined as an actual key/value format instead of the simple strings?
.ddev/config.yml
web_environment:
  MY_VARIABLE: value

.ddev/config.local.yml
web_environment:
  MY_VARIABLE: overridden value

Would it be good if the environment variables were defined as an actual key/value format instead of the simple strings?

I'm pretty sure that the other format already works in yaml but I haven't tested it. I usually can remember VAR=value easier.

I don't think it matters. And there's a virtue to the current format: you can unset an environment variable by doing this in your list of string:
web_environment:
- KEEP_THIS_ONE=newvalue
- LOSE_THIS_ONE=

You could not do this intuitively with a map of string.

I tried the key/value format and it failed due to YAML parsing when I tried to start ddev, so I don't think it is supported? I don't see why we couldn't "unset" a value the same way, by assigning it '~' or null as per https://stackoverflow.com/questions/34089496/empty-field-in-yaml.


Update to<EMAIL_ADDRESS>

Update WASI-virt to<EMAIL_ADDRESS>Several interfaces in wasi-sockets changed, so this updates the virtual-adapter accordingly.

I think the virt-deny / "strip virt" functionality also needs to be updated here for the function signature changes. Ideally we should auto-generate all of this from the WITs, but that work hasn't been done yet so for now those all need to be maintained manually.

Yeah, was trying to split out some changes to help isolate a wasm-encoder chage, but split out too much.

@sunfishcode I've pushed some more WIT updates here as well as using the WIT bindgen bug fix at https://github.com/bytecodealliance/wit-bindgen/pull/831 that was necessary to get this to build.
The current failure is now that we use an empty world to build up the full virt world (virt-base) but it seems somewhere along the upgrade path, worlds are now being automatically pruned from components, so we likely need to change the strategy in https://github.com/bytecodealliance/WASI-Virt/blob/main/src/lib.rs#L168 where we read the full WIT folder from the binary encoding in the virtual adapter, to ensure that we can definitely find all the worlds that we encoded from the WIT folder instead of them getting automatically pruned in the binary.

I've posted https://github.com/sunfishcode/WASI-Virt/pull/1 as an update to this PR which updates the decoding process for the newly-encoded WIT format.

I've updated the PR with @alexcrichton's fix, and can confirm the remaining bugs are now just in the deny and strip virt updates. Will try and push those shortly.


kube-aws: kubernetesServiceIP is no longer a parameter.

It is now cacluated from Cluster.ServiceCIDR, so it is now a member of the Config struct.
\cc @aaronlevy @ericchiang

Rather than restructuring a bunch of stuff, couldn't we just set the KubernetsServiceIP at the entry points to the cluster struct? More or less looks like that would just be configFromBytes() (where we could just parse the IP from the serviceCIDR)

It's a matter of keeping with convention. Derived values that are computed from the yaml parameters are set in cluster.Config method, and are members of the Config struct.
The Config struct is Cluster + derived values

My gut reaction is that this feels off. If this simple of a change requires this much code, either we structured it in a way that makes maintainability difficult, or there could be some better options.
Some concerns:
We now have validation of a config happening in 2 places: cluster.valid() and cluster.Config()
The valid() method actually only validates against the ServiceCIDR, not the stored KubernetesServiceIP. So there could be situations where that (public) field is not valid, but the valid() code reports that everything is fine.
What about, as another option:
It looks like the only places the KubernetesServiceIP are referenced are in valid() and NewTLSAssets. The valid() function already just uses the ServiceCIDR to determine the kubernetes serviceIP, why don't we just update NewTLSAssets to do the same (and not store as a field on config{})

I agree, it's better now.

lgtm


Fix style check on arm64

Description
Right now make style failed on arm64. This PR fixes it.
Checklist

[ ] Investigated and inspected CI test results
~[ ] Unit test and regression tests added~
~[ ] Evaluated and added CHANGELOG entry if required~
~[ ] Determined and documented upgrade steps~
~[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

If we do not run amd64 on arm64, we would not need to cross-compile rocksdb, right? I am having everything arm64 on my m1.

The current build tags ensure that rocksdb is not required for any architecture other than amd64. If we modify them, then arm64 will start requiring rocksdb. This works locally because we have built rocksdb on our macs, but upstream, we do not want to rely on building rocksdb for arm64


feat: the shift on a quotient category

This PR constructs the shift on a quotient category.

[x] depends on: #6652

Thanks for the review!
bors merge


fix: bump edge-runtime to 1.0.15

What kind of change does this PR introduce?
Bumps edge-runtime to v1.0.15 which included bug fix for #869

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3707

Relevant Lines:
5935

💛  - Coveralls


0.7.10 npm run release fails on linux

I am trying to build beaker for packaging on linux. npm install works fine but npm run release (which I assume creates an executable package) fails with the following trace:
Operation System: linux 4.14.5-1
Beaker Version: 0.7.10
$ npm run release

> beakerbrowser@ release /home/jeancf/Desktop/beaker-0.7.10
> npm run build && build -p never && gulp postbuild

> beakerbrowser@ build /home/jeancf/Desktop/beaker-0.7.10
> gulp build

[20:47:31] Using gulpfile ~/Desktop/beaker-0.7.10/gulpfile.js
[20:47:31] Starting 'burnthemall-maybe'...
[20:47:31] Finished 'burnthemall-maybe' after 6.12 ms
[20:47:31] Starting 'bundle'...
[20:47:31] Starting 'less'...
[20:47:31] Finished 'less' after 40 ms
'TimeoutError' is imported from external module 'beaker-error-constants' but never used
'TimeoutError' is imported from external module 'beaker-error-constants' but never used
'TimeoutError' is imported from external module 'beaker-error-constants' but never used
'default' is imported from external module 'function-queue' but never used
'default' is imported from external module 'moment' but never used
[20:47:40] Finished 'bundle' after 8.99 s
[20:47:40] Starting 'build'...
[20:47:40] Finished 'build' after 75 μs
electron-builder 19.43.4
Skip app dependencies rebuild because npmRebuild is set to false
Packaging for linux x64 using electron 1.8.2-beta.2 to dist/linux-unpacked
Error: ENOENT: no such file or directory, open '/home/jeancf/Desktop/beaker-0.7.10/app/node_modules/sodium-signatures/node_modules/sodium-native/tmp/lib/libsodium.so'
    at w (/home/jeancf/Desktop/beaker-0.7.10/node_modules/electron-builder/src/asar/asarUtil.ts:191:11)
    at writeStream.write (/home/jeancf/Desktop/beaker-0.7.10/node_modules/electron-builder/src/asar/asarUtil.ts:193:43)
    at afterWrite (_stream_writable.js:466:3)
    at onwrite (_stream_writable.js:457:7)
    at fs.write (fs.js:2242:5)
    at FSReqWrap.wrapper [as oncomplete] (fs.js:703:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 255
npm ERR! beakerbrowser@ release: `npm run build && build -p never && gulp postbuild`
npm ERR! Exit status 255
npm ERR!
npm ERR! Failed at the beakerbrowser@ release script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/jeancf/.npm/_logs/2017-12-19T19_47_59_728Z-debug.log

Am I on the right track to build a package? How can I fix the error?

Hi.. Am mostly still a newbie here, but occasionally I can still catch something. For this line:

Error: ENOENT: no such file or directory, open '/home/jeancf/Desktop/beaker-0.7.10/app/node_modules/sodium-signatures/node_modules/sodium-native/tmp/lib/libsodium.so'

That ENOENT could be seen as meaning something like "error: no entity (or entry)".
Can you follow your file hierarchy and locate that libsodium.so file manually? If it's really not at that location above, you could try to run something like updatedb and then locate libsodium.so to see where that file landed within your Linux file hierarchy, if it's even there in your setup at all.
At this point in things, users over at the npm/npm Github tend to have success by doing things like cleaning and/or updating their cache. Some users have even gone the harsh route of deleting something, like maybe a full directory of some sort, but I'm not comfortable with that route... so I'm not going to even try to search that one down. I think what happens when users go that hardcore deletion route is they're simply resetting whatever they did the first time.

@jeancf Could you try running npm run burnthemall and then npm run release ?

@pfrazee npm release still fails with the same error after trying npm run burnthemall.
Following the idea from @Butterfly I was able to locate the issue though.
/home/jeancf/Desktop/beaker-0.7.10/app/node_modules/sodium-signatures/node_modules/sodium-native/tmp/lib/libsodium.so is actually a broken symlink.
-rw-r--r-- 1 jeancf jeancf 2.3M Dec 21 17:05 libsodium.a
-rwxr-xr-x 1 jeancf jeancf 1.1K Dec 21 17:05 libsodium.la
lrwxrwxrwx 1 jeancf jeancf   19 Dec 21 17:05 libsodium.so -> libsodium.so.18.2.0
lrwxrwxrwx 1 jeancf jeancf   19 Dec 21 17:05 libsodium.so.18 -> libsodium.so.18.2.0
drwxr-xr-x 2 jeancf jeancf 4.0K Dec 21 17:05 pkgconfig

There is a /home/jeancf/Desktop/beaker-0.7.10/app/node_modules/sodium-signatures/node_modules/sodium-native/deps/libsodium/src/libsodium/.libs/libsodium.so.18.2.0 however. If I copy that file to the other directory the symlinks are OK again.
Now running npm run release fails with another error:
> beakerbrowser@ release /home/jeancf/Desktop/beaker-0.7.10
> npm run build && build -p never && gulp postbuild

> beakerbrowser@ build /home/jeancf/Desktop/beaker-0.7.10
> gulp build

[17:13:39] Using gulpfile ~/Desktop/beaker-0.7.10/gulpfile.js
[17:13:39] Starting 'burnthemall-maybe'...
[17:13:39] Finished 'burnthemall-maybe' after 467 μs
[17:13:39] Starting 'bundle'...
[17:13:39] Starting 'less'...
[17:13:39] Finished 'less' after 8.66 ms
'TimeoutError' is imported from external module 'beaker-error-constants' but never used
'TimeoutError' is imported from external module 'beaker-error-constants' but never used
'TimeoutError' is imported from external module 'beaker-error-constants' but never used
'default' is imported from external module 'function-queue' but never used
'default' is imported from external module 'moment' but never used
[17:13:42] Finished 'bundle' after 3.3 s
[17:13:42] Starting 'build'...
[17:13:42] Finished 'build' after 22 μs
electron-builder 19.43.4
Skip app dependencies rebuild because npmRebuild is set to false
Packaging for linux x64 using electron 1.8.2-beta.2 to dist/linux-unpacked
Building AppImage for arch x64
Error: Cannot detect repository by .git/config. Please specify "repository" in the package.json (https://docs.npmjs.com/files/package.json#repository).
Please see https://electron.build/configuration/publish
(...)

@jeancf what distro are you running?

For me starting Beaker fails with npm run release and succeeds as intended with npm start. Don't know whether that matters but just posting as FYI.
Error: ENOENT: no such file or directory, open '/home/chjh/beaker/app/node_modules/sodium-signatures/node_modules/sodium-native/tmp/lib/libsodium.so'
    at w (/home/chjh/beaker/node_modules/electron-builder/src/asar/asarUtil.ts:191:11)
    at writeStream.write (/home/chjh/beaker/node_modules/electron-builder/src/asar/asarUtil.ts:193:43)
    at afterWrite (_stream_writable.js:455:3)
    at onwrite (_stream_writable.js:446:7)
    at fs.js:2246:5
    at FSReqWrap.wrapper [as oncomplete] (fs.js:703:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 255
npm ERR! beakerbrowser@ release: `npm run build && build -p never && gulp postbuild`
npm ERR! Exit status 255
npm ERR!
npm ERR! Failed at the beakerbrowser@ release script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/chjh/.npm/_logs/2017-12-21T17_28_20_525Z-debug.log

I am on Arch Linux.
/~JC
-------- Message original --------
Objet : Re: [beakerbrowser/beaker] 0.7.10 npm run release fails on linux (#793)
De : Paul Frazee<EMAIL_ADDRESS>À : beakerbrowser/beaker<EMAIL_ADDRESS>Cc : JC Francois jc@noirextreme.com,Mention<EMAIL_ADDRESS>
@jeancf what distro are you running?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/beakerbrowser/beaker/issues/793#issuecomment-353406886

This seems like an issue either with an upstream dependency or with NPM. What version of node/NPM are you using?

node-9.3.0
npm-5.6.0
Sorry, I am unfamiliar with npm and how it works. Is appImage part of npm?  Do you imply that when it npm tries to build AppImage, it is actually trying to installl it to my system and not inside the beaker folder? I looked for an appimage package in the repos but there is none.

@jeancf is your goal to build a distributable package of Beaker, or just to build it so you can run from source? If it's the latter, then you don't need to run npm run release. You can just do npm install ; npm run rebuild; npm start. And then for subsequent runs, npm start

@pfrazee I was trying to build a distributable package for arch. I was hoping that npm run release would generate the files in the target system locations ('/usr/share', '/usr/bin', etc.) before packaging them in the AppImage file (disclaimer: I have no idea whether this is how AppImageKit works).
In the meantime I noticed that somebody created a package for arch invoking npm installand npm run rebuild.
On second thoughts I would be happy with a package that is just installing the AppImage file system wide. However for that there is an issue with the install window that pops up when you launch the AppImage:

Would you like to integrate /home/jeancf/Desktop/beaker-browser-0.7.10-x86_64.AppImage with your system?
This will add it to your applications menu and install icons.
If you don't do this you can still launch the application by double-clicking on the AppImage.

Is there a way to suppress this message (e.g. by passing a command-line argument such as ./beaker-browser-0.7.10-x86_64.AppImage --no-install)? If it was the case the package could handle the placement of icons and desktop files in system-wide locations instead of ~/.local


Dog Randomization

Hi,
I was wondering if there could be a version of the code without the dog randomization.
Thank you!

Added with f8c053a056c65643c022ffb0c1d9b32b307c1a9c, let me know if this solves it for you! If you follow the readme for the simple NFT deployment, it should give you a URL to view your NFT on opensea.


server not defined when used in a helper used in an acceptance test (maybe ember-mocha related)

I'm using v2 beta 9 and ember 2.5
TypeError: Cannot read property 'create' of undefined

from this line:
server.create('user');

which is in a test helper:
import Ember from 'ember';
import 'aeonvera/tests/helpers/service-named';
import { server } from 'ember-cli-mirage';

export default Ember.Test.registerAsyncHelper('login', function(app, assert) {
  server.create('user');

which is called from this acceptance test:
import Ember from 'ember';
import { it } from 'ember-mocha';
import startApp from 'aeonvera/tests/helpers/start-app';
import 'aeonvera/tests/helpers/login';
import startMirage from 'aeonvera/tests/helpers/setup-mirage-for-integration';

describe('Acceptance | login', function() {
  let application;

  beforeEach(() => {
    application = startApp();
    startMirage(this.container);
  });

  afterEach(() => {
    Ember.run(application, 'destroy');
    server.shutdown();
  });

  it('can login', function(done) {
    login();
    done();
  });
});

any ideas why server is undefined?

You don't import server, it's actually a global at the moment.

server is still undefined, actually, I've been trying to convert my qunit suite to mocha. Acceptance functions didn't carry over at all. So, I think I need to somehow tell ember that my test is an acceptance test

Yes, by default Mirage is instantiated in an Ember app initializer. You need to manually start Mirage if you're not in an acceptance test.

I believe I have in my beforeEach hook. So I think something else may be
the culprit.
On Tue, May 17, 2016, 10:21 PM Sam Selikoff<EMAIL_ADDRESS>wrote:

Yes, by default Mirage is instantiated in an Ember app initializer. You
need to manually start Mirage
http://www.ember-cli-mirage.com/docs/v0.2.0-beta.9/manually-starting-mirage/
if you're not in an acceptance test.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/samselikoff/ember-cli-mirage/issues/741#issuecomment-219908058

for the record:

my imports for this test:
import Ember from 'ember';
import { describe, it, beforeEach, afterEach } from 'mocha';
import { expect } from 'chai';

import startApp from 'aeonvera/tests/helpers/start-app';
import startMirage from 'aeonvera/tests/helpers/setup-mirage-for-integration';

import 'aeonvera/tests/helpers/login';

and the setup-mirage file:
import mirageInitializer from '../../initializers/ember-cli-mirage';

export default function startMirage(container) {
  mirageInitializer.initialize(container);
}

I'm also trying to talk with the mocha people on how to properly set up for an acceptance test.

Same here, server is definitely not present on acceptance tests. Normal setup here, nothing out of the ordinary :confused:


Calculation of the Generalized Advantage Estimation

Hi! Thanks for sharing the RNN-PPO implementation, it's very insightful. I have a question about the GAE calculation calc_advantages as part of the rollout buffer.
My understanding is that the GAE is calculated over a single episode at a time. However, with the current approach the GAE is calculated over all the episodes combined per worker. If I am not mistaken about the implementation of the data sampling.
The exact line I'm talking about:
https://github.com/MarcoMeter/recurrent-ppo-truncated-bptt/blob/9206a97b7546ec62e668eaf67ae6d4b752e0f0ee/trainer.py#L177

Hi @RobvanGastel
thanks to reaching out!
It is more efficient to process the data by workers. To ensure that the GAE is computed episode-wise the mask from line 181 is used.

Thanks for pointing that out, I overlooked the boolean mask, sorry for the inconvenience. I have another question about the sampling of full episodes, does the zero padding affect the update method in any way, .e.g. have you observed any difference in using full episodes vs. padded ones?
https://github.com/MarcoMeter/recurrent-ppo-truncated-bptt/blob/9206a97b7546ec62e668eaf67ae6d4b752e0f0ee/buffer.py#L91

Padding is applied whenever a sequence is shorter than the expected sequence length. This also applies to full episodes. The padding is concatenated to the end of the sequence. During optimization, the padded values are masked. So in the end the padding is only useful for processing larger batches.
However, I'm not sure if the optimization is affected if the padding is concatenated before the beginning of the sequence.

Thanks for the quick response, it answered all my questions!

Happy to help!


Private ECR image in runners

I shared an example in the comments.

I know this issue is not about your plugin.
But I wish at least you have an example to support private ecr images in runners with docker machine.

After I installed amazon-ecr-credential-helper to both instance, it started to work. Here the full sample for the ones who wants to use private ECR image in runner:
module "gitlab_runner" {
  source  = "npalm/gitlab-runner/aws"
  version = "4.11.1"

  userdata_pre_install = "sudo yum install amazon-ecr-credential-helper -y"
  userdata_post_install = "echo '#!/bin/bash\nsudo apt-get update\nsudo apt-get install amazon-ecr-credential-helper -y' >> /var/tmp/user_data.sh"
  docker_machine_options = ["amazonec2-userdata=/var/tmp/user_data.sh"]
  runners_environment_vars = ["DOCKER_AUTH_CONFIG={\"credHelpers\":{\"${local.ecr_aws_account_id}.dkr.ecr.${local.region}.amazonaws.com\": \"ecr-login\"}}"]

  ami_filter = {
    name = ["amzn2-ami-hvm-2.*-x86_64-ebs"]
  }
  runner_ami_filter = {
    name = ["ubuntu/images/hvm-ssd/ubuntu-eoan-19.10-amd64-server-*"]
  }

  gitlab_runner_version    = "12.8.0"
  # ........
}

resource "aws_iam_role_policy_attachment" "allow_ecr_full_agent" {
  role       = "${module.gitlab_runner.runner_agent_role_name}"
  policy_arn = "arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryFullAccess"
}

resource "aws_iam_role_policy_attachment" "allow_ecr_full" {
  role       = "${module.gitlab_runner.runner_role_name}"
  policy_arn = "arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryFullAccess"
}

@realsby This setup isn't working for me, would you mind verifying this example is still valid?
Thanks!

@DavidGamba Yes it is working. This is the recent copy.
module "sas_gitlab_default" {
  source  = "npalm/gitlab-runner/aws"
  version = "4.13.0"

  userdata_pre_install     = "sudo yum install amazon-ecr-credential-helper -y"
  userdata_post_install    = "echo '#!/bin/bash\nsudo apt-get update\nsudo apt-get install amazon-ecr-credential-helper -y' > /var/tmp/user_data.sh"
  docker_machine_options   = ["amazonec2-userdata=/var/tmp/user_data.sh"]
  runners_environment_vars = ["DOCKER_AUTH_CONFIG={\"credHelpers\":{\"${local.ecr_aws_account_id}.dkr.ecr.${local.region}.amazonaws.com\": \"ecr-login\"}}"]

  ami_filter = {
    name = ["amzn2-ami-hvm-2.0.20200304.0-x86_64-ebs"]
  }

  runner_ami_filter = {
    name = ["ubuntu/images/hvm-ssd/ubuntu-eoan-19.10-amd64-server-20200325"]
  }

}

@realsby thanks so much, just for clarity with that I can just call the image directly in my .gitlab-ci.yml file right?
job1:
  image: "391495333905.dkr.ecr.us-west-2.amazonaws.com/dgamba-deployments-base:latest"
  ...

Or are you doing anything different there?

Hi guys, we're trying to setup the same thing, not having it all working yet. (see #234 for details). Is above configuration still working @realsby , @DavidGamba ?
Do your runners maybe also report?

gitlab-runner: Failed to process runner builds error: failed to update executor: no free machines that can process builds

It seems our runner-agent is not successfully pushing the user-data to the actual docker machine runners..
Thanks in advance!

@sjoerd-dijkstra I recently updated everything, runner version, os ami images, this module version and they all worked fine without any problem with the ecr.
I am not sure what is the problem that you are facing with, i saw you also give ECR full permission to everything.
The only thing that i realize you define runners_image but when i check my terraform i did not set anything so it is using the default value of the module. Maybe its because of the docker version i don't know.


Does not refresh modified dependencies

I'm using this Quasar AppExtension to manage tags and meta.
I'm currently working on that AE so i added a local dependency to test my progress. I noticed that while in dev or ssr mode every time i modify the AE and i run yarn add -D ../path and quasar ext invoke @dreamonkey/meta everithing works just fine. With this AE i always need instead to delete my dist folder, uninvoke and delete that dependency, re add and re invoke it and finally run quasar ssg generate.
I also tried to delete my node modules and update them but nothing changes.
Any clues if i'm doing something wrong?

If i refer to the Quasar documentation, to develop localy an app extension, you should add it to the dependencies like this:
$ yarn add --dev file://path/to/our/app/ext/root
# or
$ yarn add --dev link://path/to/our/app/ext/root

If you don't want to repeat the uninstall and install procedures, just follow the Developing section of the readme.
The only difference i can think of between this AE and this one, is that quasar-app-extension-ssg package is not published yet.
PS: On which platform are you working ? Linux, MacOS or Windows ?

@vandelpavel,
I published the AE to NPM. Could you try to update it, and tell me if you still have this issue please ?

Same project, same AE but all migrated to V2.
Still need to do that 'hack' in order to refresh the other AE dependecy.
To be clear i launch yarn add ../path then '`quasar ext invoke `` and the build still use the older dependency.
If i delete node modules and re install them it works.
(Sorry if late)


Improve join queries mapping

Stream<Tuple2<R1, R2>> Query#mapJoining(Class<R1>, Class<R2>);

which could be used like
Map<R1, List<R2>> r2sByR1 = stream.collect(groupingBy(Tuple2::left));

That'd imply either a dependency like JOOL (meh) or writing Tuple[N] classes.

https://github.com/bendem/sql-streams/commit/b6b8f90631da35e1a9740173d87df1cb657084c9


Add an input and output gain parameter

Level from -inf to +18db
Knobs and automatable
Closes #85

Oh do not merge. I forgot to stream it! duh.


Port error...

Expected behavior
Actual behavior
Steps to reproduce the behavior
Other

Error Stack
root@leiderpro:/var/www/html# node index.js
Bot (bot_1) has been logged-in.
[!] All bots online.
[!] Website server is online.
[!] Socket server is online.
events.js:163
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE :::80
at Object.exports._errnoException (util.js:1050:11)
at exports._exceptionWithHostPort (util.js:1073:20)
at Server.setupListenHandle [as _listen2] (net.js:1259:14)
at listenInCluster (net.js:1307:12)
at Server.listen (net.js:1406:7)
at Object. (/var/www/html/index.js:20:8)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
root@leiderpro:/var/www/html#

node v7.10.0

Port 80 is already in use.
Is apache running?

yes apache running

Yeah, that's why.
Apache is using port 80.
What you can do:
Stop the service by running : sudo service apache2 stop
Delete apache2 by running: sudo apt-get remove apache2

can i no use both?

Yes you can.
You can change the port in the config.js
Remember when changing the port it also changes the URL a bit. ex: csg0.trade:>port< / csg0.trade:81

oh nice man thanks :D


add feedback on user actions when uploading artifact to m2k UI

Is your feature request related to a problem? Please describe.
When I upload an artifact to move2kube UI, I dont receive any notification on the status of the upload. This can cause some confusion, specially for first time users.
Describe the solution you'd like
Usually, when we upload a file,  systems provide a loading indicator (an animation) and once the file has been uploaded, there is a notification saying file uploaded successfully.
Describe alternatives you've considered
None
Additional context
This is a minor feature, but it could improve the overall user experience when onboarding an app

@pabloloyola Can you please check the current flow, and see if it is fixed?


[C++] Refactor includes and add option to play nice with CMake and large projects to avoid header name conflicts

Some of the aeron-client headers have very common names like Subscription.h and Context.h which could lead to include conflicts in large projects.
A common practice for C++ libs is to use a stuttering directory structure (e.g. boost, folly, fmt, date, tl_expected, etc) so that the user can #include "library/header.h" instead of #include "header.h" directly.
This would be a breaking change though so the alternative I came up with was to add the AERON_CLIENT_STUTTERING_HEADERS option to CMakeLists.txt. This option installs the headers under an aeron-client directory during the build so the user can #include "aeron-client/Aeron.h" for example.
To make this work without breaking existing code I had to make all the local includes relative to the file path.
I'm not sure how you feel about this stylistically speaking but it's a compromise that allows existing code to continue as is while allowing new code to use the stuttering option.
Includes were also inconsistent between <> and "" so I changed all local includes to "".
This solution also plays nice with CMake FetchContent.
Example usage:
CMakeLists.txt:
# aeron
FetchContent_Declare(
  aeron
  GIT_REPOSITORY git@github.com:e2m-investimentos/aeron.git
  GIT_TAG master
)

set(AERON_CLIENT_STUTTERING_HEADERS ON)

FetchContent_MakeAvailable(aeron)

install(
  TARGETS aeron aeronmd aeron_client_shared aeron_driver
  RUNTIME DESTINATION ${MY_BIN_INSTALL_DIR}/aeron
  LIBRARY DESTINATION ${MY_LIB_INSTALL_DIR}
  ARCHIVE DESTINATION ${MY_LIB_INSTALL_DIR}
)

MyClass.h:
#include "aeron-client/Aeron.h"
....

The install can be configured in a number of ways. So, changing the current structure is not necessary. If you want a specific type of setup, then do it in your own project install.
The <> and "" are done for system vs. local headers. And is how we want it.
Also, the use of relative paths in includes is a bad idea all around.
Thanks, though. But this is not changes we want to make.

Understood. Just a comment on the includes, when I mentioned the inconsistency it was for local headers specifically, e.g.
AtomicArrayUpdater.h:
#include "concurrent/Atomic64.h"
"HeaderFlyweight.h":
#include <concurrent/AtomicBuffer.h>

Sometimes CLion does things automatically. So, not ideal. :) I try to fix them as I find them. Thanks for pointing that one out!

Also for reference in case anyone looks at this issue in the future, I don't think this is solvable from outside the project without poluting the include path.
I could certainly install the headers somewhere else for the sake of my own includes but the transitive includes would then fail, i.e. if I have aeron-client/ in my include path I can #include "aeron-client/Aeron.h" but then Aeron.h would fail at #include "ClientConductor.h" for example.
I suppose if you happen to have another dependency with the same header names you'd have to choose one of the conflicting dependencies to fork.