azure vm docker create yields devicemapper backend

I'm creating ubuntu 14.04.2 LTS vm's using the following syntax for the xplat cli.
azure vm docker create --ssh -l "West US" -n "dockerhost01" dockerhost01 "b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_2_LTS-amd64-server-20150309-en-us-30GB" user pass --availability-set "dockerhost01-as" --virtual-network-name "docker-net" -b Subnet-1 --docker-cert-dir ./certs

The resulting docker instances use devicemapper as the storage backend, not aufs and as such are affected by this issue: https://github.com/docker/docker/issues/4036.  Below is the docker info from one of my deployed machines.  If I run the docker installation manually (https://github.com/Azure/azure-docker-extension/blob/master/scripts/install.sh#L65-L72) on a VM created from the same image, I do not have the same problem and the docker installation picks up aufs as expected.  Is the code in this repository the 'live' docker extension for azure, or is there some other problem ?
Thanks.
docker info:
Containers: 0
Images: 0
Storage Driver: devicemapper
 Pool Name: docker-8:1-131207-pool
 Pool Blocksize: 65.54 kB
 Backing Filesystem: extfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 305.7 MB
 Data Space Total: 107.4 GB
 Metadata Space Used: 725 kB
 Metadata Space Total: 2.147 GB
 Udev Sync Supported: false
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.82-git (2013-10-04)
Execution Driver: native-0.2
Kernel Version: 3.16.0-31-generic
Operating System: Ubuntu 14.04.2 LTS
CPUs: 1
Total Memory: 1.639 GiB
Name: dockerhost01
ID: ....
Username: ....
Registry: [https://index.docker.io/v1/]
WARNING: No swap limit support

@spanditcaa Thanks, I will take a look into this. Meanwhile what is the version of azure CLI you have installed?

0.8.16.  I'll update to .17 and let you know if that makes a difference.

@spanditcaa I just used the same image 1 to create a new VM with this cmomand and it uses aufs.

Yes - it looks like 0.8.17 did the trick.  Mine came out with aufs as well.  Thank you.


Implement User Management System

TODOs

[x] Add basic user management page

[x] Set page to allow for user edits

[x] Create registration process

[x] Send email with proper link to register

[x] Properly setup DNS handling (https://github.com/Sh4yy/vercel-email#setup-spf)
[x] Test sending email on create user

Interesting Resources
https://github.com/carstenlebek/svelte-email
https://github.com/Sh4yy/vercel-email

closed by 6d1c2083956e0abfdf8b5349301c378163098292


Life attribute on Particle Emitter is not applied to particles individually

Issue details
The behaviour of Life and Life Offset attributes of a Particle Emitter is different than the rest of attributes such as Rotation, Angle, Gravity, etc... in the sense that it is not evaluated by particle but only by time. What this means is that All particles emitted at one time will have the same Life. This limitation doesn't allow simple effects such an explosion in which not all particles live the same.
According to the Wiki:

Life: How long a single particle will live.

Life Offset: How much life is used up when a particle spawns. The particle is still moved/rotated/etc for the portion of its life that is used up. This allows particles to spawn, eg, halfway through their life.

It could be that the way the Life attribute behaves atm is useful for some type of effect but as a user I miss a Life attribute that affects each particle individually.
Whether we need a new Life attriubute or fix the existing one I will happily work on a PR.
Reproduction steps/code
Video showing the issue, observe that when life value is modified to be Ranged, all particles have the same Life.
https://youtu.be/IXOgCgAUmk8
Version of LibGDX and/or relevant dependencies
1.9.8

Note the Emission, Life, and Life Offset graphs say "Duration" while the other graphs say "Life". That label describes what the X axis of the chart represents.
I've not used the particle emitters in a long time. To try what you propose, change this in ParticleEmitter:
particle.currentLife = particle.life = life + (int)(lifeDiff * lifeValue.getScale(percent));

To:
life = (int)lifeValue.newLowValue();
lifeDiff = (int)lifeValue.newHighValue();
if (!lifeValue.isRelative()) lifeDiff -= life;
particle.currentLife = particle.life = life + (int)(lifeDiff * lifeValue.getScale(percent));

It does seem to make sense, maybe providing better control than the current implementation, but I would have to get into trying to create effects both ways to see what I liked better. I'm not sure I'll find time to do that. Do others have opinions?
Can someone verify what this change would do to existing effects? I expect it breaks them pretty badly. I guess it could be a life setting or a separate property.

Thanks for your inputs.
In my opinion, most of the times, when you use Ranges you want property values to affect each particle indivuidually. There are some specific effects, though, that require those values to apply to all particles so no solution covers all cases. This applies to all properties, from Rotation to Velocity, not just Life.
If I had to design how the Particle Editor works, properties would affect "Each particle individually" by default and for extra versatility, a setting/checkbox on each of them would allow to switch to "All particles".
I agree that we must keep the option to set Life property to work as it has worked until now.
There are 2 options:

We leave current behaviour as default and add a setting to change it to apply particles individually.
We change current behaviour and add a checkbox to set it to how it was before.

Option 1 has the advantage of being fully backwards compatible.
Option 2 has the advantage of consitency across properties and (this is an opinion) that default will be the most common use case. It also opens the door for adding that setting to the rest of the properties.
I'll work on a PR, personally I prefer Option 2 but it can easily be changed.

If you want to play here's a modified Particle Editor with Nate's changes (bear in mind Life Offset behaviour has not been changed). I recommend opening it next to the old one to compare.
https://drive.google.com/open?id=1dTwDWn042aezX13dqJYFomsvgZ7fH1-W

A checkbox and not breaking existing effects sounds good!


Convert build process to Maven

Maven, and its Tycho plugin seem to have really good support for Eclipse plugins.  Eventually, I would like to migrate to using Maven instead of Ant.
Help is wanted, as I'm not sure how to wrangle the dependencies this project has (on the findbugs eclipse plugin and fb-contrib).

As it turns out, eclipse provides ant tasks with okay support for this.  Ant is working fine for now.


Improve MDR page based on customer feedback

⚠ IMPORTANT ⚠: This is a public repository. Make sure to not disclose:

[x] personal data beyond what is necessary for interacting with this Pull Request;
[x] business confidential information, such as customer names.

LGTM as well!


immediate crash on startup

Describe the bug
the game crashes on startup, after reading #10 i found i had the same problem. so i disabled randompatches, but stumbled across a similar but different crash instead
Logs or/and crash reports
https://mclo.gs/NvunWXa
Versions

Valkyrie: 0.1.3
Red Core: 0.2
mixinbooter: 7.1
Forge: 1.12.2 2860
Java: openjdk 1.8.0_372

Specification:

OS: windows 11
CPU: i9 13950hx
GPU: rtx 4080
RAM Allocated: 8gb

Oh, that is an OptiFine issue, it is fixed in 0.2-Dev to download the dev build you must join my Discord server and head into #Dev Builds under the Valkyrie category, there you will find all dev builds.
0.2 should be released pretty soon.
*Note: Sorry for the extremely late reply, I just realized that GitHub stopped automatically watching my repo's orgs, so I was never notified of this. *

Duplicate of #7

ahh ok, i have a look.
thanks.


Upgrade webpack to v5

I ran into an issue with the build for 9.11.1 release.
Azure pipelines windows-latest now use node v18 and something changed regarding the usage of legacy openssl packages which made our builds mysteriously fail. We do not use openssl directly but I believe that webpack uses it. Googling about this issue, they do not plan on making webpack v4 compatible with Node v18, so the correct approach here would be to upgrade webpack to v5.
But since this could be a massive task, I instead implemented a set of recommended workarounds to just fix our build for now.
When we do upgrade to webpack v5 and fix this problem the right way, we can revert the following workarounds:

https://github.com/dnnsoftware/Dnn.Platform/pull/5547/commits/0541446385273dac33181f871beff0f126d61cd0 added --openssl-legacy-provider to make our build work with the newer node v18
https://github.com/dnnsoftware/Dnn.Platform/pull/5547/commits/755668af0394d4951a2c7d2cffe9340337c0fd02 For some reason, could not confirm what version of node azure was using, so this enforced using v18+
https://github.com/dnnsoftware/Dnn.Platform/pull/5547/commits/4c78bc7f4177cbf73832f523bf2334b87f794034 lerna was no recognizing this option so I had to upgrade it to a version that would pass the unknown arguments to the build tool (yarn), before that upgrade it would fail instead of passing those unknown arguments forth.

Done in #5570


[Close #254] feat: support custom tls config

The following patch adjusts the podMonitor and serviceMonitor resource. The static configuration tlsConfig is replaced so that the TLS configuration can be configured individually by the user.
The option insecureSkipVerify: true has been removed as it is a security risk. Users also have the option of redefining the insecureSkipVerify property directly via tlsConfig if necessary. With regard to the previous rbac auth option, however, this is superfluous.
Furthermore, the schema, i.e. HTTP or HTTPS, can now be defined to tell Prometheus which protocol should be used for communication.
The following sample configuration specifies that the x509-certificate-exporter encrypts requests via HTTPS and the HTTP client must authenticate itself via HTTPS (client auth).
prometheusServiceMonitor:
  tlsConfig:
    caFile: /etc/prometheus/tls/ca/ca.crt
    certFile: /etc/prometheus/tls/app2app/tls.crt
    keyFile: /etc/prometheus/tls/app2app/tls.key
    insecureSkipVerify: false
    serverName: prometheus-x509-certificate-exporter

prometheusPodMonitor:
  tlsConfig:
    caFile: /etc/prometheus/tls/ca/ca.crt
    certFile: /etc/prometheus/tls/app2app/tls.crt
    keyFile: /etc/prometheus/tls/app2app/tls.key
    insecureSkipVerify: false
    serverName: prometheus-x509-certificate-exporter

Important Note: The serverName attribute must correspond to the CommonName or a Subject Alternative Name (SAN) of the TLS certificate. If this is not the case, prometheus will reject the connection trying to match the IP address of the pod with the CommonName / SAN.
The client certificate and private key as well as the certificate of the certificate authorithy must be mounted additionally via the extraVolumes and extraVolumeMounts option. This configuration is not standard and must also be implemented by the user if TLS client authentication is required.

Here is an excerpt from my prometheus instance, which now retrieves the metrics using HTTPS authentication and encryption.

Hi @volker-raschek
This is great, everything looks good.
Thanks for opening the PR and your thorough descriptions.
Also, sorry it took ages.

:tada: This PR is included in version 3.16.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Support flatMap function in GroupedStream

flatmap function takes one element and produces zero, one, or more elements.  such as, a flatmap function splits sentences to words:
flatmap("hello world") -> "hello" "world"

please assign it to me

I'd like to do this. plz assign it to me

Can you assign it to me? I‘m working on this these days.


Fix Inf/Sup

The Monoid instances for Inf and Sup have the identity elements the wrong way around. For example, at the moment we have that:
> Sup false <> mempty
Sup (true)

:+1: Thanks!


daguike-gulp-rev-del

This is a fork of rev-del where some dude fixed a bug (I don't even know what the bug is), and then decided to not contribute it back to rev-del.
https://github.com/daguike/rev-del
Could it be blacklisted?

Yeah and also encourage them to send the fix back

I left a comment. I don't know what bug they've even fixed, though.


Serialize the options Hash

Serialize options hash in MiqAeMethod
Depends on PR https://github.com/ManageIQ/manageiq-schema/pull/105

@gmcculloug
I had to rebase


TypeError: get_encoders() got an unexpected keyword argument 'use_adapter'

import os
from keras_bert import load_trained_model_from_checkpoint

layer_num = 12
checkpoint_path = 'rubert_cased_L-12_H-768_A-12_v1'

config_path = os.path.join(checkpoint_path, 'bert_config.json')
model_path = os.path.join(checkpoint_path, 'bert_model.ckpt')
model = load_trained_model_from_checkpoint(
    config_path,
    model_path,
    training=False,
    use_adapter=True,
    trainable=['Encoder-{}-MultiHeadSelfAttention-Adapter'.format(i + 1) for i in range(layer_num)] +
    ['Encoder-{}-FeedForward-Adapter'.format(i + 1) for i in range(layer_num)] +
    ['Encoder-{}-MultiHeadSelfAttention-Norm'.format(i + 1) for i in range(layer_num)] +
    ['Encoder-{}-FeedForward-Norm'.format(i + 1) for i in range(layer_num)],
)

I try to run this code from tutorial
and this error arises:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-23-a18dfbad0880> in <module>
     15     ['Encoder-{}-FeedForward-Adapter'.format(i + 1) for i in range(layer_num)] +
     16     ['Encoder-{}-MultiHeadSelfAttention-Norm'.format(i + 1) for i in range(layer_num)] +
---> 17     ['Encoder-{}-FeedForward-Norm'.format(i + 1) for i in range(layer_num)],
     18 )

TypeError: load_trained_model_from_checkpoint() got an unexpected keyword argument 'use_adapter'

By the way, i tried to upgrade keras-transformers - it didnt help

pip install --upgrade keras-bert

这是keras-transformer版本问题，换成0.31.0就ok了

这是keras-transformer版本问题，换成0.31.0就ok了

ok

这是keras-transformer版本问题，换成0.31.0就ok了

大哥牛逼

This is an out-dated issue. See #190 and #191 if you still want to use the adapter.

这是keras-transformer版本问题，换成0.31.0就ok了

Please read the last two lines carefully:

TypeError: load_trained_model_from_checkpoint() got an unexpected keyword argument 'use_adapter'
By the way, i tried to upgrade keras-transformers - it didnt help

你好，可以使用的Bert模型都有哪些？albert,robert可以用吗

这是keras-transformer版本问题，换成0.31.0就ok了

Please read the last two lines carefully:

TypeError: load_trained_model_from_checkpoint() got an unexpected keyword argument 'use_adapter'
By the way, i tried to upgrade keras-transformers - it didnt help
你好，可以使用的Bert模型都有哪些？albert,robert可以用吗

What is the solution to this problem ?? I am using 0.69.0 which still has the problem, do I need to down grade to 0.31.0?

pip install keras-bert==0.81.1 slove the problem

大哥牛逼

Try pip install keras-transformer==0.33.0


Fix broken link

In content/{en, ja, ko, zh}/docs/setup/production-environment/windows/user-guide-windows-containers.md:
https://gist.github.com/{wagnerandrade => 19WAS85}/5424431

thanks
/lgtm
/assign @tengqm

/lgtm
For English and Chinese.
I'm not gonna approve this because I'm unsure this is okay for all localizations involved.

/lgtm
For Korean.
Thanks for update.

/approve
For Chinese.

/approve
for Korean 👍

/assign @inductor

/lgtm
/approve

/assign @sftim

@tengqm now the other localizations are approved, will you please approve?  en is the only one left?


Use pathlib instead of strings for paths!

At least we should replace hard coded stuff like this:
https://github.com/choderalab/covid-moonshot-ml/blob/hallucinate-fragalysis/scripts/hallucinate_fragalysis.py#L117
f"{in_dir}/{compound_id}/{dimer_s}/{best_str}"

with os.path.join.
But I guess using pathlib instead of using strings at all is even better.

Right idea, but this issue is too general.


Shim executables don't ensure termination of child processes

Duplicating from https://github.com/chocolatey/choco/issues/2272. Both package managers share this problem.
What You Are Seeing?
Abrupt termination of a shim executable causes its child to be orphaned. The child becomes a daemon process.
Note that this doesn't apply to Ctrl+C from the CLI, which is treated differently by the terminal or OS. The problem occurs when the process is killed through any other method.
What is Expected?
When a shim executable terminates for any reason, all work should be stopped, i.e. the subprocess should terminate. It should either:

Avoid spawning a subprocess.
Use the job objects API, ensuring that when it terminates, its descendants terminate.

How Did You Get This To Happen? (Steps to Reproduce)
This may happen due to programmatic termination of a shim process, or simply by clicking "End Process" in Task Manager or Process Explorer. Programmatic termination may happen in a build system that involves shelling out to various build tools such as sass. An error in one of the tasks may cause termination of the entire build, which may involve programmatic termination of immediate child processes, causing the orphan problem described above.
Programmatic termination is particularly important for watching-and-restarting, which is common in build systems. Currently, it's not viable to programmatically auto-restart executables generated by Scoop, because the "real" process doesn't die.

kiennq's shim uses jobs. See https://github.com/kiennq/scoop-better-shimexe/blob/f334a2ca21d231c0b244bb9b14b219355e60a616/shim.cpp#L212
To switch to his shim, see https://github.com/lukesampson/scoop/issues/3634#issuecomment-750371232

Thanks for the pointers. This is also a duplicate of https://github.com/lukesampson/scoop/issues/3294 which I failed to find before opening the issue.
Testing this with watchexec. 71's version worked when invoked manually from the terminal, but when called indirectly via make, was failing with Error -1073740940. kiennq's version seems to work in both environments, and terminates the child process properly. Issue seems to be solved. Thanks! Perhaps it should be the default, but that's a beaten horse already. 🐴🙂


Need CI pipeline to run BDD tests when making changes to master

As a developer
I need BDD unit tests to be run automatically when pushing to or opening a PR for master
So that I can have some assurance that changes to master have not broken existing functionality that passes those tests
Details and assumptions

CI tests will be run using GitHub Actions
There will be a file .github/workflows/bdd.yml added to this repository and configured to run these tests
Test coverage should not decrease in order for the changes to master to be accepted

Acceptance criteria
Given a proposed change to the master branch
When that change is attempted to be merged, or has a PR opened for it
Then GitHub Actions will automatically run the BDD unit test suite for that change

We will need to wait on this until the BDD unit is covered in class.


Analyze GoC SEA with Microsoft

Describe the issue
Once Microsoft has gained access to GoC GitHub repos for the Azure SEA, we want to try it out and see what it offers, especially around upkeep, updates and security patches.
Which Sprint Goal is this issue related to?

Note: 'Milestone' is a ZenHub term that we use synonymously with 'Sprint'.

The 'Milestone' description (created in ZenHub) should clearly list Sprint Goals. This section should indicate which 'goal' this issue is related to.
Additional context

GoC Government of Canada
SEA Secure Environment Accelerator
PoC Proof of Concept

Definition of done

Determine if a demonstrator can be applied within Phase 2 or requires new space
Feedback/advice/next steps from MS documented

Done.  Microsoft has said the SEA is good


[Suggestion] Crafttweaker support

The mod is amazing and could be even more with a crafttweaker support! :D

Hi,
In theory it already has CraftTweaker support 😁
I have done some basic testing of CraftTweaker and it seems to work. For example:
import mods.emergingtechnology.Processor;

Processor.addRecipe(<minecraft:diamond>, <minecraft:redstone>);

Please let me know if you need more information or something doesn't work.
Thanks!


Fixed issues with multiple profiles

When you have a lot of provisioning profiles, spaceship times out when it tries to fetch them
(Spaceship.provisioning_profile.all, Spaceship.provisioning_profile.app_store.all, Spaceship.provisioning_profile.ad_hoc.all, Spaceship.provisioning_profile.development.all, Spaceship.provisioning_profile.app_store.find_by_bundle_id("com.krausefx.app"))
I've added a new option skip_fetch_profiles which sould be used along with skip_name_verify to avoid timeouts with multiple profiles.
This could be only one option, but I didn't know if you wanted to keep thing more tidy and have different names reflecting what will do each option

Thanks for the pull request @ericertl. How about a different approach: Introducing a new command: sigh create_profile which will create a profile using the given parameters. What do you think?

I'm cool with that approach as long as it doesn't fetch profiles.
I just wanted to save you some time and to contribute to Fastlane

Okay, let's keep it like this. The only thing I'd like to be changed: Let's merge skip_fetch_profiles and skip_name_verify and into one option and name it :skip_fetch_profiles.

Merged both options into skip_fetch_profiles

Looks great, thanks for working on this @ericertl :+1:


Can't figure out how Spread Splitter works

Hello everybody,
Kindle Comic Converter 5.5.2
I've converted several cbr/cbz to .mobi thanks to this very helpful program.
But I can't manage to make spread splitter work. In the generated mobi files, the double-pages are always two single pages even when I fully check the box.
The only time it "worked" was because the double page was litterally two pages on one jpg.
I'm not sure what I'm missing here therefore I need help. Thanks
Maybe I just misunderstood the intent of this feature and instead of gathering two pages two be full, it's rather splitting a full-width double-page in two single pages ?
For instance, here is a "double-page" not displaying as a spread.

The only time it "worked" was because the double page was litterally two pages on one jpg.

I'm not sure what I'm missing here therefore I need help. Thanks Maybe I just misunderstood the intent of this feature and instead of gathering two pages two be full, it's rather splitting a full-width double-page in two single pages ?

It's page splitting, not page gathering :wink:
It takes a jpg containing 2 pages (width > height) and splits it and/or rotates it
C'est du fractionnement de pages, pas du regroupement de pages :wink:
Il prend un jpg contenant 2 pages (largeur > hauteur) et le divise et/ou le fait pivoter
Double page parsing mode.
0: Split
1: Rotate
2: Both
[Default=0]

see/voir
https://github.com/ciromattia/kcc/blob/4ec4c9966c727d6dac44507d34607bd7d2c5ed5c/kindlecomicconverter/image.py#L120

Haha yes, I should have guessed that.
So I should rather find a way to combine two pages in order to create a full-width spread. Maybe you know some way to do so ?
But I'm not even sure I want to recreate my generated .mobi from my cbz files. It's not even that uncomfortable to not have a full-width spread in the end
(Merci pour la traduction en français ^^)

@Nurovek
je ferme le ticket
rouvrir si nécessaire


Polymer on NPM stuck on version 1.2.5

Hey,
could you please publish 1.6.1 to npm? Thanks.

This is something we need to do for 2.0!

Can we at least push v1.7.0 to NPM?

Has this gotten any attention to push the latest version? Or are you waiting until 2.0 to publish a new version on npm?

Bump. We're aiming for full Yarn support for our components to start moving away from Bower but not being able to pull in Polymer as a peer dep is stopping us from doing that. Is there anything blocking publishing 1.7 to NPM (for Yarn)?

The client-side packages in the @polymer scope are still experimental as of now. We're trying to ready all the pieces that will let published fully supported packages, but we're not there yet. We're focused on getting 2.0 out the door, and then npm/yarn support will be top priority.

2.0 is on NPM

Is it still experimental?

Also looks like all the other packages in the @polymer scope are still alpha versions (0.0.x) - is there a timeline to bump those?

Is it still experimental?

Yes

Recently, while installing polymer2 through npm, the following message was brought to my attention:

...psst! While Bower is maintained, we recommend yarn and webpack for new front-end projects!

This message appears since late may as a npm deprecated message, and also on the bower.io and in it repo README.
Obviously it's not an easy task since the documentation and the starter kit heavily depends on bower, and Polymer/polymer is not the only repo to update, but migrating to npm seems the way to go.

@mrjoops please see #326 - it is the original issue to track npm progress

Closing this issue per https://github.com/Polymer/polymer/issues/326#issuecomment-387910751 @polymer/polymer is now maintained on NPM since version 3 🎉


next-intl/link is causing an error in tests

Description
The version I'm using: 3.0.0-beta.9
There is no problem while development but I can't fix this error in tests. I've attached a repository you can peek at that reproduces the error in the simplest way. This error occurs in all components where we've used the I18nLink component. This causes all of our component tests to fail.
 FAIL  src/components/Card/Card.spec.tsx
  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/dgknca/Desktop/next-intl-reproduce/node_modules/.pnpm/next-intl@3.0.0-beta.9_next@13.4.13_react@18.2.0/node_modules/next-intl/dist/src/link/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export { default } from './Link';
                                                                                ^^^^^^

    SyntaxError: Unexpected token 'export'

      10 |   return <Link href={href} locale="en" />;
      11 | }
    > 12 |
         | ^

      at Runtime.createScriptFromCode (node_modules/.pnpm/jest-runtime@29.6.2/node_modules/jest-runtime/build/index.js:1496:14)
      at Object.<anonymous> (src/components/I18nLink.tsx:12:54)
      at Object.<anonymous> (src/components/Card/Card.tsx:12:58)
      at Object.<anonymous> (src/components/Card/Card.spec.tsx:7:54)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        0.758 s
Ran all test suites.
 ELIFECYCLE  Test failed. See above for more details.

Mandatory reproduction URL (CodeSandbox or GitHub repository)
https://github.com/dgknca/next-intl-jest-error-reproduce
Reproduction description
Steps to reproduce:

Open reproduction
Run tests with pnpm test command
See the error SyntaxError: Unexpected token 'export'

Expected behaviour
No error

yes, it works. thanks!

Hello @amannn. I have the same error in version<EMAIL_ADDRESS>with<EMAIL_ADDRESS>I tried to solve it with the solution above, but I was not successful.

@cjambrosi Can you create a minimal reproduction and open a new issue that references it?

@amannn , thanks for replying. I opened a new issue and created a repository to reproduce the error.


fix sandbox dependencies

I'm assuming that invariant must come from the devDependencies present. It might not be. We could just list it as a new dependencies, as that seems to solve the problem manually within codesandbox.  Waddya think?
I think the problem is that devDependencies don't show up in the sandbox. https://github.com/codesandbox/codesandbox-client/issues/2794

@jaketrent did you try the suggestion i put in the issue https://github.com/pluralsight/design-system/issues/1545#issuecomment-760350441

@jaketrent did you try the suggestion i put in the issue https://github.com/pluralsight/design-system/issues/1545#issuecomment-760350441

@danethurber Sorry, I didn't see that suggestion.  No, I did not try it.  I did it manually in a codesandbox at one point, and it worked.  I didn't want to add it, because it didn't make sense. We're not importing it anywhere.  It's not a named dependency in our projects.  Something is using it.  And my guess was that that something was the thing that should be added to the codesandbox dependencies instead. I'm guess it's one of the things that we have in devDeps, since everything else mentioned in the src is in deps.  Based on the experiences in this thread: https://github.com/codesandbox/codesandbox-client/issues/2794#issuecomment-542195016

@danethurber Sorry, I didn't see that suggestion.  No, I did not try it.  I did it manually in a codesandbox at one point, and it worked.  I didn't want to add it, because it didn't make sense. We're not importing it anywhere.  It's not a named dependency in our projects.  Something is using it.  And my guess was that that something was the thing that should be added to the codesandbox dependencies instead. I'm guess it's one of the things that we have in devDeps, since everything else mentioned in the src is in deps.  Based on the experiences in this thread: https://github.com/codesandbox/codesandbox-client/issues/2794#issuecomment-542195016

ah, so we do.  Ok, I'll look at that route.  Thanks!

ah, so we do.  Ok, I'll look at that route.  Thanks!

@danethurber k, changed and ready for another review.

@danethurber k, changed and ready for another review.


fix issue with hyphens in domain name

fix #468

Thank you for reporting the problem and sharing the fix, this is now merged in version 1.3.


test fixture setup logging improvements

https://github.com/fedimint/fedimint/pull/1870#discussion_r1133217362
First log echo -n "starting <service> ...  and when it starts, log echo "done"

This is outdated


Animations not correctly imported in godot 4

Godot version
4.0a12
System information
Windows 11
Issue description
When importing assets from blender, the included animations are not played as intended. The motions of the animated objects dont correspond correctly to the ones in blender. I tested with the same file imported into Godot 3 where it worked without issues.
Steps to reproduce
Make a rigged model in blender. Animate it. Exxport it to gltf. Import into Godot 4.0a12. Try to play the animations from the AnimationPlayer.
Minimal reproduction project
testproject.zip

Did you try disabling optimizer?

do you mean in the export options of blender "Optimize Animation size"?

No, Godot has built in optimization, this sometimes leads to losing entire tracks on import.

Thanks! This indeed was the issue. thank you very much!

np :)

Duplicate of https://github.com/godotengine/godot/issues/58968 (same cause).


0.6 compatibility

Main changes:

removed references to mutable require.paths,
replaced/removed references to sys,
made the example work,
a bit of refactoring (unused requires).

Test and example still work on node v0.4.12.

Thanks for this patch.  Quick question, what version of Node.JS is Journey intended for now?  Can't find it anywhere.

Weird, Cause I was trying it with Node version 0.4.7 and it still wasn't working.  Might have been my environment. O well.
Anyways, I have been woking with your updated branch,  mmalecki:0.6-compatibility and everything has been working as expected.  Thanks for updating the module!

done

awesome, thanks!

thanks!


Add permission level to Group

We can now set the permission on the group create but we don't have a way to fetch what permission level this group has afterwards.
Can we add a new field to Group called permissions that returns a GroupPermission.
It may also be nice to add functionality to groups to change permission levels after create with a updatePermissions function but that's more a nice to have.

Will add a way to show current permissions.
The permissions model for a group is set in stone once the group is created, but we are going to add more permissions models that include flexible policies like "group admins can do X". Then the admin list will be mutable.
Doing it that way makes the security model easier to reason about. Less room for funny-business if the core policies are immutable.

Another request is to be able to see who the group admin is. So maybe a field like group_admin that returns a member? Unless you think that information should be private then maybe just a is_admin to see if the person viewing is the admin.

Also interested in knowing if it would be technically possible to validate that someone is the admin of a group in our backend? To add features for the admin out of the protocol (1st feature in mind : name the group before it's part of the protocol)

This seems to exist: https://github.com/xmtp/libxmtp/blob/0a3787f023de5b9de510c11dcb7625265597ca09/bindings_ffi/src/mls.rs#L1263


Add posts 0000-01-02_jaga9505

This pull request user jagadish950

Have first branch

This pull request jaga9505 floders


portico: Add headings to /for/communities.

Add headings to break up the page.
Remove badly worded reference to /why-zulip.
I tried to add buttons to the bottom of the page, but didn't know how to fix the CSS.

Testing plan:
Manual testing.
GIFs or screenshots:

Cherry-picked in #19147 after fixing.


Follow up items for AWS SDK v2 migration

Creating this issue to track the following items as part of a follow up for migrating AWS SDK to v2 in discovery-ec2 and repository-s3:

https://github.com/opensearch-project/OpenSearch/pull/7372/files#diff-05a1e15342dc93417ff7096c9c7fd764f592dc43fb27bc016ab7b6d6788693cbR157

I think this change effectively will move us from IMDSv1 to IMDSv2. Something we should consider as a fast follow-up

https://github.com/opensearch-project/OpenSearch/pull/7372/files#diff-d2df6c057bdc71a1a9f9c590a229241a4f1a36d255fa1ddcec686b7b1c0fc590R118

Would have preferred try-with-close for BufferedReader

https://github.com/opensearch-project/OpenSearch/pull/7372/files#diff-d2df6c057bdc71a1a9f9c590a229241a4f1a36d255fa1ddcec686b7b1c0fc590R120

nit: This should be EC2

Opened an issue for s3ThirdParty test and yamlRestTest region related failures: #7866

For moving from IMDSv1 -> IMDSv2 I opened https://github.com/opensearch-project/OpenSearch/issues/7916.


Issue #3208: Fix for py logging formatter

Please refer to https://github.com/robotframework/robotframework/issues/3208

apply logging formatter as stated here: https://dzone.com/articles/python-custom-logging-handler-example

This change needs some tests and possibly also an update to documentation.

I don't see any test for RobotHandler at all!? Do you have any suggestions where to integrate?
In the stack post 1 you can see the motivation for the fix.

I'm sure there are tests for this in the atest directory. See atest/README rst for details.

Acceptance tests for logging using logging are at
https://github.com/robotframework/robotframework/blob/master/atest/robot/test_libraries/logging_with_logging.robot
and test data file executed by those tests at
https://github.com/robotframework/robotframework/blob/master/atest/testdata/test_libraries/logging_with_logging.robot
and finally the library these tests use is at
https://github.com/robotframework/robotframework/blob/master/atest/testdata/test_libraries/LibUsingPyLogging.py
How all this works together is explained at atest/README.rst.


sparse submit error: TypeError: pre_submit() takes 3 positional arguments but 4 were given

Using sparse submit to submit a topology to storm running on the localhost. There is full error message:
Traceback (most recent call last):
File "/usr/bin/sparse", line 11, in
sys.exit(main())
File "/usr/lib/python3.4/site-packages/streamparse/cli/sparse.py", line 79, in                                                                                main
args.func(args)
File "/usr/lib/python3.4/site-packages/streamparse/cli/submit.py", line 281, i                                                                                n main
timeout=args.timeout)
File "/usr/lib/python3.4/site-packages/streamparse/cli/submit.py", line 165, i                                                                                n submit_topology
_pre_submit_hooks(override_name, env_name, env_config, options)
File "/usr/lib/python3.4/site-packages/streamparse/cli/submit.py", line 100, i                                                                                n _pre_submit_hooks
pre_submit_fabric(topology_name, env_name, env_config, options)
TypeError: pre_submit() takes 3 positional arguments but 4 were given

I faced similar problem, so fixed my fabfile.py
$ cat fabfile.py
def pre_submit(topology_name, env_name, env_config, options):

With streamparse 3.10.0 we added options to the list of arguments sent to the pre_submit and post_submit hooks. I apologize for the backward incompatible change. We should have tried to apply introspection to see how many arguments the hook takes.

Hello Guys,
First great work you guys are doing!
I am also affected by this issue. Any idea when a fix is coming?


[CIVP-24576] FIX relax SQL type checking in civis_file_to_table

This pull request relaxes SQL type checking in civis.io.civis_file_to_table, by casting to VARCHAR when type inconsistency is detected for a given column and at least one input file has VARCHAR.

[x] (For Civis employees only) Reference to a relevant ticket in the pull request title
[x] Changelog entry added to CHANGELOG.md at the repo's root level
[x] Description of change in the pull request description
[x] If applicable, unit tests have been added and/or updated
[x] The CircleCI builds have all passed

@skomanduri Thank you for catching the column name issue -- this PR is ready for another pass!


fix: Sentinel error instead of nil check.

Changes:

fix: Sentinel error instead of nil check.
fix: Move router pipeline creation under router.
create utils.go in router package.

@michaljurecko KCP test still fails

@Matovidlo link please?

@michaljurecko https://github.com/keboola/keboola-as-code/actions/runs/9903811027/job/27359999464?pr=1906

(I am rebasing it)

(rebased)


Torch mode implementation

@ekreutz could you please look into merging this pull request. This is the torch mode implementation only, I've removed everything else. The original author of this pull request doesn't seem to be activate and it would be really useful to have this functionality included in this package.

@ekreutz  correct me if I'm wrong but if FLASH_MODE_TORCH isn't available there is already a logic handling this case in CameraSource.java line 840.
if (mFlashMode != null) {
            if (parameters.getSupportedFlashModes() != null) {
                if (parameters.getSupportedFlashModes().contains(
                        mFlashMode)) {
                    parameters.setFlashMode(mFlashMode);
                } else {
                    Log.i(TAG, "Camera flash mode: " + mFlashMode + " is not supported on this device.");
                }
            }
        }

and setting the flash mode to on doesn't act like torch mode anyways since it is not continuously enabled. For that I believe the we would need to add a flashmode property.

hey this pr what implmented is working

it is working just not getting a lot of traction with the repo owner to merge it.

@ekreutz FLASH not working i have tested with android phone


Sync v24.5 and develop

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[ ] No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[ ] All tests pass: $ python run-tests.py --all (or $ nox -s tests)
[ ] The documentation builds: $ python run-tests.py --doctest (or $ nox -s doctests)

You can run integration tests, unit tests, and doctests together at once, using $ python run-tests.py --quick (or $ nox -s quick).
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

I'll fix the release and the branches.

Talked to @Saransh-cpp

I will fix v24.5 based on #4259
This one can be closed until the final release


How to set coefficient_restitution ? Can't get ball to bounce.

I've edited the fixtures/3D/examples/example.json to use a sphere
{
    "scene_type": "distance_barrier_rb_problem",
    "max_iterations": 1000,
    "timestep": 0.01,
    "rigid_body_problem": {
        "coefficient_restitution": 1,
        "gravity": [0, -9.8, 0],
        "rigid_bodies": [{
            "mesh": "sphere.obj",
            "position": [0, 3, 0],
            "rotation": [30, 135, 0],
            "linear_velocity": [0, 0, 0],
            "angular_velocity": [0, 0, 0]
        }, {
            "mesh": "plane.obj",
            "is_dof_fixed": [true, true, true, true, true, true],
            "position": [0, -1, 0]
        }]
    }
}

I changed coefficient_restitution = 1 hoping that this would get the sphere to bounce off the ground plane but it's still sticky:
https://github.com/ipc-sim/rigid-ipc/assets/2241689/be530834-38f1-42bc-b0f8-1e0d3b9db6f8
I don't think I understand how to set coefficient_restitution. All of the 3D examples set it to -1. But I thought this value was setting the coefficient of restitution which is a non-negative quantity.
How should I adjust my .json to see a bouncing ball?

Hi Alec, actually the coefficient_restitution is broken as in our paper we say: "Our current formulation does not provide direct control for restitution." The parameter was left in from a legacy attempt that was only implemented in 2D (I don't think it is even compatible with IPC). I have found the implicit Euler time integrator dampens out the motion so that bouncing doesn't happen at "large" time step sizes (e.g., the 0.01 you are using). The alternative to reducing timestep would be to switch time integrators, but I remember we had difficulty implementing other integrators that were reliably stable.


MRG: Update pub list

I ran this locally to update the publication list.

Please merge if you're happy with the changes

Thanks for the look @jasmainak


⚠ Mobitopup has degraded performance

In 4d39ded, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 10462 ms

Resolved: Mobitopup performance has improved in 9b29b47.


Add relevant use cases

Description of the Change
This pr adds relevant iroha use cases. Please review and pay attention to huge introduction section. I describe more in Possible Drawbacks.
Benefits
Documentation with relevant use cases.
Possible Drawbacks
The introduction to the use cases is somewhat big. Although, it is not directly relevant to use case section, it provides useful context for it. We need to think what can we do with it, maybe we can move part of the introduction section to other docs?

I have recently discussed with @grimadas his new use case proposal, and what I've seen looks really nice, can't wait to see it updated here

Please reformat headings using the single style "Title Case". Please use this tool for checking hard cases.
Example:
Use case scenarios ->  Use Case Scenarios


Support multiple delimited recipient addresses sharing the same TO/CC/BCC name

The API to(@Nullable final String name, @Nonnull final String address) should be able to handle comma or semicolon separated address for the same To name. This can be useful when mailing a group of users while addressing them as a group in case they don't have a separate dedicated group mail they can subscribe to:
to("Maintenance group", "john@abc.com;richard<EMAIL_ADDRESS>
Same goes for cc() and bcc().

Released in 4.3.0.


support for multiple model occurence in perf main

Before you start, read CONTRIBUTING.md and the guide for diagnostic developers.
Please discuss your idea with the development team before getting started, to avoid disappointment later. The way to do this is to open a new issue on GitHub. If you are planning to modify an existing functionality, please discuss it with the original author(s) by tagging them in the issue.

Tasks

[x] Create an issue to discuss what you are going to do, if you haven't done so already (and add the link at the bottom)
[x] Give this pull request a descriptive title that can be used as a one line summary in a changelog
[x] Make sure your code is composed of functions of no more than 50 lines and uses meaningful names for variables
[x] Circle/CI tests pass. Status can be seen below your pull request. If the tests are failing, click the link to find out why.
[x] Preferably Codacy code quality checks pass, however a few remaining hard to solve Codacy issues are still acceptable. Status can be seen below your pull request. If there is an error, click the link to find out why. If you suspect Codacy may be wrong, please ask by commenting.

Modified recipe/diagnostic

[x] Assign the author(s) of the affected recipe(s) as reviewer(s)

If you need help with any of the tasks above, please do not hesitate to ask by commenting in the issue or pull request.

Closes #1605
Fixing Klaus' issue with SMPI (and also perfmetrics) not supporting the use of a single model with different ensemble/experiment. Will also change dataset name in the relevant plots for differentiation.

Is this ready for testing?
If so, please mark it as ready.

Was wanting to wait for @zklaus feedback to see if it fixes his problem before marking ready. Ready from my side though.

Just gonna mark this as ready since there's been no word from @zklaus and I guess other people can test it just as well knowing what the issue was.

@mattiarighi or @zklaus It would be great if you could have a go at reviewing/testing this before the ESMValTool v2.0.0 feature freeze next week?

Will test once @zklaus has approved.

@bettina-gier do you want to try the suggested change?

Testing now but just looking at the code I think the change is correct, my previous test was only with 2 ensemble members so I didn't have that issue. Also thinking if there's a better way to do it than splitting it in 2 loops.

Testing now but just looking at the code I think the change is correct, my previous test was only with 2 ensemble members so I didn't have that issue. Also thinking if there's a better way to do it than splitting it in 2 loops.

Sounds great, Bettina!
I don't see a straightforward way to put them into the same loop(s).
But indeed one can put these two statements outside the loop (I updated above):
             experiments = metadata_att_as_array(info_items, "exp")
             ensembles = metadata_att_as_array(info_items, "ensemble")

Updated with your fix, works fine for me. Thanks for testing and finding the bug and fix!
I found a way to leave it in the single loop to check if the name already has the experiment appended before appending again, I'll attach it if you want to see. However, your version results in more consistent naming as it will always have dataset - experiment - ensemble, whereas the 1-loop version will append first whatever differs first.
  ; Extend model name by ensemble/experiment on multiple occurence
  if (.not. (dimsizes(datasetnames) .eq. \
      count_unique_values(datasetnames))) then
    new_datasetnames = datasetnames
    experiments = metadata_att_as_array(info_items, "exp")
    ensembles = metadata_att_as_array(info_items, "ensemble")
    do imod = 0, dimsizes(datasetnames) - 1
      do jmod = 0, dimsizes(datasetnames) - 1
        if imod.eq.jmod then
          continue
        else
          if (datasetnames(imod) .eq. datasetnames(jmod)) then
              if ((experiments(imod) .ne. experiments(jmod)) .and. \
                  (all(str_split(datasetnames(imod), " ") .ne. \
                   experiments(jmod)))) then
                new_datasetnames(imod) = new_datasetnames(imod) + " " + \
                                          experiments(imod)
              end if
              if ((ensembles(imod) .ne. ensembles(jmod)) .and. \
                  (all(str_split(datasetnames(imod), " ") .ne. \
                   ensembles(jmod)))) then
                new_datasetnames(imod) = new_datasetnames(imod) + " " + \
                                          ensembles(imod)
              end if
          end if
        end if
      end do
    end do
    datasetnames = new_datasetnames
    delete(new_datasetnames)
  end if

Updated with your fix, works fine for me. Thanks for testing and finding the bug and fix!
I found a way to leave it in the single loop to check if the name already has the experiment appended before appending again, I'll attach it if you want to see. However, your version results in more consistent naming as it will always have dataset - experiment - ensemble, whereas the 1-loop version will append first whatever differs first.

Great, thanks! Hope this will be fixed in the next release.

@YanchunHe or @axel-lauer Do you think you could find someone to try this out and approve the pull request? If it gets approved and merged before Monday morning, it can still be included in v2.1 of the tool.

I am testing this right now...

We'll do the feature freeze around 3:30 PM CEST today.


Dataset ids

This adds name, guid etc. to the Dataset object. Still just a skeleton implementation.

Looks great, thanks @mbaudis! I've made a few comments above --- basically, I think we need to clarify id/name/guid at the top level. @diekhans, I'm sure you have something to say on this...

@jeromekelleher
 basically, I think we need to clarify id/name/guid at the top level.

Exactly; see my comment on https://github.com/ga4gh/schemas/pull/397 and elsewhere ...

@jeromekelleher Also, keep in mind that we're working on the metadata branch https://github.com/ga4gh/schemas/blob/metadata/src/main/resources/avro/metadata.avdl

@jeromekelleher @diekhans @dglazer @helenp
I've changed the PR to just add name to Dataset (and change the ```id`` comment to locally. Pls. vote, for moving this into master.

+1

I agree with @jeromekelleher re reverting the "biosample" comment changes.
Other than that, +1.

@dglazer @jeromekelleher Reverted the comments, but not feeling that good about something logically wrong & just doing it for procedural reasons.
Sample will be Biosample (is so already on the metadata branch, with PR and votes); and the comment reference Sample from the Experiment object is void (as of right now) which wouldn't be different when changing it to any other name. Just going with this would have saved some overhead, even if I didn't document the reasoning.


Things to fix or look at asap

General

[ ] Timestamp columns should have a consistent name throughout the package
[ ] Generally just have a timestamp column, not "Year" in addition?
[x] Own-line comments should be '#' followed by space followed by a capitalized letter
[ ] Datasets should be checked for consistent rep, plot, subplot
[x] Function documentation should say "XXX data" not "Return XX data"
[ ] Do we want the summary functions?
[ ] Naming consistency: in general let's use this_column not this.column or thisColumn
[ ] At end run code through styler package?

Tests

[ ] Once metadata is updated then other tests (e.g. expect_is(dat$Year, "integer") in test.fd_remote_sensing.R can be removed

fd_belowground.R

[x] fd_soilCO returns an NA DateTime column
[ ] Add fd_soilCO to forte_table_metadata.csv

fd_leaf_physiology.R

[ ] Add all tables to forte_table_metadata.csv

fd_litter.R

[ ] fd_lai is computing derived data (see discussion in #17 ); do we want to keep it?
[ ] Add all tables to forte_table_metadata.csv

fd_remote_sensing.R

[ ] Add all tables to forte_table_metadata.csv

fd_photosynthesis has multiple timestamp/date columns (HHMMSS, Timestamp, DateTime); clean up, remove

Let's remove the field descriptions in functions' documentation entirely and just depend on metadata table--that would be a LOT easier. So we'll want a fd_metadata(dataset = NULL) function that returns that information.

I am revisiting all the column heading x_x stuff now.


Invalid argument(s): Failed to load dynamic library 'libiris_event_handler.so': dlopen failed: library "libiris_event_handler.so" not found

Describe the bug
Added all the example code from the agora website  [https://docs.agora.io/en/interactive-live-streaming/get-started/get-started-sdk?platform=flutter](official agora website). When testing the live stream from the android app live stream was not working. On the Console, it throw the error :
Invalid argument(s): Failed to load dynamic library 'libiris_event_handler.so': dlopen failed: library "libiris_event_handler.so" not found
To Reproduce
Steps to reproduce the behavior:

Go to [https://docs.agora.io/en/interactive-live-streaming/get-started/get-started-sdk?platform=flutter](offical agora website)
Add all the code from site to the flutter app.
Run app
Select host option
Click on the join

Expected behavior
Using example code from the official site of agora live stream example should be working.
Screenshots

Smartphone :

Device: Pixel 5 android emulator
OS: Android 11 (API 30)

I think a reproducible demo for this issue if helpful.

I have listed steps in "To Reproduce" section

i had this issue yesterday after upgrade to 6.0.0, too. like you, i had the issue on emulator, not on a real device.
Smartphone

Device: Google Pixel 3 Android Emulator
OS: API 29 Android

Only support x86_64  arch for the emulator.

Same issue after upgrade to 6.0.0, on real device Xiaomi Redmi 4 Pro

same issue

here it what i get as error

can any one help please

I'm facing same issue. have anyone got the solution?

any sollution about this error.?

Any solution about this error ??

Any solution about this error ??

Any solution??

If you meet this error, please check the steps below:

If you run on an android emulator, the libiris_event_handler.so only support x86_64  arch
Please check pubspec.lock if there's iris_event package, if not run flutter packages get first
Please run flutter clean first before building


Fix Esc key event and various fixes

A bunch of cleanup and fixes, mainly to the showAlways and floating options, as well as fixing the Esc key handler

hi bergie,
i know this is quite a bunch of things. but it would be great if you could comment on things you do not like so we can push this forward and eventually get it merged. we have more stuff (new plugins and core fixes) we would like to create pull requests. but as things did not happen in branches, its rather a bunch of code...
i am on irc today (and friday too) if you want to discuss
cheers,david

@colinfrei will create a new (sorry, even a bit bigger than this) request from our branch that we rebased on your master today. and he will close this request, as all the stuff is contained in the new request we will do.
we now painfully rebased our branch on yours, i think if you merge this request things might get confused again ;-)


Error: the "file" argument must be of type string. received an instance of Object. (when spawning an electron child process)

Type: regression
System Information:
CPUs | Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12 x 2592)
GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off
Memory (System) | 15.73GB (2.79GB free)
Screen Reader | no
VM | 0%

Enabled extensions:
Extensions: none
Version with bug:
Version: 1.75.0 (system setup)
Commit: e2816fe719a4026ffa1ee0189dc89bdfdbafb164
Date: 2023-02-01T15:23:45.584Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: No
and
Version: 1.76.0-insider (system setup)
Commit: a7d49b0f35f50e460835a55d20a00a735d1665a3
Date: 2023-02-08T05:24:04.744Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: Yes
Latest version without bug:
Version: 1.74.3 (system setup)
Commit: 97dec172d3256f8ca4bfb2143f3f76b503ca0534
Date: 2023-01-09T16:59:02.252Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: No

Steps to reproduce:

install 1.74.3 version
clone reproduce repository. TL;DR of it is: spawnSync(electron);
open repository folder
install dependencies using npm i
run "Run Extension" configuration

open command palette (ctrl+shift+p)

choose Hello World
on latest working version, a window would open:

install 1.75.0 version
repeat 5-7
an error message appears:

Any help would be greatly appreciated since we have been unable to find a workaround. @deepak1556

Problem persists in 1.76.0

I am also seeing this error in VSCode when opening a folder with a C# .sln file.  It started after a recent update and was never present before.
Error!
The "file" argument must be of type string. Received an instance of Object

Version: 1.81.0-insider (Universal)
Commit: 02d3b49d8035a9b30db3b0ae706796af9b1a4260
Date: 2023-07-17T05:33:53.966Z
Electron: 22.3.14
ElectronBuildId: 21893604
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.6.0

.NET Runtimes
Microsoft.AspNetCore.App 3.1.32 [/home/jesse/.dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.19 [/home/jesse/.dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.32 [/home/jesse/.dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.19 [/home/jesse/.dotnet/shared/Microsoft.NETCore.App]

.NET SDKs
3.1.426 [/home/jesse/.dotnet/sdk]
6.0.411 [/home/jesse/.dotnet/sdk]

OS
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.2 LTS
Release:        22.04
Codename:       jammy

This changed with our move to use utility process for the extension host which now has a builtin electron module https://github.com/electron/electron/blob/main/lib/utility/api/exports/electron.ts that conflicts when resolving the npm package. You can either fork a process from the extension and perform the electron application launch from there or use absolute path to workaround this issue.
diff --git a/extension.js b/extension.js
index e79557e..b1bb371 100644
--- a/extension.js
+++ b/extension.js
@@ -1,8 +1,7 @@
 // The module 'vscode' contains the VS Code extensibility API
 // Import the module and reference it with the alias vscode in your code below
 const vscode = require("vscode");
-const electron = require("electron");
-const { spawnSync } = require("child_process");
+const { fork } = require("child_process");

 // this method is called when your extension is activated
 // your extension is activated the very first time the command is executed
@@ -23,10 +22,7 @@ function activate(context) {
   let disposable = vscode.commands.registerCommand(
     "extension.helloWorld",
     () => {
-      // The code you place here will be executed every time your command is executed
-      const spawn_env = JSON.parse(JSON.stringify(process.env));
-      delete spawn_env.ELECTRON_RUN_AS_NODE;
-      spawnSync(electron, [`${__dirname}/main.js`], { env: spawn_env });
+      fork(`${__dirname}/child.js`);
     }
   );

// child.js

const electron = require("electron");
const { spawnSync } = require("child_process");

const spawn_env = process.env;
delete spawn_env.ELECTRON_RUN_AS_NODE;
spawnSync(electron, [`${__dirname}/main.js`], { env: spawn_env });


Add pretty-formatters for Gherkin (for Java)

Is your feature request related to a problem? Please describe.
As someone who writes Gherkin feature files, I'd like to be sure my formatting is consistent across contributors to the project - whether editing in an IDE, or a text editor - and that can be automated as part of i.e. a code formatter like Spotless
Describe the solution you'd like
Add a pretty-formatter for Gherkin as a first-class citizen. This would allow taking i.e. a String, returning a String that is formatted according to pre-defined rules, and with indentation that can be specified.
I've recently implemented this in https://gitlab.com/jamietanna/gherkin-formatter and have licensed as MIT purposefully so Cucumber could take it as-is.
Describe alternatives you've considered
We write our own formatter.

Duplicate of #1662. Also see https://github.com/cucumber/common/pull/1725

But your code is really nice! Thanks for the effort :-)

Thanks @aslakhellesoy - do you think it's worth me raising a separate PR for importing my implementation?

@jamietanna this could be really usefull especially for the cucumber-eclipse plugin that currently lacks formatting capabilities.


Got confused by the merge editor

I just tried using the merge editor, and I was super confused by how to choose changes until I scrolled down and then saw that there were checkmarks that I can check.

Can you share a gif? I'm a bit confused by what confuses you...

In other words, you didn't know how to use this new feature and you figured out how to use it without any help. That's pretty great design, I would say.
"I am often confused by new things. Once I spend a moment to understand them, I am no longer confused."

Human

The demo gif was super helpful. Maybe adding a link to that gif next to the mergeEditor setting would alleviate any such confusion:

@hediet I think this is a good example

I got feedback from a friend who hit this same behavior. They had several coworkers look at this screen and they could not discover what to do the first time. Only after finding a tutorial on YouTube did they figure out that checkmarks were the mechanism.
Essentially we should show the checkmarks always even if the chunks are larger than the viewport, they should probably float. Another idea discussed was allowing you to right click in the chunk to accept it

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Reflect recent src relocations

r325826 relocated sys/boot/fdt/dts to sys/dts
r325834 relocated sys/boot to stand

These changes are fine, but I'm surprised by the number of locations that needed to change in the source.

This change:
-    _FDTDIR=$FREEBSD_SRC/sys/boot/fdt/dts
 +    _FDTDIR=$FREEBSD_SRC/dts

strips sys/ out as well, and it shouldn't. (Sorry, can't comment on the commit / line number exactly).

Cherry-picked, thanks!


Enable calling other snapps, creating accounts, ...

and deploying snapps from within a snapp.
Also, fix weird 3-way account interaction in the current examples when funding a snapp account.
This is a nice-to-have in the current mocked-blockchain situation, but a must-have once testnet is available.

Closing

calling other zkApps is tracked by #185
creating accounts from a zkapp just means sending MINA there, is implemented
deploying zkapps from a zkapp means updating its verification key & permissions -- should just be possible already, but a bit esoteric, can get a separate issue whenever its needed and turns out to not be easy to do already
the 3-way account interaction is fixed


proposal: x/pkgsite: consistent slash to search

Currently, slash to search doesn't work on the main page
What did you do?
I went to the main page and typed slash to search
What did you expect to see?
I expected a search prompt like on any other page, for example:

What did you see instead?
No slash to search on the home page

/cc @julieqiu
This doesn't need to be in the proposal process. The website team can figure it out.


Server incompatability.

The latest version of AmunRa does not work on servers because servers don't have LWJGL but the add-on requires it. Crash report: http://pastebin.com/5UFtTp2P

Removed it from everything non-client, should be fixed in next build

Doesn't the AmunRa class reference Vector3f when registering planets?

It did, which was a mistake. I changed it to the Vector3 class from micdoodle


50% of all entities missing for km200 / ip-inside

Coming from ioBroker I installed home assistant some 4 days ago to check if it is worthwhile considering to move to ha.
For ioBroker I wrote an adapter to read the ems-esp and km200 API and create the states (entities).
Compared to my ioBroker-adapter (screening the km200 API for all states),  I now get just less than 50% of the states using this custom component in ha.
I have quite some difficulties in understanding the coding practice in ha and for your component.
I can't find the logic where you select the km200 states/fields to be read.
Is this fixed or do you read through all the km200 structure?
BTW: Why are most entities inactive and have to activated manually?

I guess we can figure out it on discord.
Component present only entities which are used by HA entities and have meaningful states. Rest are not fetched as it doesn't make sense imo.
Most entities are inactive because there were people who had problems with API locked out by bosch servers, because of too many requests.


refactor: removes testing library

Removes testing library and rewrites all tests using it using vue test utils.
Signed-off-by: Philipp Rudloff<EMAIL_ADDRESS>

So this is just the switch of testing libraries and the changes related to that right? If so looks good to me!

Yep, it’s just removing testing library and changes affected tests.

One question I had was, all the isloading="true"s were changed to isloading="false"s in the App.spec file for the donut charts, wondered why that was needed?

This change is caused by the point in time of asserting the snapshot being at a different point in time of the component’s life cycle. A call to flushPromises was added to get the timing correct and that effectively delays said assertion to a slightly later point at which the loading prop is already switched to false. This is actually more accurate as that test specifically wants to wait for loading to be done.

Gotcha, yeah makes sense, thanks!


Printer is listed under the TPlink devices

Describe the bug
I installed the integration and configured my TPLink router. However, under the TPLink integration, there are now listed two devices: the TPLink router but also my Samsung Printer. The printer is handled by Samsung SyncThru integration.

Home Assistant Version: 2024.10.1
TP-Link Router Integration Component Version: 1.15.2

Hi
What is your router hardware version?

I figured out that it is due to the device_tracker entity, that the TP Link integration created for the printer. This tracker entity probably cuases the cross-reference between the printer device and the TPlink integration based on MAC address. The entity is listed on the printer device page as well.

So it is correct work. HA shows connected devices


Replace DatePicker with Material3 DatePicker

https://developer.android.com/reference/kotlin/androidx/compose/material3/package-summary#DatePicker(androidx.compose.material3.DatePickerState,androidx.compose.ui.Modifier,androidx.compose.material3.DatePickerFormatter,kotlin.Function0,kotlin.Function0,kotlin.Boolean,androidx.compose.material3.DatePickerColors)

Good evening,
Can I work on this one?

Good evening,
Can I work on this one?

Hey. Sure, go ahead!


[2.0] Documentation: fix schema create command namespace

Q
A

Type
bug

BC Break
no

Fixed issues

Summary
In the "Indexes" page, the namespace of the schema:create command seems to come from an old version of mongodb-odm. This PR fixes this mistake.
(same as #1832 for version 2.0)

Thanks @l-vo!


@gao14g first post title format

Needs spacing in the title.

@gao14g you can close this issue if it's resolved now


Defect:  event post hangs using 2 images per node.

Defect/Bug Report #314
Hi. When performing the following toy example for some configuration settings, the event post statement  hangs.
For example, this happens with 4  and 8 images, only when the images are distributed in the following way: 2 images for each node.
program prova_post
    use iso_fortran_env
    implicit none
    integer :: np, me
    type(event_type), allocatable :: snd_copied(:)[:]

    me=this_image()
    np = num_images()
    if (allocated(snd_copied)) deallocate(snd_copied)
    allocate(snd_copied(np)[*])
    if (me == 2)  print*,'I am  image 2, I am posting to 4'
    if (me == 2) event post(snd_copied(2)[4])
    if (me == 2) print*,' I am image 2, I have posted to 4'
    if (me == 4) event wait(snd_copied(2))
    if (allocated(snd_copied)) deallocate(snd_copied)
end program prova_post

OpenCoarrays Version: 1.9.0
Fortran Compiler: gfortran 7.1
C compiler used for building lib: gcc 7.1
Installation method: cmake
Output of uname -a:  Linux yoda 2.6.32-642.11.1.el6.x86_64 #1 SMP Fri Nov 18 19:25:05 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
MPI library being used: MPICH 3.2
Version of CMake: CMAKE-3.8.2

Observed Behavior
I am  image 2, I am posting to 4

(program hangs)
Expected Behavior
I am  image 2, I am posting to 4
 I am image 2, I have posted to 4

Steps to Reproduce
I am using a PBS script to run the program.
I have compiled the program using:
caf -o prova_post.x -g prova_post.f90

And I run it using the following script:
#!/bin/bash
#PBS -l nodes=2:ppn=2,walltime=04:00:00
#PBS -N caf_prova_post
#PBS -e caf_prova_post.err
#PBS -o caf_prova_post.out
#PBS  -W x="NACCESSPOLICY:SINGLEJOB"
cd $PBS_O_WORKDIR

cafrun -np 4./prova_post.x>prova_post.out

Hi, this sounds like a problem related with the MPI progress and the fact that events are currently based on MPI atomic operations. What happens if you run the same code on a single node with 4 processes?

In that case I got the expected output. I obtain the expected output if I run the same code on 4 nodes too. The problem arises only when I distribute images on 2 nodes (2 per node).

Ok, I know what is going on, I'll produce a patch in the next hour. Because of our policy, the patch may take up to 24 hours before hitting the trunk. If you need to fix this issue quickly I recommend to apply the patch yourself to your OpenCoarrays. The patch will be just few lines long.

I'm just curious: have you tried to run your code with MVAPICH?

@afanfa Alessandro, very responsive fix! I'm happy to merge this soon, but I saw over on the PR you wanted to discuss this further. I'm happy to look at it with you, or we can also try to get Damian online too.
@Ambra91 Thanks for the detailed bug report, and for using the template! It helps A LOT when people go the extra mile to help make our lives easier! Should be getting a fix out pretty soon.

Thank you for the quick response and for addressing the issue.
@afanfa I am experiencing the same problem with MVAPICH too.

@Ambra91 thanks again for such a wonderful and detailed report! 💯 Please try again using the master branch and confirm that this issue is fixed. If, not, then we'll reopen it.
Thanks again for your contribution!

@Ambra91 Can we use your code for a regression/unit test?

@zbeekman Yes, of course.


Mouse and keyboard stops working

When the application is started my mouse and keyboard stops working.
It can be solved by unhooking the monitor and using the built in macbook pro monitor, as soon the monitor is reconnected mouse and keyboard wont react to anything except caps lock again.
I believe it's the same as the issue "freezed my hackitosh right from the start. Restart required to get back. #105"
My external monitor is a DELL UD2717D

More info would be nice, what macOS, what GPU, what cable, ... also, maybe try ddcctl and report back if you have the same issue or not.


NF-kappaB binding

Hi,
Could I request a new term 'NF-kappaB binding', as a
child of 'transcription factor binding' (GO:0008134).
PMID: 15087454
Thanks,
Emily
(P06748 + IPI)
Reported by: edimmer
Original Ticket: "geneontology/ontology-requests/1771":https://sourceforge.net/p/geneontology/ontology-requests/1771

thanks www.movied.org


Translate Web-based ConfigGenerator

Add vue-i18n to translate strings
I was translate it to zh-CN

Waiting for @Aareksio review 👍

getLocale method is a mess, but it should do the job. LGTM

@Aareksio webpack dynamic require, it's webpack' s magical..

I removed the to lower case to comply with the RFC 3066

Thanks for your contribution! I'll try to hook those parts into our crowdin platform for further localization.


[WIP] NPM package of the Topologymodeler

NPM package @winery/topologymodeler
This adds the possibility to package the topologymodeler as npm package with the use of ngpackagr. This change will make it possible to use the topologymodeler in different contexts, i.e, by passing the data to it directly or by configuring it to fetch the data from an endpoint by itself. Also updates Angular version to 6 so it becomes easier to use this as dependency in latest angular-cli generated projects, which already use Angular 6.

Start and end date: 2018-05-01 - 2018-07-01

Contributors: Josip Ledic, @ledicjp

Supervisor: Karoline Saatkamp, @saatkamp; Lukas Harzenetter, @lharzenetter;  Oliver Kopp, @koppor

Current state of this:

[x] new branch topologymodeler-packaging

[x] Successfully packaged with ng-packagr ✅

[x] Created new npmjs organization "Winery" to publish this package on: @winery/topologymodeler

[x] Make endpoints configurable (see npm link for documentation)

[x] Possibility to configure a "readonly" variant (see npm link for documentation)

[x] Possibility to configure an "auto-layout on startup" option

[x] Enhance & clean up bundling process (exclude unnecessary code from package, etc.)

[x] Fully compatible with Angular 6

[x] Added hotkeys and hotkey cheatsheet

[x] refined styling of multiple components

[x] added some more elements that improve the UX

e.g., popovers instead of directly opening a new tab
graphical delete buttons for relationship templates and node templates
fixing the issue where clicking the label of a relationship template wouldn't result in a selection, etc...

Missing steps:

[ ] CI solution which automatically bundles the latest build that passes and updates the version on npm

[ ] Ensure that Travis CI passes

[ ] Ensure that you followed http://eclipse.github.io/winery/dev/ToolChain#github---prepare-pull-request.

[ ] Branch name checked. That means, the branch name starts with thesis/, fix/, ...

[ ] Ensure that the commit message is a good commit message

[x] Ensure to use auto format in all files

[ ] Change in CHANGELOG.md described

Can one of the admins verify this patch?

CQ created as CQ 16867


Get rid of @ccallable usage

Apparently it doesn't work properly. Use jl_eval_string("MyApp.julia_main") instead or something.

Or work around it...

I'll leave it in for now since I have workarounds for all issues with it.


Width to fit selected item

Can't get component in single-select mode to fit selected option's width.
I tried this CSS but it doesn't work
https://jsfiddle.net/au1k8tq5/4/

Not sure what you mean. Maybe try setting the show-labels to false?
https://jsfiddle.net/shentao/o6xh6g23/

Sorry if I didn't explained clearly, I mean when selected option with any text length, I want container to fit selected option's width. By default container has 100% width, this is not suitable for my app. In my fiddle with given CSS, long option get cropped:

This is fixed in the newest master (still to be released to NPM) when you add width: fit-content; to .multiselect class.
Please wait for the new release or download the sources and build it yourself.


[GOBBLIN-1557] Make KafkaSource getFilteredTopics method public

Dear Gobblin maintainers,
This is my first PR here, please don't hesitate to comment for me to improve!
JIRA

[ ] My PR addresses the following Gobblin JIRA issues and references them in the PR title.

https://issues.apache.org/jira/browse/GOBBLIN-1557

Description

[ ] The method was originally private, and it is useful to be able to override it in subclasses, to redefine how to get topics to be processed.

Tests

[ ] My PR updates a class without unit test

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3408 (e0e64b3) into master (384dc09) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3408      +/-   ##
============================================
- Coverage     46.52%   46.51%   -0.01%
+ Complexity    10246    10241       -5
============================================
  Files          2063     2063
  Lines         80475    80475
  Branches       8989     8989
============================================
- Hits          37443    37435       -8
- Misses        39567    39572       +5
- Partials       3465     3468       +3

Impacted Files
Coverage Δ

...in/source/extractor/extract/kafka/KafkaSource.java
5.09% <ø> (ø)

...a/org/apache/gobblin/util/limiter/NoopLimiter.java
40.00% <0.00%> (-20.00%)
:arrow_down:

.../org/apache/gobblin/metrics/RootMetricContext.java
71.87% <0.00%> (-7.82%)
:arrow_down:

...lin/util/filesystem/FileSystemInstrumentation.java
92.85% <0.00%> (-7.15%)
:arrow_down:

...gobblin/service/modules/core/GitConfigMonitor.java
81.35% <0.00%> (-1.70%)
:arrow_down:

.../org/apache/gobblin/cluster/GobblinTaskRunner.java
63.46% <0.00%> (-0.33%)
:arrow_down:

.../apache/gobblin/runtime/api/JobExecutionState.java
80.37% <0.00%> (+0.93%)
:arrow_up:

Continue to review full report at Codecov.

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

protected would work - I can change the PR accordingly. We have indeed used topic.blacklist and topic.whitelist to define topic and we need an option not based on regex but on API call, therefore the override need. Changing the PR in a bit.


Fails when no version is specified in package.json

Error description
Installed generate-changelog globally and after running it in a repository which doesn't have a version field in the package.json file, I get the following error:
TypeError: Cannot read property 'split' of undefined.
System specs
Linux Debian 9, Node.js 8.4.0 (installed with nvm), npm 5.3.0, git 2.11.0.
Full log
$ changelog -M
TypeError: Cannot read property 'split' of undefined
    at /home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/lib/package.js:55:36
    at tryCatcher (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:693:18)
    at Promise._fulfill (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:638:18)
    at Promise._settlePromise (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:582:21)
    at Promise._settlePromise0 (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:693:18)
    at Promise._fulfill (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:638:18)
    at Promise._resolveCallback (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:432:57)
    at Promise._settlePromiseFromHandler (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:524:17)
    at Promise._settlePromise (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/home/florian/.nvm/versions/node/v8.4.0/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:693:18)

It would be awesome to get support for changelogs without a specified version!


[skip ci]bugfix: change release_to_atlas.py to fit new Atlas class

class Atlas has been changed but release_to_atlas.py need to be modified too.
@panpan0000 @PengTian0
test results: http://<IP_ADDRESS>/job/BuildRelease/job/Release/job/Release/118/

:+1:


When viewing VisualStudioHelp it would be nice to see the applicable version of the target programming language

and instead show which version of C# it is. Like Version C# 7.1.

⚠ Idea migrated from UserVoice
Created By: cristadli
Created On: 2017/12/22 16:54:45 +0000
Votes at Migration: 1
Supporters at Migration: 1

@dastaffo Is this belong to your area?

@ShevaDas FYI for future offline plans

Closing this item as it's mostly related to content, that can be addressed by the respective authors.


Test for adding, removing and modifying value

This PR is wip.

Yes this is exactly what is expected. From there you should run dune runtest and make sure the output corresponds to what we expect. If it does, you can promote the output to the file with dune promote. Indeed, the cram test files contains both the command and the expected output.
This is all described in our contributing guide and in the dune documentation.
Also before doing this you might want to update your main branch and rebase on top of it as we merged a PR updating to OCaml 4.14 and you'll want to build and run the tests with that version.

You also probably want to change your editor settings to add newlines at the end of files as you'll see your changes removed it.

While running dune runtest, the test for removing a val works fine but for modifying and adding a value the following is generated
+  api-watcher: internal error, uncaught exception:
+               Includemod.Error(_)
+
+  [125]

I tried but was not able to solve this. Also how to update Ocaml version to 4.14. I ran opam switch create ./ 4.12.1 --deps-only -t this and it created a switch with Ocaml version 4.12.1

This is an error in the existing program logic, and proves that the tests are working! :tada:
The underlying reason is that the function we are calling to compare interfaces, Includemod.signatures, raises an exception when the inclusion check fails: https://github.com/ocaml/ocaml/blob/trunk/typing/includemod.ml#L1212-L1217
I suggest that for now you just dune promote those changes and add them to the test case expectations, and we will deal with handling this more gracefully in a followup.
WDYT @NathanReb?

Yeah, totally agree! The tests are doing their job here.
Once this is merged we'll open an issue to fix the underlying bug they uncovered!

I just opened #18. @harshey1103 are you interested in fixing the bug?


WireFrame issue with CAM data

To reproduce:

Open Vapor, Import->NetCDF-CF
Select the file:
/little_glade/data/Source/CAM/AMIP_0.25degree/cam5_1_amip_run2.cam2.h1.1979-01-01-00000.nc
Reduce the region (optional, I figured this would reduce compute time.  It takes a while.)
On Ubuntu, Vapor will max out resident memory and hangs.  I'm not sure if it returns.
On OSX, Vapor will crash

I believe that a step has been left out on how to reproduce: after loading the data create a wire frame renderer.

Fixed by PR 935