Error in page

I believe the line that says "option to also with the incompatible rows to a log file." should read "option to also write the incompatible rows to a log file."

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

ID: 8d9bdbe9-7671-7db4-a123-7a84b0c59711
Version Independent ID: d3ecd1af-7cce-3ac4-3bd7-ec5a79681fef
Content: Sink performance and best practices in mapping data flow - Azure Data Factory & Azure Synapse
Content Source: articles/data-factory/concepts-data-flow-performance-sinks.md
Service: data-factory
Sub-service: data-flows
GitHub Login: @kromerm
Microsoft Alias: makromer

@iposner-newsig Thank you for sharing feedback. We are actively validating it. We will share updates soon.

@iposner-newsig Created PR for this. https://github.com/MicrosoftDocs/azure-docs-pr/pull/185667. Thank you.

@kromerm Could you please review below PR and merge changes. Thank you.
MicrosoftDocs/azure-docs-pr#185667

#sign-off

PR will be merged and changes are going to reflect in doc in next build.


Change installer to stable branch

The s branch is the stable branch, we've already had a few breaking PRs merged, naturally enough. This avoids those breakages hitting users.

LGTM
But we need to update the stable branch.

Updated I just pushed there


Mention Errors on the Front End

Mention error explicitly on the front-end rather silently logging them
on server side

Current coverage is 51.25% (diff: 0.00%)

Merging #536 into development will decrease coverage by 1.07%

@@           development       #536   diff @@
=============================================
  Files                4          4
  Lines              428        437     +9
  Methods             44         44
  Messages             0          0
  Branches            58         59     +1
=============================================
  Hits               224        224
- Misses             204        213     +9
  Partials             0          0

Powered by Codecov. Last update 2a5d34a...705d766


How to make posts in the added collection visible in category tab?

I want to make my posts displayed by its category when ‘category’ tab is clicked.
In order to do this, I uncommented the ‘jekyll-archives’ part in _config.yml.
For posts in collections which are already in the template(ex.  Blog posts), it works.
However, posts that are located in collection that I added don’t appear when I click the category tab. What should I do?
(To add collection, I changed _config.yml collections part and navigation.yml file, added [collection_name].html file in _pages folder, and wrote new posts with category in the folder named _study that I made. Posts in _study folder is visible in the ‘study’ tab, but not visible in the ‘category’ tab.)

Do you mean that you want posts sorted by category - as opposed to date - when something is clicked, or are creating a new category that appears in the menu?

I want posts sorted by category. (I guess /_pages/category-archive.html does this)
I wrote new posts as below, and it appears in the 'study' menu, but not in 'Category' menu(which links to category-archive.html)
title: 'test'
date: 2024-03-18
permalink: /study/2024-03-18-study-1
categories: coding
tags:

cool posts
category1
category2

This post will show up by default. To disable scheduling of future posts, edit config.yml and set future: false.
However, for posts not in study menu, they are visible when I click 'Category' menu and sorted by their categories.

Do you mean that you want posts sorted by category - as opposed to date - when something is clicked, or are creating a new category that appears in the menu?

If you visit arcstone09.github.io site and go to 'Category' menu, posts with categories name 'coding' would be displayed. A post titled 'test' which is visible in Study menu is also classified as 'coding' category, but it is not shown in the 'Category' menu. Thanks a lot.


Expose recognized transformation

Case: instead of a gesture implicitly transforming the view, we would like to explicitly transform the items. As the items become transformed, they emit transformed event that allows the app to react by either removing too large or small items or adding new items.
This adds flexibility for programmers.
The issue emerged from the needs of the infinity example app.

Proposal
Enhance input manager API by letting targetItem be a function. The function is called every time when the target would be transformed.
An alternative way would be to provide the transformation in the event object of gesturemove and allow targetItem be null. However, this might make the code a bit dirty to read because the app should listen also wheel and programmer might still think what to do with gestureend and gesturestart.
Example:
var transformHandler = function (itr) {
  // transform something
}
var tou = new tapspace.Touchable(view, sourceItem, transformHandler)
var whe = new tapspace.Wheelable(view, sourceItem, transformHandler)
tou.start({ translate: true, scale: true })
whe.start({ scale: true })


Variance of symbolic shape

Makes test_symbolic_var pass

It's likely correct, but this and symbolic shape mean need tests in symbolic_ops and symbolic_jit to make sure it's generating a kernel that uses variable input, and jit works. Either you can add relevant tests in those files, or i can take a look later this week (busy with mlperf this week).

done in #4843


Loading and visualizing Petrel surfaces in python

Hey!
So I've made a little notebook on how to load some weird Petrel surfaces (faults and horizons) into Python and how to visualize them with pyvista.
I ran into some hurdles converting that properly to GemPy - so I've not added that functionality yet - but I should be able to do get that done sometime in the next few days.

Awesome, thanks @pytzcarraldo


Mutate values for light color temperature and white value

Description:
Fixes usage of templates for the values color_temp and white_value in light component. Instead of just validating for int the validator tries to mutate them into a int.
Related issue (if applicable): fixes #4646
Pull request in home-assistant.github.io with documentation (if applicable): -
Example entry for configuration.yaml (if applicable):
 - service: light.turn_on
        data_template:
          entity_id: light.west_light
          brightness: >-
            {% if is_state('input_boolean.sleepmode_enabled', 'on') %}100{% else %}255{% endif %}
          color_temp: >-
            {% if is_state('input_boolean.sleepmode_enabled', 'on') %}500{% else %}300{% endif %}

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Thanks!


handle bad filenames

This should take care of:
https://github.com/Mindwerks/worldengine/issues/113

Good idea updating the CHANGELOG, we should use it more

Really minor comments: merge it!

Fix #113

Looks good to have a fixed filename for grayscale and riverrs when running the console app. Should we have more flexibility when we will have an independent library?
Looks good to me, merge it!

We can always be more flexible, but with the CLI always prefixes the seed number. In theory, when used as a library... it is up to the developer to send the filename to the function. So in the GUI for example, we can leave it up to the user to specify the filename and format for output.


Add new Quiver servers

Add new Quiver servers.  Each of these new servers is a $5 Ubuntu Droplet, running in the NY region on Digital Ocean, and CloudFronted through Amazon.  They all have logging setup as per instructions on https://github.com/uProxy/freedom-social-quiver-server/blob/96e6b7ad029928c38d191b4404d567176cd3c631/README.md

:+1:


chore: skiapp to 0.0.83

chore: Promote skiapp to version 0.0.83

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


mixin: Grafana Dashboards fail server side apply

Thanos, Prometheus and Golang version used:
quay.io/thanos/thanos:v0.22.0
Object Storage Provider:
GCS
What happened:
When using the Thanos mixin with kube-prometheus, the resulting yaml manifests fail server side apply (and its validation). In particular, grafana-dashboard-bucket_replicate and grafana-dashboard-query_frontend are violating a naming convention, the rest is fine. This makes using the mixin as part of a GitOps workflow impossible, see also https://github.com/fluxcd/kustomize-controller/issues/491#issuecomment-973988095:
Error from server (Invalid): ConfigMap "grafana-dashboard-bucket_replicate" is invalid: metadata.name: Invalid value: "grafana-dashboard-bucket_replicate": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
Error from server (Invalid): ConfigMap "grafana-dashboard-query_frontend" is invalid: metadata.name: Invalid value: "grafana-dashboard-query_frontend": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')

What you expected to happen:
Generation of valid yaml manifests that can be applied.
How to reproduce it (as minimally and precisely as possible):
I tried to set up a minimal test case for half an hour and got fed up with it, sorry. Just try to use the mixin with kube-prometheus and server side apply. See the logs below and the linked issue for additional context.
Full logs to relevant components:
Logs

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.6", GitCommit:"d921bc6d1810da51177fbd0ed61dc811c5228097", GitTreeState:"clean", BuildDate:"2021-10-27T17:50:34Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.5-gke.1802", GitCommit:"d464a255a4acb8dca1e0914586f4f5085681fb51", GitTreeState:"clean", BuildDate:"2021-10-21T21:43:23Z", GoVersion:"go1.16.7b7", Compiler:"gc", Platform:"linux/amd64"}

$ kubeval kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains an empty YAML document
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-alertmanager-overview)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-apiserver)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-bucket_replicate)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-cluster-total)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-compact)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-controller-manager)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-k8s-resources-cluster)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-k8s-resources-namespace)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-k8s-resources-node)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-k8s-resources-pod)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-k8s-resources-workload)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-k8s-resources-workloads-namespace)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-kubelet)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-namespace-by-pod)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-namespace-by-workload)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-node-cluster-rsrc-use)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-node-rsrc-use)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-nodes)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-overview)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-persistentvolumesusage)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-pod-total)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-prometheus-remote-write)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-prometheus)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-proxy)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-query)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-query_frontend)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-receive)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-rule)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-scheduler)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-sidecar)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-store)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-workload-total)

$ kubectl -n monitoring apply -f kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml --dry-run=client
configmap/grafana-dashboard-alertmanager-overview created (dry run)
configmap/grafana-dashboard-apiserver created (dry run)
configmap/grafana-dashboard-bucket_replicate created (dry run)
configmap/grafana-dashboard-cluster-total created (dry run)
configmap/grafana-dashboard-compact created (dry run)
configmap/grafana-dashboard-controller-manager created (dry run)
configmap/grafana-dashboard-k8s-resources-cluster created (dry run)
configmap/grafana-dashboard-k8s-resources-namespace created (dry run)
configmap/grafana-dashboard-k8s-resources-node created (dry run)
configmap/grafana-dashboard-k8s-resources-pod created (dry run)
configmap/grafana-dashboard-k8s-resources-workload created (dry run)
configmap/grafana-dashboard-k8s-resources-workloads-namespace created (dry run)
configmap/grafana-dashboard-kubelet created (dry run)
configmap/grafana-dashboard-namespace-by-pod created (dry run)
configmap/grafana-dashboard-namespace-by-workload created (dry run)
configmap/grafana-dashboard-node-cluster-rsrc-use created (dry run)
configmap/grafana-dashboard-node-rsrc-use created (dry run)
configmap/grafana-dashboard-nodes created (dry run)
configmap/grafana-dashboard-overview created (dry run)
configmap/grafana-dashboard-persistentvolumesusage created (dry run)
configmap/grafana-dashboard-pod-total created (dry run)
configmap/grafana-dashboard-prometheus-remote-write created (dry run)
configmap/grafana-dashboard-prometheus created (dry run)
configmap/grafana-dashboard-proxy created (dry run)
configmap/grafana-dashboard-query created (dry run)
configmap/grafana-dashboard-query_frontend created (dry run)
configmap/grafana-dashboard-receive created (dry run)
configmap/grafana-dashboard-rule created (dry run)
configmap/grafana-dashboard-scheduler created (dry run)
configmap/grafana-dashboard-sidecar created (dry run)
configmap/grafana-dashboard-store created (dry run)
configmap/grafana-dashboard-workload-total created (dry run)

kubectl -n monitoring apply -f kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml --dry-run=server
configmap/grafana-dashboard-alertmanager-overview created (server dry run)
configmap/grafana-dashboard-apiserver created (server dry run)
configmap/grafana-dashboard-cluster-total created (server dry run)
configmap/grafana-dashboard-compact created (server dry run)
configmap/grafana-dashboard-controller-manager created (server dry run)
configmap/grafana-dashboard-k8s-resources-cluster created (server dry run)
configmap/grafana-dashboard-k8s-resources-namespace created (server dry run)
configmap/grafana-dashboard-k8s-resources-node created (server dry run)
configmap/grafana-dashboard-k8s-resources-pod created (server dry run)
configmap/grafana-dashboard-k8s-resources-workload created (server dry run)
configmap/grafana-dashboard-k8s-resources-workloads-namespace created (server dry run)
configmap/grafana-dashboard-kubelet created (server dry run)
configmap/grafana-dashboard-namespace-by-pod created (server dry run)
configmap/grafana-dashboard-namespace-by-workload created (server dry run)
configmap/grafana-dashboard-node-cluster-rsrc-use created (server dry run)
configmap/grafana-dashboard-node-rsrc-use created (server dry run)
configmap/grafana-dashboard-nodes created (server dry run)
configmap/grafana-dashboard-overview created (server dry run)
configmap/grafana-dashboard-persistentvolumesusage created (server dry run)
configmap/grafana-dashboard-pod-total created (server dry run)
configmap/grafana-dashboard-prometheus-remote-write created (server dry run)
configmap/grafana-dashboard-prometheus created (server dry run)
configmap/grafana-dashboard-proxy created (server dry run)
configmap/grafana-dashboard-query created (server dry run)
configmap/grafana-dashboard-receive created (server dry run)
configmap/grafana-dashboard-rule created (server dry run)
configmap/grafana-dashboard-scheduler created (server dry run)
configmap/grafana-dashboard-sidecar created (server dry run)
configmap/grafana-dashboard-store created (server dry run)
configmap/grafana-dashboard-workload-total created (server dry run)
Error from server (Invalid): ConfigMap "grafana-dashboard-bucket_replicate" is invalid: metadata.name: Invalid value: "grafana-dashboard-bucket_replicate": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
Error from server (Invalid): ConfigMap "grafana-dashboard-query_frontend" is invalid: metadata.name: Invalid value: "grafana-dashboard-query_frontend": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')

It seems this has been fixed before... https://github.com/thanos-io/thanos/commit/2ed64cab2fde4ebb8674fe68eaaff381739011a0#diff-8b2bee54f896c2326a2a35a5f6ae1c404ef2d503c2186f48fa7bf810cf151e62
... and then broken again https://github.com/thanos-io/thanos/commit/569a4d730e5f41ca949d1f973671743da482de47#diff-61d624f57144d877c035b5fe65277dff301be7e52707e37fa538ad8750ed5a75

I forgot to mark this as fixed in #4883. It's fixed. :)


process datasets

Processing ace dataset, running sh reports an error.

Why doesn't everyone have dataset related issues, is it well handled? I don't get it.


Flush pipeline when PMP CSRs are cleared

Closes: https://github.com/lowRISC/ibex/issues/2193

This is my suggested solution, but I think it's wrong: Doesn't this prevent the else case ever being entered? Indeed was the else case ever correct? It would previously not be entered e.g. on a WRITE to a debug register, which it clearly should be.
I think the if and else should be merged, and the inner if statements merged into their parents, something like the below:
assign csr_pipe_flush =
    csr_op_en_o == 1'b1 && csr_op_o != CSR_OP_READ && (
    	csr_num_e'(instr_rdata_i[31:20]) == CSR_MSTATUS   ||
     	csr_num_e'(instr_rdata_i[31:20]) == CSR_MIE       ||
      	csr_num_e'(instr_rdata_i[31:20]) == CSR_MSECCFG   ||
      	// To catch all PMPCFG/PMPADDR registers, get the shared top most 7 bits.
      	instr_rdata_i[31:25] == 7'h1D 		  	  ||
    	csr_num_e'(instr_rdata_i[31:20]) == CSR_DCSR      ||
	csr_num_e'(instr_rdata_i[31:20]) == CSR_DPC       ||
	csr_num_e'(instr_rdata_i[31:20]) == CSR_DSCRATCH0 ||
	csr_num_e'(instr_rdata_i[31:20]) == CSR_DSCRATCH1
    );

I also don't want to make any RTL changes to Ibex until I've sorted the OT earlgrey release branch

Closing this PR because it probably needs a different solution.


My sql app updates

Can someone accept this pull request so I can merge the changes that Ahub has made on the My SQL APP Updates branch into my testing branch to test the new development changes.

Thanks @AhubSajid for accepting the pull request


Moon Programs not giving advances

Raised by _Zee:

Having an issue with the Mun/Minmus Probe Strategies not actually giving an advance payment. I've tested with both Mun and Minmus, tried changing scenes several times, nothing seems to actually give the +100k or +75k advance payment. This is after confirming that the Contract spawned by Mun Probes is in my active list.

and confirmed by ibanix:

I can confirm this behavior. The 'Mun Program' did not give me the 100k advance when I took the strategy.

Fixed some problems in Contract Configurator 1.11.2 that should actually resolve this.


fix the problem of error at download the screenshot picture when there are some pics in messages history

之所以报错是因为 消息记录中的图片不属于私域中的图片 ，需要在toPNG之前 用一个后台接口转换为私域的图片地址，然后toPNG则不会报错可以正常下载   #3553
下面是 修复后的功能截图

lgtm, sadly I can't cherry pick commit this branch because bug still not fixed yet

lgtm

i think it is solved ... you can add gpt-4v model and test it ...it is solved ...
these  pic tells everythong

it we don't add the transferimg api and there's the pics in the chat history , toPNG method will go some error because the pic don't belong to this domain .
that's why we need to add the transferimg api

it we don't add the transferimg api and there's the pics in the chat history , toPNG method will go some error because the pic don't belong to this domain .
that's why we need to add the transferimg api

yeah because of cors issue, been known it

I cherry pick pr this to my fork
https://hackerchat.btz.sh/#/changelog

thanks a lot for your works, it's a good way to solve cross-domain problems, but it would lead to a ssrf


Cannot install node-sass version 3.1.2

I tried running $ npm install<EMAIL_ADDRESS>but I received this error:

<EMAIL_ADDRESS>install /Library/WebServer/Documents/plan-html/node_modules/node-sass
node scripts/install.js

Cannot download "https://github.com/sass/node-sass/releases/download/v3.1.2/darwin-x64-46_binding.node": HTTP error 404 Not Found

<EMAIL_ADDRESS>postinstall /Library/WebServer/Documents/plan-html/node_modules/node-sass
node scripts/build.js

Building: /usr/local/bin/node node_modules/pangyp/bin/node-gyp rebuild --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
module.js:340
throw err;
^
Error: Cannot find module '/Library/WebServer/Documents/plan-html/node_modules/node-sass/node_modules/pangyp/bin/node-gyp'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:289:25)
at Function.Module.runMain (module.js:467:10)
at startup (node.js:136:18)
at node.js:963:3
Build failed
OS: OS X 10.10.5
Node: 4.2.4
NPM: 3.5.2
It seems to be the github url to download is not working. Thanks for looking into it!

node-sass 3.1.2 is too old for node 4.x
Use the newest version of node-sass (3.4.2 currently).


[bug]: Popover does not close with the same button

What version of strapi-design-system are you using?
Npm version: 8.15.1
Node.js version: 20.11.1
Strapi Design System version: 1.14.1
Browser: Chrome
What's Wrong?
When you open a pop-up window with a button, it does not close on the second click (as it should be). I think this is due to the fact that both events are triggered: OnClick on the button, and onDismiss on the Popover. They change each other's states.
As you can see in this video, this bug is in Storybook Strapi. Also, when creating my plugin, I got the same error.
https://github.com/strapi/design-system/assets/53301242/0ba21fb4-a795-449c-8222-89d5da783b08
To Reproduce
This bug you can find the error in Storybook Strapi.
Expected Behaviour
Each time the button is clicked, the Popover must either open or close.

should be solved by a843b4cd


Don't delete node pools for imported clusters

Also fix examples for imported clusters.

To clarify this is more, don't delete node pools if nodepools field is not managed, correct?

Yes, that's correct.

@cmurphy can you add an issue to this PR

Issue: https://github.com/rancher/rancher/issues/32734


I need the HTTPS port to serve web content which is the sole reason for this sudden change.

Merged, thanks!


Error position doesn't have a value for anonymous code blocks

Description
It is expected that "Error position" will not be empty here.
It should be = 32 (line number where the executed statement starts) so that a user will find it easily.
You already show the line number on the inline code block correctly (it is 4 from the start of the block: "do $$...") and it is nice but not enough.
By the way, button "Go to the error" aware of the correct line number we need. So you don't need to obtain it somewhere: you already have it, just show it for a user.
This issue could be also related to #34734
DBeaver Version
Community Edition <IP_ADDRESS>407042322
Operating System
Windows 10
Database and driver
PostgreSQL 16
PostgreSQL JDBC Driver 42.7.2
Steps to reproduce
execute the code using Ctrl + Enter (place the code to the line 32, for example):
DO $$
BEGIN
 RAISE EXCEPTION '1111';
END $$;

Additional context
No response

Thank you fr bug report.

This is not only about anonymous code block but all queries.


Update sbt-scalajs-crossproject to 1.0.0

Updates org.portable-scala:sbt-scalajs-crossproject from 0.6.1 to 1.0.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.portable-scala", artifactId = "sbt-scalajs-crossproject" } ]

labels: sbt-plugin-update, semver-major

Codecov Report

Merging #370 into master will increase coverage by 0.37%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #370      +/-   ##
==========================================
+ Coverage   95.54%   95.92%   +0.37%
==========================================
  Files          15       15
  Lines         764      761       -3
  Branches       45       45
==========================================
  Hits          730      730
+ Misses         34       31       -3

Impacted Files
Coverage Δ

core/src/main/scala/io/iteratee/Enumerator.scala
97.05% <0%> (+2.09%)
:arrow_up:

Continue to review full report at Codecov.

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


Ignore tags not matching prefix, when workflow is pinned to SHAs

When updating explicit tags that include version numbers in their name in GitHub Actions workflows, we only update to tags that respect the existing format.
For example, if a workflow is pinned to the v2.3.6 tag through<EMAIL_ADDRESS>and the action's author tags codeql-bundle-v2.13.4, then RuboCop won't create updates.
However, when the workflow is pinned to the specific commit for that tag, for example like this github/codeql-action@83f0fe6c4988d98a455712a27f0255212bba9bd4 # v2.3.6, then Dependabot will still create an update to github/codeql-action/upload-sarif@cdcdbb579706841c47f7063dda365e292e5cad7a # v2.13.4.
This PR fixes the problem by ensuring the format is respected, not only for explicit tags, but also for the tags corresponding to explicit SHA pins.

Oops, I broke common CI apparently. Back to WIP.

I think it should be fixed now but I'd like to confirm that the smoke test failure is not related to this PR.


Add extension identifier with version to Equinix Metal client User-Agent headers

Add extension identifier with version to Equinix Metal client User-Agent headers
This aids Equinix in supporting clients and measuring adoption. The Consumer Token header is currently set as "gardener", the User Agent adds greater visibility. By incorporating the version number (which is already part of the LDFLAGS) the precise version will be known, making it easier to direct users to the best version.
Signed-off-by: Marques Johansson<EMAIL_ADDRESS>How to categorize this PR?

/area TODO
/kind TODO
/platform equinix-metal
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you @displague for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below.

/reviewed ok-to-test


[Transaction] Fix transaction buffer client handle endTxn op when topic or sub have been deleted.

Motivation
now, when topic have been deleted we will not handle the endTxnOnTopic and endTxnOnSub.
now, when sub have been deleted we will not handle the endTxnOnSub.
when topic or sub have been deleted, we should return success to tc on endTxnOnTopic and endTxnOnSub operation.
implement
when topic not exist in this broker, we should judge the topic if it have been created. if not created, we should return success.
Verifying this change
Add the tests for it
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes
Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Hi @eolivelli  @codelipenghui   please review again. thanks:)


port to 1.21.1

Describe your idea
would be nice to have a 1.21.1 port

https://modrinth.com/mod/defaultworldtype/version/1.21-5.0.0


Upgrade Rust version in CI setup

Right now we use 1.44.1 in .circleci/config.yml and .github/workflows/Basic.yml, which is unsupported by CosmWasm.

What is the latest version then?

The min Rust version is always documented in the CosmWasm CHANGELOG. For

CosmWasm 0.11 we require Rust >= 1.45.2,
CosmWasm 0.13 (unreleased) we requeste Rust >= 1.48.0

The CI testing should always happen on the lowest supported version.

Let's use 1.53 now in CI

Closed by #77.


chore(main): release 1.10.1

:robot: I have created a release beep boop
1.10.1 (2024-09-03)
Bug Fixes

validation color on dropdown (b2c2946)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.10.1
:sunflower:


[DS-3166] bin/make-handle-config script is broken

https://jira.duraspace.org/browse/DS-3166

+1 via code review

+1 by inspection


[Pager] Better pointer input handling

A usage is that using Pager inside a Pager, or using Pager in Scaffold with Drawer, both of these usages are buggy right now

There is not enough information in this bug.
I've just tried a VerticalPager { HoriztonalPager {} } and it works fine.

Here is a quick example, both inner and outer HorizontalPager is quite wired, but this use case might not be very useful.
val pagerState = rememberPagerState(pageCount = 10)
HorizontalPager(state = pagerState) { page1 ->
    val pagerState2 = rememberPagerState(pageCount = 2)
    HorizontalPager(state = pagerState2) { page2 ->
        Text(text = "$page1 $page2")
    }
}

Here is another example that can not drag the drawer out
Scaffold(
    drawerContent = {
        Column {
            ListItem {
                Text(text = "Drawer")
            }
        }
    }
) {
    val pagerState = rememberPagerState(pageCount = 10)
    HorizontalPager(state = pagerState) { page ->
        Text(
            modifier = Modifier.fillMaxSize(),
            text = page.toString()
        )
    }
}

I'm not surprised at all that a HorizontalPager inside of a HorizontalPager doesn't work very well. We're using scrollable() which should give us some automatic nested scrolling support, but actually making this work nicely is a very low priority.
Re: Drawer. This is sounds like https://issuetracker.google.com/167408603 which is a bug in drawer.


UHF-9159 subgroup

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

Comparison is base (42eed9b) 81.38% compared to head (c95e83a) 81.73%.

:exclamation: Current head c95e83a differs from pull request most recent head 37e2c11. Consider uploading reports for the commit 37e2c11 to get more accurate results

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #161      +/-   ##
============================================
+ Coverage     81.38%   81.73%   +0.34%
- Complexity      356      363       +7
============================================
  Files            49       50       +1
  Lines          2810     2863      +53
============================================
+ Hits           2287     2340      +53
  Misses          523      523

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


On MacOS: Illegal Instruction: 4 on CLImage2D test

Using npm 3.10.10 & node v7.2.1
When trying to get the tests working on MacOS Sierra, it seems that something has been precompiled with incompatible instruction sets:
Output from npm test:
  ...
    ✓ should return platforms and devices (42ms)

  CLImage2D
Illegal instruction: 4

Info about the Illegal instruction: 4 error on StackOverflow.
This happens when testing only CPU as well as GPU.
Doing a bit of debugging, it seems to be happening exactly at Line 58. But I'm not sure what to do about it, other than perhaps ensuring that whatever compiled code being used is very platform specific?

Bit more debugging this morning.
The script seems to be failing at the CLEvent.promise at Line 58 of imageTests.hs
Further tracing it down to failing exactly at Line 130 of clEvent.js which seems to be calling clSetEventCallback.  Something with it is causing the Illegal instruction: 4 error and throwing the program.
Let me know if I can try anything to debug.

Ok, that's could come from fastcall binary or from the OpenCL binary. Could you try to run unit tests of latest fastcall at your side? If that runs, then we're facing to an OpenCL driver problem. Maybe there are more driver binaries, and we're loading the wrong one or so.

I can't build the latest fastcall from scratch as per the issue I posted here: cmake-js/fastcall#11
But I can switch into NOOOCL/node_modules/fastcall and run npm install.
When I do this I get a few node-gyp warnings:
> node-gyp rebuild

gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
  CC(target) Release/obj.target/ffi/deps/libffi/src/prep_cif.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/types.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/raw_api.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/java_raw_api.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/closures.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/x86/ffi.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/x86/ffi64.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/x86/darwin.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/x86/darwin64.o
  LIBTOOL-STATIC Release/libffi.a
  CXX(target) Release/obj.target/ffi_bindings/src/ffi.o
../src/ffi.cc:111:11: warning: 'ForceSet' is deprecated [-Wdeprecated-declarations]
  target->ForceSet(Nan::New<String>("RTLD_NEXT").ToLocalChecked(), WrapPointer((char *)RTLD_NEXT), static_cast<PropertyAttribute>(ReadOnly | DontDelete));
          ^
/me/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: 'ForceSet' has been explicitly marked deprecated here
                bool ForceSet(Local<Value> key, Local<Value> value,
                     ^
../src/ffi.cc:114:11: warning: 'ForceSet' is deprecated [-Wdeprecated-declarations]
  target->ForceSet(Nan::New<String>("RTLD_DEFAULT").ToLocalChecked(), WrapPointer((char *)RTLD_DEFAULT), static_cast<PropertyAttribute>(ReadOnly | DontDelete));
          ^
/me/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: 'ForceSet' has been explicitly marked deprecated here
                bool ForceSet(Local<Value> key, Local<Value> value,
                     ^
../src/ffi.cc:117:11: warning: 'ForceSet' is deprecated [-Wdeprecated-declarations]
  target->ForceSet(Nan::New<String>("RTLD_SELF").ToLocalChecked(), WrapPointer((char *)RTLD_SELF), static_cast<PropertyAttribute>(ReadOnly|DontDelete));
          ^
/me/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: 'ForceSet' has been explicitly marked deprecated here
                bool ForceSet(Local<Value> key, Local<Value> value,
                     ^
../src/ffi.cc:120:11: warning: 'ForceSet' is deprecated [-Wdeprecated-declarations]
  target->ForceSet(Nan::New<String>("RTLD_MAIN_ONLY").ToLocalChecked(), WrapPointer((char *)RTLD_MAIN_ONLY), static_cast<PropertyAttribute>(ReadOnly|DontDelete));
          ^
/me/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: 'ForceSet' has been explicitly marked deprecated here
                bool ForceSet(Local<Value> key, Local<Value> value,
                     ^
../src/ffi.cc:123:11: warning: 'ForceSet' is deprecated [-Wdeprecated-declarations]
  target->ForceSet(Nan::New<String>("FFI_ARG_SIZE").ToLocalChecked(), Nan::New<Uint32>((uint32_t)sizeof(ffi_arg)), static_cast<PropertyAttribute>(ReadOnly|DontDelete));
          ^
/me/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: 'ForceSet' has been explicitly marked deprecated here
                bool ForceSet(Local<Value> key, Local<Value> value,
                     ^
../src/ffi.cc:124:11: warning: 'ForceSet' is deprecated [-Wdeprecated-declarations]
  target->ForceSet(Nan::New<String>("FFI_SARG_SIZE").ToLocalChecked(), Nan::New<Uint32>((uint32_t)sizeof(ffi_sarg)), static_cast<PropertyAttribute>(ReadOnly | DontDelete));
          ^
/me/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: 'ForceSet' has been explicitly marked deprecated here
                bool ForceSet(Local<Value> key, Local<Value> value,
                     ^
../src/ffi.cc:125:11: warning: 'ForceSet' is deprecated [-Wdeprecated-declarations]
  target->ForceSet(Nan::New<String>("FFI_TYPE_SIZE").ToLocalChecked(), Nan::New<Uint32>((uint32_t)sizeof(ffi_type)), static_cast<PropertyAttribute>(ReadOnly | DontDelete));
          ^
/me/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: 'ForceSet' has been explicitly marked deprecated here
                bool ForceSet(Local<Value> key, Local<Value> value,
                     ^
../src/ffi.cc:126:11: warning: 'ForceSet' is deprecated [-Wdeprecated-declarations]
  target->ForceSet(Nan::New<String>("FFI_CIF_SIZE").ToLocalChecked(), Nan::New<Uint32>((uint32_t)sizeof(ffi_cif)), static_cast<PropertyAttribute>(ReadOnly | DontDelete));
          ^
/me/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: 'ForceSet' has been explicitly marked deprecated here
                bool ForceSet(Local<Value> key, Local<Value> value,
                     ^
../src/ffi.cc:132:11: warning: 'ForceSet' is deprecated [-Wdeprecated-declarations]
  target->ForceSet(Nan::New<String>("HAS_OBJC").ToLocalChecked(), Nan::New<Boolean>(hasObjc), static_cast<PropertyAttribute>(ReadOnly | DontDelete));
          ^
/me/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: 'ForceSet' has been explicitly marked deprecated here
                bool ForceSet(Local<Value> key, Local<Value> value,
                     ^
9 warnings generated.
  CXX(target) Release/obj.target/ffi_bindings/src/callback_info.o
  CXX(target) Release/obj.target/ffi_bindings/src/threaded_callback_invokation.o
  SOLINK_MODULE(target) Release/ffi_bindings.node
clang: warning: libstdc++ is deprecated; move to libc++ with a minimum deployment target of OS X 10.9
ld: warning: could not create compact unwind for _ffi_call_unix64: does not use RBP or RSP based frame

But it seems to build okay. I run npm test and all 97 tests pass.

fastcall has nothing to do with node-gyp actually, it's based on CMake.js. Only the developer mode build uses node-gyp to build ffi and ref just for the benchmarks. I've added instructions there.
But, since you did run fastcall tests, and there wasn't any problem on your rig, we have a driver issue there. Which is very unfortunate, because I really cannot do anything to help. You get illegal instruction because OpenCL driver is compiled with SSE4 or AVX instruction set, and your hardware doesn't support it. Maybe there is a driver update available or something, I don't know Macs. Maybe there is another OpenCL binary in your system directory that should be loaded instead of that one from your latest PR?

I can reproduce this on a Mac with AMD GPU. However in my case even the CLBuffer get stuck at the first phase. If I switch from GPU to CPU CLBuffer tests pass, but I get "Illegal instuction: 4".

It looks like, the default device is an Intel one on the Mac that I have access to, so it is an Intel driver issue definitely. @arjunmehta Do you have clinfo? Is it same like https://github.com/unbornchikken/NOOOCL/issues/18?

Yes same output from clinfo on my Late 2013 13" Macbook Pro

I've dug myself into articles about this issue, and I believe this is really originated from fastcall. It uses "-march=native" which could cause issues on older Macs. I think if I add a unit test to fastcall which uses the same argument scheme like OpenCL event callback, it will crash with Illegal instruction. Or there might be issues about the callback which might get garbage collected on Mac before the callback really happens, this could lead to an Illegal instruction. Or there might be issues with the assembler arguments, those are kinda special case on Mac.
So I have some suspects, but I don't have access to a Mac until next week.

If you want, You can use Travis.
Set up a branch and configure for OS X. My PR for NOOOCL should give you an idea to get started with your config but let me know if you have any questions!

Ok, I managed to debug that, and unfortunately it's from the OpenCL driver. The crash originated from the driver's uint8_rgba.dylib. It throws by executing ud2 instruction in a macro called: __illegal_sampler_mode__integer_coords_must_use_nearest_filter_mode.� Dunno why, but thats the problem. Gotta look into it.

Intel driver doesn't understand linear interpolation when using integer coordinates. Dunno why, it should work by that way, and of course works on all other platfroms.
The issue fixed as of v0.12.4, all test should pass with Intel drivers.

Nice! It seems to be working/passing the tests. Great job!


ADS-sum commands?

Is there a possibility to do sum commands? See: https://infosys.beckhoff.com/english.php?content=../content/1033/tcsample_vc/html/tcadsdll_api_cpp_sample17.htm&id

At the moment sum-commands are not supported for pyads. However, this seems to be a nice feature. You are very welcome to elaborate on it.

Thanks again @bdcoyle for implementing this feature.


HW Node lacking i915 capabilities

After upgrading to 23.10-standard-amd64-generic-v2.5.0-k3sv1.29.0-k3s1 it seems hw accel capabilities have stopped working where they previously worked.
This is preventing the plex deployment from succeeding as it requires a node with gpu.intel.com/i915: "1" which is automatically applied to nodes with the intel-gpu-device-plugin.
Relevant alert:
[FIRING:1] Pod has been in a non-ready state for more than 15 minutes.
Alert: warning
Summary: Pod has been in a non-ready state for more than 15 minutes.

Details:
• alertname: KubePodNotReady
• namespace: media
• pod: plex-645cf67c5d-kf975
• prometheus: monitoring/kube-prometheus-stack-prometheus
• severity: warning

Attempted:

Create a configuration on the node with the following:

stages:
  boot:
    - name: "i915 setup"
      commands:
        - modprobe i915
name: "i915 setup"

Does not work, unsure on the execution of this file or if it even does
To try:

Push the above config in a SUC plan


Feat/routing

Proposed changes
Improves handler routing implementation.
Fixes
n/a
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[x] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING doc
[x] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes

Codecov Report

:exclamation: No coverage uploaded for pull request base (staging@dafe4c3). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             staging      #64   +/-   ##
==========================================
  Coverage           ?   95.53%
==========================================
  Files              ?       23
  Lines              ?     1299
  Branches           ?        0
==========================================
  Hits               ?     1241
  Misses             ?       58
  Partials           ?        0

Flag
Coverage Δ

unittests
95.53% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


"Error Message: fatal: not a git repository (or any of the parent directories): .git" while deploying to azure

I am unable to deploy my Angular app to Azure . I have the error below
Action: appService.Deploy
Error type: Error
Error Message: fatal: not a git repository (or any of the parent directories): .git

@Yatenga did you change your deployment source to "Local Git"? If so, you can either change it back to the default ("None"), or initialize a git repo for your project


Try to detect system JDK/JRE home

... instead of ~/.jenv/versions/system, at least on Debian/Ubuntu systems (see #103 and #123 ).
Let jenv to play nicely with Debian alternatives system. My use case (Debian 8.3):
$ sudo update-java-alternatives -l
java-1.7.0-openjdk-amd64 1071 /usr/lib/jvm/java-1.7.0-openjdk-amd64
java-1.8.0-openjdk-amd64 1069 /usr/lib/jvm/java-1.8.0-openjdk-amd64

$ jenv versions
* system (set by /home/lorenzo/.jenv/version)
  1.7
  <IP_ADDRESS>
  1.8
  <IP_ADDRESS>-internal
  openjdk64-<IP_ADDRESS>
  openjdk64-<IP_ADDRESS>-internal

$ java -version
java version "1.7.0_95"
OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb8u1)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)

$ jenv javahome
/usr/lib/jvm/java-7-openjdk-amd64

$ sudo update-java-alternatives -s java-1.8.0-openjdk-amd64
[... plugin alternative errors, not relevant here ...]

$ java -version
openjdk version "1.8.0_72-internal"
OpenJDK Runtime Environment (build 1.8.0_72-internal-b15)
OpenJDK 64-Bit Server VM (build 25.72-b15, mixed mode)

$ jenv javahome
/usr/lib/jvm/java-8-openjdk-amd64

Unfortunately, readlink -f  does not work on OSX.
But It seems that greadlink from coreutils could be an alternative for osx.

@gcuisinier thank you for the advice, I picked the function resolve_link to choose between greadlink and readlink, already used in other commands.


RFC for ImageQA Plugin

The issue
Our colleague, Rada, does sensitivity checking on each archival item we digitize. To sensitivity check, she needs to view every single image in an item, have full-screen views of the image, and be able to zoom into the image easily.
Prior to the migration she was downloading the images via the home directory folder and viewing the items in Adobe Bridge. With the migration to the Cloud, this is no longer a possibility.
Her chief complaints about using Edit METS to view the images are:

The image is too small
The images (jpgs) are too slow to load, taking 1-3 seconds to load depending

Possible resolution
To resolve the images being too small, we could add the ImageQA plugin to the existing JP2_manual_edit_METS workflow (or a new one the replicates that workflow) before the Edit METS step.
For the jpegs being too slow to load, we could test them on the ImageQA plugin to see if they are faster to switch between and if not, consider other solutions to this.
Questions

Is it possible to get a test version of the ImageQA plugin on staging Goobi to test if this is a good solution for Rada?
How much dev work will be needed to make the ImageQA plugin work in the Cloud?

We sped up the image loading in imageQA. This needs to be deployed to production.

Having talked to Rada, I have clarified her needs.
For items she knows could be sensitive and they need a longer look or for items that are handwritten, she needs the full screen view. The full screen view size and speed is good for her but is it possible to disable the fade in when the jpegs load? It is hard to look at when going at speed.
For items that are at low risk for being sensitive, she still needs to look over them but at speed. For this she would prefer having larger thumbnails. The thumbnails in the plugin is just too small still for a quick go-over.
She is willing to sacrifice the size of the preview pane on the right-hand side of the screen for larger thumbnails as she can always use the full screen mode.
When I talked to her, she said something perhaps this size might work:

We removed the large image on the right and now everything looks good. Closing this.


Panic VFS after update

Using stock NOOBS
Boot into Raspbian.
Run sudo rpi-udapte
Updates successfully and says reboot.
Reboot.
Message "PANIC: VFS: Unable to mount root fs on unknown-lock(179,2)
This is the 2nd SD card I have tried.
Using very good power supply with thick DC cables. Only ethernet and keyboard plugged in.
It also "kills" NOOBS. Can't hold shift to get into NOOBS anymore. Straight into Raspbian boot then panic.
Almost like NOOBS has been corrupted by the rpi-update

Have posted an issue on RPI firmware with more details here:
https://github.com/raspberrypi/firmware/issues/398

Duplicate of raspberrypi/firmware#398


Finding cells to refine may be inefficient

In #361, the line
# The "Ref(...)" is such that we can vectorize the search but not the array that is searched
elements_to_refine = searchsortedfirst.(Ref(cache.elements.cell_ids[1:nelements(dg, cache)]),
                                        cells_to_refine)

was replaced by
# Find all indices of elements whose cell ids are in cells_to_refine
elements_to_refine = findall(cell_id -> cell_id in cells_to_refine, cache.elements.cell_ids)

While the latter is more readable and works if cell_ids is smaller than cells_to_refine (which is important for MPI, see this comment), the former utilizes the fact that cell_ids is sorted.
As discussed with @sloede, this is currently not relevant for performance, but in case it eventually becomes relevant, this issue could help us identify the problem.

There is a function insorted determining whether something is contained in a sorted collection in Julia v1.6.

There is a function insorted determining whether something is contained in a sorted collection in Julia v1.6.

Thanks, that sounds like a good way to solve this easily. Will we wait for the release or will we use the beta for some features like we did with 1.5?

Thanks, that sounds like a good way to solve this easily. Will we wait for the release or will we use the beta for some features like we did with 1.5?

It would be okay for me to implement and test something now using the pre-release of v1.6. However, I would suggest to wait until v1.6 is released officially before merging such PRs.

It would be okay for me to implement and test something now using the pre-release of v1.6. However, I would suggest to wait until v1.6 is released officially before merging such PRs.

I would wait then until 1.6 is released, since this seems like a small and quickly implemented change to me.

I would wait then until 1.6 is released, since this seems like a small and quickly implemented change to me.


com.gargoylesoftware.htmlunit.ScriptException: Error: Bootstrap's JavaScript requires jQuery version 1.9.1 or higher

I am trying to browse http://taxtest.navajocountyaz.gov/Pages/WebForm1.aspx?p=1&apn=10301003B using Java code and the latest release of HTMLUnit (version 2.37.0, which I downloaded from https://jar-download.com/artifact-search/htmlunit along with all its dependencies).
final WebClient webClient = new WebClient();
webClient.getOptions().setThrowExceptionOnScriptError(false);
webClient.setRefreshHandler(new RefreshHandler() {
	public void handleRefresh(Page page, URL url, int arg) throws IOException {
	    System.out.println("handleRefresh");
	}
});
HtmlPage page = (HtmlPage) webClient.getPage("http://taxtest.navajocountyaz.gov/Pages/WebForm1.aspx?p=1&apn=10301003B");

The last line of code throws the following exception:
com.gargoylesoftware.htmlunit.ScriptException: Error: Bootstrap's JavaScript requires jQuery version 1.9.1 or higher (http://taxtest.navajocountyaz.gov/js/bootstrap.js#15)
I thought the problem was with my code. So, I sought help at https://stackoverflow.com/questions/60030255/com-gargoylesoftware-htmlunit-scriptexception-error-bootstraps-javascript-req and, according to RBRi, it "Looks like a problem inside HtmlUnit itself."
Please fix the problem in an upcoming release of HTMLUnit. In the meantime, I would appreciate a workaround for my code, including, if possible, which older release of HTMLUnit I need to revert back to avoid the problem.
Thank you.

I don't think that it's htmlunit issue: I opened this page in Firefox and it shows the same error. The page loads jquery 1.7.1 while bootstrap requires >= 1.9.1 and that's why it complains.

Firefox may well show the same error. But, when I open the http://taxtest.navajocountyaz.gov/Pages/WebForm1.aspx?p=1&apn=10301003B page with Firefox, I am able to see the dollar figures under "Cash Value". With HTMLUnit, I am not able to extract such values. So, for this page, HTMLUnit is not performing as well as Firefox. I would like for there to be a way in HTMLUnit to extract those dollar figures from the web page, regardless of the existence of the jQuery error.

Have done a quick test
    String uri = "http://taxtest.navajocountyaz.gov/Pages/WebForm1.aspx?p=1&apn=10301003B";

    try (final WebClient webClient = new WebClient(BrowserVersion.FIREFOX_68)) {
        webClient.getOptions().setThrowExceptionOnScriptError(false);

        HtmlPage page = webClient.getPage(uri);

        System.out.println(page.asText());
    }

Looks like everything is there. Can you please check and provide more details about the missing content.

I just tried your code, and I am getting the same exception at the
    HtmlPage page = webClient.getPage(uri);

line of code.
Maybe the problem is with the HTMLUnit+Dependencies that I downloaded from  https://jar-download.com/artifact-search/htmlunit  . Maybe the maintainer of jar-download.com got some version(s) of the dependencies wrong.
Could you download HTMLUnit+Dependencies from https://jar-download.com/artifact-search/htmlunit , try your code with it, and see whether it still works ?
I know I can also download HTMLUnit from the official site. I used to do that. But then it used to take me forever to track down all the dependencies and the dependencies of the dependencies. So, I would appreciate if you could first try the above hypothesis to see whether or not the problem is with the jar-download.com site. Then, if it is, I will download HTMLUnit from its official site.

You are sure the code throws the exception? I guess the exception is only in the logs but the code produces some output here.
Regarding the download - htmlunit-2.37.0-bin.zip from the official download location contains all you need (including all dependent libs). Do you miss something in this package?

BTW if you like to ignore the js errors you can use
webClient.setJavaScriptErrorListener(new SilentJavaScriptErrorListener());

The following import statement:
    import com.gargoylesoftware.htmlunit.javascript.*;

and adding the following code
    webClient.setJavaScriptErrorListener(new SilentJavaScriptErrorListener());

did fix the problem.
Thank you very much rbri for your help. I am going to close this issue.

Thanks for the feedback.


Create a ssh key, and reading from a file by selecting a large file may cause the page to jam

Steps to reproduce:

On the ssh key create page
Click Read From Filebutton and upload a large file. (Tested by uploading a dmg file)

Result:
By uploading a large file could cause the page to jam
Suggestion:
Add some restrictions, like only allow users to upload txt, yaml and yml this kinds of files

this is a public key so using .pub file extention check would make sense.

Now all kinds of files are still able to be uploaded, reading from a file by selecting a large file could cause the page to jam. @DaiYuzeng

We lost a few commits at the first merge for upstream, probably this fix was one of them  :-|

Validated


Feature Request: apply a default profile when no profile is set for a folder/project

Is there a way to set a "global profile" that is the default? I'd like to have the ability to create a default profile so that when I open a folder in VS Code this default profile is what loads. But when I want to change it to a typescript profile, or a python profile, etc., then I can select a different profile for that folder.

Hi Just wanted to follow up on this and ask if anyone has ideas on how I can customize this for myself? The problem this would solve for me is that my work computer syncs with OneDrive by default so it gets really slow if too many extensions are activated. What I wanted is to have the default profile be based on a VS Code setting. If i select a specific profile as my default, then it will load that profile. Otherwise, maybe I can put a settings.json file in my .vscode folder? Ideas?

Checking again to see if anyone is interested in helping me flesh this feature out. If you don't have time to develop it, I can give it a shot. Did @drod3763 or @jlongo ever flesh outhe "Global" profile idea that they requested? I think my idea is similar.


feat: new plan a lesson page - LESQ-783 LESQ-785

Description
Music year: 1956

Grid layout for new plan a lesson page
Basic cms schema template
Basic page tests
Breadcrumb ticket included in this PR

Issue(s)
Fixes #
How to test

Go to https://deploy-preview-2402--oak-web-application.netlify.thenational.academy/lesson-planning-new

should be content ="noindex,nofollow"
should be a basic responsive layout

Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner
[ ] Does this PR update a package with a breaking change

@jack-skerrett-oak This is just a placeholder that will be replaced with a component so I don't think it's worth making this change.

@jack-skerrett-oak This is just a placeholder that will be replaced with a component so I don't think it's worth making this change.

@JBR90 You'll be the one on my hit list if that component comes back with a h3!
😬

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


Add alone by alan walker

Song Name
alone
Artist Name
alan walker
Source
Youtube
Youtube Link
gOnMXUDrFTLxhuA9
Direct File Link
No response
Song ID
4
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 106668516

reject
invalid YouTube link