Allow specifying git-host-to-provider-type mapping for on-prem gitlab support

Adds support for:

gitops install for on-prem gitlab
oauth for one on-prem host or gitlab.com at a time (globally set via GITLAB_HOST)

On oauth with multiple gitlab hosts (requires more work):

We must configure a gitlab-app for each gitlab host
UI tokens saved in localStorage should be keyed by host, not provider.

On github:

gitops install for on-prem github might work (untested)
oauth support for on-prem github probably doesn't work?.. (untested)

Closes: #1203

What changed?

New flag / env var git-host-types / GITOPS_GIT_HOST_TYPES to specify a mapping

--git-host-types="gl.acme.org=gitlab,gh.acme.org=github"

Why?
Support gitops install on-prem non-gitlab.com hosts

How did you test it?

Manually against on-prem gitlab

Release notes
Not yet..

Documentation Changes
Not yet..

We have a setup with an onprem GitLab server running SSH on a non-standard port (2222 as opposed to 22) and I believe it is currently not possible to get this to work with the code in this PR.
I try the installation with something like:
gitops install --config-repo=git@gitlab.acme.org:2222/deployments/gitops-weaveworks.git --namespace gitops --git-host-types="gitlab.acme.org:2222=gitlab"

And it fails with:
Error: error creating git clients: error normalizing url: could not get provider name from URL git@gitlab.acme.org:2222/deployments/gitops-weaveworks.git: no git providers found for "git@gitlab.acme.org:2222/deployments/gitops-weaveworks.git"

Would be nice if there was a way to specify how SSH authentication should take place, as I'm not sure how to specify an SSH key or a PAT for this URL at all.

Hi @efenex ! Thanks for testing this out.
Hmmm, just checking you've tried --git-host-types="gitlab.acme.org=gitlab" without the port?
Custom ports is indeed something we overlooked in this PR 🤦 .

This code is a bit suspect https://github.com/weaveworks/weave-gitops/blob/main/pkg/gitproviders/repo_url.go#L131 and should probably be replaced with something more robust like https://pkg.go.dev/github.com/whilp/git-urls
To workaround, things to try:
Use the full ssh:// form:
gitops install --config-repo=ssh://git@gitlab.acme.org:2222/deployments/gitops-weaveworks.git --namespace gitops --git-host-types="gitlab.acme.org:2222=gitlab"


What's the minimum GPU requirement to Fine Tune LLaVA

Question
What's the minimum GPU device needed to do Fine Tuning of LLaVA?

I could finetune the 7B model on a single A100 GPU 40GB (Google Colab)
A100 or H100 are required for CUDA.
I could bypass the CUDA requirement but V100 or T4 GPUs didn't have enough memory

I could finetune the 7B model on a single A100 GPU 40GB (Google Colab) A100 or H100 are required for CUDA. I could bypass the CUDA requirement but V100 or T4 GPUs didn't have enough memory

Do you mean the minimum memory for a single GPU is 40G?

I could finetune the 7B model on a single A100 GPU 40GB (Google Colab) A100 or H100 are required for CUDA. I could bypass the CUDA requirement but V100 or T4 GPUs didn't have enough memory

hello,Is the A100 (40GB) GPU used for full parameter fine-tuning?

I could finetune the 7B model on a single A100 GPU 40GB (Google Colab) A100 or H100 are required for CUDA. I could bypass the CUDA requirement but V100 or T4 GPUs didn't have enough memory

Can you please provide more details?
I'd like to know whether it is possible to train or fine-tune LLaVA in single GPU (A100 or H100)


add metric for per-cpu, per-stage timing

Tested on a COS VM:
$ curl -s localhost:20257/metrics  | grep -i ^system_cpu_stat
system_cpu_stat{cpu="cpu0",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="guest"} 0
system_cpu_stat{cpu="cpu0",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="guestNice"} 0
system_cpu_stat{cpu="cpu0",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="iRQ"} 0
system_cpu_stat{cpu="cpu0",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="idle"} 226616.13
system_cpu_stat{cpu="cpu0",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="iowait"} 23.92
system_cpu_stat{cpu="cpu0",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="nice"} 63.08
system_cpu_stat{cpu="cpu0",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="softIRQ"} 100.91
system_cpu_stat{cpu="cpu0",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="steal"} 67.03999999999999
system_cpu_stat{cpu="cpu0",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="system"} 2134.91
system_cpu_stat{cpu="cpu0",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="user"} 5909.54
system_cpu_stat{cpu="cpu1",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="guest"} 0
system_cpu_stat{cpu="cpu1",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="guestNice"} 0
system_cpu_stat{cpu="cpu1",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="iRQ"} 0
system_cpu_stat{cpu="cpu1",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="idle"}<PHONE_NUMBER>0000002
system_cpu_stat{cpu="cpu1",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="iowait"} 339.48
system_cpu_stat{cpu="cpu1",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="nice"} 63.510000000000005
system_cpu_stat{cpu="cpu1",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="softIRQ"} 102.99
system_cpu_stat{cpu="cpu1",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="steal"} 67.47
system_cpu_stat{cpu="cpu1",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="system"} 2167.6800000000003
system_cpu_stat{cpu="cpu1",kernel_version="5.4.49+",os_version="cos 85-13310.1041.24",stage="user"} 5827.360000000001

/assign @vteratipally
/assign @Random-Liu

/assign @vteratipally
/assign @Random-Liu

/lgtm

/lgtm

/assign @Random-Liu

/assign @Random-Liu

In theory removing labels may cause potential backward compatibility issues?

In theory removing labels may cause potential backward compatibility issues?

In theory yes, however these schemas were not used.

In theory yes, however these schemas were not used.

However, we don't know whether they are used by some OSS users. In theory, it is possible that someone is using it.
We don't have deprecation policy defined for the metrics today.
Let's at least leave it one release. We can announce deprecation for those labels first in the next release, and remove them in the future.
We should file an issue to track that, so that we don't forget about it when we cut the next release.

I suggest the following:

Send a notification to sig-node (and mention this in the sig-node meeting tomorrow)
If someone is using NPD, we can follow your plan. Otherwise, I'd like to not block this PR any longer for theoretical reasons.

How does that sound?

Otherwise, I'd like to not block this PR any longer for theoretical reasons.

I think you can at least separate the label removal from the new metric change. We don't need to block the new metrics because of the label removal.

Done

/lgtm
/approve


CLI Copy Button Problem

Copy button for the CLI copies the "$"
In the Step 1 of the Carbon Tutorial the copy button for CLI git commands copies the "$" so that when it is pasted into the CLI terminal the command does not work. I did not notice this until it was time to "git remote add upstream https://github.com/carbon-design-system/carbon-tutorial.git" as all the previous entries I had typed in manually.

Noticed this same problem on the website with the getting started install section. The copy icon copies the $ in $ npm install --save carbon-components-react carbon-components carbon-icons


MGMT-636 Add container running support in the agent

     Add YAML file to describe available commands

In general i'm not sure how i feel about this change.
if we add a new command and the code needs to change as well so what is the added value here?
we can just store the commands in a go struct and do the same no?

In general i'm not sure how i feel about this change.
if we add a new command and the code needs to change as well so what is the added value here?
we can just store the commands in a go struct and do the same no?
@ori-amizur @ronniel1 what do you think?

In general i'm not sure how i feel about this change.
if we add a new command and the code needs to change as well so what is the added value here?
we can just store the commands in a go struct and do the same no?
@ori-amizur @ronniel1 what do you think?

maybe we can combine it with the state machine. and each command will have the states states that this command should be executed on?
but we still will need to change the code for new parameters.

In general i'm not sure how i feel about this change.
if we add a new command and the code needs to change as well so what is the added value here?
we can just store the commands in a go struct and do the same no?
@ori-amizur @ronniel1 what do you think?

maybe we can combine it with the state machine. and each command will have the states that this command should be executed on?
but we still will need to change the code for new parameters.

Assuming that we need some kind of definition of what can be executed, then I think that YAML file is better, since there is separation between the logic (which is the GO code), and the definition of what needs to be executed.
Adding new commands should be easier, although it is also hard-coded since it is bundled with the image.
I am not so aware what you plan for the state machine, but it does not seem to me a good idea that execution should be bundled with state machine.  A state machine should be separate from its operations, whether they are queries or just unconditional action.

In general i'm not sure how i feel about this change.
if we add a new command and the code needs to change as well so what is the added value here?
we can just store the commands in a go struct and do the same no?
@ori-amizur @ronniel1 what do you think?

maybe we can combine it with the state machine. and each command will have the states that this command should be executed on?
but we still will need to change the code for new parameters.

Assuming that we need some kind of definition of what can be executed, then I think that YAML file is better, since there is separation between the logic (which is the GO code), and the definition of what needs to be executed.
Adding new commands should be easier, although it is also hard-coded since it is bundled with the image.
I am not so aware what you plan for the state machine, but it does not seem to me a good idea that execution should be bundled with state machine. A state machine should be separate from its operations, whether they are queries or just unconditional action.

The state machine that i'm taking about is to map between the operation and the state of the node.
for example hw info need to executed when the host in discovering state.
This way we need less logic in the code. the yaml will define the behavior


Fix access to undefined storeFieldNames.entries

Fixes #2

Hey @maury91, I'd like to get to the bottom of how the storeFieldName being read is not in the type map, I can take a look if you have repro steps

Thanks @maury91 ! Addressed in another PR, closing this one out!

Thanks @maury91 ! Addressed in another PR, closing this one out!


[Question] exchangis execute write from hive to MySQL without obvious error, but fail

Before asking

[X] I have read the How to ask for help (我已阅读如何寻求帮助指引文档).

Your environment

Linkis version used: 1.1.1
Environment name and version:

hdp-3.1.4
hive-3.1.0
spark-2.3.0
scala-2.11.8
jdk 1.8.0_121
sqoop1.4.7
Exchangis1.0.0
-sqoop.version change from 1.4.6 to 1.4.7 before compilation
-hadoop.version change from 2.7.2 to 3.1.1 before compilation
-change class TransformExchangisJob.java [170 line]，Solve the problem of null. Isempty() error
--from：if(!partitionValue.get("ds").isEmpty())
--to：if(StringUtils.isNotBlank(partitionValue.get("ds")))
but bml version is 1.4.6. (..linkis/lib/linkis-engineconn-plugins/sqoop/dist/v1.4.6)

Describe your questions

Q1.  exchangis execute failed. The DSS platform reported unknown error information during execution, while the... / links / logs log reported no error

Eureka service list

Some logs info or acctch file

dss web:
2022-09-06 16:40:58.040 INFO Program is substituting variables for you
2022-09-06 16:40:58.040 INFO Variables substitution ended successfully
2022-09-06 16:40:58.040 WARN The code you submit will not be limited by the limit
Job with jobId : nodeexecution_hadoop_appconn_7 and execID : nodeexecution_hadoop_appconn_7 submitted
2022-09-06 16:40:58.040 INFO You have submitted a new job, script code (after variable substitution) is
************************************SCRIPT CODE************************************
{"id":5793.0,"refProjectId":1.49787087103597389E18}
************************************SCRIPT CODE************************************
2022-09-06 16:40:58.040 INFO Your job is accepted,  jobID is nodeexecution_hadoop_appconn_7 and jobReqId is 155 in ServiceInstance(linkis-cg-entrance, c0:9604). Please wait it to be scheduled
job is scheduled.
2022-09-06 16:40:58.040 INFO Your job is Scheduled. Please wait it to run.
Your job is being scheduled by orchestrator.
2022-09-06 16:40:58.040 INFO job is running.
2022-09-06 16:40:58.040 INFO Your job is Running now. Please wait it to complete.
2022-09-06 16:40:58.040 INFO Job with jobGroupId : 155 and subJobId : 155 was submitted to Orchestrator.
2022-09-06 16:40:58.040 INFO Background is starting a new engine for you,execId astJob_7_codeExec_7 mark id is mark_7, it may take several seconds, please wait
2022-09-06 16:40:58.040 INFO EngineConn local log path: ServiceInstance(linkis-cg-engineconn, c0:32827) /appcom/tmp/hadoop/20220906/appconn/a7ee6eab-a544-40c8-965b-c26ed59feb73/logs
try to execute exchangis.sqoop node, ready to request to http://<IP_ADDRESS>:18089/api/rest_j/v1/dss/exchangis/main/appJob/execute/5793
submitted to Exchangis with execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Inited
task8  received asyncReturnExecuteResponse
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Inited
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Scheduled
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Running
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Running
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Running
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Running
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Failed
ExchangisJob(execId: 8ec0f89a-24dc-462e-a493-5ba02e8b718d) is in state Failed
2022-09-06 16:41:18.041 ERROR Job with execId-nodeexecution_hadoop_appconn_7 + subJobId : 155  execute failed,21304, Task(codeExec_7) status not succeed,is Failed

2022-09-06 16:41:18.041 INFO job is completed.
2022-09-06 16:41:18.041 INFO Task creation time(任务创建时间): 2022-09-06 16:40:58, Task scheduling time(任务调度时间): 2022-09-06 16:40:58, Task start time(任务开始时间): 2022-09-06 16:40:58, Mission end time(任务结束时间): 2022-09-06 16:41:18
2022-09-06 16:41:18.041 INFO Your mission(您的任务) 155 The total time spent is(总耗时时间为): 20.1 秒
2022-09-06 16:41:18.041 INFO Sorry. Your job completed with a status Failed. You can view logs for the reason.

log file:

stderr.log, stdout.log is from path: /appcom/tmp/hadoop/202209xx/appconn/xx/logs
stderr.log
stdout.log
exchangis-server.log
linkis-cg-entrance.log

This question has not been answered for a long time, I will close it first, if necessary, you can turn it back on.


Record Start/Stop of video with JSON Payload

Having separate endpoints for each action seems a little sad, so we can now parse numbers as bools and use this to flip the Action.Record action.
NSJSONSerialization represents Bools as NSNumber so all numbers can be interpreted as bools :/

@facebook-github-bot shipit


dot_product_attention has inconsistent dot types in backward pass

Description
jax.nn.dot_product_attention does the first dot product with preferred_element_type=jnp.float32 (see here). For BF16 inputs, this prevents an unnecessary downcast to BF16 (can improve numerical stability, and has no extra memory usage for FlashAttention) + matches cuDNN numerics. However, in the backward pass, XLA now sees a matmul with FP32 inputs. This leads to a number of inconsistencies:

On A100/H100: this matmul will be done with TF32 (unless this is globally banned with a flag or jax.default_matmul_precision.html, which would cause further confusion as these have no impact on the cuDNN implementation). This has half the flops a user might expect, so is fundamentally less performant than expected.
cuDNN does the backward matmuls in BF16, which is inconsistent and lower-precision than XLA. Its possible users see different losses due to this difference in precision.
TPU will also do matmuls in BF16, consistent with cuDNN.

jax.nn.dot_product_attention with BF16/FP16 inputs should have device and implementation independent numerics. It should choose the TPU + cuDNN convention. This should be implemented via the new algorithm and transpose_algorithm args (https://jax.readthedocs.io/en/latest/_autosummary/jax.lax.dot.html#jax.lax.dot) once they are available in jnp.einsum.
To explicitly see the FP32 matmuls in the backward pass:
import jax
import jax.numpy as jnp

def loss(x):
  return jnp.sum(jax.nn.dot_product_attention(x, x, x, implementation='xla'))

x = jax.random.normal(jax.random.PRNGKey(0), (8, 128, 8, 64), dtype=jnp.bfloat16)
f_grad = jax.jit(jax.grad(loss))

print(f_grad.lower(x).compile().as_text())

@dfm, @kaixih, @phaw
System info (python version, jaxlib version, accelerator, etc.)
Not applicable.

Thanks for bringing this up. It is good to learn these new options of algorithm and transpose_algorithm. As for the jnp.einsum support, can we simply use its _dot_general arg and pass a wrapped lax.dot_general with algorithm and transpose_algorithm set? like
dot_general = partial(lax.dot_general, algorithm="BF16_BF16_F32", transpose_algorithm=("BF16_BF16_BF16", "BF16_BF16_BF16"))
logits = jnp.einsum('BTNH,BSNH->BNTS', query, key, _dot_general=dot_general)

Emm, it seems the algorithm and transpose_algorithm are no longer there in the lax_dot. @sbodenstein Do you know if they are reverted?

It seems that DotAlgorithm is now an option for precision, so I’ll try that instead.
By the way, when I experimented with DotAlgorithm last week, I encountered errors like this:
jaxlib.xla_extension.XlaRuntimeError: INVALID_ARGUMENT: Failed to serialize StableHLO;                                                                                Detailed error from MLIR: /home/tmp/jax_sdpa_bwd_precision/dot_demo.py:10:0: error: failed to legalize operation 'vhlo.dot_general_v2' that was explicitly marked illegal

I suspect this might be due to the feature only working when the PJRT C API is not used, but our container has it enabled by default. I have limited knowledge of the PJRT C API, so I’m wondering:

Is there a way to turn PJRT C API off temporarily and how?
Will this feature be extended to support PJRT C API in the future?

We changed the design, which just landed (https://github.com/jax-ml/jax/pull/24079). This should now work with einsum! I'm not sure about the issues you are seeing.

Thx for the pointer. I will take a look.
Basically, I saw all the tests are protected by this check. So, I want to know more about that. I can also ask in the gchat.

@kaixih — Sorry I didn't see this conversation yesterday!
Yeah, unfortunately this feature (the new DotAlgorithm) doesn't currently work with the PJRT plugin 😢. The issue is that, for compatibility reasons, the plugin serializes the HLO to an old dialect that doesn't support the algorithm argument to the dot_general operation. I think that @matthiaskramm is working on adding support for targeting more recent HLO dialects via the plugin, but I'm not sure what the status is.
Also looping in @skye and @GleasonK who have been thinking about all this. No action needed; just an example of one potentially high impact use of the versioning work!


test coverage

Write tests to cover the existing code.

I actually like rspec, but any is fine.

Assigning myself to the task, as this tool really needs some testing...


installation issues with apollo-codegen

<EMAIL_ADDRESS>prepublish /Users/moniquehaas/apollo-codegen
rm -rf lib && npm run compile

<EMAIL_ADDRESS>compile /Users/moniquehaas/apollo-codegen
babel src --out-dir lib --source-maps

ReferenceError: Unknown plugin "transform-runtime" specified in "/Users/moniquehaas/apollo-codegen/.babelrc" at 0, attempted to resolve relative to "/Users/moniquehaas/apollo-codegen"
at /usr/local/lib/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:193:17
at Array.map (native)
at Function.normalisePlugins (/usr/local/lib/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:173:20)
at OptionManager.mergeOptions (/usr/local/lib/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:271:36)
at OptionManager.addConfig (/usr/local/lib/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:221:10)
at OptionManager.findConfigs (/usr/local/lib/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:364:16)
at OptionManager.init (/usr/local/lib/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:412:12)
at File.initOptions (/usr/local/lib/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/index.js:191:75)
at new File (/usr/local/lib/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/index.js:122:22)
at Pipeline.transform (/usr/local/lib/node_modules/babel-cli/node_modules/babel-core/lib/transformation/pipeline.js:42:16)
npm ERR! Darwin 16.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "compile"
npm ERR! node v6.10.2
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>compile: babel src --out-dir lib --source-maps
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>compile script 'babel src --out-dir lib --source-maps'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the apollo-codegen package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     babel src --out-dir lib --source-maps
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs apollo-codegen
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls apollo-codegen
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/moniquehaas/apollo-codegen/npm-debug.log
npm ERR! addLocal Could not install /Users/moniquehaas/apollo-codegen
npm ERR! Darwin 16.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "apollo-codegen"
npm ERR! node v6.10.2
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepublish: rm -rf lib && npm run compile
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepublish script 'rm -rf lib && npm run compile'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the apollo-codegen package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     rm -rf lib && npm run compile
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs apollo-codegen
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls apollo-codegen
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/moniquehaas/npm-debug.log

Does this happen when you npm install -g apollo-codegen? Or are you installing from a local fork?

I have a git clone repository locally. But I do  a global npm install; npm install -g apollo-codegen (I even cleaned up all of my node- and npm installations en then reinstalled them, just to be sure it was not an npm issue. But it does not seem to be.. as I can npm other repo's without any problems

I may be misunderstanding what you're trying to accomplish, but if you want to run apollo-codegen form a local repository the usual process would be to use npm link instead of npm install. Is there a reason you're not using that?
If you're actively developing the codegen code you can use npm run watch to watch for file changes and automatically recompile.

What I am trying to accomplish is a development environment for apollo and therefore apollo codegen. I downloaded the repository to have a look at the files, not really to have a local repository. I reported the problem because I suspected there to be a problem with 'babel src --out-dir lib --source-maps' in the script of apollo-codegen. As I de installed and reinstalled all node and npm and the problem persisted I thought you may like to know about the issue..

What do you mean when you say the problem persisted? What steps did you follow to get the output you posted?
I just reinstalled npm, cloned a fresh repo, and did an npm install followed by npm link. That installs a development copy of apollo-codegen. I also tried npm install -g apollo-codegen on a clean install, and that installs apollo-codegen from npm as usual.
Is that similar to what you tried? Or am I missing something?

Thank you Martijn. This is what I did:  npm for apollo, went fine, then I went on to npm install -g apollo-codegen got my first error (same as above) Then I cleaned up my npm and node using https://github.com/brock/node-reinstall. And I npm-ed apollo, went fine again and   I npm install -g apollo-codegen and got the same error as above.

What do you mean when you say you did npm for apollo or npm-ed apollo? What command did you use here?

Oh sorry,  I did not npm apollo! I followed this instruction from the apollo  website: "You can also manually clone the apollo-ios repository, drag Apollo.xcodeproj into your project or workspace, add a dependency on Apollo.framework to your target." And that went fine..

So you also get the error when you just use npm install -g apollo-codegen, without cloning the repo? Have you still not been able to install it successfully?
What is weird to me is that your output mentions executing prepublish and compile, which shouldn't happen if you're just installing the precompiled package from npm.

Yes I get the same error when I am using npm install -g apollo-codegen. And I wondered about the output that mentions rm -rf lib && npm run compile What is happening here? Is the lib replaced somewhere? Then again babel seems to be complaining about a missing lib? babel src --out-dir lib --source-maps. My knowledge is to shallow to understand what is happening here. I wish I could understand it better to pinpoint why I am running into this error while when you rebuild it nothing really bad is happening.

As with many npm packages, Babel is used to transpile source written using modern JavaScript to more broadly compatible code. The output of this is stored in lib, and that is what is published to npm. So executing Babel should only happen during development or when publishing the package, not when installing from npm.
The output mentions /Users/moniquehaas/apollo-codegen, which I assume is where you checked out the source. Can you retry npm install -g apollo-codegen from another directory?

BINGO! I made a new testdirectory and did npm install -g apollo-codegen and it worked beautifully. Thank you! Now do I put my Xcode project (the one with apollo.xcodeproj) in that directory? So that it will find the codegen when needed (blissfully ignorant .. :-) )  Something babel in /Users/moniquehaas is maybe causing the problem? (sorry still trying to understand it, so that I do not run into it again..)

You can put your Xcode project wherever you want. The script phase you added to it will run the globally installed apollo-codegen.
Yes, you may have a stray node_modules in /Users/moniquehaas or higher up that is being picked up when you run npm from there.

Thank you very much! You pulled me through. Now happily onto experimenting with GraphQL and Apollo! Noting the stray and putting it on my node "need to learn and understand better list" for the end of the week. Have a great day!


Broken links to core datasets in a bunch of /collections pages

Example: https://datahub.io/collections/logistics-data

List of affected pages:

https://datahub.io/collections/logistics-data
https://datahub.io/collections/stock-market-data
https://datahub.io/collections/economic-data
https://datahub.io/collections/demographics
https://datahub.io/collections/education
https://datahub.io/collections/geojson
https://datahub.io/collections/healthcare-data
https://datahub.io/collections/inflation

FIXED


selinuxd is running with spc_t

What happened:
selinuxd container is running with spc_t domain type:
system_u:system_r:spc_t:s0       237236 ?        Ssl    0:01 /usr/bin/selinuxdctl daemon --datastore-path /var/run/selinuxd/selinuxd.db --socket-path /var/run/selinuxd/selinuxd.sock --socket-uid 0 --socket-gid 65535

What you expected to happen:
Based on this https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/internal/pkg/manager/spod/bindata/spod.go#L405
I would expect container should (probably?) run with selinuxd.process
How to reproduce it (as minimally and precisely as possible):
$ kubectl -n security-profiles-operator patch spod spod -p '{"spec":{"enableSelinux": true}}' --type=merge

Anything else we need to know?:
Environment:
System created by vagrant up based on Fedora 36 Cloud image

Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Others:

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle rotten

/remove-lifecycle stale


Question regarding the speed up

I saw the paper use argmax as the equation to obtain the sequence.
I understand that that would be a Viterbi algorithm, where the complexity is again O(n).
I'm confused that how is it faster than Auto-Regressive approach

I saw the paper use argmax as the equation to obtain the sequence.
I understand that that would be a Viterbi algorithm, where the complexity is again O(n).
I'm confused that how is it faster than Auto-Regressive approach

i think the reason is that model only run once, then Viterbi decode.  Auto-Regressive should run n

I saw the paper use argmax as the equation to obtain the sequence. I understand that that would be a Viterbi algorithm, where the complexity is again O(n). I'm confused that how is it faster than Auto-Regressive approach

Hello, thank you for your question. The speed up comes from the fact that NAG-BERT only do the forward computation once, as for autoregressive models they have to do forward pass n times where n is the length of output sequence.


(PDB-1848) make max-frame-size tunable

previously we had a schema that was attempting to validate this as a string,
when it should have been an int.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-stable/8/
Test PASSed.

Looks right to me, and passes tests with both databases.


Change ValueError exception to ModuleNotFoundError

The problem is analyzed here: https://github.com/sfu-db/connector-x/issues/653

Thanks @aimtsou for the PR!


[BUG] Popup error when signing in

Describe the bug
Popup support does not work in sign in windows.
To Reproduce
Steps to reproduce the behavior

Go to medium.com
Click sign in with google
error happens

I think this is related with macos permissions. Can you check if app is requesting any permission ?

try to login udemy.com on your mac


InfoBox is not rendering markdown properly in v.<IP_ADDRESS>62

Describe the bug
Markdown does not appear to be rendered properly in v.<IP_ADDRESS>62
To Reproduce
Steps to reproduce the behavior:

Run this command in the latest official release, and then in the latest beta release and observe the difference:

/usr/local/bin/dialog --title "Test" --message "Message" --infobox "# asdf"

Desktop (please complete the following information):

macOS version 14.5
swiftDialog version <IP_ADDRESS>62

Confirmed, this appears to be working in 2.5.0-4763, thanks Bart!


Show the track duration in the player

Mutagen should be able to extract the duration from the source file

Closing as I'm replacing the built-in blamscamp fork with an external player.


fix: copy loop variable to avoid race conditions

Motivation
Address a race condition found within the check method of the Latency Check. The race condition was caused by the concurrent goroutines capturing the loop variable e from the for loop, leading to unpredictable behavior as this variable was shared across all goroutines.
Closes #27
Changes
Introduced a local copy of the loop variable in the for loop to ensure each goroutine receives a unique, stable copy of the target URL.
For additional information look at the commits.
Tests done
The unit tests succeed now.
TODO

[x] I've assigned this PR to myself
[x] I've labeled this PR correctly

Race cond. still present: https://github.com/caas-team/sparrow/actions/runs/7099127501/job/19323035475

Ready for review.
This PR now also partly addresses #31 but needs to be extended in another PR for the health check and other refinements.


Code the user input to accept selected courses line by line

Updated to handle comma-delimited or line-by-line input.


Look for any open pull requests in the repository with the title "e2e-tests update" and
see if there are recent e2e-tests updates that will be applicable to your change.

Maybe there should be a CI check for this?

Maybe there should be a CI check for this?

Yeah, probably should have been added with the initial implementation. But we do at least have a story in the backlog https://issues.redhat.com/browse/STONEBLD-2401

Maybe there should be a CI check for this?

Yeah, probably should have been added with the initial implementation. But we do at least have a story in the backlog https://issues.redhat.com/browse/STONEBLD-2401

But you know what, I probably could have added that check faster than I found the issue in Jira. Opened #1179


[Analytics] Data export api enhancement

WHAT DOES THIS PR DO?

[x] Enabling export by device name
[x] Enabling export by airqloud id
[x] Support for other frequencies i.e daily and raw

WHAT ISSUES ARE RELATED TO THIS PR?

Jira cards

AN-272

HOW DO I TEST OUT THIS PR?
Use the postman environment. Replace http://<IP_ADDRESS>:5000/ with the latest deploy preview link found in this PR
WHICH ENDPOINTS SHOULD BE READY FOR TESTING?:
Link to postman
IS THERE ANY JENKINS CONSOLE LINK FOR CODE COVERAGE AND BUILD INFO?
None
ARE THERE ANY RELATED PRs?
None

The endpoint is working fine on my end. I have a question about the data returned when someone wants to export by airqloud.

I see that staging and development environments return the same number of results for the Uganda airqloud, is that normal as they have different numbers of sites?
There are two data export endpoints and it's only data export v2 that worked...is it the one you were working on for this PR?

I see that staging and development environments return the same number of results for the Uganda airqloud, is that normal as they have different numbers of sites?
Unfortunately, we are targeting production databases.
There are two data export endpoints and it's only data export v2 that worked...is it the one you were working on for this PR?
Yes, we are focusing on v2. This is just for testing purposes. If you approve v2, then am going to replace v1 with v2 and delete v2. My worry was having this PR merged without corresponding changes in the frontend.

Alright.

The endpoint is working fine on my end. I have a question about the data returned when someone wants to export by airqloud.

I see that staging and development environments return the same number of results for the Uganda airqloud, is that normal as they have different numbers of sites?
There are two data export endpoints and it's only data export v2 that worked...is it the one you were working on for this PR?

I see that staging and development environments return the same number of results for the Uganda airqloud, is that normal as they have different numbers of sites?
Unfortunately, we are targeting production databases.
There are two data export endpoints and it's only data export v2 that worked...is it the one you were working on for this PR?
Yes, we are focusing on v2. This is just for testing purposes. If you approve v2, then am going to replace v1 with v2 and delete v2. My worry was having this PR merged without corresponding changes in the frontend.

I think it is not necessary to delete V2. You can just leave the V2 and the V1 intact. So frontend implementation will just use V2.
In summary, you have done your part no need to revisit /delete things. Thanks.
Thoughts?

The endpoint is working fine on my end. I have a question about the data returned when someone wants to export by airqloud.

I see that staging and development environments return the same number of results for the Uganda airqloud, is that normal as they have different numbers of sites?
There are two data export endpoints and it's only data export v2 that worked...is it the one you were working on for this PR?

I see that staging and development environments return the same number of results for the Uganda airqloud, is that normal as they have different numbers of sites?
Unfortunately, we are targeting production databases.
There are two data export endpoints and it's only data export v2 that worked...is it the one you were working on for this PR?
Yes, we are focusing on v2. This is just for testing purposes. If you approve v2, then am going to replace v1 with v2 and delete v2. My worry was having this PR merged without corresponding changes in the frontend.

I think it is not necessary to delete V2. You can just leave the V2 and the V1 intact. So frontend implementation will just use V2.
In summary, you have done your part no need to revisit /delete things. Thanks.
Thoughts?

This is also fine @Baalmart

@Codebmk should I merge this??


Hamburger Button Menu disappeared at the time you run on mobile emulator

Try setting the property Views.Shell.HamburgerMenu.IsFullScreen = false;
Or: IsFullScreen="true" on the HamburgerMenu in Shell.xaml

The IsFullScreen default is false. Isn't it? Why does that trick work?

I want to point out that a new Ham template proj does not do this on my machine. May I ask @TavoGL, are you running Visual Studio 2015 Update 2 CTP?

Hi, I can report exact same thing. Hamburger button disappears when template switches to Narrow Visual State. Tested on local machine and on device (Lumia 1020 with latest slow ring build). Visual Studio Community 2015 v14.0.24720.00 Update 1.

@JerryNixon. I'm running VS Community 2015 Update 1

I'm using template 10 as an extension. I downloaded from visual studio gallery. I don't know if that can be an issue.

And if that it's not an issue. I think this may count as a bug.

Ok, I maybe found a way to fix missing Hamburger button.
Check References, Microsoft.Xaml.Behaviours.Uwp.Managed and try to update it (restore) back to version 1.0.3... it helped me .. but I think it is not correct way to fix this :)

@vlastimilmaca thanks, good tip

@TavoGL Well ... it turns out that was not it ... Check References for Template 10 and make sure it is on 1.1.8 ... that was the trick that helped me (I had 1.1.6) ... I'm not sure why it is not updating Template10 automatically on build as it should.

Hi folks! This two issues are happening on my machine too.

Could you confirm this occurs when you create a new Hamburger proj from Template?

Here's what I am seeing.

It appears perfect.

@JerryNixon Indeed it appears perfect. Great work btw.
But when I create new Hamburger project (I have latest template pack), it installs Template10 1.1.6 and then there is missing hamburger button. When I upgrade it to 1.1.8 it seems ok.
I recorded whole process ... hope gif will work .. it is quite long ...

@JerryNixon Well I agree with @vlastimilmaca.Works perfect. I had to update

Great work @vlastimilmaca! Thanks for recording the whole process. So everyone with the same issue are able to fix it.


treewide: deprecate ip-up.target

Motivation for this change
Systemd upstream provides targets for networking. This also includes a target network-online.target.
I would like to see ip-up.target completely gone.
In this PR I remove / replace most occurrences since some of them were even wrong and could delay startup.
There are still references that I'm unsure about:

nixos/modules/services/networking/dhcpcd.nix: is this hook really needed?
nixos/modules/services/networking/avahi-daemon.nix: has ordering wantedBy and before if-up.target which looks plain wrong to me. We should get avahi-daemon closer to upstream definition that also includes socket-activation, but this is out of scope of this PR
nixos/modules/services/networking/networkmanager.nix: is this really needed?
nixos/modules/tasks/network-interfaces-scripted.nix: is this needed?
nixos/modules/virtualisation/nova.nix: this module still uses the jobs interface, which was deprecated when I started using nixos

Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I would be thankful for comments about the remaining occurrences as well as deprecating ip-up.target  in general.

Reviewed 14 of 14 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

nixos/modules/services/network-filesystems/drbd.nix, line 58 [r1] (raw file):

      after = [ "systemd-udev.settle.service" "network.target" ];
      wants = [ "systemd-udev.settle.service" ];
      wantedBy = [ "multi-user.target" ];

Verified upstream: https://apt-browse.org/browse/ubuntu/trusty/main/i386/drbd8-utils/2:8.4.4-1ubuntu1/file/lib/systemd/system/drbd.service

nixos/modules/virtualisation/azure-agent.nix, line 182 [r1] (raw file):

      wantedBy = [ "multi-user.target" ];
      after = [ "network-online.target" "sshd.service" ];
      wants = [ "network-online.target" ];

I was suspicious this needed to be up sooner, but verified otherwise: https://github.com/Azure/WALinuxAgent/blob/master/init/coreos/cloud-config.yml

Comments from Reviewable

Looks good to me.
What did you mean by the dhcpcd hook? The start ip-up.target can obviously be removed, but the try-restart of ntpd is still necessary unless ntpd has suddenly learned how to detect interface changes.

Rebased to resolve merge conflicts and also added modified dhcpcd networkmanager and network-interfaces-scripted.
Please review whether the new commits look semantically good to you, I'm not an expert for the scripted networking stuff.

Reviewed 3 of 3 files at r3.
Review status: 16 of 17 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

 but untested

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks broke.

Comments from Reviewable

LGTM. Anything holding this back?

Just a heads up: some networking related tests are now failing https://hydra.nixos.org/eval/1292016#tabs-now-fail

I'm investigating.

Thanks @fpletz. Feel free to revert until I find time to look into this.
By the way, is there a sane way to attach to a test vm to debug the failure?

@groxxda Found some info on https://nixos.org/nixos/manual/index.html#sec-running-nixos-tests and was able to debug with the execute function.
Should be fixed with https://github.com/NixOS/nixpkgs/commit/c58654e2b78e7d3ae97ba96c80ceb3f96236e463.

Thank you @fpletz for looking into this and fixing it!
I'll bring some :beers: when we meet next time.


IPv6 support now disabled (previously working)

I noticed with the latest release, go2rtc no longer listens on ipv6.  I see on commit https://github.com/AlexxIT/go2rtc/commit/e4b68518e54ff869174d08b9917153d7c36289c8 it was disabled.
Example usage:
api:
  listen: "[2041:0:140F::875B:131B]:1984"
rtsp:
  listen: "[::]:8554"

error:
02:05:09.315 FTL [api] listen error="listen tcp4: address 2041:0:140F::875B:131B: no suitable address found"
The rtsp setting also does nothing.
Previous release (1.6.0) worked fine with this same IPv6 config.
IPv6 is very important in today's networking,  and we use it almost exclusively in our ip video setups.
Is further IPv6 support planned?   Thanks!

I didn't know it mattered to anyone. I removed them on purpose to simplify the whole linked code. I'll bring them back in the next versions

https://github.com/AlexxIT/go2rtc/releases/tag/v1.6.2

thank you so much!

Can you explain where you using IPv6? It's some home server. Or some business public or private server?
I still doesn't have much experience with IPv6

hi @AlexxIT,
We use IPv6 at home to run our local network, as well as at our business.  There are no more (limited and expensive) IPv4 addresses, and with IPv6, you don't have to use NAT, which requires less computing power on the router and firewall.
We can assign a Globally Routable IPv6 address to each device as well, and simplify our addressing plan.
We have our own ipv6 gua prefix also, 2001:db8:a20a::/48, and can assign from it to multiple sites geographically.
simple example:
2001:db8:a20a::1/48 = north america core router
2001:db8:a20a:b320::/56 = west coast
2001:db8:a20a:b320::1/64 = west coast router
2001:db8:a20a:b320::2000/64 = west coast dns server
2001:db8:a20a:b320::3000/64 = west coast web server
2001:db8:a20a:b320::1000::1/60 = west coast house
2001:db8:a20a:b320::1000::20/64 = west coast ipcamera front_door
I think it simplifies networking a lot, and most of the networking principles from ipv4 apply to ipv6.   overall i think it reduces the headache of subnetting and limited ipv4 addresses.
if you're isp doesn't support ipv6, you can also sign up for a tunnel broker to get your own ::/48 for free, www.tunnelbroker.net
china is mandating ipv6 support, so newer IOT devices should have ipv6 support built in.  in the USA, the government is also mandating ipv6 support.   adoption will only continue to improve once more and more people learn about it =D

The restore commit is incomplete, unfortunately. WebRTC still broke with the first commit.

Only WebRTC was not fully fixed.


DOC: reorg README

Add sections for:

users (with link to install instructions in docs)
reporting issues
developers (with instructions for install, tests, and docs)

Fixes #177

Thanks! :-D


Add ability to use gMSA's in IIS Deploy Task

Previously, the IIS deploy task would only allow Username/Password combo for creating an app pool. This now allows for a gMSA and let's the user know that if they don't input a password, the user will be treated as such.

The same requirement will be applicable for website physical path authentication as well. I have made necessary changes and floated a PR https://github.com/Microsoft/vsts-rm-extensions/pull/14 in new repo where our on going efforts are going on for IIS Task. All future updates or enhancements or contributions we will accept in new repo

I fixed the issue to be able to make it to next VSTS deployment. So this PR I am closing.


add svg and dot output format options to nscm reports

also adds tests for all report output formats

@julianduque @nw wops, thought I'd ping'd you on this, but didn't, so am now.  PTAL


"critical strike chance" is filtering the other types

"critical strike chance" is filtering the other types , eg. "critical strike chance against .."

You can solve that by adding the similar affixes as well and mark them as red.
https://github.com/josdemmers/Diablo4Companion/wiki/Frequently-asked-questions#how-to-ignore-similar-affixes

I understood, but I only imported a build from maxroll, so I believe that the default behavior, everything that is not imported should come, import as red

Unfortunately there are currently 300+ affixes. Adding them all would make the app really slow. Soo slow it's no longer usable.
Only way to change this is when OCR is fully implemented. But that is currently not yet ready for release.

@farukzahra Latest tests are looking good for OCR. This problem will be solved with the v3 release later this month.

Readme and wiki updated for v3. Version 3 is now available for download.


Adding Codecov GitHub Action

Codecov is a reporting tool that is intended to process any coverage report format into a format that is standard across Codecov.
Reference: https://about.codecov.io

@Uditgulati I want to work on this.

@Uditgulati I want to work on this.

@iamrajiv this is not something that should be prioritized. Pls look at other issues which are of currently more significance.

@iamrajiv this is not something that should be prioritized. Pls look at other issues which are of currently more significance.


Use JSON files for bottle upload data.

This means that we do not need to read formulae or evaluate Ruby at upload time.
CC @xu-cheng who I talked about this with. This will need some testing on our CI before it's definitely ready to merge.

Any last thoughts on this? Hoping to 🚢 soon after addressing that TODO.

@BrewTestBot test this please

@BrewTestBot test this please


illegible graphics in the cloud

https://github.com/markfirmware/gtoolkit-cloud/issues/1

I see the same problem when running GT under Ubuntu 20.04 running in a virtual machine (VirtualBox) under macOS:

No error message in the console output, which just says:
[Glutin] Profile #0 worked

When I connect to the virtual machine from macOS/XQuartz via ssh, I get an error message:
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Error: Could not find a suitable OpenGL profile for this system

plus more lines about the context.

@khinsen https://github.com/markfirmware/gtoolkit-screenshot/blob/7bc39d8d2a61aa03b793a8886b38cc90b43ec17d/mold#L17-L33 is my most recent approach in response to this problem. It uses 18.04 instead of 20.04 but updates g++-10 to what might be the newest version. If you get a chance, can you try it to see if it also helps your scenario? Thanks, Mark.

That works fine for me, thanks for digging this up! Proof:


Update community page

Docs Build status updates of commit 4579336:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/BiographyImages/FrancescoClasadonte_270x270.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/BiographyImages/SimonJackson_270x270.jpg
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


dma: add a DMA driver for the Atmel SAM0 series.

Tested using the memory++ -> memory++ and memory++ -> peripheral modes.
Depending on what happens with #6305 I'll move the fixup changes to the SoC file.
A follow up patches will switch serial TX to use DMA.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #6306   +/-   ##
=======================================
  Coverage   53.14%   53.14%
=======================================
  Files         412      412
  Lines       40148    40148
  Branches     7733     7733
=======================================
  Hits        21338    21338
  Misses      15675    15675
  Partials     3135     3135

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 a73e8fa...7daca96. Read the comment docs.

Dropped the include/dma and tests/ changes, ready for review.

@nzmichaelh I think you dropped the driver as well :)

@galak heh, yeah.
I've rebased and done a few other fixups.  This depends on #6615 landing first before it'll build though.

Still blocked on #6615.


Add chat API documentation

Adds documentation for the chat API being added in https://github.com/R2Northstar/NorthstarLauncher/pull/74. I'll mark this as ready for review when that's merged, in case any details change.

Moving to https://github.com/R2Northstar/ModdingDocs


Daily trend chart

Created a daily trend comparison for the remaining overview pages. The cumulative cost chart is sown by default, with a dropdown to select the daily cost chart.
This particular chart is used on the following overview pages:

OpenShift supplementary
All Cloud filtered by OpenShift cost
Amazon Web Services cost
Amazon Web Services filtered by OpenShift cost
Microsoft Azure cost
Microsoft Azure filtered by OpenShift cost

Note there is a known issue with the interactive legend and chart bars, where styles are not always restored after hiding legend items. I'll create a PatternFly issue and work out a solution in the upstream repo.
https://issues.redhat.com/browse/COST-852

Codecov Report

Merging #1792 (6f34302) into master (5160a70) will decrease coverage by 1.32%.
The diff coverage is 16.98%.

@@            Coverage Diff             @@
##           master    #1792      +/-   ##
==========================================
- Coverage   72.89%   71.56%   -1.33%
==========================================
  Files         303      307       +4
  Lines        5195     5909     +714
  Branches     1020     1409     +389
==========================================
+ Hits         3787     4229     +442
- Misses       1302     1657     +355
+ Partials      106       23      -83

Impacted Files
Coverage Δ

...nts/charts/dailyCostChart/dailyCostChart.styles.ts
100.00% <ø> (ø)

...omponents/charts/dailyCostChart/dailyCostChart.tsx
4.78% <0.00%> (-0.60%)
:arrow_down:

...oard/awsCloudDashboard/awsCloudDashboardWidgets.ts
100.00% <ø> (ø)

...tore/dashboard/awsDashboard/awsDashboardWidgets.ts
100.00% <ø> (ø)

.../azureCloudDashboard/azureCloudDashboardWidgets.ts
100.00% <ø> (ø)

.../dashboard/azureDashboard/azureDashboardWidgets.ts
100.00% <ø> (ø)

...tore/dashboard/gcpDashboard/gcpDashboardWidgets.ts
100.00% <ø> (ø)

...oard/ocpCloudDashboard/ocpCloudDashboardWidgets.ts
100.00% <ø> (ø)

...tore/dashboard/ocpDashboard/ocpDashboardWidgets.ts
100.00% <ø> (ø)

...ntaryDashboard/ocpSupplementaryDashboardWidgets.ts
100.00% <ø> (ø)

... and 119 more

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 5160a70...6f34302. Read the comment docs.

Codecov Report

Merging #1792 (6f34302) into master (5160a70) will decrease coverage by 1.32%.
The diff coverage is 16.98%.

@@            Coverage Diff             @@
##           master    #1792      +/-   ##
==========================================
- Coverage   72.89%   71.56%   -1.33%
==========================================
  Files         303      307       +4
  Lines        5195     5909     +714
  Branches     1020     1409     +389
==========================================
+ Hits         3787     4229     +442
- Misses       1302     1657     +355
+ Partials      106       23      -83

Impacted Files
Coverage Δ

...nts/charts/dailyCostChart/dailyCostChart.styles.ts
100.00% <ø> (ø)

...omponents/charts/dailyCostChart/dailyCostChart.tsx
4.78% <0.00%> (-0.60%)
:arrow_down:

...oard/awsCloudDashboard/awsCloudDashboardWidgets.ts
100.00% <ø> (ø)

...tore/dashboard/awsDashboard/awsDashboardWidgets.ts
100.00% <ø> (ø)

.../azureCloudDashboard/azureCloudDashboardWidgets.ts
100.00% <ø> (ø)

.../dashboard/azureDashboard/azureDashboardWidgets.ts
100.00% <ø> (ø)

...tore/dashboard/gcpDashboard/gcpDashboardWidgets.ts
100.00% <ø> (ø)

...oard/ocpCloudDashboard/ocpCloudDashboardWidgets.ts
100.00% <ø> (ø)

...tore/dashboard/ocpDashboard/ocpDashboardWidgets.ts
100.00% <ø> (ø)

...ntaryDashboard/ocpSupplementaryDashboardWidgets.ts
100.00% <ø> (ø)

... and 119 more

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 5160a70...6f34302. Read the comment docs.


The PropertySheetExtension documentation does not come up

This is on the GitGub website.
When I click the Documentation for the property sheet extensions, I get a 404:
https://github.com/dwmkerr/sharpshell/blob/master/docs/extensions/propertysheetextension/propertysheetextensions.md

Hey @RichardSharpe, thanks for noticing and sharing. Please tell me where you found that link so I can correct it.
https://github.com/dwmkerr/sharpshell/blob/master/docs/extensions/propertysheetextension/propertysheetextension.md
The link above should work (just the s at the end is wrong).

On Wed, Aug 28, 2019 at 1:37 PM Pascal Ried<EMAIL_ADDRESS>wrote:

Hey @RichardSharpe https://github.com/RichardSharpe, thanks for
noticing and sharing. Please tell me where you found that link so I can
correct it.
https://github.com/dwmkerr/sharpshell/blob/master/docs/extensions/propertysheetextension/propertysheetextension.md
The link above should work (just the s at the end is wrong).

It's in the main .md on the GitHub page.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)

On Wed, Aug 28, 2019 at 1:37 PM Pascal Ried<EMAIL_ADDRESS>wrote:

Hey @RichardSharpe, thanks for noticing and sharing. Please tell me where you found that link so I can correct it.
https://github.com/dwmkerr/sharpshell/blob/master/docs/extensions/propertysheetextension/propertysheetextension.md
The link above should work (just the s at the end is wrong).

Another question.
I am trying to follow the instructions, and I have Visual Studio 2019
Community Edition installed, but it cannot find System.Windows.Forms
to add a reference.
Where do I get that thing from?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)

Documentation was updated and redirects now to the correct page, thanks again.
Please try to keep each issue separated. Just start another issue so others can find the answer easier, if they have similar issues/questions.
Anyways, you should be able to add a reference to System.Windows.Forms from the "Add Reference..."  dialog. Like in this image:

Afterwards, you can use "using System.Windows.Forms;" inside your project.
System.Windows.Forms is part of the .NET Framework (not .NET Core). In my case (image above) my project targets .NET Framework 4.
Does that help you?

On Wed, Aug 28, 2019 at 1:55 PM Pascal Ried<EMAIL_ADDRESS>wrote:

Documentation was updated and redirects now to the correct page,
thanks again.
Please try to keep each issue separated. Just start another issue
so others can find the answer easier, if they have similar issues/questions.
Anyways, you should be able to add a reference to
System.Windows.Forms from the "Add Reference..." dialog. Like in this image:
[image: image]
https://user-images.githubusercontent.com/11256873/63891896-87d42880-c9e6-11e9-90ca-18bb409a3e1e.png

Afterwards, you can use "using System.Windows.Forms;" inside your project.
System.Windows.Forms is part of the .NET Framework (not .NET Core). In my
case (image above) my project targets .NET Framework 4.

Ahhh, that helps. Thanks.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)

Closing this issue as the initial problem was fixed.
Feel free to open another issue for other questions, if they are more "general questions", please just name your issue like "questions or help needed" or something.
Feel also free to reopen, if not resolved completely.


Adding a helper for Ubuntu specifically for mod_php

For debian and ubuntu the packages do not name the shared object as mod_php5:
https://packages.debian.org/jessie/amd64/libapache2-mod-php5/filelist
https://packages.debian.org/wheezy/amd64/libapache2-mod-php5/filelist
http://packages.ubuntu.com/trusty/amd64/libapache2-mod-php5/filelist
http://packages.ubuntu.com/precise/amd64/libapache2-mod-php5/filelist
Updating the helper to identify this as it does for rhel.

@dude051 totally didn't see this before I submitted https://github.com/chef-cookbooks/httpd/pull/37! At least it's validating that this is a fix worth doing. :smile:
@someara all things equal, please take @dude051's PR over mine. Thanks!

All good I like the case statement in your PR. Either works :)

#37 merged

Thanks for playing!


implement immutable_registers method

This commit just puts in the immutable_registers method

That was easy.
Thank you!

I can build a new version and publish the crate. But I am right now on a business trip, it may take me a couple of days.

it may take me a couple of days.

No problem, thanks for your help

It's published now as v0.3.7.
Thank you for your contribution.


Cannot use variable for versioning the workflow

I recently had this issue when implementing the test bed for our jenkins pipeline code.
Now trying to call a workflow in the same branch using github actions i run into the same issue.
do the workflow framework developers do not understand that we might have a lot of different versions and the need to use a variable to reference them? or for alocal one at least the version in my current branch?
sorry if thats not your piece of cake and I am at the wrong address.
if you know who are those people who do skip the variables for the versions please share with me :)

Hi @dr-uv-wildner, could you share your workflow to understand how you tried to version it?
For what I understand from your message, you're trying to use / interpolate an input as workflow reference when calling it from another workflow, right?
If so, it's unfortunately not possible to do it currently (there are some thread about this subject on StackOverflow: Reference 1 + Reference 2)


Fix text breaking issue with option select boxes

See this issue https://github.com/alphagov/digitalmarketplace-frontend-toolkit/issues/346.
And this trello card https://trello.com/c/E1WJJbUy
This seems to work. I'm not sure if this is best way to solve this, or if I should be solving frontend problems in a different way though. Any advice is appreciated. See gifs of different browsers below.
It works with chrome, firefox, safari, IE11. IE8 seems to have a wider issue where it's not responsive. At all. I don't know if this is intentional or not?
Add box-sizing: border-box to options-container label
The labels for options in options containers have their width set to
100% of their parent. They also have a lot more padding on the left than
the right so that they don't clash with the checkbox.
Width doesn't take into account padding, which meant that the actual
label element was extending far too much to the right and so strings
that were long enough to need to be broken would disappear out of the
options container before breaking.
By setting the box-sizing to border-box, the padding is included and so
setting the width of the label to 100% prevents it from spilling out on
the right.
I've also adjusted the width for desktop's to 94% (from 90%). This
reduction in width is to allow for the scroll bar which is only present
when viewing on a desktop width screen. Due to the label now being less
wide that it previously was, leaving a 10% gap for the scroll bar looked
too much. Changing to 94% keeps it very similar to what it was.

The line separators look like they are terminating really prematurely in this new version. The word wrap is better (insofar as the bug is gone!) but it does leave more whitespace than strictly necessary in some instances. Can we get the separators to go all the way across regardless? Would probably be happy with the early wrapping if the horizontal lines at least don't have gaps in.
Before <---------------------------- ----------------------------> After

I think the gap is there intentionally to allow for the scroll bar. Different browsers have different scroll bar width, hence the large gap I think. What browser was this on? I'm surprised there's such a big difference in the before after. I think it can easily be adjusted though.

This was on Chrome.

As discussed, on my machine once you get below 769 pixels wide, the media thing changes and you  the lines go all the way across and there are no scroll bars. If you could replicate the above so we can take a look at it it'd be handy.

After consulting with @laurenceberry, it's ok to make the lines 100% for desktop widths. It'll just sit behind the scroll bar and look less weird.

Cool. 👍

Have removed the width reduction. Here are some images of how it looks in desktop mode.
Chrome

Firefox

Safari

IE11

IE8


Backoffice - breadcrumbs

Is your feature request related to a problem? Please describe.
Loss of navigation context and relying on Browser Back button.
Describe the solution you'd like
Breadcrumbs are implemented on the Frontsite, but Backoffice also needs same. Even on Frontsite, going back is non ideal - its similar to the Browser back which does a full refresh of Backed up page. It loses context and goes to the top of start search page. Ideally, if you are going back from the Detail page you'd like to go to the specific search results page and scroll region from which the selection was made. There are a few other issues that may also need to be addressed (such as multi-page skip-jump)

Another problem that I've run into is that certain pages become "not navigable" unless you get out of the current navigation chain. For instance, if we go from Book detail to PhysicalItem detail, then at that point the PhysicalItem search page becomes inaccessible. Of course, there are always ways to work around these issues, but the UX becomes less than optimal.

Breadcrumbs are implemented on the Frontsite, but Backoffice also needs same.

I like the suggestion of having breadcrumbs in the backoffice, I completely agree that it would improve navigation.

Even on Frontsite, going back is non ideal - its similar to the Browser back which does a full refresh of Backed up page. It loses context and goes to the top of start search page. Ideally, if you are going back from the Detail page you'd like to go to the specific search results page and scroll region from which the selection was made.

That makes sense (that's how non single page apps work), the current behavior is to reload the search because we don't save the search history.

There are a few other issues that may also need to be addressed (such as multi-page skip-jump)

This is specifically fixed in inveniosoftware/react-searchkit#157 and will be available shortly. The browser back/forward button worked everywhere except for the search.

Another problem that I've run into is that certain pages become "not navigable" unless you get out of the current navigation chain. For instance, if we go from Book detail to PhysicalItem detail, then at that point the PhysicalItem search page becomes inaccessible. Of course, there are always ways to work around these issues, but the UX becomes less than optimal.

Excellent point that we probably haven't thought of. The reason why we blocked the link in the menu is a workaround to another issue but it's most definitely far from optimal.


Allow Table.read_rows to take an inclusive end key.

This commit adds the end_inclusive keyword argument, which can be explicitly passed to get [start:end] rather than [start:end).
Fixes #3592.

@lukesneeringer thank you for the improvement. Technically this doesn't truly fix #3592 since it is still not possible to query (start:end].


Rabbitmq php Uncaught ErrorException: stream_socket_client(): unable to connect to tcp://localhost:5672

Info:

System info linux
System info disto/version:

Issue:
after docker ps command ， the rabbitmq server is running
then：
run  docker exec -it laradock_php-fpm_1 php /var/www/rabbitmq/receive.php
PHP Fatal error:  Uncaught ErrorException: stream_socket_client(): unable to connect to tcp://localhost:5672 (Cannot assign requested address) in /var/www/rabbitmq/vendor/php-amqplib/php-amqplib/PhpAmqpLib/Wire/IO/StreamIO.php:141
final：
telnet <IP_ADDRESS> 5672
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS>.
Escape character is '^]'.
Connection closed by foreign host.

sorry, i think i should search the soluation for the question seriously.  rabbitmq client should connect the rabbitmq server virtual ip in docker container not local host ip, use  docker inspect laradock_rabbitmq_1


Delete functionality

We would like a way to delete existing wires and components on the schematic~

I am looking to introduce this feature in the near future along with editing the properties of nodes and components on the schematic.


Erc777

Now with additional spec workarounds for our internal usage and for external users.
Note also we already disallow a market creator or designate reporter of address(0) and ownership cannot be transferred to address(0)

Merge conflict resolved, ready to merge?


Added pkg-config support...

Added pkg-config support along with some useful versioning constants for users and package maintainers.

Deleted branch. Isolating pkg-config / versioning specific stuff into its own branch.


typo

Type of Change

[x] Bug fix (non-breaking change, fixes #)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose

Approach

Commands to test

Screenshots

Learning

fabulocity of 10, thank you! merging and pushing to newest build


Slower performance compared to numpy

In order to test the speed advantages for simple operations like addition and assignment to an array, I ran the following code to compare numpy and the OpenCL backend of ArrayFire.
import time
import numpy as np
import arrayfire as af
af.set_backend("opencl")

# This is a benchmark test to compare numpy and arrayfire:

print("The following line displays the ArrayFire build and device details:")
af.info()

aNumPy = np.random.rand(100, 100)
bNumPy = np.random.rand(100, 100)

np_time_start = time.time()

for i in range(1000000):
  cNumPy = aNumPy + bNumPy

np_time_end     = time.time()
np_time_elapsed = np_time_end - np_time_start

print("numpy implementation run took time =", np_time_elapsed," seconds")

aArrayFire = af.Array(aNumPy.ctypes.data, aNumPy.shape, aNumPy.dtype.char)
bArrayFire = af.Array(bNumPy.ctypes.data, bNumPy.shape, bNumPy.dtype.char)

kernel_compilation_time_start = time.time()

cArrayFire = aArrayFire + bArrayFire
af.eval(cArrayFire)
af.sync()

kernel_compilation_time_end     = time.time()
kernel_compilation_time_elapsed = kernel_compilation_time_end - kernel_compilation_time_start

print("Kernel compilation complete. Compilation time = ", kernel_compilation_time_elapsed)

af_time_start = time.time()

for i in range(1000000):
  cArrayFire = aArrayFire + bArrayFire
  af.eval(cArrayFire)

af.sync()
af_time_end     = time.time()
af_time_elapsed = af_time_end - af_time_start

print("arrayfire implementation run took time =", af_time_elapsed," seconds")

I'm getting this as the output:
The following line displays the ArrayFire build and device details:
ArrayFire v3.4.2 (OpenCL, 64-bit Linux, build 2da9967)
[0] INTEL   : Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz, 28135 MB
numpy implementation run took time = 8.37395715713501  seconds
Kernel compilation complete. Compilation time =  0.035042762756347656
arrayfire implementation run took time = 60.80797052383423  seconds

Is there something wrong here?

@ShyamSS-95 I was just talking to @mchandra about this over chat. The reason is because at these sizes, the overhead of kernel launching is much greater than the actual operation in OpenCL.
You should try it by increasing the array sizes and decreasing the number of iterations.
This is what I get at 4096 x 4096 for 1000 iterations:
$ AF_OPENCL_DEFAULT_DEVICE=2 python examples/helloworld/helloworld.py
ERROR: GLFW wasn't able to initalize
The following line displays the ArrayFire build and device details:
ArrayFire v3.5.0 (OpenCL, 64-bit Linux, build 06e605b0)
-0- AMD     : Hawaii, 8143 MB
-1- NVIDIA  : GeForce GTX 950, 1994 MB
[2] INTEL   : Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz, 15985 MB
-3- AMD     : Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz, 15985 MB
numpy implementation run took time = 48.15489220619202  seconds
Kernel compilation complete. Compilation time =  0.09143519401550293
arrayfire implementation run took time = 37.75742530822754  seconds


Error

please use the lastest visual studio 2022 and install the latest dev kit of c++

install the latest desktop development kit for c++

It still does not work

It still does not work

Try building NativeLib first then running the Kernel

I can't build NativeLib. it gave me this error

Can't build it because Allocator does not have to Reallocate should I replace it with Allocate

Clone the latest sourcre.

let's talk on discord

Ok

Ok this is me: SaluranSains#6313


Transition issues between 1.6.5 and 2.0.0-beta.1

I'll be actively updating this thread as I (hopefully) solve the problems I currently have.
I'm using vuetable-2 in a desktop app (electron + webpack) with data mode. Vue version 2.5.13. I've tweaked quite a few things over time to get the behaviour I wanted so I imagine some of my problems could be unique to my codebase. I'll number them for easier referencing.
1. On displaying all my dynamic tables:
[Vue warn]: Error in render: "TypeError: Cannot read property 'replace' of undefined"
found in
---> <VuetableColGroup>

TypeError: Cannot read property 'replace' of undefined
    at VueComponent.columnClass

I thought maybe this was related to data formatting, but it's unclear. The formatting appears correct (after I changed 'callback' to 'formatter' and removed instances of string value instead of function).
2. Pagination not working the first time a table is displayed.
This is possibly related to the fact that the table doesn't have data on mount, not until after. It corrects itself if I reload:
this.$nextTick(() => {
  this.$refs.table.reload()
})

which is called on a watch() on the table data.
The tablePagination object accessed in the pagination component is null initially.
3. Changing page results in this error:
[Vue warn]: Duplicate keys detected: '1'. This may cause an update error.
found in
---> <Vuetable>

This is when the next page has two rows. When it has seven rows:
[Vue warn]: Duplicate keys detected: '1'. This may cause an update error.
[Vue warn]: Duplicate keys detected: '2'. This may cause an update error.
[Vue warn]: Duplicate keys detected: '3'. This may cause an update error.
[Vue warn]: Duplicate keys detected: '1'. This may cause an update error.
[Vue warn]: Duplicate keys detected: '2'. This may cause an update error.
[Vue warn]: Duplicate keys detected: '3'. This may cause an update error.

Number of errors seems to be number of rows - 1.
One thing is that I have my own initial page implementation, and current page is tracked in my pagination component and kept in sync with the pagination in vuetable.
4. Some kind of warning about my data which mentioned using track-by to fix it.
I added track-by='id' and it has gone away. But I wonder if this is related to problem 3 and I haven't properly addressed this. All the rows have an id field which is not displayed (not in 'fields' but in the data objects themselves). I will try adding ID to fields and setting visible=false.

Vuetable is trying to generate a specific CSS class name for one of your column by guessing from the name option of field definition or the "name" of the component. So, please check all name option of your fields definition if any of them is not a string, or the component object you specified in the name option does not have a "name" key.

Since you're using Data mode, that probably is the case.

Check your pagination component implementation again.

Need to see the actual error message and some of your data in order to identify if they're related.

I neglected to add a name property to my new field component. Error's gone now. Thanks 👍

Looking into the rest currently.


Docker Swarm?

hello,
Can you explain why not use Docker1.12 with Docker swarm mode(SwarmKit) while you choose the Docker Swarm?

Docker swarm mode  does not support the third party network for the present,only the Docker Swarm supports

thanks a lot.

More specific information about the swarm mode ,please have a reference to this link:https://gist.github.com/gkvijay/e8e8f2a6a00c9887fb2abfb0adf742b3


After renaming project ios build error

** BUILD FAILED **
The following build commands failed:
CompileC /Users/ranvir/wslab/Myapp/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/React.build/Objects-normal/x86_64/RCTRootContentView.o Base/RCTRootContentView.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
CompileC /Users/ranvir/wslab/Myapp/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/React.build/Objects-normal/x86_64/RCTStatusBarManager.o Modules/RCTStatusBarManager.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(2 failures)
Installing build/Build/Products/Debug-iphonesimulator/Myapp.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2):
Failed to install the requested application
An application bundle was not found at the provided path.
Provide a valid path to the desired application bundle.
Print: Entry, ":CFBundleIdentifier", Does Not Exist
Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/Myapp.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

Hey @ranvirgorai , What version of react-native are you using?

Same issue

@danieljvdm What version of react-native are you using?

I was on 0.43.4

I don't think the RN version matters here @junedomingo . My workspace was renamed but not the project.

Have you tried cleaning it? (Product > Clean)

I'll try, but I don't think that'll change the fact that the workspace has an incorrect reference to the project. sportapp was the old name and it didn't change the reference to the new one (NowNow).

Found the problem - contents.xcworkspacedata isn't updating the project file reference to the new name.


Deprecate java docker image

Pipeline breaks because  frolvlad/alpine-oraclejdk8:slim is deprecated .
I had to switch to frolvlad/alpine-oraclejre8:slim to get it to work.

Encountered same problem... changed all Dockerfile(s) as in ...
#FROM frolvlad/alpine-oraclejdk8:slim
FROM frolvlad/alpine-java
solution from samaddico may be better for 'slim' edition


Add evaluations database setup scripts for windows and bash

We should communicate more.  This isn't done.

Which one?
src/main/resources/SQL/development/bash/sql/pg_evaluations_install.sh
src/main/resources/SQL/development/bash/pg_evaluations_install.sh


openbrf: fix build

Description of changes
ZHF: https://github.com/NixOS/nixpkgs/issues/265948
https://hydra.nixos.org/build/239129983
openbrf code is from 2016 and one of its dependencies, vcglib was updated from v1.0.1 (2017) to a newer version. this caused a couple of problems:

eigen no longer included in the vcglib sources (easy to fix)
variable BoundaryWeight is renamed and split in vcglib (easyish)

to fix (2) patch openbrf so it initializes the replacements for BoundaryWeight. Luckily, this is only used in one place in an optimization algo so the patch is straight forward.
old BoundaryWeight new BoundaryQuadricWeight, QualityQuadricWeight
testing -- needs GL to run and that doesn't work for me on nix on ubuntu. launched with QT_XCB_GL_INTEGRATION=none result/bin/openBrf and it ran but not sure how to test if actually does what is expected.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

1 package built:

openbrf

Result of nixpkgs-review pr 266190 run on aarch64-linux 1

1 package built:

openbrf

Sad to see you close this, i liked your fix. Sorry if i'm being too nitty. Would you mind if i opened a new PR with your fix, tagging you as co-author?

Sad to see you close this, i liked your fix. Sorry if i'm being too nitty. Would you mind if i opened a new PR with your fix, tagging you as co-author?

yeah- i shouldn't have closed it. sorry about that. it just seems the comments are now beyond the lines of code changed.

Sad to see you close this, i liked your fix. Sorry if i'm being too nitty. Would you mind if i opened a new PR with your fix, tagging you as author?

feel free to take the code and make changes. i do not need any co-author credit.
i just pushed the prior version, which you can find here:
https://github.com/robert-manchester/nixpkgs/pull/new/openbrf-fix-newvcg

closing due to differing opinions


Add NeedPostProcess for Parser interface to improve performance of csv parser and some external parser

Before this PR, it took 15s to render a 900 lines csv file with 6 columns on my macOS pro 2020.
After this PR, it will spend about 250ms.
So PostProcess is very slow and it's useless for rendering csv file.
This PR also make some external markup tool faster to allow them ignore PostProcess.

disabling postprocess means you don't get sanitization

disabling postprocess means you don't get sanitization

No. sanitization has still be kept. see https://github.com/go-gitea/gitea/pull/15153/files#diff-6e514d0fdd340f9204579f783328a26600737870a4ea70726b5b58ffbe5667f5R94


Unmapped error found. Code: 2600, Message: cache lookup failed for function 0, Affected entities: Employee table

Hi @staticlibs, Morning :-)
Any idea on below error which I get while connecting from application and update entry of table
Unmapped error found. Code: 2600, Message: cache lookup failed for function 0

Hi @psrinivasa2 , this is Postgres internal error, it may indicate data inconsistency or data corruption. The same intermittent error was reported on vanilla Postgres version 15.4 (the same version WiltonDB is based on).
Can you please do the following to narrow this down:

export the problematic T-SQL DB with wdb_backup
initialize new DB cluster from scratch (for example: stop windows service, rename data dir, rerun the installer)
restore problematic DB dump into clean DB cluster
run the workload that uncovers this issue

Assuming this is reproducible (this also applies to problems in #23), would it be possible for you to do one of the following options:

anonymize confidential data in this T-SQL DB and share the dump with me privately (like GDrive link to email)
set up a secure remote workplace (RDP etc) in your environment, where I can connect, set up dev environment and debug Postgres/Babelfish internals on your data with this data never leaving your premises

For such intermittent/hard to reproduce problems, I really would like to get to the bottom. Just only the error message itself is not enough to investigate this. If options above are not possible, then you need to get some engineer on your side to enable Postgres and Babelfish verbose logging (what exactly to enable depends on a problem - can elaborate), reproduce the problem, and then anonymize and share verbose logs.

thanks for the details @staticlibs  I will check on it

Hi @staticlibs, Good Morning :-)
Please find the attached log file, this does not have any confidential data, hence sharing it here.
postgresql-Fri.log

log_statement = 'all'
the above statement already been there in postgresql.conf. where should I mention babelfishpg_tds.tds_debug_log_level = 2, which config file?

one more thing to convey if it get clash, I have already enabled select * from pg_stat_statements feature

I suggest to set these options with wdb_config (it is included with installer in bin dir) - it will reload the server settings automatically:

On your screenshot log_statement is commented out with #, when set with wdb_config it will be written to postgresql.auto.conf.

Apologies, Now updated the setting and restarted WiltonDB, Alex @staticlibs, I have emailed you the log file details, please check

@psrinivasa2 , confirming that I've received the log. Will analyze it and report back.

@staticlibs  where are we on releasing the detail log installer to troubleshoot this issue?

@psrinivasa2 , installer with support for printing backtraces for all reported errors should be ready either later today or tomorrow. It should allow to track the problem to the exact place (hopefully - exact T-SQL function) where it happens.

@psrinivasa2 , published debug installer release page, wiltondb3.3_debug_10.15.0.msi  download there. If possible, please run the problematic workload on this version, it should include detailed backtraces for all error messages. This version may be up to 1.5 times slower than the normal one.
Additionally it would be better to set:
babelfishpg_tds.tds_debug_log_level = 3

This TDS setting is unrelated to backtraces, it will log all networking packets. It makes log even more verbose, but problematic SQL was not logged for some reason when it is set to 2.

Thanks much Alex @staticlibs

@psrinivasa2 , with the help of your detailed logs I've reproduced the problem and found the root cause. The problematic query uses parameter of type binary(8). Babelfish confuses this parameter type with rowversion one (that itself is defined as binary of size 8), so it is unable to find type conversion function for it and fails with error about "function 0" (where 0 is InvalidOid). I have a fix and will create updated MSI over the weekend.
As a workaround in client app, the problem should not happen if you change binary to varbinary for that query or change the length from 8 to some other value.

thanks @staticlibs

For the record, link to the upstream Babelfish issue I've opened for this problem - #2762.

Hi Alex,
Getting similar issue in other scenario with below error message
Code: 1088, Message: Cannot insert an explicit value into a timestamp column.
I have mailed you the table structure and log file details

@psrinivasa2
This problem is unrelated to binary(8), I've created a separate issue for it - #64.


Best effort support for all Hugging Face transformers models

With https://github.com/huggingface/text-generation-inference adopting a less friendly license, this seems like a good opportunity to add best effort support for all Hugging Face transformers models that generate text e.g., via AutoModelForCausalLM and AutoModelForSeq2SeqLM. This would allow them to take advantage of vLLM's other serving features while specific models can retain optimized implementations or gain them as they are implemented

https://github.com/huggingface/text-generation-inference/blob/ecf6dc3a5a31c1b0e1ed48988ddf2416b5e35660/server/text_generation_server/models/causal_lm.py#L451
https://github.com/huggingface/text-generation-inference/blob/ecf6dc3a5a31c1b0e1ed48988ddf2416b5e35660/server/text_generation_server/models/seq2seq_lm.py#L501

any updates here?

Considering there are 35 distinct model architectures defined as of now, I think we are achieving "best effort". Not to mention several models are implemented by aliasing within the llama architecture. Please open an issue for any specific models you would like to see supported!


Improvement on "focus" field README.md

It is a really nice component. But the documentation could be improved (mainly about some requirement on input fields for the card number, expired date and CVC). For example, maybe it is better to specify that one would need to give their input special and fixed input name for the focus function:
<Input name="name" /> for name input: name="name" required
<Input name="number" /> for card number input: name="number" required
<Input name="expiry" /> for expired date input: name="expiry" required
<Input name="cvc" /> for cvc input: name="cvc" required
or the focus feature such as <Card focused="expiry" /> would not work.
Or maybe it would be even better to allow users to customise their input name, and set a way for <Card name="" cardNumber="" expiry="" cvc="" /> to read those custom input names, like
<Card
    inputNames={
       name: "my input name for the card name"
       cardNumber: "my input name for the card number"
       expiry: "my input name for the expire date"
       cvc "my input name for the cvc"
    }

because <Card /> prop names like name, number seems to be pretty common?
Besides, it may also be beneficial for developers to integrate formatCreditCardNumber formatCVC formatExpirationDate and Payment plugin in your code example into this repo as API functions because similar functions are usually used together with card payment.

You are absolutely correct, the documentation on "focused" prop is poor

I agree with this.

Feel free to submit a PR to improve it.


Testing
Please run npm install to install all dependencies as well as the new hooks and then do a well-typed and a wrong test commit and try to push to a remote test(!) branch.

@orlandohohmeier I have made a test branch out of your branch, npm i and then made a small change.
Here what I was able to commit https://github.com/dcos/dcos-ui/commit/ef0e291146e762406fcab5c29e2659cdf676acf3 I'm guessing it's valid?

@weblancaster you should rm -rf node_modules and try again.

It has two ✅  and an owner ✅  merge? :)


Introduce BugPattern for removing duplicate StepVerifier#expectNext calls

Woowee! That was a freaking mess.
At first I thought I could easily solve this with a little Refaster pattern. Boy was I wrong. So many edge cases, some many little thingies. So I went down the Error Prone rabbit hole, and boi was it deep. Who knew simply traversing nodes in an AST could be such a mess? Hell, even internal functions of Error Prone (yes I'm talking about you ASTHelpers.findEnclosingNode) have infinite while loops in them. BWAAAAH!
Anyway, it's 1AM in the night and I think I have a fully working version. As in, I made all the tests I could think of and they pass. Now it's up to the Lvl. 200 mafia bosses @rickie and crew to poke some holes in this dumpster fire of a bugpattern.
To explain a little bit what is going on:
I do a little for-loop where I step to all the other method invocations. The smart logic here is getChild(), which jumps n steps over the next few nodes (child nodes) to find the next expectNext call. By jumping 2 steps at a time, we visit all the method calls. Other types of nodes that it may visit should be eliminated either by the matcher or by the position check.
Also I miss you 😢😢😢😢😢😢❤

Sometimes it helps to visually review the PR, so here's a little illustration of this PR's contents:

Nice parting gift @SimonBaars! :smile:
W.r.t. the build failures: Running ./apply-error-prone-suggestions.sh (with #441) should (largely) take care of those. :sparkles:
Shame that the various expectNext overloads aren't supported by Refaster's @Repeated annotation; we have a similar issue for ImmutableList.of and friends. Thinking of all the combinations that'd be necessary, I agree that a BugChecker is indeed the way to go.
I'll let Lvl. boss @rickie do the first review. :rofl:

Nice job @SimonBaars! It was fun to pair up on this a few times! (Still sad to see you go man 😢)
Currently review backlog is a bit full, so it'll probably be next week before I can do a proper deep-dive 😉.

Currently review backlog is a bit full, so it'll probably be next week before I can do a proper deep-dive wink.

You're beginning to turn into a manager!

@rickie

@rickie Hey, sorry, I'm not following this thread very actively.
What would you still like me to take a look at?

There are some open points that I haven't addressed yet. If you want, you can take a look there 😄.


Allow me to provide a custom window title

When using the Windows-style layout, it looks like there's an extra line-feed above the code.
That got me thinking that it would actually be a really nice/useful feature to be able to "title" the code by providing a custom window title.
Expected Behavior
Example:

Actual Behavior

Alternative
It could also be allowed to extend the code up into the title bar to remove the extra top-padding:

You can add a window title by clicking at the top-center of the window, like so:

Oh totally missed that! I clicked in the left side!

No worries! We don't talk about the feature much, because it isn't core to Carbon, but it is there.


HTTP Request properties "learn more" tooltips link botbuilder-samples

Describe the bug
For the HTTP Request property sheet, the "Learn more" links for the "?" help icons all navigate to BotBuilder-Samples/experimental/common-expression-language/README.md file on GitHub
Version
1.0.0
Browser

Electron distribution
OS

[x] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Open a bot project
On the design canvas, add an HTTP Request by [+] -> Access external resources -> Send an HTTP Request
From the property sheet for the HTTP Request invoke the tooltips for any of the following properties:  Url, body, result property, content type, or response type.
Click on the "Learn more" link found in the tooltip.

We launch a browser window that displays the boatbuilder-samples/experimental/common-expression-language README.md on GitHub.
Expected behavior
Expect to see a browser window launched that takes me to appropriate documentation

Hey @sgellock Thanks for reporting the broken doc link. I have already fixed it in PR3238.


Hammer/map changing

What's new

Changing levels will reset zoom levels (configurable)
Clicking on robots will center and zoom onto robot (configurable), switches to robot's level too

https://github.com/open-rmf/rmf-web/assets/5383623/5a506a00-c0fc-43eb-bab6-ac28b9f0ed95
Self-checks

[ ] I have prototyped this new feature (if necessary) on Figma
[ ] I'm familiar with and follow this Typescript guideline
[ ] I added unit-tests for new components
[ ] I tried testing edge cases
[ ] I tested the behavior of the components that interact with the backend, with an e2e test

I just added a FullscreenIcon on the layers to change the camera view back on the same level, hopefully it won't affect https://github.com/open-rmf/rmf-web/pull/838


Parsable error

Hi, is there any way to get an excpetion fit to mangopay exception way? My wish is a mean to detect when the error is a resource not found exception

Hello @jonathan-bibas,
Thank you for your suggestion. We are going to improve this.
Have a nice day,

Hi @jonathan-bibas
There is already a custom class for exception handling here
Do you feel the need for more? If so, can you please provide details?
Kind regards,
SoloJr