https certificate net::ERR_CERT_COMMON_NAME_INVALID on gcping.com

TL;DR: https error on https://gcping.com.  Cert common name says it's for "*.storage.googleapis.com" instead of "gcping.com" or "www.gcping.com"
Hi!
First off, thanks for the useful site!  It's great to see things like this popping up.  🙂
I noticed that the certificate that the ssl certificate for gcping.com doesn't match the domain name (specifically Chrome saying "net::ERR_CERT_COMMON_NAME_INVALID).
Steps to repro:

Navigate to https://www.gcping.com/

Expected outcome:
2. SSL certificate common name matches and the site appears like magic over ssl
Actual outcome:
2. Notice the error page Chrome serves up
3. Inspect the certificate to notice "*.storage.googleapis.com" as the common name instead of "gcping.com"
Suggested fix:
Ok, I'm going to be making some guesses based on what I see, so please feel free to correct me or ignore me.
A) It looks like you're serving directly from a gStorage bucket (via this https://cloud.google.com/storage/docs/hosting-static-website ?), so I suggest running it through a load balancer following this: https://cloud.google.com/load-balancing/docs/https/adding-a-backend-bucket-to-content-based-load-balancing (and adding ssl on your way through)
B) If, instead, you already have a load balancer on the front end (something like this? https://cloud.google.com/load-balancing/docs/https/adding-a-backend-bucket-to-content-based-load-balancing), I'd suggest adding a custom ssl certificate by following the ssl parts of this guide: https://cloud.google.com/load-balancing/docs/https/content-based-example#configuring_the_load_balancing_service
Remarks
Again, this is a lot of guessing based on what I'm seeing and I could be completely wrong in my "Suggested fix" section.  Let me know if I can help in any way!

Thanks for the report!
Yeah, HTTPS is just borked in general (see #22 for more info). The site is currently served through GCS but it doesn't have any HTTPS LB in front -- if it did, the HTTP(non-S) requests it makes to ping backends would be flagged as insecure content, and rightly so.

Fixed by https://github.com/ImJasonH/gcping/issues/29


Vue.volar crashes on startup after update 2.0.

The old version has been uninstalled.
JavaScript and TypeScript language features are enabled.

But as long as you downgrade back to version 1.8.27 there will be no problems. pls help!

Same issue here. Vue 3 Repo on M2 Pro.
Reverting to v1.8.27 working fine, But v2.0.0 to v2.0.4 crashes for me
Output:
SyntaxError: Unexpected end of JSON input
at JSON.parse ()
at Socket. (/Users/shahadat/.vscode/extensions/vue.volar-2.0.4/dist/server.js:10024:9777)
at Socket.emit (node:events:526:35)
at endReadableNT (node:internal/streams/readable:1359:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Node.js v18.17.1
[Error - 11:46:02] Server process exited with code 1.
[Info - 11:46:02] Connection to server got closed. Server will restart.
Device:
Version: 1.87.0 (Universal)
Commit: 019f4d1419fbc8219a181fab7892ebccf7ee29a2
Date: 2024-02-27T23:42:56.944Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.2.0

Same issuse. Is there any way to work around?

Duplicate of #3962?

Duplicate of #3962


Won't be able to work with BootloaderSpoofer?

Describe the bug
https://github.com/chiteroman/BootloaderSpoofer
After applied this to momo & hunter, zygisk will be detected.
Steps To Reproduce

Install momo/huter, enable Zygisk-Assistant, reboot
Open BootloaderSpoofer, select momo/huter app.
Open momo & hunter, you will see results.

Detection apk files:
Detect.zip
Context

Device: Xiaomi cas
OS: Android 13
Version of Magisk, KSU or APatch: Apatch 10763
Other Root Module(s): Zygisk-Next-1.0.5, LSPosed-v1.9.3_mod-7244-zygisk
LSPosed Module(s): None

Well, if you inject an Xposed module to an app, it will be able to detect that. There's not much we can do about that as the injected modules will reside in the address space of the target app.

Well, if you inject an Xposed module to an app, it will be able to detect that. There's not much we can do about that as the injected modules will reside in the address space of the target app.

You are right, however Shamiko is able to hide it from Momo, where Zygisk Assistant fails. I am unsure if that's the case for the OP though, but it is for me.
Should I open a new issue or only send a logcat here?

Well, if you inject an Xposed module to an app, it will be able to detect that. There's not much we can do about that as the injected modules will reside in the address space of the target app.

You are right, however Shamiko is able to hide it from Momo, where Zygisk Assistant fails. I am unsure if that's the case for the OP though, but it is for me.
Should I open a new issue or only send a logcat here?

No. Momo has outdated detection methods. Injected Xposed modules are always detectable even with Shamiko.

That is a rather controversial statement, as Momo is still one of the best apps to detect rooting.
Even if we agree with "it outdated detection methods", it would still be neat to patch those detection methods, don't you agree?


Dialog params

Hey. The documentation is written
const dialog = await this.$dialog.show(MyDialog, params, options)
But I do not understand how these parameters and options look? Can you set an example? I want for example, that the width of the window is 600px.

Sorry.
It's params vuetify. Please, close topic=)
const dialog = await this.$dialog.show(EditForm, {
                    width: 900,
                    scrollable: true
                });

Hello, @nayils!
Yes, you are right. You can set to second param all options and props of component

Third param is not use now, I will change documentation

For those who stumbled upon here and wondering "How do I pass props to the component in this.$dialog.show call", here's how:
this.$dialog.show(YourComponent, {
  somePropName: 'lorem',
  someOtherProp: '...',
})

It might not be the best place to write the above, but the comments above helped in finding this solution which doesn't seem to be in the docs.


Enforce reusable GHA naming convention

Need a GHA to enforce that anyone adding a reusable GHA should have it prefixed with reusable_ this is needed because of a limitation of GHAs where composite actions can live in their own repo (and that should be enforced as well), but reusable workflows have to live in the same repo as other workflows. This is very confusing for people so this naming convention will help people differentiate between what is a local workflow vs a reusable one.

As part of this, I think that it would be good to have a bool input option for all reusable actions to enable them or not. That way we can sync all of them across all repos and allow repos owners to enable/disable each of the reusable workflows via a config.


The v9.1.0 does not contain the latest code for the main branch

The #280 pull quest resolved some compatibility issues and merged into the main branch two months ago. For example:

The main branch lib/util/url.js file line 3:

let isWindows = /^win/.test(globalThis.process?.platform),

However, the npm package v9.1.0 released on 16 days ago is not the same as above.

The v9.1.0 verison lib/util/url.js file line 3:

let isWindows = /^win/.test(process.platform),

So, please help to release a new version of the latest code on the main branch.

v9.1.0 has appeared by magic and gummed up the works as semantic release now cannot release its own v9.1.0 which would have the changes. Trying to figure out wtf is to be done here but I do not want to be spending any time on this project anymore after begging for help for over a year.

Ideas on the back of a postcard.

@sesam semantic release has been weird and broken since before that change, but everything seems to be ticking along fine now thanks to new maintain @jonluca fixing it up. Use 9.1.2.


Any reason to make parser methods private?

A bit of background (if you are wondering why I've suddenly shown up and made a bunch of pull requests :) ):
I'm a dev on the Horde project.  We finally got fed up with our csstidy parser module and decided to look for code that could actually parse CSS3, and do it in a coherent fashion (i.e. stateful parsing, not preg crap).  Found this project and am happy.  We are going to package the parser in a PEAR package to be able to be used in our framework (i.e. autoloading is setup, etc.).
As such, one of the things I would like to see is stream support instead of reading all data into memory.  We use streams all over the place to reduce memory usage - since we have installations that have millions of users, we need to cut down memory usage as much as possible.
One way to do that is to open CSS files with fopen() and then pass the stream resource to the CSS parser instead of reading the whole file into memory (which can be 200KB+ of data).  I would then write a local Horde wrapper which extends Parser to overwrite the strlen, substr (and new strpos method I just added a pull request for) to access the stream instead of making them string operations.
However, with those methods being marked as private, there is no way to do that.  As a project, we mark everything as protected for precisely this reason - so end users can extend our classes as they see fit.
Any chance of making this change upstream?  Appreciate the requests you've already processed from me - it would be great to keep our copy as pristine as possible in order to be able to update from the main source as needed, thus the reason for the request.

I've submitted a PR for the private visibility. That was bringing me down, too!


[Bug] Image rendering via grafana API doesn't work

Describe the bug
Grafana has an API and there is a method to get rendered picture with request like:
https://my.grafana.address.com/render/d-solo/board_id/_?from=1596585600000&height=500&panelId=26&theme=light&to=1596671999000&width=1000
It works well with any panel type, except boom table panel. With Boom table panel we are getting 504 Gateway Time-out instead of picture.  Checked several times changing panel type
Version Details:

Grafana version : 6.6.0
Plugin version : 1.3.0

Duplicate of #18 .
If you still get the error with latest version, share more details about the error.


OKD 4.5:  scaled machineset down, scaled machineset up:  machine does not have valid node reference

Describe the bug
Scaling up machineset does not work in AWS, as server is provisioned in AWS, but not created as node.
oc get machines foo-worker-us-west-2a-vp27j
NAME                                 PHASE         TYPE         REGION      ZONE         AGE
foo-worker-us-west-2a-vp27j   Provisioned   i3.4xlarge   us-west-2   us-west-2a   6h3m
oc get machineset foo-worker-us-west-2a
NAME                           DESIRED   CURRENT   READY   AVAILABLE   AGE
foo-worker-us-west-2a   1         1                             20d
Error received:
machine foo-worker-us-west-2a-vp27j does not have valid node reference
Rational for scaling down / scaling up
Modified machineset adding this and wanted to test and have nodes reflect new label:
spec:
  metadata:
    labels:
      key: value

scaled machineset down
scaled machineset up
server was provisioned in AWS
MachineWithoutValidNode:  machine NAME_HERE does not have valid node reference

Version
oc version
Client Version: 4.5.0-0.okd-2020-07-14-153706-ga
Server Version: 4.5.0-0.okd-2020-07-14-153706-ga
Kubernetes Version: v1.18.3
How reproducible
100%:  I have reverted and tried with original machineset and now with the changes.
Log bundle
It is 2.8GB -- but I can provide any / all information as requested.

In AWS for the console of the provisioned system I am seeing the following:
[   19.002005] ignition[602]: GET result: OK
[   19.007708] systemd[1]: ignition-fetch.service: Main process exited, code=exited, status=1/FAILURE
[   19.019026] ignition[602]: failed to fetch config: unsupported config version
status ignition-fetch.service' for details.
[   19.025982] systemd[1]: ignition-fetch.service: Failed with result 'exit-code'.
[0;1;38;5;185mDEPEND [0m] Dependency failed for  [0;1;39mIgnition Complete [0m.
[[   19.036578] ignition[602]: failed to acquire config: unsupported config version

[ 19.019026] ignition[602]: failed to fetch config: unsupported config version

Which AMI is this machineset using?

NOTE:  When this issue was opened (2020/07/28) I was running 4.5.0-0.okd-2020-07-14-153706-ga.  I scaled down the machineset and upgraded cluster to 4.5.0-0.okd-2020-07-29-070316 to attempt to remediate.
However, that did not help.
To answer your question -- here is the answer
  providerSpec:
    value:
      ami:
        id: ami-03cbca3622d708c92

Oh, hmm, that would mean nothing, as OKD clones the initial image, not using it as it.
Could you try replacing this with AMI from official site and attempting the scaling again?

oc scale --replicas=0 machineset CLUSTER_NAME-worker-us-west-2a -n openshift-machine-api
Modifying to us-west-2 ami-0f2c8d6558d08dd83 as the follows
  providerSpec:
    value:
      ami:
        id: ami-0f2c8d6558d08dd83

As extracted from this command's output:
oc get machineset CLUSTER_NAME-worker-us-west-2a -o yaml
oc scale --replicas=1 machineset CLUSTER_NAME-worker-us-west-2a -n openshift-machine-api
Will report results as soon as known....

oc get node --selector=node-role.kubernetes.io/worker=
NAME                                          STATUS   ROLES    AGE   VERSION
ip-FOO.us-west-2.compute.internal   Ready    worker   92s   v1.18.3
o.k. that worked  -- I can scale a node.
Is this something that I need to change for all machine-sets I have as none scale?
Is this a bug somewhere or why did the AMI's not automatically get changed?
Did I miss something?
Please let me know.
Thank you.

Is this something that I need to change for all machinesets I have as none scale?

Yes.

Is this a bug somewhere or why did the AMI's not automatically get changed?

AMIs don't need to change, the OS would autoupdate itself from an older image.
The question is why AMI in machineset has been incorrect - could you collect more info about ami-03cbca3622d708c92?

I have 4 machineset defined and all 4 had referenced ami-03cbca3622d708c92.  This was as created from a vanilla openshift-install.

How could have I determined that the AMI was not available or the incorrect version?  I could find no indication what was wrong.  Is there a oc events or oc logs that I could have referenced to determine this issue?

This was as created from a vanilla openshift-install.

That's very odd. Are master machines running from this AMI? Was it a clean GA or you did upgrade to GA later?

This was upgraded from previous version. Here are the completed cluster upgrade versions:
4.5.0-0.okd-2020-07-29-070316
4.5.0-0.okd-2020-07-14-153706-ga
4.5.0-0.okd-2020-06-29-110348-beta6
4.4.0-0.okd-2020-05-23-055148-beta5
Information captured from:  oc get clusterversion -o json|jq ".items[0].status.history"

I checked all 3 masters and they all have the following ami:  ami-03cbca3622d708c92
Information captured from:  oc get machine CLUSTER_NAME-master-[012] -o yaml | grep -i ami
I am not sure the mechanism / procedure to change the master machine AMI as there is no machineset in openshift-machine-api project for master.
Is there a similar procedure to change the master AMI to ami-0f2c8d6558d08dd83 as was done for the worker nodes?
Is that recommended?
Is there any additional information I can provide to determine what occurred?

Ooh, that explains it. beta5 image is using Ignition 3.0 and won't accept Ignition 3.1, served by machine-config-server on GA.
Masters are not controlled by MachineSets, so these can't be scaled just yet - its not necessary to replace amiID there.
Seems this would affect only pre-beta5 updated clusters - and the workaround would be specifying amiID in the worker MachineSet once.

o.k.  Thank you for the explanation and the quick responses.
SYNOPSIS:  The 2 clusters I have -- the worker machinesets have been modified with the new AMI and scaled down and scaled backup referencing the AMI specified.  All is well
Thank you again.

This issue (bootimages get outdated after multiple updates) would be addressed in https://github.com/openshift/enhancements/pull/201


Add smbFlexVolInstaller.enabled to helm chart to disable daemonset deployment

What type of PR is this?
/kind feature
What this PR does / why we need it:
Adds a new value to the smb-flexvol helm chart: smbFlexVolInstaller.enabled, which permits deploying the chart WITHOUT deploying a Kubernetes DaemonSet. All other aspects of the chart (PV, PVC, test deployment) already have an enabled field, so this matches them.
Its useful for deploying further SMB volumes without having duplicate DaemonSets installed on cluster nodes.

thanks for the contribution.
BTW, there is a new SMB CSI driver, which is beta now, would you try that driver? https://github.com/kubernetes-csi/csi-driver-smb
Flexvolume driver will be only in maintenance mode.


No reply

Hi there,
I'm not receiving any reply from the bot. is there any tip that you can share in order to make it work ?
I've set up the bot and everything is correct but I cannot receive the echo reply.
Thank you.

Hi, I Had the same problem.
And I did this to work.
curl -X POST "https://graph.facebook.com/v2.6/me/subscribed_apps?access_token=<PAGE_ACCESS_TOKEN>"

Everything works fine for me. Did you forget to pass the access token to the variable "var" in index.js? Have a look on line 50.

Hi @pas2al, I'm not getting any responses either: my token was defined wrong but I fixed it and it's still no good

Hm, there has to be some misconfiguration. Create a facebook app and a facebook page. Edit these configuration like in the README. Everything works fine for me, i tried it just a minute ago.

every step by step seem fine for me! but  i can't find where is my chatbot. I don't see my chatbot in Facebook page. Help me fix it. Thanks so much..

Hm. Every steps seem fine for me, but I can not receive any reply from chatbot. Please help me!

Thanks for all. I can do it. Chatbot is working. Feel so happy.


Missing Database Templates

Hi, The Database Template only has an AI one for Retail recommendations. I've checked in 2x synapse workspaces in different Azure Tenants & I can't see it in either. I'm looking for the "Energy & Commodity Trading" one. Have they been moved somewhere else?
Thanks

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

ID: f11b1ecf-be34-eb9b-a496-1d6d0e2926ce
Version Independent ID: 553a3db4-3b66-2ea2-3c59-147992a8cd4a
Content: Overview of Azure Synapse database templates - Azure Synapse Analytics
Content Source: articles/synapse-analytics/database-designer/overview-database-templates.md
Service: synapse-analytics
Sub-service: database-editor
GitHub Login: @gsaurer
Microsoft Alias: gesaur

@dgray1k
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Resolved. Needed to add my client ip to the synapse firewall.
Rather odd that
a) didn't get the usual message when accessing synapse studio from a non-allowed IP
b) I could see the 1x retail AI template and not the others


wip: new(falco): add append_output configuration option with fields and format

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area engine

What this PR does / why we need it:
This addresses the need for a configuration option that allows to specify:

Additional output at the end of the regular message
Additional output fields, only visible in the json message, which can contain any custom message including formatted fields. Supports outputting strings with format and environment variables.

This is how it works
append_output:
  - source: syscall
    tag: persistence
    rule: some rule name
    format: "gparent=%proc.aname[2] ggparent=%proc.aname[3] gggparent=%proc.aname[4]"

  - source: k8s_audit
    fields:
      - ka.verb: "%ka.verb"
      - home_directory: "${HOME}"
      - my_field: "this is event number %evt.num"
    format: "with response code %ka.response.code"

Which issue(s) this PR fixes:

Fixes #3235
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

new(falco): introduce append_output configuration

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: LucaGuerra
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 [LucaGuerra]

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

The structure and functionality is there and can be reviewed, I need to figure out how to properly add this to the json schema and add an explanation to falco.yaml

/cc @incertum

I have updated the PR:

The json schema should be updated to reflect these changes
There is an explanation in falco.yaml about how to use this feature
Fields specified as - ka.verb are now supported. They will show up with their original type instead of being cast to string

This fixes the falcosecurity/testing failure: https://github.com/falcosecurity/testing/pull/61

Addressed @FedeDP 's comment, updated the json schema and also added a test for CLI options since the -o PR was merged in the meantime

LGTM label has been added.  Git tree hash: 04ed804283cb84988ae80420bf2bd60f16d1f84b

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, LucaGuerra
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 [FedeDP,LucaGuerra]

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

This PR may bring feature or behavior changes in the Falco engine and may require the engine version to be bumped.
Please double check userspace/engine/falco_engine_version.h file. See versioning for FALCO_ENGINE_VERSION.
/hold

false positive
/unhold


Disagreement when filtering by data source

Breaking case: Search for 'apoptosis' shows WikiPathways among results.
Filtering for 'Wikipathways' returns no results.

Fixed in commit 90833c7750e17ec5c406bddf5cc3e64ab6540e39. Switched from using id to name.


Is it possible to improve NetSerializer so it can serialize boxed-object property?

I know that net serializer only supports basic types. I want to know is it possible to improve this serializer to be able to serialize basic types that are boxed?
public class SamplePacket
{
        public object Prop { get; set; }

        public SamplePacket(object prop)
        {
            Prop = prop;
        }

        public SamplePacket()
        {

        }
}

...
var packet = new SamplePacket("abc");
as you can see the Prop in the packet is a string object, but NetSerializer cannot serialize such a property.

@sorencoder

I want to know is it possible to improve this serializer to be able to serialize basic types that are boxed?

No. This serializer generates delegates with precalculated types once when you call Subscribe for faster speed.

No. This serializer generates delegates with precalculated types once when you call Subscribe for faster speed.

I could find a way to serialize object properties, but it doesn't work for object[].
should I submit a PR?

@RevenantX
take a look at this PR: #151


Waypoint TP Feature

Stolen from emoisback, but improved

Infinite health affects the recall of pals

Infinite health affects the recall of pals

I think you need to open an Issue instead of commenting my PullRequest... 🫠

sorry i made an error and tried to delete it lol

Infinite health affects the recall of pals

I think you need to open an Issue instead of commenting my PullRequest... 🫠

sorry i made an error and tried to delete it lol

np, but I deleted my answer as well now 🤣

Has this been working reliably for you? I'm able to teleport to some locations perfectly fine, others put me in a loading screen and warps me back to base.

Has this been working reliably for you? I'm able to teleport to some locations perfectly fine, others put me in a loading screen and warps me back to base.

Tbh I didn't test it that much yet, all few locations I tried seemed to work, but I test it some more tommorow.

When you're free can you test the following locations? Trying to see if my issue is replicable.
Not working:

185,166
400, 490
-90, 150
-300, -300
-700, -450

all few locations I tried seemed to work

Luck of the draw lol. The first couple of random locations I tried didn't work.

You are right, some locations don't work.
At first I thought it was because every waypoint has a height of Z = 0.0, but raising that value before teleporting does not work properly either it seems.
I am not sure yet how to fix it...

It should work better now atleast I think.

Maybe someone else can try it again too.

Closed PR. Verified and added to master with credits. Thanks for collabing.

No, the remake character thing wasn't even working and I thought I had it removed already, so everything is fine. 👌


Revert "style(sponsors): Fix not showing svg image"

Reverts pycontw/pycon.tw#852

Codecov Report

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

@@           Coverage Diff           @@
##           master     #853   +/-   ##
=======================================
  Coverage   76.37%   76.37%
=======================================
  Files          70       70
  Lines        2688     2688
=======================================
  Hits         2053     2053
  Misses        635      635

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 4d17624...8a8db03. Read the comment docs.


Unexpected value in getOperatorList().argsArray[] for op 44 (showText)

Attach (recommended) or Link to PDF file here:
DesignerSpec-SG-009-01.pdf
Configuration:

Web browser and its version: NodeJS v10.16, Chrome 75.0.3770.100
Operating system and its version: Mac OSx
PDF.js version: 2.0.943
Is a browser extension: No

Steps to reproduce the problem:

Save the PDF file as DesignerSpec-SG-009-01.pdf
Run the following script:

#!/usr/bin/env node

const pdfjsLib = require('pdfjs-dist');

const go = async () => {
  const filename = 'DesignerSpec-SG-009-01.pdf';
  console.log('filename:', filename);
  const pdf = await pdfjsLib.getDocument(filename).promise;
  const page = await pdf.getPage(1);
  const operatorList = await page.getOperatorList();

  const index = 11;
  console.log('op:', operatorList.fnArray[index]);
  const [args0] = operatorList.argsArray[index];
  args0.forEach(item => console.log(JSON.stringify(item)));
  return 0;
};

go()
  .catch(err => {
    console.log('err:', err);
    return 1;
  })
  .then(code => process.exit(code))

What is the expected behavior?  All items in args0 will be objects.
What went wrong?  The third item in the list is a number.
filename: DesignerSpec-SG-009-01.pdf
op: 44
{"fontChar":"","unicode":"I","accent":null,"width":267,"isSpace":false,"isInFont":true}
{"fontChar":"","unicode":"t","accent":null,"width":347,"isSpace":false,"isInFont":true}
12.9
{"fontChar":"","unicode":"e","accent":null,"width":503,"isSpace":false,"isInFont":true}
{"fontChar":"","unicode":"m","accent":null,"width":813,"isSpace":false,"isInFont":true}
{"fontChar":"%","unicode":" ","accent":null,"width":226,"isSpace":false,"isInFont":false}
{"fontChar":"","unicode":"N","accent":null,"width":659,"isSpace":false,"isInFont":true}
{"fontChar":"","unicode":"a","accent":null,"width":494,"isSpace":false,"isInFont":true}
{"fontChar":"","unicode":"m","accent":null,"width":813,"isSpace":false,"isInFont":true}
{"fontChar":"","unicode":"e","accent":null,"width":503,"isSpace":false,"isInFont":true}
{"fontChar":"","unicode":":","accent":null,"width":276,"isSpace":false,"isInFont":true}

Of course I'm digging into internals, but this behavior is very curious, and the code I've examined in canvas.js for showText doesn't look like it expects this case....  Also, it looks like a spurious entry rather than a corrupted entry, because the text of unicode fields reads correctly.
This is just the first instance within this 1-page PDF.  We receive PDFs with 100s of pages showing this behavior 1000s of times.  Note that the fontChar vs unicode mismatch is what first drew my attention to this file.  That mismatch is common in files from this designer, but is otherwise uncommon.

What went wrong? The third item in the list is a number.

Please explain why you consider this to be wrong!
Given how the operator TJ is defined in the PDF specification, see https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G8.1904676 and the example just below, this is totally correct and thus expected behaviour.

[...] and the code I've examined in canvas.js for showText doesn't look like it expects this case...

Yes it does, please see https://github.com/mozilla/pdf.js/blob/5517c94d66f22cc98df6dd1dab90ced15d49f3b8/src/display/canvas.js#L1500-L1504

Unexpected because I'm not versed in the spec and just starting to use pdf.js.
Thanks for the quick response and pointers.  That's very helpful.

Closing as answered.


Block VP9/VP8 only for <1440p

Currently if you block VP8/VP9 everything that is 1440p or higher is not listed which breaks higher resolutions if those are available.
If only 1080p and lower VP8/VP9 was blocked this would not break higher resolutions.

You can edit what gets blocked so I don't see how this is a problem

@alextrv This feature would be amazing! A lot of people don't want to use VP9 and prefer h264 or AV1. However, most 2K and 4K videos are not available in AV1 and with VP9 blocked this extension will limit it to 1080p. So an option which enables VP9 is a video is 2K/4K and not available in AV1 would be great.

I second this feature request too, @alextrv!


321020043: Changes for running tests on macOS and Windows

Code review: 321020043: Changes for running tests on macOS and Windows

Coverage remained the same at 84.086% when pulling e3b00e4c0c28ae8a6a1a312b503c23893bd3dd3c on joachimmetz:tests into 85b922b317f5d44c9cbf312e14323b80133c4626 on log2timeline:master.

Coverage remained the same at 84.086% when pulling 7fc8804fb68e8999e6eb66b31d52d0d533b1beb0 on joachimmetz:tests into 85b922b317f5d44c9cbf312e14323b80133c4626 on log2timeline:master.

Coverage remained the same at 84.086% when pulling 48e1fa9d9fd199173d8b8573ed7dfc75e6b670c9 on joachimmetz:tests into 85b922b317f5d44c9cbf312e14323b80133c4626 on log2timeline:master.

Coverage remained the same at 84.086% when pulling d1b92a6db4dea242c84f1d8c0623d35693363301 on joachimmetz:tests into 85b922b317f5d44c9cbf312e14323b80133c4626 on log2timeline:master.

Coverage remained the same at 84.086% when pulling d1b92a6db4dea242c84f1d8c0623d35693363301 on joachimmetz:tests into 85b922b317f5d44c9cbf312e14323b80133c4626 on log2timeline:master.


[RELAY][DYN] Dynamic broadcast_to, zeros, ones

This PR adds a dynamic version of the relay broadcast_to, zeros and ones OP, and refactors the broadcast_to, zeros, ones OP to be purely static (not dynamic and static combined: undoes some of the refactor in https://github.com/apache/incubator-tvm/pull/5459/files). Also adds broadcast_to, zeros, ones to the dynamic to static conversion pass.

@zhiics could you take a look?

@zhiics Rebased and nitpicks fixed!

@electriclilies Could you modify the code according to the changes in #6047

Thanks @electriclilies @mbrookhart


"match" doesn't work without "patterns" (inside "captures")

if you want to retokenize ([\\s\\,\\w]+) with \\w+
you need to place "match" inside a "patterns": [] array
(or just add an empty "patterns" array, but that is not recommended)

https://github.com/worlpaker/go-syntax/blob/02bd7c945da893fdc9ec87db82eca176d4ff3432/syntaxes/go.tmLanguage.json#L1860-L1869

Thanks!


Jira cloud new tempo

Hi,
New tempo for Jira cloud broke Jira stopwatch :( Are you already aware of this issue ?
You can basically push the time but it is not saved in the new tempo.
Cheers

No I was not aware of this, since we don't use Tempo in my company. I'm not quite sure, what exactly you mean by it "broke Jira StopWatch" - could you elaborate?
StopWatch saves time in Jira by adding worklogs - basically just by using this API call: https://docs.atlassian.com/jira/REST/cloud/#api/2/issue/{issueIdOrKey}/worklog-addWorklog
I'm not really sure, what Tempo is for, so you will have to be more specific about what your problems are.

Hi,
Well, on the jira cloud version, the new plugin that it uses to add worklog is called tempo, and even if Jira stopwatch is actually making this API call, it seems to do not get populated correctly, I cannot see the timelog in the ticket either.
However I realise it might not be an issue on your side but an issue on Jira's API.
Cheers

I initially thought it wasn't working as well, but a co-worker informed me that it is severely delayed.  Sure enough, the hours that I submitted to JIRA last Friday via the JIRA Stopwatch appeared in my Tempo time sheet on Saturday.

So it's the integration between Jira and the Tempo plugin that has some issues.

@gallonmael can you confirm this?

Yes I can confirm, thank you both for this.


Fix view initialization with min/max resolution constraint

Previously the view could be initialized with a resolution or zoom parameter outside of the allowed range (either specified by resolutions array or maxResolution, minResolution, minZoom, maxZoom).
This PR refactors the initialization to 1/ be simpler and 2/ take into account the allowed resolution range. A specific test was added for this, which adds for verbosity in view.test.js but IMO makes the expected behaviour more explicit.
This fixes #9366

Yes, I thought of a better approach after creating the PR which should address that. Basically the idea is to apply all constraints at the end of applyOptions_.
There is also an issue where constraints are not applied when the map is resized, I'll try to address this as well (otherwise the initial extent constraint is moot anyway, as the map container does not always have a size).

@KaiVolland hi, to make this PR pass I had to remove the extent view parameter you used in the Zoomify rendering tests. To my understanding this was not needed anyway, could you please confirm? Thanks a lot

@jahow Confirmed, still works as intended.


SAA-264 refactor location endpoints

This refactors the 3 location-related endpoints and groups into a /locations controller, and same with tests /integration tests.

Codecov Report
Base: 68.81% // Head: 68.79% // Decreases project coverage by -0.02% :warning:

Coverage data is based on head (0544d28) compared to base (4668aa6).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #131      +/-   ##
============================================
- Coverage     68.81%   68.79%   -0.03%
+ Complexity      597      595       -2
============================================
  Files           136      134       -2
  Lines          2819     2817       -2
  Branches         82       82
============================================
- Hits           1940     1938       -2
  Misses          825      825
  Partials         54       54

Impacted Files
Coverage Δ

...vitiesmanagementapi/resource/LocationController.kt
100.00% <100.00%> (ø)

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.


VS insertions: wait for PR completion

We should turn on the "wait for PR completion" checkbox in our automated release for the insertion to VS, so that the release status dashboard has a good display of what's actually inserted.

Seems to work. The latest one didn't fail, and when I approved, it turned green.


replaces examples dir

Coverage remained the same at 83.307% when pulling f63b97856019b9e63eb1131e1be353c65c5a2e91 on hunterlester:examples into 7ceac83889303432cc05a6a7fb68d296ca869d34 on maidsafe:master.


Figure out app_label for explicitly listed SEEKER_MAPPINGS

Conflicts:
seeker/registry.py
tests/core/mappings.py
tests/core/tests.py

Just want to make sure before merging this - have you run the unit tests against your 2.1 branch?

All 4 unit tests passed on my 2.1 branch


Endpoint/Service Init Order Fix

This patch fixes an issue where service init failures would cause libStorage endpoints that use UNIX sock files to leave those sock files in place instead of removing them on error. This fix causes the service init routine to now occur before the endpoint init routine, thereby causing any service failure to occur before an endpoint's sock file is even created.
There is no issue filed for this fix, but it was a 911 issue raised by @kacole2 from the REX-Ray Slack channel. @cduchesne reproduced the error with a log file.

Codecov Report

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

@@            Coverage Diff             @@
##           master     #593      +/-   ##
==========================================
+ Coverage   33.14%   33.17%   +0.03%
==========================================
  Files          37       37
  Lines        2933     2933
==========================================
+ Hits          972      973       +1
+ Misses       1860     1859       -1
  Partials      101      101

Impacted Files
Coverage Δ

api/types/types_localdevices.go
80.88% <0%> (+1.47%)
: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 670ae33...cb162ff. Read the comment docs.

Hi @codenrhoden,
Once @cduchesne verifies it I'm going to merge this to master. At that point I'd have very few qualms about just relocating libStorage as a whole into github.com/codedellemc/rexray/pkg/libstorage and simply rewriting the paths using gofmt's package rewrite function. If we want to tag libStorage master as 0.6.3 so we know exactly which bits we copied over, then I'm fine with that too.

Hi @codenrhoden,
I guess my overall point is that if we collapse LS into RR sooner rather than later then the decision to do a minor release is only about RR instead of about both of them.

@akutz roger that. 👍


Update README

Update README.
Make docker container more verbose for dev purposes.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #59   +/-   ##
=======================================
  Coverage   62.65%   62.65%
=======================================
  Files          20       20
  Lines         241      241
=======================================
  Hits          151      151
  Misses         90       90

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 a55a3f2...3689114. Read the comment docs.


Tristan's Laundry List

[x] Look through signup code to move by just scraping on the API side.
[x] solo_claim_victory
[x] Moving Validation to game_utils
[x] Get rid of Object Oriented Get Game Response
[x] Remove silence dummy log implementation. Look for something else to silence

Please See Pull Request #3


[SPARK-25505][SQL] The output order of grouping columns in Pivot is different from the input order

What changes were proposed in this pull request?
The grouping columns from a Pivot query are inferred as "input columns - pivot columns - pivot aggregate columns", where input columns are the output of the child relation of Pivot. The grouping columns will be the leading columns in the pivot output and they should preserve the same order as specified by the input. For example,
SELECT * FROM (
  SELECT course, earnings, "a" as a, "z" as z, "b" as b, "y" as y, "c" as c, "x" as x, "d" as d, "w" as w
  FROM courseSales
)
PIVOT (
  sum(earnings)
  FOR course IN ('dotNET', 'Java')
)

The output columns should be "a, z, b, y, c, x, d, w, ..." but now it is "a, b, c, d, w, x, y, z, ..."
The fix is to use the child plan's output instead of outputSet so that the order can be preserved.
How was this patch tested?
Added UT.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3351/
Test PASSed.

Test build #96436 has started for PR 22519 at commit bd416bd.

Test build #96436 has finished for PR 22519 at commit bd416bd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/96436/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3363/
Test PASSed.

Test build #96455 has started for PR 22519 at commit d4e314a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3364/
Test PASSed.

Test build #96456 has started for PR 22519 at commit edc261c.

Test build #96455 has finished for PR 22519 at commit d4e314a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/96455/
Test PASSed.

Test build #96456 has finished for PR 22519 at commit edc261c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/96456/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3551/
Test PASSed.

Test build #96723 has started for PR 22519 at commit 2aee8b1.

Test build #96723 has finished for PR 22519 at commit 2aee8b1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/96723/
Test PASSed.

Thanks! Merged to 2.4 and master.

Should we also mention this in the migration guide?


npm build: permission denied mkdir

I tried to install shopware6 in Docker. When running the install script (./psh.phar install) I always get an authorization error with npm install:
Error: EACCES: permission denied, mkdir '/app/vendor/shopware/platform/src/Administration/Resources/administration/node_modules/node-sass/.node-gyp'

I have the same error. How did you fix this?


cabana: remove dependence on opendbc

Why aren't we relying on opendbc anymore?

Cabana currently parses DBC by itself,  the only dependency on opendbc is that it needs to read the DBC file list from the  opendbc directory.
this dbc file list can be obtained through car_fingerprint_to_dbc.json. so  looks like there is no need to link to the static library of OpenDBC anymore.

This removes a lot of DBCs from the list like radar DBCs and reference DBCs, really useful

Also, this removes radar DBCs from the list. Can we revert or at least add the remaining DBCs a better way? @deanlee

This removes a lot of DBCs from the list like radar DBCs and reference DBCs, used to be really useful.

@sshane :Just saw this message, the github notifications didn't alert me that I had this unread:(.
I'll fix this issue


Optimize some group circuits.

Refactor Group::new and Group::from_xy_coordinates to save constraints and increase clarity. The enforcement of a point being in the (sub)group is now delegated to a new circuit that does just that, and uses another new circuit to enforce that a point is twice another (this differs from the circuit that doubles a point).
This code has more separation between witness computation (console world) and circuit synthesis (circuit world), which is necessary to achieve some optimizations in the circuits.
There is a TODO for the witness computation in Group::new: there must be already code to check whether a pair of coordinates is in the (sub)group. This TODO is just at the console level; the circuit enforcement is already done in this commit.

I got a pre-commit hook error that seems unrelated to my changes, so I'm marking this PR as ready.

This PR supersedes https://github.com/AleoHQ/snarkVM/pull/2072.


ImportError for HelloWorldApp when running develop package

I can't seem to get the template to work, running Arch Linux with Python version 3.5.2. I hope the following information is useful 😄.
Steps to reproduce

Install the cookiecutter template with default options
Create a new virtual environment and install the dependencies locally
Run python setup.py develop as specified in the README
Run the helloworld executable

Expected behaviour
The example app should launch.
Actual behaviour
The executable helloworld fails with the following error (~ replaces my home directory):
Traceback (most recent call last):
  File "~/.venvs/helloworld/bin/helloworld", line 11, in <module>
    load_entry_point('helloworld', 'console_scripts', 'helloworld')()
  File "~/.venvs/helloworld/lib/python3.5/site-packages/pkg_resources/__init__.py", line 561, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "~/.venvs/helloworld/lib/python3.5/site-packages/pkg_resources/__init__.py", line 2631, in load_entry_point
    return ep.load()
  File "~/.venvs/helloworld/lib/python3.5/site-packages/pkg_resources/__init__.py", line 2291, in load
    return self.resolve()
  File "~/.venvs/helloworld/lib/python3.5/site-packages/pkg_resources/__init__.py", line 2297, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "~/test/helloworld/helloworld/cli.py", line 9, in <module>
    from helloworld import HelloWorldApp
ImportError: cannot import name 'HelloWorldApp'

Hi @kdelwat! 👋
Sorry to hear that. I haven't touched this project in ages and it worked just fine back then 😿 I don't have kivy set up and I'm not on Ubuntu/Manjaro Linux anymore.
I'm not sure how to help right now.

I've worked around the requirements and was able to reproduce the error you see. Can you please give it another try? I changed the import to be absolute so it would also work on Python 3.

The fix worked! HelloWorldApp is found. However, there seems to be a few issues with Python 3 support, including with gettext. I might try creating a PR at some point to resolve the issues.

Awesome, that would be great 😄

Resolved in #5


Integrate GitHub app test plan

[ ] Tested on local & docker
[ ] Documentation Updated
[ ] Attached required context / screenshot

To update in the docs:

For Github Bot in repository permission add: read & write permission for Issues  & subscribe to issue comment event.
Added env variable for github bot name to support mention feature.


Update EarlGrey to include TrustKit fixes

Our pull request was recently accepted, and we should update EarlGret to include this fix.

Reverted by @rotemmiz due to internal conflict with New Relic. I can't reproduce this issue with the latest New Relic, so awaiting internal upgrade of New Relic.

https://github.com/wix/Detox/pull/1408


Reintroduce tree-sitter-languages.

It seem to be active again, with proper builds, and a newer version of tree-sitter-rst. It allow to not have to do the build-parser step

Yeah, there seem to be some problems with the new release with both missing and broken wheels, let's move this to drafts.

All passing ! We don't need build-parser anymore.


difference vs classic site to site vpn?

how is this virtual wan different from just setting up a p2s vpn from each of the sites, please?

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

ID: 6d62470b-a511-4b32-5498-2ae5182ec585
Version Independent ID: df2d4c2e-8afb-14ae-6667-9a504a5f8197
Content: Use Azure Virtual WAN to create a Site-to-Site connection to Azure
Content Source: articles/virtual-wan/virtual-wan-site-to-site-portal.md
Service: virtual-wan
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@jurajgh, Thanks for the question! We are taking a look into this and will get back to you soon. In the interim, kindly take a look at the FAQ doc on Azure Virtual WAN which provides answers to some of the frequently asked questions: https://docs.microsoft.com/en-us/azure/virtual-wan/virtual-wan-faq

@jurajgh , You can have Point to Site, Express Route and VPN co-exist in the same VNET with Azure VWAN.
It lifts the limitation of having limited number of connections(Sites) from On-Premises and you can create upto 1000 connections for a Single Hub.
You can read this doc to know more about WAN: https://docs.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about
Let me know if you have any further questions.

@jurajgh , Do you have any further questions?

thx for response. i think I understand now. feel free to close this one.
On Mon, 1 Jul 2019 at 08:46, KARTHIK SRINIVAS<EMAIL_ADDRESS>wrote:

@jurajgh https://github.com/jurajgh , Do you have any further questions?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/34246?email_source=notifications&email_token=AFZH3DJADQ5IR252YVUVPMTP5GR4LA5CNFSM4H4KIO52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY5E3EA#issuecomment-507137424,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFZH3DKPFP75SKLLZZNFU63P5GR4LANCNFSM4H4KIO5Q
.

--
J.


[Error: Request to send data to device failed with error: BLE characteristic does not exist.] on ios

when trying to send custom data in ios ([Error: Request to send data to device failed with error: BLE characteristic does not exist.]) this error occur , in android works fine

I'm hitting the same thing.

You need to set up the custom data endpoint in your ESP device

True.


GreenHEART Simulation Examples

GreenHEART Simulation Examples

Added Jupyter notebook examples to the examples folder.

Green steel example
Offshore green hydrogen example

Related issue

Impacted areas of the software

Additional supporting information

Test results, if applicable

I think this looks pretty good. For the version of these that will help act as documentation to GreenHEART, let's remove the images from the repo so we don't clutter the git history. I think you also need to do a back-merge from the upstream branch to resolve the conflicts.


freezing jar dependencies

@purbon can you look at this?

testing and reviewing...

LGTM, merging so I can have another test case for our beloved jenkins.


qovery-cli: 0.94.10 -> 0.94.11

Diff: https://github.com/Qovery/qovery-cli/compare/refs/tags/v0.94.10...v0.94.11
Changelog: https://github.com/Qovery/qovery-cli/releases/tag/v0.94.11
Description of changes

Things done

Built on platform(s)

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 319275 run on x86_64-linux 1

1 package built:

qovery-cli


zotero: 6.0.10 -> 6.0.12

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/zotero/versions.
meta.description for zotero is: "Collect, organize, cite, and share your research sources"
meta.homepage for zotero is: "https://www.zotero.org"
meta.changelog for zotero is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.0.12 with grep in /nix/store/w9z5p0srrpx7b3ixvfry3g0k0wwg6bai-zotero-6.0.12
found 6.0.12 in filename of file in /nix/store/w9z5p0srrpx7b3ixvfry3g0k0wwg6bai-zotero-6.0.12

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
zotero

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/w9z5p0srrpx7b3ixvfry3g0k0wwg6bai-zotero-6.0.12 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A zotero https://github.com/r-ryantm/nixpkgs/archive/1cd743eb8ae80e746f101dddd5059fda7cfc8ff8.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/w9z5p0srrpx7b3ixvfry3g0k0wwg6bai-zotero-6.0.12
ls -la /nix/store/w9z5p0srrpx7b3ixvfry3g0k0wwg6bai-zotero-6.0.12/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

zotero

Maintainer pings
cc @i077 for testing.

@ofborg eval

Result of nixpkgs-review pr 187054 run on x86_64-linux 1

1 package built:

zotero


PLATML-1918 - Made changes to support default regression algorithm

@sathyarun18 @tumulurik
I was using snapshot version of authoring sdk in order to test these changes and I didn't want to include snapshot version in PR review. I'm planning to release authoring sdk once I get approve from both of you, as retail sales currently uses authoring sdk 0.16.1 and the newest one that will be released is 0.19.1.
I'll update pom file here after I release authoring-sdk to central repository.


Default namespaces generates problem

I get errors if an XML tag includes a default namespace declaration as below.
<Root xmlns='http://www.asam.net/mdf/v4/'>
If the tag define the namespace as xmlns:h='...', everything works OK.
A hint  or a temporary solution is to change the parser constructor to use XML_ParserCreate_MM("UTF-8", nullptr, nullptr) instead of the current XML_ParserCreateNS("UTF8", ':')

Could you send a sample file where I can check if bug is fixed?
And sorry, that it takes that long, I simply overlook the request as I was not very active on this project currently.

GitHub cannot append XML files of some reason but the below XML snippet should work as a verification.
<HDcomment xmlns="http://www.asam.net/mdf/v4">     <TX>ASAM MDF 4.0 Example file created by ETAS. Contents: 2 simple channel groups containing ints and floats in         little endian format.     </TX>     <time_source>PC timer</time_source>     <common_properties>         <e name="subject">Example</e>         <e name="project">ASAM Example Files</e>         <e name="department">ETAS GmbH</e>         <e name="author">Tobias Langner</e>     </common_properties> </HDcomment>

hmm, maybe because reader  is missing, I will setup a test case for the sample, with and without it.

I added a test to sources with the fragment above, as expected it returns namespace and element name separated by ":", means for the fragment the elementnames:
"http://www.asam.net/mdf/v4:HDcomment",
"http://www.asam.net/mdf/v4:TX",
"http://www.asam.net/mdf/v4:time_source",
"http://www.asam.net/mdf/v4:common_properties",
"http://www.asam.net/mdf/v4:e",
"http://www.asam.net/mdf/v4:e",
"http://www.asam.net/mdf/v4:e",
"http://www.asam.net/mdf/v4:e",
see test https://github.com/gittiver/libexpatpp/blob/main/test/test_asam_generation_problem.cpp

will close the issue. maybe a problem with documentation?
if something is missing, feel free to reopen.


Add documentation related to auto-mocking

Summary
The purpose of this PR is to add more documentation related to how Jest auto-mocks modules. It aims to clarify how Jest mocks and transforms values with jest.genMockFromModule. Resolves https://github.com/facebook/jest/issues/6812
Test plan
Add a few tests to verify the assertions made by the documentation in packages/jest-mock/src/__tests__/index.test.ts.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #8099   +/-   ##
=======================================
  Coverage   62.45%   62.45%
=======================================
  Files         264      264
  Lines       10374    10374
  Branches     2514     2514
=======================================
  Hits         6479     6479
  Misses       3318     3318
  Partials      577      577

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 c929ee3...746ea44. Read the comment docs.

Thank you!


closed caption

Hi, I try to download video with closed caption, but sometimes it doesnt work.
the video I want to download has the language subtitle that I want.
So, do you know what problem it is? can you fix it?
Thanks.

I can't know what is the problem if you don't share the video and the language

https://www.youtube.com/watch?v=hJg1UZnU7Hg&list=PLA281bxFYhI3b9YU6FcmArAcfbWC7DAi3&index=1
this is the video I want to download, and with Chinese subtitle.
thanks.

I only see English captions for this video. Maybe you got confused by YouTube's auto translate option?

I see, Thanks.
Sorry for disturbing you.


S251 small dataset ingest

No worries, thanks for checking through. All fixed now, I just one question about the retention for this use case. If we're allowed to keep data for 6 years, does that mean in 2023 we would accept a file from Q2/3/4 2016 as that will be the 2017 financial year? I'm thinking that we probably cannot keep this data as it will have been finalised and submitted in 2016


Client Allocation Request for: Vonechain

Client Allocation Questions
Core Information

Name: Vonechain
Website / Social Media: http://www.vonechain.com/
Region: Greater China
DataCap Requested: 5TiB
Addresses to be Notarized: f3rxun7fp4cdeuxquwvv23aktw47mxlf7bdohuwk7lmpkfofteo36fn32tnp7i42ta3hvpyuufwwcvcliuhkrq
Notary Requested: neogeweb3

@vonechain-official Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Thanks for you patience, during these days, I am busy with the slingshot matter, please forgive me.
1. Can you introduce yourself? Where can I find you online? (Github, Twitter, Linkedin handle, Wechat, etc.）
Vonechain Technology which was founded in year 2016 is a blockchain technology enterprise that established at an earlier time and fast developed in China. Currently, our headquarter office is located in Shanghai, whereas branch offices are located in Ningbo and Changsha.
Since developed, Vonechain Technology has served hundreds of clients from various industries which include finance, energy, agriculture, medical, education, property, fast-moving goods, etc.
Furthermore, Vonechain Technology has set up a public chain institute to provide industry technical support for blockchain technical development.
And Vonechain achieved in-depth cooperation with industry organizations from domestic and overseas in order to facilitate development of blockchain globalization together.
The official website is http://www.vonechain.com/ ，and there are many news about Vonchain, such as,
http://www.ifintechnews.com/readnews/8133.html
http://finance.sina.com.cn/stock/stockzmt/2021-01-20/doc-ikftpnnx9742171.shtml
http://www.cbdio.com/bigdata-expo/html/2020-06/29/content_6158753.htm
http://www.86qukuailian.com/news/2020/7917.html
https://movement.gzstv.com/news/detail/278328/
http://news.iresearch.cn/yx/2020/09/336917.shtml
https://www.chinaz.com/2020/1201/1211782.shtml
https://search.bilibili.com/all?keyword=旺链科技&from_source=video_tag
2. If you represent an organization, what is the name, nature, registration country, time since inception, and named officers of your organization?
The name of our organization is Vonechain Technology.Our company is essentially a technology company and committed to blockchain innovation. It was registrated in China and was founded in 2016.The officers of our organization is LiuTao.
3. In which region(s) do you intend to use the DataCap?
China.
4. What is your use case for the DataCap being requested?
We have built a web application http://www.filein.net/  that will store multiple types of data, which include the Image, text, video and so on. For this phrase, we will store the public dataset in the dataset list of slingshot competition.
5. Do you plan to specify advanced features when utilizing a DataCap in your storage deal? If so, please specify the feature.
No, in this phrase, we just want to test the storage flow and stablility and robustness. In the future, we will consider to add some new features to help store more useful data.
6. How many miners do you plan on allocating the DataCap? If you have a specific miner(s) you would like to allocate a DataCap, please specify.
I will send the data-deal to the different miners, they are in this list (https://github.com/filecoin-project/filecoin-plus-client-onboarding/blob/main/miners.md), because they are free to seal verified data. Besides, I will send some deals to my own miner(f0149132).
Considering the data redundancy, I will send one data to different miners for ten times(copies). Every miner can not more than 25 percent of all dataset.
7. Do you agree on providing transparency of DataCap allocation decisions & execution details in public to prevent excessive/unfair self-dealing?
Yes, I will post the deal transactions list，which will include “deal_id, miner_id, payload_cid, filename, file_format, size_in_bytes, date, curated_dataset”.

Hey @vonechain-official, thanks for the update, I will take a look and get back to you.

Hey @vonechain-official, thanks for waiting. My allocation strategy is to build trust progressively. So I could allocate 100 GiB to you for the first time. Feel free to request more DataCap when you use up the allocation.

I am experiencing the 'verified client already exists' error during allocation, I will keep you posted on this.

Hey @vonechain-official, I will not be able to allocate DataCap to you until the v13 hyperdrive network upgrade with the acceptance of FIP-0012. There are two options available:

spend the entirety of your previous allocation;
wait until the v13 hyperdrive network upgrade.

Either option will make this allocation successful. Let me know!

Request Approved
Your Datacap Allocation Request has been approved by the Notary
Message sent to Filecoin Network

bafy2bzacedehpb4u4xplslgc76yli72f7g7v4uzmlg42nzeghqmng66n7273g

Address

f3rofi6lad6glpfwewv7aejwqkplbsx3j2vvxhscrbouvldckt3wfwcohjdeqj4kgyhqmiw6qp3onbktuv545a

Datacap Allocated

100GiB

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedehpb4u4xplslgc76yli72f7g7v4uzmlg42nzeghqmng66n7273g


SD 1.5 version?

Hey, I was wondering if you have something similar that can convert a SD 1.5 checkpoint into diffusers. I tried looking at kohya's model_util but I couldn't find an easy way to do it, and a friend tried adapting your code but it's not working.
Thanks in advance for any guidance.

Yea it me :3 - So it's likely an attribute problem and  I did send the link over on twitter so i'll keep stabbing at it until someone peeks and goes "OH THIS EUREKA! you missed this!" - :P


Outgoing/dockerchanges

Changes proposed in this PR

Slight refactor in how we build docker images.
Avoids the pip install + requisite CPU time.

Why are we making these changes?
Avoids 200mb of downloads + 200 seconds to generate docker images for
the docker-based integration test workflow.
A docker image build and integration test run in it goes from
350 to 150 seconds.
See https://github.com/twosigma/Cook/pull/954 for the last round of this. I've made the requested review changes.

I'll let @DaoWen review this.

As previously discussed in #954, since we mount the integration tests as a volume when running locally, the rebuild overhead typically isn't much of an issue. But I don't see any harm in merging this, and maybe it'll help with some future workflow.


ci: add github-release.yaml

Description

It's useful if we can prepare releases after pushing a tag.
I'd like to add this workflow to all Autoware repositories.
It's already used and tested in autoware-github-actions.
https://github.com/autowarefoundation/autoware-github-actions/releases
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[x] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

After this is approved, I'll update the sync-files settings in each repository.

I've added inputs for workflow_dispatch and tested it in my fork.
https://github.com/kenji-miyake/autoware-github-actions/releases

@esteve Thank you for your review!
As I'm thinking of supporting beta/vX.Y.Z branches, I'll push some code later. Please re-review then. :bow:

Tested like this.


Enable polling support for tailwindcss cli

Reasoning
Due to an WSL2 issue (https://github.com/microsoft/WSL/issues/4739) the watch mechanism of the tailwindcss cli will not work on all potential developer setups. Especially when using vscode-devcontainers and keeping the code in the mounted directory. (assumed default behavior)
The recommended work around is to use polling instead of the normal inotify based watch mechanism.
Changes

This pull request will add a new task to tailwindcss-rails to use the polling option instead of the watch option
A parameter is added to the ./bin/dev script, to switch between watch and poll mechanism
Default behavior of tailwindcss-rails remains unchanged

Waiting for TailwindCSS to ship the polling feature. The feature was omitted in the recent v3.0.24 release.

@thebub I have a new rails 7 application with tailwindcss installed.  None of my CSS changes are reflected when reloading my pages.  Is this a current limitation to working with WSL2?  Or perhaps these issues are separate. Thanks.

@daveomcd I believe this is related to the wsl2 problem mentioned before, try moving your project files to your linux home folder (e.g. /home/daveomcd or ~) and see if the problem still happens

@daveomcd I suggest you follow the recommendation by @hyphenized and provide feedback, whether the problem is resolved or not.

@daveomcd I suggest you follow the recommendation by @hyphenized and provide feedback, whether the problem is resolved or not.

Hey @thebub, thank you for the response.  I figured out the issue I was seeing wasn't a problem with WSL2.  It was because I ran rake assets:precompile by accident.  To correct the problem I had I just needed to delete all the files in my public/assets folder.

I've created #199 which uses a task argument to implement this, which is a bit more flexible than a separate task (and can be combined with other options like debug from #198).

v2.0.13 has this feature, please see the README for an explanation.

Thanks @flavorjones. I wasn't aware of the possibility to add options as well. This is a way better solution!


Codesys Package for MegaBAS

@nikke344 is there any way you can post the source code for the Codesys package? In Codesys 3.5 SP20 there are a few compatibility issues as the package was compiled for 3.5 SP16 Patch 2. I got other stuff in my project that requires SP18 or greater so I can't run the older version of Codesys for my project. I will fix it and upload the updated version for SP20 for everyone to use if you don't have the time to work on it yourself.
Thanks

Hi Alex, @alexburcea2877
Do you got any other way to get ahold of @nikke344? He may not be getting alerts from this github account linked to this name, as he has no other projects linked so it looks like he created the account just to post this package for you. I really need to make this compatible with Codesys 3.5 SP20. I have it working partially for right now but there are some libraries that its compiled against that need to get updated to make this package fully work with SP20. This is going to be an on going issue as Codesys updates their libraries so you are going to need the source to be able to rebuild it to keep it working with the current version of Codesys as they release updates. I got some other HATs on the RPi that require >=SP18 so I am forced to run the current version to make my other devices work. If you got an email or phone number for him please can you reach out to him and ask for him to post the source code it will help me out a lot and I can keep purchasing more of the MEGA_BAS HATs from you. I got about 50 of these installed and we here at HBAC are going to be ordering another 20 or 25 boards in two weeks.
-Thanks
Howard Jr.

Hi Howard,
I am unable to reach nikke344 and I did not find any code from him on my
computer. The solution here is to make a new library for the BAS. Please
look at Sequent libraries on GitHub
https://github.com/SequentMicrosystems/SM_CODESYSand tell me if one of
the same types made for BAS will be suitable for you.
The libraries we made contain the source code so you can recompile for any
CODESYS versions.
Best regards,
Alex.
On Sat, Jun 8, 2024 at 12:22 PM Howard J. Bleier @.***>
wrote:

Hi Alex, @alexburcea2877 https://github.com/alexburcea2877
Do you got any other way to get ahold of @nikke344
https://github.com/nikke344? He may not be getting alerts from this
github account linked to this name, as he has no other projects linked so
it looks like he created the account just to post this package for you. I
really need to make this compatible with Codesys 3.5 SP20. I have it
working partially for right now but there are some libraries that its
compiled against that need to get updated to make this package fully work
with SP20. This is going to be an on going issue as Codesys updates their
libraries so you are going to need the source to be able to rebuild it to
keep it working with the current version of Codesys as they release
updates. I got some other HATs on the RPi that require >=SP18 so I am
forced to run the current version to make my other devices work. If you got
an email or phone number for him please can you reach out to him and ask
for him to post the source code it will help me out a lot and I can keep
purchasing more of the MEGA_BAS HATs from you. I got about 50 of these
installed and we here at HBAC are going to be ordering another 20 or 25
boards in two weeks.
-Thanks
Howard Jr.
—
Reply to this email directly, view it on GitHub
https://github.com/SequentMicrosystems/megabas-rpi/issues/17#issuecomment-2156148547,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD3ZCWUQ2ZQ2K4KEONRMWA3ZGNKWZAVCNFSM6AAAAABIUWK5J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJWGE2DQNJUG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi Alex,
Thanks for the link, I will take a look into it next week after I finish this project over the weekend. I got a RPi with a stack of 5 of the MEGA_BAS that I am doing the commissioning on this weekend. Its a fun one, I am migrating the points off of 4 old devices, a Delta Controls system that is crapping out over to the MEGA_BAS boards running Codesys 3.5. I got to keep the system running as I do it because the system is currently in productions, I'll have this done by Sunday, then I can look into it. After I rebuild the new library next week I will have to rebuild this project to get rid of all of the current Codesys 3.5 SP20 errors and warnings. I will send you the source code and the package file so it can make another repo on there, that way it can hopefully help others with the MEGA_BAS that need to run the current Codesys release too. Thank you, these MEGA_BAS boards are working great by the way, very good product you guys are making. Keep up the awesome work!
Thanks
-Howard Jr.

Hi Howard,
When I gave you the link to the repo with Codesys libraries, I asked if this is the type of libraries you need.
I managed to create a new library for the BAS, check it out here and let me know if it fits your needs.
Alex.

Hi Alexandru,
It looks like there is something wrong with the SM_BAS.package
When you try to install it in codesys it says the path is wrong and
closes out.
It will not install.
On 2024-06-12 22:02, Alexandru Burcea wrote:

Hi Howard,
When I gave you the link to the repo with Codesys libraries, I asked
if this is the type of libraries you need.
I managed to create a new library for the BAS, check it out here [1
[1]]
and let me know if it fits your needs.
Alex.
--
Reply to this email directly, view it on GitHub [2 [2]], or unsubscribe
[3 [3]].
You are receiving this because you authored the thread.Message ID:
@.***>
Links:
[1]
https://github.com/SequentMicrosystems/SM_CODESYS/tree/main/Building Automation
[2]
https://github.com/SequentMicrosystems/megabas-rpi/issues/17#issuecomment-2164380685
[3]
https://github.com/notifications/unsubscribe-auth/AHVQR2XH7ZTYCUEMATEUSXTZHERXBAVCNFSM6AAAAABIUWK5J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRUGM4DANRYGU

Links:
[1]
https://github.com/SequentMicrosystems/SM_CODESYS/tree/main/Building Automation
[2]
https://github.com/SequentMicrosystems/megabas-rpi/issues/17#issuecomment-2164380685
[3]
https://github.com/notifications/unsubscribe-auth/AHVQR2XH7ZTYCUEMATEUSXTZHERXBAVCNFSM6AAAAABIUWK5J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRUGM4DANRYGU

I will take a look but until then you have all the components to install it manually. The SM_BAS.devdesc.xml and SM_BAS.library are the files you need. Go to Tools> Device Repository to install the XML file and to Tools>Library Repository to install the library.

Yes the manual install method works. There is just something wrong with the compiled .package version. But the library and .devdesc.xml work perfectly. Thank you I got it to work now using those instead of the package version.Sent from my iPhoneOn Aug 11, 2024, at 9:23 AM, Alexandru Burcea @.*> wrote:
I will take a look but until then you have all the components to install it manually. The SM_BAS.devdesc.xml and SM_BAS.library are the files you need. Go to Tools> Device Repository to install the XML file and to Tools>Library Repository to install the library.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I am glad it worked. I will postpone a little bit the package fix.


bard使用 聊天就报错闪退

Please input your question
User:
mnmn
Bot:
[WARNING][2023-08-25 03:09:31][log.py:39] - Cookies may be wrong:'NoneType' object has no attribute 'group'
[ERROR][2023-08-25 03:09:31][log.py:47] - [MultiChannel] Start up failed on terminal: 'NoneType' object has no attribute 'ask'
[ERROR][2023-08-25 03:09:31][log.py:45] - App startup failed!
[ERROR][2023-08-25 03:09:31][log.py:50] - 'NoneType' object has no attribute 'ask'
Traceback (most recent call last):
File "/root/bot-on-anything/app.py", line 42, in main
start_process(channel_type[0], args.config)
File "/root/bot-on-anything/app.py", line 23, in start_process
raise e
File "/root/bot-on-anything/app.py", line 20, in start_process
channel.startup()
File "/root/bot-on-anything/channel/terminal/terminal_channel.py", line 21, in startup
for res in super().build_reply_content(prompt, context):
File "/root/bot-on-anything/channel/channel.py", line 31, in build_reply_content
return Bridge().fetch_reply_content(query, context)
File "/root/bot-on-anything/bridge/bridge.py", line 18, in fetch_reply_content
return model_factory.create_bot(type).reply(query, context)
File "/root/bot-on-anything/model/google/bard_model.py", line 28, in reply
answer = bot.ask(query)
AttributeError: 'NoneType' object has no attribute 'ask'

cookies确定是正确的

WARNING][2023-08-31 16:05:01][log.py:39] - HTTPSConnectionPool(host='bard.google.com', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1129)')))有出现这个东西吗


Is project going to support  preact 10?

Hello,
I migrated preact-render-spy to Preact 10. You can take a look at https://github.com/shelacek/preact-render-spy. It's WIP and there are some corner cases where this fork behaves differently.
@gnarf, @mzgoddard can you please comment on the Preact 10 support?

Thanks!)

I apologize for the late reaction.
I'd like to make a PR, but at the moment I'm not sure if it would ever be accepted. However, I quite like preact-render-spy for smaller projects over a much bigger enzyme. If there is no reaction from maintainers, maybe we can join forces elsewhere. I've also noticed some meaningful commits from @soerenvullriede2101.

We used preact-render-spy for a small project, with the update to v10 we wanted to use Fragments, so we updated the fork of @shelacek and fixed some tests.  It seems like the contains function etc. does not work anymore.  I could create a PR for the stuff we did, but this project seems kinda abandoned.

Any update on this?

thanks for the info, FYI: I checked out a new prect-cli typescript project and it is using enzyme now.

We migrated towards preact-testing-library, https://github.com/forem/forem/pull/8224


Typo : Warejpise

The Movement Worksheet , Warehouse Internal Pick, and Warejpise Internal Put-away pages

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

ID: 86d0ec80-99f3-35c5-1484-9b6ced2b0ec9
Version Independent ID: 905989a9-0635-a944-ab7c-8244ce465e11
Content: Move Items in Warehouses That Use Directed Put-away and Pick - Business Central
Content Source: business-central/warehouse-how-to-move-items-in-advanced-warehousing.md
Service: dynamics365-business-central
GitHub Login: @brentholtorf
Microsoft Alias: bholtorf

Hello,
Thanks for pointing this out. We've corrected the typo and will publish the updated article soon.


[Security]: vulnerability of invalid Last-will msg

Describe the bug
We found a SEGV cased by member access within null pointer of type 'nni_msg' (aka 'struct nng_msg')  in nni_msg_set_cmd_type function of message.c when it processes malformed messages.
Expected behavior
If Asan is enabled at compile time, the NanoMQ crashes and displays ASAN information.
Actual Behavior
SEGV, runtime error: member access within null pointer of type 'nni_msg' (aka 'struct nng_msg')
To Reproduce
start nanomq with ./nanomq start
Send the packet：nc <IP_ADDRESS> 1179 < ./1179-poc.raw
1179-poc.zip
in nni_msg_set_cmd_type function of message.c

in server_cb function of broker.c

Asan Log

/home/user/nanomq/nng/src/core/message.c:711:5: runtime error: member access within null pointer of type 'nni_msg' (aka 'struct nng_msg')
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /home/user/nanomq/nng/src/core/message.c:711:5 in =================================================================
==3076672==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000088 (pc 0x00000060754b bp 0x7ff360ea8a10 sp 0x7ff360ea89f0 T11)
==3076672==The signal is caused by a WRITE memory access.
==3076672==Hint: address points to the zero page.
#0 0x60754b in nni_msg_set_cmd_type /home/user/nanomq/nng/src/core/message.c:711:14
#1 0x57d2a9 in server_cb /home/user/nanomq/nanomq/apps/broker.c:667:6
#2 0x646595 in nni_taskq_thread /home/user/nanomq/nng/src/core/taskq.c:50:4
#3 0x64caf0 in nni_thr_wrap /home/user/nanomq/nng/src/core/thread.c:94:3
#4 0x66a073 in nni_plat_thr_main /home/user/nanomq/nng/src/platform/posix/posix_thread.c:266:2
#5 0x7ff368f21608 in start_thread /build/glibc-SzIz7B/glibc-2.31/nptl/pthread_create.c:477:8
#6 0x7ff368cad132 in clone /build/glibc-SzIz7B/glibc-2.31/misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:95
SUMMARY: AddressSanitizer: SEGV /home/user/nanomq/nng/src/core/message.c:711:14 in nni_msg_set_cmd_type

** Environment Details **

NanoMQ version: 0.16.5(aa188a4d) & da4d3c8a
Operating system and version: Ubuntu 20.04
Compiler and language used: gcc 9.4.0 clang 10.0.0
testing scenario: Run the broker(build with ASAN and TSAN) with the ./nanomq start command

I reported the same vulnerability by email the other day, the corresponding raw data is available for reference.
raw_data.zip

Thanks for reporting vunerbility bug.
This is identified and will be fixed now.
The first discover credit goes to @songxpu

I found the bug in version 0.16.5 last month, and I'm sorry that I was late for reporting this problem

Thanks for your comment and confirmation. I found the bug in version 0.16.5 last month, and I'm sorry that I was late for this problem. I think we(@songxpu) have discovered this bug independently.

Nevermind, you guys both are heroes


Chore/drop travis

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add ocpoc target to CI

Adds ocpoc build target to docker_run.sh - in response to PR #7787 - and updates some board_config items that had broken the build target. Docker file and container were added/built in containers PR #73.
@dagar It seems like semaphoreci is the appropriate place to add ocpoc, since that's where rpi and bebop run their test builds, but I'll reiterate that I'm brand new to the CI side of things. I haven't added the target yet, as I don't really know how to add the target to semaphoreci.

Thanks David.
A lot of the setup is based on how we could evenly spread things across the hosted CI services.
Unfortunately the semaphoreci configuration isn't stored in the repo. I'll add an ocpoc build after bebop + raspi.

@davidaroyer Can you confirm exactly what you want CI to do?
./Tools/docker_run.sh 'make posix_ocpoc_cross'

Thanks for checking on that, the toolchains are for the ubuntu version of the build (the posix_ocpoc_cross target uses Petalinux toolchains that aren't nearly as easy to get a hold of). So let's have CI run the following:
./Tools/docker_run.sh 'make posix_ocpoc_ubuntu'

Thanks again for all your help!

FYI this is now building on semaphoreci.


Update README.md

Issue #, if available:
Closes 463
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 6c2b8348e62cc176e77fe7ad5d5933dfebbd8649
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: d353a1a8a244f9a1fc279f728aa85ed5b3555e3e
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 1bfd87a0238f26451de22f95bdbcef5140b660ec
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 9e36e856f167afbbfbad29b294880049c65bb4a2
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: e5a2b13e389a9419412134ce9b88f5d408c609df
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: fb20373d8a11c6df8fc992926e56ffd26bf7e289
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 5de8eb0edb34b549cd21cbee981e834b229a972d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 78a0427cb7dbb73cffa974e71861266ab2a8ab1e
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: f2373112d170a437b97a8fe6583e41ba0333a37a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 8b4d0900dea71b14cfa9479f7c3e3c3cf011eebe
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 0b64eb1d9048a45fa5cebff6d5c32102fd0b1947
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 6d6e6bab2dcdaf70ae4b4e5bc0dea6f2bbec7f52
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: a88de0ef0d9fcdd1007c09316b61f33701154eff
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 0b64eb1d9048a45fa5cebff6d5c32102fd0b1947
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Provide new task to merge external clover.db with unit test generated clover.db to combine instrumented jar results with unit tests results

I have the plugin setup to run so I can get code coverage on my unit tests and also to generate an instrumented jar. Both of these work fine. What I would like to know is how can I combine the results of running my testing against the instrumented jar with that of the instrumented unit test results? Is this even possible?
Essentially what I would like to do is the following:

Build and collect unit tests code coverage.
Run separate tests against the instrumented jar.
Combine those results with the unit test results.

Currently I can generate both reports with some manipulation of the build/clover files but I cannot figure out a way to combine these.
Thanks.

It depends on how you setup your instrumented JAR tests. If you are using Gradle to run them you could make it so that the instrumented JR test uses the same clover.db file as the unit tests code coverage. Then Clover would just update the DB file with the additional coverage.
A more involved approach would require that you setup the instrumented JAR tests as a subproject resulting in a new clover DB that could be merged with the main project using the cloverAggregateDatabases task.
I have not tried either of these approaches but if you can get them to work it would be a great help to the project to document your steps.
FYI, the file where clover.db is generated can be read from the clover extension. This would be something like: clover.initString
You can use that value to inject the Clover property like this -Dclover.initstring=${clover.initString} for your instrumented JAR tests causing them to use the same DB file. This assumes you are executing a JAVA process like a server which expects system properties like this.

With what you are doing the best way I know how is to directly invoke the Ant tasks in the OpenClover JAR that perform the merge databases work. Perhaps I can add such a task for you in the plugin to take an external generated database and merge it using a special invocation. We already do this merge for multiproject setups to generate a consolidated report. I believe this could be implemented with a little effort on my part to make this a generic solution for others doing similar to what you are.

That would be great. I did resort to using the open clover jar directly but have not gotten to test out the above. I am hoping it will merge the databases in the way I think it should. This was previously done when our build scripts were in ant but there have been a lot of architectural changes since and it would not be feasible to port the old method.
It would be great if you added a task for merging the database!

The plugin uses the Ant tasks to generate the databases. The databases are generated by Clover as the unit tests are executed not during the reporting phase. For multi-project configuration an extra task cloverAggregateDatabases is executed to perform the clover-merge Ant task.
The Clover execution uses intermediate files named by suffixing the base name of the db file which is derived by the test task name. What I am planning to do is add a new custom task to the plugin that can be used as a database file holder for custom builds that use instrumented JAR files. That will give Gradle a way to reference the database generated by the custom tasks and allow the cloverAggregateDatabases task to do the clover-merge execution correctly.

Sounds good.


Elasticsearch GUI plugin

It should be great if you add Elasticsearch GUI installation in the docker image.
Actually I have to instal successfully the gui in the running container entering in the container:
docker exec -it build_elasticsearch_1 bash
root@91cb5674cfb3:/# plugin --install jettro/elasticsearch-gui
-> Installing jettro/elasticsearch-gui...
Trying https://github.com/jettro/elasticsearch-gui/archive/master.zip...
Downloading ...................................................................................................................................................................................................................................................................................................................DONE
Installed jettro/elasticsearch-gui into /usr/share/elasticsearch/plugins/gui
Identified as a _site plugin, moving to _site structure ...
root@91cb5674cfb3:/# exit

Thanks
Regards
Gianluca

In my opinion adding any plugins to this image ruin the concept of a base image. What I am doing is building my own Dockerfile that extends the official image to install the plugins that I use. I think that is the best approach, but you can always clone this repo and then make the changes you want.


Add DWOC fields for configuring project clone init container

What does this PR do?
Adds fields to the DevWorkspaceOperatorConfig CR for configuring project clone:
config:
  workspace:
    projectClone:
      image: <project-clone-image>
      imagePullPolicy: <pull-policy>
      env: []<env-var>
      resources:
        limits:
          memory: <quantity>
          cpu: <quantity>
        requests:
          memory: <quantity>
          cpu: <quantity>

with the following behavior:

If image is specified, it is used for project clone. Otherwise, the image from the operator definition (relatedImages) is used
If imagePullPolicy is unspecified, the value from config.workspace.imagePullPolicy is used
Environment variables are appended to the container's default env vars
Resources override default configurations, with quantities specified as "0" interpreted as "unset"

I.e. If a quantity is "0", that field is omitted from the project clone container's resources field. If all fields are zero, no resources are specified.

What issues does this PR fix or reference?
Closes https://github.com/devfile/devworkspace-operator/issues/1080
Is it tested? How?
Test by setting fields and verifying that they are used for the project clone container. Note that editing the dwoc CR does not trigger reconciles for workspaces by itself, so if your workspace is running you may need to poke it (e.g. by setting an annotation or restarting it)
PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

Also just wanted to show:
When the CPU or memory request can't be satisfied in the project-clone container, the devworkspace will fail in a similar manner to when the main devworkspace container's memory or CPU request can't be satisfied:
NAME          DEVWORKSPACE ID             PHASE    INFO
code-latest   workspace764fb09a01b9487d   Failed   Error creating DevWorkspace deployment: Detected unrecoverable event FailedScheduling: 0/6 nodes are available: 3 Insufficient cpu, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/6 nodes are available: 3 No preemption victims found for incoming pod, 3 Preemption is not helpful for scheduling..

There's no mention of the project-clone container failing specifically. Not sure if this is something we should address (or perhaps leave as an issue for a future improvement).

@AObuchow I don't think it's feasible to report why scheduling failed; in your case it failed because you increased the project clone requirements, but from the cluster's perspective, it failed because the pod itself requested more CPU than any node had available.