node-sass not support nodejs8.x

environment
Node: 8.1.2
Npm: 5.0.3
OS: MacOS Sierra 10.12.5
description
This is a project of vue that create by vue-cli, when the version of node is below 8.0.0 everything is ok, but i upgrade the version of node from 7.10.0 to 8.1.2  and get error below
My english sucks, i hope you can get my point, thanks in advance
output
➜  cms-fe git:(dev) ✗ npm run dev

><EMAIL_ADDRESS>dev /Users/liyanfeng/work/cms-fe
> node build/dev-server.js

Listening at http://localhost:8080

webpack: wait until bundle finished: /index.html
webpack built abcd519cce388f261314 in 7997ms
Hash: abcd519cce388f261314
Version: webpack 1.14.0
Time: 7997ms
                                 Asset     Size  Chunks       Chunk Names
static/fonts/element-icons.b02bdc1.ttf  13.2 kB
          static/img/p1089.e4907ea.jpg   134 kB
                                app.js  9.01 MB       0       app

ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.1.1
 @ ./src/style/style.scss 4:14-122 13:2-17:4 14:20-128

ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.1.1
 @ ./~/vue-style-loader!./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-090654d2!./~/sass-loader!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/App.vue 4:14-248 13:2-17:4 14:20-254

ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.1.1
 @ ./~/vue-style-loader!./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-5b71776a&scoped=true!./~/sass-loader!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/views/Edit.vue 4:14-273 13:2-17:4 14:20-279

ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.1.1
 @ ./~/vue-style-loader!./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-663d35be&scoped=true!./~/sass-loader!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/views/Help.vue 4:14-273 13:2-17:4 14:20-279

ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.1.1
 @ ./~/vue-style-loader!./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-92689f2a&scoped=true!./~/sass-loader!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/views/Author.vue 4:14-275 13:2-17:4 14:20-281

ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.1.1
 @ ./~/vue-style-loader!./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-54f133ed!./~/sass-loader!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/components/RenderEditor.vue 4:14-269 13:2-17:4 14:20-275

ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.1.1
 @ ./~/vue-style-loader!./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-5c2461da!./~/sass-loader!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/components/DataGrid.vue 4:14-265 13:2-17:4 14:20-271
Child html-webpack-plugin for "index.html":
         Asset     Size  Chunks       Chunk Names
    index.html  1.47 MB       0
webpack: bundle is now VALID.

You install<EMAIL_ADDRESS>you need<EMAIL_ADDRESS>Rin
rm -rf node_modules
npm install
On 21 Jun. 2017 10:11 pm, "LYF"<EMAIL_ADDRESS>wrote:

environment
Node: 8.1.x
Npm: 5.0.3
OS: MacOS Sierra 10.12.5
description
This is a project of vue that create by vue-cli, when the version of node
is below 8.0.0 everything is ok, but i upgrade the version of node from
7.10.0 to 8.1.2 and get error below
My english sucks, i hope you can get my point, thanks in advance
output
➜  cms-fe git:(dev) ✗ npm run dev

<EMAIL_ADDRESS>dev /Users/liyanfeng/work/cms-fe> node build/dev-server.js

Listening at http://localhost:8080
webpack: wait until bundle finished: /index.html
webpack built abcd519cce388f261314 in 7997ms
Hash: abcd519cce388f261314
Version: webpack 1.14.0
Time: 7997ms
Asset     Size  Chunks       Chunk Names
static/fonts/element-icons.b02bdc1.ttf  13.2 kB
static/img/p1089.e4907ea.jpg   134 kB
app.js  9.01 MB       0       app
ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:https://github.com/sass/node-sass/releases/tag/v4.1.1
@ ./src/style/style.scss 4:14-122 13:2-17:4 14:20-128
ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:https://github.com/sass/node-sass/releases/tag/v4.1.1
@ ./~/vue-style-loader!./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-090654d2!./~/sass-loader!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/App.vue 4:14-248 13:2-17:4 14:20-254
ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:https://github.com/sass/node-sass/releases/tag/v4.1.1
@ ./~/vue-style-loader!./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-5b71776a&scoped=true!./~/sass-loader!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/views/Edit.vue 4:14-273 13:2-17:4 14:20-279
ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:https://github.com/sass/node-sass/releases/tag/v4.1.1
@ ./~/vue-style-loader!./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-663d35be&scoped=true!./~/sass-loader!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/views/Help.vue 4:14-273 13:2-17:4 14:20-279
ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:https://github.com/sass/node-sass/releases/tag/v4.1.1
@ ./~/vue-style-loader!./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-92689f2a&scoped=true!./~/sass-loader!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/views/Author.vue 4:14-275 13:2-17:4 14:20-281
ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:https://github.com/sass/node-sass/releases/tag/v4.1.1
@ ./~/vue-style-loader!./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-54f133ed!./~/sass-loader!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/components/RenderEditor.vue 4:14-269 13:2-17:4 14:20-275
ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:https://github.com/sass/node-sass/releases/tag/v4.1.1
@ ./~/vue-style-loader!./~/css-loader!./~/vue-loader/lib/style-rewriter.js?id=data-v-5c2461da!./~/sass-loader!./~/vue-loader/lib/selector.js?type=styles&index=0!./src/components/DataGrid.vue 4:14-265 13:2-17:4 14:20-271
Child html-webpack-plugin for "index.html":
Asset     Size  Chunks       Chunk Names
index.html  1.47 MB       0
webpack: bundle is now VALID.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2026, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWGwXUa941BCRFd0up-HPZRzmZFjUks5sGQh6gaJpZM4OA3ei
.

thanks @xzyfer

Nuke your node_modules folder and do a npm install again.


Update message.go

cosmetic

Oh, shoot @ivy-fish, this PR is kind of messy --
e486846 (HEAD -> master, origin/master, origin/HEAD) - [#] SendMessage type use MessageType as well
914bde7 Merge branch 'eatmoreapple:master' into master
e81d986 修改HotReloadStorage定义
e91403d Update message.go
0a96046 解决冲突

Both commit e91403d and 914bde7 were "verified", meaning they were done by GH.
OK that you merge it like this?

This branch has no conflicts with the base branch now.


⚠ Bofrost.at has degraded performance

In 01788cc, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1563 ms

Resolved: Bofrost.at performance has improved in a9c7674.


Permit to disabling loading persisted binding configuration

As part of some CI tasks I would need to be able to disable loading the bindings defined in the persisted binding configuration.
I would also find useful to be able to define Modelix specific credentials as one could have multiple different credentials. For this reason if one has credentials modelix.github.user/modelix.github.token they will prevail over gpr.user/gpr.key. For users having only gpr.user/gpr.key credentials things should work as of now.
Question: should I create different PR for the different MPS versions supported?

Yes, changes on an older branch should be merged into newer branches. A PR is not required if there are no conflicts and the build is not expected to break.

Thank you, I will merge the changes also into the newer branches and avoid PRs when not necessary


Move inventory_object_attrs to default collections

In order to use find_or_build().assign_attributes the attributes must be
defined on the inventory_collection.  These are defined in ovirt but are
common for all InfraManagers.  These should be moved up to the default
inventory_collections.
Related: https://github.com/ManageIQ/manageiq-providers-ovirt/pull/172

Ovirt refresh specs are passing locally with this change plus removing them in https://github.com/ManageIQ/manageiq-providers-ovirt/pull/172

@blomquisg can you take a look?

Ovirt master passes with this change in place so as long as this is merged first we can re-run the tests on https://github.com/ManageIQ/manageiq-providers-ovirt/pull/172 before merging that

ping @blomquisg

One thing that occurs to me is the cross-over of ActiveRecord object and InventoryObject.  I'm fine with moving forward with this type of PR, but maybe we should start thinking about a way to decorate the ActiveRecord object with some representation of what/how to save and/or parse during the inventory saving and parsing processes.  Then, we wouldn't need a separate layer or Inventory objects that seem to duplicate many of the aspects of the ActiveRecord model objects.
Again, I don't want to change this PR, but just start a future discussion around this concept.
Thoughts?
/cc @Fryguy

@blomquisg completely agree, that's what @Ladas was referencing here https://github.com/ManageIQ/manageiq/pull/16613#pullrequestreview-82096309
I don't like how we have to define these when the accessors should already be defined on the model.
Marcel's original idea here was that there were some properties that we don't want refresh to set, but I think it would be more effective to have a blacklist of attributes rather than requiring a whitelist for everything else.


Cityscapse validation with bad results.

I followed the steps to prepare the cityscapse dataset and eval the pth file with script "sh eval.sh configs/video/cityscapes/tmanet_r50-d8_769x769_80k_cityscapes_video.py".
But I got some problems.

In your original config file, https://github.com/wanghao9610/TMANet/blob/master/configs/base/datasets/cityscapes_video_769x769.py, I found the  ann_dir setting is 'gtFine_19/train'. I don't know whether gtFIne_19 is different to gtFine or not. But in order to run the validation code, I change it into gtFine. And as a result, the validation code could run.
After validation, I got a strang result as shown in the picture below:
.

Actually, I got a very good results at CamVid dataset just follow the same steps with cityscapes.
Do I need some modifications to run the validation code at cityscapes dataset?
Thanks for your reply.

I figure it out. We need to use the script https://github.com/mcordts/cityscapesScripts/blob/master/cityscapesscripts/preparation/createTrainIdLabelImgs.py to convert the label into train_label.


feature/better_ecs

Uh so the new ecs works.


bug: fix version checking up to constraint

Problem

you can't define a concrete version to install if the latest version is greater than the version you choose, because we always return the latest
you can't define a constraint that would still work if the constraint it something like <=2.0.0 but the latest version is above that like 3.0.0. It should reconcile 2.0.0 but it will actually error saying, no versions met the constraint
you can't downgrade. if you change your constraint to <=2.0.0 from >2.0.0 nothing will happen

Solution
Reconcile versions up-to the given constraint. This means that if a constraint is provided, we will return whatever the maximum is that STILL VALIDATES to that constraint. This is achieved by looping through the descending order of versions and returning the first that validates.
Downgrading or pinning to a version will be achieved by saying v0.1.1 as a constraint. Basically, if a constraint is a version that can be parsed as a correct semver, we will choose that version to install regardless of if it exists or not. ( that will be determined later when we are trying to look up the component version using that version ).

Basically, if a constraint is a version that can be parsed as a correct semver, we will choose that version to install regardless of if it exists or not. ( that will be determined later when we are trying to look up the component version using that version ).

Why would we even bother to go any further if we know the version doesn't exist?

Why would we even bother to go any further if we know the version doesn't exist?

Hm, fair point.

Also Closes https://github.com/open-component-model/ocm-controller/pull/141


ERROR:_pickle.UnpicklingError: pickle data was truncated

hello , Thank you so much for sharing your work.  But i had a problem running the code. The code that would have worked properly suddenly had the following problems when it was opened.
Traceback (most recent call last):
File "demo.py", line 228, in
tf.app.run()
File "E:\Anaconda\anaconda_install\lib\site-packages\tensorflow\python\platform\app.py", line 126, in run
_sys.exit(main(argv))
File "demo.py", line 148, in main
image=image)
File "incl\tensorvision\core.py", line 137, in build_inference_graph
logits = modules['arch'].inference(hypes, image, train=False)
File "RUNS\KittiSeg_pretrained\model_files\architecture.py", line 23, in inference
vgg_fcn = fcn8_vgg.FCN8VGG(vgg16_npy_path=vgg16_npy_path)
File "F:\KittiSeg\incl\tensorflow_fcn\fcn8_vgg.py", line 33, in init
self.data_dict = np.load(vgg16_npy_path, encoding='latin1').item()
File "E:\Anaconda\anaconda_install\lib\site-packages\numpy\lib\npyio.py", line 421, in load
pickle_kwargs=pickle_kwargs)
File "E:\Anaconda\anaconda_install\lib\site-packages\numpy\lib\format.py", line 647, in read_array
array = pickle.load(fp, **pickle_kwargs)
_pickle.UnpicklingError: pickle data was truncated

or where can modify the image_iter ?

Do you solve the problem

yes.
My vgg16.m is damaged, I download another one... :P


Adding owners for the GenAI documentation

Summary
Describe your changes here.
Fixes #Issue_Number (if available)

@elbruno - can you re-create the changes to codeowners that I have here and open a new PR? This one keeps timing out on me.


"fix 404 url"

fix a invalid url

@wyyxd2017 I don't understand this PR.
https://minibroker.blob.core.windows.net/charts is a valid chart repository, and it contains the latest release (0.3.1).
https://github.com/kubernetes-sigs/minibroker/tree/master/charts, on the other hand, is not a valid chart repository.

Agreed, the canonical location for Minibroker's charts is in Azure blob storage. When you hit the root of the container, it does return a 404. However when you use that URL with helm, the instructions on how to do that are on our readme, helm is able to build URLs to the charts and download them just fine.
I'm going to close this for now but please let us know if there is a problem that prompted opening this PR!


Fix sync mode naming: change all of the SYNC_FULL to SYNC_FAST

What was wrong?
We need to fix an internal naming issue where we refer to our fast sync using SYNC_FULL. This should be renamed to SYNC_FAST, and use the fast terminology in place of full everywhere that is currently used.
Issue Reference: https://github.com/ethereum/py-evm/issues/1480
How was it fixed?
Change the name from SYNC_FULL to SYNC_FAST
Cute Animal Picture

Not really sure why I'm seeing these on CircleCI:
Build-agent version 0.1.1073-1f69f340 (2018-11-20T18:07:03+0000)
Starting container circleci/python:3.6
  image is cached as circleci/python:3.6, but refreshing...

Error response from daemon: unauthorized: authentication required

@carver @pipermerriam

Moving this PR to https://github.com/ethereum/py-evm/pull/1513


[Feature]  Avoid using hive's own FileSystem to access the location of paimon table

Search before asking

[x] I searched in the [[issues](https://github.com/apache/incubator-paimon/issues)](https://github.com/apache/incubator-paimon/issues) and found nothing similar.

Motivation
When using a permission authentication policy based on StorageBasedAuthorizationProvider, creating an external table of  paimon will cause Hive to create its own FileSystem to access the object storage location of paimon table , and it will not read the configuration of paimon for accessing the object storage .
Solution

Extend  StorageBasedAuthorizationProvider for checking whether is paimon table through the STORED BY field of table

Support multi strategy for  permission authentication  policy of paimon if the  table is stored by paimon :

do nothing for permission authentication checking

using  paimon's filesystem for checking permission authentication , the following is what we need to do

get the configuration of paimon for accessing the object storage
support the catalog property of paimon's extern table like Iceberg , so that we can access the config of object storage .  For example  :

CREATE EXTERNAL TABLE my_table
STORED BY 'org.apache.paimon.hive.PaimonStorageHandler'
LOCATION 's3://realtime/wgcn/warehouse/default.db/word_count';
TBLPROPERTIES ('paimon.catalog'='a1');

	and then we can get the catalog info from the config of HMS like:
    <property>
        <name>paimon.catalog.a1.access.key</name>
        <value>...</value>
    </property>
    <property>
        <name>paimon.catalog.a1.secret.key</name>
        <value>...</value>
    </property>

	 or somewhere user redefine

use  the paimon's filesystem and implement the  permission authentication  Refering to the implementation of StorageBasedAuthorizationProvider

add the document for guiding users config the  implemence  of StorageBasedAuthorizationProvider at HMS

Anything else?
No response
Are you willing to submit a PR?

[x] I'm willing to submit a PR!

I'm willing to submit a PR

@wg1026688210 Thanks, assigned to u~

The relevant PR has been merged and I will close this issue.


wip: ibc: add ICS4 channels support

this PR adds ICS4 channels support.

Going to squash+merge this, so that we don't risk generating conflicts, but it would be good to split out the TODOs into issues so we don't lose track.


Stencil-only attachments and MTLPixelFormatInvalid

Hello.
I cannot use Metal API Validation feature in XCode because for the stencil-only attachment I get API validation error that looks like this:
-[MTLDebugRenderCommandEncoder setRenderPipelineState:]:1580: failed assertion Set Render Pipeline State Validation
For depth attachment, the renderPipelineState pixelFormat must be MTLPixelFormatInvalid, as no texture is set.

For stencil-only attachments I use vk::ImageLayout::eDepthReadOnlyStencilAttachmentOptimal layout with eD32SfloatS8Uint or eD24UnormS8Uint image.
It would be very nice to get rid of this "false positive" validation error to be able to use API Validation.
Did I miss something in stencil-only setup maybe to make MoltenVK set depth format to Invalid for such attachments?

I'm not the original reporter, but I am getting this error as well. In my case, I'm using dynamic rendering (vkCmdBeginRenderingKHR) and providing a color attachment but not a depth attachment.
Happy to report/collect other info if that helps.
Thanks

Still trying to reproduce it with a simple triangle from Vulkan samples with no success. Meanwhile Metal capture of the problematic pipeline where depth part of depth-stencil attachment is missing, but format is still ldefined:

versus usual complete depth-stencil attachment pipeline where both attachment parts and formats are present:

Works now! You are my hero! Thank you!
P.S.: no Metal validation errors so far :P

On the other hand: there are validation errors about mixing depth and stencil store operations. Not sure if this is our bug or another MoltenVK issue. I'll investigate.
-[MTLDebugRenderCommandEncoder endEncoding_private]:7084: failed assertion `End Encoding Validation endEncoding called with store action for depth attachment still set to MTLStoreActionUnknown MTLDebugRenderCommandEncoder: mixing MTLStoreActionUnknown and MTLStoreActionStore store actions for the depth and stencil render pass attachments is not allowed.

there are validation errors about mixing depth and stencil store operations

Odd. That didn't show up in testing here. Thanks for reporting it. I'll look into it.

PR #1885 should fix this. Please retest with latest MoltenVK, and close this issue if it is fixed.

Latest version has no more issues with separate depth and stencil attachments. Thank you!


[gradle] Add 0-5

From release history https://gradle.org/releases/

Hopefully this reduces the comments in dependabot release-data bump MRs started in #3612...

Hopefully this reduces the comments in dependabot release-data bump MRs started in #3612...

🤣

I fear this will not fix the issue, sure this would reduce the number of comments in dependabot PRs, but all the date would be wrong due to the auto-update mechanism.

@marcwrobel what do you think of my try f0a8960d3a1a67e468965da1a9aa87902ea1edb3


0.1.6 fixes

@kbubnicki can you accept this PR? It fixes two typos that would break validating against 0.1.6. Once accepted, I'll create 0.1.6 again.

Done


Fix SUSE version

The last official version is 2.38.

@ChaseCrum Could you please review this? thanks.

sign-off

Merging with approval from @chasecrum


pep8 compliance in dwave.embedding.polynomialembeddor

For the polynomailembeddor file https://github.com/dwavesystems/dwave-system/blob/38e5b5bae6527e812a316a829fc19f43bb380f7f/dwave/embedding/polynomialembedder.py#L47
See discussion in #111 , especially https://github.com/dwavesystems/dwave-system/pull/111#issuecomment-429480604

The term "full yield" is not accurate here.
An "evil" coupler, in my old terminology, is an internal coupler (a coupler between a horizontal and a vertical qubit) for which both qubits exist but the coupler does not.
"No internal defects" means that "no internal couplers are missing unless one of their qubits is missing"
It's quite a far cry from "full yield" -- and using that familiar term would cause significant confusion -- it's fine for qubits to be missing, and it's also fine for external couplers (those between qubits which are parallel) to be missing where both endpoints are present.

also, do you mean to be propagating the "embeddor" typo?

No, I just seem to really like that spelling


Allow titles with math notation

What's your feature?
Since we are dealing with math, I believe it's really required to be able to have math equations in the title.
For example:
title: $\lim_{x\to a}$
Any related problems?
No response
Additional context?
No response

Agree. We could use renderMath to render the equation into the title element. Maybe just skip this step if no mathjax is detected. Great idea btw.

So, this:
https://github.com/leonhma/obsidian-functionplot/blob/2a69384215690967a02c7b39ef644b11a3aadd5a/src/common/utils.ts#L19
should change to something like
title: ${options.title is math ? renderMath(options.title) : options.title}

Yes. Either that or we could support the $ ... $ syntax obsidian uses. I don't exactly know how renderMath works but we should have a function that renders text to html element and also handles math. Then we could use it as a component for the title and legends.


More translation fixes (Part 2)

I also have some additional information/Questions:
o1s: trigger id for Roar and Charybdis seams to be incorrect (Roar is 1ED8 and should be 1ED4, Charybdis is 1ED4 and should be 1ED3) except i am missing something
e7s: translation for 4C5A might confuse people Dark's Course which translate to Light's Course in all non english languages (is there another id that can be used? as there are also correctly translated names)
qitana: IDs 3C8C/3D6D are both named Ronkan Light but are translated to different things in German ('Licht Ronkas/Ronkalicht') is there anything that can be done about this?

o1s: trigger id for Roar and Charybdis seams to be incorrect (Roar is 1ED8 and should be 1ED4, Charybdis is 1ED4 and should be 1ED3) except i am missing something

You're correct.  I went back and checked, and then re-did the o1s timeline because it was from ancient times when I made timelines by hand staring at videos<EMAIL_ADDRESS>

Also, would you mind tagging in some folks who have been translating other languages to give this a review as well?
(Also also why do your scripts sometimes say bnpcname in the commit when adjusting skills?)

Also, would you mind tagging in some folks who have been translating other languages to give this a review as well?
(Also also why do your scripts sometimes say bnpcname in the commit when adjusting skills?)

<.< most likly just a copy paste issue :x
i will see if i can find the names (if you have them in mind, could you maybe help me out with the names)?

Maybe @Bluefissure for Chinese, @Una-p for Korean, and @MaikoTan for Japanese, if y'all have time to take a quick look at these?

e7s: translation for 4C5A might confuse people Dark's Course which translate to Light's Course in all non english languages (is there another id that can be used? as there are also correctly translated names)

I don't know.  You'd have to look at the logs.  I personally don't think it would be that confusing if they all said Light's Course.

qitana: IDs 3C8C/3D6D are both named Ronkan Light but are translated to different things in German ('Licht Ronkas/Ronkalicht') is there anything that can be done about this?

I don't think this has come up before.  I'm not totally sure what to do.  I think we could:
(1) ignore it with a comment (as those both seem similar enough?)
(2) change the timeline to say "Ronkan Light 3C8C" and "Ronkan Light 3D6D" and add an English timelineReplace section??

ok so for e7s we can ignore it, and for qitana i would say we can go with option 1
for o1n, should i do it in this commit or in another one?

ok so for e7s we can ignore it, and for qitana i would say we can go with option 1

:+1:
Yeah, I think option 2 is something to keep in mind if this happens again in the future where we really want to differentiate.  Hopefully it doesn't happen, as I think it'd be really confusing to have an ability that's ambiguous in English but differentiated in other languages.

for o1n, should i do it in this commit or in another one?

I would say change triggers in a separate commit, if you don't mind.

Thanks for mention me. If you need quick kor translation, please mention me next time.
And sorry but I've no idea cause our 5.2 update will be at Sep. 1. XD

Yeah, I got confused when translating e7s Dark's Course because that's 白光奔流 in Chinese and 白光の奔流 in Japnese, which should be Light's Course in English. I'm not sure what SE's English Localization team was doing.

Btw the Heavenly Strike are two different actions in both byakko and e8s, but they share the same English name, I got it wrong at first since I did a join searching of English action names.

So in my opinion, it's better to do ID-based indexing when translating the timelines instead of searching the corresponding English names, which may be confusing and may have multiple candidates. And I think most of the wrong translation entries were results form this.
Thanks for the corrections!

So in my opinion, it's better to do ID-based indexing when translating the timelines instead of searching the corresponding English names, which may be confusing and may have multiple candidates. And I think most of the wrong translation entries were results form this.
Thanks for the corrections!

My current script is doing following:

i checks if the to translated name is part of some files i specified (bnpcname, placename etc as they cannot used by id in this case) and use it if i only find 1 element
If it finds at least 2 matching elements, it will show a notification and uses the firsts ID from the corresponding txt file (this was also the case for the confusing orbone issue MaikoTan and i had)
the rest has to be done currently by hand with SC, Godbert and some of my python scripts (thats how i found the issues in o1s)

Thanks for weighing in.  I just wanted some extra review to make sure these looked good.  I'll go ahead and merge this now.


How to install xdvi with the new texlive infrastructure?

I tried
self.texlive.combine { inherit (self.texlive) scheme-medium xdvi; };

etc., but I did not manage to get my hands on an xdvi executable. Can I install that tool somehow with the new texlive infrastructure?
Cc: @vcunat

No, I haven't packaged binaries for that one yet. For reference, it would be in https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/typesetting/tex/texlive-new/bin.nix.

Christmas time! It works for my files. Hopefully it will for yours – otherwise I can try to fix...

Works like a charm. Thank you so much!


No prompt information pops up when typing an existing container app environment name

OS: All
Build Version: 20220405.6
Regression: Not a Regression
Repro Steps:

Create a container app environment with a location.
Create a container app environment with the same name and different location again.
Check whether pops up a prompt information.

Expect:
Pop up a prompt information.
Actual:
No prompt information pops up.

More Info:
Fail to create a container app environment with the an existing name and different location.
Details of output:
1:44:50 PM: Using existing resource group "test".
1:44:51 PM: Creating new Log Analytic workspace...
1:44:53 PM: Creating new Container App environment "test"...
1:44:56 PM: Error: The resource 'test' already exists in location 'westeurope' in resource group 'test'. A resource with the same name cannot be created in location 'eastus'. Please select a new resource name.

The error happens pretty quickly, so it's not too bad. The worst part is that we create a new resource group & log analytic workspace that is now just stranded :(


Update werewolf-es.json

Partial werewolf translation. I held off translating some terms until the official translation comes out in a few weeks to have the translation use the correct terminology

Thanks for all the translation updates! I've went ahead and merged all the other pull requests. Since you mentioned the official translation for Werewolf comes out soon, would you like me to hold off on merging this issue until the official translation comes out, or merge as-is and you can send in another pull request later?

I’d say better merge as-is and I will make another PR when it comes out to
have it at least partially translated for the time being
On Thu, 29 Feb 2024 at 23:58, Veilza @.***> wrote:

Thanks for all the translation updates! I've went ahead and merged all the
other pull requests. Since you mentioned the official translation for
Werewolf comes out soon, would you like me to hold off on merging this
issue until the official translation comes out, or merge as-is and you can
send in another pull request later?
—
Reply to this email directly, view it on GitHub
https://github.com/Rayji96/foundry-V5/pull/276#issuecomment-1972114099,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKAKF3553STB5YLSFQ22OLYV6Y75AVCNFSM6AAAAABEASEDNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSGEYTIMBZHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Got it! Will do then.


libopenblas should be a dependency

r-matrix is missing the dependency for libopenblas.  If you install it on a system without libopenblas (either in conda or system) it cannot load:
> library(Matrix)
Error: package or namespace load failed for ‘Matrix’ in dyn.load(file, DLLpath = DLLpath, ...):
 unable to load shared object '/home/hermidalc/soft/miniconda3/envs/r-matrix-test/lib/R/library/Matrix/libs/Matrix.so':
  libopenblas.so.0: cannot open shared object file: No such file or directory

If you do an ldd of Matrix.so you will see it cannot find libopenblas.so.0.  This is fixed by installing conda-forge libopenblas so should be made as an r-matrix dependency.

I second this. I'm trying to combine scipy (blas_openblas), numpy (blas_openblas) and r-matrix. environment creation works fine but r-matrix fails upon use, due to incorrect libopenblas version.

I just tested this (conda create -n rtest r-matrix scipy numpy) and it works fine, with the correct libopenblas.so version installed. Are you trying to install specific versions?

I just tested this (conda create -n rtest r-matrix scipy numpy) and it works fine, with the correct libopenblas.so version installed. Are you trying to install specific versions?

r-matrix shouldn’t depend on you installing scipy or numpy its a pure R package.

I just tested this (conda create -n rtest r-matrix scipy numpy) and it works fine, with the correct libopenblas.so version installed. Are you trying to install specific versions?

Either way the last post is not really pertinent to this issue. r-matrix by itself does not work without libopenblas dependency

$ cat test.yml
name: test
channels:
  - conda-forge
  - bioconda
  - defaults
dependencies:
  - r-base>=3.6
  - r-matrix
  - numpy=*=*openblas*
  - scipy=*=*openblas*

$ conda env create -f=test.yml
Collecting package metadata (repodata.json): done
Solving environment: done
Preparing transaction: done
Verifying transaction: done
Executing transaction: done

$ conda activate test
(test) $ R

R version 3.6.1 (2019-07-05) -- "Action of the Toes"
Copyright (C) 2019 The R Foundation for Statistical Computing
Platform: x86_64-apple-darwin13.4.0 (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

  Natural language support but running in an English locale

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> library(Matrix)
Error: package or namespace load failed for ‘Matrix’ in dyn.load(file, DLLpath = DLLpath, ...):
 unable to load shared object '$HOME/miniconda3/envs/test/lib/R/library/Matrix/libs/Matrix.dylib':
  dlopen($HOME/miniconda3/envs/test/lib/R/library/Matrix/libs/Matrix.dylib, 6): Library not loaded: @rpath/libopenblasp-r0.3.7.dylib
  Referenced from: $HOME/miniconda3/envs/test/lib/R/library/Matrix/libs/Matrix.dylib
  Reason: image not found
In addition: Warning message:
package ‘Matrix’ was built under R version 3.6.2
>

(test) $ conda list
# packages in environment at $HOME/miniconda3/envs/test:
#
# Name                    Version                   Build  Channel
_r-mutex                  1.0.1               anacondar_1    conda-forge
blas                      1.1                    openblas    conda-forge
bwidget                   1.9.14                        0    conda-forge
bzip2                     1.0.8                h0b31af3_2    conda-forge
ca-certificates           2019.11.28           hecc5488_0    conda-forge
cairo                     1.16.0            he1c11cd_1002    conda-forge
cctools                   895                  h7512d6f_0    conda-forge
certifi                   2019.11.28               py37_0    conda-forge
clang                     4.0.1                h662ec87_0    conda-forge
clang_osx-64              4.0.1               h1ce6c1d_17    conda-forge
clangxx                   4.0.1                hc9b4283_0    conda-forge
clangxx_osx-64            4.0.1               h22b1bf0_17    conda-forge
compiler-rt               4.0.1                h5487866_0    conda-forge
curl                      7.65.3               h22ea746_0    conda-forge
fontconfig                2.13.1            h6b1039f_1001    conda-forge
freetype                  2.10.0               h24853df_1    conda-forge
fribidi                   1.0.5             h01d97ff_1002    conda-forge
gettext                   <IP_ADDRESS>          h46ab8bc_1002    conda-forge
gfortran_osx-64           4.8.5                h22b1bf0_8    conda-forge
glib                      2.58.3            h9d45998_1002    conda-forge
graphite2                 1.3.13            h2098e52_1000    conda-forge
gsl                       2.5                  ha2d443c_1    conda-forge
harfbuzz                  2.4.0                hd8d2a14_3    conda-forge
icu                       64.2                 h6de7cb9_1    conda-forge
jpeg                      9c                h1de35cc_1001    conda-forge
krb5                      1.16.3            hcfa6398_1001    conda-forge
ld64                      274.2                h7c2db76_0    conda-forge
libblas                   3.8.0               11_openblas    conda-forge
libcblas                  3.8.0               11_openblas    conda-forge
libcurl                   7.65.3               h16faf7d_0    conda-forge
libcxx                    4.0.1                h579ed51_0
libcxxabi                 4.0.1                hebd6815_0    conda-forge
libedit                   3.1.20170329      hcfe32e1_1001    conda-forge
libffi                    3.2.1             h6de7cb9_1006    conda-forge
libgfortran               3.0.1                         0    conda-forge
libiconv                  1.15              h01d97ff_1005    conda-forge
liblapack                 3.8.0               11_openblas    conda-forge
libopenblas               0.3.6                hdc02c5d_2
libpng                    1.6.37               h2573ce8_0    conda-forge
libssh2                   1.8.2                hcdc9a53_2    conda-forge
libtiff                   4.0.10            hd08fb8f_1003    conda-forge
libxml2                   2.9.10               h53d96d6_0    conda-forge
llvm                      4.0.1                hc748206_0    conda-forge
llvm-lto-tapi             4.0.1                h6701bc3_0    conda-forge
llvm-openmp               9.0.1                h28b9765_2    conda-forge
lz4-c                     1.8.3             h6de7cb9_1001    conda-forge
make                      4.2.1             h1de35cc_2004    conda-forge
ncurses                   6.1               h0a44026_1002    conda-forge
numpy                     1.16.2          py37_blas_openblash486cb9f_0  [blas_openblas]  conda-forge
openblas                  0.3.3             hdc02c5d_1001    conda-forge
openssl                   1.1.1d               h0b31af3_0    conda-forge
pango                     1.42.4               h6691c8e_1    conda-forge
pcre                      8.41              h0a44026_1003    conda-forge
pip                       20.0.2                     py_2    conda-forge
pixman                    0.38.0            h01d97ff_1003    conda-forge
python                    3.7.3                h93065d6_1    conda-forge
r-base                    3.6.1                h7df2c9e_4    conda-forge
r-lattice                 0.20_38         r36h159158b_1002    conda-forge
r-matrix                  1.2_18            r36h17f1fa6_0    conda-forge
readline                  8.0                  hcfe32e1_0    conda-forge
scipy                     1.2.1           py37_blas_openblash486cb9f_0  [blas_openblas]  conda-forge
setuptools                45.1.0                   py37_0    conda-forge
sqlite                    3.30.1               h93121df_0    conda-forge
tk                        8.6.10               hbbe82c9_0    conda-forge
tktable                   2.10                 h008db23_3    conda-forge
wheel                     0.34.2                     py_1    conda-forge
xz                        5.2.4             h1de35cc_1001    conda-forge
zlib                      1.2.11            h0b31af3_1006    conda-forge
zstd                      1.4.0                ha9f0a20_0    conda-forge

(test) $ conda info
     active environment : test
    active env location : $HOME/miniconda3/envs/test
            shell level : 1
       user config file : $HOME/.condarc
 populated config files : $HOME/.condarc
          conda version : 4.8.2
    conda-build version : not installed
         python version : 3.7.6.final.0
       virtual packages : __osx=10.15.3
       base environment : $HOME/miniconda3  (writable)
           channel URLs : https://conda.anaconda.org/conda-forge/osx-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://conda.anaconda.org/bioconda/osx-64
                          https://conda.anaconda.org/bioconda/noarch
                          https://repo.anaconda.com/pkgs/main/osx-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/osx-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : $HOME/miniconda3/pkgs
                          $HOME/.conda/pkgs
       envs directories : $HOME/miniconda3/envs
                          $HOME/.conda/envs
               platform : osx-64
             user-agent : conda/4.8.2 requests/2.22.0 CPython/3.7.6 Darwin/19.3.0 OSX/10.15.3
                UID:GID : 501:20
             netrc file : None
           offline mode : False

It's odd that you're getting libopenblas from the defaults channel, since when I just ran conda create -n rmatrix r-matrix it installed conda-forge/linux-64::libopenblas-0.3.7-h5ec1e0e_6 instead. The conda-forge package links correctly with Matrix.so. What happens if you create a new environment with only r-matrix in it?

That works, by coincidence I'd say, as libopenblas isn't listed as a dependency. Had 0.3.7 been listed as a dependency, conda wouldn't have deemed 0.3.6 from default usable.
(test) $ conda list | grep -e r-base -e blas -e r-matrix
libblas                   3.8.0               14_openblas    conda-forge
libcblas                  3.8.0               14_openblas    conda-forge
liblapack                 3.8.0               14_openblas    conda-forge
libopenblas               0.3.7                h3d69b6c_7    conda-forge
r-base                    3.6.2                he15a7b5_0    conda-forge
r-matrix                  1.2_18            r36h17f1fa6_0    conda-forge

(test) $ otool -L $HOME/miniconda3/envs/test/lib/R/library/Matrix/libs/Matrix.dylib
$HOME/miniconda3/envs/test/lib/R/library/Matrix/libs/Matrix.dylib:
        @rpath/R/library/Matrix/libs/Matrix.dylib (compatibility version 0.0.0, current version 0.0.0)
        @rpath/libopenblasp-r0.3.7.dylib (compatibility version 0.0.0, current version 0.0.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1)
        @rpath/R/lib/libR.dylib (compatibility version 3.6.0, current version 3.6.2)

Ah, I see the issue. It's linking against whatever blas r-base happens to pull in, but since that changes over time the linking will fail. I'll make a PR now to add libopenblas as an explicit dependency.

awesome. thanks!

@dpryan79  although, I think the dependency should be 'libopenblas'.
$ conda list -n test | grep blas
libblas                   3.8.0               14_openblas    conda-forge
libcblas                  3.8.0               14_openblas    conda-forge
liblapack                 3.8.0               14_openblas    conda-forge
libopenblas               0.3.7                h3d69b6c_7    conda-forge

libopenblas isn't in conda-forge-pinning, but is instead pulled in the the openblas meta package, which is in conda-forge-pinning. I'll have someone else double check that though.

I thought I read somewhere on conda related Github (which I cannot find now) that libopenblas is now preferred to openblas for this type of dependency. Apologies I searched again now but cannot find it, though found https://github.com/conda-forge/blas-feedstock/issues/31

This should be fixed in the next build.